Not an issue, just a thank you!

I spent a day toying with the API you expose to automate some behaviour on my system on mixer state changes. It was really easy to get this going thanks to the wiki page on the API. It's silly, but it's incredibly satisfying.
So I just wanted to say thank you, but I couldn't find anywhere to do it aside from the issue tracker.

Hi There!
It's always great to see people playing around with the API, looks like you've got a pretty creative use for it!
It was definitely interesting to see the IPC mechanism implemented, I know a lot of people simply have the Web Socket address configurable, but this comment caught my attention.. Definitely not desired behaviour!
So I've added a fix for that, the IPC will now correctly throw back the cause of the parsing error, and I've also updated the wiki to remove references to the long deprecated GetHttpState command. This should all go out with the next release.
Thanks!

updated the wiki to remove references to the long deprecated GetHttpState command (I have a feeling these two things are related).

They are, it's how I discovered that issue :smile:

It was definitely interesting to see the IPC mechanism implemented, I know a lot of people simply have the Web Socket address configurable

Ah yeah, I can see that. Honestly I probably would have turned it into a configuration option if the wiki hadn't pointed at getting that through the socket. It's nice that you can do it that way though, since it allows the system to fully figure itself out. I definitely appreciate the feature.
One thing I was wondering about that, is there a way to configure the socket location? I don't mind /tmp, but since it's part of my user session I typically stash those in XDG_RUNTIME_DIR instead.

One thing I was wondering about that, is there a way to configure the socket location? I don't mind /tmp, but since it's part of my user session I typically stash those in XDG_RUNTIME_DIR instead.

It's not, it's hard coded in many places and was a very conscious decision.
Firstly, was the desire to avoid applications that use it needing any amount of 'boiler plate', for example the Utility UI Wrapper, which is used by many people on various platforms would suddenly need a new command line argument, as it needs to locate the Utility's IPC socket to be able to start, the same would apply to your app, as well as various other apps which exist, hell, even the goxlr-client binary would need it, so being able to move it creates a hard requirement on some level of boiler plate in all languages to be able to support, and also a requirement for the user to remember to use that parameter, and remember where the socket is.
Secondly, If we looked at automatic detection, we kinda run into a similar problem, anything wanting to use the Utility would have to dig around the system to try and find the runtime location, XDG doesn't exist in some window managers, nor does it exist on MacOS, so all apps would have to go through the same steps as the daemon does when it's creating the socket in order to locate where the socket may be (again, another chunk of boiler plate spanning many languages and implementations), you can also run the risk of something running in a way that XDG may not be present, despite the socket being in an XDG location, so it can never be found..
And finally, while yes, the daemon runs as part of your user session, it is not per-user. If two goxlr-daemon processes spawned up, they would both conflict and fight with each other, rendering the GoXLR mostly useless. Messages are sent to the device in a sequential fashion via libUSB, having two processes sending together would result in sequence breaking and constant attempts to reset and reload to fix. So during startup, regardless of the user starting it, it will probe /tmp/goxlr.socket to see if there's a utility already running on the other side, and will abort its launch if it finds one. Having the socket in a user specific location would make it impossible for this test to be performed across accounts.
/tmp ends up being a reliable location for the socket that allows applications (and the utility itself) to automatically figure things out, without the need for large amounts of extra code or consideration.. So it'll likely be stuck there :)

That makes a lot of sense. Thanks for the explanation.

No problem I'm gonna close this one now :)


Node Module

Can Sovereign be run as a node module ?

I haven't looked this into yet. How do you imagine using it this way?


Problems changing status with script to HA

The status in HA is not changing when chaning the status of my MSTeams session.
Although there are parts of the script which is working the actual automatically changing of the status is not working.
When i close MSTeams from the statusbar the status in HA is updated to Offline.
When i launch the script with the SetStatus argument it is working
.\Get-TeamsStatus.ps1 -SetStatus "Beschikbaar"
I tried to figure out where it goes work but am not able to.
I saw when running parts of the script with Powershell ISE that the variable $TeamsProcess get's a value from the "Get-Process - Name Teams" part. But when i check ($null -ne $TeamsProcess) then it looks like it is empty.
I did change the vallues in the settings.ps1 file to dutch terminology like i find in the log.txt from Teams.
Are you able to help me out with this?
Thank you!

Already fixed,
After changing $env:APPDATA"\Microsoft\Teams\logs.txt to "C:\Users$UserName\AppData\Roaming\Microsoft\Teams\logs.txt" it works.


Artifacts in LazyVim's lualine

As seen in the screenshot, the breadcrumbs section of lualine has black boxes between symbols. Does not occur in the default LazyVim theme or gruvbox material for example.

I'm with this same problem, tried to change the lualine theme prop but no changes, did you find any solution ?

@sergiotales1 unfortunately, no. Seems really like a theme related issue, because it's gone if I change it to another theme, such as gruvbox material

I have found one way to solve this, apparently it's a Lazy vim lualine setup thing, the trouble.statusline usually shows the function the cursor are in and show some icons, but something is bugged with this so the icons are not shown at all, if you comment these lines of code into your lualine lazyvim config, the artifacts will be gone
Create lualine.lua into your lua>plugins folder and install the plugin like lazy vim but with these lines commented
-- do not add trouble symbols if aerial is enabled
-- And allow it to be overriden for some buffer types (see autocmds)
-- if vim.g.trouble_lualine and LazyVim.has("trouble.nvim") then
--   local trouble = require("trouble")
--   local symbols = trouble.statusline({
--     mode = "symbols",
--     groups = {},
--     title = false,
--     filter = { range = true },
--     format = "{kind_icon}{symbol.name:Normal}",
--     hl_group = "lualine_c_normal",
--   })
--   table.insert(opts.sections.lualine_c, {
--     symbols and symbols.get,
--     cond = function()
--       return vim.b.trouble_lualine ~= false and symbols.has()
--     end,
--   })
-- end

You can check my plugins config here

You can set vim.g.trouble_lualine = false in lua/config/options.lua to do the same trick that @sergiotales1, as mentioned here.


sgpmc

Translate GPflow/GPflow/sgpmc.py to gpflowr/R/sgpmc.R
When closed, remember to tick the box in the roadmap issue

nullified by #27


Polyfill is always overring default Promise object

Hi,
I just tried to use the polyfill in Chrome (latest) and it is replacing the default implementation instead of properly detecting it.
The problem seems to be in this code fragment:
if (P && Object.prototype.toString.call(P.resolve()) === '[object Promise]' && !P.cast) {
return;
}
Object.prototype.toString.call(P.resolve()) is returning '[object Object]'. Can anyone else reproduce this behavior? The fix should be simple, buit I'd like to know why this approach is being used to detect the default Promise.

Object.prototype.toString.call(P.resolve()) is returning '[object Object]'. Can anyone else reproduce this behavior? The fix should be simple, buit I'd like to know why this approach is being used to detect the default Promise.

this version of chrome still has a bugy promise implementation, so we choose our implementation which does not suffer those same issues.

dupe of : https://github.com/jakearchibald/es6-promise/issues/111 and several others.


Quiten Standardizer

Addresses #407

Codecov Report

Merging #409 (a111cb0) into dev (c9e8c4a) will decrease coverage by 2.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev     #409      +/-   ##
==========================================
- Coverage   75.04%   72.93%   -2.12%
==========================================
  Files          12       12
  Lines        1006      824     -182
==========================================
- Hits          755      601     -154
+ Misses        251      223      -28

Impacted Files
Coverage Δ

src/builtins/Transformers.jl
93.78% <100.00%> (-2.65%)
:arrow_down:

src/registry/src/info_dict.jl
75.00% <0.00%> (-25.00%)
:arrow_down:

src/model_search.jl
69.01% <0.00%> (-3.28%)
:arrow_down:

src/builtins/Constant.jl
60.71% <0.00%> (-2.15%)
:arrow_down:

src/utilities.jl
0.00% <0.00%> (ø)

src/GaussianProcesses.jl
0.00% <0.00%> (ø)

src/registry/src/Registry.jl
0.00% <0.00%> (ø)

src/registry/src/check_registry.jl
0.00% <0.00%> (ø)

src/metadata.jl
81.81% <0.00%> (+0.44%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


Non-paid Option

It would be good to have a non-paid option where admins can just manually add users. i.e. be disable the pay-to-add URL.

You can add users in the lnbits control panel

You can add users in the lnbits control panel

Understood, generally - this is specific to the nostrnip5 ext though.

Yes, the extension management screen allows you to add users to domains that you set

Yep, I see I can do it manually. There is still no way to not add a fee when creating the domain. Surely it should be optional.


how can i run the python scraping?

Issue Template
Please use this template!
Initial Check

If the issue is a request please specify that it is a request in the title (Example: [REQUEST] more features). If this is a question regarding 'twint' please specify that it's a question in the title (Example: [QUESTION] What is x?). Please only submit issues related to 'twint'. Thanks.

Make sure you've checked the following:

[] Python version is 3.6;
[] Updated Twint with pip3 install --user --upgrade -e git+https://github.com/twintproject/twint.git@origin/master#egg=twint;
[] I have searched the issues and there are no duplicates of this issue/question/request.

Command Ran

Please provide the exact command ran including the username/search/code so I may reproduce the issue.

Description of Issue

Please use as much detail as possible.

Environment Details

Using Windows, Linux? What OS version? Running this in Anaconda? Jupyter Notebook? Terminal?

my name is Daniel tulips liu ,a chinese man.
I have installed windows subsystem ubunt 18.04 . and my computer has already  install pytho3-pip,
when use git to clonte the code to my computer ,and run  pip3 install -r requesments.txt .
then ,tpye the code : twint --help ,every thing is right .
but ,when i use scraping ,my computer get the wrong result.
like this
tulipsliu@DanielComputer:/mnt/c/Users/tulipsliu$ twint -u tulipsliu --search "matlab"
CRITICAL:root:twint.get:User:Cannot connect to host twitter.com:443 ssl:True [Connect call failed ('2001::4a75:b6b7', 443, 0, 0)]
Traceback (most recent call last):
File "/home/tulipsliu/.local/bin/twint", line 11, in
load_entry_point('twint==2.1.21', 'console_scripts', 'twint')()
File "/home/tulipsliu/.local/lib/python3.6/site-packages/twint/cli.py", line 311, in run_as_command
main()
File "/home/tulipsliu/.local/lib/python3.6/site-packages/twint/cli.py", line 303, in main
run.Search(c)
File "/home/tulipsliu/.local/lib/python3.6/site-packages/twint/run.py", line 386, in Search
run(config, callback)
File "/home/tulipsliu/.local/lib/python3.6/site-packages/twint/run.py", line 285, in run
get_event_loop().run_until_complete(Twint(config).main(callback))
File "/usr/lib/python3.6/asyncio/base_events.py", line 484, in run_until_complete
return future.result()
File "/home/tulipsliu/.local/lib/python3.6/site-packages/twint/run.py", line 211, in main
await task
File "/home/tulipsliu/.local/lib/python3.6/site-packages/twint/run.py", line 228, in run
raise ValueError("Cannot find twitter account with name = " + self.config.Username)
ValueError: Cannot find twitter account with name = tulipsliu

dear all ,
thanks very much for your reply.
yours : Daniel tulips liu


Slightly better error for failed tslint.json parses

Fixes https://github.com/palantir/tslint/issues/1681
configuration's findConfiguration now returns a result wrapper with the attempted path as well as error? and results?. tslint-cli will log the failure nicely.

@nchen63 added

@JoshuaKGoldberg thanks!


Port Tests from Deprecated Arithmetic Kernels

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

https://github.com/apache/arrow-rs/pull/4465 deprecated the old arithmetic kernels, but continued to use them to provide test coverage of the new APIs.
Describe the solution you'd like

We should port the old tests / add new tests to allow the eventual removal of the now deprecated arithmetic kernels
Describe alternatives you've considered

Additional context

label_issue.py automatically added labels {'arrow'} from #4465


Implement Kadane's Algorithm

Kadane’s Algorithm for Maximum Sub-Array Sum.

Pls make sure u do the necessary changes as issues @G1Joshi . Only after that we will be merging it.
Cheers

@G1Joshi can u work on your microbyte a bit more. We expect you to submit something similar to this and this.  Pls work on it so that we can get your name up on the leaderboard ASAP :)

I am working on this issue and soon I'll commit changes to this pull request.

Cool. We're waiting for your contributions.

@all-contributors kindly add @G1Joshi  for:

[x] code
[x] content
[x] ideas
[x] doc


Added Documentation and Examples section to README.MD - Fixes #98

Pull Request (PR) description
Added Documentation and Examples section to README.MD. Wording mostly copied from SharePointDsc.
This Pull Request (PR) fixes the following issues:
Fixes #98
Task list:

[x] Change details added to Unreleased section of CHANGELOG.md?
[ ] Added/updated documentation, comment-based help and descriptions in .schema.mof files where appropriate?
[ ] Examples appropriately updated?
[ ] New/changed code adheres to Style Guidelines?
[ ] Unit and (optional) Integration tests created/updated where possible?

This change is

@Johlju - would you mind reviewing this one if you get a moment?

Codecov Report

Merging #99 into dev will not change coverage.
The diff coverage is n/a.

@@        Coverage Diff        @@
##           dev   #99   +/-   ##
=================================
  Coverage   94%   94%
=================================
  Files        5     5
  Lines      513   513
  Branches     2     2
=================================
  Hits       486   486
  Misses      25    25
  Partials     2     2

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

ReadMe.md, line 29 at r1 (raw file):

en-US

Can't find the folder. :)

Comments from Reviewable

Review status: 1 of 2 files reviewed at latest revision, 1 unresolved discussion.

ReadMe.md, line 29 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

en-US

Can't find the folder. :)

That is correct 😁 This folder gets created by the Autodocumenation code - so only exists in modules installed from the PS Gallery. I've changed the wording to better reflect this.

Comments from Reviewable

Please see comment in your PR in xStorage.

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

ReadMe.md, line 1 at r1 (raw file):

# xCertificate

Extremely minor. the file is 'ReadMe.md', should be 'README.md'? Non-blocking.

Comments from Reviewable

Review status: 1 of 2 files reviewed at latest revision, 1 unresolved discussion.

README.md, line 1 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
Extremely minor. the file is 'ReadMe.md', should be 'README.md'? Non-blocking.

Fixed! :grin:

Comments from Reviewable

I've removed this whole paragraph until I can implement a process to ensure this info is all being copied into the Resource Module during release.

Review status: 1 of 2 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 2 of 2 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Kinetic scrolling in Vue demo broken on iOS

The physics based scrolling in safari on iOS does not work with the Vue based demo at
https://demos.creative-tim.com/vue-material-dashboard/#/dashboard

Hi, @torarnv! Thank you for using our product. We will take a look at this issue and we will come back with an update.
Regards,
Dragos


WIP: Support for multiple hostnames in hostname annotation

This is a PR for https://github.com/kubernetes-incubator/external-dns/issues/197. Is there something missing? :)

Thanks for the PR again :smile: (looks good to me so far, not sure if something is missing?)

LGTM
But would like to note that if at some point we will be supporting custom TTL/Record Type per record configuration, we will have to change the specs format, as current , separated list will not allow u to do so. Thanks for the PR

Yes, totally makes sense. Is there a spec for this change? Maybe I'll implement it.

@totallyunknown there is currently no clear defined specs, but some related issues:
https://github.com/kubernetes-incubator/external-dns/issues/24
https://github.com/kubernetes-incubator/external-dns/issues/117
But it would be great if u can create a proposal in #24

Can you please also update the docs?
https://github.com/kubernetes-incubator/external-dns/blob/master/docs/initial-design.md#annotations

This doesn't seem to handle the compatibility case for route53 annotations. e.g. I have a service with
labels:   dns: route53 annotations:     domainName: "firstdomain,seconddomain"
external-dns-0.4.1 with --compatibility=molecule finds this and registers it, but only one hostname which has the exact domainName value including comma.

@kellycampbell You're right. We missed this case. I created a PR that should fix it: https://github.com/kubernetes-incubator/external-dns/pull/301 Would you mind taking a look?


Inviting others to manage responses yields "Template not found" error

Description
It's unclear what's gone wrong to get this error message. When adding a person to help manage the form responses without including a message, which should be optional, cannot proceed and an error appears.
Steps to reproduce

Go to Staging
Create a draft form
Select "Download" as the response delivery method
Go to Responses page
Select "Manage access"
Add an email address
Click "Invite"
Get error blocking the flow

Details

Browser: Chrome
Operating system: Mac
Environment: Staging
Language: EN/FR
Viewport: desktop

Expected behaviour
Continuing without an error?
and/or a more descriptive and useful error message?
Screenshots or videos

Does not persist

Encountered this again (December 2, 2024)
This seems related to #3628 where a form is not yet assigned a name/formID


HNSW Support

What kind of change does this PR introduce?
Adds support for HNSW indexes

resolves #39

https://github.com/supabase/vecs/pull/42/files#diff-944e8edf178d147d8fdc83f30b35477e6f755b70f8575252f0b28a0706673114R392-R403
def query(
        self,
        data: Union[Iterable[Numeric], Any],
        limit: int = 10,
        filters: Optional[Dict] = None,
        measure: Union[IndexMeasure, str] = IndexMeasure.cosine_distance,
        include_value: bool = False,
        include_metadata: bool = False,
        *,
        probes: Optional[int] = None,
        ef_search: Optional[int] = None,
        skip_adapter: bool = False,
    ) -> Union[List[Record], List[str]]:

        if ef_search is None:
            ef_search = 40

        with self.client.Session() as sess:
            with sess.begin():
                # index ignored if greater than n_lists
                sess.execute(
                    text("set local hnsw.ef_search = :ef_search").bindparams(ef_search=ef_search)
                )


OCM-8202 | fix: remove redudant empty lines in manual mode

https://issues.redhat.com/browse/OCM-8202
Signed-off-by: marcolan018<EMAIL_ADDRESS>

/lgtm


[Tokenizers] String type support in Tokenizers

Tensors with ov::element::string are supported as input and output of tokenizer and detokenizer correspondingly. It is implemented via modifying StringTensorPack and StringTensorUnpack ops.
TODO:

[x] Python support, requires https://github.com/openvinotoolkit/openvino/pull/21532
[x] Sentence piece tokenizer op should accept string tensors in addition to u8 packed tensors
[x] Migrate tests from pack/unpack strings to native string tensor support

BTW, tests has SEGFAULT-ed https://dev.azure.com/openvinoci/dldt/_build/results?buildId=677113&view=logs&j=0609cd82-f9f7-5e70-371c-89fca78031ab&t=aa48ded0-ede8-5b33-eb68-fea5369468cc

BTW, tests have SEGFAULT-ed https://dev.azure.com/openvinoci/dldt/_build/results?buildId=677113&view=logs&j=0609cd82-f9f7-5e70-371c-89fca78031ab&t=aa48ded0-ede8-5b33-eb68-fea5369468cc

Tests haven't migrated yet.

Pass rate has been completely fixed with https://github.com/openvinotoolkit/openvino/pull/21761.

@apaniukov, please merge it after https://github.com/openvinotoolkit/openvino/pull/21761 is merged (expected tomorrow morning). Will require changes in llm_bench and genai. @Wovchena, @eaidova, FYI.

BTW, with current PR we have 1 more failed test (610 failed total) compared with current master (609 failed)

This PR is unblocked

build_jenkins


A fork showing how to use SemanticUI and how to create a multiple page web app

How to use SemanticUI: https://github.com/sadhen/Binding.scala-SemanticUI/tree/master
How to create a multiple page web app: https://github.com/sadhen/Binding.scala-SemanticUI/tree/another_page

Thanks to this awesome starter and @Atry 's help, starting from here, I've already used Binding.scala in  my personal project and I'm ready to use it in production
Hope it will be helpful for other Scala.js newbies!

Nice one, feel free to add a link to your fork in the readme.


Fix language codes  in 3.1

I want to merge this change because coping changes from #8015  to master.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-4331 Migrate translation objects to new language codes


Using materialised view with multiple group columns

Hi All, I am using the below query to generate materialized view for clickhouse but i want the result to be seperate  by both the names can anyone help on this one
CREATE MATERIALIZED VIEW IF NOT EXISTS analytics.uflow_topapps_bytes_flowdir_or_013_mv
  ENGINE = SummingMergeTree
  PARTITION BY toYYYYMMDD ( Timestamp )
  ORDER BY (Timestamp)
  POPULATE
  AS SELECT
  toString(AppId) as name_top_apps,
  IPv6NumToString(DstIP) as name_remote_top_emdpoints,
  sum(FlowStatsBytesFwd) as upload_bytes,
  sum(FlowStatsBytesRev) as download_bytes,
  sum(FlowStatsBytesFwd + FlowStatsBytesRev) as cumulative_bytes,
  sum(FlowStatsPktsFwd) as upload_flows,
  sum(FlowStatsPktsFwd) as download_flows,
  sum(FlowStatsPktsFwd + FlowStatsPktsRev) as cumulative_flows,
  toInt64((sum(FlowStatsBytesFwd)* 8)/least(sum(Duration),60)) as upload_rate,
  toInt64((sum(FlowStatsBytesRev)* 8)/least(sum(Duration),60)) as download_rate,
  toInt64(((sum(FlowStatsBytesRev) + sum(FlowStatsBytesFwd)) * 8)/least(sum(Duration),60)) as cumulative_rate,
  toStartOfInterval(`Timestamp`, INTERVAL 300 second) AS Timestamp,
  CpeCNID as  CpeCNID
  from analytics.sampled_uflow where AccessDenied = 0 and ( FlowDir == 2 or FlowDir == 0 or FlowDir == 3 )
  Group by ( CpeCNID, name_top_apps, name_remote_top_emdpoints, Timestamp)

Is your question related to clickhouse-grafana or clickhouse-server? What kind of "both the names" do you mean?
Could you provide more context? What are you trying to do?

Is your question related to clickhouse-grafana or clickhouse-server? What kind of "both the names" do you mean? Could you provide more context? What are you trying to do?

i want the results to be grouped by both name_top_apps, name_remote_top_emdpoints separately in single  query

opened in wrong froup


Call out Task modules not supported via JS in a tab - on mobile

OPS Build status updates of commit fb5778f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/task-modules/task-modules-overview.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 6cd2871:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/task-modules/task-modules-overview.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Coredump reporter

Copies CoredumpHandler, CoreCollector, FileHelper from node-maintainer to node-admin. (First 2 commits, no functional changes from original)
Made some some simplification to those based on that this will not run nodes with yinst state
Defined CoredumpReporter which can be implemented to handle authenticated and unauthenticated endpoints.

Copy, not move or shared ?

Made some some simplification to those based on that this will not run nodes with yinst state

And we don't want them when host-admin rolls out on-prem?

And we don't want them when host-admin rolls out on-prem?

My understanding is that we will not use yinst, so listing yinst state is not needed?

@hakonhall PTAL


FYI

https://github.com/ararslan/openspecfun-builder. SpecialFunctions.jl is currently using this.

I am just trying stuff out. Also, I think it is better we use the same framework instead of hand-rolling our own for each dependency.

I am just trying stuff out.

Sure, that's why it's just an FYI. 🙂

Also, I think it is better the community use the same framework instead of hand-rolling our own for each dependency.

I 70% agree with that; I think in some cases it's fine for people to do whatever as long as it works. Granted my repo also predates a lot of the more recent usability stuff for BinaryBuilder, and at this point BinaryBuilder is obviously the better solution.
Anyway, like I said, FYI.


agent: do not add taint for edge node automatically

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
agent: do not add taint for edge node automatically
REF: https://github.com/openyurtio/openyurt/pull/763
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

The yurtcluster-operator will not add the `node-role.openyurt.io/edge:NoSchedule` taint for the edge node.

Other Note

/cc @rambohe-ch

/lgtm


Add chaincase nolooking app for multiple channel opens via PayJoin (Experimental)

Would be great to get Nolooking as an app on the RaspiBlitz. While it is still tagged as "experimental", there is an app on the Umbrel as well.
Description:

Nolooking leverages Pay-to-Endpoint (BIP78 payjoin) to negotiate a channel open for your lightning node from any BIP78 supporting wallet. Previously, custom PSBT channel funding could only be done by signing PSBTs manually. A node running nolooking can open many new lightning channel with every inbound transaction, provided the payer supports BIP78. E.g. by using Sparrow wallet, BTCPayServer, or Wasabi; following the normal QR scan and payjoin payment flow. Read the article about Lightning Powered Payjoin to hear how it can save your privacy, time, and money!

Demo: https://twitter.com/utxoclub/status/1592460852690419712
Currently only for LND, but CLN integration is being discussed.
The Benefit would be to be able to easily open multiple LN channels in one transaction (saves on-chain fees!!!), which is very privacy preserving.

This would be a community addition to raspiblitz then - if anybody is interested, use this install script template:
https://github.com/rootzoll/raspiblitz/blob/dev/home.admin/config.scripts/bonus.template.sh


Allow disabling unneeded linkTypes

Currently, all linkTypes are always visible in the Link Editor. I know that is meant more or less a drop-in replacement for the Link Editor, but the original is already hard to use. It would be a massive advantage if the tabs could be unset or disabled. That way the editor could be used for an external link, internal link, phone number etc. only.

... but isnt this possible already?
https://github.com/sitegeist/Sitegeist.Archaeopteryx#disabling-link-type-editors
Well i think its currently undocumented, and only findable in the source code how the editors are named:

Sitegeist.Archaeopteryx:Asset (Asset)
Sitegeist.Archaeopteryx:MailTo (Mail to)
Sitegeist.Archaeopteryx:Node (Document)
Sitegeist.Archaeopteryx:PhoneNumber (Phone Number)
Sitegeist.Archaeopteryx:Web (Web)

All link types are documented before that block. So I think there is nothing to do here (in theory). For a better overview you could add all link types in the linked section, but IMO this is not required.

Thanks for your feedback, you are right indeed. To make the readme a bit more user-friendly, I created a PR: https://github.com/sitegeist/Sitegeist.Archaeopteryx/pull/51


[WIP] test cleanup

This is a cleanup of the "fsharp" suite, to make it simpler
Still to be finalized, submitting for more complete CI

@dotnet-bot test this please (changed hooks)

@KevinRansom A heads up that the changes delete the batch files for the "fsharp" suite (hence the 9000 line removal)
I'm working out how to compile the "fsharp" suite driver code for .NET Core, When run in that mode, can invoke the .NET Core F# compiler to run most of the tests (same coverage as the FSC_CORE permutation).
I'm trying to reduce the use of permutations and make things a bit more explicit.
Also am trying to allow those tests to be run from the F# REPL in scripting mode, something which has worked well for F# Compiler Service testing.

Also addresses https://github.com/Microsoft/visualfsharp/issues/889


Don't crash on unrecognized file types

This can happen in .js files with allowJs: false, or .gts/.gts files when the ember-template-imports environment isn't active. It manifests as Error: Could not find source file from TypeScript when calling into the language service for e.g. definition info.

Looking back over our conversation in Discord and the code here, were you actually seeing a crash @wagenet? We do log these errors, but I can't see how this would have brought down the language server.

@dfreeman I was seeing crashes, but I guess this wasn’t actually the culprit.


Add support to manage ovn-ic with systemd

This PR adds support to manage ovn-ic daemons with systemd.
Two new .service units are added: ovn-ic.service and ovsdb-server-ic.service.

ovn-ic.service systemd-unit manages ovn-ic daemon
ovsdb-server-ic.service systemd-unit manages OVN_IC_Northbound and OVN_IC_Southbound OVSDB server processes.

Let me know whether it is acceptable.

Thanks for the PR. This is definitely acceptable.
I will take a look hopefully soon.
Thanks

I've submitted this PR as patch series in the mailing list for further review - https://patchwork.ozlabs.org/project/ovn/list/?series=220521

Since ovn-ic needs to connect to OVN NB and SB DBs, user needs to define the connection parms to these DBs using the  system file - /etc/systemd/system/ovn-ic.d/local.conf (OVN_IC_OPTS) if ovn-northd service is not runnng in the same machine right ?

Yes, that's correct. Additionally user may supply OVN_IC_OPTS via /etc/sysconfig/ovn or /etc/sysconfig/ovn-ic.

@odivlad I've been thinking about the systemd service file you added to ovn-ic.
Did you consider making ovn-ic a sub package ? I checked with some of the fedora maintainers.
Although its not a hard rule, but having  a subpackage for a service is better.
Would you mind reworking  a bit to have a separate ovn-ic sub package ?
Thanks
Numan

@numansiddique, sure I can do this.
But one thing: if we move ovn-ic and related stuff to sub-package, existing deployments should install ovn-ic package explicitly on upgrade. Is it okay, or, maybe ovn-central package should require ovn-ic for backward compatibility?

And a second question, is it required to add firewalld xml for ovn ic? I can write config, by I don't use firewalld in my setup, so I can't test it in my env.

@numansiddique, I've updated PR with requested changes.

@numansiddique, please note that

if we move ovn-ic and related stuff to sub-package, existing deployments should install ovn-ic package explicitly on upgrade. Otherwise ovn-ic will be removed from the host on upgrade. Is it okay, or, maybe ovn-central package should require ovn-ic for backward compatibility?

I see, that commit is already in tree, but just want to double-check before those changes are released.
In my understanding most deployments will install ovn-ic on the central nodes. And technically they can run ovsdb-server-ic on one-two nodes of each AZ in multi-AZ deployments. Even if they want to deploy global ovsdb on a separate nodes, it's easy to install ovn-central.rpm.
Do we really need a subpackage?

@numansiddique, please note that

if we move ovn-ic and related stuff to sub-package, existing deployments should install ovn-ic package explicitly on upgrade. Otherwise ovn-ic will be removed from the host on upgrade. Is it okay, or, maybe ovn-central package should require ovn-ic for backward compatibility?

I see, that commit is already in tree, but just want to double-check before those changes are released.
In my understanding most deployments will install ovn-ic on the central nodes. And technically they can run ovsdb-server-ic on one-two nodes of each AZ in multi-AZ deployments. Even if they want to deploy global ovsdb on a separate nodes, it's easy to install ovn-central.rpm.
Do we really need a subpackage?

@numansiddique, please note that

if we move ovn-ic and related stuff to sub-package, existing deployments should install ovn-ic package explicitly on upgrade. Otherwise ovn-ic will be removed from the host on upgrade. Is it okay, or, maybe ovn-central package should require ovn-ic for backward compatibility?

I see, that commit is already in tree, but just want to double-check before those changes are released.
In my understanding most deployments will install ovn-ic on the central nodes. And technically they can run ovsdb-server-ic on one-two central nodes of each AZ in multi-AZ deployments. Even if they want to deploy global ovsdb on a separate nodes, it's easy to install ovn-central.rpm.
Do we really need a new subpackage?

I think we decided on the sub package based on the comment on 17th Dec.

@numansiddique, please note that

if we move ovn-ic and related stuff to sub-package, existing deployments should install ovn-ic package explicitly on upgrade. Otherwise ovn-ic will be removed from the host on upgrade. Is it okay, or, maybe ovn-central package should require ovn-ic for backward compatibility?

I see, that commit is already in tree, but just want to double-check before those changes are released.
In my understanding most deployments will install ovn-ic on the central nodes. And technically they can run ovsdb-server-ic on one-two central nodes of each AZ in multi-AZ deployments. Even if they want to deploy global ovsdb on a separate nodes, it's easy to install ovn-central.rpm.
Do we really need a new subpackage?

I think we decided on the sub package based on the comment on 17th Dec.

@odivlad I've been thinking about the systemd service file you added to ovn-ic.
Did you consider making ovn-ic a sub package ? I checked with some of the fedora maintainers.
Although its not a hard rule, but having a subpackage for a service is better.
Would you mind reworking a bit to have a separate ovn-ic sub package ?
Thanks
Numan

This one.

@odivlad I've been thinking about the systemd service file you added to ovn-ic.
Did you consider making ovn-ic a sub package ? I checked with some of the fedora maintainers.
Although its not a hard rule, but having a subpackage for a service is better.
Would you mind reworking a bit to have a separate ovn-ic sub package ?
Thanks
Numan

This one.

@odivlad I've been thinking about the systemd service file you added to ovn-ic.
Did you consider making ovn-ic a sub package ? I checked with some of the fedora maintainers.
Although its not a hard rule, but having a subpackage for a service is better.
Would you mind reworking a bit to have a separate ovn-ic sub package ?
Thanks
Numan

This one.

@numansiddique So do you think the ovsdb-server-ic (suggested to rename as ovn-ic-db) should be a submodule as well? It requires same components as regular ovsdb but just with IC-DB schemas.

Before the commit 8abe98f386ff2b4a1f2f7b61188a377a5d020429 ovn spec file was generating the below ovn packages

ovn

ovn-central
ovn-host
ovn-vtep

ovn is the main package and others are sub packages. And now with this commit, it generates
- ovn
- ovn-central
- ovn-host
- ovn-vtep
- ovn-ic
ovn-ic was split from ovn-central. I think this is fine.

@odivlad I've been thinking about the systemd service file you added to ovn-ic.
Did you consider making ovn-ic a sub package ? I checked with some of the fedora maintainers.
Although its not a hard rule, but having a subpackage for a service is better.
Would you mind reworking a bit to have a separate ovn-ic sub package ?
Thanks
Numan

This one.

@numansiddique So do you think the ovsdb-server-ic (suggested to rename as ovn-ic-db) should be a submodule as well? It requires same components as regular ovsdb but just with IC-DB schemas.

Before the commit 8abe98f386ff2b4a1f2f7b61188a377a5d020429 ovn spec file was generating the below ovn packages

ovn

ovn-central
ovn-host
ovn-vtep

ovn is the main package and others are sub packages. And now with this commit, it generates
- ovn
- ovn-central
- ovn-host
- ovn-vtep
- ovn-ic
ovn-ic was split from ovn-central. I think this is fine.

@numansiddique, sure I can do this.
But one thing: if we move ovn-ic and related stuff to sub-package, existing deployments should install ovn-ic package explicitly on upgrade. Is it okay, or, maybe ovn-central package should require ovn-ic for backward compatibility?

I thought about it when I suggested the change and I also tried out your patch. I think it should be fine as I don't see many users.
Are you ok with this ?

@numansiddique, sure I can do this.
But one thing: if we move ovn-ic and related stuff to sub-package, existing deployments should install ovn-ic package explicitly on upgrade. Is it okay, or, maybe ovn-central package should require ovn-ic for backward compatibility?

I thought about it when I suggested the change and I also tried out your patch. I think it should be fine as I don't see many users.
Are you ok with this ?

@odivlad I've been thinking about the systemd service file you added to ovn-ic.
Did you consider making ovn-ic a sub package ? I checked with some of the fedora maintainers.
Although its not a hard rule, but having a subpackage for a service is better.
Would you mind reworking a bit to have a separate ovn-ic sub package ?
Thanks
Numan

This one.

@numansiddique So do you think the ovsdb-server-ic (suggested to rename as ovn-ic-db) should be a submodule as well? It requires same components as regular ovsdb but just with IC-DB schemas.

Before the commit 8abe98f ovn spec file was generating the below ovn packages
* ovn

  * ovn-central
  * ovn-host
  * ovn-vtep

ovn is the main package and others are sub packages. And now with this commit, it generates

ovn
ovn-central
ovn-host
ovn-vtep
ovn-ic

ovn-ic was split from ovn-central. I think this is fine.

I mean for interconnection feature to work, we need two components. 1) the ovn-ic controller, which typically co-locate with ovn-central (although it is ok to deploy anywhere else but still at each OVN deployment /AZ level). 2) the OVN IC DBs, which is deployed as global instances. I think 1) is closer to the ovn-central, although I am ok to have it as a sub package, but 2) may be another sub package, right? Or do you mean 1) and 2) both in ovn-ic package and in each installation only part of it will be used?

@odivlad I've been thinking about the systemd service file you added to ovn-ic.
Did you consider making ovn-ic a sub package ? I checked with some of the fedora maintainers.
Although its not a hard rule, but having a subpackage for a service is better.
Would you mind reworking a bit to have a separate ovn-ic sub package ?
Thanks
Numan

This one.

@numansiddique So do you think the ovsdb-server-ic (suggested to rename as ovn-ic-db) should be a submodule as well? It requires same components as regular ovsdb but just with IC-DB schemas.

Before the commit 8abe98f ovn spec file was generating the below ovn packages
* ovn

  * ovn-central
  * ovn-host
  * ovn-vtep

ovn is the main package and others are sub packages. And now with this commit, it generates

ovn
ovn-central
ovn-host
ovn-vtep
ovn-ic

ovn-ic was split from ovn-central. I think this is fine.

I mean for interconnection feature to work, we need two components. 1) the ovn-ic controller, which typically co-locate with ovn-central (although it is ok to deploy anywhere else but still at each OVN deployment /AZ level). 2) the OVN IC DBs, which is deployed as global instances. I think 1) is closer to the ovn-central, although I am ok to have it as a sub package, but 2) may be another sub package, right? Or do you mean 1) and 2) both in ovn-ic package and in each installation only part of it will be used?

I think having separate package for ic would be better.
User needs to use the systemd service provided by the ovn-ic package on start ovn-ic on central node.
And the user can use the service - ovn-ic-db (added in this PR) to start ovsdb-servers on another node.

I think having separate package for ic would be better.
User needs to use the systemd service provided by the ovn-ic package on start ovn-ic on central node.
And the user can use the service - ovn-ic-db (added in this PR) to start ovsdb-servers on another node.

@numansiddique, @hzhou8, thanks for the review. If I correctly understood all comments, I'm doing next:

Rename ovsdb-server-ic.service to ovn-ic-db.service
Leave ovn-ic-db.service systemd-unit incide ovn-ic subpackage.
The Numan's suggestion was that we don't add any special requirements for ovn-ic in ovn-central subpackage. Users who upgrade from previous versions to new code and who run OVN Interconnection, must install manually ovn-ic subpackage on nodes where they run ovn-ic daemon and global ovsdb interconnection servers. Should this be mentioned in NEWS file?
Honestly, my opinion is that such small change can bring an unneeded headache to users. Are there any cons in adding ovn-ic as a Requires to ovn-central package? This can give backward compatibility, and in the same time users can install ovn-ic on any other then central node. What do you think about it?

@numansiddique, @hzhou8, thanks for the review. If I correctly understood all comments, I'm doing next:

Rename ovsdb-server-ic.service to ovn-ic-db.service
Leave ovn-ic-db.service systemd-unit incide ovn-ic subpackage.
The Numan's suggestion was that we don't add any special requirements for ovn-ic in ovn-central subpackage. Users who upgrade from previous versions to new code and who run OVN Interconnection, must install manually ovn-ic subpackage on nodes where they run ovn-ic daemon and global ovsdb interconnection servers. Should this be mentioned in NEWS file?
Honestly, my opinion is that such small change can bring an unneeded headache to users. Are there any cons in adding ovn-ic as a Requires to ovn-central package? This can give backward compatibility, and in the same time users can install ovn-ic on any other then central node. What do you think about it?

I've added fixup commit (with added requires to ovn-central). Let me know if it looks good, I'll squash it and reword with correct commit message.

I've added fixup commit (with added requires to ovn-central). Let me know if it looks good, I'll squash it and reword with correct commit message.

@numansiddique, @hzhou8, thanks for the review. If I correctly understood all comments, I'm doing next:

Rename ovsdb-server-ic.service to ovn-ic-db.service
Leave ovn-ic-db.service systemd-unit incide ovn-ic subpackage.
The Numan's suggestion was that we don't add any special requirements for ovn-ic in ovn-central subpackage. Users who upgrade from previous versions to new code and who run OVN Interconnection, must install manually ovn-ic subpackage on nodes where they run ovn-ic daemon and global ovsdb interconnection servers. Should this be mentioned in NEWS file?
Honestly, my opinion is that such small change can bring an unneeded headache to users. Are there any cons in adding ovn-ic as a Requires to ovn-central package? This can give backward compatibility, and in the same time users can install ovn-ic on any other then central node. What do you think about it?

I agree with you that its not a small change. I was just wondering if there are any users who build their own packages.
Normally from what I know, people would consume from either ubuntu, centos, fedora repos.
I looked into the instructions here - https://fedoraproject.org/wiki/Upgrade_paths_—_renaming_or_splitting_packages
I think we need to create compact packages when splitting the packages. I totally missed it earlier. Sorry. I normally study about packaging and the guidelines as and when required.
I'd suggest

Revert the patch 8abe98f by moving the ovn-ic related to ovn-central package.
Add the systemd files related to ovn-ic and make it part of ovn-central package.

I think we can revisit it later if we really need to split ovn-ic into its own package. What do you think ?
Thanks

@numansiddique, @hzhou8, thanks for the review. If I correctly understood all comments, I'm doing next:

Rename ovsdb-server-ic.service to ovn-ic-db.service
Leave ovn-ic-db.service systemd-unit incide ovn-ic subpackage.
The Numan's suggestion was that we don't add any special requirements for ovn-ic in ovn-central subpackage. Users who upgrade from previous versions to new code and who run OVN Interconnection, must install manually ovn-ic subpackage on nodes where they run ovn-ic daemon and global ovsdb interconnection servers. Should this be mentioned in NEWS file?
Honestly, my opinion is that such small change can bring an unneeded headache to users. Are there any cons in adding ovn-ic as a Requires to ovn-central package? This can give backward compatibility, and in the same time users can install ovn-ic on any other then central node. What do you think about it?

I agree with you that its not a small change. I was just wondering if there are any users who build their own packages.
Normally from what I know, people would consume from either ubuntu, centos, fedora repos.
I looked into the instructions here - https://fedoraproject.org/wiki/Upgrade_paths_—_renaming_or_splitting_packages
I think we need to create compact packages when splitting the packages. I totally missed it earlier. Sorry. I normally study about packaging and the guidelines as and when required.
I'd suggest

Revert the patch 8abe98f by moving the ovn-ic related to ovn-central package.
Add the systemd files related to ovn-ic and make it part of ovn-central package.

I think we can revisit it later if we really need to split ovn-ic into its own package. What do you think ?
Thanks

Agree, lets I'll update PR.

@numansiddique, RP is updated.

Thanks. I'll take a look.
Numan

LGTM (but I didn't test it)
@numansiddique what's our process for github PR review (v.s. mailing-list patches)

rocess for githu

I normally post the patches myself for review to the ML.
I'm doing it now.

@odivlad Can you please update the first commit with your signed-off-by tag ?
Meanwhile I will add your tag myself and post it to the ovs-dev ML. I hope its fine.
Thanks
Numan

Patches posted here - https://patchwork.ozlabs.org/project/ovn/list/?series=227739

Meanwhile I will add your tag myself and post it to the ovs-dev ML. I hope its fine.

That's okay, thanks :)

Thanks for the PR. The patches are applied to the master branch.


Fee payment in community currency

Closes #269

Tested so far:

Alice could register without CC
Alice sent Ferdie 0.08 CC (Ferdie has no native tokens)
Ferdie could send 0.4 CC to Eve. Eve was successfully endowed according to polkadot-js
Ferdie could successfully register for the next ceremony.

Extrinsics not tested so far:

submittingClaims
endorseNewcomer
claimingRewards

Yes, you are right about the fallbacks. I thought for pragmatism I leave it at that for now, but there might already be cases where this is impractical. I will change that.

Ah, got the mecanism. I see fallback to native with null

I tested the same things you tested on rococo. All good
we should test an entire ceremony flow twice:

bootstrap Alice, Bob, Charlie
second ceremony: send funds to new account and register together with two bootstrappers
newbie sends claim extrinsic


Update number lookup feature from GA to preview

Data Plane API - Pull Request
We are delaying the release of GA.  Instead we'll release the feature updates as another preview.
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue: https://skype.visualstudio.com/SPOOL/_workitems/edit/3431711/

Is this review for (select one):

[ ] a private preview
[X] a public preview
[ ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:
Previous API Spec Doc: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/communication/data-plane/PhoneNumbers/preview/2023-05-01-preview/phonenumbers.json
Updated paths: /operatorInformation/:search

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

Checks stuck in `queued` state?
If the PR CI checks appear to be stuck in `queued` state, please add a comment with contents `/azp run`.
This should result in a new comment denoting a `PR validation pipeline` has started and the checks should be updated after few minutes.

Do we have to review this whole thing or look at something specific?
Or, is there a review meeting set up and discuss it then?

Do we have to review this whole thing or look at something specific? Or, is there a review meeting set up and discuss it then?

We had a review for this feature which we were originally planning to take to GA, but we decided to release it as an update to public preview before going to GA.  The only endpoint that is relevant for review is /operatorInformation/:search and its associated definitions

@JeffreyRichter and @markweitzel the PR says it's blocked until someone from the Stewardship Board signs off, what do I need to do here to get that approval?  Does @JeffreyRichter your sign-off not remove this blocking condition?


Implement retry_max; update schema docs

Fix the schema documentation: remove the mentions of the obsolete arguments limit_read and limit_write.
Implement one of the enhancements suggested in https://github.com/Valodim/terraform-provider-desec/issues/7: expose the RetryMax option of the deSEC API client as retry_max (Integer) — an optional schema argument. The default value is determined by the desec module (5 at the moment).

Sorry for the delay, I had missed the notification. Changes look good, thanks for your PR! :+1:


btn-group-vertical gaps with toggle buttons

btn-group-vertical leaves gaps when used with label-style toggle buttons. On the left is standard vertical group, followed by checkbox and radio versions:

        <input type="checkbox" /> One

        <input type="checkbox" /> Two

        <input type="checkbox" /> Three

I don't think that class is designed to be used with label

Possibly. Switching from label to something non-semantic like span seems to fix the problem. The docs use label for toggle buttons. The following works:

        <input type="checkbox" /> One

        <input type="checkbox" /> Two

        <input type="checkbox" /> Three

Did you test against v4.0.0-alpha.2, or against the v4-dev branch?

It's the dev branch. I learned that lesson on the first issue that I opened. =c)


Create Intent Blocks on Voiceflow

Idea: create intent blocks on Voiceflow platform

Use the VoiceFlow API in our application and give the functionality to the user to click on an intent block and then see the intent on the VoiceFlow page.


copr: skip calculating fmsketch when collecting statistics

What is changed and how it works?

Issue Number: Close #xxx
What's Changed:

The PR is to test whether calculating fmsketch is the bottleneck of analyze.

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

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

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note
Please add a release note.

Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with None.
If this PR will be picked to release branch, then a release note is probably required.

/run-build-arm64 comment=true


Add C# 7.1/Latest versions to project system

cc @davkean @jcouv @VSadov @jaredpar
This adds 7.1 language version, and a "Latest" option. More details in https://github.com/dotnet/roslyn/issues/17173

A few notes, please let me know if I missed something.

Noticed this area is not covered by any tests.
The strings are not localized as well (default item).
This version is intended for VS 15.3. Is master the correct branch to use?

Nice. Thanks
If it looks ok, what do you think of sorting the list differently: putting "default" after 7.0, and "latest" after 7.1?

@jcouv my two cents: in most UIs I've seen, the default item is always the first. It is what I'd expect as a user, not in the middle of the list.
I'm impartial about latest. It can be second (the current status) or last item.
@dotnet/roslyn-compiler @dotnet/project-system

@OmarTawfik Sound good. Having "default" as first entry does make sense too.

C#7.1

@davkean @basoundr localization added, and tool not run per #1794.
Not sure why language version is extracted into it's own utility, contradicting with how all other drop boxes are populated though.
This is ready for review @dotnet/project-system

Just to set expectations, this is going into 15.3?

Yes. VS 2017 Update 1.
cc @jaredpar @jcouv


minor typos in comments, removed tautology

(m_spentToday + _value >= m_spentToday) == (_value >= 0) == true

because
uint _value

It is not a tautology, because those are not integers. It is a n arithmetic overflow protection.

overflow protection

Yes, at first I had suspected exactly that.
Then I used solidity-repl to test if this throws an exception perhaps:
uint a = 2**255
a * 2

But it doesn't. It results in a
0

and
0 <= any uint

Or where is the flaw in my thinking?

those are not integers

What do you mean by that?
Doesn't uint mean unsigned integer?
uint m_spentToday
uint _value

Also tested with +
solr example input

Now I got it.
The overflow protection is not by throwing any errors, but if m_spentToday + _value overflows, then
m_spentToday + _value >= m_spentToday

is false.
Clever.
I suggest a comment in the code, to explain that.
From my pull request then only the typos remain.

Thx a lot, @chriseth - my patch-1 branch is deleted. Have a great day ;-)


Mount proxy as file in OneAgent being backwards compatible

Description
Please include the following:

A meaningful PR title guidelines
A summary of the change
Which issue is fixed (if there is one)
Relevant motivation and context

How can this be tested?
Please include some guiding steps on how to test this change during a review.

What environment is necessary for the change to be noticeable ?
What needs to be enabled/applied for the change to be noticeable ?

Checklist

[ ] Unit tests have been updated/added
[ ] PR is labeled accordingly with a single label
[ ] I have read and understood the contribution guidelines

Codecov Report
Attention: 24 lines in your changes are missing coverage. Please review.

Comparison is base (8d52618) 65.20% compared to head (b2fed94) 65.12%.
Report is 2 commits behind head on main.

Files
Patch %
Lines

...ontrollers/dynakube/oneagent/daemonset/env_vars.go
67.74%
7 Missing and 3 partials :warning:

...ntrollers/dynakube/oneagent/daemonset/daemonset.go
40.00%
4 Missing and 2 partials :warning:

pkg/controllers/dynakube/proxy/volumes.go
0.00%
5 Missing :warning:

pkg/controllers/dynakube/controller.go
40.00%
2 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2608      +/-   ##
==========================================
- Coverage   65.20%   65.12%   -0.08%
==========================================
  Files         251      252       +1
  Lines       16447    16472      +25
==========================================
+ Hits        10724    10728       +4
- Misses       4899     4915      +16
- Partials      824      829       +5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Various improvements

Added a number of extra features, including

Support for canonicalisation of radical SMILES with OBCanonicalRadicals
NN ensemble uncertainty quantification
Automated hyperparameter optimisation

Also fixed a number of bugs, allowing for smoother operation when called in an automated fashion (e.g. through a bash submission script on a cluster, where a headless environment is necessary).

Great! Thanks for adding this. I actually added & removed some of these features on my local copy,  but did not merge.


feat: :sparkles: allow TLS certificates for authentication (support AWS IoT)

Hi,
In this PR I've added the ability to provide a path to the certificate files that the client will use to authenticate. This allows authentication with AWS IoT Core using certificates only, which is a requirement of mine.
I've tested this as working to authenticate with AWS, without a username or password.

Hi @SootyOwl,
Thanks for your contribution to the MQTTAsgi project!
This will allow many more use cases for the server. The only thing we are missing is the parameter documentation in the README file.

Hey @sivulich, I've added parameters to the table in the README.

Many thanks @SootyOwl ! I'll upload a new package with the new features to Pypy soon!


[Project Addition]: Web Application for Deaf Community

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title :  Web Application for Deaf Community
:red_circle: Aim: Assisting individuals with hearing impairments to facilitate communication with the Deaf community
:red_circle: Dataset : Gesture Recognition Datasets
:red_circle: Tech Use : Python, Tensorflow, Keras, OpenCV
:red_circle: Approach: Finding the movements of hands through pre-trained models like media pipe and VITpose then taking the model with the most precise output and then assigning keywords to every movement of actions.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name : VIshwajeet Gehlot
GitHub Profile Link : https://github.com/vishuhere
Email ID<EMAIL_ADDRESS>Approach for this Project : Finding the movements of hands through pre-trained models like media pipe and VITpose then taking the model with the most precise output and then assigning keywords to every movement of actions.
What is your participant role? (Mention the Open Source program): GSSOC 2024 Contributor

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Can you share the dataset URL? Also what are the algorithms you are planning to implement here, can you specify them?
@vishuhere

Custom Dataset: I will use my own specific application, I will collect my own dataset by recording hand gestures using a webcam as I have a specific set of gestures relevant to my use case.
CNN Dataset will be used.
For Dataset url: It's not created yet.I will implement it from the scratch as I had already worked on this thing you can go through my github for more info. Also feel free to reach me anytime for such query I'm happy to clear your doubts.
PS: While assigning the task kindly put GSSOC with level3 on it.Thanks.

What are the algorithms you are planning to implement here, can you specify them? And for the level tag, initially all the deep learning issues are being given as level2, after judging the pull request and your contribution it can be upgraded to level3.
@vishuhere

Algorithmic steps involved in developing the model through hand gesture recognition:

Data Collection: I will Gather a dataset of hand gesture images or videos along with their corresponding labels.

Data Preprocessing: I will Preprocess the dataset to ensure uniformity and compatibility, including tasks like resizing images, normalization, and augmentation to increase dataset variability.

Feature Extraction: Extract relevant features from the preprocessed images or videos. This may involve Convolutional Neural Networks (CNNs) technique for automatic feature learning.

Model Selection: This part will be handled by Conventional Neural Networks (CNN).

Model Training: Training the selected model using the Custom dataset.

Model Evaluation: Evaluate the trained model's performance on a separate validation or test dataset to assess its accuracy and precision.

Deployment: Integrating the model into the website, or embedded system for real-time recognition.

Looks good to me! Issue assigned to you @vishuhere


Create OIDC connection between a configured Authentik and 2 applications

E.g. a Nextcloud instance and a Zulip instance.

@nicolas-semaphor , @augke
Please add your working configs to this branch.. to make it testable outside your infrastructure

@nicolas-semaphor @augke Can we close this as done?

@nicolas-semaphor: Closing issue as done, please reopen and add a tasklist or create new issues if not all contained work is done.


Remove Octicons and replace with a pure CSS status circle

For me, when I switched from the Rails asset pipeline over to Webpacker, the squirrel icons turned into little squares. I didn't want to have to download Octicons or create some hacky solution so I figured I would create a pull request to remove the icons altogether.
This pull request replaces the squirrels with a simple circle in the CSS and drops the trashcan icon in favor of the word Delete to match the other buttons on the page. It also saves 180kb most of which wasn't used.
Screenshots:

I would be fine with making this change, but would like @jnunemaker to chime in just to make sure there isn't more to having the squirrel icons.

I'll miss them but I'm fine with reducing dependencies. 👍

I haven't checked this on mobile but I'm assuming it's fine. I'll merge it soon if @thetimbanks doesnt.

I'd maybe go with remove instead of delete. I usually think add and remove or create and delete. Minor and I'd be curious if anyone else has any opinions on that.

@jnunemaker Yep, contextually that makes a lot more sense. I've made the change.


fixes vapor pressure error above critical temperature

addresses https://github.com/NREL/GEOPHIRES-X/issues/214

Will add a new test case based on:
End-Use Option, 2
Reservoir Depth, 6
Gradient 1, 75
Reservoir Model, 1
Time steps per year, 6
Maximum Temperature, 500


[entropy_src] Issues with Observe FIFO interface

There are two minor usability issues with the Observe FIFO Interface have been observed in the course of verification.

It is currently unclear what happens when OBSERVE_FIFO_THRESH is set to 0.   From the RTL it appears that if this is set, then the Observe FIFO will always fire an interrupt.
Recommendation: Disable this interrupt when this register is set to zero.
SW Workaround: Don't use zero as the level for this interface

There is no way to check that the Observe FIFO is not empty, only that it's value exceeds some threshold.   This may be fine if SW reads are the only way of removing or clearing this FIFO.     However disabling the IP also clears the Observe FIFO.  This can cause some confusion when SW is trying to clear it.
Recommendation: Add a depth register.
Workaround: Clear the Observe FIFO interrupt when disabling the IP, and whenever finishing an Observe read.
Example scenario:

SW requests a OBSERVE_FIFO_THRESH of 16, and polls for data.
Polling completes and SW reads the data.  (Usual procedure: read OBSERVE_FIFO_THRESH words, and clear the interrupt)
A health check interrupt fires, SW clears the interrupt and re-enables the IP, clearing the Observe FIFO in the process.
Interrupt controller exits and control returns to reading Observe FIFO data.  SW has no way of knowing that the Observe FIFO has been cleared.  Continued reading of the Observe FIFO triggers an underflow and a fatal error

FYI: @cfrantz @mcy @tjaychen @moidx @zi-v

Note: The workaround to problem 1 has already been merged as part of the test bench flow.  The DV workaround for the problem 2 will be added in an upcoming PR.  (No changes have been made to the DIFs for either of these cases)

Re 2: Can we handle the FIFO clearing part of "health check interrupt" at main?
E.g.: Disable CSRNG/EDN inside the interrupt and flag the main SW that it needs to gracefully clean the FIFO and re-enable the RNG subsystem.

There are lots of ways to work with problem 2 in Software. I just recommend we add a depth register at some point to let SW know what is happening for troubleshooting.

After digesting the two problems, here is my conclusion:
Problem 1: Agreed that zero is not useful, and interrupt should be gated with a zero depth status. Also, update doc to say that zero is reserved.
Problem 2: At construction, considered a depth register, but aim was to limit extra registers if possible (area, testing,etc). But there is no doubt it may be useful in both operation and debug modes. Also, other surrounding logic has now changed that added this register is now required when it was not before. Adding a depth reg.


Confusing error for missing { in JSX attribute initializer object

Bug Report

🔎 Search Terms
jsx attribute expression initializer double brace bracket object cannot find name
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about JSX

⏯ Playground Link

Playground link with relevant code
💻 Code
declare const MyComponent: any;

<MyComponent
  data={ someValue: true }
/>;

🙁 Actual behavior
  data={ someValue: true }
//       ~~~~~~~~~ Error: Cannot find name 'someValue'.

Anecdotally, this is a pretty common mistake and I make & see it fairly often. [example Discord question]
🙂 Expected behavior
This error message is unrelated to the actual issue, that the contents inside the JSX attribute initializer need to have double { around them.
  data={{ someValue: true }}

How about adding a suggestion like Did you mean to add '{}' brackets around the attribute value, ideally with an auto-fixer?

I guess you could speculatively parse an identifier and then a : in these positions. Not sure what you'd do with the : though.


fix: Run "go mod vendor" and "go mod tidy"

What this PR does / why we need it:
Updated the vendor files.
Release note:
None

\n    <v1.VirtualMachineInstancePhase>: Pending\nto equal\n    <v1.VirtualMachineInstancePhase>: Running",
      }
      Assertion in callback at /go/src/github.com/kubevirt/vm-console-proxy/tests/proxy_test.go:312 failed:
      Expected
          <v1.VirtualMachineInstancePhase>: Pending
      to equal
          <v1.VirtualMachineInstancePhase>: Running
  In [BeforeEach] at: /go/src/github.com/kubevirt/vm-console-proxy/tests/proxy_test.go:313 @ 02/22/23 11:11:13.087
------------------------------
Summarizing 3 Failures:
  [FAIL] Token /vnc endpoint with VMI [BeforeEach] should fail if VMI does not exist
  /go/src/github.com/kubevirt/vm-console-proxy/tests/proxy_test.go:313
  [FAIL] Token /vnc endpoint with VMI [BeforeEach] should proxy VNC connection
  /go/src/github.com/kubevirt/vm-console-proxy/tests/proxy_test.go:313
  [FAIL] Token /vnc endpoint with VMI [BeforeEach] should fail if token is expired
  /go/src/github.com/kubevirt/vm-console-proxy/tests/proxy_test.go:313

https://github.com/kubevirt/vm-console-proxy/blob/0304c6e222b16cfd65f7e9d41587f7603bac415d/tests/proxy_test.go#L309-L313
Smells like we need a longer timeout than the current 60 seconds?

Yes, I've increased the timeout in the latest revision.

/retest

There is a problem with kubevirt on OCP 4.13. It cannot start a VM.
That is not related to this PR.
/override ci/prow/e2e-functests

/test ci/prow/e2e-functests

/approve

/cc @0xFelix @lyarwood

Can you put the changes into two separate commits please?


⚠ ClamAV has degraded performance

In a337b8e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 468 ms

Resolved: ClamAV performance has improved in 88a1a9b.


Elasticsearch 5.0

The go library for Elasticsearch is available for version 5, while elogrus still uses v3.
Are there any plans to support v5?

I'll look at it. Thanks for update. 👍

simple support added. The context support added via Cancel func on hook.


Some difference on benchmark score with lm-eval compared with the original paper

Hello. I was doing some test on the "MatFormer-OLMo-1300M" checkpoint in this repo. When I measured the performance of some benchmarks and compared them with the data from the paper(Table 14), I found that some benchmark have quite different results.

Generally, the results I get from MatFormer-OLMo-1300M with lm-eval has lower accuracy in most benchmarks.
Here is the code I used to collect data and produce the image: CollectData.zip
To use the code, run python collect_data.py with environment variable MATFORMER_OLMO_CHECKPOINT_PATH set to the checkpoint directory to collect data. Then run python draw_matformer.py . to produce the image.
In the code, I packed the model into huggingface PreTrainedModel, in file "utils/LoadModel.py", to use the lm-eval interface .
Any ideas about why the difference happened?

Yes, because the paper's models are not OLMO or the same data we used. MatFormer-OLMO is an attempt at open-source reproduction but not equivalent. It is to give an idea of scaling to the public in an Open Source way.
Apologies. The only models from paper which are truly public and match numbers are here (MatViT models): https://github.com/google-research/scenic/tree/main/scenic/projects/matvit
let me know if I could help you with anything.

So you think the difference in model structure and training procedure caused the different testing results? I suspected that, but didn't realize the gap would be so large(seems OLMo version almost get lower score in every benchmark, and with large gap in some cases).
If convenient, do you see any mistake or misunderstanding in my testing code that could make the result unreliable?
For example, I set tokenizer.eos_token_id=0 in collect_data.py to make autoregressive tasks to run, but why it wasn't set when the tokenizer was initially loaded? And would extracting base_tokenizer from the originally loaded version in LoadModel.py affect the encoding results in the benchmark?
Thanks


Add github repo destroy under a  destroy flag

Overview
Today this is the process to remove a github installation.
./kubefirst destroy
./kubefirst action remove-github
./kubefirst clean  --destroy-buckets --destroy-confirm

Following the rule:

What init does, clean undo.
What cluster create does, destroy undo.

The action ./kubefirst action remove-github  could be executed protected by a flag to allow opt-into the behavior.
Example:
./kubefirst destroy --remove-github-repos

--remove-github-repos would remove gitops,  metaphors repos, and ssh keys added to the account.

Why it is opt-in?
because as it remove user information, like code on their github account we want to ensure they are aware of that, and we are unable to recover a backup of it.

from @converge:

since we dont have a user input to confirm the step, I would follow same approach we have for bucket destroy , and add extra flag --confirm-remove-github as a temporary solution


Create a 'configuration' section

Something I noticed when I was suggesting that a new pull request needed to update the documentation is that we don't actually have a section which explains all the different parts of the configuration.
I wonder if this might be more helpful for a user than having this information scattered across all the different documentation sections.
Setting up Mautic, most of the time you will work through the configuration step-by-step, so I feel like it would be more helpful if this information was all in one place and we use deep linking to hook people into the relevant section using the header anchor tags when they are elsewhere in the documentation.
For example if I'm in the email section and mention about the bounce settings we could just link to the header in the configuration > email settings section.
What do you folk think?
Totally open to discussion!

I totally agree with this suggestion, @RCheesley. In fact, there is quite a bit of information about some of these configuration settings that are currently missing/ not documented at all. I had highlighted this bit about email settings in my proposal.
Having a separate Configuration section with all the information in one place makes more sense than having it scattered the way it is all over the docs currently.

An additional idea @RCheesley if we have a configuration section then we have sub sections under that explains step-by-step guide to how to configure Mautic for e.g emails etc. And the rest.

I may have a slightly different opinion, Currently, I think the doc is easily accessible and sections grouped accordingly and if we put all the configuration into a single section we would have to remove some part of the docs which only content is the basic configuration For e.g Field Mapping as to avoid duplication.
I don’t think the configuration information is being scattered in the docs, I think it addresses what needs to be addressed to the user needs at that time. For e.g If a user wants to set up the plugin icontact I would prefer all information on how to do so be present on the page.
Also if we remove the configuration subsections in some of the docs, some part of the docs would be sparse and hold little information
This is my view, it's totally open to criticism as I am willing to learn other views on this

We now have a pretty good explanation of the Configuration at https://kb.mautic.org/knowledgebase/installation/configuration.


testing: bugfix addressing data race when testing job creation

I'm new to this repository and testing out the features currently implemented. After a clone, I noticed that while go test ./... was passing, when adding the --race param, you encounter the following race:
==================
WARNING: DATA RACE
Write at 0x00c00001f620 by goroutine 33:
  github.com/NYTimes/video-transcoding-api/db/redis.(*redisRepository).CreateJob()
      /Users/Symborski/dev/video-transcoding-api/db/redis/job.go:19 +0x1ad
  github.com/NYTimes/video-transcoding-api/db/redis.TestCreateJobIsSafe.func1()
      /Users/Symborski/dev/video-transcoding-api/db/redis/job_test.go:101 +0x96

Previous write at 0x00c00001f620 by goroutine 25:
  github.com/NYTimes/video-transcoding-api/db/redis.(*redisRepository).CreateJob()
      /Users/Symborski/dev/video-transcoding-api/db/redis/job.go:19 +0x1ad
  github.com/NYTimes/video-transcoding-api/db/redis.TestCreateJobIsSafe.func1()
      /Users/Symborski/dev/video-transcoding-api/db/redis/job_test.go:101 +0x96

Goroutine 33 (running) created at:
  github.com/NYTimes/video-transcoding-api/db/redis.TestCreateJobIsSafe()
      /Users/Symborski/dev/video-transcoding-api/db/redis/job_test.go:99 +0x3b9
  testing.tRunner()
      /usr/local/Cellar/go/1.11.5/libexec/src/testing/testing.go:827 +0x162

Goroutine 25 (running) created at:
  github.com/NYTimes/video-transcoding-api/db/redis.TestCreateJobIsSafe()
      /Users/Symborski/dev/video-transcoding-api/db/redis/job_test.go:99 +0x3b9
  testing.tRunner()
      /usr/local/Cellar/go/1.11.5/libexec/src/testing/testing.go:827 +0x162
==================

I made a quick change to address this issue and make the test a little more robust.
~/dev/video-transcoding-api ➤ c79d88c|bug-test-datarace⚡ ± go test ./... -race
?   	github.com/NYTimes/video-transcoding-api	[no test files]
ok  	github.com/NYTimes/video-transcoding-api/config	(cached)
ok  	github.com/NYTimes/video-transcoding-api/db	(cached)
ok  	github.com/NYTimes/video-transcoding-api/db/dbtest	(cached)
ok  	github.com/NYTimes/video-transcoding-api/db/redis	(cached)
ok  	github.com/NYTimes/video-transcoding-api/db/redis/storage	1.073s
ok  	github.com/NYTimes/video-transcoding-api/provider	(cached)
ok  	github.com/NYTimes/video-transcoding-api/provider/bitmovin	(cached)
ok  	github.com/NYTimes/video-transcoding-api/provider/elastictranscoder	(cached)
ok  	github.com/NYTimes/video-transcoding-api/provider/elementalconductor	(cached)
ok  	github.com/NYTimes/video-transcoding-api/provider/encodingcom	(cached)
?   	github.com/NYTimes/video-transcoding-api/provider/hybrik	[no test files]
ok  	github.com/NYTimes/video-transcoding-api/provider/zencoder	(cached)
ok  	github.com/NYTimes/video-transcoding-api/service	(cached)
ok  	github.com/NYTimes/video-transcoding-api/swagger	(cached)

Codecov Report

Merging #208 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #208   +/-   ##
=======================================
  Coverage   78.62%   78.62%
=======================================
  Files          29       29
  Lines        2914     2914
=======================================
  Hits         2291     2291
  Misses        372      372
  Partials      251      251

Continue to review full report at Codecov.

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

There's a test failure with golang at master that looks to be a preexisting condition. Will see if I can track that down too in another PR.

@zsiec thanks for fixing this! I'll add tip to allow_failures and investigate what's going on with the swagger validation on Monday or Tuesday x)


Content with many anchors can expand past right-hand nav

ie. /guides/kubernetes/app-enhancements-spring-k8s/
Not sure if the answer here is to assess how this right-hand nav is displayed or limit the number of anchors, but something to look into.

Got a screenshot of the issue?


Attendance

Can the attendance section be set up to view and print from date ranges?

Sure anything is possible with proper motivation and environment.
P.Lane
KC9EYE

From: tea1677<EMAIL_ADDRESS>Sent: Thursday, September 17, 2020 7:20:53 AM
To: kc9eye/UData<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [kc9eye/UData] Attendance (#98)
Can the attendance section be set up to view and print from date ranges?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/kc9eye/UData/issues/98, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB2C2ZV5IJ6Q3AA5QQFMMLDSGH5KLANCNFSM4RQLD4NQ.


Android App?

I was wondering if we could have an app.
And yes I am bored and don`t have ideas for what to do.

No
Same, I want to do some js at the moment

Github has live updates... Anyway, I need ideas

Interesting idea, but we don't even have a fully functional site yet!
(R.I.P ScratchyApp :P)

Who says, That Scratchy App is dead https://www.youtube.com/watch?v=ns3M1Sj6x4o


Set up ESLint

Only need a simple configuration.

Addressed in the "Version 3" work (see the v3 branch).


Update provided results.json file.

This results.json file has data for tasks:

TOP_10,
TOP_100,
TOP_100_COUNT,
COUNT,

and engines:

tantivy-0.21,
lucene-9.9.2,
lucene-9.9.2-bp,
pisa-0.8.2.

FWIW I did two runs of the benchmark, and got similar results, which suggests that there hasn't been too much noise.


Change default file permissions.

This changes the default perms in the configuration files in order to
preserve privacy and enhance security in a shared system. The files are
only readable by root.

Rather than setting the modes to restrictive all the time I've added two new parameters config_dir_mode and config_file_mode so they can be configured as needed. Thanks for the suggestion.
There's a little bit more I want to get done before I push the next release up to the forge, but it should be there soon (hopefully today or tomorrow).


Update PhantomJS in installation script

Also make it easier to update phantomjs version in the future

@tricao this is a bit outdated now, the latest version of PhantomJS is 2.1.1, but the newer format you've used looks better and more maintainable.

Hi @tricao,
If you can update this to use the latest PhantomJS 2.1.1 branch and confirm that doesn't break Sketchy, I'll accept this pull request.  Thanks for your help!

I bumped phantomjs to 2.1.1 and tested with some major sites and they all worked.
Glad I could help a bit.

Thanks!


FoundationEssentials: adjust error code constants for Windows

The Windows API calls return ERROR_TOO_MANY_OPEN_FILES (4) which is "The system cannot open the file.". One of the tests ensures that the return code is 260 which does not match reality.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@jmschonfeld - anything else left for this? I have one more change after this for FileManager, and I think that we are nearly done!


Suggestions of a discord user

This is ready for merge, awaiting Discord support approval of the privileged GUILD_MEMBER intent