Creating application security checklist

Creating an application security checklist.
Issue
https://github.com/kubernetes/sig-security/issues/111
Deploy Preview
https://deploy-preview-46326--kubernetes-io-main-staging.netlify.app/docs/concepts/security/application-security-checklist/

/remove-area blog localization web-development release-eng

/remove-language bn
/remove-language de
/remove-language es
/remove-language fr
/remove-language hi
/remove-language id
/remove-language it
/remove-language ja
/remove-language ko
/remove-language pl
/remove-language pt
/remove-language ru
/remove-language uk
/remove-language vi
/remove-language zh

/remove-sig release
/sig security

This looks good :)! I think it's a very valuable checklist for app developers.

First of all, great job, I think this document is a great addition.
But here are my thoughts. First, my question is, for whom is this document written for? Is it the 85-90% of app developers that run an http API or an event based app in a non-critical environment that just wants a good base layer? Or are we trying to point to all security features that exist from an app developer point of view?
Personally, I think we should aim this document mainly towards the 85-90% of the users. Especially since there is a tendency to want to be able to complete everything on a checklist, but if it becomes too painful, you end up doing nothing. See keep it relatively simple and provide some kind of leveling system.
I would add a header called ## base security. In there I would add the most basic stuff.
Then I would add another header, ## advanced security, or something like that.
I would keep everything you have written, but I would move these down to advanced security

rbac, if you are using rbac in your http api, you are most likely doing something wrong. I would emphasize that really hard in the document.
runtime class, custom runetime classes isn't something that the majority of Kubenetes environment will use.
Seccomp profiles, It's more or less impossible to setup unless you have some kind of tooling + since version 1.25 the default profile is enabled by default.
SElinux, most developers don't know what it is and just like secomp profile you more or less need tooling to create something decent.
AppArmor, even fewer people know what it is, and you need custom tooling to create something more advanced than default.

Thanks for the detailed response. I like this format and I will try to update the document accordingly.
Regarding the target audience I did add this point

This checklist assumes a developer is a Kubernetes cluster user that interacts with namespaced scope objects.
https://github.com/kubernetes/website/pull/46326/files#diff-5285725b7ae5cc6b415f12dbb2acf91aea311bf5dd5dc71851b29c216afcb9adR20

I did realize that identifying the target audience is key here and then keeping the list generic so that it can be used by everyone. Because app developers can consist of tools that be running cluster wide like log and metric collectors or policy agents. This is where the line between admins and developers start to blur. I'll try to add more details about the target audience for this list.

@NissesSenap I have updated the checklist structure based on your recommendation.
Can you expand on

rbac, if you are using rbac in your http api, you are most likely doing something wrong. I would emphasize that really hard in the document.

I'm not sure what you mean here.

@NissesSenap I have updated the checklist structure based on your recommendation.
Can you expand on

rbac, if you are using rbac in your http api, you are most likely doing something wrong. I would emphasize that really hard in the document.

I'm not sure what you mean here.

That is great @AnshumanTripathi , I will try to take a deeper look at the update as soon as possible. My point is that the majority of all apps ruining in Kubernetes don't need access to its API. So I would emphasize that custom rbac rules for apps just aren't needed, in the majority of applications. Still good to talk about it, just like you have, but point to that there are limited use cases for it.

@NissesSenap I have updated the checklist structure based on your recommendation.
Can you expand on

rbac, if you are using rbac in your http api, you are most likely doing something wrong. I would emphasize that really hard in the document.

I'm not sure what you mean here.

That is great @AnshumanTripathi , I will try to take a deeper look at the update as soon as possible. My point is that the majority of all apps ruining in Kubernetes don't need access to its API. So I would emphasize that custom rbac rules for apps just aren't needed, in the majority of applications. Still good to talk about it, just like you have, but point to that there are limited use cases for it.

Makes sense. I am not covering applications using Kubernetes client as a part of this checklist. I think having a doc about secure practices for applications that use the Kubernetes API (and operator) can be very helpful. I will create an issue for this :)

@NissesSenap created https://github.com/kubernetes/sig-security/issues/121 for hardening guide for using Kubernetes API

I'd suggest we place this under content/en/docs/reference/security/, a new directory for consolidating security related contents. This page is not suitable for the concepts section.

I'd suggest we place this under content/en/docs/reference/security/, a new directory for consolidating security related contents. This page is not suitable for the concepts section.

Actually in that case we can move the hardening guides to content/en/docs/reference/issues-security which already exists. It makes sense. I can move the existing hardening guide an this guide under that section. But I dont think I should do that as a part of this change though?

I'd suggest we place this under content/en/docs/reference/security/, a new directory for consolidating security related contents. This page is not suitable for the concepts section.

Actually we can move this checklist and the existing checklist to content/en/docs/reference/issues-security maybe? I dont think I should do that as a part of this change though.

I'd suggest we place this under content/en/docs/reference/security/, a new directory for consolidating security related contents. This page is not suitable for the concepts section.

Actually we can move this checklist and the existing checklist to content/en/docs/reference/issues-security maybe? I dont think I should do that as a part of this change though.

The issues-security directory is positioned to be a folder for disclosing the vulnerabilities of kubernetes release. What we are trying to compile is a collection of guidelines, best practices for users.
I don't think we want to kick this in and then follow up with another PR to move it.
We may want to get the page into a suitable folder in the first place.
The migration of other relevant pages could be left as follow-ups, for sure.

I'd suggest we place this under content/en/docs/reference/security/, a new directory for consolidating security related contents. This page is not suitable for the concepts section.

Actually we can move this checklist and the existing checklist to content/en/docs/reference/issues-security maybe? I dont think I should do that as a part of this change though.

The issues-security directory is positioned to be a folder for disclosing the vulnerabilities of kubernetes release. What we are trying to compile is a collection of guidelines, best practices for users.
I don't think we want to kick this in and then follow up with another PR to move it. We may want to get the page into a suitable folder in the first place. The migration of other relevant pages could be left as follow-ups, for sure.

Makes sense. I'll try to make that change

This page, in its current format, with its current contents, doesn't belong to the concepts section. Please consider place it under the references section.

I think this proposed "application security checklist" aligns with the live "security checklist" page which is aimed towards operators/cluster admins.
Since the "security checklist" page is currently under concepts, I'm ok to merge the "application security checklist" since under concepts
If we decide references is a better place then a PR can be made to move both of the "checklists" and possibly more like the
Authentication Mechanism Hardening Guide
/approve

/lgtm


DEV-14576 Add ability to configure bootstrap actions for EMR nodes.

https://datatamr.atlassian.net/browse/DEV-14576

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


Resolver warnings in Test::Nginx tests

I'm getting warnings like nginx: [warn] conflicting server name "_" on <IP_ADDRESS>:1984, ignored.
I see that the builds on Travis show the same kind of errors. This started happening recently.

That is because of Test::APIcast upgrade that makes metrics to listen on the same port as apicast. Not sure how to solve it.


fix: need to add in cash out codes for currency transaction activity …

Cash out codes are missing for currency transaction activity detail type

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (adb21d0) 73.79% compared to head (c013fe1) 73.74%.

:exclamation: Current head c013fe1 differs from pull request most recent head 006873a. Consider uploading reports for the commit 006873a to get more accurate results

Files
Patch %
Lines

pkg/currency_transaction/primitive.go
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #87      +/-   ##
==========================================
- Coverage   73.79%   73.74%   -0.05%
==========================================
  Files          17       17
  Lines        1698     1699       +1
==========================================
  Hits         1253     1253
- Misses        386      387       +1
  Partials       59       59

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

@adamdecaf Hey Adam, i don't have any options to merge this, is that new? I can't remember last time if I got an approval I can just push the code straight in or is it due to the code coverage bot above?

Did we give you commit access to the repo? Usually a Moov employee reviews the code and merges when it looks good.

ah ok :) i probably just remembered wrong, it's been a while since I've pushed a new fix. But I just put up another PR today.


add max memory for vm configuration (#70)

Problem
on small memory SBC default java VM memory alocation is too much "3072mb"
this result in jvb and jicofo fails to start
Solution
set VIDEOBRIDGE_MAX_MEMORY and JICOFO_MAX_MEMORY in respective config file depends on estimated max user using bridge at a time

!testme


FuzzyFilePath is unaware for changes outside sublime

FuzzyFilePath is unaware for changes outside sublime, only restarting sublime or disable - enable the plugin do the trick.
for what it's worth,
here are the very specific steps I make:
1 .open sublime
2. create files outside sublime (in my case, install something with bower)
3 .go to html file and use the auto suggestions in
<script src="|"></script>

other then that, your plugin is awesome and so do you.

Thanks!
Problem is, Sublime Text does not seem offer an event for changes in filesystem. Thus it must be implemented in python which would bring other drawbacks. Project files are cached to prevent a sluggish ui on autocompletion. The cache is updated for open files that lie within the project folder, but are not currently cached. Probably thats not the best strategy. I will look into this.
In the meantime, would a command to update the cache manually be any help?

Added and released a command ffp_update_cache which rebuilds the cache. Add a command to Key Bindings -> User like i.e. { "keys": ["super+alt+u"], "command": "ffp_update_cache" } or execute window.run_command("ffp_update_cache") in Sublime`s console to add new files in project.

FANTASTIC!
Thank you very much!


feat(procedure): Max retry time

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Increase the maximum number of retries to avoid continuous retries.
Checklist

[x]  I have written the necessary rustdoc comments.
[x]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)
https://github.com/GreptimeTeam/greptimedb/issues/286
https://github.com/GreptimeTeam/greptimedb/pull/1058

I have solved all the above code reviews, PTAL :D

There are some conflicts. Could you please resolve them? @jun0315

@jun0315  Any update? Looks like only some minor comments and conflicts waiting to be fixed.


Use environment variables to inject API key, etc.

Parcel supports build time injection of environment variables. Use this feature and set the key/domain as repository secrets so that it is injected during the actions build. This will marginally sensitive details from the repo, and make it easier to change the domain/key if we need to.

What API key are you talking about?

https://github.com/cubetastic33/toborrights/blob/8bbdfacb2fe8156315fb6ac24898d19279bd915e/scripts/order.ts#L5


fixes issue #296

Thanks for catching this!
Have you submitted the CLA? (https://tableau.github.io/contributing.html)

@t8y8 Yes I have submitted the cla when I created the pull request.

Thanks for the bug fix and catching the issue!


shift in byte mode should produce runtime error for dynamic type

This should not be possible to transpile - the lv_temp type should not allow shift in byte mode
Probably a runtime check would also be required - the field symbol of type any that is pointing to invalid type should produce a runtime error instead
  DATA lv_temp TYPE string.
  lv_temp = 'abc'.
  SHIFT lv_temp BY 1 PLACES LEFT in byte mode.
  WRITE lv_temp.

a few notes on syntax errors:
it is the responsibility of abaplint to ensure the syntax is correct, there is also a lot of work to be done here
the transpiler takes the AST, and assumes its correct ABAP syntax and does it best to transpile it

Agreed. I opened a separate issue in abaplint repository.
This code should fail with runtime error instead of executing without any issue
  DATA lv_temp TYPE string.
  lv_temp = 'abc'.
  FIELD-SYMBOLS <lv> TYPE any.
  ASSIGN lv_temp TO <lv>.
  SHIFT <lv> BY 1 PLACES LEFT IN BYTE MODE.
  WRITE lv_temp.

runtime error = OBJECTS_NOT_BYTELIKE


stm32-test build failing at link time

Please take the time to describe the bug in detail, so other contributors can pick it up and implement or declare done/obsolete in case it was fixed out of band.
Current behavior
When I run pio run -e stm32-test I get the following link errors:
Building in release mode
Linking .pio/build/stm32-test/firmware.elf
/home/dheater/.platformio/packages/toolchain-gccarmnoneeabi/bin/../lib/gcc/arm-none-eabi/9.3.1/../../../../arm-none-eabi/bin/ld: .pio/build/stm32-test/libe99/libhal.a(hal_stm32.o): in function `HalApi::InitUARTs()':
hal_stm32.cpp:(.text._ZN6HalApi9InitUARTsEv+0x150): undefined reference to `dmaUART'
/home/dheater/.platformio/packages/toolchain-gccarmnoneeabi/bin/../lib/gcc/arm-none-eabi/9.3.1/../../../../arm-none-eabi/bin/ld: .pio/build/stm32-test/libe99/libhal.a(uart_dma.o): in function `DMA1_CH2_ISR()':
uart_dma.cpp:(.text._Z12DMA1_CH2_ISRv+0x14): undefined reference to `dmaUART'
/home/dheater/.platformio/packages/toolchain-gccarmnoneeabi/bin/../lib/gcc/arm-none-eabi/9.3.1/../../../../arm-none-eabi/bin/ld: .pio/build/stm32-test/libe99/libhal.a(uart_dma.o): in function `DMA1_CH3_ISR()':
uart_dma.cpp:(.text._Z12DMA1_CH3_ISRv+0x14): undefined reference to `dmaUART'
/home/dheater/.platformio/packages/toolchain-gccarmnoneeabi/bin/../lib/gcc/arm-none-eabi/9.3.1/../../../../arm-none-eabi/bin/ld: .pio/build/stm32-test/libe99/libhal.a(uart_dma.o): in function `UART3_ISR()':
uart_dma.cpp:(.text._Z9UART3_ISRv+0x8): undefined reference to `dmaUART'
collect2: error: ld returned 1 exit status
*** [.pio/build/stm32-test/firmware.elf] Error 1

Expected behavior
Compiles and links without error.

[x] Put the issue in a milestone
[x] Assign it to one of the projects
[x] Add appropriate labels
[x] Mention dependent/blocked issues if any

stm32-test is a development environment which was used for sharing Work In Progress with other team members. It remains  unmaintained when there is no need for it, and in its current state way behind the main stm32 environment.
I'd say what this needs is a proper documentation so people are not surprised that this does not work at a given point in time.


sensirion_i2c_hal_init: add parameter to specify the device path

Can you please fix the formatting of your pull request? We are using clang-format to ensure consistent formatting of our driver code

@psachs I have fixed the formatting ...


Cow: Watch stashfin

Cow requests the watch of the watch_keyword stashfin. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

stashfin has been seen in 4 true positives, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Migrate to package:web

Description

Migrates from dart:html to package:web and dart:js_interop
WASM Support

Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[x] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

WASM support would be awesome!

Thanks for the PR, I will test and approve in a couple of days

closed in favor of https://github.com/Bdaya-Dev/oidc/pull/82
Thanks for your contribution, it helped me alot!


Polish Elasticsearch IndexStructures

relate to: https://github.com/apache/skywalking/pull/9914#pullrequestreview-1171156294
@toffentoffen

Thanks @wankai123!
Does this PR fixes this comment https://github.com/apache/skywalking/pull/9914#discussion_r1015993463?

@toffentoffen I think that comment doesn't need to fix. Isn't it? This override directly uses the value, rather than the factor parameter.

@wu-sheng Probably I am misinterpreting the code. And it is already working correctly.
I thought that https://github.com/apache/skywalking/pull/9914/files#diff-7c42c99e33896647d67385263076ec5178df8e57d072e760895ed7ca9f5d1c20R219-R223
is always applied, and that config.getIndexShardsNumber() already contains either the default value or the override.

@wu-sheng Probably I am misinterpreting the code. And it is already working correctly. I thought that https://github.com/apache/skywalking/pull/9914/files#diff-7c42c99e33896647d67385263076ec5178df8e57d072e760895ed7ca9f5d1c20R219-R223 is always applied, and that config.getIndexShardsNumber() already contains either the default value or the override.

Hi @toffentoffen, these codes just rebuild the Map structure for the override, they don't change the original logic. You can check the code history.


Support edma3 for s32z270dc2 board

This PR introduces NXP S32 EDMA3 driver for SoC NXP S32Z27 and enables its usage for board s32z270dc2
Tests:
tests\drivers\dma\chan_blen_transfer:
SUITE PASS - 100.00% [dma_m2m]: pass = 4, fail = 0, skip = 0, total = 4 duration = 8.063 seconds
tests\drivers\dma\chan_link_transfer:
SUITE PASS - 100.00% [dma_m2m_link]: pass = 3, fail = 0, skip = 0, total = 3 duration = 6.047 seconds
tests\drivers\dma\loop_transfer:
SUITE PASS - 100.00% [dma_m2m_loop]: pass = 3, fail = 0, skip = 0, total = 3 duration = 1.103 seconds
tests\drivers\dma\scatter_gather:
SUITE PASS - 100.00% [dma_m2m_sg]: pass = 1, fail = 0, skip = 0, total = 1 duration = 0.076 seconds

Added commit to Split tcdpool per device that can be used for multiple instances.

@teburd @manuargue @Dat-NguyenDuy please help me take a look into this PR. All comments addressed. Thanks

Hi @teburd, Could you please help me take a look into this PR?

I rebased and fixed the conflict.

@teburd I've add @manuargue as a co-assignee so we can move forward with this PR.

@haduongquang HAL pr merged, please rebase

blocking until #78314 is merged and update the manifest

I rebased and updated the manifest


[FEATURE] Add actual value to the error message

Is your feature request related to a problem? Please describe.
Currently the error message doesn't specify what value was received, only what was expected
Describe the solution you'd like
An error message similar to
Expected value.name to be a string, but received ${JSON.stringify(value.name)}
instead of
Expected value.name to be a string
Describe alternatives you've considered
Creating my own type with overridden error, but it takes some boilerplate and I think it would be good to have in the main type too.
Also I could just create a try/catch block and append it to the error myself, but then I would not have access to atomic values of the specific check, only to the entire object.
I'm just requesting, maybe it'll be useful as a feature. Or maybe it's too bloated for the scope of this lib.

I think this is a good idea, but it has to be made optional.
For now you could use try/catch and raw errors, it'll give you the specific value and the expected value and you could build the error message yourself


[BUG] Cannot process the vote or it's invalid

node-8080-error-16-Mar-22.log:
{"name":"mainnet-prod","hostname":"mainnet-node-0-taiwan","pid":16797,"level":50,"msg":"[CONSENSUS] [handleConsensus
Message] Cannot process the vote or it's invalid: {\"tx_body\":{\"operation\":{\"type\":\"SET_VALUE\",\"ref\":\"/con
sensus/number/319627/0x2988e548c0efb0b755b07c8993f6d536134093e78d6f1eecfdfa60d0aae29a34/vote/0x007C36bf5D0F77836eE13
8EEAc8df7051b43209b\",\"value\":{\"block_hash\":\"0x2988e548c0efb0b755b07c8993f6d536134093e78d6f1eecfdfa60d0aae29a34
\",\"stake\":100000,\"is_against\":false,\"vote_nonce\":1647396840146}},\"nonce\":-1,\"gas_price\":0,\"timestamp\":1
647396840146},\"signature\":\"0xa7c28ff16d77f1d74b3f682f45ade293ad027150f90fb2d8f1cb7fca34a56a9c7819858adbae804b6b4b
ed9d0f476491a8ba864caa0b8d0487ea938feba4981d2c3f3ba1fc971999ea08a076cfe3fbb181caddf558fecbb6d670d10d2373a12426\",\"h
ash\":\"0xa7c28ff16d77f1d74b3f682f45ade293ad027150f90fb2d8f1cb7fca34a56a9c\",\"address\":\"0x007C36bf5D0F77836eE138E
EAc8df7051b43209b\"}","time":"2022-03-16T02:14:00.217Z","v":0}
{"name":"mainnet-prod","hostname":"mainnet-node-0-taiwan","pid":16797,"level":50,"msg":"[CONSENSUS] [handleConsensus
Message] Cannot process the vote or it's invalid: {\"tx_body\":{\"operation\":{\"type\":\"SET_VALUE\",\"ref\":\"/con
sensus/number/319627/0x2988e548c0efb0b755b07c8993f6d536134093e78d6f1eecfdfa60d0aae29a34/vote/0x002C76f0aeA9Ba615428d
9dF7fedEC6f8ed5369f\",\"value\":{\"block_hash\":\"0x2988e548c0efb0b755b07c8993f6d536134093e78d6f1eecfdfa60d0aae29a34
\",\"stake\":10000000,\"is_against\":false,\"vote_nonce\":1647396840107}},\"nonce\":-1,\"gas_price\":0,\"timestamp\"
:1647396840107},\"signature\":\"0x82e95548ad10088a91d0b27ad517d1bb0741b9f8a8f1bf1dc37cbdef39670ed24e6be6d35430ed3bbd
6cd06b61666598a65c4121d543851b8b23de3cafd653a852c4b4c39d5f5022240e083866e5c56a453f52d2a0d328f44395512d5384f33126\",\
"hash\":\"0x82e95548ad10088a91d0b27ad517d1bb0741b9f8a8f1bf1dc37cbdef39670ed2\",\"address\":\"0x002C76f0aeA9Ba615428d
9dF7fedEC6f8ed5369f\"}","time":"2022-03-16T02:14:00.221Z","v":0}
{"name":"mainnet-prod","hostname":"mainnet-node-0-taiwan","pid":16797,"level":50,"msg":"[CONSENSUS] [handleConsensus
Message] Cannot process the vote or it's invalid: {\"tx_body\":{\"operation\":{\"type\":\"SET_VALUE\",\"ref\":\"/con
sensus/number/319679/0xe8bbf2f5a7f979a2a0ced6f3bccc39f2c8583e9f396f67896e8f249ada8a273a/vote/0x007C36bf5D0F77836eE13
8EEAc8df7051b43209b\",\"value\":{\"block_hash\":\"0xe8bbf2f5a7f979a2a0ced6f3bccc39f2c8583e9f396f67896e8f249ada8a273a
\",\"stake\":100000,\"is_against\":false,\"vote_nonce\":1647397940194}},\"nonce\":-1,\"gas_price\":0,\"timestamp\":1
647397940194},\"signature\":\"0x2f2384cf35320aa38fce26bbdb69bc87769df833810aae394c5d2bbbe98528fe59d957c8e29751a656cc
3cd805541a5b29fe56667e7f29a036f0b2a99afb89950c010621d9888e47f9388163c7cb22f0b3f8f3f0803584617361492978d61d7825\",\"h
ash\":\"0x2f2384cf35320aa38fce26bbdb69bc87769df833810aae394c5d2bbbe98528fe\",\"address\":\"0x007C36bf5D0F77836eE138E
EAc8df7051b43209b\"}","time":"2022-03-16T02:32:20.375Z","v":0}
...

Spin-off'ed from:

https://github.com/ainblockchain/ain-blockchain/issues/973

Not sure whether it's directly related or not but this issue was seen around the time we observed the blockchain alert.
@liayoo could you take a look?

@liayoo thanks for the update.
@minsulee2 do we have any progress on the topology logging?
https://github.com/ainblockchain/ain-blockchain/issues/985


fix!: Make format feature additive

Fixes #588

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

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

Totals

Change from base Build<PHONE_NUMBER>9:
0.0%

Covered Lines:
920

Relevant Lines:
1490

💛  - Coveralls


operator: prevent unmanaged and removed state to brick apiserver

The bump commit will go away when @sttts merge, this is for testing.

/lgtm
/hold


Add Result

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (4043a65) to head (c41a203).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #53   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           18        19    +1
  Lines          261       275   +14
  Branches        22        22
=========================================
+ Hits           261       275   +14

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


Precipitation rate still not showing on all D1 weather stations

Describe the bug
Since the firmware update (0.1.15) that happened on the D1 a little more than a week ago, I started to consult the precipitation rate, to see if it was really registering now. At first I wasn't sure, since the rainfall was pretty light, but now today the rainfall was quite heavy and the precipitation rate still didn't move at all. So I think we can conclude the issue with the precipitation rate still isn't fixed.
I checked the map with all weather stations and i looked up some D1 weather stations. ALL of the D1 weather stations still have the same issue. Those that recorded rainfall during the past days, still had the precipitation rate always staying at zero all the time. Just see for yourself in the explorer map and look up D1 weather stations and look at their data, and you will see for yourself...
I really hope it's only a firmware issue, and not a problem with the D1 stations themselves not able to register a precipitation rate ? Because the first thing can be fixed, the latter is a whole other issue...
How To Reproduce
When you have a D1, just look at your Gateway (WG1200) screen when it rains. You will see the precipitation rate still staying at 0. Or look at the historical data in the app (for any D1 weather station for that matter), and you will see the precipitation rate always stayed zero during all the time that it rained.
Expected behavior
I expect the precipitation rate to be not 0 when it rains.

Additional context
It's not related to Android or IOS, or any device for that matter, it's a problem related to all D1 weather stations.
Some practical examples of D1 weather stations with rainy days  :
Name D1 station Rainy day example
Crazy Leather Fog -                                                   20/10/2024
Rural Cobalt Atmosphere -                                      18/10/2024
Rural Cornflower Dust -                                               21/10/2024
Colossal Sangria Sandstorm -                                   18/10/2024
Recumbent Brunette Stratocumulus -                       20/10/2024

I can state same issue on my D1 (firmware 0.1.15), no precipitation rate shown even though raining coninously.

I can confirm that the precipitation rate is now showing in the graphics.
However the max rate is still staying at 0.0mm/h and is not adapting to the max recorded rate of the grapic line.

Some practical examples :
Rural Cornflower Dust - 12/11/2024
Crazy Leather Frog - 11/11/2024
Rural Cornflower Dust - 11/11/2024

It also even seems that the "Daily" mm/h is also staying at 0 as well.
Practical examples of this :
Crazy Leather Frog - 11/11/2024
Rural Cobalt Atmosphere - 11/11/2024

It also seems that the "Daily" number is also staying at 0.0mm/h, even though it rained.

Practical examples of this :
Crazy Leather Frog - 11/11/2024
Rural Cobalt Atmostphere - 11/11/2024

So even though, all the graphics are now working for the precipitation, both numbers ("Max Rate" & "Daily") above the graphics, still stay at 0.

Hey @Chris6175 , the charts show 0.0 in the labels because the time selected is the 00:00 (the start of the chart) as can be seen above the labels.

If you select a different time in the chart having precipitation, the labels will be adjusted automatically.
Could you please verify this so then we can close this issue?

Hello,
Indeed, you are correct. In that case, it working fine.
You can close it, thank you.
best regards,
Chris.


Issue #283: Configuration file for ansible-lint

I'm trying my hand at adding the configuration file mentioned in issue #283.  I'm a newbie to Python so please go easy on me.  All code was written with TDD.  I wrote the tests to invoke ansible-lint as a subprocess and compare the output of the CLI arguments to its equivalent config file.  I wasn't sure if there was a better way to write them but I'm open to suggestions.
Please let me know any concerns or suggestions.

@njenan this is great, thank you for doing this! In terms of next steps, don't feel you need to implement all of the different config files, but I would like the reading of the configuration file to be parameterised and allow for different future options (and avoid the config global)

Sounds good, working on the command line switch for the config file right now.  Because the configuration values are passed as the default values of the CLI flags (so it can be overridden from the command line), the config file needs to be parsed and loaded before the other flags are evaluated.  I'll probably have an update sent out tomorrow afternoon because it is getting late here.

Ok, I pushed some changes.  I parse the -F argument directly.  The reason for this is because I can't pull the -F value from the optparse because I need the configuration file to populate the default CLI args.  I tried using getopt, but it had problems with certain ordering of CLI args.  So... I don't have a better solution than this.  Let me know if you have any ideas.

I'm actually ok with the defaults shown with just ansible-lint --version being the standard defaults and ignoring the configuration files (otherwise they're not really defaults)
However, if you're keen to show the current defaults, maybe try the default configuration file locations first, and use them to populate the default CLI args - I don't think people need to see the defaults to be the values they push in with a file described with -F which will pretty much override any defaults.

If I understand the way opt parse works, the problem is this:
import optparse

parser = optparse.OptionParser()
parser.add_option("-a", dest="a", default="default_value")

opts, _ = parser.parse_args()
print(opts.a)

So if I invoke the script
python file.py
>> default_value

But if I add the -a arg:
python file.py -a override
>> override

So in terms of the current code, if I do the following:
def main():

     load_config_file()  # <- This can't be the first line because I don't know the location of the config file yet
...
    parser.add_option('-F', help='Specify configuration file to use.  Defaults to ".ansible-lint"')
...
    parser.add_option('-q', dest='quiet',
                      default=config.config_or_default("quiet", False),  # <- But I can't define these parser options without having the configuration files and the default values
                      action='store_true',
                      help="quieter, although not silent output")
...

So basically I need to load the configuration file, but I can't load the file until I parse the -F arg, but I can't parse the -F arg with opt parse without defining the default values, and I can't define the default values until I load the configuration file.
Hopefully I am explaining this adequately, maybe there is an obvious solution I am not seeing.

Actually, I thought about it, and I think I know what another option would be.  Load the configuration file, and then merge the args from the configuration file with the args from optparse.  There would not be a cyclical execution dependency with this approach.
The disadvantage of this approach would be that if someone set a config in a configuration file, then they would not be able to override it from the command line.  Because I wouldn't be able to tell what options were default or user specified when merging the config and CLI args.

The disadvantage of this approach would be that if someone set a config in a configuration file, then they would not be able to override it from the command line. Because I wouldn't be able to tell what options were default or user specified when merging the config and CLI args.

Yeah, you're right, this is harder than it looks!
It's not clear to me what should be expected when you add more append values  (e.g. rules directories) on the command line when using a config file anyway - should it replace or augment them?
A lot of command line arguments might work as people expect anyway if they're store_append or increase/decrease a value.
If we can get to a reasonable, documented result then we should be good - even if the documentation says "If you have a configuration file and wish to override values, please use -F with a new configuration file" that will be better than we currently have

Ok, please take another look.  I added logic to merge the config and CLI options.  In the case of True/False values, the True value is preferred, and in the case of lists they are simply merged.  I think this will produce the least surprising behavior for the user.

Ok, branch should be working now.

Two relatively minor changes and we should be good to go.
Might check with the owners of issues regarding a configuration file if this works for them before merge though.

Great! Thanks.
Some small feedback:

is -F a good option? It's for File which can be confusing with the program argument (files to check). Wouldn't be -c and/or --config[-file] better? (cf. yamllint, pycodestyle)
maybe all the options are not meant to be in conf file like verbosity or quiet
I'm not sure about the merging/adding, can be weird to use -v on the command-line but ending with -vvv because verbosity: 2 in config file. The typical behavior is having CLI args overriding config file
May be nice to avoid listing all options in merging strategy as new CLI args may be missed in the future (add in the argparse but not in the merging).

I'll update it to -c
I can remove those, I figured it was better to include it rather than not, I'll defer to @willthames judgement on this
For verbosity specifically, as far as I can tell, values 1 and over function identically (based on my quick search of the code base and a few experiments), I don't think this will be an issue.  For overriding args, there are a couple issues with overriding the default args, namely I don't have a good way of telling if an argument is default or not, so I decided to go with a merging strategy (see my first commit).    I was not able to figure out how to solve this issues, but I'm open to suggestions.
I had considered doing some sort of dynamic combination of the args and config file, but my concern was there might be bugs with unexpected values passed in by the user.  Do you have any ideas how I could make sure my code covered all cases?

Looks great! Waiting for this feature so much.

Ok, I'm going to merge this and one other PR and release it as 2.5.0-rc1 for wider testing


Expose PUDL, archives, and studio staging on plum

Assuming we can only have one source, they probably need to share a parent directory, something like
/mnt/image_sources/studio
/mnt/image_sources/pudl
/mnt/image_sources/archives

and then we configure Browse Everything to point to /mnt/image_sources.

The studios would like to try this by the end of next week (by 2/3). Work with @rmunoz to to get access to the their staging server.


SEO optimizations for KW: "AWS containers"

Optimized for SEO, primary KW: "AWS containers."

Proposed changes
Mainly just changes to metadata as well as an extra instance of the keyword and a couple of internal links that may be beneficial.

@cnunciato

to be clear ... my suggestion was for 97th to decide on this!
personally, i assume adding this is the right thing to do, since in theory,
that's what the PR is about, however, i'm never 100% sure and maybe it's
not the right thing to repeat here for some reason.
so, if they are OK with "one more" ... I'm ok ... if they don't want the
latter change, I'm ok too ... i just want to make sure they see the
suggestion ... decide and then we can commit
On Thu, Feb 20, 2020 at 12:59 PM Christian Nunciato <
<EMAIL_ADDRESS>wrote:

@cnunciato approved this pull request.
This seems fine to me, but I'll await @ericrudder
https://github.com/ericrudder's 👍 before merging, in light of his
question.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pulumi/docs/pull/2481?email_source=notifications&email_token=AB77TQV5EV426DOPZMKHOPTRD3VKNA5CNFSM4KYEQ562YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCWLTBGQ#pullrequestreview-362229914,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB77TQUBTL7LPFLLUGIEL5DRD3VKNANCNFSM4KYEQ56Q
.


feat(copy): makes copy more efficient

What this PR does / why we need it
This PR improves CopyAsync and CopyGraphAsync to include the CopyOptions, inspired from oras-go.
The current implementation:

adds support for CopyOptions events, like OnPreCopy, these were implemented in the form of Action<T>s
adds support for mounting layers from other repositories.

Pending items

[ ] Concurrency support
[x] Fix copy mounting tests
[ ] Test CopyOptions events

Which issue(s) this PR resolves / fixes

Fixes #50
Please check the following list

[x] Does the affected code have corresponding tests, e.g. unit test, E2E test?
[x] Does this change require a documentation update?
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[x] Do all new files have an appropriate license header?

This is a work in progress. Seems to be working running locally. Tests are failing and need more work.

Hi. I propose concurrency support is implemented in a separate PR. Otherwise this should be ready to review :+
Leo.

Hi all, any feedback is appreciated :1st_place_medal:
Thanks!
Leo.

Hi @leonardochaia , thank you for your contribution! Sorry for the delay. We need a bit more time to review your PR, but we’ll provide feedback as soon as we can.  Thank you for your understanding!

Hi. I propose concurrency support is implemented in a separate PR. Otherwise this should be ready to review :+

Do we want to move the mounting support to a separate PR as well?

Hi. I propose concurrency support is implemented in a separate PR. Otherwise this should be ready to review :+

Do we want to move the mounting support to a separate PR as well?

Hi @Wwwsylvia , thanks for the review. I'll apply the changes and report back.
We can move the mounting to a separate PR. In such case we would leave only the CopyOptions and related events on this PR, and implement the IMounter and mounting support on copy on a separate PR.
My goal is getting the mounting support when copying graphs since we are using this to replicate a bunch of images between registries and need to make it faster.

@leonardochaia Sounds good. Thank you!

PR simplified to only introduce the CopyGraphOptions. Next step is to update the tests to cover the events.
Separate PRs/issues to be created:

Copy to support concurrency
Repository to support mounting
Copy to support mounting

I propose we

Quick update, I've converted this PR to only include the CopyGraphOptions with events support and corresponding tests.
Next steps:
Add support for mounting to Repository https://github.com/oras-project/oras-dotnet/pull/152
Add support for mounting to Copy (after this and https://github.com/oras-project/oras-dotnet/pull/152 are merged)

Thank you! I just created the following issues to track:

#153
#154

Build should be fixed, tests passed locally.
@Wwwsylvia thanks for creating the issues, JIC: only CopyGraphOptions was introduced in this PR. I propose we leave CopyOptions for a separate PR with the MountFrom feature, as per oras-go:
// CopyOptions contains parameters for [oras.Copy].
type CopyOptions struct {
	CopyGraphOptions
	// MapRoot maps the resolved root node to a desired root node for copy.
	// When MapRoot is provided, the descriptor resolved from the source
	// reference will be passed to MapRoot, and the mapped descriptor will be
	// used as the root node for copy.
	MapRoot func(ctx context.Context, src content.ReadOnlyStorage, root ocispec.Descriptor) (ocispec.Descriptor, error)
}

https://github.com/oras-project/oras-go/blob/bf570bcc78b3aa1bad84401e3390cc79a03e426e/copy.go#L50-L57
When CopyOptions is introduced, there should be no breaking change since it should inherit from CopyGraphOptions
Thanks!
Leo.

@leonardochaia The MountFrom and OnMounted options are included in CopyGraphOptions (See https://github.com/oras-project/oras-go/blob/bf570bcc78b3aa1bad84401e3390cc79a03e426e/copy.go#L108-L113).
Since oras-dotnet is still under initial development, breaking changes are acceptable if they are necessary.

Hi @Wwwsylvia , sorry I meant to say MapRoot instead of MountFrom :+1:
Thanks!

This should be good to go.
Once this is merged I'll create a separate PR to support mounting when copying :1st_place_medal:


Update MD file on new branch 2017-48-13_01-11-53

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

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


how to deploy https://huggingface.co/flair/ner-english-ontonotes-large as it doesn't have a config.json

Hi I was trying to deploy this model on sagemaker and unfortunately it throws an error because it can't find the config.json, I was able to deploy other models using the same template provided but this one failed because there is no config.json provided. the model is available for inference in the hugging face models API and it's working fine, so please let me know how can I deploy this model onto sagemaker !! https://huggingface.co/flair/ner-english-ontonotes-large

Hey @DevBey,
Currently, the SageMaker Hugging Face Inference Toolkit only supports transformers compatible models. That's also the reason why you don't see the option "Amazon SageMaker" on the model card.
You can try to use the https://huggingface.co/asahi417/tner-xlm-roberta-large-ontonotes5 if you want a transformer-based fine-tuned on ontonotes

yeah, that's what I understood too, but can we override the methods using inference.py. because all it needs is changes in just load model and predict methods ?? if this works I could also deploy KEYBERT which again is not natively available in transformers !!
Though anyway currently I was able to deploy keybert and flair transformers onto sagemaker  by overriding their model loading and predicting functions !!
Do let me know if that would work, as I can see how optimized the hugging face sagemaker inference containers are compared to container deployed using mlflow !!

Yes, you could create your own inference.py and adding a requirements.txt with your required dependencies. As documented here: https://huggingface.co/docs/sagemaker/inference#user-defined-codemodules
Would love to hear if you see some performance difference between the containers of mlflow. But I have to that we created them to run the Hugging Face libraries, so I am not sure if you see any improvements when using flair.

ok great, thanks anyway for the help.
let me close this, for now.
only one more thing is there someplace I can find examples of custom inference.py, it would be great to see some examples of custom inference.py in PyTorch.

Okay, closing this for now. Feel free to re-open it again.
To your question, yes. The Documentation contains an example of how you can create a customer inference.py additionally you can take a look here, that's the inference.py to run tests


Use same name as for final dirs

Hello, I noticed that it has to be different names for final dirs. Is there a way to improve it or work around? I always use .venv for all my virtualenvs. It would be nice that using different names is no longer a hard requirement.

@shwsun heh, I know this day would come eventually when I added this feature. Congrats on being the first person to ask about it in ~3 years :P
Anyway, the code around this is a bit of a mess, and fixing it would require a pretty substantial overhaul of the internals of the package, which I will get to eventually but would like to put off for a while longer. Right now, the only workaround is to use the projectile integration, which is a bit of a hack but is perfectly happy with all your vitualenvs being called .venv. Would that work for you for now?

Sounds great! I will spend some time on that.

I'm going to close this, since it's possible to do this with the projectile integration. Someday I will have a Saturday and nothing to do and feel like programming and I will get around to doing the big refactor I describe above to support this in a less hacky way.


python3Packages.anyio: 3.3.0 -> 3.3.1

Motivation for this change
https://github.com/agronholm/anyio/blob/3.3.1/docs/versionhistory.rst
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 137211 at 79861edf run on aarch64-linux 1

3 packages failed to build:

home-assistant
python38Packages.apache-airflow
python39Packages.apache-airflow

2 packages skipped due to time constraints:

apache-airflow
python39Packages.teslajsonpy

86 packages built successfully:

datasette (python39Packages.datasette)
dyndnsc
lexicon
python38Packages.PyRMVtransport
python38Packages.anyio
python38Packages.authcaptureproxy
python38Packages.axis
python38Packages.datasette
python38Packages.datasette-template-sql
python38Packages.denonavr
python38Packages.dependency-injector
python38Packages.elmax
python38Packages.entrance
python38Packages.entrance-with-router-features
python38Packages.envoy-reader
python38Packages.fastapi
python38Packages.ha-philipsjs
python38Packages.httpcore
python38Packages.httpx
python38Packages.httpx-ntlm
python38Packages.httpx-socks
python38Packages.ipfshttpclient
python38Packages.ircrobots
python38Packages.ismartgate
python38Packages.json-logging
python38Packages.jupyter_server
python38Packages.jupyterlab
python38Packages.jupyterlab_server
python38Packages.jupytext
python38Packages.nbclassic
python38Packages.pylitterbot
python38Packages.pypoint
python38Packages.pytest-httpx
python38Packages.pytest-sanic
python38Packages.respx
python38Packages.sanic
python38Packages.sanic-auth
python38Packages.sanic-testing
python38Packages.slowapi
python38Packages.sunpy
python38Packages.teslajsonpy
python38Packages.total-connect-client
python38Packages.youtube-search-python
python38Packages.zeep
python39Packages.PyRMVtransport
python39Packages.anyio
python39Packages.authcaptureproxy
python39Packages.axis
python39Packages.datasette-template-sql
python39Packages.denonavr
python39Packages.dependency-injector
python39Packages.elmax
python39Packages.entrance
python39Packages.entrance-with-router-features
python39Packages.envoy-reader
python39Packages.fastapi
python39Packages.ha-philipsjs
python39Packages.httpcore
python39Packages.httpx
python39Packages.httpx-ntlm
python39Packages.httpx-socks
python39Packages.ipfshttpclient
python39Packages.ircrobots
python39Packages.ismartgate
python39Packages.json-logging
python39Packages.jupyter_server
python39Packages.jupyterlab
python39Packages.jupyterlab_server
python39Packages.jupytext
python39Packages.nbclassic
python39Packages.pylitterbot
python39Packages.pypoint
python39Packages.pytest-httpx
python39Packages.pytest-sanic
python39Packages.respx
python39Packages.sanic
python39Packages.sanic-auth
python39Packages.sanic-testing
python39Packages.slowapi
python39Packages.sunpy
python39Packages.total-connect-client
python39Packages.youtube-search-python
python39Packages.zeep
theharvester
wapiti
ytmdl

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


Allow Gitlab.com repositories as a source

Lets people use plugins from Gitlab the same way as Github/Bitbucket

Thank you for your contribution! I'll try your source.

@jameshclrk I can't test this P-R. Have you confirme that operation?

Thank you for your contribution, but I'll close this as code modification is not seen


requirements_dev.txt missing

The docs (contributing.rst and CONTRIBUTING.md) suggest that I should install a conda env using ci/requirements_dev.txt, but that file is missing.

it has existed for quite some time
you need to pull from master

Right! So sorry.


fix(bower) error on bower.json

A missing bracket cause some build system to failed.
https://travis-ci.org/davinkevin/Podcast-Server/builds/69639357

Thank you! I was about to do it but you saved my time! :dancer:


Move temp folder to ram disk

Hi, I would like to move the temp folder that's normally located next to rootfs to ram in wsl1. Since there's no way to create a joint or symlink that would be recognized I would like to do this with this tool maybe.

Sorry, LxRunOffline is unable to perform this task, and I'm not aware of any approach to achieve this.
BTW, as far as I know the temp folder doesn't store any regular files and it has 0 bytes on disk according to the Windows's property page. So I doubt there will by any performance improvements by doing so.


[freetype] use config and the correct alias

Neumann-A figured out that add_library(Freetype::Freetype ALIAS freetype) is defined so instead of Freetype::Freetype use freetype. qis Also pointed out that freetype uses a cmake config file. Thats why CONFIG parameter is required.
Describe the pull request

What does your PR fix? Fixes issue #
The usage file from freetype library.
Which triplets are supported/not supported? Have you updated the CI baseline?
All should be supported. They should not have been changed. No.
Does your PR follow the maintainer guide?
Yes.

@Neumann-A figured out that add_library(Freetype::Freetype ALIAS freetype) is defined so instead of Freetype::Freetype use freetype

??? I never said that. I said you could use that to define the target properly since add_library(Freetype::Freetype ALIAS freetype) only works with targets and CMake throws and error if target_link_libraries cannot find a target.
With target_link_libraries(main PRIVATE freetype) freetype can either be a target or a library. If freetype is not a target CMake will assume it is a library and link against. So the error you will get if you are missing a find_package call is a linker error which is not as intuitive as the CMake error if target_link_libraries would actually use a namespaced target instead. .

I am really sorry for misunderstanding you. I did what I have understand you told me and that worked.  So instead of editing the usage file this should be added to my project?
I guess this PR can then be deleted or just denied. ~Sorry

I have nothing against the PR just the twisting of facts told by the comment ;)

I have nothing against the PR just the twisting of facts told by the comment ;)
and qis was the one you told you how to do it on slack

alright, I can just say sorry again for both of you that I have mixed this up while hoping that both of you are not angry with me. 😊
Hopefully, besides that, the PR fixes the issue which I had initially.

/azp run

If we want to use CONFIG mode, we can simply delete usage.
And I think we prefer to use freetype-config.cmake because it is more adapted to the freetype generated by vcpkg.
But we already have many ports that depend on it, and we need to test using it.

Test OK, I think we can use it now.

 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.:x: B4rtware sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

/azp run

Thanks for the PR!


Do not start after restart xcode 7

and rotate all images in packed manager for 180 degrees

+1
This bug makes TimePlugin unusable

See Pull Request "XCode 7 Compatibility UUID's" to fix the issue.

Merged pull request


Feature/Extend-request-builder

added method to generate request contract
added product name to the method generating asset product
added marketplace name to the method generating marketplace for request, asset, tier config

 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.


Incorrect sign extension behavior

As reported by @wysiwyng in https://github.com/Minres/CoreDSL/issues/58, casting an unsigned value (such as an encoding field) to a signed type does not sign-extend the value (because the source type is unsigned).
https://github.com/Minres/RISCV_ISA_CoreDSL/blob/726fb8117b47714ee891f89032fb8a9ce167b1e2/RV32I.core_desc#L9-L13
(There might be other occurrences of this pattern.)

Correct form would be:
X[rd % RFS] = (unsigned<XLEN>) ((signed) imm));


Create Cow and Haybales CF

Did you just create 8 PR's which are completely unrelated to this repository on two of your GitHub accounts just to score Hacktoberfest PR's?
This is unacceptable. I'll label all of your PR's as spam and make sure you won't be allowed to participate.


Adding timeout to prevent webhook failures

If a webhook never returns, it will hang forever and all subsequent webhooks will not be called.  This resolves the issue.

Manually tested and verified to work.


[Snyk] Security upgrade jest from 23.6.0 to 24.0.0

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

packages/ffe-core-react/package.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

589/1000  Why? Has a fix available, CVSS 7.5
Prototype Pollution SNYK-JS-MERGE-1040469
Yes
No Known Exploit

494/1000  Why? Has a fix available, CVSS 5.6
Command Injection SNYK-JS-NODENOTIFIER-1035794
Yes
No Known Exploit

601/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.6
Prototype Pollution SNYK-JS-YARGSPARSER-560381
Yes
Proof of Concept

506/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
Regular Expression Denial of Service (ReDoS) npm:braces:20180219
Yes
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Coverage remained the same at 82.009% when pulling 7ccc1d5446112aaf263a1227b916ab61c54cea8f on snyk-fix-50a3ede4ffc28f49447d7b3075af42c4 into d743d78bab0f6a4ce0bc199e8e419261247ca8b6 on develop.


OAUTH2.0 authorization code grant in API description

Problem description
According to issue #53 from commonalities we should use the OIDC security scheme for NumberVerification API.
There is an inconsistency inside yaml between the description & UML that points to OAUTH2.0 authorization code grant flow.
It is either OAUTH2.0 or OpenID Connect (with ID Token delivered in token response).
Expected behavior
Description that meets requirements from Commonalities - OpenID Connect flow described within UML & API description (yaml)
Alternative solution
If we think that we should use OAUTH2.0 Authorization code grant alternatively - we should apply changes in yaml and promote them inside commonalities.
Additional context

discussion continues here: Issue#90 Identity & Consent Management


[STREAMPIPES-649] Update REST API for data streams

Purpose
Harmonize the API to read data streams.
Fixes: [STREAMPIPES-649]

@tenthe changes look good to me.
Do you know why the E2E tests fail?

Hey @bossenti thanks. The E2E tests failed due to some problems in the UI build. The problem is already resolved in dev and was not related to this PR.


KON-540 Update hasTestClass logic

Merge after https://github.com/LemonAppDev/konsist/pull/773

Duplicated with https://github.com/LemonAppDev/konsist/pull/783


Drop some artifacts during pipeline

This is similar in behavior to what the Pipeline used to do before the DAG refactor. We keep important artifacts such as asm_string, pil_string, optimized_pil and the columns, and drop the artifacts that are built along the way. They can still be computed on-the-fly if some module needs them.
This saves 50% RAM during execution in a heavy benchmark.

@georgwiese a bit of both:  constrained_machine_collection and linked_machine_graph seemed to use 5GB each which sounds quite a lot, given the asm string is like 400MB. We should still investigate.


SSL certificate size

From @tijnkooijmans on March 17, 2016 10:6
Is there any limit to the SSL certificate size in axTLS?
I'm using WifiClientSecure and when I have fully-chained certificate (6 kb) on the server the connection gets refused (error -1) while if the server only uses the non-chained certificate (1.8 kb) there is no problem.
I have 30 kb heap available when making the SSL connection so it's no memory issue.
Thanks in advance for looking into this!
Copied from original issue: esp8266/Arduino#1788

Okay, this is what seems to be happening... In order to reduce memory pressure during handshake, we allocate smaller TLS fragment buffer (~6kb) than per spec (16kb). Then when connection is established, we allow this buffer to grow as required. I will check if we can allow this buffer to grow during handshake, i.e. whether it will fit into RAM.

From @tijnkooijmans on March 17, 2016 10:52
Thanks for your super-fast response! This is the one without chain:
brokerstagingdev.minibrew.io
This is the one with chain:
brokerstaging.minibrew.io

Could you please advise how to reproduce this? What server URL should I use for non-chained certificate and fully-chained certificate?

From @tijnkooijmans on March 17, 2016 11:33
Great, thanks! Looking forward to test if you can make this work.

Did you get a chance to look into this? Thanks!

Should be fixed in latest version.


Add proxy support into client config

Sometimes clients use proxy for access internet, so I added 2 ENV var OVPN_CLIENT_PROXY & OVPN_CLIENT_PROXY_PORT.

Thanks for your PR but this too specific of an addition. (It's a client configuration)
You can easily modify the functionality of this project by mounting your own openvpn.tmpl into /etc/openvpn/templates/. Note that you can still use variables in the openvpn.tmpl! :-)


feat: add yarn berry / modern (version 2 and later) examples

This PR is related to issue #799 "Examples for Yarn 1 (Classic) and Yarn Berry / Modern (Version 2 and later)" and it complements the Yarn 1 (Classic) examples added through PR #828.
It provides new examples for Yarn Modern under the directories:

examples/yarn-modern
examples/v9/yarn-modern

together with a new corresponding workflow

example-yarn-modern.yml
an update to the following script to automate maintenance updates to cypress@latest

scripts/update-cypress-latest-other.sh

and an update to

README.md

Verification
Local
nvm use 18 # for node v18.15.0
npm install yarn -g
yarn -v

expect 1.22.19
Yarn Modern with Cypress 9.7.0
From root of repository ...
cd examples/v9/yarn-modern
yarn -v # should yield 3.4.1
yarn
yarn test

Confirm Cypress test passes.
Yarn Modern with Cypress 12.8.1
From root of repository ...
cd examples/yarn-modern
yarn -v # should yield 3.4.1
yarn
yarn test

Confirm Cypress test passes.
Update script
From root of repository ...
cd examples/yarn-modern
yarn add<EMAIL_ADDRESS>-D # install older version
cd ../..
npm run update:cypress
cd examples/yarn-modern
yarn info cypress --name-only

Confirm that Cypress has been updated to latest version (12.8.1).
GitHub
Manually run the workflow

example-yarn-modern.yml

and confirm success.

@lmiller1990
Many thanks for merging! Now that Yarn Classic and Modern are documented, I will follow up by documenting pnpm, which was not documented at all when support for this package manager was added to the action.

@lmiller1990
If you are able to, please follow the instructions in Updating the latest version in GitHub Marketplace since the Marketplace version is lagging behind at v5.3.1.
If not, then perhaps @jaffrepaul will need to take action?

Thanks @MikeMcC399, done! The marketplace now shows 5.5.1 as the latest.


Select Wine Edition

WIth the code normal wine doesn't install because you need to choose if its the stable or the experimental build

Hi @Seba201x
What your O.S.?

@4w4k3 Ubuntu


Issue #1059 Fix And Some Debug Overlay Changes

Contains
Fixes Issue #1059 and some extra changes in debug overlay to reduce the clutter.
How to test
Enable Debug Mode > Try enabling Wireframe or Bounding Box mode. You'll get a overlay text to specify the active mode.

Can one of the admins please verify this patch?

Sorry for two commits. I forgot to add a new line at end of one of the file.

No problem and thanks! Going to trigger our build bot
@GooeyHub: add to whitelist

Hooray Jenkins reported success with all tests good!

For future reference, we don't stress about how many commits there are in a PR.
Often times if the feature/change is hefty it's easier to review when it's logically split up into commits.
If you make a ton of commits with one line changes, we can also just squash and merge, which will remove the high commit count.


fix: update ras pi tutorial w/ youtube vid and minor typo fixes

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

GitHub release
1.4.2

Your semantic-release bot :package::rocket:


Add support for custom OpenAI API Base URL and DuckDuckGoSearch

Added support to change OpenAI API Base URL which fixes #22 #33
Added support to use DuckDuckGoSearch as a Bing Alternative fixed #65

Code Review Agent Run Status

AI Based Review: Successful

Code Review Overview

Summary: This PR introduces the ability to configure the OpenAI API Base URL and adds support for DuckDuckGo as an alternative search engine to Bing. These changes allow for greater flexibility in using different search engines and interacting with potentially different OpenAI API endpoints, which could be beneficial for users in regions where Bing is less effective or for those who prefer DuckDuckGo's privacy-focused approach. Additionally, the update enhances the project's configurability and adaptability to different environments and user preferences.
Code change type: Feature Addition, Configuration Changes
Unit tests added: False
Estimated effort to review (1-5, lower is better): 2 - The changes are straightforward and well-structured, but thorough testing is necessary to ensure the new functionality does not introduce regressions or errors.

 >>See detailed code suggestions<< The Bito AI Code Review Agent successfully reviewed 6 files and discovered 20 issues. Please review these issues along with suggested fixes in the Changed Files.
High-level Feedback
The PR is a valuable addition to the project, enhancing its flexibility and usability. However, it's crucial to ensure that these new features are thoroughly tested, especially since they involve external APIs and user preferences that might vary widely. Including unit tests for these new functionalities could significantly improve the PR's quality and reliability.

Add this please

Can someone please merge this?
Especially the part with the customized address of the endpoint, which is something that will solve a lot of problems.
Thank you

/review performance


user docs: Update Mute a topic doc with new Settings feature.

Adds user guide documentation for muting a topic using the new Muted topics tab in the Settings page.
Fixes #3793

Merged, thanks @synicalsyntax!


Server side blazor does not trigger @bind update for auto filled input fields

I have a test app with a login form with a username and password input, both bound to string properties on the model. It works correctly if I manually enter values in these fields (the string properties get updated from the @bind directive).
If the browser has a cached username / password combination and I select auto fill for these fields, the fields do get filled (visually on the page) but the bound password property does not get updated (the username does). The password field does get filled correctly on the browser, if I make any change to the field (add a space for example), the string password property does get updated.
It looks like whatever event is used to trigger the update does not get processed correctly or does not fire for the auto filled password. I have not tested with other auto filled form fields.
This was tested on Safari & Edge. When exactly the same code is used compiled for client side Blazor it works 100%.

Seems fixed in latest version (core 3 preview 2)

It looks like this is still an issue in Edge, works in Chrome. I use the Blazor 3.0 RTM
I use this code but the variable is never set unless you type something in the input box.
<input type="text" name="dlinput" list="dl" @bind="@myvar" />

@myvar
@code
{
string myvar;
}


Slow + No config options

I am using Pygmalion 2 7B 5q quantized gguf model on my MacBook Pro M1 14" with 16GB RAM and 512GB SSD. The model performs well with short sentences, but processing slows down significantly when I input around 512+ tokens, and even can crash in that scenario. However, when using Koboldcpp (Llamacpp based), it generates results quickly. Is there a way to improve the speed, such as utilizing BLAS or adjusting the number of GPU/CPU? Any suggestions?

I was beginning to feel frustrated about why it wasn't working, but if it's happing with other people as well, then perhaps it's the problem of the library itself 😂😮💨

It's working now.


HTTP connection check and improved error messages

One of the most common problems in abapGit is dealing with connection issues.
This change introduces a connection check when working with online repositories. The connection is checked in the following situations:

Creating a new online repo
Changing the URL in remote settings of a repo
Opening the repository view of a repo

Errors are now shown at the bottom of the current page. This allows viewing of the error longtext, which now provides details about the attempted HTTP connection (hostname, SSL ID, and proxy). It also includes links to the important transactions (rz10, strust), the global proxy settings, and the corresponding abapGit documentation (see last screenshot).
On the repo view, the header remains visible so that you can jump to the repo settings as well, for example, to correct the URL.
Before:

After:

Closes #6772

This looks great!
There might be one side effect though. Currently often developers in development systems attempt to install abapGit and fail because of network issues. Then they get the basis team involved which understandably complains about the developer messing around in system settings and certificates they have no idea about or not adhering to company policies they didn't know about because it's not their area of expertise. Since developers often have SAP_ALL in dev boxes and are just restricted by policy to not change system settings no authorization checks prevent them from messing stuff up. These new detailed error messages will lessen the chance of the basis team getting involved at all and increasing the chance of developers just trial-by-erroring their way through... Maybe add a comment to get the basis / network team involved?

True. Someone will go off, connect SAP to the world, and get covid into their system 😄
I added a comment here and also to docs.

i have a fix. needs some more testing

@mbtools is this PR ready for review again?

yes

As of today, I get this error message when accessing any repository with ZABAPGIT. Could this be related to this PR? Just wondering, because yesterday it worked and today, something is broken?!  (The fork I am running contains the changes from this PR.)

As of today, I get this error message when accessing any repository with ZABAPGIT. Could this be related to this PR? Just wondering, because yesterday it worked and today, something is broken?! (The fork I am running contains the changes from this PR.)

The certificate seems to have been renewed on GitHub's side today. You may need to trust it in your system.

Thanks for the input 🙌


Watson x

Language name
URL of example repository
URL of syntax highlighting grammar
Most popular extensions

Detected language

@johnnybostar Please fill out the issue template, and explain what it is that needs adding to Linguist.


add task owner to dbt operator

Description
add owner information to DbtxxxOperator
Related Issue(s)

#1065
Breaking Change?

Checklist

[ ] I have made corresponding changes to the documentation (if required)
[x] I have added tests that prove my fix is effective or that my feature works

here is  the result in airflow web ui

@tatiana
plz check this


Can't run in Github Actions due to sudo use

When I try to use this in Github Actions I get these errors:
initdb failed! stdout:

stderr: sudo: initdb: command not found
), location: Location { file: "/root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pgtemp-0.3.0/src/run_db.rs", line: 72, col: 9 }

from what I see, this happens because sudo can't find initdb in its secure path - adding the path to postgres to $PATH doesn't solve the issue.
I mitigated the issue by copying the whole postgresql bin &lib folders into /usr/bin & /usr/lib respectively, but it would be nice if the library could handle this.

If you have the $GITHUB_PATH step in your github action, you probably need to do something like sudo -E so that the updated $PATH environment variable is carried over.
However, postgres itself refuses to run as root so I'm not sure what you're doing will work at all.

However, postgres itself refuses to run as root so I'm not sure what you're doing will work at all.

It works, I assume thanks to the sudo call in pgtemp.
As for using sudo -E - it seems like it isn't supported by the sudo in the runner:
Run sudo -E
usage: sudo -h | -K | -k | -V
usage: sudo -v [-ABkNnS] [-g group] [-h host] [-p prompt] [-u user]
usage: sudo -l [-ABkNnS] [-g group] [-h host] [-p prompt] [-U user]
            [-u user] [command [arg ...]]
usage: sudo [-ABbEHkNnPS] [-r role] [-t type] [-C num] [-D directory]
            [-g group] [-h host] [-p prompt] [-R directory] [-T timeout]
            [-u user] [VAR=value] [-i | -s] [command [arg ...]]
usage: sudo -e [-ABkNnS] [-r role] [-t type] [-C num] [-D directory]
            [-g group] [-h host] [-p prompt] [-R directory] [-T timeout]
            [-u user] file ...

I'm not sure that there is a solution to this issue 🤷

It works, I assume thanks to the sudo call in pgtemp.
Ah, I had gone back and forth on whether to include that feature and forgot that I actually ended up keeping it.

I'm not sure why it isn't working for you in github actions then. You definitely have the $GITHUB_PATH step included in your action prior to starting pgtemp?

Yup, github path is set in an earlier step and PATH is echoed in the test
step to verify that it includes the postgresql dir, but 'sudo' doesn't use
the updated path.
On Tue, 9 Jul 2024, 23:36 Harry Stern, @.***> wrote:

It works, I assume thanks to the sudo call in pgtemp.
Ah, I had gone back and forth on whether to include that feature and
forgot that I actually ended up keeping it.
I'm not sure why it isn't working for you in github actions then. You
definitely have the $GITHUB_PATH step included in your action prior to
starting pgtemp?
—
Reply to this email directly, view it on GitHub
https://github.com/boustrophedon/pgtemp/issues/8#issuecomment-2218686203,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDEBBULSFO7BX4TD7BH7H3ZLRCWXAVCNFSM6AAAAABKSP4IOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJYGY4DMMRQGM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Allow blocking launch of federated tracker.

Let other frameworks like nvflare to set the worker parameters.

cc @rongou .


Image Resolution and Flop Parameter

Hello all,
First of all, thanks for this amazing plugin!
Would be nice if there's a parameter on the component that let's you choose the resolution. Even more, if you could choose the resolution for the detection and the resolution for the output camera image. As an example, now I'm trying an AR filter idea where I have a fullHD webcam (I want to try also a 2k webcam). Would be nice if for instance the detection was done on a lower res image like 1280x720 but still getting the fullHD original image from the webcam as a TOP (now you are constrained to 1280x720 and same res for detection and output TOP image).
Also another parameter that would be handy would be a flop parameter. For instance, coming back to the AR filter idea, to achieve a similar "selfie" ratio, I am manually flipping the webcam so the res would be 1080x1920 although the camera is still detected as 1920x1080. If the detection (face landmarks) is done on a flipped image I observed it's less accurate. Would be cool if with this Flop toggle the detection would be done on the 1080x1920 image.
Many thanks,
Joan

Hi @joansc thanks for the kind words 😄
The answer to your questions is - yes you can! Although a little work is needed.
Firstly - MediaPipe was trained on webcam type images at a pretty low resolution (most are 256x256, some are 512x512), so in order for it to work well and get the best tracking, the input images need to be approximately the same shape and size. I fixed it at 1280x720 as that seems like a good compromise between useable output and not too much bigger than the source images.
If you want to use 2K or 4K or whatever size camera images you can also do that using the "Virtual webcam" chain in the example project, although when I was looking at it yesterday I realised it needed a bit of modification to do what you are talking about. I pushed some changes to the example project that will be in the next release to make it easier to use, but the general idea is:

Pull your webcam into TouchDesigner via a VideoDevice In TOP
Fork the output to 2 nodes:

Node 1 resizes to 720p and then sends to SyphonSpout Out
Node 2 feeds into the cache TOP to delay it to match the output of the MediaPipe component.

You then run SpoutCam (or OBS if you're on Mac, sorry, it's more complicated) to receive the 720p Spout stream and present it to MediaPipe as a virtual webcam.
MediaPipe can then process a 720p video that it is expecting, and you can use the output of the Cache TOP to re-sync the MediaPipe data with your original video feed.
Once your original camera feed and the MediaPipe data is synchronised back up, you can then crop/rotate/flip/flop the image and data however you want.

Thanks for the detailed response @domisjustanumber !! Unfortunately, I am not considering using the "virtual webcam" chain because from tests I have done so far in different computers (NVIDIA rtx and so on), SpoutCam introduces a delay of about 250ms between the detection and the camera image that makes AR filters not usable. This delay is not happening when accessing the camera directly from javascript. That's why I was wondering if all these changes could be done from the js code...
Thanks for your time,
Joan

Hmm that's interesting. On my Windows machine I'm only getting a 1 frame delay with SpoutCam (MediaPipe adds another 3 frame minimum, plus processing time. On something like an RTX 3070 the processing time is usually less than 1 frame, so a total of <4 frames latency on the whole setup.
If you're seeing 250ms of delay with SpoutCam, I'd make sure you have the latest versions (or maybe it gets slowed down by CPU load?)

mmm interesting, gonna reply you back in the next days with some further testing on my side. Thanks!


Fix 3387

coverage: 92.868%. remained the same
when pulling 37a4ea715cd49c9993e42330ced211a1e0e91707 on antgonza:fix-3387
into 28d719157cfcf68ee8a35596287a332d425ca7dd on qiita-spots:dev.


update package

update some packages to fix security issues
details

Package
Affected versions
Patched versions
Overview

ini
< 1.3.6
1.3.6
The ini npm package before version 1.3.6 has a Prototype Pollution vulnerability.If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.

normalize-url
>= 4.3.0, < 4.5.1
4.5.1
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.

tar
>= 4.0.0, < 4.4.15
4.4.15
Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution

tar
>= 6.0.0, < 6.1.2
6.1.2

bl
< 1.2.3
1.2.3
A buffer over-read vulnerability exists in bl <4.0.3, <3.0.1, <2.2.1, and <1.2.3 which could allow an attacker to supply user input (even typed) that if it ends up in consume() argument and can become negative, the BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls.

realted this issue https://github.com/nodegit/nodegit/issues/1854

@ianhattendorf  @implausible  @weedz

@ianhattendorf @implausible @weedz
can you help me to check this pr?

Not a maintainer but can confirm things seems to work after updating all dependencies to the latest version, including node-pre-gyp to @mapbox/node-pre-gyp and babel-cli to @babel/cli.


Added grho: git reset --hard origin/$(current_branch)

+1
@autodidacticon You fixed typo in PR name but it remains in the commit message.

@vgaidarji Good catch.

I would vote for this feature +100 as probably I'm not the one who uses this command on daily basis.

@ncanceill

It's now groh.


Fixed issue with wrong locale under Java 9.

This PR fixes the problem with the wrong language in the language selection dialog under Java 9+. The flag was correct, but the language was always 'English'.

It seems the JDK 6 build on Travis is broken. This probably hasn't been caused by your change, but some change in the infrastructure.
After searching for the cause of

Received fatal alert: protocol_version
it seems there has to be introduced a JVM option -Dhttps.protocols=TLSv1.2 for that particular JDK. Can you give it a try.

I commit a change in .travis.yml directly to the master branch - you may try to merge it to your PR and retry the build, or modify it according to your needs.

The issue with JDK 6 persists :-(

The issue with JDK 6 persists :-(
Not sure if the problem is that the JAVA_OPTS is defined already. Are you sure to not use MAVEN_OPTS?

I saw it. JAVA_OPTS is defined but it can be overridden in the matrix. I'm not dealing with Travis every day, but I'll try my best to help with this.

@rkrell It passes now. Thank you for fixing this.

@rkrell Not sure if I get you right (Sunday morning ...  :simple_smile: ) but the null check is inside the isEmpty():
private boolean isEmpty(String var)
{
   return (var == null || var.isEmpty());
}

Thanks for finally solving this hopefully last showstopper for newer JDKs.


Inline tooltip

Hi there,
When creating our MJML plugin for SublimeLinter, I was really confused about the lack of a tooltip feature. I'm neither a Sublime Text User, and a Python programmer, so i'll need some help to finish this, but I have an early prototype using the Sublime Text Tooltip API : http://derniercri.d.pr/1lIFJ/4azXvKfE
TODO

[x] Theme support
[x] Disable/Enable Tooltip
[x] Display tooltips
[ ] Tests?
[ ] User Theme?

Can you check this PR and give me some advice to make this feature available for everyone ?

+1, must have feature

Sorry for your wait! Please correct the issues failing the build, and I will merge.

Why don't you provide the HTML in .tooltip-theme file directly? I see no benefit in separating the indicator from the template content.
Also, you should probably be using rem units for font sizes, which are relative to the standard font size for views, instead of looking up a (initially hardcoded) tooltip_fontsize setting, which needs to be adjusted by each user.

This looks great. What is the status of this?
I pulled the tooltip changes and merged them with a fork of the master. Everything looks good and is working like a charm.

This looks great. What is the status of this?
I pulled the tooltip changes and merged them with a fork of the master. Everything looks good and is working like a charm.

@averypfeiffer  according to https://travis-ci.org/SublimeLinter/SublimeLinter3/jobs/168357190 some indentation issues due to invalid flake8 styling, besides i dont belive its gonna get through, look at @FichteFoll last comment

@averypfeiffer  according to https://travis-ci.org/SublimeLinter/SublimeLinter3/jobs/168357190 some indentation issues due to invalid flake8 styling, besides i dont belive its gonna get through, look at @FichteFoll last comment

@alvarolm I don't have any more say in this than you, technically, since I'm just a user myself. I also have a long todo list, which is why I still haven't been able to take a look at this yet and most likely won't for the next few weeks either, at least.
The current blocker I see is CI failing.

@alvarolm I don't have any more say in this than you, technically, since I'm just a user myself. I also have a long todo list, which is why I still haven't been able to take a look at this yet and most likely won't for the next few weeks either, at least.
The current blocker I see is CI failing.

@FichteFoll Well anything I can do to help it get pushed through?
I gotta say, now that I am use to the tool-tips, they are pretty convenient.  It allows complete customization. @alvarolm if you want to check it out, you can pull down my fork and see what I mean.

@FichteFoll sorry, got confused.

Hey, got to this PR from #504 (hoping for a release so I can get that feature!). Are we just waiting for linting fixes on this? I'd be happy to just push a diff if that helps move things along.

I'm back from holidays i'll take a look to fix everything for this week sorry about the delay

@iRyusa pleeeeeeeeease =)

@outpunk : I've started to tweak some few things from @FichteFoll I should be able to commit it by the end of the week

@iRyusa Any update?

@iRyusa thx for continue working on this feature! we all really hope on u!

@iRyusa please find a minute to look at this. This is something that would improve everyone's workflow a lot.

@iRyusa is there something anyone can do to help you so this can be merged? Please let us know.

@iRyusa Echoing @godlevel here.
I'd be in to help speed this along if need be. Where did this get left off?

Hey, I created a new PR at #552 containing @iRyusa 's code with linting fixes to pass the tests. I've also toggled on "allow updates from maintainers" to help get this through.

This was merged in with #552

Thank you for your contribution @iRyusa and everyone involved!


Create IDIR Restricted  user-roles (managed by Heritage Branch)

Ability to create new sites (point, line or polygon feature classes), edit existing data, and delete sites as required so staff can add, review, edit and delete register records.
ACCESS TO THESE FUNCTIONS WILL BE THROUGH IDIR RESTRICTED BY USER-ROLE, MANAGED BY THE HERITAGE BRANCH.
All functions are working, but some of the HRIA  attribute data is not in ARCHES yet. In other words, functionality currently exists in HRIA and Arches, but not 100% in Arches at this point.

Update this ticket to be about defining IDIR user roles.


feat(material-experimental): add harness for mat-drawer

Follow-up from #16695. Adds a separate harness for mat-drawer and has mat-sidenav inherit from it.

Addressed the feedback @mmalerba.


Added Test Suites

This change is

cypress.env.json, line 2 at r5 (raw file):

{
  "TEST_USERNAME": "royalsix",

Should we create/use a user other than your's so we don't risk compromising your account. Maybe we should put these credentials in the CI env vars instead of in the code. That way no account is compromised.

package.json, line 15 at r5 (raw file):

  "private": false,
  "dependencies": {
    "@material-ui/core": "^4.6.1",

Because this is an actual app and not an RCL, I'm thinking that we should leave the @material-ui requirements in the Dependencies not dev/peer like in the RCLs.

package.json, line 22 at r5 (raw file):

    "gitea-react-toolkit": "0.6.6",
    "markdown-translatable": "0.8.1",
    "react": "16.11.0",

We will need react/react-dom in here for the same reason as above with it being an app and not an RCL.

package.json, line 54 at r5 (raw file):

    "style-loader": "^1.0.0"
  },
  "peerDependencies": {

No peer dependencies needed, I don't think. App vs RCL.

babel.config.js, line 8 at r5 (raw file):

	plugins: ['@babel/transform-runtime', ["istanbul", {
		"include": [
			"src/components/**/**.js"

Do we want to include all code (components and core) and not just components?


Doc update

A lightweight documentation about all configuration options.
Merry XMAS! :-)

Merry XMAS to you too.


Allow comments on non-top-level entities.

Currently Huddle supports comments only on rules. It would be good to allow them anywhere, or at least in more places.

Marking this as addressed by #41. We could allow comments elsewhere, but I think this is enough to now.


Example usage doesn't work

The example in the readme: from sageattention import sageattn doesn't actually work. It appears the attention function is actually just called attention, not sageattn.

Thank you for your suggestion! The issue has been resolved.


Remove del from all our dependencies

del can be simply replaced with fs.rm() now that we support Node.js 14 as a minimum.
fs.rm() even has a retry logic for windows builtin similar to del/rimraf.
Packages:

[x] @netlify/zip-it-and-ship-it https://github.com/netlify/zip-it-and-ship-it/pull/1423
[x] @netlify/edge-bundler https://github.com/netlify/edge-bundler/pull/394
[x] @netlify/cache-utils

Done


Causal and non-causal vocal-background separation using ConvTasNet

This is the recipe to run the lyrics/accompaniment separtion models

@jonbarker68 any idea what can be the best way to test this?

Add Model to CAD2 branch


Automatically publish maven central deployments

Artifacts are automatically deployed but currently require me to officially publish them to the maven repository. Should use the official maven deployment plugin. might just remove the GitHub deployment as it is basically useless garbage

Probably not going to do this as I don't want to scour through documentation for ages again


Add rel="noopener" when linking to images

We're using target="_blank" to open images in a new window. There are known issues with being able to exploit such links using `window.opener' (https://mathiasbynens.github.io/rel-noopener/)
Whilst the images are probably going to be hosted within the same repo and under our control, we can't really guarantee it. Adding rel="noopener" is not detrimental, so let's play it safe.

Is it worth including noreferrer too? noopener isn't supported in a fair chunk of browsers.

Good call. It's not like the images are going to have analytics tracking on them.


Disable retry

Is there a particular reason for not allowing retry times to be set to zero to completely disable retry?
	if c.Times <= 0 { 		c.Times = 3       }

Since I got no response in the past year I decided to only add the retry runner when Times > 0.


Incorrect image src in zh-cn docs

Describe the issue
Incorrect image src
URL of the docs
https://docs.dapr.io/zh-hans/concepts/overview/
Expected content
https://docs.dapr.io/images/overview-standalone.png
Screenshots

Additional context
Correct image src should not be 'https://docs.dapr.io/images/overview_standalone.png'

@skyao do you mind taking a look at this?

I can fix in technical, but i don't know "HOW TO", dapr docs in Chinese does not write in offical dapr org. You can point me HOW TO, I can fix it as i can.      : )

@hhunter-ms can you close this or remove the good first issue? looks like it was fixed


German Umlaute not displayed in  Tag when using variable at href in Razor Components

Describe the bug
When using a var at href instead of a literal string the umlaute (äüöß) in the text to show is not displayed correctly
To Reproduce
Steps to reproduce the behavior:

Using this version of ASP.NET Core
3.0.100-preview-010184 [C:\Program Files\dotnet\sdk] in Visual Studio 2019 preview 2.2
Run this code

in VS create a Blazor or RC project

in MainLayout.cshtml add:

@functions {         string cLink = "https://docs.microsoft.com/en-us/aspnet/"; }
replace
About
with
äbout

See error

The link reads: äbout
Expected behavior
The link should read: äbout
If you replace the variable with the string in the anchor tag like
äbout
it is displaying correctly.
This was working in VS 17 and core 2.1

A possible solution would be to encapsulate your link text with MarkupString
Example
@(new MarkupString("äbout"))

@sven5
Thank you - works
regards
Uwe

Thanks for contacting us, @uwefms.
@SteveSandersonMS, do we plan to handle this or the MarkupString approach suggested by @sven5 will be the way to go?

Thanks for reporting this!
This is a known issue in the components compiler, which we plan to fix. Your existing markup looks fine and will work as expected once the issue is fixed. Long term, there won't be a need to use MarkupString for this case, though it is a good workaround in the short term.
Closing as duplicate of https://github.com/aspnet/AspNetCore/issues/7147


Schema Deserialization Ignores Field initial-default and write-default Values

Apache Iceberg version
0.8.1 (latest release)
Please describe the bug 🐞
I have a simple Iceberg schema that looks like:
{
  "type": "struct",
  "fields": [
    {
      "id": 1,
      "name": "foo",
      "type": "string",
      "required": false,
      "initial-default": "foo-initial-default",
      "write-default": "foo-write-default"
    }
  ],
  "schema-id": 1
}

If I attempt to deserialize this into a pyiceberg.schema.Schema instance, it ignores the initial-default and write-default attributes:
from pyiceberg.schema import Schema

with open('/tmp/simple_schema.json', 'r') as f:
    s = Schema.model_validate_json(f.read())

print(s.fields)  # prints (NestedField(field_id=1, name='foo', field_type=StringType(), required=False),)
print(s.fields[0].initial_default)  # prints None
print(s.fields[0].write_default)  # prints None

Perhaps this is expected, but looking at the code, it seems like it should work.
If this is indeed a bug (and not expected or user error), I can work on trying to figure out why it is happening and submit a fix.
Willingness to contribute

[X] I can contribute a fix for this bug independently
[X] I would be willing to contribute a fix for this bug with guidance from the Iceberg community
[ ] I cannot contribute a fix for this bug at this time

This might be a simple fix, but I"m not exactly sure why the constructor is structured like it is, so not positive if it breaks some other usage pattern for NestedField:
diff --git a/pyiceberg/types.py b/pyiceberg/types.py
index 8fa7453..0a8c5e6 100644
--- a/pyiceberg/types.py
+++ b/pyiceberg/types.py
@@ -328,8 +328,8 @@ class NestedField(IcebergType):
         data["type"] = data["type"] if "type" in data else field_type
         data["required"] = required
         data["doc"] = doc
-        data["initial-default"] = initial_default
-        data["write-default"] = write_default
+        data["initial-default"] = data['initial-default'] if 'initial-default' in data else initial_default
+        data["write-default"] = data['write-default'] if 'write-default' in data else write_default
         super().__init__(**data)

     def __str__(self) -> str:

But if that seems good, let me know and I can PR it with tests.

Hi @paulcichonski, thanks for reporting this issue! It does indeed seem like a bug, and your proposed fix looks reasonable. Would you be interested in contributing the fix and adding a test to verify the behavior?

@kevinjqliu sure thing, gave it a shot in https://github.com/apache/iceberg-python/pull/1432 .

Thanks for noticing and picking this up right away @paulcichonski 🙌  There is more context around this I'd like to share. Officially this is supported only in V3 and onward (that is not officially released, and not yet supported by PyIceberg). But having the initial values makes it much easier to parse the Iceberg metadata (eg. if a sequence number is missing, we can set an initial default to 0). That said, we have to open up this at some point, we just have to make sure that it is properly tested 👍

Makes sense, I was wondering if it was a v3 thing.


What's the difference with babel-plugin-dotenv-import

Hello,
Can you explain what is the difference between your repo and babel-plugin-dotenv-import and how/why you took over ownership of react-native-dotenv package on npmjs.org ?

Hey @tux-tn I'm going to address it in #18 . Thanks for your question!


allow configurable log_level in msi install

mimic the install_sh convergence strategy to allow a configurable log level, cut the noise from -l debug

Merged as e78541a.  Thanks!!!


How do I start using Xamarin.AndroidSwipeLayout?

When installing the nuget Xamarin.AndroidSwipeLayout I get an error

Project 'xxx' requires the following components installed on your machine:
Xamarin.Android.Support.v4
JavaLibraryReference: https://dl-ssl.google.com/android/repository/android_m2repository_r10.zip-m2repository/com/android/support/support-v4/21.0.3/support-v4-21.0.3.aar-21.0.3
JavaLibraryReference: https://dl-ssl.google.com/android/repository/android_m2repository_r10.zip-m2repository/com/android/support/support-v4/21.0.3/support-v4-21.0.3.aar-21.0.3
AndroidResources: https://dl-ssl.google.com/android/repository/android_m2repository_r10.zip-m2repository/com/android/support/support-v4/21.0.3/support-v4-21.0.3.aar-21.0.3

Then I'm requested to double click to install them:

Please double-click here to install it.

Intallation Errors: XA5209 Unzipping failed. Please download 'https://dl-ssl.google.com/android/repository/android_m2repository_r10.zip:m2repository/com/android/support/support-v4/21.0.3/support-v4-21.0.3.aar' and extract it to the 'C:\Users\myself\AppData\Local\Xamarin\Xamarin.Android.Support.v4\21.0.3\embedded' directory
XA5209 Reason: Could not find a part of the path 'C:\Users\myself\AppData\Local\Xamarin\Xamarin.Android.Support.v4\21.0.3\embedded\aidl'.
XA5207 Please install package: 'Android Support Library' available in SDK installer. Java library file 'C:\Users\myself\AppData\Local\Android\Sdk\extras\android\classes.jar' doesn't exist.
XA5207 Please install package: 'Android Support Library' available in SDK installer. Java library file 'C:\Users\myself\AppData\Local\Android\Sdk\extras\android\libs/internal_impl-21.0.3.jar' doesn't exist.		 	0
Is it possible to create this nuget so no local install isn't needed? Don't know how to autobuild a project with this dependency.

@mronnlun  Could you please provide some more info about the IDE, OS etc that you are using.

No Response so closing


LookupEditor filter using as parameter user fields connected

Dear,
I need to filter the dropdownlist so that only the church appears that is registered with the user, that is, the user can only see his church.
Note: admin user can view all.
picture 1
User Registration, where it was informed which church the user belongs to.

picture 2
view of the dropdownlist bringing all the churches. I would like it to show only the church based on the user.

code
InscritosColumns.cs
 [LookupEditor(typeof(Gerencia.Entities.IgrejaRow)), QuickFilter, Width(200)]         public String IdIgrejaIgrejaNome { get; set; }
admin user can view all churches, here is correct, as shown in the image below.

what should I do to display only the church in the user-based dropdownlist logged in?

@juliermefelix  share ur row.cs code i need to check attribute u applied..
thanx in adv..
Aniket

follows as requested
IgrejaRepository_cs.txt
IgrejaRow_cs.txt
IgrejaLookup_cs.txt

@juliermefelix thank you sir..