[SPARK-10959] [PYSPARK] StreamingLogisticRegressionWithSGD does not t…

…rain with given regParam and StreamingLinearRegressionWithSGD intercept param is not in correct position.
regParam was being passed into the StreamingLogisticRegressionWithSGD constructor, but not transferred to the call for model training. The param is added as a named argument to the call.  For StreamingLinearRegressionWithSGC the intercept parameter was not in the correct position and was being passed in as the regularization value.

Merged build triggered.

Merged build started.

Test build #43614 has started for   PR 9087 at commit e97e691.

Test build #43614 has finished for   PR 9087 at commit e97e691.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

test this please

Merged build triggered.

Merged build started.

Test build #43617 has started for   PR 9087 at commit 8b4eb08.

Test build #43617 has finished for   PR 9087 at commit 8b4eb08.

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

Merged build finished. Test PASSed.

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

Merged into branch-1.5. Could you close this JIRA manually?


5 Create a time-series predictor

Recommended Strategy 5
Create a time-series predictor of the danger level using this tutorial. It predicts the price of avocados over time using date and volume of avocados sold. In your case, volume of avocados will actually be your predictors, and danger rating, now a continuous value of 1.0 - 5.0, is a simple drop-in for avocado price.
This may be helpful, or may be too difficult to implement. If too difficult, come up with another model we can use.

I'm having issues following the code examples here, maybe someone else can take a look at it?

If we can't figure this out, try #74, #75


Included the .mdx file extension in the 2024-hackathon blog

Similar to the 2023 blog, the .mdx extension was missing in the 2024-hackathon file.
(Please ignore the commit "d0632fa" and "2771ea7", I'm still figuring out how to use this :/ )

Going to close this because it's currently live on the site.
Holding true to the mantra: "If it ain't broken, don't fix it."


ArchGDAL randomly infers wrong file type

I was unmixing a bunch of ISOFIT generated reflectance images and randomly on a single image got the following error:
ERROR: GDALError (CE_Failure, code 1):
	Driver ARCGEN is considered for removal in GDAL 3.5. You are invited to convert any dataset in that format to another more common one. If you need this driver in future GDAL versions, create a ticket at https://github.com/OSGeo/gdal (look first for an existing one first) to explain how critical it is for you (but the GDAL project may still remove it), and to enable it now, set the GDAL_ENABLE_DEPRECATED_DRIVER_ARCGEN configuration option / environment variable to YES.

It seems that sometimes the wrong file type is inferred. I was able to open the image with no problem with gdalinfo, QGIS and custom code. Weirdly the corresponding uncertainty image opened just fine with ArchGDAL.read
Limiting the types of drivers that can be used to all calls of ArchGDAL.read() and ArchGDAL.readraster() fixed the error:
ArchGDAL.read(FILE_NAME,alloweddrivers =["ENVI"])

Interesting, thanks for reporting.  I assume that repeat runs on the same image continues to give this error?  If so, any chance you could send me a copy of that input dataset for further testing?

Yeah, repeat runs resulted in the same error, as did trying to load the image with ArchGDAL in the Julia console, it only worked after specifying drivers. I did do some more testing though on two other machines and only got the error on 1 of the machines, so in total 2 of 3 tested machines didn't work, so maybe its related to underlying dependencies? In any case I'll share the offending image if you want test yourself.


mavm provided an account without cross account role

Looks like a rare condition in the puppeteer code which clicks the role: https://github.com/superwerker/mavm/blob/144e6fb7aa5516d26901e04e64b9b2263eb308d4/code/create.js#L518-L550
happened with account<PHONE_NUMBER>28
possible solution: check if cross account role is working, would probably also fix #16 #17
Count: 3

fixed with f27b02103d850ef7836b74f92381465412dc542a


Update codeowners list

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

@jsquire Do we want to remove the Service Attention Mention Bot Rules that correspond to some of the deleted lines here?


Sometimes the device is not connecting

Hey,
Sometimes the device is not connecting and also multiple devices are not scanning/connecting.
I have also tried esptouch_flutter 1.1.0-androidv2, but the result is the same.
esptouch_flutter: ^1.0.0 and esptouch_flutter 1.1.0-androidv2
Flutter SDK Version- 2.16.1
Android Version- 10/11/12
Note-: Can you please provide some updates because we are facing that issue in our live application?

@kcs-dileeppatel we haven't planned an update on the project at the moment. What problems are you exactly facing? Any errors? What's your application / environment look like?
As it's an open sourced library, we are happy to review changes you contribute to improve the project.


Fix interpolate example on Android

Since we allow more types to be handled, null is no loner casting to 0 on android

... has figured out that this also fixes
https://github.com/kmagiera/react-native-reanimated/issues/112

I also suggest another solution:
https://github.com/kmagiera/react-native-reanimated/pull/114


Trace server

moves tracing to a web socket server to avoid freezing vscode during long traces.
Outstanding issues before merge:

needs testing
State needs to be cleared when a new trace is run.
Need to handle disconnects
Has not been tried with multiple vscode windows

persistent storage was removed.  The plan is for the server to manage a sqlite database per project.  There are build and install challenges to overcome.

Also performs the trace using ts lib. This allows us to pull additional information that is not in normal traces.


New version breaks base_url (edge case)

Hi,
I am using a self hosted NIM behind a reverse proxy, meaning to access the LLM, I use the following base URL: http://{host}/llm/v1.
When using ChatNVIDIA, using this base URL worked until version 0.2.1, where the URL is now expected to have no trailing path.
The error is as follows:
Base URL path is not recognized. Expected format is: http://host:port (type=value_error).
In my case, it is not possible to use this format.
For clarity's sake, my code looks like the following:
from langchain_nvidia_ai_endpoints import ChatNVIDIA
llm = ChatNVIDIA(
            base_url=f"http://{IP}/llm/v1",
            model=model,
        )

pip freeze
...
langchain-nvidia-ai-endpoints==0.2.1
...

The error originates from _common.py, line 147, after the validation fails.

Hi @jami3f,
Thanks for reaching out, we on it and will update you as soon as it's fixed.

Hi,
The issue is fixed in yesterdays package release: 0.2.2, let me know if issue persists.

I believe the additional necessary portions of the path get removed. In @renambot's case /llama would need to be reinserted before /v1 in the URL that is used to query the NIM.


YAML Parse error when using caNamespaces: ["*"]

Preflight Checklist

[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
[X] I am not looking for support or already pursued the available support channels without success.
[X] I agree to follow the Code of Conduct.

Vault Helm Chart Version
1.20.1
Bank-Vaults Version
1.30.0
Kubernetes Version
1.27.0
Kubernetes Distribution/Provisioner
k3s
Expected Behavior
When using,
values:
  tls:
    caNamespaces:
    - "*"

Alongside the vault helm chart as part of it's values.yaml, the helm install/upgrade will succeed and apply the tls secrets to all namespaces
Actual Behavior
When using,
values:
  tls:
    caNamespaces:
    - "*"

Alongside the vault helm chart as part of it's values.yaml, I'm getting a YAML parse error

Helm upgrade failed: YAML parse error on vault/templates/secret.yaml: error converting YAML to JSON: yaml: line 5: did not find expected alphabetic or numeric character Last Helm logs: preparing upgrade for vault resetting values to the chart's original version

Steps To Reproduce
No response
Logs
No response
Additional Information
I'm using Flux in combination with it's HelmRelease CRD, here's the full YAML
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: vault
spec:
  interval: 30m
  suspend: false
  upgrade:
    remediation:
      # Number of retries that should be attempted on failures before bailing, a negative integer equals to unlimited retries
      retries: 20
  chart:
    spec:
      chart: vault
      version: "1.x"
      sourceRef:
        kind: HelmRepository
        name: bank-vaults-repo
      interval: 12h
  # https://github.com/bank-vaults/vault-helm-chart/blob/main/vault/values.yaml
  values:
    tls:
      caNamespaces:
      - "*"
    unsealer:
      args: ["--mode", "k8s", "--k8s-secret-namespace", "vault", "--k8s-secret-name", "bank-vaults"]
      metrics:
        enabled: true
        serviceMonitor:
          enabled: true
    serviceAccount:
      name: "vault"
    metrics:
      enabled: true
      serviceMonitor:
        enabled: true
    vault:
      externalConfig:
        auth:
        - type: kubernetes
          roles:
          # Allow every pod in the default namespace to use the secret kv store
          - name: default
            bound_service_account_names: "*"
            bound_service_account_namespaces: "*"
            policies:
            - allow_secrets

Thanks for reporting this @Twinki14, we will look into it


In filters pane, Counts don't sort properly

System information:

Operating system (distribution) and version: Windows 10
DBeaver version: 21.0.1
Additional extensions

Connection specification:

Database name and version: MySQL
Driver name
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
When you sort by the "Count" column added in Issue #10961 (i.e. click on the column name), it sorts like a string/text column instead of numerically.

Also, please add locale-specific thousands separators.
Steps to reproduce, if exist:

Click the Filter button on a column
In the resulting filter pane, click the "Count" column to sort by that column

Include any warning/errors/backtraces from the logs

thanks for the report

Fixed and implemented:

The screenshot shown there always worked fine. Can you do a test with numbers of varying orders of magnitude (like 9. 14, 115, etc.)? Thanks!

Oh, sure, I wanted to show formatting :)

This looks perfect, thank you!

verified


AMQPMessage::setMessage error

Hi!
Have a simple error while processed Message body (AMQPMessage::setMessage).
At start & if length this->data > length you have undefined stay \0 in the this->data (corrupt body).
Instead :
line 30:
this->data = (char*)malloc(length);
memcpy(this->data,data,length);
I offer:
this->data = (char*)malloc(length+1);
this->data[length]='\0';
if (!this->data) {
throw AMQPException("cannot alocate memory for data");
}
strncpy(this->data,data,length);
wbr,
buy.

thanks


Create Justification Class in Java client

To address issue 280

In java, we also need the validation similar to Golang: https://github.com/abcxyz/lumberjack/blob/main/clients/go/apis/v1alpha1/config.go#L104-L108

Can you follow https://github.com/kubeflow/pipelines/blob/master/CONTRIBUTING.md#pull-request-title-convention to update the title of this PR?

Can you follow<EMAIL_ADDRESS>to update the title of this PR?

This is canonical version: https://www.conventionalcommits.org/en/v1.0.0/#summary


Why does this cmdlet dont have any implementation information

No Description or example... doesn't exist in SPO module

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

ID: fbaba231-7df2-8f4e-a761-0a9b395c5665
Version Independent ID: 5a7bc4be-bf47-e722-9be6-70b58dd0da5c
Content: Set-SPO365LinkSettings (sharepoint-online)
Content Source: sharepoint/sharepoint-ps/sharepoint-online/Set-SPO365LinkSettings.md
Service: sharepoint-powershell
Product: unspecified
GitHub Login: @techwriter40
Microsoft Alias: kirks

@VesaJuvonen for your review. thanks

@Techwriter40 Updated in #1068.

This is SP server-side cmdlet, so removed from the SPO side.


Merge Master into VentureLab Branch

We need to merge the new master into the VentureLab branch so that they can use the website, and we need the url venturelab.keep.id to work ASAP because we are beta testing with them soon, and we would like to collect funding.

this might take a long time....

@MelindaCardenas after you finish PFP can you look into this?
I am thinking that in the future, we use an internationalization software to swap out the words easily


feat: integrate lyon campus

Special issue : Campus integration
Integrate the campus of lyon on s42
🎁 If you come from https://github.com/42atomys/stud42/labels/good first issue or https://github.com/42atomys/stud42/labels/help wanted : How to add a campus on s42
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi,
just here to say that Iḿ willing to do the job. i'll go read the process for contributing and work on it in my spare time

Hi @gd-harco, noted !
We currently have a lot of issues with devcontainers.. so don't be afraid to ping me to test / validate your contribution

Hi @42atomys,
sorry to bother you. The map is created, but I couldn't commit it. I'm getting a weird error message that I guess is coming from the integrated linter. Is it related to the dev container issue you wee mentioning earlier ?
Here is the error message I get when trying "git commit" while inside the dev container
file:///usr/local/share/nvm/versions/node/v20.18.0/lib/node_modules/@commitlint/cli/lib/cli.js:132
        throw err;
        ^

Error [ERR_UNSUPPORTED_DIR_IMPORT]: Directory import '/usr/local/share/nvm/versions/node/v20.18.0/lib/node_modules/@commitlint/config-conventional' is not supported resolving ES modules imported from /usr/local/share/nvm/versions/node/v20.18.0/lib/node_modules/<EMAIL_ADDRESS>Did you mean to import<EMAIL_ADDRESS>    at finalizeResolution (node:internal/modules/esm/resolve:259:11)
    at moduleResolve (node:internal/modules/esm/resolve:933:10)
    at defaultResolve (node:internal/modules/esm/resolve:1169:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:542:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:510:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:239:38)
    at ModuleLoader.import (node:internal/modules/esm/loader:472:34)
    at defaultImportModuleDynamicallyForModule (node:internal/modules/esm/utils:214:31)
    at importModuleDynamicallyCallback (node:internal/modules/esm/utils:253:12)
    at dynamicImport (file:///usr/local/share/nvm/versions/node/v20.18.0/lib/node_modules/@commitlint/cli/node_modules/@commitlint/resolve-extends/lib/index.js:10:88) {
  code: 'ERR_UNSUPPORTED_DIR_IMPORT',
  url: 'file:///usr/local/share/nvm/versions/node/v20.18.0/lib/node_modules/@commitlint/config-conventional'
}

Node.js v20.18.0

It appears that I can't link the PR to the issue, it's number #640.


Porcupine1, custom wake word

Hi Mike,
Thank you so much for your amazing work !!!
French HA user for 3 years, would it be possible to use a french custom wake word generated with the free picovoice platform in your porcupine1 addon like  it is possible with openwakeword?
Have a good day

Thanks!
Correct me if I'm wrong, but I believe you can only create custom wake words with porcupine v2 these days. I didn't include a v2 option because it requires API keys, and we found that re-building the add-on too many times would require creating a new account with Picovoice.
I'm also in the process of creating a snowboy add-on that will allow for custom wake words to be created locally, so if you can wait just a bit longer that might be a good option :slightly_smiling_face:

Thank you for your reply.
You're right, picovoice's custom wake words require an api key. I used it on android devices with rhasspy mobile and a french custom wake word.
I'm taking note of your future add-on with snowboy (seasalt-ai for generate ?) and I'll follow the news about it.
There is no urgency because everything works wonderfully despite my pitiful English accent (convert rpi with seeed respeaker 4 Hat  from rhasspy to home assistant satellite and also use assit microphone with small conf mic)
I prefer to use the English wakeword because the French are ridiculous !!!
It's a little more complicated for my wife 😉
Once again, a big thank  for your work, and your investment since Rhasspy.

The snowboy add-on is now available: https://github.com/rhasspy/hassio-addons/tree/master/snowboy
Here is how to train custom wake words: https://github.com/rhasspy/hassio-addons/blob/master/snowboy/DOCS.md#custom-wake-words

So fast !!! You are amazing Mike !
Tanks ( for my wife)  😁
I try this tomorrow .
Good evening

Hello
Just tested with 2 French accent wakewords, and it's working fine.
You are the best 👍👏
Thanks


Fix network with -b none

Don't AllocateNetwork when network is disabled
Don't createNetwork in execdriver when network is disabled

Fix #13436

This fix worked for me

LGTM

LGTM

LGTM


fix: compat between lit-element 2.4.0 & 2.5.0

2.5.0 has a compatibility change to lit 1 for lit 2. Since we were mid-migration to Lit 2, we doubled up on these efforts and caused an infinite loop.
cc: @dfreedm @bicknellr

Git diff gore


fix(index): fallback to console.log if console.debug does not exist

Proposed fix for #10.

Closing this since we've got this in the pal now.


winget upgrade <given app> should not fail if already updated

Brief description of your issue
Previously this command would not fail (i.e. exit with a non 0 code), but since latest version of WinGet it does.
And I believe that's the correct behavior. That's how apt-get upgrade also works, and simplify things by a lot during scripting.
This unfortunately breaks one of my scripts too, which winget upgrade to ensure an app was up to date:
https://github.com/felipecrs/dotfiles/blob/master/home/dot_local/bin/executable_full-upgrade.tmpl#L79
Steps to reproduce
winget install Microsoft.VisualStudioCode

winget upgrade Microsoft.VisualStudioCode

echo $?

# will output False rather than True

Expected behavior
To not fail, as it used to be.
Actual behavior
Failing where it shouldn't.
Environment
~ ❯ winget --info                                                                                00:29:16
Windows Package Manager (Preview) v1.6.2291-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22631.2191
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.21.2291.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Enabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

Ok, after checking some things, it looks like this was always the behavior of winget.
I would still say it would be a nice thing to have a zero exit code though.

I believe WinGet is handing back the return code from the installer. I'd be concerned if we handed back a zero and the "upgrade" actually failed.
We do have the "repair" slated for MSIX and MSI based installers. Maybe we can look at the behavior when we imlement:

#148

I believe WinGet is handing back the return code from the installer. I'd be concerned if we handed back a zero and the "upgrade" actually failed.
We do have the "repair" slated for MSIX and MSI based installers. Maybe we can look at the behavior when we imlement:

Repair an App that is behaving badly #148

@denelon I don't think that's the case... I don't see the installer being downloaded nor invoked:
https://github.com/microsoft/winget-cli/assets/29582865/b7879bc3-438c-4595-9378-91fa1406f2a3

Not a perfect solution, but my PowerShell scripts scrape the No packages found matching input criteria response. Could the same be done in your bash scripts?

@stephengillie, I'd have to try to match No packages found matching input criteria and No available upgrade found, maybe also No newer package versions are available from the configured sources.
Thanks for the workaround, but I believe we can probably fix this at the root.


[WIP] Simplify path planner implementation

This PR aims to simplify the design patterns used in the implementation of path planners.
In addition, this PR will also add reset methods to the planners where it is missing, to enable recomputing the grid or roadmap to account for dynamic state of the world such as door opening and closing.
TODO:

[ ]  A-star
[ ]  RRT
[ ] PRM
[ ] WorldGraph

I've decided to implement this for the next release so I'll take this over in https://github.com/sea-bass/pyrobosim/pull/241 -- tagged you for review.


<EMAIL_ADDRESS>dependent on deprecated<EMAIL_ADDRESS>

<EMAIL_ADDRESS>dependent on deprecated<EMAIL_ADDRESS>

This has been fixed in newer releases.


feature(Select): add a 'renderItem' prop similar to Autocomplete

🚀 Feature Proposal
A clear and concise description of what the feature is.
add a a 'renderItem' method to a Select component
Motivation
for a very similar reason we use renderItem in autocomplete , i think most of us would be happy to add a visual icon to the list component shown on the the dropdown/select
Please outline the motivation for the proposal.
Example
Please provide an example for how this feature would be used.

Hi @kaminskypavel
This will be landed in v5, you can see the new syntax for these components here

@artyorsh thanks for the clarification! 🎉


Add events for account and network change

This was embarrassingly easy for how long we didn't do it.

There's an issue:
On account change, the store is updated twice:

Once with an undefined account
Once with the new account

This would probably be unexpected behavior if you just wanted to know that a change was happening, so I'd like to fix that.
That said, this is still probably better than what every dev does today to detect account changes.

Note that currently MetaMask reloads web3-touching pages on network change, but we've also said we were going to stop doing that, and rolling in a network change event is a good precursor to that breaking change.


panicked when working  with tokio async

when use reqwest to request schema registry with tokio async ,like my code below in warp main thread or use tokio::spawn to create a async block will exit
use warp::Filter;
use schema_registry_converter::schema_registry::{SrSettings};

#[tokio::main]
async fn main() {
     let hello = warp::path!("hello" / String)
        .map(|name| format!("Hello, {}!", name));
     let sr_settings = SrSettings::new(String::from("http://localhost:8081/"));

    warp::serve(hello)
        .run(([127, 0, 0, 1], 3030))
        .await;
}

thread 'main' panicked at 'Cannot drop a runtime in a context where blocking is not allowed. This happens when a runtime is dropped from within an asynchronous context.', ~/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-0.2.22/src/runtime/blocking/shutdown.rs:49:21
stack backtrace:
   0:        0x1083da9ee - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h72782cdbf82d2e78
   1:        0x1083fc1ac - core::fmt::write::h0f2c225c157771c1
   2:        0x1083d52d9 - std::io::Write::write_fmt::h6d219fc26cb45a24
   3:        0x1083dc865 - std::panicking::default_hook::{{closure}}::hde29d026f53869b1
   4:        0x1083dc5a2 - std::panicking::default_hook::h5de23f27de9ce8ce
   5:        0x1083dcdc5 - std::panicking::rust_panic_with_hook::h720143ee15fc80ba
   6:        0x10840664e - std::panicking::begin_panic::h80d64999a84f0366
   7:        0x108297874 - tokio::runtime::blocking::shutdown::Receiver::wait::hc15bfd5c68b76ca0
   8:        0x1082cbfc5 - tokio::runtime::blocking::pool::BlockingPool::shutdown::h702cd79db6adf80b
   9:        0x1082cc07d - <tokio::runtime::blocking::pool::BlockingPool as core::ops::drop::Drop>::drop::h0ab515030d41ffa8
  10:        0x1082d6215 - core::ptr::drop_in_place::h1df0de4e6c94e3fe
  11:        0x1082d8252 - core::ptr::drop_in_place::h94c49217ab7681ef
  12:        0x10801a738 - reqwest::blocking::wait::enter::he7b4b5e4e35343bf
  13:        0x108019bd7 - reqwest::blocking::wait::timeout::h7234a2ddbbcb0534
  14:        0x10803b703 - reqwest::blocking::client::ClientHandle::new::hd976e58a3aac69e4
  15:        0x10803ae1d - reqwest::blocking::client::ClientBuilder::build::h18af5d75937efe22
  16:        0x10803aece - reqwest::blocking::client::Client::new::h09aac586c8993277
  17:        0x107eff6ea - schema_registry_converter::schema_registry::SrSettings::new::h3b74a91814783f96
  18:        0x107d0a3f3 - my_web::main::{{closure}}::hbb912dd7df4aeb4d
  19:        0x107ca4120 - <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::ha2815f8e7aca5dc1
  20:        0x107c8865d - tokio::runtime::enter::Enter::block_on::{{closure}}::h6b5e9b23e5c4d655
  21:        0x107c8e506 - tokio::coop::with_budget::{{closure}}::hb18b9d07d0e693a7
  22:        0x107cebdee - std::thread::local::LocalKey<T>::try_with::ha9811a7840d57628
  23:        0x107ceb4ac - std::thread::local::LocalKey<T>::with::hcb4e45ba7e69edaa
  24:        0x107c884ad - tokio::runtime::enter::Enter::block_on::h8dea6c389ed18880
  25:        0x107d11315 - tokio::runtime::thread_pool::ThreadPool::block_on::h274b9930f19cc162
  26:        0x107ca76e8 - tokio::runtime::Runtime::block_on::{{closure}}::hf60396b6d86ee761
  27:        0x107cc90b8 - tokio::runtime::context::enter::hcb90097146788eb6
  28:        0x107c653db - tokio::runtime::handle::Handle::enter::h7963a1ebbf377697
  29:        0x107ca763d - tokio::runtime::Runtime::block_on::h61ecdca8fd87f99b
  30:        0x107cb24cc - my_web::main::h372f3d2471b960b7
  31:        0x107d1171e - std::rt::lang_start::{{closure}}::h6532f1318acae0d5
  32:        0x1083dd14f - std::rt::lang_start_internal::hbbd10965adc92ae7
  33:        0x107d11701 - std::rt::lang_start::ha5adc3b371471675
  34:        0x107cb2532 - main

Currently it's all blocking sync. Mainly because cashing will be hard. Also I don't have much experience using async jet.
So the reqwest client inside the SrSettings one is blocking. I don't really understand what your trying to do.
Something I could do, is at least for the schema_registry module, is offering async calls, by using the async reqwest client.
My main concern is with the converters. Kafka is really fast, so if I get a million messages with the some id in a second, and the Sr calls also need a second, I don't want to that a million times.
Most likely there are solutions to this, I just haven't take a look at them. I'm trying to finalise for the 2.0.0 release, it's probably good to mention the current version is blocking.
I'd love to hear how you think about those things.

What I'm trying to do is to build a http server by using warp to put all request into a channel and then with a async task to produce those requests into Kafka.

Ok, but are you using Schema Registry? In that case it would be nice if you could use this library for some of the stuff related to that.
Just to be sure, this library is not sending anything to Kafka, you need either https://crates.io/crates/rdkafka or https://crates.io/crates/Kafka for that. Now that rdkafka is async by default it would probably make sense to have async converters as well. But at this point I really don't know how much work it would be.

Sure . I'm trying to using this crate to encode message to Avro

Ok, can't promise anything, and don't think I want it to be part of 2.0.0. But seems like a valid use case with rdkafka being async by default. And know the http calls already use reqwest I don't see any problems beside the cache. But seems like a problem that has likely be solved already, so definitely going to look into it.

That's great and thanks for you work.

Thanks, at the very least I want to be confident enough I don't need to break to api to implement it. So very much thinking of adding at least support to schema_registry for async, and have the converters return an error when used with async SrSettings. Api would then be something like:
let sr_settings = SrSettings::new_builder(String::from("https://condluent.cloud.url"))
    .async()
    .build()
    .unwrap();

to create the async version. I'm not convinced async as default is a good idea, but I'll give it some thought.

I decided to bite the bullet, and split the code in blocking and async, much like how reqwest has done. I'm also going to default to async, as that seems to make most sense as both reqwest and rdkafka are async by default. I'm not sure how much will be available async when 2.0.0 comes out, but at least I don't need breaking changes adding more async features later on this way.
So unlike my last message it will be  probably the case you need to add the feature "blocking" to get access to the blocking api, and all else will be async, but like I said, the initial available async api will likely be minimal since I really want to have 2.0.0 out before Kafka summit.

@undeflife Could you maybe check if you can use it async now? Just merged in the async Avro encoder/decoder. It should use async by default, so you should only need the feature avro, and then be able to use the AvroEncoder and AvroDecoder with async implementations.

Works as expect! Thanks.


Support for untrusted modules

Feature Summary
What would need to be added to add support for untrusted modules? Specifically, in the ibc README, there is a warning saying

This crate currently does not support mutually distrusted packages. That is, modules on the host state machine are assumed to be fully trusted. In practice, this means that every module has either been written by the host state machine developers, or fully vetted by them.

Are there any specific issues that are known with the ibc-rs package that would need to be addressed, or has the possibility of support not really been fully explored? Off the top of my head we would probably need to check for reentrancy attacks.
Proposal

Add support for untrusted modules to fully support ICS 24.

The short answer is that they are not essential to the IBC protocol, and the value of this feature could come if we had hundreds of IBC apps and it simply wasn't possible to review everything. This is not the case today, and we didn't see the value of this today. By the way, not even the Cosmos SDK supports distrusted packages. In my opinion, it never should have made it in the standard.
Is this a feature that you would need?

I think I need a little bit more context around what an "IBC app" means here. Is it the case that any app that wishes to send messages through an IBC connection must be vetted by the chain developers right now, even if the connection has already been established?
What I was imagining is that the chain devs could help establish IBC connections with other chains, and then untrusted apps could register as modules to send and receive messages. Or would these apps need to split their apps into a "trusted" component that is vetted by the chain devs, and then an "untrusted" component that can't interact directly with the IBC implementation?

I think I need a little bit more context around what an "IBC app" means here.

The term is unfortunately overloaded. An "app" is the same as an "IBC module" (both not great names), or concretely in ibc-rs, the thing that implements Module. Examples are token transfer (ICS 20), interchain accounts (ICS 27), etc.

Is it the case that any app that wishes to send messages through an IBC connection must be vetted by the chain developers right now, even if the connection has already been established?

Yes. To be more precise, apps send packets over channels. A channel can only be established to an app that is bound to a port on the router, and so the channel can't "already be established". The general flow I see is:

chain developer vets app X implementation
chain developer binds app X to port P. This currently requires a hard fork of the chain.
After the hard fork, app X is available at port P
user U opens a channel to app X, connected to app X on some other chain

Specifically what we mean by "needs to be vetted" is: don't just pick an app implementation on some github repo and run it. The app can theoretically be malware; it does not run in a sandbox, and has access to the file system, network, etc. When developers incorporate apps in their chains, it is their responsibility to ensure that the app works as intended.
Let me know if there is still something that is not clear.

Apologies for missing this earlier. What you're saying makes sense. I had two follow-up questions:

Does the ibc-rs library need to be protected against reentrancy attacks? e.g. suppose that a vetted app has a bug in it in a smart contract environment. Do we need to add reentrancy guards around any parts of the ibc-rs API to try to mitigate this possibility?
Is there some way to expose a generic interface that any user / smart contract developer can use to send messages to another chain? I'm imagining that contract A on chain 1 sends a message destined for contract B on chain 2, intermediated through an IBC module on both chains that simply dumps each message into storage on the destination chain, and maybe notifies the destination contract. Could this be implemented as an IBC module on both chains?

Does the ibc-rs library need to be protected against reentrancy attacks?

That is currently an open question for me, and I currently don't have enough "concrete data" to respond. For one, it depends a lot on the smart contract platform: the EVM architecture allows for reentrancy attacks, but Move-based chains don't. There are other smart contract platforms in Cosmos (Cosmwasm, Agoric, etc), but at this moment none have expressed interest in integrating with ibc-rs, so my specific knowledge about how they work is limited.
TL;DR: we currently design the system around the assumption that IBC apps are "static" SDK-like modules (i.e. present at compile-time, and vetted by the chain developers). Reentrancy attacks thus currently fall outside the scope of ibc-rs, as they would occur in the app code, and depend on how that app code is architected. Let me know if you had a specific smart contract platform in mind.

Is there some way to expose a generic interface that any user / smart contract developer can use to send messages to another chain?

Not sure if I fully understand the question, but hopefully this is useful. Basically if somehow you implement the Module interface for both contracts, and bind them statically to a port (using the Router), then you can obviously simply create a channel between the 2 modules and send packets over it. Again, this requires that your contracts are present at compile-time (i.e. not uploaded by a user after the chain is launched). For contracts uploaded at runtime by any user, then I'd look into how cosmwasm does it. Note though that cosmwasm though is built on top of ibc-go.


Add changelog for v1.11.3

To avoid docker image gitea/gitea:1 become v1.10.6, this version have to be tagged after minutes when v1.10.6 tagged .

For the docker tag bug maybe we should remove the autotag from n-2 version branch ?

@sapk I think make the max semantic version as gitea/gitea:1 everytime when we release that docker tag.

I added the label blocked just to make it explicit that it need to be merged (or at least tagged) after #10699

Please send forward ports.


impl first_normal_slot and slots_per_epoch

this makes it easy to advance epoch-by-epoch as shown in the test. note there is a print from tests ERROR solana_runtime::bank] Burned 21 rent lamports instead of sending to 11111115RidqCHAoz6dzmXxGcfWLNzevYqNpaRAUo when warping past the warmup (the address is pubkey zero, im not sure what account is paying rent tho?)

Thanks, we should probably just add a wrapper for GenesisConfig and genesis_config() method to match solana-program-test, right?

yea we could do that instead


renumber all our failure exit codes to be unique

This might help us track down the mysterious exit 1 we see. If it's still a 1, we can dig deeper into our deps.

I'm confused by the changes to some interaction with Cached. It seems like you have regressed to the old Cached API somehow.

it's still a 1.


Add a build&test script

This is part 1 of getting rid on run_after_success.
should be a no-op because this script hasn't been used anywhere else.

@icygalz: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/release-e2e-bookinfoTests
763ecabf23d47015cc0964bc593829817d1fc518
link
/test release-e2e-bookinfoTests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@icygalz: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/release-e2e-bookinfoTests
763ecabf23d47015cc0964bc593829817d1fc518
link
/test release-e2e-bookinfoTests

prow/release-e2e-pilot-no_auth
763ecabf23d47015cc0964bc593829817d1fc518
link
/test release-e2e-pilot-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/test release-e2e-bookinfoTests
/test release-e2e-pilot-no_auth


Modules initialized multiple times

Hi, I've experienced this after upgrading from v3 to v4. Not sure if this is a bug or not, so submitting this as a question instead.
In webpack v3, when I included a common vendor chunk and two entry chunks on the same page, the modules from the vendor chunk were only initialized once.
In v4, however, it appears that shared modules are initialized for every runtime chunk (and each entry chunk by default contains one), not once. And in my case, this broke a legacy script module that had side effects. I managed to fix this by using optimization.runtimeChunk configuration to make sure there's only one runtime, but I'm still not sure if the current default behavior is expected.
Is it? I didn't find the answer in the docs.

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template and reopen, or open a new issue.

@evilebottnawi, reopen please?

@uncleyo Thanks for using issue template :+1: In near future we will investigate this

When using multiple entrypoints in a page you need to use runtimeChunk single.
I guess you are abusing entry to create a vendor chunk, which is not the correct way.

@sokra, no, I am abusing it that way. The vendor chunk is generated by splitChunks and isn't configured in the output. Two entries are loaded by the same page and both load a module from vendor chunk.
These entry chunks can be used separately or together on a page. I did configure the runtimeChunk: {name: "vendor"} now to put it there once and it works. But it still feels weird that by default a shared module would be evaluated twice in this case. Even if the shared module doesn't have side effects like mine did, it can be pretty expensive for large modules: for example, stuff like react would be initialized twice.
Also, this is not how it worked in webpack v3 with no runtime related configuration tweaks...

Ok. I did it right.
But yes, it actually work this way. When using multiple entry points on a page you need to use runtimeChunk: "single" or with name.

Having multiple entry-points on a single page, how is this possible?

@Legends yep, example i can have app.js and have visual editor which loading script using own api (example plugins for TinyMCE).

Thanks for the answer, @sokra! I kinda does make some sense the way it isolates the runtimes now, so I rather wanted to check first if this wasn't an unintended change.
I guess the biggest problem is that this goes unnoticed and many might run into this without knowing with default behavior, since there are no warning signs anywhere.
I wouldn't notice if my legacy script didn't blow up in Edge. Also, apart from the time wasted reevaluating the same modules, it can probably cause some equality checks and such to fail if code from different entries would interoperate through the global state.
Not sure what can be done about it. Just improving the docs on runtimeChunk is an option, but people on defaults might not read those. And warning from webpack-cli feels a bit too severe, since not many who has multiple entries loads them to the same page, I reckon.

@Legends, while not recommended or needed in most cases, it is actually useful sometimes, especially when dealing with legacy stuff.
For example, one entry is the app itself and another entry is loaded right before it to apply localization to the legacy framework through the global state. They are not baked together, because only one (of many) localization entry chunks is being loaded at a time.

Can we close this? Is the problem solved?

Yes, working as intended and it is now explained in the documentation


Implement Spark-compatible CAST from timestamp to numeric types

What is the problem the feature request solves?
We need to implement CAST from timestamp to numeric to match Spark's behavior.
We can break this into multiple issues if needed.
The following example is casting timestamp c to different numeric types.
scala> spark.sql("select c, cast(c as boolean), cast(c as byte), cast(c as short), cast(c as int), cast(c as long), cast(c as decimal) from t3").show
+-------------------+----+---+-----+----------+----------+----------+
|                  c|   c|  c|    c|         c|         c|         c|
+-------------------+----+---+-----+----------+----------+----------+
|2024-01-01 00:00:00|true|-16|25328|1704092400|1704092400|1704092400|
|2023-12-12 00:00:00|true|-16| 1264|1702364400|1702364400|1702364400|
+-------------------+----+---+-----+----------+----------+----------+

Describe the potential solution
No response
Additional context
No response

Also, Spark returns timestamp in seconds and Comet returns timestamp in microseconds.
// input: 2023-12-31 10:00:00.0, expected: 1.7040456E9, actual: 1.7040456E15


Implemented get_config

Related to napalm-automation/napalm-base#65

The test is failing because napalm-automation/napalm-base#69 hasn't been merged


FETCH

Song Name
the fetch song
Artist Name
Dawko & DHeusta
Source
Youtube
Youtube Link
https://youtu.be/lUFQrPixgfk?si=mxDkyzMf4_Jjlcvq
Direct File Link
No response
Song ID
689654
Start Offset [ms]
0
Extra
No response

good song zen.

accept

good song zen, i wanna make a level with it

thanks mika

i wanna make a level with it too

reject
popular songs like "Hop" are too inconvenient to be replaced by smth unrelated and are therefore usually rejected.
Note that you can still use the song yourself, but it won't be public


Updating examples, re-namespacing client

Description of changes:
Updated example trialObject
Updated client name to match service name
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Approved


Using WebApp.DockerFile getting error: "no module named gunicorn"

Describe the bug
During deployment using WebApp.DockerFile getting error: "no module named gunicorn"
To Reproduce
Steps to reproduce the behavior:

run docker build on the WebApp.DockerFile
run docker run on the built image

Expected behavior
Expected gunicorn to start
Configuration: Please provide the following

Ran on WSL Ubuntu on local posix machine

Additional context
I have applied a fix in the docker file, to pip install gunicorn instead of uwsgi which is the following:
Fix:
Line 21: && pip install --no-cache-dir gunicorn
Previous state:
&& pip install --no-cache-dir uwsgi

Hi @QuentinAd - in addition to installing gunicorn, you can try modifying the last CMD line to CMD ["gunicorn", "app:app"]. We're working on fully validating these changes and will push a fix to the Dockerfile soon.

@QuentinAd  see my #602 post about an additional issue, where I fixed this "no module named gunicorn" issue by adding gunicorn to the requirements.txt file

@sarah-widder,
gunicorn.conf.py
Added the missing 80 in the bind
import multiprocessing

max_requests = 1000
max_requests_jitter = 50
log_file = "-"
bind = "<IP_ADDRESS>:80"

timeout = 230

num_cpus = multiprocessing.cpu_count()
workers = (num_cpus * 2) + 1
worker_class = "uvicorn.workers.UvicornWorker"


BLAKE2b Implementation in Pantheon for Istanbul Hard Fork

Description
As part of the Istanbul network upgrade, BLAKE2b support will be added to Ethereum.
This bounty is to implement a BLAKE2b precompile as part of Pantheon that conforms to the specification in EIP-131 (as specified in this Github PR link) as required for the Istanbul Hard fork EIP-1679.
Note: if you wish to work on this bounty for the hackathon, please comment on the Github issue so that others know you are working on it.
The implementations should use a coding style consistent with the rest of Pantheon. Please see our Contribution Guidelines for more information, along with the following classes for reference:

The RipeMD precompiled contract is expected to have a similar pattern: Github search results
The BouncyCastle library has a Blake2bDigest that may be of use implementing the EIP.  Bouncy Castle has a MIT style license and is compatible with our Apache 2.0 license.  Be sure to attribute authorship and point to the relevant license when copying code.

Submission Requirements

Implementation of a BLAKE2b precompile as part of Pantheon which is compliant with EIP-131 (also possibly known under the numbers 2129 and 2024) and the requirements for the Istanbul network upgrade.
Unit test code to validate correct behavior.
Integration test to demonstrate correct behavior.
Passes all reference tests for the Blake 2b precompiles in the Ethereum reference tests, if they are available prior to the submission deadline.
All libraries and dependencies must use Apache 2.0 friendly licenses
A demo.md file that explains how PegaSys engineers can verify that the code works as intended, ideally without the use of 3rd party tools.

Submission Deadline: July 10th
Judging Criteria
The bounty will be awarded to the best submission based on compliance the EIP specification, code and testing quality, compliance with Contribution Guidelines, performance speed, maintenance burdens, and the Submission Requirements above, according to PegaSys.
Judging Date: July 12th
Bounty: 1000 DAI

I'll look at implementing this functionality, if you'll have me.

@atoulme this bounty is part of the ongoing Gitcoin hackathon. Anyone is free to start working on it, but the bounty will only be awarded to the winning implementation at the end of the hackathon.

@timbeiko I'm a bit confused here. Is the aim do a blake2b precompile or a blake2b f compression precompile?

It's the Compression Function F precompile, this PR will update EIP-131 - https://github.com/ethereum/EIPs/pull/2129/files

To be clear th correct EIP number for the F precompile is EIP-152!
https://github.com/ethereum/EIPs/pull/2129/files

@mhluongo yours and @shemnon's link are pointing to the same PR. Did the EIP number just change? cc: @iikirilov

EIP-152 is the successor of EIP-131.

Because completion of the hack was impossible (specifically the Gas calculation has not been specified in the EIP) we have decided to offer a compromise prize.  @iikirilov submitted the most complete solution, and that solution has the hardest part of the EIP complete: an implementation of the F compression function.  We will award half the hackathon bounty now based on that work.  Once the EIP is complete @iikirilov can submit a completed implementation ready for integration for the second half of the prize.

The gas cost appears to be specified in https://github.com/ethereum/EIPs/pull/2129.  While this is still open the got some positive feedback on the All Core Devs call.  Can you finish the gas cost calculations and function registration based on these values?

@shemnon should we close this?


feat: sync AxonBlock, Metadata, Proof with axon

What this PR does / why we need it:
This PR syncs with latest changes to AxonBlock, Metadata, Proof of Axon. Moreover, the corresponding deserialization methods to these structures are updated too.
Which docs this PR relation:
https://github.com/cryptape/layer2-internal/issues/406

/run-ci

can you use real data and interface from Axon repo to fulfill the examples to check the validation of interactivity with Axon ?

Yes, it will be updated. I'm trying to pass the mock data firstly


Added section in Monarch docs for Inspect Tokens development helper

Fixes #1805

I'm not confident I captured the same phrasing & information style as the rest of the docs, and have no emotional attachment to the way it is now if you'd rather re-phrase!

:+1: Thank you!


Doubts about output

Hi, I have some questions  about output!

seed：0
r：0.970982
nmse_test ：0.000893
nmse_test_noiseless ：0.000893
success ：FALSE
expression：extremely complex and long!
r square is 0.970982, but why success shows FALSE? What's wrong?

Success is only true when you exactly recover an expression on noiseless data. It doesn’t mean the algorithm failed. Looks like you found a pretty good fit!


[SIP-0] Superset Improvement Proposals

Superset Improvement Proposals
Purpose
The purpose of a Superset Improvement Proposal (SIP) is to introduce any major change into Apache Superset. This is required in order to balance the need to support new features, uses cases, while avoiding accidentally introducing half thought-out interfaces that cause needless problems when changed.
What is considered a major change that needs a SIP?
Any of the following should be considered a major change:

Any major new feature, subsystem, or piece of functionality
Any change that impacts the public interfaces of the project

What are the "public interfaces" of the project? All of the following are public interfaces that people build around:

Visualization types
Form data for saved dashboards and charts
REST endpoints
Data passed between backend and frontend
Configuration
Command line tools and arguments

What should be included in a SIP?
A SIP should contain the following sections:

Motivation: describe the problem to be solved.
Proposed Change: describe the new thing you want to do. This may be fairly extensive and have large subsections of its own. Or it may be a few sentences, depending on the scope of the change.
New or Changed Public Interfaces: impact to any of the "compatibility commitments" described above. We want to call these out in particular so everyone thinks about them.
New dependencies: describe any third-party libraries that the feature will require, from PyPI or NPM. In particular, make sure their license is compatible with the [Apache License v2.0] (https://www.apache.org/licenses/LICENSE-2.0).
Migration Plan and Compatibility: if this feature requires additional support for seamless upgrades describe how that will work. In particular, it’s important to mention if:

The feature requires a database migration;
Dashboards and charts that are saved or bookmarked will still work after the change;
The feature will coexist with similar functionality for some period of time, allowing for a deprecation period.

Rejected Alternatives: What are the other alternatives you considered and why are they worse? The goal of this section is to help people understand why this is the best solution now, and also to prevent churn in the future when old alternatives are reconsidered.

Who should initiate the SIP?
Anyone can initiate a SIP, but preferably someone with the intention of implementing it.
Process

Create an issue with the prefix “[SIP]” in the title. The issue will be tagged as “sip” by a committer, and the title will be updated with the current SIP number.
Notify the dev@ mailing list that the SIP has been created, use the subject line [DISCUSS] ..., the body of the email should look something like Please discuss & subscribe here: https://github.com/apache/incubator-superset/issues/5602
When writing the issue, fill in the sections as described above in “What should be included in a SIP?”. You can use the template included at the end of this document.
A committer will initiate the discussion and ensure that there’s enough time to analyze the proposal. Before accepting the SIP, a committer should call for a vote, requiring 3 votes and no vetoes—both from committers. Votes are timeboxed  at 1 week, and conducted through email (with the subject line [VOTE] ...).
Create a pull request implementing the SIP, and referencing the issue.

Template
[SIP] Proposal for _
Motivation
Description of the problem to be solved.
Proposed Change
Describe how the feature will be implemented, or the problem will be solved. If possible, include mocks, screenshots, or screencasts (even if from different tools).
New or Changed Public Interfaces
Describe any new additions to the model, views or REST endpoints. Describe any changes to existing visualizations, dashboards and React components. Describe changes that affect the Superset CLI and how Superset is deployed.
New dependencies
Describe any NPM/PyPI packages that are required. Are they actively maintained? What are their licenses?
Migration Plan and Compatibility
Describe any database migrations that are necessary, or updates to stored URLs.
Rejected Alternatives
Describe alternative approaches that were considered and rejected.

Updated to add step 2 Notify the dev@ mailing list that the SIP has been created to the process

@betodealmeida Would you like to call for votes in the mailing list for this proposal?

where should the discussion for the SIP take place ?
I believe, it could be either the dev list or the SIP issue itself.
doing on the dev list would make be easier for people not following the SIP issue itself to follow the discussion.

I believe, it could be either the dev list or the SIP issue itself.

I would vote for having the discussions on the SIP github issue.

dev@ mailing list does not support images. There are many cases where screenshots/mocks/diagrams are necessary.
Github issues allow editing, tagging, images out of the box, and is generally much easier to read than a long email thread.

doing on the dev list would make be easier for people not following the SIP issue itself to follow the discussion.

With the proposed process, author will notify dev@ mailing list that a SIP has been created. Then people can subscribe/unsubscribe to notifications. This will let people subscribe only to the discussions they are interested.

I agree with @kristw about having the discussion on Github. Images are a dealbreaker for a data visualization project. Also diagram and such.

I amended the proposal, should we specify a process to amend post-vote?

Closing this since it was voted.

hos_144

Good morning! Is there also a mobile app developer here?

could superset support connecting to OceanBase in the future?

Please note that this SIP has passed, so SIPs will move forward (or not) according to this revised process.


Discover workspaces without using them in resolution

Add minimal support for workspace discovery, only used for determining paths in the bluejay commands.
We can now discover the workspace structure, namely that the pyproject.toml of a package belongs to a workspace pyproject.toml with members and exclusion. The globbing logic is inspired by cargo. We don't resolve workspace = true metadata declarations yet.

I've edited the spec from #3404 into a docstring

Merging this now to avoid merge conflicts

@konstin - Gave this a read, looks like a good start.


maintainers/teams: remove inactive maintainer from golang

hasn't been active for a year
cc @NixOS/golang
Description of changes

Things done

Built on platform(s)

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

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

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

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

Seems so based off their GH.


Cross-Compilation for Raspberry Pi 4 Not Working

The cross-compilation settings in cross_files.txt doesn't work for the latest Raspberry Pi 4.
I changed the [host_macine] section to the following:
[host_machine]
system = 'linux'
cpu_family = 'aarch64'
cpu = 'aarch64'
endian = 'little'

But when I copied the compiled files to the Raspberry Pi 4, it shows the following message:
bash: ./example.cpp.o: cannot execute binary file: Exec format error
I also tried to execute the "sca3300-exe" file, but it didn't work. The file exists and has been set to be executable, but the terminal keeps saying the file doesn't exist when I tries to execute it.
I also tried to do local compilation, but the Raspberry Pi 4 always freeze when linking.

I have tried on my side and seems working on Raspberry Pi4. Please share log.

pi@rasp-laser:~ $ uname -a
Linux rasp-laser 5.4.51-v7l+ #1333 SMP Mon Aug 10 16:51:40 BST 2020 armv7l GNU/Linux
pi@rasp-laser:~ $ lscpu
Architecture:        armv7l
Byte Order:          Little Endian
CPU(s):              4
On-line CPU(s) list: 0-3
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):           1
Vendor ID:           ARM
Model:               3
Model name:          Cortex-A72
Stepping:            r0p3
CPU max MHz:         1500.0000
CPU min MHz:         600.0000
BogoMIPS:            108.00
Flags:               half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
pi@rasp-laser:~ $ file sca3300-exe
sca3300-exe: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0, BuildID[sha1]=d00e4a651d4f36a7b83ed87bb0912539854104cd, with debug_info, not stripped
pi@rasp-laser:~ $ ./sca3300-exe
Temperature: 0.000000
Accel_X: 0.000000
Accel_Y: 0.000000
Accel_Z: 0.000000
Temperature: 0.000000
Accel_X: 0.000000
Accel_Y: 0.000000
Accel_Z: 0.000000

To be honest I didn't work on it from a while :S Feel free to fork !

Hi!
I tried to compile the project on fresh raspberry pi OS on RPi 4 and it works with not issue, but I can't get it working. When I execute ./sca3300-exe it do nothing. Could you provide some info how did you connect RPI to SCA3300 SERIES PCB (https://www.murata.com/-/media/webrenewal/products/sensor/pdf/specification/pcbspec_scx3300.ashx?la=en&cvid=20190614072539001900) ?

Hi @trojek
Please double check Raspberry SPI configuration (sudo raspi-config). I'm pretty sure your bus is not enable.
Keep in my that I don't work on this library from a while.... Feel free to fork the project.

Hi @Ninic0c0
You was right about SPI configuration - it wasn't enabled. Currently it returns:
 Temperature: 0.000000
 Accel_X: 0.000000
 Accel_Y: 0.000000
 Accel_Z: 0.000000

I assume that I didnt't wired it properly.
I connected:
GPIO10 ->  MOSI
GPIO9 -> MISO
GPIO11 -> SCK
and:


State of the repo ?

Hi!
It seems like there are quite a few open PRs for various fixes, that haven't been merged for a while.
Can the community help with maintaining this repository?
I believe it's used quite actively, and for example, we'd be happy to invest the time into maintaining it.
I'm happy to volunteer as a maintainer, and/or we can also move this under our organisation (https://github.com/languagedrops/) and officially continue developing it if @sbugert doesn't have time to do all of this.
Thanks!

Hello!
Sorry for the super late reply.
I'm not using the library myself at the moment and can't invest enough time for maintaining it
But I probably will soonish so I would rather keep it under my github account (for now).
However, I would be more than happy to add you as a collaborator to the repo and npm!
Maybe we can work out some kind of roadmap together.
@koenpunt what are your thoughts/plans for the project?

No worries:)
Actually, we ended up migrating over to https://github.com/invertase/react-native-firebase, so we're not using react-native-admob ourselves either since yesterday.
So far, our experience has been good, but we may need a bit more time for proper evaluation.

I've been using this library successfully in multiple projects. But since I'm currently not actively working in those projects, I don't really have the time to address all issues that are opened here. Also because I think most issues are not bugs, but more like usage issues.
As for adding maintainers; I think someone should have shown reasonable investment of triaging and/or development into the project. For example @itchingpixels showed interest, but also mentioned in other issues not being familiar with Java/android development (forgive me if not accurate, just making an example here), but then also just a week after did migrate to a different solution, which is fine, but also shows lack of dedication.


clicking on index with where clause

Clicking on index with where clause gives the error "more than one row returned by a subquery used as an expression".
Regards
pgaro

Hi @pgaro ,
Thanks for reporting this. It is fixed now, will be published in next release.
Regards,
William

Hi @pgaro ,
Thanks for helping making OmniDB better. This is fixed in OmniDB 2.13.0, which we are releasing today.
I'll keep this issue open in case you want to provide your valuable feedback, as always.
Best regards,
William

Works like a charm, thank you!


Adds Cloud Servers examples

I also want to merge the new index.rst from the other PR. Also will add an example of creating an instance with cloud-init.

Ok, this has been rebased and should be ready to go.

:+1:


Flash Plugin Blocked

Hi, awesome job on the app!  I am trying to watch a live sports event through the Watch ESPN web application, but whenever I access the url through Helium, I am presented with a 'Blocked Plugin' screen.  I have ensured that my flash plugin is up to date, but the problem still persists.

Same issue observed on HBO go.

You're sure that you have flash player installed in Safari*, not just Chrome, right?

In my case, just updating the Flash Player in Safari solved the issue


Case matters for world-rewrite

In the world-rewrite section of the config, from what I can see, the case is not ignored there like it is in other places in LuckPerms.

Is this a problem? :p

Was a problem for me trying to understand why stuff wasn't working for a few hours before I thought that case might matter. Would be nice if it at least printed a warning.


Release background from problemMatcher its too complicated in its current form

One of the most frustrating things I've found with setting up a task is the problemMatcher. Its far too complicated for simple tasks such as setting up a background task to the point most don't bother to use it, which is a shame because it's quite powerful.
Here are some things worth considering:
Background Tasks
Sometimes I want to have a watch task, such as ESBuild watch. This is a pain to configure.

background should come out of the problemMatcher scope. This is because I don't care about matching the output, I just want to start background tasks and let VSCode know when something is being rebuilt.  Even though this is straight forward in theory I now need to define loads of problemMatcher config, and I usually end up just setting $tsc as a base, which is wrong if its not a TypeScript Project. This has been brought up as far back as 2016 by @dbaeumer
background shouldn't force you to have a beginsPattern it makes no sense for watch tasks which start straight away and every subsequent change just triggers similar output (like “build successful”). (see edge case)

Edge Case:
ESBuild for example doesn't show any output when a watch task starts, this means beginsPattern is not applicable, "activeOnStart": true is set but a beginsPattern is still required. After the first successful build "watch build succeeded" is shown. I can't set "watch build succeeded" as the beginsPattern because it will never show until the first save, and I can't set it as endsPattern because VScode will think im just beginning a build when it has in fact ended.
My Proposal is this:
background can stay within problemMatcher for backwards compatibility but it should be a top level item within tasks. It's not tied to problemMatching, and sometimes you just want to mark the beginning and end of a build in watch mode.
beginsPattern should be optional if activeOnStart is set to true. That way whenever endsPattern is shown a build has finished. I believe this will allow VSCode to be more flexible when creating background tasks. This would also fix https://github.com/microsoft/vscode/issues/6209 because now preLaunchTask  can start once endsPattern has been triggered.
Steps to reproduce:

Clone: https://github.com/styled-components/vscode-styled-components
npm i
run the build task
try modifying the build task to show when running and finished (this is impossible because ESBuild doesn't show any output when it starts).

Docs:

https://code.visualstudio.com/docs/editor/tasks
https://code.visualstudio.com/docs/editor/tasks-appendix

Related:

https://github.com/microsoft/vscode/issues/6209

Hey @alexr00 @meganrogge just want to highlight this is still an issue in the form of modern codegen/bundler tools like ESBuild today.
For instance, the watcher configuration was built around tools like gulp which had a start and finish.
Start: File change detected.
Finish: Compilation complete. Watching for file changes.
But modern tooling doesn't echo out to lines like that anymore as the complication is so fast, its usually just "watch deteched", so trying to configure a beginsPattern and an endsPattern for something like esbuild doesn't really work


Add static binary to distribution

We need to also distribute the static binaries for anyone that doesn't want to use an installer.

This will address https://github.com/influxdb/influxdb/issues/2069#issuecomment-86021740

This might be helpful: http://stackoverflow.com/questions/29346093/how-to-create-a-static-go-binary-which-runs-on-every-distro

Closed. This is done, just need to document it: https://github.com/influxdb/influxdb.com/issues/76

@beckettsean, where can I find the static binaries?

@smebberson Standalone binaries are available through the downloads page here:
https://influxdata.com/downloads/#influxdb

@rossmcdonald, thanks for getting back to be. But I was hoping for a static binary? I could be doing something wrong, however, the following outputs shows downloading the file and inspecting with ldd and it seems as though those binaries haven't been statically compiled?
vagrant@ubuntu-14:/src$ wget https://s3.amazonaws.com/influxdb/influxdb_<IP_ADDRESS>_x86_64.tar.gz
--2015-12-14 10:16:36--  https://s3.amazonaws.com/influxdb/influxdb_<IP_ADDRESS>_x86_64.tar.gz
Resolving s3.amazonaws.com (s3.amazonaws.com)... <IP_ADDRESS>
Connecting to s3.amazonaws.com (s3.amazonaws.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13386496 (13M) [application/x-tar]
Saving to: ‘influxdb_<IP_ADDRESS>_x86_64.tar.gz’

2015-12-14 10:16:55 (771 KB/s) - ‘influxdb_<IP_ADDRESS>_x86_64.tar.gz’ saved [13386496/13386496]

vagrant@ubuntu-14:/src$ tar xvfz influxdb_<IP_ADDRESS>_x86_64.tar.gz
./
./influxdb_<IP_ADDRESS>_x86_64/
./influxdb_<IP_ADDRESS>_x86_64/usr/
./influxdb_<IP_ADDRESS>_x86_64/usr/bin/
./influxdb_<IP_ADDRESS>_x86_64/usr/bin/influx
./influxdb_<IP_ADDRESS>_x86_64/usr/bin/influx_stress
./influxdb_<IP_ADDRESS>_x86_64/usr/bin/influxd
./influxdb_<IP_ADDRESS>_x86_64/usr/bin/influx_inspect
./influxdb_<IP_ADDRESS>_x86_64/usr/lib/
./influxdb_<IP_ADDRESS>_x86_64/usr/lib/influxdb/
./influxdb_<IP_ADDRESS>_x86_64/usr/lib/influxdb/scripts/
./influxdb_<IP_ADDRESS>_x86_64/usr/lib/influxdb/scripts/influxdb.service
./influxdb_<IP_ADDRESS>_x86_64/usr/lib/influxdb/scripts/init.sh
./influxdb_<IP_ADDRESS>_x86_64/etc/
./influxdb_<IP_ADDRESS>_x86_64/etc/influxdb/
./influxdb_<IP_ADDRESS>_x86_64/etc/influxdb/influxdb.conf
./influxdb_<IP_ADDRESS>_x86_64/etc/logrotate.d/
./influxdb_<IP_ADDRESS>_x86_64/etc/logrotate.d/influxdb
vagrant@ubuntu-14:/src$ ldd ./influxdb_<IP_ADDRESS>_x86_64/usr/bin/influx
	linux-vdso.so.1 =>  (0x00007ffff93d1000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f4b1a38e000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4b19fc8000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f4b1a5b4000)
vagrant@ubuntu-14:/src$ ldd ./influxdb_<IP_ADDRESS>_x86_64/usr/bin/influxd
	linux-vdso.so.1 =>  (0x00007fff62ece000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f4374f14000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4374b4e000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f437513a000)

Those libraries are standard libraries dynamically linked by almost all non-trivial Go programs. When Go claims to be a statically linked system, it means except for those libraries shown above. This is not something special to InfluxDB.

Okay, cool. I'm trying to get InfluxDB up and running on Alpine Linux. I'm building it locally...

@otoolep, this article seems to explain how to build a static go binary, http://blog.hashbangbash.com/2014/04/linking-golang-statically/. Can that apply to InfluxDB?

You could try it @smebberson :-) None of us have in here however.

@otoolep, yeah, I did try it, but it didn't succeed (the binary was created, but the output from ldd was the same). I'm not that familiar with Go (unfortunately) so I didn't bother pushing forward with it. I got it to build on Alpine Linux without too many issues, https://hub.docker.com/r/smebberson/alpine-influxdb/ and that is all I really needed. Thanks for your input along the way.

Great.


Android license status unknown

The issue which closed can't sovle my problem https://github.com/flutter/flutter/issues/22361
My env,lastest mac os,the latest flutter,the latest android studio,and java 11,when i run flutter doctor,console
[✓] Flutter (Channel stable, v1.0.0, on Mac OS X 10.13.6 17G5019, locale en-CN)
[!] Android toolchain - develop for Android devices (Android SDK 28.0.3)
    ✗ Android license status unknown.
[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
[✓] Android Studio (version 3.3)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[!] VS Code (version 1.31.1)
[!] Connected device
    ! No devices available

! Doctor found issues in 3 categories.

and try with this flutter doctor --android-licenses,console
A newer version of the Android SDK is required. To update, run:
/Users/tam/Library/Android/sdk/tools/bin/sdkmanager --update

and try above command,console
Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
    at com.android.repository.api.SchemaModule$SchemaModuleVersion.<init>(SchemaModule.java:156)
    at com.android.repository.api.SchemaModule.<init>(SchemaModule.java:75)
    at com.android.sdklib.repository.AndroidSdkHandler.<clinit>(AndroidSdkHandler.java:81)
    at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:73)
    at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
    at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
    ... 5 more

after search stackoverflow,https://stackoverflow.com/questions/47150410/failed-to-run-sdkmanager-list-android-sdk-with-java-9 try to modify sdkmanager with DEFAULT_JVM_OPTS='"-Dcom.android.sdklib.toolsdir=$APP_HOME" -XX:+IgnoreUnrecognizedVMOptions --add-modules java.se.ee',and run command again,console
Error occurred during initialization of boot layer
java.lang.module.FindException: Module java.se.ee not found

and search this,return tohttps://github.com/flutter/flutter/issues/22361
but,after double checked and tried,can't solve my problem.
wait online for help

See https://stackoverflow.com/questions/49758849/flutter-io-android-license-status-unknown

Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema

Indicates and issue with your Android SDK setup which is not maintained by Flutter.
Please consider asking support questions in one of the other channels listed at http://flutter.io/support .

My issue was resolved after installing Android SDK Command-line Tools on android studio sdk


Add exechealthz to 1.12/13 section as 1.11 or earlier

What this PR does / why we need it:
AKS wants to use 1.12.x by default for VMSS agent nodes. There will be InvalidImageName error for kube-dns/healthz without this change
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
InvalidImageName error for kube-dns/healthz without this change
Special notes for your reviewer:
If applicable:

[ ] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

/lgtm

/lgtm

This is a potentially breaking change

@tariq1890 can you elaborate?

https://github.com/Azure/acs-engine/blob/7f84bdf43c13a2ba01791d2435c1b9de747002f4/pkg/acsengine/params_k8s.go#L49

@tariq1890 that function will add that param for 1.7 and 1.8 clusters. But simply adding the entry in the map won't affect anything


Fix benchmark figure paths

It works: https://github.com/steffahn/evmap/tree/fix_benchmark_figure_paths

Good catch, thanks!


add known_failure annotation

@mambocab

Let's also let this sit for the moment, as it may be closed after tonight's 2.2 run.


JavaScript: Error: Permission denied to access property "x"

Write a short tutorial on JavaScript's Error: Permission denied to access property "x" error message, following the "How to troubleshoot Python ZeroDivisionError" example tutorial.
The tutorial should be organized as follows:
---
title: How to troubleshoot JavaScript Error Permission denied to access property "x"
author: your name
tags: [tutorial, JavaScript, troubleshooting]
publicationDate: today's date
description: Learn how to error handle the JavaScript Error, Permission denied to access property "x"
image: https://storage.googleapis.com/sourcegraph-assets/learn/headers/sourcegraph-learn-header.png
imageAlt: Sourcegraph Learn
browserTitle: Error Permission denied to access property "x" in JavaScript error handling
type: posts
---

Introduction with the error message

## Reproducing the error

Show how the error can be created.

## Solution 1

Provide a possible solution.

## Solution 2

Provide another solution.

## (optional) Solution 3

Optionally provide a third solution.

## Learn more

Search across open source JavaScript repositories that have the `NameError` to understand the message more.

<SourcegraphSearch query="Error: Permission denied to access property "x"" patternType="literal"/>

Check out more Sourcegraph Learn tutorials on [JavaScript](https://learn.sourcegraph.com/tags/javascript).

If this seems like a tutorial that you can write effectively for the developer community, please follow our Hacktoberfest 2021 contributor guidelines to proceed.

Hi, I'd like to pick this one up


[core] Support custom extensions

Define a mechanism to load, configure, and execute custom extensions.
Packaging
Extensions may be packaged in 3 ways:

single JAR file. Either the extension has no dependencies or it's an uberjar.
zip file. Contains a set of JAR files. This includes the extension plus its dependencies.
set of JAR files. This includes the extension plus its dependencies.

Location
Extensions should be placed at ${JRELEASER_HOME}/extensions/<extension-name>/. However, this location may be overridden by configuring an explicit value via the DSL
DSL
Here's how it may look like
extensions:
  foo:
    providers:
      - type: com.github.foo.MustacheFunctionProvider
        properties:
          maxLength: 20
  bar:
    directory: /path/to/the/jars
  qux:
    enabled: false

Extension foo will be loaded from ${JRELEASER_HOME}/extensions/foo. It may be packaged as foo-x.y.z.jar, foo.-x.y.z.zip, or as a set of JAR files inside that directory.
It lists an explicit type com.github.foo.MustacheFunctionProvider which requires additional settings upon initialization. These settings are defined using the properties map. There may be more than one provider type hence a list.
Extension bar will be loaded from /path/to/the/jars. It may be packaged as bar-x.y.z.jar, bar.-x.y.z.zip, or as a set of JAR files inside that directory.
Loading Mechanism
Each extension will be loaded and initialized upon bootstrap after resolving the model. Extensions will be treated as singletons per each invocation session. JReleaser will use the ServiceLoader SPI interface to locate, load, and initialize extensions.

Also consider an option for declaring GAV coordinates to download an extension and its transitive dependencies.

Released in v1.3.0 -> https://github.com/jreleaser/jreleaser/releases/tag/v1.3.0


--enable-extstore on s390x (IBM System Z mainframe architecture) fails tests

This is the result of lots of discussion/testing over on https://github.com/docker-library/memcached/pull/38 -- running the tests on IBM's s390x platform results in a test failure that generates what currently (as of the 1.8.5 release) amounts to a ~66MB log file: https://gist.githubusercontent.com/tianon/d3aa50500e22cf8686a08ae4fa2cbae1/raw/dbd5d5f501b04b95fad8fe2fc1aa666b16a1f44c/s390x-debian.log
(The same log, against Alpine Linux instead, with the same failure: https://gist.githubusercontent.com/tianon/d3aa50500e22cf8686a08ae4fa2cbae1/raw/dbd5d5f501b04b95fad8fe2fc1aa666b16a1f44c/s390x-alpine.log)
The Dockerfiles used for building/testing can be found at https://gist.githubusercontent.com/tianon/d3aa50500e22cf8686a08ae4fa2cbae1/raw/dbd5d5f501b04b95fad8fe2fc1aa666b16a1f44c/Dockerfile.debian and https://gist.githubusercontent.com/tianon/d3aa50500e22cf8686a08ae4fa2cbae1/raw/dbd5d5f501b04b95fad8fe2fc1aa666b16a1f44c/Dockerfile.alpine. :+1:

@tianon I may have fixed this.

Nice!  Re-ran the tests on s390x against https://github.com/memcached/memcached/commit/1e8d02e546a860d539d9b550ab23c4567a129f14:
https://gist.github.com/tianon/fe7624a76514e5806ccea753288ced3f#file-build-log
(It's uh, a bit large -- ~67MB of pure log output.)

@tianon https://github.com/dormando/memcached/tree/be-testfix - another attempt (via #660)

Sure thing, here's just the make test output (on commit https://github.com/dormando/memcached/commit/5d56b3c8d9f70abc2fe84ed366fac1a4770d7f8c, Debian Buster, s390x, ./configure --build=s390x-linux-gnu --enable-sasl --enable-sasl-pwdb --enable-tls --enable-extstore):
+ make test
./sizes
Slab Stats	64
Thread stats	-6368
Global stats	208
Settings	640
Item (no cas)	48
Item (cas)	56
extstore header	12
Libevent thread	216
Connection	456
----------------------------------------
libevent thread cumulative	6648
Thread stats cumulative		6432
./testapp
1..57
ok 1 - cache_create
ok 2 - cache_constructor
ok 3 - cache_constructor_fail
ok 4 - cache_destructor
ok 5 - cache_reuse
ok 6 - cache_redzone
ok 7 - stats_prefix_find
ok 8 - stats_prefix_record_get
ok 9 - stats_prefix_record_delete
ok 10 - stats_prefix_record_set
ok 11 - stats_prefix_dump
ok 12 - issue_161
ok 13 - strtol
ok 14 - strtoll
ok 15 - strtoul
ok 16 - strtoull
ok 17 - issue_44
ok 18 - vperror
ok 19 - issue_101
Signal handled: Terminated.
ok 20 - start_server
ok 21 - issue_92
ok 22 - issue_102
ok 23 - binary_noop
ok 24 - binary_quit
ok 25 - binary_quitq
ok 26 - binary_set
ok 27 - binary_setq
ok 28 - binary_add
ok 29 - binary_addq
ok 30 - binary_replace
ok 31 - binary_replaceq
ok 32 - binary_delete
ok 33 - binary_deleteq
ok 34 - binary_get
ok 35 - binary_getq
ok 36 - binary_getk
ok 37 - binary_getkq
ok 38 - binary_gat
ok 39 - binary_gatq
ok 40 - binary_gatk
ok 41 - binary_gatkq
ok 42 - binary_incr
ok 43 - binary_incrq
ok 44 - binary_decr
ok 45 - binary_decrq
ok 46 - binary_version
ok 47 - binary_flush
ok 48 - binary_flushq
ok 49 - binary_append
ok 50 - binary_appendq
ok 51 - binary_prepend
ok 52 - binary_prependq
ok 53 - binary_stat
ok 54 - binary_illegal
ok 55 - binary_pipeline_hickup
Signal handled: Interrupt.
ok 56 - shutdown
ok 57 - stop_server
make[1]: Entering directory '/usr/src/memcached'
Running basic tests with TLS
1..57
ok 1 - cache_create
ok 2 - cache_constructor
ok 3 - cache_constructor_fail
ok 4 - cache_destructor
ok 5 - cache_reuse
ok 6 - cache_redzone
ok 7 - stats_prefix_find
ok 8 - stats_prefix_record_get
ok 9 - stats_prefix_record_delete
ok 10 - stats_prefix_record_set
ok 11 - stats_prefix_dump
ok 12 - issue_161
ok 13 - strtol
ok 14 - strtoll
ok 15 - strtoul
ok 16 - strtoull
ok 17 - issue_44
ok 18 - vperror
ok 19 - issue_101
Signal handled: Terminated.
ok 20 - start_server
ok 21 - issue_92
ok 22 - issue_102
ok 23 - binary_noop
ok 24 - binary_quit
ok 25 - binary_quitq
ok 26 - binary_set
ok 27 - binary_setq
ok 28 - binary_add
ok 29 - binary_addq
ok 30 - binary_replace
ok 31 - binary_replaceq
ok 32 - binary_delete
ok 33 - binary_deleteq
ok 34 - binary_get
ok 35 - binary_getq
ok 36 - binary_getk
ok 37 - binary_getkq
ok 38 - binary_gat
ok 39 - binary_gatq
ok 40 - binary_gatk
ok 41 - binary_gatkq
ok 42 - binary_incr
ok 43 - binary_incrq
ok 44 - binary_decr
ok 45 - binary_decrq
ok 46 - binary_version
ok 47 - binary_flush
ok 48 - binary_flushq
ok 49 - binary_append
ok 50 - binary_appendq
ok 51 - binary_prepend
ok 52 - binary_prependq
ok 53 - binary_stat
ok 54 - binary_illegal
ok 55 - binary_pipeline_hickup
Signal handled: Interrupt.
ok 56 - shutdown
ok 57 - stop_server
# Some chunked item tests
./t/binary.t .................. ok
./t/getset.t .................. ok
./t/ssl_cert_refresh.t ........ ok
./t/ssl_ports.t ............... ok
./t/ssl_session_resumption.t .. ok
./t/ssl_settings.t ............ ok
./t/ssl_verify_modes.t ........ ok
All tests successful.
Files=7, Tests=43199, 50 wallclock secs ( 1.19 usr  0.07 sys +  3.74 cusr  0.37 csys =  5.37 CPU)
Result: PASS
Finished running basic TLS tests
make[1]: Leaving directory '/usr/src/memcached'
getaddrinfo(): Name or service not known
failed to listen on TCP port 45700: Invalid argument
slab class   1: chunk size        96 perslab   10922
slab class   2: chunk size       120 perslab    8738
slab class   3: chunk size       152 perslab    6898
slab class   4: chunk size       192 perslab    5461
slab class   5: chunk size       240 perslab    4369
slab class   6: chunk size       304 perslab    3449
slab class   7: chunk size       384 perslab    2730
slab class   8: chunk size       480 perslab    2184
slab class   9: chunk size       600 perslab    1747
slab class  10: chunk size       752 perslab    1394
slab class  11: chunk size       944 perslab    1110
slab class  12: chunk size      1184 perslab     885
slab class  13: chunk size      1480 perslab     708
slab class  14: chunk size      1856 perslab     564
slab class  15: chunk size      2320 perslab     451
slab class  16: chunk size      2904 perslab     361
slab class  17: chunk size      3632 perslab     288
slab class  18: chunk size      4544 perslab     230
slab class  19: chunk size      5680 perslab     184
slab class  20: chunk size      7104 perslab     147
slab class  21: chunk size      8880 perslab     118
slab class  22: chunk size     11104 perslab      94
slab class  23: chunk size     13880 perslab      75
slab class  24: chunk size     17352 perslab      60
slab class  25: chunk size     21696 perslab      48
slab class  26: chunk size     27120 perslab      38
slab class  27: chunk size     33904 perslab      30
slab class  28: chunk size     42384 perslab      24
slab class  29: chunk size     52984 perslab      19
slab class  30: chunk size     66232 perslab      15
slab class  31: chunk size     82792 perslab      12
slab class  32: chunk size    103496 perslab      10
slab class  33: chunk size    129376 perslab       8
slab class  34: chunk size    161720 perslab       6
slab class  35: chunk size    202152 perslab       5
slab class  36: chunk size    252696 perslab       4
slab class  37: chunk size    315872 perslab       3
slab class  38: chunk size    394840 perslab       2
slab class  39: chunk size    524288 perslab       2
<26 server listening (auto-negotiate)
slab class   1: chunk size        96 perslab   10922
slab class   2: chunk size       120 perslab    8738
slab class   3: chunk size       152 perslab    6898
slab class   4: chunk size       192 perslab    5461
slab class   5: chunk size       240 perslab    4369
slab class   6: chunk size       304 perslab    3449
slab class   7: chunk size       384 perslab    2730
slab class   8: chunk size       480 perslab    2184
slab class   9: chunk size       600 perslab    1747
slab class  10: chunk size       752 perslab    1394
slab class  11: chunk size       944 perslab    1110
slab class  12: chunk size      1184 perslab     885
slab class  13: chunk size      1480 perslab     708
slab class  14: chunk size      1856 perslab     564
slab class  15: chunk size      2320 perslab     451
slab class  16: chunk size      2904 perslab     361
slab class  17: chunk size      3632 perslab     288
slab class  18: chunk size      4544 perslab     230
slab class  19: chunk size      5680 perslab     184
slab class  20: chunk size      7104 perslab     147
slab class  21: chunk size      8880 perslab     118
slab class  22: chunk size     11104 perslab      94
slab class  23: chunk size     13880 perslab      75
slab class  24: chunk size     17352 perslab      60
slab class  25: chunk size     21696 perslab      48
slab class  26: chunk size     27120 perslab      38
slab class  27: chunk size     33904 perslab      30
slab class  28: chunk size     42384 perslab      24
slab class  29: chunk size     52984 perslab      19
slab class  30: chunk size     66232 perslab      15
slab class  31: chunk size     82792 perslab      12
slab class  32: chunk size    103496 perslab      10
slab class  33: chunk size    129376 perslab       8
slab class  34: chunk size    161720 perslab       6
slab class  35: chunk size    202152 perslab       5
slab class  36: chunk size    252696 perslab       4
slab class  37: chunk size    315872 perslab       3
slab class  38: chunk size    394840 perslab       2
slab class  39: chunk size    524288 perslab       2
<26 server listening (ascii)
<27 new ascii client connection.
<27 connection closed.
slab class   1: chunk size        96 perslab   10922
slab class   2: chunk size       120 perslab    8738
slab class   3: chunk size       152 perslab    6898
slab class   4: chunk size       192 perslab    5461
slab class   5: chunk size       240 perslab    4369
slab class   6: chunk size       304 perslab    3449
slab class   7: chunk size       384 perslab    2730
slab class   8: chunk size       480 perslab    2184
slab class   9: chunk size       600 perslab    1747
slab class  10: chunk size       752 perslab    1394
slab class  11: chunk size       944 perslab    1110
slab class  12: chunk size      1184 perslab     885
slab class  13: chunk size      1480 perslab     708
slab class  14: chunk size      1856 perslab     564
slab class  15: chunk size      2320 perslab     451
slab class  16: chunk size      2904 perslab     361
slab class  17: chunk size      3632 perslab     288
slab class  18: chunk size      4544 perslab     230
slab class  19: chunk size      5680 perslab     184
slab class  20: chunk size      7104 perslab     147
slab class  21: chunk size      8880 perslab     118
slab class  22: chunk size     11104 perslab      94
slab class  23: chunk size     13880 perslab      75
slab class  24: chunk size     17352 perslab      60
slab class  25: chunk size     21696 perslab      48
slab class  26: chunk size     27120 perslab      38
slab class  27: chunk size     33904 perslab      30
slab class  28: chunk size     42384 perslab      24
slab class  29: chunk size     52984 perslab      19
slab class  30: chunk size     66232 perslab      15
slab class  31: chunk size     82792 perslab      12
slab class  32: chunk size    103496 perslab      10
slab class  33: chunk size    129376 perslab       8
slab class  34: chunk size    161720 perslab       6
slab class  35: chunk size    202152 perslab       5
slab class  36: chunk size    252696 perslab       4
slab class  37: chunk size    315872 perslab       3
slab class  38: chunk size    394840 perslab       2
slab class  39: chunk size    524288 perslab       2
<26 server listening (binary)
Invalid value for binding protocol: http
 -- should be one of auto, binary, or ascii
Maximum connections must be greater than 0
Maximum connections must be greater than 0
Number of threads must be greater than 0
t/00-startup.t .............. ok
t/64bit.t ................... ok
t/ascii-auth.t .............. ok
t/binary-extstore.t ......... ok
t/binary-get.t .............. ok
t/binary-sasl.t ............. skipped: Skipping SASL tests
# Some chunked item tests
t/binary.t .................. ok
t/bogus-commands.t .......... ok
t/cas.t ..................... ok
t/chunked-extstore.t ........ ok
t/chunked-items.t ........... ok
t/conn-limits.t ............. ok
t/daemonize.t ............... ok
t/dash-M.t .................. ok
t/dyn-maxbytes.t ............ ok
t/error-extstore.t .......... ok
t/evictions.t ............... ok
t/expirations.t ............. ok
t/extstore-buckets.t ........ ok
t/extstore-jbod.t ........... ok
t/extstore.t ................ ok
t/flags.t ................... ok
t/flush-all.t ............... ok
t/getandtouch.t ............. ok
t/getset.t .................. ok
t/idle-timeout.t ............ ok
t/incrdecr.t ................ ok
t/issue_104.t ............... ok
t/issue_108.t ............... ok
t/issue_14.t ................ ok
t/issue_140.t ............... skipped: Fix for Issue 140 was only an illusion
t/issue_152.t ............... ok
t/issue_163.t ............... ok
t/issue_183.t ............... ok
t/issue_192.t ............... ok
t/issue_22.t ................ ok
t/issue_260.t ............... skipped: Only possible to test #260 under artificial conditions
t/issue_29.t ................ ok
t/issue_3.t ................. ok
t/issue_41.t ................ ok
t/issue_42.t ................ ok
t/issue_50.t ................ ok
t/issue_61.t ................ ok
t/issue_67.t ................ ok
t/issue_68.t ................ ok
t/issue_70.t ................ ok
Item max size cannot be less than 1024 bytes.
Cannot set item size limit higher than 1/2 of memory max.
t/item_size_max.t ........... ok
t/line-lengths.t ............ ok

#   Failed test at t/lru-crawler.t line 93.
#          got: 'yes'
#     expected: 'no'
# Looks like you failed 1 test of 224.
t/lru-crawler.t .............
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/224 subtests
t/lru-maintainer.t .......... ok
t/lru.t ..................... ok
t/malicious-commands.t ...... ok
t/maxconns.t ................ ok
# marithmetic tests
# mset mode switch
# starting serve stale with mdelete
# running mdelete
# trying to fail then stale set via mset
# confirm item still stale, and TTL wasn't raised.
# do valid mset
# testing quiet flag
# now purposefully cause an error
# testing mget opaque
# flag and token count errors
# pipeline test
# mget + extstore tests
t/metaget.t ................. ok
t/misbehave.t ............... skipped: Privilege drop not supported
t/multiversioning.t ......... ok
t/noreply.t ................. ok
t/quit.t .................... ok
t/refhang.t ................. skipped: Test is flaky. Needs special hooks.
[restart] Failed to read a tag from metadata file
[restart] no metadata save file, starting with a clean cache
# Set some values, various sizes.
# load enough items to change hash power level
# Load a couple chunked items
# Data that should expire while stopped.
# killed, waiting
Gracefully stopping
# reconnected
# low TTL item should be gone
t/restart.t ................. ok
t/slabhang.t ................ skipped: Test is flaky. Needs special hooks.
t/slabs-reassign-chunked.t .. ok
t/slabs-reassign2.t ......... ok
t/slabs_reassign.t .......... ok
t/ssl_cert_refresh.t ........ skipped: SSL testing is not enabled
t/ssl_ports.t ............... skipped: SSL testing is not enabled
t/ssl_session_resumption.t .. skipped: SSL testing is not enabled
t/ssl_settings.t ............ skipped: SSL testing is not enabled
t/ssl_verify_modes.t ........ skipped: SSL testing is not enabled
PORT: 45143
t/stats-conns.t ............. ok
t/stats-detail.t ............ ok
t/stats.t ................... ok
t/touch.t ................... ok
t/udp.t ..................... ok
t/unixsocket.t .............. ok
t/watcher.t ................. ok
t/watcher_connid.t .......... ok
t/whitespace.t .............. skipped: Skipping test because this does not appear to be a memcached git working directory

Test Summary Report
-------------------
t/lru-crawler.t           (Wstat: 256 Tests: 224 Failed: 1)
  Failed test:  192
  Non-zero exit status: 1
Files=78, Tests=104953, 374 wallclock secs ( 6.47 usr  0.29 sys + 11.22 cusr  2.51 csys = 20.49 CPU)
Result: FAIL
make: *** [Makefile:2221: test] Error 1

is that lru-crawler.t failure consistent? Never seen that before..
It seems to pass the extstore tests now though? Those always failed before.

Good point -- not consistent.  I ran it again and it's completely successful now. :smile:

Thanks! I've never seen that test flake but I'll check to see if it's async and add a retry loop if necessary.

closing this out finally. I added a separate change for the lru crawler test as it was checking a status variable outside of a memory barrier.

We are successfully built on s390x! (other platforms still pending, but they haven't been failing :sweat_smile:)
https://doi-janky.infosiftr.net/job/multiarch/view/images/view/memcached/
Thanks for your efforts!! :+1:


merge package template from Kronos-Tools/npm-package-template

Updated standard to latest version

Current coverage is 88.00% (diff: 100%)

Merging #36 into master will not change coverage

@@             master        #36   diff @@
==========================================
  Files             1          1
  Lines            25         25
  Methods           6          6
  Messages          0          0
  Branches          3          3
==========================================
  Hits             22         22
  Misses            3          3
  Partials          0          0

Powered by Codecov. Last update bd25c87...c766c0b


Add and expose framework_agreement_version field to framework model

Added framework_agreement_version field to framework model
Migration also sets special value of 'v1.0' for g-cloud-8 framework_agreement_version
Updated relevant test_all_frameworks_are_returned test

Upgrade and downgrade tested.
All looks good :+1:


mssql export creates invalid syntax

Exporting Azure mssql data results in:
INSERT INTO [ffctower-dev].dbo.airports (code,name,createdAt,updatedAt,startOffsetHrs,endOffsetHrs) VALUES  ('ATL','ATL',2018-03-26 16:04:40.867 +00:00,2018-03-26 16:04:40.867 +00:00,'-1','4')
Which fails on the dates at "16:"

We recently patched SQL generation routines so now they use native data formats.
This should be fixed in 5.0.4, please verify.