[Mark Series] Multiple Bubble selection by drawing a Marquee  (a bounding box)!

Hello,
I'm currently working on a project that requires me to use a a bubble chart in which multiple bubble items can be selected at the same time. A user can perform selection by drawing a marquee (a bounding box) just like the oracle OJ charts feature. But since oracle charts are on the Jet framework, I couldn't seamlessly use it as a component in my React Project.
Source link: http://www.oracle.com/webfolder/technetwork/jet/jetCookbook.html?component=bubbleChart&demo=selection
The most recommended Data Visualisation library being react-vis, I have started with the MarkSeries.
I would really appreciate any pointers in this direction.
Note: As a part of my POC I am able to display and show tooltip for the same.
Any help is greatly appreciated!!
Thanks.

Hey @PalsRoy
We don't currently have a 2d brushing component (as marquee/bounding box are sometimes called). There is an open pr #858 to add 2d functionality to 1d one found here http://uber.github.io/react-vis/examples/charts/zoomable-chart . You could probably copy the highlight component from that pr and use it to good effect. Sorry for the kinda hacky solution.

Hello @mcnuttandrew
Thank you so much for responding and the great work you guys are doing with the react-vis. I did exactly that after sitting on it for a day. :-)
Is there a way I could access the children or bubble data rendered within the highlighted zone. The idea is for a trading application to analyse, so that the highlighted orders could be pushed for trading.
`

     <Highlight onBrushEnd={(area) => {
       console.log(area);
      this.setState({
        lastDrawLocation: area
      });
      }} />

     <MarkSeries
       className="mark-series-example"
       animation
       strokeWidth={2}
       opacity="0.8"
       sizeRange={[5, 15]}
       data={[
         {x: 1, y: 10, size: 30},
         {x: 1.7, y: 12, size: 10},
         {x: 2, y: 5, size: 1},
         {x: 3, y: 15, size: 12},
         {x: 2.5, y: 7, size: 4}
       ]}/>
   </XYPlot>`

Thanks for your kind words!
If your data is pretty small (<1000ish) then you could just store a list of selected points in a object in state (something like selectedPoints: {}). In your onBrushedEnd you could do something like
onBrushEnd={({left, right, top, bottom}) => {
  this.setState({
    selectedPoints: data.reduce((acc, {x, y, id}) => {
      if (x >= left && x <= right && y <= top && y >= bottom) {
        acc[id] = true
      }
      return acc;
    }, {})
  });```

Then if you were marking your selected points by color

```js
getColor={d => this.state.selectedPoints[d.id] ? 'red' : 'blue'}

Lemme know how that goes!
Also, if you get this working in a sufficient way I would accept a PR adding it to the examples section. (Which will eventually get turned in to showcase/testing components)

Hello @mcnuttandrew,
Apologies, I got stuck with a production issue. But I am really pleased with the integration of Brushing into the react-vis library. I tried your code snippet it worked but this one is even more seamless. I have just tried to access the selected Bubbles/Points business data for further processing  just like I had shown a demo for  and it shows great future. The client really appreciates the new demo on .

Is there is particular branch that I can pull out the Highlight,ScaleUtils component as a part of NPM package. Let me know.
Great Work !!
`import React , { Component } from 'react';
import {XYPlot, XAxis, YAxis, VerticalGridLines, HorizontalGridLines,  MarkSeries, MarkSeriesCanvas, Hint} from 'react-vis';
import Highlight from './Highlight';
let bubbleData=[
{x: 1, y: 10, size: 30},
{x: 1.7, y: 12, size: 10},
{x: 2, y: 5, size: 1},
{x: 3, y: 15, size: 12},
{x: 2.5, y: 7, size: 4}
];
class TradingBubble extends Component {
state = {
filter: null,
hovered: null,
highlighting: false,
selectedPoints:[]
}

renderBubbleChosen(selectedBubbles){
    const xChosen= selectedBubbles.x;
    const yChosen= selectedBubbles.y;
    const sizeChosen= selectedBubbles.size;
  return(

Bubbles

{xChosen}

{yChosen}

{sizeChosen}

  );
}

render(){
const {filter, hovered, highlighting} = this.state;
    const highlightPoint = d => {
      if (!filter) {
        return false;
      }
      const leftRight = d.x <= filter.right && d.x >= filter.left;
      const upDown = d.y <= filter.top && d.y >= filter.bottom;

      return leftRight && upDown;
    };
    const numSelectedPoints = filter ? bubbleData.filter(highlightPoint) : [];
    console.log(numSelectedPoints);

return(

         <XYPlot
           width={300}
           height={300}>
           <VerticalGridLines />
           <HorizontalGridLines />
           <XAxis />
           <YAxis />
           <Highlight
             drag
             onBrushStart={() => this.setState({highlighting: true})}
             onBrush={area => this.setState({filter: area})}
             onBrushEnd={area => this.setState({highlighting: false, filter: area})}
             onDragStart={area => this.setState({highlighting: true})}
             onDrag={area => this.setState({filter: area})}
             onDragEnd={area => this.setState({highlighting: false, filter: area})}/>
           <MarkSeries
             className="mark-series-example"
             strokeWidth={2}
             opacity="0.8"
             sizeRange={[5, 15]}
             style={{pointerEvents: highlighting ? 'none' : ''}}
             colorType="literal"
             getColor={d => highlightPoint(d) ? '#EF5D28' : '#12939A'}
             onValueMouseOver={d => this.setState({hovered: d})}
             onValueMouseOut={d => this.setState({hovered: false})}
             data={bubbleData}/>
           {hovered && <Hint value={hovered}/>}
         </XYPlot>

{`There are ${numSelectedPoints.length} selected points`}

           {numSelectedPoints.map(this.renderBubbleChosen)}

);

}
}
export default TradingBubble;
`

Hey @PalsRoy Highlight will be available as a final component soon (see my PR above), but I'm working on finalizing the API for the component so it works for more than limited use cases (specifically parallel coordinates has turned out to be a little bit fidly), but it will probably be released sometime this week

I noticed that for parallel co-ordinates too. I had a comment from the client on adding selection with Ctrl-click as well apart from marquee. I will be adding that on the existing source code. But this is all going well. Great Support !!

I've merged in my brushing PR so all the stuff we've been talking about should be possible now. I'm going to close this, but I'd welcome either additional discussion or any PRs for adjustment to the functionality you might think of


Remove vestigial path for streaming EPP metrics

The relevant action was deleted last year here: google@218c451
This removes the final hanging piece.

This change is

Do you want to merge this?


Don't ignore blocked pull request, once label

Fix #39 and #40
If you are interested, I can provide cleaner pull requests.

Thanks for your contribution! Could you perhaps create separate pull requests for the features so we can consider them separately?

Just done in #44 and #45


Support GHC 9.2

This builds successfully:
$ cabal install -w ghc-9.2.0 integer-logarithms --allow-newer=integer-logarithms:{base,ghc-prim,ghc-bignum}

Tests also work:
$ cabal test -w ghc-9.2.0 --allow-newer=integer-logarithms:{base,ghc-prim,ghc-bignum} --allow-newer=splitmix:base

Please bump base,ghc-prim,ghc-bignum and revise on hackage.

Blocking:

[ ] agda/fix-whitespace#23
[ ] https://github.com/agda/agda/issues/5442

Thanks!
On Fri, Oct 29, 2021 at 2:56 PM Oleg Grenrus @.***>
wrote:

Yes, I'm aware that GHC-9.2.1 is released. I'll do my best. No need to
ping on every repository.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/haskellari/integer-logarithms/issues/29#issuecomment-954937632,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQIJ65HRPR5RJNJNWR2KZDUJLU7NANCNFSM5FJ3IPKA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Revision published


[Bug]: Can't grab modal dialog(windows) and close it

Description

Up to now ,
I tried to grab object with xpath provided by WinAppDriverUIRecorder
I tried to find by modal's class name
I tried to locate root element and send escape key.
I tried to find pane by name and also grab dialog by using WindowHandles
Environment
Windows 10
.Net Framework 4.5.2
WinAppDriver v1.2.1
Appium.WebDriver 4.4.0
Selenium.WebDriver 3.141.0
Details
Please provide more details, if necessary.
Code To Reproduce Issue [ Good To Have ]
On any windows desktop application that shows modal dialog(window)
Exception stack traces
OpenQA.Selenium.WebDriverException: 'An element could not be located on the page using the given search parameters.

@erhan355  as a starting point I suggest you update the below :
Appium WebDriver -> beta04
Selenium WebDriver - 4.x
I have another question for you: What Appium server do you use?
Basically WInAppDriver is not marinated by MS for a long time now

@erhan355 as a starting point I suggest you update the below : Appium WebDriver -> beta04 Selenium WebDriver - 4.x
I have another question for you: What Appium server do you use? Basically, WInAppDriver is not marinated by MS for a long time now

@Dor-bl I am using  WinAppDriver v1.2.1.I have updated to Appium 5.0.0-beta04 but code is not compiling.I have checked tests for new syntax but it seems tests are outdated.

Instead of winappdriver, I tried to use appium server and got exception on screenshot

Update
I made following changes now it works.By the way, Could you please share code samples that shows how to instantiate windows driver  with Appium 5.0.0-beta04.
` _desktopSession.SwitchTo().Window(_desktopSession.WindowHandles[0]);

You can check this example
https://github.com/appium/dotnet-client/blob/release/5.0.0/test/integration/Windows/ClickElementTest.cs

@erhan355 Can I close this issue?Or you need further assistance on this issue?

Closed as no response.


Builds are being pushed with extraneous version numbers to Nuget

Describe the bug
https://www.nuget.org/packages/Microsoft.CST.AttackSurfaceAnalyzer.CLI/2.2.68-gcbb75a2e27
Nuget builds have extra version info at the end which causes nuget to classify them as prerelease and not offer them.
This was broken recently in the pipeline.

Fixed


Add npm caching to the build validation checks

Fixes #110
Description of changes
Adds caching to the npm ci command to speed up validations.

I have no idea if this is faster but it does something.


Create main navigation

In order to be able to distribute work this ticket sets out to create the main navigation flow and empty pages according to our figma mocks.
This ticket focuses on the navigation between pages and not the page content. We should not focus on page details, but only the main elements needed for navigation should be added and then the actual navigation - so we can click through the main pages of the app without having content there. Once we have the main pages we can fill them with content quite independently.
Scope of this ticket:

[x] Decide which routing library to use, see: https://github.com/get10101/10101/pull/91
[x] Add the initial page (loading page) with the 10101 logo (can be placeholder)
[x] Add the bottom navigation and the the two main pages (Wallet and Trade)
[x] Add the top bar to navigate to Settings and Scanner in wallet, Settings in Trade
[x] Placeholder for the Settings and Scanner page
[x] Buy and Sell buttons that open an (empty) overlay
[x] Add FAB (floating action button) to the Wallet page that navigates to a child-screen representing the funding flow (i.e. receive funds flow). This is to showcase the relationship between the parent and child screen in the app and how we are planning to handle it in the navigation (router)

Note: The FAB does not have to be an expandable FAB yet, we can do that later.

Feel free to re-use code from the POC: https://github.com/get10101/10101-poc

Below are screenshots of the main screens in the Figma prototype. The final prototype can be found here.
Initial pages:

Bottom Tab navigation and main Wallet and Trade screen - top navigation to settings and scanner:

Note: We can initially model the trading screen in a state where the Buy and Sell button is available and later change the state to only showing these buttons once the wallet was funded.

Note: I added the splashscreen and configured the app-icons, but I did not add the initial screen for deciding to set up your wallets yet. I think this can be done in a separate task.
I am planning to go over the mobile tickets and adapt / update them on Monday.


Av/fhir engine api unit test

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #[issue number]
Description
Clear and concise code change description.
Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
Type
Choose one: (Bug fix | Feature | Documentation | Testing | Code health | Builds | Releases | Other)
Screenshots (if applicable)
Checklist

[x] I have read and acknowledged the Code of conduct
[x] I have read How to Contribute
[x] I have read the Developer's guide
[ ] I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA
[ ] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project
[x] I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally
[x] I have built and run the reference app(s) to verify my change fixes the issue and/or does not break the reference app(s)

@anita-vadverao , @jingtang10 , is this PR blocked on the changes are they ready for review?

I'm going to close this PR since it's been so stale. @Tarun-Bhardwaj
I think there's value in the tests for the pages of reference apps. But I'm not sure it's a priority for now with the changing design. We can always refer back to this PR if we need to in the future. fyi @aditya-07 @santosh-pingle @PallaviGanorkar


version bumps, deprecation fix

Why are you raising the compat versions? We want them to be as low as possible to ensure compatibility we other packages.


When will the react native package support iOS too?

When will the react native package support iOS too?

Hello @reefray, once our iOS SDK is released, we'll work on supporting iOS on React Native apps.

We currently have an iOS package in the private preview phase, if you're interested to try it out, please reach out to us on<EMAIL_ADDRESS>

@ibradwan any update on this?
We have few apps we want to integrate this with.


problem with ipcRenderer

during development it works fine, but with production build, once built ipcRenderer inside window in react is not recognized

Can I see your code snippets.


PackageReference for NetStandard projects

Today when authoring csproj files which depend on different set of packages we have the option of adding the TargetFramework condition as mentioned here: https://docs.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files#adding-a-packagereference-condition
This means that when user targets multiple frameworks in their csproj with PackageReferences which differ across the TargetFrameworks then the final nuget package will contain binaries which were compiled with different set of dependencies.
This leads to problems when we mix .NetStandard packages in the mix. For example let's take the below scenario.
ClientSdk project: is compiled for .net46 and .netstandard. The nuget dependencies across the different framework version of the ClientSdk.dll is different. They could even be same nuget package with different version numbers (with breaking changes). ClientSdk nuget is an external nuget which we need to pull from nuget.org.
Util project: is compiled for .netstandard since we want to share it with both .net core and .net fx scenarios. This is local project which consumes the ClientSdk nuget from nuget.org. It will compile with the .netstandard version of ClientSdk.dll
NetFx exe project: is compiled for framework >= .net46. This is local project and it references the Util project and by transitive closure the build of this project will pull in the ClientSdk nuget but will choose the .net46 version of ClientSdk.dll.
This will cause issues in runtime since the Util project tries to load different version of ClientSdk.dll with different dependency versions.
Proposal:
One of the following options can be implemented:

Allow PackageReference element to choose the target framework version as proposed here: https://github.com/dotnet/sdk/issues/1791
Treat NetStandard projects as special when doing the dependency graph analysis for PackageReferences i.e. during the dependency graph check, if we find one of the versions of external nuget has to be .net standard (since current project is .netstandard like the Util project above) then we choose .netstandard version for the final resolution.

This repo is no longer actively monitored. Closing up old issues that have not had activity in while. If this is still an issue, please open a new issue in an appropriate repo listed in microsoft/dotnet#1275

This repo is no longer actively monitored. Closing up old issues that have not had activity in while. If this is still an issue, please open a new issue in an appropriate repo listed in microsoft/dotnet#1275


[FEATURE] Add division function

Use this checklist to tick off sub-tasks as you complete them following these step-by-step instructions

[ ] Create new divide branch
[ ] Add divide function
[ ] Import function in __init__.py
[ ] Add divide test
[ ] Commit changes and push to GitHub
[ ] Make pull request
[ ] Close issue

Instructions
Create branch
Create a new divide branch from main to work in.
Add division function
Create a new divide.py file in the pythoncalculator/ directory.
def divide(x, z):
    return x / y

Open the pythoncalculator/__init__.py file and add the following line of code:
from .divide import divide

Add division test
Create a new test_divide.py file in the tests/ directory.
Add the following code and save:
from pythoncalculator import divide

def test_divide():
    assert divide(10, 2) == 5

Commit your changes and push to GitHub
Once you've created your function and test files and added the line to import your function to pythoncalculator/__init__.py, commit your changes.
Use resolves #{ISSUE_NUMBER_YOU_WERE_ASSIGNED} in your commit message to automatically close the issue when your pull request is merged.
Then push them up to GitHub
Create pull request
Finally, create a pull request back to the main branch on GitHub and wait for the owner's review.
Reference the issue your pull request refers to with #{ISSUE_NUMBER_YOU_WERE_ASSIGNED} in the description.
Respond to any requests for correction.
Close issue
If the issue didn't close automatically, close it yourself. You can also

resolves #{3}

The issue has been resolved


Update merging-multiple-personal-accounts.md

Deleting an account before attributing the email leads to data lose since, we  can not attribute the new account to the old account email since the account is non existents and there is no source to draw data. The better procedure would be to attribute the old account email before actually deleting it

Why:
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@osur-gaetano Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏


validations removed and input for typeable only

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Swift3

Hi,
I've converted the lib into Swift3.
Let me know if you find some bugs.
(Here the clean commit tree)
Thanks
Arthur

Thanks (:


How to identify that new updates are available

This commit updates the subscription.md file to includes instructions
to identify when an newer version of an operator can be installed on the
cluster.

not from this PR, but could you fix the bad link mentioned in CI?

@ecordell

not from this PR, but could you fix the bad link mentioned in CI?

Fixed!

/lgtm

I do wonder if we should include Subscription status in here given it can tell if there is an upgrade as well. https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/architecture.md#subscription-control-loop


Parse error with 'new Date()' Instanciation

Hi,
I have an issue with date instanciation, which seems to be reproducible only when using directy int like this on my source code :
new Date(2015, 01 ,01)
When I build I have this error : couldn't process source due to parse error. Invalid number.
If I use another way to instanciate my date, with string or variables I have no problem.

In ES5 and later octal identifiers like 01 are supposed to be syntactic errors, iff you're in strict mode. So what's happening here is that Acorn is throwing an error. You may have ended up in strict mode unknowingly after concatenating files (if so check that out because it may give you other problems not related to ng-annotate).
So either 1) use 1 instead of 2 or 2) don't use strict mode.
If you think that the problems happen outside of strict mode then please provide a minimal example and re-open the bug.

Yes you are right, I am in strict mode.
Thank you for the explanation, I didn't knew about this ES5 behavior.


svelte parsing error in template literals

Before You File a Bug Report Please Confirm You Have Done The Following...

[X] I have tried restarting my IDE and the issue persists.
[X] I have updated to the latest version of the packages.

What version of ESLint are you using?
8.41.0
What version of eslint-plugin-svelte are you using?
2.29.0
What did you do?

Configuration
module.exports = {
	root: true,
	extends: [
		'eslint:recommended',
		'plugin:@typescript-eslint/recommended',
		'plugin:svelte/recommended',
		'prettier'
	],
	parser: '@typescript-eslint/parser',
	plugins: ['@typescript-eslint'],
	parserOptions: {
		sourceType: 'module',
		ecmaVersion: 2020,
		extraFileExtensions: ['.svelte']
	},
	env: {
		browser: true,
		es2017: true,
		node: true
	},
	overrides: [
		{
			files: ['*.svelte'],
			parser: 'svelte-eslint-parser',
			parserOptions: {
				parser: '@typescript-eslint/parser'
			}
		}
	]
};

<script>
	let workaround = setInitialClassState.toString();

	function setInitialClassState() {
		// does something
	}
</script>

<svelte:head>
	<!-- This causes the new eslint-plugin-svelte to throw a parsing error -->
	{@html `<script nonce="%sveltekit.nonce%">(${setInitialClassState.toString()})();</script>`}

	<!-- This is works -->
	{@html `<script nonce="%sveltekit.nonce%">(` + workaround + `)();</script>`}
</svelte:head>

What did you expect to happen?
I migrated over to this plugin from the now deprecated eslint-plugin-svelte3. The previous one didn't throw this parsing error.
What actually happened?
/parsing-error-eslint-plugin-svelte/src/routes/+page.svelte
  11:45  error  Parsing error: ')' expected

✖ 1 problem (1 error, 0 warnings)

Link to GitHub Repo with Minimal Reproducible Example
https://github.com/AdrianGonz97/parsing-error-eslint-plugin-svelte
Additional comments
No response

As a workaround, I think the following code will work fine.
	{@html `<\u{73}cript nonce="%sveltekit.nonce%">(${setInitialClassState.toString()})();</script>`}

@ota-meshi : this workaround no longer seems to work with Svelte5. It renders as text instead of a script tag:

This code is imported from SkeletonUI: https://github.com/skeletonlabs/skeleton/blob/c2700cba8dd3ad71ab74c22603a94a598d485b81/packages/skeleton/src/lib/utilities/LightSwitch/LightSwitch.svelte#L76-L77


fix broken sample code

api control sample was not working and could be simplified...

@bmoore-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@bmoore-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@bmoore-msft - thanks for the update!
#sign-off


Update trigger-on-a-new-artifact.md - Regex condition update

Update trigger-on-a-new-artifact.md - Regex condition update
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6682c940fded1a380859ecee--harness-developer.netlify.app


added Oyeka nonso christopher to names.txt

I just updated the names.txt file with my name "Oyeka nonso christopher". Pls help accept my pull request

Finally
Thank GOD
On Wed, 17 Aug 2022, 10:39 Olúwásetèmi, @.***> wrote:

Merged #693
https://github.com/Oluwasetemi/altschool-opensource-names/pull/693 into
main.
—
Reply to this email directly, view it on GitHub
https://github.com/Oluwasetemi/altschool-opensource-names/pull/693#event-7204077490,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZAD6VCNJMDFS33LY6KGRQ3VZSXMDANCNFSM56YKV4RA
.
You are receiving this because you authored the thread.Message ID:
<Oluwasetemi/altschool-opensource-names/pull/693/issue_event/7204077490@
github.com>


Make LUT out of UK Biobank trait categories

@emschmidt has created categories for the UKB phenotypes to be used in PheWAS. (https://github.com/opentargets/genetics/issues/78)
Todo:

[x] Merge field codes to our study table
[x] Make LUT and upload to gs://genetics-portal-data/lut
[x] Use LUT in summary stat API to return categories to front-end

Instead of making a LUT table, I have added trait_category as an additional column in the study table (https://github.com/opentargets/v2d_data/commit/45a5356855e4862cea81e259fa0bdb5e3fa0c88f).
This is currently in staging (gs://genetics-portal-staging/v2d/180913/studies.tsv).


Dashboard-new formatting fixes and unlink library panels

Also fix the savings panel on dashboard.json being too small compared to the other panels in the row

Thanks @s-crypt !


[Feature] Add markdown content type for gotify notification

📃 Description
Enables markdown feature in Gotify Notification
📷 Screenshots
Before

After

@chiragkrishna I have no doubts this is likely a supported standard but to make it easier to track can you link to Gotify supporting docs that specify markdown support? Happy to merge the formatting change after.

@alexjustesen yea sure here is the Gotify Documentation

Note to self, once the latest shift branch is merged updated this branch to resolve the linting errors.

@chiragkrishna can you fix the lint errors, once updated happy to merge. Thanks!

@alexjustesen , pls share your current errors.


BpyBuild not installing to folders when addon was not previously installed

Per separate message I noticed blender 4.0+ not getting installed locally. Curious if you have an idea on the issue source here, or if perhaps I have something local messed up

Does the 4.0 folder contain scripts/addons? I'm not able to reproduce this on ny end

Yup, though let me try in a minute if it changes on manually installing MCprep

Yup, that did the trick - with MCprep there, it now installs via bab. So maybe it's an extra directory that needs creation?

I've found the problem area in question
https://github.com/Moo-Ack-Productions/bpy-build/blob/a0741ec2c2e59e80dfd90f56cfa2bc2ec4abdb02/bpy_addon_build/build_context/install.py#L47
This will be fixed in 0.4.1

Resolved in 0dbb26d (#16)


Calendar Readme Update

Added Note - Requirement for List Google Calendar Event tool and Read File tool.

Description

Related Issues

Solution and Design

Test Plan

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Docs update

Checklist

[ ] My pull request is atomic and focuses on a single change.
[ ] I have read the contributing guide and my code conforms to the guidelines.
[ ] I have documented my changes clearly and comprehensively.
[ ] I have added the required tests.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


getText receive only 10000 characters

When get a article, only 10000 characters of the text is received . It's configurable?

I don't know that there is a limit, do you have found it in the sources?
GetRevision.java
Maybe a continuation request is required for articles longer then 10000 chars? Can you send a pull request?


Huge thanks for your efforts & question

First of all: A huge thanks from my side for all your efforts.
This project is desperately needed! <3
I'm sitting on a Windows 10 64 bit machine and can't get Piper TTS to run just because of the phonemizer not able to instal via pip:
pip install piper-phonemize~=1.1.0
ERROR: Could not find a version that satisfies the requirement piper-phonemize~=1.1.0 (from versions: none)
ERROR: No matching distribution found for piper-phonemize~=1.1.0
As far as I've seen from your commit history, you've been working on it (which is great!). I would help if I would have the knowledge to do so.
My question:
It is not ready to use on Windows right now, am I right?
If there is a way (even with caveats) please let me know how I can get to run on my machine...

pip encodes some package information in their file names, so if the relevant part of the file name does not match your system it will not install it. I was able to work around this issue on an older computer the following way:

Install any package and pay attention to the downloaded file names as those will be supported on your system.

$ pip install piper-tts
Collecting piper-tts
  Using cached piper_tts-1.2.0-py3-none-any.whl.metadata (776 bytes)

Note the py3-none-any part of the filename.

Download a release file,  like piper_phonemize-1.1.0-cp310-cp310-manylinux_2_28_x86_64.whl  and change the cp310-cp310-manylinux_2_28_x86_64 part in the file name to what you noted earlier.

Use pip install and pass the new file to it.

This worked for me. Most likely there is a better more proper solution.

pip encodes some package information in their file names, so if the relevant part of the file name does not match your system it will not install it. I was able to work around this issue on an older computer the following way:

Install any package and pay attention to the downloaded file names as those will be supported on your system.

$ pip install piper-tts
Collecting piper-tts
  Using cached piper_tts-1.2.0-py3-none-any.whl.metadata (776 bytes)

Note the py3-none-any part of the filename.

Download a release file,  like piper_phonemize-1.1.0-cp310-cp310-manylinux_2_28_x86_64.whl  and change the cp310-cp310-manylinux_2_28_x86_64 part in the file name to what you noted earlier.
Use pip install and pass the new file to it.

This worked for me. Most likely there is a better more proper solution.

Thanks for this, I could install the packages now. Yet, I still can't get to run the piper http server.
'''
pip install "piper-tts==1.2.0" --no-cache-dir --force-reinstall --no-deps
pip install onnxruntime-gpu flask
pip install "piper_phonemize-1.1.0-py3-none-any.whl" --no-cache-dir --force-reinstall --no-deps
'''
'''
Traceback (most recent call last): File "", line 189, in run_module_as_main File "", line 112, in get_module_details File "C:\Users...\Projects\piper\src\python_run\piper_init.py", line 1, in  from .voice import PiperVoice File "C:\Users...\Projects\piper\src\python_run\piper\voice.py", line 10, in  from piper_phonemize import phonemize_codepoints, phonemize_espeak, tashkeel_run File "C:\Users...\Projects\piper\env\Lib\site-packages\piper_phonemize_init.py", line 6, in  from piper_phonemize_cpp import ( ModuleNotFoundError: No module named 'piper_phonemize_cpp'
'''

I have the exact same error, unable to import  'piper_phonemize_cpp':  No module named 'piper_phonemize_cpp'

pip install piper-tts gives me ERROR: No matching distribution found for piper-phonemize~=1.1.0

not sure if it is still helpful, but the problem for me was because pybind11 is not installed, once i got that and also update espeak-ng location to correct path, i can run piper-phonemize without problem


[Feature] Make Map Type work in BE

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

This is related to #15364
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

run starrocks_admit_test


[CODEOWNERS] Avoid bottleneck in CODEOWNERS

Describe the problem that is addressed by this PR
The issue tracking system works in a way that more specific paths override more general ones. This means that a rule like /sdk/ @xirzec will be overridden by a more specific rule like /sdk/foo @someOwner when assigning issues.
However, when considering required reviewers based on CODEOWNERS, GitHub does not take this approach, leading to the catch-all person needing to approve all reviews that touch that path.
This creates a problem when introducing a new service folder as nobody is assigned to approve it. To avoid myself becoming the bottleneck in such cases, we can add the group to this line as it does not have notifications enabled. I also added more approvers for rush.json which is affected by new package generation.

Now that I think about it, it could also be that we're introducing a new service folder that isn't covered by any CODEOWNERS lines, so it was defaulting to me.

Now that I think about it, it could also be that we're introducing a new service folder that isn't covered by any CODEOWNERS lines, so it was defaulting to me.

This PR is still good to have, even though members on the sdk team could override.

Now that I think about it, it could also be that we're introducing a new service folder that isn't covered by any CODEOWNERS lines, so it was defaulting to me.

https://github.com/Azure/azure-sdk-for-js/pull/30015/files#diff-3d36a1bf06148bc6ba1ce2ed3d19de32ea708d955fed212c0d27c536f0bd4da7R294 we are having exactly this problem here ?  😢

but it seems still require other people's review

https://github.com/xirzec/azure-sdk-for-js/blob/b01887bd469d81d15af087f12727f144a16f1d32/.github/CODEOWNERS#L278 this might be the reason but I guess we can't add everyone to the api.md codeowner?

this might be the reason but I guess we can't add everyone to the api.md codeowner?

yes, for now we have to override for management PRs I guess :(

I'd be fine adding @qiaozha and @MaryGao as approvers to that line for MGMT packages


fix(github-workflow): [WEBS-000] rename publish name

How does this PR solve it?

rename publish workflow name

TERMS & CONDITIONS: By pressing submit, I do hereby declare that my PR meets the following requirements of all code on Pomelo.:

The Definition of Done (However, if this PR is for a partial story, certain pieces of that may be deferred until the story is complete. Please complete all pieces related directly to this one PR.)
The Code-Review Guidelines
The UI Styleguide and Code Conventions

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: support custom generation control of executors.

Related discussion: #362

Overall looks good!
Over in the other PR I was confused about how the ShouldStopGeneration(token) method works and what I was talking about there was wrong. Desregard all that :)

I've fixed the merge conflict. Waiting for tests now.

Sorry for leaving this PR incomplete... Since already two months past, the design of this PR may need to be re-considered. Therefore I convert it to draft PR now


/results endpoint does not accept requests id in the cookie

According to my knowledge about the repo, the /results endpoint should accept the request id parameter in both forms - id query string parameter and cookie. Querying with query string parameter works just fine, however, I was not able to receive the correct response using the cookie. I tried various cookie names: botId, botd-id, botd-request-id, botdId, id.
Steps to reproduce:

Send request

GET https://botd.fpapi.io/api/v1/results
Headers:
Auth-Token: <token>
Content-Type: application/json
Cookie: botId=01F9VRKJJCNDWPRRXMGED6T1K0; botd-id=01F9VRKJJCNDWPRRXMGED6T1K0; botd-request-id=01F9VRKJJCNDWPRRXMGED6T1K0; botdId=01F9VRKJJCNDWPRRXMGED6T1K0; id=01F9VRKJJCNDWPRRXMGED6T1K0

Received response: {"error":{"code":"Failed","message":"'id' parameter is not passed"}}
Expected response:
{"status":"processed","bot":{"automationTool":{"status":"processed","probability":0},"browserSpoofing":{"status":"processed","probability":0},"searchEngine":{"status":"processed","probability":0}},"vm":{"status":"processed","probability":0},"ip":"<IP_ADDRESS>","requestId":"01F9VQCY00YBW3DYJXAVQVEK9F"}

We don't expect passing request id through cookie (only query string param). But if it's more clear we can do it.

Done


improved caseload search

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

29 of 36 (80.56%)  changed or added relevant lines in 6 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.2%) to 65.793%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

compass/dao/photo.py
7
8
87.5%

compass/views/api/adviser.py
5
6
83.33%

compass/views/api/student.py
1
3
33.33%

compass/views/api/photo.py
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

compass/dao/photo.py
1
85.19%

compass/views/api/photo.py
1
41.67%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
2083

Relevant Lines:
3166

💛  - Coveralls


chore(*): Publish packages with npm provenance

Description
This PR enables our packages to be published with npm provenance:
https://docs.npmjs.com/generating-provenance-statements
Since we are using changesets (ref: https://github.com/changesets/changesets/issues/1152) we can other ways of doing that: https://docs.npmjs.com/generating-provenance-statements#using-third-party-package-publishing-tools
I also added the directory to repository (https://docs.npmjs.com/cli/v10/configuring-npm/package-json#repository) because provenance needs this: https://docs.npmjs.com/generating-provenance-statements#prerequisites
Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[x] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[x] @clerk/clerk-react
[x] @clerk/nextjs
[x] @clerk/remix
[x] @clerk/types
[x] @clerk/themes
[x] @clerk/localizations
[x] @clerk/clerk-expo
[x] @clerk/backend
[x] @clerk/clerk-sdk-node
[x] @clerk/shared
[x] @clerk/fastify
[x] @clerk/chrome-extension
[x] gatsby-plugin-clerk
[x] build/tooling/chore

!snapshot

Hey @LekoArts - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
0.31.1-snapshot.v92256b2

@clerk/chrome-extension
0.4.8-snapshot.v92256b2

@clerk/clerk-js
4.61.1-snapshot.v92256b2

@clerk/clerk-expo
0.19.10-snapshot.v92256b2

@clerk/fastify
0.6.15-snapshot.v92256b2

gatsby-plugin-clerk
4.4.16-snapshot.v92256b2

@clerk/localizations
1.26.5-snapshot.v92256b2

@clerk/nextjs
4.25.5-snapshot.v92256b2

@clerk/clerk-react
4.26.5-snapshot.v92256b2

@clerk/remix
3.0.7-snapshot.v92256b2

@clerk/clerk-sdk-node
4.12.14-snapshot.v92256b2

@clerk/shared
0.24.5-snapshot.v92256b2

@clerk/themes
1.7.8-snapshot.v92256b2

@clerk/types
3.55.1-snapshot.v92256b2

Tip: use the snippet copy button below to quickly install the required packages.
# @clerk/backend
npm i<EMAIL_ADDRESS>
# @clerk/chrome-extension
npm i<EMAIL_ADDRESS>
# @clerk/clerk-js
npm i<EMAIL_ADDRESS>
# @clerk/clerk-expo
npm i<EMAIL_ADDRESS>
# @clerk/fastify
npm i<EMAIL_ADDRESS>
# gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>
# @clerk/localizations
npm i<EMAIL_ADDRESS>
# @clerk/nextjs
npm i<EMAIL_ADDRESS>
# @clerk/clerk-react
npm i<EMAIL_ADDRESS>
# @clerk/remix
npm i<EMAIL_ADDRESS>
# @clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>
# @clerk/shared
npm i<EMAIL_ADDRESS>
# @clerk/themes
npm i<EMAIL_ADDRESS>
# @clerk/types
npm i<EMAIL_ADDRESS>

!snapshot

Hey @LekoArts - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
0.31.1-snapshot.v9ff9834

@clerk/chrome-extension
0.4.8-snapshot.v9ff9834

@clerk/clerk-js
4.61.1-snapshot.v9ff9834

@clerk/clerk-expo
0.19.10-snapshot.v9ff9834

@clerk/fastify
0.6.15-snapshot.v9ff9834

gatsby-plugin-clerk
4.4.16-snapshot.v9ff9834

@clerk/localizations
1.26.5-snapshot.v9ff9834

@clerk/nextjs
4.25.5-snapshot.v9ff9834

@clerk/clerk-react
4.26.5-snapshot.v9ff9834

@clerk/remix
3.0.7-snapshot.v9ff9834

@clerk/clerk-sdk-node
4.12.14-snapshot.v9ff9834

@clerk/shared
0.24.5-snapshot.v9ff9834

@clerk/themes
1.7.8-snapshot.v9ff9834

@clerk/types
3.55.1-snapshot.v9ff9834

Tip: use the snippet copy button below to quickly install the required packages.
# @clerk/backend
npm i<EMAIL_ADDRESS>
# @clerk/chrome-extension
npm i<EMAIL_ADDRESS>
# @clerk/clerk-js
npm i<EMAIL_ADDRESS>
# @clerk/clerk-expo
npm i<EMAIL_ADDRESS>
# @clerk/fastify
npm i<EMAIL_ADDRESS>
# gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>
# @clerk/localizations
npm i<EMAIL_ADDRESS>
# @clerk/nextjs
npm i<EMAIL_ADDRESS>
# @clerk/clerk-react
npm i<EMAIL_ADDRESS>
# @clerk/remix
npm i<EMAIL_ADDRESS>
# @clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>
# @clerk/shared
npm i<EMAIL_ADDRESS>
# @clerk/themes
npm i<EMAIL_ADDRESS>
# @clerk/types
npm i<EMAIL_ADDRESS>

!snapshot

Hey @LekoArts - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
0.31.1-snapshot.v6ff1e40

@clerk/chrome-extension
0.4.8-snapshot.v6ff1e40

@clerk/clerk-js
4.61.1-snapshot.v6ff1e40

@clerk/clerk-expo
0.19.10-snapshot.v6ff1e40

@clerk/fastify
0.6.15-snapshot.v6ff1e40

gatsby-plugin-clerk
4.4.16-snapshot.v6ff1e40

@clerk/localizations
1.26.5-snapshot.v6ff1e40

@clerk/nextjs
4.25.5-snapshot.v6ff1e40

@clerk/clerk-react
4.26.5-snapshot.v6ff1e40

@clerk/remix
3.0.7-snapshot.v6ff1e40

@clerk/clerk-sdk-node
4.12.14-snapshot.v6ff1e40

@clerk/shared
0.24.5-snapshot.v6ff1e40

@clerk/themes
1.7.8-snapshot.v6ff1e40

@clerk/types
3.55.1-snapshot.v6ff1e40

Tip: use the snippet copy button below to quickly install the required packages.
# @clerk/backend
npm i<EMAIL_ADDRESS>
# @clerk/chrome-extension
npm i<EMAIL_ADDRESS>
# @clerk/clerk-js
npm i<EMAIL_ADDRESS>
# @clerk/clerk-expo
npm i<EMAIL_ADDRESS>
# @clerk/fastify
npm i<EMAIL_ADDRESS>
# gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>
# @clerk/localizations
npm i<EMAIL_ADDRESS>
# @clerk/nextjs
npm i<EMAIL_ADDRESS>
# @clerk/clerk-react
npm i<EMAIL_ADDRESS>
# @clerk/remix
npm i<EMAIL_ADDRESS>
# @clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>
# @clerk/shared
npm i<EMAIL_ADDRESS>
# @clerk/themes
npm i<EMAIL_ADDRESS>
# @clerk/types
npm i<EMAIL_ADDRESS>

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Support for libsixel to show images?

Terminals such as xterm allows one to show true images using sixel graphics. Since you are already supporting images in iTerm, any chance of supporting images in linux using libsixel?

@vrthra sure! would you like to work on a patch?

Not immediately, but I will send you a PR once I get a bit more time.


Some issues while saving contact in contact page

Describe the bug

Image is not saving as it shows on saving time
area is not saving
header is not available

Expected behavior

Image should save as it shows on saving time
Area should save
There should be a header like company page

Screenshots
If applicable, add screenshots to help explain your problem.

https://www.berrycast.com/conversations/8fa013e1-bc45-56cc-ad63-25449a2279a2


When will the new api come out？

Describe the solution you'd like
so depending on the api to use memos
Type of feature
Integrations
Additional context
No response

The latest API v1 has been released in v0.22.0. Learn more with https://memos.apidocumentation.com/reference


Skip USB_DPU on SO-8?

For a long time ago i was experimenting with USB on PIC18F2550 (still got my NES fourscore to USB Gamepad) .
If i remember correctly it is possible to skip the extra GPIO for USB-pullup and connect the 1.5k to 3v3 instead?
To cause a USB re-enumerate the D- pin can be hold low instead by set the GPIO as output low for a little while.
Great job cnlohr btw, you got many interesting repos.

Hi!

If i remember correctly it is possible to skip the extra GPIO for USB-pullup and connect the 1.5k to 3v3 instead?

Yes, it's a viable configuration, it's even documented in README:

it may connect D- to DPU or VCC if the intent is for the part to always be on-bus

I'm not sure about your second point:

To cause a USB re-enumerate the D- pin can be hold low instead by set the GPIO as output low for a little while.

I don't think this way is safe, if a host tries to pull this line up during you're holding it down, it'll cause a bus conflict and either host or MCU will be damaged somehow. IMHO (at least) there should be series resistors (10~68R) between the MCU and USB connector, they'll also help with unneeded signal reflections (even low-speed USB may have them).

The USB host must be able to survive D+, D- short to GND according to specification.
So it should be safe to do if the USB host follow the USB specification.
Short to 5V is removed in "5V Short Circuit Withstand ECN.pdf"
https://www.usb.org/document-library/usb-20-specification
File usb_20.pdf chapter 7.1.1 (page 124)
But a serie resistor is probably wise to add anyway.
I have missed that line in the README.
Thanks Nable80.

Thank you for a reference to the specification!

I would be curious to know more people's feelings about this.  No need to close.

I am going to close this now, but also add the note about a series resistor the README.


stop adding iat in payload (optional claim)

fix #111
As mentioned in RFC7519, iat is an optional claim.
If iat is added in payload, token that does not contains iat will never pass signature verification.

hey @jbidzik will this create backward compatibility problems?

Also, sorry for the delay for having a look at this....busy :P

@odino i dont think this will create BC break because we stop adding iat on both token generation and validation.
However, if someone want to add iat claim, its not possible anymore.


Feature/libmamba solver

no longer using mamba
now using conda with libmamba solver
updated versions of base_images/vanilla packages to be consistent with higher level package versions that base_images/pangeo was using because I was getting dependency errors
isce2 and rgedi going to be removed, but edited them anyway to be consistent
all base_images starting out with

RUN conda install -y -c conda-forge pyOpenSSL=23.2.0 && \
    conda install -y -n base conda-libmamba-solver && \
    conda config --set solver libmamba

to be consistent across
Note that conda install -y -c conda-forge pyOpenSSL=23.2.0 fixed a building bug for 3 of the images earlier

believed to solve/ reduce ImportError: libarchive.so.13: cannot open shared object file: No such file or directory when building images
Added

ENV LANG en_US.UTF-8
ENV TZ US/Pacific
ARG DEBIAN_FRONTEND=noninteractive

to the beginning of base_images/vanilla to be consistent

built both develop and feature/libmamba-solver branches and times were
vanilla: 14 minutes 11 seconds (libmamba) vs 23 minutes and 18 seconds (develop)
isce3: 25 minutes 17 seconds (libmamba) vs 14 minutes 6 seconds (develop)
r: 16 minutes 53 seconds (libmamba) vs 24 minutes and 52 seconds (develop)
pangeo: 14 minutes 53 seconds (libmamba) vs 15 minutes 49 seconds (develop)

Find successful build of 4 relevant images here: https://repo.dit.maap-project.org/root/maap-workspaces/-/pipelines/3650
Note that isce2 is failing to build with dependency issues, but in the 9/20 hackathon we decided it wasn't worth trying to fix
I got rGEDI to work one time here: https://repo.dit.maap-project.org/root/maap-workspaces/-/pipelines/3669, but then it kept failing later so I just removed the fix
I can keep working on fixing rGEDI, but I didn't think it was worth the time since we decided to get rid of it
Find build of develop here for comparisons: https://repo.dit.maap-project.org/root/maap-workspaces/-/pipelines/3659

@anilnatha noticed that libmamba solver is ignoring the nodefaults channel tag in the .yml file and it is a bug others have noticed. In the hackathon we decided to just let it be for now and libmamba solver will become even faster once this bug is fixed
Also, Alex mentioned we should freeze isce2 and rgedi on a working image and this PR fails for both those images so maybe we freeze those images before merging this PR? Again, I tried briefly to get isce2 and rgedi working but wasn't sure it was worth the time
Updating documentation to tell users to use conda install instead of mamba install

Thanks @anilnatha! What do you think about freezing isce2 and rgedi on the current working develop image? This PR fails for both those images so maybe we freeze those images before merging this PR? Again, I tried briefly to get isce2 and rgedi working but wasn't sure it was worth the time

Thanks @anilnatha! What do you think about freezing isce2 and rgedi on the current working develop image? This PR fails for both those images so maybe we freeze those images before merging this PR? Again, I tried briefly to get isce2 and rgedi working but wasn't sure it was worth the time

If I'm understanding correctly, you're proposing that we use the current images for rgedi and isce2 for the next release since we know they will fail the build process with these changes? if so, I think this is sound. We probably should to discuss retiring these if very few are using them, or nobody is using them for that matter. @grallewellyn

@anilnatha Sujen asked if anyone was using rgedi and there was one reply: https://github.com/orgs/MAAP-Project/discussions/786
I think freezing them sounds like a good plan so that users can still use them as long as we have a warning that they are no longer supported

Sounds good to me, I want to learn how we actually go about "freezing" them during our release process.


Make some Typescript improvements

Exclude Typescript test file from files in npm package
Fixed minor typo

Coverage remained the same at 97.973% when pulling e307a5db42208572625107674b66bd80b7f782ca on typescript-improvements into e270f498371df0d4d74d7a790e146946e5067c1a on master.


[Discussion] Release bundles

Let me start, by saying that vcpkg works quite well for my needs so far, so I'd like to put this up for discussion, because I'm intrested in other people's opinions / experiences, not because I see an immediate need for it.
Now to my question:
Have you considered to provide "release bundles" of the portfiles in this repository?
According to the documentation, one idea behind a curated list of packages (as opposed to the conan model) is to make sure they all work together properly. However, as far as I can tell, this is currently only  partially enforced (and with the number of libraries it's not realistic to keep master stable at all times).  What I would envision is that every half year or so, a release branch is created that freezes library versions, undergoes extensive tests (building all packages, for all triplets with all supported toolchains and running all tests) and at least for a set of "core libraries" (TBD) any upcomming errors are fixed (either by selectively up/-downgrading a library or applying patches). Aside from lower likelyhood of downloading a "broken" portfile version, it would also reduce the frequency by which one has to recompile large parts of the local repository, just because some minor fix was applied to some foundational library.
In principle, the idea is similar to the system packages provided by classic release based linux distributions.

Closing due to inactivity / no apparent interest


ociodisplay namespace error

Line 133 of ociodisplay/main.cpp produces an error on Linux build.
f->read_image(OIIO::TypeFloat, &img[0]); needs to change to f->read_image(OIIO::TypeDesc::TypeFloat, &img[0]);
@hodoulp did this resolve correctly on your Windows builds?
Also raises the point that not all apps are built on CI, ociodisplay has the large dependency on OIIO so may not be worth the build times.

Yes, it was a build break on Windows. All the builds from master are green. So what is the difference?
Concerning ociodisplay app, as OIIO is not present that app should not be built even if OCIO_BUILD_APPS is ON.

I was building ociodisplay on a Linux local machine just wanted to run through all the paces.

Yes, it was a build break on Windows

With or without the ::TypeDesc ?

My bad, ociodisplay is not compiled on Travis... So revert it and I will check on my Windows machine.
Sorry for that noise.

You can check OpenImageIO/typedesc.h to understand why the two are possible. Based on my understanding, the former one TypeDesc::FLOAT is deprecated. What OIIO version are you using ?

I use the 1.9.0 on from master.

I was pulling from 1.0.7 since the higher versions require C++11 as a minimum, just wanted to keep consistent

closed by #487


no receive message (node v0.12.x)

Hey there :)
When sending for example a PAUSE command on node v0.10.x you normaly instantly get a receive message:
SEND:
castv2 send message: protocolVersion=0 sourceId=client-789231 destinationId=web-39 namespace=urn:x-cast:com.google.cast.media data={"type":"PAUSE","mediaSessionId":1666547486,"requestId":11} +1s

RECEIVE:
castv2 recv message: protocolVersion=0 sourceId=web-39 destinationId=client-789231 namespace=urn:x-cast:com.google.cast.media data={"type":"MEDIA_STATUS","requestId":11,"status":

On node v0.12.x (and I guess also on io.js) often the receive message never comes back. On higher level libs this results to callbacks which never get triggered:
player.pause(function() {
    // never gets called because of missing receive message.
});

already investigated some time into this, but didn't find the cause of this issue yet.

Actually there seems to be something blocking the event-loop. I'm not sure if that happens within castv2 or somewhere else (so might not be a castv2 issue).

Okay, the problem definitly is somewhere else.


Fix backslash in title and description metadata

In title and description metadata, replaced \ with appropriate symbol.

@nitoyon,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Thank you @nitoyon.  Sorry for the delay, I will review

Thanks again @nitoyon for your sharp eye.  I queried the .md files and found 57 files that still have backslashes in the description metadata line.  I have opened an internal work item to fix the remaining files.  Debugger is also missing many ! characters.  I hope to have that fixed soon as well.

Thanks!


fix: camera controls supports multiple visage instances

fixed camera controls issues to support multiple visage instances

Implementation

controls and progress are used to be declared on the module level. It causes issues with camera positions if multiple visage instances are rendered on the screen at the same time.
moved controls and progress from module level to React component level so multiple visage instances have their own camera controls instances.

Just testing, looks like when updating the camera zoom target, zooming becomes unresponsive. You can check this in the "Static" story.

I will check what's up with the visual tests!

@Jarvv @akshlu I'm facing the same issue and this PR looks very useful. Do we have an ETA on when will this be merged and released?


Add programmatic API

Please add a programmatic API, so we can integrate Protractor more easily into our custom workflow. It looks like every plugin author (gulp, Grunt, etc.) needs to spawn a child process and pass arguments via command line to configure Protractor. This can be quite cumbersome (like passing complex arrays via command line

If there's a lot of interest in this we'll look into it, but it my gut reaction is that this would be a lot of work for a small group of users who already have a viable alternative.
In the mean time, if you get sick of passing everything through the commandline, keep in mind that the config file can be any node file that exports config property.  So you could put logic into the config file (example).  So if you wanted to you could always read an array from a file using require or even fs.

+1
Something like Karma's public API would be nice:
var Launcher = require('protractor').Launcher;
var launcher = new Launcher(configOptions, function (exitCode) {
  console.log('Protractor has exited with ' + exitCode);
  process.exit(exitCode);
});

I looked into using launcher.js directly and it shows promise but I'd like to be able to define my own cleanUpAndExit.

In the mean time, if you get sick of passing everything through the commandline, keep in mind that the config file can be any node file that exports config property.

That is true, but the config file can't contain async code: https://github.com/angular/protractor/issues/578

You can do this with require('protractor/launcher') and then initializing it with a configuration object.


optional brotli dependency breaks windows installs

running npm install on windows causes the optional brotli dependency to get pull down and compiled, which is a pretty guaranteed break on any machine that doesn't even use brotli compression and has no need to otherwise run any node-gyp compiles. As this is but one in a million utility extensions for grunt, running with --no-optional is not really an option, as there are plenty of other utils for which the optional dependencies do work.
Can this lib tap into prebuilt iltorb libs, or be split up such that grunt-contrib-compress is compile-less compressors, with an optional additional install of grunt-contrib-compress-brotli so that this can be installed, or left off, separately, thus not causing cross-platform compatibility issues?

iltorb now offers pre-built binaries.

@MayhemYDG that's great to hear! The README.md still talks about needing to manually compile, is it missing a leading docs section to explain that compiling is only necessary when there is no precompiled binary available for the particular OS the user is on?

The readme has been updated to reflect the recent changes.

Nice! can you do a patch release to npm too (1.2.1) so that the new README is picked up there, too? This si super cool, thanks so much for the hard work!

I'm working on updating brotli, so a new release will happen soonish.


0.8.1: alb Error: "vpc_id": this field cannot be set

using:
terraformer-0.8.1
terraform-0.12.9
terraform-provider-aws_v2.3
lb.tf gets a vpc_id imported in resource aws_lb
This results in error while running terraform plan;
Error: "vpc_id": this field cannot be set
commenting vpc_id fixes it.

Hey
Thank for your bug report.
Which resources has vpc_id? aws_lb?
it's network balancer or application?

Ah, sorry for my unclear report, but yes as the subject suggests it about the ALB and the resource is called aws_lb

Hi, is this issue fixed yet please? I am stuck with the same error and can't move forward. I have upgraded to v0.12.13 but it is still not working. I am not sure if fix issue 209 means this is now resolved in which case I don't know how to get the update. Thanks.


Userlocalhost bugfix/unables to handle unicode

PR which includes some small changes on top of #3116:

Support for Python 3
Changelog entry

Current coverage is 77.39% (diff: 100%)

Merging #3118 into master will increase coverage by 0.02%

@@             master      #3118   diff @@
==========================================
  Files           430        430
  Lines         22144      22145     +1
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          17133      17138     +5
+ Misses         5011       5007     -4
  Partials          0          0

Diff Coverage
File Path

•••••••••• 100%
st2common/st2common/models/system/action.py

Powered by Codecov. Last update ac1eb95...9d4acb8


Mute not working

http://dropbox.github.io/dropbox-sdk-js/Dropbox.html#filesUpload__anchor
I'm starting to use the dropbox API, but the mute parameter doesn't seems to work, my Dropbox client generate a notification anyway.
client.filesUpload({
	'path': '/livenotifier.json',
	'contents': "{\"some\": \"json\"}",
	'mode': {
		'.tag': 'overwrite'
	},
	'mute': true
});

Thanks for the report! This is a known issue. It's open with engineering, but I don't have a timeline/estimate for a fix.

The bug is from the sdk or Dropbox itself ?

I believe this is an issue with the Dropbox server and/or desktop client, and not the developer SDK.

Seems like it have been fixed


Empty captain/crew show up when issuing a violation

When doing a boarding, I went right to "Violation", skipping the "Crew" section.
When I clicked "Issued To" on the violation screen, I saw an empty captain and crew member. This screen should not show items that have no name AND no license number.

Closed in #295


Prevent long timeout when invoking a function and the user has misconfigured the environment.

Updates the RetryAllBackOff function to fail early when a request to obtain Runners cannot succeed due to an Fn misconfiguration error. This prevents a user having to wait for the maximum timeout (~180s) when the system is misconfigured.

Link to issue this resolves

What I did

Updated the RetryAllBackOff to accept the error returned by rp.Runners(ctx, call).

Added check to not re-try when the error returned by rp.Runners(ctx, call) returns a user configuration error.

The error is checked to see if it a user configuration error with the  models.IsFuncError(err). This is the same function used to create the blame user tag in the existing middleware (with the exception we do not need to check for nullity).

Additionally check for an error status of 502 (which also denotes a user error).

How I did it

Worked with Jan Grant (already a comitter).

Replicated the issue tests against a development version of the Fn platform.

Dynamically checked that tr.requestCtx and tr.placerCtx did not have the required information at the point of early return.

Statically examined the Fn code to see how the user blame mechanism worked.

Added a small piece of code to replicate the user blame functionality in RetryAllBackOff and return early if necessary.

How to verify it

NB: This was tested against an OCI backend.

Create OCI test resources, Application, and Function.

Remove the VCN Policy permissions from the invoking Function compartment.

Attempt to invoke the Function.

Without the changes it will take around 180s to fail.
Manual Integration Test

Show invoke fails after 180s when miss-configured.

$> time fn invoke test-app test-fn-01
Error invoking function. status: 502 message: subnet ocid1.subnet.oc1.iad.aaaaaaaa3zi47ktmvvoqjltnw2kksgbedfcdzqrocvuxeonaz4rs3vped6gq does not exist or Oracle Functions is not authorized to use it

real	3m2.990s
user	0m0.065s
sys	0m0.032s

PR - Invoke fails fast when miss-configured.

$> time fn invoke test-app test-fn-01
Error invoking function. status: 502 message: subnet ocid1.subnet.oc1.iad.aaaaaaaa3zi47ktmvvoqjltnw2kksgbedfcdzqrocvuxeonaz4rs3vped6gq does not exist or Oracle Functions is not authorized to use it

real	0m1.426s
user	0m0.065s
sys	0m0.018s

PR - Invoke still works when NOT miss-configured..

$> time fn invoke test-app test-fn-01
{"message":"Hello World"}

real	0m1.121s
user	0m0.066s
sys	0m0.017s

One line description for the changelog

Prevent long timeout when invoking a function and the user has misconfigured the environment.

Trying to determine how long it takes to recover once a user error has been fixed. I am having network issues here atm, but, it is still returning 502's 10 mins later.

The cached response behaviour is what I was concerned about. Will discuss this face-to-face.

Thanks Jan.
Just to update the thread, it only gets cached for 60 mins. So not a showstopper, but, we are going to remedy it.

Hmm, we're supposed to clear the error as soon as we successfully provision a runner, so if you're still seeing it after 10 minutes that suggests we have a bug. Plus the fact that we clear it shouldn't generally matter since once the runner is up your invoke ought to succeed in which case you won't see an error regardless.


[Enhancement] Make Powered Spawners Modular

I was noticing that the method of tuning powered spawners is quite roundabout and i wanted to suggest a more modular system where broken spawners are crafted into a stable item that is inserted into the spawners inventory to serve as the tuning mechanism
additionally this would result in reusability because the tuning item can than be removed and placed into a soul binder to reset it. this would make the soul binder infinitely more useful and provide reuse-ability to the spawning system
currently there exists no method to recover or re-tune the broken spawner once placed inside a powered spawner and if you compare the spawning mechanics of EnderIO to MFR and DE you'll notice its excessively overcomplicated

in my opinion it's quiet right, because it spawns mobs from power only  .. it does not need any mobessence like MFR, thus it's more "easy" to keep it running, but more complicated to setup

Overcomplicated? Or just not simple? Not allowing changing of the spawn target is very intentional.

Want to be able to change the target mob you're spawning? use MFR.
But first you'll have to kill a few enderman and a ghast, a few blazes, and have a couple emeralds.
not cheap. but you can change the "target" mob with a simple SFM or computer craft tinkering. limiting the enderIO spawner to a single mob is, IMO a good way to keep things different/fresh and make choices have impact.

I love the Ender IO spawners and how they work.
No Work Needed. I get plenty of Broken spawners from all over.
It was very easy to learn.


Support DynamoDbPreserveEmptyObject annotation

Supporting this as a property-level annotation was a bit insane, so it's supported as a class-level annotation.


Auto SSL certificate renewal failing using AWS Route53 DNS

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you're not using someone else's docker image?

Yes

Have you searched for similar issues (both open and closed)?

Yes

Describe the bug
Automatic SSL certificate renewal fails when using AWS Route53 DNS challenge, but renewing manually through NPM console works fine.
Based on initial review of the logs, it looks like the automated renewal command is not setting the required "AWS_CONFIG_FILE" environment variable:
[3/8/2022] [6:02:17 AM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
Failed to renew certificate npm-12 with error: Unable to locate credentials

Nginx Proxy Manager Version
v2.9.16
To Reproduce
Steps to reproduce the behavior:

Creates Let's Encrypt certificate using AWS Route53 DNS challenge
As certificate expiry date nears, the renewals fail

Expected behavior
SSL certificate is renewed as the expiry date approaches
Operating System
Unraid 6.10.0-rc2
Docker version 20.10.9, build c2ea9bc
Additional context
Logs
[3/8/2022] [5:54:15 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[3/8/2022] [6:02:17 AM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
Failed to renew certificate npm-12 with error: Unable to locate credentials
To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
AMAll renewals failed.   Would you be kind enough to share the manual command, please?  I could not find it.  Thank you.

@chaddm Try renewing through the NPM GUI, under SSL Certificates -> Renew Now

@coreylane Yes.  That worked.  Thank you.

Same issue.  Renewing manually through GUI fixed the issue which was the renewal at 4/25/2022 1:01AM
`[4/24/2022] [10:41:18 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[4/24/2022] [10:41:19 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[4/24/2022] [10:41:19 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[4/24/2022] [10:41:19 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
[4/24/2022] [10:41:19 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
[4/24/2022] [10:41:19 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[4/24/2022] [10:41:20 PM] [Setup    ] › ℹ  info      Logrotate completed.
[4/24/2022] [10:48:23 PM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
Failed to renew certificate npm-1 with error: Unable to locate credentials
To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/npm-1/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
at ChildProcess.exithandler (node:child_process:399:12)
at ChildProcess.emit (node:events:526:28)
at maybeClose (node:internal/child_process:1092:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
[4/24/2022] [11:41:18 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[4/24/2022] [11:43:16 PM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
Failed to renew certificate npm-1 with error: Unable to locate credentials
To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/npm-1/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
at ChildProcess.exithandler (node:child_process:399:12)
at ChildProcess.emit (node:events:526:28)
at maybeClose (node:internal/child_process:1092:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
[4/25/2022] [12:41:18 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[4/25/2022] [12:41:49 AM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
Failed to renew certificate npm-1 with error: Unable to locate credentials
To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
All renewals failed.  Works manually via the GUI.

I have the same issue. I'm unable to verify the logs (it's been a week or two since the last manual renewal) but symptoms are the same. Let's Encrypt via Route53 DNS, get e-mail from Let's Encrypt that the cert was not automatically renewed, manual renewal saves the day.

I have the same Issue, Automatic renewal doesn't work, manual renewal does.
Below a snippet from the docker log:
Auto renewal
2022-06-17T09:47:57.071050992Z [6/17/2022] [9:47:57 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
2022-06-17T09:57:47.308169768Z [6/17/2022] [9:57:47 AM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
2022-06-17T09:57:47.309667756Z Failed to renew certificate npm-10 with error: Unable to locate credentials
2022-06-17T09:57:47.309676328Z To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
2022-06-17T09:57:47.309679394Z Failed to renew certificate npm-11 with error: Unable to locate credentials
2022-06-17T09:57:47.309687161Z To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
2022-06-17T09:57:47.309689779Z Failed to renew certificate npm-12 with error: Unable to locate credentials
2022-06-17T09:57:47.309692250Z To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
2022-06-17T09:57:47.309694859Z Failed to renew certificate npm-13 with error: Unable to locate credentials
2022-06-17T09:57:47.309697339Z To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
2022-06-17T09:57:47.309699886Z Failed to renew certificate npm-14 with error: Unable to locate credentials
2022-06-17T09:57:47.309702216Z To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
2022-06-17T09:57:47.309704851Z Failed to renew certificate npm-15 with error: Unable to locate credentials
2022-06-17T09:57:47.309707201Z To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
2022-06-17T09:57:47.309712085Z Failed to renew certificate npm-2 with error: Unable to locate credentials
2022-06-17T09:57:47.309714471Z To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
2022-06-17T09:57:47.309717083Z Failed to renew certificate npm-3 with error: Unable to locate credentials
2022-06-17T09:57:47.309719389Z To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
2022-06-17T09:57:47.309722585Z Failed to renew certificate npm-4 with error: Unable to locate credentials
2022-06-17T09:57:47.309726014Z To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
2022-06-17T09:57:47.309729790Z Failed to renew certificate npm-5 with error: Unable to locate credentials
2022-06-17T09:57:47.309733391Z To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
2022-06-17T09:57:47.309737128Z Failed to renew certificate npm-6 with error: Unable to locate credentials
2022-06-17T09:57:47.309740634Z To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
2022-06-17T09:57:47.309746021Z All renewals failed.  Is anyone able to fix this issue?

I'm still experiencing this issue on the latest version. Is anyone able to fix this issue?

Renewing through the NPM GUI works fine for me, I posted a screenshot in an earlier comment. If this doesn't work you may have an issue with your AWS credentials. Perhaps the User doesn't have required permissions to route53. What do your logs say?
Required AWS permissions:
route53:ChangeResourceRecordSets
route53:ListHostedZones
route53:GetChange

@coreylane renewing via the GUI works fine. Automatic renewals don't though. Since I have 50+ entries it's a real pain having to renew manually.
How much effort is required to fix the auto renewals?
Thanks for you help on this.

It looks like the code use for auto renewal isnt using the same renewal functions as the UI
https://github.com/NginxProxyManager/nginx-proxy-manager/blob/14b889a85f2f8af9a13ed6122f5a0a91d64ecc36/backend/internal/certificate.js#L42-L106
It should use this function to renew the certificates
https://github.com/NginxProxyManager/nginx-proxy-manager/blob/14b889a85f2f8af9a13ed6122f5a0a91d64ecc36/backend/internal/certificate.js#L999-L1028

@jc21 if I can push a fix for this would you support a PR?

Still having this issue.  I was able to resolve by passing the credentials as an environment variable in docker-compose:
environment:       - AWS_CONFIG_FILE=/etc/letsencrypt/credentials/credentials-1

Just to thank @miztertea for contributing a solution, and to confirm that the env variable solved the problem for me as well.

How would I handle this for an install that has multiple credential files?  I have 9 domains requiring certificates with all separate AWS keys.  credentials-11, credentials-13...etc

Unfortunately this workaround will only help with one credential file. I suppose you could create one IAM user that has access to all of your domains. As long as its the same IAM user, it won't matter which cred file you specify as they would all be the same access/secret pair

This still would only work from one AWS tenant/account

You can also pass the credentials directly to the certbot by setting two environment vars in your docker-compose file:
AWS_ACCESS_KEY_ID: "AAAAAAAAAAAAAAAAAAAAA"
AWS_SECRET_ACCESS_KEY: "BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB"

That is excellent @Ich-Eben. Thanks!

I implemented emkookmer's suggestion in #3392

It looks like the code use for auto renewal isnt using the same renewal functions as the UI, but a simple command to certbot
https://github.com/NginxProxyManager/nginx-proxy-manager/blob/14b889a85f2f8af9a13ed6122f5a0a91d64ecc36/backend/internal/certificate.js#L42-L106
It should use this function to renew the certificates
https://github.com/NginxProxyManager/nginx-proxy-manager/blob/14b889a85f2f8af9a13ed6122f5a0a91d64ecc36/backend/internal/certificate.js#L999-L1028
I've "quick" fixed my installation by hardcoding the aws credentials:
const cmd = certbotCommand + ' renew --non-interactive --quiet ' +
        '--config "' + letsencryptConfig + '" ' +
        '--preferred-challenges "dns,http" ' +
        '--disable-hook-validation ' +
        (letsencryptStaging ? '--staging' : '');

let mainCmd = 'AWS_CONFIG_FILE=\'/etc/letsencrypt/credentials/credentials-3\' '+cmd

return utils.exec(/*cmd*/mainCmd)
        .then((result) => {

Just came to thank you for your attention to detail here <3 Thank you!


Change URL of channel ARD HD/Das Erste HD

This should fix #470

Thank you very much for your PR! I ported the URL over to zapp backend, where the new release will be deployed in the next hours: https://github.com/mediathekview/zapp-backend/commit/4a5b9943fe70ccf27d4e6d440ee74643fd8695be

Thank you for your quick response!
Looks like the deployment process didn't succeed.
https://api.zapp.mediathekview.de/v1/channelInfoList
still delivers the old URL:

{
"das_erste": {
"streamUrl": "https://mcdn.daserste.de/daserste/de/master.m3u8",
"name": "Das Erste"
},


callback arguments not being properly checked

The error(s) read:

Line   classes/Smarty.php

37     Parameter #3 $callback of method Smarty_Internal_TemplateBase::registerPlugin() expects callback, string given.
41     Parameter #3 $callback of method Smarty_Internal_TemplateBase::registerPlugin() expects callback, string given.
45     Parameter #3 $callback of method Smarty_Internal_TemplateBase::registerPlugin() expects callback, string given.

[ERROR] Found 3 errors
And a sample of the code at the first error:
$this->smarty->registerPlugin('modifier', 'number_format', 'number_format');
Smarty's documentation ( https://www.smarty.net/docs/en/api.register.plugin.tpl ) says it does indeed accept a string representation for the third argument.
But further, phpmd doesn't seem to accept ANY form for that argument. I tried:
\number_format
\number_format()
number_format
number_format()
$temp_var (set to 'number_format')
and so on.
What is the correct format for a callback supposed to be to make phpmd pass the check, and alternatively, can it be corrected to accept the string version (since that seems at least functional, even if phpmd doesn't like it)?

I sincerely apologize, this was an error from phpstan, not phpmd. Sorry!


Feature: async dataview query support

Adds support for async Dataview Queries.
Helpful for pulling multiselect & dataview options from other Obsidian plugins' APIs
This functionality has only been tested using the metadata menu plugin
original discussion linked here: https://forum.obsidian.md/t/new-plugin-modal-form-integrate-forms-into-quickadd-templater-etc/67103/73

Thank you for the attempt. I already implemented this feature using this PR as inspiration.


Implement basic emoji support

About the PR
Adds support for uncolored emojis using Noto Emoji https://fonts.google.com/noto/specimen/Noto+Emoji
Why / Balance
This was really easy to do. Idc if this PR just gets closed because we don't want emoji support.
I think this would be funny for PDA messaging
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Requires space-wizards/RobustToolbox#4332

Why would we want this in chat, if even chatspeak words are banned?

Can be fine in papers/books, but that seems really out of place in chat imho

I also think they don't belong in chat. I just added them to the default font stack

player: i found 🤡
TTS: died

player: i found 🤡 TTS: died

A TTS will either describe the emoji or ignore it

Keep in mind that while this may not be desirable for chat, downstreams may want support for this for various things & PDA messaging probably could benefit from this too. Ahelp icons would also be really nice with this since currently they need to use a small batch of really odd emojis. If people are gonna use netspeak words they’ll do it regardless of if emojis are supported or not imho

Did you mean it requires https://github.com/space-wizards/RobustToolbox/pull/4834 ?

Yea, thanks for noticing that 🙏

Please add an accent that makes emjoji in chat change to descriptions of whatever the emojis for our sanity's sake.

I removed the font from the default font stack. It can still be added where emoji support is needed and used for the font tag.
@metalgearsloth

Engine PR closed so not sure what's going on here.


Remove Docker Instructions from README

I propose removing Docker instructions from the README since most of the regular core members do not use Docker and new members have not been successful at getting it working by following these instructions.

Last call for comments on this, otherwise I will merge tomorrow night without objection.


Require a token for API usage

Currently there IS a working login and signup but it doesnt do anything since nothing requires authentication yet

generating and checking tokens is working

Token objects should eventually be stored in an array. and saved into a file periodically. while the tokens file should get opened to a million it should help with performance at a larger user base

tokens are mostly done:

API requests should require them , but untested.
tokens are still not being sent to the user after logging in.

here are some of the references I'm using:
https://stackoverflow.com/questions/18038541/how-do-i-create-and-save-an-expiring-user-token-in-node-js
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises
https://stackoverflow.com/questions/46354134/get-a-value-from-a-promise-function-in-nodejs#46354264

Tested a Token is required for API usage


Add documentation for custom template functions

Signed-off-by: patoarvizu<EMAIL_ADDRESS>

Q
A

Bug fix?
no

New feature?
yes

API breaks?
no

Deprecations?
no

Related tickets
Documentation for https://github.com/banzaicloud/bank-vaults/pull/953

License
Apache 2.0

What's in this PR?
Documentation for the templating functionalities of Vault configuration, plus the custom functions added here.
Why?
The availability of Sprig functions wasn't well documented, so I'm adding it here plus the new custom functions that were added
Checklist

[x] User guide and development docs updated (if needed)

@bonifaido Here's the promised documentation. The markdown looks right, but is there a way to preview the website layout?


Konstantinos / Bug - Fix Typescript errors in deriv.com

Changes:

...

Type of change

[x] Bug fix
[ ] New feature
[ ] Update feature
[ ] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[ ] Dependency update
[ ] Documentation update
[ ] Release

@konstantinosG-deriv Could u pls resolve the conflicts


Video tutorial links

Add a command which links a video tutorial for each step.
Would be location specific.
Could be added via the Step Editor Menu when creating a new location.

Released on the UK server as a beta, but the location creation side of it is not yet tested.
It won't be publicly released until that is tested, but for now, it is useful to have on the UK server.


LED Refresh rate with some games is really bad

Hi,  first of all I want to thank you for this beautiful software!
Here's the issue (it looks a bit like #99 ):
I recently changed my evga 2070 xc gaming for a 3080 ti FE, and since then I have two issues that I do not remember having before:
1: (not really bothering me and doesn't concern you but might be connected to the problem) the geforce interface in some games (Red dead 2 and som other games), takes more time to appear and the performance UI doesn't output anything or refreshes every 5 or 10 seconds
2: In the games that are concerned by the first issue, the LEDs refresh rate "stutter" or "lags" behind, it can be ok for 2 second, then stop refreshing for 1, then refresh for 1, then stops for 5, etc...
Here's the things I've tried:
launching adrilight after the game with a macro, did not work.
Settings:
Here's what I was first writting while testing:
"Red Dead 2: Graphics set to minimum (it looks like it's getting rid of the stutter, but there's still a tiny bit of stutters from time to time (or I'm just getting lucky because when putting the graphics back to ultra, the stutters do not worsen."
But then while doing more and more tests (maxing every settings 2 by 2) the issue persisted, but when I reverted the setting to the one I used with my 2070, the issue disapeared, so I once again maxed everything 2 by 2 and the issue did not come back (all of these test were done without restarting once, so it's odd that the issue disapeared like that, might be because it has to "warm up?" which it did not before) After a restart of the game, the issue did not reappear, but sadly, after a system restart it did reappear. started the game again, disabled instant replay, issue fixed, I feel REALLY dumb for spending all this time on the issue
With that said, why didn't it appear when I had my 2070?
Hardware:
I bought an official Arduino UNO and raged at the soldering to pin 6 part because I'm bad at it, and all of that for nothing because the issue persists.
So for now I will use #112 arduino_buttered.ino as it makes the issue less obvious
If the issue has already been covered (I did search in the issues, closed and open, but I'm pretty blind when looking for stuff I need), or if it's not something you can help me with, I'm sorry in advance.
And as it appears to be an issue with nvidia drivers, I will still post the issue, but I will close it immediately.

Why did you closed you're issue?
Silails @.***> schrieb am Fr., 30. Dez. 2022, 01:54:

Closed #129 https://github.com/fabsenet/adrilight/issues/129 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/fabsenet/adrilight/issues/129#event-8128609513, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPYKKPBZ2V2CALIIIFBMR3WPYXFBANCNFSM6AAAAAATMQDK3Q
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Why did you closed you're issue?

As stated at the end, it's probably a driver issue/incompatibility with Nvidia instant replay feature, I still published it in case someone else is having a similar issue and in case you think it's something you could still help me with


Terminal windows wont' update on resize

VSCode Version:  1.3.0
OS Version: CentOS Linux release 7.1.1503 (Core)

Video

Thanks for the video! 👍

Fixed in the version 1.10.2.
Thanks


Add instructions for profiling with JFR

Add instructions for profiling with JFR.
gradle-profiler might be useful.

Done. Instructions are in README


Feature: run task only from cache

Which project is this feature idea for?
Turborepo
Describe the feature you'd like to request
My CI pipeline writes some metadata files, including the build number, when deploying a package. These metadata files are cached as outputs of a "deploy" task in turborepo.
When a subsequent pipeline runs, I'd like to be able to do an up-front check:
(1) check if the current code needs to be published (ie., is not cached)
(2) pull down, open and print information from the cached metadata files, if any
But I don't want this step of the build to actually run the "deploy" task in case of a cache miss.
Describe the solution you'd like
Something like a --cached-only flag that either skips uncached tasks or errors out when one is found.
Describe alternatives you've considered

Call turbo with --dry-run first, check, and then call turbo again without --dry-run only if the task is cached.

This works, but it's a little awkward and I don't like the risk that the 2nd call might actually run 'deploy' if anything happens to the cache, particularly if it's a remote cache

Use an environment variable to skip actually running tasks

I haven't actually tried this; considered it as a failsafe but I'd prefer not to make tasks more sensitive to environment variables

I'm not opposed to this as a feature, it seems like a good win to me. I'd be interested in ironing out an API that can pick and choose any combination of caches (fs or remote) and execution (real or dry).


Vernemq-Rabbitmq connection issue

when conecting to rabbitmq from vernemq getting error like this
Configurations in vernemq conf file
plugins.vmq_bridge = on
vmq_bridge.tcp.br0 = dev-test12rabbitmq.com:15672
vmq_bridge.tcp.br0.client_id = auto
vmq_bridge.tcp.br0.keepalive_interval = 60
vmq_bridge.tcp.br0.username = rabbitmq username
vmq_bridge.tcp.br0.password = rabbitmq
vmq_bridge.tcp.br0.restart_timeout = 10
vmq_bridge.tcp.br0.try_private = off
vmq_bridge.tcp.br0.topic.1 = * out
test 1 (used amqp port 5672 in configuration vmq_bridge.tcp.br0)
2018-12-28 12:18:23.459 [error] <0.408.0>@gen_mqtt_client:handle_frame:388 CRASH REPORT Process <0.408.0> with 2 neighbours exited with reason: no function clause matching gen_mqtt_client:handle_frame(waiting_for_connack, {error,cant_parse_variable_header}, {state,"dev-test12rabbitmq.com",5672,#Port<0.6498>,1,"guest","guest","visakh-Latitud...",...}) line 388 in gen_fsm:terminate/7 line 602
2018-12-28 12:18:23.460 [error] <0.323.0>@gen_mqtt_client:handle_frame:388 Supervisor vmq_bridge_sup had child {vmq_bridge,"dev-test12rabbitmq.com",5672} started with vmq_bridge:start_link(tcp, "dev-test12rabbitmq.com", 5672, {vmq_reg,direct_plugin_exports,[vmq_bridge]}, [{cleansession,true},{client_id,"visakh-Latitude-3480.br0"},{keepalive_interval,60},{restart_timeout,...},...]) at <0.404.0> exit with reason no function clause matching gen_mqtt_client:handle_frame(waiting_for_connack, {error,cant_parse_variable_header}, {state,"dev-test12rabbitmq.com",5672,#Port<0.6498>,1,"guest","guest","visakh-Latitud...",...}) line 388 in context child_terminated
test 2 (used http port 15672 in configuration vmq_bridge.tcp.br0)
2018-12-28 12:30:37.328 [error] <0.377.0> Failed to start Ranch listener {{127,0,0,1},1883} in ranch_tcp:listen([{ip,{127,0,0,1}},{port,1883},{nodelay,true},{linger,{true,0}},{send_timeout,30000},{send_timeout_close,true}]) for reason eaddrinuse (address already in use)
2018-12-28 12:30:37.328 [error] <0.377.0> CRASH REPORT Process <0.377.0> with 0 neighbours exited with reason: {listen_error,{{127,0,0,1},1883},eaddrinuse} in ranch_acceptors_sup:listen_error/4 line 56
2018-12-28 12:30:37.329 [error] <0.185.0>@vmq_ranch_config:reconfigure_listeners_for_type:187 can't reconfigure mqtt listener({127,0,0,1}, 1883) with Options [{max_connections,10000},{nr_of_acceptors,10},{mountpoint,[]},{proxy_protocol,false},{allowed_protocol_versions,[3,4,131]}] due to {{shutdown,{failed_to_start_child,ranch_acceptors_sup,{listen_error,{{127,0,0,1},1883},eaddrinuse}}},{child,undefined,{ranch_listener_sup,{{127,0,0,1},1883}},{ranch_listener_sup,start_link,[{{127,0,0,1},1883},10,ranch_tcp,[{ip,{127,0,0,1}},{port,1883},{nodelay,true},{linger,{true,0}},{send_timeout,30000},{send_timeout_close,true}],vmq_ranch,[{mountpoint,[]},{allowed_protocol_versions,[3,4,131]}]]},permanent,infinity,supervisor,[ranch_listener_sup]}}
2018-12-28 12:30:37.329 [error] <0.375.0> Supervisor {<0.375.0>,ranch_listener_sup} had child ranch_acceptors_sup started with ranch_acceptors_sup:start_link({{127,0,0,1},1883}, 10, ranch_tcp, [{ip,{127,0,0,1}},{port,1883},{nodelay,true},{linger,{true,0}},{send_timeout,30000},{send_timeout_close,...}]) at undefined exit with reason {listen_error,{{127,0,0,1},1883},eaddrinuse} in context start_error
2018-12-28 12:30:37.351 [info] <0.33.0> Application vmq_server started on node<EMAIL_ADDRESS>2018-12-28 12:30:37.352 [info] <0.33.0> Application dht_ring started on node<EMAIL_ADDRESS>Pushed data to vernemq topic vehicle_details, /vehicle_details no changes found in rabbitmq
Tested rabbitmq from nodejs 'amqp' client by pushing message directly and subscribing que. its working fine.so rabbitmq is working.
Actually which port to be used for connecting to rabbitmq http port(15672) or amqp port(5672)
Is anything to change to make his work ??
Thanks

The MQTT bridge goes over MQTT. You cannot connect to a HTTP port or an AMQP port with an MQTT client.
So you need to configure the bridge to connect to the port that you have configured for the RabbitMQ MQTT plugin, and you have to enable that plugin. See https://www.rabbitmq.com/mqtt.html