Remediation exception methods and properties

Good morning Microsoft Team,
I am working on a project for a client to display a dashboard around tvm information, and one goal is to show the remediation exceptions that we can configure in the portal. Unfortunately there is no API endpoint for displaying these exceptions.
Is this correct, if so when is an API endpoint planned for this.

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

ID: d05f44de-05db-1ca8-1116-b0c4ad8ac377
Version Independent ID: e7a34d30-3a87-693a-27fc-265bc79231cf
Content: Remediation activity methods and properties
Content Source: microsoft-365/security/defender-endpoint/get-remediation-methods-properties.md
Product: m365-security
GitHub Login: @jweston-1
Microsoft Alias: v-jweston

@atiedemann Thank you for your feedback. I was not able to find API endpoint for displaying these exceptions. Having said that you can provide this feedback directly to our Developers/Product group via the main feedback portal:- https://feedbackportal.microsoft.com/ and they will be able to provide more information on when this is planned(if it is planned).
Hope this helps!
Thanks
Sri

@atiedemann Thank you very much for your kind feedback. Considering your valuable feedback, please log this issue as advised. Here we are limited to documentation fixes and improvements only. Concerning team will evaluate and take the appropriate action, as per their schedule. We proceed here to close it. Thanks again for taking out some time and sharing your feedback.


Test the switch libfunc helper function

The switch function in src/libfuncs.rs is a helper function used to implement libfuncs and is not directly tested, although the code generated is tested in other places. It would be good to find a way to test it directly and increase coverage of the libfuncs module.

Hi,
I would love to work on this issue.
Thanks,
Diego

@Fu8ionDiego still interested? otherwise I'll asign @g4titan

Hi @g4titan, yes I am still interested. Thanks

hey @Fu8ionDiego , wrong tag, you should tag @igaray

Can I work on this?

Assigned!


Check for temp directory write permission before downloading binary

Check if the user has permission to write to $TMPDIR before downloading binary. Else the following issue occurs:
$~ arkade get inletsctl
Downloading inletsctl
https://github.com/inlets/inletsctl/releases/download/0.8.2/inletsctl.tgz
Error: check with the vendor whether this tool is available for your system: open /tmp/inletsctl.tgz: permission denied

Expected Behaviour
If the user running arkade does not have permission to write to $TMPDIR, show error messaging stating such.
Current Behaviour

Shows Binary Download prompt and fails on accessing $TMPDIR  to store binary.
Are you a GitHub Sponsor (Yes/No?)
Check at https://github.com/sponsors/alexellis

[ ] Yes
[x] No

Possible Solution

Check for writable permission to $TMPDIR before downloading the binary
tmp := os.TMPDIR()

info, err := os.Stat(tmp)
if err != nil {
panic(err)
}

permission := info.Mode().Perm()

Steps to Reproduce (for bugs)

Create any random directory:  mkdir test-temp
Change directory mod to 100: chmod 100 test-temp
Make it the default temp directory: export TMPDIR=<absolute-path-to-'test-temp'-directory>
Run arkade get <any-binary>

Your Environment

Operating System and version (e.g. Linux, Windows, MacOS):

Linux  5.10.56-1  x86_64 GNU/Linux

What arkade version is this?

0.7.25

/add label: proposal

@alexellis Can you please take a look at this? :slightly_smiling_face:

Sounds good to me, do you want to try it out in a PR?

@alexellis I will create a draft PR

I can open this as a new bug if needed, but seeing as it's closely related to this issue...
arkade should use a temporary 'tempdir' when downloading, rather than writing to the root $TMPDIR. Otherwise there may be issues if there are equivalent files already present - either being unable to write that file, or accidentally overwriting an existing file.
E.g (when running arkade as non-root user):
sudo touch /tmp/kubectl
arkade get kubectl
Error: open /tmp/kubectl: permission denied

Or in reverse:
$ echo "Some text" >/tmp/kubectl
$ file /tmp/kubectl
/tmp/kubectl: ASCII text

$ sudo arkade get kubectl
$ file /tmp/kubectl
/tmp/kubectl: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped

Hi @mrichar1
I've seen this a few times when I've put my own files into /tmp that conflict on name.
A unique tempdir name would get around that, I don't have a problem with you sending a PR.
What brought you here? Did you run into this issue yourself?
Alex

Yes - I hit this when switching from running as root to running non-root, and was looking through existing issues to see if it had already been reported. Happy to have a go at drafting a separate PR for this.

Thanks a PR would be great @mrichar1


Fix vit-testing integration tests

During fix of the transactions_are_send_between_nodes_with_correct_order test I have figure out that it is missed preinstalled following tools:

jormungandr
vit-servicing-station-server
valgrind
iapyx
vitup

Seems that it will also help for other integration tests

@Mr-Leshiy Should we close this PR?


networking.vswitches option does not work

Issue description
When using networking.vswitches configuration keys, system fails to reliably bring up the switch.
Logs show that the down script is executed just after the up script because de underlying device is down vsint-netdev.service: Unit is bound to inactive unit sys-subsystem-net-devices-vsint.device. Stopping, too.:

Feb 02 18:15:45 nixos systemd[1]: Starting Open vSwitch Interface vsint...
Feb 02 18:15:45 nixos vsint-netdev-start[27533]: Removing old Open vSwitch vsint...
Feb 02 18:15:45 nixos vsint-netdev-start[27533]: Adding Open vSwitch vsint...
Feb 02 18:15:45 nixos ovs-vsctl[27534]: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- add-br vsint -- add-port vsint LAN --
Feb 02 18:15:45 nixos vsint-netdev-start[27533]: Adding OpenFlow rules for Open vSwitch vsint...
Feb 02 18:15:45 nixos systemd[1]: Started Open vSwitch Interface vsint.
Feb 02 18:15:45 nixos systemd[1]: vsint-netdev.service: Unit is bound to inactive unit sys-subsystem-net-devices-vsint.device. Stopping
Feb 02 18:15:45 nixos systemd[1]: Stopping Open vSwitch Interface vsint...
Feb 02 18:15:45 nixos ovs-vsctl[27550]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --if-exists del-br vsint
Feb 02 18:15:45 nixos systemd[1]: Stopped Open vSwitch Interface vsint.

If it is of any relevance, I was working with renamed interfaces (using udev), inside a Virtualbox VM:
services.udev.extraRules= ''
  KERNEL=="eth*", ATTR{address}=="xx:xx:xx:xx:xx:xx", NAME="LAN"
''

Removing the sys-subsystem-net-devices-vsint.device dependency from BindsTo= seems to restore normal behaviour (although we loose unit shutdown when the device is disabled). Since the down script is basically deleting the device (maybe test this regarding flows), this dependency might not be necessary.
I have the VM close by and can perform tests easily.
Thank you for your help
Steps to reproduce

Configure openvswitch bridge:
networking.vswitches = {   vsint = {     interfaces=["LAN"];  }; };
Rebuild system nixos-rebuild switch
Run ovs-vsctl show, no (v)switch appears
Reboot does not fix the problem

Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.

system: "x86_64-linux"
host os: Linux 4.9.65, NixOS, 17.09.2253.559ebb7ed02 (Hummingbird)
multi-user?: no
sandbox: yes
version: nix-env (Nix) 1.11.15
channels(root): "nixos-17.09.2253.559ebb7ed02"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

This issue is resolved by the referenced PR by using systemd-networkd


pre-commit check compliant for github action

In adaption of pre-commit-hook in the workflow of pmp, codes need to be compliant to the given rules, as discussed in https://github.com/PCMDI/pcmdi_metrics/pull/788 and https://github.com/PCMDI/pcmdi_metrics/pull/788#discussion_r742082484

This PR is a mass diff as @tomvothecoder predicted in his comment, but mostly for reformatting codes to follow style rules (flake8, black, isort, etc). Many thanks to @tomvothecoder for his comments which helped me learn a lot about setting up the github action workflow. There was a steep learning curve but I think I am getting better with it.
@tomvothecoder, could you please take a look the revised .pre-commit-config.yaml and setup.cfg files to see if they make sense to you?
@acordonez, could you please help running demos using this branch to see if there is any impact? I expect the result should not be affected by this change. I will also run the demos on my end, but wanted to have additional test from different end to be safer. Please also note that some files under cmec directory has been changed as well, but just about formatting and style.
@gleckler1, I have reduced flake8 error messages from hundreds to tens, and following two files still have issues and I don't have good ideas how best to fix. Any advice? If that to be too much hassle, I think I can leave them out for now (exclude the 2 files from flake8 test, until they got fixed).
pcmdi_metrics/pcmdi/scripts/pcmdi_compute_climatologies-CMOR.py:
320:43: F821 undefined name 'r'
320:46: F821 undefined name 'i'
320:49: F821 undefined name 'p'

pcmdi_metrics/devel/monsoon_wang/scripts/bar_chart_monsoon_precip_index.py:
218:18: F821 undefined name 'mod_name'
220:32: F821 undefined name 'mod_name'
223:30: F821 undefined name 'mod_name'
226:10: F821 undefined name 'numexpts'
228:23: F821 undefined name 'numexpts'
230:27: F821 undefined name 'numexpts'
231:31: F821 undefined name 'numexpts'
244:27: F821 undefined name 'numexpts'

Awesome job picking up the QA tools quickly Jiwoo! It's definitely not an easy task.

@tomvothecoder, could you please take a look the revised .pre-commit-config.yaml and setup.cfg files to see if they make sense to you?

Those files look good to me.

@acordonez, could you please help running demos using this branch to see if there is any impact? I expect the result should not be affected by this change. I will also run the demos on my end, but wanted to have additional test from different end to be safer. Please also note that some files under cmec directory has been changed as well, but just about formatting and style.

Yes, the results should be identical since it is simply code and import formatting. It would still be good to validate though.
Note, one potential issue with using isort is if you define env variables (e.g., turning off MPI with cdms2) or set configurations for libraries like matplotlib (e.g., `matplotlib.use("Agg") above certain imports. In those cases, you'd have to ignore sorting the lines for those specific imports. I performed a quick search for these cases, but luckily they don't apply.

@gleckler1, I have reduced flake8 error messages from hundreds to tens, and following two files still have issues and I don't have good ideas how best to fix. Any advice? If that to be too much hassle, I think I can leave them out for now (exclude the 2 files from flake8 test, until they got fixed).

That flake8 error F821 undefined name is saying that those variables aren't defined in the current scope, but are being referenced. The fix is to either remove the lines that reference those undefined variables, or add noqa: F821 (not suggested since it leaves broken code in place).

On a side note, I noticed the GH Actions build job fails on the "Run Tests" step because there are no tests available to run.
============================ no tests ran in 3.17s =============================
Error: Process completed with exit code 5.

https://github.com/PCMDI/pcmdi_metrics/runs/4100746374?check_suite_focus=true#step:5:120
I'm currently exploring a few possible workarounds for this.

Hey @lee1043, I have addressed the GH Actions build issues in PR #794. Please review the summary of changes (it includes removing mypy for now).
That PR will merge into this PR.

* @acordonez, could you please help running demos using this branch to see if there is any impact? I expect the result should not be affected by this change. I will also run the demos on my end, but wanted to have additional test from different end to be safer. Please also note that some files under `cmec` directory has been changed as well, but just about formatting and style.

I ran all the notebooks. The two issues I ran into are

the MJO, Monsoon Sperber, and Variability Modes drivers can't import VCS
I don't have the old style ENSO data anymore, so while I can run the ENSO notebook without error it doesn't generate metrics.
Let me know if these results are expected or if I should do more testing.

I also did a cmec-driver run using the mean climate driver, which was successful.

@acordonez Let's see what JL says about the vcs conflict.  We know we need to move away from this but I'm not sure if he is ready for doing that with MJO, monsoon sperber, and variability.
Are we missing some data for the ENSO demo?  I thought we were successful in switching to the new style.

@acordonez Thanks for checking this. While I am refactoring vcs plots (https://github.com/PCMDI/pcmdi_metrics/pull/786), I think it is okay to check output json files to see if there is any noticeable difference. Sorry, I should have clarified this in advance.
By the way could you tell me little bit more what do you mean by no old style ENSO data?

Hey @lee1043, I have addressed the GH Actions build issues in PR #794. Please review the summary of changes (it includes removing mypy for now).
That PR will merge into this PR.

@tomvothecoder thanks for the PR. I agree that removing mypy makes sense to me because most of PMP code has been wrote with dynamic typing, instead of static typing as checked by mypy.

I also did a cmec-driver run using the mean climate driver, which was successful.

@acordonez glad to hear that! Thank you for checking.

@acordonez Thanks for checking this. While I am refactoring vcs plots (#786), I think it is okay to check output json files to see if there is any noticeable difference. Sorry, I should have clarified this in advance.
By the way could you tell me little bit more what do you mean by no old style ENSO data?

The VCS issue is blocking the metrics output for MOV - the driver seems to fail before writing the JSON output. I'd have to spend some time editing the driver code to make this pass.
I'm having some kind of issue with the ENSO driver producing metrics. I thought maybe I was using the wrong data version or obs dictionary but if we merged that change, it must be something else.

@acordonez I think turning off plot option in parameter files should prevent calling vcs module, but please let me know if not.
@gleckler1 do you have any idea why the file is not available, or who to talk to?

@lee1043 @acordonez I've just looked on pcmdiweb and the only relevant file I see is pmp_enso_tutorial_files.txt
Can you try that?  The date on it is May 04 2021.   It's better to have the version in the filename, but I'm not sure where the pmp_enso_tutorial_files.v20210823.txt came from.   Late Aug was pretty busy for me, this could be a loose end for us to resolve.

@lee1043 @acordonez  Also, I see this file (pmp_enso_tutorial_files.txt) is for a demo, which I don't recall necessary being the same data as for running all the enso metrics.

@gleckler1 @lee1043 https://pcmdiweb.llnl.gov/pss/pmpdata/pmp_enso_tutorial_files.txt does work. I don't remember why a different version is in the ENSO notebook. I can make a quick PR to fix that

@gleckler1 @acordonez in the ENSO notebook cell [1] I see there are following two lines:
#r = requests.get("https://pcmdiweb.llnl.gov/pss/pmpdata/pmp_enso_tutorial_files.txt")
r = requests.get("https://pcmdiweb.llnl.gov/pss/pmpdata/pmp_enso_tutorial_files.v20210823.txt")

I found a related email thread about having this while and forwarded to both of you.

@lee1043  using the no plot option wasn't sufficient; I'm getting an import error due to VCS just for calling the help statement. Since there's just one script each using VCS in MOV and MJO I locally set those functions to not import VCS and return. Then I could run the metrics, which look the same as before.

the MJO, Monsoon Sperber, and Variability Modes drivers can't import VCS

@acordonez Just wondering if you're using the latest conda-env/dev.yml to run these notebooks? This env doesn't include vsc and vcsaddons, so you'll run into ModuleNotFoundError: No module named 'vcs'.

@acordonez I merged the PR #797 that is for removing VCS dependencies to this branch, so I think turning on plot option in parameters should have no problem by now.
In separate, somehow I am failing running Demo0 and Demo1, which I think it might not resulted by changes in this PR but by changes in directory structure in demo data or failure of some files in the demo data directory. I will investigate this.

the MJO, Monsoon Sperber, and Variability Modes drivers can't import VCS

@acordonez Just wondering if you're using the latest conda-env/dev.yml to run these notebooks? This env doesn't include vsc and vcsaddons, so you'll run into ModuleNotFoundError: No module named 'vcs'.

This should be no longer issue as I removed VCS. Thanks for pointing it out.

I have double-checked all demos results are consistent to that in the current master. With that, I am merging this PR.


[Network] az network private-endpoint-connection: Support cosmosdb types

Description

rename service-name to resource-name
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

add to S169


Extensions config for JWT signing/encryption key

Description
This PR adds a section for extension configuration with signing/encryption keys for JWT generation.
Issues Resolved
Create dynamic configuration section in config.yml for extensions
Testing
Manual tests were performed by checking if configurations were deserialized into POJO correctly. Existing tests in: ConfigTests check if the config file is deserialized correctly
Check List

[x] New functionality includes testing
[ ] New functionality has been documented
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Hi @MaciejMierzwa , could you please sign the commits with git commit --signoff? You can see more information about DCO here: https://github.com/opensearch-project/.github/blob/main/CONTRIBUTING.md#developer-certificate-of-origin

Regarding comment about adding abstract methods. What do you think about just adding concrete methods into DynamicConfigModelV7 (without adding those to the abstract class)? I could also separate DynamicConfigModel abstract class into 2 interfaces, or maybe add changes to V6 class so config would be also available there.
Returning null looks like a programming smell that will bite somebody sometime in the future.

@MaciejMierzwa Any V6 classes you see are for the old security configuration that supported ES6 and before. From ES7 and all versions of OpenSearch, V7 is the configuration that is utilized. For extensions related work, it will only be supported in OpenSearch so its only applicable to V7. If you added the same Extension section to ConfigV6 and referenced those in the method implementations in DynamicConfigModelV6 than that would also be ok, but it would never be used.
There are some methods that may return null if no value has been set in the config. See Kibana.opendistro_role which is set to null by default:

https://github.com/opensearch-project/security/blob/main/src/main/java/org/opensearch/security/securityconf/impl/v6/ConfigV6.java#L91
https://github.com/opensearch-project/security/blob/main/src/main/java/org/opensearch/security/securityconf/DynamicConfigModelV6.java#L131-L134

This PR connects with a Draft PR that @RyanL1997 opened yesterday which consumes these settings in an Authenticator for the tokens that will be issued for extensions.
See https://github.com/opensearch-project/security/pull/2672/files#diff-efd217975f23af4bb84808e2771bfc85211f12b59bb619da430a3363902207ceR264-R272 for one of the locations these settings will be consumed. The other location will they will be consumed is the JWTVendor where they are used to sign the token that is issued and encrypt sensitive claims like the roles and the backend roles.

@MaciejMierzwa On second thought, I wonder if it would be possible to have a single Abstract method. Something like:
public abstract Settings getDynamicExtensionsSettings();

The signing_key is used for the default symmetric HS512 signing for the JWT issued for extensions, but there is an open issue for JWK configurability: https://github.com/opensearch-project/security/issues/2680
The http_authenticator config is returned as a settings Object for an http_authenticator. See below for an example JWT backend config.
jwt_auth_domain:
  enabled: true
  order: 0
  http_authenticator:
    type: jwt
    challenge: false
    config:
      signing_key: "base64 encoded key"
      jwt_header: "Authorization"
      jwt_url_parameter: null
      subject_key: null
      roles_key: null
  authentication_backend:
     type: noop

Everything in the config: area of this backend would be returned as a Settings Object.
See relevant areas of the code:

https://github.com/opensearch-project/security/blob/main/src/main/java/org/opensearch/security/securityconf/DynamicConfigModelV7.java#L279

Settings.builder().loadFromSource(ad.getValue().http_authenticator.configAsJson(), XContentType.JSON).build()

https://github.com/opensearch-project/security/blob/main/src/main/java/org/opensearch/security/securityconf/impl/v7/ConfigV7.java#L324-L331

Would it be possible to make a single abstract method to return all dynamic settings for extensions?

Hi, @cwperks let me know if the changes that I made in the latest commit are more or less what you meant. I replaced method returning Settings object instead of two following methods:
    public abstract String getExtensionsSigningKey();     public abstract String getExtensionsEncryptionKey();

Hi @MaciejMierzwa, the new changes look great! Just a couple of things remaining and then this looks good to go:

Can you merge the latest changes from main into this branch? There was a build fixing PR that renewed some expired certs used in tests
As @scrawfor99 mentioned, we should add a test for this change and verify the dynamic nature of the configuration. It would also be useful to test any validation logic if the settings need to be validated. There's an example of security configuration integ tests that @lukasz-soszynski-eliatra has contributed to this repo. See https://github.com/opensearch-project/security/blob/main/src/integrationTest/java/org/opensearch/security/SecurityConfigurationTests.java#L201-L214 for an example test that updates configuration dynamically. To run integ tests locally you can use ./gradlew integrationTest --tests SecurityConfigurationTests.shouldUseSecurityAdminTool -i

Hi @cwperks, @scrawfor99, pushed in integration test that realoads cluster extensions configuration. After recent merge from main branch random commits are not recognized as signed-off. I'll probably have to nuke this PR and rebase everything.

Hi @MaciejMierzwa, thank you for adding tests. You should be able to rebase following the DCO output steps. This will let you overwrite the DCO issue. I went ahead and manually set this version as signed for you as well.

Hi @MaciejMierzwa, thank you for putting these together and adding the test! In generally this looks good to me. I just initiated the rerun of the rebase. In addition, as @cwperks mentioned above, my work of authentication backend will take in these configurations.

Codecov Report

Merging #2671 (0de11fa) into feature/extensions (73ab1fc) will increase coverage by 0.17%.
The diff coverage is 74.05%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@                   Coverage Diff                    @@
##             feature/extensions    #2671      +/-   ##
========================================================
+ Coverage                 61.24%   61.42%   +0.17%
- Complexity                 3337     3393      +56
========================================================
  Files                       262      272      +10
  Lines                     18605    18815     +210
  Branches                   3278     3288      +10
========================================================
+ Hits                      11395    11557     +162
- Misses                     5607     5655      +48
  Partials                   1603     1603

Impacted Files
Coverage Δ

...earch/security/dlic/rest/api/MigrateApiAction.java
4.30% <0.00%> (ø)

...security/dlic/rest/api/SecuritySSLCertsAction.java
71.13% <ø> (-0.59%)
:arrow_down:

...arch/security/securityconf/DynamicConfigModel.java
100.00% <ø> (ø)

...ch/security/securityconf/DynamicConfigModelV6.java
0.00% <0.00%> (ø)

...g/opensearch/security/support/ConfigConstants.java
94.44% <ø> (ø)

...ch/security/securityconf/DynamicConfigModelV7.java
62.26% <40.00%> (-0.73%)
:arrow_down:

...dlic/rest/api/RestApiAdminPrivilegesEvaluator.java
75.75% <41.66%> (-2.58%)
:arrow_down:

.../action/tenancy/TenancyConfigRetrieveResponse.java
54.16% <54.16%> (ø)

...search/security/securityconf/impl/v6/ConfigV6.java
62.37% <54.54%> (-0.96%)
:arrow_down:

...ensearch/security/action/tenancy/EmptyRequest.java
60.00% <60.00%> (ø)

... and 19 more

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

@MaciejMierzwa  The spotless issue is a result of using the default encoding in the JWTVendor. It can be fixed by swapping to a non-default encoding--specifying UTF-8 etc.

Yea, I think this part of the code got to my branch during a merge. Added charset UTF-8

@MaciejMierzwa @scrawfor99 Has a PR open in this repo to fix the issue https://github.com/opensearch-project/security/pull/2715. We need to wait for the PR to be merged and then you can merge the latest changes from main into this branch to re-run the CI or one of the maintainers can also synchronize the branches assuming there are no merge conflicts.

Merging this into the feature branch for support for extension REST handlers.


plugin error: readdirent: invalid argument

Hello!
First things first: I love this project! This is a tool/feature I'm missing in terraform.
I ran into problems right away though.
I'm using the binary https://github.com/GoogleCloudPlatform/terraformer/releases/download/0.7/terraformer-darwin-amd64
with this gcp provider's binary for darwin
https://releases.hashicorp.com/terraform-provider-google/2.5.1/
(I tried the 2.5.0 too with the same result)
When running this or any other command on my project:
terraformer import google --resources=gcs,firewalls  --zone=europe-west1-b --projects=my-secret-project

I'm getting
2019/05/03 14:38:36 plugin error: readdirent: invalid argument
2019/05/03 14:38:36 readdirent: invalid argument

Any ideas?

I tried with this version of gcp provider
ll ~/.terraform.d/plugins/darwin_amd64/
total 352760
-rwxr-xr-x  1 sergeylanz  primarygroup   122M Jan 16 20:43 terraform-provider-aws_v1.56.0_x4
-rwxr-xr-x@ 1 sergeylanz  primarygroup    50M Apr 22 20:25 terraform-provider-google_v2.5.1_x4
(venv) ➜  demo terraformer import google --resources=gcs,firewalls,forwardingRules,instanceTemplates,regionBackendServices,regionInstanceGroupManagers,networks,subnetworks,healthChecks,urlMaps,backendServices,httpHealthChecks,backendBuckets --projects=amazing-limiter-415 --zone=us-east1-c
2019/05/03 15:56:04 google importing project amazing-limiter-415
2019/05/03 15:56:04 google importing... gcs
2019/05/03 15:56:08 google importing... firewalls
2019/05/03 15:56:09 google importing... forwardingRules
2019/05/03 15:56:11 google importing... instanceTemplates
2019/05/03 15:56:13 google importing... regionBackendServices
2019/05/03 15:56:14 google importing... regionInstanceGroupManagers
2019/05/03 15:56:15 google importing... networks
2019/05/03 15:56:17 google importing... subnetworks

working
maybe permissions on ~/.terraform.d/plugins/darwin_amd64/ ?

Thanks! It wasn't the permission, I named the provider binary file as darwin_amd64...
I didn't have the darwin_amd64 folder there as I never used any tf plugins...
cp terraform-provider-google_v2.5.0_x4 ~/.terraform.d/plugins/darwin_amd64

thanks a lot!


Adding teams info

closes https://github.com/MicrosoftDocs/office-docs-powershell/issues/10169

Learn Build status updates of commit 2766a7a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsPrivacyConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

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

@get-itips

Learn Build status updates of commit 2e88c44:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsPrivacyConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

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

@tiburd Please merge this Pr. Thanks

Learn Build status updates of commit 4191d66:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsPrivacyConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

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


State update showing Warning message  and not updating state while running background task and  I open app.

When I close and  open  app it's showing Warning  message for state update as shown below
ERROR  Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function.     in App (at renderApplication.js:47)     in RCTView (at View.js:34)     in View (at AppContainer.js:107)     in RCTView (at View.js:34)     in View (at AppContainer.js:134)     in AppContainer (at renderApplication.js:40)  LOG  Runned ->  11
Code
    let [ counter, setCounter ] = useState( null );

    // state update function
    const counterHandler=( i )=>{
         setCounter( i )
    }

    for (let i = 0; BackgroundJob.isRunning(); i++)  {

           // state update function calling to update state for every job running
            counterHandler( i );

            await BackgroundJob.updateNotification({ taskDesc: 'Runned -> ' + i });
            await sleep(delay);
     }

     await BackgroundJob.stop();

I need show background running process  on view  not on notification even I close app  and if I open app need show running  state process on View please is there any solution for that ?
Thank you in advance.

Is there any update regarding this issue ??

@sureshhallyali, please take a look at the documentation:
// You can do anything in your task such as network requests, timers and so on,
// as long as it doesn't touch UI. Once your task completes (i.e. the promise is resolved),
// React Native will go into "paused" mode (unless there are other tasks running,
// or there is a foreground app).

You are receiving those errors because you are trying to update a React state object from the background. Your background tasks should not touch any UI components while the app is in the background.

@Rapsssito Thank you for the update but  is the  any way to show background running process in UI component

@sureshhallyali, I highly recommend you checking out this issue: https://github.com/Rapsssito/react-native-background-actions/issues/57.


[WIP] [Custom Directive] Add post about GraphQL custom directives

and specifically how we use them to help tighten up our error handling.
This is still a WIP, mostly because I need to add in a bunch of links (placeholders for now).

This is really cool! You've done a great job setting up the need/opportunity, and specifying how custom directives meet it. Nice work!

@joeyAghion your main question:

I'm left with a big question about the design, which is: why constrain error propagation to one "principal" field?

That's essentially a base assumption of this setup. You must be able to pick one and only one field in your query to be considered 'principal', and what the rest of the views depend on. It then follows that the singular HTTP status code, and any other binary choices (does this page render or error?, etc.) could be answered accordingly.
So far, in our main apps (plus our nested schema), that's proven to be pretty natural and seems to work well. In a hypothetical example of a product comparison page, where you'd demand both, you would have to handle that in a custom way, most likely.
My first thought as to that implementation would be a custom middleware, akin to the middleware for principal errors (covered in a future post!), found here: https://github.com/artsy/reaction/blob/c6d630f8c3213f47c5124f63eda13fbb9d8f497b/src/Artsy/Relay/createRelaySSREnvironment.ts#L107 . You would inspect the shape of the response, and throw an error if both pieces of data weren't present. Might look something like:
return next => async req => {
  if (req.id === "SampleProductPageQuery") {
    const res = await next(req)
    const hasAllData = res.json.data.prouct1 && res.json.data.product2

    if (hasAllData) {
      return res
    } else {
      throw new HttpError(500) // Maybe something better?
    }
  }
  return next(req)
}

You might be able to generalize this directive a bit, support something generically like the above snippet, etc.

Thanks for the feedback everyone!
I pushed the latest, I'll look to merge this in and tweet it on Monday.


Remove internal github requirements from requirements.txt

Fix #25.
Signed-off-by: Don Naegely<EMAIL_ADDRESS>

The base settings file includes chopauth as a requirement. @aaron0browne what are thoughts are maintaining this repository in general?

Thoughts:

I hope we will make pedsnet_harvest public, soon. That could replace some of the purpose of this repository.
On the other hand, pedsnet_harvest has its own special deviations from the pure omop repository, and it would be kind to leave a pure omop implementation up somewhere.
If we do want to maintain this, it needs a soup to nuts overhaul and a public dataset.


Add reading of PR title and body from branch config

Examples of PR title and body, both optional:
# .pr-train.yml

trains:
  Super duper train:
    - oleg-improve-readme:
        title: Readme improvements
        body: Now readme is the best
    - oleg-other-improvements:
    - oleg-improvements-combined:
        combined: true
        title: The big one # Works for combined branch too! And body is optional.

If title is not found in branch config, it will be read from git log just as before, along with body.
Resolves #6.

Hi @realyze, I can't assign you as a reviewer in this repo so you might have missed this one. When you have a chance, can you please take a look at this? Thanks!

Hello 👋  I realise this is 3 years old... but just wondering if there was a reason not to go ahead with this? I was considering forking and implementing something similar and came across this 😄

Yikes, three years 🙈 I'm so sorry for missing this.
So how would it work after the PR is already created and you want to update the description/title? What would be the source of truth? Would the config only be used when the PR is created?
I'm also a little bit hesitant to specify description in config like this. Usually you want a PR description to be a but more...uh, descriptive and not very short?

Hey, thanks for getting back to me! Yeah I'm not sure either now that I think about it actually

So how would it work after the PR is already created and you want to update the description/title? What would be the source of truth? Would the config only be used when the PR is created?

I was thinking that the yaml would always be the source of truth, so that whenever you want to update the title/description you do it via the yaml file and push. I guess the motivation for me was the idea of doing more of managing PR trains in my IDE.
But yeah it wouldn't be great if someone forgot they updated something on the UI instead and then pushed the old description from their yaml. Maybe by default it's only used when the PR is first created, and only overwrites existing stuff if another cli option is specified 🤷

I'm also a little bit hesitant to specify description in config like this. Usually you want a PR description to be a but more...uh, descriptive and not very short?

Yeah that's true, not the greatest experience to write markdown in a yaml config field


Update README.md

Just pointed to where it is at now.  Please merge ASAP as ve and openmbee are picking up steam, IMO.

Issue #47

@HuiJun: please review


Fix abi issue

Compile odex and vdex per the instruction set app uses.
Example :
When an app contains arm7 binaries, it compiles odex and vdex with arm7 instruction set.
I am on Arm64 device and trying to do odex patching an app which only contains arm7 binaries. I patched the odex but seems it didnt work, i troubleshooted a bit and found that there was a created a new folder at oat dir, arm64.
But it should compile odex vdex as arm7 not arm64.
Kindly check out the issue

Thanks for opening the issue! Can you give me more information to work with?

App's version
Android version
ABI
Device manufacturer (Pixel, Samsung, etc.)
ROM (Stock, AOSP, TouchWiz, etc.)
Original APK and modded apk (optional)
Logcat (optional)

App's version : 2.0.0 rc 1
Android version : 10
ABI : arm64-v8a, armeabi-v7a
Device manufacturer : Samsung
Rom : Stock
Original APK : use any apk which has armeabi-v7a binaries

https://github.com/giacomoferretti/odex-patcher/blob/main/app/src/main/java/me/hexile/odexpatcher/art/Art.kt
Field : CPU_ABI
It should not be like this as instruction set used by the app we are patching may be different.
Example :
some.apk -> libs/armeabi-v7a/*
In this case even if the device is arm64, the app will run on arm instruction set.
I hope my point is clear.
A possible solution : "base.apk" -> parent file -> + /oat -> arm64 or arm or x86 ...

Wait, you mean compiled ".so" libraries?

Wait, you mean compiled ".so" libraries?

Yes

Odex Patcher doesn't touch shared libraries, I don't understand what the problem is.
Can you give me the APK that you have problem with, so I can replicate it and fix it?

Okay here is a dummy apk.
System requirement : arm64 device
via-release_sign.apk.zip
Remove .zip extension and it will be installable

Now try patching the odex, you will see :
Before :
/data/app/mark.via.gp/oat/arm/.oat|.vdex
After :
/data/app/mark.via.gp/oat/ ->
arm64/.oat|.vdex
arm/.oat|.vdex
Here the arm64 folder contains patched oat, while the app uses arm one.
Reason : the app is using arm native binaries and because of that it will compile oat to same.

I would have sent a PR with fix for these issues but the project is in kotlin and i am a java person😄.
I am not that good with kotlin, so i decided not to ruin your code.

Now try patching the odex, you will see : Before : /data/app/mark.via.gp/oat/arm/.oat|.vdex
After : /data/app/mark.via.gp/oat/ -> arm64/.oat|.vdex arm/.oat|.vdex
Here the arm64 folder contains patched oat, while the app uses arm one. Reason : the app is using arm native binaries and because of that it will compile oat to same.

I have never encountered such a case, but now I understand better. I will try as soon as possible, thank you!

I would have sent a PR with fix for these issues but the project is in kotlin and i am a java personsmile. I am not that good with kotlin, so i decided not to ruin your code.

Don't worry, currently the code is very messy, so it's not a problem if it's not good, in case I'll fix it later. :wink:

Thanks!
I hope there will be a quick fix and update ;)

I have found the problem and am starting to write the fix. I need to rewrite the ISA "detection".

Yeah, removing dependence on CPU_ABI would fix it.
CPU_ABI doesn't hold any importance except for setting ISA, ISA can be known from :
"base.apk" -> parent file -> + /oat -> arm64 or arm or x86 ...

I don't want to go that way, because in the rare case that the app is not already optimized, there is no oat folder. I would check if has native lib, like Android does, and if not, fallback to CPU_ABI.

Okay, that seems plausible ;)

Any updates?

Okay!
Have good time studying :)


Update readme.md

Added Globol company website that's taking part in Hacktober fest 2021

The other companies are sorted alphabetically. Could you please use alphabetic sort ordering, too?


Added University of Cambridge

I added a new university file and details about the University of Cambridge.

https://www.dns.cam.ac.uk/about/floss.html is also interesting.


Hyperparameter settings for FB15K_237

Are there any other hyperparameter settings for different datasets to reproduce their performance in the original paper,such as FB15K_237? I tried to use the hyperparameters for FB15K to train FB15K_237 but the results are far below the benchmarks. The process of adjusting parameters is very time-consuming so I want to ask if anyone can provide some settings.
Thanks.

Hi, @Diqingling. Looks like the original FB15K_237 paper has no code published and it does not mention things like learning rate for model E and DistMult they used either. In this case, we encourage users to explore hyperparameter tuning and you can find how-to in here. Meanwhile, we are extracting the golden hyperparameters for ConvKB which also used FB15K_237 and of course, nothing stops you from extracting them yourself and create your own custom yaml file.

Thank you. I’ll try to tune the hyperparameters. Another question is that since the hyperparameters in the yaml files don’t fit dataset FB15K_237, I used them to train models with FB15K as well. However, the filtered hit-10 result of TransE is around 60.2% ,the benchmarks given in RotatE   is 74.9%. So I want to ask if there is something wrong with my training process or with the hyperparameters settings?

Thank you. I’ll try to tune the hyperparameters. Another question is that since the hyperparameters in the yaml files don’t fit dataset FB15K_237, I used them to train models with FB15K as well. However, the filtered hit-10 result of TransE is around 60.2% ,the benchmark given in  RotatE is 74.9%. So I want to ask if there is something wrong with my training process or with the hyperparameters settings?

Probably there was nothing wrong with your training process coz the best result we can get so far is 60.7%:

Model
MR/FMR
MRR/FMRR
HIT-1
HIT-3
HIT-5
HIT-10

TransE
215.1193/77.7292
0.1921/0.3413
0.0852/0.2056
0.2176/0.4050
0.3003/0.4921
0.4206/0.6070

TransE is one of the simplest models and if there is an implementation bug, it shall be easy to spot. Can you compare hyperparameters set in TransE.yaml with those displayed in your "Global Setting" log during the training?

I checked the hyperparameters in the log file and they match with the settings in TransE.yaml. The difference between 60.2% and 60.7% may be normal volatility during training process. However they are both far below the results given in HoLE paper ,where the filtered hit-10 is 74.9%. Does it mean the hyperparameters in TransE.yaml may not be golden hyperparameters? What’s more ,how do you get the hyperparameters in the exsisting yaml files? Using hyperparameter tuning module in the project or taking them from the original model papers directly?

All hyperparameters are derived from the original paperswithcode and there might be a slim chance that some authors later corrected errors in their published work, which have not been incorporated in pykg2vec. For the previous tensorflow implementation, you can see HIT-10 is 66% from that table. Hi, @louisccc, would you like to weigh in and share some history about this?


[SEO] Meaningful slug for profile page, and other pages later on like job posts

Now everyone's profile pages are with slug using the uuid, i.e. /profile/[uuid], which isn't a great thing for SEO
Reference: https://yoast.com/slug/
We may consider adding more meaningful things and keyword in the slug, simply can just use /profile/[username] like Linkedin
Same thing goes to post detail page if we want to create a separate detail page for more detail
This should be done ASAP to keep all of our links stable, and better for SEO ranking

You've got a point, and I believe this will make the link more shareable.
Maybe we can use the username part of the email address by default. Then, at some time in the future, we can allow users to edit their custom urls in profile setting just like LinkedIn?

Aggar

Better to ask user to input a username when register and make it permanent, otherwise the seo score of that link will be lost
e.g.

original slug: /profile/tommyttf
user change username: /profile/tommyttf0123
then:
/profile/tommyttf -> 404 but may already got some seo score during 1, huge damage to our site as it become 404
/profile/tommyttf0123 -> a 'new' url to google, need to wait for google bot to crawl again

Although can set redirect and sth like <link rel="canonical" href="XXX">, this require extra handling in server
So now we should first ask user to fix their username

Better to ask user to input a username when register and make it permanent, otherwise the seo score of that link will be lost
e.g.

original slug: /profile/tommyttf
user change username: /profile/tommyttf0123
then:
/profile/tommyttf -> 404 but may already got some seo score during 1, huge damage to our site as it become 404
/profile/tommyttf0123 -> a 'new' url to google, need to wait for google bot to crawl again

Although can set redirect and sth like <link rel="canonical" href="XXX">, this require extra handling in server
So now we should first ask user to fix their username

Can do username is unique in db.


AddOrUpdate() method for entity collections

Follow on from issue #189
Add support for AddOrUpdate() method on entity collection. If the entity passed in does not yet have an ID, treat it as a new entity; if it does have an ID treat it as an update for an entity with that ID.

Just pushed a fix for this - let me know if you find any problems with it.


Feature/merge transformation

Merge transformation working for xarray as a transformation

Codecov Report
Patch coverage: 90.54% and project coverage change: -0.24% :warning:

Comparison is base (d5be964) 96.88% compared to head (19d4382) 96.65%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #58      +/-   ##
===========================================
- Coverage    96.88%   96.65%   -0.24%
===========================================
  Files           40       44       +4
  Lines         5235     5413     +178
===========================================
+ Hits          5072     5232     +160
- Misses         163      181      +18

Files Changed
Coverage Δ

polytope/datacube/backends/mock.py
89.13% <75.00%> (ø)

polytope/datacube/backends/xarray.py
91.52% <80.00%> (ø)

polytope/datacube/backends/datacube.py
91.66% <81.81%> (ø)

...tacube/transformations/datacube_transformations.py
86.11% <86.11%> (ø)

...lytope/datacube/transformations/datacube_cyclic.py
90.00% <90.00%> (ø)

...lytope/datacube/transformations/datacube_merger.py
94.87% <94.87%> (ø)

polytope/datacube/__init__.py
100.00% <100.00%> (ø)

polytope/datacube/datacube_axis.py
88.37% <100.00%> (+0.42%)
:arrow_up:

...ytope/datacube/transformations/datacube_mappers.py
98.51% <100.00%> (ø)

polytope/engine/engine.py
69.23% <100.00%> (ø)

... and 19 more

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


Pagination doesn't handle short data

When using DisplayStrategy::Pagination with row_count larger than the actually data size, the code panicked at table_content.rs:495:47, with messages like following:
range end index 9 out of range for slice of length 8

Wondering if the table should just render the excess rows empty by default?
Thanks for the great work!

Thanks for reporting the bug.
Have you tried just not implementing the row_count method, when you really don't know how many rows there are? When this method is implemented the code assumes that this is the actual size of the data. If you don't know then you can return None from this method which is the default behavior.

Thanks @maccesch! I believe I failed to provide enough details. So this is my simplified data provider:
#[derive(Default, Clone)]
pub struct SimpleProvider {}

impl PaginatedTableDataProvider<user::Model> for SimpleProvider {
    const PAGE_ROW_COUNT: usize = 20;

    async fn get_page(&self, page_index: usize) -> Result<Vec<user::Model>, String> {
        match page_index {
            0 => Ok(vec![
                user::Model{ username: "abc1".to_string(), email: "abc1@def.com".to_string(), password: "password".to_string(), bio: None, image: None},
                user::Model{ username: "abc2".to_string(), email: "abc2@def.com".to_string(), password: "password".to_string(), bio: None, image: None},
            ]),
            _ => Ok(vec![])
        }
    }

    async fn row_count(&self) -> Option<usize> {
        Some(2)
    }
}

In the component I use a local resource to avoid SSR of the table:
    let provider = create_local_resource(
         || (),
         |_| async move {SimpleProvider::default()});

The in the view macro the table is created like following:

                        <Suspense fallback=move || view! {
"Loading Users"
}> {
                            move || match provider.get() {
                                None => view! { <Spinner size=SpinnerSize::Medium/> }.into_view(),
                                Some(rows) => view! {

                                        <TableContent
                                            rows
                                            scroll_container=container
                                            display_strategy=DisplayStrategy::Pagination {
                                                row_count: 10,
                                                controller: pagination_controller,
                                            }
                                        />

                                }.into_view(),
                            }
                        } </Suspense>

From the browser console, I'm getting the complaint like:
panicked at leptos-struct-table/src/components/table_content.rs:495:47:
range end index 10 out of range for slice of length 2

What did I do wrong?

BTW, if I simply let the table be rendered on both sides (CSR and SSR), like staging the provider with:
let provider = SimpleProvider::default();

Then invoke TableContent in the view! macro without differentiating:

                                        <TableContent
                                            rows=provider
                                            scroll_container=container
                                            display_strategy=DisplayStrategy::Pagination {
                                                row_count: 10,
                                                controller: pagination_controller,
                                            }
                                        />

It'll trigger the infamous hydration bug like the following:
panicked at /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/leptos_dom-0.6.7/src/html.rs:1392:13:
assertion `left == right` failed: SSR and CSR elements have the same hydration key but different node kinds. Check out the docs for information about this kind of hydration bug: https://leptos-rs.github.io/leptos/ssr/24_hydration_bugs.html
  left: "TH"
 right: "TR"

That's what led to use create_local_resource to disable the SSR in the previous comment. Thanks for looking into it!

Interesting! Thanks for the details. I'll try and reproduce it.

This has been fixed by #25


#96 Allow edit CurrentDay from external code

Fixes #96

Thanks for the pull request.  However I think your changes are more complicated than they need to be.
I have fixed this issue now.  Can you check that my fix does what you need it to?

#106 Seems fine, I will test it this evening. CurrentDay is in this version indeed a bit to complex.

You guys are amazing.  I just ran into this myself and I'm thankful the fix is inbound.

@danheron Yes #107 does fix my issue as well!


Initial DB Table

Description
Changes proposed in this pull request:

Initial Schema for Kyma Bindings,
go structs and logic.

Related issue(s)

#1198 #284

consider adding Instance ID


A string lookup should be provided for macros

Right now macros are organized in an immutable array, but it can be helpful to look them up by name without just evaluating them blindly.
We should consider providing a lazily-created ImmutableDictionary of them in addition to the array.
This came up when manually translating PortAudio's macro-style enums, which do not have identifying prefixes and had to be listed manually. (EG: PaSampleFormat)
On the flip side however, it might be kinda non-obvious why we offer both (iterating an array is valuable for certain libraries, IE: Win32.) Maybe the dictionary should only be internal?

Mochi.DearImGui's ImVersionConstantsTransformation would also benefit from this.


Proposal for useful distinction between "Text" and "String"

We've had the two datatypes text and string for quite a while but haven't really made a lot of use of it.
Distinction in elasticsearch
Now that we ware using elasticsearch for answering more and more of our queries, this distinction becomes more necessary. Elasticsearch has two types:
Keyword: Example<EMAIL_ADDRESS>will match for<EMAIL_ADDRESS>but basically nothing else. I.e. this is for exact match for exact product names (model names), ids, emails, etc.
Text: Example I've sent an email to<EMAIL_ADDRESS>Is tokenized at import time, will match for individual words, such as "email", "john", etc. Used for full-text search.
Proposal
I'm proposing to align our datatypes to the ones above, so that

string behaves like ES Keyword (exact matches for IDs, Emails, etc)
text behaves like ES Text (fuzzy* matches, full-text search, etc.)

* = Note that fuzzy does not mean vector in this case. The entire proposal is only about string/text matching behavior, vector matching is not affected.
cc @bobvanluijt @fefi42 @laura-ham

I think this makes sense to stay close at the definitions of elastic.
We have to be aware of some side effects of text though. I think during tokenization the @ and . in<EMAIL_ADDRESS>are removed, however such symbols can bear meaning and create context. Especially in cases like @ and #. Would the missing of such characters effect the vector creation?

@fefi42
Thanks for your feedback. Some answers:

Generally I think it's OK to have semantic meaning get lost through tokenization when the text property is used. If the user knows that their punctuation is semantically relevant, they should use a string field instead.
Elasticsearch applies the same tokenization at search as at index time. So if a field is imported as text and therefore the email would be indexed as john doe com, the search query<EMAIL_ADDRESS>would also be transformed. Thus the user is able to find the email by both searching for<EMAIL_ADDRESS>and by searching for john doe com. If the type was string they'd have to match it exactly.
In Vector creation we currently only support single words, so we need to strip all non-alphanumeric characters before creating a vector anyway. Not that as of now, text and string behave identically when talking about vectors. This issue is only about string/text matching.

What if we only would go for "Weaviate string == Elastic text"? That we only store text entities because we want to double down on the fuzzyness we don't need to move in the direction others already have solved...

I think not being able to filter by something exact like an email address or an ID would lead to a frustrating user experience.

I think not being able to filter by something exact like an email address or an ID would lead to a frustrating user experience

That makes complete sense to me.

Note: This will become the default behavior in 0.20.x


consider using xmlrpc module?

The xmlrpc module includes serializer/deserializer objects that can make for simpler (and probably more robust) logic when communicating with IFTTT.  I used them in my earlier port of captn3m0's ifttt-webhook (see server.js for usage example).

Is this still an active issue?

Possibly still relevant, but wasn't ever more than a suggestion.


INPUT statement from the command line does not work correctly

Not sure whether this is a quirk of the language or a bug I've introduced. Check against CP/M version.

Looks like a quirk of the Z80 version - BUFFER is used to store the results of INPUT as well as the tokenised command line string. So after XEQ finishes executing the INPUT statement on the command line, the command line is trashed, causing the syntax error.

Just tested on my Spectrum Next version - it has the same issue, so thankfully not something I've introduced with the new codebase. Will still need to check the CP/M version though suspect it will have the same issue as it is the same codebase.

Yep, same in CP/M version, so going to mark this as 'Won't Do'.


Fix Async deprecation warnings

The API for fill was changed in v0.17.0. The implementation for fill calls fill_exn in v0.17.0 so there is no difference in implementation now https://github.com/janestreet/async_kernel/blob/v0.17.0/src/ivar0.ml#L303-L317 plus the older doc strings for v0.16 is the same as the new one on fill_exn. It isn't clear whether there is just a bug fix or some behaviour change as there is no entry in CHANGES.md.

Of course v0.17.0 requires OCaml 5.1 https://github.com/janestreet/async_kernel/blob/v0.17.0/async_kernel.opam#L13-L18 so CI should skip supporting any OCaml version that Async doesn't support.

I'm hesitant to make this change since it makes gluten-async depend on 5.1, right?
how about we just disable warning 3 locally?

Ignoring the warnings is a better idea, I've update the PR.

Thank you!

ooops I pressed merge too quickly. I disabled the deprecations locally in https://github.com/anmonteiro/gluten/commit/bdb7dc480e891013694148907032616e3289a210
that's a bit more explicit, which I prefer


Bug: Swipe not working if you swipe it fast enough

Type
UI-related issues
Bug description
On the image viewer, if you swipe it fast enough the swipe will not working until wait a couple of second. I suspect it's waiting for the swipe animation to finish first OR waiting download the next image to finish.
Steps to reproduce

View an image
Swipe it fast enough

Android version
13
App version
1.4.0
Screenshots or videos
https://github.com/nullxception/boorusphere/assets/16524713/5ad2100a-f73b-4e3b-b7c7-a8f9931abc2d
Solution
No response
Additional context
No response
Acknowledgements

[X] I have searched the existing issues and this is a new and no duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I filled out all of the requested information in this issue properly.

Pretty sure it's device issues, it works perfectly fine on my phone.
https://github.com/nullxception/boorusphere/assets/58150791/6b35cf10-081b-4be8-84e5-d589f044d03d


Refactor else branches

Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

LGTM

LGTM: @cpuguy83 do you want your comment to be addressed before merging?

All good. someone can fix later, good beginner issue.

@cpuguy83 I'll open a beginner issue then..


how to have self.__WB_MANIFEST available in another file

Library Affected:
InjectManifest plugin
Browser & Platform:
Latest.
Issue or Feature Request Description:
@jeffposnick @philipwalton
I am using InjectManifest plugin. All seems great. I have the latest workbox plugin which means InjectManifest has childCompiler and all that stuff already implemented.
Now, what I need is I want self.__WB_MANIFEST to be also available in one of my other files such as app.js which is the entry point. So the flow is like this: app.js is the main entry in webpack, whatever that file imports gets built and in the plugins of webpack, as I said I also have InjectManifest plugin. What I need is that if in app.js, I write js console.log(self.__WB_MANIFEST), I want it to print a manifest too.
The reason is that I want to use that manifest for other situations as well in my src code. I found webpackCompilationPlugins this option, but I couldn't make it work as i don't have manifest in one of the plugins I might put in that option.
ONE POSSIBLE SOLUTION:
const manifest = [];  // this code is somewhere at the top of the webpack.
manifestTransforms: [
     (manifestEntry) => {
            manifest = manifestEntry
     }
],

webpackCompilationPlugins:[
      {
            apply (compiler) {
                 compiler.hooks.emit.tapPromise('bla', compilation => {
                      console.log(manifest); // I have the manifest.

                    // I can loop through the compilation.assets and get js source file of main.js and replace
                    //self.__WB_MANIFEST  with the above console.log(manifest);
                 })
             },
       },
 ]

The actual thing is, hooks.emit.tap never runs.  apply function runs, but not the hooks. and emit hook is the one i really need. I tried shouldEmit , but still no luck. Any idea? make hook works, but at that time, i don't have manifest.  All the hooks are running including make, but after make hook, none of them really get run.

Does this example help?
https://github.com/GoogleChrome/workbox/issues/2383#issuecomment-593049733

webpackCompilationPlugins:[
                {
                    apply (compiler) {
                        compiler.hooks.emit.tapPromise('ManifestWorkboxWebpackPlugin', async compilation => {
                            console.log("FIRST ONE");
                        })

                    }
                },
            ]

console.log(FIRST ONE) never gets printed while building the project. That's the issue I guess before we move into another issue.

The fix that was just merged in https://github.com/GoogleChrome/workbox/pull/2400 may also be relevant to this use case.
I'd imagine we'll cut a v5.1.0 release within the week that includes it.

This might be it. what do you suggest me to do for now to figure this out ?

I added this code in inject-manifest.js in node_modules.
if (Array.isArray(this.config.webpackCompilationPlugins)) {
      console.log("this is array");
      for (const plugin of this.config.webpackCompilationPlugins) {
        console.log(plugin);
        plugin.apply(childCompiler);
      }
    }

but still, my emit hook not gets called. :(

I put the apply plugin out of the webpackCompilationPlugins option. as just a ordinary plugin and its hooks start working. I guess I will leave this like this. I am just curious if you can think of any other solution than that for just putting self.__WB_MANIFEST in my other file , app.js. Is my way a good way in your opinion from the perspective of workbox ?

Let's move this conversation over to https://github.com/GoogleChrome/workbox/issues/2383#issuecomment-598370215, which tracks an "official" solution.


Oops, an unexpected error occured! error: Error validating: The relation field user uses the scalar fields userId. At least one of those fields is required.  Hence the relation field must be required. report id 13238

Oops, an unexpected error occured!
error: Error validating: The relation field `user` uses the scalar fields userId. At least one of those fields is required.
Hence the relation field must be required as well.
  -->  schema.prisma:12
   |
11 |   id                        Int               @default(autoincrement()) @id
12 |   user                      User?             @relation(fields: [userId], references: [id])
13 |   userId                    Int

Hi @JeevantheDev - your issue title indicates this is connected to error report 13238 - which I could also find in our system and matches the error you are posting here.

Can you maybe post the complete output you are getting when running the CLI command?
I also see from the error report that you are using CLI 2.1.1. That is reeeeeeaaaaaally old. Can you please upgrading your CLI and Prisma Client to a more recent version? Thanks.

Ya ya I got it @janpio I have to upgrade the CLI.
Thanks for reply.


[Feature Request] Enhance the KFServing session affinity example with dynamic assignments

Is your feature request related to a problem? Please describe.
The session affinity tutorial uses user hashes to consistently assign users to versions. However, this means the same set of ensures will end up seeing the candidate version in each experiment until version promotion occurs. This is not desirable.
There needs to be some type of rotation / balancing so that users assigned to the candidate version is different (randomized) across experiments.
Describe the solution you'd like
Use envoy filtering to automatically change the set of users assigned to a specific version at the start of each experiment.
The idea is that, if there's a frontend service (UI) and a backend service (ML model), the frontend must be able to generate the user hash (statically; forever the same user hash for a given user), but each time a new candidate model  is introduced in the backend, the user assignment between baseline and candidate is automatically changed.
Why is the feature useful for Iter8 users?
This provides fairness with session affinity.
Does this issue require a design doc/discussion? If there is a link to the design document/discussions, please provide it below.
Yes, a more detailed example will follow.
How will this feature be tested?

[ ] Session affinity e2e test will continue to be used for testing this feature.

How will this feature be documented?

[ ] Session affinity tutorial will evolve and will include this fairness documentation.

Obsolete.


Add requirements packages version

Fixes issue #104.

@giancastro Out of curiosity, have you experienced any specific problems relating to particular packages here? Just so that I know what we need to keep an eye on in future.

@ianthomas23, I don't remember which requirement package was, but I had a break situation involving a dask update.


Fix issues caused by reachability analysis of this.foo(...) like calls.

Fixes #33582.

@typescript-bot run dt
@typescript-bot perf test this


Add data on nourishment of children under 5.

Updated view of section on poverty, safe drinking water and, now, child nourishment
Here are a couple of screenshots of the "Human Development" section with percent of children under 5 who are malnourished. Note that the alignment of the first row (the one with poverty stats) matches the alignment of the row above it, which is not captured in the screenshot.
Kaski district

Solukhumbu district

looks good! pls push it to master.


Start Time and End Time time pickers are not working in Firefox

Currently, in the createEvent.html file, the user is not able to click on the time pickers to input a start time and an end time. In other words, upon clicking the icons, nothing happens.

 Start Time and End Time time pickers are not working in Firefox


Added Preloading page #Issue267 GSSOC 20223

Description
This PR fixes # pre loader property
Notes for Reviewers
Do check it out if any changes required .
Under GSSOC 2023

Thanks @ManishaSwain8 , we will review and merge it soon!


Implement YEAR function

PR Details

Description
Returns the year corresponding to a date. The year is returned as an integer in the range 1900-9999.
Syntax
YEAR(serial_number)
The YEAR function syntax has the following arguments:

Serial_number    Required. The date of the year you want to find. Dates should be entered by using the DATE function, or as results of other formulas or functions. For example, use DATE(2008,5,23) for the 23rd day of May, 2008.

Related Issue
Fixes #1006
Important: pull request #1003 and #1005 must be merged first!
Motivation and Context
This helps with Excels from third party, where the YEAR function is frequently used.
How Has This Been Tested
Added tests to calc_test.go
Tested on:

OS: Archlinux 5.13.10-arch1-1
WPS Spreadsheets (version wps-office <IP_ADDRESS>02-1)
LibreCalc (version libreoffice-fresh 7.1.5-2)

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Codecov Report

Merging #1007 (81e73d2) into master (dca03c6) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #1007   +/-   ##
=======================================
  Coverage   97.52%   97.52%
=======================================
  Files          29       29
  Lines       11222    11240   +18
=======================================
+ Hits        10944    10962   +18
  Misses        154      154
  Partials      124      124

Flag
Coverage Δ

unittests
97.52% <100.00%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

calc.go
97.95% <100.00%> (+<0.01%)
:arrow_up:

Continue to review full report at Codecov.

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


Support for RFC 373 is missing (Interfaces implementing other interfaces)

Summary
This project does not implement RFC 373 (Interfaces implementing Interfaces)
Version
2.4.6
Description
When trying to parse a .graphqls schema with an interface implementing another interface, the parser fails with the error Unsupported token `implements`

Hi 👋 , I just made a quick test and it looks like this is already working in dev-3.x: https://github.com/apollographql/apollo-android/pull/2851
It parses schema and generates models. The code to detect type conditions for fragments seems ok as well.
The GraphQL type hierarchy not being mirrored in the Kotlin type hierarchy, I think that's about everything that is needed?
Is there any chance you could try one of the 3.0.0-SNAPSHOT to make sure it's working as expected? If everything looks good, this should be reasonnably possible to backport to 2.x.

Hi 👋 , I just made a quick test and it looks like this is already working in dev-3.x: https://github.com/apollographql/apollo-android/pull/2851
It parses schema and generates models. The code to detect type conditions for fragments seems ok as well.
The GraphQL type hierarchy not being mirrored in the Kotlin type hierarchy, I think that's about everything that is needed?
Is there any chance you could try one of the 3.0.0-SNAPSHOT to make sure it's working as expected? If everything looks good, this should be reasonnably possible to backport to 2.x.

Well, my original project uses the gradle project so I had to create a new one, but yes, it parses correctly @martinbonnin

Well, my original project uses the gradle project so I had to create a new one, but yes, it parses correctly @martinbonnin

Thanks for confirming that, I'll backport for the next 2.x release

Thanks for confirming that, I'll backport for the next 2.x release

The fix is now in main so you can test with SNAPSHOT when they come up in ~30min. I'll make a release on monday.

The fix is now in main so you can test with SNAPSHOT when they come up in ~30min. I'll make a release on monday.


Connection refused Error in Github collector

Hi,
I am facing connection refused error when running git-hub collector as below
I/O error on GET request for "https://api.github.com/repos/capitalone/Hygieia/commits?sha=master&since=2016-08-31T12:00Z":Connect to api.github.com:443
Any idea to resolve this ?
Thanks
Jay

Hi,
did you fix this?I am facing the same issue.

Hi,
It's resolved by opening firewall to url api.git hub. Com.


Change "update package" and install to not pin unchanged versions

this new version does not pin unchanged depedencies in the resolver phase.
Instead we introduce "preferred versions" and try these versions first.
/cc @mrinaldi @dnauck

This allows us to "update package" in much more scenarios since we allow more possible resolutions. In order to keep the lock file as stable as possible we probe the old locked versions of unrelated packages first.
@mrinaldi I also added your new test case which didn't work before.

@dnauck I added you since I remember you reporting issues with updating transitive dependencies. This would work now since we don't pin the direct dependencies anymore

Very cool, indeed.
There's one downside though.
This is how long it takes to do a selective update now:
4 minutes, 48 seconds - ready.
Comparing to the 2.9.0 version:
43 seconds - ready.
and to the 2.5.0 version:
15 seconds - ready.
Seems that this lag is due to fetching all versions for every package of the whole graph.
Version 2.9.0 would not fetch versions when the package is pinned (I've a lot of pinned packages)
Version 2.5.0 would fetch versions but only for the packages from the updating package graph.
So you know, my paket.dependencies has 102 packages and 51 of them are pinned.

Yes I knew this would happen, and I already have plans to tackle perf.
At this point I just wanted to make sure it's "correct" and that I didn't
oversee something important.
On Oct 6, 2015 9:01 PM, "Marcio Rinaldi"<EMAIL_ADDRESS>wrote:

Very cool, indeed.
There's one downside though.
This is how long it takes to do a selective update now:
4 minutes, 48 seconds - ready.
Comparing to the 2.9.0 version:
43 seconds - ready.
and to the 2.5.0 version:
15 seconds - ready.
Seems that this lag is due to fetching all versions for every package of
the whole graph.
Version 2.9.0 would not fetch versions when the package is pinned (I've a
lot of pinned packages)
Version 2.5.0 would fetch versions but only for the packages from the
updating package graph.
So you know, my paket.dependencies has 102 packages and 51 of them are
pinned.
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/pull/1114#issuecomment-145966259.

Looks correct to me :+1:

@mrinaldi could you please test again. just be pretty fast now.

it's in 2.10.0-alpha

Much better now:
41 seconds - ready.

Still much slower than expected. Is there a chance I can reproduce your
sample?
On Oct 7, 2015 19:46, "Marcio Rinaldi"<EMAIL_ADDRESS>wrote:

Much better now:
41 seconds - ready.
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/pull/1114#issuecomment-146274857.

The NuGetV2.GetVersions seems to be causing the problem.
Parallelizing the calls apparently floods the server.
Some calls are taking 2, 3x more time to complete comparing to the exactly same call when not parallelizing.
Using only tryGetPackageVersionsViaOData dropped the total time to 14 seconds - ready.
I'm using ProGet 3.6.1, BTW.

Mhm maybe we need a smart way to filter unsupported api calls.
On Oct 7, 2015 20:11, "Marcio Rinaldi"<EMAIL_ADDRESS>wrote:

The NuGetV2.GetVersions seems to be causing the problem.
Parallelizing the calls apparently floods the server.
Some calls are taking 2, 3x more time to complete comparing to the exactly
same call when not parallelizing.
Using only tryGetPackageVersionsViaOData dropped the total time to 14
seconds - ready.
I'm using ProGet 3.6.1, BTW.
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/pull/1114#issuecomment-146281620.

I mean I already tried but didn't really find a smart way

The problem is not exactly unsupported calls, but the tryGetAllVersionsFromNugetODataWithFilter which is supported but takes around 2 seconds in ProGet.
For example, FindPackagesById()?id='Microsoft.Bcl.Build' takes 0:00:00.252 and Packages?$filter=Id%20eq%20'Microsoft.Bcl.Build' takes 0:00:02.243.

Of course, Async.Choice chooses the first call to return, but the Packages?$filter=Id%20eq%20'Microsoft.Bcl.Build' call definitely takes a significant amount of resources in ProGet, slowing down all other calls.

Any ideas are appreciated.
On Oct 7, 2015 20:32, "Marcio Rinaldi"<EMAIL_ADDRESS>wrote:

Of course, Async.Choice chooses the first call to return, but the
Packages?$filter=Id%20eq%20'Microsoft.Bcl.Build' call definitely takes a
significant amount of resources in ProGet, slowing down all other calls.
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/pull/1114#issuecomment-146286938.

I'm working on it, will send a PR when I'm done.


Improve connstring parsers

Our connstring parsers are currently too simple. We should try to adhere to the connstring specs used by Postgres and Mongo - for example, every part of the connstring is optional, so postgres:// is a valid connstring, as is postgresql://user@host.
Let's make some improvements so that these specs are at least more or less followed. Let Postgres and Mongo provide the defaults if these are not provided.

MongoDB connstrings
LibPQ connstrings

This is made irrelevant by #54


add value/data/seq properties to message

related to: https://github.com/Azure/azure-sdk-for-python/pull/24259

test run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1782646&view=results


Python projects' README.rst: Local referencing of image location now presents broken image

Describe the bug
Several projects that I am contributing to, I have been able to use a local reference to an image when adding to README.rst. However, recently within the last couple of months, local referencing no longer work.
Expected behavior
Images should be viewable within README.rst either if locally or remotely referenced, as they had been viewable in 2018 March.
To Reproduce
For example, Pypi.org project requests_mv_integrations:
In this project's README.rst images are referenced locally:
.. image:: ./images/requests_mv_integrations.png

Images are viewable in README.rst on Homepage Github:
https://github.com/TuneLab/requests-mv-integrations/blob/master/README.rst
However, now these same images are broken on Pypi.org:
https://pypi.org/project/requests-mv-integrations/#description
And yes, locally referenced images have been included in MANIFEST.in:
https://github.com/TuneLab/requests-mv-integrations/blob/master/MANIFEST.in
recursive-include images *.png

This was not the case in 2018 March the last time I did an upload to Pypi.org
Additional context
I investigated project requests2 and it images are still viewable, however, this projects README.rst is using external referencing of images. This is not convenient and not reasonable because typically MANFEST when :
https://raw.githubusercontent.com/requests/requests/master/README.rst
.. image:: https://raw.githubusercontent.com/requests/requests/master/docs/_static/requests-logo-small.png

@di would you be able to look into / respond to this? Thx :)

PyPI does not and has never served images from the contents of uploaded distributions. I'm not sure how it would have been working before.
The only way to have images displayed in the description is for those images to be hosted somewhere that our image proxy (warehouse-camo], based on camo] can retrieve it.

Images must be externally hosted, and this requirement has always existed. We don't expose individual files within a distribution, so this feature is not really possible, either. Sorry!


Bug report: Persisting connection issue

Description
We noticed that a Persisting connection is dropped after 90 days? So in fact, thats not permanent? Login Status looks like it is connected bute connections fails. After logout + login it works fine.
Steps to reproduce
Login
wait 100 days
try to use m365cli command
Expected results
Persisting connection should be persistend
Actual results
after more than 90 days of login, a script run fails
Diagnostics
No response
CLI for Microsoft 365 version
<IP_ADDRESS>
nodejs version
16.13.1
Operating system (environment)
Windows
Shell
PowerShell
cli doctor
No response
Additional Info
No response

@jdaehler thank you for reaching out to us and sorry to hear that you're running into trouble. After 90 days the refresh token expires which is why you need to login again and there's nothing we can do about that, unfortunately. That said, we should be handling it better rather than showing status as logged in but meanwhile throwing errors on all connections. We'll fix it.

@waldekmastykarz would the fix involve trying to fetch the token and show the status accordingly ? I don't know/couldn't find a way to check the expiry of a refresh token.

Unfortunately, there's no way to check the validity of a refresh token. 90 days is default, but organization can configure it to be different if I'm not mistaken. One improvement that we could consider, is to extend m365 status so that it always receives a fresh token to verify that the user is still connected and the connection is valid, rather than that we connected in the past and have connection information stored, but it can't be used in any way. We could also make an assumption that if the access token is older than 90 days, we won't be able to reconnect, but I wonder if that would work in all cases.

@waldekmastykarz you cannot configure the lifetime of a refresh token (more on: https://docs.microsoft.com/en-us/azure/active-directory/develop/refresh-tokens). It is correct that the default lifetime is 90 days. However there are some cases (as pointed out in the page linked) where a refresh token can be revoked; an admin or user can revoke all their refresh tokens.
AFAIK the best implementation would be to handle a rejection in case of a refresh token expiry; and the best way to do that is to use the m365 status for it, and if we are rejected present let a user know and provide them with the sign in experience like we do when you use the m365 login command?

The trick is that currently m365 status uses information about the token to display the status, without requesting a new token. So if we're to follow your suggestion, we should ignore the token and always try to get a new use when calling m365 status. That way we can verify that we're still connected. If that fails, then we know the connection expired and we can reset the connection status (basically calling logout; we could also make it explicit that the connection expired, so introduce a third state) and then showing that the user is disconnected.

@waldekmastykarz  I can try and work on this one.

Thanks @vipulkelkar!


display is ada accessible if it is a property of the event

ada_accessible: true

@desdemonhu, can you take care of this? it's ada_accessible: true


Changing from using environment variables to a config.json file

I don't believe using the global system environment variables is the best way to go about storing and reading the API keys for the program.
Many users struggle with this and also as someone who plays around with a lot of different AI tools and programs, especially given OpenAI's project-based API keys this avoids having to change environment variables when switching between programs/tools.

This does seem easier. I figured the main reason not to do this was to avoid accidentally committing the keys, but I guess if its in the gitignore then its pretty safe. @kolbytn what do you think?

Ya this may be easier for users. @SamKemp can you change the name of config to "keys" or "secrets"? Also, please have the code check for the env var is the key is not in the file so that it is backwards compatible.

Renamed config.json/config.example.json to keys.json/keys.example.json
Added check for environment variables if key is not found in keys.json, as backwards compatibility

I've not been able to test it right now, as I'm away from my main machine but I believe that code should work.

Thanks sam! Closing here, moved to our own branch #100


Update MNE testing data version

To version 0.65

Usually people just do this as part of the PR that actually uses the data, but this should work too. Might even avoid a rebase problem if the NK PR takes a while

That’s why I did it.
I still need to work on the NK PR. I don’t have much time so I wanted to push things as soon as I get them done.

On 9 May 2019, at 17:50, Eric Larson<EMAIL_ADDRESS>wrote:
Usually people just do this as part of the PR that actually uses the data, but this should work too. Might even avoid a rebase problem if the NK PR takes a while
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/mne-tools/mne-python/pull/6289#issuecomment-490960634, or mute the thread https://github.com/notifications/unsubscribe-auth/ABCJDAZ556I2XVLN5D3A47DPURB5PANCNFSM4HL3X4IA.


S3 sometimes returns etags with extra " characters

We have a CI build that uses a docker image with 'motoserver/moto:latest'. Sometime between November 2nd and November 9th, we began getting an error that Invalid base 16 character: '"'.
Looking in the moto UI, I can see that some objects have an etag with extra quotes around them. Changing our build to use the docker image 'motoserver/moto:2.2.12' seems to have fixed our issues for the time being.

Hi @psxpaul, which system is raising this error?
Any chance you have a reproducible test case? I can't remember any changes to the way etags are handled in the last 2 weeks

I just pulled master locally and started moto server. Then I tried the below aws cli commands:
$ aws s3api --endpoint-url http://localhost:5000 --region us-east-1 create-bucket --bucket test-bucket-one
$ aws s3api --endpoint-url http://localhost:5000 --region us-east-1 put-object --bucket test-bucket-one --key test-key-one --body ~/Desktop/test_file.txt
{
    "ETag": "\"5ec9357e0c38adc805bb0004b36abcf1\""
}
$ aws s3api --endpoint-url http://localhost:5000 --region us-east-1 get-object --bucket test-bucket-one --key test-key-one ~/Desktop/fetched.txt
{
    "LastModified": "2021-11-10T18:10:26+00:00",
    "ContentLength": 18,
    "ETag": "\"5ec9357e0c38adc805bb0004b36abcf1\"",
    "ContentType": "binary/octet-stream",
    "Metadata": {}
}

That's the same as the real AWS though:
$ aws s3api --region us-east-1 create-bucket --bucket asdfjkllkj
{
    "Location": "/asdfjkllkj"
}
$ aws s3api --region us-east-1 put-object --bucket asdfjkllkj --key test-key-one --body ~/Desktop/test.html
{
    "ETag": "\"4de5b1942a3350bb5f84d618b2fbb7ed\""
}
$ aws s3api --region us-east-1 get-object --bucket asdfjkllkj --key test-key-one ~/Desktop/fetched.txt
{
    "AcceptRanges": "bytes",
    "LastModified": "2021-11-10T20:53:40+00:00",
    "ContentLength": 611059,
    "ETag": "\"4de5b1942a3350bb5f84d618b2fbb7ed\"",
    "ContentType": "binary/octet-stream",
    "Metadata": {}
}

See https://github.com/aws/aws-sdk-net/issues/815 for example, confirming that the ETag is supposed to be enclosed in quotes

Hmm, yeah that's strange. I tried running our test suite again against the 2.2.13 version, then did a list-objects-v2 on the bucket after:
$ aws s3api --endpoint-url http://localhost:5000 --region us-east-1 list-objects-v2 --bucket test-bsjy0wng8w
{
    "Contents": [
        {
            "Key": "test-output/all_data_types/aa43f382c28e4a5a9d0828938930e57d/1636589728677/.batch-metrics.json",
            "LastModified": "2021-11-11T00:15:45+00:00",
            "ETag": "\"87375b9bfad2fdea54348f55b94da641\"",
            "Size": 176,
            "StorageClass": "STANDARD"
        },
        {
            "Key": "test-output/all_data_types/aa43f382c28e4a5a9d0828938930e57d/1636589728677/_SUCCESS",
            "LastModified": "2021-11-11T00:15:44+00:00",
            "ETag": "\"d41d8cd98f00b204e9800998ecf8427e\"",
            "Size": 0,
            "StorageClass": "STANDARD"
        },
        {
            "Key": "test-output/all_data_types/aa43f382c28e4a5a9d0828938930e57d/1636589728677/part-00000-de7b9338-d96d-492c-9d03-5c7c6b7749fd-c000.snappy.parquet",
            "LastModified": "2021-11-11T00:15:44+00:00",
            "ETag": "\"\"7a56ebb7d6407a4aef1c6ca143140712\"\"",
            "Size": 19246,
            "StorageClass": "STANDARD"
        },
        {
            "Key": "test-output/all_data_types/aa43f382c28e4a5a9d0828938930e57d/1636589728677/part-00001-de7b9338-d96d-492c-9d03-5c7c6b7749fd-c000.snappy.parquet",
            "LastModified": "2021-11-11T00:15:44+00:00",
            "ETag": "\"\"f4a22c19abd52d3c0b78f6afdf469f0f\"\"",
            "Size": 18554,
            "StorageClass": "STANDARD"
        },
        {
            "Key": "test-output/manifest.json",
            "LastModified": "2021-11-11T00:15:45+00:00",
            "ETag": "\"f6491eb60705c9c62ee159e246b5f1f2\"",
            "Size": 235,
            "StorageClass": "STANDARD"
        }
    ]
}

I'm still trying to reproduce this with the CLI.

I have narrowed it down to the s3 cp command:
$ aws s3api --endpoint-url http://localhost:5000 --region us-east-1 create-bucket --bucket test-bucket-one

$ aws s3api --endpoint-url http://localhost:5000 --region us-east-1 put-object --bucket test-bucket-one --key test-key-one --body ~/Desktop/test_file.txt
{
    "ETag": "\"5ec9357e0c38adc805bb0004b36abcf1\""
}

$ aws s3 cp --endpoint-url http://localhost:5000 --region us-east-1 s3://test-bucket-one/test-key-one s3://test-bucket-one/test-key-two
copy: s3://test-bucket-one/test-key-one to s3://test-bucket-one/test-key-two

$ aws s3api --endpoint-url http://localhost:5000 --region us-east-1 list-objects-v2 --bucket test-bucket-one
{
    "Contents": [
        {
            "Key": "test-key-one",
            "LastModified": "2021-11-11T00:44:49+00:00",
            "ETag": "\"5ec9357e0c38adc805bb0004b36abcf1\"",
            "Size": 18,
            "StorageClass": "STANDARD"
        },
        {
            "Key": "test-key-two",
            "LastModified": "2021-11-11T00:45:24+00:00",
            "ETag": "\"\"5ec9357e0c38adc805bb0004b36abcf1\"\"",
            "Size": 18,
            "StorageClass": "STANDARD"
        }
    ]
}

Gotcha - that is a bug indeed, introduced by yours truly.
It should be fixed as of moto >= 2.2.14.dev22 - can you confirm this?

I just did a docker pull and our tests now pass. Thanks for the quick response on this!

Happy to hear that. Apologies for breaking things!


Implement calculation of matrix bandwidth

We could start this by creating all necessary files needed by project (.gitignore, src/NodeNumbering.jl, ...) and implement a function calculating bandwidth of testdata.

Done.


feat: added custom type for LogLevel

With this type you will get a slog.LogLevel from the variable and if the value is not recognized, it will just return slog.LevelInfo

Is this going to be merged?

We should probably add the go directive to go.mod to indicate that this must be built with go1.21 and above.

Sorry for the back and forth, I know that I was the one pointing you in this direction, but after thinking about it. It makes sense to add support for this in our internal logger package. Are you OK with that?

Closing this, as I've moved the code to cloud/logger


Use AHRS fault codes for INS

Description
As per offline discussion, this patch reuses AHRS fault codes in INS diagnostics.
Type of change
Please mark options that are relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] The code builds clean without any errors or warnings
[ ] Unit tests are passing
[x] Linter tests are passing

I purposefully left the test procedure out -- this is just adding a code to checks that are already working.


Prototypical Network Clarification from Tutorial 16

Have a few questions regarding how the classification works for the Prototypical Network:

From a high level perspective, for input to the ProtoNet model, are both support set and the query point required, in order to get a corresponding label as output?
If I wanted to just have an image (single query point) be the only input to a model that can then be compared to a non-changing support set (not part of the input), would this still be considered a prototypical network problem? Would a plausible workaround to this be passing a query point and a static support set as input to get a label (also static set)?
Is the pre-trained ProtoNet file provided generalizable to other datasets? What makes it (prototypical networks in general) generalizable?

Hi,

The ProtoNet uses the support set to create the prototype feature vectors, with which the query is compared. In that sense, yes, both support set and query set are inputs to the model.
If you fix the support set but still calculate the prototypes by encoding the support set with the same encoder as the queries, then it would still be considered a ProtoNet. Thus, if you take a trained ProtoNet and evaluate it on a new dataset with fixed classes, then it is still a ProtoNet due to the way it was trained. However, if you would remove the prototypes and instead make them learnable feature vectors independent of a support set, then it is not a ProtoNet anymore and actually becomes a standard classifier, since the last layer is equivalent to a linear layer.
ProtoNets are more generalizable than normal classifiers to other datasets by adapting their classification head to new datasets. That being said, the model has been trained on CIFAR100. Thus, it will work better with datasets that are similar to CIFAR100, and performance decreases if you use datasets with very different statistics/characteristics.

Clarified! Thank you very much!


add new param for bceid account type

Description
This PR includes the following proposed change(s):

FLA-201 - Add account type as an new param on the api

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] New and existing unit tests pass locally with my changes

[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /home/runner/work/jag-file-submission/jag-file-submission/src/backend/efiling-api/src/main/java/ca/bc/gov/open/jag/efilingapi/submission/SubmissionApiDelegateImpl.java:[50,5] method does not override or implement a method from a supertype