Problem with first install in Debian 9x

Hi @dj-wasabi,
I'm experiencing some troubles when i install over Debian 9x. The first try stops with this error:

MODULE FAILURE
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: apt.cache.FetchFailedException: W:GPG error: http://repo.zabbix.com/zabbix/3.4/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 082AB56BA14FE591, E:The repository 'http://repo.zabbix.com/zabbix/3.4/debian stretch InRelease' is not signed.
failed: [<IP_ADDRESS>] (item=deb) => {
"changed": false,
"item": "deb",
"module_stderr": "Traceback (most recent call last):\n  File "/tmp/ansible_ukaNXF/ansible_module_apt_repository.py", line 556, in \n    main()\n  File "/tmp/ansible_ukaNXF/ansible_module_apt_repository.py", line 544, in main\n    cache.update()\n  File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 464, in update\n    raise FetchFailedException(e)\napt.cache.FetchFailedException: W:GPG error: http://repo.zabbix.com/zabbix/3.4/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 082AB56BA14FE591, E:The repository 'http://repo.zabbix.com/zabbix/3.4/debian stretch InRelease' is not signed.\n",
"module_stdout": "",
"rc": 1
}

If i try a second time, does not stop at this step, but when you are doing operations with APT over shell shows the same warning.
So, my fix for this problem are the next:

name: "Debian | Install gpg key"
apt_key:
keyserver: keyserver.ubuntu.com
id: 082AB56BA14FE591
state: present
when:

zabbix_repo == "zabbix"
tags:
zabbix-server
init
config

name: "Debian | Installing repository {{ ansible_distribution }}"
apt_repository:
repo: "{{ item }} http://repo.zabbix.com/zabbix/{{ zabbix_version }}/{{ ansible_distribution.lower() }}/ {{ ansible_distribution_release }} main"
state: present
when:

zabbix_repo == "zabbix"
with_items:
deb-src
deb
tags:
zabbix-server
init
config

As you can see, i removed the sign keys from Zabbix and replaced with the Ubuntu keyserver and now i can run the first run without any errors.
Do you suggest another workaround for this problem?

Hi @nidr0x
With the zabbix-agent role, I have a vars/zabbix.yml file that contains all keys. Maybe I should use that as well with the server and web roles. But first I need to find a proper Debian Stretch Docker image, so I can test this.

Hi @dj-wasabi
Thank you so much for the fix.


Preliminary support for CH4 disclosures

The tool can now deal directly with simple CH4 emissions disclosures.  At present it can handle tons (or other mass quantities) of CH4 as either scoped emissions (in the ESG data page) or as a base year quantity target (in the target data page).  In either case, the CH4 emissions data is converted to CO2e according to its global warming potential.
In another cases where CH4 is being delivered for combustion purposes (not directly emitted), we continue to use the combustion reaction formulas that create 44g of CO2 per 16g of CH4 burned in oxygen.
These changes include other small cleanups that we found along the way (inefficient and duplicated calls, badly scoped fixtures that resulted in duplicated calculations, etc).

Abandoning due to DCO problem.  See #361


fix: support Check on userset types of users

Description
This fixes Checks so that they support evaluation of relationships on usersets. For example, Check(folder:folder1, viewer, group:engineering#member). Prior to this PR checks of this form would always return false, because we did not support checks on userset types.
References
Review Checklist

[X] I have added documentation for new/changed functionality in this PR or in openfga.dev
[X] The correct base branch is being used, if not main

I think contextual tuples may need some changes. And can we add tests to check as well please?

@craigpastro it seems to work fine with ContextualTuples. I added two tests in server/test/check for these cases. Let me know what you think!

Codecov Report

Merging #146 (61f5f95) into main (3744545) will increase coverage by 0.39%.
The diff coverage is 40.62%.

@@            Coverage Diff             @@
##             main     #146      +/-   ##
==========================================
+ Coverage   75.24%   75.63%   +0.39%
==========================================
  Files          78       78
  Lines        8811     8801      -10
==========================================
+ Hits         6630     6657      +27
+ Misses       1779     1749      -30
+ Partials      402      395       -7

Impacted Files
Coverage Δ

storage/test/tuples.go
50.00% <33.33%> (-0.53%)
:arrow_down:

server/test/check.go
23.88% <36.17%> (+13.06%)
:arrow_up:

storage/memory/memory.go
90.32% <100.00%> (ø)

storage/postgres/postgres.go
64.76% <100.00%> (+0.22%)
:arrow_up:

server/commands/check.go
86.27% <0.00%> (-0.57%)
:arrow_down:

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


Tracking: Accessibility/Screen size issues

The purpose of this ticket is to go through and comment + screenshot all the instances of problematic pages with smaller screen sizes.
This can be done by using inspect element ->
press this small button
on chrome.
This will take you to a view like this:

Try different dimensions/screen widths at the top here.

For firefox, you do inspect -> clicking this button
 and then play around the different screens the same way.
I don't use other browsers, so I cant say exactly how to do this for them, but basically all browsers should have something like this.
For example:
Here, the prev/next buttons cover the text on the page.

Ended up addressing and ticketing all the issues here.


docs: Added gtag to docusaurus

SUMMARY

Our current google analytics tag for the docusaurus website isn't working. The docs suggested this may be the reason:
https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-google-gtag
I did not delete google analytics, wanted to first see if this made a difference.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@eschutho added package.json. When I was originally working on this I didn't realize that yarn added to the package, reinstalled and pushed it up.


SvelteKit release candidate migration: teams page

Migrated page endpoint to src/routes/teams/+page.svelte
Moved/renamed common hero to src/lib/components/block/block.svelte
Migrated paths section to src/routes/about/path-section.svelte
Added Playwrite test for /teams page

Replaced by mega-PR #577.


fix peerDependencies to support Angular 10, 11, 12

closes #47

Sorry man, didn't realize that you have a PR open! As I have merged the same change and release the v1.71 package, this can be close, thanks for your input!


Unstoppable Domains - Login Wallet Integration

This is an implementation to allow the users connect their wallets using Unstoppable domains through UAuth connector way.
A new command was added to test using some environment variables required to make the test with Unstoppable integration.
Here you can click and see the video with the demonstration.

Hi @pedropetri ,
Thank you for your contribution to the project. We however currently do not plan on supporting Unstoppable, as we are in the midst of a significant update of the platform.
Sorry for the inconvenience, I understand you spent time on this work. GitHub unfortunately does not provide the option to disallow pull requests from non-members, but we should have added a warning in our README file to inform external contributors of the situation. I have now added this warning to our README to make sure we don't waste anyone else's time.
Thanks again for your effort to improve our platform, we appreciate you.
Best of luck!


Add LearnGPT

By submitting this pull request, I promise I have read the contribution guidelines twice and made sure my submission follows it.
⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆

You have still not followed the guidelines:

The description should not be title-case.

@sindresorhus I have moved the LearnGPT into the "Web apps" section. Thanks! :)


New Posts First Loaded via Conversation View Not Written to Timelines

When a conversation is loaded and replies newer than the current timeline position exist, they are written to the window.posts array as conversations. Unfortunately, they never get updated to become globally readable. This means that a post may not appear in the timelines until e site is reloaded.
Not cool …

This has been resolved with the introduction of the new post storage mechanism. Closing Ticket.


Yatin: Watch uklivestreaming.blogspot.com

Yatin requests the watch of the watch_keyword uklivestreaming\.blogspot\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

uklivestreaming\.blogspot\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

uklivestreaming\.blogspot\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Rejected by cigien in Charcoal HQ. Reason: 'blogspot domains don't have the com at the end'

Rejected by cigien in Charcoal HQ. Reason: 'blogspot domains don't have the com at the end'


make denoising step faster (or optional)

some data are extremely long to process (>30min).
data: folder_shared/sct_issue/20161203_issue1059/
p.s. the seg in not in the same space-- you can use sct_register_multimodal -identity 1

On my computer, with these data:

Denoising within sct_segment_graymatter takes ~4min and GM segmentation in total takes from 5'45" to 7'30".
Denoising alone (calling sct_maths) takes around 7sec.

--> I will see if I can fasten the denoising within sct_segment_graymatter at the speed of sct_maths -denoise .

Sara, is the denoising done after or before interpolation?  It should be done before (because interpolation changes noise properties in the image)

It is done after to have a smaller image (size 75x75xZ voxels). I'll try to do it before and see if the processing time changes a lot.
For now, changing the denoising parameters in sct_segment_graymatter speeded it up to 8sec (total processing time of 1'30" VS 5'45" with old parameters)

It might be easy to find the bottleneck using cprofile. https://docs.python.org/2/library/profile.html @SaraDupont I can help you with using this tool.

Ah nice, I didn't know about cprofile, it could be useful to see if other processing steps can be fasten !

Working with the original image (size 512x512x30 vox):

With denoising after interpolation with OLD param (image size during denoising: 75x75x30 vox):

denoising: ~4min
total segmentation: 7'30"

With denoising after interpolation with NEW param (image size during denoising: 75x75x30 vox):

denoising: ~8sec
total segmentation: ~2min

With denoising before interpolation, with NEW param (on full sized image):

denoising: 6'15
total segmentation: 8'20"

With denoising before interpolation, with NEW param, with an approximative pre-crop to fasten denoising:

cropping: 10sec
denoising: 10sec
total segmentation: 2'15"

@jcohenadad Do you want to try the new version on the machine that took >30min to process ?
It's on branch sd_issue_1059

Computation on djongo on sct_testing/large:

on branch sd_issue1059:

Mean: {'med_dist': 0.38691221747151755, 'duration_[s]':<PHONE_NUMBER>0340042, 'dice_wm': 0.893424123284146, 'hausdorff': 1.5994234057373238, 'dice_gm': 0.6207222204994831}
STD: {'med_dist': 0.13866713409208728, 'duration_[s]':<PHONE_NUMBER>9917215, 'dice_wm': 0.0229926743781145, 'hausdorff': 0.30379096956509477, 'dice_gm': 0.09775863615469825}

on master

Mean: {'med_dist': 0.38480220968878986, 'duration_[s]':<PHONE_NUMBER>4050828, 'dice_wm': 0.8983245179943837, 'hausdorff': 1.6033622974563104, 'dice_gm': 0.6280646411108158}
STD: {'med_dist': 0.13785229645211938, 'duration_[s]':<PHONE_NUMBER>181169, 'dice_wm': 0.023033543868876898, 'hausdorff': 0.3050878646592654, 'dice_gm': 0.10029562247192686}

--> I'm surprised by the small difference of computation time between master and branch sd_issue1059

i'm trying to compare the syntax-- could you please copy the txt files into /sct_testing

add violin plot for test function and then discuss results

Here is the comparison between master and branch sd_issue_1059, test run on django on sct_testing/large:

performance looks similar for lower processing time on branch_1059. Woukd it be possible to investigate the origin of >600s processing time on the very few datasets?
thanks

Yes, I'm on it !

All the data that have >300sec processing time are in high resolution (0.25x0.25x2.5 mm) and have 26 to 28 slices hence the difference of processing time (GMseg challenge data from Zurich).
When I run one segmentation alone on django (for ex zurich_gmsegChallenge16_01) it takes ~150sec, instead of 725 to 870sec in multi-processing. Thus, the multi-processing biases the results.
--> The computation time depends on the data size, on its resolution and on the "amount" of processes running in parallel. That amount of processes can change during the run of isct_test_function.
To have a representative computation time I will relaunch the same tests without multi-processing on master and on branch _1059.

I see, the "multi-processing" option on isct_test_function sets single-core computation for each subject. But some users only have 4-core (or less), so it would be good to investigate where is the bottleneck in computation time. Aren't all data resampled at 0.3mm in-plane? Is the difference due to the number of slices? Does computation time scale quasi-linearly with number of slices?

Yes, all data are resampled at 0.3mm in-plane but the resampling part (forward and backward) takes more time for data with a higher resolution.  It takes also more time for larger data (and high res data are often large).
Here is a plot of the processing time as a function of the number of slices. The color code indicates the in-plane resolution (white is 0.25 and black is 0.5).

--> For the same resolution, the time does scale quasi-linearly with number of slices.
Here is a plot of the processing time as a function of the in-plane resolution. The color code indicates the number of slices (white is 3 and black is 29).

With these data, it is hard to determine whether the long processing time is due to the high resolution, the large number of slices or the large size of the data, since the data with the very high processing time combine these factors. I can investigate to disentangle the effect of each of these factors on the processing time.

i think we have a good idea now that the high processing time on a few datasets was mainly due to the large number of slices, which we don't need to address now. So we can move forward with the merge, thank you for these thorough investigations

Just merged PR #1120


Discussions are better than issues! ;-)

There is a new feature in github repositories allowing to create discussion forums: maybe some questions could be better categorized as "discussions" rather than "issues", so issues list would remain clean.

Enabled.


[java-client] ConsumerBuilder should have option for defaultSubscriptionInitialPosition

Is your feature request related to a problem? Please describe.
Using the java client, I am unable to continue a subscription from where it was last acknowledged, or from the very beginning of the topic if no such ack is recorded or the subscription is new. If I provide an earliest or latest value to the subscriptionInitialPosition then that value is used instead of continuing from where the subscription was last acked, hence the need for to provide a default when subscribing.
Describe the solution you'd like
Add an option defaultSubscriptionInitialPosition(SubscriptionInitialPosition) to ConsumerBuilder that controls where the subscription should start reading if the subscription is new or has never received an ack.
Describe alternatives you've considered

The default setting of starting a subscription after the most-recent-message (end) of the topic could be controlled at the broker, tenant, namespace or topic level. Any of these alternatives provide less control and ease-of-use than the suggested solution.

Provide a method to read out the last acked message-id directly from the PulsarClient, and combine this with consumer building options similar to the startMessageId and startMessageIdInclusive options of the ReaderBuilder interface. I think this option is less intuitive than having a default initial position option.

Change the behaviour of the current ConsumerBuilder.subscriptionInitialPosition option to use the provided value as a default, but to always continue where the subscription last left-off if an ack has been made on this subscription earlier. This alternative will change the behaviour of existing clients, and is therefore not backwards-compatible, so I would not recommend it.

I have changed my design and now rely on the pulsar client application to track positions rather than using subscriptions and acknowledgements, so I no longer need this feature for what I'm working on. Still I think this option is useful, as it allows using Pulsar subscriptions to be master of stream progress with at-least-once semantics.

@kimcs
ConsumerBuilder.subscriptionInitialPosition is only applied to the subscription that doesn't exist before. If there is already a subscription created, the consumer will start from where it was left. Hence the existing behavior of ConsumerBuilder.subscriptionInitialPosition already meets your requirements. Is that correct?

Closed as answered.


Improved aesthetics

If someone with a knick for visuals could propose some design/improve our styling it'd be very welcomed :)

On it, you may expect some ideas tomorrow

Just to make sure we're on the same page: I'm talking about the backoffice at /jazda url


Push latest versions to CocoaPods?

Will the two latest releases be published to CocoaPods? The latest version available on CocoaPods is 1.19.2.
Thanks!

Pods for 1.20.1 have now been published.


Products contains invalid products

binaries share the same codesign path:
/Contents/Frameworks/BugsnagOSX.framework/Versions/Current
Binaries:
/Contents/Frameworks/BugsnagOSX.framework/BugsnagOSX
/Contents/Frameworks/BugsnagOSX.framework/Versions/Current/BugsnagOSX
This can happen if your build process copies frameworks by following symlinks
Frameworks should use symlink , but bugsnag.framework downloaded from release has multiple files .

@typcn Thanks for bringing this up. I fixed it here: https://github.com/bugsnag/bugsnag-cocoa/commit/94779161ebb4122c1753946c45e8c5b8350f72b0 and it should come out with our next release!


Update .NET sample to use MSAL best practices

Reason for Change:
The MSAL samples do not showcase MSAL best practices such as token caching, authority configuration and assertion refresh.
Source: I am the engineering manager for MSAL.NET

Requirements

[ ] squashed commits
[ ] included documentation
[ ] added unit tests and e2e tests (if applicable).

Issue Fixed:

Please answer the following questions with yes/no:
Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?

[ ] yes
[ ] no

Notes for Reviewers:

Thanks for the ping @aramase, taking a look.

/azp run


I create a project named fmc - fast mirah compiler like fsc in scala

I create a project named fmc - fast mirah compiler like fsc in scala
the server:
nohup java -jar fmc.jar &
using telnet to send command to the server (image fractal.mirah is the file to be compiled):
telnet <IP_ADDRESS> 12580
fractal.mirah
there are two problem:

the compiler render errors to stdout, i don't know if there are any functions like ob_start/ob_getcontent in java, to collect the stdout then resend them to the client.

the client is too sample. any advantage function like -e -j -I command is not supported.

if someone know more about java and has some time, you can try to solve these two problem.
thank you

Thanks for letting us know about your tool. You might also want to look at https://github.com/jstepien/mirahd which does a similar thing, but uses Drb instead of a Java server.
In the future though, please use the mailing list to announce cool libraries you're working on. http://groups.google.com/group/mirah
Github issues are for bugs and feature requests on the language.
As far as redirecting output goes, I'm not sure. The way that mirahd solves it is by replacing stdout with a different IO object, but it does it from JRuby. I don't know how to fix that without doing some digging. Why don't you ask the mailing list?


I would like to custom organize the sort for items within item list or gallery view in a saved search with an option to display as the default

3 uses cases (requests from the curators) so far for the Milberg gallery DPUL exhibits, regarding requested organization of items viewed within saved searches for the site. while one request could be addressed in some way with a recent enhancement (date options for both ascending and descending), others (such as the coins from WA and the most recent Picturesque exhibit, where a curator wishes for a specific aesthetic ordering of subcategories, which is not possible with any metadata associated with it now) are not. Would it be possible to create a hidden field that would function as a ranking system of sorts, that could be used as the default sort order of the saved search? this would eliminate having to continue adding sort options. What do you think?
As a curator I want to create a custom sort order for my dpul collection so that I can present the items in the order they appear in the physical exhibit.

Based on conversation with @kelea99:
This can be implemented globally with one (optional) custom sort order per collection.
The user does not need to be able to make the custom sort order the default for search.
In order to create the desired browse category, submit an empty search, select the custom sort order, and save the search. Then turn it on as a browse category.

Closing this. DPUL 3.0 allows for organization of items in custom order by site builders.

yay!


Are you going to upgrade the climacell API calls

I use climacell for a personal project as well and got an email that they are moving from v3 of the API to v4 in the next 6 months or so. Please tell me you are planning on upgrading this project to use the new v4 calls so that this will continue to work.

I'll take a look at it!

Just to chime in here. I generated a new account on climacell and learned from tech support that the newly generated api keys are "v4" keys and don't work with v3 calls, which is why I was unable to get pi-weather-station to work. Excited to try out v4 calls! Thanks @elewin

I did a quick dive into it. On the API side, several field names have changed and sunrise/sunset is no longer available on the "realtime" "1m" endpoint.  These minor changes got the api working, but I didn't have time to update the react properties, etc.
https://gist.github.com/bakercp/86003bfdfdd361b7e2ae59ad7f0097c4

Here is a PR as it's easier to see the diff https://github.com/elewin/pi-weather-station/pull/6/commits/85f3c2508deee8110db7c2a3820442958d4214d1

Thanks for checking that out, I'll try to get around to it this weekend. It doesn't seem like it should be too complicated.

Thanks for your work on this! Cool project :)

Looks like three files are affected by the V4 change:
bundle.min.js and Appcontext.js have to get new API calls
index.js and Appcontext.js need to deal with the new response
Up to now I only recognized new API calls and new responses. Anything that was removed and is needed?

Looks like three files are affected by the V4 change:
bundle.min.js and Appcontext.js have to get new API calls
index.js and Appcontext.js need to deal with the new response
Up to now I only recognized new API calls and new responses. Anything that was removed and is needed?

I've created a branch that uses ClimaCell API v4:
https://github.com/elewin/pi-weather-station/tree/climacellv4
If anyone wants to test it out, let me know! I'll play around with it myself for a bit and merge it if it looks ok

I've created a branch that uses ClimaCell API v4:
https://github.com/elewin/pi-weather-station/tree/climacellv4
If anyone wants to test it out, let me know! I'll play around with it myself for a bit and merge it if it looks ok

Seems to be working just fine for me. No problems at all that I can find.

Seems to be working just fine for me. No problems at all that I can find.

Loving the project!  I've been using it flawlessly for the last month or so.  What's the upgrade path to v2?  Do we just re-clone the repo and restart?

Loving the project!  I've been using it flawlessly for the last month or so.  What's the upgrade path to v2?  Do we just re-clone the repo and restart?

ClimaCell v4 support added https://github.com/elewin/pi-weather-station/pull/8

ClimaCell v4 support added https://github.com/elewin/pi-weather-station/pull/8

Loving the project! I've been using it flawlessly for the last month or so. What's the upgrade path to v2? Do we just re-clone the repo and restart?

You could do that, or pull the latest changes with git pull origin master
If you decide to re-clone instead, you may want to backup your settings.json file so you won't have to re-enter your keys again (Though you'll need to update the weather key with a new ClimaCell v4 key)

Loving the project! I've been using it flawlessly for the last month or so. What's the upgrade path to v2? Do we just re-clone the repo and restart?

You could do that, or pull the latest changes with git pull origin master
If you decide to re-clone instead, you may want to backup your settings.json file so you won't have to re-enter your keys again (Though you'll need to update the weather key with a new ClimaCell v4 key)


Only match GitHub files that end in the filetype

Some GitHub repos (e.g. keepassxreboot/keepassxc) downloadURLFromGit() returns multiple files matching the filetype, e.g. filename.dmg, filename.dmg.DIGEST, etc. and installation will fail.
By requiring the end quote to match, the function only returns the one file that ends in the filetype and installation will succeed.

thanks !


cmd+c triggers action bound to c even when allowCombinationSubmatches is false [BUG]

Describe the bug
I have an action bound to c but cmd+c seems to trigger the action regardless what allowCombinationSubmatches is set to. There is no action bound to cmd+c in my code.
How are you using react hotkeys components? (HotKeys, GlobalHotKeys, IgnoreKeys etc)
GlobalHotKeys is used in my component.
Expected behavior
Pressing cmd+c does not trigger the action bound to c.
Platform (please complete the following information):

Version of react-hotkeys: 2.0.0-pre9
Browser - chrome

What Configuration options are you using?
I am using the default configuration.

@jiemeechong801 fixed a related bug -- does it reproduce on my fork? https://github.com/ibash/react-hotkeys/commit/23c363b901aeb1765be31f04039a4123b567baa2

@jiemeechong801 fixed a related bug -- does it reproduce on my fork? ibash@23c363b

I tried your fork, I have the "r" key registered and on osx, when pressing cmd+r, the action associated to the "r" key is triggered anyway

I could as well reproduce it with the cmd+enter. With both this and react-hotkeys-ce package.


fix: Update spire server configuration to be v1.6 compatible

Closes #4526
If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[X] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[X] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[X] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions
make run dev delayed-start ds-virtual
New Dependency Instructions (If applicable)

Cancelling without merge.  Fix already included in https://github.com/edgexfoundry/edgex-go/commit/adae08446ccafd5bbf2269dbd38b65bc1a977ca6.  This PR based on an stale copy of main.


migrate material to nullsafety

Description
NNBD migration for material
Related Issues

dart-lang/sdk#40146

Tests
I added the following tests:
None
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

@a14n is this the last PR for Material, so that when this lands all of Material supports null safety?

@a14n is this the last PR for Material, so that when this lands all of Material supports null safety?

Yes after this PR the Flutter framework will be migrated to null safety.


fix(graphql): Use the provided connection name

Fixes https://github.com/TriPSs/nestjs-query/issues/201

Codecov Report
Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (491d589) 78.85% compared to head (4ff0d21) 79.07%.

Files
Patch %
Lines

examples/all-paging/src/main.ts
0.00%
7 Missing :warning:

...kages/query-graphql/src/resolvers/read.resolver.ts
0.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #204      +/-   ##
==========================================
+ Coverage   78.85%   79.07%   +0.22%
==========================================
  Files         670      688      +18
  Lines        9573     9746     +173
  Branches      856      856
==========================================
+ Hits         7549     7707     +158
- Misses       1280     1294      +14
- Partials      744      745       +1

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


properly document guaruntee provided by zebra-network

closes https://github.com/ZcashFoundation/zebra/issues/710

@teor2345 not sure what you mean by "the relevant doc"


"Fildu de Jos" is listed in the drop-down menu

Description:
"Fildu de Jos" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Fildu de Jos" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Fildu de Jos, SĂLAJ".


Basic Windows 10 support

Brief feature description
Having the possibility to use iceoryx on Windows 10
Detailed information

Needed for ROS2 tier 1 support ROS2 Tiers

[x] Unit and integration tests, except timing tests, of the supported features need to run on Windows

[x] remove define public private #529
[x] all tests build and are green

The following features have to be implemented

[x] Implement and integrate named pipes for IPC in windows
[x] inter process capable mutex
[x] inter process capable semaphore
[x] use named ipc semaphore in named pipe

Highly welcomed by the eCAL project too.

I am on it ...

Today I tried a compilation in Windows 10 Pro (VS2017 x64):
cmake -Bbuild -Hiceoryx_meta -Ax64
cmake --build build

Patching
In order to successfully compile the current main (347224e):

I had to force the usage of the x64 toolchain for dependencies (set(CMAKE_GENERATOR_PLATFORM "x64") in the if(WIN32) section of cmake/[cpptoml,cyclonedds,googletest]/CmakeListes.txt. I also added a "-Ax64" option in execute_process. I set the same CMAKE_GENERATOR_PLATFORM in the *.cmake.in files, but it should be useless (imho)
I had to define target_compile_definitions(iceoryx_posh PUBLIC _ENABLE_EXTENDED_ALIGNED_STORAGE) in iceoryx_posh
I had to manually make a downcast for few tests (with static_cast<T>), since CL raises a compilation error:

iceoryx_posh\test\moduletests: test_mepoo_mempool.cpp:28, test_mepoo_typed_mempool.cpp:[42, 93]
iceoryx_utils\test\moduletests: test_cxx_forward_list.cpp:1837, test_cxx_list.cpp:2140, test_semaphore_module.cpp:78

The function getpid is available in Win as _getpid after the inclusion of process.h. I have included the following snippets at the begin of two sources: iceoryx_posh/source/roudi/roudi.cpp and iceoryx_posh/source/runtime/message_queue_interface.cpp#ifdef _WIN32
#include <process.h>
inline int getpid() { return _getpid(); }
#endif

for sure there is a better place/definition of this wrapper.

Testing
Even if compiled correctly, still I got errors in tests, that I'm attaching (compiled in Debug). I hope it will helps.
binding_c_intengrationtests_stderr.txt
binding_c_intengrationtests_stdout.txt
posh_components.txt
posh_integrationtests_stderr.txt
posh_integrationtests_stdout.txt
posh_moduletests_stderr.txt
posh_moduletests_stdout.txt
utils_integrationtests_stdout.txt
utils_moduletests_stderr.txt
utils_moduletests_stdout.txt
utils_componenttests_stout.txt
test_stress_sofi_stdout.txt
Examples
The examples (like simple publisher/subscriber) crashes with errors very about UID/GID (not finding 0). Ican provide more detail on request.

Cool @MatteoRagni, thanks for pushing the WIndows support. So far we do not officially support it. I also think there was no running setup so far. @elfenpiff can give a status where we are.

Hi @MatteoRagni thanks for your work but Windows is currently not yet supported. We only have a compilation test in our pipeline where the semaphore is verified.
Your getpid snippet would fit perfectly into: https://github.com/eclipse/iceoryx/blob/master/iceoryx_utils/platform/win/include/iceoryx_utils/platform/unistd.hpp
Here I proceed as follows.

Lookup the include file in the manpage (unistd.h)
Find corresponding platform file in iceoryx_utils/platform and add it here so that it behaves like the getpid in linux.

At the moment the following in Windows should work:

Semaphores
Shared Memory

The next big Windows port would be:

Unix Domain Sockets (https://github.com/eclipse/iceoryx/blob/master/iceoryx_utils/include/iceoryx_utils/internal/posix_wrapper/unix_domain_socket.hpp)

If you would like to start with this you could try to run only the iceoryx_utils message queue tests:
./build/utils/test/utils_moduletests --gtest_filter="MessageQueue*" in Windows. If everything is ported and and green we could merge it into iceoryx and we would be one step closer to our windows support.
@MatteoRagni would you like to continue? Otherwise I hope that I can continue exactly with this in 2 or 3 weeks.
Btw. if you have further questions you can contact me via gitter: https://gitter.im/eclipse/Primlwiese (or directly)

@elfenpiff I tried the actual situation of the test utils_moduletests --gtest_filter="MessageQueue*" (I removed the _WIN32 guard). I'm attaching the results, but I had to disable timedSend, since it goes in dead lock.
Unfortunately 8 on 19 are green... 😞
message_quque_stdout.txt
I'll try to check out to make something green, but it is something that I have to do in my free time unfortunately.

@MatteoRagni no problem. I will try to work as soon as possible on it. Maybe you get the Windows support as your personal christmas present ;)  but I would not count on it.

Basic Windows support is implemented. All examples are running and most of the unit tests too (except unix domain sockets or ACLs). The tests which are excluded at the moment are testing corner cases which are not relevant for the everyday use and will be implemented with #846


Support history of previous clipboard values

VSCode Version: 1.0.0
OS Version: OS X 10.11.4

Steps to Reproduce:

type cmd+K cmd+v
it does not open an option like the below

+1

@ccirello was this ever implemented by any chance? :X

Why is this closed?

+1 to @peabnuts123
This sounds useful.

Irrespective of the fact it seems like a nice feature to have. I am generally just confused as to why this issue was abruptly closed with no discussion

On Mac OS "Alfred" is a good alternative. But native vscode muli clipboard is still a must have


Feedback request emails are getting stuck in spam filters

We have an ongoing problem with email alerts regarding DMP feedback requests getting stuck in spam filters. We have played with email headers to no avail. I am creating this issue so we can continue to look into this issue and potentially think of other ways to alert users that there is a plan awaiting feedback if we can't solve the spam-filter problem.

I have a few questions to understand this issue;

Are email getting stuck in the user's spam filters or in our filters?
2 What is the originating email address (From:)
Are these issues counting against our SES?

Perhaps we can meet with IAS to help us troubleshoot the issues.

From: Maria Praetzellis @.>
Sent: Tuesday, August 3, 2021 1:01 PM
To: CDLUC3/dmptool @.>
Cc: Subscribed @.***>
Subject: [CDLUC3/dmptool] Feedback request emails are getting stuck in spam filters (#287)
We have an ongoing problem with email alerts regarding DMP feedback requests getting stuck in spam filters. We have played with email headers to no avail. I am creating this issue so we can continue to look into this issue and potentially think of other ways to alert users that there is a plan awaiting feedback if we can't solve the spam-filter problem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/CDLUC3/dmptool/issues/287, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAGF4L32PBGHSXKLP4W6DF3T3BDINANCNFSM5BPQPMYQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

Only in some spam filters. For example it is fine going to my direct ucop address. Goes into a 'promotions' folder for me in Gmail (I think because I've been testing it a lot), goes into the spam folder for the uc3 helpdesk email, and the spam folder for some insitutions.
The email in question are from our 'dmptool-do-not-reply' email address. All of the other system generated emails use the same from address with no issue.
It does go through SES but doesn't seem to have a negative effect in that regard.
I had asked IAS to take a look at it and we determined that at some point in the past (whether it was a bad from address, someone on the receiving end flagged it as spam, etc.) the algorithm used by the client flagged it and we're not sure of a way to unflag it.
I think our best solution going forward is going to be to pursue this option: https://github.com/DMPRoadmap/roadmap/issues/2964 or to completely rewrite the subject and body of the email so that it does not in any way match the old one that has been getting flagged (whether or not that would work for all situations is debatable though).

@mariapraetzellis Will create a new subject and change the body of the email.

Subject:
 %{application_name}: Your plan has been submitted for feedback
Body:
Hello %{user_name}.

Your plan "%{plan_name}" has been submitted for feedback from an administrator at your organisation. If you have questions pertaining to this action, please contact us at %{organisation_email}.

Subject:
DMP feedback request
Body:
Dear %{user_name},

"%{plan_name}" has been sent to your DMPTool account administrator for feedback.

Please email %{organisation_email} with any questions about this process.

Here's the one to admins:
Subject:
%{user_name} has requested feedback on a %{tool_name} plan
Body:
Hello %{user_name},

%{requestor} has requested feedback on a plan: '%{link_html}'. To add comments, please visit the 'Plans' page under the Admin menu in %{tool_name} and open the plan.

Here's the one for admins:
Subject:
A new DMP is awaiting your feedback
Body:
Dear %{user_name},

A DMPTool user, %{requestor}, has submitted a request for feedback on their data management plan: '%{link_html}'.

If you have any questions about this process, please email us at<EMAIL_ADDRESS>
Best wishes,
The DMPTool Team

We updated the content of the email and subject and users have confirmed that they are now receiving the emails.


Request to update user group details does not update user details, whilst reporting success.

Describe the bug
When attempting to update a user's group details, the API endpoint reports success of the change, but the change does not seem to be propagated to the database. Following queries show the change has not taken place.
To Reproduce
Given a mauro instance containing users
Given a user that is in multiple groups

When a request is made to remove the user from groups

And the API returns a message with the updated object

Then the user is not removed from the groups (although the other changes seem to have been made)

Expected behavior
Then the user should have been removed from the groups
Desktop (please complete the following information):

OS: Win10, Azure VM. Running Mauro in Docker for Windows.
Browser: Chrome, Postman
Version:
mauro-data-mapper:
image: "maurodatamapper/mauro-data-mapper:${MDM_TAG}"
build:
context: mauro-data-mapper
args:
MDM_APPLICATION_COMMIT: 4.11.0
MDM_UI_COMMIT: 6.7.0
ADDITIONAL_PLUGINS: "uk.ac.ox.softeng.maurodatamapper.plugins:mdm-plugin-database-sqlserver:5.1.0;uk.ac.ox.softeng.maurodatamapper.plugins:mdm-plugin-csv:3.0.0;uk.ac.ox.softeng.maurodatamapper.plugins:mdm-plugin-database-postgresql:4.0.0;uk.ac.ox.softeng.maurodatamapper.plugins:mdm-plugin-excel:4.0.1"
MDM_UI_THEME_NAME: "default"

Additional context
This error also occurs when attempting to remove users from groups in the UI, and also when removing a user from the only group they are part of.

@Sunspark this is because this isn’t how you edit the groups that a user is part of.
You have to use the delete user from user group endpoint. This is important as this will then update the users permissions.

The only reason the groups are included in the Json is to help the ui make less calls, I didn’t originally want the groups in the json

Delete request to “/api/userGroups/$usergroupid/catalogueUsers/$catalogueUserId”

Cool, that's something to know.
However, the functionality still doesn't work if you attempt it through the UI.

Can confirm 'delete this user from this group' API call works.

Cool, that's something to know.
However, the functionality still doesn't work if you attempt it through the UI. I also feel that the returned JSON shouldn't look like it has removed the user from the group if it hasn't.

i'll look into this

@olliefreeman @Sunspark
Yes, it took me a while to understand that I need to go to the user groups and make these changes. Perhaps just the UI can be improved to either make user groups as a read only field on the User configuration screen, or either allow users to make these changes from this screen as well.


誤変換: 太刀洗

大刀洗があって太刀洗が無い

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 29 Mar 2012 at 2:59

26409dd and c67b4c9 added the word and the test case.


Release 4.6.1

Fix changelog to use ISO date standard.
FIx Changelog PR links.
Description
[Describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves]
Contribution Check List

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable

This change is

@damacus Could this release be published to the supermarket please?


Refactoring for upgrading to gup version 1.0.0.

The gup command has been used by more people than expected. However, the implementation and design of the gup command have a very low level of completion for the following three reasons:

It was implemented by developers who were unfamiliar with golang at the time.
There was a major forced change from the initial design.
Functionality was added without limitations.

Due to these reasons, the gup command has become difficult to maintain, especially in terms of writing test code.Therefore, a complete refactoring will be performed before upgrading to version 1.0.0.

@aqyuki
Thank you for your kind offer. Unfortunately, there are no plans to update the gup command to v1.0.0 this year. The reason is that I am focusing on developing an end-to-end testing framework called go-spectest/spectest.
I feel that there is a need to increase the unit tests before updating the gup command to v1.0.0. This task is challenging and not very exciting.
If you are an engineer who enjoys development, there is a project that could use your help. It's a sub-project of spectest called go-spectest/naraku. It's a project where you are free to create APIs. The purpose of Naraku is to test the APIs created using Spectest and evaluate the usability of the Spectest framework. Currently, we don't have any API ideas, and we're in a challenging situation.
If you enjoy creating APIs, I would be delighted if you could assist with naraku.

Of course, I would like to help you!

@aqyuki
Really? That's good news! I'm glad to hear that you'll be helping with the development. I've added the development instructions to the naraku repository. The repository is newly created and doesn't have many features yet.
I would be delighted if you could propose ideas for small-scale APIs to start with. For example, APIs that return the version and codename of Linux distributions, or APIs that provide information about holidays. Once you have API ideas, please write the details in an Issue (you can write it in Japanese as well).
Once I approve the idea in the Issue, I'd like you to proceed with the implementation. If you prefer to focus solely on implementation, after I create an API proposal in the Issue, I'll mention you and ask you to implement it.
P.S.
無理のない範囲で手伝っていただければ良いです。飽きたら、すぐ止めていただいても大丈夫です。
コントローラ層にロジックを書いても問題ない程度の小さいAPIを作るところから始めるつもりです。


Resolved issue in #615

Closes #615
Fixes Issue #615
Changes proposed

[x] - Added password length validation in the SignIn page and added alert div to show incorrect credentials.
[x] - Updated already added validations in the Signup page with alert as div at the bottom of the form, rather than showing simple alert as dialog box.

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests passed.

Hey @Sar-thak-3, Thanks for Contributing :)


generate a qr code with customized eye shape

how to generate a qr code with customized eye shape as in the image you attached in the project files?

What is customized eye shape?


website: Update M5Ops Documentation

Updated the name of the default RISC-V compiler for m5.
Linked the util/m5 README.md from gem5 in this document

Before I commit can you do 2 things:

Use your real email and real name to make the commit
Add a changeid to the commit


Create Changelog

Please describe the problem you have
Create a changelog, mainly as a placeholder for the v1alpha1 release.

Per https://github.com/projectcontour/contour-operator/pull/125#discussion_r526347849:

We typically use the GH releases to note the changes in each release. Also, you can mark them as a "pre-release" which marks it as alpha (sort of).

Closing due to https://github.com/projectcontour/contour-operator/issues/122#issuecomment-729949440.


@babel/plugin-proposal-class-properties does not work with CRA 2.0

Install<EMAIL_ADDRESS>and use a package with classProperties, for example @material/react-top-app-bar, you will get this error:
...
 Support for the experimental syntax 'classProperties' isn't currently enabled
...
Add @babel/plugin-proposal-class-properties (https://git.io/vb4SL) to the 'plugins' section of your Babel config to enable transformation.

Why would you expect it be enabled for third party libraries?
Publishing code that relies on experimental transforms is quite reckless, assuming somebody does that. It will most definitely break at some point as the spec changes. It’s also unusable in Node.
Or do you mean that this is a false positive?

I had the impression that this is enabled by default, maybe I'm wrong.
In any case, adding a .babelrc file like this in project root doe snot help:
{
  "presets": [
    "react-app"
  ],
  "plugins": [
    "@babel/plugin-proposal-class-properties"
  ]
}

Is the custom .babelrc supposed to work in CRA 2.0? The documentation for the alpha version is nonexistent and its not easy to compile this information by searching through random issues.

Sorry, if you’re not ready for all the problems that come with using an undocumented release then I recommend you not rely on it.
No, it’s not expected that custom .babelrc should work. It was not, and is not supported.
Yes, class properties are turned on by default in application code. Because you have full control over it, and if the spec changes, you could run a codemod.
Class properties are intentionally off for library code. Because they are not finalised, and the spec may change or even become abandoned. Supporting this would create a huge ecosystem burden because now people won’t be able to upgrade to future Babel releases without also breaking the libraries that they depend on, and vice versa. They’re also completely unusable in Node and other environments.
If @material publishes code that relies on experimental features like class properties, I suggest filing an issue with them, and asking them to reconsider. This is pretty bad for the ecosystem as a whole, and I hope this was a mistake and not an intentional decision.

I filed https://github.com/material-components/material-components-web-react/issues/107.

Thanks, I did not know that there is that distinction between application and library code.
The use of the experimental features in @material is based on a decision, it is not a mistake. They do however provide a compiled version of their code, that can be imported from the dist/ directory. But it feels awkward to import generated code during development.
I understand that CRA is trying to be highly opinionated, but some of these opinions seems to fall out of the scope of React itself. In my opinion, CRA should be be opinionated in the relevant scope, and not try to babysit its users when it comes to making decisions outside of that scope.
For example, folks at Google feel like the experimental ES features are here to stay, they are already writing code based on them. I, as the users of both Google's Material library and Facebook's CRA, should be able to develop without these frictions. If in a near, or far, future the experimental ES features are dropped, it will be a problem of Google Material and my application, and not a problem of Facebook CRA.

folks at Google feel like the experimental ES features are here to stay

I think this might be a misunderstanding of some sort. I was physically present at a TC39 meeting just a few months ago, and I can assure you the current behavior or syntax of class properties was not by any means considered final.

I understand that CRA is trying to be highly opinionated, but some of these opinions seems to fall out of the scope of React itself. In my opinion, CRA should be be opinionated in the relevant scope, and not try to babysit its users when it comes to making decisions outside of that scope.

Respectfully, I understand your position, but I assure you that the vast majority of the users of this library won’t know what they’re getting into. If the spec changes in half a year, and all of the code published using it will stop compiling in the next version of CRA that updates Babel, people will blame React and the React ecosystem.
Being the only official project in the React ecosystem related to build tooling, I see it as our responsibility to try to ensure our users don’t shoot themselves in the foot, even if at the time they think it’s best for them.

as a example,for react-navigation,it's published as source code in npm. it use react-navigation-deprecated-tab-navigator, also it's publish using source code without compile,so
./node_modules/react-navigation-deprecated-tab-navigator/src/views/TabBarBottom.js
SyntaxError: D:...\node_modules\react-navigation-deprecated-tab-navigator\src\views\TabBarBottom.js: Support
for the experimental syntax 'classProperties' isn't currently enabled (26:23):
and is there any way to use it without eject?

No and as explained above it’s intentional. I agree it’s annoying for RN projects that adopted a different stance but that’s something you can bring up with their maintainers.

I think this can affect your own application code too, not just third party code - when using yarn workspaces for example. Maybe I'm just doing it wrong tho..
I have many packages in the workspace, and one of them is a CRA app that consumes the other packages. I just migrated my ejected CRA1 app to standard CRA2, so I fiddled around a bit.
I keep watching and transpiling the non-app packages with lerna and babel, transpiling their /src to /lib. The app then consumes their /lib.
So I just tried to change /lib to /src in the import paths to workspace packages, in the hope I might not need watching/transpiling anymore, e.g.
before: import Foo from '@client/components/lib/Foo';
attempt: import Foo from '@client/components/src/Foo';.
But it's not possible due to the Support for the experimental syntax 'classProperties' isn't currently enabled problem. Where it actually works just fine for both the app and any package individually (packages extend the babel and eslint configs "provided" by CRA)
Makes sense, as it "looks like third party code" from the app's perspective. @gaearon Any tips on how to proceed in such a yarn workspace scenario besides transpiling the individual packages? I'm googling the topic for weeks now, with no real success. I might be asking the wrong questions.. :)

@loopmode  If you have code in a workspace, it is treated as third-party code and you'll need to transpile it like you were doing.  ie keep /lib/Foo


Add seed blocks for 420,000 to 430,000

This PR adds the seed blocks for blocks 420,000 to 430,000.
Tested against the consensus hash for block 430,000 - passes successfully.

Awesome, thanks for preparing this!


How to solve the warn log?

Users of the library are seeing this warning in the browser console:
VIDEOJS: WARN: videojs.extend is deprecated as of Video.js 7.22.0 and will be removed in Video.js 8.0.0
How to solve the warn log? Thx~

#44

This is addressed with v1.3.0 of this plugin. Thanks


Allow per-view CSP nonce configuration

Fixes #62
Also corrects documentation about which features can be set at a route level.

Coverage remained the same at 100.0% when pulling 7c6b24d2cda45a260bf93bca77bfef657639bd7f on bazzadp:per_view_csp_nonce into 0040966bed66634db3d0f0b627b9bc6b541238d5 on GoogleCloudPlatform:master.

Coverage remained the same at 100.0% when pulling 7c6b24d2cda45a260bf93bca77bfef657639bd7f on bazzadp:per_view_csp_nonce into 0040966bed66634db3d0f0b627b9bc6b541238d5 on GoogleCloudPlatform:master.

Friendly ping.
Also any chance of a release once this is merged as had a few things I've added recently I'd like to use:

#56 - Restrict CSP to correct length
#60 - Remove X-Content-Security-Policy
#63 - Allow per-view CSP nonce configuration (this one)

Thanks!

Closing this as this has been merged and merged into the fork discussed in #78 and released in v8.0.0, which has been uploaded to PyPi


⚠ Bofrost.fr has degraded performance

In f72cd49, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 991 ms

Resolved: Bofrost.fr performance has improved in 87c9117.


ntr: phytochelatin synthetase avtivity

PMID:10368185
PMID:10369673
PMID:14729665
Reported by: ValWood
Original Ticket: "geneontology/ontology-requests/1775":https://sourceforge.net/p/geneontology/ontology-requests/1775

thanks www.movied.org


Revert "Remove guessing for sport offset (#21771)"

This reverts commit 26b4d50702cb643ba5fd7a1a0bee2930aafdc0e5.
This was originally done to stabilize some tests but results in missing data for TCP connection failures. The CI for this revert commit is green, the plan is to see how this looks in CI after a week or two.

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Update dependencies.

Update dependencies, especially Request.

Boo test fails :ghost:

It appears unit tests fail regardless of changes. I made the commit an empty one and still tests fail which mean you've got other issues to tackle.

Ping. Any ideas on the test fails?

So this project is dead?

@Jonahss  Any ideas of a replacement for sauce-tunnel?
The maintainer is no longer responsive and the project appears abandoned.

Uhoh.
Thanks for the ping @jdalton. Perhaps we can get the repo transferred to us.
@jmreidy are you willing to transfer ownership, or grant someone push permissions and npm publish permissions?

Huh - for some reason I wasn't getting notifications on this (including from @jdalton 11 hours ago), but I DID just receive the notifcation from @Jonahss. I may have to update my GH email prefs...
In the meantime - are these versions still good or should we update them even further? In the meantime I'll merge this PR.

@jmreidy Huzzah!
The updates should have removed the vulnerable deps but there have been updates after.
Something like greenkeeper.io can help track that.

While I'm here - what's the standard for testing for Node libs these days? 0.8 and 0.10 is silly.

0.10 still the most used version in production but I make it my oldest tested then I go 0.10, 0.12, 4, & 5.

@jdalton This is on master for now. I setup Greenkeeper and am waiting to release on NPM until I have updates for the remaining deps - so it'll be going out tomorrow. Thanks!

Released as 2.4.0.

Awesome!

Thank you!


🐛 Execution failed for task ':react-native-vision-camera:externalNativeBuildDebug'

What were you trying to do?
I'm trying to run on Android simulator but it does not work. IOS is working fine.
"react-native": "0.66.5"
 "react-native-vision-camera": "^2.14.1"

I've tried
delete my node_modules folder
yarn install
cd android
./gradlew clean
./gradlew assembleDebug

but still the same.
Reproduceable Code
No response
What happened instead?
* What went wrong:
Execution failed for task ':react-native-vision-camera:externalNativeBuildDebug'.
> Build command failed.
  Error while executing process /Users/seong/Library/Android/sdk/cmake/<IP_ADDRESS>88404/bin/ninja with arguments {-C /Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-vision-camera/android/.cxx/cmake/debug/armeabi-v7a VisionCamera}
  ninja: Entering directory `/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-vision-camera/android/.cxx/cmake/debug/armeabi-v7a'
  [1/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCameraScheduler.cpp.o
  FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCameraScheduler.cpp.o
  /Users/seong/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=armv7-none-linux-androideabi21 --gcc-toolchain=/Users/seong/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64 --sysroot=/Users/seong/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/sysroot  -DVisionCamera_EXPORTS -I../../../../build/fbjni-0.3.0-headers.jar -I../../../../build/third-party-ndk/boost -I../../../../build/third-party-ndk/double-conversion -I../../../../build/third-party-ndk/folly -I../../../../build/third-party-ndk/glog -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/React -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/React/Base -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactAndroid/src/main/jni -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/jni -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactCommon -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactCommon/callinvoker -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactCommon/jsi -I/Users/seong/Documents/usmobile/react-native-app/node_modules/hermes-engine/android/include -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/AnimatedSensor -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/Tools -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/SpecTools -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/SharedItems -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/Registries -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/LayoutAnimations -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/hidden_headers -I../../../../src/main/cpp -DFOLLY_NO_CONFIG=1 -DFOLLY_HAVE_CLOCK_GETTIME=1 -DFOLLY_HAVE_MEMRCHR=1 -DFOLLY_USE_LIBCPP=1 -DFOLLY_MOBILE=1 -DON_ANDROID -DONANDROID -DFOR_HERMES=true -DJS_RUNTIME_HERMES=1 -O0 -fno-limit-debug-info  -fPIC   -std=gnu++14 -MD -MT CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCameraScheduler.cpp.o -MF CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCameraScheduler.cpp.o.d -o CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCameraScheduler.cpp.o -c ../../../../src/main/cpp/VisionCameraScheduler.cpp
  In file included from ../../../../src/main/cpp/VisionCameraScheduler.cpp:5:
  ../../../../src/main/cpp/VisionCameraScheduler.h:7:10: fatal error: 'Scheduler.h' file not found
  #include "Scheduler.h"
           ^~~~~~~~~~~~~
  1 error generated.
  [2/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JHashMap.cpp.o
  [3/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JImageProxy.cpp.o
  [4/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JFrameProcessorPlugin.cpp.o
  [5/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCamera.cpp.o
  FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCamera.cpp.o
  /Users/seong/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=armv7-none-linux-androideabi21 --gcc-toolchain=/Users/seong/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64 --sysroot=/Users/seong/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/sysroot  -DVisionCamera_EXPORTS -I../../../../build/fbjni-0.3.0-headers.jar -I../../../../build/third-party-ndk/boost -I../../../../build/third-party-ndk/double-conversion -I../../../../build/third-party-ndk/folly -I../../../../build/third-party-ndk/glog -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/React -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/React/Base -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactAndroid/src/main/jni -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/jni -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactCommon -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactCommon/callinvoker -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactCommon/jsi -I/Users/seong/Documents/usmobile/react-native-app/node_modules/hermes-engine/android/include -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/AnimatedSensor -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/Tools -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/SpecTools -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/SharedItems -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/Registries -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/LayoutAnimations -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/hidden_headers -I../../../../src/main/cpp -DFOLLY_NO_CONFIG=1 -DFOLLY_HAVE_CLOCK_GETTIME=1 -DFOLLY_HAVE_MEMRCHR=1 -DFOLLY_USE_LIBCPP=1 -DFOLLY_MOBILE=1 -DON_ANDROID -DONANDROID -DFOR_HERMES=true -DJS_RUNTIME_HERMES=1 -O0 -fno-limit-debug-info  -fPIC   -std=gnu++14 -MD -MT CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCamera.cpp.o -MF CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCamera.cpp.o.d -o CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCamera.cpp.o -c ../../../../src/main/cpp/VisionCamera.cpp
  In file included from ../../../../src/main/cpp/VisionCamera.cpp:3:
  ../../../../src/main/cpp/FrameProcessorRuntimeManager.h:13:10: fatal error: 'RuntimeManager.h' file not found
  #include "RuntimeManager.h"
           ^~~~~~~~~~~~~~~~~~
  1 error generated.
  [6/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o
  FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o
  /Users/seong/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=armv7-none-linux-androideabi21 --gcc-toolchain=/Users/seong/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64 --sysroot=/Users/seong/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/sysroot  -DVisionCamera_EXPORTS -I../../../../build/fbjni-0.3.0-headers.jar -I../../../../build/third-party-ndk/boost -I../../../../build/third-party-ndk/double-conversion -I../../../../build/third-party-ndk/folly -I../../../../build/third-party-ndk/glog -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/React -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/React/Base -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactAndroid/src/main/jni -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/jni -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactCommon -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactCommon/callinvoker -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native/ReactCommon/jsi -I/Users/seong/Documents/usmobile/react-native-app/node_modules/hermes-engine/android/include -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/AnimatedSensor -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/Tools -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/SpecTools -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/SharedItems -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/Registries -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/headers/LayoutAnimations -I/Users/seong/Documents/usmobile/react-native-app/node_modules/react-native-reanimated/Common/cpp/hidden_headers -I../../../../src/main/cpp -DFOLLY_NO_CONFIG=1 -DFOLLY_HAVE_CLOCK_GETTIME=1 -DFOLLY_HAVE_MEMRCHR=1 -DFOLLY_USE_LIBCPP=1 -DFOLLY_MOBILE=1 -DON_ANDROID -DONANDROID -DFOR_HERMES=true -DJS_RUNTIME_HERMES=1 -O0 -fno-limit-debug-info  -fPIC   -std=gnu++14 -MD -MT CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o -MF CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o.d -o CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o -c ../../../../src/main/cpp/FrameProcessorRuntimeManager.cpp
  In file included from ../../../../src/main/cpp/FrameProcessorRuntimeManager.cpp:5:
  ../../../../src/main/cpp/FrameProcessorRuntimeManager.h:13:10: fatal error: 'RuntimeManager.h' file not found
  #include "RuntimeManager.h"
           ^~~~~~~~~~~~~~~~~~
  1 error generated.
  [7/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/FrameHostObject.cpp.o
  [8/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/CameraView.cpp.o
  [9/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/JSIJNIConversion.cpp.o
  ninja: build stopped: subcommand failed.

Relevant log output
No response
Device
Android (any device)
VisionCamera Version
2.14.1
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Just started getting this as well. I noticed it was working previously for 2.14.0 and not 2.14.1 (which was resolved from ^2.14.0 for me recently) . Just testing and will report back

To fix this problem you need to downgrade and pin the version react-native-reanimated to precisely 2.10.0.
This is only the case for situations where<EMAIL_ADDRESS>

@stevebrowndotco It solved this issue. thank you 😄

@stevebrowndotco It solved this issue. thank you 😄

Hello How to solve this issue ??


Add support for @NotEmpty annotation from the  Bean Validation API

As of v3.8, Random Beans does not support @NotEmpty annotation. This annotation has been added in Bean Validation v2.0 which is already the version supported by RB.

But doesn't Random Beans already generate non-empty collections and strings by default?

Yes, I was thinking about the use case where RB is configured to generate empty collections in the whole object graph except one or two that are annotated with @NotEmpty.

What I meant is something like:
import io.github.benas.randombeans.EnhancedRandomBuilder;
import io.github.benas.randombeans.api.EnhancedRandom;
import org.junit.jupiter.api.Test;

import javax.validation.constraints.NotEmpty;
import java.util.List;

import static org.assertj.core.api.Assertions.assertThat;

public class TestNotEmpty {

    @Test
    void nonEmptyFieldsShouldNotBeEmpty() {
        EnhancedRandom enhancedRandom = new EnhancedRandomBuilder()
                .stringLengthRange(0, 0)
                .collectionSizeRange(0, 0)
                .build();

        Foo foo = enhancedRandom.nextObject(Foo.class);

        assertThat(foo.firstName).isBlank();
        assertThat(foo.lastName).isNotBlank();
        assertThat(foo.nicknames).isEmpty();
        assertThat(foo.friends).isNotEmpty();
    }

    static class Foo {

        private String firstName;
        @NotEmpty
        private String lastName;
        private List<String> nicknames;
        @NotEmpty
        private List<String> friends;

        // getters and setters
    }
}

This fails with v3.8.0. FYI, I'm working on this for now.

That was not as easy as I expected.. Initial work pushed to branch issue-339, but BV tests are failing. It looks like I hit type erasure when RB tries to randomize a generic collection or map. Even though NotEmptyAnnotationHandler uses a different EnhancedRandom instance where the defaults should make it generate non empty collections and maps, it still generates empty collections and maps (But that's not the case for strings and arrays which are correctly randomized as non empty).
When I debug one of the failing tests, I see that a randomizer is returned as expected from NotEmptyAnnotationHandler (result of the lambda), and when the current field is a collection or map, isIntrospectable is obviously false and we hit collectionPopulator.getEmptyImplementationForCollectionInterface(type). The end result is an empty collection/map which is of course not valid according to @NotEmpty..
@PascalSchumacher Any idea?
I tried the other path of something like:

If type is String => return StringRandomizer
If type is collection => get the genetic type from the field, generate random instances, etc
If type is map => same as collection
etc

But I would not go this path.
NB: No objection on my side to declare this as limitation in the known limitation section.

Yes, if the field is a collection getType just returns the raw type. The actual type can be accessed with in field.getType().getGenericType. We would need access to (part of the logic) in FieldPopulator to generate a collection/map filled with the correct objects. But if if FieldPopulator was accessible we would also need a RandomizationContext to invoke #generateRandomValue. So I guess we have to live with this limitation.

The actual type can be accessed with in field.getType().getGenericType. We would need access to FieldPopulator to generate a collection/map filled with the correct objects.

Indeed, that's what I tried in the "other path", hoping to reuse MapPopulator and CollectionPopulator..

So I guess we have to live with this limitation.

ok we are on the same page. I will merge the changes and update the docs with this limitation.
Thank you for your time and for your quick feedback!

Upon further think about this, I believe we should revert this change, because it causes random beans to generate an invalid object for every generic Collection and Map annotated with @NotEmpty.
This test passes (bean is valid) with Random Beans 3.8.0:
static class Bean {
    @NotEmpty
    public List<String> strings;
    @NotEmpty
    public Map<Integer, String> map;
}

@Test
void test() {
    EnhancedRandom enhancedRandom = aNewEnhancedRandom();
    assertThat(enhancedRandom.nextObject(Bean.class).strings).isNotEmpty();
    assertThat(enhancedRandom.nextObject(Bean.class).map).isNotEmpty();
}

but it fails with current master.

I thought we agreed to live with that limitation and update the docs accordingly (which I did here).
The test passes with 3.8 because by default RB generates non empty collections and maps (so basically the annotation is useless).
I think the only use case (but probably I'm missing another one) of @NotEmpty is for someone who wants all collections/maps in the object graph to be empty except those annotated to be not empty (example given here which fails with 3.8).
Does this make sense?

As said above I did not consider that this feature will change the behavior of Random Beans to generate invalid beans, if a bean has a field which is a collection or map annotated with @NotEmpty.
For example I use bean validation to validate JSON objects after they have been serialized to objects. Every List field that is non-optional is annotated with @NotEmpty. Random Beans 3.8.0 will generate valid objects. Current master will not generate valid objects.

Well that indeed can look like a breaking change, but again, the fact that v3.8 generates valid data for types having NotEmpty is accidental. If I force .stringLengthRange(0, 0) and .collectionSizeRange(0, 0) to have empty collections/maps everywhere except a particular collection, it still not possible with v3.8.
In hindsight, I agree with you. I believe that not introducing a breaking change and updating the docs to mention that @NotEmpty is not supported is better than adding (partial) support for it and eventually break some existing users code.
I will revert the change and declare @NotEmpty as not supported. Thanks.

I will revert the change

Done in 0fe66af17989569f7fad533c79f5a0a3e5884d60.
I will omit mentioning that NotEmpty is not supported because it is implicitly supported by default. So I will keep that implicit in the docs too 🙃

Thanks! 👍


Policies for adding documents?

I have a bunch of various CPU documents, etc., and while I would be happy to upload them, but I am not sure what I can do. For example, I have a Z80 PDF manual, and I checked it against yours, and I found mine to be a bit newer, with a few revisions mentioned in that document. Would that be acceptable? I also have a few ASCII "cards", especially for 6502 and one or two other 8-bit CPUs. Would they be acceptable as well? I also have a few files of my own making that might be useful as well...are they OK to be uploaded too? Thanks for the clarifications!

My only concern is the 1G limit on the size of the repository that GitHub imposes.  Other than that, I'm happy to include all kinds of documents.  The ones you mention sound fine.

So why not drop github and go elsewhere? like, just... storage instead of git?
I know plenty of doc: MCS51, MCS151, MCS251, etc
Do you want docs for system on chip, or just architecture docs?

I kinda like GitHub, because it's a go-to place for many developers.  Sure, I could host the documents anywhere, but then it'd just be another website which no one cares about.
I prefer architecture docs.  I do have many implementation-specific docs too, but I don't see the point in trying to collect info on every single chip ever made.  However, there's no specific rule at this point.

okay, makes sense.
here are some goodies
http://www.keil.com/dd/docs/datashts/intel/8xc251sx_um.pdf
http://www.sharpmz.org/download/8048.pdf
You also need 6502 stuff!

@slorquet Those look good!  Can you make a pull request?

Are you seriously asking me to download the full repo (sth I did not intend to do) instead of using your currently opened browser to download 2 files to your current setup?
I dont care AT ALL about having my name in the history.

I added Contribution Guidelines.


Release/1.0.3

Coverage remained the same at 78.418% when pulling d18ae81b3c46a7b43ba20ca01fe3c2a3aea32724 on release/1.0.3 into ef5c16617d2e00e43b32c1b4b2b763b1beda70f6 on master.


refactor(linter): remove unused logic in resolve_to_jest_fn

I copied parse_jest_fn.rs file to parse_jest_fn_new.rs, the new file only changed resolve_to_jest_fn now. The new version of parse_jest_fn_call doesn't need to get the original of node, and I changed its parameters. I tried to add it to the old file, but it will influence other files, so I created a new file for it. I will delete the old file after all rules migrated.

Current dependencies on/for this PR:

main

PR #1208   👈

This stack of pull requests is managed by Graphite.

The performance does not change too much now, these two function's costly logic has been removed:

I want to migrate more rules to see changes.

Merge activity

Nov 11, 10:15 PM: @Boshen started a stack merge that includes this pull request via Graphite.


My exported trained model returns wrong predictions once in Core ML format

After successfully training a Boosted Trees Classifier model and then exported to a Core ML model and imported it into a Xcode project all processes worked well but the predictions from the converted model comes out wrong
Here is the training data set
fullHori.txt
Model creation
data    = tc.SFrame.read_csv('fullHori.csv')
model = tc.boosted_trees_classifier.create(data, target='shapes')
model.export_coreml("shpModel.mlmodel")
Model test with coremltools
model =  coremltools.models.MLModel('shpModel.mlmodel')
pred   = model.predict({'a': 0.0511, 'b': 0.0564, 'c': -0.0632, 'd': 0.0492, 'e': 0.1657, 'f': -0.0499, 'g': 0.0528, 'h': 0.2515, 'i': -0.0512, 'j': 0.0, 'k': 0.0, 'l': 0.0})

@zeparedes Thanks for reporting things. We will investigate this.

Just wondering if I can help in any way, just let me know I’ll be happy contributing

We have updated several issues with this previously, but usually these issues boil down to numerical inaccuracies that are next to impossible to prevent.  The main reason is that the boosted trees model often uses values from the training dataset in determining the split points.  At these specific values, calling the models at these specific values can often give a different prediction.
The reasons for this are usually due to two things. First, the training is done with float32, but predictions in CoreML are done with float64, and minor differences in the numerical values cause the model to go down different branches, and these different branches will have different predictions.  Second, converting from decimal values to float32 or float64 (e.g. reading from a CSV file, giving it explicitly, etc.) will produce slightly different numbers.  In other words, each of the following routes can be a different number:  decimal->float64, decimal->float32, decimal->float64->float32, float64->float32, etc.  As a result, if the original value was present in the training data, each of these paths may give a different prediction.  Thus, when testing boosted tree model export, it's very difficult to use values from the training data.

This issue is a bit deeper.  Working on a fix.

Fixed with https://github.com/apple/turicreate/pull/958


Experiment with new notification methods

We could brainstorm additional ideas ways to notify end-users and/or customize the notifications, but here are some ways to diversify beyond using SendGrid to send individual emails:

[x] Improve existing email template for moderators (ask Scott, Dave, and Val for feedback)

[x] Change email subject to something like "Please validate new OrcaHello detection" so that the request for moderation is clear (This will also help differentiate moderation requests from subscriber notifications.)

[ ] #117

[ ] Link in footer to OrcaHello summary page

[ ] #111
[ ] Devise a way to not "annoy" end-users with too many emails that the SRKWs have been detected. Maybe only send a new notification if 15 minutes has elapsed since the last send? See #26
[ ] After confirming tests worked well via Try sending via SendGrid to the<EMAIL_ADDRESS>Mailman email listserv where ~150 researchers, managers, and stewards can manage their own subscription.

Screenshots of emails (Sept, 2022):

@rawlink, from discussion with @scottveirs, here are some desires for the email templates:

The subject lines for the moderator and subscriber emails should be more differentiable
Have the confidence percentage in the subject line as well
Instead of linking to the portal in general, link specifically to the detection that needs to be reviewed

@Hurricane18 Ruakan there may be some more revision ideas in this thread.


[bug]SearchAttributeExecutingStateIds for default mode is broken after VersionOfOptimizedUpsertSearchAttribute

This is basically an optimization to reduce the UpsertSearchAttribute action to Temporal.
Before we have this optimization, consider this case State1->State2->State3. we would be upserting:
State1 start: upsert executingStateIds=State1
State1 completed: upsert executingStateIds=[]
State2 started: upsert executingStateIds=State2
State2 completed: upsert executingStateIds=[]
State3 started: upsert executingStateIds=State3
State3 completed: upsert executingStateIds=[]
With the optimization, it becomes:
State1 start: upsert executingStateIds=State1
State1 completed: Noop
State2 started: upsert executingStateIds=State2
State2 completed: Noop
State3 started: upsert executingStateIds=State3
State3 completed: upsert executingStateIds=[]
However, I realized that this doesn't work in case of "DeadEnd" or "GracefulCompleten" with multi-threading:
State1-> State2A + State2B
State2A-> DeadEnd or GracefulComplete
State2B -> State3
State3->State4
When State2A completes, it won't be able to clear up the executingStateIds for State2A, until the whole workflow is completed.

The correct way is to look at the next state like this one: https://github.com/indeedeng/iwf/issues/454
And it will require a versioning

Fixed by introducing ExecutingStateIdsMode


Documentation updated and visual toggle added in the breakpoint window

#450 #448

Thanks for following up on this


feat: Replace all usage of Q with native promises

Replaces all usage of Q with native promises

Q.fcall Q.nfcall Q.ninvoke replaced with native implementations
Q(val) replaced with Promise.resolve(val)
.fail(err) replaced with .catch(err)
.done() dropped

Happy to reimplement with async/await let/const semantics or to use Bluebird's helpers instead.

@maxwellgerber Is there an update here?


config: Allow starting TiKV nodes with <1 CPU

What is changed and how it works?
Issue Number: Close #13586, Close #13752, Ref #14017
What's Changed: Allow starting TiKV nodes with <1 CPU.
Before this change even starting a TiKV node with 0.999 CPU would fail because of rounding.
Check List
Tests

Manual test: started on k8s with 0.3 CPU

Bug fix: Allow starting TiKV nodes with <1 CPU

/retest

/test all

/cc glorv

/cc nrc

/merge

/check-issue-triage-complete

/merge

/merge


pypi not avaliable

Hi,
Looks like the repo is not maintained but I'll try regardless. Would there be any chance of getting the source for this library, it has a couple of functions which looks promising for my usecase.
Thanks

Hello.
Unfortunately I have not yet had enough time on my hands to push the skeleton code to GitHub. I will finish a working but barebones version as soon as the opportunity arises.
The reason behind the repository in the first place is that I have been working on migrating a fairly volumous VitalQIP instance to a NetBox-based DDI but due to a varying level of data quality I had to focus my efforts on data science for cleaning and formatting it.
Thanks for the reminder. 😄

Thanks for that,
I was wondering if you could shed some light on these functions in the mean time. I've tried doing an empty search towards our QIP instance but I think the empty query might be a little bit big, essentially the query times out. We have around 20-30k subnets so i'm not surprised that it times out, but it would be interesting to see how you managed to get around the timeout.
networks0 = qip.list_networks_v4()
subnets0 = qip.list_subnets_v4()

In case you ever need the same thing yourself I found another way to do it;
If you do a post request towards /qip endpoint with headers;
request.AddHeader("Accept", "/");
request.AddHeader("Content-Type", "application/json");
request.AddHeader("Cookie", QipCookie);
with body of;
request.AddStringBody("{ "service": null,"method": "QipList.getV4SubnetList", "id":30,
you will be returned a list of all the subnets with ip subnet and description. The lines above is just copy paste from some c# code I wrote :)

I apologise for the late response, it seems I forgot to follow up the issue. I am glad you found a way to fetch the data you needed from one of the other APIs - some of them are backed directly by command-line tools that may time out when called via the various web services.
For the record: VitalQIP, to my knowledge, uses three different APIs:

The JSON REST API at /json which the web interface - and you - used,
XML-RPC at /qip?RPC2 used by the web interface, and
The JSON REST API described by Swagger at /rest-api.

It is also possible to use various qip-* command-line tools at the server running the ESM software. If you need to mass export data


Update style.css

i think we should add the icons of facebook as well as the twitter handles as there is only three handles used if I am correct @vinitshahdeo ?


Event for onUploadFinished?

Hey, for a RAP app I would like to mass upload stuff via your importer and after the upload is done trigger a custom action. However in your docs I haven't found any suitable hooks, only the three that are fired before any uploading is done. Can you assist me with this issue?

makes sense, can you have a look at #386
what do you think?

that was quick! looks good to me :)

available with version 0.28.0.
https://www.npmjs.com/package/ui5-cc-spreadsheetimporter/v/0.28.0


InverseMapping on a Model with an NSDate results in exception

using RestKit 0.21.0
Mapping to an NSDate from our webservice works great. When trying to do an inverse mapping on that same object we get the following:
D restkit.object_mapping:RKMappingOperation.m:920 Finished mapping operation successfully...
Followed by:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Invalid type in JSON write (__NSDate)'
Expected result was that the NSDate converted to the proper string representation before passing to NSJSONSerialization.
Viewing the dictionary object in RKNSJSonSerialization we can see @createdAt": 2013-12-05 20:14:26 PST

Still looks like this is an issue in the latest RestKit for Cocoapods. Anyone find a solution?

Feel free to submit a PR, @mshawCS!

Wow that was a quick response @segiddins . Are you talking about a pull request on my own fork?

No, I'd like to see a PR into RestKit I can merge to fix the issue :)

Oh ok, I thought you were saying you have a fix for it. I'll have another look at it.

Is this still open? I ask because I have the exact same error when trying a postObject with an inverseMapping including an NSDate. I'm using the latest cocoapods version


Insertion order of node properties is not respected while printing

The Node class requires an OrderedDict for properties, indicating that the order that properties are inserted in is respected. However, in the print function, the props field is passed through the sorted function, breaking this expectation. This is not configurable and can end up preventing accurate round-tripping of kdl documents.
Example code:
from kdl import Document, Node, parse

doc = Document(
    nodes=[
        Node(name="test", props=OrderedDict("b": 1, "a": 2))  # `b` is inserted first
    ]
)

print(contents = doc.print())  # prints `test a=2 b=1\n`

The best resolutions for this issue would be to either remove this call to sorted or change the type of props to be a standard Dict instead of an OrderedDict  to indicate that insertion order is not expected to be preserved.

Ah right, the test suite requires them sorted alphabetically. I'll just hide that behind a PrintConfig option.


ERROR  Error: Could not load<EMAIL_ADDRESS>(imported by .nuxt/dist/server/server.mjs): EISDIR: illegal operation on a directory, read

This is my code (in app.vue):
import { join } from "path";

console.log(join(__dirname, "someFolder"));

Steps:

Disable SSR manually from this package
Run npm run generate

I checked and I think nuxt is confused as there are both path/ and path.mjs
Help will really be appreciated

I tried removing path/ in node_modules/vite-plugin-electron-renderer/builtins that worked, but now I have this error
 ERROR  require is not defined in ES module scope, you can use import instead                                                                                12:52:08

  at node_modules/.pnpm/vite-plugin-electron-renderer@0.13.12/node_modules/vite-plugin-electron-renderer/builtins/path.mjs:1:29
  at ModuleJob.run (node:internal/modules/esm/module_job:194:25)
`

In a electron project, the require always can used in Renderer process if your enable the following options:
{
  webPreferences: {
    contextIsolation: false,
    nodeIntegration: true,
  },
}

Hey! My good buddy, is there any question now?

Nah everything is good now buddy. I'm going to close this issue


Admin settings

So my friend has a server and the admins are able to dupe other admin's e2s and contraptions and we have tried to make it so they cannot but we have been unsuccessful in both advanced duplicator 1+2.
Can someone shed the light on this issue so we could fix it?

You can make them something below admin, yet elevated enough to do whatever they're there to do

It's the job of your admin mod OR your prop protection mod to do this, not adv duplicators. Go check your admin mod or prop protection mod settings.


[BUG] Missing ToValueOptional on struct derived with glib::Boxed despite having #[boxed_nullable]

Bug description
#[derive(Clone, Debug, glib::Boxed)]
#[boxed_type(name = "SomeBoxedValue")]
#[boxed_nullable]
struct SomeBoxedValue();

Some(SomeBoxedValue()).to_value();  // ToValueOptional not satisfied

This seems to work fine in the tests: https://github.com/gtk-rs/gtk-rs-core/blob/e28e523d66a5f8d79da4eb04490b25b6b1e8488c/glib-macros/tests/test.rs#L150-L181
I think the problem is
-#[boxed_type(name = "SomeBoxedValue")]
-#[boxed_nullable]
+#[boxed_type(name = "SomeBoxedValue", nullable)]

If that works, can you submit a PR that removes the boxed_nullable and shared_boxed_nullable attributes from glib-macros/src/lib.rs?

That works properly, after moving nullable to boxed_type.

If that works, can you submit a PR that removes the boxed_nullable and shared_boxed_nullable attributes from glib-macros/src/lib.rs?

Sure, thanks!


Onboarding for First Use

Simply, there should be an onboarding screen for new users.
Get guidance from the HIG

Upon further research, it’s probably not best to have an on boarding screen. User should be able to figure it out without a tutorial. If not, there are bigger problems


Make a planning for open sourcing of NBIlity

Background work and discussions :

Stakeholders
a. Wie zijn ons stakeholder (binnen en buiten Alliander) ?
b. Licentie keuze - de adoptie dremple voor ons beoogd users zo laag mogelijk houden.
c. Transitie maken vanaf openbaar naar open source.
d. Ons target audience zijn NBN, DSO/TSO's andere europese landen and bedrijven in het energie sector.

What is the expected timeline for making the Nbility project opensource

Liever einde 2023

What parts of Nbility would we like to open sources
a. In essentie - alles -maar in een phased manier
b. Wat zijn de fases dan ?

What the pro and cons for making Nbility

What contributions do we expect from the community - stap 2 -

Which community events are applicable and relevant

Besides Alliander what is the view, and vision from other partners to make Nbility open source - allee DSO + Netbeheer Nederlands

Make a bi-weekly meeting with Alliander collegaues (in the beginning) to consult and review the planning

Work packages

Core Capablities
Enterprise Capabilities
Value Streams (Waarde stroom)
Core Capabilities per value stream
Enterprise capabiltie per value streams
Business Objects
Mapping between other standards
Release Note (on webiste and landing page)
Use cases and examples

Strategy and Planning

Based on the phased release approach. In November 2023 we can make the core capabilities and enterprise capabilities models open sources. My assumption of work is that based on the already existing .xml files for these capabilities (version 2.1.1) we can import the files in Archi. After that we proceed further (i.e., publishing, versioning and collaborating) just as we do for other open source projects like LFE. To be completed - 2 Nov. 2023
Repository website and the landing page - The text (release notes, defintions etc.) in Nbility 2.1. presentation  can be used as inspiration for an introductory explanation. - 16 Nov. 2023
Two use case - to make it easier for the communuity to understand, apply and give feedback - we can add two use uses. One each for the core and enterprise capabilities. - 30 Nov. 2023

Notes
Bi -weekly status update meeting
Involve external stakeholders - other (inter)national TSO, DSO, scientific organisations
I am not aware of the paper work or formal process when making a project open source so the time and effort required for that is not in the planning
Core working and discussions group ?

Actions w.r.t the Strategy and Planning action written above.

In line with our plan of making releasing the Nbility framework in a phased manner, one strategy is to have a first release consisting of only Core capabilities and Enterprise Capabilities.

Action done (one branch made - dedicated to core and enterprise capabilities). The branch is called OS_release_1, corresponding to Open Source Release 1. Problem - not able to make changes and commit.

To do. A part of this work has already is done by colleague.

Discuss what should be in the use case ? Considering we are opensourcing core and enterprise capabilities for the first release, the use case should encompase these two aspects only. It would be ideal to start with a simple use case for example; the Financial Compensation process to the CSP (congestion service provider market party) and link it to the core and enterprise capabilities which this process support. Another example could be the Operate congestion management (Run process) of System operations, which supports/realizes many capabilities.
In the coming months as we release more aspects of the Nbility model the same use case can be used to explain the newly released aspects.
Open questions ?

Feedback over the case ?
Where will the textual description of the case be written down ?
Post the use case on the GitHub website ?
Model the use case (i.e., the link between processes and capabilities) in the Archi branch (i.e.,  ?


ReadOnlyClientInterface is not being created for CW721-base contract (Branch v0.16)

When trying to create the client for the cw721-base contract (branch v0.16!) the XxxReadOnlyInterface is not created.
Looking at the schema file
{   "$schema": "http://json-schema.org/draft-07/schema#",   "title": "QueryMsg_for_Empty",   "oneOf": [     {       "description": "Return the owner of the given token, error if token does not exist Return type: OwnerOfResponse", [....]
I noticed that when manually changing the title to (removing the "_for_Empty" part)
  "title": "QueryMsg",
and running TS-codegen again also the XxxReadOnlyClientInterface is created properly.

did you end up resolving this?


Local agent identification UI

For any agent that has the local session attribute, the UI should display some kind of badge/label to identify it as such.

Finished. Looks like