Feature Request: Larger font size for 1440p and 4k res (Scaling)

Is your feature request related to a problem? Please describe.
When using your tool on hi-res monitor the font is really small
Describe the solution you'd like
Let us adjust the font size or automatically set it to a higher number if the res is higher than 1080p
Thank you for all the works ! Always a pleasure to see a new video on the channel :)

Good point, I'll see what kind of scaling I can do. It is tricky when drawing the XAML through powershell, but I think it can be done.

The current scaling is a bit funky, but I am maxing it more uniform and you can then just maximize or manually resize it and the window will scale properly now.
Currently on test 6ab999e7d375dc21dd206de5a07fd55c604b3700


Package manager console looking in wrong location for project.json

In VS2015 community I have created the defult asp.net core web app project.
In the package manager console dotnet restore works fine but dotnet build and dotnet publish both throw an error as they are looking for project.json one level up from where it was generated.
I am able to build project from menu and also run it by hitting the green play icon and it works fine, it is just these commands in the package manager console that do not work.
Is there a menu option to publish or a way to get these commands working in package manager?
Edit: I found the publish option in the context menu hen right clicking project which works fine.  It just seems some issue with typing the commands in package manager.

This issue is being closed because it has not been updated in 3 months.
We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.


Fluentd cannot communicate with OpenSearch when using HTTPS

I am trying to use the fluentd-daemonset-opensearch.yaml configuration, modifying it a little bit, so my configuration is as such:
 env:
  - name: K8S_NODE_NAME
    valueFrom:
      fieldRef:
        fieldPath: spec.nodeName
  - name: FLUENT_OPENSEARCH_HOST
    value: opensearch.storage.svc.cluster.local
  - name: FLUENT_OPENSEARCH_PORT
    value: "9200"
  - name: FLUENT_OPENSEARCH_INDEX_NAME
    value: fluentd
  - name: FLUENT_OPENSEARCH_SSL_VERIFY
    value: "false"
  - name: FLUENT_OPENSEARCH_SCHEME
    value: "https"
  - name: FLUENT_OPENSEARCH_USER
    value: "admin"
  - name: FLUENT_OPENSEARCH_PASSWORD
    value: "admin"
...

I have an OpenSearch cluster running in my cluster, with a Kubernetes Service opensearch.storage.svc.cluster.local routing traffic to it (tested connectivity - working fine).
My OpenSearch is configured with HTTPS. However, I want fluentd to skip TLS verification.
Now when applying the DaemonSet, it's not working. Running kubectl logs on one of the pods, I see this:
... rest of fluentd configuration
  </filter>
  <match **>
    @type opensearch
    @id out_os
    @log_level "info"
    include_tag_key true
    host "opensearch.storage.svc.cluster.local"
    port 9200
    path ""
    scheme https
    ssl_verify false
    ssl_version TLSv1_2
    ca_file "/etc/ca-certificates.conf"
    user "admin"
    password xxxxxx
    client_cert ""
    client_key ""
    client_key_pass xxxxxx
    index_name "fluentd"
    logstash_dateformat "%Y.%m.%d"
    logstash_format false
    logstash_prefix "logstash"
    logstash_prefix_separator "-"
    <buffer>
      flush_thread_count 1
      flush_mode interval
      flush_interval 60s
      chunk_limit_size 8M
      total_limit_size 512M
      retry_max_interval 30
      retry_timeout 72h
      retry_forever false
    </buffer>
  </match>
</ROOT>
2023-03-20 13:04:33 +0000 [info]: starting fluentd-1.15.3 pid=7 ruby="3.1.3"
2023-03-20 13:04:33 +0000 [info]: spawn command to main:  cmdline=["/usr/local/bin/ruby", "-Eascii-8bit:ascii-8bit", "/fluentd/vendor/bundle/ruby/3.1.0/bin/fluentd", "-c", "/fluentd/etc/fluent.conf", "-p", "/fluentd/plugins", "--gemfile", "/fluentd/Gemfile", "--under-supervisor"]
2023-03-20 13:04:33 +0000 [info]: init supervisor logger path=nil rotate_age=nil rotate_size=nil
2023-03-20 13:04:34 +0000 [info]: #0 init worker0 logger path=nil rotate_age=nil rotate_size=nil
2023-03-20 13:04:34 +0000 [info]: adding match in @FLUENT_LOG pattern="fluent.**" type="null"
2023-03-20 13:04:34 +0000 [info]: adding filter pattern="kubernetes.**" type="kubernetes_metadata"
2023-03-20 13:04:34 +0000 [info]: adding match pattern="**" type="opensearch"
2023-03-20 13:04:37 +0000 [warn]: #0 [out_os] Could not communicate to OpenSearch, resetting connection and trying again. No such file or directory @ rb_sysopen -  (Errno::ENOENT)
2023-03-20 13:04:37 +0000 [warn]: #0 [out_os] Remaining retry: 14. Retry to communicate after 2 second(s).
2023-03-20 13:04:41 +0000 [warn]: #0 [out_os] Could not communicate to OpenSearch, resetting connection and trying again. No such file or directory @ rb_sysopen -  (Errno::ENOENT)
2023-03-20 13:04:41 +0000 [warn]: #0 [out_os] Remaining retry: 13. Retry to communicate after 4 second(s).
2023-03-20 13:04:49 +0000 [warn]: #0 [out_os] Could not communicate to OpenSearch, resetting connection and trying again. No such file or directory @ rb_sysopen -  (Errno::ENOENT)
2023-03-20 13:04:49 +0000 [warn]: #0 [out_os] Remaining retry: 12. Retry to communicate after 8 second(s).

Can you help me understand what is the problem?

+1, have same problem, k3s.
OS is on separate nodes.

I've posted a fix here https://github.com/fluent/fluent-plugin-opensearch/issues/99#issuecomment-1527318551


[Documentation] Update package collection docs

Add information about the new Swift Package Collection certificate type, available on
developer.apple.com, that can be used for signing package collections.

@swift-ci please smoke test


Recognized Speaker from an audio file played on laptop

I ran the demo project for Eagle on my Android device it is working fine, but I got into a case where it leads to security issues.
The case is as follows:

Enrolled a speaker.
Clicked on the test button.
Played the audio of that speaker from my laptop.
It recognizes it.
And I don't want it to recognize audio from speakers. And haven't sound any solution for that inside documentations.
There must be some sensitivity options.

Thanks, But I getting almost similar scores from an audio played from an Android phone as well as if a real person is speaking.


Implement SE-0077: precedence group declarations.

What's in this pull request?

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

What I've implemented here deviates from the current proposal text
in the following ways:

I had to introduce a FunctionArrowPrecedence to capture the parsing
of -> in expression contexts.

I found it convenient to continue to model the assignment property
explicitly.

The comparison and casting operators have historically been
non-associative; I have chosen to preserve that, since I don't
think this proposal intended to change it.

This uses the precedence group names and higherThan/lowerThan
as agreed in discussion.

Pushed separately (and with some test fixes that aren't in this request).  Closing.

Hey John. I believe that this commit has still broken the build 3 hours later:
https://ci.swift.org/job/oss-swift-incremental-RA-osx/5503/consoleFull
... after the other breakage was fixed.
I am going to disable the test that is broken. Can you please use PR testing? I understand that it can be annoying, but the smoke tests do not take that long and they would have caught this failure.
Michael

On Jul 26, 2016, at 2:38 PM, rjmccall<EMAIL_ADDRESS>wrote:
Pushed separately (and with some test fixes that aren't in this request). Closing.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/apple/swift/pull/3770#issuecomment-235413262, or mute the thread https://github.com/notifications/unsubscribe-auth/AAee33KqkP9rSXQMqXWhCklnnR1v-YATks5qZn5zgaJpZM4JVdwv.


Zookeeper: A HostProvider may not be empty!

Using phoenix driver on OSX gives this error, linux version works. Debug log stacktrace attached here:
dbeaver-debug.log

turned out to be a dns problem on our network


Is there any way to show build status in the PR list?

It'd be great to be able to see the build status in the PR list. I'm going to try to do it with filters, but an icon next to a PR would be amazing. Perhaps I could try to contribute something like this, if it's ok and not an intentionally omitted feature.

@valyagolev this seems like this feature could result in a big performance hit. It might be expensive to fetch the build status of each pr in the list.

if github API doesn’t return it with the list of PR, then yes, I suppose. In this case one might only enable it for a particular filter, e.g. for their own PRs

We now show the PR checks status in the PRs list.


Install dependencies in codecov workflow

Codecov Report

:exclamation: No coverage uploaded for pull request base (codecov@ed90b58). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             codecov       #3   +/-   ##
==========================================
  Coverage           ?   91.91%
==========================================
  Files              ?       25
  Lines              ?     1212
  Branches           ?        0
==========================================
  Hits               ?     1114
  Misses             ?       98
  Partials           ?        0

Flag
Coverage Δ

unittests
91.91% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Remote configuration support

Also including Dynamic Configuration, but it's a small part, just 100 lines of code, describing the structures it contains.
As to more specific changes to current code:

The sidecar is now per user (on windows it already uses the ConsoleSession), instead of per system.

On Windows it was necessary as memory can only easily be shared within a ConsoleSession.
On Linux it's now necessary as the notification mechanism for changes to the remote config are distributed via signals, which require either same euid or root-like capabilities.
Note AsBytes in ddcommon currently requires &'a AsBytes<'a>, while only &AsBytes<'a> (independent lifetime) is required.

General notes:

Code in remote-config/ is meant to be reusable and also accessible via FFI as needed. For most users the bare ConfigFetcher should be enough, and for some the SharedFetcher is needed. Fewest should actually need the MultiTargetFetcher. A FFi interface hasn't been defined yet as it wasn't needed:

ConfigFetcher in its simplest usage is just one function with two callbacks (store, update) essentially. StoredFile should be a wrapper for a type native to the FFI user (a pointer probably).
SharedFetcher is similar, but presents a run-loop. To be used in anyway multi-threaded applications, now three callbacks: store, update and on_fetched.

The sidecar will notify participating processes whenever remote config changes.
The sidecar uses shared memory to transmit the stuff received by the remote-config stuff.

The rustls bump will be moved later to its own PR, please ignore - it's required for windows though - and windows is still failing to build. Will be fixed soon. This causes some github actions to be broken, please ignore.
The regular testsuite seems to be verified by the coverage run though.

Codecov Report
Attention: Patch coverage is 80.67227% with 506 lines in your changes missing coverage. Please review.

Project coverage is 71.07%. Comparing base (fc6e92b) to head (f92d3f1).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #488      +/-   ##
==========================================
+ Coverage   69.67%   71.07%   +1.39%
==========================================
  Files         199      212      +13
  Lines       26606    29190    +2584
==========================================
+ Hits        18539    20748    +2209
- Misses       8067     8442     +375

Components
Coverage Δ

crashtracker
17.46% <ø> (ø)

datadog-alloc
98.76% <ø> (ø)

data-pipeline
51.30% <ø> (ø)

data-pipeline-ffi
0.00% <ø> (ø)

ddcommon
85.12% <41.46%> (-0.85%)
:arrow_down:

ddcommon-ffi
71.00% <19.04%> (-3.16%)
:arrow_down:

ddtelemetry
56.37% <ø> (ø)

ipc
84.77% <ø> (+0.10%)
:arrow_up:

profiling
79.13% <ø> (ø)

profiling-ffi
59.53% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
42.77% <59.72%> (+6.50%)
:arrow_up:

sidecar-ffi
0.00% <0.00%> (ø)

spawn-worker
54.98% <ø> (ø)

trace-mini-agent
69.36% <ø> (ø)

trace-normalization
97.79% <ø> (ø)

trace-obfuscation
95.73% <ø> (ø)

trace-protobuf
50.00% <77.55%> (+25.47%)
:arrow_up:

trace-utils
91.05% <0.00%> (+0.25%)
:arrow_up:

@brettlangdon Implemented some helper functionality to auto-parse, diff and locally store remote config files.
These all weren't needed for the purposes of the sidecar (sidecar doesn't parse most things, but just writes them to shared memory, no explicit backing storage needed; diffing happened based on shared memory contents in target processes.), but they are probably useful for most implementers.
Please have a look at examples/remote_config_fetch.rs.

Please split this up in separate PR, nobody can review this much code at once

Please consider the files in remote-config individually:
fetch/fetcher.rs as the primary RC client.
fetch/shared.rs for sharing file storage.
fetch/multitarget.rs for multiple targets.
fetch/single.rs for users just needing a single client, packaged in an a bit nicer API. Uses file_change_tracker.rs and file_storage.rs
Then parse.rs to process remote config paths / provide an entry point to the individual products.
I don't intend to split this RC beyond the point where I can do minimal end-to-end testing.


sideEffects

Hi, currently, the project's package.json file does not include the "sideEffects" field. Adding this field with the value set to false can provide potential optimisations and improve the overall performance of the project.
When "sideEffects" is set to false in the package.json file, it indicates that the package does not have any side effects during its usage. This information can be used by tools like Webpack to perform tree-shaking, eliminating unused code during the bundling process. Consequently, this reduces the bundle size and improves the loading speed of the project.

The package that this package depends on media-query-parser has been fixed, and now this downstream package will be fixed


Sync eng/common directory with azure-sdk-tools for PR 6465

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/6465  See eng/common workflow

@heaths this PR includes the gpg signing hang bug that you identified. My proxy version bump last week failed to update your package data props and actually change which proxy gets used. 🙄 This one doesn't have the same issue.


Custom Igniter Config Request

Hello! Love your mod! Can't wait for more updates.
I'm trying to make it fit in my progression based modpack and I was wondering if by chance there can be a way to allow the user to use a different igniter item as opposed to flint and steel and /or have a way to replace the blocks used for the portal platform. (i.e. replacing the center Gold Block with Brass from Create or similar.
Thank you so much for your time and patience.

Ok, adding that to the config gui on 21.0.0


Delete occurrences of theme accent color

Description
Prerequisite to solve insufficient color contrast accessibility issues by mapping from classic to PatternFly theme.
Problem
PatternFly color palette does not have magenta.
https://www.patternfly.org/v4/guidelines/colors#color-palette
Analysis

Redundantly distinguishes value from key by accent color in addition to either font style or weight:

src/Components/KeyValuePairs.js
src/Containers/Network/SidePanel/NetworkDeploymentOverlay/DeploymentDetails/ContainerConfigurations.tsx
src/Containers/Risk/ContainerConfigurations.js

Distinction between secondary and accent is hard in light theme and even harder in dark theme (see pictures).

Double style inconsistency accent versus primary above, and both are heading text that look like buttons or links. Too bad, so sad that icon apparently has inherent color independent of theme variables for Generate network policies heading (see pictures).

src/Containers/Network/SidePanel/Creator/Tiles/UploadNetworkPolicySection.tsx

Unique color in BrushableOverlay for timeline graph in Risk.

src/Components/TimelineGraph/Minimap/BrushableOverlay.js

Unused color type constants because no React element has type="accent" prop nor any data has colorType: 'accent' property:

src/constants/visuals/colors.ts

Solution

Follow example of PatternFly in which font-700 distinguishes key from value.

Remove color classes from heading text, especially because they are not links.

Remove distinction from background of modal.

Delete accent from color types. Notice that there are not enough colors for 6 compliance standards and the fifth is hard to distinguish from the second. Therefore, provide only two alternating colors for bar charts, and so on.

Residue

Investigate which theme classes does API Reference need from .redoc-wrap {…} style rule in app.tw.css file.

Checklist

[ ] Investigated and inspected CI test results
[x] ~Unit test and regression tests added~

Testing Performed

yarn build in ui

wc build/static/js/*.js
branch - master: -504 = 11724000 - 11724504

Manual testing

KeyValuePairs and so on

with accent in dark theme

without accent in dark theme

with accent in light theme

without accent in light theme

UploadNetworkPolicySection

with accent in dark theme

without accent in dark theme

with accent in light theme

without accent in light theme

BrushableOverlay

with accent in dark theme

without accent in dark theme

with accent in light theme

without accent in light theme

VerticalBarChart

with accent among 5 colors in dark theme

without accent among 2 colors in dark theme

with accent among 5 colors in light theme

without accent among 2 colors in light theme

@pedrottimark for the VerticalBarChart I find that the color use was and still looks a bit odd. Before, it looked like we used the same color for multiple bars. In the new one we have fewer differentiating bars so the legend seems a bit confusing

@sachaudh Thank you for review comments.

I restored var(--accent-500) for BrushableOverlay as the only use of accent color.
I added darker and then lighter triplets of base, primary, secondary colors for the 6 bars in Compliance Passing Standards by Clusters. It might become the only use of secondary color. Because Compliance Operator might have even more standards, we should avoid this type of color coding in the future. For example, a humble table with standard name and percent passing columns avoids color entirely, and also has clear idioms for filtering, paging, and sorting.

dark theme

light theme


[#115429827] Enable basic auth for kibana

What
https://www.pivotaltracker.com/story/show/115429827
Use HAProxy from the logsearch release to put http basic auth in front of Kibana.
How to review

Deploy the branch
Run make dev showenv, notice that KIBANA_ADMIN_PASSWORD is shown
Visit the logsearch URL
Verify that http basic auth is required, and that the creds admin/<KIBANA_ADMIN_PASSWORD> give access

Who can review
not @benhyland

For consistence with grafana #604  and #606, can we show the password in make showenv
Note that the good implementation is #606, the other one broke stuff

@keymon I don't understand what you are asking for.
What do you want done differently?

@benhyland sorry, the summary in the card did no mention it and I though you did not implement it. It is fine.

Cool, np then

works correctly, thanks for DRYing passwords script


[🐛 Bug]: Unable to use the NodeJS compatibility layer with Next.js Edge Runtime Apps

next-on-pages environment related information
➤ YN0000: ┌ Resolution step
➤ YN0032: │ fsevents@npm:2.3.2: Implicit dependencies on node-gyp are discouraged
➤ YN0061: │ @npmcli/move-file@npm:2.0.1 is deprecated: This functionality has been moved to @npmcli/fs
➤ YN0002: │ root-workspace-0b6124@workspace:. doesn't provide vercel (p45a97), requested by @cloudflare/next-on-pages
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed in 1s 226ms
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed
➤ YN0000: ┌ Link step
➤ YN0007: │ esbuild@npm:0.15.18 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 0s 747ms
➤ YN0000: Done with warnings in 2s 52ms

System:
        Platform: darwin
        Arch: arm64
        Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
        CPU: (8) arm64 Apple M1 Pro
        Memory: 16 GB
        Shell: /bin/zsh
Binaries:
        Node: 20.1.0
        Yarn: 3.5.0
        npm: 9.6.4
        pnpm: N/A
Package Manager Used: yarn (berry)
Relevant Packages:
        @cloudflare/next-on-pages: 0.10.1
        vercel: N/A
        next: N/A

Description
I thought that Cloudflare had a NodeJS compatability layer, however despite this I'm unable to build Next.js apps with the Edge runtime. Maybe this is due to Next.js's own cloud "Vercel" not supporting these APIs when edge deployed? It's very unclear to me what is meant to work and whether there is simply a mismatch between what Cloudflare supports in its edge deployments and what Next.js does...?
See:
▲  Vercel CLI 29.3.3
▲  Installing dependencies...
▲  ➤ YN0000: ┌ Resolution step
▲  ➤ YN0002: │ sebinsua-blog@workspace:. doesn't provide vercel (peba7b), requested by @cloudflare/next-on-pages
▲  ➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
▲  ➤ YN0000: └ Completed
▲  ➤ YN0000: ┌ Fetch step
▲  ➤ YN0013: │ 949 packages were already cached
▲  ➤ YN0000: └ Completed in 0s 240ms
▲  ➤ YN0000: ┌ Link step
▲  ➤ YN0000: └ Completed
▲  ➤ YN0000: Done with warnings in 0s 580ms
▲  Detected Next.js version: 13.4.2
▲  Running "yarn run build"
▲  - warn You have enabled experimental feature (typedRoutes) in next.config.js.
▲  - warn Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
▲
▲  - info Creating an optimized production build...
▲  Failed to compile.
▲  ./node_modules/@typescript/vfs/dist/vfs.esm.js:140:13
▲  Module not found: Can't resolve 'path'
▲
▲  https://nextjs.org/docs/messages/module-not-found
▲
▲  Import trace for requested module:
▲  ./lib/renderMarkdown.ts
▲  ./app/[slug]/page.tsx
▲  ./node_modules/next/dist/build/webpack/loaders/next-edge-ssr-loader/index.js?absolute500Path=&absoluteAppPath=next%2Fdist%2Fpages%2F_app&absoluteDocumentPath=next%2Fdist%2Fpages%2F_document&absoluteErrorPath=next%2Fdist%2Fpages%2F_error&absolutePagePath=private-next-app-dir%2F%5Bslug%5D%2Fpage.tsx&buildId=x3qXo4BIua3WoUC7-5BUE&dev=false&isServerComponent=true&page=%2F%5Bslug%5D%2Fpage&stringifiedConfig=%7B%22env%22%3A%7B%7D%2C%22eslint%22%3A%7B%22ignoreDuringBuilds%22%3Afalse%7D%2C%22typescript%22%3A%7B%22ignoreBuildErrors%22%3Afalse%2C%22tsconfigPath%22%3A%22tsconfig.json%22%7D%2C%22distDir%22%3A%22.next%22%2C%22cleanDistDir%22%3Atrue%2C%22assetPrefix%22%3A%22%22%2C%22configOrigin%22%3A%22next.config.js%22%2C%22useFileSystemPublicRoutes%22%3Atrue%2C%22generateEtags%22%3Atrue%2C%22pageExtensions%22%3A%5B%22tsx%22%2C%22ts%22%2C%22jsx%22%2C%22js%22%5D%2C%22poweredByHeader%22%3Atrue%2C%22compress%22%3Atrue%2C%22analyticsId%22%3A%22%22%2C%22images%22%3A%7B%22deviceSizes%22%3A%5B640%2C750%2C828%2C1080%2C1200%2C1920%2C2048%2C3840%5D%2C%22imageSizes%22%3A%5B16%2C32%2C48%2C64%2C96%2C128%2C256%2C384%5D%2C%22path%22%3A%22%2F_next%2Fimage%2F%22%2C%22loader%22%3A%22custom%22%2C%22loaderFile%22%3A%22%22%2C%22domains%22%3A%5B%5D%2C%22disableStaticImages%22%3Afalse%2C%22minimumCacheTTL%22%3A60%2C%22formats%22%3A%5B%22image%2Fwebp%22%5D%2C%22dangerouslyAllowSVG%22%3Afalse%2C%22contentSecurityPolicy%22%3A%22script-src%20'none'%3B%20frame-src%20'none'%3B%20sandbox%3B%22%2C%22contentDispositionType%22%3A%22inline%22%2C%22remotePatterns%22%3A%5B%5D%2C%22unoptimized%22%3Afalse%7D%2C%22devIndicators%22%3A%7B%22buildActivity%22%3Atrue%2C%22buildActivityPosition%22%3A%22bottom-right%22%7D%2C%22onDemandEntries%22%3A%7B%22maxInactiveAge%22%3A15000%2C%22pagesBufferLength%22%3A2%7D%2C%22amp%22%3A%7B%22canonicalBase%22%3A%22%22%7D%2C%22basePath%22%3A%22%22%2C%22sassOptions%22%3A%7B%7D%2C%22trailingSlash%22%3Afalse%2C%22i18n%22%3Anull%2C%22productionBrowserSourceMaps%22%3Afalse%2C%22optimizeFonts%22%3Atrue%2C%22excludeDefaultMomentLocales%22%3Atrue%2C%22serverRuntimeConfig%22%3A%7B%7D%2C%22publicRuntimeConfig%22%3A%7B%7D%2C%22reactStrictMode%22%3Atrue%2C%22httpAgentOptions%22%3A%7B%22keepAlive%22%3Atrue%7D%2C%22outputFileTracing%22%3Atrue%2C%22staticPageGenerationTimeout%22%3A60%2C%22swcMinify%22%3Atrue%2C%22experimental%22%3A%7B%22appDocumentPreloading%22%3Atrue%2C%22clientRouterFilter%22%3Atrue%2C%22clientRouterFilterRedirects%22%3Afalse%2C%22fetchCacheKeyPrefix%22%3A%22%22%2C%22middlewarePrefetch%22%3A%22flexible%22%2C%22optimisticClientCache%22%3Atrue%2C%22manualClientBasePath%22%3Afalse%2C%22legacyBrowsers%22%3Afalse%2C%22newNextLinkBehavior%22%3Atrue%2C%22cpus%22%3A7%2C%22sharedPool%22%3Atrue%2C%22isrFlushToDisk%22%3Atrue%2C%22workerThreads%22%3Afalse%2C%22pageEnv%22%3Afalse%2C%22optimizeCss%22%3Afalse%2C%22nextScriptWorkers%22%3Afalse%2C%22scrollRestoration%22%3Afalse%2C%22externalDir%22%3Afalse%2C%22disableOptimizedLoading%22%3Afalse%2C%22gzipSize%22%3Atrue%2C%22swcFileReading%22%3Atrue%2C%22craCompat%22%3Afalse%2C%22esmExternals%22%3Atrue%2C%22appDir%22%3Atrue%2C%22isrMemoryCacheSize%22%3A52428800%2C%22fullySpecified%22%3Afalse%2C%22outputFileTracingRoot%22%3A%22%2FUsers%2Fsebinsua%2Fdev%2Fdotcom%22%2C%22swcTraceProfiling%22%3Afalse%2C%22forceSwcTransforms%22%3Afalse%2C%22largePageDataBytes%22%3A128000%2C%22adjustFontFallbacks%22%3Afalse%2C%22adjustFontFallbacksWithSizeAdjust%22%3Afalse%2C%22typedRoutes%22%3Atrue%2C%22instrumentationHook%22%3Afalse%7D%2C%22configFile%22%3A%22%2FUsers%2Fsebinsua%2Fdev%2Fdotcom%2Fnext.config.js%22%2C%22configFileName%22%3A%22next.config.js%22%7D&pagesType=app&appDirLoader=bmV4dC1hcHAtbG9hZGVyP25hbWU9YXBwJTJGJTVCc2x1ZyU1RCUyRnBhZ2UmcGFnZT0lMkYlNUJzbHVnJTVEJTJGcGFnZSZwYWdlUGF0aD1wcml2YXRlLW5leHQtYXBwLWRpciUyRiU1QnNsdWclNUQlMkZwYWdlLnRzeCZhcHBEaXI9JTJGVXNlcnMlMkZzZWJpbnN1YSUyRmRldiUyRmRvdGNvbSUyRmFwcCZhcHBQYXRocz0lMkYlNUJzbHVnJTVEJTJGcGFnZSZwYWdlRXh0ZW5zaW9ucz10c3gmcGFnZUV4dGVuc2lvbnM9dHMmcGFnZUV4dGVuc2lvbnM9anN4JnBhZ2VFeHRlbnNpb25zPWpzJmJhc2VQYXRoPSZhc3NldFByZWZpeD0mbmV4dENvbmZpZ091dHB1dD0mcHJlZmVycmVkUmVnaW9uPSE%3D&sriEnabled=false&incrementalCacheHandlerPath=&preferredRegion=!
▲
▲  ./node_modules/cacheable-lookup/source/index.js:10:4
▲  Module not found: Can't resolve 'dns'
▲
▲  https://nextjs.org/docs/messages/module-not-found
▲
▲  Import trace for requested module:
▲  ./node_modules/got/dist/source/core/index.js
▲  ./node_modules/got/dist/source/create.js
▲  ./node_modules/got/dist/source/index.js
▲  ./node_modules/remark-oembed/index.js
▲  ./lib/renderMarkdown.ts
▲  ./app/[slug]/page.tsx
▲  ./node_modules/next/dist/build/webpack/loaders/next-edge-ssr-loader/index.js?absolute500Path=&absoluteAppPath=next%2Fdist%2Fpages%2F_app&absoluteDocumentPath=next%2Fdist%2Fpages%2F_document&absoluteErrorPath=next%2Fdist%2Fpages%2F_error&absolutePagePath=private-next-app-dir%2F%5Bslug%5D%2Fpage.tsx&buildId=x3qXo4BIua3WoUC7-5BUE&dev=false&isServerComponent=true&page=%2F%5Bslug%5D%2Fpage&stringifiedConfig=%7B%22env%22%3A%7B%7D%2C%22eslint%22%3A%7B%22ignoreDuringBuilds%22%3Afalse%7D%2C%22typescript%22%3A%7B%22ignoreBuildErrors%22%3Afalse%2C%22tsconfigPath%22%3A%22tsconfig.json%22%7D%2C%22distDir%22%3A%22.next%22%2C%22cleanDistDir%22%3Atrue%2C%22assetPrefix%22%3A%22%22%2C%22configOrigin%22%3A%22next.config.js%22%2C%22useFileSystemPublicRoutes%22%3Atrue%2C%22generateEtags%22%3Atrue%2C%22pageExtensions%22%3A%5B%22tsx%22%2C%22ts%22%2C%22jsx%22%2C%22js%22%5D%2C%22poweredByHeader%22%3Atrue%2C%22compress%22%3Atrue%2C%22analyticsId%22%3A%22%22%2C%22images%22%3A%7B%22deviceSizes%22%3A%5B640%2C750%2C828%2C1080%2C1200%2C1920%2C2048%2C3840%5D%2C%22imageSizes%22%3A%5B16%2C32%2C48%2C64%2C96%2C128%2C256%2C384%5D%2C%22path%22%3A%22%2F_next%2Fimage%2F%22%2C%22loader%22%3A%22custom%22%2C%22loaderFile%22%3A%22%22%2C%22domains%22%3A%5B%5D%2C%22disableStaticImages%22%3Afalse%2C%22minimumCacheTTL%22%3A60%2C%22formats%22%3A%5B%22image%2Fwebp%22%5D%2C%22dangerouslyAllowSVG%22%3Afalse%2C%22contentSecurityPolicy%22%3A%22script-src%20'none'%3B%20frame-src%20'none'%3B%20sandbox%3B%22%2C%22contentDispositionType%22%3A%22inline%22%2C%22remotePatterns%22%3A%5B%5D%2C%22unoptimized%22%3Afalse%7D%2C%22devIndicators%22%3A%7B%22buildActivity%22%3Atrue%2C%22buildActivityPosition%22%3A%22bottom-right%22%7D%2C%22onDemandEntries%22%3A%7B%22maxInactiveAge%22%3A15000%2C%22pagesBufferLength%22%3A2%7D%2C%22amp%22%3A%7B%22canonicalBase%22%3A%22%22%7D%2C%22basePath%22%3A%22%22%2C%22sassOptions%22%3A%7B%7D%2C%22trailingSlash%22%3Afalse%2C%22i18n%22%3Anull%2C%22productionBrowserSourceMaps%22%3Afalse%2C%22optimizeFonts%22%3Atrue%2C%22excludeDefaultMomentLocales%22%3Atrue%2C%22serverRuntimeConfig%22%3A%7B%7D%2C%22publicRuntimeConfig%22%3A%7B%7D%2C%22reactStrictMode%22%3Atrue%2C%22httpAgentOptions%22%3A%7B%22keepAlive%22%3Atrue%7D%2C%22outputFileTracing%22%3Atrue%2C%22staticPageGenerationTimeout%22%3A60%2C%22swcMinify%22%3Atrue%2C%22experimental%22%3A%7B%22appDocumentPreloading%22%3Atrue%2C%22clientRouterFilter%22%3Atrue%2C%22clientRouterFilterRedirects%22%3Afalse%2C%22fetchCacheKeyPrefix%22%3A%22%22%2C%22middlewarePrefetch%22%3A%22flexible%22%2C%22optimisticClientCache%22%3Atrue%2C%22manualClientBasePath%22%3Afalse%2C%22legacyBrowsers%22%3Afalse%2C%22newNextLinkBehavior%22%3Atrue%2C%22cpus%22%3A7%2C%22sharedPool%22%3Atrue%2C%22isrFlushToDisk%22%3Atrue%2C%22workerThreads%22%3Afalse%2C%22pageEnv%22%3Afalse%2C%22optimizeCss%22%3Afalse%2C%22nextScriptWorkers%22%3Afalse%2C%22scrollRestoration%22%3Afalse%2C%22externalDir%22%3Afalse%2C%22disableOptimizedLoading%22%3Afalse%2C%22gzipSize%22%3Atrue%2C%22swcFileReading%22%3Atrue%2C%22craCompat%22%3Afalse%2C%22esmExternals%22%3Atrue%2C%22appDir%22%3Atrue%2C%22isrMemoryCacheSize%22%3A52428800%2C%22fullySpecified%22%3Afalse%2C%22outputFileTracingRoot%22%3A%22%2FUsers%2Fsebinsua%2Fdev%2Fdotcom%22%2C%22swcTraceProfiling%22%3Afalse%2C%22forceSwcTransforms%22%3Afalse%2C%22largePageDataBytes%22%3A128000%2C%22adjustFontFallbacks%22%3Afalse%2C%22adjustFontFallbacksWithSizeA
▲  djust%22%3Afalse%2C%22typedRoutes%22%3Atrue%2C%22instrumentationHook%22%3Afalse%7D%2C%22configFile%22%3A%22%2FUsers%2Fsebinsua%2Fdev%2Fdotcom%2Fnext.config.js%22%2C%22configFileName%22%3A%22next.config.js%22%7D&pagesType=app&appDirLoader=bmV4dC1hcHAtbG9hZGVyP25hbWU9YXBwJTJGJTVCc2x1ZyU1RCUyRnBhZ2UmcGFnZT0lMkYlNUJzbHVnJTVEJTJGcGFnZSZwYWdlUGF0aD1wcml2YXRlLW5leHQtYXBwLWRpciUyRiU1QnNsdWclNUQlMkZwYWdlLnRzeCZhcHBEaXI9JTJGVXNlcnMlMkZzZWJpbnN1YSUyRmRldiUyRmRvdGNvbSUyRmFwcCZhcHBQYXRocz0lMkYlNUJzbHVnJTVEJTJGcGFnZSZwYWdlRXh0ZW5zaW9ucz10c3gmcGFnZUV4dGVuc2lvbnM9dHMmcGFnZUV4dGVuc2lvbnM9anN4JnBhZ2VFeHRlbnNpb25zPWpzJmJhc2VQYXRoPSZhc3NldFByZWZpeD0mbmV4dENvbmZpZ091dHB1dD0mcHJlZmVycmVkUmVnaW9uPSE%3D&sriEnabled=false&incrementalCacheHandlerPath=&preferredRegion=!
▲
▲  ./node_modules/cacheable-lookup/source/index.js:12:11
▲  Module not found: Can't resolve 'os'
▲
▲  https://nextjs.org/docs/messages/module-not-found
▲
▲  Import trace for requested module:
▲  ./node_modules/got/dist/source/core/index.js
▲  ./node_modules/got/dist/source/create.js
▲  ./node_modules/got/dist/source/index.js
▲  ./node_modules/remark-oembed/index.js
▲  ./lib/renderMarkdown.ts
▲  ./app/[slug]/page.tsx
▲  ./node_modules/next/dist/build/webpack/loaders/next-edge-ssr-loader/index.js?absolute500Path=&absoluteAppPath=next%2Fdist%2Fpages%2F_app&absoluteDocumentPath=next%2Fdist%2Fpages%2F_document&absoluteErrorPath=next%2Fdist%2Fpages%2F_error&absolutePagePath=private-next-app-dir%2F%5Bslug%5D%2Fpage.tsx&buildId=x3qXo4BIua3WoUC7-5BUE&dev=false&isServerComponent=true&page=%2F%5Bslug%5D%2Fpage&stringifiedConfig=%7B%22env%22%3A%7B%7D%2C%22eslint%22%3A%7B%22ignoreDuringBuilds%22%3Afalse%7D%2C%22typescript%22%3A%7B%22ignoreBuildErrors%22%3Afalse%2C%22tsconfigPath%22%3A%22tsconfig.json%22%7D%2C%22distDir%22%3A%22.next%22%2C%22cleanDistDir%22%3Atrue%2C%22assetPrefix%22%3A%22%22%2C%22configOrigin%22%3A%22next.config.js%22%2C%22useFileSystemPublicRoutes%22%3Atrue%2C%22generateEtags%22%3Atrue%2C%22pageExtensions%22%3A%5B%22tsx%22%2C%22ts%22%2C%22jsx%22%2C%22js%22%5D%2C%22poweredByHeader%22%3Atrue%2C%22compress%22%3Atrue%2C%22analyticsId%22%3A%22%22%2C%22images%22%3A%7B%22deviceSizes%22%3A%5B640%2C750%2C828%2C1080%2C1200%2C1920%2C2048%2C3840%5D%2C%22imageSizes%22%3A%5B16%2C32%2C48%2C64%2C96%2C128%2C256%2C384%5D%2C%22path%22%3A%22%2F_next%2Fimage%2F%22%2C%22loader%22%3A%22custom%22%2C%22loaderFile%22%3A%22%22%2C%22domains%22%3A%5B%5D%2C%22disableStaticImages%22%3Afalse%2C%22minimumCacheTTL%22%3A60%2C%22formats%22%3A%5B%22image%2Fwebp%22%5D%2C%22dangerouslyAllowSVG%22%3Afalse%2C%22contentSecurityPolicy%22%3A%22script-src%20'none'%3B%20frame-src%20'none'%3B%20sandbox%3B%22%2C%22contentDispositionType%22%3A%22inline%22%2C%22remotePatterns%22%3A%5B%5D%2C%22unoptimized%22%3Afalse%7D%2C%22devIndicators%22%3A%7B%22buildActivity%22%3Atrue%2C%22buildActivityPosition%22%3A%22bottom-right%22%7D%2C%22onDemandEntries%22%3A%7B%22maxInactiveAge%22%3A15000%2C%22pagesBufferLength%22%3A2%7D%2C%22amp%22%3A%7B%22canonicalBase%22%3A%22%22%7D%2C%22basePath%22%3A%22%22%2C%22sassOptions%22%3A%7B%7D%2C%22trailingSlash%22%3Afalse%2C%22i18n%22%3Anull%2C%22productionBrowserSourceMaps%22%3Afalse%2C%22optimizeFonts%22%3Atrue%2C%22excludeDefaultMomentLocales%22%3Atrue%2C%22serverRuntimeConfig%22%3A%7B%7D%2C%22publicRuntimeConfig%22%3A%7B%7D%2C%22reactStrictMode%22%3Atrue%2C%22httpAgentOptions%22%3A%7B%22keepAlive%22%3Atrue%7D%2C%22outputFileTracing%22%3Atrue%2C%22staticPageGenerationTimeout%22%3A60%2C%22swcMinify%22%3Atrue%2C%22experimental%22%3A%7B%22appDocumentPreloading%22%3Atrue%2C%22clientRouterFilter%22%3Atrue%2C%22clientRouterFilterRedirects%22%3Afalse%2C%22fetchCacheKeyPrefix%22%3A%22%22%2C%22middlewarePrefetch%22%3A%22flexible%22%2C%22optimisticClientCache%22%3Atrue%2C%22manualClientBasePath%22%3Afalse%2C%22legacyBrowsers%22%3Afalse%2C%22newNextLinkBehavior%22%3Atrue%2C%22cpus%22%3A7%2C%22sharedPool%22%3Atrue%2C%22isrFlushToDisk%22%3Atrue%2C%22workerThreads%22%3Afalse%2C%22pageEnv%22%3Afalse%2C%22optimizeCss%22%3Afalse%2C%22nextScriptWorkers%22%3Afalse%2C%22scrollRestoration%22%3Afalse%2C%22externalDir%22%3Afalse%2C%22disableOptimizedLoading%22%3Afalse%2C%22gzipSize%22%3Atrue%2C%22swcFileReading%22%3Atrue%2C%22craCompat%22%3Afalse%2C%22esmExternals%22%3Atrue%2C%22appDir%22%3Atrue%2C%22isrMemoryCacheSize%22%3A52428800%2C%22fullySpecified%22%3Afalse%2C%22outputFileTracingRoot%22%3A%22%2FUsers%2Fsebinsua%2Fdev%2Fdotcom%22%2C%22swcTraceProfiling%22%3Afalse%2C%22forceSwcTransforms%22%3Afalse%2C%22largePageDataBytes%22%3A128000%2C%22adjustFontFallbacks%22%3Afalse%2C%22adjustFontFallbacksWithSizeAdjust%22%3Afalse%2C%22typedRoutes%22%3Atrue%2C%22instrumentationHook%22%3Afalse%7D%2C%22configFile%22%3A%22%2FUsers%2Fsebinsua%2Fdev%2Fdotcom%2Fnext.config.js%22%2C%22configFileName%22%3A%22next.config.js%22%7D&pagesType=app&appDirLoader=bmV4dC1hcHAtbG9hZGVyP25hbWU9YXBwJTJGJTVCc2x1ZyU1RCUyRnBhZ2UmcGFnZT0lMkYlNUJzbHVnJTVEJTJGcGFnZSZwYWdlUGF0aD1wcml2YXRlLW5leHQtYXBwLWRpciUyRiU1QnNsdWclNUQlMkZwYWdlLnRzeCZhcHBEaXI9JTJGVXNlcnMlMkZzZWJpbnN1YSUyRmRldiUyRmRvdGNvbSUyRmFwcCZhcHBQYXRocz0lMkYlNUJzbHVnJTVEJTJGcGFnZSZwYWdlRXh0ZW5zaW9ucz10c3gmcGFnZUV4dGVuc2lvbnM9dHMmcGFnZUV4dGVuc2lvbnM9anN4JnBhZ2VFeHRlbnNpb25zPWpzJmJhc2VQYXRoPSZhc3NldFByZWZpeD0mbmV4dENvbmZpZ091dHB1dD0mcHJlZmVycmVkUmVnaW9uPSE%3D&sriEnabled=false&incrementalCacheHandlerPath=&preferredRegion=!
▲
▲  ./node_modules/clone-response/src/index.js:3:20
▲  Module not found: Can't resolve 'stream'
▲
▲  https://nextjs.org/docs/messages/module-not-found
▲
▲  Import trace for requested module:
▲  ./node_modules/cacheable-request/src/index.js
▲  ./node_modules/got/dist/source/core/index.js
▲  ./node_modules/got/dist/source/create.js
▲  ./node_modules/got/dist/source/index.js
▲  ./node_modules/remark-oembed/index.js
▲  ./lib/renderMarkdown.ts
▲  ./app/[slug]/page.tsx
▲  ./node_modules/next/dist/build/webpack/loaders/next-edge-ssr-loader/index.js?absolute500Path=&absoluteAppPath=next%2Fdist%2Fpages%2F_app&absoluteDocumentPath=next%2Fdist%2Fpages%2F_document&absoluteErrorPath=next%2Fdist%2Fpages%2F_error&absolutePagePath=private-next-app-dir%2F%5Bslug%5D%2Fpage.tsx&buildId=x3qXo4BIua3WoUC7-5BUE&dev=false&isServerComponent=true&page=%2F%5Bslug%5D%2Fpage&stringifiedConfig=%7B%22env%22%3A%7B%7D%2C%22eslint%22%3A%7B%22ignoreDuringBuilds%22%3Afalse%7D%2C%22typescript%22%3A%7B%22ignoreBuildErrors%22%3Afalse%2C%22tsconfigPath%22%3A%22tsconfig.json%22%7D%2C%22distDir%22%3A%22.next%22%2C%22cleanDistDir%22%3Atrue%2C%22assetPrefix%22%3A%22%22%2C%22configOrigin%22%3A%22next.config.js%22%2C%22useFileSystemPublicRoutes%22%3Atrue%2C%22generateEtags%22%3Atrue%2C%22pageExtensions%22%3A%5B%22tsx%22%2C%22ts%22%2C%22jsx%22%2C%22js%22%5D%2C%22poweredByHeader%22%3Atrue%2C%22compress%22%3Atrue%2C%22analyticsId%22%3A%22%22%2C%22images%22%3A%7B%22deviceSizes%22%3A%5B640%2C750%2C828%2C1080%2C1200%2C1920%2C2048%2C3840%5D%2C%22imageSizes%22%3A%5B16%2C32%2C48%2C64%2C96%2C128%2C256%2C384%5D%2C%22path%22%3A%22%2F_next%2Fimage%2F%22%2C%22loader%22%3A%22custom%22%2C%22loaderFile%22%3A%22%22%2C%22domains%22%3A%5B%5D%2C%22disableStaticImages%22%3Afalse%2C%22minimumCacheTTL%22%3A60%2C%22formats%22%3A%5B%22image%2Fwebp%22%5D%2C%22dangerouslyAllowSVG%22%3Afalse%2C%22contentSecurityPolicy%22%3A%22script-src%20'none'%3B%20frame-src%20'none'%3B%20sandbox%3B%22%2C%22contentDispositionType%22%3A%22inline%22%2C%22remotePatterns%22%3A%5B%5D%2C%22unoptimized%22%3Afalse%7D%2C%22devIndicators%22%3A%7B%22buildActivity%22%3Atrue%2C%22buildActivityPosition%22%3A%22bottom-right%22%7D%2C%22onDemandEntries%22%3A%7B%22maxInactiveAge%22%3A15000%2C%22pagesBufferLength%22%3A2%7D%2C%22amp%22%3A%7B%22canonicalBase%22%3A%22%22%7D%2C%22basePath%22%3A%22%22%2C%22sassOptions%22%3A%7B%7D%2C%22trailingSlash%22%3Afalse%2C%22i18n%22%3Anull%2C%22productionBrowserSourceMaps%22%3Afalse%2C%22optimizeFonts%22%3Atrue%2C%22excludeDefaultMomentLocales%22%3Atrue%2C%22serverRuntimeConfig%22%3A%7B%7D%2C%22publicRuntimeConfig%22%3A%7B%7D%2C%22reactStrictMode%22%3Atrue%2C%22httpAgentOptions%22%3A%7B%22keepAlive%22%3Atrue%7D%2C%22outputFileTracing%22%3Atrue%2C%22staticPageGenerationTimeout%22%3A60%2C%22swcMinify%22%3Atrue%2C%22experimental%22%3A%7B%22appDocumentPreloading%22%3Atrue%2C%22clientRouterFilter%22%3Atrue%2C%22clientRouterFilterRedirects%22%3Afals
▲  Error: Command "yarn run build" exited with 1

⚡ The Vercel build (`yarn dlx vercel build`) command failed. For more details see the Vercel logs above.
⚡ If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.

Reproduction
No response
Pages Deployment Method
Pages CI (GitHub/GitLab integration)
Pages Deployment ID
No response
Additional Information
No response
Would you like to help?

[ ] Would you like to help fixing this bug?

Hi @sebinsua I'm sorry you're having issues with your app, I believe that is it not next-on-pages related since as you can see in the logs what fails is the vercel build step
Alongside this message:
⚡ The Vercel build (`yarn dlx vercel build`) command failed. For more details see the Vercel logs above.
⚡ If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.

Something in your application is causing Vercel not to build it properly, next-on-pages only works with the output from Vercel so you do need to address that first before trying to use next-on-pages
Please try simply running manually vercel build that should currently fail, and needs to be fixed first, please let me know if the command doesn't fail
I hope this helps 🙂

Hm, you're right, but I don't really understand why Next.js doesn't support these Node modules. I've tried their serverComponentsExternalPackages config but it has no effect on the problem for me.

Sorry I am not really sure how to help 😢
If you could share your code I could try to have a look, but anyways I think that the steps to take to see if this can be helped would be to try to remove/isolate parts of your application and see if you can figure out what specific package is causing issues, from then you can try running next build and see if that works, if it doesn't then it's a problem with next itself otherwise it's a problem with the vercel cli
once you do the above you can open an issue in either the next or vercel repo and hopefully someone can help or clarify if what you're trying to do is actually not supported

My suggestion is to make it clearer in the README or docs that while Cloudflare workers supports many of the Node.js standard libraries that Next.js disables these when the 'edge' runtime is configured.

Thanks for the suggestion 🙂, I'll try to add something, one thing that concerns me is that we don't want to be too descriptive/involved with Next/Vercel aspects since that is a bit out of scope of what next-on-pages does (which is talking the vercel output and make it Cloudflare compatible), but if adding a small sentence somewhere can avoid confusing people than I think we should totally try to do that.

@sebinsua I've opened a PR for updating the supported doc I hope that improves the situation, if you want please have a look and let me know what you think 🙂

By the way, I noticed in your logs above that you have imports from other unsupported modules such as os and dns, so even if Next.js wasn't blocking things I think the code would still not run on the Cloudflare network 😢


Add Levels.fyi to company pages 💸

Description
To help members more easily access information regarding salary for each company, we want to include a link to the Levels.fyi salary page of each company on their company page.

Acceptance Criteria
Add a levels_fyi field to the companies table in the database. This can be done through a database migration.
Add the following Levels.fyi logo to the images folder:

Then, when loading the frontend for each company page (which is done in the loader function here, check the companies table for a non-null value for levels_fyi (which was added issue # !). If there is no levels_fyi value, do nothing (no Levels.fyi logo should appear on the UI). Otherwise, have the Levels.fyi logo appear underneath the link to the company page.
The logo should be a link to the page https://www.levels.fyi/companies/<levels_fyi_field_value>/salaries. Implement this link with a tooltip, such that when hovering over the logo, the words 'View Salary Information on Levels.fyi' appear (see an example of a tooltip implementation here).

This is my first open source contribution but I'm interested in working on this feature.
Do I need to wait for database PR 'add levels_fyi field to companies database' #330 to go through first? I am not seeing the correct type/interface in the packages/db/dist/db.d.ts file and I'm getting this error when I add the argument 'companies.levels_fyi' to the select property in the getCompany() query function.

You've got it @wflore19!
Yeah, technically #330 needs to be merged and pulled into your local before you'll see a levels_fyi field appear, but in the meantime feel free to ignore this error and just continue with the rest.
Or, if you'd like, you can just manually add the migration in @lianarosa's PR here to your local, run yarn db:migrate, and then that should add the levels.fyi field to your local database.

Sounds good I'll try to get running with what Liana has done. Thanks.


Space in Values

Hi,
I am using Syncronous API, i am trying to set a value which contains space using HMSET. But it is not getting SET as expected since the hiredis library is seperating the parameters using space.
So, the command  HMSET MYKEY MYFIELD "SOME VALUE HERE" works perfectly fine when i execute it in redis cli. But when i use the same command using hiredis, it assigns value 'SOME' to MYFIELD and value 'HERE' to Field 'VALUE'.
Is there a way to achieve this?
Thanks in advance. :)

You can do it like this:
#include <stdio.h>
#include <hiredis/hiredis.h>

int main(int argc, const char **argv) {
    redisContext *c = redisConnect("localhost", 6379);
    redisReply *reply;

    const char *data = "The quick brown fox jumped over the lazy dog";
    reply = redisCommand(c, "HMSET myhash myfield1 %s", data);
    freeReplyObject(reply);

    reply = redisCommand(c, "HMSET myhash myfield2 %s", "Or with a string literal");
    freeReplyObject(reply);
}

oh ok, this works. Thanks.
Actually, i was creating string first and then passing it in redisCommand like this
sprintf(str, "HMSET myhash myfield %s", "String data here");
reply = redisCommand(c, str);

According to documentation at thttps://redis.io/docs/latest/commands/hmset/ one should be able to add multiple fields at once.
My situation has 17 fields for the one hash - how do I overcome this nicely?
My command/usage:
hmset HASH  accept "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.7" accept-encoding "gzip, deflate, br, zstd" accept-language "en-GB,en-US;q=0.9,en;q=0.8" connection "keep-alive" host "<IP_ADDRESS>:8080" purpose "prefetch" redirect-slug "TheTest" sec-ch-ua "Google Chrome;v=125, Chromium;v=125, Not.A/Brand;v=24" sec-ch-ua-mobile "?0" sec-ch-ua-platform "Windows" sec-fetch-dest "document" sec-fetch-mode "navigate" sec-fetch-site "none" sec-fetch-user "?1" sec-purpose "prefetch;prerender" upgrade-insecure-requests "1" user-agent "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"

Is this a question about how to do this in hiredis (the C Redis API)?

I slept on it and have decided to try and replace the space as one would do witha URL '%20'?


Adding missing commands in const.py

Adding missing ZCL commands COMMAND_MOVE_SATURATION, COMMAND_STOP_MOVE_STEP and new ROTATED (used by IKEA), ROTATED_FAST and ROTATED_SLOW.
Shall moving ROTATED from IKEA INIT and importing it instead.
All commands is needed by tuya TS004F quirk https://github.com/zigpy/zha-device-handlers/issues/1322 and some more in the near future (LIDL remote https://github.com/zigpy/zha-device-handlers/issues/613).

Codecov Report

Merging #1411 (ad7667c) into dev (e4e6250) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev    #1411      +/-   ##
==========================================
+ Coverage   80.51%   80.52%   +0.01%
==========================================
  Files         222      222
  Lines        6409     6414       +5
==========================================
+ Hits         5160     5165       +5
  Misses       1249     1249

Impacted Files
Coverage Δ

zhaquirks/const.py
100.00% <100.00%> (ø)

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 e4e6250...ad7667c. Read the comment docs.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 80.527%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
5165

Relevant Lines:
6414

💛  - Coveralls


Updated TypeScript version into 2.4.1

set noStrictGenericChecks typescript compiler option to true due to Generic Error

The fix implied more changes than expected:

[X] Upgraded TypeScript version into 2.4.1
[X] Upgraded TypeScript lib from es5 to es6 due type errors
[X] Added @types/core-js dependency
[X] Modify all imports to pass the tslint
[X] string-literals.ts convertType function, replace type.text by  type.value

[X] Update gruntfile.js to add the compiler options
[X] Change react.d.ts for known FIX link

Finally, the build compiles and run the tests with

61 passing (44s)
52 failing

I need to do a lot of changes and fixes, so I think that I've done something wrong in some stage, could a core developer help me to fix this? Thanks
I leave the pull request at this stage to have a changes track

Any idea when this will get released?

The major changes made are to support TS 2.4 as soon as possible, and then remove the parches to apply the best practices. I'm OK with your decision to first apply the best procedure and then release the new version.
So, I will make a new PR for the tslint issue in the next days. How do you want to procedure with the ts version upgrade?

👍

We're really looking forward to the release of this!

@aleixmorgadas Thanks for doing the whitespace changes in a separate PR. I made some changes to this PR to tighten the generics type definitions and avoid some of the CI timeouts.
@blakeembrey Can you take a quick look and create a release for this? The version number was already bumped.

Hi, I also need this update, when will be merged?

@CosminIonascu In the meantime you can install this pull request by running:
yarn add -D TypeStrong/typedoc#549/head
or
npm install --save-dev TypeStrong/typedoc#549/head

Ok, thank's!

Also @CosminIonascu, you will ned to build the dist folder in order be able to run the node script:
https://github.com/TypeStrong/typedoc/blob/master/UPDATING.md

@blakeembrey I've replaced the lib es2016 by the old once to show you the errors.
So, the build now is broken just to show you what happens. If it's OK, then undo my last changes on tsconfig.json 😁

@blakeembrey I've undone the change in the tsconfig.json file, and it works.
There was a lot of errors at the beginning, so they guided me to that change. View all thread to find the reason.

@aleixmorgadas The changes you made were invalid JSON. I'll try to check it out for myself.

@blakeembrey Yes the commit d3d4d42 had an invalid JSON, but the first errors weren't.

@aleixmorgadas As far as I can see, there's no changes to tsconfig.json in the PR I merged. It looks like you undid the changes making it es2016 and it passed. Let me know if I'm not looking at the right thing.

Oh, I see what you meant now too. I thought you were undoing the change to demonstrate it failing. The order of the conversation confused me, sorry. I saw your TravisCI link first and I thought that was you showing it fails using the es2015 config. Now I understand that you undid the changes all together (not to es2015 as a demo, then back to es2016).


IndexError: list index out of range

I tried this, but failed at the last step, please see the attached screeshot:

Gonna look into this soon!


feat: Update scrollToBottom and scrollToTop methods to allow smooth behaviour

Uses the scrollTo() method instead of directly setting the scrollTop. By default, it will still scroll instantly. When passing smooth = true, it'll set the behaviour to smooth.

Hey @quietdreamr.
Thankyou for your contribution. I am currently quite busy, but before I can merge this I need to test it with other behaviours such as - streaming, media images with eventual loading and other UX aspects.
Apologies for not being able complete this right away as I have just moved countries and don't have much free time.

Hey @quietdreamr. Thankyou for your contribution. I am currently quite busy, but before I can merge this I need to test it with other behaviours such as - streaming, media images with eventual loading and other UX aspects. Apologies for not being able complete this right away as I have just moved countries and don't have much free time.

No problem at all. It is not urgent. All the best with the moving process!

Hey, I just had a look at your code and whilst it is great, there are a few things to note:

Whilst you have made a great start, there is work to be done on actually allowing the devs to toggle whether the scrolling behaviour should be smooth or instant. This will involve the establishment of a toggle property/attribute that is not intrusive to the existing Deep Chat's API and at the same time would pave way for implementing new scroll related features in the future. This takes time to get right, hence needs to be carefully thought out. Additionally, there will ofcourse need to be work to update the Deep Chat's code to facilitate this and the documentation as well.
The smooth scrolling seems to break the stream UX in the FireFox browser as the chat stops scrolling to the bottom. I wonder if anything can be done to fix this.

Given the work mentioned above and outstanding issues that I still need to get through, I will keep the PR open but not merge it until I am comfortable with preparing it for a new release.
(I know that the code does not affect the existing functionality, but because not all of its branches can be activated - I do not want to confuse any other devs that may be using/analysing this project's code).
Thankyou for your great initiative once again!


Backport issue(#1153) and (#1154) to branch opendistro-1.3

opensearch-security pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly

Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)
Backporting

Github Issue # or road-map entry, if available:

Description of changes:

Why these changes are required?

What is the old behavior before changes and new behavior after changes? (Please add any example/logs/screen-shot if available)

Testing done: (Please provide details of testing done: Unit testing, integration testing and manual testing)

Setup Instructions

8.Is it backport from main branch? (If yes, please add backport PR # and commits #)
Yes,

#1153  and commit hash is : ea101e287afb85189837a6b6526f10cb9b99e4c6

#1154  and commit hash is : 5a81a424f4dc0dd1e72df9d8c27710e9dbcdec1b
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1206 (91e6347) into opendistro-1.3 (a99cb8b) will increase coverage by 0.07%.
The diff coverage is 80.95%.

@@                 Coverage Diff                  @@
##             opendistro-1.3    #1206      +/-   ##
====================================================
+ Coverage             62.40%   62.47%   +0.07%
- Complexity             2892     2895       +3
====================================================
  Files                   221      221
  Lines                 16063    16068       +5
  Branches               3015     3014       -1
====================================================
+ Hits                  10024    10039      +15
+ Misses                 4470     4458      -12
- Partials               1569     1571       +2

Impacted Files
Coverage Δ

...ecurity/configuration/ConfigurationRepository.java
75.59% <80.95%> (+6.27%)
:arrow_up:

...ty/configuration/ConfigurationLoaderSecurity7.java
65.00% <0.00%> (+1.00%)
: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 a99cb8b...91e6347. Read the comment docs.


QChat for Visual Studio Professional

Hi,
I would like to have AWS Q-Chat available in Toolkit for VisualStudio 2022 Professional Version.
Thanks and best regards
Marco

Thanks for reaching out @MarcoSchneider-TUI . This is a duplicate of the request in #392 , and will be closed. Please add a +1 reaction to that issue to register your interest in this feature.


Angular version is outdated

The app is currently on versión 6 of the Angular framework which is no longer supported.
https://angular.io/guide/releases

I can help you migrate to latest Angular version to take advantage of bug and security fixes and new improvements to the platform if you are open for merge requests.

Hey, thanks for your interest to help
I think the plan was to migrate from angular to next or nuxt, let me know if you're interested in helping on that part

Hi @bilelmoussaoui
I can help depending on the framework chosen. I'm more familiar with Angular and Vue.
Why do you plan a migration to another framework?
I think updating to latest Angular version will help to reduce bundle size and improve loading speed of the app and the developer experience without needing a migration to another framework.

Because most of the pages don't change much and having the pages server rendered makes more sense in our case.

Angular provides a tool to upgrade the version semi-automatically and, depending on the deprecated components the website might be using, it could take a couple of hours to update to Angular 10.  I also offer you my help if you are interested.

I have submitted a pull request which updates Angular to latest stable version until the app is migrated or server side rendered pages is implemented.


Parser panics on incomplete expression

parse panics on 100 + as an expression instead of returning parser error

This is fixed now


The example doesn't play any sound on Android on macOS

The example doesn't play any sound on Android on macOS
To reproduce

Build the example for iOS. It plays sounds as expected.
Build the example for Android on an M1 macOS.
We would expect it to play some sounds,
but it doesn't.

Screenshot

This package more stable now.


Proposal : "Disconnected run the Pebble Phone app"

Hi,
PebbleJS is really cool and useful when we don't want to learn a new language.
I read the code and I wondered is there is a way to avoid to display the message "Disconnected run the Pebble Phone app".  This message is displayed a lot and C apps don't have this behavior.
Maybe some UI elements can be stored in a buffer, or something like that.
Do you think it's a good idea ?
(I don't have the level to help you to do that, too much abstraction in this code for me )

It's possible that the disconnection detection is too aggressive. I'll see about handling the case where the watch and phone reconnect, but the JS hasn't yet been killed by the phone. Right now, when they disconnect, the watch assumes all state is lost, hence the abrupt message. Maybe it can display a no-bluetooth icon in the status bar briefly, and the fullscreen message only when there is a very high chance the JS side has been killed.
Thanks! I'll report back my findings when I get around to it.

Thanks for the details.
So by the way you will be able to detect and use the Bluetooth connection find / lost, which is very nice!


GCC 48

This adds GCC 4.8 support, all tests pass on CentOS/RHEL 7. Previously discussed in #212.
All tests pass on Travis, even on GCC 4.8!

Coverage remained the same at 100.0% when pulling c5576d77beee13968474c559903fd48ca3f26b88 on henryiii:gcc48 into e184b6ecf26eb13b7e7afef4cef57783c29a32eb on nlohmann:develop.

:+1:

I missed the compiler testing list in the readme, added a line there too. The other version strings may be a bit out of date.
Also, I'm testing with the external GCC 4.8.5 package just like all the other GCC versions, but GCC 4.8.4 is the default compiler on Travis, so for the first time you could have a no extra packages GCC build of JSON on Travis.

You’ll also want to update the text in the little graphic on the main page where there’s a 3.2.1 release.

Thanks so much for the effort!


can't import jfoenix in the eclipse IDE

i trying to use JFXTextField  in eclipse IDE
but i can't to import it to the class

what should i do ?

Right click on your project in the package explorer, select Properties. On the left select "Java Build Path", then select the library tab on the right.  In the library tab, click on "Add external JARS" then navigate to the JFoenix jar file you downloaded and select it.


Rocket league (again)

Rocket league isn't working again! Love the program by the way

Also, the preview option does not work on any of the listed games, not sure if that's an issue on my end?

They should work... send over your latest log? Located in logs folder.

2016_18_12 - Copy.txt
Here you go. Thank you for offering to help!

Okay, after looking over the logs I realised simply re-downloading would fix the preview error, which it did.
I did some research and found that guy here:
https://github.com/d-karl/Rocket-League-Chroma-Control
He basically instructs users to start rocketleague with the -logs flag which opens an eventlog window beneath rl and than manages to read this window for logged events. (I've tested this, there really is plenty of information)
Perhaps that is something you want to look into

It looks like it can detect the current state (main menu, in-game), when you score a goal, when the countdown starts. Which is all nice, I can utilize it with effects. But it would mean that the boost amount, team scores, and current team will no longer work. I'll see if there's more in the log that I can harvest.

If using those logs meant that you would not have to update the pointers, I'm sure people would be willing to accept the compromise?

Well i was referred to this post but actually i already have check this and nothing works.
Still have problems related with Rocket League.
Thanks.

@s3cas sorry if it was not clear: Aurora support for Rocket League is broken at the moment, because it's to time consuming to update the memory pointer for every patch of Rocket League.
@santosch

I did some research and found that guy here:
https://github.com/d-karl/Rocket-League-Chroma-Control
He basically instructs users to start rocketleague with the -logs flag which opens an eventlog window beneath rl and than manages to read this window for logged events. (I've tested this, there really is plenty of information)

He stated at the Razer forum that his software no longer works, because:

In one of the latest patches, Psyonix apparently changed the log level, meaning I can't detect events anymore.

He made no more updates since September.
@santosch Can you still read the logs for team, goal, countdown?

Hi @brainbug89 ,
The question is how can i make some steps with program only works with Razer?
I have try grab some info on Rzer forum like pointers and other stuff but seems with last update all mod's get a strange process.
I really like the mod's for another games but seems I will need to use a normal profile from LGS for Rocket League.
Thanks guys.

@brainbug89 unfortunately, you are right.
While in menu the log is very talkative, but when i join a game there occurs almost nothing.
I only get a ~ "Update player stats" whenever i do something (goal, shot, etc.) and the only real event still logged is an "EpicSave" - but not if you do the save, only if a shot that you did is saved by another player.
Somehow strange, i actually think this should not be there any more as well.
I also experimented a bit with guessing of additional start params (-debug, -log=ALL etc.) to try to change the log level but as expected i was not successful with that.
This is making me really sad :'-(

Duplicate of #185


Ensure repository information is included in published package.json file

As laid out in https://github.com/material-components/material-web/pull/2878, the repository field in package.json is used to by some companies to verify that PRs are made to correct packages from npm.

It sure is!
https://github.com/material-components/material-web/blob/6aa42f3399e9b8433a6920a6e6779d16a0c55cce/package.json#L8-L11


Associate regions with ModelRuns instead of SiteEvaluations

Currently, a SiteEvaluation has a many-to-one relationship with a Region. This means that two SiteEvaluations in a given ModelRun can be associated with two different Regions. In practice, we generally speak about ModelRuns being associated with Regions, not SiteEvaluations; furthermore, in practice we never associated two or more SiteEvaluations in the same ModelRun with more than one Region.
This PR modifies our data model to associate a ModelRun with a Region directly to a) simplify the data model and queries, and b) provide a foundation for work to improve the performance of the model run list endpoint (i.e. this PR doesn't attempt to make any optimizations to that endpoint outside of the implicit speedup that may be gained by the new data model; I'll include that in a follow on PR).
Some notes about this:

To ensure the atomicity of the migration operations, I needed to split the Django migrations into three files. Alternatively we could have set atomic = False and used one, but for data integrity/stability I opted for multiple migrations.
This touches a significant amount of the rdwatch Django app's endpoints. So I took this as an opportunity to improve our testing coverage and did this refactor via TDD. All the tests I added are essentially just integration tests that hit an API endpoint and examine the response.
There is one breaking API change - when creating a model run, the user must now provide a region.
There were a couple endpoints in django/src/rdwatch/views/site_evaluation.py that we don't use anymore (and in fact, were 500'ing for me when I tested them locally...). Since they're unused, I just removed them rather then attempting to fix them and port the new data model changes to them.

Ah, I forgot about the node vector tile server, that needs to be updated too.

@BryonLewis I believe I addressed all of your requested changes. I also wanted to mention, I did a minor refactor of the vector tileserver to use the postgres.js library instead of node-pg https://github.com/ResonantGeoData/RD-WATCH/pull/396/commits/1a8fa2f5acddc7850b126186a61f817d0287aa1d. That library makes it way easier to pass parameters into queries, as you can use a JS template literal with string interpolation instead of passing an array and referencing params by index. This should make updating these queries less of a hassle in the future.


Upgrade react-router-dom to v6

Part of the dependency updates required to migrate to react v18 properly

Initial groundwork done in #2495.
Further work needed in the future:

#2505
hoisting of Academy routes to routerConfig.tsx


fix(plugin-preview): should use correct default previewMode

Summary
Should use correct default previewMode.
isMobile should be removed in Rspress 2.0
Related Issue
closes: #1714

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

can not image how the tests added


feat(robot-server): cal check mock api

overview
This is a mocked up calibration check http api implementation.
These endpoints will be the first to utilize the jsonapi based v2 schema Ian created.  This PR represents the way will define our API going forward.
review requests

Ignore that tests don't pass.

Think deeply not just about the implications for calibration and sessions, but for all future API. Do we like that all responses have this schema:

{
  "meta": {},
  "links": {
     "nextstep": "/someurl/12345/go"
  },
  "data": {
    "id": "id of object",
    "type": "type represented in attributes",
    "attributes": {
      "name": "string",
      "quantity": 0,
      "price": 0,
      .......
    }
  }
}

Best way to review is to run the robot server and view the docs:

run it OT_API_FF_useFastApi=TRUE make dev
go to http://localhost:31950/redoc or http://localhost:31950/docs#/
Look at the Sessions and Calibration Check sections.

risk assessment
None.

I'm liking the direction this is heading. Left my two cents

Think deeply not just about the implications for calibration and sessions, but for all future API. Do we like that all responses have this schema:

{
  "meta": {},
  "links": {
     "nextstep": "/someurl/12345/go"
  },
  "data": {
    "id": "id of object",
    "type": "type represented in attributes",
    "attributes": {
      "name": "string",
      "quantity": 0,
      "price": 0,
      .......
    }
  }
}

I've felt a little iffy on the data and attributes objects in the past; they feel a little bit like unnecessary nesting to me. I could be talked into flattening one or both of them into a response interface that includes meta, links, type, id(if applicable) ,and then whatever arbitrary model fields. We'd have to carefully consider collection responses if we go the flattening route, though (perhaps with atype: 'collection'`).

I can't see the id being at the root level if we support collections. Unless you're thinking we return an object or a collection (?)

I can't see the id being at the root level if we support collections. Unless you're thinking we return an object or a collection (?)

Yeah an id it wouldn't make sense in that context. If we wanted to flatten a little and be consistent with collections, I guess I'm proposing something along the lines of:
{
  // ...
  type: 'collection',
  collection: [
    {
      type: 'item'
      id: 'abc',
      // ...
    },
    // ...
  ]
}

I can't see the id being at the root level if we support collections. Unless you're thinking we return an object or a collection (?)

Yeah an id it wouldn't make sense in that context. If we wanted to flatten a little and be consistent with collections, I guess I'm proposing something along the lines of:
{
  // ...
  type: 'collection',
  collection: [
    {
      type: 'item',
      id: 'abc',
      // ...
    },
    // ...
  ]
}

json api spec has data being a list or object. How do you feel about that? I like explicitness.

This is being closed. These endpoints are now in edge and used to drive calibration check.


Add tooltip sort by value in AreaChart

Description
Added a prop to AreaChart to allow sorting tooltip entries by value, instead of the order of labels in the categories prop.
Sometimes you'll want to use the same color for multiple lines in your chart--in this case, it helps reduce ambiguity when the tooltip displays fields in order of value.
Related issue(s)

What kind of change does this PR introduce? (check at least one)

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New Feature (non-breaking change which adds functionality)
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
How has This been tested?
I tested functionality using storybook. I can add tests if needed.

Screenshots (if appropriate):
Before:

After:

The PR fulfills these requirements:

[x] It's submitted to the main branch
[x] When resolving a specific issue, it's referenced in the related issue section above
[x] My change requires a change to the documentation. (Managed by Tremor Team)
[ ] I have added tests to cover my changes
[ ] Check the "Allow edits from maintainers" option while creating your PR.
[ ] Add refs #XXX or fixes #XXX to the related issue section if your PR refers to or fixes an issue.

We've just rolled out a feature allowing the creation of custom tooltips → v3.9. This eliminates the necessity to address this within Tremor directly. We appreciate you submitting the PR and for being an active member of our community! 🙏


Cannot connect to database - Minimal Compatibility Level of<PHONE_NUMBER>

When I attempt to open tabular editor from my PowerBI model, I receive a message that the "database compatibility level of 1601 is below the minimal compatibility level of<PHONE_NUMBER> needed for [model 'Model]...FormatStringDefinition at PowerBI mode."
A clear and concise description of what happened. Include any error messages or stack traces if possible. Also, feel free to add screenshots or recordings showing the problem.

Application specifics

Tabular Editor 2.16.8214.24954
Semantic Engine used: [e.g. Power BI Desktop, Azure Analysis Services, SSAS 2019, etc.]
Model Compatibility Level: 1601 (I think)

Additional context
The model includes a DirectQuery Connection to a PowerBI dataset in service and a few import tables. I have had a previous, potentially related, issue in this model while working in tabular editor. After working in tabular, I was unable to save the changes to PBI, because it somehow duplicated format string measures were created even though I don't use the format string expressions in this model. Luckily, I had recently saved my work and was able to continue using tabular editor after opening the last saved file.

Try to update to the latest version of Tabular Editor (2.17.3) and let us know if the issue persists.

That did the trick. Thanks, the check for updates button under preferences suggested there were no updates. But I just downloaded and installed the newest version and I am now able to use the editor again. Thanks again!


cosmodevbuild rebuilds always

cosmodevbuild rebuilds the dycore and cosmo even though the source has not changed.

Yes it does, but doesn't it just skips many of the build-steps in cmake, because .o files are already present?
Dycore compilation then only takes a few seconds

This is not a serious issue. Won't fix.


Metacp move should gracefully handle AccessDeniedException on windows

I hit a test failure on Windows in the scalafix CI using metacp https://ci.appveyor.com/project/scalacenter/scalafix/build/215#L1007
[info] scalafix.tests.core.BasePrettyTypeSuite *** ABORTED *** (15 milliseconds)
[info]   java.nio.file.AccessDeniedException: C:\Users\appveyor\AppData\Local\Temp\1\metacp6981278481363537711\jsse-E46B1924A1D00ABDBA3438467208B53E.jar -> C:\Users\appveyor\AppData\Local\semanticdb\cache\3.7.3\jsse-E46B1924A1D00ABDBA3438467208B53E.jar

The cause is likely that the file was being used elsewhere, judging by answers here

http://grokbase.com/t/openjdk/nio-dev/098x6jeh0b/wrong-exception-thrown
https://stackoverflow.com/questions/22988210/java-nio-file-accessdeniedexception-while-using-files-move/22988462
http://www.javaquizplayer.com/blogposts/blogpost3.html

I propose to

catch this exception on windows only,
fallback to a non-atomic move
catch exception if non-atomic move fails, with no fallback.

under the theory that the file already exists. Any Windows people who can recommend a less hacky solution?

The relevant piece of code in metacp is here
https://github.com/scalameta/scalameta/blob/0b41ec6a0cac00eef35fc043a74e6cffda12afdc/semanticdb/metacp/src/main/scala/scala/meta/internal/metacp/Main.scala#L41-L53


WIP: Add web UI for some bloopyboi functionality

Work in Progress

Remaining:

Verify protobuf is working. Use it or type sharing.
Verify http2 works
add basic viewing of config
Make tasks for phase 2

Call phase 1 complete


code hilighting, highlight div bookends

Issue Type: Feature Request
when a div is selected i wand the partner closure end div  , span etc. to be hilighted in some obvious way.
dealing with nesting issues this is a real problem.
VS Code version: Code 1.69.2 (3b889b090b5ad5793f524b5d1d39fda662b96a2a, 2022-07-18T16:12:52.460Z)
OS version: Windows_NT x64 10.0.22621
Restricted Mode: No

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.70.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Could you share a gif or video of the painful behavior you're seeing?
/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette).
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


AM-2911 TEST: with JBS Integration enabled

Jira link (if applicable)
AM-2911 "Judicial Refresh (via ASB or Job) does not include Judicial Bookings when generating organisation Role-Assignments"
Change description
This is to test #1575 but with JBS inclusion in ASB/Job Refreshes turned on in PREVIEW.
Checklist

[x] commit messages are meaningful and follow good commit message guidelines
[x] Does this PR introduce a breaking change - NO

close temporarily to clear down helm.

Closing this TEST PR as the parent one is now merged.


Missing None definition

I'm porting some code from C to Rust, and it is frequently using None to compare against Window or Atom. In the X11/X.h None is defined to be 0 by preprocessor macro. Currently i compare values against 0, but that doesn't seem like a good idea. What is the reason behind None not being in the API ?

Ah ok, thanks. I guess i will stick to the 0.

I think the constant should exist. Name collision is unavoidable, and solved with crate namespacing.
Anyone who wants to annoy all future maintainers of their software with use x11::*; presumably knows what they're doing, and deserves the clear and helpful compiler errors they get.

As @dagit mentioned, I do think having maybe a XNone constant could be helpful.  Possibly to be added to xlib.rs. Does require documentation. Which this library is currently completely missing. As the old old maintainer mentioned, possibly something for v3. Afaik he was planning to go for a similar approach as x11rb does atm


Fix 148 - Custom IMU Orientation

This is an extension of the fix_148 branch made by superjax https://github.com/rosflight/firmware/pull/252. I figured that degrees made more sense in this context, but there wasn't a conversion to radians yet. I also made some organization changes to make it match conventions I saw elsewhere in the code base.

Hey @legoabram!
I just updated this to rebase from the current master.  Can you check and make sure that the rebase didn't change anything?  It looks good from my end, it just needs to be validated on hardware before merging into master.  (both fixedwing and multirotors)

Sounds good to me. I'll double check the rebase tomorrow. However, I don't have any access to a multirotor. Would anyone at the MAGICC lab be available to help me test this on one in the next couple days?

Yeah, I can try to fly it soon.

Thanks!  Sorry this took so long!


mutateFormDataBeforeSave doesn't work on ManageRecords

Package
filament/filament
Package Version
v2.15.24
Laravel Version
v9.26.1
Livewire Version
v2
PHP Version
PHP 8.1
Problem description
mutateFormDataBeforeSave doesn't work on ManageRecords
I created a simple resource
add mutateFormDataBeforeSave  to Pages/ManageResource.php
protected function mutateFormDataBeforeSave(array $data): array
  {
      $data['competed_by'] = $data['completed'] == true ? auth()->id() : null;

      return $data;
  }

it doesn't work
Expected behavior
on save it should use the same Edit and create actions as full resource
Steps to reproduce
1- create a simple filament resource
2- try to ->mutate form data
Reproduction repository
https://github.com/cobraprojects/filament-test
Relevant log output
No response

Hello! Thats because the mutate* functions exist on specific page classes like Edit, not resources classes in general.
In this case, since you just have a List/Manage page, you can use actions to customise this - https://filamentphp.com/docs/2.x/admin/resources/listing-records#customizing-data-before-saving-1


Upload the first non-NDA version of PCS playbook

version approved for online publishing for non-NDA users

will try to submit code review internally


status of QuickGraph?

I think this package is a valuable addition to the .Net ecosystem, but I also believe it could use some love in terms of API user-friendliness, support for .net standard/.net core, release mgmt, 'official' nuget package update, ...
@pelikhan, what is the status of this project? There are some forks out there in the mean time, but I'd prefer having a statement from the original/official creator before jumping on any of those... Do you plan to evolve QuickGraph further in the future? Are you looking for help? Let us know!

It is dormant but I take PRs.

You might be interested in these two forks https://github.com/YaccConstructor/QuickGraph and https://github.com/KeRNeLith/QuikGraph. The last one seems more active and up-to-date.


Edited AppIcon to make it have the modern macOS style

Really small change, but I changed the AppIcon to give it a more Big Sur-like look.
Before:

After:

👍