Left and Right pane disappears

Describe the bug
We connect to cluster and when Lens is about show the cluster object., the left and right appears completely blank and not showing anything
To Reproduce
Steps to reproduce the behavior:

Connect to Cluster
The left and right disappears completely.

Expected behavior
The cluster information should appear
Screenshots

Environment (please complete the following information):

Lens Version: Lens: 5.2.4-latest.20210923.1

OS: MacOS
ProductName:	Mac OS X
ProductVersion:	10.15.7
BuildVersion:	19H1417

Installation method (e.g. snap or AppImage in Linux):
Apple dmg file

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
info:    ▪ 📟 Setting Lens as protocol client for lens:// +0ms
info:    ▪ 📟 Protocol client register succeeded ✅ +3ms
info:    ▪ 🚀 Starting Lens from "/Applications/Lens.app/Contents/MacOS/Lens" +103ms
info:    ▪ 🐚 Syncing shell environment +1ms
info:    ▪ 💾 Loading stores +2s
info:    ▪ [BS]: LOADED from /Users/miali/Library/Application Support/Lens/lens-user-store.json +39ms
info:    ▪ [DA]: LOADED from /Users/miali/Library/Application Support/Lens/lens-cluster-store.json +44ms
info:    ▪ [NU]: LOADED from /Users/miali/Library/Application Support/Lens/lens-hotbar-store.json +4ms
info:    ▪ [MT]: LOADED from /Users/miali/Library/Application Support/Lens/lens-extensions.json +2ms
info:    ▪ [C]: LOADED from /Users/miali/Library/Application Support/Lens/lens-filesystem-provisioner-store.json +2ms
info:    ▪ [KA]: LOADED from /Users/miali/Library/Application Support/Lens/lens-weblink-store.json +3ms
info:    ▪ 🔌 Starting LensProxy +10ms
info:    ▪ [LENS-PROXY]: Proxy server has started at <IP_ADDRESS>:59354 +4ms
info:    ▪ 🔎 Testing LensProxy connection ... +1ms
info:    ▪ ⚡ LensProxy connection OK +117ms
info:    ▪ 🖥  Starting WindowManager +4ms
info:    ▪ 🧩 Initializing extensions +59ms
info:    ▪ [EXTENSION-DISCOVERY] loading extensions from /Users/miali/Library/Application Support/Lens +0ms
info:    ▪ [EXTENSION-INSTALLER] installing dependencies at /Users/miali/Library/Application Support/Lens +57ms
info:    ▪ [WINDOW-MANAGER]: Loading Main window from url: http://localhost:59354 ... +181ms
info:    ▪ [EXTENSION-INSTALLER] dependencies installed at /Users/miali/Library/Application Support/Lens +820ms
info:    ▪ [EXTENSION-DISCOVERY] watching extension add/remove in /Users/miali/.k8slens/extensions +6ms
Native extraction module not loaded, msgpackr will still run, but with decreased performance. Cannot find module 'msgpackr-extract'
Lens Cloud Extension activated
info:    ▪ [C]: LOADED from /Users/miali/Library/Application Support/Lens/extension-store/lenscloud-lens-extension/auth-token-store.json +68ms
info:    ▪ [C]: LOADED from /Users/miali/Library/Application Support/Lens/extension-store/lens-survey/preferences-store.json +4ms
telemetry main extension activated
info:    ▪ [N]: LOADED from /Users/miali/Library/Application Support/Lens/extension-store/lens-telemetry/preferences-store.json +48ms
[@mirantis/lens-extension-cc/ExtensionMain.onActivate()] extension activated
info:    ▪ [PREFERENCE-STORE]: LOADED from /Users/miali/Library/Application<EMAIL_ADDRESS>+40ms
info:    ▪ [CLUSTER-STORE]: LOADED from /Users/miali/Library/Application<EMAIL_ADDRESS>+2ms
[@mirantis/lens-extension-cc/IpcMain.restoreClusters()] Restored 0 clusters from clusterStore into catalog, clusters=[]
info:    ┏ [IPC-RENDERER]: adding extension handler +1ms
info:    ┗ [1] { channel: 'addClusters', extension: { name: '@mirantis/lens-extension-cc', version: '3.0.3' } }
info:    ┏ [IPC-RENDERER]: adding extension handler +2ms
info:    ┗ [1] { channel: 'removeCluster', extension: { name: '@mirantis/lens-extension-cc', version: '3.0.3' } }
info:    ┏ [IPC-RENDERER]: adding extension handler +0ms
info:    ┗ [1] { channel: 'deleteCluster', extension: { name: '@mirantis/lens-extension-cc', version: '3.0.3' } }
info:    ▪ [STORE]: SAVING /Users/miali/Library/Application Support/Lens/lens-extensions.json +6ms
info:    ┏ [IPC-RENDERER]: adding extension listener +109ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'deleteOneCluster',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.2.4-latest.20210923.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'loadRemoteSpacesClusters',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.2.4-latest.20210923.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'createOneSpace',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.2.4-latest.20210923.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'leaveOneSpace',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.2.4-latest.20210923.1' }
info:    ┗ [4] }
info:    ▪ [EXTENSION]: enabled<EMAIL_ADDRESS>+69ms
info:    ▪ [EXTENSION]: enabled<EMAIL_ADDRESS>+4ms
info:    ▪ [EXTENSION]: enabled<EMAIL_ADDRESS>+0ms
info:    ▪ [EXTENSION]: enabled<EMAIL_ADDRESS>+1ms
[CLUSTER-CONNECT] cluster proxy started on port 59369
[CLUSTER-CONNECT] cluster proxy is using aes-256-gcm for end-to-end encryption
info:    ▪ [EXTENSION]: enabled<EMAIL_ADDRESS>+64ms
info:    ▪ [WINDOW-MANAGER]: Main window loaded +846ms
info:    ▪ [KUBECONFIG-SYNC]: starting requested syncs +500ms
info:    ┏ [KUBECONFIG-SYNC]: starting sync of file/folder +0ms
info:    ┗ [1] { filePath: '/Users/miali/Library/Application Support/Lens/kubeconfigs' }
info:    ┏ [KUBECONFIG-SYNC]: starting sync of file/folder +1ms
info:    ┗ [1] { filePath: '/Users/miali/.kube' }
info:    ▪ 📡 Checking for app updates +1ms
info:    ▪ Checking for update +0ms
info:    ▪ [KUBECONFIG-SYNC]: ignoring '/Users/miali/.kube/config.eksctl.lock' due to ignore glob: *.lock +8ms
info:    ▪ [WINDOW-MANAGER]: Main window has reported that it has loaded +41ms
info:    ▪ [WINDOW-MANAGER]: Attaching webview +554ms
info:    ▪ Update for version 5.2.4-latest.20210923.1 is not available (latest version: 5.2.4-latest.20210923.1, downgrade is disallowed). +155ms
info:    ┏ [CLUSTER]: activate +4s
info:    ┃ [1] {
info:    ┃ [2]   id: '1a21faf5e741741bc09102d60a087562',
info:    ┃ [3]   name<EMAIL_ADDRESS>info:    ┃ [4]   ready: false,
info:    ┃ [5]   online: false,
info:    ┃ [6]   accessible: false,
info:    ┃ [7]   disconnected: true
info:    ┗ [8] }
info:    ┏ [CLUSTER]: bind events +1ms
info:    ┃ [1] {
info:    ┃ [2]   id: '1a21faf5e741741bc09102d60a087562',
info:    ┃ [3]   name<EMAIL_ADDRESS>info:    ┃ [4]   ready: false,
info:    ┃ [5]   online: false,
info:    ┃ [6]   accessible: false,
info:    ┃ [7]   disconnected: true
info:    ┗ [8] }
info:    ┏ [CLUSTER]: reconnect +0ms
info:    ┃ [1] {
info:    ┃ [2]   id: '1a21faf5e741741bc09102d60a087562',
info:    ┃ [3]   name<EMAIL_ADDRESS>info:    ┃ [4]   ready: false,
info:    ┃ [5]   online: false,
info:    ┃ [6]   accessible: false,
info:    ┃ [7]   disconnected: true
info:    ┗ [8] }
info:    ┏ [KUBE-AUTH]: out-channel "kube-auth:1a21faf5e741741bc09102d60a087562" +843ms
info:    ┃ [ 1] {
info:    ┃ [ 2]   data: 'Authentication proxy started\n',
info:    ┃ [ 3]   meta: {
info:    ┃ [ 4]     id: '1a21faf5e741741bc09102d60a087562',
info:    ┃ [ 5]     name<EMAIL_ADDRESS>info:    ┃ [ 6]     ready: false,
info:    ┃ [ 7]     online: false,
info:    ┃ [ 8]     accessible: false,
info:    ┃ [ 9]     disconnected: true
info:    ┃ [10]   }
info:    ┗ [11] }

Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: <<Secret Data>>
    server: <<URL>>
contexts:
- context:
    cluster: capi.us-east-1.eksctl.io
    user: <<USER>>
  name<EMAIL_ADDRESS>current-context<EMAIL_ADDRESS>kind: Config
preferences: {}
users:
- name<EMAIL_ADDRESS>  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - token
      - -i
      - capi
      command: aws-iam-authenticator
      env:
      - name: AWS_STS_REGIONAL_ENDPOINTS
        value: regional
      - name: AWS_DEFAULT_REGION
        value: us-east-1

Same here...

If you disconnect and reconnect, or go back to the catalog and then back to the cluster does the issue persist?
@tahirali-endurance Is there ever any more logs after the [KUBE-AUTH]: out-channel "kube-auth:1a21faf5e741741bc09102d60a087562" +843ms line?

Well, neither disconnect, reconnect or going back and forth resolved the issue. That's what I see:
info:    ┏ [KUBE-AUTH]: out-channel "kube-auth:1a21faf5e741741bc09102d60a087562" +2s
info:    ┃ [ 1] {
info:    ┃ [ 2]   data: 'Authentication proxy started\n',
info:    ┃ [ 3]   meta: {
info:    ┃ [ 4]     id: '1a21faf5e741741bc09102d60a087562',
info:    ┃ [ 5]     name<EMAIL_ADDRESS>info:    ┃ [ 6]     ready: false,
info:    ┃ [ 7]     online: false,
info:    ┃ [ 8]     accessible: false,
info:    ┃ [ 9]     disconnected: true
info:    ┃ [10]   }
info:    ┗ [11] }
info:    ┏ [CLUSTER]: refresh +28s
info:    ┃ [1] {
info:    ┃ [2]   id: '1a21faf5e741741bc09102d60a087562',
info:    ┃ [3]   name<EMAIL_ADDRESS>info:    ┃ [4]   ready: true,
info:    ┃ [5]   online: true,
info:    ┃ [6]   accessible: true,
info:    ┃ [7]   disconnected: false
info:    ┗ [8] }
info:    ┏ [CLUSTER]: refresh +30s
info:    ┃ [1] {
info:    ┃ [2]   id: '1a21faf5e741741bc09102d60a087562',
info:    ┃ [3]   name<EMAIL_ADDRESS>info:    ┃ [4]   ready: true,
info:    ┃ [5]   online: true,
info:    ┃ [6]   accessible: true,
info:    ┃ [7]   disconnected: false
info:    ┗ [8] }
info:    ┏ [CLUSTER]: refresh +30s
info:    ┃ [1] {
info:    ┃ [2]   id: '1a21faf5e741741bc09102d60a087562',
info:    ┃ [3]   name<EMAIL_ADDRESS>info:    ┃ [4]   ready: true,
info:    ┃ [5]   online: true,
info:    ┃ [6]   accessible: true,
info:    ┃ [7]   disconnected: false
info:    ┗ [8] }
info:    ┏ [CLUSTER]: refresh +30s
info:    ┃ [1] {
info:    ┃ [2]   id: '1a21faf5e741741bc09102d60a087562',
info:    ┃ [3]   name<EMAIL_ADDRESS>info:    ┃ [4]   ready: true,
info:    ┃ [5]   online: true,
info:    ┃ [6]   accessible: true,
info:    ┃ [7]   disconnected: false
info:    ┗ [8] }

I have the same issue. Deleting the cluster from kubeconfig and readding solved it for a few hours, but now it is the same and can't do anything to fix it. I have 3 clusters and the problem persists with only 1 of them

I need to renderer logs, if you open up devtools would you be able to paste the logs from its console?

I think this is a duplicate of https://github.com/lensapp/lens/issues/3829 so I am going to close this, please add some logs to that issue.

This above issues relates to Windows and I am still facing the issue. These are the logs
[USER-STORE-USER-STORE]: LOADED from /Users/miali/Library/Application Support/Lens/lens-user-store.json
instrument.js:109 [CLUSTER-STORE-CLUSTER-STORE]: LOADED from /Users/miali/Library/Application Support/Lens/lens-cluster-store.json
instrument.js:109 [CLUSTER-STORE] requesting initial state sync
instrument.js:109 [HOTBAR-STORE-HOTBAR-STORE]: LOADED from /Users/miali/Library/Application Support/Lens/lens-hotbar-store.json
instrument.js:109 [EXTENSIONS-STORE-EXTENSIONS-STORE]: LOADED from /Users/miali/Library/Application Support/Lens/lens-extensions.json
instrument.js:109 [EXTENSION-FILESYSTEM-FILESYSTEM-PROVISIONER-STORE]: LOADED from /Users/miali/Library/Application Support/Lens/lens-filesystem-provisioner-store.json
instrument.js:109 [WEBLINK-STORE-WEBLINK-STORE]: LOADED from /Users/miali/Library/Application Support/Lens/lens-weblink-store.json
instrument.js:109 [CLUSTER-STORE] start to listen (1)
instrument.js:109 Download the React DevTools for a better development experience: https://reactjs.org/link/react-devtools
instrument.js:109 Lens Cloud Extension activated
instrument.js:109 [L]: LOADED from /Users/miali/Library/Application Support/Lens/extension-store/lenscloud-lens-extension/auth-token-store.json
instrument.js:109 [D]: LOADED from /Users/miali/Library/Application Support/Lens/extension-store/lens-survey/preferences-store.json
instrument.js:109 telemetry extension activated
instrument.js:109 [N]: LOADED from /Users/miali/Library/Application Support/Lens/extension-store/lens-telemetry/preferences-store.json
instrument.js:109 [@mirantis/lens-extension-cc/ExtensionRenderer.onActivate()] extension activated
instrument.js:109 [PREFERENCE-STORE]: LOADED from /Users/miali/Library/Application<EMAIL_ADDRESS>instrument.js:109 [CLUSTER-STORE]: LOADED from /Users/miali/Library/Application<EMAIL_ADDRESS>instrument.js:109 [IPC-RENDERER]: adding extension listener Object
instrument.js:109 [PROTOCOL ROUTER]: internal registering /preferences
instrument.js:109 [PROTOCOL ROUTER]: internal registering /
instrument.js:109 [PROTOCOL ROUTER]: internal registering /landing
instrument.js:109 [PROTOCOL ROUTER]: internal registering /landing/view/:group/:kind
instrument.js:109 [PROTOCOL ROUTER]: internal registering /cluster
instrument.js:109 [PROTOCOL ROUTER]: internal registering /entity/:entityId/settings
instrument.js:109 [PROTOCOL ROUTER]: internal registering /cluster/:clusterId
instrument.js:109 [PROTOCOL ROUTER]: internal registering /cluster/:clusterId/settings
instrument.js:109 [PROTOCOL ROUTER]: internal registering /extensions
instrument.js:109 [PROTOCOL ROUTER]: internal registering /extensions/install/:LENS_INTERNAL_EXTENSION_PUBLISHER_MATCH(@[A-Za-z0-9_]+)?/:LENS_INTERNAL_EXTENSION_NAME_MATCH
instrument.js:109 [EXTENSION]: enabled<EMAIL_ADDRESS>instrument.js:109 [EXTENSION]: enabled<EMAIL_ADDRESS>instrument.js:109 [EXTENSION]: enabled<EMAIL_ADDRESS>instrument.js:109 [EXTENSION]: enabled<EMAIL_ADDRESS>instrument.js:109 [EXTENSION]: enabled<EMAIL_ADDRESS>instrument.js:109 [EXTENSION]: enabled<EMAIL_ADDRESS>instrument.js:109 [EXTENSION]: enabled<EMAIL_ADDRESS>instrument.js:109 [@mirantis/lens-extension-cc/IpcMain.restoreClusters()] Restored 0 clusters from clusterStore into catalog, clusters=[]
instrument.js:109 Running Auth Callback Server on http://localhost:58961
instrument.js:109 [StorageHelper]: loading finished for /Users/miali/Library/Application Support/Lens/lens-local-storage/app.json
instrument.js:109 Running CORS Anywhere Proxy on http://localhost:58962/
instrument.js:109 Can't access https://k8slens.dev/welcome_banners/welcome_banner_02.html
(anonymous) @ instrument.js:109
instrument.js:109 Can't access https://k8slens.dev/welcome_banners/welcome_banner_01.html
(anonymous) @ instrument.js:109
instrument.js:109 Can't access https://k8slens.dev/welcome_banners/welcome_banner_03.html
(anonymous) @ instrument.js:109
instrument.js:109 Can't access https://k8slens.dev/welcome_banners/welcome_banner_04.html
(anonymous) @ instrument.js:109
instrument.js:109 Can't access https://k8slens.dev/welcome_banners/welcome_banner_05.html
(anonymous) @ instrument.js:109
instrument.js:109 [EXTENSION]: enabled<EMAIL_ADDRESS>instrument.js:109 [StorageHelper]: saving /Users/miali/Library/Application Support/Lens/lens-local-storage/app.json
instrument.js:109 [LENS-VIEW]: refreshing iframe views, visible cluster id=1a21faf5e741741bc09102d60a087562
instrument.js:109 [LENS-VIEW]: init dashboard, clusterId=1a21faf5e741741bc09102d60a087562
instrument.js:109 [LENS-VIEW]: waiting cluster to be ready, clusterId=1a21faf5e741741bc09102d60a087562
instrument.js:109 [LENS-VIEW]: cluster is ready, clusterId=1a21faf5e741741bc09102d60a087562
instrument.js:109 [LENS-VIEW]: loaded from http://1a21faf5e741741bc09102d60a087562.localhost:58930/

@tahirali-endurance do you mean the linked issue? If so then no, it is not just a windows issue. Initial report was from a linux user and macOS users have also commented. The symptoms are basically the same which is why I think it is a duplicate.

I still see the same issue and I think I have updated to latest version.
Lens: 5.2.4-latest.20210923.1
Electron: 12.0.17
Chrome: 89.0.4389.128
Node: 14.16.0
© 2021 Mirantis, Inc.

I've updated Lens to the latest version and right pane seems to be working now...


Inferred type does not conform to upper bound(s)

Hi, when I run test in local, it build failed

Hi, thank you for reporting. What is Java version?


CPython_to_GH.py invoke Rhino 5.0 in a RH6 context

Problem
I'm trying to test the CPython_to_GH.py example with Rhino 6.0.
What happened
I installed ghpythonremote in my conda env (python2.7, activated), and the ironpython configuration seems to be set up properly, with the console telling me the following:
> python -m ghpythonremote._configure_ironpython_installation
The gh-python-remote package will be installed in Rhino IronPython with the command:
C:\Users\harry\.conda\envs\py27\python.exe -m pip install --upgrade --target=C:\Users\harry\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib --no-binary=:all: --no-compile --ignore-requires-python gh-python-remote
...
Successfully installed gh-python-remote-1.2.1 plumbum-1.6.7 rpyc-4.1.1
INFO:Copied example files to C:\Users\harry\AppData\Roaming\Grasshopper\UserObjects\gh-python-remote

Notice that the IronPython of Rhino 6 is correctly identified above.
But if I run python CPython_to_GH.py in the path examples, Rhino 5 will be invoked and the following error shows up:

Well, I did python -m ghpythonremote._configure_ironpython_installation 5 as well. Before I did that, the error was simply "cannot locate module ghpythonremote".
Am I doing anything wrong here? I feel like there should be a parameter in the PythonToGrasshopperRemote class to let it know that we are dealing with RH5 or RH6, if both are installed in the system.

This is some seriously old and dusty code you are looking at here Yijiang :-) I don't think anyone's really used it in the past 2 years. Thanks for trying it!
It looks like there are two things to fix here:

there needs to be a way to select which version of Rhino to run
there is a bug in the example you show, I'm guessing a mismatch in exception handling settings in rpyc between the two interpreters.

I'll try to have a look at it this week


Maintainers and publishing

I know that this is a free, open-source project and I appreciate all the time and effort this has been put into by you and the collaborators. Currently react-static v16 is in beta and there is still errors that I constantly fight with (using react-static in production), some of them already fixed in PRs and while it kinda works, I find myself to work with ugly workarounds like patching react-static files by overwriting them inside the node_modules folder.
Maybe it could help to call for maintainers with publish and PR merge rights? I believe that react-static is a great solution for statical page building and there is people commiting and participating in the development, adding maintainers could help getting to v16 and future updates a lot faster.

I have a day reserved for React Static coming up. I'll put this on my list of things to address. Thanks!

Can I apply for maintainer's role?

Yeah @sw-yx, that would be a great first step. Travis is already set up, so adding an automated publishing pipeline for @canary tag shouldn't be too much of an issue, especially if someone PR'd the travis-ci.yml :)

If someone would like to PR that travis setup then I’d be happy to help
with the publish keys
On Thu, Sep 6, 2018 at 7:48 AM Benjamin Kniffler<EMAIL_ADDRESS>wrote:

Yeah @sw-yx https://github.com/sw-yx, that would be a great first step.
Travis is already set up, so adding an automated publishing pipeline for
@canary https://github.com/canary tag shouldn't be too much of an
issue, especially if someone PR'd the travis-ci.yml :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/731#issuecomment-419099619,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCcXV4xkDfTm1VG-T0MDt_EBsPnEDks5uYSfDgaJpZM4WaykQ
.

Unfortunately, I made a veeeerrrry bad mistake of writing v6 on master. In all reality, master should remain up to date with the stable public release of React Static. This will change next version. I am still figuring out how to cherry pick the commits for v5 into another branch...

Info: master branch now points to 5.x.x and the v6 branch to 6.0.0-beta.

Not to derail thread but curious why you feel was a mistake to develop on master?
Seems like this reduces complexity and can then just cut tagged release branches / public releases from them.. patch these release branches with bug fixes as needed, merge back to master..
https://reallifeprogramming.com/git-process-that-works-say-no-to-gitflow-50bf2038ccf7

Mostly this has to do with a lot of the CI and github experience for users.
If @latest points at 5.x, then I think users expect to be able to see
master reflect the latest stable version. This also keeps the CI in sync
for things like building the website/docs properly for existing users and
keeps issues like we’ve seen in the last few weeks where people are trying
to install plugins that don’t exist yet, or use features in v6 that aren’t
fully complete. Turns out these people had no idea they were using v6,
because they were simply referring to the master branch for docs, examples,
and code.
I know there are ways to develop @next on master and likewise keep older
versions on their own branches (v5), but given the circumstances and
current CI setup, I think it made more sense to do a v6 branch etc.
On Thu, Sep 6, 2018 at 4:04 PM Conor Dockry<EMAIL_ADDRESS>wrote:

Not to derail thread but curious why you feel was a mistake to develop on
master?
Seems like this reduces complexity and can then just cut tagged release
branches / public releases from them.. patch these release branches with
bug fixes as needed, merge back to master..
https://reallifeprogramming.com/git-process-that-works-say-no-to-gitflow-50bf2038ccf7
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/731#issuecomment-419256222,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCZLYuecteP3Qb-oryWnawPlTnfV3ks5uYZvygaJpZM4WaykQ
.

Tanner, if you need help maintaining RS - I could potentially help with some of the smaller issues.
I got some capacity problems at the moment, but then things cool down, I can lend a hand in the maintenance.

All of everyones help here is extremely appreciated. I am 💯 for adding more maintainers and moving forward as long as we can check these boxes off:

[ ] Automate testing and releases based on PR's
[ ] Draft some better maintainer/contributor guidelines
[ ] Find some time to walk each new maintainer through the v6 codebase and vision for the future of the library

I'll also be interested in becoming a maintainer :) time to give something back to react-static

Alright guys. I'm planning a react-static live-stream / group chat for all those interested in being a maintainer/contributor.
I will be going through the following agenda items:

React-Static's past, motivation, goals, and future
How we want to automate/collaborate on Github and NPM
Architectural overview
Code Overview
Specific implementations for complex parts of RS
The v6 plugin system, how it probably needs to evolve even more.
"PR", the marketing kind ;) and other various community-bound discussions.

I plan on using something Google hangouts or zoom.us and I plan on recording the meeting for future maintainers/contributors to watch.
Browse the source beforehand. The more you are familiar with the inner workings of RS, the more productive we can be!
Bring questions, but most importantly, bring ideas and solutions on how we can make RS work more smoothly.
I plan on doing this meeting sometime during the day this week between the hours of 9:30 and 2 MST. I plan on the entire meeting going for about an hour, but am okay if we go over by another hour.
If you have specific times that work best for you, speak now!

if we can do later on in the week, that will be ideal for me :) Will be on the hangout for sure

Between those hours are perfect.

if you could give a day's heads up on twitter too that'd be great

Yes, I'm interested too!

I think we're going to tentatively shoot for Wednesday, 10AM MST. The hangout will be hosted here: https://hangouts.google.com/call/kxtrzI_sFswXNW3ZUD7vAAEE (I hope those links don't expire)

Damn, I will be in the road. Hope to see recording after.

Dang, I'll be at the Framework Summit then. I'll have to check out the recording afterwards.

Time and date works for me :) Excited to be a part of it.

For those who cannot make the meeting tomorrow, I will gladly do a second mini-meeting as long as we can find a time that works for a majority of you. Comment with your available times :)

I can't participate unfortunately but I'd be super happy if you could record it and make it available somewhere!

literally any other time this week would work, haha. you picked the one period i'm traveling. but i'll dial in tmr

For those who miss it, I also don’t mind getting on a call and doing a recap :)

I would love to dial in but I have a meeting that evening :/ another day would work nicely for me though!

Meeting starts in 2 hours!

https://hangouts.google.com/hangouts/_/iqoe3qoxdnenjiwn3qxbperzn4e

@tannerlinsley, i missed this! please let me know if you will be doing another. maybe during the upcoming 3 day weekend?

Agenda

Motivation & Goals
Library Overview
Code & Architecture
Todos

Collaboration on Github and NPM

PR descriptions, labels, triaging issues
Contributor Doc / Guidelines

Release Automation

Travis - Run Tests
Push the release to the proper branch (branch + PR description / notes)

Master
Release
Beta
Next

React-Router ⇒ Reach Router

Own Router API

navigate()

V6

React 16-ify
Plugin API (2nd iteration) (client-side plugins)
Test pages directory support (nested routes)
Improve testing
Dogfood/experimenting v6 in our own sites
react-static-plugin-gatsby-plugin

Use a gatsby plugin in react-static
API translation layer Gatsby API ⇒ React-Static API
Not everything will be supported, but some will

"PR", the marketing kind ;) and other various community-bound discussions.

Design Good Sites / Marketing material for RS
Documentation - needs a big upgrade, too sparse, no search, more branded
Gatsby + Next backed by funding, large companies.
Open Source Future of RS, Netlify cares about RS (because it's truly OSS)
CodeSandbox (I'm working on one right now https://codesandbox.io/s/72n304yq40)
Examples into users hands quickly
Be active on Twitter, tag @reactstaticjs
Spectrum.chat/react-static

Motivation & Goals
Other SSG's were either too heavy, too dirty, or diverged from React

"Just React"
Reduce pain and complexity, not LOC
Library Size & Complexity
Power = Flexibility
Speed

Library Overview
React-Static is a tool to handle the common SSG pains of

Bundling / Code-Splitting
CSS strategies (imports, css-in-js, webpack, loaders)
Iterative Development (Hot Reloading)
Routing
Preloading JSON, Templates/Chunks
Asset Pipelining (Public folders, imports, webpack resolves)
Static Exporting
Progressive Enhancement
Speed, auto-optimizations

It does this using the following tools:

React / ReactDOM
Babel
Webpack
React-Universal-Component (import('../myComponent.js') = chunk)

webpack-flush-chunks (reports chunk names)
extract-css-chunks-webpack-plugin (css support)
The best.

React-Router (Reach-Router)
React-hot-loader
Socket.io (hot-data-reloading)

Roughly, these are the lifecycles for each stage:

Start

Subscribe to Config

Defaults & Overrides
Resolve Paths
Resolve Plugins
hook('config')

Clean temp directory
Fetch siteData
Create index.html placeholder from Document
Subscribes to and prepare Routes

Routes built and normalized from config and pages directory

Extract Templates from all routes
Bundle for Dev and start the webpack development server

JIT Middleware for siteData and routeData
Socket for hot-data-reloading is provided as well

Bundle

Build Config (same as in start)
Clean dist directory (same as dev
Fetch siteData
Prepare Routes (same as in start)
Extract Templates from all routes
Copy Public Files
Bundle for node and production

Export

Build Config (if not already built)
Prepare Routes (if not already prepared)
Export Routes

Fetch siteData
Fetch routeData
Write data to JSON

Route-split
Shared Data (woah...)

Multi-threaded renderToString

Page-specific data is embedded in HTML for initial page speed

Client

HTML is rendered
React Mounts on existing HTML

First load RouteData and SiteData use JSON embedded in HTML

Link / Prefetch used to preload templates and JSON
History is monkeypatched to disallow route changes until required webpack chunks and JSON are loaded
All data is cached in the session and made available to RouteData on the fly

@tannerlinsley I'm willing to help and be a maintainer 👍

:hand: Willing and ready to help!

Did ya miss our contributor onboarding call? Watch the call whenever you have time!
https://www.youtube.com/watch?v=z8dtYF7CMMY
We discuss in length the ins and outs of ReactStatic and how you can help contribute to its future right now! #react #oss #Hacktoberfest2018 #JAMstack #javascript
https://twitter.com/ReactStaticJS/status/1047548731665436672

I've added everyone who attended the meeting as a collaborator on the project up this point! Thanks guys!

Thanks Tanner!

Also, I've created a Project here: https://github.com/nozzle/react-static/projects/2 to help us all coordinate on the library. If you are a contributor you should be able to add, edit and link cards there!

@tannerlinsley Thanks for the invitation. Let's get to work :)

I've added everyone who attended the meeting as a collaborator on the project up this point! Thanks guys!
@tannerlinsley I wasn't added. Can you add me, please?

I've added everyone who attended the meeting as a collaborator on the project up this point! Thanks guys!

@tannerlinsley I wasn't added. Can you add me, please?

@tannerlinsley Me as well!

@max-allen Added 😄

@krvajal Added 🎉

should this be a weekly meeting? im currently trying to formally get some time from work to do this, and i know not everyone can commit to this same level of commitment. but i dont know how else oss groups are run.

I would gladly do one off meetings whenever needed. We can always record them for posterity too.

We could plan a meeting around a single subject, like the plugins for example.

To better help all of us work together more closely, I've created a private slack organization where we can have private chats, ping each other more quickly, and have more fast-paced creative conversations.
Please send an email to tannerlinsley[at]gmail.com from the email you'd like me to send an invite to.

Hey guys sorry, only now I had time to watch all 2 hours of first hangout meeting. So I have followup questions:
What about dynamic routes in context of Reach-router and other context of v6 ? I do have many pages which is allowed for authorized users only.
How did you test multithreading on netlify? They told me that they provide only single core for deploying.

Dynamic routes will still work just fine in v6. If we do end up switching to Reach Router, I have no doubt it will be just as good, or possibly better at handling dynamic routes than react-router, but haven't gotten that far yet.
Multithreading doesn't come out of the box on netlify so they say, but I've seen even free plans running on a mulit-core. For testing, they gave me a standard enterprise box which comes with 6 cores (I think). I've been using https://github.com/tannerlinsley/react-static-large-site-test to do that.

FYI: https://twitter.com/tannerlinsley/status/1052198459460055040
@ 8:15 MST (in 30 minutes) I’ll be live-streaming how @ReactStaticJS’s browser-client works and how #react #suspense has already helped shape v6 into a better library.
Watch/chat here: https://t.co/XKwRRGvrgw


Play application plugin: Write plugin implementation class with current model

Convert existing logic from software model to current model
Can compile Java/Scala code
Can create JAR and assets JAR
Can run a Play application

Note: Calls off to task type in Gradle core including the Play tool chain

Implementation:

https://github.com/gradle/play/blob/master/src/main/java/com/lightbend/play/plugins/PlayApplicationPlugin.java


Add predefined variable ${fileDirBasename}

Hello, I have some dotnet solutions opened as my root workspace.
For example:
${workspaceFolder}:
/home/username/dotnet-solution1
${file}:
/home/username/dotnet-solution1/project1/Program.cs
/home/username/dotnet-solution1/project2/Program.cs
/home/username/dotnet-solution1/project3/Program.cs
/home/username/dotnet-solution1/project4/Program.cs
When I open Program.cs or other cs file, I want press F5 to debug the corresponding project.
So I need this ${fileDirBasename} variable.
this is my expected lanunch config:
{
    "name": "Launch current project",
    "type": "coreclr",
    "request": "launch",
    "preLaunchTask": "build",
    "program": "${fileDirname}/bin/Debug/netcoreapp2.0/${fileDirBasename}.dll",
    "args": [],
    "cwd": "${fileDirname}",
    "stopAtEntry": false,
    "console": "internalConsole"
}

my expected build task:
{
    "label": "build",
    "command": "dotnet",
    "type": "process",
    "args": [
        "build",
        "${fileDirname}/${fileDirBasename}.csproj",
        "/property:GenerateFullPaths=true",
        "/consoleloggerparameters:NoSummary"
    ],
    "problemMatcher": "$msCompile"
}

/findDuplicates

There might be already a feature request for this, unfortunetly I can not find it.
Leaving it open as a feature request for now and assigning to @alexr00

for this project directory structure what is this variable different than ${relativeFileDirname}?

@rioj7
consider this example:
/home/username/dotnet-solution1/dir1/project1/Program.cs
${relativeFileDirname} will be dir1/project1, I won't get "${fileDirname}/${fileDirBasename}.csproj" using ${relativeFileDirname}

@kzhui125  I have added this variable to the extension Command Variable v0.7.0.
In case you have a project structure
/home/username/dotnet-solution1/dir1/project1/Program.cs
/home/username/dotnet-solution1/dir1/project1/subdir1/tool.cs

And if your current file is tool.cs the launch or build will go bad.
Then you should use extension.commandvariable.file.fileAsKey
{
  "version": "2.0.0",
  "tasks": [
    {
        "label": "build",
        "command": "dotnet",
        "type": "process",
        "args": [
            "build",
            "${input:chooseFileBasename}/${input:chooseFileBasename}.csproj",
            "/property:GenerateFullPaths=true",
            "/consoleloggerparameters:NoSummary"
        ],
        "problemMatcher": "$msCompile"
    }
  ],
  "inputs": [
    {
      "id": "chooseFileBasename",
      "type": "command",
      "command": "extension.commandvariable.file.fileAsKey",
      "args": {
        "/project1/": "project1",
        "/project2/": "project2"
      }
    }
  ]
}

You need to make the key as specific as needed.

Could you do ${fileDirname}/${relativeFileDirname}/${fileBasenameNoExtension}.csproj?

@rioj7 thanks, I will have a try.
@alexr00
for example:
/Users/test/Documents/dotnet-solution1 opened as ${workspaceFolder}:
/Users/zm/Documents/dotnet-solution1/dir1/project1/Program.cs opend as ${file}
my expected launch.json:
/Users/test/Documents/dotnet-solution1/dir1/project1/bin/Debug/netcoreapp2.0/project1.dll
my expected tasks.json:
/Users/test/Documents/dotnet-solution1/dir1/project1/project1.csproj
${fileDirname} will be /Users/test/Documents/dotnet-solution1/dir1/project1
${relativeFileDirname} will be dir1/project1
${fileBasenameNoExtension}.csproj will be Program.csproj
so ${fileDirname}/${relativeFileDirname}/${fileBasenameNoExtension}.csproj will be:
/Users/test/Documents/dotnet-solution1/dir1/project1/dir1/project1/Program.csproj
It's not as expected.

${workspaceFolder}/${relativeFileDirname}/${fileBasenameNoExtension}.csproj?

@alexr00
${fileBasenameNoExtension}.csproj will be Program.csproj
But project1.csproj is expected

Ok. The feature request here is for a variable the resolves to the second to last segment of the current file's path.

The new variable is fileDirnameBasename

\closedWith 551db7ec94f02a4bdc8999092cf8bef642b3992d

Verified with
{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "echo",
            "type": "shell",
            "command": "echo",
            "args": ["${fileDirnameBasename}"],
            "problemMatcher": []
        }
    ]
}


Integrate MultiPL-E

WIP Integration of MultiPLE

This code pulls out code that we normally run in the MultiPL-E evaluation container.
I think the easiest way to address the dependency problem is the following:

Tell a user "you had better have dependencies installed!"
We can give them a container with both the PL toochains installed and the eval-harness dependencies, along with some instructions on how to run commands in a container.

Yes exactly! I'll upload some code and instructions to use the container

Re: performance issues.
I have obtained the following results for Python and Java on HumanEval:
Python:
pass@1: 0.181 // temp 0.2
pass@10: 0.284 // temp 0.8
pass@100: 0.466 // temp 0.8
Java:
pass@1: 0.143, // temp 0.2
pass@10: 0.252, // temp 0.8
pass@100: 0.416 // temp 0.8

Which are pretty consistent with previously self-reported numbers (off by < 0.02).

This implementation now matches original MultiPL-E for all scores including for pass@100 after this fix
{
  "multiple-py": {
    "pass@10": 0.29917045146858745,
    "pass@100": 0.4996997700167089
  },
  "config": {
    "model": "bigcode/santacoder",
    "temperature": 0.8,
    "n_samples": 200
  }
}


Releasing from RC with no patch branch tries to use minor branch

When trying to release 3.7.1 from 3.7.1-rc1 there was no 3.7.1 branch. cow tried to create the release from 3.7.x-dev instead which means bringing in commits that were not meant to make the 3.7.1 release.
If there's no patch branch we should fall back to the latest tag (ie: 3.7.1-rc1 in this case) if it exists for the release version we are aiming for...

@tractorcow we had a brief chat about this and some other things this morning. Do you know why cow v2 doesn't create patch branches any more?
We were of a consensus that making patch branches is probably how this should behave by default (even if transparently creating a patch branch, merging and deleting it does nothing in most cases). This would mean we can tag security releases easily without releasing the rest of the patch changes in a minor release line too.
Do you have any thoughts about this?

Somewhat related: RFC: Better handling of minor release branches

Because composer only worked with patch versions with self.version. This is because you'd install 3.7.1.x-dev, and the self.version would work all the way down the chain.
With the new cow you NEED the branch-alias for those branches. Because you don't have 3.7.1.x-dev in the branch-alias it wouldn't install.
The fix is to have cow make the branches, but then instead of relying on composer to "set" the right branch on install, you'd make cow reset them post-install. You'd also need to adjust the 'branching' option to support the patch branch.
Not terribly hard but it was done this way intentionally. The major motivation is that I was sick to death of deleting and merging those branches manually. And with 10+ modules multiplied by the number of releases, it was a huge maintenance burden.
Just so you know what you are getting yourself into. :)

We also need to ensure it uses the full git refs when referencing patch release branches vs. tags (they have the same "short name"). This tripped us up in the 4.2.0 release recently.

We've resolved this limitation by introducing the release:checkout-tagged-base command, which shifts the branches back to the last commit in common with the related release candidate (e.g. shifts to match 4.6.1-rc1 for the 4.6.1 release.) That approach has been working pretty well for us this year. Based on that, I don't think adjustments to support patch-level branches are necessary.


os/sdk-modifying-flatcar.md: Call out name of development branch

The names were not explicitly mentioned because the transition to the
new branch structure wasn't completed. We have now settled for main
as development branch but there is no new Edge development branch yet
which needs to be added here later.

:+1:
vbatts@melisma ~/trunk/src/scripts $ ./set_version --dev-board --board-version amd64-usr/main-nightly --dev-sdk --sdk-version sdk-main-nightly
vbatts@melisma ~/trunk/src/scripts $ echo $?
0


Need Help to Add More Zones, Work, Paren'ts House, etc.

First of, let me say, this is fantastic integration with really amazing documentation.  I'm struggling how to figure out how to add more zones, i.e. work, parent's house, etc with friendly names.
Where can I create more zones...so if I'm currently at work, can I define a zone with my current location?

You would do this in Home Assistant > Settings > Areas & Zones

John, that is the thing to do. Zone changes will be picked up automatically by iCloud3 when they are made. That is what a zone is for.

Thank you! It works. I’m new to Home Assistant
On Mon, Feb 26, 2024 at 8:07 PM John @.***> wrote:

You would do this in Home Assistant > Settings > Areas & Zones
image.png (view on web)
https://github.com/gcobb321/icloud3_v3/assets/12992040/f4301f68-b51c-476b-bcd5-bd82851b963d
—
Reply to this email directly, view it on GitHub
https://github.com/gcobb321/icloud3_v3/issues/280#issuecomment-1965609556,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABF66EW5OWJOUYRBI7XBTTDYVUWT7AVCNFSM6AAAAABD3D3MEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRVGYYDSNJVGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thank you! It works. I’m new to Home Assistant.
On Mon, Feb 26, 2024 at 8:07 PM John @.***> wrote:

You would do this in Home Assistant > Settings > Areas & Zones
image.png (view on web)
https://github.com/gcobb321/icloud3_v3/assets/12992040/f4301f68-b51c-476b-bcd5-bd82851b963d
—
Reply to this email directly, view it on GitHub
https://github.com/gcobb321/icloud3_v3/issues/280#issuecomment-1965609556,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABF66EW5OWJOUYRBI7XBTTDYVUWT7AVCNFSM6AAAAABD3D3MEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRVGYYDSNJVGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


🐛 Source code in showcase app not color-highlighted

Describe the bug
In the showcase app, the source code for "A read-only TextBox with various properties set" is not color-highlighted.
To Reproduce
Steps to reproduce the behavior:

Go to https://bdlukaa.github.io/fluent_ui/#/forms/text_box
Click on 'Source code' below "A read-only TextBox with various properties set"
See that the source code is not color-highlighted

Expected behavior
Source code should be color-highlighted, the same way as the other source code is
Screenshots

Apparently it's because of a typo, fixing it

I did a quick search through the example app.
The InfoBar as a popup section is also poorly highlighted.


Can not add localhost as custom Safe App anymore.

While testing out my Safe App, I used to be able to add localhost as a custom app. Now I get an error "The app doesn't support Safe App functionality."
I've recently changed browsers, so I re-visited Chrome and found that my localhost custom app is still cached there and still works there. But if I open up an incognito window and try to add it, I also get "The app doesn't support Safe App functionality."
Dev console says The FetchEvent for "http://localhost:3000/manifest.json" resulted in a network error response: the promise was resolved with an error response object., but it's there if I visit the url and it's the same manifest.json we use for our production app.

Could you confirm that you configured CORS correctly for the app? For me it's possible to access an app via localhost
https://github.com/safe-global/safe-apps-sdk/tree/main/packages/safe-apps-sdk#cors


Configure extension storage

Context

#45

Todos

WM enabled flag (global)
List of websites where WM was disabled by the user
Wallet address information (id, authentication server, resource server, asset code, asset scale)
Remaining balance (can be stored alongside wallet address information?)
Amount type (recurring or single-use)

can be a flag (recurring: true | false)

Access tokens & manage URLs for:

quotes
outgoing payments

Rate of pay (cents per hour)

Info: related to task #59

@ionutanin update on 23 Jan:
Complete dev for state management store config & local context provider with custom hooks to retrieve data from store.
In progress: unit testing
Goal: have ready for review by the end of the 25 Jan

@ionutanin has now added unit tests (with min. 80% coverage), and is about to begin the next #59 .

Agreed that @ionutanin will address review and get final review in order to merge PR today (16 Feb).


Add some whitelist items for belts

About the PR

t-ray scanner, gas analyzer for tool belt
syringe for botany belt
trash tag for swab
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl: lzk

tweak: added some tools to belts whitelist
tweak: swab is trash now

Is it intentional that chief engineer belt was not updated to being able to hold t-ray and gas analyzer?

lmao
gonna make pr later


⚠ Fortnite has degraded performance

In cd97eba, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1641 ms

Resolved: Fortnite performance has improved in c7dab7a.


Add getCode() method to DeserializeThis that can return the generated code.

This PR adds a new method to DeserializeThis, which returns the underlying generated code.
http.get("url/to/resource").deserializeThis("MyClass").getCode()

This is helpful when exploring REST API's and you want to start making your code mode type-safe. Some plugins exist for this already in the Market Place, like https://plugins.jetbrains.com/plugin/9960-json-to-kotlin-class-jsontokotlinclass- which has almost a million downloads. So the use case is probably pretty common.
The returned code is cleaned up, so all serialization code is removed including the use of UntypedAnyNotNull and UntypedAny which are replaced with the normal Any and Any?
Regarding the API:
I am not 100% sure that having this method DeserializeThis is the best place. While it is natural to put it there, maybe it would be nicer to move it directly to the HttpResponse so you can do something like:
http.get("url/to/resource").generateDataClass("MyClass")

Or alternatively have a getCode() method on the generated top-level class so you can do:
// Cell 1
val response = http.get("url/to/resource").deserializeThis()

// Cell 2
response.getCode()

Input is welcome.

Testing this a bit further I ran into this use case:
@Serializable
public data class DeserializedClass(
    public val `object`: String,
    public val `data`: List<Any?>,
    @SerialName("has_more")
    public val hasMore: Boolean,
)

Which makes me think that maybe we should keep the Serialization API's, since you probably want to use it with Ktor, but Any is not supported so you get a compile-time warning. I am leaning toward that being fine as it indicates you have a problem with your API response that needs to be handled somehow 🤔

Moved review to Space


tag mv not found

raise Exception("Error: tag '{}' is not found. Please check your input SAM/BAM file.".format("mv"))
Exception: Error: tag 'mv' is not found. Please check your input SAM/BAM file
this error is showing while runnign this code "# PAF output for plotting
ALIGNMENT=reform_output.paf
squigualiser reform --sig_move_offset 0 --kmer_length 1 -c --bam out.sam -o ${ALIGNMENT}"

What's the command you used for basecalling? Likely you missed the flag to ensure to move table.

dorado basecaller<EMAIL_ADDRESS>/data/gecko/bioinf_shared/minion_storage/230615-FNB-mk1c/KLPN/20230615_1225_MC-115296_FAW84557_c4d119ad/pod5 > /home/user_pool_1/mohd/POD5/230615-FNB/calls.bam

Hi @UmairK291095,
Please pass the argument --emit-moves.

Worked. Thanks


Compatibility with kurento webRTC server

Hii,
Hope all are doing good.
Can we play the p2p call to a kurento webRTC server using this demo app ?

hi did you find any solution??


Error on C-c C-k when cider-error/cider-doc is showing

Occasionally, when the *cider-error* or *cider-doc* buffer is showing, and you try to evaluate a file with C-c C-k, the error/doc buffer vanishes and the error
Wrong type argument: stringp, nil

is shown in the minibuffer.

It would be great to have a reliable way of reproducing this error. Perhaps it only happens if you use a hyperlink in the error/doc buffer to jump to another file, before you do C-c C-k?

Tentative steps to reproduce:

Evaluate a form at the REPL that gives an error.
In the stack trace buffer, click on one of the hyperlinks that points to one of your currently open buffers.
Press C-c C-k.
Receive error:

Wrong type argument: stringp, nil

The above steps are not necessary nor sufficient for reproduction. I still don't have a 100% reproducible test case, but the problem is in this function in CIDER. Under certain unknown conditions, quit-window causes the current window to be reset to the cider-repl buffer, which causes nil to be returned from buffer-file-name, which results in the error above.


Json deserialization

In order to easily use the json file for documentation rendering, could it be possible to "deserialize" and get a ProjectReflection object ?

Neat idea! Currently not possible, and this would probably require a fair bit of work since serialization is spread out over so many different classes right now. If you want a ProjectReflection for now it's probably best to use the api to generate one.
const td = require('typedoc');
const app = new td.Application({
  // options
});
const inputFiles = app.expandInputFiles('src');
const projectReflection = app.convert(inputFiles);

From what I (believe to) recall this is practically impossible at the moment because:

not all the required information is retained in the JSON output,
there's a lot of cross-references between reflections that cannot be restored,
there are references to TypeScript type instances that cannot be skipped.

A better way might be to stop accessing reflection instances in the theme and instead rely on a reduced dataset (like from toObject()).

I recently spent quite a bit of time in the serialization code and agree with mootari. There isn't any nice way to resolve this. If you need a ProjectReflection when rendering a theme, the best way to do that is to use the code I provided above.

So... this seems to be a recurring theme with TypeDoc for me. I think something is impossible, then 6 months or a year later I come back and realize - this isn't that difficult. There are a few things that need to happen first (and some of these are being done for library mode), but this is definitely doable, and I really like the idea.

[ ] Semi-revert the serialization work done to separate models and serailizers. We still need the serialization module so that plugins can add their own data to the serialized models, but much of it can be restored to the models so that the code lives together and is easier to reason about.
[ ] Create a new method on Application:interface Application {
    restoreFromJson(json: object): ProjectReflection
}

[ ] Create the Deserializer module.interface Deserailizer {
    addReflectionDeserailizer(kind: ReflectionKind, Extract<SomeReflection, { kind }>)
    addReflectionDeserailizer(kind: TypeKind, Extract<SomeType, { kind }>)
    deserializeReflection(json: object): SomeReflection
    deserializeType(json: object): SomeType
}

The deserializer should work in much the same way as the serializer used in library mode (not pushed to GH yet, still have another 200 or so type errors to fix...)

#1180 is the more common user facing side of this feature, so I'm going to track it over there.


Update list view page

Update the page so that the user can view the people who are a part of that particular list

Update list view page works and has been merged and deployed.


Failed to Parser Path on Windows 11

Xmake Version
v2.9.6+20241030
Operating System Version and Architecture
Windows 11 23H2 v22631.4317
Describe Bug
After creating a new xmake project, in CLion, with a WSL, with the config,

When click the "run" button, the little green triangle, the IDE alerted an IDE internal error, with details here
java.nio.file.InvalidPathException: Illegal character [:] in path at index 17: \\wsl$\ArchlinuxD:\Codelib\SDLDemo
	at java.base/sun.nio.fs.WindowsPathParser.nextSlash(WindowsPathParser.java:224)
	at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:130)
	at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
	at java.base/sun.nio.fs.WindowsPath.parse(WindowsPath.java:92)
	at java.base/sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:231)
	at java.base/java.nio.file.Path.of(Path.java:148)
	at com.intellij.execution.configurations.GeneralCommandLine.withWorkDirectory(GeneralCommandLine.java:153)
	at io.xmake.utils.execute.CommandExKt.createWslProcess(CommandEx.kt:53)
	at io.xmake.utils.execute.CommandExKt.createWslProcess$default(CommandEx.kt:39)
	at io.xmake.utils.execute.CommandExKt.createProcess(CommandEx.kt:72)
	at io.xmake.utils.SystemUtils$runvInConsole$1$1.invokeSuspend(SystemUtils.kt:140)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:608)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:873)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:763)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:750)

Expected Behavior
On a totally user face, it is supposed to nothing to happend.
For the function here, the path resolving, it is supposed to resolve correctly.
Project Configuration
Nop, since there's no configuration generated.
Additional Information and Error Logs
Error message
java.nio.file.InvalidPathException: Illegal character [:] in path at index 17: \\wsl$\ArchlinuxD:\Codelib\SDLDemo
	at java.base/sun.nio.fs.WindowsPathParser.nextSlash(WindowsPathParser.java:224)
	at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:130)
	at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
	at java.base/sun.nio.fs.WindowsPath.parse(WindowsPath.java:92)
	at java.base/sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:231)
	at java.base/java.nio.file.Path.of(Path.java:148)
	at com.intellij.execution.configurations.GeneralCommandLine.withWorkDirectory(GeneralCommandLine.java:153)
	at io.xmake.utils.execute.CommandExKt.createWslProcess(CommandEx.kt:53)
	at io.xmake.utils.execute.CommandExKt.createWslProcess$default(CommandEx.kt:39)
	at io.xmake.utils.execute.CommandExKt.createProcess(CommandEx.kt:72)
	at io.xmake.utils.SystemUtils$runvInConsole$1$1.invokeSuspend(SystemUtils.kt:140)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:608)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:873)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:763)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:750)

The Remote Directory field should contain a Unix path.

I will add validation and error handling logic later.

A better way is considered to specify a new configuration for WSL, I suggest.

A better way is considered to specify a new configuration for WSL, I suggest.

Yes, you can create a new configuration in the configuration editor later.
By the way, don't forget to save and sync the project before building. Although the plugin includes a simple upload feature, it is recommended to use tools like rsync instead.

I mean, a new UI to specify if using WSL, a new configuration UI.
---Original---
From: @.>
Date: Sun, Nov 3, 2024 23:48 PM
To: @.>;
Cc: "Yaokai @.>;"State @.>;
Subject: Re: [xmake-io/xmake-idea] Failed to Parser Path on Windows 11 (Issue#60)
A better way is considered to specify a new configuration for WSL, I suggest.
Yes, you can create a new configuration in the configuration editor later.
By the way, don't forget to save and sync the project before building. Although the plugin includes a simple upload feature, it is recommended to use tools like rsync instead.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: @.***>

Thanks for your suggestions. I will consider making improvements.


fix for - Not able to remove or add a new cluster-admin in rosa cli

fix for - Can't create temporary admin user for ROSA cluster
Signed-off-by: Tzvika Avni<EMAIL_ADDRESS>SDA-6170
SDA-6106

@pvasant PTAL

@zgalor @oriAdler  PTAL

/ok-to-test

@zvikorn I left one comment on the name of the constant. Other than that, it is GTG.

/lgtm


[BUG] make p-values consistent with the literature

Reference issue

Closes #15009
What does this implement/fix?

The implementation of p-value computation via a permutation test in scipy.stats.multiscale_graphcorr was inconsistent with how they are computed in the literature. This PR fixes that.
Additional information

@mdhaber Just opened a PR

It seems like the failures in the tests are unrelated to my code

It would be OK to check that the p-value is divisible by 1/(n+1) but not 1/n.

@tupui added. @mdhaber this test basically does that. In previous tests it returns 1/1000 but this checks if it returns 1/1001

Thanks @sampan501@tupui !


Create a dashboard page with the most added and removed entities

Only for entity lists

Duplicate of https://github.com/WormBase/author-first-pass/issues/206


Enum singleton cases should be optionally serialized to string.

enum E {
  case E1
  case E2
}

val e: E = E.E1
println(e.asJson) // expect "E1"  json string here, but current is {"E1":{}}

In most situations, serializing singleton cases to empty object is meaningless.  Actually, we want a string const here.

I found this technique in source code to accomplish this behavior:
import io.circe.derivation.ConfiguredEnumCodec
import io.circe.derivation.Configuration
import io.circe.syntax.*

given Configuration = Configuration.default

enum E derives ConfiguredEnumCodec {
  case E1
  case E2
}

val e: E = E.E1
println(e.asJson) // got "E1"


iOS / Android: Events stop when touched HTML Element is removed from the DOM

Hello,
I have a big problem with hammer js on iOS devices: There seems to be a problem with events and removed HTML elements. Say we have a container, on which we use hammer with one panstart and one panmove handler. Inside we have a HTML element, which we start dragging. When the the element is removed during some logic inside the panmove handler, no event will be fired anymore, even if the finger is still on the device and moving. Desktop browsers don't show this annoying behaviour. Any suggestions?

Losing track of user input because the underlying dom element has been removed is likely expected and acceptable behavior. Closing unless @arschmitz feels otherwise.

This is actual specified behavior on Touch-Events and thus can not be fixed in hammerjs.
When perfoming a touch gesture all subsequent events are send to the exact same Element where the gesture startet. This means, all touchmove Events are send to the same element where touchstart was fired. This still happens, when the corresponding element is removed from the DOM. Because of the the touchmove ebent send to the elemen will not bubble through the DOM to your listener any more. This is specified browser behavior and can not be changed.
If you want to caputure the touchmove-event after removing the node from the DOM you have to reattach the event.target vom touchstart (panstart) to the DOM within the element your hammer-instance is bound to and hide it any other way (e.g. display:none).


Incompatible with latest Stripe (10.3)

I am trying to add this bundle to my project but it seems that the latest version of Stripe is not usable.
Below is the error from the terminal
Information from https://repo.packagist.org : #StandWithUkraine
Using version ^0.8.1 for fpt/stripe-bundle
./composer.json has been updated
Running the update of composer fpt/stripe-bundle
Loading composer repositories with package information
Updated dependencies
Your requirements could not be resolved into a set of installable packages.

 Problem 1
    - The root file composer.json requires fpt/stripe-bundle ^0.8.1 -> satisfiable by fpt/stripe-bundle [0.8.1].
    - fpt/stripe-bundle 0.8.1 requires stripe/stripe-php ^v7.121.0|^v8.0.0|^v9.0.0 -> found stripe/stripe-php [v7.121.0, ..., v7.128.0, v8.0.0, ..., v8.12.0, v9.0.0, ..., v9.9.0] but it conflicts with your root composer.json require (^10.3).

Use the --with-all-dependencies (-W) option to allow upgrades, downgrades and removals of packages currently locked to specific versions.
You can also try to rerun compose require with an explicit version constraint, e.g. "compose require fpt/stripe-bundle:*" to see if a version is installable, or "compose require fpt/stripe-bundle:^2.1" if you know which one you need.
The installation failed and the ./composer.json and ./composer.lock files reverted to their original content.

Composer.json:
"require": {
    ....
    "stripe/stripe-php":"^10.3",
}

Thanks.

+1

Hello, @Papoel  thank you for reporting this issue. I just merged a fix to allow v10 and publish 0.9, can you please have a look ?

Hi @FabienPapet sorry for answering so late, I haven't had time to look yet but I will do that soon. Thanks for the consideration.


The result of "Format document" is weird of certain HTML content.

From @slayerxj on July 28, 2017 7:28

VSCode Version: Code 1.14.2 (cb82febafda0c8c199b9201ad274e25d9a76874e, 2017-07-19T23:34:09.706Z)
OS Version: Windows_NT ia32 6.1.7601
Extensions: none

Steps to Reproduce:

The origin code is

...
EDA system Alpha-SX series

Execute "Format Document".
The result is

...
EDA system Alpha-SX                series

The setting "editor.wordWrap": "off", which is the default value. But actually most lines are wrapped.
But in this case the line is not wrapped and have a lot of redundant white-spaces.
Here is a minimum file to reproduce this issue.
<!DOCTYPE html>

Reconstruct the schematic editor the EDA system AlphaSX series

Copied from original issue: Microsoft/vscode#31628

We use http://jsbeautifier.org/ as underlying formatter.
To repruduce on http://jsbeautifier.org/:

paste example above to http://jsbeautifier.org/
set 'Wrap lines near 120 characters'
format

@aeschli -
Excellent bug report.
With the repro steps you provided, I can reproduce the issue.
I see your original comment said you have  "editor.wordWrap": "off".  But then your repro steps talk mention setting wrap to 120.  To have wordWrap turned off you'd set the wrap value to 0.  Then this problem does not occur.

@bitwiseman Sorry for the confusion. Ignore the "editor.wordWrap": "off" comment. That's a VSCode setting and is not related to html formatting. I'll update the description...

I am seeing the same thing in VSCode 1.16.1, particularly after inline a and code tags.
I am using " " instead of spaces to prevent the unwanted white space appearing (the unwanted white space can cause problems in output).


Additional Macro

@mohammed82008 built this nice macro for defining concrete structs that respect user parameters here:
https://github.com/JuliaNonconvex/NonconvexCore.jl/blob/master/src/utilities/params.jl
Do you guys think it'd be worth it to move the code for it here? I think @params is fairly generic, so I'd suggest keeping up the pattern with @cement.

Nice, thanks! I too would like an excuse to make a cement macro, which is 80% of why I proposed this.
@mohamed82008 Do you know of anything else @params does that @concrete doesn't, or can I close this issue?

or can I close this issue?

Looks like you can close this issue :)


Don't suggest Code snippets for import statements

Environment data

Language Server version: 2020.10.3
OS and version: macOS
Python version: 3.9

Feature description
When writing an import statement, Intellisense currently suggests Code snippets. See screenshot below. IMO it doesn't make much sense to for example suggest try / except when writing from typ.... In those cases I'm looking for a specific module and not exception handling. Same with import typ...

I'm going to transfer this to vscode-python; these are provided by the Python extensions snippets which we don't have control over. They'd need to be improved to better detect the right context.
(Personally, I don't think the snippets are even worth having, but that's my preference.)


Request the Full password sync potential issue FAQ | Revoke token behavior

Hi Team,
After run the full password sync, the end user's token will be revoked. We may need to remind the end user to refresh the current status. As it is tenant level configuration, if you can provide this reminder FAQ in this document will be better in case the end user surprised logout in the old session
And, the audit log showed the password update may also give the admin side confusion.

Please let me know if you need more information. many thanks!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dedc709c-19ce-e83b-dae8-7cc18793632e
Version Independent ID: 1f14d8cc-761d-1cf3-e40a-6a8774b7e812
Content: Enable password hash sync for Azure AD Domain Services
Content Source: articles/active-directory-domain-services/tutorial-configure-password-hash-sync.md
Service: active-directory
Sub-service: domain-services
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@TonySh127-ms Thank you for the feedback . We will investigate and update this thread.

thank you so much @shashishailaj !

WE were not able to verify this and hence we would like to understand more on this. Could you please send us an email on azcommunity [at] microsoft [dot] com with a subject line  "ATTN Shashi" and referencing this issue and we will help you with the next steps of engagement .
Thank you. .


Go SDK: Improve compatibility with Fiber web framework

While implementing SSE with DataStar Go SDK in a Fiber application, I encountered challenges due to the SDK's dependency on net/http interfaces.

DataStar's NewSSE requires http.ResponseWriter and http.Request
Fiber uses fasthttp underneath
Attempts to bridge using Fiber's HTTP adapter result in non-functional SSE connections

Working alternative without using DataStar GO SDK helpers:
app.Get("/events", func(c *fiber.Ctx) error {
    c.Set("Content-Type", "text/event-stream")
    c.Set("Cache-Control", "no-cache")
    c.Set("Connection", "keep-alive")
    c.Set("Transfer-Encoding", "chunked")

    c.Status(fiber.StatusOK).Context().SetBodyStreamWriter(func(w *bufio.Writer) {
        for {
            msg := fmt.Sprintf("event: datastar-merge-signals\nretry: 1000\ndata: signals { \"ordersToday\": %s }\n\n",
                strconv.Itoa(rand.Intn(100)))
            fmt.Fprintf(w, msg)

            if err := w.Flush(); err != nil {
                return
            }
            time.Sleep(2 * time.Second)
        }
    })
    return nil
})

Is there a viable way that maybe I'm not seeing at the moment to use your SDK along side with Fiber without workarounds?

I understand the reasons behind your statement. I was struggling on why my handler was stuck in the event loop until I analyze the SDK source code. No problem, now I know that the custom methods I developed were needed for my case. Go point on HTTP2, I wasn't are of that. Thank you again @delaneyj.


feedback and suggestions

Is it necessary (appears yes) to undertake domain validation when domains are also hosted in Azure DNS (same account/region)?  It seems there should be an easier way to validate domains we own and which are hosted in Azure DNS (not Azure App Service Domains) - why can't this process be totally automated as in "Please select from your Azure DNS hosted domains "  Seems needlessly complex...
Are there any special instructions to configuring records where you have child zone setup (e.g. staging.mydomain.com)
It would be good if the examples provided showed entering information in Azure DNS.  The values supplied have titles "type, host, value" - would be good to see exactly how these correspond to titles of form elements in Azure DNS when creating CNAME and TXT records.  I've done this process a number of times and always struggle to get it to work...
Rod

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

ID: 224b73dd-c59d-a833-0d4d-a778af6086a9
Version Independent ID: c6b167c9-9589-45d0-ee6a-7a47a4aec41e
Content: Map existing custom DNS name - Azure App Service
Content Source: articles/app-service/app-service-web-tutorial-custom-domain.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@rodneytamblyn
Thanks for your feedback! We will investigate and update as appropriate.

To clarify this issue:
I have discovered that automated certificate generation from Azure App Service is not possible for DNS child zones.  The solution was to delete the child zone (staging.mydomain.com) and enter the required CNAME and TXT records on the root zone (mydomain.com).  It needs to be very explicitly warned when creating child zones that App Service automated certificate generation will not be possible.
Rod

Thank you for your feedback. We're adding this to our backlog to prioritize. #please-close


chore(build): upgrade slsa framework and verifier

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind cleanup
Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area library
What this PR does / why we need it:
Another slsa fix.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: LucaGuerra
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [alacuku]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


aarch64-binfmt-P: Could not open '/lib/ld-linux-aarch64.so.1': No such file or directory

I get this error when trying to run the AMD64 version on an x64 CPU. Very odd!

Looks like you have the ARM64 version instead?


bug: 211 mikemurray mini cart quantity

Resolves #211
Impact: minor
Type: feature/bugfix
Issue
The quantity input in the cart drawer was not hooked up to the withCart decorator. This issue revealed itself when the I fixed the issue where the popover would close on click here: https://github.com/reactioncommerce/reaction-next-starterkit/pull/212
Solution

Add event handlers to adjust cart item quantity

Testing

Add an item to the cart
Hover over the cart icon to open the mini-cart drawer
Adjust the quantity in of the item
Hover off of the cart drawer, and back unto it to ensure the changes to the quantity did indeed happen.

Known issue
It seems as though the quantity input is not reactive for some reason. If you're on the cart page and open the mini-cart drawer and increment the quantity, then the input doesn't change. This may be related to how the quantity input handles local state.

@willopez This should be reviewed after #212 has been merged to master


How to accept octet-stream

I have the input sample:
input_sample = b"image_content"

Is there a way to accept binary content? I would like to send raw data (e.g. --data-binary of curl)

Instead of implicitely converting to base64, the schema should expect octet stream when input is bytes


Looking forward to your open source！

Great work, looking forward to open source and roughly when it will be released!

< 3 weeks


Fix links in the README

Just a few minor README link fixes.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

I signed it!

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

I'm going to mute this thread. Please @-me if you need a response.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Looks like the links have been fixed in a prior PR. Thanks!


error: "Request failed with status code 401"

Please help, I have read the other "401 issues" and have the latest update for headless-cms but still doesn't work?
And it's the same for me, if I put same wordpress adress as site adress then I can access "http://localhost:3000/api/get-products" otherwise I get:
{
"success": false,
"products": [],
"error": "Request failed with status code 401"
}

Same issue

Hello,
Also stumbled upon this issue.
Did you find a solution for this?


Copy only selected tabs

Users can now select tabs in Firefox.  When more than one tab is selected, how about changing the menuitem to "Copy selected tabs URLs" and just copy those?

@Gitoffthelawn Done. Tested in both Chrome and Firefox.

Thank you so much!


delineator, clamshells

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 5
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[c,d]

/trunk merge


feat: Expanded with Loop Language

If you want to know more about the Loop Programming Language go to:

looplang.org
github.com/looplanguage

Nice!


msgpack requirement fails on older versions

requirements.txt line 3 doesn't specify a minimum version of python-msgpack. 0.4.6 works, 0.3.0 throws an exception when importing eom:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/gunicorn/arbiter.py", line 473, in spawn_worker
    worker.init_process()
  File "/usr/lib/python2.7/dist-packages/gunicorn/workers/base.py", line 100, in init_process
    self.wsgi = self.app.wsgi()
  File "/usr/lib/python2.7/dist-packages/gunicorn/app/base.py", line 115, in wsgi
    self.callable = self.load()
  File "/usr/lib/python2.7/dist-packages/gunicorn/app/wsgiapp.py", line 33, in load
    return util.import_app(self.app_uri)
  File "/usr/lib/python2.7/dist-packages/gunicorn/util.py", line 362, in import_app
    __import__(module)
  File "/opt/rse/rse.py", line 29, in <module>
    from eom import auth
  File "/usr/local/lib/python2.7/dist-packages/eom/auth.py", line 140, in <module>
    __packer = msgpack.Packer(encoding='utf-8', use_bin_type=True)
  File "_packer.pyx", line 77, in msgpack._packer.Packer.__init__ (msgpack/_packer.cpp:77)
TypeError: __init__() got an unexpected keyword argument 'use_bin_type'

No idea what the actual minimum version needed is, sorry. Presumably it's whenever the use_bin_type argument was added to msgpack.Packer.

We can probably just require that it be 0.4.6 and higher; I don't think there was ever a specific version intended.


Data rounding on RiskProfiler

There are a few issues open pertaining to data rounding (#29, #46, #43), so I am making one issue that will cover them all.
Included below is a proposed rounding scheme for data presented on RiskProfiler. This should be implemented site-wide (maps and charts). I suspect some back and forth between the science and dev team will be needed to get this right, so consider this scheme as V1. Also, @phil-evans, as you implement this, if you notice the results are coming out weird, make a comment here so it can be addressed.
Scenario data
Dollars:
if x = 0, display '0'
if x < 1000, display 'less than 1000'
if x >= 1000 display two significant figures (e.g. 23,456 becomes 23 thousand; 234,567 becomes 230 thousand; 2,345,678 becomes 2.3 million)
Injuries/Building Damages:
if x = 0, display '0'
if 0 < x < 1, display '0'
if 1 <= x < 10, display 'less than 10'
if x >= 10, display two significant figures (e.g. 422 becomes 420, etc.)
Disaster Debris:
if x = 0, display '0'
if x < 100, display 'less than 100'
if x > 100 display two significant figures (as above).
Probabilistic Data
Probable Life Loss:
if x = 0, display '0'
if 0 < x < 0.01, display one significant figure.
if x > 0.01 display two significant figures.
Ratios:
if x = 0, display '0'
if x < 0.01, display one significant figure.
if 0.01 < x < 0, display two significant figures.
Capital Asset Loss:
Follow DRSA scheme for dollars
Building Damage:
Follow DSRA scheme for building damages

this required a pretty extensive overhaul of the method of formatting/displaying figures - ready to review on both the scenarios and risks pages

@JulieVdV @plesueur @tieganh please review

I started looking into this yesterday and following @plesueur rounding scheme above comparing it on  beta riskprofiler and against our postgis db (v1p4p3). Writing a specific query for each condition to match above scheme and picking a few spots to validate the results. Will compare 1 scenario assuming the method applies to all and look at the risks.

Gone through 1 scenario and everything looks fine. Only one possible mismatch I noticed is when rounding to 2 sig figs for values under 100. For example, 14.xx becomes 10, 27 becomes 30 etc. Technically that's 1 sig fig only so not sure if that needs to be changed or mentioned somewhere else that its ok. @plesueur @phil-evans
Will start looking at the probabilistic next.

fixed today along with the eCr_Fatality bug - see #74

Just following up from our meeting on Thurs for small values that are >0 and mentioning display sig figs, it should still display the sig fig value and not 0. For example actual value 0.0022 should display 0.002 (1 sig fig, psra life loss rule) and not 0.

Hello Folks!
First of all, this looks awesome. Thank Habitat7 for all the effort on this one.
As a final check, I looked over the rounding results, and have a few edits below (listed in order of priority).

[ ] Highlighting Will C's observations about the 0 values being reported for probabilistic results. Please follow the scheme for rounding probabilistic values.

[ ] Need to apply the rounding scheme to the scenario overview side panels. In the below examples, Deaths should = 3.4 thousand; Damage should = 18 thousand buildings

[ ] I am proposing the following minor edit to the rounding scheme provided at the top of the page. The rationale for the change is that you can clearly see the exact values on the graphs when x < 100, and notice a discrepancy in what is reported. This will resolve that.

Scenario data - Injuries/Building Damages:
if x = 0, display '0'
if 0 < x <= 1, display '1 or less'
if 1 < x < 100, report a range to the nearest 10 (1 to 10, 10 to 20, 20 to 30, 30 to 40, 40 to 50, etc...).
if x >= 10, display two significant figures (e.g. 422 becomes 420, etc.)

[ ] Risk scores are rounded to the nearest ten currently (as requested, sorry about that!). Please round to the integer.

Just reviewed. Looking so good! Thanks for all the effort. A few comments.

[ ] I'm not sure if I'm looking at the most recent version, but I don't see the scenario injuries/building damage data rounding scheme update. This includes reporting values between 1 < x < 100 as a range to the nearest 10 (e.g. if X is between 1 and 10 report '1 to 10' on the bars and map, if it's between 10 and 20, report it as '10 to 20' on the bars and map, and so forth up to x < 100). See example below. Let me know if you have questions.

[ ] you may be working on this now, but if not, for the average annual fatalities and annual probability of fatality (probabilistic data), the values shown on the map should match those on the sidebar. In other words, use the same rounding rules. See examples below.
-here average annual fatalities reported on the map should be 0.0008.

-here the annual probability of fatality reported on the map should be 0.000001.

check it out now @plesueur - for the first one i misread the request and i had only made it round to the nearest 10 rather than a range.:

Nice work Phil! Using a range to the nearest ten works great! No proposed edits on that one at this point.

Also nice work on matching the map and sidebar values. Looks good to me.
@wkhchow and @phil-evans , I'm getting some interesting results for the annual probability of fatality and average annual fatalities.
Example 1: showing 0 average annual fatalities even though the color shows its much higher.

Example 2: I get a 0 annual probability of fatality for Toronto. Is that correct based on our database?

Also nice work on matching the map and sidebar values. Looks good to me.
@wkhchow and @phil-evans , I'm getting some interesting results for the annual probability of fatality and average annual fatalities. Example 1: showing 0 average annual fatalities even though the color shows its much higher.  Example 2: I get a 0 annual probability of fatality for Toronto. @wkhchow is that correct based on our database?

The newest revision is being updated and should fix the 0 probabilities mentioned above.

[ ] Scenario data - Injuries/Building Damages:
if x = 0, display '0'
if 0 < x <= 1, display '1 or less'
if 1 < x < 100, report a range to the nearest 10 (1 to 10, 10 to 20, 20 to 30, 30 to 40, 40 to 50, etc...).
if x >= 10, display two significant figures (e.g. 422 becomes 420, etc.)

Following up again on this rule above.
It looks like the rules are applied to the PSRA as well for absolute damages/injuries, but when viewing the probability we see the actual 'rounding' applied. Just want to confirm we want that applied to PSRA side as well?  @phil-evans @plesueur

good catch @wkhchow - the sidebar indicators were formatting according to the rules of the current selected indicator, rather than the rules that should be applied for each individual figure. so it looked right when you were exploring 'annual fatalities' etc but not 'economic loss'. please review and let me know if you're still seeing bugs.
also see below:

if a number is tiny enough javascript returns it as 'Xe-Y' - should we change that to display as 0.0000000X?

@phil-evans. Annual probability of fatality is often reported in scientific notation, but I think you're right to report it as a decimal for this case. We may lose people when there are too many zeros, but we would probably lose more people to a number with a 'e' in the middle.

good catch @wkhchow - the sidebar indicators were formatting according to the rules of the current selected indicator, rather than the rules that should be applied for each individual figure. so it looked right when you were exploring 'annual fatalities' etc but not 'economic loss'. please review and let me know if you're still seeing bugs.
also see below:

if a number is tiny enough javascript returns it as 'Xe-Y' - should we change that to display as 0.0000000X? @plesueur

FYI @phil-evans. I was just poking around the riskprofiler.ca website, and the issue Will found still persists there (but is resolved on the .work site).


Exclusion syntax for paket.template files

PR for #880

[X] parses -- to exclude files
[x] change to !* pattern
[x] disallow the space to avoid ambiguity
[X] apply pattern/globs during packaging
[x] when fixing a relative path (..) append \ to windows drive (C:)
[ ] how to exclude entire directory

is this ready to merge?

Will push the latest fixes after lunch ;)

Apart from not matching against directories (!myDir) where you'd have to use (!myDir/*.*) everything should be in. It would probably be enough to fix that in Fake.Globbing without touching this code.

it's also important to have a bit of documentation for this.

:+1:

Is the documentation sufficient?

Yep thanks a lot

very cool. thanks a lot.
released in paket 1.18


Failed to load certificate chain from

Hello all,
We have been struggling to have Isito operational within our K8’s environment running within a VMWare PKS private cloud platform. Specifically, we are required, per our organization’s security policy and posture, to use our PKI’s keys.
A quick summary of our environment:
We have a 2-tier PKI environment (Root -> Issuing CA). We cut/signed a Subordinate CA certificate for the Istio CA (to sign on behalf of our PKI Issuing CA) from our issuing CA. In the end, here is what we are expecting the PKI to look like in context to Istio:
Root CA -> Issuing CA -> Istio CA -> Leafs (i.e. Envoy, etc.)
We have created all proper certificate files for Istio to use, following this document:
We have created a K8’s secret:

kubectl create secret generic cacerts -n istio-system --from-file=ca-cert.pem --from-file=ca-key.pem --from-file=root-cert.pem --from-file=cert-chain.pem

We are also installing Istio using istioctl; moved away from helm and ported our values over. In addition, we are applying the default profile:

istioctl manifest apply --set profile=default  --set values.global.mtls.enabled=true

We started with v.1.46, and consistently we would identify within the logs our certificate chain would be loaded properly just after Citadel signed its certs.
Example:

validationServer          x509 cert [0] - Issuer: (this is the Istio generated cert signed by the Istio CA as the Subject is blank) Subject: ""
validationServer          x509 cert [1] - Issuer: (this is the subordinate CA public key/cert that our internal issuing CA signed)
validationServer          x509 cert [2] - Issuer: (this is our Issuing CA’s public key/cert from our internal PKI)

All looks normal until after the ‘validationController’ completes, during discovery with Pilot, when Istiod is attempting to reach out to each [and every] service, it fails with a [generic] handshake error:
Example:

grpc: Server.Serve failed to complete security handshake from "###.###.###.3:48326": EOF

The ingress controller fails to start and its log states ‘unable to communicate with Envoy (Is Pilot running?)‘ type messages. The Istio-proxy container, within the Prometheus pod, states the same thing too. All makes sense given the condition.
We tried different angles, and nothing would work for us. On the cusp of seeing 1.51 being released in just a matter of a few days, we waited for that to be released and attempt with the new version.
We went ahead and tried on 1.51 with no success still; however, the outcome behavior is different. This time, the ingress controller came ‘up’ as healthy, but its log again barks about the same issue – unable to communicate with Envoy. The same behavior, like with 1.46, occurs within istio-proxy too (doesn’t start, same log entries). The kicker, we get a completely different error within Istiod’s logs. Instead of a [generic] security handshake message, we receive this (seems to be at the same procedure time when each service is being connected to initially like in 1.46):
> warn    ads      ADS:CDS: ACK ERROR <IP_ADDRESS>:40606 router~###.###.###.3~istio-ingressgateway-75877dc5bf-jrnrs.istio-system~istio-system.svc.cluster.local-1 Internal:Error adding/updating cluster(s) outbound|15020||istio-ingressgateway.istio-system.svc.cluster.local: Failed to load certificate chain from <inline>, outbound|80||istio-ingressgateway.istio-system.svc.cluster.local: Failed to load certificate chain from <inline>, outbound|443||istio-ingressgateway.istio-system.svc.cluster.local: Failed to load certificate chain from <inline>, outbound|15029||istio-ingressgateway.istio-system.svc.cluster.local: Failed to load certificate chain from <inline>, outbound|15030||istio-ingressgateway.istio-system.svc.cluster.local: Failed to load certificate chain from <inline>, outbound|15031||istio-ingressgateway.istio-system.svc.cluster.local: Failed to load certificate chain from <inline>, outbound|15032||istio-ingressgateway.istio-system.svc.cluster.local: Failed to load certificate chain from <inline>, outbound|31400||istio-ingressgateway.istio-system.svc.cluster.local: Failed to load certificate chain from <inline>, outbound|15443||istio-ingressgateway.istio-system.svc.cluster.local: Failed to load certificate chain from <inline>
How can it state this?: Failed to load certificate chain from <inline>
Here is what I mean by that question, I exported the cert that was generated/signed (from: /var/run/secrets/istio-dns), grab the chain, subordinate cert, and root cert, feed it into OpenSSL – it’s good.

Openssl verify -CAfile root-cert.crt -untrusted intCA.crt -untrusted istioca.[internal_FQDN].crt new-chain.pem
new-chain.pem: OK

We went ahead and turned on 'debug' based logging (wow, there's a lot to comb through!). All we were able to distinguish/confirm was our root-CA's public key does get passed down to each namespace; presuming this is to add it to a "trust store" to trust it. Which is good to see.
Help, please? :)
Thank you!

Eric Buono

Expected behavior
Istio to start properly; Envoy and pilot to use the certificate chain we have defined.
Steps to reproduce the bug
This occurs on every installation using our signed subordinate CA certificate. Using the demo certificates, Istio installs and starts up without any issues.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
istioctl version:

client version: 1.5.1
control plane version: 1.5.1
data plane version: 1.5.1 (5 proxies), 1.4.3 (1 proxies)

Kubectl version:

Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"20c265fef0741dd71a66480e35bd69f18351daea", GitTreeState:"clean", BuildDate:"2019-10-15T19:16:51Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"windows/amd64"} Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"20c265fef0741dd71a66480e35bd69f18351daea", GitTreeState:"clean", BuildDate:"2019-10-15T19:07:57Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
istioctl

That log comes from Envoy rejecting the config. For whatever reason it isn't loading the certs correctly. I would suggest getting a config dump from one of the pods that rejects this: https://github.com/istio/istio/wiki/Troubleshooting-Istio#collecting-information-2 and see what the cert config looks like, and additionally maybe turning envoy debug logging on to see if it explains why it failed to load

Thanks for the reply! Sounds good, that will be our next steps tomorrow then. We were out of ideas on where to go from here. I'll report back - thanks!

Thanks again Howard for the pointer! We were able to extract the Envoy config and after decrypting the encoded chain, it was obvious what was happening. To provide insight to someone else down the road, here is what we saw:

-----BEGIN CERTIFICATE-----
[Leaf]
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
[SubCA-Cert]
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
[Issuing CA Cert]
-----END CERTIFICATE----------BEGIN CERTIFICATE-----
[Root CA Cert]
-----END CERTIFICATE-----

We just needed to add a carriage return at the end of the cert-chain file. The EOF was at the pipe (below):

-----END CERTIFICATE-----|

It needs to be like this (obviously!):

-----END CERTIFICATE-----
|

Got to love simple mistakes that make you chase your tail.
I hope this helps someone else down the road.
Thanks all!
-Eric


Typecast problem

Apollo version:
apollo-runtime version 0.4.4
apollo-android-support version 0.4.4
apollo-rx2-support 0.4.4
i have a problem with typecasting
LatestEventsQuery latestEvents = LatestEventsQuery.builder()                 .portal("23ffbb5d-d57c-40aa-ae7d-2415dd1f58e3")                 .start(new Date().getTime())                 .end(new Date().getTime() + DateUtils.WEEK_IN_MILLIS * 8)                 .build();
okHttpRequest body:
{"query":"query latestEvents($portal: UUID!, $start: DateTime!, $end: DateTime!) {  latestEvents(dateRange: {start: $start, end: $end, timezone: \"UTC\"}, portal: $portal) {    __typename    edges {      __typename      node {        __typename        uuid        title        lastUpdated        featuredImage {          __typename          url(params: {width: 600, height: 400, method: CROP})        }        dateRange {          __typename          start          end        }        locationName      }      cursor    }    pageInfo {      __typename      endCursor      hasNextPage    }  }}","variables":{"portal":"23ffbb5d-d57c-40aa-ae7d-2415dd1f58e3","start":"1519049720683","end":"1523888120683"}}
problem is variables.start is string instead of Long

I see that $start: DateTime! is a grahql custom scalar type. So it will be serialized as string. If you need it to be sent as Long then this graphql field must be declared as Int.
See com.apollographql.apollo.CustomTypeAdapter#encode it always returns String.

Ok, GraphQL spec was abstract to the encode format of custom scalar types, I guess this PR fixes this issue https://github.com/facebook/graphql/pull/326.
We need to allow user to define what Json supported type will be returned as result of com.apollographql.apollo.CustomTypeAdapter#encode