Add Docstrings to pyiceberg/table/inspect.py

I would like to try and complete this one please.

Assigned it to you @askalik 🎉


Unable to import json file in Safari/Mac

Import button isn't active. Chrome/Mac works fine
Safari Version 9.1 (116<IP_ADDRESS>)
Max OS X 10.11.4

Issue reopens here


Set-DbaSpConfigure works but outputs wrong and missing info in warning

Just needs some variables fixed

Submitted PR. Do we need pester for that? Cause rn there is none 🤷♂

closed via https://github.com/sqlcollaborative/dbatools/commit/4c24b0b9d78c1169afee5fd285bbb8f7d0b54abf


Chore ug fix rexong

Codecov Report
Base: 61.42% // Head: 61.42% // No change to project coverage :thumbsup:

Coverage data is based on head (21b2f06) compared to base (c3a4e22).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #315   +/-   ##
=========================================
  Coverage     61.42%   61.42%
  Complexity      627      627
=========================================
  Files           112      112
  Lines          2263     2263
  Branches        257      257
=========================================
  Hits           1390     1390
  Misses          779      779
  Partials         94       94

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


flake8 Integration

Added a few lines to tox.ini after reading this . Hope this works.

Hi @ydjain,
thx for the patch. How do you call flake8 from tox? In Home Assistant, flake8 is automtically called when running tox. When I run tox, I do not see any results from flake8 and I would expect to get a lot of warnings...

Hi I have realised my stupidty :stuck_out_tongue_closed_eyes:  and have made changes accordingly...I have added pylint too...all issues raised by flake8 have been resolved

looks great, thx!


Mappings with Snippet Choice Nodes

Make sure you have done the following

[X] I have updated to the latest version of blink.cmp
[X] I have read the README

Bug Description
Given a snippet with a choice node, and a supertab keymap
a snippet such as this
{
  "coc": {
    "body": "${1|fix,feat,build,chore,ci,docs,style,refactor,perf,test|}(${2:scope}):${3:title}",
    "prefix": "coc"
  }
}

will need <c-y> to accept from the choice node.
Relevant configuration
keymap = { preset = 'super-tab' },

neovim version
NVIM v0.11.0-dev-1408+gffaab09e99
blink.cmp version: branch, tag, or commit
0.8.1

Seems like this would be up to the snippet provider you're using. The default uses the built in vim.snippet but there's also LuaSnip and mini.snippets

I think it gets a bit more complicated than that to overwrite, as if you wanted to use <Tab> for that menu too, then blink has already set buffer local keys maps for the key

Ah I see, you want the completion menu to popup with the options. Putting this in the backlog for now


Move the location tracker and isInfected() to a background process (isolate)

Useful link: https://pub.dev/packages/workmanager

unecessary


Rollup of fixes

Update development dependencies to the latest
Update badges and links in the readme
Use the full twisted version of 13.1.0 not 13.1
Pull in support for managing the nofile limits from #232

All of these look good to me :+1:

@tas50 Any reason to wait on this? It's mostly small fixes that look pretty sane to me, but if you have a few more to tack on I can wait to merge

Merge away.  I'd merge, but I don't have access.


[The Forest] Server Launch Failure

Oxide version: Core 2.0.3596
Game name and version: The Forest 0.69
OS version: Windows Server 2016

Problem
Server does not reach full initialization.
The Forest Dedicated Server just stops doing anything past the "The Forest Server is Vac Secure!" (If enabled otherwise stops at after "Connected to Steam Successfully"
Is still responding in tasks but memory usage does not change, still shows process activity.
Logs are clean. No errors.
Reproduction

Install Oxide into Server Directory
Run Server Application

I noticed that once, but can't reproduce it anymore. Oxide doesn't control how your server starts though, so I suspect the issue lies with the game itself, perhaps with save loading.

Test without Oxide loads fully with no issues.
Able to connect and use server.

im testing 2 days ago... can't start official steam server throught , but still i don't know why , im on it too @lukespragg

I'll take a look in a bit. Unsure why it's doing that.


integrations: Changed screenshot for SVN bot in static folder.

https://github.com/zulip/zulip/pull/32539

@Niloth-p please take a look.

This looks good to me!
The commit message needs to be edited.

"in static folder" - this need not be explained in the commit message, as the edited files and their file paths are already visible in the commit.
We use present tense in the commit titles.
We want to mention the motive of this change in the commit title - so being specific like "Update outdated screenshot" instead of "change screenshot" could help clarify the reason for the change.
SVN can be updated to Subversion.
And it would help to link back to the issue with "Fixes part of #num." in the commit body.

The screenshot looks much improved indeed.
Though it would help to have tech-business-themed examples, I think this looks fine too.

Let's be consistent about using "subversion" rather than "svn" in the screenshot, too.


MINOR: Resolve SslContextFactory method deprecations

The SSLUtilsTest uses the deprecated methods SslContextFactory#getNeedClientAuth and #getWantClientAuth. These are only valid in the context of a server, so they were moved to the SslContextFactory.Server class. We can avoid the deprecation but keep the assertions in the test by using the SslContextFactory.Server type instead of the parent SslContextFactory type.
I did the same for the call-sites in main, and for the SslContextFactory.Client type. This is necessary for a future upgrade of Jetty which actually removes these methods, and expects the specialized forms to be passed-around instead. This should not have any functional changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Test failures appear unrelated, and the connect tests pass for me locally.


Handling ISO values

In response to our discussion around ISO values today, I'll point people to my draft 2.0 spec: https://github.com/GraphBLAS/binsparse-specification/pull/20. I think either option is easy for me to parse, but option 2 is a closer match to a level-by-level format spec, so I thought I'd ask what y'all think:
Two main options were discussed today:

Keep the iso value as part of the datatype (i.e. "iso[int8]"). V1.0 is unchanged. V2.0 needs a change so that the Element Level will absorb the functionality of the ISO Level.
Handle things in the formats (i.e. "iso[CSR]"). The 2.0 PR is unchanged, but V1.0 needs a change so that the predefined formats (like "CSR" or "COO") can also accept "iso[CSR]" or "iso[COO]", and "iso" is no longer part of the datatype.

In option 1, we would add text to the description of an ElementLevel to say that
If the values_type is `iso`, then the values array is instead to be interpreted as follows:

: values
:: Array of size `1` whose element holds the value of all explicit entries in the sparse tensor.

In option 2, as long as we're in the business of defining format aliases, we would also say that "CSR" is an alias for
{
  "format": {
    "level": "dense",
    "rank": "1",
    "subformat": {
      "level": "sparse",
      "rank": "1",
      "subformat": {
        "level": "element",
      }
    }
  },
}

and "iso[CSR]" is an alias for
{
  "format": {
    "level": "dense",
    "rank": "1",
    "subformat": {
      "level": "sparse",
      "rank": "1",
      "subformat": {
        "level": "iso",
      }
    }
  },
}

I really think either is fine here, so a simple poll:
❤ react for 1, 🚀 react for 2

A third option is to not have it encoded in the datatype (i.e., not "iso[int8]") or the format (i.e., not "iso[CSR]"), and instead have e.g. CSR as the format, int8 as the datatype, and introduce a new metadata key such as "is_iso": true.


Giphy not listed in urls

[There should be a listing for giphy.com under the URL section for Microsoft Teams. If the customer has this url blocked they will not be able to use them.]

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

ID: 66bd8666-3566-a901-b25b-eb6baba6264a
Version Independent ID: e9f6310f-2207-8c81-d31a-3d5a80beb26b
Content: Office 365 URLs and IP address ranges - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/urls-and-ip-address-ranges.md
Service: o365-administration
GitHub Login: @kelleyvice-msft
Microsoft Alias: kvice

@LauraWi Please help us in resolving this issue. Thanks

@Strick1969  Thank you for your feedback. I'm currently working with the author to update the giphy.com URL. I shall update you shortly.
Thanks
Sri

Thanks for reaching out. The Office 365 endpoints web service is only designed to include endpoints that are specific to Office 365 services and features. The services you mentioned are not part of Office 365 and are therefore outside the scope of endpoints we can include in the database. -Kelley


Lost all existing configuration / or crash

Nothing working / can't view yaml / can't edit any existing objects or add new.

This looks more like the connection to home assistant is not working.

This looks more like the connection to home assistant is not working.

No.
The rest of my instance is 100% working, automations runnings and default dashboards perfectly.

Fixed by using reverse proxy on Fusion HA URL, even when using on local network.


Tap setup

This lets you setup body parts by tapping them. It's an idea proposed by @ButterscotchV :3.
I was gonna do it before but kinda left it on the dust until now.
This is based on #647 and also depends on SlimeVR/SolarXR-Protocol#89

Ready for review


Support for TryAddAWSService

Description
Added TryAddAWSService extensions methods to ServiceCollectionExtensions that calls TryAdd(ServiceDescriptor descriptopr) extension method from Microsoft.Extensions.DependencyInjection.Extensions.
Motivation and Context
I couldn't mock out and test an IAmazonS3 client with .NET Core's DependencyInjection framework, because of the lack of TryAdd* methods. My mocked out S3 client would get overwritten when ConfigureServices in Startup.cs got invoked.
These changes make it possible to do so, by not overriding the mocks.
Note: TryAdd methods make sure that if a service is already in the serviceCollection it will not be overwritten in Startup.ConfigureServices()
Testing
I wrote a test that adds a mocked service and then invokes TryAddAWSService<IAmazonS3>(); and confirms that the mock is not overwritten when IAmazonS3 service is retrieved from dependency injection.
The test project didn't have any mocking library dependencies so I made a simple FakeS3 class that implements the IAmazonS3 interface.
I ran the tests on Windows 10 Visual Studio 2017 15.6.6
Changes do not affect any other areas of code.
Types of changes

[x] New feature (non-breaking change which adds functionality)

Checklist

[ ] My code follows the code style of this project (Unsure)
[x] My change requires a change to the documentation (requires additional feature documentation)
[ ] I have updated the documentation accordingly (the documentation is in a different repository, if I'm not mistaken, if this gets merged I will gladly update it)
[x] I have read the README document
[x] I have added tests to cover my changes
[x] All new and existing tests passed

License

[x] I confirm that this pull request can be released under the Apache 2 license

Great, I'll get this released as soon as I can.

Version 3.3.6 of AWSSDK.Extensions.NETCore.Setup was released with this pull request.


'django' jQuery namespace causing issues?

I'm getting:
Uncaught TypeError: Cannot read property 'fn' of undefined
on:
$.fn.autoSuggest = function(data, options) {.
as well as:
Uncaught TypeError: Object # has no method 'autoSuggest'
Seemingly the plugin isn't able to access the namespaced version of jQuery from the admin?

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
fieu, @driver005, @CarmeloMaitaO, @haroldo-ok, @peterzam, @jendaa, @nikitavoloboev, @DanielBodnar, @deorsi, @jmcph4, @supertoub, @logicminds, @ingikim, @julmot, @jzarca01, @bgruszka, @lisoleg, @andreasasprou, @leapit, @ltartari


Feature request: Remember line position

[x ] I have read through the manual page (man fzf)
[ x] I have the latest version of fzf
[ x] I have searched through the existing issues

Info

OS

[x ] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[x ] bash
[ ] zsh
[ ] fish

Problem / Steps to reproduce
Feature request:
Hello,
I'm MB. A very nice and polite guy.
I have this feature request: remembering line position.
Sometimes I use fzf to go through documents manually and pick out URL's for example.
But every time I re-open the document like this for example (see below) I have to start at the top of the document again.
cat txtfile | fzf
It would be useful if there was a flag and a line history file to enable this feature.
So for example if last time I used fzf on the txtfile I finished on line 33 fzf will automatically display line 33 as the first line instead of line 1 for that document.
Or something like that. Especially if it's a long document it gets almost impossible to go through it with fzf because every time I re-load I have to start from the beginning again. I can't use the search function because I want to scroll through the document vertically.

I think one way of accomplishing something like what I'm looking for is by letting fzf do things with lines in the background.
Current behavior:
When user selects line fzf closes and does something with the line
Desirable behavior with flag --background:
When user selects line fzf does something with the line in the background. User can continue working with fzf and it does not close down.

See https://github.com/junegunn/fzf#executing-external-programs


uninstall draftd on draft init

This enables users to upgrade the draft daemon on every new release.
closes #202

How come we're choosing to uninstall instead of upgrading the image? @bacongobbler

That might be a better way to handle this. I figured that because we're at a point where we are constantly making breaking changes to Draft we might want to do something a little more destructive until we have a better upgrade story... At least for now.
Perhaps we can move forward with this as a crutch, but keep #202 open until we decide that the upgrade path is fairly stable? For example I'm currently working on a hack to implement #168 which may change how draft init works or how the chart is laid out.

For what it's worth this was pulled out from #347 so it's completely fine if we don't put this in.

Alright that's cool. I'll lgtm and then we can throw the upgrade flag in or whatever we decided from #202 before 1.0


Crashes game

I tried playing the game with the mod but it crashed and this is the debug results.
"An unhandled win32 exception occurred in sonic.exe [4796].
Just-In-Time debugging this exception failed with the following error:
No installed debugger has Just-In-Time debugging enabled. In Visual
Studio, Just-In-Time debugging can be enabled from
Tools/Options/Debugging/Just-In-Time.
Check the decumentation index for 'Just-in-time debugging, errors' for more information."
How do I fix it?

Never mind it just doesn't work with the lantern mod.

And i got a run time error.

You need to disable the Lantern Engine mod and delete the "d3d8.dll" file in SADX folder.
That said, are you sure this mod is for you? Unless you're developing your own mods and want to make use of order-independent transparency, there isn't much point in installing it right now. It's not going to improve the game's visuals or performance (at least not at this point), and it isn't compatible with the Lantern Engine mod. It also isn't complete and there are a few bugs, performance issues, and some visual effects are missing.
If you're just looking to play the game, d3d8to9 + Lantern Engine is the way to go for now.


Song Crashes and Errors

Describe your bug here.
The song got Crash And Other one the game Crashes and closed the app.
Command Prompt/Terminal logs (if existing)
Don't use the command
Use virtual studio code to fix it
openfl/events/SampleDataEvent.hx (line 189)
openfl/media/Sound.hx (line 748)
flixel/sound/FlxSound.hx (line 623)
flixel/sound/FlxSound.hx (line 487)
states/PlayState.hx (line 1224)
states/PlayState.hx (line 1694)
flixel/FlxState.hx (line 203)
flixel/FlxGame.hx (line 752)
flixel/FlxGame.hx (line 682)
flixel/FlxGame.hx (line 556)
openfl/events/EventDispatcher.hx (line 444)
openfl/display/DisplayObject.hx (line 1400)
To be consistent with flash the listener function registered to SampleDataEvent has to provide between 2048 and 8192 samples.

Are you modding a build from source or with Lua?
Source
What is your build target?
Neko, HashLink, or other build system
Did you edit anything in this build? If so, mention or summarize your changes.
Fix this problem

tha's a problem for haxeflixel,it fixed in nf Engine,I need time to finish my Engine then fix psychEngine


Add lang attribute to <html> tag

Problem
For a11y and HTML validation purposes, the <html> tag should have a lang attribute. See Google Lighthouse's error about this:

Solution
Based on the site-wide language that the user is using (English, Spanish, etc.), set the lang attribute on the <html> tag. See details on the lang attribute.

This passes the Lighthouse test! Looks like this works.


Please add Somerville, MA!

Hey @ouleena ! There's an email currently proposed for Somerville in issue #618. Can you comment there with anything you'd like to add or edit?

Will do. Thanks!


Support word granularity git diffs

In dracula theme:

Switch to catppuccin theme:

What face is magit using to display that line diff? If you don't know just move your cursor over one of those highlighted changes in the dracula theme and press M-x describe-char, then it'll tell you the face it's using for that character.

What face is magit using to display that line diff?

diff-refine-added and diff-refine-removed

Weird, those faces aren't used in my magit. Do you have any special setup at all?
I was experimenting around with trying to support this in #158 (using diff-refine- faces) but I could only see a difference in diff-mode. If your magit uses those faces for some reason then #155 should work as a fix for you, but it would be awesome if you could try those changes out yourself and tell me if it made a difference. Currently I'm still experimenting with the colours on that PR, nothing's final yet.

Weird, those faces aren't used in my magit. Do you have any special setup at all?

I haven't set up magit myself, but I'm using Doom Emacs, so that might be the reason. 🤔

but it would be awesome if you could try those changes out yourself and let me know about it

I tried the changes in #158, and they worked for me. However, the foreground color can be adjusted to make the text stand out better.

Thank you!


fix Fix memory exceed  limit and query has been canceled, Allocator will block 100ms

Proposed changes
Issue Number: close #xxx
After memory exceeds limit, Allocator first checks whether the query is canceled
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


Remove rebase_fallback from mergify config

Description
Remove rebase_fallback from mergify config as rebase_fallback is now deprecated
Fixes # (issue)
Type of change
What is it?

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run npm run lint:js:fix to check that my code is properly formatted

Codecov Report
Patch and project coverage have no change.

Comparison is base (a6fab6b) 29.90% compared to head (610ffcb) 29.90%.

:exclamation: Current head 610ffcb differs from pull request most recent head d4c3f67. Consider uploading reports for the commit d4c3f67 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #645   +/-   ##
=======================================
  Coverage   29.90%   29.90%
=======================================
  Files         127      127
  Lines        2852     2852
  Branches      885      885
=======================================
  Hits          853      853
  Misses       1828     1828
  Partials      171      171

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


feat: add "report" and "report outline" icons

Adds icons for report and an outline variant of the report icon.

Thanks for the pull request, @xitij2000! I've created OSPR-6515 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@xitij2000 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

@adamstankiewicz Is this Blended work by any chance? If yes, please tag it in the title.


integration3: terminal on Snapdragon broken after shutdown

When the mainapp is stopped using Ctrl+C on the Snapdragon it leaves the linux shell scrambled.
A workaround for now is to type exit and enter a new shell.

Better workaround is to run:
stty sane

The following code seems to be the culprit:
            // change input mode so that we can manage shell
            struct termios term;
            tcgetattr(0, &term);
            term.c_lflag &= ~ICANON;
            term.c_lflag &= ~ECHO;
            tcsetattr(0, TCSANOW, &term);
            setbuf(stdin, NULL);

Removing it allows terminal to shut down correctly.

 The solution is to re-instate the previous shell state.

Pushed fix to integration3

Tested, works. Thanks @mcharleb.


snapshot invalidate_hard_deletes feature

Is your feature request related to a problem? Please describe.
invalidate_hard_deletes=True for snapshots not working with CH because of its default non-nullable column
Describe the solution you'd like
dbt general default__snapshot_staging_table macro can be modified in two places by changing {{ strategy.unique_key }} to toNullable({{ strategy.unique_key }}) - in snapshotted_data and deletes_source_data CTEs

I was able to workaround this by specifying query_settings={"join_use_nulls": 1} in the snapshot config.


Install packages as sources/submodules

Is your feature request related to a problem? Please describe.
I want to use a packages as submodules and in-project sources
Describe the solution you'd like
-- path is specified, sources are copied into the project directory
add_requires("sqlite3", { type = "source", path = "third_party" })
-- path is not specified, use the default packages directory
add_requires("sqlite3", { type = "source" })

So we can use amalgamation files or get the sources and edit them easily
-- use git add submodule
add_requires("libcustom", { type = "submodule", path="third_party" })

Describe alternatives you've considered
I don't know what syntax to suggest as i don't know very well lua and you api
Additional context
No response

see https://xmake.io/#/package/local_3rd_source_library

The c++ libraries are not like the go/rust libraries, and most of the time it is not possible to introduce a git url and have it compile completely. If you look at the cmake packages in xmake-repo, many of them require additional configuration and even many patches to get them to compile.
Therefore, it is essential to define packages, and introducing them directly via a git url is very unreliable.
If your cmake is simple, it will compile perfectly well. Then even if you define packages, it's only a few lines of configuration and not very complicated.
package("sqlite3")
    set_sourcedir(path.join(os.scriptdir(), "sqlite3"))
    on_install(function (package)
        import("package.tools.cmake").install(package)
    end)
package_end()

add_requires("sqlite3")

only 8 lines.
But if your cmake package is complex and requires all sorts of extra configuration to ensure that it compiles through. Then you have to define the package and it simply won't work the way you say.
package("pcre2")
    set_sourcedir(path.join(os.scriptdir(), "pcre2"))
    on_load(function (package)
        local bitwidth = package:config("bitwidth") or "8"
        if package:version():ge("10.39") and package:is_plat("windows") and not package:config("shared") then
            package:add("links", "pcre2-" .. bitwidth .. "-static")
        else
            package:add("links", "pcre2-" .. bitwidth)
        end
        package:add("defines", "PCRE2_CODE_UNIT_WIDTH=" .. bitwidth)
        if not package:config("shared") then
            package:add("defines", "PCRE2_STATIC")
        end
    end)

    on_install(function (package)
        if package:version():lt("10.21") then
            io.replace("CMakeLists.txt", [[SET(CMAKE_C_FLAGS -I${PROJECT_SOURCE_DIR}/src)]], [[SET(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -I${PROJECT_SOURCE_DIR}/src")]], {plain = true})
        end
        local configs = {"-DPCRE2_BUILD_TESTS=OFF", "-DPCRE2_BUILD_PCRE2GREP=OFF"}
        table.insert(configs, "-DBUILD_SHARED_LIBS=" .. (package:config("shared") and "ON" or "OFF"))
        table.insert(configs, "-DPCRE2_SUPPORT_JIT=" .. (package:config("jit") and "ON" or "OFF"))
        local bitwidth = package:config("bitwidth") or "8"
        if bitwidth ~= "8" then
            table.insert(configs, "-DPCRE2_BUILD_PCRE2_8=OFF")
            table.insert(configs, "-DPCRE2_BUILD_PCRE2_" .. bitwidth .. "=ON")
        end
        if package:debug() then
            table.insert(configs, "-DPCRE2_DEBUG=ON")
        end
        if package:is_plat("windows") then
            table.insert(configs, "-DPCRE2_STATIC_RUNTIME=" .. (package:config("vs_runtime"):startswith("MT") and "ON" or "OFF"))
        end
        import("package.tools.cmake").install(package, configs)
    end)

If you have a way to make xmake automatically know if it can build it successfully, and no additional configuration is needed, just set a git url. You can tell me.

I totally agree when those libraries are external libraries (i mean external to the user project and the user has no control on it), the current system is great. And i didn't mean to compile libraries external to the user project with another build system. I will be more specific;
There is somecases where the users wants/needs to modify the sources or use a submodule architecture.
In-Source
Some libraries are designed to be built directly using the sources providing amalgamation files (or multiples files). So to use them, we just copy the files to our project, add some defines and build.
With sqlite3 for example, the sources could be part of the current sqlite3 package and we could select between static/shared/source library type
Currently
-- goto sqlite website
-- copy the sources
    add_files("third_party/src/sqlite3.c")
    add_headerfiles("third_party/src/sqlite3.h")
-- we have 2 different ways to manage external code (xmake + local third_party)

Could be
add_requires("sqlite3-dev") // or w/e the syntax
-- 1 way to manage add_requires("nds")
-- we can modify the source code depending on if we use a local repo or not

I don't know if it would requires a lot of change to handle that so i would understand that's not a priority if you need to make a lot of modifications.
Submodules
For the submodules, i was not talking about handling libraries external to the current project or building with other build systems.
Some projects use this architecture in the same project so the user has control on all those libraries.
I was suggesting supporting submodules for xmake only, all libraries would use xmake to build. If the project user switch to xmake, he just has to add a xmake.lua to his submodules, the transition is really easy.
I think having one interface (add_requires) to handle all cases of external code could be very powerful. Compiled libraries are so easy to use with xmake, would be so cool to handle sources and submodules the same way, even if it's not a priority :)

If you just want to use xmake to maintain submodules, then there must also be an xmake.lua file inside the submodule project to maintain them, as different source files, they also have different compilation options.
Of course, in this case, there is really no need to define packages, but there is even less need to use add_requires.
Wouldn't it be simpler to simply use includes + add_deps to integrate them?
includes("submodules/*/xmake.lua")

target("test")
     add_deps("sqlite3", ...)

use includes("submodules/*/xmake.lua"), all subprojects in your submodule directory will be loaded automatically. If the submodule directories do not exist, they do not have any negative impact.


User Level Access of the cQube Reports

Purpose of the Feature
Implementing of the user level based accessing of the cQube reports
Description of the Feature

cQube reports should be capable enough to access the reports as per the user levels.
On page load every user can be able to see all the high level summery of the state.
The Blocks, Clusters and Schools buttons would be disabled for the all the users accept the state level users.
A button would be provided as "Access Your location'. When the user clicks on the button then the user may able to see their particular location and the lower levels of their locations.
The upper level select options will be disabled for the users. The user may get only the lower level location selection which are belongs to the user location.

The current Access levels we have in cQube are,
State level users,
District level users,
Block level users,
cluster level users,
school level users
For example, If the user belongs to a district then the user can be able to access only their district information as well as the lower levels of their districts.
If the user belongs to a Block level then the user may be able to see their block level information as well as the lower levels of their block.
Effected Code Areas
Python: Modify the API for the state to provide the User Level & User location along with the user credentials
Angular JS & Node JS: - has to get the input from the API as User Level & User location along with the user credentials
Provide the selection options according to the user levels

Implimentation from Angular and node js is done


Fix retrieving executionInMillis saved as Integer by Mongo driver

… MongoDB
Issue reference
Closes #566
Documentation PR reference
No documentation changes
Description and context
The mongo driver may have saved the exectutionMillis field as Integer instead of Long for legacy migrations. This changes allows the Mongock migration to run regardless if the field is saved as Long or Integer.
Benefits
MongoCk will run old migration scripts more reliably.
Possible Drawbacks
I don't see any drawbacks.
Checklist

[ ] Unit tests provided
[ ] Integration tests provided
[ ] Documentation updated in documentation project
[ ] Updated example in example projects

Hello @bfeigl ,
thanks for your collaboration. This is really helpful. We are running the pipeline and once is green, it's almost ready to merge. Could you add some tests covering this, please?

Hi @dieppa, I added a test case which I expect to cover the issue but I don't get the integration tests to run and it seems that they are not executed as well in the github action builds? The following snippet is from the log of the run earlier today...
--- maven-surefire-plugin:3.0.0-M4:test (integration-test) @ mongodb-springdata-v3-driver --- [INFO]  [INFO] ------------------------------------------------------- [INFO]  T E S T S [INFO] ------------------------------------------------------- [INFO] Running io.mongock.driver.mongodb.springdata.v3.repository.SpringData3LockRepositoryITest [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 s - in io.mongock.driver.mongodb.springdata.v3.repository.SpringData3LockRepositoryITest [INFO] Running io.mongock.driver.mongodb.springdata.v3.repository.SpringData3LockManagerITest [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in io.mongock.driver.mongodb.springdata.v3.repository.SpringData3LockManagerITest [INFO] Running io.mongock.driver.mongodb.springdata.v3.repository.SpringData3ChangeEntryRepositoryITest [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in io.mongock.driver.mongodb.springdata.v3.repository.SpringData3ChangeEntryRepositoryITest [INFO] Running io.mongock.driver.mongodb.springdata.v3.driver.SpringDataMongo3DriverITest [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in io.mongock.driver.mongodb.springdata.v3.driver.SpringDataMongo3DriverITest

Hello @bfeigl ,
this is something we are facing and fixing in a branch. The problem is due to mix Junit4 and Junit5. Don't worry about it, I will take a look and give you feedback!
Thanks

Hello @bfeigl ,
we have fixed the test execution in another branch that hasn't been merged yet. So what we are going to do it:

Merge your changes
Rebase the branch that fixes the tests with your changes
Run the tests and ensure everything is fine
Release develop with your changes

Thanks!

Hello @dieppa,
thank you for your reply.
I'm looking forward to the release!

Hello @bfeigl , this has been merged and release.
Thank you for your contribution


how to fix it

Please limit the GitHub to bugs only. If you need support you can join the discord (link on wiki page).


Update 3rd party libs wiki page with new webpack build

Versions
angular-cli: 1.0.0-beta.11-webpack
node: 5.3.0
os: win32 x64

3rd party libs content is outdated. It should describe the process of adding 3rd party libs using webpack instead of broccoli.

Help us @filipesilva 💃

I can give some insight if needed. If the third party module can be imported via npm install, AND the 3rd party lib is of one of the following JS Module format: (es6, commonjs, commonjs2, amd, typescript), then you can simply import the file into your app (as long as you have valid ambient or global typings for it).

However if you have a var, global style 3rd party module, you will not be able to include the library. (unless hacking a bit at it). This is going to be feature we add here in the near future.

@TheLarkInn I can confirm this, it is working. I used 'ng-bootstrap' as example form the Angular UI Team.
Now going to try the other libraries I want to use.
Waiting for the guide how to hack a bit hehe.

I've updated the README to reflect usage of third party libs on the webpack branch. It's way, way easier than before, but as @TheLarkInn mentioned the globals bit of it is still not working.
https://github.com/angular/angular-cli/pull/1633 addresses loading of global CSS as well.


Move Unit Tests & Linting to GitHub Actions

Cloud Build is opaque.  Contributors should be able to see their tests running / failing and all the details included.  GitHub Actions has better visibility.

Hey @dinagraves if you're open to outside contributions, this might be something I could help with :)

Ooh, that'd be great!

Also note #143 -- let's put any new CI config into a ci folder.

+1 that would be wonderful! Thank you!

@davidstanke is it important that the new folder is called ci? For GitHub Actions, the build files are usually placed in .github.

Ah, good point @rethab --- yes, do that! :)


How to train with large dataset

Hello,
I believe that this is a fairly simple question but since I'm very new to ML in general, it still baffles me. I just followed the training instruction and has successfully trained my model on one pair of data (a clean speech.wav and a noise.wav) now I want to ask how can you repeat this process for larger dataset, I'm currently having a set of data with 300 files for these 2 categories and I don't think repeating this process 300 times is the way I should go.
Thanks.

just concatenate the audio files.
But you need to be aware, that the input format is not .wav it's plain pcm without any header.

I want to know how to  concatenate the audio files. Did you use any useful tools？Or just copy the RAW files and paste them into one file? How can I get a long RAW data? I would be very grateful if you could help me

I wrote a python script to concatenate files. For reading audio files I used the soundfile package and resampled if needed using scipy.

I am not quite familiar with python as a greenhand. But I tried to connent RAW files just like to connent TXT files ,obviously it is wrong. It has the error like "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 26050: invalid start byte"
Here is my python code and I wonder how can I fix it...
-- coding:utf-8-
import sys
import importlib
importlib.reload(sys)
import os
import os.path
import time
time1=time.time()
def MergeTxt(filepath,outfile):
k = open(filepath+outfile, 'a+')
for parent, dirnames, filenames in os.walk(filepath):
for filepath in filenames:
txtPath = os.path.join(parent, filepath)
f = open(txtPath)
k.write(f.read()+"\n")
k.close()
print ("finished")

if name == 'main':
filepath="xxx"
outfile="result.raw"
MergeTxt(filepath,outfile)
time2 = time.time()
print (u'Time：' + str(time2 - time1) + 's')

After training, the "sound" part of my test was also severely weakened. Is this because I selected an inappropriate data set? How should I train to accurately recognize noise and human voice? Do I need to modify the loss function? Can you provide the raw duration of your training set and the settings of your parameters? I'm in 4H noise and 4H pure human voice files at 4000000 COUNT and 128 batch_size. With 120 epoch and my final val_loss is around 2. In this case, both sound and noise are suppressed to a large extent.Is there anything inappropriate between my data set and the parameters I selected？
I would be very appreciate for your help. Thx!!

Sorry, but I think your behavior in the GitHub issues is somewhat inappropriate.
You spammed the very same question three times across multiple issues:
https://github.com/xiph/rnnoise/issues/208
https://github.com/xiph/rnnoise/issues/201#issuecomment-1209169089
https://github.com/xiph/rnnoise/issues/196
You can answer your question yourself, by reading the rnnoise paper and newer speech enhancement papers.
They all report numbers on how much data they are using.


#47 - Apply since logic to new architecture solution

Add code to control usage of rls create or published dates as filtration condition.

Added manual date filtration as it is not provided by API for pulls and commits.

Update of unit tests.

Change number of issue in test fixtures to be able do assertions. Update of influences unit tests.

Closes #47

Release notes:

Add code to control usage of rls create or published dates as filtration condition.


feat: use opentelemetry library for tracing

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en.
close #2

It will be reviewed after #61

@melikhov-dev I updated the pull request, take a look


Removing deprecated @AfterInitialization annotation

With the release of v0.9.9 the @AfterInitialization annotation was deprecated (to be removed in v1.1.0). This was done in favor of using Java's @PostConstruct annotation.
Note: This annotation must remain in the v1.0.x branch!

removed from code base with ea5c21ca031a6ff994c71553e126afd03e389f22

When upgrading from older version:
Replace all occurrences of @AfterInitialization with @PostConstruct
(javax.annotation.PostConstruct)


Correctly fail tests using RSpec

We previously spotted that if we had invalid HTML on one of our pages, the build would fail (correctly) on Jenkins, but not on our local environments. This was fixed in a previous pull request, such that the build would (correctly) fail locally when running bundle exec rake. However, running a single test using bundle exec rspec <file> would (incorrectly) pass a test with invalid HTML.
This behaviour appears to be related to the RACK_ENV environment variable. We use Slimmer for skinning GOV.UK frontend apps to give them a consistent look. The build failures are because in a test environment, Slimmer will also parse our HTML and check that it's valid. However, to determine if we're in a test environment, Slimmer checks the RACK_ENV variable, which is presumably set correctly when running the application, or when running rake, but not when running "just" rspec.
This change updates the RACK_ENV environment variable to match the RAILS_ENV variable, which is also manually set in spec_helper.rb. Therefore, Slimmer will be run in "strict" mode, and fail when provided with invalid HTML.

 Investigate why Calculators tests pass locally but fail on CI


IMN-229 - dedupe puppeteer instance

The changes has been integrated directly in the PR #567. Closing the PR


Gitlab ci configuration

Hello, i try settings up ruff for Gitlab Ci code quality, i checked up lot of google result, but still can'T figure out how to make it work
my gitlab-ci.yml:
stages:
  - test

include:
  - template: Code-Quality.gitlab-ci.yml

Testing:
  stage: test

  rules:
    - if: "$CI_PIPELINE_SOURCE == 'merge_request_event'"
    - if: "$CI_COMMIT_TAG =~ /^v(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(-alpha\\d*|-debug\\d*|-beta\\d*|-rc\\d*|)$/"

  image: "python:3.10"

  before_script:
    - 'pip3 install pytest pytest-asyncio pytest-automock pytest-cov pytest-html-reporter ruff junit2html'

  script:
    - pytest -m GCI -rap --junitxml=gci_test_report.xml
    - ruff ./ --format gitlab > gl-code-quality-report.json

  artifacts:
    name: "${CI_PROJECT_NAME}_tests_reports"
    when: always
    reports:
      codequality: gl-code-quality-report.json
      junit: gci_test_report.xml
    expire_in: never

the result:

any tips or information on how i could make it work (also a section in the documentation for github/gitlab integration could be really nice)

I've never used Gitlab, but there might be some helpful comments in the original PR? See: #1424.
@saadmk11 may be able to answer a question about it too, if he's available.

Yeah i already tested that without success :(
Le mer. 1 févr. 2023, 16 h 09, Charlie Marsh @.***> a
écrit :

I've never used Gitlab, but there might be some helpful comments in the
original PR? See: #1424 https://github.com/charliermarsh/ruff/pull/1424.
@saadmk11 https://github.com/saadmk11 may be able to answer a question
about it too, if he's available.
—
Reply to this email directly, view it on GitHub
https://github.com/charliermarsh/ruff/issues/2454#issuecomment-1412725331,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSPAADEJR7ORFLIBAPRVT3WVLGHZANCNFSM6AAAAAAUOERPGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

When I implemented this, I used this config to test it on GitLab CI:
include:
  - template: Code-Quality.gitlab-ci.yml

code_quality:
  image: python:3.10-slim
  allow_failure: false
  script:
    - pip install ruff
    - ruff . --format gitlab > gl-code-quality-report.json
  artifacts:
    reports:
      codequality: gl-code-quality-report.json

Is it On pipeline or on autodevops?
Le mer. 1 févr. 2023, 16 h 14, Maksudul Haque @.***> a
écrit :

When I implemented this, I used this config to test it on GitLab CI:
include:

template: Code-Quality.gitlab-ci.yml

code_quality:
image: python:3.10-slim
allow_failure: false
script:
- pip install ruff
- ruff . --format gitlab > gl-code-quality-report.json
artifacts:
reports:
codequality: gl-code-quality-report.json
—
Reply to this email directly, view it on GitHub
https://github.com/charliermarsh/ruff/issues/2454#issuecomment-1412731806,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSPAACQLQLKTS3XIAQT4NLWVLG2JANCNFSM6AAAAAAUOERPGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

i copy/pasted the @saadmk11 code example,
i tested with and without the include
and i still have the same error message (gitlab 14)

there is the code i tested
include:
  - template: Code-Quality.gitlab-ci.yml

code_quality:
  image: andrejreznik/python-gdal:py3.10.0-gdal3.2.3
  allow_failure: false
  script:
    - pip install ruff
    - ruff . --format gitlab > gl-code-quality-report.json
  artifacts:
    reports:
      codequality: gl-code-quality-report.json

so i don'T know why, after few try and stop it's now working.

Glad it's working! Sorry I couldn't be more helpful!

no worry, my ci is simple but complex, it's only an include with override. so we create standard ci pipeline for all project

so, new branch, new merge request, same issue, so back to the beginning

You can checkout the troubleshooting section of GitLab Code Quality Docs: https://docs.gitlab.com/ee/ci/testing/code_quality.html#troubleshooting

Ok so look like it'S working now,
there is a small recap in case you would like to documente the step in the official documentation:
# could be any name if you don't use the template (the template is not required for the process to work)
code_quality:
  stage: test
 # not sure if you could use a different stage

  rules:
    - if: "$CI_PIPELINE_SOURCE == 'push'"
    # THIS TRIGGER IS REQUIRED IF YOU WANT THE PROCESS TO WORK

    - if: "$CI_PIPELINE_SOURCE == 'merge_request_event'"
    # I want it to run also when i create a merge_request(or update)

  image: "python:3.10"

  before_script:
    - 'pip3 install ruff'
    # don't forger to install ruff

  script:
    - ruff ./ --format gitlab > gl-code-quality-report.json
    # redirect output to a json file(could be any name)

  artifacts:
    name: "${CI_PROJECT_NAME}_code_quality"
    #artifact could have any name
    when: always
    # i want the artifact to be created even if test failed
    reports:
      # the artifact is a reports object
      codequality: gl-code-quality-report.json
      # artifact is a codequality artifact this must be your json name (any name)

    expire_in: never

Awesome, thanks for following up!

i still have a fix to do, the pipeline run on main after i merged, i want to prevent that to happend, i update my post in few min with the final answer


How to change tabbar height?

Hello i'm working with this tabbar but i don't know how to change the tabbar height, thanks

Currently, you can not change tab bar height. I am working on this. In my next update, you will be able to change. Thanks

Just to join the requested feature. Waiting for an update :)


crun: 0.19.1 -> 0.20

https://github.com/containers/crun/releases/tag/0.20

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 125313 at 2489d71b run on aarch64-linux 1

4 packages built successfully:

buildah
cri-o
crun
podman


Update website

This PR will bring to toltec-dev.org information introduced in https://github.com/toltec-dev/toltec/pull/453 and https://github.com/toltec-dev/toltec/pull/460
Thanks to @Eeems for bringing the web repo to my awareness.

All fair points. I will leave this PR in its current state then.

Added a link to GitHub discussions in the first FAQ item, to give an alternative to those who don’t want to use Discord.
Pushed updated build to: https://toltec-dev.org/gbyl-homepage/
If everyone agrees, I think we can merge this.

Excellent! I italicized the warning to make it stand out a little more. We can merge it now.


This is generally fine, since the status will just be updated 5 seconds later at the next periodic refresh. In an upcoming release, I'll be converting this to a debug message so it doesn't fill up the logs like this.


[BUG] Test location lists are not displayed

Describe the bug
The app is not displaying the list of test location on Test Locations screen when user choose All Providers
To Reproduce
Steps to reproduce the behavior:

Install the safer app
Proceed with Onboarding screens
Verify the user role as University Student and proceed to Safer Illinois Home screen
Tap on the Find test locations button

Actual Result
No test location is displayed for All Providers. Also, only "All providers" is available in the drop-down list.
Expected behavior
Test locations should display for the selected providers. Also, Mckinley providers should also be added to the drop-down list.
Screenshots

Smartphone (please complete the following information):

Device: [e.g. Android]
App Version [e.g. 2.9.17]

Unable to reproduce. The locations are loaded.

Please provide clear steps or close the ticket

This situation might happen if any of the requests for loading providers or location fails. Versions 2.9.22 and 2.10.13 are updated to display error message in such case, as well as some general cleanup in this was applied.

This issue is resolved


Design a simple, fast source finder based on Lucas' model convolution

I think it could be quite nice if XGA had its own simple source finder - an obvious choice would be to convolve with window functions at different scales to separate extended and point sources, then perhaps use a clustering algorithm to find clusters of brighter pixels which could be attributed to a source.

What would be fun, in combination with this, would be adding another type of Source class which would calculate intersections between observations, and any that overlap would be combined into a source. Then I could run this source finder on a combined set of data


Epic: Metaprogramming

Proposal: https://hackmd.io/Tkzo_ryvTsWMPESmWHPiZw?view
### Core Tasks for Noir 1.0
- [ ] https://github.com/noir-lang/noir/issues/4586
- [ ] https://github.com/noir-lang/noir/issues/4587
- [ ] https://github.com/noir-lang/noir/issues/4588
- [ ] https://github.com/noir-lang/noir/issues/4589
- [ ] https://github.com/noir-lang/noir/issues/4590
- [ ] https://github.com/noir-lang/noir/issues/4591
- [ ] https://github.com/noir-lang/noir/issues/4796
- [ ] https://github.com/noir-lang/noir/issues/4916
- [ ] https://github.com/noir-lang/noir/issues/4917
- [ ] https://github.com/noir-lang/noir/issues/4924
- [ ] https://github.com/noir-lang/noir/issues/4925
- [ ] https://github.com/noir-lang/noir/issues/4953
- [ ] https://github.com/noir-lang/noir/issues/4954
- [ ] https://github.com/noir-lang/noir/issues/5146
- [ ] https://github.com/noir-lang/noir/issues/5168
- [ ] https://github.com/noir-lang/noir/issues/5201
- [ ] https://github.com/noir-lang/noir/issues/5255

### Bugs for Noir 1.0
- [ ] https://github.com/noir-lang/noir/issues/4879
- [ ] https://github.com/noir-lang/noir/issues/4915
- [ ] https://github.com/noir-lang/noir/issues/4922
- [ ] https://github.com/noir-lang/noir/issues/5194

### Nice-to-haves for Noir 1.0+
- [ ] https://github.com/noir-lang/noir/issues/3379
- [ ] https://github.com/noir-lang/noir/issues/4592

Current goal is to get a vertical slice of metaprogramming working to support deriving a trait impl of a simple type on a simple trait like Default:
comptime fn derive_default(typ: TypeDefinition) -> Quoted {
    let generics: [Quoted] = typ.generics();
    assert(generics.is_empty(), "derive_default: Deriving Default on generic types is currently unimplemented");

    let type_name: Type = typ.as_type();
    let fields: [(Quoted, Type)] = typ.fields();

    let fields: Quoted = fields.map(|(name, _)| quote { $name : Default::default(), })
        .join();

    quote {
        impl Default for $type_name {
            fn default() -> Self {
                Self { $fields }
            }
        }
    }
}

#[derive_default]
struct Foo {
    x: Field
}

// Expected output:
//
// impl Default for Foo {
//     fn default(this: Self) -> Self {
//         Foo {
//             x: Default::default(),
//         }
//     }
// }

Required unimplemented features:

Query functions on TypeDefinition: generics, as_type, and fields
Quoted type for quoted, unparsed raw token streams. I think this is necessary to quote code fragments like quote { $name : Default::default(), } which is only valid in the context of struct initialization. I've chosen this name to avoid confusion with crypto tokens that Tokens or TokenStream may cause.

Additionally, to support this and make unquoting easier into arbitrary locations of quoted values, I'd like to move from an AST representation of quoted values to a token stream. This will ensure we can combine values like quote { $name : Default::default(), } where $name is spliced in despite us not knowing what grammar rule it should be part of (is it an identifier? an expression?).
Quoted token streams will be the new default type of quoted values with alternate types like quote Type { ... } or quote TopLevelItem { ... } only being used to force a quoted value into a particular shape so that specific methods can be called on it. TypeDefinition is the only type with methods on it above but we can imagine similar methods on a Type value which would be meaningless on unparsed Quoted values.
Notably, quoting the impl as a token stream avoids us needing to rework the parser to make our top level statement parser recursive since at parse time we'd only be parsing a token stream here.
The token stream ends when the matching } is found.
We avoid actually parsing Quoted values until they're expanded into a macro's call site: either a top level statement or an expression. When this happens, we parse the token stream and issue an error if we cannot parse into a top level statement or an expression.

Some helper functions like join to join a slice of quoted values into one:

fn join(slice: [Quoted]) -> Quoted {
    let mut ret = quote {};
    for element in slice {
        // Since quoted values are token streams, we do not need (or want) a `;` separator.
        ret = quote { $ret $element };
    }
    ret
}

Next goal is getting the full derive macro working from the Comptime Grimoire:
#[derive(Default, Eq, Cmp)]
struct MyStruct { my_field: u32 }

type DeriveFunction = fn(StructDefinition) -> Quoted

comptime mut global HANDLERS: HashMap<TraitConstraint, DeriveFunction> = HashMap::new();

comptime fn derive(s: StructDefinition, traits: [Quoted]) -> Quoted {
    let mut result = quote {};

    for trait_to_derive in traits {
        let handler = HANDLERS.get(trait_to_derive);
        assert(handler.is_some(), f"No derive function registered for `{trait_to_derive}`");

        let trait_impl = handler.unwrap()(s);
        result = quote { $result $trait_impl };
    }

    result
}

comptime fn derive_via(t: TraitDefinition, f: Quoted) {
    HANDLERS.insert(t.as_constraint(), unquote!(f));
}

#[derive_via(derive_do_nothing)]
trait DoNothing {
    fn do_nothing(self);
}

comptime fn derive_do_nothing(s: StructDefinition) -> Quoted {
    let typ = s.as_type();
    let generics = s.generics().join(quote {,});
    quote {
        impl<$generics> DoNothing for $typ {
            fn do_nothing(self) {
                // Traits can't tell us what to do
                println("something");
            }
        }
    }
}

Features we still need to do this:

Add extra arguments to annotations
Variable argument count for annotations
Apply annotations to a trait & TraitDefinition type
unquote method in stdlib. It can be simple: fn unquote(q: Quoted) -> Quoted { q } since applying the ! on a macro automatically unquotes anyway.
A usable compile-time HashMap type. The existing constrained one is slow (but maybe usable enough?).
TraitConstraint type
impl Hash for TraitConstraint
impl Eq for TraitConstraint
Quoted::as_trait_constraint

This issue is subject to feature creep particularly since there's no set amount to comptime functions or functionality we should support. As a result, after my above comment on features we need to complete a general derive macro is complete I'm going to consider this issue as a whole completed as well.
Any remaining issues we can keep as separate bugs / feature requests.

https://github.com/noir-lang/noir/pull/5667 has been merged so I'm closing this issue now.
With PR, all issues linked here except #5201 have been implemented.


Add getOrCreate for deltatable API

When creating a new job that requires a merge function from the second run forward, I need to use this kind of code:
if DeltaTable.isDeltaTable(spark, OUTPUT_PATH):
    deltaTable = DeltaTable.forPath(spark, OUTPUT_PATH)
    merge_join_condition = ' ... not important ...'
    (
        deltaTable.alias("old").merge(
            df.alias("new"),
            merge_join_condition)
        .whenMatchedUpdateAll()
        .whenNotMatchedInsertAll()
        .execute()
    )
else:
    df.write.format('delta').partitionBy('year', 'month', 'day').save(OUTPUT_PATH)

It would be nice if we could have something like:
deltaTable = DeltaTable.getOrCreate(spark, OUTPUT_PATH, 'year', 'month', 'day') # partition column
merge_join_condition = ' ... not important ...'
(
    deltaTable.alias("old").merge(
        df.alias("new"),
        merge_join_condition)
    .whenMatchedUpdateAll()
    .whenNotMatchedInsertAll()
    .execute() # Here write or create the table using the partition columns above.
)

What do you think?
Doron

@gdoron Yep, this would be useful. How about calling it createIfNotExists to be consistent with SQL CREATE TABLE IF NOT EXISTS statement?
We are working on a table creation Scala/Python API right now for Generated Columns feature. Definitely will add this to the table creation API.

This has been added to the Delta 1.0 release. Please checkout https://github.com/delta-io/delta/releases/tag/v1.0.0
Closing this issue. Please reopen if this does not satisfy the requirements.


⚠ Nextcloud has degraded performance

In ff9651d, Nextcloud ($SERVER_BASE/nextcloud/) experienced degraded performance:

HTTP code: 200
Response time: 5796 ms

Resolved: Nextcloud performance has improved in 108e878 after 10 minutes.


v2

v2
Bidirectionally reliant on https://github.com/JackalLabs/canine-chain/issues/365
Bidirectionally reliant on https://github.com/JackalLabs/jackal.js/issues/15
For the Jackal Protocol v4 upgrade, the logic surrounding uploading files has changed enormously. Thus making protos v1 for Jackal.js v1 & v2 incompatible with the chain. During the chain upgrade, all web-apps using Jackal.js must update to Jackal.js v3.x.x in order to continue using the Jackal Protocol, which will in turn require an update to protos v2.
### Success Criteria
- [x] Remove discontinued protos
- [x] Add new protos
- [x] Update protos modified to improve consistency

completed with publish of v2
https://github.com/JackalLabs/jackal.js-protos/releases/tag/v2.0.0


Incorrect resource provider commands

Under the pre-req's it states to register several resource providers at the subscription level with the following command:
Register-ResourceProviderIfRequired
I cant see that this command exists and should be register-azresourceprovider

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

ID: 00d02e07-0813-47ed-69d3-b4d777d07b53
Version Independent ID: 9a403bb0-bd87-78ea-f987-12b1fe354eb0
Content: Register your Azure Stack HCI servers with Azure Arc and assign permissions for deployment - Azure Stack HCI
Content Source: azure-stack/hci/deploy/deployment-arc-register-server-permissions.md
Service: azure-stack
Sub-service: azure-stack-hci
GitHub Login: @alkohli
Microsoft Alias: alkohli

@integyjc
Thanks for your feedback! We will investigate and update as appropriate.

Hi @integyjc
I couldn't locate any mention of the Register-ResourceProviderIfRequired command on this page. It seems the document has been updated to include the Register-AzResourceProvider command instead. Perhaps this is what you were referring to.

@integyjc These commands were updated. Closing this issue.
#please-close


When charging stations in site are public, throw error if site is made private

throw an AppError when charging stations are public but the site is being converted to private before charging stations are made private.

Do I need to log the Error?

Do I need to log the Error?
Normally, when you throw the exception, it should be already logged.

Like the other issue, create an issue + link your PR to it + paste the link in Asana.

@LucasBrazi06 While throwing the AppError, why do we not see the message in the notification that pops up? It seems like a longer process if the user has to go to the logs and read the message.

@LucasBrazi06 While throwing the AppError, why do we not see the message in the notification that pops up? It seems like a longer process if the user has to go to the logs and read the message.

You have to catch the exception in the front-end and display an i18n message ;-) so I would expect a PR in the dashboard also.

@RohanAntony  Still not attached to an issue, just did it.


[bctls-fips-<IP_ADDRESS>.jar] We are having an issue to validate the certificate chain with FIPS-140

We are using JDK1.8.0_92, Tomcat 7.0.69, X509 Certificate w BCFKS keystore.

How do I disable validation? how do I disable the certificate chain validation?

I got the errors below
Caused by: java.security.cert.CertificateException: Unable to construct a valid chain
at org.bouncycastle.jsse.provider.ProvX509TrustManager.validateChain(Unknown Source)
at org.bouncycastle.jsse.provider.ProvX509TrustManager.checkTrusted(Unknown Source)
at org.bouncycastle.jsse.provider.ProvX509TrustManager.checkServerTrusted(Unknown Source)
... 82 more
Caused by: java.security.cert.CertPathBuilderException: Unable to find certificate chain.
at org.bouncycastle.jcajce.provider.PKIXCertPathBuilderSpi.engineBuild(Unknown Source)
at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280)
at org.bouncycastle.jsse.provider.ProvX509TrustManager.buildCertPath(Unknown Source)
... 85 more

How do I debug validation process?

How do I disable validation? how do I disable the certificate chain validation?

That seems like a bad idea. I gather from email elsewhere that you are using self-signed certs - have you added them to the trust store (passed to TrustManagerFactory.init)? ProvX509TrustManager will skip CertPathBuilder when a trusted cert is being used directly: https://github.com/bcgit/bc-java/blob/bc3b92f1f0e78b82e2584c5fb4b226a13e7f8b3b/tls/src/main/java/org/bouncycastle/jsse/provider/ProvX509TrustManager.java#L201

Closing as inactive. Assumed resolved.


Fix: Desktop Activity Page - Fix "Click on a bar" Break Point

Issue
https://github.com/covidcanidoit/covidcanidoit/issues/275
Before

Result

┆Issue is synchronized with this Trello card by Unito

Hi @OozyGrub, did you forget to commit some changes? We pulled down the PR and didn't notice any changes.

@botanical I added a single option to the element and the result was shown in the figures. Can you check again?

this is what I'm seeing...

I'm working on it. I fixed the wrong thing. If you refresh the page, all categories are appeared. I'll take a look at it.


add [homebrew] cask service

I went for the '/' route to distinguish regular and cask formulas, much like many other services
both regular and cask services are similar in implementation, but different schemas and api routes make it quite hard to find any common code to refactor, so I decided to leave it as it
this closes #1638

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @pnowaczyk!

  Generated by :no_entry_sign: dangerJS against bff6980b6b695379417ddd2f58cba46dcc88122f

That's odd, I've never seen the Docker Cloud tests fail before. I've kicked off a re-try

Huh, odd. For the record it doesn’t actually run any tests, just builds an image.


Do not log all JSON-RPC parameters

Call parameters are logged now like this:
..."params":{"any_tags":[],"channel_ids":["deed21cf85c453e074b95949098fcd0c3dc65d69","9ab8d447066d328d8ebd115f725e701bd6fce93a","82f1d8c257d3e76b711a5cecd1e49bd3fa6a9de9","0871b29c7db6f1ec013694c8146f772539fcffa3","537305bc1bd71e2a5d76efacd607fd0f4d95da0c","c07ce3862335cfe9ba72054347c4ea7808ce4eaa","0e1aff187fbd3d2b2b16e5e8c213d3e782dafa98","a1303dc6a592605b08d60cac19ecbc1c877d7de7","2a294ea41312c6da8de5ebd0f18dbfb2963bb1a4","d6350f9158825662b99e4b5e0442bcc94d39bc11","3e7bb536a1b755b6eb64043ae3fa933d5935eaad","0518c93a80efeaf06fb4ac4d3fa72cc6390ac100","b8a2d928a3d3f44457a10abd0539b84e4a29c286","564789ffe2420980dcf9e00c4746feb5bc0daad0","7364ba2ac9090e468855ce9074bb50c306196f4c","e33372c0d8b2cdd3e12252962ee1671d66143075","3e63119a8503a6f666b0a736c8fdeb9e79d11eb4","1ce5ac7bab7f2e82af02305ced3c095e320b52e5","588ff6ffc72884e61e8d19a9412d6db9ec67167e", ...
This is excessive and clogs up the logs. Would be good to limit the number of parameters logged to some reasonable number to avoid that.

I have created a pull request addressing this issue (#381), if something is not ideal please say it and I can work on it.

This should be closed because #381 has been merged.

Thank you for the poke!


FYI - 1.0 breaks compatibility with 0.5

Hi there,
I resolved this for myself by downgrading back to 0.5 but just figured I'd leave a little note here for anyone who follows.
I have a project in production using HashIDs -- it's how we resolve URLs. Thousands of URLs. Today I upgraded to Rails 5 and in the process upgraded from 0.4.1 to 1.0.0. The config key names changed, I updated them (couldn't find anything in the docs for that but it was pretty simple to figure out).
But even though I kept the values the same (only updated names), old HashIDs just stopped resolving. The secret is the same ,min length is the same, etc -- but find_by_hashid with a valid old hash ID just wouldn't work.
As mentioned, the fix was to drop back to 0.5.0 (so 0.4.1 -> 0.5.0 is fine).

Currently in the process of upgrading here too, and noticed that the previous config.secret seems to have been replaced by config.salt but nothing indicates if they act the same or if it's just impossible to maintain the previous ids...

I used the new options, no errors were indicated, everything just broke :)

From my investigation, I believe the latest version uses a new special prefix for all generated hashids (i.e. it encodes [42, your_id] vs just encoding your_id) so as to avoid accidental decoding of numeric hashids.
See https://github.com/jcypret/hashid-rails/issues/30 for my proposed solution.

@ezuk Just merged in a PR (https://github.com/jcypret/hashid-rails/pull/37) from @olliebennett that addresses this. There is a new config option to disable hashid signing for backwards compatibility. I've also added some additional notes to the README explaining the upgrade process.


Delegated authentication: fix again the DistributedJ2ESessionStore

This is a new implementation of the DistributedJ2ESessionStore based on a cookie to solve previous issues.

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

@mmoayyed I just synced the PR with the master branch. I tested it again and it works. Would you mind testing a login/logout/login (login = authentication delegation to Okta) so we could merge this fix in v6.1.3 and v6.2.0? Thanks

Will do, sure.

Tested. No issues.


Feature Request: install without installing ghoscript

@NickNaso Is there a way to include ghotscript lib with this package ?
Goal: use serverless functions easily with this lib 9hard to install apt-get packages on serverless node environnements)

Thanks for the suggestion I hope to have this in the next release.


Evaluate and determine feasibility of Linux Distro partner VMR branches and Microsoft VMR branches being identical

One of the foundational rules of Unified Build is that our distro partners should be building the same commits as Microsoft builds. See https://github.com/dotnet/arcade/blob/main/Documentation/UnifiedBuild/Foundational-Concepts.md#public-open-source-net-releases-must-be-buildable-by-net-distro-maintainers-from-a-single-commit-in-the-upstream-repository. This does not mean that Microsoft builds the exact same product as distro partners. Build behavior may be different (restoring different packages, inclusion of non-OSS components in the Windows Build, etc.). It simply means that the ideal is that the commits we build will be the same as what our distro partners can build. There should be no permanent delta between the public upstream branches and what Microsoft builds.
It is time to test this in practice. Our distro partners have more restrictive rules about what may appear in the VMR with respect to binaries and source code licenses. As a result, we currently cloak files that do not abide by their rules but are not required to build the source-built Linux .NET products. Some of these cloaked files will be required to release the Microsoft-built product. My general sense is that most cloaking is generally a "bad" code smell w.r.t. to licensing and checked in binaries, and most should be able to be removed.
We need to evaluate all the currently cloaked items and determine the following:

Is the cloaked item required for Microsoft's build?
If it is not, then the cloaking entry can stay, but should the file be in the source repo at all? What purpose does it serve?
If the item is required for Microsoft's build, then what will it take to get rid of the cloaking? Example resolutions might include:

Re-evaluation of a license file (is the license problematic? Is it an installation artifact, or talking about actual source code)
Moving non-OSS compatible licensed code to another repo (should the code have been in the repo in the first place?)
Removal of binaries via restoring them from a package. Test assets commonly in this category.

T-shirt size: L. There is quite a bit of unknown here. This may be largely mechanical, an easy change. or it may uncover some serious issues.

T-shirt size: L or XL

Thanks @omajid.
Wanted to summarize the discussion we had on this today and the proposed solution:

As Microsoft seeks to build its product from the VMR, We do not believe it's really feasible in the near/mid term to remove all the binaries, non-compliant licenses for tests, etc. from existing repos that contribute to the VMR.
Many of the components which are problematic aren't even interesting from the standpoint of a Linux distro maintainer (winforms.,wpf, windowsdesktop).
As an alternative approach:

We will change the VMR sync such that it will sync into a branch without cloaking. Let's call this the VMR-All branch
We will provide a distro-maintainer-centric branch which will comply with your requirements like the existing branch does.
This branch will be a subset of the VMR-All branch, related in git history. Let's call this a VMR-SourceOnly branch. It will have the cloaked set of files removed.
These cloaked files may also include repos that are not interesting for distro maintainers, e.g. winforms
PRs that update a VMR-All branch will also test updates to the corresponding VMR-SourceOnly branch.
Upon checkin, the VMR-SourceOnly branch will be immediately updated (no lag) via a merge process.
On release day, we will create at least two tags and two releases. One tag will point to the VMR-All content for the release, and the other to the source only compatible content.
We may helpfully restrict source only builds to source-only branches, and vice versa to improve UX.
The naming of these releases and tags is TBD, suggestions would be welcome.
At some point in the future we may seek to unify the sources, but for now, no.

/cc @dotnet/distro-maintainers.
Unless there are further objections to this plan, I'll open issues for the work.

Thanks @omajid for the clarification. I assume that a pre-build process that removes the unwanted binaries and licenses from the source tree wouldn't be an acceptable solution here? Thinking about sourcelink, etc.

I believe that unifying sources is fine, as long as we also have a list of non-compliant files contained in the source tree. That way, we can script the removal of these files before packing the source into a source package for upload.
On our side (Canonical), the process of downloading and packaging the source from the VMR is already scripted, so adding this extra step in between would be a no-brainer.
@ViktorHofer is that what you meant?

I assume that a pre-build process that removes the unwanted binaries and licenses from the source tree wouldn't be an acceptable solution here?

I don't think this is the bar we want.  We want to treat source-building as something that has first class support rather than something that requires a number of hoops to jump through.

Yes some can but others can't

What are the distros that can't and that have a strict requirement on licenses of all source files in the repo?

We've heard from a set of distro maintainers that the want to take a sha or tarball and be able to feed it directly into their build systems without having to do any preprocessing.

Yes, this is the goal for me, if possible. That minimizes the chances of an attack on a developer (eg, me) or their machine compromising .NET itself.

I assume that a pre-build process that removes the unwanted binaries and licenses from the source tree wouldn't be an acceptable solution here?

Removing disallowed licenses duruing a pre-build step is workable for us. We would be sharing/uploading the source-code archive publicly, and that may already conflict with the license and its terms.
However, if all the licenses are permissible, we can delete (open source licensed) binaries in a pre-build step without any issues.

What are the distros that can't and that have a strict requirement on licenses of all source files in the repo?

Debian, Fedora and RHEL, to name a few.

Right, I have seen number of these pre-processing scripts. For example, https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/blob/snapshot/debian/orig-tar.sh looks like a preprocessing script for LLVM project for Debian.
I understand that no preprocessing is easier for distro maintainers, but I do not think there are hard rules about it from what I have seen.

It sounds to me like maintaining a subset branch is a more complete solution, at a similar cost. We need to maintain an exclusion list in either solution, it's just a matter of where and when it is applied. Having the subset branch also allows for last minute fixes to be checked into that branch without changing the original. This is valuable if source-only build specific issues are discovered after we have locked down and completed the Microsoft build of .NET. Uncommon, and it shouldn't happen, but it does happen.
If we don't have that branch, we need to maintain a patching mechanism

If we don't have that branch, we need to maintain a patching mechanism

That's only true when we treat branches as the HEAD of what to build instead of SHAs. It sounds like we want to pin/tag a SHA and then hand that off to distro partners. I wonder why we couldn't just add commits to the release branch? Shouldn't the Microsoft build also be driven based off a SHA and not a branch?

We need to maintain an exclusion list in either solution, it's just a matter of where and when it is applied

The downside that I see with that is that we effectively split our product in two which requires separate tags, GH releases and impacts the developer workflow (i.e. can I build the SB product from the non SB branch?). Those are just concerns that I want to raise before we start going down one path vs the other.

That's only true when we treat branches as the HEAD of what to build instead of SHAs. It sounds like we want to pin/tag a SHA and then hand that off to distro partners. I wonder why we couldn't just add commits to the release branch? Shouldn't the Microsoft build also be driven based off a SHA and not a branch?

That's fair. It wouldn't be prohibitive of additional changes to not have two branches.

The downside that I see with that is that we effectively split our product in two which requires separate tags, GH releases and impacts the developer workflow (i.e. can I build the SB product from the non SB branch?). Those are just concerns that I want to raise before we start going down one path vs the other.

Also fair. There are definitely dev UX issues to work out on both sides. Building SB from the main branch should work, though not vice-versa. If it doesn't work, then what we're also saying is that if you have a single branch, then you should be deleting files from the dev's machine prior to build when building SB. That has generally poor UX. In addition, the prep script has a greater burden on distro maintainers.

Epic: https://github.com/dotnet/source-build/issues/3989

I'm closing this work now in favor of the new epic.


⚠ Bofrost.de has degraded performance

In 6cc1975, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1201 ms

Resolved: Bofrost.de performance has improved in 2f0b945 after 19 minutes.


When will the code be updated?

Hi!
I am very interested in your work after reading your paper, and I would like to ask when you will update the code and demo of the paper. I would like to try to reproduce your results.
Thanks in advance!

Hi!
Thank you so much for your interest in our work!
Demo - We have our demo ready, we will be updating it on our webpage by this week.
Code - We are currently in the process of cleaning the codebase, we will update the repo soon. Please also note that we are currently occupied in other projects, so it could take a few weeks until we update this repo.

Hey, any update on when the code will be released?

Good question.


Adds GET Support, Switch to Official Python Docker Image, and other goodness

Closes #3.
This PR was originally intended to just add GET support to the API, but then turned into a bit more:

Adds method param for specifying whether to use usaddress's parse or tag function
Adds validate param to check if address string is either incomplete or contains invalid address parts, like P.O. Box
Adds time and host attributes to /status resource
Fixes error handling bug
Adds InvalidApiUsage exception and error handling
Adds PyDoc strings to all functions

In addition, I've switched the Dockerfile around to use the Official Python Docker Image.  This makes the Docker setup super clean, and automatically installs all Python dependencies for you so long as you put a requirements.txt in the root of your project.

Just realized I haven't updated the README to reflect these changes.  Let me get those in before anyone merges this.

Done tweaking with the README for now.  Feel free to review, merge, etc.


🐛  improve docs about chart workflow

Documentation improvements
Add exception if regions dataset is not baked (needed for harmonization step)

Thanks for reminder @lucasrodes !


[Portainer] Backup not getting restored, probably user error

Portainer

name: Documentation request
about: Documentation on how to properly restore a backup!
title: ''
labels: ''
assignees: ''

Which addon?
Portainer
Addon or app?
Addon
Describe the solution you'd like
Documentation on how to restore a backup!
Describe alternatives you've considered
I've tried clearing the password in the config, no luck.
Additional context
I've put my backup in /share as per instructions, but when starting the portainer instance (might've been my second time starting it, so even after uninstalling and reinstalling, it still wouldn't mount it), it doesn't mount it as an option on startup, I tried clearing the password field, it repopulates as "homeassistant" every time though.

s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-aaa_dockerfile_backup.sh
cont-init: info: /etc/cont-init.d/00-aaa_dockerfile_backup.sh exited 0
cont-init: info: running /etc/cont-init.d/00-aaa_portainer_install.sh
cont-init: info: /etc/cont-init.d/00-aaa_portainer_install.sh exited 0
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
 Add-on: Portainer
 Manage your Docker environment with ease
-----------------------------------------------------------
 Add-on version: 2.16.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.3  (amd64 / generic-x86-64)
 Home Assistant Core: 2022.11.1
 Home Assistant Supervisor: 2022.11.dev0303
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums
 https://github.com/alexbelgium/hassio-addons
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/30-nginx.sh
cont-init: info: /etc/cont-init.d/30-nginx.sh exited 0
cont-init: info: running /etc/cont-init.d/portainer.sh
cont-init: info: /etc/cont-init.d/portainer.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun portainer (no readiness notification)
s6-rc: info: service legacy-services successfully started
[13:52:49] INFO: Starting Portainer...
[09:52:49] INFO: Waiting for port 9000 to open...
[13:52:49] INFO: ... password set to homeassistant
[13:52:49] INFO: ... non-addon containers hidden
[13:52:49] INFO: ... portainer launched
2022/11/04 01:52PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:530 > encryption key file not present | filename=portainer
2022/11/04 01:52PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:549 > proceeding without encryption key |
2022/11/04 01:52PM INF github.com/portainer/portainer/api/database/boltdb/db.go:124 > loading PortainerDB | filename=portainer.db
2022/11/04 01:52PM INF github.com/portainer/portainer/api/internal/ssl/ssl.go:80 > no cert files found, generating self signed SSL certificates |
2022/11/04 01:52PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:686 > created admin user with the given password. |
2022/11/04 13:52:50 server: Reverse tunnelling enabled
2022/11/04 13:52:50 server: Fingerprint c1:7b:ed:ea:d2:e5:90:b8:12:9a:84:76:ce:43:b8:03
2022/11/04 13:52:50 server: Listening on <IP_ADDRESS>:8000...
2022/11/04 01:52PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:789 > starting Portainer | build_number=24674 go_version=1.18.3 image_tag=linux-amd64-2.16.0 nodejs_version=14.20.1 version=2.16.0 webpack_version=5.68.0 yarn_version=1.22.19
2022/11/04 01:52PM INF github.com/portainer/portainer/api/http/server.go:337 > starting HTTPS server | bind_address=:9443
2022/11/04 01:52PM INF github.com/portainer/portainer/api/http/server.go:322 > starting HTTP server | bind_address=<IP_ADDRESS>:9000
[09:52:50] INFO: Starting NGinx...```

Hi, open the addon options in yaml and put "". I just tested and it works. Each password change resets the database for info

Thank you!


[DO NOT MERGE] Add normalizer to latest preview API

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

This PR exposes normalizers to the 2020-06-30-Preview API version. The docs links still need to be updated after they are written and published.
Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[x] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.

early 2021 (@ishansrivastava90  and @Yahnoosh to confirm)

When you expect to publish swagger? Please provide date, or month to public if date is not available yet.

early 2021 (@ishansrivastava90  and @Yahnoosh to confirm)

If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[x] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[x] SDK of Java
[x] SDK of Js
[x] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

(@ishansrivastava90  and @Yahnoosh to confirm)
Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

handing off to @ishansrivastava90 (was not able to get autoRest command to work)
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Let's hold off on merging this until the API changes are actually deployed.

Sounds good

On Dec 4, 2020, at 4:59 PM, Bruce Johnston<EMAIL_ADDRESS>wrote:
Let's hold off on merging this until the API changes are actually deployed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Azure/azure-rest-api-specs/pull/11954#issuecomment-739096011, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHXR3JQGWN27L5PETC7TZPTSTGAVRANCNFSM4UNYO7BQ.

Closing this since we're not ready to merge it yet (the feature hasn't been deployed). We'll re-open the PR once the changes are ready.

@brjohnstmsft Can you re-open this PR since the changes are checked in and scheduled for next deployment? It seems that I don't have reopening rights. T

@brjohnstmsft Can you re-open this PR since the changes are checked in and scheduled for next deployment? It seems that I don't have reopening rights. T

I don't see a re-open button on my end either. I might have to push an update (probably a rebase) to get the re-open button to show up.

I don't see a re-open button on my end either. I might have to push an update (probably a rebase) to get the re-open button to show up.

@ishansrivastava90 @robertklee I don't seem to have re-open rights either, but there's no rush -- This shouldn't be merged until the changes are deployed worldwide.

@ishansrivastava90 @robertklee I don't seem to have re-open rights either, but there's no rush -- This shouldn't be merged until the changes are deployed worldwide.

@ishansrivastava90  @brjohnstmsft If you need me, feel free to ping me once you are ready by commenting here. I can open a new PR if re-open isn't working at that point. Exciting that it's going to deployment soon! :)

@ishansrivastava90  @brjohnstmsft If you need me, feel free to ping me once you are ready by commenting here. I can open a new PR if re-open isn't working at that point. Exciting that it's going to deployment soon! :)


Training Loss Anomaly Issue

Hello, based on your open source v1.1.0 code, I re-trained the first stage with about 3.5m data, and then trained the second stage with your 400w data, which however still maintains the resolution of 65x512x512 in this stage. However, during the training process there was a loss anomaly and the visualisation crashed, I would like to ask if this happened during your training, and where is the reason for this?

Training is unstable, you can add bs or reduce lr. When there is a sudden increase loss, interrupt training and resume from the nearest checkpoint that is normal.


[staging-next] libpsl: 0.21.0 -> 0.21.1

Motivation for this change
Cause of many failures due to some tests. the latest version seems to build fine.
https://github.com/NixOS/nixpkgs/pull/146259
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Dupe of #146255

@trofi beat me to the punch
https://github.com/NixOS/nixpkgs/pull/146255


Footnote extension: BACKLINK_TEXT does not work

The BACKLINK_TEXT setting of the footnotes extension does not work.
The following code has no effect on the backlink symbol, while the other settings on the other extensions do work:
extension_configs = {
        'markdown.extensions.toc': {
            'permalink': "#"
        },
        'markdown.extensions.codehilite': {
            'guess_lang': False
        },
        'markdown.extensions.footnotes': {
            'BACKLINK_TEXT': "X"
        }
}

I'm not able to replicate the problem in the current version:
>>> import markdown
>>> markdown.version
'2.6.8'
>>> text = '''paragraph[^1]
...
... [^1]: A Footnote'''
>>> markdown.markdown(text, extensions=['markdown.extensions.footnotes'], extension_configs={'markdown.extensions.footnotes': {'BACKLINK_TEXT': 'back'}})
u'
paragraph1
\n
\n
\n
\n
\n
A Footnote back
\n
\n
\n
'

But, I did notice we don't have a test for this, so I just pushed one: cd752c0.

Interesting, in isolation (using the exact code from your answer) it works, just not, when used together with the other extensions. Is it known to be incompatible with any extensions? I use the following:
extensions = ['markdown.extensions.toc',
                       'markdown.extensions.codehilite',
                       'pymdownx.extra',
                       'pymdownx.github'
                      ]

Where pymdownx.extra contains/loads markdown.extensions.footnotes.

Ah, I would suggest reporting this as a bug to pymdownx. If you are not calling the footnote extension directly, then pymdownx would need to pass the config on. I haven't looked looked at that code, so I'm not sure how it's being done.

FYI, markdown.extensions.extra doesn't recognize {'markdown.extensions.footnotes': {'BACKLINK_TEXT': 'back'}} either (at least from my tests).  Is this something that is expected?
As a side note, I would advice not using both pymdownx.extra and pymdownx.github as including both may include some extensions twice causing unexpected behavior: http://facelessuser.github.io/pymdown-extensions/usage_notes/.  Pick one wrapper extension, and manually configure the missing extensions.

This was my run:
>>> markdown.markdown(text, extensions=['markdown.extensions.extra'], extension_configs='markdown.extensions.footnotes': {'BACKLINK_TEXT': 'back'}})
u'
paragraph1
\n
\n
\n
\n
\n
Footnote ↩
\n
\n
\n
'

Interesting. I just noticed that we don't document anything regarding using config settings with markdown.extensions.extra. I looked at the code and it was not immediately obvious so I guessed and this works.
>>> markdown.markdown(text, extensions=['markdown.extensions.extra'], extension_configs={'markdown.extensions.extra': {'markdown.extensions.footnotes': {'BACKLINK_TEXT': 'back'}}})
u'
paragraph1
\n
\n
\n
\n
\n
A Footnote back
\n
\n
\n
'

While it makes sense (sort of), it is certainly less than ideal (that's a lot of nested dicts). However, I don't think I'll be changing it as I'm inclined to not have an "extra" extension in the future (3.0). Just let each stand on their own.

I'm inclined to not have an "extra" extension in the future (3.0). Just let each stand on their own.

I've been considering this myself.
Thanks for outlining how nested settings work, I had no idea that it was possible.

Thanks for outlining how nested settings work, I had no idea that it was possible.

It has to work that way now as an extension only gets settings for itself. Therefore extra never sees settings for "footnotes". However, extra makes custom calls to the extension loading methods so any settings not passed to extra are not available when footnotes is loaded. The only way to pass to extra and tell extra which extension they belong to is to nest them. Well, I suppose you could make extra aware of each supported extensions' configs, but ugh.

Well, I suppose you could make extra aware of each supported extensions' configs, but ugh.

Nah, what you're doing makes the most sense.  I wrongfully assumed that extra was prepackaged and didn't accept settings.
I do plan on dropping "wrapper" extensions in the future, but until i start the deprecation, I'll mimic what you do in extra in regards to settings.


AngelicSearch

A good start. Could you add documentation corresponding to the pseudo-code and JUnit tests exercising the implementation. Thanks.

This looks nice. It would be great to see it finished up.

Closing due to lack of further progress.


Detect SIReadLock locks in the pg_locks metric

Coverage remained the same at 64.7% when pulling a3a4c668739223e9f388b6a7cf030eb8e63e2255 on ocharles:patch-1 into e2df41f43effdfbb4544b3efb70350380ad895fe on wrouesnel:master.

Can I do anything to help get this merged?