The permission 'Immutable storage' is displayed as 'unknown' in the 'Summary' dialog when attaching one storage account by the connection string (SAS) which is created from portal

Storage Explorer Version: 1.22.0-dev
Build Number: 20211026.1
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 18.04/MacOS Big Sur 11.6
Architecture: ia32\x64
How Found: Exploratory testing
Regression From: Not a regression
Steps to Reproduce

Select one non-ADLS Gen2 storage account -> Open the storage account in portal.
Make sure all the allowed permissions are selected -> Click 'Generate SAS and connection string'.
Copy the connection string.
Go to storage explorer -> Open the connect dialog -> Click 'Storage account or service'.
Select 'Connection string (Key or SAS)' -> Click 'Next'.
Paste the connection string -> Click 'Next'.
Observe the permissions in the 'Summary' dialog.
Check all permissions display well.

Expected Experience
All permissions display well.
Actual Experience
The permission 'Immutable storage' is displayed as 'unknown'.

Addition Context

The allowed permissions for one non-ADLS Gen2 storage account.

For one ADLS Gen2 storage account, the permission 'Immutable storage' can't be selected.

Verified this issue on the build 20211115.2. Reproduce.
So we are going to reopen this bug and verified it on a newer build.

I misread the repro steps, as I thought this was for a blob SAS. But that panel also needed the missing permission.

Verified on the build main 20211116.4. Reproduce.
Will verify this issue on a newer build.

Reproduce on the latest build 20211117.3. so we are going to re-open it and keep eyes on this issue.
Will close this issue once it got fixed.

Update:
This issue does not reproduce when using 'SAS URL'.

This issue reproduces when using 'Connection string'.

The screenshot from Portal:

New change has been merged that fixes permission labels for account connection strings.


fix: remove debug build from --version output

Fixes Debug build being printed when using --version.
We always compile with asserts enabled (-UNDEBUG), so checking whether -NDEBUG is defined is not a reliable way of detecting whether it is a release or debug build for us.
This wasn't necessary in the CMake build because we set -UNDEBUG after creating the gflags targets.

Will actual debug builds still be detected with this change?

Will actual debug builds still be detected with this change?

What do you mean by detected? I'm deleting this print condition entirely so it'll never get printed.

Will actual debug builds still be detected with this change?

What do you mean by detected? I'm deleting this print condition entirely so it'll never get printed.

The code is here to help identify debug builds, but the code is incorrect so we're fixing the problem by removing the code.  So, I'm asking two questions:

Do we need this information?  Presumable the use case is for internal users to be able to know if a particular build was compiled in debug mode.  Informally it also lets us do ad-hoc audits that confirm that release builds do not have debug information enabled.
If we need the information, what is the correct code to detect debug builds.

Will actual debug builds still be detected with this change?

What do you mean by detected? I'm deleting this print condition entirely so it'll never get printed.

The code is here to help identify debug builds, but the code is incorrect so we're fixing the problem by removing the code. So, I'm asking two questions:

Do we need this information?  Presumably the use case is for internal users to be able to know if a particular build was compiled in debug mode.  Informally it also lets us do ad-hoc audits that confirm that release builds do not have debug information enabled.

If we need the information, what is the correct code to detect debug builds?

We were only uploading Release and RelWithDebug build configurations for internal testing. CMake passes the -NDEBUG flag for both those builds so I don't think our internal users will miss this.
Not sure about developers though.
In any case we can bring this back and in both bazel and cmake we can just detect that it's a debug build using:

compilation_mode in bazel

CMAKE_BUILD_TYPE in cmake

Ok, let's put this on the backlog, but wait for a developer request/feedback before we prioritize the work.

Do we need this information?  Presumably the use case is for internal users to be able to know if a particular build was compiled in debug mode.  Informally it also lets us do ad-hoc audits that confirm that release builds do not have debug information enabled.

Also just want to mention that this was not a reliable mechanism to confirm release builds do not contain debug info since RelWDebug builds do not contain this print statement.


Unable to cross compile from within gitlab ci/cd pipeline

Checklist

[X] I've looked through the issues and pull requests for similar reports

Describe your issue
When I attempt to run the pipeline I get the following error
info: downloading component 'rust-std' for 'x86_64-pc-windows-gnu'
info: installing component 'rust-std' for 'x86_64-pc-windows-gnu'
Error:
0: docker inspect runner-ckasrop8m-project-62-concurrent-0 failed with exit status: 1
Stderr:
Error: No such object: runner-ckasrop8m-project-62-concurrent-0
Stdout:
[]
What target(s) are you cross-compiling for?
x86_64-pc-windows-gnu
Which operating system is the host (e.g computer cross is on) running?

[ ] macOS
[ ] Windows
[X] Linux / BSD
[ ] other OS (specify in description)

What architecture is the host?

[X] x86_64 / AMD64
[ ] arm32
[ ] arm64 (including Mac M1)

What container engine is cross using?

[X] docker
[ ] podman
[ ] other container engine (specify in description)

cross version
cross 0.2.5
Example
create a gitlab pipeline using the docker executer, the image I am using is the rust-latest image with cross installed. have the pipeline try to cross compile a package
Additional information / notes
It builds in a container with the same image not run by the gitlab pipeline

Found a dupicate


Check various things

Check, if the shortcut works when access help is disabled.
Check, if toggle with tab also works when the other selection option is used.

It works like a charm.


TreeExplainer on LightGBM model throws JSONDecode Error

Hi I have trained a LightGBM on my data. But I am unable to create a TreeExplainer on the model.
Please see the code below:
params = {
    "max_bin": 512,
    "learning_rate": 0.05,
    "boosting_type": "gbdt",
    "objective": "binary",
    "metric": "binary_logloss",
    "num_leaves": 10,
    "verbose": -1,
    "min_data": 100,
    "boost_from_average": True
}

model = lgb.train(params, d_train, 1000, valid_sets=[d_test], early_stopping_rounds=50, verbose_eval=10)

shap.initjs()
explainer = shap.TreeExplainer(model)
shap_values = explainer.shap_values(X)

Error Log:
JSONDecodeError                           Traceback (most recent call last)
<ipython-input-10-ea79d715786a> in <module>

      2 shap.initjs()
----> 3 explainer = shap.TreeExplainer(model)
      4 shap_values = explainer.shap_values(X)

~\AppData\Local\Continuum\anaconda3\envs\work_fstests\lib\site-packages\shap\explainers\tree.py in __init__(self, model, data, model_output, feature_dependence)
     94         self.feature_dependence = feature_dependence
     95         self.expected_value = None
---> 96         self.model = TreeEnsemble(model, self.data, self.data_missing)
     97
     98         assert feature_dependence in feature_dependence_codes, "Invalid feature_dependence option!"

~\AppData\Local\Continuum\anaconda3\envs\work_fstests\lib\site-packages\shap\explainers\tree.py in __init__(self, model, data, data_missing)
    534             self.model_type = "lightgbm"
    535             self.original_model = model
--> 536             tree_info = self.original_model.dump_model()["tree_info"]
    537             try:
    538                 self.trees = [Tree(e, data=data, data_missing=data_missing) for e in tree_info]

~\AppData\Local\Continuum\anaconda3\envs\work_fstests\lib\site-packages\lightgbm\basic.py in dump_model(self, num_iteration, start_iteration)
   2151                 ctypes.byref(tmp_out_len),
   2152                 ptr_string_buffer))
-> 2153         ret = json.loads(string_buffer.value.decode())
   2154         ret['pandas_categorical'] = json.loads(json.dumps(self.pandas_categorical,
   2155                                                           default=json_default_with_numpy))

~\AppData\Local\Continuum\anaconda3\envs\work_fstests\lib\json\__init__.py in loads(s, encoding, cls, object_hook, parse_float, parse_int, parse_constant, object_pairs_hook, **kw)
    346             parse_int is None and parse_float is None and
    347             parse_constant is None and object_pairs_hook is None and not kw):
--> 348         return _default_decoder.decode(s)
    349     if cls is None:
    350         cls = JSONDecoder

~\AppData\Local\Continuum\anaconda3\envs\work_fstests\lib\json\decoder.py in decode(self, s, _w)
    335
    336         """
--> 337         obj, end = self.raw_decode(s, idx=_w(s, 0).end())
    338         end = _w(s, end).end()
    339         if end != len(s):

~\AppData\Local\Continuum\anaconda3\envs\work_fstests\lib\json\decoder.py in raw_decode(self, s, idx)
    351         """
    352         try:
--> 353             obj, end = self.scan_once(s, idx)
    354         except StopIteration as err:
    355             raise JSONDecodeError("Expecting value", s, err.value) from None

JSONDecodeError: Invalid \escape: line 9 column 36 (char 205)

This is happening only with lightgbm, not with XGboost and CatBoost. Please help to resolve this.

I have never received this message before, but as you mentioned, it now crept up. Any solution would be greatly appreciated.

@firmai @Ashish-Tripathy I believe this is an issue with lightgbm, adding @guolinke .  I am also seeing this issue in our builds.  It may have been fixed already in lightgbm (and then it would be in 2.2.4 version), here is the related issue and fix:
https://github.com/microsoft/LightGBM/issues/2130
https://github.com/microsoft/LightGBM/pull/2131
The cause of the error was:
In https://github.com/Microsoft/LightGBM/blob/v2.2.3/src/io/tree.cpp#L511 returns from the constructor early, shrinkage_ remains uninitialized and in a very rare case its value is NaN.

However, while the error message is the same it is possible that this is a different issue or there are multiple issues.  Note the error is random, so just rerunning usually fixes it.
I was actually hoping to look into this issue eventually when I get a chance.

@firmai The quick fix worked for me. For now, I can contend with this.
@imatiach-msft tried rerunning multiple times, every time the same error. Tried running with previous versions as well but was getting the same error. It seems like the errors are same as you have mentioned.

@Ashish-Tripathy does this still happen with 2.2.4 in LightGBM? It does seem like a LightGBM issue since it is just a standard JSON loader that is crashing while trying to parse the LightGBM output.

Incredibly, downgrading matpotlib from 3.1.3 to 3.0.3, as reported here https://www.gitmemory.com/AlexeyKupershtokh,  solved the issue for me

We fixed more nan, inf issues in the dumped json file. You can check lightgbm v2.3.0

@nepslor I have downgraded my matplotlib, the issue persists.
shap==0.30.1
lightgbm==2.3.0
matplotlib==3.0.3
Can you please specify your shap and lightgbm versions?

@billydentsu I have your same versions. I noticed the bug represented when switching between scientific and non-scientific modes in pycharm. Let me know if you experience the same

@nepslor I see. @guolinke found out that my issue was caused due to quotes (") appearing in my dataframe's column names.


Learning project: Compare IncludeOS and node.js

I'm writing a simple IncludeOS echo service, and comparing it with a similar node.js service. My goal is to familiarize myself with IncludeOS and possibly produce an interesting blog post.

I'm implementing this in matiashf/IncludeOS-vs-node.js. Closing this.


fix Read the Docs builds failing

Read the Docs builds failing, but working perfectly locally

tracked issue on Read the Docs repo

tracked issue on Read the Docs repo


ST ISM330DLC IMU driver

TODO: review rotations

This was merged as part of https://github.com/PX4/Firmware/pull/12593.


Problem installing in Yosemite

I'm installing xmpp-node-client. When installing I get this error:
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the node-stringprep package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild

Node version: v0.12.2
Npm version: 2.10.0
Read in previous closed issues that deleting  ~/.node-gyp and retry might work, I had no luck.
This happens when installing through npm install.
Any idea?

Installed the module and it is not the case anymore.
Works for me per node 0.12

I'm experiencing this issue (via hubot > hubot-xmpp).  What's the workaround?

@jaxzin ask them to make a new release
It was fixed in https://github.com/markstory/hubot-xmpp/pull/95


Ownership updates.

Could you please update the data for new owner for Swift ppc64le builds? Thanks!

@asowani Can you please resolve the merge conflict?


Update dependencies (again)

Sorry, I think I did it correctly this time :|

I am currently on vacation. Since this is not critical I‘ll take a look at this, as soon as possible. Thanks a lot for your contributions!

Sure thing, have a nice vacation! :)

fyi: https://greenkeeper.io/

Yep, that's what I wanted to recommend as well 😄
I think it requires permissions so only you can set that up.

I‘ll add it as soon we have proper tests and CI servers in place.


⚠ Samsung has degraded performance

In b07c4a5, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2318 ms

Resolved: Samsung performance has improved in 565561a.


Engineering Checklist for Onboarding Van

New Engineer Onboarding Checklist
Special Notes

[x] Paste a link to the general onboarding ticket, which includes the onboarding authorization, here: https://github.com/cloud-gov/product/issues/2910

Complete additional cloud.gov trainings

    Federal employees and staff contractors, expand this section. Not applicable to project contractors.

Engineers who are federal employees or staff contractors have a Contingency Plan role and may participate in Incident Response, so they must complete the CP and IR trainings. Project contractors do not need to complete these trainings. Check one of the following:

[ ] Coordinate with your onboarding buddy to schedule Contingency Planning training within 60 days. (and annually after that). This will cover the following document, which you should also review before or after training:

[ ] Read the Contingency Plan.

[ ] Coordinate with your onboarding buddy to schedule Incident Response Training within 60 days of joining the team (and annually after that). This will cover the following document, which you should also review before or after training:

[ ] Read the Incident Response Guide.

Slack channels
Project contractors: Your buddy will add you to the private channel for your project.

    Federal employees and staff contractors, expand this section:

Your onboarding buddy will add you to these Slack channels:

[x] #cg-aws-security - private channel where bots post security notices
[x] #cg-billing - private business development channel (if applicable)
[x] #cg-incidents - private channel for incident response
[x] #cg-ops-banter - private channel for operations/engineering banter
[x] #cg-priv-all - private channel for in-team discussion
[x] #cg-priv-compliance - private channel for security and compliance discussions

Google Groups

    Federal employees and staff contractors, expand this section:

[x] cloud.gov AWS
[x] cloud.gov Notifications (🗣)
[x] cloud.gov Operations
[x] cloud.gov Security
[x] cloud.gov Support (🗣)

Channels marked with (🗣) receive a lot of messages, either from customers or bots, and you may want to mute them.

Learn our policies and procedures
In addition to the topics in the trainings section, review the following documents:

[x] Review the cloud.gov open source policy guidance about protecting sensitive information.
[x] Read the Continuous Monitoring Strategy, particularly the cloud.gov team responsibilities.
[x] Read the Configuration Management Plan.
[x] Read the cloud.gov Security Policies and Procedures. These documents explain the high-level policies and procedures we must comply with while running cloud.gov, sorted into security control "families" They explain that we follow GSA IT security policy, and they provide a summary of the procedures in our System Security Plan.
[x] Review the System Security Plan (the latest version lives on Google Drive; look for "cloud.gov System Security Plan (SSP)" as a .docx file). Of particular note for onboarding: Section 9 (System Description) and Section 10 (System Environment)
[x] Review the team's Engineering Practices. Some of these are mandatory because they fulfill FedRAMP requirements.

Getting to know cloud.gov
Resources on cloud.gov:

[x] View the video: A Technical Overview of cloud.gov
[x] Read the Delivery Process document to learn about how we work.
[x] Read our service disruption guide to learn how we handle customer-facing service disruptions.

Resources on CloudFoundry/BOSH:

[x] Look at Opensourced content for cloud foundry training classes: zero to hero (beginner), bosh/operator, and microservices
[x] Here is some training materials: GitHub - CloudCredo/training-operating-the-foundry: Training materials for Operating a Platform: BOSH and Everything Else
[x] Very thorough documentation on BOSH: Ultimate Guide to BOSH
[x] BOSH 101 presentation recording and slides

Getting hands-on with cloud.gov:

[x] Sign up for a cloud.gov sandbox using your GSA email address and start experimenting to get familiar with the basics of the PaaS from a user's perspective.

This is also required in order to make you a platform admin once you've completed the Cybersecurity and Privacy training.

Engineering-specific items
Machine admin rights

[x] In order to install development tools on your Mac, you will need to request local admin rights by submitting a ServiceDesk ticket using this justification. If you're unable to create a ticket for yourself, your onboarding buddy can create one for you.

Engineering account management
Before starting this section, you must complete:

GSA IT Security & Privacy Awareness Training
Role-based trainings listed under Learn our policies and procedures

AWS user names should be identical across accounts so that permissions can be correctly managed by Terraform.

[x] Create AWS Accounts by following these instructions. These accounts should be setup as read-only at the start, and once the 3 mandatory cloud.gov trainings are complete they will be switched to full admin accounts and added to the audit input file:

[x] AWS Commercial accounts
[x] AWS GovCloud accounts
[x] Ensure new person creates a 55-day Google Calendar reminder to update passwords, which expire every 60 days

[x] Add them to Nessus Manager via the GUI

[x] Add them to the ScanAdmins team in Settings > Groups

    Federal employees and staff contractors, expand this section:

You are a member of the Cloud Operations team, which means you have additional administrative permissions:

[x] Make them an admin of the platform.
[x] Add them to the platform-ops team in GitHub.
[ ] Add them as an admin on the cg-django-uaa docs
[ ] Add them to our dockerhub org and ensure we're not over our license count
[ ] Add them as an agent to the cloud.gov support Zendesk (Ask a cloud.gov member with admin access to Zendesk to add them).
[ ] Add them as Technical users to Ubuntu Advantage (Admin users for leads and supervisors)

Additional compliance setup/review

[ ] Install caulking git leak prevention by following the README
[ ] Verify caulking by running make audit and pasting a screenshot as a comment on this GitHub issue
[ ] Set GPG signing set up for GitHub (instructions here) and paste the output of git config commit.gpgsign as a comment on this GitHub issue

Install a development environment for cloud.gov

Note: Make sure you have followed the instructions in Machine admin rights at the top of this section to get local admin rights on your machine before moving forward

[ ] Install Homebrew (brew)
[ ] Clone the product repo, cd into it, and run brew bundle install to install everything in Brewfile.
[ ] Verify CloudFoundry installation via the CLI (once an existing cloud.gov teammate has made your cloud.gov admin account)

cf login -a api.fr.cloud.gov --sso
cf orgs

As a cloud.gov team member, you should have a long list of organizations
If you have none or one (e.g. sandbox) org, please reach out to your onboarding buddy

[ ] Configure aws-vault by following our directions
[ ] Fix fly, the Concourse CLI, by running xattr -d com.apple.quarantine /opt/homebrew/bin/fly. Concourse does not sign fly with an Apple Developer account, so you must use xattr to manually remove the binary from quarantine. Verify by running fly -h in your command line.
[ ] Install cloud.gov dev tools by cloning the cg-scripts repo: run git clone https://github.com/cloud-gov/cg-scripts.git in your command line

Figure out your first tasks
Project contractors: Check in with your project lead about first tasks.

    Federal employees and staff contractors, expand this for instructions:

The engineering team currently contains the following squads, each with their own projects:

Assurance, which focuses on security and compliance
Platform, which maintains and improves cloud.gov, focusing on internals like our AWS architecture and Cloud Foundry
Customer Success, which focuses on customer-facing features like service brokers and observability tools

If you are not already assigned to a particular squad, work with your onboarding buddy to join squad standups and learn what each squad is working on.

Assurance-specific items
These items are only mandatory for someone stepping into an Assurance squad role, but you are welcome to subscribe even if you are on another squad:

[ ] Subscribe to CISA alerts/updates: https://www.cisa.gov/about/contact-us/subscribe-updates-cisa
[ ] Subscribe to FedRAMP mailing lists: https://public.govdelivery.com/accounts/USGSA/subscriber/topics?qsp=USGSA_2224
[ ] Read Compliance Lead documents at root of the Google Drive Security and Compliance folder

Done!


Issues with commit c9b90df (msd vs variance references)

Hello Martians,
The recent renaming of MSD to the correct label variance seems not fully implemented in all commands yet. I just encountered a major bug in the DNA finder command. It is still referencing to MSD for filtering but the new filter must reference to variance. Unfortunately turning off the filter doesn't allow to run DNA finder at this moment. This problem might also occur in other commands using MSD.

Hi @mjosch,
Thanks for reporting this problem. The DNAFinder is actually in mars-commands, not mars-core, so I will close the issue here and fix it over there. Indeed this was a big oversight on my part to not also check that mars-commands still works.


bsf update --check

Few users may not prefer having a GitHub app/bot and would instead prefer if their CI failed when there is an update available so they can run bsf update themselves to commit the changes.
For this, we need a flag on bsf update command - --check.
When packages can be updated, the command will exit with status code 1(which is what users can run in their CI).

Hey @hanshal101 , thanks for showing interest.
I would suggest making a function to compare the slices. We can then compare the config we read and the the newPackages after updates.
If there is a change and user has passed the check flag, we can os.Exit(1).
PS: only gotcha when comparing slices is that we can't do a reflect.DeepEqual or something like that because we cannot rely on ordering of the elements.

Cool, I'm thinking of creating a compare function - func compareVersions(a,b []strings) bool {}, here i would create a go slice something like this count := make(map[string]int) and here I'll add all the key as version and inc the number (for a []string), and in the same way I would dec for b, and if the map in the count  doesn't have a zero it would return false.
How does this sound?

sounds good, we can discuss the specifics on a PR review. Thanks for picking this :)


Farridav/vagrantfile and testing

Adding in a vagrantfile for easy testing, and ensuring we do an idempotence test in travis

LGTM :metal:


ONVIF pairing error on Windows 10

Hi @roleoroleo
I've tried to pair my y21ga with firmware 0.1.5 and 0.1.6 with Windows 10 device pairing (Device enumeration and pairing Windows store app) to connect to the ONVIF service, but I can't manage to.
The NotPaired error pop-ups altho I can see the device on the ONVIF Device Manager.

CONFIG:

WINDOWS VERSION:
VERSION 21H1 (OS COMP: 19043.906)

Same here

I don't know how to fix the problem.
The cam replies to the discovery request but Windows doesn't understand the response.
I have to investigate.

I don't know how to fix the problem.
The cam replies to the discovery request but Windows doesn't understand the response.
I have to investigate.

Is there any update with the issue?

I tried to change the response from the cam but no luck.
I don't know how to fix it.


Android Basics: classes-and-inheritance

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-training-classes-and-inheritance?return=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-kotlin-unit-2-pathway-1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-training-classes-and-inheritance#4
In which task and step of the codelab can this issue be found?
5. Modify classes in the hierarchy
Implement floorArea() for RoundHut
Describe the problem
"The floor area of a circular dwelling is 2 * PI * radius."
I think 2 * PI * radius is a circumference. The area is PI * radius * radius
Further in the code samples it is correct.

Duplicate of #3


Declarative style in Testing

It is not an issue, it is more a feature, but I would like to use this declarative style in my tests, do you think it is possible to do this?

You mean something like https://github.com/imanghafoori1/laravel-makesure
it is a work in progress .


Go-to-definition on tagged union property should filter down to known union case

TypeScript Version:  2.9.1
Issue produced using vscode 1.25.1 which appears to depend on 2.9.1

Search Terms:
tagged union, go to definition
Code
type Animal = Cat | Dog;

interface Cat {
  animaltype: "Cat",
  color: string,
  friendly: boolean;
};

interface Dog {
  animaltype: "Dog",
  color: string,
  likesToFetch: boolean;
}

const cat: Animal = {
  animaltype: "Cat",
  color: "brown",
  friendly: true
};

Expected behavior:
Go-to-definition on the color property goes to the definition on Cat instead of showing definitions for both Cat and Dog.
Actual behavior:
Go-to-definition shows candidate definitions in both the Cat and Dog interfaces.
Playground Link:  https://www.typescriptlang.org/play/#src=type Animal %3D Cat | Dog%3B

interface Cat {
  animaltype%3A "Cat"%2C
  color%3A string%2C
  friendly%3A boolean%3B
}

interface Dog {
  animaltype%3A "Dog"%2C
  color%3A string%2C
  likesToFetch%3A boolean%3B
}

const cat%3A Animal %3D {
  animaltype%3A "Cat"%2C
  color%3A "brown"%2C
  friendly%3A true
}%3B
Related Issues:

QuickInfo needs to do the same as well. Assuming you have multiple jsdoc comments for color on both Dog or Cat, the compiler should be smart enough to only pick one or the other based on the discriminant property type.


Second draft

Major updates to language about an executive committee based on conversations in #24
Please add your thoughts, questions, comments, concerns!

This is ready for another review @val-pf, @lossanna, @alex-r-bigelow.

Thanks for fixing this @julianpistorius !!!


FixedSizeList inside Popover, causes flickering onEntering

[x ] The issue is present in the latest release.
[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
When opening a Popover that has FixedSizeList (react-window) as children and the itemCount is quite large (E.g 10k), you can notice a flickering happening.

Expected Behavior 🤔
No flickering should be happening
Steps to Reproduce 🕹
Example here
Steps:

Use Popover
Pass FixedSizeList (react-window) as a children
Item count is 10k

Context 🔦
I'm generating a large list in a Popover.
Your Environment 🌎
Browser: Google Chrome (Version 88.0.4324.146 (Official Build) (64-bit))

`npx @material-ui/envinfo`
 System:
    OS: Windows 10 10.0.18363
  Binaries:
    Node: 14.9.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.16.0 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 88.0.4324.146
    Edge: Spartan (44.18362.449.0)
  npmPackages:
    @material-ui/core:  4.9.13
    @material-ui/icons:  4.9.1
    @material-ui/react-transition-group:  4.3.0
    @material-ui/styles:  4.11.2
    @material-ui/system:  4.11.2
    @material-ui/types:  5.1.0
    @material-ui/utils:  4.11.2
    @types/react:  17.0.0
    react:  16.13.1
    react-dom:  16.13.1
    typescript:  3.8.3

I can only reproduce on Chrome. It looks like a rendering issue with this browser. I could even catch the white layout in the dev tools:

You can use a Fade animation, it seems to solve the issue https://codesandbox.io/s/material-demo-forked-332f8.


Add support for Education Edition 1.17.30

Education edition has recently updated to 1.17.30

Yes, please update bundabrg ❤.

Bump.

I'm working on it. Hopefully soon.

ETA when it's done?

A new version of Minecraft: Education Edition has been released - 1.17.31

how long we neeeed


sun_light SCN properties

how about something like :
{
  "azimuth": [
    0-360
  ],
  "elevation": [
    0-360
  ],
  "cast_shadow" : true,
  "color": [
    0-256,
    0-256,
    0-256,
  ],
  "intensity": [
    0-256,
  ],
},

working great ! is it possible to get shadow support at least for directional light ?

Yes; note that shadow map support is a full thing, regardless of light type. It's either all light types or nothing.


Kalyan split cred from structs

Split DataStore credentials into a separate structure to prevent
accidental logging.

Agreed.. With Encryption, this may not be needed. Was not sure if we could get it scheduled ASAP. This was some consolation till then - where we cannot accidentally spill the credentials by printing the whole structure.. Hence got this recommended change in.
If the secrets are encrypted, this change may not be needed.

I agree with @nordmark  that we shouldn't do this twice. We merged the big hammer of actually not logging anything that may contain credentials -- so that should keep us safe for now. At the same time -- we should absolutely schedule the real transition for the next sprint.
If we agree -- I don't think I'll be reviewing this in details.
@kalyan-nidumolu ?

I agree with @nordmark that we shouldn't do this twice. We merged the big hammer of actually not logging anything that may contain credentials -- so that should keep us safe for now. At the same time -- we should absolutely schedule the real transition for the next sprint.

Agree.. As discussed, Srinibas will pick it up support for encrypted passwords in the next sprint.. So will close this PR..


refactor: Unify pydantic evented model modules

This PR unifies and deduplicates a lot of the pydantic evented model code.  It's still a work in progress.  @Czaki, this will affect what you're doing in #279 ... If you'd prefer, i'm happy to wait to merge this until you're don there (and then will do the conflict resolution myself).  Or, if you want to wait, this might make your life easier over there

I think that #279 is ready for next review,

just merged in #279  ... but won't merge this PR until that one is in


fix: incorrect loading of native library with multiple backends

What this PR does
It fixes the incorrect loading of native library when having multiple backends installed. This issue has been mentioned in #456 and #589.
Description about the issue
The behavior in master branch now is quite wierd.

When using LLama.Example project directly, all things go as exepected.
When installing both cpu and cuda backend packages and using LLamaSharp in another project, it cannot load correct library even if the log does show it loads the desired library.

Let's consider the case2. I had many tries and it's concluded as below.

When I used WithCuda or WithLibrary to load the cuda version library, the log shown it had selected that file to load but actually no gpu is used. Besides I could confirm it's not because of the model loading problem.
There were 5 folders/files in my output path, which are llama.dll, avx, avx2, avx512, cuda11. When I was trying to load the cuda library, I could delete neither avx or cuda11 folder. That means, these two files were both occupied by a certain process, which is obviously the one I started.
If I deleted avx folder, the case became that avx2 and cuda11 were both occupied. Still, cuda library could not be used.
I confirmed the order of searching was correct and I didn't see a double-loading in logs.

After deleting all the folders except cuda11, I found it works. The only thing I could come up with is that avx, avx2, etc. hit the keywords of dotnet runtime and it does not obey the rules we write in our code.
Finally I changed all the paths and insert one more level directory llama-sharp into the paths of native libraries. All things worked as expected again on my PC.
To be honest I don't think my solution is good enough because I still don't know the reason behind it. Besides, through this debug I found some problems in current native loading code, so I'd like to take this PR as a discussion before releasing next version with LLaVA.
@martindevans @SignalRT Hope that this mention doesn't bother you. Your participation will help a lot. :)

Discussion
NativeLibraryConfig with LLaVA
I think we just need to use the same way with llama.dll to deal with LLaVA here. If I'm not mistaking it, there was already a discussion about whether to put llava libraries in each backend packages. I'm not sure if it still needs discussion.
OpenCL support
It seems that OpenCL related logic has not been added to NativeLibraryConfig. I'll add it later if it's not ignored intentionally.
More flexible loading strategy
I think maybe we should make a better abstraction and allow user to override some APIs to add more flexible control of library loading. Currently, as far as I know, users who want to publish an app with LLamaSharp often maintain the location of native libraries themselves, while their user could have various environments. Finally it always fallbacks to using WithLibrary, limiting the usage of our control strategy.
However the time cost of it seems to be a problem. I think it should at least be no hurry.

cc @vvdb-architecture @xuzeyu91 Would you like to help to test on this PR? Here's some steps for reference:

clone the code and checkout to this PR.
build the LLamaSharp project.
Go to LLama/packages and find the nuget package generated in step 2.
In Visual Studio, add the path in step3 as a nuget package folder and select it as the source.
(important) delete C:\Users\xxx.nuget\packages\llamasharp\0.10.0 to clear the cache.
Install your self-compiled LLamaSharp package.
a) Follow .github/prepare_release.sh to compile backends and install them. or b) Install published backend packages but modify the content of your output path every time you rebuild your project.

If you're unable to delete those two folders my best guess would be that we're explicitly loading one library (e.g. CUDA) but then it's also implicitly loading the AVX library when one of the native methods is called.
Maybe we should experiment with using SetDllImportResolver (link? There's been discussion about doing that before, and it's really the "proper" way to do this I think.

Yes, there must be two libraries loaded at the same time.
I've tried SetDllImportResolver but it seemed to only show the library name (llama.dll) instead of library file path when calling a native api.

I've tried SetDllImportResolver but it seemed to only show the library symbol name (llama) instead of library file path when calling a native api.

What I meant about using SetDllImportResolver is rather than using our current system (which loads the DLL ahead of time, and then just hopes that dotnet uses it) we could instead do all of our loading logic inside SetDllImportResolver. It's the proper API for it, and if we do that we'll know exactly what the loading system is doing because we're in control of it!

NativeLibraryConfig with LLaVA
I think we just need to use the same way with llama.dll to deal with LLaVA here. If I'm not mistaking it, there was already a discussion about whether to put llava libraries in each backend packages. I'm not sure if it still needs discussion.

I agree that we need the same way to load both libraries, llama.dll and llava_share.dll. My approach was to use the same directory layout, so I would suggest keeping this path and adapt the directory structure to the one that works better to the project.
The only thing that we didn´t discuss yet was if llava libraries will be in the same nuget packages (that's my preference, it will be the easiest way to the user).

@AsakusaRinne did you still want me to try this change out or should I wait while you all explore SetDllImportResolver as the solution?

It's okay to try it later, no hurry please

I've started experimenting with a SetDllImportResolver based approach, just as a prototype for testing. I'll push it up as a separate PR.

After some test, I believe #603 is a better approach to resolve this problem and it'll be completed in another PR. Close this now, thank you all!


Issue 1548 Fix for has_one association update

Fixes #1548
This pull introduces/changes:

While creating a association, we are checking if there is any reverse has_one association on target instance, if found we are deleting that association before creating new one.
Without this fix the target instance would have two has one relations of same type.

Codecov Report

Merging #1549 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1549      +/-   ##
==========================================
+ Coverage   93.33%   93.34%   +0.01%
==========================================
  Files         104      104
  Lines        4815     4824       +9
==========================================
+ Hits         4494     4503       +9
  Misses        321      321

Impacted Files
Coverage Δ

lib/neo4j/active_node/rels.rb
85.71% <100%> (+14.28%)
:arrow_up:

lib/neo4j/active_node/query/query_proxy.rb
94.7% <100%> (+0.06%)
: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 291c79a...24280ee. Read the comment docs.


postfix

adding spamassassin to the postfix pipeline
in the postfix nix expression we have this hardcoded masterCf (see below).
in order to add a spamassassin pipeline one has to alter the nix expression, i would like to suggest that we make the masterCf a default value for a mkOption which can be changed from configuration.nix
what do you think?

masterCf = ''
    # ==========================================================================
    # service type  private unpriv  chroot  wakeup  maxproc command + args
    #               (yes)   (yes)   (yes)   (never) (100)
    # ==========================================================================
    smtp      inet  n       -       n       -       -       smtpd
    #submission inet n       -       n       -       -       smtpd
    #  -o smtpd_tls_security_level=encrypt
    #  -o smtpd_sasl_auth_enable=yes
    #  -o smtpd_client_restrictions=permit_sasl_authenticated,reject
    #  -o milter_macro_daemon_name=ORIGINATING
...

https://github.com/NixOS/nixpkgs/blob/release-14.12/nixos/modules/services/mail/postfix.nix

services.postfix.extraConfig and services.postfix.extraMasterConf don't suffice?

the problem is this:
the manuals always mention to use:

smtp      inet  n       -       -       -       -       smtpd -o content_filter=spamfilter

along with:

spamfilter
          unix  -       n       n       -       -       pipe
   flags=Rq user=spamd argv=/usr/bin/spamfilter.sh -oi -f ${sender} ${recipient}

note: this means that one has to alter main.cf as appending would not overwrite the configuration (i tried that already).
see:
https://wiki.apache.org/spamassassin/IntegratedSpamdInPostfix
solution
do you have a better idea how to do that? i wonder, don't you use spamassassin?

I see ... yes, fixing that issue needs a modification of the existing config rather than appending to it. You are right.
Personally, I use spamassasin via procmail:
environment.etc = [
  {
    target = "procmailrc";
    source = pkgs.writeText "procmailrc" ''
      # generated global procmail configuration -- do not edit

      DEFAULT="/var/spool/mail/$LOGNAME"
      DROPPRIVS="yes"

      :0fw
      * < 512000
      | ${pkgs.spamassassin}/bin/spamc
    '';
  }
];

services.postfix.extraConfig = ''
  mailbox_command = ${pkgs.procmail}/bin/procmail
'';

so what do you think about my proposed solution?

I think it sounds fine.

@qknight, will you implement this patch?

Pull requests to implement the described feature would be welcome.


default caching in the pex tool is incorrect

if you do pex --repo=/tmp/path/to/my/repo -r req and that requirement gets pulled into $PEX_ROOT/build, subsequent calls to 'pex -r req' will resolve to the version in $PEX_ROOT/build if 'req' is ahead of the PyPI tip.  this is unexpected default behavior. the pex tool should only do this if --cache/--cache-ttl are both specified.

@wickman +1 to this issue -- that was a big surprise. :)

https://rbcommons.com/s/twitter/r/2076/ addresses this for the most part (source packages are always built...but it removes the -s option in favor of being uniform with pip.)

should be fixed by c93ea9c7.


AWS Security Hub

Updates the AWS backend to publish to Security Hub instead of SQS.
Adds AWS-centric detection values to the FalconEvent class.
Documentation updates.

Looks good to me. All I noted are nits, except for the error handling on non-existence instance on line 73.
I am bit confused by the region handling, it seems that we report all the detections for instances in any region to security hub in single fixed region. I may got this wrong as I am not well versed in boto3 region handling, but that is the impression I got from the code, a bit of clarity on that would appreciated for future readers.


Bug:  If parse() not found date returns now datetime

subj,
For example:
this code works only with Python 3. Python2 returns datetime.datetime.now()
        if sys.version_info >= (3, 0):
            target = datetime.datetime(2006, 9, 25, 23, 5).timetuple()
            self.assertExpectedResult(self.cal.parse('25 сентября 2006 23:05'), (target, 3))

I want, if parse not found date returns None value

Needed for v2 - see Issue #121

I agree.  It's important to return None instead of now, otherwise there is no way to check for errors.  It also makes it way too easy to introduce bugs.

Just because several people have commented requesting the wrong thing, I feel morally obligated to say explicitly: don't return None. Do raise an exception. See http://stackoverflow.com/a/1313837/1464495 and http://programmers.stackexchange.com/a/220647/203750 if unsure. Thanks.

Will this be fixed on day ? It's quite annoying...


Out of memory after 65 inserts

Hi,
sqlite works now with my esp8266 NodeMCU thanx to your library.
But the following code results in a "out of memory" message after approx. 65 dataset inserts:
randNumber=random(50);

   for (int i=1;i<1000;i=i+1) {
      char query[200];
      sprintf(query, "Insert into messungen (datum, liter) VALUES ('2020-12-20 20:59:00', %d);", randNumber);
      rc = db_exec(db1, query);
      if (rc != SQLITE_OK) {
         sqlite3_close(db1);
         return;
      }
      delay(100);
   }

I've set the stack size to 6144 in the following file:
/home/myuser/.arduino15/packages/esp8266/hardware/esp8266/2.7.4/cores/esp8266/cont.h
Is there more i can try to get rid of the out of memory error?
Best wishes
Daniel

What is the page size?  For a low memory MCU like Sqlite, it does not work well if page size > 512

What is the page size?  For a low memory MCU like Sqlite, it does not work well if page size > 512

Hi, where/how can i set the page size? I am using SQLite Studio.

Hi, where/how can i set the page size? I am using SQLite Studio.


Illegal argument: source must be a string of length > 0

Issue Id: 0df1b54d-14ea-f280-323b-64054adad4b7Versions - 1.39.1-  9df03c6d6ce97c6645c5846f6dfa2a6a7d276515-  c8252b63f547674d2faf361d4181bb76b0b5f81a-  d3eb24828e2d977e4f3ac16ff1a332a020028464-  5cd3b2abc98ebc8c8e226f0cd95a9bca93e2b4adStack Error: Illegal argument: source must be a string of length > 0/vs/base/common/errors.ts#156:9 (illegalArgument)/vs/workbench/api/common/extHostTypes.ts#2001:9 (arg4)/vs/workbench/api/common/extHostTypes.ts#1839:17 (construct)/vs/workbench/api/common/extHostTypes.ts#20:31/vs/workbench/api/common/extHostTask.ts#293:17 (to)/vs/workbench/api/common/extHostTask.ts#612:51 (getTaskExecution)/vs/workbench/api/common/extHostTask.ts#470:25 (apply)/vs/workbench/services/extensions/common/rpcProtocol.ts#398:16 (_doInvokeHandler)/vs/workbench/services/extensions/common/rpcProtocol.ts#383:31	at p._receiveRequest (\out\vs\workbench\services\extensions\node\extensionHostProcess

@vscodeerrors what were you doing when this occurred?
Can you reproduce it? If you can reproduce it, does it happen when you disable extensions?


Fix ci failures above php 7.1

What is this?
fix ci errors.

by follow usage change about phpunit.xml's attribute.
pinning php-cs-fixer version.

Details
Deleted colors="auto".
currently, colors value must be true or false, and default is auto.
(and all current supported versions are default auto)
see also: https://github.com/sebastianbergmann/phpunit/pull/1527
Move whitelist setting attributes into whitelist tag attributes
targets:

addUncoveredFilesFromWhitelist
processUncoveredFilesFromWhitelist
those two kind of attributes have deleted from phpunit tag.

Deleted logIncompleteSkipped attribute
logIncompleteSkipped is no longer allowed in phpunit.xml.
and because, we have no skipped test, we don't need it.
so, simply I delete it.
Add testsuite name
In latest version, name attribute is must be set.
avoiding php-cs-fixer bug #4684
avoiding https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/4684
This bug is only in 2.16.1, so, on composer.json, set !=2.16.1.

Please read the CLA carefully before submitting your contribution to Mercari.
Under any circumstances, by submitting your contribution, you are deemed to accept and agree to be bound by the terms and conditions of the CLA.
https://www.mercari.com/cla/

↑ok, I agree to mercari-CLA

Thank you ! @rugamaga


client.Describe No result returned

the code that reproduces this issue or a replay of the bug
const  imgUrl=`https://cdn.discordapp.com/attachments/1008571049039896576/1119473369813884958/manuelcorazzari_dirty_hands_holding_dirt_from_the_ground_sun_li_98bfb5e5-8c4f-4cb3-879a-bc229108e505.png`
const msg = await client.Describe(imgUrl);
console.log({ msg });

Describe the bug

No result returned
error log
No result returned

ws:true

https://github.com/erictik/midjourney-client/blob/main/example/describe.ts

I have the same problem with describe
The Code
   const msg = await client.Describe(       "https://img.ohdat.io/midjourney-image/1b74cab8-70c9-474e-bfbb-093e9a3cfd5c/0_1.png"     );
    console.log({msg});
The output:

https://github.com/erictik/midjourney-client/blob/main/example/describe.ts#L18

Yeah, I saw that client.Connect() but it gave me this error:
TypeError: client.Connect is not a function
    at main (/*******/index.js:12:18)
    at Object.<anonymous> (/*******/index.js:24:1)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:23:47

Maybe I'm forgetting something important?

npm install midjourney

Ok,
ny default npm installed v 2.7.79.
I forced the package.json to 3.0.80 and it works!
Thank you!

Ok, ny default npm installed v 2.7.79. I forced the package.json to 3.0.80 and it works! Thank you!

Still no. What's wrong， "midjourney": "^3.0.81"

help @clementepestelli

The task was successfully created, but the returned result was not broadcast

有毒，仓库代码也不行，其他setting API，reset api都可以，就这个Describe 不行，救命

I have the same issue with the example. No msg is returned from Describe().

Doesn't work for me either, using the latest version. Node 20<EMAIL_ADDRESS>no matter if I enable websockets or not - it submits the describe request and I can find the response in the discord channel, but MJ API never catches the response. Maybe because it's a public channel?


Fully rely on GetTransaction to find the block for the given TX in gettxoutproof

GetTransaction falls back to checking the UTXO set in case the txindex is
not available. This means we don't have to manually check the UTXO set and
can simply delegate this to GetTransaction.
This should fix a similar performance issue as in https://github.com/dashpay/dash/pull/1727. I however was not sure why it was implemented the way it was before, so I'd be happy to see some additional review here. There is a slight possibility that the order in which it was done before had a reasoning behind and that it is important to first check the UTXO set before going to the txindex.

This will conflict with https://github.com/bitcoin/bitcoin/pull/9738

Ok I see. Do you think this one is worth the effort to do a backporting first and then add a fix based on that?

I'm not sure about the logic behind the code as it's written currently tbh, so not sure if it's safe to fix/remove it. Need more time to investigate.

Ok, I can't find any reasonable explanation why it was implemented this way (via using oneTxid) besides probably that it was initially designed to work with a single tx and ability to handle multiple txes was added during peer review but no one re-reviewed this. I think it makes sense to drop oneTxid and AccessByTxid logic here in rpc and instead wrap GetTransaction(txid, ...., true) with for (const auto& txid : setTxids) { like in 9738.


Add max_step arg in basesolver

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #2253
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[ ] No style issues: $ pre-commit run (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[ ] All tests pass: $ python run-tests.py --all
[ ] The documentation builds: $ python run-tests.py --doctest

You can run unit and doctests together at once, using $ python run-tests.py --quick.
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

Yes, i'll try to finish this up asap.
Apologies as this one went down in the stack, thanks for pinging.

It looks like Chocolatey community repositories are under maintenance, which explains the Windows job failures.

Should also do changelog for this, right?

@rtimms I'd be happy to have your review & input on this. Thanks.

Closing since this is superseded by #4673.


supporting global styles directly in otion

I'm trying out otion in a gatsby project, and I'm aware that otion currently does not support global styles.
https://github.com/kripod/otion/tree/master/packages/otion#global-styles
However, by not supporting global styles makes using otion kinda awkward, as you need to rely on your build tool, i.e gatsby, to prefix the global styles. So you need to configure those things in two areas.
Please let me know if I'm wrong, and that there's a better way to add global styles!

While otion inlines scoped CSS during SSR for better per-page performance, global CSS should be referenced from a <link> tag, so that they may persist in the cache during page changes. Global styles are suitable for application-wide styling (e.g. normalization and/or reset), while inlining the scoped rules generated by otion accounts for faster page transitions due to the inlined per-page styles.
Thank you for the suggestion! I hope the rationale behind intentionally delegating global CSS to other solutions is a bit clearer now. The goal is maintaining the low bundle footprint while also encouraging performance-focused development patterns.

Thank you for the reply!

I hope the rationale behind intentionally delegating global CSS to other solutions is a bit clearer now.

Yea it is. I just realized that I was too accustom to the way emotion or styled-components work and that global css can technically be cached indefinitely i.e. Cache-Control: immutable.

The goal is maintaining the low bundle footprint

This is certainly what draws me towards it!

I've added this information to the readme so that it's available for future reference. Thank you for the question again! 🙌


Use net.Buffers for multiWrite

Simplifies multiWrite a bit and helps in cases when a user writes directly to a net.Conn, by avoiding some syscalls.

I'm using the resp package directly in one of my small import scripts / tools and this helps a bit since I'm writing directly to a net.Conn.
No performance numbers because I don't have my other notebook at hand.

Neat! Didn't know that was a thing


Grid View selection sometimes is not updated after selecting new entry.

This task is automatically imported from the old Task Issue Board and it was originally created by Adam Obuchowicz.
Original issue is here.

Steps to reproduce

Open "component list panel" debug scene
after the component is loaded, move the selection down with the arrow key.

Expected
The selection is over the entry.
Actual
The selection is sometimes a bit moved up.
Notes
The behavior is caused by the fact that local scope entries declares contour and highlight offsets, which cannot be read upon selecting, because we select them when they were not yet visible (scrolling animation just started).

EnsoGL is removed.


Proposal: alternative to Redis::BaseObject.expiration_filter

PRs #172 and #173 highlight a weakness in the current implementation supporting expiration options on class macros, notably in Redis::BaseObject.expiration_filter:
https://github.com/nateware/redis-objects/blob/dffb9a0e9ab6159cd3ccf1dffdafb0265c8f2d88/lib/redis/base_object.rb#L26
This approach requires maintainers to register all appropriate methods and theirs aliases with  expiration_filter. This is problematic for Redis::Objects which makes heavy use of alias methods in subclasses.
An alternative approach ideally obviates the need for a separate registry, makes it explicit that expiration is supported within the method definition itself, and handles alias methods seamlessly.
I propose replacing the current implementation with the following:
# Redis::BaseObject
def allow_expiration(&block)
  block.call.tap { set_expiration }
end

Subclasses would simply pass the method implementation as a block to allow_expiration:
# Redis::HashKey
def store(field, value)
  allow_expiration do
    redis.hset(key, field, marshal(value, options[:marshal_keys][field]))
  end
end
alias_method :[]=, :store

This PR depends on tests implemented in #172 and #173.

Thanks Ross!  Hopefully this fixes a few outstanding bugs as well.

@nateware Thanks for the quick merge and version bump!


0.71 beta Google maps location sharing now tracks account itself

Home Assistant release with the issue:

Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Component/platform:

Description of problem:
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:
Not so much a bug but the Google maps location sharing update now appears to track the account registered itself as opposed to other accounts shared with registered account. This appears to negate the whole problem of creating a new account. This should be listed as a fix and mentioned in the release notes as well as the component docs when the beta is finalized.

I updated the dependency to 2.0.7 which included a fix for accounts which are only sharing themselves. Now, it looks like that the changes in #14177 are not playing nice with the update in #14640.
So, for @omriasta does it look like a feature. Any other thoughts about a possible drop of the usage of a secondary account which users need to share their location with?

Looks like a feature to me as it makes it easier as long as the documentation mentions this.
Omri Asta
On Tue, Jun 5, 2018 at 12:45 PM -0400, "Fabian Affolter" <notifications<EMAIL_ADDRESS>wrote:
I updated the dependency to 2.0.7 which included a fix for accounts which are only sharing themselves. Now, it looks like that the changes in #14177https://github.com/home-assistant/home-assistant/issues/14177 are not playing nice with the update in #14640https://github.com/home-assistant/home-assistant/pull/14640.
So, for @omriastahttps://github.com/omriasta does it look like a feature. Any other thoughts about a possible drop of the usage of a secondary account which users need to share their location with?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/issues/14821#issuecomment-394779841, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALRnyJN8hejPtYEJxus8fg14qhu59PXwks5t5rWRgaJpZM4UaBMZ.

I have updated to 0.71 but I do not see the shared account as a device tracker, I still see the 2 expected devices as trackers.

Could not open pickle file, either file does not exist or no read access.
1:24 PM components/device_tracker/google_maps.py (ERROR)
Im running hassio/os 32bit 0.74.0 117  any help is appreciated

Home Assistant release with the issue:
0.76.0b1
Last working Home Assistant release (if known):
None
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
google_maps
Description of problem:
The problem is that the component can not create the file known_devices.yaml
in the log there are these two errors:
2018-08-14 11:30:46 ERROR (MainThread) [homeassistant.components.device_tracker] Unable to load /config/known_devices.yaml: Config file not found: /config/known_devices.yaml

2018-08-14 11:31:53 ERROR (SyncWorker_7) [locationsharinglib.Service] Could not open pickle file, either file does not exist or no read access.

Configuration is:
device_tracker:

platform: google_maps
   username<EMAIL_ADDRESS>   password: password

Hey guys, any news on this feature? is this implemented or can I help this go live somehow?

Feature worked until 0.80…it is now broken.
From: insajd<EMAIL_ADDRESS>Sent: Thursday, October 18, 2018 1:09 PM
To: home-assistant/home-assistant<EMAIL_ADDRESS>Cc: Omri Asta<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [home-assistant/home-assistant] 0.71 beta Google maps location sharing now tracks account itself (#14821)
Hey guys, any news on this feature? is this implemented or can I help this go live somehow?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/issues/14821#issuecomment-431088362, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALRnyNwMEKPX6rCfy_uNdWSCbygq5TBYks5umLW-gaJpZM4UaBMZ.

Closing this issue...no longer using the component due to stability


Port JavaMapForEachInspection

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#37  👈
#36
#35
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ermattt and the rest of your teammates on  Graphite


Re-sorted imports

Using isort, all imports are auto-sorted. It's a standardized import sorting tool.

Seems to be coveralls that's failing. I think it's mostly due to this being a forked repo.

@LilSpazJoekp can you review this?

Did you run pre_push?

Did you run pre_push?

Linting is running fine, but Coveralls is failing. Probably because both repos are forks.

I'll move this to main repo then.


[YUNIKORN-2290] Add K8s 1.29 to the e2e test matrix

What is this PR for?
Add K8s 1.29 to the e2e test matrix
What type of PR is it?

[x] - Improvement

Todos
What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-2290
How should this be tested?
AC in my fork https://github.com/brandboat/yunikorn-k8shim/pull/5
Screenshots (if appropriate)
N/A
Questions:
N/A

@brandboat please update scripts/run-e2e-tests.sh as well.

Already addressed comment in the latest comment, thanks


[Draft] Azure Arc Postgres overview dashboard

Adds extensions/arc for managing Azure Arc resources.
The UI is built with a ModelViewDashboard plus other ModelView components.
Communication with the Arc data controller is done via typescript clients and models generated from the controller's swagger specification.  No dependency on azdata CLI.

See extensions/arc/src/controller/README.md

This is a draft PR to get feedback on the approach.

Please update to use the existing dashboard framework.

@kburtram can you help me understand what this means?  I was told to use the ModelViewDashboard that @alanrenmsft contributed in https://github.com/microsoft/azuredatastudio/commit/41d21d799cc2adfdd38a85356eb3617b81d4b231

@bergeron the PR has a lot of code so I haven't tried to parse through it, so it could be I'm missing something.  In ADS we have a feature that we call the "Dashboard" that is usually launched from the Manage option on a resource.  All dashboard-like experiences should fit into this feature area.  New dashboards should contribute dashboard pages to this framework and all customization to the dashboard frame should be done through dashboard extensibility APIs.
From a glance, it looked like this was a new custom document type that was hosting dashboard-like content, rather than a proper dashboard type contributing dashboard pages to the existing dashboard feature.  Did I miss something in the code?

@kburtram The ModelView Dashboard is (part of) the new dashboard framework that @alanrenmsft added.
This is just a draft PR so @bergeron doesn't have it fully hooked up yet (the extension just launches the dashboard on activate currently for demo'ing purposes) - so it isn't using any of the JSON contribution points that the other dashboards added.
That being said - this case is likely going to need to use the extension API directly since we need to build up the main content area and all the tabs from service calls and as such can't have them contributed from the JSON anyways.

@Charles-Gagnon thanks.  The question I asked @alanrenmsft was is this PR using the official dashboard APIs that we plan to use for all our 1st-party and 3rd-party dashboard experiences going forward, or is this using the lower-level building blocks directly and rehosting them in a different document.  As long as the taskbar, left nav, content area frame, and document window are being created through the dashboard API then this is likely an experience we would want to support as part of the "dashboard feature" scope.  Otherwise, we'll want to update this PR to only use dashboard APIs to implement the dashboard-like features.
Perhaps separating the PR so that the auto-gen code is not included would make it easier to see what is being done here exactly.  Let's make sure we're including the correct folks like @alanrenmsft  and @anthonydresser in design discussions regarding the dashboard-related work here to avoid needing a lot of refactoring during code sign-off.

@bergeron I'm going to close this until we have something ready for review


IndexError: list index out of range

I use my data, have two colums, one is timestamp, one is value.
And use the Multivariate-SingleStep-LSTM and Multivariate-MultiStep-LSTM, the list index out of range:

The purpose of this code is to add environment variables, which are not in your data, so you need to comment out these two lines.


Improve multi-user mode, prevent watcher loops, improve payload parsing

Three points have been addressed:

multi-user mode:
the stipple.js route has been moved to the ws channel, if the channel differs from default. This is necessary, as otherwise the data in the model definition would always use the values of the latest client that joined.
I put @asysnc in front of update!(model, field, newvalue, oldvalue) to enhance responsiveness of the server. Otherwise all observables that are triggered by the update fire and are handled before the ws channel continues. Rewind, if you think, you always want synchronous handling. We could also think about including an argument sync in payload...
Also for the sync reason, I moved the update!() after the broadcast to the other clients in multi-user-mode.

prevent watcher loops:
normally Vue.js's watchers always fire when an update arrives via webchannel. This can lead to enhanced traffic or even loops with more than one client per channel. I chose @abellion's  proposal to detach and reattach the watchers. (I didn't use the mixing approach, though.) I also added some log comments to make sure, the communication is going ok

payload parsing
Base.parse(valtype, arg) needs a String argument. It can fail, if an Integer needs to be converted to a Float. Therefore I first try convert and then Base.parse(valtype, string(arg))

With all these changes I can use multiple users and mutliple clients per user. If multi-user-mode == true all clients of the same user synchronise.

There are still some @info logs, we might reduce that, particularly for plots that's too verbose ...

Please don't merge yet, I need to do some corrections!

Sometimes I hate git merge ...
But now it should be ok

final testing revealed, that the version with active: false instead of cb: () => null did not work (although it seemed to work before ... ?)
This has now all been fixed and tested from a freshly started REPL.
@essenciary  Please consider merging if you find it useful
P.S.: In order to test advanced multi-user-mode with broadcasting between clients call Stipple.set_multi_user_mode(true).

I ran into a problem that I needed to include a watch function in my js_methods and wondered why it didn't work after the watcher changes. The reason was, that the wathcer was also suppressed. With the last modification I propose to use a function as a watcher that you would normally not write that way. So probability of collision is drastically reduced.

@hhaensel Thanks for this amazing work! As you're actively working on this complex issue, you're better suited to follow the implementation. I've invited you as a contributor to the repo with write/merge access.

😃 I feel honoured

Thank you for your help with these awesome features! 🙏🤩

Have you tested whether your apps run smoothly with this code?
I would do some final testing and merge tomorrow ...

@hhaensel I didn't have the chance but I'll test the examples today.

@hhaensel I merged into a new branch hh-multi as I wasn't sure how to install your fork. I'll test single user mode now using the demos.

@hhaensel Unfortunately the branch doesn't seem to work - the UI does not update in https://github.com/GenieFramework/StippleDemos/blob/master/GermanCredits.jl

I also started trying some things, followed up here: https://github.com/GenieFramework/Stipple.jl/issues/10#issuecomment-717488764
Still not working though but that was the approach I had in mind.


Struct gets coerced into **kwargs (when *args is also present)

Why would we ever define Dry::Struct#to_hash method? Its purposed for implicit coercions like in the following example. We should define #to_h only, I guess.
Example:
[1] pry(main)> HueBridge.new.lights.last
=> #<HueBridge::Light id=15 name="Sofa" on=true brightness=144 hue=7676 saturation=199>
[2] pry(main)> a = HueBridge.new.lights.last
=> #<HueBridge::Light id=15 name="Sofa" on=true brightness=144 hue=7676 saturation=199>
[3] pry(main)> def b(*c, **d)
[3] pry(main)*   puts "args"
[3] pry(main)*   p c
[3] pry(main)*   puts "kwargs"
[3] pry(main)*   puts d
[3] pry(main)* end
=> :b
[4] pry(main)> b(1, a)
args
[1]
kwargs
{:id=>15, :name=>"Sofa", :on=>true, :brightness=>144, :hue=>7676, :saturation=>199}
=> nil
[5] pry(main)> b(a, 1)
args
[#<HueBridge::Light id=15 name="Sofa" on=true brightness=144 hue=7676 saturation=199>, 1]
kwargs
{}
=> nil

Monkey-patch fix:
class Dry::Struct
  undef_method :to_hash

  def to_h
    self.class.schema.keys.each_with_object({}) do |key, result|
      result[key] = Hashify[self[key]]
    end
  end
end

But I am not 100% of the implications of it

Yeah, I know that, this is how ruby works, they really messed with it IMO. Structs are supposed to work as hashes so this is expected. I wouldn't go with a monkey patch though, you can subclass Dry::Struct and use it as a base where you need
class MyStruct < Dry::Struct
  undef_method :to_hash
end

^also, you don't need to override to_h, undefining of to_hash doesn't affect it.

You say "Structs are supposed to work as hashes", but I wonder where is this requirement coming from.
In Ruby neither Struct nor OpenStruct implements the implicit conversion method to_hash. Both implement the explicit conversion method #to_h
More on the differences between implicit and explicit conversion methods here.
irb(main):001:0> A = Struct.new(:a, :b)
=> A
irb(main):002:0> def iii(**kwargs)
irb(main):003:1> puts kwargs
irb(main):004:1> end
=> :iii
irb(main):005:0> iii A.new(1,2)
Traceback (most recent call last):
        3: from /Users/sevos/.rbenv/versions/2.5.0/bin/irb:11:in `<main>'
        2: from (irb):5
        1: from (irb):2:in `iii'
ArgumentError (wrong number of arguments (given 1, expected 0))
irb(main):006:0> iii A.new(1,2).to_h
{:a=>1, :b=>2}
=> nil
irb(main):009:0> iii OpenStruct.new(a: 1, b: 2)
Traceback (most recent call last):
        3: from /Users/sevos/.rbenv/versions/2.5.0/bin/irb:11:in `<main>'
        2: from (irb):9
        1: from (irb):2:in `iii'
irb(main):010:0> iii OpenStruct.new(a: 1, b: 2).to_h
{:a=>1, :b=>2}
=> nil
irb(main):007:0>

I am afraid that there may be more cases when the struct may be deconstructed into a hash prematurely or accidentally causing us to lose the information about the type of the data it carries. Please tell me what are the cases you find this behaviour useful? Maybe there is really more good than harm...
Personally I use Dry::Struct as a base class for business domain entities and it's more of a better-Struct than a better-Hash, so I would prefer not to deconstruct that objects easily. Of course there should be a way to convert it to a hash, when needed.
Thanks for the idea for the base class, but now I worry more about dry-struct compatibility with other libraries, which may deconstruct it accidentally.

This is not a requirement, this is a design choice. One quick example is rom's interface for writing data, it relies on coercions made by Hash[value], anything hash-like can be passed in, including structs.

Thanks for clarification

For the record, this also just bit me. I was definitely not expecting my entity object to deconstruct into a hash because I had a keyword arg in a composite class initializer.

FYI: This does not even require **kwargs, regular keyword arguments are enough.
def display(*items, color: true)
  puts "items: %p color: %p" % [items, color]
end

Calling this with a Dry::Struct causes: ArgumentError : unknown keywords: item_attribute, item_attribute2, item_attribute_x


[TASK]  Move secscan nightly tests to aws

What's the task? Please describe
we need to move the security scan nightly test from DO to aws.
Describe the items of the task (DoD, definition of done) you'd like

Please use a task list for items on a separate line with a clickable checkbox https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists

[x] Move secscan nightly tests to aws
[x] Make sure the secscan run without issues.

Additional context
Add any other context or screenshots about the task request here.

Security scan work without issues.


ExtensionHost high CPU usage

Type: Bug
ExtensionHost is constantly consuming ~20% of CPU.
 My system is stuck at 100% CPU usage. Even after restarting.

Does CPU usage remain high after disabling all extensions? If so you can use Help: Start Extension BIsect to identify the extension that's causing the problem.

Disabling all extensions helps. But bisect did not help. It shows following message after first iteration.
Extension Bisect
[Content]
Extension Bisect is done but no extension has been identified. This might be a problem with Code.

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

Thank you for your prompt answer. This indicates either that this is not a vscode issue, or that it was a vscode issue fixed in the meantime (past month), so there is nothing to do on our side.

In my experience, the high CPU usage of the extension host process is never caused by vscode, but by an installed extension. If you want to try to find out which one it is and create an issue against it, you can try the following:

run F1 > Help: Start Extension Bisect
(this will restart VS Code with half of your extensions disabled)
try to do the steps which reproduce the problem
if the problem reproduces, click "This is bad" (this narrows down the problematic extension to the half which was enabled)
if the problem does not reproduce, click "Good now" (this narrows down the problematic extension to the half which was disabled)
these steps will repeat until the problematic extension is found

initial
step
final


Remove resolved TODO comments

Codecov Report
Base: 70.26% // Head: 70.26% // No change to project coverage :thumbsup:

Coverage data is based on head (0904e54) compared to base (3640e8d).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #276   +/-   ##
=======================================
  Coverage   70.26%   70.26%
=======================================
  Files          60       60
  Lines       11589    11589
  Branches     1565     1565
=======================================
  Hits         8143     8143
  Misses       1902     1902
  Partials     1544     1544

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


feat: add support for containers arg to helm chart

@bpetit This adds support for the --containers arg to the helm chart.
It also extends the RBAC rules for listing pods.

@bpetit Could we include these helm chart changes in 0.4.0?
There is also this related PR https://github.com/bpetit/rs-k8s-sync/pull/1 which means we don't need to mount a kubeconfig.

ofc !


[Fix] make nvm use display .nvmrc's version in output messages

Set $PROVIDED_VERSION equals to $NVM_RC_VERSION only if a .nvmrc file is
present and the user didn't provided a version to use (.ie typed nvm use).

Behavior before this fix :

$ nvm use
Found '.nvmrc' with version <v0.10.28>
N/A: version "N/A" is not yet installed.

You need to run "nvm install N/A" to install it before using it.

Behavior after this fix :

$ nvm use
Found '.nvmrc' with version <v0.10.28>
N/A: version "v0.10.28" is not yet installed.

You need to run "nvm install v0.10.28" to install it before using it.

Thanks! This needs two more things before it's ready - tests, and then rebasing it down to a single commit.

Just tried with nvm 0.33.1 and couldn't reproduce the issue anymore.
I think you can close this PR as somehow it's now included in master branch

Thanks for confirming!

@anchnk any chance you could check the "allow edits" box on the RHS of the PR?


Forward error message of the response to UnknownError

to get more informative exceptions.
I run into a 403 (API rate limit exceeded) but the exception only told me UnknownError

Thanks

:+1: Nice package, works well and is easy to use


Create template config file.

Turn config file into a template, so it can be overwritten in place with new options using existing values.

Closed by #56.


Align thymocyte / DN T Cell with MP

See:
https://sourceforge.net/tracker/?func=detail&atid=1109502&aid=3610968&group_id=7
6834

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 20 Apr 2013 at 8:07

Closing.  Will reopen if a better description of the problem is provided.  I suspect MP is the problem, not CL in any case.


Monitor - cannot rename route

When trying to rename a route, the response is "500 - Internal server error".
In the server log I can see the route update logic trying to read the existing route details using the new name instead of the old name.

Note: this name is a simple label for humans. Could you allow all? UTF chars (especially space, dash…)

The route update logic has been fixed.
About the characters that can be used in the group names and the route names: currently these names can consist of a-zA-Z0-9 and dash (with a maximum length of 15 characters). This naming convention was already in use for the GR routes. At the time it also seemed like a good idea to limit the available characters because the names are used in the url's. But this limitation is in not really necessary: we are using location names already in url's, and these contain all kind of characters and spaces and accents, etc.
This issue is left open to lift the character limitation on the name.

The restriction on the characters that can be used in group and route names has been lifted in release 4.0.32. It is now possible to have accents, spaces, etc. in the names.


feat: create storage-transcode-videos extension

Adding new extension for annotating videos through video the Video Intelligence Api https://cloud.google.com/video-intelligence/docs/quickstart
Uses Cloud storage to watch and process videos as they are added.
Testing
Basic test run showing installation, transcoding input and output.
Installation

Transcoding

Logging

@googlebot I consent.

Testing
Basic test run showing installation, transcoding input and output/
Installation

##Transcoding

Logging

Closing as this has now been moved to https://github.com/GoogleCloudPlatform/firebase-extensions


Update from upstream

Pull latest upstream and rebase my modifications onto it

Needs testing, just wanted to create the PR right now.

Moved to #2


Failed to start on termux on android tablet

Describe the bug
Getting some internal error
Client information
OS:
Version:
Comand

export PATH=$PATH:~/.spoof-dpi/bin
~ $ с^C
~ $ rm -rf .spoof-dpi
~ $ curl -fsSL https://raw.githubusercontent.com/xvzc/SpoofDPI/main/install.sh | bash -s linux-arm64
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100 17333  100 17333    0     0  78257      0 --:--:-- --:--:-- --:--:-- 78786
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 2354k  100 2354k    0     0  1573k      0  0:00:01  0:00:01 --:--:-- 3588k
./spoof-dpi

Successfully installed SpoofDPI.
Please add the line below to your rcfile(.bashrc or .zshrc etc..)

export PATH=$PATH:~/.spoof-dpi/bin
~ $ cd .spoof-dpi/
~/.spoof-dpi $ cd bin
~/.spoof-dpi/bin $ ls
spoof-dpi
~/.spoof-dpi/bin $ ./spoof-dpi
error: "/data/data/com.termux/files/home/.spoof-dpi/bin/spoof-dpi" has unexpected e_type: 2

Additional context

This project is not for android environment

I build it on android and it started in termux

Yeah, but there's nothing weird even if it doesn't work on android because it hasn't been tested on android.


The configuration used in forward and backward may be inconsistent

Some functions (e.g. convolution_2d) change their behavior based on chainer.config, while they may use different config options between forward and backward. It is currently difficult to change the behavior of backward for selected function applications.
This was easily done when we passed options to each function manually, in which case the same option is used for both forward and backward. I feel we should use the same convention; the configuration used in forward is reused in backward instead of reading the config again in backward from chainer.config.

The issue looks still existing.

Duplicate of #2938.


Add ep-featured-list

Added featured list to entry page and updated associated styles.
@nickirios As this featured list will be placed in other elements on the page, I'm not sure if it is situated in the right spot.

Closing and will reopen a new one with entry-page as base.


Added Shivanshi's Profile

Hi, Added my profile to the profiles.js folder.
Thank you!

[ ] Resolve merge conflicts

Can i just make a new PR? I feel moving content in this one would mess up other people's profiles which have conflicts


[QA] Re-Sharer can increase permissions

Setup via docker-compose-eos-test.yml from branch fix-yml-for-rc5 on localhost
Via WEB UI:

login as einstein, share a folder with richard as viewer only
log in as richard, accept the folder, re-share to moss as editor
login as moss, accept the folder, enter the folder, upload a file into it. Works. BAD.
check the situation as einstein:

Although richard is clearly only Viewer, and moss received the share through richard, moss is Editor.
(At least einstein can clearly see what happend). Okayish.
Expected behaviour: share receiver can only reshare with same or subset of his own permissions.

A public link created by richard with Editor role behaves differently:
Richard sees, that  the link has Editor permissions, but
users of the link cannot upload until einstein gives richard editor permissons.

According to @pmaier1 re-sharing should not be possible at all.

@butonic Can you please confirm, that this was expected?

Kind of dupe of https://github.com/owncloud/ocis/issues/552 ?

Also similar issue https://github.com/owncloud/product/issues/270

Retested with ocis-1.0.0-rc8 via ocis/deployments/examples/ocis_traefik/
No more resharing conspiracy possible:
share receiver gets an GRPC error when trying to re-share a readonly share.
That is an acceptable workaround, but not nice.

Retested with ocis-1.0.0-rc8 via ocis/deployments/examples/ocis_traefik/

Try a reload after encountering the error. Unfortunately the share is created nevertheless.

@pmaier1 @micbar just want to bring this to the picture again. As it has p2-high is this something we should re-test and come to a conclusion?

@pmaier1 @micbar just want to bring this to the picture again. As it has p2-high is this something we should re-test and come to a conclusion?

We should fix it during our hardening of the share features.

We should fix it during our hardening of the share features.

re-sharing is щаа. Need a re-test when we turn it on

Resharing is disabled.


What happened to oracletabledependency?

Hi Christian,
we cannot find anymore the oracletabledependency - seems to be deleted everywhere. Could you please let me know why - any major issues you encountered with it?
Thanks in advance

OracleTableDependency is not anymore supported. Every development has been stooped.
Why? No resources available.


406 error why?

i got a 406 response code error

Well it's proxyless tool, so it can't be helped. Try to use vpn or external proxies.

proxys cant help it much too
figured out the soltuion is using windows api rn

your repo helped me thanks for that

your repo helped me thanks for that

proxys cant help it much too figured out the soltuion is using windows api rn

Can u send example pls??


Add Test in build pipeline to ensure InstallFiles are up to date

To ensure the installation YAML files are always up to date with the code, we should add a test job in the build pipelines which essentially runs the make create-install-files command and fails if the result causes the git state to become dirty.

Gracias


doc: preparing for publication

proofreading-typos, punctuation
copyediting-style, clarity, flow, consistency

superseded by https://github.com/SUSE-Cloud/socok8s/pull/363. Move edits to correct location


TypeError: done is not a function

Hi
I have a simple flow, where I input START to your node, I get:
1/30/2021, 5:19:35 PMnode: 3555ea0f.3e2936
msg : error
"TypeError: done is not a function"

What Node-RED version are you using? I'm using v1.2.9 and the node works without any issue.

it was the version :D
thx


Add new Foundation libraries to SwiftRuntimeLibsOrdered

Now that Foundation has added a handful of new libraries to the build that are linked from Foundation itself, we're seeing a handful of build logs that contain contents like the following:
... -lFoundationInternationalization -lFoundationEssentials -lFoundationInternationalization -lFoundationEssentials -lstdc++ -lswiftCxx -lswiftCxxStdlib -lstdc++ -lswiftCxx -lswiftCxxStdlib -lstdc++ -lswiftCxx -lswiftCxxStdlib -lstdc++ -lswiftCxx -lswiftCxxStdlib -lFoundationInternationalization -lFoundationEssentials -lFoundationInternationalization -lFoundationEssentials -lFoundationInternationalization -lFoundationEssentials -lswift_Differentiation -lFoundationInternationalization -lFoundationEssentials -lFoundationInternationalization -lFoundationEssentials -lFoundationInternationalization -lFoundationEssentials -lFoundationInternationalization -lFoundationEssentials ...

Per https://github.com/apple/swift-foundation/issues/872, this list seems to be used to deduplicate linked libraries for common libraries. This change adds the new Foundation dynamic libraries (FoundationEssentials, FoundationInternationalization, and _FoundationICU) along with swiftSynchronization (which Foundation also links now) to this list for deduplication to help minimize the issues caused by these repeated link flags.
(I'm not extremely familiar with this list, but it seems that since Foundation is already there we should add the new Foundation libraries, however feel free to let me know if we shouldn't do this or if there's a different change that should be made)

@swift-ci please smoke test

I think you can remove the icu libs now: those are no longer built or shipped separately.

As long as we're here, might as well update this list for 6.1. Some more candidations for addition: swift_Builtin_float, swift_Differentiation, swiftDistributed, swiftObservation, swift_Volatile, Testing.
@stephentyrone, @ktoso, @grynspan, @al45tair, wdyt, should we add any of those?

I honestly don't know. :)

@grynspan, try this: find a large project with many Testing test files, then run swift build --build-tests -v on linux. Does the last link command building the test runner have one -lTesting or many?

Ah, yes, one per file. So sounds like we should add Testing as you've suggested.

Pinging @gwynne and @compnerd too, in case you have any input.

@al45tair and @FranzBusch, mind pushing this change through to completion and into Swift 6? We are going to see a regression with a ton of repeated linker flags otherwise.
It looks like everybody went on summer vacation in the last couple weeks when this was proposed, but with the Swift 6 release likely coming in the next month, we should get this in.

Thanks, @compnerd, do you have an opinion on which other of the new runtime libraries listed above should also be de-duplicated?

I'd say that Testing is a good idea to add to the list, the other ones don't seem as important.

Alright, if someone would go ahead and merge, @jmschonfeld doesn't seem to be active lately, so I went ahead and submitted #76224 with my remaining suggestions for this pull, so we can get those in separately.

Sorry for the delay @finagolfin! I'll go ahead and merge this one, thanks for the followup PR!


locale.json does not use "JSON with comments" mode

testing #39588
locale.json uses the JSON language mode, not the JSON with comments mode.
That said, comments in locale.json are not errors and I can having trailing commas.
F1
Configure Language
result:

If comments are accepted, then all is ok.
As said the language mode is lying here, that's expected.


QSFS: Docker Image.

According to TC342 & TC387 and the requirements that these test cases verify REQ174, REQ175, REQ176 there should be a qsfs docker image and a docker build script available and easy to use.
but as mentioned in TC387 when i searched for a qsfs docker image on threefold's docker hub profile i didn't find any

 # cd /var/run
/run # ls
redis  zinit.sock

zstor has not created the socket to yet so the test command in the zinit configuration fails.
Probably because
2023-03-02 14:02:12 +00:00: DEBUG connecting to zdb at [300:cc55:8958:c1ff:229e:63d2:6fda:878d]:9900
2023-03-02 14:02:12 +00:00: DEBUG connecting to zdb at [300:cc55:8958:c1ff:229e:63d2:6fda:878d]:9900
2023-03-02 14:02:12 +00:00: DEBUG connecting to zdb at [300:cc55:8958:c1ff:229e:63d2:6fda:878d]:9900
2023-03-02 14:02:12 +00:00: DEBUG connecting to zdb at [300:cc55:8958:c1ff:229e:63d2:6fda:878d]:9900
2023-03-02 14:02:42 +00:00: ERROR error during storage: ZDB at [300:cc55:8958:c1ff:229e:63d2:6fda:878d]:9900 741-18336-meta1, error operation CONNECT caused by timeout

The zdb container is not reachable from within the container, it is from the VM though so a docker ipv6 problem

using host networking makes it work but:
[+] initializing zdbfs v0.1.11
[+] blocks cache size: 4096 KB
[+] virtual filesystem size: 10.0 GB
fusermount3: fuse device not found, try 'modprobe fuse' first

And extra todo:

[ ] make sure local o-db only listens on the localhost interface or on a socket

modprobe fuse on the host does not solve it as the fuse device is not available in the container
Passing the fuse device with  --device /dev/fuse is not sufficient:
[+] initializing zdbfs v0.1.11
[+] blocks cache size: 4096 KB
[+] virtual filesystem size: 10.0 GB
fusermount3: mount failed: Operation not permitted

passing --privileged or --cap-add SYS_ADMIN works but the zstor logs are flooded with
2023-03-03 13:07:13 +00:00: DEBUG encoding file "/data/index/zdbfs-meta/zdb-namespace" with key path "/data/index/zdbfs-meta/zdb-namespace"
2023-03-03 13:07:13 +00:00: ERROR failed to process store command error during accessing local storage for attempting to store file which is not in the file tree rooted at /mnt: invalid data, queueing a retry

dropping the root property from the zstor config makes this error disappear but bouncing intothis one now:
2023-03-03 13:25:56 +00:00: DEBUG Finding backend config
2023-03-03 13:25:56 +00:00: ERROR failed to process store command error during configuration: could not find any viable backend distribution to statisfy redundancy requirement, queueing a retry
2023-03-03 13:25:56 +00:00: DEBUG the scheduler forwarding command Store(Store { file: "/data/index/zdbfs-meta/zdb-namespace", key_path: None, save_failure: true, delete: false, blocking: false })
2023-03-03 13:25:56 +00:00: DEBUG encoding file "/data/index/zdbfs-meta/zdb-namespace" with key path "/data/index/zdbfs-meta/zdb-namespace"
2023-03-03 13:25:56 +00:00: DEBUG file checksum: 4ab1d2c1bb4be398cd9726251442fc78 ("/data/index/zdbfs-meta/zdb-namespace")
2023-03-03 13:25:56 +00:00: DEBUG Loading metadata for key /testdocker/meta/f46911200c6be4cc49cf7c1df2a37b6a
2023-03-03 13:25:56 +00:00: DEBUG Reading data from zdb metastore for key /testdocker/meta/f46911200c6be4cc49cf7c1df2a37b6a
2023-03-03 13:25:56 +00:00: DEBUG Metadata for file "/data/index/zdbfs-meta/zdb-namespace" not found.
20

The zstor config had redundant groups set to 1 while there was only 1 group configured, have set it to 0


doc/html Contents empty

Describe the issue
Some recent internet-drafts are showing up with an empty table of contents in the side panel.  I'm also getting a JS error that might have something to do with that:
properties of undefined (reading 'match')
    at wr (nav.js:11:20)
    at Array.map (<anonymous>)
    at xr (nav.js:27:10)
    at HTMLDocument.<anonymous> (document_html.js:45:5)

Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

This is because https://github.com/ietf-tools/rfc2html/pull/12 got merged. Will fix.


ui.begin(g)  --> TypeError: Cannot read property 'begin' of null

Hey there, I am not sure if this is a Kha or Zui problem.
Maybe you can help.
I tried all kinds of variations. I can't call ui.begin(g).
Screen is black and Debug goes crazy.
Main:
 class Main {
    public static function main() : Void {
        System.start({title:"Project", width:1024, height:768}, initialized);
    }

    private static function initialized(window : Window) : Void {
       Assets.loadEverything(function(){
		    var game = new Project();

        	System.notifyOnFrames(
            	function(fbs : Array<Framebuffer>) {
                game.render(fbs[0]);
           		}
        	);
        	Scheduler.addTimeTask(game.update, 0, 1 / 60);
    	});
	}
}

Project:
class Project {

	public var ui:Zui;

	public function new (){
		var ui = new Zui({ font: Assets.fonts.AndaleMono });
	}

	public function update():Void{
	}

	public function render (framebuffer:Framebuffer):Void{

		var g = framebuffer.g2;
		g.begin();
		g.drawRect(40,40,40,40,6);
		g.end();

		gui(g);
	}

	public function gui (graphics:Graphics){
		ui.begin(graphics);

		if (ui.window(Id.handle(),10,10,240,600)){
			if (ui.panel(Id.handle( {selected: true}),'panel',false,true)){
				ui.text('some text');
				ui.textInput(Id.handle( {text:'text input here'} ), 'textIn' );
				ui.check(Id.handle(), 'checkbox');
				ui.slider(Id.handle({value: 0.3}),'slider', 0, 2);
				Ext.colorPicker(ui, Id.handle());
			}
		}

		ui.end();
	}
}

Debug Console:
TypeError: Cannot read property 'begin' of null
SystemImpl.hx:60
    at Project.gui (/Volumes/HDD2/Luetze/Haxe/KHA/Kha Zui/Sources/Project.hx:45:2)
    at Project.render (/Volumes/HDD2/Luetze/Haxe/KHA/Kha Zui/Sources/Project.hx:39:3)
    at /Volumes/HDD2/Luetze/Haxe/KHA/Kha Zui/Sources/Main.hx:22:17
    at Function.kha_System.render (/usr/local/lib/haxe/lib/kha/git/Sources/kha/System.hx:196:4)
    at animate (/usr/local/lib/haxe/lib/kha/git/Backends/HTML5/kha/SystemImpl.hx:449:5)

Any ideas?
Thanks & best,
tL.

I think I got it, sorry 'bout that...

Weeeell, no I don't.
Can make it work in one file, can't make it work in two files.
If you have an idea, please shoot...

Hi, sorry but that's not enough info for me to tell what is wrong. Please try playing with the examples first at https://github.com/armory3d/zui/tree/master/examples, that should help.

Thank you.
I've got eveything rolling now.


Databasetarget: use parameters on install

RunInstallCommands should now take into account all parameters passed to it.
WriteEventToDatabase and RunInstallCommands both use parameter looping logic, so that has been extracted into its own private method.
Various additions to the Unit tests.
Added a reference to Microsoft.Data.Sqlite and removed Microsoft.Data.Sqlite.Core.
This should make all sqlite tests work for both 452 and netcore.
fixes https://github.com/NLog/NLog/issues/2715

AFAIK we could also configure the parameters in the XML config for the install, ins't?
Maybe we should add an example for it at  https://github.com/nlog/nlog/wiki/Database-target

Setting it to "System.Data.SqlClient" in the full framework will fail, because the switch-case for it is excluded

Believe the following line will work just fine for the full-framework:
ConnectionType = Type.GetType(DBProvider, true, true); // DBProvider = "System.Data.SqlClient"


MM-16044 - Updating radio buttons (a11y)

Summary
MM-16044 - Updating radio buttons (a11y)
Ticket Link
https://mattermost.atlassian.net/browse/MM-16044

Code looks good but we should probably have QA look at it before it's merged

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3085.test.mattermost.cloud
Test Admin Account: Username: sysadmin | Password: Sys@dmin123
Test User Account: Username: user-1 | Password: User-1@123

Spinmint test server destroyed


FR: Sort for Backlinks

Backlinks is obsidian core feature that does have sort but i cannot set a default sort to be e.g. new to old sorting (see pic below). Since the user defaults for sorting is doable for the embedded query, was hoping that it can be implemented for backlinks as well.

pic 1: Obsidian Backlinks does not have settings to save

pic 2: Query Control offer to save setting on sort but currently only affecting search and embedded query

Here's FR at Obsidian -- https://forum.obsidian.md/t/support-user-default-preferences-for-show-more-context-and-sort-order-in-backlinks/35757/

+100 🙏