Logged events are not flushed using useStatsigClient and

The following component works correctly in a React app that has a client provider using StatsigProvider higher up the tree. When StrictMode is enabled, however (which is the default in Next.js > 13.4), the log queue never gets flushed, and the events logged by the click button never get logged.
'use client'

import { useStatsigClient } from '@statsig/react-bindings'
import { useState } from 'react'

const rand = () => Math.random().toString().slice(2)

export const ClientEventsTest = () => {
  // side note: useStatsigClient() returns a new object each time, which can lead to all sorts of bugs when used directly (`client = useStatsigClient()`)
  const { client } = useStatsigClient()
  const [pageViewId] = useState(rand)
  const [clicks, setClicks] = useState(0)

  return (
    <button
      className='btn btn-primary' onClick={() => {
        const _clicks = clicks + 1
        setClicks(_clicks)
        client.logEvent('test-event', 'button-click', { random: rand(), pageViewId, clickCount: String(_clicks) })
      }}
    >Clicks: {clicks}
    </button>
  )
}

Thanks for the report, we are looking into it

Hmm this seems related to your other report: https://github.com/statsig-io/js-client-monorepo/issues/12
Are you seeing the following warning:
[Statsig] Creating multiple Statsig clients with the same SDK key can lead to unexpected behavior. Multi-instance support requires different SDK keys.

React strict mode renders everything twice, leading to multiple StatsigClient instances.
I think this is causing issues with the useStatsigClient hook returning the original instance which no longer has the background flush timer running as we clear it when we detect it is not the 'most recent' created instance.

I'm not seeing that warning, but I can see that multiple instances are being created. I thought it was only being created once due to React's console.log suppression, which I thought had been removed, but apparently the version of next that we're on is still holding on to that "feature". Incredible that useMemo doesn't actually do what it claims to do in Strict mode (at least on the version that we're on, which admittedly is out of date).
Odd that I'm not seeing the warning you mentioned, even when working around (const realConsoleLog = window.console.log) the log suppression issue.

Ah, yes, I knew this but forgotten... useMemo isn't guaranteed to only run once, and so strict mode runs it twice, while suppressing the logs the second time. I'll fix my code to use a ref, and suggest you guys update your React docs to do the same.

I was also surprised that useMemo is suggested in the docs. The way other libraries do (e.g. react-query) is using useState like:
 const [client] = useState(() => new StatsigClient(DEMO_CLIENT_KEY, { userID: 'a-user' }));

@Mitelak I think that's best, and what I went with as well, although I mentioned using a ref above.

So I dug into it. Because strict mode is renderering twice, its causing the shutdown method here to be called. This is killing the background flusher in EventLogger.
Because the background flusher is currently being started during construction, there is no way to start it again once it has been shutdown.
I am working on a fix now to address this and get it all working with strict mode enabled.

@daniel-statsig I found the same digging into it on Friday afternoon. Thanks for working on a fix.

@bgmort, I published 1.7.0 which contains a fix for this (https://github.com/statsig-io/js-client-monorepo/releases/tag/1.7.0). If you are able, can you pull it and let me know if it resolves the issue?
Note that the SDK won't auto shutdown through the StatsigProvider anymore. You may want to do something similar to this sample: https://github.com/statsig-io/js-client-monorepo/blob/1.7.0/samples/next-js/src/utils/useBootstrappedClient.tsx#L19-L28

@daniel-statsig I tried but it didn't work for me. In your useBootstrappedClient pattern, the init happens in a useEffect, the values aren't set on the server render or the initial client render, so I get all false values on the initial render.
I was able to get it to work with some tweaks, but it's fairly messy. We're considering turning off Next's strict mode option and inserting the StrictMode component ourselves below the providers in the tree.


bitwarden_rs-vault: 2.17.1 -> 2.18.1b

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/dani-garcia/bw_web_builds/releases.
meta.description for bitwarden_rs-vault is: "Integrates the web vault into bitwarden_rs"
meta.homepage for bitwarden_rs-vault is: "https://github.com/dani-garcia/bw_web_builds"
meta.changelog for bitwarden_rs-vault is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

directory tree listing: https://gist.github.com/29d1df1fc31f8757402d07f5f9db0a1d

du listing: https://gist.github.com/6e7d06abc62691633fb253d628607618

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

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
bitwarden_rs-vault

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/yga8kg08kw6w2ngfik9rpdcxw3naip31-bitwarden_rs-vault-2.18.1b \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/yga8kg08kw6w2ngfik9rpdcxw3naip31-bitwarden_rs-vault-2.18.1b
ls -la /nix/store/yga8kg08kw6w2ngfik9rpdcxw3naip31-bitwarden_rs-vault-2.18.1b/bin

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

1 package built:

bitwarden_rs-vault

Maintainer pings
cc @msteen for testing.

Result of nixpkgs-review pr 112471 at d63af470 run on aarch64-linux 1

1 package built:

bitwarden_rs-vault

1 suggestion:

warning: unclear-gpl
gpl3 is a deprecated license, check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/tools/security/bitwarden_rs/vault.nix:25:5:
   |
25 |     license = licenses.gpl3;
   |     ^

Tested on my server.


Use minder-config for rotation job

Summary
I missed saving this somehow.
Change Type
Mark the type of change your PR introduces:

[x] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 52.336%. remained the same
when pulling 4b3892108d7a6030499e0599e1af6ca1d2bb6dd6 on fix-config-rotate
into bebb68983b73a1b7b43ef9fcd6ca75f86d306e43 on main.


Asymmetric Timestamp handling

Scenario:
Ingest Infoton with different format of dateTime:
"2011-02-7T00:01:00.000"
"2011-02-17 00:01:00.000"
"2017-03-07T14:22:42Z"
"2017-03-07T14:22:42"
"2017-03-07 14:22:42"

Infoton for example too:
<http://PATH/hasPermId> "5000672051" .
<http://PATH/hasDateOfIncorporation> "2011-02-17T05:00.000Z"^^<http://www.w3.org/2001/XMLSchema#date> .
<http://PATH/hasIPODate> "2011-02-17 00:01:00.000"^^<http://www.w3.org/2001/XMLSchema#dateTime> .

CM-Well will need to correct them by http://www.w3.org/2001/XMLSchema#date to mangling Date.
The result
Date fields were not written correctly, and mangling was found duplicate a String AND Date.

Could not reproduce 😔
$ curl localhost:9000/_in?format=ntriples --data-binary '<http://example.org/Guy><http://PATH/hasIPODate> "2011-02-17 00:01:00.000"^^<http://www.w3.org/2001/XMLSchema#dateTime> .'
{"success":true}

$ curl "localhost:9000/meta/ns/AqNb2A/hasIPODate?format=json&pretty"
{
  "type" : "ObjectInfoton",
  "system" : {
    "uuid" : "0c68f6813ed9e4def656cf0d05850835",
    "lastModified" : "2018-06-14T13:02:04.984Z",
    "path" : "/meta/ns/AqNb2A/hasIPODate",
    "dataCenter" : "lh",
    "indexTime" :<PHONE_NUMBER>088,
    "parent" : "/meta/ns/AqNb2A"
  },
  "fields" : {
    "mang" : [ "d" ]
  }
}

This issue will be handled as part of the http://www.w3.org/2001/XMLSchema#date issue.
Currently ..#date is being treated as String rather than date.
@MoriaYechiel please close this issue when you open the two new related issues.


Autofocus Issue

Step 1: We disabled the autofocus.
Step 2: We enabled it again. But the auto focus is not working.
Also,
Tap to focus is not consistent.

Camera1, Camera2?
Are you calling it with preview/stream/record started? If not, it is ignored.
What do you mean with consistent? not working sometimes times?

We are using camera2.
We are using button for toggling the autofocus(enable/disable). preview state and run time streaming state.
Sometimes it's not working. This will happen when the auto focus is disabled but the user taps to focus.

Hi @pedroSG94, Any update on this? Could you able to recreate this?

Hello,
I was doing tests but I'm not able to reproduce your case as you described.
I found a bug that if you are using tap to focus, enableAutoFocus stop to work in camera2, and I fixed it. Call enable and disable autofocus multiple times without use tap to focus was working fine.
Commit:
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/commit/432d69c5f613ddb2754d82919292a8aec8c468b1
I tested in 2 devices with the same result.
To know if enable/disable autofocus was success you can call:
rtmpCameraw.isAutoFocusEnabled();

If not success this means that something happens and normally it is that you called it without camera started

Thanks @pedroSG94 This fix is working. But when we disable the auto focus, screen gets blurred. Is there any possibilities to fix this issue?

It isn't an issie. Disable autofocus is set focus to infinity, so it is working as expected.


feat: convert hugo docs workflow calls to use Taskfile task

Description
This pull request changes the following:

convert hugo docs workflow calls to use Taskfile task
fixed some eslint errors
updated github workflow to use taskfile

Related Issues

Closes #639

:tada: This PR is included in version 0.31.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


New Offsets for June 6th, 2023

Works for me?

I made a fork just for this. Most of the offsets didn't move or moved only 16 bytes. I assume because the code didn't really change? It would make sense if all they did was add a new folder for Heroic Verse vol 2.

Seems good to me as well, thanks for the help.


[LiveComponent] Uncaught TypeError: currentLevelData is null

Hi,
I'm trying to use select2 js with LiveComponents.
I'd like to save the select value when it change on component using
this.component.{liveProp} = data

This use return an error: Uncaught TypeError: currentLevelData is null
I removed a lot of lines to test.
There is my js code:
import { Controller } from '@hotwired/stimulus'
import $ from 'jquery'
require('select2')

export default class extends Controller {
    connect () {
        this.element.addEventListener('live:connect', (event) => {
            this.component = event.detail.component

            this.component.on('render:finished', (component) => {
                this.addSaveSelectValueOnChangeEvent($('.selectTag'))
            })
        })
    }

    addSaveSelectValueOnChangeEvent (elements) {
        for (let i = 0; i < elements.length; i++) {
            const that = this
            const target = elements[i]
            $(target).select2({
                tags: true,
                tokenSeparators: [',', ' ']
            })

            console.log(that.component.firewalls)

        }
    }

Hi there!
Sorry for the slow reply. Hmm, I'm guessing that.component.getData('firewalls') also gives the same error? What does your LiveComponent look like? I assume you have a firewalls LiveProp? Can you post a stack trace for the error?
It definitely could be a bug. At the very least, it's an unfriendly error message that needs improving.


[BUG]: TLS illegal parameter error when upgrading CSI PowerFlex v2.9.1 to v2.10.0

Bug Description
User currently using csi2.9.1( powerflex - vxflexos )  and when upgrade the version to csi2.10.0 , we had an tls illegal parameter error and the same has been attached here
Host OS : Ubuntu 20.04.6 LTS
Kernel : 5.4.0-172-generic,
User shared Additional info if this helps:
how to update cipher in vxflexos config ?
Below is the CIPHERS Configured on PowerFlex Gateway Server.
The ciphers used by the GW's embedded Tomcat webserver are listed in /opt/emc/scaleio/gateway/conf/server.xml line 116 (the ciphers attribute of the SSL Connector definition)
ciphers="xxxxxxxxxxx,yyyyyyyyyyyyyy,xxxxxxxxxxxxxxxxxxxxxxxxxx,zzzzzzzzzzzzzzzzzzzzzz"
Logs
NA
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
Update the cipher suites on the csi-powerflex cluster and upgrade the driver.
Expected Behavior
Driver should be in running state.
CSM Driver(s)
CSI-powerflex v2.10.1
Installation Type
No response
Container Storage Modules Enabled
No response
Container Orchestrator
k8
Operating System
Ubuntu 20.04.6

Unrelated to CSM so closing this issue.

@adarsh-dell - I'm re-opening this issue to get a better understanding if this failure is dependent on what is configured for ciphers in the GW configuration.  This seems to be happening on the network connection between the driver and the GW server.  Please provide additional information on if this error only happens in cases where the GW server is configured a certain way.  Thank you.

Investigation and Case Study on TLS Handshake Failure
Overview
Below is the observations and case study conducted during the investigation of a TLS handshake failure between an HTTP client (driver) and the PFX gateway server. The aim is to understand the root cause of the issue and explore potential solutions.
TLS Configuration in HTTP Client
The HTTP client in this scenario can set the TLS configuration during client creation, either by specifying a set of cipher suites or by leaving this field unset to use the default cipher suites. The crypto/tls package in Go provides the CipherSuites() function, which returns only secure cipher suites.
Example: Setting TLS Configuration in HTTP Client
package main

import (
    "crypto/tls"
    "net/http"
)

func main() {
    tlsConfig := &tls.Config{
        CipherSuites: []uint16{
            tls.TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
            tls.TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
        },
    }

    client := &http.Client{
        Transport: &http.Transport{
            TLSClientConfig: tlsConfig,
        },
    }

    resp, err := client.Get("https://example.com")
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()
}

TLS Configuration on Server Side
The PFX gateway server allows users to configure cipher suites by editing the server.xml file. Although the server comes with predefined secure suites, users can manually update this configuration to meet specific security requirements.
Cipher Suite Concept
For a TLS handshake to succeed, there must be at least one mutually supported cipher suite between the client and server. If such a cipher suite exists, the handshake should proceed successfully, and the mutually supported suite will be used for further secure communication.
Observations and Findings

Despite having a matching cipher suite configured on both the client and server sides, the TLS handshake was failing.
The same TLS configuration and cipher suite worked successfully with a dummy Go server, indicating that the issue was not with the client or driver side.
Using the curl utility to explicitly specify the cipher suites also resulted in handshake failures, further suggesting an issue on the server side.

Conclusion
The investigation revealed that the problem likely lies with the PFX gateway server. Even though the client and server had mutually supported cipher suites, the handshake was failing due to server-side issues. And the issue is seen with few suites only and is working fine with other suites. We have tested the upcoming i.e. CSI v2.11.0 driver with 3 versions of array after setting only secured suite and it was working fine and filed a ticket against PFX with our findings.
Recommendations

Server Configuration Review: Ensure the PFX gateway server configuration is correctly set and there are no discrepancies in the server.xml file.
Testing with Different Servers: Test the client with different servers to confirm the server-side issue.
Debugging Server Logs: Review server logs to identify any errors or misconfigurations that could cause the handshake failure.
Server Update: Consider updating the server software to the latest version to fix any known issues related to TLS handshakes.

Additional Resources

Go TLS CipherSuites Documentation
TLS Handshake Process

References

Go HTTP Client Configuration
OpenSSL Cipher Suites

Thanks,
Adarsh
@gallacher I Hope this much of information will be fine.


Add meBridge.isFluidCrafting

Describe your idea
Follow-up on #430, to the tune of isItemCrafting.
It's now possible to queue fluids for crafting - thank you! My use-case is (unsurprisingly) auto-crafting. The missing isFluidCrafting method means we can't skip submitting the crafting job if there's already a job in progress.
Linked Issues
#430

AdvancedPeripherals-1.19.2-0.7.29r.zip
A bit late, but if you want, you can test them here. I Added a isFluidCraftable and isFluidCrafting function
unzip the file before using it


Create define to configure the factor that fonts are multipled by while prerendered

I found increasing this makes the text a little nicer. I tried applying roundTranslation to the visual but it doesn't look as good. It would be a better solution if we were dealing with pixel perfect fonts. Some more work needs to be done in text-land.

Done with daa219e


Firebird 3.0 server connection

I can't connect a remote firebird 3.0 server (localhost works fine!).
I receive an error:
Incompatible wire encryption levels requested on client and server [SQLState:28000, ISC error code:335545064]
Incompatible wire encryption levels requested on client and server [SQLState:28000, ISC error code:335545064]
Incompatible wire encryption levels requested on client and server
Incompatible wire encryption levels requested on client and server
Any help?
THIA
Marcio

I have found the problem.
Modifing firebird.conf: wirecript = enable

I found the problem.
Modifing the file firebird.conf -> WireCrypt = Enabled


feat: support is_secret boolean on environment variables

This pull request adds a new is_secret boolean to the createEnvVars and updateEnvVar endpoints.

@codebyuma, what do you think of the descriptions here?

Hey @jasonbarry, I'm going to pass this to @jmarlena who'll be helping with this project 🎉

Note: changed from feat: to chore(docs): as the generated clients technically supported this already (as they pass anything received in the payload body to the API), so this PR is more of a docs change than a functionality change.


Switch to using Vec for ble_ident

(this needs manual testing which I'm hoping I can do by tomorrow)

@simon Any chance we can merge this before #22 ?

Closing as this now doesn't have the full fixes for ble_ident. Will do the work directly in #22


KOGITO-4376 Review license header validation during maven build

Centralize license header settings in kogito-build-parent bom
Use checkstyle to validate license header based on regex ( no git dependency )
For now Checkstyle will log errors in console but not break the build, this will allow changes to be pushed later on before we turned it on
For automatically formatting classes we will still use license-maven-plugin. To format code please run:  mvn com.mycila:license-maven-plugin:format

Assembly:

https://github.com/kiegroup/kogito-examples/pull/553
https://github.com/kiegroup/kogito-runtimes/pull/1046

I quickly send new conventions in this PR https://github.com/kiegroup/kogito-runtimes/pull/1049

@danielezonca that is not part of the JIRA i worked on this ;), we should not mixed it IMHO

@danielezonca added instructions to contributing guide.

jenkins please retest this

jenkins please retest this


npm

What happened to the keen-js module on npm (https://www.npmjs.com/package/keen-js)? We've been using it and now all of a sudden everything stopped working.

+1 ..switching to https://www.npmjs.com/package/keen.io but this is a real doozy...

It seems that 2.3.0 is there, but none of the earlier versions are, any longer.

@kesla @ablearcher9 @paulmelnikow sorry about that, we had some issues with the latest deploy, and will get this fixed up asap. Can you all elaborate on what you're seeing now? I want to make sure we get all of the issues covered.

I can't install e.g. 3.2.8 from npm.
$ npm info keen-js | grep 'versions:'
  versions: '3.3.0',

That should be a list which includes all the old versions.

Seeing the following error in CircleCI builds:
ERR! fetch failed https://registry.npmjs.org/keen-js/-/keen-js-3.2.4.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404

As of this morning, this repository no longer has a 3.2.8 tag. Can you restore it? Our build process depends on being able to pull this code. It's disruptive when versions just disappear.
I see 3.2.5 is now in npm though, so that's good.

@kesla @ablearcher9 @paulmelnikow @TaylorBriggs we're super sorry about this! The package was mistakenly unpublished and all but a few versions were dropped. We asked our NPM friends if it was possible to restore those versions, and unfortunately it was not :(
As a work-around, I've republished these latest versions, and can republish other older versions by request. Here is what's available now:

v3.2.5
v3.2.7-r
v3.2.8-r
v3.2.9-r
v3.3.0

Added messaging around this, pointing back to this issue thread.


Document SchemaRegistryClient properties

Currently, the documentation for the SchemaRegistryClient properties is missing. Especially the one with spring.cloud.stream.schemaRegistryClient.endpoint.
Thanks to the StackOverflow question

Duplicates #878


Is it possible to train multiple motions at once

hey, I took a cursory look at your code, i see   envs/reference_motion.py    Line 71  : " for motion_file in self.motion_files: "
Does this mean that I can specify multiple motions to train at the same time? If so, what would the command look like?
Thanks a lot.

Yes. Actually, we also report the performance of our implementation of multiple motion training in the paper (Table 3).
Just pass multiple motion files to the iccgan.py for training. For example,
python iccgan.py walk kick --rank 0 --world_size 8
...
A thing needs to pay attention to: because ICCGAN depends on given poses to decide action (next pose), it may be confused if there are multiple reference motions sharing some very close pose sequences.

thanks, Your work is so cool that I'm confused as to why there are so few stars hhhhhhh


Update DisplayEnumerates in ExampleTypes.cpp to take kind into account

Just a small fix to one of the examples. I noticed that the existing code can end up printing out invalid data. I unfortunately cannot share the PDB that is causing this but the issue is resolved by considering the kind of the field record.

Thanks Sebastian!


Not all nodes return from long list

Puppeteer version: 1.3.0
Platform / OS version:  Mac OS 10.11.6
Node.js version: 8.9.4

What steps will reproduce the problem?
When iterating on log list of children not all nodes are returned.
logitems = await page.evaluate((sel) => {
        let element = document.querySelector(sel);
         return element.children.length;
     }, '#log > div > div.log.scroll');
console.log('got logitems:', logitems); // return 1000

const LOGITEM_SELECTOR = '#log > div > div.log.scroll > div:nth-child(INDEX) > span.message';
for(var i = 3; i <= logitems-3; i++)  {
        let logitem = LOGITEM_SELECTOR.replace("INDEX", i);
        console.log(logitem)
        let dat = await page.$eval(logitem, el => el.innerHTML).catch(e => {console.log(e);});
}

The code above stop on any i > 200 and produce an error:
Error: failed to find element matching selector "#log > div > div.log.scroll > div:nth-child(215) > span.message"
This behaviour is very similar to what happens when inspection nodes in Chrome - when dealing with very long list inspector produce a dialog message "Show All nodes".

There's no code in pptr that would cause this kind of behavior. You either found a bug in webplatform/devtools protocol, or something fishy going on with your website. It's impossible to figure unless I'll be able to reproduce this.
Please refile with a decent repro.


no_beats_prefix attribute not working

Environment

Terraform version: v0.12.23

Graylog version: 3.2.3

terraform-provider-graylog version: latest

OS (client side): Ubuntu Bionic

Overview
Importing a beaver input or creating a new beaver input with attribute no_beats_prefix is failing
Expected behavior
It should work
Actual behavior
It doesn't
How to reproduce
Importing existing input
tf import graylog_input.beat 5ebd299946e0fb0012d44b6c
graylog_input.beat: Importing from ID "5ebd299946e0fb0012d44b6c"...
graylog_input.beat: Import prepared!
  Prepared graylog_input for import
graylog_input.beat: Refreshing state... [id=5ebd299946e0fb0012d44b6c]

Error: Invalid address to set: []string{"attributes", "0", "no_beats_prefix"}

trying to create a new input
resource "graylog_input" "beat" {
  title  = "test"
  type   = "org.graylog.plugins.beats.Beats2Input"
  global = "false"

  attributes {
    bind_address          = "<IP_ADDRESS>"
    port                  =  5044
    recv_buffer_size      = 262144
    no_beats_prefix = false
    decompress_size_limit = 8388608
  }
}

tf plan
Error: Unsupported argument
  on beat.tf line 10, in resource "graylog_input" "beat":
  10:     no_beats_prefix = false

An argument named "no_beats_prefix" is not expected here.

Thank you for your feedback.
Probably you are using not https://github.com/terraform-provider-graylog/terraform-provider-graylog (terraform-provider-graylog) but https://github.com/suzuki-shunsuke/go-graylog (go-graylog).
Please see the following document.
https://terraform-provider-graylog.github.io/#/?id=relation-to-go-graylog
Your example is invalid for terraform-provider-graylog.
Please reinstall the provider from https://github.com/terraform-provider-graylog/terraform-provider-graylog/releases and update the configuration.
AS IS
  attributes {
    bind_address          = "<IP_ADDRESS>"
    port                  =  5044
    recv_buffer_size      = 262144
    no_beats_prefix = false
    decompress_size_limit = 8388608
  }

TO BE
  attributes = jsonencode({
    bind_address          = "<IP_ADDRESS>"
    port                  =  5044
    recv_buffer_size      = 262144
    no_beats_prefix = false
    decompress_size_limit = 8388608
  })

I have confirmed that I can create and import the following example.
resource "graylog_input" "beat" {
  title  = "test"
  type   = "org.graylog.plugins.beats.Beats2Input"
  global = "false"

  attributes = jsonencode({
    bind_address          = "<IP_ADDRESS>"
    port                  = 5044
    recv_buffer_size      = 262144
    no_beats_prefix       = false
    decompress_size_limit = 8388608
  })
}

Thank you.

Yes my bad, I somehow used the wrong provider binary, issue is fixed applying your changes


Update https://bitcoinops.org/workshops/ with details of the Paris workshop

Should include:

dates
venue
topics

@jamesob

You think we should wait until afterwards to publish the venue? Sorta seems like a needless security risk to put it out there publicly before the event.


ITO flow: Add checkbox for non-US citizen message

Add 1 choice: "I am no US citizen"
add js validation, checkbox must be selected

Yeah, it's in now. But I need to somehow overrule the error message that "you need at least two choices in a single selector". Do we change the message flow designer or make a work-around here?

Lucas will update that check

Great. I will look into "add js validation, checkbox must be selected" once that is done. Thanks!

Just use a multi-select widget instead of single-select, with one option. Having only one option is allowed there.
For the validation add this in the textfield that you get when clicking 'Open validation editor':
function run(result) {
    if (!result.value) {
        return 'You must select the checkbox';
    }
    return true;
}

Thanks!
Multi-select done, awaiting fix to be able to change validation code.

Done and checked.


API sometimes returning extreme values

Describe the bug
Noticed this morning that the API sometimes is returning really extreme values for certain data points like apparentTemperature, humidity and temperature.
I also noticed that the currently and minutely data has precipProbability returning -999 and visibility is always returning 0.

Expected behavior
API should not return extreme values
Actual behavior
API is returning extreme values
API Endpoint
Production
Location
Barrhaven, Ontario
Other details
No response
Troubleshooting steps

[X] I have searched this repository and Home Assistant Repository to see if the issue has already been reported.
[X] I have read through the API documentation before opening this issue.
[X] I have not included my API key anywhere in my issue.
[X] I have written an informative title.

@alexander0042 I think this might be fixed now? I wonder if the cause was bad data being integrated into one of the servers which is why it didn't happen all of the time?

Sorry about this! It was a glitch in the healthcheck that kept restarting things, but all better now.


[FIX] Add bundling sap-ui-core-noJQuery.js and sap-ui-core-noJQuery-dbg.js

Fixes https://github.com/SAP/ui5-builder/issues/192

Coverage increased (+0.2%) to 84.848% when pulling 49e04b8a6c4eebfc7f598d3b8bfabcdcefd996b3 on add-bundle-sap-ui-core-noJQuery into 3bf0f56097163ad04b3dfd1e9efab40ccd3607b5 on master.

Will be merged as https://github.com/SAP/ui5-builder/pull/235


style updates on comment index and preview

Style buttons and spacing on Comment Preview
Comment Index: Update "x" to "remove" for better readability until icons come in
Hide Review button if there are no comments in the Index

I added a few very minor comments on the diffs, but this LGTM!


Add backport of fnameescape().

The backport was added in order that there might be no fnameescape() at less than 7.1.299 version of vim.

Hey @kawaz
The only concern I have atm is the way how this patch is described

there might be no fnameescape

(I'm not native english spear, so)  from what I see it looks like there's no enough certainty whether it's an issue or not.
Just double checking to make sure we're on the same page, as there were no actual issues regarding backward incompatibility so far...unless that's the one )
I'll play with it once i have a spare minute...
Thank you!

Closing, as haven't hear from u

Hi there, I have a version of vim on my uni servers of VIM - Vi IMproved 7.1 (2007 May 12, compiled Jul 17 2007 15:47:48)
It is missing fnameescape. I believe adding this code might allow me to run Vundle on this vim.


STATICFILES_DIRS warnings

WARNINGS:
?: (staticfiles.W004) The directory '/Users/dwiga/Playground/dwilab/silvertech/src/public' in the STATICFILES_DIRS setting does not exist.
?: (staticfiles.W004) The directory 'static/dist' in the STATICFILES_DIRS setting does not exist.
To Reproduce
appeared soon after running the app python manage.py runserver
Expected behavior
No issues appeared
Desktop (please complete the following information):

OS: Mac OS X

How to fix the issue? something I need to do?

simply add dist/ folder inside static/ folder and the warning will gone.

simply add dist/ folder inside static/ folder and the warning will gone.

thanks


Portable dependency

Hi,
Any plans to add a portable dependency?
I'm the author of the SpriterDotNet library and I plan to add UV as a renderer in addition to MonoGame. Also, I'd like to create a portable library and publish it to NuGet (similar to what I've done for MonoGame) but I can't do it at the moment since there's no portable UV dependency.
Btw, great work with UV!
Cheers

Portable Class Libraries are unlikely to happen, given that PCLs aren't really supported by Microsoft anymore anyway, but support for .NET Standard probably will at some point. I haven't done much research into how much effort would be required, or if .NET Standard even supports all of the features I require at this point, so I can't give a time frame for when it might happen.
Thanks for your kind words. 😄

I spent a little bit of time experimenting with things today to get an idea of what would be required to support .NET Standard. There are some things I can do immediately to make the transition easier, and those will probably go in the next major release of Ultraviolet.
However, I think I'm going to be sticking with my original plan of waiting for the release of .NET Standard 2.0 before I port Ultraviolet. Given how big of a change it looks like it's going to be between 1.0 and 2.0, it doesn't seem sensible to go to the effort of updating my entire codebase right now.
Once .NET Standard 2.0 is out and supported by all of Ultraviolet's key platforms (Windows, Linux, macOS, iOS, Android), I will almost certainly be releasing a compatible version of Ultraviolet soon thereafter.

To be honest I haven't even considered .NET Standard yet but after taking a look it seems that the 2.0 version will come soonish and hopefully will allow to properly develop cross-platform libraries.
Anyway, waiting for it makes perfect sense. Thanks for looking into it.

I know it's been a while, but I'm working on .NET Standard 2.0 support now in the netstandard feature branch. Everything seems to be coming along well, so I'll be finishing that up today and tomorrow and the new assemblies will be included in the 2018.01 release.


Upgrade Linux Kernel for flatcar-3510 from 5.15.122 to 5.15.123

Subject says it all.

See instead https://github.com/flatcar/scripts/pull/1042


Error on dynamic recompilation

dotnet version: 6.0.100-preview.6.21355.2
OS: Windows 10
osu-framework: 2021.728.0
I created a default osu-framework project using a template with a spinning box and tried to stop the rotation (by commenting the corresponding line) while running visual tests in debug mode (no debugger attached). However, the dynamic recompilation failed (the console log is attached to this issue). Installing NuGet.ProjectModel and System.ComponentModel from the NuGet site doesn't seem to help.
log.txt

Possible duplicate of https://github.com/ppy/osu-framework/issues/4512
If you're using an installed version of dotnet that's managed by a version manager like asdf, it does not install all the required dependencies and you should use the system provided dotnet or download and install manually from the dotnet website.

I do not use any version manager though. I reinstalled dotnet from the microsoft site just in case, and the problem is still there (same exception is thrown).

Would you be able to post your system specs and the version of dotnet you are running?

I edited the comment to include the mentioned details.

I would try downgrading to use dotnet 5.x instead of dotnet 6-preview. I don't believe the framework has been tested to work on dotnet 6 yet.

I downgraded; unfortunately, the error perseveres. Manual installing of packages doesn't help still.

I've looked into this some more and it looks as if having the template game target net5.0 alongside netstandard2.1 fixes this, but I have no idea why. Upon adding some logging in RoslynTypeReferenceBuilder, something seems to trigger the game project into attempting to load System.ComponentModel.Composition, which somehow works with lazer (even though it doesn't target net5.0 explicitly), but fails with the templates.
In the end the game seems to find the dll in /usr/share/dotnet/shared/Microsoft.NETCore.App/5.0.8/System.ComponentModel.dll which is a bit weird. Maybe the project has to be aware of net5.0's existence to see some assembly redirects or something? No idea.

In my case targeting net5.0 alongiside netstandard2.1 also fixes the issue.

So after the .NET 6 bump dynamic recompilation stopped working entirely everywhere for me (as in, not only in templates as described above), with
[runtime] 2022-02-17 21:26:47 [error]: Error with dynamic compilation!
[runtime] 2022-02-17 21:26:47 [error]: System.IO.FileLoadException: Could not load file or assembly 'NuGet.ProjectModel, Version=<IP_ADDRESS>0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. Could not find or load a specific file. (0x80131621)
[runtime] 2022-02-17 21:26:47 [error]: File name: 'NuGet.ProjectModel, Version=<IP_ADDRESS>0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

Is anyone else seeing this? After bumping the package in question (as well as Microsoft.CodeAnalysis.* packages, as that started spewing next), and fixing a few new compiler warnings, recompilation started working again - but I am curious whether it's something with my box or it is just plain broken.
Changes that make recompilation work again for me are on the following branch to preview: https://github.com/ppy/osu-framework/compare/master...bdach:dynamic-compilation-net-6?expand=1

IIRC I was getting this also on .NET 5, so I just wrapped the resolver in a try/catch block if an assembly is not found.

so I just wrapped the resolver in a try/catch block if an assembly is not found.

that is... not a solution by any means.

While I was testing my DrawVisualiser extension, this recompilation error occurred:

and this one is off topic when it comes to this issue thread.

so I just wrapped the resolver in a try/catch block if an assembly is not found.

that is... not a solution by any means.

I'm actually going to backtrack on this slightly because while installing new packages helped framework-side, on a game-side framework checkout there are more problems with missing SQLite.PCL binaries and that may not be so easy to fix properly. So adding a fallback catch path (with appropriate logging) may be best at least for now?


Make subscriber class

How to publish to topic to test functionality:
ros2 topic pub /blah_blah  geometry_msgs/PoseStamped '{ header: { frame_id: "/map" }, pose: { position: { x: 0.25, y: 0 }, orientation: { x: 0, y: 0, z: 0, w: 1 } } }'

Looking into if there is already a mechanism to associate a widget with a node:
Found this from PerkLab bootcamp - breakdown of data, display, storage MRML nodes:

Example (transform node)

TODO:
[] organize the files (see notes) - Laura
[] look at vtkNew for templated classes - Anton
[] add vtk conversion methods and test in python (PoseStamped -> vtkMatrix4x4) - getLastMessage returns a vtkMatrix that you can actually manipulate (right now it's yaml) - Laura
[] what is the mechanism to add a widget for a subscriber node? (can't be generic), can we create one for the string (label - that refreshes) - eg. right click (edit properties)

to create a subscriber from the python console enter the following:
ros2 = slicer.modules.ros2.logic()
ros2.CreateNewSubscriber('/mySub', 'pose')
First argument is the name, second is the type of subscriber (right now it's setup for 'string' or 'pose')


add codes for predicting pose with 3D pretrained model

Ref #29

Great, thanks @Marcovaldong! @heury, since you asked for this feature, would you mind testing if it works for you?

@rohitgirdhar It is working nicely. Thanks @Marcovaldong

Cool, thanks!


assistant flow setup fails with character limit here

Tried the vanilla sample, and updated my openai uri and key details in .env. However setup.py call failed. Any idea what to change in sample? Perhaps, "sales_data_insights" function description content need to be reduced. Is it?
$ python src/assistant_flow/setup.py
..
..
OPENAI_API_VERSION 2024-05-01-preview
Traceback (most recent call last):
File "/mnt/d/work/practice/AI/llm/assistant-pf-demo/src/assistant_flow/setup.py", line 101, in
assistant = client.beta.assistants.create(
File "/home/udev/miniconda3/envs/llmenv/lib/python3.9/site-packages/openai/resources/beta/assistants.py", line 156, in create
return self._post(
File "/home/udev/miniconda3/envs/llmenv/lib/python3.9/site-packages/openai/_base_client.py", line 1240, in post
return cast(ResponseT, self.request(cast_to, opts, stream=stream, stream_cls=stream_cls))
File "/home/udev/miniconda3/envs/llmenv/lib/python3.9/site-packages/openai/_base_client.py", line 921, in request
return self._request(
File "/home/udev/miniconda3/envs/llmenv/lib/python3.9/site-packages/openai/_base_client.py", line 1020, in _request
raise self._make_status_error_from_response(err.response) from None
openai.BadRequestError: Error code: 400 - {'error': {'message': "Invalid 'tools[1].function.description': string too long. Expected a string with maximum length 1024, but got a string with length 1919 instead.", 'type': 'invalid_request_error', 'param': 'tools[1].function.description', 'code': 'string_above_max_length'}}

I had the same issue with that api version.
I reduced the function description (using gpt also 😆 ).
Seems to work fine:
"get some data insights about the contoso sales data in the following structure:
Number_of_Orders INTEGER
Sum_of_Order_Value_USD REAL
Sum_of_Number_of_Items REAL
Number_of_Orders_with_Discount INTEGER
Sum_of_Discount_Percentage REAL
Sum_of_Shipping_Cost_USD REAL
Number_of_Orders_Returned INTEGER
Number_of_Orders_Cancelled INTEGER
Sum_of_Time_to_Fulfillment REAL
Number_of_Orders_Repeat_Customers INTEGER
Year INTEGER
Month INTEGER
Day INTEGER
Date TIMESTAMP
Day_of_Week INTEGER in 0 based format, Monday is 0
main_category TEXT
sub_category TEXT
product_type TEXT
Region TEXT
If you are unsure of the data available, you can ask for a list of categories, days, etc.

query for all the values for the main_category
The data will be returned in a json format in the data property of the returned object with the query used to get the data in the query property.
If a query cannot be answered, the tool will return a message in the error property of the returned object."


Change to Bulma framework

Because the old template was not looking that good, I decided to make the change to Bulma (and yeah new things are cool).
This change means having to go over ALL the views and update them, so sorry for the long diff..
Here are some screens:
Server overview

Server services

App overview

Backup page

Login page

Here is a cat eating stuff from a fork to make up for the long diff:

Going to merge this in for the livestream. After-merge review would be appreciated :-)

Skimmed through the code. Looks good to me


Update ruby version in Gemfile

Hello.
Will be good to add the ability for update a ruby version in:

Gemfile;
Gemfile.lock;
.ruby-version.

Thanks.

Hi there. JFYI, Bundler 2.4.19 has supported the following option recently:
ruby file: '.ruby-version'

See also the PR https://github.com/rubygems/rubygems/pull/6876


Horizon crashes after unexpected TransactionResultCode

Sent a payment transaction with USD credits to an account that did not have a trust line for the currency/issuer pair (it also happens to be the same account as the sender).
Actor crashed!
XDR::EnumValueError: Unknown Stellar::TransactionResultCode member: -2
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/xdr-0.0.1/lib/xdr/enum.rb:21:in read' 	org/jruby/RubyKernel.java:1886:in tap'
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/xdr-0.0.1/lib/xdr/enum.rb:20:in read' 	/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/xdr-0.0.1/lib/xdr/union.rb:37:in read'
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/xdr-0.0.1/lib/xdr/struct.rb:18:in read' 	org/jruby/RubyHash.java:1341:in each'
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/xdr-0.0.1/lib/xdr/struct.rb:17:in read' 	org/jruby/RubyKernel.java:1886:in tap'
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/xdr-0.0.1/lib/xdr/struct.rb:16:in read' 	/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/xdr-0.0.1/lib/xdr/struct.rb:18:in read'
org/jruby/RubyHash.java:1341:in each' 	/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/xdr-0.0.1/lib/xdr/struct.rb:17:in read'
org/jruby/RubyKernel.java:1886:in tap' 	/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/xdr-0.0.1/lib/xdr/struct.rb:16:in read'
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/xdr-0.0.1/lib/xdr/concerns/converts_to_xdr.rb:55:in from_xdr' 	/Users/andrewrogers/Code/stellar/horizon/app/models/hayashi/transaction.rb:26:in result_pair'
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/memoist-0.11.0/lib/memoist.rb:147:in result_pair' 	/Users/andrewrogers/Code/stellar/horizon/app/models/hayashi/transaction.rb:12:in result'
/Users/andrewrogers/Code/stellar/horizon/app/models/hayashi/transaction.rb:49:in fee_paid' 	/Users/andrewrogers/Code/stellar/horizon/app/jobs/history/ledger_importer_job.rb:35:in perform'
org/jruby/RubyArray.java:1613:in each' 	/Users/andrewrogers/Code/stellar/horizon/app/jobs/history/ledger_importer_job.rb:34:in perform'
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in transaction' 	/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in within_new_transaction'
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in transaction' 	/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/activerecord-4.1.9/lib/active_record/transactions.rb:208:in transaction'
/Users/andrewrogers/Code/stellar/horizon/app/jobs/history/ledger_importer_job.rb:19:in perform' 	/Users/andrewrogers/Code/stellar/horizon/app/jobs/application_job.rb:12:in with_db'
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:294:in with_connection' 	/Users/andrewrogers/Code/stellar/horizon/app/jobs/application_job.rb:12:in with_db'
/Users/andrewrogers/Code/stellar/horizon/app/jobs/history/ledger_importer_job.rb:16:in perform' 	/Users/andrewrogers/Code/stellar/horizon/lib/instrumentation.rb:62:in perform_with_instrumentation'
org/jruby/RubyProc.java:271:in call' 	/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/metriks-<IP_ADDRESS>/lib/metriks/timer.rb:51:in time'
/Users/andrewrogers/Code/stellar/horizon/lib/instrumentation.rb:61:in perform_with_instrumentation' 	org/jruby/RubyKernel.java:1958:in public_send'
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in dispatch' 	/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/celluloid-0.16.0/lib/celluloid/calls.rb:63:in dispatch'
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/celluloid-0.16.0/lib/celluloid/cell.rb:60:in invoke' 	/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/celluloid-0.16.0/lib/celluloid/cell.rb:71:in task'
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/celluloid-0.16.0/lib/celluloid/actor.rb:357:in task' 	/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/celluloid-0.16.0/lib/celluloid/tasks.rb:57:in initialize'
/Users/andrewrogers/.rbenv/versions/jruby-1.7.19/lib/ruby/gems/shared/gems/celluloid-0.16.0/lib/celluloid/tasks/task_fiber.rb:15:in `create'

Duplicate of #29


Is it possible to put our pretrained model in this project?

Nice project for agriculture. I believe it can be useful for the community.
Is it possible to put our pretrained model and something else to this project.
We trained a ViT-large model in PlantCLEF, and then finetune the model in 13 plant disease-related recognition datasets, one plant growth stage classification and one weed detection dataset.  The experiments suggest nice performance.
Paper details can be referred to here and code.
We want to put our model here. If it is possible, please tell me.

@xml94 The question of how the AgML community can contribute models is a very important one. We're at the point where we need to develop a solution. I'm moving this broader conversation to Issue #34. @amogh7joshi and I will provide some initial thoughts on this but would be really interested in getting you and your team involved in helping to be the first model contribution, and thinking about the best method for community contributed models. Looking forward to it!


Update LICENSE

For now the current license is "The Unlicense".
Ideally we would update it to the "BSD 3-Clause License", which is the one used by most of the other Jupyter projects.
I think @fcollonval raised that question before. Is there anything special we should do before updating? I suppose we could open the PR and gather the opinion of everyone who contributed until now (4 people as of today), and merge it if we all agree.
What do you think?
cc @echarles

BSD 3-Clause License, Apache License 2.0 or MIT License make sense to me.

I think BSD 3-Clause is the better choice to align with the other jupyter project. And we definitely need the agreement of all participants and especially of @MMesch as he sets the current license.


https://datatracker.ietf.org/doc/html/draft-ietf-secsh-filexfer-02 returns draft-ietf-secsh-filexfer-13.txt

Describe the issue
As title - If I ask for draft-ietf-secsh-filexfer-02 then the content I get back is draft-ietf-secsh-filexfer-13.txt. The same seems to be true for other revisions, though I didn't check all ten possibilities.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

duplicate of #4933. Please read the comments there.


Can't install using the classic installer (v<IP_ADDRESS>)

Description
When trying to install the latest version (<IP_ADDRESS>) using the classic installer, I receive the following error:
The provided package name does not match the expected package name. Check the AppXDeploy...
(the rest of the message is cut off).

This happens on two different systems (one desktop, and one Surface Pro 8), both running Windows 11 Pro 22H2. Files <IP_ADDRESS> is already installed on both computers.
I have purchased Files through the store to help support the project, but I prefer to use the classic installer.
Steps To Reproduce

Download the classic installer from the Files website.
Run the installer.

The error appears right at the start of the installation process.
Requirements
Please fix the installer so that I can install the latest version of Files!
Files Version
<IP_ADDRESS>
Windows Version
Windows 11 Pro 22H2 22621.3296
Log File
There isn't a log file - the error is in the installer.

Thanks for the report, please see https://files.community/docs/install#:~:text=starting an update.-,Steps required,-for the “classic


Fixed DAG zoom in and zoom out nodes separated from arrows #1679

Codecov Report

Merging #1680 into dev will increase coverage by 0.17%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##              dev    #1680      +/-   ##
==========================================
+ Coverage   14.92%   15.09%   +0.17%
==========================================
  Files         284      283       -1
  Lines       13960    13801     -159
  Branches     2270     2244      -26
==========================================
  Hits         2083     2083
+ Misses      11655    11496     -159
  Partials      222      222

Impacted Files
Coverage Δ

...hinscheduler/server/worker/task/http/HttpTask.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Fix the response body is not closed  in 4xx when istio-agent fetch wasm

Signed-off-by: Shiming Zhang<EMAIL_ADDRESS>[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[x] Does not have any changes that may affect Istio users.

@wzshiming: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
581aaa0736560269992622c826b60e48e78022dd
link
/test integ-pilot-multicluster-tests_istio

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.

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

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
581aaa0736560269992622c826b60e48e78022dd
link
/test integ-pilot-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
581aaa0736560269992622c826b60e48e78022dd
link
/test integ-ipv6-k8s-tests_istio

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

@wzshiming: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
581aaa0736560269992622c826b60e48e78022dd
link
/test integ-pilot-multicluster-tests_istio

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

@wzshiming: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
581aaa0736560269992622c826b60e48e78022dd
link
/test integ-pilot-multicluster-tests_istio

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


Address sporadic DNS resolution issues when using nginx.ingress.kubernetes.io/auth-url

Whenever a coredns pod is restarted it can happen that ingresses using the nginx.ingress.kubernetes.io/auth-url annotation start returning 5xx because nginx attempts to resolve the DNS name against a non-existent coredns pod, which fails for obvious reasons.
The problem is caused by cilium without kube-proxy but with eBPF enabled as described in https://github.com/kubernetes/ingress-nginx/issues/9222#issuecomment-1655108298.
The mitigation when this happens is to restart the nginx-ingress pods which makes the DNS resolution issues go away, but this shouldn't be the longterm solution here.
I have a few ingresses making use of the authentik-output-proxy to implement auth via:
nginx.ingress.kubernetes.io/auth-url: http://authentik-outpost-proxy.identity.svc.cluster.local:9000/outpost.goauthentik.io/auth/nginx

I need to come up with a solution for this since I don't want to disable eBPF.

I haven't encountered this issue for months now. Closing.


Mobile does not work

For some reason mobile does not work. This may be a JS WebRTC issue.

This is due to horrendous mobile support for WebRTC. Nothing we can do here

This is due to horrendous mobile support for WebRTC. Nothing we can do here


🌐 Add Chinese translation for docs/zh/docs/environment-variables.md

@skyanye Can you spend some time to apply these changes?

@skyanye Could you spend some time applying these changes?

@nick-cjyx9 Sorry, I reject to continue translate anymore. I think the content you marked above does not need to be modified. Because the translation is for people who only know Chinese, in order to express clearly, it is usually not translated directly from English. I saw the translated content on other pages of your website, which is difficult to understand. It is better to read it directly in English. In addition, your website does not parse markdown correctly. If you do not add spaces, there are a lot of asterisks on the website, which greatly affects the reading experience. Please log in to the page and check it yourself.

Thank you for bringing this to my attention; I will review it later. However, I must respectfully disagree, as I believe the spacing plays an important role in enhancing the reading experience. Inconsistent typesetting can lead to a disorganized presentation, so I won't be able to approve this change.
Apologies for any inconvenience caused.


Insert list of data into POST request

Hi, I try to insert list of data into body of my POST request. Example from documentation:
POST https://apidata.mos.ru/v1/datasets
[ "Id", "Caption", "SefUrl"]

Result:
[ { "Id": 1147, "Caption": "Электронная нотная библиотека города Москвы", "SefUrl": "7719028495-elektronnaya-notnaya-biblioteka-goroda-moskvy" } ]
My version of code:
import pprint
import requests
from requests import Session, Request

method = 'datasets'
data_list = ["Id", "Caption", "SefUrl"']
s = Session()
req = Request('POST', 'https://apidata.mos.ru/v1/{0}'.format(method))
prepped = req.prepare()
prepped.body = data_list
esponse = s.send(prepped)

response = requests.post('https://apidata.mos.ru/v1/{0}'.format(method), data=data_list)
print response.url

if response.status_code == 200:
    pprint.pprint(response.json())
else:  # TODO - use custom exceptions
    message = "A request to the DataMos API was unsuccessful. The server returned HTTP {0} {1}."
    print message.format(response.status_code, response.reason)

The result is:
Traceback (most recent call last):
  File "/home/max/bot_project/DataMosAPI/data_mos_api/test_post.py", line 12, in <module>
    response = s.send(prepped)
  File "/home/max/bot_project/Bots_Django/venv/local/lib/python2.7/site-packages/requests/sessions.py", line 609, in send
    r = adapter.send(request, **kwargs)
  File "/home/max/bot_project/Bots_Django/venv/local/lib/python2.7/site-packages/requests/adapters.py", line 423, in send
    timeout=timeout
  File "/home/max/bot_project/Bots_Django/venv/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/home/max/bot_project/Bots_Django/venv/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py", line 356, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/lib/python2.7/httplib.py", line 1057, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib/python2.7/httplib.py", line 1097, in _send_request
    self.endheaders(body)
  File "/usr/lib/python2.7/httplib.py", line 1053, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python2.7/httplib.py", line 901, in _send_output
    self.send(message_body)
  File "/usr/lib/python2.7/httplib.py", line 873, in send
    self.sock.sendall(data)
  File "/home/max/bot_project/Bots_Django/venv/local/lib/python2.7/site-packages/requests/packages/urllib3/contrib/pyopenssl.py", line 311, in sendall
    sent = self._send_until_done(data[total_sent:total_sent + SSL_WRITE_BLOCKSIZE])
  File "/home/max/bot_project/Bots_Django/venv/local/lib/python2.7/site-packages/requests/packages/urllib3/contrib/pyopenssl.py", line 301, in _send_until_done
    return self.connection.send(data)
  File "/home/max/bot_project/Bots_Django/venv/local/lib/python2.7/site-packages/OpenSSL/SSL.py", line 1253, in send
    raise TypeError("data must be a memoryview, buffer or byte string")
TypeError: data must be a memoryview, buffer or byte string

It looks like your API is expecting you to post JSON. Try simplifying your code to this:
import pprint
import requests
from requests import Session, Request

method = 'datasets'
data_list = ["Id", "Caption", "SefUrl"']
s = Session()
response = requests.post('https://apidata.mos.ru/v1/{0}'.format(method), json=data_list)
print response.url

if response.status_code == 200:
    pprint.pprint(response.json())
else:  # TODO - use custom exceptions
    message = "A request to the DataMos API was unsuccessful. The server returned HTTP {0} {1}."
    print message.format(response.status_code, response.reason)

It's work. Thank you:)))


Update Slack to 2000

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3155
Originally created by @pnadolny13 on 2022-01-12 14:43:26

View 2 previous comments from the original issue on GitLab


[thci] allow to specify custom commands

This commit uses Param9 to specify custom commands for Thread BR THCI to control otbr-agent.

@karthick-grl Could you help review this PR?

LGTM

Seems like an useful feature. Anyhow, could we maybe document somewhere in the THCI file the list of tracked extra parameters? Maybe within __parseExtraParams().

Doxygen added.

BTW, not big fan of having many private methods in the OpenThreadTHCI class since this makes it impossible to override them in the OpenThread_BR one.

It's always easy to rename __parseExtraParams to _parseExtraParams whenever necessary?


docs: DeepLake example

Updated the Deep Lake example. Added a link to an example provided by Activeloop.

cc @adolkhan

@baskaryan No feedback from author


What is prop-drilling?

Prop Drilling is the process by which you pass data from one part of the React Component tree to another by going through other parts that do not need the data but only help in passing it around.
How to solve it? Using state management tools such as Redux

@u-uysal  You can use useContext to avoid prop drilling


Re-add site, change one starter site, add another

Requesting merging of this commit so as to:

Re-add my main site to the list of Eleventy sites
Change the listing for my current starter site (URL change)
Add the listing for a new starter site

Thanks in advance for considering!

Not understanding why those checks failed; I followed same procedures as with previous PRs for the same types and locations of these JSON files. Please advise what help I can offer, if any, to move this along.

@brycewray After having a look at the Netlify deploy details, this is where your local build is failing

Without going into the branch which you submitted this PR, I can't say for certain if that is the only issue, but hopefully this helps you to get your local build running so all the checks pass.

@tannerdolby Thanks. I guess what's throwing me on this is that the workflow has changed since the last time I submitted a PR here; at least, I don't recall my previous PRs to this repo having gone through an actual build process, since I was submitting only JSON files and thus didn't think there was a need to check them locally (assuming valid JSON, of course). That said, I'll run my fork locally and see what I can figure out. I appreciate your help!

Checks keep failing. All I can say is, it works locally and my proposed JSON changes (two new files and one revised file) appear valid. Still unsure what's wrong at the Netlify end. I see there was a reference to https://github.com/11ty/11ty-website/pull/884 having a build issue, too. Whether there's any connection is beyond me. Again, if someone can let me know what else I can try, I surely will. Thanks.

 I think Zach is aware of the checks failing as he merged the PR I referenced in 884. You can probably let this be for now, and if any Eleventy member needs you to change something they will request changes.

 I think Zach is aware of the checks failing as he merged the PR I referenced in 884. You can probably let this be for now, and if any Eleventy member needs you to change something they will request changes.

Thanks to you all! Much appreciated.

Closing this one. Will make a different PR.

Closing again. Will submit a different PR since some stuff has changed.


Create CONTRIBUTING.md

Create a proper Contributing File
This a beginner friendly documentation  issue.

[ ] Create a proper CONTRIBUTING.md file. Describe as much you can.
[ ] Update README.md
[ ] Follow a proper commit style guideline. ( Eg: doc: your message here )
[ ] Please describe your work done in the PR.

Hi @yash2189 Can I work on this?

Yes sure @Kunal1198

Please review my PR #2 .


Bypass Shielded Communication by default

Is your feature request related to a problem? Please describe.
It is not obvious and not described anywhere that calling a command without an -X option will trigger SEC counter growing up, event data read.
Describe the solution you'd like
make the choice reversed, leave the -X for backward compatibility but mark it as deprecated + add a special option to actively enable shielded communication. By default the communication should bypass the shielded connection.
Additional context
https://github.com/Infineon/optiga-trust-m/issues/67 shows that -X usage isn't obvious

Add important notes for users to decide whether to disable the Shielded connection based on their application.
https://github.com/Infineon/linux-optiga-trust-m#important-notes


Empty selection

Hi, I'm about to use this picker, have you considered any empty selection / no-color state?
If it's already out there maybe I missed it from the documentation
Thanks!

Hi
This isn't in the documentation,
Would you like to see an option to choose transparent/no-color?

What is your use case?

Exactly! Im adding a color filter to a list where a list item may not have any color asigned. Id love to help supporting this feature

yeah, I think NoColor Slot will be perfect for this use case.
You can make a PR if you want, otherwise I will be shipping this feature and FallbackInput slots this weekend.

v1.0.0 released
no-color/transparent swatch can be added with a color with the value of ''(empty-string)


Updated docstrings to inform that the methods accept fh=ForecastingHo…

…rizon.

Reference Issues/PRs

What does this implement/fix? Explain your changes.

I updated the docstrings of the following methods to inform that they accept fh=ForecastingHorizon.
sktime.forecasting.base._base.BaseForecaster.fit()
sktime.forecasting.base._base.BaseForecaster.predict()
sktime.forecasting.base._base.BaseForecaster.score()
sktime.forecasting.base._sktime._SktimeForecaster._set_fh()
sktime.forecasting.base._sktime._SktimeForecaster.predict()
sktime.forecasting.base._sktime._SktimeForecaster.update_predict_single()
sktime.forecasting.base._sktime._OptionalForecastingHorizonMixin._set_fh()
sktime.forecasting.base._sktime._RequiredForecastingHorizonMixin._set_fh()
sktime.forecasting.base.adapters._pmdarima._PmdArimaAdapter.fit()

Does your contribution introduce a new dependency? If yes, which one?
No.

What should a reviewer concentrate their feedback on?

Any other comments?

PR checklist

For all contributions

[ ] I've added myself to the list of contributors.
[ ] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[ ] I've added unit tests and made sure they pass locally.

For new estimators

[ ] I've added the estimator to the online documentation.
[ ] I've updated the existing example notebooks or provided a new one to showcase how my estimator works.

Thanks @julramos, if you're interested in getting more involved, please checkout the events we have planned over the next few weeks: https://github.com/alan-turing-institute/sktime/issues/863 - let me know if you have any questions.


Helm 3 doesn't create namespace

https://github.com/helm/helm/issues/5753

Disabled custom namespaces at: https://github.com/vardius/go-api-boilerplate/pull/25

Split namespace creation and app charts deployment into two seperate flows
https://github.com/vardius/go-api-boilerplate/pull/27


Adding GitHub Action workflow.

Based on "Go Release Binaries" (https://github.com/marketplace/actions/go-release-binaries).

Not sure what this gets over the existing releaser stuff I have. Plus this won't be signed.

If you have something that works for you, it‘s not needed.


Allow RuneliteAPI url be configurable via environment variables

This allows it easier to target local API servers, which could be used for improved (perceived) security as well as easier local testing.
The reason I chose the environment variable approach is because this should be a really advanced feature only used by either a system on top of runelite for development/security purposes. For development specifically, this would be better because you can setup your shell with these environment variables and not have to launch runelite with a flag all the time.

I have also similar thing covered here for anyone interested: https://github.com/runelite/runelite/pull/1199

I see that the url is configurable via http-api/src/main/resources/runelite.properties in the other approach. How can I set this on runtime without setting a file? I'm working on launching runelite from another system and setting environment variables/command line flags are a lot easier to work with than files.


How can SalutDevice be uniquely identified?

Hi, I'm looking for a way to uniquely identify a device. The only thing I've found that should be (as far as I understand) unique inside SalutDevice is macAddress, but it has a protected access rights, so I can't really use it in my classes. So how can I identify a specific device?

You could use a very small Unique ID that you can generate using the Java Standard Library as part of your instance name.
This a great library for doing so.
So for instance, you could take the person's name, convert it to numbers, then convert that to a unique HashID.
Then pass that in here:
SalutServiceData serviceData = new SalutServiceData("sas", 50489, userNameUniqueID);
I hope that helps.

It makes sense, thanks.

Awesome! :D

Hi, There is a passage about getting you own Mac Address http://robinhenniges.com/en/android6-get-mac-address-programmatically and it works for me in both Android 5.1 device and Android 6 device.


Implement multiple users

Implemented in this branch:

Multiple users (Add/update/delete/list)
Disable/enable password protection without removing the htpasswd file
Unit tests for new functionality
Unit tests now return non-zero exit code if one or more failed
Fixed running unit tests on Travis

Nice solution! I have a small problem with the naming of some of the commands, but not a big change. I'm also yet to test this out on my dokku instance and I'll likely do that once the commands are renamed.
Thanks for the contribution!

Had a play with it now and it looks really good. There are a few minor problems:

I think we should remove the user namespace for now
I think we should keep the unset name instead of changing it to delete
The unset method is currently missing the path to the HTPASSWD file
The README needs to be updated with the new commands and the first TODO item removed

Thanks for this contribution! It's great!

Once I get back home I'll implement the changes and fixes, thanks for the feedback!

All done!
Please let me know if I missed anything or if you spot anything else.

Looks great! Merging it in now.
Thanks again for the contribution!