CsvMapWriter writes from Map

Hello, I am using super-csv 2.3.1. I am trying to write Map<Object, Object> to csv. I tried to use CsvMapWriter but I get compilation error because CsvMapWriter.write method only accepts Map<String, ?> as the first argument whereas on the website on the link below, it is mentioned that CsvMapWriter "Writes each row of CSV from a- Map or Map ". I do not see the implementation of Map in write method.
http://super-csv.github.io/super-csv/writers.html
Can you please advise. I don't think I am missing anything. All the examples so far I have seen are only passing Map .
If I cannot pass Map, do I need to create a custom cell processor?
Thanks .

This is my first use of github.  I have just realized that my post isn't posted correctly. Somehow the generics are missing with the class names so I am having to put it in quotes :( . I am rewriting my query here -
Hello, I am using super-csv 2.3.1. I am trying to write Map"<"Object, Object">" to csv. I tried to use CsvMapWriter but I get compilation error because CsvMapWriter.write method only accepts Map"<"String, ?">" as the first argument whereas on the website on the link below, it is mentioned that CsvMapWriter "Writes each row of CSV from a- Map"<"String">" or Map"<"Object">" ". I do not see the implementation of Map"<"Object">" in write method.
http://super-csv.github.io/super-csv/writers.html
Can you please advise. I don't think I am missing anything. All the examples so far I have seen are only passing Map"<"String">" .
If I cannot pass Map"<"Object">" to the write method, do I need to create a custom cell processor?
Thanks .

It seems many cannot find the examples in the left menu. You are not the first to get lost. Have a look at this page and please respond if it solves your problem
http://super-csv.github.io/super-csv/examples_writing.html

I have seen this example and I am using ICsvMapWriter example , except that the map I want to write to Csv has key of type Object whereas in the example , map's key is String type . The write method doesn't accept Map with key as Object type .
Thanks ,
Poonam
Sent from my iPhone
On 14 May 2015, at 19:44, Kasper B. Graversen <notifications<EMAIL_ADDRESS>wrote:
It seems many cannot find the examples in the left menu. You are not the first to get lost. Have a look at this page and please respond if it solves your problem
http://super-csv.github.io/super-csv/examples_writing.html

Reply to this email directly or view it on GitHubhttps://github.com/super-csv/super-csv/issues/45#issuecomment-102132405.
The information contained in this email and any attached files is confidential and intended solely for the addressee(s). The email may be legally privileged or prohibited from disclosure and unauthorised use. If you are not the named addressee you may not use, copy, or disclose this information to any other person. If you received this message in error please notify the sender immediately and delete it from your system.
Any opinion or views contained in this email message are those of the sender, and do not represent those of the Company in any way and reliance should not be placed upon its contents. Unless otherwise stated, this email message is not intended to be contractually binding. Where an Agreement exists between our respective companies and there is conflict between the contents of this email message and the Agreement then the terms of that Agreement shall prevail.
Excelian Limited / 44 Featherstone Street London / EC1Y 8RN / United Kingdom
T +44 (0)207 336 9595 / www.excelian.com

Ah I see your point. Not sure of a generic way to turn objects intro sane strings for the header. Any ideas? Maybe we need tune the docs slightly :)

I would just create a new map with the keys converted to Strings. The API relies on the String values in the nameMapping array to match with keys in the Map - so even if you allowed Object keys and toString()'d them, the values in that array would be horrendous.


Neither default entry or browser is ready for webpack inclusion

I just ran across a bug that isn't a high priority but I wanted to report it and ask what way you would prefer to proceed before opening a PR:
In my project I do import focusWithin from 'focus-within'; /* ... */ focusWithin(document); in my entry-point file. Doing so results in my vendors bundle including focus-within/index.js. I do not include the browser file manually in its own <script /> tag for two main reasons: existing build chain and performance.
A user with Safari 9 (this is why the bug isn't a high priority) visited my application an immediately errored out with: SyntaxError: Unexpected keyword 'const'. Const declarations are not supported in strict mode.
While my application handles the babel transformations required for our supported browsers list (which admittedly does not include Safari 9 but does convert all const/let to var still), as is standard convention we do not transform any node_modules as we expect them to be pre-compiled. We have resolve the issue by carving out an exception and passing focus-within through our babel transformation.
Looking at focus-within I think there are three possibilities for resolution going forward:

Update the build config to transform the const/let into var in the index output(s), thereby producing a more strict ES5 compat build.
Update the build config to leave a module.exports ... line so it becomes eligible for inclusion in common Webpack flows
Ignore this case entirely and provide instructions in the documentation on how to force babel processing for users like me.

I am unfamiliar with rollup (I poked around to see if I could open a PR quickly) but am more than happy to do the leg work on whichever of the above solutions you would prefer for your project.

This is an interesting request, but I don’t see a compelling reason to precompile the Node version for browsers when that is already being done using the browser.js file. Otherwise, if you wish to compile it for a browser, you’ll need to transform it from Node 6 to your browsers list.

as is standard convention we do not transform any node_modules as we expect them to be pre-compiled

I’m not sure that’s a standard convention, but I do understand what you are saying.
The node version of this library supports Node 6 environments with specific distributions for CommonJS and ModuleJS (see https://unpkg.com/focus-within@3.0.2/). This follows Node.js long term support.
I’m surprised you are not already compiling packages from node_modules whenever you replace import or require statements, as those packages commonly reference other packages themselves.
The browser version of this library is pre-compiled for a large set of browsers and would handle this for you. (see<EMAIL_ADDRESS>or require('focus-within/browser')).
For maintenance reasons, I distribute nearly all of my packages the same. It narrows down bespoke problems if one package is distributed differently than others. I’d like to continue following Node LTS for the packaged version and a conservative browsers list for the browser version. ould you provide some more insight into why I should standardize my distributions for Node 6 and strict ES5?
The environment targets for rollup are configured here: https://github.com/jonathantneal/focus-within/blob/master/.rollup.js#L7

I’m surprised you are not already compiling packages from node_modules whenever you replace import or require statements, as those packages commonly reference other packages themselves.

Webpack handles import/require resolution (and shimming/wrapping of the module system to run in a browser) which means the overhead of running Babel is not required to handle transpiling node_modules (the performance hit is quite large given the sheer number of node_modules files that get run).
Because the browser.js file strips the module.exports (https://github.com/jonathantneal/focus-within/blob/master/.rollup.js#L59) webpack can't correctly include and provide the function correctly (import focusWithin from 'focus-within'; /* ... */ focusWithin(); would fail because nothing was exported so the function could never be called. In fact the file wouldn't be included at all because Webpack tree-shaking would notice the function provided was never referenced, because it wasn't exported, and therefore can be stripped from the final build).
A good solution would be not stripping the module.exports so module systems like Webpack can include the browser file.

I’m not sure that’s a standard convention, but I do understand what you are saying.

The official docs in Webpack for utilizing Babel recommend excluding node_modules: https://webpack.js.org/loaders/babel-loader/#usage
create-react-app by default sets up webpack config to whitelist app source only (thereby excluding 3rd party or vendor libs in node_modules).

I'm having the same issues as @dcousineau on this. Maybe a solution would be to compile the browser.js to a UMD Module instead of compiling it to CommonJs and than removing the module.exports. This is mentioned on the Rollup Docs in the Compatibility section.
A UMD Module would work when included as script tag and also when using require('focus-within/browser') with webpack.


fix: include README.md in published package

Also re-enables publish step.

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


linux/386 does not work with 1.2.x

After upgrading to golang-cross:1.12.2 based on debian buster, cross compiling for linux/386 does not work.
fyne-cross --targets="linux/386"
Build output folder: /code/lucor/test/build
Target linux/386
Building...
# runtime/cgo
In file included from _cgo_export.c:3:
/usr/include/stdlib.h:25:10: fatal error: bits/libc-header-start.h: No such file or directory
 #include <bits/libc-header-start.h>
          ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
exit status 2

To fix need to create a dedicated 386 docker image.

Fixed into the develop branch


Do you have an example for AWS

Asked by @Rainer-Lang
@thshdw Do you have an example for AWS? Where I have to use the pem-file?

Hello,
I don't have AWS account but this should work...
"cmd": "ssh -i /path-to/my-key-pair.pem<EMAIL_ADDRESS>

@Rainer-Lang did this work for you?

That's my configuration and it's working good:
{"name": "server.compute.amazonaws.com",
"cmd": "ssh -i ~/.ssh/aws.pem<EMAIL_ADDRESS>

But tab names do not work.

@petethepig something like this should make a tab name for you.
            {
              "cmd": "ssh -i ~/.ssh/aws.pem<EMAIL_ADDRESS>              "inTerminal": "tab",
              "name": "server.compute.amazonaws.com",
              "theme": "basic",
              "title": "title of tab"
            }


feat: PostCSS & Tailwind Plugins

I've added two plugins: a PostCSS plugin and a Tailwind plugin (which uses the PostCSS plugin).

Has dev mode and build mode
Inlines source map
Works with Tailwind IntelliSense
Should work with Tailwind and PostCSS plugins if they are imported and instantiated successfully

Example usage
import { defineConfig } from "$fresh/server.ts";
import postcssPlugin from "$fresh/plugins/postcss.ts";
import tailwindPlugin from "$fresh/plugins/tailwind.ts";
import pfm from "https://esm.sh/postcss-font-magician";

export default defineConfig({
  plugins: [
    postcssPlugin({
      css: ["./src/font_magician.css"],
      dest: "./static/styles",
      mode: "render",
      sourceMap: true,
      setup: () => {
        return [
          pfm({
            variants: {
              "Inter": {
                // ...
              },
            },
            foundries: ["google"],
          }),
        ];
      },
    }),
    // Development mode
    tailwindPlugin(
      {
        css: [
          "body { @apply bg-yellow-500 }",
          "./src/style.css",
        ],
      },
      (await import("./tailwind.config.ts")).default,
    ),
    // Production mode
    // Outputs to ./static/styles/myDestinationFileName.css
    tailwindPlugin(
      {
        css: { myDestinationFileName: "./src/style.css" },
        mode: "build",
        dest: "./static/styles",
      },
      (await import("./tailwind.config.ts")).default,
    ),
  ],
});

Result

Also, I tested this with Deno SaaSKit, and it's not working. Have I made a mistake with the configuration of the plugin?
https://github.com/denoland/saaskit/tree/tailwind-plugin-test

@iuioiua

Also, I tested this with Deno SaaSKit, and it's not working. Have I made a mistake with the configuration of the plugin?

Switching the mode to "render" will let Tailwind process styles during dev. Otherwise, you'd have to run the build step to output the .css file, then add them to your <head>.
But as @marvinhagemeister suggested, we can probably drop that now. I'm going to see what I can do with the features added in #1961. I think I can make the plugin much more succinct. Closing this PR for take-two.
Thank you both for your advice!

@jasonjgardner I'm planning to work on a fallthrough route for static assets so that generated ones can be stored in build.outDir. Hoping to get that done on Monday.


Initial changes for supporting multiple cameras

Signed-off-by: Chris Richardson<EMAIL_ADDRESS>

@davidplowman Would you mind having a go at running this pull request on a compute module sometime, with 2 cameras (no rush!).
On my pi with a webcam + picamera, I can now get 2 preview windows running simultaneously :)
#!/usr/bin/python3

import time

import numpy as np

from picamera2 import Picamera2, Preview

picam2a = Picamera2(0)
picam2a.configure(picam2a.create_preview_configuration())
picam2a.start_preview(Preview.QT)

picam2b = Picamera2(1)
picam2b.configure(picam2b.create_preview_configuration())
picam2b.start_preview(Preview.QT)

picam2a.start()
picam2b.start()
time.sleep(5)

overlay = np.zeros((300, 400, 4), dtype=np.uint8)
overlay[:150, 200:] = (255, 0, 0, 64)
overlay[150:, :200] = (0, 255, 0, 64)
overlay[150:, 200:] = (0, 0, 255, 64)

picam2a.set_overlay(overlay)
picam2b.set_overlay(overlay)
time.sleep(5)

I'm using Qt rather than QtGL here, as I made a simple change to convert MJPEG->RGB.

@chrisruk Hi Chris, just tried this on my CM4 and it looks really promising!
I found all the previews worked fine together, including the QTGL one (not quite clear to me how access to the GPU gets arbitrated there, but perhaps that's a question for later on!). The only funny thing, which I see you're looking at already, is that closing one preview seemed to close them all (and leave things a bit messed up).
It's probably a bit early to review, but I did have a snoop through some of the changes. I guess the os.pipe was an easy way to signal the individual cameras in the same way and continue to use the QSocketNotifier. In some ways that seems over-complicated, but OTOH the architecture we have (where Qt is optional) really requires a Qt-free way to send signals, so maybe it needs to be like this? Don't know if there are any alternatives there.
I also thought it might tidy things a bit if the CameraManager class perhaps had register/unregister functions to tell it that it needs to watch for a particular camera (or not any more).
Thanks also for looking at the Qt threading issues. When I'm not working with Qt I tend to forget what a pain it can be! I haven't really understood all that yet, but I wonder if there's a way we could make a single thread that does all the Qt stuff and actually persists forever. We've had a long-standing problem where if you close and re-create a Qt preview, it complains about being in the wrong thread (though it works fine), and maybe there could be a route to fixing that. Not sure. Arguably we could do something like that as a separate commit even before adding multi-camera support.
Finally, I thought the MJPEG camera changes probably want to go into a separate PR - I feel we could possibly review and merge all that first? How does that work, by the way, do you get reasonable framerates with all that JPEG decode going on?
Anyway, I'm encouraged how well things work already, perhaps let's talk next week!

Cool, thanks for checking it out on the CM4 :)
Yeah, that's a good point about whether we need to use QSocketNotifier, will try and have a think about that.  I think libcamera uses an eventfd rather than std. file handle, like I'm currently doing, I don't think there's builtin python support for eventfds but can look for a library for that.

I also thought it might tidy things a bit if the CameraManager class perhaps had register/unregister functions to tell it that it needs to watch for a particular camera (or not any more)."

Good point, I do wonder, but need to confirm, if the CameraManager class for a particular process would only be seeing data for the camera IDs that are passed as cookies to create_request.

I wonder if there's a way we could make a single thread that does all the Qt stuff and actually persists forever. We've had a long-standing problem where if you close and re-create a Qt preview, it complains about being in the wrong thread (though it works fine)

That's a good point, I've also just bumped into that message when altering the .stop() function.  I'm wondering if something is possibly persisting outside of the thread itself somehow, will see if I can dig into that.

Finally, I thought the MJPEG camera changes probably want to go into a separate PR - I feel we could possibly review and merge all that first? How does that work, by the way, do you get reasonable framerates with all that JPEG decode going on?

Yeah thats seems a good idea re. using a separate pull request for that.  I've not analysed the fps, but it did seem to look visually ok to me.  I had to make it so that certain libcamera controls that weren't available for my webcam can be bypassed.  The webcam itself seems to just pass MJPEG data directly, so I just made a function to convert the MJPEG to RGB for Qt.

Anyway, I'm encouraged how well things work already, perhaps let's talk next week!

Sounds good

Just moved to https://github.com/raspberrypi/picamera2/pull/376, to rebase again from next, with multiple new changes


loadConfigFromFile API can not loadConfig have loadEnv func in vite.config.ts?

Describe the bug
in vite.config.ts call loadEnv to get env vars:
import { defineConfig, loadEnv } from 'vite'

export default defineConfig(({ command, mode }) => {
  const env = loadEnv(mode, process.cwd())
  const microAppName =  env. VITE_MICRO_APP_NAME
  return {
      base: "./",
          build: {
	       outDir: microAppName,
          }
    },
})

And then load vite.config.ts by loadConfigFromFile  API. But I got this config:
 {
  base: './',
  build: {
    outDir: 'undefined',
  }
}

is loadConfigFromFile API can not load config with loadEnv ?
Reproduction
https://stackblitz.com/edit/vitejs-vite-hbxjuy?file=vite.config.ts
Steps to reproduce

vite.config.ts with loadEnv:

import { defineConfig, loadEnv } from 'vite'

export default defineConfig(({ command, mode }) => {
  const env = loadEnv(mode, process.cwd())
  const microAppName =  env. VITE_MICRO_APP_NAME
  return {
      base: "./",
          build: {
	       outDir: microAppName,
          }
    },
})

load config by loadConfigFromFile API:

 const config = await loadConfigFromFile(
    {
      mode,
      command: mode === "development" ? "serve" : "build"
    },
    undefined,
    configRoot
  );

console log config:

 {
  base: './',
  build: {
    outDir: 'undefined',
  }
}

System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (16) x64 Intel(R) Xeon(R) W-2245 CPU @ 3.90GHz
    Memory: 20.23 GB / 31.73 GB
  Binaries:
    Node: 16.17.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.15.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.11.0 - E:\project\incall-nuwa\node_modules\.bin\pnpm.CMD
  Browsers:
    Edge: Spartan (44.19041.3570.0), Chromium (119.0.2151.97)
    Internet Explorer: 11.0.19041.3570

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I has found reason. beacause loadEnv function need right path:
const env = loadEnv(mode, process.cwd())

to
const env = loadEnv(mode, path.resolve(__dirname, "./"));


Add pre-commit hook for JSL (JavaScript Lint)

JavaScript Lint is a static analyzer in the vein of JSLint, JSHint, etc.
Unfortunately this tool is not available through a cross-platform package manager, so no install_command. The javascriptlint package on npm is unmaintained (no commits in 3 years) and does not provide an executable.
If you're on a Mac, though, you can get it with brew install jsl :smile:

If there is no convenient way to install a tool via well-known package manager, I would argue such a hook should be disabled by default.
Merged in bf2366da9ae28d4beab316983c59aca88c573e4e. Disabled by default in b5c79ff9d3538039e0c74d9bfa2b4d1dbacf05ed.
Thanks!

Ah, for some reason I thought that if required_executable wasn't in the path, the hook simply didn't run. Thanks for the merge and the fix!


Use "Option-key" in open recent on macOS

This seems more correct on macOS.

I'm adding a very similar placeholder in https://github.com/microsoft/vscode/pull/152988 so I'd like to make sure they're aligned.

No, Cmd is being used as "alternate opening" also for quick pick, I would be careful to change muscle memory here.
Agree though that maybe Cmd was not the best choice for macOS. However the intent was to align it with the Ctrl key that is used on Windows/Linux.

Hm, actually we support both Cmd and Alt key to open to the side in quick pick...

I guess this picker is really special in that it has a keybinding modifier for the one action and for the other.

Ah this is only about the string, fair enough 👍


build/{id}/run throws 404

Set up: Visual Studio 2015, Mac Remotebuild server.
When deploying from VS, everything works fine, except the fact that the app is not started. When looking at the console on the Mac, I see:
GET /cordova/build/12815/run 404
All other requests return 200.
Can't find anything on the internet about this?

If you open up the "output" console in Visual Studio, you should see some extra information. What does it say towards the end there? There are a number of reasons that it could be failing to launch, and the information in the output log should help clarify the cause.

Starting launch process C:\Program Files (x86)\nodejs\node.exe "C:\Users\user\AppData\Roaming\npm\node_modules\vs-tac\remoteDevice.js" --platform ios --action launch --path "C:\Projects\PhoneApp\bld\ios\Debug\buildInfo.json" --serverUrl http://mac:3000/cordova --language en-NZ --loglevel warn  --cliVersion 5.4.0
Timed out connecting debugger to remote Apache Cordova app. See Output window for JavaScript console output.
Unable to find the app to debug. Check that the device is awake and unlocked.
------ Cordova tools 5.4.0 already installed.
Requesting launch on remote iOS device for buildNumber 12815 on server http://mac:3000/cordova...
Failed to launch iOS remote for build C:\Projects\PhoneApp\bld\ios\Debug\buildInfo.json to http://mac:3000/cordova :
Http 404: Unable to launch app
------ Cordova tools 5.4.0 already installed.
Requesting debug on remote iOS device for buildNumber 12815 on server http://mac:3000/cordova...
Debugging - Successfully Debugging on the device
{webDebugPort=9221}

Phone is unlocked & active.

That Unable to launch app error occurs when there is a failure to communicate with idevicedebugserverproxy, and unfortunately we typically don't get much information to work off.
Can you please reproduce the error, and then without turning off remotebuild run ps ax | grep idevicedebugserverproxy on the mac and check whether the process is running? If it is, you could try killing it and then running it yourself using the same port that remotebuild would: idevicedebugserverproxy 3001 and see if that mentions any errors. If that appears to work, try resubmitting your build with idevicedebugserverproxy still running, and see if any errors are printed as part of the communication.
If none of that works, we can try some more detailed debugging.

Thanks. I get the following error from the proxy:
recv failed: Undefined error: 0
Receive failed: Bad file descriptor

What version of iOS is running on the phone? Around previous iOS releases I had seen some flakiness in launching as sometimes the protocol to talk to the devices changes. Unfortunately it isn't giving us a lot to work with...
You could also try running brew update && brew upgrade libimobiledevice to see if there is an updated version which fixes the issue.

iOS 9.2 is running on the device (iPhone 6 & iPhone 5)
When I run upgrade, it says :
limimobiledevice 1.2.0 already installed.
So it seems I already have latest version.
Anything else I can test? It's quite annoying. Debugging only works when I open the app manually at the right time, otherwise I have to try again.

The version of Cordova shouldn't matter here, since the step that is failing is launching an application that has already been built, which does not differ based on the contents of the application.
I'm checking to see if I can get it to repro at all on my end. Does your app id (e.g. io.cordova.helloworld) have any unusual characters in it, or contain the substring '.app'?

You must be kidding me....
It did contain ".app", changed that to ".mobile" and now it works.
Awesome :dancer:
But this should be either fixed or documented very clearly I think...

I'm afraid that you've discovered the same "wait, really?!" bug that I did a few months back. Fun fact; try launching the same application (with the .app name) from within xcode, and I believe it will also fail. Seems to be a limitation of the platform. For the record .App is fine, it's just exactly .app that can't appear.
Glad we got that sorted out, and it's definitely a candidate for better documentation. Thanks for reporting this :)


Improve gitstream build logic change detection

Avoid script changes in samples or snippets, list file names to match

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you.


Extension issue

Issue Type: Bug
Extension Name: vscode-icons
Extension Version: 11.0.0
OS Version: Windows_NT x64 10.0.19041
VSCode version: 1.52.1

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Please take a look at #2392.


Feature Request: Add hud interaction for show token and actor image

I would like some kind of HUD-level action to be added to the single token as was done in its time with https://github.com/zeel01/TokenHUDArtButton, but integrating it with your dialogue for choose specific players to visualize.
A very low priority request.

Hello,
Thx for suggesting new features.
The basic is now implemented with 0.0.20

Hi sorry to bother , it is possibile on the hud to add the option to show the image to a specific player like you already done on the journals ?

@p4535992 Sure thing, this is live with 0.0.21


Can't click on icons twice on the website

On the website, when you click once on an icon, it opens a modal with import code. When you close this modal and click on the icon again, the modal doesn't pop up

Thanks for raising this issue – fixed by 0167ea8


Document Compliant Kubernetes on Baremetal

Lennart knows what to write here. :)

Closing, we made a lot of progress on this issue with the provider audit.


Extension issue

Issue Type: Bug
Extension Name: vsliveshare
Extension Version: 1.0.3121
OS Version: Windows_NT x64 6.3.9600
VSCode version: 1.51.0

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Hello,
Could you provide us with more information about the problem?

Closing this due to inactivity and lack of actionable details. Please re-open if you're still experiencing this problem. Thanks!


shouldn't $forge->runRecipe($recipeId); include a way to pass server ids?

Just wondering how you can run a recipe on a specific server or set of servers
in the api docs the payload is described as
⊖{
    "servers": ⊖[
        1,
        2
    ]
}

but according to your docs the runRecipe() only accepts a recipeId?

I haven't tried it yet, but if you look at the usage section, you probably can run recipes like so:
$server = $forge->server(SERVER_ID_HERE);
$server->->runRecipe($recipeId);

@jpmurray no, since recipes can be run on multiple servers at once. Adding it to the Server class wouldn't make sense. I've opened a PR (#19) to address this issue 🙂


Draw overlay for both 2D and 3D birefringence acquisitions

Resolves #263

@talonchandler This naive solution does leave the GUI window unresponsive after reconstruction finished on the Automaton computer. Not sure if it is because of this though.

Codecov Report

Merging #270 (867b5b7) into main (f84f09d) will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff          @@
##            main    #270   +/-   ##
=====================================
  Coverage   4.38%   4.38%
=====================================
  Files         22      22
  Lines       4970    4970
=====================================
  Hits         218     218
  Misses      4752    4752

Impacted Files
Coverage Δ

recOrder/plugin/main_widget.py
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Now the GUI does not freeze, but there's a delay before 3D overlay can be updated. On a local computer with high single-thread CPU performance, a 21512512 volume (from demo MM camera) takes < 1s; with Xeon Silver @2.4GHz we typically have on microscope computers, a<PHONE_NUMBER> volume will take 5~10s to be rendered.


Fixed snprintf into const char*

I've tried compiling the examples with MSVC2022, and it didn't work due to this write to string::data(). I'm not sure if this works elsewhere, but according to the standard, data() returns a const char*. With a const_cast this is still very much undefined behavior, but at least it compiles now, and it seems to work fine.

FWIW I think you can use &result[0] to avoid the const cast.

Neither the const_cast nor &result[0] should be used.
In pre-C++17, data() only returns immutable storage and changing the underlying data is UB.
Since C++17, data() offers a non-const overload which is what is used in this case.
What is the error you're seeing with MSVC2022? Should compile fine when using at least C++17.

It's just the regular "const char* is incompatible with char*". The project configuration here says we're working with C++11. https://github.com/MolecularMatters/raw_pdb/blob/26683ab3cff61c64f5d4c91254b7696a1797cb0c/CMakeLists.txt#L5 That actually generates a vcxproj for C++14, since C++11 doesn't appear to be an option.

Either way, the const_cast is not a solution, but a duct tape.
This has to be done differently entirely (e.g. snprintf into a stack buffer, return a std::string from there).

Sure, if you want to fix this properly, I'd be more than happy with that too. Though considering that this is just in the example code, I'm not sure it's worth the effort.

Shouldn't be a lot of work, will do this tomorrow.


Manifest v2, Manifest v3

What are the plans regarding manifest v3 adoption, and will manifest v2 still be supported
Especially for adblockers

The plan is to keep ManifestV2 active. It's quite easy to handle (as a note: we announced it almost immediately when ManifestV3 was announced).

@kiwibrowser
Do you plan to implement Manifest V3 also (while keeping the webRequest API)? I am asking because I was trying to install a Manifest V3 extension and the Chrome Web Store marked it as incompatible with my browser. Would be fantastic if both were supported in parallel. Finally, what will you do when Google removes extensions like uBlock Origin from the Chrome Web Store? Will it be possible to install them from GitHub and update them from there as well? Thank you for your time!

@Peacock365
Using my custom manifest V3 extension with latest build. No issue.
uBlock has already started developing V3 version: uBlock Minus. But currently not compatible with kiwi browser.

uBlock has already started developing V3 version: uBlock Minus. But currently not compatible with kiwi browser.

Once the UBlock Minus add-on is available for download on the Chrome Store for Google Chrome Desktop, will that also mean UBlock Minus will be available on the Chrome Store for Kiwi too?

Sorry! for off-topic conversation.. GitHub needs to bring pm feature..
@sliceanddice9
You can try that extension by downloading it from here: https://github.com/gorhill/uBlock/releases
Look for uBlock lite (re-named from uBlock Minus)
Don't know why Chrome store flags it "not compatible"

uBlock has already started developing V3 version: uBlock Minus. But currently not compatible with kiwi browser.

Once the UBlock Minus add-on is available for download on the Chrome Store for Google Chrome Desktop, will that also mean UBlock Minus will be available on the Chrome Store for Kiwi on Mobile too?

I know this is like 9 months late but (just in case) the developer of ublock origin recently released the first release of the lite version of the extension and is still releasing the normal version as a zip file for chromium browsers.

Confirmed that Kiwi will support both MV2 and MV3 .

Today, @Violentmonkey stopped working completely in @KiwiBrowser 124.0.6327.4, even if developer mode is activated in Extensions page.
https://community.metabrainz.org/t/user-scripts-on-mobile/134406/27?u=jesus2099
https://github.com/violentmonkey/violentmonkey/issues/1934

Ah, sorry it's because of https://github.com/violentmonkey/violentmonkey/issues/2180 not because of Kiwi Manifest v3!


meta loop echo hi does not echo hi

🐛 Bug Report
meta loop arguments are not passed to command without passing command as one argument
To Reproduce
% meta loop echo hi
# Only displays folder names but not hi

Expected behavior
Every argument passed to meta loop command should be passed to to the command.

meta loop is not a command.
meta exec echo hi is a valid command
loop echo hi is a valid command, for loop.


feat(consensu): add central invoke transaction

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2861  👈 (View in Graphite)
#2715
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


webhooks: Updated docs for some complex integrations.

@rishig, @timabbott: FYI :)

@timabbott, @rishig: Updated with more! Thanks! :)

@timabbott: Also, I implemented your feedback :)

Thanks @eeshangarg!

Bitbucket: Probably "Zulip" is a good title, rather than "Zulip webhook". I would also say "Choose Webhooks" rather than "choose webhooks on the left hand side", unless it is a confusing enough UI that that would be helpful. Also let's go with "Check the Active checkbox" instead of the current "Remember to check the"
Beanstalk doesn't look done; there should be only ~5 instructions? Also the URL looks different, is that still correct?
We should also put this into using the macros of the others, if it is easy (i.e. first step is "create the stream you would like to use for XXX notifications ..."). If reusing the macro is hard, even just making it be the identical text will make it easier to maintain it later.
hm, similarly for beeminder; steps 4, 5, and the first half of 6 should be one step. The second half of 6 should be it's own step.

Maybe let's write the style guide first, so we can make sure we're in sync with all the pieces of the style?
After seeing these, I'm also realizing that the filled in screenshot is better than an empty one. (Or at least, that an empty one looks sort of strange.) No need to go back and change the ones you've already done, but maybe let's rethink what we want to do here.
One possibility is just to remove all the screenshots; that has the benefit of not needing to standardize them, and the screenshots never going out of date. Also possibly we can then instead highlight the "Congratulations" screenshot, which is an advertisement for the webhook, rather than a random screenshot of the service.
Another possibility is to add a red box or something around each of the boxes that need to be filled.
I'm leaning slightly towards removing them, but interested in yours and Tim's thoughts.
My thought is that the main goal of this text is to encourage the user to get started with the process, and then provide enough assistance that they never get scared or stuck. And for that I'm not sure how much the screenshot helps. Tim: three to look at are Airbrake (no screenshot), Appfollow (screenshot works well), and Beanstalk (screenshot doesn't work well, imo).
Also lastly just want to check that you are using the zulip integrations email and password for each of these sites? That will make it easy to go through and update when we do a round of updating in the future.

I think removing them is fine unless there's a specific reason they're required (e.g. something is very hard to find).  In that case, we probably want a smaller screenshot, with perhaps some drawing on the image done to mark the thing that's hard to find.

Great, sounds good to me. In that case we can also change our numbering a bit, so that "click Save" is in the same instruction as "fill out the stuff".
So a typical doc, where nothing is complicated or needs an extra picture, might look like

from macro
from macro
Go to blah. Click blah, and then click blah. [i.e. navigational instructions]
Enter in the URL you .... Check the Active button ... Click Save. [i.e. fill out the form and click save instructions].

@timabbott, @rishig: Updated with all the requested changes. I wouldn't be surprised if this might need another couple of rounds of feedback, especially the Facebook doc is tricky! Looking forward to your feedback! Also, I think I'll reiterate on this set of commits before doing any more since this might still need changes! Thanks! :)

great, thanks! A few thoughts:
Beeminder

So far, we've put "Create a URL" and "Create the bot" in the same step. For beeminder, they are different steps. Possibly the beeminder route is the correct one (make them separate steps), but if we go that route we should update our style guide notes to say that. (Or is the beeminder one separate because the URL instructions are longer?)
Step 4 starts with "Next, ..". We shouldn't start with transition words, since it makes it more likely to introduce bugs in macro refactoring.
Now that we don't have the image, I think we should use casing like "Deadline & Reminders" or "Save changes" in the situation were it is in all caps in the beeminder UI. The bold, all caps is too scary.
This webhook seems to operate in a strange way on the zulip end. What happens if you specify a stream and also click "Make this goal private"? Probably the private thing should be explained in step 3.

Other notes:

The CircleCI instructions seem unfinished, but we can deal with that later
If there is ending punctuation in the setting, like "Enable this checkbox?", we should leave the punctuation out of our instructions. Starting punctuation, like "+ New Notification" should stay.
If there are 4 sentences, we should generally join the middle ones with an "and". E.g. instead of "Click W. Click X. Click Y. Click Z.", "Click W. Click X, and click Y. Click Z".
We should generally not include "log on to your ..".

This is getting to the point of being pretty nit-picky, though I feel like we're making good progress towards a template that we can just apply to most new integrations without thinking.
I think next steps are probably to:

Start writing things down into a style guide. A paper doc seems like a good place to start; I can create one if you'd like.
Get 5 of the easiest ones merged from this list, so we reduce the number of integrations we're looking at.

The facebook one is a bit complicated, so we can do that after we nail the simple ones. But at a first pass:

We don't need the notice at the bottom ("This integration is not created by ...")
Do we need a token? If not, we should just set it to something reasonable, like token=unused.
"Select the User category .." should be the start of a new step. Also, we can remove the "therefore".
Replace "Zulip server" with "Zulip organization" in the last row.

Thanks!

@rishig: I have a few thoughts:
About Facebook:
Implemented everything except I don't agree that we should just set token to a value such as unused. The token argument is needed for server verification and the user is required to type what they chose as the token when they specify the webhook URL. Also, each notification in Facebook can be specifically configured, so there might be instances where users may want to specify different tokens for different kinds of notifications. I don't think we should take away a choice that seems to be such a recurring part of the setup process on Facebook's end. I would love to hear your further thoughts about this. :)
About Beeminder:
Okay, so there are three ways to use the webhook:

For notifications via PM, in which case a stream need not be created or specified. Only the user's Zulip email suffices.
For notifications to a public stream, in which case the user's Zulip email need not be specified, the target stream is enough.
For notifications via PMs and streams, depending on which "reminders" are "private" or not. In this case, both the user's Zulip email and a target stream would be specified in the URL and private reminder notifications would be sent as a PM and public reminder notifications would be sent to the target stream.

For now, I divided the docs into two sections, one for PMs, one for streams. This separation seemed justified and simplified the steps and allowed the language and style to not deviate from the style we are aiming for here. However, I haven't addressed the ability to receive both PMs and stream notifications, and I would appreciate your thoughts on whether we should or not. Off the top of my head, users might want either but not both. Not to mention the third point leaves the possibility that a private reminder (such as about the user's weight goals, which can be a personal topic) may inadvertently get posted to a public stream. What do you think?
Separate steps for "create a bot" and "construct URL"
I am not so sure about this one. Both steps seemed intertwined enough in most cases that they should go together. However, in certain cases, constructing a URL can be complicated enough to warrant its own step (which is the case with Beeminder, depending on whether the user wants PM or stream notifications). So, I am a bit unsure as to what's the best choice here in the long run and I would appreciate your thoughts!
As an aside, separating the two would involve a larger refactor in the macros that probably shouldn't be a part of this PR (for example, splitting up the create-bot-construct-url.md type macros).
Style guide
Here is the Paper Doc where I started writing the style guide. It is only a first draft, so probably needs lots of improvements. :) Please feel free to edit as you please!
That's all I have for now! Thanks for your guidance, @rishig and @timabbott! :)
-Eeshan

Facebook: Let's move this to czo, but it's worth thinking about how we do server verification and notification configuration for our other integrations, that don't have such a token.
Beeminder: hm, let's also take this to czo then, and likely leave it out of the first 5 we merge. It seems complicated in a couple of different ways (e.g. why does "Click on Make this goal private" matter?)
Separate steps: sounds good; causing a big refactor is a great reason to leave it as is :). The rule can be "for straightforward things where a macro applies, use a macro". And for everything else, can be a judgement call based on how complicated the URL construction is, with the default being that it's a separate step.
Also, if you notice that there is a pattern of constructing URLs that is repeated a couple of times, we can consider making a new macro for it.
Style guide: awesome! Looks great; I'll do a quick editing pass tonight or tomorrow, but the rest of the PR can proceed in parallel.
Maybe to make things simple, could you open a separate PR with a couple of the most straightforward integrations from this PR, so we can merge them and reduce the size of this PR?
Thanks @eeshangarg!

@rishig: Done! This PR now contains only the commits that need more work, the rest have been moved over to #8501! :) Also, this PR will have merge conflicts when #8501 is merged, since commits in both PRs depend on commits that will be merged as part of #8501. I'll take care of that! :)
Renaming this as a WIP till we decide how to move further! Thanks! :)

@rishig: I just rebased after #8501 was merged and this PR is now as concise as it can possibly be. Here are few things we need to sort out before I go ahead and migrate all webhook docs:

Finalise the style guide.
Facebook: we still need to discuss how to approach this one.
Beeminder: we still need to discuss how to approach this one.
Crashlytics: could you please see my commit description and share your thoughts on whether we should actually sign up and link an app to a Crashlytics account to verify the correctness of our instructions?
CircleCI: you mentioned this one isn't complete. I'm not sure, I think it is. What other steps do you think we need? Once the URL to query is in the CircleCI config file, shouldn't CircleCI take care of the rest?
Dropbox: Could you please share your thoughts on step 3? Should it be split up? There are 4 sentences but I don't see an eloquent way to join the middle ones with an "and", like you suggested.

Thanks!
-Eeshan

Great, thanks! For facebook and beeminder, let's start a discussion on czo (maybe in #integrations)?
Crashlytics: sounds good, agreed it is too much work to verify. I would change "the URL we created above" to "the URL created above"
CircleCI: I think we want complete instructions in our documentation, rather than linking to their docs.
E.g. a problem with just linking to docs: "CircleCI also supports Slack, HipChat, Campfire, Flowdock and IRC notifications; you configure these notifications from your project’s Project Settings > Notifications page." Does this apply to zulip or not?
Their documentation is also written for highly technical people, e.g. "This example will POST a JSON packet to the specified URL".
Dropbox: "Dropbox My apps page" -> "Dropbox apps page". Otherwise looks great!

@rishig: Updated! A few thoughts:

CircleCI: So, you can't setup a webhook for Zulip as you would for Slack, HipChat, etc. There is no UI you can go to. Even in Project Settings --> Webhook Notifications, CircleCI simply links to the same place we linked to.
Facebook: Turns out token can't be blank. So I set it to unused.
Beeminder: Dropped the commit for now. Let's resolve the discussion on czo before we move forward!

Looking forward to your feedback! Thanks! :)

Thanks @eeshangarg!

CircleCI: Interesting! In any case, it's fine if they have to manually change the config.yml file, but we should give them the instructions for what to change in our documentation, rather than sending them to the circle ci site (particularly because the circle ci documentation is written for a much more technical audience).

Facebook, Beeminder: sounds good! The beeminder discussion is at https://chat.zulip.org/#narrow/stream/127-integrations/topic/incoming.20to.20PMs.

Thanks @eeshangarg! I merged Dropbox, and Crashlytics after a minor change.
I also pushed updates to CircleCI and Facebook to https://github.com/rishig/zulip/tree/review-8433

CircleCI: I think putting in the URL is a bit confusing, so I want to replace it with something like . That causes the formatting bug below; any ideas as to what is going on, or for a workaround?

Facebook: ongoing discussion in chat.

@rishig: Updated! Not the best at CSS, so there is probably a better fix for the code-block problem than I what I came up with! Thanks! :)

Tim, could you take a look at the CSS commit when you get a chance?
The facebook one is still blocked on us understanding what it does, but the CircleCI one can be merged.

@timabbott, @rishig: Just updated this! Could you please take a look? Thanks! :)

FYI I don't think this PR has anything to do with the build failure

Tim, passing to you for reviewing/merging this.

I'm going to get Brock's feedback on the CSS change.

Sounds good; merged, thanks @eeshangarg!


Add db.operation to Dalli instrumentation

We should have a db.operation attribute in Dalli instrumentation. See https://github.com/open-telemetry/opentelemetry-ruby-contrib/blob/main/instrumentation/dalli/lib/opentelemetry/instrumentation/dalli/patches/server.rb#L14.

@arielvalentin Is this still relevant? Can I pick this up?

Maybe? @plantfansam could you provide more details into what the db.operation should be vs db.statement?
https://opentelemetry.io/docs/reference/specification/trace/semantic_conventions/database/#call-level-attributes

Maybe? @plantfansam could you provide more details into what the db.operation should be vs db.statement?

Absolutely! So per the semantic conventions, db.operation is meant to be the name of the operation being executed. So in MYSQL it might be DELETE or SELECT.
DB statement is meant to be the entire statement that's being executed. So that value might be something like SELECT * FROM wuser_table; SET mykey "WuValue".
As I see it, db.operation may allow a coarser-grained perspective on database spans when db.statement is redacted, and this is valuable work.

I appreciate the guidance and context here.
Probably want to take these comments into consideration as well:

The span name SHOULD be set to a low cardinality value representing the statement executed on the database. It MAY be a stored procedure name (without arguments), DB statement without variable arguments, operation name, etc. Since SQL statements may have very high cardinality even without arguments, SQL spans SHOULD be named the following way, unless the statement is known to be of low cardinality: <db.operation> <db.name>.<db.sql.table>, provided that db.operation and db.sql.table are available. If db.sql.table is not available due to its semantics, the span SHOULD be named <db.operation> <db.name>. It is not recommended to attempt any client-side parsing of db.statement just to get these properties, they should only be used if the library being instrumented already provides them. When it's otherwise impossible to get any meaningful span name, db.name or the tech-specific database name MAY be used.

Awesome. Thanks. I will get back soon :)


I added this library to junit third party engine list

Hi,
I added this to https://github.com/junit-team/junit5/wiki/Third-party-Extensions .
I hope it helps.

Thanks!


Wait_for_completion=True does not raise an exception if the AML job fails

AML build refs_pull_585_merge_1637075124_422ff8d0
But the LungPR leg of the build is green: https://innereye.visualstudio.com/InnerEye/_build/results?buildId=45489&view=logs&j=f1141c13-3f1a-5076-cbd7-2c513939ac8b

Wrong repository. should be in InnerEye


Prevent duplication of bucket properties in state of get/put FSMs

When using non-typed buckets, the bucket properties from the bucket are merged with the default bucket properties. However, they were merged using lists:keymerge rather than lists:ukeymerge, which kept all of the duplicated propertied in the merged list. This PR changes riak_kv_get_fsm and riak_kv_put_fsm to use lists:ukeymerge instead, which takes the value from the custom properties list if it exists, and discards the matching key from the default list.

Looks good to me, silly and trivial as it is, a test would have stopped the original issue ever getting out, so I'd really recommend adding a unit test that shows this does what is expected (no dups, favours the custom props over the default props)

I guess it is a pain to use the riak_core_bucket_props fun since this PR will touch 2 repos. Is up to you.

Can one of the admins verify this patch?


Flu Near You fails to initialize

Home Assistant release with the issue:

0.84.6
Last working Home Assistant release (if known):
N/A
Operating environment (Hass.io/Docker/Windows/etc.):

Docker
Component/platform:

sensor/flunearyou
Description of problem:
Flu Near You fails to load when it receives CDC ratings that aren't a part of the integration's mapping. See trace below.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
sensor:
  - platform: flunearyou

Traceback (if applicable):
Error while setting up platform flunearyou
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/helpers/entity_platform.py", line 128, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
    return fut.result()
  File "/usr/src/app/homeassistant/components/sensor/flunearyou.py", line 91, in async_setup_platform
    await fny.async_update()
  File "/usr/src/app/homeassistant/components/sensor/flunearyou.py", line 207, in async_update
    CATEGORY_CDC_REPORT, self._client.cdc_reports.status)
  File "/usr/src/app/homeassistant/components/sensor/flunearyou.py", line 196, in _get_data
    self.data[category] = await method()
  File "/config/deps/lib/python3.6/site-packages/pyflunearyou/cdc.py", line 57, in status
    return adjust_status(info)
  File "/config/deps/lib/python3.6/site-packages/pyflunearyou/cdc.py", line 23, in adjust_status
    STATUS_MAP[int(info['level'])],
KeyError: 6

Additional information:

Setting in sensor.yaml coordinates works.  If you set coordinates using the UI it doesn't work at all.  Can we update it so it can read coordinates from the UI and not set it in the sensor.yaml?


Is fn.cloneNode = fn line still relevant?

https://github.com/ryansolid/dom-expressions/blob/a1d24a1a4fb07c3a63919c978ec4180896de9248/packages/dom-expressions/src/client.js#L67-L84

Backwards compat


Update README.md

@jeffrymorris Did you mean to do this PR into the couchbaselabs fork instead of my original fork? I'm happy to accept it, just want to make sure it's what you intended.

Yeah, wring branch!
On Sun, Jun 14, 2020, 10:59 AM Brant Burnett<EMAIL_ADDRESS>wrote:

@jeffrymorris https://github.com/jeffrymorris Did you mean to do this
PR into the couchbaselabs fork instead of my original fork? I'm happy to
accept it, just want to make sure it's what you intended.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/brantburnett/Couchbase.Extensions/pull/15#issuecomment-643800409,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADO4IGQ62F67SKQBB7WQFTRWUFXPANCNFSM4N4YBW5A
.

"Wrong" (sigh)
On Sun, Jun 14, 2020, 2:52 PM Jeffry Morris<EMAIL_ADDRESS>wrote:

Yeah, wring branch!
On Sun, Jun 14, 2020, 10:59 AM Brant Burnett<EMAIL_ADDRESS>wrote:

@jeffrymorris https://github.com/jeffrymorris Did you mean to do this
PR into the couchbaselabs fork instead of my original fork? I'm happy to
accept it, just want to make sure it's what you intended.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/brantburnett/Couchbase.Extensions/pull/15#issuecomment-643800409,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADO4IGQ62F67SKQBB7WQFTRWUFXPANCNFSM4N4YBW5A
.


Create repo to house annual survey

Every year the Rust project puts out an annual survey. Previously this was largely coordinated in a mix of Google Docs, Google Sheets and hackmds. This year we would like to solidify our process by creating  a dedicated repo that will house all relevant non-sensitive information that relates to the survey.
Additionally, we will be using the Rust pontoon instance for doing translations which usually works through GitHub repositories.
Name: surveys
Permissions: community-survey

Done - https://github.com/rust-lang/surveys.
No setup work in terms of pontoon; let us know if particular changes are needed there.


Remove useless code samples and add missing ones

I created scripts to manage code samples (internal only)

I found out the following code samples are still in this repo but not used by the documentation anymore, so I removed them:

meilisearch-dart
- 'faceted_search_2' not found in documentation
- 'get_keys_1' not found in documentation
- 'documents_guide_add_movie_1' not found in documentation
- 'getting_started_communicating_with_a_protected_instance' not found in documentation
- 'faceted_search_facets_1' not found in documentation

I found the following code samples were missing:

meilisearch-dart
- 'get_typo_tolerance_1' not found
- 'update_typo_tolerance_1' not found
- 'reset_typo_tolerance_1' not found
- 'typo_tolerance_guide_1' not found
- 'typo_tolerance_guide_2' not found
- 'typo_tolerance_guide_3' not found
- 'typo_tolerance_guide_4' not found
- 'async_guide_canceled_by_1' not found
- 'facet_search_1' not found
- 'facet_search_3' not found

All of them were missing, because the related features are implemented.

@ahmednfwela @brunoocasali be careful before fixing this kind of issue: https://github.com/meilisearch/meilisearch-dart/issues/340 -> the code samples were not implemented, so the full issue was not done 😊

yes my bad, sometimes I create 3/4 prs a day and forget to add the code samples 😅

bors try

@curquiza I suggest also fixing the link at the top to
https://github.com/meilisearch/documentation/blob/main/.code-samples.meilisearch.yaml

I made a PR that supersedes this https://github.com/meilisearch/meilisearch-dart/pull/358
@curquiza

@curquiza I suggest also fixing the link at the top to
https://github.com/meilisearch/documentation/blob/main/.code-samples.meilisearch.yaml

I changed the description. Before a kind of documentation existed at this link. I removed it. Not all the code samples are present in https://github.com/meilisearch/documentation/blob/main/.code-samples.meilisearch.yaml

I made a PR that supersedes this #358 @curquiza

Thank you!
However, can we still merge this current PR? The goal is to provide an up to date documentation to the users as soon as possible
@brunoocasali will review the other PR when he will come back from Holiday 😊

yes sure! we can merge this PR now, but is there a place that contains all the code samples ?


The animate() method does not return widget

In the Tabris blog about creating animations, it clearly states that the animate() method returns the widget.

It is interesting to note that the call to animate(..) returns the widget itself, so you can easily chain a call to register a listener to animation events. Building upon the simple example above, the following snippet shows how to listen to an animation end event:

widget.animate(
  {opacity: 0.5}, {duration: 1000}
).on("animationend", function() {
    console.log("animated ended");
});

This is not supported by the documentation and doesn't appear to be true in version 1.5. I get an error when attempting to use the code shown in the example and capturing the result of the animate() method returns "undefined":
var tmp = widget.animate({opacity: 0.5}, {duration: 1000});
console.log(tmp);    // returns 'undefined'

Adding return this; to the end of the animate function in Animation.js fixes this.


New Feature Request: Refresh Stats (i.e. store WordCount in the texts table)

Is your feature request related to a problem? Please describe.
Currently, if the content is edited within books (i.e. content is added or deleted), it does not automatically update statistics for the book. The word count still shows the same as before.
Describe the solution you'd like
It would be good to have a refresh statistics button in the Statistics page (http://localhost:5000/stats/) so a stats refresh can be triggered on demand for all books after they are updated.
Describe alternatives you've considered
No alternatives available.
Additional context
None

Currently, for some reason, I only track word count at the book level, when the book is created.  Field: books.BkWordCount.
Word count is also tracked in the texts.TxWordCount, but is only populated when a page is marked read -- this change happened as the code grew.
What should happen: on book creation, the word count should be stored in TxWordCount, and just summed for displaying the book stats, no need to store it separately.
Unfortunately this change will require the books to all have their stats calculated.

Possible solution: store "book stats calculated" flag in system settings, and if that flag is not present and there are texts with null TxWordCount, then calc all the counts and set the flag.  Set the flag at the end of the routine regardless so it's not re-calculated.
Actually, instead of this, the start-up routine could just do a check for texts with null count, and then calculate the counts.  No need for a flag, no need for anything, just do a one-time update, and show a message that this is being done at start up.

Fixed in the develop branch.  Word counts in texts are stored at the text level, and update if the text is updated.
This was low priority but still good to get done.  Thanks :-)

Launched in 3.1.1


⚠ Home NAS has degraded performance

In f5c37f5, Home NAS ($MY_NAS_URL) experienced degraded performance:

HTTP code: 200
Response time: 15306 ms

Resolved: Home NAS performance has improved in a144df3 after 2 hours, 43 minutes.


Extract method returns incorrect code

Steps to Reproduce

Type

x = 1
y = 1

Select the two lines and extract method on the lines

Expected behavior
def new_func():
    x = 1
    y = 1

new_func()

Actual behavior
def new_func():
    x = 1

new_func()
y = 1

Extract Method on the three lines inside func below does nothing:
def func():
    x = 1
    y = 2
    return x * y

workspace/applyEdit message is:

  "jsonrpc": "2.0",
  "id": 8,
  "method": "workspace/applyEdit",
  "params": {
    "label": "Command 'pylance.extractMethod'",
    "edit": {
      "changes": {
        "file:///c%3A/Users/stellahuang/source/repos/PythonApplication10/PythonApplication10/PythonApplication10.py": [
          {
            "range": {
              "start": {
                "line": 1,
                "character": 0
              },
              "end": {
                "line": 1,
                "character": 0
              }
            },
            "newText": "def new_func():\n    x = 1\n\n"
          },
          {
            "range": {
              "start": {
                "line": 1,
                "character": 0
              },
              "end": {
                "line": 1,
                "character": 5
              }
            },
            "newText": "new_func()"
          }
        ]
      }
    },
    "metadata": {
      "isRefactoring": true
    }
  }

so looks like pylance isn't returning the correct edits at the first place.

but the textDocument/codeAction request is sending the wrong range to pylance, the _vs_selectionRange has the correct range.
  "traceparent": "00-319dc53d5a70fd459c7fa23603b3a7c5-46f9f679959dbc4d-01",
  "jsonrpc": "2.0",
  "id": 16,
  "method": "textDocument/codeAction",
  "params": {
    "textDocument": {
      "uri": "file:///C:/Users/stellahuang/source/repos/PythonApplication10/PythonApplication10/PythonApplication10.py"
    },
    "range": {
      "start": {
        "line": 1,
        "character": 0
      },
      "end": {
        "line": 1,
        "character": 5
      }
    },
    "context": {
      "_vs_selectionRange": {
        "start": {
          "line": 1,
          "character": 0
        },
        "end": {
          "line": 2,
          "character": 5
        }
      },
      "diagnostics": [],
      "triggerKind": 1
    }
  }

https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1378352
See above for the response from LSP team. It's by design that the range is always current line in VS. If pylance depends on the range, we will need to use _vs_selectionRange instead.

def func():
    x = 1
    y = 2
    return x * y

This is a separate issue, let me file another ticket to track it.


Made a nodejs wrapper. can you add it to README? as 3rd party wrapper?

https://github.com/softmarshmallow/uguu-api
Is it ok to publish like this? if you don't like, I will remove the package.
If it's ok can you share it on README so others can access?

pomf is separate from uguu, one hosts files permanently and the other hosts files temporarily


oktadev not working in cordova application

I getting following error ,
Error: node_modules/capacitor-secure-storage-plugin/node_modules/@capacitor/core/types/definitions-internal.d.ts:16:18 - error TS2430: Interface 'CapacitorInstance' incorrectly extends interface 'CapacitorGlobal'.
Types of property 'Plugins' are incompatible.
Property 'SecureStoragePlugin' is missing in type '{ [pluginName: string]: { [prop: string]: any; }; }' but required in type 'PluginRegistry'.
16 export interface CapacitorInstance extends CapacitorGlobal {

node_modules/capacitor-secure-storage-plugin/dist/esm/definitions.d.ts:3:9
3 SecureStoragePlugin: SecureStoragePluginPlugin;

'SecureStoragePlugin' is declared here.
Error: src/app/app.module.ts:9:10 - error TS2305: Module '"../../node_modules/@ionic/storage/dist/esm"' has no exported member 'IonicStorageModule'.
9 import { IonicStorageModule } from '@ionic/storage';

Error: ./src/app/app.module.ts 17:74-92
"export 'IonicStorageModule' was not found in '@ionic/storage'

Ionic Info;

Ionic:

Ionic CLI : 6.15.0
Ionic Framework : @ionic/angular 5.6.7
@angular-devkit/build-angular : 0.1102.13
@angular-devkit/schematics : 11.2.13
@angular/cli : 11.2.13
@ionic/angular-toolkit : 3.1.1

Utility:

cordova-res : not installed
native-run : not installed

System:

NodeJS : v14.17.0
npm : 6.14.13
OS : macOS Big Sur

You are correct. I just tried to create an app using Cordova and these instructions. It fails to startup with lots of compilation errors. I'll look into fixing it.
Just curious, why do you want to use Cordova instead of Capacitor? The Ionic folks seem to recommend Capacitor over Cordova.

Can you please try the latest release (v4.1.2) and see if it fixes it?

Still we are getting same error
(base) kutti@init-mac-01 secure-ionic % ng add @oktadev/schematics --platform=cordova
ℹ Using package manager: npm
✔ Found compatible package version<EMAIL_ADDRESS>✔ Package information loaded.
The package<EMAIL_ADDRESS>will be installed and executed.
Would you like to proceed? Yes
✔ Package successfully installed.
Error: node_modules/capacitor-secure-storage-plugin/node_modules/@capacitor/core/types/definitions-internal.d.ts:16:18 - error TS2430: Interface 'CapacitorInstance' incorrectly extends interface 'CapacitorGlobal'.
Types of property 'Plugins' are incompatible.
Property 'SecureStoragePlugin' is missing in type '{ [pluginName: string]: { [prop: string]: any; }; }' but required in type 'PluginRegistry'.
16 export interface CapacitorInstance extends CapacitorGlobal {
~~~~~~~~~~~~~~~~~
node_modules/capacitor-secure-storage-plugin/dist/esm/definitions.d.ts:3:9
3         SecureStoragePlugin: SecureStoragePluginPlugin;
~~~~~~~~~~~~~~~~~~~
'SecureStoragePlugin' is declared here.
** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
✔ Browser application bundle generation complete.
60 unchanged chunks
Build at: 2021-05-25T06:27:00.747Z - Hash: 5edcdb266b9fe0697903 - Time: 1267ms
Error: node_modules/capacitor-secure-storage-plugin/node_modules/@capacitor/core/types/definitions-internal.d.ts:16:18 - error TS2430: Interface 'CapacitorInstance' incorrectly extends interface 'CapacitorGlobal'.
Types of property 'Plugins' are incompatible.
Property 'SecureStoragePlugin' is missing in type '{ [pluginName: string]: { [prop: string]: any; }; }' but required in type 'PluginRegistry'.
16 export interface CapacitorInstance extends CapacitorGlobal {
~~~~~~~~~~~~~~~~~
node_modules/capacitor-secure-storage-plugin/dist/esm/definitions.d.ts:3:9
3         SecureStoragePlugin: SecureStoragePluginPlugin;
~~~~~~~~~~~~~~~~~~~
'SecureStoragePlugin' is declared here.
ionic info
Ionic:
Ionic CLI                     : 6.15.0
Ionic Framework               : @ionic/angular 5.6.7
@angular-devkit/build-angular : 12.0.1
@angular-devkit/schematics    : 11.2.13
@angular/cli                  : 12.0.1
@ionic/angular-toolkit        : 3.1.1
Utility:
cordova-res : 0.15.3
native-run  : not installed
System:
NodeJS : v14.17.0
npm    : 6.14.13
OS     : macOS Big Sur

Hmmm, it works for me. Can you please try the following:
rm -rf node_modules
rm package-lock.json

Then, create an npm-shrinkwrap.json file and add the following to it:
{
  "dependencies": {
    "capacitor-secure-storage-plugin": {
      "version": "0.4.0",
      "dependencies": {
        "@capacitor/core": {
          "version": "2.4.7"
        }
      }
    }
  }
}

Then, run npm install and ionic serve to see if it works.

It's working. Thanks


Will not boot after installation

Stuck in shell. Always went back to Mojave image until I removed it. Now it simply doesn't boot.

@101arrowz have you upgraded VirtualBox to the latest version?  I've done it and haven't had any issues.

@101arrowz I spoke too soon.  It looks like VirtualBox can't boot from an APFS using EFI.  You can get around this by installing a driver but I found using this other script to be easier.  It already installs the driver plus everything else.


I would like to ask if i could have the source code before build

May I have the source code to build a custom relay switch for my garage that make use of a ultrasonic distance sensor to check whether the garage is open.
If yes you can contact me<EMAIL_ADDRESS>

Hi @dylanbarne,
Well... I didn't get your point. If you can explain more detail about what you are going to do, that would be brilliant.
Please feel free to ask me if you have any questions.

I want to build a component which uses and ultrasonic distance sensor to detect whether my garage is open and then uses that to set the garage to either the on or off position. I am unsure of how to use typescript for homebridge in combination with gpio. The documentation seems to be missing some important stuff. 😆 Thanks for any help you can give

For garage door I use https://www.npmjs.com/package/homebridge-gpio-garagedoor-d

Here is a typescript version of the garage door plugin - https://github.com/KraigM/homebridge-gpio-garagedoor
Feel free to message me if you have any questions.

Thank you so much, how does he turn on the gpio pin using typescript. In his code there is no specific point where he tells the raspberry to turn the pin on, this is the closest he gets


React 16

React 16 has been released.
This brings a lot of new really cool features. Let's discuss how(if) we can make use of things such as fragments, improved server-side rendering, error boundries etc.

And webpack 3 please! , What about react-router 4, does it work for server side rendering?

@againksy see https://github.com/reactGo/reactGo/pull/919

@GGAlanSmithee But why we dont have react-router-4 master?

@againksy I don't know, you'd have to ask the maintainers. There is an open PR (the one I linked) and another WIP by @choonkending, but I don't know the status of them.


[Feature Request]:[Go SDK] Improve "bad return type" messaging

What would you like to happen?
During analysis of DoFn types, when there's an issue with a type such as having an unencodable Exported field type, it can end up causing a message bad return type for <DoFn>: <type> but not including why it's a bad return type.
Message comes from here: https://github.com/apache/beam/blob/master/sdks/go/pkg/beam/core/funcx/fn.go#L468
Eg The following can trigger this message through this analysis.
type myRet struct{
  Error error // unencodable interface type as field type.
}

The complexity in fixing this though is that it may be possible that the wrapper type (myRet) has a coder registered for it, so it's permitted in this position. This might not be known at the functional Go type analysis level funcx operates on.
The ideal solution may be to change the analysis somewhat: The funcx analysis should return a list of suspect types, where they're coming from (this is critical), and why it's possibly a bad type, which a higher level validator can that inspect and validate against the higher level information (such as availability of coders for that type). This would prevent false rejections, and provide complete debugging information without iterating the pipeline one problem at a time.
But it would be sufficient to simply have the current message be more detailed about why the type is bad, instead of the current, less obvious situation.
Issue Priority
Priority: 3 (nice-to-have improvement)
Issue Components

[ ] Component: Python SDK
[ ] Component: Java SDK
[X] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

.take-issue


Use proper string types in database model

Currently all string types are text which is suboptimal for strings where we know the maximum character lengths (tokens for example) and which we perform searches on.

Turns out performance-wise it won't matter in PostgreSQL


feat: Debugging the creation and deletion of pods with configmap

What type of PR is this?

feat
What does this PR do?

Debugging the creation and deletion of pods with configmap
Which issue(s) does this PR fix?

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

/cc @wangyizhi1 @xyz2277

/approve

/lgtm


Initializing application settings from the server side

There is a need for angular application to load settings from the server when initializing, before it's bootstrapped. For example, application needs to know location of the token service, api service or anything else. This configuration is stored on the server in a file separate from the minified source code to simplify configuration changes.

What is the current behavior?
It would be natural to put this initalization code into Config or Run application methods. The problem is that any ajax request is asynchronous and there is no way to halt bootstraping.

As a workaround(example below) a manual call via XHR is made to the server and bootstrapping doesn't begin until:
a) Dom is loaded.
b) Server settings are loaded.
The code looks cumbersome. Additionally, there's no way to inject custom variable (server settings) into config, so higher scope variable is used to work around the issue.
CodePen: http://codepen.io/akoltsov/pen/PNqxVo
Pseudo code:
/**** START ****/
var SERVERSETTINGS = {}; // notice high scope
var app = angular.module('X');

var xhr = new XmlHttpRequest();
xhr.onload = function() {
  IsConfigLoaded = true;
  app.config(function(ConfigProvider) {
    // apply loaded settings in the app.
    ConfigProvider.Configure(SERVERSETTINGS); // extends default settings
    bootstrap();
  }
};
xhr.send();

angular.element(document).ready(function () {
  IsDomLoaded = true;
  bootstrap();
});

bootstrap() {
  if (IsDomLoaded and IsConfigLoaded) {
    angular.bootstrap(document, app.name);
  }
}

/**** END ****/

What is the desired behavior?
Is there a simpler way or we need a way to delay running of angular application until it's ready.

What is the motivation / use case for changing the behavior?
Ability to configure application from the server.

Which version of Angular, and which browser and OS does this issue affect? Did this work in previous
versions of Angular? Please also test with the latest stable and snapshot versions.
Any 1.x version.

Two suggestions:

Write the settings directly into the page from your server when you render it initially.  This is probably the best and most performant option, saving the user a round trip.

Use Promises.

const ready = new Promise(resolve => $(resolve));
const settings = fetch('/mySettingsUrl');

Promise.all([ ready, settings ]).then(() => {
  angular.bootstrap(document, app.name);
});

This is a dupe of https://github.com/angular/angular.js/issues/5854
and similar to
https://github.com/angular/angular.js/issues/4010
https://github.com/angular/angular.js/issues/4003
There are currently no plans to implement this, mainly because the workarounds for this specific problem aren't too horrendous.


Added BitLocker support for Plaso

Tested locally with BitlockerGo image by running
turbiniactl -C bitlocker -e /evidence/incoming/test.dd -r [recovery key]
turbiniactl -C bitlocker -e /evidence/incoming/test.dd -p [password]
This PR allows Plaso analysis on a BitLocker image without needing a large amount of local storage for the decrypted image, by using the --credential option provided by log2timeline.py. This is a stopgap until FUSE mounting is supported for a BitLocker image in #346.
There is a known issue with this approach: when an incorrect password was provided, the decrypting module (inside dfvfs) waits and asks for a valid password from stdin, which would block the processing.

Is this ready for review? or @ericzinnikas , did you want to take a look at this at all before I take a look?  Thanks!

Yes this is ready for review, but I think @ericzinnikas should have a look at it first.

LGTM. But there are a few refs to unencrypted_path / import tempfile / etc., that you can remove since we don't need a tempfile any more.

Fixed and ready for review

Also tested & this works. I was going to suggest adding support for recovery_key credential type but it doesn't seem like plaso supports that and I wasn't able to test manually -- so this seems good for now.

Great, I'll review this and the other BitLocker PR over the weekend.

Oh, sorry, can you make sure the tests are passing though?  It looks like you just need to run yapf on the code (example command should be in the output of the failed test).  Thanks!

Also, you probably know this already, but you can get 'yapf' through the 'dev' optional dependencies (e.g. pip install -e .[dev]).

@aarontp Oh right, forgot to run yapf for the last commit - will fix it now.

Thanks!


essential code should not be in assert's

The call to unloadLibrary() should not be in an assert, because when compiled with -release it gets elided.
This appears to be blocking https://github.com/D-Programming-Language/dmd/pull/5359 so please pull.

Why the move to assert(0)?

The call to unloadLibrary() should not be in an assert, because when compiled with -release it gets elided.

It's a unittest, so the asserts should always be compiled, right?

It gets compiled with -release, meaning the library does not get unloaded.

Auto-merge toggled on

Someone just recently told me asserts were run as soon as -unittest is passed. But I vaguely remember we have two assert variants for inside and outside of unittest blocks (and apparently only the former is run in release tests).

It sure seems like we should be running all this code in a unittest instead of in a main function.
I agree with moving the unload library out of an assert. Having any action inside an assert is a no-no. But the others are just checks of values.

Someone just recently told me asserts were run as soon as -unittest is passed. But I vaguely remember we have two assert variants for inside and outside of unittest blocks (and apparently only the former is run in release tests).

After being disabled with -release all asserts are reenabled with the -unittest switch: https://github.com/D-Programming-Language/dmd/blob/master/src/mars.d#L1087.
What's different in unittest blocks is that other functions are called instead of the usual assert: https://github.com/D-Programming-Language/dmd/blob/master/src/e2ir.c#L1904. Not sure what's the reasoning, though.


Loca Installation guide video.

fix issue #129
Under JWOC.
Update readme.md with local installation guide video.

its having some issues, raising new pr with all things,


Ref/insufficient funds

Closes #131

Coverage increased (+0.04%) to 95.76% when pulling 5d537afc603529f05b0c52c0dafa3dea134e109b on isocolsky:ref/insufficient_funds into a3e1fc68bb35c6339a23a47360ab1bd49a3c7d90 on bitpay:master.

well done!


Declare watching tasks without endsPattern

Reference https://github.com/ionide/ionide-vscode-fsharp/issues/412
I'm trying to use Webpack with a custom loader (fable-loader) together with Visual Studio Code tasks so the custom loader can highlight warnings and errors directly in the IDE. This is already working fine for single compilations, but not so well in watch compilations. The reason is VS Code task configuration requires both beginsPattern and endsPattern of a watch compilation in the output. However I cannot get Webpack to output a message at the end of a watch compilation after all warnings and errors have been displayed. (I've asked in Webpack forum and StackOverflow but didn't get a reply.)
Would it be possible to make the endsPattern optional? In this case, every time the beginsPattern occurs, VS Code would just reset all errors and warnings previously reported by the task an start over. That would be perfect for my use case.
Thanks a lot for your support and for the great tool!

Finally webpack is outputting messages at the start and end of recompilations so this can be closed :)

@alfonsogarciacaro , can you please provide link to this webpack feature.

@edvin It's not a feature in the sense you activate or deactivate it. Also, I couldn't find it in the Webpack releases. I just noticed that in latest Webpack version (2.4.1) when compiling in watch mode you get the following messages at the start and the end of each recompilation:
webpack: Compiling...

...

webpack: Compiled Successfully

Wrong edvin @alfonsogarciacaro - pinging  @edvinv just in case :)

Ups, sorry! 😅

@alfonsogarciacaro , thx but I see those two messages only in webpack-dev-server and not in webpack --watch. And also error messages (in my case ts-loader or awesome-typescript-loader) are generated after webpack: Compiled Successfully, so no way to detect compalation end.


Unable to delete Set inside a Transaction if a write operation is queued

Expected behavior
Be able to delete the key successfully (Redis can do that when using MULTI/EXEC.
Actual behavior
Redisson hangs out
org.redisson.transaction.TransactionTimeoutException: Transaction was discarded due to timeout 5000 milliseconds

Steps to reproduce or test case
The following (Kotlin) code reproduce the problem:
val transaction = redisClient.createTransaction(TransactionOptions.defaults())
val set = transaction.getSet<String>("set-transaction")
// If you remove the following line, the #delete works.
// If you change the operation to a read-only operation (ex. #contains), its works too
set.add("hello") // or set.remove("queue")
set.delete()
transaction.commit()

Redis version
7.2.3
Redisson version
3.24.3
Redisson configuration
val config = Config()
config.useSingleServer()
    .setAddress("redis://<IP_ADDRESS>:6379")
    .setDatabase(0)
    .setPassword("password")
    .clientName = "client"
this.redisson = Redisson.create(config)

@DiscowZombie did you find a solution to this?

@DiscowZombie did you find a solution to this?

No, but I have used the following workaround:
val transaction = redisClient.createTransaction(TransactionOptions.defaults())
val set = transaction.getSet<String>("set-transaction")
if (set.size == 1 && set.contains(key)) {
    set.delete()
} else {
    set.remove(key)
}
transaction.commit()


Spike use tsc for garn.ts

This is a POC of how we could get a better user experience by using standard typescript LSP when editing garn.ts files. This works well for me to get editor typechecking and autocompletion using typescript-language-server.
One thing that is nice about this solution is that it shouldn't affect an existing typescript repo's tsconfig at all since all we need to do is add a reference to our own tsconfig.json under .garn where we can have all of our conflicting rules.
The hard part here though is figuring out how to populate the ts-declarations dir. I think there are a few solutions here, but I don't really love any of them. Would love to see if anyone else has better ideas:

We could create a nix package with all of the typescript declarations going back to v0.0.1 and symlink .garn/ts-declarations to the nix store
We could package a zip of all the typescript declarations going back to v0.0.1 in the garn binary an extract it to the .garn dir when initializing a garn project
We could include a package.json in the .garn directory that when running npm install in there the user gets type declarations for the specified version. It is then up to the user to keep the version in package.json up to date.

Closing for now until we decide to pick up this issue again.


Bodhi updates for development branches show as "skipped" and are not linked.

What happened? What is the problem?
Bodhi updates for development branches (f40 and rawhide at the time of writing) are displayed as "skipped" in the new Bodhi Update job section added in #215: https://dashboard.packit.dev/jobs/bodhi-updates
I'm not sure what "skipped" means in context for Packit but, for example:
https://dashboard.packit.dev/results/bodhi-updates/266
https://dashboard.packit.dev/results/bodhi-updates/265
Alias "not provided" and Update Creation Time "not provided", but the Bodhi updates are actually created by Packit:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-289a641391
https://bodhi.fedoraproject.org/updates/FEDORA-2024-75d641297c
What did you expect to happen?
Development branch updates come through with "success" and a link to the Bodhi update is provided.
Example URL(s)
https://dashboard.packit.dev/jobs/bodhi-updates
Steps to reproduce
1. GOTO https://dashboard.packit.dev/jobs/bodhi-updates
2. Inspect any `f40` or `rawhide` update
3.

Workaround

[ ] There is an existing workaround that can be used until this issue is fixed.

Participation

[X] I am willing to submit a pull request for this issue. (Packit team is happy to help!)

Well, I said there is no workaround but one can simply go to Bodhi and look for the update (which is what I did). I knew it existed because the version bump Bugzilla was updated with links to both updates: https://bugzilla.redhat.com/show_bug.cgi?id=2265008

hi @ckelleyRH ! Thanks for this issue.

but the Bodhi updates are actually created by Packit

Even though Bodhi UI shows that they were created by packit user, those are actually triggered automatically, see the docs. Therefore from Packit side, there is really no submission time or anything. You can also see This update was automatically created in the update detail you linked.
I get your point it might not be clear looking at our dashboard and am wondering what could we improve since ideally, we want to display only actions that were really triggered/processed by Packit. We could definitely at least provide this explanation in the dashboard.

I get your point it might not be clear looking at our dashboard and am wondering what could we improve since ideally, we want to display only actions that were really triggered/processed by Packit. We could definitely at least provide this explanation in the dashboard.

If we're saying that we only want to show updates that were actually generated by Packit, rather than just looking like they were to the untrained observer, then perhaps development branch updates shouldn't be displayed at all? I wouldn't have thought about this at all probably if they weren't displayed, I would have just seen the bug closed due to the update going straight to stable and moved on.

We usually suggest to put in the bodhi_update job definition the fedora-branched alias as a target. Because bodhi updates are triggered automatically for the development branches. And for this reason we got an error.

Yes, I can go through and update all the configurations so that this doesn't happen at all, thanks for the pointer!

@majamassarini - does fedora-branched include f40 (I expect it does)? If so, even if I fix my configs to not build for rawhide, it will still trigger this behaviour for f40 right?

yes, it should include f40. This behaviour puzzled me too (the automatic update for f40). I think this could be something temporary since the branching has happened not so long ago. But let's see what others say (@lbarcziova or @lachmanfrantisek).

Yes, this should be only temporary, until it reaches Updates-testing Activation, after that, the updates for f40 will not be created automatically.

Yes, this should be only temporary, until it reaches Updates-testing Activation, after that, the updates for f40 will not be created automatically.

Currently I have a basically identical Packit set up in every repo like this:
jobs:
- job: pull_from_upstream
  trigger: release
  dist_git_branches:
    - fedora-development

- job: koji_build
  trigger: commit
  dist_git_branches:
    - fedora-development

- job: bodhi_update
  trigger: commit
  dist_git_branches:
    - fedora-development

So I want to only do rebases in rawhideand if there is an embryonic stable branch like f40 is now, I want that rebase in that branch too - hence fedora-development.
If I am to not create the Bodhi update for rawhide, which I agree is unnecessary, to what can I change fedora-development? There doesn't appear to be a sensible way of doing this...

If I am to not create the Bodhi update for rawhide, which I agree is unnecessary, to what can I change fedora-development? There doesn't appear to be a sensible way of doing this...

I am not sure I am following you. I think you simply don't need a Packit bodhi_update job.

If I am to not create the Bodhi update for rawhide, which I agree is unnecessary, to what can I change fedora-development? There doesn't appear to be a sensible way of doing this...

I am not sure I am following you. I think you simply don't need a Packit bodhi_update job.

I think I may be just confused, but it doesn't matter anyway because the team has decided to use fedora-rawhide and drop bodhi-update so this all goes away for us. Thanks for answering the scope creep questions (sorry)!


adding modalboxes to emotions

1. Why is this change necessary?
adds possibility to open modal boxen from emotions
2. What does this change do, exactly?
see #1
3. Describe each step to reproduce the issue or behaviour.
add default modal code into emotions and try to click the link.. it will open in the same window instead of opening the modal box
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[ ] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-22356
Please use this issue to track the state of your pull request.

Hi @alea123, thank you very much for your contribution! 💙


No Connect() function on client.Client, How to connect?

This API has changed since the last time I used it. But I noticed there is no longer a Connect() function and I am getting a "Connection Closed" error when trying to use.  Could you provide an example on how to connect? I'd be happy to contribute to the README file here with an example once I get it working.
Steps:

Run docker image eventstore/eventstore:20.6.0-buster-slim in dev mode.
Install the go sdk github.com/EventStore/EventStore-Client-Go v0.0.0-20210901083018-267dadb3ad6f
Connect with:

	log.Println("starting app")
	config, err := eventClient.ParseConnectionString(connString)
	if err != nil {
		log.Fatalf("could not create client configuration: %s", err.Error())
	}
	log.Printf("Config = %v", config)

	client, err := eventClient.NewClient(config)
	if err != nil {
		log.Fatalf("could not create client: %s", err.Error())
	}
	// client.Connect() ???
	// err = client.CreatePersistentSubscription(context.Background(), persistent.SubscriptionStreamConfig{})
	// if err != nil {
	// 	log.Fatalf("could not connect to client: %s", err.Error())
	// }
	defer client.Close()

Make an appendToStreamCall
Error returned "Could not construct append operation. Reason: rpc error: code = Unavailable desc = connection closed"

Thanks,
Nolan

I was using the incorrect docker container.
 eventstore/eventstore:21.6.0-buster-slim is what this sdk is being tested against.
I get another error when running the append function, but I'll open a new ticket.

Hi there.
The Go client test suite is running "20.6" version of the server no problem. The version is not the issue here. About your initial question, there is no Connect function. The 'real' connection is done internally and automatically.

Hi there. Thank you for your response. After reviewing the source code, I came to that realization and I appreciate you taking the time respond and confirm that. My second issue was of my own doing again, my slice of events had an empty element because I misused the make() function syntax. When I corrected my payload, things worked as normal.
Thank you again,
Nolan


[Outlook] (manifest) relation of module extension to JSON manifest

Besides the work in the PR title, this also fixes an erroneous claim in the article.

Docs Build status updates of commit 26dc29c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/outlook/extension-module-outlook-add-ins.md
:warning:Warning
View
Details

docs/outlook/extension-module-outlook-add-ins.md

Line 13, Column 178: [Warning: file-not-found - See documentation] Invalid file link: '../microsoftteams/platform/m365-apps/extend-m365-teams-personal-tab.md'.
Line 32, Column 497: [Warning: file-not-found - See documentation] Invalid file link: 'initialize-add-in.md'.
Line 32, Column 572: [Warning: file-not-found - See documentation] Invalid file link: '../javascript/api/office/office.addincommands.event'.
Line 32, Column 572: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL.  Otherwise, remove the view parameter. URL: ../javascript/api/office/office.addincommands.event?view=common-js-preview#office-office-addincommands-event-completed-member(1)

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 42d8a25:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/extension-module-outlook-add-ins.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1cab7c5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/extension-module-outlook-add-ins.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Is there a typo in line 11?

https://github.com/Aidlab/aidlab-python-examples/blob/e8e8db3a59488ae1f72b0fed3c2c26397e798a08/Aidlab/data.py#L11

Can you paste exact problem you are encountering here?

it's been too long and I haven't looked since... I believe the problem was something about the code referencing the directory structure incorrectly

I am closing it now as we've made some improvements here. Feel free to reopen this issue if the problem will happen again.


Decide on tech stack

Probably Python
Thoughts:
Gameloop - custom
Visualisation - pygame
Training - stablebaselines3?
How do we store models? They should be accessible from anywhere
We also want metadata about them

Stack:

Python
Pygame


Can't access to curl http://localhost:8090

Fail to curl http://localhost:8090

docker containers have all started

You should make this issue to delta-all-in-one repo. Close this issue.

A workaround:
use ssh local port forwarding
ssh -fNt -L 8090:{your-server-ip}:8090 {your-server-ssh-name}
or just edit your host file to make localhost resolved to your server ip.

This is the same as deltaboard#51