issue with  s.source link in Specs/vcx/0.0.9/vcx.podspec

I am trying to build Sovrin connector app (https://github.com/sovrin-foundation/connector-app) for ios. When I run the instructions via yarn pod:dev:install for ios, it downloads this repository to install vcx. However  s.source link in Specs/vcx/0.0.9/vcx.podspec points to { http => 'https://repo.corp.evernym.com/filely/ios/vcx.framework_20180523.1433_universal.zip' }. The link is not working for me. I am not sure if I am on the right path but, I believe the instructions in the connector-app is outdated.

While building Sovrin connector app https://repo.corp.evernym.com/filely/ios/vcx.libvcxpartial_20181026.0952_universal.zip is not work


Fix test write duplicate type

Existing test is flaky because it relies on the ordering of elements within a JSON object To fix it, compare the parsed string against all possible orderings.
The flaky tests was found by running NonDex (https://github.com/TestingResearchIllinois/NonDex).

Codecov Report

Merging #3533 (9100895) into master (8124e5e) will decrease coverage by 0.07%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3533      +/-   ##
============================================
- Coverage     80.46%   80.38%   -0.08%
+ Complexity     7488     7484       -4
============================================
  Files           157      157
  Lines         27915    27929      +14
  Branches       6731     6737       +6
============================================
- Hits          22461    22452       -9
- Misses         3445     3466      +21
- Partials       2009     2011       +2

Impacted Files
Coverage Δ
Complexity Δ

...com/alibaba/fastjson/serializer/SerialContext.java
82.69% <0.00%> (-3.85%)
21.00% <0.00%> (-1.00%)

src/main/java/com/alibaba/fastjson/JSONPath.java
75.32% <0.00%> (-0.49%)
275.00% <0.00%> (ø%)

...main/java/com/alibaba/fastjson/util/FieldInfo.java
86.42% <0.00%> (-0.34%)
99.00% <0.00%> (ø%)

...n/java/com/alibaba/fastjson/util/JavaBeanInfo.java
86.89% <0.00%> (-0.17%)
216.00% <0.00%> (-1.00%)

...java/com/alibaba/fastjson/parser/ParserConfig.java
80.61% <0.00%> (-0.15%)
227.00% <0.00%> (-1.00%)

...main/java/com/alibaba/fastjson/util/TypeUtils.java
79.21% <0.00%> (-0.12%)
653.00% <0.00%> (-1.00%)

...ain/java/com/alibaba/fastjson/asm/ClassReader.java
87.23% <0.00%> (-0.07%)
44.00% <0.00%> (ø%)

...ava/com/alibaba/fastjson/parser/JSONLexerBase.java
69.94% <0.00%> (-0.07%)
811.00% <0.00%> (-2.00%)

.../main/java/com/alibaba/fastjson/JSONValidator.java
64.72% <0.00%> (+0.34%)
56.00% <0.00%> (+1.00%)

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 8124e5e...9100895. Read the comment docs.


Operations defined by structured header should support an aoid override

The Temporal proposal has a need to mention both the 262 and 402 flavors of some operations, which ecmarkup rejects as duplicate definitions. This can be addressed for traditionally-defined operations via an aoid suffix, but an attempt to do the same for a structured operation is rejected ("nodes with structured headers should not include an AOID"). I'm attempting to work around this in https://github.com/tc39/proposal-temporal/pull/1920/commits/82f542b2765314767577c0ec4a5a65b1326a7afc by effectively suppressing the structured definition, but it would be better if instead something like <emu-clause id="sup-canonicalizetimezonename" type="abstract operation" aoid="CanonicalizeTimeZoneName402"> were supported.

Can you say more about why you need these to be AOIDs?

They don't need to be AOIDs specifically, that just seemed like an obvious option.

I am trying to have two abstract operations in the same proposal spec which are both defined by structured header including the same name (one for showing changes in ECMA-262, the other for showing changes in ECMA-402) but do not result in an error from ecmarkup --lint-spec --strict, ideally because ecmarkup has a way to recognize them as distinct despite that identical name. This is not currently possible with structured headers, but is possible without them:
<emu-clause id="sec-temporal-isbuiltincalendar" aoid="IsBuiltinCalendar">

IsBuiltinCalendar ( _id_ )

<emu-clause id="sup-temporal-isbuiltincalendar" aoid="IsBuiltinCalendar402">

IsBuiltinCalendar ( _id_ )

Ah, ok. And to be clear, in the snippet you give without structured headers, you're not actually using the AOID for anything, right? That is, you don't expect to be able to write IsBuiltinCalendar402("foo")  in an algorithm step and have it link to that second definition?
The solution I'm currently envisioning is a field in the dl along the lines of
redefinition

true
, which if present would suppress that warning.
Such a field could also cause ecmarkup to

automatically add a note to the original section which links to the other definition(s)
check that the signatures are compatible

unless you're opposed.
But this solution would not have the effect of allowing you to refer to it and have the reference automatically link, like happens with IsBuiltinCalendar402 in the snippet you've given.

Ah, ok. And to be clear, in the snippet you give without structured headers, you're not actually using the AOID for anything, right? That is, you don't expect to be able to write IsBuiltinCalendar402("foo") in an algorithm step and have it link to that second definition?

Correct; the ECMA-402 version is technically referenced from other ECMA-402 operations that do appear in the proposal, but it's acceptable for those references to instead jump to the ECMA-262 version (e.g., like the IsValidTimeZoneName links in https://tc39.es/proposal-temporal/#sup-canonicalizetimezonename go to #sec-isvalidtimezonename rather than the immediately preceding #sup-isvalidtimezonename) because the target audience can be trusted to understand.

The solution I'm currently envisioning is a field in the dl along the lines of
redefinition

true
, which if present would suppress that warning.
Such a field could also cause ecmarkup to

automatically add a note to the original section which links to the other definition(s)
check that the signatures are compatible

unless you're opposed.
But this solution would not have the effect of allowing you to refer to it and have the reference automatically link, like happens with IsBuiltinCalendar402 in the snippet you've given.

Thanks, works for me!


useField return "field is not valid" when the helper validators() is not used

It is not possible to use a validator made with  const isRequired = () => createValidator(BalValidators.isRequired(), 'validator.required') directly in useField.
const {
      errorMessage: firstNameErrorMessage,
      value: firstName,
      name: firstNameName,
    } = useField('firstName', isRequired()))

Even when the validator passe it will retourn the error message firstNameName is not valid.
Using the helper function validators will works
const {
      errorMessage: firstNameErrorMessage,
      value: firstName,
      name: firstNameName,
    } = useField('firstName', validators([ isRequired() ]))

As a side note, it would be easier to be able to chain the validator to combine them like with yup : validators.isRequired().isEmail() .

Hi @gagarine
This issue will be fixed with this PR => https://github.com/baloise/design-system/pull/310
Cheers,
hirsch


Use Message instead of GeneratedMessageV3

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


feat(PeriphDrivers): Provide user a way to manually drive SPI slave select pin

Description
While using SPI manual chip drive requires, existing SPI driver drive SS pin by HW, there is no any option to disable this behaviour, This feature exactly require while porting Zephyr/MBED... On these platform i add an patch at the top of SDK layer.
It will be nice if SDK support it on default.
Checklist Before Requesting Review

[x] PR Title follows correct guidelines.
[x] Description of changes and all other relevant information.
[ ] (Optional) Link any related Github issues using a keyword
[ ] (Optional) Provide info on any relevant functional testing/validation.  For API changes or significant features, this is not optional.

@Jacob-Scheiffler @EdwinFairchild
I think I remember you two making updates to the bootloader examples (Bootloader and BLE_OTAS) and having some flash size problems for the ME17. These changes cause the project size of those two examples to exceed the flash size which throws build errors. Is there a way to provide some more space in those examples?
The library size is going to increase over time as we add fixes and features to the MSDK, so we're going to run into this issue again in the future. We may need to have a discussion about improving the memory footprint of our drivers and, as a start, enforce the proper use of integer type sizes (uint8_t/int8_t, uint16_t/int16_t, uint32_t/int32_t) in our library.

Just some minor comment revision.
It might also be useful to add a function that lets you select the slave select pin to drive if the HW CS control scheme is disabled.

It is also an option but CS pin might be a standard GPIO too, so it will be more generic if CS pin configure and drive by app layer instead of driver layer.

Can it be merged?
Thanks.

We need to resolve the build failure

@Jacob-Scheiffler @EdwinFairchild
I think I remember you two making updates to the bootloader examples (Bootloader and BLE_OTAS) and having some flash size problems for the ME17. These new SPI changes caused the project size of those two examples to exceed the flash size which throws build errors. Is there a way to provide some more space in those examples?
The library size is going to increase over time as we add fixes and features to the MSDK, so we're going to run into this issue again in the future. We may need to have a discussion about improving the memory footprint of our drivers and, as a start, enforce the proper use of integer type sizes (uint8_t/int8_t, uint16_t/int16_t, uint32_t/int32_t) in our library.

Our SPI drivers are already the biggest drivers in the SDK.  Even with -Os they're almost 7KB.
I think we should be trying to reduce this instead of forcing projects to adapt to driver bloat.
Surely we can trim 48 KB of code somewhere to get this build to pass.
arm-none-eabi-size libPeriphDriver_softfp.a

   text    data     bss     dec     hex filename
      2       0       0       2       2 mxc_assert.o (ex libPeriphDriver_softfp.a)
    468       4      12     484     1e4 mxc_delay.o (ex libPeriphDriver_softfp.a)
     38       0       0      38      26 mxc_lock.o (ex libPeriphDriver_softfp.a)
    116       0     504     620     26c nvic_table.o (ex libPeriphDriver_softfp.a)
    696       0       0     696     2b8 pins_me17.o (ex libPeriphDriver_softfp.a)
   1372       0       0    1372     55c sys_me17.o (ex libPeriphDriver_softfp.a)
    860       0       0     860     35c adc_me17.o (ex libPeriphDriver_softfp.a)
   2368       0      25    2393     959 adc_reva.o (ex libPeriphDriver_softfp.a)
    288       0       0     288     120 aes_me17.o (ex libPeriphDriver_softfp.a)
   1028       0      16    1044     414 aes_revb.o (ex libPeriphDriver_softfp.a)
    160       0       0     160      a0 crc_me17.o (ex libPeriphDriver_softfp.a)
    356       0       4     360     168 crc_reva.o (ex libPeriphDriver_softfp.a)
    330       0       0     330     14a dma_me17.o (ex libPeriphDriver_softfp.a)
   1736       0     120    1856     740 dma_reva.o (ex libPeriphDriver_softfp.a)
    266       0       0     266     10a flc_common.o (ex libPeriphDriver_softfp.a)
    542       0       0     542     21e flc_me17.o (ex libPeriphDriver_softfp.a)
    848       4       0     852     354 flc_reva.o (ex libPeriphDriver_softfp.a)
    399       0    1025    1424     590 gpio_common.o (ex libPeriphDriver_softfp.a)
   1160       0       0    1160     488 gpio_me17.o (ex libPeriphDriver_softfp.a)
    290       0       0     290     122 gpio_reva.o (ex libPeriphDriver_softfp.a)
    652       4       0     656     290 i2c_me17.o (ex libPeriphDriver_softfp.a)
   4382       0     108    4490    118a i2c_reva.o (ex libPeriphDriver_softfp.a)
    528       4       0     532     214 i2s_me17.o (ex libPeriphDriver_softfp.a)
   2137       0      56    2193     891 i2s_reva.o (ex libPeriphDriver_softfp.a)
     30       0       0      30      1e icc_me17.o (ex libPeriphDriver_softfp.a)
    110       0       0     110      6e icc_reva.o (ex libPeriphDriver_softfp.a)
   1097       0       0    1097     449 lp_me17.o (ex libPeriphDriver_softfp.a)
    312       0       4     316     13c lpcmp_me17.o (ex libPeriphDriver_softfp.a)
     88       0       0      88      58 lpcmp_reva.o (ex libPeriphDriver_softfp.a)
    508       0       0     508     1fc owm_me17.o (ex libPeriphDriver_softfp.a)
   1216       0       8    1224     4c8 owm_reva.o (ex libPeriphDriver_softfp.a)
    532       0       0     532     214 pt_me17.o (ex libPeriphDriver_softfp.a)
    771       0       0     771     303 pt_reva.o (ex libPeriphDriver_softfp.a)
    728       0       0     728     2d8 rtc_me17.o (ex libPeriphDriver_softfp.a)
    864       0       0     864     360 rtc_reva.o (ex libPeriphDriver_softfp.a)
    164       0       0     164      a4 sema_me17.o (ex libPeriphDriver_softfp.a)
    459       8      24     491     1eb sema_reva.o (ex libPeriphDriver_softfp.a)
     96       0       0      96      60 simo_me17.o (ex libPeriphDriver_softfp.a)
    232       0       0     232      e8 simo_reva.o (ex libPeriphDriver_softfp.a)
   1198       0       0    1198     4ae spi_me17.o (ex libPeriphDriver_softfp.a)
   5603       0      80    5683    1633 spi_reva1.o (ex libPeriphDriver_softfp.a)
    138       0       0     138      8a trng_me17.o (ex libPeriphDriver_softfp.a)
    460       0      16     476     1dc trng_revb.o (ex libPeriphDriver_softfp.a)
    248       0       0     248      f8 tmr_common.o (ex libPeriphDriver_softfp.a)
   1055       0       0    1055     41f tmr_me17.o (ex libPeriphDriver_softfp.a)
   2789       0      48    2837     b15 tmr_revb.o (ex libPeriphDriver_softfp.a)
     54       0       0      54      36 uart_common.o (ex libPeriphDriver_softfp.a)
   1048       0       0    1048     418 uart_me17.o (ex libPeriphDriver_softfp.a)
   3998       0      80    4078     fee uart_revb.o (ex libPeriphDriver_softfp.a)
      0       0       0       0       0 wdt_common.o (ex libPeriphDriver_softfp.a)
    160       0       0     160      a0 wdt_me17.o (ex libPeriphDriver_softfp.a)
    248       0       0     248      f8 wdt_revb.o (ex libPeriphDriver_softfp.a)
    722       0      28     750     2ee wut_me17.o (ex libPeriphDriver_softfp.a)
    582       0       8     590     24e wut_reva.o (ex libPeriphDriver_softfp.a)

Yeah there is always some issue with bootloader space on the ME17 since that baby does not have the second flash bank we partition it's single bank for bootloader and app.  That bootloader is as lean as it can get, i think asserts are turned off ? among other little tweaks, but I agree maybe the real issue is the ever-growing SPI driver so maybe tackling otherwise increasing bootloader space to buy usa  few more revisions lol

Yeah there is always some issue with bootloader space on the ME17 since that baby does not have the second flash bank we partition it's single bank for bootloader and app. That bootloader is as lean as it can get, i think asserts are turned off ? among other little tweaks, but I agree maybe the real issue is the ever-growing SPI driver so maybe tackling otherwise increasing bootloader space to buy usa few more revisions lol

Asserts are always added to PROJ_CFLAGS in the project's core Makefile.  This is left over from the original legacy Makefiles.  I'll add a better mechanism to disable them.
@EdwinFairchild @sihyung-maxim @Jacob-Scheiffler @ozersa...  Please re-approve given the changes below:
I reduced the SPI_RevA object size by 830KB by removing unnecessary asserts (https://github.com/Analog-Devices-MSDK/msdk/pull/674/commits/acaf898598981b6c5df9b1e66fdc8deea7ee647f)
Almost every single function had something along the lines of
int spi_num;
spi_num = MXC_SPI_GET_IDX((mxc_spi_regs_t *)spi);
MXC_ASSERT(spi_num >= 0);
(void)spi_num;

As a check to ensure the function has a valid MXC_SPIN this is useless.  The functions accept mxc_spi_regs_t, so the compiler will complain about undefined symbols at compile time.

As a check to ensure we don't access memory out of bounds of the state array it's more logical but still essentially useless.  The only way the user can cause the assertion to return -1 is to give it an undefined MXC_SPIN.  See point above.

Yeah there is always some issue with bootloader space on the ME17 since that baby does not have the second flash bank we partition it's single bank for bootloader and app. That bootloader is as lean as it can get, i think asserts are turned off ? among other little tweaks, but I agree maybe the real issue is the ever-growing SPI driver so maybe tackling otherwise increasing bootloader space to buy usa few more revisions lol

Asserts are always added to PROJ_CFLAGS in the project's core Makefile. This is left over from the original legacy Makefiles. I'll add a better mechanism to disable them.
@EdwinFairchild @sihyung-maxim @Jacob-Scheiffler @ozersa... Please re-approve given the changes below:
I reduced the SPI_RevA object size by 830KB by removing unnecessary asserts (acaf898)
Almost every single function had something along the lines of
int spi_num;
spi_num = MXC_SPI_GET_IDX((mxc_spi_regs_t *)spi);
MXC_ASSERT(spi_num >= 0);
(void)spi_num;

As a check to ensure the function has a valid MXC_SPIN this is useless.  The functions accept mxc_spi_regs_t, so the compiler will complain about undefined symbols at compile time.
As a check to ensure we don't access memory out of bounds of the state array it's more logical but still essentially useless.  The only way the user can cause the assertion to return -1 is to give it an undefined MXC_SPIN.  See point above.

Looks good, I like clean code.
Thanks.

Yeah there is always some issue with bootloader space on the ME17 since that baby does not have the second flash bank we partition it's single bank for bootloader and app. That bootloader is as lean as it can get, i think asserts are turned off ? among other little tweaks, but I agree maybe the real issue is the ever-growing SPI driver so maybe tackling otherwise increasing bootloader space to buy usa few more revisions lol

Asserts are always added to PROJ_CFLAGS in the project's core Makefile. This is left over from the original legacy Makefiles. I'll add a better mechanism to disable them.
@EdwinFairchild @sihyung-maxim @Jacob-Scheiffler @ozersa... Please re-approve given the changes below:
I reduced the SPI_RevA object size by 830KB by removing unnecessary asserts (acaf898)
Almost every single function had something along the lines of
int spi_num;
spi_num = MXC_SPI_GET_IDX((mxc_spi_regs_t *)spi);
MXC_ASSERT(spi_num >= 0);
(void)spi_num;

As a check to ensure the function has a valid MXC_SPIN this is useless.  The functions accept mxc_spi_regs_t, so the compiler will complain about undefined symbols at compile time.
As a check to ensure we don't access memory out of bounds of the state array it's more logical but still essentially useless.  The only way the user can cause the assertion to return -1 is to give it an undefined MXC_SPIN.  See point above.

I thought the assert was for cases when the user defines its own SPI instance instead of using the predefined instances in the CMSIS part header file. Although rare for this to happen, it's meant for scenarios like this.
#define SLAVE_SPI_BASE ((uint32_t)0x12345678UL) // Purposefully added incorrect SPI base address.
#define SLAVE_SPI ((mxc_spi_regs_t *)SLAVE_SPI_BASE)

Alternatively, I can do a separate PR just for the SPI RevA file and we can rebase on that.  We could merge that in a few minutes.

@ozersa My changes have been reverted in favor of the separate PR

Rebased this branch, @Jacob-Scheiffler ready to merge pending your approval


net7.0 support

I know that .NET 7 has an in-built rate limiter, and I know that it's implied via .NET Standard 2.0 and 2.1 support, but if you've tested your code on .NET 7 then perhaps you should update the README.md to reflect this.

.Net 7.0 is supported and also, I've updated the README.md


selectTab with bug

After initialization selectTab (), the first Tab text or display the state.
BottomNavigationBar.MODE_SHIFTING

Please provide solution. I am facing same issue.

check latest release

i am facing :startActivityForResult(requestcode),but in method "onActivityResult",selectTab(position) is useless. so it is "show()";


[Map] MH-NOFF(ScriptsOnly)

URL: https://unrealarchive.org/maps/unreal-tournament/monster-hunt/N/mh-noffscriptsonly_b7030f7a.html
Hash: b7030f7a714e25aa67abcf1f6ccf00bd52cb9dae
Current name: MH-NOFF(ScriptsOnly)
This is made by gopostal (Kelly/Jack Griffin) - it is not a playable MH map but a Demo map for the No Friendly Fire actor that stops monsters from attacking one another in all circumstances.

Moved to tests and demos


fix: filetype patterns with wildcards

Problem
While inspecting the generated filetype:servers mapping, I realized there are servers with * wildcards in their filetype patterns.
return {
  filetype_servers = {
    ["*"] = { "typos_lsp" },
    ["*.hl"] = { "hyprls" },
    [".config/hypr/*.conf"] = { "hyprls" },
    ["hypr*.conf"] = { "hyprls" },
  },
}

auto-lsp.nvim cannot deal with these as the filetype lookup is done through simple table indexing.
Solution

Investigate upstream and find out why exactly those patterns are required.
Scan through the entire mapping every time.
Register separate autocmds just for each of those filetypes with wildcards.

They were mistakes from upstream.
typos_lsp
The * filetype is unnecessary. Generic servers can just omit filetypes field completely, and lspconfig will launch them upon BufReadPost instead of FileType.
hyprls
https://github.com/hyprland-community/hyprls/issues/11#issuecomment-2189841216

Hi! I actually did a PR for lspconfig to include hyprls (see neovim/nvim-lspconfig#3137) but it's misconfigured: I mistook filetypes for file name patterns...
However someone fixed my mistake lmao, thx @mehalter
So the lspconfig should work if the hyprlang filetype is defined

It was a mistake, and the filetypes with wildcards can be removed completely.

neovim/nvim-lspconfig#3273


redirect_uri must not contain #simply-edit

The OAuth2 spec explicitly forbids redirect_uri with a #hash. (https://datatracker.ietf.org/doc/html/rfc6749#section-3.1.2) "The redirect uri must not include a hash".
So instead of redirecting to #simply-edit, must redirect to ?simply-edit or something like it.
The problem there is that simply.route doesn't allow routing on ?..., so the main route must handle this case and switch to the editmode page.

slightly more involved fix, since solid-auth-fetcher doesn't like ?simply-edit=1 in the search params, but this problem is now fixed. If ?simply-edit is in the url, the start base component filters it out and redirects to the same url with #simply-edit


Optimized clang.wasm

Looks like clang.wasm on the demo site wasn't optimized by wasm-opt. Attached is an optimized version, which is 13% smaller (34.10 MB to 29.77 MB)
clangO.wasm.gz

Nice, thanks! You may want to take a look at lld too.

Sure, attached.
lld is almost half the size, 34 MB to 19 MB.
lldO.wasm.gz

Updated here: https://github.com/binji/wasm-clang/commit/88838f3cf4a4e7dfae026fce4ef81c880f297808


<EMAIL_ADDRESS>hash check failed

Checking hash of balenaEtcher-Setup-1.4.8-x64.exe ... ERROR Hash check failed!
App:         Extras/etcher
URL:         https://github.com/balena-io/etcher/releases/download/v1.4.8/balenaEtcher-Setup-1.4.8-x64.exe#/dl.7z
First bytes: 4D 5A 90 00 03 00 00 00
Expected:    b8f8114cc2e106c2a9bd4b1855180f547b7da6ffbcb763c66a8d0d3a1655fb0c
Actual:      e96da0150428e29c9effcd6a32175a36ad49ffd5c7e5ae3823deea6b239f2ebb
Don't have time to day make pull, hope someone can :)

b8f8114cc2e106c2a9bd4b1855180f547b7da6ffbcb763c66a8d0d3a1655fb0c is the correct hash, please try again.


Add a Quassel IRC Helm Chart

Add a Quassel IRC Helm Chart
Quassel IRC is a modern, cross-platform, distributed IRC client, meaning that one (or multiple) client(s) can attach to and detach from a central core.
Quassel Homepage: https://quassel-irc.org/

/assign @seanknox

Assigning seanknox as requested by the bot :)

Thanks for the PR. Looks really good. I'd suggest you move it to stable directly.

Done.

EDIT: Let me update the readme references. Derp.

Done.

/ok-to-test


Supernovas file

This PR creates a supernovas output file with all the SN rates for Types Ia and Ib integrated by time and mass

Closed in favor of #3


#4399: add spell checker script for docs spellchecking

#4399: add spell checker script for docs spellchecking

Rebased for you. Pls fetch and hard reset to origin.


Add default (in Quarto params) and custom (in metadata) dead bands

See #6
Example
With default dead band:

With custom dead band of 60 seconds specified in the metadata:

☝ fyi @wilsonsj100 I think this addresses your https://github.com/COMPASS-DOE/sw/issues/6#issuecomment-1401238237

That should work! Just to clarify: do do we put in the custom deadband when we are in R or do we have to go back to the meta-data file? Also does the code flag and automatically go back and recalculate that flux or?

Above, the first figure shows flux model fit with default dead band of 10s; and the second, with a custom 60s dead band.

Ah okay I think I understand that now. We should write that in the code notes / protocol and say that if you have to change the deadband then you should put a note in the notes section.
Thanks!


Lcd

While testing my #867 PR, I found out that the lcd nodes were rotting bad. It took me a while to fix the concurrency/bad access issues, but here it goes.
@zehortigoza, could you help reviewing?

+2, works for me. Just s/calloc/malloc as Leandro pointed.

Thanks, everybody. Merging soon with the due fixes.


Gray not available for Aplite colorpickers

It is possible to fill a shape with a 'gray' color on aplite (dithered gray) but the colorpickers on aplite config pages only allow to choose white or black.
I don't know if the colorpicker should propose also this new color or if the developer needs to specify its own palette in the config.json

sorry... I didn't read the documentation :-p


Add tests for rewriting headers and status.

Ah, bad timing, we simultaneously duplicated each others efforts.

I forgot to add orig_response to the signature in my test case...

I think my tests cover the same as your tests, but slightly more. Anything you think I should add?

No worries, thanks!


Adding automatic formatter to development pipeline

To be discussed in sprint planning

Formatter options reside in workspace settings file (tentative version):
{
    "python.analysis.typeCheckingMode": "strict",
    "python.testing.pytestArgs": [
        "src"
    ],
    "python.testing.unittestEnabled": false,
    "python.testing.pytestEnabled": true,
    "editor.formatOnSave": true,
    "python.formatting.provider": "black",
    "python.formatting.blackArgs": [
        "--line-length=80"
    ],
    "isort.args": [
        "--profile",
        "black"
    ],
    "python.linting.mypyEnabled": true,
    "python.linting.mypyArgs": [
        "--follow-imports=silent",
        "--ignore-missing-imports",
        "--show-column-numbers",
        "--no-pretty"
    ],
    "python.linting.pylintEnabled": true,
    "[python]": {
        "editor.codeActionsOnSave": {
            "source.organizeImports": true
        }
    }
}

But this occupies whole of the workspace settings file - what if developer needs local overrides?
Discussed here: https://github.com/Microsoft/vscode/issues/37519

Closing this in favour of using new Workspace as a solution.

=> Look into workspace settings.
So the task is:

Coming up with formatter configuration that matches CI/CD pipeline's
Coming up with an unintrusive way to version control the configuration

Need an editor-agnostic solution, independent of VS Code.
E.g., git hook? Shell script that can be invoked by editor of choice?

https://towardsdatascience.com/python-code-formatting-made-simple-with-git-pre-commit-hooks-9233268cdf64


Add fermosit helm repository.

Add fermosit repository with Zabbix chart.

The Artifact Hub, a CNCF sandbox project, is another place you can list your repos. To do that, you login (or create an account), create an organization, and list your repository. You can link it to a user or organization.


Change VM public networking

Change the public network for creating PowerVS VMs as the old public network does not exist anymore.

/cc @Rajalakshmi-Girish

/approve


x/net/html: panic: runtime error: invalid memory address or nil pointer dereference

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.10.3 linux/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GORACE=""
GOTMPDIR=""
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"

What did you do?
package main

import (
	"strings"

	"golang.org/x/net/html"
)

func main() {
	r := strings.NewReader("<template><tBody><isindex/action=0>")
	html.Parse(r)
}

What did you expect to see?
No panic exit.
What did you see instead?
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x58 pc=0x47fd29]

goroutine 1 [running]:
golang.org/x/net/html.inBodyIM(0xc420118410, 0x4caa68)
        /path/to/gopath/src/golang.org/x/net/html/parse.go:988 +0x1d49
golang.org/x/net/html.inTableIM(0xc420118410, 0xc42014a000)
        /path/to/gopath/src/golang.org/x/net/html/parse.go:1433 +0x20e
golang.org/x/net/html.inTableBodyIM(0xc420118410, 0x0)
        /path/to/gopath/src/golang.org/x/net/html/parse.go:1590 +0x145
golang.org/x/net/html.(*parser).parseCurrentToken(0xc420118410)
        /path/to/gopath/src/golang.org/x/net/html/parse.go:2180 +0x84
golang.org/x/net/html.(*parser).parse(0xc420118410, 0xc42014c000, 0xc420118340)
        /path/to/gopath/src/golang.org/x/net/html/parse.go:2206 +0x5b
golang.org/x/net/html.Parse(0x4d5b00, 0xc42000a0e0, 0xc420110150, 0xc4200dff78, 0xc42001a118)
        /path/to/gopath/src/golang.org/x/net/html/parse.go:2232 +0xdb
main.main()
        /path/to/gopath/src/html/main.go:11 +0x73
exit status 2

Hello @tr3ee, thank you for reporting this issue and welcome to Go!
I noticed that you already filed https://github.com/golang/go/issues/27702 with a somewhat similar repro but different crash stacktrace. I believe the common issue in both of them is incomplete tags?
If the issue is the same, would you mind closing this one? A consolidated issue is easier to track but also please provide the content of this bug as a reproducer for that issue. If not, please ignore my comments..
In the meantime, I'll page @nigeltao @namusyaka

Hello @odeke-em , thank you for your reply.
It's ok if you close this, and I will re-edit the content of issue #27702 .

Hello @odeke-em ,
After discussing with the CVE Assignment Team members, I think it's best to reopen this issue, because of CNA rules counting_decisions

@tr3ee Thank you for your report!
This isn't same with #27702 so I will fix these issues separately.


Unable to install

I have tried to install the provider under WSL and a linux VM while following the documentation. Both times I have been unable to initialize terraform as it seems to be unable to find the provider in the registry?
Could you please help? I've run out of good ideas.
root@andromeda-terraform:~# go version
go version go1.15.2 linux/amd64

root@andromeda-terraform:~# terraform -version
Terraform v0.13.2

root@andromeda-terraform:~# ls -lah ~/.terraform.d/plugins/
total 59M
drwxr-xr-x 2 root root 4.0K Sep 10 20:41 .
drwxr-xr-x 3 root root 4.0K Sep 10 20:43 ..
-rwxr-xr-x 1 root root  30M Sep 10 20:41 terraform-provider-proxmox
-rwxr-xr-x 1 root root  29M Sep 10 20:41 terraform-provisioner-proxmox

root@andromeda-terraform:/home/abigail/abigail-terraform/andromeda# cat main.tf

provider "proxmox" {
    pm_api_url = "https://<proxmox-ip>:8006/api2/json"
    pm_user = "root@pam"
    pm_password = "<password>"
    pm_tls_insecure = "true"
}

root@andromeda-terraform:/home/abigail/abigail-terraform/andromeda# terraform init

Initializing the backend...

Initializing provider plugins...
- Finding latest version of hashicorp/proxmox...

Error: Failed to install provider

Error while installing hashicorp/proxmox: provider registry
registry.terraform.io does not have a provider named
registry.terraform.io/hashicorp/proxmox

Figured it out. This provider does not seem to work in the most recent version of Terraform. I went back a major version from v0.13.2 to v0.12.17 and it worked straight away. That should probably be in the docs!

Thanks for posting this.... I'm new to terraform and this was driving me insane. It should absolutely be included in the docs!


enh: use front-edge v1 as prod api from front-edge

Description
Testing on front-edge can be deceptive, because the "public api" used is still actual prod instead of being front-edge's v1 api
Risk

Deploy Plan

Thank you! Always wondered if it was or was not using edge. Now we know and this is def the intended state


bugfix insert into select profile could not build successfully

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

Do we need to change "OlapTableSink" to "VOlapTableSink" here?
Status GroupCommitBlockSink::prepare(RuntimeState* state) {
    RETURN_IF_ERROR(DataSink::prepare(state));
    _state = state;

    // profile must add to state's object pool
    _profile = state->obj_pool()->add(new RuntimeProfile("OlapTableSink"));
    init_sink_common_profile();
    _mem_tracker =
            std::make_shared<MemTracker>("OlapTableSink:" + std::to_string(state->load_job_id()));
    SCOPED_TIMER(_profile->total_time_counter());
    SCOPED_CONSUME_MEM_TRACKER(_mem_tracker.get());


regex search not working when using complex regex

VS Code Version: 1.58.2
OS Version: MacOS 11.5.2 (20G95)

Steps to Reproduce:

Open up the search tab
Enable the regex search
Use the regex ^(?=[\s\S\n]*(Landroid\/view\/Window;->addFlags))(?=[\s\S\n]*(0x2000))[\s\S\n]*$ to search

No results will be returned. Search will keep running indefinitely.
This regex actually matches a smali source code: https://regexr.com/6525n

This is probably https://github.com/microsoft/vscode/issues/30874, you could try simplifying the regex


Fix compatibility with ruamel.yaml 0.18.5

yaml.safe_load has been removed after having been deprecated since 0.17.0.

Thanks @FriedrichFroebel


Create SparkLeapFrameTransformBuilder

This will require creating a converter form MLeap UDFs to Spark UDFs

Began work on this that looks promising, just need to add in tests to make sure it is working as expected. See https://github.com/combust-ml/mleap/compare/feature/udfs...feature/spark-integration for work done so far.

Done with PR #19


Cannot use ngx-store

I'm submitting a ...  (check one with "x")
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[x] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request

Current behavior

Install https://github.com/zoomsphere/ngx-store
run npm run build:universal prod
run npm run serve

Error:
ReferenceError: localStorage is not defined
at Object. (/Users/personal/code/udoma/webapp/.server/server.js:1:2943050)
at webpack_require (/Users/personal/code/udoma/webapp/.server/server.js:1:285)
at Object.module.exports.list (/Users/personal/code/udoma/webapp/.server/server.js:1:553740)
at webpack_require (/Users/personal/code/udoma/webapp/.server/server.js:1:285)
at Object. (/Users/personal/code/udoma/webapp/.server/server.js:1:779544)
at webpack_require (/Users/personal/code/udoma/webapp/.server/server.js:1:285)
at Object. (/Users/personal/code/udoma/webapp/.server/server.js:1:623706)
at webpack_require (/Users/personal/code/udoma/webapp/.server/server.js:1:285)
at Object. (/Users/personal/code/udoma/webapp/.server/server.js:1:778813)
at webpack_require (/Users/personal/code/udoma/webapp/.server/server.js:1:285)
Expected/desired behavior
Run smoothly
QUESTION:
How I can define it only for the browser. Can I create second custom decorator which is checking the platform?

Probably it was a problem with the module. I switched to https://github.com/PillowPillow/ng2-webstorage and it works perfectly for now


Request type change applies to all related ministry requests

Current behavior:
Assign a request to multiple ministries and open the request. System will create a new request for each assigned ministry. If changing the request type for one of the newly created ministry requests (personal to general or vice versa), the change applies to all related ministry requests.
Questions for business:

[ ] Need to confirm with business whether this behavior is by design or not. If not, we need to fix it ASAP.

[ ] Another question is shall the system keep the personal information if changing a request from personal to general. e.g. "on behalf of details", "child details" and "additional applicant details". (currently, the system will keep "on behalf of details" and "child details")

Discussion at Jan 19 sprint planning - This is an edge case - For ease, need to separate the requests out if request type, delivery mode, application category changes during the process

Q: If changing a request from personal to general - Do we need to delete personal fields? A: Fields should disappear from front end but will remain in backend. Attachments will remain in Attachments Log

@jadmsaadaot - As per our discussion, 4 fields(requesttype, applicantcategory, deliverymode, receivedmode) which is editable from the OPEN state 'onwards' need to be moved to FOIMinistryRequests Table., from the FOIRequests. This bug arises since those 4 fields are editable. So, we need to make those editable on(or from OPEN status), then we have a higher effort on backend. But if we decide to make it "UNEDITABLE/ DISABLED"  then its minor effort on front end.
@m-prodan , @JHarrietha-AOT @arielleandrews @lmullane -Thoughts?

Decision at refinement Jan 28/22: Go with option #2.

ready for qa

QA completed. This works as expected: Request type, applicant category, received mode and delivery mode are editable while request is in Intake in Progress but disabled once moved to Open. Nice work @jadmsaadaot!

@jadmsaadaot, can you please add an estimate to this ticket.


DSA-Regions extra Constraints

for the test "offsetting from middle of cell to a new cell" the dsa-regions introduces extra constraints to the DS Graph
Before it the program DSG looked like

Now it looks like this:

The higher Node ID's indicate that extra merges are occuring but I'm not sure why yet

That is weird, I'm not sure why that would be happening either. This test is a bit of an edge case, so there may be some quirk to it I overlooked.

In mergeCells
val collapsedCell = resultNode.addCell(offset, resultLargestAccesses(offset))
        val outgoing: Set[Slice] = cells.flatMap { (_, cell) =>
          if (cell.pointee.isDefined) {
            Some(cell.getPointee)
          } else {
            None
          }
        }.toSet

Instead of cells.flatMap, it should be resultCells(offset).flatMap This was fixed with the overlapping accesses, so once that's merged it should be fixed

The extra merges are to be expected since we are merging the Indexes with corresponding value in the index map


Initial version of CLI docs

I think in the long run this may be a bit verbose, but for the time being it's ostensibly better than TODO :wink:

Codecov Report

Merging #886 (bae49f1) into master (67d7624) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #886   +/-   ##
=======================================
  Coverage   51.75%   51.75%
=======================================
  Files          80       80
  Lines        6056     6056
=======================================
  Hits         3134     3134
  Misses       2743     2743
  Partials      179      179

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 67d7624...bae49f1. Read the comment docs.


Support resolve relative asset path in homepage

See MoePlayer/hexo-tag-dplayer#10

unknown block tag: aplayer


obsolete GO:0010108 detection of glutamine

Please provide as much information as you can:

GO term ID and Label
GO:0010108 detection of glutamine

Reason for deprecation
This sounds like what might be a collection of different processes?

"Replace by" term (ID and label)
I will request a new term for something that functions as a glutamine sensor

"Consider" term(s) (ID and label)
Suggestions for reannotation

Are there annotations to this term?
I don't think so?

Are there mappings and cross references to this term? (InterPro, Keywords; check QuickGO cross-references section)

no

Is this term in a subset? (check the AmiGO page for that term)

Any other information

How about if we create 'nutrient sensor activity', and suggest to replace
GO:0009594 detection of nutrient
GO:0010108 detection of glutamine
GO:0031318 detection of folic acid
with that new MF, and use has_input to specify the exact chemical?
SGD has 2 annotations from PMID:34535752
@srengel Does that sound OK to you?
Thanks, Pascale

@ValWood

SGD has 2 annotations from PMID:34535752

Oh I wasn't aware. I did not see this in P2GO...I guess it will be imported at some point

sounds ok to me @pgaudet

@ValWood  pinging myself to update pombe pib2

Oh now I can see the annotations in SGD - I guess it was just some glitch

It's in AmiGO ..
http://amigo.geneontology.org/amigo/term/GO:0010108
and in Noctua, indeed : http://noctua.geneontology.org/editor/graph/gomodel:617b481400003011
I guess SGD loads a file from Noctua that QuickGO doesn't ?
@srengel @suzialeksander
Thanks, Pascale

yes SGD loads annotations from P2GO and from Noctua.

So doesn't the EBI load the annotation that so into AmiGO from Noctua into QuickGO?

No. This is on the to-do list.

The parent term of GO:0010108 detection of glutamine is GO:0009593 detection of chemical stimulus. Perhaps it is sufficient to merge them? There is a MF GO:0070406 glutamine binding I believe appropriate for Sc PIB2 annotation.
IMHO, "nutrient sensor activity" sounds like a rather complex MF (with BP built in).

The BP 'detection' is a single step, that for most other terms represents some sensor activity (see small molecule sensor activity & children).
Maybe to discuss on the next ontology call?
Thanks, Pascale

There is a MF GO:0140786 glutamine sensor activity.

My feeling on this is that "nutrient sensor activity" seems like something that is context dependent, e.g. one organism's nutrient maybe another's waste. In other words, such MF terms have an implied purpose (BP). In the case of chemical reactions, we usually don't assign directions thus we are agnostic about what the desired product is.

My feeling on this is that "nutrient sensor activity" seems like something that is context dependent,

it is, but when the nutrient sensor term is used as an MF term  we would only use it in the correct context of specifying a known nutrient?  These sensor terms are essential for modeling, because they determine the starting point of a pathway (indicating that other indirect affects are causally upstream).

i have removed the two SGD annotations.  in noctua, which was not easy to do in any intuitive way.  hope i didn't mess it up.

@srengel Thanks!

i have removed the two SGD annotations. in noctua, which was not easy to do in any intuitive way. hope i didn't mess it up.

@srengel - it'd be helpful to know what changes you made and why it didn't seem easy to do in an intuitive way.  We can follow-up offline.  Thanks.


compiler: Document side effects when adding documents vs adding executables

When using the compiler with a single GQL-Schema added via add_type_system and multiple GQL-Operations that are added after an initial validation of the schema, there can be significant performance differences in the validation of the operations  depending on the procedure.
According to the documentation, add_document should behave similarly to add_executable, but with the added ability to accept SDL input. However, it seems to trigger re-validation of the initially validated schema, even without any new types added, which can be costly for large schemas.
For my testing & benchmarking, I used the GitLab schema with 60000 lines of SDL. Validation using apollo-compiler takes ~ 40 ms on my machine. Validating a 250 line nested query with inputs and variables against this schema takes ~1ms. If I use add_document for a query against this schema, the operation validation time increases to ~40ms. I have attached a simple example below.
The issue seems to be the definition of  type_definition_files in the InputDatabase.  Since at this stage, all of the documents should be unparsed sources, there is no way to exclude them from the type system in case the root document node doesn't contain any types, am I reading that correctly?
If this is the intended behavior, it would be very helpful to clarify the possible side effects in the documentation or adjust the nomenclature.
Intuitively, every executable is a document node with definition nodes consisting of only operation and fragment nodes, so there should be no issues with add_document in this case.

Repro
fn bench_simple_query_compiler_with_validation() {
    let query = include_str!("testdata/simple_query.graphql");
    let schema = include_str!("testdata/simple_schema.graphql");

    let mut compiler = ApolloCompiler::new();
    compiler.add_type_system(schema, "schema.graphql");

    compiler.db.object_types();
    compiler.validate();

    let start = Instant::now();

    let file_id = compiler.add_document(query, ""); // FIXME use add_executable instead

    let elapsed_parsing = start.elapsed();
    let mut diagnostics = compiler.db.ast(file_id)
        .errors()
        .into_iter()
        .map(|err| {
            ApolloDiagnostic::SyntaxError(SyntaxError {
                src: compiler.db.source_code(file_id),
                span: (err.index(), err.data().len()).into(),
                message: err.message().into(),
            })
        }).collect::<Vec<ApolloDiagnostic>>();

    let elapsed_parser_syntax_check = start.elapsed();
    // We only want to validate the new operation against the schema here, everything else is already validated
    diagnostics.extend(compiler.db.validate_executable(file_id));

    let elapsed = start.elapsed();

    println!("Time elapsed after parsing is: {:?}", elapsed_parsing);
    println!("Time elapsed after syntax error check is: {:?}", elapsed_parser_syntax_check);
    println!("Time elapsed after parsing & validation is: {:?}", elapsed);
}

oooofff, that sounds like a bug actually! Type system re-validation should not be triggered for an already validated type system, especially since the original type system was not updated. Under the hood salsa caches all internal queries given their input stays the same, and since the inputs for the type system validation queries has not changed, we should be incurring the cost of additional parsing.
Going to investigate this a bit more!

The input for the type system queries has indeed changed since they're all relying on aggregating typed from type_definition_files, as mentioned above. I'm not sure if salsa can cache that kind of case, since all underlying inputs change  but the change doesn't impact the output of the computation (because no types were added)

I expect this should be fixed in apollo-compiler 1.0: the public API no longer has compiler objects. Schema validation and executable validation should now be completely separate.
If you have both a schema and a query in the same file, add_document is replaced by parse_mixed which returns a tuple of Schema and ExecutableDocument whose respective validation is still separate.
PR https://github.com/apollographql/apollo-rs/pull/676 adds a rough port of your repro code. I didn’t have your 250 lines query so I ran it with a very simple one instead. Please let us know if you still find something suspicious!

I will close this issue, as we've redesigned the compiler with the 1.0.0-beta.x releases and this side effect is no longer there. Feel free to reopen if something isn't right still.


Fix processing of function calls in templates

Currently the following is impossible. This should be relatively easy to fix.
ie. Passing the attributes to exclude to AttributesHTML
<% component FormTextInput, "Class=$AttributesHTML('class')" %><% end_component %>

This is fixed.


Fix typo s/precidence/precedence/

This PR fixes just a typo, I found it in https://github.com/rubyide/vscode-ruby/pull/709
If this change is not needed, please close this PR 🙏

@kachick thank you for the PR! However, we pull this file from an upstream repo with a script, so the next time that script is run your change would get overwritten. If you want to make this change, please consider making a PR to the upstream repo.
https://github.com/microsoft/vscode/blob/3f1f36333d3453f67a36b6bfb1206e9159e9c4f0/extensions/ruby/syntaxes/ruby.tmLanguage.json#L2-L6

@alexr00 Yes, I already did it in https://github.com/textmate/ruby.tmbundle/pull/138. It is merged. So I should just wait for script is run?

Ah, I didn't read carefully enough! I'll be running the script to pull grammar changes next week so the change will come in then.

Thank you for the updating plan! 🙏
BTW...  https://github.com/textmate/ruby.tmbundle was root repository, but looks not active than VSCode community for now. 😅
Don't you plan to import syntaxes from other active extensions? An example, https://github.com/rubyide/vscode-ruby 🤔

@kachick since there are rarely issues with the ruby grammar we have no plans to change which repo we get our grammar from.

Hmm... Sure! Thanks for the answer! 🙏


feat(deps): general dependency maintainance tooling

apps all need dependency maintenance, but it's usually hard as there is zero support for it
this adds a couple hooks in the style I have in all my apps so you can hook from monorepo scripts
at a higher level or just run them here
also updates deps, and fixes a pod install issue I had in a project

Yes, nice enhancement! 🚀 Thanks


MTV-1717 | Wait for DV status to not be paused

Issue: When CDI is managing lot of DVs at once it can take some time before the CDI reconciles the DVs status and start the import. In the function updateCopyProgress we check the DV status and if it is paused we do continue and as next phase we have snapshot removal. So if the DV is still in paused state and we start the cutover and MTV skips over the phase thinking it already finished as the DV is in paused.
Fix: Add WaitForDataVolumesStatus phase to wait until the DVs do not have the paused status.
Ref: https://issues.redhat.com/browse/MTV-1717
https://github.com/kubev2v/forklift/blob/ea83264881b3dcd4a88dd627c1ca75da2483f408/pkg/controller/plan/migration.go#L1573-L1575

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 22 lines in your changes missing coverage. Please review.

Project coverage is 15.63%. Comparing base (38f14ec) to head (2dd3022).
Report is 5 commits behind head on main.

Files with missing lines
Patch %
Lines

pkg/controller/plan/migration.go
0.00%
22 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1243   +/-   ##
=======================================
  Coverage   15.63%   15.63%
=======================================
  Files         112      112
  Lines       23105    23149   +44
=======================================
+ Hits         3612     3620    +8
- Misses      19208    19241   +33
- Partials      285      288    +3

Flag
Coverage Δ

unittests
15.63% <0.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Merging for 2.7.6 release any notes I'll address in further PRs


Reset millis to 0

Fixes #51

Codecov Report

Merging #53 into master will increase coverage by 0.11%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #53      +/-   ##
=========================================
+ Coverage   94.39%   94.5%   +0.11%
=========================================
  Files          58      58
  Lines         820     837      +17
  Branches       32      41       +9
=========================================
+ Hits          774     791      +17
  Misses         46      46

Impacted Files
Coverage Δ

...src/main/scala/cron4s/lib/joda/JodaInstances.scala
92.5% <100%> (+2.17%)
:white_check_mark:

...n/scala/cron4s/lib/threetenbp/JSR310Instance.scala
100% <100%> (ø)
:white_check_mark:

...ala/cron4s/lib/javatime/JavaTemporalInstance.scala
100% <100%> (ø)
:white_check_mark:

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 f808712...1bf9c5b. Read the comment docs.


Ensure consistency of ellipsis usage in user guide

#362

Shouldnt the ... for find be after the bracket? To match with tag and command notes

Isn't is written like that already


Add Package project status attribute?

Issue description
I noticed that we have some packages where the upstream project is officially unmaintained or had no activity for 8 years. I think it would be helpful for package maintainers and users to mark such packages.
We would have to add a new meta attribute like:
meta.project-status (one word would be preferred)
that can have several states
maintained (default)
unmaintained (official upstream statement)
example: qsyncthingtray (last release 5 years ago, unmaintained)
abandoned (no update for X years)
example: syncthing-tray (last release 8 years ago)
I think we can keep such packages (like we do right now) for those that are still using them, but remove when they become broken or insecure. A package lifecycle diagram might be nice for the documentation.
We can show the project status in the search with a colored label: green, orange, blue
We could also include broken and insecure packages and show a big warning, so users know the packages exist and need some work.
With the new meta attribute, we can also add options like allowBroken:
allowUnmaintained = true;
allowAbandoned = true;
(default true, so the behavior does not change. users can change that)
Also the option to allow single packages:
permittedUnmaintainedPackages = [];
permittedAbandonedPackages = [];
We can create a script to check how long a package (definition) had no update and check the upstream status.
We have to think about the wording to not conflict the project status with out package maintainership status. Many packages have no maintainer set, so they are technically unmaintained.
What do you think?

This sounds like something covered by/can be integrated into nixos/rfcs#127, but I have no idea of the Implementation Status of the RFC.

Also, I'd explicitly call it "upstreamMaintained" or something, to make the distinction clear

since i have a bit of experience with adding meta attributes, i would name this abandoned and make it a boolean set to false by default.
the documentation would say "this package has been officially abandoned by the upstream maintainers"
however, i'm not entirely sure how useful this would be, since you can always just check the repo to see how long it's been since the last commit.
maybe i'll implement this if my other metadata PRs get accepted (otherwise i would have to deal with a fair few merge conflicts)

Rather than try to assign an exact duration to 'unmaintained', it might be better to put the date (or just year) of the last non-bot revision/patch into meta and let the consumer decide.


Travis: Add oraclejdk10

Coverage decreased (-0.02%) to 89.617% when pulling 29c39200d03f60f9f18a413b7e473e5d18041aef on PascalSchumacher:travis_java_10 into 9ba69d7b9af1ab71e0ca2d0044f464261ae6a199 on apache:master.


Add HTML alerts for web builds.

For every FlxG warn in PlayState.hx there is a js function that makes an alert if you are compiling to HTML5. Seems pretty self-explanatory doesn't it?
Tell me if there are any other FlxG warns you want me to put a js function into.

maybe make it so that it adds warning messages if you're using debug mode for haxe

maybe make it so that it adds warning messages if you're using debug mode for haxe

That's already used with FlxG.log.warn()

Surprised this hasn't been closed yet.


docs: fix entry variable

Description (required)
Fixes the documentation in the Querying and rendering with the Content Layer API section section, where a variable named entry was used without a prior definition. It has been updated to correctly reference the post variable instead.

Username of Astro Discord: fbuireu

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any broken links you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Netlify 🥳.

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
reference/configuration-reference.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Thanks for this fix @fbuireu, and welcome! 🎉
Just a side note about configuration-reference.mdx contents. This file is auto-generated from JSDoc comments in withastro/astro repository (see Where to find docs source content). To avoid your fix being overwritten the next time the file is generated, the PR should be made on withastro/astro repository.
However, in this case, the same fix (https://github.com/withastro/astro/pull/11814) is already awaiting approval, so that's not a problem. 😉

Haha, thanks. I missed the filename :sweat_smile:


Improve test descriptions on Secret handshake

Use hexadecimal numbers to relate test descriptions and test implementations.

Much better.  Thanks!


Version fixes

The newest sysctl cookbook drops Chef 11.x compatibility.  This PR reverts to v0.7.5
The newest fpm and json gems drop ruby 1.9 compatibility.  This PR reverts to a prior json that retains 1.9.x support.

You've tested these changes?

Yep, it Works On My Machine™


Review

Updated choices to display as buttons. @sdurandeu - Please redo the screenshots to use buttons rather than text, or we can see if we can get the test team to do that.

Sure. We are working on this today, sorry for the delay.


Fightboard display layouts

This adds display layouts for both the regular and mirrored Fightboards.

@thnikk we're having a problem merging fsdata.c.
Since this is built by our web configurator, could you revert changes to /lib/httpd/fsdata.c and commit? Then we'll squash & merge this and build w/ your webconfigurator changes.

I'm not sure if my upstream merge was necessary but that should do it.


Add license

Can you please add license for this project, something like Apache or MIT?
I will be happy to add more functionality after it will be added

@klg71 Can you please share your thought about it? I want to know if I will be able to use this project or I need to find another solution. Thank you!

Added MIT license :)

Thank you!


Shadow robot kinetic distro

I'd like to add the Shadow Robot repos to be indexed and coumented on ros.org

Hi @georgiablanco it looks like these repositories were added to Kinetic in #26918 and the commits later applied to this PR are removing the source entries. Is that intended or can this PR be closed?

Yes I have removed the source on purpose.

We are holding Kinetic releases in preparation for a sync. While this is not a release in the interest of keeping the distribution stable during the sync window I'm going to wait to merge this until the sync is out.

Sync is out


Actions in Handler

Hello!
Please tell me, if I create a button with the OpenFile action, then it can only be activated from Handler.
Is it possible to make an action from other controllers?

If this is not in the telegraph, then maybe someone solved it temporarily...

@Freshblood1121 you can start handling it in your webhook handler and then call the controller from it
I'm not sure exposing the controller name is a good idea here

I can't see the code, but I guess this could be optimized
anyway in V2 I'm planning to add a router for telegraph to handle such cases


How do I hide the margin of an edge GridItem

As shown

I want the GridItem to sit close to the GridLayout

May I ask how you solved this problem


Repo sync for protected CLA branch

The pull request is created from master637674265744999955 to master to fix git push error for protected CLA branch

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


Sim_control not working

Hello team, sorry to bother you. I have encounterd a problem and I could really use your help. Thanks a lot!
System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04): Ubuntu 20.04 LTS
Apollo installed from (source or binary):
Apollo version (3.5, 5.0, 5.5, 6.0): 6.0
Output of apollo.sh config if on master branch: master branch

Steps to reproduce the issue:

building Apollo, enable DreamView
start DreamView, select cars, modes, map
enable sim_control
send routing request

After I send the routing request, the car is freezing and nothing happens. The console shows that Planning triggers safe mode. Here is the screenshot:

I checked the cyber_monitor, here is the info:

I also looked into the log, and here is the DreamView Log:

Supporting materials (screenshots, command lines, code/script snippets):
What should I do? DO I have to reinstall Apollo?

I noticed the planning module not work working properly, which outputs message:
F0112 19:41:34.817965 483466 planning_component.cc:50] Check failed: ComponentBase::GetProtoConfig(&config_) failed to load planning config file /apollo/modules/planning/conf/planning_config.pb.txt

I also have a question: do I have to use the cyber_recorder to replay the bag before using sim_control?

I also have a question: do I have to use the cyber_recorder to replay the bag before using sim_control?

delete the file /apollo/modules/planning/conf/planning_config.pb.txt and try again.
There are 2 ways to initialize sim_control.

The initial position of the vehicle without any operation
Use "localization_reader_" to get an initial point

delete the file /apollo/modules/planning/conf/planning_config.pb.txt and try again.
There are 2 ways to initialize sim_control.

The initial position of the vehicle without any operation
Use "localization_reader_" to get an initial point

Thank you @daohu527 . I have solved the problem by reinstalling the Apollo master branch. I guess it is because I have made some modification to the code before that I don't remember now.
Although now the planning module works fine, when I enable the sim_control and corresponding modules, then giving the routing command, the route can be formed but the car does not move at all. Is that because I haven't played the record file at the same time? Do I have to play a record file when using sim_control?

Thank you @daohu527 . I have solved the problem by reinstalling the Apollo master branch. I guess it is because I have made some modification to the code before that I don't remember now.
Although now the planning module works fine, when I enable the sim_control and corresponding modules, then giving the routing command, the route can be formed but the car does not move at all. Is that because I haven't played the record file at the same time? Do I have to play a record file when using sim_control?

Seems PerceptionObstacle topic is missing? You need to check the log and observe

Seems PerceptionObstacle topic is missing? You need to check the log and observe

I have not played any record data or add obstacles, so there are no obstacles. I just click sim_control and enable planning, prediction, perception and routing modules. Is that the reason?

I have not played any record data or add obstacles, so there are no obstacles. I just click sim_control and enable planning, prediction, perception and routing modules. Is that the reason?

you should just enable routing, planning and sim_control.
sim_control will publish the mock PerceptionObstacle topic.

you should just enable routing, planning and sim_control.
sim_control will publish the mock PerceptionObstacle topic.

Thank you for your reply. I have tried your way, and here is the output (the car still not move):

And here are the logs of planning module, and routing module:

Here is the log of mainboard:

Here is the log of DreamView:

Can you take a look for me? Really thanks!

Thank you for your reply. I have tried your way, and here is the output (the car still not move):

And here are the logs of planning module, and routing module:

Here is the log of mainboard:

Here is the log of DreamView:

Can you take a look for me? Really thanks!

when I play the record file (e.g. Demo_3.5.record) , the planning module works. but after playing the record file, the planning module does not work and say no message comes, even though I have give a route

when I play the record file (e.g. Demo_3.5.record) , the planning module works. but after playing the record file, the planning module does not work and say no message comes, even though I have give a route

You error message is "Failed to create reference line from routing". If the code has not been modified, I think there is a problem with the map or routing message sent
Planning module's input are localization, perception, and chassis. it's output is a "ADC Trajectory". sim_control will provide the above information to the planning module.
You cannot enable sim_control and play record at the same time, I suggest you find the simplest map first like single lane map

You error message is "Failed to create reference line from routing". If the code has not been modified, I think there is a problem with the map or routing message sent
Planning module's input are localization, perception, and chassis. it's output is a "ADC Trajectory". sim_control will provide the above information to the planning module.
You cannot enable sim_control and play record at the same time, I suggest you find the simplest map first like single lane map

Thank you for your answer. Do you mean using the file map_gen_sin_lane.py  under modules/tools/map_gen?

Thank you for your answer. Do you mean using the file map_gen_sin_lane.py  under modules/tools/map_gen?

You can download map from https://content.lgsvlsimulator.com/maps/singlelaneroad/

You can download map from https://content.lgsvlsimulator.com/maps/singlelaneroad/

Hi, I have tried the single lane road. The car does not move and the planning module says: "Failed to update reference line after rerouting". the log of mainboard sais "detect froward jumps in time"

Hi, I have tried the single lane road. The car does not move and the planning module says: "Failed to update reference line after rerouting". the log of mainboard sais "detect froward jumps in time"

@GabrielZZZ Hello, you could use r6.0.0 instead of master branch. It works for me.

@GabrielZZZ Hello, you could use r6.0.0 instead of master branch. It works for me.

@GabrielZZZ
Is the master branch working now?

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


"Value does not fall within the expected range"

Hi, so I'm trying to deploy it with my onnx file on the hololens 2 but after I implement and open in hololens, Status blocked: "Value does not fall within the expected range" shows up and nothing happenes... do you know how to fix this problem? The only thing I made changed is just adding my onnx file to the asset folder.

Hi, so I'm trying to deploy it with my onnx file on the hololens 2 but after I implement and open in hololens, Status blocked: "Value does not fall within the expected range" shows up and nothing happenes... do you know how to fix this problem? The only thing I made changed is just adding my onnx file to the asset folder.

Hi
Could you please help me out with the set up
I was not able to see the scripts in my visual or Unity


Example code 5.2.1 idf - heap_task_tracking example: main task name gets corrupted and longer as time goes on. (IDFGH-12942)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
"main" task name gets corrupted and longer as time goes on. I see the above issue when I run the heap_task_tracking example project. Is this a risk ? CAP_32BIT returns 0 always, Any suggestions? Thanks all
Task: Pre-Scheduler allocs -> CAP_8BIT: 3068 CAP_32BIT: 20
Task: ipc0 -> CAP_8BIT: 9584 CAP_32BIT: 0
Task: main -> CAP_8BIT: 3648 CAP_32BIT: 0
Task: ipc1 -> CAP_8BIT: 16 CAP_32BIT: 0
Task: example_task -> CAP_8BIT: 220 CAP_32BIT: 0
Task: Pre-Scheduler allocs -> CAP_8BIT: 3068 CAP_32BIT: 20
Task: ipc0 -> CAP_8BIT: 9584 CAP_32BIT: 0
Task: ���? -> CAP_8BIT: 3648 CAP_32BIT: 0
Task: ipc1 -> CAP_8BIT: 16 CAP_32BIT: 0
Task: example_task -> CAP_8BIT: 40 CAP_32BIT: 0

Hi! On the master it works fine. There was an issue #13467 that was fixed recently. This fix is already in v5.2.2.

CAP_32BIT returns 0 always

Seems it is correct behavior. @SoucheSouche Could you check this? Thanks.

what is the git difference to the Release/v5.2 to the v5.2.2 it was not supose to have all commits to the same?

what is the git difference to the Release/v5.2 to the v5.2.2 it was not supose to have all commits to the same?

There is a doc that describes IDF release branches - https://docs.espressif.com/projects/esp-idf/en/stable/esp32/versions.html#checking-the-current-version.
Yes, for sure, you can use the release/v5.2 branch, it includes changes v5.2.2.
(release/v5.2 branch includes more commits than v5.2.2, the new commits will go to the next release v5.2.3 in the feature).

@SCgenie

CAP_32BIT returns 0 always

Yes, it is the correct output. The freertos allocates the stack for tasks with the following caps:
#define FREERTOS_SMP_MALLOC_CAPS    (MALLOC_CAP_INTERNAL|MALLOC_CAP_8BIT).
See the difference CAP_8BIT and CAP_32BIT -> https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/mem_alloc.html?highlight=cap_32bit#bit-accessible-memory

Hi @SCgenie,
I will close the ticket since it seems that your concern was answered. Fill free to reopen if you have any other questions related to your problem.


Submission for coding challange

https://people.sap.com/mozhgan.ghasemzadeh

Thanks a lot for your contribution. The solution looks great and I'll close this PR now!
You should receive your badge soon.


ADD ARRAY ELEMENTS

Description to problem is added.

Description added.

Changes have been made. Please check.


Change default handoffConditionTimeout to 15 minutes.

Most of the time, when handoff is taking this long, it's because something is preventing Historicals from loading new data. In this case, we have two choices:

Stop making progress on ingestion, wait for Historicals to load stuff,
and keep the waiting-for-handoff segments available on realtime tasks.
(handoffConditionTimeout = 0, the current default)

Continue making progress on ingestion, by exiting the realtime tasks
that were waiting for handoff. Once the Historicals get their act
together, the segments will be loaded, as they are still there on
deep storage. They will just not be continuously available.
(handoffConditionTimeout > 0)

I believe most users would prefer [2], because [1] risks ingestion falling behind the stream, which causes many other problems. It can cause data loss if the stream ages-out data before we have a chance to ingest it.
Due to the way tuningConfigs are serialized -- defaults are baked into the serialized form that is written to the database -- this default change will not change anyone's existing supervisors. It will take effect for newly created supervisors.

Thinking a bit about this change and discussing it with @kfaraz, it probably is ok to make this change. Initially, I was worried about this leading to holes in the data and recovery. But since it's only the hand-off, those holes will be temporary since the segment has been created.


overflow and position issues in comments popup

Fixed the overflow issue
Fixed the position issue in mobile devices

Thanks for the quick fixes


replaced renderer with path tracer class to be passed into a window

placed renderer object with path tracer object to pass to the window for populating the pixel buffer.
I had to rearrange the points of the rectangle class to correctly display the rendered image. Originally the image was inverted (-1 pointed up)

Codecov Report

Merging #37 (4c06321) into main (67cf7bb) will decrease coverage by 0.68%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #37      +/-   ##
==========================================
- Coverage   40.98%   40.30%   -0.69%
==========================================
  Files          29       31       +2
  Lines         649      660      +11
==========================================
  Hits          266      266
- Misses        383      394      +11

Impacted Files
Coverage Δ

src/main/main.cpp
0.00% <0.00%> (ø)

src/renderer/pathTracer.cpp
0.00% <0.00%> (ø)

src/renderer/pathTracer.h
0.00% <0.00%> (ø)

src/renderer/rectangle.cpp
0.00% <0.00%> (ø)

src/window/glfwWindow.cpp
0.00% <0.00%> (ø)

src/window/window.cpp
0.00% <0.00%> (ø)

src/raycast/camera.h
0.00% <0.00%> (ø)

src/scene/scene.h
0.00% <0.00%> (ø)

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 67cf7bb...4c06321. Read the comment docs.


⚠ Bofrost.at has degraded performance

In ee0bbaf, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1186 ms

Resolved: Bofrost.at performance has improved in 43cc0e3 after 20 minutes.


Bump tokio from 0.2.11 to 0.3

This PR shall update tokio to version 0.3.
Changes

adapt AsyncRead, AsyncWrite implementations
rename delay_for -> sleep, Delay -> Sleep
...

Fixes #2302

There are still quite some errors left to resolve, so I am happy to get some input there 😃

Thanks for this! I had also started a branch just yesterday doing this, which was useful to find all the things that aren't easily fixable in hyper, and started trying to put them back into Tokio. The biggest one is vectored writes, but there's a few smaller things too. I'll list them in the original issue.

@seanmonstar: Thanks for this! I had also started a branch just yesterday doing this, which was useful to find all the things that aren't easily fixable in hyper, and started trying to put them back into Tokio. The biggest one is vectored writes, but there's a few smaller things too. I'll list them in the original issue.

Sounds like a good plan 😁

Thanks for starting this! Eliza did most of the rest in #2317, and the one last tweak was finished in #2319.


Some basic benchmarks

These should serve as a baseline against which we can asses changes in the future. They all focus on StartActivity() and Complete()/Dispose(), which right now seem likely to have the most prominent performance considerations.
There are four sets of benchmarks. In each, the Complete() variant is similar to the Dispose() one, but sets a level and exception.
Leveled off
This one covers the common case of a span being suppressed by the level set on the target logger. The major costs will probably be around interface dispatch and the minimum level comparison. The ActivitySource version is only roughly comparable, since activity sources don't apply any level-like concept:
BenchmarkDotNet v0.13.12, macOS Sonoma 14.2.1 (23C71) [Darwin 23.2.0]
Apple M3 Pro, 1 CPU, 11 logical and 11 physical cores
.NET SDK 8.0.201
  [Host]     : .NET 8.0.2 (<IP_ADDRESS>11), Arm64 RyuJIT AdvSIMD
  DefaultJob : .NET 8.0.2 (<IP_ADDRESS>11), Arm64 RyuJIT AdvSIMD

Method
Mean
Error
StdDev
Ratio
RatioSD
Allocated
Alloc Ratio

ActivitySourceBaseline
20.363 ns
1.8095 ns
5.2785 ns
1.00
0.00
-
NA

StartThenDispose
1.590 ns
0.0009 ns
0.0007 ns
0.10
0.04
-
NA

StartThenComplete
1.856 ns
0.0007 ns
0.0007 ns
0.11
0.04
-
NA

The baseline here seems to be much slower on my MBP than Linux desktop; will need to do some investigation but don't think it's blocking right now.

Leveled on, tracing not configured
This usage is SerilogTracing in the simplified, local, SerilogTimings-like mode: the logging pipeline is used, but no activity listener is set up and so the spans are associated with new Activity() instances. This will be relevant for people migrating directly from SerilogTimings without (initially) enabling any additional tracing functionality.

Method
Mean
Error
StdDev
Gen0
Gen1
Allocated

StartThenDispose
280.7 ns
0.57 ns
0.50 ns
0.1488
-
1.22 KB

StartThenComplete
620.0 ns
0.48 ns
0.37 ns
0.2489
0.0010
2.04 KB

Sampled off
This usage covers fully-configured SerilogTracing with System.Diagnostics.Activity integration, but where sampling suppresses the intended span.

Method
Mean
Error
StdDev
Gen0
Allocated

StartThenDispose
55.51 ns
0.218 ns
0.193 ns
0.0162
136 B

StartThenComplete
56.03 ns
0.205 ns
0.181 ns
0.0162
136 B

Tracing on
Finally, the fully-configured, fully-enabled version. The baseline is for a recorded Activity that reaches an ActivityListener that does nothing. The ActivityListenerOnly case covers external activities generated outside SerilogTracing but recorded through its listener.

Method
Mean
Error
StdDev
Ratio
Gen0
Gen1
Allocated
Alloc Ratio

A...SourceBaseline
142.8 ns
0.33 ns
0.31 ns
1.00
0.0496
-
416 B
1.00

A...ListenerOnly
353.3 ns
3.14 ns
2.94 ns
2.47
0.1564
0.0005
1312 B
3.15

S...Dispose
340.7 ns
0.79 ns
0.74 ns
2.39
0.1488
-
1248 B
3.00

S...Complete
677.9 ns
1.54 ns
1.36 ns
4.75
0.2489
0.0010
2088 B
5.02

Trimmed out some detail her to try to squeeze the table in without wrapping.

I've updated the benchmarks and re-run. I've also added an ignoreLevelChanges flag which cuts 140 B allocation from all of the TracingOn configurations; there's still some unscientific overhead spread across all of the cases in that set - it would be worth splitting this up a bit in a future revision.


Compare candidate policies and views

Not sure this is a job for the federal government. More a job for the free press, right?


Zone.js does not work with Zombie/jsdom

I'm trying to get an Angular2 app running in Zombie, and seeing the following error (presumably from jsdom):
TypeError: Cannot redefine property: onclick
at Function.defineProperty (native)
at canPatchViaPropertyDescriptor (http://localhost:8080/app.js:35698:12)
at Object.apply (http://localhost:8080/app.js:35677:9)
at Object.apply (http://localhost:8080/app.js:35288:29)
at http://localhost:8080/app.js:35165:16
at linkDynamicModule (http://localhost:8080/app.js:262:32)
at getModule (http://localhost:8080/app.js:231:9)
at http://localhost:8080/app.js:266:16
at http://localhost:8080/app.js:35147:20
at linkDynamicModule (http://localhost:8080/app.js:262:32)
in http://localhost:8080/
ORIGINALY FILED AS: https://github.com/angular/angular/issues/3584

/cc @danhalliday

Looks like we need to wrap that check in a try/catch for environments that make that property non-configurable.

I might be able to spend some time looking at a PR, as it'd be really cool to try out Zombie with Angular 2. When you say try/catch it, do you mean just fail more gracefully, or do you think it would be possible for Zone to work without redefining onclick?

What's strange is that looking at the code, it seems Zone already handles non-configurable properties (here: https://github.com/angular/zone.js/blob/f8a2be5ab889b3026774ea36cea4e385399a52df/lib/patch/property-descriptor.js#L36 it looks like patchViaCapturingAllTheEvents() should be called).

I've debugged my app code and tracked down the actual stack trace for the error:
Object.defineProperty(obj, prop, desc); (https://github.com/angular/zone.js/blob/master/lib/utils.js#L73)
patchProperty(obj, eventName); (https://github.com/angular/zone.js/blob/master/lib/utils.js#L88)
utils.patchProperties(HTMLElement.prototype, onEventNames); (https://github.com/angular/zone.js/blob/master/lib/patch/property-descriptor.js#L21)
propertyDescriptorPatch.apply(); (https://github.com/angular/zone.js/blob/master/lib/patch/browser.js#L34)
browserPatch.apply(); (https://github.com/angular/zone.js/blob/master/lib/browser/zone.js#L13)

Turns out canPatchViaPropertyDescriptor() returns true.

I was getting this error when trying to run Angular2 with<EMAIL_ADDRESS> However after upgrading to<EMAIL_ADDRESS>and the latest version of Angular2 and it's dependencies I no longer get this error and I'm able to run Angular2 in jsdom.

@natewallace does this still work for you<EMAIL_ADDRESS>is throwing this issue for me still with angular2

@bvkimball Yes, it still works for me with<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>

With<EMAIL_ADDRESS>and<EMAIL_ADDRESS><EMAIL_ADDRESS>fails for me.

Is there any momentum on this<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>fails when running tests via jest and I'd like to avoid rewriting my existing suite if at all possible

Would love to have A PR for this.

I tried to write a patch for jsdom some times ago and it could work but I don't have the skills to make  a real PR of it: https://github.com/tmpvar/jsdom/pull/1610

Is there a repo to reproduce? I run the angular2 in zombie simply get a error 'TypeError: Parameter "url" must be a string, not object'


Synchronize loading / generation of bitmap

I am using FFImageLoading in my mvx project. It works great when loading recyclerview. I have an issue when I tried to create downsample bitmaps from a bunch of local files. The bitmap is required immediately to proceed for map marker generation.
Not sure if I misunderstood something, I found image is not available after the return of both statements:

ImageService.Instance.LoadFile(xxx).DownSample(width: xxx).Into(imageViewAsync)
await ImageService.Instance.LoadFile(xxx).DownSample(width: xxx).IntoAsync(imageViewAsync)

The only time that I can use imageViewAsync is after the trigger of .Finish(xxx). However, it is trigger only after the UI thread is free, i.e. after the execution of my current code completes. In that case, I have trouble when I need to load for a consecutive number of times. I spent days to find a workaround with no luck.
Similar to an old issue #59, I need a solution to generate a bitmap synchronizely with dowmsample feature. I guess the solution there was a bit out dated that I am not able to implement. Is there any solution that I can implement with the current version?
Thank you very much for the great work.

Currently, you should use:

await ImageService.Instance.LoadFile(xxx).DownSample(width: xxx).AsBitmapDrawableAsync() for Android
await ImageService.Instance.LoadFile(xxx).DownSample(width: xxx).AsUIImageAsync() for iOS
await ImageService.Instance.LoadFile(xxx).DownSample(width: xxx).AsBitmapDrawableAsync() for Windows (yeah I noticed bad naming, we should change it in future)

Perfect. Thank you very much.


[Feature] - Support react-native versions lower of 0.73

feature requested in https://github.com/facebook/react-native/issues/15114#issuecomment-1908137889, requires:

creating new branches for 0.70, 0.71, 0.72
test ios and android
(OPTIONAL) reimplement private APIs
patch react-native-renderer for 0.70, 0.71, 0.72
release to npm from 0.70, 0.71, 0.72 branch

not planned and not completed


Fixed #5470 -- Page admin's views' incorrect selection of available languages

Now get languages from site-specific cms admin site rather than the
current site if the obj doesn't exist in the view.
Getting the language from the request now gets available languages from
cms_admin_site in request.session if current_page is not present. If the
language is not in that set, use the first available from the set.

This is the properly-based and formatted PR, originally #5539.

LGTM

@nolsto Don't forget to add a changelog entry: http://docs.django-cms.org/en/release-3.3.x/contributing/development-policies.html#changelog

@nolsto closing this for now. If still relevant please reopen against develop branch :)
Thank you very much.


Use main branch instead of master

About 1.5 years ago, we deprecated the master branch in favour of the main branch. We intend to remove it soon, likely by May 1st 2023.

Thanks @kbdharun @pixelcmtd and apologies for the delay. I've merged the PR and hope to publish a new release soon.


Devtool development flow isn't working for greengrass-bin (dunfell-next)

Hello
I am trying to use devtool to modify the greengrass-bin recipe but the devtool build greengrass-bin step fails with the following error install: cannot stat '/image/build/tmp/work/armv7vet2hf-neon-poky-linux-gnueabi/greengrass-bin/2.9.4-r0/LICENSE': No such file or directory   .  Running bitbake greengrass-bin builds the recipe without an issue.
Steps to reproduce:

Create a dunfell build environment
source poky/oe-init-build-env
devtool modify greengrass-bin
devtool build  greengrass-bin
->  this fails with install: cannot stat 'image/build/tmp/work/armv7vet2hf-neon-poky-linux-gnueabi/greengrass-bin/2.9.4-r0/LICENSE': No such file or directory

I could solve it with this patch.
Using  ${S} is also what the poky binary installation helper class uses bin_package.bbclass.
Bootlin has an interesting slide in their yocto training material about the different variable names

Thank you! Will fix this today.


Callbacks for progress tracking

If parameter tuning is not being used, evaluation metric is not printed.
Would you consider adding events/callbacks so that custom functions can be called for progress logging / inspecting / interrupting on condition?
Thanks for sharing your work @cerlymarco!

Hi,
thanks for the feedback. You should use verbose >1 to print feature selection logs.
If you support the project, don't forget to leave a star ;-)
All the best


gitpod nextflow version too low for demo workflow

Description of the bug
Summary
The nextflow version in the gitpod is too low for the demo workflow. I used the Gitpod environment as described in the nf-core/demo tutorial
nf-customize -> nextflow run nf-core/demo -profile test --outdir results
Nextflow 24.09.2-edge is available - Please consider updating your version to it

 N E X T F L O W   ~  version 24.02.0-edge

 ┃ Launching `https://github.com/nf-core/demo` [high_brenner] DSL2 - revision: 04060b4644 [master]

Downloading plugin<EMAIL_ADDRESS>Nextflow version 24.02.0-edge does not match workflow required version: >=24.04.2

I tried to update nextflow, but to no avail:
nf-customize -> nextflow self-update

      N E X T F L O W
      version 24.09.2-edge build 5927
      created 14-10-2024 21:22 UTC
      cite doi:10.1038/nbt.3820
      http://nextflow.io

Nextflow installation completed. Please note:
- the executable file `nextflow` has been created in the folder: /opt/conda/bin

nf-customize -> nextflow info
  Version: 24.02.0-edge build 5907
  Created: 10-03-2024 19:56 UTC
  System: Linux 6.1.91-060191-generic
  Runtime: Groovy 4.0.19 on OpenJDK 64-Bit Server VM 17.0.13-internal+0-adhoc..src
  Encoding: UTF-8 (UTF-8)

Is there another way to update nextflow on gitpod?
Command used and terminal output
nf-customize -> nextflow run nf-core/demo -profile test --outdir results
Nextflow 24.09.2-edge is available - Please consider updating your version to it
N E X T F L O W   ~  version 24.02.0-edge
┃ Launching https://github.com/nf-core/demo [high_brenner] DSL2 - revision: 04060b4644 [master]
Downloading plugin<EMAIL_ADDRESS>Nextflow version 24.02.0-edge does not match workflow required version: >=24.04.2
nf-customize -> nextflow self-update
  N E X T F L O W
  version 24.09.2-edge build 5927
  created 14-10-2024 21:22 UTC
  cite doi:10.1038/nbt.3820
  http://nextflow.io

Nextflow installation completed. Please note:

the executable file nextflow has been created in the folder: /opt/conda/bin

nf-customize -> nextflow info
Version: 24.02.0-edge build 5907
Created: 10-03-2024 19:56 UTC
System: Linux 6.1.91-060191-generic
Runtime: Groovy 4.0.19 on OpenJDK 64-Bit Server VM 17.0.13-internal+0-adhoc..src
Encoding: UTF-8 (UTF-8)
Relevant files
No response
System information
I used the Gitpod environment as described in the nf-core/demo tutorial

Thanks Felix. I found the same thing. I'll get a PR in to reduce.


update to support netstandard

fixes https://github.com/dbelmont/ExpressionBuilder/issues/27

bump :)

assuming this repo is dead. so will close this

So are there no plans to support .NET Standard / Core?


Update alluxio python client on pypi.org,

Hi.
What about updating alluxio python client on pypi.org, may be with version 0.1.2? It seems last commit
https://github.com/Alluxio/alluxio-py/commit/00137ad71ac2638e227e5e43200e84ba068982aa (Be compatible with Python3) is not included in module distribution.

@LuQQiu  can you check if cherrypicking the commit helps? thanks


plz!! help!!!!!

ERROR: Requirements have not been satisfied properly. Please look at the README file for configuration instructions.
If you still cannot resolve this error, please submit an issue here:
https://github.com/k4m4/kickthemout/issues
Details: No module named 'scapy'
How can I fix this problem?
also I did "pip install -r requirements.txt"!!
I want to install "kickthemout" in kali linux 2017.2.

Hi there @classer12271227. It seems that you haven't followed the correct installation steps. Please refer to the readme file for the appropriate instructions. If you still don't manage to resolve your problem, please re-open this issue. The installation process has been updated. Thanks!


Remove libnx as a dependency

To remove libnx as a dependency, you would have to write your own NSO generator, so there's that. then you have to re-implement some of the SVC syscalls (which isn't hard), so shrug

@Thog was able to remove it as a dependency, but their solution had other problems and had to be reverted. Hopefully they can fix it.

Why do we want to remove libnx?

@3096 libnx isn't design to be working as a subsdk and not any libnx's APIs are currently used by the project. As such, libnx takes some extra KB for nothing and force us to patch it to make it work on an dynamic environment.

Libnx is still linked against in the MakefileNSO, but AFAIK it's not necessary anymore? What's the status here?


[3.2] Properly hide GraphEdit's minimap

A backport of #46563. Fixes #46556 for 3.2.

Thanks!

For the reference: https://github.com/godotengine/godot/issues/53831


Fix: #120. Add NDC profile.

This PR
adds the NDC profile contributed by @giorgialodi
Fixes #120

@ioggstream dovrebbe essere ok

@ioggstream @ronytw revised the file of this pull request. See third commit.

minor typos

Sort languages. Add "for semantic interoperability".


static virtual polymorphism

Create a pattern that allows drivers to choose between runtime polymorphism and static polymorphism. Static is not runtime switchable and makes the code less dynamic, but it improves runtime performance at the cost of additional space needed.

The code example here demonstrates how to do this pretty easily. https://godbolt.org/z/7EEEGhn1E
Simply put, the scheme for this is as follows:
struct interface {};
struct implementation {};

// Default set the T to the interfaces so the app developer does not have to supply this themselves
template<class T = interface>
struct driver {
  // Make the constructor templated in order to separate the types between the class and the constructor.
  // Otherwise if T was used here, then the class T would be forced to whatever the input type is.
  template<class U>
  driver(U& p_impl) : m_impl(&p_impl) {}
  T* m_impl;
};

Future iterations should use std::derived_from<B, B> concept or type-traits std::is_base_of utility to determine that the template T and U have an actual relationship to each other, and if they do not, then we output a useful message.


Unable to resolve SQL server hostname in connection string

I am unable to connect to a SQL instance on a microsoft/mssql-server-windows-developer container from a microsoft/aspnet container.
From the aspnet container I can ping the sql server hostname successfully but if the connection string contains the hostname it returns the error:
"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)".
If an IP is used it works successfully.
I have been able to re-create the issue using the following powershell:
$db_hostname ="dbhost"
$sapassword="DockerTest1!"

docker run -d --name sqlcontainer -h $db_hostname -e ACCEPT_EULA=Y -e sa_password=$sapassword -p 1433:1433 microsoft/mssql-server-windows-developer
docker run -d --name sqlexpresscontainer -h expresshost -e ACCEPT_EULA=Y -e sa_password=$sapassword -p 1434:1433 microsoft/mssql-server-windows-express
docker run -d --name aspcontainer -h asphost microsoft/aspnet

$sqlhealth = ""
while ( $sqlhealth -ne "healthy" )
{
    Write-Host "waiting for SQL to be healthy"
    Start-Sleep 2
    $sqlhealth = Invoke-Expression "docker inspect -f='{{.State.Health.Status}}' sqlcontainer"
}

$psTestcmd = @"
hostname;
ping $db_hostname;
`$SqlConnection = New-Object System.Data.SqlClient.SqlConnection;
`$SqlConnection.ConnectionString = \"Server = $db_hostname; User ID = sa; Password = $sapassword;\";
`$SqlCmd = New-Object System.Data.SqlClient.SqlCommand;
`$SqlCmd.CommandText = \"SELECT 'Connection to SQL Server successfull'\";
`$SqlCmd.Connection = `$SqlConnection;
`$SqlAdapter = New-Object System.Data.SqlClient.SqlDataAdapter;
`$SqlAdapter.SelectCommand = `$SqlCmd;
`$DataSet = New-Object System.Data.DataSet;
`$SqlAdapter.Fill(`$DataSet);
"@

docker exec sqlcontainer powershell -command "$psTestcmd"
docker exec sqlexpresscontainer powershell -command "$psTestcmd"
docker exec aspcontainer powershell -command "$psTestcmd"

The SQL containers are able to resolve the DNS addresses but the ASP container cannot even though it can ping the DNS hostname.
It seems to be similar to this issues https://github.com/moby/moby/issues/31093 but I have check the reg values and all containers are set to 0.

 Could you please check if this works just to eliminate other possibilities .
Ex -
docker run -d --name sqlcontainer -h $db_hostname -e  ConnString= 'Data Source=$server;Initial Catalog=.;User ID=sa;Password=password '  -p 1433:1433 microsoft/mssql-server-windows-developer

Do you have a choice to simply pass the connection string directly ? Could you please check if this works just to eliminate other possibilities .
Ex -
docker run -d --name sqlcontainer   -e ConnString= 'Data Source=$server;Initial Catalog=.;User ID=sa;Password=password ' -p 1433:1433 microsoft/mssql-server-windows-developer