nginx service improvements

To address https://github.com/NixOS/nixpkgs/issues/5832

Can we lower to 1sec? 10 sec is really too much in my opinion.

@lethalman it's not good as it will throw start request repeated too quickly for nginx.service
see as below, just tried:
[root@www:~/nixpkgs]# journalctl -b  |grep -v 'rejected connection' |tail -500 |egrep "emerg|nginx.service"
Jan 19 16:51:15 www nginx[22347]: nginx: [emerg] unknown directive "blablabla" in /nix/store/hash-nginx.conf:24
Jan 19 16:51:15 www systemd[1]: nginx.service: main process exited, code=exited, status=1/FAILURE
Jan 19 16:51:15 www systemd[1]: Unit nginx.service entered failed state.
Jan 19 16:51:15 www systemd[1]: nginx.service failed.
Jan 19 16:51:16 www systemd[1]: nginx.service holdoff time over, scheduling restart.
Jan 19 16:51:16 www nginx[22366]: nginx: [emerg] unknown directive "blablabla" in /nix/store/hash-nginx.conf:24
Jan 19 16:51:16 www systemd[1]: nginx.service: main process exited, code=exited, status=1/FAILURE
Jan 19 16:51:16 www systemd[1]: Unit nginx.service entered failed state.
Jan 19 16:51:16 www systemd[1]: nginx.service failed.
Jan 19 16:51:17 www systemd[1]: nginx.service holdoff time over, scheduling restart.
Jan 19 16:51:17 www nginx[22376]: nginx: [emerg] unknown directive "blablabla" in /nix/store/hash-nginx.conf:24
Jan 19 16:51:17 www systemd[1]: nginx.service: main process exited, code=exited, status=1/FAILURE
Jan 19 16:51:17 www systemd[1]: Unit nginx.service entered failed state.
Jan 19 16:51:17 www systemd[1]: nginx.service failed.
Jan 19 16:51:19 www systemd[1]: nginx.service holdoff time over, scheduling restart.
Jan 19 16:51:19 www nginx[22384]: nginx: [emerg] unknown directive "blablabla" in /nix/store/hash-nginx.conf:24
Jan 19 16:51:19 www systemd[1]: nginx.service: main process exited, code=exited, status=1/FAILURE
Jan 19 16:51:19 www systemd[1]: Unit nginx.service entered failed state.
Jan 19 16:51:19 www systemd[1]: nginx.service failed.
Jan 19 16:51:20 www systemd[1]: nginx.service holdoff time over, scheduling restart.
Jan 19 16:51:20 www nginx[22392]: nginx: [emerg] unknown directive "blablabla" in /nix/store/hash-nginx.conf:24
Jan 19 16:51:20 www systemd[1]: nginx.service: main process exited, code=exited, status=1/FAILURE
Jan 19 16:51:20 www systemd[1]: Unit nginx.service entered failed state.
Jan 19 16:51:20 www systemd[1]: nginx.service failed.
Jan 19 16:51:21 www systemd[1]: nginx.service holdoff time over, scheduling restart.
Jan 19 16:51:21 www systemd[1]: start request repeated too quickly for nginx.service
Jan 19 16:51:21 www systemd[1]: Unit nginx.service entered failed state.
Jan 19 16:51:21 www systemd[1]: nginx.service failed.

5 times tried to restart and gave up with start request repeated too quickly for nginx.service

Might be a good idea to add Use StartLimitBurst= to configure how many starts per interval are allowed
not sure what's the default value of it.
or keep it to at least 5s ..
actually the same should be done in the dovecot commit https://github.com/NixOS/nixpkgs/pull/5845  where you changed it to 1s

@arno01 we can think of it. It's certainly an improvement over the previous Restart=no default. It's so dependent on the target the system, that after all you can change those values. It's not that we can decide a good value for every system, as this is mainly an hack for a more graceful failure by default.
I have no strong opinion on this, except that 10s is too much.

This delay 5s doesn't generate any friction, but only ensures that the service is started.
If it was anyway started from the first time, then it wasn't delayed at all as it is RestartSec parameter on-failure only.
So when something is wrong, it will give it 5s or 10s before retrying.. and this something is wrong might really need 5s as we know the dhcpd problem now https://github.com/NixOS/nixpkgs/issues/5832#issuecomment-70471743 ...
with 1s it will try just 4-5 times which is not enough

@lethalman okay then, 5s should be enough

Merging this, I think it's a good to have default.


Creation of documentation/implementation guide for Worklist DataGrid

Summary
Create implementation guide and required documentation for Worklist DataGrid.
Testing
This change was tested using:

[ ] WDIO
[ ] Jest
[ ] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[ ] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[ ] Accessibility review
[ ] Functional review

This PR resolves:
UXPLATFORM-9322

I removed the Tech Review Required label as this time we do not have a process to engage the Tech Writer team. Those conversations are ongoing but nothing will be finalized by the time you'll need to merge this PR.

@chrismichalewicz We can still keep the label for the designated tech reviewers on the team to utilize. Once we get the process finalized, we can revisit the labels.

@chrismichalewicz We can still keep the label for the designated tech reviewers on the team to utilize. Once we get the process finalized, we can revisit the labels.

@sdadn  Sounds good, I readded it. I just was afraid it would prevent merging or something.

From an older PR I know but since we're trying to update the documentation to be ready for consumers, we should fix this:
https://github.com/cerner/terra-framework/blob/e290a269aa4c0fae47ee6b4768922b83410733a8/packages/terra-framework-docs/src/terra-dev-site/doc/data-grid/WorklistDataGrid.1/About.2.doc.mdx#L2
We're using the wrong component for the version badge.

"Default" looks weird here, I think we should rename the example to Basic Worklist Data Grid. I think you just need to rename the file.

From an older PR I know but since we're trying to update the documentation to be ready for consumers, we should fix this:
https://github.com/cerner/terra-framework/blob/e290a269aa4c0fae47ee6b4768922b83410733a8/packages/terra-framework-docs/src/terra-dev-site/doc/data-grid/WorklistDataGrid.1/About.2.doc.mdx#L2
We're using the wrong component for the version badge.

Updated to terra-data-grid

"Default" looks weird here, I think we should rename the example to Basic Worklist Data Grid. I think you just need to rename the file.

Updated


Mission Corrupt on Restart

Bug report

Basic Information

Mission version: 1.96.146070
Map used: Lythium
Mods used:

@BMS
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=1617973312

ace
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=463939057

ACE Compat - RHS Armed Forces of the Russian Federation
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=773131200

ACE Compat - RHS United States Armed Forces
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=773125288

ACE Compat - RHS: GREF
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=884966711

Achilles
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=723217262

ADV - ACE Splint
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=1291442929

Advanced Rappelling
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=713709341

Advanced Sling Loading
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=615007497

Advanced Towing
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=639837898

bCombat
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=314397752

CBA_A3
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=450814997

CUP Terrains - Core
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=583496184

Jbad
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=520618345

LYTHIUM
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=909547724

Project OPFOR
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=735566597

RHSAFRF
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=843425103

RHSGREF
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=843593391

RHSUSAF
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=843577117

task_force_radio
Steam
http://steamcommunity.com/sharedfiles/filedetails/?id=620019431

Dedicated or local game: Dedicated
Source of the mission file (URL): https://drive.google.com/open?id=1_t_0Fvrdqk0fZwxFlyQDB3t_KSEQPGqz

Individual Things
Did you edit anything within the mission files?
Yes
If yes, what did you edit exactly?
Unlock Zeus, Ace Configs and put some starter vehicles
Short Issue Description
Sometimes when you restart the server, the kp option menu like Arsenal, Secondary missions disappear, and actually when you destroy the fob, the tension level not lowered.
Expected Behaviour

When you activate a secondary objective like "Fob Hunting", the mission has no cost and don't low the tension level.
Steps to Reproduce the Issue

Screenshots, Serverlog or any other helpful Information
Error in expression <at_readiness
|| _resources_intel_old != resources_intel
|| _infantry_cap_old != >
Error position: <resources_intel
|| _infantry_cap_old != >
Error Undefined variable in expression: resources_intel
File mpmissions__cur_mp.lythium\scripts\server\game\synchronise_vars.sqf..., line 52
Server Log: https://drive.google.com/open?id=1gvnhLoxUsR1EJxb0BwHUWz52d7p3sfR9

You're using 0.96.4 which had a bug with corruption of intel value, this was fixed in 0.96.5.
To fix the issue execute resources_intel = 0; on server via debug console.
It's advised to update to latest release to prevent this from happening again..


 I don't think this is very practical and it's better if we find a solution for it.
I searched the issue and it seems like there is a solution for it and the launch template of the node groups should be changed to auto delete the resources that are created by the EKS.
I'll update the issue when more information later.

The issue is discussed in here aws/amazon-vpc-cni-k8s#69
It seems like with enabling delete_on_termination flag, the issue will be resolved.

It seems that configuration flag isn't available anymore. An alternative option would be to use delete time provisioners to delete all services on the cluster before its removal, but I don't think that would be a best practice
https://developer.hashicorp.com/terraform/language/resources/provisioners/syntax#destroy-time-provisioners

That means the ingress controller needs to be created after the infrastructure is ready, which seems to go against your proposal of merging cluster and config folders into one.

I think we can have merging both folders and releasing an ingress controller via terraform.
In this case probably using ALB ingress controller would make more sense since it is required if you want to use AWS WAF.


Blog post topic: The kids are alright: Reddit frenzies and fundamental information

Hi guys! From our survey, we have the following participants that show an interest in this topic (github handle in brackets, if provided):
Lian (@findfunongh), Jonas (@Jonas-Materna), Mengqi (@Cathy-Cai), Jonas (@jonwessel), Mahmoud (@mdelshadi)

Hi guys,
I know it might be a bit late to get in touch regarding the blog topic. I
am wondering if anyone who is interested in this blog topic would like to
form a group together and discuss the topic, or if you have already had a
group would you mind adding an extra ;)
All the best,
Mengqi Cai (Cathy)
On Tue, May 18, 2021 at 8:31 AM Tobias Witter @.***>
wrote:

Hi guys! From our survey, we have the following participants that show an
interest in this topic (github handle in brackets, if provided):
Lian @.*** https://github.com/findfunongh), Jonas (
@Jonas-Materna https://github.com/Jonas-Materna), Mengqi (@Cathy-Cai
https://github.com/Cathy-Cai Cai (Cathy)), Jonas @.***
https://github.com/jonwessel), Mahmoud @.***
https://github.com/mdelshadi)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/trr266/rescorptrans/issues/19, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATYXORE3YVD37CGMCDZYAVLTOICSPANCNFSM44FEJMUQ
.

Hi guys, I know it might be a bit late to get in touch regarding the blog topic. I am wondering if anyone who is interested in this blog topic would like to form a group together and discuss the topic, or if you have already had a group would you mind adding an extra ;) All the best, Mengqi Cai (Cathy)
…
On Tue, May 18, 2021 at 8:31 AM Tobias Witter @.> wrote: Hi guys! From our survey, we have the following participants that show an interest in this topic (github handle in brackets, if provided): Lian @. https://github.com/findfunongh), Jonas ( @Jonas-Materna https://github.com/Jonas-Materna), Mengqi (@Cathy-Cai https://github.com/Cathy-Cai Cai (Cathy)), Jonas @.*** https://github.com/jonwessel), Mahmoud @.*** https://github.com/mdelshadi) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#19>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATYXORE3YVD37CGMCDZYAVLTOICSPANCNFSM44FEJMUQ .

Hi Cathy,
I am also new to the course and would like to form a group with you. WE can then decide on a topic for the blog post. Please post your response.
Thanks and Regards,
Sukanya Bhattacharyya.

Hi guys, I know it might be a bit late to get in touch regarding the blog topic. I am wondering if anyone who is interested in this blog topic would like to form a group together and discuss the topic, or if you have already had a group would you mind adding an extra ;) All the best, Mengqi Cai (Cathy)
…
On Tue, May 18, 2021 at 8:31 AM Tobias Witter @.> wrote: Hi guys! From our survey, we have the following participants that show an interest in this topic (github handle in brackets, if provided): Lian<EMAIL_ADDRESS>https://github.com/findfunongh), Jonas ( @Jonas-Materna https://github.com/Jonas-Materna), Mengqi (@Cathy-Cai https://github.com/Cathy-Cai Cai (Cathy)), Jonas<EMAIL_ADDRESS>https://github.com/jonwessel), Mahmoud @.*** https://github.com/mdelshadi) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#19>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATYXORE3YVD37CGMCDZYAVLTOICSPANCNFSM44FEJMUQ .

Hi Cathy,
I am also new to the course and would like to form a group with you. WE can then decide on a topic for the blog post. Please post your response.
Thanks and Regards,
Sukanya Bhattacharyya.

Hey Sukanay,
Thanks for the reply. I am personally interested in the topic in this issue, which is "The kids are alright: Reddit frenzies and fundamental information". Please let me know if you are interested or not :)

Hey,
Yes I am interested in the topic, could you please give me your WhatsApp
number? We could easily converse there and then also sometimes on GitHub to
show participation. Waiting for your reply.
Sukanya.
On Thu 27. May 2021 at 19:56, Mengqi Cai (Cathy) @.***>
wrote:

Hi guys, I know it might be a bit late to get in touch regarding the blog
topic. I am wondering if anyone who is interested in this blog topic would
like to form a group together and discuss the topic, or if you have already
had a group would you mind adding an extra ;) All the best, Mengqi Cai
(Cathy)
… <#m_4311816124772445917_>
On Tue, May 18, 2021 at 8:31 AM Tobias Witter @.> wrote: Hi guys! From
our survey, we have the following participants that show an interest in
this topic (github handle in brackets, if provided): Lian<EMAIL_ADDRESS>https://github.com/findfunongh https://github.com/findfunongh), Jonas (
@Jonas-Materna https://github.com/Jonas-Materna
https://github.com/Jonas-Materna https://github.com/Jonas-Materna),
Mengqi (@Cathy-Cai https://github.com/Cathy-Cai
https://github.com/Cathy-Cai https://github.com/Cathy-Cai Cai (Cathy)),
Jonas<EMAIL_ADDRESS>https://github.com/jonwessel), Mahmoud @.**
https://github.com/mdelshadi) — You are receiving this because you were
mentioned. Reply to this email directly, view it on GitHub <#19
https://github.com/trr266/rescorptrans/issues/19>, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATYXORE3YVD37CGMCDZYAVLTOICSPANCNFSM44FEJMUQ
.
Hi Cathy,
I am also new to the course and would like to form a group with you. WE
can then decide on a topic for the blog post. Please post your response.
Thanks and Regards,
Sukanya Bhattacharyya.
Hey Sukanay,
Thanks for the reply. I am personally interested in the topic in this
issue, which is "The kids are alright: Reddit frenzies and fundamental
information". Please let me know if you are interested or not :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/trr266/rescorptrans/issues/19#issuecomment-849827088,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARULSBQ5QMDPLP72V4E4YCLTP2BV3ANCNFSM44FEJMUQ
.

https://github.com/trr266/rescorptrans/issues/7#issuecomment-826871085
On Thu, 27 May 2021 at 20:09, Sukanya Bhattacharyya <
@.***> wrote:

Hey,
Yes I am interested in the topic, could you please give me your WhatsApp
number? We could easily converse there and then also sometimes on GitHub to
show participation. Waiting for your reply.
Sukanya.
On Thu 27. May 2021 at 19:56, Mengqi Cai (Cathy) @.***>
wrote:

Hi guys, I know it might be a bit late to get in touch regarding the blog
topic. I am wondering if anyone who is interested in this blog topic would
like to form a group together and discuss the topic, or if you have already
had a group would you mind adding an extra ;) All the best, Mengqi Cai
(Cathy)
… <#m_5459370381059780917_m_4311816124772445917_>
On Tue, May 18, 2021 at 8:31 AM Tobias Witter @.> wrote: Hi guys!
From our survey, we have the following participants that show an interest
in this topic (github handle in brackets, if provided): Lian<EMAIL_ADDRESS>https://github.com/findfunongh https://github.com/findfunongh), Jonas (
@Jonas-Materna https://github.com/Jonas-Materna
https://github.com/Jonas-Materna https://github.com/Jonas-Materna),
Mengqi (@Cathy-Cai https://github.com/Cathy-Cai
https://github.com/Cathy-Cai https://github.com/Cathy-Cai Cai (Cathy)),
Jonas<EMAIL_ADDRESS>https://github.com/jonwessel), Mahmoud @.**
https://github.com/mdelshadi) — You are receiving this because you were
mentioned. Reply to this email directly, view it on GitHub <#19
https://github.com/trr266/rescorptrans/issues/19>, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATYXORE3YVD37CGMCDZYAVLTOICSPANCNFSM44FEJMUQ
.
Hi Cathy,
I am also new to the course and would like to form a group with you. WE
can then decide on a topic for the blog post. Please post your response.
Thanks and Regards,
Sukanya Bhattacharyya.
Hey Sukanay,
Thanks for the reply. I am personally interested in the topic in this
issue, which is "The kids are alright: Reddit frenzies and fundamental
information". Please let me know if you are interested or not :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/trr266/rescorptrans/issues/19#issuecomment-849827088,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARULSBQ5QMDPLP72V4E4YCLTP2BV3ANCNFSM44FEJMUQ
.


No versions associated with library

impact search currently lists versions of libraries that can not be downloaded. There should be a flag (maybe the default) to hide these packages as they are of no use to users.

I'm closing this because I think we recognize the issue.  Once we have a running version of the new Go implementation, feel free to reopen if you still see remaining issues.


DAWN-465 ⁃ Provide to/from variant for transaction types

Provide to/from variant on chain controller for transaction types.
Verify each transaction type can be converted to/from via templated method on chain controller via unittests.
Update abi_serializer for missing transaction types
Update abi_serializer for any other missing native types

ATC:

chain_test should continue to run without error.

Yes, this has been completed.


Revert "sim: add CONFIG_SIM_STACKSIZE_ADJUSTMENT to reduce variability"

Summary
This reverts commit 6b5a7a73ba76671c81dc70485befb5ed5e818fe0.
Because:

it broke existing configurations.

it makes stack-related api very confusing.
eg. the "stack_size" argument of nxtask_init has different meanings
depending on "stack".
eg. pthread_attr_setstack and pthread_attr_setstacksize

stacksize is inherently arch-dependent.
the goal to share the same stack size configurations among archs
is questionable.

Impact
sim
Testing

Summary
This reverts commit 6b5a7a7.
Because:

it broke existing configurations.

could you point out which config broken?

it makes stack-related api very confusing.
eg. the "stack_size" argument of nxtask_init has different meanings
depending on "stack".
eg. pthread_attr_setstack and pthread_attr_setstacksize
stacksize is inherently arch-dependent.

Yes, that's why the adjust is located in arch/sim.

the goal to share the same stack size configurations among archs
is questionable.

As I explain no one try to the same stack config for all arch, I just want to fix sim problem.

Impact
sim
Testing

Summary
This reverts commit 6b5a7a7.
Because:

it broke existing configurations.

could you point out which config broken?

eg. my local config, which is now using much larger stack than intended.

it makes stack-related api very confusing.
eg. the "stack_size" argument of nxtask_init has different meanings
depending on "stack".

If you don't like the stack size reported from ps, I can change the report size as user passed one, but allocate the bigger memory.

i was not talking about the report size.
nxtast_init takes "non adjusted" stack_size for stack==NULL
while it takes "adjusted" stack_size for stack!=NULL.

eg. pthread_attr_setstack and pthread_attr_setstacksize

stacksize is inherently arch-dependent.

Yes, that's why the adjust is located in arch/sim.

the goal to share the same stack size configurations among archs
is questionable.

As I explain before no one try to the same stack config for all arch, I just want to fix sim problem.

ok.
maybe "the goal to share the same stack size configurations between arch X and sim is questionable" is a better description?

Impact
sim
Testing

Copy from https://github.com/apache/incubator-nuttx/pull/4977:
If you don't like this patch, please revert DEFAULT_STACK_SIZE too. From my review, DEFAULT_STACK_SIZE provided by you also try to fix the same stack size. And let's modify all the hardcode stack size in application or add CONFIG_xxx_STACK_SIZE=65536 in all defconfig under boards/sim.

Summary
This reverts commit 6b5a7a7.
Because:

it broke existing configurations.

could you point out which config broken?

eg. my local config, which is now using much larger stack than intended.

DEFAULT_STACK_SIZE on sim equals 65536 before the change, SIM_STACKSIZE_ADJUSTMENT equals 65536 after change. Both config has the similar functionality and same default value, so the stack consumption should be similar.

it makes stack-related api very confusing.
eg. the "stack_size" argument of nxtask_init has different meanings
depending on "stack".

If you don't like the stack size reported from ps, I can change the report size as user passed one, but allocate the bigger memory.

i was not talking about the report size.
nxtast_init takes "non adjusted" stack_size for stack==NULL while it takes "adjusted" stack_size for stack!=NULL.

Yes, this is the only case we can't adjust, but this feature is seldom used.

eg. pthread_attr_setstack and pthread_attr_setstacksize

stacksize is inherently arch-dependent.

Yes, that's why the adjust is located in arch/sim.

the goal to share the same stack size configurations among archs
is questionable.

As I explain before no one try to the same stack config for all arch, I just want to fix sim problem.

ok. maybe "the goal to share the same stack size configurations between arch X and sim is questionable" is a better description?

All programs(except pthread_attr_setstack) which has the stack size with fine tuning or hardcode value can run on sim correctly.  this approach is better than DEFAULT_STACK_SIZE. So, please revert both in this PR if you like.

Copy from #4977: If you don't like this patch, please revert DEFAULT_STACK_SIZE too. From my review, DEFAULT_STACK_SIZE provided by you also try to fix the same stack size issue. And let's modify all the hardcode stack size in application or add CONFIG_xxx_STACK_SIZE=65536 in all defconfig under boards/sim. @yamt please revert DEFAULT_STAck_SIZE related change too, thanks.

i don't follow your logic.
DEFAULT_STACK_SIZE doesn't have the api inconsistency issue CONFIG_SIM_STACKSIZE_ADJUSTMENT has.

Summary
This reverts commit 6b5a7a7.
Because:

it broke existing configurations.

could you point out which config broken?

eg. my local config, which is now using much larger stack than intended.

DEFAULT_STACK_SIZE on sim equals 65536 before the change, SIM_STACKSIZE_ADJUSTMENT equals 65536 after change. Both config has the similar functionality and same default value, so the stack consumption should be similar.

it makes stack-related api very confusing.
eg. the "stack_size" argument of nxtask_init has different meanings
depending on "stack".

If you don't like the stack size reported from ps, I can change the report size as user passed one, but allocate the bigger memory.

i was not talking about the report size.
nxtast_init takes "non adjusted" stack_size for stack==NULL while it takes "adjusted" stack_size for stack!=NULL.

Yes, this is the only case we can't adjust, but this feature is seldom used.

i guess pthread_attr_setstacksize is seldom used too, right?
or, is it somehow important?

eg. pthread_attr_setstack and pthread_attr_setstacksize

stacksize is inherently arch-dependent.

Yes, that's why the adjust is located in arch/sim.

the goal to share the same stack size configurations among archs
is questionable.

As I explain before no one try to the same stack config for all arch, I just want to fix sim problem.

ok. maybe "the goal to share the same stack size configurations between arch X and sim is questionable" is a better description?

All programs(except pthread_attr_setstack) which has the stack size with fine tuning or hardcode value can run on sim correctly. this approach is better than DEFAULT_STACK_SIZE. So, please revert both in this PR if you like.

my biggest complaint is the api inconsistency.
that's why i prefer Kconfig-level (or maybe Application.mk level) adjustment over this approach.

Yes, this is the only case we can't adjust, but this feature is seldom used.

i guess pthread_attr_setstacksize is seldom used too, right? or, is it somehow important?

pthread_attr_setstacksize is important, but SIM_STACKSIZE_ADJUSTMENT can handle this case correctly. What this approach can't handle is pthread_attr_setstack with non NULL pointer, but this case is rarely used.

All programs(except pthread_attr_setstack) which has the stack size with fine tuning or hardcode value can run on sim correctly. this approach is better than DEFAULT_STACK_SIZE. So, please revert both in this PR if you like.

my biggest complaint is the api inconsistency.

api inconsistency only happen for pthread_attr_setstack with non NULL pointer. If you like, we can fix this inconsistency too: let up_use_stack ignore the preallocated stack pointer and allocate a new stack with the adjusted size.

that's why i prefer Kconfig-level (or maybe Application.mk level) adjustment over this approach.

Kconfig/Application.mk level adjustment can't handle these cases automatically:

The default stack size in Kconfig is a fine tune value, not DEFAULT_STACK_SIZE
The code call pthread_attr_setstack with the hard code value

But, the above cases happen frequently. Before we find a better solution, please don't revert this patch. It's a waste of time to fix the stack size issue on simulator.

Yes, this is the only case we can't adjust, but this feature is seldom used.

i guess pthread_attr_setstacksize is seldom used too, right? or, is it somehow important?

pthread_attr_setstacksize is important, but SIM_STACKSIZE_ADJUSTMENT can handle this case correctly. What this approach can't handle is pthread_attr_setstack with non NULL pointer, but this case is rarely used.

All programs(except pthread_attr_setstack) which has the stack size with fine tuning or hardcode value can run on sim correctly. this approach is better than DEFAULT_STACK_SIZE. So, please revert both in this PR if you like.

my biggest complaint is the api inconsistency.

api inconsistency only happen for pthread_attr_setstack with non NULL pointer. If you like, we can fix this inconsistency too: let up_use_stack ignore the preallocated stack pointer and allocate a new stack with the adjusted size. This fix is reasonable since the preallocated memory isn't difference from the dynamically allocated memory.

i've seen an app which is actually checking if it's running on the preallocated stack.
i'm not saying it's a good idea. i'm just saying such an app exists.

that's why i prefer Kconfig-level (or maybe Application.mk level) adjustment over this approach.

Kconfig/Application.mk level adjustment can't handle these cases automatically:
1. The default stack size in Kconfig is a fine tune value, not DEFAULT_STACK_SIZE

2. The code call pthread_attr_setstack with the hard code value

But, the above cases happen frequently. Before we find a better solution, please don't revert this patch. It's a waste of time to fix the stack size issue on simulator.

i feel what you really want is a way to ignore ~all user-specified stack addr / size.
how do you think?

api inconsistency only happen for pthread_attr_setstack with non NULL pointer. If you like, we can fix this inconsistency too: let up_use_stack ignore the preallocated stack pointer and allocate a new stack with the adjusted size. This fix is reasonable since the preallocated memory isn't difference from the dynamically allocated memory.

i've seen an app which is actually checking if it's running on the preallocated stack. i'm not saying it's a good idea. i'm just saying such an app exists.

app should trust the kernel, the fix could be simply remove the check.

that's why i prefer Kconfig-level (or maybe Application.mk level) adjustment over this approach.

Kconfig/Application.mk level adjustment can't handle these cases automatically:
1. The default stack size in Kconfig is a fine tune value, not DEFAULT_STACK_SIZE

2. The code call pthread_attr_setstack with the hard code value
But, the above cases happen frequently. Before we find a better solution, please don't revert this patch. It's a waste of time to fix the stack size issue on simulator.

i feel what you really want is a way to ignore ~all user-specified stack addr / size. how do you think?

Yes, but just for sim. Simulator is a very special target, it doesn't make sense to let developer fix the stack overflow issue on it.

api inconsistency only happen for pthread_attr_setstack with non NULL pointer. If you like, we can fix this inconsistency too: let up_use_stack ignore the preallocated stack pointer and allocate a new stack with the adjusted size. This fix is reasonable since the preallocated memory isn't difference from the dynamically allocated memory.

i've seen an app which is actually checking if it's running on the preallocated stack. i'm not saying it's a good idea. i'm just saying such an app exists.

app should trust the kernel, the fix could be simply remove the check.

i vaguely remember that the code was actually changing its behavior depending on the stack on which it's running.
anyway, i guess such a "fix" needs a deep understanding on the app code.
it can be more difficult than tweaking the stack size for sim.

In this very special case, app code can add #ifndef CONFIG_ARCH_SIM to skip the check.

https://github.com/apache/incubator-nuttx/pull/5384 is acceptable for me


feat(stream-logs): stream logs to file for job and flow commands

Issue
Fixes https://github.com/sasjs/cli/issues/587.
Intent
Stream logs to a file as a job or flow is executing.
Implementation

Bumped adapter version.
Updated PollOptions for flow and job commands.

Checks

[x] Code is formatted correctly (npm run lint:fix).
[x] Any new functionality has been unit tested.
[x] All unit tests are passing (npm test).
[x] All CI checks are green.
[x] JSDoc comments have been added or updated.
[x] Reviewer is assigned.

@all-contributors add @krishna-acondy  for code, infra

I'd like to get https://github.com/sasjs/adapter/pull/486 in and update the adapter here before merging this PR.


Type inference - code after early return from an 'if' should infer the same type as the 'else' block would

Version 1.8

First of all I'm sorry if I get the jargon wrong, I'm new to typescript (I tried to search for this issue and failed, I may have used the wrong search terms).

When using type guards, code in an else block uses the condition in the if to infer the type of the variable. However if the if contains an early return the rest of the function should be treated as the else of the if from we we returned.
Code
// A self-contained demonstration of the problem follows...
type Foo = { a: string };
function isFoo(x): x is Foo {
	return x && typeof(x.a) === 'string';
}

type Bar = { b: string };

function buz1(arg: Foo|Bar) : string {
	if (isFoo(arg))
		return arg.a;  // OK arg inferred to be Foo
	else
		return arg.b; // OK arg inferred to be Bar
}

function buz2(arg: Foo|Bar) : string {
	if (isFoo(arg))
		return arg.a;  // OK arg inferred to be Foo

	return arg.b;  // ** Error b isn't a member of Foo|Bar **
}

Expected behavior:
function buz2 should compile with no error.
Actual behavior:
Error when accessing member b of arg even though arg can be inferred to be of type Bar (as it is in buz1.else).

Hey @lanzkron I believe this will be fixed in TypeScript 2.0 where we'll start using control flow analysis for types. Give the nightlies a try out with npm install -g typescript@next and see how it works!

You can read more about this feature in #8010.

tested that it works fine in @next


Implement _check function

Here is what I did:

fork the repository and read the contribution guide well.
as the guide explain I run the lining command and passed all requirements
the last thing I ran the test command and also all tests were passed correctly.

@danthareja plz review my pullrequest.


Plans for 1.0.0

I've been working up a set of things I'm planning on doing in order to release the next major version of node_redis, 1.0.0
There will be some breaking changes, but it should get the library in a better place for both maintainability and extensibility.

Move the repository to a Github Org.  -- this will only change the location, and the old location should redirect
Split the parser into a separate module
redo the tests to isolate unit tests vs regression tests & generally separate tested areas
Implement the new SCAN functionality
(this is the big one) remove the offline_queue and connection retry support from the core library.

That last one is the big breaking change, but I feel it needs to be done for a few reasons:

If extracted, the same behavior could be done via an external module.
The way that Redis works, I feel (and antirez agrees) this idea is fundamentally flawed. The Redis server saves some state for redis clients, and reconnections in the middle of a command stream cannot guarantee the same behavior as if there was no interruption.
So long as this library controls connection retries, any Sentinel or Cluster implementation cannot be in a separate module. This is important for encouraging modularity in the library, and allowing different implementations of sentinel/cluster support.
there are long-standing bugs with the current implementation
Most of the option-related feature requests right now involve different settings related to this feature. If it can be re-implemented in separate modules, different use-cases can be more easily constructed without option-bloat.

I would like to get this done by the end of this year, and would absolutely appreciate help! Very soon I will start to push work-in-progress branches for some of the above work, and would welcome any help!
Also, feel free to provide comments/feedback on this plan here.

+1 for sentinel support


IE11 - repeat.for with sort value converter not updating component after sort direction changes.

I'm submitting a bug report

Library Version:
2.0.0

Please tell us about your environment:

Operating System:
Windows 10

Node Version:
8.11.3

NPM Version:
6.1.0

JSPM OR Webpack AND Version
Gulp 4

Browser:
IE 11

Language:
TS v2.1.6

Current behavior:
repeat.for with sort value converter failing is to update component when a size attribute is present on the select element.
I have a select list sorted by a value converter and two buttons to toggle the sort direction. In IE 11 the select list does not update even though the value converter is being called an my list object is updated.
The root cause appears to be using the size attribute on the select element
This is working in all other browsers.
Expected/desired behavior:

Skeleton App Demo

What is the expected behavior?
The select lists sort direction changes when either button is pressed.

What is the motivation / use case for changing the behavior?
Cross browser compatibility.

I think you mean v1.3.0 for aurelia-framework. The current version for aurelia-binding is v2.1.3.

You are correct, I've updated with my aurelia-binding version.

I've determined the root cause.
Using the size attribute on a select element seems to be preventing the list from updating.
As gist.run is not working in IE 11 I've updated a skeleton app to recreate the issue.
Bug Demo Project

I was able to reproduce this on IE11.
Here's the crazy part (or maybe not-so-crazy; we're talking about IE, after all..)
You can see the DOM update when you inspect it (note that Zulu is on top):

But the visual update does not occur (note that Zulu is still at the bottom):

Even hand-editing the DOM will not cause the updates to render. Somehow this very specific set of conditions just causes the select element to stop re-rendering.
Google revealed a handful of dropdown quirks in IE but nothing that explains this. I'm baffled by it (but also not, because it's IE..)
@bigopon  any ideas?

Wow, that's ... crazy when hand editing the DOM doesn't cause IE to re-render. I'm not even sure if this is Aurelia related.

Changing the size attribute to 1 and revert it back to 3 will make IE rerender the select. So the workaround is
export class App {
  public readonly myBrokenSelect: HTMLSelectElement;
  public router: Router;

  public userList = [
    new User('Zulu', 0),
    new User('Lima', 1),
    new User('Bravo', 1)
  ];

  @observable() // make it observable so we can trigger the rerender
  public sortDirection = 'ascending';

  ...

  // This just to trigger the render
  sortDirectionChanged() {
    if (this.myBrokenSelect) {
      const currSize = this.myBrokenSelect.size;
      this.myBrokenSelect.size = 1;
      this.myBrokenSelect.size = currSize;
    }
  }
}

@Ra-Sedgwick nice bug that you discovered there. @fkleuver you are right about it not being so crazy 😄

@bigopon Interesting that that works..
@Ra-Sedgwick Is this an acceptable workaround for you?

Thanks for the workaround @bigopon its cleaner then what I came up with.
In my app I'm applying a filter via a value converter as well and this workaround still has issues if the list has been filtered.
The first time the sort direction is toggle (with a filter applied)  the select box still fails to update, however any subsequent toggles work.
Introducing a slight delay has everything working as expected.
       if (this.selectBox) {
            setTimeout(() => {
                const currSize = this.selectBox.size;
                this.selectBox.size = 1;
                this.selectBox.size = currSize;
            });
        }

@EisenbergEffect I don't think this is something we can / want to fix since it's a very quirky IE11 thing. But we may want to keep this open as a todo to document this somewhere, or simply to make this easier to find for other people with the same issue. What do you think?

Definitely would be good to document this.

IE is Cobol of the future


Add resources/configuration to support Tenant use

Current Terraform version
0.13.5
Description
The Tenant API has support for creating and removing accounts from Cloudflare, and the standard API also has support for updating existing accounts. It would be great if these could be added to support declaring new Cloudflare account and having them created.
As part of this work the account_id parameter defined in the provider would most likely need to be added as a parameter to each resource type so that a provider isn't tied to a single account.
Use-cases

Cloudflare resellers declaring each Cloudflare account and their properties like zones within Terraform, rather than manually managing them manually or through a custom-built program using the Tenant API

Potential Terraform configuration
resource "cloudflare_account" "example_account" {
    name = "Example Account"
    type = "standard"
}

# Use the new account ID when creating a zone using a new account_id parameter
resource "cloudflare_zone" "example_zone" {
    zone       = "example.com"
    account_id = cloudflare_account.example_account.id
}

Community note

Please vote on this issue by adding a 👍 reaction
to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull
request, please leave a comment

Thanks for raising this @indygriffiths! Looks like we'll need to add cloudflare-go support for this one first before we start using it in Terraform.

While revisiting this, the functionality for Tenants managing Accounts already exist however the change to move the account ID definition into the resources which will be breaking changes. Will need to await for the next major release to address this.

While revisiting this, the functionality for Tenants managing Accounts already exist however the change to move the account ID definition into the resources which will be breaking changes. Will need to await for the next major release to address this.

as of #1563 (landed in v3.13.0, https://github.com/cloudflare/cloudflare-go/pull/850 upstream), this should be complete except for some Workers methods which are due for a revamp and won't be addressed due to the internal models and business logic attached.
if you find individual resources still impacted, please raise individual issues and we can work on getting them addressed.

(deprecations in both systems will come with the next major version)


Count of string data

hii @nicolaskruchten ,
i want sum of sting values . how can i do that?
i have tried sum aggregater but it is only doing sum for int values. now i want to do sum or count of string value then it is not giving anything. how can i achieve this?
thanks.

What is the sum of strings? For example how would you sum "a" and "b"?

I want total count of party and gender and province.
I mean their is 2 gender and 5 parties so i want that count .
how can i get that?

I’m afraid I don’t understand... can you provide an example of your desired
output please?
On Thu, Dec 6, 2018 at 00:54 rspatel0928<EMAIL_ADDRESS>wrote:

[image: untitled]
https://user-images.githubusercontent.com/29850643/49564324-209eb180-f949-11e8-8a23-72ad959317aa.png
I want total count of party and gender and province.
I mean their is 2 gender and 5 parties so i want that count .
how can i get that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nicolaskruchten/pivottable/issues/1056#issuecomment-444757088,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMbA0n6Oe8obBJDVOCFrWWLzTuUJVOmks5u2LELgaJpZM4ZCiEM
.

here we have party and gender in cols. and Province in row.  i can see that their is 2 distinct value in gender , male and female. same as in Party their are 5 values and same foe Province.
In my side i am working on huge data so i want the count of that distinct value in some column .
like Party is 5 ,Gender is 2 and Province is 11.

Ok I understand the math but I don’t understand the visual output you’re
looking for. Can you provide a sketch or mock-up or something?
On Thu, Dec 6, 2018 at 08:20 rspatel0928<EMAIL_ADDRESS>wrote:

here we have party and gender in cols. and Province in row. i can see that
their is 2 distinct value in gender , male and female. same as in Party
their are 5 values and same foe Province.
In my side i am working on huge data so i want the count of that distinct
value in some column .
like Party is 5 ,Gender is 2 and Province is 11.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nicolaskruchten/pivottable/issues/1056#issuecomment-444868163,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMbAy1lyODHQLx5L1H4QFPEsG4O-8pWks5u2RmYgaJpZM4ZCiEM
.

Something like this!?

I see. There's no feature for this right now, no, but if you click on the little filter triangles, there you will see the count of unique values. You can also use the "count unique" aggregator instead of "count".


RootUrl not working

I set up my WebAPI under a separate map:
app.Map("/api", appApi => {
                var config = new HttpConfiguration();
                config.EnableSwagger(c => {
                    //c.RootUrl((req) => "/api/"); // doesn't work now
                    c.IncludeXmlComments(GetXmlCommentsPath());
                    c.SingleApiVersion("v1", "WebHost API");
                }).EnableSwaggerUi();

                config.DependencyResolver = new AutofacWebApiDependencyResolver(container);
                WebApiConfig.Register(config);
                appApi.UseAutofacMiddleware(container);
                appApi.UseAutofacWebApi(config);
                appApi.UseCors(CorsOptions.AllowAll);
                app.UseStageMarker(PipelineStage.MapHandler);
                appApi.UseWebApi(config);
            });

It shows empty API list:

If I edit the address, then my API shows up:

But, the link to try out my API is broken:

I tried to use the setting c.RootUrl((req) => "/api/"); with and without / on both ends, but I get Internal Server Error (500) with a cryptic message "invalid url...". And there is additional / in the address if I uncomment the RootUrl setting:

I remember a similar issue since v4, but then haven't been using Swashbuckle for a long time. If this not a bug, could you please help me with correct settings?

I've observed the same problem with the latest build. It really looks like a bug.

RootUrl expects a lambda that returns an absolute URL. The following should work ...
c.RootUrl(req => SwaggerDocsConfig.DefaultRootUrlResolver(req) + "/api");

Thanks for this!
I am running a very similar setup where I have my web api OWIN app running under a different map than the rest of my app and have been struggling with the configuration for several hours. I finally got everything working except for swagger.
I got rid of the SwaggerConfig.cs file and moved all configuration to my Web Api app startup configuration
public void Configure(IAppBuilder appBuilder)
{
    appBuilder.Map("/api", app =>
    {
		HttpConfiguration config = new HttpConfiguration();
		NinjectWebCommon.ConfigureNinject(app, config);
		config.EnableSwagger(c => ConfigureSwagger(c))
                    .EnableSwaggerUi();
                ...
    }
}

And my ConfigureSwagger function is defined below my Configure function as
private static void ConfigureSwagger(SwaggerDocsConfig config)
{
	config.RootUrl(req => SwaggerDocsConfig.DefaultRootUrlResolver(req) + "/api");
	config.SingleApiVersion("v1", "My Api");
}

That RootUrl call, with that specific configuration, fixed everything (I hope).

why the rootpath relative to host not supported in Swashbuckle? it works well in swaggerui itself.
this could really help when publishing apis behind reverse proxy that has different transport, host, port...


feat: suggest upgrade when cli version is outdated

What kind of change does this PR introduce?
Bug fix, feature, docs update, ...
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

16 of 38 (42.11%)  changed or added relevant lines in 4 files are covered.
7 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.004%) to 58.183%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/bootstrap.go
0
1
0.0%

internal/bootstrap/bootstrap.go
0
1
0.0%

internal/utils/release.go
16
21
76.19%

cmd/root.go
0
15
0.0%

Files with Coverage Reduction
New Missed Lines
%

internal/storage/rm/rm.go
2
90.48%

internal/gen/keys/keys.go
5
11.76%

Totals

Change from base Build<PHONE_NUMBER>:
-0.004%

Covered Lines:
6527

Relevant Lines:
11218

💛  - Coveralls


Willing to pay someone to speed up pdfminer

pdfminer works great for text extraction and most PDF files I process take less than a second.
But some PDF files can take a couple minutes (even though the size is similar), which is too slow when you are trying to provide an immediate response.
I'd be happy to hire someone to make pdfminer faster and your changes could be open source.  Please contact me if you are interested in doing that.

hi, i want to improve pdfminer, i will contact you.

also, https://jazzband.co/ could be a long time solution?

Hi @jeffoneill,
Thanks for your willingness to pay money to active contributors to this project. You could also consider to pay money to the people who have created pdfminer from scratch. Check out the Change Log of the original pdfminer here.
If you would like to speak to current maintainers, you could checkout the gitter.
If you would like to speed up the processing of specific pdf's, please provide examples of those pdf's and the code that you are using to process it.

Hi @pietermarsman, I'd go broke quickly if I started paying the developers of every open source project that I use! 😄
I'll find an example PDF that I can share.

Closing this because there is nothing actionable. Feel free to create a new issue if you have a problem with a specific pdf.


JS linter errors introduced by PR 1778

PR #1778 introduced 2 new JS linter errors
/home/travis/build/DMPRoadmap/roadmap/lib/assets/javascripts/views/shared/create_account_form.js
  3:8   error  Using exported name 'validateOrgSelection' as identifier for default export  import/no-named-as-default
  4:10  error  'isValidText' is defined but never used                                      no-unused-vars

can't test in UI. closing issue.


Change how the client version number is obtained

Currently the client obtains version information using the Bundle this works fine for Cocoapods builds however, this does not work for SwiftPM builds. Instead we should use a final field to supply the version information.

This was fixed by #173


Remove faces that don't match the same attribute layout

Fixes two related problems where gltfs were rendering incorrectly because the number of uv attributes did not match the number of position attributes.
The first case is when two primitives in the same mesh use different types of attributes.
usemtl primitive1material
f 77 78 79
f 77 80 78
usemtl primitive2material
f 3665/2676 3666/2677 3634/2678
f 3711/2679 3709/2680 3710/2681

This is fixed by storing attribute data on the primitive rather than the mesh. The downside to this is the vertex cache gets reset more often, meaning possibly more duplicate vertices. This won't affect most models, but it could be worse for those that are constantly interleaving usemtl lines.
The second case is when faces within a primitive use different types of attributes.
f 1/1/1 2/2/1 4/3/1 3/4/1
f 3 4 8 7
f 7/9/3 8/10/3 6/11/3 5/12/3

Most of the faces look like the first and third, but there would occasionally be faces like the second that don't match the attribute layout. These faces don't really make sense because they are missing uv coordinates and won't be textured properly anyways. Those faces get discarded now though I am thinking they should instead be assigned (0,0) uv coordinates.

Do we need to do a 1.x branch version of this PR as well, or is it something that can't easily be backported?

Yes still need to do the backport, which shouldn't look too different.

Works as advertised.  Please up CHANGES

@lilleyse no rush, but don't forget about this.

@mramato updated.

Thanks!


Refactor README.md

Minor spell check and refactoring of the README.

Closing this one as the change for typo was discussed at : https://github.com/puppeteer/puppeteer/pull/9455#discussion_r1058191106
And changes the other changes they idle no difference on the generated website,
if the intention for them  please comment and I would be happy to rereview that part.


PP counter wont record any of my pp plays while in fullscreen osu.

I tried doing the restful thing but it didnt work. Instead of using OBS I use the alternative for streaming. It's called Streamlabs OBS. works the same way. I need help since when i leave Auto playing and alt tab to my desktop it records the auto bot pp play. Sometimes it does work but only for one map. It dosent record my 100 50 and miss hits as well. If you want a more detailed explanations I have a video I can send but this place dosent support mp4 files.

I left  video parts there
Should I retry installing it? I was just following this youtuber name Narrator.
https://www.youtube.com/watch?v=zmIaa7js0wc&t=1s

https://puu.sh/Bx2ZY/0e6832f630.zip
try this which contain a lot plugins.
just you start Sync.type "o i" and then start osu!.
You will see pp displayer ingame.
And you can them with osu! in your streamlab obs.
but I suggest you show pp with obs plugin:https://github.com/OsuSync/RealTimePPDisplayer/wiki/How-to-setup-obs-plugins-when-you-are-playing-osu!-fullscrren
if above method all not good.You can modify OutputMethods=text in comfig.ini and normally pp info will always write to rtpp.txt in Sync folder.your streamlab obs could read this file and show.
tomorrow I will make a list of tutorial video about how to setup and customize Sync(and its plugins)

Thank you so much

Mikirasora your file really helped me but i have a question how can i make the font size bigger?

Mikirasora your file really helped me but i have a question how can i make the font size bigger?

If you mean ingame content.you can try this

your the best dude thank you so much for helping me out!

MikiaSora wait nvm...when i play osu I can see my pp counter and it records my misses and hits. But when I see my stream, myy pp counter glitches and rarely shows up. I  private message your discord


Unable to draw outside bounds of CollapsableColumn

Hi there!
I just wanted to say thank you for creating the this libary! It came at the perfect time for me and existing libraries had some flaws 🙏
The CollapsableColumn is near perfect for my needs but I need to draw some buttons outside the bounds.
I was wondering if it would be possible to remove the
clipScrollableContainer(Orientation.Vertical) from the CollapsableColumn to enable this?
Happy to raise a PR if you agree, otherwise I can just copy CollapsableColumn and remove it myself 👍
Thanks

The reason it's there is if your collapsable isn't at the top of the screen the content will slide up but still be visible. I do think it's reasonable to be able to disable though if you want to clip a parent view instead. Maybe with a clip: Boolean = true param?

Ah ok that makes sense 👍
Raised a PR here, let me know what you think.


Ready guide + meta tags

Includes the following updates:

Corrections to meta tags for fasttrack reporting
Rebase of Ready guide from current repo

Docs Build status updates of commit d7ecfc1:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/cloud-adoption/migrate/baseline-migration-guide/assess.md
:warning:Warning
View
Details

docs/cloud-adoption/migrate/baseline-migration-guide/index.md
:warning:Warning
View
Details

docs/cloud-adoption/migrate/baseline-migration-guide/organize-resources.md
:warning:Warning
View
Details

docs/cloud-adoption/migrate/baseline-migration-guide/prerequisites.md
:warning:Warning
View
Details

docs/cloud-adoption/migrate/baseline-migration-guide/secure-and-manage.md
:warning:Warning
View
Details

toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

bread/toc.json
:warning:Warning

Details

docs/cloud-adoption/migrate/baseline-migration-guide/assistance.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/migrate/baseline-migration-guide/manage-costs.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/migrate/baseline-migration-guide/migrate.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/migrate/baseline-migration-guide/optimize-and-transform.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/ready/azure-readiness-guide/before-you-start.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/ready/azure-readiness-guide/govern-org-compliance.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/ready/azure-readiness-guide/index.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/ready/azure-readiness-guide/manage-access.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/ready/azure-readiness-guide/manage-costs.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/ready/azure-readiness-guide/monitoring-reporting.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/ready/azure-readiness-guide/organize-resources.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/ready/azure-readiness-guide/staying-current.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/migrate/baseline-migration-guide/assess.md

Line 167: [Warning] Invalid file link:(~/cloud-adoption/migrate/migration-considerations/assess/estimate).

docs/cloud-adoption/migrate/baseline-migration-guide/index.md

Line 75: [Warning] Invalid file link:(~/cloud-adoption/migrate/expanded-scope).
Line 81: [Warning] Invalid file link:(~/cloud-adoption/migrate/expanded-scope/).

docs/cloud-adoption/migrate/baseline-migration-guide/organize-resources.md

Line 113: [Warning] Invalid file link:(~/cloud-adoption/migrate/ready/considerations/naming-and-tagging).

docs/cloud-adoption/migrate/baseline-migration-guide/prerequisites.md

Line 92: [Warning] Invalid file link:(~/cloud-adoption/migrate/baseline-migration-guide/azure/architecture/cloud-adoption/migrate/theory/prerequisites/planning-checklist).

docs/cloud-adoption/migrate/baseline-migration-guide/secure-and-manage.md

Line 0: [Warning] Duplicate tab id: (siterecovery, 2).

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\5am1\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\5am1\building-blocks\extending-templates\toc.json'.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\5am1\bread\toc.json'.

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


Porting from tinyxml to tinyxml2

In Tinyxml creating a declaration was like : TiXmlDeclaration xmlDecl = new TiXmlDeclaration("1.0", "UTF-8", "");
But in Tinyxml2 it requires to create a document first
tinyxml2::XMLDeclaration decl = doc.NewDeclaration();
decl->SetValue("xml version="1.0" encoding=""");
In tinyxml2, Do I need to do InsertEndChild after creating a new declaration?

Yes, you do. The declaration will not be added to the document structure until you add it explicitly. The test project contains an example (search for NewDeclaration() call).

Thanks.
While porting to tinyxml2, apart from changes of namespace and class name, if there is possibility of more changes like these , I think a porting document can be helpful.

Since I am porting my application to tinyxml2, I can work on this ,if you think it can be helpful to others. @Dmitry

Well, I cannot comment on this, I never say any code for earlier tinyxml. Perhaps @leethomason has some ideas.

It's been so long since I ported over...I've sort of forgotten the stumbling blocks. Should have documented it then.
I would like to address some issues in the Readme: the TinyXML-1 vs. 2 part is pretty outdated (there is no reason to use TinyXML-1 any more.) If you had a brief list of porting notes, it could go in the readme, and replace much of the existing 1 vs. 2 discussion.

Also a good issue to remember to more aggressively deprecate TinyXML-1. That version should be fully retired.

I'm doing this now :-(
Most of it seems pretty straightforward - xDoc.NewXYZ instead of new XYZ.  ToElement() instead of Element(), create a XMLPrinter to export an object to text, etc.
The stumbling blocks come with the lack of Clone(), and the missing index parameters on Child().

Clone() is problematic; although writing a DeepClone() is on the list. (But still doesn't work quite the same.)
The Child() index is (of course) fixable - it's just such a performance stumbling block.
And Parse()...yeah. Sorry about that. But didn't want to keep persisting the irregularity.

It was said earlier:
--Since I am porting my application to tinyxml2, I can work on this ,if you think it can be helpful to others. @dmitry
--Well, I cannot comment on this, I never saw any code for earlier tinyxml. Perhaps @leethomason has some ideas.
I would very much appreciate a porting guide. I am struggling with the various API changes, such as XMLDeclaration. At the very least I think that there should be a prominent statement that there are significant API differences - it is not a drop-in replacement.

I came here looking for an answer to the XMLDeclaration question, but since there isn't one:
   XMLDocument doc;     XMLDeclaration* decl = doc.NewDeclaration();     doc.LinkEndChild(decl);


ISPN-6273 Add documentation for ClusterExecutor

Fixed a few outdated comments on javadoc

https://issues.jboss.org/browse/ISPN-6273

Pushed, thanks


Update Issue - Automate_undefined_23694

default description

Property
Value

Browser
Chrome 100.0

Operating System
Windows 10

Resolution
1280x588

Screenshot Attached
Screenshot URL

Updated Screenshot Attached


Workaround race condition in shutdown hooks between LogManager and ElasticApmTracer.stop()

Describe the bug
When the agent log level is set to DEBUG and the application terminates normally so that the shutdown hooks are run by the JVM, the application should log instrumentation statistics at DEBUG level. However there is a logging manager shutdown hook which turns off logging config, and this causes the log level for loggers to no longer be reported as being at debug level. The order of running shutdown hooks is non-deterministic, so this is a race condition. The consequence is that sometimes the statistics is outputted and sometimes not. In my testing for a "Hello World" Java application with normal termination, the statistics were never outputted.
Steps to reproduce

Create a Java application that consists of just System.out.println("hello") in the main method
Run with the Java agent and log level set to DEBUG

A more detailed option is to run the above test with a custom agent with the following line added at the top of MatcherTimerLifecycleListener
System.out.println("MatcherTimerLifecycleListener is at debug level? "+logger.isDebugEnabled());

Expected behavior
Should see the instrumentation statistics printed at DEBUG level, but instead they are not printed

I think #2448 fixes this

Indeed fixed, thank you @tobiasstadler !


FEDX-965: Readme updates

FEDX-965

Remove a reference to an outdated CLI option
Add a basic example readme for the pub.dev view

Security Insights
No security relevant content was detected by automated scans.
Action Items

Review PR for security impact; comment "security review required" if needed or unsure
Verify aviary.yaml coverage of security relevant code

Questions or Comments? Reach out on Slack: #support-infosec.

QA +1 @Workiva/release-management-p


Contribution Questions

I posted a couple days ago about this (https://github.com/JimBobSquarePants/ImageProcessor/issues/103), but it was an aside to a follow up on an old closed issue. I'm not sure if the admins are alerted to posts on closed issues, so I figured I'd write a new post. I've been working a lot with ImageProcessor over the last couple of weeks and I built a file manager app as a proof of concept to investigate the feasibility of using ImageProcessor in our CMS. I would like to share it with the community, but I don't know how or if you would go about taking a contribution for something like this. I don't maintain a blog, but I did set up a Github repo for it.
The file manager that I built uses Web Forms, but I am also working on a version for asp.net 5 using the new DNX stuff. I'm not very experienced with the kind of low level image manipulation work you are working on for V3 and I have never been involved in corporate API reviews, but I may be able to contribute and help out with building the new ImageProcessor.Web or equivalent. I am thinking about working on some middleware to incorporate and test some of the work you are doing on V3, but I figured I'd ask to see if you have any specific plans in this regard. No sense in doing something that goes against your long term plans, especially if I am going to try and contribute something back to the project.
Anyway, thanks for your hard work. Fantastic progress has been made here. Hoping to find a way to help out.

Hi there,
Sorry I missed your post, I get quite a few on my various projects and some slip through the net when I'm looking at them on my mobile.
I'm absolutely looking for help build the next generation ImageProcessor.Web so any help you could give in that department would be most appreciated. I haven't looked at Asp.Net 5 at all yet so it will be a learning experience for me (Much like doing all this low level stuff is).
The API is something I really want to get right (I'm looking for reviewers for the base library too) so we can work on that together. I want to really standardize the url API also. The current version is a bit of a mess.
Things to consider when we design the API.

IImageSource for pluggable image sources (local, remote, cloud, db)
IImageCache for pluggable cache mechanism
IQueryParser for parsing individual querystring parameters, this would tie into a modernized equivalent of QueryParamParser
Managing arrays for things like crop coordinates should match the MVC6 methodology
Everything should be configurable
As much as possible should be testable
Async all the things!

We should be able to make a much leaner version than the current one which should be faster also. (Not to say the current one isn't quick of course :wink: )
There's a fair amount of stuff we can rework from the current version so we should be able to make fairly rapid progress.
Thanks for raising this. It's made my day!
We can chat more about the API etc on Gitter, hopefully there we can attract more interest.

Hi Jim,
Thanks for the positive feedback. Your API concerns make complete sense to me. Sounds like a solid plan.
I've been prototyping since the early betas of asp.net vnext to investigate porting our CMS, so I've begun to learn the ins and outs. My current thinking is to get a basic file manager up and running (hopefully by the end of the weekend), and then start building an ImageProcessor.Web package in my file manager solution on top of your V3 code to add thumbnail and image resizing support. This will give me an opportunity to learn the new middleware constructs that are replacing the old http handler concepts. I'll start with the most basic resizing stuff (just the width and height APIs, no cache etc.). As you mentioned, getting the API right is extremely important, so I think we should keep it super basic at first in order to get the new dnx pipeline integration done right. Once that is done right it should be fairly easy to move whatever we like over to your repo and start layering on the additional features.
If you want to check out the web forms file manager that I built it is at https://github.com/PromontoryProtean/WebFormsFileManager. This is what I am currently porting to asp.net vnext. It's taking me some time to get organized because I have prototype code scattered all over the place, and I am trying to make it fit for consumption on Github.
I'm on the road tomorrow for work but will check out Gitter on Friday. I have never used it before but will get myself set up. Definitely looking forward to collaborating on this.

Hey Jim - I've reached a point where I am beginning to bring V3 into my new file manager. I set myself up on Gitter under PromontoryProtean. I've never used Gitter so I'm not sure what you have in mind for creating a room. Do you have something already set up? Or are we doing this from scratch?

Great to hear!
There's already a room setup here
https://gitter.im/JimBobSquarePants/ImageProcessor
You should be able to join that room an we can chat there.


Move arc length calculations from pens.perimeterPen to misc.bezierTools

As discussed in https://github.com/robofab-developers/fontPens/pull/5.

and 💯 for adding the doctests!

Thanks :) I could recycle the doctests from the fontPens functions ;)


commonjs

hey, folks, do you have plans to publish chalk with both CommonJs and ESM using conditional exports?

Duplicate of #632


Refactor cluster builder

It is focused on cluster builder, it split out traffic policy and upstream tls settings apply.
And also move out some helper functions from cluster.go.
The target is to make the cluster building more readable and now the calling stack like cluster.go->clusterbuilder.go
->cluster_traffic_policy.go->cluster_tls.go.
In theory, we should not allow calling in the opposite direction, which can make circular dependency. And it can also prevent us from moving the cluster builder out to a separate pkg.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test release-notes

unit-tests-arm64_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test release-notes

unit-tests-arm64_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test unit-tests-arm64

lint_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test release-notes

unit-tests-arm64_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test unit-tests-arm64

lint_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test lint

gencheck_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test release-notes

unit-tests-arm64_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test unit-tests-arm64

lint_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test lint

gencheck_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test gencheck

unit-tests_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test unit-tests-arm64

lint_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test lint

gencheck_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test gencheck

unit-tests_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test unit-tests

release-notes_istio
2f36d4549f32014713316fc9e150028b175f3c61
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test gencheck

unit-tests_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test unit-tests

release-notes_istio
2f36d4549f32014713316fc9e150028b175f3c61
link
true
/test release-notes

lint_istio
2f36d4549f32014713316fc9e150028b175f3c61
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
2b13a598362c448b90e353129ac56bce3b0041e1
link
true
/test unit-tests

release-notes_istio
2f36d4549f32014713316fc9e150028b175f3c61
link
true
/test release-notes

lint_istio
2f36d4549f32014713316fc9e150028b175f3c61
link
true
/test lint

gencheck_istio
2f36d4549f32014713316fc9e150028b175f3c61
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
2f36d4549f32014713316fc9e150028b175f3c61
link
true
/test lint

gencheck_istio
2f36d4549f32014713316fc9e150028b175f3c61
link
true
/test gencheck

release-notes_istio
4f5afe80cd78eb168f9630620493a1a0c860f27f
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

The target is to make the cluster building more readable and now the calling stack like cluster.go->clusterbuilder.go
->cluster_traffic_policy.go->cluster_tls.go.
In theory, we should not allow calling in the opposite direction, which can make circular dependency.

TBH I don't feel great about this. I mean the end result is fine, but we shouldn't be trying to define dependencies as files. Files are not really meant to be used like this in Go, just an organizational pattern. If we really want to make this dependency chain we would need to use packages, which I think is overkill


Remove simplebicycle class

This is no longer necessary as the bicycle submodule now has a BicycleKinematic class.

PR https://github.com/oliverlee/phobos/pull/112

Merged https://github.com/oliverlee/phobos/commit/2858f4e99eff42a29fce9782cedac8205b7c50f1


[SPARK-48467][BUILD] Upgrade Maven to 3.9.7

What changes were proposed in this pull request?
The pr aims to upgrade maven from 3.9.6 to 3.9.7.
Why are the changes needed?
https://maven.apache.org/docs/3.9.7/release-notes.html

Does this PR introduce any user-facing change?
No.
How was this patch tested?

Manually test
Pass GA.

Was this patch authored or co-authored using generative AI tooling?
No.

cc @dongjoon-hyun


Wip/pr/6767

am I right in reading this as "if you print a line out it works, remove the print and it doesn't"? suspect there's something else going on...


Update dependencies

Bump all dependencies.
In particular, this gets the latest ouroboros-network which has a fix for mainnet sync.

bors r+


fix: dataset row use tab

Seems that we should be using id instead of index to determine if we are viewing a row ref. Note that even with this fix I think row refs are broken.
Before:

After:

Approving, but with the caveat that dataset_rowxEV92JtCymTYhgoUs0LSVYBGrTJyR6jXitU7gmxyT3A is a pretty gnarly variable name lol. Can we make this simpler?

Yeah, that's kind of the issue - it used to be e.g. datset_row3


Fail download Data to wifi

Hi ! i got an error when i try to download a file with data's mobile and i switch on wifi.
Can i do something for that or it come from the library ?

@RemyBarbosa You have to enabled try on network fail in the FetchConfiguration Builder.
 final FetchConfiguration fetchConfiguration = new FetchConfiguration.Builder(this)
                .enableRetryOnNetworkGain(true)
                .build()

Please have a look at the sample app.

Are you sure you have not restricted the download to WiFi only?
Lincoln Karuhanga
-----Original Message-----
From: "RemyBarbosa"<EMAIL_ADDRESS>Sent: 17/09/2018 15:22
To: "tonyofrancis/Fetch"<EMAIL_ADDRESS>Cc: "Subscribed"<EMAIL_ADDRESS>Subject: Re: [tonyofrancis/Fetch] Fail download Data to wifi (#243)
still doesn't works, but only in this way : mobile data -> wifi
wifi -> mobile data perfectly works
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Yep the download start with mobile data, i can see the progression and if i switch to wifi during the download the i got an error.

@RemyBarbosa when the switch occurs an error will be thrown. But fetch will wait and retry again in 10 seconds. Are you setting a NetworkType on the request or Fetch? eg:
fetch.setGlobalNetworkType(NetworkType.WIFI_ONLY);
//or
request.setNetworkType(NetworkType.WIFI_ONLY);


ignore redis failure on classification create

don't 500 that may cause a duplicate classification submission instead just carry on as the lifecycle event will eventually fire but still go ahead and notify that redis is down.

LGTM


Unable to sync commit with LFS files

OS: Windows 7/10

Created new repository
adding LFS filters to git attributes and synced commit
Commit LFS files locally
Attempt Sync

Received failed to sync error message. When trying to push through git shell, I received these error messages:

C:\Users\MIguel Ponce\Documents\GitHub\LFS-Filterless [master]> git push
Di.png is an LFS pointer to af8e81e3089ad082f171266b4de154bd398de4df0d41c90dc592
bb12ef5723a6, which does not exist in .git/lfs/objects.
Run 'git lfs fsck' to verify Git LFS objects.
error: failed to push some refs to 'https://github.com/MichaelClickalot/LFS-Filt
erless.git'
C:\Users\MIguel Ponce\Documents\GitHub\LFS-Filterless [master]> git lfs fsck
Object Di.png (af8e81e3089ad082f171266b4de154bd398de4df0d41c90dc592bb12ef5723a6)
could not be checked: The system cannot find the file specified.
Object Diamonds.png (527757d3abf20082b55e9f7173cd24b4ebabfdbe84592c91658cd60a690
27f62) could not be checked: The system cannot find the file specified.
C:\Users\MIguel Ponce\Documents\GitHub\LFS-Filterless [master]>

Log file:
TheLog.txt
Found a related issue here: #564

What commands did you run to create the repo? Here's the error message:

Di.png is an LFS pointer to af8e81e3089ad082f171266b4de154bd398de4df0d41c90dc592
bb12ef5723a6, which does not exist in .git/lfs/objects.

Assuming .gitattributes is setup, those files should be created after running git add on the file.

I created the repo through the desktop client

What desktop client? What LFS filters did you add? What files were committed?

Windows desktop client (tried with 2 different repositories in Windows 7 and Windows 10, on both the bump-lfs and production builds)
LFS filters: *.png, *.txt
files:

(text files are over 100mb in size, let me know if you want me to attach as well)

Not sure if this is relevant, but this was working up until I switched from bump-lfs to production build, then stopped working thereafter.

Well, here's how it's supposed to work in Git LFS. Maybe this will help you troubleshoot in Desktop:
$ git init
Initialized empty Git repository in /Users/rick/p/foo/.git/
$ git lfs track "*.png"
Tracking *.png
$ git lfs track "*.txt"
Tracking *.txt
$ echo "png" > pseudo.png
$ echo "txt" > real.txt
$ tree .git/lfs/objects
.git/lfs/objects
└── logs

1 directory, 0 files
$ gs
## Initial commit on master
?? .gitattributes
?? pseudo.png
?? real.txt

At this point, the repo has been initialized. The patterns are in .gitattributes. The png and txt files are in the repo, but are still untracked. Nothing is in .git/lfs/objects.
$ git add .
$ tree .git/lfs/objects
.git/lfs/objects
├── 33
│   └── d8
│       └── 33d8344a7135c42aa3876706b908f95b702d83ff53e05e4aaff17c07bf67a98e
├── 7c
│   └── 4c
│       └── 7c4c231187cd4b75677c312faa7787da874bdbb7d71e1c9dc0619f3e27a53940
└── logs

5 directories, 2 files

Files are staged, but not committed. The files are now in .git/lfs/objects.
$ git commit -m "booya"
[master (root-commit) 06f96ed] booya
 3 files changed, 8 insertions(+)
 create mode 100644 .gitattributes
 create mode 100644 pseudo.png
 create mode 100644 real.txt
$ git show
commit 06f96edf35eed8fcd7bf75f343bf4caa22477c8b
Author: risk danger olson<EMAIL_ADDRESS>Date:   Thu Mar 10 15:42:18 2016 -0700

    booya

diff --git a/.gitattributes b/.gitattributes
new file mode 100644
index 0000000..7da20c6
--- /dev/null
+++ b/.gitattributes
@@ -0,0 +1,2 @@
+*.png filter=lfs diff=lfs merge=lfs -text
+*.txt filter=lfs diff=lfs merge=lfs -text
diff --git a/pseudo.png b/pseudo.png
new file mode 100644
index 0000000..84f2bee
--- /dev/null
+++ b/pseudo.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33d8344a7135c42aa3876706b908f95b702d83ff53e05e4aaff17c07bf67a98e
+size 4
diff --git a/real.txt b/real.txt
new file mode 100644
index 0000000..739557c
--- /dev/null
+++ b/real.txt
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c4c231187cd4b75677c312faa7787da874bdbb7d71e1c9dc0619f3e27a53940
+size 4

The commit shows the LFS pointers for the png and txt files ^
It looks like this part isn't happening for some reason.

@technoweenie Just fyi, the bump-lfs version of the Desktop app is a branch that includes git-lfs 1.1.2. Production includes git-lfs 1.1.0. From what I understand about this, it looks like if you ever use 1.1.2 and then for some reason use 1.1.0 on the same repo, it permanently corrupts it so that it stops working with any version. If this is indeed the case, then it's kinda bad because if for some reason we have to rollback a release or someone accidentally has the wrong git-lfs on the path, it's game over :-P

Based on discussion with @shana, it's possible the switching between the git lfs versions (1.1.0 to 1.1.2, and vice versa several times) caused it to become permanently corrupt.

Can I get a detailed step by step reproduction? Nothing in the original steps mentioned that the LFS version was being rolled back anywhere.

The problem started as a continuation of the issue mentioned on #5820.
Prerequisite: Windows client installed with build speakeasy/bump-lfs.

create a repository and publish
add LFS filters to git attributes, and commit
push files through git LFS
switch to production build
create a subfolder within the repository, and copy the files from step 3 into it
create a commit and push

That's essentially when the problem started.

Keep in mind this is an OSS repo, and none of us work on Desktop. So the best I can do is try to replicate this with the command line, under the assumption Desktop is not doing anything special, and the system has the default git lfs config.
1) create a repository and publish
$ git init
Initialized empty Git repository in /Users/rick/p/foo/.git/
$ git remote add origin https://github.com/technoweenie/musical-octo-meme
$ git push origin master
error: src refspec master does not match any.
error: failed to push some refs to 'https://github.com/technoweenie/musical-octo-meme'

Not sure how desktop handles empty repos...
2) add LFS filters to git attributes, and commit
First, I created an empty directory with the v1.1.2 and v1.1.0 LFS binaries. Here's the current lfs env:
$ git config filter.lfs.smudge "/Users/rick/p/foo/git-lfs-1.1.2/git-lfs smudge %f"
$ git config filter.lfs.clean "/Users/rick/p/foo/git-lfs-1.1.2/git-lfs clean %f"

$ git-lfs-1.1.2/git-lfs env
git-lfs/1.1.2 (GitHub; darwin amd64; go 1.6; git bf6a6c9)
git version 2.5.4 (Apple Git-61)

Endpoint=https://github.com/technoweenie/musical-octo-meme.git/info/lfs (auth=none)
LocalWorkingDir=/Users/rick/p/foo
LocalGitDir=/Users/rick/p/foo/.git
LocalGitStorageDir=/Users/rick/p/foo/.git
LocalMediaDir=/Users/rick/p/foo/.git/lfs/objects
TempDir=/Users/rick/p/foo/.git/lfs/tmp
ConcurrentTransfers=3
BatchTransfer=true
GIT_LFS_TEST_DIR=/Users/rick/p/git-lfs-temp
GIT_LFS_TEST_MAXPROCS=4
git config filter.lfs.smudge = "/Users/rick/p/foo/git-lfs-1.1.2/git-lfs smudge %f"
git config filter.lfs.clean = "/Users/rick/p/foo/git-lfs-1.1.2/git-lfs clean %f"

Now to actually track the files, and push just .gitattributes.
$ git-lfs-1.1.2/git-lfs track "*.png"
Tracking *.png
$ git-lfs-1.1.2/git-lfs track "*.txt"
Tracking *.txt
$ git add .gitattributes
$ git commit -m "gitattributes"
[master (root-commit) d57ee92] gitattributes
 1 file changed, 2 insertions(+)
 create mode 100644 .gitattributes
$ git push origin master
...
 * [new branch]      master -> master

3) push files through git LFS
$ echo "png" > fake.png
$ echo "txt" > real.txt
$ git add fake.png real.txt

# Now the objects are in .git/lfs/objects
$ tree .git/lfs/objects
.git/lfs/objects
├── 33
│   └── d8
│       └── 33d8344a7135c42aa3876706b908f95b702d83ff53e05e4aaff17c07bf67a98e
├── 7c
│   └── 4c
│       └── 7c4c231187cd4b75677c312faa7787da874bdbb7d71e1c9dc0619f3e27a53940
└── logs

5 directories, 2 files

$ git commit -m "add LFS files"
[master 5667ca0] add LFS files
 2 files changed, 6 insertions(+)
 create mode 100644 fake.png
 create mode 100644 real.txt

$ git push origin master
Git LFS: (2 of 2 files) 8 B / 8 B
...
   d57ee92..5667ca0  master -> master

4) switch to production build
$ git config filter.lfs.smudge "/Users/rick/p/foo/git-lfs-1.1.0/git-lfs smudge %f"
$ git config filter.lfs.clean "/Users/rick/p/foo/git-lfs-1.1.0/git-lfs clean %f"

$ git-lfs-1.1.0/git-lfs env
git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 258acf1)
git version 2.5.4 (Apple Git-61)

Endpoint=https://github.com/technoweenie/musical-octo-meme.git/info/lfs (auth=basic)
LocalWorkingDir=/Users/rick/p/foo
LocalGitDir=/Users/rick/p/foo/.git
LocalGitStorageDir=/Users/rick/p/foo/.git
LocalMediaDir=/Users/rick/p/foo/.git/lfs/objects
TempDir=/Users/rick/p/foo/.git/lfs/tmp
ConcurrentTransfers=3
BatchTransfer=true
GIT_LFS_TEST_DIR=/Users/rick/p/git-lfs-temp
GIT_LFS_TEST_MAXPROCS=4
git config filter.lfs.smudge = "/Users/rick/p/foo/git-lfs-1.1.0/git-lfs smudge %f"
git config filter.lfs.clean = "/Users/rick/p/foo/git-lfs-1.1.0/git-lfs clean %f"

Now it's reverted back to v1.1.0.
5) create a subfolder within the repository, and copy the files from step 3 into it
$ mkdir sub
$ cp fake.png sub
$ cp real.txt sub

$ gs
## master
?? git-lfs-1.1.0/
?? git-lfs-1.1.2/
?? git-lfs-darwin-amd64-1.1.0.tar.gz
?? git-lfs-darwin-amd64-1.1.2.tar.gz
?? sub/

6) create a commit and push
$ git add sub
$ git commit -m "add files in subdir"
[master c0372ff] add files in subdir
 2 files changed, 6 insertions(+)
 create mode 100644 sub/fake.png
 create mode 100644 sub/real.txt

# no LFS upload needed because those files were already uploaded in step 3.
$ git push origin master
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 341 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 0 (delta 0)
To https://github.com/technoweenie/musical-octo-meme
   5667ca0..c0372ff  master -> master

Is Desktop wiping the .git/lfs/objects directory? The only LFS command that deletes files in .git/lfs/objects is git lfs prune. However, it only deletes old objects after they've been pushed, and if they're in commits older than 3 days.
Am I missing anything else?

@technoweenie thanks for digging into this

Not sure how desktop handles empty repos...

We normally initialise a repo with a commit containing a .gitattributes file (and maybe a .gitignore).
I'll see if I can grab a log from @mponce1's install to see how we're following this behaviour in Desktop.

Looking at the logs we're trying to git lfs push origin with the new objects and then encounter the .git/lfs/objects issue:
Diamond PNG.png is an LFS pointer to 527757d3abf20082b55e9f7173cd24b4ebabfdbe84592c91658cd60a69027f62, which does not exist in .git/lfs/objects.

Run 'git lfs fsck' to verify Git LFS objects.
error: failed to push some refs to '[URL]'

This happened a couple of times - basically when we'd try to push - in that session. I'd just like to confirm whether this is related to switching releases on-the-fly, so I'll do another run-through as well before adjusting my internal DEFCON setting...

So I just ran through these steps with Git LFS 1.1.2 (without switching versions) and couldn't encounter this issue. @mponce1 I'll leave it to you how far you want to explore how much of an issue switching versions might be here...

I think the version switching is a red herring. There isn't a huge difference between v1.1.0 and v1.1.2. I'm just trying to figure out how the repository gets into this state.

Diamond PNG.png is an LFS pointer to 527757d3abf20082b55e9f7173cd24b4ebabfdbe84592c91658cd60a69027f62, which does not exist in .git/lfs/objects.

Until v1.1.0, Git LFS didn't ever delete files from .git/lfs/objects. It does now, but only through the git lfs prune command:

Deletes local copies of LFS files which are old, thus freeing up disk space.
Prune operates by enumerating all the locally stored objects, and then deleting
any which are not referenced by at least ONE of the following:

the current checkout

a 'recent branch'; see [RECENT FILES]
a 'recent commit' on the current branch or recent branches; see [RECENT FILES]
a commit which has not been pushed; see [UNPUSHED LFS FILES]
any other worktree checkouts; see git-worktree(1)

This only happens when you run git lfs prune, or git lfs fetch --prune, which I don't think Desktop is doing. This is why I'm trying to get the exact sequence of commands to try and replicate the bug in LFS.

Tried recreating with a new VM instance but didn't run into the same problem. I'll continue to look into this but will close it out in the meantime.


Add camera trackConstraints to BarcodeScanner props

Hello,
I'm creating these pull request to add a small change to props.
Adding trackConstraints to BarcodeScanner props to be used in useCamera hook.
It's usefull to define MediaTrackConstraints: https://developer.mozilla.org/en-US/docs/Web/API/MediaTrackConstraints/facingMode
for example deviceId to choose between cameras.
Thanks!

Published on version 2.1.0


Support accessibility drag/drop

It would be very helpful to add accessibility support.
Here's a reference guide https://dev.opera.com/articles/accessible-drag-and-drop/

Hi @GCheung55. This is an excellent idea. Would you be interested in working on a PR to implement it? I’m a little short on development time right now but I can help out in any way you need. Let me know what you think :)

This project is now being maintained by the team at @heroku.
To get the project healthy and maintainable again, we're doing a bit of spring cleaning of older issues and pull requests. This issue hasn't been touched in a while so we're closing it. Note that we have added some notes on accessibility to the README.
Please feel free to re-open if you'd like to resume the conversation.


Model file reduced by 90MB after removing inputs

I use the following script to remove the 2 inputs from a siamese network and the output (a cosine distance layer).
#!/usr/bin/env python

from dir.model import load_siamese_network
import sys

def load_siamese_network(filepath, include_distance=True):
    custom_objects = {
        'contrastive_loss': contrastive_loss
    }
    model = load_model(filepath, custom_objects=custom_objects)
    if not include_distance:
        # layer 0 and 1 are inputs
        tuned_model = model.layers[2]
        return tuned_model
    return model

src = sys.argv[1]
dst = sys.argv[2]
model = load_siamese_network(src, include_distance=False)

model.save(dst)

Here's the code I use to generate the siamese network from a base network: https://gist.github.com/aeec5b2a6efb1090375d4211aabbed6f
It appears to be working as expected but I was surprised to see that the saved file is twice smaller than the original one (90MB instead of 180MB). How could removing 2 inputs and a distance layer with no weights so dramatically reduce the file size?
Since this is a siamese network, both inputs share the same network + weights so removing an input shouldn't really affect the file size that much. That being said, it's possible that Keras isn't that smart about saving the model to disk and is duplicating the network weights for each input although they really are shared.
Is this what is happening? Or did I setup the siamese network wrong?

In my case, a 10 layers CNN is just 6MB whereas a 4 layers one is more than 670MB !!! I still dont understand

In both cases, you can try using model.summary() to debug what is going on.
You can also inspect the contents of the HDF5 file using the Python h5py API.

model.summary() gives the right thing. I'll see what the h5py will tell me but when I tried with hdfview, I am said that the weights are null, however when Iload the model, weights are not null but have some values. I just hope it is not randomly initialized values. But a 675MB model with hdfview also tells me it has null weights...

@fchollet is it possible that although the weights are shared for both inputs, keras is duplicating the weights in the hdf5 file?


Content cluster explorer

Find services.xml at http://localhost:19071/application/v2/tenant/default/session/2/content/ - from there, build a UI to navigate to the content clusters, where one can view schemas, metrics, and data
In a UI, the user can navigate to content clusters and see highlevel metrics, like document count. For each content cluster, link to the interface to manipulate documents.
Create a simple handler (see #16870) that parses services.xml and creates a view with content clusters, and schema(s) within these clusters.

Hi, I want to work on this issue. Can you help me through it ?

Hi, you are free to create a Pull Request. But I think this issues can be closed, as https://github.com/vespa-engine/sample-apps/tree/master/examples/operations/multinode-HA#integrations is created, we do not want to duplicate what is already in Vispana ...

Feel free to browse the issues and contribute where you can - I am sorry we cannot make recommendations ;-)


Not much help...

Document lacks detailed explanation. Dont create documents as task.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ecb6fa26-f01e-e9dd-efad-74c0898e2027
Version Independent ID: 4582bdc2-1d26-067d-4343-a63736d4bf8f
Content: Key Vault secret with template - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/key-vault-parameter.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

@Pankaj8878 - thanks for the feedback. What details are you looking for that are not in the article?

@Pankaj8878 Did you get chance to review earlier comment from @tfitzmac? Can you please provide the requested additional information so that we can assist you accordingly?

Hi,
The document needs more clarification with examples. It's so difficult to
understand the sequence of actions mentioned and why those needed etc.
Thanks.
Regards,
Pankaj
On Fri, Nov 27, 2020, 5:45 AM KrishnaG-MSFT<EMAIL_ADDRESS>wrote:

@Pankaj8878 https://github.com/Pankaj8878 Did you get chance to review
earlier comment from @tfitzmac https://github.com/tfitzmac? Can you
please provide the requested additional information so that we can assist
you accordingly?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/66677#issuecomment-734771648,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKWKNNODAFOP3Q2VBU2FRSDSR57OFANCNFSM4UCNWOIA
.

@Pankaj8878 - would it be helpful to go through a tutorial?  Here is one - https://docs.microsoft.com/azure/azure-resource-manager/templates/template-tutorial-use-key-vault.  Let us know if we need to provide any additional clarification and examples.
#please-close