Adapt Test to handle Exception class changing its parent

in KAFKA-14417 ConcurrentTransactionsException was changed from an ApiException to be a RetriableException (which is itself an ApiException)
Doing if/else logic based on instanceof check so the test can handle the ConcurrentTransactionsException being of either heritage as Jenkins sees the updated class but my local build only sees the old one

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

The actual PR where the ExceptionClass was changed in Dec 6th.
https://github.com/apache/kafka/pull/12915/files#diff-1746d0b93646b9a55a932b23f4052734815876066003ab45cb237b4a0379a309

Need a code owner to merge it.   There are two overlapping issues.

the AK change to ConcurrentTransactionsException
some CVE Scanning issue that causes build failure, which has been addressed in https://github.com/confluentinc/common/pull/496

rest-utils master build can get past the CVE, but fails a test due to ConcurrentTransactionsException
This PR should pass the ConcurrentTransactionsException, but fails the CVE check first.
Even tho this PR branch is up to date with rest-utils master except for this change, the PR builder still is pulling the old CVE logic.
The pressing thing is that rest-utils master has been failing for 20 days due to the ConcurrentTransactionsException change, which is preventing downstream projects from picking up newer upstream Kafka dependencie.


Fix Example demo site.

Currently the example demo site is not working due to the changes that we have been making to the framework.

Resolved with
https://github.com/Amber-Crystal/amber/pull/12
https://github.com/Amber-Crystal/amber/pull/34


As a user, I want to track my performance

Resolved in #186

Performance tracking functional as of #245


Unable to display IMAGE within table rows

Please share more information about what you want.

{         key: "avatar",         text: "Avatar",         width: 70,         sortable: false,         cell: record => {           return (             <img               className="image css-img-object"               src={                 record.avatar                   ? record.avatar                   : "/assets/img/default.png"               }               style={{                 width: "30px",                 height: "30px",                 borderRadius: "50%",                 marginRight: "10px"               }}             />           );         }       },
This is how I render images in the table

What is the error you got while using the above code?

Can you please provide detail?

I'm closing this issue now.
if anyone will face this issue again they can reopen it.


Fix  version for autoscaler and metrics-server

Description of changes:
Update  autoscaler and metrics-server version to 1.31 for dev bundles.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherry-pick main


i wanna just only show custom emoji

what should i do ?

+1 on this.
i have tried changing the js file in the vendor but it doesn't work anyway,but i have heard that the js file in public/extensions/the-turk-flamoji/dist needs to be changed, but I don't know where to change it,does anyone know?

+1

+1

Put this in you css customization:

.emoji-picker__container:nth-of-type(2),
.emoji-picker__container:nth-of-type(3),
.emoji-picker__container:nth-of-type(4),
.emoji-picker__container:nth-of-type(5),
.emoji-picker__container:nth-of-type(6),
.emoji-picker__container:nth-of-type(7),
.emoji-picker__container:nth-of-type(8),
.emoji-picker__container:nth-of-type(9),
.emoji-picker__container:nth-of-type(10){
  display: none;
}

.emoji-picker__category-name:nth-of-type(2),
.emoji-picker__category-name:nth-of-type(3),
.emoji-picker__category-name:nth-of-type(4),
.emoji-picker__category-name:nth-of-type(5),
.emoji-picker__category-name:nth-of-type(6),
.emoji-picker__category-name:nth-of-type(7),
.emoji-picker__category-name:nth-of-type(8),
.emoji-picker__category-name:nth-of-type(9),
.emoji-picker__category-name:nth-of-type(10)
{
  display:none;
}


More plugins - what do you want/need?

Ideas for further plugins, open a new issue or share ideas here :)

[ ] something that generates a graph right away without other manual steps

Diff plugin, that would allow us to create series of CSV/JSON files and display performance change over the time.

Thanks for your input @hauleth !
With "display change over time" what do you mean? Do you mean just some console output ranking the outputs by which is fastest, do you want a graph.. ?

Let's imagine that you creating libraty and you want to compare speed of different versions. It would be great to have some way to display graph of changes in the same functionality over time.
I am trying to write something like rails/rails-perftest for Phoenix/Plug and it would be great to have possibility to graph performance changes over the time.

It's a nice idea and I know other people wanna work on similar things. It's definitely possible. My only caveat is that to be accurate they'd need to be done on the same system, with the same load and same dependencies and approximately the same data in the DB etc.
Might be more accurate to check out different revisions and hen benchmark them in a go on the system... that'd also need some serialization and graphing from there so the work for a benchee plugin is the same :tada:
Thanks for telling me the use case, it makes developing something to aid your cause much easier. Although, no promises to a when :)

Rust's criterion-rs will automatically show you the diff between current and last run, making it easy  to check if code changes provide performance improvements.
Maybe I'm missing something, but with benchee if I wanted to compare two runs I'd either have to jot the previous result down, or write some custom code to store and compare. Or is there a better way already?

I have written a little bit of code to compare benchmarks between branches. For now, it is just a dirty alpha version.
  defmodule GitLoadSave do
    @file_name "benchee.run"

    def config(branch \\ "master") do
      case load(branch) do
        nil -> [save: save()]
        load -> [load: load, save: save()]
      end
    end

    defp load(branch \\ "master") do
      case branch == branch() do
        true ->
          nil

        false ->
          System.tmp_dir!()
          |> Path.join(app())
          |> Path.join(branch)
          |> Path.join(@file_name)
      end
    end

    defp save do
      tag = branch()

      path =
        System.tmp_dir!()
        |> Path.join(app())
        |> Path.join(tag)
        |> Path.join(@file_name)

      [path: path, tag: tag]
    end

    defp app, do: to_string(Mix.Project.config()[:app])

    defp branch,
      do:
        "git"
        |> System.cmd(["rev-parse", "--abbrev-ref", "HEAD"])
        |> trim()

    defp trim({str, 0}), do: String.trim(str)
  end

This can be added to the benchee config [formatters: ...] ++ GitLoadSave.config(). After that, you can run the benchmarks in the master and after that in a different branch with a comparison to the master.

@yuhama there is the Saving & Loading - you can save the previous results, tag them, and load them back into your benchmarking suite where they will be part of the comparison. We don't show explicit differences beyond that - I'd be happy to get input on how to do that/what to do. Criterion is on my radar though and getting all their statistical stuff in is something I want to do, but might need to brush up my statistics for :)
@NickNeck thanks for sharing!


Tuuli Edit230318

ISic278-284, Latin inscriptions from Taormina, encoded

All good and merged. I haven't deleted the branch, since I'm not sure if you're still working in it at present. You might want to start a new branch?


PC-976: Init

@tomecko - all fixed in https://github.com/samwise-tech/components/pull/10/commits/9906de458ed6c266c5a9e273d117f56bb6784633


[BUG] Empy Embed Message

Describe the bug
This is a bug with empty embed message.
If u setup color value and then remove them.
U get bug with empty embed message.
To Reproduce
Steps to reproduce the behavior:

Go to control panel
Then choose any rss and setup Embed message

Setup color value
Then save.
Remove color value
wait when u get rss message.
get this shit:

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Branch (please specify one):
master
Additional context
I can't fully remove color option of embed message.
So ... I can't fully remove embed message?

Thanks for the report. I saw that you were referring to the public bot - I've fixed the issue on there now.
For the record, you can edit or remove embeds through Discord commands


[DNM] Add windowing capability at sidecar

Works with https://github.com/projectriff/go-function-invoker/pull/10

I tested the three Java samples, all LGTM with the latest changes

Merged as 8efed627f7c2b68e325f8ecb885585f5ba38bfd1


Error handling message: player_queues/play_media: Resource not found

What version of Music Assistant has the issue?
2.4.0b4
What version of the Home Assistant Integration have you got installed?
2024.11.2
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
I get the error "Error handling message: player_queues/play_media: Resource not found" in the log when playing some tracks. For example track 4 of a specific album. Note that the track plays when using directly Jellyfin or VLC.
How to reproduce
Play a specific track
Music Providers
Jellyfin
Player Providers
Any (same error happens when using chromecast or DLNA)
Full log output
music-assistant.log
Additional information
No response
What version of Home Assistant Core are your running
2024.11.1
What type of installation are you running?
Home Assistant Supervised
On what type of hardware are you running?
Linux

Please supply the automation or script you are using which causes this.

The jellyfin error in that log could indicate the user lacks the download permission (We stream the download url).
If the user definitely has that permission then there is something else going on that means the jellyfin api isn't returning enough information to construct a url. That's not something I've seen happen before, so I'm currently more leaning towards a permission issue.

@sunjaxx based on the above please look into whether there is a permissions problem here


Updated Readme to reflect the change of default triplet.

Still need some justification for this change

Justification provided.

Still need some justification for this change

Justification provided.

What do you suggest us do in this PR? Are you suggesting that we should drop the support for dynamic library dependencies? Is so, I think this is a big decision that neither you nor I can make, we should engage @vinjiang or C++ working group.

Still need some justification for this change

Justification provided.

What do you suggest us do in this PR? Are you suggesting that we should drop the support for dynamic library dependencies? Is so, I think this is a big decision that neither you nor I can make, we should engage @vinjiang or C++ working group.

No, not at all. I suggest that what we wrote in Readme should at least work with the default setting, that is all. Customers shouldn't come back to us and tell us that they followed the Readme only to find there is some 'package not found' error.

Still need some justification for this change

Justification provided.

What do you suggest us do in this PR? Are you suggesting that we should drop the support for dynamic library dependencies? Is so, I think this is a big decision that neither you nor I can make, we should engage @vinjiang or C++ working group.

No, not at all. I suggest that what we wrote in Readme should at least work with the default setting, that is all. Customers shouldn't come back to us and tell us that they followed the Readme only to find there is some 'package not found' error.

Then how are we going to follow up on that issue caused by dynamic library? Do you have any issue tracking that?

Still need some justification for this change

Justification provided.

What do you suggest us do in this PR? Are you suggesting that we should drop the support for dynamic library dependencies? Is so, I think this is a big decision that neither you nor I can make, we should engage @vinjiang or C++ working group.

No, not at all. I suggest that what we wrote in Readme should at least work with the default setting, that is all. Customers shouldn't come back to us and tell us that they followed the Readme only to find there is some 'package not found' error.

Then how are we going to follow up on that issue caused by dynamic library? Do you have any issue tracking that?

Is this change breaking dynamic library? If not, why are we considering this?

Still need some justification for this change

Justification provided.

What do you suggest us do in this PR? Are you suggesting that we should drop the support for dynamic library dependencies? Is so, I think this is a big decision that neither you nor I can make, we should engage @vinjiang or C++ working group.

No, not at all. I suggest that what we wrote in Readme should at least work with the default setting, that is all. Customers shouldn't come back to us and tell us that they followed the Readme only to find there is some 'package not found' error.

Then how are we going to follow up on that issue caused by dynamic library? Do you have any issue tracking that?

Is this change breaking dynamic library? If not, why are we considering this?

 I don't feel this is right.

The default triplet on Windows is x86-windows. I think it's okay for us to use x64-windows since x64 has become mainstream nowdays. But is there any reason we should use -static?
This is the root cause of the problem, we are using -static in CMakeSettings.json.

The default triplet on Windows is x86-windows. I think it's okay for us to use x64-windows since x64 has become mainstream nowdays. But is there any reason we should use -static?
This is the root cause of the problem, we are using -static in CMakeSettings.json.
Why not create a PR and change that?

I don't have a strong opinion against static or dynamic library by default, as long as both are supported. That's why I don't consider changing to use dynamic library by default an improvement. Please do drive this default setting to be changed if you think the change is necessary and beneficial for our customers.
However, I do have concern over a not working by default readme, that motivated this change.

The default triplet on Windows is x86-windows. I think it's okay for us to use x64-windows since x64 has become mainstream nowdays. But is there any reason we should use -static?
This is the root cause of the problem, we are using -static in CMakeSettings.json.
Why not create a PR and change that?

I don't have a strong opinion against static or dynamic library by default, as long as both are supported. That's why I don't consider changing to use dynamic library by default an improvement. Please do drive this default setting to be changed if you think the change is necessary and beneficial for our customers.
However, I do have concern over a not working by default readme, that motivated this change.

What if we consider the fact that in CMakeSettings.json there's also x86-windows-static triplet, which doesn't exist at all (ref: https://github.com/microsoft/vcpkg/tree/master/triplets)?

It's in community triplets. I'm not saying we should support community triplets, just a fun fact.
Let discuss it in this afternoon's meeting to finalize our plan.
PS E:\dev\src\cpp\vcpkg> vcpkg install curl:x86-windows-static libxml2:x86-windows-static
Computing installation plan...
The following packages will be built and installed:
    curl[core,non-http,ssl,sspi,winssl]:x86-windows-static
  * libiconv[core]:x86-windows-static
  * liblzma[core]:x86-windows-static
    libxml2[core]:x86-windows-static
  * zlib[core]:x86-windows-static
Additional packages (*) will be modified to complete this operation.
Starting package 1/5: zlib:x86-windows-static
Building package zlib[core]:x86-windows-static...
-- Using community triplet x86-windows-static. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: E:\dev\src\cpp\vcpkg\triplets\community\x86-windows-static.cmake
-- Using cached E:/dev/src/cpp/vcpkg/downloads/zlib1211.tar.gz
-- Using source at E:/dev/src/cpp/vcpkg/buildtrees/zlib/src/1.2.11-deec42f53b
-- Configuring x86-windows-static
-- Building x86-windows-static-dbg
-- Building x86-windows-static-rel
-- Installing: E:/dev/src/cpp/vcpkg/packages/zlib_x86-windows-static/share/zlib/copyright
-- Performing post-build validation
-- Performing post-build validation done
Building package zlib[core]:x86-windows-static... done
Installing package zlib[core]:x86-windows-static...
Installing package zlib[core]:x86-windows-static... done
Elapsed time for package zlib:x86-windows-static: 11.57 s
Starting package 2/5: curl:x86-windows-static
Building package curl[core,non-http,ssl,sspi,winssl]:x86-windows-static...
-- Using community triplet x86-windows-static. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: E:\dev\src\cpp\vcpkg\triplets\community\x86-windows-static.cmake
-- Using cached E:/dev/src/cpp/vcpkg/downloads/curl-curl-curl-7_68_0.tar.gz
-- Using source at E:/dev/src/cpp/vcpkg/buildtrees/curl/src/url-7_68_0-cd669cc759
-- Configuring x86-windows-static
-- Building x86-windows-static-dbg
-- Building x86-windows-static-rel
-- Installing: E:/dev/src/cpp/vcpkg/packages/curl_x86-windows-static/share/curl/vcpkg-cmake-wrapper.cmake
-- Installing: E:/dev/src/cpp/vcpkg/packages/curl_x86-windows-static/share/curl/copyright
-- Performing post-build validation
-- Performing post-build validation done
Building package curl[core,non-http,ssl,sspi,winssl]:x86-windows-static... done
Installing package curl[core,non-http,ssl,sspi,winssl]:x86-windows-static...
Installing package curl[core,non-http,ssl,sspi,winssl]:x86-windows-static... done
Elapsed time for package curl:x86-windows-static: 1.52 min
Starting package 3/5: libiconv:x86-windows-static
Building package libiconv[core]:x86-windows-static...
-- Using community triplet x86-windows-static. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: E:\dev\src\cpp\vcpkg\triplets\community\x86-windows-static.cmake
-- Using cached E:/dev/src/cpp/vcpkg/downloads/libiconv-1.16.tar.gz
-- Using source at E:/dev/src/cpp/vcpkg/buildtrees/libiconv/src/1.16-de9101a181
-- Configuring x86-windows-static
-- Building x86-windows-static-dbg
-- Building x86-windows-static-rel
-- Installing: E:/dev/src/cpp/vcpkg/packages/libiconv_x86-windows-static/share/libiconv/copyright
-- Performing post-build validation
-- Performing post-build validation done
Building package libiconv[core]:x86-windows-static... done
Installing package libiconv[core]:x86-windows-static...
Installing package libiconv[core]:x86-windows-static... done
Elapsed time for package libiconv:x86-windows-static: 5.848 s
Starting package 4/5: liblzma:x86-windows-static
Building package liblzma[core]:x86-windows-static...
-- Using community triplet x86-windows-static. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: E:\dev\src\cpp\vcpkg\triplets\community\x86-windows-static.cmake
-- Using cached E:/dev/src/cpp/vcpkg/downloads/xz-mirror-xz-v5.2.4.tar.gz
-- Using source at E:/dev/src/cpp/vcpkg/buildtrees/liblzma/src/v5.2.4-66bfe33102
-- Configuring x86-windows-static
-- Building x86-windows-static-dbg
-- Building x86-windows-static-rel
-- Installing: E:/dev/src/cpp/vcpkg/packages/liblzma_x86-windows-static/share/liblzma/copyright
-- Performing post-build validation
-- Performing post-build validation done
Building package liblzma[core]:x86-windows-static... done
Installing package liblzma[core]:x86-windows-static...
Installing package liblzma[core]:x86-windows-static... done
Elapsed time for package liblzma:x86-windows-static: 17.28 s
Starting package 5/5: libxml2:x86-windows-static
Building package libxml2[core]:x86-windows-static...
-- Using community triplet x86-windows-static. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: E:\dev\src\cpp\vcpkg\triplets\community\x86-windows-static.cmake
-- Using cached E:/dev/src/cpp/vcpkg/downloads/GNOME-libxml2-v2.9.9.tar.gz
-- Using source at E:/dev/src/cpp/vcpkg/buildtrees/libxml2/src/v2.9.9-d5fcf4dfb8
-- Configuring x86-windows-static
-- Building x86-windows-static-dbg
-- Building x86-windows-static-rel
-- Performing post-build validation
-- Performing post-build validation done
Building package libxml2[core]:x86-windows-static... done
Installing package libxml2[core]:x86-windows-static...
Installing package libxml2[core]:x86-windows-static... done
Elapsed time for package libxml2:x86-windows-static: 15.99 s

Total elapsed time: 2.369 min

The package curl:x86-windows-static provides CMake targets:

    find_package(CURL CONFIG REQUIRED)
    target_link_libraries(main PRIVATE CURL::libcurl)

The package libxml2 is compatible with built-in CMake targets:

    find_package(LibXml2 REQUIRED)
    target_include_directories(main PRIVATE ${LIBXML2_INCLUDE_DIR})
    target_link_libraries(main PRIVATE ${LIBXML2_LIBRARIES})


[FEATURE] Custom angles for polarArea graph

Expected Behavior
Provide custom value for each angle of the polar graph.
Current Behavior
Every angle is 360/#values °
Possible Solution
Provide the custom angles in the options like this
 var options = {
 		type: 'polarArea',
 		data: {
 		labels: ["A", "B", "C", "D", "E"],
 		datasets: [{}]
 		},
 		options: {
 			customAngles: [
 				10, 40, 80, 80, 150
 			]
 		}
 	}

 	var ctx = document.getElementById('chartJSContainer').getContext('2d');
 	new Chart(ctx, options);

and use it in
Chart.controllers.polarArea = Chart.DatasetController.extend({...
updateElement: function(arc, index, reset)

This should be closed with https://github.com/chartjs/Chart.js/pull/4753.

Possible in v3.0.0-beta.3 https://jsfiddle.net/rbgoeskx/
Will send a PR updating this to use degrees instead of radians


Refactor the configuration system

The alternative approach proposed here leverages function decorators to supply a user's choice of default values for the many parameters of the main entry points to DataMapPlot. While a bit more complicated than the former approach, this one avoids the awkward playing with the locals() dictionary, and ensures that strictly positional parameters to configuration-completed functions can never be set through the configuration file.

I like the decorator approach; it's much cleaner to use (just harder to get working properly initially, but you've done that hard work already).


Add admonitions, dynamic admonitions titles, admonitions colors

Added admonitions as standard with GFM, with the added capability of changing the token or changing the title directly in markdown for zero-config.
Color for each type of admonition is fixed for light/dark theme, the light theme has a paler version of the color.
> [!TIP]
> You showld use Fuwari!

> [!IMPORTANT]
> You showld use Fuwari!

> [!NOTE]
> You showld use Fuwari!

> [!CAUTION]
> You showld use Fuwari!

> [!WARNING]
> You showld use Fuwari!

> [!NOTE / My custom note]
> You showld use Fuwari!

> [!NOTE/]
> You can hide the title!

> [!NOTE / Mi nota] === [!NOTE/Mi nota] === [!NOTE /Mi nota] === [!NOTE/ Mi nota]
> Whitespaces are accounted for and trimmed

https://github.com/saicaca/fuwari/assets/65259076/58babe7b-648c-4de9-97c4-e5e0e0eaee82
TODO: Color could be dynamic and skewed to the current --hue value:
  :root {
    --hue: 210;
    --admonitions-color-skew: 0.1; /* The amount to skew the original color */
  }
  /* Let say that our base color for the !TIP label is: hsl(87deg 65% 54%) */
  .tip .admonitions{
        /* hsl( calc(base-hue + (target-hue - base-hue) * skew-amount), base-saturation, base-lightness) */
    color: hsl(calc(87 + (var(--hue) - 87) * var(--skew-amount)), 65%, 54%);
        /* This new color  will be dynamically skewed towards the theme hue */
  }

I dont know if dynamic calc() expressions are allowed in stylus, or if you want just static colors.

This is really good and I need it exactly.

Hey, I originally intended to have icons, but for example some of the unicode ones that you use do not show in edge/SI. I will look at adding md/fa icons as a ::before element. I think at the end using emoji or other unicode icons in the markdown itself will be the default. Still, I will look at the ::before solution

@JoeyC-Dev Can you test the new commit? Now works just like GH, its a :before pseudo with a webkit mask to apply the color, pure css

@Fabrizz I haven't tried it on my blog, but it does not like fit: the icon gets stripped.

Yeah, the mask-size was not correct, now it works

Verified working:

Tested on Chrome, Edge, Firefox, duckduckgo (mobile, based on edge) and all looks okay.
But need to warn user to clean the cache (specially for owners who use CDN), or it will look like this:

I eager for this feature for a long time. Really appreciate your work!

Ahhh, PR closed.


show-names - Suppot new commit view

Part of #7808
Test URLs
https://github.com/refined-github/sandbox/commit/54c10fe670779eab43b6a18b7fb06e51dd7050af#r148774860
Screenshot

Actually it doesn't show current username here, but for testing I let it shows here.

You can add labels to PRs now 🙌


Complete the transaction on StarCoin (with signature)

Complete the transaction on StarCoin (with signature)
TASK's

[ ] Send a transaction
[ ] Obtain transaction info

🙋🏻♀

Money: 500 xUSDT

https://stcscan.io/main/transactions/detail/0x28b027fb572d518c7273e9cb2caee570a2b3edb1e9f70e4662d20a6cfe9f30d1

Dependencies excluded from the package (only Hex packages can be dependencies): bcs

BCS Should be published to hex first so this SDK can be publish

Dependencies excluded from the package (only Hex packages can be dependencies): bcs

BCS Should be published to hex first so this SDK can be publish

updated


Behavior Alfresco

Good afternoon, I had referred you to several articles on alfresco I have read. I am writing because I need to develop a behavior on the creation of a node of a custom type. This node has an association with other nodes. I developed the first part of behavior javascript onNodeUpdate under the policy, but it turns out I get the modified properties but can not access the array association because it is null. Please if you can direct me to finish the job. Thank you. Best regards
Note: my email is<EMAIL_ADDRESS>

Questions on how to do something in Alfresco should be posted in the Alfresco Forums.


TypeError: Cannot read property 'constant' of undefined

(node:77743) UnhandledPromiseRejectionWarning: TypeError: .../.....2d2e7a10.js: Cannot read property 'constant' of undefined
    at PluginPass.FunctionExpression|FunctionDeclaration (.../node_modules/babel-preset-modernize/dist/plugins/transform-iife-arrows/index.js:1:424)
    at newFn (.../node_modules/@babel/traverse/lib/visitors.js:175:21)
    at NodePath._call (.../node_modules/@babel/traverse/lib/path/context.js:55:20)
    at NodePath.call (.../node_modules/@babel/traverse/lib/path/context.js:42:17)
    at NodePath.visit (.../node_modules/@babel/traverse/lib/path/context.js:92:31)
    at TraversalContext.visitQueue (.../node_modules/@babel/traverse/lib/context.js:115:16)
    at TraversalContext.visitSingle (.../node_modules/@babel/traverse/lib/context.js:84:19)
    at TraversalContext.visit (.../node_modules/@babel/traverse/lib/context.js:143:19)
    at Function.traverse.node (.../node_modules/@babel/traverse/lib/index.js:82:17)
    at traverse (.../node_modules/@babel/traverse/lib/index.js:64:12)

Caused by this line

Ah interesting, it should just be skipping things without a binding. Thanks for the error report!

I ran into this error, and then made a simple patch to check !binding, but then ran into this next (not sure if related or should open a new ticket):
HookWebpackError: /Users/n8/dish/dish-app/static/js/app.9bb14696b5da5188a1a3.js: Cannot read property 'arguments' of undefined
    at makeWebpackError (/Users/n8/dish/node_modules/webpack/lib/HookWebpackError.js:49:9)
    at /Users/n8/dish/node_modules/webpack/lib/Compilation.js:2107:11
    at eval (eval at create (/Users/n8/dish/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:66:1)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
-- inner error --
TypeError: /Users/n8/dish/dish-app/static/js/app.9bb14696b5da5188a1a3.js: Cannot read property 'arguments' of undefined
    at NodePath._getKey (/Users/n8/dish/node_modules/@babel/traverse/lib/path/family.js:194:25)
    at NodePath.get (/Users/n8/dish/node_modules/@babel/traverse/lib/path/family.js:186:17)
    at NodePath._getPattern (/Users/n8/dish/node_modules/@babel/traverse/lib/path/family.js:226:21)
    at NodePath.get (/Users/n8/dish/node_modules/@babel/traverse/lib/path/family.js:188:17)
    at visitParam (/Users/n8/dish/node_modules/babel-preset-modernize/dist/plugins/transform-destructuring/index.js:1:5836)
    at Array.forEach (<anonymous>)
    at PluginPass.Function (/Users/n8/dish/node_modules/babel-preset-modernize/dist/plugins/transform-destructuring/index.js:1:7244)
    at newFn (/Users/n8/dish/node_modules/@babel/traverse/lib/visitors.js:175:21)
    at NodePath._call (/Users/n8/dish/node_modules/@babel/traverse/lib/path/context.js:55:20)
    at NodePath.call (/Users/n8/dish/node_modules/@babel/traverse/lib/path/context.js:42:17)
caused by plugins in Compilation.hooks.processAssets
TypeError: /Users/n8/dish/dish-app/static/js/app.9bb14696b5da5188a1a3.js: Cannot read property 'arguments' of undefined
    at NodePath._getKey (/Users/n8/dish/node_modules/@babel/traverse/lib/path/family.js:194:25)
    at NodePath.get (/Users/n8/dish/node_modules/@babel/traverse/lib/path/family.js:186:17)
    at NodePath._getPattern (/Users/n8/dish/node_modules/@babel/traverse/lib/path/family.js:226:21)
    at NodePath.get (/Users/n8/dish/node_modules/@babel/traverse/lib/path/family.js:188:17)
    at visitParam (/Users/n8/dish/node_modules/babel-preset-modernize/dist/plugins/transform-destructuring/index.js:1:5836)
    at Array.forEach (<anonymous>)
    at PluginPass.Function (/Users/n8/dish/node_modules/babel-preset-modernize/dist/plugins/transform-destructuring/index.js:1:7244)
    at newFn (/Users/n8/dish/node_modules/@babel/traverse/lib/visitors.js:175:21)
    at NodePath._call (/Users/n8/dish/node_modules/@babel/traverse/lib/path/context.js:55:20)
    at NodePath.call (/Users/n8/dish/node_modules/@babel/traverse/lib/path/context.js:42:17)

I have the same problem here, do you a solution for that?

I have the same problem here, do you a solution for that?

I believe this may be fixed in HEAD, if anyone wants to re-check. I haven't done the release yet.


Merge pull request #1 from zwave-js/master

fix: respect ignore location setting in hass entities (#234)

Accidebt

Accidebt

Pull Request Test Coverage Report for Build 486551568

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 23.677%

Totals

Change from base Build 484827662:
0.0%

Covered Lines:
1957

Relevant Lines:
8443

💛  - Coveralls

Pull Request Test Coverage Report for Build 486551568

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 23.677%

Totals

Change from base Build 484827662:
0.0%

Covered Lines:
1957

Relevant Lines:
8443

💛  - Coveralls


Testcase Syntax

Going to suggest for testcases (since this works in Rust MeTTa) we adopt a standard test writing format
; it is non-deterministic: each value is matched against all cases
!(assertEqual
 (case (+ 1 (superpose (1 2 3)))
  ((3 OK-3)
   (4 OK-4)))
 (superpose (OK-3 OK-4)))

; one case can produce multiple results
!(assertEqual
  (case (+ 1 (superpose (1 2 3)))
     (($x (+ 1 $x))))
  (superpose (3 4 5)))

Most tests seem to be described with the addition of these two functions
assertEqualToResult
assertEqual
(isa red color)
(isa green color)
(isa blue color)
!(assertEqualToResult
  (match &self (isa $color color) $color)
  (red green blue))

The tests in MeTTamorph directly run both MeTTa and MeTTamorph on the same test files each and check whether the output matches, this is the reason why such assertions are unnecessary. Producing the same output is the implicit assertion which is reported when it fails.

Yes, I agree that comparing results from compiled and not compiled versions is a good approach for this project, but it may turn out to be the case that something in addition is needed. Some MeTTa code cannot be supported by the compiler and running compiled functions from such the code should also be checked. Thus, I suppose that more tests will be added, which will not be completely compiled. It will still be possible to compare partly-compiled and not compiled versions, but writing such tests may appear not too convenient. Let's try and see how it goes.

Why i was suggesting it is that most all tests in  hyperon-experimental https://github.com/trueagi-io/hyperon-experimental/tree/main/python/tests/scripts  use assertEqualToResult assertEqual  and didn't see wanting to have to edit those tests files just for metta-morph :)

If we'd like to run all the unit tests from the main repo with the use of compilation by metta-morph, this would make perfect sense. Well, it also makes sense to be able to run these tests manually to check the results under metta-morph. Thus, I agree that it makes sense to introduce asserts for this sake, although it doesn't imply that unit tests in metta-morph itself should necessarily use them.

Good point, we can add these assert functions at least.


Google Webstore - missing popup.js

I just installed this extension from the store
https://chrome.google.com/webstore/detail/no-coin/gojamcfopckidlocpkbelmpjcgmbgjcl
But it doesn't include the popup.js.

Thanks for reporting this, I will look into this right now.

This was an issue with the build step. I published an update to the Chrome Web Store which should be available in the next hour and also submitted it on the Mozilla Add-On Store which should take about 24 hours to be available (if the submission is successful).
Could you please check if you have the update in an hour and confirm this is fixed? Thanks!

Passed 24 hours and reviewed by myself, this seems fixed. Please reopen an issue if there are any more problems. Cheers!


Class as parameter?

Can we do something like
class Serializable {
   public toString() {}
}
class Test extends Serializable {
    public key:string
}

test(Test);
function test(klass: Class<? extends Serializable>) {
    var obj = new klass();
    obj.toString()
}

You might want something like
function tests<T extends Serializable>(constructorFn: new () => T) {
    var obj = new constructorFn()
    obj.toString()
}

Where the type new () => T means that you can call a value of that type and get a T out of it.

But it also allows to pass anything to it (like some class did not extend from serializable) .

That's because your implementation of Serializable just requires toString(): string, which every type has by default anyway. That means every constructor function is structurally compatible with Serializable. If the method's name was something else, or you added an extra property on Serializable (like __serializable: any), then you'd get some safety here.

It does not seem work with generics.


Update AutoRest C# version

Update AutoRest C# version

Can one of the admins verify this patch?

Does this need to get in for GAs next week, or can it wait? I'm concerned at the size/breadth of this change, and that tests are failing when today is supposed to be code-complete.

The plan is to wait until after GA.

@pakrym could you provide a description of what the change involves?

@pakrym could you provide a description of what the change involves?

Breaking every library in the repo, apparently 😄
On a more serious note, this change makes it so every collection property is always initialized and is not settable in most cases which follows our guidelines closer than the current version is (collections are null and settable).

this change makes it so every collection property is always initialized and is not settable in most cases

Interesting. I thought you already did that a week or two ago in time for Search to take advantage of that. What is different this time around?

Interesting. I thought you already did that a week or two ago in time for Search to take advantage of that. What is different this time around?

That change only affected calling ToArray vs ToList for required collection to allow later mutation. This one is way more it basically removes the need for Initialize = true, EmptyAsUndefined = true all over the place (also removes these properties all together)

Closing, this would be done in stages.


Make Stdlib's ArrayObject a soft dependency of ValueGenerator

Alternative to  #22.
Note: PropertyReflection require stdlib PriorityQueue due the EventManager use.

I suggest removing stdlib from the suggest section now, as it is used only if your own code passes a stdlib ArrayObject to the ValueGenerator, which means it is used by your own code already.

Note: PropertyReflection require stdlib PriorityQueue due the EventManager use.

@Maks3w PropertyReflection itself does not use the PriorityQueue. If the EventManager needs it internally, it is the job of the EventManager to declare it IMO

The event manager no longer uses it on the develop branch.
On Nov 16, 2015 9:15 AM, "Christophe Coevoet"<EMAIL_ADDRESS>wrote:

@Maks3w https://github.com/Maks3w PropertyReflection itself does not
use the PriorityQueue. If the EventManager needs it internally, it is the
job of the EventManager to declare it IMO
—
Reply to this email directly or view it on GitHub
https://github.com/zendframework/zend-code/pull/23#issuecomment-157063371
.

TBH zend-eventmanager shouldn't be a required dependency. It's only used by the annotation sub component.

Ready for merge.
I've tagged this as BC Break because there is a minor change which affect to getConstants signature.

@weierophinney Typehint removed


tests: add "NeomakeSh on (emulated) Windows"

Ref: https://github.com/neomake/neomake/pull/1490

Should be covered already by the test above.


Update build.ts

Here is a beginning solution to address an issue with build.
When working with plugins, the configuration is shared for both front and back, and only created once.
I tried with this one for example : https://www.npmjs.com/package/rollup-plugin-visualizer
The issue with the previous plugin, is that the output file stats.html is created once for client, then erased when the server build.
There is actually no way to make a difference between the two builds :

Returns :

Maybe adding an option to differentiate builds could help to load different plugins for client and server and also help with this kind of plugins.

Thanks a lot for this @DavidBabel. I was planning of something similar, I'll review at the first opportunity.

Note that is more a suggest / approach / issue than a real PR.
I did it to add context to the issue.

0.6 has been released, there is no more rakkas.config, it's all Vite config now (which solves this).


bug: Invalid environment variables

Provide environment information
System Info:
System:
OS: macOS 12.5
CPU: (8) arm64 Apple M1
Memory: 129.66 MB / 8.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 14.20.0 - ~/.nvm/versions/node/v14.20.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v14.20.0/bin/yarn
npm: 6.14.17 - ~/.nvm/versions/node/v14.20.0/bin/npm

  "ct3aMetadata": {
    "initVersion": "6.4.0"
  }

Describe the bug
Environment variable handling seems to be spotty at times. I initially got the error invalid environment variables while attempting to navigate to my custom (next-auth) catch-all route /auth/signin. The route is used to render the appropriate login form based on the type of auth the user wants to use (credentials, oauth, or email), this is done by grabbing that directly from the route: auth/signin/credentails or auth/signin/email, etc...
In any case when I navigate to these routes, the environment variables are not populated/accessible. I created a thread on Theo's discord to see if anyone had any ideas. Although nothing seems to be working for me.
https://discord.com/channels/966627436387266600/1031586269588881429/1031586269588881429
Oddly this was working in an older project which was spun up using:
  "ct3aMetadata": {
    "initVersion": "5.12.0"
  }

Here is the file in question where the issue first presented: src/pages/auth/[...index].tsx
import {
  AuthTabLink,
  CredentialsAuthForm,
  MagicAuthForm,
  OAuthButton,
  UserRegistrationForm,
} from '@/components';
import {
  Container,
  Divider,
  HStack,
  useColorMode,
  VStack,
} from '@chakra-ui/react';
import { PageLayout } from 'chakra.ui';
import { GetServerSideProps } from 'next';
import { getCsrfToken, getProviders, getSession } from 'next-auth/react';
import { useRouter } from 'next/router';
import { useEffect, useState } from 'react';

interface AuthPageProps {
  providers: {
    [key: string]: {
      callbackUrl: string;
      id: string;
      name: string;
      signinUrl: string;
      type: string;
    };
  } | null;
  isAuth: boolean;
  csrfToken?: string | undefined;
}
type SignView = 'magic' | 'credentials' | 'oauth' | 'register';
const AuthPage: React.FC<AuthPageProps> = ({
  providers,
  csrfToken,
  isAuth,
}): JSX.Element => {
  const router = useRouter();
  const { colorMode } = useColorMode();
  const [signInView, setSignInView] = useState<SignView>('magic');

  const { asPath } = router;

  // routing booleans
  const isRegister = signInView === 'register';
  const isMagicAuth = signInView === 'magic';
  const isCredentialAuth = signInView === 'credentials';
  const isOAuth = signInView === 'oauth';
  const isSigninRoute = isMagicAuth || isCredentialAuth || isOAuth;

  // style
  const shadow = colorMode === 'light' ? 'sm' : 'md-dark';

  return (
    <PageLayout title={asPath} type="default">
      <Container w="100%" h="100%" mt="64">
        <VStack
          maxW="md"
          w="full"
          px={8}
          pb={8}
          boxShadow={shadow}
          rounded="md"
          gap={3}
        >
          <HStack as="ul" justify="space-between" w="full" pt={12} pb={4}>
            <AuthTabLink to="magic" providerName="Passwordless" />
            <AuthTabLink to="credentials" providerName="Email" />
            <AuthTabLink to="oauth" providerName="OAuth" />
          </HStack>
          <Divider
            position="relative"
            color="transparent"
            shadow={colorMode === 'light' ? 'md' : 'dark-md'}
          />
          {!isSigninRoute && isRegister && !isAuth && <UserRegistrationForm />}
          {isSigninRoute && !isAuth && (
            <>
              {isMagicAuth && (
                <MagicAuthForm
                  csrfToken={csrfToken || ''}
                  providerId={providers?.email?.id}
                />
              )}
              {isCredentialAuth && <CredentialsAuthForm />}
              {isOAuth && (
                <VStack>
                  {providers &&
                    Object.values(providers)?.map((provider) => {
                      if (
                        provider?.id !== 'credentials' &&
                        provider?.id !== 'email'
                      ) {
                        return (
                          <OAuthButton key={provider?.id} provider={provider} />
                        );
                      }
                    })}
                </VStack>
              )}
            </>
          )}
        </VStack>
      </Container>
    </PageLayout>
  );
};

export default AuthPage;

export const getServerSideProps: GetServerSideProps<AuthPageProps> = async (
  context
) => {
  const { req } = context;
  const session = await getSession({ req });

  if (session) {
    return {
      redirect: { destination: '/?success=You are already signed in.' },
      props: {
        providers: null,
        csrfToken: undefined,
        isAuth: false,
      },
    };
  }

  return {
    props: {
      providers: await getProviders(),
      csrfToken: await getCsrfToken(),
      isAuth: !!session,
    },
  };
};

To reproduce
I've created a repo, that can be used to reproduce the issue: https://github.com/gaurangrshah/env-test or use gitpod:
https://gitpod.io/#https://github.com/gaurangrshah/env-test.git
Clone the repo locally:
git clone https://github.com/gaurangrshah/env-test

use yarn or npm to install deps:
yarn

npm install

Then add the required environment variables:
# Prisma
DATABASE_URL=file:./db.sqlite

# Next Auth
NEXTAUTH_SECRET=
NEXTAUTH_URL=http://localhost:3000

# Next Auth Spotify Provider - dev
SPOTIFY_CLIENT_ID=
SPOTIFY_CLIENT_SECRET=

Then you should be able to spin up the development server:
yarn dev

npm run dev

Finally navigate to: http://localhost:3000/auth/signin
And you should see the error message: invalid environment variables

Additional information
NOTE: if I remove the custom signin page redirect from the [...nextauth].ts file, the native signin methods, pages, etc still work. For some reason the issue seems to be localized to the custom signin page only as of now.
NOTE: in the repo i created to demo this issue for some reason teh NEXTAUTH_SECRET variable never makes it into the env.

What was the fix?

Hey @nexxeln, it's more of a workaround than a fix, I noticed that commenting out all of the imported auth forms made the page render and bypass the render, so I began last night to localize the definition all of the required auth form components.
So initially I was trying to handle the rendering of all the providers and their associated forms more imperatively, where as now I've simply decided to go the declarative route given that it was my imports that were causing th error in the first place.
This is the current state of the login pages: src/pages/auth/[...index].tsx
import {
  Box,
  Button,
  chakra,
  Container,
  Divider,
  HStack,
  IconButton,
  Input,
  InputGroup,
  InputRightElement,
  useColorMode,
  VStack,
} from '@chakra-ui/react';
import { PageLayout } from 'chakra.ui';

import { signIn, useSession } from 'next-auth/react';
import { useRouter } from 'next/router';
import { useEffect, useState } from 'react';
import { onPromise, trpc } from '@/utils';
import { CustomIcon } from 'chakra.ui/icons';
import { parseFormData } from '../../utils/forms';

type SignView = 'magic' | 'oauth' | 'register';
const AuthPage: React.FC = (): JSX.Element => {
  const router = useRouter();
  const { colorMode } = useColorMode();
  const [signInView, setSignInView] = useState<SignView>('magic');
  const { data: session } = useSession();
  const isAuth = !!session?.user;
  const { asPath } = router;

  // routing booleans
  const isRegister = signInView === 'register';
  const isMagicAuth = signInView === 'magic';
  // const isCredentialAuth = signInView === 'credentials';
  const isOAuth = signInView === 'oauth';
  const isSigninRoute = isMagicAuth || isOAuth;
  const { data } = trpc.auth.formUtils.useQuery();

  useEffect(() => {
    const view = asPath.split('/')[3] || 'magic';
    setSignInView(view as SignView);
  }, [asPath]);

  // style
  const shadow = colorMode === 'light' ? 'sm' : 'md-dark';

  useEffect(() => {
    if (isAuth) void router.push('/');
  }, [isAuth, router]);

  return (
    <PageLayout title={asPath} type="default">
      <Container w="100%" h="100%" mt="64">
        <VStack
          maxW="md"
          w="full"
          px={8}
          pb={8}
          boxShadow={shadow}
          rounded="md"
          gap={3}
        >
          <HStack as="ul" justify="space-between" w="full" pt={12} pb={4}>
            {/* <AuthTabLink to="magic" providerName="Passwordless" /> */}
            {/* <AuthTabLink to="credentials" providerName="Email" /> */}
            {/* <AuthTabLink to="oauth" providerName="OAuth" /> */}
          </HStack>
          <Divider
            position="relative"
            color="transparent"
            shadow={colorMode === 'light' ? 'md' : 'dark-md'}
          />
          {/* {!isSigninRoute && isRegister && !isAuth && <UserRegistrationForm />} */}
          {isSigninRoute && !isAuth && (
            <>
              {isMagicAuth && (
                <>
                  <VStack w="full" color="white">
                    <chakra.form
                      onSubmit={onPromise(async (e) => {
                        e.preventDefault();
                        const form = e.currentTarget;
                        const inputs = [...form.querySelectorAll('input')].map(
                          parseFormData
                        );
                        await signIn('email', {
                          callbackUrl:
                            '/auth/verify-request?success=Please check your email.',
                          ...inputs,
                        });
                      })}
                    >
                      <input
                        name="csrfToken"
                        type="hidden"
                        defaultValue={data?.csrfToken}
                        disabled
                      />
                      <InputGroup>
                        <Input
                          name="email"
                          type="text"
<EMAIL_ADDRESS>                          w="full"
                        />
                        <InputRightElement>
                          <IconButton
                            aria-label="submit"
                            type="submit"
                            size="sm"
                            icon={
                              <CustomIcon
                                icon="plane"
                                size="1.5rem"
                                color="brand.700"
                              />
                            }
                          />
                        </InputRightElement>
                      </InputGroup>
                    </chakra.form>
                  </VStack>
                </>
              )}
              {isOAuth && (
                <VStack alignItems="flex-end" gap={4}>
                  {data?.providers &&
                    Object.values(data?.providers)?.map((provider) => {
                      if (
                        provider?.id !== 'credentials' &&
                        provider?.id !== 'email'
                      ) {
                        return (
                          <Box key={provider.id}>
                            {/* <OAuthButton key={provider?.id} provider={provider} /> */}
                            <Button
                              w="full"
                              size="lg"
                              variant="outline"
                              onClick={() => void signIn(provider?.id)}
                            >
                              OAuth
                            </Button>
                          </Box>
                        );
                      }
                    })}
                </VStack>
              )}
            </>
          )}
          {/* <RegisterLink /> */}
        </VStack>
      </Container>
    </PageLayout>
  );
};

export default AuthPage;

// export const getServerSideProps: GetServerSideProps<AuthPageProps> = async (
//   context
// ) => {
//   const { req } = context;
//   const session = await getSession({ req });

//   if (session) {
//     return {
//       redirect: { destination: '/?success=You are already signed in.' },
//       props: {
//         providers: null,
//         csrfToken: undefined,
//         isAuth: false,
//       },
//     };
//   }

//   return {
//     props: {
//       providers: await getProviders(),
//       csrfToken: await getCsrfToken(),
//       isAuth: !!session,
//     },
//   };
// };

So it seems I've tracked down the issue, this wasn't an actual bug, it was part of the old codebase when migrating from create-t3-app v5 to 6.
To be specific, i was wrapping the next-auth's signIn method in various places to use for different authentication providers, for example this is the one for credentials authenticaiton:
export async function credentialsLogin({
  email,
  password,
}: AuthenticateUserInput): Promise<SignInResponse | undefined> {
  return await signIn('credentials', {
    callbackUrls: '/?success="Welcome!"',
    redirect: true,
    email,
    password,
  });
}

https://github.com/gaurangrshah/env-test/blob/25c0b224433ddefbe46cd2c944ddd47369b2639f/src/lib/next-auth/fns.ts#L9
I assume this caused my client to call the server in some unexpected way, which didn't sit well. That is what triggered the error on my end. Oddly enough this caused all my named exports from my components/auth folder to throw the error, because they were being imported using absolute paths as shown below:
import {
  AuthTabLink,
  CredentialsAuthForm,
  MagicAuthForm,
  OAuthButton,
  UserRegistrationForm,
} from '@/components';

I noticed that if I imported each component individually the errors went away.
import {  AuthTabLink } from '@/components/auth/auth-tab-link';
import {  CredentialsAuthForm } from '@/components/auth/credentials-auth-form';
//...


Allow filtering by group in entries endpoint of API

This would speed up some scripts significantly. When I want to fetch new entries in a category, I have to ask for entries in each feed - hunderds of requests. This way I could do it in one request.

See PR #794


HTTPS Health probes with custom certificates

When health probes are sent over HTTPS, does the backend need to respond with a certificate signed by a public CA?
What about self-signed certificates or certificates signed by a private CA?
Application Gateway v2 allows you to upload root trusted certificates for backend, but Front Door doesn't seem to.

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

ID: f35a0b39-ab2f-ba8a-0907-e0f3a6b69135
Version Independent ID: 0e6c8267-a911-9c6b-0522-3ec96753b3ef
Content: Azure Front Door Service - backend health monitoring
Content Source: articles/frontdoor/front-door-health-probes.md
Service: frontdoor
GitHub Login: @sharad4u
Microsoft Alias: sharadag

@xenalite , Thank you for posting here. We will investigate and get back to you.

@xenalite , Please find the answers inline:

When health probes are sent over HTTPS, does the backend need to respond with a certificate signed by a public CA?
Yes, AFD will expect a signed certificate.
What about self-signed certificates or certificates signed by a private CA?
Should be fine with a private CA, however self-signed certs are not allowed.
Application Gateway v2 allows you to upload root trusted certificates for backend, but Front Door doesn't seem to have it.
One of the requirements for Front Door health probes is that the hostname you provide for the backend to AFD config, should match the subject name on the certificate.

Let me know if you have any further questions.

@xenalite , Do you have any update on this issue?

@msrini-MSFT Hello. Thank you for the update.
I have a back-end certificate signed by an internal CA, so the chain is not fully known to Front Door.
HTTPS health probes are not healthy in this case.
The certificate Subject Alternative Names match the host name.

@xenalite , AFD expects a signed CA. If you use internal CA, it will not work.
If you have any further questions, let me know.


Where to find the HTML theme file in non-NixOS?

The README says:

After rebuilding, the full theme can be previewed at file:///etc/stylix/palette.html in a web browser.

On non-NixOS systems, the file can't be added to /etc/. Where is it?

Seems like it is in ~~/.config/stylix~. Do you want a PR improving the README?

Yeah, file:///home/«user»/.config/stylix/palette.html is the Home Manager equivalent. (Technically $XDG_CONFIG_HOME could be different, but it is almost always .config.)
Please go ahead with a PR :+1:


Supporting more than just arrays

So, the issue I'm facing is that I want to use ramda everywhere in my project, but I am frequently dealing with other kinds of data structures (for example, facebook's immutable data structures). Currently I'm just wrapping up immutable's methods in curryN's to get similar behavior, but it really would be nice to translate the increasing amount of work in this library in other places (for example, immutable does have map, but it doesn't have some of the other funcs, and these just need to be re-written (often times copy-pasting with minimal changes)). I was wondering whether consideration had been given to generalizing these functions, perhaps against JS's iterator spec ( https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/The_Iterator_protocol )?
However, this only covers half the equation because it doesn't really define what the result type should be unfortunately. Perhaps (at least internally), iteration methods could be defined in terms of two base functions: next and push, which would form an iterable-instantiable tuple: [next, push]. For example, say we defined map as so:
function map(f, iterable)
{
    next = iterable[0],
    push = iterable[1];
    result = push();
    while ([value, next, done] = next())
    {
        if (done)
            return result;

        result = push(result, f(value));
   }
}

So, for arrays it would be something like this:
function arrayToIterable(anArray)
{
    return [ arrayNext(anArray, 0) concat]
}

function arrayNext(anArray, anIndex)
{
    function ()
    {
        return [anArray[anIndex], anIndex < anArray.length - 1, next(anArray, anIndex + 1)];
    }
}

function arrayPush(lhs, value)
{
    if ( arguments.length === 0)
       return [];

   lhs.push(rhs);

   return lhs;
}

So now map(f, arrayToIterable([1,2,3])) works fine. To make it even more painless for the array common case:
function toIterable(anObject)
{
    if (anObject.next && anObject.concat)
        return anObject;

    if (Array.isArray(anObject))
        return arrayToIterable(anObject);

    if (anObject.toIterable)
        return anObject.toIterable();

    return objectToIterable(anObject);
}

function map(f, iterable)
{
    iterable = toIterable(iterable); // no op for existing iterables...
}

Now map(f, [1,2,3]) works again. And if we fill in the missing objectToIterable:
function objectToIterable(anObject)
{
    return [ objectNext, objectPush];

}

function objectNext(anObject, keys, index)
{
    return [[anObject[keys[index]], keys[index]], index < keys.length - 1, objectNext(anObject, keys, index + 1)];
}

function objectPush(anObject, keyvalue)
{
    if (arguments.length === 0)
        return { };

    anObject[keyvalue[1]] = keyvalue[0];

    return anObject;
}

Now all of a sudden map works for objects right out of the gate:
map(function(keyvalue) { return [keyvalue[0], toUpperCase(keyvalue[1])]; }, { "hEllo" : 5, "bye": 0 });

And it gives me the ability to take Facebook's immutability library and add this:
List.prototype.toIterable = function()
{
   return [ ListNext(aList, 0), function(aList, aValue) { return aList.push(aValue); } ]
}

function ListNext(aList, anIndex)
{
    if (arguments.length === 0)
        return new List();

    return [aList.get(anIndex), anIndex < aList.size - 1, ListNext(aList, anIndex + 1) ];
}

And now I can use all of Ramda's funcs with facebook's work. Also interesting, is that I can actually get translate functions for free, by just doing this:
iterable = myList.toIterable();
iterable.push = arrayPush;
toArray = R.map(R.identitity, iterable);
array = toArray(myList);

@buzzdecafe

We already dispatch to any object that implements map

I had no idea!  Could this be generalised for all Ramda iterating functions?  This is the main reason I still have lodash in most projects.  I use objects much more than arrays, but find Ramda gives preferential treatment to arrays.
I really like this feature.

@JAForbes yeah, we should make a bigger deal about that feature. At present we dispatch on most of the Fantasy-Land "methods", and a few more for lazylist integration. I'm working with @kevinbeaty on implementing list iterators as transducers which may make what you are after easier

Iterating linked lists vs array is about 50x faster in most browsers (Made this point somewhere else already, cant remember where)
http://jsperf.com/usage-of-linked-list-vs-array/17
This would be something i would love to have, also for copying immutable large lists, the linked list would be much more efficient allowing shared memory items as in Clojure.

While there might be some good information there, that perf test is significantly flawed.
The linked list and array implementations have different behavior.  It's pretty useless to compare them.  Also, really, what's the point of comparing single-element iterations?  Why bother?
I'm also not a fan of comparing multiple different things in a single JSPerf test, but that's secondary.
It seems likely that a linked list like this might have pretty good iteration performance, but this test fails to demonstrate it.

Although this has some interesting ideas in it, and the work @buzzdecafe and @kevinbeaty have been doing on transducer integration is related, I don't think this issue involves any further action for now.  Closing without prejudice.


Not setting WickedPdf.config[:exe_path]

When deploying to Heroku the gem is not setting the binary exe path, and I can't use wkhtmltopdf in production. Currently I only added the gem in the Gemfile and bundled before deploying. Is there any other steps necessary in order to make it work in heroku?

hello, do you have a wicked_pdf config file in your initializers?  If so, please make sure it's not configuring exe_path.
there shouldn't be any extra steps.
but if you are using Bundler.require to load gems in your app, could you try to place this gem after wicked pdf in your Gemfile?

Still no success, here follows my initializers/wicked_pdf and Gemfile:
initializers/wicked_pdf:
WickedPdf.config = {
    :layout      => "print",
    :disposition => "inline",
    :margin      => { top: 25, bottom: 15, left: 7, right: 7 },
    :dpi         => "300",
    :header      => { spacing: 20, html: {template: 'layouts/print/header'} },
    :footer      => { spacing: 5, html: {template: 'layouts/print/footer'} }
}

Gemfile:
require 'rubygems'

source 'http://rubygems.org'
ruby "2.2.2"

...
gem 'wicked_pdf', '~> 0.11.0'
...

group :development, :test do
  gem 'wkhtmltopdf-binary-edge', '~> <IP_ADDRESS>'
  ...
end

group :production, :staging do
  gem 'wkhtmltopdf-heroku'
  gem 'rails_12factor'
  gem 'rails_serve_static_assets'
end

I wonder if it is because the config is being overwritten.
could you try this in your initializer?
WickedPdf.config = (WickedPdf.config || {}).merge({
    :layout      => "print",
    :disposition => "inline",
    :margin      => { top: 25, bottom: 15, left: 7, right: 7 },
    :dpi         => "300",
    :header      => { spacing: 20, html: {template: 'layouts/print/header'} },
    :footer      => { spacing: 5, html: {template: 'layouts/print/footer'} }
})

i will try to make an empty app to reproduce this issue

also, are you running the app under Heroku cedar-14?

@pallymore it is working now, it appears that the configs were being overwritten somewhere then. Thanks for the help!

cool :)


Telemetry exporter has error in logs, traces still being captured for a route in skip_paths

Environment info:

KrakenD version: 2.6.0
Additional environment information: rke2 v1.27.11 (k8s)

---- 1 ----
We have our observability config as follows:
"telemetry/opentelemetry": {
    "exporters": {
        "prometheus": [
            {
                "name": "gateway_prometheus",
                "port": 5092,
                "process_metrics": false,
                "go_metrics": false
            }
        ],
        "otlp": [
            {
                "name": "gateway_trace",
                "host": "jaeger.domain",
                "port": 4317,
                "use_http": false
            }
        ]
    },
    "layers": {
        "global": {
            "disable_metrics": false,
            "disable_traces": false,
            "disable_propagation": false
        },
        "proxy": {
            "disable_metrics": false,
            "disable_traces": false
        },
        "backend": {
            "metrics": {
                "disable_stage": false,
                "round_trip": true,
                "read_payload": true,
                "detailed_connection": true,
                "static_attributes": [
                    {
                        "key": "my_metric_attr",
                        "value": "my_middle_metric"
                    }
                ]
            },
            "traces": {
                "disable_stage": false,
                "round_trip": true,
                "read_payload": true,
                "detailed_connection": true,
                "static_attributes": [
                    {
                        "key": "my_metric_attr",
                        "value": "my_middle_metric"
                    }
                ]
            }
        }
    },
    "skip_paths": [
        "/"
    ]
}

Metrics and traces seem to be collected but I see this in the logs every 30 seconds (scrape interval):
ERROR [SERVICE OpenTelemetry] failed to upload metrics: rpc error: code = Unimplemented desc = unknown service opentelemetry.proto.collector.metrics.v1.MetricsService

---- 2 ----
We use "/" as our health path and have added that to skip_paths. However, I can still see traces being collected for that path.
---- 3 ----
We have our circuit breaker config as follows:
"qos/circuit-breaker": {
    "interval": 60,
    "timeout": 10,
    "max_errors": 10,
    "name": "krakend-circuitbreaker",
    "log_status_change": true
}

However, we can't seem to see any logs when the circuit status changes. Not sure if the circuit breaker is actually working?
Are the above behaviours expected?
Thanks.

Hi @samstride,
This is a buy 1 get 2 free offer! :joy:
I will focus on the non-otel question, and my colleagues will jump in for the other 2.
To make sure that the circuit breaker is working, first of all, check --lint the configuration to make sure it is in the right place and with the right attributes. If it is OK, my thinking is that the values are hard to get. The "max_errors": 10 means the same backend must see 10 consecutive errors. One error after another. This is a pretty high value, and if a single request works while trying to count to the consecutive 10, nothing will happen.

@alombarte ,
krakend check -c krakend.json --lint
Parsing configuration file: krakend.json
Syntax OK!

So linter is passing.
The way we tested the circuit breaker:

have backend running
start load generation... let it run for some time
take down backend... we see errors showing up in load gen tool as expected... the load generator is definitely sending more than 10 requests/sec and the backend is down for more than 2 mins...
looking at krakend logs since log_status_change = true, it is unclear if the circuit breaker did anything...

When the server starts, you should see a log line like this:
KRAKEND DEBUG: [BACKEND: /something][CB] Creating the circuit breaker named 'krakend-circuitbreaker'

Could you verify this? If the log is not there (make sure your logging level is set to ' DEBUG`), the CB it has not been loaded in the backend section. If the line is there, then the problem is probably in what is tested vs what is declared in the configuration.

@alombarte , thanks, have set log level to DEBUG, can see the log
DEBUG [BACKEND: ....][CB] Creating the circuit breaker named 'krakend-circuitbreaker'

Can't see any logs when state changes.
Pasting sample config here for reference:
{
    "endpoint": "/something",
    "method": "POST",
    "output_encoding": "no-op",
    "extra_config": {
        "qos/ratelimit/router": {
            "max_rate": 500,
            "capacity": 500,
            "client_max_rate": 50,
            "client_capacity": 50,
            "every": "1s",
            "strategy": "ip"
        }
    },
    "backend": [
        {
            "encoding": "no-op",
            "host": [
                "something:5050"
            ],
            "url_pattern": "/",
            "extra_config": {
                "qos/circuit-breaker": {
                    "interval": 60,
                    "timeout": 10,
                    "max_errors": 3,
                    "name": "krakend-circuitbreaker",
                    "log_status_change": true
                },
                "qos/ratelimit/proxy": {
                    "max_rate": 500,
                    "capacity": 500
                }
            }
        }
    ]
}

If you see the initialization line, then the CB is watching problems. I've copied and pasted your CB section into a configuration, and it works as expected:
krakend_1  | [00] 2024/05/21 07:10:38 KRAKEND INFO: [SERVICE: Gin] Listening on port: 8080
krakend_1  | [00] [GIN] 2024/05/21 - 07:10:40 | 500 |    1.695672ms |    <IP_ADDRESS> | GET      "/test"
krakend_1  | [00] [GIN] 2024/05/21 - 07:10:41 | 500 |    1.566328ms |    <IP_ADDRESS> | GET      "/test"
krakend_1  | [00] [GIN] 2024/05/21 - 07:10:42 | 500 |    1.144562ms |    <IP_ADDRESS> | GET      "/test"
krakend_1  | [00] 2024/05/21 07:10:42 KRAKEND WARNING: [CB] Circuit breaker named 'krakend-circuitbreaker' went from 'closed' to 'open'
krakend_1  | [00] [GIN] 2024/05/21 - 07:10:42 | 500 |    1.262023ms |    <IP_ADDRESS> | GET      "/test"
krakend_1  | [00] 2024/05/21 07:10:42 KRAKEND ERROR: [ENDPOINT: /test] circuit breaker is open
krakend_1  | [00] Error #01: circuit breaker is open
krakend_1  | [00] 2024/05/21 07:10:42 KRAKEND ERROR: [ENDPOINT: /test] circuit breaker is open
krakend_1  | [00] Error #01: circuit breaker is open
krakend_1  | [00] 2024/05/21 07:10:45 KRAKEND ERROR: [ENDPOINT: /test] circuit breaker is open
krakend_1  | [00] [GIN] 2024/05/21 - 07:10:45 | 500 |      78.108µs |    <IP_ADDRESS> | GET      "/test"
krakend_1  | [00] Error #01: circuit breaker is open
krakend_1  | [00] 2024/05/21 07:11:32 KRAKEND WARNING: [CB] Circuit breaker named 'krakend-circuitbreaker' went from 'open' to 'half-open'
krakend_1  | [00] 2024/05/21 07:11:32 KRAKEND WARNING: [CB] Circuit breaker named 'krakend-circuitbreaker' went from 'half-open' to 'open'
krakend_1  | [00] [GIN] 2024/05/21 - 07:11:32 | 500 |    1.485633ms |    <IP_ADDRESS> | GET      "/test"
krakend_1  | [00] 2024/05/21 07:11:34 KRAKEND ERROR: [ENDPOINT: /test] circuit breaker is open
krakend_1  | [00] [GIN] 2024/05/21 - 07:11:34 | 500 |      81.804µs |    <IP_ADDRESS> | GET      "/test"
krakend_1  | [00] Error #01: circuit breaker is open
krakend_1  | [00] 2024/05/21 07:11:34 KRAKEND ERROR: [ENDPOINT: /test] circuit breaker is open

Please open an issue in the Circuit breaker repository if you have a reproducible example. And let's leave this issue for the OTEL part.

Closing this issues since these have been fixed in v2.6.3. Traces are no longer collected for routes specified  in skip_paths.
For any one else who has this issue, just make sure you are on a recent version and have set disable_metrics: true to disable pushing of metrics to your backend.
"otlp": [
{
"disable_metrics": true,
"name": "gateway_trace",
"host": "jaeger.domain",
"port": 4317,
"use_http": false
}
]


:+1: the issues that are important to you!

Figuring out which issues are the most important is hard for an open source project.
The best way to measure this is by tracking the :+1: on a issue. So please leave one on the issues you care about!
How to get a speedy fix on your issue

:100: Do it yourself, we motivate and welcome contributions!

If you add a test/test-plan that fails without your change and works afterwards, then your PR will probably be merged quickly!
We like to help people learn Rust, so don't worry about your programming skills.

:star_struck: Have a proper reproduction of the issue with a minimal example.

Include the pixi.toml and pixi.lock when you can. Simplify the file to the least amount of lines where the issue comes up.
Include the commands you ran in the terminal.
Include a pixi info so we know what type of system you are running on.

:question: Ask the right questions, no question is wrong but there are badly formulated questions.

Add your specific use-case, e.g. you're in HPC, you're building a library, you're working on a slow internet machine, etc.
Tell us what you tried.
Add your workaround if you found any.

:people_hugging: Get others involved

Share your issue in our Discord or socials to drag attention to it.

Most upvoted issues: https://github.com/prefix-dev/pixi/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc


Try different "project" displaying using the thirdweb framework.

Different projects is meaning different galleries, so the easier to create the project individually, the faster and more convenient will be for the customers.


grafana alerting does not work with new metric-tank

the alerting queries sent to metric-tank respond with
minDataPoints/maxDataPoints cannot be honored with the series requested

I generally dont like the idea of a minDataPoints variable and i think the best option is to just get rid of it.
The alignRequests() function is far to complex.  We need to strip it down considerably. We will also need to extend the logic to use the retention of each aggregation once https://github.com/raintank/raintank-metric/issues/82 is implemented.  eg if you request a 2month period then raw is not an option as its retention is only 1month.
I should have a PR ready with a slimmed down approach on monday.

OK PR submitted.  There is still more work to be done to clean out the ramSpan argument being passed in to alignRequests()
The new logic is much simpler and more then 100x faster.
Though the existing logic had some nice features, like preferencing in-memory data over fetching from Cassandra, the complexity was just way to high to lead to any benefit.  Additionally, the performance bottleneck of this application is going to be CPU.  Calling out to Cassandra to get aggregated data is going to yield far superior performance to performing runtime consolidation of large spans of data in memory.

@Dieterbe any objections to me merging PR #93

This was merged.

for the record, i like that we got rid of the mindatapoints stuff. we were forcing ourself into extra complications for no good reason.


unrecognized

Commonly used in Markdown, though.

Thanks for your feedback! First, as you might know, there are two exiting ways for obtaining hard line breaks in Markdown syntax without depending on HTML-like constructs:

two trailing spaces at the end of a line = the standard Markdown but "invisible" way
A trailing backslash at the end of a line = corresponding to Pandoc's escaped_line_breaks extension, which I recently added to lunamark and therefore is now supported too here.

In terms of the underlying SILE construct, they are (currently) translated in a \cr. So there is actually a way to achieve the intended presentation - See also https://github.com/sile-typesetter/sile/issues/416 where I mentioned that.
However, you are right: more generally we might eventually consider adding support for some of the HTML constructs commonly used in Markdown and therefore likely to be found in user content... As far as I need them too for book production,
 also possibly comes to mind: while strictly non-HTML Markdown has horizontal rules, these cannot be styled. Real books do not use a long full-rule line, though, but rather various kinds of dinkus / pendants / ornaments....
This being said, it's a complex topic: The lunamark reader has to support HTML (which I think it may perhaps already do, but I did not check and try yet), but then SILE also needs to support parsing and rendering a (decent subset of HTML) too... For now, there's still a lot to do to ensure regular (Pandoc-extended) Markdown is well supported so that this package set can be worth a "1.0", so personally I am afraid I am unlikely to have a look at HTML soon.

Also, #7 might be a prerequisite before starting any work on this -- It's typically something we might want opt-in / opt-out.

Noted. I've started on it.

For the record, relates to Pandoc's raw_html (enabled by default in Pandoc, but it can be disabled). Lunamark doesn't condition it via an extension option (as it is the default in Markdown)

@ctrlcctrlv Thanks for the attempt at PR #18 - It was challenging and made me try and think about it. I created #29 with my findings - In brief here, while using htmlparser was indeed an interesting option (and thanks too for having brought it to my attention), it wouldn't work well... Because Pandoc and Lunamark don't exactly do what I would have naively thought.
So back on topic, let's indeed refocus on the initial scope of the issue. I edited the issue title: If we go for
, we could as well support <wbr/> (from HTML5), which provides breakpoints where to line-break if needed. This could be a nice typographical addition (e.g. translating into a penalty in SILE). Both wouldn't need an HTML parsing library, just some clever string checks. Wanna try? Or I can do it, if you want/prefer (?). I kept that topic in the "milestone 1.1", which has no due date yet, but ideally within a few weeks (more or less).

Wanna try? Or I can do it, if you want/prefer (?). I kept that topic in the "milestone 1.1", which has no due date yet, but ideally within a few weeks (more or less).

I'm on it finally. Found another small bug I'll want fixed on pandocast, so I'll do that on the same occasion, and ensure both conversion route work.


deprecate the GraphQL playground

Already deprecate the GraphQL playground as we plan to make it inaccessible.

I may have misunderstood, do we not plan to remove access to it? Or should I instead change the text to not warn of a coming deprecation?

We do something here but don't know what so pushing to CHRON-350.


Convert Stokes I model to same reference frequency as polarization

Its rather awkward to have outputs at two different reference frequencies: one for the Stokes I model and one for everything else.
I had implemented this, but disabled it because I didn't know how to propagate the errors to a new reference frequency. After a bit of a stats deep-dive, I think I figured out how to do it (but it needs to full covariance matrix, so it can't be fixed in post-processing). I need to implement this at some point, but don't have time now...

Fixed by #119.


Create admin page with layout

add admin route
create metric card component and use it for total number of records, certificates and users
create text field for search
create users table with some mock data

Closes #23

@humphd @humphd @Ririio
Did a big update with server-side integration, here is what it looks like now:
https://user-images.githubusercontent.com/32075241/228369957-681e671c-d760-401d-a239-53b02f9b30d1.mov

@humphd filed the follow-up of the user certificate status
https://github.com/DevelopingSpace/starchart/issues/473

@humphd filed the follow-up of the user certificate status
#473

Great.  Please flag me when you want a review again.

@humphd filed the follow-up of the user certificate status
#473

Great. Please flag me when you want a review again.

I already did an update so please do it when you can, thanks

@humphd updated, please rereview it

@Myrfion the CI seems stuck here, can you please rebase so we can get this through testing and hopefully landed soon?

@Myrfion please squash all that into 1 commit vs. 8.

Please squash this into a single commit. I'd like to get this landed soon.

I believe we could also squash when merging?

You can, but doing so means you can't also rebase, so you get a merge commit.

You can, but doing so means you can't also rebase, so you get a merge commit.

I carefully copied the code and squashed the commits. I think the PR is ready to go.


Improve i18n navigations

Applied translatedLink to some navigations which are missing it.
When changing the language with the select component on the upper right side, it also changes the current pathname following the selected language.

The second one looks a bit dirty and might be unreadable. We can revert it anytime.

This is truly amazing! thanks, @adhrinae I love how you fixed the select for languages


Prisma Migrate Reset without exectung seed script

I would like to be able to run prisma migrate reset --preview-feature without running the seed script. Ideally I could add a flag to disable it.
The reason is, that I plan to use prisma migrate reset --preview-feature -f as part of my CI process, where I want to handle seeding by myself

Hi,
Thanks for reporting this! It has already been reported before, so I am going to close this as a duplicate of https://github.com/prisma/prisma/issues/5317


fs: Remove a couple debug logs

The trace log in open can be a bit misleading since at first glance it looks like an error, but in some cases it's expected for open to fail, like when calling try_exists.
The debug log in create_dir_all is showing internal details so probably not all that useful to end users.

Checklist

[ ] Sensible git history (for example, squash "typo" or "fix" commits). See the Rewriting History guide for help.
[ ] Update the changelog (if necessary)

I debated a bit here as to whether it might be better to go the other direction here, and add more logs at trace or debug level, e.g. on each entry to open we could trace the path and other parameters. In other parts of the uefi crate we have very little logging, so went with removing -- but I'd be open to a different approach.
(My main motivation for this change is that I spent a little time being confused about why I was getting a file-open error, until I realized it was trace logging happening when calling write on a new file; write calls try_exists, which calls open.)

I'm in favor of removing them. The interface seems to be stable enough (no bug reports in the last couple of months), so we can also remove this very verbose logging - especially as it results in confusions


Checksum for a single file

Please, implement a possibility to calculate a checksum for a single file. I know that there are other tools for that, but there are no utilities which can do a checksum both for a file and a directory.

Stop it, get some help man.
Those tools already do checksums for single file, and if you need both, just issue 2 commands and append the results.


error when running project

after running, i just see  this :
1437.3 ms
189.4 ms
1.0 ms
120.2 ms
41.5 ms
0.6 ms
0.7 ms
at the left+top corner of page
what is this and how i can run currectly ?

My issues were solved by:

putting ruby on the right version with rvm

configuring mysql correctly with a root password (see also: https://stackoverflow.com/questions/4179576/how-do-i-switch-to-older-versions-of-the-ruby-rails-environment )

rm -r frontend/node_modules

npm install

npm i --save<EMAIL_ADDRESS>

foreman start (you need to do run this command every time you make a change with installed packages)


Change bearing with touch event in mobile browsers

Description
deck.gl supports changing bearing of the view fine in desktop browsers. However, this same expected behavior does not work on mobile browsers with deck.gl. With standard Mapbox GL JS (no deck.gl integration), one can change the map's bearing on mobile by holding the map with one finger while simultaneously dragging around with a second finger.
Repro Steps
Visit an example deck.gl map: https://flightmapper.io/maps/dbabbs on mobile. Try to change bearing with touch events. Only zoom with two finger pinch works. Bearing change does not work
To view intended behavior on Mapbox GL JS in mobile browser (without deck.gl dependency), try a map like: https://docs.mapbox.com/mapbox-gl-js/example/simple-map/ . Bearing changes does work.
Environment (please complete the following information):

Framework Version: deck.gl 5.3
Browser Version: Mobile Safari on iOS 12.1.4 or iOS Chrome 72.0.3626.101
OS: iOS 12.1.4

Thanks for reporting, this is a new feature because we never planed doing it in this way.


Overhaul

Merged all JSON files into data.json
Setup routing with route parameters. (added all possible routes)
Reading from RAM instead of doing an I/O Read on every request. (Improves performance and fixes request flooding vulnerability)

Wow sir, this makes my work more easier and better 🎉 🙌🏻


Misc changes

Interface independent changes

Codecov Report

Merging #29 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #29   +/-   ##
=======================================
  Coverage   86.66%   86.66%
=======================================
  Files          11       11
  Lines         525      525
=======================================
  Hits          455      455
  Misses         70       70

Impacted Files
Coverage Δ

tests/test_laplace.cc
100% <ø> (ø)
:arrow_up:

include/mfmg/amge_host.hpp
50% <ø> (ø)
:arrow_up:

tests/main.cc
100% <ø> (ø)
:arrow_up:

include/mfmg/amge.templates.hpp
60% <ø> (ø)
:arrow_up:

source/amge.cc
100% <ø> (ø)
:arrow_up:

include/mfmg/amge_host.templates.hpp
64.89% <100%> (ø)
:arrow_up:

tests/test_eigenvectors.cc
100% <100%> (ø)
:arrow_up:

tests/laplace.hpp
100% <100%> (ø)
: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 0ad106c...8535e37. Read the comment docs.


Combine some short tasks.

bcftools roh and bcftools stats for DeepVariant vcf
writing the cohort yaml and pedigree, as well as the phrank lookup
small variant normalization, slivar filter/annotate, slivar compound hets, and slivar tsv
svpack task compresses and indexes output

Depends on https://github.com/PacificBiosciences/wdl-dockerfiles/pull/31
Depends on https://github.com/PacificBiosciences/wdl-dockerfiles/pull/29

These don't really save a ton of time, but they prevent spinning up extra nodes for 1- to 5-minute jobs.  Trading off added complexity within tasks for reduced overhead of copying inputs and outputs around.


Fix cargo sha

fixes #8566

cc @wizeman

My fetch is getting yet another hash 16f371jj89xplfc1fygvvhyhrq634v0w9674gz6j06m7blxqylpx. Do you know if leaveDotGit is needed? #8567.

@vcunat I just tried to build without leaveDotGit and it seems to build and work fine, apart from some error messages during the build due to the lack of a .git directory, and the lack of the git commit in the output of cargo --version.
Since the leaveDotGit is causing more problems than it solves, I think I will remove it instead of merging this PR to update the hash once again. I will close this PR later when I push the fix.
BTW, the leaveDotGit was introduced by @madjar, so maybe he can clarify if anything else could be broken.

It was package a long time ago, before cargo even had a its 0.1.0 release, so git was pretty much the only way to have a version. Since it now has stable releases, that's not needed anymore. We could even use the github tarball with the same effect.


Support multi-environment

Coverage decreased (-0.2%) to 65.751% when pulling f81b4219ee2d35daf52a00d1b0da9f77fde4fe61 on humingcheng:master into ee0cb876ea8abfb848a163e7f1502bfd0863331c on ServiceComb:master.


There should be a 'forgot password' option on the login page.

As a user it is quiet possible that I forget my login password. If that happens I wont be able to login to my account.
A good solution would be to add a 'Forgot Password' option on the login screen, clicking on which, the user is directed to change their account password via a confirmation link sent to their registered email address.
An alternative that's possible is; when the user clicks on 'Forgot Password' an OTP is sent to their mobile number that is linked to the account. The user can now log in with the OTP and then change their password by going into 'settings'->'change password'.
But, I believe the first suggested implementation would be easier.

@anitab-org/mentorship-backend-maintainers we don't have a forgot password feature yet, right?

Nope. It bothers me too a bit. Fortunately there's some work going on here.

Thanks Bartek, so we can put this on hold for  now

As a user, in case I forget my login password, there should be an option to change it on the login page.

@MaheKhan please use the issue template which can be found here and reformat your issue body

As a user, in case I forget my login password, there should be an option to change it on the login page.
@MaheKhan please use the issue template which can be found here and reformat your issue body

okay. Did that.

Is anyone working on this I want to work on this if no-one is doing this....

Hi @Techno-Disaster. Is this issue open? If open, can this be assigned to me?

Hi @Techno-Disaster. Is this issue open? If open, can this be assigned to me?

Hi @Techno-Disaster. Is this issue open? If open, can this be assigned to me?

Waiting for backend implementation.

Hi @Techno-Disaster. Is this issue open? If open, can this be assigned to me?

Waiting for backend implementation.

Hi @Techno-Disaster. Is this issue open? If open, can this be assigned to me?

Waiting for backend implementation.

Ok.

Hi @Techno-Disaster. Is this issue open? If open, can this be assigned to me?

Waiting for backend implementation.

Ok.


what does "Occurrences" mean?

There is one result of my project:  333222.0ms (cumulative time) and  26 (occurrences)  instance method disLikeButtonPressed().  What does occurrences mean?  And how should I optimize? Thanks.

I'm curious too! All of my files have either 26 or 72 occurrences, which sounds like some thing is triggering the type checker a lot. Any leads on how to investigate would be great

Occurrences mean that the compiler is type checking a method or property multiple times. There's a more information about this here.
Having that said, there's something odd about the new Xcode. When the app was built, this was an irregularity but with the latest Xcode versions it's the norm to have 26-27 occurrences. I haven't had much time for this project lately and thereof haven't looked into why this is.

Interesting -- any chance you could ping the person who recommended the addition of Occurrences to see if they have any input?

Seems that the last version is bugged, it gives everytime "26 occurrences" and the ms for methods are  even higher of that for file!

While I still haven't had time to look into why the latest Xcode results in 26-27 occurrences, the medium post I linked to earlier does explain how and why you can get larger times for a method than for a file.

It can happen due to Batch mode. https://github.com/apple/swift/blob/master/docs/CompilerPerformance.md#compilation-modes
If it's enabled, the compiler will try to combine multiple jobs into a single batch job and will run a single front-end invocation per such job.
The issue here is once a Batch job is finished, it will unpack it, and print the same output as many times as many single jobs were in BatchJob.
In my case, the time was exactly the same for each occurrence. For parseable-output, it's trivial to recognize such a situation. Because "real_pid" will be the same, but negative sub-"pid" will be different for every sub-job.
"pid": -1027,
"process": {
"real_pid": 26760
}
But I'm not sure it's possible to do for logs.


Pasting two lines doesn't replace selected text, is this normal behavior?

You can try it on the demo site, just copy two or more lines of text and select a text to replace on the editor. When you paste it the selected text doesn't get replaced. The text just adds below.

Hi @quiji - yes this is the expected behaviour - if you copy more than one line of content into the editor it will appended that content after the currently selected element.
Improved support for pasting HTML content in is on the list of things to to and we may improve this when we look at copy/paste against. In the meantime if you want to modify the behaviour you can do so by overriding paste method: https://github.com/GetmeUK/ContentTools/blob/master/src/scripts/editor.coffee#L316

Thanks for the quick response!
I noticed there is a paste event. I wonder whats best: patch the paste method or catch the event and prevent bubbling up.. What do you suggest?

@quiji I think I'd recommend clearing the paste event bindings (ContentEdit.Root().unbind('paste')) and then applying your own to handle the paste events. I thinks that's cleaner than patching the ContentTools.EditorApp.paste method personally.


[monitor] Migrate @azure/monitor-opentelemetry to ESM/vitest

Packages impacted by this PR

@azure/monitor-opentelemetry

Issues associated with this PR

https://github.com/Azure/azure-sdk-for-js/issues/31338

Describe the problem that is addressed by this PR
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.