Missing commandlet mapping for DirectorySetting and DirectorySettingTemplate

The doc is missing the mapping for the following AzureAD commandlet for both DirectorySetting and DirectorySettingTemplate:
Get-AzureADDirectorySetting
Get-AzureADDirectorySettingTemplate
New-AzureADDirectorySetting
Remove-AzureADDirectorySetting
Set-AzureADDirectorySetting

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

ID: dada1864-4eb3-a28d-7894-af6d352a0f54
Version Independent ID: 4f4e8d2f-85ad-06bd-aee2-797f2b921a0a
Content: Find Azure AD and MSOnline cmdlets in Microsoft Graph PowerShell
Content Source: microsoftgraph/docs-conceptual/azuread-msoline-cmdlet-map.md
Product: non-product-specific
Technology: microsoft-graph-powershell
GitHub Login: @msewaweru
Microsoft Alias: eunicewaweru

Hi @bachoang - thanks for highlighting this.
This set of cmdlets fall under the Azure AD Preview module, whose map is currently work in progress. We should have a map for Azure AD Preview cmdlets in the coming weeks. Thanks.


Error: unable to show help on sites or addons with Volta

- Do you want to request a feature or report a bug?
Bug 🐛
- What is the current behavior?
Some commands like sites or addons don't show help by default on 2.23.0 when installed through https://volta.sh
- If the current behavior is a bug, please provide the steps to reproduce.
curl https://get.volta.sh | bash
volta install netlify-cli
netlify sites
/bin/sh: netlify: command not found
Error: Command failed: netlify sites --help
    at showHelp (~/.volta/tools/image/packages/netlify-cli/2.23.0/src/utils/show-help.js:4:3)
    at SitesCommand.run (~/.volta/tools/image/packages/netlify-cli/2.23.0/src/commands/sites/index.js:11:7)
    at SitesCommand._run (~/.volta/tools/image/packages/netlify-cli/2.23.0/node_modules/@oclif/command/lib/command.js:44:31)
netlify addons
netlify addons
/bin/sh: netlify: command not found
Error: Command failed: netlify addons --help
    at showHelp (~/.volta/tools/image/packages/netlify-cli/2.23.0/src/utils/show-help.js:4:3)
    at AddonsCommand.run (~/.volta/tools/image/packages/netlify-cli/2.23.0/src/commands/addons/index.js:11:7)
    at AddonsCommand._run (~/.volta/tools/image/packages/netlify-cli/2.23.0/node_modules/@oclif/command/lib/command.js:44:31)

- What is the expected behavior?
show help
- Local Environment Information
System:
OS: macOS 10.15.1
CPU: (4) x64 Intel(R) Core(TM) i5-8210Y CPU @ 1.60GHz
Binaries:
Node: 12.13.1 - ~/.volta/tools/image/node/12.13.1/6.12.1/bin/node
Yarn: 1.19.0 - ~/.volta/tools/image/yarn/1.19.0/bin/yarn
npm: 6.12.1 - ~/.volta/tools/image/node/12.13.1/6.12.1/bin/npm

Is the CLI installed locally in your project or globally on the machine?

Globally through https://volta.sh

Interesting. How do you install the CLI via https://volta.sh
Sounds like the CLI bin path is wrong when installing that way

More specifically when showHelp is called, we shell out to the globally installed netlify binary here https://github.com/netlify/cli/blob/0de2228ef2002a8ef7a85923570a3d4e6c64b134/src/utils/show-help.js#L4
I'm unfamiliar with volta.sh, is it installing things in a special way?
Follow up, is it possible to just install via npm with npm install netlify-cli -g ?

Volta does not support global install for now (it's kind of the point of Volta).
@charlespierce would know better how Volta install things.

Hi @DirtyF @DavidWells This is almost assuredly an issue with Volta itself, and not netlify-cli. One of our bigger remaining pain points at the moment is global tools calling global tools, see https://github.com/volta-cli/volta/issues/492
To clarify so I have the full context, the netlify command here shells out to itself (with the --help flag added) in these situations?

netlify addons --> netlify addons --help

Okay, thanks for clarifying! Given that, this is definitely the same issue as described in https://github.com/volta-cli/volta/issues/492 above, an issue within Volta itself. I think this is the first use-case I've seen where a tool calls itself through the command-line, but that would result in the same behavior we've seen when tools call other tools.
@DavidWells This shouldn't need any changes on the netlify-cli side.


bsky shows inaccurate relative times if the clock on the host is set incorrectly

Describe the bug

If the time zones on the host are set wrong, bsky will show "N hours ago" instead of "ten seconds ago" or "now" immediately after a post is created.
To Reproduce
Steps to reproduce the behavior:

Set the time and date manually into the future in Windows 10:

Make a new post (or just look at an existing post, they have the bug too)
Observe that all posts show the relative time as "now".

Expected behavior
bsky should either show the absolute time or an accurate relative time.
Screenshots
This shows "now" when it should really show "1 hour ago" (notice "8:17 AM" in the bottom right, although I took the screenshot at 11:17 EST).

Details

Platform: Desktop Firefox Windows
Platform version: Firefox 119.0, Windows 10 (not sure the patch version, can look it up if you care)
App version: Build version: 1.55.0; Platform: web

Additional context
I first hit this because dual-booting Linux and Windows screws up the CMOS time (Windows treats it as time-zone aware whereas linux treats it as UTC).
Note that this is not specific to setting the time into the future; manually setting it to sometime in the past also shows wrong relative times.

lol

here's a possible way this could be fixed:

server returns the current time
client records the current time according to the host and measures the difference
it adds that difference every time it calls Date.now() to update the relative times

then you can still update in real-time, but it's accurate (or at least, as accurate as the ticks on the host, which hopefully are harder to break than timezones).

We do need to make sure that trusted timestamps are being used (aka the appview) but if the client has it's clock wrong, isn't this a somewhat fruitless effort? I don't want to try to implement a clock sync to the client

yes, that makes sense. i no longer have this problem, i figured out how to get linux's system clock to be timezone-aware.


Remove System.register from UMD header

This PR removes System.register from the UMD header of tslib.js in favor of System's built in module format detection. This fixes an issue with how tslib.js loads when running inside of JSPM/SystemJS.
Fixes: https://github.com/Microsoft/TypeScript/issues/12887

@DanielRosenwasser can you publish an update to npm?

@rbuckton Just FYI, the global System is currently slated to be removed so as to not conflict with then System global proposed in TC39.
The current recommendation is to use the SystemJS global. This shouldn't affect module emit, at least for the time being, as a wrapper providing both names is currently injected.
You can see SystemJS rename to window.SystemJS over window.System for details.
Thanks! ❤

@rbuckton Just FYI, the global System is currently slated to be removed so as to not conflict with then System global proposed in TC39.
The current recommendation is to use the SystemJS global. This shouldn't affect module emit, at least for the time being, as a wrapper providing both names is currently injected.
You can see SystemJS rename to window.SystemJS over window.System for details.
Thanks! ❤


fix project avatars image src

closes #207 as the API now returns the project image avatar URL with the scheme (https) we can use this instead of // relative URL from the domain.

Hey @camallen -- I'm still seeing this issue persisting in ALICE with PFE projects (not FEM). Have cleared my cache, etc. Perhaps I'm missing a step?

Hey @camallen -- I'm still seeing this issue persisting in ALICE with PFE projects (not FEM). Have cleared my cache, etc. Perhaps I'm missing a step?

Wait, @snblickhan I think this one's on me - I need to manually deploy the project.

I merged 208 intending to deploy...
Then I realised I needed to update the React Scripts (#209), I decided to get that in before I deployed...
Then 209 turned out to be a bigger problem than expected and has been on hold

I'm reverting my code to pre-209 dependencies and deploying now. brb

Wait, @snblickhan I think this one's on me - I need to manually deploy the project.

I merged 208 intending to deploy...
Then I realised I needed to update the React Scripts (#209), I decided to get that in before I deployed...
Then 209 turned out to be a bigger problem than expected and has been on hold

I'm reverting my code to pre-209 dependencies and deploying now. brb

@snblickhan Awright, give it a go now! https://alice.zooniverse.org/

@snblickhan Awright, give it a go now! https://alice.zooniverse.org/

@shaunanoordin Can confirm it is now working! Thank you!

@shaunanoordin Can confirm it is now working! Thank you!


New package: Blizzard.BattleNet version <IP_ADDRESS>41

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Verify:

Hi @SkylerWallace,
This application displays <IP_ADDRESS>56, and the installer doesn't write a version number to the Registry. Should this version number be used instead of the current <IP_ADDRESS>41?

Verify:
Hi @SkylerWallace,
This application displays <IP_ADDRESS>56, and the installer doesn't write a version number to the Registry. Should this version number be used instead of the current <IP_ADDRESS>41?

The installer file is <IP_ADDRESS>41. This installer seems to update the launcher to the latest version; Blizzard has a "live" client.
I think having the version number set to <IP_ADDRESS>41 is most accurate for this.

Verify:


feat: new commands for VPC configurations

Two new sub-commands:
neonctl vpc-endpoints org

Manage VPC endpoints

Commands:
  neonctl vpc-endpoints org list         List configured VPC endpoints for this organization
  neonctl vpc-endpoints org assign <id>  Add or update a VPC endpoint for this organization  [aliases: update, add]
  neonctl vpc-endpoints org remove <id>  Remove a VPC endpoint from this organization
  neonctl vpc-endpoints org status <id>  Get the status of a VPC endpoint for this organization

Options:
      --org-id        Organization ID  [string]
      --region-id     The region ID. Possible values: aws-us-west-2, aws-ap-southeast-1, aws-ap-southeast-2, aws-eu-central-1, aws-us-east-2, aws-us-east-1, azure-eastus2  [string] [required]

(If the org ID is omitted, but the user has only 1 org, then that org is used.)
and
neonctl vpc-endpoints project

Manage project-level VPC endpoint restrictions

Commands:
  neonctl vpc-endpoints project list         List VPC endpoint restrictions for this project
  neonctl vpc-endpoints project assign <id>  Add or update a VPC endpoint restriction for this project  [aliases: update, add]
  neonctl vpc-endpoints project remove <id>  Remove a VPC endpoint restriction from this project

Options:
      --project-id    Project ID  [string]

(If the project ID is omitted, but the user has only 1 project, then that project is used.)
For example:
% neonctl vpc-endpoints org status --region-id azure-eastus2 vpc-test12
┌─────────────────┬───────┬───────┬─────────────────────────┬─────────────────────────────┐
│ Vpc Endpoint Id │ Label │ State │ Num Restricted Projects │ Example Restricted Projects │
├─────────────────┼───────┼───────┼─────────────────────────┼─────────────────────────────┤
│ vpc-test12      │ test  │ new   │ 0                       │                             │
└─────────────────┴───────┴───────┴─────────────────────────┴─────────────────────────────┘

Depends on #303,
https://github.com/neondatabase/cloud/pull/21842
and also another PR (yet to be drafted) to upgrade the api-client in neonctl once more.
Fixes https://github.com/neondatabase/cloud/issues/21840
Informs https://github.com/neondatabase/cloud/issues/18315

Slack convo: https://neondb.slack.com/archives/C07DJTH0YHK/p1734357879707389?thread_ts=1734349106.090229&cid=C07DJTH0YHK

We need to get an id somewhere? IMO it makes CLI usecase not very useful

The customer has to provide the ID themselves (on their side) see
https://neon.tech/docs/guides/neon-private-networking
I'll add a doc link.


Subtitles downloaded without a match on TV series name even though correct title in filename

I've noticed that for some TV series, the wrong subtitles get downloaded. When looking at the extra verbose output I can clearly see that Subliminal couldn't match on the TV series name, which in this case exists in the filename as "Into.the.Badlands".

I tried adding the release year to the filename, so the TV series name instead would read as "Into.the.Badlands.2015". When running Subliminal on this name the name of the TV series could be matched and the correct subtitles gets downloaded.

The hash matching, which I know have been a problem in several other issues here at Github before, is not the issue here. During my testing I got the same problem on the real video file, as well as a blank text file only renamed to "Into.the.Badlands.S02E01.Tiger.Pushes.Mountain.WEBDL-1080p.x264.AC3.tt3865236-RARBG.mkv", to force the match on filename.
The problem here is simply that the release year is needed in the filename for making the match on the TV series name, which is a problem since the TV series name is simply "Into the Badlands", without the release year in the title, on e.g. The TVDB. This simply makes it impossible right now to rename the file automatically with for instance Sonarr, as the release year cannot be forced into the filename during renaming.
I don't know if the fact that two older movies with the title "Into the Badlands" exist on IMDB causes this problem, but Subliminal does recognize both episode and season from the filename, so I think a match should only be made towards TV series anyway.

This seems to not be a problem anymore in latest develop:
DEBUG:subliminal.cli:Collecting path Into.the.Badlands.S02E01.Tiger.Pushes.Mountain.WEBDL-1080p.x264.AC3.tt3865236-RARBG.mkv
DEBUG:subliminal.core:Found subtitles {}
INFO:subliminal.core:Refining video with hash
WARNING:subliminal.refiners.hash:Size is lower than 10MB: hashes not computed
INFO:subliminal.core:Refining video with metadata
INFO:subliminal.core:Refining video with tvdb
INFO:subliminal.refiners.tvdb:Searching series 'Into the Badlands'
DEBUG:subliminal.refiners.tvdb:Found 1 results
DEBUG:subliminal.refiners.tvdb:Found exact match on series u'Into the Badlands'
DEBUG:subliminal.refiners.tvdb:Found series {u'seriesId': u'27749', u'rating': u'TV-14', u'overview': u'A mighty warrior and a young boy search for enlightenment in a ruthless territory controlled by feudal barons.', u'firstAired': u'2015-11-15', u'id': 289079, u'aliases': [u'Badlands'], u'networkId': u'', u'network': u'AMC', u'zap2itId': u'SH02278173', u'seriesName': u'Into the Badlands', u'status': u'Continuing', u'added': u'2014-12-07 22:05:02', u'imdbId': u'tt3865236', u'lastUpdated':<PHONE_NUMBER>, u'addedBy': 307101, u'genre': [u'Action', u'Drama'], u'banner': u'graphical/289079-g4.jpg', u'slug': u'into-the-badlands', u'airsTime': u'10:00 PM', u'siteRatingCount': 28, u'airsDayOfWeek': u'Sunday', u'runtime': u'45', u'siteRating': 8}
INFO:subliminal.refiners.tvdb:Getting series episode 2x1
1 video collected / 0 video ignored / 0 error
DEBUG:subliminal.refiners.tvdb:Found episode {u'seriesId': 289079, u'airsAfterSeason': None, u'dvdEpisodeNumber': 1, u'productionCode': u'', u'overview': u'Six months after the Season 1 finale, Sunny finds a new foe, as well as a new, unexpected ally, while MK learns about his gift in a mysterious place.', u'airedSeasonID': 696341, u'thumbAdded': u'2017-03-20 03:52:19', u'episodeName': u'Tiger Pushes Mountain', u'airedSeason': 2, u'airsBeforeSeason': None, u'showUrl': u'', u'id': 5928292, u'dvdDiscid': u'', u'filename': u'episodes/289079/5928292.jpg', u'dvdSeason': 2, u'writers': [u'Alfred Gough', u'Miles Millar'], u'airedEpisodeNumber': 1, u'absoluteNumber': 7, u'thumbHeight': u'225', u'imdbId': u'tt5543760', u'lastUpdated':<PHONE_NUMBER>, u'director': u'Nick Copus', u'lastUpdatedBy': 396427, u'dvdChapter': None, u'airsBeforeEpisode': None, u'language': {u'overview': u'en', u'episodeName': u'en'}, u'thumbAuthor': 459860, u'siteRatingCount': 7, u'directors': [u'Nick Copus'], u'firstAired': u'2017-03-19', u'guestStars': [], u'siteRating': 7.9, u'thumbWidth': u'400'}
INFO:subliminal.core:Refining video with omdb
DEBUG:subliminal.refiners.omdb:No need to search
INFO:subliminal.core:Listing subtitles with provider 'opensubtitles' and languages set([<Language [en]>])
INFO:subliminal.core:Initializing provider opensubtitles
INFO:subliminal.providers.opensubtitles:Logging in
...

Feel free to reopen the issue otherwise


Fix override title if not within an exhibit.

Coverage remained the same at 100.0% when pulling e27171747edae300498121e059ebb1f731049c9e on search_across into 12808116ce59c91acce1941018edd183aca004b4 on master.


feat: add the ability to convert image/heic to image/jpeg on the fly in order to be able to show in <img /> tag

I believe we do Capacitor.convertFileSrc(path) to generate a string which we can bind to <img /> src.
But image/heic won't work. : S
Maybe the file picker can convert image/heic to image/jpeg on the fly if it's cheap to do so

I have added a new method convertHeicToJpeg (see #89) which can be used to convert a picked HEIC image to a JPEG image.
I have not done this on-the-fly on purpose, as not everyone may need this conversion and jpeg files would be generated unnecessarily. I also prefer to have a separate method instead of another method option. This way, error messages can also be handled separately and it feels cleaner.
Feedback is welcome!

@robingenz this sounds good to me!


Missing arch/ and configs/ subdirectories when "git checkout" 7.11 to 7.15

I'm trying to get Atmega128 work with NuttX and when I did "git checkout 7.15" noticed that arch/ and configs/ directories were empty.
I think it was caused because in the past some directories were separated from nuttx/ kernel.
This issue happens from 7.11 to 7.15! So version <= 7.10 seems fine as well version >= 7.16.
@patacongo I remember you said you have all NuttX tarball versions saved in your computer.
Could you please update it to some free online file sharing? (i.e. https://www.pcloud.com offer 10GB for free)

This is how I discovered to issue:
I'm using the BK-AVR128 board and noticed that older NuttX version (i.e. 6.10 before Kconfig era) didn't have any activity in the serial (the TXD line just went from low to high) and the same thing happens after version 7.17.
In version 7.16 I can see it printing many "KKKKKKKKKKKKKKKK", using logic analyzer the sequence seems to be 0x44 0x4b 0x4b 0x4b 0x4b ....
I'm using avr-gcc toolchain (called Linux GCC on menuconfig), but sure if avr buildroot toolchain works, since I don't have it.

More some info:
eac916c90797d1c342e9e9663084b3155d49a481 - doesn't work
ed1535f18846ebcd1744121b85de40dde5d25e3d - prints: DKKKKKKK... in the serial console

@patacongo I remember you said you have all NuttX tarball versions saved in your computer.
Could you please update it to some free online file sharing? (i.e. https://www.pcloud.com offer 10GB for free)

7.12 through 7.15 are available here: https://sourceforge.net/projects/nuttx/files/nuttx/  The arch/ and configs/ directories are fully present in that tarball.  Sounds like the upstream repository is bad.
If you were looking at a version where the submodules were used, then you would see submdule files in those directory.  They are not so I assume that there is some corruption in the githut repositories.

If you were looking at a version where the submodules were used, then you would see submdule files in those directory. They are not so I assume that there is some corruption in the githut repositories.

The Documentation/ directory was made a submodule by 40f52f72d793ccdfb16cb8076d2d03aeb60c61ca
The configs/ directory was made a submodule by 2113f4af7ba585b6fecae010b64051556d5d9b11
The arch/ directory as made a submodule with e9a3cc34576f3942b7bbd3d5fecf697cde7748eb
The normal directories were restored sometime after 1645c75d4b0ae8f8c375b9d77a2e84c28ef13f45 (last submodule update).

Thank you @patacongo for confirming the issue. At least for AVR issue, using version 7.16 to 7.17 is enough to track the serial issue.

Thank you @patacongo for confirming the issue. At least for AVR issue, using version 7.16 to 7.17 is enough to track the serial issue.

What I don't understand is why github won't access those directories.  There must be something there it cannot handle.  It worked well on BitBucket (where the change was made) and the files are clearly in the repository because you can see the file history for arch/, Documentation/, and configs all the way back to the beginning.
github is not tolerant of any quirkiness in the repository.  It won't access anything it doesn't like.  For example if you look at the contributors:  https://github.com/apache/nuttx/graphs/contributors , it doesn't see anything before about 2014.  That is the date when the repository was converted from SVN to GIT.  So the statistics miss something like 20 thousand contributions.
My belief is that that is caused by the fake email addresses that the old SVN-to-GIT conversion tool created.  Ijust use a UUID for the email address.
Bitbucket can also see all commits from day one when NuttX was under CVS, then, SVN, then GIT.

@patacongo I think it is not much problematic since nobody it too worried about preserving all arches and boards, but I think it should be nice to have the complete history of NuttX saved in the git.
Maybe if you have the original bitbucket, it should be nice to keep it as Read-Only with a comment at top saying that the development is happening here in the github (this repository is preserved only to history purposes).


[FSDE-2133] Prepared Chi 5.1.0 release

https://ctl.atlassian.net/browse/FSDE-2133

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-139/1/. :white_check_mark:

You can check this PRs instance in https://561c597cce8e540ffa453229b4227234b8dd4501-chi-pr.enterprise.ctl.io

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-139/2/. :white_check_mark:

You can check this PRs instance in https://69c7bdea709e1a8856f96c6e55d2df36f04866d6-chi-pr.enterprise.ctl.io


Code to parse metadata

To parse the meta data of PDF document

The Package that was used has build issue and have opened an issue with the package, so that the developers can work on it and resolve it.


Please document a way to set digest_method and signature_method for signing

I'm updating some code that uses rsa-sha1 for signing to use xml-kit instead of doing things more manually. One of my first tests, I noticed that it switches to rsa-sha256 by default, which breaks compatibility with some external parties we've integrated with.  I investigated the source and discovered that the class including ::Xml::Kit::Templatable can override digest_method and signature_method to control the signing algorithms, but that interface is totally undocumented.
I would like to not depend on undocumented internals, and would really appreciate some documented way to control the signing algorithms.

Whoops.  That doesn't even work quite right, due to
      DIGEST_METHODS = {
        SHA1: 'http://www.w3.org/2000/09/xmldsig#SHA1',

The correct string for that digest method is 'http://www.w3.org/2000/09/xmldsig#sha1'.  I guess this is sneaking in an actual bug report, though the bug is still gated behind an undocumented interface.

In https://github.com/saml-kit/xml-kit/pull/11 I have correct the mistake to sha1 and documented an API for specifying the designed digest_method and signature_method.
You can now use:
item.sign_with(key_pair, digest_method: :SHA1, signature_method: :SHA1)

Or you can set the digest/signature methods directly via an attr_accessor.
item.digest_method = :SHA1
item.signature_method = :SHA1

This has been published in https://rubygems.org/gems/xml-kit/versions/0.4.0.

Thank you.


Add self to maintainers, fix trivial go vet errors in test for 1.7

I haven't updated any dependent repos yet, ask me before lgtm

Current coverage is 74.10% (diff: 100%)

Merging #114 into master will not change coverage

@@             master       #114   diff @@
==========================================
  Files            53         53
  Lines          2298       2298
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1703       1703
  Misses          515        515
  Partials         80         80

Powered by Codecov. Last update b89c7a6...84c3769

Current coverage is 74.10% (diff: 100%)

Merging #114 into master will not change coverage

@@             master       #114   diff @@
==========================================
  Files            53         53
  Lines          2298       2298
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1703       1703
  Misses          515        515
  Partials         80         80

Powered by Codecov. Last update b89c7a6...84c3769

https://phabricator.twitter.biz/D8539

LGTM


line chart

line chart, how to set the axis interval for x

https://stackoverflow.com/questions/66669093/how-to-set-category-axis-mark-interval-and-label-interval-in-apache-poi-5-0-0


unable to use check update and auto sync

Issue Type: Bug
check for update option not working every time he show me net::ERR_CERT_AUTHORITY_INVALID and auto sync show check log file
log file show :-
[2020-12-30 11:24:53.257] [userDataSync] [info] Using settings sync service https://vscode-sync.trafficmanager.net/
[2020-12-30 11:24:53.257] [userDataSync] [info] Auto Sync is disabled.
[2020-12-30 11:25:09.858] [userDataSync] [info] Request failed https://vscode-sync.trafficmanager.net/v1/manifest
Please See This Image.

VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:34:46.910Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz (4 x 3491)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: unavailable_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: unavailable_offskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
3.87GB (1.09GB free)

Process Argv
--crash-reporter-id b2366b99-c81e-40a9-8a01-7c919e1e073e

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

LiveServer
rit
5.6.1

![image](https://user-images.githubusercontent.com/76550123/103333248-4c8eb180-4a93-11eb-98b7-4901f5300c03.png)

Seems to have proxy / network issues and hence you are not able to connect to our update or settings sync service.
@joaomoreno / @lszomoru  Is there a way user can test to check access to these services?

Seems to have proxy / network issues and hence you are not able to connect to our update or settings sync service.
@joaomoreno / @lszomoru  Is there a way user can test to check access to these services?


chore: java 7 cleanup and stable branch

Removes unused java 7 ci files.
Marks branch 1.21.x as stable.

Checking with the yoshi team on how to modify these templated files.

We should hold off on this until further notice from @lesv
Around 3 weeks from now.

Closing for now


I want a whole world data!

I want a whole world data!
thanks.

Hey! You can select "World" as you would any other country!
See the screenshot below:


How to make custom log changes persistent

Hello. I am quite new to this. Is it possible to make persistent changes made accrding to this article: https://www.redmine.org/projects/redmine/wiki/HowTo_add_a_logo_to_your_Redmine_banner
I wanna make a custom logo.

Thanks for reply! Will try


Parse record values lazily in Column op?

We parse the whole record in get_next_record(), which results in redundant work if only some of the columns are used. Let's make the record parsing lazy by detecting column offsets in get_next_record(), but only parsing the values in Column and related ops.

@penberg so instead of using OwnedRecord we need to something like an OwnedLazyRecord which doesn't parse values but just store value offsets ??

@penberg, If you think the above comment is a step in the right direction, I'd like to take this issue.


THE CHATBOT AND RETURN TO TOP BUTTON ARE COLLAPSING ON SAMLL SCREENS

### Is your feature request related to a problem? Please describe.
On smaller screens, the chatbot and the "Return to Top" button are overlapping or collapsing into each other, causing usability issues. This results in a frustrating experience for users who might accidentally trigger one feature while trying to use the other. The lack of adequate spacing and positioning adjustments for mobile screens reduces the accessibility and effectiveness of both elements.
### Describe the solution you'd like
I would like the chatbot and "Return to Top" button to be repositioned and optimized for smaller screens. The solution should:
### Ensure both elements are not overlapping or collapsing into one another.
Use media queries to reposition the chatbot to a suitable area on the screen, such as the bottom left or right, while keeping it out of the way of the "Return to Top" button.
Maintain adequate spacing between the elements so that both are easily accessible.
Ensure that both the chatbot and the "Return to Top" button are responsive, resizing appropriately on smaller screens without impacting their usability.
### Additional context
For mobile-friendly design, Flexbox or absolute positioning can be used to maintain consistent spacing. Here’s an example screenshot showing how the elements overlap on smaller devices. Proper responsive adjustments for these features should enhance the user experience, especially on smartphones and tablets.

@Harshdev098 and my dear @dnyanesh99borse I will request to you please assign me this issue, I'll make sure I'll solve issue as early as possible with great efficiently .

yes sir no worry at all you can assign this issue to him too. glad to do @Harshdev098

@dnyanesh99borse  Are you still working on it

hey @Harshdev098 is this issue open? if so can i contribute to it??


Add Calculator

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#17  👈
#16
#15
#14
#13
#12
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @kanziw and the rest of your teammates on  Graphite

Merge activity

Apr 10, 8:08 AM EDT: Graphite rebased this pull request after merging its parent, because this pull request is set to merge when ready.


[CLI] CLI should look at cwd and use locally-installed binary (if present)

One problem with npm install -g is that it installs an executable at a certain version -- whereas various projects could be built using/expecting a different version.
One way I dealt with this for the Jest CLI was to look at CWD and try to determine if we're currently inside a project that depends on the CLI (and, if so, delegate execution to the local version instead of the globally-installed version).
This should also help reduce the frequency with which people need to update their global CLI version.

Agreed. This is why grunt-cli exists.

Are you talking about the flow-typed cli binary?

@ryyppy: right

(PS: I have this PR mostly ready, just need to test a bit more before I send it out for review)


New problems with the printer

Good afternoon,
We have again problems with the RegEx adjustments this time for large signatures.
The signature would be:
PDJ 33 380/1949-1947
These signatures can also be longer.
Would they give us guidance on the regex settings?

Could you give me the number of lines and an example for the desired output?
Like:
Number of Lines: 4
1: PDJ
2: 33
3:
4: 380/1949-1947
Could signatures contain any special characters like $%& ?

Could you give me the number of lines and an example of the desired output?

Yes i can :
An example is :
PDJ 35 380 / 1949-1974
Maximum of 2 lines
Line 1: PDJ 35 380
Line 2: 1947-1974

Number of lines:

Maximum 2

Could signatures contain special characters such as $%&?

Ein Beispiel ist:
PDJ 35 380 / 1949-1974
Maximal 2 Zeilen
Zeile 1: PDJ 35 380
Zeile 2: 1947-1974
Anzahl der Zeilen:  Maximal 2
Könnten Signaturen Sonderzeichen wie $%& enthalten?
Nein nur /()+-_*

Is the linebreak always after the /?

Oh! For small signatures not. But that works already.
In the case of the large signatures, if they do not fit to 70 mm x 20 mm in a single line, the annual numbers or editions should then be placed in a second line, which is then behind the /

Ok.
In that case, the RegEx: ^(.*)[/](.*)$ should be fine.
I attached the Modi\defaultMode.json, Formate\default_gross.json and FormateCSS\default_gross.css.

Fixed, after the changes, I can also display the major signage on small signatures, or larger ones as it fits and here at the location better.
I thank them once again for the quick fix.
Is there a way to learn how we can make small adjustments ourselves? Because the wiki doesn't contain everything as exactly as you change things in RegEx.

You're welcome.
I can recommend this website to test regular expressions and to deepen the understanding of it.

We have a small problem still how to do after the first 6 letters e.g. IHZ-UH insert a distance 3 characters ? The text then, for example This is how it looks: IHZ-UH___283 288/ 1985-2019. The underscores should be the distance.

Ok, for the default_klein:
Change the RegEx,
from:
^([\w\-]+\s[\w\.\,]+)([\s\/]?)([^\/\:]*)([\/\:]?)(.*)$
to:
^([\w\-]+\s)([\w\.\,]+)([\s\/]?)([^\/\:]*)([\/\:]?)(.*)$
and edit the line grouping,
from:
$1$2$3$4$5$6
to:
$1   $2$3$4$5$6
For the default_gross:
Change the RegEx,
from:
^(.*)[/](.*)$
to:
^([\w\-]+\s)([\w\.\,]+)(.*)[/](.*)$
and edit the line grouping,
from:
$1
$2
to:
$1   $2$3
$4

Thank you very much.
Now it's perfect.
Thank you for the super-fast support

You're welcome.
The RegEx for default_gross isn't correct.
Currently the result will be 4 white spaces instead of 3.
To correct this, you have to change the RegEx,
from:
^([\w\-]+\s)([\w\.\,]+)(.*)[/](.*)$
to:
^([\w\-]+)\s([\w\.\,]+)(.*)[/](.*)$


Easier management of root type contributions

Here are some things I would like users to not have to think about:

I haven't defined a Query type yet, can I use QueryField?
I haven't defined a Query type yet, can I use extendType with it?
I want to modularize my schema, can I use Query type repeatedly and have it merge?

Here's what I've been thinking about; Multiple calls to root types get merged:
// A.ts
export const QueryA = queryType({ ... })

// B.ts
export const QueryB = queryType({ ... })

I suspect in almost all cases this would be exactly the desired functionality.
On the config properties:

definition – merging this is easy

description – append, order determined by order Nexus sees them (e.g. config property types array items order)

nonNullDefaults – this doesn't need to merge, it can just stay local, which makes perfect sense IMO

rootTyping – this I'm not sure about. Can we just keep it local? I don't see how since the typings are global... Otherwise it is a sharing situation and any that set it affect all others. And if multiple set it then last one wins (same definition of order as explained for description). I am not very happy with the behaviour here but two things make me not mind:

In vast majority of cases backing type for root types is undefined
jsdoc can explain the quirks

WDTY @Weakky @tgriesser

I just realized that extendType doesn't require the original type to have been defined. That's great.
So now the main difference left in this proposal is:
queryType({ definition(){ ... } })

// vs

extendType({ type: 'Query', definition(){ ... } })

Not a big difference...
And a trivial way to cut the difference yet further:
queryType({ definition(){ ... } })

// vs

extendQueryType({ definition(){ ... } })

I don't know if then the new merging behaviour I'm proposing is worth it.
If we wanted to cut the difference further we would have to do this for extendType:

allow it to specify NonNullDefaults
allow it to specify description

Isn't this what queryField does?

What's exactly the use case of having multiple queryTypes? Is it to avoid a bigger schema.ts? In this case, I'd like to see Nexus a little bit more (not that much) opinionated, helping users to split queries, mutations and object types into different files since the beginning.
I use extendType basically for joining graphs (different projects) in the same gateway endpoint. I try to avoid using it inside the same project because we can end up in weird cases of inheritance, circular dependencies, and so on. BTW, the nexus documentation about extendType could be improved.
Back to the question, if my project grows enough and I see the need of having to split queryType, I vote for just defining queryTypes where I need and let the framework merge them for me.

@tgriesser ah I forgot this worked:
export const Mutation = mutationField((t) => {
  t.crud.createOneBlog()
  t.crud.updateManyBlog()
})

The naming is a tad surprising here.

Aside:

Some jsdoc would help a lot.
Also although there it is overloaded the VSC ui doesn't show the UI for navigating the overloads... Do you know why that might be?

Do you think this variant of mutation field is worth it from an API surface area perspective?

I feel like the object form with the very consistent definition method might be good enough...
And if we do want to keep both forms, do you think the overload approach is the right way here?
For example if extendType gets the additions I was mentioning before nonNullDefaults etc. then there becomes a clear difference in functionality:
extendType({
  type: 'Mutation',
  nonNullDefaults: ...,
  definition(t) {
    t...
  }
})

// and, built over ^, this --v

extendMutationType({
  nonNullDefaults: ...,
  definition(t) {
    t...
  }
})

// which clearly allows capability––the type config––not possible in this API

mutationField(t => {})
mutationField('foo', {})

What's exactly the use case of having multiple queryTypes? Is it to avoid a bigger schema.ts? In this case, I'd like to see Nexus Schema a little bit more (not that much) opinionated, helping users to split queries, mutations and object types into different files since the beginning.

@ricardoalmeida FWIW, for a monolithic schema, this is the directory structure I generally use:

1 folder per "graphql type", 1 file per top-level mutation / query / subscription, generally 1 file per objectType, interfaceType, enumType, etc...
I only use queryField / mutationField / subscriptionField. Not sure how well this would work for joining graphs across projects but just thought it was worth sharing.
GraphQL types are for definition only, all logic exists in the context... the context (we call it DataContext) is then responsible for wrangling all of the different services, etc.

Some jsdoc would help a lot.

I agree, feel free to add some. Maybe something that matches the docs? It shows up for me before any arguments are supplied:

Also although there it is overloaded the VSC ui doesn't show the UI for navigating the overloads... Do you know why that might be?

Do you think this variant of mutation field is worth it from an API surface area perspective?

Which variant are you referring to? I think the current form works great. As I mentioned above, I only ever use mutationField, so if I need to express something like a connectionField, it's the only way to do it.
Not sure I see the value of making any changes to these apis personally.

Not sure I see the value of making any changes to these apis personally.

One limitation right now is that extendType does not have access to type configuration like nonNullDefaults. And I've seen use-cases for plugins to add type configuration too. It would be neat if extendType maintained access to it.

nonNullDefaults is a pretty powerful API. I don't know that you'd want to "extend" a type and have that being something that might get changed for multiple types, especially on the root level - unless you're thinking that it would apply just to the fields defined within that extendType, in which case that seems more reasonable to add support for, though I don't think it'd be something I'd find myself reaching for personally.

unless you're thinking that it would apply just to the fields defined within that extendType, in which case that seems more reasonable to add support for, though I don't think it'd be something I'd find myself reaching for personally.

Yep, was thinking this.
I am going to close this issue as the proposal doesn't seem strong enough to warrant all the discussion and internal change.
If it was cheap to do I would say mutationType queryType subscriptionType should merge and thus make mutationField subscriptionField queryField obsolete, thus simplifying the API surface area at the "cost" of increasing the semantic complexity of those three functions. I think the trade would be worth it because I cannot think of a use-case for non-merging mutationType queryType subscriptionType, thus the "semantic complexity" would be none since its what (I think) would be expected/most intuitive anyways.
All that said, I'm worried achieving this will be too costly in terms of internal change and discussion. I think there are more important things to do for 1.0 than this...


Applying PHP code format in readme

nothing special. Just added php formatting in sample code for readability. :)

Coverage remained the same at 89.592% when pulling fb2ee2aabec3c4cead98fbf822b2c42a4533fbb1 on gunjanpatel:patch-1 into f87d1c9d3bddfcf64dde10fe72d93c13225c9733 on consolidation-org:master.

Coverage remained the same at 89.592% when pulling fb2ee2aabec3c4cead98fbf822b2c42a4533fbb1 on gunjanpatel:patch-1 into f87d1c9d3bddfcf64dde10fe72d93c13225c9733 on consolidation-org:master.

Thanks.


Strategy for handling interlaced content

Currently the GStreamer pipeline(s) used by voctocore are not specifically taking interlaced content into account. This would not be a problem if all elements handled interlaced content transparently. Unfortunately this does not seem to be the case.
This ticket is a collection of various observations pertaining to GStreamer, voctocore and interlacing.
Caps
For video/x-raw there is a interlace-mode flag defaulting to progressive. The precise interlacing is determined by a mixture of caps and per buffer flags.
Documentation:

https://cgit.freedesktop.org/gstreamer/gst-docs/tree/markdown/design/mediatype-video-raw.md
https://cgit.freedesktop.org/gstreamer/gst-docs/tree/markdown/design/interlaced-video.md

Wrong metadata
If the internet is to be trusted metadata of interlaced video is wrong more often than not.
One offender here seems to be our good friend ffmpeg. It happily sets the Interlaced flag of a Matroska container to false for 1080i50 content read from a decklink card.
PsF
Progressive segmented Frame is a way to transport progressive frames using interlaced equipment.
A single frame is split up into two fields, as opposed to fields being recorded at twice the framerate.
If this is known frames can be recreated by simple weaving as opposed to regular deinterlacing.
When interlaced data is represented as frames as opposed to two fields this puts us in an interesting situation wrt. metadata. Software correctly signalling that the transport was interlaced, won't tell us that the source data was actually progressive. Software labelling data transmitted over an interlaced transport as progressive is now telling the truth "by accident".
intervideo{sink,src}
The most obvious case of not handling interlaced content (more specifically caps with interlace-mode=mixed) is intervideo{sink,src}. It throws a set of assertions:
** (python3:11851): CRITICAL **: gst_video_converter_new: assertion 'in_info->interlace_mode == out_info->interlace_mode' failed
** (python3:11851): CRITICAL **: gst_video_converter_frame: assertion 'convert != NULL' failed
** (python3:11851): CRITICAL **: gst_video_converter_free: assertion 'convert != NULL' failed

Some debugging reveals that the failing conversion is trying to convert the black filler frame to the correct output caps which have a non-progressive interlace-mode.
Scaling
Scaling interlaced video seems to be generally hard/annoying. So much so that the BBC apparently does a deinterlace/scale/re-interlace step to get decent quality (src). Much worse though I'd be surprised if the compositor element actually used an interlacing aware algorithm when the caps indicate it's necessary. However, I have not verified this, so I might very well be wrong.
Solutions

Require that source video is progressive

This is apparently what gst-switch does
Easiest solution by far
Use source ffmpeg with -deinterlace or a yadif filter

Deinterlace input ourselves if necessary

deinterlace element already handles this transparently, passing through progressive data
Wrong metadata makes this hard(er), so we probably would need a switch to enforce deinterlacing of a source

Make the pipeline capable of handling interlaced video

Not clear this is sensibly possible when scaling
Possibly means fixing up a lot of elements

Testing notes
Source with interlaced testvideo:
gst-launch-1.0 videotestsrc ! video/x-raw,format=I420,width=1920,height=1080,framerate=25/1,pixel-aspect-ration=1/1,interlace-mode=mixed ! matroskamux ! tcpclientsink host=localhost port=10000

Source from decklink:
gst-launch-1.0 decklinkvideosrc device-number=1 mode=1080i50 connection=SDI ! videoconvert ! video/x-raw,format=I420 ! mux. decklinkaudiosrc device-number=1 connection=embedded ! mux. matroskamux name=mux ! tcpclientsink host=localhost port=10000

I'd lean towards declaring voctomix to be progressive only, thus handing the task of handling progressive input over to the architect of the respective setup.
We have been running a complete-progressive Voctomix at //SEIBERT/MEDIA with a Zidoo-Streamer as Scaleconverter and one of the JVCs, both of which can do 1080p25.
For systems where this can't be achieved (AFAICT the Pavo-Boxes can only do 1080i25, I'm unsure about the Panasonic-Cameras) it would be best to deinterlace at the source, because voctomix will scale the interlaced video without proper handling it.
the other approach that I thought about would be to make the Source-Elements interlacing-aware and automatically add a deinterlacer in there. The Problem is that I can see a lot going wrong there, from wrong metadata to wrong field-order. If this is handled transparently bx voctomix the risk of the system architect not being aware of this possibly destructive step is high.

As written in another issue, this could be resolved with FFmpeg git head of today.
Adding deinterlacing to voctomix "on-demand" is a good idea from a signal-flow point of view, but can lead to some bad surprises regarding performance. deinterlacing takes significant amounts of CPU times and that also depends on the video content, e.g. it is difficult to predict.
Since "only" the scaling is a problem, while fullscreen interlaced video may be passed disguised as being progressive, maybe adjust the scaling? Something like "do a nearest-pixel-scaling of 50% first, then do another scale to desired size" should be a poor-man's deinterlacing solution that has a small CPU footprint.


增加文章阅读次数

增加文章阅读次数

I think it's OK to modify DocumentModel.go/Document, add ViewCount filed. When func (c *DocumentController) Read() is called and check passed, update the ViewCount directly by calling func (item *Document) InsertOrUpdate(cols ...string). However, maybe this method should do migration after update.


Move to hatchling for build + pyproject.toml for package def

Closes #1641. WIP to see how angry CI is at me for pulling the rug out from under it.

[x] Moves project definition into pyproject.toml and use hatchling as backend
[x] Remove setup.cfg by moving config options to other files as appropriate
[x] Move the build_client and copy_client commands into a dedicated script with click for CLI
[x] Remove setup.py
[x] Adjust README.rst to bake in the citations, to keep pyroma happy and have correct rendering on GitHub and citations on PyPi.
[x] Use https://github.com/ofek/hatch-vcs as plugin to generate __version__ and revision from tags.

[ ] I don't like that the normal version number now has the git revision in it, I need to look more into this plugin to see how to configure it.

[x] Port hatch_build.py from LiberTEM-live
[ ] Make pyroma happy again in CI due to lack of setup.cfg
[x] Disable pyroma due to missing build dependencies in CI (only?)
[ ] Update the release scripts to handle setting the version and revision from git tag

Contributor Checklist:

[x] I have added or updated my entry in the creators.json file
[ ] I have added a changelog entry for my contribution
[ ] I have added/updated documentation for all user-facing changes
[ ] I have added/updated test cases
[ ] I have included the rebuilt production build of the client (only if changes were made to the GUI)

Reviewer Checklist:

[ ] /azp run libertem.libertem-data passed
[x] No import of GPL code from MIT code

[ ]  I don't like that the normal version number now has the git revision in it, I need to look more into this plugin to see how to configure it.

You can also check how this is done for LiberTEM-live, which uses a custom hatch_build.py for baking the revision, and tool.hatch.version for reading the version from __version__.py  (basically keeps the old way of versioning, just with new packaging around it)

/azp run libertem.libertem-data

[ ]   I don't like that the normal version number now has the git revision in it, I need to look more into this plugin to see how to configure it.

You can also check how this is done for LiberTEM-live, which uses a custom hatch_build.py for baking the revision, and tool.hatch.version for reading the version from __version__.py (basically keeps the old way of versioning, just with new packaging around it)

Great, my fault for not looking too closely at the way you set it up over there. I've followed the same pattern here! Thanks for the tip.

/azp run libertem.libertem-data

/azp run libertem.libertem-data


Subscription fix

This fixes the case when a connect fails and the subscription worker innerLoop is block on waiting on conThreads.  The problem was conThreads was not cleared when connect thrown an exception (only when it return without an error).

bors r+


Expense Inviting Errors with 0 total amount

Describe the bug
It seems that inviting a user to submit a reimbursement by default gives error; Validation error: Validation min on amount failed, although we mark the amount here as optional.

To Reproduce
Steps to reproduce the behavior:

Go to any collective
Click on submit expense and go through the flow on creating an expense invite (type reimbursement as seen on the below screen-cast)
See error

Expected behavior
We should not see any error and the validation should not be done since the amount field is optional.
Screenshots
invite-error.webm

This was reported at, https://opencollective.freshdesk.com/a/tickets/216459

Strange, the min on amount has always been there: https://github.com/opencollective/opencollective-api/pull/426. Either:

A sequelize update changed the default behavior for this validation
Or we changed something in the invite process
Or the invite process has never worked with 0 amounts

Duplicate of https://github.com/opencollective/opencollective/issues/6587


rapidjson ARM architecture release build bug

axmol version:
devices test on:
developing environments

NDK version: r23c
Xcode version: 14.2+
Visual Studio:

VS version: 2022 (17.9+)
MSVC version: 19.39+
Windows SDK version: 10.0.22621.0+

cmake version:
Steps to Reproduce:

Firstly, this is not an issue with Axmol, but rather with the rapidjson library.
An application I ported over from Cocos2d-x was previously using an older version of rapidjson included with it (which was also from cocos2d-x), so it was never using the radpijson in Axmol.  Deleting the local version of rapidjson so the app would use the version supplied with Axmol has resulted in reproducible crashes on iOS (arm64).
The crashes only occur in the release builds (with optimizations on).  The crashes do not occur with ARM debug or x86/x86_64 (debug/release).
The links below describe the issue, which is still unresolved, but there are a few ways to work around it.
https://github.com/Tencent/rapidjson/issues/388
https://github.com/Tencent/rapidjson/issues/301#issuecomment-93767130
https://github.com/Tencent/rapidjson/issues/601
https://github.com/cocos2d/cocos2d-x/issues/16492
Checking the local version of rapidjson, I noticed this difference in document-wrapper.h:
Axmol version:
#pragma once

#include "rapidjson.h"
#include "document.h"

Cocos2d-x version:
// Wrapper file for document.h to fix the crash bug (https://github.com/cocos2d/cocos2d-x/issues/16492)

// Bug in gcc 4.9.0 on ARM with ARM instruction set, -O2 causes the bug
// This gcc version cannot use #pragma GCC push_options/pop_options as well. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59884

#include "json/rapidjson.h"

#if defined(__arm__) && defined(RAPIDJSON_GNUC) && RAPIDJSON_GNUC >= RAPIDJSON_VERSION_CODE(4,9,0) && RAPIDJSON_GNUC < RAPIDJSON_VERSION_CODE(5,0,0)
    #pragma GCC optimize ("O1")
#endif
#include "document.h"
#if defined(__arm__) && defined(RAPIDJSON_GNUC) && RAPIDJSON_GNUC >= RAPIDJSON_VERSION_CODE(4,9,0) && RAPIDJSON_GNUC < RAPIDJSON_VERSION_CODE(5,0,0)
    #pragma GCC reset_options
#endif

The above optimization fix as implemented does not work with the latest Xcode 15, since the compiler checks don't do anything, and would need to be updated to work with the compiler used in Xcode 15.
The alternative work-around, which can be done in our projects, is to use the CrtAllocator instead, and have custom Document and Value types. For example:
namespace jsonfix
{
using JDocument = rapidjson::GenericDocument<rapidjson::UTF8<>, rapidjson::CrtAllocator>;
using JValue = rapidjson::GenericValue<rapidjson::UTF8<>, rapidjson::CrtAllocator>;
}

...and then use jsonfix::JDocument and jsonfix::JValue instead of rapidjson::Document and rapidjson::Value.   This is the way I've implemented it in my own project.

Thanks, it is very useful info

Is it unaligned memory access crash or something else?

@halx99 This issue is just to inform others of the problem, so if you want to set the "Helpdesk" label on it, then that would be good.  Feel free to close the issue at any time, since there may not be anything we can do about it in the rapidjson source.

maybe align issue, any memory pool implemention shoud ensue allocated address base align max_align_t

https://github.com/yasio/yasio/issues/283

maybe align issue, any memory pool implemention shoud ensue allocated address base align max_align_t, @rh101 could you try redefine RAPIDJSON_ALIGN?

I'll test that out later today to see if it works.

could provide reproduce sample code and device info to test on

could provide reproduce sample code and device info to test on?

I did try to create a reproducible test case, but no matter what I've tried so far, I can't reproduce it.
Running as a release build on an iPhone 7 (arm64).
The project is here: https://github.com/rh101/issue2048
The test.json file is it parsing is similar to the one that it crashes on in the main application.  If I manage to find out what the difference is between this and the main app, or manage to reproduce it, then I'll post an update.

Just something to note.  If the Undefined Behavior Sanitizer option is enabled for the current scheme, then the crash does not occur.

A few screenshots from the crash:

reproduced by your sample project?

reproduced by your sample project?

Sorry no, those screenshots are from the main project that has the issue.  I'll update the post to mention that.

initializer-list order issue? try trace the execution order?

OK, so @halx99 pointed something out to me, which is that if a library linked to the application happens to use a different versions of rapidjson, then strange things happen on iOS.
While tracing this issue, 2 different versions of the the allocators.h loaded from different code paths, and it turned out there is a library in the app that did in fact include its own version of rapidjson.  The mismatch with the implementation of the MemoryPoolAllocator was the cause of all of these issues.  Deleting the rapidjson from that library, and forcing it to use the version supplied with Axmol fixed the problem.


Kusto Connection Icon in Python Notebook

I'm working in a Python notebook and the "Configure Kusto Connection" item in the notebook toolbar is showing up.
Is there a way to make sure this only shows up for Kusto Notebooks?

Aah, I added this for those using kqlmagic with Jupyter notebooks.
Hmm, need to figure out when to display this.
Possibly when kqlmagic is used in a cell.


move ov page

Docs Build status updates of commit aebeb69:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/latest/cognitiveservices-face-readme.md
:white_check_mark:Succeeded
View (azure-node-latest)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 70a52a4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/latest/cognitiveservices-face-readme.md
:white_check_mark:Succeeded
View (azure-node-latest)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

#sign-off


Allow revoting without change of selected BPs

This is needed because vote power is reduced with time. So I should be allowed to revote without changing my selected BPs.

This is now available in the most recent release.


fix typo in additionalProperties

Pull Request Test Coverage Report for Build 98737

0 of 0   changed or added relevant lines in 0 files are covered.
23 unchanged lines in 19 files lost coverage.
Overall coverage decreased (-0.9%) to 78.105%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Builder/Adapters/TestFlow.cs
1
79.67%

/libraries/Microsoft.Bot.Builder.Dialogs.Adaptive/Actions/EmitEvent.cs
1
55.56%

/libraries/Microsoft.Bot.Builder.Dialogs.Adaptive/Actions/GetActivityMembers.cs
1
30.77%

/libraries/Microsoft.Bot.Builder.Dialogs.Adaptive/Actions/IfCondition.cs
1
76.47%

/libraries/Microsoft.Bot.Builder.Dialogs.Adaptive/Actions/SignOutUser.cs
1
63.64%

/libraries/Microsoft.Bot.Builder.Dialogs.Adaptive/Actions/SwitchCondition.cs
1
80.49%

/libraries/Microsoft.Bot.Builder.Dialogs.Adaptive/DialogManager.cs
1
81.03%

/libraries/Microsoft.Bot.Builder.Dialogs.Adaptive/Generators/ActivityChecker.cs
1
86.62%

/libraries/Microsoft.Bot.Builder.Dialogs.Adaptive/Testing/TestActions/AssertReplyActivity.cs
1
80.77%

/libraries/Microsoft.Bot.Builder.Dialogs/ObjectPath.cs
1
86.03%

Totals

Change from base Build 98714:
-0.9%

Covered Lines:
14287

Relevant Lines:
18292

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3


Fix some test errors

Also export \cdot alias for dot/inner.

These errors should be fixed by #304.


TextField view moves too far when it updates

When the TextField updates its view (e.g. the cursor moves off the left or right side) the view moves too far, essentially hiding all of the old text. It should probably only move the view enough to show one or two new characters instead.

Added some changes here: 9625bbca9a044e90e5c591673cedd81d57661efd
Not perfect but definitely more usable


Move shader analysis to Vulkano crate, make available for runtime shaders

- **Breaking** Vulkano-shaders no longer generates a `Shader` struct, but instead provides `load` as a standalone function that returns `Arc<ShaderModule>` directly.
- **Breaking** Vulkano-shaders no longer generates a function for each entry point. Entry points are now retrieved using the `entry_point` method of `ShaderModule`.
- **Breaking** The `shader` module is moved to the crate root, and `spirv` is now a submodule of it.
- **Breaking** `ShaderModule::new` is renamed to `from_bytes` to match the existing `from_words`.
- **Breaking** `ShaderModule` now parses and analyses the shader provided to it on construction, checks whether the shader is compatible with the device, and gathers data such as descriptor sets and input/output interfaces directly from its code. To provide this data yourself as before, and avoid parsing, you can use the `_with_data` constructors.
- **Breaking** `ComputeEntryPoint` and `GraphicsEntryPoint` are removed, as are the functions on `ShaderModule` that generate them. Instead, you can look up an entry point using the `entry_point` method.

- Added support for additional shader types in `ShaderStage`, `ShaderStages` and `PipelineStages`.

Fixes #1558, #1673. This moves most of the shader analysis code from Vulkano-shaders to the main Vulkano crate, so that it can be used for runtime-loaded shaders as well. ShaderModule will now analyse the code given to it by default, but it's still possible to provide the data manually if you want. This is done by Vulkano-shaders to avoid having to parse and analyse the code each time the program is run, so you don't have to pay a performance penalty for using Vulkano-shaders.
The new code also checks compatibility between the shader (SPIR-V capabilities and extensions) and the device. For this, I added more code to autogen that generates checks from vk.xml, which already contains information about device requirements for each SPIR-V capability and extension.
The rest of the changes are mainly rearranging and changes of APIs to facilitate this. Shader entry points can now be retrieved at runtime via a string, based on the data collected from the shader. Vulkano-shaders generates its code a little differently.

@Rua Thank you for your hard work! It's amazing!
I only did a brief code review at this moment, left a few comments to discuss and maybe to fix. I will take a closer look later and do some tests.
In addition to that I have a concern about the generated entry-point reusability. Previously the user could load the module, and then reuse it's main entry point every time they create a pipeline. WIll they be able to the same in he new implementation, or the entry point generation in place is unavoidable?

EntryPoint is not very expensive to generate. The entry_point method will borrow the ShaderModule, look up the name in a HashMap, and generate a new CString (which admittedly could be done in the pipeline builder, but performance wise it doesn't matter where it's done).

@Rua Can you fix merging conflicts, please?

Done.

@Rua I adapted my project's code to these changes, but I'm receiving the following error:
SpirvExtensionNotSupported {
             extension: "SPV_EXT_descriptor_indexing",
             reason: RequirementsNotMet(
                 [
                     "Vulkan API version 1.2",
                     "device extension `ext_descriptor_indexing`",
                 ],
             ),
         }

There was no such error before, and it worked fine. If I raise the Instance version to 1.2 the error is gone, but what I don't understand is that it works regardless to the Vulkan version specified in the vulkano_shaders macro(i.e. it work with 1.1 and 1.2 both).

Do you have the ext_descriptor_indexing extension enabled on your device? That's actually a requirement in the spec, listed here and in vk.xml. I guess that Vulkano-shaders did not previously check for this, but the PR is behaving correctly.

@Rua I just tried to enabled it(for Vulkan 1.1). And it asked to enable "khr_maintenance3"(ExtensionRestrictionNotMet(ExtensionRestrictionError { extension: "ext_descriptor_indexing", restriction: RequiresDeviceExtension("khr_maintenance3") })). So I did it too. Now the error is:
FeatureRestrictionNotMet(
             FeatureRestrictionError {
                 feature: "descriptor_indexing",
                 restriction: RequiredByExtension(
                     "ext_descriptor_indexing",
                 ),
             },
         )

I guess that Vulkano-shaders did not previously check for this, but the PR is behaving correctly.

How so? I suppose, the Instance/Device of Vulkan 1.2 shouldn't let the user load the shader that requires Vulkan 1.2 and/or it's extensions, and explicitly specifies version 1.1.

And if you enable the feature too, what happens then? The feature requirement is also according to spec; some extensions require a feature to be enabled when the extension is enabled. ext_descriptor_indexing requires the feature descriptor_indexing, you can see it in the Vulkano documentation: https://docs.rs/vulkano/0.26.0/vulkano/device/struct.Features.html#structfield.descriptor_indexing.

How so? I suppose, the Instance/Device of Vulkan 1.2 shouldn't let the user load the shader that requires Vulkan 1.2 and/or it's extensions, and explicitly specifies version 1.1.

It's not really a matter of the shader version itself as far as I can tell. Rather, the shader is compiled with certain SPIR-V capabilities and extensions enabled, and those in turn require matching features and extensions on the Vulkan device. If you look at the SPIR-V assembly code of your shader, you will see the OpCapability and OpExtension instructions. Vulkano sees those when it parses the shader and checks the device to make sure the proper support for them is enabled. Those instructions are in turn generated by shaderc based on the glsl code you've written.

@Rua Sorry, what do you mean by enabling the feature?

When you create a device, you pass in a Features struct. You enable a feature by setting the appropriate member of the struct to true.

@Rua Got it. Now it says that the feature is not supported. It looks very strange, because all of it works with Vulkan 1.2 and without explicitly enabling of these features and extensions.

Anyway, I don't think this is a blocker for the PR merging.

I think I see where the problem lies. The descriptor_indexing feature must indeed be enabled if the extension is enabled:

If ppEnabledExtensions contains "VK_EXT_descriptor_indexing" and the pNext chain includes a VkPhysicalDeviceVulkan12Features structure, then VkPhysicalDeviceVulkan12Features::descriptorIndexing must be VK_TRUE

However, VkPhysicalDeviceVulkan12Features is a Vulkan 1.2 structure, so it's not available on Vulkan 1.1 and therefore this VUID will never apply. The logic for checking this doesn't take the version into account, so that's a bug that still needs fixing.

Understood. ok, I thought there is something with my gpu driver.
Anyway, PR is merged. Thanks for all the fixes and explanations!


2.1.1 confusion

In section 2.1.1. Merkle Particia Trees you write

This allows the state data structure itself to represent not only the intrinsically correct paths in the data, but also the requisite cryptographic proofs which go into making sure that a piece of data was valid in the first place.

To me the highlighted part means that the modified tree allows for cryptographic proofs, implying that a non-modified tree would not allow this. If this was the intent, then in my opinion it is not true - any Merkle tree allows such proofs. This article from the official Ethereum wiki states that Merkle Patricia Trees were chosen because of optimization opportunities.

that link is to https://github.com/chronaeon/beigepaper/issues/url did you mean to link to the wiki?

Oops 😅
I have edited the hyperlink.

@morenoh149 thanks for the link!
@rkapka good points -- how would you re-phrase it?
I'm merely trying to drag the line between inherent vagueness and too much detail, and in this case it looks like I missed the point entirely! I thank you for this correction.
I'll link the appropriate section here:

Optimization
Merkle Patricia tries solve the inefficiency issue by adding some extra complexity to the data structure. A node in a Merkle Patricia trie is one of the following:
NULL (represented as the empty string)
branch A 17-item node [ v0 ... v15, vt ]
leaf A 2-item node [ encodedPath, value ]
extension A 2-item node [ encodedPath, key ]
With 64 character paths it is inevitable that after traversing the first few layers of the trie, you will reach a node where no divergent path exists for at least part of the way down. It would be naive to require such a node to have empty values in every index (one for each of the 16 hex characters) besides the target index (next nibble in the path). Instead we shortcut the descent by setting up an extension node of the form [ encodedPath, key ], where encodedPath contains the "partial path" to skip ahead (using compact encoding described below), and the key is for the next db lookup.
In the case of a leaf node, which can be determined by a flag in the first nibble of encodedPath, the situation above occurs and also the "partial path" to skip ahead completes the full remainder of a path. In this case value is the target value itself.
The optimization above however introduces some ambiguity.
When traversing paths in nibbles, we may end up with an odd number of nibbles to traverse, but because all data is stored in bytes format, it is not possible to differentiate between, for instance, the nibble 1, and the nibbles 01 (both must be stored as <01>). To specify odd length, the partial path is prefixed with a flag.

Based on this reading, it seems clear to me that the Beigepaper would benefit by including the gist of this whole excerpt and excluding my initial assertion that MP trees somehow contribute to the overall veracity of the Blockchain data structure.


🎁: Generate a shareable link to the current state of the workspace and application

Expected outcome

It should be possible to generate a shareable link with the current state of the workspace and the applied filters, fields, sorting and group by for Table and Garden view.
Having it humanly readable is a bonus - but not a requirement.
Business Value / Developer Experience

It will enable a dashboard to link to existing application and the data foundation for KPIs. This is particularly interesting for the current JC Portal and the new Landing Page / Dashboard.
Acceptance Criteria

Feature: Generate a shareable link of current state of the workspace state and application
Scenario: Generate link

[ ] When In the workspace, and Clicking the Share button
[ ] the user will see a quick notification that the url is copied into the clipboard

Scenario: Use the link

[x] When applying the link
[x] the user gets the exact same state in the workspace and the application as when generating the link

This is considered a POC for JC - but a generic one is needed for Project Portal.
@Gustav-Eikaas you may consider linking to the Project Portal rather than JC Portal.

Scenario 2: Is kinda implemented in JC portal Dev env

hmm - I see that PBI also supports bookmark.
Thoughts
If we had pre-created shared bookmarks which everyone had - which was categorized as KPI related etc - then the Dashboards/KPIs in around in the system could call those bookmarks.

I do get a parallel to PCS Saved Search.

Closed for now.


Con Travel: Links to renewals/replacements service

There's some work on start pages in the other branches, so expect conflicts when those are merged, and at that point I'll do some more work to clean up the page in general, but this is what it looks like with those links in:

Have also added a line about linking to renwals/replacements services on the pattern page, under start page.

@sanjaypoyzer were there any plans to do a similar thing with parking permits - so links to renew permit & replace a lost permit?

Yep, there's a separate issue for it so will do it separately
On Fri, 17 Feb 2017, 09:20 kaydale<EMAIL_ADDRESS>wrote:

@sanjaypoyzer https://github.com/sanjaypoyzer were there any plans to
do a similar thing with parking permits - so links to renew permit &
replace a lost permit?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alphagov/verify-local-patterns/pull/154#issuecomment-280598543,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6qyyCt416eOBK5qOk-r7D487KbgRmJks5rdWZDgaJpZM4MDSa-
.

--
Sanjay Poyzer
Twitter: @sanjaypoyzer
Tel: +44 7895 123 673


Update jtreg to 5.1 for jdk 15 and 15+

Signed-off-by: Sophia Guo<EMAIL_ADDRESS>

Updated to include all versions.


Added new sections to the Selenium GRID page

Added Specifying the Port, Common Errors, Troubleshooting sections to the Selenium GRID page

Thanks Diemol


Fix typo on Guide.md

Ha – my original intention was "then just make sure it's ..." But this works too!

Thanks :+1:


Travis fixes (mostly ElasticSearch)

Noticed a lot of issues in Travis, trying this

Thanks for looking into this.

Thanks!!

interesting/scary that our tests have been running on python 3.4 only for the last month or so. luckily there were no regressions in python 2.7/3.3

@erikbern, nah, that's not true. It just says 3.4 in the label on Travis. It's tox that decides the python version, which is taken from the .travis.yml matrix section.

The python --version command returned 3.4 as well

That's expected, I think. When Travis says it's 3.4, it only means that the system python will be python 3.4. The first thing tox does is to install a python virtual env with a pinned python version.


Feature Request: Managed Certificates

We want to host a range of client apps and our API in ACA, which all needs public ingress and custom domain names. We currently use Azure App Service which supports automatic refresh of TLS binding certificates from Key Vault.
We use an automated Let's Encrypt function app, to issue and renew our certificates every 60 days, which stores the certs in Key Vault and it is too cumbersome for us to manually download new certificates from Key Vault and upload them to ACA that often.
So we would like for ACA to support the same auto-refresh of certificates from Key Vault as App Service does.
We know that alternatively we could use FrontDoor, CloudFlare or other reverse proxy service, but that's an extra tier in, our already growing environment, with extra work, cost.
TIA
:-) Henrik

On our roadmap but can't share an ETA yet.

Great - Kendall said as much during a session at the Build event, just couldn't find it here amongst the roadmap items, so just wanted to spot a light on it.


Added hovering resume templates

Added some hovering effects to the resume templates.
https://user-images.githubusercontent.com/91081814/195631211-69b52caa-afa4-4649-8801-de1ab25902c2.mp4

Make cursor pointer when hovering over the resumes.
Also add different resumes. I will then merge your PR

I will add the cursor pointer while hovering. But the resumes are the ones which were already there on the site. I didn't add them. I just made the effects. I will do the changes required.

Added cursor pointer while hovering and added different resume templates.
https://user-images.githubusercontent.com/91081814/195662430-23147477-9a24-4180-9da9-702a49fc0c41.mp4

Please review my pr.

I cann't see the Navigate to top button in the preview.
Also Please add good looking resumes

Its visible for me. Please check the deployment link.
https://resume-maker-f02q41b9q-killerraj369.vercel.app/
The button will appear only if you scroll down a bit from the main page.
Regarding the resume template part I will try to find some better pics. But it would be great if you can assign it for no code developers.

Ok then.


Add optional options to client

Adds an configuration dataclass:
usage:
client = weaviate.Client(
    "http://localhost:8080",
    additional_config=Configuration(
        grpc_port_experimental=port,
        connection_config=ConnectionConfiguration(
            session_pool_connections=100, session_pool_maxsize=100
        ),
    ),
)

This currently only adds two options, but this would be a good starting point in adding more knobs in a structured way.
Long-term (in version 4) we could move more options into this dataclass, bur currently we should not introduce any breaking changes.

Codecov Report
Patch coverage: 100.00% and project coverage change: -0.03 :warning:

Comparison is base (0e33223) 96.01% compared to head (c120457) 95.99%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #302      +/-   ##
==========================================
- Coverage   96.01%   95.99%   -0.03%
==========================================
  Files          63       64       +1
  Lines        7402     7413      +11
==========================================
+ Hits         7107     7116       +9
- Misses        295      297       +2

Impacted Files
Coverage Δ

integration/test_grcp.py
97.29% <100.00%> (+0.15%)
:arrow_up:

test/test_client.py
100.00% <100.00%> (ø)

weaviate/client.py
98.55% <100.00%> (+0.04%)
:arrow_up:

weaviate/connect/connection.py
90.21% <100.00%> (-0.86%)
:arrow_down:

weaviate/options.py
100.00% <100.00%> (ø)

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

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

Some feedback: I'm thinking maybe it would be good to be shorter? Less typing.
client = weaviate.Client(
    "http://localhost:8080",
    config=Config(
        grpc_port_experimental=port,
        conn_config=ConnectionConfiguration(
            session_pool_connections=100, session_pool_maxsize=100
        ),
    ),
)

Alternatively, just put all these settings as part of the client?
client = weaviate.Client(
    "http://localhost:8080",
    grpc_port_experimental=port,
    session_pool_connections=100,
    session_pool_maxsize=100
)

I cannot say that short argument names would be better, this object is a one time creation. With modern IDEs that support autocomplete I do not see how this can be a problem. It is better to be over-descriptive than under-descriptive. Also for me it look weird when some parameters do not have abbreviations and some do.

One benefit of this approach is that we could expose all config options to libraries. Right now, libraries using Weaviate often package the client in such a way that you cannot add all config options i.e. LangChain and Auto-GPT, which can be frustrating.
However it will add confusion if we add this now, as users will not see why additional_config has GRPC and session info but nothing else.
Does it makes sense to do a single breaking change at some point where all config options are moved to the new format. Maybe this could coincide with switching to a client supporting async queries?

HI all,
thanks for your feedback!
@kmulka-bloomberg
The problem is that we have already have 8 options directly in the client. With the new ones, it would be 11 which feels like to much. Looking at the list of options we currently have, I think only three (url + auth + additional_headers and maaybe timeout) are used regularly by our users and the rest only by a tiny fraction. I think it would greatly improve the UX and reduce the "too many choices"-confusion by moving the extra stuff somehwere else.
I agree that some words are a bit long, maybe using Config instead of Configuration would make things shorter and still be 100% clear?
@trengrj
My current idea (totally up for discussion) is to leave the important ones directly in the client and only move the more advanced ones, but that would be at some point in the future. Async would be nice, let's see 😅


Create Shortcuts which launch RDP connection automatically

Hi
Firstly thanks so much for this great tool! I find it really useful.
I'd like to ask the following:
When setting up a connection to one of the local servers via your tool, it remembers the IP\domain which it has previously connected to. Once the connection is established it'll prompt me for the windows user password. This happens regardless whether I tick "remember me" or not. In a .rdp file you can specify whether you're allowed to save your password or not. Is that also the case here?
Also is it possible to create a file which will contain all the settings and just automatically connect to the server without prompting for a password every time, like for example a .rdp file? I guess I could use any random file extension such as .rdcc and set it shall be always be opened with your app. I just need to know what config to put in there.
Many thanks!

UPDATE: I can just set the .rdp file to be opened with the RDP client downloaded from microsoft..... Thanks a mil!


Implement native dialogs handling (close #451)

/cc @inikulin @AlexanderMoskovkin @VasilyStrelyaev

\r-

lgtm

So far getNativeDialogHistory returns the list of dialogs from the earliest to the most recent one.
What if we reverse that order?
The most common scenario is getting the latest dialog - let it be [0].
And this is also what is implied by the word 'history'.
What do you think? @helen-dikareva @inikulin @AlexanderMoskovkin

So, if I expect just one alert in my test and simply want to handle it, what I write is
t.setNativeDialogHandler(() => {});

which looks... hm...
@helen-dikareva @inikulin @AlexanderMoskovkin

@VasilyStrelyaev Nah, I think it's just fine. We provide some basic generic API on top of which you can build your own if you commonly use it, e.g.:
function expectAlert(t) {
     t.setNativeDialogHandler(() => true);
}

test('yo', t => {
    expectAlert(t);
});

@testcafe-build-bot \retest

@testcafe-build-bot \retest

@testcafe-build-bot \retest

Just blinking tests, please review @inikulin @AlexanderMoskovkin @VasilyStrelyaev

@testcafe-build-bot \retest

\r-

@testcafe-build-bot \retest

lgtm

@testcafe-build-bot \retest

FPR

Overall lgtm, great job! Just some minor issues left.
\r-

Ok, thanks

@testcafe-build-bot \retest

@helen-dikareva Errors now have new format

I just guessed

@testcafe-build-bot \retest

only unstabled qunit, FPR

@testcafe-build-bot \retest

\r-

@testcafe-build-bot \retest

@testcafe-build-bot \retest

Just blinking tests, FPR

@testcafe-build-bot \retest

@testcafe-build-bot \retest

@testcafe-build-bot \retest

@testcafe-build-bot \retest

@testcafe-build-bot \retest

lgtm

\r-

@testcafe-build-bot \retest

FPR

lgtm

lgtm

@kirovboris @georgiy-abbasov @churkin Can you review instead of @AlexanderMoskovkin, please?

-\r

/r-

lgtm

@testcafe-build-bot \retest

@testcafe-build-bot \retest

@testcafe-build-bot \retest

lgtm

lgtm

lgtm


Use gcf and gca to get/create figure axes in qubit graph

I noticed that using dnx.draw_chimera under a plt.subplot(...) would fail because of the use of plt.figure(1) inside draw_qubit_graph.
I think it can be fixed this way.
plt.gcf(): Get the current figure. If no current figure exists, a new one is created using figure().
Then, plt.gca() is also necessary. The cax is OK as is.

looks good!


Pass on supported gun opts in connect()

This change allows users to pass on options supported by gun in a connect() call.
For example, this means that you can use alternative TLS port 2197 without gun guessing that you want TCP transport (add transport => tls), and you can set a longer keepalive than the default 5 seconds.

Hi Ulf,
Thanks a lot for your contribution, could you please fix the Travis complains? after that I will merge it for sure!
thanks

Just in case, @uwiger … the error that travis reports is:

The code in the following (LINE, COL) locations has the same structure: (237, 3), (251, 3).

It's an Elivs error that, unless you can abstract that code into something else that makes sense (probably not), you can "fix" by increasing min_complexity for the dont_repeat_yourself rule in the elvis.config file.

@elbrujohalcon feels like cheating, but you're right - I couldn't easily come up with a refactoring that wouldn't be less readable than the existing code. :)

BTW, I noticed issue inaka/apns4erl#205, which has been around for a while. Since gun defaults to sending keepalives every 5 seconds, I assume that the problem should be resolved. OTOH, a 5-second interval seems a bit eager for an APNs idle ping, right?

As I understand it, the code coverage is reduced due to the changes related to the proxy setup. There don't seem to be any proxy-related test cases in the connection_SUITE.

Since dialyzer run on the test code complained, I moved the gun options under a separate options key.

I guess we can safely ignore codecov… right, @ferigis?

How did you get to a keepalive value of 10000? Trial and error? I'm looking into increasing the default to something more reasonable.

How did you get to a keepalive value of 10000? Trial and error? I'm looking into increasing the default to something more reasonable.

I only used 10 seconds in the test suite. I assumed that we might want to set the value to something much higher, but it's surprisingly hard to find some recommendation on the subject.
I found this article, which admittedly talks about a device being connected to APNS, but it makes sense that Apple shouldn't force mobile, battery-powered devices to ping at intervals of a few seconds.

When device is charging or enough battery, keep-alive is sent every 15-30 minutes.

there is of course also this...:

HTTP/2 ping is a terrible idea. The best we can hope for is that nobody uses it. That boat has sailed already though, as Apple is encouraging the PING frame use for checking the state of TCP connections to their APNS service.

I think the biggest improvement would be to make Gun NOT send the PING if there's been traffic sent or received in that time period. Then maybe set it to 1 minute by default, since there is no real power constraint. So Gun would by default send PING 1 minute after any data was sent or received.
To be honest there probably aren't too many people with mostly idle connections, so it might not make sense for it to be enabled by default. Not having it enabled would help avoid certain issues like too_many_pings. Having written all this I think this makes the most sense.

Is this not merged solely due to Travis CI complaints? Or is there something else missing? I read the whole thread and this seems good to go.


Ranger solr: fix deprecated mergepolicy configs

Ranger solrconfig.xml currently uses deprecated merge options. See "Upgrading from Solr 5.4" section at https://apache.googlesource.com/lucene-solr/+/branch_5x/solr/CHANGES.txt for more details.
What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)
Please review Ambari Contributing Guide before opening a pull request.

Closing PR as it's over 6 months old.


No sound after update Easy Effects to 7.1.3.

Hi, thanks for this project, I've been using it for a long time, and it works perfectly fine until today, I updated Easy Effect to 7.1.3, and now it has no sound, but the sound will come back when I remove presets or exclude the apps. Any help will be appreciated.

Uhm, the problem is not originated by the presets, which are just a bunch of convenient settings for EasyEffects (no audio source change).
The problem you're seeing is more likely to be with audio routing. I've updated to EasyEffects 7.1.3 too but I'm not experiencing the problem.
I'm using the Flatpak version on Ubuntu 20.04, with pipewire instead of PulseAudio.
Unfortunately I'm not very good at troubleshooting the Linux audio stack. The only thing I would suggest is to try uninstalling EasyEffects and its presets, maybe trying the Flatpak version.

Hi @JackHack96, thank you for your reply, and I just reinstalled EasyEffects and presets, now it works perfectly great, thank you so much. And sorry for the late response :)


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter chargemaster for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.chargemaster
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E204] Version "0.11.0" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.
[ ] :heavy_exclamation_mark: [E402] Types of adapter in latest repository and in io-package.json are different "vehicle" !== "energy"

WARNINGS:

[ ] :eyes: [W202] Version of package.json (0.11.0) doesn't match latest version on NPM (0.10.0)

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check at any time by adding the following comment to this issue:
@iobroker-bot recheck
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
Note: This issue replaces issue #512
@mcm1957 for evidence

@ioBroker-Bot recheck

Thanks for contacting me.
I received your request to recheck this repository. I will start doing my work soon.
I will close an existing issue and create a new one if still any issues are to be evaluated and potentially to be fixed.
Thanks for spending your time and working at an ioBroker adapter.
your
ioBroker Check and Service Bot

This issue has been replaced by new isse #514
This issue can be closed.
your
ioBroker Check and Service Bot


integrating yo office updates (#570)

Update Outlook quick start to reflect changes in Yo Office.

Minor updates.

Add 'npm start' command info back to Outlook quick start.

Start of updates to Outlook tutorial.

More tutorial updates (manifest section).

More updates to manifest section of tutorial.

More updates to manifest section of tutorial.

More updates to manifest section of tutorial.

More tutorial updates (image, etc.).

Rewrite tutorial to better leverage components of the OOTB Yo Office project.

Update manifest section.

Update Task Pane sections.

Change to Fabric Core.

Update code designation for commandline code samples.

Minor update to add-ins quick start.

Update 'Define buttons' section of Outlook tutorial.

Update 'First run experience' section and 'UI-les button' section of Outlook tutorial.

Add content about updating webpack.config.js with dialog settings.

Minor update.

Minor update.

Minor update.

Minor update.

Minor update.

fixing folder changes from template update

typo fix

Add insertDefaultGist function to global scope

Minor formatting

Docs Build status updates of commit 5f7a190:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/add-ins/addin-tutorial.md
:white_check_mark:Succeeded

docs/add-ins/images/addin-tutorial/add-in-buttons-for-owa.png
:white_check_mark:Succeeded

docs/add-ins/images/addin-tutorial/add-in-buttons-owa.png
:white_check_mark:Succeeded

docs/add-ins/images/addin-tutorial/button-and-pane-1.png
:white_check_mark:Succeeded

docs/add-ins/images/addin-tutorial/button-and-pane.png
:white_check_mark:Succeeded

docs/add-ins/images/addin-tutorial/yeoman-prompts-2.png
:white_check_mark:Succeeded

docs/add-ins/images/addin-tutorial/yeoman-prompts.png
:white_check_mark:Succeeded

docs/add-ins/images/quick-start-button-2.png
:white_check_mark:Succeeded

docs/add-ins/images/quick-start-task-pane-1.png
:white_check_mark:Succeeded

docs/add-ins/images/quick-start-yo-prompts.png
:white_check_mark:Succeeded

docs/add-ins/images/yo-office-outlook.png
:white_check_mark:Succeeded

docs/add-ins/quick-start.md
:white_check_mark:Succeeded

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


Measure dart runtime mode (mixed versus sound) during hot reload process

This requires reading from the newly added isolate flags object in https://github.com/dart-lang/sdk/issues/43588 . This is blocked by the flutter engine not supporting sound mode.

This was marked as fixed, but I tried to use the new API today and it did not work correctly, see https://github.com/dart-lang/sdk/issues/43588

Issue might be in the flutter/engine

This needs to be done per-isolate

This is now blocked by package:dwds, since that is pinned to an earlier VM Service

We managed to roll package:vm_service last week which will unblock adding these APIs

This is done in the null-safety analysis event category.

This is done in the null-safety analysis event category.


Remove request for U2 - With Or Without You

Requesting an official voting to remove U2 permanently from the list.
https://www.strawpoll.me/16274134

Hahaha what's the reason? I guess I kinda agree that the drums are a bit too much at some point

Ho, I guess I voted incorrectly by accident. Anyway, I'll merge this one.


Unauthorized client

My integration stopped working due to the client expiring.  I followed the docs to create a new app and client secret.  Set  permissions as I want them.  Upon restart and attempt to authorize, I get this error when I click the Link O365 account:
unauthorized_client: The client does not exist or is not enabled for consumers. If you are the application developer, configure a new application through the App Registrations in the Azure Portal at https://go.microsoft.com/fwlink/?linkid=2083908
I didn't see a similar issue

You didn't need to create a new app, just a new secret.
I would start again, make sure you are logging in with the correct details and follow the instructions careful. Also be careful with the client id and secret you configure the integration

It's likely you have copied the Client id or secret wrong.

I already redid the secret for sure. I do them again.
\Greg

From: RogerSelwyn @.>
Sent: Monday, April 15, 2024 5:22:52 PM
To: RogerSelwyn/O365-HomeAssistant @.>
Cc: uSlackr @.>; Author @.>
Subject: Re: [RogerSelwyn/O365-HomeAssistant] Unauthorized client (Issue #220)
It's likely you have copied the Client id or secret wrong.
—
Reply to this email directly, view it on GitHubhttps://github.com/RogerSelwyn/O365-HomeAssistant/issues/220#issuecomment-2057832376, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGEO6Z7R7PLEZBWS7AISSADY5RAKZAVCNFSM6AAAAABGIDE45SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJXHAZTEMZXGY.
You are receiving this because you authored the thread.Message ID: @.***>


optional deps should be dev deps?

We were getting strange issues:
yarn install v1.8.0
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
warning cs-core-api > ember-lodash > semantic-release > @semantic-release/npm > npm ><EMAIL_ADDRESS>this version has a breaking change. use 1.1.0 or upgrade to latest
error Couldn't find package<EMAIL_ADDRESS>required by "<EMAIL_ADDRESS>on the "npm" registry.

Which lead me to question, why are the CI/deployment scripts part of the dependencies. Shouldn't they be moved to devDependencies?

our yarn.lock exploded when updating to the newest version too.

Just noticed this too when checking the yarn.lock diff.

fix in the pipe for this. New release going out tonight

released as 4.19.2