Please contact support :)

Great work man!.
First I want to share some modification that I did. ` async def handle_prompt(self, prompt_text):
    # Get the dialog element
    dialog = await self.page.querySelector('div[role="dialog"]')

    if dialog:
        # Get all the link elements
        links = await dialog.querySelectorAll('a')

        for link in links:
            # Get the link text
            link_text = await self.page.evaluate('(element) => element.textContent', link)

            if link_text == 'Stay logged out':
                print('Found a link with text "Stay logged out"')
                await link.click()
                await asyncio.sleep(0.5)

    prompt_textarea = await self.page.querySelector('#prompt-textarea')
    if prompt_textarea is None:
        print("Cannot find the prompt input on the webpage.\nPlease check whether you have access to chat.openai.com without logging in via your browser.")
        self.session_active = False
        await self.close()
        return

    try:
        # await self.page.type('#prompt-textarea', prompt_text, {'delay': 3})
        # await self.page.type('#prompt-textarea', prompt_text, {'delay': 1})
        await self.page.type('#prompt-textarea', random.choice(string.ascii_letters))
        await self.page.evaluate(f"() => {{document.querySelector('#prompt-textarea').value = '{prompt_text}';}}")
        await asyncio.sleep(5)`    I'm testing with visible browser so '''Stay logged out''' popup might not come when you work windowless mode. Second thing is typing letter by letter for larger prompt last forever so I type one char to make submit btn enabled and then paste the text.  I saw you change the browser test lib from pypeteer to playwright, but unfortunately both stop to work. I think they done extra protection or some kind of ban. Although normal browser window works just fine.

** I tried with Tor browser same thing. They have some kind of protection. Cloud.... get into verification loop even I"m checking I'm human.

Hey Alex,
thanks a lot for your feedback!
Sorry for the late response, I've been pretty busy lately (just saw your email as well).
I'll look into it and get back to you 😊

Any updates?


Why does the checkbox gets disappeared when we use the "Toggle device toolbar"?

Why does the checkbox gets disappeared when we use the "Toggle device toolbar"?

Current Behavior
Currently I am using customToolbarselect and whenever I shrink the window to look like a mobile device by using the "Toggle device toolbar" the checkboxes get disappeared? Is there anything that I forgot to mention in the options?

Tech
Version

Material-UI
latest

MUI-datatables
latest

React
latest

browser
chrome

etc

seems like the checkbox column should especially show when options.responsive: true


Update test commands

Description
Currently, running $ yarn test --browsers=Chrome --grep='multinomial' don't filters tests.
The syntax to use to pass arguments to the package script running with yarn (run) has changed.
Because of this, the arguments that are passed to the yarn test which is posted in DEVELOPMENT.md are not applied to the karma start command.
So I updated the command to match the new syntax.
Please refer to the issue below
https://github.com/yarnpkg/yarn/issues/1667

For repository owners only:
Please remember to apply all applicable tags to your pull request.
Tags: FEATURE, BREAKING, BUG, PERF, DEV, DOC, SECURITY
For more info see: https://github.com/tensorflow/tfjs/blob/master/DEVELOPMENT.md

This change is

Which version of yarn are you using?
With yarn -v I get 1.5.1.
When I run this I get the following message:
warning From Yarn 1.0 onwards, scripts don't require "--" for options to be forwarded. In a future version, any explicit "--" will be forwarded as-is to the scripts.

In the issue that you linked, the user is using yarn version 0.16.1.

One fix could be to specify a minimum yarn version in the 'engines' entry of our package.json https://yarnpkg.com/en/docs/package-json#toc-engines. We could try >= 1.4.0 as a start.

@nsthorat You're right. My yarn version was outdated. I updated yarn to v1.5.1 and not it works like a magic. So I got the test commands back.
@tafsiri I think that is good idea to specify minimum yarn version. So I done that on last commit.

The travis CI's yarn version is v1.3.2 so I lower the minimum yarn version in the 'engines' entry to fix the error on CI.


Exploratory Analysis of Models on Hub

Using the huggingface_hub library, I was able to collect some statistics on the 9,984 models that are currently hosted on the Hub. The main goal of this exercise was to find answers to the following questions:

How many model architectures can be mapped to tasks that we wish to evaluate? For example a model with the BertForSequenceClassification architecture is likely to be about text classification; similarly for the other ModelNameForXxx architectures.
How many models have an architecture, dataset, and metric in their metadata?
Which tasks are most common?

Number of models per dimension
Without applying any filters on the architecture names, the number of models per criterion is shown in the table below:

Has architecture
Has dataset
Has metric
Number of models

✅
❌
❌
8129

✅
✅
❌
1241

✅
✅
✅
359

These numbers include models for which a task may not be easily inferred from the architecture alone. For example BertModel would presumably be associated with a feature-extraction task, but these are not simple to evaluate.
By applying a filter on the architecture name to contain any of "For", "MarianMTModel" (translation), or "LMHeadModel" (language modelling), we arrive at the following table:

Has task
Has dataset
Has metric
Number of models

✅
❌
❌
7452

✅
✅
❌
1150

✅
✅
✅
337

Architecture frequencies
Some models either have no architecture (e.g. the info is missing from the config.json file or the model belongs to another library like Flair), or multiple ones:

Number of architectures
Number of models

0
1755

1
8125

2
1

3
3

Based on these counts, it thus makes sense to just focus on models with a single architecture.
Number of models per task
For models with a single architecture, I extract the task names from the architecture name according to the following mappings:

"MarianMTModel" => "Translation"
architectures containing "LMHeadModel", "LMHead", "MaskedLM", "CausalLM" => "LanguageModeling"
architectures containing "Model", "DPR", "Encoder" => "Model"

The resulting frequency counts are shown below:
LanguageModeling                    3250
Translation                         1354
SequenceClassification               829
ConditionalGeneration                766
Model                                655
QuestionAnswering                    364
CTC                                  318
TokenClassification                  286
PreTraining                          163
MultipleChoice                        37
MultiLabelSequenceClassification      17
ImageClassification                   15
MultiLabelClassification              11
Generation                             7
ImageClassificationWithTeacher         4

Fun stuff
We can visualise which tasks are connected to which datasets as a graph. Here we show the top 10 tasks (measured by node connectivity) with the top 20 datasets marked in orange

thanks to a tip from @osanseviero and @julien-c, i can improve the analysis by making use of ModelInfo.pipeline_tag to infer the tasks. i'll update the analysis with this improved mapping

Using the ModelInfo approach suggested by @osanseviero and @julien-c makes the analysis much simpler :)
Breakdown by task
First, the pipeline_tag already contains the task information and provides a more realistic grouping of the model architectures:
pipeline_tag        number_of_models
====================================
unknown                         2394
text-generation                 2286
translation                     1373
fill-mask                        958
text-classification              860
text2text-generation             748
question-answering               368
automatic-speech-recognition     329
token-classification             324
summarization                    228
conversational                    32
image-classification              22
audio-source-separation           19
table-question-answering          19
text-to-speech                    17
zero-shot-classification          17
feature-extraction                 8
object-detection                   5
voice-activity-detection           3
image-segmentation                 3
Semantic Similarity                2
sentence-similarity                2

We can see there are two similar-looking tasks: Semantic Similarity and sentence-similarity. By looking at the corresponding model IDs in the table below, we can see that they appear to be models produced using sentence-transformers

model_id

Sahajtomar/french_semantic

Sahajtomar/sts-GBERT-de

osanseviero/full-sentence-distillroberta2

osanseviero/full-sentence-distillroberta3

Suggestion: rename Sentence Similarity to sentence-similarity to match the naming convention of pipeline tags
Drilling down on the unknown pipeline tags
We can see 2,394 models are currently missing a pipeline tag, which is about 24% of all the models currently on the Hub:

has_pipeline_tag
num_models

True
7623

False
2394

Of the models without a pipeline tag, we can drill down further by asking how many of them have a config.json file:

Interestingly, the list of model IDs with a pipeline tag but no config.json file includes models like distilbert-base-uncased, for which an architecture field probably did not exist when this model was trained.
A list of the model IDs is attached.
2021-06-04_models-without-pipeline-tag-with-config.csv

Thanks for the analysis!
re: Semantic similarity. The user overrode the pipeline tag in the METADATA some months ago. I agree that they should be sentence-similarity, which is a fairly recent task.
Some brainstorm ideas for further analysis:
re: If I understand correctly, we have 2394 repos without a pipeline tag and we might want to put some effort on those. From those repos:

1253 have a config.json. Is there anything we can obtain from the config to understand what they are? (unrelated: I think we assume that these are Transformer based, so maybe it also makes sense to add transformers tag, which we currently don't use at the moment.)
Not necessarily useful, but it might also be worth classifying the ones without a config and without a pipeline tag. We could check if 1. the repos are empty; 2 the repo has a file that could correspond to another library; etc. This might be more challenging though.

we currently assume (see code in ModelInfo.ts, it's fairly short to read) that models that have a config.json file and no library name in their tags is a transformers model.
Lots of model repos are empty (or WIPs) so I wouldn't aim to classify all models.

PS/ fixed the metadata for one model in https://huggingface.co/Sahajtomar/french_semantic/commit/2392beb954ae32dafa587e03f278a0158d1da7b5

and the other in https://huggingface.co/Sahajtomar/sts-GBERT-de/commit/935c5217fd8f03de0ccd9e6e3f34e21651573e84

pytorch unneeded as it's inferred from the files
task name can be in tags and will be inferred as the pipeline type
Fixed the library name (can also be in tags)

Finally, cc'ing model author @Sahajtomar for visibility. Let us know if any issue 🙂

we currently assume (see code in ModelInfo.ts, it's fairly short to read) that models that have a config.json file and no library name in their tags is a transformers model.

Yes, I was suggesting that maybe we should make it more explicit and add the transformers tag to those. As we intend to expand our usage to more libraries, longer-term I think we should reduce the magic that happens in our side, and have transformers as an explicit tag. (related PR https://github.com/huggingface/moon-landing/pull/746)

Yes agreed, probably not short term but when we start adding more validation to the yaml block in models we can 1/ add this rule 2/ update all updateable models on the hub

while checking for suitable datasets for model evaluation, i discovered several models have typos / non-conventional naming for the datasets: tag.
using some fuzzy string matching i compiled a list of (model, dataset, closest_dataset_match) where the closest match to a canonical dataset in datasets was based (arbitrarily) on whether the levenstein distance is > 85.
i wonder whether it would be useful to include some sort of validation in the yaml, along the lines of "did you mean dataset X?" where X is one of the datasets hosted on the hub?
non-canonical-datasets.csv

i wonder whether it would be useful to include some sort of validation in the yaml, along the lines of "did you mean dataset X?" where X is one of the datasets hosted on the hub?

Yes 👍
Also check out https://observablehq.com/@huggingface/kaggle-dataset-huggingface-modelhub from @severo which looks great (cc @gary149)


feat: The Cell Count chart data is abnormal

issues：https://github.com/Magickbase/ckb-explorer-public-issues/issues/318
The result obtained by adding live cells and dead cells together is not accurate when displayed on the chart as "all cells". Therefore, we should update the chart to change it to have three labels (live, dead, all).

Please have a review @FrederLu @silySuper @littleLip520

After seeing the Cell Count table, I have 2 questions:

The labeling order is inconsistent with the order in the icon. Is it more intuitive and easy to understand if using the same order?
Is Y-axis only for All Cells? When the current nodes of Live cell and Dead cell are mapped to Y-axis through screenshots, it is found that the data displayed are inconsistent.

Cell Count needs to indicate whether it should be the respective occupancy of Live cell and Dead cell in All cells at the current node.

After seeing the `Cell Count` table, I have 2 questions:

The labeling order is inconsistent with the order in the icon. Is it more intuitive and easy to understand if using the same order?
Is Y-axis only for All Cells? When the current nodes of Live cell and Dead cell are mapped to Y-axis through screenshots, it is found that the data displayed are inconsistent.

Cell Count needs to indicate whether it should be the respective occupancy of Live cell and Dead cell in All cells at the current node.

After seeing the `Cell Count` table, I have 2 questions:

The labeling order is inconsistent with the order in the icon. Is it more intuitive and easy to understand if using the same order?
Is Y-axis only for All Cells? When the current nodes of Live cell and Dead cell are mapped to Y-axis through screenshots, it is found that the data displayed are inconsistent.

Cell Count needs to indicate whether it should be the respective occupancy of Live cell and Dead cell in All cells at the current node.

We greatly appreciate the first suggestion. As for the second suggestion, since it directly displays the data, we need to communicate and confirm whether there is an issue with the data.

After seeing the `Cell Count` table, I have 2 questions:

The labeling order is inconsistent with the order in the icon. Is it more intuitive and easy to understand if using the same order?
Is Y-axis only for All Cells? When the current nodes of Live cell and Dead cell are mapped to Y-axis through screenshots, it is found that the data displayed are inconsistent.

Cell Count needs to indicate whether it should be the respective occupancy of Live cell and Dead cell in All cells at the current node.

Regarding the first suggestion, I successfully made the requested modifications, but I realized it was incorrect. This value cannot be set because the candlestick chart changes with the height, and it should be identified based on color instead.

Comparing the data of 2022/4/28/ and 2022/5/1, it is found that the amount of All Cells and Dead cell has increased, but the amount of Live cells has decreased, but from the figure, Live cell cell` is also rising, it feels wrong.

1.A cell contains two status：dead or live ，total cell=dead cell+live cell ，why some days shows total cell >dead cell+live cell?

2.In the chart,I can not find 2022-05-25 data,what is the reason?
https://github.com/Magickbase/ckb-explorer-frontend/assets/25971273/c1901d96-c241-42e4-9072-e3dd22db23b0

Comparing the data of 2022/4/28/ and 2022/5/1, it is found that the amount of All Cells and Dead cell has increased, but the amount of Live cell has decreased, but from the figure, Live cell cell` is also rising, it feels wrong.

It needs to be revalidated. This time, the issue with the scale of the candlestick chart has been fixed.

1.A cell contains two status：dead or live ，total cell=dead cell+live cell ，why some days shows total cell >dead cell+live cell?

2.In the chart,I can not find 2022-05-25 data,what is the reason?
2023-06-<IP_ADDRESS>.mov

If there is data available for that date, it will be displayed. There is data available for May 25, 2022, in the mainnet test.

Comparing the data of 2022/4/28/ and 2022/5/1, it is found that the amount of All Cells and Dead cell has increased, but the amount of Live cell has decreased, but from the figure, Live cell cell` is also rising, it feels wrong.

It needs to be revalidated. This time, the issue with the scale of the candlestick chart has been fixed.

The above problems have been improved. But now this graph does not feel like a stacked graph (live cell + dead cell = all cells), it is more like an overlapping graph.

refer to  https://explorer.nervos.org/charts/liquidity

Comparing the data of 2022/4/28/ and 2022/5/1, it is found that the amount of All Cells and Dead cell has increased, but the amount of Live cell has decreased, but from the figure, Live cell cell` is also rising, it feels wrong.

It needs to be revalidated. This time, the issue with the scale of the candlestick chart has been fixed.

The above problems have been improved. But now this graph does not feel like a stacked graph (live cell + dead cell = all cells), it is more like an overlapping graph.
refer to https://explorer.nervos.org/charts/liquidity

It seems that the issue is related to the data. Let's continue the discussion on this matter in the following link：https://github.com/Magickbase/ckb-explorer-public-issues/issues/347

This is the updated version after the changes. It needs to be tested. Thank you.
@FrederLu

 This is the updated version after the changes. It needs to be tested. Thank you. @FrederLu

Now it looks like a stacked graph.
It can be seen from the screenshot that there are live cell and dead cell information, but the All Cells information cannot be seen in the unit time of the chart.
Although we know that the sum of living cells and dead cells is all the cells, it is better to use the corresponding icon to display it to make the information of all cells more eye-catching.

 This is the updated version after the changes. It needs to be tested. Thank you. @FrederLu

Now it looks like a stacked graph. It can be seen from the screenshot that there are live cell and dead cell information, but the All Cells information cannot be seen in the unit time of the chart. Is it possible to consider using a line with the color of all cells on the top of the dead cell area? In this way, the corresponding icon information is available.

It has been bolded.


FltGetFileNameInformation: FO_CLEANUP_COMPLETE (not a post-close)

FltGetFileNameInformation cannot get file name information in the post-close path.

FltGetFileNameInformation returns STATUS_FLT_INVALID_NAME_REQUEST much earlier than in post-close. As I understand it, function returns an error if target file object has FO_CLEANUP_COMPLETE. That is: post-cleanup and later (including pre close).

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

ID: 82c69953-3606-33d2-1c71-fa25b72a82da
Version Independent ID: 67b78c7c-0fdc-ab17-d7d7-53a6b3eaded0
Content: FltGetFileNameInformation function
Content Source: wdk-ddi-src/content/fltkernel/nf-fltkernel-fltgetfilenameinformation.md
Product: windows-hardware
GitHub Login: @windows-driver-content
Microsoft Alias: windowsdriverdev

FltGetFileNameInformationUnsafe has correct description:

… following types of circumstances, where querying the file system for name information can cause deadlocks:
….

After an IRP_MJ_CLEANUP operation is completed.

@kITerE , this another important correction that needed to be made - I have updated the page - thanks!


Fix partial matching warning in tests

Seen on my system with options(warnPartialMatchDollar = TRUE) .

Codecov Report

Merging #198 (f426d53) into main (2a11bdb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #198   +/-   ##
=======================================
  Coverage   88.34%   88.34%
=======================================
  Files          60       60
  Lines        9024     9024
=======================================
  Hits         7972     7972
  Misses       1052     1052

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Create event failes

Subject: Create event failes
Description:
Submit an event
Results:
Every field is filled in for the "Create event" form. It keeps responding with "Unknown Content-type received" without any remark where there might be a problem.
Backend version: develop-0023fa73
Frontend version:
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Page: https://couchers.org/event/new
User: pelgrim (61)

not enough info or can't reproduce


Support macOS Builds

Currently running dotnet restore and dotnet build on macOS ends with the following failure.
➜ dotnet build
Microsoft (R) Build Engine version 16.10.0-preview-21181-07+073022eb4 for .NET
Copyright (C) Microsoft Corporation. All rights reserved.

  Determining projects to restore...
  All projects are up-to-date for restore.
  You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
  You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
  You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
  You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
  You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
  You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
  You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
  You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
  You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
  SourceGenerator -> /Users/khalidabuhakmeh/Projects/Dotnet/Insights/artifacts/SourceGenerator/bin/Debug/netstandard2.0/NuGet.Insights.SourceGenerator.dll
  Logic -> /Users/khalidabuhakmeh/Projects/Dotnet/Insights/artifacts/Logic/bin/Debug/netcoreapp3.1/NuGet.Insights.Logic.dll
/Users/khalidabuhakmeh/Projects/Dotnet/Insights/src/Worker.Logic/CatalogScan/Drivers/NuGetPackageExplorerToCsv/NuGetPackageExplorerFileRecord.cs(5,15): error CS0234: The type or namespace name 'AssemblyMetadata' does not exist in the namespace 'NuGetPe' (are you missing an assembly reference?) [/Users/khalidabuhakmeh/Projects/Dotnet/Insights/src/Worker.Logic/Worker.Logic.csproj]
/Users/khalidabuhakmeh/Projects/Dotnet/Insights/src/Worker.Logic/CatalogScan/Drivers/NuGetPackageExplorerToCsv/NuGetPackageExplorerFileRecord.cs(42,16): error CS0246: The type or namespace name 'PdbType' could not be found (are you missing a using directive or an assembly reference?) [/Users/khalidabuhakmeh/Projects/Dotnet/Insights/src/Worker.Logic/Worker.Logic.csproj]
  Logic.Test -> /Users/khalidabuhakmeh/Projects/Dotnet/Insights/artifacts/Logic.Test/bin/Debug/netcoreapp3.1/NuGet.Insights.Logic.Test.dll

Build FAILED.

/Users/khalidabuhakmeh/Projects/Dotnet/Insights/src/Worker.Logic/CatalogScan/Drivers/NuGetPackageExplorerToCsv/NuGetPackageExplorerFileRecord.cs(5,15): error CS0234: The type or namespace name 'AssemblyMetadata' does not exist in the namespace 'NuGetPe' (are you missing an assembly reference?) [/Users/khalidabuhakmeh/Projects/Dotnet/Insights/src/Worker.Logic/Worker.Logic.csproj]
/Users/khalidabuhakmeh/Projects/Dotnet/Insights/src/Worker.Logic/CatalogScan/Drivers/NuGetPackageExplorerToCsv/NuGetPackageExplorerFileRecord.cs(42,16): error CS0246: The type or namespace name 'PdbType' could not be found (are you missing a using directive or an assembly reference?) [/Users/khalidabuhakmeh/Projects/Dotnet/Insights/src/Worker.Logic/Worker.Logic.csproj]
    0 Warning(s)
    2 Error(s)

Thanks for the heads up! NuGetPackageExplorer.Core does work fully on non-Windows platforms that's what is happening here.

I tried to run tests from Logic.Tests (after setting <EnableNPE>true) but it fails on:
  Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(328, 5): [NETSDK1073] The FrameworkReference 'Microsoft.WindowsDesktop.App' was not recognized

Not too sure where this Windows Desktop SDK dependency is coming from. It looked like a pure .NET Core class library to me.

I think it's coming through NuGetPackageExplore.Core. I should be able to repro the problem close enough on Linux to figure out a solution. I think what I need to do is to completely disable NuGetPackageExplorer stuff when not running on Windows. I tried that before but I guess I missed some spots.

Build is passing on Mac OS GitHub Actions CI. Tests run by using a real Azure storage account. I need to add instructions for that while Azurite issues are getting worked out. But essentially these environment variables need to be set:
https://github.com/NuGet/Insights/blob/183717ba35680cb27841ba962fd1792b29940efa/test/Logic.Test/TestSupport/TestSettings.cs#L20-L35


Please consider remove the -p flag!

If your templates use partials you should pass paths to partials using -p flag:

This is very much inconvenient, could you please add a feature that kill the -p flag? Please?

His there!
Would you be so kind and elaborate why that argument is so inconvent?
On Sun, 28 Mar 2021 at 15:17, d892fc @.***> wrote:

If your templates use partials you should pass paths to partials using -p
flag:
This is very much inconvenient, could you please add a feature that kill
the -p flag? Please?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/janl/mustache.js/issues/774, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJMWE6NO2W4LSQ5FDNKF3TTF4T73ANCNFSM4Z6A4TJQ
.

@phillipj
Thanks very much for your attention!
The situation is if a mustache template use partials, I have to pass paths to partials using -p flag, like this:
$ mustache -p path/to/partial1.mustache -p path/to/partial2.mustache dataView.json myTemplate.mustache

This is inconvenient because sometimes it's difficult to figure out what partials I've used in a template, what is worse is that even I have figured out that, I have to input a lot of words in the Terminal, it's very painful.
So I think there might be some way to not let a user to provide such information, because mustache.js can figure out them automatically:
-p path/to/partial1.mustache -p path/to/partial2.mustache

@phillipj
Thanks very much for your attention!
The situation is if a mustache template use partials, I have to pass paths to partials using -p flag, like this:
$ mustache -p path/to/partial1.mustache -p path/to/partial2.mustache dataView.json myTemplate.mustache

This is inconvenient because sometimes it's difficult to figure out what partials I've used in a template, what is worse is that even I have figured out that, I have to input a lot of words in the Terminal, it's very painful.
So I think there might be some way to not let a user to provide such information, because mustache.js can figure out them automatically:
-p path/to/partial1.mustache -p path/to/partial2.mustache

I see your point of having to provide potentially many partial arguments.
It would be interesting to hear what & how you would have expected mustache.js to know where partials are located.

The fact is I don't know, and that's why I asked for your help!

Ahh okey.
I can personally imagine this behaving in lots of different ways. The obvious factors would be folder structure, filenames and extensions. Those will vary from project to project, and what would work for the majority of projects isn't obvious until we've got insights from many projects.
With that in mind, I'm very hesitant implementing anything into mustache.js itself. At least until we've got more use cases at hand. And removing the -p argument from the command line tool we've got wouldn't help much as far as I'm concerned.
But, the above does not mean we can't help you. There's usually several ways to solve a challenge. More concrete details about what you're facing would be helpful tho..

 Or are you strictly enforced to use the mustache executable?
How does your folder structure & filenames look like?

Jan, thank you very much for your reply!

I'm sure that I will use the command line interface rather than custom JavaScript scripts to compile our templates, and we are certain to use mustache.js rather than any other language implementation of {{ mustache }}.

We don't use partials from node_mosules/ directories for now, our partials are either relative path to current template or use absolute paths.

The file extension is either .html or .mustache, we prefer .html because I think that mustache is only a useful syntax extension of HTML.
-------- 原始邮件 --------
发件人： Phillip Johnsen @.>
日期： 2021年3月29日周一 19:48
收件人： "janl/mustache.js" @.>
抄送： d892fc @.>, Author @.>
主 题： Re: [janl/mustache.js] Please consider remove the -p flag! (#774)
Ahh okey.
I can personally imagine this behaving in lots of different ways. The obvious factors would be folder structure, filenames and extensions. Those will vary from project to project, and what would work for the majority of projects isn't obvious until we've got insights from many projects.
With that in mind, I'm very hesitant implementing anything into mustache.js itself. At least until we've got more use cases at hand. And removing the -p argument from the command line tool we've got wouldn't help much as far as I'm concerned.
But, the above does not mean we can't help you. There's usually several ways to solve a challenge. More concrete details about what you're facing would be helpful tho..

 Or are you strictly enforced to use the mustache executable?
How does your folder structure & filenames look like?

―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/janl/mustache.js/issues/774#issuecomment-809314192, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI3IO2XFWBPICIZNSFA3DTDTGBZLHANCNFSM4Z6A4TJQ.

Janl, you are right.
But I still prefer using the executable, because it is easier to use for us.
-------- 原始邮件 --------
发件人： Phillip Johnsen @.>
日期： 2021年3月31日周三 04:14
收件人： "janl/mustache.js" @.>
抄送： d892fc @.>, Author @.>
主 题： Re: [janl/mustache.js] Please consider remove the -p flag! (#774)
Thanks for sharing!
A custom .js script could do what you're looking for in many different ways, without being overly complex. Let me know if you'd reconsider using such a .js script that you'd be in total control of ofcourse, rather than the mustache executable directly.
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/janl/mustache.js/issues/774#issuecomment-810547663, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI3IO2X57LJ3AMXXF2ESH5LTGIWMDANCNFSM4Z6A4TJQ.

A custom script is acceptable, but not my choice.
The logic is actuall analysis the {{> too/bar/baz }} directives, and find out where they are located.
We don't have to remove the -p command line flag, we can just ignore its values.
-------- 原始邮件 --------
发件人： Phillip Johnsen @.>
日期： 2021年3月31日周三 04:14
收件人： "janl/mustache.js" @.>
抄送： d892fc @.>, Author @.>
主 题： Re: [janl/mustache.js] Please consider remove the -p flag! (#774)
Thanks for sharing!
A custom .js script could do what you're looking for in many different ways, without being overly complex. Let me know if you'd reconsider using such a .js script that you'd be in total control of ofcourse, rather than the mustache executable directly.
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/janl/mustache.js/issues/774#issuecomment-810547663, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI3IO2X57LJ3AMXXF2ESH5LTGIWMDANCNFSM4Z6A4TJQ.

While, it is not a must to implement the enhanced version of the mustache executable.
We found a third solution to this. A web compiler normally has there parts, a checker, a complier and a minifier.
For example, rollup.js compiler has rollup-plugin-eslint to integrate ESLint, rollup-plugin-terser to integrate terser.
At the end, we found PostHTML like rollup.js  has a simple plugin named as post html-plugin-include can do the job.  So we don't need mustache executable to implement the feature we have been talking about.
The mian reason is, for now, I only need the partial including feature of mustache, I like mustache's syntax style, it's simply and looks handsome.
We use two temple engines in our project, one for temple designing, the other for use in HTTP request handlers.  The designer gives bundles of HTML temples, not a lot of partials.
-------- 原始邮件 --------
发件人： Phillip Johnsen @.>
日期： 2021年3月31日周三 04:14
收件人： "janl/mustache.js" @.>
抄送： d892fc @.>, Author @.>
主 题： Re: [janl/mustache.js] Please consider remove the -p flag! (#774)
Thanks for sharing!
A custom .js script could do what you're looking for in many different ways, without being overly complex. Let me know if you'd reconsider using such a .js script that you'd be in total control of ofcourse, rather than the mustache executable directly.
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/janl/mustache.js/issues/774#issuecomment-810547663, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI3IO2X57LJ3AMXXF2ESH5LTGIWMDANCNFSM4Z6A4TJQ.

We found a third solution to this.

Great to hear you found something that suites your needs!
Handlebars.js has also been a great alternative for those who like mustache, but wants more opportunities.
I'm closing this issue for now, although for those who stumble upon this issue later and would like something similar, share your thoughts as feedback and other concrete use cases is a requirement for make this happen in mustache.js itself.

I like mustache more, handlebars is too heavy.


Reduce Happa build time

Description
Happa build takes a lot of time and happens a lot (joe cares about credit usage, but we can probably save on carbon and developer time here too).
Therefore, to reduce the "time to build" a release:
TODO

[ ] Get the "build time" of Happa and add in the issue (we could decide on a build time threshold later and add some monitoring)
[ ] Check the build logs and find what is consuming so much time
[ ] Provide a list and apply the optimization we can bring
[ ] Get the new "build time" of Happa and add in the issue after optimization

Joe will be speaking to CircleCI on April 21st, so we should ideally have investigated/fixed this before then.

Credits are calculated based on build minutes, price varies depending on the resource class used. We use Docker medium for everything except for tests, where we use x-large. This was necessary after we switched from SWC to Babel because tests kept timing out.
Current build times (last 30 days as of April 13th, 2022):

Jobs sorted by credit usage:

I think another area for improvement is the number of runs as well. While this doesn't necessarily improve time per build, it reduces the number of credits/resources used.
renovatebot creates around 3 PRs per day to upgrade dependencies, and merging one causes the other branches to rebase again. We can configure this to try and reduce this. We can also examine the existing package groups to see if we can identify other groups of dependencies to update together.

After the changes from the above PR, we:

only build FE docs when creating a release
have combined lint, typecheck, prettier into one step
have combined build-container and push-happa-docker/quay steps

An example from before:

An example of the build process now:

There hasn't been enough runs to get a reliable average on the build time/credit usage, but this is something we can track overtime and reevaluate in the future if required.


Rosetta: Re-enable the disabled tests, ensure it's on CI (Andrew may have already covered this?)

@lk86 @aneesharaines Is there more to do here? (I'm not sure which the disabled tests were.)

Duplicate of #9332


Feature/winter 21  schedule wizard step1

// Imagine the actual release notes will go into the branch that has the wizard all wired up. This is just the UI for step 1
Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata
Definition of Done
Refer to Asteroids DoD document to see any additional details for the items below
Place holder data is incorporated (Refer to Case Management Sample Data document)
Base axe-core JEST test included for any new LWC (No critical violations)
CRUD/FLS is enforced in Apex
~~ Update & Test permission sets to account for new features and CRUD/FLS~~
All modified classes are unit tested (Apex) at 100% coverage

[ ] UX approval or UX not necessary
PR contains draft release notes
[ ] Attach work item to the pull request with Lurch **Lurch:attach W-000000 or **Lurch:add
[ ] All acceptance criteria have been met

[ ] Developer
[ ] Code Reviewer
[ ] QA

[ ] QE story level testing completed

W-7981428


ShapeNet on JSNet

Hello People, I'm wondering how the authors of the paper tested their network on the ShapeNet dataset? Any ideas?

@azzabaatout The testing process is similar to testing on the S3DIS dataset, but only the accuracy of semantic segmentation is calculated.


Update routing index.mdx

Link reload doesn't work without href
Overview

What is it?

[ ] Feature / enhancement
[x] Bug
[ ] Docs / tests / types / typos

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Use cases and why

One use case

Another use case

Checklist:

[ ] My code follows the developer guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Hi @alimrb 👋
Thanks a lot for this adjustment 🙏  tbh i am not sure if this is not a bug 👼
IMO the condition here should be adjusted: https://github.com/BuilderIO/qwik/blob/main/packages/qwik-city/runtime/src/link-component.tsx#L25
to:
if(elm.href || reload) { ... }
@adamdbradley can you confirm that or am i mistaking 👼


Deprecation warnings with PostCSS 5.0

Looks the module still works, but as it's installed alongside PostCSS there's nothing stopping the 5.0.0 bump, which results in these warnings for me:
Container#eachAtRule is deprecated. Use Container#walkAtRules instead.
Container#eachRule is deprecated. Use Container#walkRules instead.
Container#eachDecl is deprecated. Use Container#walkDecls instead.
Node#style() is deprecated. Use Node#raw()
Node#before is deprecated. Use Node#raws.before
Node#_value was deprecated. Use Node#raws.value

Just saw that postcss is actually a dependency of autoprefixer-core. Would you advice not installing PostCSS directly in my module like this?
 "autoprefixer-core": "^5.2.1",
 "postcss": "^5.0.0",

Looks like a reinstall of all modules actually resolved this.
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

Autoprefixer will moved to PostCSS 5.0 in 6.0 release

@ai What can you suggest instead?

@joseluisq I do not see a big problems with warnings. Just ignore it.
Also you can downgrade PostCSS runner (like gulp-postcss) to PostCSS 4.x. But it is not ideal way.
Sorry, I just have no time in this month to release 6.0 — because of major update we need o implement many awesome things :).

@ai Thanks I understand
PostCSS is cool ! in fact autoprefixer-core v5.x and PostCSS v4.x work fine.
Sounds great ! So I await for your next release ! :+1:


Nav-bar not mobile friendly

Description
The nav-bar on the SMP website is not mobile friendly.
Expected Behavior
It should fit the size of any mobile screen.
Screenshots

Environment:

OS: [e.g. Ubuntu]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]
Device: [e.g. laptop, iPhone 8]

@warunicorn19  Can I work on this?

yup! @debo19


Add CHANGELOG and automantion

Use commitizen as default to bump and another program to automatically update changelog version.

https://github.com/Lucs1590/Nkocr/commit/1edc9d37806a2ec5e861b55062537ba829d4619e


android-sdk breaks PATH

When I install the android SDK, it breaks my PATH completely. Nothing on my path functions after I do this, requiring me to keep the console window that I installed it in open to use scoop (or anything else). Uninstalling it solves the problem, but I don't consider this an optimal solution. Is there a reason this happens?

Update: so apparently if the PATH environment variable exceeds a particular length it breaks it. Weird. Anyway, all has been solved.


Docker image

We need a docker.io image.

We need to make things configurable via docker run -e.
We should use the Alpine base image.

Here I wrote a minimal example based on the Alpine image and an external JSON config file:
FROM    alpine:3.5
LABEL maintainer<EMAIL_ADDRESS>
ENV     LC_ALL en_US.UTF-8

RUN apk add --no-cache nodejs git python make g++ graphicsmagick
RUN npm install -g databank-mongodb
RUN npm install -g pump.io
RUN adduser -D -g "" pumpio

ADD     pump.io.json /etc/

EXPOSE  8080
CMD  ["/usr/bin/pump"]

@adundovi I'd like the Docker image to be something officially maintained by the pump.io project - that means in some "official" namespace on Docker Hub and maintained in-tree, in sync with the rest of the codebase. If you're willing to maintain this long-term as a member of the project I'd be thrilled if you submitted a PR so that we can iterate on it and get that going.

@strugee Well, I would like to contribute with that, but I am still fighting with different kind of "500 Internal Server Error" issues and there is no sense to submit anything if the stuff is not working. To add, I am not skillful with nodejs, which is making things harder to debug, thus I do not know if the bugs lie in my particular setup or in the pump.io code. If I will have the basic feature set working I will certainly polish and publish the docker code.

@adundovi nonsense! PRs are a great way to get feedback on work-in-progress implementations. I regularly submit half-baked PRs to get early feedback on stuff :)
If you send a PR I can try to reproduce your 500 errors locally and try and find where the problem is. Just prefix the title with [WIP] or something.

@adundovi are you still interested in doing this?

@strugee Here I put something to start with, but I don't know which repo is appropriate for the PR?

@adundovi probably this one? I'm not familiar with Docker so I dunno if that'll make things difficult - if so we can create a separate repo. But I think we should aim for this one if possible

will this work?
https://github.com/niktrix/docker-pump.io
On Mon, Mar 27, 2017 at 10:58 AM, Alex Jordan<EMAIL_ADDRESS>wrote:

@adundovi https://github.com/adundovi probably this one? I'm not
familiar with Docker so I dunno if that'll make things difficult - if so we
can create a separate repo. But I think we should aim for this one if
possible
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pump-io/pump.io/issues/789#issuecomment-289357142,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABM9ZqdQjBYf99rRWgtaszqikKyLFZ2Eks5rp0jvgaJpZM4A7r7l
.

--
Nitin Gurbani
http://niktrix.in

@niktrix that Dockerfile seems really old... it's installing MongoDB from a third-party repo (which is unnecessary), it doesn't allow configuration, and it would be nice to base it on the Alpine image, so the image is smaller

@adundovi @niktrix if one of you is interested in writing a modern Dockerfile that we can officially accept and sending a Pull Request including it, please say so. Otherwise I think I'll just write one myself

@strugee  we dont have bandwidth to do so, thanks

@niktrix I used your Dockerfile as a starting point for mine.
@strugee I made a PR #1307 (this one is with the Alpine image)

Is there a docker image for the raspberry pi (3)?

@Serkan-devel you should feel free to build one yourself using the Dockerfile in this repository, but we are not officially distributing Docker images yet due to #1418.


Gradle's failure to load *.module file may cause a failing build

Description
It seems that in some cases Gradle does not respect published-with-gradle-metadata in POM file, and therefore fails to load module file, thus missing some necessary dependencies, and resulting in unstable or failing build.
Example
In a project I am working on we have a dependency to io.insert-koin:koin-android:3.2.0, which, in absence of ~/.m2/repository will result with the following part of the dependency tree:
+--- io.insert-koin:koin-android:3.2.0
     +--- io.insert-koin:koin-core:3.2.0
          \--- io.insert-koin:koin-core-jvm:3.2.0

In our code we use classes from io.insert-koin:koin-core-jvm:3.2.0 library.
However, if there is a local Maven repository available and io.insert-koin:koin-core:3.2.0 is already downloaded by Maven, Gradle will read the koin-core-3.2.0.pom file. That POM file contains the hint published-with-gradle-metadata, which should, to my understanding, cause Gradle to also download koin-core-3.2.0.module file, and add io.insert-koin:koin-core-jvm:3.2.0 to the dependency tree.
However, this does not happen, and it results in the dependency tree where io.insert-koin:koin-core-jvm:3.2.0 is missing:
+--- io.insert-koin:koin-android:3.2.0
     \--- io.insert-koin:koin-core:3.2.0

which will result in a failing build.
Steps to reproduce

Install Maven, version e.g. 3.8.4
Delete Gradle cache (~/.gradle/caches) and local Maven repo (~/.m2/repository), if they exist
Force download of io.insert-koin:koin-core:3.2.0 dependency to local Maven repo with mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:get -DrepoUrl=https://repo1.maven.org/maven2/ -Dartifact=io.insert-koin:koin-core:3.2.0
Confirm that ~/.m2/repository/io/insert-koin/koin-core/3.2.0/koin-core-3.2.0.pom exists and it contains string published-with-gradle-metadata in the comment
Unpack the attached example project, change local.properties accordingly, and build it with ./gradlew build
The build will fail because of missing classes from koin-core-jvm

Expexted result

The build passes

Workaround

Stop Gradle daemons (./gradlew --stop)
Delete local Maven repo (~/.m2/repository)
Repeat the build
The build will pass

Note: I used Gradle 7.4.2 and Maven 3.8.4, tested on Windows 10.
Tiny example project demonstrationg the issue
gradle-unstable-build.zip

Pls. check out the following section of the documentation: https://docs.gradle.org/current/userguide/declaring_repositories.html#sec:case-for-maven-local
In short: since your Maven local repo doesn't have the module file, Gradle will only use the pom.


Adding Draft Validate functionality into main

Description
Host of new features to enable the draft validate command into the main branch.
Fixes # (issue)
Feature # (details)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. Is it a  breaking change which will impact consuming tool(s).

Unit test suite for cmd/validate and pkg/safeguards

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

note: rebased #279  here onto main to handle divergent branches from patching go module versions


make it a panel view not a field

Hey, as a quick workaround, here's some minimal code to wrap the field in a panel view.
panel.plugin('me/doctorpanelview', {
  views: {
    doctorview: {
      component: {
        template: `
          <k-view class="doctor-panel-view">
            <k-header>Kirby Doctor</k-header>
            <k-doctor-field label="Doctor" progress="Performing checks..." job="plugin-doctor/check">
          </k-view>
        `
      },
      icon: "bug",
      label: "Doctor"
    }
  }
});

Hey, as a quick workaround, here's some minimal code to wrap the field in a panel view.
panel.plugin('me/doctorpanelview', {
  views: {
    doctorview: {
      component: {
        template: `
          <k-view class="doctor-panel-view">
            <k-header>Kirby Doctor</k-header>
            <k-doctor-field label="Doctor" progress="Performing checks..." job="plugin-doctor/check">
          </k-view>
        `
      },
      icon: "bug",
      label: "Doctor"
    }
  }
});


Flashing header during transition from issue to index

https://youtu.be/RLi7RX2m3Xc

Already tracking, it’s from the org move
Sent with GitHawk

Closing b/c it looks like this is fixed on the latest TF build? I didn't do anything... 🤷♀

I'm still seeing it

@gingerbeardman which version of iOS?
Sent with GitHawk

11.3 (15E216)
It looks to me that the flashing is changing transparencyof whatever is behind the overlap of the header.

Reproduction:
Whilst reading this comment in GitHawk swipe slowly from the left edge of the screen

Hmm ya doesn’t happen for me, gonna leave closed unless it resurfaced with more detail on what’s going on
Sent with GitHawk

Strange, now it's not doing it for me in this issue. I'll keep an eye out

OK. Here are new steps to reproduce:

Start GitHawk fresh
2. Tap a link that opens in a web view
Swipe screen slowly from left edge
Notice the flashing

It does not happen unless a web view has been opened.

🤔 so the only blackish thing I can find in the view hierarchy is this UILayoutContainerView from the UISplitViewController.

I think the "something black" is a red herring?

It might be 🤷♂
Sent with GitHawk

Ya those are the CALayers storing text bitmaps.
Thanks for the repro steps @gingerbeardman! I’ll take a look when I have time.
Sent with GitHawk


[Snyk] Security upgrade node from 14.1.0 to 16

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

Dockerfile

We recommend upgrading to node:16, as this image has only 467 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

714
OS Command Injection SNYK-DEBIAN9-OPENSSL-2807589
No Known Exploit

714
Buffer Overflow SNYK-DEBIAN9-PYTHON27-1063180
No Known Exploit

714
CVE-2019-9636 SNYK-DEBIAN9-PYTHON27-340070
No Known Exploit

714
Directory Traversal SNYK-DEBIAN9-PYTHON27-341379
No Known Exploit

714
Insufficiently Protected Credentials SNYK-DEBIAN9-PYTHON35-584435
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Directory Traversal

just a test


Notebook diff accordions should use or align with existing components

Testing #226663
These:

Look similar, but not quite the same, as these other tree/accordion elements we have

Off the top of my head, it probably makes the most sense to align to the tree view both from a styling and interaction POV. For example, the collapsible sections in the notebook diff and only be expanded/collapsed by clicking on the chevron. In tree views/views/settings TOC, you can click anywhere on the containing element.
It also looks like I can't focus on the element to expand/collapse with just the keyboard.

It also looks like I can't focus on the element to expand/collapse with just the keyboard.

Duplicate of https://github.com/microsoft/vscode/issues/105922

looks good to me (I can click anywhere to expand), but maybe @daviddossett should take another look since I don't see much inconsistency in those screenshots.


Debouncing Entry and Exit Events

I have a Google Pixel running Pie. Frequently I see it generate extremely quick sequences of entry and exit events—even when the phone is sitting 12 inches away from a beacon broadcasting quickly at high power and configured to detect within a 5 meter radius. Given that the goal of our app is to notify others when people arrive and leave, this is disconcerting behavior.
I've thought about ways to try and debounce this either on our device or on our server, but there are some complications, particularly on iOS where background operation is limited. (Although the problem seems less prevalent on iOS.) Plus, it's just kind of gross.
Is there a way for the native SDK to expose a parameter controlling how sticky locations are? This might help tune it to the peculiarities of different devices. (FWIW I've seen this with other beacons, so I suspect it's an issue with Android's Bluetooth stack on this device and not necessarily your beacons.)

Probably best discussed on the native SDK's bug trackers and/or Estimote Forums, since these are changes that would need to be implemented on the native side. A "knob" for the stickiness sounds like a potentially good idea (:
A quicker fix for your app would be to be more liberal with the trigger radius. From my own experience, Androids especially vary drastically, and generally require higher numbers.

OK good to know. What radius to you suggest for Android? I tried some higher numbers but then had the opposite problem (that you'd expect): not getting exit events promptly.

It's really tough to say, I'd actually expect that for the best results, the numbers would need to be tuned almost per device. There's been ideas/efforts to crowd-source this knowledge, but none that I know of have worked out. (e.g., see the model-distance-calculations.json in the open-source Android Beacon Library)


Saltern Tweaks

Makes the bar look nicer
Fixes dark areas of the station
Dorms is actually dorms, with 3 rooms
Some tile fuckups in maint
Small changes

Screenshots?

I hope you didn't forget to fix roundstart atmos!

Bar and Dorms

cute, good changes

cute, good changes

meet me in dorms 3 after merge

But where is dorms 4

But where is dorms 4

your bedroom

But where will we fit the locker room now?


Plugin for self-update

Proposed changes
Extended Software Management apt-plugin to manage module type "tedge". Module type "tedge" is defined to manage thin-edge self-update. See https://github.com/thin-edge/thin-edge.io-specs/pull/20
Types of changes
What types of changes does your code introduce to thin-edge.io?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue
https://github.com/thin-edge/thin-edge.io/issues/759

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have read the CONTRIBUTING doc
[ ] I have signed the CLA (in all commits with git commit -s)
[ ] I ran cargo fmt as mentioned in CODING_GUIDELINES
[ ] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

Obsolete. Was transfered to https://github.com/thin-edge/thin-edge.io/pull/1067


[Feature] Boleto rejection handling

Se agrega soporte a rechazos de Boleto.
Cambios:

Migración a nuevo MVP de PaymentResultActivity + tests.
Adaptación de pantallas de rechazo a Boleto.

Codecov Report

Merging #702 into develop will increase coverage by 0.13%.
The diff coverage is 20.32%.

@@             Coverage Diff             @@
##           develop     #702      +/-   ##
===========================================
+ Coverage    28.31%   28.44%   +0.13%
===========================================
  Files          251      253       +2
  Lines        18257    18306      +49
  Branches      1565     1557       -8
===========================================
+ Hits          5170     5208      +38
- Misses       12546    12550       +4
- Partials       541      548       +7

Impacted Files
Coverage Δ

...k/src/main/java/com/mercadopago/model/Payment.java
99% <ø> (ø)
:arrow_up:

...c/main/java/com/mercadopago/RejectionActivity.java
0% <0%> (ø)
:arrow_up:

...rcadopago/providers/PaymentResultProviderImpl.java
0% <0%> (ø)

...in/java/com/mercadopago/PaymentResultActivity.java
0% <0%> (ø)
:arrow_up:

...mercadopago/presenters/PaymentResultPresenter.java
82.6% <82.6%> (ø)

Continue to review full report at Codecov.

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

Ahí subí los cambios @valeserber !


Zone level forwarding is sometime not correct.

If you have multiple Azure platforms you connect to from on-premise, zone level forwarding may not be correct. Because some clients connecting to the other Azure platform can not resolve the FQDN and fail to connect to Azure Database which host the domain of "database.windows.net". So I would like you to add some comments to avoid such situation. I think we should use FQDN level forwarding to avoid such situation.
https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-dns#on-premises-workloads-using-a-dns-forwarder
Important
The conditional forwarding must be made to the recommended public DNS zone forwarder. For example: database.windows.net instead of privatelink.database.windows.net.

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

ID: a88af182-32aa-a8f3-359d-b92ae1cfb8c7
Version Independent ID: 01ce07fc-4bc2-def5-9ecd-a80330ad9488
Content: Azure Private Endpoint DNS configuration
Content Source: articles/private-link/private-endpoint-dns.md
Service: private-link
GitHub Login: @asudbring
Microsoft Alias: allensu

@ms-ishiyam
Thanks for your feedback! We will investigate and update as appropriate.

@ms-ishiyam , could you please elaborate what you are referring to as "multiple Azure platforms"?
As mentioned in this section, If you're using a private endpoint in a hub-and-spoke model from a different subscription or even within the same subscription, link the same private DNS zones to all spokes and hub virtual networks that contain clients that need DNS resolution from the zones.

More details about such setup can be found in the below doc:
https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/private-link-and-dns-integration-at-scale?toc=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fazure%2Farchitecture%2Ftoc.json&bc=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fazure%2Farchitecture%2Fbread%2Ftoc.json

"multiple Azure platforms" means that the customer has multiple clients and ER network in a on-premise environment like below.
Client1 (on-premise1) -------- ER1 ----- Hub1 -----Spoke1-1
Client2 (on-premise1) -------- ER2 ----- Hub2 -----Spoke2-1
I think most big customers must have this scenario. They can not use zone level conditional forwarding.

@ms-ishiyam , thank you for the update. We have assigned this to the content owner/author for review.
@asudbring , for your review.

Sending to PM for review
#reassign:@ivapplyr

Thanks for your dedication to our documentation. We have created an internal work item in our backlog to resolve this issue. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


[WebToolsE2E][AspireDeployment] When multiple user accounts are signed in, publish Aspire Starter App to ACA using VS fails with failed to resolve user access to subscription

INSTALL STEPS

Clean machine: Win11 x64 23h2 ENU
2 Install VS 17.10 Preview 3 [latest build, includes Aspire 8.0.0-preview.5.24201.12]

Note: you need a build that includes Antonio's fix for AzDO bug 2016615. Otherwise, you will run into the issue in that bug first
Apply NuGet Feeds

Install latest daily azd build

I got azd version 1.8.0-beta.1-daily.3665690

REPRO STEPS

Open VS, sign-in to 2 accounts in Account Settings

I signed in with both my work account (@microsoft.com) as well as a live.com account (@live.com). Both have access to their respective Azure subscriptions.

MVC app - build, run and publish using live account
2. New ASP.NET Core MVC web app > WebAppMvc2
3. Build and run, then publish to Azure App Service (Windows) using the live.com account - this works fine.
4. Close the solution
Aspire Starter app - build, run and publish using live account
5. New Aspire Starter app > Use redis option is unchecked > AspireStarterApp2
6. Build and run,
7. Publish to ACA - create a new publish environment using the live.com account
8. Hit Publish in VS
ACTUAL
Publish fails

Build started at 5:57 PM...
1>------ Build started: Project: AspireStarterApp2.ServiceDefaults, Configuration: Debug Any CPU ------
1>C:\Program Files\dotnet\sdk\8.0.300-preview.24170.4\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(311,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
1>AspireStarterApp2.ServiceDefaults -> C:\Users\balach\source\repos\AspireStarterApp2\AspireStarterApp2.ServiceDefaults\bin\Debug\net8.0\AspireStarterApp2.ServiceDefaults.dll
2>------ Build started: Project: AspireStarterApp2.Web, Configuration: Debug Any CPU ------
3>------ Build started: Project: AspireStarterApp2.ApiService, Configuration: Debug Any CPU ------
3>C:\Program Files\dotnet\sdk\8.0.300-preview.24170.4\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(311,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
2>AspireStarterApp2.Web -> C:\Users\balach\source\repos\AspireStarterApp2\AspireStarterApp2.Web\bin\Debug\net8.0\AspireStarterApp2.Web.dll
3>AspireStarterApp2.ApiService -> C:\Users\balach\source\repos\AspireStarterApp2\AspireStarterApp2.ApiService\bin\Debug\net8.0\AspireStarterApp2.ApiService.dll
4>------ Build started: Project: AspireStarterApp2.AppHost, Configuration: Debug Any CPU ------
4>AspireStarterApp2.AppHost -> C:\Users\balach\source\repos\AspireStarterApp2\AspireStarterApp2.AppHost\bin\Debug\net8.0\AspireStarterApp2.AppHost.dll
========== Build: 4 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Build completed at 5:57 PM and took 05.947 seconds ==========
4/4/2024 5:57:48 PM: Info
4/4/2024 5:57:48 PM: Info Provisioning Azure resources (azd provision)
4/4/2024 5:57:48 PM: Info Provisioning Azure resources can take some time.
4/4/2024 5:57:48 PM: Info
4/4/2024 5:57:49 PM: Info Analyzing Aspire Application (this might take a moment...)
4/4/2024 5:57:56 PM: Info Initialize bicep provider
4/4/2024 5:57:59 PM: Info Creating a deployment plan
4/4/2024 5:57:59 PM: Error deployment failed: failing invoking action 'provision', error deploying infrastructure: resolving bicep parameters file: fetching current principal id: getting tenant id for subscription xyz. Error: failed to resolve user access to subscription with ID 'xyz'. If you recently gained access to this subscription, run `azd auth login` again to reload subscriptions.
Otherwise, visit this subscription in Azure Portal using the browser, then run `azd auth login`

Workaround
Open Command Prompt, run azd auth logout. Then go back to VS and hit 'Publish' again. It works fine this time.
EXPECTED
Publish to succeed

@weikanglim Both app publish is using the live.com account. One succeeds and other fails asking to login again.
Is this a fix on azd side or any VS issue?


Door Knocking

You may want to add the following feature to Vane Trifle (that I came up with on a sponge plugin once)
If someone attempts to break i.e. punch a door, it should make the zombie break sound on the door (and possibly broadcast it to the owner if in a region) even if the door is protected.
Allows for a cute RP way of paging or knocking, or just a lil trollin'

Sounds like a nice feature!
(For contributors: Except for region broadcasts this is easy to implement)

Hi,
I'd like to take that.

I appreciate it! If I recall correctly, Stonewall0210 also expressed interest in implementing this. I am not sure though whether they already started. I'd like to suggest coordinating this on the discord if possible.

Do you have a discord invite? :)

Sure, look at the top of the readme on the main page of the repository!

Was this ever implemented?

Not that I know of, feel free to take it on if you want :)

Lords of Minecraft RP server has implemented this idea as well, except using Villager Bells, so that could be worth doing too.


fix: comment stripping should remove multiline comments (#279)

Resolves #279

Thanks for the PR dear @cjpearson
Removing multi-line comments without AST awareness can be unsafe this is why we don't it.
See https://github.com/unjs/mlly/pull/56 for some context.
Until https://github.com/unjs/mlly/issues/219 arrives, if we can find similar solution to #56 i am open to it otherwise i would wait.

I've tweaked the approach to use acorn rather than regular expressions for the comment stripping. My understanding is #219 will cover replacing ESM_RE and CJS_RE, so I made it so the change just affects comment stripping portion. Once #219 is done I suppose the comment stripping will be entirely unnecessary


0.59 changelog

Summary of the Pull Request
What is this about:
Readme update for the 0.58 release.
This will be copy / pasted for release notes.
We're waiting a couple of days to hopefully bring in some dependency updates into the release, so it's possible we'll still include some of the open PRs in the release and add those to this PR.

We've since merged some fixes that we'll include in the release, so I've updated the changelog to reflect this.

I've added mentions to the Windows App SDK upgrade, which fixes Settings not opening on machines with UAC off.

I've added some changes to reflect the new self-contained reality, which should fix most installer issues we've seen with 0.58 and allow running on Windows 10 ARM64 as well.


Document Metamodel::Primitives' parameterization cache API

The problem
The parameterization cache is very handy in MOP-heavy code, but is rather unintuitive and undocumented.
Solution provided
Document the set_parameterizer, parameterize_type, type_parameters, and type_parameter_at methods of Metamodel::Primitives.
Adds "parameterizer" and "noop" as words.

checking set_parameterizer, I don't see it specced - are these rakudo specific? (not a blocker to merge)

I'd say these are in a similar limbo to the rest of Metamodel. Sometimes Metamodel behaviour gets specced in one way or another, but not with these. At the same time, they're not marked implementation-detail, and are depended on occasionally in the ecosystem.


Topology plugin applicability to non-Openshift clusters?

Hi. I was wondering if your topology plugin is intended to work on non-OpenShift clusters?  Review this, then perhaps no.
If yes, it can work on any cluster, I'm presuming that a resource on such a cluster should still be annotated with app.openshift.io/connects-to for the visualisation to work appropriately?  Would it make more sense to implement something like backstage.io/connects-to for this to remain somewhat generic functionality? Thanks.
app.openshift.io/connects-to': '[{"apiVersion": <RESOURCE_APIVERSION>,"kind": <RESOURCE_KIND>,"name": <RESOURCE_NAME>}]

Hi, the topology plugin should work with any Kubernetes versions.
Feel free to join our Janus Community Slack channel for more discussion https://janus-idp.slack.com/join/shared_invite/zt-1pxtehxom-fCFtF9rRe3vFqUiFFeAkmg

Thanks for the assistance on slack.


simplify back propagation (remove unnecessary sequence traversal)

The original recursive back propagation algorithm performs breadth-first visiting of Values in the graph, simply to add them to a linear sequence. The sequence is then reversed and iterated over to invoke the _backward() function in each Value.
It is possible to invoke the _backward() function in a single pass during the breadth-first visiting of Values, without creating an interim linear sequence. This PR simplifies the algorithm accordingly.

@tf318 This implementation fails tests:
FAILED test_engine.py::test_sanity_check - assert 128.0 == 46.0
FAILED test_engine.py::test_more_ops - assert 15.166180758017475 < 1e-06


generate linnarsson zarr from hdf5 directly

We don't need to convert to OME to then convert back to zarr...
I added scripts to convert directly to zarr and then tile the chunked full resolution array into lower resolutions. Since we haven't determined our standard yet for pyramids (see https://github.com/hubmapconsortium/vitessce-image-viewer/issues/91), these scripts generate tiles in the format current supported for zarr in Viv:
.
└── linnarsson.images.zarr
    └── pyramid
        ├── 00 # generated by img_hdf5_reader.py
        │   ├── .zarray
        │   ├── 0.0.0
        │   └── ..etc
        ├── 01 # generated by tile_zarr_base.py
        │   ├── .zarray
        │   ├── 0.0.0
        │   └── ..etc
        └── 02 # generated by tile_zarr_base.py
            ├── .zarray
            ├── 0.0.0
            └── ..etc

The linnarsson.images.json should be very similar to the config in viv now, where keys here are "channels" and have the same url since it's one zarr array:
{
  "polyT": {
    "sample": 1,
    "tileSource": "https://s3.amazonaws.com/vitessce-data/0.0.20/master_release/linnarsson/linnarsson.images.zarr/pyramid/"
  },
  "nuclei": {
    "sample": 1,
    "tileSource": "https://s3.amazonaws.com/vitessce-data/0.0.20/master_release/linnarsson/linnarsson.images.zarr/pyramid/"
  }
}

The only thing missing in Viv logic is minZoom. I guess I could add that here to the linnarsson.images.json. In the future we shouldn't be exporting a linnarsson.images.json and instead should have this contained in the .zattrs of the base zarr. But this is what viv supports now and we want to update our demo. It would be good to iron out the zarr schema sooner rather than later..

We will need to change the s3 urls obviously, but all the converters are in place.

We don't need to convert to OME to then convert back to zarr...

What I remember from last summer was that we wanted to think of OME-TIFF as our central format: We think we'll have a lot of formats coming in, and we may want to generate a range of output formats as well, and we don't want m*n scripts.
This assumptions might no longer be true, but I'd like to be more clear about the roadmap. Perhaps loop in Nils?
Sorry not to raise this concern earlier.

I am working on making converters for many types of images, but specifically OME-TIFF with Heath in https://github.com/hubmapconsortium/img2zarr. I figured for the purposes of vitessce, and @ngehlenborg demo on wednesday, this should suffice because its the format the data are provided in.

We should talk tomorrow, but the schema in this PR and the Vanderbilt one should match.  I can show you what it should look like and you can also give me feedback since one is Zarr and one is not.

@mccalluc I updated s3_target.txt --> cloud_target.txt and all instances of $S3_TARGET --> $CLOUD_TARGET


Issue with count touching cells

Hi Kent,
I have been having  an issue with count_touching_cells. I have used the following code in RStudio on a Windows PC:
**base_path <- '~/OPAL R ANALYSIS/T panel/SPATIAL ANALYSIS/TOUCH PAIRS/IMminGC/SEGNO/'
paths <- list_cell_seg_files(base_path)
files <- list_cell_seg_files(base_path)
pairs <- list(
c('CD3DN', 'AE1AE3'),
c('CD3DN', 'CD3CD4'),
c('CD3DN', 'CD3CD4FOXP3'),
c('CD3DN', 'CD3CD8')
)
write_images <- FALSE
touch_counts <- purrr::map_df(files, function(path) {
count_touching_cells(path, pairs, write_images=write_images)
})**
I get the following error message:
Error in touch_pairs[, 1] : incorrect number of dimensions
Called from: unique(touch_pairs[, 1])
Is there anything wrong with the script?
Many thanks.
Kind regards,
Athanasios

Your code looks fine. Are you using the latest version of phenoptr? If so, can you send me the cell seg data and segmentation map files that are failing? (Add cat(path, '\n') before count_touching_cells to see which one is failing; see my profile for email.)

Thank you for your suggestion. I found the error causing file pair and removed it. The script run fine after that.

This problem occurred when there was a single touching cell pair. Fixed with the above commit.

Thank you for the failing example. The error occurred when there was
exactly one touching cell pair. It is fixed now in the development version
of phenoptr. You can install this with
devtools::install_github('akoyabio/phenoptr@9000')
Thanks again,
Kent
On Tue, Apr 9, 2019 at 9:16 PM Athanasios72<EMAIL_ADDRESS>wrote:

Closed #4 https://github.com/akoyabio/phenoptr/issues/4.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/akoyabio/phenoptr/issues/4#event-2264621807, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AOFrjaLsQUylNgwH94EvwJ89XWLMJJUPks5vfTt3gaJpZM4cXD90
.

--
Kent Johnson | Principal Software Developer


If the user is not found, at least return the ID.

https://i.imgur.com/sw23Zpo.png

Hm, I'd rather have it consistently return User objects. There's likely a bug somewhere that causes it to not have the user object available at that time. Is there a situation where this happens consistently?

I would have to frequently deal with Ghost users, they can be intentionally made and controlled. Even the dj property on the advance event was undefined when one entered the booth. The plug front end code does a bulk request when an unknown ID enters the waitlist so they're at least visible in the room. Same reason guest count drops below 0.
Is there another way I can get the raw data of the waitlist update event instead? Cause an ID is better than undefined.

Ahh, i see. In that case let's default to user objects with just the user ID, so they still support all the methods like other user objects. That way library users don't have to type-check every result manually. Should be something like wrapUser(mp, { id: id }).

Ahh, good one. Just making sure, cause I'm not familiar with how this is made, but I'd need to get partial and the user model in the waitlist plugin?
Also, the only method that wouldn't work would be mention.

You'd need to get the wrapUser function for use inside the wrapWaitlist function, and then pass on the mp variable that's available in wrapWaitlist. For reference, the historyEntry data model also calls the User model in that way: https://github.com/goto-bus-stop/miniplug/blob/84f986fdad777e99885cf3535c6cc10881d4d9fd/src/data/historyEntry.js#L14

done :+1:

I think we should use the mp.user() result if it's available, and use the wrapUser way only if it's not. Can you make that change? Looks good otherwise :tada:

Sweet, thanks! :pray: I'm on mobile now so will release tomorrow.


using a non-existent file name with -m crashes with a traceback

Problem
Running tl in merge mode with a non-existent file path crashes with a traceback due to a FileNotFoundError
How to reproduce
Run tl like so:
tl -m badname1 badname2

Expected
When not in merge-mode, error notifications are popped up, so I would expect the same behavior.

Thanks. Should be fixed in 1.1.1


Tactician v2

I started working on v2

[ ] how to do debug command? With v2 the command handler map is not known in advance
[ ] tests
[ ] update readme
[x] should DoctrineMiddlewarePass, SecurityMiddlewarePass, ValidatorMiddlewarePass be part of this?

Hey, thanks for getting the jump on this. I confess I'm not using Symfony anymore so I was dreading this a bit. :sweat_smile:
To answer some of your questions:

My thought with the debug command is to use MapByStaticList instead. As I recall (and it's been a bit), the compiler passes built a static list of all the mappings ahead of time and then built it into a a ContainerBasedHandlerLocator. So, the MapByStaticList does basically the same.

The compiler passes for Doctrine, Validator and Security middleware could all be split out into separate packages (splitting out the Validator stuff into a separate package has been requested a few times). That said, I honestly didn't have the energy or patience for the additional package management work that would entail.

I see the tag based mapping/handling stuff was deleted in this PR but I think it might still be needed. Don't forget, the bundle has some other features base tactician doesn't have (yet) like detecting mapping based on typehints.

Also because I haven't written these down anywhere, here's my paper sketch ideas for Bundle 2.0

Let's only support modern versions of Symfony

Maybe we can move more of this out of the config.yml and more into the services.yml. Most of the work around the config.yml is just doing multiple command buses and adding middleware to them. These are tasks that I think would be better off in the services.yml where it's much simpler for folks to manage and work with them, instead of guessing at the autogenerated names (which are a repeatedly filed bug). The only services we need to auto generate then are the command locators, so maybe there's no need for the config.yml work at all.

Anyways, none of that second part is a hard contract, just something to keep in mind. :)

@rosstuck The problem with debug command is, that we know only handlers on container build.
The mapping happens in CommandHandlerMiddleware by running $this->mapping->getClassName($commandClassName).
We would have to implement reverse mapping and run handlers through it to generate mapping up front. Currently, I don't see a way to do it 🤔

I see the tag based mapping/handling stuff was deleted in this PR but I think it might still be needed. Don't forget, the bundle has some other features base tactician doesn't have (yet) like detecting mapping based on typehints.

I decided to revisit it when the rest is done. After looking into it for a while, does not seem that trivial.

Just to be sure, it's correct to drop service locator, amirite?


Fix the Cocoa releasability CI job

Introducing Xcode 9 / Swift 3.2 / Swift 4.0 support into our release packaging caused issues with CI. We appear to be hitting timeouts due to building all of the Swift versions for iOS taking over 40 minutes. In order to address this I've split the various Swift build steps so they can run in parallel. I've also taken this opportunity to restructure the CI job using a Jenkins pipeline using Groovy.
Remaining work:

[ ] Installation examples

This is now ready for review.

The assumption is that whatever commit is being built has already been tested via the CI jobs run on our PRs. For the most part the tests that are run are ones that test release packaging. There's a few exceptions designed to prevent obviously broken builds from being released (the macOS and iOS static tests).


Replace _underscore prefixed names in Delegate code

Now that major Delegate and Signal changes have been merged, we should update to remove underscore prefixed names, such as _Delegate.
Related: PR #319 for changes to the rest of the code base.

My suggestion here is to rename _Delegate to DelegateType. This should be done after PR #342 is merged, so as to avoid merge conflicts.


Edit the readme file

Readme file needs to be edited to be consistent with the Call for Code starter kit.

Going to close since we made many updates, thank you!


Support for AMP analytics

In Accelerated Mobile Pages, regular javascript is prohibited. Instead, it provides an amp-analytics tag with a lot of customizability.  Are you planning on supporting this?
https://www.ampproject.org/docs/reference/components/amp-analytics

Thanks for the link to APM analytics, Joren. I am currently not using it, but it sounds like a great feature. Would you be able to contribute an implementation?

@jcassee As much as I'd want to, I'm afraid I don't have the time to build such a feature, especially since it'll be a rather big feature.

I am not sure it would be a big feature, actually. The secret to this project is that it really does not do very much. :-) But I appreciate your time constraints.


DRILL-3535: Add support for Drop Table

@jacques-n uploaded patch with your review comments. Please take a look.

LGTM +1


Improve documentation

Added information for the README.md and the contribution guide

Coverage remained the same at 66.737% when pulling c62ef213eb4c8bafd3686b6324ef86fb43dc20ce on improve-documentation into dcf22ad3176762b010e8b93c027e2ed493018257 on master.


fix: implement validation for Dictionary names and keys

This commit updates our Dictionary implementation to ensure we throw nice error messages when given invalid dictionary names or keys, such as a name for a non-existant dictionary or a key that is too long.
I've also updated the xqd header to have an enum defined for the return codes of the host-calls as it makes it simpler to understand what each return code stands for.

This is currently blocked on this Viceroy PR -- https://github.com/fastly/Viceroy/pull/182


numpy random integration

This is the complete integration of the Numpy Random submodule from beginning to end.
Documentation: https://github.com/flojoy-io/docs/pull/124
Nodes: https://github.com/flojoy-io/nodes/pull/135
Python: https://github.com/flojoy-io/python/pull/45
Bug improvement:
While we have retained style conventions for how the manifest.yaml files should be written, autogenerating these nodes and the respective manifests have highlighted that studio is really sensitive to this formatting, and cannot boot successfully should things like tabs be \t and not spaces. I have implemented safer loading for all places where the yamls are needed (for example in the documentation generation, in generate_manfests.py, etc, to implement some sort of userproofing, to ensure user-generated manifests (that may not remember to keep the formatting) can still be recognized.

hey @trbritt
@JeffDotPng / @itsjoeoui / @mdasifhasan  can fill you in more, but i believe that this week they are merging a change to the nodes API that among other things, will create stronger typing and allow for multiple node inputs and outputs
some details here
https://flowjoy.slack.com/archives/C03KH05RZLK/p1687563713367559
your autogeneration pipeline will have to be tweaked at that point, so we may just want this PR to sit until then

hey @trbritt
@JeffDotPng / @itsjoeoui / @mdasifhasan can fill you in more, but i believe that this week they are merging a change to the nodes API that among other things, will create stronger typing and allow for multiple node inputs and outputs
some details here https://flowjoy.slack.com/archives/C03KH05RZLK/p1687563713367559
your autogeneration pipeline will have to be tweaked at that point, so we may just want this PR to sit until then

@smahmed776 Is this " change to the nodes API" complete?
@trbritt Should we move to resolve these conflicts and merge?

hey @trbritt
@JeffDotPng / @itsjoeoui / @mdasifhasan can fill you in more, but i believe that this week they are merging a change to the nodes API that among other things, will create stronger typing and allow for multiple node inputs and outputs
some details here https://flowjoy.slack.com/archives/C03KH05RZLK/p1687563713367559
your autogeneration pipeline will have to be tweaked at that point, so we may just want this PR to sit until then

@smahmed776 Is this " change to the nodes API" complete?
@trbritt Should we move to resolve these conflicts and merge?

Yes the change to node API is complete.


LongPressGestureHandler event payload inconsistent between ios/android

I'm trying to implement hold-and-drag interaction like this: user long press on an element, dragger appears under user's finger if long press active, then user could start moving the dragger by moving fingers.
Code below works fine on iOS, but not on Android. It turns out that the event payload is different for ios and android (android event payload didn't provide x, y, absoluteX, absoluteY, etc). Not sure if this is the expected behavior.
How to implement this interaction if there's no absoluteX to use?
handleLongPressGestureEvent = (o) => {
    console.log(o.nativeEvent); // move the element by o.nativeEvent.absoluteX
  }

 render() {
    return (
        <LongPressGestureHandler
          onGestureEvent={this.handleLongPressGestureEvent}
        >
          <View style={{height: 200, width: 200, backgroundColor: 'green'}} />
        </LongPressGestureHandler>
    );
  }

Event payload for ios
absoluteX: 137.5;
absoluteY: 335.5;
handlerTag: 1;
numberOfPointers: 1;
state: 4;
target: 4;
x: 50;
y: 102;

Event payload for android
handlerTag
:
1

numberOfPointers
:
1

state
:
 4

Hi, @chunghe
Thank for using this library.
Take a look on our docs here and here. In fact, there are some "extra" fields given on iOS but we do not document them and do not support. They were added cause their handling was extremely easy as they are given by iOS recognisers. However, they are not done yet on Android (maybe they will be added soon).
I advise to do it in another way. Let you use two GestureHandlers instead of one: you could add PanGestureHandler for dragging and LongPressGestureHandler(read about using many handlers simultaneously for your press interaction.
I do not consider your issue as a problem so I close it. If you still face some troubles, please, reopen it 😄.

Thank you! This is really helpful.

I'm trying to implement following interaction:
The screen is empty at the beginning,

user long-press at point A, a circle appears at point A
user's finger leaves the screen, circle disappears
user long-press at point B, a circle appears at point B

Do you think it's possible to implement this using react-native-gesture-handler? I've tried to implement this using PanGestureHandler + LongPressGestureHandler. But PanGestureHandler won't active if user just longpress-and-hold at one point, so at step 3, circle won't appear at point B.
Really appreciate if you could guide me a direction.

@chunghe
I see this and consider as problem which solves https://github.com/kmagiera/react-native-gesture-handler/pull/212
Suppose will be merged soon

@osdnk can you elaborate on how that solves the problem? I am struggling with the same problem and haven't found a solution.
@chunghe did you find a way to get it working?

Oh, well, would you mind opening new issue with this problem? My previous PR was quite a dirty workaround and decided not to merge.
And frankly speaking I totally forgot about it.

@computerjazz i gave up implementing that feature eventually :(. i think it's not possible ( at least to my knowledge ) using current version react-native-gesture-handler.

Done :)


schedule job to purge old PsCmdResults

There is no job to clean up old psCmdResults

fixed v3.3.3


feat: add hover popup to centroids and project features

refs #16

I also had the thought today that perhaps a hover popup could be configured as part of the feature service.

I wasn't able to find this. Is this a thing?

I wasn't able to find this. Is this a thing?

I'm not sure. Maybe it's an AGOL thing, not stand-alone server.


Update geo.py kwikqdrdist_matrix for nonsquare matrices

In equation for cavelat, "lata + latb.T" was changed to "latb + lata.T", such that it is possible to also have nonsquare matrices as inputs for kwikqdrdist_matrix. The result for kwikqdrdist_matrix with square matrices as inputs is not affected by this change.

Thanks, Christoph!


WIP Add dotnet core 3.0 support

Describe the changes you have made to improve this project
Support DotNet Core 3.0

[ ] Add target netcoreapp3.0 and use FrameworkReference Microsoft.DesktopUI for this
[ ] Disable paket (doesn't support netcoreapp3.0) and use package references
[ ] Change the SDK from MSBuild.Sdk.Extras to Microsoft.NET.Sdk.Wpf
[ ] Remove the sdk from global.json (so it takes the latest)
[ ] Add installing the SDK to appveyor.yml
[ ] Run all other targets (net45, net46, net47)

It's nice to see you already took the initiative, I unfortunately didn't have time yet.
Don't forget to replace build.ps1, your version is deeply integrated with paket.
If you need help, let me know!!!!!
P.S.
One thing I do need to mention, currently the dotnet core 3.0 SDK can some times be unstable!!
Using the latest might break your build...


Add eval to prebuilt dataset demo

This cl:
1- adds eval to prebuilt dataset demo
2- applies minor corrections to EvalFunc class and its test
TESTED= the unittest passes, demo runs successfully and the run_trec_eval.py script also runs successfully.

tracking issue: https://github.com/castorini/rank_llm/issues/89


auth: Log when a user tries to login with deactivated account.

Helps to see if users are often trying to login with deactived
accounts.
A use case: Trackdown whether any deactivated bot users are still
trying to access the API.
This implementation adds a new key inactive_user_id
to return_data in the function is_user_active which
check if a user_profile is active. This reduces the effort
of getting user_id just before logging.
Modified tests for line coverage.

Testing Plan:
Ran automated tests and modified tests to cover this logging

@timabbott could you take a look?

Great, merged, thanks @chdinesh1089!


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Topic wireframes issue#2

Ready for some feedback on the wireframes
Only difference between Add Topic/Edit Topic pages is that Add Topic doesn't have a status input field (since a new topic would be Active by default).
Let me know if I missed and fields or if you'd like to modify the design.

Re: ^^

Yes, please create user stories, I doubt there will be much there it's a very simple UI. There should be enough to cover pretty path testing of all functionality.

Let's prototype it, in my mind it was just a form exposed in the accordion. In general I'm not a fan of modal dialogs.

Sequence from the data perspective is just any value used for sorting. If I had a list of topics within a Path and I can drag items in the list to re-arrange them then the UI can adjust sequence under the covers. See here for an example of a draggable/sortable list. (NO I'M NOT PROPOSING JQUERY)

Auto-Save - on-change (on-blur) to any property, make an API patch call with only the property that changed.  The full updated document will be returned, so there is a pseudo-real-time-concurrency component to the pattern as well. See the person-ui for an example. - More specifically about the New Topic page, you only need a name on the initial POST api call, and you MUST have a unique name on that call, so only ask for that one value, after a successful POST you just switch over to the edit view.

@FlatBallFlyer  I added some basic user stories, and updated all of the wireframes. Ready for another round of feedback.
I haven't updated sequences yet because I wanted to clarify a couple more things. So the drag-and-drop sequence topics would displayed on the /topics/ page under the respective category. Is that correct? So based on this feature, would the edit topic page display a field for sequence or just default to put it at the end? Would using a number for sequence field be easier than a string for sorting?

It's looking good. Here is some more feedback:
Status
Since we only have 2 statuses (Active and Archived) let's just have a simple button, at the bottom of the form. If the status is "Active" the button is "Archive" and it changes the status to Archived. If the status is Archived the button says "Restore" and it changes the status to Active. When we implement RBAC this control will only be available for users with the "Staff" role.
Topic List view and Path Sequence
It seems to me like we need 2 list views (grouped by Category and grouped by Path). On the group-by-path view the items within a path can be dragged to a different place in the same path (Not between paths). When dragged the UI is responsible for adjusting sequence on as many topics as required and persisting those changes. The sequence would not be exposed in the edit topic view. If you want to change sequence to be numeric I'm fine with that, to do that you should open an issue on the mongodb repo, and the topic-api repo to make that change.
User Stories
I think of user stories slightly differently than you, I'm open to different ideas, but I like to use the Design Thinking approach to user stories. Every user story should start with a Needs statement, and then lists a series of steps... so something like this:
Mentors need a way to find a specific Topic by Category

Opens /
Redirects to /topics with by category layout
Clicks on Topic and opens /topic view

Mentors need a way to add skills to a topic

Opens /topic/OID
Clicks on +
Fills in new Skill

Mentors need a way to remove a skill from a topic

Opens /topic/OID
Expands Skills section
Clicks trashcan next to skill
Confirms delete
Form updates

It is also nice to have a slug to identify the need/story, so find a way to include that in the Markdown - maybe on the ## Line as in
add-skill: Mentors need a way to add a skill to a Topic

Also thinking about the add/edit a resource form - we could open that in a new page.... I don't know, it might be nice to be able to edit multiple resources at the same time (multiple tabs), and we might have people who want to view/edit a resource without navigating to the topic. What are your thoughts about this approach?

@FlatBallFlyer  Regarding your comments above, I like your idea and think it is cleaner to have the add and edit a resource on a separate page (wouldn't need to insert a form into the edit topic page). There could also be a link to 'Add a Resource' on the /topics page. The same could be done for skills as well. However, if we implemented this, we would need a new list, add, and edit route for resources (and skills), right?

I'm thinking that:

We need to have a /resource/[id] path that edits a resource. This will likely be used from other UI's that reference resources directly.
The add resource button in the Topic page does the post before hading off to /resource/[id] for editing. The Topic needs the resource ID.
No need for a list resource or skill UI - the Topic lists these
I think probably skills is the same, but it's such a simple object that maybe we do it in-place in the Topic.... I'm less sure about this part of the design.

@FlatBallFlyer
Pushed commit to this PR branch:

updated format for user-stories
created two different wireframes for topics with categories and paths
path view now has a path/sub-path dropdown to handle discussed changes to path hierarchy

Let me know your feedback, thanks!


Add new announcement

Added announcement for QF
We have to add another announcement for pick'em. Someone help me finish this plz as I have goucaode lecture this afternoon.

Todo: Add board and mappool information to this announcement


Add Python 3.10 to the supported versions

This pull request adds a CI build job with Python 3.10 and updates the package metadata.
Category (place an x in each of the [ ])

[ ] slack_bolt.App and/or its core components
[ ] slack_bolt.async_app.AsyncApp and/or its core components
[ ] Adapters in slack_bolt.adapter
[ ] Document pages under /docs
[x] Others

Requirements (place an x in each [ ])
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've run ./scripts/install_all_and_run_tests.sh after making the changes.

Need to upgrade pytest to 6.x to run tests in Python 3.10: https://github.com/pytest-dev/pytest/releases/tag/6.2.5


SST deploys lots of resources, when I really just want one stack (per stage) to be deployed

Is there a way to fix this problem? I was using the VSCode debugger, which was redeploying for me as I saved/made changes. Going along in this fashion isn't feasible.

.

Is the solution to eventually call sst remove to delete all those resources in one swoop when done developing? Side question, but does sst remove work when the stack changes (new resources/constructs are added) locally from what's been deployed, and a resource isn't found on AWS to delete. I've seen an error get reported, but I'm assuming it went ahead and deleted everything that was created that is part of the local stack code. Moreover, if a resource is removed from the local stack code, does sst remove know that it should delete the originally provisioned resource?

Furthermore, how can I verify if every resource created is actually deleted in AWS (or not deleted) as a result of running sst remove?

@riyadshauk Just from eyeballing those resources, are they not a part of your app? Can you share what's in your app?

Good point, my mistake, I think you're probably right.
And for checking which resources are actually there, this suffices for me for now https://console.aws.amazon.com/cloudformation