[rebase] 1.18.6

To be force-pushed after approval.
$ git range-diff go1.18.5...cf go1.18.6...bas/1.18.6
 1:  f67f7367cc <  -:  ---------- VERSION: add cf tag
 -:  ---------- >  1:  691dae856b VERSION: add cf tag
 2:  1d4ea6e952 =  2:  79d841592a cmd/go/internal/imports, go/build: add cfgo build tag
 3:  5b0d0981cf =  3:  7232d9060f .github: add docker-compose.yaml and GitHub Action for CI
 4:  ce2e27f7f3 =  4:  9e0dc75d6d .github: remove upstream issue and PR templates
 5:  ca24c1b387 =  5:  4f0dc5910b .github: update CODE_OF_CONDUCT.md and add PR template
 6:  7766f2d2b2 =  6:  abf5e1c061 cmd/api, go/build: ignore CF-specific API changes
 7:  c8e9d551f1 =  7:  f2bcb1e099 circl: import crypto library CIRCL
 8:  7df2f0a3ef =  8:  5535f67af3 crypto: add support for CIRCL signature schemes
 9:  40f45ba033 =  9:  9d6c988ae4 crypto/tls: add PQSignatureSchemesEnabled option
10:  fce4049412 = 10:  ddcc1eef9e crypto/tls: add CFControl parameter to Config
11:  228eb60ea2 = 11:  0e028b9a76 crypto/tls: add Config.CFEventHandler to expose intra-handshake timing
12:  25a938be77 = 12:  f64b58ce72 crypto/tls: implement draft-ietf-tls-subcerts-10
13:  512de31620 = 13:  8063e0d0af crypto/tls: implement draft-ietf-tls-esni-13
14:  b82366e6f9 = 14:  580551c54c Fix CIRCL integration and dependencies. (#115)
15:  536f4232b3 = 15:  b1785c694e Add hybrid post-quantum key agreement.
16:  f99753b4a2 = 16:  5eb5ff0d96 tls: Expose PQ CurveIDs (#121)
17:  7ecb308d0e = 17:  2bba1fcfae Update circl, changing hybrid post-quantum key exchanges (#123)
18:  e4f07a8a47 = 18:  210ad3a703 tls: rename Kyber<x>X25519 to X25519Kyber<x>Draft00 (#122)
19:  109e878a17 = 19:  ca3fe71a7f crypto/tls: TLS 1.3: Send alert on invalid ECDH share (#126)
20:  fcd6ea914c = 20:  abb10c141e Fix DC implementation #131
21:  4d2a840e50 = 21:  d42b2400d4 tls: report CurveIDs for TLS <1.2 kexes (#132)

We could probably have squashed some commits such as

Will do in a separate PR before rebasing to 1.19.x.


docs(Block): add documentation to Block

Add documentation to the Block widget and its sub-components (Padding, Borders).
Relates to #386

I fixed most of your comments. I just left out the comments about the style and style prioritization. I agree that we should use a consistent language and document the style priorities. But I think this would be better documented in the style module (mainly the way we merge style), then any method could reference that as a base and add on top of it.
As for the consistent language, we could add to the guideline, for example:

Setters that replace values use this sentence: 'Sets xxx'
Setters that add default values use this sentence: 'Sets the default for xxx'

Put in other words, some sort of template.
Let me know what you think. I think consistency is very important, but how do we enforce it across multiple collaborators.

Thanks - I'll slap together a PR that fixes up the remaining wording for styles.

I removed the commit message body, as I don't think it really added much info to the changelog that wouldn't be answered by reading the commit title.


how to make the package Server start just by Android studio IDE,or use the custom gradle sh?

i alwas saw the error at bottom when i change different project patch without close the package  nodeserver

i just know to use


Allow changing opacity of kbd in menus

"workbench.colorCustomizations": {
    "menu.keyboardShortcutOpacity": "#fff8",
},

@usernamehw thank you for the Pull Request, please follow our PR guidelines:
<!-- Thank you for submitting a Pull Request. Please:
* Read our Pull Request guidelines:
  https://github.com/Microsoft/vscode/wiki/How-to-Contribute#pull-requests.
* Associate an issue with the Pull Request.
* Ensure that the code is up-to-date with the `master` branch.
* Include a description of the proposed changes and how to test them.
-->

Not able to find the issue. (It might be actually closed).
The idea is to make possible reducing shortcut visibility and focus on the text of the menu item.
Default opacity should be the same as theme foreground (usually 1). Changeable via theme or workbench.colorCustomizations.


[BUG] ctx.selected_labels is empty in resolve_input and resolve_output

System information

OS Platform and Distribution: Ubuntu 20.04
Python version: 3.8.10
FiftyOne version: 0.22.0
FiftyOne installed from: pip

Commands to reproduce
See the sample operator in the code section below.
Describe the problem
The ctx.selected_labels always return an empty list when it is read from the context of resolve_input and resolve_output of an operator in python. The ctx.selected_labels returns the correct information only when it is read from the execute function. It is worth noting that the value of ctx.selected works correctly in the three functions.
The below screenshots shows the input and output panels of the below referenced sample operator.
Operator Input:

Operator Output:

Having a look at the frontend code, it seems that the selectedLabels state is missing from useExecutionContext:
https://github.com/voxel51/fiftyone/blob/7ee780bc7a4c854371dc9c5facd181517a718d9b/app/packages/operators/src/state.ts#L113-L132
Code to reproduce issue
Below is a sample operator to reproduce the behavior:
class SelectedLabelsOperator(foo.Operator):
    @property
    def config(self):
        return foo.OperatorConfig(
            name="selected_labels_operator",
            label="Selected Labels Operator",
            dynamic=True,
        )

    def resolve_input(self, ctx):
        inputs = types.Object()

        inputs.message(
            "Number of Selected Labels",
            label=f"Number of Selected Label: {len(ctx.selected_labels)}",
        )

        inputs.message(
            "Number Selected Samples",
            label=f"Number Selected Samples: {len(ctx.selected)}",
        )

        return types.Property(inputs)

    def execute(self, ctx):
        return {
            "num_selected_labels": len(ctx.selected_labels),
            "num_selected_samples": len(ctx.selected),
        }

    def resolve_output(self, ctx):
        outputs = types.Object()

        outputs.message(
            "Number of Selected Labels",
            label=f"Number of Selected Label: {len(ctx.selected_labels)}",
        )

        outputs.message(
            "Number Selected Samples",
            label=f"Number Selected Samples: {len(ctx.selected)}",
        )

        outputs.int("num_selected_labels", label="Num Selected Labels")
        outputs.int("num_selected_samples", label="Num Selected Samples")

        return types.Property(outputs)

Other info/logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Please do not use screenshots for sharing text. Code snippets should be used instead when providing tracebacks, logs, etc.
What areas of FiftyOne does this bug affect?

[x] App: FiftyOne application issue
[ ] Core: Core Python library issue
[ ] Server: FiftyOne server issue

Willingness to contribute
The FiftyOne Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the FiftyOne codebase?

[ ] Yes. I can contribute a fix for this bug independently
[ ] Yes. I would be willing to contribute a fix for this bug with guidance from the FiftyOne community
[ ] No. I cannot contribute a bug fix at this time

@msamadony Thank you for the very detailed bug report. I've submitted a PR to fix this #3558.

@ritch Thanks a lot for the very quick feedback and fix. I left you one comment/question there, as I suspect there is another line that needs to be updated as well.


installation error

when i install this language it shows red error that this package is not available,
also could you please add norwegian language, so i will install it ?
http://<IP_ADDRESS>/download.php
thank you

Sorry, we missed these tickets.
We have fixed. Thanks for your report.


Ngera/ ngara

Ngera/ ngara  created by<EMAIL_ADDRESS>on 2018-06-18 12:41:05

<EMAIL_ADDRESS>replied, All, Thoughts on the below please? My personal thought is it ngera is a question word and ngara is a declaration of existence/location. And, probably, that inconsistent spelling has muddled them for decades.
I thought I'd share this email from Bena Sakuma with you.  This was regarding a translation/transcription of the words to Mangtekang which includes the phrase "e di ngera aikal moruul", which I had originally had as "e di nga era aikal moruul".  I had made the comment that according to the dictionary, ngara and ngera are alternate spellings for "what, which".  Bena said:
(NGERA) is question such as (NGERA SOAM? NGERA KEDILUNG? NGERA UNGIL? (NGARA) BELONGS TO ORGANIZATION) NGARA OMERAEL OR NGARA TLOK OR NGARA BOES  ngera is always a question.  ngara is never used to ask question
I see that Josephs has "ngara/ngarang" as the question word "what", so I'll let you figure out who is the correct on this.  When I was in Palau in March, I was told that Bena (who I knew back in the 80s) is considered to be someone quite authoritative on the language.

<EMAIL_ADDRESS>replied, Ngara Metal, Ngara boes, Ngara kikm,  Ngara chelong , Ngara mlengui.
Ngaraard, etc.  Some place names like States have changed their spelling
from Ngara   to Ngere . Good to find out why the changes were made.

<EMAIL_ADDRESS>replied, ngera / ngerang is a question word that is sometimes misspelled as ngara / ngarang. ngara as a verb is contraction of ngar er a... absolutely different word from the first one...

<EMAIL_ADDRESS>replied, It is not necessarily misspelled all the time. They are both used in
questions.
"Ngara" is used in questions that ask about location, direction, time of
event, and the likes. Examples: 1) Ngara keskelel a uum? Where in the
kitchen is it? 2). Ngara telang el klok ra mekong? About what time did you
get there? 3) Ngara mo bedul ker a blim ra urerem? Which direction is your
house from your work?
Then "ngera" is for all others. Examples: 1) Ngera meng uaisei a
blekerdelem? Why are you acting like that? 2) Ngera ke dilung er tir? What
did you tell them? 3) Ngera rolel e ak rullau el ocherchur? How do I make
you laugh?
J


allowMajorUpdates Parameters for update-properties Maven Goal

I've noticed versions:update-properties goal is missing the following optional parameters that are available to the use-latest-versions goal:
allowIncrementalUpdates: Whether to allow the incremental version number to be changed.
allowMajorUpdates: Whether to allow the major version number to be changed.
allowMinorUpdates: Whether to allow the minor version number to be changed.
Is there any way to use these parameters with the versions:update-properties goal?

I too would like to see this, and it feels like the two goals should be consistent in this manner.

+1

+1 also
These are very useful parameters. use-latest-versions and its variants cannot update properties and; update-properties can only change version to the latest value. There is a gap here.

+1

+1 Not auto-updating to the next major version (which would have breaking API changes) is important..

+1

+1

+1

+1

+1.

This issue is already fixed.


Click event not triggered for drag target

Hi,
Version:  Master as at 06-Sep-2015
The click event is not being triggered for drag sources. Here is a fiddle that demonstrates the problem.
In the fiddle, the click event is bound for both the #source and #target elements. When tested on iOS 8.4.1, tapping on the drop target should alert 'target clicked'. However, tapping on the drag source does not alert anything.
There is some documentation on this on MDN.
Thanks.

This is a known shortcoming, although I guess it didn't have an open issue. We currently only generate that click event for anchor elements which don't have an explicit draggable attribute.
I've discussed this issue a bit before.

... the browsers initiate their native drag handling only in special cases, when the mouse is moved a certain amount after being pressed down. Without sufficient movement, it's handled as a classic click.

Ideally we would like to have similar handling via touchmove and fallback to clicks without enough movement ...

We don't have the ideal implementation yet, and so we initiate the drag event even if you don't move your cursor after pressing down.
I'm not sure if the new spec branch behaves correctly already, however this would certainly be something suited for that branch.


feat: output subnet association IDs

Output route table, network security group and NAT gateway association IDs.

Closing because the value of the subnet association ID is the exact same as the value of the subnet ID. No reason to output both.


Is there an easy way to go back to the starting point?

This looked like a promising tool for making tas speedruns, but I found after I ran a script, it was difficult to go back to the starting position, without running a tp command. Is there a built-in way to do this?

Save-states have been added in the most recent version. A more robust version will come later.


GUI Text for viewer.py

🚀 Feature
Add a Text GUI interface to viewer.py.
Motivation
Currently, we use Magnum::ImGuiIntegration to render text to the window for viewer.cpp (C++ viewer application). We'd like to have a similar interface for adding text to frames in viewer.py (Python viewer application)
Additional context
At some point we (@mosra) discussed this and determined there may be some blockers implementing this feature in Python. If so, let's record them here for tracking.

I don't remember any blockers for implementing this, really. Except that I'd have to expose a few more Magnum APIs to Python, which is nothing complex on its own. I could do that.
Back then we used ImGui because it allowed to have a tiny FPS counter done with a single line of code ... but at the cost of a massive new dependency, of which we use not even 1%. Because ImGui is a large library on its own, exposing all of it to Python is not simple. There's PyImGui but for that I'd first need to make it work with the Magnum backend, and that's currently an unknown amount of work. Instead, I'd really like to use the far more lightweight Magnum::Text library, for both C++ and Python.

I don't remember any blockers for implementing this, really. Except that I'd have to expose a few more Magnum APIs to Python, which is nothing complex on its own. I could do that.

That would be great. If the investment is small, I'd like to get this working.

I'd really like to use the far more lightweight Magnum::Text library, for both C++ and Python.

That sounds fine to me. Remove a dependency and have a better mirror between the C++ and python implementations. Is that ready to use for C++? Looks like we'd need bindings to support python.

Yes, that's what I meant -- the Text library is ready to be used from C++, it just needs to have its essential functionality exposed to Python. I'll reach out to you on Slack to discuss priorities.


Resolved issues in removing namespace for additional upf's

The namespace for the additional UPF's not removed properly. So updating the shell command in the uninstall file to remove the namespace properly.

Thanks. I'll take care of re-sync'ing aether-onramp.


Change deprecated terminal command (Third PR)

Hope this time it's gonna be ok :)
Fixes #2706

I am really sorry but I have no idea how to pass Add new issues to project check — the issue was created and referenced correctly. I don't know what else I need to do.

I am really sorry but I have no idea how to pass Add new issues to project check — the issue was created and referenced correctly. I don't know what else I need to do.
Nothing on your side, that's my issue ;)

LGTM, thanks!


registerOnRemoveHandler cannot be called from Config/Settings page or iframeContext

The registerOnRemoveHandler cannot be called from Config/Settings page or iframeContext, I get an error when I try to do so.
I've created a second page for the removal experience where I call registerOnRemoveHandler (basically a call to our backend to clean up), and register the url for that page when I call setSettings - though, the app doesn't redirect there, so what's the point of the removeUrl anyhow?
Any help is much appreciated.

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

ID: c21a27c1-d01a-6cc7-c991-73af6492aad8
Version Independent ID: b15d2142-df29-250e-9a0a-b734dcb93162
Content: Office 365 Connectors - Teams
Content Source: msteams-platform/concepts/connectors/connectors-creating.md
Product: msteams
GitHub Login: @o365devx
Microsoft Alias: o365devx

removeUrl is used for Tab removal experience. For Connectros removeUrl is not used. Please take a look at Integrating the configuration experience.
For Connectors, Register a microsoftTeams.settings.registerOnRemoveHandler() event handler, which gets called when the user removes your connector. Please take a look at sample Connector code for the same. You can quickly try this using Connector App manifest to check if event is getting fired for you or not.
If you are still facing issue, please share code snippet of what you are trying.


Add animations for switch

Can you please add animations for the switch and stuff? That would take this project to a new level.

I would have added animations, but Tkinter doesn't support animations of any kind. So I just simply can't.

You could provide the animations so that you can use them something like https://stackoverflow.com/questions/65223063/is-it-possible-to-provide-animation-on-image-tkinter


VS 2017 references old versions even after installing Latest SDK

I was using .Net Core 2.1.1 untill now, and recently updated the SDK to 2.1.401 (.Net Core Runtime 2.1.3). When i create a new project the version of Microsoft.AspNetCore.App and Microsoft.NETCore.App under Dependencies > SDK is still 2.1.1. Looking at the properties of Dependencies > NuGet, the package is being referenced from "C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.app\2.1.1"
I tried installing Package 2.1.3 using NuGet package manager, and it downloaded all dependencies (v2.1.3) from NuGet despite that i have 2.1.3 already installed on my machine.
I've tried specifying the version in the .csproj file, but again it downloads from the NuGet.
I am using VS 15.7.4 on Win 10 x64. And i have following .Net Core SDKs installed on my machine :
1.1.0 , 2.0.0 , 2.1.201 , 2.1.301 , 2.1.302 , 2.1.401.

We control sdk-version by having a global.json in the root of our solution.
{
    "sdk": {
        "version": "2.1.401"
    }
}

We are on Linux and Mac (vscode), but I guess this should work when you are using Visual Studio as well.

@uffebjorklund Sorry i couldn't find global.json anywhere in my project.

There is no global.json by default.. just add one and then copy paste the content from my first post

I have also faced this issue. This is irrespective of VS 2017.  I am not sure why NuGetFallbackFolder\ folder has the older version. When you issue dotnet --info command, it displays the current version.
I have also checked this after deleting the NuGetFallbackFolder. Once it's deleted, this is folder get again created at the time of dotnet new from somewhere (but don't know from where).

Issue moved to dotnet/cli #9933 via ZenHub


Questions about the most original dataset

Hello. I want to know if there are any more original datasets beyond this dataset, and if I want to train my own dataset, what format should it be in? Alternatively, if I want to use an open-source dataset for training, how can I convert it into the format shown in the image?

Hello. The image contains all of our original datasets. Please refer to instruction_generate to generate the text.


Fix jackson and resteasy deps

@andreaturli Thanks. Will wait for Jenkins and merge.

@sjcorbett, does the failure looks related to you?

close and re-open to rebuild

No, looks like another unreliable test.


Problem Generating signature

We are having a problem to use your API.
normalized_params = urllib.urlencode(zsorted_params)
AttributeError: module 'urllib' has no attribute 'urlencode'
Generating signature libraries has been updated.

This module is written in Python 2. Are you using Python 3?

use normalized_params = urllib.parse.urlencode(sorted_params) instead of
normalized_params = urllib.urlencode(sorted_params)


[Bug]: Scanning and adding sensitive columns will only add one page of sensitive columns

ODC version
odc423
OB version

What happened?
Scanning and adding sensitive columns will only add one page of sensitive columns
What did you expect to happen?
Add all sensitive columns scanned out
How can we reproduce it (as minimally and precisely as possible)?
Scan multiple pages of sensitive columns and add sensitive columns. Scan again to view sensitive columns
Anything else we need to know?
No response
Cloud
No response

Fixed In Commit 33a649a8923bb8f78f17b3cc15c54f884142735a

pass


Almost a JS

Looks like Lemon is close to JS so why not to make it as a subset of JS?

JS is also close to Java, Java is also close to C++, C++ is also close to C. This is no point question.

I am not against Lemon syntax per se. Just a learning curve consideration for new people.
At least I would implement JS runtime library: Array, String, Object methods with familiar signatures.
Source code and architecture looks clean and nice so it may evolve to something interesting.
But problem is that you have plenty other competitors from micro JS implementations to big ones.
So either you will provide some unique features or super small and effective implementation of existing language. Some selling point is required to be short.

I have zero intention make Lemon replace JavaScript.The syntax is familiar like JS is not a because Lemon syntax like JS.It's becuase JS's syntax like others.
I'm a C developer,so the syntax is very straight forward, also I'm not interested invent some weird syntax just let people think Lemon is different,just quite opposite I'd like people use it smoothly.
The competitor from JS is absurd,If someone use JS very well, they have no reason replace to Lemon. if someone will give Lemon a try, they can always fallback to JS, everyone happy, right?
if you want discuss more about Lemon, I suggest open a topic in https://groups.google.com/d/forum/lemon-lang I'd be happy to answer anything about Lemon, Thanks.


Allow packages that rely on fourseven:scss to add an include path

This is an idea to make it easier for users to include partials provided by other packages such as reywood:bootstrap3-sass or matthew:foundation5-sass. Currently, the user has to include something along the lines of @import '.meteor/local/build/programs/server/assets/packages/reywood:bootstrap3-sass/bootstrap'; in their scss file to use these packages. One problem with this is that some systems apparently have an underscore instead of a colon in the path.
Here's a half baked idea I came up with to maybe solve this problem. In a package that relies on fourseven:scss, one would include a JS file on the server (i.e. api.addFiles([ "include-path.js" ], "server")). In that file, they would have something like Scss.addIncludePath("path/to/reywood:bootstrap3-sass"), and meteor-scss could push that value onto the includePaths array option. Then users could just add @import 'bootstrap'; to their scss file. I haven't quite figured out how to get the real path to the package in a consistent way, but figured this would be food for thought.

+1

3.4.0-beta1 supports cross-package imports for this.


Blended queries with boolean rewrite can result in inconsistent scores [LUCENE-9269]

If two blended queries are should clauses of a boolean query and are built so that

some of their terms are the same
their rewrite method is BlendedTermQuery.BOOLEAN_REWRITE

the docFreq for the overlapping terms used for scoring is picked as follow:

if the overlapping terms are not boosted, the df of the term in the first blended query is used
if any of the overlapping terms is boosted, the df is picked at (what looks like) random.

A few examples using a field with 2 terms: f:a (df: 2), and f:b (df: 3).
a)
Blended(f:a f:b) Blended (f:a)
        df: 3             df: 2
gets rewritten to:
(f:a)^2.0 (f:b)
df: 3      df:2

b)
Blended(f:a) Blended(f:a f:b)
        df: 2        df: 3
gets rewritten to:
(f:a)^2.0 (f:b)
 df: 2     df:2

c)
Blended(f:a f:b^0.66) Blended (f:a^0.75)
        df: 3                  df: 2
gets rewritten to:
(f:a)^1.75 (f:b)^0.66
 df:?       df:2

with ? either 2 or 3, depending on the run.

Migrated from LUCENE-9269 by Michele Palmia (@micpalmia), updated Apr 11 2022
Attachments: LUCENE-9269-test.patch

I recently encountered this issue when migrating from Solr 7.x to 9.x. For me it caused wrong scores for a query that consists of exact match with a boost ORed with a fuzzy match, e.g.:
text:foobar^10 OR text:foobar~1
I think it should be quite a popular use-case, so I'm a little surprised this issue is not more popular.
Debugging it I came to the same conclusion, that TermQuery should take into consideration its perReaderTermState field in equals and hashCode implementation.
I have made a simple app that demonstrates the problem: bug-example.zip
Please note that this problem may not always be visible and seem random because it depends on hash codes that depend on StringHelper.GOOD_FAST_HASH_SEED which is based on the current time. It is useful to set tests.seed system property to reproduce the problem consistently.
@micpalmia have you succeeded in implementing the fix? Is there any chance for a PR?

while testing a solution for adding perReaderTermState to the current TermQuery#equals implementation, I found a test that I believe is not doing anything of what it was designed to do - essentially it was rewritten for an only tangentially related change, and it's been working as no-op since (test is TestMultiTermQueryRewrites#checkBoosts, problematic edit was this, missing essential initialSeekTerm). Should I fix it as part of my proposal for this or open a new issue?

Yikes -- did you ever open a separate issue/PR for this missing initialSeekTerm?


[Question] Will a jetbrains plugin be developed?

Hi there!
I am using PHPstorm and astro type of file is not supported by the ide. Are there plans to develop a plugin for it?
Thanks.

I am using PHPstorm and astro type of file is not supported by the ide. Are there plans to develop a plugin for it?
Thanks.

Hello @yesworld, we talk about this on our docs' Editor Setup page: https://docs.astro.build/en/editor-setup/#jetbrains-ides
TL;DR: We would love to support JetBrains IDEs but they don't support language servers, meaning we would have to write an entirely new extension in another language. The future Fleet IDE will support language servers though, and then we will be able to run our current tooling in it.


fix(wattpm): graceful shutdown not working

wattpm closes the process without waiting for the default 10s. I also tried manually adding it to the watt.json config, but it's still not considered.
You can reproduce this issue here. This causes fastify hooks like onClose or preClose to not being triggered, while like onReady are.

@ShogunPanda can you take a look?

wattpm closes the process without waiting for the default 10s. I also tried manually adding it to the watt.json config, but it's still not considered.

It shouldn’t wait for the default 10s. The 10s are only needed if something does not close properly, otherwise it’s instant.

Ok, so the main issue here seems to be that:

fastify hooks like onClose or preClose to not being triggered


Unable to login if Ghost admin is at /blog/ghost

Ghost version: 0.11.4
App version: 1.5.3

I can't login into my blog anymore since the latest updates. My ghost installation is under example.com/blog/ if it helps. I noticed that the app had troubles handling that, redirecting me to the root URL sometimes instead. So this detail might help.
The app is just showing "unexpected error during sign in. Please try again" toast.
I already tried clearing the cache or reinstalling, still no luck.

Hi @RcrdBrt, your detail about the blog being under example.com/blog/ seems spot-on - I don't test with that kind of setup. I should probably add a unit test for this case.
I'll fix this. Thanks for reporting!

Would you mind sharing your blog URL for testing purposes? The only thing I will do is try to login with incorrect username/password a few times, of course.

Sure. Https://rcrdbrt.com/blog

This is fixed. There are also now unit tests in place to check for various types of blogs (blog.example.com, example.com/blog, https://my-blog.com, etc), so hopefully this kind of issue won't happen again.


binary-handling 2nd try

moved 'src' handling from CachingFilterInputStream into Caches, added AbstractFilterInputStreamCache which handles basic 'src' handling functions and keeps track of 'consumers', Caches extend AbstractFilterInputStreamCache now.

I am still having problems, I have updated to the latest git and the latest hub. Can you try this locally in some scratch folder and let me know if it works:
git clone https://github.com/adamretter/restream.git
cd restream
git checkout -b pr-2
hub am -3 https://github.com/adamretter/restream/pull/2

Ignoring the white space seems to help:
hub am -3 https://github.com/adamretter/restream/pull/2 --ignore-whitespace


fix: put the space back in the space name

There were the following issues with your Pull Request

Commit: 21aa4a5e016cf8a9a2239a4fd215d5e039493eba
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/fabric8io/fabric8-ui

This message was auto-generated by https://gitcop.com

@pmuir snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-821-fabric8-ui.int.rdu2c.fabric8.io


Export RouterSink and HistoryAction

Note I had to skip the commit hook as it fails on Windows (probably OK on Bash on Ubuntu for Windows)
Also I didn't Update the version as while there are no instructions it looks like this is a separate process.

Cool.  Released as 4.0.7


training problem

I'm a new rookie to be honest, and I wonder where to modify the batch_size in this project.
I got no result after searched in the config files.
I ask this question because all my 4 V100 gpus use very little memory even I modify the 'samples_per_gpu' to 400, which is very inefficient.

Thanks for your help and looking forward to your guidance :)

samples_per_gpu is the correct field to modify. However, your observation does seem abnormal to me. Perhaps you can add the -v flag to the torchpack command to see whether there are error messages.

samples_per_gpu is the correct field to modify. However, your observation does seem abnormal to me. Perhaps you can add the -v flag to the torchpack command to see whether there are error messages.

Thanks a lot, I'll try

Hi Haotian,
I solved last problem by adding the -v flag, thank you very much.
However new problem came out:
Traceback (most recent call last):
File "tools/train.py", line 96, in
main()
File "tools/train.py", line 85, in main
train_model(
File "/home/yetonghui/project/mitbevfusion/mmdet3d/apis/train.py", line 93, in train_model
cfg.lr_config,
File "/home/yetonghui/project/tools/anaconda3/envs/mit_bevfusion/lib/python3.8/site-packages/mmcv/utils/config.py", line 507, in getattr
return getattr(self._cfg_dict, name)
File "/home/yetonghui/project/tools/anaconda3/envs/mit_bevfusion/lib/python3.8/site-packages/mmcv/utils/config.py", line 48, in getattr
raise ex
AttributeError: 'ConfigDict' object has no attribute 'lr_config'
I checked the items in cfg but there's no key named 'lr_config'. So I wonder where to find this 'lr-config'.
Maybe I got some omissions in the yaml files? But I git clone this project completely, which means the yaml files are completely correct.
Please point out my mistakes.
Best,
Tonghui

That's because we haven't released the lr_config in the current release. We anticipate that the training details will be released next month, please stay tuned.

thank u :)
It is really an excellent work!
wish u the best

Closed due to inactivity.


Doctests failing

What is your issue?
The doctest is currently failing with

E   UserWarning: h5py is running against HDF5 1.14.3 when it was built against 1.14.2, this may cause problems

this is something that's out of our control, h5py would have to be built against hdf5=1.14.3 on conda-forge. How do we usually deal with warnings raised by dependencies? Add a filter to one of the conftest.py files?


fix: focus management for stepper

PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] If applicable, have a visual design approval

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] clarity.design website / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?
When navigating between steps using the next button the focus was not set on the next step heading button.
Issue Number: N/A
https://github.com/vmware/clarity/issues/3528
What is the new behavior?
When the user clicks next on a valid step the next step is automatically focused.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

WIP: need to update the aria announcements to remove the success state as it is no longer needed with the focus management.


Rails 5 support

As Rails 5.0 is out now, can we get compatibility release in rubygems, please?

I will soon. It's there but for some unfinished tests and fixes. Have you been using the repo? If so, have you seen any issues?

On Jul 18, 2016, at 9:07 AM, Miks Miķelsons<EMAIL_ADDRESS>wrote:
As Rails 5.0 is out now, can we get compatibility release in rubygems, please?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

No, I'm not used because in my case it's dependancy in another gem.

Which gem?

On Jul 18, 2016, at 10:33 PM, Miks Miķelsons<EMAIL_ADDRESS>wrote:
No, I'm not used because in my case it's dependancy in another gem.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Nothing famous - https://github.com/cubesystems/releaf

@straydogstudio i am about to use this gem in a Rails 5.0 project over the weekend, will let you know if any problem arise.

Thanks. My test suite ran with no errors or deprecations using the repo. I am totally buried. But hope to get this out in the next few days.

Version 0.5.0 with Rails 5 support and testing is published.


Check if statically degrqdes img quality

Investigation
CDN
https://cdn.statically.io/img/r9.lv/i/20200820-Juglas-Shoemaker-0001-1-by-Janis-Rullis-2048x.webp
Origin
r9.lv/i/20200820-Juglas-Shoemaker-0001-1-by-Janis-Rullis-2048x.webp

Conclusion
Keep the CDN solution because it looks exactly as the original.
Although the size is smaller, doesn't mean it is done on the account of the quality (maybe stripped away some EXIF or the compression is excellently done).
Note
If doubts arise again, then repeat this task. Maybe the example used here wasn't very fitting to notice differences.


Circleci project setup

version: 2.1
orbs:
node<EMAIL_ADDRESS>jobs:
build:
executor:
name: node/default
tag: '10.4'
steps:
- checkout
- node/with-cache:
steps:
- run: npm install
- run: npm run test

version: 2.1
orbs:
node<EMAIL_ADDRESS>jobs:
build:
executor:
name: node/default
tag: '10.4'
steps:

checkout
node/with-cache:
steps:
run: npm install
run: npm run test


test module is not packaged

As a packager, I'm usually running unit tests for every packaging.
Ah, I see, tests work for python3 only. :(
Let me know, if you're planning to change the situation.

Simplecrypto now packages the tests module.
I've migrated to Python 3 years ago, and the bytes <-> str incompatibility is specially hard hitting on some of the modules (formats, for example). So sorry, but I don't have plans to backport the tests to Python 2. However, I'll be thankful if somebody does it and submits a PR.


yt-dlp upgrade, non-web content detection tweak

Upgraded to yt-dlp 2023.06.21
Tweaked non-web content detection to account for absence of content-type (assume target url is web content in that case)

Thanks @bensteinberg! Good catch, as always 🦅 👁


fix(README) : Prepare Prerequisites on Arch Linux

After I install arch linux and prepare according to the prompt of README.MD. When I excute the commands follows , error occurs.
# In the TiFlash repository root:
mkdir cmake-build-debug  # The directory name can be customized
cd cmake-build-debug

cmake .. -GNinja -DCMAKE_BUILD_TYPE=DEBUG

ninja tiflash

error(cmake/tools.cmake:87):
Cannot find ar.

After excute
sudo pacman -S llvm

No error occurs again.
What problem does this PR solve?
Issue Number: close #6800
Problem Summary:  Prepare Prerequisites on Arch Linux is not enough. We should add ' llvm ' .
What is changed and how it works?
Just append ' llvm ' in prepare commands on Arch Linux in README.md
Check List

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note
None

Thanks for your contribution. But we have mention llvm in line59 - 61 🤔

I just read the 59-61 lines of readme.md. Is that the content of Ubuntu not Arch Linux ?

/run-all-tests

/run-all-tests

/merge


Annotations support

Description:
Need to be able to add annotations using Kuberneted:Deployment annotation, like below.
spec:
  replicas: 1
  template:
    metadata:
      annotations:
       prometheus.io/scrape: "true"
       prometheus.io/path: /metrics
       prometheus.io/port: "9797"

Sorry Raj, I am confusing? what do you really want?


Ad manager no longer self inits

An oversight from the Jasmine 2 upgrade. Ad manager no longer self inits because it was impossible to test without it sprawling across several of it's dependencies.

Does this need a code change in app_core to call init() then?

It's already there, I just missed this https://github.com/lonelyplanet/rizzo/blob/master/app/assets/javascripts/app_core.js#L28

Ah, gotcha
+1


Get dependencies up to date

Bump ruby version: 2.3.1 is the latest ruby version. This also adds it to the Gemfile for a
bundler check.
Remove heroku buildpacks: We can deploy this directly from gh-pages, and don't have a need for
Heroku.
Update scss-lint config: v0.50 is even with thoughtbot's sass guides.

👍

We can deploy this directly from gh-pages

Take a look at Netlify, it’s where we are deploying the new Bourbon and Neat websites and is really quite nice. Gives us a few features that GitHub Pages does not have:

Automatic PR preview websites so you can view changes on a special PR-specific URL
Free, one-click SSL
Integrations directly with GitHub for automatic deploys
Still free for open-source projects

@tysongach Nice, I'll dig into that. Thank you.


Update README.md relative path live reload

Updated description on how to support relative paths live reload outside of current app.

AFAIK, this is not guaranteed to work across all operating systems, so I would prefer to not document it.

Do you know where it wouldn't work? I've checked it on mac. Feel free to close PR then)

Some systems only allow you to monitor the current working directory or a given directory, so nothing outside of the Phoenix root would be caught.


There is a problem with the configuration.

@fro9-dev can you try the latest version 6.1.1 on windows and see if you still see an issue.

All my problems have been solved.
I'll close this PR.
Thank you for your quick feedback 👋


change react default icon to openai

hey!! i could work with it . could you please assign it to me ?

@Nishad-007 what do you mean?

Going to have to decline this one because, even though the app clearly does need a better favicon, using OpenAI's logo is probably a copyright concern.


Program FAQ Draft

Draft of program materials that will serve as basis for landing page and/or FAQ.

[ ] Base on eligibility requirements from UBF
[ ] Base on format used in sample CFR from LSB team

DoD:

[ ] Share with Howard, Harpreet, Jeanne, Susan, Catherine
[ ] Set a deadline for edits/discussion that fits with target program launch date

No longer relevant.


Add an option to send an empty commit in vscode

Currently if you try using the vscode git UI, you can only send a commit, if some changes have been made to the code base. It would be nice to have an option of sending an empty commit using the UI.

Here's a scenario where it could be helpful. Say, you have a repository which runs various CI's. But you don't want to change anything in the code base. You only want to send an empty commit, such that the CI(s) are triggered because of the commit. Yes, I can issue the following command from the command line. But, I can't if I am using github.dev (without a command line/codespaces).
git commit --allow-empty -m "This is an empty commit"

An example:
When conda-forge feedstock's are created, sometimes you would need to send a PR with an empty commit, to trigger building the package(s) on conda-forge channel. I find it quite useful to work on the conda-forge PR's from github.dev. So, allowing to send an empty commit with an optional message would be really helpful.

See https://github.com/microsoft/vscode/issues/107753#issuecomment-705609420

This is possible either by clicking the Commit button in the SCM viewlet when there are no current change, or by invoking the Git: Commit Empty command from the command palette. Will be closing this issue for now, but please feel free to reopen in case these commands do not work for you. Thanks!

Thank you.

@lszomoru Thank you, for your response. But when I tried this from github.dev, it did not work.

It looks like the functionality to add an empty commit does not exist in GitHub.dev and vscode.dev.


Suggestion for fixing the propblem with type comparisons in QSettingsManager._get

This PR fixes #8 , #12 , #10 , #11 and #9

Thanks again for your contributions @MrLeeh
I have a few tests to run and then I'll release this onto PyPi.


fix(elastic): update offset2ids management

Goals:
Solving inconsistent offset issue on deletion https://github.com/jina-ai/docarray/issues/407.
I've found that after index deletion, update offset persistence has missed on truncating the trailing offset if the len of ids is less than initial length. So in this PR I submit logic to reevaluate offset length compared to in memory offset ids list and bulk delete offset which is more than the offset ids len
Also solving inconsitent offset issue on extend/add https://github.com/jina-ai/docarray/issues/412
Elasticsearch handle document indexing as upsert operation when indexing using same id, however the extend logic didn't using this logic, so I update the offset indexing to not extend id that already exist

...
...
[x] check and update documentation, if required. See guide

please re-review @JoanFM


Remove subdivision from Scheme2SortingParameters

Seems like this argument is not used anywhere. It is also not described in scheme2.md. Perhaps redundant with phase1_npca_per_subdivision?

Thanks @khl02007 !


[ogre-next] upgrade ogre-next 2.3.3 and fix osx

fix #35114

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

How I sold the error?
fatal error: 'wchar.h' file not found

We should update the image of the ci?
https://stackoverflow.com/questions/26185978/macos-wchar-h-file-not-found

@talregev I think it's enough that we have installed OSX 13.5 and xcode. Maybe it's a usage or condition issue? https://github.com/microsoft/vcpkg/blob/master/scripts/azure-pipelines/osx/README.md

@FrankXie05 as I understand from the stack overflow, we should update the latest headers. not update the osx nor the xcode.
Can you verify that?

Can you also tag a mac osx users?

@BillyONeal I tag you as you update the ci image if needed.

@talregev The SO post is much older than the vcpkg CI configuration.

@FrankXie05 as I understand from the stack overflow, we should update the latest headers. not update the osx nor the xcode. Can you verify that?

I will investigate it.

@talregev The SO post is much older than the vcpkg CI configuration.

How we solve this issue?
I think In the ci we have a good version of osx, and it missing additional headers that can download as they say in the SO post.
Can you verify it?

@FrankXie05 as I understand from the stack overflow, we should update the latest headers. not update the osx nor the xcode. Can you verify that?

I will investigate it.

@FrankXie05 Thank you 🙏🏻

@FrankXie05
I try to find solution for my self:
Also for find this string: `#include_next <wchar.h>"
error msg:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/__mbstate_t.h:29:
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/wchar.h:123:15: fatal error: 'wchar.h' file not found
#include_next <wchar.h>

As You can see it already point out to the new location: "/Library/Developer/CommandLineTools/"
I also try to find the wchar.h file. by command: sudo find / -name "wchar.h"
On github action it locate on /Library/Developer/CommandLineTools/SDKs/MacOSX13.1.sdk/ and mode.
Also I read these:
https://stackoverflow.com/questions/46342411/wchar-h-file-not-found
https://github.com/AcademySoftwareFoundation/OpenShadingLanguage/issues/1055
I know it need to config xcode that it will see this include, not sure how to do it.
I hop these hints will give you a good start on the investigation.

@FrankXie05 @dg0yt
It ready for review.

So it now no longer uses the same artifact names as port ogre. But do the artifacts still export the same symbols as port ogre's artifacts? Then there will be an issue with autolinking for msbuild. (AFAIU. It might be resolved by installing the artifacts to to lib/manual-link, but I'm not an expert on this.)

So it now no longer uses the same artifact names as port ogre. But do the artifacts still export the same symbols as port ogre's artifacts? Then there will be an issue with autolinking for msbuild. (AFAIU. It might be resolved by installing the artifacts to to lib/manual-link, but I'm not an expert on this.)

I am not expert as well.

For windows it install the ogreNextMain to lib/manual-link

This is typical for all those main libs which provide an implementation of the main entry point - i.e. the same symbol.
And IMO the same problem exists for ogre vs ogrenext. But I don't have MSVC, so I can't check the binary artifacts.

You probably need to expplicitly disable  OGRE_BUILD_LIBS_AS_FRAMEWORKS to make ogre-next treat Apple platforms as regular Unix platforms.

@FrankXie05 It ready for review.

@FrankXie05  any news?

The osx code needs a review on osx. I already pointed at disable OGRE_BUILD_LIBS_AS_FRAMEWORKS.
For Windows, I expect that both ogre and ogre-next libs provide the same symbols. This breaks msbuild autolinking, despite changing the name of the artifacts. So I'm afraid the ports cant be installed at the same time, on windows.

The osx code needs a review on osx. I already pointed at disable OGRE_BUILD_LIBS_AS_FRAMEWORKS. For Windows, I expect that both ogre and ogre-next libs provide the same symbols. This breaks msbuild autolinking, despite changing the name of the artifacts. So I'm afraid the ports cant be installed at the same time, on windows.

I already test OgreNext linkage on windows while Ogre already installed, and it worked.

I already test OgreNext linkage on windows while Ogre already installed, and it worked.

Did you test CMake, or did you test msbuild autolinking?

Also for osx, it already linkage other port. Not sure what are you trying to solve.

I would like to see less complexity in the portfile, and I want to ensure that transitive usage requirements are exported correctly.
Building downstream libs must succeed, but it might be an insufficient indicator: The transitive usage requirements are needed when linking executables.
For gz-rendering7, I don't know if the build used ogre-next, or simply disables related capabilities:
For gz-cmake3, this PR patches dependencies, but actually doesn't declare ogre-next as a dependency. In the CI run, it is build before ogre-next, so it can't really find it. Clear bug, shouldn't pass review.
Installing 176/195 gz-cmake3:x64-osx...
...
Installing 185/195 ogre-next:x64-osx...
...
Installing 186/195 gz-rendering7:x64-osx...

So if gz-cmake3 doesn't complain about the absence of ogre-next, what gives us confidence that gz-rendering wouldn't silently ignore ogre-next if the CMake config is broken? And I'm really afraid it is broken becuase the osx binaries are moved without updating the CMake config... I would be happy to be proven wrong.

on windows I tested it with gz-rendering7 .
for gz-rendering7 on x64-osx, it use the ogre-next also it create a specific target and pc file for it.
You can see it on the ci logs.
Before my changes on gz-cmake3 the gz-rendering7 on x64-osx didn't use ogre-next and not create the target nor the pc file.

So, my poor MBA finished the osx build. My first findigs.

There is no CMake config, but a couple of find modules and additional scripts. I don't know if they are useful.
There could be pc files but they are removed by the port.  It would be nice to have them (working).
The installation layout is framework-style, but vcpkg wants non-framework style. IMO this must be changed.

The FindGzOGRE2.cmake Is useful. This how gz-rendering7 find ogre-next in all os (linux, windows and osx).
I remove the osx pc files. it needed zziplib pc file on osx (maybe other port?), If you want to have a correct pc file for ogre-next, you can create a PR after mine, and fix the other needed pc file ports for ogre-next.

The FindGzOGRE2.cmake Is useful. This how gz-rendering7 find ogre-next in all os (linux, windows and osx).

Not installed by ogre-next.

I remove the osx pc files. it needed zziplib pc file on osx (maybe other port?),

Questionable, but someone else must decide.

The FindGzOGRE2.cmake Is useful. This how gz-rendering7 find ogre-next in all os (linux, windows and osx).

Not installed by ogre-next.

I remove the osx pc files. it needed zziplib pc file on osx (maybe other port?),

Questionable, but someone else must decide.

gz-rendering7 is a consumer. It use ogre-next.

I close the PR by mistake.

@FrankXie05 This PR is block from your side?

Can this be approved?
ogre-next:x64-osx:/debug/lib/OgreNextHlmsPbsStatic.framework/OgreNextHlmsPbsStatic
ogre-next:x64-osx:/debug/lib/OgreNextHlmsPbsStatic.framework/Resources
ogre-next:x64-osx:/debug/lib/OgreNextHlmsPbsStatic.framework/Versions/2.3.3/OgreNextHlmsPbsStatic
ogre-next:x64-osx:/debug/lib/OgreNextHlmsPbsStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/debug/lib/OgreNextHlmsPbsStatic.framework/Versions/Current
ogre-next:x64-osx:/debug/lib/OgreNextHlmsUnlitStatic.framework/OgreNextHlmsUnlitStatic
ogre-next:x64-osx:/debug/lib/OgreNextHlmsUnlitStatic.framework/Resources
ogre-next:x64-osx:/debug/lib/OgreNextHlmsUnlitStatic.framework/Versions/2.3.3/OgreNextHlmsUnlitStatic
ogre-next:x64-osx:/debug/lib/OgreNextHlmsUnlitStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/debug/lib/OgreNextHlmsUnlitStatic.framework/Versions/Current
ogre-next:x64-osx:/debug/lib/OgreNextMainStatic.framework/OgreNextMainStatic
ogre-next:x64-osx:/debug/lib/OgreNextMainStatic.framework/Resources
ogre-next:x64-osx:/debug/lib/OgreNextMainStatic.framework/Versions/2.3.3/OgreNextMainStatic
ogre-next:x64-osx:/debug/lib/OgreNextMainStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/debug/lib/OgreNextMainStatic.framework/Versions/2.3.3/Resources/ogrelogo.png
ogre-next:x64-osx:/debug/lib/OgreNextMainStatic.framework/Versions/Current
ogre-next:x64-osx:/debug/lib/OgreNextMeshLodGeneratorStatic.framework/OgreNextMeshLodGeneratorStatic
ogre-next:x64-osx:/debug/lib/OgreNextMeshLodGeneratorStatic.framework/Resources
ogre-next:x64-osx:/debug/lib/OgreNextMeshLodGeneratorStatic.framework/Versions/2.3.3/OgreNextMeshLodGeneratorStatic
ogre-next:x64-osx:/debug/lib/OgreNextMeshLodGeneratorStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/debug/lib/OgreNextMeshLodGeneratorStatic.framework/Versions/Current
ogre-next:x64-osx:/debug/lib/OgreNextOverlayStatic.framework/OgreNextOverlayStatic
ogre-next:x64-osx:/debug/lib/OgreNextOverlayStatic.framework/Resources
ogre-next:x64-osx:/debug/lib/OgreNextOverlayStatic.framework/Versions/2.3.3/OgreNextOverlayStatic
ogre-next:x64-osx:/debug/lib/OgreNextOverlayStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/debug/lib/OgreNextOverlayStatic.framework/Versions/Current
ogre-next:x64-osx:/debug/lib/OgreNextPlanarReflectionsStatic.framework/OgreNextPlanarReflectionsStatic
ogre-next:x64-osx:/debug/lib/OgreNextPlanarReflectionsStatic.framework/Resources
ogre-next:x64-osx:/debug/lib/OgreNextPlanarReflectionsStatic.framework/Versions/2.3.3/OgreNextPlanarReflectionsStatic
ogre-next:x64-osx:/debug/lib/OgreNextPlanarReflectionsStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/debug/lib/OgreNextPlanarReflectionsStatic.framework/Versions/Current
ogre-next:x64-osx:/debug/lib/OgreNextSceneFormatStatic.framework/OgreNextSceneFormatStatic
ogre-next:x64-osx:/debug/lib/OgreNextSceneFormatStatic.framework/Resources
ogre-next:x64-osx:/debug/lib/OgreNextSceneFormatStatic.framework/Versions/2.3.3/OgreNextSceneFormatStatic
ogre-next:x64-osx:/debug/lib/OgreNextSceneFormatStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/debug/lib/OgreNextSceneFormatStatic.framework/Versions/Current
ogre-next:x64-osx:/debug/lib/Plugin_ParticleFXStatic.framework/Plugin_ParticleFXStatic
ogre-next:x64-osx:/debug/lib/Plugin_ParticleFXStatic.framework/Resources
ogre-next:x64-osx:/debug/lib/Plugin_ParticleFXStatic.framework/Versions/2.3.3/Plugin_ParticleFXStatic
ogre-next:x64-osx:/debug/lib/Plugin_ParticleFXStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/debug/lib/Plugin_ParticleFXStatic.framework/Versions/Current
ogre-next:x64-osx:/debug/lib/RenderSystem_GL3PlusStatic.framework/RenderSystem_GL3PlusStatic
ogre-next:x64-osx:/debug/lib/RenderSystem_GL3PlusStatic.framework/Resources
ogre-next:x64-osx:/debug/lib/RenderSystem_GL3PlusStatic.framework/Versions/2.3.3/RenderSystem_GL3PlusStatic
ogre-next:x64-osx:/debug/lib/RenderSystem_GL3PlusStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/debug/lib/RenderSystem_GL3PlusStatic.framework/Versions/Current
ogre-next:x64-osx:/debug/lib/RenderSystem_MetalStatic.framework/RenderSystem_MetalStatic
ogre-next:x64-osx:/debug/lib/RenderSystem_MetalStatic.framework/Resources
ogre-next:x64-osx:/debug/lib/RenderSystem_MetalStatic.framework/Versions/2.3.3/RenderSystem_MetalStatic
ogre-next:x64-osx:/debug/lib/RenderSystem_MetalStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/debug/lib/RenderSystem_MetalStatic.framework/Versions/Current
ogre-next:x64-osx:/debug/lib/RenderSystem_NULLStatic.framework/RenderSystem_NULLStatic
ogre-next:x64-osx:/debug/lib/RenderSystem_NULLStatic.framework/Resources
ogre-next:x64-osx:/debug/lib/RenderSystem_NULLStatic.framework/Versions/2.3.3/RenderSystem_NULLStatic
ogre-next:x64-osx:/debug/lib/RenderSystem_NULLStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/debug/lib/RenderSystem_NULLStatic.framework/Versions/Current
...
ogre-next:x64-osx:/lib/OgreNextHlmsPbsStatic.framework/OgreNextHlmsPbsStatic
ogre-next:x64-osx:/lib/OgreNextHlmsPbsStatic.framework/Resources
ogre-next:x64-osx:/lib/OgreNextHlmsPbsStatic.framework/Versions/2.3.3/OgreNextHlmsPbsStatic
ogre-next:x64-osx:/lib/OgreNextHlmsPbsStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/lib/OgreNextHlmsPbsStatic.framework/Versions/Current
ogre-next:x64-osx:/lib/OgreNextHlmsUnlitStatic.framework/OgreNextHlmsUnlitStatic
ogre-next:x64-osx:/lib/OgreNextHlmsUnlitStatic.framework/Resources
ogre-next:x64-osx:/lib/OgreNextHlmsUnlitStatic.framework/Versions/2.3.3/OgreNextHlmsUnlitStatic
ogre-next:x64-osx:/lib/OgreNextHlmsUnlitStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/lib/OgreNextHlmsUnlitStatic.framework/Versions/Current
ogre-next:x64-osx:/lib/OgreNextMainStatic.framework/OgreNextMainStatic
ogre-next:x64-osx:/lib/OgreNextMainStatic.framework/Resources
ogre-next:x64-osx:/lib/OgreNextMainStatic.framework/Versions/2.3.3/OgreNextMainStatic
ogre-next:x64-osx:/lib/OgreNextMainStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/lib/OgreNextMainStatic.framework/Versions/2.3.3/Resources/ogrelogo.png
ogre-next:x64-osx:/lib/OgreNextMainStatic.framework/Versions/Current
ogre-next:x64-osx:/lib/OgreNextMeshLodGeneratorStatic.framework/OgreNextMeshLodGeneratorStatic
ogre-next:x64-osx:/lib/OgreNextMeshLodGeneratorStatic.framework/Resources
ogre-next:x64-osx:/lib/OgreNextMeshLodGeneratorStatic.framework/Versions/2.3.3/OgreNextMeshLodGeneratorStatic
ogre-next:x64-osx:/lib/OgreNextMeshLodGeneratorStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/lib/OgreNextMeshLodGeneratorStatic.framework/Versions/Current
ogre-next:x64-osx:/lib/OgreNextOverlayStatic.framework/OgreNextOverlayStatic
ogre-next:x64-osx:/lib/OgreNextOverlayStatic.framework/Resources
ogre-next:x64-osx:/lib/OgreNextOverlayStatic.framework/Versions/2.3.3/OgreNextOverlayStatic
ogre-next:x64-osx:/lib/OgreNextOverlayStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/lib/OgreNextOverlayStatic.framework/Versions/Current
ogre-next:x64-osx:/lib/OgreNextPlanarReflectionsStatic.framework/OgreNextPlanarReflectionsStatic
ogre-next:x64-osx:/lib/OgreNextPlanarReflectionsStatic.framework/Resources
ogre-next:x64-osx:/lib/OgreNextPlanarReflectionsStatic.framework/Versions/2.3.3/OgreNextPlanarReflectionsStatic
ogre-next:x64-osx:/lib/OgreNextPlanarReflectionsStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/lib/OgreNextPlanarReflectionsStatic.framework/Versions/Current
ogre-next:x64-osx:/lib/OgreNextSceneFormatStatic.framework/OgreNextSceneFormatStatic
ogre-next:x64-osx:/lib/OgreNextSceneFormatStatic.framework/Resources
ogre-next:x64-osx:/lib/OgreNextSceneFormatStatic.framework/Versions/2.3.3/OgreNextSceneFormatStatic
ogre-next:x64-osx:/lib/OgreNextSceneFormatStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/lib/OgreNextSceneFormatStatic.framework/Versions/Current
ogre-next:x64-osx:/lib/Plugin_ParticleFXStatic.framework/Plugin_ParticleFXStatic
ogre-next:x64-osx:/lib/Plugin_ParticleFXStatic.framework/Resources
ogre-next:x64-osx:/lib/Plugin_ParticleFXStatic.framework/Versions/2.3.3/Plugin_ParticleFXStatic
ogre-next:x64-osx:/lib/Plugin_ParticleFXStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/lib/Plugin_ParticleFXStatic.framework/Versions/Current
ogre-next:x64-osx:/lib/RenderSystem_GL3PlusStatic.framework/RenderSystem_GL3PlusStatic
ogre-next:x64-osx:/lib/RenderSystem_GL3PlusStatic.framework/Resources
ogre-next:x64-osx:/lib/RenderSystem_GL3PlusStatic.framework/Versions/2.3.3/RenderSystem_GL3PlusStatic
ogre-next:x64-osx:/lib/RenderSystem_GL3PlusStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/lib/RenderSystem_GL3PlusStatic.framework/Versions/Current
ogre-next:x64-osx:/lib/RenderSystem_MetalStatic.framework/RenderSystem_MetalStatic
ogre-next:x64-osx:/lib/RenderSystem_MetalStatic.framework/Resources
ogre-next:x64-osx:/lib/RenderSystem_MetalStatic.framework/Versions/2.3.3/RenderSystem_MetalStatic
ogre-next:x64-osx:/lib/RenderSystem_MetalStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/lib/RenderSystem_MetalStatic.framework/Versions/Current
ogre-next:x64-osx:/lib/RenderSystem_NULLStatic.framework/RenderSystem_NULLStatic
ogre-next:x64-osx:/lib/RenderSystem_NULLStatic.framework/Resources
ogre-next:x64-osx:/lib/RenderSystem_NULLStatic.framework/Versions/2.3.3/RenderSystem_NULLStatic
ogre-next:x64-osx:/lib/RenderSystem_NULLStatic.framework/Versions/2.3.3/Resources/Info.plist
ogre-next:x64-osx:/lib/RenderSystem_NULLStatic.framework/Versions/Current

@dg0yt I see you open another PR of ogre-next. feel free to fix it as you see fit.
I convert my PR to draft.

Can this be approved?

@dg0yt I see you open another PR of ogre-next. feel free to fix it as you see fit. I convert my PR to draft.

I'm confused; @dg0yt it looks like you're saying you want to merge this because it blocks your PR? /cc @talregev
This looks good to me and my comments are only extreme nitpicks not worth resetting a build over.

@BillyONeal feel free to merge this PR.

@BillyONeal feel free to merge this PR. Also feel free to commits your changes.

OK, I'm giving @dg0yt a bit to respond and will merge tomorrow if I don't hear back

I started the new PR because @talregev didn't integrate the proposed (and IMO necessary) changes such as OGRE_BUILD_LIBS_AS_FRAMEWORKS (which is alreay part of #27115), and the lack of the changes may cause more changes (or damage) to other ports.
I will continue that PR.
But I also have to deal with other ports/bugs which prevent proper testing of the port, on some platforms. (Cf. freeglut android.)
@BillyONeal I also raised this point:

For Windows, I expect that both ogre and ogre-next libs provide the same symbols. This breaks msbuild autolinking, despite changing the name of the artifacts. So I'm afraid the ports cant be installed at the same time, on windows.

Could you please help answer that question?

I already put your suggested OGRE_BUILD_LIBS_AS_FRAMEWORKS=OFF in this PR.
You can also continue to work on this PR after it will merge.

@BillyONeal I also raised this point:

For Windows, I expect that both ogre and ogre-next libs provide the same symbols. This breaks msbuild autolinking, despite changing the name of the artifacts. So I'm afraid the ports cant be installed at the same time, on windows.

Could you please help answer that question?

It seems like there is at least an attempt to allow them to coexist; I did a dumpbin /exports Ogre*.lib and out of ~10000 symbols, there are only 190 duplicates, and many of those are duplicated 'within universe'. For example, ??0HlmsBufferManager@Ogre@@QEAA@AEBV01@@Z is in both OgreNextHlmsUnlit.lib and OgreNextHlmsPbs.lib but not in any Ogre non-next libs.
It does look like there are a lot of symbols shared between OgreMeshLodGenerator.lib and OgreNextMeshLodGenerator.lib which maybe needs an inline namespace or something, but it seems upstream is at least trying to make the effort.
That all said, even if upstream made no attempt for this to work, I don't think that's a reason to block an update. It is reason to not add something and it is reason to remove something but I don't think it has effect on updates.

Thanks for the update and reviews :)


SortByColumns function

SortByColumns function implementation.
Doc: https://learn.microsoft.com/en-us/power-platform/power-fx/reference/function-sort
As a reference, check how https://github.com/microsoft/Power-Fx/pull/796. Other fixes came in place after this PR, but it is a good starting point.
Add your test cases to ../Microsoft.PowerFx.Core.Tests/ExpressionTestCases

Can be post GA


Form async validation live page is broken

If we try follow to link from
https://github.com/TinkoffCreditSystems/stapp/tree/master/examples/form-async-validation
to codesandbox.io
We unfortunately see this:

Hi, @vkhv.
Thanks for the report! Fortunately, this is already fixed in #21. We plan to merge it (and release Stapp 2.0.0, btw) tomorrow.


Website deployment on demo2.grid.tf gives error

Description
Trying to deploy a website on demo2.grid.tf, it generates an error

Version information
MacOS,
demo2.grid.tf
Browser: chrome 84

@gmachtel already done a lot of deployments since. please reopen with more details if you re-encouter this


TLS: new method to specify SSL/TLS version

SSL/TLS protocols only listed in ssl_protocols should be used.
The name "ssl_protocols" comes from nginx.
Resolves #428.
Document hasn't been updated yet.

I'd appreciate if you review this PR after next release..  Help me to improve the patch.

To know which SSL/TLS protocol is finally selected, #426 enables it.

I took your review comments, rebased to current devel head and force pushed.

I've finished this. @speidy @jsorg71, can you look at this, too?

No problem in such case. I designed the feature with old config file compatibility.
If ssl_protocols directive is not found in xrdp.ini, xrdp behaves as same as former. Only SSLv2 will be disabled.  If ssl_protocols directive is found and set to empty, all SSL protocols will be disabled.

Rebased to devel head again.

No more change requests?

OK, I think it's ready to merge.  What do you think @speidy @jsorg71 ?

If no objections in a week, I'll merge by myself.

lgtm

A week past, merged.


Error defining a list with only one element

Hi,
I'm having an issue where running conform.effective fails with the following error:
** (Protocol.UndefinedError) protocol Enumerable not implemented for {:type, 'memory'}
    (elixir) lib/enum.ex:1: Enumerable.impl_for!/1
    (elixir) lib/enum.ex:116: Enumerable.reduce/3
    (elixir) lib/enum.ex:1776: Enum.map/2
    (elixir) lib/enum.ex:1229: Enum."-map/2-lists^map/1-0-"/2
    lib/conform/translate.ex:132: anonymous fn/6 in Conform.Translate.convert_types/2
    (elixir) lib/enum.ex:1755: Enum."-reduce/3-lists^foldl/2-0-"/3
    lib/conform/translate.ex:129: Conform.Translate.convert_types/2
    lib/conform/translate.ex:95: Conform.Translate.apply_schema/2

The issue happens when I have a list of {:atom, :binary} and the list has only one element. My current work-around is to add another dummy element that I ignore.
I am running the latest versions of conform (2.2.2) and distillery (1.2.2) and the relevant section of my schema / config are:
"evl_daemon.storage_engines": [
  commented: false,
    datatype: [
      list: [list: {:atom, :binary}]
    ],
    default: [
      [type: "memory", maximum_events: "100"]
    ],
    doc: "Enabled storage engines and their options.",
    hidden: false,
    to: "evl_daemon.storage_engines"
],

The relevant entry in the config file is:
evl_daemon.storage_engines = [type = "memory", maximum_events = "100"]

Am I doing something wrong in my schema which is triggering this issue?

This looks similar to issue #68

@zaid I'll take a look at this first thing tomorrow. Thanks for the report!

I've got this fixed locally, just addressing some other outstanding issues before pushing a new release :)

Perfect! I'll test it as soon as you push your changes. Thank you for fixing this so fast 👍

I've pushed the fixes to master, could you give it a shot?

I just gave it a quick test and it is giving me a different error now:
** (Conform.Translate.TranslateError) Invalid value for evl_daemon.zones: Expected value of type `:binary`, got ['[1', 'Front door', ']', '[2', 'Garage door', ']', '[3', 'Basement door', ']', '[4', 'Kitchen door', ']', '[5', 'Office motion sensor', ']', '[6', 'Family room motion sensor', ']', '[7', 'Basement glass break sensor', ']', '[8', 'Basement motion sensor', ']']
    lib/conform/translate.ex:328: Conform.Translate.parse_datatype/3
    lib/conform/translate.ex:145: anonymous fn/6 in Conform.Translate.convert_types/2
    (elixir) lib/enum.ex:1755: Enum."-reduce/3-lists^foldl/2-0-"/3
    lib/conform/translate.ex:142: Conform.Translate.convert_types/2
    lib/conform/translate.ex:108: Conform.Translate.apply_schema/2
    lib/conform/translate.ex:84: Conform.Translate.to_config/3
    lib/mix/tasks/conform.effective.ex:106: Mix.Tasks.Conform.Effective.do_run/1
    (mix) lib/mix/task.ex:294: Mix.Task.run_task/3

The config file that I tested with can be found here
The schema file can be found here
The entry that it is failing on is parsed using a transformer so I'm wondering if the reason for failure is because of that (since I don't explicitly define the datatype in the mapping section).

Ok, you should be good to go on master now, can you confirm before I cut a new release?

I'm still having an error when it tries to parse evl_daemon.zones. Here is the error message:
** (Conform.Translate.TranslateError) Invalid value for evl_daemon.zones: Expected value of type `:binary`, got [['1', 'Front door'], ['2', 'Garage door'], ['3', 'Basement door'], ['4', 'Kitchen door'], ['5', 'Office motion sensor'], ['6', 'Family room motion sensor'], ['7', 'Basement glass break sensor'], ['8', 'Basement motion sensor']]
    lib/conform/translate.ex:328: Conform.Translate.parse_datatype/3
    lib/conform/translate.ex:145: anonymous fn/6 in Conform.Translate.convert_types/2
    (elixir) lib/enum.ex:1755: Enum."-reduce/3-lists^foldl/2-0-"/3
    lib/conform/translate.ex:142: Conform.Translate.convert_types/2
    lib/conform/translate.ex:108: Conform.Translate.apply_schema/2
    lib/conform/translate.ex:84: Conform.Translate.to_config/3
    lib/mix/tasks/conform.effective.ex:106: Mix.Tasks.Conform.Effective.do_run/1
    (mix) lib/mix/task.ex:294: Mix.Task.run_task/3

My mix.lock shows the following entry for conform:
"conform": {:git, "https://github.com/bitwalker/conform.git", "facff314c16436228134e044a41c54fc0648dbc0", []},

Let me know if I'm doing something wrong.

Oh sorry, could you look in the test/schemas/evl_daemon.schema.exs file? You'll see the change I had to make to the mappings/transforms for that and the partitions option. Transforms are executed after mappings are done, so you have to define a valid datatype for the initial value, even if you transform it into something totally different later.

Oh that explains it. I just made the same changes and verified that conform.effective is returning the expected results.
Thank you for fixing this 👍


Updade app.py

Self-esducation propose

@JoseEvongo you need to clone this repo and make changes to your repo. This repo is master repo and cannot be modified. Please make changes to your own github repo which is cloned from this repo.


Error: No "exports" main defined in package.json

Describe the bug
Unable to run tests. Getting the following error Error: No "exports" main defined in /home/madhank/Desktop/git/learn-dsa/node_modules/vitest/package.json
Stack trace:
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  bin/src/data-structures/single-linked-list/single-linked-list.spec.js [ bin/src/data-structures/single-linked-list/single-linked-list.spec.js ]
Error: No "exports" main defined in /home/madhank/Desktop/git/learn-dsa/node_modules/vitest/package.json
 ❯ src/data-structures/single-linked-list/single-linked-list.spec.ts:1:0

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
RangeError: Invalid count value
 ❯ generateCodeFrame node_modules/vitest/dist/chunk-vite-node-externalize.0791f2ed.mjs:10294:35
 ❯ node_modules/vitest/dist/chunk-vite-node-externalize.0791f2ed.mjs:10168:50
 ❯ printStack node_modules/vitest/dist/chunk-vite-node-externalize.0791f2ed.mjs:10258:32
 ❯ printError node_modules/vitest/dist/chunk-vite-node-externalize.0791f2ed.mjs:10163:3
 ❯ processTicksAndRejections node:internal/process/task_queues:96:5
 ❯ DefaultReporter.printTaskErrors node_modules/vitest/dist/chunk-vite-node-externalize.0791f2ed.mjs:7488:7
 ❯ DefaultReporter.reportSummary node_modules/vitest/dist/chunk-vite-node-externalize.0791f2ed.mjs:7434:7
 ❯ DefaultReporter.onFinished node_modules/vitest/dist/chunk-vite-node-externalize.0791f2ed.mjs:7293:5
 ❯ DefaultReporter.onFinished node_modules/vitest/dist/chunk-vite-node-externalize.0791f2ed.mjs:7627:5

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in /home/madhank/Desktop/git/learn-dsa/node_modules/vitest/package.json
    at new NodeError (node:internal/errors:372:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:472:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:693:7)
    at resolveExports (node:internal/modules/cjs/loader:482:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:919:27)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/home/madhank/Desktop/git/learn-dsa/src/data-structures/single-linked-list/single-linked-list.spec.ts:1:1) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Reproduction
Repo - https://github.com/madhank93/learn-dsa and run the command npm run test
System Info
System:
    OS: Linux 5.14 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz
    Memory: 9.78 GB / 15.40 GB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Browsers:
    Chrome: 103.0.5060.134
    Firefox: 103.0
  npmPackages:
    vitest: ^0.18.0 => 0.18.0

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

We managed to silence the error by removing this line:
https://github.com/vitest-dev/vitest/blob/main/packages/vitest/package.json#L28

@yacinehmito Upgrading the package didn't work for me as well. So I delete the entire repo and cloned it again. Not sure this is the right thing to do.

On our end, the culprit was eslint-import-resolver-alias. Its last version is 4 years old, at a time where ESM support was not a topic.
Node's resolution logic assumes that it's running in CommonJS, so it was looking for a require field in the relevant export in package.json. There was none, so it crashed with this error.
We fixed the problem by using eslint-importe-resolver-customer-alias, which is more recent and specifies to Node's resolver that ESM is used, so that it looks at the import field instead.

I was having similar issues, error messages like that:
1:1   error    Resolve error: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in /home/fthebaud/Workspace/de.idnow.vi.web.frontend/node_modules/vitest/package.json
    at new NodeError (node:internal/errors:371:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:453:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:671:7)
    at resolveExports (node:internal/modules/cjs/loader:482:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
    at findModulePath (/home/fthebaud/Workspace/de.idnow.vi.web.frontend/node_modules/eslint-import-resolver-alias/index.js:99:27)
    at Object.exports.resolve (/home/fthebaud/Workspace/de.idnow.vi.web.frontend/node_modules/eslint-import-resolver-alias/index.js:75:10)
    at v2 (/home/fthebaud/Workspace/de.idnow.vi.web.frontend/node_modules/eslint-module-utils/resolve.js:116:23)
    at withResolver (/home/fthebaud/Workspace/de.idnow.vi.web.frontend/node_modules/eslint-module-utils/resolve.js:121:14)
    at fullResolve (/home/fthebaud/Workspace/de.idnow.vi.web.frontend/node_modules/eslint-module-utils/resolve.js:138:22)  import/namespace

As suggested by @yacinehmito, replacing eslint-import-resolver-alias by the more recent eslint-import-resolver-custom-alias fixed the problem.


Plugin doesn't work with a VTT files using windows line endings

Using windows line endings \r\n in the VTT file causes the plugin to not parse correctly.  Either the documentation should be updated to specify that only UNIX line endings "\n" or "\r" are supported or the split regex data.split(/[\r\n][\r\n]/i);  should be modified to support \r\n line endings.
I could send a PR for the data.split regex if you are open to it.

Changing the processVtt method to look for \r\n first using (\r\n){2} and then if none are found, using the current regex should work while still being backward compatible.

This module sucks I can't believe this is 'the best videojs has to offer' in terms of vtt sprite support

You're right @k-harker
https://www.w3.org/TR/webvtt1/#webvtt-line-terminator
A WebVTT line terminator consists of one of the following:

A U+000D CARRIAGE RETURN U+000A LINE FEED (CRLF) character pair.
A single U+000A LINE FEED (LF) character.
A single U+000D CARRIAGE RETURN (CR) character.

@mayeaux please...


OCM. Prevent federated users from being added as members of the space

Version 6.3.0
web 10.2.0
ocm setup, see here https://owncloud.dev/ocis/development/testing/#running-test-suite-with-federated-sharing-ocm
Steps:

user creates space and tries to add external user as member

Expected: 403 Forbidden
Actual:
curl -k -X POST 'https://ocis-server:9200/graph/v1beta1/drives/space_uuid/root/invite' -u admin:admin -d '{"roles":["a8d5fe5e-96e3-418d-825b-534dbdf22b99"],"recipients":[{"objectId":"external_user_uuid: ","@libre.graph.recipient.type":"user"}]}' -v
gets 200 OK - but user hasn't access to space

Related issue https://github.com/owncloud/web/issues/11579

need also prevent adding members to space using "https://ocis-server:9200/graph/v1beta1/drives/spaceUUID/items/spaceUUID/invite" endpoint
added test apiOcm/share.feature:231 and linked issue


Detecting exposed ports in images

One of the issues I'm constantly facing when using Kompose with various docker-compose files is that they don't always specify port. With docker-compose this is not an issue but, for Kompose it is as we need to create service for every exposed port.
We should investigate if it is possible to get exposed ports from image metadata without downloading image itself. Or maybe if there is some other solution for this.

So I looked into this a bit.
Lost of images do not have an exposed port, as you can reach a containerized service on any port even it is not 'EXPOSED'.
So even if we could introspect an image from a repo to figure out the EXPOSE, it may not even have one.
Case in point, the carts image form the sock shop example:
https://github.com/microservices-demo/carts/blob/master/Dockerfile
So I think we gonna have to create services with empty ports :( that will need to be edited by hand.

yeah that's a problem, as we need a port to create a service. Not sure how to solve this.
We can create a basic service set port to "1" but it won't work.

You are right. I forgot that when they are on the same network it doesn't mater what is in EXPOSE. :-(.
There is one solution that would probably work, but it is really ugly. We can generate Service with  all 65536 ports :laughing:

There is one solution that would probably work, but it is really ugly. We can generate Service with all 65536 ports :laughing:

yeah. that could be our last resort. we could do this by default and then warn the user about this and tell them to either add port definition to docker compose file or edit the generated artifacts to put in the correct port.

that's pretty much impossible. afaik there is no wildcard for service ports in services. So that would mean creating 65k entries in the port definition of the service (so ugly). Plus pretty sure the proxy would run out of file descriptors somewhere, since it needs to listen on those ports...

You can create a headless service (clusterIP: "None") and you should not be required to define ports.

but DNS won't work ?

DNS works for headless services.

try this with a headless service:
apiVersion: v1
kind: Service
metadata:
  labels:
    app: sockshop
  name: front-end
spec:
  clusterIP: None
  ports: null
  selector:
    service: front-end

But the endpoint does not seem to get set with the Pod IP matching the selector. Hence no DNS.
I will keep looking into it.

I have made a fix for this in https://github.com/skippbox/kompose/pull/148/commits/96493a5527bfc6b43e90e76feb39e2efb6f9333b
We need to use a "dummy" port in the headless service creation, otherwise the endpoint does not get populated and DNS entries do not get created.

@runseb how about having a separate PR for this particular thing, rather than having it embedded in the "Socks Shop example"?

@surajssd ok, I broke things up. #157 addresses the headless service alone.

@sebgoa thanks :+1:

@kadel https://github.com/kubernetes-incubator/kompose/pull/157 has been merged, would this be closed?

@cdrage yes this can be closed.


Merge ByteArrayComparers

Description of Changes
There were couple of mismatched implementations of byte array comparison / hashing. This PR simply keeps the most efficient one as a utility and forwards all the usages to it.
API

[ ] This is an API breaking change to the SDK

If the API is breaking, please state below what will break
Requires SpacetimeDB PRs
List any PRs here that are required for this SDK change to work

@jdetter Was a bit concerned because this is touching performance-sensitive code and wanted to test it with Bitcraft, so leaving open until his approval.


Can I use system-context-menu while clicking some special target?

I use ui.bootstrap.contextMenu for a html.
While I'm click something special, I want use system-context-menu instead of ui.bootstrap.contextMenu.
I knew that I can identify which target to use different contextMenu by using $event.target.
I tried contextMenuOptions return null or false, but it return to me a blank contextMenu, not `system-context-menu.

What params should be used for switch between system-context-menu and ui.bootstrap.contextMenu?

There's currently no way to specify when to turn it off. However, you can try adding something like:
event.stopPropagation();
event.preventDefault();

to the element containing system-context-menu. Just make sure that the event already has reached system-context-menu before you stop propagation. If you provide a plunkr I might be able to help a bit more.
This is really outside the scope of this project, so I'll be closing this unless there's a good reason not to.


No Related Persons warning not showing actual text

🐛 Bug Report
The No Related Persons warning text is showing the internationalization keys rather than the actual text.
To Reproduce

Navigate to a patient with no related persons
See that the no related persons warning does not have the proper text

Paste your code here:
Expected behavior
It should have the proper text.

I would like to take this.

Hello I created a PR that would fix this.
https://github.com/HospitalRun/hospitalrun-frontend/pull/1905
please feel free to comment on it.
thanks

Hi, @rubencgt thanks for your contribution :) To avoid making other people work for nothing, as written here, we always recommend waiting for the assignment. PR is fine anyway.
@Brahyt thank you for your helpfulness!!

No worries, always excited to help OSS.

@tehKapa @Brahyt  as this is my PR I didn't know how it works.
next time it wont happen, apologies for the miss-understanding


Remove stop from response

Closes #113

This doesn't affect streaming, so I did not change the streaming example.
String stop sequences will not work while streaming. We might want to skip sending finish tokens though?

I think this looks good. If you could open another PR to remove stop tokens from streaming requests that would be great!


[Question] Hide Prev/Next buttons option

Is it possible to hide Prev/Next buttons when the slide reaches the first/last image?
By hiding these buttons we let know the visitor it is the end of the slide. I am not using loops because this feature creates confusion. Not all people realize when is the end of a slide.

You can write a little code to compare  getCurrentSlideCount() against getTotalSlideCount(). If they are equal that means the last slide is reached. If getCurrentSlideCount()  = 1 then that pretty much tells you that it's the first slide.


Update NEAR logo

https://near.org/downloads/NEAR_PressKit.zip

[ ] Logo in the top Left corner (Desktop layout of Explorer)
[ ] Logo in the top Left corner (Mobile layout of Explorer)
[ ] Favicon

I think it is black one and not white one.

since we are going to implement new home page next week, and this is included, I do not think it is good to do so.


chore(deps): update terraform terraform-ibm-modules/secrets-manager/ibm to v1.12.4

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/secrets-manager/ibm (source)
module
minor
1.11.0 -> 1.12.4

Release Notes

terraform-ibm-modules/terraform-ibm-secrets-manager (terraform-ibm-modules/secrets-manager/ibm)
v1.12.4
Compare Source
Bug Fixes

add validation for resource group in a case existing SM CRN is not set (#113) (95afb00)

v1.12.3
Compare Source
Bug Fixes

update the DA reference architecture diagram (#111) (647b18a)

v1.12.2
Compare Source
Bug Fixes

fix kms reference error when sm crn is set (#112) (e83d417)

v1.12.1
Compare Source
Bug Fixes

do not create kms key if existing SM instance is passed (#110) (6b4d74f)

v1.12.0
Compare Source
Features

add support to use existing Secrets Manager instance in the DA solution (#109) (1bfd5e1)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Backport v2.4.1 features

(Draft)

Self-review by comparing diffs -> looks good, tests pass; merging.


[FEA] Add Nan handling in GpuArrayMin

Is your feature request related to a problem? Please describe.
This is a subtask of #5320
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context, code examples, or references to existing implementations about the feature request here.

Blocked by https://github.com/rapidsai/cudf/issues/11530

If we can remove the hasNaNs config altogether, we can close issue #6332 without fixing it.


Any document on how to use Mqttnet.Extensions.Rpc

Describe your question
Is there some documents or sample code to show how to make rpc working ? thank you very much !

Please see RpcClient_Samples in the Samples directory.


Too many different instances in Birch Forest (and only there)

Hey there! First of all: great dataset, congrats!
I'm trying to do some instance segmentation but I noticed that the Birch Forest has up to 2522 different instances on some images.

I've seen that the other scenes don't have this problem, probably you just forgot to "cut" the instances to 256, correct?

So I was wondering what the correct approach to use the Birch Forest with other scenes could be. Probably it's sufficient to just extract the unique classes with numpy and have the frequencies returned as well, cutting the array to 256. After that, one can copy to a new image only the pixels that correspond to one of the 256 most frequent colors. Does this make sense or is there a much easier way?
Thanks!

Hi, thanks for reaching out! In fact, I have encountered similar situations before. I suspect this might be related to some APIs of AirSim, the simulator we use for collecting labeled data. However, I previously resolved it in the following way:
First, you should be able to find a color_palette.xlsx file on Zenodo. This file contains information about up to 255 RGB values within the scene. You can read the RGB information as follows:
color_palette_path = "color_palette.xlsx"
color_palette = pd.read_excel(color_palette_path)  # 4 cols: Index, R, G, B
# take RGB
color_palette = color_palette.iloc[:, 1:].values
# to list
valid_rgb_values = color_palette.tolist()

Then, you can filter out the pixel that are not in valid_rgb_values, which will give you a very clean labeled image containing at most 255 RGB values. I hope this helps!

You're right, totally forgot about that file... I'll try, thanks!


Fix broken hashCode for Json values

This is a very old bug (around since #16) that finally started causing problems for @pvillega in #141.
Removing the hashCode definition means each case class will have its own generated hashCode that will be consistent with the equals on Json.
This seems to fix the issue, but I really wish we had tests in place for this kind of thing.

Current coverage is 74.64%

Merging #142 into master will increase coverage by +0.14% as of 9909132

Powered by Codecov. Updated on successful CI builds.


pythonPackages.optree: init 0.11.0

Description of changes
Optimized PyTree Utilities
Closes https://github.com/NixOS/nixpkgs/issues/310612
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

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

4 packages built:

python311Packages.optree
python311Packages.optree.dist
python312Packages.optree
python312Packages.optree.dist

Since this is a missing dependency in keras that causes an error, I think I'll add the automatic backport label.

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

4 packages built:

python311Packages.optree
python311Packages.optree.dist
python312Packages.optree
python312Packages.optree.dist


fix: reduce bundle size by limiting external dependencies

I removed external dependency of flux-standard-action that includes entire loadash with it when imported. Instead, I re-implemented single function we are using and relied on single modules from loadash that are required. Should reduce the size significantly
resolves #273

This may be a duplicate of
https://github.com/klarna/electron-redux/pull/204

:tada: This PR is included in version 2.0.0-alpha.3 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Training of TecoGAN hasn't been verified

Hi, I tried to train and test the TecoGAN model, but it doesn't seem to be supported. Have you completed this part?

The TecoGAN networks and training are implemented followed by the original paper. But the hyper-parameters are not tuned so the training will not converge.
Now the author open-sourced his codes including training script. You can refer his code


[Feature] add plugin.jdbc.trace_sql_parameters into agent CDS

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Add plugin.jdbc.trace_sql_parameters into agent CDS.
Use case
Sometimes don't want to change the agent config and restart the application to see the sql parameter. Add  plugin.jdbc.trace_sql_parameters into agent CDS make it can be changed dynamic.
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@zhyyu Are you working on this?

@zhyyu Are you working on this?

Yes, I am working on it. I meet some classloader issue, org.apache.skywalking.apm.plugin.jdbc.JDBCPluginConfig.Plugin.JDBC is loaded by two different AgentClassLoader . I am finding out the reason.

I write a  JDBCPluginDynamicConfigService BootService register the watcher change the config, but business thread use another classloader to see JDBCPluginConfig.Plugin.JDBC.TRACE_SQL_PARAMETERS, so the watcher don't work..

I think you don't need a service,  you should have a watcher(AgentConfigChangeWatcher). Have you checked this?

AgentConfigChangeWatcher

I create a new bootservice and watcher in jdbc-commons package. If i do not create a new  service, can I reuse ContextManagerExtendService or other existed bootservice to register my new warcher?

Why do you make things so complex? You just need a watcher, and when the JDBC plugin is intercepting Driver initialization, you register this into the kernel, then you could have everything you need.

You don't need bootservice. DCS has a kernel level service already.


On OpenBSD  "system monitor"  has mem & cpu usage at 0%

As per the subject, the System Monitor is showing 0% for both the CPU Usage and the Mem Usage. Additionally, the CPU Temp field is blank. The Disk IO panel is also blank.
This is on OpenBSD 6.2 stable, lumina installed from ports (version 1.3.0). Thinkpad T400.

That is expected.
The OS support system for OpenBSD has not had the CPU/Memory routines defined or setup by an OpenBSD user/developer yet:
(See the chart of OS support capabilities)
If you would like to fill in that missing functionality, it is just a single file with a couple lines per function in our source tree:
https://github.com/trueos/lumina/blob/master/src-qt5/core/libLumina/LuminaOS-OpenBSD.cpp
There are four functions total at the bottom of the file (lines 250 -> 264) which will need to be filled in to enable reading that data on OpenBSD.
If you want to see an example of how we do it on FreeBSD, you can look HERE. For FreeBSD it is mostly just reading sysctl's, but it uses iostat to get the disk read/write activity.

I'll take a look this weekend.  We upgraded our version of qt with the
latest release this week so I'll want to build the media player as
well.
On Fri, 2017-10-13 at 13:31 +0000, Ken Moore wrote:

That is expected.
The OS support system for OpenBSD has not had the CPU/Memory routines
defined or setup by an OpenBSD user/developer yet:
(See the chart of OS support capabilities)
If you would like to fill in that missing functionality, it is just a
single file with a couple lines per function in our source tree:
https://github.com/trueos/lumina/blob/master/src-qt5/core/libLumina/L
uminaOS-OpenBSD.cpp
There are four functions total at the bottom of the file (lines 250
-> 264) which will need to be filled in to enable reading that data
on OpenBSD.
If you want to see an example of how we do it on FreeBSD, you can
look HERE. For FreeBSD it is mostly just reading sysctl's, but it
uses iostat to get the disk read/write activity.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c5
5493e4bb","name":"GitHub"},"entity":{"external_key":"github/trueos/lu
mina","title":"trueos/lumina","subtitle":"GitHub
repository","main_image_url":"https://cloud.githubusercontent.com/ass
ets/143418/17495839/a5054eac-5d88-11e6-95fc-
7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent
.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-
b52498112777.png","action":{"name":"Open in GitHub","url":"https://gi
thub.com/trueos/lumina"}},"updates":{"snippets":[{"icon":"PERSON","me
ssage":"@beanpole135 in #480: That is expected.\r\n\r\nThe OS support
system for OpenBSD has not had the CPU/Memory routines defined or
setup by an OpenBSD user/developer yet: \r\n(See the chart of OS
support capabilities)\r\n\r
nIf you would like to fill in that missing functionality, it is just
a single file with a couple lines per function in our source tree:
\r\nhttps://github.com/trueos/lumina/blob/master/src-qt5/core/libLumi
na/LuminaOS-OpenBSD.cpp\r\n\r\nThere are four functions total at the
bottom of the file (lines 250 -\u003e 264) which will need to be
filled in to enable reading that data on OpenBSD.\r\nIf you want to
see an example of how we do it on FreeBSD, you can look [HERE](https:
//github.com/trueos/lumina/blob/master/src-
qt5/core/libLumina/LuminaOS-FreeBSD.cpp). For FreeBSD it is mostly
just reading sysctl's, but it uses iostat to get the disk
read/write activity."}],"action":{"name":"View Issue","url":"https://
github.com/trueos/lumina/issues/480#issuecomment-336453121"}}}


3rd party libs synched with official builds?

Are the third party Windows libraries we are distributing under
Documentation/Downloads
the same ones we've used to build our release?

Yes, they've been updated.