Bug report:  spo report returns TypeError: Cannot read property 'trim' of undefined

receiving another UnhandledPromiseRejectionWarning:
> m365 spo report activityuserdetail --period D180 --output json > foo.json
(node:17644) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'trim' of undefined
    at SpoReportActivityUserDetailCommand.getReport (C:\Users\z003292x\AppData\Roaming\npm\node_modules\@pnp\cli-microsoft365\dist\m365\base\PeriodBasedReport.js:47:32)
    at C:\Users\z003292x\AppData\Roaming\npm\node_modules\@pnp\cli-microsoft365\dist\m365\base\PeriodBasedReport.js:24:41
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:17644) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:17644) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

> m365 version
"v4.1.0-beta.85537cc"

a similar error happens with
m365 spo report siteusagedetail
as well

I also can't reproduce the issue. (Windows 10)

It's unfortunately our production tenant with >250.000 SC.  The output when including --debug is
> m365 spo report activityuserdetail --period D180 --output json --debug > foo.json
Executing command spo report activityuserdetail with options {"options":{"period":"D180","output":"json","debug":true}}
Existing access token XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX still valid. Returning...
Request:
{
  "headers": {
    "common": {
      "Accept": "application/json, text/plain, */*"
    },
    "delete": {},
    "get": {},
    "head": {},
    "post": {
      "Content-Type": "application/x-www-form-urlencoded"
    },
    "put": {
      "Content-Type": "application/x-www-form-urlencoded"
    },
    "patch": {
      "Content-Type": "application/x-www-form-urlencoded"
    },
    "user-agent": "NONISV|SharePointPnP|CLIMicrosoft365/4.1.0-beta.85537cc",
    "accept-encoding": "gzip, deflate",
    "accept": "application/json;odata.metadata=none",
    "authorization": "Bearer XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
  },
  "decompress": true,
  "responseType": "json",
  "url": "https://graph.microsoft.com/v1.0/reports/getSharePointActivityUserDetail(period='D180')",
  "method": "get"
}
Response:
{
  "status": 200,
  "statusText": "OK",
  "headers": {
    "cache-control": "no-store, no-cache, max-age=0, s-maxage=0, private",
    "pragma": "no-cache",
    "transfer-encoding": "chunked",
    "content-type": "application/octet-stream",
    "etag": "\"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=\"",
    "server": "Microsoft-IIS/10.0",
    "x-xss-protection": "1; mode=block",
    "x-content-type-options": "nosniff",
    "strict-transport-security": "max-age=31536000; includeSubDomains",
    "x-frame-options": "Deny",
    "content-security-policy": "frame-options",
    "requestid": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
    "content-disposition": "attachment; filename=\"SharePointActivityUserDetail10/20/2021 5:59:32 PM.csv\"",
    "x-powered-by": "ASP.NET",
    "date": "Wed, 20 Oct 2021 17:59:32 GMT",
    "connection": "close"
  }
}
(node:22104) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'trim' of undefined
    at SpoReportActivityUserDetailCommand.getReport (C:\Users\z003292x\AppData\Roaming\npm\node_modules\@pnp\cli-microsoft365\dist\m365\base\PeriodBasedReport.js:47:32)
    at C:\Users\z003292x\AppData\Roaming\npm\node_modules\@pnp\cli-microsoft365\dist\m365\base\PeriodBasedReport.js:24:41
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:22104) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:22104) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Closing due to lack of response.


Crashes & Performance issues while using CeTZ-Plot

Describe the bug
Hello, I have been using tinymist in VSCode for some time, but finally did the switch to neovim.
I hoped that the problems will go away, but it seems that tinymist is the issue.
When I enter a .typ file, the tinymist starts and it takes good seconds before it responds to any input, which I guess would be expected, considering that typst takes a little less to compile it. I am using the CeTZ-Plot package for plotting graphs, currently working on file with 7 graphs (in sum ~2.3k points) so there's stuff going on, but it still is just a few pages.
My first problem is the performance when editing: i.e. when I type a variable name, it grabs the first letter, says: "unknown variable" for few seconds before it updates, or the variable content popups take a long time, and in that time things like go-to-definition don't work, as the server is processing the previous action. Sometimes it seems like it gets stuck calculating something that I already changed, before it can notice that it changed. It works quickly right now as I am writing this issue, as it has time to go idle, but when editing it often gets behind.
Second problem are the semi-frequent crashes, see the included log.
Also, the highlighting of #function  sometimes overflows and highlights a few characters in front of the #, but that's not my main point.
If there are any more logs needed or something I could do, I can try. I just want to report the rust panic and point out performance issues when using the plot package.
Package/Software version:
NVIM v0.10.2
Build type: RelWithDebInfo
LuaJIT 2.1.1727870382
(on Arch Linux)

Logs:
These are the last 3 lines from ~/.local/state/nvim/lsp.log after one tinymist crash, with rust panicking in the last
[ERROR][2024-11-22 11:25:59] .../vim/lsp/rpc.lua:770	"rpc"	"/home/sukulent/.local/share/nvim/mason/bin/tinymist"	"stderr"	"[2024-11-22T10:25:59Z INFO  sync_lsp] handling textDocument/documentHighlight - (319) at Instant { tv_sec: 1967, tv_nsec: 584135220 }\n"
[ERROR][2024-11-22 11:25:59] .../vim/lsp/rpc.lua:770	"rpc"	"/home/sukulent/.local/share/nvim/mason/bin/tinymist"	"stderr"	"[2024-11-22T10:25:59Z INFO  sync_lsp] handled  textDocument/documentHighlight - (319) in 95.78µs\n"
[ERROR][2024-11-22 11:25:59] .../vim/lsp/rpc.lua:770	"rpc"	"/home/sukulent/.local/share/nvim/mason/bin/tinymist"	"stderr"	"[2024-11-22T10:25:59Z INFO  sync_lsp] notifying textDocument/didChange - at Instant { tv_sec: 1967, tv_nsec: 846758483 }\nthread 'main' panicked at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14/library/alloc/src/vec/mod.rs:2207:36:\nslice index starts at 21186 but ends at 21139\nnote: run with `RUST_BACKTRACE=1` environment variable to display a backtrace\n"

Hello, thank you for submitting the issue. There are two points to solve before we discuss them:

you seems to be putting multiple issues in a single issue, making it difficult to solve them one by one.
Neither source code triggering the issues nor the steps to reproduce. You also didn't provide the settings and configuration about tinymist. So we only know there are issues encountered on your side but we cannot step in and investigate them on our side.

You could check the closed issues about neovim to learn how to solve above points.
Short note: Specific to slow completion with using large packages like cetz, we have improved the cache efficiency on analyzing source code in packages in 0.12.4, you could upgrade and check them again.


Version deployment config release for Helm charts

Hey team! Please add your planning poker estimate with Zenhub @dbadham-fr @shaunharrisonFR


New feature: Send notification

Hello, I want to send a notification to my Panasonic Viera.
I can develop it in python, but I don't know where I can found some information/API endpoint to do that.
Do you have any idea how to do that ?
Thanks !

There isn't any public API AFAIK. But wireshark is your pall 👍

Unfortunately, there is no public API. Wireshark will probably be your only solution to reverse engineer the endpoint.

Messaging via HDMI CEC could be an option..
http://events17.linuxfoundation.org/sites/events/files/slides/cec-elce2016.pdf


Memory Leak

There seem to be some memory leak issues which are causing some problems on long-running tasks.

After fix, it seems there is still an issue further exploration required.

Seems I was mistaken. Will close this now and can open a new one later if another problem pops up.


[Tour of Beam] Learning content for "Introduction" module

fixes #22497

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @sirenbyte

R: @kerrydc


Update README.md

What does this PR do?
I just fixed "window.opener.postMessage" as in https://appwrite.io/docs/getting-started-for-flutter
Have you read the Contributing Guidelines on issues?
Yes

THANK YOU! All changes merged 🥳
Please reach out to me on our Discord server if you would like to claim your Appwrite swags! As a way of saying thank you, we would also love to invite you to join the Appwrite organization on GitHub. Please share your GitHub username with us on Discord.
You can accept the invite by visiting https://github.com/orgs/appwrite/invitation. By joining our team, you will officially be an Appwrite maintainer on GitHub.
You can change your membership visibility settings, so your new Appwrite team membership badge will show up on your personal GitHub profile.
Please feel free to look for more PRs you might be interested in helping with on our long list of Hacktoberfest friendly issues and help make Appwrite better :)


Exhaustiveness check fails on types with a literal field

Bug Report

🔎 Search Terms

exhaustiveness check, type alias
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about exhaustiveness checks

⏯ Playground Link

Playground link with relevant code
💻 Code

type Circle = {
  kind: "circle";
  radius: number;
}

function getArea(circle: Circle) {
  switch (circle.kind) {
    case "circle":
      return Math.PI * circle.radius ** 2;
    default:
      const _exhaustiveCheck: never = circle;
      return _exhaustiveCheck;
  }
}

🙁 Actual behavior
An error is reported on the _exhaustiveCheck assignment: Type 'Circle' is not assignable to type 'never'.
🙂 Expected behavior
No error to be reported, as all possible instances of Circle have circle.kind === "circle", which is covered by the first switch case

Duplicate of #18056.  A single type isn't considered to be a union so discriminated union narrowing doesn't work.  This code does work in general, as long as you have more than one possibility:
Playground
Workaround for cases where there really is only one kind: Union the type with { kind: never }.


Cell boundaries

Hi there,

Please note I've only used Hydrogen with IJavascript so I'm not sure if my observations only apply to this combination.

I think I understand that compared to a Jupyter notebook, it's difficult for Hydrogen to determine the boundaries of cells to enable the display of intermediary computation results in Atom when the whole notebook is ran? Is that the reason why intermediary results aren't displayed or updated?
For languages (like Javascript) where an optional line delimiter (;) can be used, wouldn't it be possible to use the presence of the delimiter as a cue to render the cell?
For other cases, or in addition to this, maybe Hydrogen could remember where existing cell runs have been requested and when a run all command is issued, it would update these bubbles (it seems that currently - with IJavascript - its only updating the final checkmark).
I guess that the more general case is to try to introspect the code to define the appropriate cell boundaries. This seems almost like something that would fit in a Kernel extension if there was interest upstream in allowing this type of freeform notebook.
Let me know if that's unclear and I can explain more visually what I'm suggesting.
Cheers!
Jun

Just had a thought that this might allow to copy paste in between Jupyter and Hydrogen!

We haven't documented this yet, but Hydrogen already provides the option to define code cell (see #328 ). The relevant commands are hydrogen:run-cell and hydrogen:run-cell-and-move-down.

@lgeiger Perhaps, we need to add a command to run all cells, e.g. hydrogen:run-all-cells.

Is it supposed to work with IJavascript?
I'm trying this

In Javascript, cell boundaries are marked by:
// %%

In general, for any other language, one has to use the syntax of that language to write comments.

Oops, now I see it was specified in the pull request.
Sorry but I've never used this feature before and I'm fairly new with Jupyter. I can't make it work.
Is // %%is equivalent to // <codecell> and // In[12]?
Where should I place the code to execute? Is there an opening of the boundary and a closing of it? 😲
Here are my feable attempts:
// %%
x = 2

// In[1]
y = 2+2

// In[2]
z = x-2

// <codecell>
// t = "in the comments??"

On 23/07/16 23:17, Jun Matsushita wrote:

Oops, now I see it was specified in the pull request.
Sorry but I've never used this feature before and I'm fairly new with Jupyter. I can't make it work.

We really need to document this.

Is |// %%|is equivalent to |// | and |// In[12]|?

Yes, they are equivalent.

Where should I place the code to execute? Is there an opening of the boundary and a closing of it? 😲

At the moment there are only two commands to run code cells:
-hydrogen:run-cell
-hydrogen:run-cell-and-move-down
Your example defines three code cells:

x = 2
y = 2+2
z = x-2

If the cursor is between // %% and // In[1] when the command hydrogen:run-cell is invoked, then the first cell will be executed.
If the cursor is between // In[1] and // In[2] when the command hydrogen:run-cell-and-move-down is invoked, then the second cell will be executed, and the cursor will be moved down to the third cell.
The first // %% and the last // <codecell> aren't necessary, Hydrogen assumes the first cell starts at the beginning of the file, and the last cell finishes at the end of file.

Perhaps, we need to add a command to run all cells, e.g. hydrogen:run-all-cells.

I would suggest we add this behavior to hydrogen:run-all rather than adding a new command for this. I'll make a PR next week.

We really need to document this.

@n-riesco I would really appreciate if you could add this to the readme since my written english isn't that great.

On 24/07/16 13:48, Lukas Geiger wrote:

I would suggest we add this behavior to |hydrogen:run-all| rather than adding a new command for this. I'll make a PR next week.

+1

We really need to document this.

@n-riesco https://github.com/n-riesco I would really appreciate if you could add this to the readme since my written english isn't that great.

Thanks! I'll try my best and add it to the readme next week 😉

Thanks so much for the explanation! I really appreciate your time and effort. Hydrogen is great! I also found a bug :)

Oh and +1 to adding the behaviour to hydrogen:run-all !


fix create-per-test missing default value

ref: https://github.com/github/orchestrator/issues/691

Clarified on #691


test(api-client): fix flaky socketio-api-client.test

Describe the bug
The packages/cactus-api-client/src/test/typescript/unit/socketio-api-client.test.ts appears to be failing intermittently.
To Reproduce
Run it through the CI enough times to make it fail. Observe that it works sometimes and not other times.
Expected behavior
Tests should be stable, e.g. always failing or always succeeding with a given revision of the code.
Logs/Stack traces
Summary of all failing tests
FAIL packages/cactus-api-client/src/test/typescript/unit/socketio-api-client.test.ts (15.777 s)
SocketIOApiClient Tests › Sync Request Tests › Returns decoded response from the validator

thrown: "Exceeded timeout of 3000 ms for a hook.
Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

    276 |
    277 |   describe("Sync Request Tests", function () {
> 278 |     beforeEach(async () => {
        |     ^
    279 |       // Connect client and server sockets
    280 |       testServer.on("connection", (socket) => {
    281 |         log.debug("Server socket connected", socket.id);

    at packages/cactus-api-client/src/test/typescript/unit/socketio-api-client.test.ts:278:5
    at packages/cactus-api-client/src/test/typescript/unit/socketio-api-client.test.ts:277:3
    at Object.<anonymous> (packages/cactus-api-client/src/test/typescript/unit/socketio-api-client.test.ts:196:1)

Cloud provider or hardware configuration:
GitHub Action Runner for the Cactus CI
Operating system name, version, build:
Ubuntu-20.04
Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
1.0.0-rc.3
@outSH

@petermetz
I've just executed this test over 800 times on local VM and didn't find any errors, I assume this is probably due to periodic low performance of CI environment. I've increased the timeouts for all tests (3s -> 5s), and separate setup timeout (3s -> 1 minute). Let's see if this solves the issue :)

@outSH Great! Thank you very much! I agree, I'm pretty sure that the free VMs we get allocated for the GitHub CI jobs are heavily throttled in the hypervisor level somehow so they are probably pretty "weak" even compared to a regular laptop.


Gzip support.

Would be nice to have an option to prefer sending gzipped versions of files.

Add the compression middleware before this middleware (https://github.com/expressjs/compression).

@dougwilson thats a fine solution, and my current one. I was under the impression that it was more performant to serve pre gzipped files and thought it would be a good feature for this lib.

It is never performant to serve static files from Node.js, because all file I/O uses a small thread pool. Many modules currently exist on npm and there is a PR with some initial ideas about adding it here I have not yet looked at enough besides to say it's missing some error handing that will crash the server.

The module https://github.com/code42day/connect-gzip-static is a good one, and even uses the same core modules this module does.

@dougwilson I think this can rather be meant a little differently. E.g. why not caching gzipped buffers after first read, instead of always streaming the file. This would only take some boilerplate with node core libs. The only non-straightforward thing is to not to allow certain clients (like older IE versions) to retrieve gzip data streams, as they can't accept it properly.
The behaviour could be only enabled with an option flag.
This would mitigate the typical node caveat you mentioned by a lot.
I think it's worth having it in the ecosystem.


Upgrade all dependencies

Package name
This package internet_file is 2 years old (2022) and is used with  pdfx: ^2.7.0 (2024) making both incompatible with most of google and firebase dependencies : example :

Because google_fonts >=4.0.5 depends on http ^1.0.0 and every version of internet_file depends on http ^0.13.4, google_fonts >=4.0.5 is incompatible with internet_file.
So, because admin depends on both google_fonts ^6.1.0 and internet_file any, version solving failed.

package internet_file: ^1.2.0 published on pub.dev has  http ^0.13.4, dependency while the same version coming from github repository has a proper  http ^1.0.0 version


(GH-620) Fix showing selected source after editing source.

Changed SelectedItem to CurrentItem
SelectedItem is not getting updated after change to any source, I'm not sure why.
Added DraftSource to prevent updating SelectedSource if save button was not clicked.
Disabled multi select.

Relates to #620

@DamianMaslanka5 apologies for not getting to this sooner, I am only just seeing it now.
I have just taken this for a spin, and on the whole, it looks good, however, I am seeing one issue with this change.  If I do the following:

select a source, make a change, and then save it
click a different source
click back onto the source that was changed
click on the same different source

Then I get the following exception:

I haven't had a chance to dig into this yet, but I thought I would respond here in case you knew immediately what the problem is.

@gep13 No problem. I fixed the issue and i found source of the bug. DataGrid is using GetHashCode and Equals but in ChocolateySource these methods are overriden and you probably know that if property is mutable it shouldn't be used in GetHashCode. If we don't modify the source directly it works well. If it looks good for you let me know and I will squash the commits, or you can do it.

@DamianMaslanka5 I have just taken this for a spin, and it is now working perfectly.
Thank you again for taking the time to do this!


Rename to s2s-handler-{babel,typescript}

Coverage remained the same at 95.346% when pulling 789c749dfe6a2a9346aa43a13600a5a2fc65d1a8 on rename-handler into d34324814be0830c21ac9a41558d0b1332a6eb13 on master.


added DivideTwoNumbers.cpp

Why:
Closes #108
What's being changed:
added DivideTwoNumbers.cpp

hi @hi-Kartik2004 ! I didn't use "using namespace std" on purpose. this is an issue that has been answered in StackOverflow that explains it.


python311Packages.uiprotect: 1.1.0 -> 1.7.2

Diff: https://github.com/uilibs/uiprotect/compare/refs/tags/v1.1.0...v1.7.2
Changelog: https://github.com/uilibs/uiprotect/blob/refs/tags/v1.7.2/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 319921 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.unifiprotect
python311Packages.uiprotect
python311Packages.uiprotect.dist
python312Packages.uiprotect
python312Packages.uiprotect.dist


Optionally exclude input geom from results

Resolves #1106

Coverage increased (+0.02%) to 85.49% when pulling 454a01c3313b21c6b4b3c49b343ede1242e9d717 on issue1106 into 1fc769f2d16ec7e8e4c8034b46b12f7271d54c47 on master.


Documentation updates

Some updates to the documentation about the concurrency flags to (hopefully) make their function clearer.

Thanks !


Reduce content in Success banner

This tweaks the success message shown when submitting to:

remove the duplicate word "successfully" (banner already has the title "Success")
remove the line about receiving emails from the banner and move it to body text, so that it'll be shown even on later page loads
change "when something changes" to "when the provider makes a decision" to be more specific.

Technically you'll also be emailed about other changes, eg being rejected automatically, invited to an interview, or being withdrawn (at your request) but those don't feel like they need to be explicitly mentioned.
🗂 Trello card
Screenshots
Before

After

 Improve our success messaging when a candidate submits an application


Report problem for remote script

@bot-gradle test ACC

OK, I've already triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build


How to scale Landmark points relative to the texture size in v0.8.0

Hi @homuler ,
I am using pose tracking solution and want to scale the resulting Normalized landmarks.
I saw your are using this code and the scaling vector is (100,100,100) but when I scale them myself using GetLocalPositionNormalized(...) with same scale I am not getting correct mapping over the canvas.
I also try to scale it using texture width and height:
textureWidth = textureFrame.width;
textureHeight = textureFrame.height;

Is there anything additionally you are doing or should I change scaling vector?
Scaling in V0.0.6 was much easier, like this example I made few weeks ago.
Thanks,
Arham

the scaling vector is (100,100,100)

Do you mean this code?
https://github.com/homuler/MediaPipeUnityPlugin/blob/a3b90d13eac636ff837d52723eaa6f0046adb459/Packages/com.github.homuler.mediapipe/Runtime/Scripts/Unity/Annotation/PoseWorldLandmarkListAnnotationController.cs#L15

Yes

PoseWorldLandmarkListAnnotationController is used to annotate pose_world_landmarks, which is LandmarkList, not NormalizedLandmarkList.
pose_world_landmarks uses real-world 3D coordinates in meters and not proportional to the size of the input image.
This is why PoseWorldLandmarkListAnnotationController has predefined _scale vector.

x, y and z: Real-world 3D coordinates in meters with the origin at the center between hips.

If you want to know the position on the input image, you need to use pose_landmarks.

x and y: Landmark coordinates normalized to [0.0, 1.0] by the image width and height respectively.

The current ImageCoordinate API is not very good and requires a RectTransform argument (receiver to be precise) to represent the dimension of the input image.
https://github.com/homuler/MediaPipeUnityPlugin/blob/bed2f478eddf3b8be106adcc2044e576e8337e22/Packages/com.github.homuler.mediapipe/Runtime/Scripts/Unity/CoordinateSystem/ImageCoordinate.cs#L271-L282

Got it so (100,100,100) is used only for world landmarks, but where did you pass RectTransform rectTransform in GetLocalPosition function?
Here you just passed the target, rotationAngle and isMirrored. if I get to know the value of rectTransform then I think this will work for me as well.
https://github.com/homuler/MediaPipeUnityPlugin/blob/a3b90d13eac636ff837d52723eaa6f0046adb459/Packages/com.github.homuler.mediapipe/Runtime/Scripts/Unity/Annotation/PointAnnotation.cs#L65
The plugin needs some documentation, let me know how I can contribute for this?

Looks like the RectTransform is coming from here:
https://github.com/homuler/MediaPipeUnityPlugin/blob/a3b90d13eac636ff837d52723eaa6f0046adb459/Packages/com.github.homuler.mediapipe/Runtime/Scripts/Unity/Annotation/HierarchicalAnnotation.cs#L35
Could you please explain how I can define or calculate my own RectTransform?
Thanks

If it's OK, please just add RectTransform to the GameObject where the input image is displayed.
In the sample app, RectTransform is attached to Annotatable Screen from Add Component menu (note that RawImage is also attached to it).

As for the annotation, the child GameObject called Annotation Layer also has a RectTransform attached to it, which is actually referenced by Hierarchical Annotation (but in your case, I think you don't need to create a child GameObject like this).
https://github.com/homuler/MediaPipeUnityPlugin/blob/a3b90d13eac636ff837d52723eaa6f0046adb459/Packages/com.github.homuler.mediapipe/Runtime/Scripts/Unity/Annotation/AnnotationController.cs#L11-L19
https://github.com/homuler/MediaPipeUnityPlugin/blob/a3b90d13eac636ff837d52723eaa6f0046adb459/Packages/com.github.homuler.mediapipe/Runtime/Scripts/Unity/Annotation/AnnotationController.cs#L58-L64
However, as I wrote in https://github.com/homuler/MediaPipeUnityPlugin/issues/367#issuecomment-985094266, the current API is not very good, so I'm planning to change it so that we can call like this:
// var position = GetAnnotationLayer().GetLocalPosition(target, rotationAngle, isMirrored);
var position = target.GetLocalPosition(inputWidth, inputHeight, rotationAngle, isMirrored);

I think I am doing something wrong here in scaling:
Here is what I did in PoseTracking solution:
in Run function:
rectTransform = GameObject.Find("Annotatable Screen").GetComponent<RectTransform>();

Then once I got the NormalizedLandmark I scale them using these functions using rectTransform :
public static Vector3 GetLocalPositionNormalized(RectTransform rectTransform, float normalizedX, float normalizedY, float normalizedZ, float zScale, RotationAngle imageRotation = RotationAngle.Rotation0, bool isMirrored = false)
        {
            var rect = rectTransform.rect;
            var isInverted = IsInverted(imageRotation);
            var (nx, ny) = isInverted ? (normalizedY, normalizedX) : (normalizedX, normalizedY);
            var x = IsXReversed(imageRotation, isMirrored) ? Mathf.LerpUnclamped(rect.xMax, rect.xMin, nx) : Mathf.LerpUnclamped(rect.xMin, rect.xMax, nx);
            var y = IsYReversed(imageRotation, isMirrored) ? Mathf.LerpUnclamped(rect.yMax, rect.yMin, ny) : Mathf.LerpUnclamped(rect.yMin, rect.yMax, ny);
            var z = zScale * normalizedZ;
            return new Vector3(x, y, z);
        }

        public static Vector3 GetLocalPositionNormalized(RectTransform rectTransform, float normalizedX, float normalizedY, float normalizedZ, RotationAngle imageRotation = RotationAngle.Rotation0, bool isMirrored = false)
        {
            // Z usually uses roughly the same scale as X
            var zScale = IsInverted(imageRotation) ? rectTransform.rect.height : rectTransform.rect.width;
            return GetLocalPositionNormalized(rectTransform, normalizedX, normalizedY, normalizedZ, zScale, imageRotation, isMirrored);
        }

these functions returning the position based on the world coordinate (inside 3D Room).
Am I using the correct functions to scale my normalized coordinates?

Will you describe more clearly

what you want to do?

I'd thought you were trying to overlay something on the image, so I don't know why you're referring to 3D Room

what you're doing now?

the code above does not include the definition of PoseUtils#prepareLandmarks and where normalizedLandmarkList comes from

what's currently not working as expected?

screenshots or text logs, etc... may help us to understand the situation

P.S. You don't need to copy and paste GetLocalPositionNormalized. Just add using Mediapipe.Unity.CoordinateSystem; to the source file and you can call it like rectTransform.GetLocalPosition(...).

what you want to do?
I am trying to scale the landmarks as you did with Point annotations.
what you're doing now?
I am trying to scale landmark points using your utility functions, in PoseUtils.prepareLandmarks I am looping through the landmarks and then scaling them using GetLocalPositionNormalized function then returning the scaled list. I have just updated the code for PoseUtils#prepareLandmarks in the above thread.
what's currently not working as expected?
My landmark points are not scaling as expected.
I tried this approach as you said:
// in PoseTrackingSolution
rectTransform = GameObject.Find("Annotatable Screen").GetComponent<RectTransform>();
landmarkModels = PoseUtils.prepareLandmarks(normalizedLandmarkList, rectTransform);

// In my PoseUtils
public static List<LandmarkModel> prepareLandmarks(NormalizedLandmarkList normalizedLandmarkList, RectTransform rectTransform)
        {
            List<LandmarkModel> list = new List<LandmarkModel>();
            if (normalizedLandmarkList == null || normalizedLandmarkList.Landmark.Count == 0) return list;

            for (int i = 0; i < normalizedLandmarkList.Landmark.Count; ++i)
            {
                Vector3 point = rectTransform.GetLocalPosition(normalizedLandmarkList.Landmark[i]);
                list.Add(new LandmarkModel(point.x, point.y, point.z, normalizedLandmarkList.Landmark[i].Visibility, normalizedLandmarkList.Landmark[i].Presence));
            }

            return list;
        }

But getting the Nose(Point) at the bottom of the screen (See little ping ball in the image):

When I did Debug.Log(rectTransform.rect);
(x:-754.00, y:-565.50, width:1508.00, height:1131.00)

I'm not sure, but maybe this Sphere is not created as a child object of the screen?
Note that these methods calculate the local position, not the position in 3D world space.
https://github.com/homuler/MediaPipeUnityPlugin/blob/bed2f478eddf3b8be106adcc2044e576e8337e22/Packages/com.github.homuler.mediapipe/Runtime/Scripts/Unity/CoordinateSystem/ImageCoordinate.cs#L271-L282
https://docs.unity3d.com/ScriptReference/Transform-localPosition.html

Cool!
Making it the child of Annotations Screen worked for me.
I also set sphere.transform.localPosition instead of sphere.transform.position
I have once separate question (If you want me to create a new issue then  let me know).
How to resize Annotatable Screen to portrait mode? actually the previous version was easy because we were able to change the WebCamTexture plane.
Thanks.

I have once separate question (If you want me to create a new issue then let me know).

I don't know what exactly you're having trouble with, so please create a new issue and explain the details.


Consider Macros 1.1 to register script handlers

Something like this:

#[derive(ScriptHandler)]
struct EventHandler;

impl EventHandler {
  #[script]
  fn sum(&self, a: i32, b: i32) -> i32 { a + b }

  #[script(name="div")]
  fn custom_div(&self, a: i32, b: i32) -> i32 { a / b }
}

However it does not seem possible. Apparently, Macros 1.1 allow only type-level attributes.

Also there is a proc-macro-hack for function-like macros, but it can't be used inside impl blocks and can't contain more than one declaration within the same scope.

As for custom attributes
(which seem the most convenient) it isn't stabilized yet. But available on nightly though.

Attributes are available now ( Rust 1.30). Need to check them out.

https://doc.rust-lang.org/reference/procedural-macros.html


ModusToolbox Example Question

Hello! I see that ModusToolbox is one of the frameworks in the PAL source. However, I don't see how to reconcile the CMAKE build system of the tests, etc with the make build system of Modustoolbox. Is there an an example somewhere which shows the full instructions or build system to integrate this into a Modustoolbox project?
Thanks!

Hi @keenanjohnson,
The cmake workflow is supporting the unit testing, but it is not integrated in the ModusToolbox make system. Only run separately.
You can build multiple code examples of this library for PSoC6 using this code example -> https://github.com/Infineon/mtb-example-multi-half-bridge (which uses this library).
A new release of that example, migrated to the ModusToolbox 3.0 is planned in the upcoming week.s

Thanks @jaenrig-ifx ! That answers my question :).
If anyone at Infineon is wondering, I would definitely appreciate a future where cmake or some other more modern build system is supported officially by modustoolbox :)


Error install Canvas version 3.4.4: count(): Parameter must be an array or an object that implements Countable

Whilst installing Canvas version 3.4.4 (latest at the time of writing) I encounter an error:
An unexpected error occurred. Installation could not continue.
[✘] count(): Parameter must be an array or an object that implements Countable

Tried to run php artisan canvas install again to no avail. Also completely removing the whole project (directory) and database and starting afresh did not solve this issue...
Anyone encountered this before? I have no idea where the error is coming from.
Any help is appreciated, if more info is needed, please let me know!

Are you using PHP 7.2? If so, that will be the issue. PHP 7.2 introduced a kind of breaking change in that calling count() on a null yields an error, unlike in previous versions where it would return 0.
If you're on 7.2 let me know and I'll look into fixing this over the weekend.

Thanks for your answer!
Indeed I'm using PHP 7.2. I will change versions for now and see if that solves the issue, but indeed the issue should probably be fixed for future versions!

Glad that fixed it. I've done a bit of testing locally - the root cause is actually in Laravel itself (vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php:1231).
Canvas currently uses Laravel 5.3 which does not support PHP 7.2. Laravel 5.5 seems to.
Best case for now is to use this project on 7.1 as the highest dependency, as Laravel 5.3 and the latest Canvas release both support it.
I'll look into setting the maximum PHP version for Canvas to 7.2 in the composer.json file, to hopefully help highlight this restriction.

Thanks for jumping in @glennmcewan.

laravel 5.3 is quite old now. Seem canvas did not upgrade when 5.4 came around, nor 5.5, nor 5.6. Does canvas have any plans to stay current with its main dependency?

Trying to use Canvas now, Same error.
Is downgrading my php version the only solution?

Last commit was > 10 months ago. That should tell is all we need to know (Canvas is dead). I'm out.

@jdunk @jjdelarosa - I can try to take a look at this in the next few days I'm just travelling at the moment and will be back home next week.


Can't seem to escape _ in string literals

Describe the bug
I have the need to get a literal _ in a Form element's Description, not italics. I've tried several methods for escaping and searched for an answer but can't seem to find the right way to do this.
Use case is displaying the name of an env var in my TUI that the user needs to set.
To Reproduce
Steps to reproduce the behavior:
huh.NewGroup(
huh.NewNote().
Title("🤖 Experimental: LLM Generation 🦙✨").
Description(`*_Optional_* LLM-powered alpha features.

Currently generates:
- column _descriptions_
- relevant _tests_
via the Groq API.

You'll need:
✴ A Groq API key
✴ Key stored in env var GROQ\_API\_KEY`),
...

Expected behavior
I would expect escaping with a backslash or something similar (doubling the character, etc) to allow an actual underscore in the string instead of triggering formatting.
Screenshots

Desktop (please complete the following information):

OS: MacOS Sonoma 14.1.1
Version: v0.3.1

Additional context:
Thanks for making such a great library! I love it so much.

Hey @gwenwindflower, thanks so much for opening this issue. We should probably have a "Raw" mode for non-markdown based notes.

This is throwing me off with the Note as well. I'm adding this filename:
user-stats_2024-04-28_15-55-21.csv
And the _ chars are italicizing/removing parts even if I put the filename in a codeblock with ticks. And agree, love this library. Thank you!

Hey, thanks all for the feedback.
As a quick fix, we've allowed escaping characters with a backslash.

How may we take your order?

`CHARM\\_BURGER`

What we may want to do in the future is add support for a Transform(s string) string or Render(s string) string function so you can use whichever rendering you want and by default have a simple markdown parser but that would enable you to use glamour or your own custom string transformation.

Closing for now since this particular issue is solved.


BLD-56635: add journey segment resource

We also add data sources for each resource we create. They're pretty simple and fetch the resource by name.


Add subscription support.

graphql-java has some support for executing subscriptions - the "query" you would run when you want to notify your subscribed clients of some event.
This PR just adds subscription as another supported operation.
The subscribing/unsubscribing, transport, etc. are not handled here, those are perhaps concerns for another library.
The test currently just uses the context to pass data about the event that occurred to the resolver, but maybe there's a better (and more type-safe) way to do this.

This is great, thanks!

It might be good to add something to the readme about this change


Using generics in tsx modules parses as tsxTagName & tsxTagAttrib

When I have an arrow function that uses generics in a TSX file it parses the first generic argument (up to and including the "," after the argument) as tsxTagName and the second argument as tsxAttrib. I'm using the excellent vim-HiLinkTrace plugin to see the syntax highlighting trace.

You can see that although the type def works fine, the generics in the arrow definition do not.
If I change it to a named function instead it seems like it gets parsed as plain text:

I feel like in both cases this should parse as a tsxType or tsxGenerics, no?
I tried to fix it myself, but these regexes are a little beyond my reach at the moment. Any thoughts?
I created a simple repo to reproduce the issue: https://github.com/joefiorini/tsx-generics-syntax-repro
It uses vim-plugged to install the plugins. Can be run in NeoVim with nvim -u init.vim.

Sorry it took me so long to respond. I think it's a little better, but I still see some issues. I've updated my example repo to include a few more examples that seem to break for me. I'll also include a screenshot here

Hi Joe,
Thanks for providing the new examples. Lets see if this latest commit helps solve the issue.

We could also add syntax rules for say the Props['type'] part and make it customizable as an additional feature in the future.


default html formatter is not working after upgrading to 1.30

VSCode Version:1.30
OS Version:win10

Steps to Reproduce:
1.auto closing and intelli sense both stopped working and enabling it in setting doesn't help
2.tried in clean os, still the same

Does this issue occur when all extensions are disabled?: Yes

always displays a notice: " There is no document formatter for 'html'-files installed."

This is the same as #64993  I think.

I encountered the same problem after upgrading to 1.30.

simply uninstall 1.30 then reinstall 1.29 won't solve this issus. need to delete this folder
”users[username]\appdata\roaming\Code" before reinstalling 1.29.
this way can get the auto formatter back

This only happens for HTML files opened on no workspace.
See #64993

I can repro and I'm looking into this now.

No-workspace bug: This should be fixed in 1.30.1.


LLM should default to logging to SQLite

Currently you have to remember to run llm init-db first - but I think running llm logs may create that database as a side effect?
It should log by default, and provide an option for turning logging off using the same mechanism as:

#31

TODO

[ ] Log by default
[ ] Setting mechanism for turning off log-by-default
[ ] --log option for turning on logging for a specific prompt

There's already a --no-log option, I can add a --log mechanism for explicitly logging even if the setting is turned off.

Relevant code: https://github.com/simonw/llm/blob/1bdb2e7438052242c75da192e3cb74612e897f98/llm/cli.py#L249-L254

Need to update the documentation around this too.

Setting the default model looks like this:
llm models default gpt-4

For disabling and enabling logs I'm going to go with:
llm logs disable

llm logs enable

I feel like there should be a way to tell the current status of logging too. Maybe:
llm logs status

Which could show not just the on/off state but also the size of the DB and number of records in it.

I just need the --log option now.


Confused about Multi.asFlow extension

Kotlinx coroutines Reactive includes an general extension fun to convert Publisher to Kotlin Flow, https://github.com/Kotlin/kotlinx.coroutines/blob/master/reactive/kotlinx-coroutines-reactive/src/ReactiveFlow.kt
Besides add extensions to general ReactiveStreams API, https://github.com/Kotlin/kotlinx.coroutines/tree/master/reactive it also supports Reactor, Rxjava2/3, JDK 9 Flow API.
But in these implementations, it does requires a suspend modifier for fun .asFlow.

/cc @heubeck

Thank you for pointing this out, @hantsy.
Mutiny-Kotlin was created before Mutiny switched to the Publisher API.
Will have a look and probably propose a refactoring.

The JDK9 extension also includes a asFlow fun, I have tried here https://github.com/hantsy/quarkus-sandbox/blob/master/mongodb-kotlin-co/src/main/kotlin/com/example/PostResources.kt#L4 and https://github.com/hantsy/quarkus-sandbox/blob/master/mongodb-kotlin-co/src/main/kotlin/com/example/PostResources.kt#L28, works.

lets follow up on this discussion in https://github.com/smallrye/smallrye-mutiny/issues/1325


Patch invoke sp dsc command memory leak

Pull Request (PR) description
Corrected the issue in order to remove-pssession and avoid memory leak from the Invoke-SPDSCCommand function in SharePointDsc.Util.psm1
This Pull Request (PR) fixes the following issues
Fixes #1037
Task list

[x ] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md in the resource folder.
[ ] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[ x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #1038 into dev will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##             dev   #1038   +/-   ##
=====================================
  Coverage     92%     92%
=====================================
  Files        118     118
  Lines      12232   12232
  Branches       1       1
=====================================
  Hits       11340   11340
  Misses       891     891
  Partials       1       1

You change to the Changelog.md file has an issue:
CHANGELOG.md: 6: MD013/line-length Line length [Expected: 80; Actual: 86]
Please make sure the line is split across multiple lines.

Yes sorry about that, just saw the appveyor report. I corrected the line in the changelog to be under the 80 characters per line. I just committed the change, it should be ok.

appveryor still reports  12 failed tests, but according to what I understand, it does not seem related to my modifications:
Error-Level PSSA rule(s) did not pass.
The following PSScriptAnalyzer rule 'PSDSCUseIdenticalMandatoryParametersForDSC' errors need to be fixed:
MSFT_SPSearchContentSource.psm1 (Line 1): The 'Required' parameter 'ScheduleType' is not present in 'Get-TargetResource' DSC resource function(s).
MSFT_SPSearchContentSource.psm1 (Line 219): The 'Required' parameter 'ScheduleType' is not present in 'Set-TargetResource' DSC resource function(s).
MSFT_SPSearchContentSource.psm1 (Line 683): The 'Required' parameter 'ScheduleType' is not present in 'Test-TargetResource' DSC resource function(s).
For instructions on how to run PSScriptAnalyzer on your own machine, please go to https://github.com/powershell/PSScriptAnalyzer
[-] Should pass all error-level PS Script Analyzer rules 105ms
Expected $null, but got @(Microsoft.Windows.PowerShell.ScriptAnalyzer.Generic.DiagnosticRecord, Microsoft.Windows.PowerShell.ScriptAnalyzer.Generic.DiagnosticRecord, Microsoft.Windows.PowerShell.ScriptAnalyzer.Generic.DiagnosticRecord).
482:                     $errorPssaRulesOutput | Should -Be $null
at , C:\projects\sharepointdsc\Modules\SharePointDsc\DSCResource.Tests\Meta.Tests.ps1: line 482
I will look into it on monday.

I think that this has something to do with the new release of PSScriptAnalyzer. They released a new version three days ago.
The errors you are encountering are referring to subclasses, which should not be used in the *-TargetResource methods.

Raised an issue in PSSA (https://github.com/PowerShell/PSScriptAnalyzer/issues/1192) and DscResource.Tests (https://github.com/PowerShell/DscResource.Tests/issues/317)

I have a workaround what I will implement and merge. After that you can sync your branch with Dev and (hopefully :-) all tests will then pass.

PR submitted. I will merge it once all tests have completed. After that you can update your branch from Dev

PR merged. Can you pull from Dev and resolve the merge conflict in the Changelog?

Yes, that did the trick!
One question. In PR #1042 @sguilbault-sherweb submitted pretty much the same fix, if I am not mistaking. However, there just the finally keyword was added. Isn't that a better solution than what you have implemented here? The finally block is always executed, even if the try block contains a return keyword.

Yes, the finally block in PR #1042 is way cleaner !

Ok, great! Will close this PR and merge the other one. Thanks for your help!


Comparisons for FormatAgent()

✨ Feature Request

Allow objects of type FormatAgent to be compared to each other to see if they are equal. For example:
>>>import iris.fileformats
>>>from copy import deepcopy
>>>agent_copy = deepcopy(iris.fileformats.FORMAT_AGENT)
>>>agent_copy == iris.fileformats.FORMAT_AGENT
True

Currently the result would be false.
Motivation
It would be useful for testing purposes.
Additional context

Use Case
ANTS uses iris.load and modifies iris.fileformats.FORMAT_AGENT to modify some FormatSpecifications and add a few more. We want it to do this within a context manager so that iris behaviour is not modified by importing ants. To test this we need to test that once outside of the context manager, the FORMAT_AGENT is the same as it was before the context manager was called. This requires comparing the FORMAT_AGENT to a copy of itself.

@jrackham-mo tells us that the MIAO team (ANTS developers) would be interested in writing this so I have assigned @mo-tgeddes in the meantime.


Feature/page templates

Issue: #370
What I did - Changes to the template documentation code sandbox examples

Screenshots (if appropriate):
Checklist

[x] changeset has been added
[x] I have made corresponding changes to the documentation
[ ] New and existing unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works

How to test

Codecov Report

Merging #903 (548083a) into dev (17ee57a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #903   +/-   ##
=======================================
  Coverage   86.77%   86.77%
=======================================
  Files         175      175
  Lines        4575     4575
  Branches     1562     1562
=======================================
  Hits         3970     3970
  Misses        301      301
  Partials      304      304

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

I wonder if we should have a quick meeting to go over these changes

👍


[DateTimePickerV2] The focus for date time input field is working in chrome when doing tabination. But in FF it's not showing the Focus.

The focus for date time input field is working in chrome and Safari when doing tabination. But in FF it's not showing the Focus.
https://next.carbon-addons-iot-react.com/?path=/story/2-watson-iot-experimental-☢-datetimepickerv2--single-select
In Chrome, showing the focus when doing tabination (PAL Storybook)

(GRAPHITE)
In FireFox, not showing the focus when doing tabination

In Chrome, showing the focus

@JordanWSmith15
This is the thing with Firefox on Mac
We need to do 2 things to enable the tabfocus

In System Preferences → Keyboard, in the Shortcuts pane, check the “all controls” radio at the bottom.

In Firefox, type "about:config" in the URL bar. There is no accessibility.tabfocus preference on the mac, so you'll have to make one. Right click in the window, create a new "integer" pref, and set it to 7.

https://support.mozilla.org/en-US/questions/1278793

Ok... that's pretty interesting. Why is it different than all the other fields on this page though? https://pages.github.ibm.com/maximo-app-framework/graphite/main/reference-app/?dataFormatting%3AselectedTab=2#/dataFormatting

Taking another look today. I see the issue is specific to the invalid state not the regular state.


[BEAM-12596] Ensure that SDFs always report a size >= 0.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @udim @chamikaramj

LGTM

Run Python PreCommit


Add a verification check when a new GAE runtime is created

When creating an app-tools-lib-for-java runtime, there is no check that the cloud sdk exists on the system (that we have a valid path to the cloud sdk install). This step is done when the user attempts to run/debug the runtime (check is done CloudSdk.Builder#build).
Should we be calling PathResolver.INSTANCE.getCloudSdkPath() to check that is returns a path when a new runtime is created? If we do this, the user can input the path if we didn't find it or prompt the user to install gcloud if they dont have it.

@elharo @briandealwis

How would this affect he new project wizard which creates a (possibly invalid) runtime?

We could have the check in the new project wizard too. If we cannot resolve the location of the cloud sdk (that is after the path resolver and after prompting the user for the location), the new project creation will fail. My thought is you cannot use the App Engine features without the cloud sdk and user can always create a dynamic web module and install the facet later after they install cloud sdk.

@nbashirbello use CloudSdkPrompter — it does what you're looking for.

@nbashirbello Is this now done and/or obsolete?

This bug still exists. I will work on it


feat request: http3 support

http3 client hello impl ref https://github.com/SagerNet/sing-box/blob/main/common/sniff/quic.go#L20

wait for https://github.com/golang/go/issues/32204

wait for https://github.com/golang/go/issues/58547


Cant upload video (1.9gb)

I have a collection called home movies and i have a file field in the collection with a limit of 25000000 bytes. But whenever i try to upload a video of 1.9gb it says something went wrong with the request, but when i upload a small video it works fine. Everything i do is through the admin ui

Could you start PocketBase with --debug and see if there is a more detailed error message from the console?
Do you have a reverse proxy (eg. nginx, apache, etc.) that has body size limit?
Also please note that form-data requests larger than 32MB will be stored temporary on the disk, so you need to have at least 2gb free disk space in your case.

ok ill try to run the command and i will see what the error is.
I have enough space ~200gb

I've just tested it locally. The only way I can simulate an error with large files (excluding
lack of disk space) is if the upload takes too much time and the request is being timeouted.
Currently the read timeout is 60s but for large file upload this may not be sufficient and I'll consider increasing it with the next release to 180s (and eventually make it configurable).

That definetly is the case then. Hopefully this i fixed soon.
My upload takes about a minute


Identity Security Stamp mismatch during ConfirmEmailDataProtectorTokenProvider validation

Hello, it’s my first issue ever so I hope that I am posting this in the right place. I have a question regarding ASP.NET Core Identity Security Stamp. In our project we have an issue that happens occasionally. We are using ASP.NET Core 2.1.
We have following sign up procedure:

Admin creates a user manually, under the hood userManager.CreateAsync method is called. Password is generated but is not used in the process whatsoever.
Admin sends user an activation email, providing it with the token for resetting password (which includes security stamp value). When user enters the link, he must enter new password which will be further used in login. If during the validation in ConfirmEmailDataProtectorTokenProvider.ValidateAsync there is a mismatch on the user security stamp, password change fails. If it succeeds, the userManager.ResetPasswordAsync is called.

After research we’ve concluded that we do not use any UserManager methods which could change the Security Stamp value besides two used in above process, that is userManager.CreateAsync and userManager.ResetPasswordAsync. By our understanding, seeing different security stamps in the second step should never occur (by normal application usage), because there are no methods called that would potentially change the value. But for some reason it happens occasionally. We’ve set the logging in the reset password procedure, on the ConfirmEmailDataProtectorTokenProvider level, ValidateAsync  method:
Email stamp: 7bd27900-6720-4d5e-8601-e3c62d2a23bf
Database stamp: R6HSK7TRWZXC4Z7DJKVHA6YPQMLIQO5U

We noticed that one of the stamps was GUID and the other one is Base32 (which is used in our ASP.NET Core version – UserManager.NewSecurityStamp). After checking the DB, we’ve seen that there is no easily noticeable rule what type of security stamp is set on the user entity, but only about 6% was in Base32 notation.
Can you provide us with some guidance why that behaviour occurs? Could that be the case in the mismatch or maybe you have some other clue?
We’ve also checked that GUID was generated for security stamp in earlier version of .NET Core (2.0). We host our application as an Azure Web App, maybe something could go wrong while updating version of .NET Core on remote server? The project was started at 1.X (unfortunately I’m not sure about exact version) and was updated regularly so there were few such updates.
I’d be grateful for any help.
With regards,
Jacek

Could we get a repo? Even a private repo would help, we'd like to look at how you're doing an email stamp.

Hi, as I am working on the same project with @CodingKobold, I'll be probably able to provide you with some details. Unfortunately we can't share a repo for various reasons, however I don't think we are doing anything fancy.
One application (let's call it admin panel) calls Web API that is exposed by another app (let's call it account app) in order to get a link for email confirmation. The admin app renders an email and sends it to the user with that link embedded.
Account API where we create the token looks like this:
[HttpPost]
[Route("activationmail/send")]
public async Task<IActionResult> SendActivationAsync([FromBody] UsernameAndEmailWebModel usernameWebModel, [FromQuery] string languageCode)
{
    var user = await _userManager.FindByNameAsync(usernameWebModel.Username);

    if (user == null)
    {
        return BadRequest();
    }

    var activationUrl = await CreateActivationUrlAsync(usernameWebModel, languageCode);

    if (activationUrl.IsNullOrEmpty())
    {
        return BadRequest();
    }

    return Ok(activationUrl);
}

private async Task<string> CreateActivationUrlAsync(UsernameAndEmailWebModel usernameWebModel, string languageCode)
{
    var user = await _userManager.FindByNameAsync(usernameWebModel.Username);

    if (user == null)
    {
        return string.Empty;
    }

    var token = await _userManager.GenerateUserTokenAsync(user, TokenProviderType.ConfirmEmailTokenProvider, TokenPurpose.Confirmation);

    var baseUri = _serverSelfUriProvider.GetServerBaseUri();
    var relativeUri =
        $"Account/ActivateAccountLanguageChange?token={WebUtility.UrlEncode(token)}&languageCode={languageCode}";

    var uri = new Uri(new Uri(baseUri), relativeUri).ToString();

    return uri;
}

Please let me know if you need any other code from our side.
There is also another question. Why format of SecurityStamp in our DB differs? One time it is guid, another something that looks like Base64 ? Question out of curiosity I guess. We don't operate directly on IdentityDbContext so there is a slim chance we are actually the ones modifing it.

We really can't progress this without a repo. Usually it's a data protection configuration mismatch. The stamp formats don't affect tokens in any meaningful way. I have to close this unless we get a small repro.


Jan Edrozo | Carets

Ada Trader
Congratulations!
Comprehension Questions

Question
Answer

How do Backbone Views help structure your code?
Backbone Views helped me structure my code my allowing me to separate which code related to DOM events stay in the view and move business logic (e.g. order model's custom priceCheck function) to the models while keeping the app.js file lean.

Did you use jQuery directly in your Views? How, and why?
I used this.$('css-selectors') when appending to specific elements, and $el in each view's render function to add its respective compiled template html content.

What was an example of an event you triggered? Why did you need to trigger it?
In the quote's view, there are 2 buttons: buy and sell. On click, the quote's buy and sell methods are executed and in both cases, a custom event (clickedBuyOrSellQuote) is triggered. This event is triggered so the quote_list_view can execute its showTrade function which appends the trade transaction in the trade history.

In what way is unit testing in JavaScript similar to unit testing in Ruby? In what ways is it different?
Both are similar in that they have describe, before, and it blocks and testing is ideally suited for business logic in the model. JS testing is different in the syntax and model business logic can include events (e.g. triggers and listeners -- would like more assistance on specific testing of triggers and event listeners, please).

Ada Trader
What We're Looking For

Feature
Feedback

Core Requirements

Git hygiene
Good number of commits and good commit messages

Comprehension questions
Check

Organization

Models and collections are defined in separate files
Check

Code that relies on the DOM is located in or called by $(document).ready
Check

Functionality

Quote prices change when clicking Buy and Sell
Check

The Trade History updates when buying and selling a quote
Check

A user can create an open order using the Order Entry Form
Check

An open order removes itself from the open orders and updates the Trade History when fulfilled
Check

General

Has separate views for different parts of the app
Check

Uses events (listening/handling and triggering) to manage different behavior in views
Check

Practices good standards for views (ES6 syntax, doesn't directly use jQuery, returns this in render)
Check

Error handling for the Order Entry Form
Great work here!

Testing

Has unit tests for models
Nice work, I have small criticisms, but a very good first jump into testing!

Overall
Really good work.  You hit all the requirements.  I have a few minor criticisms, most seriously that the OrderListView and QuoteListView instances overlap, and you can read my in-code notes.  Very impressive work!


Optimize hyphen

Managed to save 15 characters here.
I am a bit confused why ((.0000001)+"")[2] doesn't work here. It returns "-" in all browsers and node.js but returns 0 in tests. Any idea why?

Hmm. That is strange. .0000001 would be 1e-7 and .00000001 is 1e-8.

It’s because you unwrapped the number from +[].
The expressions inside the definitions are not real JavaScript expressions

@hazzik, if that is the case, why does it work with 7 zeros and not 6? (((.00000001)+"")[2 and not ((.0000001)+"")[2)
Another option would be to just use (+((+(+!+[]+[+!+[]]+(!![]+[])[!+[]+!+[]+!+[]]+[!+[]+!+[]]+[+[]])+[])[+!+[]]+[+[]]+[+[]]+[+[]]+[+[]]+[+[]]+[+[]]+[+!+[]])+[])[!+[]+!+[]] which saves a further 3 characters (18 in total)

if that is the case, why does it work with 7 zeros and not 6? (((.00000001)+"")[2] and not ((.0000001)+"")[2])

Because if there are 6 zeros the number gets converted to 0.000001, eg it loses one 0. With 6 zeros the number becomes "1e-7" (instead of "1e-8").

So, this works: '(+(.+[0000001])+"")[2]' and saves 3 characters.

So, this is this: (+(.0000001)+"")[2]
(+((+(+!+[]+[+!+[]]+(!![]+[])[!+[]+!+[]+!+[]]+[!+[]+!+[]]+[+[]])+[])[+!+[]]+[]+[+[]]+[+[]]+[+[]]+[+[]]+[+[]]+[+!+[]])+[])[!+[]+!+[]]
_________________________________________________________the error is HERE ^^^^

And this is (+(.0000001)+"")[2]
(+((+(+!+[]+[+!+[]]+(!![]+[])[!+[]+!+[]+!+[]]+[!+[]+!+[]]+[+[]])+[])[+!+[]]+[]+[+[]]+[+[]]+[+[]]+[+[]]+[+[]]+[+[]]+[+!+[]])+[])[!+[]+!+[]]
___________________________________________________________same error HERE ^^^^

And this is correct version: (+(.+[0000001])+"")[2]
(+((+(+!+[]+[+!+[]]+(!![]+[])[!+[]+!+[]+!+[]]+[!+[]+!+[]]+[+[]])+[])[+!+[]]+[+[]+[+[]]+[+[]]+[+[]]+[+[]]+[+[]]+[+!+[]]])+[])[!+[]+!+[]]
______________________________________________________________no error HERE ^^^^

The error happens because of the double digit replacer here: https://github.com/aemkei/jsfuck/blob/977aeeff2a924a1747baf0ee34738f435fdcec05/jsfuck.js#L184

Thanks for the explanation @hazzik :)
I will update the branch.

@aemkei, I've updated the branch. Thanks again hazzik.

Perfect. Guess we once need to add an explanation to the README about how the character mapping works.


Upgrade Syslog-ng Configuration

what

Fix this warning

[2018-08-01T23:13:04.271134] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.13 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file.;

why
We recently upgraded to alpine:3.8 which bumped the syslog-ng version.

Fixed in https://github.com/cloudposse/geodesic/pull/208


threadDelay impl does not prevent underflow

Describe the bug
If the argument to threadDelay is "very negative", it will underflow.
To Reproduce
Steps to reproduce the behaviour: I didn't record them. I think pass a negative duration to threadDelay that is between -2X and -1X where X is the minBound of Int.
Expected behaviour
Every non-positive argument should have the same behavior.

I don't see anything wrong here using threadDelay from si-timers:
λ putStrLn $ IOSim.ppTrace $ runSimTrace (threadDelay ((-1) * fromIntegral  @Int maxBound))
0s - Thread []   main - ThreadDelay TimeoutId 0 Time -9223372036854775807s
0s - Thread []   main - ThreadDelayFired TimeoutId 0
0s - Thread []   main - ThreadFinished
0s - Thread []   main - MainReturn () []
λ putStrLn $ IOSim.ppTrace $ runSimTrace (threadDelay ((-1.5) * fromIntegral  @Int maxBound))
0s - Thread []   main - ThreadDelay TimeoutId 0 Time -13835058055282163710.5s
0s - Thread []   main - ThreadDelayFired TimeoutId 0
0s - Thread []   main - ThreadFinished
0s - Thread []   main - MainReturn () []
λ putStrLn $ IOSim.ppTrace $ runSimTrace (threadDelay ((-2) * fromIntegral  @Int maxBound))
0s - Thread []   main - ThreadDelay TimeoutId 0 Time -18446744073709551614s
0s - Thread []   main - ThreadDelayFired TimeoutId 0
0s - Thread []   main - ThreadFinished
0s - Thread []   main - MainReturn () []

Testing it with IOSim was not a good idea, because in IOSim we don't do DiffTime conversions.


User Managment

User Managment with ion_auth https://github.com/benedmunds/CodeIgniter-Ion-Auth

Will be done by using our own library, which gives us the ability to easily customize the routine for external providers (OAuth, Authkey ..)

Considering Ion Auth is a possible (good) solution because it is very flexible. Anyhow the hashing (PHPass) as well as the MY_Controller would be needed to be customized.


macOS: "option-as-alt" defaults to "true" for US keyboard layouts

A common issue for US-centric users of a terminal is that the "option" key on macOS is not treated as the "alt" key in the terminal.
Background
macOS does not have an "alt" key, but instead has an "option" key. The "option" key is used for a variety of purposes, but the troublesome behavior for some (and expected/desired behavior for others) is that it is used to input special characters.
For example, on a US standard layout, option-b inputs ∫. This is not a typically desired character when using a terminal and most users will instead expect that option-b maps to alt-b for keybinding purposes with whatever shell, TUI, editor, etc. they're using.
On non-US layouts, the "option" key is a critical modifier key for inputting certain characters in the same way "shift" is a critical modifier key for inputting certain characters on US layouts.
We previously tried to change the default for macos-option-as-alt to left (so that the left option key behaves as alt) because I had the wrong assumption that international users always used the right option key with terminals or were used to this. But very quickly beta users with different layouts (such as German, I believe) noted that this is not the case and broke their idiomatic input behavior. This behavior was therefore reverted.
Solution
This confusing behavior happened frequently enough that I decided to implement the more complex behavior in this commit. The new behavior is that when a US layout is active, macos-option-as-alt defaults to true if it is unset. When a non-US layout is active, macos-option-as-alt defaults to false if it is unset. This happens live as users change their keyboard layout.
An important goal of Ghostty is to have zero-config defaults that satisfy the majority of users. Fiddling with configurations is -- for most -- an annoying task and software that works well enough out of the box is delightful. Based on surveying beta users, I believe this commit will result in less configuration for the majority of users.
Other Terminals
This behavior is unique amongst terminals as far as I know. Terminal.app, Kitty, iTerm2, Alacritty (I stopped checking there) all default to the default macOS behavior (option is option and special characters are inputted).
All of the aforementioned terminals have a setting to change this behavior, identical to Ghostty (or, Ghostty identical to them perhaps since they all predate Ghostty).
I couldn't find any history where users requested the behavior of defaulting this to something else for US based keyboards. That's interesting since this has come up so frequently during the Ghostty beta!

I don't think there is a "right" solution. I just wanted to provide a data point: I use a Mac with the PL (Polish) keyboard layout. I installed ghostty and was surprised that the ctrl+alt+f shortcut which normally brought up fzf in fish doesn't work anymore. It produced "ń" instead, which is what I normally get in every app if I press alt-n.
It took some searching and trying things out to encounter the macos-option-as-alt setting. After I set it to true, I got the behavior I expected. I am also unable to type Polish characters in a shell in ghostty (so, alt-n does not produce "ń"), but I'd rather have that breakage than having ctrl+alt+f broken.
Of course, ideally I'd like the best of both worlds. I tried configuring bindings to override (keybind="alt+n=text:ń"), but that didn't work as expected.


Unable to use the Inventory Tracking template

Describe the bug
This template works perfectly in the UI preview section.
However, for a real annotation section, no "CocaCola" or "RedBull" small icon image is shown for annotation. Only the image to be annotated is shown on the screen.
To Reproduce
Just try the inventory tracking system and upload a sample image, you'll see all those icon label are not being shown.
Expected behavior
I was expecting those small icon images are displayed to the annotators, so that the annotators can select the icon image and draw a bounding box on the given image (if he/she spot a CocaCola in the image, he/she should be able to spot and label it)
Screenshots

Environment (please complete the following information):

MacOS 12.6
Label Studio 1.6.0

Most likely you are using wrong input task. It should be like this:
{
  "data": {
    "image": "https://htx-pub.s3.amazonaws.com/templates/inventory-tracking/shelf.jpeg",
    "objects": [{
      "value": "CocaCola",
      "html": ""
    }, {
      "value": "RedBull",
      "html": ""
    }, {
      "value": "Burn",
      "html": ""
    }, {
      "value": "Breezer",
      "html": ""
    }, {
      "value": "Monster",
      "html": ""
    }]
  }
}

Try to insert this labeling config to your project:
<View>
  <View style="display:flex;justify-content:center">
    <PolygonLabels name="objects" toName="image" value="$objects"/>
  </View>
  <Image name="image" value="$image"/>
</View>

I see, that helps. Those little icons' image URLs should also be uploaded via "data insert", which solves the issue.


Improve Target Build functionality

The way Target Build dropdown currently works, it seems that every project remembers the last value of target build.
If I type some target name, build, then type another, build, I can see both of the targets in the dropdown.
It doesn't look possible to remove items from there, or to persist the entire list - when I restart FD or close/open project - only the last target is shown, and dropdown is empty.
Additionally, looks like the last target is stored somewhere in FD local app data, not the project properties files.

I think available target builds should be editable in project properties, and stored in the project xml file. Are there plans to implement

fdbuild is called with -target $(TargetBuild) - however doesn't look like that is doing anything further. Shouldn't it at least define a CONFIG::$(TargetBuild) compiler constant, or something like that?

If I delete all the text in the target build dropdown, fdbuild is called with -target "" instead of no target. How to reset target to null?

Is it possible to call a custom command instead of fdbuild? I saw a custom build project properties option, but can't figure out where to put my custom build command (unless I'm supposed to put it in pre-build or post-build). Actually it would be preferrable if I could have default fdbuild behavior with one target and a custom command (e.g. script) with another target, are there any plans like this? I know you're working on #548 so all this will probably be replaced or significantly changed anyway.

yes we have a few ideas like that
currently the argument is for you to use, but we could certainly imagine adding a compiler constant - we didn't think about that
minor bug, null or empty have the same effect
if you choose Custom Build nothing should be built automatically and you can instead define the command to execute in the Build tab > Pre/post-build

All right, thanks for clearing it up.
2. Is there any way to affect how fdbuild operates? E.g. besides the options offered in project properties, can I insert some script in between fdbuild and calling of the compiler? Or is there any way I can run a script to modify the auto-generated build config xml (obj/ProjectNameConfig.xml)? Is that xml generated before or after the pre-build command is run?
4. So how about if Custom Build is selected, Pre-Build Command Line label should instead show Build Command Line?

You can use the argument in a pre-build script, but this happens before the Flex config is generated.
You're right, it would be friendlier.

Everything we discussed should be added to the wiki also.

Ok, do you think this would work? I didn't test this, but if everything works the way I suppose it does, this should set CONFIG::ios or CONFIG::android compiler constant if target is ios or android, respectively, enabling to use conditional compilation rather than run-time checking.

Set compiler option Load configuration file to obj/ProjectName-target.xml (for example).
Set pre-build command line: scripts/setup-target.sh $(TargetBuild)

scripts/setup-target.sh (bash script in this example):
#!/bin/sh
ios_config=build/ios-config.xml
android_config=build/android-config.xml

target_config=obj/ProjectName-target.xml

case $1 in
	ios)
		cp -f "$ios_config" "$target_config"
	;;
	android)
		cp -f "$android_config" "$target_config"
	;;
	'')
		rm -f "$target_config"
	;;
	*)
		echo "Unknown target \"$1\"" >&2
		exit 1
	;;
esac

In this minimal example the script just copies a target-specific compiler configuration file, which can contain all the necessary options for a particular target.
build/ios-config.xml:
<?xml version="1.0" encoding="utf-8"?>
<flex-config>
  <compiler>
    <define append="true"><name>CONFIG::android</name><value>false</value></define>
    <define append="true"><name>CONFIG::ios</name><value>true</value></define>
  </compiler>
</flex-config>

build/android-config.xml:
<?xml version="1.0" encoding="utf-8"?>
<flex-config>
  <compiler>
    <define append="true"><name>CONFIG::android</name><value>true</value></define>
    <define append="true"><name>CONFIG::ios</name><value>false</value></define>
  </compiler>
</flex-config>

Yes this should definitely work and is basically the use case for the target build option.

I like the idea of putting use cases / examples in the wiki. I bet there are many nice FD features many people would use if they only knew about them / how to use them.


Feature: update events sf43

This PR updates the way events are used since Symfony 4.3 Beta 2 #975

removed Event class
created a CommentCreatedEvent event object
update calls to dispatch()
used Symfony\Contracts\EventDispatcher\Event instead of the Event class

I have a problem when I update the calls to dispatch() to remove the event name. The comment.created event is inside the not called listeners but it works fine when I keep the event name.
I don't know if it is an issue or not.

The composer.json needs to be updated to requiere 4.3-beta2 and make tests pass

Maybe I should wait that #974 is merged.

@ayshiff thanks for this contribution! We did some minor tweaks while merging, but your pull request was great. Thanks to reviewers too.


Use EditorConfig to define file formats and coding style

Merged. Thank you for the contribution!
(Note to self: TODO update release notes)


When the show_numbers option is set, the files can't be seen

Description
Hey @dedukun, thanks for this wonderful plugin!
I'm using yazi 0.2.3 (at the HEAD). It seems to work with number + commands. But the problem is that I couldn't see any files besides the preview file list in the right-most section (see the screenshot below). Can you please help me figure out what's the problem here?
Screenshot

My ~/.config/yazi/init.lua
require('relative-motions'):setup({
    show_numbers = 'relative_absolute',
    show_motion = true,
})

Hey, it seems that the last commit in yazi changed the code that we are using for the render of the numbers (talk about timing... :sweat_smile:).
I'll look into the new render code and update the plugin accordingly.

Oh I see. Thanks for your prompt response. I'll try again once you're done with the update.

It works perfectly now! Thanks so much @dedukun.
BTW, it'd be good if the absolute line number gets a distinct look compared to the other relative line numbers.

What do you think would be a good look? Maybe I'll add a way for the user to configure via the setup function how they want the numbers to look.

Do you mind testing #3? If that's works as expected I'll merge into main

I've tested it and it's working quite well, at least for three-digit numbers and below. I think it's good to go! Thanks again, @dedukun.

I've merged it. I might change it a bit in the future to work better with 1000+ files and I might add a flag to disable this offset, but for now I think that it's fine like this.
I'm closing this issue, thanks for the suggestion and testing the PR.

Same problem again. Yazi says the File global variable has been removed

Hey, yes I noticed now, upstream  changed the UI extension  code, so what we have now doesn't work. I'll try to fix it as soon as possible

@ProfiGMan should be fixed in HEAD.

Works just as intended! Thanks a lot

Same problem. I tried all values of show_numbers and only none can show files/directories again

Hey @khaitranhq, what version of Yazi are you using?
A couple of weeks back, upstream changed an API that we use in the plugin and I added supported to it in 026fb16, if you are using release 0.3.3 it might be that you need to use a previous commit, I created branch https://github.com/dedukun/relative-motions.yazi/tree/0.3.3 that you can use to test it.
If that doesn't fixes your issue, please create a new issue so that we can look further into it.


[Bug Fix] Add latest tag to all image in graphscope's helm chart

While installing the graphscope helm chart, as the tag is nil, the image is rendered as registry.cn-hongkong.aliyuncs.com/graphscope/graphscope: so we can't install it as expected.

The image tag was expected to be Chart.AppVersion: https://github.com/alibaba/GraphScope/blob/main/charts/graphscope/templates/coordinator.yaml#L22
Don't use latest as tag please as it hard to ensure compatibility with the latest image version and the old chart versions.

If AppVersion is not rendered correctly, I suggest you figure out why it is not rendered, rather than changing the default value to "latest".

Make sense, the latest commit is to add default tag(Chart.AppVersion) to graphscope-store's helm chart.
It fix the following error:
$ helm install graphscope-store "./graphscope-store"
Error: INSTALLATION FAILED: YAML parse error on graphscope-store/templates/coordinator/statefulset.yaml: error converting YAML to JSON: yaml: line 39: mapping values are not allowed in this context

Codecov Report

Merging #2205 (8ee47bf) into main (4279b8f) will increase coverage by 0.02%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2205      +/-   ##
==========================================
+ Coverage   40.01%   40.03%   +0.02%
==========================================
  Files          87       87
  Lines        9752     9752
==========================================
+ Hits         3902     3904       +2
+ Misses       5850     5848       -2

Impacted Files
Coverage Δ

python/graphscope/deploy/kubernetes/utils.py
70.47% <0.00%> (+0.95%)
:arrow_up:

Continue to review full report at Codecov.

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


Sig Bus when using update/upsert with PlanetScale

Bug description
When trying to update a record using either update or upsert the node process crashes with a bus error.
Workaround: update the record using prisma.$execRaw
How to reproduce

Create a simple model using PlanetScale as the database

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["referentialIntegrity"]
}

datasource db {
  provider             = "mysql"
  url                  = env("DATABASE_URL")
  shadowDatabaseUrl    = env("SHADOW_DATABASE_URL")
  referentialIntegrity = "prisma"
}

model Counter {
  id                  String          @id @default(cuid())
  createdAt           DateTime        @default(now())
  updatedAt           DateTime        @updatedAt
  amount          Int
}

Insert a record using await prisma.counter.create(...)
Attempt to update the record using await prisma.counter.update({ data: { amount: 100 }})
Watch node crash

Expected behavior
Record should be updated in the database
Prisma information
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["referentialIntegrity"]
}

datasource db {
  provider             = "mysql"
  url                  = env("DATABASE_URL")
  shadowDatabaseUrl    = env("SHADOW_DATABASE_URL")
  referentialIntegrity = "prisma"
}

model Counter {
  id                  String          @id @default(cuid())
  createdAt           DateTime        @default(now())
  updatedAt           DateTime        @updatedAt
  amount          Int
}

Environment & setup

OS: MacOs
Database: PlanetScale (MySQL)
Node.js version: v17.2.0

Prisma Version
prisma                  : 3.6.0
@prisma/client          : 3.6.0
Current platform        : darwin
Query Engine (Node-API) : libquery-engine dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash    : dc520b92b1ebb2d28dc3161f9f82e875bd35d727
Studio                  : 0.440.0
Preview Features        : referentialIntegrity

We had the same issue with Planetscale.
Downgrading to "prisma": "3.5.0" and "@prisma/client": "3.5.0" did the job.

Another report of the SIGBUS problem:
https://github.com/prisma/prisma/discussions/10720#discussioncomment-1822126
@maximiliankaske You were/are also using referentialIntegrity = "prisma" in your schema?

Can you both @maximiliankaske and @kayleg please take another look with 3.7 to confirm this is still broken? Thanks.

Took a quick look at this myself with 3.7.0:
C:\Users\Jan\Documents\throwaway
λ mkdir 10569

C:\Users\Jan\Documents\throwaway
λ cd 10569

C:\Users\Jan\Documents\throwaway\10569
λ npm init -y
Wrote to C:\Users\Jan\Documents\throwaway\10569\package.json:

{
  "name": "10569",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}

C:\Users\Jan\Documents\throwaway\10569<EMAIL_ADDRESS>
λ npm install prisma @prisma/client

><EMAIL_ADDRESS>preinstall C:\Users\Jan\Documents\throwaway\10569\node_modules\prisma
> node scripts/preinstall-entry.js

><EMAIL_ADDRESS>install C:\Users\Jan\Documents\throwaway\10569\node_modules\prisma
> node scripts/install-entry.js

><EMAIL_ADDRESS>postinstall C:\Users\Jan\Documents\throwaway\10569\node_modules\@prisma\engines
> node download/index.js

><EMAIL_ADDRESS>postinstall C:\Users\Jan\Documents\throwaway\10569\node_modules\@prisma\client
> node scripts/postinstall.js

prisma:warn The postinstall script automatically ran `prisma generate` and did not find your `prisma/schema.prisma`.
If you have a Prisma schema file in a custom path, you will need to run
`prisma generate --schema=./path/to/your/schema.prisma` to generate Prisma Client.
If you do not have a Prisma schema file yet, you can ignore this message.

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>
+<EMAIL_ADDRESS>
added 4 packages from 1 contributor and audited 4 packages in 23.763s
found 0 vulnerabilities

C:\Users\Jan\Documents\throwaway\10569<EMAIL_ADDRESS>
λ npx prisma init --datasource-provider=mysql

✔ Your Prisma schema was created at prisma/schema.prisma
  You can now open it in your favorite editor.

Next steps:
1. Set the DATABASE_URL in the .env file to point to your existing database. If your database has no tables yet, read https://pris.ly/d/getting-started
2. Run prisma db pull to turn your database schema into a Prisma schema.
3. Run prisma generate to generate the Prisma Client. You can then start querying your database.

More information in our documentation:
https://pris.ly/d/getting-started

Then modified the schema.prisma to be:
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["referentialIntegrity"]
}

datasource db {
  provider             = "mysql"
  url                  = env("DATABASE_URL")
  referentialIntegrity = "prisma"
}

model Counter {
  id        String   @id @default(cuid())
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
  amount    Int
}

And created a database at PlanetScale, created a develop branch and then created a connection string to that via their UI, and put it in our .env file.
Then a small script.js in the root of the project:
const { PrismaClient } = require('@prisma/client')

const prisma = new PrismaClient()

// A `main` function so that we can use async/await
async function main() {

  let counter = await prisma.counter.create({
    data: {
      amount: 5
    }
  })
  console.log(counter)

  let update = await prisma.counter.update({ data: { amount: 100 }, where: { id: counter.id } })
  console.log(update)
}

main()
  .catch((e) => {
    console.error(e)
    process.exit(1)
  })
  .finally(async () => {
    await prisma.$disconnect()
  })

And that does exactly what it should be doing as far as I can see:
C:\Users\Jan\Documents\throwaway\10569>node script.js
{
  id: 'ckxhmhpgf0000lws28vg64ku1',
  createdAt: 2021-12-22T14:20:01.695Z,
  updatedAt: 2021-12-22T14:20:01.696Z,
  amount: 5
}
{
  id: 'ckxhmhpgf0000lws28vg64ku1',
  createdAt: 2021-12-22T14:20:01.695Z,
  updatedAt: 2021-12-22T14:20:01.987Z,
  amount: 100
}

(I can also not reproduce the problem with 3.6.0)

Working perfectly in 3.7.0 for me. Thanks @janpio


Improve error message when adding EKS cluster with invalid AMI

What kind of request is this (question/bug/enhancement/feature request):
Enhancement & Bug
Rancher: master on 11/29
Steps:
Add an Amazon EKS cluster with a wrong IAM role (at the Custom AMI override filed)

Result:
Failed to provision the cluster, the UI shows the error:
Error creating stack: stack failed to create: reason unknown

Rancher's log shows this error:
[ERROR] ClusterController c-wpsbk [cluster-provisioner-controller] failed with : error creating stack: stack failed to create: reason unknown
W1128 21:53:07.945215       7 reflector.go:270] github.com/rancher/norman/controller/generic_controller.go:175: watch of *v1.Event ended with: The resourceVersion for the provided watch is too old.

The EKS cluster is active on AWS console even though the IAM role is invalid.
Finally, if I delete the rke cluster from Rancher, the actual cluster on AWS will NOT be deleted.
(see the cluster named "eks"  )

The cause of this is that when an invalid AMI is used, cloudformation does not emit a CREATE_FAILED event. Instead the eventreason is tied to the ROLLBACK_IN_PROGRESS event. To fix, we just need to account for ROLLBACK_IN_PROGRESS in the stack-creation-error-handling logic, preferably with CREATE_FAILED still taking priority.

https://github.com/rancher/kontainer-engine/pull/103

Failed to validate on master 12/21
Steps are the same as the original ticket described.
Results:

:white_check_mark: the error message in Rancher provided meanful information.

:x: The corresponding eks cluster was not deleted after deleting it from Rancher.

@cjellick @maxkorp


Type coercion error in make-package-set while building

Issue description
When I run nix-build after cloning jwiegley/hoogle-local, I get the error "value is a function where a list was expected". The stack trace blames this line, character 24, which is the symbol packages.
Steps to reproduce

Clone jwiegley/hoogle-local.
Cd into the new directory and run nix-build.

Technical details

system: "x86_64-linux"
host os: Linux 4.4.0-116-generic, Ubuntu, 16.04.3 LTS (Xenial Xerus)
multi-user?: no
sandbox: no
version: nix-env (Nix) 2.0
channels(daniel): "nixpkgs-18.09pre134684.9049f8a418b"
nixpkgs: /home/daniel/.nix-defexpr/channels/nixpkgs

I don't use hoogle-local anymore, not since ghcWithHoogle became a standard part of haskellPackages. I'd encourage building a nix environment (with nix-shell or myEnvFun) based on that instead.

Should this not be an issue in hoogle-local instead of here?

Should this not be an issue in hoogle-local instead of here?
That's a good point, my bad.