test: KeyRegistry symbolic tests

Motivation
Followup to #397 adding Halmos symbolic tests for the KeyRegistry.
Merge Checklist
Choose all relevant options below by adding an x now or at any time before submitting for review

[ ] The PR title adheres to the conventional commits standard
[ ] The PR has been tagged with change type label(s) (i.e. documentation, feature, bugfix, or chore)
[ ] The PR's changes adhere to all the requirements in the contribution guidelines
[ ] All commits have been signed

Additional Context
If this is a relatively large or complex change, provide more details here that will help reviewers.

PR-Codex overview
Focus of the PR
This PR focuses on adding test cases for the KeyRegistry contract.
Detailed summary

Added SPDX license identifier
Imported necessary contracts and interfaces
Initialized contract variables
Set up metadata validator and IdRegistry
Registered fids
Set up KeyRegistry
Set initial states
Added a function to verify KeyRegistry invariants
Added a function to split cases
Created calldata for different function selectors

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@horsefacts The test failure was due to known limitations of Halmos, and I've adjusted the test as a workaround: https://github.com/farcasterxyz/contracts/pull/398/commits/6e242f884191860110e3b3cbea27af17b44f4f6f
Here are the specific limitations: In the add, addFor, or trustedAdd function, an external call is made to validators[keyType][metadataType], where both keyType and metadataType are symbolic. Since only validators[1][1] is set to the StubValidator, the expression validators[keyType][metadataType] is not further evaluated and remains as it is. (Halmos doesn't automatically perform case splitting here, to prevent potential path explosion.) Then, the target of the external call remains undetermined, causing the symbolic execution to fail.
To address this limitation, I've added explicit case-splitting for the add, addFor, and trustedAdd functions in the test. Explicit case splitting can be done by simply adding a if-statement with no-op. For convenience, I've introduced a helper function split_cases() for that.
Please let me know if you have any questions or comments!

Thanks for this @daejunpark! This technique does make sense. I could tell the error had something to do with an external call to a symbolic address but couldn't work out the right way to constrain it.


[1.12] client crash on startup

Issue description:
client crash's on startup
What happens:
yep, the client crash's on startup
What you expected to happen:
loading of mod... ;-)
Version (make sure you are on the latest version before reporting):

Minecraft: 1.12
Forge: <IP_ADDRESS>3
Refined Storage: 1.5.19

Does this issue occur on a server? [yes/no]
didn't test it, error was on starting client.
If a (crash)log is relevant for this issue, link it here:
crash-2017-10-09_08.57.29-client.txt

Update your Forge. I should probably set a minimum version.

okay, but sorry for asking.
am i blind or isn't the <IP_ADDRESS>3 the latest for 1.12.0?
forge 1.12
is there a way to use later forge versions on 1.12.0? (1.12.2 - <IP_ADDRESS>2 for example)

Oh, indeed, it seems like I broke 1.12.0 compatibility... I will push a new version that brings back compatibility with 1.12.0 later today.

Fixed in RS 1.5.20

thanks a lot!


Original iteration of adding comments

Done in group in #women-in-tech's voice channel last week.
In branches, not yet merged:

Adding styles
Adding RUD to comments which already have a Create
Adding profile pictures
Adding password, name, and email change

Original submission:
Comment models, route, controllers. No views yet https://github.com/100devs/binary-upload-boom/pull/272/commits/ecdee42fd981269eb53aefcfdf5fcd261a8543a7
Comments visible in post.ejs https://github.com/raissa-k/latest-social-network/commit/6dc9e09f463f0dad56dd1519a8c957f6fee1a95d


REST and Datastore Emulator Support

Use transport if it's passed in so rest can be selected.
Make key_file_path optional. This way if the DATASTORE_EMULATOR_HOST env var is provided we can use the  local emulator without having a valid credentials json file.

@tkasa can you please update the documentation (README) also (related to config and nullable key file path)?

@tkasa can you please update the documentation (README) also (related to config and nullable key file path)?

@arafatkn Updated now.


Cell counting

Thanks for developing Cellpose and releasing it publicly.
I am interested in applying Cellpose model to segment some cells. My quick question is that I wonder if the current Cellpose program can count how many cells are segmented as a result. I didn't find a related function yet in both the paper and github. Is there a way of counting how many cells are segmented using some current functions? If not, is there a room for counting the number of segmented cells as a result by modifying the current python codes?

from the saved NPY file:
import numpy as np
dat = np.load('img_seg.npy', allow_pickle=True).item()
ncells = dat['masks'].max()

is there another way that you would want this output?

closing due to inactivity

Another way to do this is:
from cellpose import models, utils
from cellpose.io import imread

model = models.Cellpose(gpu=True, model_type='cyto3')

files = ['cell_00001.bmp', 'cell_00002.bmp']
imgs = [imread(f) for f in files]

masks, flows, styles, diams = model.eval(imgs, batch_size=8, diameter=None, channels=[0,0],
                                         flow_threshold=0.4, do_3D=False)

for idx in range(len(imgs)):
    outlines = utils.outlines_list(masks[idx])
    print("Number of Cells:", len(outlines))


Show all rows causes total page number is minus rows number (ex. 1 from -28)

Issue Type
Bug
Specs
vue-good-table 2.11.0
Chrome 67.0.3396.99
Expected Behavior
When I select show all rows, I would like to see info on right bottom : page 1 from 1.
Actual Behavior
I actually see page 1 from -28 (rows number)
Steps to Reproduce the Problem

Load page with table
Select show all records
See pages section

Possible solution
Change method in Table.vue from
 pageChangedEvent() {
       return {
         currentPage: this.currentPage,
         currentPerPage: this.currentPerPage,
         total: Math.floor(this.totalRowCount / this.currentPerPage)
       };
     }

to
 pageChangedEvent() {
       return {
         currentPage: this.currentPage,
         currentPerPage: this.currentPerPage,
         total: this.currentPerPage === -1 ? 1 : Math.floor(this.totalRowCount / this.currentPerPage)
       };
     }

@xaksis no problem ;) could you please tell me, when it can be done?

@wussup v2.11.1 now has the fix. Unfortunately, it wasn't as simple as correcting the pageChangeEvent object... since that is just the payload to the outside component for a page change event specifically (which isn't fired on perPageChange).
Internally VgtPagination had to be updated to convey the right currentPage value to VgtPaginationPageInfo component so that the input widget could be adjusted accordingly.
closing.


[BEAM-25] Temporarily reject stateful ParDo in DataflowRunner (until support is added)

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[x] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @bjchambers
At present, the user-facing API for stateful DoFn is in the codebase but prevented from use. It is ParDo.of(...) that rejects stateful DoFn. In #1399 I am removing this rejection, so I need to add it to all runners until they support the API.
I have also added a JUnit category so runners can exclude this from their RunnableOnService test suites.

Filed BEAM-1038 against myself following @amitsela's comments on #1409.

I'll reorder the change to DoFnSignature before the other changes when I squash.


fix default block_exists

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1dd2510). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #484   +/-   ##
=========================================
  Coverage          ?   45.87%
=========================================
  Files             ?      131
  Lines             ?    13296
  Branches          ?        0
=========================================
  Hits              ?     6100
  Misses            ?     7196
  Partials          ?        0

Impacted Files
Coverage Δ

chain-storage/src/store.rs
0% <ø> (ø)

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 1dd2510...c56fb4c. Read the comment docs.

It's a bit questionable whether block_exists() should return true for a block that can't actually be retrieved. However I guess this will all become academic once the genesis data becomes a real block.

Yes, vincent raised a similar note regarding this. This will change once we have the initial block.


ChangeTextureAtlasBuilder into expected Builder conventions

The old API wasn't actual builder format. When making my SpriteSheet and using it as an example, I improved it on my own and decided to implement those changes back to Bevy for the TextureAtlasBuilder.
This is a light API breaking change.

Thanks for those changes @cart, I was pulling stuff from my spritesheet and missed those doc comments.


[Relax] Easier use of Function.bind_params with relax.op.create.*

The Function.bind_params method requires all bound values to have StructInfo annotations.  While these are generated on construction for relax::Constant and relax::PrimValue, the most common cases of bound values, other useful expression such as relax.op.zeros(shape,dtype) do not have StructInfo until they are normalized.  In addition, because Function.bind_params may be used in contexts that do not have a relax.BlockBuilder available, performing this normalization is not straightforward.
This commit updates the constructors for Relax operations within the tvm.relax.op.create namespace to infer their StructInfo on construction, if it is possible to do so.  This allows these operations to be used inside Function.bind_params.

Rebase onto main, since the CI failures were caused by https://github.com/apache/tvm/pull/17371.


The OLE DB provider "OraOLEDB.Oracle" has not been registered.

When I use mssql-docker, is there any way to use Database Link with Oracle?
In default, the OLE DB provider for Oracle isn't avaliable because Client or ODAC need to be installed as well.
How we can resolve this?

Are you using the mssql-server-linux image?  If so, this is a limitation of SQL Server on Linux right now.  We dont have a way to load these kinds of DLLs into the SQL PAL.

Yes, mssql-server-linux.
So, and in mssql-server-windows (developer or express), this is possible?
Thank you!

It might be possible in Windows, but we havent tested it yet.

Ok, thank you!


Add a contributing guide "CONTRIBUTING.md"

Fixes https://github.com/redhat-beyond/HighTeach/issues/5.

Please squash the commits so we can merge it


Fix wiki links

May have to add .html to the links/filenames (or .md for use on GitHub rendering), but ideally would preserve the extension-less URLs to match the source MediaWiki website.

See also https://github.com/github/pages-gem/issues/69

See also https://github.com/jgm/pandoc/issues/1982 - we or pandoc also turn spaces into underscores in the relative URLs, and deal with special characters like percent signs with encoding, etc.
This also applies to the filename for each wiki page, where we probably need to follow the MediaWiki "canonical database form". Quoting http://www.mediawiki.org/wiki/Manual:ImportImages.php which focused on files (see our issue #1):
Note: The "canonical database form" ... is obtained from the file name by capitalizing the first letter, replacing all spaces with underscores, and then replacing multiple consecutive underscores with one underscore.
I've not found an ideal reference for this yet, see also http://en.wikipedia.org/wiki/Help:Page_name which also talks about percent-encoding.

Having tested this now, GitHub/Jekyll serves pages with and without the .html extension. This means we can continue to use the MediaWiki style links (without extension) and work when rendered via GitHub/Jekyll. However, the links won't work when viewing the markdown directly in GitHub where the links would need a .md extension.
However, there are likely to be some broken links due to the case (and special character) rules.

With the biopython.org wiki we were lucky that one URL was a problem - wiki/BioSQL - minor enough we can probably just move the single page child page wiki/BioSQL/Windows to wiki/BioSQL_on_Windows (or similar) and remove the problematic folder wiki/BioSQL/.
For www.open-bio.org there are currently ten folders like wiki/BOSC/ and wiki/BOSC_2014/ which make direct access to the parent page require adding .html to the URL. See https://github.com/OBF/OBF.github.io/issues/1

The pandoc issue was fixed, the MediaWiki writer will do spaces to underscores in wikilink URLs.

Still issues (probably worth filing with pandoc), e.g. on the OBF main page,
```the scope and role of our [[membership]].inMain_Page.mediawiki``
Pandoc v1.15.2 made this the scope and role of our [membership](membership "wikilink"). in Main_Page.md.
It should have been made into a wikimedia style page name with leading capital, i.e. the scope and role of our [membership](Membership "wikilink"). instead.

Another problem, again on the OBF main page,
`` [[:File:OBF-Bylaws.pdf| Our bylaws]] lay out how the Board is elected, ...```
with pandoc v1.15.2 gives:
[ Our bylaws](:File:OBF-Bylaws.pdf "wikilink") lay out how the Board is elected, ...
Interestingly :File:OBF-Bylaws.pdf as the URL works in mediawiki, redirecting to File:OBF-Bylaws.pdf which seems more sensible.
I've edited the wiki to link directly to the file with:
[[media:OBF-Bylaws.pdf|Our bylaws]] lay out how the Board is elected, ...

I've created another issue in pandoc re the files .
https://github.com/jgm/pandoc/issues/3052
Need to also look at what happens with media: links

Have you found any solution for fixing links to other .md files, adding the extension?  I wonder if anybody else wrote a script to post-process it, parse the generated MD, check links, and try to apply fixes to links that don't work according to which way they're broken.

@ec1oud We've just used extension-less URLs in all the MediaWiki conversions thus far.

I believe this is all working although we are using the extension-less URLs (with an implicit and optional .html at the end).
e.g. https://biopython.org/wiki/Download and https://biopython.org/wiki/Download.html are the same page, relative links like "Download" work.


non-stdin golang formatter

hey! thank you for creating this plugin. In reddit comments you asked about formatters that do not support stdin. There is one that i use - https://github.com/incu6us/goimports-reviser
It had to be set up using temp files in null-ls. (and it is kinda broken for it right now)

Thanks @malinka-2233!
I just submitted a commit that adds support and added an example in the readme file specific to goimports-reviser.


Automated cherry pick of #6460

Cherry pick of #6460 on release-5.28.
/cc  @lieut-data

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: 457d2a0437e6963a68e9e82e367c049060cfa585


Uncaught Error: spawn E2BIG

[Enter steps to reproduce:]
This happens every time I open Atom and it reopens my notes files (plaintext). It happened on the last version and it happens on this version.
Atom: 1.29.0 x64
Electron: 2.0.5
OS: 10.13.4
Thrown From: Atom Core
Stack Trace
Uncaught Error: spawn E2BIG
At internal/child_process.js:323

Error: spawn E2BIG
    at _errnoException (util.js:1024:11)
    at ChildProcess.spawn (internal/child_process.js:323:11)
    at exports.spawn (child_process.js:514:9)
    at Object.exports.fork (child_process.js:115:10)
    at new Task (/Applications/Atom.app/Contents/Resources/app/src/task.js:37:52)
    at Function.module.exports.Task.once (/Applications/Atom.app/Contents/Resources/app/src/task.js:19:20)
    at Object.startTask (/Applications/Atom.app/Contents/Resources/app/node_modules/fuzzy-finder/lib/path-loader.js:18:35)
    at Object.startLoadPathsTask (/Applications/Atom.app/Contents/Resources/app/node_modules/fuzzy-finder/lib/main.js:129:43)
    at get_process.nextTick (/Applications/Atom.app/Contents/Resources/app/node_modules/fuzzy-finder/lib/main.js:31:45)
    at _combinedTickCallback (internal/process/next_tick.js:131:7)
    at process._tickCallback (internal/process/next_tick.js:180:9)

Commands
?
Non-Core Packages
None

What OS are you on?  Are your files paths in the project really long?  (200+ characters)

In addition, how large is the file that Atom is trying to open?
In the meantime, you should be able to get around this using atom --clear-window-state, but as a word of caution, you'll lose any unsaved changes in your projects.

OS is OSX 10.13.4.
Paths are very short ~/Documents/NOTES for example.
I can't actually find any issues caused from this error, it appears spurious.

Also,

how large is the file that Atom is trying to open?

Tiny, we're talking less than 10k probably for all my notes. These are like todo lists and stuff.

In the meantime, you should be able to get around this using atom --clear-window-state, but as a word of caution, you'll lose any unsaved changes in your projects.

Did you give this a try @bhartvigsen (or did you not want to risk losing unsaved changes)?

I tried it and the error goes away and I'm left with a blank Atom. So really all this tells us is that the error is triggered when re-opening a handful of tabs of plaintext files, not a whole lot of insight I think that can be drawn from that.

This issue still exists in 1.40.1 which I believe is the latest version. This occurs on OSX 10.13.6.
I can reproduce it by closing Atom and then reopening it. Here is the stack trace:
Error: spawn E2BIG
at ChildProcess.spawn (internal/child_process.js:357:11)
at spawn (child_process.js:540:9)
at Object.fork (child_process.js:121:10)
at new Task (/Applications/Atom.app/Contents/Resources/app/static/:14:41354)
at Function.Task.once (/Applications/Atom.app/Contents/Resources/app/static/:14:42100)
at Object.startTask (/Applications/Atom.app/Contents/Resources/app/static/:11:816751)
at Object.startLoadPathsTask (/Applications/Atom.app/Contents/Resources/app/static/:11:189167)
at get_process.nextTick (/Applications/Atom.app/Contents/Resources/app/static/:11:187131)
at process._tickCallback (internal/process/next_tick.js:61:11)


Support redux ^4.0.0

Currently can't use flutter redux with this library as it requires redux version ^4.0.0.

Ah, good call! I knew I forgot to update one of these libs

Published version 0.4.0 with support for Redux 4.x!


[WIP] Uniswap v3 risk metrics

What's done:

influx_univ3.py: Ingesting metrics and catching most exceptions
influx_metrics_univ3.py: Calculating metrics using above data
TWAP length of 1 minute using uni v3 oracle
Window length of 1 min is enforced with a tolerance of 10 secs. Both window length and tolerance are parametrized

What's left:

Making influx_univ3.py a bit more resilient. Still facing some time out issues
Deploying these scripts on heroku and checking how things run over an extended period of time

@mikeyrf I have already deployed this branch to my project pipeline on Heroku and can confirm that the scripts run on Heroku. Adding descriptions for important files/changes below so you can prioritise these files as you review the code.

Aptfile: This is a config file required to run the heroku apt buildpack (https://elements.heroku.com/buildpacks/heroku/heroku-buildpack-apt). This buildpack is required to install gsl.
pyproject.toml:

Removed scipy because poetry is unable to install it
Added my fork of eth-brownie to be able to use alchemy's archive node through Heroku but without relying on the brownie command brownie networks add

sushi_quotes.json: This is a copy of quotes.json but named with the prefix "sushi_" so it's understood that these quotes are different from the uni v3 ones. I've retained the original quotes.json file too so that older deployments don't stop running.
influx_metrics.py: Fixed a bug related to column names in the original script
influx_metrics_univ3.py: Calculates metrics from price cumulatives. Logical flow of code as follows -

Find the timestamp when metrics were last recorded in the bucket ovl_metrics_univ3. Otherwise, if metrics have never been recorded before then just start from 30 days back.
Find list of timestamps between find_start() and now
Get all price cumulatives for above list of timestamps
For each timestamp, calculate TWAPs and metrics. TWAPs are hourly and metrics have a 90d lookback period.

influx_univ3_1h.py: Gets price cumulatives from archive node at 10 min intervals. These are used in influx_metrics_univ3.py to calculate 1h TWAP.

A batch of cumulatives are pulled from the archive node using multiple threads, these are converted to a pandas dataframe which is pushed to influx in one go. Therefore the entire batch containing data for many days gets pushed to influx at once, making data collection for weeks/months faster.
The same script also supports real time data collection. When real time data is needed, the size of the pandas dataframe being pushed to influx is just 1 row (corresponding to the latest/current timestamp).


TrackedGeometry or TrackedImage

This page flips between using OnUpdateTrackedGeometry and OnUpdateTrackedImage such that it's not clear which one should be used.

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

ID: 4db9ec0f-8219-f292-1ac5-6ca607125b33
Version Independent ID: a04e35e0-a4a8-2af9-88a7-a5d44f90901b
Content: QR codes in Unreal - Mixed Reality
Content Source: mixed-reality-docs/mr-dev-docs/develop/unreal/unreal-qr-codes.md
Product: mixed-reality
Technology: mr-dev
GitHub Login: @hferrone
Microsoft Alias: v-hferrone

@sw5813 Can you assist?

Tracked geometry is used for 4.26 and image used for < 4.26.


CI Testing Updates

As we didn't update the linting to use matrix tests on TravisCI, this reverts back to using TravisCI regular tests as before to pass linting for a release.
Furthermore, this migrates over the tests from @olgabot 's PR introducing the TravisCI tests in matrix-style to GitHub Actions which will eventually be (?) our testing platform soonish.
I tried making this cleaner in the matrix tests but let me know if you see something completely missing!
Furthermore this PR bumps to 1.4 for a release 👍
PR checklist

[x] This comment contains a description of changes (with reason)
[x] If you've fixed a bug or added code that should be tested, add tests!
[ ] If necessary, also make a PR on the nf-core/rnaseq branch on the nf-core/test-datasets repo
[x] Ensure the test suite passes (nextflow run . -profile test,docker).
[x] Make sure your code lints (nf-core lint .).
[ ] Documentation in docs is updated
[ ] CHANGELOG.md is updated
[ ] README.md is updated

Upon the final merge of this to dev, the GitHub Actions won't show up here.
Please see this branch update here for the Github Actions tests until then:
https://github.com/apeltzer/RNAseq/runs/253357512

Had to bump Nextflow Version - the CI didn't finish on TravisCI because it only found Java11 JDK instead of Java8 which isn't supported by Nextflow 0.32.0.

Please wait for this to finish too:
https://github.com/apeltzer/RNAseq/commit/3359630828a517b4c75961747f862e0998e1c270/checks?check_suite_id=257688757


Implement write function; Improve error handling; Update style

I have added some code. We will probably need to make the overall use case scenario (logic) as well to make it a service. Maybe we will delegate it to Kylle if he returns.
Let me know what you think.

Yes, and probably we also need to ask AI for writing it's own version of code, but maybe we will do that when Kylle will be able to join us


Callbacks

Closes #331
Checklist

[x] Tests have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?
feature
What is the current behavior? What is the new behavior?
This PR introduces Callback support in Prism (issue #331).

Does this PR introduce a breaking change?
No
Dependencies (needed to be merged first)

https://github.com/stoplightio/types/pull/54
https://github.com/stoplightio/http-spec/pull/31

However, I ended feeling that it is too much to carry the whole engine just for resolving such simple syntax.

Yeah that's totally legit. I'm jumping on this right now!

This is so cool, amazing work @StefanDywersant.
One thing could do with a bit of polish: I was using https://webhook.site/ which is a cool request bin type thing which captures webhooks for testing. Apparently their API is not responding quite how Prism would like:

I guess it's because the callback has rather specific requirements for the callback:
      callbacks:
        actions:
          '{$request.body#/url}?token={$request.body#/token}':
            post:
              summary: 'Receive notification about certain invoice'
              requestBody:
                required: true
                content:
                  application/json:
                    schema:
                      $ref: '#/components/schemas/notification'
              responses:
                200:
                  description: 'Notification successfully processed'
                  content:
                    text/plain:
                      examples:
                        ok:
                          value: 'ok'

Here is what it responded with:
HTTP/1.1 200 OK
Cache-Control: no-cache, private
Content-Encoding: gzip
Content-Type: text/plain; charset=UTF-8
Date: Wed, 06 Nov 2019 15:02:21 GMT
Server: nginx/1.10.3
Transfer-Encoding: chunked
Vary: Accept-Encoding

Anyhow, the error message it gives is not as descriptive as it could be.

[VALIDATOR] ✖  error     Violation: The received media type does not match the one specified in the document

Maaaybe that should actually be displayed as [CALLBACK]? Or if not, a super clear message:
Violation: The description document expects text/plan or application/json but instead it got application/nonsense

Beyond the error message, I suppose if somebody wanted to avoid this problem they would simply not specify a content right?
So instead of:
              responses:
                200:
                  description: 'Notification successfully processed'
                  content:
                    text/plain:
                      examples:
                        ok:
                          value: 'ok'

it would be:
              responses:
                200:
                  description: 'Notification successfully processed'

Beyond the error message, I suppose if somebody wanted to avoid this problem they would simply not specify a content right?

If you do not specify the content prism will also report an error that it couldn't match. Basically callbacks validation acts exactly the same as normal request validation.
That points to a possible problem which I also noticed doing more or less the same as you are doing with webhook.site: when contents are not defined, shouldn't prism accept whatever mediaType of response?
@philsturgeon @XVincentX

@StefanDywersant You're correct, there might be a little bug in the mismatchMediaType function — which checks for something even though there's nothing to look for.
Let's keep this separate though. I'll investigate into this — in meantime I would just change the error message from a generic thing to something more like "I received THIS and instead this is what's available in the document"

@StefanDywersant ahh well this just shows that my next job of "play with proxy server and contract testing to make sure it works as expected" should have been done sooner. My bad.
If the API does not specify content, then anything which comes in is a bonus, maybe a warning or an info, but certainly not an error. It's the sort of thing we'd report to folks via Studio somehow (long way off) saying "Hey we found some content, looks like this is JSON, here is the schema. Wanna save that to your description?" etc.
How do I make a callback which says "I dont care what they respond with im just looking for a 200? A lot of callbacks work this way, they just want a "Yep!" and nothing more.

How do I make a callback which says "I dont care what they respond with im just looking for a 200? A lot of callbacks work this way, they just want a "Yep!" and nothing more.

 Our comments passed each other like ships in the night. If you do the thing he suggested I've got a thumb ready and waiting!

 Our comments passed each other like ships in the night. If you do the thing he suggested I've got a thumb ready and waiting!

Done in a22024aa2a0e381c0f8ef5e25e6466450a39b8e2


cleanup(pubsub)!: rename SubcriptionOptions

BREAKING CHANGE

Rename pubsub::SubscriptionOptions to pubsub::SubscriberOptions as these
are bound to an specific subscriber object.

Fixes #5205

This change is

/cc: @kamalaboulhosn


large images cannot be cleared at the bottom

When using large images, the brush is not applicable in the bottom region. It seems like there is a cut where the brush stops working.

@hhromic works!! Thank you very much


A* isn't a good algorithm for the compute program

The compute program sometimes generates suboptimal routes. Instead of A*, something like Dijkstra's algorithm would be better

A* is optimal, you can't get better routes just by using a less efficient algorithm. What's possible though is that your heuristic isn't "admissible"; I haven't looked yet but as long as you use euclidean distance then A* should return the optimal route. If you have really weird rail links, you could try using a different metric for the actual edge weights though (not the heuristic), such as taxicab or just 2*euclidean.

When A* terminates its search, it has found a path from start to goal whose actual cost is lower than the estimated cost of any path from start to goal through any open node.

I'll look into the heuristic


V2: Update proto version to v2

We were using "v1alpha1", however that can't be right since the main branch already uses a package named "v1": https://github.com/connectrpc/conformance/tree/main/proto/connectrpc/conformance/v1.
(My bad, I didn't realize how the existing protos were structured/named, or I wouldn't have suggested "v1alpha1" initially...)
So this changes it to "v2". The real question: do we hedge our bets and instead call it "v2alpha1"? Or do we just hold off to actually publish (by merging this to main and pushing to the BSR) until we're comfortable enough that "v2" is the right name?
I also went ahead and did git rm _legacy, just because a git grep found some references to "v1alpha1" in there, too. I didn't quite understand why they were there, so I figured it was better to just wipe that whole folder since AFAICT we haven't needed it (and can always get all of that code from the main branch if ever we do need any of it).
When we do merge v2 branch to main, I think we should also create a v1 branch at that time that points to the last commit before the merge. That way we have an easy way to reference the old code.

I was originally thinking the v1 on main didn't matter since we didn't publish those to the BSR yet, but I guess those protos have been available for anyone to use from the repo, so we can't make breaking changes to them now.
My vote would be to hold off until we actually publish and then just use v2, but no biggie either way.

@smaye81 FYI, the v1 protos are on the BSR: https://buf.build/connectrpc/conformance/

FYI, the v1 protos are on the BSR

Oof, that was done due to a miscommunication. I thought we removed them. https://bufprivate.slack.com/archives/C03FFSJELH4/p1697489587709479?thread_ts=1697480343.693549&cid=C03FFSJELH4

FYI, the v1 protos are on the BSR

Oof, that was done due to a miscommunication. I thought we removed them. https://bufprivate.slack.com/archives/C03FFSJELH4/p1697489587709479?thread_ts=1697480343.693549&cid=C03FFSJELH4

Ah yeah I remember when they got published, but I thought they were removed also.


Export SkeletonProps and SkeletonThemeProps interfaces

My team is using this library in a TypeScript project. We've build a wrapper component around a Skeleton component because our wrapper components supports some additional props.
However, we also support all of the props mentioned in the SkeletonProps interface so we want to extend this interface. This isn't possible because the SkeletonProps and SkeletonThemeProps` aren't exported.

This is available as of v2.1.1.


feat(table/scanner): Initial pass for planning a scan and returning the files to use

Very rough initial implementation of metrics evaluation and a simple scanner for Tables that produces the list of FileScanTasks to perform a scan along with positional delete files and so on.
This also includes a framework and setup for performing integration testing that is adapted from the approach used in pyiceberg, creating docker images and a file of tests which are only executed by setting the integration tag which is used in a new workflow which runs those tests.
This provides an end-to-end case of using a table and row-filter-expression to perform manifest and metrics evaluations to create the plan for scanning. The next step would be actually fetching the data!

@Fokko @nastra This should be ready for review now, though there's a weirdness in the number of data files being created for one of the integration testing tables on the CI here vs when I run the docker compose and provisioning locally. I don't know enough about spark-iceberg internals to know whether that is a quirk, expected, or something that I should change the tests for. Any ideas?
I've added a comment in scanner_test.go referencing the weirdness. You can also look at the failed CI runs for examples.

@nastra Any further comments?

thanks for the patience here @zeroshade. I'll do a full review in the next 2-3 days

@zeroshade could you please rebase this one now that all the other PRs are merged?

@nastra All rebased already :smile:


adding react 0.14 support

this fixes #52
There's only one issue that I need your help.
var LinkedValueUtils = require('react/lib/LinkedValueUtils');
This doesn't exist in react 0.14 and ReactLink will be deprecated in the future.
So.. what should we do?

Hmm... That's not really React 0.14 support, but a strict dependency on it. I'm fine using 0.14 in the for our gh-pages. But I would say that *.getDOMNode() should be replace by React.findDOMNode(...) for now. This would make it possible to run react-mentions both on 0.13.x and 0.14. Regarding LinkedValueUtils I would need to talk to @jfschwarz. My best guess would be to simply add our own version, since this thing is really not that hard to implement.

@jfschwarz should also be around next week. He might also be ok with strictly doing a 0.14 version and bumping the major.

Yeah.. the name is a bit misleading.. But we have to move forward anyway.. There's no reason to continue supporting 0.13, IMO. We should just bump the version as this is a breaking change and move on.
About findDOMNode:
From React docs:

If you need access to the underlying DOM node for that component, you can use ReactDOM.findDOMNode as an "escape hatch" but we don't recommend it since it breaks encapsulation and in almost every case there's a clearer way to structure your code within the React model.

Also, findDOMNode doesn't work with 0.14 stateless components.

#54 is better


Merge Button Issue

I am not able to add Accept Merge button in new extension which i am working on
Its asking for proposed api but its not enabling if i add that in my package.json

/dev-question

We have a great extension developer community over on GitHub discussions and Slack where extension authors help each other. This is a great place for you to ask questions and find support.
Happy Coding!


Existing broken links

There are some broken links in README.md, because @yoshuawuyts deleted .github once at 063cbd880465af167e42e92dabb4098cf331768b
But I'm sorry, I don't know the reason and the context.
If it is necessary, I will revert files of .github.
I think it’s better than nothing.
Thanks,
File list

.github/CODE_OF_CONDUCT.md
.github/CONTRIBUTING.md
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/question.md
.github/PULL_REQUEST_TEMPLATE.md
.github/stale.yml

Related PR
#337

Hey! Bumping this again, would the team be happy if we restored those files? CONTRIBUTING.md and CODE_OF_CONDUCT.md feel particularly important. Alternatively, we should at least remove the broken links from README.md. Thanks!
/cc @yoshuawuyts


refactor scripts

Initial checklist

[x] I read the support docs
[x] I read the contributing guide
[x] I agree to follow the code of conduct
[x] I searched issues and couldn’t find anything (or linked relevant results below)
[x] If applicable, I’ve added docs and tests

Description of changes
TODO

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (c774c78) 60.17% compared to head (d8666ed) 60.17%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #193   +/-   ##
=======================================
  Coverage   60.17%   60.17%
=======================================
  Files          13       13
  Lines         349      349
  Branches       29       29
=======================================
  Hits          210      210
  Misses        139      139

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


Fix: Ambient session not working

.longForm / .longFormAudtio can't be used with the .ambient session category - this PR fixes that issue as it uses .default policy instead of longForm

Great, thanks @grubicv. As a JavaScript dev I have no idea what this is change is brining/improving - could you explain the what and why in some more detail here?
Thanks.

@bradleyflood basically you want to use ambient session category on iOS devices when you want to play a sound without affecting the current media being played (such as apple music using avaudiosession) and only when the app is open - in our case it's playing a beat playlist as a backing track for apple music.
https://developer.apple.com/documentation/avfaudio/avaudiosession/category/1616560-ambient
The issue is that iOS doesn't allow you to use ambient as a session category if you put a policy for longForm/longFormAudio since that one is used for playing tracks on the main audio route so it's basically conflicting (you don't want to play it as a regular track, but rather as an ambient sound, but you're trying to route it to the longForm route). In that case an exception occurs on that line stating that and basically blocks you from playing sounds in ambient mode since it can't be set. Therefore you need to use the default policy route that's used for playing ambient audio, so I just added a simple condition that uses .default policy route if user wants to use ambient session category, and longForm/longFormAudio for other things.


⚠ Bofrost.com has degraded performance

In 574cc74, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 822 ms

Resolved: Bofrost.com performance has improved in 83a9932.


Add Microsoft SQL Server Express to Windows VMs

A pull request for the issue: #413 Add Microsoft SQL Express to Windows VMs
Disk Space: 500 Mb
Installation time: 5 minutes
Link to successful canary build with current scripts.

/azp run windows2016, windows2019

/azp run windows2016, windows2019


fix typo in README.md

Found a typo in the README.md. Thought I'd fix it :)

@polferov thanks, but the readme is generated from the content.md
can you update that file as well?

Codecov Report
Base: 93.05% // Head: 69.79% // Decreases project coverage by -23.26% :warning:

Coverage data is based on head (dc91126) compared to base (7941d5e).
Patch has no changes to coverable lines.

: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     #784       +/-   ##
===========================================
- Coverage   93.05%   69.79%   -23.26%
===========================================
  Files         118      118
  Lines       23145    23141        -4
===========================================
- Hits        21537    16152     -5385
- Misses       1608     6989     +5381

Impacted Files
Coverage Δ

src/lib/storage_test.rs
0.00% <0.00%> (-100.00%)
:arrow_down:

src/lib/proxy_task_test.rs
0.00% <0.00%> (-100.00%)
:arrow_down:

src/lib/recursion_level_test.rs
0.00% <0.00%> (-100.00%)
:arrow_down:

src/lib/scriptengine/rsscript.rs
0.00% <0.00%> (-93.45%)
:arrow_down:

src/lib/cli_test.rs
4.47% <0.00%> (-92.24%)
:arrow_down:

src/lib/scriptengine/rsscript_test.rs
0.00% <0.00%> (-86.62%)
:arrow_down:

src/lib/legacy_test.rs
17.64% <0.00%> (-82.36%)
:arrow_down:

src/lib/environment/mod_test.rs
16.15% <0.00%> (-79.86%)
:arrow_down:

src/lib/runner_test.rs
30.37% <0.00%> (-60.92%)
:arrow_down:

src/lib/profile_test.rs
40.27% <0.00%> (-59.73%)
:arrow_down:

... and 43 more

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

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

Did do 👍. Also found the same typo in another place.

@polferov thanks for the change and sorry for late review. i think you added one sentence by mistake. lets drop it and i'll approve the pr. thanks

never mind, i'll merge this and remove thatline.
thanks a lot for helping improve the docs :)


Flaky test cht::segment::tests::drop_many_values under Cargo Tarpaulin

Test cht::segment::tests::drop_many_values is failing occasionally when executed under Cargo Tarpaulin. Perhaps the timings of dropping invalidated cache keys are affected by Cargo Tarpaulin in a non-deterministic way (?)
https://app.circleci.com/pipelines/github/moka-rs/moka/520/workflows/ad175a12-9d63-4a20-b10d-d3dad9b78a81/jobs/506
#!/bin/bash -eo pipefail
docker run --security-opt seccomp=unconfined -v "${PWD}:/volume" \
  --env RUSTFLAGS='--cfg circleci' \
  xd009642/tarpaulin \
  cargo tarpaulin -v \
    --features 'sync, future, dash' \
    --ciserver circle-ci \
    --coveralls ${COVERALLS_TOKEN} \
    --timeout 600 \
|| true

...

failures:

---- cht::segment::tests::drop_many_values stdout ----
thread 'cht::segment::tests::drop_many_values' panicked at 'assertion failed: this_key_parent.was_dropped()', src/cht/segment.rs:1448:13
stack backtrace:
   0: rust_begin_unwind
             at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/core/src/panicking.rs:143:14
   2: core::panicking::panic
             at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/core/src/panicking.rs:48:5
   3: moka::cht::segment::tests::drop_many_values
             at ./src/cht/segment.rs:1448:13
   4: moka::cht::segment::tests::drop_many_values::{{closure}}
             at ./src/cht/segment.rs:1364:5
   5: core::ops::function::FnOnce::call_once
             at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/core/src/ops/function.rs:227:5
   6: core::ops::function::FnOnce::call_once
             at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

failures:
    cht::segment::tests::drop_many_values

test result: FAILED. 112 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 45.93s

I forgot to update this issue. As a workaround, I turned off the assertion when testing with Cargo Tarpaulin: https://github.com/moka-rs/moka/commit/26dfc910f256ec52feeb3945279d5bb86dfbb052


Is this project dead?

No, though it's not supposed to be extended and I've moved onto other projects so maintenance is not top priority. If the project is broken file an issue for why it's broken and someone will likely eventually take a look.


Search Criteria not stored between windows

If I hit select all and see some dungeons and close the window for a minute to do some other things and open the window again it doesn't keep my select all setting.  I have to click it again to add see the search results.
This is fine for select all but if im selecting only 3/4 dungeons then I have to go in and manually reselect those.

Right now that is a technical limitation. I'm currently working on a rework of the UI code to enable this.

The selected search is now stored properly between tabs and closing(opneing the window.


Mix-precisioned training

Hi. We want to use it in mix-precisioned mode, as  our GPU don't have much memory, and we want to speed up the training.
I change the code to use mix-precisioned training feature in TF2. It works for MPC (stage 1).
But for the fine-tuning stage, the loss becomes nan at the very beginning.
I try to debug it, and find out the PositionalEncoding in speech_transformer.py is always returning NaN.
        input_labels = layers.Input(shape=data_descriptions.sample_shape["output"], dtype=tf.int32)
        inner = layers.Embedding(self.num_class, d_model)(input_labels)
        inner = PositionalEncoding(d_model, scale=True)(inner) #it returns NaN
        inner = layers.Dropout(self.hparams.rate)(inner)
        self.y_net = tf.keras.Model(inputs=input_labels, outputs=inner, name="y_net")

could anyone help? Thanks a lot

@iou2much thanks, @leixiaoning please help check this

@iou2much thanks, @leixiaoning please help check this

ok, i will check.  @tjadamlee

Hi. We want to use it in mix-precisioned mode, as our GPU don't have much memory, and we want to speed up the training.
I change the code to use mix-precisioned training feature in TF2. It works for MPC (stage 1).
But for the fine-tuning stage, the loss becomes nan at the very beginning.
I try to debug it, and find out the PositionalEncoding in speech_transformer.py is always returning NaN.
        input_labels = layers.Input(shape=data_descriptions.sample_shape["output"], dtype=tf.int32)
        inner = layers.Embedding(self.num_class, d_model)(input_labels)
        inner = PositionalEncoding(d_model, scale=True)(inner) #it returns NaN
        inner = layers.Dropout(self.hparams.rate)(inner)
        self.y_net = tf.keras.Model(inputs=input_labels, outputs=inner, name="y_net")

could anyone help? Thanks a lot
did you use  os.environ['TF_ENABLE_AUTO_MIXED_PRECISION'] = '1'  for supporting mixed precision training？ @iou2much

Hi. We want to use it in mix-precisioned mode, as our GPU don't have much memory, and we want to speed up the training.
I change the code to use mix-precisioned training feature in TF2. It works for MPC (stage 1).
But for the fine-tuning stage, the loss becomes nan at the very beginning.
I try to debug it, and find out the PositionalEncoding in speech_transformer.py is always returning NaN.
        input_labels = layers.Input(shape=data_descriptions.sample_shape["output"], dtype=tf.int32)
        inner = layers.Embedding(self.num_class, d_model)(input_labels)
        inner = PositionalEncoding(d_model, scale=True)(inner) #it returns NaN
        inner = layers.Dropout(self.hparams.rate)(inner)
        self.y_net = tf.keras.Model(inputs=input_labels, outputs=inner, name="y_net")

could anyone help? Thanks a lot

did you use os.environ['TF_ENABLE_AUTO_MIXED_PRECISION'] = '1' for supporting mixed precision training？ @iou2much

nope. I add this before the model initialization.
tf.keras.mixed_precision.experimental.set_policy('mixed_float16')


Would superqt's ensure_main_thread help here?

I don't fully understand things here so this is a bit of a drive by but would something like superqts ensure_main_thread be helpful here?
https://github.com/napari/superqt/blob/ba1ae92bccc282da040281751b71afcbe4c0e302/src/superqt/utils/_ensure_thread.py#L35
It really nicely solved a problem in napari-micromanager of errors when we tried to update the gui from not the main thread: https://github.com/tlambert03/napari-micromanager/pull/114

Oh, that would help!
The guts of the implementation are at https://github.com/napari/superqt/blob/ba1ae92bccc282da040281751b71afcbe4c0e302/src/superqt/utils/_ensure_thread.py#L106-L125 and make use of a part of the Qt API I did not know existed until just now.

Somewhat related: are you aware of qtpy? https://github.com/spyder-ide/qtpy#qtpy-abstraction-layer-for-pyqt5pyqt6pyside2pyside6
I know mpl has it's own qt compatibility layer, but maybe could use qtpy to simplify that?

We have talked about it (and I am roughly in favor).  But we have our own layer that we understand and it works for our needs.  It is not obvious that picking up a dependency (which will change / break under us 😈 ) is going to be less work in the long run.  Mix of sunk-cost fallacy and devil-you-know.
Our compat layer is now also much better about detecting what is already imported which I think blunts one of the biggest pro arguemnets for qtpy (if everyone uses qtpy -> harder for users to get into broken mixed states).

Re-reading the superqt implementation more carefully part of what I thought was Qt API was actually defined in that file too.  I think the core mechanism is the same (use signal/slots to move the work from the background thread to the main thread).  In the teleporter implementation we rely on having a singleton QObject that we use to push the work through (pro only one, con have to make it on the correct thread, was making custom signals per thing we wanted to push across).  In the superqt scheme there is a generic QObject that is inited with a callable + args + kwargs.  That object is then sent to the main thread and invoked.  Not sure of any cons, pros are it is simpler to explain and easier to use 🤷🏻 .


updates needed to 'getMessage element' in json apis and ajax course

Describe the Issue
curriculum/course/step: 04-data-visualization/json-apis-and-ajax/handle-click-events-with-javascript-using-the-onclick-property.md
This file contains the following test message:
Your code should use the document.getElementById method to select the getMessage element.
However, the reference to "getMessage element" in the test should instead refer to #getMessage element as getMessage is the value of an id attribute.
While we're here also, I noticed that this sentence in the same challenge can be made simpler:
You can implement an onclick event handler which triggers when the user clicks on the element with id getMessage, by adding the following code:
Instead of 'the element with id getMessage' we can just say 'the #getMessage element'? 2 words less but it also makes translating it a lot less wordier for Arabic at least.
Affected Page
https://www.freecodecamp.org/learn/data-visualization/json-apis-and-ajax/handle-click-events-with-javascript-using-the-onclick-property
Your code

Expected behavior
use #getMessage element as described above
Screenshots
No response
System
N/A
Additional context
No response

Thank you for taking the time to open this. However, I do not see a bug here.

However, the reference to "getMessage element" in the test should instead refer to #getMessage element as getMessage is the value of an id attribute.

The test is:
https://github.com/freeCodeCamp/freeCodeCamp/blob/8fe7893b0dc51334d259d459b657093efa565e71/curriculum/challenges/english/04-data-visualization/json-apis-and-ajax/handle-click-events-with-javascript-using-the-onclick-property.md?plain=1#L39-L41
That is how the getElementById method works - it takes the name of an id as a string. The element's id is not equal to #getMessage. The element's id is getMessage.
Hope this clarifies

I understand that getElementById takes an id, but the test description: "Your code should use the document.getElementById method to select the getMessage element." says that we should use the method to select the getMessage element which is not the same thing as saying "to select the element whose id is getMessage".
The 'getMessage element' suggests something that looks like this <getMessage> versus something that has an id attribute.
This is the same standard btw used in all the NRWD course. We say #id-name element when we are referring to an element who id is value is id-name in many places. So we would just be making this sentence adhere to this standard of writing.

Ah, thank you for clarifying. I thought you were referring to the test.

I have made a slight edit to the original description to clarify that the 'test message' is the concern.

Hey @Sboonny @hbar1st @ShaunSHamilton, what is the issue with my PR? please help me


Add docker-compose for verion control and building locally, as well as a few language servers

The proposed implementation of using docker-compose is not yet ready as we have not determined how the build process for these images will be done. With that, we also don't know how we will maintain things like base images as well.
For the time being, I think it would be best to leave that work to the language maintainers until we have good automation around all of that. I have opened a issue related to the changes I have mentioned above here https://github.com/lspcontainers/dockerfiles/issues/8


User can’t see the failure reason of a dataset if it doesn’t have any successful revision.

Original source: https://github.com/datahq/datahub-qa/issues/140 from Adam
Tasks

[ ] rewrite the router logic so User could see the showcase page even if the dataset has an errors.

Analysis
Error is here:
https://github.com/datahq/frontend/blob/378737c51937e86255d38f78bdbcbe34a4fe6fbf/routes/index.js#L389

@AcckiyGerman user always can see failed revisions but he/she must be the logged in as the owner. Was it discussed?

@anuveyatsu Agree, probably @akariv forget to login, when got this bug.


Add a missing staggered hours working pattern

Trello card URL:
https://trello.com/c/4owuXmAO/762-update-working-pattern-options-so-there-is-more-flexibility-around-types-of-role-reflecting-the-needs-of-jobseekers-schools
Changes in this PR:
Add "Staggered hours" to the flexible working options. It is included in the DfE guidance about what flexible working means.

 Update 'working pattern' options so there is more flexibility around types of role reflecting the needs of jobseekers/schools


Update package.json

CoffeeScript on NPM has moved to coffeescript (no hyphen). Please update references to coffee-script to use coffeescript instead.

Fixes: #704

Do we know when this will be merged with master?

This change will not prevent the error on Windows. If the eval is causing the npm install to fail, just changing from coffee-script to coffeescript will not prevent the eval from failing. If version 1 of coffee script is needed for jsforce, then fixing coffee script version to 1.12.7 might be the best choice.


JaxTyping warning and performance issues

Hi @patrick-kidger
For reasons beyond my control, I have to use an old version of JAX, which means an older version of Equinox as well (0.9.2).
I get this error
UserWarning: jaxtyping version >=0.2.23 should be used with Equinox version >=0.11.1

Is this harmless? Is there any performance hit associated with this ?
Thanks,

What this is referring to specifically is that jaxtyping.install_import_hook and equinox.field(converter=...) are not compatible when using jaxtyping>=0.2.23 and equinox<=0.11.0.
The reason is that in this scenario, jaxtyping will run typechecking against your eqx.Module before the converter runs, rather than after it.
As long as that's not a problem for you then you can safely ignore this warning.

There is no performance hit. However, the eqx.field(..., converter=...) might raise false-positive errors. In practice though, if you didn't have issues with converters before, you probably won't experience them now. You can take a look at thisPR, where this warning was introduced.
To disable the warning you can use copybara (as recommend in the comment in the source code), or just downgrade to jaxtyping 0.2.22 .


ISPN-12503: Initial commit for the JIRA ISPN-12503

Please review the committed changes for Jira: ISPN-12503

@durgeshanaokar Some tips for this and future PRs:

The PR title should just be the commit message which should be in format of "ISPN-### ". For example, I had no clue what this PR is about other than the JIRA number at a quick glance.
The description for a PR should have the first line be a link to the JIRA that it references at a minimum. For example https://github.com/infinispan/infinispan/pull/9275. If you feel the issue is a bit more complex, then put any additional pertinent information in there as needed.
Also update the JIRA to say it currently it is in Pull Request Sent status with a link back to the PR on the JIRA.
Separate note: you can also make a PR for preview purposes if necessary to say run the full tests suite. But make sure to put the Preview label.

Of all of these really the first is really the only important one. You will want to reduce friction for other team members to look at your PRs otherwise they can languish and don't give people more reasons for that to happen, haha.

I think this is a good initial attempt. However, something doesn't feel right to me.  The URI can specify ssl, server list, user, pass and all the properties that can be supplied in hotrod-client.properties file. I feel like URI should be mutually exclusive with all of those configuration values that are standard for a remote cache manager (the store specific ones should stay). For example I can specify a URI that starts with hotrod: but also enable ssl in the remote store configuration, which would break the original URI.
Either way I think this needs some discussion or thought around it to make sure we know how these behave and what to expect. I personally think the RemoteStoreConfigurationBuilder in validate should only allow URI to be specified or the other properties.
There are also some other configuration options that don't make sense for a remote cache store such as near cache and force return values (the latter should always be true). But I am not sure if that is important enough to prevent a user from configuring.

Either way I think this needs some discussion or thought around it to make sure we know how these behave and what to expect. I personally think the RemoteStoreConfigurationBuilder in validate should only allow URI to be specified or the other properties.

Me and @durgeshanaokar discussed this on zulip. My feeling was that if you can define something in the URI in the client and then override it later, the same should also apply for the RemoteStore.
I think there is some merit in making it so that only the URI can be configured to stop users confusing themselves and us :smile: . @tristantarrant Any thoughts as the original implementor?

There are also some other configuration options that don't make sense for a remote cache store such as near cache and force return values (the latter should always be true). But I am not sure if that is important enough to prevent a user from configuring.

I think that's beyond the scope of this PR as it's already possible for users to configure these properties on RemoteStore.

Hey Will,
Thanks for the feedback, I will take care of it.
I agreed with the points that there could be more discussion required on
the JIRA.
Regards
Durgesh
On Wed, Apr 28, 2021 at 11:53 PM William Burns @.***>
wrote:

I think this is a good initial attempt. However, something doesn't feel
right to me. The URI can specify ssl, server list, user, pass and all the
properties that can be supplied in hotrod-client.properties file. I feel
like URI should be mutually exclusive with all of those configuration
values that are standard for a remote cache manager (the store specific
ones should stay). For example I can specify a URI that starts with
hotrod: but also enable ssl in the remote store configuration, which
would break the original URI.
Either way I think this needs some discussion or thought around it to make
sure we know how these behave and what to expect. I personally think the
RemoteStoreConfigurationBuilder in validate should only allow URI to be
specified or the other properties.
There are also some other configuration options that don't make sense for
a remote cache store such as near cache and force return values (the latter
should always be true). But I am not sure if that is important enough to
prevent a user from configuring.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/infinispan/infinispan/pull/9274#issuecomment-828678319,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEB4HAEQOX2VABD7YHMPUR3TLBHC7ANCNFSM43XC756A
.

--
Thanks and Regards
Durgesh Anaokar

I think there is some merit in making it so that only the URI can be configured to stop users confusing themselves and us smile . @tristantarrant Any thoughts as the original implementor?

People can really complicate their lives already:
hotrods://host:11222?use_ssl=false
so I wouldn't be too prescriptive. Generally, the URI should be the first element to be processed, with all other configs applied on top.

We may also need to let the user know that the URI would be like:
hotrods://<IP_ADDRESS>:19711,<IP_ADDRESS>:19811?use_ssl=false&tcp_no_delay=true&tcp_keep_alive=false&force_return_values=false

Otherwise will get parsing exception.

Either way I think this needs some discussion or thought around it to make sure we know how these behave and what to expect. I personally think the RemoteStoreConfigurationBuilder in validate should only allow URI to be specified or the other properties.

Me and @durgeshanaokar discussed this on zulip. My feeling was that if you can define something in the URI in the client and then override it later, the same should also apply for the RemoteStore.

You actually can't do that right now as the RemoteCacheManager only takes a URI related argument or a Configuration, but not both. There is technically a weird way you can by specifying a URI in the URI which seems like that shouldn't be possible personally, but we can disregard that one.

I think there is some merit in making it so that only the URI can be configured to stop users confusing themselves and us smile . @tristantarrant Any thoughts as the original implementor?

People can really complicate their lives already:
hotrods://host:11222?use_ssl=false
so I wouldn't be too prescriptive. Generally, the URI should be the first element to be processed, with all other configs applied on top.

So if we do that, which wins in the above code? Should ssl be enabled or not? The way the code is currently ssl would be disabled, but to me the URI protocol should be pretty explicit and not be overwritten.

You actually can't do that right now as the RemoteCacheManager only takes a URI related argument or a Configuration, but not both. There is technically a weird way you can by specifying a URI in the URI which seems like that shouldn't be possible personally, but we can disregard that one.

I was thinking that users can do it by using HotRodURI.create("hotrod://...").toConfigurationBuilder() and then passing the configuration to RCM, but that is in the impl package so I guess the users are on their own if they go down this route.


[docs]: Add a separate section to describe how to use shared mdx as components in other mdx files

What problem does this feature solve?
Add a separate section to describe how to use shared mdx as components in other mdx files.
like https://rspress.dev/guide/basic/use-mdx#use-component
What does the proposed API look like?

Add users should configure route.exclude too
https://github.com/web-infra-dev/rspress/blob/main/packages/document/rspress.config.ts#L42


Loading Icon

@Pseudo-64 Please confirm, is the icon only to be used when auto-saving, or can we use it when the game is loading a level as well?

@vitormaduro @Hhk187 Yes, this is the autosave icon to be used.


Detecting pages

We converted a WARC file to WACZ, and it did not detect any pages.  The url based UI is not as user friendly.
Is there any configuration we can provide to help it detect pages.  Or is there any post-processing we can do to identify the pages?

Hey there, without the WARC file or additional details about the command you ran it's a little tricky to nail down the problem.
Generally, the command I use to convert WARCs to WACZ files with a full text and URL index (searchable pages & page detection) is:
wacz create -f filename.warc -o filename.wacz -t --detect-pages

If you don't use --detect-pages they won't be detected, if you don't use -t the text index will not be generated, and also if you only use -t without --detect pages the text index won't be generated.
If the above is what you've done and it's still unsuccessful, there may be a bug to look into!  More details about your files would be appreciated so I can try to reproduce them!

The url based UI is not as user friendly.

I assume this is referring to ReplayWebpage?  If yes, this is something I'm working on right now! :)

Thank you for the response and the clarification.  --detect-pages helped.
Yes, we are using ReplayWebpage.


Don't run osgiBundle when it's not required.

Motivation:
osgibundle is so slow, I prefer to not run it if it's not needed.

@mdedetrich @Roiocam Trigger an JMH  bench you will notice it.

And my PC is using SSD too.

Trigger an JMH bench you will notice it.

Run JMH after clean up, it only costs 3s when executing stream osgiBundle

 Jmh/run -i 10 -wi 10 -f1 -t1 .*CollectBenchmark.*
Have no idea :(

@He-Pin This is probably why its not working on windows, same problem as before https://github.com/sbt/sbt-osgi/pull/100/files#diff-2530a9c505dd4cb34217eb195d5db3cab065049f033db306f485078da72edd5dR184
Making fix now


Job that is assigned to me does not appear in "my jobs"

<IP>/test_run/d9da8c48-b2cc-42cc-bdda-1d86daa4bf8e (scylla-master/longevity/longevity-mini-test-1h-test#2) was assigned to me but for some reason it does not appear in the "my jobs" page

@k0machi

The job was started back in December, and to be shown on "My jobs" page it has to be at most month old if it's not assigned to a schedule.

😳 Did not notice that


Missing a key step (which I found elsewhere)... appcenter login

one key step which is missing... is that in order to do a code push from the command line using the Dynamic Deployment Assignment, you first need to log into the appcenter. Should probably be mentioned prior to giving the command on how to deploy from command line. As a first attempt, following the getting started guide, it was a critical step. Cheers!

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

ID: 39490e39-be97-2bba-5afc-6bc8bed39690
Version Independent ID: 357a2070-e41c-b346-e18b-606eec7255c2
Content: Using the React Native SDK with CodePush - Visual Studio App Center
Content Source: docs/distribution/codepush/react-native.md
Service: vs-appcenter
GitHub Login: @Zakeelm
Microsoft Alias: zakeelm

@GitHubTracey Great suggestion, thanks. I've asked the product PM to consider a doc update.

@Zakeelm Can you take care of updating CodePush doc?

@GitHubTracey docs updated, thanks for pointing that out.

@GitHubTracey Hey, going to close this! I just added a few sentences to our docs to make this more clear.


Name spacing libraryTargets...

Do you want to request a feature or report a bug?
feature

What is the current behavior?
Custom named objects are not valid libraryTargets
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
Add custom named object as the export value for 'libraryTarget'
If this is a feature request, what is motivation or use case for changing the behavior?
In short, this would prevent name collision when multiple devs are authoring components across shared systems, which are dynamically loaded.
Specifically, I want to lazy load Vue single file components that are name spaced in a custom named object.
The resulting bundle would look something like,
var MyCustomObj[componentName] = webpack([0])....
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

Pass an array to library. This doesn't work with all libraryTargets so check documentation.


MMM-awesome-alexa "WARNING! electron-v6.1-linux-arm/snowboy.node"

Hello everyone!!
I spend lots of hours trying to solve this problem and i think i will need your help.
I Installed the Magic Mirror on my Raspberry Pi 4 and it´s working normal.
The problem is when I insert the Alexa module (MMM-awesome-alexa), and I start the Magic Mirror I only see a "Black Screen" with the cursor.
I try to see what kind of problem I receive on terminal it shows like this:

According this I try to see the file "snowboy.node" on /home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/snowboy/lib/node/binding/Release/electron-v6.1-linux-arm/snowboy.node , but I don´t have the folder "electron-v6.1-linux-arm".
I have   ..../Release/node-v64-linux-arm, and is nothing inside.
I see some one that had the same problem and recommend to use this command on the MMM-awesome-alexa directory:
npm run electron-rebuild
But I receive another error:

I appreciate the help of all of you.
Thanks fsdfsd

I tried to install the module again using this steps: https://awesome-alexa.js.org/#/installation
And i see that in this code :
npm install --only=prod

I receive some errors image below:

My problem is because of this errors installation?
Really appreciate some help on this

I tried to installing electron-rebuild
cd ~/MagicMirror/modules/MMM-awesome-alexa
npm install electron-rebuild
./node_modules/.bin/electron-rebuild

And now when i start MagicMirror i have the same "Black Screen" but the error is different:

I'm having pretty much the same issue. I have no idea how to go about fixing it.

@IsaacMartinez15
Maybe you made the same wrong thing like me, you should have to install Raspbian on your Raspberry (Raspbian Buster with desktop and recommended software) (https://www.raspberrypi.org/downloads/raspbian/). I had the Noobs and I get that problem. I do not instaled Alexa again but I think this will solve your problem.


patch the color book shadow

also fix a typo in marin splash. the book no longer has the ENTITY_PHYSICS_GRABBABLE and ENTITY_PHYSICS_SHADOW flags set.

My apologies- the entrance rando Wild check appears to have failed, though I don’t believe altering the book flags should have affected its generation. Is the seed it generated for the test a rare un-100%able seed?

Yeah, dont think that is caused by you, just random edge case it managed to hit.
This change might confuse some people as the shadow is the usual "this is a 1.0" rom check.
(Currently out camping, so will check&merge when back)


az appservice web deployment slot swap return

Hi,
I'm working with jenkins job with swap, and the return failed, is there anyway to get return code or like azure site swap to get output
az appservice web deployment slot swap --slot release -n test -g testrg --verbose
INFO: Starting long running operation    '<azure.cli.command_modules.appservice.custom.AppServiceLongRunningOperation object at 0x2420c50>'
ERROR: The response from long running operation does not contain a body.
Build step 'Execute shell' marked build as failure

@leitu , can you run with --debug and share the output? Webapp service might emit out errors not conforming to arm standard.

@leitu, i can reproduce now.
@annatisch, do you know why msrest runtime doesn't allow empty body when query for status? Node.js runtime allows it:
requests.packages.urllib3.connectionpool : Starting new HTTPS connection (1): management.azure.com
requests.packages.urllib3.connectionpool : "GET /subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/resourceGroups/yugangwlinux/providers/Microsoft.Web/sites/yugangwlinux-web3/operationresults/f65514b2-bcbd-40bb-91e1-6c562512c1af?api-version=2016-08-01&azureAsyncOperation=1 HTTP/1.1" 202 0
msrest.pipeline : Received status: 202 for method 'GET'
msrest.pipeline : Is forced retry: False
msrest.http_logger : Response status: 202
msrest.http_logger : Response headers:
msrest.http_logger :     'Content-Length': '0'
msrest.http_logger :     'Expires': '-1'
msrest.http_logger :     'X-AspNet-Version': '4.0.30319'
msrest.http_logger :     'x-ms-ratelimit-remaining-subscription-reads': '14998'
msrest.http_logger :     'X-Powered-By': 'ASP.NET'
msrest.http_logger :     'x-ms-request-id': '7b674878-09a5-415c-99e6-3a26b33f7cbe'
msrest.http_logger :     'Strict-Transport-Security': 'max-age=31536000; includeSubDomains'
msrest.http_logger :     'x-ms-correlation-request-id': '7b674878-09a5-415c-99e6-3a26b33f7cbe'
msrest.http_logger :     'Retry-After': '15'
msrest.http_logger :     'Location': 'https://management.azure.com/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/resourceGroups/yugangwlinux/providers/Microsoft.Web/sites/yugangwlinux-web3/operationresults/f65514b2-bcbd-40bb-91e1-6c562512c1af?api-version=2016-08-01'
msrest.http_logger :     'Pragma': 'no-cache'
msrest.http_logger :     'Cache-Control': 'no-cache'
msrest.http_logger :     'Date': 'Wed, 22 Mar 2017 17:28:09 GMT'
msrest.http_logger :     'Azure-AsyncOperation': 'https://management.azure.com/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/resourceGroups/yugangwlinux/providers/Microsoft.Web/sites/yugangwlinux-web3/operationresults/f65514b2-bcbd-40bb-91e1-6c562512c1af?api-version=2016-08-01&azureAsyncOperation=1'
msrest.http_logger :     'Server': 'Microsoft-IIS/8.0'
msrest.http_logger :     'x-ms-routing-request-id': 'WESTUS2:20170322T172810Z:7b674878-09a5-415c-99e6-3a26b33f7cbe'
msrest.http_logger : Response content:
msrest.http_logger :
msrest.exceptions : The response from long running operation does not contain a body.
The response from long running operation does not contain a body.

@yugangw-msft this code was refactored with msrestazure 0.4.7, should I assume this is this version?

@lmazuel , 0.4.7 is what i am using

In 0.4.7, I copied the algorithm from C#. I think it's accurate with what they do:
https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/src/ClientRuntime/Microsoft.Rest.ClientRuntime.Azure/AzureClientExtensions.cs#L496-L498
       private static async Task UpdateStateFromAzureAsyncOperationHeader<TBody, THeader>(
            IAzureClient client,
            PollingState<TBody, THeader> pollingState,
            Dictionary<string, List<string>> customHeaders,
            CancellationToken cancellationToken) where TBody : class where THeader : class
        {
            AzureOperationResponse<AzureAsyncOperation, object> asyncOperationResponse =
                await client.GetAsync<AzureAsyncOperation, object>(
                    pollingState.AzureAsyncOperationHeaderLink,
                    customHeaders,
                    cancellationToken).ConfigureAwait(false);

            if (asyncOperationResponse.Body == null || asyncOperationResponse.Body.Status == null)
            {
                throw new CloudException(Resources.NoBody);
            }

@leitu, please try again. Webapp service team notified they have rolled out a server side fix for this.
@lmazuel, thanks for the detail explanations.

thanka
On Sat, Mar 25, 2017 at 6:11 Yugang Wang<EMAIL_ADDRESS>wrote:

@leitu https://github.com/leitu, please try again. Webapp service team
notified they have rolled out a server side fix for this.
@lmazuel https://github.com/lmazuel, thanks for the detail explanations.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/2595#issuecomment-289143970,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACvAAs_ad3wcpA1H65e_9nyQ8qw6WAwIks5rpDGMgaJpZM4Mk0bU
.


[Bug]: Uses 90%+ of the CPU

Checklist

[X] I have read the appropriate section in the contributing guidelines
[X] I believe this issue is a problem with polybar itself and not a misconfiguration on my part
[X] I have searched for other open and closed issues that may have already reported this problem
[X] I have checked the known issues page for this problem.
[X] I have followed the debugging guide to narrow down the problem to a minimal config.

Steps to reproduce

Take the minimal config file provided.
Past it in ~/.config/polybar/config.ini.
Run: polybar main --reload &.

Minimal config
;  __  __           _       _
; |  \/  | ___   __| |_   _| | ___  ___
; | |\/| |/ _ \ / _` | | | | |/ _ \/ __|
; | |  | | (_) | (_| | |_| | |  __/\__ \
; |_|  |_|\___/ \__,_|\__,_|_|\___||___/

[module/blur]
type = custom/script
click-left = ~/.local/bin/polybar/blur check
exec = ~/.local/bin/polybar/blur
tail = true
interval = 0

[module/current-course]
type = custom/script
tail = true
exec = cat '/home/singularis/.local/share/current_course'

[module/bspwm]
type = internal/xworkspaces

label-active = %{F#9F728B}%name%%{F-}
label-active-underline = ${colors.primary}
label-active-padding = 1

label-occupied = %name%
label-occupied-padding = 1

label-urgent = %name%
label-urgent-background = ${colors.alert}
label-urgent-padding = 1

label-empty = %name%
; label-empty-foreground = ${colors.disabled}
label-empty-padding = 1

[module/cpu]
type = internal/cpu
interval = 2
format-prefix = " "
format-prefix-foreground = ${colors.foreground-alt}
format = <label>
format-foreground = ${colors.foreground}
label = %percentage%%

[module/date]
type = internal/date
interval = 1
format-prefix = ""
date = "%Y/%m/%d | "
date-alt = "%b %d %Y (%a) | "
time = %I:%M:%S
time-alt = %H:%M:%S
label = " %date%%time% "

[module/pulseaudio]
type = internal/pulseaudio

format-volume = <label-volume> <bar-volume>
label-volume = " %percentage%%"
label-volume-foreground = ${root.foreground}

label-muted = 🔇 muted
label-muted-foreground = #666

bar-volume-width = 10
bar-volume-foreground-0 = ${colors.foreground}
bar-volume-foreground-1 = ${colors.foreground}
bar-volume-foreground-2 = ${colors.foreground}
bar-volume-foreground-3 = ${colors.foreground}
bar-volume-foreground-4 = ${colors.foreground}
bar-volume-foreground-5 = ${colors.foreground}
bar-volume-foreground-6 = ${colors.foreground-alt}
bar-volume-gradient = false
bar-volume-indicator = |
bar-volume-indicator-font = 2
bar-volume-fill = ─
bar-volume-fill-font = 2
bar-volume-empty = ─
bar-volume-empty-font = 2
bar-volume-empty-foreground = ${colors.foreground-alt}

[module/battery]
type = internal/battery
battery = BAT0
adapter = ADP1
full-at = 98

format-charging = <animation-charging> <label-charging>
format-discharging = <ramp-capacity> <label-discharging>
label-full = %percentage%%

ramp-capacity-0 = 
ramp-capacity-0-foreground = ${colors.alert}
ramp-capacity-1 = 
ramp-capacity-1-foreground = ${colors.warning}
ramp-capacity-2 = 
ramp-capacity-3 = 
ramp-capacity-4 = 
ramp-capacity-foreground = ${colors.foreground-alt}

animation-charging-0 = 
animation-charging-1 = 
animation-charging-2 = 
animation-charging-3 = 
animation-charging-4 = 
animation-charging-foreground = ${colors.foreground-alt}
animation-charging-framerate = 750

[module/mpd]
type = internal/mpd
host = <IP_ADDRESS>
port = 6600
; Seconds to sleep between progressbar/song timer sync, Default: 1
interval = 2
format-online = <label-song>
format-online-prefix = " "
format-online-prefix-foreground = ${colors.foreground-alt}
label-song = %artist% - %title%
label-offline = mpd is offline
label-song-maxlen = 36

[settings]
screenchange-reload = true

[global/wm]
margin-top = 5
margin-bottom = 5

;  ____       _       _                   ____             __ _
; |  _ \ ___ | |_   _| |__   __ _ _ __   / ___|___  _ __  / _(_) __ _
; | |_) / _ \| | | | | '_ \ / _` | '__| | |   / _ \| '_ \| |_| |/ _` |
; |  __/ (_) | | |_| | |_) | (_| | |    | |__| (_) | | | |  _| | (_| |
; |_|   \___/|_|\__, |_.__/ \__,_|_|     \____\___/|_| |_|_| |_|\__, |
;               |___/                                           |___/

[colors]
background = ${xrdb:color0:#222}
background-alt = ${xrdb:color3:#222}
foreground = ${xrdb:color7:#222}
foreground-alt = ${xrdb:color2:#555}

color0 = ${xrdb:color0:#222}
color1 = ${xrdb:color1:#222}
color3 = ${xrdb:color3:#222}
color4 = ${xrdb:color4:#222}
color5 = ${xrdb:color5:#222}
color6 = ${xrdb:color6:#222}
color7 = ${xrdb:color7:#222}
color8 = ${xrdb:color8:#222}
color9 = ${xrdb:color9:#222}
color10 = ${xrdb:color10:#222}
color11 = ${xrdb:color11:#222}
color12 = ${xrdb:color12:#222}

urgent = #f00
primary = #9F728B
secondary = #9F728B
alert = #9F728B
active = {active}
inactive = {inactive}
error = #ff5555
highlight = ${xrdb:color2:#f00}

[bar/main]
background = ${xrdb:color0:#222}
background-alt = ${xrdb:color3:#222}
foreground = ${xrdb:color7:#222}
foreground-alt = ${xrdb:color2:#555}
highlight = ${xrdb:color2:#f00}

color0 = ${xrdb:color0:#222}
color1 = ${xrdb:color1:#222}
color3 = ${xrdb:color3:#222}
color4 = ${xrdb:color4:#222}
color5 = ${xrdb:color5:#222}
color6 = ${xrdb:color6:#222}
color7 = ${xrdb:color7:#222}
color8 = ${xrdb:color8:#222}
color9 = ${xrdb:color9:#222}
color10 = ${xrdb:color10:#222}
color11 = ${xrdb:color11:#222}
color12 = ${xrdb:color12:#222}

width = 100%
height = 35
radius = 9.0
fixed-center = false
wm-restack = bspwm

line-size = 1

border-left-size = 2.5
border-right-size = 2.5
border-top-size = 0
border-bottom-size = 0

padding-left = 0
padding-right = 0
padding-bottom = 0

module-margin-left = 2
module-margin-right = 2
module-margin-bottom = 0

font-0 = "DejavuSansMono:size=7.8;4"
font-1 = "FontAwesome:size=7.8;4"
font-2 = "FontAwesome:size=7.8;1"
font-3 = "FontAwesome:size=7.8;1"
font-4 = "FontAwesome:style=Regular:pixelsize=7.8;2"
font-5 = "Iosevka:style=Regular:pixelsize=7.8;2"
font-6 = "Source Code Pro:pixelsize=7.8;2"
font-7 = "Source Han Sans JP:style=Regular:pixelsize=7.8;2"
font-8 = "Siji:style=Regular:pixelsize=7.8;2"

modules-left = bspwm current-course
modules-right = blur mpd cpu battery pulseaudio date arrow

cursor-click = pointer
cursor-scroll = ns-resize

Polybar log
notice: Parsing config file: /home/singularis/.config/polybar/config.ini
notice: Loading module 'bspwm' of type 'internal/xworkspaces'
notice: Loading module 'current-course' of type 'custom/script'
notice: Loading module 'blur' of type 'custom/script'
notice: Loading module 'mpd' of type 'internal/mpd'
notice: Loading module 'cpu' of type 'internal/cpu'
notice: Loading module 'battery' of type 'internal/battery'
error: Invalid value for "module/battery.ramp-capacity-1-foreground", using default value (reason: The reference ${colors.warning} does not exist (no fallback set))
notice: Loading module 'pulseaudio' of type 'internal/pulseaudio'
notice: pulseaudio: using default sink alsa_output.pci-0000_00_1f.3.3.analog-stereo
notice: Loading module 'date' of type 'internal/date'
error: Disabling module "arrow" (reason: Missing section "module/arrow")
notice: Loaded 8 modules
notice: Loaded font "DejavuSansMono:size=7.8" (name=DejaVu Sans Mono, offset=4, file=/usr/share/fonts/TTF/DejaVuSansMono.ttf)
notice: Loaded font "FontAwesome:size=7.8" (name=FontAwesome, offset=4, file=/usr/share/fonts/awesome-terminal-fonts/fontawesome-regular.ttf)
notice: Loaded font "FontAwesome:size=7.8" (name=FontAwesome, offset=1, file=/usr/share/fonts/awesome-terminal-fonts/fontawesome-regular.ttf)
notice: Loaded font "FontAwesome:size=7.8" (name=FontAwesome, offset=1, file=/usr/share/fonts/awesome-terminal-fonts/fontawesome-regular.ttf)
notice: Loaded font "FontAwesome:style=Regular:pixelsize=7.8" (name=FontAwesome, offset=2, file=/usr/share/fonts/awesome-terminal-fonts/fontawesome-regular.ttf)
notice: Loaded font "Iosevka:style=Regular:pixelsize=7.8" (name=Iosevka, offset=2, file=/usr/share/fonts/TTF/iosevka-regular.ttc)
notice: Loaded font "Source Code Pro:pixelsize=7.8" (name=Source Code Pro, offset=2, file=/usr/share/fonts/adobe-source-code-pro/SourceCodePro-Regular.otf)
notice: Loaded font "Source Han Sans JP:style=Regular:pixelsize=7.8" (name=Source Han Sans JP, offset=2, file=/usr/share/fonts/adobe-source-han-sans/SourceHanSansJP-Regular.otf)
notice: Loaded font "Siji:style=Regular:pixelsize=7.8" (name=Noto Sans, offset=2, file=/usr/share/fonts/noto/NotoSans-Regular.ttf)

Expected behavior
I expect it to work fine without having it go all crazy and hogging up all the CPU.
Actual behavior
It keeps slowing my computer down to only 10 fps and my fans start going crazy when I don't even have anything open. Just polybar is launched.
Window Manager and Version
BSPWM 0.9.10
Linux Distribution
Arch Linux 6.1.21-1-lts
Polybar version
polybar 3.6.3

Features: +alsa +curl +i3 +mpd +network(libnl) +pulseaudio +xkeyboard

Additional Context / Screenshots
No response

Have you tried figuring out what module causes the load?
I see tail modules that run commands that are not actually "tailing", for example this one:
[module/current-course]
type = custom/script
tail = true
exec = cat '/home/singularis/.local/share/current_course'

even if I just run polybar with the bspwm and current-course modules, it still acts all crazy with the CPU hogging and stuff. It kinda works fine with only the bspwm module, but even then it still takes up about 20% of the CPU. Could this be a problem with my laptop on a hardware level or something I'm doing wrong on a software level?

even if I just run polybar with the bspwm and current-course modules, it still acts all crazy with the CPU hogging and stuff

Well, current-course definitely should not have tail = true. It takes ~15% CPU with this option on my machine too. How does it look without bspwm and current-course (and potentially blur) modules?
Also, you are using xworkspaces instead of an actual bspwm module. Is it intentional?

tail = true should only be used for long-running scripts, continuously producing output.
What's happening is that the cat command is executed all the time without any pause in between because the interval is 0 (implicitly for tail = true)


[FEAT] Implement approx_distinct

Motivation
Attempt to tick off some missing implementation from #1977 and #1980.
The motivation is to retrieve the unique list of values from an aggregated list, as opposed to count returned by approx_count_distinct.
Implementation
The API may not be piped correctly to meet the requirements of the linked issues.
This is my first time writing rust - i most likely have done something wrong. I'd appreciate any feedback.
Tests
Tests are included, replicated from approx_count_distinct.
I've included a new make target which would make it easier for developers to test the library in a different python environment.
When I use this to build a wheel and use the new function in a different python environment, approx_distinct behaves the same as approx_count_distinct even though the tests run as expected in the build environment. Halp pls!

Potential improvements:

Use a single DaftApproxDistinctAggable trait for both approx_count_distinct and approx_distinct since the implementation requires the same upstream datatype.
Re-useapprox_distinct in the approx_count_distinct call path to remove duplicate code
Not sure if there's a more efficient way to do this

I've attempted to improve performance, how do i re-trigger the codspeed benchmark?
Also I sadly don't know enough about rust to know what i'm doing wrong for the ubuntu builds

Took a quick look over the PR.
FWIW it seems to me that this is an implementation of distinct using a HashSet, and not an approx_distinct. Which is great because I believe distinct is the functionality that we want rather than approx_distinct.
We should clean up the implementation to remove references to sketches or approximation

I could use a little assistance in the most efficient way to resolve the None datatype inclusion.
Lastly, I don't know how to resolve the ubuntu build issues - any helpful pointers would be appreciated!

Lastly, I don't know how to resolve the ubuntu build issues - any helpful pointers would be appreciated!

@NellyWhads now that I think about it, it feels odd to me that this is being implemented as an aggregation. What we really want is an expression, e.g. list.value_counts
The difference here is that approx_count_distinct aggregates approximate counts potentially from different partitions into a group. But list.distinct operates on a per-row level.
I think most of your algorithm and tests can be reused, but we just need to rework the way they're integrated as an expression. If you look at src/daft-functions/src/list/value_counts.rs and see what we do with list.value_counts, this would be a good starting point.

Closing this PR in favor of #3494 as per the comments in this thread.


Support Python 3.10

Codecov Report

Merging #87 (3251e30) into master (c65c685) will increase coverage by 0.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #87      +/-   ##
==========================================
+ Coverage   83.68%   83.80%   +0.11%
==========================================
  Files           7        7
  Lines         141      142       +1
==========================================
+ Hits          118      119       +1
  Misses         23       23

Impacted Files
Coverage Δ

manage_fastapi/constants.py
80.76% <100.00%> (+0.76%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Bump glutin to 0.12

This removes a lot of duplicated dependencies

I don't see a reason to do this explicitly, as it is already a requirement for the #974 PR.

Right, didn't look at all open PRs before submitting, sorry ^^

No problem. :D


Specify DSTROOT and INSTALL_PATH for xcodebuild explicitly

Hey :)
It seems that some plugin projects do not set DSTROOT as $(HOME) and INSTALL_PATH as /Library/Application Support/Developer/Shared/Xcode/Plug-ins (for instance, CodePilot). Bundles therefore do not go where they should and installation fails.
I think it would be best to pass these settings to xcodebuild so we wouldn't need to rely upon anything. I also added install build action, it seems to be the proper way to trigger installation actions (setting permissions, copying products, etc.).

@nickynick thanks for your work, appreciate it!
As a consequence of fighting fights with xcodebuild over the past year, we'll move away from local building to binary distribution soon.
Because of that, I'll close this PR and reopen in case we don't roll out binary distribution in a timely manner.
Best


Fixing C compatiblity for GDNative NET module

Also add net interfaces to gdnative_api.json
Fixes GodotNativeTools/godot_headers#39

Thanks!


Unindent over-indented functions

For some reason (probably erroneous copy and paste) many functions in
qiita_db/util.py were indented too much. No changes were made here other than
to correct the indentation level of these functions.

few comments

Reviewed and no comments added on top of @wasade 's

Coverage remained the same at 79.07% when pulling 057b71738b0f7a670c777acdeaee239b3b8ebce5 on adamrp:unindent_util_code into d1ad2b536a68a0a53e0f02eea9703203a9afd62b on biocore:master.

Coverage decreased (-0.03%) to 79.04% when pulling 74e172e3a5b96c3a56e3510b28f52da8c7044ae5 on adamrp:unindent_util_code into d1ad2b536a68a0a53e0f02eea9703203a9afd62b on biocore:master.


standardized result document

@mr-tz  review and merge OR when i next go to dev i'll mark this as draft again and keep going from here.
i think we'll end up accumulating fairly large PRs if we wait each feature to be implemented (lots of stuff to fix along the way). thats why i'm ok with incremental PRs that are "better than before but not perfect".


Lazy import scipy.stats

This speeds up import time of the mlptrain package by 80ms on my machine (from 610ms to 530ms).
The rest of the import time comes from the autode package. There are some easy wins to make as well, such as not importing matplotlib.pyplot until needed.
EDIT: mlptrain uses an old autode v1.1, so perhaps things are different in the later versions.

For reference, I am analyzing import times with
python -Ximporttime -c "import mlptrain" 2> import.dat

You can inspect the resulting text file manually, or visualize it with tuna
pip install tuna
tuna import.dat


Markdown links don't render in footnotes

Markdown links don't appear to be rendering when they are placed in footnotes. When the example below is rendered, the link in the body appears as expected, but the one in the footnote appears as the markdown.
---
layout: distill
title: Example
description: Example
date: 2024-05-07
future: true
authors:
  - name: Anonymous
bibliography: 2024-05-07-distill-example.bib
toc:
  - name: Footnotes
---

## Footnotes

Just wrap the text you would like to show up in a footnote in a `<d-footnote>` tag.
The number of the footnote will be automatically generated.<d-footnote>This will become a hoverable footnote. [Test link](https://www.google.com/)</d-footnote>

***

[Lorem ipsum](https://www.google.com) dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Thanks for the report. As a temporary workaround, you should be able to use html on the foortnotes, that is, something like Lorem ipsum should work


Error with Euclides number comparing 2 faces

Hi there, I'm using the library from node js and it works quite good, but I have some errors comparing 2 faces. Usually it works good, but sometimes it does not recognise the same person, and sometimes returns that 2 different faces are the same...
My code looks like this:
import { Request, Response } from 'express';
import '@tensorflow/tfjs-node';
import * as faceapi from 'face-api.js';
import { loadImage, Canvas, Image, ImageData } from 'canvas';
import fetch from 'node-fetch';
import env from '../config/environment';

// @ts-ignore
faceapi.env.monkeyPatch({ Canvas, Image, ImageData, fetch });

const maxDescriptorDistance = Number(env.faceMaxdescriptor);

interface ResultType {
  message: string;
  data?: any;
  success: boolean;
  error?: string;
};

let loadedModels: boolean = false;
const loadFaceApiModels = async () => {
  return new Promise(async (resolve) => {
    if (!loadedModels) {
      await Promise.all([
        faceapi.nets.ssdMobilenetv1.loadFromUri(`${process.env.AWS_URL}/faceRecognitionModels`),
        faceapi.nets.faceLandmark68Net.loadFromUri(`${process.env.AWS_URL}/faceRecognitionModels`),
        faceapi.nets.faceRecognitionNet.loadFromUri(`${process.env.AWS_URL}/faceRecognitionModels`),
      ]);
      loadedModels = true;
      resolve();
    } else {
      resolve();
    }
  });
};

const detectFace = (image: any): any => faceapi.detectSingleFace(image).withFaceLandmarks().withFaceDescriptor();

export const checkFace = async (req: Request, res: Response): Promise<void> => {
  const {
    body: { image1, image2 },
  } = req;

  let result: ResultType = { success: false, message: req.t('faceRecognition.notMatch'), error: 'FACE_NOT_MATCH' };
  await loadFaceApiModels();
  try {
    const [canvasImage1, canvasImage2] = await Promise.all([ loadImage(image1), loadImage(image2) ]);
    if (canvasImage1 && canvasImage2) {
      const [detection1, detection2] = await Promise.all([ detectFace(canvasImage1), detectFace(canvasImage2) ]);

      if (detection1 && detection2) {
        const distance = faceapi.euclideanDistance(detection1.descriptor, detection2.descriptor);
        result.data = distance;
        if (distance <= maxDescriptorDistance) {
          result = {
            success: true,
            message: req.t('faceRecognition.success'),
            data: distance,
          }
        } else {
          result = { success: false, message: req.t('faceRecognition.notMatch'), error: 'FACE_NOT_MATCH', data: distance };
        }
      } else {
        result = { success: false, message: req.t('faceRecognition.cannotDetectFace', { image: !detection1 ? image1 : image2 }), error: 'FACE_NOT_DETECTED' };
      }
    } else {
      result = { success: false, message: req.t('faceRecognition.noImageError', { image: !canvasImage1 ? image1 : image2 }), error: 'NO_IMAGE' };
    }
  } catch (error) {
    result = { success: false, message: req.t('faceRecognition.error'), error: 'INTERNAL_ERROR', data: error };
  };

  res.status(200).send(result);
  return;
};

So this endpoint basically receive 2 images urls which are saved in a bucket in s3 (they are public)
Something like:
POST to endpoint/check

body: {
"image1": "S3_PATH_IMAGE_1",
"image2": "S3_PATH_IMAGE_1"
}

I'm using euclides number with value 0.6 as I saw in the documentation...
But for example with an image, if the right person is compared, it returns an euclides number 0.35541702332548575, and a different person is compared and it returns 0.5926215395658295 (also we are testing with male and female image)
Can I improve in someway the validations? I don't want to reduce euclides numbers, because in some cases the same person fails in the comparison with 0.62 or something similar, so if I reduce the number, it will fail multiple times.
Thanks in advance, and thanks because the library is really useful!

A threshold of 0.6 is optimal yes, I won't change it. The quality of the image and the size of the face in the image after cropping also affects the accuracy.
Can I improve in someway the validations?
One thing that can be done is to match a query image to 2 or more images of reference person X and then take the mean of the distances.