[10.14 Mojave] - Disable Mail.app remote content loading broken

macOS

Version: 10.14 Beta
Build: 18A293u

Describe the bug
When running Lockdown in fix mode the Disable automatic loading of remote content by Mail.app setting is not fixed. The fix_command fails with the message Could not write domain com.apple.mail-shared.
To Reproduce
Steps to reproduce the behavior:

Execute ./Lockdown fix
[❌] Failed to fix: Disable automatic loading of remote content by Mail.app

Expected behavior

[✅] FIXED: Disable automatic loading of remote content by Mail.app

Terminal Output
$ ./Lockdown fix
[⚠ ] You are about to engage FIX mode which WILL make changes to your Mac 💻
[⚠ ] Do you want to continue? (y/N) y
[✅] 0xmachos has chosen to continue
2018-06-04 23:23:34.454 defaults[1987:51908] Could not write domain com.apple.mail-shared; exiting
[❌] Failed to fix: Disable automatic loading of remote content by Mail.app
[⚠ ] No fix_command: Check EFI Firmware Integrity
[⚠ ] No fix_command: Check FileVault enabled
[⚠ ] No fix_command: Check firmware password set

Additional context
Executing defaults domains shows that com.apple.mail-shared is a valid domain. However executing defaults read com.apple.mail-shared returns the error Domain com.apple.mail-shared does not exist. The domain still doesn't exist after launching Mail.app and manually unchecking the setting.
There are no new domains with mail in the name.
I suspect this might be due to this being the first developer Beta of 10.14. Will test again when the next build comes out.

Running  sudo fs_usage -w -f filesystem then toggling the option in the Mail.app UI produces the following output:
23:11:23.522043  openat            F=3        (RWC__E)  [-2]//Users/0xmachos/Library/Preferences/com.apple.mail-shared.plist.OZF0cLm                                                                                0.000137   cfprefsd.9953
23:11:23.572801  lstat64                                /Users/0xmachos/Library/Preferences/com.apple.mail-shared.plist.OZF0cLm                                                                                0.000006   fseventsd.9887
23:11:25.263661  open                   [  2] (R_____)  /Users/0xmachos/Library/Containers/com.apple.mail/Data/Library/Preferences/ByHost>>>>>>>                                                                              0.000052   cfprefsd.9982
23:11:25.263854  open                   [  2] (R_____)  /Users/0xmachos/Library/Containers/com.apple.mail/Data/Library/Preferences/com.apple.coreaudio.plist                                                                  0.000027   cfprefsd.9982

$HOME/Library/Preferences/com.apple.mail-shared.plist is queried.
Executing defaults read $HOME/Library/Preferences/com.apple.mail-shared.plist produces the expected list of keys:
{
    AddressDisplayMode = 0;
    AlertForNonmatchingDomains = 0;
    DisableURLLoading = 1;
    ExpandPrivateAliases = 1;
}

Toggling the option in the Mail.app UI changes this value.
Still no idea why defaults read com.apple.mail-shared is returning Domain com.apple.mail-shared does not exist.

Running sudo fs_usage -w -f filesystem then toggling the option in the Mail.app UI produces the following output:
23:38:37.782960  openat            F=3        (RWC__E)  [-2]//Users/0xmachos/Library/Preferences/com.apple.mail-shared.plist.6BCtyGr                                                                                0.000548   cfprefsd.27438
23:38:38.339161  lstat64                                /Users/0xmachos/Library/Preferences/com.apple.mail-shared.plist.6BCtyGr                                                                                0.000051   fseventsd.7147

$HOME/Library/Preferences/com.apple.mail-shared.plist is queried.
Executing defaults read $HOME/Library/Preferences/com.apple.mail-shared.plist outputs:
2018-06-06 23:49:09.027 defaults[1547:37798]
Domain /Users/0xmachos/Library/Preferences/com.apple.mail-shared.plist does not exist

Executing this command again with sudo outputs:
{
    AddressDisplayMode = 0;
    AlertForNonmatchingDomains = 0;
    DisableURLLoading = 0;
    ExpandPrivateAliases = 1;
}

Executing sudo defaults read com.apple.mail-shared outputs:
2018-06-06 23:53:48.405 defaults[1586:39758]
Domain com.apple.mail-shared does not exist

Directly querying the .plist with sudo defaults read works but querying the domain name, even with sudo fails.
We can be reasonably sure that the preference is stored in the com.apple.mail-shared domain. No idea why the defaults read is saying the domain doesn't exist.

On High Sierra:
defaults read $HOME/Library/Preferences/com.apple.mail-shared.plist

Works without sudo.

On Mojave Developer Beta 2 com.apple.mail-shared is no longer listed by defaults domains.

On Developer Beta 5 com.apple.mail-shared is also not listed by defaults domains.
Attempting to write the preference via:
sudo defaults write $HOME/Library/Preferences/com.apple.mail-shared DisableURLLoading -bool true

Succeeds however the change is not detected by Mail.app even after quitting and reopening it.
Changing the setting via the Mail.app preferences UI alters  $HOME/Library/Preferences/com.apple.mail-shared.plist.
Unsure why Mail.app isn't detecting the new value when changed via defaults.

Per Howard Oakley:
Have you given Terminal ‘Full Disk Access’ in Privacy?
Works fine here using that setting.

Once done
defaults read com.apple.mail-shared

Works as expected.


Add layer opacity control to all types of layers

Add layer opacity control to all types of layers, especially Tiled Image layers.
Now this parameter exists in Layer interface, but it is used only for Graticule line color now.
Opacity implementation can be ported from WorldWindJS.

Fixed by #40

Technically opacity works, but it influence somehow next layers, which should not have opacity.
Please test if placemarks layer has pacity but then shapes layer has no opacity. It should draw opaque shapes.

Plus this opacity feature should be compatible with imageColor.alpha opacity control of each Placemark.

Fixed in 469794a7b1b207af78f44ab9f8ee3ce0f1dc90aa


Implement NetworkDeviceFunction

As oneview-redfish-user, I access "/redfish/v1/Chassis/<server_hardware_uuid>/NetworkAdapters/<deviceId>/NetworkDeviceFunction/<id>" and receive a NetworkDeviceFunction object associated with this adapter, one for each 3-tuple (physical_port, virtual_port, port_function). The ID should be the concatenation of each element id separated by "_". The NetworkDeviceFunction capabilities can be collected from OneView ServerHardwareType.

Added a "s" to NetworkDeviceFunction in the URL:
/redfish/v1/Chassis/<server_hardware_uuid>/NetworkAdapters//NetworkDeviceFunction/
now it is:
/redfish/v1/Chassis/<server_hardware_uuid>/NetworkAdapters//NetworkDeviceFunctions/


csrf filter: add support for additional source origins

Signed-off-by: Derek Schaller<EMAIL_ADDRESS>For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description: Add feature to CSRF filter to support whitelisting additional source origins.
Risk Level: Low
Testing: Included unit tests and sandbox changes (manually tested)
Docs Changes: Included
Release Notes: Included

/retest

/retest

Can someone rerun that macos azure build for me?

Thanks for reviewing @mattklein123 !


Updating grunt-karma dependency to latest version in order not to get…

When forked and tried to install the dependencies I got the followign error again and again:
➜  ng-password-strength git:(master) npm i
npm ERR! Darwin 14.4.0
npm ERR! argv "node" "/usr/local/bin/npm" "i"
npm ERR! node v0.10.36
npm ERR! npm  v2.7.0
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package karma does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/davidpelayo/Projects/ng-password-strength/npm-debug.log

By updating the grunt-karma dependency and karma from console, the error got fixed.

Already updated but not showing


Opening the forward baggage door and how the sound changes

Not sure if this is something you're able to do anything about or if it's more a MSFS thing but I've noticed how opening the forward baggage door with the engine running increases the sound from the engine inside the cockpit like you would have opened the cockpit door.

Yes, it's because open door. All opened doors will cause external sound to loud. I think it's not issue, but i dont know how it sound in real aircraft

Got it.
I've no experience with the real aircraft either but I doubt the engine sound will leak into the cockpit like in MSFS with the baggage door opened.


Please fix

Describe the bug
Please fix
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-ui2ufb3t
Steps to reproduce
Please fix problem
Expected behavior

Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 122
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 45154662,
  "usedJSHeapSize": 38308250,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}

Additional context
Error:
out-of-memory: RuntimeError: unreachable
    at wasm://wasm/a36bee7a:wasm-function[10]:0x1f9f
    at wasm://wasm/a36bee7a:wasm-function[7]:0x1e60
    at _0x43b5e9 (https://zp1v56uxy8rdx5ypatb0ockcb9tr6a-oci3.w-credentialless-staticblitz.com/filesystem-worker.fc837ba8.js:1:352094)
    at _0x5d803b (https://zp1v56uxy8rdx5ypatb0ockcb9tr6a-oci3.w-credentialless-staticblitz.com/filesystem-worker.fc837ba8.js:1:352762)
    at async _0x1104d3._initSlabAsync (https://zp1v56uxy8rdx5ypatb0ockcb9tr6a-oci3.w-credentialless-staticblitz.com/filesystem-worker.fc837ba8.js:1:355280)
    at async _0x1104d3.create (https://zp1v56uxy8rdx5ypatb0ockcb9tr6a-oci3.w-credentialless-staticblitz.com/filesystem-worker.fc837ba8.js:1:353217)
    at async _0x2d6cac.init (https://zp1v56uxy8rdx5ypatb0ockcb9tr6a-oci3.w-credentialless-staticblitz.com/filesystem-worker.fc837ba8.js:1:493966)

tl;dr: try loading bolt.new on a machine with more RAM or free up device memory
Not from the team at all but it looks like you are using bolt.new on a mobile phone.  The way bolt and stackblitz work (from my limited/outsider understanding) is that they rely on your machines memory to do much of anything.  If you are on a mobile phone, try working on a laptop or desktop instead.
Best of luck!


Add sample users to QuickStart

With a bit of luck this should be able to light up the mic new /users/ pages brought by lyft/amundsenfrontendlibrary#90
Still marked as WIP because it reverts #16 encode(utf-8) change (which I don’t understand?) - can that behavior be moved - maybe to a universal transform step? If so this PR could add that commit as well.

thanks @jornh , I think we could get rid of the encoding part. Our internal API returns unicode for user info instead of string which I use the encode to transform the data. But I think I could work around in the user extractor. Let me know once the pr is ready for review. Super excited for the pr to enrich our sample data.

Thanks @feng-tao that was the doubt I had.
I hope you like the theme I picked for CSV content! My aim is to get example data shown in the Amundsen introductory blog post 🙂

@jornh , that's great. I wonder whether with the sample user data, you are able to view the user profile page in Amundsen. cc @danwom as we are still actively working on Amundsen people/user.

In the latest Amundsenfrontend you can visit the route /user/[user_id] to view a profile page. The page is still a WIP as we need to implement bookmarks, owned resources, and frequently used resources as tabs on this page. We also need to implement searching user resources.

A screenshot I created a little while back using the PR #90 branch before it got merged:

URL<EMAIL_ADDRESS>

maybe we should mention on the example data we have in a place(or update the existing doc). But it could be a different pr. Thanks @jornh for the pr. This is awesome :)

I must admit I didn’t try it out end to end after frontend PR 90 got merged - I broke my container setup after they got pushed to DockerHub and mostly spent my Amundsen time the last few days on knowledge sharing.
Kudos to @danwom for the nice layout. Sorry for my schreenshot “leak” 😉

maybe we should mention on the example data we have in a place(or update the existing doc). But it could be a different pr.

Agree, it would be cool to have some kind of data flow illustration for each example source:

csv
which Databuilder pieces would be involved in reality (e.g)
Which pieces it lights up in the metadata model
API endpoints
Which UI components it lights up.
etc?

Not sure about the format - simplest would be a simple table. Something fancy could be overlaid on the architecture diagram.

Actually @ttannis build the profile page. I just merged in the feature branch. https://github.com/lyft/amundsenfrontendlibrary/pull/44

Hah, my bad, thanks @danwom for sharing a bit of history actually I think from before I met Amundsen ... waay back then
Yep there it is beautifully mocked up front and center in https://github.com/lyft/amundsenfrontendlibrary/pull/44

Guess, if I’m bored some rainy day I could go back and read up on PR history 😉

@jornh I don't expect anyone to have known this. Just wanted to give credit where it is due. 😄


Update SETUP.md

Updates to hi-light some other lines that are required.

Omitting the android-specific setup seems to resolve this issue: Issue when using react-native-reanimated with react-native-multithreading #3659


chore: [One-click binding] mongodb testcases cypress

Description
Added test cases to test one click binding for a MongoDB datasource.
PR fixes following issue(s)
Fixes #22993
Type of change

Chore (housekeeping or task changes that don't impact user perception)

Testing

How Has This Been Tested?

[x] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test sha=b75e5326415400c8900a420dd3f0ba3e920f0320


Create a Fantasy Book Cover Gallery

Pull Request Details:

Title: Create a Fantasy Book Cover Gallery
PR Link: #15
Issue: #14

Next Steps:
I'm ready for feedback and any necessary revisions. Please review at your earliest convenience, and feel free to provide comments or suggest improvements.
Thank you for your time and consideration!

Hi User,
Thank you for your pull request. I appreciate your contribution to our project.
I have reviewed your changes and everything looks good. Please be patient, and I'll get back to you as soon as possible.
If you have any questions or need further assistance, don't hesitate to ask.
Best regards,
Jayesh


docs(using-webhooks/server/README.md): typescript link added

PURPOSE
This aims to add the Typescript src link.

Thanks!

Thanks!


Login options - Netlify identity widget

This is awesome, but is limited to people with GitHub accounts. Could Netlify identity widget be used to authenticate so that more people could use the app?

This app is a wrapper for the GitHub Discussions API, so I'm not sure how having a third-party login would work

If a user doesn't want to log in or doesn't have a GitHub account, they can use the default anonymous bot to write comments.

@anurag629 anonymous commenting doesn't exist in this project https://github.com/giscus/giscus/issues/65


Applying ECA on 3D inputs?

Hi, I was wondering if this could be applied to models dealing with 3D inputs? Would the codes written below be correct? I'm not sure why the codes have squeezed the Width layer out. In 3D input, with X, Y and Z, which dimensions should be squeezed out? Should it be both X and Z? Would the codes below be correct?
 def forward(self, x):
        # x: input features with shape [b, c, h, w]
        b, c, z, h, w = x.size()

        # feature descriptor on the global spatial information
        y = self.avg_pool(x)

        # Two different branches of ECA module
        y = self.conv(y.squeeze(-1).squeeze(-2).transpose(-1, -2)).transpose(-1, -2).unsqueeze(-2).unsqueeze(-1)

        # Multi-scale information fusion
        y = self.sigmoid(y)

        return x * y.expand_as(x)

@shakjm  I meet the same problem， do you solve it？

@shakjm I meet the same problem， do you solve it？

Hello, I manage to run it with this set of codes that I've edited. It seems that the author doesn't monitor this page at all. I have tested this with my deep learning application, but my Squeeze & Excitation network still outperforms this method, no matter the slight changes I have done to it

@shakjm I meet the same problem， do you solve it？

Hello, I manage to run it with this set of codes that I've edited. It seems that the author doesn't monitor this page at all. I have tested this with my deep learning application, but my Squeeze & Excitation network still outperforms this method, no matter the slight changes I have done to it

I understand that BCHW, then compressed into BC11, then NC1, and then replaced with N1C for 1D convolution operation. Is the 3D input BCDHW also BC111, then NC1, and then replace it with N1C for 1D convolution operation?

@shakjm I meet the same problem， do you solve it？

Hello, I manage to run it with this set of codes that I've edited. It seems that the author doesn't monitor this page at all. I have tested this with my deep learning application, but my Squeeze & Excitation network still outperforms this method, no matter the slight changes I have done to it

I understand that BCHW, then compressed into BC11, then NC1, and then replaced with N1C for 1D convolution operation. Is the 3D input BCDHW also BC111, then NC1, and then replace it with N1C for 1D convolution operation?

@shakjm I meet the same problem， do you solve it？

Hello, I manage to run it with this set of codes that I've edited. It seems that the author doesn't monitor this page at all. I have tested this with my deep learning application, but my Squeeze & Excitation network still outperforms this method, no matter the slight changes I have done to it

I understand that B×C×H×W, then compressed into B×C×1×1, then N×C×1, and then replaced with N×1×C for 1D convolution operation. Is the 3D input B×C×D×H×W also B×C×1×1×1, then N×C×1, and then replace it with N×1×C for 1D convolution operation?

Yes, you are right, it will be BxCx1x1x1 . The whole operation should focus on the Channel dimension (that is why they did the swap). This is only based on my understanding. So what you have explained tallies with my understanding.
Also, you may refer to this closed topic for better you to understand it better
https://github.com/BangguWu/ECANet/issues/7

Yes, you are right, it will be BxCx1x1x1 . The whole operation should focus on the Channel dimension (that is why they did the swap). This is only based on my understanding. So what you have explained tallies with my understanding.
Also, you may refer to this closed topic for better you to understand it better
#7

So do experiments based on this idea have any effect, or is it not as effective as SE Net?

Yes, you are right, it will be BxCx1x1x1 . The whole operation should focus on the Channel dimension (that is why they did the swap). This is only based on my understanding. So what you have explained tallies with my understanding.
Also, you may refer to this closed topic for better you to understand it better
#7

So do experiments based on this idea have any effect, or is it not as effective as SE Net?

My experiments uses 10-fold cross validation, and I've only tried it for one folder. My experiment uses only a small block of SE Net, and ECA performs very closely to my modified SE block. It performed -0.1% sensitivity as compared to SE block. So this introduced idea did not help my work.. You have to try it with your application to see if it helps.

Yes, you are right, it will be BxCx1x1x1 . The whole operation should focus on the Channel dimension (that is why they did the swap). This is only based on my understanding. So what you have explained tallies with my understanding.
Also, you may refer to this closed topic for better you to understand it better
#7

So do experiments based on this idea have any effect, or is it not as effective as SE Net?

My experiments uses 10-fold cross validation, and I've only tried it for one folder. My experiment uses only a small block of SE Net, and ECA performs very closely to my modified SE block. It performed -0.1% sensitivity as compared to SE block. So this introduced idea did not help my work.. You have to try it with your application to see if it helps.

ok，thanks！

My code:
y = self.conv(y.squeeze(-1).squeeze(-1).transpose(-1, -2)).transpose(-1, -2).unsqueeze(-1).unsqueeze(-1)
Is it differ from yours?

Here is the implementation I am using for 3D input, kindly correct me if I am wrong:
from torch import nn
import math

class ECABlock(nn.Module):
    """
    ECA-Net: Efficient Channel Attention for Deep Convolutional Neural Networks
    https://doi.org/10.48550/arXiv.1910.03151
    https://github.com/BangguWu/ECANet
    """

    def __init__(self, n_channels, k_size=3, gamma=2, b=1):
        super(ECABlock, self).__init__()
        self.global_avg_pool = nn.AdaptiveAvgPool3d(1)

	# https://github.com/BangguWu/ECANet/issues/243
	# dynamically computing the k_size
        t = int(abs((math.log(n_channels, 2) + b) / gamma))
        k_size = t if t % 2 else t + 1

        self.conv = nn.Conv1d(1, 1, kernel_size=k_size, padding=(k_size - 1) // 2, bias=False)
        self.sigmoid = nn.Sigmoid()

    def forward(self, x):
        b, c, _, _, _ = x.size()
        # feature descriptor on the global spatial information
        y = self.global_avg_pool(x)

        # Two different branches of ECA module
	# https://github.com/BangguWu/ECANet/issues/30
	# https://github.com/BangguWu/ECANet/issues/7
        # y = self.conv(y.squeeze(-1).squeeze(-2).transpose(-1, -2)).transpose(-1, -2).unsqueeze(-2).unsqueeze(-1) # b, c, z, h, w = x.size()
        y = self.conv(y.squeeze(-1).squeeze(-2).transpose(-2, -1)).transpose(-2, -1).unsqueeze(-2).unsqueeze(-1) # b, c, w, h, z = x.size()

        # Multi-scale information fusion
        y = self.sigmoid(y)

        return x * y.expand_as(x)


test 15543

Codecov Report

Merging #389 (1c5e1a2) into master (7a8c129) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #389   +/-   ##
=======================================
  Coverage   72.53%   72.53%
=======================================
  Files          11       11
  Lines         579      579
=======================================
  Hits          420      420
  Misses        134      134
  Partials       25       25

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 7a8c129...1c5e1a2. Read the comment docs.


Add my duck

Description
Here my contribution to "The Duck Gallery".

You must respect the following conditions

Your contribution must respect the code of conduct
It's your first PR to this repository
You have added your image of the duck downloaded from https://pimpmyduck.zenika.com
You have not changed the image of the duck
The image filename must be your GitHub username (ex: your-username.png)
You are using your own GitHub user and it's the same as the PR author
Into the contributors.js file, the message must be short and respect the code of conduct

If the PR doesn't respect those conditions, it will be closed

Thanks for your PR @CaioSouzalimaa !
We will reset this project in October for the Hacktoberfest. We will merge this PR in october 😄

Thank's for your PR @CaioSouzalimaa  🙏
FYI I created this PR https://github.com/zenika-open-source/the-duck-gallery/pull/287 to fix the name and the directory.
Have a great Hacktoberfest 🎃


Exception on clear with optionvaluePath

Uncaught Error: Assertion Failed: Cannot call get with 'id' on an undefined object.

could be fixed with changing
value = get(data, optionValuePath);
to
value = data ? get(data, optionValuePath) : undefined;
on line 464
i have no clue how to contribute and get it released as a new version of the plugin so I just leave you the hint

just saw this issue is a duplicate of #130, which already has a pull request


ci: skip build if Bicep file unchanged

Bicep file was built in #16 even though no changes were made to the Bicep file 🤷 This PR should fix that.


Refactor Orders service to use messaging

Order service implementation is quite naive at the moment, as it makes blocking calls to Payment and Shipping services, which is not how a real-world Order Processing service would work.
We should capture the Order as quickly as possible, and use messaging to move Order through various states (CREATED, PAID, SHIPPED) instead.

The problem is that the only backend that has messaging support at the moment is Redis, and we don't have messaging support in Helidon yet, so maybe this should wait until the latter is available.


fetch with URL object fails with Cannot read properties of undefined (reading 'has')

We are using fetch passing a URL object as resource parameter - and a second options argument containing headers. The first parameter may be any object with a stringifier.^1
However, currently it implies here^2 that any object passed as first argument to fetch must be a Request.
TypeError: Cannot read properties of undefined (reading 'has')\n    at o9.fetch (/node_modules/.pnpm/aws-xray-sdk-fetch@3.6.0_aws-xray-sdk-core@3.6.0/node_modules/aws-xray-sdk-fetch/lib/fetch_p.js:71:25)\n    at o9.getData (/libs/instruments/service-cityfalcon/src/lib/cityfalcon.service.ts:179:12)\n    at params (/libs/instruments/service-cityfalcon/src/lib/cityfalcon.service.ts:60:14)\n    at Array.map (<anonymous>)\n    at o9.getMarketNewsTimeline (/libs/instruments/service-cityfalcon/src/lib/cityfalcon.service.ts:59:18)\n    at mWe (/libs/instruments/cloud/src/lib/market-news/market-news.get-market-news.fn/index.ts:103:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at gfe (/node_modules/.pnpm/@middy+core@4.7.0/node_modules/@middy/core/index.js:120:32)

Im having the same issue here, was using a URL object as first parameter for fetch, and encounter the same error. Not every time the first parameter is a object, it will be a Request. For now i updated my code to send the URL.href string as resource, but should be fixed


Prefetch job input data

Discussed offline with @msteffen and @JoeyZwicker .
Currently, jobs read data lazily.  That is, a file is not actually downloaded to the machine on which the job runs, until the job attempts to read that file.  This makes sense because given a job and a set of input files, we don't actually know which subset of the input files the job will actually need to read over the course of its execution.  For instance, if we have a 1TB dataset and the job only needs to read one file, it'd be really dumb to download the entire dataset to the machine.
On the other hand, there is a large class of jobs that do need to read all or most of its input data, so it might make sense for there to be a way to prefetch these data before the job actually reads them.  To see the benefit of prefetching input data, consider this execution pattern:

Read (download) a small file.
Do a long computation.
Read (download) a huge file.
Do another computation.

If we don't prefetch input data, then the total execution time will be the sum of all these individual steps.  If we do prefetch input data, however, step 2 and 3 can be done in parallel (i.e. we'd be downloading the huge file when the long computation is running), therefore reducing the total execution time of this job.
The most obvious way to expose this functionality would be to have a prefetch flag in the pipeline spec.  So if you know that your pipeline will need to read all or most of the input data, then you might want to set the prefetch flag to true to enable the optimization.

Definitely like this idea. Here's how I'd imagine implementing this.
Step 1, add a cache to our fuse implementation. It should be able to cache actual files (the results of GetFile) and also the results of meta queries (ListFile et al). The latter is probably much more important since reading a file normally requires several meta ops followed by a single GetFile.
Step 2, make it so that the fuse layer proactively tries to fill the cache using whatever information it has handy to try to fill it with things the user is likely to request next. A couple of thoughts on this algorithm.

I'd prefer not to have a prefetch flag if we can avoid it but instead make this happen transparently for users. I'm worried about having too many performance nobs for users to turn making it too confusing. In this case I think an oblivious algorithm should work really well if it follows the simple rule that as long as the job is still running, the cache isn't and there's data the job could read that isn't cached it should attempt to read whatever data it thinks the job is likely to need in the future. If the job winds up finishing without needing that data then we wasted some bandwidth and memory which seems fine.

Likely this algorithm should start by requesting all of the meta ops, listing out all the files in the commits the job is processing since those add a lot of round trips. Actually it would be even better if we could start computing this information in CreateJob and have it ready for the worker pods once they come online.

Another thought on this.  If we ever decide to prefetch all input data for a given job, then we don't even need FUSE anymore.  /pfs can just be a normal file system.  We can skip a lot of overhead/bugs that way.

Jobs now download, process and upload data concurrently. Some of the details in this issue have changed but as much as is makes sense in the current system, this is implemented.


DEV: run copier update to fix pypi publishing

Description

Result of running copier
Motivation and Context

Primary goal is to fix pypi publishing.
How Has This Been Tested?

Squashed this to two commits (we don't need my random walk to fixing everything!) but could go to 1 if we want.

The decrease in the coverage is the tests of persistent dict.
I do not think it is worth adding a test run that pins zict back, but could be convinced otherwise.


Add mention kinds & selectors to OpenCtx provider protocol

This PR modifies the MetaResult to the following:

mentions.kind is the list of types of mention items the provider can return. For example github pr, issues, code search results.
mentions.selectors is the list of regex patterns, which if matches with the mention text would mean that the provider can return items for that. We will use it to get context items from all the supported providers for when the user pasts in a URL after @.
Whey we do not have features.mentions: boolean | {} ? because then you can not do meta?.features?.mentions?.selector. We will always have to check of the mentions type first.
Accordingly the meta.selector is moved to meta.features.annotations.selectors.

export interface MetaResult {
    /**
     * The name of the provider.
     */
    name: string
    /**
     * The features supported by the provider.
     */
    features?: {
        /**
         * Configuration for the mentions feature.
         */
        mentions?: {
            /**
             * Whether the provider implements the mentions feature
             */
            implements?: boolean
            /**
             * A list of patterns matching the mention text for which the provider can return mentions
             */
            selectors?: MentionSelector[]
            /**
             * A list of kinds of  mentions the provider supports.
             */
            kinds?: MentionKind[]
        }
        /**
         * Configuration for the annotations feature.
         */
        annotations?: {
            /**
             * Whether the provider implements the mentions feature
             */
            implements?: boolean
            /**
             * A list of patterns matching the mention text for which the provider can return mentions
             */
            selectors?: AnnotationSelector[]
        }
    }
}

High level comments, just looked at PR description

implements seems duplicative. Can't we just check if the mentions field is present?
Does the feature nesting provide any value? Why not just have a high level mentions and annotations field on meta. This is just a taste perspective on "unnecessary nesting"
The description of selector seems a bit vague. Additionally regexp isn't a universal thing, but there are many different flavours. Given we want HTTP support, maybe mention the regex is a javascript regex?
Given we are creating behaviour changes based on the current message, it feels like message should be an optional part of MentionParams.
Can't we just always call mentions, what is a concrete example where its useful to do this via a selector vs the mention function call itself deciding if it should provide mentions (assuming we now pass in message)

@sqs @keegancsmith Update:

Removed the mentions.kinds altogether, @eseliger and I are exploring an idea of rather multiplexing at the provider level, which means just returning multiple providers for a single package for different things. It makes sense and we will discuss it separately. So this PR only implements mentions.selectors now.
@keegancsmith I have removed meta.features nesting.
@sqs I have removed implements.
@keegancsmith @sqs I have updated the description for the mention selectors. Please provides ideas if wish to improve it further and we can always address is separately.
@keegancsmith we can not always call mentions on all the providers. This is being done to bypass provider selection. For example a user writes @https://github.com/sourcegraph/cody/pull/123, the Github & Repositories provider can say yes, we recognise it (based on a cheap client side regex match without calling provider as we have meta info beforehand), and then we can make mentions call to only those 2 providers and list the mentions, without the user having to select a provider at all. Also the same reason why we have selectors for annotations.

@thenamankumar do you have a PR yet for cody? This is a backwards incompatible change, so for example against current versions of cody my in development providers do not show up (since they no longer set features.mentions)


Clarify some wasm terms in the introduction

This PR aims to make the documentation more readable for people who are not very familiar with WebAssembly.
Closes https://github.com/bytecodealliance/wasmtime/issues/8101.
Thanks to @abrown for the clarification. That was indeed the piece of information that I was missing.

(Going to just commit my suggestions and enqueue this to merge)


Add support for Bandcamp player

https://play.google.com/store/apps/details?id=com.bandcamp.android

My bad, found old thread, I'm new to git, sorry! Can't even find where to delete this... lol embarassing


Collab Cafe - 01/08

Summary
Actions for Collab Cafe on 1st August
Source
No response
Detail
Actions for Collab Cafe on 1st August
Intended Output

[x] Decide the cafe topic - Principles and implications
[x] Prepare cafe logistics
[ ] Open key issues on the repo as a result of the Collaboration Cafe
[ ] Write up a blog post summarising the Collab Cafe
[ ] Add all attendees (who want to be) as contributors for ideas to the specification

Who can help
No response

@katie-rds is going to open issues for the Public trust principle!


newmockresponses.go

with new kafka version V0_10_0_0 if you are using sarama-cluster and want to mock the consumer. there are no mock responses which are mandatory. those are added now.

will fix the tests and reopen again.


Proper db migration process

After pulling latest and running the data import, encountered several missing db artifacts.
File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 86, in _execute
    return self.cursor.execute(sql, params)
psycopg2.errors.UndefinedTable: relation "vulnerabilities_vulnerabilityseverity" does not exist
LINE 1: ...lities_vulnerabilityseverity"."reference_id" FROM "vulnerabi...
                                                             ^

On start the db initialization is run only if the db does not exist.
PostgreSQL Database directory appears to contain a database; Skipping initialization
But should also account for updates on an existing db, similar to Liquibase or Flyway (Java).

Could you try deleting the images and pulling again ? The problem is caused because the migrations have not been ran since a schema change

Ok that solves it.
Would it be possible if this can be done without deleting then re-creating the images?

Would it be possible if this can be done without deleting then re-creating the images?

yes
you could do the following in the project dir
sudo docker-compose up
sudo docker-compose exec web bash
python manage.py makemigrations vulnerabilities
python manage.py migrate

Would it be possible if this can be done without deleting then re-creating the images?

yes
you could do the following in the project dir
sudo docker-compose up
sudo docker-compose exec web bash
python manage.py makemigrations vulnerabilities
python manage.py migrate

Thanks.
But previously I also deleted then re-created images, could this be avoided at all?
https://github.com/nexB/vulnerablecode/issues/312

@chess-equality  yes, these both issues are caused  because the docker images and the code are out of sync.
When you pull latest, your code is latest. But the deps and schema remain same as that of intial image creation.

I would also suggest that proper migrations be included in the repo, if possible.  I realize this project is a free gift to the open source community, but it makes it difficult to keep up to date with your code having to re-scrape everything without a migration process (which is fairly easily created with Django).

@DjDeepDive

thank you for the kind words!

yes, we need stable migrations alright! I guess the schema is still evolving fast but that's not a reason. Django has superb migration support.

@sbs2001 ping me on Gitter when you come online tomorrow so we can sync, I think you made the migration in your latest PR an initial migration?

@DjDeepDive with that said, if you can chip in to help too that would be mucho welcomed!

@DjDeepDive with that said, if you can chip in to help too that would be mucho welcomed!

Gladly.  What needs done?

Migrations are not included (mainly because there would be tons of them and schema is evolving), hence causing this problem.  As a short term fix on these, a fake migration via
python manage.py migrate --fake vulnerabilities zero
python manage.py migrate

would do the trick. But ofcourse this is a hack.
A proper solution would be to include all migrations in the repo

@sbs2001 IMHO we should start including them, even with fast schema updates, they should work well enough. @tdruez what's your advice there?

@sbs2001 Migrations are not included (mainly because there would be tons of them and schema is evolving)

I don't think it's a valid argument to not include migrations along code changes. Django provides ways to squash migrations when needed: https://docs.djangoproject.com/en/3.1/topics/migrations/#migration-squashing
As a side note, make sure to consolidate all the migrations of a branch into one file before merging a PR.

@tdruez Thanks for the insights!

@tdruez  thanks for the link. We will start with real "squashed migrations" hence forth rather than creating one fresh ;)
Closing this I will take better care of migrations next time ;)


Modify github actions workflow to trigger on both push and pull

Will ensure that code coverage computation by Coveralls happens both when a PR is opened and when it is merged (so that the main branch coverage is always up to date).
With this change, the workflow_dispatch event trigger can probably be dropped.

I'd like us to have the best of both worlds:

Avoid running the workflow twice during PRs, see #42
main branch coverage is updated when a PR is merged

Since every merged PR to main results in a push we could modify the workflow to
on:
  push:
    branches:
      - main
  pull_request:
  workflow_dispatch:


Bug: Formula input - biconditional

The biconditional (%) of the new formula input (I) window is broken. It's a bit more complicated than all the other operators. Other operators work great with the stack data structure - just pop, set, and add. Biconditionals unfortunately have a required symmetry in their existential graph conversion: P ↔ Q becomes:
┌─────────┐
│   ┌───┐ │
│ P │ Q │ │
│   └───┘ │
└─────────┘
┌─────────┐
│   ┌───┐ │
│ Q │ P │ │
│   └───┘ │
└─────────┘

which doesn't really translate well when the stack input ↔ P Q pops the desired key and sets it immediately, making the TreeNodes that it needs to fill, and filling them as soon as those nodes are popped from their own todo stack.
Biconditionals need to make multiple copies of the graphs, just with the inputs swapped. With a longer and more complicated equation like: (P ∧ (Q ∨ R)) ↔ ¬(S ∧ T), this issue becomes far more pronounced. We no longer have to copy just P and Q as above, but entire operator chains. This simply doesn't work with the stack data structure, but I'm hesitant to make a work around that gets rid of the stack simply because it's so good, relatively clean, and simple to implement for the other "normal" operators.
The current implementation maintains two parallel stacks, one for the actual polish notation input, and one for the created existential graph nodes. They get popped and set in unison, and when the formula is well-formed, both stacks are empty and the existential graph is fully and correctly built. Workarounds for the biconditional would either need to add a lot of excess case checking for biconditionals and lots of extra logic for copying the graph but switching places, or do away with the stack altogether, and only build the existential graph at the very end instead of as it is inputted.
The second option is probably the most viable, but it would involve parsing the polish notation (↔ ∧ P ∨ Q R ¬ ∧ S T in the above example) tree a second time, and would still require lots of additional branching to duplicate the biconditional halves. If we kept the stack, we'd probably have a stack of QList<TreeNode*>, where normal operators QLists' would have only one element as usual, but the biconditional would update every item in the list. It'd be doable but quite the headache.
Any solution that I can think of at the moment would be far too messy and difficult to maintain if necessary. I only see a single good option at the moment; disable the keybind for the biconditional operator and set it as a future goal to implement later.

I thought about it more and figured the stack of QLists would be the way to go. I let it just simmer for a bit and just out of the blue figured out a semi-okay way to do it. I've implemented it in https://github.com/casey-c/egg/commit/a7ad0fd1c761a4a1cf7277acdc6c3d9898dfa649 .I think it's okay, but I'm not positive that it works 100%. I also hope I didn't break any of the other operators, but I think they're okay as far as I can tell.
 I'm know for sure there's a lot of room for cleanup (this is one of the worst commits ever in this project, IMO), but I'm too tired to figure it out right now. I'm going to try and do some cleanup and hopefully stumble upon a better solution that doesn't involve code duplication (root nodes and non root nodes are handled the same way but slightly differently...) and hopefully am able to come up with some compact, reusable functions for the operators, since they all kind of do the same thing.
If I can get rid of the root's dupe code and see if I can shrink the if-else chain to be a bit more readable, I'd be happy. I'll try and get to this when I document this branch.


Unnecessary memory allocation

PHP_METHOD(Test_SPropertyAccess, __construct) {

	zval *_0, _1, _2, *_3, *_4 = NULL;

	ZEPHIR_MM_GROW();

	ZEPHIR_INIT_ZVAL_NREF(_0);
	ZEPHIR_INIT_VAR(_0);
	ZVAL_STRING(_0, "abc", 1);

Both ZEPHIR_INIT_ZVAL_NREF and ZEPHIR_INIT_VAR allocate memory via ALLOC_ZVAL; memory allocated by ZEPHIR_INIT_ZVAL_NREF is leaked.

 I'd like to add support for anything/everything at some point, but keeping the issue open doesn't help that. :) If anyone wants to get started, I'd love that.


[20.09] libqb: 0.17.2 -> 2.0.2

Motivation for this change
Fixes CVE-2019-12779.
(cherry picked from commit 68889745cb52f4854adb87140489191f14848b7a)
Things done

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

[ ] NixOS
[ ] macOS
[x] 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"
[x] 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.

this is probably an API/ABI-breaking update (0.17.2 -> 2.0.2).

The changelog of libqb is not really clear about that. It does not look like the project does semver.
There is no BC explicitly listed in the changelogs of the major versions:
https://github.com/ClusterLabs/libqb/releases/tag/v1.0rc1
https://github.com/ClusterLabs/libqb/releases/tag/v2.0.0

I don't see any maintainers. The version number could also be tracking abi, which is fine in nixpkgs, since everything is built from source. The security severity is only "moderate", but I would rather have a potential breakage than a vulnerability.


[stable/kong] servicemonitor.yaml: error converting YAML to JSON #19956

Which issue this PR fixes
Fixes [stable/kong] #19956
Special notes for your reviewer:
Attempting to deploy resulted in "kong/templates/servicemonitor.yaml: error converting YAML to JSON: yaml: line 10: did not find expected key"
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @hbagdi

@jlentzfl:

Please add DCO to your commit.
Add a changelog entry in the README.md file.

@hbagdi Done

/test pull-charts-e2e


Error

Hello,
I have developed an application using the framework, everything works fine except when I access the web page througth the Citrix Secure Web browser from an IOS device.
The problem is when calling for example
Q.serviceRequest(..., ..., ...);
sometimes specially if i use 3G I got and error popup

saying only "undefined".
Is there a way to ask Serenity when is ready to process the service requests?
Any help will be appreciated
Thanks.

Unfortunately XHR (ajax) requests doesn't give any error text when a connection error like CONNECTION_REFUSED or CONNECTION_RESET occurs. That's why you see "undefined" as there is no message to show. This is a limitation with XHR itself. I tried to give a more descriptive message in latest commit, but it will always be limited.


Select mic using prepareAudio

I'm trying to select mic using prepareAudio but the only result that happens is a sped up sounding voice on playback. I'm using AudioDeviceInfo to get the device id of the microphone and passing that value to the prepareAudio method. Is this not the correct usage? If not, how do I select a different microphone?

Hello,
If you means parameter "int audioSource".
This parameter support this values:
https://developer.android.com/reference/android/media/MediaRecorder.AudioSource
In most of cases using MediaRecorder.AudioSource.MIC or MediaRecorder.AudioSource.VOICE_COMMUNICATION is enough but if you are using bluetooth microphone enable it using SCO could be necessary:
https://developer.android.com/reference/android/media/AudioManager


Feature/store constructor

closes #39

Codecov Report

Merging #45 into master will increase coverage by -0.01%.

@@            Coverage Diff             @@
##           master      #45      +/-   ##
==========================================
- Coverage   98.18%   98.18%   -0.01%
==========================================
  Files          10       10
  Lines         497      551      +54
==========================================
+ Hits          488      541      +53
- Misses          9       10       +1

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 bd969a5...447cd7d. Read the comment docs.


[All Hosts] (requirement sets) add and correct info for perpetual lic…

…ense Office on Mac
Fixes 3085

Docs Build status updates of commit f9ad55f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/overview/office-add-in-availability.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/add-in-commands-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/custom-functions-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/dialog-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/dialog-origin-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/identity-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/keyboard-shortcuts-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/open-browser-window-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/ribbon-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/shared-runtime-requirement-sets.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit cd8abf1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/overview/office-add-in-availability.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/add-in-commands-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/custom-functions-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/dialog-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/dialog-origin-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/identity-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/keyboard-shortcuts-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/open-browser-window-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/ribbon-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/shared-runtime-requirement-sets.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 579d240:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/overview/office-add-in-availability.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/add-in-commands-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/custom-functions-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/dialog-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/dialog-origin-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/identity-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/keyboard-shortcuts-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/open-browser-window-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/ribbon-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/shared-runtime-requirement-sets.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit e10fed6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/overview/office-add-in-availability.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/add-in-commands-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/custom-functions-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/dialog-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/dialog-origin-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/identity-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/keyboard-shortcuts-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/open-browser-window-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/ribbon-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/shared-runtime-requirement-sets.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


FSLeyes plugin: Remove green cross once plugin has been loaded

The green cross below is not relevant (only 2d view) and should be removed:

I'll take a look at this when possible. FSLeyes just made a new release and the developer documentation is currently blank.

Changes made with commit 7b6c4df


Validate tiles referenced

For #35
@lilleyse Let me know if you think this is a reasonable way to go about it. Thanks!

@lilleyse Added support to handle multiple promises, could you tell me if this way is what you were hinting at?

@lilleyse Added the readTile promise to the list of promises. Let me know if everything is good to go.

You can remove the tilePromises.push(resolve({ areas.
I may have more comments later - can you added tests and if possible remove the commits from https://github.com/AnalyticalGraphicsInc/3d-tiles-tools/pull/29? If that's not easily doable we should merge https://github.com/AnalyticalGraphicsInc/3d-tiles-tools/pull/29 first.

@lilleyse I think it might be a better idea to merge #29 first... I'll try to finish that up

@lilleyse The test seems to result in an async exception... not sure how to fix this: any ideas would be appreciated!

I think the source of the problems is that the example tileset in validateTilesetSpec references non-existent content like b.b3dm, c.b3dm, etc. Eventually we'll need to check if a tileset references non-existent tiles, but for now I would just remove those contents.

@lilleyse I got rid of the non-existent content, but I believe the issue now is that the file isn't being read into a tileset in vaildateTileset

Ah ok. In the test before calling validateTileset you will need to call readTileset.

@lilleyse Updated the test, but for the issue now is files such as parent.b3dm and ll.b3dm are in the directory /specs/data/TilesetGzipped along with tileset.json but readTile tries to look for them in the same directory. Should I also pass in the directory of the tileset as a param?

Should I also pass in the directory of the tileset as a param?

Yeah that sounds like a good idea.

@lilleyse I added the path as an argument, and the test passes but I end up with the following error:
Unhandled rejection TypeError: Cannot read property 'addExpectationResult' of undefined     at Env.fail (/Users/sumitshyamsukha/Desktop/3d-tiles-tools/validator/node_modules/jasmine-core/lib/jasmine-core/jasmine.js:987:24)     at Function.next.fail (/Users/sumitshyamsukha/Desktop/3d-tiles-tools/validator/node_modules/jasmine-core/lib/jasmine-core/jasmine.js:1903:19)     at /Users/sumitshyamsukha/Desktop/3d-tiles-tools/validator/specs/matchers/expectPromise.js:14:26     at tryCatcher (/Users/sumitshyamsukha/Desktop/3d-tiles-tools/validator/node_modules/bluebird/js/release/util.js:16:23)     at Promise._settlePromiseFromHandler (/Users/sumitshyamsukha/Desktop/3d-tiles-tools/validator/node_modules/bluebird/js/release/promise.js:504:31)     at Promise._settlePromise (/Users/sumitshyamsukha/Desktop/3d-tiles-tools/validator/node_modules/bluebird/js/release/promise.js:561:18)     at Promise._settlePromise0 (/Users/sumitshyamsukha/Desktop/3d-tiles-tools/validator/node_modules/bluebird/js/release/promise.js:606:10)     at Promise._settlePromises (/Users/sumitshyamsukha/Desktop/3d-tiles-tools/validator/node_modules/bluebird/js/release/promise.js:681:18)     at Async._drainQueue (/Users/sumitshyamsukha/Desktop/3d-tiles-tools/validator/node_modules/bluebird/js/release/async.js:138:16)     at Async._drainQueues (/Users/sumitshyamsukha/Desktop/3d-tiles-tools/validator/node_modules/bluebird/js/release/async.js:148:10)     at Immediate.Async.drainQueues [as _onImmediate] (/Users/sumitshyamsukha/Desktop/3d-tiles-tools/validator/node_modules/bluebird/js/release/async.js:17:14)     at processImmediate [as _immediateCallback] (timers.js:383:17)

@lilleyse can you help move this forward?

Sorry for the delay @sumitshyamsukha.
In order to fix the error validateTileset will also need to accept that second parameter (maybe called tilesetDirectory, and then tileContent.url will need to become path.join(tilesetDirectory, tileContent.url).

@lilleyse The error seems to still come up even after changing that param. Could it be something with the tests?

@lilleyse is this ready?

Did some small cleanup - may require a bit more work but its good to merge into the validator-master branch.
Thanks @sumitshyamsukha!


Finish rename to Trino

Finish rename to Trino, notably use X-Trino in HTTP headers.

@losipiuk can you create a (any) version tag after merging this?

@losipiuk can you create a (any) version tag after merging this?

@losipiuk can you create a (any) version tag after merging this?

I tagged as 0.300.0. We can start versioning from this. cc: @findepi

@losipiuk can you create a (any) version tag after merging this?

I tagged as 0.300.0. We can start versioning from this. cc: @findepi


Add autodidax to dev docs toctree and ignore md file to silence warning.

Fixes CI failure from google/jax#5827.

Thanks, Tom!


Downgrade to Xcode 11.3 for MacOS travis

Thanks for the pull request @baothientran!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium for Unreal Samples works.

Thanks @baothientran!


Error: react-native-fast-tflite is not yet supported on Android! I couldn't manage to get TFLite to build for NDK/C++

Hi @mrousavy , I am using expo-49 on android and getting this error

Yep, as you can read in the title, RN Fast TFLite is not supported on Android yet.
See this section in the README:

i’ve linked tflite with my shared lib in a personal project a few months ago, tomorrow i’ll try to find it and share that part

i was able to get it working on android by just adding some  missing headers and removing those lines from the async thread, didn't have time yet to debug this yet, just pasting in case it's obvious for someone at first glance
Buffer buffer = fetchURL(modelPath);
auto model = TfLiteModelCreate(buffer.data, buffer.size);

Awesome!! How did you include it in CMake?

didn't changed anything on cmake just removed the comments you implemented previously

i've created this small script to build it and copy the headers,
#!/bin/bash

# Variables
output_dir="output"

cd tensorflow || exit 1

rm -rf tmp output
mkdir -p tmp/include
mkdir -p "$output_dir/include"
mkdir -p "$output_dir/lib"

abis="android_arm64=arm64-v8a android_arm=armeabi-v7a android_x86_64=x86_64"

for abi in $abis; do
  rm -rf bazel-bin bazel-out
  IFS="=" read -r key value <<< "$abi"
  output_subdir="$value"

  bazel build \
          -c opt \
          --config="$key" \
          //tensorflow/lite/c:tensorflowlite_c

  mkdir -p "$output_dir/lib/$output_subdir"
  cp bazel-bin/tensorflow/lite/c/libtensorflowlite_c.so "$output_dir/lib/$output_subdir/" || exit 1
done

# include tensorflow headers
rsync -avm --include='*.h' -f 'hide,! */' tensorflow tmp/include

cp -r tmp/include "$output_dir/"

i've facing issues in previous projects while building tflite on mac, even if it compiles successfully with symbols in place, so just to make sure i created this docker file also
# Using the latest Ubuntu LTS arm64 image
FROM amd64/ubuntu:22.04

# Define bazel version
ARG BAZEL_VERSION=5.3.0

ENV ANDROID_DEV_HOME /android
RUN mkdir -p ${ANDROID_DEV_HOME}

ENV ANDROID_SDK_FILENAME commandlinetools-linux-9645777_latest.zip
ENV ANDROID_SDK_URL https://dl.google.com/android/repository/${ANDROID_SDK_FILENAME}

ENV ANDROID_API_LEVEL 30
# min API level supported by NDK
ENV ANDROID_NDK_API_LEVEL 23
ENV ANDROID_BUILD_TOOLS_VERSION 30.0.3
ENV ANDROID_SDK_HOME ${ANDROID_DEV_HOME}/sdk
RUN mkdir -p ${ANDROID_SDK_HOME}/cmdline-tools
ENV PATH ${PATH}:${ANDROID_SDK_HOME}/cmdline-tools/latest/bin:${ANDROID_SDK_HOME}/platform-tools
ENV ANDROID_NDK_FILENAME android-ndk-r21e-linux-x86_64.zip
ENV ANDROID_NDK_URL https://dl.google.com/android/repository/${ANDROID_NDK_FILENAME}
ENV ANDROID_NDK_HOME ${ANDROID_DEV_HOME}/ndk
ENV TOOLCHAIN=${ANDROID_NDK_HOME}/toolchains/llvm/prebuilt/linux-x86_64

ENV PATH ${PATH}:${ANDROID_NDK_HOME}:${TOOLCHAIN}/bin

ARG UID=1000

RUN apt-get update -y

RUN apt-get install -y sudo \
      git \
      g++ \
      gdb \
      clang \
      curl \
      python3-numpy \
      gnupg \
      apt-transport-https \
      openjdk-11-jdk \
      make \
      ninja-build \
      cmake \
      autoconf \
      automake \
      libtool \
      locales-all \
      dos2unix \
      rsync \
      tar \
      unzip \
  && apt-get clean

RUN cd ${ANDROID_DEV_HOME} && \
    curl --progress-bar -L -O ${ANDROID_SDK_URL} && \
    unzip ${ANDROID_SDK_FILENAME} -d /tmp && \
    mv /tmp/cmdline-tools ${ANDROID_SDK_HOME}/cmdline-tools/latest && \
    rm ${ANDROID_SDK_FILENAME}

RUN cd ${ANDROID_DEV_HOME} && \
    curl --progress-bar -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:90.0) Gecko/20100101 Firefox/90.0" -O ${ANDROID_NDK_URL} && \
    unzip ${ANDROID_NDK_FILENAME} -d ${ANDROID_DEV_HOME} && \
    rm ${ANDROID_NDK_FILENAME} && \
    bash -c "ln -s ${ANDROID_DEV_HOME}/android-ndk-* ${ANDROID_NDK_HOME}"

# make android ndk executable to all users.
RUN chmod -R go=u ${ANDROID_DEV_HOME}

# add build user to sudoers
RUN echo "builder ALL=(ALL) NOPASSWD:ALL" > /etc/sudoers.d/builder

# download and install Bazel
RUN curl -fL --progress-bar -O https://github.com/bazelbuild/bazel/releases/download/${BAZEL_VERSION}/bazel-${BAZEL_VERSION}-installer-linux-x86_64.sh && \
chmod +x bazel-${BAZEL_VERSION}-installer-linux-x86_64.sh

RUN ./bazel-${BAZEL_VERSION}-installer-linux-x86_64.sh && \
rm -f bazel-${BAZEL_VERSION}-installer-linux-x86_64.sh;

# Set the locale
ENV LANG en_US.UTF-8
ENV LANGUAGE en_US:en
ENV LC_ALL en_US.UTF-8

# create a new user using the provided user id
RUN useradd -m -u ${UID} -s /bin/bash builder

# switch to the new user
USER builder

CMD ["/bin/bash"]

and then
# build it
docker build . -t builder -f build.DockerFile

# execute on current project dir
docker run -it -v $PWD:/host_dir builder

# build from inside docker
cd host_dir && ./build_tflite.sh

Hi @rodgomesc , I am also facing the same error while testing this in Android, can you please explain the step-wise solution for script and docker? and how exactly you have used the script for error solving. i am not getting above solution.

anyone figure this out yet?

I really hope you guys could fix this! This would be a great addition

You can take a look rodgomesc test -> https://github.com/rodgomesc/react-native-fast-tflite
I'm also trying to figure this one out, because this implementation seems very promising compared to other RN tflite implementations.

Does this works for Android ?? I looked at the read me. I think it's the same configaration.

Im still testing it but the was working on the build -> https://github.com/rodgomesc/react-native-fast-tflite/commit/8fa1476786eceef9e49c9ab9191022842e35e102

Did it work? @frankbaele

it works i didn't send a pr because is a mess right now, need  time to organize the code and cleanup some things, for what i'm working  i decided to use pure C implementation

Does this works for Android now??

I'm also looking forward to seeing this working on android. @rodgomesc tell me if you need any kind of assist on this.

Would be great to have this on android 👍

@rodgomesc it would be awesome to see this working on android as well and thanks for your time

Hello everyone,
I apologize for the delay in my response, I've been quite busy lately. I have a proposition that could potentially benefit us all. How about we consider sponsoring @mrousavy with a contribution of $50? This could help in offloading some tasks on his end, and in turn, he might be able to provide me some guidance to solve another issue that's important to me,
What are your thoughts on this?

@rodgomesc I'd be interested in chipping in $50 to help fund Android support on this project. I'm not sure how we'd go about coordinating. But I see there's a Discord channel - maybe we can chat about it there?

same, also willing to chip in

🎅 Ho, Ho, Ho! 🎄
Hey fellow coders and code-esses! 🚀 Guess what? react-native-fast-tflite just got an cool PR #12 ! 🛠🎁
🎁 Your turn to spread the cheer:
Now, I've heard rumors that some of you promised to support Santa (aka me!) for fixing this. 🎅 If you're ready to make good on those promises, drop a line below! Let's make sure the tech elves are accounted for in Santa's nice list! 📜🎉
🎄 Note:
This PR is more festive than a tree full of twinkling lights. Take a look, share your thoughts, and let's keep the holiday coding spirit alive! 🎅🎄
🍪 Cookies for all who contribute! 🍪
Merry coding and happy holidays to all! 🌟

react-native-fast-tflite 1.0.0 is out and it now supports Android! 🥳🚀
Thanks to @jaroslawkrol for spotting the version mistake in build.gradle it now builds fine! 👏


Specify port that the repl starts on

Desired Behavior
Instead of picking a random port every time, we should be able to specify a port that the repl will start on.
Context
Every time I restart the REPL, I have to change my IntelliJ remote REPL connection configuration. I would like that to remain static so I don't have to deal with it.

I would like to work on this myself as a short introductory pull request.
I found in the code where the REPL is created and the port is selected. Now I just need to learn how to add fields to the DSL that gets added to build.gradle so that I can specify the port number in there.
Any pointers would be appreciated, but I can probably figure it out by myself given enough time.

Hi Tom, This is supported already; see the ClojureNRepl section in main doc. Can specify in the build.gradle or as an argument.

Wow sorry apparently I am really bad at reading the documentation. Sorry! Thanks for the heads up


Install and Configure @husky, @lint-staged and @commitlint

Why implement husky, lint-staged and commitlint? What are the advantages?

Commits Pattern
Automated Test before the commit
Git Flow Integration
Code Pattern
Error Signaling (Stage Area Files)
Auto-correct

more details: lint-staged, husky
reference: styleguides

Looking forward to implementing this one :)


OOP School Library: - Feature/setup classes 👨🏾💻 💻

OOP School Library: - Feature/setup classes 👨🏾💻 👨🏾💻
In this milestone, I have managed to do the following:

Added the Person class and provided it's methods, including the private ones. 🎏
Added the student class that extends the person class and the public method. 🎏
Added the Teacher class that extends the person class and its methods. 🎏
Setup rubocop. 🎏
Fixed rubocop errors. 🎏

💯

Thank you @julie-ify  @Alfredbis29


(PUP-11985) correctly enable module:stream without default profile with dnfmodule

the old code would work correctly for ensure => present, but not for ensure => 'some_stream', as dnf does include the whole module spec in the error message and the old regex didn't match anymore.
# dnf module install -d 0 -e 1 -y 389-ds
Error: Problems in request:
broken groups or modules: 389-ds

# dnf module install -d 0 -e 1 -y 389-ds:1.4
Error: Problems in request:
broken groups or modules: 389-ds:1.4

Can one of the admins verify this patch?

Opened https://github.com/puppetlabs/puppet/issues/9142

Nothing in this PR touches Windows related code, so 🤷♀


RE 2, room 704, crash due to G-Adult

Version
3.1.7 (06d5680)
Seed
R720-YZKK-ZXRHA0N5ZCY0003N7QZBNGU9ZZZZZZZZZZZZZZZZZZZZZ
Scenario
RE 2 (Leon A)
Player Character
William
What happened?
In room 704, the game crashed without a reason

Fixed


PSBT does not serialize the same as BIP hex deserialized

BIP 174 includes a bunch of PSBTs serialized as hex, for one of them, when we deserialize it then serialize it, the hex does not match.
use bitcoin::consensus::encode::{serialize_hex, deserialize};
use bitcoin::hashes::hex::FromHex;
use bitcoin::util::psbt::PartiallySignedTransaction;

type Psbt = PartiallySignedTransaction;

macro_rules! hex_psbt {
    ($s:expr) => (deserialize::<Psbt>(&<Vec<u8> as FromHex>::from_hex($s).unwrap()));
}

fn main() {
    let expected_psbt_hex = include_str!("../combine_psbt_hex");

    let mut psbt = signer_one_signed_psbt();
    let other = signer_two_signed_psbt();
    psbt.combine(other).expect("failed to combine PSBTs");

    let want_psbt = hex_psbt!(expected_psbt_hex).unwrap();
    assert_eq!(psbt, want_psbt);

    // Deserialize PSBT hex from BIP does not serialize to the same hex?
    let got = serialize_hex(&psbt);
    assert_eq!(got, expected_psbt_hex);  // This assertion fails.

    // Our code roundtrips just fine.
    let back = hex_psbt!(&got).unwrap();
    assert_eq!(back, want_psbt);
}

fn signer_one_signed_psbt() -> Psbt {
    let hex = include_str!("../sign_1_psbt_hex");
    hex_psbt!(hex).unwrap()
}

fn signer_two_signed_psbt() -> Psbt {
    let hex = include_str!("../sign_2_psbt_hex");
    hex_psbt!(hex).unwrap()
}

AFAIR PSBT does not have a deterministic serialization, since different keys can be serialized from same input/output/global map in any order. So this is probably a non-issue.

Indeed, Psbt serialization does not need to match the spec. It is serializing a key-value map, and we can serialize the keys in any order.

I thought that might be the case, so all the other times we serialized just happened to match the test vector by chance. Thanks, closing.


Extreme UV Index

Describe the bug
What's going on here? The UV index is coming in at corrupt values:
  - datetime: "2024-10-23T05:00:00+00:00"
    condition: clear-night
    wind_bearing: 115
    precipitation_probability: 0
    cloud_coverage: 3
    uv_index: 0
    temperature: 67
    apparent_temperature: 61
    dew_point: 41
    pressure: 30.01
    wind_gust_speed: 14.03
    wind_speed: 6.35
    precipitation: 0
    humidity: 39
  - datetime: "2024-10-23T06:00:00+00:00"
    condition: clear-night
    wind_bearing: 20
    precipitation_probability: 0
    cloud_coverage: 4
    uv_index: 60.48
    temperature: 65
    apparent_temperature: 59
    dew_point: 41
    pressure: 30.01
    wind_gust_speed: 15.88
    wind_speed: 7.16
    precipitation: 0
    humidity: 41
  - datetime: "2024-10-23T07:00:00+00:00"
    condition: clear-night
    wind_bearing: -10
    precipitation_probability: 0
    cloud_coverage: 5
    uv_index:<PHONE_NUMBER>48422800
    temperature: 64
    apparent_temperature: 57
    dew_point: 41
    pressure: 30.01
    wind_gust_speed: 15.5
    wind_speed: 7.09
    precipitation: 0
    humidity: 43
  - datetime: "2024-10-23T08:00:00+00:00"
    condition: clear-night
    wind_bearing: 6
    precipitation_probability: 0
    cloud_coverage: 7
    uv_index:<PHONE_NUMBER>71759100
    temperature: 62
    apparent_temperature: 56
    dew_point: 40
    pressure: 30
    wind_gust_speed: 13.56
    wind_speed: 6.35
    precipitation: 0
    humidity: 45
  - datetime: "2024-10-23T09:00:00+00:00"
    condition: clear-night
    wind_bearing: 30
    precipitation_probability: 0
    cloud_coverage: 8
    uv_index: 0
    temperature: 61
    apparent_temperature: 56
    dew_point: 40
    pressure: 29.99
    wind_gust_speed: 11.18
    wind_speed: 5.37
    precipitation: 0
    humidity: 46
  - datetime: "2024-10-23T10:00:00+00:00"
    condition: clear-night
    wind_bearing: 35
    precipitation_probability: 0
    cloud_coverage: 10
    uv_index: 0
    temperature: 60
    apparent_temperature: 55
    dew_point: 39
    pressure: 29.99
    wind_gust_speed: 9.35
    wind_speed: 4.52
    precipitation: 0
    humidity: 47
  - datetime: "2024-10-23T11:00:00+00:00"
    condition: clear-night
    wind_bearing: 27
    precipitation_probability: 0
    cloud_coverage: 12
    uv_index: 0
    temperature: 59
    apparent_temperature: 55
    dew_point: 39
    pressure: 29.98
    wind_gust_speed: 8.19
    wind_speed: 3.89
    precipitation: 0
    humidity: 48
  - datetime: "2024-10-23T12:00:00+00:00"
    condition: clear-night
    wind_bearing: 20
    precipitation_probability: 0
    cloud_coverage: 14
    uv_index: 0
    temperature: 59
    apparent_temperature: 54
    dew_point: 39
    pressure: 29.98
    wind_gust_speed: 7.61
    wind_speed: 3.58
    precipitation: 0
    humidity: 49
  - datetime: "2024-10-23T13:00:00+00:00"
    condition: clear-night
    wind_bearing: 24
    precipitation_probability: 0
    cloud_coverage: 16
    uv_index:<PHONE_NUMBER>137725000
    temperature: 58
    apparent_temperature: 53
    dew_point: 40
    pressure: 29.99
    wind_gust_speed: 7.49
    wind_speed: 3.58
    precipitation: 0
    humidity: 51
  - datetime: "2024-10-23T14:00:00+00:00"
    condition: clear-night
    wind_bearing: 32
    precipitation_probability: 0
    cloud_coverage: 18
    uv_index:<PHONE_NUMBER>0941292000
    temperature: 58
    apparent_temperature: 53
    dew_point: 40
    pressure: 30
    wind_gust_speed: 7.58
    wind_speed: 3.67
    precipitation: 0
    humidity: 52
  - datetime: "2024-10-23T15:00:00+00:00"
    condition: sunny
    wind_bearing: 30
    precipitation_probability: 0
    cloud_coverage: 17
    uv_index: 0
    temperature: 60
    apparent_temperature: 56
    dew_point: 41
    pressure: 30.01
    wind_gust_speed: 7.61
    wind_speed: 3.58
    precipitation: 0
    humidity: 50
  - datetime: "2024-10-23T16:00:00+00:00"
    condition: sunny
    wind_bearing: 14
    precipitation_probability: 0
    cloud_coverage: 14
    uv_index: 0
    temperature: 65
    apparent_temperature: 62
    dew_point: 42
    pressure: 30.02
    wind_gust_speed: 7.38
    wind_speed: 3.13
    precipitation: 0
    humidity: 44
  - datetime: "2024-10-23T17:00:00+00:00"
    condition: sunny
    wind_bearing: 2
    precipitation_probability: 0
    cloud_coverage: 9
    uv_index: 0
    temperature: 72
    apparent_temperature: 69
    dew_point: 43
    pressure: 30.03
    wind_gust_speed: 7.11
    wind_speed: 2.46
    precipitation: 0
    humidity: 36
  - datetime: "2024-10-23T18:00:00+00:00"
    condition: sunny
    wind_bearing: 20
    precipitation_probability: 0
    cloud_coverage: 7
    uv_index: 15482.88
    temperature: 78
    apparent_temperature: 76
    dew_point: 43
    pressure: 30.02
    wind_gust_speed: 7.16
    wind_speed: 1.79
    precipitation: 0
    humidity: 29
  - datetime: "2024-10-23T19:00:00+00:00"
    condition: sunny
    wind_bearing: 84
    precipitation_probability: 0
    cloud_coverage: 8
    uv_index:<PHONE_NUMBER>01255520000
    temperature: 83
    apparent_temperature: 81
    dew_point: 43
    pressure: 30.01
    wind_gust_speed: 7.78
    wind_speed: 1.36
    precipitation: 0
    humidity: 24
  - datetime: "2024-10-23T20:00:00+00:00"
    condition: sunny
    wind_bearing: 166
    precipitation_probability: 0
    cloud_coverage: 11
    uv_index:<PHONE_NUMBER>16298000000
    temperature: 87
    apparent_temperature: 84
    dew_point: 42
    pressure: 29.99
    wind_gust_speed: 8.99
    wind_speed: 1.39
    precipitation: 0
    humidity: 21
  - datetime: "2024-10-23T21:00:00+00:00"
    condition: sunny
    wind_bearing: 230
    precipitation_probability: 0
    cloud_coverage: 15
    uv_index:<PHONE_NUMBER>11176950000
    temperature: 89
    apparent_temperature: 86
    dew_point: 42
    pressure: 29.97
    wind_gust_speed: 10.74
    wind_speed: 2.01
    precipitation: 0
    humidity: 20
  - datetime: "2024-10-23T22:00:00+00:00"
    condition: sunny
    wind_bearing: 250
    precipitation_probability: 0
    cloud_coverage: 17
    uv_index:<PHONE_NUMBER>14522600000
    temperature: 89
    apparent_temperature: 86
    dew_point: 43
    pressure: 29.95
    wind_gust_speed: 12.82
    wind_speed: 3.31
    precipitation: 0
    humidity: 20
  - datetime: "2024-10-23T23:00:00+00:00"
    condition: sunny
    wind_bearing: 247
    precipitation_probability: 0
    cloud_coverage: 19
    uv_index:<PHONE_NUMBER>14522600000
    temperature: 88
    apparent_temperature: 84
    dew_point: 44
    pressure: 29.95
    wind_gust_speed: 14.45
    wind_speed: 4.68
    precipitation: 0
    humidity: 22
  - datetime: "2024-10-24T00:00:00+00:00"
    condition: sunny
    wind_bearing: 250
    precipitation_probability: 0
    cloud_coverage: 21
    uv_index:<PHONE_NUMBER>11176950000
    temperature: 86
    apparent_temperature: 82
    dew_point: 45
    pressure: 29.96
    wind_gust_speed: 14.76
    wind_speed: 5.37
    precipitation: 0
    humidity: 25
  - datetime: "2024-10-24T01:00:00+00:00"
    condition: sunny
    wind_bearing: 280
    precipitation_probability: 0
    cloud_coverage: 24
    uv_index:<PHONE_NUMBER>16298000000
    temperature: 81
    apparent_temperature: 78
    dew_point: 46
    pressure: 29.97
    wind_gust_speed: 13.24
    wind_speed: 4.94
    precipitation: 0
    humidity: 29
  - datetime: "2024-10-24T02:00:00+00:00"
    condition: clear-night
    wind_bearing: 310
    precipitation_probability: 0
    cloud_coverage: 27
    uv_index:<PHONE_NUMBER>01255520000
    temperature: 77
    apparent_temperature: 73
    dew_point: 46
    pressure: 29.99
    wind_gust_speed: 11.12
    wind_speed: 4.03
    precipitation: 0
    humidity: 35
  - datetime: "2024-10-24T03:00:00+00:00"
    condition: clear-night
    wind_bearing: 300
    precipitation_probability: 0
    cloud_coverage: 31
    uv_index: 0
    temperature: 72
    apparent_temperature: 69
    dew_point: 46
    pressure: 30.01
    wind_gust_speed: 10.07
    wind_speed: 3.58
    precipitation: 0
    humidity: 39
  - datetime: "2024-10-24T04:00:00+00:00"
    condition: clear-night
    wind_bearing: 226
    precipitation_probability: 0
    cloud_coverage: 34
    uv_index: 0
    temperature: 69
    apparent_temperature: 66
    dew_point: 46
    pressure: 30.02
    wind_gust_speed: 11.16
    wind_speed: 4.21
    precipitation: 0
    humidity: 42
  - datetime: "2024-10-24T05:00:00+00:00"
    condition: clear-night
    wind_bearing: 124
    precipitation_probability: 0
    cloud_coverage: 37
    uv_index: 0
    temperature: 68
    apparent_temperature: 64
    dew_point: 46
    pressure: 30.02
    wind_gust_speed: 13.24
    wind_speed: 5.39
    precipitation: 0
    humidity: 45
  - datetime: "2024-10-24T06:00:00+00:00"
    condition: partlycloudy
    wind_bearing: 40
    precipitation_probability: 0
    cloud_coverage: 39
    uv_index: 0
    temperature: 66
    apparent_temperature: 62
    dew_point: 46
    pressure: 30.01
    wind_gust_speed: 14.54
    wind_speed: 6.26
    precipitation: 0
    humidity: 47
  - datetime: "2024-10-24T07:00:00+00:00"
    condition: partlycloudy
    wind_bearing: 12
    precipitation_probability: 0
    cloud_coverage: 41
    uv_index:<PHONE_NUMBER>0941292000
    temperature: 65
    apparent_temperature: 61
    dew_point: 46
    pressure: 30
    wind_gust_speed: 13.78
    wind_speed: 6.22
    precipitation: 0
    humidity: 50
  - datetime: "2024-10-24T08:00:00+00:00"
    condition: partlycloudy
    wind_bearing: 22
    precipitation_probability: 0
    cloud_coverage: 43
    uv_index:<PHONE_NUMBER>137725000
    temperature: 64
    apparent_temperature: 59
    dew_point: 46
    pressure: 30
    wind_gust_speed: 11.61
    wind_speed: 5.46
    precipitation: 0
    humidity: 53
  - datetime: "2024-10-24T09:00:00+00:00"
    condition: partlycloudy
    wind_bearing: 40
    precipitation_probability: 0
    cloud_coverage: 44
    uv_index: 0
    temperature: 62
    apparent_temperature: 58
    dew_point: 46
    pressure: 29.99
    wind_gust_speed: 9.17
    wind_speed: 4.47
    precipitation: 0
    humidity: 55
  - datetime: "2024-10-24T10:00:00+00:00"
    condition: partlycloudy
    wind_bearing: 43
    precipitation_probability: 0
    cloud_coverage: 44
    uv_index: 0
    temperature: 61
    apparent_temperature: 57
    dew_point: 45
    pressure: 29.99
    wind_gust_speed: 7.38
    wind_speed: 3.6
    precipitation: 0
    humidity: 56
  - datetime: "2024-10-24T11:00:00+00:00"
    condition: partlycloudy
    wind_bearing: 33
    precipitation_probability: 0
    cloud_coverage: 44
    uv_index: 0
    temperature: 59
    apparent_temperature: 56
    dew_point: 45
    pressure: 29.98
    wind_gust_speed: 6.31
    wind_speed: 3
    precipitation: 0
    humidity: 57
  - datetime: "2024-10-24T12:00:00+00:00"
    condition: partlycloudy
    wind_bearing: 20
    precipitation_probability: 0
    cloud_coverage: 45
    uv_index: 60.48
    temperature: 58
    apparent_temperature: 55
    dew_point: 44
    pressure: 29.98
    wind_gust_speed: 5.82
    wind_speed: 2.68
    precipitation: 0
    humidity: 58
  - datetime: "2024-10-24T13:00:00+00:00"
    condition: partlycloudy
    wind_bearing: 12
    precipitation_probability: 0
    cloud_coverage: 46
    uv_index:<PHONE_NUMBER>28546700
    temperature: 58
    apparent_temperature: 55
    dew_point: 44
    pressure: 29.99
    wind_gust_speed: 5.7
    wind_speed: 2.68
    precipitation: 0
    humidity: 60
  - datetime: "2024-10-24T14:00:00+00:00"
    condition: partlycloudy
    wind_bearing: 16
    precipitation_probability: 0
    cloud_coverage: 46
    uv_index:<PHONE_NUMBER>03793000
    temperature: 58
    apparent_temperature: 55
    dew_point: 45
    pressure: 29.99
    wind_gust_speed: 5.79
    wind_speed: 2.77
    precipitation: 0
    humidity: 62
  - datetime: "2024-10-24T15:00:00+00:00"
    condition: partlycloudy
    wind_bearing: 40
    precipitation_probability: 0
    cloud_coverage: 43
    uv_index: 158.76
    temperature: 60
    apparent_temperature: 57
    dew_point: 45
    pressure: 30
    wind_gust_speed: 5.82
    wind_speed: 2.68
    precipitation: 0
    humidity: 60
  - datetime: "2024-10-24T16:00:00+00:00"
    condition: sunny
    wind_bearing: 87
    precipitation_probability: 0
    cloud_coverage: 35
    uv_index: 0
    temperature: 64
    apparent_temperature: 62
    dew_point: 46
    pressure: 30
    wind_gust_speed: 5.66
    wind_speed: 2.26
    precipitation: 0
    humidity: 53

Expected behavior
UV index is below 13
Actual behavior
UV index shows values like<PHONE_NUMBER>48422800
API Endpoint
Production
Location
West Hills, CA
Other details
This broke my HA card. I added a filter to fix it:

You can see which day the data is corrupt at because it's missing after the filter is applied
Troubleshooting steps

[X] I have searched this repository and Home Assistant Repository to see if the issue has already been reported.
[X] I have read through the API documentation before opening this issue.
[X] I have not included my API key anywhere in my issue.
[X] I have written an informative title.

I checked the API this morning and I don't see the extreme UV index values that you are seeing. The issue must have been specific to that run and since a newer run was integrated the issue solved itself.
Will still keep this open and will ping @alexander0042 to look into things on his end to see what the issue was.

Yes it seems like it got fixed by itself

I'm kinda surprised that @alexander0042 didn't comment on this issue after he commented on the discussion I re-opened. It could be because the issue sorted itself out that its not a priority?
Since the issue solved itself out we can close this issue or if you'd prefer the dev to look into this and see what might have caused the issue we can leave it open.

Apologies for not commenting, it was because I was looking to see if I could find an obvious source, but no luck! This absolutely shouldn't be happening though, and it's a clue that something weird went on. UV index is one of the weirder values, since it comes from a separate GFS dataset, which can make it helpful for troubleshooting.
One helpful question is if you remember approximately when this started happening and when it stopped?


Allow interior SchemaField and EmbeddedDataField instances to take undefined or null if they can be initialized

[ ] The darkness field in foundry.documents.BaseAmbientSound is a SchemaField that is not required and can be safely initialized from a value of an explicit undefined or null, but currently errors in the tests
[ ] The texture field of foundry.documents.BaseNote is an EmbeddedDataField that is not required and can be safely initialized from a value of an explicit undefined or null, but currently errors in the tests

This is a part of the broader issue that the check for if field.initial can be assigned to the field's assignment type is incomplete.


XMLHttpRequest fix for IE11

I found jxm not working in IE11 when websocket was disabled (or failed) and Chunked was set to false.
Here I propose to set Chunked = true permanently for IE11.
Determining IE11 version is based on https://msdn.microsoft.com/en-us/library/ie/bg182625(v=vs.110).aspx, since it is changed compared to previous IE versions.

LGTM


vue: Unknown custom element from .md

Hi, I'm not sure what I'm doing wrong, but my vue-component doesn't get render from .md file
<template>
  <vHeading lvl="1">Nice to see you.</vHeading> // <- get's rendered
  <component :is="getMarkdownComponent(section)" />

<script>
  import vHeading from<EMAIL_ADDRESS>  import mdHeading from<EMAIL_ADDRESS>
  export default {
    extends: mdHeading.vue.component,
    components: {
      vHeading
    },
    methods: {
      getMarkdownComponent(section) {
        const md =<EMAIL_ADDRESS>        return md.vue.component
      },

my markdown file
---
subject: Hello
tags:
  - tag1
  - tag2
---
# Title
## Title

<vHeading lvl="1">Nice to see you.</vHeading> // <- doesn't get rendered

message

The content gets displayed, only my vue-component doesn't get rendered. I get only this error

"Unknown custom element:  vHeading"

looks some approaches to inject an external component are mixed 👀  The Vue component which is returned by getMarkdownComponent didn't get vHeadingComponent.
There are 2 solutions to fix that:

Inject vHeading in the method like https://github.com/hmsk/frontmatter-markdown-loader-nuxt-sample/blob/master/pages/article.vue
Get rid of <template> block and unneeded methods

third idea came up:
components: {
  MyComponent: {
    extends: vHeading,
    components: { mHeading }
  }
},

then use <my-component /> on template

Hi, thanks for your help. I tried the first version and it worked ;)


How to solve angular_router: ^2.0.0-alpha incompatibility with angular 5.0.0-alpha?

Today I started trying advice from @matanlurey in https://github.com/dart-lang/angular/issues/676.   In my project pubspec.yaml file:
environment:
  sdk: '>=1.24.0 <2.0.0'
dependencies:
  angular: ^5.0.0-alpha
  angular_components: ^0.9.0-alpha
  angular_forms: ^1.0.1-alpha
  angular_router: ^2.0.0-alpha
  browser: ^0.10.0
  dart_to_js_script_rewriter: ^1.0.1
  sass_builder: ^1.0.0

but Resolving dependencies...
Incompatible version constraints on angular:
- angular_components 0.9.0-alpha depends on version 5.0.0-alpha
- angular_forms 1.0.1-alpha depends on version ^5.0.0-alpha
- angular_router 2.0.0-alpha depends on version ^4.0.0
- huastecappadmin depends on version ^5.0.0-alpha
Process finished with exit code 1

Any Idea?

You already got an answer in #676
Why did you create the same issue again?

You still don't seem to have the dependency_overrides mentioned in #676

Based on your response to #676 it seems like your issue is resolved. Please reopen if I'm mistaken.


update gisce/react-formiga-components to v1.3.1

Automated changes by create-pull-request GitHub action

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[BUG] python -m tdvt.tdvt run NAME --verify , exits with failure on successful smoke test

Describe the bug
A clear and concise description of what the bug is.
python -m tdvt.tdvt run NAME --verify

exits with:
2 smoke test(s) ran.
Smoke tests failed, exiting.

Even though output test_results_combined.csv indicates passes.
Desktop (please complete the following information):

OS: Windows - NA
Tableau Version 2019.4 - NA

About you:
Name: Chris Clark
Company: Actian
It looks like a spurious message. This used to work a few months back (commit 7da82beb98a75acaf67fc92acf529c0492b4303c from July 2018) and there was no message. See comment on https://github.com/tableau/connector-plugin-sdk/commit/c3599be53c38fba2665e2806c9d1d11199c370b7

Original code at https://github.com/tableau/connector-plugin-sdk/blob/b9ed43a68d5bc76c16cb81757b134435d4adf010/tdvt/tdvt/tdvt.py#L535

Posted https://github.com/tableau/connector-plugin-sdk/pull/404

Thanks for opening a PR for this! We have it fixed in the dev-tdvt branch (here) and will get it released to master soon.

Fixed in #397