Site support request : http://lelombrik.net

I tried to download some videos on this site and none worked. It download the html page.
I found some different video formats.

http://lelombrik.net/67282 Youtube
http://lelombrik.net/53136 Dailymotion
http://lelombrik.net/67285 Vimeo
http://lelombrik.net/67254 Hosted video ?

$youtube-dl -v -s http://lelombrik.net/67282
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['-v', '-s', 'http://lelombrik.net/67282']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 2.7.8 - Linux-3.16.0-28-generic-x86_64-with-Ubuntu-14.10-utopic
[debug] exe versions: none
[debug] Proxy map: {}
[generic] 67282: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 67282: Downloading webpage
WARNING: URL could be a direct video link, returning it as such.

Thanks for this great tool :+1:

This was actually due to a bug (see #4753) which has been fixed by 61ca9a8. The embedded (YouTube/vimeo/DailyMotion) and native lelombrik.net videos should be caught by the generic extractor in the next release of youtube-dl. Thanks for the report.

I believe this issue to be fixed in youtube-dl 2<IP_ADDRESS> and newer. See our FAQ if you need help updating.

I confirm the fix in version 2<IP_ADDRESS>
Thanks


add package Ombrelin/plexrich

[ x] Have you signed the Contributor License Agreement?
[ x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x ] Have you tested your manifest locally with winget install -m <manifest>?

Microsoft Reviewers: Open in CodeFlow

Hello,
thank you for your response.
I have an issue with the "Silent" attribute of my manifest. I specified it (/VERYSILENT in my case since I use InnoSetup) :
Installers:
  - Arch: x64
    InstallerType: EXE
    Url: https://github.com/Ombrelin/plex-rich-presence/releases/download/v1.5/plex-rich-presence-setup-1.5.exe
    Sha256: 2B61DC6FB1E786D4FE88FFFCC7E09F142E046EF447278DD25E04F2FC3EB5BC67
    Language: en-US
    Silent: /VERYSILENT

But when I validate, I get :

Manifest Warning: Unknown field. Field: Silent Line: 18, Column: 5
And
Manifest Warning: Silent and SilentWithProgress switches are not specified for InstallerType exe. Please make sure the installer can run unattended.

It seems that my Slient field is not properly detected. I don't understand why. Do you have any clue about that ?
Thank in advance

Greetings
Looks like this is INNO installer.
if you download the EXE and run it with the /? you will see the options.
Here is what you can do.

remove the the line      Silent: /VERYSILENT
replace the InstallerType of EXE with Inno


Even with clustering, map causes app to become unresponsive with large dataset

May need to restrict the map functionality to only when there are less than 1000 records selected. Even at 5,000, there's a substantial slowdown.
dc.js can potentially handle much more data than that

I'm sure there are other optimizations I could add, but the map no longer seems to hang the rendering of the DC charts on initial load. It's still not super fast, but I'm using the trick of calling clearLayers() and addLayers() as a batch (rather than adding each marker via an individual addLayer() call, which made a big difference. See, e.g., https://github.com/Leaflet/Leaflet.markercluster/issues/59
Committed this change in: 392d8db162a2e523b925a4e4d93c3e30bb35ad50


use hive.openshift.io/v1

/approve
/retest

/hold
This guy is hitting the issue of not being able to use var expansion in the second stage of the build.
We don't deploy it on hive, it's not a blocker for https://github.com/openshift/hive/pull/924


Initial cut of primitives from piet-scene

Pulls in the primitives from the piet-scene crate, replacing the geometry and path types with those from kurbo. There are a few alterations to naming and docs and the addition of some convenience "builder" methods to making constructing various types easier.
There are more types to add to this crate-- specifically things related to fonts and text. I though I'd keep the initial PR smallish, covering just enough to serve current piet-scene needs.
I have a working branch with updates to the full piet-gpu repo to support these changes that is ready to go after this lands.

Cargo metadata and kurbo version have been updated.
I removed the hsl constructors for color (but kept hlc). Happy to spend some time in the future discussing high quality color support as I think this crate is now a suitable place for it.  I kept the (currently) unfortunately named parse module for now because I intend to fill it with some actual parsing machinery in the next PR.
Merging this so we can move forward!


feat(ffe-tabs-react): add props thin and className to TabGroup

This commit adds two new props to the TabGroup component.
Bool thin adds the --thin modifier to remove top and bottom padding.
String className adds given css classes to the tab group.
See #203 for screen shots

Coverage remained the same at 79.329% when pulling 08814dd66ecc357c122726f191f865038a547d9d on add-tab-group-thin-modifier into 5641ae540c8ecf2a2cfd3c266082252da2201512 on develop.

Oh my. I thought prettier was still prettifying my edited lines. Maybe we should re-enable that?
Anyways, I've made some new, prettified commits now.


Option to have Find/Replace in bottom panel instead of tiny widget

There was numerous requests to make font in the Find/Replace widget larger and/or monospace, e.g. #101064, #122065 and #145911. There is even the suggestion to have syntax highlighting of regular expressions in that widget.
However, I think that we need something more radical. I think that we need an alternative to that tiny widget.
It seems that VSCode developers want to make as much space available for text in editor, and because of that they don't want to make that widget larger. And I am always for that that we have as much space for the text in editor, especially with small screens.
But there are situations when we simply need to search very complex patterns in text and that tiny widget is not very practical in such cases. Even more, the space for editor could be reduced significantly if we open Terminal/Output panel anyway. So, I suggest that you add an option to have Find/Replace as a new tab in the bottom panel.
Just take a look how that could be much more observable and user friendly with multi-line input boxes (Find/Replace side by side):

or like this (Find/Replace one above other):

Personally, I would not make these two Find/Replace input boxes symmetrical, but I would use the second, vertical arrangement with the single-line Replace input box. Firstly, because the replacement string is usually much shorter than the Find string. Secondly, I suppose it would be harder for implementation to have two symmetrical boxes when resizing that panel; if the Replace input box is a single-line on the bottom of the panel, I think the code for resizing the panel would be simpler.
By the way, if you use the same editing control for the Find/Replace input boxes as it is in the main editor, I think that you don't need to fear how to implement different colors for syntax highlighting of regular expressions since the themes already have support for these elements, like "keyword.control.anchor.regexp", "punctuation.definition.group.regexp", "punctuation.definition.character-class.regexp" and so on, which could look like this:

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


update package for react native > 0.60.0

@johniak
please update for react native > 0.60
version 1.0.2 have problem with auto Link in new react native
any update???

I'm having the same problem

@mskarimi
you can use this package instead react-native-background-color


"value" argument must not be a number error in Electron and Web App Examples

Steps to reproduce:
Follow the tutorial until the insert new mutations portion in both Electron and Web App tutorials. Following error shows up in the console:

I was looking at this more closely and checking in safe_app to understand if it would make sense to support an entry's key to be either numeric or string, but it seems that in SCL we are always passing it as an array of bytes and I guess they are treated in SCL as a string, so even if we were kinda supporting both types in our safe-app-nodejs API we were internally doing the convertion to/from string always. So, it seems that we can probably just keep it as is and fix the tutorials boilerplates as you @manavbp were doing in your PR https://github.com/maidsafe/safe_examples/pull/410
I in parallel sent a PR to safe-app-nodejs with additional tests for inserting and fetching entryes with strings and numbers. https://github.com/maidsafe/safe_app_nodejs/pull/345


Update python dependency for arm32.v7 image.

For version 1.4.3 of azure-iothub-device-client python package, it's recommended that  version of boost is >= 1.58. (Se pypi description).
resin/raspberrypi3-python Is based of jessie images from resin, where the highest available libboost-python is 1.55.
This causes all sorts of problems running on Raspberry Pi. The docker file should be updated to support the latest release of azure-iothub-device-client.

@FluxReality , the updated template is merged into our develop branch, you could run cookiecutter https://github.com/Azure/cookiecutter-azure-iot-edge-module --checkout develop to have a try.

Hi @FluxReality , our new python cookiecutter package is released now. For arm32v7 image, it is using libboost-python1.62.0 now. You could create a new Python Module with our VS Code IoT Edge extension.


Issue 104 advanced intermediate outputs

Resolve #104
Allow defining lists of outputs in the pipeline JSON
Add new methods get_outputs, get_output_names and get_output_variables.
Modify output_ argument behavior in MLPipeline fit and predict methods.

Codecov Report

Merging #105 into master will increase coverage by 0.79%.
The diff coverage is 89.9%.

@@            Coverage Diff            @@
##           master    #105      +/-   ##
=========================================
+ Coverage   77.31%   78.1%   +0.79%
=========================================
  Files           5       5
  Lines         626     676      +50
=========================================
+ Hits          484     528      +44
- Misses        142     148       +6

Impacted Files
Coverage Δ

mlblocks/mlpipeline.py
87.72% <89.9%> (+2.26%)
:arrow_up:

mlblocks/datasets.py
32.9% <0%> (-3.23%)
:arrow_down:

Continue to review full report at Codecov.

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


An error occurred while running subprocess cordova

C:\IonicApp\LIMSApp>ionic cordova platform add andriod

cordova platform add andriod --save
Using cordova-fetch for andriod
Failed to fetch platform andriod
Probably this is either a connection problem, or platform spec is incorrect.
Check your connection and platform name/version/URL.
Error: cmd: Command failed with exit code 1 Error output:
npm ERR! code E404
npm ERR! 404 Not Found: andriod@latest

npm ERR!      C:\Users\User\AppData\Roaming\npm-cache_logs\2018-10-09T13_46_01_190Z-debug.log
[ERROR] An error occurred while running subprocess cordova.
    cordova platform add andriod --save exited with exit code 1.

    Re-running this command with the --verbose flag may provide more information.

C:\IonicApp\LIMSApp>ionic cordova platform add android@latest

cordova platform add android@latest --save
Using cordova-fetch for cordova-android@latest
Platform android already added.
[ERROR] An error occurred while running subprocess cordova.

    cordova platform add android@latest --save exited with exit code 1.

    Re-running this command with the --verbose flag may provide more information.

C:\IonicApp\LIMSApp>ionic cordova platform add android@latest --verbose
ionic:cli-utils Terminal info: { tty: true, ci: false } +0ms
ionic:cli-utils CLI global options: { _: [ 'cordova', 'platform', 'add', 'android@latest' ], help: null, h: null, verbose: true, quiet: null, interactive: true, color: true, confirm: null, json: null, project: null, '--': [] } +0ms
ionic:cli-utils:lib:project Project type from config: Ionic Angular 3 (ionic-angular) +0ms
ionic:cli-utils Project name: undefined +227ms
ionic:cli Context: { binPath: 'C:\Users\User\AppData\Roaming\npm\node_modules\ionic\bin\ionic', libPath: 'C:\Users\User\AppData\Roaming\npm\node_modules\ionic', execPath: 'C:\IonicApp\LIMSApp', version: '4.1.2' } +0ms
ionic:cli-utils:lib:integrations:cordova:config Using config.xml: C:\IonicApp\LIMSApp\config.xml +0ms

cordova platform add android@latest --verbose --save
No scripts found for hook "before_platform_add".
Using cordova-fetch for cordova-android@latest
saving exact
Running command: cmd "/s /c ""C:\Program Files\nodejs\npm.cmd" install cordova-android@latest --production --save-exact""
Command finished with error code 0: cmd /s /c ""C:\Program Files\nodejs\npm.cmd" install cordova-android@latest --production --save-exact"
Removing "cordova-" prefix from cordova-android
Platform android already added.
CordovaError: Platform android already added.
at C:\IonicApp\LIMSApp\node_modules\cordova\node_modules\cordova-lib\src\cordova\platform\addHelper.js:145:35
at _fulfilled (C:\IonicApp\LIMSApp\node_modules\cordova\node_modules\q\q.js:854:54)
at C:\IonicApp\LIMSApp\node_modules\cordova\node_modules\q\q.js:883:30
at Promise.promise.promiseDispatch (C:\IonicApp\LIMSApp\node_modules\cordova\node_modules\q\q.js:816:13)
at C:\IonicApp\LIMSApp\node_modules\cordova\node_modules\q\q.js:624:44
at runSingle (C:\IonicApp\LIMSApp\node_modules\cordova\node_modules\q\q.js:137:13)
at flush (C:\IonicApp\LIMSApp\node_modules\cordova\node_modules\q\q.js:125:13)
at process._tickCallback (internal/process/next_tick.js:61:11)
[ERROR] An error occurred while running subprocess cordova.

    cordova platform add android@latest --verbose --save exited with exit code 1.

    Re-running this command with the --verbose flag may provide more information.

ionic:cli-framework:utils:process onBeforeExit handler: process.exit received +0ms
ionic:cli-framework:utils:process onBeforeExit handler: running 1 queued functions +16ms
ionic:cli-framework:utils:process error while killing process tree for 9476: { Error: Command failed: taskkill /pid 9476 /T /F
ionic:cli-framework:utils:process ERROR: The process "9476" not found.
ionic:cli-framework:utils:process
ionic:cli-framework:utils:process     at ChildProcess.exithandler (child_process.js:276:12)
ionic:cli-framework:utils:process     at emitTwo (events.js:126:13)
ionic:cli-framework:utils:process     at ChildProcess.emit (events.js:214:7)
ionic:cli-framework:utils:process     at maybeClose (internal/child_process.js:915:16)
ionic:cli-framework:utils:process     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
ionic:cli-framework:utils:process   killed: false,
ionic:cli-framework:utils:process   code: 128,
ionic:cli-framework:utils:process   signal: null,
ionic:cli-framework:utils:process   cmd: 'taskkill /pid 9476 /T /F' } +133ms
ionic:cli-framework:utils:process Error from function 0 in exit queue: { Error: Command failed: taskkill /pid 9476 /T /F
ionic:cli-framework:utils:process ERROR: The process "9476" not found.
ionic:cli-framework:utils:process
ionic:cli-framework:utils:process     at ChildProcess.exithandler (child_process.js:276:12)
ionic:cli-framework:utils:process     at emitTwo (events.js:126:13)
ionic:cli-framework:utils:process     at ChildProcess.emit (events.js:214:7)
ionic:cli-framework:utils:process     at maybeClose (internal/child_process.js:915:16)
ionic:cli-framework:utils:process     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
ionic:cli-framework:utils:process   killed: false,
ionic:cli-framework:utils:process   code: 128,
ionic:cli-framework:utils:process   signal: null,
ionic:cli-framework:utils:process   cmd: 'taskkill /pid 9476 /T /F' } +3ms
ionic:cli-framework:utils:process onBeforeExit handler: exiting (exit code 1) +2ms
Please can any one tell me what is the problem it is really frustration.
I an uninstall and install  Cordova , andriod and all other packages 10 times .
But noting is working.
I just want to run my app in android emulater because I am using SQlite.
If any other option pleas let me know.

This happens on ionic cordova build and ionic cordova run commands for me as well.  It started when I moved to ionic 4.2.1

I don't get why this doesn't get ANY ATTENTION AT ALL from the devs.
I receive this error since I updated to Ionic CLI 4.2.1, I can't use the livereload feature because of this :/
I'm getting this error on all "ionic cordova ..." commands:
ionic cordova run android
ionic cordova build ios
ionic cordova platform add
etc
My ionic info:
Ionic:

   ionic (Ionic CLI)  : 4.2.1 (/usr/local/lib/node_modules/ionic)
   Ionic Framework    : ionic-angular 3.9.2
   @ionic/app-scripts : 3.2.0

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : android 7.1.1, ios 4.5.5
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 2.2.0, (and 6 other plugins)

System:

   Android SDK Tools : 26.1.1 (/Users/francovalerio/Library/Android/sdk)
   ios-deploy        : 2.0.0
   NodeJS            : v8.11.2 (/usr/local/bin/node)
   npm               : 6.4.0
   OS                : macOS
   Xcode             : Xcode 9.4.1 Build version 9F2000

So for me, the problem was occurring during plugin installation.  It was so hard to find because the log that said "Failed to fetch plugin ...." was buried with a ton of other logs, and doesn't look like an error at all.  Once I fixed the plugin install issue, everything was working fine.


borgbackup closure depends on tox, detox, eventlet and more

Issue description
when adding borgbackup to my system packges,
to my surprise without actually compiling it sill depended on tox, detox eventlet and maybe more
i am also surprised that tests for nix package installs use tox, since that usage is misplaced
nix should run tests directly against the installed version

cc maintainer @nckx


[Chore] Add conditional check in ERC1155 claimTo test using TW_SECRET_KEY

#3442  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jnsdls and the rest of your teammates on  Graphite


Added option to select different hash type in badphotocopy.

I added option to select different hash type to emulate different effect.  We may add in more hash type later if needed.
Examples from existing hash type:

Examples from new hash type:

This looks good and I'll merge it once we get the Github Actions checks to pass. Please sync your fork with the latest commits to the official branch.
To fix this, run these in order:

pip install -r requirements-dev.txt
pre-commit install
pre-commit run --all-files
git commit -m ...

This will install pre-commit which will make sure we don't commit any code without running black etc. After you install pre-commit, when you try to git commit, it will run the same checks we have in Github Actions, and fix any files that don't match. Then you can commit again and everything should pass.
Let me know if you have any trouble

This looks good and I'll merge it once we get the Github Actions checks to pass. Please sync your fork with the latest commits to the official branch.
To fix this, run these in order:
1. `pip install -r requirements-dev.txt`

2. `pre-commit install`

3. `pre-commit run --all-files`

4. `git commit -m ...`

So how long usually it took for each step?
This run for half an hour now, is this normal?

Depending on the network speed, but it shouldn't take so long.
Once they are all downloaded, they will be cached for future use, so you should only have to download once unless parts are updated.

Depending on the network speed, but it shouldn't take so long.
Once they are all downloaded, they will be cached for future use, so you should only have to download once unless parts are updated.

Alright, i will retry again later, thanks.

@proofconstruction  I executed those command lines, but looks like facing error to add new commit:
Output from command lines:

Error:

Could you advise again?

I closed this pull request and reverted the changes from my end. However, i'm still facing the permission denied issue when i try to re-commit again, do you have any idea?

I think this may be due to committing from inside GitHub Desktop. Can you try from inside a terminal? (Windows Terminal is really good)

I think this may be due to committing from inside GitHub Desktop. Can you try from inside a terminal? (Windows Terminal is really good)

I tried but looks like it's the same:

I guess i will need to refork and manually replace the updates again, thanks for the help.

This stackoverflow thread seems to indicate that it's a known bug. Maybe if you update your PATH variable?
I'm not familiar with development on Windows, sorry.

This stackoverflow thread seems to indicate that it's a known bug. Maybe if you update your PATH variable?
I'm not familiar with development on Windows, sorry.

Is alright, i tried that previously , non of that working, and it is only occur on this repo, but not the other repo. I will try to refork and try again, thanks.


Select flag and labels logic change

Resolves #218 .
The naming could be changed a bit but the idea is the same. I've tested the changes on a sample test locally.
Will update the test files soon.
This PR adds a new flag --select-labels which will AND the labels ( similar to the previous behaviour of --labels ) and change the --labels flag behaviour to OR the labels.

/ok-to-test

@harshanarayana the tests need to be updated, I'm a bit busy atm. Will find time to update the tests asap and get this ready.

/test

/re-test

/test all


[Windows 10] cut off taskbar icon

Describe the bug
On Windows 10 and Ferdi 5.4.3 the taskbar icon seems to be cut off and looks like bad quality.
To Reproduce
Install Ferdi and open it.
Look at icon in the taskbar.
Expected behavior
Uncut and high resolution icon.
Screenshots

Desktop (please complete the following information):

OS: Windows 10 1909
Browser Ferdi
Version 5.4.3

Additional context
Seems to be related to https://github.com/getferdi/ferdi/issues/159 and https://github.com/getferdi/ferdi/issues/272

The bug seems to be resolved as of Version 5.4.4 beta3.


Fixed Forever.stop() killing parent process on Forever.exit()

Fixed Forever.stop() killing parent process on Forever.exit()
Added exitOnStop option to Forever.config
Changed exitOnStop default false
Fixed exitOnStop always being true

Could you please fix tests?


Node Test

Hey @fchollet,
getting an issue with
import msvcrt ModuleNotFoundError: No module named 'msvcrt'
But only in this particular test 🙄


Some change from office laptop

I accepted your code which is written from an office laptop.

OK. Keep going step by step we will figure out all GitHub operations based on the project that we did.


Addition to SoundFile class

How would this new feature help increase access to p5.js?
Most appropriate sub-area of p5.js?

[ ] Accessibility (Web Accessibility)
[ ] Build tools and processes
[ ] Color
[ ] Core/Environment/Rendering
[ ] Data
[ ] DOM
[ ] Events
[ ] Friendly error system
[ ] Image
[X] IO (Input/Output)
[ ] Localization
[ ] Math
[ ] Unit Testing
[ ] Typography
[ ] Utilities
[ ] WebGL
[X] Other (specify if possible)

New feature details:
Hi @therewasaguy, the "SoundFile" class has a lot of functions for reporting the status of a song in a sketch. I believe the API can be simplified by creating one function "SoundFile.status()" to return all the parameters at once in JSON format.
I would like to work on this. :)

@nakul-shahdadpuri  i encourage your thoughts , it would great if you present things in particular.
like what parameters do you think should be merged and how  will it increase the usecase of this library,
we should  keep in mind the consistent dilevery with intuitive docs of apis to users, accordingly we have to look how this thing wil go as feasible ! :)


Saved State Forward Compatibility

Is it possible to preserve saved state forward compatibility?  That is, can the tool be updated to allow saved states created in 4.1 to work in 4.2?  Currently they do not.
It turns out we have a lot of users linking directoy to the GPV from their own websites using saved states, so they can have the right zoom levels, active selections, etc.  Here's an example from our Community Development Department (planning):
http://gis.cambridgema.gov/map/Viewer.aspx?state=027248041504
This state link throws an error with 4.2:
http://gis.cambridgema.gov/gpv42/Viewer.aspx?state=027248041504
The first image below and the attached text file contain a more detailed error message.  The second image below gives some more details of the saved sate.

error_message.txt

My install is updated and works:
http://gis.cambridgema.gov/gpv42/Viewer.aspx?state=027248041504


Enable #!share for sharing between .NET subkernels and JavaScript / out of proc subkernels

Sharing variables between .NET subkernels (C#, F#, PowerShell) uses the #!share magic command and requires kernels to inherit DotNetKernel.
This doesn't currently work with remote kernels, including JavaScript kernels and connected kernels.
Layering a command/event-based interaction over the in-proc implementation and allowing #!share to use that could unify this experience.

Related: #1552


Fix useLazyQuery

Hi there!
I'm currently writing an application using this project (which is great btw!) but I'm encountering a few problems.
One of them is that useLazyQuery seems to have some pieces missing. Notably, how do I re-trigger the same query, but with different parameters? The returned execute callback doesn't allow to do that...

Hi! Have you tried passing in a ref/reactive as a param? Like:
const { $client } = useNuxtApp()
const text = ref('robert')

const { data } = await $client.hello.useLazyQuery(text)

setTimeout(() => {
  text.value = 'clement' // updating the ref should rerun the query
}, 500)


Upgrade dependencies for Xcode 6.3

CI hasn't been updated for Xcode 6.3 yet, but the tests build and pass locally.

Looks good to me.


textarea won't resize onload version 1.0.0-alpha.2

It seems like the problem encountered here persists:
https://github.com/Dogfalo/materialize/issues/4613
can someone confirm this or it is just me. I have a text that is longter than the normal textarea but the resize on load does not work:
$(document).ready(function(){     $('#user_edit_about_me').trigger('autoresize'); });
Again this is version 1.0.0-alpha.2
https://codepen.io/ensayofr/pen/NwoBWK

This is an error in the docs. You should be using the function:
M.textareaAutoResize($('#textarea1'));
Fixed in 36f97281a12e1cc00dd6eb0833ae5ca5da433fbf.


Fix code

The CreatePane return void but the catch return OutputWindowPane that can not compile

@lindexi : Thanks for your contribution! The author, @gregvanl, has been notified to review your proposed change.

Thanks!
#sign-off


fix: fixing vulnerability: server-side request forgery in axios

PR summary
axios 1.7.2 allows SSRF via unexpected behavior where requests for path relative URLs get processed as protocol relative URLs.
Fixes:

also due to the changes in in node-sdk-core, under the following PR: https://github.com/IBM/node-sdk-core/commit/901ece06d6f7897164b54d58f316da94ae1fc5da
I had to re-adjust the UT files to ensure the functions used for testing are pulled from ibm-cloud/sdk-test-utilities versus its original directory.
As a result of those needed manual changes, a PR generated by dependabot - https://github.com/IBM/networking-node-sdk/pull/134 was failing.
Snippet of one of the many failing messages:
FAIL test/unit/direct-link.v1.test.js
  ● Test suite failed to run
    TypeError: Cannot destructure property 'getOptions' of 'unitTestUtils' as it is undefined.
      26 |
      27 | const {
    > 28 |   getOptions,
         |   ^
      29 |   checkUrlAndMethod,
      30 |   checkMediaHeaders,
      31 |   expectToBePromise,
      at Object.getOptions (test/unit/direct-link.v1.test.js:28:3)

PR Checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[x] Bugfix
[ ] Feature
[x] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x ] No

Other information

@srukotla your fix didn't solve the problem. The builds are failing.  Please review this.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


homebrew cask

from the readme: for learning purpose (electron/react/deploying electron apps)
so maybe add homebrew cask as a way of deploying it

Just installed 0.4.0 through brew cask, so it looks like this was done! The issue can probably be closed 🙃

@AndrewSB weird, I didn't do anything related to homebrew yet.

It must have been someone else in the community.


deploying embedding model in same way as LLM

🚀 The feature, motivation and pitch
can we deploy the embedding model such as bge,e5 etc. using vllm? if yes could u point to the resources for it.
Alternatives
No response
Additional context
No response

🚀 The feature, motivation and pitch
can we deploy the embedding model such as bge,e5 etc. using vllm? if yes could u point to the resources for it.
Alternatives
No response
Additional context
No response

Have you solved it?


[Home/Auctions] Lots By Artists You Follow > II

Follow up to https://github.com/artsy/emission/pull/851.
(Comments inline)
Skip New Tests

Fails

:no_entry_sign:

No CHANGELOG added.

:no_entry_sign:

Missing Test Files:

src/lib/Scenes/Favorites/Components/Artworks/__tests__/index-tests.tsx
src/lib/Scenes/Home/Components/Sales/Relay/__tests__/SalesRenderer-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

Fails

:no_entry_sign:

No CHANGELOG added.

:no_entry_sign:

Missing Test Files:

src/lib/Scenes/Favorites/Components/Artworks/__tests__/index-tests.tsx
src/lib/Scenes/Home/Components/Sales/Relay/__tests__/SalesRenderer-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

Whew! Lots of Relay struggling in this one related to container composition after I consolidated queries into a single <QueryRenderer />. I'm sure I'm missing something somewhere but as soon I moved the query into the root, i could no longer keep the paginationContainer in LotsByArtistsYouFollow and had to move it down as a direct descendent and then pass data in; it seems like a child that uses a fragmentContainercan't render a child that has apaginationContainerand expect to connect thepaginationContainer` data back to the root query.

Fails

:no_entry_sign:

No CHANGELOG added.

Warnings

:warning:

Missing Test Files:

src/lib/Scenes/Favorites/Components/Artworks/__tests__/index-tests.tsx
src/lib/Scenes/Home/Components/Sales/Relay/__tests__/SalesRenderer-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

Warnings

:warning:

Missing Test Files:

src/lib/Scenes/Favorites/Components/Artworks/__tests__/index-tests.tsx
src/lib/Scenes/Home/Components/Sales/Relay/__tests__/SalesRenderer-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

Warnings

:warning:

Missing Test Files:

src/lib/Scenes/Favorites/Components/Artworks/__tests__/index-tests.tsx
src/lib/Scenes/Home/Components/Sales/Relay/__tests__/SalesRenderer-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

Warnings

:warning:

Missing Test Files:

src/lib/Scenes/Favorites/Components/Artworks/__tests__/index-tests.tsx
src/lib/Scenes/Home/Components/Sales/Relay/__tests__/SalesRenderer-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

Ok flipped lots_by_followed_artists back on and followed a bunch of people and all seems good.  If everything looks all right I believeee this is ready to ship.

Warnings

:warning:

Missing Test Files:

src/lib/Scenes/Favorites/Components/Artworks/__tests__/index-tests.tsx
src/lib/Scenes/Home/Components/Sales/Relay/__tests__/SalesRenderer-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

Warnings

:warning:

Missing Test Files:

src/lib/Scenes/Favorites/Components/Artworks/__tests__/index-tests.tsx
src/lib/Scenes/Home/Components/Sales/Relay/__tests__/SalesRenderer-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

This isn't working  for me locally, after I get to the first load of additional works, the current page (e.g. page 1 of artworks)  disappears - looking at network now

Looking like there's likely a data issue on the bid increment strat for some of the Sales

OK,  this looks 👍  to me when my data wasn't going awry


Cleaning up Dashboard

Goal
The ALB Application dashboard did not differentieate ELB from Target Request.
Target Counts:
https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-cloudwatch-metrics.html

The number of HTTP response codes generated by the targets. This does not include any response codes generated by the load balancer.

ELB Counts:

The number of HTTP response codes that originate from the load balancer.                                                  This count does not include any response codes generated by the targets.

Review

[ ] @Pocket/backend

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix Terms/Privacy text responsive and Login Center

Related Issue
Fixes : #1131
Description
Terms and condition and privacy policy page text responsive for small screen.
Make Login page in center to avoid overlapping.
Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)

Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

@Suchitra-Sahoo Please check it and merge !
Thank You !


Help: how to list all kube-vip nodes and make vip move faster ?

how to list all kube-vip nodes  ?
how to configure to let vip move to another kubernetes master faster when one of the kubernetes master is down ?
in my situation:
after we shutdown a kube master node manually , kube cluster not available immediately.  about 2 mins later , vip moved , and kube cluster available again .

dan@k8s01:~$ k get pods -A -o wide | grep -i vip
kube-system   kube-vip-cloud-provider-0                  1/1     Running   0          9m56s   <IP_ADDRESS>      k8s04   <none>           <none>
kube-system   kube-vip-k8s01                             1/1     Running   0          7m17s   <IP_ADDRESS>   k8s01   <none>           <none>
kube-system   kube-vip-k8s02                             1/1     Running   0          7m14s   <IP_ADDRESS>   k8s02   <none>           <none>
kube-system   kube-vip-k8s03                             1/1     Running   0          6m39s   <IP_ADDRESS>   k8s03   <none>           <none>

The above can quickly list where kube-vip is running?
Also if the failover is taking 2 minutes then ARP broadcasts appear not be updating the network correctly. Can you attach any logs and configuration (yaml) to this issue please.

Thanks reply! @thebsdbox
we followed this tutorials to configure kube-vip,   https://kube-vip.io/control-plane/  ，From the beginning to ‘remaining-nodes’ part.

E0710 07:14:07.439440       1 leaderelection.go:321] error retrieving resource lock kube-system/plndr-svcs-lock: Get "https://server01048:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/plndr-svcs-lock": dial tcp <IP_ADDRESS>:6443: connect: connection refused
E0710 07:14:07.706652       1 leaderelection.go:322] error retrieving resource lock kube-system/plndr-cp-lock: Get "https://server01048:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/plndr-cp-lock": dial tcp <IP_ADDRESS>:6443: connect: connection refused
I0710 07:14:12.265002       1 leaderelection.go:253] successfully acquired lease kube-system/plndr-cp-lock
time="2021-07-10T07:14:12Z" level=info msg="Node [server01048] is assuming leadership of the cluster"
time="2021-07-10T07:14:12Z" level=info msg="This node is starting with leadership of the cluster"
time="2021-07-10T07:14:12Z" level=info msg="Broadcasting ARP update for <IP_ADDRESS> (fa:16:3e:4b:81:e4) via eth0"
I0710 07:14:12.268240       1 leaderelection.go:253] successfully acquired lease kube-system/plndr-svcs-lock
time="2021-07-10T07:14:12Z" level=info msg="Beginning watching services for type: LoadBalancer in all namespaces"
time="2021-07-10T07:14:12Z" level=info msg="Service [kubernetes] has been addded/modified, it has no assigned external addresses"
time="2021-07-10T07:14:12Z" level=info msg="Service [kube-dns] has been addded/modified, it has no assigned external addresses"
time="2021-07-10T07:14:12Z" level=info msg="Service [calico-kube-controllers-metrics] has been addded/modified, it has no assigned external addresses"
time="2021-07-10T07:14:12Z" level=info msg="Service [calico-typha] has been addded/modified, it has no assigned external addresses"
time="2021-07-10T07:14:15Z" level=info msg="Broadcasting ARP update for <IP_ADDRESS> (fa:16:3e:4b:81:e4) via eth0"
time="2021-07-10T07:14:18Z" level=info msg="Broadcasting ARP update for <IP_ADDRESS> (fa:16:3e:4b:81:e4) via eth0"
time="2021-07-10T07:14:21Z" level=info msg="Broadcasting ARP update for <IP_ADDRESS> (fa:16:3e:4b:81:e4) via eth0"
time="2021-07-10T07:14:24Z" level=info msg="Broadcasting ARP update for <IP_ADDRESS> (fa:16:3e:4b:81:e4) via eth0"
About 2mins later, we can ping to vip again:
64 bytes from <IP_ADDRESS>: icmp_seq=84 ttl=64 time=0.494 ms
64 bytes from <IP_ADDRESS>: icmp_seq=85 ttl=64 time=0.451 ms
64 bytes from <IP_ADDRESS>: icmp_seq=86 ttl=64 time=0.412 ms
64 bytes from <IP_ADDRESS>: icmp_seq=87 ttl=64 time=0.434 ms
From <IP_ADDRESS> icmp_seq=94 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=100 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=104 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=110 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=117 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=129 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=132 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=142 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=151 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=154 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=157 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=160 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=161 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=179 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=182 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=186 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=189 Destination Host Unreachable
64 bytes from <IP_ADDRESS>: icmp_seq=192 ttl=64 time=2416 ms
64 bytes from <IP_ADDRESS>: icmp_seq=193 ttl=64 time=1417 ms
64 bytes from <IP_ADDRESS>: icmp_seq=194 ttl=64 time=417 ms
64 bytes from <IP_ADDRESS>: icmp_seq=195 ttl=64 time=0.392 ms
64 bytes from <IP_ADDRESS>: icmp_seq=196 ttl=64 time=0.383 ms

Ah!
You only have two control plane nodes! Etcd will not like that, you need to have an odd number in order for the clustering to work!

Closing issue as there has been no updates for 10 days.. please feel free to re-open.


Content Change Request

Which part of the repository is your change request related to?
MVDS Page
Please describe which content you would expect here and tell us how to solve this request
Add information on what a person should know (or which skills they should have) prior to experimenting with MVDS.
Can you already provide any alternative (or updated) content that can/should replace the existing content?
No.
Additional notes
No.

Closing this issue as the MVDS page will be part of IDS Testbed repository.
Changes already reflected in the pull request there


Add the ability to zoom in and pan around the SVG diagram.

Added the ability to zoom in on a part of a diagram.

Double click a non-clickable area of the diagram to zoom it in.
Hold the control key and use the mouse wheel/scroll to zoom in/out
Click and hold a zoomed in diagram and move mouse to pan
Pinch on trackpad/mobile to zoom in and out

Still to do : Add button(s) to control zoom under the sag, add button to reset to original size, add some sort of bounding box so that the zoomed element doesn't take over the full screen.

@dirkgroot Would love to get your input on this early stage concept.

Found a better SVG Zooming library that gives me the ability to zoom within the svg's container and add control buttons but lost the ability to require the control key to be held down to zoom with mouse.

Still working on this functionality. I moved the Pan/Zoom version of the SVG to a modal. I was unhappy with how having it directly on the page was interfering with normal site usage as you couldn't;t scroll up/down the page when the mouse was over the svg area.
I still need to figure out a good style for the 'zoom' button that surfaces the modal.
For the modal itself I used the built in Bulma CSS's modal and their sample JS so that additional resources would not have to be added to the site. I also added a new property to the DSL to allow users to enable/disable this functionality. When disabled (default) the JS for the modal and pan/zoom are excluded from the generated html.
@dirkgroot @jp7677 Any feedback?

This is what I ended up with for the positioning of the 'zoom/pan' button. I split the FigCaption in to two lines, one for the title and one for the download links and added the zoom button as a link there.

here is what I did for the positioning of the 'zoom/pan' button that opens the modal window. I split the caption on the diagram in to two lines, first for the diagram title and the second for the download links. When the Zoom feature is enabled the extra link is added to the list.

Hi @qtzar sorry again for the late response, I promise, this one is next on my list.
Already a heads up, could you please organize new browser dependencies according to https://github.com/avisi-cloud/structurizr-site-generatr/pull/328 ?

@jp7677 Much appreciated & I have setup the browser dependency as requested.

@qtzar Please see https://github.com/avisi-cloud/structurizr-site-generatr/pull/334


Add achievements

It makes sense to add some achievments. It could be for example cards for some solved words which you could earn.


Remove FixtureMultipleYield

This exception is not used anywhere
Cleaned up unused imports in errors.py

@igboyes  We should raise an exception in the case that a generator fixture yields more than once. I think right now that just won't be caught.
We could also remove it and pick an applicable builtin exception. What do you think?

What is a good example of a generator fixture?

What is a good example of a generator fixture?

Generator fixture is any fixture with a yield. It is there for when there is cleanup steps to be done when the workflow instance.
For example, a generator fixture could be used to create a temporary directory.  work_path is implemented in a similar way.
@fixture
def temp_path():
     tempdir = Path(...)
     tempdir.mkdir()
     yield tempdir
     shutil.rmtree(tempdir)

This promises that the temp_path will be available to the workflow and that
when the workflow completes, or fails, or is cancelled the code after the yield will be invoked.

Yes. That is the same concept from pytest. I meant a built-in fixture.
You want to catch a situation like this:
@fixture
def temp_path():
     tempdir = Path(...)
     tempdir.mkdir()
     yield tempdir
     yield tempdir
     shutil.rmtree(tempdir)

Correct?

Yes. That is the same concept from pytest. I meant a built-in fixture.
You want to catch a situation like this:
@fixture
def temp_path():
     tempdir = Path(...)
     tempdir.mkdir()
     yield tempdir
     yield tempdir
     shutil.rmtree(tempdir)

Correct?

Yes that's the situation. Right now the shutil.rmtree line would never run and there'd be no notification to the developer about it

Issue opened: https://linear.app/virtool/issue/VIR-784/raise-exception-when-there-are-multiple-yield-statements-in-a-fixture
I'll close this PR. I think the exception should end with Error to follow the Python exception naming convention.


Improve note input box + Add indicator if there is a note

[ ] batter input field
[ ] batter view of note
[ ] indication of note on the version item in the table

#46 Done


Merge stacked_area_chart into standard_time_series

With the addition of the stack_mode parameter to the stacked area chart dashboard item, it now completely subsumes standard_time_series - by setting stack_mode to none, you get exactly the same rendering as standard_time_series.
Merge stack_mode into standard time series, and have the factory() method produce a StandardTimeSeries instance for either value of item_type, which should seamlessly convert existing data. That will make all standard time series easily convertible between stacked/no stack/streamgraph/percent view.

Done


Support Rust-style "where" syntax for generic parameters

Suggestion
🔍 Search Terms

rust where

✅ Viability Checklist

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code: this would introduce new syntax that would currently be an error.
[x] This wouldn't change the runtime behavior of existing JavaScript code: this would be a purely type-level construct
[x] This could be implemented without emitting different JS based on the types of the expressions: this would get erased at runtime
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.): this would be a purely type-level feature
[x] This feature would agree with the rest of TypeScript's Design Goals. It's more inspired by the syntax in Rust than attempting to replicate it

⭐ Suggestion
Instead of writing:
function getProperty<T, K extends keyof T>(obj: T, key: K) {
  return obj[key];
}

You'd also be allowed to write:
function getProperty<T, K>(obj: T, key: K)
  where
  T extends object,
  K extends keyof T
{
  return obj[key];
}

It might even be preferable to leave T and K off the generic parameters list (the bit inside <..>), since the intent is most likely for them to be inferred based on obj and key, but we'll get to this later.
For a type alias, instead of:
type Pick<T extends object, K extends keyof Type> = {[k in K]: T[k]};

you'd also be able to write:
type Pick<Type, Keys> = {[K in Keys]: Type[K]}
  where
  Type extends object,
  Keys extends keyof Type;

This mirrors an identical syntax in Rust (see also Rust RFC 135). It would solve three distinct problems:

Legibility
When a function or type alias has many generic arguments, each with an extends clause and a default value, it can get difficult to pick out what the type parameters are, or even how many of them there are. A where clause lets you push the generic bounds and defaults outside the parameter list, improving its legibility.

Scoped type aliases
There's no easy type-level equivalent of factoring out a variable to eliminate duplicated expressions like you would in JavaScript. A where clause would make it possible to introduce type aliases that don't appear in the generic parameter list.

Partial inference for functions
See #10571. It's not currently possible to specify one type parameter for a generic function explicitly but allow a second one to be inferred. By creating a place to put types that's not the parameter list, a where clause would make this possible.

There are examples of all three of these in the next section.
💻 Use Cases

Legibility
There are many examples of complicated generic parameter lists out there. Here's one chosen at random from react-router:
export interface RouteChildrenProps<Params extends { [K in keyof Params]?: string } = {}, S = H.LocationState> {
    history: H.History;
    location: H.Location<S>;
    match: match<Params> | null;
}

It's clearer that there are two type parameters if you move the constraints and default values out of the way:
export interface RouteChildrenProps<Params, S> where
  Params extends { [K in keyof Params]?: string } = {},
  S = H.LocationState
{
    history: H.History;
    location: H.Location<S>;
    match: match<Params> | null;
}

The existing workaround for this is to put each type parameter on its own line:
export interface RouteChildrenProps<
  Params extends { [K in keyof Params]?: string } = {},
  S = H.LocationState
> {
    history: H.History;
    location: H.Location<S>;
    match: match<Params> | null;
}

It's a judgment call which you prefer. I find the other two uses more compelling!
Scoped type aliases
With complicated generic types and functions, it's common to have repeated type expressions. Here's a particularly egregious example (source):
import * as express from 'express';
/** Like T[K], but doesn't require K be assignable to keyof T */
export type SafeKey<T, K extends string> = T[K & keyof T];
export type ExtractRouteParams<Path extends string> = ...;  // see https://twitter.com/danvdk/status/1301707026507198464

export class TypedRouter<API> {
  // ...
  get<
    Path extends keyof API & string,
  >(
    route: Path,
    handler: (
      params: ExtractRouteParams<Path>,
      request: express.Request<ExtractRouteParams<Path>, SafeKey<SafeKey<API[Path], 'get'>, 'response'>>,
      response: express.Response<SafeKey<SafeKey<API[Path], 'get'>, 'response'>>,
    ) => Promise<SafeKey<SafeKey<API[Path], 'get'>, 'response'>>
  ) {
    // ... implementation ...
  }
}

wow that's a lot of repetition! Here's what it might look like with where:
export class TypedRouter<API> {
  // ...
  get<Path extends keyof API & string>(
    route: Path,
    handler: (
      params: Params,
      request: express.Request<Params, Response>,
      response: express.Response<Response>,
    ) => Promise<Response>
  )
  where
    Params = ExtractRouteParams<Path>,
    Spec = SafeKey<API[Path], 'get'>,
    Response = SafeKey<Spec, 'response'>
  {
    // ... implementation ...
  }
}

By introducing some local type aliases in the where list, we're able to dramatically reduce repetition and improve clarity. We should actually remove Path from the type parameters list since the intention is for it to be inferred, but let's save that for the next example.
Existing workarounds include factoring out more helper types to reduce duplication, or introducing an extra generic parameter with a default value, e.g.:
class TypedRouter<API> {
  // ...
  get<
    Path extends keyof API & string,
    Spec extends SafeKey<API[Path], 'get'> = SafeKey<API[Path], 'get'>,
  >(
    route: Path,
    handler: (
      params: ExtractRouteParams<Path>,
      request: express.Request<ExtractRouteParams<Path>, SafeKey<Spec, 'response'>>,
      response: express.Response<SafeKey<Spec, 'response'>>,
    ) => Promise<SafeKey<Spec, 'response'>>
  ) {
    // ... implementation ...
  }
}

This still repeats the type expression twice (SafeKey<API[Path], 'get'>), but since it's used three times, it's a win! This is kinda gross and creates confusion for users about whether Spec is a meaningful generic parameter that they'd ever want to set (it isn't).
Partial inference for functions
Sometimes you want to infer one generic parameter to a function and have the others be derived from that (#10571). For example (following this post):
declare function getUrl<
  API, Path extends keyof API
>(
  path: Path, params: ExtractRouteParams<Path>
): string;

This fails if you pass API explicitly and try to let Path be inferred:
getUrl<API>('/users/:userId', {userId: 'bob'});
//     ~~~ Expected 2 type arguments, but got 1. (2558)

This problem could be solved by using where to introduce a type parameter that's not part of the generics list:
declare function getUrl<API>(path: Path, params: ExtractRouteParams<Path>): string
  where Path extends keyof API;

This would allow Path to be inferred from the path parameter while still specifying API explicitly and enforcing the extends keyof API constraint. The only workarounds I'm aware of now involve introducing a class or currying the function to create a new binding site:
declare function getUrl<API>():
  <Path extends keyof API>(
    path: Path,
    params: ExtractRouteParams<Path>
  ) => string;

A where clause would help with the general problem that there are two reasons to put a type parameter in the generic parameters list for a function:

You want users to specify it
You want it to be inferred

and there's no syntax for distinguishing those. A where clause would let you do that.

Scoped type aliases are enough to get my vote, but does it have to follow Rust's syntax? Might there be a better syntax to do this?

Scoped type aliases are enough to get my vote, but does it have to follow Rust's syntax? Might there be a better syntax to do this?

@00ff0000red it doesn't have to follow Rust's syntax exactly, I mostly offer that as evidence that it's not a completely crazy idea (and I assume much of the discussion in the Rust RFC would also be relevant to TypeScript).

@00ff0000red it doesn't have to follow Rust's syntax exactly, I mostly offer that as evidence that it's not a completely crazy idea (and I assume much of the discussion in the Rust RFC would also be relevant to TypeScript).

Seems good. But I guess there must once be a good reason for not using "where" as generic constraint.
Because C# does use similar syntax https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/generics/constraints-on-type-parameters
They are designed by the same person, so... I am curious too :)

Seems good. But I guess there must once be a good reason for not using "where" as generic constraint.
Because C# does use similar syntax https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/generics/constraints-on-type-parameters
They are designed by the same person, so... I am curious too :)

Scoped type aliases are enough to get my vote

Related: #40780 / #30979.

Scoped type aliases are enough to get my vote

Related: #40780 / #30979.

Seems good. But I guess there must once be a good reason for not using "where" as generic constraint.
Because C# does use similar syntax https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/generics/constraints-on-type-parameters
They are designed by the same person, so... I am curious too :)

Good point @ShuiRuTian, now I feel sheepish about calling this Rust-style syntax :) Updated the title of the issue and added a note.

Seems good. But I guess there must once be a good reason for not using "where" as generic constraint.
Because C# does use similar syntax https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/generics/constraints-on-type-parameters
They are designed by the same person, so... I am curious too :)

Good point @ShuiRuTian, now I feel sheepish about calling this Rust-style syntax :) Updated the title of the issue and added a note.

Looking at the Rust RFC, another motivator there was being able to specify constraints that involved multiple type parameters. So something like:
const users = [
  ['John', 'Doe'],
  ['Bobby', 'Droppers'],
] as const;

function greet<First, Last>(first: First, last: Last)
  where [First, Last] extends typeof users[number] {
  // ...
}

I wouldn't say this is common, but I can think of a few situations I've run into where it would have been convenient.

Looking at the Rust RFC, another motivator there was being able to specify constraints that involved multiple type parameters. So something like:
const users = [
  ['John', 'Doe'],
  ['Bobby', 'Droppers'],
] as const;

function greet<First, Last>(first: First, last: Last)
  where [First, Last] extends typeof users[number] {
  // ...
}

I wouldn't say this is common, but I can think of a few situations I've run into where it would have been convenient.

So it's actually not a syntax sugar, it's introduced a new way to restrain the generic types right?

So it's actually not a syntax sugar, it's introduced a new way to restrain the generic types right?

So it's actually not a syntax sugar, it's introduced a new way to restrain the generic types right?

If the constraint involves multiple parameters, yes. That wouldn't be in v1 of this proposal, I just wanted to flag it as a possibility that this syntax opens up.

So it's actually not a syntax sugar, it's introduced a new way to restrain the generic types right?

If the constraint involves multiple parameters, yes. That wouldn't be in v1 of this proposal, I just wanted to flag it as a possibility that this syntax opens up.

I don't love the syntactic positioning of this or the idea that it would be a place to introduce type parameters, but I'm compelled by this as an alternative approach to some other feature requests (namely upper-bounded generics). Namely you could imagine writing things like this
interface Array<T> {
  // Proposing that "where" go at the end of the type parameter list
  includes<U where T extends U>(el: U): boolean
}

I don't love the syntactic positioning of this or the idea that it would be a place to introduce type parameters, but I'm compelled by this as an alternative approach to some other feature requests (namely upper-bounded generics). Namely you could imagine writing things like this
interface Array<T> {
  // Proposing that "where" go at the end of the type parameter list
  includes<U where T extends U>(el: U): boolean
}

Also, if the where clauses didn't influence inference at all, which I think would be desirable, then you could solve non-inferential type parameter (#14829) use cases:
declare function assertEqual<T, U where U extends T, T extends U>(actual: T, expected: U): boolean;
const g = { x: 3, y: 2 };
// Would correctly error
assertEqual(g, { x: 3 });

Also, if the where clauses didn't influence inference at all, which I think would be desirable, then you could solve non-inferential type parameter (#14829) use cases:
declare function assertEqual<T, U where U extends T, T extends U>(actual: T, expected: U): boolean;
const g = { x: 3, y: 2 };
// Would correctly error
assertEqual(g, { x: 3 });

Also, if the where clauses didn't influence inference at all, which I think would be desirable, then you could solve non-inferential type parameter (#14829) use cases:
declare function assertEqual<T, U where U extends T, T extends U>(actual: T, expected: U): boolean;
const g = { x: 3, y: 2 };
// Would correctly error
assertEqual(g, { x: 3 });

Or perhaps
declare function assertEqual<T, U where [U, T] extends [T, U]>(actual: T, expected: U): boolean;

Also, if the where clauses didn't influence inference at all, which I think would be desirable, then you could solve non-inferential type parameter (#14829) use cases:
declare function assertEqual<T, U where U extends T, T extends U>(actual: T, expected: U): boolean;
const g = { x: 3, y: 2 };
// Would correctly error
assertEqual(g, { x: 3 });

Or perhaps
declare function assertEqual<T, U where [U, T] extends [T, U]>(actual: T, expected: U): boolean;

Linking a few other related issues for local type aliases that I missed earlier #23188 (2018), #41470 (2020)

The topic of scoped types aliases came up again recently as a tangent in #26349 (on partial inference).  This issue seems maybe the most lively/promising place to move the discussion to where it's still on-topic.  To briefly summarize the tangent, it started when I mentioned a gist where I explore the synergy between partial inference and what I've called "private types" (e.g. private T = infer, where the T really is a type parameter, but one that the API author doesn't want a caller to ever write explicitly, hence private).  This led to some agreement that the concept is particularly useful (though I'm not sure the proposal in this issue actually handles this particular synergy well).
Stepping back, let me try to summarize the bigger picture.  There are three main contexts where type aliases are useful:

in type nodes (which often themselves show up in top-level type aliases), e.g.type Foo<T> =
    // ...somehow define alias U...
    Bar<U>;

but might also be relevant as anonymous inline types, e.g.type Mapped<T> = {
  [K in keyof T]: /* ...somehow define alias U... */ Bar<U>
}

in classes/interfaces, e.g.class Foo<T> {
  // ...somehow define alias U...
  bar(): U {...}
}

in functions, e.g.function foo<T /* ...somehow define alias U... */>(arg: T): U {...}

These contexts are unfortunately somewhat opposed to each other: e.g. #23188 and #41470 both propose "type node" syntaxes, which support inline use in mapped types, but wouldn't (directly) benefit the classes/functions case at all (whereas e.g. #7061 wouldn't help the inline case).  Syntax proposals that "live inside the <...>" are more general, though they leave out the inline/anonymous usage, and they risk conflating aliases with parameters (see concerns by @RyanCavanaugh about abusing type parameters on #32525 and #45311).
In addition to simply local aliases, I also want to call attention to several distinct-but-related user needs, which have varying degrees of relevance across the three contexts:

Inference.  Local aliases may want to participate in partial inference (this is the case I mentioned above, from #26349), where the alias probably wants to be treated as a real type parameter as far as all the bookkeeping goes; this would obviously depend on a definition-site opt-in rather than call-site, which is what #26349 tracks.
Constraints.  There's a handful of bugs around constraint checking (#42388, #51385).  The current <T extends ...> syntax is very limited: it can only set an upper bound (rather than a lower bound, see #14520), and because this bound participates in inference, it disallows cycles (which further limits its usefulness quite a bit).
Associated types.  There are some use cases for making these type aliases available in outside scopes as well, e.g. #9889.  This obviously adds some additional complications, and I see it as a bonus rather than a requirement.

The proposed syntax options include the following:

semicolon inside the type parameter list, to separate the public from the private parameters (note that this has some analogue with #52811 private (runtime) function parameters)
where, either inside or outside the parameter list
satisfies to introduce a non-bounding constraint (i.e. T satisfies IsStringLiteral<T>, which would be a cycle otherwise)
private or # for private type parameters
_ or infer to opt-into partial inference, either at the call-site or the definition-site
as for introducing a "yoda"-style alias (SomeComplicatedExpression<T> as U)
let..in or {{ /*...aliases…*/ type=... }} for an anonymous approach

The original tangent was about "private types".  As referenced above, putting these into the bracketed type parameter list is potentially a mistake, but it's currently the only hammer we have available, so I think a lot of developers are biased in favor of it.  Even without direct language support for private type parameters, it's possible to at least partially emulate it with an impossible-to-write optional type parameter, though this only works when inference is off (i.e. the non-optional parameters are explicitly specified).
I'd therefore consider definition-site partial inference and arbitrary constraints to be the two most important requirements (with aliasing being a nice bonus, but not strictly required).  The former should hopefully follow from #26349, so the main question to me is how to express arbitrary constraints.  I like satisfies as an analog to extends inside the parameter list - the RHS of this clause could reference all parameters in the list (no order dependence) and would be checked after all inference, leading to an error (or a failed overload match, for overloaded functions) if the constraint fails.  This could be abused if necessary to resolve arbitrary conditions
function foo<T satisfies SomeCondition<U> extends true ? T : never, U extends T>(...)

and it's likely to be relatively straightforward to implement in place.


Moving Pull Requests from Codeplex

I am the author of 6 of the 11 pull requests on CodePlex (https://entityframework.codeplex.com/sourcecontrol/list/contributions), would it be helpful for me to move those over myself to ensure the proper alerts are registered to come to me as necessary?
Brandon

@brandondahler Thanks! We have assigned the PRs on the CodePlex repo to team members for review, so you may want to wait a bit until you get some feedback, but if you want to go ahead and resubmit them here and close them there that works too.

No problem :).


cannot validate certificate for x.x.x.x because it doesn't contain any IP SANs even when server_name passed

global:
  scrape_interval:     15s
  evaluation_interval: 15s
  scrape_timeout: 15s

# Alertmanager configuration
#alerting:
#  alertmanagers:
#  - static_configs:
#    - targets:
      # - alertmanager:9093

# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
  # - "first_rules.yml"
  # - "second_rules.yml"

scrape_configs:
  - job_name: 'kubernetes-pods'
    kubernetes_sd_configs:
    - role: pod
      api_server: 'https://api.internal.example.com'
      basic_auth:
        username: 'admin'
        password: 'password'
      tls_config:
        ca_file: '/opt/prometheus-2.1.0.linux-amd64/ca.crt'
        server_name: kubernetes
        insecure_skip_verify: false
    scheme: https
    relabel_configs:
    - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_scrape]
      action: keep
      regex: true
    - source_labels: [__meta_kubernetes_pod_namespace,__meta_kubernetes_pod_label_name]
      separator: '/'
      target_label: job
    - source_labels: [__meta_kubernetes_pod_node_name]
      target_label: node
  - job_name: 'kubernetes-nodes'
    kubernetes_sd_configs:
    - role: node
      api_server: 'https://api.internal.example.com'
      basic_auth:
        username: 'admin'
        password: 'password'
      tls_config:
        ca_file: '/opt/prometheus-2.1.0.linux-amd64/ca.crt'
        server_name: kubernetes
        insecure_skip_verify: false
    scheme: https
    relabel_configs:
    - action: labelmap
      regex: __meta_kubernetes_node_label_(.+)

I am getting the below error.
Get https://x.x.x.x:10250/metrics: x509: cannot validate certificate for x.x.x.x because it doesn't contain any IP SANs

and the kubernetes cluster is running on aws using kops and the certificate has subject CN=kubernetes
can anybody help me on how to resolve this issue?

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


Disable kamal-proxy version vX.Y is too old ERROR

It's been an hour since the release of new kamal-proxy and we have started seeing errors on deployment.
Releasing the deploy lock...
  Finished all in 58.8 seconds
  ERROR (RuntimeError): Exception while executing on host X.X.X.X: kamal-proxy version v0.8.0 is too old, please reboot to update to at least v0.8.1
Error: Process completed with exit code 1.

Deployments should not fail for this reason. :)
Perhaps there is a way to disable this?

Currently each Kamal release is pinned to a specific Kamal Proxy version. So if you upgrade Kamal to a new version that is pinned to a different proxy version, then you also need to update the proxy along with it. (The message you see here comes from Kamal, not Kamal Proxy; that's where we enforce the restriction).
You can continue to use Kamal 2.2.0 instead of 2.2.1 if you're not ready to do the kamal proxy reboot step.
We are planning to relax this restriction somewhat (perhaps allowing minor or patch version differences) but keeping both sides closely in step has been valuable while we've been building out the features in both.
I'm closing this since it's really a Kamal question rather than a Kamal Proxy one. Would suggest opening a discussion on the Kamal repo if you'd like to discuss some alternatives, though.


Scenarios are not running: SignalRBroadcast, SignalREcho

Some scenarios have stopped running:

Scenario
Environment
Last Run

SignalRBroadcast
Linux, Physical, http, KestrelSockets
2019-10-27 19:43:37Z

SignalREcho
Linux, Physical, http, KestrelSockets
2019-10-27 19:49:41Z

Logs

These are running.


Insert alternate spellings

Ok, @jobcurtis, I decided to take the "actual" spelling from the artists' Wikipedia titles. I also made this file consistent with the artists in #288, which required adding a few more rows. This is ready for review.

Thanks for the review, merging now.

If we're serious about keeping duplicates down in the future then one of the things we might want is a tool for merging duplicate artists. I think it would be pretty straightforward to implement. Probably worth waiting to see how many duplicates we actually get though.

Yep, agreed. I've done it manually a few times:

Identify the canonical artist with CanonicalArtistId1 and alternate spelling artist with AlternateArtistId2. Those are the only two inputs needed.
UPDATE Artworks SET ArtistId = CanonicalArtistId1 WHERE ArtistId = AlternateArtistId2;
INSERT INTO AlternateSpellings VALUES (CanonicalArtistId1, (SELECT Name FROM Artists WHERE ArtistId = AlternateArtistId2));
DELETE FROM Artists WHERE ArtistId = AlternateArtistId2;

A tool or a short script could run the steps a bit quicker.


Refresh travis

This PR is to make .travis.yml up to date.
I removed `circle.yml as it was quite outdated and was not triggering builds.

Nice job.  Thanks for taking the lead!

Thanks for reviewing and useful suggestions, @prjemian!


[enhancement] Include Icons with Menu API

This will make life easier for mobile and web devs

Implemented in https://github.com/fafadiatech/newscout_web/pull/190


Handling flipped ref alleles in dosage files (encoded 0 to 2)

Original Program's handling of flipped reference alleles operates for dosage files encoded -1, 0, 1 (continuous). This update would handle SNPs with flipped reference alleles with dosages encoded 0, 1, 2 (continuous). The 0:2 dosage format is used in PrediXcan example dosage files and produced if using the convert_plink_to_dosage.py script.
Hope this is helpful,
-Hannah C Ainsworth, Kip D Zimmerman, Carl D Langefeld from Wake Forest's Center for Public Health Genomics

Thanks a lot! This was definitely something we had to address. We'll merge it with other changes soon.


Refitter fails to generate FormData parameter for file upload

Describe the bug
Refitter ignores the IFormFile parameter decorated with [FromForm] which is used for receiving file upload.
The controller parameter is completely missed in the generated refit interface method.
If it worked, the generated method would have [Multipart] as method annotation and StreamPart as the type for IFormFile parameter
https://github.com/reactiveui/refit#multipart-uploads
Support Key: 8hz0dgn
OpenAPI Specifications
"requestBody": {
"content": {
"multipart/form-data": {
"schema": {
"type": "object",
"properties": {
"formFile": {
"type": "string",
"format": "binary"
}
}
},
"encoding": {
"formFile": {
"style": "form"
}
}
}
}
}
Additional context

@richardhu-lmg thanks for taking the time to report this. Multi-part upload support is currently not implemented yet but I will add it to my to-do list

Any estimate re when the fix will be implemented?

@richardhu-lmg thanks for taking the time to report this. Multi-part upload support is currently not implemented yet but I will add it to my to-do list

Any estimate re when the fix will be implemented?

@richardhu-lmg Sorry, I can't really honestly say when I'll implement this. I'll try looking into how complex this is tonight, and if it's simple enough, it will probably be done in a few minutes or hours. Otherwise, it will be completed when I find the time.
@richardhu-lmg You are more than welcome to give it a shot yourself and create a pull request, I'm very open and lenient regarding pull requests

@all-contributors please add @richardhu-lmg for bugs

I have an implementation  where the following OpenAPI v3 specifications
{
   "openapi":"3.0.2",
   "paths":{
      "/foo/{id}/files":{
         "post":{
            "summary":"uploads a file",
            "operationId":"uploadFile",
            "parameters":[
               {
                  "name":"id",
                  "in":"path",
                  "description":"Id of the foo resource",
                  "required":true,
                  "schema":{
                     "type":"integer",
                     "format":"int64"
                  }
               }
            ],
            "requestBody":{
               "content":{
                  "multipart/form-data":{
                     "schema":{
                        "type":"object",
                        "properties":{
                           "formFile":{
                              "type":"string",
                              "format":"binary"
                           }
                        }
                     },
                     "encoding":{
                        "formFile":{
                           "style":"form"
                        }
                     }
                  }
               }
            },
            "responses":{
               "200":{
                  "description":"successful operation"
               }
            }
         }
      }
   }
}

Generates the following Refit interface
public interface IApiClient
{
    [Multipart]
    [Post("/foo/{id}/files")]
    Task UploadFile(long id, StreamPart formFile);
}

@richardhu-lmg Will this work for you?


[Extension Bug]

Extension – Title

Author:

Description
Steps To Reproduce

The current behavior
The expected behavior
Raycast version
Version:

@roelvangils Did you miss something? 😄
Please fill the data for an issue next time 😉


[Broker] Fix call sync method in async rest api for internalUnloadTopic

Motivation
Avoid call sync method in async rest API for PersistentTopicsBase#internalUnloadTopic.
Modifications

Use async instead of sync method.

Verifying this change

[x] Make sure that the change passes the CI checks.

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: ( no)
The schema: ( no )
The default values of configurations: ( no)
The wire protocol: ( no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation

[x] no-need-doc

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks


gulp: generate documentation after bundling

pls merge

This has nothing to do with the autogen though?

It is, actually it fixing that error which you mentioned. The problem was that documentation were generated before creation of folder. However there are number of other heroku-related issues. I already close to finish...


Without unique project names, even with different --remote-repo-url=, projects with duplicate filepaths are merged

snyk monitor --project-name="backend/requirements.txt" --remote-repo-url="https://github.com/snyk-tech-services/cloud"
and
snyk monitor --project-name="backend/requirements.txt" --remote-repo-url="https://github.com/mrzarquon/server"
Will update the same project in Snyk just moving the grouping between the two different remote-repo-urls.
A fix will:

check for git, use git remote url if no --remote-repo-url is provided, to set a $SNYK_BASENAME var, or use --basename value if provided
update the projectname call to include --project-name="${SNYK_BASENAME}/${project}"

This should ensure each project is unique going forward.

Fixed in #30

I think this is no longer the case (the glitch was fixed) but probably fine to leave things as is


ci: provide npm publish from PR pipeline

@pradel ,
This might be useful for proposals testing

@pradel ,
What's your vision here?

@antongolub sounds good, I will review the prs once I have a bit of time, these days are quite busy (in about 1/2 weeks)


JupyterLab Extensions

Should users be allowed to add their own JupyterLab extensions? Are there any others we should have by default?
I don't know the answer to either of these questions, but I'll look around to see if I can find anything else that could be useful to an average user!

In answer of the second question.
For quality of life purposes, it seems useful to have the jupyterlab-lsp extension. It provides extended features for autocompletion, function signatures, and error detection. For similar purposes, the jupyterlab variable inspector might be handy, as it shows active variables, much like the Python Spyder IDE. It's especially useful in a notebook, since blocks can be activated non-linearly, and it's hard to tell what variables have already been instantiated.
Lastly, the jupyterlab debugger might be a good addition. I think it might also cover the utility of the variable inspector above, but I'm not sure if it provides details into what variables actually contain (which the inspector does).

In answer of the second question.
For quality of life purposes, it seems useful to have the jupyterlab-lsp extension. It provides extended features for autocompletion, function signatures, and error detection. For similar purposes, the jupyterlab variable inspector might be handy, as it shows active variables, much like the Python Spyder IDE. It's especially useful in a notebook, since blocks can be activated non-linearly, and it's hard to tell what variables have already been instantiated.
Lastly, the jupyterlab debugger might be a good addition. I think it might also cover the utility of the variable inspector above, but I'm not sure if it provides details into what variables actually contain (which the inspector does).

@mat-adamec would you think you will have time to investigate some interesting extensions useful for Python development?

https://github.com/jtpio/jupyterlab-system-monitor
https://github.com/jupyter-lsp/jupyterlab-lsp
https://github.com/jupyterlab/debugger (The debugger extension is shipped by default with JupyterLab 3.x and doesn't need to be installed manually.)
https://github.com/microsoft/gather
https://github.com/jupyter/nbdime
https://github.com/jupyterlab/jupyterlab-latex

@oshadura What sort of investigations are you hoping for? Just a write-up of what useful functionality I think each one adds that might be useful for HEP?
I can try to do this. Is it possible to make a local JupyterLab instance for myself to test them, or will they be added to coffea-casa? I've only ever worked with local JupyterHubs.


Consider fetching balances for Improved Efficiency

Currently, balances are stored from a CSV file and used solely for the computation of assets_sum, which is necessary for generating the solvency proof.
However, storing balances might not be essential since the smart contract does not take balances as call data.
Instead, it fetches the balances of addresses directly on-chain.

Closing issue and moving it to #105


Forum migration broke all the old links

The KSP forums are migrated from vBulletin to IPS, unfortunaly this migration broke all the old forum links. I asked KasperVld if he could make a redirection script so that the old links redirect the user to the new links, but looks like that isn't possible.

Olympic1: I noticed that the old links doesn't work anymore, I thought you would redirect them to the respective thread.

KasperVld: Turns out it's not possible, sorry. I did look into it though.

Turns out that the new forum links also need to have to be changed
Old forum link
http://forum.kerbalspaceprogram.com/threads/100067
New Link
http://forum.kerbalspaceprogram.com/index.php?/topic/100067-/

Will send out an email to modders and have them update their links as they see fit.

Thx


Unable to compile

The url "https://jitpack.io/com/github/jellysquid3/sodium-fabric/1.16.x~next-SNAPSHOT/maven-metadata.xml" never responds leading to the build failing to get necessary file.
Screenshot:

Putting the url in a browser doesnt work either:

Seems like jitpack is having issues... for now, you can just grab a precompiled jar from https://github.com/comp500/Indium/runs/1743990522
If you need to compile it yourself, you'll probably have to add a maven local publishing task to Sodium, then run it and set Indium to compile using that as a dependency.

Seems like jitpack is having issues... for now, you can just grab a precompiled jar from https://github.com/comp500/Indium/runs/1743990522
If you need to compile it yourself, you'll probably have to add a maven local publishing task to Sodium, then run it and set Indium to compile using that as a dependency.

I think I'll just use the precompiled jar, since im no expert. By the way thanks for the jar, other than that I have no idea whats going on with jitpack.

I think I'll just use the precompiled jar, since im no expert. By the way thanks for the jar, other than that I have no idea whats going on with jitpack.

I didn't even know the "Actions" tab existed, guess I learned something new today.

I didn't even know the "Actions" tab existed, guess I learned something new today.

Jitpack seems to be back up :)

Jitpack seems to be back up :)


Create UI for wish stage

Codecov Report
Base: 0.00% // Head: 0.00% // No change to project coverage :thumbsup:

Coverage data is based on head (8c28d1c) compared to base (26d0263).
Patch coverage: 0.00% of modified lines in pull request are covered.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


feat: add ng-add schematic

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

ng add only adds ngworker@lumberjack as a dependency.
Karma is used for unit tests.

Issue Number: N/A
What is the new behavior?

ng add also registers Lumberjack (LumberjackModule.forRoot()) and optionally the console and HTTP drivers with the console driver being registered by default.
Jest is used for unit tests.

Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information
Continuation of #51.

Commits 4602686-f4e49a5 broke schematic tests.

@NachoVazquez Please resolve the change requests you addressed.

In the schematics-e2e job when using Angular 9.0, the following warning is displayed and the matrix leg fails:

ts-jest[versions] (WARN) Version 3.7.5 of typescript installed has not been tested with ts-jest. If you're experiencing issues, consider using a supported version (>=3.8.0 <5.0.0-0). Please do not report issues in ts-jest if you are using unsupported versions.


09/10/2018 05:48 : Create Pull Request for branch prTesting_2018091005 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Ranger docker build fails

ranger docker build fails due to the solr version being references having been removed from download site.
Updating.

this is working now.


Stop supporting IE 11

New Features
Since React 18 plan to stop supporting IE 11, I think it is better to stop supporting IE 11 at version 5.x. Version 4.x will continue to support IE11.
What is the new or updated feature that you are suggesting?
Stop supporting IE 11
Why should this feature be included?
This change reduces bundle size and improves performance.
What docs changes are needed to explain this?
It is necessary to add "IE 11 is not supported" to release note.

Honestly there's basically nothing to do here :)  Redux is so tiny that there's nothing IE11 specific, really.
That said, the master branch (which may, eventually, someday, become v5 if we ever get around to releasing it) has already been updated to target a more modern syntax.  React-Redux v8 also has that same change.
So, I'm going to close this as "already done / nothing else to do".


Extended display area not rendered on resize until minimized and refocused

ec12246190f27e5261d05a6bf70f7dd7bc7a11b3 should fix it, you might want to try the latest release v0.5.6

This is still an issue for me. v0.12.17 on an AMD GPU.


Serious Rebuild Scale Bug - 100% repro

Describe the bug
When rebuilding the same character over and over as you would with lod the position bone is reduced in size.
Environment (please complete the following information):

Unity Version: 2018.2.6f1
UMA Version: v2.8.1 RC2
Platform Build (if not editor): Editor

To Reproduce
Steps to reproduce the behavior:

Load 'UMA Core Demo - Texture LOD' Scene
Modify the "UMASimpleLOD.cs" script line 142 into "bool changedSlots = true;" this will force a rebuild of the mesh and not just the as well as the textures.
Press Play
In scene view find a character at a high lod 3+
Select the Position Bone, write down the scale
Move closer with WASD
Observe that when changing LOD the Position Bone changes scale.

Expected behavior
It is expected that when rebuilding the same recipe you get the same results.
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
I originally noticed this problem with the power tools, but was able to reproduce it in UMA Vanilla.

This was fixed in Release 2.8.1 Thanks!


How to get PRs merged

Seems like this project is dead? We would love to get this PR merged (or commented on) https://github.com/mwunsch/handlebars.scala/pull/57, because then we don't need to maintain an internal forked version. What can we do to speed up the process? Do you need more maintainers?

The network graph now looks like this, which is a clear indicator that there is continued interest in the project, but the original maintainer(s) don't have time to take care of it anymore:

If noone objects, I would go ahead and fork this repo to a neutral repository and add the people that have worked on forks as maintainers.

The network graph now looks like this, which is a clear indicator that there is continued interest in the project, but the original maintainer(s) don't have time to take care of it anymore:

If noone objects, I would go ahead and fork this repo to a neutral repository and add the people that have worked on forks as maintainers.

Hi @nightscape and others. If you'd like to take over mainternship of this repo, I'd be open to discussion. You are correct, I no longer have the time nor the interest in this project, and would happily turn it over to someone who finds it useful.

Hi @nightscape and others. If you'd like to take over mainternship of this repo, I'd be open to discussion. You are correct, I no longer have the time nor the interest in this project, and would happily turn it over to someone who finds it useful.

Hi @mwunsch, thanks for responding so quickly!
I see two ways forward:

We leave the Git repo under your handle and you add a few people as admins on it. The harder part is setting up publishing so that you don't have to do anything manual. For this we would need a bit of your time w.r.t. Sonatype login & PGP key setup.
We move the Git repo to a new organization and change the Maven organization (and probably for consistency purposes the package names as well) correspondingly. In that case it would be just like setting up a new Sonatype account for which we probably wouldn't need your time and help.

Do you have any preferences?

Hi @mwunsch, thanks for responding so quickly!
I see two ways forward:

We leave the Git repo under your handle and you add a few people as admins on it. The harder part is setting up publishing so that you don't have to do anything manual. For this we would need a bit of your time w.r.t. Sonatype login & PGP key setup.
We move the Git repo to a new organization and change the Maven organization (and probably for consistency purposes the package names as well) correspondingly. In that case it would be just like setting up a new Sonatype account for which we probably wouldn't need your time and help.

Do you have any preferences?

@mwunsch did you find time to consider the options?
If you don't care, just add me as an admin to the project and I will take it from there :wink:
I would probably go for option 2 then.

@mwunsch did you find time to consider the options?
If you don't care, just add me as an admin to the project and I will take it from there :wink:
I would probably go for option 2 then.

@nightscape My preference is for Option 2!

@nightscape My preference is for Option 2!

@mwunsch ok! If you can add me as admin to the repo I'll take it from there :+1:

@mwunsch ok! If you can add me as admin to the repo I'll take it from there :+1:


Update to WinMLRunner v1.3.0

Closing this PR, as the Windows ML Container docs, in their current state, have been retired.


OpenID Connect specification non-conformance

OpenID Connect specification non-conformance
The redirect URI for the Open ID Connect endpoint includes a fragment (OAuth 2.0 / RFC 6749)
https://datatracker.ietf.org/doc/html/rfc6749#section-3.1.2
The redirection endpoint URI MUST be an absolute URI as defined by
[RFC3986] Section 4.3.  The endpoint URI MAY include an
"application/x-www-form-urlencoded" formatted (per Appendix B) query
component ([RFC3986] Section 3.4), which MUST be retained when adding
additional query parameters.  The endpoint URI MUST NOT include a
fragment component.

Additional context
This is preventing connection to the Microsoft Azure Active Directory OpenID endpoint.

The # symbol in the provided URL is used by Angular for internal view routing. Because Angular is a single page application, the # is used in URLs as client-side navigation fragments to switch between component views. The hash location strategy does usually cause issues with external URLs though (e.g. SEO) because of the fact they are client-side only.
It is possible to setup a new page route with a direct URL which will internally navigate to the correct component to continue authorization.

@oughnic This change has been merged to the develop branch now. Once you have a release including this fix, the redirect URL will now be:
https://{domain}/redirects/open-id-connect-redirect.html


Background image doesn't change fast enough upon login

This is assuming a user has selected dark mode and login. The logo will change to the dark mode logo on the loading screen, but the background image doesn't keep up.

Yes I noticed this too, it will be fixed by the latest PR

Merged. Kudos @digitaltwinnn


fixed #1431

What is the purpose of the change
fixed #1431
Brief changelog
prevent invoking log method when getLogHost exception occurs.
Verifying this change
Unit Tests OK

Codecov Report

Merging #1435 into master will decrease coverage by 0.03%.
The diff coverage is 20%.

@@            Coverage Diff             @@
##           master    #1435      +/-   ##
==========================================
- Coverage   31.59%   31.55%   -0.04%
==========================================
  Files         682      682
  Lines       33035    33048      +13
  Branches     6592     6595       +3
==========================================
- Hits        10436    10429       -7
- Misses      20748    20767      +19
- Partials     1851     1852       +1

Impacted Files
Coverage Δ

.../java/com/alibaba/dubbo/common/utils/NetUtils.java
14.28% <20%> (-1.39%)
:arrow_down:

...om/alibaba/dubbo/rpc/filter/ActiveLimitFilter.java
83.33% <0%> (-5.56%)
:arrow_down:

...a/dubbo/remoting/transport/netty/NettyChannel.java
61.25% <0%> (-5%)
:arrow_down:

...ubbo/rpc/protocol/dubbo/ChannelWrappedInvoker.java
41.66% <0%> (-4.17%)
:arrow_down:

...bo/remoting/transport/netty/NettyCodecAdapter.java
56.71% <0%> (+1.49%)
:arrow_up:

Continue to review full report at Codecov.

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

Hi, kimming, there are some conflict in your PR #1435. Could you please update the PR, thanks.

Hi @kimmking, I use one simple way to avoid this issue, pls. check https://github.com/apache/incubator-dubbo/commit/70ec90dae80cf1c1537f0dd83f8a844a905ebbdb


Go modules

Moved the project to go modules

this looks heroic (as I was just thinking the same) - 👏

This looks amazing - if I happen to get the goahead to fix up our email situation at work, I'll definitely swing back round to this to see if it works and hopefully contribute some attachment-related stuff.

@tyndyll any chance to get this merged?

@katexochen from what I understand, people gave up on this project and mailpit was made in its stead.  I can recommend it, it fixes some other issues with mailhog that I had in production.

@Asday good to know, is there any official statement on this?

Yes

I personally don't have time to maintain the project anymore, and as I no longer use it, there's little incentive to dedicate time to it like I used to - I have other projects to focus on. But I hear you and I will try to find some time to give it a bit of a spring clean (but I don't know how soon that'll be).


monoid defined in_terms_of_plus:  are 0 and operator+ the good abstraction?

I wonder if 0 and operator+() is the appropriated abstraction. What about an Additive concept that defines zero<M>() -> M and 'add(M, M) -> M'?

Well, the point of that deriving mechanism was convenience, so that a user could easily get a monoid instance for a custom type without having to implement anything in addition (assuming their type has the correct operator and identity element as default constructor).
There might indeed be an argument for the abstraction you describe too, but I have no plans to introduce it right now. Perhaps if my interest in this project is sparked anew at some point.

No problem. It was just a suggestion.


Feature/react16

Add react 16 support

Codecov Report

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

@@            Coverage Diff            @@
##             master       #4   +/-   ##
=========================================
  Coverage          ?   89.65%
=========================================
  Files             ?        2
  Lines             ?       58
  Branches          ?       18
=========================================
  Hits              ?       52
  Misses            ?        6
  Partials          ?        0

Impacted Files
Coverage Δ

src/components/Slider.ts
88.46% <100%> (ø)

src/components/Alert.ts
100% <100%> (ø)

Continue to review full report at Codecov.

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


First New Questionnaire created still allows "copy from existing" model

The questionnaire is being added immediately and not filtering itself out of the existing model list. Copy existing should not show up for the first one created.

"Copy from" option in wizard will be removed, replaced with a per-app "Copy me" option