Minecraft - Spigot.yml

Do you think some environment variables for spigot.yml file settings could be added? I'm mostly looking for a bungeecord: true setting. I can add in a workaround for now to change the file, but it would be a useful feature to have.

That sounds like a good and feasible idea.
As a note to myself, here's the config file docs
https://www.spigotmc.org/wiki/spigot-configuration/

It would probably be best to prefix them all by SPIGOT_ just to keep things separated, though I'm sure you were already going to do that. There are... a LOT of settings in the spigot.yml file, to be honest. I'd assist in adding them if I understood your whole setup and if I had the time.
As a side note, does PaperSpigot have some of its own configuration settings? Does Sponge? It may be a good idea to look into that at the same time so you don't need to in the future.
I really appreciate this resource, by the way. I've been working on a bungeecord/mc server clustering system in Kubernetes, and this is the minecraft image I've been using. ^^

Sorry for the silence, I have been continuing to think of this off and on. I'm thinking the image could bundle a spigot.yml.template file that would get processed with bash to do variable substitution such as:
bungeecord: ${SPIGOT_BUNGEECORD:-false}

...however, since you mention running this Kubernetes, it might be more effective to manage the spigot.yml as a ConfigMap entry and mount that into the container.
Speaking of Kubernetes, you might be interested in this tool I created that leverages service discovery to proxy and route incoming client connections:
https://github.com/itzg/mc-router#using-kubernetes-service-auto-discovery


Replace rush with pnpm + lage + beachball

Replaced rush with pnpm + lage + beachball. This allows to better control different workflows of the monorepo: dependencies managing, building/testing packages and versioning.
Developer workflows should be similar to the ones before only need to replace rush with pnpm run when executing commands eg. rush build -> pnpm run build, rush cover -> pnpm run cover, etc.
Added setup for prettier. It is not enforced at the moment but it could be run in CI pipeline to make keep code format consistent.

@aruniverse I guess we will need to create new pipelines or can we make the old ones point to the new definition files?

@aruniverse I guess we will need to create new pipelines or can we make the old ones point to the new definition files?

we will need new pipelines, cant replace the existing ones with updated definitions

@saskliutas @aruniverse How do I build, update now ?  I have little experience with pnpm.

@saskliutas @aruniverse How do I build, update now ? I have little experience with pnpm.

its in the description

take a look at the docs, https://pnpm.io/cli/run

@saskliutas @aruniverse How do I build, update now ? I have little experience with pnpm.

its in the description
 take a look at the docs, https://pnpm.io/cli/run

After updating, pnpm is not available, should I global install pnpm ?  Which version ?

@saskliutas @aruniverse How do I build, update now ? I have little experience with pnpm.

its in the description
 take a look at the docs, https://pnpm.io/cli/run

After updating, pnpm is not available, should I global install pnpm ? Which version ?

Yes you need to install it globally. You can use latest version. Only requirement is that it would be >8.0.0.


where is mnist_mlp_run.py

it's called mnist_mlp_train.py: https://github.com/samuela/git-re-basin/blob/main/src/mnist_mlp_train.py


Change design to receive results in callbacks

Feat: Change design to callback, Flutter Side
Feat: Change design to callback, Swift Side
Docs: update
Fix: [VNRecognizedTextObservation] encode
Refactor: Add Logs
Refactor: Eliminated the need to cast Results.
Docs: update

#10


Developer quick start guide

Document how to set up a development enviroment, build ramen and deploy
it to the test environment. The document is intended to help new contributors to
start quickly.
Notes:

The current version include workarounds for issues with volsync (#661)
and velero (#662).
Addional steps discussed in #760 will be added later.
The document is not linked yet from CONTRIBUITING. When this is finished I'll update
CONTRIBUITING to link to this page and remove unneeded content.

How/where does this fit into CONTRIBUTING.md, do we want to redirect from a quick-start link to here in contributing to this doc?

Yes, we need to link to this page from CONTRIBUTING.md and maybe also from the README.

Contributing also has instructions on DCO/signed-off/forks/clones etc. I suggest we keep that in one place, and make this a quick start for testing ramen in general.

Right, I think some content from CONTRIBUTING.md should move here. CONTRIBUTING.md
can be the entry point for contributors, linking to all other docs. But I don't want
to design the entire thing upfront but build it incrementally.

Changes in current version:

Remove the unneeded workarounds for disabling velero and volsync
Add "Configuring Ramen" to the next steps

When configuring ramen is automated and can be done with one command, or
is included in make deploy-* we can remove this next step.


rPackages.RQuantLib: Fix quantlib

Description of changes

Update quantlib
Enable intraday (=high resolution) dates
Fix rPackages.RQuantLib

Re-opening PR agains r-updates. Original: https://github.com/NixOS/nixpkgs/pull/292029
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I'll just fix the original PR against master, then. I can be maintainer if it's needed.


Clarify statements around CDS Service performance and stale data (fixes #221)

Remove requirement that CDS Services must perform on the order of 500ms
Remove requirement that EHR must supply the latest EHR data

Both of these requirements were not feasible or technically possibly under all scenarios.

This PR and associated changes fixed #221 and #225.

This PR also fixed #339


Experiment with stronger typing for map

Is this interesting direction to explore?
It can take many forms, like

stronger (whiteout undefined) typing if there is controlled creation path that populates initial values.
users could mark some fields as readonly (likely useful only with above or having two alternative interfaces for same data).
types baked into DDS (as an optional layer on top of it):

class SharedMapTyped<T> extends SharedMap {
    readonly values: WithUndefined<T>;
}

potentially alternative handle representation (if we find something interesting / useful here to reduce mental overload).

This is an interesting approach. i'd put thing in framework, not map itself, as it should be optional. another approach i'd thought about was something like
TypedSharedMap<T>{

get(key: key of T): T[key];

set(key: keyof T, T[key];

}

@DLehenbauer curious about your thoughts here

Either way will work fine I think. I prefer not to have .get/.set (stylistically), but that creates its own problems (you have to separate "values" object from map itself).
One thing to poke at though is semantics of this:
map.get("a").foo = 1;

Is it clear to developers that it is supposed (not in current implementation - that's completely broken!) to be noop?
Do developers expect it to be noop? Or do they expect it to fail, and require some kind of explicit copy for this workflow to work:
const value = map.get("a");
value.a = 1; // should this fail? be no-op?
const valuePrime = deepCopy(value); // or something else of same semantics
valuePrime.a = 1;
map.set("a", valuePrime);

The reason this question is important: it's a bit more obvious that value.a = 1 is noop (if we chose noop path here) with get() flow than with using my approach.

Closing, but we should keep discussion going :)


Synchronize dev with master

we need to have the dev branch synchronized again..

Coverage: 90.433%. Remained the same when pulling dd0a23244adfa9d371463e63e71f68cea35e2eef on master into 184deb97dc1319bf8102c4dfaee6a36fcd9255fa on dev.

I would rather create a new dev branch and rename the old one to dev-1.9.1 (since the pull requests are not rebased yet).

ok, I see that you've updated the branches
thanks I close this


Change to Debounce Watcher.

Also ignore copy errors so copy can be retried 10 times.
Compare filename and extensions, to ignore .dll.exp file changes.

Nevermind, the crash was caused by a different change I was testing.  I was messing with the flags passed to dlopen(), trying to fix the issue with TLS.

Cool! Is this fine to merge now?

Yes.  This PR is safe to merge.  With this PR you can use TLS and println! in the plugin on Linux (should be ok on MacOS and windows too).
I have been working with cr.h to find the root cause of issues with reloading a library with TLS.  For now the work around is to just use different filenames (like the timestamp commit in this PR).  The library will not be unloaded even if dlclose is called, because thread_local variables with destructors registered haven't been run.  Which keeps references to the library preventing it from unloading.
The cr-sys crate is stable to use now.  I am looking into adding some features into cr.h to make it easier to use (like custom library symbols and better host-side notification load/unload/rollback/reload/etc..).
Once that work is done, it should be possible to change the dynamic_reload over to using cr-sys while still keeping the same API.  This will allow cr.h to handle the library reloads and verification.

Awesome! That sounds great.


Release v1.0.0

If the fatal issue is not reported on v1.0.0-alpha, we will release it on October 29.
refs: #32

done


Issure #1325 was closed but still some questions are to answer

#1325 was closed, but some of the questions are still open.
First I'm very disappointed about SAP's decision not to prevent a re-occurens of the issue. ("there is nothing we will do")
Here the Questions:
Question 1

getTemporaryExposureKeyHistory()
Retrieves key history from the data store on the device to upload to your internet-accessible server. Calling this method prompts Google Play services to display a dialog that requests consent from the user to gather and upload their exposure keys.The keys that are returned depend on the API version. These key include the past 14 days, but not the current day’s key. (This is different for allowlisted accounts, which also return the current day’s key.)The consent granted by the user lasts for 24 hours. The dialog prompting for consent appears only once for every 24-hour period, regardless of how many times the app calls the method.In v1.7 and higher: Allowlisted apps support returning keys that include the current day’s key, which is tagged with an expiration date (rollingPeriod). When the current key is released, the device stops using it to generate BLE beacons, and replaces it with a new key. Calling this causes a new key to be selected for the remainder of the current day. As a result, if this method is called multiple times, several keys with different rollingPeriod and identical rollingStartNumber can be released for those days it was called on. To enable this feature, contact your Google representative.

So the devices were mistakenly part of the allowlisted accounts?
Question 2
In the UTC time interval 2020-10-07 22:00 to 2020-10-08 2:00 at least one user uploads a same day key.
Can I assume that some of the keys in the 2020-10-08-hour-01.zip were created by a device that is still part of the allowlisted accounts?

There's a difference between allowlisted accounts and apps:

allowlisted accounts: a Google account on an allowlist for the beta program of Exposure Notifications; we use allowlisted users internally for some testing activities but
allowlisted apps: an app (using Exposure Notifications) that is on an allowlisted for certain features

Note that both are referenced in the description of getTemporaryExposureKeyHistory().

So the devices were mistakenly part of the allowlisted accounts?

As per the above description, I guess you mean allowlisted apps 😉  No, it looks like there was a bug on Google side that caused same-day TEKs in CWA, despite the fact that CWA was not on the allowlist for this feature. This has been fixed by Google in the meantime through server-side config on their end.

Can I assume that some of the keys in the 2020-10-08-hour-01.zip were created by a device that is still part of the allowlisted accounts?

I think it's unlikely that this was an allowlisted account (see description above). I assume that this was either a device that had not yet received the server-side update from Google (my primary assumption) or the device had wrong device time.

Hi @mlenkeit

I assume that this was either a device that had not yet received the server-side update from Google (my primary assumption) or the device had wrong device time.

Iirc, @thomasaugsten mentioned somewhere in #933 that Google is able to push client-side config files to the ENF (without any version change). As all pushes to clients happen in waves, it could explain why some devices may still behave in that way.

@vaubaehn that's right AFAIK. Depending on the parameter and the kind of change, Google has different options to roll it out, such as updating all clients at once or in waves. I'm not entirely sure what option Google chose here but I assume it was "all at once".
@Tho-Mat have your questions from the original post been answered? If so, I would suggest that you close the issue.

@mlenkeit

Depending on the parameter and the kind of change, Google has different options to roll it out, such as updating all clients at once or in waves. I'm not entirely sure what option Google chose here but I assume it was "all at once".

Thanks for the additional information. It's fun to learn.

@Tho-Mat have your questions from the original post been answered? If so, I would suggest that you close the issue.

There was no more communication since one week so this issue will be closed.
Thank you very much for all contributors!
Best regards,
SG
Corona-Warn-App Open Source Team


After v1.47 gardenlet fails to reconcile ControllerInstallations with helm3 charts

How to categorize this issue?

/area robustness usability
/kind bug regression
What happened:
After v1.47 gardenlet fails to reconcile ControllerInstallations with helm3 charts, i.e. Chart\.yaml.apiVersion=v2
What you expected to happen:
The controller installation to be successfully reconciled
How to reproduce it (as minimally and precisely as possible):
Deploy the following ControllerDeployment (have just a single v1.Service resource)
---
apiVersion: core.gardener.cloud/v1beta1
kind: ControllerDeployment
metadata:
  name: foo
type: helm
providerConfig:
  chart: H4sIAAAAAAAAA+1X32/bNhDOM/+Ka7uHtpgpS/4F+C1Isi1Y0QZ1YextoKSzxEUiBZJy4hXd376jlCCN284rUCUoyg8GRVHH49HH7+640To6GhhjwmI2656E/WfXjyfTOJkl87kfj8eTyfwIZkMb5tFaJwzAkdHa/Zfcoe/fKTbkf15iVctCaYODrOEdPJ9Ov+j/2WS25/9kupgcwXgQa/bwg/v/GVwI59AoC05DfwjgqkQFaSurXKoCGpFdigItZ8/gXSkt2LZptHHUoYNTQVHpFGrhspKkfwaDlXByizTPlR+NC5WTAoUFfdUKnjcGN/Iac7iSJPfkBYc3qtqBVt1MbxI0aKCSCjnjp6s/V45sIxUnuq5JwfpkBbk0lvFCuqhre/MZT/82UdfeDpRF5JvbV7tV0Z2ilPbXNrCRFVr2kturhtpUXFLrat/XpIe9/IdmrIWRurVwfnpG6zZG/4WZY1zmKKJenIYY39pM5xixx3bu/4Dn/0kpjOM7UVfDrHGI//Fisc//ZDEO/H8IiEau0Vhi5BK2CRNNc/c65jEfj3LcshxtZmTjuvFj+I3yBWT+1MBGG/i9TYmt6Ig+StS4pEHN3K6hHumrZNYxnm0/o/ixt//Dw/M/1xkv9HBrHOL/fL6f/+PpNA78fwhEEawuTv8Y/ULZ70Q3O0p1pXuH124JyThJYHV8AaszIJYL1b2IDSVKKRxCputGqJ1P7PCrMDkqSteZVs7ItKVcbVkUsVv9r2SGyuLonMSc3Eg0FEiosihxlPAxI7lCLwuvwqu2JYwyeMp5RL8tqlybiPJ72aacVo2Km9XuOiXl8Oh2+qgzQlcVmpHBQlpnugjESS2dd+Dw03OKSdCrX5+9XZ2/ef3i5hWvRd1UGH1Jh0+TcHbtaDc+mJG+p956KqO6KukmLKISKZUTcG9TfdnUhcybQV9eudL/lcZQJQF3i8K9RVnzsfZvGTU9/x3SjslCO9BN8Ovvf8lkMg33v4fAff9bNFsiqsgy3apvVhIerP9m+/F/nvj7f4j/w+Ne/RezS6nyJaz6Y3DcHwNWoxO5cGLJAPoC7/174GtRtXQp9AH1wwf6UokUK+tlwEfZzwk99mYDPoHn/7Z30mAXwEP8H8efxP9ZHO5/D4KOqakwj21HQEBAQEBAQEBAQEBAQEBAQMAw+Bfzjb0UACgAAA==
  values:
    image:
      tag: v0.1.0-dev
---
apiVersion: core.gardener.cloud/v1beta1
kind: ControllerRegistration
metadata:
  name: foo
spec:
  deployment:
    deploymentRefs:
    - name: foo
    policy: Always
  resources:
  - kind: Extension
    type: foo

and make sure the gardenlet fails to reconcile the ControllerInstallation with
ts="2022-06-13T15:48:15.779+0000" level=info msg="Error syncing ControllerInstallation foo-d6kbq: can't create load chart from archive: apiVersion 'v2' is not valid. The value must be \"v1\""

If the gardenlet is downgraded to v1.46.2, the ControllerInstallation is successfully reconciled.
Anything else we need to know?:
This was working fine until v1.46.2
Environment:

Gardener version:  >= 1.47
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
Others:

This seems to be introduced with https://github.com/gardener/gardener/pull/5804. The upstream change is https://github.com/helm/helm/pull/6180 and it is related to https://github.com/helm/helm/issues/5907. My understanding is that as long as Gardener is using k8s.io/helm@v2, it should not be able to manage helm V2 charts.

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/reopen

You are completely right, that's happens because of corresponding validation in the LoadArchive/LoadFiles funcs of k8s.io/helm v2.16.1+incompatible package. However, I didn't find why it happed since after 1.47 version, cause I don't see any changes in these functions.
Anyway, I'm going to create PR for that issue, cause I have the same problem with rendering helm chart (with apiVersion v2) for managedResources.

Have you checked if it is what I suspected in #6103 (comment) ?

I missed it. Yes, it's true, the apiVersion check was introduced in one of the updates from v2.13.1 to v2.16.1.

/touch

/reopen

/lifecycle frozen


Upgrade org.apache.maven.plugins:maven-install-plugin 3.1.0 -> 3.1.1

This PR contains the following updates:

Package
Type
Update
Change

org.apache.maven.plugins:maven-install-plugin
build
patch
3.1.0 -> 3.1.1

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade maven-install-plugin 3.1.0 -> 3.1.1

See https://github.com/apache/maven-install-plugin/compare/maven-install-plugin-3.1.0...maven-install-plugin-3.1.1


Use 'isKey={true}' to specify a unique column.

I am using react-bootstrap-table table component. Event after having isKey in my My TableHeaderColumn am still getting error saying - "Uncaught (in promise) Error. No any key column defined in TableHeaderColumn. Use 'isKey={true}' to specify a unique column."
Below is my code
const TableComponent = (props) => {
  const { isKeyProp } = props
  const products = [
    {
      id: 1,
      name: 'Item name 1',
      price: 100,
    },
    {
      id: 2,
      name: 'Item name 2',
      price: 200,
    },
    {
      id: 3,
      name: 'Item name 3',
      price: 300,
    },
  ]
  return (
    <BootstrapTable data={products} keyField={uuidV4()} >
      <TableHeaderColumn dataField={products.id} isKey={isKeyProp} >Product Id</TableHeaderColumn>
      <TableHeaderColumn dataField={products.name} >Product Name</TableHeaderColumn>
      <TableHeaderColumn dataField={products.price} >Product Price</TableHeaderColumn>
    </BootstrapTable>
  )
}

TableComponent.propTypes = {
  isKeyProp: PropTypes.bool.isRequired,
}

TableComponent.defaultProps = {
  isKeyProp: true,
}

No clue why ..

This doesn't seem to be enzyme-related, and you're not including any of the code that creates the element, or enzyme-wraps it.
Closing for now; feel free to provide that information and we can reopen.


Enable/Disable logging from toolbar

Would be nice to toggle the logging from the toolbar.

Right now clicking the toolbar takes you to your connectordb homepage. Logging can be disabled in options page (right click, options, disable logging).
I don't know which use of the toolbar button is best - enabling/disabling logging, or going to the server page. Technically, incognito mode turns off logging, but I think maybe toggling with button is better.


Zoom control won't show

BUG / PROBREM REPORT
SUMMARY
Zoom control won't show even we have enabled.
VERSIONS
Xamarin.Forms.GoogleMaps - 2.2.1-beta1
PLATFORMS
(test only on iOS Emu)

[x] iOS

HOW TO REPRODUCE

By testing the sample solutions / iOS / BasicMapPage
Once we click on the 'ZoomControls Enable' button, the control itself won't show up.

This is not worked on iOS because GoogleMaps iOS SDK does not support it.


Automatically pull in config from application settings

Currently the config must be manually specified. This can be a fairly tedious process since it involves extracting the settings from the HTML snippet in the newrelic console each time settings are changed. This can lead to the settings in the console being inconsistent from the settings manually specified in the javascript config if they are not perfectly transcribed.
Summary
It would be nice if rather than having to manually extract config from the HTML snippet, this config was automatically pulled from newrelic. This seems to be already done with the APM browser injection method, so it seems like it should be possible here too.
Desired Behavior
I would like to be able to call some API endpoint, specify the necessary tokens and entity IDs etc, and in return get the config settings for the application.
Possible Solution
Expose an API endpoint that returns the config for a given application, specifically the init, loader_config, and info settings. Alternatively, add some function within this library to automatically pull in the settings from a given application.
Additional context
Testing or changing features in the newrelic console requires a significant amount of effort to do, in comparison with the APM browser injection which pulls in the config settings automatically.

Hi @paulwalko This is actually already possible with our GraphQL APIs. Here is a doc that can help you implement this. Keep in mind it requires an API key to access these APIs and those keys should not be exposed publicly. However, you could integrate this into your build or CI/CD process in some way, as long as you do not expose the key. Please let us know if you need further assistance.


How to specify custom response decoder?

it's now trying to get a valid function code (of course there won't be, since the function code is custom), and give up after 20 retries.
tokio-modbus-0.16.1\src\codec\rtu.rs 265 ---> Failed to decode response frame: Invalid function code: 0x65
Is there a way users can specify their own decoder outside?

Decoding of user-defined function codes (65..=72 and 100..=110) has not been implemented yet.
get_response_pdu_len() only supports a limited subset of functions codes while decode_response_pdu_bytes() already passes through all unhandled function codes.

There is also a considerable amount of redundancy between the code of the mentioned functions. Could probably be rewritten in a better way.

yes, when I return a correct number for a custom function code in get_response_pdu_len(), it goes correctly.  but there's many other function codes and only the user knowns what len is expected.

yes, when I return a correct number for a custom function code in get_response_pdu_len(), it goes correctly. but there's many other function codes and only the user knowns what len is expected.

Checking the expected size only is an additional safety measure. The CRC code in the ADU serves as the sentinel.
Decoding of ADU/PDU frames should be rewritten. I have vague ideas, but unfortunately no time to do this.


company environment specific settings

Not meant to be included, but worth to mention which are and why and maybe for to be added to knowledge base.
I am using the following:
network.automatic-ntlm-auth.allow-non-fqdn
boolean: Set to true to enable SSO auth when using non-FQDN url.
network.automatic-ntlm-auth.trusted-uris
string: enter domain name where SSO is desired, multiple domain are comma separated
security.enterprise_roots.enabled
boolean: when true, the computer certificate store is used
plugins.load_appdir_plugins
boolean: I dont know yet the security implications, but when using "skype for business" (S4B) and when you click a meeting URL in for example email, the S4B meeting client is invoked over a browser and fails to open S4B meeting client... setting this one to true resolves this "problem"
It doesn't work for me personally, since I am browsing with sandboxed FF.... obviously. ;)

plugins.load_appdir_plugins -> default false.
security.enterprise_roots.enabled -> default false (hidden pref)
network.automatic-ntlm-auth.trusted-uris -> default blank string
network.automatic-ntlm-auth.allow-non-fqdn -> default false
I don't think we need these at all. If anything we would enforce the defaults and that's it. But these seem pretty specific to enterprise, and in that case, they're not private anyway. Even a home user wanting to use S4B, that's their problem. People should learn to use multiple browsers and multiple profiles for specific tasks.

No meant to be included... just for KB, if someone would need such.


Display proper price for product on category page

Fix #891

If we're here me and @elwoodxblues want to suggest a change:
Override Product.get_price_range and return PriceRange(product.price, product.price) if no variants exist. Then we don't need the if condition at the beginning of get_availability.

Codecov Report

Merging #896 into master will not impact coverage.

@@           Coverage Diff           @@
##           master     #896   +/-   ##
=======================================
  Coverage   59.37%   59.37%
=======================================
  Files         114      114
  Lines        5972     5972
  Branches      724      724
=======================================
  Hits         3546     3546
  Misses       2288     2288
  Partials      138      138

Continue to review full report at Codecov.

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

👍 LGTM


Provide hooks to enable extensions to extend command line options

VS Code has a set of basic command-line options. However, there is currently AFAIK no way for extensions to handle additional command-line options.
My specific use case is that SQL Server Management Studio supports connecting to a SQL Server database via parameters passed to the command line:
ssms -S dbserver -U myUser -P pwd1234

which opens a new SQL editing window with the given connection parameters. If VS Code allowed extensions to handle additional command line options, then the same could be done with VS Code, via the MS SQL extension.
Some additional thoughts:

In order to prevent conflicts between extensions, some sort of naming scheme for each option might be required:
vscode -mssql:S dbserver -mssql:U myUser

It would probably be easier to map options to commands contributed by the extension, but I am not sure that would be sufficient. For example, in this particular scenario, there is no corresponding command to open a new editor which is already connected with the following connection parameters. Also, AFAIK commands don't take arguments/parameters.

Hi guys, just wondering how this was going? I would love this feature.
Keep up the good work!
Cheers.


Crowding in the processing block

There is crowding in the processing block when the names are long.

I feel I may have fixed this with a different issue. Will have to double check.

fixed with https://github.com/azavea/raster-foundry/commit/506f28635324955dac688f78d1e6703cf48e0f62


Squelch devtoolset-11 compile errors

Minor header changes to get the core module to compile/link correctly with gcc 11.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Andrew Timmes seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


chore(readme): fix links

Signed-off-by: Brian Gleeson<EMAIL_ADDRESS>PR summary
Fix readme links so that it opens the correct code option in the docs
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[x] Documentation content changes
[ ] Other (please describe)

:tada: This PR is included in version 0.3.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


GAH: Do we engrave on layer 5?

information in the instruction panel valley
icons for each die inside the die cradle

I have created a 6th layer which is a "blank" fifth layer. That way we can decorate the back on the fifth layer, but the user can choose instead to use layer 6 that has no decoration.


WFLY-14436 Improve error for incorrect class for xa-datasource-class, etc.

Issue: https://issues.redhat.com/browse/WFLY-14436

Hello, sudeshnas93. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

@tadamski please approve


Don Prep Videos

Rajmeet:

[x] Spring Tutorial Create RESTFul Web Services using Spring MVC and Spring Boot by John Thompson
[x] Things I Wish I Knew When I Started Testing Spring Boot Applications by Philip Riecks
[x] Spring Boot + Junit 5 + Mockito Tutorial
[ ] DTOs vs. Entities – The Truth by Greg Turnquist

Aayushi

[ ] Spring Tutorial Create RESTFul Web Services using Spring MVC and Spring Boot by John Thompson
[ ] Things I Wish I Knew When I Started Testing Spring Boot Applications by Philip Riecks
[ ] Spring Boot + Junit 5 + Mockito Tutorial
[ ] DTOs vs. Entities – The Truth by Greg Turnquist

Suvan

[ ] Spring Tutorial Create RESTFul Web Services using Spring MVC and Spring Boot by John Thompson
[ ] Things I Wish I Knew When I Started Testing Spring Boot Applications by Philip Riecks
[ ] Spring Boot + Junit 5 + Mockito Tutorial
[ ] DTOs vs. Entities – The Truth by Greg Turnquist

Bharath

[ ] Spring Tutorial Create RESTFul Web Services using Spring MVC and Spring Boot by John Thompson
[ ] Things I Wish I Knew When I Started Testing Spring Boot Applications by Philip Riecks
[ ] Spring Boot + Junit 5 + Mockito Tutorial
[ ] DTOs vs. Entities – The Truth by Greg Turnquist

Tryston

[ ] Spring Tutorial Create RESTFul Web Services using Spring MVC and Spring Boot by John Thompson
[ ] Things I Wish I Knew When I Started Testing Spring Boot Applications by Philip Riecks
[ ] Spring Boot + Junit 5 + Mockito Tutorial
[ ] DTOs vs. Entities – The Truth by Greg Turnquist

No longer a valid issue


Question: Data Conversion

I was looking for a forum to ask this question, but there doesn't seem to be much available yet, so I thought I'd ask it here instead.
Concerning Data Conversion from older NAV versions, what would be the best way to approach conversion of data to the extension structure?
Of course, we could simple export data to excel, copy/paste, write an xmlport, but there might be better/smarter/faster ways to convert data from a physical table in an old version to an extension table in NAV 2018?

Your scenario is an on-prem db with tradtional C/AL changes and you now want to move to extensions, right?
I would say your install Codeunit should handle that as it should have access to the old (C/AL) tables and could fill the new (AL) tables as needed

If you want the new extension fields to be available at the same time as the old fields you need to handle naming of fields by either renaming the old fields first, or using new field names in the extension so that there's no overlap. I'd recommend the latter as it would be better practice to use a prefix in your new fields and then use the Caption property to set the friendly name. This not only lets you have both old and new fields in order to move data, but also helps future-proof your extension in the event another extension is installed with the same field names.

@tfenster
That makes a lot of sense, and then using the Data Version to figure out if this is the initial install before triggering code that looks for the old tables and any data that might be there. Thanks!
@MikeGlue We have been adding the prefix to all AL development and Conversion, so that works perfectly. Thanks!

@tfenster @MikeGlue this worked perfectly, thank you both for your help. I created two procedures to handle Tables as well as Table Extension Fields in a fairly generic manner during the initial installation.
Closing the Issue.

@bwdeleeuw Thanks for letting us know. If you have a generic solution, do you mind sharing it? I would guess a lot of people are creating something along those lines

@tfenster
Sure, I made something like this:
codeunit 60000 "Installation Template"
{
    Subtype = Install;

    trigger OnInstallAppPerCompany();
    var
        ModuleInfo: ModuleInfo;
    begin
        NavApp.GetCurrentModuleInfo(ModuleInfo);
        if ModuleInfo.DataVersion = Version.Create(0, 0, 0, 0) then
            HandleFreshInstallAndConversion;
    end;

    local procedure HandleFreshInstallAndConversion()
    var
    begin
        TransferTable(50000,Database::"New AL Table 2");
        TransferTable(50001,Database::"New AL Table 2");
        TransferField(18,50000,60000);
        TransferField(27,50001,60001);
    end;

    procedure TransferTable(SourceTableID: Integer; TargetTableID: Integer);
    var
        SourceRef: RecordRef;
        TargetRef: RecordRef;
        FldRef: FieldRef;
        FieldsSource: Record Field;
        FieldsTarget: Record Field;
        TempFieldsNoToTransfer: Record Integer temporary;
    begin
        FieldsSource.SETRANGE(TableNo, SourceTableID);
        FieldsSource.SETRANGE(Class, FieldsSource.Class::Normal);
        FieldsSource.SETRANGE(Enabled, TRUE);
        if FieldsSource.FINDSET then
            repeat
                if FieldsTarget.GET(TargetTableID, FieldsSource."No.") then
                    if(FieldsTarget.Class = FieldsSource.Class) AND
                        (FieldsTarget.Type = FieldsSource.Type)
                    then begin
                        TempFieldsNoToTransfer.Number := FieldsSource."No.";
                        TempFieldsNoToTransfer.INSERT;
                    end;
            until FieldsSource.NEXT = 0;

        if TempFieldsNoToTransfer.ISEMPTY then
            exit;

        SourceRef.OPEN(SourceTableID);
        TargetRef.OPEN(TargetTableID);
        if SourceRef.FINDSET then
            repeat
                TempFieldsNoToTransfer.FINDSET;
                repeat
                    FldRef := TargetRef.FIELD(TempFieldsNoToTransfer.Number);
                    FldRef.VALUE := SourceRef.FIELD(TempFieldsNoToTransfer.Number).VALUE;
                until TempFieldsNoToTransfer.NEXT = 0;
                TargetRef.INSERT;
            until SourceRef.NEXT = 0;
    end;

    procedure TransferField(SourceTableID: Integer; SourceFieldID: Integer; TargetFieldID: Integer);
    var
        SourceRef: RecordRef;
        FldRef: FieldRef;
    begin
        SourceRef.OPEN(SourceTableID);
        if SourceRef.FINDSET then
            repeat
                if SourceRef.FieldExist(SourceFieldID) then begin
                    FldRef := SourceRef.FIELD(TargetFieldID);
                    FldRef.Value := SourceRef.FIELD(SourceFieldID).Value;
                    SourceRef.Modify;
                end;
            until SourceRef.Next = 0;
    end;
}

There are a caveats to this code, concerning the TransferField procedure. If you have multiple fields in the same table, this code would not be optimal, because it runs through each record for each field repeatedly. It works for my current needs, but of course there would be a smarter way to handle multiple fields in the same base table at the same time. I was playing with the idea of a List, but didn't need it yet.


WIP/RFC: refactor/revisit tests/runtests

This is required/useful to use with other test runners then, e.g.
pytest.

I'm closing this as it is stale, a work in progress, and there is not really much detail on what it solves.
Please create a ticket detailing the problem being addressed in more detail if you wish to pick this up again.

@pope1ni
Fair enough, thanks for cleaning up things.
However, there is some reasoning in the commit message already - IIRC this came out of me trying to use pytest with Django's testsuite.

Thanks @blueyed. I noticed the references to pytest. I presume that you're referring to using it as the test runner for Django's test suite rather than for the tests for a project using Django.
My thinking was that the details I've asked for would include the explaining how the tests would be invoked using pytest and what each of the required changes are to make the current code compatible.

https://code.djangoproject.com/ticket/30415
I think it was related this ticket which was closed as 'needsinfo'.

@smithdc1 yes, thanks for linking.
@pope1ni yes, it is meant for using other test runners, specifically pytest here.
This was apparently from when I've started to look into making pytest more compliant to Python's unittest etc, but has stalled since then.
I might come back to it after all, but likely not in the near future.
AFAICT it would still make sense to have this as a (refactoring) step, but apparently needs some review of the ticket and PR, which even myself am not into anymore currently.
Therefore I'm still fine with it being closed for now.
Thanks again for everything.


[Issue 246.3][Try #2] Gui: Added Backend Connection and CSS comments

Add process operators button with functionality
Update CSS for better documentation

Per our F2F reviews with Jimmy, Kishore and me, this PR is good to go.


Testing Input Object .

Currently in the client since we have protected access over the methods in InputObject it becomes impossible to test an argument that has an input object as the value .

I am good with there being a public getter method on InputObject

PR - https://github.com/americanexpress/nodes/pull/39/

👍 will be releasing a new version shortly


Make clicking on a course deselect all its sections when all sections are either selected or closed

Currently, clicking on a course will only deselect every section in the course when all sections are selected. Since courses are likely to have one or two closed sections that won't be selected by the initial click on the course, the behavior should be changed so that it ignores closed sections when checking to see if all the sections are selected.

I noticed this as well thanks

This is implemented as of 2608408.


question about MIDI and F0

I wonder how to get F0 truth in practice ? In my opinion, MIDI could be labeled mannually,  and  the F0 truth are usually got from human voice? And i wonder why you focus on midiless version in future, the midiless performance better than midi one or the midi lable is harder to obtain than F0?
In my test, the ph_dur estimation is poor, when test  your midi-A version. If given the ph_dur GT as input, the performance is improved a lot. However  the performance in midi-B test is always  better than midi-A test .
I am new to SVS, sorry for above questions.

Advantages of doing so are discussed in #67. MIDI are harder to label, and decoupling MIDI from acoustic models can improve the controllability and performance. In the future, pitch (f0) can be predicted from lyrics and MIDI via variance models.
Old MIDI-A and MIDI-B both have duration predictors; there is no difference in their duration prediction method and logic.

0831 is a really old checkpoint. At that time we haven't gone far from the original repo.


Add support for https uri in extensions.wasm.v3.VmConfig

Title: Add support to fetch wasm binary from https base clusters
Description:
Currently, using https urls to fetch wasm binaries, does not support https, as it will always set the wrong :scheme:http header, despite configuring an https url.
Bootstrapping wasm service:
        bootstrap_extensions:
        - name: envoy.bootstrap.wasm
          typed_config:
            "@type": type.googleapis.com/envoy.extensions.wasm.v3.WasmService
            singleton: true
            config:
              name: wasm-plugin
              root_id: wasm_root_id
              vm_config:
                runtime: "envoy.wasm.runtime.v8"
                code:
                  remote:
                    http_uri:
                      uri: "https://github.com/XXX/YYY/releases/download/ZZZ/envoy-wasm-plugin.wasm"
                      timeout: 600s
                      cluster: "github-com"
                    sha256: "aab45ba4aab5c313b5206fa57b3843cd6a09c633eddef08371a83699c312aaf2"

Creating static cluster:
          - name: "github-com"
            connect_timeout: "60s"
            type: STRICT_DNS
            load_assignment:
              cluster_name: "github-com"
              endpoints:
              - lb_endpoints:
                - endpoint:
                    address:
                      socket_address:
                        address: github.com
                        port_value: 443
            transport_socket:
              name: envoy.transport_sockets.tls
              typed_config:
                "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
                sni: github.com

This results in the following error traces:
2023-09-26T19:30:48.587732Z	debug	envoy config external/envoy/source/common/config/remote_data_fetcher.cc:35	fetch remote data from [uri = https://github.com/XXX/YYY/releases/download/ZZZ/envoy-wasm-plugin.wasm]: start	thread=27
2023-09-26T19:30:48.587780Z debug envoy router external/envoy/source/common/router/router.cc:478  [C0][S17801876496647140807] cluster 'github-com' match for URL '/XXX/YYY/releases/download/ZZZ/envoy-wasm-plugin.wasm' thread=27
2023-09-26T19:30:48.587866Z debug envoy router external/envoy/source/common/router/router.cc:686  [C0][S17801876496647140807] router decoding headers:
':path', '/XXX/YYY/releases/download/ZZZ/envoy-wasm-plugin.wasm'
':authority', 'github.com'
':method', 'GET'
':scheme', 'http'
'x-envoy-internal', 'true'
'x-forwarded-for', '<IP_ADDRESS>'
'x-envoy-expected-rq-timeout-ms', '600000'
  thread=27

...

2023-09-26T19:30:48.588508Z debug envoy router external/envoy/source/common/router/router.cc:1278 [C0][S17801876496647140807] upstream reset: reset reason: connection failure, transport failure reason: immediate connect error: Network is unreachable thread=27
2023-09-26T19:30:48.588576Z debug envoy http external/envoy/source/common/http/async_client_impl.cc:123 async http request response headers (end_stream=false):
':status', '503'
'content-length', '166'
'content-type', 'text/plain'
  thread=27

As one can see, the headers are not taking into account the fact that my uri is of scheme https.
Source code:
Digging into the code, I can see the following.
https://github.com/envoyproxy/envoy/blob/f1369ae370a1062744980b0c0a4a991c8acf68a2/source/common/config/remote_data_fetcher.cc#L33C52-L33C66
void RemoteDataFetcher::fetch() {
  Http::RequestMessagePtr message = Http::Utility::prepareHeaders(uri_);
  message->headers().setReferenceMethod(Http::Headers::get().MethodValues.Get);
  ENVOY_LOG(debug, "fetch remote data from [uri = {}]: start", uri_.uri());
  const auto thread_local_cluster = cm_.getThreadLocalCluster(uri_.cluster());
  if (thread_local_cluster != nullptr) {
    request_ = thread_local_cluster->httpAsyncClient().send(
        std::move(message), *this,
        Http::AsyncClient::RequestOptions().setTimeout(
            std::chrono::milliseconds(DurationUtil::durationToMilliseconds(uri_.timeout()))));
  } else {
    ENVOY_LOG(debug, "fetch remote data [uri = {}]: no cluster {}", uri_.uri(), uri_.cluster());
    callback_.onFailure(FailureReason::Network);
  }
}

https://github.com/envoyproxy/envoy/blob/f1369ae370a1062744980b0c0a4a991c8acf68a2/source/common/http/utility.cc#L1083
RequestMessagePtr Utility::prepareHeaders(const envoy::config::core::v3::HttpUri& http_uri) {
  absl::string_view host, path;
  extractHostPathFromUri(http_uri.uri(), host, path);

  RequestMessagePtr message(new RequestMessageImpl());
  message->headers().setPath(path);
  message->headers().setHost(host);

  return message;
}

As you can see, they just do not take into account the scheme at all.
Also, there is no logic to deal with retries, or with 302 HTTP redirect (eg http > https) from the upstream web server containing the wasm binary.

This is correct, URL fetching of wasm is very rudimentary and should only be used with care in production. Envoy should be issuing a warning if you look into the logs. This is the reason why Istio built a whole separate sidecar to pre-fetch the modules.


Revert

Revert changed to a branch - revert-delivery-date
delivery_date column is no longer necessary

Revert changes to previous actions and code changes


Declaration of Encore\Admin\Form\Field\Checkbox::groups($groups = Array) should be compatible with Encore\Admin\Form\Field\Select::groups(array $groups)

Laravel Version: ^5.8.*
PHP Version: 7.1.3
Laravel-admin: ^1.7

Description:
Declaration of Encore\Admin\Form\Field\Checkbox::groups($groups = Array) should be compatible with Encore\Admin\Form\Field\Select::groups(array $groups)
Steps To Reproduce:
Problem is about when I run install laravel admin again

I am having this problem as well . Have you been able to solve it

Yes it is solved by switch laravel Admin version 1.8.9
On Mon, May 24, 2021, 7:47 PM Charles Awulor @.***>
wrote:

I am having this problem as well . Have you been able to solve it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/z-song/laravel-admin/issues/5326#issuecomment-847018529,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARLPDY2KTEP7MZKTEWUQ4TTPJDGXANCNFSM45GTBCDA
.

Yes it is solved by switch laravel Admin version 1.8.9
…
On Mon, May 24, 2021, 7:47 PM Charles Awulor @.***> wrote: I am having this problem as well . Have you been able to solve it — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5326 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARLPDY2KTEP7MZKTEWUQ4TTPJDGXANCNFSM45GTBCDA .

But the bug has reappeared in v1.8.12, The other version of v1.8.11 doesn't have this problem


App opens in fullscreen

App opens in fullscreen on mac os mojave.

@sohojmanush need more info

Just to also confirm I'm having this happen. I'm running Mojave and when started, OpenMTP fills the screen - covering my (auto-hidden) menu bar. Covering the menu bar makes re-sizing OpenMTP a little difficult as the menu keeps popping up over OpenMTP.

Just to also confirm I'm having this happen. I'm running Mojave and when started, OpenMTP fills the screen - covering my (auto-hidden) menu bar. Covering the menu bar makes re-sizing OpenMTP a little difficult as the menu keeps popping up over OpenMTP.

confirmed also in Big Sur 11.0.1
here is default window size, too big in my Samsung 28' 4K

for additional information i also attach detailed structure of my machine
HacOS_config.txt

confirmed also in Big Sur 11.0.1
here is default window size, too big in my Samsung 28' 4K

for additional information i also attach detailed structure of my machine
HacOS_config.txt

This is my only issue with openmtp, in combination with the UI in my opinion being a bit too big. It doesn't remember the window size when last opened, and always takes up the largest amount of screen space possible. I downloaded the beta to see if this was also the behaviour in that version.
https://user-images.githubusercontent.com/10742076/156920542-b2585bae-73a8-4dd6-9452-e3dac850ddf6.mov
Technically speaking, it's not opening in full screen as that is a separate mode, and your menubar and dock would be obscured.

I will take a look at it.

I did a little research here and I see why it's opening maximized (calling mainWindow.maximize() will do that), but it seems like Electron apps won't preserve their window position without quite a bit of work.
I attempted to put something together for that, but I don't understand settings.js well enough yet to know how to persist and restore settings. And as some other developers on the Internet have noted, there are a lot of edge cases: if you fix it so it works correctly with multiple monitors, you can end up creating a situation where the window is offscreen and you can't get it back. Electron really just needs to create an API for this (there's an 8-year-old feature request ticket for it).
@ganeshrvel I can remove the line that maximizes the window on start, but are you OK with the new behavior where the window always starts as a centered 880x640px window?

The reason I havent removed maximize() by default is that on a smaller screen the file names gets crushed down (on list view) and few other reasons.
What we could here is to write back window dimensions to the settings.json file on a resize event and later when they open the app preset the window size (fetch it from settings.json if it is set).


Apply requires to extend_api

Is there currently a way to achieve this?
@hug.extend_api ('/backoffice', requires = token_key_authentication)
def extend_api_backoffice():
        import backoffice
        return (backoffice,)

or
hug_auth = hug.http (requires = token_key_authentication)
@hug_auth.extend_api ('/backoffice')
def extend_api_backoffice():
        import backoffice
        return (backoffice,)

I would also like to know if there is a way to extend like that

@timothycrosley, does 287933cab78652d0535ea5b93d87fa161e9feabe look correct to do this?


[DemoApp] Fix constraint bug

There is a bug which it is shown our xcode console related with constraints.


[fftw3] Add fftw3 port to vcpkg

Hello,
I made a fftw3 port for vcpkg.
It currently builds a SSE/SSE2 enabled version of fftw.
It can be build statically and dynamically.
I have not tested the static version in a project. But the library seems fine.
Greetings,
Nagua

@nagua,
Thanks for having already signed the Contribution License Agreement. Your agreement has not been validated yet. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Great job, thanks!
I made a modification while merging to avoid completely replacing the CMAKE_CXX_FLAGS variable. Instead, I just added /bigobj and /openmp to the add_definitions() directive.


Creating remote instances is not as fast as it could be

It has been observed, that creating many (> 100) remote instances of objects with VRPC takes much longer than expected. We have measured latencies of around 400-800ms per instance in a test setup. By looking through the code and the timings, the following performance improvement points have been identified:

use QoS 0 instead of QoS 1. On a developer laptop (i7) with a local, anonymous broker, we see 10..20ms in flight time for QoS 1 and only 1..2ms for QoS 0
combine subscriptions for member functions at least into a single SUBSCRIBE packet but much better use wildcards
switch the order of publish/subscribe after instance creation

With that, the latency problems of 800ms can be reduced to <15ms.

The issue is addressed in two ways:

Subscription is now using wildcarding
OoS 0 setting is optionally possible


Extract JWT configuration

Extracts the JWT configuration out of the root configuration object into its own configuration object.
This means that if validation is added to the respective properties, the variables won't be required to be set if the module is not enabled.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

14 of 14 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 93.099%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
6789

Relevant Lines:
7043

💛  - Coveralls


[UCHAT-3452] Removed the option of giving user the display option to …

…see nickname of team members instead of username/full_name.
Summary
In User's Account Settings and Team&User Setting of the Admin Console, uChat currently gives users and admin the option to choose nickman as the attribute to be displayed for team members instead of username or fullname. However, uChat doesn't have the notion of nickname. Thus this change is to remove those options from all applicable places.
Ticket Link
https://jira.uberinternal.com/browse/UCHAT-3452
Related Pull Requests
Has server changes: No
Has redux changes: No
Has mobile changes: No
Testing
Done on localhost and verified that both user settings and admin console team display settings have got the option removed:
![User settings changes]
(https://drive.google.com/open?id=1Vvi9qYIX4JODjWcOIXCkmw75kcbIZ6HG)
![Admin console changes]
(https://drive.google.com/open?id=11ZdmOfi7giAmy3C_6PzUKFEPixMi9OoR)

So this seems like a 'feature' of something that we can never merge to Mattermost. Okay for now, but we need to start thinking about how we merge all customization as options into the main mattermost project rather than a random commenting.
This also makes rebasing harder latter.
If you still want to merge knowing this, then go again.

So this seems like a 'feature' of something that we can never merge to Mattermost. Okay for now, but we need to start thinking about how we merge all customization as options into the main mattermost project rather than a random commenting.
This also makes rebasing harder latter.
If you still want to merge knowing this, then go again.

Yes @csduarte , thats my concern as well. We need to device a plan to make our merges & rebasing simpler. In fact that is the reason, I ended up doing this commenting instead of implementing it the correct way which is to make this option configurable using some server side configuration. Because merging 8 lines of commented out code would be simpler then passing on a config flag/option across multiple layers of code touching a lot of files.

I fixed the UTs and directly pushed in dev branch for the staging build & deployment for demo.


Logout from settings

I had to delete the migrations and reset the DB version since there's a bug with activeandroid and deletions (https://github.com/pardom/ActiveAndroid/issues/127) or something that I failed to understand with migrations.
After this s merged you need to re-install the app.
Oh and ignore the commits by Ido, I'm working from his computer :D

some comments
:ok:


Solve Oracle special syntax error，  for example：start with  connect by

What changes were proposed in this pull request?

[ ] Finshed changes describe

How was this patch tested?

[ ] Testing done

Are there and DOC need to update?

[ ] Doc is finished

Spark Core Compatibility

commit太多，关闭新开PR.


Support Vector index and HNSW as the first implementation

Still making more improvements, configs, etc.

Support Vector Index on top of float array(float multi-value) column
First Implementation is HNSW
Add predicate as well as function: VectorSimilarity(v1, v2, [optional topK, default: 10]) to retrieve topK closest vectors

Note:

The function VectorSimilarity will return a double of the similarity, and in real usage, we re expecting v1 to be an embedding column, v2 to be the search term embedding literal.
Since VectorSimilarity is a predicate, once config the topK, this predicate will return topk rows per segment. Then if you are using this index with other predicate, you may not get expected number of rows since the records matching other predicate might not in the topk rows.

Sample query is:
SELECT ProductId, UserId, l2_distance(embedding, ARRAY[-0.0013143676,-0.011042999,...]) AS l2_dist, n_tokens, combined
FROM fineFoodReviews
WHERE VECTOR_SIMILARITY(embedding,   ARRAY[-0.0013143676,-0.011042999,...], 5)
ORDER by l2_dist ASC
LIMIT 10

Codecov Report

Merging #11977 (6fa3965) into master (972b555) will decrease coverage by 61.45%.
Report is 1 commits behind head on master.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master   #11977       +/-   ##
=============================================
- Coverage     61.44%    0.00%   -61.45%
+ Complexity     1141        6     -1135
=============================================
  Files          2385     2332       -53
  Lines        129189   127008     -2181
  Branches      19998    19629      -369
=============================================
- Hits          79381        6    -79375
- Misses        44061   127002    +82941
+ Partials       5747        0     -5747

Flag
Coverage Δ

custom-integration1
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration1
?

integration2
?

java-11
?

java-21
<0.01% <0.00%> (-61.31%)
:arrow_down:

skip-bytebuffers-false
?

skip-bytebuffers-true
?

temurin
<0.01% <0.00%> (-61.45%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

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

Files
Coverage Δ

...java/org/apache/pinot/segment/spi/V1Constants.java
0.00% <ø> (-12.50%)
:arrow_down:

...apache/pinot/common/function/FunctionRegistry.java
0.00% <0.00%> (-82.61%)
:arrow_down:

...org/apache/pinot/sql/parsers/CalciteSqlParser.java
0.00% <0.00%> (-84.48%)
:arrow_down:

...local/segment/index/datasource/BaseDataSource.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...org/apache/pinot/spi/config/table/FieldConfig.java
0.00% <0.00%> (-51.57%)
:arrow_down:

...ot/common/request/context/predicate/Predicate.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...src/main/java/org/apache/pinot/sql/FilterKind.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ent/local/segment/store/FilePerIndexDirectory.java
0.00% <0.00%> (-93.25%)
:arrow_down:

...pache/pinot/segment/spi/index/StandardIndexes.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...pinot/segment/spi/store/SegmentDirectoryPaths.java
0.00% <0.00%> (-70.28%)
:arrow_down:

... and 30 more

... and 1973 files with indirect coverage changes
:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!

this looks cool!
do you have a design doc? I'm curious how other conditions in the WHERE clause are executed, will it be done before vector search


nchat: 5.3.5 -> 5.4.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/d99kris/nchat/releases.
meta.description for nchat is: Terminal-based chat client with support for Telegram and WhatsApp
meta.homepage for nchat is: https://github.com/d99kris/nchat
meta.changelog for nchat is: https://github.com/d99kris/nchat/releases/tag/v5.4.2
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.4.2 in filename of file in /nix/store/afi8zqs6a841ma2dzqxl07riq0ns7n19-nchat-5.4.2

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

nchat

Instructions to test this update (click to expand)

Either download from the cache:
nix-store -r /nix/store/afi8zqs6a841ma2dzqxl07riq0ns7n19-nchat-5.4.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/8d16a352a956e34427c41e7e53ec9effae353244#nchat

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/afi8zqs6a841ma2dzqxl07riq0ns7n19-nchat-5.4.2
ls -la /nix/store/afi8zqs6a841ma2dzqxl07riq0ns7n19-nchat-5.4.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

nchat

Maintainer pings
cc @luftmensch-luftmensch @sikmir for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368821

x86_64-darwin

:white_check_mark: 1 package built:

nchat


Add random distribution for requests

See if sending requests in a random distribution has better performance by not overloading the network.

Gah sorry. Really not a fan of how git defaults PRs back to the main repo rather than on my fork.


Can't move controls with color

iOS 17.3.1 iPhone 12 max pro
When starting the app and selecting full color, the color wheel button is stuck on the top left of that section and the brightness slider at the top. Can't move either u til I click on the target twice to switch to B/W and back to color.

hi @swOOnkCS , thanks for testing out the app and adding this issue!  Was this for the web version of the app or the native version? I believe I've seen this bug on web for iOS.


⚠ Bofrost.es has degraded performance

In 26b2336, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1613 ms

Resolved: Bofrost.es performance has improved in b03fcd9 after 8 minutes.


python312Packages.aiopvapi: 3.0.2 -> 3.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.aiopvapi is: Python API for the PowerView API
meta.homepage for python312Packages.aiopvapi is: https://github.com/sander76/aio-powerview-api
meta.changelog for python312Packages.aiopvapi is: https://github.com/sander76/aio-powerview-api/releases/tag/v3.1.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.1.0 with grep in /nix/store/47cnr1j9rxwv5nvrapvjrq8pjsdmyrgp-python3.12-aiopvapi-3.1.0
found 3.1.0 in filename of file in /nix/store/47cnr1j9rxwv5nvrapvjrq8pjsdmyrgp-python3.12-aiopvapi-3.1.0

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.hunterdouglas_powerview
python311Packages.aiopvapi
python312Packages.aiopvapi

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/e16feba63068cbea141e4a75237f458612ec6c9f#python312Packages.aiopvapi

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

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

5 packages built:

home-assistant-component-tests.hunterdouglas_powerview
python311Packages.aiopvapi
python311Packages.aiopvapi.dist
python312Packages.aiopvapi
python312Packages.aiopvapi.dist

Maintainer pings
cc @fabaff for testing.

Duplicate of #298062


swagger

with aspnetcore backend,is it possible use swagger to generate proxy api for ngx-admin ,and how to integrate it to ngx-admin

Hi @masterchen! ngx-admin has all data services defined in @core/data. Those services has mocked data hardcoded directly in it. You could remove all data and send an HTTP request to API endpoints instead.


Update Offering Access Action (domain/zone)

Implement a general re-usable action form/component for changing the domain/zone access for offerings.

cc @shwstppr


chore: re-enable file permissions test on darwin

Greetings,
the TestPermissionDenied was disabled on Darwin because it was accessing /root which does not exist on Mac. Well, MacOS is not UNIX I guess.
A "good first issue" ticket was created:
https://github.com/apache/camel-k/issues/2563
I wanted to take a stab on this, however, unfortunately it looks like TestPermissionDenied was already fixed. It now creates a proper temporary file and drops permissions via Chomod. The only thing that was left to be done was to remove the build tags.
And this is exactly what this PR does. Tested on the latest MacOS on Macbook Pro M1, I believe Intel should be the same story.
Have a good one. Cheers.

There is another such test, which now works too
https://github.com/apache/camel-k/blob/main/pkg/cmd/source/util_test.go
Perhaps you'd like to remove those build tags there as well


[CCXDEV-12017] Use Github workflows to run CI tests and update Go version

Description

Update Go version to 1.20 (maximum version supported by go tidy)
Remove Travis CI configuration file and replace to with corresponding Github workflows
Apply goimports on all files (to make golangci-lint pass)
Fix all issues detected by 'revive' linter (to make golangci-lint pass)
Remove whitespace linter as fixing all the files seems to end up in a loop (will look into it in another PR)

Fixes CCXDEV-12107
Type of change

Go version update
CI configuration update

Testing steps
CI (Github workflows) should pass
Checklist

[x] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

I'd use the same Go version as is specified in Dockerfile

makes sense. Going with 1.18 then


Python library LD2410: Error returning values?

Thanks for the library. In my first attempts to understand how it works, I do tests that consist of repeatedly requesting the same information. The result is that every time I request the firmware version, the software returns a different value.
For example:

print(radar.read_firmware_version())
INFO:root:Reading firmware version
V55.126.03031407
print(radar.read_firmware_version())
INFO:root:Reading firmware version
V7.55.05030314
print(radar.read_firmware_version())
INFO:root:Reading firmware version
V5.03.40048040

The same thing happens when I ask it to return the detection parameters:

radar.edit_detection_params(2, 3, 1)
INFO:root:Editing detection parameters
print(radar.read_detection_params())
INFO:root:Reading detection parameters
([148, 66, 112], [206, 10, 116, 200, 255, 55, 7, 20], [3, 5, 0, 0, 2, 148, 66, 206])
print(radar.read_detection_params())
INFO:root:Reading detection parameters
([9, 192, 18], [180, 18, 199, 200, 255, 55, 7, 20], [67, 43, 0, 14, 33, 132, 18, 192])
print(radar.read_detection_params())
INFO:root:Reading detection parameters
([130, 32, 203], [2, 38, 77, 134, 4, 126, 55, 7], [3, 3, 5, 64, 40, 128, 0, 8])

And the same, for example, when I ask for the Bluetooth MAC:

radar.bt_enable()
INFO:root:Enabling Bluetooth
radar.bt_query_mac()
INFO:root:Getting Bluetooth Address
'02:7d:00:00:7d:00'
radar.restart_module()
INFO:root:Restarting module
radar.bt_query_mac()
INFO:root:Getting Bluetooth Address
'00:02:yy:00:00:00'
radar.restart_module()
INFO:root:Restarting module
radar.bt_enable()
INFO:root:Enabling Bluetooth
radar.bt_query_mac()
INFO:root:Getting Bluetooth Address
'00:00:00:00:55:00'

I am sure that I am not fully understanding how the LD2410 library for Python works.
I would appreciate some help.

It's been a while since I've used my own library so I might not be too familiar at this point. It seems that it could be a baud rate mismatch. Thus the values that come out might fluctuate depending on the run.


Rewrite build.py -> release.py and fix bugs

Description
Fixes the outstanding bugs currently in main. Rewritten for readability. Some extra error handling, however there needs to be more robustness as currently the action fails when multiple are executed in a row (such as multiple merges happening in a flurry).
Also need to edit mods.txt modification code to work with new mods.json file.
Fixes #538
Fixes #539
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Local testing:

Zip files match as expected
Tested case when kismetdebugger compiled
Tested case when kismetdebugger not compiled

Release:

Zip files match as expected

Checklist

[x] I have commented my code, particularly in hard-to-understand areas.

Release version mods.txt including the cpp mods that aren't included in release is intended, in case release and dev zips get mixed together without overwriting mods.txt

Release version mods.txt including the cpp mods that aren't included in release is intended, in case release and dev zips get mixed together without overwriting mods.txt

Was not aware that this was the intended behavior - redacting my previous statement that indicated the correct behavior is restored.

https://github.com/UE4SS-RE/RE-UE4SS/issues/543
Adding this for tracking purposes, but the completion of this PR should not qualify as the full fledged fix for #543

release.py's git history is restored now

Need to see the github concurrency setting added to the workflow files + python version locked down before I personally approve. Rest of the comments are nice if you get to them, but not necessarily worth blocking for.

@narknon do you want to do final check of the output files? Release is -124-ge0fe418

Output looks good.  Do we still have the bug with the first line of mods.txt not activating mods? Maybe it was fixed with the json switch?

Output looks good. Do we still have the bug with the first line of mods.txt not activating mods? Maybe it was fixed with the json switch?

I don't know but that's out of scope of this PR anyway.


google-cloud-sdk: Fix build warnings

Description of changes

--replace is deprecated, so switch to --replace-fail
Avoid trying to write logs to read-only home during check phase

Things done
Also added myself to maintainer list.

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I'd prefer commits title in lowercase. But LGTM.

Thanks, I'll keep that in mind for next time :)


Smooth Coloring

Repair the algorithm.

The smooth-coloring algorithm has been fixed.
See https://github.com/hacktheverse/Soap-Bubbles/pull/5.


Move UFFD handling to orchestrator

There is a problem with our current Rust UFFD handler. We will move the handler to orchestrator so we can properly develop and fix it.

After investigating this might not be enough to fix all the Uffd problems. We are checking alternative solutions and then ideally getting rid of the Uffd.


Organizations and Users Must Accept Terms, Create Response Area

Problem
Version 3 has a brand new terms of service. And organizations need to have a geofence in order for the system to work correctly.
Solution
Map

When a user logs in, if their organization does not have a primary work location, then they are prompted to add one in a mandatory modal.
Terms
When a user logs in, if user_users.accepted_terms_timestamp < portal_portals.tos_updated_at, then add a mandatory "Accept Terms and Privacy Policy" button, with links to the TOS and Privacy Policy.

I'm going to mark this complete for now. Admins will be manually adding organization areas as soon as https://github.com/CrisisCleanup/crisiscleanup-3-api/issues/155 is complete.
We can revisit this later if we want to.


[Do not merge] Testing SI new release

Should be testing the branch in this PR
https://github.com/SpikeInterface/spikeinterface/pull/2137

I mean, if the pre-release is equivalent to current SI main, it's covered in the 'dev branch' part of our CI on every run

It is not exactly main as SI uses a specific branch to accrue changes and there might not be a an open PR in neuroconv at that specific point in time or the branch might not run together with the cron.


Fix printing instance name when model name is expected

The utility function expects a model name, but caller supplied model instance name instead. This PR fixes this problem.

The ultimate goal of this PR is to fix L0_model_config, which the model instance name no longer matches the model name when count = 1 after merging https://github.com/triton-inference-server/core/pull/231.


eslint plugin peerDep warnings return

#255 returns :(
Using npm 5.5.1 and latest standard (10.0.3), I am getting peerDep warnings from some eslint plugins:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>- 3.x but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^3.0.0 but none is installed. You must install peer dependencies yourself.

Both plugins are only being pulled in by standard:
$ npm ls eslint-plugin-import
<pkg>
└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>$ npm ls eslint-plugin-react
<pkg>
└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>

Could you give standard@beta a try? We just published it and it updates eslint and other plugins to their latest versions.

@beta fixes it... 👍

🗣 Standard 11 is released! Run npm install standard@latest --save-dev to update to the latest version. This will also update the version in package.json ✨
Changelog: https://github.com/standard/standard/blob/master/CHANGELOG.md#1100---2018-02-18


Urlbar fixes

This has fixes for:

Initial state (previously it would show an empty value on the home page)
Multiple tabs (now the value is set when switching between tabs)

It also includes a simple addition to the navigation e2e test to make sure the value gets set
r? @jsantell

r+ with comments addressed


Using Datagrid, when there's many headers, footer / pagination gets pushed off page

Select one ...  (check one with "x")
[x ] bug
[ ] feature request
[ ] enhancement

Expected behavior
When I see a data-grid on the page with many headers (i.e. more than 10-15 so that the table goes off screen horizontally), I should still be able to paginate between pages without scrolling.
Actual behavior
When I see a data-grid on the page with many headers (i.e. more than 10-15 so that the table goes off screen horizontally), the page footer also gets stretched, so the user doesn't see the pagination information unless they scroll.
Reproduction of behavior
https://plnkr.co/edit/8FuGECUhfHX83iXe2NIn?p=preview
Workaround
In the data-grid.component.css file:
/deep/ .datagrid {
  max-width: 100%;
  .datagrid-table-wrapper {
    overflow: auto;
  }
  .datagrid-head, .datagrid-body {
    display: table;
    width: 100%;
  }
}

The solution becomes:

And seems to work for us!

Angular version: 4.4.5

Clarity version:
Latest version

OS and version:
MacOSX latest

Browser: [all]

The workaround above causes new issues (at least with 0.10.14). We get unnecessary horizontal scrollbar as grid gets too wide many times. e.g. if you have an 'expand' column, then grid gets that columns width extra wide. There are other cases too, but this one most easy to reproduce as it always happen.
The empty grid text is also no longer vertically centered. Small bug, but it's another side effect.
We got these two issues reported as bugs and with that can no longer use the workaround. I really hope there is another solution as most of our grids gets their pager/item number and vertical scrollbar hidden with the current Clarity.

Another workaround that did the trick for me.
  clr-datagrid {

    height: auto !important;
    margin-bottom: 1.5rem;
    position: relative;

    clr-dg-footer {
      position: absolute;
      bottom: -1.5rem;
      left: 0;
      right: 0;
    }
}

Fixed by #2670.


Do you have a suitable chart component?

Bar / Line chart。。。

I recommend this one:apexcharts / Blazor-ApexCharts

cool,tks.


executeMobile 'scroll'

@imurchie, please see TODO:
https://github.com/appium/appium-ios-driver/blob/master/lib/commands/execute.js#L71-L79
AFAIKT from https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/touch-actions.md scroll is the only supported command - please confirm.

@imurchie @scottdixon "mobile: swipe" works fine for me in current appium version.May i know why there is no support for the same in appium-ios-driver. Please clarify. If there could be a support shall i look into this?

All of the mobile commands other than mobile: scroll were deprecated in 1.4 and removed in 1.5. The touch action API is better for these actions.


fix viper loading and updated docker compose

Codecov Report

Merging #36 into master will decrease coverage by 0.13%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master      #36      +/-   ##
==========================================
- Coverage   60.76%   60.63%   -0.14%
==========================================
  Files          11       11
  Lines         599      602       +3
==========================================
+ Hits          364      365       +1
- Misses        212      213       +1
- Partials       23       24       +1

Impacted Files
Coverage Δ

cipher/viper.go
75% <50%> (-9.62%)
:arrow_down:

Continue to review full report at Codecov.

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


Add SSR support, init only on client

Server side rendering ends up with following error:
ReferenceError: addEventListener is not defined
    at eval (webpack:///./node_modules/first-input-delay/src/first-input-delay.js?:179:4)
    at Object../node_modules/first-input-delay/src/first-input-delay.js (<anonymous>:12488:1)
    at __webpack_require__ (<anonymous>:20:30)
    at Module.eval (webpack:///./node_modules/perfume.js/dist/perfume.es5.min.js?:2:122)

Could you please provide some example configs how to get it running only on client side?

Have you tried by checking the Production Environment? What SSR library do you use? I can try to create a mini demo for it.

Ciao, and sorry for this late reply.
Also, we have the buffered flag enabled which will help for Server Side Rendering and Google Tag Manager issues. 🤩
With V3 we will drop the support for Paint Timing and First Input Delay polyfill and only serve the results from the Vanilla API 🍾
You can already test it with Perfume.js v3.0.0-rc.5
I am going to have v3 under monitoring before release it officially, in case of possible cross browser bugs.


chore: update RHOAS Go SDK to match pattern

This should resolve https://github.com/redhat-developer/app-services-cli/issues/1049

LEt's try it (look valid but not sure it will work)


Library beta: Missing support for Node 10, 12

Search terms
Unexpected token ?
Expected Behavior
TypeDoc should work on the minimum version of node specified in package.json
Actual Behavior
Crashes due to incorrect target setting in tsconfig.json
I broke this because after checking https://node.green/, it seemed that I ought to be able to use bigints. However TS doesn't support bigints unless target is set to ES2020... not thinking about optional chaining, I set that. Will fix tomorrow.
Environment

Typedoc version: 0.20.0-beta.5
TypeScript version: 4.0.3
Node.js version: 10.x / 12.x
OS: Windows

Fixed by 671e6d3ece5efa4b3296aec8a7140f1872034154


Respect $XDG_CACHE_HOME for the DB

On Linux, it's common to follow the XDG base directory spec which specifies

$XDG_CACHE_HOME defines the base directory relative to which user-specific non-essential data files should be stored. If $XDG_CACHE_HOME is either not set or empty, a default equal to $HOME/.cache should be used.

Which should change the fallback at
https://github.com/mgax/minivirt/blob/2e6e5f47a0d1a674bbb0ac4bef1b5112614e77f0/minivirt/cli.py#L21
to query $XDG_CACHE_HOME and fall back to the original then.
On macOS there's probably something similar, though I'm not really aware of the specs and ecosystem around there.
On a related note, I'm not sure if the cache folder is the best location for the DB. It does contain essential data, so $XDG_DATA_HOME might fit better (breaking change).

Yep, totally agree! The current state of things comes from "let's have something that functions, clean it up later".


[VS Code] Share Workspaces

It doesn't appear that Live Share supports sharing workspaces of multiple projects. It seems like it only shares the originating project, and omits the other ones.
Our solution is to open a new VSCode window, open each one individually, and create multiple shared sessions. It's kinda painful at the moment.

@ajwhite Hey! We’re actually finishing up support for workspaces right now 👍 This is one of our most frequent requests, so we’re hoping to get an update out in the next week or so that addresses this.

Hey old friend 👋
That's awesome! I tried to search for an existing issue, but didn't find one. I thought it had to have been requested by someone else. Cool stuff

Much rather consolidate 👍
closing, and looking forward to it 🎉


Not showing after webkit view played

Hi guys,
After few tried I understood that SubtleVolume is not working if a video has been played through the WebKit view (WKWebView).
So, for reproduce the issue, load a web page (YouTube), try to increase or decrease the volume (everything is working for what about the SubtleVolume) then play a video, come back and no custom controls anymore.

Ciao Pietro,
did you try calling resume after the webkit video played?

Ciao Andrea,
Calling resume everything is working perfectly :D
I’ll let you know if there will be other cases in which it will not be displayed, thank you so much!
--
Best regards,
Pietro Messineo
On 5 aprile 2019 a 16:34:04, Andrea Mazzini (notifications<EMAIL_ADDRESS>scritto:
Ciao Pietro,
did you try calling resume after the webkit video played?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/andreamazz/SubtleVolume/issues/25#issuecomment-480298260, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AI8j4ModorM8YPtFf10vqLVnr5_5BEnaks5vd17agaJpZM4ce4uj.


fix: issue 784 router update start new server listening

Fix issue where router update creates a new server and replaces the old server but doesn't start the new server listening
Add config hot-reload to router when using a local config file (using the router update fix)
Motivation and Context
Fix corrects a mismatch between the documentation and implementation for router updating
Addition for hot-reload improves developer experience when running with a local config file
TODO

[ ] Tests or benchmark included
[ ] Documentation is changed or added on https://app.gitbook.com/
[X] PR title must follow conventional-commit-standard

https://github.com/wundergraph/cosmo/issues/784

Hi @wainglaister,
Thanks so much for your contribution! I've updated the comments for the methods. Unfortunately, we can't merge the PR just yet. It needs tests, and the watcher functionality should be properly abstracted into a package. Given this, the priority of this feature is quite low at the moment, and we don't have the resources to guide you through these changes or to ensure that this feature is working as expected.
To prevent such situations in the future, we recommend creating an issue first. Thank you!

As described earlier in comment. No action is left here.


Messages received while recent messages load are grey and with no badges

Describe the bug
While the recent messages load (or, in other words, before they are loaded in) messages received via the normal IRC connection are missing color and badges.
To Reproduce

Open chatterino2, and look at a fast chat around the time of the connect.
Expected behavior

Messages load in with color and badges.
Screenshots

Chatterino version
2.1.0 (21.08.2019 59b3242-1) which is equivalent to commit c81e1929c9dffab64f58e5e676dc5623c14036b0
Additional context

I can't reproduce exactly. The color of the names were not changing to grey, but there was duplicate messages and badges were not properly loading. Emotes seem to be working properly as well (even sub emotes). In your image personal sub emotes don't seem to load (nymnHmm).

Can confirm, this is fixed by #1232


Fix: unmanaged Styles

Implemented changes
This PR handles the issue described in  #587. The idea is that sorting the ol layers by removing and re-adding them will not actually remove the connected interactions.
@silvester-pari is this how the desired behaviour?

Screenshots/Videos

Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I have added a test related to this feature/fix
[ ] For new features: I have created a story showcasing this new feature
[x] All checks have passed
[x] The PR title follows conventional commit style and reflects the type of change (major/minor/patch, breaking)
[x] The PR title describes the change within this element (each merged PR equals one entry in the element's changelog!)

That's true, I think this might also be the most practical solution from a cartographic standpoint for most real-world problems. I'm thinking that when changing the layer order, the selection layer most often is not dragged below a full opaque image-baselayer, but most likely underneath overlay layers or border layers, where the geometry of the selected feature "is expected" to stay on top


Fix issue with workflow on forks

This allows the add-to-project workflow to work on forks.

On reopened would a duplicate issue be created?

This automation doesn't create issues, it just adds them to the project, and an issue cannot be added twice. See this test issue if you want to try it out yourself.


Composer installer not found

Issue Type

Bug Report / Support Request

Your Environment
Vagrant 2.2.3

No vboxmanage and ansible not found
Your OS

Windows (10)

Full console output
TASK [geerlingguy.composer : Set php_executable variable to a default if not defined.] ***
skipping: [project-lvho-st]

TASK [geerlingguy.composer : Check if Composer is installed.] ******************
ok: [project-lvho-st]

TASK [geerlingguy.composer : Get Composer installer signature.] ****************
ok: [project-lvho-st]

TASK [geerlingguy.composer : Download Composer installer.] *********************
changed: [project-lvho-st]

TASK [geerlingguy.composer : Run Composer installer.] **************************
fatal: [project-lvho-st]: FAILED! => {"changed": false, "cmd": "php composer-installer.php", "msg": "[Errno 2] No such file or directory", "rc": 2}

Summary
Can't up vagrant box, it fatally ends with being unable to install composer properly

Can you try vagrant destroy -f (to delete the VM) then vagrant up again to try creating it again? Sometimes network issues may cause the composer installer download to fail or have an issue... maybe that's what happened here.

I did that (but without -f flag) multiple times and it could not bring it up successfully.
First time, I installed drupal-vm, I did it with empty drupal folder, just to make sure that installation does not ruin my drupal code.
Maybe, it has to do with the fact, that I did not remove it now, and I have it inside existing drupal installation that is made via https://github.com/drupal-composer/drupal-project previously?


Does the substrate runtime use wasmi?

I'm interested in wasm-based blockchain VM, and want to know wasmi's mechasim.
Does the substrate runtime use wasmi? Are there any related docs?

where can I find these docs? I wish I could write a tutorial to introduce  substrate runtime to the public. Thanks.


Unwanted 20 kHz lowpass filtering occuring on Raspberry Pi

When recording with a Raspberry Pi, frequencies above 20 kHz are greatly attenuated.

When recording from a Windows laptop, high frequencies are not attenuated.

The spectra pictured above were recorded with the same Audiomoth Dev 1.0.1 device running AudioMoth-USB-Microphone firmware 1.3.1, with similar environmental noise (consistent 32 kHz noise, me snapping my fingers, and whistling). Data were recorded at 250,000 samples per second. Both the Windows PC and the Raspberry Pi were using Release 1.0.0 of this repository (AudioMothLiveSetup1.0.0.msi and AudioMothLiveBuild1.0.0.sh, respectively).
Data were recorded on an MSI P65 laptop running Windows 11 Pro with the following command:
AudioMoth-Live.exe 250000 autosave 1 C:\Users\username\Desktop\data
Data were recorded on a Raspberry Pi 4B 2GB device running Raspberry Pi OS Bookworm with the following command:
AudioMoth-Live 250000 autosave 1 ~
The desired unfiltered data is also obtained when using the AudioMoth-Live-App on the Windows PC, or when using the Audiomoth as a standalone SD logger (basic firmware 1.10.1).
This issue has been replicated across many Audiomoth Dev 1.0.1 devices and many Raspberry Pi 4b devices.

Update: I tried recorded with the AudioMoth as a generic USB mic using arecord, and the filtering issue is still present. So, the issue seems to be inherent to the Raspberry Pi.

Update: I recorded to a computer running Linux Mint with arecord, and the 20 kHz filtering is not occurring. So, the issue isn't inherent to Debian OS.

I think this is an OS issue with the changes in Bookworm. Previously Raspberry Pi OS used PulseAudio on top of Linux ALSA for sound. Bookworm seems to have introduced the use of PipeWire (https://pipewire.org) for sound which may have broken the app. I'll investigate more tomorrow. Hopefully, there will be an easy fix.

I managed to reproduce the same filtering you are seeing and confirm that it is caused by PipeWire in Bookworm. You can confirm the Raspberry Pi OS that is installed by:

cat /etc/os-release

There are two fixes. You can enter the Raspberry Pi configuration and switch back to using PulseAudio.

sudo raspi-config

Enter '6 Advanced Options' and then 'A7 Audio Config' and switch from '2 PipeWire' to '1 PulseAudio'. Then select '' to save the change and restart.
Or, you can change the PipeWire configuration to allow other sample rates.

sudo nano /usr/share/pipewire/pipewire.conf

Uncomment and change the two lines from:
#default.clock.rate                  = [ 48000]
#default.clock.allowed-rates = [ 48000 ]
to:
default.clock.rate                  = [ 48000]
default.clock.allowed-rates = [ 8000, 16000, 32000, 48000, 96000, 192000, 250000, 384000 ]
Both fixes work for me. I'll confirm on another couple of machines and then update the instructions.

Both fixes also worked for me (tested 250 kHz and 384 kHz sampling rates).
I read that PipeWire is supposed to be more performant than PulseAudio, but in my tests PipeWire seemed to have slightly more CPU usage. But, both were low enough it doesn't really matter (2% vs 3% with 384 kHz sampling).
Thanks so much for the solutions! And thanks for the speedy reply. We are starting experiments on Monday, and I was starting to get stressed.

Great. I'll update the instructions and close the issue.


fixed 4025 - allow setting background via name

Issue: https://github.com/storybooks/storybook/issues/4025
What I did
I updated the backgrounds addon so I can choose my background by name as well and not just by value.
How to test
Is this testable with Jest or Chromatic screenshots?
Does this need a new example in the kitchen sink apps?
Does this need an update to the documentation? Yes.
If you run a storybook which includes the backgrounds addon you can set ?background={valueOrName} to choose the background
If your answer is yes to any of these, please make sure to include it in your PR.
For maintainers only: Please tag your pull request with at least one of the following:
["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

Can you please merge from master, it should fix all the CI things

There is also a linter warning

I wonder why I haven't seen that before 🤔 Should be fixed now.


Fetch jbullet from jcenter rather than updates.jmonkeyengine.org

Sometimes, even the best websites aren't available, like for example updates.jmonkeyengine.org.
Then gradle build does this:
FAILURE: Build failed with an exception.

* Where:

Build file 'C:\Temp\jme\test\sdk\build.gradle' line: 129

* What went wrong:

A problem occurred evaluating root project 'sdk'.

> Could not resolve all dependencies for configuration ':corelibs'.

   > Could not resolve org.jmonkeyengine:jme3-jbullet:3.1.0-alpha3.

     Required by:

         :sdk:unspecified

      > Could not resolve org.jmonkeyengine:jme3-jbullet:3.1.0-alpha3.

         > Could not get resource 'http://updates.jmonkeyengine.org/maven/org/jm

onkeyengine/jme3-jbullet/3.1.0-alpha3/jme3-jbullet-3.1.0-alpha3.pom'.

            > Could not GET 'http://updates.jmonkeyengine.org/maven/org/jmonkeye

ngine/jme3-jbullet/3.1.0-alpha3/jme3-jbullet-3.1.0-alpha3.pom'.

               > updates.jmonkeyengine.org:80 failed to respond

But wait, jcenter has it covered!
https://bintray.com/jmonkeyengine/org.jmonkeyengine/jme3-jbullet/view
So is probably better to link there for the dependency.

Apparently, jbullet isn't on jcenter :sob:


🚀 Feature: Run container as non root user

🔖 Feature description
Add the posibility to run the server as non root user, like linuxserver.io images do
🎤 Pitch
It would be a great improvement to run the server as non root user to improve system security

Good idea but I don't know how to do this :( If someone is an expert in Docker feel free to create a PR.

I concur this would be a good idea. Some code has to interpret UID=XXXX GID=XXX parameters in the YML file.

Thanks to @adriadam10 this will be released in the next release.

Released in v0.18.0.


Fix hardcoced react dependencies from unpkg.com

Those URLs are returning 404. Bringing them into the node dependencies and importing from there instead.
The unavailability of these resources, which was impacting the game today.

I'm not sure about all the changes in the lock file though. Please feel free to edit that if it's introducing any issues.
Worth noting that this may not fix things depending on how you're packaging the dependencies before deploying, but it does fix it locally.

Hmm, I don't think this is the route we want to go right now. Usually a CDN has a number of advantages for loading these files, being located closer to the user, it has a favorable network path for faster download speed.
At some point we may bring in a bundler like webpack, but for now I'll move these links to CDNJS which should be more reliable

My thinking hehind this change was to remove a 3rd party dependency, even if it'sjust a temporary measure, or a middle step for something else, because these were clearly impacting people when they became unavailable.
But yes, you make a fair point, a CDN makes way more sense. I'm closing this.