Animating images loaded into flash memory?

I was wondering if it might be possible to animate an image loaded into flash memory. If so, some examples or demos would be helpful to look at.
Thanks!

https://www.youtube.com/watch?v=-h9Vm0Ow_Is


Edit to install_dep_packages.sh

I could be incorrect but the build dependences (./install_dep_packages.sh) script does not include -j for when multiple threads used and are passed to make in the build scripts. I  made the changes to successfully build on ubuntu 20.04.

Is your PR pushing 103 commits because you've rebase OVS? Either way, can you clean this up to only include the commit you're pushing to address the issue? Thanks!


add new strategy [dps-nft]

Fixes # .
Changes proposed in this pull request:

Oh also check

Hey @andreibadea20 strategy erc721 should work in your case, please try and let me know if you face any issue

Hello! Sorry to bother you again, but I just made a new pull request and I
want to explain that my strategy is slightly different from ERC721, because it
calculates the voting power depending on the nfts number of each user + the
number of nfts claimed and locked at the time of voting and I need to get
the information about nfts from 2 different contracts, using a subgraph.
Thanks for your time!
Have a nice day!
On Tue, 28 Jun 2022 at 21:40, Chaitanya @.***> wrote:

Oh also check
Hey @andreibadea20 https://github.com/andreibadea20 strategy erc721
should work in your case, please try and let me know if you face any issue
—
Reply to this email directly, view it on GitHub
https://github.com/snapshot-labs/snapshot-strategies/pull/664#issuecomment-1169090783,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZG7H2ZWQR3VXGL6IILIACLVRNBIDANCNFSM5ZIBFH5A
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add the resume download for downloading script

This is useful when we want to finish a download started by a previous instance of wget. For instance,  if my internet connection times out for some reason, the wget process will automatically resume from where it was interrupted.

:+1:


Update SDK for CMK API.

What
This PR updates SDK for CMK API.

That's a great idea! I did try to do it so I guess the interfaces stayed the same.

Could you do a release to include this pr? thanks!

sure thing: https://github.com/confluentinc/ccloud-sdk-go-v2/releases/tag/cmk%2Fv0.6.0


[viki] HTTP Error 422: Unprocessable Entity

[debug] Command-line config: ['-v', 'https://www.viki.com/videos/1080865v', '--c
ookies', 'C:UsersNomaanDesktopcookies.txt']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] yt-dlp version 2021.06.23
[debug] Python version 3.9.5 (CPython 64bit) - Windows-10-10.0.19043-SP0
[debug] exe versions: ffmpeg 4.4-full_build-www.gyan.dev, ffprobe 4.4-full_build
-www.gyan.dev
[debug] Proxy map: {}
[debug] [viki] Extracting URL: https://www.viki.com/videos/1080865v
[viki] 1080865v: Downloading video JSON
ERROR: Unable to download JSON metadata: HTTP Error 422: Unprocessable Entity (c
aused by <HTTPError 422: 'Unprocessable Entity'>); please report this issue on
https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; s
ee  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp w
ith the --verbose flag and include its complete output.
  File "C:\Users\Nomaan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3
.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\yt_dlp\extract
or\common.py", line 679, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "C:\Users\Nomaan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3
.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\yt_dlp\Youtube
DL.py", line 3089, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.152
0.0_x64__qbz5n2kfra8p0\lib\urllib\request.py", line 523, in open
    response = meth(req, response)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.152
0.0_x64__qbz5n2kfra8p0\lib\urllib\request.py", line 632, in http_response
    response = self.parent.error(
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.152
0.0_x64__qbz5n2kfra8p0\lib\urllib\request.py", line 561, in error
    return self._call_chain(*args)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.152
0.0_x64__qbz5n2kfra8p0\lib\urllib\request.py", line 494, in _call_chain
    result = func(*args)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.152
0.0_x64__qbz5n2kfra8p0\lib\urllib\request.py", line 641, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)

please follow the issue template and contributing guidelines
In any case... I can reproduce it too, even with the test video
yt-dlp -F -v https://www.viki.com/videos/1175236v-choosing-spouse-by-lottery-episode-1
[debug] Command-line config: ['-F', '-v', 'https://www.viki.com/videos/1175236v-choosing-spouse-by-lottery-episode-1']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] yt-dlp version 2021.06.23 (exe)
[debug] Plugin Extractors: ['SamplePlugin']
[debug] Python version 3.8.10 (CPython 64bit) - Windows-10-10.0.19043-SP0
[debug] exe versions: ffmpeg 2021-06-09-git-e01bf559df-full_build-www.gyan.dev, ffprobe 2021-06-09-git-e01bf559df-full_build-www.gyan.dev
[debug] Proxy map: {}
[debug] [viki] Extracting URL: https://www.viki.com/videos/1175236v-choosing-spouse-by-lottery-episode-1
[viki] 1175236v: Downloading video JSON
ERROR: Unable to download JSON metadata: HTTP Error 422: Unprocessable Entity (caused by <HTTPError 422: 'Unprocessable Entity'>); please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
  File "yt_dlp\extractor\common.py", line 679, in _request_webpage
  File "yt_dlp\YoutubeDL.py", line 3089, in urlopen
  File "urllib\request.py", line 531, in open
  File "urllib\request.py", line 640, in http_response
  File "urllib\request.py", line 569, in error
  File "urllib\request.py", line 502, in _call_chain
  File "urllib\request.py", line 649, in http_error_default

Looks like the main culprit is the hardcoded app version (latest one from the site is 4.0.74, but seems like it can go as far back as 3.1.0)

[debug] Command-line config: ['-v', 'https://www.viki.com/videos/1080865v', '--c
ookies', 'C:UsersNomaanDesktopcookies.txt']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] yt-dlp version 2021.06.23
[debug] Python version 3.9.5 (CPython 64bit) - Windows-10-10.0.19043-SP0
[debug] exe versions: ffmpeg 4.4-full_build-www.gyan.dev, ffprobe 4.4-full_build
-www.gyan.dev
[debug] Proxy map: {}
[debug] [viki] Extracting URL: https://www.viki.com/videos/1080865v
[viki] 1080865v: Downloading video JSON
ERROR: Unable to download JSON metadata: HTTP Error 422: Unprocessable Entity (c
aused by <HTTPError 422: 'Unprocessable Entity'>); please report this issue on
https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; s
ee  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp w
ith the --verbose flag and include its complete output.
File "C:\Users\Nomaan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3
.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\yt_dlp\extract
or\common.py", line 679, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "C:\Users\Nomaan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3
.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\yt_dlp\Youtube
DL.py", line 3089, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.152
0.0_x64__qbz5n2kfra8p0\lib\urllib\request.py", line 523, in open
response = meth(req, response)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.152
0.0_x64__qbz5n2kfra8p0\lib\urllib\request.py", line 632, in http_response
response = self.parent.error(
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.152
0.0_x64__qbz5n2kfra8p0\lib\urllib\request.py", line 561, in error
return self._call_chain(*args)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.152
0.0_x64__qbz5n2kfra8p0\lib\urllib\request.py", line 494, in _call_chain
result = func(*args)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.152
0.0_x64__qbz5n2kfra8p0\lib\urllib\request.py", line 641, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)

please follow the issue template and contributing guidelines!!
In any case... I can reproduce it too, even with the test video
yt-dlp -F -v https://www.viki.com/videos/1175236v-choosing-spouse-by-lottery-episode-1
[debug] Command-line config: ['-F', '-v', 'https://www.viki.com/videos/1175236v-choosing-spouse-by-lottery-episode-1']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] yt-dlp version 2021.06.23 (exe)
[debug] Plugin Extractors: ['SamplePlugin']
[debug] Python version 3.8.10 (CPython 64bit) - Windows-10-10.0.19043-SP0
[debug] exe versions: ffmpeg 2021-06-09-git-e01bf559df-full_build-www.gyan.dev, ffprobe 2021-06-09-git-e01bf559df-full_build-www.gyan.dev
[debug] Proxy map: {}
[debug] [viki] Extracting URL: https://www.viki.com/videos/1175236v-choosing-spouse-by-lottery-episode-1
[viki] 1175236v: Downloading video JSON
ERROR: Unable to download JSON metadata: HTTP Error 422: Unprocessable Entity (caused by <HTTPError 422: 'Unprocessable Entity'>); please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
  File "yt_dlp\extractor\common.py", line 679, in _request_webpage
  File "yt_dlp\YoutubeDL.py", line 3089, in urlopen
  File "urllib\request.py", line 531, in open
  File "urllib\request.py", line 640, in http_response
  File "urllib\request.py", line 569, in error
  File "urllib\request.py", line 502, in _call_chain
  File "urllib\request.py", line 649, in http_error_default

Looks like the main culprit is the hardcoded app version (latest one from the site is 4.0.74, but seems like it can go as far back as 3.1.0 for now)

Is there any solution to this? A fix?

EDIT: Changing the app version seems to have fixed the initial error, but it seems like there is another underlying issue with format extraction (everything is in mhtml now)
I'm definitely not experienced in this site either, so hopefully someone else could pick this up?

i got this link - https://www.viki.com/videos/1080865v to download
using the HTTP-TRACKER firefox addon  and finding the mp4
but the file is DRM encrypted

There's still hope. Just wait for the dev. They might just busy
This is not drm.

Try this url:
Video Url >> https://m-content6-viki.s.llnwi.net/1180911v/dash/1180911v_dash_high_1080p_32327f_2107020646_track1_dashinit.mp4
Audio Url >> https://m-content6-viki.s.llnwi.net/1180911v/dash/1180911v_dash_high_1080p_32327f_2107020646_track2_dashinit.mp4

i got this link - https://www.viki.com/videos/1080865v to download
using the HTTP-TRACKER firefox addon and finding the mp4
but the file is DRM encrypted

I could give you the download links. Which episode?

i got this link - https://www.viki.com/videos/1080865v to download
using the HTTP-TRACKER firefox addon and finding the mp4
but the file is DRM encrypted

All of viki videos are DRM protected already.
but non drm still exist but using another method and android api

Even the example videos seems to have DRM now. Unless someone can provide examples without DRM, the site will no longer be supported

but non drm still exist but using another method and android api

That is not the least bit helpful. Explain the method so that someone can have a look at implementing it @zackmark29

Even the example videos seems to have DRM now. Unless someone can provide examples without DRM, the site will no longer be supported

but non drm still exist but using another method and android api

That is not the least bit helpful. Explain the method so that someone can have a look at implementing it @zackmark29

Yes I'm trying now to implement the method. But since this is my first time to edit ydl codes, this might be a little ugly :)

Yes I'm trying now to implement the method.

Don't worry too much about it. We can fix it in reviews. Once you have a working implementation, feel free to open a PR

Yes I'm trying now to implement the method.

Don't worry too much about it. We can fix it in reviews. Once you have a working implementation, feel free to open a PR

This is good now I think.
I'll fix now the subtitle

@pukkandan can you take a look? https://github.com/yt-dlp/yt-dlp/pull/473


Launcher converter vm2domain refactor some network parts

What this PR does / why we need it:
Refactor iface multi queue, network indexing and extract SRIOV hostdev creation.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/test all

/retest

/retest

/sig network

/test all

/uncc  dhiller , danielBelenky
/cc @ormergi

/test all

/uncc dhiller danielBelenky

/cc @AlonaKaplan @enp0s3

I'm only concerned that with this change we are moving the discovery and handling of sriov pci addresses to the converter, which in my eyes should stay clean from environment-related operations

@vladikr @AlonaKaplan , as the SRIOV mapping is debatable, I removed it from this PR and will handle it in a following one.
That one also relates to the SRIOV migration effort, so it will be good to separate it.
If you have time to look at this now again, I will appreciate it.

/retest

change: Answered comments.
(unfortunately I messed something up and the push includes a rebase)

/retest

/retest

/approve

/lgtm


Clean production data for other environments

The data we collect has changed (grown, mostly) since this data migration logic was last used, and so we aren't removing all the real personal data that we should.
We delete all draft things because they've never been made public and we try to remove real names and email addresses where we've asked for them:

Draft briefs are deleted
All framework agreements are deleted
All brief responses are deleted
Two more fields are added to the declaration because we need them for the updated signing flow

Gonna merge this soon because I've run it a few times and smoothed out all the kinks.

Yeah, go for it, it looks good 👍


Failed to Connect to external Postgres database

Hello,
I have postgres database setup on Azure and I am able to connect to it with psql.
When I am setting below configurations in values.yaml, I am getting error "Can not connect to database. Please check connectivity and settings (see the properties prefixed by 'sonar.jdbc.')."
Values.yaml:
jdbcUrlOverride: "jdbc:postgresql://<azure db server>:5432/<azure database>”
postgresql:
  enabled: false
  postgresqlServer:  "<azure db server>"
  postgresqlUsername: "<azure db user>@<azure db server>"
  postgresqlDatabase: "<azure database that is already created>"
  postgresqlPassword: "<azure database password>"

elasticsearch:
   configureNode: false
   bootstrapChecks: false

initSysctl:
  enabled: false

Are there any other configurations required for establishing connection? where can I see properties set for sonar.jdbc as mentioned in error?

@Shruti-R  I'm also using Azure Postgresql, there is a known issue with GSS requests.
Try adding gssEncMode=disable as described in this post: https://community.sonarsource.com/t/sonarqube-upgrade-8-4-to-8-5-fail-to-connect-to-azure-postgresql-database/33411

thanks @etiennetremel that helps


customize OPTIONS method return for work around CROS

Hi Julien,
Currently, I write service interface with httprouter and VUE as my web. Then I found, chrome will send OPTIONS method for the request first to check, then POST it. For httprouter, It has the setting for   HandleOPTIONS, but it just return response with default one. So  I need to override every url with OPTIONS method.

Want to know, if it's possible to override customized default OPTIONS method response for httprouter?

Found the merged PR ：https://github.com/julienschmidt/httprouter/pull/190， I just need to pull the lastest code


When FutureW is used as an Applicative Functor, ap should execute asynchronously / non-blocking

Using ap(  ) on a FutureW instance is currently blocking.
Non-blocking behaviour is expected on Futures.

Fixed in https://github.com/aol/cyclops-react/pull/243


Converting HTTPBody data to string for access signature

I noticed any of my requests containing parameters using the API key auth method were receiving an ACCESS_SIGNATURE does not validate error from the sandbox api. Found that your toBeSigned variable was not converting the HTTPBody data to a string properly.

Thanks for this fix!


Update Makefiles to new dune-based F*

This is a companion PR to FStarLang/FStar#2815
With F* being built with dune, the structure and location of the F* libraries have changed: fstarlib and fstar-compiler-lib both become fstar.lib, and are now located in $FSTAR_HOME/lib/fstar/lib/fstar_lib.cmx* instead of $FSTAR_HOME/bin/*.cmx*.
Thus, this PR fixes the Makefiles of Karamel, krmllib and tests to invoke the OCaml compilers and linkers with the right libraries and with an appropriate OCAMLPATH.
In this process, this PR also fixes the way FSTAR_HOME is used, allowing Karamel to be built and tested even if the user installs F* via opam and does not set FSTAR_HOME.
This PR makes everest green (cf. project-everest/everest@925043549b2573160e93a23fab3abd10f969e70a)
Once this PR is approved, I'll merge it after merging the corresponding F* PR. Thanks in advance!
NOTE: This PR does NOT change the way Karamel is built. To track the conversion of Karamel itself to dune, please see #212 (in progress)

This looks good, thanks. But the build of krml still depends on ocamlbuild, for tests/ctypes ... do you think this could be fixed as part of this PR? That way, we could completely deprecated ocamlbuild for the Everest build, which would be a huge win and would simplify maintenance going forward.

I know, but I still need to figure out how to do these tests/ctypes, and I don't want that hard piece to block the merge of the F* PR (which has been around for 3 weeks already.) So I'd like to merge this PR first, separately from #212, with separate PRs also in HACL* and elsewhere. This way, if anything breaks, we can more easily track whether it comes from the new F* dune build or the new Karamel dune build.
Thanks again!


Access Issue: X-ray Spine Dataset Download Link Not Working

Hi,
Thank you for your excellent work and the comprehensive evaluation presented in your paper and repository. I am currently trying to access the X-ray spine dataset referenced in your study to validate your approach. However, the link provided for the dataset appears to be broken or inaccessible.
May you please provide an alternative link to the dataset, or share the dataset via email if possible?
My email address is<EMAIL_ADDRESS>I appreciate your support and look forward to your response.
Best regards,
Marawan Elbatel

Thank you for your interest in our work and for reaching out regarding the X-ray spine dataset. Unfortunately, I do not have the permission to share the dataset directly. For access to the dataset, I kindly recommend contacting Dr. Shuo Li directly via his email<EMAIL_ADDRESS>or Dr. Wang (lswang@xmu.edu.cn). They may be able to provide you with further assistance regarding your request. Thanks for your understanding.

Thanks for your prompt response and guidance.


Time out on bluesky opt-ins?

I followed @ap.brid.gy from my bluesky handle @starrwulfe.xyz around 6 hours ago and still no show at https://fed.brid.gy/bsky/starrwulfe.xyz.

Are there any time outs?
Is there a way to reset and re-follow?
Can a confirmation mention/DM be made for those doing a follow so we know the backend is up and ready?

(These also apply to the AP side as well if possible.)

I'm having the same problem.

Sorry all! I'll look.

I am having this issue with @hcj.vibes.cool

Yup, sorry all, there are a number of missing Bluesky accounts that followed ap.brid.gy but haven't been bridged. I'll work on those.

I did a first pass at backfilling all of these missing accounts.

I'm up and running since this time yesterday actually. Feel free to close
whenever it's complete on your end.
On Sun, May 5, 2024 at 10:27 AM Ryan Barrett @.***>
wrote:

I did a first pass at backfilling all of these missing accounts.
—
Reply to this email directly, view it on GitHub
https://github.com/snarfed/bridgy-fed/issues/997#issuecomment-2094830715,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADMUUMUGO4BDQL7X7EEZQDZAY6VBAVCNFSM6AAAAABHF7K636VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJUHAZTANZRGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks! Spot checked some of the missing accounts here and they're up and running too. Tentatively closing.


Apply changes from Abstractions

What does this Pull Request accomplish?

Use the version of the FilterPinsAndPinGroups method from Abstractions.
Make use of the new isOfflineModeEnabled parameter from the TryDeterminePowerLineFrequency utility method, to avoid an unexpected error in offline mode.

Why should this Pull Request be merged?
TestStandSteps wants to integrate latest Abstractions capabilities.
What testing has been done?
Rely on auto tests in Pre.

@Mattjet27 I'm bypassing you since it's a pretty simple change.


Remove ineffectual | never type unions

Apparently never is never needed in a type union. You can pass in never as any generic parameter without there being a type error. I had not understood that never worked this way.

TIL!


Add startBlockSyncer

Relates to #52.
Overview
This combines BlockSyncer.tickingFunction and ChainProducer.getNextBlocks into a process that retrieves blocks from cardano-http-bridge.
Comments
It's pretty clear after looking at this feature "as a whole" that we must rework the code to address a few issues:

[x] nextBlocks should return more than the requested number of blocks if that makes sense (for example, returning the entire contents of an epoch pack file, or returning all the blocks from unstable epochs).
[x] Error handling should be fixed. One possibility is to remove ExceptT ErrGetNextBlocks and use throwIO to throw the Servant.Client.Core.ClientError (or whatever exception), and let the exception bubble up. (Because there's no way to recover from these errors). ⇒ fixed in #63
[x] Where should the state be kept? The state being the slot where the block syncer is up to (can be less than the network tip). ⇒ Modified tickingFunction

The following can go in a later PR:

How to initially catch up to the network tip, while still consuming blocks in small batches.
The BlockHeadersConsumed is unnecessary because nextBlocks never returns blocks before the start slot given to it.

rebased on top of latest master.


SAK-41701 - Performance problem in Tests & Quizzes tool

Tests & Quizzes tool returns all submission list in the course when asked to open with student profile. If there is no problem with this few students, there is a problem with a certain number of students (such as 200 and greater) with serious performance problems and some students cannot take the exam.

Could you explain a bit more? Are you saying that when a student tries to take a test, the JSF code iterates over a load of data that it doesn't need to?

Of course, i can summarize that, the processAction method under the AuthorActionListener class was called when the student was trying to open the assetsment tool. This led to the return of all submission lists for each student(is there a need for each submission list on the tool for a student?). I think this situation should be related to compilation priority of JSP tags. I have observed serious performance problems related to this situation. I observed serious performance problems in the assesment tool where the number of students and submission are high.

Thanks @kolkhetian , the PR has been reviewed by the core team and decided to merge it, thanks again for this wonderful contribution.


1.94 breaks screenshot scanning on high-dpi devices

Niantic changed the font dpi slightly and on some devices it makes ocrad fail really bad when doing the actual OCR. My N6 for example is fine but I've gotten new screen shares from a few other people that it's broken in.

@Fragger can you expand on the cause if necessary?

So far it appears ocrad just has issues with the font being slightly thinner.  I still have some more things I want to play with/test ways of fixing it.  I'll comment back when I have.


chore: Adjust Harvard upper busway config with new child stops/routes.

Summary of changes
Asana Ticket: Fix up Harvard busway berth assignments
Updated Harvard upper busway config to account for new berth assignments.
Reviewer Checklist

[x] Meets ticket's acceptance criteria
[ ] Any new or changed functions have typespecs
[ ] Tests were added for any new functionality (don't just rely on Codecov)
[x] signs.json changes were also made in signs_ui
[ ] This branch was deployed to the staging environment and is currently running with no unexpected increase in warnings, and no errors or crashes (compare on Splunk: staging vs. prod)

The gist of this change looks correct, but the overall shape of this config looks incorrect, coming out of #809 . That PR added several new config entries, but they should probably have been added as additional source entries instead. Each config generates a separate row on the sign, so we typically want to collapse things by route, so each route gets one line.
We should fix this up so there are 9 configs, and they can have multiple sources if we need to e.g. support multiple stop ids for a route.

Ahh I see. That makes sense.


Move tests to json files, progress on #25

Remaining to do:

[x] create a json schema for the test file (with just array object or string for the type)
[ ] create some more tests ?

Would be interesting to somehow export the test functions to make it easy to add tests for protodef users (to add tests for https://github.com/PrismarineJS/node-minecraft-protocol/blob/master/src/datatypes/minecraft.js )

test writing tracked in #56
test function exporting tracked in #55


[Sortable] Incorrect layout animation on drop when using the rectSwappingStrategy

Hi there 👋
First of all, wanted to say a huge thanks for this library. It's incredibly easy to use, works super well and is super polished. You should be very proud of it.
Anyway, the issue I'm facing is that with a sortable grid, when I drag an item to any position, except for its direct neighbour to the left or right (interestingly, even if the neighbour is on a different row), there will be a double animation fired of the drop (swap) target moving from it's original position to it's new position. I would not expect this, instead I would expect that since it is already there it would not have to move again.
You can see this happening here:
https://user-images.githubusercontent.com/1286001/122676117-d7b95a80-d21f-11eb-8f79-279783a8d9ae.mov
And this is a sandbox to play with this behaviour:
https://codesandbox.io/s/zealous-bell-lfng3?file=/src/App.js
I think this may be something that I have done wrong rather than a bug in the library, but I've been tearing my hair out and I can't seem to track down what is wrong here. I would really appreciate some help solving this.

Ok, after some more fiddling with this, I figured out that I can use animateLayoutChanges: () => false in useSortable.
I still find this confusing, because in the storybook examples, the <SortableItem> components have animateLayoutChanges: undefined, which I believe should set them back to the default animation. Despite this, they seem to handle drop animations fine.
Going to leave this issue open until I can get some clarity from the dev.

Hey @valtism, thanks for the kind words.
The main difference between your example and the storybook examples is that you are using rectSwappingStrategy. I'll have to spend more time investigating into why the layout animation is yielding this behaviour when used in coordination with rectSwappingStrategy.
For now as you have discovered, you can get around the issue by disabling layout changes in useSortable

This doesn't just happen with rectSwappingStrategy, you can change it to rectSortingStrategy in the codeSandbox and see that you still get this layout animation happening.

@valtism that's because of the way you're moving items on sort end. Your custom sort function assumes that the items need to swap position instead of being sorted. If you replace it with arrayMove that is exported from @dnd-kit/sortable you won't see that behavior.


Question

is this program runs on any device or it's only run on hawei devices?

Client development and access requirements：
1. Only Huawei phones are supported
2. HMS Core (APK) <IP_ADDRESS>0 or later has been installed
3. The phone you use is running EMUI 8.1 or later

then which device that can be scanned?

i have honor band 5 is it scannable because i dont get scancallback from the app

So far we only support devices that they use bluetooth protocols according to https://www.bluetooth.com/specifications/gatt/services/ . There are some APPs designed for scanning BLE device's protocols in apps market you may look for it.


Update SA1203SA1214SA1215CodeFixProvider to ElementOrderCodeFixProvider

Initial implementation. The results of the SA1203 tests altered slightly when access level checking was enabled.
Fixes #573
Fixes #1103
Code fix for SA1204

Rebased and added a fix all provider.
Roslyn.sln tests:
4475 SA1202 violations fixed in 3637ms.
907 SA1204 violations fixed in 2142ms.

@vweijsters Thanks for all the feedback.
Empty lines between members are now preserved, and file headers are now properly handled.
HasLeadingBlankLines and GetLeadingTriviaWithoutLeadingBlankLines are duplicates of the methods in SA1212SA1213CodeFixProvider. I think they should be moved to an extension method an unified in a separate pull request.
StripFileHeader and GetFileHeader are duplicates of the methods in UsingsCodeFixProvider.UsingsHelper. I think they should be unified in a separate pull request.
During testing I encountered and fixed a bug in SA1214 which does change its behavior slightly.

:+1: Looks good to me


Data source anomaly: IECEE TRF 60065-CC:1998

This applies to IEC 60065 ed 6. Not sure why the version is “CC”.
Given that IECEE TRF 60065D:2002 is "applies to IEC 60065, 7th ed”, perhaps the normalised identifier is "IECEE TRF 60065C:1998".

Requested clarification from IEC.

From IEC:
Secretariat reply: apparently there was a problem when our TRF data migrated from one database to another in 2016, the reference has been fixed and the TRF will shortly appear with the correct reference in the IEC webstore.
We don't need to handle "-CC". @mico please close when you see this.

This has been fixed by IECEE:
https://webstore.iec.ch/publication/7583

It is now "IECEE TRF 60065C:1998"


ARM64 Dockerfile cannot use the client and server debian packages

The following lines are meant to download debian packages on amd64 arch, but unfortunately those files are not available for aarch64.
https://github.com/cybergarage/puzzledb-go/blob/3366bc205979dc0736b29f5ed4e3482b2b0a1659/Dockerfile#L12
https://github.com/cybergarage/puzzledb-go/blob/3366bc205979dc0736b29f5ed4e3482b2b0a1659/Dockerfile#L16
How can I run puzzledb-go in a Raspberry Pi 4?
Can you make a cross-platform Dockerfile please?

@al-sabr Thank you for your report.
I'll create a new Dockerfile for Raspberry Pi to switch the default storage from FoundationDB to go-memdb.

@al-sabr
I am about to set up a RasberryPI, what operating system are you planning to use?

@al-sabr
If you want it to work on RasberryPI, delete all the following FoundationDB-based plugins directories

puzzledb/plugins

coordinator/fdb
store/kv/fdb

It would be easy to modify Server::reloadEmbeddedPlugins() to not load that deleted plugins. The standard config file has the FoundationDB plugins disabled, so this procedure should work.


update pathology_nuclei_segmentation_classification README

Fixes # .
Description
Update REAMDE in pathology_nuclei_segmentation_classification to clarify how to download the dataset.
Status
Ready
Please ensure all the checkboxes:

[x] Codeformat tests passed locally by running ./runtests.sh --codeformat.
[x] In-line docstrings updated.
[x] Update version and changelog in metadata.json if changing an existing bundle.
[ ] Please ensure the naming rules in config files meet our requirements (please refer to: CONTRIBUTING.md).
[ ] Ensure versions of packages such as monai, pytorch and numpy are correct in metadata.json.
[ ] Descriptions should be consistent with the content, such as eval_metrics of the provided weights and TorchScript modules.
[ ] Files larger than 25MB are excluded and replaced by providing download links in large_file.yml.
[ ] Avoid using path that contains personal information within config files (such as use /home/your_name/ for "bundle_root").

/build


f5-config.py creates priority groups for repo servers

The current configuration for f5-configy.py scripts creates a pool for the repo servers with a priority group of 100, 95, 90 with a balancing scheme of fastest-node. This forces all the traffic to go through a single node that we discovered. They should be set to all the same priority with least connection node for balancing.
current output
create ltm pool /QE-IAD3-1/QE-1_POOL_REPO { load-balancing-mode fastest-node members replace-all-with { QE-1_NODE_569038-infra03_repo_container-45441f9f:8181 { priority-group 100 } QE-1_NODE_569037-infra02_repo_container-20bae48b:8181 { priority-group 95 } QE-1_NODE_568575-infra01_repo_container-9c514b02:8181 { priority-group 90 } } min-active-members 1 monitor /QE-IAD3-1/QE-1_MON_HTTP_REPO }
something like
create ltm pool /QE-IAD3-1/QE-1_POOL_REPO { load-balancing-mode least-connections-node members replace-all-with { QE-1_NODE_569038-infra03_repo_container-45441f9f:8181 { priority-group 100 } QE-1_NODE_569037-infra02_repo_container-20bae48b:8181 { priority-group 100 } QE-1_NODE_568575-infra01_repo_container-9c514b02:8181 { priority-group 100 } } min-active-members 1 monitor /QE-IAD3-1/QE-1_MON_HTTP_REPO }

This section is completed during the issue resolution process. If you are reporting an issue, please do not modify the section below.
Which branches are impacted by this issue?
Remove branches that are not impacted.
For each pull request, update the branch line to reference it.

[x] master (https://github.com/rcbops/rpc-openstack/pull/1290)
[ ] mitaka-13.0 (#1322)
[ ] liberty-12.2 (https://github.com/rcbops/rpc-openstack/pull/1337)
[ ] kilo (https://github.com/rcbops/rpc-openstack/pull/1336)

Upgrade impact. Consider the impact on moving between major, minor and patch releases.

[x] This change does not impact upgrades
[ ] This change addresses a potential upgrade impact
[ ] The upgrade impact is being tracked by another issue.

The issue tracking the upgrade impact is:
Testing impact

[ ] An issue/pull-request has been create or exists to track the testing gap, and is referenced below
[x] This change includes additional testing
[ ] This change is tested by the existing setup

Additional testing links:
Release note

[ ] This change includes a release note.
[x] This change does not require a release note.

Doc Impact
Does your change require documentation?

[x] Yes, and I submitted an issue to Docs issues
[ ] Yes, and I contributed a documentation patch to docs-rpc
[ ] No documentation required for this change

Additional documentation links (please add links if you have ticked yes):

Still a valid concern

@nategraf does this need to be considered for backports? Also, please can you update the description with info about doc impact and release notes etc, and links to the backport PRs once they are made.

Was this tested in a hardware lab? The pull request checks do not test this script. The description above states that additional testing has been included with the change - what is this additional testing?

@mancdaz I couldn't find a place in the docs where the exact load balancing method for repo servers is mentioned. (I could have just missed it) A docs change is not needed for this patch in particular, unless it is decided that all load balancing default configurations should be documented.
@git-harry This has not been tested in the hardware lab. I consulted with Johnny and Edgar on the networking team and both found that the change to be small and said the configuration it produced looked good. The change I made in the PR follows established code paths by simply changing a hard coded setting so there is not a possibility of breaking the code itself. There could be an issue if, for some reason, the repo servers behave poorly in an active-active configuration. To my knowledge this is not an issue because until the repo servers are synced, they are removed from the load balancer, and once they are synced they will serve equivalent packages. Hardware lab testing may be needed, but this I will need to defer to y'all for that, as I no longer have access to any hardware lab resources.

@git-harry @mancdaz Please confirm that the backports for Liberty and Kilo are needed.

Yes, this should be backported to kilo and liberty since the errant behaviour will exist there too.
EDIT: Backports have been submitted and links added to the description

@b3rnard0 looks @mancdaz already has done with backport, though I'm in progress. Avoiding duplicated work, I won't commit from my side.


Remove old ingress (again)

What does this pull request do?
Remove old ingress (again)
History:

Removed in a01c4506f7b2c41f44b491883d26b091c7fde9d8
Realised the new ingress was not v1, rolled back in d8707683cf607a3c87a9fc2b9b1ab8d0f1845e1e
Migrated to v1 in 90e1bc5818ca793cf963b9b7569daf9540e58c9d and d27ea638288860617c9fd5930d234d3015d92c54
Finally removing it now for good

What is the intent behind these changes?
Remove the old versions of Ingresses that prevent the hosting environment from being upgraded.

Old ingresses will be unsupported from today.
This makes this urgent, so bypassing reviews, sorry 🙇♂


RGB (Color) Additions from Nick's code

Small changes here & there, but logic is mostly the same.

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


EqualStreetNames accross the World

City
Link
Maintainer

Belgrade
- (wait for green light)
@stalker314314

Brussels
https://equalstreetnames.brussels/
@jbelien

Should we bundle all the versions in one single repository ?

You can see my changes here: https://github.com/stalker314314/equalstreetnames split into 3 different buckets (pipeline, web and data changes). They are not big, but also not easily abstracted away. I can understand how pipeline changes can be abstracted - have come config file that can define your overpass query and languages of interest.
For web, since I am not good with web, I have no idea how to pull that (but we need to abstract away languages, site needs to be localized, map need to have different bounding box) - some pre/post processing of html?
Data should not reside in git (or it could, but updating might be mess, maybe keep it out of git, or use it as submodule). Not sure if you would adopt approach where all data is updated at once, with same script, or each individual owner is owning data for their city and it is external to this repo? I prefer latter.

Data should not reside in git (or it could, but updating might be mess, maybe keep it out of git, or use it as submodule).

I never played with Git submodules but I think having a submodule by "region" (city, ...) could indeed be a good solution for this !
I'll try to move everything related to Brussels (in our case) to a submodule and see how it goes !
Stay tuned 🎉

@stalker314314 I restructured the repository to isolate all the data/information related to Brussels in the cities/brussels folder.
The scripts and structure should now be independent from any city !
I still have to remove the this line to make the scripts completely independent of the city. I'll do that as soon as I have finished to update all the wikidata profiles.
The cities/brussels could become a sub-module !
Let me know if you think the new structure is good enough to include Belgrade as a sub-module too (I'll work on the loader - see #25 - this afternoon or tomorrow) !

Awesome. I will try it by merging Belgrade! But, what are next steps for me - should I create PR to add Belgrade here, or keep it in fork, or wait for submodules?

should I create PR to add Belgrade here, or keep it in fork, or wait for submodules?

Let's try to go for sub-modules. I'll move brussels to a sub-module !
 Brussels is now a sub-module ! 🍾

@stalker314314 Looking at your scripts, I just realized I still need to make the languages configurable in scripts/geojson.php. I'll take care of it tomorrow !

Hi,
There are still some artifacts:) They don't block me, just wanted to let you know:
https://github.com/openknowledgebe/equalstreetnames/blob/master/scripts/geojson.php#L104
https://github.com/openknowledgebe/equalstreetnames/blob/master/scripts/geojson.php#L151
and getGender could be improved: https://github.com/openknowledgebe/equalstreetnames/blob/master/scripts/geojson.php#L388

These one too:
https://github.com/openknowledgebe/equalstreetnames/blob/master/resources/map.ts#L17
https://github.com/openknowledgebe/equalstreetnames/blob/master/resources/map.ts#L34
(sorry if I am annoying you, I am just dumping all missing places as I go, and since I am first one, I guess this is expected. Hopefully, next city will not need to do all of this:D)

Awesome ! Nice catch !
I'll fix that later today !
 Thanks for your help !

I updated the scripts !
And moved the map settings in .env (see step 5 of "Run locally")


Restrict branch build to master

What was the feature/problem?
Double builds on PRs from branches in the main project.
How does this PR address the above feature/problem?
Restrict travis to master for push builds.
Check lists (check x in [ ] of list items)

[ ] Test passed
[ ] Coding style (indentation, etc)

Additional Comments (if any)

Codecov Report

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

@@          Coverage Diff           @@
##           master    #132   +/-   ##
======================================
  Coverage    95.7%   95.7%
======================================
  Files          28      28
  Lines         419     419
  Branches       45      45
======================================
  Hits          401     401
  Misses         15      15
  Partials        3       3

Flag
Coverage Δ

#api
97.12% <ø> (ø)
:arrow_up:

#ui
94.69% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Support RSS/Atom/JSON Feeds

Is your feature request related to a problem? Please describe.
As far as I can tell, there isn't a way to follow people on bluesky from any news aggregators.
Describe the solution you'd like
Implement a RSS/Atom/JSON feed for use user's public posts. Maybe supports credentials for RSS/Atom/JSON feeds so people can also follow users private posts, if their account is allowed to see them. Though, I think public posts is plenty.
Additional context
If Bluesky is aiming for decentralization and user freedom, supporting open standards like RSS/Atom/JSON is needed. Especially now, with people leaving centralized platforms. Currently, I can follow people on Mastodon, Cohost, Twitter (using Nitter), and Tumblr easily from my news aggregator, but people that go over to Bluesky are essentially disappearing off the internet for me, at least until Bluesky supports news feeds.

Yeah I was looking for these as well. Maybe Open RSS can provide them if Bluesky somehow can't. Looks like Bluesky has an API to do it.

The basic feature has shipped. If there are more specific requests for additional features, like different formats (Atom), please open new issues.


feat: Init pytorch backend of onnx model serving

https://github.com/tobegit3hub/simple_tensorflow_serving/issues/36

Great. Thanks for your contribution @wrongtest 👍


Make naming style of Inbox contract consistent with the rest  of the project.

See https://github.com/EspressoSystems/op-leader-election/pull/72#discussion_r1324205053

Closed in #100.


AD FS OBO: secure WebAPIOBOController with Authorize attribute

Description:
As discussed in issue ticket #3061 (Shouldn't WebAPIOBOController be secured with an Authorize attribute?),
the WebAPIOBOController controller should be secured with an Authorize attribute to validate the OAuth token when the ToDoListService calls the WebAPIOBO API, otherwise the AD FS configuration for WebAPIOBOController will never really be tested when running this locally.
Thanks to Toby Artisan (@tobyartisan) for making us aware of this issue.
Changes proposed:

add the [Authorize] attribute within the AD FS OBO Controller code
add user: {User.Identity.Name} to the output string
add MarkDown syntax highlighting to the code snippet
improve the grammar/readability of preceding instructions
change the MD code block fence characters to back ticks

issue ticket closure or reference:
Closes #3061

Checking with engineering.


[6.4.x] DROOLS-987 - Errors in Phreak under heavy and multi threaded load - f…

…ixed tests as rule node fires rules directly
(cherry picked from commit 4ec6f14438709211b0cc347a91cecf24c5b1a460)

merging as requested for one off patch


Docker the right way

This PR is on top of CD setup in #103.
What does this PR do?

It changes the way to build docker image. By always using the result of msbuild /t:Publish in the docker image. And we are not using docker BUILD container, but using the same artifacts that were tested in previous stage.
added a flag to skip running db migrations. By default it is ran. As mentioned in discussion in #101
added e2e tests, mostly ported from LiGet

Dockerfile is changed a bit:

uses tini for init system to reap any processes.
does not run as root by default. There is a baget user.
because of above changes default listening port to 9090.
when container starts it changes uid and gid of baget user based on owner of volume mount.
environment variables are all specified in Dockefile for clarity. Now a basic server to try out can be run with docker run baget.

Motivation
The e2e tests ensure that some of the most basic commands, such as nuget push or paket install pass.
This step would be great to execute before publishing final docker image.
Most of this is LiGet's CD ported to BaGet.
The files in .build are part of our internal bash script helpers used for common stuff. This is added for reference, nothing fancy there.

Opened #108 instead


the string of 'True' and 'False' after safeDump has  quotation marks

the object is
{
a : 'a',
b: 'True',
c: 'False'
}
after safeDump , the yaml file is like this:

What is special of 'True' and 'False'？

http://nodeca.github.io/js-yaml/#yaml=cXVvdGVkOiAiVHJ1ZSIKbm9xdW90ZTogVHJ1ZQ==

I mean why ‘a’ has convert to a（no quotation marks），but ‘True’ convert to ‘True’（has quotation marks）

Because quotes are skipped when possible. And not skipped when impossible.


Insert a README.md

Hello World!

[ ] Add a readme file to project

[ ] Add description about project
[ ] Badges?
[ ] How to contribute
[ ] Code of Conduct
[ ] Add a how to build the project (pre-requisites)

Thanks, Bruno! I totally forgot that...

We are not going to have a badge right now.


added support for allow_disk_use

Added support for missing allow_disk_use param: https://pymongo.readthedocs.io/en/stable/api/pymongo/collection.html#pymongo.collection.Collection.aggregate

@pcorpet
Hi, I can see there is an issue with:
W: GPG error: https://packages.erlang-solutions.com/ubuntu focal Release: The following signatures were invalid: BADSIG D208507CA14F4FCA Erlang Solutions Ltd<EMAIL_ADDRESS>in Travis Cl

Hi @pcorpet, have you had time to look at this PR?

@pcorpet Hi, I can see there is an issue with: W: GPG error: https://packages.erlang-solutions.com/ubuntu focal Release: The following signatures were invalid: BADSIG D208507CA14F4FCA Erlang Solutions Ltd<EMAIL_ADDRESS>in Travis Cl

Can you try rebasing on HEAD of develop please?

Please add a usage in any of existing test or copy an existing one to set it with True or False and check that there are no errors (for regression).

Add a usage of the keyword argument as well in a test.

Thanks for your changes!

@pcorpet thank you! When do you plan to release a new version?


Possible to disallow initial value?

Is it possible to disallow the use of certain values?
My specific use case is the use of the initial value inside e.g. the color property.
I want to disable this because this value is not supported by IE, but seems like an excellent fix for some issues (until you test in IE).
color: initial // Does not work on IE
What version of Sass Lint are you using? 1.10.2

There's a PR open in #1142 which will add a rule to do this.

Though notably #1142 only disallows values for a specific property - a blanket blacklist for all instances of the use of the initial value across all property names isn't possible. But it could be extended to allow e.g.
no-disallowed-property-values:
  properties:
    '*': initial


Kotlin version is missing in build.gradle

After pasting the version fields from https://developer.android.com/codelabs/android-room-with-a-view-kotlin?hl=en#3, the Gradle builds says
Build file '...\RoomWordSample\app\build.gradle' line: 57

A problem occurred evaluating project ':app'.
> Could not get unknown property 'kotlin_version' for object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

I solved this error by adding
kotlin_version = '1.4.21'

in the ext-section.

Thanks for the tip!

Fixed, thanks for reporting!

Thanks!!


Add shouldForwardProp to theme

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
I'm using a custom property to create custom variants for OutlinedInput.
The problem is that I need to pass the property to the component for the theme to have it, but the property ends up being rendered to the DOM.
Examples 🌈
Component usage:
<OutlinedInput state="error />

Theme:
{
  "MuiOutlinedInput":{
    "variants":[
      {
        "props":{
          "state":"error"
        },
        "style":{
          "my_custom_styles":"go here"
        }
      }
    ]
  }
}

Motivation 🔦
The motivation is the same as the function shouldForwardProp that exists in styled.
Avoid rendering unnecessary properties to DOM.

This would be a great feature to have and I am currently having the same issue. Is there anyone working on this and if not could you maybe point me to the respective place in the codebase where this could be added? I could add that feature myself in that case.
cc @siriwatknp
Thanks in advance!

Any updates?

Please don't let this one die :)

@mnajdova A new use case for the variants API. This case needs to style based on the ownerState, not just props.

We'd like to have this too

Hi @mnajdova
Is there any update on this, its really very helpful feature.

The issue itself looks like a duplicate of https://github.com/mui/material-ui/issues/19466, it's about supporting additional props in the components. The decision is about whether creating a wrapper component as an API is easier/more intuitive in comparison with a new API about specifying which props should be propagated. I am tagging @aarongarciah so we can include this in the planning for the next theming customization/experience. If we decide to add this support in one of the next majors, we can likely backport it in v6 too.

Duplicate of #19466

@mnajdova IMO, we can create a wrapper component and it's good when we have some additional features to add.
But for simple changes like just giving support of maxWidth in the TableCell component we will create a wrapper where we're simply returning the same component and nothing new is being done. I think adding this new functionality might be great.

We have the same problem, for example, that we introduce the prop dense for the IconButton via theming and module augmentation for a button variant with less padding, which technically works great, but the boolean prop is forwarded to the DOM, resulting in the following error message in Chrome:
Warning: Received `true` for a non-boolean attribute `dense`.

If you want to write it to the DOM, pass a string instead: dense="true" or dense={value.toString()}.

As far as I understand, there should be a way to override which props are forwarded in the theme for a component, like shouldForwardProps in styled. Since we maintain a whole design system's component library based on MUI, a wrapper component is not a good alternative here, as it would have to have the same feature set as an original MUI component when consumed, because this is what our users expect. A custom component therefore always means a certain overhead of code and an alternative import source of a component actually provided by MUI, which could be avoided with such a functionality.


the network (0) is not support

🐛 Bug Report
the network (0) is not support

Steps to Reproduce

Expected Behavior

Your Environment

Closing this issue due to lack of meaningful context.


sync writing systems from FLEx to LF on every sync

Note: writing system == input system
Recently, LF was changed to no longer allow writing systems modifications in the LF UI.  This was intentional due to confusion and a fundamental writing systems mismatch between LF and FLEx (LF's model is too simple).  This decision was made in anticipation of this current issue, namely that FLEx is the authority on writing system definitions and LF should be updated with FLEx's writing systems on every sync.
Practically speaking, I think we should delete LF writing systems and recreate them from FLEx on every sync.  This seems like the simplest way to do a "one way sync" from FLEx -> LF.  There shouldn't be a performance issue here - most projects only have a handful of writing systems, surely less than a dozen.

At a recent standup meeting for Language Depot, we mentioned that the Analysis and Vernacular booleans aren't always getting set correctly on some projects, even during initial clone. So I also need to investigate why that is happening, though if we change the writing systems to always update from FLEx (not just during initial clone) then that may become a moot point.

BTW. it was commit 3cd4cecfe6b417f40404edcfc579f2edd3a26ed5 (way back in 2016) that switched to only updating the writing systems on initial clone. That might be helpful as I investigate.

Actually, I just ran some tests that confirm that the input systems are getting set in LF on every Send/Receive. What's happening only on initial commit (in the current state of the code) is that the default input systems for each field are set, based on which fields are expected to take vernacular input systems (citation form, lexeme, etymology, and example sentences) and which ones are expected to take analysis input systems (everything else). And I don't think we should change that, because people are allowed to adjust the list of input systems for each field. (Probably by removing some of the vernacular input systems, e.g. if you have tha-TH, tha-Latn, and tha-x-aud input systems, you probably don't want tha-x-aud on any fields except Pronunciation, so you probably removed it from lexeme and citation form. If we overwrote those choices on every S/R, it would be bad UX).
So AFAICT right now, this issue might already be resolved and there's nothing further to do on it. I'll discuss with Chris when I get a chance.

AFAICT right now, this issue might already be resolved and there's nothing further to do on it. I'll discuss with Chris when I get a chance.

This is great news!  Thank you for the update, Robin.

sounds like this is resolved.


Swift 3 issue

I'm using Swift 3, and the sample code.
When compiling, I get this error:

Command failed due to signal: Segmentation fault: 11

While emitting SIL for getter for window at /AppDelegate.swift:14:14

By removing the lazy keyword, this error disappears, but I got a new error at:
customWindow.touchVisualizerWindowDelegate = self
Any idea to solve this issue ?
Thx,
Arnaud

I've update the example, but I should really have a better way for configuring the touch window.

Awesome, thanks a lot ! 👍

Oh and here is the new version I'm working on too:
https://github.com/design-utilities/sensor-visualizer


Docs show globals with . instead of -

You show the syntax as:
bcl-globals.get
But it should be:
bcl-globals-get

Thanks for catching this.  I've updated the docs.


Adding MSI Installation for Preview Handler

Summary of the Pull Request
Adding MSI installation support for Preview Handlers. Added all the registry changes required under HKEY_CURRENT_USER.  Used two separate Component for Preview Handler one for copying the dll and one for updating Registry under Current_User. Unable to do that in a single component because of ICE57 error.

PR Checklist

[x] Applies to #963

Validation Steps Performed

Installed and validated Preview Handlers with MSI.

should we also update the README.md or there is another task for it?

should we also update the README.md or there is another task for it?

which readme?

should we also update the README.md or there is another task for it?

which readme?

The README for preview pane.
https://github.com/microsoft/PowerToys/pull/1436#issuecomment-594890621


Use SerialIterator in train_mnist_custom_loop.py

Other MNIST examples use SerialIterator.

Jenkins CI test (for commit f056e7d041ebda638b94970ed1997e8c536651fc, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit 5b607bd6536af9754cd9a3446459101380fc1333, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit 5b607bd6536af9754cd9a3446459101380fc1333, target branch master) succeeded!

LGTM!


Reset dcsr.PELP to NO_LP_EXPECTED upon resuming from debug mode?

Regarding Zicfilp, the "Preserving Expected Landing Pad State on Traps" section:

An MRET or SRET instruction is used to return from a trap in M-mode or S-mode, respectively. When executing an xRET instruction, if xPP holds the value y, then ELP is set to the value of xPELP if yLPE is 1; otherwise, it is set to NO_LP_EXPECTED; xPELP is set to NO_LP_EXPECTED.
Upon entry into Debug Mode, the pelp bit in dcsr is updated with the ELP at the privilege level the hart was previously in, and the ELP is set to NO_LP_EXPECTED. When a hart resumes from Debug Mode, if dcsr.prv holds the value y, then ELP is set to the value of pelp if yLPE is 1; otherwise, it is set to NO_LP_EXPECTED.

As one can see, xPELP is reset to NO_LP_EXPECTED upon <M/S>RET, but this behavior is not mandated on dcsr.PELP when resuming from debug mode. Is this discrepancy intended?
Thanks,
Ming-Yi Lai

Yes, that was intentional and follows similar difference between dret and mret/sret for dcsr.prv and mstatus.mpp/spp. Unlike M/S mode there is no scheduler in debug mode or a privilege level higher than Debug mode.

Ok, thanks for the reply :)


[Feature request] Add arm64 support

Idea
I really like the project, but sadly the image is not arm64, anything I can do to make it work? I don't mind compiling the image myself.

I was able to build the image locally just removing the buildx part, I will keep this open because not everyone might be able to build it locally so I still think an arm64 version of this image should exist

Duplicate of https://github.com/jlesage/docker-handbrake/issues/48
The problem is that cross-compiling HandBrake is not easy. HandBrake's build system is not fully adapted for that.

Duplicate of https://github.com/jlesage/docker-handbrake/issues/48
The problem is that cross-compiling HandBrake is not easy. HandBrake's build system is not fully adapted for that.

You can run the build process that you have right now in an arm64 runner, it should work.

I think it would work to make a separate arm64-only image. But I'm not sure how it would work to create a multi-arch image like you can do with buildx.

I think it would work to make a separate arm64-only image. But I'm not sure how it would work to create a multi-arch image like you can do with buildx.

A separate image is better than none but a multi-arch can be better. If you want to go with the second option why don't you enjoy the beauty of open source and check other projects's github actions and see how they do it?

Unfortunately, I didn't find a version of HandBrake being cross-compiled for Linux ARM64.


Improve TesseractCoding  website Visibility

To improve the visibility of the website you should:

Add a link to the website in the repository description
Add a link to the website in the main README.md file

Hello there @omonimus1, I'll work on adding the website's URL onto the main README.md file, and let the maintainer add the website's URL onto the description box.

Hello there @omonimus1, I'll work on adding the website's URL onto the main README.md file, and let the maintainer add the website's URL onto the description box.


Update gradle to 8.10.2

fyi --- Gradle 8.11 is available

Gradle 8.11.1 is available https://gradle.org/releases/


feat(prisma2/cli): allow arbitrary generator commands with flags

only show the JS example when generator is prisma-client-js
fix #1101

It is 🚀 in<EMAIL_ADDRESS>


Add license [skip ci]

This PR adds a license file to the repo root, which I think is required for the github sbt task not to get really mad. It's the same license file from the docs folder, just in the root.

LGTM, probably you're already aware, but creating the first release (0.0.1 or whatever) will invoke the ci-docs task, as part of this action.
However, you'll need a documentation sbt module:
lazy val documentation = project
  .enablePlugins(MdocPlugin)
  .settings(mdocOut := file("."))
  .settings(publish / skip := true)

It requires the mdoc plugin.

I'll add that next


Delete prop onInitialLayoutView

Could you run the tests by doing yarn test? Usually these changes break them, resulting in a CI/CD failure.

I don't understand the question, I thought it was like that, and after doing it manually.


measurements.sequence

Since measurements.sequence is now a required field for measurements, the conversion scripts should presumably fill it in.
Our conversion scripts already generate measurements.txt with the records in the correct order.  So, in a measurements table with n rows, can the measurements simply be added to each record starting with 0 and ending with n-1?  (or starting with 1 and ending with n) .
Does anyone see a problem with implementing this into all MagIC 3 conversion scripts?

no - i guess we need this one.  lisa

On Dec 6, 2017, at 1:52 PM, Lori J<EMAIL_ADDRESS>wrote:
Since measurements.sequence is now a required field for measurements, the conversion scripts should presumably fill it in.
Our conversion scripts already generate measurements.txt with the records in the correct order. So, in a measurements table with n rows, can the measurements simply be added to each record starting with 0 and ending with n-1? (or starting with 1 and ending with n) .
Does anyone see a problem with implementing this into all MagIC 3 conversion scripts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/PmagPy/PmagPy/issues/273, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKrDYIr348YZiqbFM3i3Npg6TrzmmBhks5s9wyfgaJpZM4Q4pYc.

When we have online validation, the plan is that, if the sequence is missing, we will add the sequence by using the order in the upload file. The sequence is a signed float so you can start with 1 or 0. Putting them into the scripts is probably a good idea as validation is not happening right now and having the sequence created closer to the original data files reduces the likely hood for mistakes.

Great, this is easy to implement anyway.


Remove redundant eslint max-len overrides

Summary
The max-len eslint rule was disabled in #3444. No reason to keep around the inline disables of it.

Test plan
yarn lint

Thanks @SimenB. This is great.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #3548   +/-   ##
=======================================
  Coverage   62.28%   62.28%
=======================================
  Files         181      181
  Lines        6714     6714
  Branches        6        6
=======================================
  Hits         4182     4182
  Misses       2529     2529
  Partials        3        3

Impacted Files
Coverage Δ

packages/jest-config/src/utils.js
81.63% <ø> (ø)
:arrow_up:

packages/jest-validate/src/warnings.js
100% <ø> (ø)
:arrow_up:

packages/jest-matchers/src/toThrowMatchers.js
79.62% <ø> (ø)
:arrow_up:

packages/jest-haste-map/src/lib/extractRequires.js
100% <ø> (ø)
:arrow_up:

packages/jest-docblock/src/index.js
100% <ø> (ø)
:arrow_up:

packages/pretty-format/src/index.js
98.06% <ø> (ø)
:arrow_up:

packages/jest-cli/src/lib/getTestPathPattern.js
60% <ø> (ø)
:arrow_up:

packages/jest-message-util/src/index.js
87.05% <ø> (ø)
:arrow_up:

packages/jest-matchers/src/matchers.js
98.35% <ø> (ø)
:arrow_up:

packages/jest-config/src/normalize.js
90.9% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Fix various typos

Corrects various typos that I've found in the repository.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (f8aa129) 90.59% compared to head (911f461) 90.59%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #485   +/-   ##
=======================================
  Coverage   90.59%   90.59%
=======================================
  Files          10       10
  Lines        2946     2946
=======================================
  Hits         2669     2669
  Misses        277      277

Impacted Files
Coverage Δ

src/JET.jl
79.26% <ø> (ø)

src/abstractinterpret/abstractanalyzer.jl
86.59% <ø> (ø)

src/abstractinterpret/inferenceerrorreport.jl
90.38% <ø> (ø)

src/abstractinterpret/typeinfer.jl
93.99% <ø> (ø)

src/analyzers/jetanalyzer.jl
90.75% <100.00%> (ø)

src/toplevel/virtualprocess.jl
96.32% <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.


Make overlays and toasts clickthrough

Thanks a lot for making this fantastic package!
It would be great if there were a way to make the overlays and toasts optionally clickthrough.
I use this package to display an info notification, but it currently blocks other elements behind it from being clicked. This is suboptimal as it breaks the flow of the app. Would this be possible?

It would be great if there were a way to make the overlays and toasts optionally clickthrough.

Sorry, I can not get the picture in my mind for optionally clickthrough.  Can you give me more details of this?

it currently blocks other elements behind it from being clicked.

Because in my understanding, the front elements in the UI should intercept click events. This is also the default behavior of flutter.

Sorry for being unclear.
I mean that e.g. when launching an overlay, it would be great if you could provide an option, a simple boolean for example, to make the overlay blocking or non-blocking.
Although the default behavior in Flutter is to be blocking, I think it would be useful to get this option. E.g. native toasts in Android are clickthrough too (to my knowledge at least).

You can wrap your custom overlay with IgnorePointer widget, then your custom overlay wouldn't  interupt any touch event anymore.
The package provider toast has been warpped IgnorePointer   in 76b0cee16c1019f2491bbe415127f76f884b5d5c

Awesome! Exactly what I was looking for, thanks a lot for the help!


The Tree view layout shows incorrect when running/cancelling the action 'Search From Here'

Storage Explorer Version: 1.26.0-dev
Build Number: 20221006.3
Branch: feature branch
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Monterey 12.6 (Apple M1 Pro)
Architecture: ia32/x64
How Found: From running test cases
Regression From: Previous release (1.26.0)
Steps to Reproduce

Launch Storage Explorer (Make sure the scroll bar shows up for the tree view).
Right click one subscription node -> Click 'Search From Here'.
Check whether the tree view layout shows normal.

Expected Experience
The tree view layout shows normal.
Actual Experience
The tree view layout shows incorrect.

Additional Context

This issue doesn't reproduce when running 'Searching From Here' for the Quick Access/ Emulator & Attached nodes.
This issue can be resolved by resizing using 'Zoom In/Out'.
The log for this bug has been collected.

Verified this issue on the build 20221028.4. Fixed.


request params is not support

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
class Item(BaseModel):
    name: str
    age: int
    height: float

app = FastAPI()

@app.get("/hh")
async def update_item(item: Item):  # item需要与Item对象定义保持一致
    return {
        "method": 'get',
        "people_name": item.name,
        "people_age": item.age,
        "people_height": item.height
    }

Description
this  request  method    is     GET
if   i    request  this  function  by    postman  ,

so   that is  not  support
Operating System
Windows
Operating System Details
No response
FastAPI Version
0.63.0
Python Version
Python 3.10.0
Additional Context
emo

You have wrong code in your handler, pydantic model is used for body parameters from JSON in post request.
If you want to use query parameters your code should look like:
@app.get("/hh")
async def update_item(name: str, age: int, height: float):
    return {
        "method": 'get',
        "people_name": item.name,
        "people_age": item.age,
        "people_height": item.height
    }

More on query parameters in docs.
But judging by the name of the handler function, you should use the POST method and send the JSON inside.

# to resolve GET method

item: Item = Depends(Item)

# to resolve GET method

item: Item = Depends(Item)

thank you    your method  is right        you  is  my  angel baby

You have wrong code in your handler, pydantic model is used for body parameters from JSON in POST request. More on it in docs. And as you can see error message shows you that you have missing fields in body. If you want to use query parameters your code should look like:
@app.get("/hh")
async def update_item(name: str, age: int, height: float):
    return {
        "method": 'get',
        "people_name": item.name,
        "people_age": item.age,
        "people_height": item.height
    }

More on query parameters in docs. But judging by the name of the handler function, you should use the POST method and send the JSON inside.

i  know  what you say ,   see  the panla  comments,  you will know other way  to  deliver params   of  GET

@panla interesting method didn't know about it, thank you!
@yztdemo I must still admit that for clarity if you wan't to update something it is better to not use GET method, cause it's misleading.
As mentioned in docs it's better to use PUT or PATCH methods.

@insomnes   @yztdemo
issue 3525
issue 2997
name: Optional[str] = Query('', title='name')


Basic implementation for experimentation

I've created a patch for babel-plugin-bare-import-rewrite which has an option to enable experimentation with proposal-pkg-exports.  Although the original goal of that plugin is to support live transformation of bare imports through a web server like express-transform-bare-module-specifiers, it is also able to operate with @babel/register in node.js processes.  https://github.com/cfware/babel-plugin-bare-import-rewrite/blob/proposal-pkg-exports/fixtures/pkg-exports-bin.js demonstrates this.
I haven't released this feature to npm yet, is it interesting to anyone?  One potential issue it operates using the less strict --es-module-specifier-resolution=node mode.  Obviously this is only useful for testing pkg-exports without node.js native ESM since @babel/register does not work with native ESM.

That looks like really need, thanks for the ping!

I'm going to close this issue to make it a bit clearer what threads need conclusion before we can ship exports. We're getting close to finalizing the implementation!

Sounds reasonable, I'm going to leave my experimental branch in place for now but I suspect it's diverged from the current spec.  Will likely wait for resolve to have support for exports lookup before I take any further action.

@coreyfarrell as soon as i know what node version it will land in, i'll add it :-)


Write a GO program to print fibonacci series by recursion

Description
Write a GO program to print fibonacci series by recursion
Input  : 5
Output : 0 1 1 2 3

How to contribute

Save the solution in print_fibonacci_series_by_recursion.go file
Add print_fibonacci_series_by_recursion.go file in print-fibonacci-series-by-recursion folder

Hey @Chirag8023,
This issue has been assigned to you for more than 15 days.
We are unassigning you from this issue.
If you are still interested in contributing to this issue, please get auto-assigned on the issue by commenting !assign again.
Thanks for your contributions :)


[BUG] Composable index template mapping can prevent creating an index if mappings conflict

Describe the bug
In the index templates documentation for Composable index templates, it states:

Settings and mappings that you specify directly in the create index request override any settings or mappings specified in an index template and its component templates.

This documentation is not accurate.
Specifically, overriding is not possible if the conflicting type can't be merged (e.g., between object and nested, field and object, etc.).  Overriding only occurs on "leaf" components.  (See https://github.com/opensearch-project/OpenSearch/commit/ab65a57d700efa58e98544d7e49bd758961602dc)
Worse, this mapping conflict prevents index creation, including system indices.
A user could accidentally add a wrong mapping and potentially prevent a node from even starting up: https://github.com/opensearch-project/observability/issues/1872
Related component
Indexing
To Reproduce

Create a component template with an object or nested mapping for a field ("error" in this case):

PUT _component_template/error_mapping_template
{
  "template": {
    "mappings": {
      "properties": {
        "error" : {
          "type": "nested",
          "properties": {
            "message": {
              "type": "text"
            },
            "status": {
              "type": "integer"
            }
          }
        }
      }
    }
  }
}

Create an index template using that composable template mapping:

PUT _index_template/match_all_template
{
  "index_patterns": [
    "*"
  ],
  "template": {
    "settings": {}
  },
  "priority": 10,
  "composed_of": [
    "error_mapping_template"
  ],
  "version": 1
}

Attempt to create an index with a conflicting field mapping (including a system index):

PUT /.plugins-foo-system-index
{
  "mappings": {
    "properties": {
      "error": {
        "type": "text"
      }
    }
  }
}

Receive the below error, and observe that the index did not successfully create.

{
    "error": {
        "root_cause": [
            {
                "type": "illegal_argument_exception",
                "reason": "can't merge a non object mapping [error] with an object mapping"
            }
        ],
        "type": "illegal_argument_exception",
        "reason": "can't merge a non object mapping [error] with an object mapping"
    },
    "status": 400
}

Expected behavior
The mapping specified in the create index API call overrides the template mapping, and the index is actually created.
Additional Details
Plugins
N/A.  Reproduced on a local cluster using HEAD of 2.x branch, using ./gradlew clean run.
However, this is a significant issue for any plugin that uses a system index.  It's a critical issue for plugins that prevent a node from starting up if the system index is not created.
Host/Environment (please complete the following information):
Reproducable locally on macOS; occurred on a production cluster on AOS, OpenSearch version 2.15
Additional context
This is significant in that:

Many plugins use system indices
These index templates are in control of the user and yet conflict with system indices
There's no easy way for a plugin, when creating a system index, to avoid this conflict or specify "don't use templates at all", essentially allowing a user to break several plugins without really even knowing it.

In this case, to work around the bug I had to create a (temporary) higher priority matching template with an empty object in the mapping field to prevent the incompatible mapping.
Stack trace leading to the error:
java.lang.IllegalArgumentException: can't merge a non object mapping [error] with an object mapping
        at org.opensearch.index.mapper.ObjectMapper.merge(ObjectMapper.java:767) ~[opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.index.mapper.ObjectMapper.doMerge(ObjectMapper.java:798) ~[opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.index.mapper.RootObjectMapper.doMerge(RootObjectMapper.java:364) ~[opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.index.mapper.ObjectMapper.merge(ObjectMapper.java:771) ~[opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.index.mapper.RootObjectMapper.merge(RootObjectMapper.java:359) ~[opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.index.mapper.Mapping.merge(Mapping.java:130) ~[opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.index.mapper.DocumentMapper.merge(DocumentMapper.java:310) ~[opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.index.mapper.MapperService.internalMerge(MapperService.java:521) ~[opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.index.mapper.MapperService.internalMerge(MapperService.java:483) ~[opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.index.mapper.MapperService.merge(MapperService.java:447) ~[opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.cluster.metadata.MetadataCreateIndexService.updateIndexMappingsAndBuildSortOrder(MetadataCreateIndexService.java:1441) ~[opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.cluster.metadata.MetadataCreateIndexService.lambda$applyCreateIndexWithTemporaryService$3(MetadataCreateIndexService.java:523) [opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.indices.IndicesService.withTempIndexService(IndicesService.java:982) [opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexWithTemporaryService(MetadataCreateIndexService.java:514) [opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequestWithV2Template(MetadataCreateIndexService.java:783) [opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequest(MetadataCreateIndexService.java:457) [opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequest(MetadataCreateIndexService.java:483) [opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.cluster.metadata.MetadataCreateIndexService$1.execute(MetadataCreateIndexService.java:389) [opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]
        at org.opensearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:67) [opensearch-2.18.0-SNAPSHOT.jar:2.18.0-SNAPSHOT]

To be honest, I think the existing behavior makes sense. You apply a template as a rule to be followed with indices to be matched, and it follows as directed to.
Now to get to the point how to obtain the desired behavior. I think there is a work-around which makes sense. (There may be better ways to do it which I'm not aware).
So basically let's say you want to create a different rule for your system indices. So,

Create a new component template

PUT another _component_template: error_mapping_template2
{
  "template": {
    "mappings": {
      "properties": {
        "error" : {
              "type": "text"
            },
            "status": {
              "type": "integer"
            }
          }
        }
      }
    }
  }
}

Create another index-template with a higher priority for a sub-set of indices:

PUT _index_template/match_all_template
{
  "index_patterns": [
    "system*"
  ],
  "template": {
    "settings": {}
  },
  "priority": 20,
  "composed_of": [
    "error_mapping_template2"
  ],
  "version": 1
}

Now your system* patterns will obey your higher priority template.

PUT /system-index
{
  "mappings": {
    "properties": {
      "error": {
        "type": "text"
      }
    }
  }
}

(this succeeds)

To be honest, I think the existing behavior makes sense. You apply a template as a rule to be followed with indices to be matched, and it follows as directed to.

Yes, to a point.  You can (and the documentation says as much) override any template field mapping; the templates are just defaults.
But there are some mappings that you can't override, and that's not documented and not obvious to users.

I think there is a work-around which makes sense.

Yes, I described the workaround with a higher-priority template. You don't even need the complexity of a new composable template, just one with empty mappings:
PUT _index_template/temporary_high_priority
{
  "index_patterns": [
    ".*"
  ],
  "template": {
    "mappings": {}
  },
  "priority": 1000000
}

This works fine for "fixing" a plugin, but in order to use this workaround for a plugin that wants to create a system index you would have to:

query the existing templates
iterate the templates and use some fancy regex or glob match to identify matching ones, or just assume all match and find the max priority. Also save a set of their names.
increment that max priority
create a temporary template making sure the name doesn't conflict, with the highest priority
create your system index
delete your temporary template.

Compare that to alternative solutions like:

have a "use_templates=false" parameter for create index
have a "template" : "none" field in the create index body
forbid user match-all ([*]) templates from matching against system indices

If we're not going to allow full override behavior I'd prefer one of the above solutions, to give plugins (or any index creator) the power to completely override a template.

System index shouldn't follow the index template created by user for their business purpose. I vote for filtering out the system index creation from index template.

System index shouldn't follow the index template created by user for their business purpose. I vote for filtering out the system index creation from index template.

@zane-neo Thanks for this suggestion. I generally agree. Follow-up question: is there a specific definition of "system index" that we can use for this filtering?  Is it as simple as a leading dot, or does it need to be "registered"?  (CC: @cwperks for comment here)

Looks like it's available for injection here: https://github.com/opensearch-project/OpenSearch/blob/6c7581ef6c67abc5bab0431b2be430361d8a7392/server/src/main/java/org/opensearch/node/Node.java#L1493
But could be cleaner if we can access it from one of the arguments passed to createComponents().

Now to just figure out where to fetch that object when matching indices with a template...

And one clarification for my comment above. The system index registration supports "patterns". When a concrete index is made that matches the pattern, it is considered a system index.
For instance is the alerting plugin registers .opendistro-alerting*, then as soon as .opendistro-alerting-config, .opendistro-alerting-detectors, etc. are created they are system indices since they match one of the registered patterns.

Looks like systemIndices is already present in the MetadataCreateIndexService:
https://github.com/opensearch-project/OpenSearch/blob/456ca97f077929ba51d53dc8578b9b770e3a2417/server/src/main/java/org/opensearch/cluster/metadata/MetadataCreateIndexService.java#L276
We also already ignore hidden indices here:
https://github.com/opensearch-project/OpenSearch/blob/456ca97f077929ba51d53dc8578b9b770e3a2417/server/src/main/java/org/opensearch/cluster/metadata/MetadataCreateIndexService.java#L437-L451
So we probably just need to add system indices to that list (or perhaps make them hidden?  Is that something in control of plugins?)

System index shouldn't follow the index template created by user for their business purpose. I vote for filtering out the system index creation from index template.

@zane-neo Thanks for this suggestion. I generally agree. Follow-up question: is there a specific definition of "system index" that we can use for this filtering? Is it as simple as a leading dot, or does it need to be "registered"? (CC: @cwperks for comment here)

I believe it's a simple leading dot for system index, I think it's the current convention in OpenSearch.


Feature/batch program

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

149 of 186 (80.11%)  changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.7%) to 66.93%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

compass/exceptions.py
5
6
83.33%

compass/dao/csv.py
56
59
94.92%

compass/views/api/student.py
4
37
10.81%

Totals

Change from base Build<PHONE_NUMBER>:
0.7%

Covered Lines:
2291

Relevant Lines:
3423

💛  - Coveralls


Add UI for controlling more settings

Zulip has a very large number of settings that a user can change, and even more that an org admin can change. The mobile apps (both the legacy zulip-mobile app, and this new app) provide UI for controlling only a small number of these settings.
Most users will never touch most of the settings; most of those they do, they'll touch just once, setting to their preferred values, and never touch again. When a user does want to change a setting that's not in the mobile app, they can always resort to the web app — even if their phone is the only device at hand, they can use their phone's browser. So the bulk of the settings are of low value to implement; and it'd be a lot of work to implement all of them, so we won't be setting out to do that comprehensively in the near or medium term.
Some settings come up more often, though. Any setting that it seems like a large swath of users will want to change, or some users will want to frequently change, is one we should consider implementing.
This is an umbrella issue for us to collect feedback on settings that users would like to see implemented. We'll file individual issues for specific settings when we decide to actually implement them.
Related issues

See the other issues with the "a-settings" label.

One piece of feedback last week:

Are there some settings in particular you find yourself regularly missing in the current [legacy] mobile app?

In particular, the detailed notification settings in Personal settings would be very useful to have, and also user group management. Most other settings I guess would just be nice to have, but I can't think of any others that are necessary to me.

The first part calls for going beyond

#661

to the finer-grained notification settings the web app offers controls for.


Added code generation for OnXyz and SendXyz methods (1/2)

This is part one that only includes a few file changes to make the objective a little clearer.  the next is just a bunch of deleted code (yay deleted code! 🥳 )

TLDR: I'm sick of trying to keep all the methods in sync, but want to offer both an interface and delegate based interface for every handler.  This solves that since handlers follow a fairly common pattern.

Really cool idea! First seeing source generators in action. How was the dev experience with em?

@NTaylorMullen I was actually pretty pleased with it.  I have not played with the latest source generators but I assume they would be fairly similar.  Sometimes I'd break things literally in half, break the generator, and using generated methods and things fall apart fast... however that's what unit tests are for.


feat(core, crashlytics, analytics): Support latest stable Android core 1.7.0

Description
Hi all,
Currently Android code latest stable version is 1.7.0
This PR is to support Android core 1.7.0 due to the opened issue:
[firebase_core][firebase_analytics][firebase_crashlytics] Build APK failed:verifyReleaseResources'. in Android core 1.7.0 and compileVersion 31 #7723

By upgrading compileSDKVersion to 31 solve the issue since the issue:
AAPT: error: resource android:attr/lStar not found.
lStar which is a system attribute that's new as of API level 31
This is why causing the error and failed to compile and build APK
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

@Salakar  Hello Salakar
This is my first time send out the PR to FlutterFire. Noticing that I had to sign the CLA.
I've just signed the CLA. I would like to request for the Repository manager who I suppose is you by seeing you are the 1st person listed in the Insight Tab.( If im tagging the right person) to click re-run button next to description as documentation in CLA :)
Thank you for your help!

Hey @chloe722, good work 😄! Is there any chance you could also update the compileSdkVersion version across all the plugins that are listed here which aren't deprecated? We'd prefer to roll these changes inside one PR if possible. Thanks.

Hi @russellwheatley
I went through all the listing packages and update the compileSdkVersion that aren't at latest 31. PR is ready to check again ! Thank you :)


Update LICENSE file

Fix copyright year in License file

SonarCloud CI has been fixed at https://github.com/trustwallet/wallet-core/pull/3665


BelongsToManyCheckboxList checkboxes are not reset/cleared after 'create & create another'

Package
filament/forms
Package Version
2.8.3
Laravel Version
8.78.1
Livewire Version
2.8.2
PHP Version
8.1
Bug description
If you use BelongsToManyCheckboxList and click the button 'create & create another', on the next screen the selected checkboxes are still checked.
Steps to reproduce
No response
Relevant log output
No response

Fixed by #1190.


updated main script filename in docker launch script

Using docker script, I couldn't launch the container (error : not finding the main script file in /StaCoAn/src/main.py). I simply put the new main script filename in the stacoan.sh file inside the docker folder to make it work :)

https://github.com/vincentcox/StaCoAn/commit/b07240a050667315e5db4a9d2326bd40de86860e
Indeed, thanks for notifying me. Should be fixed in the latest main.


COUNT function

Description

The COUNT function receives a query expression as param an returns a table containing only one row, called count with the total number of rows returned from the query passed in.
Definition:
query = GET <[fields, ]> FROM <entity> <[entity_id, ]> ON <chain>
COUNT(<query>)

Examples:
# ✅ Valid query
COUNT(GET * FROM tx WHERE block = latest ON eth)

Can I attempt this issue?

Can I start working on this?

@0xdevcollins assigned to you


Spacer time-out

Spacer back-end currently does not respect the set time-out.

Also, printing of Horn clauses is done after checking them. Which means we cannot get them if Spacer cannot find a solution.

Added timeout and also moved the printing of horn clauses.


luci-app-wireguard: interface change causes an item to be deleted

Steps to reproduce:

Add new WireGuard interface: (bogus keypair)

uci set network.wg0.proto='wireguard'
uci set network.wg0.private_key='QBkdsTbMxI6xzhZDCY6t+wGQddy6DOTfSTxph+UFMXM='
uci add_list network.wg0.addresses='<IP_ADDRESS>/32'
uci set network.wg0.dns='<IP_ADDRESS>'
uci add network wireguard_wg0
uci set<EMAIL_ADDRESS>uci set<EMAIL_ADDRESS>uci add_list<EMAIL_ADDRESS>uci set<EMAIL_ADDRESS>uci set<EMAIL_ADDRESS>uci set<EMAIL_ADDRESS>uci set<EMAIL_ADDRESS>uci commit network

Network → Interfaces → WG0 → "Advanced Settings" tab → uncheck "Force link" then "Save & Apply"
Network → Interfaces → WG0 → "Advanced Settings" tab → check "Force link" then "Save & Apply"
(sometimes you have to repeat steps 2 and 3, you'll see it when pending changes increments to 2)

Actual behavior:
network.wg0.dns='<IP_ADDRESS>' has been deleted from the configuration
# uci show network.wg0
network.wg0=interface
network.wg0.proto='wireguard'
network.wg0.addresses='<IP_ADDRESS>/32'
network.wg0.private_key='QBkdsTbMxI6xzhZDCY6t+wGQddy6DOTfSTxph+UFMXM='

Expected behavior:
network.wg0.dns='<IP_ADDRESS>' should be in the configuration
# uci show network.wg0
network.wg0=interface
network.wg0.proto='wireguard'
network.wg0.addresses='<IP_ADDRESS>/32'
network.wg0.private_key='QBkdsTbMxI6xzhZDCY6t+wGQddy6DOTfSTxph+UFMXM='
network.wg0.dns='<IP_ADDRESS>'

Additional Information:
OpenWrt version information from system /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='22.03.2'
DISTRIB_REVISION='r19803-9a599fee93'
DISTRIB_TARGET='ath79/generic'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='OpenWrt 22.03.2 r19803-9a599fee93'
DISTRIB_TAINTS=''

Workaround: set network.wg0.peerdns=0 as well


fix: UPS tracking and improvments

Proposed change

Fix UPS Tracking
Add ConfigEntryNotReady if we can't pull data on startup
Change to use self._attr_unit_of_measurement
Update tests for changes

Type of change

[ ] Dependency upgrade
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests
[ ] Documentation update
[ ] Adds a new shipper
[ ] Update existing shipper

Additional information

This PR is related to issue: n/a

Codecov Report

Merging #498 (41ebd92) into dev (17fd86e) will decrease coverage by 0.62%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##              dev     #498      +/-   ##
==========================================
- Coverage   99.06%   98.44%   -0.63%
==========================================
  Files           6        6
  Lines        1287     1284       -3
==========================================
- Hits         1275     1264      -11
- Misses         12       20       +8

Impacted Files
Coverage Δ

custom_components/mail_and_packages/const.py
100.00% <ø> (ø)

custom_components/mail_and_packages/__init__.py
97.27% <66.66%> (-2.73%)
:arrow_down:

custom_components/mail_and_packages/sensor.py
98.30% <100.00%> (-0.09%)
:arrow_down:

custom_components/mail_and_packages/helpers.py
98.15% <0.00%> (-1.00%)
:arrow_down:

custom_components/mail_and_packages/camera.py
97.93% <0.00%> (+2.06%)
:arrow_up:


[miniz] Update to 3.0.2

Describe the pull request

What does your PR fix?
Updates miniz to 3.0.2

Which triplets are supported/not supported? Have you updated the CI baseline?
As before, Yes

Does your PR follow the maintainer guide?

Yes

Thanks for the update!


Added vercel analytics to docs

Incorporated Vercel analytics into the docs. This is my initial experience with Changesets, and I’m not entirely sure how to utilize it. Since I don’t have the Bun runtime installed, I manually added the changes.
Fixes #82

@kratos-respawned you can remove the changeset stuff as that only applies to changes made to the cli folder

@kratos-respawned you can remove the changeset stuff as that only applies to changes made to the cli folder

done

@kratos-respawned please rebase with beta