Flush log file each minute

Once #4 is done, it should be possible to flush the log file each minute because the sample rate is independent from the CPU load.

Anything new about it? Its a real problem for me that the logfile isn't written while the program is running. So I can't use the received data to work with in another program.
I've also added in line 726 	setbuf(logfile,NULL); in input.c but has no effect. I'm not so deep into programming, can you explain why?

Correction: Now at the first start after a reboot you can see "--new log--" in the logfile right after start. Program exited with STRG+C, logfile deleted and dcf77pi re-run there is no "--new log--" in the file anymore.
This seems really strange for me.
Very curious to hear your explanation.

"So I can't use the received data to work with in another program." <-- I think you want to use the library (libdcf77.so) instead, dcf77pi is just a front-end. For analyzing existing logs, there is already dcf77pi-analyze.
Using setbuf(logfile, NULL) would cause each character to be flushed immediately, putting stress in SD-like cards (typically in a Raspberry Pi) or high NFS load. setbuf() has an option to flush the buffer per line, which is what we want here. (Normally a block of size BUFSIZ is allocated so the file is only updated about once every 30 minutes - 2 hours). The log file was flushed every minute by dcf77pi for a while but it turned out that this caused too much delay, confusing the reception of bit 0. That bit is used to determine the length of a 0 pulse.
With STRG+C you mean Ctrl+C? You can just press Q to exit dcf77pi as shown, it will save the log file. If you change the log file when running by pressing L the old log file will be saved before the new one is opened. dcf77pi opens existing log files in append mode, so no existing content is ever deleted.

<-- I think you want to use the library (libdcf77.so) instead
I'll take a look. A simple text file from where I can read in is probably the easiest for me (I'm very new to Linux and mostly firm with bash scripts, but not with C-programs or shared librarys).

Using setbuf(logfile, NULL) would cause each character to be flushed immediately, putting stress in SD-like cards (typically in a Raspberry Pi) or high NFS load.
Yeah I know, thats not good for the SD-Card. But strange thing is, even with this line in Code, it doesn't output immediately. I can't understand this why. And even this strange behaviour that it is writing immediately after the first start after boot "--new log--", but nothing more. The other lines appear very delayed, but also ok for me, as long as the appear within 1-2 hours.

The log file was flushed every minute by dcf77pi for a while but it turned out that this caused too much delay, confusing the reception of bit 0 (see commit b1af9e4). That bit is used to determine the length of a 0 pulse.
Very resonable, because it blocks the program. What do you think about doing the writing in another thread, like this:

open the log create --new log --, close it
call "write_log(char *)" (or simmiliar), passing one line of received chars to write out
3.create a new thread in that function, that does the writing
3.1 open log file in append mode
3.2 write out the received line
3.3 close the file
now return to the caller. There is almost no delay in the main program, so minute bit will be detected correctly.

With STRG+C you mean Ctrl+C? You can just press Q to exit dcf77pi as shown, it will save the log file.
Yeah, sorry you're right, I mean Ctrl+C. Yeah you're right with pressing Q and I want to controll the Programm from a script so I can't send Q key (or is there a solution? Btw: I've noticed sending "q" doesn't work, only "Q". Is there a special reason for case sensitivity?

you're right with pressing Q and I want  to controll the Programm from a script so I can't send Q key (or is there a solution?

Perhaps you can try the readpin program (installed in the same place as dcf77pi)? dcf77pi is really designed to be a TUI program, not a UNIX pipe.

Btw: I've noticed sending "q" doesn't work, only "Q". Is there a special reason for case sensitivity?
Yes, to make it harder to accidentally exit the program (you have to press two keys simultaneously now, or use Caps Lock).

Very resonable, because it blocks the program. What do you think about doing the writing in another thread, like this:

That's indeed what I experienced. Flushing the log file each minute at the minute should be easier with #4 finished (I believe). For now I can also flush it at second 2 of each minute, given that bits 1-14 are only for licensed Meteotime users and therefore not very interesting (I asked them if I could add a Meteotime decoder to the program/library by using their decoder chip but they refused).

Perhaps you can try the readpin program
After start, it outputs every second, but after a few seconds, it seems to hang and skips a lot of seconds. Don't know why.

For now I can also flush it at second 2 of each minute, given that bits 1-14 are only for licensed Meteotime users and therefore not very interesting
Please do not, I need these bits, because I want to decode the weather data.

(I asked them if I could add a Meteotime decoder to the program/library by using their decoder chip but they refused).
Perhaps they misunderstood you and thought your program will decode the data without chip. There is already a program that decodes the weather data with a connected chip. See https://dcf77logs.de/Software.aspx?id=000003
And even the decoded data is provided free for everyone. https://dcf77logs.de/live

And even the decoded data is provided free for everyone. https://dcf77logs.de/live

That was explicitly forbidden when I was on the phone with them, so dcf77logs is technically illegal.

Perhaps the staff had a bad day, because when you have to buy their chip to decode, then more people would do and they get money. There are even ways to decode it without their chip at all.

Problem with changed code was not working is now solved, due to different install versions I was using different versions of dcf77pi which had not the changes, I've made. Sorry for that.
However even with flushing logfile after each character, dcf77pi has no problems in detecting the correct time and bits.

Doesn't that increase the load? You could also reapply the above commit to flush the log file each minute.
Regarding Meteotime, more people buying their chip seems plausible but back in 2014 they answered:

As discussed by phone yesterday, the Meteotime-service is something totally different from DCF77. It is a privately financed, not public and not free of charge, offered data service. The Meteotime-service is provided by HKW and it just uses the DCF77-langwave signal as carrier for the meteorological information. The use of Meteotime data is only allowed with reference to a valid license contract between customer and HKW. HKW has to verify, whether a license contract with the applying company can be signed or not. HKW has to release / adjust the license contract in accordance to the nature of application.

Regarding Meteotime, more people buying their chip seems plausible but back in 2014 they answered:

Strange answer. Everyone can buy the HKW581 Chip and use the data http://arduino-projects4u.com/product/meteotime-hkw581/
But ok, they're Germans, they're sometimes very strange.

Doesn't that increase the load?

The CPU load is between 0-1 % read from a RDP connections, so this overhead is also there.
I didn' know how to revert back to the commit with flushing the logfile each minute (and perhaps that was the problem, flushing each minute is too much data at the same time, whereas flushing every char makes no problems.)
However I've created a safe way to flush the data every minute within a thread (so the main program can't block and miss a signal). Feel free to include that code into your project. Would be great if you can make the interval configurable with the json file, but it's also ok like the way now.
Everything is done in input.c (and input.h to declare function)
#include <pthread.h>
int
append_logfile(const char * const logfilename)
{
logfile = fopen(logfilename, "a");
if (logfile == NULL)
return errno;
fprintf(logfile, "\n--new log--\n\n");
pthread_t flush_thread;
pthread_create(&flush_thread,NULL,flush_logfile,NULL);
return 0;
}
`void
*flush_logfile()
{
for(;;)
{
fflush(logfile);
sleep(60);
}
}`

Using a thread might be interesting too. I might have meant "flush like file at each minute marker", which might be different from each minute in case of reception errors
I did have an email conversation with the owner of ArduinoProjects4U, I'll ask how he thinks about decoding Meteotime.

Tested the changed code now for 2 days (dcf77pi is running since then). It works perfectly. Not a single Bit was lost in that time. Before the log was flushed unpredictably and perhaps thats why I had some bit errors from time to time like
``00001011001110000100101101100000001110100__11111000000110010a60821c2.0290

Before the log was flushed unpredictably and perhaps thats why I had some bit errors from time to time like
00001011001110000100101101100000001110100__11111000000110010a60821c2.0290

It could be because of flushing, but also because of bad radio reception. dcf77pi writes a dash to the log file (and colors the corresponding bit yellow in the live view) if the pulse is too long (more than 300ms).
dcf77pi-analyze will substitute the value of the corresponding bit in the previous minute in those cases.

I finally sent the email today, let's see what happens.

According to him interpreting the plaintext is legal when using the HKW 581.

Code for flushing the log file committed, perhaps revisit this once #4 is done


Broken API links in Light.js API Docs

When I go to the Light.js package I can click Full Documentation and it takes me to the API Docs.
But when I scroll down the menu and try to click any of the API links (see screenshot below), they are all broken. The temporary fallback is to view the SUMMARY.md file that contains the same links:

Ah... you're right. It might be solved by adding a .nojekyll file here.


OSM PodSecurityPolicy

Signed-off-by: Kalya Subramanian<EMAIL_ADDRESS>
Description:
Fixes #1941

Affected area:

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Control Plane          [ ]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests                  [ ]
CI System              [ ]
Demo                   [ ]
Performance            [ ]
Other                  [ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?

Codecov Report

Merging #3299 (c055602) into main (591d8d0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3299   +/-   ##
=======================================
  Coverage   66.42%   66.42%
=======================================
  Files         165      165
  Lines        7807     7807
=======================================
  Hits         5186     5186
  Misses       2590     2590
  Partials       31       31

Flag
Coverage Δ

unittests
66.42% <ø> (ø)

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

Continue to review full report at Codecov.

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

Where  does this stands with regards to PSP deprecation ?


[WIP] Cuss

I think it’s better to pull everything in from cuss. As cuss includes all the terms here anyway. But adding something to cuss needs manual labour (to classify a term with a sureness rating). So it’s better to ask people to contribute there, because it’s hard for me to update non-English profanities.

Supersedes GH-18.

Sweet, I’ll merge this when cuss is released, as that involves a fix to the sorting as well


Change button label from 'Add XYZ' to 'Save XYZ'

 Change the second "add" button for mentor, org to "save" to provide clarity that this step is needed for the action to be completed


Grading Issue Isabel

Individual Review "Isabel" grading "Nandan"

[ ] Individual should show that they were key contributor and example to team.  This includes their participation in ideas, plans, creating individual issues, providing code commits to project, crossover grading participation, being on task and positive example in the classroom.

Individuals Video, Issue(s), Commits(s)

[ ] Video in CPT caption style , includes Web demo of key contribution to project, 1 minute
[ ] Issue(s) that show plans/progress to team objectives
[ ] Highlights of key commit(s) in Issues, summarizes code contributions
[ ] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks

Per check.
0.55 not attempted/no check
0.7 attempted, incoomplete, but some runtime
0.8 mastery and runtime
0.9 above and beyond.
Freeform comment.
Provide positivies and growth summary.
Justify or comment on final score.
Be sure to provide extra details on anything below 0.7 average or above 0.8.
https://jplip.github.io/frontTri2/ Check out Binary Music/Binary Challenge

Video is in CPT style and its very good although the quality of the video is a little bad. The code is working perfectly and I think its very creative to convert binary to music. Logic Gate usage was also pretty creative with badges earned for answering questions. Creativity definetly helps here. Github analytics shows consistent participation. Overall, its a pretty good project.
0.91/1


Acceptance tests

Added a list of acceptance test that should be addressed in implementation and design of transfer manager. Most of these tests were taken from the CLI and boto3. Currently, an x indicates it has been accounted for and has been tested in some fashion. Hopefully this list will eventually get moved to the docs where we can link to which tests satisfy the acceptance test.
cc @jamesls @JordonPhillips

:shipit:  I think this looks like a good start.

:shipit:


Exponent Label missing

Hello,
Thank you for continuing this great tool. I have been using it for more than 10 years.
When using the latest export_fig version, the 'Exponent Label' is missing in PDF, EPS and PNG, though there are no problems at a co-worker system.
My system: Win10 64, matlab2013b
Co-worker system: Win10 64, matlab2016b

test.pdf

Fixed (the cause was due to an internal Matlab bug - the exponent is removed when the axes *TickMode is set to manual)


Feature request: Support the XDG Base Directory Specification

Currently the configuration files, binary, cache files etc are placed in a hidden folder in the user's home directory: ~/.platformsh. This is not following the XDG standard which is used across all common operating systems (Linuxes, Unixes and most Windows shells).
It would be great if we could default to the right locations ($XDG_CONFIG_HOME for the configuration, $XDG_STATE_HOME for state.json, $XDG_CACHE_HOME for cache files etc).
To provide backwards compatibility, we could check if ~/.platformsh exists, and use it if it does, but new installations should follow the standard.
For a good overview of what the standard entails, see https://wiki.archlinux.org/title/XDG_Base_Directory

I recognise it's nice to comply with specifications in general. But is there another practical advantage?
There's a support advantage when everyone has files in the same place regardless of configuration or OS. There's also somewhat an advantage of locating the binaries, cache, state, and config in the same place (easy to delete), although also this can be a disadvantage (not easy to use separate filesystems, e.g. r/o for bin and r/w for cache).
As well as backwards compatibility, I had particularly wanted to avoid the potential for installation resulting in multiple copies of the application in different locations. Tools such as Drush and PHP itself suffer from this (frequently PHP has been installed via MAMP and via Homebrew, at different versions and with different extensions enabled depending on the user / PATH).
Maybe this could be done carefully for the next major version alongside a reworking of how the app is packaged/installed.

Maybe this could be done carefully for the next major version alongside a reworking of how the app is packaged/installed.

A lot of this has happened now since https://github.com/platformsh/cli and all packaging/installation decisions are happening there


Add support for javax.ws.rs.core.Application. Part I.

should work:
@GET
public String getAllOrders(@Context Application app) {
    Map<String, Object> properties = app.getProperties();
}

RoutingConfig internally should keep javax.ws.rs.core.Application instance.
RoutingConfig should provide methods to specify providers from Class

e.g. addBodyWriter(SimpleGsonBodyWriter.class)

RoutingConfig should provide new method putApplicationProperty, related to javax.ws.rs.core.Application -> getProperties() method

done.


Proposal: Unify labelling across adopt github repositories

We've previously had discussions on jenkins machine labelling, but several of the AdoptOpenJDK github repositories use labels for the different OSs and architectures. In openjdk-infrastructure I've tried to standardise these using prefixes for some of the variants such as provider:azure or os:aix or arch:aarch64
openjdk-test has some of the arch: prefixes but not os: and build does not currently use prefixes and has the somewhat ambiguous aarch for aarch64 (presumably to contrast with arm for 32-bit?) as well as separate p-linux, x-linux z-linux (which I'd suggest we replace with separate os:linux arch:ppc64le etc.)
I suggest modifying across all of the relevant repos so that we use consistent naming:

os: prefixes: linux aix macos windows solaris freebsd (and anything else I've missed!)
arch: prefixes; x64 (and possible x32/x86/x86-32 if required, could also use x86-64 instead)  ppc64 ppc64le arm32 (or aarch32) aarch64 (or arm64 sparc (or sparcv9) s390x (We have a list in https://github.com/AdoptOpenJDK/openjdk-infrastructure/blob/master/ansible/plugins/inventory/adoptopenjdk_yaml.py#L42 as well but that possible needs updating and it would be good to be consistent
provider: Likely only required for the infrastructure repo but should match these

Where I've listed alternatives in brackets, those are not my personally preferred options)
For awareness and review @M-Davies @andrew-m-leonard @smlambert @aixtools @gdams @karianna

Also see discussion in https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/93

Also see discussion in https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/93

arch: prefixes; x64 (and possible x32/x86/x86-32 if required, could also use x86-64 instead) ppc64 ppc64le arm32 (or aarch32) aarch64 (or arm64 sparc (or sparcv9) s390x (We have a list in https://github.com/AdoptOpenJDK/openjdk-infrastructure/blob/master/ansible/plugins/inventory/adoptopenjdk_yaml.py#L42 as well but that possible needs updating and it would be good to be consistent

I've always found x32 to be more expressive and easier to skim than the others there so my preferred list would be:

x64 and x32
ppc64 and ppc64le
arm and arm32 (do we actually need the version number appended to the end like so 'armv7', 'armv8'?)
aarch64 and aarch32
s390x
sparc and sparcv9
riscv

...but I understand that a lot of our code uses x86-32 right now so I won't demand this from whoever choses to give this issue a crack

arch: prefixes; x64 (and possible x32/x86/x86-32 if required, could also use x86-64 instead) ppc64 ppc64le arm32 (or aarch32) aarch64 (or arm64 sparc (or sparcv9) s390x (We have a list in https://github.com/AdoptOpenJDK/openjdk-infrastructure/blob/master/ansible/plugins/inventory/adoptopenjdk_yaml.py#L42 as well but that possible needs updating and it would be good to be consistent

I've always found x32 to be more expressive and easier to skim than the others there so my preferred list would be:

x64 and x32
ppc64 and ppc64le
arm and arm32 (do we actually need the version number appended to the end like so 'armv7', 'armv8'?)
aarch64 and aarch32
s390x
sparc and sparcv9
riscv

...but I understand that a lot of our code uses x86-32 right now so I won't demand this from whoever choses to give this issue a crack

Also see discussion in AdoptOpenJDK/openjdk-infrastructure#93

Thanks - that was the "previousl had discussion" issue that I hadn't yet looked up to reference it :-)

Also see discussion in AdoptOpenJDK/openjdk-infrastructure#93

Thanks - that was the "previousl had discussion" issue that I hadn't yet looked up to reference it :-)

Hmmm you've send you want all of arm arm32 aarch64, aarch32, sparc and sparcv9 - is that what you means? We should attempt to standardise on one for each of those three architectures (Note that riscv which I missed from my list could have riscv64 as an alternative.
Re armv7 armv8 those are effectively synonims for arm32/aarch32 and arm64/aarch64 respectively so should be deprecated in favour of whatever we choose.

 We should attempt to standardise on one for each of those three architectures (Note that riscv which I missed from my list could have riscv64 as an alternative.
Re armv7 armv8 those are effectively synonims for arm32/aarch32 and arm64/aarch64 respectively so should be deprecated in favour of whatever we choose.

We have to also keep in mind that these arch values will be used the jenkins job name creation

Just to be clear, we don't use the values from github issue labels directly in the jobs right? So you're just saying we should try and make them consistent with the jobs for convenience (a good goal obviously)?
One area where we do have a problem is with arm in particular, since the test suites etc. use different namings (a known issue that Shelley and I have discussed before) - the build jobs use arm for arm32, test jobs are named with aarch32 so we already have an inconsistency.

We have to also keep in mind that these arch values will be used the jenkins job name creation

Just to be clear, we don't use the values from github issue labels directly in the jobs right? So you're just saying we should try and make them consistent with the jobs for convenience (a good goal obviously)?
One area where we do have a problem is with arm in particular, since the test suites etc. use different namings (a known issue that Shelley and I have discussed before) - the build jobs use arm for arm32, test jobs are named with aarch32 so we already have an inconsistency.

While I would directly benefit from the build scripts using the same labels as test and having a standard set across the project, I also think that having all the labels be configurable by third parties without hack and slash would be beneficial.

While I would directly benefit from the build scripts using the same labels as test and having a standard set across the project, I also think that having all the labels be configurable by third parties without hack and slash would be beneficial.

@AdamBrousseau Devils advocate question: What would be the reasons for wanting to diverge? Compatibility with someone's own existing labels or something else?

@AdamBrousseau Devils advocate question: What would be the reasons for wanting to diverge? Compatibility with someone's own existing labels or something else?

If another third party already had their own label schema I think it would be beneficial to them if our scripts were configurable.

If another third party already had their own label schema I think it would be beneficial to them if our scripts were configurable.

 We should attempt to standardise on one for each of those three architectures (Note that riscv which I missed from my list could have riscv64 as an alternative.

A standard for each would be ok for github labels but not for jenkins names (in my opinion) as that would make identifying jobs more difficult.

Re armv7 armv8 those are effectively synonims for arm32/aarch32 and arm64/aarch64 respectively so should be deprecated in favour of whatever we choose.

In that case I choose arm32 and arm64 😊

Just to be clear, we don't use the values from github issue labels directly in the jobs right? So you're just saying we should try and make them consistent with the jobs for convenience (a good goal obviously)?

No we don't use the github issue labels but we do use similar ones (ideally the github issue labels and jenkins job labels should be the same). What I'm referring to is how we construct the job names: https://github.com/AdoptOpenJDK/openjdk-build/blob/b35e817efaa66635e9c21ec197476a8f22ceca6b/pipelines/build/common/config_regeneration.groovy#L532

Hmmm you've send you want all of arm arm32 aarch64, aarch32, sparc and sparcv9 - is that what you means? We should attempt to standardise on one for each of those three architectures (Note that riscv which I missed from my list could have riscv64 as an alternative.

A standard for each would be ok for github labels but not for jenkins names (in my opinion) as that would make identifying jobs more difficult.

Re armv7 armv8 those are effectively synonims for arm32/aarch32 and arm64/aarch64 respectively so should be deprecated in favour of whatever we choose.

In that case I choose arm32 and arm64 😊

Just to be clear, we don't use the values from github issue labels directly in the jobs right? So you're just saying we should try and make them consistent with the jobs for convenience (a good goal obviously)?

No we don't use the github issue labels but we do use similar ones (ideally the github issue labels and jenkins job labels should be the same). What I'm referring to is how we construct the job names: https://github.com/AdoptOpenJDK/openjdk-build/blob/b35e817efaa66635e9c21ec197476a8f22ceca6b/pipelines/build/common/config_regeneration.groovy#L532

In that case I choose arm

Just to throw a(nother) spanner in the works, I would probably go for aarch64 since that's what uname -m returns on those systems (xLinux gives x86_64 for reference). On most of the arm32 system it gives armv7l so normally I'd choose that, but I suspect most people wouldn't find that as clear ...

In that case I choose arm

Just to throw a(nother) spanner in the works, I would probably go for aarch64 since that's what uname -m returns on those systems (xLinux gives x86_64 for reference). On most of the arm32 system it gives armv7l so normally I'd choose that, but I suspect most people wouldn't find that as clear ...

Was curious - what would uname -m return on AIX. Neither ppc, nor ppc64. Nope - some number - perhaps related to the processor model.
Still curious: where did ppc and ppc64 actually come from? Was that from back when AIX was ported to the PS3 - that was built on the POWER4 chip? And also linux ported to the PS3 - and likely the imac models built on the POWER4 (or was it POWER5 - for both).
I guess everyone knows what it means (ppc64) - but I doubt that is the abbreviation used to document the processor ABI.
At least power and ppc64 are both 5 characters. :)

Was curious - what would uname -m return on AIX. Neither ppc, nor ppc64. Nope - some number - perhaps related to the processor model.
Still curious: where did ppc and ppc64 actually come from? Was that from back when AIX was ported to the PS3 - that was built on the POWER4 chip? And also linux ported to the PS3 - and likely the imac models built on the POWER4 (or was it POWER5 - for both).
I guess everyone knows what it means (ppc64) - but I doubt that is the abbreviation used to document the processor ABI.
At least power and ppc64 are both 5 characters. :)

Linux has always used ppc64 or ppc64le so it makes sense to be consistent in the architecture name (I /think/ it was ppc32 on a 32-bit Linux on POWER.

Linux has always used ppc64 or ppc64le so it makes sense to be consistent in the architecture name (I /think/ it was ppc32 on a 32-bit Linux on POWER.


Fix typo in README.md

Thank you for your pull request.
It looks like this may be your first contribution to an Oro, Inc. open source project, in which case you'll need to sign a Contributor License Agreement (CLA) at http://www.orocrm.com/contributor-license-agreement/
If you've already signed the CLA, it's possible we don't have your GitHub username or you're using a different email address. GitHub uses the email address you set in your local Git configuration to associate commits with your GitHub account. Please sign the CLA again using the correct GitHub username and email address or see this help article on setting the email on your git commits.
Once you've signed the CLA, please allow for some time for the submission to be processed.

Hi, @alex-kuzmenko. Thank you very much for your contribution! Your PR was merged to development branch and soon you'll see it at master.


Reduce boolean expressions to DNF

yes

After careful consideration, I think this issue can be closed. @Sedictious feel free to close under my authority!


High CPU usage with BD Discord  [Bug]

Describe the Bug
i have noticed that my discord is going from normaly 2-4% cpu ussage
but with installed BD discord its going to 20-50% Usage + the desktop manager or dwm usage is going up too i regoniced this on my both PC´s!
To Reproduce
idk use bd discord
Expected Behavior
just a little higher usage and not raping my CPU
Screenshots

8-12% (not normal)
Discord Version

Additional Context
My Systems:
System 1:
CPU: Ryzen 5 1600 Stock 3.2ghz
GPU: GTX 970 MSI
RAM: 16gb 2933mhz  cl 16
BOARD: Asus Prime 370x
OS: Windows 10 Pro
SSD 960 256GB
3TB Harddisk Toschiba p300
System 2:
CPU: Ryzen 5 2600 with OC 4.02ghz
GPU: GTX 980 TI SC EVGA
RAM: 16gb 2933mhz  cl 16
BOARD: B450 Aorus Elite
OS: Windows 10 Pro
SSDs 960 256GB,2x MX500 1TB

Having the same issue as well.

This is generally caused by your theme being too intensive with animations, transitions, etc. A few things can help with this, the first is use a different theme that doesn't have a ton of animations or transitions. Another thing is enable reduced motion in Discord Settings > Accessibility, and disable Hardware Acceleration in  Discord settings > Advanced if your GPU usage is also high.

the problem is i alreaddy tried all these steps and it dosnt help the resson why i postet it here

Does this still occur if you remove all themes and plugins?

Having the same problem as well

Does this still occur if you remove all themes and plugins?

yep with plugins is a little bit more

Having the same problem as well

i feel you bro

I cannot reproduce this with no plugins or themes. Currently using 0.1%

I cannot reproduce this with no plugins or themes. Currently using 0.1%

both systems are AMD Ryzen
if you need some logfiles or details etc. tell me i will send.

On my computer, which is running a Ryzen 2600X/3600 (recent upgrade) + 1060 6GB, I don't have this issue. Just for the record to show that Ryzen processor is not the issue.

I tried on my Ryzen build as well as my intel-based laptop and could not reproduce the issue on either.

Many crashing, memory, and cpu issues have been fixed with the latest update.


grpc c++ client ---- Is multithreading used for handling epoll events?

Is multithreading used for handling epoll events?
epoll events ：Including: HTTP message, sending data, receiving data, metadata, etc。
These operations require a lot of resources and require multithreading to improve performance。
Is there an implementation in the source code? Where is it?

Please refer to the Stackoverflow or Google Group for questions about gRPC implementation or usage.


Wrong line in compilation error message in macro expansions

When declaring many properties in Object#property macro, if there is a compilation issue triggered by the expanded code the location pointed by the exception is misleading.
file: foo.cr
class Foo
  property x, y : Int32
end

Foo.new

The following error shows there is an issue with line 12, yet the file is 5 lines long.
$ crystal build foo.cr
Error in macro 'property' /usr/local/Cellar/crystal-lang/0.18.7_1/src/object.cr:667, line 12:

  1.
  2.
  3.         def x
  4.           @x
  5.         end
  6.
  7.         def x=(@x)
  8.         end
  9.
 10.
 11.
 12.         @y : Int32
 13.
 14.         def y : Int32
 15.           @y
 16.         end
 17.
 18.         def y=(@y : Int32)
 19.         end
 20.
 21.
 22.

        @y : Int32
        ^~

instance variable '@y' of Foo was not initialized in all of the 'initialize' methods, rendering it nilable

https://play.crystal-lang.org/#/r/172u

The "line 12" bit is showing what line of the expanded macro snippet the exception is in, not the place in the original file.


Rearrange list of standards

On this page, instead of a bunch of square buttons, make a list of standards organized as follows. Note the starred items. Note also some minor renaming (e.g. Experiments to Experiment) that can be done along with this change as long as it doesn't break the checklist generator.
General
General Standard
Engineering Research
Mixed Methods
Qualitative
Action Research
Case Study
Grounded Theory
Qualitative Survey
Quantitative
Benchmarking
Data Science
Experiment
Longitudinal
Optimization Study
Quantitative Simulation
Questionnaire Survey
Repository Mining
Literature Review
Case Survey
Critical Review*
Meta Analysis*
Meta Synthesis*
Systematic Review*
Other
Meta Science
Replication
*We're in the process of dividing the Systematic Review Standard into Critical Review, Meta Analysis and Meta Synthesis. Work with what's there.

Should this be formatted as a side menu or kept at the top of the page?

I think it should be at the top of the page, but written like a table of contents instead of a bunch of boxes.

@drpaulralph Done in the PR above. You can check a live example at https://eschltz.github.io/standardstest/docs/


Add support for Artifact Hub

Helm Hub has gone. This adds back in the support in the form of Artifact Hub, which replaces Helm Hub

Codecov Report

Merging #4646 into master will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4646      +/-   ##
==========================================
- Coverage   57.87%   57.86%   -0.01%
==========================================
  Files        1061     1061
  Lines       34426    34432       +6
  Branches     4901     4900       -1
==========================================
+ Hits        19923    19925       +2
- Misses      14503    14507       +4


[Intel MKL] BFloat16 operator enabling - round 4

This PR enables BFloat16 version of AddN, FusedBatchNorm, Reshape, Slice,
and Transpose.

@nhasabni can you please resolve conflicts.

@penpornk thanks for approval!


Use Lib Phonenumber

It would be great to autoformat the number with https://github.com/google/libphonenumber and reject everything which is not type=mobile.  Also the nunber format can be normalized with this.

Rejecting mobile numbers would have to be an optional setting, I think. In many cases land lines will probably work as some providers automatically create a phone call and read the SMS text.

maybe add a config option to optionally add a "number type filter" -> add a comma seperated list of options which are valid:
see: https://github.com/google/libphonenumber/blob/b75f2937daea4e6a67cb91de7325061938df37bd/metadata/src/main/java/com/google/i18n/phonenumbers/metadata/Types.java#L22
so I would like to add a filter: MOBILE, FIXED_LINE_OR_MOBILE, PAGER
or optionally, there is a function for this: https://github.com/google/libphonenumber/blob/b75f2937daea4e6a67cb91de7325061938df37bd/java/carrier/src/com/google/i18n/phonenumbers/PhoneNumberToCarrierMapper.java#L117

https://github.com/netzbegruenung/keycloak-mfa-plugins/pull/94


t2t_trainer resume from checkpoint

my training was interrupted by a memory problem. i would like to resume training from existing checkpoint files, but i fail to see how to do this with the current t2t_trainer code.

works out of the box. duh.. sorry


[Bug]: PDF to DOCX= Error 504

Installation Method
Docker
The Problem
From your website, and from local docker I tested various PDFs to DOCX and all returned ERROR 504.
And it didn't provide extra details.
Version of Stirling-PDF
0.31.1
Last Working Version of Stirling-PDF
No response
Page Where the Problem Occurred
No response
Docker Configuration
No response
Relevant Log Output
No response
Additional Information
No response
Browsers Affected
No response
No Duplicate of the Issue

[X] I have verified that there are no existing issues raised related to my problem.

504 is a timeout issue caused by nginx settings or similar proxies/server timeouts
The website is intended as demo and as such is not set up for long processes
For local there may be some configs you need to setup


Dead Link

The destination of the link "How to Use The Same External Ethernet Adapter For Multiple SCCM OSD" is dead, would this be updated to an archived version or to a more recent source please.

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

ID: 5cd6c1f5-529c-4b6a-6d70-6a091df10f3e
Version Independent ID: df97fced-4167-f5d8-8643-50cbb1ba69e4
Content: Ethernet adapters and Surface deployment (Surface) - Surface
Content Source: devices/surface/ethernet-adapters-and-surface-device-deployment.md
Product: w10
Technology: windows
GitHub Login: @Dansimp
Microsoft Alias: dansimp

An independent contributor will publish a PR for the dead link. Thank you.

@illfated @RAJU2529 i don't see any issue with adding the link you found as replacement. It's on a official Microsoft domain, written by a Microsoft employee and it addresses the issue. I'll create a PR and ad it.

@VLG17 . I wll be waiting for the result. If the new link is merged means, if I create on coming PR , I will consider techcommunity also.

(Ref. PR #6722 )

Closing via #6722. Thank you.


Move to signing service v2

Note: you'll find the updated username and password in your lastpass. both should be treated as secure variables in your build system.

@onovotny,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@onovotny should this repo also be updated https://github.com/cake-build/bakery?

@mholo65 Yes, didn't see that, but should be the same set of changes. Anywhere you are signing with the existing service/config should be moved over.
BTW, the service does support VSIX's if you have any addin's/templates.

@onovotny thanks! I’ll update that one then.
Do we sign VSIX packages? @gep13 @agc93?

@mholo65 no, we aren't currently signing VSIX packages.  We probably should.  Both the Visual Studio and Visual Studio Code packages.

Sign all the things! :)

@onovotny your changes have been merged, thanks for your contribution 👍

@onovotny @devlead was there a linked issue for this PR?


microsite - step 2 - add modest amount of initial content

closed by https://github.com/zio/zio-dynamodb/pull/124 and https://github.com/zio/zio-dynamodb/pull/127


Ensure README is up to date for a sample app

After Eric has rad_hoc_rails stabilized inside of his app, we should comb through the README and make sure it works on a standard app.
This is pretty much the case with the test_app in the spec folder, but I'd like to run through the whole thing with a fresh Rails app.

I see Eric contributing. I'm considering this money in the bank!


fix: back navigation from details page navigates to locale-home

HH-323.
The default path was just the current locale, so it was added to current path.
It should have a beginning slash, so it would become an absolute path.

Sports-Helsinki branch is deployed to platta: https://liikunta-pr423.dev.hel.ninja :rocket::rocket::rocket:

Hobbies-Helsinki branch is deployed to platta: https://harrastukset-pr423.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://liikunta-pr423.dev.hel.ninja :laughing::tada::tada::tada:

Events-Helsinki branch is deployed to platta: https://tapahtumat-pr423.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://harrastukset-pr423.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://tapahtumat-pr423.dev.hel.ninja :laughing::tada::tada::tada:

VENUE GRAPHQL PROXY is deployed to platta: https://venue-graphql-proxy-pr423.dev.hel.ninja :rocket::rocket::rocket:

EVENTS GRAPHQL PROXY is deployed to platta: https://events-graphql-proxy-pr423.dev.hel.ninja :rocket::rocket::rocket:


feat: test

Description

Related Issue

Types of changes

[ ] Docs change / Dependency upgrade
[ ] Bug fix
[ ] New feature / Improvement
[ ] Refactoring
[ ] Breaking change

Checklist

[ ] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

!canary


Register

@JuliaRegistrator register()

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/2218
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" b29fa2d0bdcff27b71b146f92493ab7f34758d90
git push origin v0.1.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/2349
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.1 -m "<description of version>" 92c15e2b5051b8d80336c5f9e81a89e826c0f547
git push origin v0.1.1

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/7304
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.2 -m "<description of version>" c65b3687a43947f7cee8b65f423e6da6fc0e7e76
git push origin v0.1.2

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/12083
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" f29d70a7950444aefafc85f59796323251704e82
git push origin v0.2.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/13043
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" 16c2b72c3423eb41d29338e62eb1d9d31160284c
git push origin v0.3.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/13941
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.1 -m "<description of version>" 61d0145041edf628dd5e200a12e409db969996c3
git push origin v0.3.1

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/15125
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.2 -m "<description of version>" 167f49c6c01ff4244ed3c88bd29d7e2061be0e33
git push origin v0.3.2

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/16771
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.3 -m "<description of version>" 9dacc1c4046525e53f9aad84ff5b45beab52d13d
git push origin v0.3.3

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/32445
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.4 -m "<description of version>" 4aca081e2779cfd0d652c57fdb358f5c783e5a45
git push origin v0.3.4


Unable to add more than one free upgrade

The docs seem to indicate that more than one free upgrade can be added, but I'm not able to add more than one.

Hi there.
I'm not sure exactly what you mean here. Can you give an example?

I think I was trying to add both integrated astro mech and guidance chips - both zero cost.
From: Graham Gilchrist<EMAIL_ADDRESS>Sent: Tuesday, September 04, 2018 6:36 PM
To: grahamgilchrist/hotac-squad-builder
Cc: indyrcpilot; Author
Subject: Re: [grahamgilchrist/hotac-squad-builder] Unable to add more than one free upgrade (#173)
Hi there.
I'm not sure exactly what you mean here. Can you give an example?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/grahamgilchrist/hotac-squad-builder/issues/173#issuecomment-418539947 , or mute the thread https://github.com/notifications/unsubscribe-auth/Ajn47cDPFEvW7L7Lg1jRWx3K7Q6V9Svbks5uXwBkgaJpZM4SprDc .  https://github.com/notifications/beacon/Ajn47bBMlvYnWY6EpF2dFIgd3bx1_t70ks5uXwBkgaJpZM4SprDc.gif

HI. Integrated astromech is included by default in the xwing build as an automatic "free upgrade". Guidance chips requires use of a modification slot and can be equipped as a modification.
Here's a screenshot of this working:

This all seems to be working as expected here. Unless there's more feedback, I'll close this issue?

Thanks for the clarification... per your other email, go ahead and close this issue.
Chuck
From: Graham Gilchrist<EMAIL_ADDRESS>Sent: Friday, November 16, 2018 11:30 AM
To: grahamgilchrist/hotac-ship-builder
Cc: indyrcpilot; Author
Subject: Re: [grahamgilchrist/hotac-ship-builder] Unable to add more than one free upgrade (#173)
HI. Integrated astromech is included by default in the xwing build as an automatic "free upgrade". Guidance chips requires use of a modification slot and can be equipped as a modification.
Here's a screenshot of this working:
https://user-images.githubusercontent.com/632974/48634160-d5822600-e9bc-11e8-92db-e11595dc5db4.png image
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/grahamgilchrist/hotac-ship-builder/issues/173#issuecomment-439448673 , or mute the thread https://github.com/notifications/unsubscribe-auth/Ajn47eKZtMgK8O4fUSHbgyzXsfXtgefOks5uvuf_gaJpZM4SprDc .  https://github.com/notifications/beacon/Ajn47bQnj-oDCW3J8kFPsHxSCcyKYE-Mks5uvuf_gaJpZM4SprDc.gif


Run postmark on Cloudflare workers

Cloudflare workers runs v8 js environment with webworkers api.
It doesn't have full node APIs which axios is making use of.
Instead, it has its own implementation of fetch api that can be used.
In order to support postmark.js in this environment, you'd need a way to inject http-client rather than using axios hard-coded.
Cloudflare is a widely used serverless environment. Would be great to have this option.

Hi @danbars
since the latest version of the library 3.0.1, although we do not encourage doing this, it's possible.
For node-fetch for example can look like this with implemented http client contract for example:
const fetch = require("node-fetch");
import * as postmark from "postmark";
import {ErrorHandler} from "postmark/dist/client/errors";

const client: postmark.ServerClient = new postmark.ServerClient("token");

class HttpClientNew extends postmark.Models.HttpClient {
  public client:any;
  private errorHandler: ErrorHandler;

  public constructor(configOptions?: postmark.Models.ClientOptions.Configuration) {
    super(configOptions);
    this.errorHandler = new ErrorHandler();
  }

  public initHttpClient(configOptions?: postmark.Models.ClientOptions.Configuration): any {
    this.client = fetch.default;
  }

  public httpRequest<T>(httpMethod: postmark.Models.ClientOptions.HttpMethod, path: string, queryParameters: ({} | object),
                        body: (null | object), requestHeaders: any): Promise<any> {

    let that = this;
    return this.client(`${this.getBaseHttpRequestURL()}/${path}`, {
      method: httpMethod,
      headers: requestHeaders,
      body: JSON.stringify(body)}).then(async function (response:any) {
        if (!response.ok) {
          let dataJson = await response.json();
          await Promise.reject(that.errorHandler.buildError(dataJson.Message,dataJson.ErrorCode, response.status));
        } else {
          return response.json();
        }
    });
  }
}

client.httpClient = new HttpClientNew();

In order to use your custom http client you will need to handle requests and errors to provide library compatible errors and response in json format. One thing to keep in mind is that although this is possible now, we do not provide support for it, since it can completely alter the behaviour of the library and is out of the scope of our verifications.


Create a top-level claim that pertains to your high-risk critical security property (from HW #2)

The Nexcloud Mail app is acceptably secure


How to do multiple imports of a third party component

Hi @kirillzyusko , thank for the helpful library. But got a question as a first time user.
I need to import a third party component in different files by different components, but not sure which is best way to do so.
For example:
option 1)
File A:
const ThirdPartyComponent = register({ require: () => require('rn-third-party-library') });
<ParentComponentA >
{ThirdPartyComponent()}
</>

File B:
const ThirdPartyComponent = register({ require: () => require('rn-third-party-library') });
<ParentComponentB >
{ThirdPartyComponent()}
</>

option 2)
index.ts:
export const ThirdPartyComponent = register({ require: () => require('rn-third-party-library') });
File A:
<ParentComponentA >
{ThirdPartyComponent()}
</>

File B:
<ParentComponentB >
{ThirdPartyComponent()}
</>

Could you advise which option should be taken or any better solution?

Hi @SamuelGuNUAA
For me second option looks more preferable, since you will have less code duplication :) I would recommend you to go with this option.
Though it's important to remember, that if you are trying to make some libraries lazy-loadable (such as react-native-reanimated, react-native-gesture-handler) - it may break your app (especially in release mode) 🙂


Migration to offical action

https://github.com/marketplace/actions/build-and-push-docker-images

baef20786d9366e7b244d36054c64abd908eb901


Fixed puppet enterprise 404 link

Can one of the admins verify this patch?

CLA signed by all contributors.

Hi @pranjal9599 thanks for your contribution! Can you preface your git commit summary (in 2efcc77) with (docs) and force push to your topic branch?


Add showing optional modifier (?)

Provides more information about property.

Looks good!
Could you add one  example?
i.e.: secondaryWeapon?: WT to the Viking class in the demo folder
https://github.com/demike/TsUML2/blob/5e583a06f983a6b8ced730b825d780bdf528aeeb/src/demo/viking.ts#L9

Many thanks for the nice contribution!


Improve method unmaskValue, checked if mask has value, before apply it

Fixes issue #84

Bug’s reason:
When ng-required is set up, the following code is executed:
var originalIsEmpty = controller.$isEmpty;
controller.$isEmpty = function(value) {
 if (maskPatterns) {
   return originalIsEmpty(unmaskValue(value || ''));
 } else {
   return originalIsEmpty(value);
 }
};

But the conditional "if (maskPatterns)" always is true, because maskPatterns is set to [];
When unmaskValue method is executed without mask, always return "", because maskPatternsCopy does not have a value.
function unmaskValue(value) {
  var valueUnmasked = '',
				maskPatternsCopy = maskPatterns.slice();
  // Preprocess by stripping mask components from value
  value = value.toString();

  angular.forEach(maskComponents, function(component) {
	value = value.replace(component, '');
  });
  angular.forEach(value.split(''), function(chr) {
	if (maskPatternsCopy.length && maskPatternsCopy[0].test(chr)) {
	  valueUnmasked += chr;
	  maskPatternsCopy.shift();
	}
  });
  return valueUnmasked;
}

In other places works because before of the call, unmask is checked if the variable maskProcessed is true, but in controller.$isEmpty doesn't check that.
Solution.
There are many solutions, but I think the best is always unmaskValue check if it has a mask or not.. Before to apply it, like this.
// Empty mask, so don't try to apply mask, just return the value
if (maskPatterns.length === 0) {
  return value;
}

Looks good, thanks!

I have another suggestion:
I've created a plunker with your example, because it's best to other people see how the directive works without download the source code.
I suggest that you put it in help page.
http://plnkr.co/edit/egXuGTrDF2UcEja5ITyj?p=preview

If you are going to do that you might as well just have the check at the beginning of the function and skip the rest of the code. Since if there are no maskPatterns, then there are no maskComponents to try and strip either.
Also, why not modify the $isEmpty function? That seems like a more logical place to make this change as I don't think unmaskValue should even be called unless the maskPatterns and/or maskComponents arrays have a non zero length.

@lukepfeiffer10, I think the best place to put this validation is within the unmaskValue method, not $isEmpty, Who need to ensure that everything is correct is the method itself, no other
About putting the validation in the first statement... I didn't do that, because I wasn't sure that maskComponents don't change other things
Due to this, I tried to explain everything I've done. Feel free to change something.
Regards

@RenatoRC I can understand where you are coming from, but what you discovered is actually a bug in the $isEmpty function. The only time that the code will hit the else block is before processRawMask is run for the first time (which happens almost immediately rendering the else block mostly useless). This is because the maskPatterns variable gets set in the processRawMask function to [].
Also, with an empty mask the processRawMask function sets maskProcessed to false which then makes the initialization function call uninitialize. So, for the case of the ui-mask being empty the ui-mask code is not initialized. Based on this information I think it would be best to go this route:
var originalIsEmpty = controller.$isEmpty;
controller.$isEmpty = function(value) {
  if (maskProcessed) {
    return originalIsEmpty(unmaskValue(value || ''));
  } else {
    return originalIsEmpty(value);
  }
};

Ensuring that the $isEmpty function knows there has been no mask processed and thus should not call the unmaskValue function.

@lukepfeiffer10 Yes, There are a bug in $isEmpty,
I agreed with your suggest, just to change the variable maskPatterns to maskProcessed, its works, like this plunker
http://plnkr.co/edit/BoYPUOnjAkfOIeFXS5iP?p=preview
However, there are other way to solve that. We can put the validation inside the unmaskValue, just ensure that it'll always works. If someone call them without check if maskProcess is true, it will works anyway.
This plunker show up it.
http://plnkr.co/edit/xSeSXGEQhTQJDTjlx7Jx?p=preview
What do you prefer?
I'm very grateful about your suggest and our discussion here.

@RenatoRC My preference is to have the check changed in the $isEmpty function because if there is no mask defined then we shouldn't be running the unmaskValue function.
If anyone else reads this maybe they have an opinion as well but this seems like the only case where unmaskValue is called without a mask being defined and really it shouldn't even be doing that anyway.

@lukepfeiffer10
How I can ignore this pull request?
I'll chang the $isEmpty, how you suggested and do a pull request again. Or maybe, Can you changed the variable and do a new pull request?

@RenatoRC I believe you can make the new change and commit on your local branch and then do git rebase -i HEAD~2 and just delete the previous commit.
This should erase that commit from your local history. Then I think from there you just have to push your branch and the PR should update. However, if you have troubles pushing the local branch do a forced push and it will rewrite the remote branch history to match your local branch.
Hopefully that makes sense... If not I can submit a separate PR later.

@RenatoRC Finally got around to making a new PR for this issue #93. Sorry about the delay.

@lukepfeiffer10 Thank you very much about new PR.

Merged #93 instead of this one


New text when user runs "hossted" with no command

replace A brief description of your application with Hossted CLI v0.1.7 - for help contact us at<EMAIL_ADDRESS>("v0.1.7" should contain the actual version of course)

Should be fixed in v0.1.8. Will reassign when it is released.

Implemented in 0.1.8, please check

confirmed to work, closing.


include processing time information in the output

Just an idea for further development: It can be useful if the client get information about the time required for execution of the whole pipeline and processing time of each service. This will help to find the bottleneck in the processing.

This is implemented. If you add the request parameter stats=true, the response is wrapped.
Example:
curl -vX POST --header "Content-Type: application/json" --header "Accept: application/json" -d<EMAIL_ADDRESS>"http://api-dev.freme-project.eu/current/pipelining/chain?stats=true"

Where @pipeline.json is a pipeline description (see the chain method for an example).
The result looks like:
{
	"metadata": {
		"serviceToDuration": {
			"http://api-dev.freme-project.eu/current/e-entity/dbpedia-spotlight/documents":1461,
			"http://api-dev.freme-project.eu/current/e-link/documents/":4299,
			"http://api-dev.freme-project.eu/current/e-translation/tilde":1963
		},
		"totalDuration":7723
	},
	"content": {
		"body": ...
		...
		}
}

Here the metadata contains a mapping serviceToDuration which contains how long each separate service takes to process its request. totalDuration is the time to process the complete pipeline. Times are in milliseconds.
content contains the original pipeline response.
If this is OK, I will post an issue to add this in the API documentation.

This also works on templates, E.g.:
curl -vX POST --header "Content-Type: text/plain" --header "Accept: application/json" -d "Brussels is the capital of Belgium." "http://api-dev.freme-project.eu/current/pipelining/chain/37?stats=true"

I like that this is displayed only via parameter "stats=true" so it is optional. How is it implemented? I think it could be done as a general filter so it is automatically enabled on every endpoint.

I like that this is displayed only via parameter "stats=true" so it is optional. How is it implemented?

Right now it is pretty hard-coded. The pipelines code returns a result with statistics anyway, and in the Broker the statistics are filtered out or kept depending on the value of the parameter. See the method pipeline() (it's not many lines of code ;) ).

I think it could be done as a general filter so it is automatically enabled on every endpoint.

Indeed. Then we also need a generic way to gather statistics...

Well actually when I think about it the general filter does not make so much sense. The execution time of a request is only of interest in the pipelines. When a user is interested in the execution time of a single request he can measure it himself and does not need the stats parameter.

"serviceToDuration" in the response is now called "serviceDurations".
@m1ci If you are OK with how it looks, can you close the issue, or comment if not?

nice work. Small remark on the naming - instead of "serviceDurations" I would call it "executionTime"

Done. Example:
{"metadata": {
	"executionTime": {
		"http://api.freme-project.eu/current/e-entity/dbpedia-spotlight/documents":1701,
		"http://api.freme-project.eu/current/e-translation/tilde":5284
	},
	"totalExecutionTime":6985 },
"content":{ ... }
}

great, fine by me. If there is nothing more to discuss just go ahead and close the issue.


Error in loading the Plugin "UnrealEnginePython" because the module "UnderalEnginePython"could not be found.

Every time I open the Unreal Engine this error message appear and I still want to use the plugin.
Im using the UnrealEnginePython_20170808_4_17_python27_win64.zip version.
I've python 27 Insalled.
HELP! PLEASE!
-Luv u Xuxu, if you answer this question.

Hi, ensure you have  64bit python2 version and that it is in the system PATH. Eventually tru and embedded version with python3

I also encounter a simillar problem on win64 with the embedded version 3.6.
My error is as such : Could not find definition for module 'UnrealEnginePython' (referenced via default plugins -> UnrealEnginePython.uplugin)

@SysOverdrive is this an official editor distribution or a custom compiled one ?

Hi @rdeioris
it was the UnrealEnginePython_20180907_4_20_python36_embedded_win64.zip from the releases pages available in the instructions.

You are using a 32bit python :)

Great works now with Python 64 bit installed, thank you

Any news from the ones who where using the embedded version for 3.6?
I tried with both UnrealEnginePython_20181128_4_21_python36_embedded_win64 and UnrealEnginePython_20181128_4_21_python37_win64.
Both give me the same error when compiling from both the editor and VS:
Using Visual Studio 2017 14.16.27023 toolchain (D:\Programs\VisualStuidoBuildTools\VC\Tools\MSVC\14.16.27023) and Windows 10.0.17763.0 SDK (C:\Program Files (x86)\Windows Kits\10).

ERROR: Could not find definition for module 'UnrealEnginePython' (referenced via default plugins -> UnrealEnginePython.uplugin)

Okay, after struggling to find a solution for 2 days, I tried compiling from the source and it worked. I am using python 3.7 intalled on my machine and UE4 version 4.21.
If someone is having the same issues, try following the steps described here:
Installation from sources on Windows (64 bit)
And always compile from VS with UE4 editor closed for the first time!

Got same problem. Turns out that there is predefined list of path where compiler looks for python.
private string[] windowsKnownPaths =
{
// "C:/Program Files/Python37",
"C:/Program Files/Python36",
"C:/Program Files/Python35",
"C:/Python27",
"C:/IntelPython35"
};
Its in the Plugins/UnrealEnginePython/Source/UnrealEnginePython/UnrealEnginePython.Build.cs
Add there your path to python. For some reason its not mentioned in the How-to-install tutorial. I guess it happens sometimes.

Python37 autyomaticly installs to "C:/Users/chris/AppData/Local/Programs/Python/Python37", so added this to the file mention above but I still get the error...


Updated C# projects to CPS/SDK-style format

Converted packages.config to package references
Removed unused using statements
Replaced local copy of StyleCop and NUnit with NuGet packages Using MSBuild to restore nuget packages instead of nuget.exe

I've been experiencing random crashes from htmlInstaller.exe, especially during test runs on the build agents.
The crash dumps, attached within build artifacts, indicate a stack trace originating from htmllayout.dll.
I've been trying to migrate from HtmlLayout to Sciter.JS but that is still work in progress.
In the meantime, I've been re-running builds in hopes the crash doesn't happen.
You can see the same code builds and tests pass successfully:
https://github.com/icnocop/dotnetinstaller/actions/runs/6268834204

I would like this PR merged before working on any new issues, like https://github.com/dotnetinstaller/dotnetinstaller/issues/163 for example.

Looks good, did a cursory look.


Buzzer should confirm/not confirm if mission is valid or not

This addresses this:
https://github.com/PX4/Firmware/pull/2363
I think we should not get too carried away though for the release 8).

Closing this and tracking it in the PR.


On first startup after power cycle, both monitors display black but the cursor is still rendered (invalid behavior)

I am on a relatively fresh Arch Linux installation, and I have done some light configuring of hyprland.conf, but nothing too major; just a few keybinds and startup programs. On first dropping into a Hyprland session after a power cycle from an unconfigured SDDM, Hyprland functions normally for a few seconds until both of my monitors black out, and Hyprland only renders the cursor. When I open a terminal, the cursor changes to typing mode (if you can call it that), indicating that windows are still running in the background, but I just can't see them. If I drop into a TTY or exit Hyprland with SUPER+M, and re-login, then everything works perfectly fine. I don't think it's a crash, but it certainly isn't intended behavior. I've tried to find any other issues that mention this, but I've come up short.
I am running an AMD 6950XT with the relevant drivers installed (mesa, lib32-mesa, vulkan-radeon, lib32-vulkan-radeon). I recently switched from the unstable driver builds to the latest stable builds, but even after that the issue persists.

Steps to reproduce:

Open Hyprland immediately after power cycle.

Expected outcome:

Hyprland functions normally and renders everything properly.

Noted outcome:

On boot, Hyprland blacks out and only renders the cursor. Restarting Hyprland fixes the issue.

I have sourced the log from the most recent time this happened in the linked text file.
hyprtemplog_output.txt
If any other information is needed, please let me know.

I have also have this issue. When loading Hyprland on a startup boot, everything works as expected for about 30 seconds. Then the screens go black. Restarting Hyprland fixed the issue.

Nothing looks amiss, please launch hyprland with HYPRLAND_LOG_WLR=1 and pass the log

forgive my noobishness, but how would i go about doing that?

Sounds like a similar issue to #2291

oh, yeah, dupe. Let's move to #2291


NIFI-9773 Refactor nifi-system-tests using JUnit 5

Description of PR
NIFI-9773 Refactors the nifi-system-tests module to use JUnit 5. The upgrade involved refactoring of the JUnit 4 TestWatcher in NiFiSystemIT to a new TroubleshootingTestWatcher implementation applied using the JUnit 5 ExtendsWith annotation.
Additional changes include enabling the GitHub system-tests workflow for push and pull request operations that include changes to the nifi-system-tests path.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[X] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[X] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Error:  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 319.671 s <<< FAILURE! - in org.apache.nifi.tests.system.pg.BatchFlowBetweenGroupsIT
Error:  org.apache.nifi.tests.system.pg.BatchFlowBetweenGroupsIT.testSingleConcurrencyAndBatchOutputToBatchInputOutput  Time elapsed: 317.629 s  <<< ERROR!
java.util.concurrent.TimeoutException: testSingleConcurrencyAndBatchOutputToBatchInputOutput() timed out after 5 minutes

Looks like you need to up the timeout.

Error:  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 319.671 s <<< FAILURE! - in org.apache.nifi.tests.system.pg.BatchFlowBetweenGroupsIT
Error:  org.apache.nifi.tests.system.pg.BatchFlowBetweenGroupsIT.testSingleConcurrencyAndBatchOutputToBatchInputOutput  Time elapsed: 317.629 s  <<< ERROR!
java.util.concurrent.TimeoutException: testSingleConcurrencyAndBatchOutputToBatchInputOutput() timed out after 5 minutes

Looks like you need to up the timeout.

Thanks for the feedback. The default timeout is five minutes for all tests, and this is generally sufficient. I have still observed sporadic time outs due to some conditions not being handled properly. I restarted the Ubuntu Java 11 system-tests job for now, but separate work may be necessary to track down the source of that particular problem.

Fair enough. I see green. That's good enough for me.

Will review tonight or tomorrow morning, as time permits.


Make BaseView Public

Resolves #10 by making BaseView and its members public.

[x] Code Review
[ ] Manual Testing

Current coverage is 100.00%

Merging #14 into master will not affect coverage as of 5ba0797

@@            master     #14   diff @@
======================================
  Files            6       6
  Stmts          113     113
  Branches         0       0
  Methods          0       0
======================================
  Hit            113     113
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 5ba0797

Powered by Codecov. Updated on successful CI builds.