(#230) Add Admin Only Source For Chocolatey Core Packages

Description Of Changes

Add ChocolateyCore admin only source
Add ChocolateyCore NuGet repo within Nexus
Add Jenkins job Update ChocolateyCore Repository
Change previous C:\choco-setup\files\files directory to be C:\choco-setup\files\packages

Motivation and Context
Main reason for creating this repository was from feedback of admins not wanting their end users to see the Chocolatey core packages in the default repository. This way ChocolateyInternal only contains the packages brought in by the Jenkins internalization pipeline. Also cleaning up the end user view.
Testing

Tested on local VM.

Operating Systems Testing

Windows Server 2022

Change Types Made

~[ ] Bug fix (non-breaking change).~
~[ ] Feature / Enhancement (non-breaking change).~
[X] Breaking change (fix or feature that could cause existing functionality to change).
[X] Documentation changes.
[X] PowerShell code changes.

Change Checklist

[x] Requires a change to the documentation.
[X] Documentation has been updated.
[x] Tests to cover my changes, have been added.
[x] All new and existing tests passed?
[x] PowerShell code changes: PowerShell v3 compatibility checked?

Related Issue

Docs PR with README changes: https://github.com/chocolatey/docs/pull/1038

Fixes #230

Converted back to draft after finding issue when running ClientSetup script.


0.3.0 rc

Description
Merges the 0.3.0 release branch into release.
This release candidate has successfully passed our release testing process.
Release note
Unreal GDK version 0.3.0 is go!
Corresponding Engine version: https://github.com/improbableio/UnrealEngine/tree/4.20-SpatialOSUnrealGDK-0.3.0
Make sure to upgrade your GDK and Engine fork to the latest release. Either use the 0.3.0 tagged commits or switch your projects to the release branches and git pull.
Make sure to run Setup.bat and regenerate your project files after upgrading!
Happy developing!
GDK team
Release Notes 0.3.0
New Known Issues:

If the Query Based Interest Enabled checkbox in the SpatialOS GDK for Unreal Runtime Settings is ticked, level streaming will be supported, but at the cost of poorer performance.
Replicated TimelineComponents are not supported.

For current known issues, please visit this docs page
Features:

The default connection protocol is now TCP.
Query Based Interest is now supported as an opt-in feature.
Level streaming is now supported. You must enable Query Based Interest to use level streaming.
The GDK Toolbar now recognises when a local deployment is running, and contextually displays start and stop buttons. - (@DW-Sebastien)
Added interface support for Unreal Engine 4.21 UNetConnection. - (@GeorgeR)
Unreliable RPCs are now implemented using events instead of commands. This resolves associated performance issues.
The delete dynamic entities setting now works when used in conjunction with multiple processes.
You can now determine the type of a SpatialOS worker from within the game instance.
Entity IDs are now reserved in batches instead of individually. This accelerates the creation of SpatialOS entities.
Multiple server-workers can now be used in conjunction with the use multiple processes setting.
You can now serialize and deserialize component data defined in external schema (schema that is not-generated by the Unreal GDK). You can use this to send and receive data, and edit snapshots.
Improved logging during RPCs.

Bug fixes:

The GDK now automatically compiles all dirty blueprints before generating schema.
Attempting to load a class which is not present in the schema database now causes the game to quit instead of crashing the entire editor.
Actor::ReplicateSubobjects is now called in the replication flow. This means that Subobjects are now replicated correctly.
Schema generation is no longer fatally halted when blueprints fail to compile.
AActor::TornOff is now called when a TearOff event is received. This is in-line with the native implementation.
References to objects within streaming levels, that are resolved before the level has streamed in, no longer cause defective behavior on the client.
Attempting to replicate a NonSpatial actor no longer causes a crash.
The SpatialOS Launcher now launches the correct game client, even when UnrealCEFSubProcess.exe is present in the assembly.
Duplicate startup-actors are no longer created when a server-worker reconnects to a deployment.
BeginPlay is no-longer called authoritatively when a server-worker reconnects to a deployment.
Fast Array Serialization now operates correctly in conjunction with GameplayAbilitySystem.
Reference parameters for RPCs are now correctly supported.
Clients now load the map specified by the global state manager, rather than loading the GameDefaultMap before querying the global state manager.
Automatically generated launch configurations for deployments with a prime numbers of server-workers are now generated with the correct number of rows and columns.
Generating schema for a level blueprint no longer deletes schema that has been generated for other levels.
Deleting recently created actors no longer causes crashes.
Having multiple EventGraphs no longer causes incorrect RPCs to be called.
TimerManager, which is used by SpatialOS networking, is no longer subject to time dilation in the World instance.
Clients no longer crash after being assigned multiple players.
GetWorkerFlag can now be called from C++ classes.
Pathless mapname arguments are now supported by the GDK commandlet.
When NotifyBeginPlay is called, BeginPlay is no longer called on actors before their Role is correctly set.

External contributors:
In addition to all of the updates from Improbable, this release includes 2 improvements submitted by the incredible community of SpatialOS developers on GitHub! Thanks to these contributors:

@DW-Sebastien
@GeorgeR

Closing as we are instead re-pointing release to the release candidate tag.


Delete unneeded Over65RecommendationText in ManageSpecialPopulation.cql

This has been removed in PR: https://github.com/ccsm-cds-tools/ccsm-cds-with-tests/pull/64, along with a few other recommendation texts that were no longer used.


BUG: TypeError: get_network() got an unexpected keyword argument 'nodes'

pyrosm version 0.5.3
from pyrosm import OSM, get_data
osm = OSM(get_data("test_pbf"))
nodes, edges = osm.get_network(nodes=True, network_type="driving")

TypeError: get_network() got an unexpected keyword argument 'nodes'

@DawnyWu Hi! This feature is only available in the new pyrosm version 0.6.0 that I will most probably release later today (sorry you just got in the middle of transition to the new version). If you want to start testing already now, you can install it from the master:
pip install git+https://github.com/HTenkanen/pyrosm.git@master

New version can now be installed with pip or using conda:
https://pyrosm.readthedocs.io/en/latest/installation.html


[Request] rust-nightly toolchain

Link to the package upstream website/repository
rust-nightly
Utility this package has for you
Rust toolchain without using a different flake/overlay (and with purity)
Do you consider the package(s) to be useful for every Chaotic-Nyx user?
YES!
Do you consider the package to be useful for feature testing/preview?

[X] Yes

Are you sure the package isn't available upstream already?

[X] Yes

Does the package's license allow redistributing it?
YES!
Have you searched the issues to ensure this request is unique?

[X] YES!

Have you read the README to ensure this package is not banned?

[X] YES!

More information
Could be based on this? https://github.com/nix-community/fenix

UPDATE: Current stuck due to: https://github.com/chaotic-cx/nyx/issues/403

I forgo to update on this, now we do have "Fenix" in our flake.nix. We just need to choose an attrset in it to provide.
Our CI will probably want https://nix-community.cachix.org/ though.

Closing this, don't have time to do it myself, if someone is that much interested, please open a PR instead.


Bad call to rustdoc when cargo test --package feature when using features

TLDR: this (almost) minimal project doesn't work: https://github.com/TeXitoi/cargo_bug_feature_package
When using features, and calling cargo test --package feature, --cfg arguments are bad when calling rustdoc.

Maybe a duplicate of #2539

Right now --cfg flags are passed here to rustdoc  which originates from this field which are all filled in here.
The bug here is that we're passing root_pkg to the calculations here, which doesn't work with the --package flag where we're actually testing something other than the root crate. I think this may be the same issue as https://github.com/rust-lang/cargo/issues/2539 because we attempt to pass build script cfg values, but that would require https://github.com/rust-lang/cargo/issues/2539 specifically being related to the -p flag which it currently doesn't mention.
I think we'll want to tweak this logic and perhaps just update Compilation to not only store the cfg values for the root package, but rather the entire crate graph. That way later on we can just look up the relevant piece in the hash table in Compilation instead of always picking the one cfgs value.
I'm going to tag this E-easy as I think it shouldn't be too hard to tackle, but if anyone works on this and needs some help feel free to ping me!

Hi @alexcrichton, I can take a look at this if no one has done it yet. (yes, I'm chasing E-easy tags in this project 😆 )

@jhbabon sure! Let me know if you need any pointers!

Hi! Sorry for the delay on this. This is the fix I managed to do: https://github.com/rust-lang/cargo/pull/3242


typo lol

Hi Alex! This is a great idea for a commandline tool.

Thanks, I've been sitting on it for a while and thought it was good enough to publish.


CLI11 weird behavior

If compile SPERR on MacOS using gcc-12, invoking CML utilities will throw and give weird message:
shaomeng@cisl-luxora SPERR/build-gcc % ./bin/compressor_3d -h
terminate called after throwing an instance of 'CLI::CallForHelp'
  what():  This should be caught in your main function, see examples
zsh: abort      ./bin/compressor_3d -h

This issue seems disappeared. Closing.


fix: remove suggestion of using fetch-depth

Description
Changesets automatically deepens a shallow clone as necessary, So we don't need to recommend a complete deep clone in order
for changesets to work.
Ref: https://github.com/changesets/action/pull/177

He @harshcut! Thanks for your attention to detail!


Support findInjector in fragment chain

I have a feature that utilize Android navigation. The activity implements the getInjectorFactory() to provide the component for all the fragments in the nav_graph. However, we have another project that requires the logic to be condense in a Fragment instead of Activity, and the fragment owns the nav_graph. Under current implementation, Fragment.findInjector() only checks the fragment itself, and its parent activity, but not the fragment chain. I would like to know if there is an workaround to have the OWNER fragment implements getInjectorFactory() like the activity does, instead of having to implement InjectorHolder for every single fragment in the graph (It is also inefficient to do so, components are re-created, and if we have to pass fields in the component factory, it is very hard to pass those arguments.)
@rodgavila do you know any workaround?

Hey @tsenggordon. My guess is that currently that intermediate fragment is an AuthAwareFragment. What you'll need to do is have that intermediate fragment be either an AuthRequiredFragment or an AuthOptionalFragment that will create a new scope under it:
https://github.com/dropbox/kaiken/blob/37d279723bdc689a4e5cf3f52412523025115e61/scoping/src/main/java/com/dropbox/kaiken/scoping/AuthAwareFragment.kt#L12
Let me know if this works.

@rodgavila, sorry I missed one important detail, is that the parent Activity is not a kaiken supported activity (It is an AppCompatActivity), is it still possible the make the change you suggested? If not, is there a way to do user scoping without having the parent activity being KaikenActivitiy?

The parent activity will need to be a Kaiken activity, no way around that. Is there an issue preventing you from ch as find that to be a Kaiken activity? It should be a very minimal change. And ideally all Activities should eventually be Kaiken activities.

Hey @rodgavila and @tsenggordon - The parent activity is our main activity. It implements AuthOptionalActivity. I changed the scoping of the intermediate fragments to implement AuthRequiredNavHostFragment and AuthRequiredFragment. However I still get error that Fragment does not implement InjectorHolder and neither its parent activity. Thoughts?

Yeah of course. Overview below. Thanks for taking a look. Really appreciate it
Our IAP flow can be launched from MainActivity and IapActivity:

IapActivity implements AuthRequiredActivity and InjectorHolder<IapComponent> and has iap_nav_graph
MainActivity implements AuthOptionalActivity

When IAP flow is launched from MainActivity:

We create ParentFragment
ParentFragment implements AuthRequiredFragment and InjectorHolder<IapComponent>
ParentFragment embeds iap_nav_graph in AuthAwareNavHostFragment
GrandchildFragment implements AuthAwareFragment
App crashes when GrandchildFragment invokes inject() in onAttach

Exception:

com.dropbox.kaiken.runtime.InjectorNotFoundException
"Fragment class GrandchildFragment does not implement InjectorHolder and neither its parent activity"

The main activity that hosts the fragments needs to be an InjectorHolder of the component otherwise, it won't find the component.


Templates never reloaded

The content of a filesystem-based template is cached and never reloaded. We should monitor the filesystem for changes.

Could influence #22 (Cache rendered pages), as we must only reload the cache if the file gets changed. Therefore, our mechanism introduced here should allow for template change detection from outside.

Done for viewer template, yet to do is the editor template (and possibly unit tests).

Should refactor the last change. Maybe I can move the logic around atomic.Value into the Template struct itself, so that none of its users need to bother.


Solve miscellaneous log outputs

Solve log errors that don't seem to affect anything

"E/SpannableStringBuilder: SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length"
"W/ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@40703b1"
"E/libc: Access denied finding property "vendor.gralloc.disable_ahardware_buffer""

Solved all the errors:

"E/SpannableStringBuilder: SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length"
This error is thrown soely based on the keyboard. If you use the google keyboard this error will be thrown once you delete a whole line and get moved to the one before, but if you use the swift keyboard it will be thrown whenever you delete a few words or do the same things in the google keyboard. This error does not do anything that affects the experience of the user in any way, it just appears in logs.

"W/ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@40703b1"
This disappeared all together with development. Originally this was cause by some sort of way I was creating my activities and linking their xml views together, but with development I have seemed to fix it since this error is not thrown at all between my two devices anymore. This error never did anything to the user experience though, it just popped up in logs.

"E/libc: Access denied finding property "vendor.gralloc.disable_ahardware_buffer""
This is dependent on the device running the app. If a google pixel runs Lockbook, this will be thrown in the logs but it does not affect the user experience at all. But if I run this on my Samsung Galaxy Tab S6 lite, it will not be thrown in the logs. It seems this log error is dependent on the device running it.


thirdparty Add xxhash lib

Proposed changes
Add xxhash lib for BE, which is the faster hash method by test.
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Is there any test data for performance improvement?

Is there any test data for performance improvement?

The detail will be another pr of shuffle hash compute. For more detail, you can see here: https://github.com/Cyan4973/xxHash


Preview for mobile

Component or Package Name: jsx-email
Component or Package Version: latest

Feature Use Case
react-email is got the preview mobile which is pretty cool to have an idea of how the email will look like in both devices
Feature Proposal
I personally find the switch a bit annoying so since most of emails is 640px wide max, I'd just show simultaneously the mobile and desktop on the same screen. I'd same some time.

For sure! We've got an active branch for this here: https://github.com/shellscape/jsx-email/tree/feat/jsx-email/preview-devices. You're welcome to checkout that branch and give it a shot. It's not quite where I want it to be, but it's close. And as per usual it's a far better experience than what react-email have cobbled together 🙊  I'm hoping to get this done early next week.
I posted a preview on discord last week as well https://discord.com/channels/1156307748552716398/1156766131462361211/1183525703069732966


Rulesets cannot be set for all repos when the org does not have an enterprise subscription

Problem Description
When the GitHub organization does not have an enterprise subscription, it is not possible to set rulesets for all repos in the organization.
What is actually happening
What happens is that safe-settings queries https://api.github.com/orgs/<my_org>/rulesets and the API returns a 403 with a message that reads: Upgrade to GitHub Enterprise to enable this feature.. This prevents the use of safe-settings to apply rulesets to all individual repos in the org.
What is the expected behavior
It is expected that safe-settings should allow a user to set a ruleset for all repos in an organization by controlling rulesets on all repos in the org instead of via the org-level rulesets.
Error output, if available

  |
-- | --

{"level":50,"time":1699959656065,"pid":26,"hostname":"safe-settings-demo-99cb5dcf8-hwg58","name":"probot","name":"probot","name":"event","id":"13bc6ffc-82dd-11ee-92eb-11a42222cbb3","name":"HttpError","status":403,"response":{"url":"https://api.github.com/orgs/[REDACTED]/rulesets","status":403,"headers":{"access-control-allow-origin":"*","access-control-expose-headers":"ETag,
 Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit,
X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource,
X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes,
X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id,
 Deprecation,
Sunset","connection":"close","content-encoding":"gzip","content-security-policy":"default-src
 'none'","content-type":"application/json; charset=utf-8","date":"Tue,
14 Nov 2023 11:00:56 GMT","referrer-policy":"origin-when-cross-origin,
strict-origin-when-cross-origin","server":"GitHub.com","strict-transport-security":"max-age=31536000;
 includeSubdomains;
preload","transfer-encoding":"chunked","vary":"Accept-Encoding, Accept,
X-Requested-With","x-accepted-github-permissions":"organization_administration=write","x-content-type-options":"nosniff","x-frame-options":"deny","x-github-api-version-selected":"2022-11-28","x-github-media-type":"github.v3;

format=json","x-github-request-id":"B62A:3EA2:4C2CA2:9E0057:65535367","x-ratelimit-limit":"5000","x-ratelimit-remaining":"4899","x-ratelimit-reset":"1699962859","x-ratelimit-resource":"core","x-ratelimit-used":"101","x-xss-protection":"0"},"data":{"message":"Upgrade
 to GitHub Enterprise to enable this
feature.","documentation_url":"https://docs.github.com/rest/orgs/rules#create-an-organization-repository-ruleset"}},"request":{"method":"POST","url":"https://api.github.com/orgs/[REDACTED]/rulesets","headers":{"accept":"application/vnd.github.v3+json","user-agent":"probot/12.3.1
 octokit-core.js/3.6.0 Node.js/16.20.2 (linux;
x64)","x-github-api-version":"2022-11-28","authorization":"token
[REDACTED]","content-type":"application/json;
charset=utf-8"},"body":"{\"name\":\"Enforce pull
requests\",\"target\":\"branch\",\"enforcement\":\"active\",\"conditions\":{\"ref_name\":{\"include\":[\"~DEFAULT_BRANCH\"],\"exclude\":[\"refs/heads/oldmaster\"]},\"repository_name\":{\"include\":[\"<mark>[REDACTED]</mark>\"],\"exclude\":[\"test\",\"test1\"],\"protected\":true}},\"rules\":[{\"type\":\"pull_request\",\"parameters\":{\"dismiss_stale_reviews_on_push\":true,\"require_code_owner_review\":true,\"require_last_push_approval\":true,\"required_approving_review_count\":1,\"required_review_thread_resolution\":true}}]}","request":{"retryCount":1}},"stack":"HttpError:
 Upgrade to GitHub Enterprise to enable this feature.\n    at
/opt/safe-settings/node_modules/probot/node_modules/@octokit/request/dist-node/index.js:86:21\n
    at runMicrotasks (<anonymous>)\n    at
processTicksAndRejections (node:internal/process/task_queues:96:5)\n
at async sendRequestWithRetries
(/opt/safe-settings/node_modules/octokit-auth-probot/node_modules/@octokit/auth-app/dist-node/index.js:398:12)\n
    at async Job.doExecute
(/opt/safe-settings/node_modules/bottleneck/light.js:405:18)","type":"Error","msg":"Upgrade
 to GitHub Enterprise to enable this feature."}

Context
This may well be the intended behavior and if so, it would be good to make this clear in the documentation.
Are you using the hosted instance of probot/settings or running your own?
Self-hosting
If running your own instance, are you using it with github.com or GitHub Enterprise?
github.com
Version of probot/settings
Probot v12.3.1 (Node.js: v16.20.2)
Version of GitHub Enterprise
N/A

also having this issue with GitHub Team subscription

I have found this too. A bit concerning as I suspect GitHub might full deprecate classic branch protection at some point.

@cachedout @raleonardo @paddyroddy I also just started trying out rulesets and have so far only used it in repo specific settings files. The behavior you describe is actually mentioned in the README. Maybe it's not super clear, but the rulesets defined in the settings.yml are applied as org level rulesets only. If you want repo level rulesets you have to use suborgs or repo level settings files.
Recent commit with changes of the relevant section in the readme: https://github.com/github/safe-settings/commit/15408100d15ac18d2698ac2e3bd901b6ba5545db
You should be able to use repo level rulesets by defining a suborg that includes the desired repositories by using a glob pattern.
Bare in mind a repo can only be part of a single suborg, so the final solution varies depending on your config structure.
If you don't have any suborgs or repo level override files, then you should be able to do something like this:
File: admin/.github/suborgs/a-descriptive-filename.yml
# "Sub organization" for trying out repo level rulesets

suborgrepos:
  - *

rulesets:
  # demo ruleset with some random settings
  - name: my-repo-level-ruleset
    target: branch
    enforcement: active
    conditions:
      ref_name:
        include:
          - "refs/heads/main"
        exclude:
          - "refs/heads/[0-9]*.[0-9x]*.x"
    bypass:
      actors:
        users:
          - "dependabot"
    current_user_can_bypass: never
    description: |
      Repository-level ruleset applied to a glob pattern of repos.
    rules:
      - type: required_linear_history
      - type: required_signatures
      - type: deletion
      - type: update
      - type: creation
      - type: non_fast_forward
      - type: pull_request
        parameters:
          required_approving_review_count: 1
          dismiss_stale_reviews_on_push: true
          require_code_owner_review: true
          require_last_push_approval: true
          required_review_thread_resolution: true
          automatic_copilot_code_review_enabled: true
      - type: required_status_checks
        parameters:
          strict_required_status_checks_policy: true
          do_not_enforce_on_create: true
          required_status_checks:
            - context: ci
            - context: lint

Disclaimer: I don't know how this will work if you have defined the same ruleset in both the suborg and a repo level settings file. With branch protections you could have it defined on the suborg level and then just override the required status checks. I'm not sure if you can do that with the rulesets and the rules (or if you have to define the complete required_status_checks rule in every repo settings file).

@anderssonjohan thanks! Will give this a go today

Nice that worked well https://github.com/UCL-MIRSG/.github/blob/main/safe-settings/suborgs/rulesets.yaml


Updated data connector and template

Required items, please complete
Change(s):

Modified app config to use CRON schedule directly
Added handling for empty inventory storage containers
Remove unnecessary app insights properties from ARM template

Reason for Change(s):

Customer reported issues when inventory storage not populated

Testing Completed:

Yes

Here is some evidence of the updated function app working successfully.


Exploit found causing the server to time out

Hello,
I found people abusing a new exploit lagging out the server,
/execute at @e run summon item
Please block this as it highly lags the server making it unplayable.
~Adabellemine1984

^

UwU

Temporarily patch: spam /de (possibly in a commandblock loop) (doMobSpawning disabled, difficulty peaceful)


Support for volume expansion

Hi,
When will you support volume expansion to work?
Best regards,
Giang

Currently the feature is planned for Q4/2020 delivery.


COMP: Upgrade ITK from v5.1.1 to v5.2.0

Upgraded to ITK version 5.2.0, which was released on May 28, 2021.
ITK 5.2.0 fixed a critical issue, with commit  https://github.com/InsightSoftwareConsortium/ITK/commit/7cebc26dfae73d90dbf4702aa1ccc544e9b70a37 "COMP: Fix OpenJPEG build error with Visual Studio 16.9", by James Butler (@jamesobutler) and @spacelg
Following pull request https://github.com/SuperElastix/SimpleElastix/pull/425 and https://github.com/SuperElastix/SimpleElastix/pull/428 by David Young (@yoda-vid)
Obviously, ITK 5.2.0 has many other improvements: https://github.com/InsightSoftwareConsortium/ITK/releases/tag/v5.2.0

lgtm

GitHub Actions was already building with the v5.2.0 tag, so this was the final step.


Write guide for how to go from zero policy to all the policies

As a WG User who has one management cluster, one+ leaf cluster, and a handful (~10) of objects (apps/kustomizations/etc) and namespaces (~5-10), I would like to know how to write policies and properly store them in my GitOps repo, so that I can enforce them on my cluster(s).
Acceptance criteria:

[ ]  The guide explains what problem the user can solve, why the user wants to solve that problem, and a summary of the outcome
[ ]  Provides a complete list of prerequisites:

[ ]  what state does the cluster need to be in?
[ ]  do I need to have set anything up outside the cluster?
[ ]  is this guide for a development environment? or do i need a "real" env with network/dns/routing etc?

[ ] An intuitive journey through the steps
[ ] Yaml/command output is collapsed to avoid saturating the page
[ ] Screenshots with readable text, if applicable
[ ] Every copy-pastable command is tested
[ ] An example repository that shows the completed solution, which users can easily clone and apply to their cluster if they want

@MostafaMegahid Do we still need to do this ("need" being up to you and team)?


When calling plot or help, nothing happens (no display, no message, no error)

Describe the bug
Plotting or calling R help normally displays the resulting plot or help doc in a panel on the top right of the editor. Plotting and help display all work fine in my IDE, but sometimes, and it has happened already 5 or 6 times, this functionality stops working out of the blue, and nothing happens when calling plot or help, no display, no message, no error. I am not able to reproduce the error, but it has happened multiple times. Restarting the app doesn't solve the issue. The odd thing is that every time that functionality has stopped working, the issue was only solved the next time VSCode had an update and installing it, even though the update had nothing to do with the issue or R.
To Reproduce
Impossible to reproduce. It seems to happen without an event preceding it.
Do you want to fix by self? (We hope your help!)
No
(If related)setting.json

// An optional encoding to pass to R when executing the file, i.e. 'source(FILE, encoding=ENCODING)'
"r.source.encoding": "UTF-8",

// Keeping focus when running
"r.source.focus": "editor",

// Use active terminal for all commands, rather than creating a new R terminal
"r.alwaysUseActiveTerminal": false,

// Use bracketed paste mode
"r.bracketedPaste": true,

// Enable R session watcher
"r.sessionWatcher": true,

// Delay in milliseconds before sending each line to rterm (only applies if r.bracketedPaste is false)
"r.rtermSendDelay": 8,

Expected behavior
Plot or help are displayed.
Environment (please complete the following information):

OS: macOS 10.15.7
VSCode Version: 1.68.1
R Version: 4.1.1
vscode-R version: 2.5.0

Did you close vscode and reopen it so that the session watcher did not attach to the session where you create plots?
It should work again if you attach the session, or call dev.off() to close the device and plot again.


Add support for STL files

Release v1.0.0 drops built in file loaders. Loaders provided by three.js should be used instead.


Suggestion: use NoLock in Cache

I suggest to use NoLock in cache implementation. That will eliminate null checks.

make singleton from NoLock

    public static final class NoLock implements Lock{
        public static final Lock INSTANCE = new NoLock();

        public NoLock() {
        }

Use NoLock in Cache

...
public Cache(boolean disableLocks) {
            this.lock = disableLocks? NoLock.INSTANCE:  new ReentrantLock(CC.FAIR_LOCKS);
        }

        protected boolean isDisableLocks() {
            return this.lock instanceof NoLock;
        }

Remove null check

...
            @Override
            public Object get(long recid) {
                int pos = pos(recid);
                Lock lock = this.lock;
                lock.lock();
...
            @Override
            public Cache newCacheForOtherSegment() {
                return new HashTable(recids.length, isDisableLocks());
            }

I used 1). But not other two. Null check is performed anyway as part of NPE check when accessing method an a field. And microbenchmarks shows current version is bit faster.


Feature/fix mailchimp issues

Ah, can you check flake8?
I already updated basxbread to require the CI to pass, will do the same for basxconnect at some point.


DynamicModelCacheKeyFactory behavior changed since 3.0 release?

My whole dynamic filter mechanism is built on this, using a binary key to develop different models depending a dynamic key that is generated like this:
public (Boolean u, Boolean a, Boolean h) Key => (ActiveUserId != 0, ActiveAccountId != 0, ShowHidden);
Starting with deployments today (builds from yesterday or 2 days ago work fie), the alterantive models are not found anymore.
My dynamic model key factory is:
    public class DynamicModelCacheKeyFactory : IModelCacheKeyFactory
    {
        public Object Create(DbContext context)
        {
            if (context is Repository dynamicContext)
            {
                return (context.GetType(), dynamicContext.Key);
            }
            return context.GetType();
        }
    }

Not sure this relatres to an EfCore change or a change in the runtime (changing the way those generated structs are compared).
This has totally cut down redeployment (WITHOUT code change) of new compiled versions which now blow, and as such I am stuck from updateing the 2.2 runtimes and deploying anything.

@NetTecture We didn't change anything in this area and I am not sure how this worked for you before. ValueTuple shouldn't be used as the cache key since it's a value type, use a Tuple instead. See: https://github.com/aspnet/EntityFrameworkCore/blob/release/3.1/test/EFCore.Cosmos.FunctionalTests/EmbeddedDocumentsTest.cs#L426

@AndriySvyryd We've been waiting for you to triage this. Is there anything actionable on our side?

@ajcvickers No, we can close this now

@Nettecture have u solve ure problem ?

Yes, sorry. It was basically a call that was made BEFORE setting the parameters that resulted in the memory cache being initialized with always the same key. Changing db timeout actually loads the model ;)
Sorry for not coming back.

In 2.2 the code calls only once when Object is changed
   public Object Create(DbContext context)
        {
            if (context is Repository dynamicContext)
            {
                return (context.GetType(), dynamicContext.Key);
            }
            return context.GetType();
        }

Could U check in 3.0 it calls everytime when dbcontext is created !

I've opened nee one
https://github.com/aspnet/EntityFrameworkCore/issues/18611


[DO NOT MERGE]  EC2 TEST

Signed-off-by: Lokesh Mandvekar<EMAIL_ADDRESS>

cirrus support resolved the EC2 issue. Closing..


how to insert null value to datetime column ?

btw: when fetch a row from database, the null will be "0001-01-01 00:00:00", how to make it to be null ？

Just make the struct field a pointer to time.Time
type User struct {
gorm.Model
FirstPurchase *time.Time
}

I tried using MSSQL (microsoft SQL server) and it works when creating a new record. The value of 'FirstPurchase' field will be null.
But when I bind the data from SQL database to structure, the value of 'FirstPurchase' will become null no matter it has value or not.
How can it be solved?
FYI, the range of datetime of MSSQL  is January 1, 1753, through December 31, 9999 and it will have out of range error when default "0001-01-01 00:00:00" is inserted into the database.
https://docs.microsoft.com/en-us/sql/t-sql/data-types/datetime-transact-sql?view=sql-server-2017

The same issue, can not insert null to timestamp field
type StateLog struct {
	gorm.Model
	EquipmentId string
	Equipment   *Equipment
	StateId     string
	State       *State
	Enter       *time.Time
	Leave       *time.Time
}

When I insert a row into db by create function, I get blow sql statement
INSERT  INTO "smt_ep_state_logs" ("created_at","updated_at","deleted_at","equipment_id","state_id","enter","leave") VALUES ('2019-12-12 09:39:03','2019-12-12 09:39:03',NULL,'FJX01_KX_A','fault','2019-12-12 01:39:02','2019-12-12 09:39:03') RETURNING "smt_ep_state_logs"."id"

the inserted content:
StateLog<ID: 0, EquipmentId: FJX01_KX_A, StateId: fault, Enter: 2019-12-12 01:39:02 +0000 UTC, Leave: <nil>>

deleted_at field insert null as expected
but leave field change to "2019-12-12 01:39:02" automaticly, where it should be null as deleted_at


Render Jupyter Notebooks as web pages

Jupyter notebooks are a very common medium for experimentation and result communication.
Is your feature request related to a problem? Please describe.
Jupyter notebooks are currently displayed as json
Describe the solution you'd like
It would be nice to have an nbviewer server that renders notebooks to html
Describe alternatives you've considered
N/A
Additional context
unrendered example from the hub: https://huggingface.co/keras-io/deep-neural-decision-forests/blob/main/deep-neural-decision-forests.ipynb
rendered example from github: https://github.com/barbagroup/AeroPython/blob/master/lessons/01_Lesson01_sourceSink.ipynb

This is very valuable feedback @cakiki , but I think the forum (https://discuss.huggingface.co/c/site-feedback/2) is a much better place to discuss this than here (especially since we're restructuring the repo a little bit)


HDFS-14718. HttpFS: Sort response by key names as WebHDFS does

1270

 Quality gate: Passed
 Everything looks good
Details


Event is undefined is thrown when running ng-serve

🐞 bug report
Affected Package
Unknown
Is this a regression?

 Yes, the previous version in which this bug was not present was: 8.2.3
Description
Event is undefined is thrown when running ng-serve, further investigating resolves this is caused by importing a package which is built as an Angular library and exported as umd package.
When running ng serve in the project where the library is built it will run the serve without any errors.
The code that causes the issue is defined on a component exported by the library:
  @HostListener('window:beforeunload', ['$event']) onBeforeUnload(event: Event) {
    if (this.state.pendingChanges) {
      event.returnValue = true;
    }
  }

🔬 Minimal Reproduction

Create a library project containing a component that has uses a @HostListener with an Event as argument and build the files.
Use the built library in an angular project as NPM package.
Run ng serve.

🔥 Exception or Error
ReferenceError: Event is not defined
🌍  Your Environment
Angular Version:
@angular-devkit/architect          0.900.6
@angular-devkit/build-angular      0.900.6
@angular-devkit/build-ng-packagr   0.900.6
@angular-devkit/build-optimizer    0.900.6
@angular-devkit/build-webpack      0.900.6
@angular-devkit/core               9.0.6
@angular-devkit/schematics         9.0.6
@angular/cdk                       9.1.2
@angular/material                  9.1.2
@ngtools/webpack                   9.0.6
@nguniversal/builders              9.0.2
@nguniversal/common                9.0.2
@nguniversal/express-engine        9.0.2
@schematics/angular                9.0.6
@schematics/update                 0.900.6
ng-packagr                         9.0.3
rxjs                               6.5.4
typescript                         3.7.5
webpack                            4.41.2

Hi @handijk, I tried to replicate this however I wasn't able. Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.
If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.


Remove TrueCrypt from the FAQ

Little PR based on #74
I can change the text, just tell me

Ty. I would be good to provide an alternative but right now, I don't know any that's half as good. Maybe I should just link to a truecrypt fork.

I talked with a friend and the conclusion we came with is that people should encrypt important data using GnuPG, since we don't know any good storage encryption software appart the old TrueCrypt.


Windows updater and installer

An installer for Atom on Windows that auto updates
https://github.com/atom/atom/pull/3815 https://github.com/atom/atom/issues/3428 https://github.com/atom/atom/issues/2729

@kevinsawicki Awesome. Thank you very much

This is still happening https://github.com/atom/release-notes/issues/16
On Windows, the release notes are never up to date for me and Atom thinks it has to restart/shows the restart to update button even if I just did that and no update is available (blue squirrel in the bottom right). A manual restart at least removes the squirrel. The LocalStorage field release-notes:version is stuck on 144. I could probably fix it by editing that but for debugging purposes I did not yet.
@kevinsawicki Is there anything I can provide to help debug this?

@Stanzilla, please see #3757 for the main issue.

@50Wliu Aha! Thank you!


Mouse and keyboard, again

Windows: Use Raw Input for both (e.g. https://docs.microsoft.com/en-us/windows/win32/inputdev/using-raw-input)
Linux: Xlib for both (PTB just opens more "displays" to handle input)

https://github.com/aforren1/toon-rawinput is the work-in-progress Raw Input version, which seems to be working pretty well so far?


Exclude on edges option?

Hi Cellpose community,
I am really pleased with the Cellpose segmentation results and I look forward to using it in the future. To this end, I would interested to know if there is an "exclude on edges" feature, similar to that in ImageJ, within the current release? If not, is there a work-around within the Cellpose to LabelsToROI plugin pipeline that would accomplish something similar?
Thanks!

This is a good idea - for now it would be pretty simple to do as a post-processing step in a Jupyter notebook, but it would be great to implement (maybe under utils or transforms) as an optional flag. It would also be very useful for breaking apart large images to be stitched later.

certainly doable, to be clear this removes masks touching the edge of the image?
hmm for stitching you may still get duplicates that aren't touching the edges, but I guess for a rough count that's fine? I'm not sure the optimal stitching method to be honest.

@carsen-stringer Yes, the exclude on edges option would remove masks touching the edge of images.  For our purposes, this would avoid segmenting cells/objects that are only partially in view.  Like @kevinjohncutler suggested we ended up editing the mask files as a post-processing step, but an optional flag is a perhaps a better idea. Thanks!

this has been added as a command line flag in the github version, try --exclude_on_edges

Hello,
Thank you for cellpose segmentation. It is saving me a lot of time with analysis.
I tried using the exclude_on_edges for segmentation
model = models.Cellpose(gpu=True, model_type='cyto')
channels = [0,0]
masks, flows, styles, diams = model.eval(anno_imgs, diameter=None, channels=[0,0], flow_threshold=0.4, do_3D=False, exclude_on_edges=True)
but got an error
eval() got an unexpected keyword argument 'exclude_on_edges'
Is it possible to use the function in jupyter lab?
Thank you
Megha


[events] small CSS issue in events list page

[Just a suggestion, not part of the ticket] In case you feel it's worth doing :)
I was doing some tests and I created this [ignore the UI differences]

when the autocomplete is like a pill feels more consistent, this is how looks now on the page

Done in #4912
Anything with LocationAutocomplete should be a separate ticket I think, since that component is used many other places.


oxc-transform npm package: allow options argument to isolatedDeclaration to be optional?

https://github.com/oxc-project/oxc/pull/5170 added support for sourcemaps and a third "options" argument to isolatedDeclaration, but starting in v0.26.0 the third argument became required. If you omit the third argument you get:

Uncaught TypeError: Cannot convert undefined or null to object

and if you pass in {} as the third argument you get

Uncaught [Error: Missing field sourcemap] { code: 'InvalidArg' }

This differs from the transform function, where the third argument is optional and the default behavior is equivalent to passing in {sourcemap: false}.

@MichaelMitchell-at I assume you are using oxc at Airtable, feel free to dm me on Discord or twitter if you wish for a direct line of communication for higher level support.

@MichaelMitchell-at I assume you are using oxc at Airtable

Almost! Hoping to by the end of the week.
FWIW we're planning to be using the Rust crates directly now instead of the npm package, so this issue isn't blocking us :)


Add Grid Control Functions

Verison v0.10.10

Add functions and command line options to allow user to get and set grid charging and exporting modes (see https://github.com/jasonacox/pypowerwall/issues/108).
Supports FleetAPI and Cloud modes only (not Local mode)

Command Line Examples
# Connect to Cloud
python3 -m pypowerwall setup # or fleetapi

# Get Current Settings
python3 -m pypowerwall get

# Turn on Grid charging
python3 -m pypowerwall set -gridcharging on

# Turn off Grid charging
python3 -m pypowerwall  set -gridcharging off

# Set Grid Export to Solar (PV) energy only
python3 -m pypowerwall set -gridexport pv_only

# Set Grid Export to Battery and Solar energy
python3 -m pypowerwall set -gridexport battery_ok

# Disable export of all energy to grid
python3 -m pypowerwall set -gridexport never

Programming Examples
import pypowerwall

# FleetAPI Mode
PW_HOST=""
<EMAIL_ADDRESS>pw = pypowerwall.Powerwall(host=PW_HOST, email=PW_EMAIL, fleetapi=True)

# Get modes
pw.get_grid_charging()
pw.get_grid_export()

# Set modes
pw.set_grid_charging("on") # set grid charging mode (on or off)
pw.set_grid_export("pv_only")   # set grid export mode (battery_ok, pv_only, or never)

Closes #108

https://pypi.org/project/pypowerwall/0.10.10/


Re-enable smoke-tests in master

As part of updating the master branch to 5.0, smoke tests were disabled until the entire product is built. This should be re-enabled once the master branch builds through core-sdk.

This was fixed with the Preview 4 update.  https://github.com/dotnet/source-build/pull/1621


IE support

In the "First Run" part:
/***********************************************
 * FIRST RUN
 ***********************************************/

var userAgent = window.navigator.userAgent;
var isEdge    = /Edge/.test(userAgent); // thank you MS
var isChrome  = /chrome/i.test(userAgent) && !isEdge;
var isSafari  = /safari/i.test(userAgent) && !isEdge;
var isMobile  = /mobile/i.test(userAgent);
var isEnabledForBrowser = (isChrome || isSafari) && !isMobile;

Why is it Chrome/Safari only? IE could use some smoothscrolling love as well, or are there any issues I may not be aware of?

IE has built in smooth scrolling as far as I know
(Meaning one tick of mouse wheel is not just a discrete 100px jump but an animation)

I think you may be able to enable it as a configuration setting, though I am not aware exactly how, but I am on a Windows 7 PC right now and by default IE11 is not animating.

According to this it's On by default since Windows 8
http://stackoverflow.com/questions/29416448/how-to-disable-smooth-scrolling-in-ie11
Couldn't find other references yet. It's been a while since I used 7, so I might have remembered it wrong.
Can you look for more references if it's indeed W 8+ only?

sure, will check n let u know

I use Windows 8.1 with the browser Edge and the SmoothScroll not worked.

will check, thanks

Hi,
I'm also interested in the issue for Windows 8.1, any help will be appreciated.
Thanks

I'll be able to look into this over the weekend.

It seems to me that Edge is only available in Windows 10.
http://stackoverflow.com/questions/31781292/can-i-download-use-microsoft-edge-in-windows-8-1
https://www.quora.com/Can-I-download-Microsoft-Edge-for-my-Windows-8-1-laptop
Is it what you guys meant? Windows 10 & Edge?
@Giovancruz @dbdev

@Maximilianos  I just checked and Windows 7 doesn't indeed have the kind of smooth scrolling I remembered. It does have something called "smooth scrolling" but it's not really smooth, and the animation is almost nonexistent.
Windows 8 has a totally different kind of smooth scrolling, which was good enough not to be messed with.
I'll think about enabling it for Win7 + IE 11 specifically.
Not sure about older versions of IE though.

Just keep me posted guys on the IE issue, it would be nice to get something similar to the Mac version.

@dbdev You should have smooth scrolling in IE 11 under Windows 8.1.

Hi again,
do you guys have the possibility to check is there is an issue with Windows 8 and the scrolling with the mouse wheel?
Thanks a lot for a response

I have W7 and W10 but no 8.

@galambalazs thanks for the effort, let me know if I can help with something

Does the wheel scroll in Chrome works correctly in those versions?

in Chrome? yes definetely.
My issue was for IE on W7

Thanks for checking.

Regarding IE 11 i've got an issue, that when the background-Image is fixed, the Image is somehow shaking when Scrolling with the mouse-wheel. Is that a known issue?

Windows 7, 8, 10 ?

Hi.
I have Win7 & IE11 & try to fix:
var isExplorer    = /Trident\/|MSIE /.test(userAgent); // IE
var isEnabledForBrowser = (isChrome || isSafari || isExplorer) && !isMobile;

But if I press key down in IE11 I got error here:
    // our own tracked active element could've been removed from the DOM
    if (!document.contains(activeElement)) {
        activeElement = document.activeElement;
    }

I think will be good if to support and the fuc... IE :) Win7 will live few years yet.

what error?

Like this: https://github.com/skatejs/skatejs/issues/153 = "document.contains doesn't exist"

Right. Seems like easy to fix:
if (activeElement.ownerDocument != document) {
    activeElement = document.activeElement;
}

I may update the repo with this in the future, but in the meantime you can use this.

added IE 11 Win 7 support in v1.4.4, also fixed this bug above.
Let me know guys how it works
cc @Maximilianos @artfulcat

All is right. Thx.


Registry entry installed but not detected

After a fresh first install, first use was OK (face fusion). Then I installed Bark, and from there "install requirements" pops up every time I attemp to start anything. The only "uninstalled" thing is Registry, the program add the reg entry correctly and then again the same pop up, entering in a loop. The reg entry is there, I checked it. Reset bin folder, cache, no success...

Same issue for me on win10, the only way is to delete and reinstall.

I clicked the X on the popup window instead of OK or Cancel after it said it installed it, then i clicked "Refresh" and it worked.


quote image tags in vagrant setup

Helm treats tags as float64 whenever possible. This means tag "2.0"
would become just "2" which causes ImagePullBackOff.
Signed-off-by: samuel.elias<EMAIL_ADDRESS>

Coverage increased (+0.1%) to 77.902% when pulling 0972ea7e02aa935e6422e84676a40107c5130364 on samelias:quote_tags into 0dd4f7ea2e82e363c8b4f8d1e538c3da83532e31 on contiv:master.


Add new tag at the bottom

Please add the new tag as last of the list to avoid mixing up the previous set tag irder

Adding at position 1 is something stupid I did in order to show nice TAG animations. I shall change this as suggested, implementation will also be more linear


Shell command for inference on raw data

Hi,
Thanks for your paper, it's really impressive. Could you pls tell what is the shell script command to run inference on raw data?
Thanks in advance. Best wishes.

@RajNS02  Did you manage to make it work?

Thank you for your attention. There is currently no direct shell command for inference on raw data, as different structure prediction tasks have different input-output formats and evaluation measures.
If you want to run inference on custom data, you need to:

Define how the task data should be loaded and serialized in  src/data_processing/datasets.py. Both TASK_MAPPING and the task class.
Add the task config in src/data_processing/config.ini.
If you need to evaluate, define the task's evaluation measures in src/glm/evaluate.py.
Use the manager.py to inference. Examples are under src/tasks/mt.


Support Gradle configuration cache

Running SkippyAnalyze task in a project which uses Gradle's configuration cache yields the following error:
1 problem was found storing the configuration cache.
- Task `:autoinvoice:skippyAnalyze` of type `io.skippy.gradle.SkippyAnalyzeTask`: invocation of 'Task.project' at execution time is unsupported.

Corresponding E2E test: https://github.com/skippy-io/skippy-regression-suite/pull/2

Quick update: All E2E test except TestFailureTest.java pass with Configuration Cache enabled using the changes in #160 . I'm still investigating why the result property for a failed test is set incorrectly with Configuration Cache enabled.

My best guess is that it's somehow related to not having the class-dirs as inputs, so Gradle doesn't realize the task is stale (due to classpath changing), and the task is not re-run as a result. Simply adding --rerun-tasks to the arguments here might be enough to validate the hypothesis. https://github.com/skippy-io/skippy-regression-suite/blob/8192a55ca11e9793d3ce803fc7be892d5e10ceb3/src/test/java/io/skippy/test/gradle/TestFailureTest.java#L40C17-L40C73

I added some logging. From what I can tell, it's not due to tasks not being executed.
What I see:  SkippyAnalyzeTask and the test tasks use different instances of TestFailedListener. The tests tasks report failed tests to TestFailedListener@00000000. SkippyAnalyzeTask references TestFailedListener@11111111.

I will create a minimal project that demonstrates my problem and reach out to the Gradle folks for help.

FYI: https://discuss.gradle.org/t/sharing-objects-across-taks-with-configuration-cache-enabled/48598
Sample repo to re-produce the issue in isolation: https://github.com/skippy-io/gradle-configuration-cache-issue

Accidentally closed this issue when squashing the PR. Have to add additional tests and figure out how to solve that for Gradle 7.
@Kantis What version of Gradle are you using? This should be fixed in 0.0.21-SNAPSHOT if you use Gradle 8 or above.

You can use snapshot versions as follows:
buildscript {
    repositories {
        mavenCentral()
        maven { url = 'https://s01.oss.sonatype.org/content/repositories/snapshots/' }
    }
    dependencies {
        classpath 'io.skippy:skippy-gradle:0.0.21-SNAPSHOT'
    }
}

apply plugin: io.skippy.gradle.SkippyPlugin

repositories {
    maven { url = 'https://s01.oss.sonatype.org/content/repositories/snapshots/' }
}

dependencies {
    testImplementation 'io.skippy:skippy-junit5:0.0.21-SNAPSHOT'
}

This has been fixed in release 0.0.22 which has been published to Maven Central and Gradle's Plugin Portal.
PRs:

https://github.com/skippy-io/skippy/pull/169
https://github.com/skippy-io/skippy-regression-suite/pull/4


Grid doesn't display inside Tabs

I'm having trouble displaying the grid when placed inside  tabs. The tabs by the way are tabset from Angular UI Bootstrap.
One thing I noticed is that when a browser viewport resize happens (displaying dev console or when displayed inside an iframe that was resized) the grid starts to render properly.
The issue is demonstrated here: http://plnkr.co/edit/T7kQLHiqcxQ8X9uS2Bmr?p=preview
Note that when you start resizing the preview window, the grid inside the tab starts to render.
But when you switched tabs, same issue manifests again.

The usual cause of this is rendering the grid inside the tab when the tab is still hidden.
The canonical answer is to use an ng-if on the tab based on tab.active.  So the grid only tries to render when someone actually clicks on the tab (this also has the advantage of improving your application performance - angular won't be trying to evaluate all the watches for the grids that aren't visible).
(and I think you forgot to save your plunker - that plunker has no tabs in it).

Thanks for the prompt reply @PaulL1. I updated (and saved) the plunker to show 3 scenarios: Inside a single tab, inside 2 tabs, and outside tabs.
I expected I didn't need any ng-if if I am displaying the grid in a single tab only. Is that a reasonable expectation?

It ties back to http://ui-grid.info/docs/#/tutorial/108_hidden_grids.  If the grid isn't visible then it doesn't render cleanly.  Basically the tab is doing an ng-show, and the grid doesn't really like living in an ng-show.
The easiest workaround is the ng-if, then you're not taking the grid load on your system unless the user clicks on the tab.  The second-best is to let them click on the tab, put a timeout in, and call gridApi.core.handleWindowResize().

@PaulL1 thank your for pointing out that document. It makes more sense to me now. Will use ng-if as you suggested.

Just one more note @PaulL1. The ng-if workaround doesn't seem to work with Angular 1.3.x as tested here: http://plnkr.co/edit/05x8HmaJSkxPoO8RcmA8?p=preview

Often that's an angular digest cycle thing - so the tabShown is getting set and the grid is getting shown, but the tab hasn't rendered yet.  We tend to use $timeout liberally for that - but always without a time associated with it (so we're just using it to run after the digest cycle completes).
http://plnkr.co/edit/JZxj7vQP9oXGaqe2OE8i?p=preview

@PaulL1 I deleted previous comment because I made additional test and it seems now ng-if works on angular 1.3.x if width is set initially: http://plnkr.co/edit/ks2n9k4MTOa69q2PLbdY?p=preview
Of course the $timeout approach works too.

@PaulL1 Your solution of calling gridApi.core.handleWindowResize() worked like a charm. I put it in ng-click of the Accordion that i had used
<uib-accordion-group is-open="status.isEngMetOpen" ng-click="gridApi.core.handleWindowResize()">


Add versioning to codegen utility

A lot of people are going to use this utility, and over time we expect it to evolve with new features and bug fixes.
To ensure that our users have the most up to date version, this PR does the following:

Grabs the last commit to change any file that would affect the codegen utility (anything from the codegen source, or go modules relating to it)
Injects that as a version arg into the codegen build
Adds a --version flag to codegen
Updates the makefile with a target that compares the current and built versions and removes the binary if it's an old version

The upshot of this is that whenever someone runs the update scripts, if the codegen tool needs to be rebuilt, it will automatically, if it doesn't, then there's no point rebuilding it.

LGTM
Just one observation - updating things like 'openapi-gen' or 'yq' will lead to the 'codegen' rebuild, but won't touch another tools.

Just one observation - updating things like 'openapi-gen' or 'yq' will lead to the 'codegen' rebuild, but won't touch another tools.

Eventually we will drop a lot of the other binaries as we are planning to integrate the tools into the codegen tool, that's why I didn't worry about their versioning yet

WDYT about adding a check for the vendor folder and remove another binaries if it changed?

But I like this idea! Will have a think about how to track that, probably need an output file that tracks the commit any time a file is created. Problem is that will make all of the targets phony, so it expands the scope a bit as I'll have to add ifs for all of the tools

@lobziik Please review the second commit, this change makes a version check for the rest of the tools as well

/lgtm

/label qe-approved
/label docs-approved
/label px-approved


Unhandled exception - System.MissingMethodException: Method

Description
Unhandled Exception:
System.MissingMethodException: Method 'FFImageLoading.Forms.CachedImage.set_CacheDuration' not found
On loading (in this case Android app, not tried IOS yet) app was working with previous version, updated component and this resulted
Steps to Reproduce
As above
Expected Behavior
Not to crash
Actual Behavior
Unhandled Exception:
System.MissingMethodException: Method 'FFImageLoading.Forms.CachedImage.set_CacheDuration' not found
Basic Information
Screenshots

Reproduction Link / Code

Clean and rebuild of solution while running as admin user resolved this


in LargePageDrivers still BSOD

Hey here another one :)
I was verifying in WinDbg that beep.sys PageSize is LargePage
Here my WinDbg output:
lkd> !pte ffff8b8d891674b0
VA ffff8b8d891674b0
PXE at FFFFE773B9DCE8B8    PPE at FFFFE773B9D171B0    PDE at FFFFE773A2E36240    PTE at FFFFE745C6C48B38
contains 0A0000000533D863  contains 0A00000005340863  contains 8A0000010BA008E3  contains<PHONE_NUMBER>000000
pfn 533d      ---DA--KWEV  pfn 5340      ---DA--KWEV  pfn 10ba00    --LDA--KW-V  LARGE PAGE pfn 10bb67
On attempting to call the function HookDriverDispatch() I'm still getting BSOD with Violation Code ATTEMPTED_WRITE_TO_READONLY_MEMORY
To test this project I was adding every driver to LargePageDrivers.  (Which is of value REG_MULTI_SZ)
What am I missing.
OS: Windows 10 Build 1941
Help appreciated thanks :)

This doesnt work for eac anymore it closes with a game security violation sadly

Hey @Aquarius6969 I don't want to use this for any ac. I would like to replicate the blog. But no matter which driver I use I get slapped by a lovely BSOD. Even though I made sure for the Reg. entry and set it to * .
I assume you were able to run the code? Could you help me. Thanks in advance


Corporate Console - Search does not work in View Manager popup

Background

Launch Corporate Console
Login as nirupamavmentee2
Click on the company 4clamanagercomp
Click on the VIEW MANAGER for the project
Search with search criteria
Observed that search is not working

Verified and search is working as expected


HomematicIP cloud: Add logic to check accesspoint connection state

Description:
Homematic IP is a cloud based system. while hass keeps connected to the HmIP cloud the access-point might get disconnected (unplugged cable or something). This PR checks for the access-point connection and sets all connected devices to unavailable to prevent hass automations to happen based on out-of-date device states.

Thanks @sander76 for you support.
@balloob I would like to implement a "configurator" for "homematicip_cloud" for easier configuration (user has to enter the ID, press the button on the access point and enter the authentication token). Do you have a good example for me?

@mxworm we've moved away from the configurator. Instead, use Config Entries. See the docs

@balloob OK, Config Entries is the way.
Can you have a look on my PR for "homematicip_cloud": https://github.com/home-assistant/home-assistant/pull/14084

There are 129 open PRs. Please don't ask for reviews.


Implement ETA in matrix service get requests

Per the thread in the_matrix_reloaded

[ ] Method to determine ETA in new redshift/batch infrastructure is determined
[ ] ETA is populated in get requests to the matrix service

Conversation from slack
Parth Shah [8:15 AM]
@Brian Raymor In order to provide an estimate, we will need the ability to do 4 things 1) investigate query queue length 2) estimate query runtime based on # of input bundles 3) investigate batch queue length 4) estimate conversion runtime based on # of cells. However, there is a chicken and egg problem here. We can't estimate cell # (ie conversion time) until the query completes. Also, batch scales up resources so ETA is not correlated with length of batch queue. Additionally, point 4 is dependent on Marcus' changes getting merged in so that we have new #s for conversion times
Parth Shah [8:17 AM]
I will add this comment to the ticket. But summary is that this needs to be discussed with team and granularity expected needs to be established
Calvin   [4 hours ago]
From a brief conversation I had with adrienne and dave, it sounds like a general indication of progress would be a good first step. Providing a percentage based on the state table is something we can consider. Considering all the variability with Batch cold starts and concurrent load, providing inaccurate time estimates might be a worse user experience than providing none at all (edited)
Parth Shah   [3 hours ago]
A percentage is also a poor experience if not correlated with time though.
Parth Shah   [3 hours ago]
I would prefer something like 5/8 steps completed rather than a percentage for optimal experience given various moving parts

Another option is to deprecate ETA if we cannot calculate a meaningful value. Other DCP asynchronous API(s) like the Query Service do not support this feature.

@theathorn and @NoopDog - after much review, we cannot find a solution that would return a meaningful ETA, so the matrix service cannot support this property.
@mckinsel and @calvinnhieu - what do you think about annotating as deprecated so the swagger documentation is correct and we do not break the API with the data browser?
    v0_MatrixResponse:
      type: object
      properties:
        ...
        eta:
          type: string
          deprecated: true


Should debug.openDebug default to openOnFirstSessionStart?

See: https://github.com/microsoft/vscode-js-debug/issues/598#issuecomment-658530825
I think that openOnFirstSessionStart is a better default. Or maybe at least openOnSessionStart should only apply to top level sessions.
cc @weinand @isidorn

@connor4312 based on what you wrote in the linked issue aren't you proposing the default becomes openOnFirstSessionStart?

Oops, yes :)

Yeah I like this change. We can do it start of next milestone to gather feedback.
Also assigning to me and to August.

Actually I did this change couple of days ago, thus assigning to July and closing.
Code pointer https://github.com/microsoft/vscode/blob/5696babbc1dce41788bae04b1a04ad35140bebfb/src/vs/workbench/contrib/debug/browser/debug.contribution.ts#L232

To verify.

Make sure you do not have debug.openDebug in your settings
Start debugging -> make sure debug viewlet gets opened
Stop debugging. Close debug viewlet (open exporer, or close sidebar)
Start debugging -> make sure debug viewlet does not get openet


[PR] Update to SAFE stack v2.2 & Migrate to MySql #32

This issue is related to the pull request #32 .
The following list of points is copied from the pull request:
Update to only dotnetcore3.1 projects
simplify paket groups
[BUGFIX] Error with Fable solved by setting the version for Fable.SimpleJson to 3.11.0
Migrate database from MSSQL to MySql
-> Add docker-compose.yml file for MySql+Adminer instance
-> Add db.sql dump file to initialize Swate DB to MySql docker instance
-> Adjust fake.fsx to automatically start docker-compose with "OfficeDebug" target
Update README with information about docker.

In addition i though about automaticall adding the LocalConnectionString to the user secrets, but was unsure if this is wanted.
If you found room for improvement or want something changed, just tell me.

Applied requested changes:
Apply Requested Changes According to PR #32
- Return to previous fake-cli version 5.20.3
- Fix typo in README.md
- Return to inline dependencies in build.fsx
- Allow users to set MySql password during setup with optional paramater
- Remove Client side user secret

I tried to solve the problems you had running this on your machine;
Bug-Fix:

- add Fable.Elmish to Client paket.references
- add testApi and increase specificity of api forwarding
- add install.cmd and related info to README.md
- revert build.fsx inline dependencies to paket build-group


Sound Null safety

This is a request to add support for null safety to this package. See the migration guide for details about enabling null safety.

I think I won't have time to look into it much myself, but I would def review a PR.


Failed building wheel for fbprophet

pip install fbprophet
Collecting fbprophet
Using cached fbprophet-0.1.1.tar.gz
Requirement already satisfied: matplotlib in /root/anaconda2/lib/python2.7/site-packages (from fbprophet)
Requirement already satisfied: numpy in /root/anaconda2/lib/python2.7/site-packages (from fbprophet)
Requirement already satisfied: pandas>=0.18.1 in /root/anaconda2/lib/python2.7/site-packages (from fbprophet)
Requirement already satisfied: pystan>=2.14 in /root/anaconda2/lib/python2.7/site-packages (from fbprophet)
Requirement already satisfied: six>=1.10 in /root/anaconda2/lib/python2.7/site-packages (from matplotlib->fbprophet)
Requirement already satisfied: python-dateutil in /root/anaconda2/lib/python2.7/site-packages (from matplotlib->fbprophet)
Requirement already satisfied: functools32 in /root/anaconda2/lib/python2.7/site-packages (from matplotlib->fbprophet)
Requirement already satisfied: subprocess32 in /root/anaconda2/lib/python2.7/site-packages (from matplotlib->fbprophet)
Requirement already satisfied: pytz in /root/anaconda2/lib/python2.7/site-packages (from matplotlib->fbprophet)
Requirement already satisfied: cycler>=0.10 in /root/anaconda2/lib/python2.7/site-packages (from matplotlib->fbprophet)
Requirement already satisfied: pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=1.5.6 in /root/anaconda2/lib/python2.7/site-packages (from matplotlib->fbprophet)
Building wheels for collected packages: fbprophet
Running setup.py bdist_wheel for fbprophet ... error
Complete output from command /root/anaconda2/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-8Yl5PE/fbprophet/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" bdist_wheel -d /tmp/tmpICUNmGpip-wheel- --python-tag cp27:
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/fbprophet
creating build/lib/fbprophet/stan_models
INFO:pystan:COMPILING THE C++ CODE FOR MODEL anon_model_7a788197ac3493030b72020b9ffdbe7d NOW.
error: command 'gcc' failed with exit status 4

Failed building wheel for fbprophet
Running setup.py clean for fbprophet
Failed to build fbprophet
Installing collected packages: fbprophet
Running setup.py install for fbprophet ... error
Complete output from command /root/anaconda2/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-8Yl5PE/fbprophet/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-FZ012k-record/install-record.txt --single-version-externally-managed --compile:
running install
running build
running build_py
creating build
creating build/lib
creating build/lib/fbprophet
creating build/lib/fbprophet/stan_models
INFO:pystan:COMPILING THE C++ CODE FOR MODEL anon_model_7a788197ac3493030b72020b9ffdbe7d NOW.
error: command 'gcc' failed with exit status 4
----------------------------------------

Command "/root/anaconda2/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-8Yl5PE/fbprophet/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-FZ012k-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-8Yl5PE/fbprophet/

It looks like gcc isn't working correctly in anaconda.
The easiest way to install Prophet in anaconda is through conda-forge:
conda install -c conda-forge fbprophet

Alternatively, try installing gcc in Anaconda:
conda install gcc

and then try pip install again.

If that didn't work then feel free to re-open!

For pip install users change the python interpreter to python 3.7 issue will get solved. With python 3.6 interpreter pystan and fbprophet problem comes

Try installing fbprophet on pycharm. Then copy those package folders(fbprophet, fbprophet-0.5-py3.6.egg-info) from
PycharmProjects/SMAP/venv/lib/python3.6/site-packages
to .local/lib/python3.6/site-packages .
And if plotly error raises install plotly.

Try installing fbprophet on pycharm. Then copy those package folders(fbprophet, fbprophet-0.5-py3.6.egg-info) from
PycharmProjects/SMAP/venv/lib/python3.6/site-packages
to .local/lib/python3.6/site-packages .
And if plotly error raises install plotly.

Cannot install fbprophet on pycharm also


[BUG] request() got an unexpected keyword argument

After update to  schemathesis-3.19.0 this code is not working
PARAMS    = { "from": "2022-01-01T00:00:00", "to": "2022-03-01T00:00:00", "top": 1}

def test_api(case):
    case.call_and_validate(headers=HEADERS, params=PARAMS)

        try:
            with self.operation.schema.ratelimit():
>               response = session.request(**data)  # type: ignore
E               TypeError: request() got an unexpected keyword argument 'top'

/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/schemathesis/models.py:367: TypeError

I changed part of code on line 354 in schemathesis/models.py
        if params is not None:
            #_merge_dict_to(data, "params", params)
            data['params'] = params # <<<<<<<<<

After this change it is working again.
Is it bug? Or I using incorrect call of case.call_and_validate ?

Hi! It is indeed a bug, thank you for reporting!
Will fix it soon

@comato It should be fixed in 3.19.1 which was released a few minutes ago.


Idea: Partial support in createContextHelper

I like the createContextHelper shorthand, but I don't find myself able to use it very often due to a particular pattern I use in my tests. I just thought I'd throw the idea out there, but I do have a workaround if this is more of a me thing.
I often create helpers which accept a Partial<T> of the context, and have the helper merge a default value with the partial. Using this type of helper I can keep my test focussed on just the part of the context I need to change, with the rest of the context set to some reasonable default (a fake value or jest.fn() for functions).
My current workaround is pretty simple:
const createPartialContextHelper = <ContextValue,>(
  Context: React.Context<ContextValue>,
  defaultValue: ContextValue
) =>
  createHelper((value?: Partial<ContextValue>) => ({ children }) => (
    <Context.Provider value={{ ...defaultValue, ...value }}>
      {children}
    </Context.Provider>
  ));

Which would be used the same as createContextHelper:
const Context = React.createContext<{ user: User, onEnter: () => void }>(...);

const withMyContext = createPartialContextHelper(Context, {
  user: FakeUser,
  onEnter: () => {},
});

But can be called with a Partial<T>:
it("calls onEnter sometime", () => {
  const onEnter = jest.fn().mockWhatever();

  render(<Something />, {
    wrapper: wrap(withMyContext({ onEnter }))
  })

  ...
})

This is a really nice idea. Currently this is addressed by using composite helpers. With a single call to createHelpers()  you can create multiple helpers each of which is dedicated to a separate part of the thing that you're trying to mock.
So for example to create the helpers:
const [withUser, withOnEnter] = createHelpers(
  (
    [user]: [User],
    [onEnter]: [() => void]
  ) =>
    ({ children }) => (
      <Context.Provider value={{
        user: user ?? fakeUser,
        onEnter: onEnter ?? () => {},
      }}>
        {children}
      </Context.Provider>
    )
);

And then you can use them like:
// Just provide a user, use the default onEnter:
render(<Something />, { wrapper: wrap(withUser(someUser)) });

// Just proved a mock onEnter, use the default user:
render(<Something />, { wrapper: wrap(withOnEnter(jest.fn())) });

// Provide both:
render(<Something />, { wrapper: wrap(withUser(someUser), withOnEnter(jest.fn())) });

I do like having smaller, more specific helpers, with names that make it very obvious which part of the complex thing you are interested in mocking. However, your partial approach is a lot simpler. I think there's room for both approaches in the library.
I'd be open to a PR if you want to do one 🙂


Remove package-lock.json from root dir

Can you please remove package-lock.json from root directory as long as we have both clients (during development). This is required to silence a yarn warning.

Should not be a problem. We gonna need it in client root though.


Can't start on MacOS: chill'ax error: not started

I did:
git checkout 1.0.20170717233424

followed by:
 bin/wasabi.sh start

and am seeing:
Successfully built 9f3c7da36c97
wasabi: starting
4a14bc2da8b4ba73f61de270613b3c5100f29bad08cfb72897909228d7059a1d
chill'ax error: not started

usage: container.sh [options] [commands]

options:
  -v | --verify [ true | false ]         : verify installation configuration; default: false
  -m | --migration [ true | false ]      : refresh cassandra migration scripts; default: false
  -s | --sleep [ sleep-time ]            : sleep/wait time in seconds; default: 3
  -h | --help                            : help message

commands:
  start[:wasabi,cassandra,mysql,docker]  : start all, wasabi, cassandra, mysql, docker
  stop[:wasabi,cassandra,mysql,docker]   : stop all, wasabi, cassandra, mysql, docker
  console[:cassandra,mysql]              : console all, cassandra, mysql
  status                                 : status
  remove[:wasabi,cassandra,mysql]]       : remove all, wasabi, cassandra, mysql

@llambda is this all of the output? can you try starting each service individually? I'm betting that the mysql container is having issues coming up

I'm having the same issue.
Successfully tagged wasabi-main:mshai4-1525274647
Successfully tagged wasabi-main:latest
wasabi: starting
27b24b6714d55fef3f213a9ce275f8cafbed0f2116bd6d68dc7cc25554460793
chill'ax error: not started
usage: container.sh [options] [commands]

Having the same issue, anyone have more details on a workaround or how to go about debugging this?
It seems 'wasabi.sh status' is printing this out ("start:wasabi" calls "status") .
In 'wasabi.sh status', "wget -q --spider --tries=20 --waitretry=3 http://localhost:8080/api/v1/ping" isn't working.
I'm seeing:
$ wget --spider http://localhost:8080/api/v1/ping
Spider mode enabled. Check if remote file exists. --2018-05-08 19:39:52--  http://localhost:8080/api/v1/ping Resolving localhost (localhost)... <IP_ADDRESS> Connecting to localhost (localhost)|<IP_ADDRESS>|:8080... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying.

👋 i'm not a maintainer but I can lend a hand if you are having issues.
Can you attach the logs from the docker containers (wasabi, mysql, cassandra)? Most problems I have encountered starting up on mac can be traced back to one of those underlying systems.

Thanks @brendanjryan . I added the log files to the comment above. It seems that there is a problem with the injector.

My docker logs for the wasabi container looks the same, where the root issue is:
"Caused by: com.datastax.driver.core.exceptions.InvalidQueryException: Unknown identifier source_url"
I've found this to be broken by this commit - https://github.com/intuit/wasabi/commit/afbfd8fdb1f5072907c37b68a00e80bc55a19335  from 13 days ago.  I reverted my local setup back to its parent commit - https://github.com/intuit/wasabi/commit/1d2f066541b176ee84c00dc9516b370553b76a40 - rebuilt, and restarted and that resolved the issue for me.

This is my error:
[INFO] --- maven-surefire-plugin:2.11:test (default-test) @
wasabi-experiment-objects ---
[INFO] Surefire report directory:
/Volumes/HDD/Projects/Wasabi/wasabi/modules/experiment-objects/target/surefire-reports
[INFO] Using configured provider
org.apache.maven.surefire.junitcore.JUnitCoreProvider

T E S T S

Exception in thread "main" java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at
java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:510)
at
java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:522)
Caused by: java.lang.RuntimeException: Class java/util/UUID could not be
instrumented.
at
org.jacoco.agent.rt.internal_8ff85ea.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:140)
at
org.jacoco.agent.rt.internal_8ff85ea.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:101)
at
org.jacoco.agent.rt.internal_8ff85ea.PreMain.createRuntime(PreMain.java:55)
at org.jacoco.agent.rt.internal_8ff85ea.PreMain.premain(PreMain.java:47)
Results :
... 6 more
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
Caused by: java.lang.NoSuchFieldException: $jacocoAccess
at java.base/java.lang.Class.getField(Class.java:1958)
at
org.jacoco.agent.rt.internal_8ff85ea.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:138)
... 9 more
FATAL ERROR in native method: processing of -javaagent failed
[INFO]
/bin/sh: line 1: 14354 Abort trap: 6
/Library/Java/JavaVirtualMachines/jdk-10.0.1.jdk/Contents/Home/bin/java
'-javaagent:/Users/mshai4/.m2/repository/org/jacoco/org.jacoco.agent/0.7.9/org.jacoco.agent-0.7.9-runtime.jar=destfile=/Volumes/HDD/Projects/Wasabi/wasabi/modules/experiment-objects/../target/jacoco.exec,append=true,excludes=com/intuit/wasabi/tests/**/*.class'
-jar
/Volumes/HDD/Projects/Wasabi/wasabi/modules/experiment-objects/target/surefire/surefirebooter1553630742891458696.jar
/Volumes/HDD/Projects/Wasabi/wasabi/modules/experiment-objects/target/surefire/surefire15263645749158983248tmp
/Volumes/HDD/Projects/Wasabi/wasabi/modules/experiment-objects/target/surefire/surefire7617235667786685019tmp
[INFO]
------------------------------------------------------------------------
[INFO] Skipping wasabi
[INFO] This project has been banned from the build due to previous
failures.
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] wasabi 1.0.20180427082617-SNAPSHOT .................
SUCCESS [  5.121
s]
[INFO] wasabi-experiment-objects ..........................
FAILURE [  3.898
s]
[INFO] wasabi-export ...................................... SKIPPED
[INFO] wasabi-assignment-objects .......................... SKIPPED
[INFO] wasabi-exceptions .................................. SKIPPED
[INFO] wasabi-analytics-objects ........................... SKIPPED
[INFO] wasabi-authentication-objects ...................... SKIPPED
[INFO] wasabi-eventlog .................................... SKIPPED
[INFO] wasabi-cassandra-datastax .......................... SKIPPED
[INFO] wasabi-authorization-objects ....................... SKIPPED
[INFO] wasabi-user-directory .............................. SKIPPED
[INFO] wasabi-feedback-objects ............................ SKIPPED
[INFO] wasabi-auditlog-objects ............................ SKIPPED
[INFO] wasabi-database .................................... SKIPPED
[INFO] wasabi-repository-datastax ......................... SKIPPED
[INFO] wasabi-experiment .................................. SKIPPED
[INFO] wasabi-assignment .................................. SKIPPED
[INFO] wasabi-util ........................................ SKIPPED
[INFO] wasabi-analytics ................................... SKIPPED
[INFO] wasabi-auditlog .................................... SKIPPED
[INFO] wasabi-event-objects ............................... SKIPPED
[INFO] wasabi-event ....................................... SKIPPED
[INFO] wasabi-email ....................................... SKIPPED
[INFO] wasabi-feedback .................................... SKIPPED
[INFO] wasabi-authentication .............................. SKIPPED
[INFO] wasabi-authorization ............................... SKIPPED
[INFO] wasabi-api ......................................... SKIPPED
[INFO] wasabi-functional-test ............................. SKIPPED
[INFO] wasabi-main ........................................ SKIPPED
[INFO] wasabi-swagger-ui 1.0.20180427082617-SNAPSHOT ...... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 11.561 s
[INFO] Finished at: 2018-05-09T16:37:11-05:00
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test)
on project wasabi-experiment-objects: Error occured in starting fork,
check output in log -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :wasabi-experiment-objects
error: invalid: mvn  -Pdevelopment clean
org.jacoco:jacoco-maven-plugin:prepare-agent findbugs:check test package
javadoc:aggregate
usage: build.sh [options]
options:
-b | --build [ true | false ]  : build; default: false
-p | --profile [profile]       : build profile; default: development
-t | --test [ true | false ]   : test; default: false
-h | --help                    : help message
wasabi: [Start] creating keyspace and migration schemas
cqlsh  --cqlversion="3.2.1"  -e "CREATE KEYSPACE IF NOT EXISTS
wasabi_experiments WITH replication = {'class' : 'SimpleStrategy',
'replication_factor' : 1};" --username= --password="" wasabi-cassandra 9042
java -jar -Dcassandra.migration.keyspace.name=wasabi_experiments
-Dcassandra.migration.cluster.port=9042
-Dcassandra.migration.cluster.username=
-Dcassandra.migration.cluster.password=
-Dcassandra.migration.scripts.locations=filesystem:/wasabi/mutation
-Dcassandra.migration.cluster.contactpoints=wasabi-cassandra
/wasabi/cassandra-migration.jar migrate
Cassandra Migration 0.9
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
Connected to cluster: Test Cluster
Data center: datacenter1; Host: wasabi-cassandra/<IP_ADDRESS>
Current version of keyspace wasabi_experiments: 036
Keyspace wasabi_experiments is up to date, no migration necessary
wasabi: [DONE] creating keyspace and migration schemas
Warning: Using a password on the command line interface can be insecure.
wasabi: building
Sending build context to Docker daemon  53.21MB
Step 1/22 : from centos
---> e934aafc2206
Step 2/22 : ENV WASABI_MODULE wasabi-main
---> Using cache
---> 0bf7579d09f2
Step 3/22 : ENV WASABI_UI_MODULE wasabi-ui-main
---> Using cache
---> dd2719161f17
Step 4/22 : ENV WASABI_PORT 8080
---> Using cache
---> 2573d1e30ef9
Step 5/22 : ENV WASABI_JMX_PORT 8090
---> Using cache
---> a2ed7423cf28
Step 6/22 : ENV WASABI_DEBUG_PORT 8180
---> Using cache
---> a68e196becf5
Step 7/22 : ENV WASABI_SRC_DIR
wasabi-main-1.0.20180427082617-SNAPSHOT-development
---> Using cache
---> 18963b9e983c
Step 8/22 : ENV WASABI_HOME
/usr/local/wasabi-main-1.0.20180427082617-SNAPSHOT-development
---> Using cache
---> ff93c37f061f
Step 9/22 : ENV WASABI_JAVA_OPTIONS ""
---> Using cache
---> 2952879b819a
Step 10/22 : ENV JDK_MAJOR_VERSION 8u131
---> Using cache
---> b784ad9d6406
Step 11/22 : ENV JDK_MINOR_VERSION b11
---> Using cache
---> df54236263fc
Step 12/22 : ENV JDK_VERSION ${JDK_MAJOR_VERSION}-${JDK_MINOR_VERSION}
---> Using cache
---> 81fb68a173e4
Step 13/22 : RUN yum -y update && yum install -y wget
---> Using cache
---> ded0b885289f
Step 14/22 : RUN wget --no-check-certificate --no-cookies --header "Cookie:
oraclelicense=accept-securebackup-cookie"
http://download.oracle.com/otn-pub/java/jdk/${JDK_VERSION}/d54c1d3a095b4ff2b6607d096fa80163/jdk-${JDK_MAJOR_VERSION}-linux-x64.rpm
&&
rpm -ivh jdk-${JDK_MAJOR_VERSION}-linux-x64.rpm && rm
jdk-${JDK_MAJOR_VERSION}-linux-x64.rpm
---> Using cache
---> 3fdf79244108
Step 15/22 : COPY ./ ${WASABI_HOME}/
---> Using cache
---> a26e0a029650
Step 16/22 : COPY entrypoint.sh /usr/local/bin/
---> Using cache
---> dc1710f80954
Step 17/22 : RUN sed -i -e $'s/1>>.*2>&1//' ${WASABI_HOME}/bin/run
2>/dev/null;
---> Using cache
---> 94cd96e6f941
Step 18/22 : EXPOSE ${WASABI_PORT}
---> Using cache
---> cf58122b2a76
Step 19/22 : EXPOSE ${WASABI_JMX_PORT}
---> Using cache
---><PHONE_NUMBER>72
Step 20/22 : EXPOSE ${WASABI_DEBUG_PORT}
---> Using cache
---> 2cfb021bb4aa
Step 21/22 : ENTRYPOINT ["entrypoint.sh"]
---> Using cache
---> 663209f3c3f0
Step 22/22 : CMD ["wasabi"]
---> Using cache
---> 1d2df2465eb0
Successfully built 1d2df2465eb0
Successfully tagged wasabi-main:mshai4-1525901846
Successfully tagged wasabi-main:latest
wasabi: starting
595b58482e889a8f41c0d40f3673792b3d0b6c8b21294b7c84cf669596984faa
chill'ax error: not started
usage: container.sh [options] [commands]
options:
-v | --verify [ true | false ]         : verify installation
configuration; default: false
-m | --migration [ true | false ]      : refresh cassandra migration
scripts; default: false
-s | --sleep [ sleep-time ]            : sleep/wait time in seconds;
default: 3
-h | --help                            : help message
commands:
start[:wasabi,cassandra,mysql,docker]  : start all, wasabi, cassandra,
mysql, docker
stop[:wasabi,cassandra,mysql,docker]   : stop all, wasabi, cassandra,
mysql, docker
console[:cassandra,mysql]              : console all, cassandra, mysql
status                                 : status
remove[:wasabi,cassandra,mysql]]       : remove all, wasabi, cassandra,
mysql
Any thing I can do better here?
On Wed, May 9, 2018 at 3:16 PM, John Wang<EMAIL_ADDRESS>wrote:

My docker logs for the wasabi container looks the same, where the root
issue is:
"Caused by: com.datastax.driver.core.exceptions.InvalidQueryException:
Unknown identifier source_url"
I've found this to be broken by this commit - afbfd8f
https://github.com/intuit/wasabi/commit/afbfd8fdb1f5072907c37b68a00e80bc55a19335
from 13 days ago. I reverted my local setup back to its parent commit -
1d2f066
https://github.com/intuit/wasabi/commit/1d2f066541b176ee84c00dc9516b370553b76a40

rebuilt, and restarted and that resolved the issue for me.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/intuit/wasabi/issues/265#issuecomment-387862150, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGQEANpJ-PJIAYql7_I0hTBQuwTUc2tks5tw06dgaJpZM4Oc-Pd
.

fwiw - My workaround was done on an Ubuntu box (it doesn't build on my Mac for some reason, haven't had a chance to look into why yet).
@symadept the exceptions you're seeing from the test cases shouldn't matter.  Looking towards the tail end of your output, it looks like your docker containers are up; and you can verify by running "docker ps" which should print out something like below:
:~$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                                                     NAMES
06d7988219cb        wasabi-main         "entrypoint.sh wasabi"   23 hours ago        Up 23 hours         <IP_ADDRESS>:8080->8080/tcp, <IP_ADDRESS>:8090->8090/tcp, <IP_ADDRESS>:8180->8180/tcp    wasabi-main
64acc3782bda        mysql:5.6           "docker-entrypoint..."   2 days ago          Up 24 hours         <IP_ADDRESS>:3306->3306/tcp                                                    wasabi-mysql
ea50488a93fd        cassandra:2.1       "docker-entrypoint..."   2 days ago          Up 24 hours         7000-7001/tcp, <IP_ADDRESS>:9042->9042/tcp, 7199/tcp, <IP_ADDRESS>:9160->9160/tcp   wasabi-cassandra
Check the docker logs in your wasabi container by doing "docker logs -f <container_id>"  (docker ps will give you your container id) and share any errors/exceptions you see in those logs

@j33wang Thanks! I can confirm your analysis and the workaround. After rebuilding based on 1d2f066 it works.

I had the same problem on Ubuntu 16.04 (x64) in Virtualbox, and checking out 1d2f066 allowed me to get it to start. It would be nice if we didn't have to workaround this error in this way.

---> 974cb2c7c819
Successfully built 974cb2c7c819
Successfully tagged wasabi-main:dongbiaozheng-1530076181
Successfully tagged wasabi-main:latest
wasabi: starting
i had the same problem on MAC,
chill'ax error: not started
usage: container.sh [options] [commands]
options:
-v | --verify [ true | false ]         : verify installation configuration; default: false
-m | --migration [ true | false ]      : refresh cassandra migration scripts; default: false
-s | --sleep [ sleep-time ]            : sleep/wait time in seconds; default: 3
-h | --help                            : help message
commands:
start[:wasabi,cassandra,mysql,docker]  : start all, wasabi, cassandra, mysql, docker
stop[:wasabi,cassandra,mysql,docker]   : stop all, wasabi, cassandra, mysql, docker
console[:cassandra,mysql]              : console all, cassandra, mysql
status                                 : status
remove[:wasabi,cassandra,mysql]]       : remove all, wasabi, cassandra, mysql

Still getting the same issue on Mac OS 10.11 today.
Reverting to 1d2f066 also worked for me. Thanks @j33wang

Mac OS High Sierra, version 10.13.4, Reverting to 1d2f066 also worked for me too, Thanks @j33wang.

Thanks @j33wang , reverting to 1d2f066 worked for me too! This has been around for a while, would be nice to have a fix for it...

reverting to 1d2f066, rebuilding  and starting did not work for me on mac os 10.13.6

I am still getting chill'ax error: not started even after reverting to 1d2f066 on mac os 10.13.6 (17G65).


Broken links from Carbon home page

The links on Carbon home page are broken. Getting started, components, and guideline links are broken

Its been fixed but not pushed to the website.


Another action scheme and basic feature engineering.

If the build fails, that's not me. Only uploaded a notebook

Again, don't pull out python 3.7 from the supported versions, or each time I have to revert that commit to be able to merge it.
It should be however fixed and should pass all tests now


Docs and programs are opened at background

When I select an image (.jpg format) it automatically opens in front of the app, but .docx, .pdf or dierct accesses are opening behind the app

Duplicate of #985.


show menu on left-click of system tray icon, not just right-click

pass-winmenu doesn't do anything when you left-click the system tray icon; there really isn't much that'd make sense to have happen.
given that the right-click menu is the most likely mouse-driven thing to do, it'd make sense to show that menu regardless of which button was used. :)

Sensible suggestion, thanks! I've implemented it and will include it in the next release.

Implemented as of v1.11.


Unable to create Git repositories

Hello!

Vote on this issue by adding a 👍 reaction
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Issue details
I am unable to create a new repository using the Git resource and initialization type of Cleanor Uninitialized.
Steps to reproduce
import pulumi_azuredevops as ado

project = ado.Project(
    "testproject",
    description="Test Project Description",
    version_control="Git",
    visibility="private",
    work_item_template"Agile"
)

repo = ado.Git(
    "repo",
    project_id=project.id,
    initialization=ado.GitInitializationArgs(
        init_type="Clean",
    ),
)

Expected: A new repository "repo" to be created.
Actual: Pulumi errors out:
azuredevops:index:Git (repo):
    error: azuredevops:index/git:Git resource 'repo' has a problem: "initialization.0.service_connection_id": all of `initialization.0.service_connection_id,initialization.0.source_type,initialization.0.source_url` must be specified

If I specify a source_url of another repo and change the init_type to Clone it all works fine.

Got into the same issue with the version v2.3.0.

Same issue with v2.3.1.
Workaround: you can try to add dummy values for required fields (ServiceConnectionId, SourceType and SourceUrl) just to bypass the validation, like this:
repository, err := azuredevops.NewGit(ctx, repoName, &azuredevops.GitArgs{
	Name:          pulumi.String(repoName),
	ProjectId:     pulumi.String(project.Id),
	DefaultBranch: pulumi.Sprintf("refs/heads/main"),
	Initialization: azuredevops.GitInitializationArgs{
		InitType: pulumi.String("Clean"),
		ServiceConnectionId: pulumi.String(""),
		SourceType:          pulumi.String("Git"),
		SourceUrl:           pulumi.String("https://repo.com"),
	},
})

Note: if you already have a git repo using provider previous version (2.1.1), Pulumi will try to delete and create it again after this change.
(Go SDK, not tested in .NET)

This is related to https://github.com/pulumi/pulumi-terraform-bridge/issues/540

I believe there are two paths to addressing this:

Implement a complete fix for https://github.com/pulumi/pulumi-terraform-bridge/issues/540, which we likely need to be very careful with as this may have subtle interactions with other providers.
Fork the upstream to remove the default values for two of the affected properties - which is presumably what is causing trouble here (the combination of default and required_with).  https://github.com/microsoft/terraform-provider-azuredevops/blob/81649c07e6bc69b2f4d2f0a0252a33246d7bdab0/azuredevops/internal/service/git/resource_git_repository.go#L128C25-L128C25

I looked into this and compared what we do here with what terraform does.
TLDR: I don't think this is a problem with us handling RequiredWith but rather with the provider using a default of an empty string to mean null. TF seems to handle this by doing config validation before actually setting the defaults.
This is my understanding of the problem:
The provider sets a default value for service_connection_id of an empty string but it kind of means null there, since the empty string is not a valid value for this.
Terraform seems to do the config validation BEFORE getting the defaults from the provider. This means that the validation passes there since the value for service_connection_id is still null. Terraform then gets the default from the provider (an empty string) and then passes it to the planning phase.
That then yields some errors (.initialization[0].service_connection_id: planned value cty.StringVal("") for a non-computed attribute) but they tolerate them because this is provider is using a LegacyTypeSystem.
In tf-bridge we seem to do the reverse - we set the defaults from the schema and only then pass the config for validation which yields the error about the RequiredWith.
I tested moving around the validation in terraform and it does yield the same error if I first apply the default to the config.
I also tested ignoring the error in tf-bridge and everything works fine. The provider seems to handle the empty string values which actually mean null fine.
Should we re-order the operations here? Alternatively we could add some condition about ignoring this type of errors in ValidateResource but I'm not sure how to make certain this doesn't yield any false negatives.

We just released https://github.com/pulumi/pulumi-azuredevops/releases/tag/v2.14.1 which contains a fix for this issue.