Existing links to Kubernetes documentation no longer working

Several pages are broken.
https://kubernetes.io/docs/tasks/debug-application-cluster/debug-service/
https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application/

/retitle Existing links to Kubernetes documentation no longer working
This looks to have been caused by PR #32823.
/kind bug
/language en
/triage accepted

This issue has been resolved by the PR #33220.
And I confirm that in content/en/, there exists no link that points to debug-application-cluster/**.md.
/close

I would like to work on this issue. Thanks.
/assign

@jihoon-seo The Whats Next section of the https://kubernetes.io/docs/tasks/debug-application-cluster/debug-service/ is leading to 404 error. Could please double check it and if the error is there, can I go ahead and work on the issue?

@Babapool Yes I see 404 too. Please go ahead!
[Suggestions]
In content/en/docs/tasks/debug/debug-application/debug-service.md
-[Slack](/docs/tasks/debug/overview/#slack) or
+[Slack](https://slack.k8s.io/),

-Visit the [troubleshooting overview document](/docs/tasks/debug/overview/)
+Visit the [troubleshooting overview document](/docs/tasks/debug/)

Sure I will create a new issue and label it as good first issue so that new contributors can work on it :)

Created a new issue 👍  . Thanks @jihoon-seo


fixing mkdirp arguments

I have got error when trying to use the package.
Seems the mkdirp arguments were illegal
I have made the functions async, hope its clearer

Thanks for the PR, @srikanthkyatham! Just wanted to let you know that I've seen it and I should have time in the next few days to review.
I've been thinking about replacing mkdirp with fs.mkdir with the recursive option as true. Any thoughts? Now might be a good time to make that move.

I can check it and update the pr

Hi mjhea0,
seems the recursive option is supported in

v10.12.0 | The second argument can now be an options object with recursive and mode
properties.

If choose this option it would mean node 8 would be broken. How do you wish to handle it.

We should probably drop 8 since it's no longer being maintained.
https://nodejs.org/en/about/releases/
Agreed?

Agreed. We should drop the node 8

Open question, how do you wish to handle the cases where creation of folders fail?
Option

throw an error
ignore the failure and proceed with execution

Could you make it configurable with a fail_silently variable?

Default value is true so it will log the error to console and execution will proceed.
Allow the end user to override this by setting a config variable in cypress.json.

How does that sound?

@srikanthkyatham, your fix works. Just tried it, see #26 for reference

@srikanthkyatham this looks good. any more changes?

@mjhea0 no I that's about it.

@mjhea0, @srikanthkyatham, can you please review #26? Thanks.

Released! https://www.npmjs.com/package/cypress-visual-regression
Thanks for your help. Much appreciated.


Initialization script missing

how to add Initialization script to create server struct

ok solved

UserData: "mkdir hiiii\n mkdir bye",


Scenario scaling functionality uses 'present' value of AREA attribute 'number_of_residences'. It should use the 'future' value.

The scaling does not result in the desired number of residences. e.g. Scaling to 100 residences results in a number of residences that is higher, if the number of residences are higher in the future than in the present. We have determined this is because the scaling functionality uses the following ratio to scale the future numbers:
number_of_residences_for_scaling / present:AREA(number_of_residences)
I think it should be this ratio, though;
number_of_residences_for_scaling / future:AREA(number_of_residences)
Yes, I made up the first of these attributes...
Example:
Scaling to 250 residences for the following situation:

This results in:
193+88=281 residences!
This happens to equal 250 * 8.3 / 7.387

Background
I am creating scaled scenarios for a project John and I are working on. These are due early next week and a lot remains to be done. Hence the priority tag.
Notifying @ChaelKruip and @dennisschoenmakers

I have pushed and deployed a fix. I expected to have to use an ugly hack to achieve this but luckily found a workaround in the latest commit.
It should now work as you expect.

Set new households to 5M
Set old households to 5M
Scale to 1,000 households

The resulting scenario has 500 old and 500 new.

@antw works like a charm! :smile:


New release?

Last release was in August. We have a few minor commits in master that is not released yet. What do you think of releasing 1.4.0 this year?

i honestly don't see any value in releasing, as nothing much changed. using ::class constants seems to be the only change and that is purely a code style thing imho. or is there value in bringing that to the users? is that enough to need a new minor version or could we tag 1.3.1?

We could add https://github.com/Nyholm/psr7 to the message factory discovery (and i would actually make it top 1 in the list since it's the only one that is 100% compatible with PSR7)
And also Artax as an async adapter once the PR has been merged and then release a new version ?

I am big fan of nyholm/psr7 so +1 for adding it.

if we have any valuable things to add, i agree we should do that and then release.

@Nyholm see https://github.com/php-http/discovery/issues/105. This change currently breaks all Magento 2 installations that use mailgun/mailgun-php, resulting in emails not being sent.

Closing this since 1.4 has been released


verify_cert doesn't seem to be set server-side

Describe the bug
Config of "verify_cert" for an ldap server configured to false, appears as true on server UI.
To Reproduce
resource "harbor_config_auth" "ldap" {
  auth_mode             = "ldap_auth"
  ldap_url              = ""
  ldap_search_dn        = ""
  ldap_search_password  = ""
  ldap_base_dn          = ""
  ldap_filter           = ""
  ldap_uid              = "uid"
  ldap_group_base_dn    = ""
  ldap_group_filter     = ""
  ldap_group_membership = "memberof"
  ldap_group_gid        = "cn"
  ldap_group_admin_dn   = ""
  ldap_verify_cert      = false
}

Expected behavior
Verify cert to be false in UI
Additional context
Add any other context about the problem here.

Provider Version [3.9.3]
Terraform Version [1.4.6]
Harbor Version [v2.8.2-d4c34dcc]

hi, thanks for the bug report
I think it's due to the omitempty : https://github.com/goharbor/terraform-provider-harbor/blob/main/models/config.go#L40

fix in : v3.9.4


Filters not working

I tried with the latest code in contact_demo, and for eg in the contacts screen, I tried to search for "last_name" containing some characters. When the page refreshes, the selection (also reflected in the url as query parameters) always goes to the "Equals" selection for the first filtered field. I'm not sure if this is an issue with ex_admin or this codebase.

@smpallen99 : Does this line need any changes? I am seeing some random times where the url has "#{name}_eq" - but, if I manually change it to "#{name}_contains", the filtering starts working.


FabricBetterGrass

CurseForge link
https://curseforge.com/minecraft/mc-mods/fabricbettergrass/
CurseForge Mod Distribution
Allowed
Modrinth link
https://modrinth.com/mod/fabricbettergrass
Source/other link
https://github.com/UltimatChamp/FabricBetterGrass
Mod file size
130.91 KiB
License
Apache License 2.0
What it does
OptiFine's Fancy and Fast better grass on Fabric!
Why should it be in the modpack

OptiFine-parity!
Available for 1.19.3-1.20.6!
There are plans for a NeoForge port once Continuity (and Sodium) updates.

Additional details

This mod is a fork of ArdaGrass.
The mod is, currently, under 'Review' on Modrinth. Now on Modrinth, too!

Testing the mod kind of works. I have these weird zones where the effect isn't applied in fancy mod.

Also switching form off/fast/fancy requires a quit and rejoin of the world, and this is not stated anywhere.
A couple of other things:

The mod depends on midnightLib, which is not in fo. It's not too heavy (50K), but it's a thing to keep in mind.
Have you had any contact/authorization of the original mod dev?
IDEA: it's possible to add a toggle for the mod in the video settings (like optifine does)?

I am also curious about any talks with the original dev, maybe they would be willing to upstream the work you've done? Or better yet, maybe you two can collaborate to maintain the original mod together?
MidnightLib is in FO via Puzzle, so that's not a problem.
The original mod, tracked on #717, had a concern about the current Continuity implementation not being sustainable. Is that addressed in this fork?

I have these weird zones where the effect isn't applied in fancy mod.

That's how it's supposed to work, isn't it? The places where the grass block isn't connected with another grass block below will not be better-grassified.

Also switching form off/fast/fancy requires a quit and rejoin of the world, and this is not stated anywhere.

Hmm... I'll place a comment then, warning the user.

Have you had any contact/authorization of the original mod dev?

No 😕, but the author has abandoned the project, so, I'll doubt he will have any objection. Moreover, it looks like he's not active on GitHub, nowadays...

it's possible to add a toggle for the mod in the video settings

great idea! i think i'll put that in sodium's Quality settings, in the next release

had a concern about the current Continuity implementation not being sustainable. Is that addressed in this fork?

currently, the mod is using the same implementation. I'll take a peek at that...

No 😕, but the author has abandoned the project, so, I'll doubt he will have any objection. Moreover, it looks like he's not active on GitHub, nowadays...

The original mod is made for a specific server and modpack, hence it is made for a specific Minecraft version and not updated very often. You should contact said modpack (see their Discord link on Modrinth) to actually know about it.

That's how it's supposed to work, isn't it? The places where the grass block isn't connected with another grass block below will not be better-grassified.

I remembered that it blended with the block below and on the side (like with a dirt side if the block below it's dirt, stone if it is stone... But maybe it was another mod/resourcepack

Hmm... I'll place a comment then, warning the user.
Isn't possible to force-reload the render (like sodium does i belive)?

That's how it's supposed to work, isn't it? The places where the grass block isn't connected with another grass block below will not be better-grassified.

I remembered that it blended with the block below and on the side (like with a dirt side if the block below it's dirt, stone if it is stone... But maybe it was another mod/resourcepack

Hmm... I'll place a comment then, warning the user.
Isn't possible to force-reload the render (like sodium does i belive)?

I am also curious about any talks with the original dev, maybe they would be willing to upstream the work you've done? Or better yet, maybe you two can collaborate to maintain the original mod together?

I've reached the author privately on Discord, and he seems to be cool about me maintaining the fork! I'm also going to split the revenue with the author, once he accepts the revenue request on Modrinth, which he has agreed to (he didn't want the revenue actually).

I need some opinions:
Should I JiJ MidnightLib like Puzzle has?

I need some opinions: Should I JiJ MidnightLib like Puzzle has?

I would prefer if you didn't, as it reduces redundancy. However, as you mentioned - it is really small, so ultimately it doesn't matter to me; you can include it if you feel it improves the UX for users.

had a concern about the current Continuity implementation not being sustainable. Is that addressed in this fork?

Continuity's SpriteCalculator class isn't really much of a work to port in the mod (merely a copy-paste)! If PepperCode1 decided to remove the class from the mod in the future, then the only effort I'll have to do is taking permission from them to use it in the mod.
So, I'll continue to include Continuity as a dependency until that actually happens.

had a concern about the current Continuity implementation not being sustainable. Is that addressed in this fork?

Continuity's SpriteCalculator class isn't really much of a work to port in the mod (merely a copy-paste)! If PepperCode1 decided to remove the class from the mod in the future, then the only effort I'll have to do is taking permission from them to use it in the mod.
So, I'll continue to include Continuity as a dependency until that actually happens.

Hmm. Well, the older version of that class is already available under LGPL, and according to your code, you only refer one method from it anyway.
So wouldn't it reduce a lot of complexity and fragility to just copy that one method over and not depend on Continuity?

Hmm...

I've just ported the mod to 1.21 (there were some changes to Minecraft's ModelLoader class)

Everything works fine, on the mod's end.
Not uploading to Modrinth, as I'm waiting for MidnightLib to update, as it causes a crash in the options screen.


TritonCTS runTritonCTS segment failed in gtest

Excuse me, I am now learning codes of TritonCTS and try to use gTest to test it.
While running runTritonCts(), core dumped,
I was running same flow with test/simple_test.tcl
Here's my codes:
const char* defName = "src/TritonCTS/test/16sinks.def";
const char* lefName = "src/TritonCTS/test/Nangate45/Nangate45.lef";
const char* libName = "src/TritonCTS/test/Nangate45/Nangate45_typ.lib";

ord::OpenRoad* openRoad;
Tcl_Interp* interp = Tcl_CreateInterp();
Tcl_Init(interp);
openRoad = ord::OpenRoad::openRoad();
openRoad->getDbNetwork()->clear();
openRoad->getSta()->clear();
ord::tclAppInit(interp);

openRoad->readLef(lefName, "test", true, true);
openRoad->getSta()->readLiberty(
      libName, openRoad->getSta()->cmdCorner(), sta::MinMaxAll::all(), true);
openRoad->readDef(defName, false, false, false);
// give arguments necessary to tritonCTS
Tcl_Eval(interp, "create_clock -period 5 clk");
Tcl_Eval(interp, "set_wire_rc -clock -layer metal3");
TritonCTS* cts = openRoad->getTritonCts();
cts->getParms()->setRootBuffer("CLKBUF_X3");
ASSERT_NO_THROW(cts->setBufferList("CLKBUF_X3"));
cts->getParms()->setSinkBuffer("CLKBUF_X3");
cts->getParms()->setWireSegmentUnit(20);
cts->getParms()->setSinkClustering(false);

cts->runTritonCts(); // <=here segment fail
openRoad->getDb()->clear();

And the result is as following:
Eden 1 bf0818133c50a401442cb0b8185912bfd142c7b2
This program is licensed under the BSD-3 license. See the LICENSE file for details.
Components of this program may be licensed under more restrictive licenses which must be honored.
[INFO ODB-0222] Reading LEF file: src/TritonCTS/test/Nangate45/Nangate45.lef
[INFO ODB-0223]     Created 22 technology layers
[INFO ODB-0224]     Created 27 technology vias
[INFO ODB-0225]     Created 134 library cells
[INFO ODB-0226] Finished LEF file:  src/TritonCTS/test/Nangate45/Nangate45.lef
[INFO ODB-0127] Reading DEF file: src/TritonCTS/test/16sinks.def
[INFO ODB-0128] Design: test_16_sinks
[INFO ODB-0130]     Created 1 pins.
[INFO ODB-0131]     Created 16 components and 96 component-terminals.
[INFO ODB-0133]     Created 1 nets and 16 connections.
[INFO ODB-0134] Finished DEF file: src/TritonCTS/test/16sinks.def
*****************
* TritonCTS 2.0 *
*****************
*****************************
*  Create characterization  *
*****************************
[INFO CTS-0039] Number of created patterns = 2376.
[INFO CTS-0084] Compiling LUT
Min. len    Max. len    Min. cap    Max. cap    Min. slew   Max. slew
2           4           1           34          1           26
[WARNING CTS-0043] 792 wires are pure wire and no slew degration.
TritonCTS forced slew degradation on these wires.
[INFO CTS-0046]     Num wire segments: 2376
[INFO CTS-0047]     Num keys in characterization LUT: 838
[INFO CTS-0048]     Actual min input cap: 1
**********************
*  Find clock roots  *
**********************
[INFO CTS-0002]  User did not specify clock roots.
************************
*  Populate TritonCTS  *
************************
Initializing clock nets
Looking for clock nets in the design
[INFO CTS-0007]  Net "clk" found for clock "clk"
[INFO CTS-0009]  Initializing clock net for : "clk"
[INFO CTS-0010]  Clock net "clk" has 16 sinks
[INFO CTS-0008]  TritonCTS found 1 clock nets.
****************************
*  Check characterization  *
****************************
  The chacterization used 1 buffer(s) types. All of them are in the loaded DB.
***********************
*  Build clock trees  *
***********************
[INFO CTS-0027]  Generating H-Tree topology for net clk
[INFO CTS-0028]     Tot. number of sinks: 16
[INFO CTS-0030]     Number of static layers: 0
[INFO CTS-0020]  Wire segment unit: 14000  dbu (7 um)
[INFO CTS-0023]  Original sink region: [(3730, 1730), (22730, 20730)]
[INFO CTS-0024]  Normalized sink region: [(0.266429, 0.123571), (1.62357, 1.48071)]
[INFO CTS-0025]     Width:  1.3571
[INFO CTS-0026]     Height: 1.3571
[WARNING CTS-0045] Creating fake entries in the LUT.
Level 1
    Direction: Vertical
    # sinks per sub-region: 8
    Sub-region size: 1.3571 X 0.6786
[INFO CTS-0034]     Segment length (rounded): 1
    Key: 2376 outSlew: 2 load: 1 length: 1 isBuffered: false
[INFO CTS-0032]  Stop criterion found. Max number of sinks is (15)
Building clock sub nets...
[INFO CTS-0035]  Number of sinks covered: 16
[INFO CTS-0033]  Clock topology of net "clk" done.
****************
* Post CTS opt *
****************
[INFO CTS-0036]  Avg. source sink dist: 17902.50 dbu.
[INFO CTS-0037]  Num outlier sinks: 0
********************
* Write data to DB *
********************
Writing clock net "clk" to DB
[INFO CTS-0018]     Created 3 clock buffers.
Segmentation fault (core dumped)

While I try Tcl_EvalFile(interp, "src/TritonCTS/test/simple_test.tcl")
It gave me same result.
I guess I have missed something to init openRoad or TritonCTS
But I have called all codes that i could find.
Could you plz give me some advice?

I'm not clear why you don't just
cd cd src/TritonCTS/test/
openroad simple_test.tcl

to run this test.  Why write your own driver that is mostly calling tcl_eval?

It is because i wanna do unit tests for every functions in TritonCTS,
and in case their functions changed if i modify some codes.
openroad simple_test.tcl runs well
but it only do a global regression for TritonCTS.
Is it impossible to call functions individually in TritonCTS?
  In your code you are calling cts->runTritonCts which is the top level entry point you would get from calling the tcl command.  Is your goal to have more fine grained tests or just setup different situations that would lead to more coverage.  The later is easier to do and would require less c++ coding but sometimes it is tricky to hit a particular condition.

Thank you for your understanding.
Indeed, i'm going to have more fine grained tests.
I tried every functions before writeDateToDb() individual , for example buildClockTrees and populateTritonCts
They all run correctly.
I have test all parts of TritonCTS in gtest except this one.
If it is difficult to achieve, maybe I should give it up temporarily.

Is this a project you are doing with the intention to submit it or just for your own use?  If the former we should discuss how this would integrate as we don't currently use gtest.

It is just for my own use and not urgent.
I'm now doing this just for learning algorithm and codes of TritonCTS.
So if this will cost you too much energy, I don't think there is any need to waste your precious time.
I can just use another way to do the same thing, maybe, gtest is not necessary.
I just wonder why after building HTreeBuilder successfully, writeDateToDb() failed.
If it is possible to run tcl script, why I can't call these function directly in cpp?
Is that I forgot anything before init TritonCTS? openRoad? openDB? or Tcl_interp?
These are my questions indeed.
I'm sorry for such a chattering.

I don't know off hand why it crashes.  The initialization sequence is a bit involved so you might have missed a step.  You could debug writeDataToDb as a learning exercise as well.


Cannot pass the tests after adding new tokens

Hi, I created the fork  of brightscript-parser
and I added support for conditional compile if/else statements:
#if, #else, #else if, #end if.
I named the tokens: condIf, condElse, condElseIf, condEndIf.
When I run the tests, its failed with the following errors:
nyc mocha src/**/*.spec.ts --full-trace --bail

  √ all tokens are placed into a bucket
  √ all tokens have a token definition
  BrightscriptLexer
    getMatch() works for --
      √ endFunction
      √ endIf
      √ endSub
      √ endWhile
      √ exitWhile
      √ exitFor
      √ endFor
      √ elseIf
      1) condElseIf

  10 passing (73ms)
  1 failing

  1) BrightscriptLexer
       getMatch() works for --
         condElseIf:

      Expected 'identifier' to equal 'condElseIf' for 'condelseif'
      + expected - actual

      -identifier
      +condElseIf

      at matchMany (C:\Git_works\brightscript-parser\src\BrightscriptLexer.spec.ts:17:49)
      at Context.<anonymous> (C:\Git_works\brightscript-parser\src\BrightscriptLexer.spec.ts:39:9)
      at callFn (C:\Git_works\brightscript-parser\node_modules\mocha\lib\runnable.js:372:21)
      at Test.Runnable.run (C:\Git_works\brightscript-parser\node_modules\mocha\lib\runnable.js:364:7)
      at Runner.runTest (C:\Git_works\brightscript-parser\node_modules\mocha\lib\runner.js:455:10)
      at C:\Git_works\brightscript-parser\node_modules\mocha\lib\runner.js:573:12
      at next (C:\Git_works\brightscript-parser\node_modules\mocha\lib\runner.js:369:14)
      at C:\Git_works\brightscript-parser\node_modules\mocha\lib\runner.js:379:7
      at next (C:\Git_works\brightscript-parser\node_modules\mocha\lib\runner.js:303:14)
      at Immediate._onImmediate (C:\Git_works\brightscript-parser\node_modules\mocha\lib\runner.js:347:5)
      at runCallback (timers.js:696:18)
      at tryOnImmediate (timers.js:667:5)
      at processImmediate (timers.js:649:5)

ERROR: Coverage for lines (86.47%) does not meet global threshold (100%)
ERROR: Coverage for functions (81.82%) does not meet global threshold (100%)
ERROR: Coverage for branches (28.57%) does not meet global threshold (100%)
ERROR: Coverage for statements (86.67%) does not meet global threshold (100%)

===================  Coverage summary ==================
Statements   : 86.67% ( 182/210 )
Branches     : 28.57% ( 4/14 )
Functions    : 81.82% ( 9/11 )
Lines        : 86.47% ( 179/207 )
==================================================

I implemented it in the forked formatter and in forked vscode-brightscript-language extension.
I installed this extension in vscode and its works very well regardless failed tests in brightscript-parser.
Could you please advice about described issue?
Thanks

I think I found the problem. I'm working on a fix in a local copy of your branch. I'll let you know when I get it fixed up.

Thanks!

Here's a new commit (in a temporary repository) that shows what I had to do in order to get the tests to pass. https://github.com/TwitchBronBron/brightscript-parser-evgygor/commit/8a12fd2f25c729067e0d107fbc3fe6fd74290952

Here's a new commit (in a temporary repository) that shows what I had to do in order to get the tests to pass. TwitchBronBron/brightscript-parser-evgygor@8a12fd2

I implemented those changes and created the pull request, It's failed on missing reviewer.
Could you please review the PR?
Thanks


security: ugrade lodash to v4.17.14

To avoid https://snyk.io/vuln/SNYK-JS-LODASH-450202

Pull Request Test Coverage Report for Build 473

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.497%

Totals

Change from base Build 472:
0.0%

Covered Lines:
634

Relevant Lines:
643

💛  - Coveralls

Thanks for the PR!


Error deprecated<EMAIL_ADDRESS>

PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.
ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
Error on installation
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142

As indicated, this is not an error but a warning. Such messages are quite frequent in the Node.js ecosystem and are most often harmless, il will disappear once the related package using it will update or change its dependency. It's not directly related to this package, so we can't do much about it.


Updated template for best practices with Python SDK

Added implementation of graceful exit via SIGTERM
Added support for handlers
Enhanced code structure to allow for easy expansion

Is ther a change in the minimum python version with this PR?

I need help to try the changes and make sure they run fine on a device and simulator. I am seeing this exception when local debugging. I will set time to work through this together.
Exception has occurred: ModuleNotFoundError
No module named 'azure'
File "C:\Work\AzureIoT\IoTEdge\VSCode\SampleSolutions\EdgeSolution091021\modules\SampleModule\main.py", line 9, in
from azure.iot.device.aio import IoTHubModuleClient


Add config flow support

This change makes it possible to setup pyscript from the UI so a restart is not required (but configuration.yaml is still supported so there is no breaking change). I also updated the code to create the <config/path>/pyscript folder if it doesn't exist - not sure if there was an intentional reason why you required the user to create the folder but it seemed like an easy improvement (and otherwise, the user would have to create the pyscript folder before setting the integration up in the UI).

If this PR is accepted, it paves the way for, in my opinion, a very useful feature.
Currently, we can use state.set() in pyscript. However, this has several caveats that go with it:

the entities it "creates" are not restored,
existing entities with the same entity_id are blindly overwritten,
these entities cannot be managed (renamed, etc) in the Home Assistant UI

Using Config Flow and the appropriate Home Assistant Entity Objects, pyscript could support pyscript.binary_sensor.create() and pyscript.binary_sensor.update() as well similar methods for sensor to allow for pyscript automations to actually create entities/devices in the Home Assistant way.
This Code which allows creating of such entities/devices over websocket commands for use with Node-Red should provide a good example of how this is done.

Thanks for this PR!  It looks good.  Yes, there was no good reason to have the user create the pyscript directory - I saw that python_scripts did it that way.  Thanks for adding tests too.

I ran pylint and got the following warnings:
************* Module pyscript.config_flow
custom_components/pyscript/config_flow.py:19:4: W0222: Signature differs from overridden 'async_step_user' method (signature-differs)
custom_components/pyscript/config_flow.py:19:4: W0222: Signature differs from overridden 'async_step_user' method (signature-differs)

@dlashua reported and I've confirmed this issue.
This PR has broken the initial loading of config settings.  It used to be that the config_entry argument to async_setup_entry() contained the current yaml configuration, starting with a top-level entry for pyscript.  The load_files() function extract's pyscript's apps config with:
apps_config = config.get(DOMAIN, {}).get("apps", None)

That's now None for two reasons:

config_entry.data starts below "pyscript", not at "pyscript"
config_entry.data is some old setting - it's not the current yaml configuration

On reload it works correctly since it explicitly loads the latest yaml config with:
config = await async_process_component_config(hass, conf, integration)

That might be an expensive operation, so I'm not sure whether it's ok to do that on startup.

Thanks for the heads up @craigbarratt clearly missed some things. I actually think the way that reload is working would not work with config entries. We shouldn't be loading data from the config, we should be loading the data from the config_entry. I've already fixed the issue I think, I just need to figure out how to resolve the reload before I submit a new PR

I actually don't understand how config flow works, and how the configuration is stored.  Can you mix yaml with new-style config?
The reason this is important is that just before your PR, I committed a change that allows other config parameters (below pyscript) to be available for pyscript apps and scripts.
So I guess we need a way to harmonize new-style and yaml config, for both startup and reload.

You mean can you add YAML config info in addition to setting up the config through the UI? I don't believe so unless you had a separate YAML file for the additional config items that your integration read and loaded in.
The way config flow works is that you define a schema for a config, and then the UI shows it to the user to fill out based on the data types -> once the user submits, the backend sees a dictionary as you would expect from a YAML config and stores that to data in the config_entry. To handle YAML configs, there is an "import" flow that reads in the YAML and then passes that dictionary to the backend call that creates the entry, essentially mimicking a user doing the same.

So perhaps we should have a separate yaml configuration file for pyscript apps?  @dlashua - what do you think?

There is one other option - We can make it so that if a user sets up through the UI, we can import just the apps section of the config on a reload and update the config entry. I would have to think about how that should work, but it is an option.


Disable any animation of a particular child view programmatically

My child view is being animated because of the parent view animation. How can I disable this for the child view ?
thx

Just to clarify. Do you want the subview to not move with the superview?

Just to clarify. Do you want the subview to not move with the superview?

Yes exactly

Yes exactly

Le 1 mars 2018 à 03:56, Luke Zhao<EMAIL_ADDRESS>a écrit :
Just to clarify. Do you want the subview to not move with the superview?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/lkzhao/Hero/issues/406#issuecomment-369458260, or mute the thread https://github.com/notifications/unsubscribe-auth/AeL8EMrfrK9_PUgTcoOhTpdlnFaenW0cks5tZ2NwgaJpZM4SNXSt.


Update to Diffusers 0.10.0

What does this PR do?

This PR integrates minor changes brought by Diffusers v0.10.0.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Patching v3

include firewall class for dependency packages
add ubuntu 22.04 and module dependencies to metadata
move kubectl and kubeadm to generic install classes
add firewall also for non firewalld systems
add kubeadm tool to controller
update class documentation
add module dependency for augeasproviders_core
add dependencies between sysctl and kmod
require file kubectl before using it
allow to set advertise_address

This would break literally every single one of the clusters that I currently manage, firewalld has absolutely nothing to do with the OS family.

oh okay. isn't firewalld only a RedHat thing? the module the resources are from supports only RedHat systems. And i never saw firewalld on a ubuntu, does this work?

for all the firewall questions from @tuxmea I myself have no clear answer. @ananace do you have a opinion on that? How/if we should restrict these firewall settings?

Question: should we add firewall and firewalld module as dependency to metadata.json?

it is already in here. see the changed files/metadata.json.

it is already in here. see the changed files/metadata.json.

OK. Already reviewed and unchanged, so the file did not show up. Sorry.


Add Pagination or lazy load

Is your feature request related to a problem? Please describe.
I am not sure if this is the right place to open the issue. But we are working on a project that has a big scope and we want to add all the hosts as target in reconmap. http://localhost:8080/targets?projectId=2 REST endpoint gives a list of all targets in the project which becomes too large for webbrowser to read and page starts hanging.
Describe the solution you'd like
Add pagination.
Describe alternatives you've considered
Lazy load is another way of doing it but still you will need to have pagination on the api.
Additional context

Thanks for reporting this @0xcrypto . I'll add pagination to the targets page this week. Regards

Just so that I can test it with your volume. What's the number of targets you are adding? I have tried adding 1000 and takes a few seconds (< 3s) to load but works fine (no hangs or rendering lags)
I'll add pagination anyway because I think is necessary, but wondering if I should be testing with less or more based on your usage.
Thanks!

Just so that I can test it with your volume. What's the number of targets you are adding? I have tried adding 1000 and takes a few seconds (< 3s) to load but works fine (no hangs or rendering lags)
I'll add pagination anyway because I think is necessary, but wondering if I should be testing with less or more based on your usage.
Thanks!

I did around 50k I think.

Hi @0xcrypto . I have pushed the changes to support pagination on the project targets view. Let me know if they look OK to you. Thanks

We already running reconmap in prod so will update later. Thanks for the update <3


Hitting "Value was either too large or too small for an Int32." after the host sends setBreakpoint

After this request is sent and before the debug adapter responds I'm seeing a popup dialog saying "Value was either too large or too small for an Int32" at which point the host crashes. Is there any way to see what's going on within the host to debug this error?

I would suggest first starting by turning on logging (see https://github.com/Microsoft/VSDebugAdapterHost/wiki/Logging) and look for numeric fields returned by the debugger with a value outside of the range of 32-bit integer. There are additional troubleshooting steps you can take next, but looking at the logs is probably the easiest thing.

So it turns out the Visual Studio host uses 32 bit integers for breakpoint/stack/etc IDs. Is this a bug on VS's side or a


Responsive Taxonomy Picker

Is there a method to make the client side taxonomy picker responsive using bootstrap or other CSS means? When I open it on a mobile device and use the taxonomy picker, it is opening to much larger than the screen/not usable.

There is not. And CSS really isn't my favorite thing. So feel free to work on writing CSS to make it responsive :)

Thanks for the update. I will start by looking at the classes created by the picker and see what I can target via CSS.

Closing this issue due to age. If you believe this is still an issue in the latest release please re-open and let us know.


Expose multiple subject overload of evaluate-measure

Update evaluator to expose multiple subjects overload of evaluate-measure
This is needed for use with both Spark DQMP and CDR DQMP to increase performance of batch jobs. This will allow us to not have to iterate through measures one by one in parallel

Here's the function overload that's protected and needs to be either public or refactored such that subjects can be determined independently of Measure eval:
https://github.com/DBCG/cql-evaluator/blob/master/evaluator.measure-hapi/src/main/java/org/opencds/cqf/cql/evaluator/measure/r4/R4MeasureProcessor.java#L217


fix: WRAPPER_REACT_QUERY.md

This PR updates the integration of the react query with mmkv. I have also updates doc links

awesome thanks!

@AlirezaHadjar Can you clarify why you replaced here the PersistQueryClientProvider with a different approach which just uses the persistQueryClient function? Isn't PersistQueryClientProvider more applicable, as also recommended by official docs of react-query?

@fobos531 in the case of no persister or any persister the method you menthioned is recommended but as for sync persister, I could only find this method https://tanstack.com/query/latest/docs/framework/react/plugins/createSyncStoragePersister

@fobos531 in the case of no persister or any persister the method you menthioned is recommended but as for sync persister, I could only find this method tanstack.com/query/latest/docs/framework/react/plugins/createSyncStoragePersister

You can find it here, with the example for the sync persister: https://tanstack.com/query/latest/docs/framework/react/plugins/persistQueryClient#persistqueryclientprovider
IMO this approach might be more preferable compared to the method mentioned in this PR. What do you think?

@fobos531 in the case of no persister or any persister the method you menthioned is recommended but as for sync persister, I could only find this method tanstack.com/query/latest/docs/framework/react/plugins/createSyncStoragePersister

You can find it here, with the example for the sync persister: https://tanstack.com/query/latest/docs/framework/react/plugins/persistQueryClient#persistqueryclientprovider
IMO this approach might be more preferable compared to the method mentioned in this PR. What do you think?

As I checked both doc pages, I couldn't find any advantages of one to the other. Could you please elaborate on what do you mean by "preferable"?

@fobos531 in the case of no persister or any persister the method you menthioned is recommended but as for sync persister, I could only find this method tanstack.com/query/latest/docs/framework/react/plugins/createSyncStoragePersister

You can find it here, with the example for the sync persister: tanstack.com/query/latest/docs/framework/react/plugins/persistQueryClient#persistqueryclientprovider
IMO this approach might be more preferable compared to the method mentioned in this PR. What do you think?

As I checked both doc pages, I couldn't find any advantages of one to the other. Could you please elaborate on what do you mean by "preferable"?

Primarily due to reasons listed in the screenshot below:

To be honest, I've never experienced issues described in that screenshot, but it convinced me to use that approach regardless.

Correct!
I used this method as it is more similar to experimental persister. So could you please open a PR for the change?

Correct! I used this method as it is more similar to experimental persister. So could you please open a PR for the change?

Sure: https://github.com/mrousavy/react-native-mmkv/pull/658


Spaces and double quotes

I have some trouble with spaces in the tags. The following code results in an error:
let write_query = WriteQuery::new(Timestamp::Now, "temperature")
    .add_field("value", 25)
    .add_tag("tag1", "ABC DEF".to_string());

The error contains: Err(DatabaseError { error: "influxdb error: \"{\"error\":\"unable to parse \'temperature,tag1=\\\"ABC DEF\\\" value=25\': invalid field format\"}\n\"" })
By replacing the spaces with a backslash influxdb accepts the request:
let write_query = WriteQuery::new(Timestamp::Now, "temperature")
    .add_field("value", 25)
    .add_tag("tag1", "ABC DEF".replace(" ", "\\ "));

The second issue is that the influxdb stores the double quotes of the tags as follows:
time                tag1                   value
----                ---                    -----
1583008260693608605 "ABC DEF"              25

If I use the python influxdb client the double quotes are not stored. So I tested it without surrounding double quotes. I changed write_query.rs as follows:
-Text(text) => write!(f, "\"{text}\"", text = text),
+Text(text) => write!(f, "{text}", text = text),

It works as expected. So I guess that the spaces must be handled by escaping with backslash instead of surrounding with quotes.
influxdb version is 1.3.6-1

Thanks for reporting this. Seems like an oversight on my side. Feel free to open a Pull Request fixing the correct

#55 should be covering this.


Pre-release updates

This PR updates the changelog in preparation for the upcoming release.

I generally use https://github.com/choldgraf/github-activity
or use the "Generate Changelog" feature in GitHub directly when drafting a release.
In other projects there are other automations/tools we use but here the above work.

Ok fixed all the headings @gabalafou


rpc: migrate libpreflight's fee computations to rs-soroban-env

The fees computed in RPC's simulateTransaction method are tightly coupled the host VM.
The disconnect between the RPC and rs-soroban-env in terms of fees has caused quite a lot of frustration in platform team.
The platform team doesn't take part in metering algorithm making it hard to update the fees algorithm in isolation from the Core team's decisions and code changes.
By migrating the fee computations to rs-soroban-env we hope to considerably improve the situation.

Here is a document from @dmkozh with various storage/auth modes.

Just calling it out that when emulating in the host, we will also need to account for XDR decoding.


Add newsletter form

Quick Description 🛠
implementing newsletter form submissions helps users to subscribe and be updated
@Puskar-Roy please assign me this issue, i want to work on it
also please assign level 2, gssoc-extd, hacktoberfest labels
Select the open-source program you're contributing to
GSSOC 2024 EXTD, Hacktoberfest 2024
Adherence to Code of Conduct

[X] I adhere to the CONTRIBUTING GUIDELINES of this project.

Hey @meghanakn473👋! Thanks for raising this issue and demonstrating your interest in contributing to our project!🚀
We value your engagement and eagerly anticipate your contributions. Should you wish to get involved, please use the /assignme command to self-assign the issue.
This issue provides an excellent opportunity for us to enhance our project, and we're excited to have you join us! Please take a moment to review our CONTRIBUTING GUIDELINES before getting started.
If you have any questions or need assistance, feel free to reach out to us on LinkedIn.❤

/assignme

@Puskar-Roy please add the labels level 2, gssoc-extd, hacktoberfest

@meghanakn473 actually we do not need any news letter as of now

Hello @meghanakn473! We'd like to inform you that the issue has been resolved and is now closed. We appreciate your understanding and look forward to your continued involvement with our repository!🤗
If you encounter any further issues, please don't hesitate to reach out to us on LinkedIn. Thank you for your support!❣
Happy coding!✨ We hope to see you again soon!❣


chore(deps): upgrade slonik

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Cartographer multi-session mapping

Hello everyone,
I was exploring the cartographer-package and wanted to know if it has support for multi-session mapping. I would really appreciate some help here.
Thanks

Can you elaborate a bit more what you mean with multi-session mapping?

The task I wish to address is suppose I map a part of a room today using cartographer and store it and kill all the running processes then would I be able to continue the mapping of the remaining room the next day and combine the two maps (online/offline both methods are considerable)? Would this be possible through the ros package provided by cartographer?

You can serialize the state to a .pbstream file (/write_state service) and the next day load this file again via --load_state_filename argument of the node and continue mapping, potentially using the /start_trajectory service to set a reasonable start pose. Alternatively, the offline node also supports processing multiple bagfiles, but this is probably not suitable if there is a large gap between mappings.

Thank you @MichaelGrupp this approach worked as desired.


training for coco form

Dear authorsreally impressive approach and great results! Thank you for publishing your work.
I don't have data in VID format, but only data in coco format, is it impossible to train the dataset in image format?

Hey, you can train this video objector as a general object detetor. But you have to change the code of  the data loading. Previous works [e.g. Relation Networks for Object Detection] show the relation module is also benefical to object detection in single frame, but in this work, we don't test its performance.

Hey, you can train this video objector as a general object detetor. But you have to change the code of the data loading. Previous works [e.g. Relation Networks for Object Detection] show the relation module is also benefical to object detection in single frame, but in this work, we don't test its performance.

Dear author, thanks for your sharing! I don't need training but target detection based on TUM datasets(Continuous RGB images). How to run the detection task based on the TUM datasets? which file should I change the code of the data loading?Could you be more specific? thank you very much!!


Luminus fix

remove additional colon in redirect url

Pull Request Test Coverage Report for Build 1754

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 24.312%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sagas/index.ts
0
2
0.0%

Totals

Change from base Build 1750:
-0.01%

Covered Lines:
1211

Relevant Lines:
4150

💛  - Coveralls


Visual glitch

When waking from sleep, terminal is white.
Killing and opening a new terminal gets rid of the issue

/home/samuel/Pictures/Screenshot_20201219_143514.png

/duplicate of #69665


Multiple copies of Jss when using styled-jss and glamor-jss (not directly a Mui issue)

When using styled-jss/ glamor-jss and inspecting my production bundles with webpack bundle analyzer, I'm seeing multiple copies of Jss being bundled . for instance styled-jss is bringing in 16KB, similar with glamor jss. Is there a way to fix this during the mui / jss instantiation? Or is it going to just fall on webpack / build process fixes?

@jeremy-coleman You can try to force your package manager to install a single version of JSS. It should do it. Otherwise, the ecosystem would have to set JSS as a peer dependency. We don't. Also, you can checkout our alternative APIs, it's a way to save bundle size: https://material-ui.com/customization/css-in-js/#styled-components-api---15-lines-.


COMPLETED/IN DRAFT: Italian translation

Phew, what did I get myself into. Technical translation is more rigorous than I expected. So if there are any native speakers to revise/adapt please feel free to join in or get in touch with me.

Pull Request Test Coverage Report for Build 998756698

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.196%

Totals

Change from base Build 995566219:
0.0%

Covered Lines:
1055

Relevant Lines:
1119

💛  - Coveralls

@fgandellini ho notato che ti e piaciuto il mio commento. Ho finito gli ultimi documenti ma non mi sento sicuro nel prodotto. Potete per favore aiutarmi?? Il mio italiano non e eccezionale ma ho fatto del mio meglio. Sarebbe grande se un madrelingua corregga il contesto tecnico!

Hey @davedbase! I'm on holiday these days but as soon as I'll be back I'll be happy to take a look to you documents! 🙂
I'm really interested in this project but I didn't have time to properly use it yet, checking your docs is a great starting point! 😉

@fgandellini amazing! No rush and I'd be so appreciative. I have no idea how Italians translate code or context of certain topics. So I likely butchered a lot of that and could use a deep look. Also note that we moved all documentation over to https://github.com/solidjs/solid-docs/tree/main/it. =)
Buona vacanza!

Hey @davedbase! I'm back from the holidays, ready for some translation work! :wink:
Should I review the translations directly on https://github.com/solidjs/solid-docs/tree/main/it? Or should I update them in this repo?

Welcome back! Thanks so much for helping make corrections. I'm sure you'll find a lot of the phrasing and even grammar off. I had to lean on my poor language education and Google Translate to make things work decently haha.
If you can, you should fork the repo, make adjusts to the markdown files in it and then Pull Request it back to the solid-docs repo :-)


Update tekton tasks manifests to version v0.12.0

Update tekton tasks manifests to version v0.12.0
Release note:
NONE

/retest

/test e2e-tests-cluster-scope

/retest


Allow semi-sync even if a replica's promotion rule is "must_not"

This PR resolves https://github.com/openark/orchestrator/issues/1369 by introducing a flag that allows enabling semi-sync on an unpromotable host.

Superseded by https://github.com/openark/orchestrator/pull/1373


Hey

Renegade

Why:
Closes [issue link]

What's being changed:

Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[x] This pull request impacts the contribution experience

[x] I have added the 'writer impact' label
[x] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Hey

Think you

Hey my guy

Fakka

Hey

Help me

Gift me

You

M


build-info-api 2.13.11 not on bintray

It appears build-info-api 2.13.11 didn't get pushed to Bintray?
https://dl.bintray.com/jfrog/jfrog-jars/org/jfrog/buildinfo/build-info-api/

@algoRhythm99,
All packages are now available on Bintray.
We'll male sure to publish new Build-Info versions  to Bintray as soon as they ate released.
Thanks


Packt Video

Its seems that Packt is now release video, can we download this too?

Yup, look at the latest (yesterday's) release.

I'm not sure wether you have already fixed it in the last couple hours, but yesterday I saw that when I included a video_tag in download_formats, the script first downloaded the code as "name_of_book_video.zip" and subsequently the videos folder with the same file name, thus making the video download fail

Is there away for me to download previous miss download?

You're right, there are conflicting file names. What I'd do is to skip downloading code files for videos as they are already in the package with the video. Does it seem reasonable to you or maybe you have another idea how to solve this problem?
@ranrinc Just remove code files and download and run download again with proposed fix installed (you can install it with pip install git+https://github.com/mjenczmyk/Packt-Publishing-Free-Learning.git@code --upgrade).
You can see the pull request here: #141.

@mjenczmyk alright.. I got this part and yes its now function correctly. Thanks

Should we merge? Is this the fix you would expect? What do you think @ranrinc @AlessioC?

@mjenczmyk I have no objection on merging this..

@mjenczmyk Another possibility could be to force the video and code download separately (therefore not together) but I don't know if is possible. Otherwise yes, I think that your fix is a good loophole. :)


macOS: There's no -D switch in BSD install

One of the latest commits (https://github.com/SymbiFlow/yosys-symbiflow-plugins/commit/c613a356f3b5a6e93d2ba64f3568f4e47cef4768) added the install -D command.
After that change building the plugins on macOS fails in the https://github.com/litex-hub/litex-conda-eda repository.
The BSD's install -d seems to have a similar meaning to the GNU's install -D but I'm not sure about that:
     -d      Create directories.  Missing parent directories are created as required.

It'd be great if the script could either have install used universally to both implementations or simply have the commands replaced in the commit with install as a fail-over for macOS.

Oh, sorry, just seen this bug assignment. Will make something that should work in both.

I'm working on this FYI. I have 100% working Mac build locally, just trying to deal with propagating changes through all the deps. My changes remove all the conda stuff (separately I'm moving surelog / UHDM onto conda-forge, I'd like to obviate the need for a separate Litex-hub channel ideally).

@hzeller I'm not a member of this repo I don't think but feel free to assign off to me


Root url config

I have _config.yml for prose set up so that it enables metafields for the root folder:
...
prose:
  rooturl: ''
  siteurl: 'http://yubisay.github.io/scac'
  media: 'assets'
  metadata:
    '':
      - name: "title"
        field:
          element: "text"
          label: "Title"
          type: "text"
      ...

Metafields for pages in root folder work fine, the problem comes when I try to create a new file via prose and save it:

and the URL is
https://api.github.com/repos/Yubisay/SCAC/contents//2017-11-01-sample.md?ref=master
Here you see it inserts bad github API call.
What may be wrong with it or how can I resetup it?

I've confirmed this bug, will look into a fix.

Looks like the title meta field is causing this.

Awesome! Thanks a lot!


PHOENIX-5554 Synchronize @Parameters, @BeforeClass and @AfterClass me…

…thods
adds the synchronized keyword to the mentioned methods

This was submitted.


Render the public key on the project edit page.

When you create a new project, a box appears at the right hand side to show you the public deployment key you need to add to your repository to allow PHPCI to pull down the code.
Once a project is created though, there's no way to access the key - it's not shown on the project form any more. The attached patch sorted it for me, but not sure if there are other impacts since this was specifically set to null previously?

I think it was a security part to hide it. But in my opinion it doesn't need to be hidden if you are able to edit the project.
:+1:

:+1:

I can't merge this one, maybe because the from is: unknown repository
Do you use a private repository?

I think I may have trashed the repo and re-forked since I raised the PR (My bad!). Happy to raise a new PR, but might be quicker just to manually make the change yourself, it's a trivial change. Let me know!

I merged it in 7c4a9261660598355a34647bd161fe3e4a55cb3a but create a typo in the pull number


Don't recommend python*- prefix with PyPI keys

Discussion
https://github.com/ros/rosdistro/pull/25474#discussion_r441702655
https://github.com/ros/rosdistro/pull/23836#discussion_r382837461
I think it would make sense to avoid python- or python3- prefixes on PyPI only keys because it could give a mistaken impression that it determines the Python version used.
The prefix doesn't make a difference because the actual python version depends on ROS_PYTHON_VERSION which itself is set by the ROS distro.
https://www.ros.org/reps/rep-0151.html#rosdep-and-pip-packages.
I think it would be confusing if a package in ROS Melodic workspace depended on python3-foobar-pip because rosdep would install it for Python 2.

This makes sense for PyPI only keys since migration from a -pip key to a system package key will require changing the key no matter what.
Does it make sense to explicitly state that when PyPI packages are being used to "fill in" on systems where a distribution default package is unavailable the python3?- key format should still be used.

. We really don't want to have pip rules overriding the apt rules. And if you have python3-foo it's much harder to double check that foo-pip doesn't exist some hundreds of lines away in the database. Whereas if you have python3-foo and python3-foo-pip they are side by side and are trivial to identify as conflicting.

I don't think I understand this part. What does it mean for two rules to conflict?

Another significant advantage of having the names the same is that when/if things get added to an apt repository in the future the new rosdep key is just removing the '-pip' extension which is easier for maintainers and clear what the substitute should be.

Does this mean PyPI rules should be removed when platform specific packages become available? foobar-pip and python3-foobar should never exist at the same time? What happens if they do?

@tfoote friendly ping :)

I don't think I understand this part. What does it mean for two rules to conflict?

If I install a pip version of foo I'll get whatever is in pypi and it will mask the underlying apt version. If they were the same version that's not problem. But generally pip is far ahead of the apt versions.

Does this mean PyPI rules should be removed when platform specific packages become available? foobar-pip and python3-foobar should never exist at the same time? What happens if they do?

Generally yes
Both of these come down to the fact that pip installations will mask the debian based installations. If I depend on foo as installed via apt. I know what version I'm getting. If someone else pip installs foo they'll get whatever version is latest in pypi. This may be a major new version, with newer upgraded APIs and possibly changed dependencies etc. That's not really a problem if I want the latest version and ask for it. But if foo is a library that other people are depending on the pypi version is rarely 100% compatible so other packages relying on foo we be potentially broken with the unbenownst upgrade.
This is particularly pernicious because as a developer I can assert that I need debian package foo at version X.Y.Z and can have my installation scripts check that the debian package is installed at the right version. However, rosdep will assert that the debian package is installed correctly. However when I try to import the package I'll get the pip version.
Even more confusing is if I have everything working. And then I add a new package to my workspace that you then use rosdep to resolve the pip version will then potentially break an already running system as a side effect of installing.
So at the high level the pip rules should only be added for targets or platforms for which there does not exist an apt or other default installer version.
We have the convention of having the -pip rules to be clear about what's pip only. And what we should be doing is when we add an apt rule we should null out the pip rule for that and future versions. (We don't have automation for this so it often doesn't happen.) We do allow you to add pip resolutions for apt packages on older platforms where the apt package is not available and the pip one can backfill where there's no backports, because those won't conflict. But as a rule the rosdep keys should be defining the canonical version of the package that we are standardizing on using on that platform. And developers can have an expectation that if they rely on that key, they will have what it promises is available.
So this is why I want the same prefix so that when reviewing pull requests these conflicts can be noticed when reviewing PRs more easily.

So this is why I want the same prefix so that when reviewing pull requests these conflicts can be noticed when reviewing PRs more easily.

@tfoote Updated PR to require python3- prefix and require old -pip keys to be deleted in c3935b73d

@tfoote would you be willing to check that the changes match your comments before I merge it?


operator portworx-certified (23.10.2)

New operator bundle
Name: portworx-certified
Version: 23.10.2
Certification project: 5f74aac1270696c35e043284
Test result URL: https://catalog.redhat.com/api/containers/v1/projects/certification/test-results/id/65af7152f60a30c99d90c485
Test logs URL: https://catalog.redhat.com/api/containers/v1/projects/certification/artifacts/id/65af715134e5d62c320484e7

/pipeline restart operator-hosted-pipeline


SupportedAlgorithms.IsSupportedKeyWrapAlgorithm does not consider SymmetricAlgorithms

Our runtime supports SymmetricKeyWrap algorithms:
A128KeyWrap and A256KeyWrap.
This method should account for these algorithms.

https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/1472


New downloads from ITV Hub not working

Example follows
john@systemj ~/Videos/TV Shows/2019 $ youtube-dl --verbose "https://www.itv.com/hub/the-widow/2a5540"
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--verbose', u'https://www.itv.com/hub/the-widow/2a5540']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2019.04.07
[debug] Python version 2.7.15rc1 (CPython) - Linux-4.15.0-47-generic-x86_64-with-LinuxMint-19-tara
[debug] exe versions: avconv 3.4.4, avprobe 3.4.4, ffmpeg 3.1.3-static, ffprobe 3.4.4, rtmpdump 2.4
[debug] Proxy map: {'no': 'localhost,<IP_ADDRESS>/8,::1'}
[debug] Using fake IP <IP_ADDRESS> (GB) as X-Forwarded-For.
[ITV] 2a5540: Downloading webpage
ERROR: Unable to extract params; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 796, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 529, in extract
ie_result = self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/itv.py", line 62, in _real_extract
r'(?s)(<[^>]+id="video"[^>]*>)', webpage, 'params'))
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 1004, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract params; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

youtube-dl does not support show pages, for now, you can use individual episode URLs(ex: https://www.itv.com/hub/the-widow/2a5540a0001).

I've used the following node-red code to generate a playlist file that you can then download with
youtube-dl -i --download-archive archive.txt -a playlist.txt --socket-timeout 2
[{"id":"66b17bde.aeffa4","type":"inject","z":"61dd4d54.ab17d4","name":"","repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"Test","payloadType":"str","x":110,"y":50,"wires":[["a706303.2a852d"]]},{"id":"a706303.2a852d","type":"http request","z":"61dd4d54.ab17d4","name":"","method":"GET","ret":"txt","url":"https://www.itv.com/hub/the-hive/1a9014","tls":"","x":150,"y":100,"wires":[["3ca0343f.d0007c"]]},{"id":"3ca0343f.d0007c","type":"html","z":"61dd4d54.ab17d4","name":"","property":"payload","outproperty":"payload","tag":"a.complex-link","ret":"attr","as":"single","x":200,"y":150,"wires":[["3cb6e303.7763ac"]]},{"id":"3cb6e303.7763ac","type":"function","z":"61dd4d54.ab17d4","name":"","func":"var txt = \"\";\n\nmsg.payload.forEach(function(data){\n    if(data.href.includes('the-hive')){\n        txt += data.href + \"\\n\"; \n    }\n});\n\nmsg.payload = txt;\n\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","x":210,"y":200,"wires":[["dec7963e.3f01d8"]]},{"id":"dec7963e.3f01d8","type":"file","z":"61dd4d54.ab17d4","name":"","filename":"/mnt/data/playlist.txt","appendNewline":false,"createDir":false,"overwriteFile":"true","x":290,"y":250,"wires":[[]]}]

A bit of automation and you could have node-red export the playlist a few mins before a cron job runs youtube-dl.


Add Rails prompt

edit: I just found https://github.com/rweng/pry-rails/pull/54. In contrast to the old PR, this approach keeps the behaviour of the default pry prompt.
Been pointed here by @r-obert from pry/pry#493. Maybe this is useful.
This adds a new Pry prompt with the current Rails environment and project folder and makes it the default prompt.
I often have multiple rails consoles open and some of them also on production environments to gather data or to cleanup fraudulent users. It would be super helpful if each prompt would show the current project and most importantly the current Rails environment.
This change to the prompt makes clear what project and environment the current rails console is running on. It should help to prevent people from accidentally deleting/changing data in the wrong environment. That's why I would make it the default promt, but I know that it is a bigger visible change and I'm open about not making it a default.

Questions

Default/Not default?
I'm also not sure if the project name is really needed in the prompt, but I often have multiple projects I'm working on and it was helpful already.
Rails comes with production, development and test environments by default, so I added the formatting for those (test without any formatting), but maybe this could be improved.
I didn't add tests due to the open points above

LGTM :+1:

Thanks! I'm happy to merge this with or without the project name, but personally I'd prefer making it opt-in instead of the default. We could add a note to the README saying what line to add to your .pryrc to use it.

Ok, I made it not default and added a note to the README 👍
Unfortunately we have to include the check for PryRails::RAILS_PROMPT because otherwise running just pry would show an 'unintialized constant' warning as pry-rails is not loaded when using pry.

Why don't we display Rails environment by default? It seems very useful.
Anyone could add a line to .pryrc to hide it.

yeah, i see no reason to not display it by default.
the prompt still includes the default pry prompt, so nothing is lost.

The main reason is that I don't think plugins should change what happens when you use binding.pry unless that change is the main purpose of the plugin. There's a lot of potential for plugins stepping on each other's toes that way.

I just released pry-rails 0.3.5 with this code. Thanks for the contribution!

Awesome, thank you! ✨


DEBUG: EmberFire  : 0.0.0

Not sure if this is already known.
So when you are running in a development environment for Ember, it console.log's the version of the dependencies, and I just noticed that there is no version set for EmberFire.
DEBUG: -------------------------------
Ember      : 2.10.2
Ember Data : 2.11.0
Firebase   : 3.6.4
EmberFire  : 0.0.0
jQuery     : 3.1.1
-------------------------------

I feel like setting a version for EmberFire would be helpful, no?

This is a bug in our release script, we should have it patched up next release; see #462
I'll leave this issue open till then. Thanks for the report

Still open, still an issue

This is still an issue for me? Anyone else?
Tks

Yep, still there.

@jamesdaniels Mind re-opening this?

Tracking in #504


Modal: Fix backdrop not readjusting when height changes

Fixes #15136.
Closes #15345.
Closes #15314.
Refs #14724, #14927.
Effectively reverts #14724 but still fixes #13816. The backdrop will now again be appended to the body and not the .modal container.
Also includes a workaround for when an opening accordion makes the modal overflow to minimize jumping on the dialog. (It's more of a proof of concept, I understand if we take it out before merging.)
/cc @cvrebert @fat @XhmikosR
Sorry it took so long guys.

How does this fix #15106 exactly? handleUpdate() is still undocumented.

I thought handleUpdate() wouldn't be necessary anymore?

To clarify: handleUpdate is no longer needed to adjust the height of the backdrop, it now only centers the modal by applying padding when the modal is overflowing. So you'd only need to call it if the height change made the modal display a scrollbar when it before didn't have one. That's not a new problem though, it's been around for much longer.

While #15910 did add a note about needing to call handleUpdate(), the API docs are still missing an entry for it.

True, but since handleUpdate can't be called with the string argument to $.fn.modal it would be kinda out of place there.

lgtm

True, but since handleUpdate can't be called with the string argument to $.fn.modal it would be kinda out of place there.

@hnrch02 I think that's an oversight in and of itself. We don't intentionally make folks jump through the .data('bs.foo') hoop with anything else...

@cvrebert So you suggest we add $().modal('handleUpdate')?

Yeah.

It is actually already accessible that way, we just need to document it.

So when can we expect 3.3.4?

Looks like the CSS changes here caused #16148. Are they necessary?

so is there a fix for this & #16148 being worked on?

@allspain "This" is a pull request, so it's not clear what you're referring to.

@hnrch02 Can you answer mdo's question?

Sorry I was referring @mdo 's question, and the bug (#16148) this pull request may have introduced. Should have been more concise.

@mdo Just wanna follow up here: I merely reverted the CSS to the pre 3.3.0/#15136 state. #16148 is a problem that exists since at least v2.


Component name

We can't use Slim\Http as we need that for Slim itself.
Options:

Slim\Psr7
Slim\HttpMessage

I vote Slim\Psr7.

I don't have any strong feelings about this. But since the repository is already named Slim-Psr7 class name should also be Slim\Psr7 or OCD kicks in.

The repo is brand new & can be changed.. It's a given that we'd match namespace name :)

Slim\Psr7 +1

Slim\Psr7 +1


add new device with notch: Pixel 4a

Description

Added Pixel 4a notch support
Compatibility

OS
Implemented

Android
✅

Checklist

[x] I have tested this on a device/simulator for each compatible OS
[x] I mentioned this change in CHANGELOG.md

v8.0.2 is live :rocket:

v8.0.2 is live 🚀

Thank you ! Glad to help :)


Removed redundant type binding

Fine with me if it works. :)

@Lucretiel master branch has been updated to fix the nightly regression (see #197 for details).
Please rebase this branch to master before merging.

Done


Set CMS_Type job classad based on the dashboard activity

Fixes #9252
Status
not-tested
Description
Created a new job class ad called CMS_Type which has a very very generic classification of our job.
It's based on the dashboard activity - which has an schema as is validated for every single request - which might be repurposed in the future.
Is it backward compatible (if not, which system it affects?)
Yes
Related PRs
Goes along the lines of https://github.com/dmwm/WMCore/pull/9184
External dependencies / deployment changes
No

It seems to be working just fine. I'll patch the production agents tomorrow morning.

BTW, these unittests are not behaving well. It doesn't update the new unit tests added in the last days and simply keep reporting them as new unit tests. I couldn't find anything wrong in jenkins (besides a broken GitHub import where it doesn;t matter)... To be checked, but I guess I'll probably not have time to do so today.

@vytjan Vytas, I talked to Christian today and he said T0 jobs are also present in the CMS Job Monitoring dashboard.
In this case, can you please patch the T0 production and replay agents with this patch (or one of its backported version)? Thanks

Thanks @amaltaro Alan, I will test this in a replay and then patch the T0 production/replay agents.

@amaltaro Alan, T0 production and replay agents are all patched.


todo-modern: Cannot build project

When I attempt to build the project (either with npm run build or yarn run build, and after installing node_modules & updating the schema), I get this failure:
> @ build /Users/bropa18/Projects/relay-examples/todo-modern
> relay-compiler --src ./js/ --schema ./data/schema.graphql

HINT: pass --watch to keep watching for changes.
Parsed default in 0.12s

Writing default
TypeError: options.path.includes is not a function
    at Transformer.visitLinkedField (/Users/bropa18/Projects/relay-examples/todo-modern/node_modules/relay-compiler/bin/relay-compiler:1526:37)
    at Transformer._visit (/Users/bropa18/Projects/relay-examples/todo-modern/node_modules/relay-compiler/bin/relay-compiler:776:35)
    at /Users/bropa18/Projects/relay-examples/todo-modern/node_modules/relay-compiler/bin/relay-compiler:872:30
    at Array.forEach (native)
    at Transformer._map (/Users/bropa18/Projects/relay-examples/todo-modern/node_modules/relay-compiler/bin/relay-compiler:871:16)
    at /Users/bropa18/Projects/relay-examples/todo-modern/node_modules/relay-compiler/bin/relay-compiler:847:30
    at Array.forEach (native)
    at Transformer._traverseChildren (/Users/bropa18/Projects/relay-examples/todo-modern/node_modules/relay-compiler/bin/relay-compiler:841:31)
    at Transformer._traverse (/Users/bropa18/Projects/relay-examples/todo-modern/node_modules/relay-compiler/bin/relay-compiler:826:26)
    at Transformer.traverse (/Users/bropa18/Projects/relay-examples/todo-modern/node_modules/relay-compiler/bin/relay-compiler:765:26)

npm ERR! Darwin 15.6.0
npm ERR! argv "/Users/bropa18/.nvm/versions/node/v5.10.1/bin/node" "/Users/bropa18/.nvm/versions/node/v5.10.1/bin/npm" "run" "build"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.3
npm ERR! code ELIFECYCLE
npm ERR! @ build: `relay-compiler --src ./js/ --schema ./data/schema.graphql`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ build script 'relay-compiler --src ./js/ --schema ./data/schema.graphql'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the  package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     relay-compiler --src ./js/ --schema ./data/schema.graphql
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/bropa18/Projects/relay-examples/todo-modern/npm-debug.log

This is in the npm-debug logfile:
14 verbose stack Error: @ build: `relay-compiler --src ./js/ --schema ./data/schema.graphql`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/Users/bropa18/.nvm/versions/node/v5.10.1/lib/node_modules/npm/lib/utils/lifecycle.js:239:16)
14 verbose stack     at emitTwo (events.js:100:13)
14 verbose stack     at EventEmitter.emit (events.js:185:7)
14 verbose stack     at ChildProcess.<anonymous> (/Users/bropa18/.nvm/versions/node/v5.10.1/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:100:13)
14 verbose stack     at ChildProcess.emit (events.js:185:7)
14 verbose stack     at maybeClose (internal/child_process.js:850:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)

The version of relay-compiler that was installed is 1.0.0-rc.3.
I am using node 5.10.1 and npm 3.8.3 (and yarn 0.24.6).
Any pointers where to take this?

OK, I started experimenting with different versions of node, and 6.10.2 works.  Haven't tried other.  Is node 5 not compatible?

@object88 there is some syntax that node/babel-node support differs from each version. not knowing the detail.
from my experience, you'd better avoid the ambiguous syntax like
use
import * as React from 'react'

instead of
import React from 'react'

(just for a example, React with babel supports both though)
and use
const someGraphObjectType = new GraphQLObjectType({...});
export { someGraphObjectType };

instead of
export const someGraphObjectType = new GraphQLObjectType({...});

Closing since it seems like this has been resolved

Should there be a documentation note around this, if there is no code change?


Add a generic string format keyword

I would like to propose a generic string format keyword giving a more clean and generic way to format strings.
As suggested by @pekkaklarck in Slack this keyword could be something like this example:
${result} =    Format String    Template with {x} and {y}    x=foo    y=bar

This enhancement should solve some substituitions issues like this gist from @mayribeirofernandes.

Yeah, let's do this. Ought to be easy by using str.format.
The main use case is having a template in a file and replacing values in it. Could even consider supporting passing the template as a path to an existing file in addition to passing it as a string.

This ought to be pretty easy to implement. If there's someone interested to do it, this issue can be added to RF 3.1 scope.

I've added the keyword but I haven't added any tests, where can I find them?
Is my documentation clear enough? I don't know if everyone using Robot Framework knows Python well so I change the "args" and "kwargs" to anothers names.

PR #2831 looks pretty good, but there are still few issues that need to be fixed (see my review) before it can be merged. Do you @elyssonmr have time to look at the changes? I try to get RF 3.1 RC 1 out in two weeks.

Yes I do. I'm doing it today or tomorrow.

Thanks for updates @elyssonmr. Added some more comments to the PR.


[WIP] Release

Feature

[x] 支持 react 组件 watchDist #120
[x] 支持小程序跨端使用不同的后缀的类型文件
[x] 支持 css module

Bugfix

[x] 修复 rax 组件 demo 使用 rax-portal 报错 #110
[x] 修复 yaml 升级 v4 导致 api 变更  #116

Codecov Report

Merging #95 (a0d5187) into master (ac082e1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #95   +/-   ##
=======================================
  Coverage   78.35%   78.35%
=======================================
  Files          27       27
  Lines        1035     1035
  Branches      189      189
=======================================
  Hits          811      811
  Misses        224      224

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 ac082e1...a0d5187. Read the comment docs.

Codecov Report

Merging #95 (a0d5187) into master (ac082e1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #95   +/-   ##
=======================================
  Coverage   78.35%   78.35%
=======================================
  Files          27       27
  Lines        1035     1035
  Branches      189      189
=======================================
  Hits          811      811
  Misses        224      224

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 ac082e1...a0d5187. Read the comment docs.

变更写到 Changelog 里，之前的几个主要版本也可以补充下

变更写到 Changelog 里，之前的几个主要版本也可以补充下

done


The compatibility about Apollo 3.5 and CUDA 10.1

System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04): 18.04
Apollo version (1.0, 1.5, 2.0, 2.5, 3.0): 3.5
-**NVIDIA card : GTX1070
-**CUDA Version: 10.1
-**NVIDIA-SMI: 435.21

Dear Apollo team,

Currently i am trying to running apollo 3.5 on my Ubuntu PC. But the preception module is not running on my PC, because the libcuda.so.1 can not be found. But as you see in the screenshot, the nvidia gpu card and cuda are rightly installed. So i have questions here, is the apollo 3.5 also compatible to the CUDA 10.1 ? Or the apollo is only compatible to CUDA 8.0?

Did you install the nvidia-docker (or the newer version of docker with nvidia violate).
Could you please show your result of nvidia-smi inside the apollo docker (after running the 'dev_into.sh')

To question 1: Did you install the nvidia-docker (or the newer version of docker with nvidia violate).
If i understand right, i have already installed the nvidia-docker on my host PC, like it shows in the screen shot.

To question 2: Could you please show your result of nvidia-smi inside the apollo docker (after running the 'dev_into.sh')
I can not use the "nvidia-smi" in the apollo docker container. I think that the nvidia driver should also be firstly installed in the apollo docker container. But when i try to install it with commands "sudo apt-get update" and "sudo apt install nvidia-435". I got the error "the install-package of nvidia version 435 was not be found".  Could you give me some advise for the question, how can i get the install-package "nvidia-435" in apollo docker container?
Besides i have also tried to install the founded install-package nvidia-418 in the apollo docker container. I got an other problem there.
Here is the error msg in screenshot:

Could you please help me for this problem ?
Thanks in advance!

et update" and "sudo apt install nvidia-435". I got th

I don't think you will need to install nvidia things inside the apollo docker, as the apollo docker itself should get the environment ready with the driver and CUDA. So was there any error when you were running dev_start.sh, so the docker failed to get some of the layers?

The reference is about " FROM nvidia/cuda:10.0-cudnn7-devel-ubuntu18.04"
But i got one question here, if this reference can also be used for apollo 3.5?
Here are the msg in screen shots after the conduction of dev_start.sh. The error msgs are about libcaffe2_gpu.so and libcaffe2_gpu.so.

There is no msg after the execution of dev_into.sh after the execution of dev_start.sh.

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


Enable folding on headings

Not exactly sure if this will work.
Copied from markdown configuration

Hm, it doesn't seem to work unfortunately. According to this documentation, it looks like it's necessary to use a folding range provider?
For Markdown this seems to be implemented in the vscode-markdown-languageservice project, in src/languageFeatures/folding.ts#L58.

I see. Creating a language server for gemtext would probably be an overkill 😄


Requesting clarity on the distinction between HKT<> and Kind<>

📖 Documentation
Hello! Right off the bat, I want to mention that I have seen the HKT documentation and this issue and both were very helpful for me.
However, I just want to make sure that I understand correctly, and I believe that the output of this issue should be included in the documentation so that it makes sense for other users.
I understand that HKT<> and Kind<> and their higher-kinded friends are both abstractions over higher-kinded types. Both have the same type signature, but while HKT<> is based off of phantom types, Kind<> is based off of the URItoKind<> dictionaries.
What I do not understand is when to use which one.
In this issue, you mention this in response to @amaurymartiny's suggestion that HKT and Kind are interchangeable (by the way, I am aware that Kind used to be called Type, and I am replacing mentions of Type with Kind):

AFAIK that's because you also augmented Observable and Promise with _URI and _A. If you don't do that, you must use Kind

This leads me to believe that HKT is intended to be used in custom types that define a _URI field, and Kind is intended to be used in built-in types that do not already define a _URI field.
I also realize that each higher-kinded HKT type extends the previous one, so HKT2 extends HKT and so on. Is this done so that higher-kinded types can be used in places where a lower-kind is expected?
Basically, I want to know if I'm on the right track with this and what I'm missing. I'd like some concrete use cases describing when you should use HKT vs Kind and what the technical difference is between the two.
Thanks in advance!

This leads me to believe that HKT is intended to be used in custom types that define a _URI field, and Kind is intended to be used in built-in types that do not already define a _URI field.

@jchitel no, that's an old encoding (fp-ts v1), with v2 you don't need those fields.
I'm using HKT to implement a function
// Foldable.ts

export function intercalate<M, F>(M: Monoid<M>, F: Foldable<F>): (sep: M, fm: HKT<F, M>) => M

Kind to handle * -> * type constructors (for the same function)
export function intercalate<M, F extends URIS>(M: Monoid<M>, F: Foldable1<F>): (sep: M, fm: Kind<F, M>) => M
export function intercalate<M, F>(M: Monoid<M>, F: Foldable<F>): (sep: M, fm: HKT<F, M>) => M

Kind2 to handle * -> * -> * type constructors (for the same function)
export function intercalate<M, F extends URIS2>(M: Monoid<M>, F: Foldable2<F>): <E>(sep: M, fm: Kind2<F, E, M>) => M
export function intercalate<M, F extends URIS>(M: Monoid<M>, F: Foldable1<F>): (sep: M, fm: Kind<F, M>) => M
export function intercalate<M, F>(M: Monoid<M>, F: Foldable<F>): (sep: M, fm: HKT<F, M>) => M

etc...


[crypto] Basic CLI tool (like keytool) to generate ECVRF proofs

let's call it cryptotool and down the road put all useful crypto functionality here, so at least users have a reference.
It's fine for this tool to stay in Sui vs fastcrypto.
cc: @joyqvq @Eis-D-Z @StefPler @geomel @benr-ml

do we want this to be in sui? ie user needs to build the entire sui binary to use them. if we don't use anything directly depends on sui, does it make sense to put it in fastcrypto? a cli tool to call all fastcrypto apis.

@joyqvq Anything would work, let's do the easiest and lighter

+1 for adding it to fastcrypto, and keeping it as light as possible

This issue is closed by a PR in fastcrypto: https://github.com/MystenLabs/fastcrypto/pull/405.


Incrementalified.

Requires hosting permission PR created and merged first
https://github.com/jenkinsci/incrementals-tools

Pipeline is failing with:
No tool named mvn-default found

cc @XiongKezhi


Fix broken edit link

Seems like the edit button in the footer is adding 1 too many "/docs"
https://github.com/remix-run/react-router-website/assets/12396812/e7177e1e-0619-4cfc-8879-68db1fe744e6

Yay :D


feat: added automatic conversion of plugins to new schema

To be merged after #327
A new method .newschema() for Plugins is introduced.
An optional argument of set_hardware_requirements can be set to True and the user will be prompted to enter the information, field by field, with hints for the type of information that must be entered.
The user can also skip any field by pressing  ⏎ the return key .
Example:
>>> from polus.plugins import plugins
>>> bf = plugins.BasicFlatfieldCorrectionPlugin
>>> bf.newschema(set_hardware_req=True)
coresMax[str, float]: 4.0
coresMin[str, float]: 1.0
cpuAVX[bool]: true
cpuAVX2[bool]: False
cpuMin[str]:
gpu[amd, tpu, nvidia]: nvidia
gpuCount[float]:
[...]

Refactored hardware requirements input as keyword arguments


Bluemix MongoDB environment variable is incorrect

Then set it as an environment variable for your application by running cf set-env [your-app-name] MONGODB [your-mongodb-uri]

should be changed to
cf set-env [your-app-name] MONGODB_URI [your-mongodb-uri]

Is this still the correct format?  If so, can you submit a PR for it?
Thanks

It looks like that section of readme.md has already been update.  Thanks.


Update BTB Benchmark module

BTB version: 0.3.6

Description
Update the benchmark module in order to be able to execute the ATM classification problems to perform a global benchmark over all the datasets that can be found at http://atm-data.s3.amazonaws.com/index.html .
Tasks
In order to achieve this, the following tasks must be performed:

Create a ATMChallenge class that accepts a datasetname as an input.
Create class method that returns a list of available datasets.
Create a class method that returns an instantiation for all the available datasets.
Inside btb/benchmark/tuners/__init__.py create a method that returns all the tuning_functions (at the moment only for BTB).

A short sniped of code that represents our goal is as follows:
from btb.benchmark import benchmark, ATMChallenge, get_all_tuning_functions

challenges = ATMChallenge.get_all_challenges()
tuning_functions = get_all_tuning_functions()
results = benchmark(tuning_functions, challenges, iterations=200)
results.to_csv('results.csv', index=False)

Solved by #181


Update frequently-failed-cases.md

Docs Build status updates of commit d169cb7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit dad393b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3b9e2c9:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/design/designing-in-meeting-tab.md
:warning:Warning
View
Details

msteams-platform/apps-in-teams-meetings/design/designing-in-meeting-dialog.md
:warning:Warning
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/design/designing-in-meeting-tab.md

Line 226, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#validation-guidelines' in 'concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md'.

msteams-platform/apps-in-teams-meetings/design/designing-in-meeting-dialog.md

Line 236, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#validation-guidelines' in 'concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5bd930e:
:clock10: Pending: waiting for processors (13 builds ahead of you)
:warning: Docs Build is busy, currently there are 13 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 5bd930e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/design/designing-in-meeting-dialog.md
:warning:Warning
View
Details

msteams-platform/apps-in-teams-meetings/design/designing-in-meeting-tab.md
:warning:Warning
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/design/designing-in-meeting-dialog.md

Line 236, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#validation-guidelines' in 'concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md'.

msteams-platform/apps-in-teams-meetings/design/designing-in-meeting-tab.md

Line 226, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#validation-guidelines' in 'concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 50ab82b:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 50ab82b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/design/designing-in-meeting-dialog.md
:warning:Warning
View
Details

msteams-platform/apps-in-teams-meetings/design/designing-in-meeting-tab.md
:warning:Warning
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/design/designing-in-meeting-dialog.md

Line 236, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#validation-guidelines' in 'concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md'.

msteams-platform/apps-in-teams-meetings/design/designing-in-meeting-tab.md

Line 226, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#validation-guidelines' in 'concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Fix minor typo setthemename

Minor renaming of misspelled var

Thanks for this and I'm also sorry to say themes will be retired so this code is going away ☺
I just kept it in case and plan to remove soon if I don't get too much negative feedback. I asked the channel before, but you never know...
Keep sending improvements. Again, sorry about this.
Refresh your master against Kip v2.8.2 to get the latest.


JSON Parsing is untested

JSON parsing is not yet tested for the output from BRP072A42 module, may not read values as expected

JSON parsing is working as of version 0.0.10


Run computation_order tests on CI

Nah, probably, this isn't a great idea. I think the list should be a whitelist, not a blacklist, since newly added tests will fail.

Closing in favor of https://github.com/pfnet-research/chainer-compiler/pull/265


command "dump" is not defined when running cue dump ./...

Originally opened by @yujunz in https://github.com/cuelang/cue/issues/1077
What version of CUE are you using (cue version)?

$ cue version
cue version 0.4.0 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
❯ cue help cmd
...
Available Commands:
  dump
...

❯ cue dump ./...

What did you expect to see?
Run the specified command
What did you see instead?
❯ cue dump ./...
command "dump" is not defined
Ensure commands are defined in a "_tool.cue" file.
Run 'cue help' to show available commands.

While dumping each directory all works
❯ tree .
.
├── app
│   └── app.cue
├── app.cue
└── dump_tool.cue

❯ cue dump .
name: root

❯ cue dump ./app
name: app

Test case: test.tar.gz

Hi @yujunz - apologies for the delay in replying to this (we've been catching up post migration in #1078)
Using ecb17c94, we I can't reproduce this:
exec cue dump ./...
cmp stdout stdout.golden

-- app/app.cue --
package test

application: app: _
-- app.cue --
package test

application: [Name=_]: {
	name: Name
}

releases: [
	for k, x in application {
		name: k
	},
]

application: root: _

-- dump_tool.cue --
package test

import (
	"encoding/yaml"
)

command: dump: {
	task: print: {
		kind: "print"
		text: yaml.MarshalStream(releases)
	}
}

for rls in releases {
	command: "dump-\(rls.name)": {
		task: print: {
			kind: "print"
			text: rls
		}
	}
}
-- stdout.golden --
name: root

Closing this for now, as we still aren't able to reproduce. More than happy to reopen if you can provide more details.


CSGShape3D Gizmo Breaks When Detaching Script Editor

Godot version
v4.1.1.stable.official [bd6af8e0e]
System information
Godot v4.1.1.stable - Ubuntu 22.04.2 LTS 22.04 - Vulkan (Forward+) - integrated AMD Radeon Vega 8 Graphics (RADV RAVEN) () - AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx (8 Threads)
Issue description
The gizmos to resize a CSGShape3D do not show up if the script editor is detached.
Steps to reproduce

Create project
Create 3D scene
Add a  CSGShape3D
Select the shape in the scene editor (the orange gizmo to resize the shape shows and the shape is shaded with a blueish color)
Detach script editor
Deselect the shape
Select the shape again (The orange gizmo and blue shading is gone)

Minimal reproduction project
CSG-Test.zip

I have the same issue, but for me it's EVERY Gizmo. After detaching the script editor, the Gizmo handles of CollisionShape3D, Light3D, CSGShape3D, FogVolume, etc. are gone.
System:
EndeavourOS (Arch), Linux 6.1.50-1-lts, Nvidia GTX1080ti

The issue I specified was fixed in 4.1.3