New tools

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 116283 at 584cec47 run on x86_64-linux 1

6 packages built successfully:

castxml
m2r
md4c
python38Packages.pygccxml
python39Packages.pygccxml
xmldiff

3 suggestions:

warning: build-tools-in-build-inputs
llvm is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/tools/castxml/default.nix:37:3:
   |
37 |   buildInputs = [
   |   ^

warning: missing-phase-hooks
checkPhase should probably contain runHook preCheck and runHook postCheck.
Near pkgs/development/tools/castxml/default.nix:52:3:
   |
52 |   checkPhase = ''
   |   ^

warning: unused-argument
Unused argument: stdenv.
Near pkgs/tools/text/xml/xmldiff/default.nix:2:3:
  |
2 | , stdenv
  |   ^

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 116283 run on x86_64-linux 1

6 packages built:

castxml
m2r
md4c
python38Packages.pygccxml
python39Packages.pygccxml
xmldiff

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

castxml:

warning: build-tools-in-build-inputs
llvm is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/tools/castxml/default.nix:37:3:
   |
37 |   buildInputs = [
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md


adding option to clamp to border and border being white

I need to see how to not have package updates not trigger on PR check

Yeah I just noticed. This should fix my shadows

We should not modify the default "null" sampler to be white. If you need a clamp to border, white colored sampler, you should create one. So we need to add the clamp to border address mode, and a new property, the border color.

Good point. It should be fixed

Two things need to be changed.
Default sampler should be transparent black and so should be the default option in create info


There is no top border in dropdowns thatopen upwards.

I noticed that there is no top border in dropdowns that open upwards.

@Nudasoft Thanks for your feedback! I fixed this problem in #16 and bump version to 1.2.2. Please check it out.


Inability to change token visibility state after changing its name

Description
When the module is enabled it makes it impossible to change the token visibility state after its name was changed when the token was invisible. Confirmed with the module Find The Culprit that Light/Sound Mask is responsible for this.
Steps to Reproduce

Place a token on the map
Change visibility state to invisible
Open the token menu and change its name
Toggle visibility state
Result: The visibility state cannot be toggled

Versions
Module: 0.5.2
dnd5e: 2.0.3
Foundry: 10.290

Additional info

Check attached video

token bug.webm

Thanks! Fixed in v0.6.0. Sort of took the long way round to address this, as I decided to improve how all the configurations were done.


Example of music generated using mostly default parameters (tier-2), at epoch9 and epoch11

In case folks are interested, I've uploaded several of the generated wav files at epoch=9 and epoch=11.
Please browse to:  https://soundcloud.com/user-637335781
Thanks to kundan2510 for answering my earlier question re mem alloc error and to reduce batch size.
The trainnig run was as follows:
THEANO_FLAGS=mode=FAST_RUN,device=gpu0,floatX=float32 python -u models/two_tier/two_tier.py --exp BEST_2TIER --n_frames 64 --frame_size 16 --emb_size 256 --skip_conn False --dim 1024 --n_rnn 3 --rnn_type GRU --q_levels 256 --q_type linear --batch_size 64 --weight_norm True --learn_h0 True --which_set MUSIC
GPU: Single GPU : 8 GB GTX 1080 with 2560 CUDA Cores
Epoch 9 took about 24 hours, and getting to epoch 11 took an additional 6 hours. Training run was aborted at the start of epoch12
This is a very exciting project/code you guys have! wow!
-Best regards!

I am glad that it worked. Closing the issue.


routes and mongodb

This uses some of the scripts from sweeper/get-prs to populate a database.
Queries are working, except where noted: working on an aggregation pipeline for pareto results (label:BLOCKED).

@raisedadead yes, go ahead. :)

Done.

@raisedadead Tracey and I already tested #34, so you can go ahead and merge it.  working on another PR which will finish the work #34 started to completely replace the data.json file.  Should have that PR ready by Jan 2nd.


[BEAM-2277] Fix URI_SCHEME_PATTERN in FileSystems

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify.
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

FileSystems#URI_SCHEME_PATTERN was (?<scheme>[a-zA-Z][-a-zA-Z0-9+.]*)://.* which caused IllegalArgumentException when using Hadoop filesystem.
The reason is that as part of its flow in HadoopResourceId#getCurrentDirectory it uses java.net.URI#resolve which converts URIs of format "hdfs:///path/to/file" to "hdfs:/path/to/file", which is still a valid HDFS URI, however was not correctly identified as HDFS scheme in FileSystems#parseScheme

R: @dhalperi / @lukecwik

Verified that using this change solves the issue in https://issues.apache.org/jira/browse/BEAM-2277 and now able to run WordCount successfully using Spark runner reading/writing to/from HDFS.

Coverage decreased (-0.01%) to 70.186% when pulling ca05ed560888a2f2a86442b89e23fb7f49e1acfd on aviemzur:fix-uri-scheme-pattern-in-filesystems into d6ac39a23e50e82c013e5052b48cb6ffbf929195 on apache:master.

Ooh, nice catch. Unfortunately, this is not the right fix -- HadoopResourceId is not implemented correctly. (The entire point of not using URI is that URI is unusably terrible in what it does, and we want normalized, consistent paths with obvious behavior.)
Of course the real issue is that the designer of FileSystems APIs did not provide any documented semantics or a test suite. I'll work on that now.

But a URI is able to have /, //, and /// and they all mean different things.

After speaking with Dan in person, it turns out that other parts of our codebase use string based equality and sorting instead of URI based equality and sorting and thus would break if /// was changed to / since it would change sort orders and equality checks in other parts of the code base. This will require making HadoopResourceId and all other ResourceIds stricter until the internals are migrated to using URIs.

Sure.
The regex for URI is still wrong though, so do we want to merge this fix as well?

I'll merge this and keep proceeding on BEAM-2277

Thanks @aviemzur !


Submodules don’t get processed

List of modules sent to server in list_of_modules duplicates modules, e.g. two entries for ../www/sdl/modules/languages.json if you select one of the language-specific submodules
Looks like submodules are somewhat set up to process, but only by a weird approach: the input filename from the frontend needs to have an md5 of the submodule’s title attribute appended to the end, e.g. ../www/sdl/modules/languages.json13add3ace4d7ac08f0190cb68b6f71d6 for the PHP Language Guidance submodule. (see Trello processor)
JS doesn’t properly add this md5 hash in its submodule renderer

Fixed as of da08e1a25529c1c5fdbf4de2a2b4d31e1733bf56


Cannot change param name from 'page' to 'cursor'.  getNextPageParam: (lastPage) => lastPage["cursor"], returns the cursor as page="cursorValue"

What version of kubb is running?
v2.19.5
What platform is your computer?
MacOS
What version of external packages are you using(@tanstack-query, MSW, React, Vue, ...)
5
What steps can reproduce the bug?
Basically the issue is that I cannot change {page: pageParam}  to be something like {cursor: ''}, whatever getNextPageParam returns it is appended to page

	const getProjectsQuery = useGetProjectsInfinite(
		{
			filter: debouncedFilter.trim(),
		},
		{
			query: {
				initialPageParam: 0,
				getNextPageParam: (lastPage) => {
					return lastPage.data?.cursor;
				},
			},
		}
	);

export function getProjectsInfiniteQueryOptions( 	params?: GetProjects["queryParams"], 	options: GetProjects["client"]["parameters"] = {} ) { 	const queryKey = getProjectsInfiniteQueryKey(params); 	return infiniteQueryOptions({ 		queryKey, 		queryFn: async ({ pageParam }) => { 			const res = await client<GetProjects["data"], GetProjects["error"]>({ 				method: "get", 				url: /api/v1/customer/projects, 				...options, 				params: { 					...params, 					["page"]: pageParam, 					...(options.params || {}), 				}, 			}); 			return res.data; 		}, 		initialPageParam: 0, 		getNextPageParam: (lastPage) => lastPage["cursor"], 		getPreviousPageParam: (firstPage) => firstPage["cursor"], 	}); }

Setting infinite.queryParam to 'cursor' does not work in the kubb.config.js?

@stijnvanhulle
Actually it does, but is that supposed to be used for page based pagination?
We use two strategies for infinite loading, cursor based and page based, so seems that it is not possible to generate different query param names for different strategies?

@gentrith44belt I would suggest using https://www.kubb.dev/plugins/swagger-tanstack-query/#override and defining based on path/operation what your queryParam and cursorparam will be.
With Kubb we can not know what the cursor is and what is paginated so that's why both options are there and it's then up to the implementer to define which one to be used.

@stijnvanhulle I will take a look, we changed the backend to use the same parameter name. Thanks for the response, keep up the good work 👍


Add Future support and example app

Hi! I've updated this framework to

Use SwiftNIO's Futures, instead of GCD.
Add an example app, which mirrors the default Vapor 3 project structure.
Fix a couple small GraphiQL bugs.

(Note that until https://github.com/GraphQLSwift/GraphQL/pull/43 is merged, I'm pointing to my custom branch of GraphQLSwift.)
Thanks very much for this framework, I think it will make setting up a Swift GraphQL server much, much easier!

Is there a branch o can run now

You can add
.package(url: "https://github.com/noahemmet/GraphQLRouteCollection.git", .branch("futures"))

to your Package.swift's dependencies if you'd like to test. Please let me know if you find any bugs or weird behavior!


Configuring components.ingressGateways.k8s.service.externalTrafficPolicy breaks ingress gateways

Bug description
Setting externalTrafficPolicy to Local wipes out all the default configuration for the ingressgateway service, including the ports.
[x] Configuration Infrastructure
[ ] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
A valid service is generated with a mix of configured values and defaults.
When generating a manifest with the following configuration:
Steps to reproduce the bug
Generate a manifest using the following IstioOperator:
apiVersion: install.istio.io/v1alpha2
kind: IstioOperator
spec:
  hub: gcr.io/cf-routing
  profile: default
  components:
    ingressGateways:
      - name: istio-ingressgateway
        enabled: true
        k8s:
          service:
             externalTrafficPolicy: Local

Observed:
The istio-ingressgateway service lacks any ports:
apiVersion: v1
kind: Service
metadata:
  annotations: null
  labels:
    app: istio-ingressgateway
    istio: ingressgateway
    release: istio
  name: istio-ingressgateway
  namespace: istio-system
spec:
  externalTrafficPolicy: Local
  ports: null
  selector:
    app: istio-ingressgateway
    istio: ingressgateway
  type: LoadBalancer

Desired:
A valid service is produced:
apiVersion: v1
kind: Service
metadata:
  annotations: null
  labels:
    app: istio-ingressgateway
    istio: ingressgateway
    release: istio
  name: istio-ingressgateway
  namespace: istio-system
spec:
  externalTrafficPolicy: Local
  ports:
  - name: status-port
    port: 15021
    targetPort: 15021
  - name: http2
    port: 80
    targetPort: 8080
  - name: https
    port: 443
    targetPort: 8443
  - name: tls
    port: 15443
    targetPort: 15443
  selector:
    app: istio-ingressgateway
    istio: ingressgateway
  type: LoadBalancer

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
17:48 $ istioctl version
client version: 1.6.0

How was Istio installed?
N/A
Environment where bug was observed (cloud vendor, OS, etc)
N/A

The problem here is that list items have replace rather than merge semantics. That clearly isn't what we want in most cases.

An update on this: it appears that the json merge library we're using is not doing what we want in this case. It behaves this way with lists in the picture (hence our gateways) and the at a glance the fix is likely to be quite involved. A better option would be to go with the k8s strategic merge library which has excellent test coverage and obviously works as k8s users expect. The trouble with using that library (other than that it's internal to k8s) is that it requires struct tag annotations. The good news is once these tags are added it seems to work as we'd like, but adding these into our protos seems unnecessary since we're looking for default behavior everywhere. I'll spend a bit more time to see if there's a way around this.


Roll Engine from 94e5cb8b2b0d to c82438816938 (1 revision)

https://github.com/flutter/engine/compare/94e5cb8b2b0d...c82438816938
2021-09-28<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from sFMn4Ory_... to fvDpNa7Tc... (flutter/engine#28900)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from sFMn4Ory_r_G to fvDpNa7TcAQr
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Task :app:bundleReleaseJsAndAssets FAILED

Description
My project uses react-native 0.57.1 . The project cannot be upgraded because my project contains few libraries which no longer provides supports. When i try to release the application it is giving me error as
`> Task :app:bundleReleaseJsAndAssets
warning: the transform cache was reset.
Loading dependency graph, done.
ENOENT: no such file or directory, open '/var/folders/0d/j3_gbcw90g91rth_wg55hmlm0000gn/T/metro-cache/02/3154c487e966a254c29e1d9457ab44ec57855038ebde7a743fe3e6fba3e197fa1b73aa'
Error: ENOENT: no such file or directory, open '/var/folders/0d/j3_gbcw90g91rth_wg55hmlm0000gn/T/metro-cache/02/3154c487e966a254c29e1d9457ab44ec57855038ebde7a743fe3e6fba3e197fa1b73aa'
at Object.openSync (fs.js:462:3)
at Object.writeFileSync (fs.js:1384:35)
at FileStore.set (/Users/niteshrajkhanal/Desktop/pharmasolution/pharmasolution-reactnative/node_modules/metro-cache/src/stores/FileStore.js:43:8)
at Cache.set (/Users/niteshrajkhanal/Desktop/pharmasolution/pharmasolution-reactnative/node_modules/metro-cache/src/Cache.js:96:31)
at /Users/niteshrajkhanal/Desktop/pharmasolution/pharmasolution-reactnative/node_modules/metro/src/Bundler.js:190:13
at Generator.next ()
at step (/Users/niteshrajkhanal/Desktop/pharmasolution/pharmasolution-reactnative/node_modules/metro/src/Bundler.js:11:657)
at /Users/niteshrajkhanal/Desktop/pharmasolution/pharmasolution-reactnative/node_modules/metro/src/Bundler.js:11:817
at processTicksAndRejections (internal/process/task_queues.js:97:5)

Task :app:bundleReleaseJsAndAssets FAILED
Task :app:javaPreCompileRelease

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:bundleReleaseJsAndAssets'.

Process 'command 'node'' finished with non-zero exit value 1

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 35s
15 actionable tasks: 15 executed
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/getting-started.html
✨  Done in 39.71s.`
React Native Version
0.57.1
Output of npx react-native info
npx react-native info                                                                                ─╯
React Native Environment Info:
System:
OS: macOS 13.3.1
CPU: (8) x64 Apple M1
Memory: 21.51 MB / 8.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 12.22.12 - ~/.nvm/versions/node/v12.22.12/bin/node
Yarn: 1.22.19 - ~/.yarn/bin/yarn
npm: 6.14.16 - ~/.nvm/versions/node/v12.22.12/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
IDEs:
Android Studio: 2022.2 AI-222.4459.24.2221.9862592
Xcode: 14.3/14E222b - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.57.1 => 0.57.1
Steps to reproduce
To make APK file

Delete (index.android.bundle) files inside directory android/app/src/main/assets.
run $ react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res
Delete folders (drawable,drawable-hdpi,drawable-mdpi,drawable-xhdpi,drawable-xxhdpi,drawable-xxxhdpi,raw)
run $ react-native run-android --variant=release

Snack, code example, screenshot, or link to a repository

⚠	Unsupported Version of React Native
ℹ	It looks like your issue or the example you provided uses an unsupported version of React Native. Due to the number of issues we receive, we're currently only accepting new issues against one of the supported versions. Please upgrade to latest and verify if the issue persists (alternatively, create a new project and repro the issue in it). If you cannot upgrade, please open your issue on StackOverflow to get further community support.

ok.

My project uses react-native 0.57.1

Closing as we can't support 0.57 as it's just too old sorry.


Fix includes for Stan Math /prim flatten

Submission Checklist

[x] Run unit tests: ./runTests.py src/test/unit
[x] Run cpplint: make cpplint
[x] Declare copyright holder and open-source license: see below

Summary
https://github.com/stan-dev/math/pull/1606 will remove mat, arr and scal from the Stan Math's /prim folder. This PR fixes the includes in the Stan repo.
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
Rok Češnovar
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

This PR should be merged together with https://github.com/stan-dev/math/pull/1606 and https://github.com/stan-dev/cmdstan/pull/792

This one needs another review and then we are really done @mcol


fix(overflow-menu): position jumping

Related Ticket(s)
Closes #9827
Description
the refBottom needs to be compared to the containerTop, so that the menu sticks to the bottom of button
Example (using local yarn pack:
https://codesandbox.io/p/devbox/test-overflowmenu-t4slfp?file=%2F.codesandbox%2Ftasks.json%3A1%2C241
live demo: https://t4slfp-9000.csb.app/
Changelog
New

{{new thing}}

Changed

changed refBottom to a let and then equal refBottom = refBottom - containerTop;
^ wondering if this can be cleaned up code wise, but testing locally with overflow-menu it seems successful

Removed

{{removed thing}}

@kennylam thanks for the approval! Thinking I should cherry pick this commit into the v1 branch as well?

Ooh yes, good call!


Visual studio 2019 go to definition and Intellisense not working in Python project

This issue has been moved from a ticket on Developer Community.

The description of problem is as title,  thanks for your help.
Closing VS and deleting .vs folder does not help.

Original Comments
Feedback Bot on 1/11/2022, 10:12 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Original Solutions
(no solutions)

Can you please provide some sample code or a sample application so we can try to repro this?

Closing old issue. If this is still a problem, please reopen with the information requested. thanks


[Healer Layout] Debuffs on healer raid frames

Option to completely hide debuffs on the player raid frames. Many of us use addons like Decursive to dispel, and having whole health bars covered in icons makes it hard to see people their health.

with new update, now you can disable big debuff icon on raid frames
go to config panel, unitframe section, uncheck debuff watch


Add endpoint /resourcepool/resource/vpn

Description
No response

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/issues/194


Planets in house KP -  api has a bug ( one of the house is getting all the planets again)

SC of planets in house KP - from the new KP link

SC of planets in house KP Astrosage

Very nice catch! We'll investigate this further and get back to you in the meantime feel free to look at the code in calculate.cs. As of now I can't quite see where the bug is it is not obvious some digging is required.


GroupBy.dtypes is deprecated in upstream

Following this change in upstream:

https://github.com/pandas-dev/pandas/pull/51997

Xref https://github.com/dask/dask/issues/10089.
Fixes this failure in upstream build:
FutureWarning: DataFrameGroupBy.dtypes is deprecated and will be removed in a future version. Check the dtypes on the base object instead

[x] Tests added / passed
[x] Passes pre-commit run --all-files

Maybe I'm missing some subtlety here

@jrbourbeau my understanding is that your method would emit a warning around numeric_only if there's any non-numeric column in self.obj (including those being grouped on), whereas @j-bennet's approach would only be checking the non-group columns for non-numerics (which I assume are the only columns that would be impacted by the option?).
Not sure what pandas behavior for the deprecation warning is here or if we want to mirror it

@jrbourbeau

Given the deprecation warning says "Check the dtypes on the base object instead", is there a reason we can't just do something like

I was hoping to avoid _get_numeric_data, which is retrieving dataframe columns, while we only need dtypes of those columns. Yes, your way would work, and maybe I should just do that.

my understanding is that your method would emit a warning around numeric_only if there's any non-numeric column in self.obj (including those being grouped on)

Ah, good point. You're totally right. In that case though, we should be able to just subtract off the grouping column(s). Those are available at self._meta.grouper.names. That is:
has_non_numerics = (set(self.obj._meta.dtypes.index) - set(self._meta.grouper.names)) - set(numerics.columns)

@j-bennet and I tried this suggestion ^ offline and it appear to work (including in the tests @j-bennet correctly highlighted in https://github.com/dask/dask/pull/10111#issuecomment-1487532908). Additionally, it looks like this also allows us to remove some xfails when using pandas>=2.0

I was hoping to avoid _get_numeric_data, which is retrieving dataframe columns, while we only need dtypes of those columns.

Fair point. But since we're calling _get_numeric_data on _meta, it should still be returning an empty pandas DataFrame/Series, so I wouldn't worry about micro-optimizing for just retrieving dtypes in this case. You bring up a good point about us using a private method though. I'm not totally sure if _get_numeric_data and pd.api.types.is_any_real_numeric_dtype agree in their definitions of what constitutes "numeric" dtypes. @phofl do you know if those two method agree with one another?

The remaining upstream failures are because of https://github.com/pandas-dev/pandas/issues/52151.

@jrbourbeau We have a fast path for this that depends on the block type unfortunately. Checking for is_numeric_dtype and _is_numeric on the dtype (e.g. getattr(ser.dtype, "_is_numeric")) should be equivalent, but again this is private unfortunately...

Thanks for the info @phofl. No worries, let's just stick with _get_numeric_data for now. We've been using it here, and in other places, for a long time. It'd definitely be nice to avoid using private methods, but that's a separate issue from what this PR is fixing


Fix syntax in template

@emord @czue err slightly awkward commits posing as dan, but fixed this when deploying datadog

actually just gonna close so people don't get confused when they do a git blame

lol


[Docs] Search feature is broken

Description

Fix the search feature in Meshery docs

[Optional] To Reproduce
Steps to reproduce the behavior:

Go to 'https://meshery.layer5.io/docs/'
Try using the search bar
See error

@chandrashritii, I just checked the search bar and they work fine.

@EmmanuelTheCoder That's odd. The search feature has been broken since a few months. It's not working for me. Just to confim, you're talking about the search feature on  https://meshery.layer5.io/docs, right?
Also, if it is working for you, that's great. Can you post a screenshot?


Fix time order on DateTimePicker #775

This PR closes #775
Description
The time order was wrong on DateTimePicker with 24hours display

when will this be published on npm?

Next week probably

I need this fix, but I can't figure out how to build it.  I published a fork here:
https://www.npmjs.com/package/@maven-io/material-ui-pickers
When I install the package I get this error:
Command failed.
Exit code: 127
Command: lerna bootstrap
Arguments:
Do you know what I am missing?

You must make a build and then publish it

@joejoejoew as I needed too, I created a temporary package while the version isn't closed, take a look<EMAIL_ADDRESS>(yeah, the name is to remember that this is really temporary)


Generate Python code for CPU kernels

@jpivarski
@trickarcher although this may not be directly relevant to your infrastructure code, you might be interested in taking a look :)

Great start!

Maybe just put the LICENSE comment line at the top of dev/genpython.py.

Done.

What does the generated documentation look like? You could attach some screenshots to the GitHub comments.

Okay, I like the choice of putting it last in the left-bar, since it is the most internal of internal interfaces. It should probably be called "kernels," rather than "cpukernels," and get some text at the beginning explaining what this is all about, but that can come later. There's no bulleted-list-as-table-of-contents, but I had forgotten that the left-bar expands when you open one of these, so everything that we need is there.
When a function has several type variants, like awkward_ListArray_min_range, how do you find out that the corresponding real names are

awkward_ListArray32_min_range
awkward_ListArrayU32_min_range
awkward_ListArray64_min_range

Are they in a bulleted list below the screenshot you showed? They could be given as three blue signatures below the heading. Then you wouldn't need the for C in int which is wrong (can't be evaluated; int isn't iterable; you probably intended it for cases like for C in (bool, int, float) but it came out wrong in this case).
If it makes things any easier, you could just pretend that int32_t, uint32_t, int64_t are Python types, as though someone did this:
>>> int32_t = int
>>> uint32_t = int
>>> int64_t = int

When we evaluate them for tests, we can put that in the preamble.
The requirements are (a) we have to be able to look up the real names of the function, such as awkward_ListArray32_min_range, because that's what ctypes sees, (b) the Python code needs to be executable, because we'll want to use exactly the same code in the tests, to demonstrate that these really are the definitions, and (c) type-variants of the same function (defined in terms of the same templated code, internally) need to be grouped somehow.
It would be enough to make it look like this:
awkward_ListArray_min_range
===========================

.. py:function:: awkward_ListArray32_min_range(tomin: List[int64_t], fromstarts: List[int32_t], fromstops: List[int32_t], lenstarts: int64_t, startsoffset: int64_t, stopsoffset: int64_t)

.. py:function:: awkward_ListArrayU32_min_range(tomin: List[int64_t], fromstarts: List[uint32_t], fromstops: List[uint32_t], lenstarts: int64_t, startsoffset: int64_t, stopsoffset: int64_t)

.. py:function:: awkward_ListArray64_min_range(tomin: List[int64_t], fromstarts: List[int64_t], fromstops: List[int64_t], lenstarts: int64_t, startsoffset: int64_t, stopsoffset: int64_t)

.. code-block:: python

    def awkward_ListArray_min_range(
        tomin,
        fromstarts,
        fromstops,
        lenstarts,
        startsoffset,
        stopsoffset
    ):
        shorter = fromstops[stopsoffset + 0] - fromstarts[startsoffset + 0]
        for i in range(lenstarts):
            range = fromstops[stopsoffset + i] - fromstarts[startsoffset + i]
            shorter = (shorter < range) if shorter else range
        tomin[0] = shorter

    awkward_ListArray32_min_range = awkward_ListArray_min_range
    awkward_ListArrayU32_min_range = awkward_ListArray_min_range
    awkward_ListArray64_min_range = awkward_ListArray_min_range

(Or some other simple way to indicate that the three type variants correspond to the one implementation, without a lot of verbiage.)
A few things I found in typing this out: (1) there's a terrible bug in the original function: startsoffset was used in fromstops and stopsoffset was used in fromstarts. The bug never caused an error because it's likely that the offsets have always been zero, but it's a ticking time bomb. Can you please fix this (in another PR, if you want to keep it separate from this work) and search for cases where offsets are used with the wrong arrays? They are always linked by name; you'll always be able to tell. If you fix that and all tests continue to pass, then we're nevertheless in a much better state because these bugs will reveal themselves as segfaults, and would be hard to debug.
The second thing is (2) the tomin assignment must be tomin[0] = shorter. Otherwise, Python can't export the value of tomin from the function. In the signatures, you're saying it's a List, let's take that seriously and use it that way because it's the only way to translate the assignment-through-pointer of C into Python. There aren't any &tomin instances in the codebase—explicit pointers are used throughout, so that should make it easier.
(3) This while loop wasn't translated into a for loop. I don't see any reason why it can't be—it has simple structure.
(4) Python builtin function names like range should be given the same treatment as keywords like from: we should avoid them in these code blocks because they're needed for things like making for loops. You don't have to look up a whole list of builtins to avoid, fixing range should be enough for now.
Sorry I found so many things to fix! I wanted to merge this and move on to testing, but some of these things will bite us in the tests. (It's probably a good hint that the tests should include non-zero offsets, to find any other bugs like the one above.)

It should probably be called "kernels," rather than "cpukernels,"

Done.
I made the functions having various template variants look like this -

What do you think?

The second thing is (2) the tomin assignment must be tomin[0] = shorter

I made all *x = y assignments into x[0] = y.

(3) This while loop wasn't translated into a for loop.

Done.

(4) Python builtin function names like range should be given the same treatment as keywords like from: we should avoid them in these code blocks because they're needed for things like making for loops.

Done.

I know I said earlier that integer types should all be int in Python, but we have to distinguish the integer specializations, so revert to int32_t, uint32_t, int64_t. It's a matter of removing the code that maps all of them to int. Same for float vs double. We can pretend that these symbols have been defined in Python, as that's easy to do in the testing code.
The signatures are all on the specialized functions (in blue), so they don't need to be generalized in the implementation, which means that you don't need a C or a C = int. See my code example.
After that, the documentation is perfect.
But then there's still the issue of the wrong offsets being used, discovered by looking at this documentation, but independent of it. That can be another PR, but a sweep through all kernels, looking for this type of mistake, needs to be done.

@jpivarski What do you think?
There is specialized code in genpython.py to deal with functions having dynamic memory arrays like https://github.com/scikit-hep/awkward-1.0/blob/master/src/cpu-kernels/operations.cpp#L3307. I'll remove that code when I can refactor the code to remove the dynamic size allocation.

This looks great! I'd merge it now if you're ready. Are you?

This looks great! I'd merge it now if you're ready. Are you?

Yes :)


cas: rename to store?

The CAS package also implements a secondary index system. Should we rename it to generically be the "store"?

Didn't we just go in the other direction for some reason? :-/
On Tue, Mar 31, 2015 at 3:53 PM, Brandon Philips<EMAIL_ADDRESS>wrote:

The CAS package also implements a secondary index system. Should we rename
it to generically be the "store"?
—
Reply to this email directly or view it on GitHub
https://github.com/coreos/rocket/issues/707.

@jonboulle I renamed it early on from downloadstore https://github.com/coreos/rocket/commit/fe67591878f4a4a1d995f1e088979f081c0a1067

Back then it was only a CAS and was being used for stuff other than downloads, now it is lots of stuff.

OK, this change SGTM
On Tue, Mar 31, 2015 at 4:00 PM, Brandon Philips<EMAIL_ADDRESS>wrote:

Back then it was only a CAS and was being used for stuff other than
downloads, now it is lots of stuff.
—
Reply to this email directly or view it on GitHub
https://github.com/coreos/rocket/issues/707#issuecomment-88278056.


Analytics is a Prerequisite

Although the Prerequisites section does mention "Analytics" it does not clearly state that it's a prereq.  Maybe more relevant for Azure Devops Server where Analytics is a separately installed extension (that's my understanding anyway). I presume these widgets don't become available until you install the extension.

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

ID: a9d627b9-9aa8-c52c-3178-cffbefe9727a
Version Independent ID: 31967bb3-2635-da97-782c-641f432750f7
Content: Configure Burndown & Burnup widgets - Azure DevOps
Content Source: docs/report/dashboards/configure-burndown-burnup-widgets.md
Product: devops
Technology: devops-analytics
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@EQDGL - Thank you for your comment. If you make sure your content version selector is set to Azure DevOps Server 2019, you'll see the following item is added to the Prerequisites section:

Have enabled or installed Analytics. You must be an account owner or a member of the Project Collection Administrator group to add extensions or enable the service.

You are correct that all Analytics widgets are available only after Analytics is installed or enabled.


Panel and sidebar sizes are not persisted

Close sidebar/panel
Reload window
Open panel/sidebar
They are very small

fixed by https://github.com/microsoft/vscode/issues/77884


Fix typos in "Modifying Resources" doc page

Thank you so much for these PRs! I’m traveling for the holidays but I’ll be able to review these soon.


Update Add-a-Virtual-Gateway-to-a-Tenant-Virtual-Network.md

Updated the example. It was incomplete earlier

Thanks, Anirban! Merging now.


Support mount options for storage mount

We just hit this problem. It's been in-progress for the last 15 months - any sort of ETA on this?

@chriswue mountOptions are available in apiVersion >= 2024-03-01 (https://learn.microsoft.com/en-us/rest/api/containerapps/container-apps/create-or-update?view=rest-containerapps-2024-03-01&tabs=HTTP#volume).
They are also available in the UI when editing a container

Ok thanks, is this also being worked on for NFS shares?

This is feature is now in GA. Currently NFS shares are not supported to use mount options.


$locationProvider.html5Mode(true) is broken

Somehow need to convince browserSync that all requests are for index.html?

https://github.com/BrowserSync/browser-sync/issues/204
seems that adding the connect-history-api-fallback module fixes this.

AH!  Yes!


Queue auction stage events in delegate server after a new auction is set

@MangoIV

This has quite some overlap with my PR eyes How do we manage that issue?

You can just rebase on that PR and make your PR stacked on that one, no?

You can just rebase your PR on that PR and make your PR stacked on that one, no?

I have got more commits and more significant changes to the Main logic. Wouldn't it be better to do it vice Versa?

@MangoIV

I have got more commits and more significant changes to the Main logic. Wouldn't it be better to do it vice Versa?

This PR is nearly finished. And actually I missed that @nazrhom already answered my concerns, and probably gonna merge it now.
Your PR marked as draft so I did not checked last version.


Make all LDAP tests pass

[ ] Setting up an environment where LDAP tests can be executed
[ ] Make all LDAP tests pass

At least, i did not need this feature, so i close this issue.


fix env var typo in curl command

I think the original ${ENV_VARIABLE} interpolation is correct and the proposed change in this Merge Request is not needed (and not even correct).

Well, regardless, the original format doesn't work for me and the proposed change does. I don't think there's anything special/unique about my setup. Also looking at the open issues I'm not the only one who experienced the issue either.

the way it is written is correct, this PR technically incorrect; what you are changing this to is technically brace expansion. Environment variables on there own are typically just $FOO but when inserted into a string its better to wrap with curly brackets to distinguish the exact variable name like ${FOO}BAR

I've tested this in the update on master and based on my results I'm keeping the original syntax in use.


Add support for openpgp

If I create a new encrypted file from the command line (micro test.asc) it asks for a password but then thinks that the password was incorrect (because the file didn't exist before) and the file just shows No name and test.asc: EOF. I also think that the password shouldn't be displayed when typing it in. You can use terminal.ReadPassword (from golang.org/x/crypto/ssh/terminal which this already depends on) to read a command line password without displaying it.
I think this needs some more work before it can be merged but I think this is a great addition to the editor. Thanks for taking the time to contribute!

I will fix things and make improvements.
The purpose of this pull request is to support PGP files encrypted with a
single password. The editor will be able to create a password encrypted
file or open/edit an existing password encrypted file. A file is assumed to
be encrypted if the file extension is gpg (binary format) or asc (text
format). If the user doesn't want to encrypt/decrypt a file then they won't
enter a password, and the file will be saved as is.
I should probably add support for looking at "magic" bytes to determine if
a file is a pgp/gpg encrypted file, so files with other extension can be
supported.
On Tue, Jul 18, 2017 at 12:13 PM, Zachary Yedidia<EMAIL_ADDRESS>wrote:

If I create a new encrypted file from the command line (micro test.asc)
it asks for a password but then thinks that the password was incorrect
(because the file didn't exist before) and the file just shows No name
and test.asc: EOF. I also think that the password shouldn't be displayed
when typing it in. You can use terminal.ReadPassword (from
golang.org/x/crypto/ssh/terminal which this already depends on) to read a
command line password without displaying it.
I think this needs some more work before it can be merged but I think this
is a great addition to the editor. Thanks for taking the time to contribute!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zyedidia/micro/pull/730#issuecomment-316149483, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAPZFP6r4bxPe9hG92tKLCcNGr5Prc78ks5sPPW7gaJpZM4OTtaY
.

Sorry I've just been idling with this issue. I'll try to test it and hopefully merge it soon.

Am I correct in my understanding that a file can only be encrypted if it has the extension .asc or .gpg?

Correct. Only files with .asc or .gpg are encrypted.

Thanks for keeping this up-to-date. I'll try review and merge soon. My only concern is the x/crypto dependency which adds another 55,000 lines of dependency code -- but there isn't much that can be done about it and it really isn't a big deal.

build tag 'phat' is now required for openpgp support; gzip support has also been added @zyedidia

I was just about to start building this feature. I'm presuming this was never merged in? @pointlander do you know if I can resurrect this merge or should I start a new one??

I will fix the conflicts @silverark

https://github.com/pointlander/micro/tree/next

merge completed @silverark

Thank you @pointlander
That's brilliant. Thanks for your hard work

Thanks for updating this! I will try to take a look through it soon.

I don't think micro should support OpenPGP in any way. The general consensus in the security community is that PGP does what it does quite badly:
https://latacora.singles/2019/07/16/the-pgp-problem.html
https://blog.cryptographyengineering.com/2014/08/13/whats-matter-with-pgp/
Adding support for it at this point would not be wise. It might make sense to create a plugin that does this (and change micro where it needs changes for the plugin to work).
If users want OpenPGP support, just use the gpg on files micro produces. It is easy and works with the unix philosophy, e.g. gpg -d encrypted.asc | micro.

How would the user write the file to disk in encrypted form? This feature also adds compression support, and vi encryption format should be supported. Should be using this: https://github.com/awnumar/memguard

With version 2.0.3 you can also pipe the contents of a file edited with micro to another unix tool. I am not familiar with the unix tools used for encryption but presumably one could do something like decompress file.txt | micro | compress > file.txt. In general I'm hesitant to implement features in micro that require heightened security because it's easy to get things wrong and the stakes are much higher.
Are you suggesting using memguard for keeping the file contents that are being edited in-memory by micro in a secure enclave? Correct me if I'm wrong but it doesn't seem like the implementation of this PR currently supports that.

This pull request doesn't have memguard, but it would be a good idea.

And what about multiple files?


Not an editor command: PlugInstall despite Vim-Plug being installed correctly

I have plug.vim file in .vim/autoload and Git and Vim versions are up-to-date. My .vimrc file is this:
call plug#begin('~/.vim/plugged')
  Plug 'mhinz/vim-startify'
call plug#end()

The problem is the usual one: Not an editor command: PlugInstall. I tried uninstalling and reinstalling Vim-Plug but the result was still same.

VIM - Vi IMproved 8.2

Type:

[ ] Bug
[ ] Enhancement
[ ] Feature Request
[x] Question

OS:

[ ] All/Other
[x] Linux
[ ] OS X
[ ] Windows

Vim:

[x] Terminal Vim
[ ] GVim
[ ] Neovim

Solved! Vim was reading a different vimrc file than I was customizing.


Flakey NATS tests

E.g., in this build https://circleci.com/gh/weaveworks/flux/1046
Quite irritating, since it means clicking rebuild all the time.

Fixed by #446 (tom some extent ..)

Also https://circleci.com/gh/weaveworks/flux/1074, though (I believe) we see this variety much less often

Continuing to occur: e.g. https://circleci.com/gh/weaveworks/flux/1344

There is no longer any NATS in this repo.


Store public attestation gist url on Firestore

gists are published on user's github, people should be able to reshare of something goes wrong so we should save a copy of it on our side

Steps

[ ] Update the participant's document collection with the gistUrl parameter.
[ ] Show gistUrl + preconfigured tweet url when the participant runs the contribute command again after completing all contributions or have decided to stop contributing.

Corner cases

[ ] If the participant stops before the gist is published, we could regenerate it if

[ ] gistUrl is empty
[ ] the participant has the public attestation locally
[ ] the participant has not removed the gist permissions for the CLI.

[ ] Otherwise, we cannot reproduce the public attestation


active item index?

is there a way to get the index of the currently active window? This is especially important on touch scrolling.

Great Thanks. This was very useful and I could do what I wanted to do.


Using Prefix: Friendly Name & Entity ID don't match

In HassWS, I set a prefix of "desktop_". Entity_IDs show correctly but the friendly name has a hyphen (-) between the prefix and the sensor name.
For example, in Home Assistant I see:
Name = desktop_-CPULoad
Entity ID = sensor.desktop_cpuload

This should be an easy fix. I will take a look.

It's because of this issue. Hass.io does not support - characters in entity names.

It's because of this issue. Hass.io does not support - characters in entity names.

That's the problem. The hyphen isn't supposed to be there. HassWS is setting the friendly name to include the hyphen.
In my example posted above, the prefix was set as "desktop_" (which after some experimentation "desktop" would accomplish the same since it looks like HassWS appends an underscore automatically if there isn't one).
The information from the link is talking about the Entity ID's name, not the friendly name. Entity IDs can only have lowercase letters, numbers, and underscores. The friendly name is more flexible and can include spaces.
Even hovering over the What's This? shows the name with a hyphen and entity ID with an underscore. They don't match. In theory, the name could simply replace the hyphen with a space.

can you please confirm that you are expecting the attributes to be :
entity Name : desktop ActiveWindowSensor
entity ID : sensor.desktop_activewindow

correct. bonus points if you can make the first letter of the entity name capitalized.
entity Name : Desktop ActiveWindowSensor
entity ID : sensor.desktop_activewindowsensor


Cant get it to work - error in skills

No matter how I try I dont get this working.
Snips seems to work - installed on RPI3 whith apt-get.
The fake weather or the OWM seems not working...But maybe it is not the skills but the snipsmanager?


Set default Firefox prefs

https://github.com/kblok/puppeteer/pull/20/commits/35d5ba5830402af16070cafdc071c1970875a0d9

can I work on this one?

@fgiuliani  Sure!


Optional positional args and the need for unit

https://rescript-lang.org/docs/manual/latest/function#optional-labeled-arguments
There are a couple of things about optional args that are not coder-friendly:

Positional args cannot be optional (even if there is just one arg)
The need for "unit" param/arg as a final positional arg even when all args are labelled

Is there no way to make this a nicer experience? Mixing positional and labelled args in general seems a slightly odd allowance, but particularly so if it is causing this "unit" oddness. A necomer to the language (e.g. me a couple of weeks ago) is not going to understand why this is necessary:

Note for the sake of the type system, whenever you have an optional argument, you need to ensure that there's also at least one positional argument (aka non-labeled, non-optional argument) after it. If there's none, provide a dummy unit (aka ()) argument.

The need for "a dummy unit argument" is precisely the kind of quirk that could turn people away from this language. We come here in search of something better than typescript, so if this is going to remain in the language, I think we deserve a more detailed explanation than "for the sake of the type system". What is the trade-off here, what are we gaining in exchange for needing to use the dummy unit arg?

I would label this a Question, but no labels are available ;)

This can be explored in the context of uncurried types, where the number of arguments is fixed. So if an optional argument is omitted, the intention is clear.
With curried types, the intention is ambiguous, maybe the intention is to provide that extra argument later. In general, even a simpler example is confusing, one with only say 3 mandatory labelled arguments (~x, ~y, ~z) => x+y+z. If you only supply z, that is interpreted as partial application, returning a function that still expects x and y. This is going to surprise a number of users who simply forgot to pass extra mandatory arguments.
With uncurried types, passing only z is an error.
Uncurried types by default are explored in compiler v11, under development.

See here https://github.com/rescript-lang/rescript-compiler/pull/5907


Having problems with named params in annotations

Hi!
I am trying to extract the value of a named parameter this way but I don't know if I am doing it right or this is not supported yet. Using scala.meta 1.1.0 and macro paradise 3.0.0-M5
@namedParam(some = "text")
class SomeClass

final class namedParam(some: String) extends scala.annotation.StaticAnnotation {
  inline def apply(defn: Any): Any = meta {
    val q"new $_(some = $string)" = this
    defn
  }
}

The above code doesn't compile, throws the following error
Error:scalac: Error: unsupported tree AssignOrNamedArg(Ident(TermName("some")), Literal(Constant("text")))
(AssignOrNamedArg) some = "text"
(Apply) namedParam(some = "text")
(Template) Template(List(), List(namedParam(some = "text")), val _ = _, None)
(Apply) new namedParam(some = "text")
org.scalameta.paradise.converters.ConvertException: unsupported tree AssignOrNamedArg(Ident(TermName("some")), Literal(Constant("text")))
(AssignOrNamedArg) some = "text"
(Apply) namedParam(some = "text")
(Template) Template(List(), List(namedParam(some = "text")), val _ = _, None)
(Apply) new namedParam(some = "text")

Am I doing something wrong? Thanks in advance!

Hi Quaiks!
Looks like this is one of missing parts in scala_reflect - scala_meta trees converter. I'll add this functionality soon.

That was quick! Thanks @Dveim. I am looking forward to it!

See https://github.com/scalameta/paradise/pull/36 .

Nice!

Should be fixed in 3.0.0-SNAPSHOT.


procedural_function not allowing body

Hi Matthew.
First, thanks for the great work. I'm implementing pss DSL 2.0 via ANTLR4 with a project, and I ran into an issue with target functions while using this grammar.
I looked in the grammar files and found the FIXME tag, and noticed that procedural_stmt was commented out between the braces. I also noticed that the vscode extension you have does not have the same issue, though I see the grammar files are older.
I was hoping you might be able to provide some detail as to what was going on there and why that line needed to be commented out.
Any other knowledge you might have on other non-working parts would be most appreciated as well, if anything comes to mind.
Thank you again!

这是来自QQ邮箱的自动回复邮件。
您好，您的邮件我已收到，我会尽快查收并回复。

Hi Ron,
Thanks for reaching out on this. The official PSS grammar focuses on readability/understandability over being able to be implemented efficiently. I think there was sufficient ambiguity around procedural_function body that even ANTLR4 choked.
Looks like this is one of the ambiguities I didn't get resolved in this version of the parser As far as I can tell, I corrected the ambiguity in my 'other' version of the grammar (it's a PSS+ grammar, so not directly applicable). Let me investigate and get this version of the grammar updated.
Thanks again for raising this!

Thanks, Michael!
I greatly appreciate it. I'm a bit new to PSS grammar, so I'm still learning all of the various edges. Your libraries have been a tremendous help in getting up to speed more quickly.
I'll keep an eye out for your changes!

Hi Ron,
Have a look at the latest commit d042e76. I've rolled in disambiguation fixes that enable ANTLR to work well. Let me know if you run into further issues!

Looks good. Thanks again, Matthew!


Test resources not copied to output folder in some cases

In some cases, not all test resources are copied to the build/resources/test folder.
See this SO question: https://stackoverflow.com/questions/73934745/gradle-not-copying-all-test-resources-to-output-dir
Expected Behavior
When I run the test or processTestResources task, all test resources should be copied to the output folder.
Current Behavior
Only a subset of files are copied: resources under foo/ are copied; resources under hello/ are not copied.
The problem is gone if I remove this line. Please refer to the linked SO question for the details.
Context
This is just a simplified tests case; in the original project, test resources are not being copied to the output folder and this makes unit tests fail.
Steps to Reproduce
https://github.com/guillerodriguez/gradle-test-resources-issue
Your Environment
Issue can be reproduced with GH actions; see linked project.

Sorry, wrong repo URL. Fixed.

Could you try changing the offending line to:
    from(processTestResources) { include 'foo/' }

The rationale is that from processTestResources { include 'foo/' } configures the processTestResources tasks instead.

Could you try changing the offending line to:
    from(processTestResources) { include 'foo/' }

The rationale is that from processTestResources { include 'foo/' } configures the processTestResources tasks instead.

Yes, that fixes the issue. I had already noticed this by (blindly) playing around, but didn't understand why it worked (actually I still don't understand -- why do the parentheses make a difference?)
Also, is this documented anywhere? In the documentation for the copy task, section "File copying in depth" explains how a task argument can be passed to from, and shows some examples that do not include parentheses (see example 33). Then the section about "Filtering files" which talks about include and exclude does not mention any of this either.

I believe this is related to Groovy precedence when resolving the expression.
Without the parenthesis, Groovy interprets everything after from as the argument.
And so it fetches the reference to the processTestResources task, applies the configuration closure to it, and then passes the result to from.
So the end result is that you configured in-line the processTestResources instead of configuring the from.
Adding the parenthesis changes the meaning by clearly indicating that the result of calling from with a task is what is to be configured.
Closing the issue as this is more a Groovy specific thing that a Gradle issue, although I agree it is confusing when you encounter it.

OK, thank you for the clarification.
Perhaps the documentation for the copy task could mention this pitfall and/or include some examples.


Can’t ignore a directory

Wanted to do something like this:
rev:
  dist:
    files:
      src: [
        "!<%= yeoman.dist %>/images/norev/*"
        "<%= yeoman.dist %>/images/**/*.{png,jpg,jpeg,gif,webp}"
      ]

But it doesn’t seem to be working. I want rev to ignore everything in the norev directory. I want to ignore those files because usemin fails when trying to process a javascript file optimised by r.js that contains HTML underscore templates in it.

:+1:

:+1:

:+1:

:+1:

:+1: Thanks!


Update README.md

The zabbix_server_database_creation variable doesn't exist. This needs to be zabbix_database_creation.
Description of PR
Documentation correction.
Type of change
Docs Pull Request

Thanks! 👍

I also noticed that zabbix_server_database_sqlload should be zabbix_database_sqlload. There may be others. When I have more time I see if I can create a PR with all the documentation fixes.

Hi @mklvr Ok, thanks! I was just thinking if this name shouldn't conflict with the zabbix-proxy role. As both have the possibility to not load the sqlfiles. Both have the zabbix_database_creation property, I'm not sure if this would be ok.
Do you by chance have also a proxy running (and if so, configured with the Ansible role) and do you want to be able to have 1 property or 2, 1 for the server and 1 for the proxy?

I'm not currently using the proxy role, but perhaps it would be better to leave the prefix for these variables as zabbix_server_* and then just make sure the role actually checks those variables.
However, if the variables were to overlap between the server and playbook roles it wouldn't be that big of a deal, I imagine, since different values can be specified at the playbook level.


Problem with images frames - From Storyboard + Constraints

The Frames UIImages are not fit the frame of the Banner when I use Constraints into my storyboard.

Sorry，It doesn't support Auto Layout, next I will support it


Implemented new IViewModelExtension AttachOrReplaceChild

GitHub Issue: #

Proposed Changes

Feature

What is the current behavior?
Currently, when we try to attach again a child (with the same name) on a parent ViewModel, it will throws an exception.
What is the new behavior?
Now, if you use the extension method AttachOrReplaceChild, it will detach the previous instance (and disposed it) and attach the new instance to the parent ViewModel.
Checklist
Please check if your PR fulfills the following requirements:

[ ] Documentation has been added/updated
[x] Automated Unit / Integration tests for the changes have been added/updated
[x] Contains NO breaking changes
[ ] Updated the Changelog
[ ] Associated with an issue

Other information

@takla21 @Iguins @jeanplevesque  would it be preferable to change the Attach to allow replace automatically? In other words, why is it important to have a different method to "orReplace" ?

@MatFillion That's the same question @vincentcastagna and I were wondering as well. At the time, we wanted to use this fix without interfering with anything else, so that's why I've moved it into another method.


Radio button view does not reflect model changes within Angular

Hi,
I am using V. 1.0.6 of MDL and no-matter what I try, I cannot get the radio button of type mdl-js-radio reflect model changes. When I remove the mdl-js-radio attribute, thus keeping only mdl-radio class in the surrounding label, it works 2-way.
With mdl-js-radio it is only 1-way i.e. clicking the radio buttons is reflected in view and model, but model changes from a location watch don't get visualized.
With a text input everything works fine, too. It's just the radio buttons.
On load and initialization of the page button view is reflected properly. Later updates from the location watch (triggered e.g. by using the Back button in the browser) don't get visible.
Any idea?
Cheers
Pascal

The same is happening in KnockoutJS.

The GitHub issue tracker is for issues, bugs and feature requests with MDL. MDL is targeted at static content sites and integration with any kind of framework is not a first-class use case for us. But, if you need help with these kind of things, please head over to StackOverflow and use the material-design-lite tag. From what I know, similar things have been covered a few times on there and there’s people who do know how to make it work :)

I've now successfully used the bootstrap radio buttons.


Document agent and proxy options

agent option was added by #102
proxy option was added by #133

Maybe you should take a look to https://github.com/mzabriskie/axios/issues/370 before documenting the agent option publicly.

httpAgent and httpsAgent are already documented ;)

Yeah. #366 documents the proxy option but it has not been merged yet (waiting for the author to fix an issue).


Make coverage reports easily accessible to developers

As a Plutus Core developer I want to have easy access to coverage reports so I know if I need to improve the coverage on a PR.
Acceptance criteria

Coverage reports for a PR can easily be accessed by the developer making the PR.

Coverage reports can easily be generated by developers locally.

I doubt this is ever going to happen, but if anybody disagrees do feel free to reopen.


Title line breaking

Title should look like as a single line without line breaks. Currently, you can make a line break, and it won't be fixed next.

Fixed in 3.1.0.


update graphql-java-kickstart implementation with latest schema changes

Update to expected schema that verifies @requires directive functionality.
Changes:

add missing User entity type resolver
correct ProductDimension.unit return value
add averageProductsCreatedPerYear: Int @requires(fields: "yearsOfEmployment") on User type
add new yearsOfEmployment: Int! @external field on User type`

NOTE: @link test is still failing as graphql-java-tools currently does not support schema directives
Related Issues:

https://github.com/apollographql/apollo-federation-subgraph-compatibility/issues/128

LibraryFederation 1 SupportFederation 2 Support

GraphQL Java Kickstart (Spring Boot)_service🟩@key (single)🟩@key (multi)🟩@key (composite)🟩@requires🟩@provides🟩@ftv1🟩@link🟥@shareable🟩@tag🟩@override🟩@inaccessible🟩


Example broken

Hi, this example on the front page is not working for me:
//Update
var notify = $.notify('Saving Do not close this page...', { allow_dismiss: false });
notify.update({ type: 'success', 'Success Your page has been saved!' });
Error:
Uncaught SyntaxError: Unexpected token }

Yeah
{ type: 'success', 'Success Your page has been saved!' }
Should probably be something like:
{ type: 'success', message: 'Success Your page has been saved!' }
Javascript won't understand how a json can have one element with a key and the other one without a key.
I would suggest try that, and see.

Whoops, I am terrible at typing. lol


Spelling

What this PR does / why we need it:
This PR corrects misspellings identified by the check-spelling action.
The misspellings have been reported at https://github.com/jsoref/cert-manager/commit/bca1c47eeb1b7436891479def2835dfb3fa78ef0#commitcomment-47820545
The action reports that the changes in this PR would make it happy: https://github.com/jsoref/cert-manager/commit/3aed6e91b3b9690584ebdefad6b06ad26fa44ec1
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Previous round #2624
Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.
The CRD changes would probably trigger a bump to a chart.
The changes to UsageContentCommittment probably can't be made at all, as they're probably API breaks. If that's correct, let me know and I can trivially drop them.
This is an example of where having an action that runs on PRs could catch things and prevent poor APIs from sneaking in.
@maelvls
Release note:

/assign @jakexks

/ok-to-test

/assign @jsoref

We will discuss the possible move to a "US normalized" spelling across the codebase tomorrow during the daily standup 10:00 UTC!

No idea what this is, it doesn't seem related to me:

--- FAIL: TestCtlRenew (73.98s)
testwebhook.go:110: Waiting for ListenPort to be allocated (got error: Run() must be called before Port())
apiserver.go:60: Found CRD with name “certificaterequests.cert-manager.io”
apiserver.go:60: Found CRD with name “certificates.cert-manager.io”
apiserver.go:60: Found CRD with name “challenges.acme.cert-manager.io”
apiserver.go:60: Found CRD with name “clusterissuers.cert-manager.io”
apiserver.go:60: Found CRD with name “issuers.cert-manager.io”
apiserver.go:60: Found CRD with name “orders.acme.cert-manager.io”
--- FAIL: TestCtlRenew/--all_and_--all-namespaces_given (2.86s)
ctl_renew_test.go:176: failed to trigger issuance of Certificate testns-2/testcrt-4: Put “http://<IP_ADDRESS>:32947/apis/cert-manager.io/v1/namespaces/testns-2/certificates/testcrt-4/status”: context deadline exceeded
FAIL
73/74 Tests Passed!
expand_more

(help?)

/retest

/lgtm

/retest


Set expanded/collapsed value of each legend row

Added collapsed property in layerConfig legend object to manage the collapsed state of the layer's legend.
const layerConfig = {
  title: 'Store types',
  visible: true,
  showOpacityControl: true,
  opacity: 0.4,
  legend: {
    attr: 'storetype',
    collapsed: true, // false by default
    type: LEGEND_TYPES.CATEGORY,
    labels: DATA.map((data) => data.label),
    colors: DATA.map((data) => data.color),
  },
};

By this way, you can stay informed about what is the state of the legend and indicate the initial value.
Test added for this feature.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 70.467%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
1222

Relevant Lines:
1634

💛  - Coveralls


*: rewrite coreos-metadata in rust

we've been reviewing it as we go and did a review of the project as a whole as well.

Hi there! I wonder, what was the purpose of the rewrite?

@burdiyan It was a technical one. In order to support fetching SSH keys from Azure, we needed crypto primitives that weren't available in Go (namely CMS). The added benefit of going to Rust is a smaller binary, smaller memory footprint, and less bugs, just to name a few.

Thanks! Good to know.
El 3 nov 2017 1:21 +0100, Alex Crawford<EMAIL_ADDRESS>escribió:

@burdiyan It was a technical one. In order to support fetching SSH keys from Azure, we needed crypto primitives that weren't available in Go (namely CMS). The added benefit of going to Rust is a smaller binary, smaller memory footprint, and less bugs, just to name a few.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


[v7-alpha.21] Pagination does not work with grouping

First of all, thank you so much for your work - it is awesome!
Bug description
I noticed a bug when trying to use useGroupBy, useExpanded and usePagination hooks: as soon as the grouping is activated (either manually by the user, or programmatically, using default table state), the component runs into an infinite re-rendering cycle. Meaning that it starts re-rendering every several milliseconds without any reason. Also, pagination stops working.
To reproduce
To reproduce it, I slightly modified your original example of grouping:

Go to https://codesandbox.io/s/tannerlinsleyreact-table-grouping-zrmbi
Open the console: you'll see there's only one "rendering..." message logged from the component, which is as expected
Now click on any column to group by it
You'll notice infinitely many "rendering..." messages appearing in the console
Try clicking on "next page" button: pagination doesn't work
If you disable grouping of that column, everything works fine again
If you remove usePagination hook and adjust the component to use rows instance property instead of page, grouping works fine without infinite re-rendering

Expected behavior
Obviously, no infinite rendering and working pagination.
Additional context
I also noticed that nestExpandedRows table option doesn't have any effect. Either it is true or false, when you expand the last row in the grouped table, nested values are paginated and thus are not displayed. Maybe it's a separate bug, or maybe it's related.
I could live with this issue by simply disabling pagination when using grouping. But in my own code, I use a common Table component where I need to provide both functionalities for the outer components. And it seems there is no way to disable pagination with table options, is there? As a side note, it would be nice to have such an option

When you render rows you can do something like (paginationEnabled ? page : rows).map(renderRow); to disable pagination. You'll still have page in the instance state but you can just ignore it.

@paolostyle , this doesn't help because infinite rendering bug is still present even when I use rows and ignore page property. It's a big performance issue, the table works very slow.
Right now I solved it by disabling pagination in an ugly way:
const { goupBy } = props;
const tableInstance = useTable(
  { ... },
  useGroupBy,
  useEpanded,
  !groupBy ? usePagination : undefined // disable pagination if grouping is enabled
);

I know it's against "the rules" to put a hook behind a condition, but as long as goupBy property is constant for a given instance of a component, the number of hooks executed for every component instance is constant and it works just fine. So it helps me avoid performance issues by disabling pagination when using grouping, but I still hope there will be a better solution soon :)

Pagination also does not appear to work with sorting:
Example: https://codesandbox.io/s/tannerlinsleyreact-table-pagination-0qo8w
Open the console after sorting a column and there will be an infinite rendering loop. Let me know if I should open a separate issue for this, although it seems related.

@zbluhm , I see somebody already opened this issue, 11 minutes ago:
https://github.com/tannerlinsley/react-table/issues/1445

any update on this? I am struggling with sorting and pagination

It'll be fixed soon. Hang tight.

FYI, this is working on a local copy I am working on. Will ship very soon.

This should be fixed. See https://github.com/tannerlinsley/react-table/tree/master/examples/kitchen-sink for an example.

Awesome, thank you @tannerlinsley !


YouTube Movie Trailer

This adds the ability to also include youtube trailer videos with movie selection.  If the current selected movie has an associated youtube trailer it will be displayed on the front page, else it won't be.  Users can also preview their trailer by clicking the 'YouTube' link next to the movie in the list.  Also includes a button to open a new tab to YouTube search with the movie title pre-populated in the search.
A few screen grabs:

There's a few very minor things that I'll probably cleanup at some point, but overall this looks pretty good. I don't think the youtube vid on the dashboard will work though. Did you test it? I added you as an admin user so you should be able to Host a Meeting and try it out.

Yay!!! I'm not in love with the overlay view - is it ok to ditch that and just watch the movie on the page?
:heart_eyes:

But that'a the movie theater experience! :smile:
In all seriousness thought, yeah, I'm fine to change it to whatever.  Maybe display it below the 'Add Movie' button on the left side or something?

The reason I don't think the dashboard part will work is because I fail to save the full movie when selecting a new one, so I don't think dashboardVm.currentMovie.trailerUrl will ever get a value.
Minor things that you can clean up if you'd like:

Use the object syntax in the ng-class directives. I think this just reads cleaner. Example: ng-class="{'display-flex': dashboardVm.currentMovie.trailerUrl}"
I'm not sure it's necessary to check that the url is defined and a non-empty string prior to calling validateYoutubeUrl. Won't the validator handle this?
There seems to be an extraneous Movie attribute in the movie name input tag.
I think if you avoid specifying the protocol in the URLs then the browser will reuse whatever protocol is in use by the current page.
The code in youtubeValidator.validateYoutubeUrl and youtubeValidator.youtubeIdParser is very, very similar. I'd love to see this DRYed up a little. Also, I might rename youtubeValidator since it's doing more than validation (see youtubeIdParser).

Things that I'd eventually change just because I'm OCD (that you can totally ignore):

Break out the new config function in app.js instead of defining it inline and indent the array values.
Add a line break before the watchTrailer function.
This is a JavaScript pattern I see frequently for setting default values on variables that I kind of like: $scope.width = $scope.width || 560;
I'd probably break this template out into an html file.
I'm trying to add tests with all the new stuff I add. I've set a poor example with the initial code, so I would accept this PR without the tests, but you're welcome to add some if you want. :)
Please add your name to the readme under the contributors section too!

Major Fix
You were correct, the trailer was not being saved/retrieved.  Now that I have access as an admin I was able to change it so it saves and gets the trailer URL.
Minor Fixes

Changed ng-Class
Hey man, that Movie attribute was there when I got here
I left it as https:// solely because that's what youtube uses, and since we're opening a blank window I figure why not just use their protocol instead of possibly sending users to http://youtube and having it redirect to https://
After reading your message and thinking about how it works I rewrote that service so it's only one method since returning the youtube ID is the same as returning true (as far a conditional is concerned)

OCD Fixes

I think I meant to do that as I tested what exactly needed to be white listed on the configuration but kept pushing it off and forgot about it
Space added before the watchTrailer function
Removed the ternary style for setting default height and width -- I like the suggested style much more!

TODO

Move the youtube template into it's own HTML file
Add unit tests

I'll take a closer look this evening, but after a quick glance I think this is totally mergable. You, or I, or someone else can submit follow on PRs for the remaining TODO items. Excellent work @BrandonCKrueger!

I'm merging this to master, which will publish to the dev site (prepend 'dev.' to the prod site host). I'll play with it a little there and if all looks good, I'll promote to PROD after a bit.

Welcome to the cool nerd kids club @BrandonCKrueger :)


[Issue 81] 2 PCA implementations that give same results but different from Python scikit-learn implementation

In relation to the first of our action points (to find another example as an acceptance test for our PCA objects), I used the worked example from the PCA Tutorial By Lindsay Smith. As input, I used the mean centred data and what I was able to find is that our output from PolyMath match the output computed in the above-mentioned source.
PCA Tutorial Paper's Output:

x
y

-.827970186
-.175115307

1.77758033
.142857227

-.992197494
.384374989

-.274210416
.130417207

-1.67580142
-.209498461

-.912949103
.175282444

.0991094375
-.349824698

1.14457216
.0464172582

.438046137
.0177646297

1.22382056
-.162675287

PolyMath:
SVD-Based Implementation of PCA:

Jacobi-Based Implementation of PCA

The chief conclusion we can draw is that our data are correct up to the negated signs.
Scikit-Learn
Scikit Learn matches the output of the paper exactly:
[[-0.82797019 -0.17511531]
 [ 1.77758033  0.14285723]
 [-0.99219749  0.38437499]
 [-0.27421042  0.13041721]
 [-1.67580142 -0.20949846]
 [-0.9129491   0.17528244]
 [ 0.09910944 -0.3498247 ]
 [ 1.14457216  0.04641726]
 [ 0.43804614  0.01776463]
 [ 1.22382056 -0.16267529]]

The gist for the python code that generated the above may be found here.
This PR simply adds acceptance tests for the PCA objects' transform: message, using the worked example of the above-mentioned paper.

with Mathematica:
PrincipalComponents[
 N[{{-0.827970186, -0.175115307}, {1.77758033,
    0.142857227}, {-0.992197494, 0.384374989}, {-0.274210416,
    0.130417207}, {-1.67580142, -0.209498461}, {-0.912949103,
    0.175282444}, {0.0991094375, -0.349824698}, {1.14457216,
    0.0464172582},
   {0.438046137, 0.0177646297},
   {1.22382056, -0.162675287}}]]

{{0.82797,
  0.175115}, {-1.77758, -0.142857}, {0.992197, -0.384375}, {0.27421, \
-0.130417}, {1.6758, 0.209498}, {0.912949, -0.175282}, {-0.0991094,
  0.349825}, {-1.14457, -0.0464173}, {-0.438046, -0.0177646}, \
{-1.22382, 0.162675}}


Fix deploy prod

lgtm, can you remove the few console.log's in the PR?

we need those for some troubleshooting in prod at the moment


add dash in aggregated ranks

Let's add a dash in between the start and end rank (e.g., 51-84').

No, the dash should be shown in between the two numbers.


Error: Head "http://<IP_ADDRESS>:11434/": dial tcp <IP_ADDRESS>:11434: connectex: No connections could be made because the target machine actively refused them.

What is the issue?
Good morning, does anyone know what this problem is?
I have already installed and downloaded the model correctly. I'm using phi3, but when running I get this error. I tried running other models and the error is the same. Did the service go down by any chance?

OS
Windows
GPU
AMD
CPU
Intel
Ollama version
0.1.41

Are you still experiencing this?  If so, can you upgrade?  If that doesn't clear it up, can you share the server log?
https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md


155 top up on send screen

Noticed one thing:

send button is disabled if 0. I guess we can remove that condition now if action: topup is set


Feature question: Boilerplate for enum traits

I work with Rails and encounter models with enum fields.
class Task
  enum status: {queued: 0, started: 1, finished: 2}
end

Then in factory I define traits for these statuses in a programmatic way
FactoryGirl.define do
  factory :task, class: 'Task' do
    Task.statuses.each do |k, _|
      trait(k) { status: k }
    end
  end
end

This allows me to do build_stubbed(:task, :finished).
I want to simplify this process to be able to write
FactoryGirl.define do
  factory :task, class: 'Task' do
    define_enum_traits_for(:status)
  end
end

How would I go about defining a define_enum_traits_for method that is accessible in FactoryGirl.define block in all factory files of a project?
I had a look at https://github.com/thoughtbot/factory_girl/issues/564 but that does not seem quite what I'm after.

@lancejjohnson and I took a first pass at this in https://github.com/thoughtbot/factory_bot/commit/03e9a87773465e20f2276bbf9677a0c5d1e63035, and I think it is definitely doable. @seanpdoyle and I had also discussed maybe defining these automatically by looking at the object's defined_enums.

This'd be great!

it would be nice to be able to use it without the enum field type, e.g. with a provided set of values (so it would work with :string or even other column types): traits_for_enum :status, %w[enabled locked whatever]

I just ran into this problem again, I think?
So I have a GamePurchase model with an enum that can be used to show whether you've completed a game, like this:
enum completion_status: {
  unplayed: 0,
  in_progress: 1,
  dropped: 2,
  completed: 3,
  fully_completed: 4,
  not_applicable: 5
}

And then I made a factory with a trait like so, to test randomized values when running the test suite:
# spec/factories/game_purchases.rb
trait :completion_status do
  completion_status { rand(0..5) }
end

The problem is that, when I went to add a new option to the enum I forgot to update this trait, so the new option wasn't ever being used in the test suite.
Solving this issue wouldn't really solve my problem, but I'm wondering if there's a better option here, or if there's a way to solve both these problems at once? Sorry if this isn't the right place to ask this 🙇

@composerinteralia what is the status on this? would you accept a pr onto your branch adding the modifications i proposed?

@eLod I haven't had time to work on this recently, and I am unlikely to have time in the next few weeks.
I have mixed feelings about opening this field up to accept a set of values, but it had crossed my mind. Seeing some code would definitely help make a decision. I don't have a could sense of how much complexity that would add. I could also imagine somebody wanting to pass a hash: traits_for_enum :status, { enabled: 0, locked: 1, whatever: 2 }.
I also still like the idea of defining these traits automatically for any Rails models with traits.

@composerinteralia my main use case is generally status columns with string values, sometimes even with a dedicated table to hold the enumeration values (so it is easy to add/remove values via an admin interface without code modification). sometimes i don't control the database schema. because of these i don't really use Rails' enum field myself (it only supports integer values in the database), but i would benefit from the boilerplate (not needing to write all the traits for all the different enumeration values).
i don't have a problem supporting any enumerable (arrays and hashes) values passed and have some time to work on it if you agree. i can definitely look into defining these traits automatically for models with enums (i guess you've meant that). my concern is rather i would only work on this if there is willingness to accept the feature in the end, it's not clear to me if the idea itself has support (i mean the enum traits, not the modifications i proposed specifically).

@eLod that makes sense to me. I definitely plan to get this feature in eventually, and would appreciate your help on it if you are willing.

@composerinteralia sure, i don't have time on the weekend but i can look into it next week, will look around and comply my thoughts about how to go with the implementation and get back to yo. if you have anything else in mind not covered in this issue yet please add. thanks.

@composerinteralia pushed an initial version, opened a pr, left some comments

@klyonrad oh yes, i haven't realised it, that said the docs specifically mention it is designed for integers (so the implementation can change). anyways i feel using the helper for associations (e.g. where the enum comes from another table) is still a valid use-case.

Will this be picked up for reviewing/merging in this year? Is there anything that blocks it?

I do plan to get this feature merged in. The only thing blocking it is a lack of time to review. I will try my best to take a look this month.


Fix: cache client problem

With multi-client  config, cache setting was not individual but inherit from the last client setting.
This fix #9  resolve this issue by dynamically build the proxy handler required by guzzle.

:+1: except some comments to add

:+1:


Integration tests

We should look at creating, as a first step, integration tests.
These should be adapted from the benchmarks repo.
Possibly as a set of Fortran programs run via a shell script?

Closing as duplicate of #115.


Executing VACUUM with PostgresOperator

Dear Airflow Maintainers,
Environment

Airflow version: v1.7.0
Airflow components: PostgresOperator
Python Version: Python 3.5.1
Operating System: 15.4.0 Darwin

Description of Issue
I am trying to execute a VACUUM command as part of DAG with the PostgresOperator, which fails with the following error:
[2016-05-14 16:14:01,849] {__init__.py:36} INFO - Using executor SequentialExecutor
Traceback (most recent call last):
  File "/usr/local/bin/airflow", line 15, in <module>
    args.func(args)
  File "/usr/local/Cellar/python3/3.5.1/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/airflow/bin/cli.py", line 203, in run
    pool=args.pool,
  File "/usr/local/Cellar/python3/3.5.1/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/airflow/models.py", line 1067, in run
    result = task_copy.execute(context=context)
  File "/usr/local/lib/python3.5/site-packages/airflow/operators/postgres_operator.py", line 39, in execute
    self.hook.run(self.sql, self.autocommit, parameters=self.parameters)
  File "/usr/local/Cellar/python3/3.5.1/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/airflow/hooks/dbapi_hook.py", line 109, in run
    cur.execute(s)
psycopg2.InternalError: VACUUM cannot run inside a transaction block

I could create a small python script that performs the operation, as explained in this stackoverflow entry. However, I would like to know first if the VACUUM command should be supported by the PostgresOperator.
Reproducing the Issue
The operator can be declared as follows:
conn = ('postgres_default')
t4 = PostgresOperator(
    task_id='vacuum',
    postgres_conn_id=conn,
    sql=("VACUUM public.table"),
    dag=dag
    )

Using autocommit=True should solve the issue

@slvwolf That's correct... and good catch.
@rrbarbosa If you haven't already, please create a JIRA for this -- we don't use Github Issues anymore .. refer to https://github.com/apache/incubator-airflow/issues/1445
Once you create the JIRA, you can ping me (to write a fix for this) or either you or @slvwolf can submit a PR for it.

@r39132 https://issues.apache.org/jira/browse/AIRFLOW-139
I don't see what the PR would look like though. If I understand @slvwolf correctly, I should only add a new argument when creating the operator.


feat(rust)!: add workspace with generated bindings crate

The main goal of this PR is to start making some changes that should help to get #1305 ready for review. I'll update that PR later to be compatible with the changes introduced here.
A summary of the changes:

Add a Cargo workspace for the Rust implementation of ADBC, this allow having separate crates for different components (like drivers).
Add a bindings crate arrow-adbc-sys to the workspace that auto generates bindings based on adbc.h using bindgen when the generate features is enabled. There is a symbolic link to the adbc.h header in the bindings crate. I noticed that the go lib has a copy that is checked to be in sync with pre-commit, if that is preferred I can update. CI checks if the checked-in bindings are in sync with adbc.h header.
Update some existing definitions to use the generated bindings.
Add dependabot config to keep Rust dependencies up-to-date.
Remove usage of non-approved GitHub actions for Rust workflow.
Check in Cargo.lock file following this blog post.
Remove an unused dev dependency.
Fixed some Clippy warnings.
Updated dependencies.
Remove Adbc prefix from item names.
Remove deprecated function from std::error::Error impl, added a Result type.
Added some missing ingest options.

I plan on updating the trait definitions in a follow-up PR to provide both sync and async versions.

This makes the ADBC core traits depend on the bindings right? I think we don't want to do that to allow for pure-Rust drivers.

Closing in favor of #1723.


fix: update hardware wallet flow to better match revamped onboarding

Checklist

[x] JIRA - LW-10122
[ ] Proper tests implemented
[ ] Screenshots added.

Proposed solution

Remove legal and analytics from the timeline steps on hardware wallet flow.
Remove the create loader and all done page from the flow to better match the revamped onboarding design.

Testing
Follow the hardware wallet onboarding flow
Screenshots
Attach screenshots here if implementation involves some UI changes

Changes unknown
when pulling 5f032a751b9dcf7b33425dc541232de6ac85c3fa on fix/lw-10122-hardware-flow-improvements
into ** on feat/lw-9651-revamp-onboarding-develop-branch**.


Inconsistent behaviour when adding buffer() inside concatMap()

First of all my apologies, this might be a stupid user error problem or a real bug - I am new to using Wonka and cannot yet tell which one it is. :)
I am implementing my own bufferCount() operator by concatMap and nested buffer inside. At some point I wondered why the buffers always emit with size of 1 and resorted back to the original buffering example. I suspect there is a bug somewhere or a concept I don't understand, so here is a simplified example - this time with interval timers instead of a counter.
Please help me figure out what am I missing. Alternatively, I would appreciate a bufferCount() implementation as that is my target anyway. :)
Wonka example on buffering works alright:
pipe(
  interval(100),
  buffer(interval(1000))
  // prints [1, 2, 3, 4, 5, 6, 7, 8, 9, 10], [11, 12, ...], etc...
  subscribe(console.log)
)

However, when nested inside concatMap, the arrays emit one item at time
pipe(
  interval(100),
  concatMap(value =>
    pipe(
      fromValue(value),
      buffer(interval(1000))
    )
  ),
  // prints [1], [2], [3] etc...
  subscribe(console.log)
)

Sorry, I must've forgotten to come back to this ✌
In the second code snippet you've applied buffer only to items inside the concatMap (which runs one mapped stream at a time in series). This means that only your fromValue output of one item will be buffered at a time.
I'm not quite sure what bufferCount does but does it just collect a maximum number of items until emitting? Because if so you nay be able to implement it using scan aggregating values into an array and filter

Sorry, I must've forgotten to come back to this ✌
In the second code snippet you've applied buffer only to items inside the concatMap (which runs one mapped stream at a time in series). This means that only your fromValue output of one item will be buffered at a time.
I'm not quite sure what bufferCount does but does it just collect a maximum number of items until emitting? Because if so you nay be able to implement it using scan aggregating values into an array and filter


On MacOS, build.sh installs arithmoi without llvm

Add constraint on cabal install for MacOS to not use LLVM for arithmoi, addressing a known problem:
https://bitbucket.org/dafis/arithmoi/issue/15/fails-to-compile-with-ghc-784-due-to-fllvm
http://stackoverflow.com/questions/24796874/cant-install-diagrams-arithmoi-on-mac

Do you mean -fllvm? -llvm I think is enabled by default already, no? (I might be misreading things...)

cabal install --constraint "arithmoi -llvm" ... is correct.
cabal install 'arithmoi==0.4.*' -f -llvm for installing just arithmoi is also correct.
By the way, just a few seconds ago I finally completed a fully automated install of IHaskell on Mac OS on a fresh machine. It was quite involved (since my normal machines had a lot of state already from fiddling around with things) but I got it working and will verify it by wiping everything and running my script.
Right now I have the setup do various things before finally calling ./build.sh all and ./build.sh display. Should I just submit this wrapper script as a specific mac-build-everything.sh or something like that?

Sounds good. Yes, wrapper script sounds good -- that said, make sure there is good documentation about what the script does (even if just as comments in the script), because as a user, I would be afraid of running such a script, given that it has to do a lot of things (install native libs, etc).


Uncaught TypeError: $ is undefined

Getting uncaught typeError at $.fn.daterangepicker . I am using this plugin in wordpress.  jQuery is loaded correctly before this code.
Any solution?

Resolved this issue. There was a problem with the jQuery version. After upgrading it is working.

Resolved this issue. There was a problem with the jQuery version. After upgrading it is working.

What's the correct version of jQuery? I got this issue too .
thanks bro

@opcodespace

@sunwenli Sorry I cannot remember that. it was less than version 2. I installed jQuery migrate plugin in wp to resolve this issue.


Header Information

How I can see which header worked on test if payload successed ?

For this you have to use -p option and play it in burpsuite


Simplify ObserverToken using a typealias

Simplify ObserverToken using a typealias

Thx for the pull request and sorry for responding so late. I'll close this in favor of #43.


why don't I add my protype moveleft function

I add my protype function moveleft(),But it always has one error Uncaught TypeError: Object # has no method 'moveleft'
Can you help me why and how to solve it?
SvgPanZoom.prototype.getPublicInstance = function() {
var that = this
// Create cache
if (!this.publicInstance) {
this.publicInstance = this.pi = {
, moveLeft: function() {that.moveLeft ();}
SvgPanZoom.prototype.moveLeft = function() {
var viewBox = this.viewport.getViewBox();
var offsetX = (viewBox.x -10) * this.getZoom();
var offsetY = (viewBox.y) * this.getZoom();
this.getPublicInstance().pan({x: offsetX, y: offsetY});
}

thanks  , I sovle it


Keeping version numbers in sync in angular library project package.json files

When building an Angular Library application, is there an automated way to keep the root level package.json and the library application's package.json (e.g. under projects/my-library) file versions in sync when using npm version commands?
When I use the command, its only incrementing the root level package.json, is there a special command, or any other way to propagate the version number down to the library package.json file?
I have seen some solutions such as running a script after ng build to read the root level package.json version number and write that into the library one. Is this a good approach or are there better ways supported with the cli?
Thanks

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.


[ServiceBus] Test and failure improvements

Small but important: does not import ServiceBusSession any more.
A smattering of small test improvements.

ensure incorrect_queue_conn_str test validates success and failure cases and consistency of different entry points.
ensure specificity of authorization/authenication errors
Begin adding "raises" stanzas to docstrings.
normalize convert_connection_string_to_kwargs to throw AuthenticationError on misaligned entity_path
fix flaky scheduled tests: both moving away from the receive_messages calls in tests, and making scheduled vs enqueue time a <= relationshi rather than ==.
similarly, if we're using the "source of truth" internal time for max wait time valdiation, must be<= since the milliseconds can actually be EXACT.

/azp run python - servicebus - tests

/azp run python - servicebus - tests

/azp run python - servicebus - tests

/azp run python - servicebus - tests

/azp run python - servicebus - tests

/azp run python - servicebus - tests

/azp run python - servicebus - tests


Fix destroy

Checklist

[ ] npm test passes
[ ] tests and/or benchmarks are included
[ ] commit message follows commit guidelines

Description of change

fixed: 1742


docs: user should restart docusaurus after adding prism additionalLanguage

if you add php language and don't restart your server, you will get an error like this
uncaught Error: Cannot find module './prism-php'
until you restart your server

Motivation
(Write your motivation here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

thanks 👍


Why do the Observables "extend Observable" instead of using Observable.create()?

In RxBinding1, the observables were created using Observable.create() (now called Observable.unsafeCreate()).
While it made sense that they were never changed to Observable.fromEmitter() for compatibility reasons; I'm wondering: why use extends Observable (and extends MainThreadDisposable on listener) instead of Observable.create(ObservableEmitter) and creating a MainThreadDisposable that wraps it?
I check the source code of RxBinding for Rx-best-practices and I was somewhat surprised that it works so differently compared to Rx1 implementation.

https://github.com/JakeWharton/RxBinding/pull/316#issuecomment-265414491

Understood.


New Player Prefs reset value of previous ones

When creating a new Player Pref, the values of the existing Player Prefs of the same type as the new one are resetted to their default values.

Forgot that Player Prefs value are saved by Unity and not in my asset data so I had to manually delete the Player Pref when deleting it from the asset data. Quickly solved.

After some debugging I found out that:

Only the value of the Player Prefs whose name is the default name of their type change their value. But they really change, not only their value field.
The key isn't correctly passed when instantiating a new PlayerPref and it thinks it's the default of its type, even if it already existed. I didn't realize because it's instantly updated to its proper name. Likely, that's all the problem.

Indeed, that was the problem. I was initializing the Player Pref with its default value and then filtering its key so it's not repeated, but the Player Pref, thinking it was the default of its type, set its value to the default of its type. Now the key is filtered before being passed to the Player Pref constructor. Problem solved.


Update to the SD card build and SDK build readmes.

Update for the dependencies for building the SD card image.
Update to build instructions highlighting the CMake options.

I think this branch starter from a very old branch. Can you rework this PR? I think you have only 1-2 commits, right?


[AGPUSH-2202] Update ReadMe after integration of Kafka

No need of Wildfly Full profile after removal of JMS.

yay! :tada:
thanks for this!