Status code: null. Only on Android release build.

At await openAI.onChatCompletion(request: request), I got an error like below.

status code :null message :null data:null

This only happened when I tried a release build on a real Android device, not a debug build on an Android emulator or a debug/release build on an iOS simulator.
Also, the debug build worked fine on the real machine, so it doesn't seem to be a device problem.
Or do I have to do something special on a real Android device?
Package version: 2.0.4
[✓] Flutter (Channel stable, 3.7.6, on macOS 13.2.1 22D68 darwin-arm64, locale ja-JP)
    • Flutter version 3.7.6 on channel stable at /Users/yukikomine/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 12cb4eb7a0 (10 days ago), 2023-03-01 10:29:26 -0800
    • Engine revision ada363ee93
    • Dart version 2.19.3
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /Users/yukikomine/Library/Android/sdk
    • Platform android-33, build-tools 32.1.0-rc1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.76.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.60.0

[✓] Connected device (3 available)
    • iPhone 8 Plus (mobile) • 083471F2-780D-49E5-A78B-4EE552A1B560 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-4 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 110.0.5481.177

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!
yukikomine@YukinoMacBook-Pro chat_ai %

Thank you.

On Sat, 11 Mar 2566 BE at 23:35 komineyuki @.***> wrote:

At await openAI.onChatCompletion(request: request), I got an error like
below.
status code :null message :null data:null
This only happened when I tried a release build on a real Android device,
not a debug build on an Android emulator or a debug/release build on an iOS
simulator.
Also, the debug build worked fine on the real machine, so it doesn't seem
to be a device problem.
Or do I have to do something special on a real Android device?
Thank you.
—
Reply to this email directly, view it on GitHub
https://github.com/redevRx/Flutter-ChatGPT/issues/18, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKLSYJJRZMOZ2C6ECXFZVDLW3SSWNANCNFSM6AAAAAAVXSJVAI
.

This error occurs as soon as I call the function.
But I will try it later.
Thank you.

I tried it but didn't work.
HttpSetup(
        receiveTimeout: const Duration(seconds: 20),
        sendTimeout: const Duration(seconds: 20),
        connectTimeout: const Duration(seconds: 20)),

Can you find the differeces between Debug build and release build?

I'm so sorry. I just forgot to give permission.
Thank you for your reply and, thank you for creating such a good package.

I'm getting same issue, can you give me detail explanation about the solution? What permission did you add?

I'm so sorry. I just forgot to give permission. Thank you for your reply and, thank you for creating such a good package.

@dhiyaulhaqZA I just added these two lines: android.permission.INTERNET and android.permission.ACCESS_NETWORK_STATE.
android/app/src/AndroidManifest.xml
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example.gpt">

    <uses-permission android:name="android.permission.INTERNET"/>
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>

    <application
        ....

I hope this solves your problem.

I'm getting this issue on Android 7.0, i tested with Android 9 and 13, it work perfectly but with Android 7.0, the response always is
I/flutter ( 1688): error:  I/flutter ( 1688): status code :null  message :null  I/flutter ( 1688): data:null

@redevRx After debugging inside your package, I found that the error was caused by the exception "CERTIFICATE_VERIFY_FAILED: certificate has expired(handshake.cc:393)", can you please check it ?

Thank you it will check it.

I'm getting same issue on Android only (working fine on iOS), can you give me detail explanation about the solution? What permission did you add?

I'm so sorry. I just forgot to give permission. Thank you for your reply and, thank you for creating such a good package.

This issue caused by CERTIFICATE_VERIFY_FAILED and solved by adding trusted certificate. This solution solves my problem: https://stackoverflow.com/a/69481863

Thanks for sharing your solution

Try
class MyHttpOverrides extends HttpOverrides{
  @override
  HttpClient createHttpClient(SecurityContext context){
    return super.createHttpClient(context)
      ..badCertificateCallback = (X509Certificate cert, String host, int port)=> true;
  }
}

void main(){
  HttpOverrides.global = new MyHttpOverrides();
  runApp(MyApp());
}


Clarification on Stream.version

In the javadoc of Stream.version, it says that the version can be a list of comma-separated versions:
https://github.com/wildfly-extras/wildfly-channel/blob/e1410ae8535470df03521700781ba21848cf8a94/core/src/main/java/org/wildfly/channel/Stream.java#L50
but in the json schame, it says that: This must be either a single version.
https://github.com/wildfly-extras/wildfly-channel/blob/e1410ae8535470df03521700781ba21848cf8a94/core/src/main/resources/org/wildfly/channel/v1.0.0/schema.json#L79
We need to keep the version requirement consistent in the 2 places above.

@gaol Who is verifying this? what it should be? either single version or both?

@moulalis , maybe @jmesnil or @spyrkob can comment on this

Thanks @gaol that should be a single version only


Git gutter is missing inner color with doom themes

Hi!
Sorry, more fringe issues, I wasn't sure if I should reopen the old issue I created in regards to the size of the fringe.
Here is how my fringe with git gutter looks with the dracula theme:

and here is how it looks with the Doom One theme (which I'm currently using)

and Doom Dracula:

It's like the inner portion of the bar isn't being colored for some reason.  Is this a conflict with another setting I might have?

I solved this by just customizing the face, I'm not sure if that's what you did @hlissner for your screenshots.
I noticed that the diff-hl-* faces are not themed in the .el files.

@BrandonShega I also ran into the same issue. I customized the face as well, in my emacs.d config files.
Maybe this is worth reopening again?

@BrandonShega I use git-gutter. What you saw in my screenshots were custom bitmaps I defined for them.
Anyhow, as of 2526456 I've added matching backgrounds to the diff-hl faces, which should resolve this issue.

For posterity, if folks want to undo this, use:
(custom-set-faces
  '(diff-hl-change ((t (:background nil)))
  '(diff-hl-delete ((t (:background nil)))
  '(diff-hl-insert ((t (:background nil))))


Merge pull request #2 from SaschaWillems/master

What is this PR supposed to do? No changes as far as I can see?


[MRG] ENH: Add function to search for specific connections

This PR turned into a gauntlet of if/else statements so I'd definitely love some input if you guys see a place to simplify. In any case I am quite happy with the functionality and to my eyes everything seems to be working correctly. The API works as follows:
net.pick_connection(src_gids='L2_pyramidal', target_gids=[0, 1, 2])

Will return the index of any connections in net.connectivity that both contain L2 pyramidal cells as src_gids, and [0, 1, 2] in the set of target_gids.
net.pick_connection(receptor=['nmda', 'ampa'])

Will return all connections that have either NMDA or AMPA synapses.
More succinctly, supplying a list to a single parameter corresponds to a logical_or, whereas supplying multiple parameters corresponds to a logical_and across the parameters. While it's wordy to explain, I find this setup to be the most intuitive with what I expect in a search function.
Let me know what you guys think!

Codecov Report

Merging #367 (9ead04c) into master (27c63b8) will decrease coverage by 1.14%.
The diff coverage is 85.27%.

:exclamation: Current head 9ead04c differs from pull request most recent head 638c47f. Consider uploading reports for the commit 638c47f to get more accurate results

@@            Coverage Diff             @@
##           master     #367      +/-   ##
==========================================
- Coverage   91.00%   89.86%   -1.15%
==========================================
  Files          13       15       +2
  Lines        2557     2949     +392
==========================================
+ Hits         2327     2650     +323
- Misses        230      299      +69

Impacted Files
Coverage Δ

hnn_core/params_default.py
100.00% <ø> (ø)

hnn_core/viz.py
83.48% <57.60%> (-7.45%)
:arrow_down:

hnn_core/extracellular.py
86.69% <86.69%> (ø)

hnn_core/network.py
94.07% <98.88%> (+0.89%)
:arrow_up:

hnn_core/dipole.py
94.00% <100.00%> (-0.02%)
:arrow_down:

hnn_core/network_builder.py
92.63% <100.00%> (+0.58%)
:arrow_up:

hnn_core/parallel_backends.py
82.00% <100.00%> (-0.71%)
:arrow_down:

hnn_core/utils.py
100.00% <100.00%> (ø)

hnn_core/cell_response.py
83.73% <0.00%> (-0.57%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

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

More succinctly, supplying a list to a single parameter corresponds to a logical_or, whereas supplying multiple parameters corresponds to a logical_and across the parameters. While it's wordy to explain, I find this setup to be the most intuitive with what I expect in a search function.

I think this makes sense to me!

I like this @ntolley !!!

@ntolley I recommend changing the title back to [WIP] when you are not actively seeking reviews or waiting for the PR to be merged. These prefixes allow us to filter the PRs that need attention: https://github.com/jonescompneurolab/hnn-core/pulls?q=is%3Apr+is%3Aopen+MRG. Probably not a biggie here but more important in larger projects that you may want to contribute to in the future :)

Ready for more reviews here. The major change is the addition of check.py which cleans up a lot of redundant code in both net.add_connection, and net.pick_connection. I'll have to do a sweep to see if there's anything else that can benefit from the existing functions, or can be simplified by moving generic input checking to this file.

Just some minor comments. Looks fine otherwise!

Sorry for the delay, I'll try to look look through this tomorrow!

I went ahead and merged @rythorpe so we can keep the ball rolling. I hope it's okay. Thanks a lot @ntolley for the PR !

Sounds good, sorry @ntolley for taking so long! This will help a lot with unifying drive and local network connectivity.


Clicking a global role name in the global roles list leads to a 404

rancher/rancher:master 7/25
Clicking a global role name in the global roles list leads to a 404 error message.
Navigate to Security > Roles from the navigation mentu.
Click on the "Global" tab.
Click on a role name in the list to view the role.
User is presented with a 404.
The error message suggests it is searching for the role in role templates instead of global roles.

Version - 2.0 master 7/30
Verified fixed


Update Developer Guide Non-Functional Requirements

Add tags to each non-functional requirement (NFR) to track the aspects of the application that have been covered by NFRs.
Add requirement on recoverability and security in case of data corruption as well as basic protection of data.
Rename persons to students to reflect our adaptation of AB3
Resolves #11

Codecov Report

Merging #39 (01cb929) into dev (2d332ea) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev      #39   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Continue to review full report at Codecov.

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

Updated scalability/capcity NFR to 100 only. Can merge if all is ok

LGTM!


Fix documentation

See https://github.com/readthedocs/readthedocs.org/issues/8357.

https://readthedocs.org/projects/robotics-python/builds/14286036/ doesn't show the import warning anymore 👍🏽


"swapoff" still need to be done manually

I found that "swapoff" still need to be done manually if you want to init master or join node, and there's no log can give me a hint this need to be done manually.
You can see log below:
hui-zhi@linux-2kew:~/caasp> skuba node join --role worker --user hui-zhi --sudo --target <IP_ADDRESS> node1
W0926 18:05:15.989078   14507 ssh.go:306]
The authenticity of host '<IP_ADDRESS>:22' can't be established.
ECDSA key fingerprint is 30:8a:10:f1:4f:c2:75:1e:bb:f4:65:fb:b0:2f:f5:bf.
I0926 18:05:15.989141   14507 ssh.go:307] accepting SSH key for "<IP_ADDRESS>:22"
I0926 18:05:15.989149   14507 ssh.go:308] adding fingerprint for "<IP_ADDRESS>:22" to "known_hosts"
[join] applying states to new node
[join] failed to apply join to node failed to apply state kubeadm.join: Process exited with status 1
F0926 18:08:03.703525   14507 join.go:51] error joining node node1: failed to apply state kubeadm.join: Process exited with status 1
hui-zhi@linux-2kew:~/caasp> sudo swapoff -a
hui-zhi@linux-2kew:~/caasp> skuba node join --role worker --user hui-zhi --sudo --target <IP_ADDRESS> node1
[join] applying states to new node
[join] node successfully joined the cluster
hui-zhi@linux-2kew:~/caasp>

There is informationo about swap removal in our documentation
There is also bug#1151689 about default verbosity level.
Can you see error about swap problem in your output when you run skuba with -v 5 argument?

IMHO, I don't think we should assume every CaaSP customer start with SLE15-SP1 installation, they may have exist SLE15-SP1 with swap enabled. we should expose the useful kubeadm log and only hide what we can handle automatically. The current log doesn't help.
I have not tried with -v 5 argument, but I think we need to show what exactly failed and what we recommend customer to do.

You can see it on log if you uses "-v 3"

IMHO, I don't think we should assume every CaaSP customer start with SLE15-SP1 installation, they may have exist SLE15-SP1 with swap enabled. we should expose the useful kubeadm log and only hide what we can handle automatically. The current log doesn't help.
I have not tried with -v 5 argument, but I think we need to show what exactly failed and what we recommend customer to do.

We specifically had this reported by someone who installed on existing SLE
https://github.com/SUSE/doc-caasp/issues/517
Is manual disabling of SWAP still necessary for other installation types?

IMHO, I don't think we should assume every CaaSP customer start with SLE15-SP1 installation, they may have exist SLE15-SP1 with swap enabled. we should expose the useful kubeadm log and only hide what we can handle automatically. The current log doesn't help.
I have not tried with -v 5 argument, but I think we need to show what exactly failed and what we recommend customer to do.

We specifically had this reported by someone who installed on existing SLE
SUSE/doc-caasp#517
Is manual disabling of SWAP still necessary for other installation types?

On bare metal, yes, but not sure about others. I think we should expose the "swap off" to customers if it caused by it, even without "-v 5" argument.


v2.8.4 Cannot install js from the domain: https://raw.githubusercontent.com/

What is the problem?
js cannot install
How to reproduce it?

open https://github.com/ParticleCore/Iridium/raw/master/src/Userscript/Iridium.user.js
no tab pop up for install

What is the expected result?
a tab pop up for install js
What is the actual result?
no tab pop up for install
Environment

Browser: maxthon
Browser version: newest
Violentmonkey version: newest
OS: win7

Same problem here.
OS: Windows 10 64bit

you can now install js from url


Support custom SSL certificates and completely disabling cert validation

Currently, the workerd runtime blocks requests to domains with custom SSL certificates for security reasons. This is a problem when using proxies or when developing with Spin.
Related #1745
This PR adds support for Node's NODE_TLS_REJECT_UNAUTHORIZED=0 (disable cert validation) by using Node's fetch instead of workerd's fetch. Also, it supports Node's NODE_EXTRA_CA_CERTS=file by forwarding this custom cert in a Node variable to workerd:
# Disable certificate validation
NODE_TLS_REJECT_UNAUTHORIZED=0 npm run dev

# Provide additional CA certificates
NODE_EXTRA_CA_CERTS=/usr/.../ca-certificates/my-file.crt npm run dev

More info: https://github.com/cloudflare/workers-sdk/issues/5345

After testing a bit with @jsaubry , I've changed the approach and removed the original --disable-network-filter flag in favor of reusing Node's environment variables, since developers are already familiar with that.


Index Problem

where it says, "element = soup.contents[0]" it should say "element = soup.contents[1]" so that it goes to the Tag element and not the NavigableString element

Thanks for letting me know. What file is this in?

dfs.ipynb is currently working for me in both my development environment and Colab.
If you still think something is incorrect, please provide the information I need to replicate the error you are seeing.


TS Server fatal error:  Debug Failure. unexpected PrivateIdentifier

TypeScript Version: 3.8.3
Steps to reproduce crash
1.
2.
3.
TS Server Error Stack
Error: Debug Failure. unexpected PrivateIdentifier
    at forEachIdentifierInEntityName (tsserver.js:32705:30)
    at bindPotentiallyMissingNamespaces (tsserver.js:32579:35)
    at bindPropertyAssignment (tsserver.js:32644:31)
    at bindStaticPropertyAssignment (tsserver.js:32572:13)
    at bindSpecialPropertyAssignment (tsserver.js:32562:21)
    at bindWorker (tsserver.js:32114:29)
    at bind (tsserver.js:31991:13)
    at bindExpressionStatement (tsserver.js:31065:13)
    at bindChildrenWorker (tsserver.js:30566:21)
    at bindChildren (tsserver.js:30487:17)
    at bind (tsserver.js:32002:21)
    at tsserver.js:30493:94
    at bindEach (tsserver.js:30509:21)
    at bindEachFunctionsFirst (tsserver.js:30493:13)
    at bindChildrenWorker (tsserver.js:30603:21)
    at bindChildren (tsserver.js:30487:17)
    at bindContainer (tsserver.js:30433:17)
    at bind (tsserver.js:32005:21)
    at bindSourceFile (tsserver.js:30051:17)
    at Object.bindSourceFile (tsserver.js:29987:9)
    at initializeTypeChecker (tsserver.js:66293:20)
    at Object.createTypeChecker (tsserver.js:34785:9)
    at Object.getTypeChecker (tsserver.js:98416:79)
    at synchronizeHostData (tsserver.js:135228:21)
    at Proxy.getProgram (tsserver.js:135310:13)
    at InferredProject.Project.updateGraphWorker (tsserver.js:139786:53)
    at InferredProject.Project.updateGraph (tsserver.js:139729:42)
    at ProjectService.assignOrphanScriptInfoToInferredProject (tsserver.js:141705:25)
    at ProjectService.assignProjectToOpenedScriptInfo (tsserver.js:143132:26)
    at tsserver.js:143396:107
    at Object.mapDefined (tsserver.js:562:30)
    at ProjectService.applyChangesInOpenFiles (tsserver.js:143396:48)
    at Session.handlers.ts.createMapFromTemplate._a.<computed> (tsserver.js:144260:46)
    at tsserver.js:146003:88
    at IOSession.Session.executeWithRequestId (tsserver.js:145994:28)
    at IOSession.Session.executeCommand (tsserver.js:146003:33)
    at IOSession.Session.onMessage (tsserver.js:146027:35)
    at Interface.<anonymous> (tsserver.js:147342:27)
    at Interface.emit (events.js:203:13)
    at Interface._onLine (readline.js:316:10)
    at Interface._normalWrite (readline.js:461:12)
    at Socket.ondata (readline.js:172:10)
    at Socket.emit (events.js:203:13)
    at addChunk (_stream_readable.js:295:12)
    at readableAddChunk (_stream_readable.js:276:11)
    at Socket.Readable.push (_stream_readable.js:210:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:166:17)

@kanekko Do you have steps to reproduce this? Can you share an example project that triggers it?
Also please try upgrading your workspace to use typescript@next by installing this extension. After installing that and restarting VS Code, do you still see this issue?

Synthesized a repro:
const x = {};
x.#bar.baz = 20;

Even though this is a fatal error, it's a very low hitter so for in telemetry. Fixing in 3.9 sounds good


Put Height Warning In 'Agent Settings' page

Hi, If I make an agent with a height of n, and step height < n, a warning will appear in the inspector's Nav Mesh Surface section. I feel like it would be a nice enhancement to also have this warning in the Navigation pane itself. Just thought it would be a nice-to-have. If this is out of scope, then feel free to close this. Thanks!
(label this as enhancement I guess?)

Indeed, the Navigation > Agents window could use that warning message as well. Thank you for the suggestion.


chore: remove patch version from go version in go.mod

relates to https://github.com/gofrs/flock/pull/57#discussion_r1664265710

Hello,
technically speaking, the path part of the version is now a requirement, there is some tolerance for compatibility reasons.
I don't remember where I saw the explanation, I will find it.

:thinking: I didn't find where I saw that, maybe I made a confusion with toolchain.
Why is this important for you?

technically speaking, the patch part of the version is now a kind of requirement,

I guess since 1.22 correct?

I dont see anything in the documentation that implies youre forced to use 1.21.0 and cant go to 1.21.1. Everything in the go mod docs indicate that this is the minimum go version required for this package and consumers are free to go to a later version as needed.
Is there an error youre observing?

I understand what you called "noise" (the useless path version), I had the same reaction at the beginning.

I guess since 1.22 correct?

As I didn't find a reference, I will not be able to really answer this question.
From my memories, yes and no, as go1.21 introduced the behavior.
But without an official reference, I will not fight against this change.

Is there an error youre observing?

Now I'm forced to set 1.21.0 as version in go.mod when I vendor: https://github.com/moby/buildkit/actions/runs/9779428021/job/26998669203?pr=5118#step:5:539
Nothing functional that's just a nit but still...

I guess I will have the same issue in the future if someone is doing the same so not directly directed to you but go toolchain shenanigans 😅

I don't take it badly: I did it because I was thinking it was a good practice.

I think I have a kind of reference:

Go 1.21 introduces a small change to the numbering of releases. In the past, we used Go 1.N to refer to both the overall Go language version and release family as well as the first release in that family.
https://tip.golang.org/doc/go1.21

This means that go1.21 is now a "release family" and go1.21.0 is a version.

At go 1.21 or higher:

The go line declares a required minimum version of Go to use with this module.
...

https://go.dev/ref/mod#go-mod-file-go

The go directive should theoretically declare a version (the minimum version).
I know it's not really explicit, and I'm sure I read an explicit message about that, I'm annoyed to not find it.

I think I have a kind of reference:

Go 1.21 introduces a small change to the numbering of releases. In the past, we used Go 1.N to refer to both the overall Go language version and release family as well as the first release in that family.
https://tip.golang.org/doc/go1.21

This means that go1.21 is now a "release family" and go1.21.0 is a version.

At go 1.21 or higher:

The go line declares a required minimum version of Go to use with this module.
...

https://go.dev/ref/mod#go-mod-file-go

The go directive should theoretically declare a version (the minimum version).
I know it's not really explicit, and I'm sure I read an explicit message about that, I'm annoyed to not find it.

Ah thanks for this feedback, ok I get it better now.

The PR https://github.com/moby/buildkit/pull/5118 has been merged, is your PR still required?

Not required, I guess we can't do anything about it if we have other dep doing the same and related to your previous comment I think this is fine now. Thanks for your time!

@ldez I can add a bit of context on the why here because it's been a thorn for us (at work) for a while.
The new automatic toolchain upgrades introduced in Go 1.21 mean that the go directive in each of your dependencies' go.mod files gets fed into an MVS-style selection algorithm, which will update your go.mod file if necessary.  It also means that, by default at least, go build, go test, etc. will check that directive and automatically (and silently) download and use that specific version of Go.
As a library, though, the practical effect of this is that updating the Go version in our go.mod will force all downstream consumers to also use that version of Go (or a higher one).  I don't think that's a decision that library authors should be making for their consumers, so our go.mod should have the lowest version of Go that includes the features actually in use by the library's code and NOT whatever version any of us happen to be using locally for development.

our go.mod should have the lowest version of Go that includes the features actually in use by the library's code and NOT whatever version any of us happen to be using locally for development

Agree. How would we feel about using 1.15 since that was the latest version that the travisci build supported?

I think 1.19, or maybe 1.20, would be good since that shouldn't trigger any inadvertent/unwanted Go version changes downstream.

I talk about that inside Gofrs Slack channel.
The new MVS clarification of the meaning of the go directive creates a hard requirement since go1.21.
As a library, like you said, the version of go or dependencies should be handled very carefully.

The problem exposed to the PR is the difference between "release family" and "version".

I was thinking that setting it to 1.20 would be "safe" since everyone should be using at least 1.21 now, but that's definitely not a point I'm going to argue over.as long as we're not pushing consumers onto newer versions of Go.

Going forward, though, we shouldn't change the version unless we are using newer language features

I think 1.19, or maybe 1.20, would be good since that shouldn't trigger any inadvertent/unwanted Go version changes downstream.

I don't share this opinion because using unmaintained go1.19 or go1.20 is a security issue.
I think "forcing" the usage of a Go team-supported version (at least to the .0 patch) is not a bad practice.
But I'm against, for a lib, using the latest Go version (currently go1.22), or the latest patch version, unless it's really needed. (I think we agree on that)
I will not update the go directive after each new minor/major release of Go, but if I need to update Go I will update to the "old stable" version (currently go1.21).
(I think we also agree on that)

The whole versioning has become so complex; fun fact: go now can downgrade language versions per package / file; despite the go1.0 compatibility promise, it may disable features.
Another fun example; backward compatibility code (i.e. files with stubs for old go versions) may no longer always work; see https://github.com/opencontainers/runc/pull/4277#issuecomment-2114392288

using unmaintained go1.19 or go1.20

I guess my point is that the version of Go being used won't be what's in this library's go.mod, it will be whatever is specified by the consuming application.
FWIW, I've personally set GOTOOLCHAIN=local on my development machines so that it will always use what I have installed (1.22.5 right now).

Philosophically, I share @dylan-bourque's opinion. I'd prefer that we avoid compelling users to upgrade go versions unless we are leveraging a specific feature of the go version in our mod file. I definitely get that people should be upgrading, but the reality is there are some cases where they don't or can't for a number of reasons and using our package shouldn't get in the way of that.
That doesn't mean that we need to support old go versions. We can continue testing against stable and old stable, and guarantee that we fix bugs for latest go and the latest version of our package. I think though that we should not be the pressure that forces people to upgrade.

Definitely 👍 👍👍👍 on GOTOOLCHAIN=local ... I'm not a big fan of --help meaning; "download a binary and install" 🙈🙈 https://github.com/golang/go/issues/60956

I think we all agree on the background subject: don't update the Go version unless you needed.
I just have no problem defining the old stable as a requirement (not day one, and not the latest patch).

not a big fan of --help meaning; "download a binary and install"

@thaJeztah we had someone run into that with go list the other day

I found the reference I was thinking of (yes I never give up :smile:)
Code QL, when using at least go1.21, reports a warning:

This report is about this file.
module github.com/golangci/golangci-lint/scripts/gen_github_action_config

go 1.21

require (

The documentation reference inside the screenshot is https://go.dev/doc/toolchain#version


remove get_magnitudes

remove unnecessary get_magnitudes() in direction_constraint_optimizer

Codecov Report

Merging #35 into master will increase coverage by 1.24%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #35      +/-   ##
==========================================
+ Coverage   82.19%   83.43%   +1.24%
==========================================
  Files          57       57
  Lines        3174     3128      -46
  Branches      384      370      -14
==========================================
+ Hits         2609     2610       +1
+ Misses        407      361      -46
+ Partials      158      157       -1

Impacted Files
Coverage Δ

...olbox/optimizers/direction_constraint_optimizer.py
64.70% <ø> (+21.95%)
:arrow_up:

src/ast_toolbox/mcts/BoundedPriorityQueues.py
86.04% <0.00%> (+4.65%)
:arrow_up:

Continue to review full report at Codecov.

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


Does  Privilege clause support using wildcard (用户权限配置是否支持通配符

我创建了很多存储组。如：
`set storage group to root.js.nanjing.jiangning;
set storage group to root.js.nanjing.pukou;
set storage group to root.js.suzhou.zhangjiagang;
set storage group to root.js.yangzhou.gaoyou;`

现在我想赋予某个用户root.js路径下的存储组的权限该如何操作？
我在IoTDB上进行GRANT USER jsiot PRIVILEGES INSERT_TIMESERIES on root.js.*  操作，但是这样并没有生效
I create a lot of storage groups, e.g.:
`set storage group to root.js.nanjing.jiangning;
set storage group to root.js.nanjing.pukou;
set storage group to root.js.suzhou.zhangjiagang;
set storage group to root.js.yangzhou.gaoyou;`

Now I want to assgin the privilege of inserting data into timeseries which have prefix "root.js" to some user.
I tried  GRANT USER jsiot PRIVILEGES INSERT_TIMESERIES on root.js.* but failed.

Currently, IoTDB does not support it.  But this is a very good feature.
Does someone want to implement it?

well, I checked v0.12.4, it works like this:
GRANT USER jsiot PRIVILEGES 'INSERT_TIMESERIES' on root.js

好吧，我检查了 v0.12.4，它的工作原理是这样的： GRANT USER jsiot PRIVILEGES 'INSERT_TIMESERIES' on root.js


Virtual wire table has a typo

The VwId table for hub-to-spoke virtual wires has a typo where VwIds are incorrectly assigned.

Addressed in #9


Fix byterange variable assignments

Fixes #279

Looks good, thanks! Can you fix the pre-commit error so I can merge?

I've fixed this on master using your fix, thank you!


Confusion cased by the description on step 11 of color marker

Describe the Issue
While try to help camper in the forum https://forum.freecodecamp.org/t/preview-does-not-work-on-the-responsive-web-design-course/536554/4
He mentioned not being able to see the changes, after looking into it, I can see why this happened.
I think we should warn learners about this, like we do in skyline project, to reduce the coming confusion.
Affected Page
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-css-colors-by-building-a-set-of-colored-markers/step-11

What should the warning say exactly? I'm a little confused about why it doesn't show.

What should the warning say exactly?

I am leaving this part for people who smarter than me, and because I am worried that people will open a pull request without other people skimming in and voicing their opinion.
But to answer the question, we can alter the first paragraph and the last, and reword it, so people won't expect a color to be changed.

It's time to add some color to the page. Remember that one way to add

to something like

It's time to set color to the background. Remember that one way
...
and set its background-color property to red. this won't change the page

I can add this change if you would like. But if there is anything else other than rewording what it says, I might not be the best person for it.

I would wait for other people to voice their opinion

Yeah, that works for me. I'm excited to see what they do so I can learn from it lol.

Agreed @Sboonny, seems a little weird to mention at the beginning that they are going to add color but then they can't see any color added after they add the CSS. Personally, I might swap step 11 and 12 so that the div has width/height when they add the background color to it. But I can see how they built this up because step 12 explains why they didn't see any color immediately after completing step 11.
I might start the first sentence as:
"It's time to give the marker some color." or "It's time to add some color to the marker."
Just to make it clear that the background color they are adding is for the marker and not the "page".
And then ya, just add a little warning after the last sentence.
"Please note, the color will not appear yet after you add the CSS."

I do think that swapping step 11 and 12 might be better, but you could run into the same problem there. You would be adding a width and height, but nothing would show up on the page still. I would just change the descriptions cause it's easier.
Step 11:
Change the first sentence to "It's time to add some color to the marker."
And add "You will not see any changes after you add the CSS" after the last sentence.
Step 12:
Change the description to:
"The background color was applied, but since the marker div element is empty, it doesn't have any height by default.
"In your .marker CSS rule, set the height property to 25px and the width property to 200px.
^ Maybe overboard, but I swapped it so they add the height first since it's mentioned as the problem. Also, I remove the first sentence since we are mentioning it at the end of the previous step.
What do you all think?

Sounds good, Tom.  Does anyone want to take this up?

I'll work on these changes!

So I'm trying to find the file but everything is all different. How do I find this?


VMware.WorkstationPlayer version 17.5.0

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@stephengillie I believe this error is the same that we had with Vmware horizon. You may need to manually validate.

Automatic Validation ended with:

2024-03-11 23:39:10.005 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.38.33135.0

(Automated response - build 870.)

@wingetbot waivers Add Validation-Installation-Error

@stephengillie are you able to approve this one?

@stephengillie Odd (in a good way? 😄 ) that this PR got to a later stage to have it get considered for manual validation?
This one https://github.com/microsoft/winget-pkgs/pull/139465/ and other PRs for the same package didn't 👀

I've made the updates, can it be validated now? :)

Automatic Validation ended with:

2024-03-13T21:19:36.6808479Z ##[error] Manifest Error: Duplicate field found in the manifest. [Agreements]

(Automated response - build 870.)

Automatic Validation ended with:

2024-03-13T21:19:36.6808479Z ##[error] Manifest Error: Duplicate field found in the manifest. [Agreements]

(Automated response - build 870.)

Can you please add the exception again?

Looks good to me. Agreements need to be manually validated by an admin, so I'll leave the approve/merge to them

Hi @https://docs.vmware.com/en/VMware-Workstation-Player/17.5/rn/vmware-workstation-175-player-release-notes/index.html,
This package uses Agreements, but this PR's AgreementsUrl doesn't match the AgreementsUrl on file.
(Automated response - build 870.)


Monitor a validator on waiting list

Future support validator node functionalities for validator on waiting list
Hello, I was wondering if I could monitor my node as a validator, even when it's on the waiting list.
Currently, as at the setup process the program checks the get_eras_stakers, it will fail when we put the stash account of a none active validator account.
May I ask if there will be any support in the future for the functionalities of a validator node (current balance, current nominated stake, total stake etc) as a none active validator, or should we just put our node as monitoring node?

Hi @HikaruG  thanks for your question.
It is possible to monitor a validator which is not in the active set yet, in fact we monitor ours. Can you give me the stash address of the validator so that I can replicate the issue?
With regards to balances, we currently monitor the bonded balance when the validator is active though. For the time being we will not be adding further functionalities as we are focusing on other high-priority tasks related to PANIC. That being said, these functionalities you have mentioned are planned to be included in the future.

@dillu24 Hello, thanks for your response!
Here is my stash account: 5F21cD4mwgJLmc5GNaL3ooZtEin2mLJuku3rky5epWkbPCuJ.
It is a westend validator on the waiting list.
But how can one replicate this issue, given that this stash account parameter needs to be set with the linked running instance which has its sessionKey set to the controller account (that the stash account has bonded too)?
Understood for the priorities, thank you for answering my question !

So I replicated the issue by connecting with a public node, and setting stash_address to be your stash. The problem is not because your validator is not in the active set, but because Westend does not have Democracy capabilities.
Essentially, for PANIC to monitor any chain, all functions in the Polkadot JS API must be supported. From what I can see, the democracy functions are not supported. In fact, when the council members function is called PANIC starts to error.

Oh ok that makes more sense.
I also ended up getting theUndefined blockchain error with the monitor node mode, which made me realize that the validator has not the only problem.
Will try using my actual mainnet node, thank you for digging into the issue !

Just to also to point out, that the Undefined blockchain error is also due that democracy blockchain metrics cannot be imported by the blockchain monitor because they do not exist for Westend.


Damienbod/ignore properties configuration

PR from @os1r1s110
Properties can be ignored now using the atttribute JsonIgnore

@filipw @os1r1s110 Updated now with the improvements. Json attributes are per default active and can be opted out. The configuration has been renamed so it's clear that its only for the 2 json properties and it is usually not required to set this. (Optional).
Good? Time for a merge party and a release :)

json configuration removed, code clean up
@filipw @os1r1s110 review please


Properly handle nested array data in prepareDataForValidation.

Previously, we would always return an object even if values was an array. Now, we test to see if values is an array and set data accordingly.
I've included a test for this scenario.
Fixes #2213.

This fix didn't went in release of 2.1.4, right? I still have the issue 😢

@elmarburke No, it was merged just after 2.1.4 was released.

hi @jaredpalmer wanted to ask, if there any plan to release this fix in 2.1.5, and is there any plan in general release 2.1.5?

This is a pretty dreadful problem, since it makes nested arrays totally unusable. However I found a workaround, which is to install the CI version of Formik from just after the PR was merged: npm install https://pkg.csb.dev/jaredpalmer/formik/commit/157603ab/formik. You can also use newer builds listed on this page, but the command above seems to work okay for me.


+foo &bar ...  not recognized as valid syntax by dojo

in e.g. +transform &json +http://..., I think the motivating example was |init-auth-google &json .^(json %cx %/keys/json)?

This was actually closed in favor of #402, which contained some details that were missing here. Should've referenced. Will copy your edit over for you.

Ah, so the "+foo &eBay" was just a typoed spurios duplicate, got it


Update Dan-Daily-66308162-9b64-4d34-a8bc-fac71407f7d5.yml

The family_name and other_names/name were spelled "Daily" rather than "Daley"
The YAML file name also contains the error, but I believe that should be a different pull request, as I do not fully understand the impact of a change.

Pull Request Test Coverage Report for Build 789

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 62.233%

Totals

Change from base Build 766:
0.0%

Covered Lines:
931

Relevant Lines:
1496

💛  - Coveralls


Add support for https://api.slack.com/methods/users.lookupByEmail

Not sure if tests can be added here since the existing methods don't have them

The Travis failure is a known thing - the only 2 failed tests are these which need secret credentials, which you don't have.

Yes, I'll test this and add a comment to the method implementation here if needed :)

One thing to comment. I don't have experience with this API endpoint, but: https://api.slack.com/methods/users.lookupByEmail says "Custom bot users cannot use this method".
I am not sure how to interpret it. So beware it might not work as you expect.

Thank you!


Should VariableForProperty report lint for transparent and inherit?

  VariableForProperty:
    enabled: true
    properties:
      - color
      - font

.foo {
   color: inherit;
   font: inherit;
}

.bar {
   color: transparent;
}

This reports lint, but I'm not sure it should?
Similar to my reasoning here: https://github.com/brigade/scss-lint/issues/376#issue-59166822
Writing this seems like a smell...
$inherit: inherit;
$transparent: transparent;

.foo {
   color: $inherit;
   font: $inherit;
}

.bar {
   color: $transparent;
}

Thanks for the suggestion, @chris-dura.
I've added a quick fix to this in 5a8cac9a2121c37b688712fc28f35e7aaa97dd36.
Can you think of other property values for which it might make sense to ignore? We may need to create a dictionary of values to ignore based on the property in question.

Can you think of other property values for which it might make sense to ignore?

I added currentColor to the list: https://github.com/brigade/scss-lint/pull/433


Including support to inject Twig Runtime Loaders

Class Zend\Expressive\Twig\TwigRendererFactory modified to read the config key [twig][runtime_loaders] and inject the objects registered in it into the RuntimeLoaders list in the Twig_Environment.

I'm going to refactor this work after merging #15, as that pull request splits off the logic for creating the Twig_Environment.

:+1:

Thanks, @lucassabreu; merged to develop for release with 1.2.0.


Feature Request: Aurelia template

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:
Hi,
my "favourite framework" is Aurelia. But it is really complex to make it work with electron because of its module format and I don't have a solution for working with electron-compile. So it would be nice if someone can add a working Aurelia template to electron-forge.
I would love it.

Moved to https://github.com/electron-userland/electron-forge-templates/issues/44


Add E2E Test of the live preview feature by Playwright

Description
Resolve: #132
Blocked by: #129

Added minimal E2E testing by Playwright to prevent breaking the Live Preview feature
At this point, I am only testing that there is no error output to the browser console at all
In addition, I made sure to test for 3 patterns: maplibre, mapbox and geolonia
And I also made this test run on GitHub Actions
Right now, the live preview with mapbox is broken in the latest main branch, so the test is failing as intended!

Once the following pull request is merged, the test should pass
#129

IMPORTANT NOTE

Testing live preview with mapbox on local dev env has required to set the environment variable named mapboxAccessToken
Also testing on the GitHub Actions has required to add the Environment secrets on the repository settings
I am not authorized to manipulate the Secret of this repository, so I need someone who is authorized to do so.

Type of Pull Request

[x] Others (Adding more tests)

Verify the followings

[x] Code is up-to-date with the main branch
[x] No build errors after npm run build
[x] No lint errors after npm run lint
[x] No errors on using charites help globally
[x] Make sure all the exsiting features working well
[x] Have you added at least one unit test if you are going to add new feature?
[x] Have you updated documentation?

Refer to CONTRIBUTING.MD for more details.
Screenshots

Thanks! This is a good idea. I'll try to find someone with access to the repository secrets (I don't either... maybe @miya0001 ?) I'll have to check about whose (what?) Mapbox account we should use to create the Mapbox key as well...

@yuiseki I've added the mapbox token as secrets.MAPBOX_ACCESS_TOKEN

Currently I change the status of this pull request to draft because fix and check mapbox secret.
I will soon re-request review, please wait!

[x] I've merge current main branch into this branch
[x] I've made changes to use secrets.MAPBOX_ACCESS_TOKEN . Thanks @keichan34 !
[x] I've made change to use actions/cache in GitHub Action for speed up this test
[x] Finally, The test that had been added by this pull request have passed
[x] I've updated the description of this pull request

This pull request is ready for review 🙏


Don't use the heap for small BitArrays

The layout of a BitArray is:
struct BitArray
  @size : Int32
  @bits : UInt32*
end

BitArray always allocates storage on the heap to store the bits. This PR optimizes this by using the address of @bits itself for storage if the bits fit into a pointer, usually 64 bits; in this case, @size is negative (but #size is still non-negative). This simplifies some operations on small BitArrays, most notably #== and #dup.

This is incorrect, BitArray has class semantics so there must be a pointer somewhere.


User Authentication

Use Case
User authenticates through email in order to send campaign later (limit spam).  Store their information into a database on airtable to be indexed for each campaign letter

Background info

passport-google-oauth

Implementation

[x] vue + express + node set up @BeeXiong
[x] creating crm in airtable @manishapriya94
[ ] setting up airtable as a database
[ ] passport authentication

Wanted to address setting airtable as a database? @BeeXiong

Should we go for mongodb (would work with Passport)
Should we go for serverless for Fire Torch (Firebase)

How does this affect the cross referencing for user with voter registration in the future?
How does this affect the cross referencing for campaigns/letters sent in distribute airtable

There are 2 versions of how we can authenticate users @ankitagrawal98

Passport with MongoDB
Firebase + Vue Serverless

For reference: will have to install this into npm

I think this depends on where we want the work done.
If people feel comfortable with Vue then we can go firebase.

More code on the front end so we need to be comfortable with Vue syntax.

If we want to keep the work on the back end we go Passport + Mongo

Probably got more people familiar with express/node.js

Some thoughts on the other questions...

How does this affect the cross referencing for user with voter registration in the future?

Looked like it was pretty easy to associate data to user ID's in Firebase and would probably be the same for Mongo. Solves ❓ below ⏫

How does this affect the cross referencing for campaigns/letters sent in distribute airtable

I think we need to standardize on something so we can set up that relational aspect. I'm thinking it will be a nightmare to have to go between two data sources.

I think I'd prefer Firebase Authentication + Cloud Firestore (DB) together is nice 👍 but it does impact your workflow with airtable too @manishapriya94
Thoughts???

Hi @manishapriya94
Sorry for the super late reply 😅
If the plan is to keep the project in Heroku, I would recommend a Postgres/MySQL DB. In my experience, MongoDB has been huge pain to setup in Heroku. Also, I believe the Heroku add-on costs extra $$$.
I've never used Firebase, but it seems pretty cool. I'm a fan of passport. I use it pretty regularly and the setup is usually pretty simple.

I'd recommend going with the boring postgres or mysql approach also. It doesn't scale as nicely as firebase. But, you'd be very successful if you got to that point of it ever being a problem.
Being relational would be the big win. Easier to associate data with other data.


[Missing SNMP Profile]-Broadforward-BFX-DRA

Device Vendor: Broadforward
Device Model: BFX-DRA
System Object Identifier (SysOID): .<IP_ADDRESS>.4.1.39216.
List of critical metrics that you expect in the profile (does not need to be all-inclusive, just a general idea of your expectations): Basically the counters and the Status.
   ( dmtrPeerAdminStatus, dmtrPeerDiameterId, dmtrPeerConnectionStatus,
    dmtrPeerTransportStatus,
   dmtrPeerRealm,
     dmtrPeerProductName,
    dmtrPeerRxCount, dmtrPeerTxCount,
    dmtrPeerLastOOS, dmtrPeerOOSDuration, dmtrPeerOOSCount,
    dmtrPeerTransLastOOS, dmtrPeerTransOOSDuration, dmtrPeerTransOOSCount,
    dmtrPeerSendQueueSize, dmtrPeerSendQueueSizeMax,
    dmtrPeerTxFailedCount, dmtrPeerTimeoutCount,
   dmtrPeerRxResult2xxxCount,
  dmtrPeerRxResult4xxxCount,
    dmtrPeerRxResult5xxxCount,
    dmtrPeerRxBytesCount, dmtrPeerTxBytesCount,

dmtrPeerSctpRxSacks, dmtrPeerSctpTxSacks,
dmtrPeerSctpRxDups, dmtrPeerSctpRxGapAcks,dmtrSctpAddrState)
and some more.
Please provide a public gist with a sanitized (sensitive information removed) SNMP walk of the device. Providing MIB files is not a substitute for an SNMP walk and failure to provide one here will result in delays for closing this issue. The output of these commands shows the "true story" of what a device will respond to in SNMP and is used to ensure that our profiles are efficient and accurate for your devices.
Gist Link: https://gist.github.com/Gopinathind/a56c5492f5dcc5a534d6aa638e8a9938

Example SNMP walk commands: added them in the above gist link
snmpwalk added to the Gist Link above

thanks for the request @Gopinathind; can you please update your gist to include an SNMP walk formatted as requested in the issue template? the command you used is missing the formatting flags:
snmpwalk -v 2c -On -c $COMMUNITY $IP_ADDRESS . >> snmpwalk.out

Specifically, the -On flags provide a numerical OID output that makes parsing the results exponentially easier for us.
e.g.; right now your results look like this:
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10

we need them to look like this:
.<IP_ADDRESS>.<IP_ADDRESS>.0 = OID: .<IP_ADDRESS>.4.1.8<IP_ADDRESS>

Hey @thezackm thank for your quick comment, I have added the snmpwalk.out in the gist with the OID as requested.

Hi guys, when can I expect this to be updated?
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Zack Mutchler @.>
Sent: Wednesday, January 26, 2022 7:34:37 PM
To: kentik/snmp-profiles @.>
Cc: Gopinath Ravichandran @.>; Mention @.>
Subject: Re: [kentik/snmp-profiles] [Missing SNMP Profile]-Broadforward-BFX-DRA (Issue #138)
CAUTION: This email originated from outside Lebara. Do not click links or open attachments unless you recognize the sender and know the content is safe. Please verify sender name and email address before you respond.
thanks for the request @Gopinathindhttps://github.com/Gopinathind; can you please update your gist to include an SNMP walk formatted as requested in the issue template? the command you used is missing the formatting flags:
snmpwalk -v 2c -On -c $COMMUNITY $IP_ADDRESS . >> snmpwalk.out
Specifically, the -On flags provide a numerical OID output that makes parsing the results exponentially easier for us.
e.g.; right now your results look like this:
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
we need them to look like this:
.<IP_ADDRESS>.<IP_ADDRESS>.0 = OID: .<IP_ADDRESS>.4.1.8<IP_ADDRESS>
—
Reply to this email directly, view it on GitHubhttps://github.com/kentik/snmp-profiles/issues/138#issuecomment-1022227252, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXPD2JJ5JSD7OLY4CDB4KS3UX75PLANCNFSM5M2L3J7A.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
This email is confidential and may be subject to privilege. If you are not the intended recipient, please do not copy or disclose its content but contact the sender immediately upon receipt.

@Gopinathind
Given that this is a pretty uncommon piece of kit it's going to take a bit to get this profile figured out and processed, I'd expect it's about a week out with various obligations Zack and I have in the pipe right now.
A question for you, what do you call this thing so I know what kind of name to given the profile?

Hi @Mesverrum , Thanks for turning out with a time, the profile is for DRA- "Diameter Routing Agent"

#157 should get you going.
There are some extra steps you'll have to do for this.
A new container image should be ready shortly with this profile built into it so pull that image down.
You should already have your snmp-base.yaml file with the list of all your devices, because this device just came back as a generic Linux host there wasn't anything to key in on to automatically associate this profile to your devices.  So you will need to edit the devices section of your snmp-base.yaml file and for each of these you would need to edit the line where it says
mib_profile: net-snmp.yml
to
mib_profile: "!diameter.yml"
This forces it to ignore the build in matching and just use the profile you specify.  This step should be repeated for each DRA device.
Then search for mibs_enabled under the global section and you need to add this to the list
- MF-DIAMETER-MIB
At that point you can remove your container, fire up a new one and you should start getting this data back.  Let us know if you run into any issues.

Thanks a lot @Mesverrum ,
Let me do the steps which you have advice and feedback here.


DIG app amd myDIG don't work on Firefox or Safari

The browser shows a blank screen after login, in both the DIG UI and myDIG

Thomas fixed the DIG app. For myDIG, this issue depends on #25

Closing, won't fix for the current version, waiting for the new GUI


Allow context propagator to be set on LocalActivityOptions

Expected Behavior
Users should be able to add custom ContextPropagators to LocalActivityOptions just like ActivityOptions.
Actual Behavior
LocalActivityOptions does not have a list of context propagators and users are unable to add custom ContextPropagators.
Steps to Reproduce the Problem

Create a LocalActivityOption using builder
Implement a ContextPropagator.
Try to set the new ContextPropagator to LocalActivityOption.

Specifications

Version: 1.0.9
Platform: sdk-java

It's a duplicate of https://github.com/temporalio/sdk-java/issues/490
Please see a resolution here describing why we decided that it's not something we want to implement. Please use WorkerOptions#contextPropagators instead.


HOCS-1581 : required by date for M-Ref cases

Set different M-Ref deadline for whole Case lifetime, not per stage.
New endpoint to set deadline using different SLA (in days).
Calculation for Stage deadline includes Case deadline date for defaulting.
Merge to UKVI2.

changes look fine but the build failed:(


fix: solve the problem  of results double calculated.

Results have been summed in _calculate()

@cr0hn Please help to review


[fix] ReadAttribute should put UTF8String type for Char String attributes

Problem

Fixes #8096

Change overview

Put UTF8String (by PutString) when encoding TLV data for ReadAttribute
Includes "Data buffer to numeric types convert" in #7937

Testing

Added CHAR_STRING attribute in TestCluster

@bzbarsky-apple @vivien-apple PTAL.

I think I have fixed the same issue with #8134 that has been cherry-picked already. And I did something very similar to the rest of your patch with https://github.com/project-chip/connectedhomeip/pull/8167
I should have checked more properly the PR list :(

@erjiaqing Please rebase on ToT so it's clearer what the actual changes being made here (after #8134, and ideally after #8167, which is just waiting on CI to merge) are?

@erjiaqing Please rebase on ToT so it's clearer what the actual changes being made here (after #8134, and ideally after #8167, which is just waiting on CI to merge) are?

Seems this PR is already covered by #8167, close now.


A new era of Web-Components

A new monorepo architecture with several component libraries. ui-components now uses sass/scss for styles instead of .styl as well as updated blueprintjs.

Probably yes, it looks like the form-components and data-components both
have package-lock files that didnt get sequester in a .gitignore.
On Tue, 5 Jul 2022, 1:18 PM Daven Quinn, @.***> wrote:

Which file(s) in this PR are causing the length to be 500k lines? Is it
just lock files of various types?
—
Reply to this email directly, view it on GitHub
https://github.com/UW-Macrostrat/web-components/pull/9#issuecomment-1175356619,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APTCHI4ZH2DWJHW25GQQWEDVSR4A7ANCNFSM52XBFM6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

There are also some very long JSON files in the data/macrostrat directory. Maybe of the "1" liners are a single data value. I loaded one on the diff viewer and it was around 4,000 lines. I'm guessing that the data files are taking up the most room.

The all-columns.topo.json file is 197,000 lines alone.

That data is generated and should probably just be omitted from the repo, or minified/gzipped.
Daven
On Jul 5, 2022, 4:44 PM -0500, Casey Idzikowski @.***>, wrote:

The all-columns.topo.json file is 197,000 lines alone.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


--show-hidden-metrics-for-version flag missing from documentation

This is a Bug Report

Problem:
@RainbowMango reported:

v1.17 has been released and seems no update about the new-added flag.
https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/

Proposed Solution:
Identify issue with generated content.
Amend generated content with update pull request?
Page to Update:
https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/
Additional Information:
My guess is that other new features are also missing from the generated documentation. I saw hints of that when reviewing pull requests for the v1.17 release.
/priority important-soon

@sftim, can this page keep this same as kube-apiserver -h.I think it's hard to maintain this by the current form.Is there any suggertion for this?

@lojies I'm not sure what you're saying here.
If you're saying that the current process for incorporating generated reference documentation is a hard to use, I agree.

The reference docs are not generated correctly. I suspect that the generator didn't update the MINOR_VERSION in the Makefile before running make comp.

/kind bug

Currently, the Makefile requires updating as part of the generation process. This has always been the case and is probably documented.
One way to address that issue would be to update the Makefile after the getting the reference repo. Could simply add a sed call to the generate-command and modify the Makefile.

/close

The flag is on board now.


Research Spike: Smoke Test using RPC

AC

[ ] The RPC Client Library epic and associated issues are filled out with tasks that describe in detail smoke testing Forest using RPC
[ ] There is a clearly defined scope & acceptance criteria for the RPC Client Library epic

Some notes / thoughts...

Separate test suites for mainnet read-only tests (interop, validation)
vs. read-write local dev net tests (mining, posting storage contracts, and other operations that contribute to the blockchain)

This will expand on the work done on #1118

Should this be in the form of a script? or more of a "health check" command

A bash script is fine too


Bug - Server crashes while pregenerating

While pregenerating the server keeps crashing randomly. From what I've seen it's always the watchdog.
Crashlog: https://hastebin.com/uhojamuyex.pl
Log: https://hastebin.com/lipozivufo.md

Links don't work anymore unfortunately, hope this has been fixed already for v7.


Update subkey page

Closes https://github.com/substrate-developer-hub/substrate-developer-hub.github.io/issues/171
Update includes:

Dependencies
Description of --network
More password and inspect examples
More HD key derivation explanation and examples
Message signing and verification

We need to duplicate this page for the versioning stuff


Safari JOSM remote control

The current mechanism for JOSM remote control does not work in a Safari browser with the standard security settings.
An attempt to use the remote control function results in following error message:
[Warning] [blocked] The page at https://knooppuntnet.nl/en/monitor/groups/fr-nwn/routes/GR9/map
  was not allowed to display insecure content from
  http://localhost:8111/zoom?left=5.71663525&right=5.74048406&top=43.3849624&bottom=43.37447519

Thanks to @pyrog for reporting this problem (telegram).

A test shows JOSM remote control can be made to work in the Safari browser by opening the JOSM links in a separate browser tab.
Although remote control works this way, there is no way for the knooppuntnet application to know whether JOSM has accepted the command, or even whether JOSM has been started and has remote control enabled.  There is some feedback in the second browser tab where the "OK" response from JOSM is displayed.
Tests have been done to verify whether some feedback can be obtained by opening the link in an iframe, but this did not work.
Given the lack of feedback, the only thing knooppuntnet can do is to wait for a bit between separate commands (for example 1 second), and hope for the best. In practice this may actually be good enough.

OSMCha manage "correctly" JOSM remote control under Safari.
It open the remote control in a new tab (cf. source code)

Todo

[ ] JOSM remote control in Monitor map

[ ] OSM remote control in Route details (ID and nodes column)


Shuttle consoles are fragile

They can also softlock if destroyed

Fixed by simply just making them spawn the board on destruction


payload's content-type cannot be set

when I try to send raw payload and select json type, it sends the request as "text/plain;charset=UTF-8".

What version of Postman are you using?
Selecting JSON from the list just sets the Content-Type header to "application/json". If the header is modified after that, it's not reset to application/json.

it seems I was using the old version. I upgraded. Thanks.


fix(sec): upgrade org.pac4j:pac4j-oidc to 5.2.0

What happened？
There are 1 security vulnerabilities found in org.pac4j:pac4j-oidc 3.8.3

CVE-2021-44878

What did I do？
Upgrade org.pac4j:pac4j-oidc from 3.8.3 to 5.2.0 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
The specification of the pull request
PR Specification from OSCS
<EMAIL_ADDRESS>

@pen4 it looks like some code changes are required to uprade, since you have another PR open https://github.com/apache/druid/pull/14787 for 5.3 as well, I will close this


init fails when alb module added, missing provider registry.terraform.io/hashicorp/security

Description
terraform init fails due to unavailable provder registry.terraform.io/hashicorp/security when making use of module terraform-aws-modules/alb/aws version 6.6.1
Versions

Terraform: 0.14.4

Provider(s):

 Terraform v0.14.4
+ provider registry.terraform.io/hashicorp/aws v3.63.0
+ provider registry.terraform.io/hashicorp/template v2.2.0

Module:

Terraform v0.14.4
+ provider registry.terraform.io/hashicorp/aws v3.63.0
+ provider registry.terraform.io/hashicorp/template v2.2.0

Reproduction

Have working repository
Add the implementation of this module for the first time in a nested module of my own.
Run terraform init
Verify by commenting out implementation rerunning init

Code Snippet to Reproduce
data "aws_vpc" "selected" {
  id = var.vpc_id
}

data "aws_subnet_ids" "all" {
  vpc_id = data.aws_vpc.selected.id
}

data "security_group" "phoenix" {
  vpc_id = data.aws_vpc.selected.id
  name   = "Phoenix"
}

resource "random_pet" "this" {
  length = 2
}

locals {
  short_type   = substr(var.lb_type, 3)
  short_int    = var.internal == true ? "int" : "ext"
  lb_name      = join("-", [var.environment_name, var.service, local.short_type, local.short_int, random_pet.this.id])
}

module "alb" {
  source  = "terraform-aws-modules/alb/aws"
  version = "6.6.1"

  name = local.lb_name

  load_balancer_type = var.lb_type

  vpc_id          = data.aws_vpc.selected
  subnets         = data.aws_subnet_ids.all.ids
  security_groups = [data.security_group.phoenix.id]

  target_groups = [
    {
      name_prefix      = var.environment_name
      backend_protocol = "HTTP"
      backend_port     = 80
      target_type      = "instance"
      health_check = {
        enabled             = true
        path                = var.heatlh_check_path
        port                = var.heatlh_check_port
        healthy_threshold   = 2
        unhealthy_threshold = 2
        timeout             = 5
        interval            = 6
        protocol            = "HTTP"
        matcher             = "200"
      }
    }
  ]

  http_tcp_listeners = [
    {
      port               = 80
      protocol           = "HTTP"
      action_type        = "forward"
      target_group_index = 0
    }
  ]

  https_listeners = var.internal == true ? [] : [
    {
      port               = 443
      protocol           = "HTTPS"
      action_type        = "forward"
      certificate_arn    = var.acm_certificate_arn
      target_group_index = 0
    }
  ]

  tags = {
    Environment = var.environment_name
  }
}

Expected behavior
terraform init will complete successfully with all relevant modules and providers downloaded
Actual behavior
terraforom init fails with this error
Error: Failed to query available provider packages

Could not retrieve the list of available versions for provider
hashicorp/security: provider registry registry.terraform.io does not have a
provider named registry.terraform.io/hashicorp/security

If you have just upgraded directly from Terraform v0.12 to Terraform v0.14
then please upgrade to Terraform v0.13 first and follow the upgrade guide for
that release, which might help you address this problem.

Terminal Output Screenshot(s)
$ terraform init
Initializing modules...

Initializing the backend...

Initializing provider plugins...
- terraform.io/builtin/terraform is built in to Terraform
- Finding latest version of hashicorp/security...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of hashicorp/template from the dependency lock file
- Finding latest version of hashicorp/random...
- Installing hashicorp/aws v3.63.0...
- Installed hashicorp/aws v3.63.0 (self-signed, key ID 34365D9472D7468F)
- Installing hashicorp/template v2.2.0...
- Installed hashicorp/template v2.2.0 (self-signed, key ID 34365D9472D7468F)
- Installing hashicorp/random v3.1.0...
- Installed hashicorp/random v3.1.0 (self-signed, key ID 34365D9472D7468F)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/plugins/signing.html

Error: Failed to query available provider packages

Could not retrieve the list of available versions for provider
hashicorp/security: provider registry registry.terraform.io does not have a
provider named registry.terraform.io/hashicorp/security

If you have just upgraded directly from Terraform v0.12 to Terraform v0.14
then please upgrade to Terraform v0.13 first and follow the upgrade guide for
that release, which might help you address this problem.

data "security_group" is wrong. It should be data "aws_security_group".


Support S3 URI as Live.dir to store DVCLive data in cloud storage

I am using Ray Jobs to execute training on EC2 worker nodes forming an auto-scaling Ray Cluster. I would like to save DVCLive output in a persistent remote storage location (AWS S3). If the Ray Job would use dvc exp run, the output can be saved at the end of training to the Git repo via dvc exp push. But if a failure would occur or training is interrupted, the output up to that point would only be on the worker node which will get terminated.
Further, in my setup, I am not actually running dvc exp run as the Ray Job command. Instead, I am running dvc exp run --queue && dvc queue start (using CLI or VS Code Extension) on my local machine. The DVC queue task is a custom script which submits the training job and sync's the intermediate outputs from remote storage in S3 to the local machine at regular intervals until the job is in a terminal state. The advantage of doing this is that I can use local dvc exp commands as if the training tasks would be running locally, e.g., to follow progress, compare live plots, etc. My custom script thus takes care of the download of the training job output from S3 to the local machine. PyTorch Lightning TensorBoard logs can be written directly to S3 as supported by lightning.pytorch.loggers.tensorboard.TensorBoardLogger where save_dir can be a URI, and Ray Tune / Train state is uploaded by Ray by specifying a storage_path URI.
With Ray Train <2.5, I was using RunConfig(local_dir=...) along side SyncConfig(upload_dir=...) to have Ray upload the DVCLive output located in local_dir from the local directory to the remote storage. This is now deprecated since Ray 2.5. When the job is running on the Ray cluster head node, the dvclive output folder is still synced correctly, but when run on worker nodes it is not (even though it exists on the local EC2 instance drive which I checked).
I could likely fix this by adjusting my Ray Train script to either save the DVCLive output to a folder inside the Ray session.get_trial_dir() or taking care of the upload of DVCLive output myself.
However, ideally, DVCLive itself (or at least the dvclive.lightning.DVCLiveLogger) would support URIs (S3 in my case) as an output dir for logged data, just as the TensorBoardLogger of PyTorch Lightning supports (thanks to URI support of torch.utils.tensorboard.SummaryWriter).
pl.Trainer(
  logger=DVCLiveLogger(dir="s3://bucket/prefix/dvclive", save_dvc_exp=False, dvcyaml=False),
  ...
)

I worked arounds this with a small DVCLiveLogger wrapper.
from deepali.core.storage import StorageObject

from dvclive.lightning import DVCLiveLogger as _DVCLiveLogger
from dvclive.lightning import ModelCheckpoint, rank_zero_only

class DVCLiveLogger(_DVCLiveLogger):
    def __init__(self, dir: str, **kwargs) -> None:
        storage = StorageObject.from_path(dir)
        super().__init__(dir=str(storage.path), **kwargs)
        self.storage = storage

    def after_save_checkpoint(self, checkpoint_callback: ModelCheckpoint) -> None:
        super().after_save_checkpoint(checkpoint_callback)
        self.storage.push(force=True)

    @rank_zero_only
    def finalize(self, status: str) -> None:
        super().finalize(status)
        self.storage.push(force=True)

Note that I'm using a little helper from my own open source lib here for syncing a local temp folder with S3. You could probably use PyTorch Lightnings fsspec abstractions instead rather.

@aschuh-hf I thought there was a GH issue for this already, but I can't seem to find it. Do you plan to change the path for each experiment you run?

Yes, in this case, where experiments are executed as batch jobs potentially in a cluster environment such as Ray with results stored in cloud storage such as S3 I have to use a separate output path for each experiment.
My train stage script uses a timestamp and DVC_EXP_NAME and DVC_EXP_BASELINE_REV environment variables to derive an experiment run suffix for output URIs (Ray Train storage, DVCLive output dir and/or TensorBoard log dir).
version="$(date -u +%Y-%m-%d)-${DVC_EXP_BASELINE_REV:0:8}-${DVC_EXP_NAME}"

s3_dvc_dir="s3://${s3_bucket}/${s3_prefix}dvc/${version}/"
s3_log_dir="s3://${s3_bucket}/${s3_prefix}logs/${version}/"
s3_out_dir="s3://${s3_bucket}/${s3_prefix}state/"  # excl. version subdir because Ray Train appends it

Nice @aschuh-hf! I was looking a bit into #237, and this looks like the same idea that's needed there. It's also related to the discussion in #638. It would be great to converge on a smoother experience here that doesn't require adding a helper to sync to and from cloud storage to track jobs run on ray or in other remote/distributed compute scenarios.

An integration with Ray Tune (and Ray Train) sounds fantastic.
When using Ray Tune, I currently disable DVCLive because Tune already provides me with an experiment analysis object which basically let's me compare trials, e.g., as Pandas dataframe. But it would indeed be better and more convenient if those trial results would be nicely integrated with individual DVC experiment runs instead (across dvc exp CLI output, VS Code tables, and DVC Studio).
The reason I chose not to write the DVCLive to the trial working directory, and thus having to upload the artifacts to remote storage manually in the DVCLiveLogger is that the trial folder names are more cryptic and I would need to use Ray to parse the experiment JSON files to figure out under which S3 prefix the results are stored, even though with Ray Train I only have one trial folder. Choosing my own upload path made it easier to download the data using aws s3 sync in my local script in order to place it where DVC expects to find it (i.e., the metrics, plots, and outs paths configured in dvc.yaml).

doesn't require adding a helper to sync to and from cloud storage

Not having to use my own helper would be great!
Another aspect is the handling of AWS credentials in this case for long running training jobs. I haven't looked into how to enable the script itself to update credentials before they expire (so if DVC can handle that for me even better), but basically I need the local train stage script to wait until I manually update those (we are using okta-awscli) before it can get the latest results from cloud storage. Especially when the Ray train job finished, the script still needs to wait until it can get the final results before exiting such that DVC can create a final experiment commit rev.
A smoother integration may be to execute dvc exp run as Ray job command instead and save final results with dvc exp push. That way one doesn't need to worry about cloud storage credentials and having a long running helper script on the local machine. The DVC CLI tools (dvc exp show) and VS Code Extension could possibly also get the state of a running experiment from cloud storage directly to display the data of a not yet finished run alongside other experiments. That would sound like a nicer solution than my work-around (though I find having those long running helper scripts run by as DVC queue tasks on my always on workstation works quite well).
In case of DVC Studio, I imagine the train job would directly submit the data to the running Studio server. It's just that DVC CLI and VS Code Extension have to actively obtain this data differently I suppose.
Since I first set this up, we also changed our Ray cluster IAM roles to allow me access to the GitHub repository. Do you think it would be feasible / good to exchange data with DVC CLI / VS Code Extension via the GitHub repository? I'm just not sure whether it would be good to push so many intermediate experiment results as commits to the remote repository (unless this is actually not an issue at all, or the previous commit would be replaced; in the end leaving just one "latest" experiment commit for each run).

Sorry for the long delay here @aschuh-hf! We are still thinking about this one but got caught up with other priorities.

When using Ray Tune, I currently disable DVCLive because Tune already provides me with an experiment analysis object which basically let's me compare trials, e.g., as Pandas dataframe. But it would indeed be better and more convenient if those trial results would be nicely integrated with individual DVC experiment runs instead (across dvc exp CLI output, VS Code tables, and DVC Studio).

Makes sense. I think it may be better for us to start with Ray Train here since it's simpler than managing results from many experiments at once.
Have you considered using EFS to share the repo across the cluster so you can actually write dvclive output there?
Otherwise, I think it should be possible to support s3 paths in dvclive, and we could document how to have your stage download those to the repo when training finishes. It doesn't feel like the cleanest solution to me but it could at least unblock you.
We could also provide realtime updates via Studio. Not sure if that interests you but could be helpful for the general public to not have to write a helper to intermittently download results.
cc @mnrozhkov


Create KeyStore

http://docs.oracle.com/javase/7/docs/api/java/security/KeyStore.html

"You can no longer get the private key in raw form by design. The PrivateKeys returned by the KeyChain delegate their operations back to the keystore. From native code the supported API is use JNI to make calls using PrivateKeys using return by the KeyChain API. I believe chromium has some code showing how to do this, I believe they use an OpenSSL engine that delegates back to Java."
https://groups.google.com/forum/#!topic/android-security-discuss/OVnB9pVIE5s


[$1000] Desktop -  User locked out, can't use the app at all

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.3.83-11
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @marcaaron
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1697230242487469
Action Performed:

Downloaded the desktop app and sign in
Delete the desktop app
Download the desktop app again
Try to sign in
App freezes and throws a JS error
ReconnectApp appears to be called in a loop many times
Navigate back to sign in page
Locked out because too many magic codes requested (I only attempted to sign in once).

Expected Result:
Just be able to sign in. No weird network stuff seemingly causing many requests for magic codes resulting in getting locked out of the account temporarily.
Actual Result:
Got locked out. Can't use the app at all.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01115e59ed0c307000
Upwork Job ID:<PHONE_NUMBER>877924352
Last Price Increase: 2023-10-26

This feels like it might be external, but I'm not sure. I'll start external, please let me know if we need a backend engineer to help on this one.

@allroundexperts I'd love your thoughts here. Is this something that can be handled by an external contributor or do we need to take it internal?

Okay, thanks! Bumping.

I'm not able to reproduce this? When I re-install the app previously loggedin session stays same? I don't see any issues.

Not able to move forward past step 3.

Is there anything I'm missing? Do I need to logout after re-installing the app? Do I need to reboot my system?
cc: @marcaaron

I tried on staging app.

It's probably not consistently reproducible. But should be documented because it happened.

@marcaaron would you recommend as a next step here? If it's not easily reproduceable, any ideas on how we can fix?

Leave it open and see if anyone else reports it or catches a reproduction. If not then I guess we could assume it's been "fixed". But pretty awful bug IMO.

any ideas on how we can fix

Not without a repro

Issue not reproducible during KI retests. (First week)

Welp, I guess we close for now and assume it's fixed.  Hopefully, if it's not fixed, someone can figure out some consistent reproduction steps 🤷