Correct Path to WSDLProcessor in README

Purpose
The README instructions for running the WSDLProcessor include incorrect path to the project folder. This corrects the path in the cd command.
Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone https://github.com/Azure-Samples/api-management-schema-import.git

Test the code
Run the code samples in the 'Run WSDLProcessor' of the README in CMD.

## What to Check
Ensure the steps take you to the correct project directory and allow you to build it.

Thanks for your contribution!


Update intro-to-pfx.md

Learn Build status updates of commit e26b052:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

powerapps-docs/cards/make-a-card/power-fx/intro-to-pfx.md
:white_check_mark:Succeeded

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


Patch ImprovedStrategies metadata

closes https://github.com/KSP-CKAN/NetKAN/issues/554
This change should make stuff load in the right order for the mod to work based on the issuereport linked above.

#rebuild


[CLOSED] Provide better error handling methods

 Issue by ananthanandanan
Monday Apr 13, 2020 at 06:08 GMT
Originally opened as https://github.com/Aniketh01/NaWaB/issues/12

 Comment by Aniketh01
Wednesday Apr 15, 2020 at 07:48 GMT

@ananthanandanan , @iammarco11 Please do more research on how to add better error handling into this project, handling tweepy error codes, python3 based error handling and other stuff. Make sure the discussion on this happens here as to keep note no what all have to be fixed and what's not.

 Comment by Aniketh01
Thursday Apr 23, 2020 at 17:04 GMT

This is how proper logging should be handled: https://docs.python.org/2.3/lib/node304.html


[WIP] New landing page, implements #7265

Summary
Implements new landing page as discussed in #7265
Test plan
Run website locally, make sure it looks as the design.
Dec 30 progress:

70% of the homepage implemented using new design.

ToDo:

[x] Cards section
[ ] Main information (white text over gray background)
[ ] Yellow bullet points
[ ] Philosophy

Notes:
Docusaurus fulfills its purpose, but its CSS architecture leaves much to be desired, making really hard to make some changes, also it doesn't support custom Navigation bar, only Footer, I am expressing these concerns because you will find some ugly CSS that could be completely avoided if Docusaurus was different.

So cool! It's deployed here: https://deploy-preview-7566--jest-preview.netlify.com/

Docusaurus fulfills its purpose, but its CSS architecture leaves much to be desired, making really hard to make some changes

Will be improved in the next version: https://docusaurus.io/blog/2018/09/11/Towards-Docusaurus-2#layout
Not sure if an alpha is published, or viable to use?

Do'h, I forgot to uncomment my progress :/

Will be improved in the next version: https://docusaurus.io/blog/2018/09/11/Towards-Docusaurus-2#layout

That's good to know, It is there any progress or proposition about how exactly it is going to be?

I think to one way to simplify the header CSS, is to make the custom nav CSS only affect the index page - then the rest of the pages can use the navigation bar etc. Which at least scopes the hacks to a single page.

We have a working implementation of the cards in #7567 - so I've ticked that for you 👍

I think Jest's philosophy hasn't changed much over the years:

Fast
Feature-rich
Easy to use out of the box but highly configurable
Approachable with familiar APIs
Extensible
Well documented
Fun!

How about:

Jest is a JavaScript testing framework designed to ensure correctness of any JavaScript codebase. It allows you to write tests with its approachable, familiar and feature-rich APIs that give you results quickly. Jest is extensively documented, requires little configuration and can be extended to match your requirements. Jest makes testing delightful.

?

The cards are fantastic. I have some thoughts on how I think it could lead to a better first impression:

Can we make the initial animation a bit faster? Like, let's turn one card around within ~1s of opening the page. Otherwise we make it seem like Jest is slow.
I'd like for at least 2 cards to be green at all times. It could be 2, 3 or 4 green cards, and at most 2 red cards. It doesn't give a good impression if the cards "fail" on the first visit to the website.


Remove build step from Dockerfile

Feature Suggestion
Remove the initial build step in the Dockerfile and depend on that being run on the host.
Possible Implementation
Remove the first step in the multistage build, copy contents from app build output instead.
Context
Running the build inside the docker is pretty finicky. There are a lot of individual files to copy in and it makes the build pretty fragile. It is also ridiculously slow as yarn install has to do everything from scratch. I think it makes more sense to simply remove the first step and rely on the app to be bundled on the host before building the container.
I'm usually prefer having everything in a single Dockerfile, but in this case I don't think it makes much sense. Latest related issue is #436

I'll take it, PR coming soon.

@paulpach Thanks, but hold up! This is already in review: #446
Dunno why GitHub didn't pick up the link, guess it has to be in the original PR body?

Fixed by #446


Combine two MultiSeries objects

We need a way to combine two MultiSeries objects. I'm opening this as a separate action item, but I actually think it can be handled in the same way as #18 - via a MultiSeries.add method.
MultiSeries.add(MultiSeries) could detect accept different types (Series, MultiSeries, list of Series) and handle them appropriately.

yes, and same as #18: overloaded + or & method would be most valuable as a shorthand.

the new Series.equals() method should help

from our side, is this one covered by https://github.com/LinkedEarth/paleoPandas/issues/18, or is there anything else which needs doing here?

it is not covered.  See the latest version of Paleopandas Playground.ipynb for an illustration. AFAICT, #18 only allows to a a Series to a MultipleSeries object, not to combine two MultipleSeries objects. This still needs to be done by the end of the project, but I'm guessing won't be huge ordeal?

Addressed by #354 . Still needs a notebook tutorial, or at least informative docstrings on and and add to highlight usage differences.


Fix RVM Ruby prompt on superjarin theme

It seems like the test to see if RVM is installed was not working.
This fix may also apply to the other themes that show the RVM Ruby version in the prompt, but I didn't want to mess around with the other themes because I haven't tested them.

Addressed by changes in #922


SSR issue using useLayoutEffect() with Nextjs

I use useHover in my next app and have this error message:
Warning: useLayoutEffect does nothing on the server, because its effect cannot be encoded into the server
renderer's output format. This will lead to a mismatch between the initial, non-hydrated UI and the intended
UI. To avoid this, useLayoutEffect should only be used in components that render exclusively on the client.
See https://reactjs.org/link/uselayouteffect-ssr for common fixes.

Solution:
Something like:
import { useEffect, useLayoutEffect } from 'react';

const useIsomorphicLayoutEffect =
  typeof window !== 'undefined' ? useLayoutEffect : useEffect;

export default useIsomorphicLayoutEffect;

+1


How the linear resizing is supposed to work?

When I resize an image in GIMP, I got completely different result.
For example, in DCV I do this:
// w == 3; The image is a 2MP RGBA photo.

auto slice = image.sliced;
writeln(slice[0, 0, 0 .. $]);
auto thumbnail = slice.resize!linear([w, w]);
auto rgb = thumbnail[0 .. $, 0 .. $, 0 .. 3];
writeln(rgb);

and I got this:
[196, 198, 249, 255]
[[[196, 198, 249], [156, 166, 189], [82, 59, 100]], [[231, 163, 178], [35, 39, 34], [104, 98, 122]], [[141, 120, 119], [26, 36, 44], [169, 141, 130]]]

The first pixel of the downscaled image is the same as the first pixel of original image.
This is not what I expect.

The first pixel of the downscaled image is the same as the first pixel of original image.

Yes, the first and the last pixels remain the same as in input image, as shown in the [example] (https://github.com/ljubobratovicrelja/dcv/tree/master/examples/imgmanip).

This is not what I expect.

Weighting for interpolation is completely in favor of the first element there. Should it be different?
What did you expect?  Also, what did gimp give you?

Thanks for your response.
I supposed, the first result pixel was the average value of the corresponding part of the source image (in downsampling case).
Now, I am confused. If the first pixel is the first pixel of the source image and the right-top pixel is the right-top pixel of the source image, then, what is the middle-top pixel? The average value of the whole row except for the first and the last pixels?

That would be some another interpolation scheme. You can see how bilinear implementation works [here] (https://en.m.wikipedia.org/wiki/Bilinear_interpolation).  Sorry I'm not able to give you more elaborated example at the moment, hope you can understand it from Wikipedia. Also, you can take a look at the  [2d resizing] (https://github.com/ljubobratovicrelja/dcv/blob/master/source/dcv/imgproc/imgmanip.d#L522),  and [bilinear interpolation] (https://github.com/ljubobratovicrelja/dcv/blob/master/source/dcv/imgproc/interpolate.d#L135)  source code. It's not too complicated to understand.

Ok, thanks.


Formatting fails to update files due to path quoting issues

Black seems to not be working, and initially I thought it was a bug in my code or something, but running python -m black main.py works just fine. What's happening?
Environment data

VS Code version: 1.49.1
Extension version (available under the Extensions sidebar): v2020.9.111407
OS and version: Windows 10
Python version (& distribution if applicable, e.g. Anaconda): 3.8.5
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
Relevant/affected Python packages and their versions: black: 20.8b1
Relevant/affected Python-related VS Code extensions and their versions: None
Value of the python.languageServer setting: Jedi

Expected behaviour
Code to be formatted after running "Format Document" (Shift+Alt+F).
Actual behaviour
Black runs for a split second and nothing happens.
Steps to reproduce:

Have a line over 80 characters long which should be formatted
Run formatter
Be dissapointed at your still ugly code.

Logs

> f:\Programs\Python\Lynez Experiment\env\Scripts\python.exe "D:/Data/Microsoft Visual Studio Code/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py" black --diff --quiet "f:\Programs\Python\Lynez Experiment\main.py"
cwd: f:\Programs\Python\Lynez Experiment
> f:\Programs\Python\Lynez Experiment\env\Scripts\python.exe "D:/Data/Microsoft Visual Studio Code/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py" black --diff --quiet "f:\Programs\Python\Lynez Experiment\main.py"
cwd: f:\Programs\Python\Lynez Experiment

Note: Issue #14054 seems to have the same problem, but nobody seems to have an answer.

I'd be more than happy to help, if anyone told me how to.

@DRACL10N #14054 was due to incorrect argument configuration provided by the user. In your case I would manually run the command:
f:\Programs\Python\Lynez Experiment\env\Scripts\python.exe "D:/Data/Microsoft Visual Studio Code/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py" black --diff --quiet "f:\Programs\Python\Lynez Experiment\main.py"

and see if that returns the diff correctly. If there are any warnings are errors printed or if it takes too long then formatting will not work. If there are no errors or warnings, then please share your settings and if possible the repro code.

@karthiknadig it gives me the exact same out as if I were to press Shift-Alt-F. It shows me where it would change something, but does nothing about it.

At the very least it would be great to know what file in the extension tells VSCode how to run black. Tell me that and I will fix this myself, since nobody else seems to care too much.

I have the same issue. Looking at the output console, I see this:
I:\Languages\Python\envs\myenv\Scripts\python.exe "c:/Users/XXX/.vscode/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py" black --diff --quiet i:\Projects\my-project\main.py
cwd: i:\Projects\my-project

When running black directly on the command line with --diff --quiet or using the above command, I get the expected output from black.
I want to add that this happens on project where everything was working before, without any changes to the virtual environment, and thus to the black version, so this is most likely due to a recent update.

Thank you, I'm so glad to see I'm not alone. I'm thinking for a temporary fix we could find the file that tells VSCode to give black the --diff --quiet args, then it would start working again in theory.

@karthiknadig I would like to add the "needs PR" label to this please, as I've decided to do it myself

@DRACL10N We investigate issues in order based on priority and severity, which includes the impact it has on your ability to use the extension to do productive work, and the number of people affected. If other users come forward and leave a comment demonstrating they are seeing/reproducing the problem then we will raise this issue's priority.

VSCode to give black the --diff --quiet args and remove them, then it would start working again in theory.

They way formatting works with VS Code is we use --diff to generate text edits. These are then sent to VS Code Editor to apply those edits. This allows you to use editor features such like undo/redo etc. If you get rid of --diff then black will attempt to format the file in place. This will mean that VS Code does not know about those edits, and you will need to reload the file for VS Code to get the formatted file. Note that nothing has changed in this part of the code for a while.
I believe the issue was caused by this change: https://github.com/microsoft/vscode-python/commit/23725abd4249811f24475e215c2d78ed5e508e79 . I have already reverted this (https://github.com/microsoft/vscode-python/pull/14108) in main (last week), and this should be out in the bug fix release (probably this week).

Thank you

Does this bug effect Pylint as well?

pylint it depends. If you are using Microsoft language server or Pylance, you will not see pylint results (see https://github.com/microsoft/vscode-python/issues/7314).
The formatting issue should be addressed in the latest version 2020.9.112786.

How do I know if I'm using the language server? When I enable Pylint, I get little to nothing shown in terms of errors and whatnot.


My organization within the company is responsible for maintaining a large Go monorepo (~20k packages). In this monorepo, all packages fall under 1 Go module.

For the most part, we run a fairly off-the-shelf gopls setup without any customization of note. This is what our stats look like (from `bea7373d8a8268c2e3a260c1b8d41f96c4f7489e`):

$ gopls stats -anon
Initializing workspace...     done (3m26.109285333s)
Gathering bug reports...      done (1.781858458s)
Querying memstats...          done (1.284304292s)
Querying workspace stats...   done (701.076375ms)
Collecting directory info...  done (7.958301292s)
{
"DirStats": {
"Files": 288174,
"TestdataFiles": 8243,
"GoFiles": 77688,
"ModFiles": 20,
"Dirs": 64532
},
"GOARCH": "arm64",
"GOOS": "darwin",
"GOPACKAGESDRIVER": "",
"GOPLSCACHE": "",
"GoVersion": "go1.23.1",
"GoplsVersion": "(devel)",
"InitialWorkspaceLoadDuration": "3m26.109285333s",
"MemStats": {
"HeapAlloc":<PHONE_NUMBER>,
"HeapInUse":<PHONE_NUMBER>,
"TotalAlloc":<PHONE_NUMBER>4
},
"WorkspaceStats": {
"Files": {
"Total": 72996,
"Largest": 9189430,
"Errs": 0
},
"Views": [
{
"GoCommandVersion": "go1.22.0",
"AllPackages": {
"Packages": 23170,
"LargestPackage": 624,
"CompiledGoFiles": 89502,
"Modules": 1031
},
"WorkspacePackages": {
"Packages": 18127,
"LargestPackage": 354,
"CompiledGoFiles": 61173,
"Modules": 1
},
"Diagnostics": 95
}
]
}
}

### What did you see happen?

The experience of using gopls is good (i.e. rpcs like jump-to-definition, refactor symbol, etc. are fast) once initial workspace load has occurred, but initial workspace loads are a poor experience for our users. This poor experience is owed to two behaviors:

Firstly, initial workspace loads (IWLs) are slow. This is partially owed to the performance of the expensive upfront `go list` call itself:

$ time go list -e -json=Name,ImportPath,Error,Dir,GoFiles,IgnoredGoFiles,IgnoredOtherFiles,CFiles,CgoFiles,CXXFiles,MFiles,HFiles,FFiles,SFiles,SwigFiles,SwigCXXFiles,SysoFiles,TestGoFiles,XTestGoFiles,CompiledGoFiles,Export,DepOnly,Imports,ImportMap,TestImports,XTestImports,ForTest,DepsErrors,Module,EmbedFiles -compiled=true -test=true -export=false -deps=true -find=false -pgo=off -- /Users/rma/stripe/gocode/... builtin
[ ...A bunch of redacted go list output... ]
go list -e  -compiled=true -test=true -export=false -deps=true -find=false  -  31.41s user 48.00s system 120% cpu 1:06.01 total

…but the majority of the time is spent on calling `packages.Load` on all of the packages that `go list` returns.

Secondly, because [IWLs are blocking](https://github.com/golang/tools/blob/bea7373d8a8268c2e3a260c1b8d41f96c4f7489e/gopls/internal/cache/snapshot.go#L1331-L1333) and VSCode waits on code actions before the IDE is able to save files, users are unable to save files/exit their IDEs/etc:

> ```Saving 'main.go': Getting code actions from ''Go', 'ESLint', 'GitHub Copilot Chat'' (configure).```

…while IWL is incomplete. This is partially a corollary of the first issue. While it is true that making code actions non-blocking for saves would fix this UX issue, if IWL were fast, this UX issue would not be perceived by users in the first place.

We have dipped our toes in trying to patch this behavior. For example, an early attempt at hacking around this behavior (on a `v1.16.1` base) [no-ops the initialization routine altogether](https://gist.github.com/rma-stripe/c9c5573025209389678af3a9755137e6), relying solely on gopls loading in package data as files are manually opened by the user. As expected, this hack has some large tradeoffs associated with it, because initialization is a load bearing part of gopls: it breaks features like "Rename symbol" and "Find all references", and it occasionally causes the wrong imports to be pulled in. However, buggy as it is, this hack in essence describes what we think the desirable IWL behavior would be:

* The initial snapshot at gopls startup does not await IWL
* On startup, an async IWL routine runs `go list` and lazy loads package data into the currently "active" snapshot
* While this async routine has not completed, language server RPCs which rely on all workspace packages being loaded (such as "Find all references" are not available)

### What did you expect to see?

This issue is a feature request.

* Does the newly proposed workspace initialization approach align with the gopls roadmap?
* Is there a better approach (in the interim) to addressing the slow/blocking behavior of IWLs than the no-op/hack solution linked above?

We would appreciate any tips/guidance in writing an upstream-able patch, or a better hack.

### Editor and settings

_No response_

### Logs

_No response_

Related Issues and Documentation

x/tools/gopls: high memory consumption when used with a monorepo #37670 (closed)
x/tools/gopls: add ability to avoid scanning an entire workspace #53278 (closed)
x/tools/gopls: init project cost long time when open the go project #62715 (closed)
x/tools/gopls: too many memory usage #37759 (closed)
x/tools/gopls: crash importing test variant of tools file #66109 (closed)
x/tools/gopls: feedback is extremely slow with large monorepo #44188 (closed)
cmd/go: `go list` commands called by `golang.org/x/tools/go/packages.Load()` varies from ~500ms to 3s with no other changes #63863 (closed)
x/tools/gopls: massive cpu and memory usage #46897 (closed)
x/tools/gopls: gopls walks entire filesystem of a go module #52993 (closed)
x/tools/imports: should not scan bazel-out directories #35914

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Thanks for filing this thoughtful issue.
I've wanted the ability to bypass the initial workspace load for a while. This is in line with the work in https://go.dev/issue/68002, which I'm working my way up to now.
I expect this to be doable, though there will almost certainly be many edge cases to take care of (for example: producing reasonable errors for workspace-wide misconfiguration).

So, I "got this working" today, in the sense that I removed the guardrails preventing gopls from working prior to the initial workspace load. In principle, I think the guardrails are misguided anyway: we don't enforce the same restrictions when reloading a workspace (for example, after making a go.mod change), so there's really no reason we can't allow gopls to function prior to the initial workspace load.
However, the change actually poses a significant challenge for testing, since we seek the completion of the initial workspace load in many places as a signal that gopls is ready to be used. Now there is no such signal.
@rma-stripe I'm curious if patching the following CL and installing gopls works well for you. That would at least be a signal that we're on the right track.
https://go.dev/cl/626536

…but the majority of the time is spent on calling packages.Load on all of the packages that go list returns.

That's surprising to me. Can you say more? I'd expect the post-processing of packages should be a minor cost. Certainly gopls type checking those packages can take a while, but that is not considered to be part of the initial workspace load.

I'm curious if patching the following CL and installing gopls works well for you. That would at least be a signal that we're on the right track.

In general the patch works well. I was able to visually time when the initial workspace load completes by looking for the (*Snapshot).load event with the same query + number of packages as event #1: https://gist.github.com/rma-stripe/d14b1336fcea83672ef15b41d3cdab05
Prior to the initial workspace load's completion, features like jump-to-definition and definition-on-highlight work. Some other features, like "Find all references" are blocked on the initial workspace load completion, which makes sense, as we can't find all references to a symbol without introspecting the whole workspace.
An issue I was only able to repro once: By repeatedly opening not-yet-loaded packages by hand (maybe one every 5 seconds) prior to the initial workspace load's completion, I was able to get gopls in a stalled/jammed state where it would not create (*Snapshot).load events for individual files (whether on file open or on file save-after-change) until the initial workspace load succeeded.
Were this patch upstreamed, we would consider it a significant improvement over the current behavior of gopls in our custom-patched version.

That's surprising to me. Can you say more? I'd expect the post-processing of packages should be a minor cost. Certainly gopls type checking those packages can take a while, but that is not considered to be part of the initial workspace load.

I don't fully remember what this was about, sorry. We did some work prior to filing this issue trying to figure out what parts of IWL are slow, but the details of those experiments have since been deleted by our Slack retention policy.

An issue I was only able to repro once: By repeatedly opening not-yet-loaded packages by hand (maybe one every 5 seconds) prior to the initial workspace load's completion, I was able to get gopls in a stalled/jammed state where it would not create (*Snapshot).load events for individual files (whether on file open or on file save-after-change) until the initial workspace load succeeded.

What could have happened there is this: if you ran a find-references request, it would have blocked other requests, and would itself have awaited initialization. Does that sound plausible? If we were to land this CL, we'd also want to allow navigation to be handled asynchronously to workspace-wide requests. The good news is that we recently added a mechanism for such concurrency.
If we're going to land this, we need to do approximately the following:

Allow Snapshots to share the view initialization query. Otherwise, each keystroke cancels the previous initializatoin and starts afresh. Instead, we can record overlays that have changed since the last query, and invalidate its results when it completes.
Have a more general mechanism for raising a progress dialog for the initialization query. For analysis, we raise a popup only if analysis takes longer than 5 seconds. We can do the same for loads.
Have a better detection mechanism for the completion of the initial workspace load, for the purposes of testing.

This is a non-trivial amount of work -- at least several days work to do it properly. However, I do think it's worth doing as it can really improve the experience of using gopls on large codebases.

Investigating code paths that await initialization, there are a number of perhaps surprising conditions to sort out. Notably, if you open a file outside a workspace folder, and ask for file-oriented information about that file, gopls currently awaits initialization of each workspace folder, because it has to see which build that file most logically "belongs" to. I suspect this is what occurred to get @rma-stripe's session into a blocked state.
This mechanism is particularly gnarly, because we really don't want to allow other messages to proceed until we've resolved the correct build for that file request, because we need to acquire the Snapshot (a logical point in time) before we allow other state-affecting notifications to be processed.

What could have happened there is this: if you ran a find-references request, it would have blocked other requests, and would itself have awaited initialization. Does that sound plausible?

I think it was likely some other edge case. If this were true, you could repro by:

Starting a fresh VSCode
Prior to IWL completion, run a find-references request
Still prior to IWL completion, open another (unindexed) package and hover over a symbol, and observe that the symbol definition doesn't appear

However, the very last part of Step 3 ("observe that the symbol definition doesn't appear") doesn't hold true, because opening a new file in VSCode causes the find-references context to cancel:
[Error - 1:56:57 PM] Request textDocument/references failed.
  Message: context canceled
  Code: 0

So long as the context cancelation for the workspace-wide req reliably occurs, the IDE shouldn't get into such a jammed state. Maybe that allows for landing the changeset without blocking it on "allow[ing] navigation to be handled asynchronously to workspace-wide requests", maybe not?

(this is not going to make v0.17. as the fix is too risky, but I plan to work on it soon after the release)

Experienced the same issue since ~v0.15, related to expandWorkspaceToModule behavior changes, I guess.
This happens in very large monorepo that contains 300k individual packages under single go.mod and 13k modules from vendor folder. Standard gopls gets stuck initially loading workspace. go list -e -json -deps=true ... with the root go.mod seems to be the bottleneck. This command can't complete even outside gopls.
At the same time, indexing vendor folder takes reasonably short time and initial startup scales linearly.
I've seen mention of overlay feature in other issues. I couldn't find any improvements with exactly this approach as it's hard to blacklist entire folder from the build without mentioning all the individual files. But I achieved inf -> 12s initial load improvement with the same concept with using alternative build graph discovery and VFS directory filters (FUSE). I would run package discovery on directories that I work on and blacklist rest of the monorepo. I guess it would be easily reproducible if overlay files supported gopls directoryFilters like syntax: blacklist all by default and add some actually necessary folders, maybe take additinal care of std and 3d party.
That said, it requires keeping track of used packages which can be hard without some external discovery tools.
The second approach that allowed to work in this monorepo included patching gopls itself.
https://github.com/golang/tools/blob/ebeac1b80e43c36980be76d3a691a5cc3722d245/gopls/internal/cache/load.go#L96 By disabling recursive go list, gopls could initially startup and load packages on demand relying on current package scope. This, in turn, broke features like references and implementations for packages that were not yet opened by an editor.
Possible improvement would be to implement a custom setting that tells to go list given folders in order to properly index at least some packages and partially fix references. But it requires additional attention to caching so that gopls wouldn't run go list again and again.
All of this was mentioned before in some form and this is just PoC implementation. But I hope this would be beneficial to think of a solution that feels sensible for everyone.


[NETBEANS-54] Module Review profiler.j2se

According to https://cwiki.apache.org/confluence/display/NETBEANS/List+of+Modules+to+Review
build.xml is part of the 'Problems to be solved centrally'. So there's nothing to be done here.
Sorry for the extra work.


Remove TailwindCSS & PostCSS configuration files

Description
Tailwindcss was removed in favor of NextUI, commit.
However, the imports are still present in styles/globals.css.
Other redudant files like tailwind.config.js and postcss.config.js are also present. Which in turn cause the CI/CD to fail.
This PR removes those redudant files and deps.
Fixes #126
Changes Include

[x] Bug fix 🐛

How Has This Been Tested?
Tested on local system & CI/CD
Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

PR looks good thanks for sharing & I'll merge it after you made the other subtle change.
Side note; The other PR you share earlier is HUGE & I'll review it over a weekend. I'll also need to setup the Netlify secret tokens which I don't have access to. So, I hope you understand & will be patient with me on that regards.

PR looks good thanks for sharing & I'll merge it after you made the other subtle change.
Side note; The other PR you share earlier is HUGE & I'll review it over a weekend. I'll also need to setup the Netlify secret tokens which I don't have access to. So, I hope you understand & will be patient with me on that regards.

Yes ofcourse man.


Microsoft Visual C++ (latest version)

A couple of problems when compiling in MSVC (latest version)
Compiler errors:
Severity	Code	Description	Project	File	Line	Suppression State
Error	C3177	you cannot have a conversion function to a type that contains 'auto'	ctbignum\field.hpp	29
Severity	Code	Description	Project	File	Line	Suppression State
Error	C3547	template parameter 'Is' cannot be used because it follows a template parameter pack and cannot be deduced from the function parameters of 'cbn::ext_gcd'	dsapp	ctbignum\gcd.hpp	69
Incompatible features
#define CBN_ALWAYS_INLINE [[gnu::always_inline]] in config.hpp
template <> struct dbl_bitlen<uint64_t> { using type = __uint128_t; };
template <> struct dbl_bitlen { using type = __uint128_t; };
in type_traits.hpp

Hi Keith / @bitlush ,
Thank you for your interest in the project! I've never tried compiling with MS's Visual Studio, nor do I have windows/Visual Studio... Would you be interested in contributing, e.g., by sending a pull request?

__uint128_t is indeed a clang/gcc-only thing. Do you know whether MS has something like that?
Probably, some macros (or constexpr-if) can help here to switch this case off for the MS compiler.
BTW, even if MS does not provide a 128-bit type, then as a workaround you can use the big-ints with 32-bit limbs, since most of the code is templated on the limb type,
or I can define a dedicated 64x64bit mul function. (I already did that once, but removed it some time ago)

Regarding the always inline, this should probably be "__forceinline" for Visual Studio,
a macro should then choose between the GNU and Microsoft pragma based on the detected compiler.

Regarding:

explicit operator auto() const { return data; }

I am not sure if I actually use that somewhere.
Does the following (explicitly spelling the type to the compiler) compile?
explicit operator big_int<sizeof...(Modulus), T>() const { return data; }

The error with:

constexpr auto ext_gcd(std::integer_sequence<T, A...>,
                       std::integer_sequence<T, B...>)

must have been caused by the Is template parameter pack, which did not serve any purpose (it    probably originated from some copy pasting from ext_gcd_impl), but neither clang nor gcc complained about it. I have already removed that.

I'll fork and create a pull request as I've managed to get the bits I've tried it compiling. I've also had to sprinkle a few static_casts around the code to remove compiler warnings. I also use Clang and AppleClang as well so I can easily do a regression on those.
Great work by the way, this is a wonderful library.

Great! I'd be very interested to see where exactly those static_casts are needed.
BTW The old multiplication code (circumventing __uint128_t ) can be found commit: fba16e2ef5b908a33cd198fb

@bitlush,
I discovered that in type_traits.hpp, the specialization of dbl_bitlen for unsigned long interfered with that of uint64_t,  so I commented-out the former, see commit  1223979

@niekbouman, OK thanks for the heads up. It'll be a day or two before I can check my changes through as the tests are problematic under MSVC.
I'm going to propose using the following to fix the missing 128-bit integers in type_traits.hpp:
#if defined(_MSC_VER)
using default_limb_t = uint32_t;
#else
using default_limb_t = uint64_t;
#endif

And then I can update all templates like so:
template <size_t N, typename T = default_limb_t,
          typename = std::enable_if_t<std::is_integral<T>::value>>
struct big_int : std::array<T, N> {};

If you've got a view on this approach, please let me know, I'm not overly convinced it's a great way to go.
I'm undecided if a better approach is to actually use a zero abstraction wrapper for limb data types i.e. limb8_t, limb32_t, limb64_t which would overload the maths operations, provide a better route to fix all the overflow warnings in MSVC by keeping the code free of static_cast fixes, allow limb64_t to use platform specific code for multiplications etc when 128 integers don't exist, but it's a lot of work and adds more code and complexity.

Hi Keith @bitlush ,
Any luck so far getting the code to run on MSVC?
best,
Niek


FIX: Added a bottom margin to tracks tag for design consistency

Added margin of 5 to the bottom of tracks tag, to have some space between the track carousel and the tag. It aligns with the rest of the design where effects tag also have a margin of 5 between it, and effects carousel

Good spot, thanks for the PR! However, this makes the page scrollable, which I prefer not to happen. Maybe we can reduce the margin at both places?

Good point! It will be a good idea to just do that instead

What I meant was that the current page layout fits the screen size perfectly, making it non-scrollable. However, increasing the margin pushes other elements down, causing the page to become scrollable. This adjustment feels somewhat unstable. Perhaps if we reduce the margin at both places, it should work.

@ArvindParekh I still have an unclear picture of idea you're trying to convey. I still get "the page is not scrollable(which it is), it will make it scrollable" vibe. What monitor resolution do you have?


odo catalog list services show empty list when namespace just created

/kind bug
When the command odo catalog list services is executed after the current namespace is created, it can take a few time to get the list of services, the time the clusterserviceversions are in pahe Succeeded in this namespace.
What versions of software are you using?
Operating System:
Linux
Output of odo version:
odo v2.3.0 (6ed4ee4b6)
Server: https://api.crc.testing:6443
Kubernetes: v1.21.1+051ac4f
How did you run odo exactly?
odo project create myproject
odo catalog list services
Actual behavior
no deployable operators found
Expected behavior
It could be helpful to get a list of services, even incomplete, when the clusterserviceversions are not in Succeeded phase.
This could also help running the tests more quickly.
Any logs, error output, etc?

We moved to checking for "Succeeded" phase of an Operator in #4202 after receiving a problem from the user.

We moved to checking for "Succeeded" phase of an Operator in #4202 after receiving a problem from the user.

I understand that the problem was that the operator was not working correclty, and in this case to not display it. Has it been considered to also display those in pending state (empty Phase) also?
if csv.Status.Phase == "Succeeded" || csv.Status.Phase == "" {
			csvList.Items = append(csvList.Items, csv)
		}

@feloy suggested to show the Operators in odo catalog list services output as long as they have "Failed" to install. So what we could do is probably add a check for phase not equal to Failed and show all such Operators. We could add a column in the output indicating whether the Operator is "ready" or "not ready" for use.

Implementing this feature does not seem to have any impact on the time run to test.

/close


please unseal the CommentStyle

I would like to use this, but I cannot
  case object SensibleLineComment extends CommentStyle {
    override val commentCreator = new LineCommentCreator("//")
    override val pattern: Regex =
      "(?s)(// Copyright[^\\n]*[\\n]// Licen[cs]e[^\\n]*[\\n])(.*)".r
  }

can you please unseal in the next release? Unless you are matching over the ADT there is no point in sealing.

I don't think we should be doing this. The following configuration should be enough for the use case you described in #139:
headerLicense := Some(HeaderLicense.Custom(
  """|Copyright: 2017 https://gitlab.com/fommil/stalactite/graphs
     |License: http://www.gnu.org/licenses/lgpl-3.0.en.html
     |""".stripMargin
))
headerMappings := headerMappings.value + (HeaderFileType.scala -> HeaderCommentStyle.CppStyleLineComment)

Of corse we would have to fix #117 in order to create headers without new line between comment and body.

I don't think that's enough... my matchers allow for line comments beneath the lines that I care about. I would typically use this when I want to have custom copyright information there.

I don't understand your use case. Do you have some files which start with // Copyright:  but then have something different from 2017 https://gitlab.com/fommil/stalactite/graphs?

yes, exactly. Typically when I've copied some code from elsewhere and am required to include their headers by their terms.

Looking at CommentStyle again, I don't understand why I decided to configure it using inheritance. It would be enough to have:
sealed trait CommentStyle {
  def pattern: Regex
  def commentCreator: CommentCreator
  // apply methods
}

case class SimpleCommentStyle(
  val pattern: Regex
  val commentCreator: CommentCreator
)

val CStyleBlockComment = SimpleCommentStyle(
  pattern = commentBetween("""/\*+""", "*", """\*/""")
  commentCreator = new CommentBlockCreator("/*", " *", " */")
)

// other implementations

This way you could simply instantiate a SimpleCommentStyle with the configuration you need. Would that work for you?

sounds good!

thank you @britter !

Is it possible to also unseal CommentCreator ? Otherwise it's still impossible to define a custom style.
(As a workaround, one can probably use IdentityCommentCreator and include the comments in the license text)

OMG! This is a can of worms ;-)
@britter, what do you think?


v4 table updates

Few table updates:

Fixes the inverse table's border color. Adds a new variable that lightens the inverse table's background color a bit instead of using $body-bg.
Fixes the responsive table behavior. Instead of using a parent class again, this scopes (as the comment above it indicates) the styles to under 768px.

Fixes part of #21585
Fixes #21577 (/cc @pmsaue0 as credit for the fix)
Closes #21677, closes #21678, and closes #21676 as they're no longer needed.

Gave up on CI lol.


Adding support for fields/edges dialect-specific DDLs

Would you like to add support for ddl's to add default values for the time fields?

Pasting here my comment from #558:

I've landed 3e7481c3a015400fd5f407aba1c57f35731601dc that ignores the MySQL default values for time fields, and it should not apply any changes for the second time the migration runs.
However, it won't work with the current way you declare the schema, because you add additional parameters to the schema datatype (the create/update default values).
I suggest to close this issue and open a new one for adding support for fields/edges dialect-specific DDLs. For example:
// Add abstraction for common DDLs.
field.Time("create_time").
    DDL(
        field.Default("CURRENT_TIMESTAMP"),
        field.OnUpdate("CURRENT_TIMESTAMP")
    )

// Add additional information for the given column. The EXTRA in the
// INFORMATION_SCHEMA table. For example, the "ON UPDATE" clause.
field.Time("update_time").
    SchemaDef(map[string]string{
        MySQL: "DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP",
    })

// Completely override the ent-migration column definition.
field.Time("create_time").
    SchemaDef(map[string]string{
        MySQL: "TIMESTAMP DEFAULT CURRENT_TIMESTAMP NOT NULL",
    })

Feedback or thoughts are welcome.

That syntax would be nice :)

Closing, as this was implemented by entsql.Annotation. Thanks 🙏


Upgrade tested AGP version to 3.5.1

cc: @gradle/build-cache

Latest AGP seems to have a memory leak, which makes the performance test fail. We will fix the test on master, we are using a later version on release now.


bring back #7002

bring back #7002 which was reverted in #7031 and include the fix from #7034

@swift-ci test


Vue style guide generator

Idea: have a catalog of all the components in a project:
like https://github.com/sapegin/react-styleguidist but for vue :)

I've just started working on such a component - https://github.com/shershen08/vue-styleguide-generator. Hope can get someway near to what React version does ;)

Hello @nicolas-t
I have developed what you need,
https://github.com/vue-styleguidist/vue-styleguidist


Wrong mobileMode detecting if gridster is hidden on initialization

Version 13.2.
If gridster container have display: none on initialization, gridster initializing in mobile mode and staying in it when container becomes visible. Mobile mode stays turned on until first resize.
First time mobileMode detecting returns 'true' because $elem[0].offsetWidth is zero for hidden block children, like demonstrated here: http://jsfiddle.net/4weysLa1/
It not reproducing in 0.11.7, because there are a watch for $elem[0].offsetWidth || parseInt($elem.css('width'), 10);, which toggles mobileMode when gridster becomes visible, but now this watch working only in some conditions.

I'm using a workaround - triggering resize events manually when element.offsetWidth changes, but gridster onResize handler have 100ms debounce, so sometimes mobile mode is visible for small time when grid opening

the latest commit adds some explicit checking for the gridster element being hidden.  my tests with ng-show and ng-hide work well.

@danomatic Thanks!


Add current deployment config for the TrustyAI service

@anishasthana: This is turrent OSD deployment for the trustyai-service, just for comparison.

@anishasthana can I ask you to have a look at we need to change, in order to merge this? Thank you!

@anishasthana Removed ImageStream, move env vars to ConfigMap and moved image location to the trustyai quay.io org.
(Just as a note, at the time of writing, the image is still not pushed to quay, but we plan to do it today).

Sounds good! Let me know once the image is pushed up. I can run through a test deployment to confirm. Related -- where is the dockerfile being used to build this image?

@ruivieira the manifests/opendatahub/base/kustomization.yaml  file needs to be:
`apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
commonLabels:
app: trustyai
app.kubernetes.io/part-of: trustyai
resources:

../default
trustyai-configmap.yaml`

Thanks @RobGeada, added.


[firebase_messaging] Different notification format for Android and iOS

firebase_messaging: 4.0.0+1
There is a different notification format for iOS and Android - parameter for onMessage callback.
iOS:
{google.c.a.c_l: 20190226 - en, google.c.a.c_id:<PHONE_NUMBER>588377404, gcm.n.e: 1, google.c.a.e: 1, count: 2, gcm.message_id: 0:1552019268226658%929750ef929750ef, path: lists_custom/2019-02-26/list, action: list, google.c.a.udt: 0, google.c.a.ts:<PHONE_NUMBER>, aps: {alert: 2 new flowers were added to the herbary}, click_action: FLUTTER_NOTIFICATION_CLICK}
Android:
{notification: {title: null, body: 2 new flowers were added to the herbary}, data: {action: list, path: lists_custom/2019-02-26/list, count: 2, click_action: FLUTTER_NOTIFICATION_CLICK}}

@benadrasni
The issue at https://github.com/flutter/flutter/issues/29027 has been closed and moved here. Future collaboration on this issue will be done here.

I'm having a similar issue but what weird is notification I got in iOS simulator and iOS devices is different.
iOS simulator:
{FROM_NOTIFICATION: true, from: /topics/5ddcbeaf15deea0007923d88, _id: 5de0a474067c110007d860fd, notification: {body: testing, title: Testing title for patch, e: 1, click_action: ISSUE_MESSAGE}, sentBy: 5d6e229fe7d43e0008157087, imageCheck: false, collapse_key: com.connyonair.onair, type: ISSUE_MESSAGE, ISSUE_ID: 5ddcbeaf15deea0007923d88, issueId: 5ddcbeaf15deea0007923d88, createdAt: 2019-11-29T04:54:12.457Z}
iOS device:
{issueId: 5ddcbeaf15deea0007923d88, gcm.message_id:<PHONE_NUMBER>415106, google.c.a.e: 1, type: ISSUE_MESSAGE, aps: {alert: {title: Testing title for patch, body: Zi Jing Lim: testing}, sound: default, content-available: 1.0}, _id: 5de0a474067c110007d860fd, sentBy: 5d6e229fe7d43e0008157087, FROM_NOTIFICATION: true, createdAt: 2019-11-29T04:54:12.457Z, imageCheck: false, ISSUE_ID: 5ddcbeaf15deea0007923d88}
I've tried this two code but I received null when I try to get the body using data["body"].
Code 1:
var data = message["data"];
if (Platform.isIOS) {
data = message;
}
Code 2:
var data = message["data"] ?? message;
Flutter Doctor:
[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Mac OS X 10.15.1 19B88, locale en-MY)
• Flutter version 1.9.1+hotfix.6 at /Users/jing/Development/flutter
• Framework revision 68587a0916 (3 months ago), 2019-09-13 19:46:58 -0700
• Engine revision b863200c37
• Dart version 2.5.0
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /Users/jing/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.2
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.2.1, Build version 11B500
• CocoaPods version 1.8.4
[✓] Android Studio (version 3.5)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 40.2.2
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
[✓] VS Code (version 1.40.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.6.0
[✓] Connected device (4 available)
• A0001             • f9ff5e1a                                 • android-arm • Android 5.1.1 (API 22)
• JinG iPhone       • b9405437c35d652421a58b319f816fdcb6e4a933 • ios         • iOS 13.2.3
• iPhone 11 Pro     • BDA95402-8188-4226-AA50-61A3E8C57D54     • ios         • com.apple.CoreSimulator.SimRuntime.iOS-13-2 (simulator)
• iPhone 11 Pro Max • 2CF9B59A-20BA-4A43-B2E8-545C243DECE2     • ios         • com.apple.CoreSimulator.SimRuntime.iOS-13-2 (simulator)
• No issues found!

Hey @benadrasni and @JinG312 I'm reviewing old issues. Is this still an issue with the most recent version?

Hey,
I still have this code in my sources, so yes.
onResume: (Map<String, dynamic> message) async {
setState(() {
_notificationData = Map.from(
Platform.isIOS ? message : message[notificationAttributeData]);
});
},
On Mon, Apr 20, 2020 at 9:50 AM Kirsty Williams<EMAIL_ADDRESS>wrote:

Hey @benadrasni https://github.com/benadrasni and @JinG312
https://github.com/JinG312 I'm reviewing old issues. Is this still an
issue with the most recent version?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FirebaseExtended/flutterfire/issues/1065#issuecomment-616603805,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXZ4ENEXBDLJA3QAK7J7ATRNROLPANCNFSM4JAIKPIQ
.

@benadrasni thanks!

I have this issue as well. It's weird having different payloads for android and ios

Hey all 👋
As part of our roadmap (#2582) we've just shipped a complete rework of the firebase_messaging plugin that aims to solve this and many other issues. Both Android & iOS should now be consistent, we also now have a typed api RemoteMessage for messages rather than the raw map that was returned previously.
If you can, please try out the dev release (see the migration guide for upgrading and for changes) and if you have any feedback then join in the discussion here.
Given the scope of the rework I'm going to go ahead and close this issue in favor of trying out the latest plugin.
Thanks everyone.


Cleanup code and readme

This works, but be warned that the mass of changes may cause conflicts in your feature-* branches.
This marks the official 0.8.1 release.

@homu r+

:pushpin: Commit 57422d3 has been approved by smo-key

:hourglass: Testing commit 57422d3 with merge f95373b...

:sunny: Test successful - status


PreserveReference and "An item with the same key has already been added." ArgumentException

I'm having an issue with PreserveReference, I worked around it and I pretty much stopped using it, but I'd like to know if I'm missing something (which is likely).

so, when I have circular references PreserveReference didn't resolve that for me

and when I have (what seems as, it's hard to trace it, I didn't debug it with Mapster source, will do if needed) 2 properties pointing to the same object reference - then I get the above error (which is a typical dictionary/hash issue somewhere inside the Mapster code).

so it's simple hierarchy that I'm trying to map (basically entities to view-models, pretty typical), no circular references (I made sure of that, the code is quite mature)

what it's supposed to actually handle (2 properties pointing to the same object) is when it fails (that error)

as soon as I remove the PreserveReference all is working (just not preserved references of course)

I'll try and dive deeper into this, provide a sample solution etc.,
but I just wanted to see if this is a known issue, or even if you ever encountered it, or it's something specific to my data/code.

Hi,
I tried to reproduce, but it works fine. Could you pls provide reproducible code?
public class ParentPoco
{
    public ChildPoco Child1 { get; set; }
    public ChildPoco Child2 { get; set; }
}
public class ChildPoco
{
    public Guid Id { get; set; }
}
public class ParentDto
{
    public ChildDto Child1 { get; set; }
    public ChildDto Child2 { get; set; }
}
public class ChildDto
{
    public Guid Id { get; set; }
}
class Program
{
    static void Main(string[] args)
    {
        TypeAdapterConfig.GlobalSettings.Default.PreserveReference(true);
        var child = new ChildPoco {Id = Guid.NewGuid()};
        var poco = new ParentPoco {Child1 = child, Child2 = child};
        var result = poco.Adapt<ParentDto>();
        Console.WriteLine(result.Child1 == result.Child2); //true
    }
}

thanks on your response,
I thought it wasn't simple issue,
I certainly will sit down and make a small project - it's part of a larger scenario, but I'll figure something out.
This is how I'm using it, as a start only (that's the offending code)
config.NewConfig<ISomeEntity, SomeViewModel>()
    .ConstructUsing(entity => container.Resolve<SomeViewModel.Factory>()(entity))
    .IgnoreAttribute(typeof(DoNotMapAttribute))
    .IgnoreNullValues(true)
    .PreserveReference(true);

...but I should know better, I'll provide an example.
I basically just wanted to get a first response to see if it's worth investing time into it.

I have no clue why PreserveReference doesn't work in your case. Mapster checks item not exists before adding new item to dictionary. My guess is there might be some other issues that cause the problem.

And just to update, I didn't have enough time but I figured out where the problem is, roughly, I have hierarchical data structure and I was applying TypeAdapter.Adapt redundantly at every level, i.e. not just on the root but also on each child (building, again, it's own hierarchy). If I de-duplicate that and just have one mapping on the root (that takes care of the entire hierarchy) the issue goes away. Exception is somewhere within the expressions created, but it's hard to debug those.
That isn't wrong though per se, but I'm guessing it should work.
I'm going to write a small unit test with some sample data that mimics the above case - and will post that - but need a bit more time to find some space to do it. So I didn't forget about it!

Hi, even I don't know root cause of this problem. I changed from Dictionary.Add to Dictionary[key] when adding new references to solve this issue. If you can provide test case, I'm happy to inspect the problem. I will close this issue for now.


Add futurecoder

What does this PR do?
Add resource
For resources
Description
futurecoder: 100% free and interactive Python course for beginners
Why is this valuable (or not)?
Website explains in detail: https://futurecoder.io/
How do we know it's really free?
Start instantly on https://futurecoder.io/course/
No account required, no ads, open source (https://github.com/alexmojaki/futurecoder), can jump to any part of the course instantly in table of contents: https://futurecoder.io/course/#toc
For book lists, is it a book? For course lists, is it a course? etc.
It's a highly interactive tutorial. Running correct code is required to advance.
Checklist:

[x] Read our contributing guidelines
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction)

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

I prefer lowercase futurecoder but it seems a lot of people don't...

I prefer lowercase futurecoder but it seems a lot of people don't...

I agree since is the original title that we can see in the webpage.
Thanks for your development. It seems pretty.

Wow!!
Thanks, and welcome to free-programming-books and thanks for making this free!

Yes, it's usually a good idea to follow the capitalization of the source, as long as it isn't SCREAMING.

Yes, it's usually a good idea to follow the capitalization of the source

But that's not what's been merged


spec: clarify relationship between CRM and "apps"

(This is partly leading on from the discussion in https://github.com/coreos/rocket/issues/294)
A Container Runtime Manifest declares one or more apps to be executed. At the time of writing the format of declaration looks like this:

apps the list of apps that will execute inside of this container
* app the name of the app (string, restricted to AC Name formatting)
* imageID the content hash of the image that this app will execute inside of (string, must be of the format "type-value", where "type" is "sha512" and value is the hex encoded string of the hash)
* isolators the list of isolators that should be applied to this app (key is restricted to the AC Name formatting and the value can be a freeform string)
* annotations arbitrary metadata appended to the app (key is restricted to the AC Name formatting and the value can be a freeform string)

There are several issues with this schema:

Each "app" technically refers to an app image (ACI), which may or may not actually contain an app declaration (since "app" is an optional section of the Image Manifest). The spec is unclear as to what will occur if the referenced image does not contain an app declaration. (Relatedly, "app" should likely more accurately be called "name")
"app" references are not unique. There is a fairly simple use case of wanting to use a particular app-image multiple times within a container, but it is unclear how this behaviour should be represented in the spec, or at least how implementations should go about handling it (currently in Rocket we actually mandate that apps within a CRM must be unique)
For each app, there is only a partial ability to override some of the parameters defined in the Image Manifest. For example, currently isolators (from the app section of the Image Manifest) and annotations can be overridden/extended; but there is no such ability to override the exec or eventHandlers

This is closely related to, but not the same as, https://github.com/appc/spec/issues/83
One possible solution is to extend the schema of app references in the CRM to match that of the Image Manifest. In this way, all of the parameters in the Image Manifest could be explicitly overridden at a later stage. However, this does potentially mean a lot of duplication between the information contained in the IM and the CRM.

The first issue was clarified in #72.

@wereHamster I don't think we properly understood your question there; I think we should define (or at least describe) the expected behaviour in the spec.

I didn't have a question. Just mentioning that the behavior under the condition outlined in the first point was explained in the first comment on #72. That is: the executer should fail.

@wereHamster right, I think we're on the same page now, that's what this ticket should clear up ;-)

I am starting to think that what we should tweak the meaning of the "name" (née "app") field: rather than being necessarily equivalent to the name of the image (let's call that the ACI name) it would be a distinct value referring to the app inside the running container (let's call that the CRM app name).
We could then mandate in the spec that this field/value be unique within a given container/CRM.
Then implementations could provide simplifications of this abstraction: for example a basic workflow that generates CRMs would just use the ACI name as the CRM app name (i.e as Rocket does today)

Solves the duplication problem (multiple ACIs with the same name in their manifest)
Gives a consistent way to uniquely refer to an app within a container (container UUID + CRM app name)
Makes it clear that the only field in the "app" schema that actually references the app (as opposed to extending/overriding it) is the imageID
Easy to implement "backwards compatible" simplifications where the ACI name and CRM app name are the same

Potentially confusing since sometimes the ACI name and CRM app name would differ and sometimes they might be the same
Incompatible with the issue/proposal described in #106, which essentially goes in the opposite direction (of adding labels to the "app" schema, i.e. extending rather than narrowing the reference information)

@cdaylward thoughts?

https://github.com/appc/spec/commit/9aafd97bcebd31d7f82b7f04fb1d2ce4661ec3b8 partially addressed this issue by introducing a new level of naming abstraction (essentially the CRM app name I described above). However it does not yet address the issue of uniqueness.


Batch edit when creating a new series is broken

I'm seeing this on both Firefox and Chrome.
Steps to reproduce:

Create a new series
Select Michaelmas
Check W1, W2 and W3

You end up with:

When clicking the trash icon next to the drop downs the weeks get deselected again.
There's an additional issue that the dates don't change in the event list when changing a day or hour

I cannot reproduce this on the latest UI. Various batch edit fixes have gone in towards the end of last week that seemed to have fixed this as well.


bug in resty.template, version issue?

now the version of resty.template in lor () is 1.6-dev,  it should be updated to the latest version 1.9,
because i got a bug in using template blocks.

oh i found it has been upgraded.


Preview 'index' page also shows instance variables

I have a preview component that contains some instance variables:
class TestComponentPreview < ActionView::Component::Preview
  attr_accessor :some_accessor

  def with_default_title
    render(TestComponent, title: "Test component default")
  end
  ...
end

When I navigate to http://localhost:300/rails/components both the 'getter' and 'setter' are listed. I know this is easy to fix by changing ActionView::Component::Preview#examples but currently I'm having trouble finding the time to set up a unit test for this.
# lib/action_view/component/preview.rb
def examples
  public_instance_methods(false)
    .map(&:to_s)
    .reject { |e| (e =~ /=$/) || instance_methods(false).map(&:to_s).include?("#{e}=") }
    .sort
end

@juanmanuelramallo care to have a look here?

Sure thing!

@bazzel Sorry for the late answer.
Do you think a private attr_accessor would also work?
class TestComponentPreview < ActionView::Component::Preview
  def with_default_title
    render(TestComponent, title: "Test component default")
  end

  ...

  private

  attr_accessor :some_accessor
end

I don't see why we would need to use attribute accessors publicly on a ActionView::Component::Preview object, maybe you can elaborate a bit more the example? I might be missing something.

Haven't thought of using a private variable 😳but that removes the need for filtering out the instance variables. Thanks for the reply!


Create a "Visualizers" library and add the existing "robot visualizer" block

In order to use the simulator in other frameworks, typically within the controller models in whole-body-controllers (refer to whole-body-controllers#121, we need to convert the robot visualizer into a library.

We create a main library mwbs_lib.slx to which we link other sub-libraries robotDynamicsWithContacts_lib.slx and visualizers_lib.slx (newly created), which wil be visible in the library broaser as follows:

RobotDynWithContacts
Robot Visualizer

The RobotVisualizer block is the new one we create here from the pre-existing block test_matlab_system_2020b/Robot visualizer/robotVisualizer

For creating a tree of sub-libraries in a library, refer to https://www.mathworks.com/help/simulink/ug/adding-libraries-to-the-library-browser.html.

Implemented by #41 .

CC @traversaro


starting from version 3.5.1  the switch /kbd:layout does not work

hello
with version 3.4.0 we can use the switch /kbd:layout:Italian to force the remote desktop to use italian layout
starting with 3.5.1  the switch does not work anymore, the following message in instead displayed:
/usr/bin/xfreerdp  /kbd:layout:Italian  /v:<IP_ADDRESS>
[14:14:04:565] [36539:00008ebb] [ERROR][com.freerdp.client.common.cmdline] - [parse_kbd_layout]: Could not identify keyboard layout: Italian
[14:14:04:565] [36539:00008ebb] [ERROR][com.freerdp.client.common.cmdline] - [parse_kbd_layout]: Use /list:kbd to list available layouts
[14:14:04:565] [36539:00008ebb] [ERROR][com.freerdp.client.common.cmdline] - [freerdp_client_settings_parse_command_line_arguments_int]: Command line parsing failed at 'kbd' value 'layout:Italian' [-1002]
FreeRDP - A Free Remote Desktop Protocol Implementation
See www.freerdp.com for more information
Usage: /usr/bin/xfreerdp [file] [options] [/v:[:port]]
Syntax:
.....
xfreerdp +version
This is FreeRDP version 3.8.0 (n/a)
if instaed I use 3.4.0 release all works fine:
/usr/bin/xfreerdp  /kbd:layout:Italian  /v:<IP_ADDRESS>
[14:22:07:560] [216904:00034f49] [INFO][com.freerdp.client.x11] - [xf_setup_x11]: Enabling X11 debug mode.
[14:22:07:561] [216904:00034f49] [INFO][com.freerdp.client.x11] - [xf_pre_connect]: No user name set. - Using login name: *****
[14:22:08:69] [216904:00034f49] [WARN][com.freerdp.crypto] - [verify_cb]: Certificate verification failure 'self-signed certificate (18)' at stack position 0
could you help to solve the issue

@gmassimiani can you post your build-config?
this looks like a build error (missing headers/optional libraries)

hello Akallabeth thanks for your support
I forgot to specify my environment, that is fedora 40, so I download the packages directly from fedora repo.
I will tries to test directly from source

@gmassimiani ok, found the issue.
there was a bug in keyboard layout file loading (looks like some code was not committed :/)

ok, thanks for you support


Write out a debug log

Either always write out a debug log, or store all the values that we are looking for in a variable and if something major occurs write it out.

Look into Start-Transcript and Stop-Transcript to see if this what we are looking for. Place inside of a Try Finally block to always do a cleanup if required at the end of the script.
@lusassl-msft will look into this.

Do we want to store the debug log in parallel or should we replace the "default" .txt output file?

We would want to do it in parallel.
The debug will always include the default information. The default will only include the debug if we display it on screen with -Verbose.
Then we delete the debug log if no errors were detected or when we have the Verbose switch set.


Renovate bot configured

🤖 Add Renovate Bot
What's Added

Automatic tracking and updates for the following dependencies:

vue-i18n
radix-vue
unplugin-vue-router
@unocss/core
@unocss/reset
floating-vue
@vee-validate/zod
unocss
vee-validate
@vueuse/core
@vueuse/integrations
@unhead/vue
vite-plugin-vue-devtools
@vue/test-utils

How It Works

🕐 Checks for updates every weekend
🔄 Auto-merges minor and patch updates after 3 days of stability
🔍 Creates PRs for major updates
⚡ Ignores all other dependencies

Security Settings

⏳ Stability period: 3 days
🛑 Rate limit: 4 PRs per hour
👥 Maximum 16 concurrent PRs
🎯 Pin version strategy

What's Next

Renovate will create a Dependency Dashboard in Issues
You can track all updates status there
Manual update checks can be triggered if needed

Testing

[x] Configuration validated
[x] Package rules set up
[x] Limits configured

@torderonex 🔥🚀


Fix

This fixes the .disabled property reflection for range-input. Previously, only the disabled attribute worked.
Fixes #142.

It looks like disabled never reaches the underlying input. Also, I can't figure out why it didn't work before. The property getter/setter reflected the value from the input.

The styling relies on range-input[disabled].

This PR may fix the styling but it breaks the behaviour 😄 .
Feels like the original problem is with if (attributeValue === null) continue; in _reflectAttributes(), and it should remove the attribute instead? However, from memory, I think that broke something, so if you do that be sure to test.

Yeah I'm kinda stumped here - it seems like the (prior to this PR) reflection should have worked since it does:
this._input.disabled = true
this.setAttribute('disabled', this._input.getAttribute('disabled'))

...which should be equivalent to setAttribute('disabled', '')...

this.setAttribute('disabled', this._input.getAttribute('disabled')
...which should be equivalent to setAttribute('disabled', '')...

For the disabled=true case that is correct, but not for disabled=false.
+1 to Jake. I think the error is in line 97:
if (attributeValue === null) continue;
should do an removeAttribute().

Side note: The REFLECTED_X array and the method _reflectAttributes() should really be called _passthroughAttributes() or something. This isn’t really the normal reflection, isn’t it?

We had a rogue for-in loop instead of a for-of loop. And the line Jake and I pointed out.

Ahh wow yeah that'd be from the back and forth we did on the reflection approach. The hasAttribute thing is fine, though it doesn't seem like that was the cause of the .disabled bug.

The difference is the explicit "removeAttribute" call. See previous commit.


NamedHivePartitionSensor supports

With this pull request you can create NamedHivePartitionSensor task on the dag-creation-manager edit page directly.

I think it is more clearly to write commands in this way


DB1 Update

New HDD delivered
Still not accessible the Raid 5 HDD
Troubleshooting stop due to Server room renovation

Awaiting Mark Installer

Recovery tool application need a key to retrieve the data files.


python312Packages.black: 24.3.0 -> 24.4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.black is: The uncompromising Python code formatter
meta.homepage for python312Packages.black is: https://github.com/psf/black
meta.changelog for python312Packages.black is: https://github.com/psf/black/blob/24.4.0/CHANGES.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 24.4.0 with grep in /nix/store/akg7p4sd87fv2kcbazsimnxr9vha8zk1-python3.12-black-24.4.0
found 24.4.0 in filename of file in /nix/store/akg7p4sd87fv2kcbazsimnxr9vha8zk1-python3.12-black-24.4.0

Rebuild report (if merged into master) (click to expand)

60 total rebuild path(s)

60 package rebuild(s)

First fifty rebuilds by attrpath
ansible-lint
ansible-navigator
black
black-macchiato
blacken-docs
cwltool
marimo
nbqa
nitrokey-app2
pynitrokey
python311Packages.aiogithubapi
python311Packages.ansible-navigator
python311Packages.asteroid-filterbanks
python311Packages.betterproto
python311Packages.black
python311Packages.black-macchiato
python311Packages.cwl-upgrader
python311Packages.cwl-utils
python311Packages.detectron2
python311Packages.flyingsquid
python311Packages.ibis-framework
python311Packages.marimo
python311Packages.mypy-boto3-builder
python311Packages.pgmpy
python311Packages.pyannote-audio
python311Packages.pynitrokey
python311Packages.pytest-black
python311Packages.pytest-examples
python311Packages.pytest-notebook
python311Packages.python-lsp-black
python311Packages.schema-salad
python311Packages.sigstore
python311Packages.sigstore-protobuf-specs
python311Packages.spsdk
python311Packages.spyder
python311Packages.ufmt
python312Packages.betterproto
python312Packages.black
python312Packages.black-macchiato
python312Packages.cwl-upgrader
python312Packages.cwl-utils
python312Packages.detectron2
python312Packages.flyingsquid
python312Packages.marimo
python312Packages.mypy-boto3-builder
python312Packages.pgmpy
python312Packages.pynitrokey
python312Packages.pytest-black
python312Packages.pytest-examples
python312Packages.pytest-notebook

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/akg7p4sd87fv2kcbazsimnxr9vha8zk1-python3.12-black-24.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.black https://github.com/r-ryantm/nixpkgs/archive/61d712bb0e93a6f95817014233c764636d2026fe.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/61d712bb0e93a6f95817014233c764636d2026fe#python312Packages.black

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/akg7p4sd87fv2kcbazsimnxr9vha8zk1-python3.12-black-24.4.0
ls -la /nix/store/akg7p4sd87fv2kcbazsimnxr9vha8zk1-python3.12-black-24.4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

8 packages marked as broken and skipped:

python311Packages.pynitrokey
python311Packages.pynitrokey.dist
python311Packages.spsdk
python311Packages.spsdk.dist
python312Packages.pynitrokey
python312Packages.pynitrokey.dist
python312Packages.spsdk
python312Packages.spsdk.dist

24 packages failed to build:

python311Packages.aiogithubapi
python311Packages.aiogithubapi.dist
python311Packages.betterproto
python311Packages.betterproto.dist
python311Packages.ibis-framework
python311Packages.ibis-framework.dist
python311Packages.python-lsp-black
python311Packages.python-lsp-black.dist
python311Packages.sigstore
python311Packages.sigstore-protobuf-specs
python311Packages.sigstore-protobuf-specs.dist
python311Packages.sigstore.dist
spyder (python311Packages.spyder)
spyder.dist (python311Packages.spyder.dist)
python312Packages.betterproto
python312Packages.betterproto.dist
python312Packages.detectron2
python312Packages.detectron2.dist
python312Packages.flyingsquid
python312Packages.flyingsquid.dist
python312Packages.pgmpy
python312Packages.pgmpy.dist
python312Packages.sigstore-protobuf-specs
python312Packages.sigstore-protobuf-specs.dist

70 packages built:

ansible-lint
ansible-lint.dist
ansible-navigator (python311Packages.ansible-navigator)
ansible-navigator.dist (python311Packages.ansible-navigator.dist)
black (python311Packages.black)
black-macchiato (python311Packages.black-macchiato)
black-macchiato.dist (python311Packages.black-macchiato.dist)
black.dist (python311Packages.black.dist)
blacken-docs
blacken-docs.dist
cwltool
cwltool.dist
marimo (python311Packages.marimo)
marimo.dist (python311Packages.marimo.dist)
nbqa
nbqa.dist
nitrokey-app2
nitrokey-app2.dist
pynitrokey
pynitrokey.dist
python311Packages.asteroid-filterbanks
python311Packages.asteroid-filterbanks.dist
python311Packages.cwl-upgrader
python311Packages.cwl-upgrader.dist
python311Packages.cwl-utils
python311Packages.cwl-utils.dist
python311Packages.detectron2
python311Packages.detectron2.dist
python311Packages.flyingsquid
python311Packages.flyingsquid.dist
python311Packages.mypy-boto3-builder
python311Packages.mypy-boto3-builder.dist
python311Packages.pgmpy
python311Packages.pgmpy.dist
python311Packages.pyannote-audio
python311Packages.pyannote-audio.dist
python311Packages.pytest-black
python311Packages.pytest-black.dist
python311Packages.pytest-examples
python311Packages.pytest-examples.dist
python311Packages.pytest-notebook
python311Packages.pytest-notebook.dist
python311Packages.schema-salad
python311Packages.schema-salad.dist
ufmt (python311Packages.ufmt)
ufmt.dist (python311Packages.ufmt.dist)
python312Packages.black
python312Packages.black-macchiato
python312Packages.black-macchiato.dist
python312Packages.black.dist
python312Packages.cwl-upgrader
python312Packages.cwl-upgrader.dist
python312Packages.cwl-utils
python312Packages.cwl-utils.dist
python312Packages.marimo
python312Packages.marimo.dist
python312Packages.mypy-boto3-builder
python312Packages.mypy-boto3-builder.dist
python312Packages.pytest-black
python312Packages.pytest-black.dist
python312Packages.pytest-examples
python312Packages.pytest-examples.dist
python312Packages.pytest-notebook
python312Packages.pytest-notebook.dist
python312Packages.schema-salad
python312Packages.schema-salad.dist
python312Packages.ufmt
python312Packages.ufmt.dist
rstfmt
rstfmt.dist

Maintainer pings
cc @sveitser @autophagy for testing.

Already on master.


Remove support for Kubernetes 1.23

What this PR does / why we need it:

Increase the minimum Kubernetes version to 1.24
Remove image references used by Kubernetes 1.23
Remove code used to handle special cases for Kubernetes 1.23
Remove E2E tests based on Kubernetes 1.23
Update various references (e.g. tests and examples) to 1.26

Which issue(s) this PR fixes:
xref #2595
What type of PR is this?
/kind api-change
Does this PR introduce a user-facing change? Then add your Release Note here:
[ACTION REQUIRED] The minimum Kubernetes version is increased to 1.24.0. Please use KubeOne 1.5 to upgrade your clusters to Kubernetes 1.24 prior to upgrading to KubeOne 1.6. If your clusters are running Docker, please migrate them to containerd using KubeOne 1.5.

Documentation:
TBD

/hold

/hold cancel

/approve
/lgtm


uni: use sri hash

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 250979 run on x86_64-linux 1

Result of nixpkgs-review pr 250979 run on x86_64-linux 1

1 package built:

uni


Update COMBAT2022

Project cdabcf0b-7602-4abf-9afb-3b410e545703 was updated in order to have matching developmental stage and age values. We also added the most recent bionetwork & atlas values based on the tracker (Immune v1.0).
A blood atlas of COVID-19 defines hallmarks of disease severity and specificity
This ticket is created to remind that it needs to be verified in browser for release R44.

Verified in the browser, check indexed dev_stages & spreadsheet as well.


[SPARK-31279][SQL][DOC] Add version information to the configuration of Hive

What changes were proposed in this pull request?
Add version information to the configuration of Hive.
I sorted out some information show below.

Item name
Since version
JIRA ID
Commit ID
Note

spark.sql.hive.metastore.version
1.4.0
SPARK-6908
05454fd8aef75b129cbbd0288f5089c5259f4a15#diff-ff50aea397a607b79df9bec6f2a841db

spark.sql.hive.version
1.1.1
SPARK-3971
64945f868443fbc59cb34b34c16d782dda0fb63d#diff-12fa2178364a810b3262b30d8d48aa2d

spark.sql.hive.metastore.jars
1.4.0
SPARK-6908
05454fd8aef75b129cbbd0288f5089c5259f4a15#diff-ff50aea397a607b79df9bec6f2a841db

spark.sql.hive.convertMetastoreParquet
1.1.1
SPARK-2406
cc4015d2fa3785b92e6ab079b3abcf17627f7c56#diff-ff50aea397a607b79df9bec6f2a841db

spark.sql.hive.convertMetastoreParquet.mergeSchema
1.3.1
SPARK-6575
778c87686af0c04df9dfe144b8f744f271a988ad#diff-ff50aea397a607b79df9bec6f2a841db

spark.sql.hive.convertMetastoreOrc
2.0.0
SPARK-14070
1e886159849e3918445d3fdc3c4cef86c6c1a236#diff-ff50aea397a607b79df9bec6f2a841db

spark.sql.hive.convertInsertingPartitionedTable
3.0.0
SPARK-28573
d5688dc732890923c326f272b0c18c329a69459a#diff-842e3447fc453de26c706db1cac8f2c4

spark.sql.hive.convertMetastoreCtas
3.0.0
SPARK-25271
5ad03607d1487e7ab3e3b6d00eef9c4028ed4975#diff-842e3447fc453de26c706db1cac8f2c4

spark.sql.hive.metastore.sharedPrefixes
1.4.0
SPARK-7491
a8556086d33cb993fab0ae2751e31455e6c664ab#diff-ff50aea397a607b79df9bec6f2a841db

spark.sql.hive.metastore.barrierPrefixes
1.4.0
SPARK-7491
a8556086d33cb993fab0ae2751e31455e6c664ab#diff-ff50aea397a607b79df9bec6f2a841db

spark.sql.hive.thriftServer.async
1.5.0
SPARK-6964
eb19d3f75cbd002f7e72ce02017a8de67f562792#diff-ff50aea397a607b79df9bec6f2a841db

Why are the changes needed?
Supplemental configuration version information.
Does this PR introduce any user-facing change?
'No'.
How was this patch tested?
Exists UT

Test build #120449 has started for PR 28042 at commit 3b3cb8c.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25157/
Test PASSed.

Test build #120449 has finished for PR 28042 at commit 3b3cb8c.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/120449/
Test FAILed.

retest this please

Test build #120491 has started for PR 28042 at commit 3b3cb8c.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25196/
Test PASSed.

Test build #120491 has finished for PR 28042 at commit 3b3cb8c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/120491/
Test PASSed.

Merged to master.

Merged to branch-3.0 too.


Example of one dropdown field leading to updated values for another dropdown field

I have a container component and a page component. The page component is a redux form. The form is stateless.
My goal is to have two dropdown select fields, changing the first select results in a new set of values in the second select & both dropdown select fields load their values via ajax.
I have made this work but with a great deal of code and I'm sure I've made it too complex.  Posting the code here would be a huge exercise in unwinding it from the surrounding application.
Would someone be willing to post the simplest possible implementation of the above scenario using redux form?
thanks

TL;DR: The lists of options are props from a reducer, and whenever the first dropdown changes, you clear the value and load new options for the second one.
I'm going to use a countries-cities relationship here in the example.
Normalize to clear the cities value
import {createStore, combineReducers, compose } from 'redux';
import {reducer as form} from 'redux-form';
import locationLoader from './locationLoader';

const reducer = combineReducers({
  locationLoader, // reducer in charge of loading locations
  form: form.normalize({
    myForm: {
      city: (value, previousValue, allValues, previousAllValues) => {
        if (allValues.country !== previousAllValues.country) {
          // country changed. clear out city value.
          return '';
        }
        return value;
      }
    }
  })
});

Form
import {loadCities, loadCountries} from '../reducers/locationLoader';

@reduxForm({
    form: 'myForm',
    fields: ['country', 'city']
  },
  state => ({
    countries: state.locationLoader.countries,
    cities: state.locationLoader.cities
  }),
  {
    loadCities,    // action creator to dispatch load cities action
    loadCountries  // action creator to dispatch load countries action
  }
)
class MyForm extends Component {
  componentDidMount() {
    this.props.loadCountries();
  }

  render() {
    const {cities, country, fields: {country, city}} = this.props;
    return (
      <form>
        <select {...country}
          onChange={event => {
          country.onChange(event);                   // send change to redux-form
          this.props.loadCities(event.target.value); // load cities in country selected
        }}
          disabled={!countries.length}               // wait for countries to load
        >
          <option>Select a country</option>
          {countries.map(option => <option value={option.id} key={option.id}>{option.name}</option>)}
        </select>
        <select {...city}
          disabled={!cities.length}                 // wait for cities to load
        >
          <option>Select a city</option>
          {cities.map(option => <option value={option.id} key={option.id}>{option.name}</option>)}
        </select>
      </form>
    );
  }
}

This is never-run pseudo code and it may contain typos. There are several ways to do this, but you requested the simplest one.

How can I do this with v6? Fields have a normalize but this is only called when their value changes, not when another fields value has changed.

My backend developer didn't listen to me :) so the keys (ids) of the cities are not the unique. I would like to reset (show the 1st option '-- Please select ... --')  the city each time the country has been changed.
The code looks like
handleChange(event, newValue) {
const { countries } = this.props;
const result = countries.find(country => ${country.id} === newValue);
this.setState({ cities: result ? result.cities : [] });
}
render() {
const { countries } = this.props;
const { cities } = this.state;
return (
<Field
name="Country"
label={'Country'}
placeholder="Select Country"
component={renderField}
type="select"
options={countries}
optionsKey="id"
optionsValue="name"
onChange={this.handleChange}
/>
  <Field
    name="city"
    label={'City'}
    placeholder="Select City"
    component={renderField}
    type="select"
    options={cities}
    optionsKey="id"
    optionsValue="name"
  />
</div>);

}
If I select the cities with the same id for two countries, when I change the country, the city is not changed.


Downloading the bin everytime

Hi there
This one fails everytime, hence re-downloading the bin each time
TASK [brianshumate.vault : Check Vault installation] ******************************************************************************************************
fatal: [i-0ea3899fb8d4801ce]: FAILED! => {"changed": false, "cmd": "command -v vault", "msg": "[Errno 2] No such file or directory: b'command': b'command'", "rc": 2}
...ignoring

I'm running ansible 2.9.xx on Debian 10 if that helps. command -v vault works on my default bash shell, and sh too. I guess it's missing /usr/local/bin in its PATH.

Did you override the vault_bin_path? It should be set to /usr/local/bin by default.
Also, which platform are you running into this issue?

Yes, the default path.
It's running on debian 10, on AWS EC2.
Le sam. 17 oct. 2020 à 07:59, Ming Xie<EMAIL_ADDRESS>a écrit :

Did you override the vault_bin_path? It should be set to /usr/local/bin
by default.
Also, which platform are you running into this issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ansible-community/ansible-vault/issues/173#issuecomment-710757194,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOJBH4LD4WDDJ6DREOYEVLSLEXELANCNFSM4RGXIP3A
.

You're right. I can reproduce this on Debian but not CentOS.
I'm not sure why this fails. Here is the full trace for it:
TASK [ansible_vault : Check Vault installation] ***********************************************************
task path: /vagrant/roles/ansible_vault/tasks/main.yml:34
<localhost> ESTABLISH LOCAL CONNECTION FOR USER: vagrant
<localhost> EXEC /bin/sh -c 'echo ~vagrant && sleep 0'
<localhost> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo /home/vagrant/.ansible/tmp/ansible-tmp-1602956224.225932-261002391649915 `" && echo ansible-tmp-1602956224.225932-261002391649915="` echo /home/vagrant/.ansible/tmp/ansible-tmp-1602956224.225932-261002391649915 `" ) && sleep 0'
Using module file /usr/lib/python3/dist-packages/ansible/modules/commands/command.py
<localhost> PUT /home/vagrant/.ansible/tmp/ansible-local-7610_fcwo_gh/tmpe1nrve8h TO /home/vagrant/.ansible/tmp/ansible-tmp-1602956224.225932-261002391649915/AnsiballZ_command.py
<localhost> EXEC /bin/sh -c 'chmod u+x /home/vagrant/.ansible/tmp/ansible-tmp-1602956224.225932-261002391649915/ /home/vagrant/.ansible/tmp/ansible-tmp-1602956224.225932-261002391649915/AnsiballZ_command.py && sleep 0'
<localhost> EXEC /bin/sh -c 'sudo -H -S -n  -u root /bin/sh -c '"'"'echo BECOME-SUCCESS-eixwytotrwwdnaumdmdroziddvgsyygy ; PATH=/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin /usr/bin/python3 /home/vagrant/.ansible/tmp/ansible-tmp-1602956224.225932-261002391649915/AnsiballZ_command.py'"'"' && sleep 0'
<localhost> EXEC /bin/sh -c 'rm -f -r /home/vagrant/.ansible/tmp/ansible-tmp-1602956224.225932-261002391649915/ > /dev/null 2>&1 && sleep 0'
The full traceback is:
  File "/tmp/ansible_command_payload_tzso79xq/ansible_command_payload.zip/ansible/module_utils/basic.py", line 2592, in run_command
    cmd = subprocess.Popen(args, **kwargs)
  File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
fatal: [localhost]: FAILED! => {
    "changed": false,
    "cmd": "command -v vault",
    "invocation": {
        "module_args": {
            "_raw_params": "command -v vault",
            "_uses_shell": false,
            "argv": null,
            "chdir": null,
            "creates": null,
            "executable": null,
            "removes": null,
            "stdin": null,
            "stdin_add_newline": true,
            "strip_empty_ends": true,
            "warn": true
        }
    },
    "msg": "[Errno 2] No such file or directory: b'command'",
    "rc": 2
}
...ignoring

command is a shell built in, not a command. This looks like a regression of a "fix" for ansible-lint.
https://github.com/ansible-community/ansible-vault/commit/a770997232fdd86eee0c5c174306dbb40077a73e

Indeed, I just checked, reverting the commit fixed it.

Thanks for reportingand testing!

vault version could be used as a pre-condition test.

vault version could be used as a pre-condition test.


Fancy Zones Doesn´t fit the whole screen

Microsoft PowerToys version
v0.37.2
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
When editing the zones the software shows them as full screen, but when I try to fit a window it only uses a portion of the screen.
PowerToysReport_2021-05-24-17-34-26.zip

✔ Expected Behavior
The zones would use the whole screen

❌ Actual Behavior
It leaves a huge space in the bottom and right part of the screen

Other Software
No response

I was going to open this issue. I am using external monitor at home and resolution of the monitor and laptop's screen are different. So i have to resize fancy zone everytime when i switch main screen. It would be good if it the bug fix.

What monitor was custom layout 1 created under and is it a canvas based layout?

Why: Canvas base layouts are dependent on screen resolution and lets us directly lock everything to exactly where you wanted it.  That looks a lot like your smaller monitor's resolution

The first time it occurred it was made in the smaller resolution monitor, but I thought that would be the issue so I created another one and the bug still was there.
With the last update it got solved, maybe because of a reset but I can't reproduce the error again, so I think in my case it's fixed!
Thanks!!!!!


Bug Fix: Image Filter App (effects overlapping each other)

Issue Type:

[x] Bug Report
[ ] Feature Request
[ ] Documentaion

Describe the bug

There are 8 effects and if someone tries multiple effects at the same time, they overlap each other
for instance, If I applied the Vintage effect, then the Lomo effect, the Vintage effect is already there onto the image over to that Lomo effect is also applied.

Possible solution

Clearing previous filter if already applied before applying a current effect, changes to script.js
creating revertFilters()  function and applying it to all 8 effects to remove overlapping of effects

Screenshots

If applicable, add screenshots to help explain your problem.

please assign me this issue as a GSSoC participant. If any doubt about a given issue, I can clear it more.


Add documentation for each template

As discussed in AliSoftware/SwiftGen#232
⚠ WIP ⚠

I wanted to work on the documentation today, but am not sure how much worth it is, as we'll be removing quite a few things once we work on 5.0. Do I only document the templates we want to keep for 5.0?

I think it's only worth working on documenting templates we intend to keep. No need to document things (templates, tags, filters or anything) that we intend to drop in 5.0


Establish io

Work to establish actual hardware I/O, plus several other completions (like webrepl support)

Accepted


Dropbox link

Time:  2021-06-24
Venue: Shenzhen, China
from 4:04PM to  4:38PM ， I'm downloading data， the link fails suddenly and cannot be accessed。
DropBox Link: https://www.dropbox.com/sh/lmd8wmgibz24r2h/AABnfUHq6k-H_sT7I0UGR_D5a?dl=0
Response: Error (404)  ,  We can't find the page you're looking for.
Hope you can fixed it


Cucumber JSON Test Corpus

Each Cucumber implementation that produces JSON reports does so inconsistently because the JSON format does not have a schema.
To make it easier to test tools that consume Cucumber JSON we would like to have a corpus of JSON documents generated by different Cucumber implementations and versions.
There is an existing corpus in json-to-messages. They are not in git, but generated by running make.
The proposal is to:

Add JSON documents to Git to make them easier to consume without having to run any build commands
Move them out of json-to-messages to a separate json-corpus directory (separation of concerns)
Use make to orchestrate the (re)generation of JSON files when needed
Base the corpus on feature files defined in compatibility-kit

This corpus would be used to test json-to-messages as well as some proprietary tools built in SmartBear. The same corpus could be used to test any tool that consumes Cucumber JSON, so we hope to get input from the community here.

Hi @laxersaz - would you be interested in collaborating on this? I assume you've had to deal with JSON inconsistencies in Cluecumber?

@laxersaz I see there are some documents in https://github.com/trivago/cluecumber-report-plugin/tree/main/example-project/json - do you have a record of what cucumber implementation/version was used to generate each of these?

These initially came from your repo: https://github.com/aslakhellesoy/cucumber-json-formatter

In the example project readme, it is also referenced:
The example Cucumber JSON files are located in the project's json directory. These are based on the https://github.com/aslakhellesoy/cucumber-json-formatter project. The report is generated inside the target/cluecumber-report directory.

These initially came from your repo: https://github.com/aslakhellesoy/cucumber-json-formatter

Aha! And I see I wrote this:

This repo will document the behaviour of the json formatter for different Cucumber implementations.

I had completely forgotten about this. I also see that this repo is a fork of https://github.com/cucumber/cucumber-json-testdata-generator which has had a little bit of activity recently, the latest one by @tooky.
What do you say - shall we just rubber-stamp https://github.com/cucumber/cucumber-json-testdata-generator as the official one and continue to collaborate there?

Sure makes sense.

Ok I'm closing this then. The official repo for Cucumber JSON test data is https://github.com/cucumber/cucumber-json-testdata-generator


Teacher API In progress.

Note that this PR is branched off of the branch teacher-dev and is also rooted in the branch teacher-api.
PS: This PR is in progress, but if you feel like it, you may merge it if needed. It should probably be merged in after the branch teacher-dev authored by @ndall.
This PR includes the initial implementation of the API for the teachers. With the new system I wasn't able to get the stuff running, so none of the APIs are tested. Additionally credentials are missing from the implementation.
I imagine we add an endpoint called login which returns an auth token given valid credentials. This token can then be sent in the auth header for each request.
The initial branch teacher-api had logic such that each teacher is only able to modify and view his/her own assignments. However, in my own implementation I have not enforced this as I don't know if we want this.
I have not touched the original implementation that @ndall committed.

Please approve Kian


Mismatch in TMDB

Seems like an edge case:
Code breaks when TMDB match returns is more than +/- 1 year of release date.
Example: Need for Speed (2014)
TMDB look up returns Need for Speed (2018)
directory.py - Line 126 only accepts movie_release_year + / - 1 so you get a KeyError: 'release_date'
You can bypass this error by removing the TMDB key (quick fix) from default_config

wrong project. pls delete.