Performance Graphs source of excessive Disk I/O

I've been running an adsb-reciever config for maybe 6 months, and experienced a flash SD card failure recently. As far as I can tell, this is due to the excessive writes caused by the Performance Graphs feature.
I'd like to request an option to run the performance graphs (collectd) and the visual display to a /tmpfs location, rather than directly writing to disk disk to eliminate this significant cause of disk I/O. I think an easy "Low Disk I/O" option in configuration would be really valuable in extending the reliability of these systems.
I also intend to move my syslog to a /tmpfs location, to avoid more disk writes. I hope eliminating those two sources will also lower the jdb2 writes, but frankly I'm not sure how to address the journaling issue 100%.
Here's the output of a couple minutes of: sudo iotop -a -o demonstrating the large writes caused by collectd.
Total DISK READ :       0.00 B/s | Total DISK WRITE :       0.00 B/s
Actual DISK READ:       0.00 B/s | Actual DISK WRITE:       0.00 B/s
  TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND
   69 be/3 root          0.00 B    660.00 K  0.00 %  0.89 % [jbd2/mmcblk0p2-]
 2834 be/4 root          0.00 B      0.00 B  0.00 %  0.35 % [kworker/u8:3]
21574 be/4 root          0.00 B      0.00 B  0.00 %  0.35 % [kworker/u8:1]
  361 be/4 root          0.00 B     48.00 K  0.00 %  0.00 % rsyslogd -n [rs:main Q:Reg]
  785 be/4 root          0.00 B     15.67 M  0.00 %  0.00 % collectd [rrdtool queue]

Hello,
I use https://github.com/azlux/log2ram

I tried adding a soultion such as this in an earlier version of the scripts. Things did not go well and a few receivers were trashed. At that point I decided I would leave it up to the users to set up their own solutions to deal with excesive wear caused by logging. I have done my best to streamline the lite version as much as possible to limit writes for those running SD cards without massive changes to the way the stock OS runs. There are just too many different devices, setups, and distros the scripts are capable of running on.
I would be open to adding a wiki page to the project outlining how to do so if anyone wishes to share the steps they used to setup such a system successfully on their device.
As a side note external USB hard drives fairly inexpensivly which will negate this issue.

Maybe a switch to turn off the performance graphs then? I'm not sure how I could do that and avoid having my configuration trashed on the next upgrade. I would be happy to file a separate bug for that if that's the best course of action.


Maven uses src/plugin.yml instead of plugin.yml

It's not really an important problem, but when PlaceholderAPI support will be complete, it may induce some bugs, since it will consider the wrong plugin.yml file.

@steve4744 Any idea?

No, sorry. I don't see why PlaceholderAPI will cause an issue if pom.xml is set up correctly?

It's just that's it's that Maven is (supposedly) including the wrong plugin.yml file. It shouldn't cause problems.

I've fixed this in latest commit?


use a list instead

https://github.com/Sudal12/project-google/blob/8e80c6474b8aaabd1041cee636e2bb21a559f2d4/results.html#L18

done the changes


buffub "prepend: stack overflow" issue

sometimes while recording, i get a weird "prepend: stack overflow" issue (see screenshot)
not sure if this is related, but when recording to a buffer, seeing some weird behavior selecting a portion of the wf with the mouse

i'll look into it tomorrow!

i tried a few times but really can't reproduce the issue. can you provide more details as when this happens?

i'm usually creating a 20 sec, stereo samplebuffer and then recording in from one xgroove and playing back the samplebuffer on another xgroove

I'm not sure if it's related, but I get the message "jpatcher: stack overflow -- outlets are disabled until this message is cleared" if I try to open<EMAIL_ADDRESS>

buffub is not recording to empty buffers for me... i'm following the steps as per the act_info...

I'm going to close this issue, there's been many improvements to buffub and buffer_host in the last couple months and the original issue i had is long gone, and i have not seen users reporting this issue recently


Feature Request: Add ability to forward an email to an actual email account

We need the ability to preview emails in specific email clients.   The ability to select an email, specify an email address, and send it via SMTP would help facilitate this.

Interesting.
So you envision this as something like:

Select an email
Click a button. Be presented with some type of dialog
Enter an email address
Mail gets sent out through the internet

Do I have that correct?

Yes, your steps would meet my needs.

I's also love the ability to actually tick a box and allow those mails to be 'forwarded' onto a 'real' SMTP server that we can configure, with the ability to change the outbound address ideally.

Yes.  I have a use case where it'd be nice to forward the email on via SMTP to another server.  Basically the use case being that we use mail slurper to do lots of testing, but sometimes we want to be able to see the message as it would appear in, say, Outlook.
Another alternative would be to allow for downloading of the message as a .msg file that you could just open in outlook.

yes this would be nice indeed, especially if one would want to test how an email looks in multiple clients. A targeted forwarded original-mail would come in handy.

Agreed ! this would be nice to have , or , An imap access to all the mails in the server. We also would like to test the look of mails in multiple clients.

Downloading the e-mail as a file would be a quick way to meet the "See how the e-mail looks on e-mail clients" requirement.


fix "Assert #74 failed in aria.core.Timer" in test launcher

I have updated this PR to use setTimeout instead of aria.core.Timer.addCallback.
As the indentation changed, it is better to look at this diff which ignores white space changes

26de55b8d25901ed3296ff80e2168d61f0835e20 LGTM


Convert new fields of jira issue for EE to domain layer fields

Description
Depends on #514

duplicated #518


[BUG] Hello, teacher. I am unable to download the data of "housing". I clicked the “download”, but it failed.

import os
import tarfile
import urllib
DOWNLOAD_ROOT = "https://raw.githubusercontent.com/ageron/handson-ml2/master/"
HOUSING_PATH = os.path.join("datasets","housing")
HOUSING_URL = DOWNLOAD_ROOT + "datasets/housing/housing.tgz"
def fetch_housing_data(housing_url = HOUSING_URL, housing_path = HOUSING_PATH):
os.makedirs(housing_path, exist_ok = True)
tgz_path = os.path.join(housing_path, "housing.tgz")
urllib.request.urlretrieve(housing_url, tgz_path)
housing_tgz = tarfile.open(tgz_path)
housing_tgz.extractall(path = housing_path)
housing_tgz.close()
fetch_housing_data()
import pandas as pd
def load_housing_data(housing_path = HOUSING_PATH):
csv_path = os.path.join(housing_path, "housing.csv")
return pd.read_csv(csv_path)
housing = load_housing_data()
housing.head()

import os
import tarfile
import urllib
DOWNLOAD_ROOT = "https://raw.githubusercontent.com/ageron/handson-ml2/master/"
HOUSING_PATH = os.path.join("datasets","housing")
HOUSING_URL = DOWNLOAD_ROOT + "datasets/housing/housing.tgz"
def fetch_housing_data(housing_url = HOUSING_URL, housing_path = HOUSING_PATH):
os.makedirs(housing_path, exist_ok = True)
tgz_path = os.path.join(housing_path, "housing.tgz")
urllib.request.urlretrieve(housing_url, tgz_path)
housing_tgz = tarfile.open(tgz_path)
housing_tgz.extractall(path = housing_path)
housing_tgz.close()
fetch_housing_data()
import pandas as pd
def load_housing_data(housing_path = HOUSING_PATH):
csv_path = os.path.join(housing_path, "housing.csv")
return pd.read_csv(csv_path)
housing = load_housing_data()
housing.head()

After I run, nothing happened.

Hi @zhupipia,
I just tried running your code in Colab, and it worked just fine. What environment are you running this code in? What do you mean by "nothing happened"? Was anything displayed? Did you get an error message? Are you sure you ran the code? Could you please provide more details (e.g., a screenshot).

Thanks for the update, @zhupipia . I recommend you go through the code examples using Colab, as it does not require any installation on your own system, you get access to a free virtual machine online which can be equipped with a GPU or even a TPU, and it runs in your web browser. Just go to https://homl.info/colab2 , then login to your Google account (if needed), and select the notebook you want to open (for example 02_end_to_end_machine_learning_project.ipynb). Next, run the cells one by one. Feel free to play with the code. If anything fails, you can always reopen the original notebook in Colab and run it to see if the error was due to any changes you made to the code.
The code will run on the virtual machine on the cloud, so any data that the code downloads will be downloaded to that virtual machine. If you train a model and you want to keep it, you can always download it to your own machine.
Hope this helps.

But not it good path on file wrong


[#7142] support webhook functionality in alarm

support webhook functionality in alarm.
changes:

batch: webhook sender implementation
web: UI webhook support
testing

and you can use test receiver using this sample project slack-receiver

Codecov Report

Merging #7553 (7e67015) into master (932a359) will increase coverage by 0.00%.
The diff coverage is 33.03%.

@@           Coverage Diff            @@
##           master    #7553    +/-   ##
========================================
  Coverage   38.85%   38.86%
========================================
  Files        3481     3493    +12
  Lines       99812   100023   +211
  Branches    12251    12261    +10
========================================
+ Hits        38786    38872    +86
- Misses      58029    58157   +128
+ Partials     2997     2994     -3

Impacted Files
Coverage Δ

...inpoint/batch/alarm/DefaultAlarmMessageSender.java
0.00% <0.00%> (ø)

...orp/pinpoint/batch/alarm/checker/AgentChecker.java
35.71% <0.00%> (-7.77%)
:arrow_down:

.../checker/DataSourceConnectionUsageRateChecker.java
100.00% <ø> (ø)

.../pinpoint/batch/alarm/checker/DeadlockChecker.java
88.88% <ø> (ø)

...int/batch/alarm/checker/FileDescriptorChecker.java
100.00% <ø> (ø)

...p/pinpoint/batch/alarm/checker/GcCountChecker.java
0.00% <ø> (ø)

...oint/batch/alarm/checker/HeapUsageRateChecker.java
100.00% <ø> (ø)

...nt/batch/alarm/checker/JvmCpuUsageRateChecker.java
100.00% <ø> (ø)

...int/batch/alarm/checker/LongValueAlarmChecker.java
66.66% <0.00%> (-33.34%)
:arrow_down:

...batch/alarm/checker/SystemCpuUsageRateChecker.java
100.00% <ø> (ø)

... and 49 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 932a359...7e67015. Read the comment docs.

Codecov Report

Merging #7553 (7e67015) into master (932a359) will increase coverage by 0.00%.
The diff coverage is 33.03%.

@@           Coverage Diff            @@
##           master    #7553    +/-   ##
========================================
  Coverage   38.85%   38.86%
========================================
  Files        3481     3493    +12
  Lines       99812   100023   +211
  Branches    12251    12261    +10
========================================
+ Hits        38786    38872    +86
- Misses      58029    58157   +128
+ Partials     2997     2994     -3

Impacted Files
Coverage Δ

...inpoint/batch/alarm/DefaultAlarmMessageSender.java
0.00% <0.00%> (ø)

...orp/pinpoint/batch/alarm/checker/AgentChecker.java
35.71% <0.00%> (-7.77%)
:arrow_down:

.../checker/DataSourceConnectionUsageRateChecker.java
100.00% <ø> (ø)

.../pinpoint/batch/alarm/checker/DeadlockChecker.java
88.88% <ø> (ø)

...int/batch/alarm/checker/FileDescriptorChecker.java
100.00% <ø> (ø)

...p/pinpoint/batch/alarm/checker/GcCountChecker.java
0.00% <ø> (ø)

...oint/batch/alarm/checker/HeapUsageRateChecker.java
100.00% <ø> (ø)

...nt/batch/alarm/checker/JvmCpuUsageRateChecker.java
100.00% <ø> (ø)

...int/batch/alarm/checker/LongValueAlarmChecker.java
66.66% <0.00%> (-33.34%)
:arrow_down:

...batch/alarm/checker/SystemCpuUsageRateChecker.java
100.00% <ø> (ø)

... and 49 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 932a359...7e67015. Read the comment docs.

good!!
I will merge the code after the 2.1.1 release.

good!!
I will merge the code after the 2.1.1 release.

Thank you so much for contributing a very useful feature.^^

Thank you so much for contributing a very useful feature.^^

Thank you @Pinpoint

Thank you @Pinpoint


Added the ability to use an additional addresses

Codecov Report

Merging #1174 (ba3f064) into master (f422f70) will decrease coverage by 0.52%.
The diff coverage is n/a.

:exclamation: Current head ba3f064 differs from pull request most recent head 4d8ffdb. Consider uploading reports for the commit 4d8ffdb to get more accurate results

@@            Coverage Diff             @@
##           master    #1174      +/-   ##
==========================================
- Coverage   41.44%   40.92%   -0.53%
==========================================
  Files         412      414       +2
  Lines        8867     8988     +121
  Branches     1406     1434      +28
==========================================
+ Hits         3675     3678       +3
- Misses       5181     5299     +118
  Partials       11       11

Impacted Files
Coverage Δ

src/screen/types.ts
100.00% <0.00%> (ø)

src/ledger/LedgerWait.tsx
0.00% <0.00%> (ø)

src/app/screen/Screen/Screen.tsx
0.00% <0.00%> (ø)

src/wallets/WalletList/WalletMenu.tsx
0.00% <0.00%> (ø)

src/create-account/AddHDAddress/index.ts
0.00% <0.00%> (ø)

src/create-account/AddHDAddress/AddHDAddress.tsx
0.00% <0.00%> (ø)

src/accounts/actions.ts
26.00% <0.00%> (+1.00%)
:arrow_up:

Continue to review full report at Codecov.

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


NBT tag compatibility

Just to start off this is a great plugin, however....
Items that have shops set up for them do not check for a match of NBT Tags as they are getting sold or bought to and from. Is there any way in which you can make it so the NBT Tages are used to buy and sell with? For example, a custom named item going into the shop and coming out as a normal item or a normal item going and coming out a named item is a worrying prospect since we place high value on the custom named items.

I'm pretty sure that at least display names are working. The rest should also be working fine except some NBT tags, but that should be fixed in the next update (8e867a7). So, what exactly is not working for you and what version are you currently using?

Thank you for updating this (well in dev builds), my friend wants to know if you have a paypal so he can donate as he believes you are a great developer.


More tests, more automated validation, update to latest Android/Gradle

This started as work on #5 with some new tests, but then turned into a general cleanup to enable lint, add PMD, FindBugs, as well as bumping to the latest gradle and Android build tools.
No new APIs or changes to existing APIs. No real need to update, but there is some better NPE checking thanks to FindBugs.

pull request is good by me. Nice code cleanup!

In general all good.
Possible improvements:
Move logic for alert Types into separate class for preventing GodClass of PMD


Plugin depends on global Raphael which will be removed in Bitbucket Server 5.0

I'm one of the frontend developers on the Bitbucket Server team at Atlassian.
This plugin currently depends on a globally available Raphael in the jquery.commitgraph.js module.
Raphael being available as a global was a side-effect of it being an AUI dependency, and in Bitbucket Server 4.10 we are updating to a version of AUI (6.0.0) that no longer includes or depends on Raphael.
Even though Raphael was never part of our API, we are aware that some popular plugins such as this one are using it, and to avoid customer upgrade pain we have temporarily provided a deprecated Raphael dependency. This dependency will be removed in Bitbucket Server 5.0.
Our recommendation is to either bundle your own version of Raphael, or another drawing library, with your plugin.

Bitbucket Server 5.0 has been released so a solution is now needed.


fix compile warnings

Coverage remained the same at 86.467% when pulling 6016858cbdb58a9958932245fc98f24566da4a37 on wujimin:fix-compile-warnings into bbf3f8f1e5f959d65ad842ba2ce02e7a82445288 on ServiceComb:master.


Fixing a link

There was an error while validating job 8be75c8a-c44a-4820-b10f-a749f87e9d75 Message:
Result status: Failed
There was a problem accessing Github repository 'https://github.com/Microsoft/cordova-docs.git'.
Details:Microsoft.LightweightJobEngine.Core.Language.ContextCommandBase+ContextCommandException:
Result status: Failed
There was a problem accessing Github repository 'https://github.com/Microsoft/cordova-docs.git'.
---> System.AggregateException: One or more errors occurred. ---> System.ArgumentException: Error clonning repository ---> LibGit2Sharp.NotFoundException: Branch 259 not found. Available branches: origin/master
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.GetBranch(Repository repo, String name)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.<>c__DisplayClass30.<>c__DisplayClass34.b__29(KeyValuePair2 branch)    at System.Collections.Generic.List1.ForEach(Action1 action)    at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.<>c__DisplayClass30.<CloneRepository>b__28()    at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.<>c__DisplayClass1.<ExecuteAction>b__0()    at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.ExecuteAction[TResult](Func1 func)
at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.ExecuteAction(Action action)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository(String url, IDictionary2 branches)    --- End of inner exception stack trace ---    at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository(String url, IDictionary2 branches)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository()
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.GetVersionAsync(String path)
at Microsoft.DPS.Commands.IdentifyDocumentsToPublish.CheckExternalServicesCommand.Do(IDictionary2 context)    --- End of inner exception stack trace ---    --- End of inner exception stack trace ---    at Microsoft.LightweightJobEngine.Core.Language.ContextCommandBase.ThrowIfErrorsLogged()    at Microsoft.DPS.Commands.IdentifyDocumentsToPublish.CheckExternalServicesCommand.Do(IDictionary2 context)
at Microsoft.LightweightJobEngine.Core.Language.JobWorkflow1.RunCommands(Guid jobId, IDictionary2 context, CancellationTokenSource cancelSignal)


Can't find extesnion on vscode

I just can't find the Motoko extension on my vscode I also tried the contributing commands still I can't install. I also have both node and npm installed but still I'm unable to install the extension.

As an open-source contributor, here's how I package and install the extension:

After cloning the repository, run npm install to download all the npm dependencies.
Run npm run package to generate the .vsix file in the root directory of the repository.
Right-click on the newly generated vscode-motoko-0.3.9.vsix (in the root directory) and select "Install Extension VSIX" (at the bottom of the menu).

Hopefully this helps! If you're running into a different issue and get a chance to send an error log, I'll do my best to point you in the right direction.

In case anyone finds this in the future, the VS Code extension is available here.


<EMAIL_ADDRESS>hash check failed

I encountered an issue while using：scoop install carrot/typora
I received an error message：
PS C:\Users\Administrator\Desktop> scoop install carrot/typora
WARN  Purging previous failed installation of typora.
ERROR 'typora' isn't installed correctly.
Removing older version (0.11.18).
'typora' was uninstalled.
Installing 'typora' (0.11.18) [64bit] from carrot bucket
typora-setup-x64.exe (77.2 MB) [==============================================================================] 100%
Checking hash of typora-setup-x64.exe ... ERROR Hash check failed!
App:         carrot/typora
URL:         https://typora.io/windows/typora-setup-x64.exe
First bytes: 4D 5A 50 00 02 00 00 00
Expected:    2c2c80c32d813744b6d48851687c752e819c0cd4246440842effd3d10473dd22
Actual:      1b7e6d1e2c232408755ecfda1e723d2a10e7d50a9ab7ffd750edb17dfa51cc49

The official download link is no longer valid.
https://typora.io/windows/dev_release.html
https://download.typora.io/windows/typora-update-x64-1117.exe


add warning for worker

This bug exists for a long time and I don't think the Rust team can fix it soon. So we must do something to get around it or disable this feature, not only adding the warning comment.
E.g, we can try to use CondVar to solve this problem but I worry its performance, maybe we can use a faster one parkinglot.

Now we decide to use crossbeam channel instead, so we can close this PR.


import - migrate from perl to python (CP & Fortinet)

add a second import process which handles cp & fortinet
create new new systemd service for import_mgm

implemented in #1339


Tool throwing ValueError

I used this back when it was released. Have tried to use it again today, with the same credentials as before, and am getting the following traceback:

Enter the game's abbreviation in speedrun.com (eg. "smb1" for Super Mario Bros.): smb1
Traceback (most recent call last):
File "main.py", line 15, in
File "Data.py", line 30, in getRuns
ValueError: invalid literal for int() with base 10: 'Number of runs7485'
[10592] Failed to execute script 'main' due to unhandled exception!

Looks like something might have changed in the site formatting to cause it to crash.

Thanks for the report. Speedrun.com has changed CSS style names, hope this fixes the issue

Worked for me, thanks.


chore(maintenance): update release flow diagram

Description of your changes

This PR updates the content of the diagram that shows the release process in the maintainers handbook.
Before

After

Related issues, RFCs

Issue number: #2044
Checklist

[x] My changes meet the tenets criteria
[x] I have performed a self-review of my own code
[ ] I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my change is effective and works
[x] The PR title follows the conventional commit semantics

Breaking change checklist
Is it a breaking change?: NO

[ ] I have documented the migration process
[ ] I have added, implemented necessary warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Hi, thanks for the review!
I have update the diagram to make the manual steps stand out more (converted them into milestones):

Regarding the separation of version & release I would leave it as a single section/diagram. I have however updated the description above to more explicitly call out that the release process is composed by multiple district workflows.


Document using SASS_PATH to enable absolute path imports

There are a couple of issues where this appears to be the solution. See: https://github.com/facebook/create-react-app/issues/4494#issuecomment-441464956 and https://github.com/facebook/create-react-app/pull/5599#issuecomment-433996606
We should add this to the Sass docs: https://facebook.github.io/create-react-app/docs/adding-a-sass-stylesheet

@jayantbh Would you like to work on this since you're the one who reported the fix?

@iansu sure! Will do!


saved model predict function call leads to OOM

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04.4 64-bit
TensorFlow installed from (source or binary): pip
TensorFlow version (use command below): 2.4.0
Python version: 3.7.9
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: CUDA 11.0, cuDNN <IP_ADDRESS>
GPU model and memory: NVIDIA GeForce GTX 1660 Ti (6 GB)

Describe the current behavior
I am trying to load a saved model (h5 file=3.8MB) using the setup described above and then use the model.predict on a numpy array of size (45000, 32, 32, 3) and float32 datatype and I get a OOM memory error.
I have set the memory growth option:
for gpu in tf.config.experimental.list_physical_devices('GPU'):
tf.config.experimental.set_memory_growth(gpu, True)
Describe the expected behavior
while training the same model with dataset does not cause an error, the predict function. So, I am not sure what is happening. Th
Standalone code to reproduce the issue
https://github.com/rajatsaxena/test/blob/main/Similarity-CIFAR10-car.ipynb

@rajatsaxena ,
Please take a look at this issues with similar error log.It helps.link1,link2,link3.
Thanks!

reducing the batch size helps, but the dataset isn't that big for both a 6gb and 12gb GPU to crash. I had run the same script on these exact same GPUs with Cuda10 and TF2.2 without any problem

I was able to reproduce the issue in TF v2.4,v2.5 and nightly.Please find the gist.

@rajatsaxena
For GPU, try limiting GPU memory growth as per this guide and let us know if it helps.

Alright, I will give it a shot

It did not help. Is there a specific location in the above script where I should add it?

@rajatsaxena
Add it before the model training.


Improve the UI and add important card elements

I think it would be pretty if the entries could be changed into a card view as mentioned in #8 point number 2.
Image below for reference

I would also like to include necessary elements such as Deadline, Difficulty etc based on the information found each of those websites.
Please assign me to the task if you think this is a good issue

I am assigned to both of you. Don't forget to tell the details about what are the changes you have made, create a screen recording too, after your added feat how the website is gonna look.

@iriteshmishra I do not have write access

Any update @Acesif

Any update @Acesif

Please check PR #64

RESOLVE CONFLICT

Due to the merging of the latest PR, #64 is no longer valid, I'll close it and make another PR that works with the current version.


Support dry mode

Many wall mount HVAC systems support drying only mode to reduce humidity in the room. ha-dual-smart-thermostat makes a great overlay on top of those systems to implement twin set points where the underlying climate component does not support it. It's reasonably straightforward to implement a binary switch to enable/disable dry mode on these units if ha-dual-smart-thermostat  was to support a DRY only mode.

Duplicate of #25

It's more complex.
Of course, I could just add a switch for the dehumidifier to turn on/off, but it needs some other stuff required by the underlying climate entity built into the home assistant.
And if I just added the toggle, others will rightfully request a fully featured hygrostat.
So I will implement a fully featured hygrostat.
This will involve:

dryer switch
humidity sensor
min/max humidity
humidity tolerances

Stay tuned!

Well that would be amazing, and apologies for the dupe

I implemented the feature, but the climate entity in Homeassistant only supports a partially featured hygrostat (a dryer).
So, you will be able to switch to the dry mode and set target humidity and tolerances.
It will be included in the next beta/release.


useOverlayPosition enforces styles directly

🐛 Bug Report
useOverlayPosition started to enforce styles directly on the ref here. Is there any way to prevent this from happening?
🤔 Expected Behavior
Being able to apply the styles conditionally depending on the variant of the popover.
😯 Current Behavior
Previously we had an ability to set the position styles on any node we wanted, now we're forced to have the styles applied directly to the node that ref we pass into usePopover (which then goes to the useOverlayPosition
💁 Possible Solution
Easiest way would be to add a prop that allows to omit the direct application of styles in useOverlayPosition applied here. But I'm sure there could be an easier / better solution?
🔦 Context
We're using usePopover to create our popover which comes in a couple of different shapes. Our dropdown changes from a regular popover into an action sheet on mobile, so we were applying the popover styles conditionally depending on the screen width. Now the styles are applied directly without any way to omit/override them.
💻 Code Sample
https://github.com/adobe/react-spectrum/blob/83677f94489fdfa535fd511157f5292ad80b7b09/packages/%40react-aria/overlays/src/useOverlayPosition.ts#L147-L150
These set of lines are problematic for us
🌍 Your Environment

Software
Version(s)

react-aria
3.23.1

Browser
Chrome

Operating System
MacOS

🧢 Your Company/Team
Not affiliated with Adobe
🕷 Tracking Issue (optional)

Unfortunately, there isn't a way to prevent this from happening at the moment. Could you instead render a different component for mobile instead of reusing the same Popover? For some of our components (Dialogs, ComboBox, etc) we render a Tray that uses useModalOverlay instead for these cases.

We've quite a strong rule of not using javascript to change DOM nodes for responsiveness - we want to handle these via media queries (which we were able to do with the previous approach). I'll not bump the version for now, but I would love to hear back if it could be avoided in the future 🙏🏻


Generate web notifications when Inverse window is minimised

If the Inverse window is obscured or minimised, chat messages are missed.
Solution
Add logic to the pade plugin for Inverse to intercept chat messages and create a notification message when the Inverse window is not in focus or minimised.

Done in version 0.3.7


vivaldi: use ffmpeg instead of ffmpeg_3

Motivation for this change
https://github.com/NixOS/nixpkgs/issues/120705
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I only made sure that it builds, not that it works.

ACK-ing. Diff looks good, I'll try it out when I get a chance later


iOS Analytics events not showing up

Hi!
I put the Firebase plugin in my Unity application and everything went fine (Android version). I tried with the iOS version but it is not logging the events. I know the events take a few hours to appear but they are not appearing either after 1 day or in debug mode.
For debug mode, I've put the "-FIRAnalyticsDebugEnabled" argument, just like the tutorial (https://firebase.google.com/docs/analytics/ios/events#view_events_in_the_xcode_debug_console). On another site (https://support.google.com/firebase/answer/7201382?hl=pt&utm_id=ad), I realized that there is another argument "-FIRDebugEnabled". I tried both of them but none logged my events.
Another thing I noticed is that the "GoogleService-Info.plist" file that I downloaded on the Firebase website comes with the variable "IS_ANALYTICS_ENABLED" = false. It does not say anything in the tutorial (https://firebase.google.com/docs/analytics/unity/start?hl=pt-br) but I put it true.
Am I doing something wrong?

You're enabling data collection
https://github.com/firebase/quickstart-unity/blob/master/analytics/testapp/Assets/TestApp/UIHandler.cs#L66
?
On Tue, Jun 27, 2017 at 11:22 AM, brunok8<EMAIL_ADDRESS>wrote:

Hi!
I put the Firebase plugin in my Unity application and everything went fine
(Android version). I tried with the iOS version but it is not logging the
events. I know the events take a few hours to appear but they are not
appearing either after 1 day or in debug mode.
For debug mode, I've put the "-FIRAnalyticsDebugEnabled" argument, just
like the tutorial (https://firebase.google.com/docs/analytics/ios/events#
view_events_in_the_xcode_debug_console). On another site (
https://support.google.com/firebase/answer/7201382?hl=pt&utm_id=ad), I
realized that there is another argument "-FIRDebugEnabled". I tried both of
them but none logged my events.
Another thing I noticed is that the "GoogleService-Info.plist" file that I
downloaded on the Firebase website comes with the variable
"IS_ANALYTICS_ENABLED" = false. It does not say anything in the tutorial (
https://firebase.google.com/docs/analytics/unity/start?hl=pt-br) but I
put it true.
Am I doing something wrong?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-unity/issues/91, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AFw1RHocVBpMWWddDfDxgtmbXPKl71xGks5sIUhagaJpZM4OHAfj
.

Yes! I'm enabling data collection like the example.
I guess my xcode console can help (I don't know why exactly it's putting the same code twice):

2017-05-29 12:54:41.638343 brincando[22620:5072036] [Firebase/Analytics][I-ACS023105] Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters:
post_score,
{
firebase_screen_id (_si) = -396951154609863799;
score = 42;
firebase_screen_class (_sc) = UnityDefaultViewController;
firebase_realtime (_r) = 1;
firebase_debug (_dbg) = 1;
firebase_event_origin (_o) = app;
}
2017-05-29 12:54:41.640 brincando[22620]  [Firebase/Analytics][I-ACS023105] Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters:
post_score,
{
firebase_screen_id (_si) = -396951154609863799;
score = 42;
firebase_screen_class (_sc) = UnityDefaultViewController;
firebase_realtime (_r) = 1;
firebase_debug (_dbg) = 1;
firebase_event_origin (_o) = app;
}

2017-05-29 12:54:41.646107 brincando[22620:5072192] [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 415
2017-05-29 12:54:41.648 brincando[22620]  [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 415
2017-05-29 12:54:41.657411 brincando[22620:5072026] [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 13,<PHONE_NUMBER>620
2017-05-29 12:54:41.658 brincando[22620]  [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 13,<PHONE_NUMBER>620
2017-05-29 12:54:41.678965 brincando[22620:5072026] [Firebase/Analytics][I-ACS023038] Uploading events. Elapsed time since last successful upload (s): 21.54594898223877
2017-05-29 12:54:41.679 brincando[22620]  [Firebase/Analytics][I-ACS023038] Uploading events. Elapsed time since last successful upload (s): 21.54594898223877
2017-05-29 12:54:41.681181 brincando[22620:5072026] [Firebase/Analytics][I-ACS023039] Measurement data sent to network. Timestamp (ms), data:<PHONE_NUMBER>675, <FIRAPBMeasurementBatch: 0x170016af0>
2017-05-29 12:54:41.681 brincando[22620]  [Firebase/Analytics][I-ACS023039] Measurement data sent to network. Timestamp (ms), data:<PHONE_NUMBER>675, <FIRAPBMeasurementBatch: 0x170016af0>
2017-05-29 12:54:41.690525 brincando[22620:5072050] [Firebase/Analytics][I-ACS900000] Uploading data. Host: https://app-measurement.com/a
2017-05-29 12:54:41.690 brincando[22620]  [Firebase/Analytics][I-ACS900000] Uploading data. Host: https://app-measurement.com/a
2017-05-29 12:54:41.747085 brincando[22620:5072192] [Firebase/Analytics][I-ACS901006] Received SSL challenge for host. Host: https://app-measurement.com/a
2017-05-29 12:54:41.747 brincando[22620]  [Firebase/Analytics][I-ACS901006] Received SSL challenge for host. Host: https://app-measurement.com/a
2017-05-29 12:54:41.849945 brincando[22620:5072050] [Firebase/Analytics][I-ACS023044] Successful upload. Got network response. Code, size: 204, 0
2017-05-29 12:54:41.850 brincando[22620]  [Firebase/Analytics][I-ACS023044] Successful upload. Got network response. Code, size: 204, 0
2017-05-29 12:54:41.860015 brincando[22620:5072036] [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): -0.2379031181335449
2017-05-29 12:54:41.860 brincando[22620]  [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): -0.2379031181335449
2017-05-29 12:54:41.860374 brincando[22620:5072036] [Firebase/Analytics][I-ACS023028] Upload task scheduled to be executed in approx. (s): -0.2379031181335449
2017-05-29 12:54:41.860 brincando[22620]  [Firebase/Analytics][I-ACS023028] Upload task scheduled to be executed in approx. (s): -0.2379031181335449
2017-05-29 12:54:41.878356 brincando[22620:5072050] [Firebase/Analytics][I-ACS023024] No data to upload. Upload task will not be scheduled
2017-05-29 12:54:41.878 brincando[22620]  [Firebase/Analytics][I-ACS023024] No data to upload. Upload task will not be scheduled
2017-05-29 12:54:41.878814 brincando[22620:5072050] [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2017-05-29 12:54:41.880 brincando[22620]  [Firebase/Analytics][I-ACS002003] Measurement timer canceled

Have you tried enabling debug view to verify events are being sent from the
device?
https://firebase.google.com/docs/analytics/debugview
From the log it looks like the events are being uploaded somewhere.  It
makes me wonder whether your GoogleServices-Info.plist is the config
associated with the project you're trying to log data to.
On Tue, Jun 27, 2017 at 11:58 AM, brunok8<EMAIL_ADDRESS>wrote:

Yes! I'm enabling data collection like the example.
I guess my xcode console can help (I don't know why exactly it's putting
the same code twice):
2017-05-29 12:54:41.638343 brincando[22620:5072036] [Firebase/Analytics][I-ACS023105]
Event is not subject to real-time event count daily limit. Marking an event
as real-time. Event name, parameters:
post_score,
{
firebase_screen_id (_si) = -396951154609863799;
score = 42;
firebase_screen_class (_sc) = UnityDefaultViewController;
firebase_realtime (_r) = 1;
firebase_debug (_dbg) = 1;
firebase_event_origin (_o) = app;
}
2017-05-29 12:54:41.640 brincando[22620] [Firebase/Analytics][I-ACS023105]
Event is not subject to real-time event count daily limit. Marking an event
as real-time. Event name, parameters:
post_score,
{
firebase_screen_id (_si) = -396951154609863799;
score = 42;
firebase_screen_class (_sc) = UnityDefaultViewController;
firebase_realtime (_r) = 1;
firebase_debug (_dbg) = 1;
firebase_event_origin (_o) = app;
}
2017-05-29 12:54:41.646107 brincando[22620:5072192] [Firebase/Analytics][I-ACS012018]
Saving bundle. size (bytes): 415
2017-05-29 12:54:41.648 brincando[22620] [Firebase/Analytics][I-ACS012018]
Saving bundle. size (bytes): 415
2017-05-29 12:54:41.657411 brincando[22620:5072026] [Firebase/Analytics][I-ACS023116]
Bundle added to the upload queue. BundleID, timestamp (ms): 13,
1496073280620
2017-05-29 12:54:41.658 brincando[22620] [Firebase/Analytics][I-ACS023116]
Bundle added to the upload queue. BundleID, timestamp (ms): 13,
1496073280620
2017-05-29 12:54:41.678965 brincando[22620:5072026] [Firebase/Analytics][I-ACS023038]
Uploading events. Elapsed time since last successful upload (s):
21.54594898223877
2017-05-29 12:54:41.679 brincando[22620] [Firebase/Analytics][I-ACS023038]
Uploading events. Elapsed time since last successful upload (s):
21.54594898223877
2017-05-29 12:54:41.681181 brincando[22620:5072026] [Firebase/Analytics][I-ACS023039]
Measurement data sent to network. Timestamp (ms), data:<PHONE_NUMBER>675,
<FIRAPBMeasurementBatch: 0x170016af0>
2017-05-29 12:54:41.681 brincando[22620] [Firebase/Analytics][I-ACS023039]
Measurement data sent to network. Timestamp (ms), data:<PHONE_NUMBER>675,
<FIRAPBMeasurementBatch: 0x170016af0>
2017-05-29 12:54:41.690525 brincando[22620:5072050] [Firebase/Analytics][I-ACS900000]
Uploading data. Host: https://app-measurement.com/a
2017-05-29 12:54:41.690 brincando[22620] [Firebase/Analytics][I-ACS900000]
Uploading data. Host: https://app-measurement.com/a
2017-05-29 12:54:41.747085 brincando[22620:5072192] [Firebase/Analytics][I-ACS901006]
Received SSL challenge for host. Host: https://app-measurement.com/a
2017-05-29 12:54:41.747 brincando[22620] [Firebase/Analytics][I-ACS901006]
Received SSL challenge for host. Host: https://app-measurement.com/a
2017-05-29 12:54:41.849945 brincando[22620:5072050] [Firebase/Analytics][I-ACS023044]
Successful upload. Got network response. Code, size: 204, 0
2017-05-29 12:54:41.850 brincando[22620] [Firebase/Analytics][I-ACS023044]
Successful upload. Got network response. Code, size: 204, 0
2017-05-29 12:54:41.860015 brincando[22620:5072036] [Firebase/Analytics][I-ACS002002]
Measurement timer scheduled to fire in approx. (s): -0.2379031181335449
2017-05-29 12:54:41.860 brincando[22620] [Firebase/Analytics][I-ACS002002]
Measurement timer scheduled to fire in approx. (s): -0.2379031181335449
2017-05-29 12:54:41.860374 brincando[22620:5072036] [Firebase/Analytics][I-ACS023028]
Upload task scheduled to be executed in approx. (s): -0.2379031181335449
2017-05-29 12:54:41.860 brincando[22620] [Firebase/Analytics][I-ACS023028]
Upload task scheduled to be executed in approx. (s): -0.2379031181335449
2017-05-29 12:54:41.878356 brincando[22620:5072050] [Firebase/Analytics][I-ACS023024]
No data to upload. Upload task will not be scheduled
2017-05-29 12:54:41.878 brincando[22620] [Firebase/Analytics][I-ACS023024]
No data to upload. Upload task will not be scheduled
2017-05-29 12:54:41.878814 brincando[22620:5072050] [Firebase/Analytics][I-ACS002003]
Measurement timer canceled
2017-05-29 12:54:41.880 brincando[22620] [Firebase/Analytics][I-ACS002003]
Measurement timer canceled
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-unity/issues/91#issuecomment-311452981,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFw1RLwDhvAzbpOS9HlNF0oKYfyRLzzYks5sIVDsgaJpZM4OHAfj
.

Yes, I used the Debug View with the Android version and It works perfectly! =D
I saw two different arguments to use on iOS version, which one is the right one?

-FIRAnalyticsDebugEnabled (https://firebase.google.com/docs/analytics/ios/events#view_events_in_the_xcode_debug_console)

-FIRDebugEnabled (https://support.google.com/firebase/answer/7201382?hl=pt&utm_id=ad)

Is there some way to check if my GoogleServices-Info.plist it's ok? The bundle Id is the same as my game.
Thanks again!

You need to use -FIRDebugEnabled to enable debug mode.
The easiest way to verify your GoogleServices-Info.plist is to download the
config file from your project on the Firebase Console and use "diff
path_to_plist_in_your_xcode_project path_to_downloaded_plist" to compare
them.  The config is not just based upon the game bundle ID, it's also
based upon API key etc.
On Tue, Jun 27, 2017 at 2:26 PM, brunok8<EMAIL_ADDRESS>wrote:

Yes, I used the Debug View with the Android version and It works
perfectly! =D
I saw two different arguments to use on iOS version, which one is the
right one?

-FIRAnalyticsDebugEnabled (https://firebase.google.com/
docs/analytics/ios/events#view_events_in_the_xcode_debug_console
https://firebase.google.com/docs/analytics/ios/events#view_events_in_the_xcode_debug_console
)
2.
-FIRDebugEnabled (https://support.google.com/
firebase/answer/7201382?hl=pt&utm_id=ad
https://support.google.com/firebase/answer/7201382?hl=pt&utm_id=ad)
Is there some way to check if my GoogleServices-Info.plist it's ok? The
bundle Id is the same as my game.
Thanks again!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-unity/issues/91#issuecomment-311490784,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFw1RA8W7RGrVQVOd8tMilf9LmuruMVWks5sIXOJgaJpZM4OHAfj
.

Ok! I use the -FIRDebugEnabled but still it's not working.
I downloaded a new version of my GoogleServices-Info.plist and tried to diff with the other one in my project and they are the same one.
This GoogleServices-Info.plist comes with the "IS_ANALYTICS_ENABLED". Is that right? I tried to put true but still I don't receive the events.

Did you follow the debug view instructions with -FIRDebugEnabled ?
https://firebase.google.com/docs/analytics/debugview
Are you 1000% sure the GoogleServices-Info.plist matches the one included
in your xcode project as well?
Did you try our sample application with your GoogleServices-Info.plist to
see whether you get the same behavior?
https://github.com/firebase/quickstart-unity/tree/master/analytics/testapp
On Thu, Jun 29, 2017 at 6:05 PM, brunok8<EMAIL_ADDRESS>wrote:

Ok! I use the -FIRDebugEnabled but still it's not working.
I downloaded a new version of my GoogleServices-Info.plist and tried to
diff with the other one in my project and they are the same one.
This GoogleServices-Info.plist comes with the "IS_ANALYTICS_ENABLED". Is
that right? I tried to put true but still I don't receive the events.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-unity/issues/91#issuecomment-312147367,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFw1RBIgf6AGmRN1lJNtJ77vEjRvh03gks5sJEnBgaJpZM4OHAfj
.

Any update on this?

@brunok8 it's been a few weeks and we haven't heard from you so I'll assume your issue is resolved.  Let me know if it isn't.

For anyone finding this, just wanted to call out that enabling data collection (as indicated above) via calling this on your first script will typically fix this issue:
FirebaseAnalytics.SetAnalyticsCollectionEnabled(true);

I had the same issue: worked on android but not iOS.  No idea why this works, but they should really make this more clear in the docs for Firebase Analytics if this is a true requirement.
Also confusing was that I did have something in the logs relating to Firebase Analytics before making the SetAnalyticsCollectionEnabled call (below).  Note that seeing a single log entry like the line below does not indicate Firebase Analytics is on and tracking properly.
[Firebase/Analytics][I-ACS031010] Tracking view controller.

just a note
FirebaseAnalytics.SetAnalyticsCollectionEnabled(true);

on iOS that is:
AnalyticsConfiguration.shared().setAnalyticsCollectionEnabled(true)

I'm having this same issue and I can't figure out how to fix it.
Has anyone here found a solution?

Having same issue. Getting error:
My environment:
Windows
Visual Studio 2017 version 15.8.9
Nuget Packages:
Xamarin.Firebase.iOS.Analytics - 5.1.4
Xamarin.Firebase.iOS.Core - 5.1.3
Xamarin.Firebase.iOS.InstanceID - 3.2.1
@smhk @stewartmiles , any idea how to fix it in Xamarin Visual Studio?
I am adding line Firebase.Core.App.Configure();
before return base.FinishedLaunching(app, options); in
FinishedLaunching event in AppDelegate

@niraj-bpsoftware the Xamarin SDK is authored and maintained by Microsoft and some open source contributors you can report bugs / ask them about it here https://github.com/xamarin/GooglePlayServicesComponents/

Ok thanks @stewartmiles

Hi,我想我遇见同样的问题了，这是返回的，我截取关键的
2019-09-26 16:31:11.060991+0800 DemoRealm[22499:434703] 6.6.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60100000 started
2019-09-26 16:31:11.061113+0800 DemoRealm[22499:434703] 6.6.0 - [Firebase/Analytics][I-ACS023008] To disable debug logging set the following application argument: -noFIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
2019-09-26 16:31:11.061240+0800 DemoRealm[22499:434703] 6.6.0 - [Firebase/Analytics][I-ACS023009] Debug logging enabled
2019-09-26 16:31:11.131877+0800 DemoRealm[22499:434708] 6.6.0 - [Firebase/Analytics][I-ACS029014] Successfully parsed a configuration. Version:<PHONE_NUMBER>507383
2019-09-26 16:31:11.132021+0800 DemoRealm[22499:434697] 6.6.0 - [Firebase/Analytics][I-ACS023016] Analytics is ready to receive events
2019-09-26 16:31:11.155143+0800 DemoRealm[22499:434708] 6.6.0 - [Firebase/Analytics][I-ACS032003] iAd framework is not linked. Search Ad Attribution Reporter is disabled.
2019-09-26 16:31:11.157415+0800 DemoRealm[22499:434712] 6.6.0 - [Firebase/Analytics][I-ACS023024] No data to upload. Upload task will not be scheduled
2019-09-26 16:31:11.158176+0800 DemoRealm[22499:434711] 6.6.0 - [Firebase/Analytics][I-ACS023012] Analytics enabled
2019-09-26 16:31:11.162668+0800 DemoRealm[22499:434697] 6.6.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: CrashController, -8387759398351854882
2019-09-26 16:31:11.162744+0800 DemoRealm[22499:434697] 6.6.0 - [Firebase/Analytics][I-ACS031013] Screen view event not logged. App is not active.
2019-09-26 16:31:11.166333+0800 DemoRealm[22499:434722] 6.6.0 - [Firebase/Analytics][I-ACS033003] Scheduling user engagement timer
2019-09-26 16:31:11.166871+0800 DemoRealm[22499:434722] 6.6.0 - [Firebase/Analytics][I-ACS002002] Engagement timer scheduled to fire in approx. (s): 3600
2019-09-26 16:31:11.179258+0800 DemoRealm[22499:434712] 6.6.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, screen_view (_vs), {
2019-09-26 16:31:11.183429+0800 DemoRealm[22499:434727] 6.6.0 - [Firebase/Analytics][I-ACS023073] Debug mode is enabled. Marking event as debug and real-time. Event name, parameters: screen_view (_vs), {
2019-09-26 16:31:11.191872+0800 DemoRealm[22499:434712] 6.6.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: screen_view (_vs), {
2019-09-26 16:31:11.193440+0800 DemoRealm[22499:434727] 6.6.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 0.9726080894470215
2019-09-26 16:31:11.193604+0800 DemoRealm[22499:434727] 6.6.0 - [Firebase/Analytics][I-ACS023028] Upload task scheduled to be executed in approx. (s): 0.9726080894470215
2019-09-26 16:31:12.262132+0800 DemoRealm[22499:434712] 6.6.0 - [Firebase/Analytics][I-ACS002001] Measurement timer fired
2019-09-26 16:31:12.262396+0800 DemoRealm[22499:434712] 6.6.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2019-09-26 16:31:12.262686+0800 DemoRealm[22499:434712] 6.6.0 - [Firebase/Analytics][I-ACS023033] Starting data upload
2019-09-26 16:31:12.264323+0800 DemoRealm[22499:434712] 6.6.0 - [Firebase/Analytics][I-ACS023105] Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters: screen_view (_vs), {
2019-09-26 16:31:12.267334+0800 DemoRealm[22499:434712] 6.6.0 - [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 420
2019-09-26 16:31:12.267531+0800 DemoRealm[22499:434712] 6.6.0 - [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 11,<PHONE_NUMBER>165
2019-09-26 16:31:12.269473+0800 DemoRealm[22499:434712] 6.6.0 - [Firebase/Analytics][I-ACS023038] Uploading events. Elapsed time since last successful upload (s):<PHONE_NUMBER>480072
2019-09-26 16:31:12.269598+0800 DemoRealm[22499:434712] 6.6.0 - [Firebase/Analytics][I-ACS023039] Measurement data sent to network. Timestamp (ms), data:<PHONE_NUMBER>269, <APMPBMeasurementBatch: 0x60000200cbf0>
2019-09-26 16:31:12.271454+0800 DemoRealm[22499:434727] 6.6.0 - [Firebase/Analytics][I-ACS900000] Uploading data. Host: https://app-measurement.com/a
2019-09-26 16:31:12.343835+0800 DemoRealm[22499:434727] 6.6.0 - [Firebase/Analytics][I-ACS901006] Received SSL challenge for host. Host: https://app-measurement.com/a
2019-09-26 16:31:12.427019+0800 DemoRealm[22499:434721] 6.6.0 - [Firebase/Analytics][I-ACS023044] Successful upload. Got network response. Code, size: 204, -1
2019-09-26 16:31:12.429486+0800 DemoRealm[22499:434697] 6.6.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): -0.2642010450363159
2019-09-26 16:31:12.429662+0800 DemoRealm[22499:434697] 6.6.0 - [Firebase/Analytics][I-ACS023028] Upload task scheduled to be executed in approx. (s): -0.2642010450363159
2019-09-26 16:31:12.432034+0800 DemoRealm[22499:434721] 6.6.0 - [Firebase/Analytics][I-ACS023024] No data to upload. Upload task will not be scheduled
2019-09-26 16:31:12.432176+0800 DemoRealm[22499:434721] 6.6.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
实际上自定义事件的，都可以打印和在DubugView上显示，但是crash事件显示不了，不知道跟
ACS023024] No data to upload. Upload task will not be scheduled
2019-09-26 16:31:12.432176+0800 DemoRealm[22499:434721] 6.6.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
这个有什么关系吗？我搜索了半天一直也没有答案。我是按照 https://firebase.google.com/docs/crashlytics/force-a-crash?authuser=0  这个文档来测试Firebase Crashlytics 实现，强制崩溃事件，我已经研究了两天，期待您的回复！


"Failed to change helper page protection to read / write" assert on macOS Big Sur (Rosetta 2)

Hi all,
In the process of preparing our product for the Apple ARM switch, running a CoreRT compiled binary, we're hitting this assert:
https://github.com/dotnet/corert/blob/bb212a9d2083046724f48e206f47b7dfb78d9979/src/Native/Runtime/unix/PalRedhawkUnix.cpp#L1207
I suspect this may be related to how Rosetta 2 translates/recompiles instructions on the fly which could mean they might disallow read/write access to code pages - but I can't find any documentation on whether or not that's the case.
Is there another way to flush the process write buffers rather than using the mprotect call, that we could utilize for Big Sur / Rosetta 2?

I suspect that newer macOS does not like switching the page protection on pages mapped from the binary. Allocating the special page using mmap like what we are doing in CoreCLR should fix that: https://github.com/dotnet/runtime/blob/6072e4d3a7a2a1493f514cdf4be75a3d56580e84/src/coreclr/src/pal/src/thread/process.cpp#L3506
A separate question is about the right way to implement this on Apple Silicon. It is something we have identified as a problem that will need investigation.

Thanks for the quick reply, Jan!
This is how it's currently allocated as far as I understand:
https://github.com/dotnet/corert/blob/bb212a9d2083046724f48e206f47b7dfb78d9979/src/Native/gc/unix/gcenv.unix.cpp#L341
It looks identical permission wise to the CoreCLR method - but maybe I'm looking in the wrong place?

Yes, you are right (I was looking in the wrong place).
I do not see anything obviously different. CoreCLR works fine Rosette 2 as far we know. It would be interesting to find out where it differs.

Thanks @Suchiman, I'll try that out and report back, hopefully with a PR if I get it working.

@christianscheuer Do you plan to send a PR for this one as well?

Yes, sorry for not updating here - when testing now I weirdly am not getting the error, probably due to the fact that I had to make a few changes to our build due to the other issues. The build I mentioned working flawlessly was without this fix - probably because I'm not hitting the code path that triggered this any longer.
I'll keep testing this more thoroughly with the older build that triggered this and hopefully I can get it to still repro. Will submit PR or an update if I can get something working that makes sense.


[FEATURE] Send Alerts to specific channels based on test / folder pattern

Is your feature request related to a problem? Please describe.
Exploring Playwright as a solution for our needs, and one of the things we utilize is a reporter that lets us notify teams/channels based on their tests failing.
Describe the solution you'd like
The ability to notify a specific channel if a specific test/folder/pattern fails. So if a test in tests/auth/**.spec.ts fails, then notify the channel #auth-team.
Additional context
Add any other context or screenshots about the feature request here.

hmm, tricky.  Theres an existing config here:
https://github.com/ryanrosello-og/playwright-slack-report?tab=readme-ov-file#onfailurechannels
But its pretty basic, currently it only accepts a string of channels.
from what I understood, you want something like:
{
  ...
  onFailureChannels: [
    {
      channelName: "failed-auth-channel",
      pattern: "tests/auth/**.spec.ts",
    },
    {
      channelName: "generic-automation-failures",
      pattern: "*",
    },
  ],
  ...
};

@fspinillo ?

hi guys!
I needed the same thing so I made a fork of the repo and implemented some functions for:

send failures to different channels, filtering tests by a specific pattern
configure a different report for failures report

I think my code was not very well organized, and some tests fail because they should be updated. That's why I didn't make a request to add changes to the ryanrosello repo.
Feel free to analyze the changes and incorporate them to the main repo.
any suggestions are welcome

link to the forked repo


Error: Cannot find module '@verdaccio/cli'

Your Environment

verdaccio version: 7.0.0-next.2
node version 18
package manager<EMAIL_ADDRESS>os: [mac]
platform: docker

Describe the bug

When I run pnpm run start:watch, it throws the error
Error: Cannot find module '@verdaccio/cli'
/opt/verdaccio-build # pnpm run start:watch

> verdaccio-dev@ start:watch /opt/verdaccio-build
> concurrently --kill-others "pnpm _build:watch" "pnpm _start:server" "pnpm _debug:reload"

[1]
[1] > verdaccio-dev@ _start:server /opt/verdaccio-build
[1] > node --inspect packages/verdaccio/debug/bootstrap.js --listen 8000
[1]
[2]
[2] > verdaccio-dev@ _debug:reload /opt/verdaccio-build
[2] > nodemon -d 3 packages/verdaccio/debug/bootstrap.js
[2]
[1] Debugger listening on ws://<IP_ADDRESS>:9229/1d513886-117d-4889-844e-1d620cc4db61
[1] For help, see: https://nodejs.org/en/docs/inspector
[0]
[0] > verdaccio-dev@ _build:watch /opt/verdaccio-build
[0] > pnpm run --parallel watch --filter ./packages
[0]
[2] [nodemon] 2.0.20
[2] [nodemon] to restart at any time, enter `rs`
[2] [nodemon] watching path(s): *.*
[2] [nodemon] watching extensions: ts,json,js
[2] [nodemon] starting `node packages/verdaccio/debug/bootstrap.js`
[1] node:internal/modules/cjs/loader:1080
[1]   throw err;
[1]   ^
[1]
[1] Error: Cannot find module '@verdaccio/cli'
[1] Require stack:
[1] - /opt/verdaccio-build/packages/verdaccio/debug/bootstrap.js
[1]     at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
[1]     at Module._load (node:internal/modules/cjs/loader:922:27)
[1]     at Module.require (node:internal/modules/cjs/loader:1143:19)
[1]     at require (node:internal/modules/cjs/helpers:119:18)
[1]     at Object.<anonymous> (/opt/verdaccio-build/packages/verdaccio/debug/bootstrap.js:5:1)
[1]     at Module._compile (node:internal/modules/cjs/loader:1256:14)
[1]     at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
[1]     at Module.load (node:internal/modules/cjs/loader:1119:32)
[1]     at Module._load (node:internal/modules/cjs/loader:960:12)
[1]     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:86:12) {
[1]   code: 'MODULE_NOT_FOUND',
[1]   requireStack: [ '/opt/verdaccio-build/packages/verdaccio/debug/bootstrap.js' ]
[1] }
[1]
[1] Node.js v18.18.0
[1]  ELIFECYCLE  Command failed with exit code 1.
[1] pnpm _start:server exited with code 1
--> Sending SIGTERM to other processes..
[0]  ELIFECYCLE  Command failed.
[0] pnpm _build:watch exited with code SIGTERM
--> Sending SIGTERM to other processes..
[2] pnpm _debug:reload exited with code SIGTERM
 ELIFECYCLE  Command failed with exit code 1.

I've never manage to make work correctly pnpm start:watch correctly, please use pnpm start and always do pnpm build locally first, every package is independent need to be build first.


Add Situation value object

Motivation and Context
There is repeated logic throughout the services which verifies
the validity of the situation string for ActionFeedback
(limited to 100 chars). This class moves that validation
to a single place but ActionFeedback still expects a string.
For now the toString() method can be used but it would be
better if ActionFeedback accepted a proper Situation type
in the future (not sure if this is possible with the jaxb
generated class).
What has changed
Add Situation value object.
How to test?
This only adds to the API so just run the unit tests.
Links
[will link to the PR that uses this once opened]

 Create an auto-verifying notify endpoint service


About Virtual Fly Brain

Description of the issue
WADCHAIN
This form is for VFB bug reports and feature requests.
If you need help, please use the forum.
Describe the bug or feature request in detail.
Always include a code snippet, screenshots, and any relevant data to help us understand your issue.
Browser

[x] All of them
[ ] Chrome
[ ] Firefox
[ ] Internet Explorer

OS

[ ] All of them
[x] Windows
[ ] macOS
[x] Linux
[x] Android
[ ] iOS

no issue described, possible duplicate of #382


Apply cahced setting calls ASAP

The SDR block will cache any settings calls while the future is busy setting up the device handle. Currently, these cached calls are forcibly applied when the block is activated. However, they should really be applied ASAP when the device handle is setup.
Meaning that the std::future task should run through all settings calls after its finished getting a device handle. Some extra synchronization will be needed to protect the cached settings while the future is processing them because additional settings could potentially be made.  Possibly, we can just make a dedicated execution thread in the place of using std::future.
Fixing this issue means that the block will continue to set itself up while the topology activates, but without blocking calls. This is because talking out to hardware can be a costly or long operation, such as calibration and waiting on time-outs. A block, its stream, and configuration will be fully setup by the time activate() is called.

Some updates:

Working on implementation on this branch: https://github.com/pothosware/pothos-sdr/tree/sdr_thread
Consider a default blocking mode which blocks for completion on all calls
An optional threaded background mode which is set by the GUI by default
And event squashing should be configurable: never, always, after activation


BLAST issue after July 5 downtime

Greetings!
Error message when trying to blast against private genomes ( e.g. 1502.1869  or 1502.2501 )
We were not able to complete your BLAST request. Please let us know with detail message below.
mkdir<EMAIL_ADDRESS>Permission denied

Try it again now.

It worked!  Thanks so much, Bob!

You are welcome.


releases.json isn't up to date

releases.json isn't up to date
The json file located here: https://github.com/dotnet/core/blob/master/release-notes/releases.json (and where the .NET Core SDK Installer build task points to) doesn't seem to be up to date. I am missing a lot of runtimes in there. Some I have checked are 2.1.10, 2.1.11, 2.1.12 (and also the SDKs are missing for example 2.1.801). Is this file still being updated? And why are these runtimes missing?
Tagging @leecow since he seems to be the last one who updated this file :).

That file is no longer being updated and instead you should be using https://github.com/dotnet/core/blob/master/release-notes/releases-index.json together with version-specific releases.json (e.g. https://github.com/dotnet/core/blob/master/release-notes/2.1/releases.json). See https://github.com/dotnet/announcements/issues/87 for more details.
Though that announcement also says that the old releases.json should have been removed, which hasn't happened.

@svick ahhh! I totally missed that announcement. I also see now that they updated the azure-pipelines task to point to releases-index.json instead. That they haven't removed it yet is a bit confusing though but good to know I shouldn't look at it anymore!

Sorry for the confusion! Obsoleted files (json and csv) have been removed.


[Optimizer] Move AdamW in GluonNLP to MXNet

Description
Move the adamw optimizer defined here to MXNet. https://github.com/dmlc/gluon-nlp/blob/20321598a732d254d4a9e036eecbe0ae8abb48a0/src/gluonnlp/optimizer.py#L31-L32

It should be moved to https://github.com/apache/incubator-mxnet/tree/master/python/mxnet/optimizer


how to install it

Hello,
we are interested in using you sonar plugin to do test on https://www.argonaut-project.org/ who is written in perl.
Could you give us some instructions on how to install your plugin
Cheers

There is a gradle build script inside the project. You can build the gradle project, and it will create a java plugin that you need to put inside your sonarqube server. The setup is similar adding plugins for other languages.

perl critic output is defaulted to "perlcritic.txt".

Sorry, I haven't watched comments on my repo too closely. I'll add some docs once I have a bit of time to continue on this. As for now if you only want to test the plugin, the simplest thing would be to start up the docker container that has sonarqube with this plugin included, by calling ./gradlew sonar-perl-plugin:run. Otherwise, as @mxlei01 said, do a gradlew sonar-perl-plugin:build and copy the resulting jar file sonar-perl-plugin/build/sonar-perl-plugin-0.1.jar into the plugins dir of your sonar installation (should be sth. like /opt/sonarqube/extensions/plugins/)

Added some documentation on the README.md. I also simplified the use-case of trying out the project, using docker-compose.

BTW: I have just simplified the sample project integration even further. It should be very straight forward for any perl project now to run sonar-scanner based analysis against a local sonarqube by adding this kind of Dockerfile:
https://github.com/otrosien/sonar-perl/blob/master/perl/sample-project/Dockerfile


Error: Migration engine exited (Docker on M1 Max)

Bug description
I am getting this error while running Prisma inside a Docker container on M1 Max:
2022-12-01T21:12:33.935Z prisma:engines  binaries to download libquery-engine, migration-engine, introspection-engine, prisma-fmt
2022-12-01T21:12:34.240365632Z 2022-12-01T21:12:34.240Z prisma:loadEnv  project root found at /usr/local/app/package.json
2022-12-01T21:12:34.242856299Z 2022-12-01T21:12:34.242Z prisma:tryLoadEnv  Environment variables not found at null
2022-12-01T21:12:34.242979757Z 2022-12-01T21:12:34.242Z prisma:tryLoadEnv  Environment variables not found at undefined
2022-12-01T21:12:34.243005382Z 2022-12-01T21:12:34.242Z prisma:tryLoadEnv  No Environment variables loaded
2022-12-01T21:12:34.245266257Z 2022-12-01T21:12:34.245Z prisma:getConfig  Using getConfig Wasm
2022-12-01T21:12:34.249764841Z 2022-12-01T21:12:34.249Z prisma:getConfig  config data retrieved without errors in getConfig Wasm
2022-12-01T21:12:34.250321132Z 2022-12-01T21:12:34.250Z prisma:loadEnv  project root found at /usr/local/app/package.json
2022-12-01T21:12:34.252674591Z 2022-12-01T21:12:34.252Z prisma:tryLoadEnv  Environment variables not found at null
2022-12-01T21:12:34.252717674Z 2022-12-01T21:12:34.252Z prisma:tryLoadEnv  Environment variables not found at undefined
2022-12-01T21:12:34.253228924Z 2022-12-01T21:12:34.253Z prisma:tryLoadEnv  No Environment variables loaded
2022-12-01T21:12:34.253870091Z Prisma schema loaded from prisma/schema.prisma
2022-12-01T21:12:34.255586924Z 2022-12-01T21:12:34.255Z prisma:getConfig  Using getConfig Wasm
2022-12-01T21:12:34.256507382Z 2022-12-01T21:12:34.256Z prisma:getConfig  config data retrieved without errors in getConfig Wasm
2022-12-01T21:12:34.258214882Z Datasource "db": PostgreSQL database "antimony_events_dev", schema "public" at "db-events:5432"
2022-12-01T21:12:34.260412216Z 2022-12-01T21:12:34.260Z prisma:getConfig  Using getConfig Wasm
2022-12-01T21:12:34.262079966Z 2022-12-01T21:12:34.261Z prisma:getConfig  config data retrieved without errors in getConfig Wasm
2022-12-01T21:12:34.286840799Z
2022-12-01T21:12:34.287205924Z Error: Error: Migration engine exited.
2022-12-01T21:12:34.287249132Z     at canConnectToDatabase (/usr/local/app/node_modules/prisma/build/index.js:92248:13)
2022-12-01T21:12:34.287253341Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2022-12-01T21:12:34.287256049Z     at async ensureDatabaseExists (/usr/local/app/node_modules/prisma/build/index.js:92965:22)
2022-12-01T21:12:34.287258424Z     at async _MigrateDeploy.parse (/usr/local/app/node_modules/prisma/build/index.js:95028:28)
2022-12-01T21:12:34.287266632Z     at async main (/usr/local/app/node_modules/prisma/build/index.js:98523:18)

My Dockerfile:
FROM node:alpine AS build

RUN apk add openssl

WORKDIR /usr/local/app
COPY package.json tsconfig.json nodemon.json babel.config.js jest.config.js ./

RUN yarn install --pure-lockfile --non-interactive --production=false

ENV PATH="/usr/local/app/node_modules/.bin:${PATH}"
# ENV NODE_ENV="production"

## Add the wait script to the image
ADD https://github.com/ufoscout/docker-compose-wait/releases/download/2.9.0/wait /wait
RUN chmod +x /wait

ENV DEBUG="prisma*"

CMD /wait && prisma migrate deploy && prisma generate && yarn start

How to reproduce

Expected behavior
the migration should succeed (it works when using platform: 'linux/amd64' in docker-compose.yml OR when using the ARM version of node:slim -- only alpine is affected)
Prisma information

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

Environment & setup

OS: macOS (M1 Max, Docker with Linux Alpine)
Database: PostgreSQL
Node.js version: v19.2.0

Prisma Version
prisma                  : 4.7.0
2022-12-01T21:14:56.969825546Z @prisma/client          : 4.7.0
2022-12-01T21:14:56.969827462Z Current platform        : linux-arm64-openssl-1.1.x
2022-12-01T21:14:56.969829171Z Query Engine (Node-API) : E_CANNOT_RESOLVE_VERSION (at<EMAIL_ADDRESS>2022-12-01T21:14:56.969831212Z Migration Engine        : E_CANNOT_RESOLVE_VERSION (at<EMAIL_ADDRESS>2022-12-01T21:14:56.969833004Z Introspection Engine    : E_CANNOT_RESOLVE_VERSION (at<EMAIL_ADDRESS>2022-12-01T21:14:56.969841546Z Format Binary           : E_CANNOT_RESOLVE_VERSION (at<EMAIL_ADDRESS>2022-12-01T21:14:56.969843421Z Format Wasm             : @prisma/prisma-fmt-wasm 4.7.0-74.39190b250ebc338586e25e6da45e5e783bc8a635
2022-12-01T21:14:56.969845129Z Default Engines Hash    : 39190b250ebc338586e25e6da45e5e783bc8a635
2022-12-01T21:14:56.969846879Z Studio                  : 0.477.0

Alpine Linux on ARM64 is now supported as of Prisma 4.10.0 and newer. I'll go ahead and close this issue.


reorganization-edit docs for WP

What's relationship between this and #1979?

Bryan suggested I do this, so that he could merge the files.  We are keeping the other PR to preserve the conversation.  I think because I was merging the master into my branch, instead of rebasing or something like that.

This replaces #1979


chore: IE11 EOL and un-rollup files

Using bundle-size we recently discovered that due to es6 classes and
statics, things were leaking into the bundle that shouldn't be there.
This PR modifies the build to create two separate directories:

lib -> es6 modules
lib-commonjs -> commonjs

The PR also changes the target to ES2019 (EOL for IE11 🪦). However, this results in bundle size improvements shown below:
Before:

After:

closed in favour of #95 to release alpha, so the repo can be tagged


Cost Explorer Reports support

Describe the feature
Cost explorer has an ability to save reports in the web console
There is no cli support
There is no botocore support
There is no documented API
Use Case
Our billing group needs an easy way to get started in cost explorer. The easiest way to do this is to save reports. However we use terraform to automate everything we do in the web interface. Without this, there is no way to periodically check that changes haven't been made.
Proposed Solution

Add the api documentation to the aws cost explorer website
Implement support for it in botocore (I'd like to take a crack at this)

Other Information
No response
Acknowledgements

[X] I may be able to implement this feature request
[ ] This feature might incur a breaking change

SDK version used
2
Environment details (OS name and version, etc.)
n/a

Approval seems needed before I try to put up a PR because there is no documented API for this.
Using the network tab of the console I see things like:
http method: PUT
endpoint: https://us-east-1.console.aws.amazon.com/cost-management/data/report/v2/createReport
{
  "reportName": "jjshoe-test",
  "reportType": "COST_USAGE",
  "chartStyle": "GROUP",
  "queryAttributes": {
    "filter": null,
    "granularity": "MONTHLY",
    "metrics": [
      "NET_UNBLENDED_COST"
    ],
    "historicalTimePeriod": {
      "historicalOption": "LAST_3_MONTHS"
    }
  }
}

http method: GET
endpoint: https://us-east-1.console.aws.amazon.com/cost-management/data/report/v2/getReports
[
  {
    "reportId": "changed",
    "reportName": "jjshoe-test",
    "queryAttributes": {
      "historicalTimePeriod": {
        "historicalOption": "LAST_3_MONTHS"
      },
      "metrics": [
        "NET_UNBLENDED_COST"
      ],
      "granularity": "MONTHLY"
    },
    "createdAt":<PHONE_NUMBER>443,
    "updatedAt":<PHONE_NUMBER>443,
    "isDefault": false,
    "default": false,
    "reportType": "COST_USAGE",
    "chartStyle": "GROUP"
  }
]

@tim-finnigan it would be additions to the CE space. Cost and usage reports, as far as I understand, generates data which gets delivered to an s3 bucket, and not viewable int he web like reports in CE are.

@tim-finnigan it would also be great to know if the calls I documented above are part of the API, but not documented, or in fact are not part of the "official" api.

Hi @jjshoe thanks for following up. I don't know the answers to your questions but reached out to the Cost Explorer team to try and get more information. I also created a new issue for this in our cross-SDK repository: https://github.com/aws/aws-sdk/issues/315. Please refer to that issue for updates going forward.


BUG: Conflict with Magento's RequireJS

Hey!
A number of people have said that there are possible conflicts on sites running Magento and trying to load the web-vitals library.
For example, if you visit https://www.foeger.com/eu_de/ and try to load the web-vitals library, the window.webVitals namespace is never created. Magento uses RequireJS, and it seems like this could be the cause of the conflict.
Sorry for not being able to define the bug any better, but it does seem to be a recurring problem on sites running Magento and/or RequireJS.

Ahh, I see how the example on the docs wouldn't work if the page is using RequireJS or another AMD loader. For a site using RequireJS, you'd want to load it like this:
require(['https://unpkg.com/web-vitals'], (webVitals) => {
    webVitals.getCLS(console.log);
    webVitals.getFID(console.log);
    webVitals.getLCP(console.log);
});

However, it probably doesn't make sense for your template to include a conditional that can load the script both ways depending on the environment.
I can see a few options to fix this:

Your template could load the library using a module script (e.g. either <script type="module">, or using dynamic import()). However, I seem to remember GTM not allowing any ES6, so I'm not sure if this is possible.

I could add another build of the library that just creates a browser global, and then your template could load that script. The URL would be something like: https://unpkg.com/web-vitals/dist/web-vitals.iife.js

What do you think?

Thanks - I think your final option (2) is the best in terms of GTM's template sandbox. The sandbox does allow ES6 but only selected things which have been transpiled into the sandbox JS (e.g. arrow functions, const/let), and there's no guarantee these features would get added in the future.
So having a "regular" JS script injection is likely the best option for custom templates. Thanks for looking into this!
Simo

I've added the "iife" script version discussed in option (2), and I've published v2 of the library, so you should be able to update your template to inject the following script URL:
https://unpkg.com/web-vitals/dist/web-vitals.iife.js
Let me know if this doesn't fix the issue for some reason.


 Does it mean that hotspots in 7381 will be removed from denylist?

Are you going close 7391? Does it mean that hotspots in 7381 will be removed from denylist?

No, it just closes the PR. The issue should still remain I hope.

Are you going close 7391? Does it mean that hotspots in 7381 will be removed from denylist?

No, it just closes the PR. The issue should still remain I hope.

ok perfect, thank you


Structurally assignable generic types with an object contraint are not assignable, when their properties are a type expression of the constraint

Bug Report
🔎 Search Terms
generic object type assignment
🕗 Version & Regression Information
This is the behavior in every version I tried, and I reviewed the FAQ for all entries on "bugs that aren't bugs", and nothing matches.
⏯ Playground Link
Playground link with relevant code
💻 Code
declare const makeType: <T>() => T;

export type A<T extends { a:unknown }> = {
   readonly foo: T["a"] | string
}

const ok: A<{a:number}>["foo"] = makeType<A<{a:string}>["foo"]>();
const whyError1: A<{a:number}> = makeType<A<{a:string}>>();
const whyError2: A<{a:number,b:string}> = makeType<A<{a:string}>>();
const whyError3: A<{a:number,b:string}> = makeType<A<{a:number,b:boolean}>>();

Note that in the code above:

The type { readonly foo: string } is assignable to A<T> for all T.
A<{ a: string } is { readonly foo: string }.

🙁 Actual behavior
The assignments of whyError1, whyError2, whyError3 fail even though the types on both sides structurally resolve to what should be assignable types.

For whyError1 and whyError2, LHS resolves to { readonly foo: number|string }, RHS resolves to { readonly foo: string }.
For whyError3, both LHS and RHS resolve to { readonly foo: number|string}.

🙂 Expected behavior
All assignments should be allowable.

FWIW, if the type is instead defined like this:
export type A<T extends { a:unknown }> = T extends { a: infer X } ? {
   readonly foo: X | string
} : never

Then all assignments work. However, this form makes it impossible to make A an interface.
Also, the OP gives a minimal example of the behavior. In reality, the constraint T is being thrown around in a number of types, interfaces and functions, and has several properties.

We intentionally take a completeness/performance trade-off here since this situation isn't particularly common, and always performing a structural check when a reliable variance measurement exists is extremely expensive.


Greenboot fails due to missing '/etc/ostree/remotes.d/fedora-iot.conf'

Describe the bug
Recent disk images no longer include the '/etc/ostree/remotes.d/fedora-iot.conf' file parsed by greenboot.
As a result when logging into a system:
Script '01_update_platforms_check.sh' FAILURE (exit code '1'). Continuing...
Boot Status is GREEN - Health Check SUCCESS
To Reproduce
Please describe the steps needed to reproduce the bug:

Boot recent Fedora 39 IoT disk image
SSH in

Expected behavior
No script failure.
Additional context
The system can still be updated, the remote repository information is now included in:
cat /sysroot/ostree/repo/config
[core]
repo_version=1
mode=bare
[remote "fedora-iot"]
url=https://ostree.fedoraproject.org/iot
gpgkeypath=/etc/pki/rpm-gpg/
gpg-verify=true
contenturl=mirrorlist=https://ostree.fedoraproject.org/iot/mirrorlist
[sysroot]
bootloader=none
readonly=true

investigate why the change has happened first
take a look at https://github.com/fedora-iot/greenboot/pull/116

Need a F40 IoT build that includes the RPM with ostree remote config to assess the current state of the problem.
Likely have to sort out why the remote config is landing under /sysroot/ostree/repo; possibly an rpm-ostree/ostree behavior?

In Fedora 40, there is no longer a greenboot error as the remote is included in /etc/ostree/remotes.d/fedora-iot.conf as expected (provided by fedora-iot-config). The remote is no longer included in /sysroot/ostree/repo/config so there is no conflict and updates work.
In Fedora 39, the disk image - Fedora-IoT-39-20240201.0.aarch64.raw.xz - the remote has also been removed from  /sysroot/ostree/repo/config, resulting in an error:
rpm-ostree status
State: idle
Deployments:
● fedora-iot:fedora/stable/aarch64/iot
       OstreeRemoteStatus: Remote "fedora-iot" not found
                  Version: 39.20240201.0 (2024-02-01T18:02:07Z)
                   Commit: 01b59135918d7b465a8dfaad2429c4331fad2a7f2c60e64050bd569f3f06ab22

To get updates working again:
ostree remote add --set=gpg-verify=true --set=gpgkeypath=/etc/pki/rpm-gpg/ --set=contenturl=mirrorlist=https://ostree.fedoraproject.org/iot/mirrorlist  fedora-iot 'https://ostree.fedoraproject.org/iot'

This change seems to only affect new disk images, testing our GA image from 39.20231103.1 and upgraded was ok:
[root@localhost ~]# rpm-ostree status
State: idle
Deployments:
● fedora-iot:fedora/stable/aarch64/iot
                  Version: 39.20240201.0 (2024-02-01T18:02:07Z)
                   Commit: 01b59135918d7b465a8dfaad2429c4331fad2a7f2c60e64050bd569f3f06ab22
             GPGSignature: Valid signature by E8F23996F23218640CB44CBE75CF5AC418B8E74C

  fedora-iot:fedora/stable/aarch64/iot
                  Version: 39.20231103.1 (2023-11-03T18:17:43Z)
                   Commit: cc8d419f72d84ac24d0a95e235c0cdf72844f73d9d6f42a41fcddf23dfb34f7d
             GPGSignature: Valid signature by 6A51BBABBA3D5467B6171221809A8D7CEB10B464
[root@localhost ~]# cat /sysroot/ostree/repo/config
[core]
repo_version=1
mode=bare

[remote "fedora-iot"]
url=https://ostree.fedoraproject.org/iot
gpgkeypath=/etc/pki/rpm-gpg/
gpg-verify=true
contenturl=mirrorlist=https://ostree.fedoraproject.org/iot/mirrorlist

[sysroot]
bootloader=none
readonly=true

Disk images from Fedora 38 included the remote in /etc/ostree/remotes.d/fedora-iot.conf and continue to work on upgrade.

Disk image from  Fedora-IoT-39.20231208.0-20231208.0.aarch64.raw includes the remote in /sysroot
As of  Fedora-IoT-39.20231214.0-20231214.0.aarch64.raw, the remote is no longer included at all.

● fedora-iot:fedora/stable/aarch64/iot
       OstreeRemoteStatus: Remote "fedora-iot" not found
                  Version: 39.20231214.0 (2023-12-15T01:47:31Z)
                   Commit: 536c86a9db2fa7b332a33f7d027ebf81226f52079990117563e2e37ba5f0259e

ostree version didn't change ostree-2023.7-2.fc39.aarch64

osbuild/images had a big jump from v0.15.0 > v0.18.0

We will need to add fedora-iot-config into F39 to fix this. Testing how best to do that as it will cause the legacy installer issues with duplicated remotes.

Some info that might help track this down (adding to Paul's comment above).
osbuild/images v0.18.0 included the change to the packaged remote config.  Instead of hard-coding the remote configuration in the disk image creation (which was replicating the disk creation kickstart), it was added in the fedora-iot-config package.  This was done for both Fedora 39 and 40.
That change was included in osbuild-composer v95.
The change was merged into osbuild-composer here: https://github.com/osbuild/osbuild-composer/commit/5b19bd6809fdffab5e7b26c666729eef44c2a14f
This change was planned for a while with Peter and Antonio.  The plan included packaging a remote configuration with fedora-iot-config, install the package in the iot-commit itself, and stop setting it during disk creation or in the Anaconda kickstart.

PR to add a script to detect and fix the remote

This is fixed in fedora-iot-config-1-1.fc39 and fedora-release-39-36 included in todays compose Fedora-IoT-39-20240226.0


[SPARK-40663][SQL] Migrate execution errors onto error classes: _LEGACY_ERROR_TEMP_2076-2100

What changes were proposed in this pull request?

This PR proposes to migrate 25 execution errors onto temporary error classes with the prefix _LEGACY_ERROR_TEMP_2076 to _LEGACY_ERROR_TEMP_2100.
The error classes are prefixed with _LEGACY_ERROR_TEMP_ indicates the dev-facing error messages, and won't be exposed to end users.
Why are the changes needed?

To speed-up the error class migration.
The migration on temporary error classes allow us to analyze the errors, so we can detect the most popular error classes.
Does this PR introduce any user-facing change?

No
How was this patch tested?
$ build/sbt "sql/testOnly org.apache.spark.sql.SQLQueryTestSuite"
$ build/sbt "test:testOnly *SQLQuerySuite"

@itholic Could you resolve conflicts here, please.

@itholic Please, fix the test failures:
[error] /home/runner/work/spark/spark/sql/catalyst/src/main/scala/org/apache/spark/sql/errors/QueryExecutionErrors.scala:1006:25: parameter 'messageParameters' is already specified at parameter position 2
[error] Note that 'errorSubClass' is not a parameter name of the invoked method.
[error]       messageParameters = Map("optionName" -> optionName))
[error]                         ^
[error] /home/runner/work/spark/spark/sql/catalyst/src/main/scala/org/apache/spark/sql/errors/QueryExecutionErrors.scala:1044:25: parameter 'messageParameters' is already specified at parameter position 2
[error] Note that 'errorSubClass' is not a parameter name of the invoked method.
[error]       messageParameters = Map.empty)
[error]                         ^
[error] two errors found

Fixed, thanks! :-)

+1, LGTM. Merging to master.
Thank you, @itholic.


Update renovatebot/github-action action to v38.1.11

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
patch
v38.1.8 -> v38.1.11

Release Notes

renovatebot/github-action (renovatebot/github-action)
v38.1.11
Compare Source
Build System

deps: update dependency typescript to v5.1.6 (b8d2871)

v38.1.10
Compare Source
Miscellaneous Chores

deps: update dependency @tsconfig/node16 to v16 (#776) (1da123a)
deps: update dependency lint-staged to v13.2.3 (e093539)

Build System

deps: update dependency semantic-release to v21.0.6 (4ab927d)

Continuous Integration

deps: update actions/setup-node action to v3.7.0 (9038e41)
deps: update renovate docker tag to v35.159.6 (0cf0a94)

v38.1.9
Compare Source
Documentation

update references to actions/checkout to v3.5.3 (ce294bf)

Miscellaneous Chores

deps: update commitlint monorepo to v17.6.6 (a8e4d64)
deps: update dependency @types/node to v16.18.37 (9952b36)
deps: update dependency prettier-plugin-package to v1.3.1 (087c455)
deps: update linters to v5.60.0 (b057bb5)
deps: update linters to v5.60.1 (5c09708)

Build System

deps: update dependency typescript to v5.1.5 (9143c4e)

Continuous Integration

deps: update renovate docker tag to v35.143.0 (e466248)
deps: update renovate docker tag to v35.144.0 (78dd8c4)
deps: update renovate docker tag to v35.144.2 (72da75e)
deps: update renovate docker tag to v35.144.3 (9cc209c)
deps: update renovate docker tag to v35.146.1 (7486463)
deps: update renovate docker tag to v35.147.0 (c5be64d)
deps: update renovate docker tag to v35.150.0 (f60632d)
deps: update renovate docker tag to v35.151.1 (5656713)
deps: update renovate docker tag to v35.154.0 (b4eab58)
deps: update renovate docker tag to v35.155.0 (b481ba1)
deps: update renovate docker tag to v35.156.0 (8e1d99d)
deps: update renovate docker tag to v35.157.1 (a0fd369)
deps: update renovate docker tag to v35.158.0 (c6313ab)
deps: update renovate docker tag to v35.159.1 (8e991b6)
deps: update renovate docker tag to v35.159.4 (88c3789)
deps: update renovate docker tag to v35.159.5 (a57504f)

Configuration
📅 Schedule: Branch creation - "before 5am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Branch automerge failure
This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


Add native style prop note

This was a point of confusion for me when I was getting set up with styled-components in react native.

I'll remind myself to add it to the website as well :)


[ceres] build failure

Host Environment

OS: windows
Compiler: VS 2019 default compiler
vcpkg version: 2021-09-10-2059ef11aa6067e6f59b0d939c5d17e3c5c47d3e

To Reproduce
Steps to reproduce the behavior:
`.\vcpkg install ceres --triplet=x64-windows
Failure logs
install-x64-windows-rel-out.log
Additional context

Tried install english language pack. [not working]
Tried completely remove vcpkg and perform complete reinstall. [not working]

Maybe related to https://github.com/ceres-solver/ceres-solver/issues/291.
Please remove and re-install glog and try again.

Thank you!

Maybe related to ceres-solver/ceres-solver#291. Please remove and re-install glog and try again.

Thanks, the aforementioned 'unresolved symbol' problem is solved now, however, a LINK 1168 error popped up. I managed to successfully get around it by disabling parallel install in ceres port. BTW, I encounter another LINK 1168 error when building openblas as well, solved it by disabling parallel.

mt.exe : general error c101008d: Failed to write the updated manifest to the resource of file "lib\openblas.dll". The requested operation cannot be performed on a file with a user-mapped section open.
Also related to the parallel build or anti virus.

And please do NOT use the same vcpkg for parallel build.

Do not use the same copy of vcpkg to execute the install command in different processes, and please turn off your anti-virus.

mt.exe : general error c101008d: Failed to write the updated manifest to the resource of file "lib\openblas.dll". The requested operation cannot be performed on a file with a user-mapped section open. Also related to the parallel build or anti virus.

Figured out, I deleted the openblas buildtree and it worked.

LINK : fatal error LNK1168: cannot open bin\ceres-debug.dll for writing
ninja: build stopped: subcommand failed.

Same as above, there must be some other threads accessing this file at the same time.

Can you please modify ports/ceres/portfile.cmake line 53 to:
vcpkg_install_cmake(DISABLE_PARALLEL)

And try again?

Can you please modify ports/ceres/portfile.cmake line 53 to:
vcpkg_install_cmake(DISABLE_PARALLEL)

And try again?

That's exactly what I do when I say about "disabling parallel". Still not working.


check fields regridded with TempestRemap

We found some issues with our TempestRemap code in the albedo (see https://github.com/CliMA/ClimaCoupler.jl/issues/764). We also need to check if other fields regridded with TR (e.g. surface fluxes) look okay or not.

Using the config/ci_configs/gpu_amip_albedo_temporal_map setup, I see the following fields for input data after they've been read in and regridded:

SST_init

SIC_init

land_area_fraction

CO2_init

The first three look good. The CO2 looks unusual, and we have minimum(CO2_init) == maximum(CO2_init) == 0.00037866, but I want to plot the NetCDF input before regridding to see if this comes from the regridding.

CO2 might be ok. I remember seeing strange patterns when plotting something uniform, as it comes up with a default colorbar with a very small range.

All of the regridded files look fine, so we can close this issue


Excessive Spikes of Star Shapes Not Drawing Correctly

Using the pyglet's shapes module, I drew a star.
Star(x=250, y=200, outer=30, inner=100, spikes=1000)

I think there is a glitch here. Maybe I could use that do make patterns.

That's certainly an interesting pattern.
I'm not sure if I would call it a bug, because it's really just how OpenGL renders things. The inner and outer "rings" are inverted, and there aren't enough pixels to show everything. Things might become discernable if you zoomed in a bit, or maybe played with anti-aliasing.
We could maybe add an assertion to that class that checks that the outer diameter is larger than the inner. 🤔


Extend the livecheck DSL to work for resources

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

This PR extends the livecheck DSL to work for resources as mentioned here.

As suggested by @nandahkrishna, I have verified livecheck DSL inside resource block by updating few resource blocks locally.
For instance: inside Library/Taps/homebrew/homebrew-core/Formula/airshare.rb, add the livecheck block inside the resource aiohttp like mentioned below:
...
  resource "aiohttp" do
    url "https://files.pythonhosted.org/packages/5a/86/5f63de7a202550269a617a5d57859a2961f3396ecd1739a70b92224766bc/aiohttp-3.8.1.tar.gz"
    sha256 "fc5471e1a54de15ef71c1bc6ebe80d4dc681ea600e68bfd1cbce40427f0b7578"
    livecheck do
      url "https://brew.sh/foo-1.0.tar.gz"
      regex(/foo/)
    end
  end
...

and from interactive ruby-shell (brew irb), run and check the following outputs:
:airshare.f.resources[0].livecheck.class
:airshare.f.resources[0].livecheck.url
:airshare.f.resources[0].livecheck.regex

and it works as expected.
=> Livecheck
=> "https://brew.sh/foo-1.0.tar.gz"
=> /foo/

Kindly, do let me know if I miss something or any further improvement that we can do here.

Thank you everyone for the valuable feedback. I have updated tests and relevant documentation (as suggested by @samford and @nandahkrishna). Do take a look and let me know if any changes are required.

Great work @mohammadzainabbas 🎉


[Program]: Write a R program to find cube of a number

Description
Write a R program to find cube of a number
Input  : 2
Output : 8

How to contribute

Save the solution in program/program/find-cube-of-a-number/find_cube_of_a_number.r file

!assign

!assign

!assign


DBT Snapshot filling in dbt_valid_to for most recent record

Describe the bug
We have a bug where a DBT Snapshot model is populating a timestamp in the column "dbt_valid_to" for the most recent record of a unique key. This happens for around 70k unique keys out of 20 million in our table. The snapshot is using the timestamp strategy. The row is not deleted in the source table.
Steps To Reproduce
config
`config(
unique_key='ID',
target_database='SNAPSHOT' if target.name != 'dev' else 'SNAPSHOT_DEV',
target_schema='SCHEMA',
strategy='timestamp',
updated_at='ROW_UPDATED_AT',
)`
DBT Version
It has been running on 0.16.0 but just upgraded to 0.18.0 in dbt cloud to see if it helps.
Expected behavior
The most recent row per unique key should have a NULL value in the dbt_valid_to column. When this gets populated it does two things:

It looks like the record is no longer active when it is
The update / insert logic when using snapshots seem to ignore this unique key now. When the record changes, no new entries occur

Screenshots and log output
Sql Query
 SELECT id 	,dbt_valid_from 	,dbt_valid_to FROM WAREHOUSE.SCHEMA.TABLE WHERE id = 4251182 ORDER BY dbt_valid_to DESC
Screenshot of Output

System information
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[ ] bigquery
[x] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
0.16.0

The operating system you're using:
DBT Cloud
The output of python --version:
This happens in dbt cloud
Additional context
Add any other context about the problem here.

@skamalgl It sounds like this is an error you experienced while using dbt v0.16.0. In that case, this bug sounds a lot like the one outlined in https://github.com/fishtown-analytics/dbt/issues/1884, which we resolved in v0.17.0. If that's so, upgrading is the ultimate resolution here.
That doesn't get you out of a tricky spot with the handful of records that were errantly updated without a corresponding insert. In that regard, your recourses are:

Correct those records manually by nullifying the dbt_valid_to of the most recent record.
Try out / wait for dbt v0.19.0 (currently in beta), which has an optional config for detecting hard-deleted records, both when they go missing and when they "revive." In this case, because there is no record with unique identifier 4251182, its next detection would be considered a revival.

I'm going to close this issue as a duplicate, but please continue to comment here if I've missed or misunderstood an important piece of this.


Add implementation of jump search algorithm

closes https://github.com/AlgoGenesis/C/issues/28

I am participating in gssoc-ext for the first time. Could you please assign me to this task?

you need to go into issues and create a new one there.