Improve fuzzy match for word input

Currently, there is only correct or wrong input. We want fuzzy matches, for example to catch typos. solved.
If the word "Glättkelle" is being asked for, we might accept "Glattkelle" as well. Or "glättkelle". solved.
We could introduce a new counter for "almost correct". That means words that have only a few wrong characters do not count as wrong but as "almost correct". solved.
If the user input is almost correct, we should not go to the next word immediately, but show the correct answer instead. Additionally, we could display a yellow glow around the input field in order signalize that the input was almost correct. solved.

give users the chance to correct the word 1 time and reduce the bar to get the almost right status.

idea: try using a more sensitive string distance algorithm like cosine similarity (rather than levenshtein distance)

Show what exactly changed to improve the word from almost right to right.

Add more hints for word second try.

Not relevant anymore (since this repo now is a pure CMS)


Switch to go install to install hack/generate

go get is no longer supported outside of a module in the legacy GOPATH mode (that is, with GO111MODULE=off). Other build commands, such as go build and go test, will continue to work indefinitely for legacy GOPATH programs.

from 1.22 release notes: https://tip.golang.org/doc/go1.22
Should fix https://master-jenkins-csb-serverless-qe.apps.ocp-c1.prod.psi.redhat.com/job/ci/job/knative-nightly-ci-eventing-kafka-broker/732/console

/cc @matzew


✨ Add support for Canvas docs block

Add support for the psuedo Story parameter for stories rendered in the Canvas block in MDX-based stories (the Docs addon).
Fixes #11

Rewrite stylesheets on the DOCS_RENDERED event in addition to STORY_RENDERED
Apply the .pseudo-[state] classes directly to the story elements in docs pages

👋🏻 I'm fairly new to some of the Storybook internals so I'd love to know if there's a better way to apply the CSS classes to individual stories in docs pages.

any update? this looks promising

@isc30 I did set up my fork to publish to @hover/storybook-addon-pseudo-states if you're looking for a solution in the meantime.


Support ALTER SERVER to change connection url

Problem Statement
User mappings and foreign tables rely on a foreign server, which means you cannot change or fix a connection string once a user mapping or foreign table is created. Additionally, testing a foreign server is only truly possible after these elements are added.
Possible Solutions
Support ALTER SERVER similiar to PostgreSQL:
ALTER SERVER name OPTIONS ( SET url 'jdbc:postgresql://example.com:5432/')

Considered Alternatives
dropping foreign tables, user mappings and foreign server, then recreate all of them.

@proddata Thank you for reporting. It's implemented by #17131 and will be released with the upcoming 5.10 feature release.


Trigger notification after 5 minutes

According to https://github.com/toggl/toggl-button/issues/1444, The idle notification should be triggered after 5 minutes, but it will only be triggered when the user's state change from idle to active.
This PR attempts to Trigger the idle notification after 5 minutes of idle time regardless of the use state.
Also if the user's state change from idle to active  and the inactive period were more than 5 minutes, I believe this is what the desktop app does.

@shantanuraj I just updated the PR considering the offsets that you suggested :)

@chukitow I merged your changes in #1466  https://github.com/toggl/toggl-button/pull/1466/commits/2f8298ae6236e2b41f7645d3d18fa80b26bb6e97

Did some minor cleanup to conform with our commit conventions
Removed the delta thingie I suggested, without maintaining local state multiple notifications were being triggered at short intervals doesn't offer any significant improvements on the cost of more code.
Refactored the code a bit.
Squashed the commits

Closing this.

Awesome! @shantanuraj let me know if there is anything else I can help with :D

That'll be it for now, we'll push a release to the stores in a few hours
Thanks for your contribution 🙇


network: fetch blocks in parallel

Blockcache size is 2000, while max request size is 500.
Try to fetch blocks in chunks starting from current height.
Lower height has priority.
Close #1376 .

Maybe it can be simplified. You can store the highest requested block in Server (requestedHeight) and upon entering into requestBlocks compare it to BlockHeight(). Then
if requestedHeight < blockHeight + 1500
    CompareAndSwapUint32(requestedHeight, old, old + 500)
    NewGetBlockByIndex(requestHeight+1, -1)
else
    index := random(4)
    NewGetBlockByIndex(blockHeight+index*500, -1)

This way we start with blockHeight, then move on to blockHeight + 500, then + 1000, then + 1500. If we keep entering this function before blockHeight moves +500, we're re-requesting randomly things in blockHeight/blockHeight + 200 range. Non-random requests can lead to starving if we only have 4 peers and one of them never responds for some reason.
And that's it, I think it's a little simpler (no locking, no maps).

Actually, this solution explicitly prevents starving by not updating number of sent requests if the request sent to client is sent again. Though there are some other unlikely situations when starving is probable (should be easy to fix).
random solution is a bit simpler, but harder to test. I'll try it.


Add @MainActor annotation to navigationTransition(:interactivity:)

I believe the recent release of SwiftUI Introspect 1.3.0 breaks SwiftUI Navigation Transition by isolating introspect(:on:scope:) to @MainActor.

It's urgent fix.. waiting for it too :)

Thanks @tgrapperon!


when building sample Muai :	The type or namespace name 'Devices' does not exist in the namespace 'Windows'

Cannot build the sample on VS2022. i suppose there is some library more that i need ??
Steps to reproduce

Open the sample from the github page in VS2022
install Plugin.ble v3.1.0 beta.1
build Ble.Client.maui project

Expected behavior
i expect the sample would build as this should not be very old.
Actual behavior
84 errors with  namespace errors like :
Error	CS0234	The type or namespace name 'Devices' does not exist in the namespace 'Windows' (are you missing an assembly reference?)	Plugin.BLE (uap10.0.19041)	C:\Users\HP\source\repos\dotnet-bluetooth-le\Source\Plugin.BLE\Windows\Adapter.cs	13	Active
Crashlog
Configuration
Version of the Plugin:  Plugin.ble 3.0
Platform: Win 11
Device:  PC HP

Hi @ghisbo,
I'm the friendly issue checker.
Thanks for using the issue template :star2:
I appreciate it very much. I'm sure, the maintainers of this repository will answer, soon.

Probably some problem with the Windows SDK? Either it's missing completely or you have a wrong version. BLE.Client.Maui targets version 10.0.19041.
For me the MAUI sample client builds and runs well on Windows (with VS 2022 version 17.8.3), and it also builds alright in our CI.


Attempt to execute code removed by Dart AOT compiler (TFA)

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Android logcat output when launching release application.
Stacktrace
I  Attempt to execute code removed by Dart AOT compiler (TFA)
I  #0      AddonsObjectBoxStorageProvider.create (package:addons_benefits/core/data/object_box/addons_object_box_storage_provider.dart)
I  <asynchronous suspension>
I  #1      AddonsBenefitsInjectionModule._registerProviders (package:addons_benefits/core/addons_benefits_injection_module.dart:144)
I  <asynchronous suspension>
I  #2      AddonsBenefitsInjectionModule.registerDependencies (package:addons_benefits/core/addons_benefits_injection_module.dart:88)
I  <asynchronous suspension>
I  #3      _initFeatures (package:my_app/src/application/di/injection_container.dart:193)
I  <asynchronous suspension>
I  #4      init (package:my_app/src/application/di/injection_container.dart:180)
I  <asynchronous suspension>
I  #5      _registerDependencies (package:my_app/main.dart:257)
I  <asynchronous suspension>
I  #6      main.<anonymous closure> (package:my_app/main.dart:36)
I  <asynchronous suspension>
I  #7      main (package:my_app/main.dart:32)
I  <asynchronous suspension>

Expected results
Android release application interacts with a user.
Actual results
Android release build gets stuck when launching an application. It doesn't crash but just freezes and stops performing. The debug build works as expected. iOS release and debug builds are working fine.
Code sample
Code sample
The first instance of code where it possibly fails
static Future<AddonsObjectBoxStorageProvider> create({
    required AddonReminderDomainModelMapper mapper,
  }) async {
    Directory directory = await getApplicationDocumentsDirectory();
    String appPath = directory.path;
    String directoryPath = '$appPath/addons';
    Store store;
    if (Store.isOpen(directoryPath)) {
      store = Store.attach(getObjectBoxModel(), directoryPath);
    } else {
      store = await openStore(directory: directoryPath);
    }
    return AddonsObjectBoxStorageProvider._create(store, mapper);
  }

Logs
Logs
I  Attempt to execute code removed by Dart AOT compiler (TFA)
I  #0      AddonsObjectBoxStorageProvider.create (package:addons_benefits/core/data/object_box/addons_object_box_storage_provider.dart)
I  <asynchronous suspension>
I  #1      AddonsBenefitsInjectionModule._registerProviders (package:addons_benefits/core/addons_benefits_injection_module.dart:144)
I  <asynchronous suspension>
I  #2      AddonsBenefitsInjectionModule.registerDependencies (package:addons_benefits/core/addons_benefits_injection_module.dart:88)
I  <asynchronous suspension>
I  #3      _initFeatures (package:my_app/src/application/di/injection_container.dart:193)
I  <asynchronous suspension>
I  #4      init (package:my_app/src/application/di/injection_container.dart:180)
I  <asynchronous suspension>
I  #5      _registerDependencies (package:my_app/main.dart:257)
I  <asynchronous suspension>
I  #6      main.<anonymous closure> (package:my_app/main.dart:36)
I  <asynchronous suspension>
I  #7      main (package:my_app/main.dart:32)
I  <asynchronous suspension>

Flutter Doctor output
Doctor output
[!] Flutter (Channel unknown, 3.10.6, on macOS 14.0 23A344 darwin-arm64, locale en-GB)
    ! Flutter version 3.10.6 on channel unknown at /Users/rsetkus/opt/flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/docs/get-started/install.
    ! Unknown upstream repository.
      Reinstall Flutter by following instructions at https://flutter.dev/docs/get-started/install.
    • Framework revision f468f3366c (4 months ago), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/rsetkus/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS and macOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once installed, run:
        sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
        sudo xcodebuild -runFirstLaunch
    • CocoaPods version 1.12.1

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

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

[✓] IntelliJ IDEA Community Edition (version 2023.2.4)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

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

[✓] Connected device (3 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64  • Android 14 (API 34) (emulator)
    • macOS (desktop)             • macos         • darwin-arm64   • macOS 14.0 23A344 darwin-arm64
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 118.0.5993.117

[✓] Network resources
    • All expected network resources are available.

Thanks for the report @rsetkus
Can you provide us complete runnable reproducible code sample that throws the error ?

AddonsObjectBoxStorageProvider.create (package:addons_benefits/core/data/object_box/addons_object_box_storage_provider.dart)
I  <asynchronous suspension>
I  #1      AddonsBenefitsInjectionModule._registerProviders (package:addons_benefits/core/addons_benefits_injection_module.dart:144)
I  <asynchronous suspension>
I  #2      AddonsBenefitsInjectionModule.registerDependencies (package:addons_benefits/core/addons_benefits_injection_module.dart:88)
I  <asynchronous suspension>

These seems to be coming from third party implementation.

cc @alexmarkov

Thanks for the report @rsetkus Can you provide us complete runnable reproducible code sample that throws the error ?

AddonsObjectBoxStorageProvider.create (package:addons_benefits/core/data/object_box/addons_object_box_storage_provider.dart)
I  <asynchronous suspension>
I  #1      AddonsBenefitsInjectionModule._registerProviders (package:addons_benefits/core/addons_benefits_injection_module.dart:144)
I  <asynchronous suspension>
I  #2      AddonsBenefitsInjectionModule.registerDependencies (package:addons_benefits/core/addons_benefits_injection_module.dart:88)
I  <asynchronous suspension>

These seems to be coming from third party implementation.

I can try a minimal reproducible application. Is there anything else that would be helpful for you to detect the area of problem?

Repro would be the best. It might be duplicate of https://github.com/dart-lang/sdk/issues/52874
Try checking if making store variable nullable fixes it.

Repro would be the best. It might be duplicate of dart-lang/sdk#52874
Try checking if making store variable nullable fixes it.

Trying to apply the changes @mraleph suggested but after the change, it takes hours to make a build (roughly 5 hours). Build gets stuck at step
[+919448 ms] [+919301 ms] kernel_snapshot: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents:
/Users/rsetkus/projects/my-app/features/addons_benefits/lib/core/data/object_box/addons_object_box_storage_provider.dart}
[  +57 ms] [ +246 ms] /Users/rsetkus/opt/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/Users/rsetkus/opt/flutter/bin/cache/dart-sdk/bin/snapshots/frontend_server.dart.snapshot --sdk-root
/Users/rsetkus/opt/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk_product/ --target=flutter --no-print-incremental-dependencies -DBUILD_TYPE=enterprise
-DSHA1_CERTIFICATE=... -Ddart.vm.profile=false -Ddart.vm.product=true --aot --tfa --packages
/Users/rsetkus/projects/my-app/.dart_tool/package_config.json --output-dill
/Users/rsetkus/projects/my-app/.dart_tool/flutter_build/d66a517e4f75945a72904f6846bea346/app.dill --depfile
/Users/rsetkus/projects/my-app/.dart_tool/flutter_build/d66a517e4f75945a72904f6846bea346/kernel_snapshot.d --source
file:///Users/rsetkus/projects/my-app/.dart_tool/flutter_build/dart_plugin_registrant.dart --source package:flutter/src/dart_plugin_registrant.dart
-Dflutter.dart_plugin_registrant=file:///Users/rsetkus/projects/my-app/.dart_tool/flutter_build/dart_plugin_registrant.dart --verbosity=error package:my_app/main.dart

Not sure if that is related Dart AOT. Any ideas about what might it cause?

@rsetkus Could you create a minimal reproduction? Also, could you try building your app with the latest Flutter version on the main channel? The main channel can be selected using flutter channel main and then flutter upgrade.

Hi. Just heads up, I am working on creating a minimal reproduction. The error appears on a large scale project, so it might take some time to create it.

Hi. Here is the minimal reproducible project https://github.com/rsetkus/flutter-mre. I have managed to recreate the same error as we get on actual project.

@rsetkus thank you! could you please license the code in the repo under some open source license (e.g. MIT, Apache, BSD, GPL - all work, not AGPL preferrably). We can't look at the code which does not have a clear license.

@rsetkus thank you! could you please license the code in the repo under some open source license (e.g. MIT, Apache, BSD, GPL - all work, not AGPL preferrably). We can't look at the code which does not have a clear license.

Done

I can reproduce the problem on Flutter 3.10.6, but not on the current tip of the tree. As far as I can see, this is indeed a duplicate of dart-lang/sdk#52596.
After changing code in AddonsObjectBoxStorageProvider.create() to Store? store; the problem disappears. Also, it builds rather quickly: frontend_server step took ~20s on my machine.
@rsetkus Could you post the full build log (with `-v) of the slow build, so we would see all timings? Can you reproduce the slow build on your minimal repro project?
Consider upgrading to the latest beta or wait for the next stable release which should happen soon.

You are right. Indeed, changing Store? store; does the trick. I got confused myself and changed class scope Store variable instead of the function scope.
Would you consider it as Flutter bug? If so, do you need any log reports? Happy to provide if you need.

It's worth investigating sudden increase in compilation time if it can be reproduced on the latest version. If that's the case, could you provide a minimal repro and logs?


Using useGLTF from react-three-drei

When I use a list of GLTF files to show its 3D image, at the begining they all show, but when I try to select the ones I selected before, the image will not show again.
Looks like once the image was showed it doesn't re-renders and there is no browser memory to show it back.
Do you know how to fix this? I tried attaching a useEffect when the list changes but doesn't work.
`import { useEffect } from 'react'
import { Canvas } from '@react-three/fiber'
import { useGLTF, OrbitControls} from '@react-three/drei'
import {useControls} from 'leva'
import Papir1 from '../resources/BP_LD.gltf'
import Papir2 from '../resources/CC_LD.gltf'
import Papir3 from '../resources/MC_LD.gltf'
export default function Papir3D() {
const papirs = {
    "1137 - Berenguer i Petronella" : Papir1,
    "1412 - Compromis de Casp": Papir2,
    "1605-1608 Mapa Cathalonia": Papir3
}

const {papir} = useControls({transient: false, papir: { options: Object.keys(papirs) } })

useEffect(() => {

}, [papir])

function Model({ url, ...props }) {
    const { scene } = useGLTF(url)
    return <primitive object={scene} {...props} />
}

return(
    <>
    <Canvas camera={{ position: [2, 1, 2], fov: 25 }}>
        <hemisphereLight color="white" groundColor="blue" intensity={0.75} />
        <spotLight position={[50, 50, 10]} angle={0.15} penumbra={1} />
        <Model position={[0, 0, 0]} url={papirs[papir]} />
        <OrbitControls />
    </Canvas>
    </>

)

}`

i am also having same question how to update the controls input when props changes

Please make a sandbox.

https://codesandbox.io/s/levasandbox-5bv9lc?file=/src/App.js
here is very basic example, when ever when some  parent component send props updates, in child component which is rendered should get updated value in leva component

@kkbandaru I'm not sure how the sandbox is relevant to the above, but no, Leva doesn't recompute its schema on props change. You need to add a dependency to the schema if you want to, and even though it won't change the props value. This is by design.
Here's a working version of your sandbox anyway. Not sure it has the best render flow (clearly not to be honest since you will have a double render, but anyway)...
https://codesandbox.io/s/levasandbox-forked-dt7hp6?file=/src/App.js

Closing until there's a proper sandbox showing the problem!

This is the sandbox of a working project with simple images, it works perfect:
https://codesandbox.io/s/pairing-threejs-to-ui-wlz1o0?file=/src/App.js:558-619
The problem is when I use larger files.
I can't upload more than 50Mb to sandbox, so just 2 of 3 files:
https://codesandbox.io/s/shy-framework-e4hubp?file=/src/App.js
When you change the file, it remembers the last one displayed.

Added a sandbox to this issue:
https://github.com/pmndrs/leva/issues/391#issuecomment-1284486608
El sáb, 22 oct 2022 a las 15:16, David Bismut @.***>)
escribió:

Closing until there's a proper sandbox showing the problem!
—
Reply to this email directly, view it on GitHub
https://github.com/pmndrs/leva/issues/391#issuecomment-1287788688, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AUYAZ5RQTYVETBFJ6NMNWU3WEPSK3ANCNFSM6AAAAAAREB6XOA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Switch to Nanobind (0.7.0 --> 0.8.0) broke extension example

The extensions example from the documentation is broken after switching from Pybind11 to Nanobind. (Version > 0.7.0)

Sorry about that. Should be mostly fixed in #962


Unable to run the flow using Firefox in Linux

I have problems using tagui with firefox on ubuntu 16.04.2 LTS
./tagui filename firefox
Gecko error: it seems /usr/bin/firefox is not compatible with SlimerJS.
See Gecko version compatibility. If version is correct, launch slimerjs
with --debug=true to see Firefox error message_
I am using Firefox version: 61.0.1 (64-bit)
Later I modified slimerjs/src/application.ini  file into
MinVersion=53.0.0
MaxVersion=61.*
But, it didn't work for me and when I tried to run the file after this setting, I am getting the below error..
c is undefined
-> resource://slimerjs/slQTKeyCodeToDOMCode.jsm: 36
-> resource://slimerjs/slQTKeyCodeToDOMCode.jsm: 36
-> resource://slimerjs/slimer-sdk/webpage.js: 15
How do I  able to run the flow? Please post the steps to reproduce...
Thanks in advance,
sahithi N.

Hi Sahithi, TagUI uses SlimerJS to handle Firefox browser. SlimerJS is not working with the new versions of Firefox which has compatibility-breaking changes, see the open issue here - https://github.com/laurentj/slimerjs/issues/694
Copying @Aussiroth as he will be taking over supporting questions and advice on TagUI usage.


Corrected a typo in releaseWakelock

Corrected a typo in releaseWakelock

Ahhhhh, oops, nice find, will push that out, thank you :+1:


ui(homepage): Fix file name text alignment

In PR #2947, the heading was made to align in the centre which no doubt looks good. Unfortunately now the entire page is centre aligned.
Desktop

Mobile

Solution
The idea is to make the file names left aligned, why?
Because in all the webpack docs it left aligned, hence its the standard.

how did you connect .splash h2 rule to the filenames? @pranshuchittora


WebSocket connection to 'ws://<IP_ADDRESS>:9000/' failed: Connection closed before receiving a handshake response

Hello,
I'm trying to create a web socket with your library.
With the exemple client.html,

I started the socket : php -q testwebsock.php And receive Master socket: Resource id #6
I launch a localhost server php -S localhost:8080
I access to localhost:8080/client.html

In the js console, I receive this message:
WebSocket connection to 'ws://<IP_ADDRESS>:9000/echobot' failed: Connection closed before receiving a handshake response
The issue is on firefox and chrome (up-to-date)
I'm using OSX 10.12.2
The direct command websocket = new WebSocket('ws://echo.websocket.org'); worked fine
Thanks in advance

Did you open your firewall?

Me too facing same issue ?
Any leads on this ?

you open the websocket port on server 8080 and then you try to connect with the client on port 9000.  Modify the client to reflect your server port

woww I have problem that I did not how to run web socket , in your post you explain we should both
1- I started the socket : php -q testwebsock.php And receive Master socket: Resource id How to access uri parts #6
2-I launch a localhost server php -S localhost:8080
thanks very much


About collaboration

I extracted some off topic messages from #1710 so I can reply here without continue mixing with the original topic.
@technorama commented on Oct 21, 2015, 7:44 PM GMT

@waj You've already expressed that not only my ideas but my code are not welcome regardless of what they are, even if it's your design (that you don't have or won't share).  You're unwilling to collaborate on the design online or if I fly to Argentina (your excuse was a lie).  You left me waiting for any communication whatsoever for over a week when you had already told another member you wouldn't accept my offer.  Later you claim threading is fun, not a priority, don't have the time, your contributions aren't welcome no matter what lengths you go to (even temporarily moving to Argentina and learning Spanish).
Now you're going to import an external project to one that doesn't want what I can do?  Especially when I have extensive OpenSSL experience?
@datanoise accepted my PR's quickly.  The same has not been true of crystal.
Your idea of "enjoy" is very different from mine.

Seems like you're inferring that I have something personal against you. Well, I do have something, which is the constant unpleasant way that you have to express to others. That could be something belonging to your personality, but that's all. I respect your ideas and the work you done so far, and I think you're a respectable software developer.
Regarding the particular topic that you're referring about design collaboration (multithreading in Crystal) all I did was try to let you know that I found really hard to process your ideas into our vision of Crystal at this point. You were working hard into GC and threadind issues but just to find that we are still not so sure about the direction we want to take in that area. So I thought it could be a good idea to try to stop you from working on that topic until we have a plan. Seems like this was actually a bad idea because of course you're free to even fork the project and have your own direction if you want. Still I think we're free to accept or reject any work done by others no matter how much time was spent, but I wanted to minimize that posibility.
And no, I don't want to meet you in person to collaborte on this. I think I have the right to not give a logical explanation.
@mverzilli commented on Oct 21, 2015, 9:10 PM GMT

@technorama well if you did come to Argentina and met @waj and @asterite you'd realise they're two of the nicest guys working on software out there :).

I think you're taking things way too personal: "not only my ideas but my code are not welcome", "you left me waiting for a week", "import an external project to one that doesn't want what I can do", etc.

Please realise that everyone here is contributing to the extent each one can, and @waj and @asterite are no exception. If you didn't receive a reply for a week it's because there's a lot going on: work commitments, personal lives and lots of other aspects of Crystal itself.

Everyone here is giving you credit for some important contributions you already made, but some people is asking you for a little bit more kindness on your interactions.

I'm sure your OpenSSL experience and the rest of your ideas are being taken into account just as anyone else's, so don't let your manners cast a shadow over that.

@technorama commented on Oct 21, 2015, 9:47 PM GMT

@mverzilli My issues are not with the time delays but with the way it was handled.  Another project member was told about rejecting my offer within a day or 2 and the reasons why.  It took over a week to tell me directly.   It's obviously not a time issue if they have time to speak to others but not tell me directly, ask me questions or answer any of mine. Many attempts were made to contact asterite and waj through irc, email, issues, and wiki entries.  No comments were ever made on my proposals except "don't work on that".  Every collaboration effort was made on my part and none on theirs except silence and a belated "no".

Maybe you're right and my communication suck. I'll try to improve that. Thanks for the heads up.
@technorama commented on Oct 21, 2015, 9:56 PM GMT

I've bent over backwards to collaborate on threading, get a spec approved, or get anything at all.  What will be accepted?  Who can tell me that?  Why should I create PR's when I don't know if they will be approved?  Why create issues and email proposed designs if they are met with silence?  What other options do I have other than complaining publicly or forking?

This isn't just about threading.  It's the smallest of issues sitting around for months without a response: #1284.

Again, that's why I tried to warn you asap about the posibility that we wanted to take a different direction and I didn't want you were working in vain. I think my mistake here was that I did it in private. From now on, all aspects of communication from me about Crystal will be done in public (IRC, GitHub or through the mailing list)
@kirbyfan64 commented on Oct 21, 2015, 10:14 PM GMT

@technorama BUT you're missing the point. This is a project managed by people. Which means, there inevitably will be delays, accidental non-replies (you know, when you read a GitHub issue, say you'll reply later, and don't), and stuff like that. @datanoise's project is small and has WAY fewer issues open than Crystal.

Also, about the PR approval: normally, it's best to open an issue related to whatever and mention that you'll implement it...but don't implement it yet. That way, if it gets closed, there's no lost work, and you can avoid constantly tweaking PR commits over and over again.

@technorama commented on Oct 21, 2015, 11:04 PM GMT

@kirbyfan64 You're missing the point.  I've tried all of those things.  First I created PR's which sat idle.  Then I tried issues describing the proposed interfaces which also sat idle.  Sometimes if I create the issue (which is ignored) and then submit a PR the code gets merged.  Other times neither get any feedback.  Either way I'm wasting my time.

It's requires me reading their minds to know what will or won't be approved.

Let me say this again.  As people their communication about PR's and issues suck.

I'm so sorry you feel you're wasting time. Lots of stuff contributed by you was merged already and is currently running on every program compiled with Crystal. If an issue or PR is sitting idle without answer, please try bumping the thread again. Maybe sometimes we still didn't have the time to reply. Maybe we still are not sure what to say. Or maybe we're just humans and forgot to reply.
Put yourself in our position for a moment and think about a scenario with the opposite situation: we decide to delegate some important area of the project to someone but we get no answer after some time or the work is not what we expected. Should we merge it anyway? Are either us or that person wasting time?
@technorama commented on Oct 21, 2015, 11:08 PM GMT

@kirbyfan64 You're point about @datanoise's project only supports my position.  Crystal moves too slow with issues and PR's.   The bottlenecks are @asterite and @waj.  They're busy people and that's ok but funneling everything through them is only going to make the problem worse.  I thought distributed development was a solution for this problem but apparently I'm mistaken.

Crystal moves at the speed and pace we want it to move. No rush, no pressure, we want to take the time it takes. How could we be bottlenecks? We created this project. Maybe you have a misconception about how open source should work.
My honest desire is not to extend this to an endless conversation. Instead I wish you reconsider the position you want to take and keep belonging to this community because I still consider you a valuable member.

I thought distributed development was a solution for this problem but apparently I'm mistaken.

To add to the original project, only those with write access to the original project can do it (by accepting others' patches), how else could it be done? Distributed development cannot bypass that. Remember it is possible as always with free software to make a fork/derivative (although yes, forking a big project like this, especially a language, is probably practically infeasible, at least without a lot of resources).

I want to add a couple of things to what @waj said.
@technorama Imagine this scenario: we never create Crystal. Then you come to us and say: "hey, you, why didn't you create Crystal?  As a complaint.
Now back to the real scenario: we create Crystal after spending about 3 years to do so, with all of the efforts being spent in our free time. Yes, we have a bountysource program but that doesn't cover the costs at all. We have no client, no one is really paying us or asking us to do anything. We go at our pace, because we don't like to rush things. We love this project and have a lot of fun doing it. And at the same time we might help bring the world a valuable tool, and something fun to use.  Of course you can learn Spanish, but it will take you months to learn it to a level where we can comfortably discuss these things face to face.  We have work to do, we have family, cats, and then we spend some time doing Crystal. Some of that time we have to answer issues, review pull requests, reply messages in google groups, maybe reply some things on IRC. The rest of that time (which now you can realize is pretty little) we can focus on continuing designing the language. And we wouldn't like to delegate the design of many core things to somebody else.
If the above seems unfair from our side, think of other languages. Did you, or anyone else, had a chance to define the design of Java, C# or Go? No. They have been defined by a core team without opinions or help from anyone else. I imagine Matz says "no" more than "yes" to many ideas and contributions from others.
So we could just make Crystal closed source, or just make the pull requests button go away. We don't. We provide it so others can help us build the language and propose new ideas and features, but we reserve the right to decide what we think is good or bad. With time, our opinions might change and some wishes might happen (like the formatter, or splat type restriction, or even some of your pull requests). Many other followers got rejected PR and ideas from us, and most accept our design choices, our pace and our efforts.
@vyp Forking this language is not far fetched at all. Remember: we are just a few doing it, and we do it in our free time. It seems @technorama has much more time than us, so forking it and continuing it might deliver a better, more efficient and correct language in less time. If that happens, at that point we can decide to merge the changes or just continue using the other language. See also the onyx-lang.

Well I meant in the sense of gathering a community, having website, docs etc. But I haven't seen Onyx before, that's really cool @ozra, but I wish you had some samples of the changes in syntax somewhere! https://github.com/ozra/onyx-lang#what-does-the-current-syntax-draft-look-like :stuck_out_tongue:

@technorama - You seem like a real sharp developer, intense! Now, a sidenote: I grew up with a alcoholic dad, there was lots of yelling, abusive language and fist fighting - I've learned to turn anything thrown at me to a summer breeze (ok, somewhat). But most people don't. Just as we like to format code so it fits a project, we can benefit a lot from formatting our language to communicate well in a project.
Your ideas deserve some public relations polishing - good arguments, and your skills are enough - if you try to tone down you equally intense language and keep the intensity to the coding, I think those who are more sensitive to choice of words will be more willing to listen, read, understand and ultimately merge.
People skills count when dealing with people. Keep up the good work! I really like your ideas!
@asterite @vyp - What a surprise to see a mention on Onyx here :-) Yes I reckon a lot more people than me, are seeking a "next gen" language to use, and not a Rubyish language. Now Crystal happen to be a really interesting next gen language at its core - I'm really impressed by it!
My intention is to get a language where everything's up to debate via RFC's to form an as educated idea as possible about the best way forward. And to stay completely compatible with Crystal. Because many people do love ruby syntax - and I see no reason to not share a module universe and be a "family". This way, if it hopefully takes off by interest, there are two pathways to the same core yielding PR's, fixes to libs, etc.
I realize that some people might frown upon it. But my intentions are all good :)
@vyp - I have more work that is not pushed to origin yet. I'll make sure to get some samples up.
The motto I go by initially is to support all the ideas I have so far found to be interesting or think might be interesting to others (I already have some favourites, but figure it's better to get input, hopefully a superior idea grows from collaboration), in parallel, so that it can later be distilled down.
You can basically write almost ruby syntax, almost python syntax, a more haskellish and livescriptish slant - all mixed as you will. There are no ambiguities the way it's designed now - but obviously it would be better to reduce it to not lock up other syntactic sugars that could become ambiguous with this liberal RFC-stage setup.
One of the important concepts, structurally, is that it uses indent sensitivity (keep good form!), but one can also use end-keywords to assert and ensure structure (unlike pythons optional end-keywords which are just pre-processed and not interchangeably used.). A kind of double life guard. What you see is much more likely what you intended and also get.
The idea about allowing diversity is that different kinds of code may benefit from different choices of style, and also that different users like it differently. I'd like to get it so that you have a formatting-conf for checking in (project style), and another for checking out (your style). The ideas awoke from @technorama 's issue on elastic tabstops in #1682, and the fact that I myself have used a crude search n replace back/forth method for editing others code.
I also have a lot of RFC's prepared that I will post in the issues, once I've gotten them concise and divided enough. So that there's a base structure for initial commentry.
It could likely also work as an experimental ground for lib and core-features, that might be interesting for Crystal to merge in, and otherwise those features might drop out of Onyx instead, to maintain the long term goal of full co-compile compatibility.
And, well same thing as for Crystal goes for me, I have wood to cut for the winter, cat's, dog and lady of the house to attend to ;-)
Sorry for taking up valuable screen estate about Onyx here, @asterite, @waj, etc!!

@waj What everyone sees from me is months of frustration building.  I tried contacting @waj, @asterite, @jhass in public (issues, PR's, irc) and private.  So far @jhass has been wonderful.  He's fair, diplomatic, merges or comments quickly,  and is helpful even in responding with IDK.  With @waj and @asterite it's mostly 1 sided conversations.  Private messages, channel messages go mostly unanswered.  Emails have never been answered.
My tone was completely different months ago.

2015-07-22 10:01:53     dzv     thank you for looking but there is a bigger issue
2015-07-22 10:02:20     dzv     how can we grow the community if everything is on your shoulders?
2015-07-22 10:02:41     dzv     perhaps jhass could serve as a merge approver?
2015-07-22 10:03:07     dzv     or some other additional people?
2015-07-22 10:13:02     waj     eventually there will be more maintainers
2015-07-22 10:13:33     waj     but I think I prefer to keep control until we reach a more stable state
2015-07-22 10:14:19     dzv     there are bugfixes and other contributions i would like to make
2015-07-22 10:14:45     dzv     but i'm not going to commit myself to them if my commits won't be accepted
2015-07-22 10:14:54     dzv     and right now there's no feedback.  i have no idea if i'm wasting my time or not
2015-07-22 10:15:32     dzv     maybe there is a middle ground
2015-07-22 10:15:48     waj     if you look at the commit history you?ll see there are many PR accepted every day
2015-07-22 10:16:27     dzv     expanding community contributions from trusted members.  i'm not asking for myself to be one of them.  i'm asking if you would consider promoting some other members.  perhaps there are some active members already
2015-07-22 10:16:54     dzv     i watch the commits every day but see nothing about my own which makes me think my approach is wrong
2015-07-22 10:17:33     dzv     or that you only want bug fixes.  or secretly hate Process#spawn which solves a different problem than Process#run
2015-07-22 10:18:45     waj     no? it?s nothing like that. I?m sorry you get the wrong impression. We?re not full time commited to the project anyway. We need to work also so we can pay our bills :)
2015-07-22 10:19:22     dzv     understood.  i would like crystal to gain enough traction where i can pay my bills by writing programs in it

It's not like I'm raising a new issue.  This issue is just becoming public now because I don't see improvement (with the exception of promoting @jhass).  Adding @jhass as a contributor was not enough.  He's not empowered to make language design changes and often punts to @waj or @asterite.
If @waj and @asterite followed @jhass's public relations lead there wouldn't be a problem.

I'm closing this as there's nothing to track here.


fix: unicode escaping by replacing fastjson version

Motivation and Context

TODO

[ ] Tests or benchmark included
[ ] Documentation is changed or added on https://app.gitbook.com/
[ ] PR title must follow conventional-commit-standard

@devsergiy can you add a test that validates that the behavior is "locked in*?

You can take inspiration from

https://github.com/golang/go/blob/master/src/encoding/json/encode_test.go#L784
https://github.com/goccy/go-json/blob/master/encode_test.go#L928


Question: Is there a mechanism to schedule periodic tasks?

There is not. You could try having a task schedule the next one though - we haven't tried this but depending on your requirements it could work.


Refactor tradeparams, move events to relevant components

Hi,
Attached contained changes that should refactore our tradeparams as mentioned in the card here https://trello.com/c/wcjZI13L/656-refactor-onchange-events-in-tradeparams-moved-to-each-param-component

Coverage decreased (-0.006%) to 28.721% when pulling 630f26d117927c74d636a1589ed4c6fb2a622f29 on nuruddeensalihu:nuru/trade_params_refactor into 49338e12bef322871acfa795ffc8c4ac7f9dfcc4 on binary-com:master.

@qingweibinary Review, please?

Coverage decreased (-0.08%) to 28.652% when pulling eadac83242402180f4369951a2ca43e7fa8c008b on nuruddeensalihu:nuru/trade_params_refactor into 49338e12bef322871acfa795ffc8c4ac7f9dfcc4 on binary-com:master.

LGTM 👍

Coverage decreased (-0.3%) to 28.405% when pulling d7cb279e6387eb3a6a711c4ddaa7c1c8cab6f917 on nuruddeensalihu:nuru/trade_params_refactor into 49338e12bef322871acfa795ffc8c4ac7f9dfcc4 on binary-com:master.


Why do I get the log event "event filtering in sensu-plugin is deprecated"?

I use the slack handler (https://github.com/sensu-plugins/sensu-plugins-slack) and sometimes I get the log entry below in the sensu-server.log. When I look at the slack plugin I don't see any deprecated filtering functionality. Why do I get the error below?
{"timestamp":"2017-09-27T15:49:52.379390+0200","level":"info","message":"handler output","handler":{"command":"handler-slack.rb","type":"pipe","filters":["production_environment","state_change"],"severities":["ok","critical"],"handle_flapping":false,"handle_silenced":false,"name":"slack"},"event":{"id":"79cf548e-3ad4-49c7-9117-462ab9622793"},"output":["warning: event filtering in sensu-plugin is deprecated, see http://bit.ly/sensu-plugin\nconnection refused attempting to query the sensu api for a stash\nconnection refused attempting to query the sensu api for a stash\nconnection refused attempting to query the sensu api for a stash\nwarning: occurrence filtering in sensu-plugin is deprecated, see http://bit.ly/sensu-plugin\n"]}

See also https://github.com/sensu-plugins/sensu-plugins-slack/issues/52

@pietervogelaar the deprecated functionality is in the sensu-plugin library, which is a dependency of the slack handler that you are using. Please see https://blog.sensuapp.org/deprecating-event-filtering-in-sensu-plugin-b60c7c500be3 for the reasoning behind these messages and how to move forward. Once the slack handler and other plugins like it are updated to use a more recent version of sensu-plugin, these messages will go away.


Interactive plots no longer loading

Hi,
It appears that interactive plots are no longer loading from html files. This includes any maps stored locally and the examples within the documentation on https://datamapplot.readthedocs.io/en/latest/interactive_intro.html
The maps either fail to load all together, or get stuck on the spinning wheel. Static plots are unaffected.
I'm also not currently able to create any new interactive plots. I'm assuming something is failing within the external calls when the maps load?
Screenshot below

They are loading here, so it is hard to debug what the issue is. I have heard some people having issues with google fonts, but that shouldn't really effect html files you've already created (it should just fallback on fonts).

Okay, I've managed to have something fail to load. It seems like something has changed in the javascript ecosystem and loaders for deck.gl are no longer working. I honestly have no idea how to fix that right now, but I certainly understand that it is a major issue. I'll see what I can figure out ...

Appears to be working again for me too, thanks for looking into it

Glad to hear things are back working. I guess this is the downside of relying on CDNs for javascript. Maybe in the future I'll try to have a version that can just inline all the javascript directly into the html?


Wiki broken link

Issue Description

https://www.freecodecamp.com/wiki/
Link Wiki-Central is 404. (Guides on how to Contribute)
Browser Information

Browser Name, Version:  Chrome 51
Operating System:  Ubuntu 14.04
Mobile, Desktop, or Tablet:  Desktop

More completely:
None of the links on the main Wiki landing page to other pages within the Wiki are functional, and this includes:

https://freecodecamp.github.io/wiki/CamperBot
https://freecodecamp.github.io/wiki/Algorithm-Wiki-Template
https://freecodecamp.github.io/wiki/Wiki-Central

Also, it seems that clicking a link to the Wiki from a source outside of the FCC website (eg the URL in @Devinsuit's issue description above) results in a lack of search functionality on the landing page, and refreshing results in no change. Can anyone reproduce that, or is it already reported?

Confirmed (accessing link directly https://www.freecodecamp.com/wiki/ results in page load but no search functionality) - But yeah, it's probably a side effect of the migration (and no idea if there's a bug outstanding)

I believe #9513 may be relevant.

Hey everyone, we are moving away the wiki completely to the forum. And while that happens there will be some of the links that are broken. We request all contributors to pitch in the effort to help audit the same and make pull requests (if needed) in the codebase addressing the same.
Please feel free to follow and your comments on
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/9731


[DOCS] Documentation and Wiki Page

Is your feature request related to a problem? Please describe.
No documentation currently present.
Describe the solution you'd like
Integrated API Documentation and examples via the Wiki.
Describe alternatives you've considered
N/A
Additional context
https://amethyst-studio.github.io/k-value/index.html

Wiki as in github wiki or a external site?

It will be using the GitHub Wiki @ghostdevv. I'm working on a lot of this stuff at the moment, as I am doing #2 which is the start of this.

Oki sounds good @xCykrix

The wiki page is partially implemented. A new issue will be introduced to follow up on adding documentation regarding contributing adapters and creating custom adapters with our API.


Forge4Flow

Forge4Flow
Grant category

Developer tools / services ✅

Description
Problem statement

Audience: Developers immersed in the Flow blockchain landscape.
What's Missing?: The Flow ecosystem is buzzing with activity, but developers hit roadblocks. They're grappling with fragmented authentication processes, the need for real-time event tracking, and smoother third-party service integrations. These gaps make development slower and less intuitive than it could be.

Proposed solution
Forge4Flow is born out of an innate understanding of these pain points and aims to become a dectralized development platform, the DAO itself is formed under Wyoming's Decentralized Autonomous Organization LLC Supliment with a token and governance plan in works ensure the platform is governed by both the developers and the Flow ecosystem as a whole.

Auth4Flow: Blockchain-based authentication lacks comprehensive user verification, requiring custom solutions for advanced functionalities and role-based access control. Transitioning to a Web3 environment increases the complexity of achieving secure user access control, both within DApps and when interacting with Web2 technologies. Auth4Flow offers a simple, open-source Identity and Access Management platform that simplifies Web3 authentication. It supports various authorization schemes, including RBAC, FGAC, ReBAC, and NFT/FT gated access.

Alerts4Flow: One of the biggest advanges of the Flow Blockchain is it's ability to emmit events from within contracts, thus allowing developers to react to changes as they occur. Unfortuantley tooling in this area has not been widely developed. With Alerts4Flow developers can easily setup Event Monitors to receive alerts in realtime using Websockets or Webhooks.

Impact

Developers face challenges in creating dApps due to issues like user authentication, access control, system monitoring, and third-party integration. Forge4Flow aims to address these problems with a developer infrastructure and tooling platform.

Milestones and funding

Milestone
Deliverables
Timeline
Risks
USD proposal

0 - Beta Rollout (v0.1.0) & Docs
- Secure and stable MVP of Auth4Flow & Alerts4Flow.  - Comprehensive API documentation.  - Detailed getting started guide for new users.
2-4 weeks
- Security vulnerabilities in MVP.  - Incomplete documentation leading to misconfiguration.  - API instability affecting user experience.
$5,000

1 - DAO Launch
- Initiate DAO ensuring decentralized control of funding.  - Introduce Forge4Flow Token with a 5-year release plan, focusing on developer grants and community events.  - Release the DAO Whitepaper (draft link).  - Air-drop 50 million tokens to key developers and launch community engagement DApp.
2-4 weeks
- Regulatory compliance for DAO and Token launch.  - Lower than expected community engagement or adoption.  - Technical issues with token distribution.
$5,000

2 - SDK Debut
- Release beta versions of server and client SDKs.  - Ensure compatibility for platforms like JavaScript, NodeJS, React, NextJS, Swift, Kotlin, Go.  - Detailed documentation for each SDK.
2-4 weeks
- Incompatibility issues with different platforms.  - SDKs not meeting developer expectations.  - Delays in hiring the Kotlin developer.
$10,000

3 - Forge4Flow Manager
- Development of Docker/Container-based management solution.  - Integrated Admin Dashboard for easy management.  - Features to manage instances, users, groups, events, etc.  - Detailed user guide for the manager.
3-5 weeks
- Integration and stability issues with Docker.  - UX/UI challenges with Admin Dashboard.  - Delays or increased costs in hiring outside resources for the dashboard.
$15,000

4 - Walletless Magic
- Develop walletless onboarding solutions.  - Incorporate account linking functions.  - Documentation on best practices for secure integrations.
4-6 weeks
- Security concerns over private key management.  - Technical challenges with walletless integration.  - Usability issues affecting user adoption.
$15,000

5 - Security Deep Dive
- Comprehensive pentesting of all platform components.  - External security audits.  - Identification and swift resolution of discovered vulnerabilities.  - Release of a detailed security report.
4-6 weeks
- Discovery of critical vulnerabilities.  - Delays or higher costs associated with resolving discovered issues.  - Challenges in securing third-party integrations.
$15,000

6 - Final Polish & Tweaks (v1.0)
- Gather and analyze user feedback for improvements.  - Resolve identified issues and bugs.  - Optimize the platform for performance and user experience.  - Release the polished version 1.0 to the community.
4-6 weeks
- Overlooked issues emerging post-launch.  - Delays in implementing user feedback.  - Potential performance or stability issues as platform scales.
$15,000

Total funds on the table: $80,000
Team Snapshots

Name
Role
Background
Reach Out

Brian Pistone (BoiseITGuru)
Founder/Full-Stack Developer
IT Guru
<EMAIL_ADDRESS>

Jared Milne
Frontend Developer
--
<EMAIL_ADDRESS>

TBD
Kotlin Developer
--
--

Hello, just a heads up I have added an additional team member to the grant request.
We have also setup a more detailed project management board available at https://projects.forge4flow.com/projects/forge4flow-core/work_packages?query_id=30

Hello,
I have made some changes to the grant proposal to reflect a change in direction we are taking with event monitoring. These changes replaces Alerts4Flow with Functions4Flow.
Forge4Flow
Grant category

Developer tools / services ✅

Description
Problem statement

Audience: Developers immersed in the Flow blockchain landscape.
What's Missing?: Despite the vibrant activity within the Flow ecosystem, developers face significant hurdles. These include fragmented authentication processes, a lack of efficient, event-driven architecture, and the need for more streamlined integrations with third-party services. These issues collectively slow down and complicate dApp development.

Proposed solution
Forge4Flow is born out of an innate understanding of these pain points and aims to become a dectralized development platform, the DAO itself is formed under Wyoming's Decentralized Autonomous Organization LLC Supliment with a token and governance plan in works ensure the platform is governed by both the developers and the Flow ecosystem as a whole.

Auth4Flow: Blockchain-based authentication lacks comprehensive user verification, requiring custom solutions for advanced functionalities and role-based access control. Transitioning to a Web3 environment increases the complexity of achieving secure user access control, both within DApps and when interacting with Web2 technologies. Auth4Flow offers a simple, open-source Identity and Access Management platform that simplifies Web3 authentication. It supports various authorization schemes, including RBAC, FGAC, ReBAC, and NFT/FT gated access.

Functions4Flow (evolved from Alerts4Flow): Building upon the foundation of Alerts4Flow, Functions4Flow offers a dynamic serverless platform for the Flow blockchain. It enables developers to deploy NodeJS and Go functions triggered by both time-based schedules or real-time Flow blockchain events. This system facilitates a wide array of dApp functionalities, from automated tasks to responsive blockchain interactions. As we expand, more programming languages will be supported, further establishing Functions4Flow as a versatile tool for dApp development.

Flexible Deployment

Forge4Flow Core: The central component, comprising Auth4Flow and Functions4Flow, is engineered for flexible deployment. It can be deployed efficiently on a single node for smaller applications or scaled up to a Kubernetes cluster for enterprise-level solutions. This flexibility ensures that Forge4Flow can cater to a wide range of use cases and deployment scenarios, from individual developers to large organizations.

Impact

Forge4Flow is poised to revolutionize the Flow blockchain development landscape by offering essential tools and infrastructure. It simplifies user authentication, enables real-time event handling, and streamlines the deployment of serverless functions, making dApp development more efficient and user-friendly.

Milestones and funding

Milestone
Deliverables
Timeline
Risks
USD proposal

0 - Beta Rollout (v0.1.0) & Docs
- Secure and stable MVP of Auth4Flow & Alerts4Flow.  - Comprehensive API documentation.  - Detailed getting started guide for new users.
2-4 weeks
- Security vulnerabilities in MVP.  - Incomplete documentation leading to misconfiguration.  - API instability affecting user experience.
$5,000

1 - DAO Launch
- Initiate DAO ensuring decentralized control of funding.  - Introduce Forge4Flow Token with a 5-year release plan, focusing on developer grants and community events.  - Release the DAO Whitepaper (draft link).  - Air-drop 50 million tokens to key developers and launch community engagement DApp.
2-4 weeks
- Regulatory compliance for DAO and Token launch.  - Lower than expected community engagement or adoption.  - Technical issues with token distribution.
$5,000

2 - SDK Debut
- Release beta versions of server and client SDKs.  - Ensure compatibility for platforms like JavaScript, NodeJS, React, NextJS, Swift, Kotlin, Go.  - Detailed documentation for each SDK.
2-4 weeks
- Incompatibility issues with different platforms.  - SDKs not meeting developer expectations.  - Delays in hiring the Kotlin developer.
$10,000

3 - Forge4Flow Manager & Functions4Flow Launch
- Development and launch of Docker/Container-based Forge4Flow Manager.  - Integrated Admin Dashboard for managing instances, users, groups, events, etc., and deploying Functions4Flow.  - Release of Functions4Flow as part of the Manager, supporting both time-based and event-driven functions.  - Detailed user guides for the Manager and Functions4Flow.
3-5 weeks
- Integration challenges with Docker.  - UX/UI complexities in the Admin Dashboard.  - Ensuring stability and functionality of Functions4Flow within the Manager.
$15,000

4 - Walletless Magic
- Develop walletless onboarding solutions.  - Incorporate account linking functions.  - Documentation on best practices for secure integrations.
4-6 weeks
- Security concerns over private key management.  - Technical challenges with walletless integration.  - Usability issues affecting user adoption.
$15,000

5 - Security Deep Dive
- Comprehensive pentesting of all platform components.  - External security audits.  - Identification and swift resolution of discovered vulnerabilities.  - Release of a detailed security report.
4-6 weeks
- Discovery of critical vulnerabilities.  - Delays or higher costs associated with resolving discovered issues.  - Challenges in securing third-party integrations.
$15,000

6 - Final Polish & Tweaks (v1.0)
- Gather and analyze user feedback for improvements.  - Resolve identified issues and bugs.  - Optimize the platform for performance and user experience.  - Release the polished version 1.0 to the community.
4-6 weeks
- Overlooked issues emerging post-launch.  - Delays in implementing user feedback.  - Potential performance or stability issues as platform scales.
$15,000

Total funds on the table: $80,000
Team Snapshots

Name
Role
Background
Reach Out

Brian Pistone (BoiseITGuru)
Founder/Full-Stack Developer
IT Guru
<EMAIL_ADDRESS>

Jared Milne
Frontend Developer
--
<EMAIL_ADDRESS>

TBD
Kotlin Developer
--
--

Gave separate agreement.


Binding for special named properties

There are a few special properties in Javascript which have proper names such as this, super, and new.target. We have historically not done name binding for these properties instead hardcoding locations for them to live in the ByteCodeGenerator and loading from those locations when we emit specially-crafted parse nodes referring to those properties.
Originally we simply tracked a register where we stored the this value during the function prologue but over time the set of things we needed to keep track of has drastically increased. First came lexical capture of this for lambda and then super and the special handling for derived class constructor calls to super(). At this point juggling all of the state to specially handle these values is becoming a problem and hindering further development of frontend optimizations.
Instead of constructing special parse nodes for each of these special names, we now create ordinary-ish name parse nodes and push references to the well-known pids corresponding to those names. This acts basically exactly the same as how we handle references to ordinary identifiers. We use values for these pids which are not valid identifiers for Javascript code such that user code cannot declare them.
We create symbols for these special names in a slightly-special way. Ordinary name binding works by binding references to names upwards to their var decls. Special named properties like this do not have var decls, though. We fix this by adding var decls for special named properties to functions when they contain references to the names. When we are finished parsing a function, we check to see if it contains references to each special name. If it does, we create a var decl for the special name in the parameter scope and bind those references to it. The logic to do this is in CreateSpecialSymbolDeclarations().
Global function never sets a binding for super or new.target but it does create a binding for this which will load the global this value. This binding is not stored in a root field for reasons explained below.
One key of this design is that lambda functions do not bind any of the special names. In this way, they are able to automatically capture the bindings from their parent. There is one caveat here which is the case of lambda with global function as the parent (global lambda). In this case, the lambda should capture the value of this by ordinary capture but it cannot because the global scope is not an object. We don't need to worry about the other special symbol capture here because super and new.target are invalid syntax at global scope. In this case, we create a binding for this in the global lambda and load the root this object into it.
Another benefit of doing binding of these special names is that eval doesn't have to do special work to capture these values, either. Direct eval doesn't need to create bindings for any of these special names and doesn't need to perform a stack walk, either. It can just do a scoped property lookup to fetch the outer bindings. There is a caveat here, as well, for the global this binding. If a direct eval captures global this, the scoped property lookup will not find any value for this in the scope chain. Instead we'll try to look in the root object but there can't be a this binding there because it would be observable, would be a reference to itself essentially, and would cause other problems. So instead, we detect this case when the scoped property lookup for the this property id fails and we load and return the global this value directly. With these improvements, eval no longer needs to load the this value via the first argument.
Indirect eval gets a binding for this which loads the global this value. It otherwise works the same as direct eval.
To keep track of the additional information we need to know which names are special, which nodes contain references to additional special names, etc we add three new parse nodes.

PnSpecialName is a subclass of PnPid and is used as a holder for flags to indicate which special name this parse node represents. This is very similar to a regular PnPid and only needs to exist because we don't want to bloat PnPid itself with extra flags. There will also be more of these special names in the future. All PnSpecialName nodes have their opcode field set to knopName to avoid replacing all cases of knopName in conditionals with a boolean or of the two. We use a flag on ParseNode (ParseNode::isSpecialName) to indicate that the node has an sxSpecialName field.

PnSuperReference is a subclass of PnBin and is used to indicate a super reference via dot access (knopDot) or index access (knopIndex). We need to have a reference to this at every super reference site because super references maintain the this binding through their calls. We don't have a flag on ParseNode or PnBin to indicate that the node has an sxSuperReference field. Instead we determine this by looking at the pnode1 property and checking to see if it is a special name node for the super name.

PnSuperCall is a subclass of PnCall and is used to indicate a call to super() in the context of a derived class constructor. The super call itself will need to use both the this and new.target values so we stash them on this parse node. All PnSuperCall nodes have their opcode field set to knopCall so as to avoid needing to change all the conditional statements currently checking for knopCall to include both (ie: if(nop == knopCall) => if(nop == knopCall || nop == knopSuperCall)). We use a flag on PnCall (PnCall::isSuperCall) to indicate the parse node has the sxSuperCall field.

In ByteCodeGenerator we treat these special symbols pretty much like ordinary symbols. We do store references to them directly in FuncInfo because we sometimes want to access them directly instead of during regular symbol enumeration. We collect the special symbols in AddVarsToScope similar to what we do for arguments.
There are a couple of pieces which are special we handle while emitting byte code. We do not check the special symbols for redeclarations. It should not be possible for them to be redeclared. Similarly, we skip initializing these special symbols via LdUndef because we will always immediately load a value in LoadAllConstants when the symbol exists. Because of that, we always assign a register for these special symbols. The pattern they have is to load a value into that register (via LdThis, LdNewTarget, LdHomeObj, etc) and then immediately store to the prop which will put the value into a scope slot if there is one.
The super() in a derived class constructor has a big impact on how these special symbols work. Because of super calls we need to have a TDZ for this in derived class constructors. This can't work like an ordinary block scope binding so we have a couple of concessions. When we emit a knopName node for the special name this, we'll emit a ChkUndecl if the symbol is marked as needing a declaration (we set this in the parser when this is bound in a derived class constructor) or if this was loaded from a scoped property lookup (we don't know where the this binding came from in that case - could have been a derived class constructor). In other cases we can skip this check because we know this was bound to some value. The other special work for this as part of super() has to do with loading the this value to make sure it has not already been assigned and assigning the result of super() back to this. When we load this to check that it is undeclared, this property load will throw a ReferenceError if it is, in fact, undecl. But we want to find out if the value is undeclared here, not throw if it is. This is accomplished via a flag added to EmitPropLoad named skipUseBeforeDeclarationCheck. When we pass this flag, we skip throwing a ReferenceError if the value is undecl. It is only used for this load of this in super(). The opposite is a flag added to EmitPropStore named skipUseBeforeDeclarationCheck. EmitPropStore will throw a ReferenceError at runtime if we try to store to a property which has an undecl value. That's exactly what we want to do when we assign to this as part of super(), though.
This change also makes a rough attempt to clean up all the now unused code we previously needed to keep around to manage the special values. There is probably a lot more code which can be safely removed in future changes.

Huge but important change. It might take me a while to digest this. :)


Showing version of CS IP used

Should there be an attribute in METS root element defining which version of the E-ARK specification the IP conforms to?

Version will be possible to see through the naming and directory use.

Is it possible to get the version into the folder path to the profile @carlwilson durin g the publication process so this is achieved through CSIP6?
PROFILE="https://earkcsip.dilcis.eu/profile/E-ARK-CSIP.xml"


Porting to ROS2

Hi, @koide3
Thank you for this awesome framework!
I would like to interest do you have any thoughts about porting this project to ROS2?
Best, Daniil.

Maybe I will not, because I'm developing a new SLAM framework and reducing the effort to maintain this package. But, if there are many requests, I'll consider porting to ROS2.

Thank you for your response! May consider you already have one request 😁

So this makes people curious! What's the new SLAM framework?

ROS2 version is expected!!

ROS2 version is expected!!

Really? Where is a proof? 🙂


List concatenation not working

Of these three functions which concatenate two lists, only the third one works properly:
def concat1():
    a = ['a', 'b']
    b = ['c', 'd']
    return a + b

def concat2():
    a = ['a', 'b']
    b = ['c', 'd']
    return [*a, *b]

def concat3():
    a = ['a', 'b']
    b = ['c', 'd']
    r = []
    r.extend(a)
    r.extend(b)
    return r

The first returns a string, 'a,bc,d', and the second returns a list containing two nested lists, [ [ 'a', 'b' ], [ 'c', 'd' ] ]
I have tested this in the latest PyPI version, 3.9.0, which is also the latest Git master revision at the time of writing this.

Related: [1] * 4 does not produce [1, 1, 1, 1] as expected

Are these not working even with operator overloads enabled using the opov pragma?

Thanks! This fixes all cases except for [*a, *b], which still produces [['a', 'b'], ['c', 'd']].
IMO this feature should be made more prominent in the docs, given that it silently produces incorrect behaviour. Even more helpful would be to emit a warning when it is obvious that non-numeric objects are being added (in my case it I was adding list literals, which should be easy to detect).


[RDBMS]Remove the preview tag for server key and ad admin commands for Postgres and MySql

Description
Remove the preview tag for server key and ad admin commands for Postgres and MySql
Testing Guide
History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

OSSRDBMS

OSSRDBMS

Hi @shinilm, I changed your PR title to the right module name, which could be used to generate history notes.

Hi @shinilm, I changed your PR title to the right module name, which could be used to generate history notes.

Thanks a lot Zunli Hu for the approval.  Please help merge this PR
Thanks
Shinil
From: Zunli Hu<EMAIL_ADDRESS>Sent: Monday, January 4, 2021 6:15 PM
To: Azure/azure-cli<EMAIL_ADDRESS>Cc: Shinil Mannadath<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-cli] [RDBMS]Remove the preview tag for server key and ad admin commands for Postgres and MySql (#16412)
Hi @shinilmhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshinilm&data=04|01|shinim%40microsoft.com|9fa257205131431ca8c408d8b11fbd32|72f988bf86f141af91ab2d7cd011db47|1|0|637454097218640066|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=e7z2C4GYPpYyydPVayY5Qa8ij081tuyWy9KZQsxiuI8%3D&reserved=0, I changed your PR title to the right module name, which could be used to generate history notes.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fpull%2F16412%23issuecomment-754340512&data=04|01|shinim%40microsoft.com|9fa257205131431ca8c408d8b11fbd32|72f988bf86f141af91ab2d7cd011db47|1|0|637454097218645042|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=V%2BrOoCXmHjqxmPHKEFG9NITLUFquep4Ct5FuUydL7eg%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKUG6JTEHUEYYBXEONMD543SYJY3FANCNFSM4VQA2LDA&data=04|01|shinim%40microsoft.com|9fa257205131431ca8c408d8b11fbd32|72f988bf86f141af91ab2d7cd011db47|1|0|637454097218650021|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=LSY0FR644hnFSDqCxgrf3mU66O55FOytRGHk5H8VCtI%3D&reserved=0.

Thanks a lot Zunli Hu for the approval.  Please help merge this PR
Thanks
Shinil
From: Zunli Hu<EMAIL_ADDRESS>Sent: Monday, January 4, 2021 6:15 PM
To: Azure/azure-cli<EMAIL_ADDRESS>Cc: Shinil Mannadath<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-cli] [RDBMS]Remove the preview tag for server key and ad admin commands for Postgres and MySql (#16412)
Hi @shinilmhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshinilm&data=04|01|shinim%40microsoft.com|9fa257205131431ca8c408d8b11fbd32|72f988bf86f141af91ab2d7cd011db47|1|0|637454097218640066|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=e7z2C4GYPpYyydPVayY5Qa8ij081tuyWy9KZQsxiuI8%3D&reserved=0, I changed your PR title to the right module name, which could be used to generate history notes.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fpull%2F16412%23issuecomment-754340512&data=04|01|shinim%40microsoft.com|9fa257205131431ca8c408d8b11fbd32|72f988bf86f141af91ab2d7cd011db47|1|0|637454097218645042|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=V%2BrOoCXmHjqxmPHKEFG9NITLUFquep4Ct5FuUydL7eg%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKUG6JTEHUEYYBXEONMD543SYJY3FANCNFSM4VQA2LDA&data=04|01|shinim%40microsoft.com|9fa257205131431ca8c408d8b11fbd32|72f988bf86f141af91ab2d7cd011db47|1|0|637454097218650021|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=LSY0FR644hnFSDqCxgrf3mU66O55FOytRGHk5H8VCtI%3D&reserved=0.


Fix efficient-nft-pab for seabug

Use untyped minting policy

Lets drop this PR and merge it as part of #363 363


Localization support

I am planning to translate the UI strings (in SmartRenameUI\SmartRenameUI.rc) into Russian for personal use.
Relatedly, wanted to know if the localization support is planned — it would be great to have an easily localizable list of strings for other people to contribute translations.

If there is interest I would try to add localization support.

I am planning to translate the UI strings (in SmartRenameUI\SmartRenameUI.rc) into Russian for personal use.
Relatedly, wanted to know if the localization support is planned — it would be great to have an easily localizable list of strings for other people to contribute translations.


Golang: Make usage of contexts consistent

Remove the special method client.AddChainWithContext and make the following methods
take a x/net/context.Context as their first parameter:

GetSTH
AddPreChain
AddChain
AddJSON

Fixes #1326.

LGTM; Paul, are you OK with the API change?


Improve Unicode support in Zip archives

Very new Unicode characters don't get along with Simple Comic.
For example, I have a zipped archive (in UTF-8) with SPLASHING SWEAT SYMBOL Unicode: U+1F4A6 (U+D83D U+DCA6), UTF-8: F0 9F 92 A6 (GitHub doesn't want to let me put the actual symbol in) in the file names. Simple Comic doesn't recognize these and asks me for the encoding. Then in the encoding chooser UTF-8 isn't an option. I can unzip the file with zip or StuffIt and the files are correctly named.
When I open a plain image or directory it seems to work ok, regardless of how the file is named.
What I'd like to see is better unicode detection for Zip and other archives (I can only confirm this bug with Zip archives using UTF-8 encoding).

Not sure how hard it will be to remove Universal Detector completely but I want to give it a shot.


Bugfix/#ab26899 fix form name

This removes the required field for Form Name

The request needs to go from the branch to dev


Remove requirement for ParticipantStatus body for Compensate/Complete callbacks

As per Gitter discussion distinctions by HTTP status codes are preferred, so 200 HTTP status is enough and ParticipantStatus body is redundant.

this was superseded by #299. Closing.


Windows: v1.11.1 can't be launched saying .NET 4.6.2 isn't installed

Storage Explorer Version:  v1.11.1
Build Number:  I can't go to Help menu
Platform/OS: Windows 10
Architecture: I can't go to Help menu
Regression From:  It was working in previous version, but I can't get the version number now
Bug Description

I'm seeing below dialog after upgrading to v1.11.1:

I'm pretty sure that my Windows 10 has both latest .NET 4.6.2 & 4.7.2 (runtime + Dev Pack) installed.
Steps to Reproduce

N/A
Expected Experience

It's supposed to be launched.
Actual Experience

I can't launched the tool any longer.
Additional Context

Just updated, having the same issue. Ive got .net framework 4.8 installed on Win 10. Downgrade to 1.10.0 and it works again.

@LucGosso How to get an older version? I have no downgrade option and I can't find a link to an older version from the site https://azure.microsoft.com/en-us/features/storage-explorer/

Hi everyone. To help us diagnose this issue, we need some logs...to get those logs please do the following....

In file explorer navigate to C:\Users\<your username>\AppData\Local\Temp\servicehub
Delete the logs folder
Open PowerShell
cd 'C:\Program Files (x86)\Microsoft Azure Storage Explorer\' (if you installed elsewhere, then you'll need to modify the path to account for that)
$env:SERVICEHUBTRACELEVEL="all"
.\StorageExplorer.exe
After you get the error, go back to C:\Users\<your username>\AppData\Local\Temp\servicehub, where you should see the logs folder again
Zip that folder up and attach it to this issue

Thanks!

Attempted to get you some logs, but 1.11.1 is now working for me. No logs to provide, but sharing my experience:
I had 1.10 before, and when I ran it asked me to update, which I did. It updated to 1.11.1 which then caused the issue from this thread.
I fully uninstalled the application, then installed 1.11.0 so that I could go about my current task.
In response to the request for logs, I then downloaded latest which is currently 1.11.1, ran, and now it's working fine. Closed and re-open to check, but still fine.
No OS restarts during any steps above.

Hmmm. That's very odd. We did notice an issue that doing a non-clean install (which we normally do) would result in the error you saw. But for that reason, we made the 1.11.1 update a clean install. I'll go ahead and do exactly as you did though. Maybe it will revealed something we missed...

Well, doing that same upgrade path didn't cause me any issues.
I'll say that for anyone else facing this problem please:

get the log files (if you're willing)
you can try uinstalling and then reinstalling from https://storageexplorer.com , as doing that fresh unblocked Monkeyfish

I just upgraded and am getting the same error message despite having .NET Framework 4.7 and 4.71 installed. Attaching log files.
StorageServiceClient-24012-HqvHe5-1.zip

@tsulli , can you try uninstalling and then reinstalling from https://storageexplorer.com ? I think that will fix the issue based on the error message. Also, any idea what version of Storage Explorer you were on before you upgraded?

Uninstalling and reinstalling did solve the issue for me. I think I was using 1.7.0 but I'm not 100% sure. Thanks for looking into this!

No problem. Having the upgrade process be solid is very important to us. I'll try doing an upgrade from 1.7.0 and see if I can reproduce.
 It should be this:

I had this problem also but I re-installed before I got to the request above (sorry).  However, when I look in "C:\Program Files (x86)\Microsoft Azure Storage Explorer" now, there are NO files.  I suspect that this is because I installed it to C:\Apps (and possibly to the same location the previous time).  Maybe that additional piece of information (installing to a location other than the default) is helpful.

No worries that you didn't see the request. My first priority is making sure none of you are blocked. :)

@MRayermannMSFT Below are my logs:
AzureStorageExplorerLogs.zip
I'll try to reinstall it to see if it can be worked around.

A clean re-installation has addressed the issue, I'm unblocked anyway.

@Zossin , yep. Looks the same as tsulli's logs. Glad you became unblocked. @FDFessler , how did you accomplish installing in C:\apps? I just noticed our installer doesn't let you customize install location, so are you merely copying the files manually?

I was prompted to where I wanted to install it.  See screenshot below:
[image: image.png]
On Tue, Nov 26, 2019 at 3:59 PM Matthew Rayermann<EMAIL_ADDRESS>wrote:

@Zossin https://github.com/Zossin , yep. Looks the same as tsulli's
logs. Glad you became unblocked. @FDFessler https://github.com/FDFessler
, how did you accomplish installing in C:\apps? I just noticed our
installer doesn't let you customize install location, so are you merely
copying the files manually?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/AzureStorageExplorer/issues/2321?email_source=notifications&email_token=AGMP5U6TF3HP2E5GXTZYIJDQVWE4FA5CNFSM4JREBLV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFHNMQQ#issuecomment-558814786,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMP5U4VZ45HYRRYBVHGAPLQVWE4FANCNFSM4JREBLVQ
.

Turns our a reg key is written when you install that saves the install location. Once I uninstalled and then restarted my machine, I was able to choose a different location (C:\apps). Though even doing that, I still can't repro the clean install failing.

I did upgrade to Win 10 1909 in between so don't know if that made a
difference.  Also, I think I upgraded WASE from 1.3.1 instead of 1.8.1
which I mentioned in my post but TBH I don't actually remember (sorry)!
Also, I don't know if it has anything to do with it saying it's upgrading
to 1.10.1 but when it's all done it's 1.11.1  -- just something I noticed
(and I think other did also).  If I come across it again I will try to
capture the information you requested.  Have a HAPPY THANKSGIVING! 🦃🍰
---  Freeman
On Wed, Nov 27, 2019 at 12:54 PM Matthew Rayermann<EMAIL_ADDRESS>wrote:

Turns our a reg key is written when you install that saves the install
location. Once I uninstalled and then restarted my machine, I was able to
choose a different location (C:\apps). Though even doing that, I still
can't repro the clean install failing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/AzureStorageExplorer/issues/2321?email_source=notifications&email_token=AGMP5UZ7TVIPKYM4A3K55XLQV2X7DA5CNFSM4JREBLV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFKJOOY#issuecomment-559191867,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMP5U4UNISNEEENGPKTQMTQV2X7DANCNFSM4JREBLVQ
.

@FDFessler your comment just made me understand what the issue is!!! Thank you!

Ok, the issue was on our end. No one should encounter this problem now. I'll leave this open for a bit though just incase anyone does though...

OK!  Glad I could help! :-)

Confirming installing 1.11.1 worked for me now.
Regards

Given no new reports since yesterday, I'm going to go ahead and close this. Thanks everyone.

This is NOT fixed!

Storage Explorer, on the latest version, is just utterly broken.  This is a DOA release and there is no fix.
Environment; Windows server 2016

Downgraded to 1.10.0 to fix the issue. 1.11.1 is DOA

Hey, BAD NEWS ... it IS broken again.  The interesting thing is this is the
one that was FIXED after the uninstall and reinstall!!
Do you want me to go through the trouble-shooting steps you outlined before?
---  Freeman
On Tue, Dec 3, 2019 at 6:13 PM Matthew Rayermann<EMAIL_ADDRESS>wrote:

Closed #2321
https://github.com/microsoft/AzureStorageExplorer/issues/2321.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/AzureStorageExplorer/issues/2321?email_source=notifications&email_token=AGMP5U7HIXCWU275FW5X3UTQW3RZHA5CNFSM4JREBLV2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVH7EBAY#event-2852012163,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMP5U72QOJZWASU6RVYA6DQW3RZHANCNFSM4JREBLVQ
.

Yes, if you could go through the steps again that'd be fantastic. I'm assuming it is exactly the same error message yes?

Yes, it is.  I'm not in the office until 2020 but I may remote in to get
that information for you.  In the meantime ... have a very *MERRY CHRISTMAS
*and HAPPY NEW YEAR!
On Tue, Dec 17, 2019 at 4:52 PM Matthew Rayermann<EMAIL_ADDRESS>wrote:

Yes, if you could go through the steps again that'd be fantastic. I'm
assuming it is exactly the same error message yes?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/AzureStorageExplorer/issues/2321?email_source=notifications&email_token=AGMP5U2BRSOW3GWV3FNVYCTQZFCZFA5CNFSM4JREBLV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHECODQ#issuecomment-566765326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMP5UYT3LMZF35L3RBTFF3QZFCZFANCNFSM4JREBLVQ
.

I got this error after updating to version 1.11.2
Shutting down the storage emulator, quitting the emulator and explorer and relaunching them solved the problem for me. Hope it can help some of you.


Fixed yargs non-hyphenated options

The problem can be found by running npm run tasks.list. This commit fixes the exception that results

Excellent thank you @smac89 👍


Update README

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (63c24ba) 64.37% compared to head (07e5965) 64.37%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #378   +/-   ##
=======================================
  Coverage   64.37%   64.37%
=======================================
  Files           5        5
  Lines         160      160
  Branches       35       35
=======================================
  Hits          103      103
  Misses         52       52
  Partials        5        5

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


How to refit model parameters in the Cpp runtime (Executor) or activate In-flight batching in the Python runtime (builder.Engine)?

I am using TensorRT-LLM in version 0.12.0 with the following setups:

Build a TensorRT-LLM engine using the engine = build(model, build_config, return_build_config) function in the builder.py file. Save the Engine to the disk via engine.save()
Instantiate a ModelRunnerCpp class via: decoder = ModelRunnerCpp.from_dir(engine_dir, rank = model_parallel_rank)

Now, the from_dir() function will create a Cpp runtime via
    executor = trtllm.Executor(
        engine_dir,
        trtllm.ModelType.DECODER_ONLY,
        trtllm_config)

However, the Executor is not compatible with the refitter functionality from TensorRT. As far as I am concerned, it seems that online refitting is only supported by the Python runtime and the in-flight batching feature is only supported by the Cpp runtime. I am writing this issue to confirm whether it is possible to enable both online refitting and IFB with current version of TRTLLM?
For further clarification, online refitting refers to the process to update the model parameters in the TRTLLM engine by passing weight dict in the memory directly without serializing the whole model and offloading the engine to the disk. (Just in case I am using the wrong wording.)
Much thanks for your help!

Hi @hello-11 ,
could you try to update weights after building the engine, but before running the C++ runtime:
trtllm-refit --checkpoint_dir <checkpoint_dir> --engine_dir <refittable_engine> --output_dir <output_new_engine>
Please, refer to docs for more info: https://github.com/NVIDIA/TensorRT-LLM/tree/main/examples/sample_weight_stripping#engine-refitter.
I'll close the issue, but feel free to reopen, if you have more questions.

🤔 It seems that I do not have the permission to reopen this Issue. Not sure whether this issue is still under tracking

Hi @TranSirius ,
refitting in the C++ runtime directly in device memory without saving on disk is currently not supported. You can try to add logic manually, but I am not 100% sure about the feasibility and applicability for your use-case. You can check how the onnx parser refit works in https://github.com/onnx/onnx-tensorrt/blob/main/ModelRefitter.cpp
Particularly interesting functions are getRefittableWeights, setNamedWeights. Refer to the development guide for documentation https://docs.nvidia.com/deeplearning/tensorrt/developer-guide/index.html#refitting-engine-c

Hi @nekorobov ,
That works for me! Much appreciate your help!
Best regards


Short git diff behavior changed, no clean way to undo

Describe the bug
A clear and concise description of what the bug is.
Commit 0e7b4e60a846af1d4487ebe1218f8e07fffaa89b sets $LESS, and to a value that changes git behavior in an annoying way: short diff etc output now stops in the pager and needs user to press q, even when a pager is not needed. After exiting the pager, the output is no longer visible when typing the next shell command.
environment.variables does not seem to provide a mechanism to unset this annoying default. All I can do is read git's documentation for what it uses for $LESS when not set, and duplicate that in my configuration.
Many people using git on the command line won't even know what happened, and will simply have a worse git experience.
Steps To Reproduce
Make a small change in a git repo, run git diff. NixOS unstable (21.11) will pause in less waiting for human input. After less exits the diff will no longer be visible.
Expected behavior
What NixOS 21.05 did: git diff outputs the short diff, and the shell prompt returns with the diff visible.
Notify maintainers
@heisenberg33
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

system: "x86_64-linux"
host os: Linux 5.14.5, NixOS, 21.11 (Porcupine)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.15
channels(root): "nixos-21.11pre317242.bc9b956714e"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

It may be fixed by #139988


ARM action support

Not a bug, but if you run on selfhost runner, and using arm cpu, than you will get this error

because default, action will download x64 version of packsquash, it will be great if this action can work on arm system!

This is an oversight, as we didn't think about the possibility of this action being executed under a GitHub Actions runner in an architecture other than x64. And PackSquash already supports the ARM64 architecture, so there is no real reason for the action to not bother checking on what architecture it is running on to download the proper executable.
This check can be easily done via the uname -m command, which is defined by POSIX to return the system "hardware type". Linux implementation of the underlying syscalls indeed returns the architecture codename, which is aarch64 for the supported PackSquash ARM64 port, and x86_64 for x64.
Thanks for reporting this issue!


eventing sources namespace

https://github.com/knative/eventing-sources/blob/master/config/default/kustomization.yaml#L2
What do people feel about changing the namespace to knative-eventing-sources ?
Not sure if eventing-sources-system is a good choice

Thx!


Update Media (big).ini to fix scaling issues

Fixed some elements not moving in accordance with changes in scale, which resulted in the track info and progress bar moving towards (and eventually overlapping) the album art and playback controls on scales higher than 1 and moving away from them on scales lower than 1.

Looks good, thanks for your help :)


Allow optional command attributes

One example:
In case we want to retire security codes in the TLC SXL, we would make the attributes optional, to make the transition easier.

Note: for statuses you choose which attributes you want.

Yes, for some attributes in commands sometimes also, it could be very interesting to be able to set some as "optional" !
For the "incomplete commands" error, it would just means that only "required" ones are missing (could also concern some optional ones if required in the context. depending of explanations in the SXL).

Right. The most straightforward is the ability to mark each attribute as optional.
This would not cover cases where certain combinations are allowed. To handle that we would need a json schema or similar systems, but for now I think that might be overkill.

To be backward compatible, the core spec should state that attributes are required unless otherwise stated.

Once this change is implemented in core, we should go through the TLC SXL as mark relevant attributes as optional.

Task for the core WG:
Describe in the core spec that command attributes can be marked as optional in SXLs.

PR: https://github.com/rsmp-nordic/rsmp_core/pull/181

Follow up tasks

ability to mark command request arguments as optional in SXL yaml sources (schema repo)
consider optional flag when we generate json schema and validate
show optional flag in documentation
go through the TLC sxl and mark relevant arguments as optional


Superfluous response.WriteHeader

Hello everyone,
I recently downloaded and installed version v8.0.0 Clustering using the provided binaries instead of building them from source.
After installation, I can see that the deny rules are reflected in the application's firewall state. I am able to register a user and successfully authenticate.

However, my issue is that the authenticated user can only access the VPN server, and not any other resources. Upon checking the logs, I found the following errors:
2024/09/25 11:27:17 http: superfluous response.WriteHeader call from github.com/NHAS/wag/internal/router.(*Challenger).WS (session_manager.go:157) 2024/09/25 11:27:21 websocket origin does not equal expected value: "http://<IP_ADDRESS>:445" != "" 2024/09/25 11:27:21 pablo_deny <IP_ADDRESS> failed to create websocket challenger: websocket: request origin not allowed by Upgrader.CheckOrigin 2024/09/25 11:27:21 http: superfluous response.WriteHeader call from github.com/NHAS/wag/internal/router.(*Challenger).WS (session_manager.go:157) {"level":"info","ts":"2024-09-25T11:27:24.409979+0200","caller":"traceutil/trace.go:171","msg":"trace[755734487] put","detail":"{key:wag/node/229e0fb671e145bf/ping; req_size:65; response_revision:32151; }","duration":"249.360221ms","start":"2024-09-25T11:27:24.160602+0200","end":"2024-09-25T11:27:24.409962+0200","steps":["trace[755734487] 'process raft request'  (duration: 249.278958ms)"],"step_count":1} 2024/09/25 11:27:25 websocket origin does not equal expected value: "http://<IP_ADDRESS>:445" != "" 2024/09/25 11:27:25 pablo_deny <IP_ADDRESS> failed to create websocket challenger: websocket: request origin not allowed by Upgrader.CheckOrigin 2024/09/25 11:27:25 http: superfluous response.WriteHeader call from github.com/NHAS/wag/internal/router.(*Challenger).WS (session_manager.go:157)
Could you help me with this error? Is it that I'm configuring it incorrectly, or could it be a bug?
Thanks in advance for your help!

Howdy, that looks like you haven't sent the domain url properly.
It's checking the origin of the web socket verifier request (which effectively allows you to change networks and not have to re-mfa if your device responds within 6 seconds)
But it's not finding the challenge so it might be deauthenticating you.
Also, if you're installing wag from binaries have you enabled IP forwarding?
Can you asloc heck that the user is shown as authenticated in the wag ui..

Hello! 🤠
Thank you for the quick response; you are right, I hadn't configured the following in the config.json

I’m not sure if this is what you were referring to, but after adding it, the WebSocket error has gone.
On the other hand, yes, the IP forwarding policy in iptables is set to accept:

Finally, yes, the user is authenticated and registered:

Now, despite not showing any errors in the log, I still cannot access the local network:
Ping to the VPN server:

Ping to a powered-on server in the local network:

Thank you :)

Mmm sorry, I thought that  if the registration was successful, it would also grant authorization.Are you referring to this?:

Yes. That's showing its not authorised. And also that it's trying to register your mfa for some reason.
I think you should probably reset the account mfa and try again.
Not sure what the problem is there

Well, I don't understand it 😭 . I've reset the MFA key, but now I'm getting the same WebSocket error as before. And my colleague has successfully re-registered, now they appear as authorized:


Ad cut off on conclusion card

I think I'm going to have to keep testing this because it appears to do this on some but not all screens?

Tested it on multiple screens and they're all ok. Don't know if that one screen was just a fluke?