SPFx in Teams tab not rendering until browsed to in spo

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
macOS
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[X] other (enter in the "Additional environment details" area below)

Additional environment details

MacOS Teams Desktop Client

Describe the bug / error
I have a custom Teams personal app that has two tabs: one tab surfaces an spfx webpart, while the other a React SPA provisioned and deployed using the Teams Toolkit. After a couple days of not browsing to the custom Teams app, however, the tab that surfaces the SPFx component is stuck on a spinner -- the other tab has no problems. The console gives me the following error:
App resource defined in manifest and iframe origin do not match
failureCallback @ TeamsLogon.aspx?SPFX...rceLocale=en-us:240
In order to get the spfx tab to render I have to do the following in Chrome and Edge:
browse to a SharePoint page with the webpart and then refresh the static tab in Teams
On the Teams Desktop client I added a reference to the SharePoint page in a Teams Channel and after browsing to that Teams channel tab I can then see the spfx component in the custom app's spfx tab
Steps to reproduce

Create 3 webparts: a search webpart, a directory webpart, and a faculty webpart that references the two main components of the search and directory webparts. For example, the FacultyWebpart.tsx will render the Faculty.tsx component, whose function is to render the Search.tsx and Faculty.tsx components.
Create your own teams manifest.json file in the teams folder of the SharePoint solution, so that when you deploy the sppkg it knows which webpart to make available in Teams
Create a Fluent UI Personal app using the Teams Toolkit
In the manifest.json inside the appPackage folder, create two static tabs: one that references the spfx webpart to be served and the other tab for the React app provided by Teams Toolkit
Provision, Deploy, and send to Production

Expected behavior
I shouldn't have to browse to the SPO page with the spfx webpart to then see it in the custom Teams app

Here's what my Teams Toolkit manifest.json looks like:
{
  "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.17/MicrosoftTeams.schema.json",
  "version": "1.26.0",
  "manifestVersion": "1.17",
  "id": "bda4dea9-fa92-4f2c-81a1-8b95a8c70e40",
  "name": {
    "short": "Directory",
    "full": "Full name for Directory"
  },
  "developer": {
    "name": "JourneyTEAM, LLC",
    "websiteUrl": "https://www.journeyteam.com",
    "privacyUrl": "https://www.journeyteam.com",
    "termsOfUseUrl": "https://www.journeyteam.com"
  },
  "description": {
    "short": "Short description of DepartmentDirectory",
    "full": "Full description of DepartmentDirectory"
  },
  "icons": {
    "outline": "outline.png",
    "color": "color.png"
  },
  "accentColor": "#FFFFFF",
  "staticTabs": [
    {
      "entityId": "SPFxEmployeeDirectoryTab",
      "name": "Faculty & Staff",
      "contentUrl": "https://(redacted_domain_name).sharepoint.com/_layouts/15/TeamsLogon.aspx?SPFX=true&dest=/_layouts/15/teamshostedapp.aspx%3Fteams%26personal%26componentId=386dd1b8-71f5-4d5d-a568-b44b211067f0%26forceLocale=en-us",
      "scopes": [
        "personal"
      ],
      "context": [
        "personalTab"
      ]
    },
    {
      "entityId": "DepartmentDirectoryTab",
      "name": "Departments",
      "contentUrl": "https://ashy-hill-0f884b110.5.azurestaticapps.net/index.html#/department-directory",
      "websiteUrl": "https://ashy-hill-0f884b110.5.azurestaticapps.net/index.html#/department-directory",
      "scopes": [
        "personal"
      ]
    },
    {
      "entityId": "about",
      "scopes": [
        "personal"
      ]
    }
  ],
  "validDomains": [
    "(redacted_domain_name).sharepoint.com",
    "ashy-hill-0f884b110.5.azurestaticapps.net",
    "*.login.microsoftonline.com",
    "*.sharepoint.com",
    "*.sharepoint-df.com",
    "spoppe-a.akamaihd.net",
    "spoprod-a.akamaihd.net",
    "ashy-hill-0f884b110.5.azurestaticapps.net*"
  ],
  "webApplicationInfo": {
    "id": "2db8265f-5a18-4d83-a39c-335603046850",
    "resource": "api://ashy-hill-0f884b110.5.azurestaticapps.net/2db8265f-5a18-4d83-a39c-335603046850"
  },
  "authorization": {
    "permissions": {
      "resourceSpecific": []
    }
  }
}

Here's what my spfx teams manifest.json looks like:
{
	"$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.17/MicrosoftTeams.schema.json",
	"version": "1.2",
	"manifestVersion": "1.17",
	"id": "aa1185ab-38c1-4621-b54d-90e94523e602",
	"developer": {
		"name": "JourneyTEAM, LLC",
		"mpnId": "",
		"websiteUrl": "https://www.journeyteam.com",
		"privacyUrl": "https://www.journeyteam.com",
		"termsOfUseUrl": "https://www.journeyteam.com"
	},
	"name": {
		"short": "Teams Faculty Directory",
		"full": "Teams Faculty Directory"
	},
	"description": {
		"short": "Teams Employee Directory description",
		"full": "Teams Employee Directory description"
	},
	"icons": {
		"outline": "aa1185ab-38c1-4621-b54d-90e94523e602_outline.png",
		"color": "aa1185ab-38c1-4621-b54d-90e94523e602_color.png"
	},
	"accentColor": "#FFFFFF",
	"staticTabs": [
		{
			"entityId": "Belmont Faculty Directory",
			"name": "Faculty Directory",
			"contentUrl": "https://(redacted_domain_name).sharepoint.com/_layouts/15/TeamsLogon.aspx?SPFX=true&dest=/_layouts/15/teamshostedapp.aspx%3Fteams%26personal%26componentId=386dd1b8-71f5-4d5d-a568-b44b211067f0%26forceLocale=en-us",
			"scopes": ["personal"],
			"context": ["personalTab"]
		},
		{
			"entityId": "about",
			"scopes": ["personal"]
		}
	],
	"validDomains": [
		"*.login.microsoftonline.com",
		"*.sharepoint.com",
		"*.sharepoint-df.com",
		"spoppe-a.akamaihd.net",
		"spoprod-a.akamaihd.net",
		"resourceseng.blob.core.windows.net",
		"msft.spoppe.com"
	],
	"webApplicationInfo": {
		"id": "00000003-0000-0ff1-ce00-000000000000",
		"resource": ""
	}
}

Here's an example of how I call the two components from two separate webparts:
import * as React from "react";
import { useMemo, useState } from "react";
import styles from "./FacultyStudentTeamsDirectory.module.scss";
import type { IFacultyStudentTeamsDirectoryProps } from "./IFacultyStudentTeamsDirectoryProps";
import EmployeeDirectory from "../../employeeDirectory/components/EmployeeDirectory";
import { IReactTemplateProps } from "@journeyteam/directory-extensions";
import SearchBox from "../../searchBox/components/SearchBox";
import { ISelectedRefiner, ISelectedRefinerValues } from "../../../models/refiner";
import * as SPSearch from "@pnp/sp/search/types";

export declare enum TemplateType {
	adaptiveCard = "adaptive-card",
	react = "react",
	handlebars = "handelbars",
}
export default function FacultyStudentTeamsDirectory(props: IFacultyStudentTeamsDirectoryProps) {
	const {
		isDarkTheme,
		hasTeamsContext,
		initialSearchText,
		employeeCardTemplate,
		studentView,
		propertyPanelOpen,
		focusSections,
		directoryRefiners,
		refiners,
	} = props;

	const [selectedRefiners, setSelectedRefiners] =
		useState<ISelectedRefinerValues[]>(directoryRefiners);
	const [searchBoxRefinersSourceData, setSearchBoxRefinersSourceData] = useState<
		SPSearch.IRefiner[]
	>([]);
	const [searchText, setSearchText] = useState(initialSearchText ? initialSearchText : "");
	const [cardWidth, setCardWidth] = useState(275);

	useMemo(() => {
		const handleResize = () => {
			if (window.innerWidth < 500) {
				setCardWidth(150);
			} else if (window.innerWidth < 800) {
				setCardWidth(200);
			} else {
				setCardWidth(275);
			}
		};

		// Call the handleResize function initially to set the width based on the current viewport size
		handleResize();

		// Set up the event listener for the resize event
		window.addEventListener("resize", handleResize);

		// Clean up the event listener when the component is unmounted
		return () => {
			window.removeEventListener("resize", handleResize);
		};
	}, []);

	const searchBoxRefinersChanged = (searchBoxRefiners: ISelectedRefiner[]) => {
		const mappedSelectedRefiners = refiners.map<ISelectedRefinerValues>((refiner) => {
			const matchedRefiners = searchBoxRefiners.filter(
				(selectedRefiner) => selectedRefiner.Name === refiner.PropertyName
			);
			return {
				PropertyName: refiner.PropertyName,
				SelectedRefiners: matchedRefiners,
			};
		});
		setSelectedRefiners(mappedSelectedRefiners);
	};

	const onSearchChange = (val: string) => {
		setSearchText(val);
	};

	const _refinersChanged = (refiners: SPSearch.IRefiner[]) => {
		if (searchBoxRefinersSourceData.length === 0) {
			setSearchBoxRefinersSourceData(refiners);
		}
		if (searchBoxRefinersSourceData[0]?.Entries.length < 20) {
			setSearchBoxRefinersSourceData(refiners);
		}
	};

	return (
		<section
			className={`${styles.facultyStudentTeamsDirectory} ${hasTeamsContext ? styles.teams : ""}`}>
			<SearchBox
				onSearchChanged={onSearchChange}
				initialSearchText={initialSearchText}
				refinerSourceData={searchBoxRefinersSourceData}
				refiners={props.refiners}
				onSelectedRefinersChanged={searchBoxRefinersChanged}
				searchByFilters={props.searchByFilters}
				searchByLabel={undefined}
				searchByPlaceholder="Search By"
				refinersLabel=""
				refinersPlaceholder="Search Refiners"
				searchLabel={""}
				searchPlaceholder={""}
			/>

			<EmployeeDirectory
				 searchText={`${
					searchText}*`}
				itemsPerPage={20}
				preFilter={`-"SPS-HideFromAddressLists":1`}
				refiners={selectedRefiners}
				onRefinersChanged={_refinersChanged}
				useLibraryTemplate={false}
				showProfileLink={undefined}
				customStyles={undefined}
				employeeCardTemplate={employeeCardTemplate}
				focusSections={focusSections}
				headerSections={props.headerSections}
				otherSections={[]}
				sourceId={undefined}
				sort={[
					{
						Property: "firstName",
						Direction: 0,
					},
				]}
				hiddenRefiner={[]}
				serviceScope={props.serviceScope}
				context={props.context}
				templates={props.templates}
				editMode={true}
				employeeCardWidth={cardWidth}
				propertyPanelOpen={propertyPanelOpen}
				paginationLocation={1}
				toggleDirectReportsExport={false}
				directReportsExportUrl=""
				studentView={studentView}
				isDarkTheme={isDarkTheme}
			/>

	);
}

Further update...just deploying my spfx solution and syncing to Teams works as a standalone personal app. The personal app that has multiple personal tabs (one being the spfx component and the other being a React app provisioned and deployed in Entra) doesn't work for the spfx tab until I first navigate to the standalone spfx personal app

@VesaJuvonen any update on your guys end by chance?

From what I'm seeing, seems the issue may lie in that the teams app manifest only allows for one set of id and resource to be referenced in the webApplicationInfo. In my case, one tab is leveraging an spfx component (resource would be the teamsitedomain and id the multi-tentant Microsoft Graph app id) and the other a teams app that was provisioned in entra using the Teams Toolkit.


onCancelled dont get trigger

onCancelled dont get trigger if it was cancelled before it getting to the login page. I had tried to look at the previous issues and said it was because it was version 3.5 but I think i had included the correct head version.
<script src="https://www.paypalobjects.com/api/checkout.js" data-version-4></script>
paypal.Button.render({

           env: "sandbox",

           // Set up a getter to create a Payment ID using the payments api, on your server side:
           onCancel: function (data) {
               alert("hello");
               // window.postMessage("close");
           },
          ..... other method
           style: {
               size: 'responsive', // tiny, small, medium
               color: 'gold', // orange, blue, silver
               shape: 'rect', // pill, rect
           }

       }, '#paymentButton');

We are experiencing the same as well.

This should be resolved now. Please clear your browser cache and let me know if you still see the issue. Thanks!

Fixed indeed!

I am using angularjs and I can confirm onCancel is never called.

@joweste can you raise a new issue and fill out the details with your version, etc?


Hdp dependencies

Adds maven relocation for conflicting jars with Hortonworks Ranger. Also updates ranger common plugins to latest ver

incorrect branch


Re-factor document.getElementsByName lookups in the AnnotationLayer (issue 14003)

This replaces direct document.getElementsByName lookups with a helper method which:

Lets the AnnotationLayer use the data returned by the PDFDocumentProxy.getFieldObjects API-method, such that we can directly lookup only the necessary DOM elements.
Fallback to using document.getElementsByName as before, such that e.g. the standalone viewer components still work.

Finally, to fix the problems reported in issue 14003, regardless of the code-path we now also enforce that the DOM elements found were actually created by the AnnotationLayer code.
With these changes we'll thus be able to update form elements on all visible pages just as before, but we'll additionally update the AnnotationStorage for not-yet-rendered elements thus fixing a pre-existing bug.
Fixes #14003

/botio integrationtest

@Snuffleupagus here is an integration test: https://github.com/calixteman/pdf.js/commit/2d551ea62e147841679cab821241ed6b32363dbf

@Snuffleupagus here is an integration test: calixteman@2d551ea

Thank you, thank looks fantastic!

/botio integrationtest

@Rob--W Review ping; did you want to take a closer look specifically at the GetElementsByNameSet-part of this patch, since that's most relevant to issue #14003?
The rest of the patch fixes an existing short-comings of the implementation, with it not being able to target elements on not-yet-rendered pages, and have been reviewed by Calixte.

/botio unittest

/botio integrationtest

/botio test


Please migrate Newtonsoft.Json to System.Text.Json, to reduce download szie

Hi Team,
Please remove dependence of Newtonsoft.Json, and migrate json processing to System.Text.Json. It will save few kb of download size and improve performance.
Microsoft recommends it.
https://docs.microsoft.com/en-us/dotnet/standard/serialization/system-text-json-migrate-from-newtonsoft-how-to?pivots=dotnet-6-0

The problem is that System.Text.Json still is not equivalent to Newtonsoft.Json (and if you ask me has still childhood problems even with simple types...). Just my opinion, I'm not using System.Text.Json anywhere because of these issues.


Create release preparation pipeline for bundle

This is complete
https://azfunc.visualstudio.com/Azure Functions/_release?view=all&_a=releases&definitionId=49


[Docs] Fix DefaultTechDocsCollatorFactory how-to

Hey, I just made a Pull Request!
Just keeping the how-to guide in sync with the latest scheduler changes.
:heavy_check_mark: Checklist

[x] Added or updated documentation
[x] All your commits have a Signed-off-by line in the message. (more info)

I realised that I screwed up and was too quick at updating the docs! The new package update won't be out until the main release...


Address validation

This PR handles issue #295 and #322
This PR also implements JSHint. I added a few custom configurations in .jshintrc:

"asi": true - turns off the "missing semicolon" warning (unless we want this?)
"sub": true - http://jshint.com/docs/options/#sub
"multistr": true - http://jshint.com/docs/options/#multistr

I learned a couple things when running jshint:

We tend to close function declarations with semicolons, though our preferred style guide does not recommend it, not does JSHint. Let's be cautious of this.
We call view/context variables in the JS - an entirely common practice (e.g., "{{ my_context_variable_made_avaliable_in_the_template }}"). I found an instance where we (1) did not stringify the variable, and (2) called a Django filter on the JS side (e.g., {{ variable|safe }}).  It seems safer to convert such variables to JSON on the python side and then parse it on the JS side. (We can also use escapejs when appropriate, too.)

@hancush - I'd like to start documenting these JS "hints" (as it were) in the testing guidelines. At end of this section makes sense, no?

Now - those pesky merge conflict!


Screen artifact from Light sources with shadow map PCF filter enabled

Release Type: Official Release
Version: <IP_ADDRESS>2
Platform(s): Windows
Describe the bug
Point Light and Spot Light with shadow map PCF filter enabled produces a black screen artifact randomly.
To Reproduce
Steps to reproduce the behavior:

Create new project
Add a Point Light or Spot Light
Enable shadows
Enable PCF filter
Move around camera and the artifact should eventually appear across the screen

Expected behavior
No screen artifacts should appear.
Screenshots

I've reproduced this issue with a spotlight in the MyGame template - it even shows up in the editor.
After a lot of time inside RenderDoc, my conclusion is the following lines:
https://github.com/stride3d/stride/blob/4c46fdcc4da0021514fbaaea3d432095d164b9b6/sources/engine/Stride.Rendering/Rendering/Shadows/ShadowMapReceiverBase.sdsl#L39-L41
My understanding is that the first line transforms the pixel position (from world space) into "shadow map texture space".
This calculation occurs for every pixel on screen and basically every pixel that's nowhere near the spotlight/shadow should theoretically be "outside" the UV space of the shadow map. The problem is that there are some weird angles where this matrix calculation causes shadowPosition.w to be zero then the division by w causes xyz to be infinite and the subsequent shadow calculations produce garbage results (ie. NaN).
I think the solution might be to do an early exit check if the pixel isn't actually within the shadow map uv space?
Any graphics guru able to chime in?
I couldn't reproduce this issue with the point light, I think it needs a more precise setup to reproduce it, though I suspect it should have the same issue.

@Basewq thanks a lot for investigating. I've also traced this bug down to the shadow maps, but couldn't find the correct line.
I'll have a look at it!

I can confirm the issue is in the editor as well. Here's an example with a Point Light.

You can add these just before the division if you want to suppress the NaN issue
//check if shadowmap pixel pos are too close
if(shadowPosition.w < 1e-15){
    //add epsilon operator
    //shadowPosition.w += 1e-15;
    //or exit
    return 0.0;
}

Before

After


[BUG] The plugin needs a bit of "how to use" doccumentation.

Describe the bug
I cant find any instructions how to use the plugin.  I had to read the code to discover the commands.
To Reproduce
Steps to reproduce the behavior:

install the plugin
open a document
place the cursor where you want some text
????

Expected behavior
A paragraph or 2 in the README or nearby, with a list of the command words. Possibly also a recap of the <F1> method of opening the command window (for newer users of VSCode).
Once I did find the commands, it works great.
Desktop (please complete the following information):

OS: macos
Version 1.3.2

There is a wiki about how to run commans here: https://github.com/aroary/lorem_ipsum/wiki
The wiki is not displayed on the extension page but an abridged version should be added.


Unmet peer dependencies

Bug report
Required System information

Npm version: 8.5.4
NodeJS version: v16.14.2
Strapi Design System version: 4.3.2-beta1
Browser: All

Describe the bug
This project has peer-dependencies errors
Steps to reproduce the behavior
npm install --strict-peer-deps

Expected behavior
Install dependencies successfully
Current behavior
 ERR_NPM_PEER_DEP_ISSUES  Unmet peer dependencies

.
└─┬ @strapi/strapi
  └─┬ @strapi/admin
    ├─┬ @strapi/design-system
    │ └── ✕ unmet peer<EMAIL_ADDRESS>found 1.1.1 in @strapi/admin
    └─┬ react-virtualized
      ├── ✕ unmet peer<EMAIL_ADDRESS>|| ^16.0.0-alpha": found 17.0.2 in @strapi/admin
      └── ✕ unmet peer<EMAIL_ADDRESS>|| ^16.0.0-alpha": found 17.0.2 in @strapi/admin

Additional context
The error occurs also with pnpm

I believe this issue should be fixed in the latest release by https://github.com/strapi/design-system/pull/620 . In case you are still running into problems feel free to ping me :)


[WIP] Make celerite, pybind, scikit-learn, and bokeh optional dependencies

This PR addresses #435 by making celerite, pybind, scikit-learn, and bokeh optional dependencies.  This should make the installation of Lightkurve significantly easier without losing many features.
TODO:

[ ] Update installation docs to explain required vs optional dependencies.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@5b680bf). Click here to learn what that means.
The diff coverage is 46.15%.

@@            Coverage Diff            @@
##             master     #436   +/-   ##
=========================================
  Coverage          ?   88.28%
=========================================
  Files             ?       28
  Lines             ?     5011
  Branches          ?        0
=========================================
  Hits              ?     4424
  Misses            ?      587
  Partials          ?        0

Impacted Files
Coverage Δ

lightkurve/interact.py
59.84% <0%> (ø)

lightkurve/correctors.py
81.75% <50%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@5b680bf). Click here to learn what that means.
The diff coverage is 47.05%.

@@            Coverage Diff            @@
##             master     #436   +/-   ##
=========================================
  Coverage          ?   87.93%
=========================================
  Files             ?       28
  Lines             ?     5013
  Branches          ?        0
=========================================
  Hits              ?     4408
  Misses            ?      605
  Partials          ?        0

Impacted Files
Coverage Δ

lightkurve/tests/test_interact.py
94.18% <0%> (ø)

lightkurve/interact.py
59.84% <0%> (ø)

lightkurve/tests/test_correctors.py
75.36% <100%> (ø)

lightkurve/correctors.py
81.38% <50%> (ø)

Continue to review full report at Codecov.

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


Remove encoding/decoding of user-facing frame urls.

I'm reasonably sure these encode/decode function calls were added for a reason in the original pull request, but I can't remember why now, and I can't find a comment about them. Do either of you remember what these were for? The frame construction code has since changed, and looking at dashboards with graphite widgets I'm not seeing any breakage, so maybe they aren't needed.
fixes #280
@juliusv @grobie

Strong vote to write more tests in this project, as they act as a specification. The rate of "I have no idea why this functionality is here" got way too high recently for my taste.
The encoding and decoding was requested in order to

properly escape a user entered parameter (e.g. target set to alias(seriesList, "new $&?= name"))
make it easier to read/modify a given target by unescaping any special characters

this seem to do the trick?

I'm not sure what the behavior is now with this trick. I couldn't find tests nor at least a commit message which describes the reasons for the change in best case with examples. Mixing whitespace changes with behavior changes in one commit also makes it more difficult to see the changes.
Can you please split the commit in two and explain the changes in the commit message? This will also help in the future with questions like "Do either of you remember what these were for?".

split

I can't really judge the side effects of only escaping a few characters. In general my experience is that such "fixes" will only postpone the issue and lead to similar issues later. On the other hand, any other solution to handle template variables might require more changes to the code, so it might be a compromise we want to add. @juliusv time ;)

Hey, haven't forgotten about this - it's just queued behind launch-critical
stuff at the moment. Will get to it soon.
On Tue, Jan 20, 2015 at 8:14 PM, Tobias Schmidt<EMAIL_ADDRESS>wrote:

I can't really judge the side effects of only escaping a few characters.
In general my experience is that such "fixes" will only postpone the issue
and lead to similar issues later. On the other hand, any other solution to
handle template variables might require more changes to the code, so it
might be a compromise we want to add. @juliusv
https://github.com/juliusv time ;)
—
Reply to this email directly or view it on GitHub
https://github.com/prometheus/promdash/pull/283#issuecomment-70713600.

This probably needs a rebase on master now?

rebased, seems to still be working

@juliusv ping

@juliusv k, i think this is ready now. I can't think of a good way to support '&' in, say, an alias function, but that may just be an acceptable limitation.

@juliusv updated

:+1:


Blog app: Integration-Specs-for-Views -and-Fix-N+1-Problems

In this PR, I have done the following tasks.

Solved the N+1 problem when fetching all posts and comments for a user.
Used Capybara to write integration tests for each view in your project.
Added User index page integration tests
Added User show page integration tests
Added User post index page integration tests
Added Post show page integration tests

1.

2.

3.

4.

All tests:

Thanks for your comment. I have done all the comments!!!


Compiler arch not recognized in Windows + Anaconda due to localization of objdump

Window 7 64 bit, Anaconda3 64 bit, gcc 5.3.0
python -m nuitka --standalone --mingw64 hello.py

Error, mismatch between Python binary ('D:\data\anaconda3\python.exe' -> 'pei-x86-64') and C compiler ('D:\Data\anaconda3\Library\mingw-w64\bin\gcc.exe' -> 'None') arches.

The problem is due to the localized output of objdump (italian in this case):
objdump -f d:\data\anaconda3\Library\mingw-w64\bin\gcc.exe

d:\data\anaconda3\Library\mingw-w64\bin\gcc.exe:     formato del file pei-x86-64
architettura: i386:x86-64, flag 0x00000132:
EXEC_P, HAS_SYMS, HAS_LOCALS, D_PAGED
indirizzo di partenza 0x0000000000401510

Can be fixed in SingleExe.scons, lines 1430-1431:
        if " file format " in line:
            return line.split(" file format ")[-1]

become:
        if line.startswith(binary):
            return line.split()[-1]

You didn't check develop, did you? I believe that one is fixed there already. That fix just sets LANG=C making the output reliable.

Nuitka-0.6.9rc5-py3.7 still fails.
Manually setting LANG=C in the environment does work thoug.


Issue from website page 使用缓存图片

From URL: https://www.flutterchina.club/cookbook/images/cached-images.md
Because every version of flutter_test from sdk depends on http 0.12.0 and flutter_cache_manager >=0.1.0-rc.1 depends on http ^0.11.3+14, flutter_test from sdk is incompatible with flutter_cache_manager >=0.1.0-rc.1.
Because cached_network_image >=0.4.1 <0.4.2 depends on flutter_cache_manager ^0.1.1 and cached_network_image >=0.4.2 depends on flutter_cache_manager ^0.1.2, cached_network_image >=0.4.1 requires flutter_cache_manager ^0.1.1.
Thus, flutter_test from sdk is incompatible with cached_network_image >=0.4.1.
So, because aicoin depends on both cached_network_image ^0.4.1 and flutter_test any from sdk, version solving failed.

pub get failed (1)
exit code 1

Some version constraints need to be updated or flutter_cache_manager needs an update to support newer dependencies.
I'm going to close because this site is not maintained by the Flutter team.

Flutter (Channel dev, v0.10.0, on Mac OS X 10.13.6 17G3015, locale zh-Hans-CN)
• Flutter version 0.10.0 at /Users/charles/flutter
• Framework revision d954ae6850 (2 days ago), 2018-10-09 16:21:06 -0400
• Engine revision bf377896ff
• Dart version 2.1.0-dev.6.0.flutter-a50dfd6698

Some version constraints need to be updated or flutter_cache_manager needs an update to support newer dependencies.
I'm going to close because this site is not maintained by the Flutter team.

Flutter (Channel dev, v0.10.0, on Mac OS X 10.13.6 17G3015, locale zh-Hans-CN)
• Flutter version 0.10.0 at /Users/charles/flutter
• Framework revision d954ae6850 (2 days ago), 2018-10-09 16:21:06 -0400
• Engine revision bf377896ff
• Dart version 2.1.0-dev.6.0.flutter-a50dfd6698

With "version constraintsI mean thedependencies: ...section inpubspec.yaml`

@gxzlolo please check the bug https://github.com/renefloor/flutter_cache_manager/issues/48 and its workaround.


bugfix:  fix fastjson serialization of time data types

[ ] I have registered the PR changes.

Ⅰ. Describe what this PR did
Detail is in issue 4443
Ⅱ. Does this pull request fix one issue?

fixes #4443
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

@xjlgod add commit log in change/1.5.0:
https://github.com/seata/seata/blob/develop/changes/1.5.0.md
https://github.com/seata/seata/blob/develop/changes/en-us/1.5.0.md

@xjlgod add commit log in change/1.5.0: https://github.com/seata/seata/blob/develop/changes/1.5.0.md https://github.com/seata/seata/blob/develop/changes/en-us/1.5.0.md

I have done it.

https://github.com/seata/seata/pull/4505#issuecomment-1087718470
I have done it.

Codecov Report

Merging #4505 (8ac278f) into develop (53d65bf) will increase coverage by 0.03%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             develop    #4505      +/-   ##
=============================================
+ Coverage      49.35%   49.39%   +0.03%
- Complexity      4073     4075       +2
=============================================
  Files            731      731
  Lines          25465    25475      +10
  Branches        3156     3160       +4
=============================================
+ Hits           12569    12584      +15
+ Misses         11559    11550       -9
- Partials        1337     1341       +4

Impacted Files
Coverage Δ

.../java/io/seata/rm/datasource/DataCompareUtils.java
64.94% <0.00%> (-7.47%)
:arrow_down:

...erver/storage/file/session/FileSessionManager.java
49.01% <0.00%> (-0.66%)
:arrow_down:

...er/src/main/java/io/seata/server/ServerRunner.java
50.00% <0.00%> (ø)

...very/registry/zk/ZookeeperRegisterServiceImpl.java
61.76% <0.00%> (+0.73%)
:arrow_up:

...o/seata/server/coordinator/DefaultCoordinator.java
55.39% <0.00%> (+5.39%)
:arrow_up:

你的分支过老了,我无法帮你合并最新的develop代码

请尽快合并最新seata develop分支代码并推送到此分支,以便我们进行合并pr


add qtum(QTUM)

Hi, now ledger nano s wallet support QTUM, please add QTUM
regards

Please ask the QTUM community to submit a pull request for this.
For an example of what is required, see the commit where nubits network was added. https://github.com/iancoleman/bip39/commit/8dd28f2cff4e1f673f4aa7adc93a7254de72a297

Closed in favour of https://github.com/iancoleman/bip39/pull/144


fluxible example with react-intl?

It would be really useful to have as a starting point / reference. Thank you!

Yup, we will probably do it as part of the fluxible.io doc site, you can follow the issue there: https://github.com/yahoo/fluxible.io/issues/76

Closing this in favor of the fluxible.io one.


Fix differences between release and debug builds

hash_log
From the module docs:
A tool for narrowing down the point of divergence between two executions that should be identical.
Sprinkle calls to `emit(some_hash)` throughout the code.
With `-Dhash-log-mode=create`, all emitted hashes are written to ./hash_log.
With `-Dhash-log-mode=check`, all emitted hashes are checked against the hashes in ./hash_log.
Otherwise, calls to `emit` are noops.

At the moment the only calls to emit are on read/write start/finish in test storage. This is pretty high leverage though, since most decisions end up being committed to disk at some point.
I added a single hash_log run with a low event count to CI to act as a regression test.
Zero grid blocks
Zero grid blocks on init and before every point of reuse.
This fixes several buffer bleeds, including https://github.com/tigerbeetledb/tigerbeetle/issues/404.
We also weren't initializing filter blocks at all so they all converged towards being all set. I don't see any perf improvements from fixing this but our one benchmark atm only stresses compaction, not lookups.
In some places we used to set blocks to undefined, but this appears to have different behavior in debug vs release so I changed these all to zero too.
I also noticed https://github.com/tigerbeetledb/tigerbeetle/issues/419 while poking around in the grid.
Zero filter padding
We explicitly set the padding to zero for index and data blocks, but not for filter blocks. Shouldn't actually be necessary to zero padding for any of them now, but better safe than sorry.
Zero messages
These were set to undefined in debug builds. Given the issues above, I switched this to zero. I also switched an assert about zeroed padding that only ran in debug builds - it should pass in release builds now too. (If we're worried about perf we could put it behind config.verify instead - I mostly just wanted to remove debug vs release differences).

bors r+


How can I get Location data back from a keyboard?

I have a bot that does a series of interaction with the user. The user will first provide some info and as a response to the user reply, my bot asks for location using the button object wrapped inside keyboard object as follows:
bot.on('/test', msg => {

  let fromId = msg.from.id;
  let firstName = msg.from.first_name;
  let reply = msg.message_id;
  //the bot.keyboard() takes first argument as array of arrays
  let markup = bot.keyboard([[bot.button('location','Send your location')]],"once");
  //console.log(markup);
  return bot.sendMessage(fromId, "Send location" , { markup });
});

I cannot figure out where can I put the callback method that will get the location sent by the user. I found out that the "update" event can be listened to. But I guess there is a more convenient way of getting this done. Could you please suggest something on this?

Hello. Just listen location event:
bot.on('location', msg => {
  const {latitude, longitude} = msg.location;
  console.log('Location:', latitude, longitude);
});

Great! Thanks!


docker-compose update

ooking at your docker-compose.dev.yml file, the issue with the Docker build process likely stems from the dockerfile path configuration in the build section for one or more services. Specifically, the line in the backend service configuration:
yaml
Copy code
dockerfile: /Dockerfile.dev
This line specifies an absolute path (/Dockerfile.dev) from the root of the filesystem, which is probably not what you intended. Docker is looking for Dockerfile.dev at the root of your entire file system, not relative to the context directory you specified (./backend).
Correcting the Path
You should remove the leading slash to make the path relative to the context directory. The corrected backend service definition should look like this:
backend:
container_name: backend
environment:
- REDIS_HOST=redis
env_file:
- .env
networks:
- myNetwork
build:
context: ./backend
dockerfile: Dockerfile.dev
volumes:
- ./backend:/backend
entrypoint: sh ./django-entrypoint-dev.sh
restart: always
ports:
- 8000:8000
- 5678:5678
depends_on:
- db
- redis


MudChart Bar - How to change X scale

I was trying to figure out how to change the X scale/range of the  bar Chart
 <MudChart ChartType="ChartType.Bar" ChartSeries="@GetWorkPositionChartSeries(item)" XAxisLabels="@XAxisWPCountersLabels" Width="100%" Height="350px" ChartOptions="WorkPositionCountersChartOptions"
                            />
@*the bar chart**@

Inserting the bar chart data:
private string[] XAxisWPCountersLabels = { "WP Name" };
        private List<WorkPositionCounter> workPositionsCounters;
        private ChartOptions WorkPositionCountersChartOptions =  new ChartOptions()
        {

              InterpolationOption = InterpolationOption.Periodic
        };

        private List<ChartSeries> GetWorkPositionChartSeries(WorkPositionCounter item)
        {
            List<ChartSeries> result = new List<ChartSeries>()
            {
                new ChartSeries()
                {
                    Name = "Ok",
                    Data = new double[] {item.Ok}
                },

                new ChartSeries()
                {
                    Name = "NOK",
                    Data = new double[] {item.NOk}
                }
            };

            return result;
        }

The result with a big scale:

I'm not sure if you can change the graph X scale using the component's properties. Although it's very hacky you can add precedent  empty data fields to one of your chart series entry  (to reduce the spacing between them) and change the  scale via the  mud-charts-bar-series style. The problem you'll face with this is correctly placing the X axis labels in their new positions.
Not sure if this is 100% what you're trying to achieve but here's the example:
https://try.mudblazor.com/snippet/GOmbaraGxFBDIqUq

This will be fixed in the new charts coming out. See #2474

This answers my question #3751.  Thanks


Cannot connect by module name

When I tried to connect to a blob storage module, I got the following error:

Azure.RequestFailedException: Server failed to authenticate the request. Make sure the value of Authorization header is
formed correctly including the signature.
RequestId:13d2ca2e-8be7-41fa-9f1d-f4a9d2f5bf02
Time:2020-04-06T15:51:05.9726238Z
Status: 403 (Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly
including the signature.)
ErrorCode: AuthenticationFailed
The blob storage module name is in lower case. And if I change the module name of BlobEndpoint to the IP address, it works correctly.

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

ID: 07a44a28-a19c-f68e-167c-5e8ad91605e0
Version Independent ID: 33eacdff-4f0a-c543-d8f9-e7b208bab015
Content: Store block blobs on devices - Azure IoT Edge
Content Source: articles/iot-edge/how-to-store-data-blob.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@levi106  Thank you for reaching out to us, this  channel is to improve Azure documentation. Can you please help with the documentation link you are referring, so that we can route you accordingly.

@BharathNimmala-MSFT
The following is the document link:
https://docs.microsoft.com/en-us/azure/iot-edge/how-to-store-data-blob#connect-to-your-blob-storage-module

For modules that are deployed on the same device as where the Azure Blob Storage on IoT Edge module is running, the blob endpoint is: http://:11002/.

@levi106 Thank you for sharing the documentation link, i have assigned the issue to @AshokPeddakotla-MSFT  to further review and take it forward. Thanks

@levi106 As specified, if both are deployed in the same device you will be able to access using the http://:11002/
Could you please confirm, whether both deployed on the same device or different device? also, have you specified the account name and key properly?

Both deployed on the same device.
Working correctly if specifying IP address instead of module id, so I think the account name and key are correct.

@levi106 Thanks for confirming. Let me check this issue internally and update you as earliest. Thanks for your time and patience.

Meanwhile I am assigning this issue to the author @kgremban to review further and update the doc if there are any changes.

@levi106 If you can't use the module name then it's a name resolution issue / DNS issue. Could you please double check on this?

@levi106 Did you get a chance to see the above suggestions? Are you still blocked?

Which DNS setting? I have confirmed that the blob container has been received the request from a blob container's log.

@levi106 Are you making the connection request from another IoT Edge module running on the same device, or a separate application running on the same device?
Using the module name in the endpoint only works for module-to-module communication on the same device because IoT Edge modules are on their own network and can resolve each others' names.
So if you are on a separate application, then what you're describing is the expected behavior and I can update the documentation to be more clear about that.

@kgremban
Another IoT Edge module running on the same device.
The following is the logs on the blob module side:
x-ms-client-request-id:f892b641-509a-4ea4-b4a4-8dcba120fc46
x-ms-date:Fri, 24 Apr 2020 10:47:31 GMT
x-ms-return-client-request-id:true
x-ms-version:2019-07-07
/samplecontainer/samplecontainer
restype:container'.
at Microsoft.Cis.Services.Nephos.Common.Authentication.NephosAuthenticationManager.SharedKeyAuthenticate(String stringToSign, String requestSignature, AuthenticationInformation authInfo) in F:\Storage-XStore\src\XFE\common\src\Authentication\NephosAuthenticationManager.cs:line 1359
at Microsoft.Cis.Services.Nephos.Common.Authentication.NephosAuthenticationManager.AuthenticateImpl(IStorageAccount storageAccount, RequestContext requestContext, NephosUriComponents uriComponents, GetStringToSignCallback getStringToSignCallback, TimeSpan timeout, AsyncIteratorContext1 context)+MoveNext() in F:\Storage-XStore\src\XFE\common\src\Authentication\NephosAuthenticationManager.cs:line 689    at AsyncHelper.AsyncIteratorContextBase.ExecuteIterator(Boolean inBegin) in F:\Storage-XStore\src\XFE\external\AsyncHelper\src\AsyncIteratorContextBase.cs:line 105    --- End of inner exception stack trace ---    at Microsoft.Cis.Services.Nephos.Common.Authentication.NephosAuthenticationManager.EndAuthenticate(IAsyncResult asyncResult) in F:\Storage-XStore\src\XFE\common\src\Authentication\NephosAuthenticationManager.cs:line 452    at Microsoft.Cis.Services.Nephos.Common.Authentication.XFEBlobAuthenticationManager.AuthenticateImpl(IStorageAccount storageAccount, RequestContext requestContext, NephosUriComponents uriComponents, GetStringToSignCallback getStringToSignCallback, TimeSpan timeout, AsyncIteratorContext1 context)+MoveNext() in F:\Storage-XStore\src\XFE\common\src\Authentication\XFEBlobAuthenticationManager.cs:line 251
at AsyncHelper.AsyncIteratorContextBase.ExecuteIterator(Boolean inBegin) in F:\Storage-XStore\src\XFE\external\AsyncHelper\src\AsyncIteratorContextBase.cs:line 105
--- End of inner exception stack trace ---
at Microsoft.Cis.Services.Nephos.Common.Authentication.XFEBlobAuthenticationManager.EndAuthenticate(IAsyncResult asyncResult) in F:\Storage-XStore\src\XFE\common\src\Authentication\XFEBlobAuthenticationManager.cs:line 155
at Microsoft.Cis.Services.Nephos.Common.Protocols.Rest.BasicHttpProcessorWithAuthAndAccountContainer1.ProcessImpl(AsyncIteratorContext1 async)+MoveNext() in F:\Storage-XStore\src\XFE\common\Protocols\REST\src\BasicHttpProcessorWithAuthAndAccountContainerBase.cs:line 2689"
[2020-04-24 10:47:31.216] [info    ] [tid 25] Info: Processing exception: {0}, p0="Microsoft.Cis.Services.Nephos.Common.Authentication.AuthenticationFailureException: The MAC signature found in the HTTP request 'EIgsST+eMsjK4dSxXyfO4dr4cD+M4GnQI+EfXJadef8=' is not the same as any computed signature. Server used following string to sign: 'PUT

@arduppal or @mbialecka could you take a look at this?

@levi106 Do you have the full error message/log? The one you pasted looks trimmed.
This is certainly unexpected that just swapping the IP to module name would trigger the error. Can you share what language and SDK version you are using to connect to blob storage module? In the meanwhile you can try making sure the code uses this api version: 2017-04-17.
It looks like something (SDK?) is creating wrong API endpoint, this looks suspicious: "/samplecontainer/samplecontainer", unless both your account name and blob container are named "samplecontainer"?

@mbialecka
Thanks for the reply.
I have uploaded a sample program to GitHub. And also, I have attached the full container logs:
succeeded.log
error.log

Can you share what language and SDK version you are using to connect to blob storage module?

The SDK version is Azure.Storage.Blobs 12.4.2.

In the meanwhile you can try making sure the code uses this api version: 2017-04-17.

I don't know how to do that, because it seems that there is no option to set the version to 2017-04-17.
If some workaround is needed for .NET SDK, please document it like the Python SDK.

@levi106 What BlobEndpoint are you using? http://blobstoremodule:11002/ or http://blobstoremodule:11002/blobuser ? The logs with the errors show url which is missing the account name.
Logs without error show:
http://<IP_ADDRESS>:11002/blobuser/samplecontainer/telemetry_data_20200508_042747.json
Logs with error show:
http://blobstoremodule:11002/samplecontainer/telemetry_data_20200508_042217.json
Notice the missing "blobuser" in the second case.
I was able to use 12.4.2 SDK both with IP and module name fine. I think the issue may be with connection string itself.

The results were differ whether the url contains an IP address or a host name.
#r "nuget: Azure.Storage.Blobs"
open Azure.Storage.Blobs
open System

let s1 = "DefaultEndpointsProtocol=http;BlobEndpoint=http://blobstoremodule:11002/blobuser;AccountName=blobuser;AccountKey=NqeVzx2M3GfktU/lMpRA6WTxp7XeW5IN2Cq4POOvtyoognWEBwUynd5e4PMqJhzkG2wLffDZABvYzKY7TmrKGw=="
let c1 = BlobContainerClient(s1, "samplecontainer")
printfn "%A" c1.Uri.AbsoluteUri

let s2 = "DefaultEndpointsProtocol=http;BlobEndpoint=http://<IP_ADDRESS>:11002/blobuser;AccountName=blobuser;AccountKey=NqeVzx2M3GfktU/lMpRA6WTxp7XeW5IN2Cq4POOvtyoognWEBwUynd5e4PMqJhzkG2wLffDZABvYzKY7TmrKGw=="
let c2 = BlobContainerClient(s2, "samplecontainer")
printfn "%A" c2.Uri.AbsoluteUri

"http://blobstoremodule:11002/samplecontainer"
"http://<IP_ADDRESS>:11002/blobuser/samplecontainer"

@levi106 I now see the problem. It looks like an issue with the Blob Storage SDK. Please follow up here: https://github.com/Azure/azure-sdk-for-net/issues/10539
I was also able to find a workaround. If you create container client from storage account client the URI seems to be formed correctly:
var client = new BlobServiceClient(connectionString);
var container = client.GetBlobContainerClient(containerName);
// Now container.Uri is formed correctly

I hope this helps.

Thanks @mbialecka
I've made sure your workaround works correctly.

The table storage connection works fine. Only the Blob and Queue storage has the issue. @mbialecka 's approach works fine for the queue storage as well (when used the appropriate classes).

Closing this issue since the related bug that Magdalena opened in the SDK has been resolved
#please-close

@levi106 - When you originally filed this issue, the commands you provided contained an Azure Storage account access key. The key has been edited out of the issue, but we recommend you revoke/rotate account keys to ensure that key cannot be used.


[WIP] Support ResNet

I start with finding what caffe functions are missed in chainer from warnings CaffeFunction class leaves for each size of ResNet caffe models.
$ python -c "from chainer.links import caffe
caffe.CaffeFunction('ResNet-50-model.caffemodel')" 2>&1 | awk 'NR % 2 == 1 {print $11}' | sort | uniq
BatchNorm
Eltwise
Scale
Softmax

$ python -c "from chainer.links import caffe
caffe.CaffeFunction('ResNet-101-model.caffemodel')" 2>&1 | awk 'NR % 2 == 1 {print $11}' | sort | uniq
BatchNorm
Eltwise
Scale
Softmax

$ python -c "from chainer.links import caffe
caffe.CaffeFunction('ResNet-152-model.caffemodel')" 2>&1 | awk 'NR % 2 == 1 {print $11}' | sort | uniq
BatchNorm
Eltwise
Scale
Softmax

Here I found the following four caffe functions should be implemented.

BatchNorm
Eltwise
Scale
Softmax

To be done

Make CaffeFunction class interpret the caffe functions used in ResNet.
Make it possible to use ResNet in chainer/examples/modelzoo.

While Caffe's softmax layer has engine parameter that would specify implementation to compute softmax, is using Chainer softmax function's default parameter use_cudnn=True enough as SoftmaxWithLoss does?

Do we have any information about Caffe's scale layer other than:

https://github.com/BVLC/caffe/blob/master/src/caffe/proto/caffe.proto

I think use_cudnn is appropriate for the substitute of engine parameter.

Is it the document of ScaleLayer ?
http://caffe.berkeleyvision.org/doxygen/classcaffe_1_1ScaleLayer.html#details

Thanks! I missed it.

rel #930

Now I want to confirm the basic approach to support Caffe's ScaleLayer, especially the difference of 'broadcasting' between numpy and Caffe.

https://github.com/BVLC/caffe/blob/master/src/caffe/proto/caffe.proto#L1030
http://docs.scipy.org/doc/numpy-1.10.1/user/basics.broadcasting.html

Please review the change in https://github.com/pfnet/chainer/pull/1028/commits/89aba641f418ea6b3f1aaecf17e08158d91ebe18.
The basic approach is that, for example, think about the following bottoms and axis scale parameter.
Shape of bottom[0]: 100x3x40x60
Shape of bottom[1]: 3x40
axis              : 1

In numpy manner, bottom[1] is broadcasted as following, which makes no sense and violates numpy's broadcasting rule.
Bottom[0] (4d array): 100 x 3 x 40 x 60
Bottom[1] (2d array):            3 x 40

So we first get another shape for bottom[1] with axis parameter for broadcasting in numpy manner. Please see shape_for_broadcasting_in_numpy function in https://github.com/pfnet/chainer/pull/1028/commits/89aba641f418ea6b3f1aaecf17e08158d91ebe18.
Shape of bottom[0]    : 100x3x40x60
Shape of bottom[1]    : 3x40
axis                  : 1
New shape of bottom[1]: 3x40x1

Then broadcast the new bottom[1] in numpy manner.
Bottom[0]     (4d array): 100 x 3 x 40 x 60
New bottom[1] (3d array):       3 x 40 x  1
Result        (4d array): 100 x 3 x 40 x 60

Finally we multiply the broadcasted bottom[1] to bottom[0] in element-wise.

I think a good technique.
Please continue this PR.

Thanks.

ScaleParameter in caffe.proto is not found in caffe_pb2.py, which seems to be added in https://github.com/BVLC/caffe/commit/081690709e4a199824f433cc196c55c47731073f on Jan 23. Do we need recompile the latest caffe.proto for py2, since #974 supports it for py3 only? If so, how can I do that?

Oh, we need to generate both caffe_pb2.py and caffe_pb3.py from a newer proto file. I think a newer proto file breaks compatibility.

Now I catch up the situation that the caffe_pb2.py and  caffe_pb3.py in #974 are generated from maybe the same old version of caffe.proto, which has incompatibility with at least caffe rc3 version, causing some change of interpretation of ConvolutionLayer in CaffeFunction class and its test.

Do you think it is beneficial if we extract _ScaleChain, _ScaleFunction, _BiasLink, _BiasFunction from caffe_function and register them as independent Chain / Function / Link? If we do it, we need to reconsider their interfaces as they depend on Caffe's prototxt (for example _ScaleChain.__init__ takes blobs as arguments).

Please write test cases of Function.Maximum where the shapes of two input variables are inconsistent.

Do you think it is beneficial if we extract _ScaleChain, _ScaleFunction, _BiasLink, _BiasFunction from caffe_function and register them as independent Chain / Function / Link? If we do it, we need to reconsider their interfaces as they depend on Caffe's prototxt (for example _ScaleChain.init takes blobs as arguments).

I'm not sure clear use cases for them besides interpreting Caffe models, but we can and I suppose it would make no harm. I will do it.

Please review this PR for due to v1.9.0 release. While some small stuff remains, I suppose it is implemented and verified as far as it may be merged to master.
Remaining things

Tests for ScaleLayer's helper functions and classes.
Handling old layer names not in V1LayerParameter.

How verified

CI pass
evaluate_caffe_net.py script runs on resnet with causing no errors.

py2 on CPU
py3 on CPU
py2 on GPU, finally out of memory on my environment(2GB)

input some pictures to get fairly good prediction results with ILSVRC-2012 labels.

py2 on CPU

How verified
Is it the way you verified your code? Or is it the requirement for the reviewer (myself) on how to verify the code?

Is it the way you had verified your code? Or is it the requirement for the reviewer (myself) on how to verify the code?

The way I did.

The way I did.

OK I understand it.

Could you remove [WIP] from the PR title if it is merge-ready?

I removed "[WIP]" prefix of the PR title. While some reviewed points remain, they can be fixed after v1.9.0 release.

I've found that maximum function's backwards test has some instability with FP16, trying to fix its test data to avoid it.

It seems to be tempered, though not away.


net: panic if too many DNS servers.

If the DHCP server provides more servers than smoltcp's DNS_MAX_SERVER_COUNT, panic here https://github.com/smoltcp-rs/smoltcp/blob/main/src/socket/dns.rs#L170
hardcoded 6 here https://github.com/embassy-rs/embassy/blob/a1fce1b554bea8cad7f87073748145aaeca634f8/embassy-net/src/lib.rs#L699

we should truncate instead of panic.

I mean it explicitly mentions, that this panics under the condition, which you described. However, introducing a check and returning a Result might be more ideal, than just panicking.

Agree about handling this gracefully


update mesos-go

We need this commit https://github.com/mesos/mesos-go/commit/10ceb4fb01222c59f313fec154a6af275eadb6c1 to support IP instead of hostname for the mesos master uri

ping @jimenez @tnachen

ah cool, lgtm!


openvpn/networkmanager: OpenVPN cipher lookup failed

Issue description
I am unable to configure the Cipher field of an openvpn connection in networkmanager. The dropdown is greyed out, with the text "OpenVPN cipher lookup failed".  This causes problems because OpenVPN defaults to a very weak cipher (BF-CBC) that most modern vpn servers reject.
Steps to reproduce
On a system with networking.networkmanager.enable = true set and plasma5 installed, use kde5-nm-connection-editor to create an openvpn connection.  On the VPN tab of the connection editor, click Advanced..., and then click on the Security tab in the Advanced OpenVPN Properties window that pops up.  The top item should read Cipher: and the dropdown will be greyed out with the error message mentioned above.

Technical details

System: NixOS 17.03 at 12a39478fd79ee514a76e593f40345f319d9f5a1
Nix version: 1.11.8
Nixpkgs version: 12a39478fd79ee514a76e593f40345f319d9f5a1

temporary workaround: use nmcli connection edit <name> to manually edit the vpn.data property and add cipher = <whatever> to it


bug: Getting error whenever trying to delete a plugin through :Lazy

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10
Operating system/version
MacOS Sonoma 14.2
Describe the bug
A plugin is not getting deleted completely. Gets install everytime you open a file in nvim.

Steps To Reproduce
Go to :Lazy
Click X to remove a plugin
It goes to a "not installed" list
Remove its config lines present in the nvim config files.
When open a file with neovim it reinstalls again.
When try to uninstall it again, if you press X when it is in the not installed list, it gives some error (PFA ss below.)
Expected Behavior
As soon as i press x, it should just be gone, as its config files are also deleted (~/.config/nvim/). The ones present in ~/.local/share/nvim are still there. Even if I delete the files from there, the plugin gets reinstalled.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

You're trying to delete a plugin that is not a directory. It's literally in the error.
Are you creating symlinks yourself or anything like that?

No, I havent created any symlinks. How can I delete those plugins then?

When open a file with neovim it reinstalls again.

This can only happen when it's referenced somewhere in your config.
Are you using something to manage your dot files? That automatically creates symlinks or something like that?

Is it because bufferline is a default lazyvim plugin and hence present in a lot of file under ~/.local/share/nvim path?
But it is no where present in my config under ~/.config/nvim/lua

You should have mentioned you use LazyVim. LazyVim the distro is not the same as lazy.nvim the plugin manager.
Check the LazyVim docs on how to disable plugins. Just deleting it with :Lazy is not how that works

Ahh I see, need to put them in disabled.lua file putting enable = false.
Thanks man! You the legend! :)

enabled, not enable

Got it sir ! btw folke I know you are an awesome programmer, just wanted to know I am in college now, it is good to learn data structures and algorithms to be a better developer and is learning c++ also a good thing to do given everybody is going after python these days? I know very offtopic question but your little guidance might clear my many doubts.
Thanks in advance

Learning any programming langages and indeed the theory on data structures and algorithms is great :)


solve migration issues

[ ] To support multiselects values of interactive elements should be strings (rule 27 in rule_mapping.py)

should be fixed in #431


Input lag (only characters)

The menu buttons etc. react with the speed thex should react with but when you touch a character on a keyboard it takes some time to appear in the text line and for the colour of the character to change. I have no idea why.

I have the exact opposite problem. If I hold the stylus over the key for more than ~0.1 seconds, the character is printed multiple times...

Yeah, I've noticed that too when I was testing earlier today. I will look into it.

Hm, I thought I could fix it using the WAIT constant, but the program doesn't seem to care. It's my first time coding back in C again for some time, maybe that's why I'm not seeing why that doesn't fix the issue.


[OpenCL] Fix type casting error

Faced situation when generated OpenCL kernel contained the following if
condition:
if (uint4(...) && (int4(...) == int4(...)))

In this case, got the following error:
"can't convert between vector values of different size ('uint4' and 'int attribute((ext_vector_type(4)))')"
Added casts for binary ops. But it was necessary to modify CastFromTo
and add new method CastTo. Because with CastFromTo the following
code was generated:
if (uint4(...) && (convert_uint4(int4(...)) == convert_uint4(int4(...))))

But the OpenCL compiler still generated the same error.
This is why added new method CastTo. In this method we don't check the
current type of op and just add cast to a new type.
Finally the following code will be generated:
if (uint4(...) && convert_uint4(convert_uint4(int4(...)) == convert_uint4(int4(...))))

Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

Sorry, closed and opened this PR several times, due to on our branch I saw some problems with generated kernels. But all these problems were specific for our branch, because we have modified the codegen. This PR should work on the tvm/main.
@csullivan, @masahi, @comaniac please, review it.


feat!: add option to assign a collision layer on collision generation

This PR adds an additional field to the PendingConvexCollision to set collision layers. I realized that setting default collision is needed only for the generated collision. In all other cases user can define needed collision layer explicitly. Closes #217.

Ho, thanks for the contribution.
What is the advantage to have it as a field of the PendingConvexCollision instead of inserting the component directly?

What is the advantage to have it as a field of the PendingConvexCollision instead of inserting the component directly?

PendingConvexCollision creates collision recursively for scene meshes. If I just insert CollisionLayers to the entity with PendingConvexCollision - it won't work.

@jcornaz So this parameter works like current rigid_body parameter. The specified layers will be inserted into every mesh entity in spawned scene.

@jcornaz We can, but I don't think this behavior is very obvious. It will also be inconsistent with the body_type parameter. I would introduce a small breakage for the benefit of a more nicer API.

I want to try as hard as I can to avoid breaking changes, no matter how "small" it is.
But I agree with your point about how obvious it would be. I only partially agree with your point about consistency, yes it would be inconsistent, but we may fix that differently by changing how the body type is defined instead (and deprecating the rigid_body field in PendingCollisions)
Maybe we could introduce a new type that would explicitly hold the configuration for that feature. Maybe something like:
struct CollisionGenerationConfig {
  body_type: RigidBodyType,
  layers: CollisionLayers,
}

One could configure the behavior of the PendingConvexCollision with that struct.
And we would make sure to keep the field private (or mark the struct #[non_exhaustive]) so that we can extend the configuration in the future.

Or, we can add a new component that replaces the existing PendingConvexCollision and deprecate the old one.
Obviously, we should try to not redo our mistake to have the field public, so that we can extend it later.

Maybe we could introduce a new type that would explicitly hold the configuration for that feature. Maybe something like:

Could you explain this a bit more? Not sure if I get it.

Or, we can add a new component that replaces the existing PendingConvexCollision and deprecate the old one.

I understand your point about breakages, it's a good approach. We should always think about how to do it without breakages. Sometimes it even leads us to better ideas.
But in this particular case I don't see a lot of difference between deprecated struct and a newly added field. On my CI warnings are marked as errors. It's a trivial change, I can understand what needs to be changed from the compilation error, I don't need a deprecation message. Bevy itself (for which this plugin is written) is also making breakages. So I would expect breaking changes at early development stage.

But why CollisionGenerationConfig contains RigidBody? We have it in PendingConvexCollision. But as to end user, this behavior makes the API less clear...

We could deprecate the rigid_body in PendingConvexCollision. The advantage is consistency. Basically I made that proposition to address that point you made:

It will also be inconsistent with the body_type parameter

Which I agree with, hence my attempt to suggest a solution that addresses that concern.

Deprecating the PendingConvexCollision and using a new one with builder patter looks also less consistent to me. Because in Bevy bundles usually plain structures.

Yes, I agree. But as I mentioned in a previous message, I disagree with how bevy treats breakages, and I don't want to replicate what I consider to be a mistake in bevy. Using plain structures with all public fields leads to the necessity of breaking changes, which I don't want.
In other words: Yes it is inconsistent with bevy. But I think that avoiding breaking changes is more important than being consistent with bevy.

 Because it is deprecated doesn't mean you cannot use it. If one is using it, they can migrate it their leisure.
If if is a breaking change, you at least need to spend the cognitive effort to understand what is the new API

That's true for massive changes. Not migrating to a new API can be useful when it is totally different and the transition results in a change in the application structure. In this case delaying transition worth it. But how it could be useful with minor change?

I agree that it is even more important for massive changes. But I don't think it becomes "false" for small changes. And small/big is kinda subjective. Because we don't know from where they update. If a user jumps from version 1.0.0 to 10.0.0 they may be a lot of "small" breaking changes, which together makes it big.

I would migrate to a new API if that easy.

Yes, me too. But I believe it should be up to the user to make that decision. I don't want to impose it on them.

So I would sacrifice compatibility for API sanity.

Me too... kinda. Let's say that I may agree to make a breaking change if absolutely required for the quality of the API.
But I don't think it is the case here. Potentially we can make the API even better than it would be by adding a field in PendingConvexCollisions.
I don't see deprecation as hurting the API quality. I consider that as a graceful removal from the official API. Existing users are well informed that it is no longer supported and new users don't have to see it at all (we can and should hide it from the docs).
For this PR, I suggest the following course of action:

Create a new CollisionShapeGeneration component, that is meant to be the successor of PendingConvexCollision

The content is a replication of the existing PendingConvexCollision (plus layers)
with private fields
builder-like way of setting the fields.

Deprecate and hide from the docs PendingConvexCollision

For the system implementation, we can consider many approaches. I would suggest implementing From<PendingConvexCollision> for CollisionShapeGeneration.

For each entity with CollisionShapeGeneration: Execute the collision shape generation normally.
For each entity with PendingConvexCollision and without CollisionShapeGeneration:

Convert the PendingConvexCollision into a  CollisionShapeGeneration and use it to execute the collision shape generation normally.

We may also do that in multiple PRs and even share the load. For example, I could introduce CollisionShapeGeneration and deprecate of PendingConvexCollision without any change of feature. And then you can add support for collision layers.
I am still very open for the design of the API and it's implementation. Only when it comes to breaking changes, I am quite settled, that this feature doesn't need nor deserve an API breakage.

Yes, that's close to the idea I had indeed, and that sounds good to me. It is probably the best solution. I think we can go with that.

I will update the PR today after work.

Done! I also added Default implementation for easier creation.

Should I provide new method as well?

No, default is enough.

You can #[allow(clippy::type-complexity)]

Thanks!


Update Tutorials to v2.0.0-rc4

cc @Swader if you want to review

Very good, thanks!

Added @jimmychu0807 as a reviewer because I made some changes to some front-end code.

update to rc4 looks clean and A+


Switch Absorption to an attribute

Cleaner for the tooltip for gold armor and the enchantment, and better for mod compat

Did in 1.2.0

Did in 1.2.0


Register package

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/49160
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.1 -m "<description of version>" dc105f969db2001de35174e32f794e17081320a0
git push origin v0.3.1

Also, note the warning: This looks like a new registration that registers version 0.3.1.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/49160
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.1 -m "<description of version>" dc105f969db2001de35174e32f794e17081320a0
git push origin v0.3.1

Also, note the warning: This looks like a new registration that registers version 0.3.1.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.


[Bug]: GPUs cannot be used with Tainted Nodes

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

The difference is that I usually add a Taint to my nodes called "notebooksonly". I did add it to the GPU node, because:
A) that node has no taint by default
B) I had noticed random pods landing on it and hogging it for nothing
However, as soon as I add the taint, a few minutes later, the drop down disappears.
When I remove the taint, the drop-down re-appears.

From the downstream issue https://issues.redhat.com/browse/RHODS-4769
Expected Behavior
GPUs should work for both using tolerations & not using tolerations.
Steps To Reproduce
See the current behaviour / downstream ticket.
This is likely related to the Prometheus query omitting results -- but that is just a guess. Might be impacted by #573 and supporting of scaling (which could change the "show the dropdown" logic -- may not work with unscalable nodes that have tolerations)
Workaround (if any)
No response
OpenShift Infrastructure Version
No response
Openshift Version
No response
What browsers are you seeing the problem on?
No response
Open Data Hub Version
2.3.0

Relevant log output
No response

As it is, tolerations added manually to a Notebook definition are "erased" when you start the Notebook through the UI. This is incompatible with multiple pools of GPUs that you have to taint to properly schedule specific workloads, or just with standard management of workloads placement through taints.
We should either:

Leave the tolerations in the Notebook CR alone, or only reconcile the ones we provide access to trough the UI, like GPU request  = nvidia.com/gpu toleration.
Or provide a mechanism in the UI to fully managed tolerations on Notebooks.

So today we have a toleration for nvidia.com/gpu (code link) -- this should be covered if you taint your node with the same. We also have the "NotebooksOnly" (configurable) default toleration for Notebooks if you check out the cluster settings as an admin -- but that's not tied to (Nvidia) GPU, that's additional.
I would imagine this is handled already to some degree 🤔
In the work for accelerators, I imagine this will be more flexible and seamless for what is being tainted/tolerated... effectively this should be done, no?

See https://github.com/opendatahub-io/odh-dashboard/issues/1450

More specifically the CR we will create to allow customization for accelerators (https://github.com/opendatahub-io/odh-dashboard/issues/1371)

This is no longer valid due to Habana work - moving to closed after talking to Gage.  Please reopen with questions if there are any misunderstandings.


Replaces double.INFINITY with DateTime.infinity.

Against https://github.com/dart-lang/angular_components
Replaces double.INFINITY with DateTime.infinity.
v/ v1.0.0

I'll also note that this doesn't speak to the nature of infinity.

published the fixed version: https://github.com/dart-lang/dart2_fix/releases/tag/1.0.0%2B1


feat(react-query): clarify cli command explanations

Overview

PR Checklist

[x] I did below actions if need

I read the Contributing Guide
I added documents and tests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.08%. Comparing base (ebe1c8e) to head (30154c1).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1185   +/-   ##
=======================================
  Coverage   78.08%   78.08%
=======================================
  Files          65       65
  Lines         607      607
  Branches      121      121
=======================================
  Hits          474      474
  Misses        123      123
  Partials       10       10

Components
Coverage Δ

@suspensive/utils
47.16% <ø> (ø)

@suspensive/react
100.00% <ø> (ø)

@suspensive/react-dom
100.00% <ø> (ø)

@suspensive/react-native
100.00% <ø> (ø)

@suspensive/react-query
72.18% <ø> (ø)

@suspensive/react-query-4
0.00% <ø> (ø)

@suspensive/react-query-5
0.00% <ø> (ø)

@suspensive/jotai
0.00% <ø> (ø)

@suspensive/cache
98.23% <ø> (ø)

@suspensive/react-image
80.39% <ø> (ø)

Update docs please after please

Could you please explain what you mean in more detail?

The documentation update was planned for a new PR after this one. Should I include it in this PR instead?

The documentation update was planned for a new PR after this one. Should I include it in this PR instead?

I think that It's up to your decision

I think that It's up to your decision

I have updated the documentation and included it in this PR!


Update CMakeLists

Add CONFIGURE_DEPENDS to check for new source files on build
Replace literal target name with variable
Use new include command

Works great! Thank you :)


ungoogled-chromium 92.0.4515.159 crashes with wayland flags

Describe the bug
~
❯ chromium --enable-features=UseOzonePlatform --ozone-platform=wayland
[281477:281477:0913/134642.439438:ERROR:cursor_loader.cc(115)] Failed to load a platform cursor of type kNull

(chromium:281477): Gtk-WARNING **: 13:46:42.481: Theme file for capitaine-cursors-white has no directories
[281513:281513:0913/134642.514926:ERROR:gpu_init.cc(441)] Passthrough is not supported, GL is egl
[281513:281513:0913/134642.519897:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[281477:281477:0913/134642.591404:ERROR:platform_shared_memory_region_posix.cc(47)] Descriptor access mode (0) differs from expected (2)
zsh: trace trap (core dumped)  chromium --enable-features=UseOzonePlatform --ozone-platform=wayland

~
❯ which chromium
/etc/profiles/per-user/cole/bin/chromium

~
❯ readlink -f $(which chromium)
/nix/store/ilhrxff0xz1dfh3jlr8hr7yvngyj4l0w-ungoogled-chromium-92.0.4515.159/bin/chromium

cc: @primeos

seems like this might just be upstream: https://bugs.chromium.org/p/chromium/issues/detail?id=1246834

Looks like the fix is available in Chromium beta (tested 41dbc0a9954d852ef1d33ec5c79d64fe3cc84b8c)

Aaaand in the stable https://github.com/NixOS/nixpkgs/commit/a39908a7cb0e01c7d3c2f8a9199b14de6209f687

Does this also apply to electron? I hit the same thing and have to use Xwayland instead.

It seems it does, at least I'm in the same boat. But for electron_17 with version 17.3.1 a fix is in sight: https://github.com/NixOS/nixpkgs/pull/166587 and upstream: https://github.com/electron/electron/pull/33499

I guess we can close this one

Yes, seems like it :)

Does this also apply to electron?

https://github.com/NixOS/nixpkgs/issues/158175 ;)


Backport file leak fixes

Closes #16705

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test and merge

Your PR is queued because #16827 is being built.

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.


Bump Jest v29

Explanation

References

Changelog

@metamask/package-a

: Your change here
: Your change here

@metamask/package-b

: Your change here
: Your change here

Checklist

[ ] I've updated the test suite for new or updated code as appropriate
[ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[ ] I've highlighted breaking changes using the "BREAKING" category above as appropriate

don't this we need this anymore


Support custom error message for mask validation

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@evshi this is already done with #841


Bad permissions on google_apputils.egg-info

ls -la google_apputils.egg-info
total 56
drwxr-x---   9 schwehr  eng   306 Feb 29  2012 .
drwxr-x---  11 schwehr  eng   374 Feb 29  2012 ..
-rw-r-----   1 schwehr  eng   247 Feb 29  2012 PKG-INFO
-rw-r-----   1 schwehr  eng  1032 Feb 29  2012 SOURCES.txt
-rw-r-----   1 schwehr  eng     1 Feb 29  2012 dependency_links.txt
-rw-r-----   1 schwehr  eng   175 Feb 29  2012 entry_points.txt
-rw-r-----   1 schwehr  eng    23 Feb 29  2012 namespace_packages.txt
-rw-r-----   1 schwehr  eng    53 Feb 29  2012 requires.txt
-rw-r-----   1 schwehr  eng     7 Feb 29  2012 top_level.txt

Missing r-x and r-- for dir and files.  So python's install process can write
into a tree as one user (e.g. root) and block other setup.py's from working.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

bigquery-2.0.12/table_formatter.py
sudo -u fink-bld [ENV] sh -c /tmp/fink.4ugD2
perl -pi -e "s/'google-api-python-client==.*',//" setup.py
perl -pi -e "s/'oauth2client==.*',//" setup.py
/sw/bin/python2.7 setup.py build
Traceback (most recent call last):
  File "setup.py", line 22, in <module>
    use_setuptools()
  File "/sw/src/fink.build/bigquery-py27-2.0.12-1/bigquery-2.0.12/ez_setup.py", line 74, in use_setuptools
    import pkg_resources
  File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 2825, in <module>
    add_activation_listener(lambda dist: dist.activate())
  File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 710, in subscribe
    callback(dist)
  File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 2825, in <lambda>
    add_activation_listener(lambda dist: dist.activate())
  File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 2257, in activate
    self.insert_on(path)
  File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 2364, in insert_on
    self.check_version_conflict()
  File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 2401, in check_version_conflict
    nsp = dict.fromkeys(self._get_metadata('namespace_packages.txt'))
  File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 2251, in _get_metadata
    for line in self.get_metadata_lines(name):
  File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 1219, in get_metadata_lines
    return yield_lines(self.get_metadata(name))
  File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 1211, in get_metadata
    return self._get(self._fn(self.egg_info,name))
  File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 1326, in _get
    stream = open(path, 'rb')
IOError: [Errno 13] Permission denied:
'/sw/lib/python2.7/site-packages/google_apputils-0.3.0-py2.7.egg-info/namespace_
packages.txt'
### execution of /sw/bin/python2.7 failed, exit code 1
### execution of /tmp/fink.4ugD2 failed, exit code 1

What version of the product are you using? On what operating system?

fink mac osx 10.8

Please provide any additional information below.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 15 May 2013 at 9:37

We won't be fixing issues directly in this repository.  Development of this library has been moved to https://github.com/abseil/abseil-py.  If it can be reproduced there, please open an issue in the abseil-py project.


Circular redirects for nl da sv flow translations

Is there an existing issue for this?

[X] I have searched the existing issues

Which content section have you found a bug in?
Learn
What kind of bug is it?
Broken link
What happened?
the lang code in the redirect_url should be en and not translation-specific. My bad 😳
Anything else?
will fix after lunch before next build!

Fixed by PR #1207


Data Mapping

As a NAD administrator, I want map provided fields from the record to NAD required/defined fields, so I can process record.
AC:

Explore technical complexity for P3 and possible solutions.

PR has been merged with the Initial design of the crosswalk/column mapping logic which uses yaml configuration files. To complete this work, we want to consider the points below. The points labeled (Minor) are not required for the MVP, however, (Major) labeled points are.

Need some UI components to allow the user to upload a config or create a config visually. (Major)
Decide on how many configs will we allow a data producer to create to serve different source data schemas and do we want to allow the application to store historical updates of a config. (Minor)
As of today, we are storing the configs locally within the application but do we want to store them in an external storage system such as S3 instead. (Minor)

Hi @akuny @JuliaCardis @VRagulina @seckb: I added the flows for the data mapping UX in this prototype. As mentioned in slack, I'd love to walk through this with the team to discuss, answer any questions and discuss a concern about the proposed flow. I'll grab us time next week!
Thanks!


Hotkey grouping

It would be nice to group hotkeys by section or functionality, something like this:

+1

+1

+1
or I hope hotkey service provide to swap keyset.

Sorry for the delay here, I'm trying to clean up old tickets. If this is important to you guys, please open a PR for it.  Thanks!

Hey @chieffancypants, any chance you could merge #205 any time soon? Thanks for this great module!


ok: RuntimeException with message 'Too many arguments, expected arguments "command".'

Very close to being able to use this wonderful tool, any help much appreciated.
I run: ./artisan magic, a Chrome is being controlled by automated test software browser window comes up, dev console shows:
Magic Test started

I log in, dev console looks ok, no errors. Nothing in network tab relating to magic-test-laravel or testing generally.
If I select text & press Ctrl + Shift + A the dialogue box pops up saying assertion generated.
I go into psy shell, type ok but get the message:
RuntimeException with message 'Too many arguments, expected arguments "command".'
in:
Psy Shell v0.10.12 (PHP 8.1.2 — cli)
No major changes are made to the ExampleTest.php which has the simplest initial test method in it:
    public function testBasicExample()
    {
        $this->browse(function (Browser $browser) {
            $browser->visit('/')
                //    ->assertSee('Laravel');
                ->magic();
        });
    }

What could be wrong? Full output here:
*** Starting a 🧙 Magic Test session...
PHPUnit 9.5.13 by Sebastian Bergmann and contributors.

Psy Shell v0.10.12 (PHP 8.1.2 — cli) by Justin Hileman
New version is available (current: v0.10.12, latest: v0.11.1)

*** Welcome to your 🧙 Magic Test session! ***

* To make a assertion press Ctrl + Shift + A on your browser.
* Type ok to magically write it to your test file.
  (make as many assertions as you wish)
* Type finish to finalize and save your test file.
* Type exit to leave.

💡 Tip: Do not close your browser window before finalizing this session here.
>>> ok
RuntimeException with message 'Too many arguments, expected arguments "command".'

Using https://chromedriver.storage.googleapis.com/97.0.4692.71/chromedriver_mac64_m1.zip for the installed browser Version 97.0.4692.99 (Official Build) (arm64)
./artisan tinker works fine for the same project.
./artisan dusk returns OK (1 test, 1 assertion) when I switch commenting on magic() and assetSee('Laravel').

I'll try it on my M1 tomorrow morning with those versions

Seems to be related to PsySH maybe...

So I have just run:
composer create-project laravel/laravel magictest
cd magictest
composer require laravel/dusk
./artisan dusk:install

This downloads various ChromeDrivers to ./vendor/laravel/dusk/bin/, including: chromedriver-mac-arm, which, when run, shows
Starting ChromeDriver 97.0.4692.71 (adefa7837d02a07a604c1e6eff0b3a09422ab88d-refs/branch-heads/4692@{#1247}) on port 9515
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.

Then ...
composer require magic-test/magic-test-laravel --dev

from the last command I get the response:
Using version ^0.14.0 for magic-test/magic-test-laravel
./composer.json has been updated
Running composer update magic-test/magic-test-laravel
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires magic-test/magic-test-laravel ^0.14.0 -> satisfiable by magic-test/magic-test-laravel[v0.14].
    - magic-test/magic-test-laravel v0.14 requires psy/psysh ^0.10.4 -> found psy/psysh[v0.10.4, ..., 0.10.x-dev] but the package is fixed to v0.11.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require magic-test/magic-test-laravel:*" to figure out if any version is installable, or "composer require magic-test/magic-test-laravel:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

If I use the -W flag I get:
composer require magic-test/magic-test-laravel --dev -W
Using version ^0.14.0 for magic-test/magic-test-laravel
./composer.json has been updated
Running composer update magic-test/magic-test-laravel --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Lock file operations: 3 installs, 1 update, 0 removals
  - Locking magic-test/magic-test-laravel (v0.14)
  - Downgrading psy/psysh (v0.11.1 => v0.10.12)
  - Locking spatie/backtrace (1.2.1)
  - Locking spatie/laravel-package-tools (1.11.0)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 3 installs, 1 update, 0 removals
  - Downgrading psy/psysh (v0.11.1 => v0.10.12): Extracting archive
  - Installing spatie/laravel-package-tools (1.11.0): Extracting archive
  - Installing spatie/backtrace (1.2.1): Extracting archive
  - Installing magic-test/magic-test-laravel (v0.14): Extracting archive
Package swiftmailer/swiftmailer is abandoned, you should avoid using it. Use symfony/mailer instead.
Generating optimized autoload files
[...]
> @php artisan vendor:publish --tag=laravel-assets --ansi --force
No publishable resources for tag [laravel-assets].
Publishing complete.

Updating .env to show APP_URL=http://magictest.test and running ./artisan dusk I get OK (1 test, 1 assertion).
Commenting out ->assertSee('Laravel');, adding ->magic(); & running ./artisan magic shows the browser window.
If I select text & press Ctrl + Shift + A the dialogue box pops up saying assertion generated.
Then ...
>>> ok
RuntimeException with message 'Too many arguments, expected arguments "command".'

Thanks again for all your help. By the way do you know that the Sponsor this project section shows no ways of sponsoring?

Any news on this? I assume it will be an issue for all Laravel installs ...

Thanks in anticipation ...

@rightwayround I've fixed the psysh dependency (haven't updated it yet), but the command error doesn't seem to be limited to magic test. See: https://laracasts.com/discuss/channels/laravel/runtimeexception-with-message-too-many-arguments-expected-arguments-command
Looking into it..

@rightwayround i'm getting that on a clean laravel install, too

@rightwayround so it's a known issue: https://github.com/bobthecow/psysh/issues/704
Using symfony/console:6.0.2 should fix it for you. I'll tag a release using the newest PsySH version

@rightwayround v0.15 has been tagged

Thanks for your efforts, but I am still having the same issue.
I rm -rf the magictest folder, redo the actions I took above & see the following:
➜  magictest ./artisan magic
*** Starting a 🧙 Magic Test session...
PHPUnit 9.5.13 by Sebastian Bergmann and contributors.

Psy Shell v0.11.1 (PHP 8.1.2 — cli) by Justin Hileman

*** Welcome to your 🧙 Magic Test session! ***

* To make a assertion press Ctrl + Shift + A on your browser.
* Type ok to magically write it to your test file.
  (make as many assertions as you wish)
* Type finish to finalize and save your test file.
* Type exit to leave.

💡 Tip: Do not close your browser window before finalizing this session here.
>>> ok
RuntimeException with message 'Too many arguments, expected arguments "command".'

My composer.json shows "magic-test/magic-test-laravel": "^0.15.0",.
My composer.lock shows:
[...]
           "require": {
               "psy/psysh": "^0.10.4|^0.11.1",
[...]
   "packages": [
[...]
       {
           "name": "psy/psysh",
           "version": "v0.11.1",
[...]

I have just been looking here (https://github.com/bobthecow/psysh/issues/705) and can see it's an upstream problem. I will pester those guys. If you have any bright ideas on what I could do as a work around let me know? Otherwise thanks for everything.
Also, fix your sponsorship link!

… is it working for you @mateusjatenee?
Are you using valet?

@rightwayround have you tried this? https://github.com/bobthecow/psysh/issues/705#issuecomment-1028522039

@mateusjatenee yes I did try that. I get the following - which is why I asked whether you were using valet:
➜  magictest composer global require symfony/console:6.0.2

Changed current directory to /Users/rightwayround/.composer
./composer.json has been updated
Running composer update symfony/console
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires symfony/console 6.0.2, found symfony/console[v6.0.2] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - mnapoli/silly 1.7.3 requires symfony/console ~3.0|~4.0|~5.0 -> found symfony/console[v3.0.0, ..., v3.4.47, v4.0.0, ..., v4.4.37, v5.0.0, ..., v5.4.3] but it conflicts with your root composer.json require (6.0.2).
    - laravel/valet v2.18.9 requires mnapoli/silly ^1.0 -> satisfiable by mnapoli/silly[1.7.3].
    - laravel/valet is locked to version v2.18.9 and an update of this package was not requested.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Running composer global update laravel/valet shows:
Changed current directory to /Users/rightwayround/.composer
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Installing dependencies from lock file (including require-dev)
Nothing to install, update or remove
Generating autoload files
17 packages you are using are looking for funding.
Use the `composer fund` command to find out more!

hey! running in to this while running in sail. after trying (https://github.com/bobthecow/psysh/issues/705#issuecomment-1028522039) it seems to return the same RuntimeException

Could throwing cash at this make the problem go away

@rightwayround I cannot replicate your error. Can you send me a list of the packages you have installed and their versions?


Clean up create service headings

This PR cleans up the hierarchy and spacing of headings through the create service flow. Today there are a few examples where the headings are inconsistent, the spacing is off, or it is the wrong type of heading.
Each tab should follow a H2 > H3 > H4 rule and related headings/objects should visually be grouped together.
Some before and after examples:
Before - Three H2 headings, inconsistent with other tabs

After - One H2 heading, three H3s

Before - Two H2 headings and some minor spacing issues

After - One H2 heading, two H3s, spacing improved

Before - One H2 heading, three H3s

After - One H2 heading, one H3, two H4s

cc @ashenden @jfurrow for visual review.

@jfurrow I couldn't quite figure this one out. There's an empty div here which adds some unwanted space above the add constraint button. How do I remove this?

@leemunroe Thanks for this PR!
I just pushed a commit to handle the extra FormGroup component. It was used to display errors, but rendered an empty FormGroup when no errors were present. Now it omits the FromGroup entirely when no errors are present.

@leemunroe - thanks for the PR! 💯  :1st_place_medal:


INPUT_PARAMETER_NAME is breaking in entrypoint.sh

I have done everything like described in the docs and i am getting an error:
##[warning]Unexpected input 'parameter_name', valid inputs are ['entryPoint', 'args', 'ssm_parameter', 'prefix', 'simple_json', 'jq_filter']
The parameter_name is unused in the entrypoint.sh, but it is still being checked for it's existence.

If i declare "parameter_name" in the action, the action is breaking
If i don't declare "parameter_name" in the action, the entrypoint.sh is breaking with the error "Set SSM parameter name (parameter_name) value."

Hey, thanks for reporting! I think I see the issue, haven't been using this for a long time since I don't have AWS access anymore. I will have to create a new account, fix those thing and test it out, but in the meantime, as a quick workaround, can you try to set both ssm_parameter and parameter_name with same values and see if it will work?

I just fixed the bug, please use ssm_parameter from now on, I updated README with proper information, sorry for the confusion. I'll close this issue, feel free to reopen it if needed!


How to register a bot on Discord

I want to register a new Discord bot to run https://github.com/zmoog/go-bender/ on my laptop during development, so I can keep running the main bot on k8s.

Navigate to https://discord.com/developers/applications and log in using your Discord user.
Click on New Application (for dev, I'll Flexo as application and bot name)
Click on Settings > Bot
Enable to following intents: presence, server members, and message content.

Quick test:


Redirect www. to the base URL

Set up app services to support multiple custom host names. We use a map of host name to the index of the corresponding certificate secret name to support reusing certificates for multiple host names.
Only the first host name listed is set up to work with Verify, so it is assumed that the rest redirect to that one.
Redirect www. to the base URL. This is untested because we don't have an environment to easily test it on.
To do before merging

[ ] Manually deploy to development and confirm everything still works (including Verify). It deploys fine to a tmp environment, but that doesn't support actually using the domains.
[ ] Copy the wildcard certificate to the production Key Vault (or request a new one for www. and use that).

Note: this is untested for multiple domains as the only environment we have that can support that is production.

 Add www. to the URL

I have a general question: will the way we do this when we have the actual service.gov.uk domain the same as here? i.e. within the app code? Is it something we can configure further up the stack? Traditionally I'd expect this to be done in the web-server configuration, but not sure how things fit together here in Azure land.

@erbridge I've made some tweaks to this based on the change I made in #400, which should simplify redirection a bit. Can you have a look when you get back?