(recently) migrated to microsoft accounts cant use skins

friend of mine migrated thier mojang account to microsoft,now opon attempting to change skin it gives a 401 error,inticating that the credentials are invalid,if anyone has experience this issue too,or knows a solution feel free to share them,have a good day.
Image related.

Try using the latest version (0.1.1a) if it still doesn't work use your vanilla launcher to upload the skin for the first time, then it should work.


Sort fails on date-like values with links

Describe the bug
Sorting on a field which includes links does not appear to be working correctly.
To Reproduce
I've got a directory named "Choro Rep" and all the files in it have a last-reviewed field, e.g.
last-reviewed:: [[2021-10-18]]

And here is a dataview query sorted by last-reviewed desc e.g.
table
  last-reviewed as "Last Reviewed",
  status as "Status",
  composer as "Composer"
from "Choro Rep"
sort last-reviewed desc

Expected behavior
The results should sort by the last-reviewed date e.g. the dates in the screenshot should be
2021-10-15
2021-10-09
2021-09-20
2021-09-04
2021-09-04

Screenshots

Desktop (please complete the following information):

OS: Mac OS 10.5.2
Obsidian Version 0.12.15
Dataview Version 0.4.18

Smartphone (please complete the following information):

Device: iPhone 12
OS: iOS14.8
Obsidian Version 1.0.4
Dataview Version 0.4.18

Additional context

This worked as expected with Dataview 0.4.5. I'm not sure at which version it stopped working as expected.
I realize I'm dealing with text strings that represent dates, but I'm not expecting Dataview to recognize that, the string "2021-10-15" should precede the string "2021-10-09" in a descending sort.

Hello,
sorry to come back to you so late. I currently go through older issues to see which are stale or already solved.
I cannot reproduce this behaviour anymore. Using your example query, I get the correct order - without the date() function:

Is this true for you too or do you still face problems?

I can't reproduce the issue either, so thanks for fixing it, even if you don't remember fixing it! Thanks, also, for checking back.


Add new contributor course to cheat sheet and resources

Would like to add the new contributor course (k8s.dev/course) to the following pages on the contributor website for easy reference for new contributors and for everyone :)
here:
https://github.com/kubernetes/contributor-site/tree/master/content/en/resources
and here:
https://github.com/kubernetes/community/tree/master/contributors/guide/contributor-cheatsheet

/sig contributor-experience

/assign

/area contributor-guide

/close


flashback report fail for "ERROR 1105 (HY000): cannot set flashback timestamp after min-resolved-ts(1970-01-01 00:00:00 +0000 UTC)"

Bug Report

What version of TiKV are you using?
[2023/02/26 14:27:36.720 +00:00] [INFO] [lib.rs:85] ["Welcome to TiKV"]
[2023/02/26 14:27:36.720 +00:00] [INFO] [lib.rs:90] ["Release Version:   6.7.0-alpha"]
[2023/02/26 14:27:36.720 +00:00] [INFO] [lib.rs:90] ["Edition:           Community"]
[2023/02/26 14:27:36.720 +00:00] [INFO] [lib.rs:90] ["Git Commit Hash:   f0af6ff1f5a01def628ddc6fe61bbb5d005cfc9d"]
[2023/02/26 14:27:36.720 +00:00] [INFO] [lib.rs:90] ["Git Commit Branch: heads/refs/tags/v6.7.0-alpha"]
[2023/02/26 14:27:36.721 +00:00] [INFO] [lib.rs:90] ["UTC Build Time:    Unknown (env var does not exist when building)"]
What operating system and CPU are you using?

Steps to reproduce
tikv config:
[resolved-ts]
enable = true
advance-ts-interval = "20s"
scan-lock-pool-size = 2
[cdc]
min-ts-interval = "1s"
hibernate-regions-compatible = true
incremental-scan-threads = 4
mysql> select now();
+---------------------+
| now()               |
+---------------------+
| 2023-02-27 01:56:32 |
+---------------------+
1 row in set (0.01 sec)
mysql> flashback cluster to timestamp '2023-02-27 01:50:32';
ERROR 1105 (HY000): cannot set flashback timestamp after min-resolved-ts(1970-01-01 00:00:00 +0000 UTC)
mysql>
What did you expect?
flashback successfully
What did happened?
mysql> flashback cluster to timestamp '2023-02-27 01:50:32';
ERROR 1105 (HY000): cannot set flashback timestamp after min-resolved-ts(1970-01-01 00:00:00 +0000 UTC)
mysql>

tikv-flashback.log

See https://github.com/pingcap/tidb/issues/41758


No Vuex store detected

Hello,
I'm seeing no Vuex store inside devtools anymore. With other projects on other Vue+Vuex versions it works perfectly.
Current env:
"vue": "^2.4.1",
"vuex": "^2.4.0"

// main.js
import Vue from 'vue'
import App from './components/App.vue'
import router from './router'
import store from './vuex'
import localforage from 'localforage'

localforage.config({
    driver: localforage.LOCALSTORAGE,
    storeName: 'guildlabs'
})

Vue.config.devtools = true

const app = new Vue({
    el: '#app',
    store,
    router,
    render: h => h(App)
})

// vuex/index.js
import Vue from 'vue'
import Vuex from 'vuex'
import auth from '../app/auth/vuex'

Vue.use(Vuex)

export default new Vuex.Store({
    modules: {
        auth: auth
    }
})

// app/auth/vuex/index.js
import state from './state'
import * as mutations from './mutations'
import * as actions from './actions'
import * as getters from './getters'

export default {
    namespaced: true,
    state,
    mutations,
    actions,
    getters
}

Yes, all the other files for state, mutations, actions and getters also exist and have content inside app/auth/vuex.
Is this a known problem with devtools, that it doesn't detect newer versions?

Hey, can you boil down the error and provide a repro using this template?
Thanks!

@posva It's a private project. Can't really give the full stuff out. Only thing I can confirm now, that a downgrade of Vuex 2.4 to Vuex 2.3.1 worked.

Ok, make sure to open a new issue if you manage to reproduce it in a simple HTML page or a codepen

I had the same issue and the downgrade worked for me too.
But I couldn't reproduce it.
Could it be webpack related?

I also have the same issue, downgrade to 2.3.1 worked.

The issue still exists. Could it be Vuex related, since it only works with Vuex 2.3.1, but not with 2.5 or 3.0?

Same issue here.  Using vue-dev tools on firefox.  I used to see vuex store before.  Now it's gone.  Using:
"vue": "^2.4.4",
"vuetify": "^0.16.9",
"vuex": "^3.0.0",
Yet, for some strange reason,  my vue-developer window is showing the vue version as:
Ready. Detected Vue 2.5.2.
Infact, I can't even see any components in it.

Same issue here.  Using vue-dev tools on firefox.  I used to see vuex store before.  Now it's gone.  Using:
"vue": "^2.4.4",
"vuetify": "^0.16.9",
"vuex": "^3.0.0",
Yet, for some strange reason,  my vue-developer window is showing the vue version as:
Ready. Detected Vue 2.5.2.
Update:  Ok, seems there was a error in the way I was using ...mapGetters which caused vue-dev to not detect anything.  mapGetters seems to no longer accept an array of properties.  Instead we need an object as parameter:  That is, can't do: ...mapGetters( [ x, y ] ).
Instead need to do:  ...mapGetters( {  x: 'X',  y: 'Y' } )
Once this was fixed,  I see the vuex store again in vue-developer tools.

Had this problem also and discovered that devtools does not work for Vuex IF NODE_ENV is not 'development'. Regardless of whether devtools is explicitly turned on with
Vue.config.devtools = true;
The fix for us was to use a different flag to turn on production things and leave NODE_ENV as 'development'.

Had this problem with this env:
"vue": "^2.4.1",
"vuex": "^2.4.0"

my store.js file
import Vuex from 'vuex'
import Vue from 'vue'

Vue.use(Vuex);

export const store = new Vuex.Store({
  state: {
    here: 'test'
  },
  getters: {
    here (state) {
      return state.here
    }
  }
});

main.js
import { store } from './store/store'
new Vue({
  el: '#app',
  router,
  store,
  components: { App },
  template: '<App/>'
})

trying to console.log(this.$store.getters.here) its works properly but still not detected by vue-devtools

@nshgraph 's hint helps. I just changed NODE_ENV to "development" and now vue-devtools can find my vuex instance.

I found that dev-tools in firefox doesn't show my vuex store, but chrome dev-tools does.
<EMAIL_ADDRESS><EMAIL_ADDRESS>
the store works fine, just dev-tools doesn't detect it. And only in firefox.
NODE_ENV is development
Vue.config.devtools = true;
doesn't help..

#612 . check this .

I struggled with this issue for awhile. I found that just declaring
Vue.config.devtools = true;
in the root app file was not enough. It seems that when I imported a store from another file like this:
import store from './store'
then I had to add:
Vue.config.devtools = true;
in ./store.js as well.

This worked for me as well.
I suspect it has something to do with the devtools property being set to true before the store is created, such that when it is, it is true.
That's probably why moving the creation of the Store in the same file as the Vue instance in the main entry file worked as well.

I struggled with this for a bit too long before I realized that I forgot make my store a new Instance of Vuex.Store

call me love, u know am waiting
am at the shop
On Tue, May 1, 2018 at 12:51 PM Eric Lakatos<EMAIL_ADDRESS>wrote:

I struggled with this for a bit too long before I realized that I forgot
make my store a new Instance of Vuex.Store
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-devtools/issues/405#issuecomment-385738959,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkYRe-k4xuN4VabNna8u3eqgN0iTXU3Pks5tuKCsgaJpZM4PJcoB
.

@MathieuDerelle Thanks, you made my day!

Why need to use ?
Vue.config.devtools = true

what if production version ?

Why need to use ?
Vue.config.devtools = true

what if production version ?

try this
Vue.config.devtools = process.env.NODE_ENV === 'development'

that's the default case
https://github.com/vuejs/vue/blob/d483a49c86874b2e75863b661f81feecd46ae721/src/core/config.js#L58
but the point is precisely to be able to debug the production environnement
Either it's a demo site and you can just use Vue.config.devtools = true or it is not and you should add other conditions

I ran into this error and just want to put it out there to make sure you actually export the new Vuex Store. I was exporting
export default {
  state,
  mutations,
  actions,
  getters
};

Which actually works with getting things from the state. However, the minute you use ...mapGetters you start running into issues. Also, the devtools doesn't see the Vuex instance because... well... it's not there. Simple mistake that can lead to a some confusion when you're copying / pasting across projects
I should have had:
export default new Vuex.Store({
  state,
  mutations,
  actions,
  getters
});

Adding
Vue.config.devtools = true;
Doesn't solve my problem, event if added in both app.is & store.js files

It needs to be before the store initialization new Vuex.Store(...) so it depends on how your code is structured

It needs to be before the store initialization new Vuex.Store(...) so it depends on how your code is structured

solve my problem
it toast me another problem， my process.env.NODE_ENV is production

We have encountered such a problem. Has anyone of you solved it?

I just encountered this too after switching from the

I had this same issue, disabling the Chrome plugin fixed it for me.

I just encountered this too after switching from the

Adding this here hoping it helps others. I lost two hours and a good bit of hair over this.
My setup: I'm using the remote devtools, the one working over ngrok. And at some point, it stopped seeing the store.
The reason seems to be related to the fact I uninstalled the vue-devtools extension from Chrome.
Apprently, you still need it installed and disabled. I can only guess if you don't have it installed the remote tool is missing some rights/permissions to talk to Chrome.
Anyways, I was able to repro it consistently. If I remove the extension from Chrome and restart remote devtools and re-serve the app, the store is not detected. If I add the extension back to Chrome (and keep it disabled), it starts working properly.

Lost two hours and a good bit of hair over this.
Setup: using the remote devtools, the one working over ngrok. At some point, it stopped seeing the store. Tried changing vuex version, vue version, vuex-module-decorators version and @vue/devtools version. Nothing helped.
The reason seems to have been related to having completely removed Vue devtools extension from Chrome (which I did, since I was now using the remote standalone electron app).
Apparently, you still need the extension installed and disabled. I can only guess the electron app is missing some permissions when talking to Chrome if the extension is not installed.
I was able to repro it consistently:

if I remove the extension from Chrome and restart remote devtools and re-serve the app, the store is not detected
if I add the extension back to Chrome (and keep it disabled), it starts working properly.

doesn't have the effect, but change to

Lost two hours and a good bit of hair over this.
Setup: using the remote devtools, the one working over ngrok. At some point, it stopped seeing the store. Tried changing vuex version, vue version, vuex-module-decorators version and @vue/devtools version. Nothing helped.
The reason seems to have been related to having completely removed Vue devtools extension from Chrome (which I did, since I was now using the remote standalone electron app).
Apparently, you still need the extension installed and disabled. I can only guess the electron app is missing some permissions when talking to Chrome if the extension is not installed.
I was able to repro it consistently:

if I remove the extension from Chrome and restart remote devtools and re-serve the app, the store is not detected
if I add the extension back to Chrome (and keep it disabled), it starts working properly.

The issue with me is that im using tauri, so i can't install the extension


No device connected

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{  D455}

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Linux (Ubuntu 16) }

Kernel Version (Linux Only)
(5.4.0)

Platform
PC

SDK Version
{librealsense2.49.0 }

Language
{C/C# }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
Hello!When I try to collect the data,there is a fatal error:
RealSense error calling rs2_pipeline_start_with_config(pipe:0x560b767d4380, config:0x560b769168a0):
No device connected
What should I do?Thanks in advance!

Hi @kongxin22  Could you provide more information please about the script or program that you are using that produces this error?  If it is a script that you have created, please paste it into a comment if possible.  Thanks!

@MartyG-RealSense I find that if I pull out the camera and connect it again,the problem will not occur.Is it a big problem?

Unplugging and re-inserting the camera resets it.  It is fine to resolve the problem like this, though it can become understandably annoying if it has to be done often.
The camera can also be reset without unplugging in the RealSense Viewer program by going to the 'More' option near the top of the options side-panel and selecting the 'Hardware Reset' menu option.

If you are writing your own script then you can also reset the camera when the script launches by placing a hardware_reset() instruction in the script.

Hi @kongxin22  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.

Hello.Long  time no see.The problem was shelved by me.Today when I ran my script,which called pipe to start,the problem was still here:
RealSense error calling rs2_pipeline_start_with_config(pipe:0x556234ce8e80, config:0x556234ca8280):
No device connected
This time I used a new camera.I thought maybe my script  has errors.But sometimes it did run after reinserting the camera today.And I tried it on many computers with no luck.I am confused.What is the problem?

Hi @kongxin22  Are the multiple computers that you used all the same manufacturer / model?


Hugin window opens and makes computer unusable

Hi! First of all, thank you so much: this script is great. It even stitches the panorama better than the one that comes with the camera!
I have a problem running the video script (though this happens also with the panorama script, but in that case doesn't bother): when the panorama scripts (which is called by the video script for each frame) runs Hugin, that opens for a second a window. The problem is this turns impossible to use the computer, because that window gets the focus and I can't do anything on other windows.
Is there any workaround for this?
Edit: this happens using Ubuntu 16.04, with the Hugin from the official repo.
Thank you so much!

Hi there, Milton.
It is strange that the script opens any window, it does not do that on my computer. (Arch linux)
Can you post a little of your console output?
The reason I ask is that hugin is not actually used by the script, only some of the panotools that Hugin also relies upon.
-Evert-

I'm stumped.
Thanks for the thorough reply, and the small video.
One thing you could try is to run each of the commands in the script one by one on the terminal to see which one it is that is creating that popup.
I am having a guess that .pto is defined as a Hugin file somewhere in your system setup, and it tries to open Hugin every time the system reads a .pto file. However, this should not happen from the command line.

I think that you're right.The PTO file type is associated with Hugin. What I don't understand is why, after editing every place where that association appears, is still opening the window! Anyway, it seems more a problem of my computer than of your script.
Thank you again!


Fix doc parser's tags and unrecognized characters.

Pull Request Description
Fixes docparser's characters.

Important Notes
Removal of '#' in links because of scala parser breaking the doc string, by thinking it is a commented out code. To be reverted in the future.

Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the Scala, Java, and Rust style guides.
[x] All documentation and configuration conforms to the markdown and YAML style guides.
[x] All code has been tested where possible.

Label it.

Label it.


Checking if promise unresolved before resolving

Javascript promises are only resolved once.
However, according to googleApiClient docs, it retries to establish connection even after calling onConnectionSuspended once.
This throws an error as promise might have already been resolved or rejected once.

hi @ankitghike thanks for the PR. We're currently rewriting the android part on the @vonovak/android-promises branch and this has been fixed there already so I'm going to go ahead and close this.
However, we'll be glad if you continue contributing, just discuss the things with us on slack, as discussed here.

actually let me keep it open for people who may run into similar issues on master

closing since this should be okay on master


update release info

This PR does the following:

Adds release info for Kubeflow 1.5.1 (replaces PR https://github.com/kubeflow/website/pull/3298)
Adds a "media" section to the table which contains links to media about the release, for example:

Our official release blogs
Our official video overview
Our official roadmap (I also fixed the roadmap links, which were not pointing to the correct headers, because the names had changed)

Fixes the 1.5.0 table to not include "mpi-operator" (as this is not part of Kubeflow 1.5)

Screenshot of new "media" row:

@jbottum could you give this a quick review, and LGTM if it's ok to you?

/lgtm


[Android] ScrollView not working properly after WebView is pressed

Bug description:
I was trying to create a simple screen where it has a WebView inside a ScrollView, and the fixed header shrinks on scroll. It works perfectly on IOS, but on Android, as soon as I press inside the WebView, the ScrollView will not be working, cannot scroll down whatsoever.
To Reproduce:

Clone repo: https://github.com/mk-nickyang/react-native-webview-android-scrolling-bug
run yarn start & yarn android
Press inside the WebView and then start scrolling

Expected behavior:
ScrollView should be working properly after WebView is pressed
Screenshots/Videos:
https://user-images.githubusercontent.com/29244509/175817685-bee81377-1ddc-44c2-b906-5f54589264ba.mov
Environment:

OS: macOS Monterey
OS version: 12.4
react-native version: 0.68.2
react-native-webview version: 11.22.3

Possible related issues:
https://github.com/react-native-webview/react-native-webview/issues/2360, https://github.com/react-native-webview/react-native-webview/issues/2057

one suggestion for the issue : use view tag for webview wrapping with scrollView will gets you bugs in lower versions of android and use flatlist for assigning webview in react native app instead of using scrollView and wrapping webview with view tag with collapsable={true} and webview with collapsable={false} and using domstorageenabled={true} and using container style with flex:0 flexGrow:1 and top:0, right:0, bottom:0, left:0 will result in improve permonece and solves issue not scrolling webveiw
for using webview in flatlist assign webview url to dummy data in array for flatlist rendering and call the webview inside flatlist using array object model try it it will work as i assume

Still searching

For me if i scroll to the top, the webview is scrolling to the bottom. NestedScrolling is also enabled

Experiencing this issue with an animated title. I can't scroll the webview out of view as long as i am animating the height of my title component onScroll. Can we reopen this?

@PhillipFraThailand hi did you find the solution I am also. facing same. issue
my webview inside scrollview is not scrolling
can you please tell if you have solved the issue

@swaroopaillinda i ended up disabling the scrolling animation on android for the specific cases where it happened


Fix entaglement for -reactive() feature

Sorry, I totally forgot to include this in my last PR
Fixes the ->reactive() functionality for AlpineJS code.

Kindly release it once merged, Thanks!


evaluation

I have trained the model, but I have to compare it with the ground truth of the testing data  when I evaluate it, that is, every line should be correspond to each other. How can I know which lines are predicted? For example, one graph has four lane lines, but the network only predicts three of them. How can I know which three of the four lines are predicted?

@chenyiman Maybe you should make some rules (eg. Pixel distance with label or something) to identify it:)


Invite someone in the Chat

Describe the solution you'd like
Endpoint:
POST /api/v1//s/chat/thread//member/invite HTTP/1.1
JSON:
{
"uids": ["Array of UserID's to be invited to Chat", "MUST BE ABLE TO (i.e. the invitee needs to follow the inviter)"],
"timestamp": "A JS Timestamp"
}

Got it. Will be adding at the update

Did the module inviteChat.js, and wrote the example already. This new feature will be added at the 3.0.0-nightly
Closing due to finished


Cilium pod fails to start due to CrashLoopBackOff error in config init-container

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Cilium pod of the cilium daemonset fails occasionally to start due to CrashLoopBackOff-error in the config init-container on a newly created node. We have configured the node with following taint:
node.cilium.io/agent-not-ready=true:NoExecute

i.e. for kubernetes the node is Ready at this point, but it won't accept any actual workload. We are using karpenter for node scheduling, which is also affected by this problem because Karpenter sees the node as Ready even though it is not able schedule any new workloads on it and won't therefore spin up more nodes. This error occurs currently on one specific cluster several times a week.
Cilium Version
We are using a custom build image based on cilium:v1.13.1, which has been patched with this fix for bottlerocket:
https://github.com/cilium/cilium/pull/23953
Kernel Version
5.15.102
Kubernetes Version
v1.24
Sysdump
We have generated the sysdump, but it is too big to be attached here. If required we can provide it to you separately. Here is the output we got while collecting the sysdump:

Relevant log output
Here is the kubectl describe from the failing cilium-pod:

Status:               Pending
IP:
IPs:                  <none>
Controlled By:        DaemonSet/cilium
Init Containers:
  config:
    Container ID:  containerd://a7f91c4c1845ce5f053cd676518965793a32b6e9a916eb3a831318bb22d10ef9
    Image:<PHONE_NUMBER>59.dkr.ecr.eu-central-1.amazonaws.com/cilium:v1.13.1-idealobuild.1@sha256:d0b35d32667b0b9a19a0dd6e2038651d3a796f578646fe6d90cb2d5385b56a9e
    Image ID:<PHONE_NUMBER>59.dkr.ecr.eu-central-1.amazonaws.com/cilium@sha256:d0b35d32667b0b9a19a0dd6e2038651d3a796f578646fe6d90cb2d5385b56a9e
    Port:          <none>
    Host Port:     <none>
    Command:
      cilium
      build-config
    State:       Waiting
      Reason:    CrashLoopBackOff
    Last State:  Terminated
      Reason:    Error
      Message:   -allow-config-keys strings        List of configuration keys that are allowed to be overridden (e.g. set from not the first source. Takes precedence over deny-config-keys
      --deny-config-keys strings         List of configuration keys that are not allowed to be overridden (e.g. set from not the first source. If allow-config-keys is set, this field is ignored
      --dest string                      Destination directory to write the fully-resolved configuration. (default "/tmp/cilium/config-map")
      --enable-k8s-api-discovery         Enable discovery of Kubernetes API groups and resources with the discovery API
  -h, --help                             help for build-config
      --k8s-api-server string            Kubernetes API server URL
      --k8s-client-burst int             Burst value allowed for the K8s client
      --k8s-client-qps float32           Queries per second limit for the K8s client
      --k8s-heartbeat-timeout duration   Configures the timeout for api-server heartbeat, set to 0 to disable (default 30s)
      --k8s-kubeconfig-path string       Absolute path of the kubernetes kubeconfig file
      --node-name string                 The name of the node on which we are running. Also set via K8S_NODE_NAME environment. (default "ip-10-32-226-151.eu-central-1.compute.internal")
      --source strings                   Ordered list of configuration sources. Supported values: config-map:<namespace>/name - a ConfigMap with <name>, optionally in namespace <namespace>. cilium-node-config:<NAMESPACE> - any CiliumNodeConfigs in namespace <NAMESPACE>.  node:<NODENAME> - Annotations on the node. Namespace and nodename are optional (default [config-map:cilium-config,cilium-node-config:kube-system])

Global Flags:
      Exit Code:    1

We see this log output on all the pods, which are running on the node with the affected cilium-pod:
Error from server: no preferred addresses found; known addresses: []

### Anything else?

The pods are running in AWS on EC2-instances:

System Info:
Kernel Version:                 5.15.102
OS Image:                       Bottlerocket OS 1.13.3 (aws-k8s-1.24)
Operating System:               linux
Architecture:                   amd64
Kubelet Version:                v1.24.10-eks-08ad9cc
Kube-Proxy Version:             v1.24.10-eks-08ad9cc

### Code of Conduct

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

@ldelossa

It wouldn't be possible for us to use to the upstream version of cilium due to this bug, the network wouldn't come up at all.
We rely on Karpenter for the creation of Nodes and without it we cannot perform any tests, unfortunately.

Please find the cilium dump here - https://drive.google.com/file/d/1_QDBRVtsPerBHxwWZhbjYZXpjYxoIGqD/view?usp=sharing

Hi ! Anything more that we can provide here?

We have noticed that this problem occurs more frequently in those clusters, which are running lots of small workloads and use the consolidation-functionality of the karpenter. In this kind of cluster consolidation causes new nodes to be more frequently replaced (new nodes are being started, workloads moved over, old nodes removed) and we see this cilium error occurring more often. After disabling the consolidation we have noticed that this specific error can still occur but more seldom.

In the end we were able to figure out that this issue is actually related to Bottlerocket (https://github.com/bottlerocket-os/bottlerocket/issues/3143). We are now using the latest release (Bottlerocket OS 1.14.2), which seems to have resolved this issue.


As a developer, I need to write code documentation

Added comments to the important parts of the state machine and created basic WIP documentation.


docs: daisyui integration

hey, i love shadcn, it was the first library I used when learning svelte, I kinda moved away from it because I love just having the utility classes daisyui provides without importing anything, but I still kinda missed some of the components from shadcn, so i took some time and integrated both of than, just wrote some documentation to help the next person that is trying to do the same
also have an exemple of how it looks with the music exemple and a theme changer on the top right
https://shad-daisy.vercel.app/
https://github.com/andre-brandao/shad-daisy

Do I need to add a changeset for docs?

Hey there, @andre-brandao, great job working this out!
This would be a nice thing to add to GitHub Discussions (please add this guide there) as a reference to point people to, but I'm not going to merge this into the project.
This puts the burden on us (the maintainers) to keep up with any changes to DaisyUI, which we didn't sign up for and do not wish to do.
If you'd like to maintain this guide, you can do so via a GitHub Discussions post and we'll gladly point those interested in integrating with DaisyUI there!
Hope you understand!

@huntabyte just did that


hide app contents when locked

Task/Issue URL: https://app.asana.com/0/414235014887631/1169498296439393
Tech Design URL:
CC:
Description:
Hides the app contents when app switching and consistently hides the contents with the same view (blank snapshot)
Fixes #611
Steps to test this PR:
App Lock: off, Auto-Clear: off

Switch apps - no content hidden
Background the app, then bring to foreground, no content hidden, no authentication
Kill the app then launch the app, no content hidden, no authentication

App Lock: on, Auto-Clear: off

Switch apps - content hidden by blank snapshot screen
Background the app, then bring to foreground, no content hidden, user is required to authenticate
Kill the app then launch the app, no content hidden, user is required to authenticate

App Lock: off, Auto-Clear: on

Switch apps - content hidden by blank snapshot screen
Background the app, then bring to foreground, no content hidden, no authentication required
Kill the app then launch the app, no content hidden but any open tabs have gone,  no authentication required

App Lock: on, Auto-Clear: on

Switch apps - content hidden by blank snapshot screen
Background the app, then bring to foreground, no content hidden, user is required to authenticate
Kill the app then launch the app, no content hidden but any open tabs have gone, user is required to authenticate

Internal references:
Software Engineering Expectations
Technical Design Template

Good job. I've got a few questions:

My original reasoning behind making blank/lock screen appear only when in the background (instead of resign active) is that the resign active happens for every system dialog (permissions, open in system dialog, battery warning) and I wanted to avoid blinking the app screen in these scenarios. I'm fine with making that change, but I want to double check that this implication is not an issue.
Is private func displayOverlay() needed now?
If 'show keyboard on app entry' feature is enabled, then keyboard appears on the lock screen when coming back to the app.

Thanks!

I think that's OK for people who have enabled this feature, it's more important to hide it in the app switcher state.

If it's not used I'll delete

thought I'd death with that, will fix.

Ok! 👍
It is used, but I think it does not goes past the guard statement if app lock is enabled.
Thanks!


Animate from main view into show view

Would be nice if we could mimic the way apple sort of zooms in on items when they are selected. As seen here when the album cover is selected: http://cl.ly/2C350j2j2y3P
Is this a default animation?

So far I've not been able to find out how to do this, though I've seen apple do it.

https://forums.developer.apple.com/thread/23015 - we can do anything we want, it's just a matter of time. Moving to the next milestone.


Support Mutation type

While mutations are already possible in future API via MutationType(ObjectType) sublclassing, we could also have extra MutationType base class that would represent single field on mutation:
class ErrorType(GraphQLObject):
  path: str
  code: str

class LoginMutation(MutationType):
    token: str | None
    errors: List[ErrorType] | None

    def __mutation__(_, info, username: str, password: str) -> LoginMutation:
        return LoginMutation(token="dsa87dsa98798sda")

Result:
type Mutation {
  login(username: String!, password: String!): LoginMutation!
}

type LoginMutation {
  token: String!
  errors: [ErrorType!]
}

type ErrorType {
  path: String!
  code: String!
}

We could use __graphql_name__ to rename LoginMutation to something else in schema, and have extra attr named __mutation_name__ to rename login on Mutation type to something else.

This can be delayed after next API is released.


Update ModelZoo with LocationNet and Multimedia Commons Dataset

The proposed change contains addition of Multimedia Commons Dataset and LocationNet.
Multimedia Commons Dataset is part of AWS Public Dataset program.
LocationNet is a ResNet-101 pre-trained with 39 million geo-tagged images from Multimedia Commons Dataset (YFCC100M) to recognize location.
README file at the link below contains model location, confirmation the trained model meets published accuracy from original paper, Jupyter Notebook tutorial for step by step instructions on how to use the trained model, and references to any other applicable docs or arxiv papers the model is based on.
https://github.com/multimedia-berkeley/tutorials/blob/master/README.md
Contributors:
Jaeyoung Choi (International Computer Science Institute, USA)
Kevin Li (University of California at Berkeley, USA)
This work is sponsored by AWS Research Grant with the help of Joseph Spisak, KD Singh, Jed Sundwall, Matt Jamieson, and Mu Li from Amazon.

@jychoi84: could you clarify the licensing of this model? Thanks!

@sbodenstein
The license for the model is Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0).
https://creativecommons.org/licenses/by-sa/3.0/

@jychoi84: thanks!


Menus unreadable when Windows is in high contrast mode

Code is not aware of the OS setting. Enable high contrast mode in Windows (not the Code theme) and all of the menus are white text on a white background

Menu is rendered by Chrome, so this is an upstream issue.

Closing as a duplicate of #9878


more c++ examples?

Since there isn't a good source of documentation and although I agree the codebase isn't very large, but this repo could benefit from a few examples on c++ usage. Apart from nodejs package, I personally believe there is a good amount of interest for using it as c++ websockets lib, as there isn't a good competitor atm.
Documentation would be perfect solution, but till then 2-3 examples of different usages(probably highlighting uWS::EventSystem & uWS::Server is and how to use them) could be posted?

Documentation will be written for the rewrite. If you want you can PR some more examples for both JS and C++.

I plan to write some as soon as I get some time, btw what happened to multithreaded example, it's empty atm 😕

Hehehe - yeah that's what happens when you need to quickly fix some build errors - just remove the code and voila! :smile_cat:
There are "examples" in tests that you can look at. I really should take some time and write some documentation soon.

Haha I'll take a look at examples, and congratulations on your release ✌

Yeah thanks.

Oh yeah, some more C++ examples will be really helpful :-) Some questions I'm currently searching for:
How to gracefully close the server and disconnect all clients? Is this the correct way? hub->getDefaultGroup<uWS::SERVER>().close(); - nothing else? All done by µWebSockes? Seems so ... cool :-)
Is it correct, that it force-closes all clients after max 15 seconds timeout then? (I think, this is a very good default, but there's currently no chance to change it, right?)
Another example would be, how to send to multiple clients (but not all). I found the broadcast() method and its optimization to prepareMessage() / sendPrepared() / finalizeMessage() and the reference-counted WebSocket-message - is it the best, to just copy this code and do my own loop? By the way a very nice performance feature, which should be better promoted in examples to show the power of the library ;-)

Yep, spot on. I do recommend using the prepareMessage and just loop over your own subset. The 15 sec is just a shot from the hip - it could be made an argument instead.

Examples can be seen in test/main.cpp

Is broadcast in multithread possible? Is this correct piece of code?
Still trying to wrap my mind around uWS.

Hi ! Since this issue seems to be an acceptable way of asking questions, I had one, if I may :)
I need to keep track of connected clients in a vector<Some_Class_Which_Contains_The_Socket>.
Problem : I want to clean this vector when a client disconnects by erasing the appropriate entry, but since the socket seems to be already destroyed, I can't use the operator == (crashes with segfault). Can this be achieved in any way ?
It would seem like a good C++ example :) I still have trouble with understanding the code without comments. Good luck documenting that, and thanks in advance for your answer :-)

If you have trouble storing the WebSocket as is (I think this should work?) then you can instead try and store the WebSocket::getPollHandle() and use that to construct a WebSocket(poll handle) with. But I think it should work without that

I confirm that storing the uv_poll_t* instead of the socket fixes the issue. Thanks a bunch man !

Hello! I figured I'd ask a question too. How can I send stuff to a specific clients? Is there a vector or something that contains every connected client?


dereferencing pointer to incomplete type ‘struct clone_args’

For libzpoline.so, i type the following command.
make
I get the following error: main.c:242:9: error: dereferencing pointer to incomplete type ‘struct clone_args’
if (ca->flags & CLONE_VM)

Thank you for your message.
I have updated the program in https://github.com/yasukata/zpoline/commit/773a09f0064a109ef2f930a9eddd08fb2f0f7635 ; I hope this change fixes the reported issue.
I would appreciate it if you give us another message here if you still see the same error after applying the change above.
Thank you very much for reporting the issue.

Thank you for your reply.
But for libzpoline.so I type the following:
make
and I get another error:
gcc -O3 -pipe -g -rdynamic -Werror -Wall -Wunused-function -Wextra -shared -fPIC -DSUPPLEMENTAL__REWRITTEN_ADDR_CHECK -c -o main.o main .c
gcc -O3 -pipe -g -rdynamic -Werror -Wall -Wunused-function -Wextra -shared -fPIC -DSUPPLEMENTAL__REWRITTEN_ADDR_CHECK -o libzpoline.so main.o -lopcodes -ldl
/usr/bin/ld: main.o: relocation R_X86_64_PC32 against symbol `syscall_hook' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
Makefile:33: recipe for target 'libzpoline.so' failed
make: *** [libzpoline.so] Error 1
Does the error mean suggests that there is a relocation issue with this symbol ？

Thank you for your quick reply.
Actually, I already have the pointer to the solution https://github.com/yasukata/zpoline/issues/11 , but I have not reflected it yet.
I made a change in https://github.com/yasukata/zpoline/commit/aa18e55fea1caaa2ab3f0505467218947d21ba0a to resolve this issue, and I hope that now you can compile the program.
Again, I would appreciate it if you write another message here if you still see the compilation error.
Thank you very much for your report.


Fix browser build sync and alive behavior

This PR is in response to Trio Issue #373. In addition to fixing the main build for GitHub actions, this also brings in these other changes:

update macos up to version 14
explicitly set Xcode version to 15.4
modify # Patch Fastlane Match to not print tables to not print user information in the clear

this was identified as a privacy issue in LoopWorkspace (happened in macos-14, not seen previously when using macos-13)

This PR uses changes to LoopWorkspace PR 164 following release of Loop version 3.4.0.
The timing is such that the main branch must exist and this PR be applied at the same time.
Status:

The Browser Build for Trio will not run using this PR until the main branch actually exists

Test

In order to test, I modified build_trio.yml in the test fork to use the dev branch for both alive-main and alive-dev
The build action was successful with this modification.

Code Review:
I compared the *.yml files found in LoopWorkspace (main, aka 3.4.1)
These 3 are identical:

validate_secrets.yml
add_identifiers.yml
create_certs.yml

These files differ only in references to LoopWorkspace vs Trio and LoopWorkspace embeds a section on customizations that it not found in Trio:

build_loop.yml vs build_trio.yml

In addition to the files listed above, comparison was also made between LoopWorkspace 3.4.1 for these files:

Gemfile
Gemfile.lock
fastlane/Fastfile

The first two files are identical. The Fastfile has the suitable changes between Loop and Trio along with some whitespace changes. The Trio version configures and uses the BUNDLE_ID which simplifies some lines.

Status
Success
Caveat - might still have some users with alive branch failures - if so, they just need to delete any branch starting with alive and then run again.
Testing
This can be tested now that there is a main branch at nightscout/Trio

Before - it would fail because SHA_MAIN was null

Test Overview:

Use loopdocs-tester GitHub username.
Need to have the branch name be called dev for the test.
Do the merge of patch from this PR into dev for just loopdocs-tester.

Test dev branch with PR 374 applied

Success: build Trio (dev) with this patch (so one commit ahead of nightscout:dev)

alive-dev and alive-main created

Test main branch

add new branch using nightscout:main
this is identical to dev branch but without the PR applied

there is no alive branch

Success: build Trio (main)

alive branch created


Runtime error handling using Duktape

Hi svaarala,
Could you please give me an idea how to handle runtime errors on javascript such as those in onclick events and invalid parameters using duktape? Is duk_safe_call effective in handling runtime errors? duk_peval helps catch syntax errors perfectly. Am I missing something.
Thanks a lot.

duk_safe_call() would work for both errors in the user callback and also in the C code setting up the call (e.g. looking up the callback):

duk_safe_call() into a wrapper function
In that wrapper function, look up the onClick handler (there are many ways to arrange that, e.g. use an index and an array of callback functions stored in the Ecmascript global object)
Still in the wrapper function, duk_call() or duk_call_method() into the handler

Another alternative is to trust your onClick handler lookup code to not throw errors. In that case you can:

Lookup the onClick handler (carefully avoiding errors)
duk_pcall() or duk_pcall_method() into the handler; these are protected calls and will catch errors

Note that in general it's not 100% possible to avoid errors even when looking up the onClick handler. For example, you may run out of memory which causes an error to be thrown from pretty much any call. So I would recommend the first approach, duk_safe_call().

yes, duk_safe_call() seems to work fine. I do have another question, I read the following link
https://github.com/svaarala/duktape/issues/253
on reference error line number and the lineNumber property works great in the js code. However if I were to retrieve the reference error line number from the C layer just like it's done with syntax errors using duk_peval, is there a way i can achieve that?


Do not overide default action because of raw_destroy

I ❤ to fix bugs by removing code. My life seems fulfilled every time I do so. Thanks @Ladas !!!
We can drop this as the raw_destroy is now callback on the OrchestrationTemplateVnf and it is
called anyway. This code would call it twice in row and possibly make ems confused.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1414881
The cause of the bug was, that delete_resource action must return action-result-hash and this was returning nil.
@miq-bot add_label bug, euwe/yes, api
@miq-bot assign @abellotti

@isimluk Any way to write a test validating that destroy only gets called once?  It would then fail before this PR and succeed with it.

+1
@isimluk I am glad I could help. :-)
although the hook seems to be conditional https://github.com/Ladas/manageiq/blob/cdc6c6319475c225cf0e5b970298c8a5a6bf8d29/app/models/orchestration_template_vnfd.rb#L6-L6 so it should not fire, unless you change the condition?

Good food for thoughts.
This will need to have some work on remote_proxy thing.
@miq-bot add_label wip

@abellotti, I have run into a dead end with https://github.com/ManageIQ/manageiq/pull/14266, so I changed this pr to just fix the bug. It is now ready for review. Thanks!

That fix looks right.  Is this euwe/yes still ? if so does it depend on other PRs and have those been euwe/yes. Thanks.

looks great :+1:

Is this euwe/yes still ?

Yes.

if so does it depend on other PRs and have those been euwe/yes.

Unfortunately, no. Dust settles on the other parts of the code.

Thanks @isimluk 👍

Euwe backport details:
$ git log -1
commit 9608b9009e5306ede9b6862abba3eee681b02f83
Author: Alberto Bellotti<EMAIL_ADDRESS>Date:   Tue Mar 21 15:03:23 2017 -0400

    Merge pull request #14097 from isimluk/rhbz#1414881

    Return result of destroy action to user, not nil
    (cherry picked from commit 9aa0cfe1ea89a277b7cf28efe0024ee21a0d3b3c)

    https://bugzilla.redhat.com/show_bug.cgi?id=1434952


Bluetooth: Audio: Fix bad buffer pointer in get_pac_records

This change fixes a buffer use from pointer-by-value to correctly
intended pointer.
Signed-off-by: Fredrik Danebjer<EMAIL_ADDRESS>

@fredrikdanebjer If you are rebasing to re-run tests, then please re-run the tests directly from the Github UI instead: They will still run on the newest main, but when you rebase you PR and push it again, you dismiss all reviews.

@Thalley ah, I didn't realize. That sounds much better, will keep it mind  :D


Requested PR for "Incorrect Battery Readings #568"

This is my "Second attempt" first try on Java Script Please have a look on the xiaomi_battery_3v block beginning in line 168 and the function toPercentageCR2032 beginning in line 43.
I'd love if this works. ;-)

Thanks!

Thank you for your great work on this project. When will this be included in an update of Zigbee2MQTT docker?


Review how we select which docker image version we use

Currently we have a 'override value' if statement in our helm files. This will allow users to override our default values of using the dev GCR repo and latest tag with whatever they use in their values.yaml
          {{- if .Values.deployment.imageOverride.enabled }}
          image: "{{ .Values.deployment.imageOverride.repo }}:{{ .Values.deployment.imageOverride.tag }}"
          {{- else}}
          image: "eu.gcr.io/sbat-gcr-release/securebanking/${{ .Chart.Name }}:{{ .Chart.AppVersion }}"
          {{- end}}

We should remove this as if the customers set imageOverride to false, then they will try and get the images from our repo, which, firstly they won't be able to do so although helm will deploy successfully there'll then be an 'imagepullerror' in kubernetes. Secondly there could be an issue with customers knowing our repo and in general our repos being public in github with regards to being spammed or something along those lines.
If we go down this route, we'll need to move any values to do with the image repo and name into our sbat-cd repo for our internal dev deployments, and use the secure-api-gateway-relenv-deployments repo for dev
If we are happy having our repo name in a public repo, then we need to see if we can override the values in the individual charts values.yaml to turn off the override so that we are using the else part of the if statement, so that we don't have to provide a value for the tag. This become a problem when deploying 1.0.1, where we upped the UI chart version to 1.0.1, but didn't update secure-api-gateway-relenv-deployments to use the docker image 1.0.1 so image 1.0.0 would still be pulled down. Where as if we use the {{ .Chart.AppVersion }} value instead, we only need to make one change

This has been completed in #939


Arbot2

hello paris neo, congratulations and success with this beautiful project! You know that artbot is not working to create images. thank you so much

Git pull successful in /root/Documents/lollms/shared/auto_sd
Service did not become available within the given time.
Couldn't load personality at /root/Documents/lollms/personalities_zoo/art/artbot
Traceback (most recent call last):
File "/root/lollms-webui/api/init.py", line 857, in rebuild_personalities
personality = AIPersonality(personality_path,
File "/root/installer_files/lollms_env/lib/python3.10/site-packages/lollms/personality.py", line 156, in init
self.load_personality()
File "/root/installer_files/lollms_env/lib/python3.10/site-packages/lollms/personality.py", line 273, in load_personality
self._processor = module.Processor(self, callback=self.callback)
File "/root/Documents/lollms/personalities_zoo/art/artbot/scripts/processor.py", line 77, in init
super().init(
File "/root/installer_files/lollms_env/lib/python3.10/site-packages/lollms/personality.py", line 1002, in init
self.install()
File "/root/Documents/lollms/personalities_zoo/art/artbot/scripts/processor.py", line 109, in install
self.prepare()
File "/root/Documents/lollms/personalities_zoo/art/artbot/scripts/processor.py", line 116, in prepare
self.sd = self.get_sd().LollmsSD(self.personality.lollms_paths, "Artbot", max_retries=-1)
File "/root/Documents/lollms/shared/auto_sd/lollms_sd.py", line 186, in init
subprocess.Popen(script_path, cwd=self.sd_folder)
File "/root/installer_files/lollms_env/lib/python3.10/subprocess.py", line 971, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "/root/installer_files/lollms_env/lib/python3.10/subprocess.py", line 1863, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
PermissionError: [Errno 13] Permission denied: PosixPath('/root/Documents/lollms/shared/auto_sd/lollms_webui.sh')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/root/lollms-webui/api/init.py", line 870, in rebuild_personalities
personality = AIPersonality(
File "/root/installer_files/lollms_env/lib/python3.10/site-packages/lollms/personality.py", line 156, in init
self.load_personality()
File "/root/installer_files/lollms_env/lib/python3.10/site-packages/lollms/personality.py", line 273, in load_personality
self._processor = module.Processor(self, callback=self.callback)
File "/root/Documents/lollms/personalities_zoo/art/artbot/scripts/processor.py", line 77, in init
super().init(
File "/root/installer_files/lollms_env/lib/python3.10/site-packages/lollms/personality.py", line 1002, in init
self.install()
File "/root/Documents/lollms/personalities_zoo/art/artbot/scripts/processor.py", line 109, in install
self.prepare()
File "/root/Documents/lollms/personalities_zoo/art/artbot/scripts/processor.py", line 116, in prepare
self.sd = self.get_sd().LollmsSD(self.personality.lollms_paths, "Artbot", max_retries=-1)
File "/root/Documents/lollms/shared/auto_sd/lollms_sd.py", line 186, in init
subprocess.Popen(script_path, cwd=self.sd_folder)
File "/root/installer_files/lollms_env/lib/python3.10/subprocess.py", line 971, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "/root/installer_files/lollms_env/lib/python3.10/subprocess.py", line 1863, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
PermissionError: [Errno 13] Permission denied: PosixPath('/root/Documents/lollms/shared/auto_sd/lollms_webui.sh')

Hi. Artbot2 is renamed artbot, the version is in the yaml file.
It is advised for old users to remove the sd_auto file from their personal folder's share and reinstall the personality. The installer will install my custom version of auto1111's stable diffusion and run it when you talk to artbot.
If you still have an error don't hesitate to come to the discord channel, i check it more often than the github.

parisneo reinstall everything from 0 and I can't use arbot, the error is the one above

Looks like you have some permission problems. Try running it with priviliges (sudo)

I reinstalled everything from 0 and ran with sudo but it's still the same. Also with docker-compose same problem

It looks like you have a specific problem on your pc. What install method are you using ?
There are many ways to install on linix. Are you using conda?


Fail to extract some images

(I apologise in advance, this is probably more suitable for a discussion, but since those aren't enabled, I'm posting it here.)
Consider this page, for example: https://www.lrt.lt/en/news-in-english/19/2159940/lithuania-plans-to-deport-kazakh-activist-despite-calls-by-meps
The main content seems to be wrapped with article.article-block but the the images inside the article (not the "header" image) somehow fail to be captured -- the command below returns only the images' credits, text below the photos, but not the images itself:
curl -s https://www.lrt.lt/en/news-in-english/19/2159940/lithuania-plans-to-deport-kazakh-activist-despite-calls-by-meps | html2md -s 'article.article-block' -i

So, I tried adding div.media-block__container, div.media-block__wrapper or img.media-block__image but with no success :)
But maybe you could advise something? Any hint?
Thanks :)

A follow up: the images in question weren't loading because the src attribute wasn't present (images were lazy-loaded).
Some workarounds are mentioned here: https://github.com/JohannesKaufmann/html-to-markdown/issues/25


Spring Boot: autodetect *DataType beans

Update Spring Boot autoconfigurations to automatically register a JdbcDataTypeProvider/R2dbcDataTypeProvider if none is declared by the user and at least one bean of type JdbcDataType/R2dbcDataType is declared.
The new *DataTypeProvider won't be registered if no *DataType beans are declared by the user. It also won't override any explicit *DataTypeProvider bean declared by the user.
Technically, this might be a breaking change, as it would start registering JdbcDataType/R2dbcDataTypes declared as beans with the Komapper where previously they were not. However, there probably shouldn't be a need for user to declare those as beans unless they intend them to be registered with Komapper anyway.

Thank you for your feedback.
I plan to review it this weekend.

Technically, this might be a breaking change,

Understood. That is acceptable.


Initial implementation of veronoi to scatter chart

Hey @esbullington I implemented voronoi in scatter chart. It is working but I need you to review this branch. This was a quick code so please ignore bad naming, no Proptype etc.
There are something I am really not happy ( search for ugly hack in my code ). To implement voronoi, I have to concat all the data and add a new color property for each data(point).
Have a look when you're free and let me know what do you think.

Thanks, yang-wei, it works great despite the clever hack you had to do!  But you're right that it's a bit of an awkward workaround, not through any fault of your own.   We're definitely at the point where we need to figure out application-wide state, or our workarounds will become increasingly hacky.  You had to create that hack to overcome our lack of a way to pass around application state (the other option would have been to pass a callback around, but that gets old fast).
With this in mind, I went ahead and pushed a branch that uses EventEmitter to address this particular issue of passing around a bit of state, in this case which polygon path element has a mouseover event.  It allows us to keep the DataSeries as they are now (which I'd prefer since I want to continue to be able to pass in custom properties for each data series to a React component).
I used your Voronoi code to make a separate Voronoi component (in common/voronoi), to which I pass EventEmitter pubsub system, which notifies the Circle component when its corresponding Voronoi polygon has a mouseover event (I used the dataseries name + array index for a unique composite key to link together the circle and polygon).
I plan on switching this simple pubsub system to the Flux pattern soon -- I just need a little more time.
I may will still use a cursor to model the state of chart frames, but the Flux pattern will help us deal with these little bits of cross-cutting ephemeral state, and for various notifications.
Anyway, if you'd like to pull down this voronoi branch and adapt/polish it, and then use it to modify this PR (or make a new one), that'd be fine since a lot of that code was written by you.  I'm afraid I can't merge this PR as it is now since we need the DataSeries to remain modular and to correspond 1-to-1 with the data series that are passed in.  But it was a clever solution!

Ok so we're using event here. I like that ! Just realised the test wasn't passed haha. Will open another pr based on your branch. Thanks for everything @esbullington . Will close this =)


Some Issues in Data Processing Modules

Hi, I notice some issues in all three files './src/datasets/bail.py&credit.py&german.py'.
Take 'bail.py' as an example:

Line13 self.load(self.processed_paths[0])
Maybe you mean self.data = torch.load(self.processed_paths[0])[0]?

Line14 sens_idx = 1
I think the sens_idx for bail is supposed to be 0.

Line15 self.data.x[:, sens_idx] = self.data.sens
I don't understand what this line does, since self.data.x[:, sens_idx] always equals to self.data.sens

Line31 self.save([data], self.processed_paths[0])
Maybe you mean torch.save([data], self.processed_paths[0])?

Thank you so much for your issues.
For the first question and fourth question, the code is correct. I just use the methods in parent class. You can check the code of in_memory_dataset here to find the load method and save method.
For the second question, you are correct. I have updated the code based on the sens_idx in nifty code.
For the third question, in the processing part we may do some normalization or transformations for the x. But we don't wan t to affect the sensitive attribute. Thus, we have a manual operation here to give the sensitive attribute in the feature matrix the original value, which is stored in self.data.sens.
I'm really grateful for your careful checking and all the questions. After I rewrote my code in pytorch lightning, I do not have time to review the code carefully. Your comments are really helpful. If you have any questions, please feel free to open more issues.

Hi, thanks for the quick reply.
You are right about Q1,3&4. The reason why I didn't find save & load method in InMemoryDataset is that I installed torch_geometric==2.0.2 (due to some GPU driver limitations), not 2.3.1 as requested. In torch_geometric==2.0.2, InMemoryDataset doesn't have save & load method.
Anyway, thanks for addressing my issures so clearly!


Update bower.json

First congratulations on your recent release,
but it seems that you omitted to update the bower.json that still reference to leaflet 0.7.x.
Can you please quick fix it.
Edit: by the way: is the leaflet-proj-refactor branch still needed or can master be used now ?

My bad, I will fix it for you!
On Wed, Jan 25, 2017 at 9:10 PM +0100, "Philippe Weber" <notifications<EMAIL_ADDRESS>wrote:
First congratulations on your recent release,
but it seems that you omitted to update the bower.json that still reference to leaflet 0.7.x.
Can you please quick fix it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/kartena/Proj4Leaflet/issues/133, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABMFbxeWh17D61XWl__LAYrYpC52fkYrks5rV6wtgaJpZM4Lt8N6.

It's in review in #134
The leaflet-proj-refactor branch should not be used anymore.

Fixed in #134

Sorry but can you also tag 1.0.1 in git, otherwise it's not usable from bower

Done!


Cannot read property 'color' of undefined

What are the steps to reproduce?
Open a node red editor with custom nodes installed
What happens?
I use a nodered environment with around 110 custom nodes. I installed these nodes using npm install [foldername].
Now whenever I open nodered I get errors about node-red not being able to read the color of undefined:

Say for example I have a node called "activity quality control":

When I keep my breakpoint at the same spot and filter for the same node type and continue the code it will come back in the same method at some point with the color:

What do you expect to happen?
I feel like this method is called too early for custom nodes or this method should contain a null check preventing the error.
Please tell us about your environment:

[ ] Node-RED version: 1.2.9
[ ] Node.js version: 12.18.4
[ ] npm version: 6.14.8
[ ] Platform/OS: Windows
[ ] Browser: Chrome/Edge
[ ] running in Docker: No

We're going to need more information to understand what is happening here.
There is nothing special about 'custom' nodes versus any node that has been npm installed - they all get loaded into the editor in exactly the same way.
When exactly did this error start occurring? Was it immediately after you installed your custom nodes?
If you've installed 100s of custom nodes have you ruled out it being a bug with one of them?

Based on your information that customnodes get loaded at the same time as normal nodes I did some extra research.
For the development I tried to use as much typescript as possible. This resulted in me using require.js to develop the node definition in a .ts file:

it looks like this require.js is a little bit too slow for node-red resulting in the node not being loaded when NodeRed calls the getNodeColor function.
I'll try to find another workaround for this.
Thanks for your information!

Closing this issue as you've found the issue in your code.

@GerwinvBeek, I just had the same error using the same setup npm install [foldername].
It turned out that my customNode.html had a data-help-name that didn't match the name of the node. Fixed that and the error was gone.
So there's that...


Invalid Windows .dll

Describe the bug
Something is wrong with Windows .dll. I'm trying to port r6-dissect-bun to Node.js with node-ffi-napi.
It gives a V8 failure:
#
# Fatal error in , line 0
# Check failed: result.second.
#
#
#
#FailureMessage Object: 00000043CB2FBBD0
 1: 00007FF7DAA5815F v8::internal::CodeObjectRegistry::~CodeObjectRegistry+114079
 2: 00007FF7DA97343F std::basic_ostream<char,std::char_traits<char> >::operator<<+65023
 3: 00007FF7DB652D52 V8_Fatal+162
 4: 00007FF7DB0BE0CD v8::internal::BackingStore::Reallocate+637
 5: 00007FF7DB307849 v8::ArrayBuffer::GetBackingStore+137
 6: 00007FF7DAA2A3B9 napi_get_typedarray_info+393
 7: 00007FFFB5EC8828
 8: 00007FFFB5EC7C19
 9: 00007FFFB5ECD003
10: 00007FFFB5ECED79
11: 00007FFFB5ECEF18
12: 00007FFFD6B326E6 FFI::WrapPointerImpl+134 [...\node_modules\ffi-napi\src\ffi.cc]:L28
13: 00007FFFD6B33943 FFI::FFI::InitializeBindings+3571 [...\node_modules\ffi-napi\src\ffi.cc]:L138
14: 00007FFFD6B376E7 FFI::InitializeBindings+471 [...\node_modules\ffi-napi\src\ffi.cc]:L339
15: 00007FFFD6B389C0 Napi::details::WrapCallback<<lambda_4b130013be4a466940e6fe08d32cda83> >+64 [...\node_modules\node-addon-api\napi-inl.h]:L74
16: 00007FFFD6B38918 Napi::details::CallbackData<Napi::Value (__cdecl*)(Napi::CallbackInfo const &),Napi::Value>::Wrapper+40 [...\node_modules\node-addon-api\napi-inl.h]:L115
17: 00007FF7DAA24B9B node::Stop+36395
18: 00007FF7DB2D6256 v8::internal::Builtins::code_handle+172790
19: 00007FF7DB2D5E49 v8::internal::Builtins::code_handle+171753
20: 00007FF7DB2D610C v8::internal::Builtins::code_handle+172460
21: 00007FF7DB2D5F70 v8::internal::Builtins::code_handle+172048
22: 00007FF7DB3A9671 v8::internal::SetupIsolateDelegate::SetupHeap+494673
23: 00007FF7DB33BB1E v8::internal::SetupIsolateDelegate::SetupHeap+45310
24: 00007FF7DB33BB1E v8::internal::SetupIsolateDelegate::SetupHeap+45310
25: 00007FF7DB33BB1E v8::internal::SetupIsolateDelegate::SetupHeap+45310
26:<PHONE_NUMBER>8B4A3B

node: 16.14.1
ffi-napi: 4.0.3
To Reproduce
Steps to reproduce the behavior:

Go to https://speedtesting.herokuapp.com/peviewer/
Import libr6dissect.dll
See error

Expected behavior
It should work the same as libr6dissect.so

so you did get this working with linux?
the ffi function should be reworked soon to expect a buffer, instead of Go freeing the output.
either 1) dll never worked or 2) buffer needs to be implemented
i haven't tested the windows dll because Bun does not yet support windows

They released experimental Bun build for Windows along with 1.0.0 release.
I got working .so with WSL, but tsc-watch or any watchers don't support WSL 2 well. RIP DX 🥲
Also, I got this V8 failure while tinkering with an HTTP-only Discord bot in serverless environment. Most likely I should compile r6-dissect by myself.
#
#
#
# Check failed: result.second.
# Fatal error in , line 0
#
#FailureMessage Object: 0x7efd7f5dc7d0
1: 0xb75ed1 [/function/runtime/nodejs/bin/node]
2: 0x1c08724 V8_Fatal(char const*, ...) [/function/runtime/nodejs/bin/node]
3: 0xfcd741 v8::internal::GlobalBackingStoreRegistry::Register(std::shared_ptr<v8::internal::BackingStore>) [/function/runtime/nodejs/bin/node]
4: 0xd1ef88 v8::ArrayBuffer::GetBackingStore() [/function/runtime/nodejs/bin/node]
5: 0xabdab0 napi_get_typedarray_info [/function/runtime/nodejs/bin/node]
6: 0x7efd94198566 [/function/code/node_modules/ref-napi/prebuilds/linux-x64/node.napi.node]
7: 0x7efd94198dad [/function/code/node_modules/ref-napi/prebuilds/linux-x64/node.napi.node]
8: 0x7efd7f5ea4f3 FFI::WrapPointerImpl(Napi::Env, char*, unsigned long) [/function/code/node_modules/ffi-napi/build/Release/ffi_bindings.node]
9: 0x7efd7f5ecce4 FFI::FFI::InitializeBindings(Napi::Env, Napi::Object) [/function/code/node_modules/ffi-napi/build/Release/ffi_bindings.node]
10: 0x7efd7f5ee3c5 FFI::InitializeBindings(Napi::CallbackInfo const&) [/function/code/node_modules/ffi-napi/build/Release/ffi_bindings.node]
11: 0x7efd7f5ef3fb Napi::details::CallbackData<Napi::Value (*)(Napi::CallbackInfo const&), Napi::Value>::Wrapper(napi_env__*, napi_callback_info__*) [/function/code/node_modules/ffi-napi/build/Release/ffi_bindings.node]
12: 0xab44dd [/function/runtime/nodejs/bin/node]
13: 0xd53d8e [/function/runtime/nodejs/bin/node]
14: 0xd551af v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [/function/runtime/nodejs/bin/node]
15: 0x15f0bf9 [/function/runtime/nodejs/bin/node]
runtime pid 89: killed by signal 5

node 16.14.1, Ubuntu 18.04 LTS, libc 2.27

I compiled valid .dll with these scripts https://github.com/BadCoder1337/r6-dissect/commit/5ed34c8205798f27a5188032f86541173f2dafe6
It works in the main thread, but doesn't in worker_thread due to the issue https://github.com/node-ffi-napi/node-ffi-napi/issues/125

I'm going to look into the Windows DLL myself soon and figure out why GitHub Actions is causing problems. Also, I will likely implement a child process / worker implementation for Node on the r6-dissect npm package. Node FFI just looks a little buggy and slow.

Thanks for the scripts, I will consider your changes when I look into the release workflow

Consider koffi FFI library.
According their benchmarks it much faster and also works in a worker thread.
Working:
new (require("worker_threads").Worker)(`
  require("fs").writeFileSync("./test/dump.json",
    require("koffi")
      .load("./lib/libr6dissect-windows-amd64.dll")
      .cdecl("dissect_read", "str", ["str"])
      ("./test/Match-2023-09-23_12-03-31-55-R07.rec")
  )`,
  { eval: true }
)

Not working:
new (require("worker_threads").Worker)(`
  require("fs").writeFileSync("./test/dump.json",
    require("ffi-napi")
      .Library("./lib/libr6dissect-windows-amd64.dll",
        { dissect_read: ["string", ["string"]] }
      ).dissect_read("./test/Match-2023-09-23_12-03-31-55-R07.rec")
  )`,
  { eval: true }
)


Error in dataset: index of the target word does not agree with the target word itself

Line 50 of the dataset specifies target word "莫名其妙" and target word index 1, but the actual word at index 1 is "可怕". It seems that the target word is correct and the target word index should be corrected to 9. It is the only item in the dataset with this problem.
https://github.com/luxinyu1/Chinese-LS/blob/363bbc482e72caae35ed71cf09e49f3b2b087999/dataset/annotation_data.csv#L50

Thanks for this issue, we will fix it recently.


Complex outputs from TFT blueprint tests

For some test cases we may need complex outputs from a blueprint test. We currently support GetStringOutput however we may require others like OutputList, OutputMap etc. We should either export the getTFOptions from tft package and directly enable usage of terratest or create wrappers for common output types.

We should export getTFOptions to avoid wrapping every terratest function.


Cannot override default error page with Laravel 11 Bootstrap Exception Handling

Laravel Version
11.20.0
PHP Version
8.3.1
Database Driver & Version
No response
Description
In Laravel 10, it was possible to utilise Laravel's exception handling for internal/application errors, whilst having a fallback for errors that did not meet that criteria (e.g. incorrect database credentials).
For example, in Laravel 10, the App\Exceptions\Handler@render method could be...
public function render($request, Throwable $exception)
{
    // If local environment, or an exception that should not be reported,
    // allow Laravel to handle rendering.
    if (app()->environment('local') || $this->shouldntReport($exception)) {
        return parent::render($request, $exception);
    }

    // Specific handling of TokenMismatchException (e.g., redirect with error message, or return JSON error if AJAX).
    // This CAN be handled in Laravel 11
    if ($exception instanceof TokenMismatchException) {
        return $this->handleTokenMismatch($request);
    }

    // Get an appropriate status code for the exception, defaulting to 500.
    $code = $this->getStatusCode($exception);

    // Return a generic error page to the user
    return response()->view('errors.generic', ['code' => $code], $code);
}

In Laravel 11, this does not appear to be possible without overriding the whole exception handler due to the loss of access to knowing if an exception should be ignored or not.  Something like this does not work as it would return the generic error pages for errors like unauthenticated etc.
$exceptions->render(function (Throwable $e, Request $request) use ($exceptions) {
    // Not possible to check if an exception is unreportable
    if (app()->environment('local')) {
        return;
    }

    // Get the status code from the exception
    $code = ...;

    return response()->view('errors.generic', ['code' => $code], $code);
});

If no rendering is specified and it's left to Laravel, then errors that do not return specific HTTP exceptions (the easiest to replicate being incorrect database credentials) will return a generic Symfony error page. These exceptions ignore the 5xx, 500 etc. custom error pages that you can configure.
Steps To Reproduce

Generate an exception that does not have HTTP error handling, such as incorrect database credentials in the .env
Load page that triggers the exception
You'll see Symfony's generic error page shown

Hey there, thanks for reporting this issue.
We'll need more info and/or code to debug this further. Can you please create a repository with the command below, commit the code that reproduces the issue as one separate commit on the main/master branch and share the repository here?
Please make sure that you have the latest version of the Laravel installer in order to run this command. Please also make sure you have both Git & the GitHub CLI tool properly set up.
laravel new bug-report --github="--public"

Do not amend and create a separate commit with your custom changes. After you've posted the repository, we'll try to reproduce the issue.
Thanks!

After attempting to create a replicate (and being unable to), I narrowed it down to an exception occuring within our error template under certain conditions (e.g. no database/invalid credentials). This was causing by a view composer that was applied to the top-most layout, that all other layouts extended.
When Laravel attempted to render our error pages, it would encounter an exception and result in Laravel returning a Symfony error page.
I've fixed it by removing the specific logic from the top-most layout, alternatively I could have used a simplified error layout.
Apologies for the false report.


[Enhancement & Bug?] Better P9K_VPN_IP_INTERFACE default

This is a small change to also register interfaces that are not just tun but also every interface that starts with "tun".
I do have another problem though:
My non-active VPN interface (tap0) is UP and my actually working VPN (tun0) ins UNKNOWN.
p9k::parseIp currently needs the interface to be UP. This breaks the segment for me atm.
❯ /sbin/ip -brief -4 a show
lo               UNKNOWN        <IP_ADDRESS>/8
wlp42s0          UP             <IP_ADDRESS>/24
tap0             UP             <IP_ADDRESS>/24
docker0          DOWN           <IP_ADDRESS>/27
tun0             UNKNOWN        <IP_ADDRESS>/32

4AEE18F83AFDEB23

I'm going to merge this, as the change is fairly small. About your issue with the UNKNOWN state of your tunnel. Well, that is not a thing P9K can handle, as UNKNOWN can mean anything.. Do you have an idea how to change that check?

Do you have an idea how to change that check?

Sadly, no, it might be an openconnect bug, but I couldn't find anything on it. Manually setting the interface to up did nothing. The VPN works well though... 🤷♀

Well, that is not a thing P9K can handle, as UNKNOWN can mean anything..

Agreed.


node.js stax vulnerability showing up in java

False positive on library stax:stax-api:1.0.1 - reported as cpe:/a:st_project:st:1.0.1 for CVE-2017-16224 - seems to me like it should be node only
<dependency>
    <groupId>stax</groupId>
    <artifactId>stax-api</artifactId>
    <version>1.0.1</version>
</dependency>

Thanks for the report - I will cycle through all of the FP reports before the next release.


Passing config_file argument for ROS2 Wrapper v3.1.5

Required Info

Camera Model
D435i

Firmware Version
<IP_ADDRESS>

Operating System & Version
Linux (Ubuntu 20.04)

Kernel Version (Linux Only)
5.11.10

Platform
PC

SDK Version
2.44

Language
{C/C++/Python}

Segment
ROS2

Issue Description
Hi!
Intel releases new ROS2 wrapper supporting foxy, eloquent and dashing.
I've modified rs_launch.py by moving all the configurable parameters into d435i.yaml file and updating config_file default value in rs_launch.py.
configurable_parameters = [{'name': 'camera_name',                  'default': 'camera', 'description': 'camera unique name'},
                           {'name': 'serial_no',                    'default': "''", 'description': 'choose device by serial number'},
                           {'name': 'usb_port_id',                  'default': "''", 'description': 'choose device by usb port id'},
                           {'name': 'device_type',                  'default': "''", 'description': 'choose device by type'},
                           {'name': 'config_file',                  'default': "'config/d435i.yaml'", 'description': 'yaml config file'}
                          ]

With run :
ros2 launch realsense2_camera rs_launch.py
warning is printed:
[WARNING] [launch_ros.actions.node]: Parameter file path is not a file: 'config/d435i.yaml'
and parameters are not loaded correctly.
Parameters written in rs_launch.py or given as cmdl argument are loaded correctly.
Thank you.

Hi @daziFR   As a starting point in investigating your case, a ROS2 case from February 2021 in the link below provides a demonstration of configuration with a yaml file that may provide useful insights.
https://github.com/IntelRealSense/realsense-ros/issues/1640

Hi @MartyG-RealSense, this works fine with the wrapper intended for foxy only (v3.1.3 and v3.1.4). The problem is introduced with added support for dashing and eloquent.
From commits, change from ' ' to " ' ' " in configurable_parameters default values and in IfCondition is done for dashing support. But this introduced problem with foxy. Or I set the value wrong for the new wrapper.

Additionally, parsing config_file fails in dashing too:
[WARNING] [launch_ros.actions.node]: Parameter file path is not a file: '/home/test/intel_realsense_ros2_dashing/src/realsense2_camera/config/d435i.yaml'
[INFO] [realsense2_camera_node-1]: process started with pid [25304]
[realsense2_camera_node-1] terminate called after throwing an instance of 'std::runtime_error'
[realsense2_camera_node-1]   what():  Failed to parse parameters from file ''/home/test/intel_realsense_ros2_dashing/src/realsense2_camera/config/d435i.yaml'': Error opening YAML file, at /tmp/binarydeb/ros-dashing-rcl-yaml-param-parser-0.7.9/src/parser.c:1387
[ERROR] [realsense2_camera_node-1]: process has died [pid 25304, exit code -6, cmd 'stdbuf -o L /home/test/intel_realsense_ros2_dashing/install/realsense2_camera/lib/realsense2_camera/realsense2_camera_node --ros-args --log-level info __node:=camera __ns:=/camera __params:=/tmp/launch_params_r6nc9itn __params:='/home/test/intel_realsense_ros2_dashing/src/realsense2_camera/config/d435i.yaml''].

Additional info, If I make change in rs_launch.py:
parameters = [set_configurable_parameters(configurable_parameters)
                            ,{LaunchConfiguration("config_file")}
                            ],

to:
parameters = [set_configurable_parameters(configurable_parameters)
                            , PythonExpression([LaunchConfiguration('config_file')])
                            ],

in ros2 foxy, parameters from config_file do get parsed and there is no warning any more "parameter file is not a file".

Given the solution that you described above for Foxy, do you still have a problem that needs to be solved please?  Thanks!

With the given proposal problem is solved.
There is another problem with wrapper v3.1.5 when using Dashing.
If node is run before rviz2, Fixed frame cannot be modified. Check image:

If I run rviz2 first, and then node, this works fine.
Should i open new case for this?

There is an issue with dashing: tf2_ros::StaticTransformBroadcaster does not keep last msg for later subscription and a solution for intel wrapper: static tf broadcaster: workaround transient local durability (master branch).
With this fix issue mentioned above is gone.
Does Intel plan to support dashing, and include this missing patch?
Thank you.

RealSense ROS does now support ROS2 Dashing, Eloquent and Foxy with a single ROS2 wrapper.
https://github.com/IntelRealSense/realsense-ros/tree/ros2
At the time of writing this though, the Debian package versions of the ROS wrapper are temporarily inaccessible.
https://github.com/IntelRealSense/realsense-ros/issues/1814#issuecomment-823020133
The solution that you identified for the static tf broadcaster is for a ROS2 wrapper that is now obsolete and no longer supported.  The current actively developed ROS2 wrapper is unrelated to that older wrapper and so a fix made for that old wrapper could likely not be applied directly to the current wrapper.

"The solution that you identified for the static tf broadcaster is for a ROS2 wrapper that is now obsolete and no longer supported. The current actively developed ROS2 wrapper is unrelated to that older wrapper and so a fix made for that old wrapper could likely not be applied directly to the current wrapper."
I agree. For testing purposes I tried to apply patch and it does work, but as you mentioned, there might be another solution.
I hope this issue will be reviewed by the Intel ROS2 wrapper developers.

Thanks very much @daziFR for your test.  I suggest creating an issue about it on the RealSense ROS forum.
https://github.com/IntelRealSense/realsense-ros/issues

Thanks @MartyG-RealSense, I've created new issue on the RealseSense ROS forum.

Thanks very much for the RealSense ROS issue creation.

Hi @daziFR  Do you require further assistance with this case, please?  Thanks!

No thanks.
Topic can be closed.

Thanks very much @daziFR for the update!


Limit the Snowplow tracker logs

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3319
Originally created by @edgarrmondragon on 2022-03-07 23:30:58

What is the current bug behavior?
What is happening now?
The snowplow tracker library is printing logs on every CLI invocation that is tracked. This is a bit distracting and not something we want users to see all the time.
What is the expected correct behavior?
What should be happening?
Commands should not display tracking logs by default.
Steps to reproduce
How one can reproduce the issue?

Run any CLI command that is currently tracked in GA
Don't use any custom logging.yaml so the the default logging config is used
Notice the log lines at the end re Snowplow tracking coming from the libray

Relevant logs and/or screenshots
Please use code blocks (```) to format console output

Possible fixes
If you can, link to the line of code that might be responsible for the problem or suggest a fix
Set the level of the snowplow_tracker.emitters logger in the default config to ERROR.
With that change, these lines can probably be removed:

https://gitlab.com/meltano/meltano/-/blob/cli-init-experience/src/meltano/cli/initialize.py#L36 (see https://gitlab.com/meltano/meltano/-/merge_requests/2562)
https://gitlab.com/meltano/meltano/-/blob/02a512b62ac5a8c63a0aff25763cde915fdeec12/tests/meltano/core/test_tracking.py#L44-45

Further regression test
Ensure we automatically catch similar issues in the future

[ ] Write additional adequate test cases and submit test results
[ ] Test results should be reviewed by a person from the team

View 4 previous comments from the original issue on GitLab


[TB] Additional Outputs

Enable the ThemeBuilder to generate outputs suitable for mobile or desktop environments such as Xcode.

Split this issue into two:

Generate mobile web output
Generate native mobile Xcode / Android artifacts


[HELP] Error: Failed to install the app.

When I write"react-native run-android", I have an error
Description

React Native version:
info Fetching system and libraries information...
(node:10788) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use node --trace-warnings ... to show where the warning was created)
System:
OS: Windows 10 10.0.17763
CPU: (16) x64 AMD Ryzen 7 2700X Eight-Core Processor
Memory: 8.67 GB / 15.95 GB
Binaries:
Node: 15.1.0 - E:\Program Files (x86)\node\node.EXE
Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.8 - E:\Program Files (x86)\node\npm.CMD
Watchman: Not Found
SDKs:
Android SDK:
API Levels: 28, 29, 30
Build Tools: 29.0.2, 30.0.0, 30.0.2
System Images: android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
Android NDK: Not Found
Windows SDK:
AllowAllTrustedApps: Enabled
AllowDevelopmentWithoutDevLicense: Enabled
Versions: 10.0.17763.0, 10.0.18362.0
IDEs:
Android Studio: Not Found
Visual Studio: 16.7.30523.141 (Visual Studio Community 2019)
Languages:
Java: 1.8.0_272 - C:\Program Files\OpenJDK\openjdk-8u272-b10\bin\javac.EXE
Python: 3.8.5 - C:\Python38\python.EXE
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.63.3 => 0.63.3
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found
Expected Results
React-native app shoud start with android emulator

Did you follow the instructions here for Windows / Android and setup the development environment?

It may be related to the fact that you have non ASCII characters in your path, https://stackoverflow.com/questions/46145053/react-native-run-android-in-emulator-throws-erro?

Proble was in the wrong path to ^Error: Cannot find module<EMAIL_ADDRESS>I just had to reinstall @react-native-community with npm i @react-native-community/cli


[W6.4f][W14-B2] Heng Zhi Xuan Caryn

Done LO-Abstract

@hzxcaryn
Accepting this PR with just a minimal review because

nothing much to take note of here, or
another of your PRs for this tutorial was reviewed in detail


Extended SMILES saved from Ketcher might be invalid for RDKit

Steps to Reproduce

Click "Open..." button
Click "PASTE FROM CLIPBOARD"
Input SMILES c1cccc(-c2ccc(Nc3cccc4c(=O)[nH]ccc34)nc2)c1
Save as Extended SMILES, and the result would be C1C=C(C2C=NC(Nc3c4c(c(ncc4)=O)ccc3)=CC=2)C=CC=1
Go to RDKit.js official website, in their online code demo, input and run:

var smiles = "C1C=C(C2C=NC(Nc3c4c(c(ncc4)=O)ccc3)=CC=2)C=CC=1"; // generated by Ketcher in step 4
var mol = RDKitModule.get_mol(smiles);
console.log(mol.is_valid())

Actual behavior

Value of mol.is_valid() in RDKit.js website is false.
Also, using RDKit to draw molecule image would fail.

Expected behavior
Smiles generated by Ketcher should all be valid to RDKit?
Ketcher version .
2.6.2

yes, aromatic bonds were not converted correctly for double bond Oxygen and aromaticity is kept as atom - which should not be a case (it should be converted to ":" bonds). It is suggested to un-aromatize such structures

@AlexanderSavelyev - I have a report from users that led me to this issue. Could you confirm that it is the same?
Load N#Cc1cn[nH]c1N, it will be saved as N#Cc1c(N)nnc1. This SMILES string is recognized by Biovia Draw and ChemDraw, but not RDKit 2020.09.5 (Python):
>>> m = Chem.MolFromSmiles('N#Cc1c(N)nnc1')
[19:51:56] Can't kekulize mol.  Unkekulized atoms: 2 3 5 6 7

A colleague helped me with the reasoning in terms of chemistry :)

It seems related to tautomers and aromaticity. The exported SMILES is ambiguous, and RDKit does not make extra assumptions in order to generate a valid structure, while it seems that Biovia Draw and ChemDraw do.
In our example, either nitrogen in the ring could have an H attached. N#Cc1cn[nH]c1N specifies its location, while N#Cc1c(N)nnc1 does not. When Ketcher processes the aromaticity of the ring, the location of the H is lost. RDKit does not restore the H, leading to an invalid structure. Similarly, in this GitHub issue, the original SMILES specifies a tautomeric [nH], but the information is lost when Ketcher processes the aromaticity of the molecule.

Need to switch to indigo for smiles generation

The bug appears because interchange KET-format doesn't support explicit implicit hydrogens count which can be specified in bracketed SMILES atoms as a virtual hydrogens counter. Typically it's not an issue but there are special cases when the standard valence model fails to determine the number of suppressed hydrogens. For instance In the example above, N-atom is connected to aromatic ring, so the automatic hydrogen counting is not possible. To avoid the ambiguousness [nH] explicitly specifies the number of implicit hydrogens = 1 for the nitrogen atom. To fix the issue on the ketcher's side:

add implicitHCount field to the atom entity of ket-format schema:
 "hImplicitCount": {
   "type": "integer",
   "enum": [0, 1, 2, 3, 4, 5]
 },

As ketcher has own parser/generator of MOL V2000, corresponding conversion of virtual hydrogens counter hImplicitCount to the "chemaxon style" Data S-Group should be implemented. I.e. if a MOL V2000 file has a data group as below:

M  STY  1   1 DAT
M  SLB  1   1   1
M  SAL   1  1  18
M  SDT   1 MRV_IMPLICIT_H
M  SDD   1     0.0000    0.0000    DA    ALL  1       1
M  SED   1 IMPL_H1
it should be converted to an atom's property implicitHCount and for generating of MOL V2000 the data S-Groups should be added basing on the implicitHCount value.
Some info about MRV_IMPLICIT_H data s-group:
http://www.scfbio-iitd.res.in/software/utility/marvin_new/marvin/help/FF/Chemaxon-specific-information-in-MDL-MOL-files_19693843.html

Functionality for supporting implicit hydrogens for mol v2000 format will be implemented separately as part of #2500


bug - cannot save file without explicit extension

When trying to save a file without explicitly giving an extension the UI silently fails (does not save the file, does not raise an error)
The command line/console log says:
writing: D:/SharpCap Captures/2024-01-16/Sun/AS_P75/2024-01-16-0853_3-Sun_Red_lapl4_ap1955_conv-enhancedcolor-redline
Error: Failed to save D:/SharpCap Captures/2024-01-16/Sun/AS_P75/2024-01-16-0853_3-Sun_Red_lapl4_ap1955_conv-enhancedcolor-redline, likely bad file extension. Try .PNG

OpenCV(4.8.0) D:\a\opencv-python\opencv-python\opencv\modules\imgcodecs\src\loadsave.cpp:696: error: (-2:Unspecified error) could not find a writer for the specified extension in function 'cv::imwrite_'

try the latest. I switched it so that save filepicker forces png or tif/tiff. It's theoretically possible to save a .png file without an extension, but the underlying image library doesn't support it directly. It determines the file format from the file extension and throws an exception if it doesn't understand, which includes absence of extension. But now it shouldn't be possible to get that exception - the filepicker automatically adds png if you omit it.

Thanks!


simplify "setup" process for reporting

by default configurable .env and var files should be placed using "*.original" naming convention.
during setup we have to update them using user content and rename, for example:
.env.original -> .env

finished: https://github.com/zebrunner/reporting/pull/2194
test scenario:

clone current reporting repo, switch to develop branch

git clone https://github.com/zebrunner/reporting.git
cd reporting
git checkout develop

try to start:

./zebrunner.sh start

->  warning message should appear
WARNING! unable to proceed without setup procedure! Please, execute:
./zebrunner.sh setup

setup reporting and start

./zebrunner.sh setup
# provide valid protocol, host and port
./zebrunner.sh start

reporting is up&running, default admin can log

Verified. Fixed.


Update to STIX 2.0 RC1

And slip in some styling improvements too.

The changes in RC2 are minor and do not affect this.

Looks great, thanks!


bugfix in compile and add merge_multi_product

Codecov Report
Attention: 23 lines in your changes are missing coverage. Please review.

Comparison is base (9147ef0) 64.19% compared to head (84217b3) 64.15%.
Report is 2 commits behind head on computgraph.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@               Coverage Diff               @@
##           computgraph     #145      +/-   ##
===============================================
- Coverage        64.19%   64.15%   -0.04%
===============================================
  Files               56       56
  Lines             3854     3909      +55
===============================================
+ Hits              2474     2508      +34
- Misses            1380     1401      +21

Files
Coverage Δ

src/FeynmanDiagram.jl
75.00% <ø> (ø)

src/computational_graph/ComputationalGraph.jl
100.00% <ø> (ø)

src/computational_graph/transform.jl
97.28% <93.75%> (-0.75%)
:arrow_down:

src/backend/static.jl
39.36% <50.00%> (+0.98%)
:arrow_up:

src/computational_graph/optimize.jl
86.25% <0.00%> (-8.93%)
:arrow_down:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Output interface.

Hi! Is it possible to specify the output interface for multicast output in linux?  something like this:
tsp -I ip <IP_ADDRESS>:1234 -O ip  vlan3@<IP_ADDRESS>:1234

Please RTFM (or tsp -O ip --help)
  -l value
  --local-address value
      When the destination is a multicast address, specify the IP address of
      the outgoing local interface. It can be also a host name that translates
      to a local address.

  --local-port value
      Specify the local UDP source port for outgoing packets. By default, a
      random source port is used.

sorry, already found...


Retain Page States

Hi there,
Is there a way to retain Page States between tabbing?

@rgodlontonshaw New release (v2.0.3) is available now and I believe your issue is sorted out.


[RadioButton] Missing documentation for "label" parameter

The component RadioButton needs a label to look right (I am not sure whether there are also some use cases where a label is not needed), but the label attribute is not documented, it is just passed along ...others.
Should this be documented?
I can submit a PR if needed.

@barbu110 This is the description for label: "Used internally by RadioButtonGroup. Use the labelPosition property of RadioButtonGroup instead Where the label will be placed next to the radio button."


iptables failed

Often encounter below problem when trying to start a container via groovy client lib:
de.gesellix.docker.client.DockerResponse(status:[text:Internal Server Error, code:500, success:false], headers:Content-Length: 419 Content-Type: application/json Date: Tue, 12 Jul 2016 02:48:01 GMT Server: Docker/1.12.0-rc3 (linux) , contentType:application/json, mimeType:application/json, contentLength:419, stream:null, content:[message:driver failed programming external connectivity on endpoint anony-WebHiveSql_master (50070d9139a670a89d21b7c617156e9d382ea858604b4976fef00b32897e84db): iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 20000 -j DNAT --to-destination <IP_ADDRESS>:8080 ! -i docker0: Fatal error: exception Unix.Unix_error(Unix.ENOTCONN, "open", "/var/log/service-port-opener.log")  (exit status 2)])
the container config is like:
{
"Cmd": [
"/sbin/init"
],
"Image": "deploy_img:1.0",
"Mounts": [
{
"Source": "/tmp/docker-deploy/anony-WebHiveSql_master//scripts",
"Destination": "/scripts",
"RW": true
},
{
"Source": "/tmp/docker-deploy/anony-WebHiveSql_master//web-hive-sql",
"Destination": "/tmp/logs/web-hive-sql/",
"RW": true
},
{
"Source": "/Users/andy/.gradle/",
"Destination": "/root/.gradle/",
"RW": true
},
{
"Source": "/Users/andy/.ssh/",
"Destination": "/root/.ssh",
"RW": true
}
],
"ExposedPorts": {
"8080/tcp": {
}
},
"HostConfig": {
"Binds": [
"/tmp/docker-deploy/anony-WebHiveSql_master//scripts:/scripts",
"/tmp/docker-deploy/anony-WebHiveSql_master//web-hive-sql:/tmp/logs/web-hive-sql/",
"/Users/andy/.gradle/:/root/.gradle/",
"/Users/andy/.ssh/:/root/.ssh"
],
"PortBindings": {
"8080/tcp": [
{
"HostPort": "20000"
}
]
}
},
"Tty": true
}
Since neither Mac OS nor the target container has "iptables", so I guess it may be an issue with hyperkit.

I think you are using Docker 4 Mac? Is so then please report it there including the UUID given via the "Diagnose & Feedback" item on the Whale menu (i.e. with logs). Please also include the actual Dockerfile and commands you are running (or anonymised/cut-down versions which exhibit the issue).
With that then the Docker 4 Mac team will be able to triage to the appropriate component. Based on the above I don't think this is a hyperkit issue though so I'm going to close this for now.


build+lnwallet: notify wallet upon relevant transaction confirmation

In this PR, we update our btcwallet dependency to include the latest changes that aim to address the recently discovered SendOutputs issue. This issue was caused by the wallet no longer requesting to be notified of when a transaction that pays to a change address confirms on-chain. This has been addressed by the dependent btcwallet PRs listed below.
This PR also includes fixes for minor issues that arose once addressing the original issue. Descriptions for those can be found in their respective commit in-line.
Depends on #2175, https://github.com/btcsuite/btcwallet/pull/571, https://github.com/btcsuite/btcwallet/pull/573.
Fixes #2011.

Investigated the test failure and concluded that it's expected as the transaction is spending an input under control of Alice, so she requests a spend notification for it.


Improve isScanning behavior

Implementing the same logic as for the isConnected function.

Shouldn't we remove the Log before we commit?

Since I am resolving the promise if the manager is null, I at least want to send a log message to the android debugger in this case. Do you think it's unnecessary?