Using Stylus instead of Less ?

Stylus syntax is more powerful than Sass or Less and Stylus community is growing : https://github.com/stylus/stylus
If it could help, there are old tools to convert Saas/Less into Stylus files:

https://github.com/andreypopp/less2stylus
https://github.com/mojotech/sass2stylus
https://github.com/demsking/less2stylus-dirs

I don't know if they work well.

@InfoLibre Oh my friend) I am one of the stylus contributors. Yes, stylus is much richer than less, but it is very poorly supported by linters and IDEs. I even wrote my own https://github.com/stylus/stlint but it needs some work. + plugin for Idea is constantly breaking https://github.com/stylus/stlint-idea-plugin
So yes, I love the stylus, but no, I will not take it into my project

@xdan Stylus begins to be used by interesting projects, https://vueup.github.io/vue-quill/ and https://github.com/quilljs/quill are using it.
I'm looking for a Bootstrap alternative which is using CSS or Stylus. https://github.com/fomantic/fomantic-ui will perhaps add a Stylus version. For https://github.com/element-plus, I don't know.
I want to use Stylus in my project https://framagit.org/InfoLibre/rapido too.


Decode paths as VirtualPaths from -print-target-info output

This change decodes the paths in -print-target-info as VirtualPaths to simplify their use throughout the driver. This initial change is pretty small, but I think it'll make it easier to use the runtime library and resource dir paths reported by the frontend throughout the rest of the driver.
I thought about modifying the frontend so it always resolves these paths to absolute, but I think that would just create problems for distributed build systems in the future.

@swift-ci test

I made a couple changes in this version:

TextualVirtualPath is a small wrapper to make decoding VirtualPaths from strings easier
I added dynamic member lookup to avoid some unnecessary nesting when accessing members of FrontendTargetInfo.Paths
rebased on the new file list changes

@swift-ci test

@swift-ci test

@swift-ci please test

Oops, I forgot about this one. Let's see if the tests still pass
@swift-ci test


Addition of Sangram Rath as Meshery Maintainer, CI

Notes for Reviewers

This PR fixes an oversight in the welcoming of @sangramrath as a Meshery Maintainer, CI.

Signed commits

[x] Yes, I signed my commits.

Thank You all


Cherry-Pick to 4.15: Update macOS .yaml to vmImage: 'macOS-latest' (#6059)

Update macOS .yaml

Change mac vm image to macOS-1015

Fixes #6058

Pull Request Test Coverage Report for Build 282042

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 78.64%

Files with Coverage Reduction
New Missed Lines
%

/libraries/AdaptiveExpressions/BuiltinFunctions/GetNextViableTime.cs
2
90.91%

/libraries/AdaptiveExpressions/BuiltinFunctions/GetPreviousViableTime.cs
2
90.91%

Totals

Change from base Build 281330:
-0.01%

Covered Lines:
24818

Relevant Lines:
31559

💛  - Coveralls


LICENSE file missing

Open source projects usually have a LICENSE file to state the license under which it is released. Please add the LICENSE file so that we know which license it is. Since it contains code from Solana Labs, I assumed it's intended to be the Apache 2 license, same as Solana?

PR created


sub Element cannot response click event when scrollView is scrolling.

sub Element cannot response click event when scrollView is scrolling.

sub Element cannot response click event when scrollView is scrolling.


Combining floatThread with Zurb

I found this Zurb responsive table with a sticky column modification on Zurb foundation framework.
http://zurb.com/playground/responsive-tables
Would it be possible to combine with floatThread so a single table can have both sticky column and table header?
Best Regards

probably not, for 2 reasons:

This plugin doesn't work well on mobile safari (so I've been told)
I looked at their code, and they clone the table, and don't cache selectors - which means that my plugin will be upset when the table it ran on no longer exists.

see https://github.com/zurb/responsive-tables/blob/master/responsive-tables.js


Camera stream does not work with E1 Zoom

Describe the bug
I setup my camera and everything works fine, except for the camera stream itself.
The preview image works (see screenshot), but the detail view fails to load.
I also attached my config to this issue.
When I use the following manual config, it works without any issue:
- platform: generic
  username: admin
  password: !secret camera_password
  authentication: basic
  still_image_url: "http://<IP_ADDRESS>/cgi-bin/api.cgi?cmd=Snap&channel=0&rs=wuuPhkmUCeI9WG7C&user=admin&password=mypassword"
  stream_source: "rtsp://<IP_ADDRESS>:554/h264Preview_01_main"

To Reproduce
Use E1 Zoom and try to access the camera stream
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Settings:

(BTW I'm not sure what to put into the Custom thumbnail path field so I just put /, because otherwise the form would not save)
Preview:

Detail view:

Environment:
Please provide useful information about your environment, like:

Home Assistant version: core-2021.6.0
Reolink camera model: E1 Zoom
Camera firmware number: <IP_ADDRESS>_21040708

Additional context
I also found this error message in the logs:
2021-06-03 01:30:28 ERROR (MainThread) [custom_components.reolink_dev.base] Host <IP_ADDRESS> error renewing the Reolink subscription

I have a working E1 zoom. Here is a screenshot of my working configuration.


convert login screen to react

[x] convert UI to react
[x] connect API call to server

a login call reaches the server; I can see the server looking for the user. No users exist right now, so the login is always rejected.


Translate file "urls.md"

Notes for contributors, the file can be translated by being aware of and understanding the file you are translating, you must have an understanding of the techniques and the explanation provided by the documentation file, and it must be in Standard Arabic, and the technical terms should be translated as follows:
For example, المتحكمات with the term next to it in English (Controllers)
For example, التهجير and next to it the term in English (Migrations)
And so on
Thank you for your contribution

I'm on it

Ok, thanks for your contribution


Add quantity of alchemical bombs to actions tab

Previously you could not see the quantity of remaining bombs without going to the equipment tab. Someone good at css can make it prettier if they want.

This is going to break the moment we start splitting off from the stack on draw

Is there a better way to do it to avoid the future changes?
What other way can we make a count of bombs available on the actions tab?

Work out how to reconcile your PR with issue #4543

Actually, I am not sure that this fix has a direct link to that other issue.
This fix just lists a quantity for alchemical items on the actions page, it doesn't matter how many stacks you have or where they are, it just lists a quantity in each action link on the action page.
Nothing fancy.
In the following example I have two stacks in the weapons section and two in a bag, quantities show up correctly on the actions page. And when you throw a bomb, the quantity correctly decrements on the stack you are using.
I can potentially take a look at the linked issue, but I am not sure how it is linked to this fix.

Closing; feel free to reopen if/when above issue is addressed


Type definition policy

@twada I'm having trouble with the breaks of tests caused by types. Do you want to make the next test a type error?
declare const set: Set<0>;
assert(set.size === 0);
set.add(0);
assert(set.size === 1); // Do you want to make this line a type error?

The asserts type predicate makes a type error on the test. Do you expect the type definition to use asserts and break the existing valid tests?

Please use Node Assert API Type definition instead.

@twada It's impossible to apply the node type definitions to the power-assert library.

So you don't need to maintain @types/power-assert. Micromark also stopped using @types/power-assert and power-assert.

Just thought I should mention that if the expected value is typed as a number, you don't get the type error.
const size = 0;
assert(set.size === size);

// or

assert(set.size === (0 as number));


Update cloudwatch, sdk-core, ses, sns, sqs, ssm to 2.20.136

About this PR
📦 Updates

software.amazon.awssdk:cloudwatch
software.amazon.awssdk:sdk-core
software.amazon.awssdk:ses
software.amazon.awssdk:sns
software.amazon.awssdk:sqs
software.amazon.awssdk:ssm

from 2.20.130 to 2.20.136
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #2874.


Implement naive derivedFrom for peripherals

This implementation resolves derivedFrom reference and produces merged_peripheral which has:

name and base_address from target peripheral,
derived_from set to None,
all other fields are taken from base peripheral if not present in target one.

@japaric, I'll try to refactor and add a test to ci/run.sh this evening.

Also, if the deriveFrom peripheral is equivalent to the base one then we should just create a type alias of the base peripheral (type Derived = Base) instead of creating a new struct.

It's a good idea but requires refactoring of code generation (and user should be aware that he should also generate all structs for base peripheral), so I've implemented it in just quick & dirty way to avoid modifying src/lib.ru since branch auto was about to merge. But I will consider it for next iteration if src/lib.rs isn't going to change much to avoid maintaining quite a big patch.
Maybe svd2rust should have some kind of standalone mode when it generates all consts with base addresses and all structs in one pass to give user consistent result.

@phil-opp I think at least one of you also wanted/needed this feature. Have any thoughts on this approach?

Hmm, I'm not sure… The advantage of a new struct is that svd2rust outputs something usable for all peripherals.  For example, when I do a svd2rust -i STM32F30x.svd gpioi I get a struct that I can use directly, even if gpioi is derived from gpiod. On the other hand, it's not really a good idea to have different types for the identical gpioi and gpiod peripherals, since it makes writing generic code much harder (e.g. a method that operates on any gpio port).

Maybe svd2rust should have some kind of standalone mode when it generates all consts with base addresses and all structs in one pass to give user consistent result.

I tried to create something like that in embed-rs/svd_board (based on svd2rust). It auto-generates a Hardware struct that contains all registers from the svd file. There's also a hw function that returns a Hardware struct filled with the correct pointers.

On the other hand, it's not really a good idea to have different types for the identical gpioi and gpiod peripherals, since it makes writing generic code much harder (e.g. a method that operates on any gpio port).

It seems to be simple to extract common functionality when we are speaking of GPIOs which are very alike although there should be different structs. For example STM32F40x.svd have different reset values for GPIOA, GPIOB and all other GPIOx MODERs. For such cases one could provide common interface via trait.
It becomes a lot more difficult for common trait extraction if we are talking of timers. For example STM32F407xx have:

two 16-bit advanced timers (TIM1, TIM8) with complementary outputs, up/down/up+down counting, DMA requests and 4 CC (capture/compare) channels,
two 32-bit general-purpose (TIM2, TIM5) with up/down/up+down counting, DMA req and 4 CC channels; but TIM2 special internal trigger output from TIM8 and USB OTG and TIM5 has special timer input remapping;
two 16-bit general-purpose (TIM3, TIM4) with up/down/up+down counting, 4 CC channels;
two 16-bit general-purpose (TIM9, TIM12) with up counting and 2 CC channels but without DMA req (and they do differ by maximum clock frequency);
four another 16-bit general-purpose (TIM10, TIM11, TIM13, TIM14) with up counting and 1 CC channel and without DMA req; also they have different max frequencies for input clock;
two 16-bit basic timers (TIM6, TIM7) with up counting, DMA req and without CC channels at all.

I truly cannot imagine set of automatically generated traits to support at least half of these functions only from SVD file even for very narrow class like STM32-only. And it's totally out of SVD scope.
And in case of not generating (or writting) such traits we will anyway generate different structs for say TIM1 and TIM6 but TIM1 obviously could be used in any place where TIM6 can be. So there should be trait for basic timer, I guess. But what traits could be generic and flexible enough to describe that it can be used as source to start ADC?
Also I think that such traits should be defined in separate crate and their implementations should be defined in repos like japaric/f3.

The advantage of a new struct is that svd2rust outputs something usable for all peripherals.

I'd be OK with e.g. svd2rust -i $F gpioc just outputting type Gpioc = Gpiob because right now it just errors :-).

it's not really a good idea to have different types for the identical gpioi and gpiod peripherals

I agree 100%.

I tried to create something like that in embed-rs/svd_board ..

I'd like to have an option to generate code for ALL the peripherals in svd2rust in the future, when it's able to handle both derivedFrom and register arrays.

For example STM32F40x.svd have different reset values for GPIOA, GPIOB

Those should have different types.
Two peripherals should only have the same type if the only different between them is name and baseAddress.

For such cases one could provide common interface via trait.

I think generating such traits is out of scope for svd2rust.

I'd be OK with e.g. svd2rust -i $F gpioc just outputting type Gpioc = Gpiob because right now it just errors :-).

As I see user usually generates code for GPIOs and wraps it to different modules to separate different registers with same names. E.g. Moder for GPIOA and GPIOB having different reset values.
In your example user should import Gpiob to such module manually because svd2rust doesn't know how user wraps its output.

As I see user usually generates code for GPIOs and wraps it to different modules to separate different registers with same names.

You are right. Then let's punt this type alias stuff until when svd2rust has a "generate everything" feature. Let's just "duplicate" the structs of equivalent peripherals for now. As the users are mainly using this manually or via a shell script they can just avoid generating duplicated structs and do the type aliasing manually.

Thanks, @grossws!
@homunkulus r+

:pushpin: Commit e94b369 has been approved by japaric

:hourglass: Testing commit e94b369 with merge e94b369...

:sunny: Test successful - status-appveyor, status-travis
Approved by: japaric
Pushing e94b369d73b9d8fdf9b8e0b54cf9fe1fe2c9291b to master...


mp4: Improve readability and maintainability

Thanks!
Just a note for https://github.com/Serial-ATA/lofty-rs/pull/268/commits/97dfeb4c38b7131c9113a7c22893788e674beb4d, I tend to prefer the late init style of:
let foo;
if cond {
    foo = ...;
} else {
    foo = ...;
}

As opposed to collapsing it into:
let foo = if cond {
    ...
} else {
    ...
}

Thanks!
Just a note for 97dfeb4, I tend to prefer the late init style of:
let foo;
if cond {
    foo = ...;
} else {
    foo = ...;
}

As opposed to collapsing it into:
let foo = if cond {
    ...
} else {
    ...
}

That's fine too and probably slightly more readable. I just try to avoid mut whenever possible.


1250 divisions verifications

https://github.com/edenlabllc/ehealth.api/issues/1250

Changes Unknown when pulling 42b908a3111e90b5a61c7fe10a9227f8dd5fa3ed on Ehealth-1250-Divisions-Verifications into ** on master**.

Coverage decreased (-0.01%) to 90.136% when pulling fdaf7388b82eb3edf6f3989bd83e8e4c686844d4 on Ehealth-1250-Divisions-Verifications into 9b747797fe21fd8d6af60755f01b1e46a1d1d90b on master.

Coverage decreased (-0.01%) to 90.136% when pulling fdaf7388b82eb3edf6f3989bd83e8e4c686844d4 on Ehealth-1250-Divisions-Verifications into 9b747797fe21fd8d6af60755f01b1e46a1d1d90b on master.

Coverage decreased (-0.01%) to 90.136% when pulling 82e37dd5f8e81c3deaedbb4a732a46a7221fd10b on Ehealth-1250-Divisions-Verifications into 9b747797fe21fd8d6af60755f01b1e46a1d1d90b on master.


match expressions

Also does empty blocks and continue (badly).
I was at first happy with how easy this was, then disappointed by how much code it took to get things right. I think we can do better with the abstractions we're using, but not sure how yet...

Going to bed now, I'll have another look at the implementation tomorrow. Looks very good so far!

@marcusklaas needed to tweak formatting of binops somewhat to fix the bugs that match exposed. Addressed all the other comments too. Most are in the last commit, some got folded into the second to last. Could you have a review pass of the last commit please?

r+, although I do think match should eventually adhere to the expression indentation configuration.
    let function_call2 = function(aarrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrg1,
                                  match self {
                                      Character::Ninja => 2,
                                      Character::Pirate => 1,
                                  });

is now always formatted as
    let function_call2 = function(aarrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrg1,
                                  match self {
            Character::Ninja => 2,
            Character::Pirate => 1,
        });

, which we may want to change. But that can be done in a later PR.


[README] Update supported operating systems and compiler version

Description
This PR updates the section of "Supported Operating Systems" and compiler version in README to align with our test matrix.
Note that although the breaking commit 96d744f has been resolved by the commit ea7ba1b, between the two is another breaking commit 82c5a83 that bumps the sycl library version. Hence it still requires a commit before 96d744f.
Checklist
All Submissions

Do all unit tests pass locally? N/A, only updating README.
Have you formatted the code using clang-format? N/A, only updating README.

@hjabird I brought back the version table with the Conan-related columns deleted and some version updates. Please let me know if you have objections.
@mmeterel Could you please take a quick look?

@hjabird I brought back the version table with the Conan-related columns deleted and some version updates. Please let me know if you have objections. Sorry I didn't check earlier...

Looks good to me.


feat: Add sonar workflow

This PR introduces the initial version of the SonarCloud workflow. https://github.com/MudBlazor/MudBlazor/issues/9236

Analyzes MudBlazor, MudBlazor.SourceGenerator, and MudBlazor.Analyzers projects.
Requires secrets from the calling workflow.
Doesn't depend on any other workflow.

Not included

This PR does not include any code coverage-related features.

The calling workflow currently looks like this:
name: sonar

on:
  workflow_dispatch:
  push:
    branches:
      - dev

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

jobs:
  analyze:
    name: Analyze
    uses: MudBlazor/Workflows/.github/workflows/template-sonar.yml@main
    secrets: inherit

I thought we were replacing codecov to have only one comment in the PR?

I thought we were replacing codecov to have only one comment in the PR?

I proposed another idea (https://github.com/MudBlazor/MudBlazor/issues/9236#issuecomment-2211718970) to start without PR decoration initially. So we can configure SonarCloud to our needs and gain some experience of working with it.

I thought we were replacing codecov to have only one comment in the PR?

I proposed another idea (MudBlazor/MudBlazor#9236 (comment)) to start without PR decoration initially. So we can configure SonarCloud to our needs and gain some experience of working with it.

Sorry missed it.
In that case I see no reason not to merge.

You could add codecoverage and leave codecov in place

You could add codecoverage and leave codecov in place

It would require some adjustments for the dotnet test command. For instance, I used /p:CoverletOutputFormat=opencover instead of /p:CoverletOutputFormat=cobertura and I removed /p:Include='[MudBlazor]*'. I think it would also work with cobertura format, but I never worked with this before.  I don't know what the benefit is to set /consoleloggerparameters:NoSummary so I removed this as well.

@mikes-gh please merge if you are satisfied

@mikes-gh probably on vacation?

Please let me know if there's anything I need to do to get this PR ready to be merged.
I intentionally chose the approach without the PR decoration so that we can get some experience with SonarCloud.

Basically the worry was that it might strain server resources. We'll try and evaluate.

Basically the worry was that it might strain server resources. We'll try and evaluate.

The current execution time is about ~ 2:50 minutes, which should be ok IMO. The project is large, that's why it takes some time. However, only MudBlazor, MudBlazor.SourceGenerator, and MudBlazor.Analyzers will be analyzed currently.

Thats fine I thought it was a lot longer.  It runs concurrently and we don't may for resources so there is no delay in getting all checks passed since other checks take longer


Fuzzy search for dictionaries

(Mentioned by @suhasm on Discord.)
Many people aren't familiar with transliteration. So it would be useful if they could type "rama" and get results for "rāma".
Possible approaches:

Automatically search dictionaries for all matches (ramā, rāma, etc) — I've seen some sites do this. I personally find it annoying but it may be ok.
When typing in a word, show possible "actual" transliterations (in an Indic script) so that the user knows what they're searching for, like Google Input Tools (or just integrate it?):

Some combination of the two: when they type in a word, show all matches that correspond to actual headwords in any of the dictionaries, so that they can pick the word before searching.

Of these, I think the second option sounds most compelling.
Philosophically, though, my controversial take is that a user having to look up a word manually is a failure, because it means:

the text they want to explore isn't on Ambuda.
or, we have the text but they can't find it.
or, there isn't a place for them to paste in their content, so instead they have to look up words one by one.

Students won't know whether the citation form of a word uses "n", cerebral-n (R), or "m", or some other nasal. Especially after removing an upasarga that contains one of the "r" vowels or consonants, and so on.  What I have seen, as a second year student of संस्कृत, is that the online tools are all too rigid for beginners. Even after properly unwinding sandhis, different tools fail for different reasons.  Consider using regex character sets like [ ङ् ञ् ण् न् म्  M] (where 'M' represents Anusvāra) for any nasal - of course, for speed, tricks (such as memorizing expanded-match patterns in unique-string space) must be employed.  Panini rules allow several optional additions and removal of characters, so here too, mapping to a regex type string that gives a unique pattern to recognize the legal variations might work wonders.
Which source modules would one look at to understand core dictionary data and for adding search APIs?

@camsanders welcome! Thank you for the astute comment.

Which source modules would one look at to understand core dictionary data and for adding search APIs?

I'll first answer for the world we're in now. Then I'll sketch a direction I'm quite excited about.
First, where we are now. We do some level of basic normalization, but we can go much further.

The main template / view logic is here.
In particular, we construct the set of search keys here.
Within that function, we normalize dictionary keys like so.

The transliteration format we use internally is SLP1, which is more amenable to computer procenning. You cand find a definition of the schema here.
Dictionary entries themselves are defined here We populate these tables with the seed scripts here.
We provide active onboarding support on our Discord channel, and we are currently working on improving our onboarding process as well.
Next, the direction I'm quite excited about:
I completely agree that it's unreasonable to expect students to know the conventions of citation forms. Even now I find myself tripped up on remembering, e.g., that the Monier-williams convention is to the anusvara before a consonant except if that consonant is प/फ/ब/भ.
The deeper problem, however extends beyond lemmata: often, it's not even clear what the citation form should look like. I can't imagine the pain a beginner would have in looking up words like श्यति (citation form शो) or संचस्क्रुषी (citation form संस्कृ).
So, what if we could generate all words with variant spellings ahead of time? If we can combine a Paninian word generator with a memory-efficient dictionary, we could look up words much more directly. And if we combine such a system with a fast segmenter, we could even allow arbitrary phrase search.

A wonderful reply! Thank you for the information. SLP1 - good choice! Thank you for the links. Perhaps we can take this discussion private briefly, and create some Future Vision pages in the wiki? Or start a thread with a more fitting title.
As to the vision, Beautiful!! That is/was the vision a friend and I had/have - although we are also wanting to build a scholar reviewed gold-standard, normalized Dictionary. We were starting to spec out a new project, and decided to survey the landscape and see if we can build on any projects, or join one. This project and the python sanskrit_parser jump out at me. You have several things that we want: crowd sourcing the annotations of documents, etc.
As I go through M.R. Kale's 2022 "higher sanskrit grammar", there seem to be quite a few optional rules, and so to forward calculate/realize the full set of permutations (the fan-out of legal realizations), I started seeing more factors of 2 than I expected. I believe there are at least 2 more zeroes in that data set than my original calculation, and we are definitely moving way into the billions of entries with multiple upasargas, and quite likely then, multiple link-backs to dhatus with use-case specs (padas). (The latter point also hints to more redundant-matches of unlikely-manifestations than are found in nature.) Of course, using associative lookup techniques, with electronic-disks, size is still not a barrier. Tho with the data size going up and the redundancy of matches and I am simply starting to question the value of this path. [Tho not hard to experiment with, and worth exploring!]  It still doesn't address the fuzzy matching problem.
In the short term, an adaptive system could be built. [the following is mostly regarding pada lookup, but some applies to shlokas too.] The fast extended "use index" should be built from actual usage.  (Whether usage comes from a user typing in a string, OR from automatically parsed documents.) When there is a hit, return it (and/or the list of options, which contains use-case info for each option). When there is a miss on a word lookup, then parse it, and if there is a hit with a pada, then add this variation to the use-index. If nothing is found  then  parse again after adjusting for potential errors made during sandhi-reversal and/OR go to extended automated pattern matching. Try really hard to give the user something.
Anything not found with some kind of perfect match should be put in a list for scholar review; anything found with thesthe above search-variations should be included in that list. Maybe we have the user confirm they are human, and type in a phrase indicating context, e.g. "asthanga hrdayam", or "yoga student". The scholar-review-list would be sorted by most frequently used/searched missed-items, and then the scholars can approve appropriate matches for real-world "use index".
E.g. beginners should be able to type , intentionally without Roman diacritical notation, these types of entries: sanskrit samskrit sanskrut sanskrta etc   !  These (and many more) common beginner errors should be added to the use-index.
Interest in Ayurveda and the Vedas is growing in the USA. I would like to make learning & understanding easier for them. So it would also be nice for the user to see maps from words back to the various source docs. Monier-Williams has many references, but in the sites I use, they are not traceable links.

One more point that is obvious to the experienced developer: any of what I suggested can be controlled by user-preferences. It would be nice to have a user profile (even with browser-session) options for the extent of searching, etc. Continuing, it would be nice to have content-access authorization for commentaries on various texts at the shloka level - and ideally,  provide a means that content providers can have that content maintained on their own server. Perhaps a subscription system could pay for some work and/or cost of keeping servers online.

Thank you for the links. Perhaps we can take this discussion private briefly, and create some Future Vision pages in the wiki? Or start a thread with a more fitting title.

For wider circulation, let's use the ambuda-discuss mailing list:
https://groups.google.com/g/ambuda-discuss
If you start a thread there, we can use it to continue our discussion.


Feature Request: Accessible Background Div

This might be a long shot, but here is my proposal:
A while back I stumbled over this reddit thread
And I found it a neat idea to be able to influence the background of my lovelace instance. I tried the Gif option to give the background some life. Gifs are however a horrible option since they either explode in file size or lack in terms of quality.
The best Alternative would be using an mp4. This solution would require some absolute positioned container in the background which could house the  element. Or maybe someone wants to use this container to create some css animations.
And maybe someday a cinemagraph like this or this could be our lovelace backgroud.

Safari supports setting mp4 files as background-image in CSS. Example: https://codepen.io/bradleytaunt/pen/JLgrag/
I don't think that at this point in Lovelace would I want to add such a feature. We first need to focus on getting it the default in Home Assistant.

Here's the current steps required for a background mp4: https://community.home-assistant.io/t/lovelace-animated-background-based-on-entity-state/132208
It'd be awesome to see a directly supported way to do this in HA, but I understand current priorities are elsewhere.

@bramkragten this should be possible after your changes to view, correct?

MP4 as background? No, only css allowed. So still only for browsers that support mp4 as background image.


Editor doesn't load properly after editing a published file

Seems like a bug where, after you edit a published graph via the pencil icon, the editor sits there without playing, displaying nothing. On reload, works ok. Most recently had this in Safari, but think i had it in Chrome too.

this seems to be fixed now so gonna close it

Just had this problem again (Safari), opening this graph via the edit icon.
http://vizor.io/matt/rocket-button-test/edit

Getting this problem quite regularly now (files that load for me first time are becoming the exception, and i'm beginning to expect to reload every time i open a file). This morning was on Kaarlo's branch, but happening on all branches for me i think. Any ideas on this one ?

Still happening? I'll keep a look out as well, i think it does happen to me sometimes.


ampx generate forms should supported nested "customType" fields

Environment information
System:
  OS: Windows 11 10.0.22631
  CPU: (24) x64 AMD Ryzen 9 7845HX with Radeon Graphics
  Memory: 6.25 GB / 31.19 GB
Binaries:
  Node: 20.12.1 - C:\Program Files\nodejs\node.EXE
  Yarn: undefined - undefined
  npm: 10.5.0 - C:\Program Files\nodejs\npm.CMD
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/backend: 1.0.0
  @aws-amplify/backend-cli: 1.0.1
  aws-amplify: 6.3.6
  aws-cdk: 2.140.0
  aws-cdk-lib: 2.140.0
  typescript: 5.4.5
AWS environment variables:
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_PROFILE = hurtec-dev
  AWS_SDK_LOAD_CONFIG = 1
  AWS_STS_REGIONAL_ENDPOINTS = regional
No CDK environment variables

Description
In a Schema, when you create a customType for nested data, then run npx ampx generate forms, the generated forms will only have input fields for the types on the root level, not the custom type. For example if I have some Device which has gps information, I might structure the data like this:
    Device: a
      .model({
        tenantId: a.string().required(),
        name: a.string().required(),
        status: a.string(),
        gps: a.customType({
          lat: a.float(),
          lon: a.float(),
          spd: a.float(),
          acc: a.float(),
        }),
      })
      .identifier(['tenantId', 'name'])

I will get text boxes for tenantId, name and status, but nothing for the gps data. It can be beneficial to model data like that for other reasons, but at the moment it means you lose the ability to have working forms generated.
As a feature request: I expect it to generate a form with fields for the nested data, possibly in a fieldset or with a heading separating them.

Hey @nootn, thank you for reaching. Marking this as feature request for customType  enhancement on form generation.


Update documentation link in README to point to plugin docs

Hi!
I've found it annoying that my browser history (which points to go-vela/vela-terraform on GitHub) doesn't get me to the Vela Terraform Plugin docs in one click.
Currently, I have to go to the overall Vela docs and then traverse the navigation menu to find the Terraform docs.
This PR is a suggestion I think would be helpful; merely to link directly to the Terraform plugin's page on the docsite.
If there's a reason this hasn't been done before, I'm all ears.
Thanks!

Whoops, opened https://github.com/go-vela/vela-terraform/pull/138 which is what I meant to do instead of PRing against my own fork.


Update rxFS2.js

Add Translation

extension source code must not be minified

also, we do not really want extensions to be translated by hand. we will automate it and send it to the translators that do the rest of our websites. this is fine for now though

extension source code must not be minified

Why?

Lint wrong.

extension source code must not be minified

Why?

Readability.

Per the GPLv3 that all files in this repository must be compatible with, the "preferred form of the work for making modifications to it" must be made available

I fixed a format error.

also, we do not really want extensions to be translated by hand. we will automate it and send it to the translators that do the rest of our websites. this is fine for now though

I think we can add both the native language and English.

due to some bugs in turbowarp desktop v1.7.2-beta.1, we will have to wait a bit for this

We will tolerate these manual translations from native speakers for now as a way to test the l10n system
Other contributors: please do not start writing translations by hand for languages you are not fluent in!


Add a '$singleton' option for graph points to keep only the latest single record

Many times a graph point is intended to only have one record stored, never multiple. If we added a '$singleton' boolean option it would allow the dev to specify that an object in the graph was to only have one record, the latest one, kept and all others discarded. Thing of the case of having a blog protocol where you have an index html record where you only ever want one, don't really care about the recordId, and just want the latest kept. The $singleton option would make that possible.

Can $singleton apply to records other than the root record?

If yes, how does that work? Say foo/bar is a $singleton. Can there only ever be one record at path foo/bar across contexts? If I try to write a new foo/bar, does that get rejected or delete the existing foo/bar, which may be in a different context.
If no, we need to validate upon protocol ingestion. It seems like the point of $singleton is to restrict a protocol to only one context.

I want to unpack this phrase just want the latest kept. If I have $singleton for protocol path foo, and a tree of descendant records below it, will writing a new record to path foo delete the entire existing tree? That's pretty drastic and dangerous behavior.

I've been working on how this would work and have some WIP PRs around it.
As discussed with @csuwildcat and I believe suggested by @diehuxx, a "$keep" property that is a positive integer greater than 0 rather than a "$singleton" property to only denote 1 would bring better flexibly.
Some thoughts on @diehuxx's questions above:
Yes, I think"$keep" records should be able to be nested.Currently when a new record is written the older ones are purged.
However the reject path is also interesting, and I could see how that might be useful. Maybe behind a protocol definition property that denotes the behavior of $keep, with default being purge. Maybe something like this:
"$keep" : {
    "limit" : 1,
    "strategy": "purge" | "reject"
}

For anything that is a child of a protocol context, the parentId and contextId are required upon creation of that record, currently I "$keep" the limit number of records within that context.
So you could have "foo/bar" with a a "$keep" limit of 5, you would then keep 5 "foo/bar"s for each parent instance of "foo".
If you had 5 "foo" records, you would then have a total of 25 "foo/bar" records.
If you query only on protocolPath 'foo/bar' without a contextId you will get all 25 records.
Would like to get some input on this.

@LiranCohen Looks good!
We discussed at office hours. I'll summarize:

I like the name $keep and the structure you proposed.
We should leave out strategy for now. reject isn't worth implementing now (ever?). The inevitable DevEx for reject is bad because.
My remaining concern is about how to implement in a way that accommodates sync. In particular how to make purging a record tree performant. When a record is purged, all of its descendants in the protocol are also purged. When purged, the record and its descendants must be deleted from the event log. How do efficiently we get the message CIDs of all descendants?

Or maybe just $limit as it was originally brought up?

@thehenrytsai I think they like keep because it implies purging/retention.

@csuwildcat, I see, fair, so: $keep: 1 seems reasonable.

Could be related to #786.


Cannot find module 'eonasdan-bootstrap-datetimepicker'

We recently took an npm dependency on v1.0.4. When running 'ember build -w', I am seeing the following error:
Cannot find module 'eonasdan-bootstrap-datetimepicker'
Error: Cannot find module 'eonasdan-bootstrap-datetimepicker'
at Function.Module._resolveFilename (module.js:339:15)
at Function.require.resolve (internal/module.js:23:19)
at Class.module.exports.treeForVendor (/home/eddie/dev/cooltrax/refresh/node_modules/ember-bootstrap-datetimepicker/index.js:59:38)
I think this means it needs to be promoted in the package.json from devDependencies to dependencies, right?

ember g ember-bootstrap-datetimepicker


(node:30264) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56 parseQuery() will be replaced with getOptions() in the next major version of loader-utils.

Is this package going to be maintained or should we use a replacement? @ngtools/webpack is great for AOT, but for webpack-dev-server it is not good and breaks things, so we have been using your loader with others like this.
 /**
                * JIT DEV BUILD
                */

               : [{
                  loader : 'cache-loader',
                  options: cacheLoaderOptions
               }, {
                  loader : '@angularclass/hmr-loader',
                  options: {
                     pretty: !isProduction,
                     prod  : isProduction
                  }
               }, {
                  /**
                   * Lazy Module loader
                   *  MAKE SURE TO CHAIN VANILLA JS CODE, I.E. TS COMPILATION OUTPUT.
                   */
                  loader : 'ng-router-loader',
                  options: {
                     loader: 'async-import',
                     aot   : AOT
                  }
               }, {
                  loader : 'thread-loader',
                  options: {
                     // there should be 1 cpu for the fork-ts-checker-webpack-plugin
                     // workers: require('os').cpus().length - 1,
                     workers: isDevServer
                        ? 3
                        : require('os').cpus().length - 1 // fastest build time for devServer: 3 threads; for production: 7 threads (os cpus minus 1)
                  }
               },

                  {
                     loader : 'ts-loader',
                     options: {
                        // disable type checker - we will use it in fork plugin
                        transpileOnly: true,
                        happyPackMode: true
                     }
                  }, {
                     loader: 'angular2-template-loader'
                  }]

But now we are receiving:
(node:35524) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
    at Object.parseQuery (C:\Source\frontend\node_modules\ng-router-loader\node_modules\loader-utils\index.js:78:3)

Is there a fix?

+1


fix: removed old JWT registration

Codecov Report

Merging #103 (5701ce6) into main (1a62325) will increase coverage by 14.31%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main     #103       +/-   ##
===========================================
+ Coverage   67.49%   81.81%   +14.31%
===========================================
  Files          48       48
  Lines        1246     1259       +13
  Branches       72       72
===========================================
+ Hits          841     1030      +189
+ Misses        353      176      -177
- Partials       52       53        +1

Impacted Files
Coverage Δ

...ataHub.MessageArchive.EntryPoint.WebApi/Startup.cs
28.23% <ø> (-5.10%)
:arrow_down:

...ssageArchive.Processing/LogParsers/LogParserXml.cs
95.55% <0.00%> (+4.44%)
:arrow_up:

...chive.Processing/LogParsers/Utilities/ParseTags.cs
94.44% <0.00%> (+11.11%)
:arrow_up:

...ve.Reader/Models/SearchCriteriaValidationResult.cs
100.00% <0.00%> (+16.66%)
:arrow_up:

...chive.Processing/Handlers/BlobProcessingHandler.cs
100.00% <0.00%> (+21.62%)
:arrow_up:

...hive.Reader/Validation/SearchCriteriaValidation.cs
92.30% <0.00%> (+33.33%)
:arrow_up:

...ssageArchive.PersistanceModels/ParsedErrorModel.cs
100.00% <0.00%> (+33.33%)
:arrow_up:

...ssageArchive.Processing/LogParsers/ParserFinder.cs
95.45% <0.00%> (+54.54%)
:arrow_up:

...ocessing/LogParsers/ErrorParsers/XmlErrorParser.cs
57.14% <0.00%> (+57.14%)
:arrow_up:

... and 5 more

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


Drop Botan.io support

😢

Why are you dropping Botan.io support?

@Wowu looks like Botan.io doesn't work anymore.
It responds about a minute and returns 504.
Are you using it?

Botan seems abandoned and we don't want keep it in the gem.


corsixth 0.60 (new formula)

A formula I tested a while ago, then somehow lost in memories. It at least worked on my machine with demo game files. There is no test as usual for bundle apps.

@BrewTestBot test this please

Looks good.
Merged. Thank you for your contribution to Homebrew!

@tomyun is there a way we can reach you to coordinate future releases @CorsixTH?

@TheCycoONE you may open an issue here at homebrew-games tap to let us know when new releases coming close and we can get ready to update the formula.


Bigfix in filter_colmap.py

The folder {source}/masked_image  is non-existent in filter_colmap.py:192. The actual folder is {masked_image_dir}.

Thanks for fixing it!


Misplaced map label

For the following Brunel, a map label is in the upper left corner.  It is likely misplaced and does not respond to a drag.
data('sample:US States.csv') map x(State) color(Income:blues)  + map(labels) + data('sample:airports2008na.csv') x(Long)  y(Lat) size(Flights:500%) legends(none)

Graham fixed this


[SPEC] Forego simplecov-html reporting to ensure Coveralls posts

I'm currently stumped on trying to get both simplecov-html and Coveralls to play nicely together, despite documentation that leads one to believe that they are best friends.
For the time being, I'm giving up on my recent attempt to introduce simplecov-html.  It's more important to ensure that the CI-based code coverage is restored and continues to work.

Content-wise, this PR seems to be sound.  However, I'm afraid that there's some conflicting state with the Coveralls service and I need to figure out what that is.  I assume that this is the unfortunately side-effect of my trying to trigger Coveralls locally from my machine.

Closing and re-opening just to give Coveralls a fresh start.


JAMES-3715 Small cleanups following Netty 4 migration

Cc @ff-wl I'm  interested by your feedback...
Playing around with the code resulting from the Netty 4 migration ( https://github.com/apache/james-project/pull/886 ) I realized:

That the threading model was further simplified than I thought (which is good!) and that we could get rid of a few configuration options and of a few extra classes (yeah!)
That some ssl related options were leftover
And that the ioWorker option was no longer applied while we easily could.

@ff-wl feel free to cherry-pick the commits.

Cc @ff-wl I'm interested by your feedback...
Playing around with the code resulting from the Netty 4 migration ( #886 ) I realized:

That the threading model was further simplified than I thought (which is good!) and that we could get rid of a few configuration options and of a few extra classes (yeah!)
That some ssl related options were leftover
And that the ioWorker option was no longer applied while we easily could.

@ff-wl feel free to cherry-pick the commits.

looks good for me. I've cherry-picked all commits and will push them to the #886 branch.

My bad https://github.com/apache/james-project/pull/899/commits/f7f0c182ee1260d330ad2ed974bd07f9f1e07436 should be removed from here: it is a mistake... Sorry...


How to Change the Incident Name

I am using the default configuration, I just used the dispatch-docker repo to deploy dispatch and load the sample Postgres data, configuring the slack integration.
After I am creating the incident using the web UI, a Slack notification is triggered and the channel is created in Slack but the incident name and the slack channel name is auto-generated as you can see in the screenshot attached.
Looks like it follows this naming-convention  [ dispatch-<org-name>-<project-name>-<number> ]
e.g:- dispatch-default-zfh-project-7
Can we change this naming convention anyhow ??

@kevgliss , can you please help here

@tarunm97 The incident name is currently controlled by the ticket plugin you have enabled. For instance, if you have jira enabled then the Jira ticket name will be the incident name. If no, ticket plugin is enabled the default is to use Dispatch's ticket plugin:
https://github.com/Netflix/dispatch/blob/master/src/dispatch/plugins/dispatch_core/plugin.py#L223
We don't currently allow this string to be configured in the Dispatch plugin (I'd be interested to know what naming scheme you were thinking of). But, depending on your requirements you could similarly create your own plugin to generate whatever string you'd like.

It is great to hear from @kevgliss , but we can make this a parameter, so users can enter what they want, and we should not hardcode the ticket-name, which I believe to be an important identifier. Thanks for the code-reference


RoaringBitset.Set(int start, int end, bool value) is inconsistent

Sometimes using RoaringBitset.Set(int start, int end, bool value) gives wrong results depending on the values of start and end...
The same call with RLEBitset works....

Thanks for the report! Opened a PR for this.


Configuration mode to eliminate attachments and camera?

I don't see a way to push a ChatView into a text-only or text-and-audio-only mode. Is this a reasonable feature request, or am I missing something?

Hey @rnewman, seems like a rather unusual request. You could pass your own input view builder without image adding button to achieve this. But if more people need it, I'll consider adding this if I have time. Have a nice day

Got it — thanks for the quick response!

Hey @rnewman, we've added this feature in version 1.3.7, you are most welcome to check it out. Have a nice day

That's awesome! I need this feature!


Single vidoe loading in data_loder.py, Annotation and Demo video making

It is not super fancy but it works and I have made sure that change to the data_loder.py can be turned off so it should not affect anything other than the making of Demo video in OpenCV.
I have done the video in openCV for now but I am hoping to update this soon

I'll work on the conflict in the weekend :)

There were a few conflicts because both we modifieddata_loader. There was no need for 2 data lodaers, thus I created one (no seperate loaders for train and validation). Can you verify I merged your code right?


Use imported protobufjs in toproto3json.ts

Description
Ran into a couple issues with conflicting types / packages because protobufjs was not being imported locally. This meant it was using the global namespace before.
Checklist
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

@googlebot I signed it!


Update to MXNet 1.2

This PR updates Sockeye to MXNet 1.2 which was released May 21st 2018.
Core change to Sockeye is the use of the new LayerNormalization operator which saves GPU memory. It uses the same set of parameters so I did not bump the major version.
Pull Request Checklist

[x] Changes are complete (if posting work-in-progress code, prefix your pull request title with '[WIP]'
until you can check this box.
[x] Unit tests pass (pytest)
[x] System tests pass (pytest test/system)
[x] Passed code style checking (./style-check.sh)
[x] You have considered writing a test
[x] Updated major/minor version in sockeye/__init__.py. Major version bump if this is a backwards incompatible change.
[x] Updated CHANGELOG.md

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@tdomhan @mjdenkowski @davvil @mjpost mxnet-1.2 is available and this can now be reviewed.

I don't know if we should bump up the major version, though. Users must update the mxnet version. It's "model backwards compatible" but not "system backwards compatible".

Yeah, but if people can update their Sockeye code, they can also update mxnet (if sockeye is installed via pip, this is automatically happening).
The last time we updated mxnet (1.1) we also just did a minor version change.

Let's keep the major version, then.


setScreenBrightness causes I/O inside event loop

Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for fullykiosk doing I/O at custom_components/fullykiosk/light.py, line 71: self.controller.setScreenBrightness(brightness)
This is probably caused because the setScreenBrightness function is not awaited somehow. Maybe needs to be called similar to this?
https://developers.home-assistant.io/docs/asyncio_working_with_async/#calling-sync-functions-from-async

Should be fixed by #20


Links added | Some IIIT's commented | Readme Updated | Contact Detail…

…s added | Open Source Projects bring on top

#1


Request for detailed tutorial

Hi, Barry Menglong Yao,
First and foremost, I'd like to express my admiration for the incredible work you've done on Mocheg. It's evident that a lot of effort and dedication went into it, and I truly appreciate your contribution to the community.
I am genuinely interested in diving deeper into your project and leveraging it for my own research/work. However, I've encountered some challenges in setting everything up. Would it be possible for you to provide a more detailed tutorial? Specifically, clarity on the data set storage path, the pre-trained model storage path, and any other configuration details would be extremely beneficial.
Understanding that you are busy, I hope this isn't too much of an inconvenience. Your guidance would significantly assist many of us in the community who are keen to make the most out of your wonderful project.
Thank you so much for considering my request, and once again, hats off to your outstanding work!
Warm regards.

Thanks for your interest! It will be helpful to add a detailed tutorial. I will work on it.
In order to solve the challenges in your case, do you mind listing these challenges?

Thank you for your time!
I would like to know how I should place the dataset in the folder? For example, should I create a folder called "data" and put all the files in the dataset in it?

Yes. A folder named "data" for the dataset and a folder named "checkpoint" for checkpoints.
In fact, you can also use other paths as long as you pass your corresponding paths as Python arguments. They are Python arguments defined in corresponding scripts like retrieve_train.py.
Please list other challenges so others can also benefit from your experience.

Thank you for your patience and help.
I'm at an academic conference right now and can't start the experiment right away, I'll be coming in next week to start the experiment and I'll list the challenges I'm having then.

I encountered an error when running python retrieve_train.py --train_config=BI_ENCODER. The error occurred at the loss_value = loss_model(features, labels) statement in /Mocheg-main/retrieval/training/model.py. The error message is RuntimeError: The size of tensor a (89) must match the size of tensor b (77) at non-singleton dimension 1, and the size of tensor a varies each time I run it. Do you know why this might be happening, and how I could resolve it? Thank you.

When I'm running python retrieve_train.py --train_config=BI_ENCODER, I encounter an error at the line loss_value = loss_model(features, labels) in /Mocheg-main/retrieval/training/model.py. The error message is: RuntimeError: The size of tensor a (89) must match the size of tensor b (77) at non-singleton dimension 1. Additionally, the size of tensor ‘a’ varies each time I run the code. Do you know why this might be happening and how I can resolve it?

Hello,
When I executed the command 'python verify.py --model_type=CLAIM_TEXT_IMAGE_attention_5_4 --batch_size=2048 --lr=0.001 --loss_weight_power=2', I encountered an error in the 'Mocheg-main/verification/train_verify.py' at the line 'output = model( claim_img_encod,device)':
RuntimeError: The size of tensor a (85) must match the size of tensor b (77) at non-singleton dimension 1.
Upon further inspection, I noticed that the issue might be due to the absence of a truncation length in the self.processor function within the /Mocheg-main/verification/util/data_util.py file:
self.processor(text=claim_and_text_evidence_list, images=img_list, return_tensors="pt", padding=True,truncation=True)
When I set the max_length parameter to 77, the code ran without any errors. I'd like to inquire if my solution is appropriate or if there might be an issue with the model I loaded?
Thank you for your assistance!

Hi,
While running the command python verify.py --model_type=CLAIM_TEXT_IMAGE_attention_5_4 --batch_size=2048 --lr=0.001 --loss_weight_power=2, I encountered an error in Mocheg-main/verification/train_verify.py at the line output = model(claim_img_encod, device):
RuntimeError: The size of tensor a (85) must match the size of tensor b (77) at non-singleton dimension 1.
I traced the issue back to the file /Mocheg-main/verification/util/data_util.py where the line self.processor(text=claim_and_text_evidence_list, images=img_list, return_tensors="pt", padding=True, truncation=True, max_length=77) did not specify a truncation length. After setting max_length to 77, the code ran without issues.
Is this the correct solution? Or is there an issue with the model I'm loading?
Thank you for your assistance!

Yes. The key is to truncate the text under 77 tokens.
It seems I truncated the text during another preprocess. But your solution is better. I have merged your modification into the repository. Thanks!

After I trained the code for the generation module, I removed the --do_train option and kept only --do_predict. and loaded the model and tokenizer under the /data/Projects/Mocheg/controllable/generation/output/bart/run_40/without/ path for inference. The generated result was completely different from the generated result just after training. For example,
Just after training with --do_train --do_predict setting:
species of grasshopper, the Dactylotum bicolor species has a colorful, bright-red coloration that is similar to the grasshoppers found in other types of bugs, such as the painted woodhopper (Scolopendra subspinipes) and the painted water bug (Anodorhynchus sanguineus). According to the Inaturalist, this species is a member of the family Vespidae, one of the few species that is endemic to North America. It is native to a few locations in North America (primarily in the eastern half of the United States), and is found in southern Mexico, Central America, and the Caribbean. The web site for the species notes that it is common in some parts of the world, particularly in central and eastern Europe. 'It is found on some of the central African countries such as South Africa, Uganda, and Zambia,' wrote the INaturalist. Furthermore, the photograph displayed above was not the only one of its kind spotted in Michigan in September 2021. Here's a look at a photograph of the genuine rainbow grasshoppe as published by the Reddit page Nature Is FuckingLit: Given that the species shown above is different, but the colors in both the photograph and the written description are similar, we rate this claim as a 'Mixture,' as well as the possibility that it could be a different species of Grasshopper species found in different locations, as of this writing, as 'Unproven.' We reached out to the Smithsonian, and will update this post if more information becomes available. As such, the rating of this claim is 'Miscaptioned,' with the status changed to 'False.'

Inference with only  --do_predict setting:
NEI  A photograph shared to Reddit in September 2021 showed a vibrantly hued grasshopper that was seen in Michigan.  Sources:  dosangst. '🔥 Really Cool Grasshopper Spotted in a Backyard in S.E. Michigan.' R/NatureIsFuckingLit, 12 Sept. 2021, [www.reddit.com/r/Nature_Is_Fucking_Lit/comments/pmy84s/really_cool_grasshopper_spotted_in_a_backyard_in/](https://github.com/VT-NLP/Mocheg/issues/www.reddit.com/r/Nature_Is_Fucking_Lit/comments/pmy84s/really_cool_grasshopper_spotted_in_a_backyard_in/). 'Is This a Real Rainbow Grasshoppers?' Snopes.Com, https://www.snopes.net/node/view/31526. Accessed 16 Sept. 2011. Species Dactylotum Bicolor. SCAN Collections Search Results. https://scan-bugs.org/portal/collections/list.php?portal_id=1&type=2&db=all&page=1. Accessed 15 Sept. 2016. 'Dactylotsum bicolor'. Bug Guide. https/bugguide.org?portals=1 &type=3&db =1&page_id =1 &page_type=1 and https://bugguide-org.org/?type=4&db_id=-1&site=1-1&search=1_1_2_1&index=2. Accessed 17 Sept. 2017. 'Rainbow Grasshoper (Dactyotum biculatus).' INaturalist.com. https//[www.inaturalism.com/?article=rainbow-grasshoppers&id=179324&article_url=http%3A%2F%2B%2C%2A%22inaturalist%2D%3C%3B%3F%3D%2E%3E%](https://github.com/VT-NLP/Mocheg/issues/www.inaturalism.com/?article=rainbow-grasshoppers&id=179324&article_url=http%3A%2F%2B%2C%2A%22inaturalist%2D%3C%3B%3F%3D%2E%3E%)

I also loaded all checkpoints in the without/ path, and all generated the same result. So I was confused about how I was supposed to load the trained model to get the perfect result.


Value for crossorigin when origins set in giscus.json

Thanks for the great tool!
I've not found any documentation on what value to set crossorigin to when using the origins key in giscus.json. I've only seen a documented value of anonymous, but assume it should be a different value when specifying in JSON?

They are unrelated.


Fix extraneous space before the only jagged vector in a lines segment

Fix #155

cc @gyosh for awareness


Add eslint

It's missing the CI/CD functionality for now, but I will do that afterwards.

It's missing the CI/CD functionality for now, but I will do that separately.

lgtm, can you run eslint --fix on the whole project, so the whole codebase is on the same page?

@probablyArth I have done so now, and there are no changes eslint is making. It's definitely working, though. If I place some double quotes or semicolons, it fixes them, but there are none existing in the project at the moment.


Use beneficiaryDistributionAmount in distributePayoutsEventElem

What does this PR do and why?
Includes the beneficiaryDistributionAmount in the DistributePayoutsEventElem component that was accidentally omitted before, and fixes a bug in parsing distributePayoutsEvent json.
Acceptance checklist

[x] I have evaluated the
Approval Guidelines
for this PR.
[x] I have tested this PR in
all supported browsers.

friendly ping @johnnyd-eth


[Bug Report] The first line of the distro logo not being displayed.

Describe the bug
The first line of the distro logo is not being displayed.
Expected behavior
The first line of the distro logo is expected to be displayed.
Screenshots
a screenshot showing the distro logo in albafetch in juxtaposition to neofetch
Desktop (please complete the following information):

OS: debian
Terminal gnome-terminal

Possibly relevant config lines:

I did not change any config files.

Additional context
I really like this program. Would love to see this bug fixed. Thank you!

good catch, thanks!


BUG:  unsuppotted useDefaultCAs: false

If  trying to set source.useDefaultCAs to false the admission webhook prevents creation of the bundle.
How to reproduce:
cat  <<EOF | kubectl apply -f -
apiVersion: trust.cert-manager.io/v1alpha1
kind: Bundle
metadata:
  name: my-org.com-ca
spec:
  sources:
  - useDefaultCAs: false

  #- secret:
  #    name: my-org.com-ca
  #    key: "tls.crt"

  target:
    configMap:
      key: "certs.pem"
    namespaceSelector:
      matchLabels: {}
EOF

Error output:
admission webhook "trust.cert-manager.io" denied the request: spec.sources.[0]: Forbidden: must define exactly one source type for each item but found 0 defined types
Workaround is trivial comment the useDefaultCAs entry, but still one would expect the false is supported value.

@pavel-jancik could you explain what useDefaultCAs: false would mean?
Currently, the default value is false, but each item in the sources array needs to contain exactly one source.
For that reason, specifying useDefaultCAs: false does not make sense.

I just wanted to explicitly mention it. I.e., make the default value visible in the bundle CR (for documentation purposes)
so that it is obvious for others that in the resulting config maps no other trusted CA will be included.
Note that, I have been cleaning the example above; the idea was not to create an empty bundle.
I have been using:
spec:
  sources:
  # Do not inject a long list generally trusted CA
  - useDefaultCAs: false

  # A Secret in the trust-manager namespace
  - secret:
      name: "our-org-ca"
      key: "ca.crt"

@pavel-jancik could you explain what useDefaultCAs: false would mean? Currently, the default value is false, but each item in the sources array needs to contain exactly one source. For that reason, the webhook thinks that useDefaultCAs: false does not make sense.

For me, not having it work feels like a bug.
If I have a helm chart, for example, and want someone to be able to pass on a value to pass to the cr, the helm chart needs a conditional instead of being able to pass a Boolean, which feels like a workaround.
I agree useDefaultCAs: {} would be a better representation, and then require that conditional, but then it would be for a good reason.


concurrent Table

Is your feature request related to a problem? Please describe.
To allow dynamic socket insertion, we must be able to modify internal/sys.(*Context).fsc.openedFiles, which is a descriptor.Table[int32, *FileEntry], after the instantiation of the WebAssembly module.
Since we there is absolutely NO guarantee the Table is not being accessed by multiple parties, this data structure should be guarded with thread-safety.
Describe the solution you'd like
Adding sync.RWMutex to guard all read/write access to underlying slices of descriptor.Table.
Describe alternatives you've considered
There seems to be no trivial alternative solution to workaround our specific requirement, given our current implementation REQUIRES a Table stays editable. The only case where this isn't an issue, is that when we can confirm there can be no concurrent access to the openedFiles, in other words, all accesses to openedFiles are virtually single-threaded.
Additional context
This is to support the big picture of being able to dynamically insert newly created network sockets into the openedFiles table (e.g., upon being requested by the WebAssembly instance).

tetratelabs/wazero#1857 discusses the possibility of adding it to the upstream.

https://github.com/gaukas/wazero/blob/5796897f37852bf2042cd63959ce4ff673c4366e/internal/sys/fs.go#L253-L261
Seems there might have been some discussion related, somewhere.

Okay, so seemingly upstream is not interested in this change. Guess we will keep this change to ourselves.

It is good to note, if we are still doing callback-to-host from WebAssembly, there will be no concurrent access to any Table, since WebAssembly will block on imported host function.
However ultimately we will shift to fully async.


Force polling on WSL

fix #187
To install watchfiles as per this PR:
Either:
(with rust installed)
pip install git+https://github.com/samuelcolvin/watchfiles.git@force-polling-wsl2

, Or if you don't have rust installed:

download the pypi_files artifact from the github actions run for this PR (once CI is passing)
extract
pip install pypi_files/<whichever wheel matches your system>

Thanks so much @danroozemond.
I completely agree that the polling delay should be signficantly larger, like 300ms.
30 seems like a weird choice, I wonder if it was a typo that no one picked up on??? :facepalm: I'll create another PR.

See #196


docs: import "Architecture" chapter from the wiki

source: https://github.com/gardener/documentation/wiki/Architecture
Signed-off-by: Christian Berendt<EMAIL_ADDRESS>

Thank you @berendt for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below.

https://github.com/gardener/documentation/wiki/Architecture can be deleted after the merge of this PR.

Yeah, I guess this makes sense, the wiki is quite hidden. Can you please also add the document to the index (https://github.com/gardener/gardener/blob/master/docs/README.md)?


Added streaming output support for local search & global search

Description
This PR introduces changes to enable streaming output in the LLM's generate method, as well as in the search methods of both LocalSearch and GlobalSearch classes. Intended to facilitate web application development or any other scenarios where streaming and real-time display of generated content is required.
Related Issues
none
Proposed Changes

Updated the generate method's return type to Generator[str, None, str] of BaseLLM and ChatOpenAI and implement it.
Updated the search method's return type to Generator[str, None, SearchResult] of LocalSearch, GlobalSearch and BaseSearch, and implement it.
Added a '--streaming' flag to the cli, allows users to specify whether they want to enable streaming output for local and global search.

Checklist

[x] I have tested these changes locally.
[x] I have reviewed the code changes.
[x] I have updated the documentation (if necessary).
[x] I have added appropriate unit tests (if applicable).

Additional Notes
A caveat with these changes is that when a method contains a yield statement, the Python interpreter automatically defines it as a generator function, meaning that it always returns a generator. If streaming is not needed, it becomes less straightforward to directly retrieve the final result, as you must use a try-except block to catch the StopIteration exception and extract the value from it. This can lead to less elegant code.
If necessary, the streaming functionality could be refactored into separate methods to maintain clarity and separation of concerns.

@6ixGODD please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree
Get Outlook for iOShttps://aka.ms/o0ukef

From: microsoft-github-policy-service[bot] @.>
Sent: Friday, August 9, 2024 2:21:44 PM
To: microsoft/graphrag @.>
Cc: 6GOD @.>; Mention @.>
Subject: Re: [microsoft/graphrag] Added streaming output support for local search & global search (PR #882)
@6ixGODDhttps://github.com/6ixGODD please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.orghttp://www.opensource.org).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase “Submission
containing materials of a third party:” followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
guidelines concerning Submissions.
Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
Licenses.

Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/graphrag/pull/882#issuecomment-2277823317, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANF563LCDWX5RDPQ7UX5F2TZQSX5RAVCNFSM6AAAAABMILU37OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZXHAZDGMZRG4.
You are receiving this because you were mentioned.Message ID: @.***>

@6ixGODD This is great work. You caught us in the middle of defining an API layer between the CLI and library code. We just merged a PR that more explicitly defines the query API.
I agree with the separation of concerns issue. Can you update/refactor to use this existing query API and if there needs to be separate functions to maintain clarity, we're open to adding new streaming functions to the API.

@6ixGODD This is great work. You caught us in the middle of defining an API layer between the CLI and library code. We just merged a PR that more explicitly defines the query API.
I agree with the separation of concerns issue. Can you update/refactor to use this existing query API and if there needs to be separate functions to maintain clarity, we're open to adding new streaming functions to the API.

I've made the corresponding changes:
I kept the --streaming command-line argument, which controls whether the output is streamed.
I modified the two APIs in api.py by adding conditional logic to decide whether to use streaming output, and included a ⬤ as a progress indicator (free to remove it if it looks out of place).
I added stream_generate and astream_generate methods to the BaseLLM abstract class for synchronous and asynchronous streaming response generation, respectively, and implemented them in the ChatOpenAI class (I also added a few private methods, following the original code style).
I added an astream_search method to the BaseSearch abstract class for streaming search, and implemented it in both GlobalSearch and LocalSearch classes.
I made the necessary updates in the CLI to support the --streaming option.
With these changes, apart from adding the streaming parameter and a few additional methods, I have made minimal modifications to the original code.

there's on_llm_new_token callback, why don't you use this method?

there's on_llm_new_token callback, why don't you use this method?

@KylinMountain I missed the on_llm_new_token callback😂 I check the code and youre right. But from an application development perspective, whether using websocket, sse, or others, typically needs to be a way to YIELD chunks of data.. I figured why not just handle it directly in the class instead of decoupling it. right?

@6ixGODD is right. The callback approach does work but it's quite messy for an external system to use and could be prone to errors that you might not think about (when considering dropped messages/tokens) depending on the use case you're targeting.
For example, in the solution accelerator, we had to implement some custom data structures and logic in order to create a proper streaming web API that would work like most programmatic clients expect (i.e. using the requests library to iterate over a response chunks).
Adding a generator function to the API is much cleaner for everyone to use (my opinion). I copied this fork and made a new PR (under review) that cleaned up several other things that we needed to take care of in order to expose a proper streaming API as a generator function.

@6ixGODD is right. The callback approach does work but it's quite messy for an external system to use and could be prone to errors that you might not think about (when considering dropped messages/tokens) depending on the use case you're targeting.
For example, in the solution accelerator, we had to implement some custom data structures and logic in order to create a proper streaming web API that would work like most programmatic clients expect (i.e. using the requests library to iterate over response chunks).
Adding a generator function to the API is much cleaner for everyone to use (my opinion). I copied this fork and made a new PR (under review) that cleaned up several other things that were needed in order to expose a proper streaming API as a generator function.

@jgbradley1 Completely agree😄I saw your new PR, and I am honored to have the possibility of contributing to this repository.


Add constructors for feedback logs

The feedback system was originally designed for reporting feedback as GOPATH was scanned, which didn’t work well for logging from the importers. This moves more of the logic around what should be logged back onto the caller and simplifies the ConstraintFeedback.LogFeedback function to print what it is given.
This is broken off from #715.

Rebased and squashed
Updated the new godep importer to use the feedback constructor
Tweaked existing feedback tests to exercise the constructors

LGTM! 🎉


[Feat]: Adding better images!

What feature?
We can add better informative images.
Show us the magic with screenshots
No response
Agreement to Code of Conduct

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

Please show us the samples of images

These are a few samples:

Ok, @Shr-reny thank you for your suggestion and interest in our project, Our theme follows images with 3d elements so, for now, we have not planned to change the current images from the home page.


Inquiry

I am new to GitHub and Ruby is new for me, I am confused with API Client Setup.
I got all detail for;
api_client = Myob::Api::Client.new({
:consumer => {
:key    => YOUR_CONSUMER_KEY,
:secret => YOUR_CONSUMER_SECRET,
},
:access_token  => YOUR_OAUTH_ACCESS_TOKEN,
:refresh_token => YOUR_OAUTH_REFRESH_TOKEN,
:company_file  => {
:name     => COMPANY_FILE_NAME,
:username => COMPANY_FILE_USERNAME,
:password => COMPANY_FILE_PASSWORD,
},
})
However, I do not sure where to run this and how it works. This will refer to "myob-api/lib/myob/api/client.rb", right? I have to run this in console right?

I used Postman to get all the details, put the API Client Setup in your new controller and start with def api_client and end(make a function). Lastly, render for checking. Do not forget create routes.


Show more useful unicode representation for IdpProfile objects.

@akatsoulas r?

Coverage decreased (-0.008%) to 90.036% when pulling a8b843b01bba2857f36a988c5443f47ed73da6de on johngian:fix-idp-profile-unicode into 177b01a8910a2425ddfe08f719d160a8af45fa47 on mozilla:master.


Adding toString, equals operator and hashcode

A desired feature is to have the PostalAddersses automtically be able to handle toString as this will help with dropdowns and other situations where printing the address on the screen would be beneficial.

@kmccmk9 awesome and thanks, I'll review your PR this week.


https dosen't work with daemons

Hey, when i configured the web to https, my browser wont connect to the daemon:

My daemon config:

and this daemon config doesen't work:

Chinese docs
https://github.com/bddjr/nginx-proxy-docs-for-mcsm/blob/master/配置HTTPS反向代理.md

Chinese docs https://github.com/bddjr/nginx-proxy-docs-for-mcsm/blob/master/配置HTTPS反向代理.md

I followed these docs to the best of my ability and even used the generator, but it simply won't work.
MCSM web and deamon are never accesible with the generated/suggested configs.
With this configuration it worked and I can access them at mcsm.kwahson.com and deamon.kwahson.com but mcsm web cannot find anything at deamon. I tried wss//deamon.kwahson.com with ports 24444 443 80 but nothing works.  Thanks a lot for the help


Look at using promises for dialogs

https://dev.to/padcom/vue-js-and-dialogs-1b28
Seems like a much cleaner model than the current v-model/passing data.

I like this... Feels much more intuitive


Message during build is only in Chinese

The message during hexo g looks like: file:// 匹配不到下列文章：hello-world.md. This should be localized by language.
In this case, Google Translate tells me this means "Can't match the following articles", which would have been very helpful for troubleshooting #2 :)

I still get this Chinese-only message if I incorrectly reference file://something. See #4


Can not run -copy separately

Now having quote and pruning options (again, thanks a lot for the fast and kind response), I have created appropriate configs with rich options and tried to use them.
My preference is not to use duplicacy-util -a, but separately use backup, copy, check and prune operations - I would like to call prune before copy to decrease data transfer overhead and also to call these operations less frequently than backups.
I have found that -copy command actually does not work for me:
PS D:\Tools> D:\Tools\duplicacy\duplicacy-util.exe -sd D:\Tools\duplicacy\duplicacy-util\ -f de_tools.yaml -copy
21:04:20 Using global config: D:\Tools\duplicacy\duplicacy-util\duplicacy-util.yaml
21:04:20 Using config file:   D:\Tools\duplicacy\duplicacy-util\de_tools.yaml
Error: No operations to perform (specify -b, -p, -c, or -a)

If I call duplicacy-util -a for the same config, it does backup, copy, check and prune normally.

duplicacy-util -version please? I think this is a minor bug but did want to verify that.

I see the problem, resolved in commit 4c1885f


Update raw method

Description

Adds a new client method RawWithResponse to give us access to the full Cloudflare response object rather than just the Result field.
Refactors the existing Raw method to use RawWithResponse as the underlying implementations are identical.

Types of changes
What sort of change does your code introduce/modify?

[ ] 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 change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] This change is using publicly documented (api.cloudflare.com or developers.cloudflare.com) and stable APIs.

Wrong repo


Update otel-tools_2.13 to 0.1.7

Updates io.superflat:otel-tools_2.13 from 0.1.6 to 0.1.7.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (0.1.6).
You might want to review and update them manually.
project/plugins.sbt

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.superflat", artifactId = "otel-tools_2.13" } ]

labels: library-update, semver-patch, old-version-remains

No commit added. No need of this PR


saving to disk as SVG

Is your feature request related to a problem? Please describe.
If saving to disk, the default output format is PNG which is inefficient and low-resolution.
I couldn't find a way to save as SVG instead, though I'm sure graphviz supports this.
Describe the solution you'd like
add option "format=[svg|png]" that allows choosing the file format.
Alternatively, derive it from the filename, i.e. filename="model.svg" sets format=svg automatically.
Describe alternatives you've considered
This works:
model_graph = draw_graph(model,
                        input_data=dummy_input,
                        save_graph=True,
                        directory="figures/")
model_graph.visual_graph.render(format='svg')

but this first saves a PNG and then the SVG as well, it would be cleaner if we had an option in the draw_graph() function itself

Sorry for the late reply,
What you could is to turn off save graph option and then save it in svg format manually.
Since this could be done with just one line of code, I am not really willing to put it.
But if you or someone else provide nice PR, I would accept it.

You can save the graph as SVG (or any other format supported by graphviz) like this:
graph = draw_graph(model, ...).visual_graph
graph_svg = graph.pipe(format='svg').decode('utf-8') # convert to binary data
with open(save_path + '.' + format, 'wb') as f:
    f.write(graph_svg)

How can I save as png?

graph_svg = graph.pipe(format='svg').decode('utf-8') # convert to binary data
with open(save_path + '.' + format, 'wb') as f:
    f.write(graph_svg)

s, u can

s, u can @naik-amey. just set format arg to "png"


Typo in documentation

There is a missing T in the first sentence. "considered par of"

Addressed in https://github.com/prometheus/prometheus/pull/11755


Deno vscode debug config

Hi!
Deno seems to have been introduced very recently and so far, I'm very happy with this!
I might need assistance to create a working vscode debugging config.
This is what I have so far:
{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "pwa-node",
      "request": "launch",
      "name": "server: deno",
      "runtimeExecutable": "deno",
      "outputCapture": "std",
      "runtimeArgs": [
        "run",
        "--inspect",
        "--allow-all",
        "npm:nuxt/nuxi",
        "dev"
      ],
      "attachSimplePort": 9229
    }
  ]
}

While it is running dev just fine, it doesnt seem to be able to bind breakpoints at all, neither client nor serverside.
Any idea? I've also tried putting --inspect after dev which results in the same problem.
Thank you!

Hello :wave:
inspect should only work for server side If i remember well. Can you try with --inspect-brk then using chrome devtools to make sure deno has opened the port for debugging ?

Thanks for your reply.
I did that, it does seem to attach just fine, altough breakpoints still aren't bound unfortunately.

In chrome://inspect it also shows up just as it should

I'm using Vivaldi but I've also tried chrome, same result.
Any idea what else to try?


Add completions

Problem
Millet doesn't offer completions, e.g. when typing val x = List. it'd be nice to mention all the things from the List structure, or even just when typing val x = S we could show String, etc as suggestions.
Solution
Implement completions in the LSP spec.

Already somewhat implemented: https://github.com/azdavis/millet/blob/4e0bed39cdb0e858cbbf84248537bdd3a01dabcc/crates/analysis/src/lib.rs/#L273-L278

Done in v0.11.0


Calendar won't see the previous year's notes

Describe the bug
After the start of the new year, the calendar has stopped recognizing the previous year's notes. The naming scheme is the same, because whenever I try to create a file that does exist, it tells me it is unable to create said file.
My naming scheme is kind of unorthodox, it is "WW-E...gg" if that makes any difference.
I am using this in conjunction with the Periodic Notes plugin.
Steps to reproduce

Go to calendar
See that the note associations have disappeared

Expected behavior
Calender shows the previous year's notes as well.
Environment
OS
Linux Mint
Obsidian Version
v1.5.3
plugin versions
Calendar: 1.5.10
Periodic Notes: 0.0.17
Thank you!

I'm curious, can you give a real example of a note's name based on the naming scheme?

Thank you for your response.
Today would be 2-1..24
(second week of the year)-(first day of the week)..(last 2 digits of the year)
I was wondering if it's the ambiguity of the year since 23 can stand for 2023 or 3023 technically, but that doesn't seem to be the problem.

That's what I was wondering when I first read your question. So, you never see the month in that date format, correct? I'm not sure the Calendar plugin can even understand what date you're trying to reference since (to its way of thinking) you're missing a key element: the month.
I don't see anything in the configuration of the current beta that allows you to tell it what your date format is except with a Locale, and those are all standard language-location choices. I believe you'd need to customize the underlying program directly to handle your unique case.


[QUESTION] Batch-normalization in pooling layer

❓ Question
Hi,
Is the batch-normalization component from the pooling layer from here:
https://github.com/Unbabel/COMET/blob/a96a688e450f7b61f9d884240ff0749223d79113/comet/modules/layerwise_attention.py#L139
mentioned in any of the COMET papers? I don't seem to see it in the main COMET citation.
Can you elaborate a bit why this was useful? It seems unusual to see batch-normalization in NLP applications.
Also, it seems this could be fixed to normalize over a single sentence during inference (use dimensions to only average over time dim) to achieve deterministic behavior consistent with batch-size 1. Would there be any downsides to that?
Thanks,
Marcin

Hi @emjotde!
This is a good observation. In the paper we only say that we use the Layerwise scalar mix to combine multiple layers. The implementation we used actually comes from this model.
The idea is that the batch normalisation helps generalisation but in experiments for this year shared task we had more time to play with different hyper parameters and we ended up deactivating it. New models from this year do not use it anymore.
Also, your suggestion is good. I'll test it out

Thanks for the answer! Feel free to close.


Only fund when faucet balance drops below 10 000 000 sats

This speeds up development a little bit. The balance is retrieved by curling the channel balance.
I left this out of  the fund-regtest recipe since it seems to be a manually invoked recipe and not an automated prerequiste, hence it is not really needed.

Not ideal this change: sometimes we will need to fund an already funded node again.

Maybe a new force-fund command for that? Or, a new autofund command and use that for the prerequisite in all etc.
For context, the problem I am trying to solve is the fund process being run every time I run just all to start the app for debugging

Not ideal this change: sometimes we will need to fund an already funded node again.

Maybe a new force-fund command for that? Or, a new autofund command and use that for the prerequisite in all etc.
For context, the problem I am trying to solve is the fund process being run every time I run just all to start the app for debugging

I never use this command 🙈 I like to keep an eye on what things happen and call each step separately.
I'm fine with a different function or an extra arg I can pass in to force funding again.

Fair enough! Do you have any preference as to a new command or arg?

Fair enough! Do you have any preference as to a new command or arg?

Eitherway is fine with me :)

Added arguments -f & --force


segment io <> outbound for page calls

@stevenmiller888 @f2prateek @amillet89

Current coverage is 93.33% (diff: 100%)

Merging #6 into master will increase coverage by 10.98%

@@             master         #6   diff @@
==========================================
  Files             1          1
  Lines            34         45    +11
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits             28         42    +14
+ Misses            6          3     -3
  Partials          0          0

Powered by Codecov. Last update 8af64dc...bd472ab

@f2prateek done!

LGTM!