To be fixed.

[ ] Display "POLY LINK" when changing parameters of linked poly tracked.
[ ] Shift and reverse is not shifting/reversing slide mask.
[ ] Allow folder manipulation in load project page.

Allow folder manipulation in load project page

folder manipulation?

cd
mkdir
etc.

Minor bug : in chromatic mode if the kit is changed in the MD, it's not following in the MC. Need to go out of the chromatic menu and then come back in for effective change.
MD 1.71, MC 2.70
Megacommand is fantastic :)

Minor bug : in chromatic mode if the kit is changed in the MD, it's not following in the MC. Need to go out of the chromatic menu and then come back in for effective change.

Yeah, this is a known 'feature/issue'. We need to implement some changes on the MD side to alert the MC when the kit's machines are changed.

MD 1.71, MC 2.70
Megacommand is fantastic :)

cheers. let us know if you run into anything else.


In final stage of setting up machine, it says active when it's not complete

Version - v1.0.0-rc3
Steps to Reproduce:

Add Packet host

Results: During the final step where we are "Waiting for agent connection", the status on the host page says Active

Expected: Shouldn't say active... maybe a "waiting" state would be better.

version - master 6/17
Verified fixed


(maint) Retire the cli version of the anonymizer tool

This commit retires the CLI version of the anonymizer code.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/139/
Test PASSed.


Release version 0.0.6

Codecov Report
All modified lines are covered by tests :white_check_mark:
:loudspeaker: Thoughts on this report? Let us know!.


Add documentation for Using Images

@jisqyv @afmckinney
Please review and merge
This is documentation only

@halatmit LGTM

@halatmit MERGED


Typo in readme's gradle section

dependencies {
    ...
    compile 'com.github.LiquidPlayer.LiquidCore:0.2.2'
}

should read like:

dependencies {
    ...
    compile 'com.github.liquidplayer.LiquidCore:0.2.2'
}

Are you sure about that?
See: https://jitpack.io/#LiquidPlayer/LiquidCore/0.2.2
It is also like this in the example, which builds correctly: https://github.com/LiquidPlayer/Examples/blob/master/HelloWorld/app/build.gradle

It seems there where some caching problems in our gradle build script in combination with Android studio.
The original 'com.github.LiquidPlayer.LiquidCore:0.2.2' was right so!


Feature: doker build jobs #26

close #26

Let me look into this, feel free to work on other issues.


Command line buffer insertion error in WSL

Microsoft Windows [Version 10.0.16299.371]
Context: This issue was discovered after editing the same command multiple times, after the length of the command extended past the window boundary. Reproducibility may vary.

Attempted to create a long chain command with a python utility to retrieve files from Internet Archive

tealsuki@DESKTOP-NENQ6QK:/mnt/d/temp$ ia search 'collection:solarsystemcollection' --itemlist | parallel --no-notice -j4 'ia download {} --glob="*.jpg|*.jpeg"'

Decide to cancel and change parameters (CTRL+C, followed by UPARROW to return to command in buffer, followed by cursoring through and editing the command)

tealsuki@DESKTOP-NENQ6QK:/mnt/d/temp$ ia search 'collection:printer-manuals-lexmark' --itemlist | parallel --no-notice -j4 'ia download {} --glob="*.pdf"'

What's wrong / what should be happening instead:

Command fails silently in this instance.
Upon returning to it in the buffer, it is revealed that the insertion point was in the incorrect position, parts of the displayed text were chopped out when the first character was inserted.

Additional notes
When editing the command, pressing the up arrow once more to traverse the buffer, and then pressing the down arrow to return to what Bash has saved as the "workspace" command (my description) will present the actual state of the command again.

Traversing the buffer multiple steps may affect reproducibility
Resizing the window may also affect reproducibility
May be related to WSL#1307 WSL#1497 and WSL#1756

Console settings:

Issue persists in Windows 10 Version 1803

Judging by the "so" leftover from the previous command, and the unexpected immediate visual deletion of the "' " (single quote and a space) the internal cursor seemed to assume it was 2 places to the right of where I'd intended to begin deletion with the visual cursor (positioned at the closing single quote). This appears to also be limited to the last executed command in my test. Further traversal does not produce the same effect.

Still having this issue in 1803 build 17134.765.

That build is two major versions out of date. Learning that it still reproduces as of approximately two (at this point) years ago is not helpful :smile:

@tealsuki Is this still happening for you (especially in the Windows Terminal)? This report's a few years old now and hasn't had any bumps on any recent builds of Windows, so it's entirely possible that this is something we just fixed along the way.


[compile] support FE compile working in windows

What type of PR is this：

[ ] bug
[ ] feature
[ ] enhancement
[ ] refactor
[x] others

What's the purpose?

run starrocks_fe_unittest

What's the purpose?

Make it easier to build FE development environment on windows

[FE PR Coverage check]
:heart_eyes: pass : 0 / 0 (0%)

run starrocks_admit_test

[FE PR Coverage check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage check]
:heart_eyes: pass : 0 / 0 (0%)


dataserv-client 2.1.12 crashes on OSX

I decided to upgrade from dataserv-client 2.1.4 to the latest release (2.1.12). Though everything with 2.1.4 worked fine, 2.1.12 crashes immediately, even when checking the version.
I am running OSX 10.11.2, and have tried to uninstall/install/upgrade, all with the same result.
% dataserv-client version
Traceback (most recent call last):
  File "/usr/local/bin/dataserv-client", line 6, in <module>
    from dataserv_client import cli
  File "/usr/local/lib/python2.7/site-packages/dataserv_client/cli.py", line 4, in <module>
    from dataserv_client import api
  File "/usr/local/lib/python2.7/site-packages/dataserv_client/api.py", line 7, in <module>
    import storjnode
  File "/usr/local/lib/python2.7/site-packages/storjnode/__init__.py", line 3, in <module>
    from . import network  # NOQA
  File "/usr/local/lib/python2.7/site-packages/storjnode/network/__init__.py", line 1, in <module>
    from . import node  # NOQA
  File "/usr/local/lib/python2.7/site-packages/storjnode/network/node.py", line 13, in <module>
    from pyp2p.unl import UNL
  File "/usr/local/lib/python2.7/site-packages/pyp2p/unl.py", line 6, in <module>
    from .lib import *  # FIXME * is evil!
  File "/usr/local/lib/python2.7/site-packages/pyp2p/lib.py", line 37, in <module>
    ip = IPDB()
  File "/usr/local/lib/python2.7/site-packages/pyroute2/__init__.py", line 89, in __new__
    cls.register(cls.registry['class'])
  File "/usr/local/lib/python2.7/site-packages/pyroute2/__init__.py", line 69, in __getitem__
    [name], 0)
  File "/usr/local/lib/python2.7/site-packages/pyroute2/ipdb/__init__.py", line 396, in <module>
    from pyroute2.iproute import IPRoute
  File "/usr/local/lib/python2.7/site-packages/pyroute2/iproute.py", line 109, in <module>
    from pyroute2.netlink.rtnl.tcmsg import get_htb_parameters
  File "/usr/local/lib/python2.7/site-packages/pyroute2/netlink/rtnl/tcmsg.py", line 29, in <module>
    _psched = open('/proc/net/psched', 'r')
IOError: [Errno 2] No such file or directory: '/proc/net/psched'

Thanks. I don't think ipdb works at all on OSX as its meant for Linux only. Will make the appropriate changes tomorrow

Same problem with FreeBSD
catbref [15:15]
File "/usr/local/lib/python2.7/site-packages/pyroute2/netlink/rtnl/tcmsg.py", line 29, in
_psched = open('/proc/net/psched', 'r')
IOError: [Errno 2] No such file or directory: '/proc/net/psched'
[15:16]
so basically same issue
Possible solution
f483 We should report it ipstream if not already done

I have the same problem with my debian nas.

version 0.5.8 is working. 0.5.9-0.6.1 are not working.
pip install pyp2p==0.5.8

Fixed with pyp2p 0.6.4. Retest with my debian nas passed.


How do I remove a particular listener after it has been used?

General information

Library version: 5.x
Browser and OS: Chrome 92.0

Issue description
How do I remove a particular listener after it has been used?
My listener has done its job and sent the data via callback.

In order to remove a particular listener, you would use the off method:
bus.off("event-name", handler);


Properly compute SymbolFlags.Optional for intersected properties

With this PR, we ignore properties originating in non-property declarations (such as exported members of modules or the members of globalThis) for purposes of computing SymbolFlags.Optional for intersected properties. Non-property declarations can't specify optionality and therefore shouldn't affect the outcome.
Fixes #50954.

@typescript-bot test this
@typescript-bot user test this inline
@typescript-bot run dt
@typescript-bot test top100

@typescript-bot test this
@typescript-bot user test this inline
@typescript-bot run dt
@typescript-bot test top100

@ahejlsberg if needed - i can change the code in XState (im actually its maintainer). But the reported error looks dubious for me - this should be assignable, right?

@Andarist Yeah, those assignments should be permitted. When checking assignability for a property that originates in a non-property declaration, we shouldn't check optionality because there is no way of controlling it.

@typescript-bot test this
@typescript-bot user test this inline
@typescript-bot run dt
@typescript-bot test top100

@typescript-bot perf test this faster

All tests look good and performance is unaffected. This one is ready to merge.


update posts

I'd like a way to update posts.  Use case I have a local markdown file.  I make a mistake and would like to update the post.

Thank you @rmchale for submitting this idea. I'll look into how it can be implemented, as it depends on each platform's API.


:soap: Show only ready providers for source of migration

Issue:
we show all providers as a posible source provider, we should only show providers that makes sense to migrate from.
Fix:
show only "ready" provider
Note:
providers do not support filtering by phase, the filtering is done on the frontend side.

cc: @ahadas
kubectl get providers --field-selector "status.phase=Ready"

will fails because providers do not support filtering by phase, it may be nice to support this filter


[PAIShare] Add more fields to template search API.

Coverage increased (+19.9%) to 71.155% when pulling ed23f0a93871a464af165327ca7088de76944494 on shaocs-paishare into b4844994fd7714e2ca8c805deb799d5e5c1310cd on paishare.

Coverage increased (+19.9%) to 71.155% when pulling ed23f0a93871a464af165327ca7088de76944494 on shaocs-paishare into b4844994fd7714e2ca8c805deb799d5e5c1310cd on paishare.

Coverage increased (+19.9%) to 71.155% when pulling ed23f0a93871a464af165327ca7088de76944494 on shaocs-paishare into b4844994fd7714e2ca8c805deb799d5e5c1310cd on paishare.


[$250] Clicking " Please sign in again" does nothing in "Session Expired" page

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

Version Number:
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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
Expensify/Expensify Issue URL:
Issue reported by:  @carlosmiceli
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1729880182560339
Action Performed:

Have a " Your Session has Expired"  screen
Click on "Please sign in again"

Expected Result:
User is taken to sign in screen
Actual Result:
Nothing happens
Workaround:
unknown
Platforms:

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

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
![Screenshot 2024-10-25 at 3 14 04 PM](https://github.com/user-attachments/assets/a0962256-b82f-4024-b3e0-13dc97578294)

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021851043610237148822
Upwork Job ID:<PHONE_NUMBER>237148822
Last Price Increase: 2024-10-28

Issue OwnerCurrent Issue Owner: @aimane-chnaif

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

I am not able to recreate, so going to see if the C+ can recreate based on the SO linked above

@aimane-chnaif — can you attempt to recreate please 🙏 Thank you!

Proposal
The Navigation.navigate() method should be invoked within the callback of isNavigationReady() as shown below:
Navigation.isNavigationReady().then(() => {
    Navigation.navigate();
});

This ensures that navigation only occurs once the navigation container is fully prepared and ready to handle navigation actions.
Reference: https://github.com/Expensify/App/blob/db592c9c9f56a6ce8208b898c1e5ba1eb864aae8/src/pages/ErrorPage/SessionExpiredPage.tsx#L35C1-L39C34

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

@NJ-2020's proposal makes sense to me.
I see that Navigation.navigate(ROUTES.SIGN_IN_MODAL); is optional - why should we or shouldn't we use this in additional to goBack()?

I like the idea of explicitly calling Navigation.navigate(ROUTES.SIGN_IN_MODAL); since it's more obvious that we are redirecting to the sign in page.
But we can iron this out in the PR.
cc: @aimane-chnaif

Payment Summary
@NJ-2020 — paid $250 via Upwork
@aimane-chnaif — paid $250 via Upwork
Regression Test
https://github.com/Expensify/Expensify/issues/443985


DefaultMixedRealityCameraProfile wrong defaults?

Describe the bug
DefaultMixedRealityCameraProfile  has the following defaults:

Clear Flags: Skybox

However, the recommendations from MRTK is: Solid Color

But it gets overriden by these defaults settings when you to so!
To reproduce

Setup a new project according to https://learn.microsoft.com/en-us/windows/mixed-reality/develop/unity/new-openxr-project-with-mrtk

On the menu bar, click on Mixed Reality > Project > Apply recommended project settings for HoloLens 2, click on Edit

Check that settings are in fact like recommended:

Press the "Play" Button to start the scene. Changes from 2. will be reseted to Skybox. Doing Step 2. will again show the same issue

Expected behavior
Settings in default are equal to Mixed Reality > Project > Apply recommended project settings for HoloLens 2
Your setup (please complete the following information)

Unity Version 2020.3.37f1
MRTK Version 2.82

Target platform (please complete the following information)

HoloLens 2

Additional context
Most likely related to that file: https://github.com/microsoft/MixedRealityToolkit-Unity/blame/80a0bb7a3928101fb5c8c0f4821f2bc92ee2aa34/Assets/MRTK/Core/Definitions/CameraSystem/MixedRealityCameraProfile.cs#L55
Workaround
Clone Default profile and override settings:
(However, only color can be selected, it is not possible to select solid color, may be an other bug?)

We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visithttps://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!


"deleted_by" not properly set when BlameableTrait is inherited

When SoftDeletes is defined in a parent class, the BlameableTrait->useSoftDeletes() cannot detect the SoftDeletes trait in the children classes. Laravel has some built-in functionality that addresses this by using class_uses_recursive function to detect trait usage up the inheritance tree. I'm working on the pull request now to fix this issue.

Hi @juventus18, thanks for pointing this. It is a confirmed bug and thanks for the PR. I'll merge it as soon as possible.

A new tag has been released: 1.4.1
Feel free to update the package version.


Heroku ActionView::Template::Error (s3_upload.js isn't precompiled)

I am currently trying to use this plugin on a Heroku Rails 3.1.3 application.
I have this in my gemfile.
gem 's3_swf_upload', :git => 'git://github.com/nathancolgate/s3-swf-upload-plugin'
gem 'aws-s3', :require => 'aws/s3'
I bundled the gem into my application, generated the rails code, created a new controller and view, and added the following to the view.
<%=raw s3_swf_upload_tag %>
<input type="submit" value="Start Uploading" onclick="s3_swf_1_object.startUploading();" />

I have added, committed and pushed all files to the heroku master. I am getting the following error.
2011-12-27T17:53:14+00:00 app[web.1]: Completed 500 Internal Server Error in 129ms
2011-12-27T17:53:14+00:00 app[web.1]:
2011-12-27T17:53:14+00:00 app[web.1]: ActionView::Template::Error (s3_upload.js isn't precompiled):
2011-12-27T17:53:14+00:00 app[web.1]:     1:

2011-12-27T17:53:14+00:00 app[web.1]:     2:
Uploader

2011-12-27T17:53:14+00:00 app[web.1]:     4:    <input type="submit" value="Start Uploading" onclick="s3_swf_1_object.startUploading();" />
2011-12-27T17:53:14+00:00 app[web.1]:     3:    <%=raw s3_swf_upload_tag %>
2011-12-27T17:53:14+00:00 app[web.1]:     5:

2011-12-27T17:53:14+00:00 app[web.1]:   app/views/pages/home.html.erb : 3 : in `_app_views_pages_home_html_erb___2628368205308588842_20282460'
I have also tried running the following.
bundle exec rake assets:precompile

In rails > 3.1 you will probably want to put the JavaScript file in the assets/javascripts folder instead of the default public/javascripts folder.

I moved s3_upload.js from public/javascripts to app/assets/javascripts however I am still seeing the same error. I have tried to rerun bundle exec rake assets:precompile.
I am still playing with it trying to understand but any help would be appreciated.

I figured it out, for anyone having this issue you must change config.assets.compile to true in config/environments/production.rb.
config.assets.compile = true

Wow... config.assets.precompile just saved my life! Thanks for that :-)


Precompiled letter sanitising - notify tag and address block checking

Adds a new /precompiled/sanitise endpoint.
Accepts: A base64 encoded PDF file (todo: do we want to change this? This should probably just be a raw file)
Returns: A regular pdf file.
What it does:

Identify if notify tag is present

if not, adds a notify tag to the first page

validates the boundaries aren't exceeded

if they are, logs an error. But doesn't return 400, because I suspect most letters we get won't pass this.

Extracts the address from the first page
puts a white block over the address
re-writes the address, in arial 8pt.
returns the new, improved, all-singing all-dancing PDF.

Suggestions on how to refactor precompiled.py so that it doesn't start with a bazillion random variables are welcome

to test (from API):
import requests
resp = requests.post(
    'http://localhost:6013/precompiled/sanitise',
    data=base64_encoded_pdf,
    headers={'Authorization': 'Token my-secret-key'}
)
resp.raise_for_status()
with open('output.pdf'), 'wb') as f:
    for chunk in resp.iter_content(chunk_size=128):
        f.write(chunk)


Updated almvm download links

Why am I on this thread?
On Fri, Feb 2, 2018 at 3:39 PM, Sachin Raj<EMAIL_ADDRESS>wrote:

Merged #66 https://github.com/Microsoft/almvm/pull/66.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/almvm/pull/66#event-1456103564, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAtRrP4F6FXgGq6Cte6NZWwldk2i-9JOks5tQ5zMgaJpZM4R36_a
.


New filter-event in PriceCalculationService.

Puts the price through a filter-event to let subscribers alter it.

Description

Questions
Answers

Why?
With the PriceCalculationService we have a central place for all price-calculations in the system (except the basket). It would make sense to give plugins the ability to alter the prices there.

BC breaks?
no

Tests exists & pass?
not yet

Related tickets?
Not that I know of any.

How to test?
Use the new event in a plugin and alter the price there.

Requirements met?
yes

You could also decorate the service, for that reason shopware build for any service a interface

That is correct. But I fail to see a way to keep most of the logic intact if you want to alter the price at that point. I built myself a workaround that consists of a decorator, but due it being private I cannot simply override the calculatePrice()-method. If I am missing out on some features a decorator could provide, please let me know.

Hey @jkrzefski,
thanks for your contribution. Please extract the function into a new Service (with interface) instead of throwing an event over the shopware singleton.

We are closing this PR due to inactivity.
For more information about our contribution guidelines, see https://developers.shopware.com/contributing/contribution-guideline/.


Remove sidebar panes when signed out

Fixes getappmap/board#272

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

v0.91.1
GitHub release

Your semantic-release bot :package::rocket:


⚠ Bofrost.at has degraded performance

In 0d5191f, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 924 ms

Resolved: Bofrost.at performance has improved in c171600 after 13 minutes.


Model being populated with incorrect columns.

Given the model objects:
type provider struct {
	gorm.Model
	UserID   uint   `sql:"index"`
	Name     string `json:"name"`
	UniqueID string `json:"unique_id"`
}

type user struct {
	gorm.Model
	Name      string `json:"name"`
	Email     string `json:"email"`
	AvatarURL string `json:"avatar_url"`

	// internal
	Providers []provider `json:"-"`
	Token     string     `json:"-"`
}

gorm generated:
                                    Table "public.users"
   Column   |           Type           |                     Modifiers
------------+--------------------------+----------------------------------------------------
 id         | integer                  | not null default nextval('users_id_seq'::regclass)
 created_at | timestamp with time zone |
 updated_at | timestamp with time zone |
 deleted_at | timestamp with time zone |
 name       | character varying(255)   |
 email      | character varying(255)   |
 avatar_url | character varying(255)   |
 token      | character varying(255)   |
Indexes:
    "users_pkey" PRIMARY KEY, btree (id)

                                    Table "public.providers"
   Column   |           Type           |                       Modifiers
------------+--------------------------+--------------------------------------------------------
 id         | integer                  | not null default nextval('providers_id_seq'::regclass)
 created_at | timestamp with time zone |
 updated_at | timestamp with time zone |
 deleted_at | timestamp with time zone |
 user_id    | integer                  |
 name       | character varying(255)   |
 unique_id  | character varying(255)   |
Indexes:
    "providers_pkey" PRIMARY KEY, btree (id)
    "idx_providers_user_id" btree (user_id)

When running this code:
func loadUserForProvider(name, id string) *user {
	var u user
	if err := db.Debug().Preload("Providers").
		Joins("inner join providers on providers.user_id = users.id").
		Where("providers.name = ? and providers.unique_id = ?", name, id).
		Find(&u).Error; err != nil {
		return nil
	}
	return &u
}

The following queries are produced:
SELECT  * FROM "users" inner join providers on providers.user_id = users.id WHERE ("users".deleted_at IS NULL OR "users".deleted_at <= '0001-01-02') AND ((providers.name = 'gplus' and providers.unique_id = 'gplus'))

SELECT  * FROM "providers"  WHERE ("providers".deleted_at IS NULL OR "providers".deleted_at <= '0001-01-02') AND (("user_id" IN ('3')))

The queries are correct, and returned the joined data as appropriate. However, at this point, the u object contains incorrect data. u.ID should be 1, but it is 3 (the ID of the provider). u.Name should contain Tyler, but it contains gplus (the name of the provider).
I am assuming this is because the id and name columns are the same name for both tables, but in the example README, both the email and user objects have an ID. The join code I am using is based on the join code for finding a user by email.
Am I doing something wrong? Or is this a bug?
Thanks!
-Tyler

Hi @tylerb
Thank you for your report, this should been fixed.


Props updated on table-column does not updating table component

When binding data on table-column, table would not be updated as data is updating.
Here is a simple demo.
https://jsfiddle.net/p0fe9s06/5/
I have done some research and found Evan You(@yyx990803)  has mention in https://github.com/vuejs/vue/issues/4332

It seems you are trying to make a slot container communicate with a slot child - in most cases this means the two components are coupled by-design, so you can do something like this.$parent.$emit(...) from the child, and listen to that event in the parent with this.$on(...).

So I try to add watch in the TableColumn
watch: {
    show() {
        this.$parent.$emit('columnUpdate');
    },
    label() {
        this.$parent.$emit('columnUpdate');
    },
    headerClass() {
        this.$parent.$emit('columnUpdate');
    },
    cellClass() {
        this.$parent.$emit('columnUpdate');
    },
    hidden() {
        this.$parent.$emit('columnUpdate');
    },
    filterable() {
        this.$parent.$emit('columnUpdate');
    },
...

and this in the TableComponent
async mounted() {
    this.columns = this.$slots.default
        .filter(column => column.componentInstance)
        .map(column => new Column(column.componentInstance));

    await this.mapDataToRows();

+   this.$on('columnUpdate', () => {
+       this.columns = this.$slots.default
+           .filter(column => column.componentInstance)
+           .map(column => new Column(column.componentInstance));
+
+       this.mapDataToRows();
+   });
},

Although it works fine, but it's not seems like an elegant approch.
Does anybody have a clue about this?

I think this is gonna be a necessary evil for the way this package is set up. I'll look into adding this later this week.
The first snippet won't need to be that verbose though, you can pass an array to the $watch method.
created() {
    this.$watch(['show', 'label', ...], () => {
        this.$parent.$emit('columnUpdate');
    });
},

Wow, thanks for the snippet. I don't know that this.$watch can pass in array.
I was thinking the columns can be somehow updated one by one instead of all columns, but since any props might be changed, it's difficlut to tracks which column has changed.
The column might even been removed from or inserted into the table. so what really necessary is watching the changes of the $slots, but it seems there is no other way to do this :(
I'm looking forward to the future update. Cheers, bro!

First of all, sorry I lied 😅 I really thought I passed an array to $watch before, but apparently it's not a feature after all 😞 (see vuejs/vue#844)
Imo it's easier to just use a single change event. I see swapping columns as an edge case, so I don't think we should be optimizing too hard at this stage.
I just released 1.4.3 which contains your proposed fix. I structurd it a bit different than you proposed, everything's defined on the parent component, and I'm looping over the properties so we never miss anything.
Here's the commit: https://github.com/spatie/vue-table-component/commit/3c9aee85f0db7adb582d724e104bb8de896d1a9e

My apologies for late comment, I found 2 issues on this commit 3c9aee8
columnComponents.forEach(column => {
    Object.keys(this.$options.props).forEach(
         prop => this.$watch(prop, () => this.mapColumns())
    );
});

this in this.$options.props, this.$watch, this.mapColumns() are actually point to TableComponent when using arrow function, so this snippet is in fact watch TableComponent's props instead of TableColumn.

It will bind watch function multiple times since mapColumns() is calling itself(recursive), the browser will hangs if the prop changes frequently(I tried).

The mysterious thing is although it is watching incorrect props but it still works!
I performed some experiments and found out it only needs to watch data.
    async mounted() {
        this.mapColumns();

        await this.mapDataToRows();
+       this.$watch('data', () => this.mapColumns());
    },

    mapColumns() {
        const columnComponents = this.$slots.default.filter(
            column => column.componentInstance
        );

        this.columns = columnComponents.map(
            column => new Column(column.componentInstance)
        );

-       columnComponents.forEach(column => {
-           Object.keys(this.$options.props).forEach(
-                prop => this.$watch(prop, () => this.mapColumns())
-           );
-       });
    },

Well, I don't understand but it just works.
One more thing.
It needs to warp with setTimeout if adding mapColumns() into watch, I don't get this as well.
watch: {
    data() {
+       // this.mapColumns(); // don't works
+       setTimeout(() => this.mapColumns(), 0);
+
            if (this.usesLocalData) {
            this.mapDataToRows();
        }
    },
},

(Confused Jackie Chan face)

You're right about watching those props, and I also have no idea why they work now 😄
I'll look into this issue again later this week :)

Hey, is there any progress of this issue?
I had submit a PR #52 for this, it will be very appreciated if you could spend some time for it.
Great thanks.

Hi! Was on holiday so a bit later on this one :)
Looks good to me, merged and tagged a fresh 1.6.1 release!


Deprecated packages in the repo, needs updating

npm WARN deprecated<EMAIL_ADDRESS>ng2-bootstrap was renamed to ngx-bootstrap, please update your dependencies
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated<EMAIL_ADDRESS>Use mz or fs-extra^3.0 with Promise Support
npm WARN deprecated<EMAIL_ADDRESS>this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated<EMAIL_ADDRESS>All features were merged back into original parse-github-repo-url
npm WARN deprecated<EMAIL_ADDRESS>Please update conventional-changelog to >1.0.0. If you are running the cli, use conventional-changelog-cli
npm WARN deprecated<EMAIL_ADDRESS>Use uuid module instead

I agree that we should keep the dependencies updated but most of these are probably  transitive deps so you need to provide more information which package needs to be updated (sometimes it might not be possible)
This will show you how minimatch got into fabric8-planner
npm ls minimatch


🐛 BUG: wrangler init tells you to use cloudflare@2 (instead of cloudflare@latest)

Which Cloudflare product(s) does this pertain to?
Wrangler core
What version(s) of the tool(s) are you using?
Wrangler 3.7.0
What version of Node are you using?
No response
What operating system are you using?
Mac
Describe the Bug
mockassignment git:(main) ✗ wrangler init
⛅ wrangler 3.7.0
Using npm as package manager.
▲ [WARNING] The init command is no longer supported. Please use npm create cloudflare@2 instead.
The init command will be removed in a future version.
Running npm create<EMAIL_ADDRESS>Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
No response

After discussing with the team we decided that we don't want to pull the latest version of create cloudflare to keep major versions in sync. However we do want to pull the latest minor version. Based on @jculvey's comment here this functionality should exist once the associated PR has been merged.


Regression: callouts render as regular block quotes

Describe the bug
Obsidian callouts render as regular block quotes after the upgrade to Perite 1.5. This is a regression issue since the feature was being introduced in #26 (original feature request).
To Reproduce

Go to https://perlite.secure77.de/?link=%2FDemo%20Documents%2Fmarkdown-sample3
Observe regular block quote styling rather than callout formatting

Expected behavior

Callouts render at least with accent color depending on their type
Optional: Callouts render with their dedicated icon
Optional: Callouts can be folded

Desktop (please complete the following information):

OS: Linux
Browser: Firefox 106.0.2 (64-bit)

Looking at the css, the function still works but it's not defined in the css. With a proper css theme it should look correct.

Unfortunately it is not so easy to rebuild the div structure we need to match with obsidian themes.
@Tooa if you have some time I would appreciate your help for extending the parsedown function

I have created an issue on parsedown, hopfully find some help there:
https://github.com/erusev/parsedown/issues/843

finally figured out how to support this, was a lot of work and I need to overwrite several default functions of parsedown to support nested elements in blocks but now it should work as expected.

will be in the next 1.5.1 release


jvm crashed after concat operation

here is log
hs_err_pid31141.log
I wonder what operations of concat contribute to the crash

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J 16093  org.nd4j.nativeblas.Nd4jCpu$NativeOps.concatFloat(Lorg/bytedeco/javacpp/PointerPointer;IILorg/bytedeco/javacpp/PointerPointer;Lorg/bytedeco/javacpp/PointerPointer;Lorg/bytedeco/javacpp/FloatPointer;Lorg/bytedeco/javacpp/IntPointer;Lorg/bytedeco/javacpp/PointerPointer;Lorg/bytedeco/javacpp/PointerPointer;)V (0 bytes) @ 0x00002b479a0c4d93 [0x00002b479a0c4cc0+0xd3]
J 19627 C2 org.nd4j.linalg.cpu.nativecpu.CpuNDArrayFactory.concat(I[Lorg/nd4j/linalg/api/ndarray/INDArray;)Lorg/nd4j/linalg/api/ndarray/INDArray; (672 bytes) @ 0x00002b479c348d58 [0x00002b479c3482a0+0xab8]
J 16954 C2 com.dp.arts.rerank.model.task.ModelPredictTask.run()V (576 bytes) @ 0x00002b479b53599c [0x00002b479b534e00+0xb9c]
J 20374 C2 com.dp.arts.rerank.model.task.ModelPredictTask.call()Ljava/lang/Object; (5 bytes) @ 0x00002b479814d734 [0x00002b479814d700+0x34]
J 26386 C2 java.util.concurrent.FutureTask.run()V (126 bytes) @ 0x00002b479af38050 [0x00002b479af37fa0+0xb0]
J 10722 C1 java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurrent/ThreadPoolExecutor$Worker;)V (225 bytes) @ 0x00002b4799769384 [0x00002b4799768360+0x1024]
J 13507 C1 java.util.concurrent.ThreadPoolExecutor$Worker.run()V (9 bytes) @ 0x00002b4799d6cf04 [0x00002b4799d6ce00+0x104]
J 12307 C1 java.lang.Thread.run()V (17 bytes) @ 0x00002b479a241bc4 [0x00002b479a241a80+0x144]
v  ~StubRoutines::call_stub
here is log

Can you post the code that resulted in this crash? Or even better, can you create a minimal example that results in the problem?

Yes please. Crash log on it's own doesn't tell us too much

The code is too complex to show. It's a part of our online environment
what may be the reasons for this crash? the log shows 'concat' resulted in the crash..

@Sirius081 if you can't give us any information, I have to treat this as irrelevant. Only re open this if you can actually help us reproduce it.

@Sirius081 Given just your crash log I can only tell you that you are probably running something in a threaded environment that isn't thread safe:

J 16954 C2 com.dp.arts.rerank.model.task.ModelPredictTask.run()V (576 bytes) @ 0x00002b479b53599c [0x00002b479b534e00+0xb9c]
J 20374 C2 com.dp.arts.rerank.model.task.ModelPredictTask.call()Ljava/lang/Object; (5 bytes) @ 0x00002b479814d734 [0x00002b479814d700+0x34]
J 26386 C2 java.util.concurrent.FutureTask.run()V (126 bytes) @ 0x00002b479af38050 [0x00002b479af37fa0+0xb0]
J 10722 C1 java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurrent/ThreadPoolExecutor$Worker;)V (225 bytes) @ 0x00002b4799769384 [0x00002b4799768360+0x1024]

So without any more information on what exactly you are doing, you are on your own there.

public INDArray getBatchFeatures(RerankContext rerankContext, int segmentID, List<Integer> instanceIds, ArrayList<String> feaList, boolean useEmbedding) {         INDArray features = getFeatures(rerankContext, segmentID, instanceIds, feaList);         if (useEmbedding) {             INDArray embeddings = getEmbeddings(rerankContext, segmentID, instanceIds);             features = Nd4j.concat(1, embeddings, features);         }
private INDArray getFeatures(RerankContext rerankContext, int segmentID, List<Integer> instanceIds, ArrayList<String> feaList) {         int batchSize = instanceIds.size();         double[][] featureMatrix = new double[batchSize][feaList.size()];        //delete code which assigns value to featureMatrix. The code is about our business         INDArray features = Nd4j.create(featureMatrix);         features.subiRowVector(gapmin).diviRowVector(gap);         return features;     }
public INDArray getEmbeddings(RerankContext rerankContext, int segmentId, List<Integer> instanceIds) {         int batchSize = instanceIds.size();         FeatureData featureData = rerankContext.getFeatureDataFromMap(segmentId);         INDArray embeddings = Nd4j.zeros(batchSize, embTotalDim);        //delete code which assigns value to featureMatrix. The code is about our business         return embeddings;     }
one thing may help is that the physical memory is almost exhausted

I've also had problems with concat in a threaded environment see #536
I ended up implementing my own dumb version of concat in java as I could not reliable reproduce the issue and running valgrind was too slow to ever trigger the fault.
I get that nd4j is not thread safe. but problem is that I have no idea which ops in nd4j that are not thread safe. I have very long running Java applications running in a threaded environment using Nd4j, so to some extent it must be thread safe. Or at least, parts of nd4j must be thread safe.
Right now I'm experiencing similar issues with pullRows and I almost can't be bothered to figure out how to call that method safely.

@emillynge If you could come up with a code snippet (that creates 1000 threads if you need) to reproduce your issue, it would also help a lot.

@saudet If I can reproduce the problem with pullRows I will file a separate issue.
But the issue is very rare ~ occurs once in 5-10 hours of running my application.
But as said, I simply revert to implementing similar functionality in pure java (which is calling Pointer.memcpy directly :confused: ) As my experience tells me I will end up spending lots of time reproducing the bug to no avail.


Out of source proto building

For now protobuf files are generated in schema folder, where the source *.proto files are located. I don't think it is really a good idea. E.g if I'd like to build in docker (after local build), there comes up a errors:
error: #error This file was generated by a newer version of protoc which is
 #error This file was generated by a newer version of protoc which is
  ^
/opt/iroha/schema/block.pb.h:13:2: error: #error incompatible with your Protocol Buffer headers. Please update
 #error incompatible with your Protocol Buffer headers.  Please update
  ^
/opt/iroha/schema/block.pb.h:14:2: error: #error your headers.
 #error your headers.

The issue seems pretty simple, but maybe I'm missing somethig or there's a reason why is it done that way

out directory for sources should be ${CMAKE_CURRENT_BINARY_DIR}, also compile methods in cmake should have OUT variable, which is set inside compile to a list of paths to sources.
this will resolve this issue

Done in #1550


Removed useless commas

@UnSimpleGeek Thanks a lot for the PR. Actually, those commas are there because of this ESLint rule: https://eslint.org/docs/rules/comma-dangle

@quanglam2807 Thanks for your answer, I removed it because of this error message while doing npm start :
A JavaScript error occurred in the main process Uncaught Exception: /home/thomas/Documents/Dev/Electron/Simpleflix/node_modules/electron-widevinecdm/src/index.js:62             ),             ^ SyntaxError: Unexpected token )     at Object.exports.runInThisContext (vm.js:78:16)     at Module._compile (module.js:543:28)     at Object.Module._extensions..js (module.js:580:10)     at Module.load (module.js:488:32)     at tryModuleLoad (module.js:447:12)     at Function.Module._load (module.js:439:3)     at Module.require (module.js:498:17)     at require (internal/module.js:20:19)     at Object.<anonymous> (/home/thomas/Documents/Dev/Electron/Simpleflix/main.js:5:21)     at Object.<anonymous> (/home/thomas/Documents/Dev/Electron/Simpleflix/main.js:51:3)

@UnSimpleGeek I should be fixed with https://github.com/webcatalog/electron-widevinecdm/releases/tag/v3.2.1

@quanglam2807 Thanks a lot, keep up the good work !


running python manage.py silk_clear_request_log it finishes with 'killed'

Hello guys,
I ran a jmeter script to perform load, after that I tried to clean the log and I got the message:
deleting Profile 0 objects
deleting SQLQuery 201290 objects
killed
The thing is the logs were not deleted right?
could you provide advise please?
Best regards

Hey @ricardodanieltapia sorry for the delay in getting to this. Here is what happens when I execute this command:
$ ./manage.py silk_clear_request_log
deleting Profile 4 objects
deleting SQLQuery 2 objects
deleting Response 2 objects
deleting Request 2 objects

This successfully clears the database for me. Where is killed coming from in your output? I'm not familiar with jmeter but it looks like the script is being killed prior to completion?

@ricardodanieltapia This would appear that some other parameters are missing in order to fulling understand what is happening with this issue? Could it be possible that another process killed the management command from completion?

Could It be out of memory? You can check with free if your database is out of memory, the process will be killed if that's the case.

Closing this issue. If there is more information about why management command is killed I can possibly investigate.


Stop unnecessary mode fallback due to accumulated optical flow drift

For discussion/comment
When the estimator is using optical flow as the only aiding source, the uncertainty in the position relative to the starting point will increase over time. At some point this will cause the position validity check to fail. This is unnecessary if operating in POSCTRL because the operator will be correcting for the drift throughout the flight.
We may want to extend this check exemption  to include other flight modes.
Relates to https://github.com/PX4/Firmware/issues/9398
Compatible with https://github.com/PX4/ecl/pull/442

@mhkabir @ChristophTobler  FYI

Thanks! I'll test this in flight soon.

Won't this miss actual failures? Stale data or the local position message reporting invalid. Reading from my phone, I might be overlooking something.

What if you set the eph threshold to infinity for position control mode? Wouldn't that capture everything without even having to check the specific estimator bits?

Won't this miss actual failures? Stale data or the local position message reporting invalid. Reading from my phone, I might be overlooking something.

Yes, I think you're right. We need a better way to achieve what this does.

What if you set the eph threshold to infinity for position control mode? Wouldn't that capture everything without even having to check the specific estimator bits?

This would not work for GPS-enabled mode, since the operator may not be compensating for drift in case GPS suddenly goes wonky. I think we need a way for the state machine architecture to make informed decision based on what estimation modality the vehicle is currently using, but preferably without directly using the estimator status flags.

The check of published position uncertainty should only be inhibited when the vehicle is solely reliant on optical flow and only in a mode where the operator has stick control. Velocity error growth should still be checked.
The scenario of GPs going wonky does not apply here because the estimator would not be using GPS.
local_position.v_xy_valid and reported accuracy is still being checked so actual estimator failures in this mode would still be caught.
Agree that a less estimator version specific way of achieving this is required.

@ChristophTobler I've added the bit position definitions to the estimator_status message and used them in the code.

@ChristophTobler I'm not sure if changing those definitions to 8 bit has saved anything. In the end we are doing a bit and with a 32 bit mask, eg control_mode & (1 << estimator_status_s::CS_GPS) so doesnt it end up casting  (1 << estimator_status_s::CS_GPS) to a 32 bit integer to do the bit and ?

With the latest changes, is it still recommended to fly with range aid enabled?
How does the terrain following behaviour change when we switch to GPS aiding from flow-only aiding?

I've updated the parameter descriptions to make the intended use clearer.

I've been unable to test this today due to problems getting the hardware setup working in indoor conditions (weather is preventing outside testing). The PX4Flow sensor does not seem to work with the LED lighting.

This commit unifies the flow height limiting : https://github.com/PX4/Firmware/commit/ec16c561853f3b2951b1124df3e7077e033ef091. I wanted to make more changes, but they can come afterwards when we refactor the whole thing. I do not want to block this PR.
I also removed the condition to automatically go into terrain following mode if reliant on optical flow. I think it is more prudent to explicitly set MPC_ALT_MODE to 1 to enable terrain following.
In general, after going through the whole navigation and controller limits architecture, I found that it is pretty hacky. After this PR, I plan to refactor it as a first step towards generalising the controller limiting system. e.g for VIO and rangefinder.
General observations :

Estimator should publish all controller limits (vx_max, vy_max, vz_max, hagl_min, hagl_max)
based on sensing sources used. The controller should not have to read them off sensor params, and should generalise without caring what the actual sensor is.
Controllers should apply navigation limits independent of manual/auto modes. It should work in missions as well.
Controller currently does not correctly handle normal altitude limiting in terrain following mode. The terrain following generally needs a refactor and testing for edge cases.

It is not a good idea to fly reliant on optical flow without terrain following and height limiting. If the vehicle flies too high, navigation and position control will be lost. Using terrain following in this situation is safer.

I'm not a big fan of terrain following because it's usually not what the user expects. But we can have the height limitations without terrain following, right?

We could try that and see what the user experience is like. It would require enabling the height limiter and using a dynamic height limit, where height_limit = max_flow_height + local_position.z + local_position.dist_bottom

I agree with Christoph. I'll implement the dynamic height limit and get the controller limiting system to work for both terrain following and altitude following modes.

@mhkabir Have you made any progress? I have something from another project I can bring across. I also wanted to add a feature so that mc_pos_control can control to lpos.dist_bottom when hovering and control to lpos.z when moving (with hysteresis on the speed threshold). I don't to add this until the dynamic height limiting is in.

@priseborough Yep. Here it is : https://github.com/PX4/Firmware/commits/pr-optFlowFixes
ECL branch : https://github.com/PX4/ecl/pull/448
I don't have an opportunity to test for a few days, so if you could have a look, it'd be great!

Going through this again I'm now thinking this should be handled by the state machine.
I'd like to add a new flag in vehicle_status_flags for the optical flow dependency, then in the state machine for position control mode add the logic that will optionally ignore condition_global_position_valid if dependant on optical flow.
If there's no objection I can make this change unless someone else wants to.

@dagar that sounds good actually! Can you work off my pr-optFlowFixes (linked above), which is this branch + some more work on top. Feel free to clean things up in my changes if you find anything.

@priseborough @ChristophTobler This should be good for testing now : https://github.com/PX4/Firmware/compare/pr-optFlowFixes
I implemented the dynamic limiting, and tested a bit in SITL. Some more SITL testing + outdoor testing TBD.
@PX4/testflights Do you guys have a vehicle with optical flow + GPS?

SITL with optical flow in the uneven_ground world seems to slow down Gazebo to the point where the vehicle just freezes on hard pitching (on master). I recommend testing with the asphalt_plane world for now because it seems to work correctly.

@mhkabir please use a different name for your branch. You should be able to raise your changes as a PR against this branch or as reviewer push them. I will review them today.

@mhkabir
"On uneven ground, the altitude limit goes up when the vehicle is over higher ground, and this can cause fast upward jumps."
Is this with the throttle stick raised so it is attempting to climb against the limit?

Superseded by https://github.com/PX4/Firmware/pull/9509


feat(docs): upgrade mkdocs/mermaid

This PR is to upgrade mkdocs-material and mermaid2 to later versions.
I also include mermaid.min.js (10.8.0) because sandboxed environments cannot access CDN to download mermaid.min.js via mkdocs-mermaid2-plugin.

Wait for decision on #99 and more testing

Seems to work fine.
Note: Mermaid dislikes Linkml class names with keywords like "class".  For example, ontology class causes syntax error rendering diagrams, but OntologyClass does not.

Hi @cmungall
I will remove that from this PR and address via https://github.com/linkml/linkml-project-cookiecutter/issues/118

Ready for review.

Examples for sample "void" schema
Dark mode (Dracula):

Normal mode:


popovers: Fix selected message being changed on scroll inside popover.

Since scroll event is always fired at root level, we don't have control over capturing the event and containing it to the popover if scroll happened inside the popover.
This can lead to unintentional moving of selected message since we try to move the selected message to rendered top / bottom if we receive a scroll event when top / bottom ends are rendered.
discussion: https://chat.zulip.org/#narrow/stream/9-issues/topic/scrolling.20emoji.20picker.2C.20changes.20focused.20message
I tested by narrowing to a topic with 2 messages and opening emoji popover. We correctly don't move the selected message.
When the end of the message list is rendered and last message is not selected; if you open emoji popover and scroll, we don't move the selected message now, I don't see this as a regression but not sure we can do better.

Yeah, this seems OK, we can refine if someone finds the updated behavior annoying, merged, thanks @amanagr!


IOS build fails

Each time I try to build the app with this module installed I get the following error

Ahh ok the reason it fails was because my .env files have values that were in double quotes e.g.
MY_URL="https://thing.domain.com"
Where as it only works without the double quotes.
I'd guess some parsing of the .env contents is required.
I think that the fact that the DOT_ENV var is being generated by Ruby to make it available to the ReactNativeConfig.m is the reason the error manifests as a syntax error in the build phase.

I had this exact same error. Moving from "key" to 'key' also solved the issue for me.

Latest version should work well with single or double quotes! Thanks folks :+1:


can we use newton-m1 in Apollo?

We have gps newton-m1, can we use it in apollo without modify apollo source code and just change configuration files?

@oska874 thanks for using Apollo. We don't support newton-m1 at this time. If there's any update on that, we'll keep everyone updated. This ticket is being closed and please feel free to open new issues if needed.


Warning on initialization after Chrome 106 update

Version

Phaser Version: 3.55.2
Operating system: Windows 10
Browser: Chrome 106.0.5249.62 (Official Build) (64-bit)

Description
Chrome shows the following warning on initialization:

Canvas2D: Multiple readback operations using getImageData are faster with the willReadFrequently attribute set to true. See: https://html.spec.whatwg.org/multipage/canvas.html#concept-canvas-will-read-frequently

Example Test Code
Just including phaser triggers this on init()
Is reproducible in any example.
Additional Information

Yes, this is already fixed in 3.60. However, Chrome isn't smart enough to remove both warnings, just the first one, even though we added the required attribute to both canvas elements we create in the Device class.


Optimizer and dashboard uses different units for workload

Optimizer: requests/minute
Dashboard: requests/second
The dashboard should change the property in the json before sending to the aam writer.

Thanks for raising the issue. Currently I have both methods implemented because we have already changed among these options along the project.
So, I can deal with this issue easily.
Let me know which one the dashboard is collecting and I will use the correct method for this case.

For me, it is a presentation issue. Let @adriannieto answer the current unit.

OK

I will change the text to have an unified unit spec across aamwriter/optimizer

@adriannieto : aamwriter uses req_per_min for workload. Could you translate the value to req/min? Thanks

This should be closed, but I can't do it.


Keep Sessions alive for multiple usage of Invoke-RemoteX commands

i.e.

Send-Files ....
Invoke-Remote ....
Invoke-Remote ...

A new commandlet Get-InvokeRemoteSession will be needed, iff it is given, $Credentials will not be used!
Draft usage:
$ses = Get-InvokeRemoteSession $(Get-Credentials)
Send-Files -session $ses ....
Invoke-Remote -session $ses ....

Iff $Credentials is given together with -session, $Credentials will be used.
Another command/cmdlet for cleaning up all open sessions may be required.

Naming Update:

Get-RemoteSession.ps1 will be used to acquire sessions
the default Remove-PSSession may be used to destroy it
Existing Invoke-Remote utilities (Invoke-Remote, Invoke-RemotePester```, ```Send-Files``` etc. will have an extra parameter called ```$Session)


Is there a changelog?

I just run composer update and this updated flight from 1.3.2 to 1.3.5 but I have no idea what has changed and if I have now to make some code changes. Is there a changelog where I could read what these changes are?

Sorry no official changelog, but you can view the descriptions of changes on the tags screen, https://github.com/mikecao/flight/tags

Hi @mikecao
I can see that you bumped to version 1.3.6: https://github.com/mikecao/flight/commit/db2c5c77e147a31c0e1fbb8fd715b9e65d763af3 but latest release is 1.3.5: https://github.com/mikecao/flight/releases
Can you add a new tag/release?


The app@sharepoint principal is not resolving in newly created tenants

Category

[x] Bug

Describe the bug
In the elevated privileges page there is an important tip about adding the app@sharepoint user as a term store administrator if you need app-only write access to the term store (I believe @wobba originally wrote about this in a post a couple of years ago).
Unfortunately we were not able to add the app@sharepoint user to the term store administrators group in a couple of tenants that we created in the past couple of days - that account will not resolve in the old and new term store UI (as shown in the following screenshots)
Old page

New page

It appears this issue is not isolated to the term store, as that user would not resolve in other user management areas (i.e. site collection admin, etc.)
What made this even more confusing was I was able to get the app@sharepoint account to resolve in one of our newly created tenants this afternoon, but that only worked via the old term store UI - the other tenant we created yesterday is still not able to resolve that account.
I also tried adding the full username i:0i.t|00000003-0000-0ff1-ce00-000000000000|app@sharepoint and experienced the same result as trying to simply add app@sharepoint.
Steps to reproduce

Create a new tenant
Go to the term store in the SharePoint admin center (you can try this in both the old and new UI)
Add app@sharepoint to the term store administrators and try to resolve that account (and/or save your change)
See the error saying no match found in the old UI (or no error, but no user resolution in the new UI)

Expected behavior
I expect the app@sharepoint account to resolve, so we can continue to use app only principals to write to the term store.
Environment details (development & target environment)

Your Developer Environment: N/A
Target Environment: SharePoint Online
Framework: N/A
Browser(s): Chrome v84
Tooling: N/A
Additional details: N/A

Additional context
My concern is this app@sharepoint account may be in the process of being removed, which means our app only apps will no longer be able to write to the term store (which would obviously be a significant issue). @VesaJuvonen do you have any insight into what might be happening here?
Thanks for your contribution! Sharing is caring.

Curious, if you create an app catalog, would that help? Seems something might trigger the creation of this system account.

Thanks for suggestion @wobba
I tried that on a new tenant I created today, and the app@sharepoint account does not resolve (in both the old and new term store management pages). I'll try again at different intervals (i.e. 6, 12, 24 hours) to see if the process of creating a tenant app catalog triggers the process of that system account; I'll leave another comment with the results of my test.

Some info in the comments here https://sharepoint.stackexchange.com/questions/168160/what-is-sharepoint-app-principal-shown-in-appprincipals-aspx-and-what-created-it but nothing definitive on how this works.

Thanks for additional suggestion @wobba
I tried creating and registering an app via /_layouts/15/AppRegNew.aspx and /_layouts/15/AppInv.aspx with the following permissions
<AppPermissionRequests AllowAppOnlyPolicy="true"> 	<AppPermissionRequest Scope="http://sharepoint/taxonomy" Right="Write" /> </AppPermissionRequests>
in the root site collection in the tenant and I am still not able to resolve the app@sharepoint account (after waiting 6 hours).
I should note that I created the tenant app catalog using the PnP cmdlet New-PnPTenantSite -Template "APPCATALOG#0" ... so I tried spinning up another tenant and created the tenant app catalog through the admin center UI in case there was something hidden happening behind the scenes when you create the tenant app catalog via the browser - unfortunately (or perhaps fortunately) I ended up with the same results: I cannot resolve the app@sharepoint account in that tenant either (I have waited a number of hours, and created the same app in that tenant as well).
Out of curiosity, what do you experience if you spin up a new tenant https://portal.office.com/Signup?OfferId=B07A1127-DE83-4a6d-9F85-2C104BDAE8B4&dl=ENTERPRISEPACK&ali=1 and try to get the app@sharepoint account to resolve?

I'm not sure this is a developer topic... we're supposed to direct questions like this that are more OOTB to TechCommunity. Might be best to post this question there...

I'll post my follow up. I experienced the same and got it to work like this:

Create a new app with app-only permissions following https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azureacs
Connected to -admin and was able to resolve Get-PnPUser -Identity "i:0i.t|00000003-0000-0ff1-ce00-000000000000|app@sharepoint"
Added i:0i.t|00000003-0000-0ff1-ce00-000000000000|app@sharepoint as a user in term store

Not sure if 2 is needed


responses should be sorted by date

I apparently deleted this in my most recent commit.
https://github.com/codeforamerica/typeseam/commit/d5945c843ebdee92dd06f067211b326a04ee8c80#diff-e6743592af994e5808e88ebe65c9d073L73

Closed with #23


Fixed Audio section in #5956

Description 📜
06.03 EditText with TextWatcher - Added Audio section
Fixed #5956
Type of change 📝

[x] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[x] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Doc#umentation (Content Creation in the form of codes or tutorials)
[x] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[x] Android Dev #(Kotlin)

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Hey @rahulsain , Checkout this PR and if everything is fine , Kindly merge it ............
Thanks


Error on npm run deploy

Describe the bug
A clear and concise description of what the bug is.
TypeError: Cannot read properties of undefined (reading 'map')
  at EnvError (/Users/BelleMorte/Desktop/djblaze/dist/index.js:136:14)
  at Object.<anonymous> (/Users/BelleMorte/Desktop/djblaze/dist/index.js:20:5)
  at Module._compile (node:internal/modules/cjs/loader:1101:14)
  at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
  at Module.load (node:internal/modules/cjs/loader:981:32)
  at Function.Module._load (node:internal/modules/cjs/loader:822:12)
  at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
  at node:internal/main/run_main_module:17:47

To Reproduce
Steps to reproduce the behavior:
I just followed the guide on adding my tokens and ran npm run deploy and ran into the error.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
https://drive.google.com/file/d/1CLHbld55T4eTj97o4ck2ac7M0DznunjC/view?usp=sharing
Details (please complete the following information):

Bot Version: latest
Hosting Provider private host, right now on my laptop

Additional context
Add any other context about the problem here.

You can close this I can't afford to use CapRover

Please provide more details and then reopen this issue. ENV File Contents (not the token!)


Method not found: 'DryIoc.Rules DryIoc.Rules.WithoutFastExpressionCompiler()

Version: 5.2.2
This error occurs when I use the following code.
How can I solve this problem.
new DryIocContainerExtension(new Container(CreateContainerRules())
.WithDependencyInjectionAdapter(services));

What extension are you using?
The exception means that the extension (whatever it is) expects the method WithoutFastExpressionCompiler to be present. But it was removed in DryIoc v5.

I want to combine IServiceCollection to inject, but it has not been successful.
Now, change to this way, but an error will be reported. When I simply use IServiceCollection, it will not work properly.Did I use it wrong?
Error：
System.ArgumentException:“At least one object must implement IComparable.”
error location：
public Repository(DbContext dbContext)
{
_dbContext = dbContext ?? throw new ArgumentNullException(nameof(dbContext));
_dbSet = _dbContext.Set();
}
IOC Code：
containerRegistry.RegisterScoped<DbContext, LidsDbContext>();
var services = new[] { typeof(IRepositoryFactory), typeof(IUnitOfWork), typeof(IUnitOfWork) };
containerRegistry.RegisterMany<UnitOfWork>(services);
//containerRegistry.RegisterScoped<IRepositoryFactory, UnitOfWork>();
//containerRegistry.RegisterScoped<IUnitOfWork, UnitOfWork>();
//containerRegistry.RegisterScoped<IUnitOfWork,UnitOfWork>();
containerRegistry.RegisterScoped(typeof(IRepository<>), typeof(Repository<>));

Do you have any good suggestions？

@lwlivy I don't fully understand the question and what the problem or exception do you have. I would suggest you to ask the question on StackOverflow tagging with dryioc and provide the  complete failing test, so people can understand the context.

@lwlivy You can see DryIoc 5.0.0 — Method not found: WithoutFastExpressionCompiler(). This issue can close. Good luck.

As far as I can understand, Prism is in action here. So, you can simply override the creation of the container rules. I guess it should be in the App.xaml.cs class.
protected override Rules CreateContainerRules()
{
    return Rules.Default.WithConcreteTypeDynamicRegistrations(reuse: Reuse.Transient)
                        .With(Made.Of(FactoryMethod.ConstructorWithResolvableArguments))
                        .WithFuncAndLazyWithoutRegistration()
                        .WithTrackingDisposableTransients()
                        //.WithoutFastExpressionCompiler()
                        .WithFactorySelector(Rules.SelectLastRegisteredFactory());
}


aws_rds_instance use wrong iam url

When trying to create a aws_rds_instance, an error is generated because a wrong iam connection is made:
    ================================================================================
    Error executing action `create` on resource 'aws_rds_instance[stage-rds-instance]'
    ================================================================================

    SocketError
    -----------
    Failed to open TCP connection to iam.us-east-2.amazonaws.com:443 (getaddrinfo: Name or service not known)

Amazon's site says IAM has only one endpoint for IAM: https://iam.amazonaws.com.
AWS Regions and Endpoints

endpoints at aws-sdk-core/endpoints.json for v1, when ussing Ohio region are outdated, updating endpoints.json should be the path to solve this, but I'm afraid v1 of awk-sdk (used by chef-provisioning-aws) is no longer under maintenance.

We've updated to V2 so this should no longer be an issue.


Issue when using tpf = search_result.download(cutout_size=20)

When using the following code.
import lightkurve as lk
search_result = lk.search_tesscut('HAT-P-11', sector=14)
tpf = search_result.download(cutout_size=20)
I get the following error message

IndexError                                Traceback (most recent call last)
~/Desktop/TESS_LK/lightkurve/lightkurve/search.py in _download_one(self, table, quality_bitmask, download_dir, cutout_size)
150                                                 download_dir,
--> 151                                                 cutout_size)
152             except Exception as exc:
~/Desktop/TESS_LK/lightkurve/lightkurve/search.py in _fetch_tesscut_path(self, target, sector, download_dir, cutout_size)
366         sec = TesscutClass().get_sectors(coords)
--> 367         sector_name = sec[sec['sector'] == 1]['sectorName'][0]
368         if isinstance(cutout_size, int):
astropy/table/_column_mixins.pyx in astropy.table._column_mixins._ColumnGetitemShim.getitem()
astropy/table/_column_mixins.pyx in astropy.table._column_mixins.base_getitem()
astropy/table/_column_mixins.pyx in astropy.table._column_mixins.column_getitem()
IndexError: index 0 is out of bounds for axis 0 with size 0
During handling of the above exception, another exception occurred:
SearchError                               Traceback (most recent call last)
 in
1 import lightkurve as lk
2 search_result = lk.search_tesscut('HAT-P-11', sector=14)
----> 3 tpf = search_result.download(cutout_size=20)
~/Desktop/TESS_LK/lightkurve/lightkurve/utils.py in wrapper(*args, **kwargs)
471             sys.stdout = devnull
472             try:
--> 473                 return f(*args, **kwargs)
474             # restore to default
475             finally:
~/Desktop/TESS_LK/lightkurve/lightkurve/search.py in download(self, quality_bitmask, download_dir, cutout_size)
236                                   quality_bitmask=quality_bitmask,
237                                   download_dir=download_dir,
--> 238                                   cutout_size=cutout_size)
239
240     @suppress_stdout
~/Desktop/TESS_LK/lightkurve/lightkurve/search.py in _download_one(self, table, quality_bitmask, download_dir, cutout_size)
161                     raise SearchError('Unable to download FFI cutout. Desired target '
162                                     'coordinates may be too near the edge of the FFI.'
--> 163                                     'Error: {}'.format(exc))
164
165             return _open_downloaded_file(path,
SearchError: Unable to download FFI cutout. Desired target coordinates may be too near the edge of the FFI.Error: index 0 is out of bounds for axis 0 with size 0

@rebekah9969 Weird! Would you be able to let me know your Lightkurve version number (i.e. print(lk.__version__))?

1.8.0
On Thu, Mar 12, 2020 at 5:08 PM Geert Barentsen<EMAIL_ADDRESS>wrote:

@rebekah9969 https://github.com/rebekah9969 Weird! Would you be able to
let me know your Lightkurve version number (i.e. print(lk.version))?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/KeplerGO/lightkurve/issues/710#issuecomment-598419006,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFRHG26SU4CFNOYZ5YKKEDRHFFMXANCNFSM4LGTHLIQ
.

I have seen the same kind of error when upgrading to 1.9.0 this morning.  In version 1.8.0 and earlier it does not appear with me.  It makes all work with search_tesscut impossible because it seems to happen irrespective of the target.

The example posted at the top of this issue is working for me.  Would either of you be willing to try again?
When MAST ingests a new sector of TESS data into the TessCut service, the service occasionally goes down for a limited of time.  The service may also experience load issues at times.  It is therefore important to verify that the issues you both encountered were not transient (which would suggest a server-side rather than a Lightkurve issue).  Thanks++++!

Hello Gurt
I  just tried this and got the same error.
---------------------------------------------------------------------------IndexError
Traceback (most recent call
last)~/Desktop/TESS_LK/lightkurve/lightkurve/search.py in
_download_one(self, table, quality_bitmask, download_dir, cutout_size)
150
download_dir,--> 151
cutout_size)    152             except Exception as exc:
~/Desktop/TESS_LK/lightkurve/lightkurve/search.py in
_fetch_tesscut_path(self, target, sector, download_dir, cutout_size)
366         sec = TesscutClass().get_sectors(coords)--> 367
sector_name = sec[sec['sector'] == 1]['sectorName'][0]    368
if isinstance(cutout_size, int):
astropy/table/_column_mixins.pyx in
astropy.table._column_mixins._ColumnGetitemShim.getitem()
astropy/table/_column_mixins.pyx in astropy.table._column_mixins.base_getitem()
astropy/table/_column_mixins.pyx in
astropy.table._column_mixins.column_getitem()
IndexError: index 0 is out of bounds for axis 0 with size 0
During handling of the above exception, another exception occurred:
SearchError                               Traceback (most recent call
last) in       1 import
lightkurve as lk      2 search_result  = lk.search_tesscut('HAT-P-11',
sector=14)----> 3 tpf = search_result.download(cutout_size=20)
~/Desktop/TESS_LK/lightkurve/lightkurve/utils.py in wrapper(*args,
**kwargs)    471             sys.stdout = devnull    472
try:--> 473                 return f(*args, **kwargs)    474
restore to default    475             finally:
~/Desktop/TESS_LK/lightkurve/lightkurve/search.py in download(self,
quality_bitmask, download_dir, cutout_size)    236
quality_bitmask=quality_bitmask,    237
download_dir=download_dir,--> 238
cutout_size=cutout_size)    239     240
@suppress_stdout
~/Desktop/TESS_LK/lightkurve/lightkurve/search.py in
_download_one(self, table, quality_bitmask, download_dir, cutout_size)
161                     raise SearchError('Unable to download FFI
cutout. Desired target '    162
'coordinates may be too near the edge of the FFI.'--> 163
'Error: {}'.format(exc))    164     165
return _open_downloaded_file(path,
SearchError: Unable to download FFI cutout. Desired target coordinates
may be too near the edge of the FFI.Error: index 0 is out of bounds
for axis 0 with size 0
On Tue, Mar 24, 2020 at 2:43 PM Geert Barentsen<EMAIL_ADDRESS>wrote:

The example posted at the top of this issue is working for me. Would
either of you be willing to try again?
When MAST ingests a new sector of TESS data into the TessCut service, the
service occasionally goes down for a limited of time. The service may also
experience load issues at times. It is therefore important to verify that
the issues you both encountered were not transient (which would suggest a
server-side rather than a Lightkurve issue). Thanks++++!
[image: Screenshot from 2020-03-24 11-39-46]
https://user-images.githubusercontent.com/817669/77464335-406b1a80-6dc4-11ea-8cb6-30960c12c5f8.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/KeplerGO/lightkurve/issues/710#issuecomment-603438210,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFRHG62MOE6OOUBIM6TWFDRJD5LVANCNFSM4LGTHLIQ
.

Weird, it's still working fine for me!
@rebekah9969 Would you be willing to:

Re-run the example with debugging output enabled, and post the debug messages on the GitHub issue.  You can use the following snippet to enable debugging messages:

import lightkurve as lk
lk.log.setLevel("DEBUG")
search_result  = lk.search_tesscut('HAT-P-11', sector=14)
tpf = search_result.download(cutout_size=20)

The debugging messages should show this:
Started querying MAST for observations within 0.0001 arcsec of objectname='HAT-P-11'.
MAST found 5 observations. Now querying MAST for the corresponding data products.
Found 1 matching cutouts.
Started downloading TESSCut for 'HAT-P-11' sector 14.
Finished downloading.
Opening /home/gb/.lightkurve-cache/tesscut/tess-s0014-2-4_297.709364_48.080860_20x20_astrocut.fits.
Detected filetype: 'TessTargetPixelFile'.
0% (4/1241) of the cadences will be ignored due to the quality mask (quality_bitmask=175).

It is possible that the debugging messages mention that a cached file is being used on your system.  In that case, deleting the cached file may solve the issue. However please save a copy of the cached file before deleting it.  If a corrupt cache file is the culprit, I would love to receive a copy of it to diagnose what went wrong.

If the above didn't yield a solution, could you confirm which version of Lightkurve you are using (print(lk.__version__)) and verify that you also encounter the issue when using the latest Lightkurve version i.e. v1.9.1.  We had a bug inside search_tesscut on the master branch at some point in February, but it was fixed before we released v1.9.0.

When I use the debug option you suggested I get the following,
Started querying MAST for observations within 0.0001 arcsec of
objectname='HAT-P-11'.
MAST found 5 observations. Now querying MAST for the corresponding
data products.
Found 1 matching cutouts.
Started downloading TESSCut for 'HAT-P-11' sector 14.
And then the same error
On Thu, Mar 26, 2020 at 1:28 PM Geert Barentsen<EMAIL_ADDRESS>wrote:

Weird, it's still working fine for me!
@rebekah9969 https://github.com/rebekah9969 Would you be willing to:

Re-run the example with debugging output enabled, and post the
debug messages on the GitHub issue. You can use the following snippet to
enable debugging messages:

import lightkurve as lk
lk.log.setLevel("DEBUG")
search_result  = lk.search_tesscut('HAT-P-11', sector=14)
tpf = search_result.download(cutout_size=20)
The debugging messages should show this:
Started querying MAST for observations within 0.0001 arcsec of objectname='HAT-P-11'.
MAST found 5 observations. Now querying MAST for the corresponding data products.
Found 1 matching cutouts.
Started downloading TESSCut for 'HAT-P-11' sector 14.
Finished downloading.
Opening /home/gb/.lightkurve-cache/tesscut/tess-s0014-2-4_297.709364_48.080860_20x20_astrocut.fits.
Detected filetype: 'TessTargetPixelFile'.
0% (4/1241) of the cadences will be ignored due to the quality mask (quality_bitmask=175).
It is possible that the debugging messages mention that a cached file is
being used on your system. In that case, deleting the cached file may solve
the issue. However please save a copy of the cached file before
deleting it. If a corrupt cache file is the culprit, I would love to
receive a copy of it to diagnose what went wrong.

If the above didn't yield a solution, could you confirm which
version of Lightkurve you are using (print(lk.version)) and verify
that you also encounter the issue when using the latest Lightkurve version
i.e. v1.9.1. We had a bug inside search_tesscut on the master branch
at some point in February, but it was fixed before we released v1.9.0.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/KeplerGO/lightkurve/issues/710#issuecomment-604566935,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFRHG6HIYJB5B3Z5YXS3BDRJOGFTANCNFSM4LGTHLIQ
.

I just updated to 1.9.1 and it now seems to work.

Perfect.  Thanks for confirming! :+1:


Error on creating new SPVisioServiceApplication: Command not found

Problem description
When creating a new Visio Service application, I'm getting that the command new-SPVisioServiceApplication is not found.
This is a fresh rollout of SP2019 on Windows 2019 servers. I believe line 111 in the MSFT_SPVisioServiceApp resource generates the issue. Just to make sure, I checked if something was off with my Sharepoint snapin, but the New-SPVisioServiceApplication cmdlet is there.
Other webapplications are getting created succesfully.
DSC Operational log:
Job {658948CE-987B-11EC-8DB2-EE000000024D} :
MIResult: 1
Error Message: PowerShell DSC resource MSFT_SPVisioServiceApp  failed to execute Set-TargetResource functionality with error message: The term 'New-SPVisioServiceApplication' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Message ID: ProviderOperationExecutionFailure
Error Category: 7
Error Code: 1
Error Type: MI

Job {658948CE-987B-11EC-8DB2-EE000000024D} :
Message The term 'New-SPVisioServiceApplication' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
HResult -2146233087
StackTrack    at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()
   at System.Management.Automation.PowerShell.CoreInvokeRemoteHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
   at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
   at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
   at Microsoft.PowerShell.DesiredStateConfiguration.Internal.ResourceProviderAdapter.ExecuteCommand(PowerShell powerShell, ResourceModuleInfo resInfo, String operationCmd, List`1 acceptedProperties, CimInstance nonResourcePropeties, CimInstance resourceConfiguration, LCMDebugMode debugMode, PSInvocationSettings pSInvocationSettings, UInt32& resultStatusHandle, Collection`1& result, ErrorRecord& errorRecord, PSModuleInfo localRunSpaceModuleInfo)

Verbose logs
{"time": "2022-02-28T11:06:28.511+01:00", "type": "verbose", "message": "[APP01]: LCM:  [ Start  Resource ]  [[SPVisioServiceApp]VisioServiceApplication]  "},
  {"time": "2022-02-28T11:06:28.511+01:00", "type": "verbose", "message": "[APP01]: LCM:  [ Start  Test     ]  [[SPVisioServiceApp]VisioServiceApplication]  "},
  {"time": "2022-02-28T11:06:28.932+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Testing Visio Graphics service app 'Visio Graphics Service Application'"},
  {"time": "2022-02-28T11:06:28.932+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Getting Visio Graphics service app 'Visio Graphics Service Application'"},
  {"time": "2022-02-28T11:06:28.932+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Executing as the local run as user domain\\setupaccount"},
  {"time": "2022-02-28T11:06:28.932+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Leaving BeginProcessing Method of Get-SPServiceApplication."},
  {"time": "2022-02-28T11:06:28.932+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Leaving ProcessRecord Method of Get-SPServiceApplication."},
  {"time": "2022-02-28T11:06:28.932+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Leaving EndProcessing Method of Get-SPServiceApplication."},
  {"time": "2022-02-28T11:06:28.932+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Current Values: ApplicationPool=SharePoint Web Services Default; Ensure=Absent; Name=Visio Graphics Service Application"},
  {"time": "2022-02-28T11:06:28.932+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Target Values: ApplicationPool=SharePoint Web Services Default; Ensure=Present; Name=Visio Graphics Service Application; ProxyName=Visio Graphics Service Application Proxy; Verbose=True"},
  {"time": "2022-02-28T11:06:28.932+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Test-TargetResource returned False"},
  {"time": "2022-02-28T11:06:28.932+01:00", "type": "verbose", "message": "[APP01]: LCM:  [ End    Test     ]  [[SPVisioServiceApp]VisioServiceApplication]  in 0.4220 seconds."},
  {"time": "2022-02-28T11:06:28.932+01:00", "type": "verbose", "message": "[APP01]: LCM:  [ Start  Set      ]  [[SPVisioServiceApp]VisioServiceApplication]  "},
  {"time": "2022-02-28T11:06:29.261+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Setting Visio Graphics service app 'Visio Graphics Service Application'"},
  {"time": "2022-02-28T11:06:29.261+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Getting Visio Graphics service app 'Visio Graphics Service Application'"},
  {"time": "2022-02-28T11:06:29.261+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Executing as the local run as user domain\\setupaccount"},
  {"time": "2022-02-28T11:06:29.261+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Leaving BeginProcessing Method of Get-SPServiceApplication."},
  {"time": "2022-02-28T11:06:29.261+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Leaving ProcessRecord Method of Get-SPServiceApplication."},
  {"time": "2022-02-28T11:06:29.261+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Leaving EndProcessing Method of Get-SPServiceApplication."},
  {"time": "2022-02-28T11:06:29.261+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Creating Visio Graphics Service Application Visio Graphics Service Application"},
  {"time": "2022-02-28T11:06:29.261+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApplication] Executing as the local run as user domain\\setupaccount"},
  {"time": "2022-02-28T11:06:29.292+01:00", "type": "verbose", "message": "[APP01]: LCM:  [ End    Set      ]  [[SPVisioServiceApp]VisioServiceApplication]  in 0.3600 seconds."},
  {"time": "2022-02-28T11:06:29.292+01:00", "type": "error", "message": "PowerShell DSC resource MSFT_SPVisioServiceApp  failed to execute Set-TargetResource functionality with error message: The term 'New-SPVisioServiceApplication' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. "},

DSC configuration
SPVisioServiceApp VisioServiceApplication{
            Name                 = "Visio Graphics Service Application";
            ProxyName            = "Visio Graphics Service Application Proxy";
            ApplicationPool      = "SharePoint Web Services Default";
            PsDscRunAsCredential = $SPSetupAccount;
            DependsOn            = "[SPServiceAppPool]SharePointWebServicesDefault"
        }

Suggested solution
Checking for the command in memory, if not, adding sharepoint pssnapin?
SharePoint version and build
Sharepoint 2019 (16.0.10383.20001)

Operating system the target node is running
OsName               : Microsoft Windows Server 2019 Standard
OsOperatingSystemSKU : StandardServerEdition
OsArchitecture       : 64-bit
WindowsVersion       : 1809
WindowsBuildLabEx    : 17763.1.amd64fre.rs5_release.180914-1434
OsLanguage           : en-US
OsMuiLanguages       : {en-US}

PowerShell version and build the target node is running
Name                           Value
----                           -----
PSVersion                      5.1.17763.2268
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.2268
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

SharePointDsc version
Name          Version Path
----          ------- ----
SharePointDSC 5.0.0   C:\Program Files\WindowsPowerShell\Modules\SharePointDSC\5.0.0\SharePointDSC.psd1

The next run, it ran fine. I've had this happen before when starting of fresh. Might this be an issue with the visio resource creation starting before the snapin is loaded?

This issue has been reported before, #372 and #790. Unfortunately we were unable to solve the issue in those cases because we were unable to reproduce and the issue creator didn't respond anymore.
This issue has something to do with timing: The code is loading the snap-in, but still can't find the cmdlet. Are you able to reproduce the issue when deploying a new farm?

I was just about to do a fresh deploy overnight, I'll let you know tomorrow.

Great! Just another quick question: Are you using SQLServerDsc in the same config by any chance?

Oh and another request if you are able to reproduce, could you please do another fresh deployment and test the following:
Adding a Start-Sleep -Seconds 3 in front of line 111 in MSFT_SPVisioServiceApp.psm1? Just to see if this is a timing issue.

No SQLServerDsc in use. I am using these, though:

xWebAdministration
CertificateDSC
StorageDSC
xCredSSP
OfficeOnlineServerDsc

The reason why I was rolling out a fresh deploy, is that I refactored my config. Of course this results in a failed deploy because of dependencies, which I'm currently trying to fix first. I'll get back here once I have that fixed.
Bear with me...

And we're back. I've added the sleep to the code, and the issue persists. Once finished, the second time the dsc config is applied, the issue is fixed. I've just missed it this time. If you want me to test some more, just let me know, happy to help!

Upped the sleep time to 120 seconds, which is clearly visible in the log, yet the commandlet is still unavailable:
  {"time": "2022-03-09T13:16:22.061+01:00", "type": "verbose", "message": "[APP01]: LCM:  [ Start  Resource ]  [[SPVisioServiceApp]VisioServiceApp]  "},
  {"time": "2022-03-09T13:16:22.061+01:00", "type": "verbose", "message": "[APP01]: LCM:  [ Start  Test     ]  [[SPVisioServiceApp]VisioServiceApp]  "},
  {"time": "2022-03-09T13:16:22.482+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Testing Visio Graphics service app 'Visio Graphics Service Application'"},
  {"time": "2022-03-09T13:16:22.482+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Getting Visio Graphics service app 'Visio Graphics Service Application'"},
  {"time": "2022-03-09T13:16:22.482+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Executing as the local run as user UGENT\\SA-Setup"},
  {"time": "2022-03-09T13:16:22.482+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Leaving BeginProcessing Method of Get-SPServiceApplication."},
  {"time": "2022-03-09T13:16:22.482+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Leaving ProcessRecord Method of Get-SPServiceApplication."},
  {"time": "2022-03-09T13:16:22.482+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Leaving EndProcessing Method of Get-SPServiceApplication."},
  {"time": "2022-03-09T13:16:22.482+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Current Values: ApplicationPool=SharePoint Web Services Default; Ensure=Absent; Name=Visio Graphics Service Application"},
  {"time": "2022-03-09T13:16:22.482+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Target Values: ApplicationPool=SharePoint Web Services Default; Ensure=Present; Name=Visio Graphics Service Application; ProxyName=Visio Graphics Service Application Proxy; Verbose=True"},
  {"time": "2022-03-09T13:16:22.482+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Test-TargetResource returned False"},
  {"time": "2022-03-09T13:16:22.498+01:00", "type": "verbose", "message": "[APP01]: LCM:  [ End    Test     ]  [[SPVisioServiceApp]VisioServiceApp]  in 0.4370 seconds."},
  {"time": "2022-03-09T13:16:22.498+01:00", "type": "verbose", "message": "[APP01]: LCM:  [ Start  Set      ]  [[SPVisioServiceApp]VisioServiceApp]  "},
  {"time": "2022-03-09T13:16:23.207+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Setting Visio Graphics service app 'Visio Graphics Service Application'"},
  {"time": "2022-03-09T13:16:23.207+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Getting Visio Graphics service app 'Visio Graphics Service Application'"},
  {"time": "2022-03-09T13:16:23.207+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Executing as the local run as user UGENT\\SA-Setup"},
  {"time": "2022-03-09T13:16:23.207+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Leaving BeginProcessing Method of Get-SPServiceApplication."},
  {"time": "2022-03-09T13:16:23.207+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Leaving ProcessRecord Method of Get-SPServiceApplication."},
  {"time": "2022-03-09T13:16:23.207+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Leaving EndProcessing Method of Get-SPServiceApplication."},
  {"time": "2022-03-09T13:16:23.207+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Creating Visio Graphics Service Application Visio Graphics Service Application"},
  {"time": "2022-03-09T13:16:23.207+01:00", "type": "verbose", "message": "[APP01]:                            [[SPVisioServiceApp]VisioServiceApp] Executing as the local run as user UGENT\\SA-Setup"},
  {"time": "2022-03-09T13:18:22.889+01:00", "type": "verbose", "message": "[APP01]: LCM:  [ End    Set      ]  [[SPVisioServiceApp]VisioServiceApp]  in 120.3910 seconds."},
  {"time": "2022-03-09T13:18:22.889+01:00", "type": "error", "message": "PowerShell DSC resource MSFT_SPVisioServiceApp  failed to execute Set-TargetResource functionality with error message: The term 'New-SPVisioServiceApplication' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. "},

same problem as
https://github.com/dsccommunity/SharePointDsc/issues/990
The loaded Powershell can not load New-SPVisioServiceApplication.
A Remove- & Add-PsSnapin not solve this... The CmdLet New-SPVisioServiceApplication not available.


Bump Upjet to commit be5e036

Description of your changes

I would like to consume Upjet PRs that come before https://github.com/crossplane/upjet/pull/424, so that changes because of those don't crowd https://github.com/crossplane-contrib/provider-upjet-aws/pull/1422. This PR consumes the following (listed in chronological order of merging):

https://github.com/crossplane/upjet/pull/441 (5cdf369)
https://github.com/crossplane/upjet/pull/413 (7eaaf8a)
https://github.com/crossplane/upjet/pull/289 (a18bd41)
https://github.com/crossplane/upjet/pull/449 (be5e036)

I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable to ensure this PR is ready for review.
[ ] ~Added backport release-x.y labels to auto-backport this PR if necessary.~

How has this code been tested

Uptest runs:

examples/dynamodb/v1beta1/table.yaml
examples/ec2/v1beta2/vpcendpoint.yaml
examples/s3/v1beta1/bucket.yaml

/test-examples="examples/ec2/v1beta1/vpcendpoint.yaml"

/test-examples="examples/s3/v1beta1/bucket.yaml"

/test-examples="examples/dynamodb/v1beta1/table.yaml"

/test-examples="examples/ec2/v1beta2/vpcendpoint.yaml"

Thank you for the PR @mergenci, we need to backport the API changes in v1beta2 to v1beta1 here too :) It would also be good if we could test some of the resources we backported with uptest.

Thanks for the catch @turkenf 💪 I committed each step of the backporting separately. I noticed that our automatic tooling is not able to handle new fields in renamed types. See https://github.com/crossplane-contrib/provider-upjet-aws/pull/1573/commits/318fcbb72cd1f28f513eccac213f8b7aaa92e055. I'll take a note of the situation in the documentation. I'll run Uptests as you suggested.

/test-examples="examples/ssm/v1beta2/maintenancewindowtask.yaml"

/test-examples="examples/apigateway/v1beta2/restapi.yaml"

/test-examples="examples/ssm/v1beta2/association.yaml"

/test-examples="examples/dynamodb/v1beta1/table.yaml"

/test-examples="examples/ec2/v1beta2/vpcendpoint.yaml"

/test-examples="examples/s3/v1beta1/bucket.yaml"

/test-examples="examples/apigateway/v1beta2/restapi.yaml"


building with npm

I am slowly giving up on Haskell, iHaskell in Jupyter worked, then don't ... as usual
pm ERR! Linux 5.13.0-30-generic
npm ERR! argv "/home/ma/anaconda3/bin/node" "/home/ma/anaconda3/bin/npm" "run" "build"
npm ERR! node v6.13.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build: tsc
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'tsc'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the jupyterlab-ihaskell package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     tsc
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs jupyterlab-ihaskell
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls jupyterlab-ihaskell
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/ma/ihaskell-brew/IHaskell/jupyterlab-ihaskell/labextension/npm-debug.log

I'm sorry you're having a difficult time with IHaskell, it is unfortunately a complicated bit of software to install because it involves wrangling the Haskell, Python, and Node dependencies simultaneously. I don't see why you need to use jupyterlab-ihaskell if you're using classic notebooks though (with jupyter notebook), and if you are sure you want JupyterLab we also provide a prebuilt extension that can be copied to e.g. ~/.local/share/jupyter/labextensions/jupyterlab-ihaskell so you don't have to build it yourself.

Every rime I build Haskell I somehow succeed (every time I reinstall the system I do it, because it posses a challenge), I've seen the JupyterLab extension, I've used it sometime ago. This time stack install ihaskell was needed, it wasn't earlier.


UI: placeholder to refine the UI

The minimal UI to enable INT in a single EVC will be covered on mef_eline's UI https://github.com/kytos-ng/mef_eline/issues/180
But still it's desirable to have UI fully supporting these endpoints:

POST v1/evc/enable
POST v1/evc/disable
POST v1/evc/redeploy

It still needs refined, but I'll go ahead and capture this on this issue, based on our last planning 2023.2, it's desirable to have, it's our tentative list, so I'll leave it with priority_low at this time

This has been refined on issue #92 and #93, so I'll go ahead and close this one here for now