text:
feature:添加bkbase内置审批服务

Codecov Report

Merging #192 (cbc56e8) into v2.6.x_develop (847b77d) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           v2.6.x_develop     #192   +/-   ##
===============================================
  Coverage           29.33%   29.33%
===============================================
  Files                   3        3
  Lines                  75       75
===============================================
  Hits                   22       22
  Misses                 53       53

Continue to review full report at Codecov.

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

authors: CodeJamz codecov-commenter

repo: TencentBlueKing/bk-itsm


text:
feat: 优化进度文件数据结构

lgtm

source: gharchive/pull-request

authors: jayjiahua liuwenping

repo: TencentBlueKing/bkunifylogbeat

license: MIT

license_type: permissive

license_source: github-api


text:
feat(backend): dbmodule增加别名

关联研发信息
dev_branch: feat/add-alias-for-dbmodule/#5281
target_branch: v1.4.0

source: gharchive/issue

repo: TencentBlueKing/blueking-dbm


text:
BSC

[ ] # - ~~@dinhtuananhne ~~

repo: Tenderly/node-extensions-library


text:
Crash on flux creation

Good job

authors: Feavy TheBaronMc


text:
Core functionality

We are moving away from NotEye, so this will not be done for a while.

repo: TheBlueRiolu/roguefics


text:
chore: switch from yarn v2 to yarn v1

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

repo: TheDome/DistributionZ


text:
Settings save tess change

Fixes #455

repo: TheJoeFin/Text-Grab


text:
Patch 4

feck


text:
Turn off legend clicks in invisible map (if not enablring major filtering point)

Although this is a good issue to address, we were limited in our abilities to make improvements due to time constrains and decided to fix other issues instead. This is something that could be changed for future improvements.


text:
Suggestions for project topic

Here are some topic ideas: Netflix data set, the World Development Indicator data set by World Bank, daily updated Covid dataset, the happiness dataset and the US police shooting dataset.


text:
YEL-6266 - updating python version

👍

authors: olatunjib s-block

repo: UKHomeOffice/docker-python-kafka-pandas


text:
Create CustomStack.java

Stack is already added. Try adding in some other language.

authors: Umar-Waseem ZapeeoSheikh


text:
Update README.md

Also while opening a PR ,pls add a description of what changes you have made in readme..

if u have any doubt regarding contribution plss ask..ok

@Unnimaya6122004 add link that help for better ui design


text:
Added a decent README.md file

Thank you for this!

authors: Vedabahu pratikpakhale


text:
Upgrade to Grafana 9.0.6

Codecov Report

Merging #34 (f71475a) into main (d79f21b) will not change coverage.
The diff coverage is 50.00%.

@@           Coverage Diff           @@
##             main      #34   +/-   ##
=======================================
  Coverage   55.26%   55.26%
=======================================
  Files          39       39
  Lines         418      418
  Branches       57       57
=======================================
  Hits          231      231
  Misses        172      172
  Partials       15       15

Impacted Files
Coverage Δ

src/components/Config/Config.tsx
100.00% <ø> (ø)

src/constants.ts
100.00% <ø> (ø)

.../volkovlabs-balenasupervisor-datasource/api/api.ts
22.80% <25.00%> (ø)

...-datasource/components/QueryEditor/QueryEditor.tsx
51.61% <100.00%> (ø)

...abs-balenasupervisor-datasource/constants/query.ts
100.00% <100.00%> (ø)

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

authors: codecov-commenter mikhail-vl

repo: VolkovLabs/volkovlabs-balena-app


text:
NOT READY: Qqq resolve

@Sakapoi fix please

authors: Sakapoi Wandalen

repo: Wandalen/wTools

license: mit

license_source: bigquery


text:
bump aie and llvm

Requires https://github.com/Xilinx/mlir-aie/pull/1489

repo: Xilinx/mlir-air


text:
Design the item class

-Finished Item Class and its style checking with PR Chore/item class + all unit tests for item class https://github.com/YC0101/4156FinalProject_ctrlZHeroes/pull/16 reviewed by Yanxi Chen @YC0101

authors: charlhhhh ruanqirui


text:
FIX THE FUCKING WINDOWS BUILD FIRST NOT THE LINUX ONE AAAAAAA

stfu and be patient

why cant yall wait for once jesus christ

authors: ArdoDev-stupid TheKitBoi YoshiCrafter29


text:
Wyujie

bors r+


text:
Delete 404 directory

No


text:
Piccole modifiche alla pagina personale

👷 Deploy Preview for boostlabunipd processing.

Name
Link

🔨 Latest commit
c3e6592613ba6de93c6a412cdc8e0ac4ccd65fe1

🔍 Latest deploy log
https://app.netlify.com/sites/boostlabunipd/deploys/640f9239b4fd440008f612b3


text:
Code review, documentation review and reformualtion

Thank you for the nice work!

authors: aauss stephaneghozzi

repo: aauss/epi-quark


text:
unit tests, update to latest

merging, no ABAP changes, but will get us to zero open pull requests 🎉

repo: abapGit/abapGit


text:
Documentation: Add link to example app, and clarify ARTPushRegistererDelegate usage

Since this is just a README update we don't require that all checks need to be green.

authors: ben-xD lukasz-szyszkowski

repo: ably/ably-cocoa


text:
feat(template-samples): dropdown typecheck and improved loading state with spinners on loading on selection of sampes

review this please @dselman

repo: accordproject/template-playground


text:
Add support for repeated positional options

Thanks for the improvement. Can you fix failing tests? Maybe some test cases don't contain the arg _

Hi, I've removed commits that add traling args. Now this PR should only have add support for repeated options which should pass all of the tests

@dmaretskyi
Thank you for your contribution! It has been released on v0.1.0
https://github.com/acro5piano/structopt/releases/tag/v0.1.0


text:
Release Workflows

Waiting for #35 and #37 to be merged

repo: advanced-security/reusable-workflows


text:
ToDoApp - FullStack - React + SpringBoot

Hi, can i participate?

@Henriquesb-1 Sure

Hi, can you provide the description of issue

repo: ajjayymahato/ToDoApp


text:
added div to search and minor style changes

Branch abandoned due to issues

authors: alexbishopbootcamp trahy

repo: alexbishopbootcamp/music-lyric-player


text:
Mejorar README (del canal de discord)

Quité el label de documentation porque no creo que entre como documentación del repo.


text:
simplify patterns: x*1=x and x+0=x

How much perf gain observed with these simplifications?

How much perf gain observed with these simplifications?

These patterns are used to remove some redundant biasadd (e.g. bias is zero) or pattern like alpha * x * y + beta, where alpha = 1, beta = 0. The performance improvement from the these patterns may not significant. However it can help us to simplify the graph, which in turn enables more opportunities.

authors: minminsun wyzero

repo: alibaba/BladeDISC


text:
bugfix: check targetPath is existed when found no mountpoint

Codecov Report

Merging #71 (f49ffbb) into main (b311163) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #71   +/-   ##
=======================================
  Coverage   10.44%   10.44%
=======================================
  Files          11       11
  Lines        1168     1168
=======================================
  Hits          122      122
  Misses       1043     1043
  Partials        3        3

Flag
Coverage Δ

unittests
10.44% <ø> (ø)

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

Continue to review full report at Codecov.

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

repo: alibaba/open-local


text:
tidevice能测Mac端应用?或者有方案提供

不能测mac端应用。有别的工具可以搜索一下
https://blog.csdn.net/lylfv/article/details/125362368

authors: codeskyblue lycfr

repo: alibaba/taobao-iphone-device


text:
feat: add gradle builder

Nice! However the configuration is still the same for both Maven and Gradle -> list of Goals and Properties, if you look at GradleBuilder, you'll see it's a little awkward how I use the properties, no?

We keep the goals and just pass a List<String> as properties then?
breakbot.yml would look like:
build:
  args: -x test # Gradle
  args: -Dmaven.test.skip # maven

For gradle it would be OK I guess but for the YAML IIUC it would be
build:
  goals: ['toto', 'foo']
  args: ['-x', 'test'] # Gradle
  args: ['-Dmaven.test.skip'] # maven

The quotes aren't needed (even for stuff like -x surprisingly), but indeed these should be arrays! Alright, I'll implement that.

authors: jrfaller tdegueul

repo: alien-tools/maracas


text:
[FIX] Use stable sort for all argsort in Alpa

Temporary fix of #752

repo: alpa-projects/alpa


text:
Release/1.1

Hello @alshapton! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file pyntel4004/src/disassembler/disassemble.py:

Line 14:63: E203 whitespace before ','
Line 14:76: E261 at least two spaces before inline comment

In the file pyntel4004/src/executer/execute.py:

Line 17:77: E203 whitespace before ','
Line 17:91: E261 at least two spaces before inline comment

closed


text:
add low prio rayon thread pool

doing this with tokio instead :)

repo: andrewgazelka/hyperion


text:
Feat/add release checklist

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

Comparison is base (c99e426) 92.11% compared to head (ba77a68) 92.11%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #427   +/-   ##
=======================================
  Coverage   92.11%   92.11%
=======================================
  Files          49       49
  Lines        3298     3298
=======================================
  Hits         3038     3038
  Misses        260      260

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

authors: codecov-commenter janvonrickenbach

repo: ansys/pydpf-composites


text:
extended_net.shunt_rlc

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

Project coverage is 83.02%. Comparing base (f222258) to head (c3d99e2).
Report is 15 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #223      +/-   ##
==========================================
+ Coverage   82.79%   83.02%   +0.23%
==========================================
  Files         104      105       +1
  Lines       17716    17605     -111
==========================================
- Hits        14668    14617      -51
+ Misses       3048     2988      -60

repo: ansys/pyedb


text:
shadow swimming in low resolution shadowmap

This is not a bug! The reason is because  sampler2DShadow has another param z.

repo: ant-galaxy/oasis-engine


text:
Anomaly Detection using Gaussian Distribution in MATLAB

Sure @KayJey Go Ahead ✨


text:
(refactor) some opportunities to use Switch String

Please see my comment to you in #155  - this type of refactor is rarely desirable, and needs to go through JIRA. We have docs on how to contribute, and opening this type of pull request is not generally useful.

Given this is 5 years old and without ticket I am closing this PR. Feel free to raise this in mailing list or file a ticket etc.

authors: desmorto jeffjirsa smiklosovic

repo: apache/cassandra


text:
HADOOP-18207. (ADDENDUM) Fix TestRouterNamenodeMonitoring

@hchaverri @goiri could you please review this PR?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 34s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 39s

trunk passed

+1 :green_heart:
compile
0m 40s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
0m 38s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
0m 35s

trunk passed

+1 :green_heart:
mvnsite
0m 42s

trunk passed

+1 :green_heart:
javadoc
0m 49s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 32s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
1m 30s

trunk passed

+1 :green_heart:
shadedclient
20m 47s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 29s

the patch passed

+1 :green_heart:
compile
0m 32s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
0m 32s

the patch passed

+1 :green_heart:
compile
0m 29s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
0m 29s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 19s

the patch passed

+1 :green_heart:
mvnsite
0m 31s

the patch passed

+1 :green_heart:
javadoc
0m 28s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 23s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
1m 16s

the patch passed

+1 :green_heart:
shadedclient
20m 25s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
20m 47s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

109m 24s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5713/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5713

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 7b28cddaac90 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a9d0061dacfe9fc3de8d1c5fbf1faee1f12e98d0

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5713/1/testReport/

Max. process+thread count
3198 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-rbf U: hadoop-hdfs-project/hadoop-hdfs-rbf

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5713/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

This is no longer required, it's being addressed with PR 5717

authors: hadoop-yetus virajjasani

repo: apache/hadoop


text:
RELEASE v1.6.1-incubating

content/docs/r1.6.1-incubating/_sources/* is unnecessary

content/docs/r1.6.1-incubating/_sources/* is unnecessary

done, also removed content/docs/r1.6.0-incubating/_sources/* .

content/docs/r1.6.1-incubating/_static/locales/bn/LC_MESSAGES/

did you enable i18n when you were building?

I suggest you run make clean before generating the doc

content/docs/r1.6.1-incubating/_static/locales/bn/LC_MESSAGES/

did you enable i18n when you were building?

forget about it, seems generated automatically

repo: apache/incubator-kyuubi-website


text:
util: Add sensitive data mynewt util to hide data in coredumps

Usual way for not including some part of RAM in core dump is to modify hal_bsp.c dump_cfg[] array with regions that should be dumped. In that case array will have more then one region and sensitive data can be put by linker script in some specific area that is not mentioned in dump_cfg.

If I understand this correctly, given that dump_cfg is a whitelist rather than a blacklist, I would need to still put the sensitive data in one area via linker script and attribute, and then include all areas except the sensitive part of RAM in every hal_bsp.c file.
My concern on this is that there is a very large number of hal_bsp.c and more to come in the future as more hardware is supported and custom coredump callbacks used with OS_COREDUMP_CB may not necessarily be able to use this feature out of the box

@kasjer We have been speaking about this and it was my suggestion to look at defining sections instead of adding more code for protected data so that we could generically define data structures and variables in a specified section. It seems to be the best way to make it user friendly. dump_cfg is also good. Though it is little weird to define variables in a region that is not present in dump_cfg. Do you know of an easy to way to do that ?

Considering that you already wanted to add one special section for sensitive data that should not go to core dump
having such function in bsp does what you want with same changes to linker scripts.
const struct hal_bsp_mem_dump *
hal_bsp_core_dump(int *area_cnt)
{
    dump_cfg[0].hbmd_start = &_ram_start;
    dump_cfg[0].hbmd_size = (int)&__mynewt_protected_start - (int)&_ram_start;
    dump_cfg[1].hbmd_start = &__mynewt_protected_end;
    dump_cfg[1].hbmd_size = (int)&_ram_start + RAM_SIZE - (int)&__mynewt_protected_end;

    *area_cnt = 2;
    return dump_cfg;
}

I think some of the reviewers already use such approach and they may have some more insight.

@kasjer We have been speaking about this and it was my suggestion to look at defining sections instead of adding more code for protected data so that we could generically define data structures and variables in a specified section. It seems to be the best way to make it user friendly. dump_cfg is also good. Though it is little weird to define variables in a region that is not present in dump_cfg. Do you know of an easy to way to do that ?

Considering that you already wanted to add one special section for sensitive data that should not go to core dump having such function in bsp does what you want with same changes to linker scripts.
const struct hal_bsp_mem_dump *
hal_bsp_core_dump(int *area_cnt)
{
    dump_cfg[0].hbmd_start = &_ram_start;
    dump_cfg[0].hbmd_size = (int)&__mynewt_protected_start - (int)&_ram_start;
    dump_cfg[1].hbmd_start = &__mynewt_protected_end;
    dump_cfg[1].hbmd_size = (int)&_ram_start + RAM_SIZE - (int)&__mynewt_protected_end;

    *area_cnt = 2;
    return dump_cfg;
}

I think some of the reviewers already use such approach and they may have some more insight.

@kasjer, would this solution cause issues with os_addr_is_ram returning 0 on protected addresses? Also, if variables on the protected ram area are on the stack, wouldn't you still be able to see them on the backtrace

@t3zeng

os_addr_is_ram returning 0, if I am understanding what you are asking , does not seem to be a problem (although I could be wrong). Seems like os_stacktrace is just trying to display text addresses from ram areas that will be in the coredump. The protected data is not in .text so it would not get displayed and thus is not a problem.

Again, assuming I am understanding your question, yes, I guess it is possible that if the protected variables are in registers on the stack they will get displayed in os_fault.c. However, I think a bigger problem is this: if those variables are accessed and they are placed on a stack (a tasks stack, for example) the will get placed in the coredump since the stacks are in ram and will be part of the coredump.

I have gone through some of the code and I think I prefer the approach where the dump_cfg is modified to exclude the protected area but I am not sure I have considered everything yet.

So, I think for protected variables on the stack, there are couple of options, others can comment more on based on their experiences but I can think of the following:

Best bet would be to define them in the mynewt_protected section
Have a protected section per stack somehow, this would need to be done from the linker script with defining dummy sections per stack and updating StackTop, StackLimit, ProtectedStackStart1 and ProtectedStackEnd1 for example and when a trap comes in, clear the individual protected stack sections. Again, this would mean a lot of changes to the existing stuff, so not sure if that is the route we want to take here.
A combined protected section for all stacks and clearing that section (Somewhat same as 1, but easily identifiable with a dedicated section)

There are already sections defined for regions of RAM which users can use to keep things out of coredump, aka storage of secret stuff. These are 'sec_data_core', 'sec_bss_core' and 'sec_bss_nz_core'. Not all users care about this, so it was left for the BSP to define whether these get included in the core or not (dump_cfg, as others have pointed out).
At the moment I'd vote no for adding another section, given that these already exist.
Regarding stack... yes. That can be a problem. General practice is to clobber the local variable which held the secret after use. Which the crypto libraries we include do. One low cost option would be to have a per-task flag which could be set just before secrets are about to be used in stack, and cleared after secret use is done. Then you could decide to either exclude that stack, or clobber (easier) before including it in the core/stacktrace.
With the current implementation we have, if I was really worried about secrets in my use-case, and I was using mynewt, I'd move all the security computations to be done by a single task, and place it's stack in 'sec_bss_core' section. Define dump_cfg to exclude 'sec_XXX'.  And not have OS_CRASH_STACKTRACE set.

There are already sections defined for regions of RAM which users can use to keep things out of coredump, aka storage of secret stuff. These are 'sec_data_core', 'sec_bss_core' and 'sec_bss_nz_core'. Not all users care about this, so it was left for the BSP to define whether these get included in the core or not (dump_cfg, as others have pointed out).
At the moment I'd vote no for adding another section, given that these already exist.
Regarding stack... yes. That can be a problem. General practice is to clobber the local variable which held the secret after use. Which the crypto libraries we include do. One low cost option would be to have a per-task flag which could be set just before secrets are about to be used in stack, and cleared after secret use is done. Then you could decide to either exclude that stack, or clobber (easier) before including it in the core/stacktrace.
With the current implementation we have, if I was really worried about secrets in my use-case, and I was using mynewt, I'd move all the security computations to be done by a single task, and place it's stack in 'sec_bss_core' section. Define dump_cfg to exclude 'sec_XXX'. And not have OS_CRASH_STACKTRACE set.

Thanks for the insight @mkiiskila
While I was looking into sec_data_core  and sec_bss_core  I came across these secret sections as well:sec_data_secret and sec_bss_secret
What is the difference in behavior between these areas?

Ah, yes. I misspoke, those 2 sections were the ones I meant! Thanks @t3zeng for pointing it out. Those 2 sections are meant for storing secret stuff.

So, I guess we do not need this PR then since it can already be handled in the BSP, so no new section is needed.

I fiddled around with sec_data_secret and looking at the memory map, it doesn't appear to move variables anywhere. Looking at the code, this seems to make sense as I don't see the macro push data to any sections nor does there seem to be areas in the linker script (eg. apache-mynewt-core/hw/mcu/nordic/nrf5340/nrf5340.ld) for secret variables to pass to dump_cfg.
Based on what I'm seeing, it looks like the intended use case is to:

add a custom area to the linker script myself
define sec_data_secret as that area in bsp.h
Update dump_cfg so that coredumps capture around the protected memory area
Add an API call to os_default_irq to clobber variables in sensitive area so that the stack doesn't show the values

Would that be correct?

Thanks for looking over this. Yes for 1-3, no for 4. The linker script indeed is where you'd insert symbols around secret data and secret bss areas, and then take those into account within dump_cfg.
Both of those items are under BSP control; we have not had an example of this being done within the BSPs in the trees, and (as you've discovered) is not specifically called out in the documentation.
Which leaves us with item #4. I have not done anything for this as I considered the risk to be small'ish. My reasoning was that a) probability of crashing during computation when secret was being used is low and b) raw secret would be held in the areas not included in coredump, and what is in the stack is only small parts of it (4 bytes in reg) and data which has been obfuscated by going (partly) through security algo.
So there is a bit of  possibility peephole. One could argue that if you can induce crashes at specific times AND get your hands on corefiles OR stacktrace appearing on the console, then you could re-construct the secret from pieces. This might be unacceptable for some use cases.
If you (or someone else?) is interested in plugging this hole, I suspect that would help some users!

Also, adding documention about the current way of doing things would be liked by many. Even modifying a BSP to demonstrate this use would be nice.

One of the points of having coredump is to see stack for tasks. If stack data is a security concern, stack itself can be put in crash-excluded area instead of destroying it, so I also don't see benefit of 4.

The stack is still useful to have but depending on where you crash it's possible to put protected data onto the stack. In cases like these you don't want to exclude the entire stack, it would be better to see it as normal for debugging purposes but with sensitive data like keys clobbered. Hiding the entire stack in a crash excluded area would mitigate a lot of the benefits of coredumps

repo: apache/mynewt-core


text:
chore: redis postProvision and preTerminate support retryPolicy

/cherry-pick release-0.9

repo: apecloud/kubeblocks-addons


text:
Add a statistics TBD to show level of knowledge of a set

The overall grade can be based on the percentage of cards in each filter. So the scores will be: Good-5, Minor-4, Medium-2, Non-0. The total score between 0 and 5 weighted by the percentage of cards in each filtered list.

There can also be a more detailed statistics as well as showing the change over time.


text:
Rename TinyArray.append benchmark

TWIMC, for posterity, colons in file names break on Windows.

authors: FranzBusch MaxDesiatov

repo: apple/swift-certificates


text:
FileManager

Implemented with https://github.com/apple/swift-foundation/pull/410

repo: apple/swift-foundation


text:
[embedded] Resolve empty -sdk path warning in embedded stdlib build, take 3

@swift-ci please test

@swift-ci please test

repo: apple/swift


text:
Remove assertions from preempting_queue_scheduler.go

I think you could also remove NodeJobDiff from NodeDb now - as you are removing the only place it is called

repo: armadaproject/armada


text:
compsgh-162 change generic input output

Uploaded ExampleFiles/ComposGH_Example_BS_01.gh on purpose?

Yes I replaced all existing components with new ones as the custom input/output parameter are stored in the components, so the work of this PR was not in the example/test file

repo: arup-group/Compos-Grasshopper


text:
fix: make tool of run_binary cfg=exec

Does this match upstream?

Upstream is "host"

repo: aspect-build/bazel-lib


text:
Adding VSTS file

It appears that tests fail on VSTS due to timeouts. I need a SME to look into it, @ajaybhargavb is that you? If not I have no clue who as most of the commits to this repo are automated.

I looked at the failure and unfortunately I have no clue what it's about. Maybe @kichalla could help.

@ajcvickers can we get someone from the EF team to look at this? It seems to be issues related to database logins and whatnot. Is there a prerequisite we're maybe missing (if so this scenario should make better error messages)?

@smitpatel Can you take a look at this?

The possible root cause of failures here, localdb instance is not running when testing starts so initial tests fail. But once the instance is running, all tests would start passing.

We have hit issues similar to this in the past when the machine/VM that is running the tests is too slow for SQL Server to startup in a reasonable time. Do we know what kind of machine is being used here?

Judging by other issues we've been running into I'm assuming the machines are pretty slow and possibly single-core. This is to be expected since we're using the lowest tier of hosted machines for now, but I also see it as an opportunity to ensure our product/test/build works on more modest setups unlike the beefy machines we usually use to test.
When this has happened in the past what was the resolution? Should we poll for SqlServer being in a ready state, or is there a "launch SqlServer and only return once it's in a ready state" command that we can run before build.cmd|sh?

sqllocaldb start command should start the default instance (which we use in testing anyway). Unsure if the command is in the path. Can you try it out if its easy to test?

@ryanbrandenburg In the past the resolution has been to use faster machines. It's a laudable goal to say we should be able to run our tests on modest setups,, but if one of the main things we depend on--that is, SQL Server Localdb--cannot run reliably on modest setups then to achieve this goal we would need to move away from using that dependency. That is something we have considered--for example, using SQLite for most testing--but that obviously impacts many things, so the motivation for doing so would have to be very strong.
Alternately, if the @smitpatel's idea pans out, then that might help.

Looks like @smitpatel's suggestion took care of it. The remaining failures are problems with dependencies.

authors: ajaybhargavb ajcvickers ryanbrandenburg smitpatel

repo: aspnet/Diagnostics


text:
Correct hyperlink to synergy data in project set-up

Thanks!

repo: asreview/asreview


text:
Support for Google Drive as File source

A few thoughts from initial observations and investigations:

Airflow’s GoogleDriveHook is pretty lacking at the moment[^1]. So we either need to contribute to that first, or just roll our own implementation in the SDK.
There’s a new Python package called fsspec that provides file API for Google Drive (and some other storages). It is gaining populatiry recently.
We are currently using smart_open, which lacks Google Drive support. So we need to implement a custom transport for it.
But fsspec actully can also do open, so it’s entirely possible to replace smart_open with fsspec for our purposes. And since fsspec has built-in Google Drive support, we’ll be able to add it more easily.

I’m wondering how it’s best to approach this. We can either replace smart_open with fsspec, or implement a custom smart_open transport. If we decide to go with the latter, we can also try to implement the custom transport directly with Google API client, or add fsspec as a dependency.
[^1]: Currently only methods to check, read, and write a file.

I took a look at fsspec’s Google Drive implementation and it seems easy enough to just use the API client, so I’m going to do that for now.
I wonder if there’s a good way to test the classes. A Moto equivalent for googleapiclient would be useful…

PR to add the file location has been created (see ref link above)

authors: kaxil uranusjr

repo: astronomer/astro-sdk


text:
Database

Postgres by Flask-SQL-Alchemy

Tables:
Character
import from react class
user id
campaign array - campaign ids
Users
id
username
password
Campaign
id
password
DM: user ID
Characters array - character ids
Notes:
id
Title
text
user id
campaign id
many to many tables:
campaign_character
campaign id
character id
campaign_user
campaign id
user id
many to many : campaign to character
many to many: campaign to user
one to many: user to character
one to many: user to notes
one to many: campaign to notes


text:
Add Tools & ToolCalls

Awesome! 👏
Thanks for your contribution!

authors: awaescher mili-tan

repo: awaescher/OllamaSharp


text:
Stop support for 1.19

PRs:

#1152
#1153
aws/eks-distro-prow-jobs#332

repo: aws/eks-distro


text:
ci: allow clippy to run on modified code when linting

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

Project coverage is 93.62%. Comparing base (1761b73) to head (f174f26).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #117   +/-   ##
=======================================
  Coverage   93.62%   93.62%
=======================================
  Files          49       49
  Lines        2791     2791
=======================================
  Hits         2613     2613
  Misses        178      178

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

authors: codecov-commenter milapsheth

repo: axelarnetwork/axelar-cgp-soroban


text:
Replace README with link to the docs

I suggest leaving the readme intact and linking it to the docs as an addition. There are a few important things to that.

in the rust ecosystem, it's pretty common to discover over crates.io; crates without a readme are mostly discarded and not considered.
this will also affect docs.rs, so people will now have to go to two places to find docs to the crate
it removes documentation from the integration. The language server and API plugins integrate directly with docs.rs
it makes updating the documentation harder as now updates need to be made in sync.

perhaps replace the first section

With a link to our axiom.co  docs but leave the quickstart and features in here?

authors: Licenser tothmano

repo: axiomhq/axiom-rs


text:
Selection Sort Code in java

Sorry for the #7 issue, did by mistake


text:
Test the Searching Page/Feature for any Possible Bugs or Potential Errors

No errors from testing. More testing would be great but as far as I can see, everything is working.

repo: ayanahye/PlantSnap


text:
Update spelling_action.yml

Spelling and url actions will fail on main, but this will help test for develop and manual workflows

repo: bandframework/bandframework


text:
SSO process runthrough with ADMS Team.

@ThibaultBC, @wrnu @prabhukiran9999 have attended the meeting with ADMS, Explained the current SSO architecture we have in mind, and explained the permissions required to meet the requirements.
The ADMS team will review the requirements and reply in a week. Closing the ticket and start work on a new ticket based on the response from the ADMS team.

repo: bcgov/cloud-pathfinder


text:
minor script update

closed due to no activity

repo: bcnmy/scw-contracts


text:
level 1 screen with no game functionality

Code reviewed as a team, no issues noted as this is the first merge and the codebase is still small

authors: beansighe ruspedpdx

repo: beansighe/PORTaLAND


text:
Data Set on Chilean Undersecretaries (1990-2022) (Version 2.0.0 -- Shy Mud)

Ok.


text:
download-agency should look in configured dirs for metadata

Hi @newsroomdev I can't merge this PR without a review, just a one line change thanks in advance!

repo: biglocalnews/clean-scraper


text:
Use jotai state management library

Use fix instead of feat
feat: fix state loss

repo: bios-bunda-mulia-university/himabios


text:
Argo application is down

The application is up, though the ssl cert is not valid. To access it, HSTS needs to be disabled on chrome.
https://sectigostore.com/blog/how-to-disable-hsts-in-chrome-firefox/

In addition to the invalid certificate I saw 503 errors.

repo: biosimulations/biosimulations


text:
Add spanish translation to assumeutxo

Thank you @BlueeeMoon! For your future translations you don't need to have the aliases field when you are creating a new file.

authors: BlueeeMoon kouloumos

repo: bitcointranscripts/bitcointranscripts


text:
Fix the filter menu position issue on mobile app

Pull Request Test Coverage Report for Build 4360437848

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 100.0%

Totals

Change from base Build 4352677253:
0.0%

Covered Lines:
1021

Relevant Lines:
1021

💛  - Coveralls

authors: aidewoode coveralls


text:
ElasticNet_StandardScaler_PolynomialFeatures.ipynb added

the approach has issue
you have performed StandardScaler twice
first on train and test set
then again inside the pipeline code
ss = StandardScaler()
X_train = ss.fit_transform(X_train)
X_test = ss.transform(X_test)
Remove above mentioned lines of code

sorry, i will rectify it

repo: blobcity/ai-seed


text:
Add spread-luminance property for DDS HDR formats to the UI.

This was a completed task from the board view. Closing as complete.

repo: bluescan/tacentview

license: ISC


text:
Apply workaround for apparent TCL "openssl" changes (especially with regards to "/etc/ssl")

For some context, it would appear that TCL's openssl package has changed out from under us and now requires a little bit of additional setup after it's extracted (which I'm guessing TCL's package manager would've handled automatically for us, but we get to apply manually).
This fixes the following when attempting to pull images on recent builds:
docker: Error while pulling image: Get https://index.docker.io/v1/repositories/library/alpine/images: x509: failed to load system roots and no roots provided.

Updated the comments to be a bit more clear and to include some testing to ensure it's actually doing what it's supposed to.

(Currently doing another test build to ensure it's working 100% properly before I merge and rebuild official v1.12.2-rc1 ISOs.)

Success!
docker@boot2docker:~$ docker run -it --rm alpine sh
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
c0cb142e4345: Pull complete
Digest: sha256:ca7b185775966003d38ccbd9bba822fb570766e4bb69292ac23490f36f8a742e
Status: Downloaded newer image for alpine:latest
/ #

Blergh, thanks for taking care of this.

authors: nathanleclaire tianon


text:
Bump git version 2.6.2

Sorry I didn't saw this PR. This is already in master

repo: boxen/puppet-git


text:
add option to Gensim embedding wrapper to remove punctuation

done

repo: brain-score/language


text:
setup linting

Running a linter works now, but current linting score is very poor, so the check fails

Did we want to combine this with black and/or autopep8 for automatic cleanup?

I think it would be great if we could add black/autopep8, but would see that as a separate PR -- @benlipkin @kvfairchild do either of you have experience with running these automatically?

Not sure about the latter, but there's an official Actions integration for black

authors: kvfairchild mschrimpf


text:
Add python deps

de862e5

repo: broadinstitute/cpg


text:
Update action summary and add screenshot

yeah, I will merge this and then you can update the screenshot

repo: bufbuild/buf-action


text:
Integrate MathJax

Actually, do I want to use MathJax? Could the vertical lines be a bad idea for people who don't know about conditional probability?

Yeah, I'm going to close this pull request.


text:
Fix duplicate vector init in wasm_module_validate

LGTM

repo: bytecodealliance/wasm-micro-runtime


text:
update Kotlin Gradle plugin version to 1.5.20

For the god sake merge this fucking PR.

authors: farhadrazzaghi sajadspeed

repo: cafebazaar/react-native-poolakey


text:
461 numbering questions results page

Hi @Ancentury; numbering looks to be working well. But there remains a spacing issue which is described in ticket #461.
There's a space between the question and the answer for questions 1, 2, 4, 5, 6, but not for questions 3 and 7. A difference between TextResult and the MultiChoiceResult ?  We would like to answer to be close to the question.
Good:

Question 1
Answer1
Question 2
Answer2

Bad:

Question 1
Answer1
Question 2
Answer 2

@MrDeshaies Fixed. Please check again. Thanks.

authors: Ancentury MrDeshaies

repo: canada-ca/aia-eia-js


text:
bump package version to 0.0.9

https://github.com/canonical/charmed-kubeflow-chisme#publishing-to-pypi
time to try :D

authors: beliaev-maksim ca-scribner

repo: canonical/charmed-kubeflow-chisme


text:
VS2022 preview axmal file error

@programClown You can post the issue on Avalonia project if you have XAML previewer issue in Visual Studio. We don't use XAML previewer even Visual Studio to develop PixelViewer in most cases.

repo: carina-studio/PixelViewer


text:
Download a gist

241d9a4797b223043e35bd5747f7bce0ac4f1850

repo: carlocardella/vscode-VirtualGists


text:
feat: add gio endpoint doc & update definitions

please update the changelog as well.

authors: alexmikhalevich vfusco

repo: cartesi/openapi-interfaces


text:
Add pagination to /inscriptions

Actually yours was earlier, I didn't remember that we already had an issue for this. Feel free to ping duplicate issues and I'll close them.

repo: casey/ord


text:
Add WebStorm EAP Cask

Doesn’t this need this fix?

Fixed.

authors: vitorgalvao zchee

repo: caskroom/homebrew-versions


text:
Add node endpoint to return contract generated events

Probably no longer needed since you can get the messages checksum via a global state query. Messages themselves are emitted via SSE.
cc: @SaiProServ

Closing the issue @rafal-ch

authors: RitaMAllenCA SaiProServ rafal-ch

repo: casper-network/roadmap


text:
Tie membership program to mailchimp to provide signees a complementary waiver to open bar

Done!


text:
add bulk download output name

Does this cover the "result.zip"  -> ".tar.gz" instance as well?

Does this cover the "result.zip" -> ".tar.gz" instance as well?

I'm not sure whether I need to, since (as was news to me) tar -xzvf result.zip works

repo: chanzuckerberg/czid-platformics


text:
can't update database property name

fixed in PR https://github.com/chojnac/NotionSwift/pull/46

repo: chojnac/NotionSwift


text:
Allow control to be chosen by shapes

So if we forget the advanced controls, there is just one simple rule:
* **All nodes with a box shape will be added to the Controller**
  This will match the box shapes in the controller.
  It would be easy for the users to understand and remember this setting.

No thanks. My default is Box shapes for ALL nodes. I dont want all of the controls added just because of my workflow.
Same for "colors" really. This should be a key combo that triggers a menu item (add to controller).
It would be much better to NOT hijack UI to use for populating other things, unless the node is marked to do so.
Why? Lots of reasons, like I said with the shapes, some people have color-blindness problems.

It would be much better to NOT hijack UI to use for populating other things, unless the node is marked to do so.

Yeah, maybe that would be the best solution.
@chrisgoringe, Could you reconsider this ?
We could have an option to add to controller in the node's right click menu.
And the nodes could have an icon, in the top right corner, or something, to visually indicate they were added to the Controller.

Yeah, I think you've convinced me.
The idea behind (re)using colors was that we could have more than one panel. But that functionality is now down (much better) with the groups.
I'll do a right-click menu.

authors: Amorano JorgeR81 chrisgoringe

repo: chrisgoringe/cg-controller


text:
Bump workflow actions

Will fix test failures in another PR.

repo: christophebedard/tag-version-commit


text:
WIP: test cli bump

/ci-e2e

/ci-ipsec-e2e

/ci-ipsec-e2e

/ci-e2e

/ci-e2e

/ci-ipsec-e2e

/ci-ipsec-e2e

/ci-e2e

/ci-e2e

/ci-ipsec-e2e

repo: cilium/cilium


text:
Adding the web

closes #19

repo: cityuseattle/CybersecurityClub


text:
Pickup lambda mod 140 for TF 1.1x compatibility

Hello, I'd like to use this module in an existing terraform project of mine that is on terraform v1.1.x. I found that the dependent lambda module had newer tags and if I pulled that tag I was able to run a successful plan. The problem before was that the 1.1.x versions of terraform don't support the "list" function, but rather now use the "toList" function. Here's the errors I got from running the plan using the published module. But when I hacked the local instance of the module under .terraform to pull the 1.4.0 version of the dependent lambda module, it worked.
terraform validate
╷
│ Error: Error in function call
│
│   on .terraform/modules/ss_asg.instance_alarms.lambda/iam.tf line 10, in data "aws_iam_policy_document" "assume_role":
│   10:       identifiers = slice(list("lambda.amazonaws.com", "edgelambda.amazonaws.com"), 0, var.lambda_at_edge ? 2 : 1)
│
│ Call to function "list" failed: the "list" function was deprecated in Terraform v0.12 and is no longer available; use tolist([ ... ]) syntax to write a literal list.
╵
╷
│ Error: Error in function call
│
│   on .terraform/modules/ss_asg.instance_alarms.lambda/iam.tf line 26, in locals:
│   26:   log_group_arns            = slice(list(local.lambda_log_group_arn, local.lambda_edge_log_group_arn), 0, var.lambda_at_edge ? 2 : 1)
│     ├────────────────
│     │ local.lambda_edge_log_group_arn is a string, known only after apply
│     │ local.lambda_log_group_arn is a string, known only after apply
│
│ Call to function "list" failed: the "list" function was deprecated in Terraform v0.12 and is no longer available; use tolist([ ... ]) syntax to write a literal list.


text:
ci: restrict test artifact download

/ok-to-merge

authors: jsilvela leonardoce

repo: cloudnative-pg/cloudnative-pg


text:
Modeling Document

Updated Modeling Document.

repo: code-logik/the-willow-tree-oms


text:
Add keynote 2 to Youtube channel

Keynote 2 did not exist

repo: codeforraleigh/CityCampNC


text:
Bump events v1.5.5 cap cr 8705

Codecov Report

Merging #200 (280ce0e) into main (d293916) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #200   +/-   ##
=======================================
  Coverage   25.13%   25.13%
=======================================
  Files           1        1
  Lines         187      187
=======================================
  Hits           47       47
  Misses        134      134
  Partials        6        6

Continue to review full report at Codecov.

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

authors: codecov-commenter roi-codefresh


text:
Update links to Docs site in CoC

Thanks 😊

repo: community/community


text:
check if saved application exists

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

authors: ch-code-analysis sardhani-ch

repo: companieshouse/acsp-web


text:
consider combining starship.yaml and config.yaml into one

Actually this makes the most sense. We can have:
name: <helmName>
version: <helmVersion>

chains:
- ...

Here i would say we should rename everything so that we dont have helm<xyz> instead make it simpler and to the point.
Non-required options could also include:
name: <helmName>
version: <helmVersion>
repo: <helmRepo> # optional
chart: <helmChart> # optional

chains:
- ...

@pyramation, maybe we should just add name and version to the config file.
The other params, can just be used as default values for most part. And for some cases will be dependent on the environment, so should be anyways passed as arguments to override defaults.
--helmNamespace
--helmRepo
--helmRepoUrl
--helmChart

This would be true for 99% of the cases.
Only in cases where someone has actually forked the starship repo, and want to use that instead of the default one, is there params like: helmRepo, helmRepoUrl, helmChart need to be defined.
Namespace is something that is dependent on the underlying cluster itself, so need not be explicit. Only in cases where you want to deploy to a namespace not selected first by the kubectl itself, is when this is needed. Again for rare cases.

so we'd have --name, --repo, --repoUrl, and --chart?
Seems nice and slick — additionally from what I recall, we can set defaults in starshipjs so these would be optional

Exactly.

OHHH this is slick! love it

repo: cosmology-tech/starship


text:
disable group by on reducer optimization for partitioned tables

ack

authors: bogensberger mfussenegger

repo: crate/crate


text:
Add tips about Cronos public RPCs integrations

/staging

repo: crypto-org-chain/cronos-docs


text:
Add a way to specify global values used in the gen framework

Currently, in PR #398 we modify gen parameters as follows:
[globals.flopoco]
conf = "frequency=800 ..."

We use this configuration file by running filament with the --gen-config /path/to/conf.toml argument.
This allows us to insert whatever values we want into the [globals] tag for the flopoco.toml gen framework file.
This is very nice in some aspects as it allows us to modify multiple different frameworks at once without worrying about namespace collisions and the like. It has some downsides, however:

We cannot specify parameters at a component-level, meaning all instances of a component will have the same gen framework settings
The setting is global, meaning if for some reason one module was built to work at a specific value (For example if we wanted XLS pipeline depth = some value we can hand optimize with), specifying this file elsewhere would break that behavior.
There is no relationship between the globals variables and the output filament, I.E. maybe we would want pipeline depth to actually affect the latency of the component output?
The configuration is in a separate file that we have to include every time we compile

I remember we discussed before the possibility of maybe using something like #[attribute=] notation or something like this to achieve the same behavior, but this might run into some of the namespacing issues we mentioned before.

repo: cucapra/filament


text:
fsusie fix

@gaow I will merge the fix ffor now for bale to test on

repo: cumc/xqtl-pipeline


text:
Return tuple for performance metrics

set display=False

repo: cvxgrp/simulator


text:
feat: add bedrock integration

moved to #75 (Merged)


text:
add len and getitem to Column

as discussed yesterday, I've removed __getitem__ and added get_value
for some existing methods (e.g. Column.mean), we have dtype at the return value to mean "something of the dtype of the column". I've done the same here - orthogonal to this issue, but we should fine a better way of expressing that

for some existing methods (e.g. Column.mean), we have dtype at the return value to mean "something of the dtype of the column". I've done the same here - orthogonal to this issue, but we should fine a better way of expressing that

Should that use Scalar instead? (or Scalar[dtype] if we want to indicate it is a scalar of the specific dtype)

yeah I like that more. will address in a separate PR though as there's some unrelated methods which would need changing too, so easier to do them all in one go and stay consistent with this PR

authors: MarcoGorelli jorisvandenbossche

repo: data-apis/dataframe-api


text:
JiraConnect: adaptive grid cells for Jira tickets

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-17246

authors: dnillovna skalkin

repo: datagrok-ai/public


text:
Fix load no dash entry on dash url error message

After 3 relaunches of tests failed randomly, don't connected with changes in PR:

repo: datalens-tech/datalens-ui


text:
STAR-1589: Fix typos in bootstrap_test.py

https://jenkins-stargazer.aws.dsinternal.org/job/improve-granularity/7/testReport/dtest-offheap-bti.bootstrap_test/TestBootstrap/ 🆗

repo: datastax/cassandra-dtest


text:
Execute order

Is this a MPSC channel?

Is this a MPSC channel?

It's a MPMC channel, so it can be used as a MPSC channel.

repo: datenlord/Xline


text:
correct mismatched enum

It's my first time contributing to open source, I did not know that I need to fork repo, instead of clone. haha...

It's my first time contributing to open source, I did not know that I need to fork repo, instead of clone. haha...

No worries, we all have been there 😉

Closes #66

@lyra95 would you also like to add a test to your PR? You just have to commit and push your changes and it will show up here.

Ok

I wanted to narrow the test target down to the method ValidateIssuer(), but I could not because  the method is protected in abstract class. Instead, I've added tests that generate tokens and verify them, which triggers the target method.

@lyra95 Thanks for adding the tests, and don’t worry, those are perfectly fine and should be testing the decoding of the token, there are already tests for the equality validator which the Issuer validator uses.

Thanks!

repo: daviddesmet/paseto-dotnet


text:
POC - Connecting Frontend views to scheduling algorithms

front end views for POC complete


text:
Fix typos

thanks!

authors: denisrosset kianmeng

repo: denisrosset/configpile


text:
/runtime/fundamentals/linting_and_formatting/ should link to lint.deno.land

https://github.com/denoland/docs/pull/1212

authors: ry thisisjofrank

repo: denoland/docs


text:
Automatic Setup QA engine in Google Cloud

Pending Spike on running SonarQube on Cloud Run (Serverless)

repo: devonfw/hangar


text:
ci: use dfinity/setup-dfx to install dfx

Thanks @smallstepman!

authors: nathanosdev smallstepman

repo: dfinity/response-verification


text:
vailphoria/heading-duplicate-text-content

@3y3 do not merge it yet

authors: moki vailphoria

repo: diplodoc-platform/transform


text:
hacktoberfest2022

Star the repo and consider giving me a follow ;) thanks


text:
Add version and coverage data retrieval in the badge job

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.87%. Comparing base (db5ff13) to head (d811210).
Report is 3 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #5   +/-   ##
=======================================
  Coverage   99.87%   99.87%
=======================================
  Files           7        7
  Lines         828      828
=======================================
  Hits          827      827
  Misses          1        1

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


text:
Installer CCAF via argoCD sur Coud PI Native (Aurahan)

Premier déploiement effectué sur le cluster Openshift de pi gen 2
Seulement la partie mas-administration, pour commencer. Cet après midi j'enchaine avec le reste des composants de CCAF
Peering avec Hugo Fontaine de Sopra Steria
Redéploiement sur la zone s2, DR

Relancer @titigmr pour kubeconfig

kubeconfig ok

repo: dnum-mi/dso-console


text:
Add EmptyPP

Good! Merged.

repo: dof-studio/freechoice


text:
dojot-module/iotagent-nodejs - Documentation

This task has been done!

authors: bizetti rascaraficci

repo: dojot/dojot


text:
Update package.json

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: donniean/configs


text:
Adding K6 load generator

This should allow us to run some benchmarks. The next step is to support custom script files to enable advanced load generation scenarios (auth, functional tests, ramp up).

repo: dotnet/crank


text:
latest Zanata translation changes in kie-wb-common from 2016-05-04

+1 to merge.

authors: kiereleaseuser manstis

repo: droolsjbpm/kie-wb-common


text:
Improve columns

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

Comparison is base (ce04a89) 100.00% compared to head (9b9f6d7) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #177   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           66        66
  Lines         1532      1526    -6
  Branches       150       149    -1
=========================================
- Hits          1532      1526    -6

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

authors: codecov-commenter durandtibo

repo: durandtibo/flamme


text:
Add is_sklearn_available

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

Project coverage is 100.00%. Comparing base (a22ac09) to head (f464d51).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #234   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           35        35
  Lines          787       796    +9
  Branches        26        27    +1
=========================================
+ Hits           787       796    +9

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

repo: durandtibo/grizz


text:
Fix #300: Stream sync get object responses

@andrewbaxter thank you for the fix, I've been vaguely aware of it

Thanks for the review and merge! :bow:

authors: andrewbaxter durch


text:
Add .editorconfig

Added in 1.2.0.

repo: eckinox/eckinox-cs


text:
Fix identifying non-geographical netcdf fields

 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.

authors: FussyDuck sandorkertesz

repo: ecmwf/climetlab


text:
Remove closed $0 balances from BalanceSheet view

Note: Should make all closed accounts not show up in the TEMPLATE LEVEL not at the CALCULATION LEVEL as it does now. Don't want anything screwing up with comparing start/end balances


text:
filter contract_request by inserted_at

Duplicate of #4300

authors: kiurchv svetavedmed


text:
Update changelog

coverage: 100.0%. remained the same
when pulling 0d142c504e4a19c28bbb6fdb94205e9d4a3eaf31 on update_changelog
into 862f9519644523a8fa173becd55cff4a7c164fff on master.

authors: coveralls elchininet

repo: elchininet/postcss-rtlcss


text:
Include msi dmg and deb artifacts

This is resolved.

repo: eliaspardo/imporTagger


text:
is there a mingw64 version for gcc in window?

I did not try but since it's dynamically linked the dll should work for both MSVC and mingw!

authors: eliemichel getfile

repo: eliemichel/WebGPU-binaries


text:
Use macos-13 in GitHub Actions

Thanks!

repo: embulk/embulk-output-stdout


text:
broker crashes when trying to pub msg to a disconnected client

fixed in #670

repo: emqx/nanomq


text:
Users shoud not be allowed to change their own organisation list

Related to pr #1267

repo: endeavourhealth-discovery/IMDirectory


text:
update labels

Will redo in viem branch


text:
add higress to projects

@phlax Thanks for your adivce, it has been modified.

repo: envoyproxy/envoy-website


text:
Fix error

bors r+

repo: eol-virtuallabx/virtuallabx-edx


text:
WIP Brickit opts

@bobokvsky обрати внимание, пожалуйста, что проверка типизации падает. почини плз


text:
Dzianis makeichyk/issue718

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

repo: equinor/engineering-symbols


text:
Testing/pre commit cleanup

I am unconvinced by the pre-push hook added in commit b3cbbf9. You can try it out by running pre-commit install --hook-type pre-push to install the pre-push hook. Unfortunately it does not progressively output the pytest results. But it does force a pytest run prior to a push going through. I'm not sure if I like it in the end.

repo: eslavich/asdf


text:
Adding en_IE

Thanks!

authors: deirdreobyrne gfwilliams

repo: espruino/BangleApps


text:
Merge   master  :   a version could run test and train stable

I apologize for mistakenly submitting the pull request. I'm still learning how to use GitHub and made an error. Sorry for any inconvenience caused.
Thanks,

repo: eth-siplab/AvatarPoser


text:
main-beta <- epic/popup

:tada: This PR is included in version 3.13.0-beta.4 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: ala-n dshovchko

repo: exadel-inc/esl


text:
Add practice exercise generator

@ErikSchierboom I know there will be a general generator in a couple of week but I'd still like to use this one until the other generator is generally available. Can you please review?

repo: exercism/emacs-lisp


text:
Are you able to validateOn individual fields instead of the entire form?

I think no, but you can create a workaround with validate. What is your use case?

Hey.
First, Thank you Fabian about useful package, modular forms, and ofcourse looking for valibot!
And about question shall to say no it's not possible, you can set validation on different fields and components(e.g. by using props) but they should placed in Form.

Thank you! 💙

And about question shall to say no it's not possible, you can set validation on different fields and components(e.g. by using props) but they should placed in Form.

I don't quite understand what you're trying to tell me.

Hi Fabian,
Thanks. I'll close the issue.

authors: Excelsior2021 araqaee fabian-hiller

repo: fabian-hiller/modular-forms


text:
lets default to using the spring starter dependencies for nice auto configuration in spring boot

[merge]


text:
build(ci): Add breeze build and test job

@Yuhta This fixes a number of build issues in breeze and introduces CI jobs to build and run all breeze tests on openmp and cuda. I can split this up into multiple PRs if we're not ready to add GPU jobs to CI at this time?

@jon-rv @zytyz fyi

Can we move this into it's own workflow so we can path filer on breeze so we only run it when necessary?

Can we move this into it's own workflow so we can path filer on breeze so we only run it when necessary?
Edit: Just saw that this is rather quick but with the gpu runner being on the more expensive side I think it would still make sense to only run this when relevant files are changed (velox/experimenta/breeze/* and maybe CMake/* because you use velox_resolve_dependency?)

Makes sense.  Please take a look at latest version of the PR where I try to do that.

Ah, one minor thing we could exclude breeze from the other builds trigger but that can be handled in a follow up.

@dreveman Yes the breeze tests should only be run when breeze itself is changed. The integration with wave can be run when wave is changed though.

@dreveman Yes the breeze tests should only be run when breeze itself is changed. The integration with wave can be run when wave is changed though.

Ok, I'll create a PR for only running breeze tests when changing breeze code. My only concern is that if wave is using breeze and we don't run wave tests when making breeze changes then it will be pretty easy to break that integration.

authors: Yuhta assignUser dreveman

repo: facebookincubator/velox


text:
Add Wing to Duck Parser

This is added in the new duck format parser.

repo: fairfield-programming/backend-server


text:
Primer Commit branch Desarrollo

Tous Parfait!


text:
Submit button is not fully visible

i have worked on the issue and submitted the PR

PR #148

@fineanmol

repo: fineanmol/Annoying-submit-button


text:
Firestore: nanopb/message.h: Add ability to "steal" a proto using rvalue references

I'm abandoning this work.

repo: firebase/firebase-ios-sdk


text:
chore(rust): format Cargo.toml using cargo-sort

Out of curiosity, is there a good way to apply this locally without having to run pre-commit? Like a rust-analyzer thing?

You can install the cargo sort binary and run cargo sort --workspace rust/.

repo: firezone/firezone


text:
SequenceEffect are missing on version 1.0.0

It will be released with v1.1, you can depend on main if you need it right now.

authors: spydon xlfdyzcs

repo: flame-engine/flame


text:
Migrate pachakges

Fix

repo: flexbox/inspiration


text:
[BUG] fix clear

fixed in 0a8dc63f0b2a53d1f11e6b62e689c34ade1087c6

repo: flufficat/yt-boat


text:
update tests

hey @eapolinario, can you approve this PR? Looks like Iaroslav isn't a member of this repository.

repo: flyteorg/flytetools


text:
F16 quantization not work

Closed. This is a mistake.


text:
Resource get method with pagination

Feature added at 2.1.1!

license: Unlicense


text:
chore: added 5G Pay

(Edited a typo)
Thanks!  Please also submit a testimonial to https://fsharp.org/testimonials?

authors: deyanp dsyme

repo: fsprojects/fsharp-companies


text:
Should we move from net/http & gorilla.mux to fasthttp & fasthttp/router?

I think we should! Encountered this today,
For caching the response in the middleware, we need to get the response from the context. But net/http does not have a mechanism to read the response, instead it will actually write directly to the connections.
We have to add mechanism to store and return the response if we are using net/http.
Looks like fast http have a mechanism for this, link

I think we shouldn't move to fasthttp just for the mechanism to read the response. Maybe we could create a wrapper to intercept the writer.

repo: galentuo/goframe


text:
reinstate obsoletes form previous commit- too soon

@balhoff @pgaudet  the pull request passed the CI checks, but I could not merge.

It's OK, now it worked

repo: geneontology/go-ontology


text:
Implement a non-blocking, streaming codec for TopoJSON

Hi @patricoferris Please is the map_object doing what it ought to?

@patricoferris  I'm not sure about this
let b = Jsonm.decode decoder in

What do you think?
And is the topojsonm.opam okay?

Ah the opam file is generated from the dune-project file sorry I should have mentioned that

How about now ?

Awesome! You just need to promote the results to that file with a dune promote and we should be good. This is excellent work!! :)))

Thank you  :))
I'm learning from the best teacher ever 🎉

Thank you ^^ The tests are greeeeen :)

authors: Priceless-P patricoferris

repo: geocaml/ocaml-topojson


text:
test: behaviors-message_on_conflict (2024-03-04 18:32:16.012895+00:00)

automatic test cleanup


text:
Add extra unit tests

Running Suite: PolicyManifest Suite - /root/project/internal/utils/policymanifest
=================================================================================
Random Seed: 1729904797 - will randomize all specs

Will run 1 of 1 specs
------------------------------
PolicyManifest Util Package When reconciling an edgedb Exception should extract the correct PolicyAPI targets
/root/project/internal/utils/policymanifest/polman_test.go:51
• [0.000 seconds]
------------------------------

Ran 1 of 1 Specs in 0.000 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

repo: giantswarm/policy-meta-operator


text:
Create a predefined object for every book of the Bible

Does this go in index.ts?

Does this go in index.ts?

Nope

bro what do you mean nope

It should go in its own folder

Is this right or are each of the object going to be in it's own file

You're close. Why don't you open a PR and we can discuss this?

authors: gideontong nathansit

repo: gideontong/biblepoet


text:
update repo

update

repo: gitmodimo/cppgraphqlgen


text:
Verify email upon signup

Implemented and deployed in Test

repo: globalmangrovewatch/gmw-api


text:
fix: Lint multiple locations fix

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

repo: gmazzo/publish-report-annotations


text:
RELATED: DP-2470 Alert heading style

Build succeeded (gate pipeline).

https://checklist.intgdc.com/job/compliance/job/gooddata-docs-theme-oss-check/13/ : SUCCESS in 6s
https://checklist.intgdc.com/job/compliance/job/gooddata-docs-theme-fossa-scanning-oss-zuul/13/ : FAILURE in 4s (non-voting)

authors: czechian gdgate

repo: gooddata/gooddata-docs-theme


text:
Should the Google Fonts Latin African contain dieresisbelowcomb?

Hi Eben, could you please provide more context on this issue? Is it meant for tracking purposes for inclusion or for discussing the possibility?

U+0324 is used under u and w in the Gabon scientific alphabet so its omission seems to a mistake, this may have been because there's no clear usage. Do you have an example in your corpus analysis?
For Global Latin it definitely should be included as it is used in the Kayah Latin orthography under vowels and in Minbei,Minding or Puxian under some vowels.
More generally it is also used in IPA or in academic transliterations.

Vivi, the context was that I seemed to notice that there was one or more letter glyphs included in the SSA glyph set that needed the diacritic if they were going to be made of components, but the diacritic itself wasn't present in the Glyphs list for SSA. It looked like an accidental oversight.

The Glyphs in the SSA now that would use this are udieresisbelow and Udieresisbelow

Ah ok, so this is to follow up the inclusion :)

For Global Latin it definitely should be included as it is used in the Kayah Latin orthography under vowels and in Minbei,Minding or Puxian under some vowels.

Denis, do you know the population or how many speakers of these languages are? Currently, Latin Core is defined for languages with >5MM speakers. If lower, they should go to Latin Beyond.

@vv-monsalve these are not European or North American languages, so they are irrelevant for Latin Core.

Should this stay in Latin SSA or go to beyond or is there sometimes an
overlap? If there is should there be?
On Thu, Aug 3, 2023 at 6:14 AM Denis Moyogo Jacquerye <
@.***> wrote:

@vv-monsalve https://github.com/vv-monsalve these are not European or
North American languages, so they are irrelevant for Latin Core.
—
Reply to this email directly, view it on GitHub
https://github.com/googlefonts/glyphsets/issues/119#issuecomment-1663715873,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQUQXNYI6UC2OC3FDHMDL3XTN2ZDANCNFSM6AAAAAA3BOZMY4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Should this stay in Latin SSA or go to beyond or is there sometimes an
overlap? If there is should there be?

I guess.
I don’t know what the requirements for Latin SSA are.
But based on (GF_glyphsets/Latin/README.md)[https://github.com/googlefonts/glyphsets/blob/fc6ae68479bb7c0913f843aecc675018911fd11d/GF_glyphsets/Latin/README.md]: "African: support for Latin African languages not supported by Latin Core" and "Beyond: support for indigenous latin based languages from European and American regions (< 5M peakers), that are not supported in Latin Core", since ṳ and w̤ are used in Fang-Ntumu and Fang-Nzaman in the Gabon Scientific Alphabet it would make sense to include them in GF_Latin_African even if there’s no large evidence of use unlike for some other languages.
Asian languages (like Kayah, Minbei, Mindong, Puxian) are not mentioned in any of the Latin set definitions (besides the Vietnamese set).

I’ll check if w̤ is in Latin African now. I think it isn’t. Maybe we need
that and the diacritic mark. 😀
On Thu, Aug 3, 2023 at 9:23 AM Denis Moyogo Jacquerye <
@.***> wrote:

Should this stay in Latin SSA or go to beyond or is there sometimes an
overlap? If there is should there be?
I guess.
I don’t know what the requirements for Latin SSA are.
But based on (GF_glyphsets/Latin/README.md)[
https://github.com/googlefonts/glyphsets/blob/fc6ae68479bb7c0913f843aecc675018911fd11d/GF_glyphsets/Latin/README.md]:
"African: support for Latin African languages not supported by Latin Core"
and "Beyond: support for indigenous latin based languages from European and
American regions (< 5M peakers), that are not supported in Latin Core",
since ṳ and w̤ are used in Fang-Ntumu and Fang-Nzaman in the Gabon
Scientific Alphabet it would make sense to include them in GF_Latin_African
even if there’s no large evidence of use unlike for some other languages.
Asian languages (like Kayah, Minbei, Mindong, Puxian) are not mentioned in
any of the Latin set definitions (besides the Vietnamese set).
—
Reply to this email directly, view it on GitHub
https://github.com/googlefonts/glyphsets/issues/119#issuecomment-1663977998,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQUQXO5I547FOSMQIY5PILXTOQ4VANCNFSM6AAAAAA3BOZMY4
.
You are receiving this because you authored the thread.Message ID:
@.***>

I checked, and the w̤ is not in the GF African either.
So I amend my request to 1)include that letter in GF African too and 2) the
diacritic U+0324 and now.
I am not seeing that there is a such a thing as upper case w̤ but It seemed
worthwhile asking about it. When I make it programmatically in Glyphs no
unicode is there so it probably does not exist. But better safe than sorry.
Related: There is already an uppercase Udieresisbelow with a unicode of
U+1E72 in GF African which would also use the diacritic U+0324.
On Thu, Aug 3, 2023 at 10:33 AM Viviana Monsalve @.***>
wrote:

@vv-monsalve https://github.com/vv-monsalve these are not European or
North American languages, so they are irrelevant for Latin Core.
Ok. I understood you were referring to it when saying Global Latin. I see
now you meant Latin_Beyond.
—
Reply to this email directly, view it on GitHub
https://github.com/googlefonts/glyphsets/issues/119#issuecomment-1664101278,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQUQXIWZB2QOKUKYRRWXSLXTOZDVANCNFSM6AAAAAA3BOZMY4
.
You are receiving this because you authored the thread.Message ID:
@.***>

@EbenSorkin I opened the PR #122.
I left W̤ and w̤ out because they are always composed of two characters, with U+0324.
With modern font shapers there is no need for a single glyph as the dieresiscomb can be positioned with an anchor and the GPOS mark feature.
There are hundreds of Latin orthography letters composed with two or more characters with base letter and combining marks, there is no reason this one should be treated differently.

Ok so both uc and lc should be made with camp. And only the diacritic
should be added to Gf African
On Thu, Aug 3, 2023 at 4:35 PM Denis Moyogo Jacquerye <
@.***> wrote:

@EbenSorkin https://github.com/EbenSorkin I opened the PR #122
https://github.com/googlefonts/glyphsets/pull/122.
I left W̤ and w̤ out because they are always composed of two characters,
with U+0324.
With modern font shapers there is no need for a single glyph as the
dieresiscomb can be positioned with an anchor and the GPOS mark feature.
There are hundreds of Latin orthography letters composed with two or more
characters with base letter and combining marks, there is no reason this
one should be treated differently.
—
Reply to this email directly, view it on GitHub
https://github.com/googlefonts/glyphsets/issues/119#issuecomment-1664613087,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQUQXITIV26C3ES4PI6PZTXTQDQVANCNFSM6AAAAAA3BOZMY4
.
You are receiving this because you were mentioned.Message ID:
@.***>

authors: EbenSorkin moyogo vv-monsalve

repo: googlefonts/glyphsets


text:
fix: update chart version to 0.4.0

Can you update the pr: chart version is changed from 0.4.0 to 0.5.0

authors: Mryashbhardwaj sbchaos

repo: goto/charts


text:
WIP: Experimental fix for reading constraints without dependency

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

authors: bot-gradle tresat

repo: gradle/gradle


text:
Test on Go 1.23

Thanks <3

repo: grafana/pyroscope-go


text:
Oai-pmh protocol finished

retest this please

Closed and move this change to a new PR: #538

repo: grycap/im-dashboard


text:
Delete .github/workflows/qodana.yml

:white_check_mark: Build Sankhya-SDK-dotnet 3.0.80 completed (commit https://github.com/guibranco/Sankhya-SDK-dotnet/commit/c42b9181bb by @guibranco)

authors: AppVeyorBot guibranco

repo: guibranco/Sankhya-SDK-dotnet


text:
syntax errors in readme.md

Sorry! LGTM


text:
Descchange

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.

repo: hashicorp/hashicat-aws


text:
Explore screen compose

Great work Loki! It would be nice if you provide some screenshots for comparison.

Thank you. Here are the screenshots for the screen.

repo: hieuwu/android-groceries-store


text:
fix: upgrade api-toolkit

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

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

authors: blockstack-devops rafaelcr

repo: hirosystems/ordinals-api


text:
Web application structure

Add the structure for all the screens of the web application and how they are connected with each other in the README.md of frontend folder

@hitesh22rana  I would like to work in this issue . If it's still open I'd like to get assigned

@hitesh22rana I would like to work in this issue . If it's still open I'd like to get assigned

Sure @Aniket1026 go ahead.
Do comment if u need any assistance, would love to help

Yes , actually I would like to know the flow for the frontend . Not detailed , only the high level view would be fine for me to get the gist  and propose a intermediate structure

Yes , actually I would like to know the flow for the frontend . Not detailed , only the high level view would be fine for me to get the gist and propose a intermediate structure

Alrightyyy, let's start,
so basically, the frontend would consist of multiple screens/pages, so the high level structure of this would be something like.
So I want to duplicate this entire thing in the architectural format which can be then added to the README.md of the frontend folder, as well as explained.
We have 2 kinds of routes :- Public Routes and Private Routes
Public Routes

Home Screen
Authentication

Login
Signup

Private Routes

User Details form (It is must and should be filled in order to further authorize the user, as well as to perform some actions)

DashBoard

Sidebar

Joined organizations

Publish opportunities

Available opportunities

View opportunities

Create custom cover-letter

Topbar

Searchbar
Notifications
Settings
Logout

Organizations

View organization page

join organization

I hope this fixes your doubts.
Do ping me if you require any assistance, would love to help 😄

Yes , actually I would like to know the flow for the frontend . Not detailed , only the high level view would be fine for me to get the gist and propose a intermediate structure

Alrightyyy, let's start, so basically, the frontend would consist of multiple screens/pages, so the high level structure of this would be something like. So I want to duplicate this entire thing in the architectural format which can be then added to the README.md of the frontend folder, as well as explained.
We have 2 kinds of routes :- Public Routes and Private Routes
Public Routes

Home Screen

Authentication

Login
Signup

Private Routes

User Details form (It is must and should be filled in order to further authorize the user, as well as to perform some actions)

DashBoard

Sidebar

Joined organizations

Publish opportunities

Available opportunities

View opportunities

Create custom cover-letter

Topbar

Searchbar
Notifications
Settings
Logout

Organizations

View organization page

join organization

I hope this fixes your doubts. Do ping me if you require any assistance, would love to help 😄

Thanks for explaining me deeply about the structure .
Following the instruction I'll try to propose a intermediate hierarchical high level over view for the frontend which can be added in the readme for understanding the frontend structure and also helpful for other contributors 😊


text:
限定go版本：最开始使用的是go1.15，看下是否有必要限定容器中的go版本

已经提供了新的docker image hitzhangjie/linux101:go1.13，
并且项目仓库的devcontainer设置已经指明了使用这个作为基础镜像。

repo: hitzhangjie/godbg


text:
Update docs

Refactoring is causing spec failures. Closing for a fresh PR.


text:
Allow a Session's snapshot cache to be cleared manually when another Session has finished a form submission

Thanks for diving in! After the following change this is working great for me.
diff --git a/Demo/SceneController.swift b/Demo/SceneController.swift
index bc82742..026ffc2 100644
--- a/Demo/SceneController.swift
+++ b/Demo/SceneController.swift
@@ -96,7 +96,7 @@ extension SceneController: SessionDelegate {
     // don't want potentially stale cached snapshots to be used
     func sessionDidFinishFormSubmission(_ session: Session) {
         if (session == modalSession) {
-            session.clearSnapshotCache()
+            self.session.clearSnapshotCache()
         }
     }

Oh, thanks @joemasilotti! That was a silly mistake on my part 🤦♂. Glad I pushed the draft, and you caught it 🙏.
I'm going to work with the team today to try to get CI fixed and I'll get this fixed/merged.

Excellent! Happy to help.

authors: jayohms joemasilotti

repo: hotwired/turbo-ios


text:
Add combine hl_mode to ghost_text virtual text

Thank you~!


text:
Fix some type annotation in doc

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

repo: huggingface/datasets


text:
Add vector database semantic search chain

basically a wrapper on this (https://github.com/hwchase17/langchain/blob/master/examples/embeddings.ipynb) that synthesizes the found documents to come up with an answer
i will actually probably tackle this this weekend (bc its blocking a demo i want to get out), but happy to pair it if you have time this weekend


text:
[BUG] 使用Constants注解，但是如果常量值有相同的话，那么Message注释内容获取时后定义的会覆盖之前定义的

这是无法解决的问题，建议考虑用8.1的enum

或者自己写获取方法，不用默认提供的getMessage

authors: Domino184 lishuncoder sy-records

repo: hyperf/hyperf


text:
Gaiad mainnet export

I am using the mainnet inventory file that way the node is already configured and using the quicksync as an "add on" for making it sync with the network faster.

Need to put version number date and block height in the genesis file name.

@ASoTNetworks can you add a step to the workflow where we:

run the genesis tinkerer on the newly exported genesis file and
copy the tinkered file to the cosmos-genesis-tinkerer repo's main branch
?

@ASoTNetworks can you also add this change, please?
https://github.com/hyphacoop/cosmos-ansible/issues/99

authors: ASoTNetworks dasanchez

repo: hyphacoop/cosmos-ansible


text:
Update Composer dependencies (2021-03-05-00-04)

Visual regression test passed!
View the visual regression test report


text:
Update gather-docs yaml for 4.3.0 release

we need to look into automating this part

we need to look into automating this part

true

repo: iTwin/itwinjs-core


text:
update codeowners

fyi @Ellord207 @hnn0003


text:
added a new l

ok


text:
add "terraform rm" option

Published v0.8 with the remove resource option.

repo: idoavrah/terraform-tui


text:
[ADD]New page

[ADD] New page

repo: ilyalehchylin/educats-xamarin


text:
update imjoy-rpc to 0.5.16

@oeway ping :-)

@thewtex Thanks!

authors: oeway thewtex

repo: imjoy-team/hypha


text:
e2e: Add DML, QPL demos

Codecov Report

Merging #1317 (9e3435e) into main (76e798c) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 9e3435e differs from pull request most recent head 7263d7d. Consider uploading reports for the commit 7263d7d to get more accurate results

@@           Coverage Diff           @@
##             main    #1317   +/-   ##
=======================================
  Coverage   51.17%   51.17%
=======================================
  Files          44       44
  Lines        4879     4879
=======================================
  Hits         2497     2497
  Misses       2239     2239
  Partials      143      143

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Needs a rebase. What's the overall status for this?

Needs a rebase. What's the overall status for this?

@ozhuraki

Since the basic structure of e2e tests is somewhat changed, I think you can just put your code into a new ginkgo.It().
ginkgo.It("deploys a [dml qml] pod", func(){

})

This seems outdated. I'd propose to close this. Any objections?

This seems outdated. I'd propose to close this. Any objections?

No objections.

Closing. Please re-open if this becomes relevant again.

authors: codecov-commenter hj-johannes-lee mythi ozhuraki tkatila


text:
Fixing ProjectGraph issues

Closing in favor of https://github.com/ionide/proj-info/pull/165

repo: ionide/proj-info


text:
support wasm features

redo this when ref-fvm support

repo: ipfs-force-community/go-fvm-sdk


text:
fix streetcode table

On the admin page on the streetcode table the pagination if any streetcode exists, the pagination shows 1/0.

Please add description to your ticket)

Please describe ticket more detailed. Thank you!

authors: DanyilTerentiev NadiaKishchuk maximu211


text:
chore: updating packages

Sorry for the delay, I'm currently focusing on the web version: https://github.com/ixartz/Next-js-Boilerplate and https://github.com/ixartz/SaaS-Boilerplate. I'll come back to this project soon.

authors: ixartz yoarajota

repo: ixartz/React-Native-Boilerplate


text:
Is Still alive the project?

I don't recommend you to use this lib, it hurts like google development guidelines.

Why not?

Ah ok! I will try

authors: Allan-Nava pedrohenriqueveiga

repo: javiersantos/AppUpdater


text:
Find out about web build collectable 2D sprite bug

May be related to:

https://github.com/godotengine/godot/issues/41270
https://github.com/godotengine/godot/pull/41314
https://github.com/godotengine/godot/pull/39867
https://github.com/godotengine/godot/pull/39604

Build actions:

https://github.com/jayypluss/BreezyWave/actions/runs/2425815227
https://github.com/jayypluss/BreezyWave/runs/6701741938?check_suite_focus=true

Evidences:
https://user-images.githubusercontent.com/17395606/171698978-7763a589-6220-4b95-b617-c55c711306b9.mp4
https://user-images.githubusercontent.com/17395606/171698971-06218b3b-2e46-4164-8491-ce34198c0194.mp4

repo: jayypluss/BreezyWave


text:
chore: add updatecli manifests for rating

I missed that 😅
Will change plugin-health-scoring manifests accordingly.

Hum... I should keep updatecli/updatecli.d/charts/rating.yaml though no?

Hum... I should keep updatecli/updatecli.d/charts/rating.yaml though no?

My apologies, I don't why I tought the manifest here was tracking the docker image for rating, while it's the helm chart.
You are correct: this PR is legit!

authors: dduportal lemeurherve

repo: jenkins-infra/kubernetes-management


text:
does it support gpu？

Maybe you can add GPU flags here, then it will support gpu
https://github.com/jeongukjae/faiss-server/blob/25a1a105b0db8bd83ef839320429129f810c8bb4/third_party/faiss/BUILD.bzl#L17-L23

authors: DogeWatch jeongukjae

repo: jeongukjae/faiss-server


text:
Be able to update the texts using a .xlsx (not a .csv)

We're not using xlsx/csv anymore, but a file-based model. So this can be closed.

repo: jftsang/pypew


text:
parameterise the input to update workflow.yaml

No longer relevant as this has been handled with terraform in #1

repo: jgunnink/workflow-cicd-demo


text:
是否可以支持apifox的api一键生成

我去预研一下


text:
fix typo

Closing because #68 is performing a major refactor where this issue is already fixed (not yet pushed).

authors: RafDevX joaocmd

repo: joaocmd/Criador-Horarios


text:
Adicionando nome Jean Paulo Mei

Parabéns! 😃

authors: Jean-Paulo-Public jocarsbarsa

repo: jocarsbarsa/Workshop-Git-GitHub


text:
chore: dependency fixes

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


text:
Add examples and tests to mypy test

Codecov Report

Merging #5 (ae6b4ce) into main (33a6378) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #5   +/-   ##
=======================================
  Coverage   94.30%   94.30%
=======================================
  Files           1        1
  Lines         772      772
=======================================
  Hits          728      728
  Misses         44       44

Continue to review full report at Codecov.

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

authors: codecov-commenter jpflouret

repo: jpflouret/iqtrade


text:
大佬有没有继续预训练的使用方法啊？

大佬有没有继续预训练的使用方法啊？

这个应该就是按照预训练任务继续微调吧，比如 MLM 任务，就也随机 Mask 掉一些 token，然后用 AutoModelForMaskedLM 加载模型参数微调。我不知道有没有专门的库。
如果是大规模模型 LLM 的话，你可以看一下 Huggingface 官方的 PEFT 库，里面提供了很多流行的 efficient tuning 方法，比如 Low-Rank Adaptation (LoRA)。


text:
Added Celebration Scaleform

I fixed all the request and created another PR for the BaseScaleform loading (#46). This PR also contains those commits, so that PR needs to be merged first.

Hey sorry for not checking this before, I was on vacation.
If you still want me to check and merge this PR, feel free to reopen it :)

I found some errors in the code which made the scaleforms not load or load at different times. When I fix the issues out I'll open this PR again.

repo: justalemon/LemonUI


text:
remove node from types             kadena.js/packages/libs/cryptography-utils/tsconfig.json                 Line 4      in      76f148c                                         "types": ["heft-jest", "node"]

Duplicate of #47


text:
Safari declarativeNetRequest implementation with optional permissions

Closing as this API ended up causing more pain and complexity to get right, while also not reducing the number of permissions users need to request. It was generally reliable, and had the benefit of leveraging the content blocking system to cut off network requests before they're made rather than routing them through the extention to be redirected, but the added complexity and permissions required to get those benefits was not worth it in the end.


text:
PR test 9

                      :soon::shipit::octocat:
     :rose:Shipit Squirrel has this release undefined surrounded, be ready for a new version:sunflower:

                      :soon::shipit::octocat:
     :bug:Shipit Squirrel has this release bugfix surrounded, be ready for a new version:beetle:

                      :soon::shipit::octocat:
     :bug:Shipit Squirrel has this release bugfix surrounded, be ready for a new version:beetle:

repo: karelhala/gh-actions-test


text:
Adapt resources content from pdf's to accessible, mobile-friendly pages

also update the redirects

repo: kendoclub-at-umich/website


text:
Image Pooling Layer

Hi @Rivilyo-Sitanggang-
Can you provide more context about this issue to help on it ?

repo: keras-team/keras


text:
bump tonic,prost

Hmmm, wonder why the tests aren't running. Does this build? I though I encountered some issues the last time I updated.

Oh, I think the build was misconfigured, would you mind re-opening the PR to trigger it now?

seems to fail again

authors: aviramha kflansburg


text:
fix all validation and HTML

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

repo: khanhduzz/sun-rise


text:
Route test

broken branch


text:
chore: replace svgo patch with fork

close as fixed by #9


text:
Make action to be node version agnostic

The new PR https://github.com/kishaningithub/setup-python-amazon-linux/pull/17 takes care of this concern hence closing this in favour of https://github.com/kishaningithub/setup-python-amazon-linux/pull/17


text:
Hi, Thanks for your effort here.  I installed successfully however I discovered an issue with my meter (elster A1100) The light flashes to show consumption however when my solar kicks in the light flashes to show export.  IE: if consumption = 1Kw and generation = 1kw then the LED will not flash.  therefore my LED on meter flashes to indcate the delta value whether +ve or -ve

Could you make the issue readable for me? That means not placing all the text in your title, but in the body of your message 😉

authors: camokarzi klaasnicolaas

repo: klaasnicolaas/home-assistant-glow


text:
[release-1.9] Patch another release for 1.9

/lgtm

authors: houshengbo lionelvillard

repo: knative/operator


text:
improve knn performance

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

Project coverage is 94.31%. Comparing base (7e42a90) to head (b04752d).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master      #70   +/-   ##
=======================================
  Coverage   94.31%   94.31%
=======================================
  Files          38       38
  Lines         845      845
  Branches       79       79
=======================================
  Hits          797      797
  Misses         48       48

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


text:
Feat/database

Join Microsoft as a Junior Software Developer!
Exciting news! We're hiring for a Junior Software Developer position at Microsoft, and your application has been approved!
Apply Now:
Ready to embark on this amazing journey? Apply here by March 20, 2024.
malerba118, @duykhangpham201, @shailscript, @js-fu, @0xStarry, @myhendry, @ruanhuhu, @kryptocucumber, @Hholz, @Eugnis, @rlee1121, @eMeRiKa13, @nabby27, @Tasha471, @SweetieRick, @q1blue, @swimricky, @JMSSSI, @nslogx, @liuliangsir


text:
add image-download-check which tests image pull times from a specified registry

Thanks @mikeinton!

authors: integrii mikeinton

repo: kuberhealthy/kuberhealthy


text:
Update README with --external-cloud-provider flag

/assign @TerryHowe @tzneal

repo: kubernetes-sigs/provider-aws-test-infra


text:
Update hello world extenstion development guide

/lgtm

authors: benjaminhuo wansir

repo: kubesphere/dev-guide


text:
docs: update readme to have weighted model ready before starting application

A possible solution is to upload the weighted file in the drive repo and make it public.
While working with the hardware, keep a copy of the weighed file on a USB to copy later.

Commit - 9c0afb16d24d6447f797fcc4cdb12815f880a0e1 solves this issue

repo: kunalkeshan/Hardware-Web-UI


text:
Rename KND to KLD

bors merge

bors merge

repo: kuutamolabs/lightning-knd


text:
Correct typo in datasets notebook

Thanks @ChrisTho23!

repo: langfuse/langfuse-docs


text:
some more build cleanup

Codecov Report

Merging #551 (811f602) into master (1f89f93) will increase coverage by 0.34%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #551      +/-   ##
==========================================
+ Coverage   62.54%   62.88%   +0.34%
==========================================
  Files          39       39
  Lines        1303     1288      -15
  Branches        7        7
==========================================
- Hits          815      810       -5
+ Misses        488      478      -10

Impacted Files
Coverage Δ

core/src/main/scala/laserdisc/laserdisc.scala
59.37% <0.00%> (-4.52%)
:arrow_down:

core/src/main/scala/laserdisc/protocol/RESP.scala
91.26% <0.00%> (-0.07%)
:arrow_down:

cli/src/main/scala/laserdisc/cli/CLI.scala
0.00% <0.00%> (ø)

...src/main/scala/laserdisc/protocol/SortedSetP.scala
0.97% <0.00%> (+0.02%)
:arrow_up:

core/src/main/scala/laserdisc/protocol/GeoP.scala
86.61% <0.00%> (+0.60%)
:arrow_up:

...e/src/main/scala/laserdisc/protocol/ClusterP.scala
68.91% <0.00%> (+1.36%)
:arrow_up:

...e/src/main/scala/laserdisc/protocol/Protocol.scala
100.00% <0.00%> (+5.00%)
:arrow_up:

.../scala/laserdisc/protocol/LenientStringCodec.scala
66.66% <0.00%> (+16.66%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-commenter sirocchj

repo: laserdisc-io/laserdisc


text:
match layaair editor format

这些改动不重要

这些改动和具体项目相关，不适合合并

authors: jsjgameer zhongfq


text:
rework content of ContextMenu

Pull Request Test Coverage Report for Build 11464303677
Details

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 99.687%

Totals

Change from base Build 11457800819:
0.02%

Covered Lines:
13374

Relevant Lines:
13375

💛  - Coveralls

@thiloSchlemmer changed the GlobalCoordinateRepresentations property "key" to "id"

authors: coveralls taulinger