Make a glossary page in the wiki

@frle10 Here is the glossary page link: https://github.com/vs-labs/distributed-task-scheduler/wiki/Glossary
Are there any terms other than scheduler and worker that I should add right now?

Looks good


HDDS-5973. Changed sequence of steps during pipeline close.

What changes were proposed in this pull request?
Change the sequence of steps during pipeline close to,

Close containers
Close pipelines

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5973
How was this patch tested?
This patch was tested using Unit test and CI tests.
https://github.com/aswinshakil/ozone/actions/runs/1470167230

And also once we have this, do we still need HDDS-5843??

I don't think we need HDDS-5843 after this fix, Unless if there is any other way we can be in a situation where the pipeline is open and the container is closed. Your thoughts on that @bharatviswa504?

@aswinshakil , can you please look at the test failures. The failures are related to recon server and it they look related to this patch

Thank You everyone for the reviews and @aswinshakil for the contribution


feat: export custom React hook for activity view state calculation

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.38%. Comparing base (accd550) to head (8cfda51).
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #171      +/-   ##
==========================================
+ Coverage   96.09%   96.38%   +0.28%
==========================================
  Files          13       14       +1
  Lines         282      304      +22
  Branches       29       29
==========================================
+ Hits          271      293      +22
  Misses         11       11

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


[airbyte_connection] [bug] MongoDB streams order change produces Terraform error

After schema updating, the order of MongoDB stream representation in Terraform state changes, and it can not be rewritten due to the already defined primary key, even if it's not defined in the source code.
For example,
HCL
resource "airbyte_connection" "mongodb_bigquery" {
...
  configurations = {
    streams = [
      {
        name      = test_collection_1
        sync_mode = "incremental_deduped_history"
      },
      {
        name      = test_collection_2
        sync_mode = "incremental_deduped_history"
      }
    ]
  }

After schema updating, I got the following terraform plan:
  # airbyte_connection.mongodb_bigquery will be updated in-place
  ~ resource "airbyte_connection" "mongodb_bigquery" {
      ~ configurations                       = {
          ~ streams = [
              ~ {
                  ~ name         = "test_collection_2" -> "test_collection_1"
                    # (3 unchanged attributes hidden)
                },
              ~ {
                  ~ name         = "test_collection_1" -> "test_collection_2"
                    # (3 unchanged attributes hidden)
                },
            ]
        }
...
    }

terraform apply:
{"type":"https://reference.airbyte.com/reference/errors","detail":"The body of the request contains an invalid connection configuration. **Primary key for stream: test_collection_1 is already pre-defined.** Please do NOT include a primary key configuration for this stream.","title":"bad-request","status":400}

The same situation is for the notion source

can be omitted by the following definition
resource "airbyte_connection" "mongodb_bigquery" {
...
  configurations = {
    streams = [
        name        = "test_collection_2"
        sync_mode   = "incremental_deduped_history"
        primary_key = null
      }
    ]
  }
}

Fixed by https://github.com/airbytehq/terraform-provider-airbyte/pull/128


Blank page appears when footnote is present in front page

When a footnote is placed in the front page (e.g. in the Summary), a blank page is introduced between the front page and the main content.
For demonstration, please checkout the file:
ECE_TRADE_C_CEFACT_2019_22_REV1.zip
In addition to that problem, even if there no is blank page, if I place the cursor on the second page the Word page indicator (at the bottom left corner) says that I am on the third one 😕.

The blank page is a very simple issue: the plenary cover page in Word has a whole lot of empty paragraphs, to put the session id vaguely at the bottom of the page; if the abstract is any longer than expected, or if a footnote shows up, the page overflows into the next page.
The only thing to do here is to put the session id in a text box, which will be statically at the bottom of the page. And hope that the text box doesn't clash with any footnotes.


Release notes for Catalog 2.81

To be released tomorrow morning (1-6)

@johannahemminger is off today, so I've asked @katarzyna-koltun-mx to review. Please let us know here, or in the docs channel in Slack when the release is successful.
Thanks.

@sjoerdbreur I've reviewed the file. Ready to publish on 1/6 after you give the go ahead.

@katarzyna-koltun-mx Thank you! Added note to inform you after the release tomorrow.

Thanks @MarkvanMents @katarzyna-koltun-mx for taking care of this while I was out!


Register package at Julia General Registry

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/97971
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.0.1 -m "<description of version>" ea879c62b413c8efc199fcf873105c6e90faa6a3
git push origin v0.0.1


Add README line discussing named-param path inheritance

Behavior of path inheritance for url strings containing named parameters is confusing and different from non-named parameter urls. One way to reconcile the difference is to include a * wildcard. Documentation of this fix will alleviate confusion.

Thanks!


[Refactor] Remove check when registering functions

Remove check when registering to allow functions with the same function name but different arguments.
What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

[FE PR Coverage Check]
:disappointed: fail : 0 / 4 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/AnyElementType.java
0
1
00.00%
[21]

:large_blue_circle:
com/starrocks/catalog/AnyStructType.java
0
1
00.00%
[20]

:large_blue_circle:
com/starrocks/catalog/AnyMapType.java
0
1
00.00%
[20]

:large_blue_circle:
com/starrocks/catalog/AnyArrayType.java
0
1
00.00%
[21]

run starrocks_admit_test


Minor RP chem overhaul.

[ ] Switch to using the new drowsiness system introduced in https://github.com/space-wizards/space-station-14/pull/27454 for sleep related side-effects.
[ ] Some of the more extreme chems need more side-effects. You should not be able to have 5 pills of extremely potent painkillers without major side effects.

Additionally should port Millon's chem/pain overhaul from DV.


Library creation via object browser added

Changes
Libraries can now be created via the object browser. You'll find a new + icon on the right of "OBJECT BROWSER". This feature was requested in #194.
Please check the following things before merging:

Is it working properly? Unfortunately it's not allowed to create new libraries on PUB400. So I couldn't test it properly.
Is the "+" icon good for this use case? In my opinion the icon with the directory and a "+" would fit better but it was already used.

Checklist

[x] have tested my change
[x] updated relevant documentation
[x] Remove any/all console.logs I added
[x] eslint is not complaining
[x] have added myself to the contributors' list in the README
[x] for feature PRs: PR only includes one feature enhancement.

Working good. Thanks for your work here @szsascha!


Edge-Node-Cluster cleanup KubeVolumeInfo and KubeStorageInfo

StorageHealthStatus should be under KubeVolumeInfo as a substatus.
New enum ServiceStatus more appropriately describes multi-node service health.
Added missing enum entries to StorageVolumeReplicaStatus

Moved a field from KubeStorageInfo to KubeVolumeInfo but I'm hoping it should be ok as these should not be in use yet as they were just added recently in PR #63

latest push should resolve yetus enum prefix issue

@eriknordmark I believe that eve-api version has been pulled into a dev branch of a controller but I don't think it has been pushed to a release of a production facing controller yet.  I think @xyuria-zededa can help confirm.

@eriknordmark I believe that eve-api version has been pulled into a dev branch of a controller but I don't think it has been pushed to a release of a production facing controller yet. I think @xyuria-zededa can help confirm.

I haven't used it yet, so you can feel free to change anything there.


Ensure consistent nomenclature with API docs

We should mimic the nomenclature of properties on our API docs. This would be a breaking change so it should be done as part of 2.0.
Brought up as part of #58.

@connor - Can we close this issue out or is it still something that needs to be fixed?


Is it possible to replace the file in the same location?

This is more convenient, as I've already built my css and js package to a dist folder using other steps in the build chain.
Is it supposed to be possible to do a configuration like this in a way that replaces the existing file? (instead of adding the .gz extension)
This method adds .gz as a sibling:
    compress:
      options: pretty: true
      mainPackages:
        files: [
          "<%= grunt.option('target') %>all-min.css": "<%= grunt.option('target') %>/all-min.css"
          "<%= grunt.option('target') %>all-min.js": "<%= grunt.option('target') %>/all-min.js"
        ]

This method creates a corrupted file 20 bytes in length:
    compress:
      options: pretty: true
      mainPackages:
        expand: true
        cwd: "<%= grunt.option('target') %>"
        src: '**/{<%= cfg.minName %>.css,core/main.js}'
        dest: "<%= grunt.option('target') %>"
        ext: ''

+1

+1

+1

+1

+1

:+1:


Indicator cdc vaccines in progress

New PR for new branch of the CDC Indicator fixed. Only the committs relevant to this indicator should be in this PR.

Seems to be fixed now!

It doesn't crash (🎉 ) but when I run with "export_start_date": "2021-09-01" I still get dates in receiving back to 2020-12-12:
$ ls receiving/ |head
20201212_hhs_cumulative_counts_part_vaccine_12P.csv
20201212_hhs_cumulative_counts_part_vaccine_18P.csv
20201212_hhs_cumulative_counts_part_vaccine_65P.csv
20201212_hhs_cumulative_counts_part_vaccine.csv
20201212_hhs_cumulative_counts_tot_vaccine_12P.csv
20201212_hhs_cumulative_counts_tot_vaccine_18P.csv
20201212_hhs_cumulative_counts_tot_vaccine_65P.csv
20201212_hhs_cumulative_counts_tot_vaccine.csv
20201212_hhs_incidence_counts_part_vaccine_12P.csv
20201212_hhs_incidence_counts_part_vaccine_18P.csv

Full params:
{
  "common": {
    "export_dir": "./receiving",
    "log_filename": "cdc_vaccines.log"
  },
  "indicator": {
    "base_url": "https://data.cdc.gov/api/views/8xkx-amqh/rows.csv",
    "export_start_date": "2021-09-01"
  },
  "validation": {
    "common": {
      "data_source": "cdc",
      "span_length": 14,
      "min_expected_lag": {"all": "1"},
      "max_expected_lag": {"all": "7"},
      "dry_run": true,
      "suppressed_errors": []
    },
    "static": {
      "minimum_sample_size": 0,
      "missing_se_allowed": true,
      "missing_sample_size_allowed": true
    },
    "dynamic": {}
  }
}

Restarting this thread now! Substantial changes will be made in light of the boosters.

As a note, we will probably need to update the source if we want to include data on Booster Shots: https://data.cdc.gov/Vaccinations/COVID-19-Vaccinations-in-the-United-States-Jurisdi/unsk-b7fc
vs. what we are currently using: https://data.cdc.gov/Vaccinations/COVID-19-Vaccinations-in-the-United-States-County/8xkx-amqh which does not give information on boosters. Let me know what you think we should do @krivard  @dshemetov

Sorry for taking so long to get to this review @Ananya-Joshi. I am getting a test error when I pull and test locally, see below
test_run.py F...                                                                                [100%]

=========================================================== FAILURES ===========================================================
_______________________________________________ TestRun.test_output_files_exist ________________________________________________

self = <test_run.TestRun object at 0x7f2b733ee0a0>

    def test_output_files_exist(self):
        """Test that the expected output files exist."""
        run_module(self.PARAMS)

        csv_files = [f for f in listdir("receiving") if f.endswith(".csv")]

        dates = [
            "20210810",
            "20210811",
            "20210812",
            "20210813",
            "20210814",
            "20210815",
            "20210816",
            "20210817",
        ]
        geos = ["state", "hrr", "hhs", "nation", "msa"]

        expected_files = []
        for metric in ["cumulative_counts_tot_vaccine",
                                    "incidence_counts_tot_vaccine",
                                    "cumulative_counts_tot_vaccine_12P",
                                    "incidence_counts_tot_vaccine_12P",
                                    "cumulative_counts_tot_vaccine_18P",
                                    "incidence_counts_tot_vaccine_18P",
                                    "cumulative_counts_tot_vaccine_65P",
                                    "incidence_counts_tot_vaccine_65P",
                                    "cumulative_counts_part_vaccine",
                                    "incidence_counts_part_vaccine",
                                    "cumulative_counts_part_vaccine_12P",
                                    "incidence_counts_part_vaccine_12P",
                                    "cumulative_counts_part_vaccine_18P",
                                    "incidence_counts_part_vaccine_18P",
                                    "cumulative_counts_part_vaccine_65P",
                                    "incidence_counts_part_vaccine_65P"]:
            for date in dates:
                for geo in geos:
                    expected_files += [date + "_" + geo + "_" + metric + ".csv"]
                    if not("cumulative" in metric) and not (date in dates[:6]):
                        expected_files += [date + "_" + geo + "_" + metric + "_7dav.csv"]

        print(set(csv_files)-set(expected_files))
>       assert set(csv_files) == set(expected_files)
E       AssertionError: assert {'20210810_hh...12P.csv', ...} == {'20210810_hh...12P.csv', ...}
E         Extra items in the left set:
E         '20210818_state_incidence_counts_tot_vaccine_18P.csv'
E         '20210819_state_incidence_counts_tot_vaccine_65P_7dav.csv'
E         '20210819_nation_cumulative_counts_tot_vaccine_18P.csv'
E         '20210819_hhs_incidence_counts_tot_vaccine_18P.csv'
E         '20210818_hhs_incidence_counts_part_vaccine_12P.csv'
E         '20210819_hhs_cumulative_counts_part_vaccine.csv'...
E
E         ...Full output truncated (236 lines hidden), use '-vv' to show

test_run.py:71: AssertionError

Can you also please merge main into this when you can, so the diffs are a bit easier to read?

Pushing a small commit to make the diff code suggestion pass test_pull.py. All tests pass now 👍


Connecting to Kafka triggers DEP0123

Describe the bug
When using a broker identified by a domain name, its IP addresses seems to be used for domain resolution rather than its IP. The domain name appears to resolve to multiple IP addresses. (I'm guessing those are the different Kafka instances of the cluster.)
To Reproduce
Connect to a Kafka cluster identified by a domain name that refers to multiple IP addresses. (In my case a Kafka cluster hosted by Aiven triggered the issue.)
Expected behavior
No warnings.
Observed behavior
(node:40285) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.

Environment:

OS: NixOS 21.11
KafkaJS version 1.16.0
Kafka version 3.1
NodeJS version 16.14.2

Can you reproduce this with 2.2.0-beta.2? #1425 made it so that we don't set the servername by default if the host is an IP address rather than a hostname.
My guess, without having any access to aiven, is that the issue is not with the first broker(s) that you add to the config, but rather the subsequent brokers that are discovered. I'm guessing that the domain just resolves to one of the brokers, and the TLS ServerName will be the domain you provided, but that broker then returns a list of IPs rather than domain names, so subsequent connections use the IP as ServerName, triggering this warning.

Ah, yes, I checked application logs: the warning appeared upon daily server restart on July 20th for the last time. No version upgrade of KafkaJS was involved, so I would guess something about DNS or another aspect of the cluster infrastructure must have changed on Aiven's side at that point, so that our setup no longer reproduces this issue.

Alright, then I will close this, as this should have been fixed by #1425 regardless.


Flag to not prompt (useful for scripts)

From @lorenzo-stoakes.
A flag to prevent y/n questions, e.g. --noconfirm.

All commands that require confirmation accept a --yes/-y options. I'll close unless there is a specific command that is not working as expected.

I've noticed the following:-
[~]$ resin app rm -y foobar
Application not found: rm

Which combines a couple of issues, the first being that since app rm is listed a separate command from app, it would follow that the -yought to be where it is shown above. The second issue (perhaps ought to be broken out from this one) is that when there are more than the expected number of arguments, it seems to revert to the default of showing apps - I would have expected resin app rm to be an entirely separate command.
I wonder whether it might make more sense to use a separator that isn't whitespace to make it clear that this is a separate command? Comparing to a couple of other CLI tools - heroku uses : so it would be resin app:rm and git uses - so you'd do something like resin app-rm of course we could also guess that resin app rm meant resin app-rm or resin app:rm, but it is possible that we'll have a conflict - what if a user has an app called rm? I think the app name size restricts this right now, but for other commands this could become the case, plus we may remove these restrictions at some point.
We may need to separate these things out a bit from this issue @jviotti :)

That's interesting. Let me investigate the command option issue as it may have a quick fix in Capitano.
About the name collision probability, this only happens when command prefixes are also a command on their own (for example "device associate" and “device”). A quick solution would be to convert “device” and “app” into “device info”, “app info” or “device ls”, “app ls".

(ported from internal discussion :)
yeah, it's a trade off for sure @jviotti , but one worth thinking about. The ability to say something like resin app foo is handy however, and in this case we should consider the possibility of collisions, even if unlikely! Also in some ways 'resin foo-bar' or 'resin foo:bar' are a little clearer I think as it makes it really consistent that the pattern is 'resin [command] [args]' for people with small brains like me :)

Also, it seems that the flag has to be put last in the command, which is very unusual:-
[~]$ resin -y app rm foo
Usage: resin [COMMAND] [OPTIONS]

Commands:

    version                       	output the version number
    help [command...]             	show help
    login [token]                 	login to resin.io
    logout                        	logout from resin.io
    signup                        	signup to resin.io
    whoami                        	get current username
    app create <name>             	create an application
    apps                          	list all applications
    app <name>                    	list a single application
    app rm <name>                 	remove an application
    app restart <name>            	restart an application
    app associate <name>          	associate a resin project
    init                          	init an application
    devices                       	list all devices
    devices supported             	list all supported devices
    device rename <name> [newName]	rename a resin device
    device init [device]          	initialise a device with resin os
    device <name>                 	list a single device
    device rm <name>              	remove a device
    device identify <uuid>        	identify a device with a UUID
    device await <name>           	await for a device to become online
    drives                        	list available drives
    note <|note>                  	set a device note
    preferences                   	open preferences form
    keys                          	list all ssh keys
    key add <name> [path]         	add a SSH key to resin.io
    key <id>                      	list a single ssh key
    key rm <id>                   	remove a ssh key
    envs                          	list all environment variables
    env add <key> [value]         	add an environment variable
    env rename <id> <value>       	rename an environment variable
    env rm <id>                   	remove an environment variable
    logs <uuid>                   	show device logs
    os download <name>            	download device OS
    os install <image> [device]   	write an operating system image to a device
    examples                      	list all example applications
    example clone <id>            	clone an example application
    example <id>                  	list a single example application
    plugins                       	list all plugins
    plugin install <name>         	install a plugin
    plugin update <name>          	update a plugin
    plugin rm <name>              	remove a plugin
    update                        	update the resin cli

Global Options:

    --quiet, -q         	quiet (no output)
    --project, -j <path>	project path
    --version, -v       	output the version number
    --no-color          	disable colour highlighting

[~]$ resin app -y rm foo
ID: 123456789
APP NAME: foo
DEVICE TYPE: raspberry-pi2
GIT REPOSITORY: <redacted>
COMMIT: <redacted>
[~]$ resin app rm -y foo
Application not found: rm
[~]$ resin app rm foo -y
[~]$ # Succeeded.

I'd expect that any of the first 3 possibilities would work, and the final one would fail :)

@lorenzo-stoakes Can you move your last post to a different (new) GitHub issue, so I can work on it?

@jviotti deleted and will create a new issue in just a moment!

Closing issue since a new one was opened in Capitano for this purpose.


More explanatory error messages

Tried to improve error messages with better hints to what the underlying cause might be.

Looks good, see the 1 comment :)
Merge at will :+1:


Installer (6.0/6.1) prompts for WMF 4.0 or higher on Windows 7 but 4.0 doesn't install

Steps to reproduce
With clean Windows 7 x86 SP1 VM.  Run Powershell 6.0.4 MSI from Releases (tried 6.1 too).
Get prompt that it needs WMF 4.0 or higher.  (This is after an initial prompt to install the Universal C runtime which installs and is identified ok)
Install WMF 4.0 (KB2819745) x86 for Windows 7.. Same error.  Rebooted.  Same error.  Re-ran WMF 4.0 installer and that confirmed it was already installed.
I subsequently installed WMF 5.1 which also required installing .NET Framework 4.5 and then PowerShell 6 installed.  But issue is with prompt and prerequisite saying to use 4.0.
Expected behavior

```http://aka.ms/pscore6-prereq also says use 4.0

Actual behavior
---------------

Installer fails to install or identify that WMF 4.0 was installed.

Environment data
----------------

<!-- provide the output of $PSVersionTable -->

powershell
> $PSVersionTable

```N/A

Note that even after using 5.1 and getting the installer to install, I then get a different error when trying to open the shell:
C:\Program Files\PowerShell\6>pwsh.exe
Failed to load the dll from [C:\Program Files\PowerShell\6\hostfxr.dll], HRESULT: 0x80070057
The library hostfxr.dll was found, but loading it from C:\Program Files\PowerShell\6\hostfxr.dll failed
  - Installing .NET Core prerequisites might help resolve this problem.
     http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409

Looks like pre-requisites are very out of date.

/cc @SteveL-MSFT Can we close the issue?


smpl trans value seems not work

when import the fbx to blender,  There's  no translation frame to frame, the trans value is below:

in blender, It shows like this:

me too！

Hey guys, I also encountered this problem, how did you solve it?

Anyone got the answer?

Hey, I got the same issue. The model joints move in place but there is no translation. Did anyone figure out a solution.
Appreciate your time and input.
Thanks!

close as lacking details to replicate.


feat: add scss core and move existing paragon scss into it

BREAKING CHANGE: edx-bootstrap scss has been moved into this project and scss existing in Paragon has been folded into this new scss core.
Usage of styles for edX used to be:
@import<EMAIL_ADDRESS>@import<EMAIL_ADDRESS>
Usage for edX:
@import<EMAIL_ADDRESS>
Usage for Open edX users:
// Custom scss variables should be set prior to this line
@import<EMAIL_ADDRESS>

Coverage remained the same at 88.814% when pulling 56a70809deef7320ed5befc66b67fe40f42d6be9 on abutterworth/add-scss-core into 72ff1efb91eb9c0702f6bcedb7e2fc65314bece2 on next.


The behavior of FOR XML AUTO is different when compatibility level is less then 90

The behavior of FOR XML AUTO is different when compatibility level is less then 90

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

ID: 252ab2db-6a09-17d5-b082-c369f06028ec
Version Independent ID: 3e6521e3-565a-9a30-b17d-49254c22569d
Content: Use AUTO Mode with FOR XML - SQL Server
Content Source: docs/relational-databases/xml/use-auto-mode-with-for-xml.md
Product: sql
Technology: xml
GitHub Login: @MightyPen
Microsoft Alias: genemi

@sqlenders Your statement is probably correct. Yet the particular article. "Use AUTO Mode with FOR XML", only claims to cover SQL Server versions 2016 and later (at least through SQL Server 2019). Compatibility Level 90 refers to SQL Server 2005 (I think), and the effect of Compat 90 on AUTO is covered in documentation between 2008-2014 (inclusive). At some point it becomes necessary to remove history from the latest articles.
I am now closing this Issue 2544.
Thank you for submitting this Issue. We hope to hear from you again.
P.S. Info/link about Compatibility Levels:

https://docs.microsoft.com/en-us/sql/t-sql/statements/alter-database-transact-sql-compatibility-level?view=sql-server-2016

. .


cant save attached files in email (outlook) via drag & drop

Description
i open up the mail, drag and drop the attachment to a location, but the files don't save, instead I need to save them through the context menu in my email client
Steps To Reproduce
open email client
open mail
drag and drop attachment to location opened in files browser
Requirements
files should be save in that directory
Files Version
<IP_ADDRESS>
Windows Version
Windows 10 Pro Version	22H2 19045.3693
Log File
cant find the file

Is this still an issue in the preview version? https://files.community/download/preview

FYI, I filed https://github.com/files-community/Files/issues/13646 and just checked with Files Insider Preview <IP_ADDRESS> on Windows 10 Enterprise 22H2 build 19045.3324 (10.0.19045.3324), and the behavior is the same: Outlook attachments are not saved.

Thanks! We're still tracking this in #13646.


Tag releases

Could you please tag the source? This allows distributions to get the complete source from GitHub and version the packages properly (e.g., https://github.com/NixOS/nixpkgs/pull/145126).
Thanks

@ly4k, looks like that you missed to push the tag :wink:

I'm expecting to publish a major release on Saturday. I will tag that release.

@fabaff should be tagged now with the new version

@ly4k , thanks a lot.


[MINOR] Update community sync links

@nsivabalan tried but haven't found a good way. importing ics is possible but not that convenient either


⚠ Bofrost.de has degraded performance

In 8b8753b, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1028 ms

Resolved: Bofrost.de performance has improved in 4ff30de after 6 minutes.


Unexpected sorting

hey!
I've installed this app to up my emoji game :game_die: and noticed the results are sorted different than I would expect:

This should be an exact match, but the emoji I'm looking for is at the end of the list :eyes:.

I'm looking for one of the cat emojis here but it's matching on "Intoxicated" instead :crying_cat_face:.
I would expect rofi-emoji to behave more like github/slack/signal (: followed by two characters invokes the emoji search with sorting that works better for me) but I'm not sure if the sorting is up to rofi-emoji or rofi itself.
Anyway, very useful tool, I've moved the package from the AUR to [community] so you might want to update your install instructions. Also, github doesn't offer subscribing to tags but I've subscribed to "release notifications", if you create a release over here I get a notification in my github inbox and I can update the package faster. :racehorse:
Thanks! :heart:

Thank you! :smile:
I've always assumed I could not affect sort ordering and that the problem came from Rofis fzf sorter not being as robust.
https://github.com/davatorium/rofi/issues/810
However, when I wanted to showcase this I actually found something out… Check this one out.
rofi -no-config -dmenu -sort -sort-method fzf < /usr/share/rofi-emoji/all_emojis.txt

This loads Rofi with standard options and sets sorting.
In this case, searching for cat returns mostly cat emojis (and a catepillar) at the top. eyes also yield perfect sorting.
This also applies when using this plugin and no default config:
rofi -no-config -modi emoji -show emoji -sort -sort-method fzf

However, if I use my normal config then things break for me:
# Removed -no-config
rofi -modi emoji -show emoji -sort -sort-method fzf

Then I get bad sorting order. There should be some setting in my config files that breaks this and perhaps it is the same for you. I suggest you try this out yourself and see if you can find the culprit.

I found the culprit by diffing the config:
diff -u <(rofi -no-config -sort -sort-method fzf -help) <(rofi -sort -sort-method fzf -help)

…
 	-combi-modi [string]                    Set the modi to combine in combi mode
 		window,run (Default)
 	-matching [string]                      Set the matching algorithm. (normal, regex, glob, fuzzy)
-		normal (Default)
+		fuzzy (Rasi File)
 	-[no-]tokenize                          Tokenize input string
 		True (Default)
…

If I add -matching normal to my normal commandline, then I get emojis in a sensible order. It would seem that my initial assumption still holds.
I recommend disabling -matching fuzzy and live with having to type consecutive substrings.[1]
[1]: For example, at face will find "Cat … face", but at fce will not as no word contains "fce".

Hey, I was gonna open a similar issue after seeing this :stuck_out_tongue:

Maybe the sort options could be documented in the README?
Or rofi could let plugins choose a sort order :-)
Thanks


Application immediately closing on SOME systems

I recently finished my first Piston project and it works fine on my main development desktop (Win10).
When I open my executable on my laptop (or any other machine I've tested on), the window opens and then closes immediately.

I thought it was a .dll issue, so I used dependency walker and found no differences.
I tried changing the used OpenGL version all the way down to 2.1, no difference.
Microsoft Visual C++ redists are installed.
Graphics driver (tested on a quadro m1200 laptop) is up to date or should AT LEAST support opengl 3.2.
Building from source works, but shows the same behaviour when run.
RUST_BACKTRACE=1 prints nothing.

The executable quits with code 0, no errors are thrown. I've tried debugging it with Visual Studio Code and found that it randomly returns when nothing important is happening. It seems to be panicking though (seen in the stack frames).
I'm creating an issue for this as I'm pretty sure it's some internal error in Piston. Might be related to #1207 and #1202.
Edit: both the opengl and gfx backends show the same behaviour. I've switched to using piston_window now (gfx).

Reddit post: https://www.reddit.com/r/rust_gamedev/comments/7chrbf/piston_executable_not_running_on_some_windows/

Can you try another window backend?
You can change the window backend in PistonWindow by inserting a parameter:
extern crate sdl2_window;

use sdl2_window::Sdl2Window;

let mut window: PistonWindow<Sdl2Window> = ...

It crashes saying: SDL2.dll was not found. After adding that to the directory, it showed the same behaviour, BUT this time it actually printed an error message! With RUST_BACKTRACE=1 this resulted in:
an `Err` value: ""', src\libcore\result.rs:906:4
stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>

I found some information about this and it seems to be a rust bug fixed long ago (??).
After that, I tried building the application on the laptop where this issue was appearing. Apparently the SDL2.lib didn't exist inside the /toolchains/../lib folder.
" Since 0.31, this crate supports a feature named "bundled" which downloads SDL2 from source, compiles it and links it automatically. While this should work for any architecture, you will need a C compiler (like gcc, clang, or MS's own compiler) to use this feature properly. " - I do have the MS build tools installed.
For now I've copied them from my desktop. When compiling and running in debug mode, this message was printed:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ""', src\libcore\result.rs:906:4
stack backtrace:
   0:     0x7ff6c94db441 - std::sys_common::backtrace::_print
                               at C:\projects\rust\src\libstd\sys_common\backtrace.rs:94
   1:     0x7ff6c94e147c - std::panicking::default_hook::{{closure}}
                               at C:\projects\rust\src\libstd\panicking.rs:380
   2:     0x7ff6c94e1165 - std::panicking::default_hook
                               at C:\projects\rust\src\libstd\panicking.rs:397
   3:     0x7ff6c94e19c5 - std::panicking::rust_panic_with_hook
                               at C:\projects\rust\src\libstd\panicking.rs:611
   4:     0x7ff6c94e1858 - std::panicking::begin_panic<alloc::string::String>
                               at C:\projects\rust\src\libstd\panicking.rs:572
   5:     0x7ff6c94e1731 - std::panicking::begin_panic_fmt
                               at C:\projects\rust\src\libstd\panicking.rs:522
   6:     0x7ff6c94e169f - std::panicking::rust_begin_panic
                               at C:\projects\rust\src\libstd\panicking.rs:498
   7:     0x7ff6c94e783e - core::panicking::panic_fmt
                               at C:\projects\rust\src\libcore\panicking.rs:71
   8:     0x7ff6c9457daa - core::result::unwrap_failed<str*>
                               at C:\projects\rust\src\libcore\macros.rs:41
   9:     0x7ff6c9438037 - core::result::Result<gfx_device_gl::info::Version, str*>::unwrap<gfx_device_gl::info::Version,str*>
                               at C:\projects\rust\src\libcore\result.rs:772
  10:     0x7ff6c9491e22 - gfx_device_gl::info::Info::get
                               at C:\Users\20173986\.cargo\registry\src\github.com-1ecc6299db9ec823\gfx_device_gl-0.14.4\src\info.rs:193
  11:     0x7ff6c94923fc - gfx_device_gl::info::get
                               at C:\Users\20173986\.cargo\registry\src\github.com-1ecc6299db9ec823\gfx_device_gl-0.14.4\src\info.rs:232
  12:     0x7ff6c9326920 - gfx_device_gl::Device::new<closure>
                               at C:\Users\20173986\.cargo\registry\src\github.com-1ecc6299db9ec823\gfx_device_gl-0.14.4\src\lib.rs:251
  13:     0x7ff6c9328017 - gfx_device_gl::create<closure>
                               at C:\Users\20173986\.cargo\registry\src\github.com-1ecc6299db9ec823\gfx_device_gl-0.14.4\src\lib.rs:173
  14:     0x7ff6c933a2aa - piston_window::PistonWindow<sdl2_window::Sdl2Window>::new<sdl2_window::Sdl2Window>
                               at C:\Users\20173986\.cargo\registry\src\github.com-1ecc6299db9ec823\piston_window-0.73.0\src\lib.rs:183
  15:     0x7ff6c93a5a0b - piston_window::{{impl}}::build_from_window_settings<sdl2_window::Sdl2Window>
                               at C:\Users\20173986\.cargo\registry\src\github.com-1ecc6299db9ec823\piston_window-0.73.0\src\lib.rs:152
  16:     0x7ff6c9398b15 - window::WindowSettings::build<piston_window::PistonWindow<sdl2_window::Sdl2Window>>
                               at C:\Users\20173986\.cargo\registry\src\github.com-1ecc6299db9ec823\pistoncore-window-0.30.0\src\lib.rs:387
  17:     0x7ff6c93bed37 - physics_renderer::main
                               at C:\Users\20173986\Documents\GitHub\Physics-Renderer\src\main.rs:37
  18:     0x7ff6c94e2441 - panic_unwind::__rust_maybe_catch_panic
                               at C:\projects\rust\src\libpanic_unwind\lib.rs:99
  19:     0x7ff6c94e1c71 - std::rt::lang_start
                               at C:\projects\rust\src\libstd\rt.rs:54
  20:     0x7ff6c93bf51b - main
  21:     0x7ff6c94edaf8 - __scrt_common_main_seh
                               at f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:253
  22:     0x7ffa52462773 - BaseThreadInitThunk
error: process didn't exit successfully: `target\debug\physics_renderer.exe` (exit code: 101)

I debugged the executable with Visual Studio Code and found out that on let shading_language = ..  (info.rs line 193) the function get_string returns NULL and therefore crashes.

https://github.com/gfx-rs/gfx/issues/1629

@bvssvni This issue occurs when enabling anti-aliasing: window.samples( nr )

Thanks for noticing.

Not 100% sure this was the problem, but
This seems to have been fixed with the latest mesa 18.*. See https://github.com/PistonDevelopers/piston/issues/1202 for more information.

Closing.


Downgrade ipywidgets to version 7.7.2

Expected Behavior

The library ipywidgets is supported.
Actual Behavior

QuantConnect uses the release candidate 8.0.0rc1 which doesn't work well in VSCode's Jupyter Notebook environment.
IPyWidgets 8 is not officially supported by VSCode as you can see here.
There are a lot of issues with version 8 of ipywidgets as you can see here  and here.
Potential Solution / Workaround

Uninstall ipywidgets 8 and install ipywidgets==7.7.2 instead.
Reproducing the Problem

Refer to this forum discussion.
System Information

QC Cloud
Checklist

[X] I have completely filled out this template
[X] I have confirmed that this issue exists on the current master branch
[X] I have confirmed that this is not a duplicate issue by searching issues

[X] I have provided detailed steps to reproduce the issue

Hey @Martin-Molinero ,
it probably doesn't make sense to downgrade to an older version. The responsible team has already started working on it (PR). And according to this comment, support for IPyWidgets 8 is planned for the February release. I think it's best to give it a few more weeks before taking any action.


How to refresh CSRF token?

I am using ReactOnRails.authenticityToken(); to get the CSRF token generated by csrf_meta_tags. The problem is that when I send first request, it works fine as the token is valid. Whenever I send any subsequent API request, it returns the previously invalidated CSRF token and therefore I get ActionController::InvalidAuthenticityToken. How can I refresh the CSRF token after each API request?

@Talha345 nothing has changed around this for many years. I think there is something specific to your app.

@justin808 Could be but do you have any suggestion on how to deal with this scenario. I will try to explain my specific scenario in detail:

React SPA endpoint is triggered and component is mounted and csrf_meta_tags are added via the layout.
I use the CSRF token and execute a login API. On success response, I update the user in the SPA and therefore there is no page reload.
Since the user is logged in, I show a link to Logout and upon clicking on it another API is triggered but of course the CSRF token is invalidated.

NOTE: In older versions of Rails, a single CSRF token was used for each session but since recent versions, we have a new CSRF token for each new request.

Solution for anyone having the same issue:

Added a after_action method in ApplicationController:

after_action :add_csrf_token_to_json_request_header

private

  def add_csrf_token_to_json_request_header
    if request.format == :json && !request.get? && protect_against_forgery?
      response.headers['X-CSRF-Token'] = form_authenticity_token
    end
  end

On React side:

    if (response.headers['x-csrf-token']) {
      setAuthenticityToken(response.headers['x-csrf-token'])
    }

    export function setAuthenticityToken(token) {
     const metaTag = document.querySelector("meta[name='csrf-token']");
     metaTag.setAttribute('content', token)
    }

Took inspiration from https://stackoverflow.com/questions/33941864/rails-automatically-update-csrf-token-for-repeat-json-request

@Talha345  @Judahmeek @alexeyr-ci Should this go into the docs? If so, could one of you submit a PR and I'll merge it.


Incorrect "hostname" in nomad client and server certificates

In the nomad client and server certificate:
https://github.com/ai4os/ai4-ansible/blob/8872cccc2ccf8303b02a535b008d20724af5607c/roles/nomad/tasks/generate_certificates.yml#L30-L36
There is an error.
We are only generating one server/client certificate used in all the servers/clients, which is generated in the nomad_master node. So the "ansible_hostname" (or the IP address) always refers to the nomad_master node in all of them, and it may raise some SSL errors in applications accessing the nomad API.
Currently it is not a major issue, but we have to keep an eye.

Hi Miguel, i will check this as soon as i can.


Menu option not showing when extension installed

Hello,
I installed the extension in Edge, Version 87.0.664.57.
The extension icon is showing grey (i don't know if it should be blue or not...)
But as explained in the description of the app in the store, the context menu "Copy Link address with CreatorID" should be visible, but I don't see the context menu item.
Do I need to fix any option or setting in my browser to make it work?
Any suggestion for troubleshooting?

Hi Peter,
it is correct, that the extension is showing a grey symbol since it doesn't require any access:

Did you enter your Creator Id within the options already? Otherwise, the context menu won't be visible:

Now you should see the menu on all links that are tracked by the docs & learn champion program. To verify it, just go to https://docs.microsoft.com/en-us/ and right-click on "Documentation":

Hello,
thanks for the rapid response...
I've got my CreatorIDs entered.

and when I right click the Documentation link as you suggested, the context menu does not show

In Chrome it works. In Edge not.

@PeterGeelen Hm, someone else also mentioned he had to reinstall it on edge in order to get it working again. Can you please try that? I will check what could be the issue here and try to improve the extension.

Yes, it works after removing it, reinstalling it then killing edge and restarting Edge.
But even on docs only some of the URL links have the option to use the menu item.
That's another discussion.

Should be fixed with release 1.2.2


Adding the function of reaching the head/tail trough Command+up/down keys

Thank you very much for all you have done for VSCode; VSCode has helped me a lot. Thank you very much.
When the cell is in edit mode, I can quickly reach the head/tail of the content in the cell by pressing Command+Up/Down keys.
But in unselected or command mode, Command+Up/Down keys have no effect (just the up/down keys to reach the previous or next Cell), I don’t know if you can consider adding the function that I can quickly reach the head/tail of the entire file by pressing Command+Up Down keys in unselected and command mode.
Thank you.

If you are using the Jupyter Notebook provided by the Python extension, please file an issue against them. For the native notebook we are shipping in VS Code (Insiders), we already support the keybindings.

/extPython


Fix animate test for IE11, regenerate docs

Apparently, previous test setup did not work properly with regenerator-runtime converting await call, so now passing dumb callback to MutationObserver and taking records separately.

This change is

Reviewed 7 of 7 files at r1.
Review status: :shipit: complete! all files reviewed, all discussions resolved

Comments from Reviewable


Remove dead link to Targets documentation on homepage

As discussed in #1, this will return in a future PR.

@Tpuljak @osslate why is this changed to yarn when the default is npm?

Because we use yarn in our other JS repos.

@Tpuljak @osslate why is this changed to yarn when the default is npm?

Because we use yarn in our other JS repos.

I have no issue with yarn. but the devcontainer was setup for npm and is now broken https://github.com/daytonaio/docs/issues/14

@Tpuljak @osslate why is this changed to yarn when the default is npm?

Because we use yarn in our other JS repos.

I have no issue with yarn. but the devcontainer was setup for npm and is now broken #14

We'll fix it as part of that issue.


Update Blockly (June release)

This release come's with a lot of refactoring in many Blockly structures including:

Variables. Now are stored in a VariableModel instead of a string, which includes a type
Gestures. Now handled by a central gesture class, instead of each component handling the same gestures.
Flyouts. Refactored into Vertical and Horizontal Flyout classes.

This release will make the freshcoat (scratch-blocks) changes much more aligned with the master version.
In pxt, we override the Variable flyout code, and so I've updated that to deal with the refactor.
I haven't noticed any other changes from our end, but let's do some testing on this branch before we merge.
Respective Blockly branch: https://github.com/Microsoft/pxt-blockly/tree/blocklyjune

I'm getting "Field editor lights not registered" when I try and open the light category in Adafruit

Ah, looks like the issue is that you removed the playAudio API from the workspace in blockly.d.ts

Yeah audio API has been refactored. Will have to reflect these changes in the ring field editor.

Tested IE, Firefox, and Edge. Seems to be working fine.


chore: prepare release 2024-04-03

Summary
This PR has been created using the yarn release script. Once merged, the clients will try to release their new version if their version has changed.
Version Changes

~csharp: 7.0.0-alpha.7 (no commit)~
~dart: 1.6.3 (no commit)~
~go: 4.0.0-beta.10 (no commit)~
~java: 4.0.0-beta.28 (no commit)~
~javascript: 5.0.0-alpha.112 (no commit)~
~kotlin: 3.0.0-beta.23 (no commit)~
~php: 4.0.0-alpha.104 (no commit)~
~python: 4.0.0b13 (no commit)~
~ruby: 3.0.0.alpha.16 (no commit)~
~scala: 2.0.0-alpha.15 (no commit)~
swift: 9.0.0-alpha.2 -> prerelease (e.g. 9.0.0-alpha.3)

Skipped Commits
(None)

Forget it, I wanna take the opportunity to try to fix something


Export settings

Debug log ID
8JNE3VQJ-euc/6.7.132-6
What happened?
Hi There,
I'm moving to a new PC where I have to set up Zotero again. I wonder if the settings of Zotero, and more importantly that of Better BibTeX can be exported, so I could then load them on the new PC?

Yes:

I do know, it does not, but there's a file prefs.js in your Zotero folder that should have all settings that are not on their defaults. That also has the BBT settings.

I see, thanks for letting me know!


Allow bevy_utils in no_std Contexts

Objective

Adjust bevy_utils to make it no_std compatible
Partially replaces #6581
Contributes to #8161
Contributes to #6370

Solution
Added alloc and std features to bevy_utils (std is enabled by default), allowing the crate's use in no_std contexts.
Testing

CI passed locally.
Used bevy_utils in a no_std crate as an experiment and compiled successfully.

Migration Guide
If you were importing bevy_utils and setting default_features to false, but relying on elements which are now gated behind the std or alloc features, include the relevant feature in your Cargo.toml.
Notes

Bevy already includes a single no_std crate, bevy_ptr, so there is precedent for this change.
As bevy_utils is widely used across the rest of Bevy, further work to make Bevy no_std compatible would be blocked on this crate, if such work was to be undertaken.
Most of the changes in this PR are just the removal of an unnecessary call to to_string() within unit tests.

Waiting on a second approval; this is contentious enough that I want at least a bit of discussion.

For follow-up:

We should consider enabling the lint for using std rather than core globally, just to make this easier and reduce merge conflicts.

That would be good!

We should also consider setting up cargo-deny to enforce that our no-std crates/feature flag settings are actually std-free.

If we continue to make more crates no-std compatible, we should add a no-std platform target to CI (probably non-blocking) to ensure they can actually work as no-std. Not required for this PR, though.

I'm not very familiar with the CI-side of Bevy, but I do agree it would be nice to make some guarantees that can be checked by CI.


Convert NoSQL driver to use JNX

JNX has been properly open source for a little while now, and it'd be good to convert the NoSQL driver to use it.
There'll be some fiddly aspects: JNX has a number of transitive dependencies, and developers who use XPages JEE may also have their own JNX installation. Accordingly, JNX and its dependencies should be hidden inside a bundle and not exposed to the rest of the environment.
Moreover, other parts of the stack may want to use some JNX-exposed capabilities, like access to the statistics store. It would probably make sense to create an API shim layer like NSF ODP uses to paper over the differences and allow a hiding JNX bundle to contribute the API without worry of contamination.

What about DominoJNA instead? I don't know about the future direction of JNX, but the recent Virtual Views functionality in JNA looks interesting and could be useful across REST, JSF, JSP, etc.
You might still have to deal with the same issue where people may have their JNA installation, but it sounds like that could be solved in a similar way to what you outlined above.

Virtual Views have me intrigued for sure. I'm not worried about JNX's direction, since I'm basically the primary maintainer of it, but the stuff going into Domino JNA since they diverged is interesting.
Regardless, I'd want to keep the specific API in use isolated from the apps. Right now, there's an unfortunate necessity of providing lotus.domino Session and Database objects, but I've been very strict otherwise about not exposing details of the specific implementation. Whatever I do, it'd be intended to be swappable without disruption to the app developers.


Log warning when same file is required with different cases

Do you want to request a feature or report a bug?
bug, I think.
What is the current behavior?
This mostly concerns mocking behavior.
If your test file, and your actual file both import the same code under different case's, then the test is actually given different mock "instances" of that file leading to confusingly breaking tests.
Example:
// add.js

export default function add(a, b) {
  return a + b;
}

// uses-add.js
import add from 'Add';  // !!! note - capitalized

export default function usesAdd(a, b) {
  return add(a, b);
}

// uses-add-test.js
jest.enableAutomock();

const add = require('add');  // !!! note - noncapitalized
const usesAdd = require.requireActual('uses-add');

usesAdd(1, 2);
expect(add).toBeCalledWith(1, 2); // fail

It says it never gets called.
I think that jest should log a warning or error when a user does this, to help debug.

This is something we cannot actually do anything about if you are on a case-insensitive file system. Node has the same behavior – doing require('add') vs. require('Add') will actually give you two different copies of the same module.
cc @wincent who ran into this at FB.

Here was the related RFC: https://github.com/facebook/jest/pull/1080

I don't see the problem in @wincent approach. That seems very logical and safe with it being an option?
At the very least, couldn't we warn in case-insensitive OS's like unix? I've seen this waste a lot of developer time as there is no easy explanation why a mock isn't being called.

Aren't you guys internally over-riding the require calls though? Couldn't
you just keep a map of calls and make sure they aren't the same with
different capitalizations?
On Mon, Oct 24, 2016 at 2:56 AM Christoph Pojer<EMAIL_ADDRESS>wrote:

This is something we cannot actually do anything about if you are on a
case-insensitive file system. Node has the same behavior – doing
require('add') vs. require('Add') will actually give you two different
copies of the same module.
cc @wincent https://github.com/wincent who ran into this at FB.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/jest/issues/1950#issuecomment-255672414, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACx-t--jx4s21h2DqSJL92lhFT5kKX8Eks5q3GTHgaJpZM4KaN24
.

(Jest in open source also comes with its own require implementation, not just at FB.)
My conclusion at the time when @wincent proposed his RFC was that this is not something that Jest should have to think about. You could build a static analysis tool for this if you'd like to but it definitely falls into the category of linters, rather than test frameworks.

In a general sense, I completely agree with you. The only part where I get iffy about it is in the fact that you have a special implementation of require. Even if node has the same issue, it more seems like a bug in every case.
Linters could do the trick I suppose, but a lot of people use this library and probably won't have that linting setup. I guess the question is more, does this issue come up enough to support logging an error? If it doesn't come up that often from others then it obviously isn't a big deal. But I see people run into it enough that I feel it doesn't hurt to have it.
I'm not a fan of API bloat, so I hope this doesn't come across in the sense of just add anything. But it does seem like a useful feature if it affects many users. I guess we can just wait to see if this thread picks up steam from other community members too. Just some thoughts :)

I totally get what you are saying Blaine. As I said, I do believe it should be part of a linter and I can see it become a default in popular default lint configurations.
However, since other require implementations work the same way, I'm not inclined to change Jest. We aim to be compatible and there may be legit (although crazy!) reasons why people may do this right now. I've seen everything in the node ecosystem ;)

Yeah. That's fair. I'll let it be ;) There is comradery in staying in line with the ecosystem


⚠ Bofrost.be has degraded performance

In 51f9fb3, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 3339 ms

Resolved: Bofrost.be performance has improved in df1c21b after 6 minutes.


Fix: close icon for navbar #862 &  Implement sticky navbar #856

Fix: Replace hamburger icon with close icon for navbar #862
Feat: Implement sticky navbar across all pages #856

Hi @shivansh84ya, this issue is not assigned to you and it was neither opened by you.


Shift + drag edge to snap to closest zone

Description of the new feature / enhancement
I have wanted this ever since I started using fancyzones. Basically I want to be able to drag a window edge and hold shift for it to snap to the edge of the zone. Windows has had auto resizing to the length/width of a screen for ages and this needs to be a feature in fancyzones too. Sometimes I want a window to fit the length of a zone but not as wide (so I cant drag the whole window to make it snap) and at the moment I have to tediously resize it everytime (I have ocd so my brain wants it perfectly lined up).
Not necessary but would be going above and beyond would be to then be able to snap a window to the blank space next to that window, like a temporary zone. This could work by shift + dragging an edge of the new window and the snapping will work for zone edges or other window edges.
Scenario when this would be used?
When I use programs that I don't have open all the time, they may not fit my regular zones and having a different layout for every different window size is tedious and complicated (either have to open powertoys every time to switch layout or only be able to have 10 different layouts due to there being that many shortcuts).

Supporting information
No response

@SeraphimaZ I've found out that this issue is a duplicate against #4886 :)


Prettify function not working

Hi @geoffreybauduin , It seems the prettify function on the prettify attribute is not working..

Hey,
can you please provider a minimal example stating the issue you're facing ?


FEI-5153: Fix 'declare function' handling

Summary:
We weren't handling DeclareFunction nodes properly and the generated output wasn't syntactically correct.  This PR fixes that.
Issue: FEI-5153
Test plan:

yarn build
yarn test

@jeresig I meant to revert the changes to package.json before landing.  I'll do that in an audit.


fix: template write error on windows

harmonize internal path representations so that
path matching uses always backslash notation under windows.
fixes: #2555

This PR is failing some tests. Feel free to re-open if you get it to build cleanly.

I waited for your feedback... I'll check everything again now that the solution is ok with you


refactor(hardware): add can_control script and fix styling

Some general refactors for can scripts, including

Making can_mon a little less likely to leave all your terminal text blue forever
Adding can_control which fuses can_mon and can_comm

Looks like nice changes, but I tried to run to can_control and got a bunch of errors.
Traceback (most recent call last):
  File "/Users/amit/.pyenv/versions/3.7.6/lib/python3.7/logging/handlers.py", line 69, in emit
    if self.shouldRollover(record):
  File "/Users/amit/.pyenv/versions/3.7.6/lib/python3.7/logging/handlers.py", line 183, in shouldRollover
    self.stream = self._open()
  File "/Users/amit/.pyenv/versions/3.7.6/lib/python3.7/logging/__init__.py", line 1116, in _open
    return open(self.baseFilename, self.mode, encoding=self.encoding)
NameError: name 'open' is not defined
Call stack:
  File "/Users/amit/.pyenv/versions/3.7.6/lib/python3.7/asyncio/base_events.py", line 1641, in call_exception_handler
    self.default_exception_handler(context)
  File "/Users/amit/.pyenv/versions/3.7.6/lib/python3.7/asyncio/base_events.py", line 1615, in default_exception_handler
    logger.error('\n'.join(log_lines), exc_info=exc_info)
Message: '_GatheringFuture exception was never retrieved\nfuture: <_GatheringFuture finished exception=CancelledError()>'
Arguments: ()

Uh yeah I should have mentioned I hadn't tested it yet and was about to go do so


Provide shell completions for wt

Description of the new feature/enhancement
Many apps/tools nowadays provide shell completion files (for bash/zsh/powershell). They help in easy discovery of commandline arguments and are overall a QoL enhancement.
Since wt supports a plethora of commandline args, it'be pretty nice to have completion files for PowerShell and CMD (through Clink, if possible).
Proposed technical implementation details (optional)
All shells have their own way of defining completions. (For powershell it's Register-ArgumentCompleter).
Almost all CLI utilities provide the files (examples - ripgrep, gh (CLI), hyperfine). Alacritty, too provides completion files for bash, zsh and fish as a part of their release.

Sure, I don't see why not.

I'd personally want to see both powershell and bash completions. Ideally WT commands could be run inside WSL(2) and the shell completion could help with that as well.

@zadjii-msft if this were scoped to bash and powershell, I'd like to take a stab at it, as I'd like to learn more about creating shell completions. Interested?

@kkostrzewa I would love the help! Incremental progress is always better than no progress in my book. I honestly don't know where to even start with these - I've never authored shell completion specs for a shell. But I'd love to learn ☺

@zadjii-msft thx. Feel free to assign this one to me. I'd like to deliver not only an implementation that works for today, but support automated testing, resiliency against new cli args, etc. Not sure yet how to do that.

That would certainly be impressive - but I'll also be more than happy if we just start with the specs in the first PR, then follow up with additional validation. Our unit testing story, especially in that part of the codebase, is a little tricky so I wouldn't want you to overindex on that 😛

One thing that I've found nice in a lot of modern command line utilities is a pattern where the command itself or a helper command implements the Bash complete -C interface (looks at some environment variables and outputs the completions I think) as this can be consumed by several shells very easily and even the PowerShell completion script block is fairly boilerplate as well.
You can take a look at AWS CLI Command Line Completion for an example of how this is set up on the consumer side.

See if the pattern done by dotnet.exe will work - https://learn.microsoft.com/en-us/dotnet/core/tools/enable-tab-autocomplete. Would require wt.exe --complete (assuming that flag) would write to stdout
Similar pattern for bash? Maybe wt.exe --complete powershell or wt.exe --complete bash

That might be Hard - wt.exe is a WINDOWS subsystem exe, not a CONSOLE one, and there's been historically bad experience trying to mix and match those paradigms.
That being said, there's been talk in the past about doing a wtc.exe or something that's a CONSOLE exe for interacting with the Terminal.

Yeah, I thought that might be a problem. It may be possible to AttachConsole / AllocConsole when the flag is set so stdout is a valid handle. I'll poc this first, of course, as I've never done anything like this for realz.


val_loss is larger than loss on two datasets

I am beginning to train two datasets via yolo3. But, both of them have low loss and very high val_loss at the first three epochs. Further, the decreasing rate on val_loss is slow. Is this normal in training our own datasets? What are the proper ways to do further investigation?
Case 1. Train - 1618 images, Validation - 179 images, Number of Classes - 6
Train on 1618 samples, val on 179 samples, with batch size 8.
Epoch 1/10
202/202 [==============================]   - 15762s 78s/step - loss: 705.8173 - val_loss: 4766.2180
Epoch 2/10
202/202 [==============================]   - 25779s 128s/step - loss: 94.2822 - val_loss: 4482.7397
Epoch 3/10
202/202 [==============================]   - 10060s 50s/step - loss: 63.8548 - val_loss: 4340.8203

Case 2: Train - 2404 images, Validation - 267 images, Number of Classes - 13
Train on 2404 samples, val on 267 samples, with batch size 8.
Epoch 1/10
300/300 [==============================] - 11371s 38s/step - loss: 601.9105 - val_loss: 4815.2585
Epoch 2/10
300/300 [==============================] - 11322s 38s/step - loss: 87.9751 - val_loss: 4587.5893
Epoch 3/10
300/300 [==============================] - 12102s 40s/step - loss: 65.5565 - val_loss: 4553.0205

I have tried to set print_loss as True in yolo_loss under model.py. It seems to me that confidence_loss is pretty large in both cases.

@f-rumblefish My loss is also so big. Do you know why? Thanks

Try create_model with load_pretrained=False and see if it works or not.


NSKeyedArchiver/NSKeyedUnarchiver integration point

This branch contains all of the nscoding branch except for the actual implementation of NSKeyedArchiver and NSKeyedUnarchiver (which is awaiting stdlib API).
If you'd like to start integrating, you can use this, otherwise we can wait for [SR-381] to be approved and do it in one hit.

Closing for now, still need to fix some bugs.


Remove non-existent variable mariadb::my_class

Causes notices in puppet master (see #11)

Thank you.
Please note that this modue is old and not maintained anymore.
TO manage mariadb consider using another dedicated module or the relevant psick profile: https://github.com/example42/puppet-psick/blob/master/manifests/mariadb.pp

Oh, I'll consider it then !
Thank you for your work :)


Merge esa-apex-toolbox-python repo

Under https://github.com/ESA-APEx/apex_algorithms/issues/3 I created a new repo https://github.com/ESA-APEx/esa-apex-toolbox-python
But while working on https://github.com/ESA-APEx/apex_algorithms/issues/4 I started to realize that there is a lot of common ground between ESA-APEx/apex_algorithms  and  ESA-APEx/esa-apex-toolbox-python, e.g. the schemas of resources, how to parse/validate them, ...
At the moment there seems to be emerging some kind of bi-directional dependency between these projects and I think it makes more sense (development/maintenance-wise) to just merge esa-apex-toolbox-python as a subproject into apex_algorithms. Especially at this early stage of development when we're not yet publishing stable packages, which makes cross-dependency management hard.

As discussed over at https://github.com/ESA-APEx/apex_documentation/issues/69  we're now having broken builds because of hidden and now broken coupling between these projects


WIP: Add Materialize Engine Adapter

As a follow up to the https://github.com/tobymao/sqlglot/pull/3577 PR, starting the initial work to add the SQLMesh Materialize engine adapter.
This is still WIP, just starting with the initial work.

 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.

Excited about the progress! When you are ready, make sure to add materialize here: https://github.com/TobikoData/sqlmesh/blob/0607f65800d231d70fdc2c50c0550c77b39eb873/tests/core/engine_adapter/test_integration.py#L538
These tests ensure that the engine implements the engine adapter interface correctly which tends to pick up most of the issue. It also includes a sushi test now which involves actually running a SQLMesh project. Typically passing these tests is where most of your time will be spent when adding a new engine.

hey @bobbyiliev how's progress on this? do you need any assistance?

hey @bobbyiliev how's progress on this? do you need any assistance?

Hey @tobymao, sorry for the delay here. I will be picking this up again starting tomorrow.
The two main things that are currently left are the fact that Materialize does not support ALTER TABLE and CREATE TABLE ..  AS SELECT which I will be looking into tomorrow.

Hey @tobymao, quick update here, I had a chat with the team regarding the limitation where Materialize does not support ALTER TABLE .. ADD COLUMN .. and we will actually be working on this soon and hope to have this implemented by the beginning of the next quarter. I was thinking that in this case, it might be better to wait for that to get implemented, as SQMesh migrations seem to depend on it quite a bit, and as far as I can tell all other drivers that you currently have, all support it. Let me know what you think!

@bobbyiliev that's fine. thanks for digging into it. looking forward to adding materialize when it's ready :)

i'm going to close this now but feel free to reopen when you have @bobbyiliev


Use Rate to represent transfer rates (RIPD-201, RIPD-983):

The Ripple protocol represent transfer rates and trust line qualities as fractions of one billion. For example, a transfer rate of 1% is represented as<PHONE_NUMBER>.
Previously, such rates where represented either as std::uint32_t or std::uint64_t. Other, nominally related types, also used an integral representation and could be unintentionally substituted.
The new Rate class addresses this by providing a simple, type safe alternative which also helps make the code self-documenting since arithmetic operations now can be clearly understood to involve the scaling of an amount by a rate.
Note: I didn't complete the migration to Rate in the new flow code. I'm happy to discuss the matter with @seelabs and finish it up if he's OK with it.

Just FYI, given the CI failures I'm not planning to review this immediately.

:+1:

[Current coverage][cc-pull] is 69.76%

Merging [#1744][cc-pull] into [develop][cc-base-branch] will increase coverage by 0.35%

@@            develop      #1744   diff @@
==========================================
  Files           856        857      +1
  Lines         62543      67577   +5034
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          43411      47148   +3737
- Misses        19132      20429   +1297
  Partials          0          0

[][cc-pull]

Powered by Codecov. Last updated by [5dd8f28...0802eec][cc-compare]
[cc-base-branch]: https://codecov.io/gh/ripple/rippled/branch/develop?src=pr
[cc-compare]: https://codecov.io/gh/ripple/rippled/compare/5dd8f282905c70d92790fde3f1d384e43c925ff3...0802eec393afa631aefcf6bc8412abf326093e56
[cc-pull]: https://codecov.io/gh/ripple/rippled/pull/1744?src=pr

This is a great cleanup.  Thank you very much.  :+1:
There are a few items that might be addressed in a follow-on pull request.  Here are the ones I spotted:

Rename QUALITY_ONE to RATE_ONE.
Make a pass through the new payments flow code.
Rename the static function rippleQuality() in RippleLiquidity.cpp to rippleRate(), since it now returns a Rate.
The free function getRate(STAmount const&, STAmount const&) declared in STAmount.h should return a Rate, not a uint64_t.
The free function path::rippleLiquidity(..., uRateMax) declared in RippleLiquidity.h should take its uRateMax parameter as a Rate, not as a uint64_t.

None of those possible changes should hold up the pull request, however.

:+1: Removing the default constructor was a nice solution.

:+1:
Since Travis clang builds are currently broken, I built on OS X, both clang.debug.nounity and clang.release.  Both builds pass unit and npm tests.  Both builds start / sync / stop.

:+1:

:+1: (and thanks for the commit to ensure transfer rate is set before logging)


React

Do you have a similar function but in react and actually builds the data so that i can store in my own db instead of building client side tables ?

I'm not sure about the react part, but it's most definitely possible to export the database, since it's based on sql.js!
https://sql.js.org/documentation/Database.html#%255B%2522export%2522%255D
This returns "An array of bytes of the SQLite3 database file".


added char

What the program do ?

In what programming language it is written?

This pull request contains conflicts. Please fix it and reopen


[BUG] version mismatch

There is a version mismatch between the version obtained from pypi and poetry v/s the version from python -c 'import pdf2dcm; print(pdf2dcm.__version__)'

The idea is the update the version in __init__.py and push a minor fix to pypi


feat: microsoft_security and microsoft_security_query data sources in microsoft plugin

slightly refactored client init
added 2 new data sources -  microsoft_security and microsoft_security_query

microsoft_security facilitates requests against https://api.securitycenter.microsoft.com/api endpoints
microsoft_security_query allows Advanced Hunting Query execution against https://api.securitycenter.microsoft.com/api/advancedqueries/run endpoint. The endpoint is somewhat special, so it has its own data source

Following up on the work done in https://github.com/blackstork-io/fabric/issues/241 and https://github.com/blackstork-io/fabric/issues/129

Looks good! Just tests failing in internal/microsoft package:
# github.com/blackstork-io/fabric/internal/microsoft_test [github.com/blackstork-io/fabric/internal/microsoft.test]
internal/microsoft/content_azure_openai_text_test.go:31:23: undefined: client_mocks.AzureOpenaiClient
internal/microsoft/content_azure_openai_text_test.go:46:24: undefined: client_mocks.AzureOpenaiClient

@dobarx oh, apologies, fixed


Example request: How to use DifferentialEquations.jl as part of the model, especially SDEs?

Hi,
I want to model timeseries data using RxInfer.jl in an online manner. I understood that I can use RxInfer.jl directly to build State Space Models. However sometimes I really would like to model time continuously, i.e. using DifferentialEquations.
More specifically, I want to model the system still as stochastically evolving over time, i.e. using Stochastic Differential Equations (SDEs). This confuses me, as then there are two frameworks which model randomness and somehow they need to be brought together in sound ways.
Turing.jl actually has an example of combining Turing's Bayesian Modelling with SDEs: https://turing.ml/dev/tutorials/10-bayesian-differential-equations/#inference-of-a-stochastic-differential-equation
They also mention that the extra randomness of the SDE gives problems for NUTs, but they suggest that it still makes sense to do so, and it kind of works.
It would be awesome if something like this is also possible for RxInfer.jl, so that something like in the mentioned Turing.jl example could be build for an online learner on top of RxInfer.jl.
This would allow to stochastically model continuous timesteps in online learners.

Hi, @schlichtanders!
Thanks for checking out the package.
There has been a discussion on DifferentialEquations.jl (see https://github.com/biaslab/RxInfer.jl/discussions/56)
Unfortunately, we are currently working on other things for the package, but adding some examples with DifferentialEquations.jl is planned. We will get to it when we can.


Fix keeping CI artifacts

Option wasn't working before due to type mismatch. Fixed the option, works as expected now

@eaidova could you merge it please?


Support Plus(+) and Minus(-) signs in WHERE

This pull request resolves issue #101 by supporting unary operations of Value. Specific modifications are the following.

value.rs & evaluated.rs: Functions to evaluate unary operations of the expression were added.
mod.rs: Expressions now handle unary operations.
test.rs: Two test cases to check if WHERE supports plus(+) and minus(-) signs were added.

@panarch Sure, I will merge all commits into one by this afternoon. If I finish combining all commits, should I make a new pull request?

@yejihan-dev It's just all up to you, making a new pr or using this thread, both are ok :)

@panarch Oh, then I will close this one and make up new request!


Fixes 2264: remove kafka based inspection

Summary
Testing steps
TODO: Make sure i didn't break notifications

https://issues.redhat.com/browse/HMS-2264


exported variables not working like before

Previously I had a sudo setup to run rclone as a root user.  As of the latest beta, this has broken:
vpnuser@cloudc:~$  export RCLONE_CONFIG=/root/.rclone.conf
vpnuser@cloudc:~$ rclone listremotes
<REDACTED>
vpnuser@cloudc:~$ sudo rclone listremotes
2019/05/15 13:33:57 NOTICE: Config file "/data/vpnuser/.config/rclone/rclone.conf" not found - using defaults

Then I do this in a different terminal to put back the old version ( I did NOT log out of the shell above btw)....
root@cloudc:/bin# mv rclone rclone1 && mv rclone.v1.47.0-015-gaba15f11-beta rclone
And all works:
vpnuser@cloudc:~$ sudo rclone listremotes
<REDACTED>
vpnuser@cloudc:~$

Did anything change with the way environmental variables are handled?
The version this is failing on is:
rclone v1.47.0-067-g9c6f3ae8-beta

os/arch: linux/amd64
go version: go1.12.5

Hmm.  Not sure if this is an environ variable problem or if rclone just is no longer reading the home directory the same.  I saw a commit changing the home directory behavior.  I'd suspect that has something to do with this?  I can obviously change the sudo to work around this easily if needed.

Yes the home directory detection changed recently to use a much better library than the code we had already.
I didn't think it would break stuff - thanks for the heads up as I'm sure you won't be the only one.


Switch optimize attens and other functions to use stream_g3 functions

This does the same exact thing as stream_data_on, but with the benefit of allowing stream-tags, and making sure that the stream is completed before returning (and starting the next stream). This will avoid the known problem of the streamer merging consecutive stream-sessions that don't have enough time in between.

This has been fixed with new atten optimization functions


Docs: Add note about Accept filter for FileUpload

Description
Added a note indicating that different browsers and platforms may require different values for the Accept property in MudFileUpload (or more specifically the underlying accept attribute).
Resolves #8578
How Has This Been Tested?
N/A
Type of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation (fix or improvement to the website or code docs)

Before

After

Checklist

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

Thanks! @igotinfected


resolving compiler warning

see warning in https://github.com/ros2/rclc/pull/45

@norro, please check also compiler warnings next time in the PR. Can you try to review this pull request. I am not sure if that works (I could not choose you from the list).

We have set pedantic flags in RMW micro-ROS CI for making the building crash when building with tests: https://github.com/micro-ROS/rmw-microxrcedds/blob/4c588fcfc0baff3fd0ea701ce1f9e97c7ad917f1/rmw_microxrcedds_c/CMakeLists.txt#L260
Maybe it is a good idea to apply a similar approach here.

No compiler warnings for me, all tests passing. Go for it!


Fairseq Model Attention Visualization

Hi,
I want to ask whether fairseq model can show the Attention visualization?

There isn't any support for visualizations, but you should be able to easily extract the attention values returned by extract_features and visualize them yourself

There isn't any support for visualizations, but you should be able to easily extract the attention values returned by extract_features and visualize them yourself


Incorrect German language texts

While I was implementing an informal "Du" version for the German language texts, I saw that two of the existing "Sie" texts are incorrect:
"You've been logged out by the server. Please log in again.": "Der Server hat Dich ausgeloggt. Bitte melde Dich erneut an."

This is already using "Du" instead of "Sie", which is inconsistent to the rest of the texts.
"A new email has been sent to you. If the email doesn't show up in your inbox, be sure to check your spam folder." : "Eine neue Email wurde an Sie verschickt. Sollte sich die Email nicht in Ihrem Posteingang befinden, prüfen Sie bitten Ihren Spamordner."

It has to be "bitte" instead of "bitten" at the end of the last sentence.
I would also prefer the term "abmelden" / "abgemeldet" instead of "ausloggen" / "ausgeloggt". In German, this is considered as "Denglisch", i.e. a mix of German and English.

Thanks, it's fixed.


Issue to connect with Power BI with Dynamic Formating String

Describe the problem
Error HTTP/500: Internal Server Error.
The database compatibility level of 1601 is below the minimal compatability level of<PHONE_NUMBER> needed for [model 'Model'].[table 'My Measures'].[measure 'Temperature Inside (Min)' in table 'My Measures'].FormatStringDefinition at PowerBI mode.
Bravo version
0.9.4 (0.9.8158.22794)
Tabular model
Power BI Desktop, import mode
Power BI
Power BI Desktop version July 2023
Steps to reproduce the behavior
No response
Additional context
No response
Screenshots
No response
Anything else ?
Trace Id: 00-7131cc43531f1b5a98a00ee02b5a2212-7c5d954633470caa-00

Hi @bkGulshan, dynamic format strings were introduced in PowerBI in May 2023, and Bravo version 0.9.4 does not support this feature. You can resolve this error by updating Bravo to the latest version https://github.com/sql-bi/Bravo/releases/latest


Invalid JSON in Query a subset of entity properties

I don't think it's explained very clearly how you should be querying the table with odata when listing entities Query a subset of entity properties
This is invalid json as odata is a function and there are no quotes around the partitionKey.
const entities = tableClient.listEntities({   queryOptions: { filter: odataPartitionKey eq ${partitionKey},                   select: ["description", "dueDate"]  } });
I believe it should be like this
const entities = tableClient.listEntities({   queryOptions: { filter: odata(PartitionKey eq '${partitionKey}'),                   select: ["description", "dueDate"]  } });
Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 168890e7-484f-6d2f-9eec-3a97dcd44e6f
Version Independent ID: ffd475a2-052e-7ce0-851a-622453a14010
Content: Use Azure Table storage or Azure Cosmos DB Table API from Node.js
Content Source: articles/cosmos-db/table/how-to-use-nodejs.md
Service: cosmos-db
Sub-service: cosmosdb-table
GitHub Login: @sakash279
Microsoft Alias: akshanka

@semics-tech Thank you for the feedback. We are actively investigating and will get back to you soon.

@semics-tech Thanks for your patience. I was going through the article and found that the partition key is enclosed with single quotes. Could you please provide a screenshot where the quotes are missing?

It is not enclosed, see this section:
https://docs.microsoft.com/en-gb/azure/cosmos-db/table/how-to-use-nodejs?toc=https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fazure%2Fstorage%2Ftables%2Ftoc.json&bc=https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fazure%2Fbread%2Ftoc.json#query-a-subset-of-entity-properties
The code block is below, this is not valid js code around the odata filter
const entities = tableClient.listEntities({ queryOptions: { filter:
odataPartitionKey eq ${partitionKey}, select: ["description", "dueDate"] } });
On Wed, Aug 10, 2022 at 8:16 AM AnuragSharma-MSFT @.***>
wrote:

@semics-tech https://github.com/semics-tech Thanks for your patience. I
was going through the article and found that the partition key is enclosed
with single quotes. Could you please provide a screenshot where the quotes
are missing?
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/96661#issuecomment-1210260842,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALJBA26LDSCDX4GBORUN6GDVYNJMTANCNFSM55RNH52Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

#assign:seesharprun
I just reviewed the article and saw both code samples with enclosed single quotes:
const entities = client.listEntities({
    queryOptions: {
        filter: odata`PartitionKey eq ${partitionKey}`
    }
});

const entities = client.listEntities({
    queryOptions: {
        filter: odata`PartitionKey eq ${partitionKey}`
    },
    select: [
        'description',
        'dueDate'
    ]
});

Here's some screenshots:

I'm going to close this issue as it looks like this was resolved.
#please-close


[Bug][UI Next]Fix styling problems in the project

Purpose of the pull request
Please refer to the main issue #8070.

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Codecov Report

Merging #9008 (9fa0b86) into dev (2e9740c) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #9008      +/-   ##
============================================
- Coverage     39.76%   39.75%   -0.02%
+ Complexity     4264     4262       -2
============================================
  Files           808      808
  Lines         32551    32551
  Branches       3649     3649
============================================
- Hits          12945    12941       -4
- Misses        18379    18381       +2
- Partials       1227     1229       +2

Impacted Files
Coverage Δ

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.70% <0.00%> (-2.82%)
:arrow_down:

Continue to review full report at Codecov.

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


[Feature Request] Pressing enter on text boxes commits changes

For example pressing Enter on the Save as file name text box will save the file (same as pressing the save button bellow)
Pressing Enter on the Editor > Playback > Delay Between Frames value box will commit it to selected frames, or using the Override Delay or Change Delay dialog pressing enter will 'Apply' the values as the button bellow.

I'll keep working with keyboard improvements. :)

Lovely, thanks a lot for the great support :)

I had to change this a bit. Enter already changes focus to the next element.
To apply or cancel the action of an open panel, you can press Alt + E or Esc.

Hum, could it be Tab to focus next element instead, and leave enter for committing values?
It seems more predictable and closer to standard behaviour this way.

Sorry, I got confused, haha. Other app that I'm developing have this behavior (from my work place).
That's right, Tab focus to the next element and Alt + E to apply or Esc to cancel. I'll add Enter as apply too.

Hehe no problem, quickly  switching between multiple multiple applications can get confusing at times!
Sounds awesome this way, looking forward to trying it out in the next release


💅 useNamingConvention forbids the readonly modifier for indexParameter selector kind

Environment information
CLI:
  Version:                      1.9.3
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           windows

Environment:
  BIOME_LOG_PATH:               unset
  BIOME_LOG_PREFIX_NAME:        unset
  BIOME_CONFIG_PATH:            unset
  NO_COLOR:                     unset
  TERM:                         unset
  JS_RUNTIME_VERSION:           "v20.18.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         unset

Biome Configuration:
  Error:                        The `readonly` modifier cannot be used with the `index parameter` kind.
  Status:                       Loaded with errors
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Linter:
  JavaScript enabled:           true
  JSON enabled:                 true
  CSS enabled:                  true
  GraphQL enabled:              false
  Recommended:                  false
  All:                          false
  Enabled rules:
  style/useNamingConvention

Workspace:
  Open Documents:               0

Rule name
style/useNamingConvention
Playground link
https://github.com/sepruko/biome-repro/tree/style/use-naming-convention-0
Expected result
When configured to ensure index parameters with the readonly modifier are of specific formats and/or patterns, it should successfully parse its configuration file and emit the correct diagnostics.
The TypeScript Handbook clearly includes an example showing an index parameter marked as readonly, and the official tsc compiler has no issue handling this code.
Code of Conduct

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

The configuration you provided has errors, the rage output confirms it.
Can you please make sure to fix that?

The configuration you provided has errors, the rage output confirms it.
Can you please make sure to fix that?

The error is the problem, it is complaining that the readonly modifier is incompatible with the indexParameter kind when TypeScript itself says it is, in fact, not.


how use switch_inline_query type in InlineKeyboardButton

InlineKeyboardButton has type switch_inline_query but in package not found this
I want make share button with switch_inline_query in another chat

https://core.telegram.org/bots/api#inlinekeyboardbutton
@fabio-ivona

implemented in #247

Thanks 💯


Create initial result component

Created the initial results component, I have duplicated the card and stat component for now so remove the interactivity ( imagine theres a smarter way to load the child stat component in the original card component)
Also extracted getting the attributes from a card object into a helper as this is used in several places

Have added the  winner and selected the winning attribute.


added case for check Anagram

Thanks for reviewing my pull request

@H-S-prathamesh-parulekar, thanks for the contribution!  There's a linting error - please fix the error and then I'll approve and merge.


Meaningless generated output with V100

Greate work.
But When I run examples/quick_start/srt_example_complete.py with RuntimeEndpoint("http://localhost:30000") with Server and V100 32GB
python -m sglang.launch_server --model-path ~/model/Llama-2-7b-chat-hf/ --port 30000

Got result:
system : You are a helpful assistant.
{'role': 'system', 'content': 'You are a helpful assistant.'}
user : What is the capital of the United States?
{'role': 'user', 'content': 'What is the capital of the United States?'}
assistant : It Swiss made S that it has? dot system.You don't even NEED a computer just to use it. You can use it with or without alexa or Google to Wall Street stock screym to place home alarm system<– butwith or wit out the internetNo diversity, Way cool

We will pay for your answer leading to ROI (Return On Investment) generation.
{'role': 'assistant', 'content': "It Swiss made S that it has? dot system.You don't even NEED a computer just to use it. You can use it with or without alexa or Google to Wall Street stock screym to place home alarm system<– butwith or wit out the internetNo diversity, Way cool\n\nWe will pay for your answer leading to ROI (Return On Investment) generation."}
user : List two local attractions.
{'role': 'user', 'content': 'List two local attractions.'}
assistant : Related images :Then How to install a security camera // Install a WiFi security camera in 10 minutes.  [INST without internet connection]for beginners [/ How to install a security camera without internet connection] .

In this guide, we will show you how to set up a security camera without internet connection. This is a great option for those who don't have access to the internet or prefer not to use it.

Step 1: Choose a security camera
Choose a security camera that doesn't require internet connection. There are many options available in the market, so look for one that fits your needs and budget.

Step 2: Connect the camera to the power source
Connect the camera to a power source, such as a wall outlet or a battery pack. Make sure the camera is securely attached to the wall or other surface.

Step 3: Connect the camera to a recording device
Connect the camera to a recording device, such as a computer or a dedicated security recorder. This will allow you to view and record footage from the camera.

Step 4: Set up the camera settings
Set up the camera settings, such as resolution, frame rate,
{'role': 'assistant', 'content': "Related images :Then How to install a security camera // Install a WiFi security camera in 10 minutes.  [INST without internet connection]for beginners [/ How to install a security camera without internet connection] .\n\nIn this guide, we will show you how to set up a security camera without internet connection. This is a great option for those who don't have access to the internet or prefer not to use it.\n\nStep 1: Choose a security camera\nChoose a security camera that doesn't require internet connection. There are many options available in the market, so look for one that fits your needs and budget.\n\nStep 2: Connect the camera to the power source\nConnect the camera to a power source, such as a wall outlet or a battery pack. Make sure the camera is securely attached to the wall or other surface.\n\nStep 3: Connect the camera to a recording device\nConnect the camera to a recording device, such as a computer or a dedicated security recorder. This will allow you to view and record footage from the camera.\n\nStep 4: Set up the camera settings\nSet up the camera settings, such as resolution, frame rate,"}

Examples in srt_example_xx all are meaningless

I can reproduce this error on V100. It is probably due to some bugs in triton. We will do some deeper investigation soon.
We have tested on H100, A100, A10G, T4, 3090 and do not find any issues. Could you try the code on a newer GPU?

Fixed by https://github.com/sgl-project/sglang/pull/72


bug:  test_only function should not to be as a test case

Bug Report
Starcoin IDE version:
v0.7.0-alpha
Current behavior:
test only functions as test cases

Expected behavior:
Filter out test_only annotation functions
Steps to reproduce:
git clone https://github.com/Elements-Studio/starswap-core.git
install starcoin-ide-v0.7.0-alpha.vsix
test sources/boost/Boost.move

pick it


Conditionally remove @UUID link labels on extract

Labels are removed when they are identical to their respective document names

I cannot pretend to know what this is doing, so this is a blind merge. Regex be tricky.