Standard interface of RNN units

Currently, several types of RNN units are implemented (stateful/stateless, LSTM/GRU). And we also have PRs that implement other kind of RNN units (SGU, DSGU (#1115), MGU (#1101), peephole (#1207) etc.).
It would be cumbersome if these RNN units had different APIs as we sometimes switch RNN units within the model without change the interfaces. So it is preferable for those RNN units to have standard interface that are common to them.

I think each RNN unit function f can be abstracted with four components. I assumes f is a Link object with parameter W (so called stateless XXX).

input: x
output: y
hidden state: h
parameters: W

Each unit f gets x and h, and it returns y and updated h: y, h' = f(x, h)
In some units, y is equivalent to h (such as GRU), or h contains y (such as LSTM).
When a user want to stack units, a second unit function gets output of a first unit function.
h1 = 0
h2 = 0
y1, h1' = f1(x, h1)
y2, h2' = f2(y1, h2)

A statefull unit s has an attribute h, and when __call__ is called, it updates its own hidden state.
def __call__(x):
    y, self.h = f(x, self.h)
    return y

For variable length inputs, we need return parts of hidden states as y. See https://github.com/pfnet/chainer/issues/1183
The interface of cuDNN's RNN helps you because it supports many types of RNNs in one API.

@unnonouno Thank you for your proposal. My vague idea was almost same as you. And also thank you for suggestion of cuDNN RNN's API. How do you think of the separation of Function and Link, as we did in LSTM?

Function is not mandatory. I mean, users can make RNN unit as a method with combination of existing Functions. I feel Link is enough though someone may need a method when they want to make parameter matrices from other functions. I don't have such a use case.

I agree with you because for example, GRU is difficult to isolate "function" part.


Implementation of Mean Perturbation Effect (mPE)

I'm planning to compute mPE on my images as it seems like this measure is no ref IQA. However, in repo, i see implementation of MS-SSIM and CW-SSIM. is there a script to compute overall mPE which seems to be combining above ones and degradation?

Sorry, mPE is actually to evaluate the perturbation effect relying on the original image, so it is not a no-ref IQA.


Add playmodes REPEAT_ONE and SHUFFLE_REPEAT_ONE

As of version 6.0, Sonos supports playmodes REAPEAT_ONE and SHUFFLE_REPEAT_ONE (http://www.sonos.com/software/release/6-0).
The commits add the new playmodes to soco/alarms.py, soco/core.py, and tests/test_core.py.

Hallo @quatauta
This looks good and fairly simple.
The Travis CI tests fail. It looks like a simple style issue about a line being too long. Can you fix that, then I will review and test and we can have it merged.
Regards Kenneth

Hello @KennethNielsen,
Thank you for pointing me to the too long line!
I fixed the too long line in bbe3569.
The Travis CI tests for python 2.6 pass now.
The tests for 2.7, 3.3, 3.4 and pypy still fail. It seems to me, they may fail not because of my changes. Unfortunately, I do not have enough experience with python to judge this.
Please tell If there is more I could/should update.
Regards, Daniel

Thanks for fixing the line.
Yes, the remaining failing tests is due to an updated version of pylint that runs on Travis CI. I have just fixed these in the master branch, so if you want, you can rebase your branch of master.
But if you don't fell up to that, we can also just merge it. I have already tested it, checked that it passes all tests and linting after rebasing.

I never did a rebase but I want to learn. I will give it a try on Saturday or Sunday.

Sounds good. I'd advice you to make an extra branch of the current state of playmode-repeat-one, so that you have something to fall back on if it fails. Other than that, it is not all that complicated. Let me know if you need any help.

I think rebasing was successful. The CI checks do pass.

Looks good. I'll merge it.
Can you please add a short comment to #332 that describes your enhancement and refers to this PR. I'll finally close the PR when we have the release note comment in place.
Thanks for your contribution :)


[BUG] - Disruptive "Waiting to Purchase" Alert

New issue checklist

[x] I have reviewed the README and documentation
[x] I have searched existing issues and this is not a duplicate

General information

Paywall version: 2.5.2
iOS version(s): 16.0.2
Xcode version: 14.0.1
Devices/Simulators affected: iPhone 12 Pro Max

Describe the bug
Upon making a purchase, the "Waiting to Purchase" modal appears just after a few seconds, claiming that the connection may be offline when in fact the purchase will still happen successfully. Network connection is strong at 186 Mbps. In fact it happens just as soon as the payment sheet is presented (the user hasn't confirmed with Apple that they would like to subscribe yet).
Steps to reproduce

Trigger a paywall
Purchase a product/or restore purchases
Wait a few seconds and an alert controller as shown in the image below will appear.

Hi @michaeljajou, thanks for the bug report. This is a known issue with users who are using StoreKit 2. Can you confirm whether this is the case? We don’t officially support StoreKit 2 yet but are working on improving this in the 3.0 release. If you’re using revenuecat you can specifically set it to use StoreKit 1.

Ah thank you for the quick response! Sounds good, I believe I am using StoreKit 2. Are there any downsides to switching down to StoreKit 1?

I am using RevenueCat, where can I find how to make that switch?

If you're handling storekit yourself then it's just a lot easier but with StoreKit 2, but I don't believe there are any disadvantages when using RevenueCat. You can do it like this when configuring Purchases:
Purchases.configure(
  with: .init(withAPIKey: configuration.environment.revenueCatApiKey)
    .with(usesStoreKit2IfAvailable: false)
)

Thank you, works great!

Great! Closing this issue now. Thanks!


scale figsize in plot_events depending on n unique events

xref #12835

@larsoner what do you think of this "low hanging fruit" improvement?
Using this MWE (if you checkout and install my branch here), this scales well to a number of 40 unique events. It looks a bit small in this PR preview, but on my screen it looks fine. Beyond scaling factor 2, it all gets wonky.
# %%
import numpy as np
import mne

events = np.arange(300).reshape(-1, 3)

if 1:
    for i in range(10, 100, 10):
        fig = mne.viz.plot_events(events[:i, :], show=True)
        figsize = fig.get_size_inches()
        print(f"previous was: n events: {i}, Figure size: {figsize}")

# Looks good up to 40 unique events
report = mne.Report("try")
report.add_events(events[:40, :], title="events", sfreq=100)
report.save("try.html", overwrite=True)

20 unique events (no changes compared to main ... and any fewer events will also produce same size fig)

30 unique events (slightly bigger figure, no events cut off)

40 unique events (max scaling, no events cut off)

60 unique events (same scaling as for 40, now some events cut off)

Looks good!
Maybe another easy improvement would be to only create the legend for the first [:40] handles and labels? That way we cut off the legend ourselves. Could even use the first [:40] handles and labels[:39] + ["..."] in cases where there are more than 40 to make it clear we've truncated?

Maybe another easy improvement would be to only create the legend for the first [:40] handles and labels?

@larsoner with https://github.com/mne-tools/mne-python/pull/12844/commits/dac65e44d8a1c2611485570af0e2ea4a018bc49f I opted instead to "magically" spread the legend over more columns.
This fixes the layout also for plots that contain really high amounts of different events, see for example the previous case of 60 unique events:
import numpy as np
import mne

events = np.arange(300).reshape(-1, 3)
n = 60
event_id = {f"very long string indeed even longer {i}": j for i, j in enumerate(events[:n, -1])}
fig = mne.viz.plot_events(events[:n, :], event_id=event_id, show=True)

With respect to the mne.Report, the changes here will also make it work "out of the box" for more cases than before, but will still lead to problems for some edge cases like:

even more unique events (so the additional figure scaling is still not enough)
very long event_id keys (so spreading over legend columns would lead to cutoffs in the horizontal again)

But all in all, I think this is about as much magic as we should introduce:

it fixes a good amount of cases
it does not introduce new problems (in that: people getting their plots cut off, would also have had them cut off with the previous code)
remaining issues should be approached with proper PRs, like dealing with html, as you suggested in #12835

Ready for merge from my side :-)

@larsoner I had one more idea on how to make the overview better when many events are supplied (and not worse when only few are supplied), see: https://github.com/mne-tools/mne-python/pull/12844/commits/b499f7b47e3c19c8610087fcf31a0bacb9d48c0f
When there are many events, the visual mapping between a dot on the canvas and the event_id becomes impossible. therefore a "duplicating" (strictly speaking) mapping in the legend would lead to a better correspondence, see examples:
Instead of having the count n just as some event id string (n) or N=n when event_id=None, it is now:

some event id string (id=1234; N=n)
id=1234; N=n

Beautiful!
How about touching some events tutorials/examples and the report tutorial just so we can see CircleCI render them, then marking for ready assuming they look good?
If you really want to venture into bonus territory you could open a PR to MNE-BIDS-Pipeline that makes CircleCI there install MNE-Python using your sappelhoff:events branch rather than upstream/main and we could inspect the reports there. But if not then we can merge this assuming MNE-Python's tutorials look good and I can bother you later if I see problems in MNE-BIDS-Pipeline :slightly_smiling_face:

Thanks for the feedback, I will go to the bonus territory as soon as I find a chunk of time!

Examples for mne website
unfortunately, all of them are clipped now 🥲

before, after
before, after
before, after
before, after
before, after
before, after

Examples from mne-bids-pipeline

ERP CORE P3 before

ERP CORE P3 after

mobi gait before

mobi gait after

As mentioned above, some plots are not affected at all (apart from more info about id and N in legend).

faces data before

faces data after

attentional blink before

attentional blink after

And some previously existing problems are not touched / solved at all (here: clipping the legend due to long event_id keys).

matching pennies before

matching pennies after

@larsoner the long texts in the legend are problematic.
For most cases, this could be fixed with text wrapping: https://stackoverflow.com/a/47058132/5201771
Do you think that is something worth trying? any other ideas?

Updated after https://github.com/mne-tools/mne-python/pull/12844/commits/0be3f9a0caf47b0c3b6eb61a19d64cc8b6e435fa
from mne docs

before, after 0be3f9a0
before, after 0be3f9a0
before, after 0be3f9a0
before, after 0be3f9a0
before, after 0be3f9a0
before, after 0be3f9a0

from mne-bids-pipeline

ERP CORE P3 before

ERP CORE P3 after 0be3f9a0

mobi gait before

mobi gait after 0be3f9a0

faces data before

faces data after 0be3f9a0

attentional blink before

attentional blink after 0be3f9a0

matching pennies before

matching pennies after 0be3f9a0

☝ https://github.com/mne-tools/mne-python/pull/12844/commits/0be3f9a0caf47b0c3b6eb61a19d64cc8b6e435fa clearly overshot with the fontsize="x-small" setting.
However, I have tested many more cases locally and found a few extra adjustments that we can try. See: https://github.com/mne-tools/mne-python/pull/12844/commits/754a8a4c45b59ab79bea503d4fbe0c08fec917e6
For me this works quite well locally (on my personal examples), and also looks good when running the examples.
Let's see how it looks online.

Yes I think overall the wrapping is an improvement. I don't think we can aim at perfection and what you have now is already an improvement in almost all cases so I think we can merge once you have another look through the examples. No need to link them all again since you've already linked plenty above -- I'm happy to trust your eyes for the last run(s), so you can just look and say "yes they look better" to save yourself some time :slightly_smiling_face:
And at the end of the day if people have event ids that are super long they should probably consider renaming them with abbreviations in the event_id they pass in to plot_events or something like that. So I'm okay with those looking a little wacky. You could document this option/idea, though, if it's not in there. Or we can add it later once we check that it actually works.

I don't think we can aim at perfection and what you have now is already an improvement in almost all cases

Thanks! I was starting to go mad :-)
A little improvement was everything I was aiming for in the first place. Seemingly low hanging fruit 😉
I will report back when the circleci renderings for mne and mne-bids-pipeline are out and I am happy.

@larsoner I checked all outputs again, and (if you ask me) we have an improvement for every example I looked at now. Ready for merge from my side!

Failure is unrelated, thanks @sappelhoff !


Remove empty query string.

Describe the bug
How do I get an empty query string off the URL?
Reproduction
Add with data then try to remove.
Logs
No response

You can set the empty string as default value and use showDefaults: false

Strange, that is what I'm doing.  I saw that suggestion in another issue.  Once I select and then deselect, it still ends up with ?filter_category=
	const selected = queryParam(`filter_${section.id}`,ssp.string(''),{
		showDefaults: false
	});

<input
	id={`filter-${section.id}-${optionIdx}`}
	value="{option.value}"
	type="checkbox"
	bind:group={$selected}
	class="h-4 w-4 rounded border-gray-300 text-blue-600 focus:ring-blue-500"
/>

Any thoughts?  Awesome script, by the way.

I don't think you can use a string to bind to a checkbox group...if you prepare a reproduction I can try to take a look

It seems similar to issue #72, at first the defaults don't show in the URL, but upon setting them and reverting them, they stay in the URL.
<script lang="ts">

    import { queryParam, queryParameters, ssp } from 'sveltekit-search-params';

    const test = queryParam('search', ssp.string(''), { debounceHistory: 500, showDefaults: false});

</script>

<input type="text" bind:value={$test}>

Before:

After typing something:

After deleting it:


Spelling errors in comments and documentation

🐞 Problem
There are a lot of spelling errors in the comments and docstrings. One may also find some in the documentation, if you dig a bit deeper.
🎯 Goal
Well obviously, they pinch my eyes. So they need to be corrected.
For a start, there are a few spelling errors in /tests/test_utils/test_kerrnewman_utils.py

💡 Possible solutions
This is mostly to get people around the codebase. So explore and correct. 😄

📋  Steps to solve the problem

Comment below about what you've started working on.
Add, commit, push your changes
Submit a pull request and add this in comments - Addresses #<put issue number here>
Ask for a review in comments section of pull request
Celebrate your contribution to this project 🎉

Specifically, an instance of this can be seen in docs/source/metric.rst. Some subtle but understandable errors are there.

I will be working on this issue. Please review the changes I have done in PR #202.

@abhijeetmanhas  A friendly suggestion from my side is, you always ask if you can work on the issue and not directly tell. :)


Consider getting rid of draft_text filter

Could we use the same |richtext as Wagtail instead? Abuse / extend its existing behavior or override it? Is this possible / recommandable?

So cool!


Ability to have custom time bar svg

Hello Team,
is there Ability to customize the timeline head with separate svg icon?

Does this example meet the needs? Any content can be defined on the left side of the timeline and synchronized with the timeline scrolling.
I think it may not be very appropriate to define operable icons in the row because it will follow the horizontal scrolling.

hey, i think you provided the Localhost url 8080.. which I cannot view the example. Please see what your example URL.
Also the ask is,  see the image. it should have the timeline head as rounded icon customizable.

Sorry, i just updated the example link below. Add do you mean to customize the style here?

Yes, thats right. Want to customize the head of the scrubber bar


Add Gitpod integration for quick dev environment in cloud

Describe the changes you have made in this pr -
Add gitpod integration to enable development in cloud and quick code and functional review
Screenshots of the changes (If any) -

Test url https://gitpod.io/#https://github.com/tachyons/CircuitVerse

Very Interesting!


JSON missing from lib directory in 1.0.0

I'm working on upgrading something to use 1.0.0, and am running into this error:
Error: Failed to load plugin jsx-a11y: Cannot find module '../util/attributes/ARIA'

I believe this is because the build step doesn't bring the JSON files over to the lib directory from src.

ah fixing now. you're right. just manually doing a cp command for that now. hmm why can't babel handle that?

Should be fixed in v1.0.1

Thanks for the fast fix! FYI https://github.com/airbnb/javascript/pull/838


Error when running fs-bq-import-collection. PartialFailureError

[REQUIRED] Step 2: Describe your configuration

Extension name: ** fs-bq-import-collection **
Extension version: ** N/A **
Configuration values (redact info where appropriate):

** project: pats-production **
** collection: oilworx-customers **
** dataset: firestore_export **
** table_prefix: oilworx_customers **

[REQUIRED] Step 3: Describe the problem
When running npx @firebaseextensions/fs-bq-import-collection i get an error and no rows are imported. I tried with several collections and projects and none of them is working. This script worked for me a week ago.
Steps to reproduce:
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
Importing data from Cloud Firestore Collection: oilworx-customers, to BigQuery Dataset: firestore_export, Table: oilworx_customers_raw_changelog
BigQuery dataset already exists: firestore_export
BigQuery table with name oilworx_customers_raw_changelog already exists in dataset firestore_export!
View with id oilworx_customers_raw_latest already exists in dataset firestore_export.
Inserting 100 row(s) of data into BigQuery
Error importing Collection to BigQuery: PartialFailureError

Expected result
Documents imported to bigquery
Actual result
No documents were imported to bigquery

I have the exact same error. And it also worked for me some weeks ago.

I was having the same problem.
This is related to
The version of the bigquery "@google-cloud/bigquery": "^2.1.0", is a really old one. I had a newer version, I was having problem with this file firestore-bigquery-change-tracker/src/bigquery/index.ts. In particular, the way they ser calling the insert(payload, options) It seems that now is insert(rows).
Try to reinstall the dependencies, and retry.

Unfortunately this is not solving the issue for me. I reinstalled the dependencies but still get the same error.

i was able to import rows updating bigquery lib to "@google-cloud/bigquery": "^4.7.0", and changing the insert method to do :
await table.insert(rows, options); where options are
const options = {
      skipInvalidRows: false,
      ignoreUnkownValues: false,
      raw: true
    } as InsertRowsOptions;

also created a PR to address this issue, @IanWyszynski can you look at it and let me know if  it looks good to you? thanks!

Hi @joaqcid
You seem to have solved this, but I wasn't able to replicate what you did.   I cloned the repo and updated the dependecy to 4.7, but that didn't seem to help when I ran it again.

I made the changes suggested in the PR to the index.js file (not using Typescript) and I updated the dependency to 4.7 but I'm still getting the error.

hi all,
i creted a branch "run-manual-import" on my fork for to run it manually, https://github.com/joaqcid/extensions
from there, you need to

npm install in firestore-bigquery-change-tracker folder (dont mind the errors)
npm install in scripts/import folder
npm run import

hope this helps

@joaqcid Do I want to use the fix-bq-import fork or the run-manual-import fork?

run-manual-import

@joaqcid.   Thanks a heap, worked a treat...

Hi @joaqcid, thanks for posting this!! Unfortunately I just followed the instructions exactly and came out with the same error. Here's the full log output:
0 info it worked if it ends with ok 1 verbose cli [ '/Users/markflegg/.nvm/versions/node/v10.18.1/bin/node', 1 verbose cli   '/Users/markflegg/.nvm/versions/node/v10.18.1/bin/npm', 1 verbose cli   'run', 1 verbose cli   'import' ] 2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'preimport', 'import', 'postimport' ] 5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true 8 verbose lifecycle<EMAIL_ADDRESS>PATH: /Users/markflegg/.nvm/versions/node/v10.18.1/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/markflegg/programming/shadda/extensions/firestore-bigquery-export/scripts/import/node_modules/.bin:/Users/markflegg/programming/google-cloud-sdk/bin:/Users/markflegg/.nvm/versions/node/v10.18.1/bin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/markflegg/programming/flutter/bin 9 verbose lifecycle<EMAIL_ADDRESS>CWD: /Users/markflegg/programming/shadda/extensions/firestore-bigquery-export/scripts/import 10 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node ./lib/index.js' ] 11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null 12 info lifecycle<EMAIL_ADDRESS>Failed to exec import script 13 verbose stack Error<EMAIL_ADDRESS>import:node ./lib/index.js13 verbose stack Exit status 1 13 verbose stack     at EventEmitter.<anonymous> (/Users/markflegg/.nvm/versions/node/v10.18.1/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16) 13 verbose stack     at EventEmitter.emit (events.js:198:13) 13 verbose stack     at ChildProcess.<anonymous> (/Users/markflegg/.nvm/versions/node/v10.18.1/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack     at ChildProcess.emit (events.js:198:13) 13 verbose stack     at maybeClose (internal/child_process.js:982:16) 13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) 14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd /Users/markflegg/programming/shadda/extensions/firestore-bigquery-export/scripts/import 16 verbose Darwin 19.3.0 17 verbose argv "/Users/markflegg/.nvm/versions/node/v10.18.1/bin/node" "/Users/markflegg/.nvm/versions/node/v10.18.1/bin/npm" "run" "import" 18 verbose node v10.18.1 19 verbose npm  v6.13.4 20 error code ELIFECYCLE 21 error errno 1 22 error<EMAIL_ADDRESS>import:node ./lib/index.js22 error Exit status 1 23 error Failed at the<EMAIL_ADDRESS>import script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]
Thanks for any help you can give!!
-mf

i creted a branch "run-manual-import" on my fork for to run it manually, https://github.com/joaqcid/extensions
from there, you need to

npm install in firestore-bigquery-change-tracker folder (dont mind the errors)
npm install in scripts/import folder
npm run import

hope this helps

@tptshoe i cant understand the error in the logs, try clearing all node_modules folders from the firebase/extensions and re-run npm install only under
/firestore-bigquery-export/firestore-bigquery-change-tracker
/firestore-bigquery-export/scripts/import
then run npm import under
/firestore-bigquery-export/scripts/import

@joaqcid  i tried your solution

getting this error  , it will be great if you can look into this

hi @madhudvs are you using the branch from my fork? looking at the logs it seems like you are using a different versio

Hi @jacquetd  am cloning from https://github.com/joaqcid/extensions
and did these steps
npm install in firestore-bigquery-change-tracker
npm install in scripts/import folder
npm run import in import

@joaqcid I see the same error as @madhudvs, maybe you can go in a bit more detail on how to follow your fix. Thank you in advance :)

@joaqcid thx a lot, this fix saved my day. by following those steps it worked with my firebase projects.

are you executing steps on branch "run-manual-import" @cedgen @madhudvs ?

@joaqcid  @cedgen    the specific branch "run-manual-import" @ https://github.com/joaqcid/extensions fixed the issue ,  now i am able to import

@joaqcid  yes, I downloaded the files on the branch "run-manual-import" and than did the steps but its still not working

MacBook-Pro:import User$ npm run import

<EMAIL_ADDRESS>import /Users/user/node_modules/extensions-run-manual-import/firestore-bigquery-export/scripts/import
node ./lib/scripts/import/src/index.js

internal/modules/cjs/loader.js:796
throw err;
^
Error: Cannot find module '/Users/user/node_modules/extensions-run-manual-import/firestore-bigquery-export/scripts/import/lib/scripts/import/src/index.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:793:17)
at Function.Module._load (internal/modules/cjs/loader.js:686:27)
at Function.Module.runMain (internal/modules/cjs/loader.js:1043:10)
at internal/main/run_main_module.js:17:11 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>import: node ./lib/scripts/import/src/index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>import script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/user/.npm/_logs/2020-02-14T10_34_01_803Z-debug.log

@cedgen looks like it didn't compile scripts/import, and not finding the code to run. do you get any errors when you run npm install under scripts/import?

@joaqcid this was a big help!!!!
git clone git@github.com:joaqcid/extensions.git
cd extensions
git checkout run-manual-import
cd firestore-bigquery-export/firestore-bigquery-change-tracker
npm i
cd ../scripts/import
npm i
npm run import

@joaqcid no errors when doing npm install at scripts/import, but still get this error:
13 verbose stack Error<EMAIL_ADDRESS>import: node ./lib/index.js13 verbose stack Exit status 1 13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16) 13 verbose stack     at EventEmitter.emit (events.js:223:5) 13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack     at ChildProcess.emit (events.js:223:5) 13 verbose stack     at maybeClose (internal/child_process.js:1021:16) 13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) 14 verbose pkgid<EMAIL_ADDRESS>

sorry @cedgen cant tell from the logs, what the problem might be, would recommend to start from a clean folder and see if that fixes it for you.
btw im running on node v10.17.0

@sourcec0de ,
got compilation errors during install:
$ npm i

><EMAIL_ADDRESS>prepare /home/astar/dev/extensions/firestore-bigquery-export/firestore-bigquery-change-tracker
> npm run build

><EMAIL_ADDRESS>build /home/astar/dev/extensions/firestore-bigquery-export/firestore-bigquery-change-tracker
> npm run clean && npm run compile

><EMAIL_ADDRESS>clean /home/astar/dev/extensions/firestore-bigquery-export/firestore-bigquery-change-tracker
> rimraf functions/lib

><EMAIL_ADDRESS>compile /home/astar/dev/extensions/firestore-bigquery-export/firestore-bigquery-change-tracker
> tsc

src/test/bigquery/snapshot.spec.ts:47:1 - error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i @types/jest` or `npm i @types/mocha`.

47 describe("latest snapshot view sql generation", () => {
   ~~~~~~~~

src/test/bigquery/snapshot.spec.ts:48:3 - error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i @types/jest` or `npm i @types/mocha`.

48   it("should generate the epxected sql", async () => {
     ~~

src/test/bigquery/snapshot.spec.ts:60:3 - error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i @types/jest` or `npm i @types/mocha`.

60   it("should generate correct sql with no groupBy columns", async () => {
     ~~

src/test/bigquery/snapshot.spec.ts:72:3 - error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i @types/jest` or `npm i @types/mocha`.

72   it("should throw an error for empty group by columns", async () => {
     ~~

src/test/bigquery/snapshot.spec.ts:79:3 - error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i @types/jest` or `npm i @types/mocha`.

79   it("should throw an error for empty timestamp field", async () => {
     ~~

Found 5 errors.

Also having this issue after node installs. Can anyone from the Firebase team merge this in?

A fix has been merged in #197

How to use this fix? npx @firebaseextensions/fs-bq-import-collection

I'm still not able to use npx @firebaseextensions/fs-bq-import-collection. The fork worked (but required editing to use collectionGroup for the query.

Hi, the package has been updated on NPM, sorry for the delay!


fix: [M3-7586] - Fix Textfield Label Tooltip Icon

Description 📝
This fixes an issue where the tooltip icons appeared elongated/distorted on focus.
Changes  🔄

Evened out padding around the button and moved some styling to parent containers

Preview 📷
Include a screenshot or screen recording of the change

Before
After

How to test 🧪
Reproduction steps

Turn on AGLB feature flag and go to http://localhost:3000/loadbalancers/0/service-targets (This bug is not AGLB specific, but this was just a good drawer to test)
Alternatively, you can look at the storybook: http://localhost:6006/?path=/story/components-textfield--with-tooltip

Verification steps

Tab through drawer and observe fixes

Check all that apply

[ ] 👀 Doing a self review
[ ] ❔ Our contribution guidelines
[ ] 🤏 Splitting feature into small PRs
[ ] ➕ Adding a changeset
[ ] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[ ] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

You can confirm this in the storybook too.


Improve Error to NSError conversion

Error->NSError conversion in Darwin Foundation fills domain and code even if provided Error does not conform to CustomNSError. This patch brings same behavior to swift-corelibs-foundation.

@swift-ci please test

@MaxDesiatov Could you please retrigger CI? I squashed commits into one.

@swift-ci please test

The only reason we didn't go deep on the first attempt was that we didn't have a lot of infrastructure set up yet and much was deferred to when we'd have good stories for conversion, for localization, etc., which now we do. More compatibility is always a good thing. LGTM


Updated secrets, now removing previous tests failed messages also.

Tests passed - https://drive.google.com/uc?id=1hfRIt8sNzaCiXX7_s-8ZyjdT3TF8X4Ga&export=download


[state_synchronizer] test_peer_manager is flaky

The state_synchronizer unit test test_peer_manager is flaky and need to be either disabled or fixed to be deterministic and no longer flaky.
Some instances of this flakiness:
https://github.com/libra/libra/pull/1007#issuecomment-533659479
https://circleci.com/gh/libra/libra/7309#tests/containers/2

Thanks for reporting, will get it fixed

Resolved


[cloud_functions] HttpsCallable.call throws PlatformException instead of CloudFunctionsException

Describe the bug
When calling .call trying to get an error (i.e. with wrong parameters, wrong function name or wrong region) I'm getting a PlatformException instead of a CloudFunctionsException
To Reproduce
This is the function that actually call .call
Future<num> _simpleFunction(String param1, String param2) async {
    final HttpsCallable _simpleFunction =
        CloudFunctions(region: "europe-west1")
            .getHttpsCallable(functionName: 'simpleFunction');

    try {
      final HttpsCallableResult response = await _addUserRemainder
          .call(<String, dynamic>{'param1': param1, 'param2': param2});

      return response.data['result'];
    } on CloudFunctionsException catch (e) {
      print('catched $e');
      rethrow;
    }
}

And this is where I call _simpleFunction
try {
        num balance;
          balance =
              await _simpleFunction('param', 'param2');
        }
      } catch (error) {
        print('Main block $error');
      }

And I always get:
I/flutter (10343): Main block PlatformException(functionsError, Cloud function failed with exception., {code: INVALID_ARGUMENT, details: null, message: Invalid QR code})
Expected behavior
Reading the implementation of .call function, it should always return a CloudFunctionsException instead.
Additional context
cloud_functions version is 0.4.2
Till the version 0.4.1+6 was working fine.

Any update on this? I'm having the same issue.
I read this  stack overflow question and it says that the cloud functions api can only throw HttpsError with certain codes, that flutter can't catch because there isn't a "functionsError" code. I can't change the implementation of the Cloud Function to throw a generic error with "functionsError" code. I need help

Is there info if this is going to be fixed? I have the same issue

the same here

I fixed it at this issue https://github.com/FirebaseExtended/flutterfire/pull/2556 but anyone reviewed it.

5 months and the bug stay :/

6 months and the bug stay, this behavaviour break all my tests. Waiting for https://github.com/FirebaseExtended/flutterfire/pull/2556 pull request being aproved @Salakar

Same error here!!

@TahaTesser Could I kindly ping you? This is issue is quite problematic and there's a ready PR (two, actually). The only thing this issue needs is a little bit of :heart:

@cubuspl42
Thanks for the info, will let the team know

cloud_functions are now in the version 0.7.0+1 and the bug still remains. The fix are in the roadmap?

Any updates on this ? Happy to help if PR review is needed :)

Any updates on this ? Happy to help if PR review is needed :)

It is working for me but using FirebaseFunctionsException not CloudFunctionsException
Future<T> _call<T>(String name, Map params) async {
    print('StripeService._call, $name, $params');
    final HttpsCallable callable = _cf.httpsCallable(name);
    try {
      final result = await callable.call(params);
      print(result.data);
      return result.data;
    } on FirebaseFunctionsException catch (e) {
      print('caught firebase functions exception');
      print(e.code);
      print(e.message);
      print(e.details);
      if (e.details == null) {
        throw "Unknown error occurred";
      }
      print(e.details["message"]);
      if (e.details["code"] == "some_code") {
        throw "Some Error";
      }
      throw e.details["message"];
    } on PlatformException catch (e) {
      print(e.message);
      print(e.details);
      final cloudException = e.details;
      throw cloudException["message"];
    } catch (e) {
      print(e);
      throw "Unknown error";
    }
  }

It is working for me but using FirebaseFunctionsException not CloudFunctionsException
Future<T> _call<T>(String name, Map params) async {
    print('StripeService._call, $name, $params');
    final HttpsCallable callable = _cf.httpsCallable(name);
    try {
      final result = await callable.call(params);
      print(result.data);
      return result.data;
    } on FirebaseFunctionsException catch (e) {
      print('caught firebase functions exception');
      print(e.code);
      print(e.message);
      print(e.details);
      if (e.details == null) {
        throw "Unknown error occurred";
      }
      print(e.details["message"]);
      if (e.details["code"] == "some_code") {
        throw "Some Error";
      }
      throw e.details["message"];
    } on PlatformException catch (e) {
      print(e.message);
      print(e.details);
      final cloudException = e.details;
      throw cloudException["message"];
    } catch (e) {
      print(e);
      throw "Unknown error";
    }
  }

AFAIK, it's fixed in upstream.

AFAIK, it's fixed in upstream.

Waiting for a official update, for now I'm using a fork reposity. But this fix breaks my CI, because some SO have limit for path too long and when you use a git reference sometimes happen

Waiting for a official update, for now I'm using a fork reposity. But this fix breaks my CI, because some SO have limit for path too long and when you use a git reference sometimes happen

This has been fixed a while back, please try the latest release, thanks.


Adjustments for Gentoo Linux

The init script for Gentoo Linux needed adjustment after Gentoo made
some developments.  Additionally, the ebuild script for Gentoo Linux was
removed at some point, but it is rather helpful for anyone running
Gentoo Linux.

Nice !!


Handle token failures

(note this also includes PR #488 - will tidy up after that one is merged)
This fixes #484

@megakid please update when you have some time and I'll try to review and merge!

@megakid please update when you have some time and I'll try to review and merge!

All done - thanks @Flydiverny


LLVM 6.0.1 entry not found

When I try:
$ llvmenv build-entry 6.0.1
Error: ErrorMessage { msg: "Entry does not found: 6.0.1" }

But the download is available: http://releases.llvm.org/6.0.1/llvm-6.0.1.src.tar.xz
6.0.0 does find its URL. Version is 0.1.8, and rustc is 1.27.1 & 1.29.0

I've released 0.1.9. Please re-open if not fixed


Add Visual Studio support for the C++ library and application plugins

Change the visual-studio plugin to understand the cpp-application or cpp-library models.

Initial support: https://github.com/gradle/gradle/pull/4411

We still need to tackle composite build support, but this should be covered by #249.


OneDrive for business - create file fails(UnauthorizedAccessException) for AppOnly accessToken

Hi,
I got the Access token by using following method.
https://developer.microsoft.com/en-us/graph/docs/concepts/auth_v2_service
By calling the Microsoft Graph API, I can list up files of every user in tenant, download them, and even can create a folder.
but I can not create file, the response is
"{"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":"Access denied. You do not have permission to perform this action or access this resource."}}"
The Azure app has all the permissions enabled, and If I get the AccessToken by going thru the Web Login based way, everything works (of course with some collection admin related configuration).
Can you check on this?
Thanks in advance.

Unfortunately any ability to write using application permissions currently has limited support. We're hopefully not far off adding official support, but we aren't there yet.

At long last we believe session based uploads should work via MS Graph for app-only scenarios. If you're still having issues please let us know.


Improve Java configuration parameters in start, dist and dist-exploded mojos

Align and improve Java configuration parameters of:

forked JVM in start mojo,
JVM in start scripts in dist and dist-exploded mojos.

Configuration changes:

add prodSettings mojo configuration parameter to override some application configuration parameters in production mode (just like devSettings mojo configuration parameter of run mojo is used to override some application configuration parameters when run in development mode),
remove httpPort and httpsPort configuration parameters from start mojo; play.server.http.port=... or play.server.https.port=... should be added to prodSettings configuration parameter to override HTTP or HTTPS port,
remove configFile parameter from dist and dist-exploded mojos, system property should be added to serverJvmArgs (-Dconfig.file=..., -Dconfig.resource or -Dconfig.url=...)

Additionally improve starting application synchronously. Since protocol, host and port can be configurable (in application configuration file or in prodSettings mojo configuration parameter) algorithm to calculate absolute URL to watch for availability must be improved.
Since configuration resolving logic inside production server starting class is quite complicated and is different in different Play! Framework versions, it will not be duplicated.
If protocol, host or port have non-default values (http, <IP_ADDRESS> and 9000) absolute URL must be specified for startCheckUrl mojo configuration parameter (e.g. https://localhost:9001/ instead of / being equivalent of http://<IP_ADDRESS>:9000).

New 1.0.0-beta6-SNAPSHOT snapshot deployed. Documentation updated.


store all track configs

It is interesting work.  It might be best if the track configs are ignored by git, so we don't have even wilder diffs.  I didn't see them in this PR, so maybe you are planning on doing that.
Let me know a bit more about what you are thinking.  This is for your graph right?

Have you come to a decision about this?


Required checkboxes

Hi,
it seems like it has no effect to set required=true here. can you confirm?
		  "applications": { 			"type": "array", 			"title": "Applications", 			"required": true, 			"items": { 				"type:": "string", 				"enum": 					[ 					"appX", 					"appY" 					] 			} 		  }
i'm looking for a solution that forces the user to choose at least one option.
Thanks!

correct the form does not force checkbox  selection.. there is no builtin browser way to do that    you can add an onSubmit() function to you form handler to check it and prevent submission with a message in the field,, but you have to code it..


bioio-tifffile takes precedence over bioio-ome-tiff for ome-tiffs

Describe the Bug

bioio-tifffile takes precedence over bioio-ome-tiff even for ome.tiff files.
Expected Behavior

OME-TIFFs should be correctly picked up by bioio-ome-tiff
Reproduction

I am in napari_bioio but its the same test data:
from bioio import BioImage

img = BioImage("napari_bioio/tests/resources/variance-cfe.ome.tiff")
img

img returns as <BioImage [plugin: bioio-tifffile installed at 2024-07-18 16:09:20.787038, Image-is-in-Memory: False]>
Environment

OS Version: [e.g. macOS 11.3.1]
bioio Version: [e.g. 0.5.0]

❯ pip freeze | grep bioio

bioio==1.0.3
bioio-base==1.0.4
bioio-imageio==1.0.0
bioio-ome-tiff==1.0.0
bioio-ome-zarr==1.0.1
bioio-tiff-glob==1.0.0
bioio-tifffile==1.0.0

Already determined that the issue is that plugin list isn't sorted into longest matching suffix first (i.e. longer suffixes are more specific and we should try them first in the case of plugins handling multiple filetypes)

Is this possibly related to #38 ?

Finally answering your question @toloudis:
Yes I believe this is the same bug as #38! Hopefully anyway.


mFAST overwrites language version and thus breaks build

Consider small project
CMakeLists.txt
cmake_minimum_required(VERSION 2.8)

find_package(mFAST)
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++14")
add_executable(a a.cpp)
//...some targets that use mFAST

a.cpp
auto f(int a, int b) { // requires c++14
	return a + b;
}

int main() {
	return 0;
}

So when I make it, I got compilation error because compilation string is
/usr/bin/c++     -std=c++14   -std=c++11 -o CMakeFiles/a.dir/a.cpp.o -c PATH/a.cpp
--std=c++11 is from lib/cmake/mFAST/mFASTConfig.cmake
I propose not to use add_definitions here and require user to choose appropriate version

Possible fix

with commit c9f9a1575d97721e450be7c60ba0631a0312b03d, you can override the c++ standard flag as follows:
cmake -DCMAKE_CXX_STANDARD=14


download bug

9.0.5

9.0.5

Version:
9.0.5

Target: windows x86  64

error info
Steps to Reproduce:

excuute cmd   electronize build /target win
cant not  download https://github.com/electron/electron/releases/download/v9.0.5/electron-v9.0.5-win32-x64.zip
error ECTRON_BUILDER_CANNOT_EXECUTE
i download this electron-v9.0.5-win32-x64.zip in chrom,  i put this rar to ToolCabinet\bin\Desktop\win-unpacked
but  this  rar will remove  when i retry excute cmd electronize build /target win  .
canyou help me ? if exsit /electron-v9.0.5-win32-x64.zip   dont download agin ,

🎉🚀 New Electron.NET version 23.6.1 released 🚀🎉
With native Electron 23 and .NET 6 support. Your problem should be fixed here. If you continue to have the problem, please let us know. Please note the correct updating of your API & CLI. Info in the README. Have fun!


Ask member to run supportbot when message is posted to channel

We can do this with a "whisper", which send the message only to the member
if we don't want to ping the whole thread
On Wed, Dec 21, 2022, 01:26 Andy Baumgartner @.***>
wrote:

—
Reply to this email directly, view it on GitHub
https://github.com/andybaumgar/nycmesh-support-bot/issues/47, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAX6K6M3JZRLRFCJEHPYMD3WOKPJVANCNFSM6AAAAAATFITMCA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Yeah that's a good idea.  I think the idea with this is to run as soon as they post, so they will likely be the only one in thread initially, but maybe a whisper also doesn't show up for others?

Yep exactly. I think you can whisper in the thread and then only they can
see it
On Wed, Dec 21, 2022, 01:34 Andy Baumgartner @.***>
wrote:

Yeah that's a good idea. I think the idea with this is to run as soon as
they post, so they will likely be the only one in thread initially, but
maybe a whisper also doesn't show up for others?
—
Reply to this email directly, view it on GitHub
https://github.com/andybaumgar/nycmesh-support-bot/issues/47#issuecomment-1360911556,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAX6K6IUKEBYCTC527LV4G3WOKQGNANCNFSM6AAAAAATFITMCA
.
You are receiving this because you commented.Message ID:
@.***>

Merged to try and demonstrate feature for review, but it doesn't work due to permissions.  There's still some issues anyways, so I created a new issue https://github.com/nycmeshnet/nycmesh-support-bot/issues/50.


Fix tests

Fix tests and make them less brittle
Update cassettes with SHARE v2 responses
Update .travis.yml
Upgrade pytest

Changes Unknown when pulling 61ee870ff2ceded1bfa57ee8fa8f52a0069a6371 on fix-tests into ** on develop**.

Changes Unknown when pulling 84ae75c20830dadd2bc6d6c32592289e0d1edf70 on fix-tests into ** on develop**.


[StorageClient] downloadAsStreamAsync() not being async

I was quite happy that StorageClient in PHP is supporting Async fetch.
But when implementing the method does not seem to be fetching data async but synchron instead.
$StorageClient = new StorageClient(array('transport' => 'grpc'));
$StorageBucket = $StorageClient->bucket('xxx');
$_search_prefix = 'some/prefix/test_';
$_promises = array();
foreach ($StorageBucket->objects(array('prefix' => $_search_prefix)) as $_object) {
    $_promises[] = $_object->downloadAsStreamAsync()->then(function(StreamInterface $data) {
                $_contents = trim($data->getContents());
            });
}
Promise\unwrap($_promises);

Basically as it seem the 2nd downloadAsStreamAsync() is waiting for the first one do finish, but not all downloadAsStreamAsync() are executed async

@jdpedrie could you take a look at this issue? Not sure if it's a question or a bug.

@fschirl, the Storage client does not utilize gRPC as a transport option - so that configuration won't have the expected effect. What the client will be falling back on is utilizing Guzzle over HTTP/1.1. The async methods exposed by guzzle required cURL, do you know if your system has it enabled?

Hi @dwsupplee ,
gRPC was already taken out after first test.
php7.3-curl was not installed so far. After adding this module it seems to work.
Many thanks for your support!

@dwsupplee installing php curl library fixed it. now async is working 100% correct. thanks!


aws-template-bastion

will be templating ssh SSO pub key to a bastion secret PR - https://github.com/giantswarm/kubectl-gs/pull/401

Can we close this one?


[1.16.5-3.0.17] Lingering potion debuffs and damage do not applied to player

Description
Vanilla (and possibly modded lingering potions) do not damage or give debuffs to player. However, mobs still affected. This is tested when enableAreaOfEffectOnPlayers is true
How to reproduce

Join a world
Give a lingering potion of harming
Throw it on yourself
See error

Version
Forge: 36.1.32
Dungeon gear: 3.0.17
No log or crash log file
Thank you~

Will be fixed in next update


Supervison hang when tuya is updated to any version over 2023.2.0

Describe the bug
Supervisor hang at reboot when updated to any version over 2023.2.0 and unable to setup platform tuya_local.
To Reproduce
Update to a version over 2023.2.0.
Expected behavior
Expected to work the same with any versions.
Additional context
Everything work as expected before upgrading.
Tried uninstalling and reinstalling whitout success.
Will stay on  2023.2.0 for now.
If the bug involves a device, then please include device diagnostics from
Bug not coming from device.
Please check if there are messages from Tuya Local in the Home
Assistant log (Settings / System / Logs), and include those too.
Logger: homeassistant.setup
Source: setup.py:343
First occurred: 10:26:58 AM (1 occurrences)
Last logged: 10:26:58 AM
Unable to prepare setup for platform tuya_local.switch: Platform not found (No module named 'custom_components.tuya_local.switch').
Logger: homeassistant.util.async_
Source: util/async_.py:182
First occurred: 11:27:44 AM (1 occurrences)
Last logged: 11:27:44 AM
Detected blocking call to sleep inside the event loop. This is causing stability issues. Please report issue to the custom integration author for tuya_local doing blocking calls at custom_components/tuya_local/device.py, line 70: self._api = tinytuya.Device(dev_id, address, local_key)
Core log
Failed to refresh device state for Catit Pixi Smart Fountain.
10:29:59 AM – (ERROR) tuya_local (custom integration) - message first occurred at 10:28:18 AM and shows up 3 times
Catit Pixi Smart Fountain receive loop terminated by exception Sensor sensor.catit_pixi_smart_fountain_water_level is providing enum options, but is missing the enum device class
10:29:59 AM – (ERROR) tuya_local (custom integration) - message first occurred at 10:28:41 AM and shows up 3 times
Failed to refresh device state for Catit Pixi Smart Fountain
10:29:46 AM – (ERROR) tuya_local (custom integration)
Unable to prepare setup for platform tuya_local.switch: Platform not found (No module named 'custom_components.tuya_local.switch').
10:29:43 AM – (ERROR) setup.py - message first occurred at 10:26:58 AM and shows up 4 times
Platform tuya_local does not generate unique IDs. ID 23017707bcff4d4f853a-filter_replaced already exists - ignoring button.catit_pixi_smart_fountain_filter_replaced
10:29:43 AM – (ERROR) button - message first occurred at 10:29:43 AM and shows up 2 times
Error unloading entry Catit Pixi Smart Fountain for button
10:29:43 AM – (ERROR) tuya_local (custom integration)
If applicable, add screenshots to help explain your problem.

You seem to have corrupted your install somehow so files are missing.  How are you installing this integration?

There seem to be a mix of real issues introduced by recent changes and strange issues due to your installation.
Unable to prepare setup for platform tuya_local.switch: Platform not found (No module named 'custom_components.tuya_local.switch').

This is a problem with your install I think.  I have smartplugs working here, so the tuya_local.switch platform is definitely not completely broken.
Detected blocking call to sleep inside the event loop. This is causing stability issues. Please report issue to the custom integration author for tuya_local doing blocking calls at custom_components/tuya_local/device.py, line 70: self._api = tinytuya.Device(dev_id, address, local_key)

This happens if your IP address is not set, and is explained in bug #407
10:29:59 AM – (ERROR) tuya_local (custom integration) - message first occurred at 10:28:18 AM and shows up 3 times
Catit Pixi Smart Fountain receive loop terminated by exception Sensor sensor.catit_pixi_smart_fountain_water_level is providing enum options, but is missing the enum device class

This is due to the recent support added for the "enum" sensor device class.  I did not expect that Home Assistant would be this strict about requiring the device class to be set if options are provided.  In this case, the Water level sensor should actually be an enum type sensor, so I have set it in the config.  But there are also other devices where options are available as a side effect of them mapping values into a percentage range, so I also have to avoid this error for those by limiting sensor.options to only return actual enum values.
10:29:43 AM – (ERROR) setup.py - message first occurred at 10:26:58 AM and shows up 4 times
Platform tuya_local does not generate unique IDs. ID 23017707bcff4d4f853a-filter_replaced already exists - ignoring button.catit_pixi_smart_fountain_filter_replaced

It seems that HomeAssistant has stopped treating two different entity types with the same id as separate, and is now requiring strictly no duplicate ids.  I will have to look into whether it is possible to migrate existing entity ids so as not to lose any user customizations or have new entities defined when I change the ids to include the entity type to avoid these errors.

I've installed from hacs. I've tried to delete component from integration than from hacs and verified that the folder was gone in custom_components, reboot and reinstall but problem remain. Don't know where to look maybe in .storage.

Can you try Redownload from the menu in HACS, and choose "main" as the version.
It is possible that the first error is caused by the second, which I have already fixed.

Thank you for your help, much appreciated. I will try when i get back home saturday.


Zebak water only gives 100 points when used on the palm tree (in a group)

Should be 200

This is working as intended. The hitpoints splat for zebak's room is the same for everyone meaning we can't tell who did what. So for groups it's done with the assumption that every time ANYONE uses the palm, you get the normal points / group size.


MIT license added #4

What's the error "The Travis CI build failed". please advice
Thanks

@shalithasuranga Ignore the build failure. Howevenr that is a seperate issue which we need help.

@shalithasuranga please use seperate branches for separate issues. :)

@rehrumesh  I understood it. Now I am familiar with scenario with multiple branching . Thanks for helping


How to work without a containerId?

Hi,
I am trying to use react-scroll with react-grid-layout.
The thing is that react-grid-layout create a div wrapper, and does not allow proper access to it, so I can't put an id attribute on it. Which mean I can't reference it with react-scroll.
But I can with ReactDOM.findDOMNode() get the actual DOM element (instance) of that div.
The problem is that I don't see any way to initialize the scroller or animate-scroll with an element instance instead of a containerId (in the options object).
Any ideas?

Hi,
I have a similar problem and haven't found a solution with the current library.
Since react uses refs why can't you just put in a ref instead of the id? Are there any downsides?
Is it possible to just change setContainer and add something like that?
if (!options || !options.ref) {     __containerElement = ref;     return;   }


Athomas21501's file

. As a reminder, you have: created a branch, created a file and made a commit, and opened a pull request


Validation does not work as expected when required files are based on if..then..else.. conditions

I suppose that this is an issue in the library we are using to validate object, (I will check the open issues tomorrow)
What happened:
foreachstateValidator is not working well when required files are based on if..then..else.. conditions
What you expected to happen:
According to the specification, foreachstate with
"name",
"type",
"inputCollection",
"iterationParam",
"actions",
"end"
is a valid object
How to reproduce it:
The code below
import {actionBuilder, foreachstateBuilder, produceeventdefBuilder} from '../../src';

fdescribe("", () => {

	it('should xxx', function () {

		const object = foreachstateBuilder()
			.name("ProvisionOrdersState")
			.inputCollection("${ .orders }")
			.iterationParam("singleorder")
			.outputCollection("${ .provisionedOrders }")
			.actions([
				actionBuilder()
					.functionRef({
							refName: "provisionOrderFunction",
							arguments: {
								"order": "${ .singleorder }",
							},
						},
					)
					.build(),
			])
			.end({
					produceEvents: ([
						produceeventdefBuilder()
							.eventRef("provisioningCompleteEvent")
							.data("${ .provisionedOrders }")
							.build(),
					]),
				},
			)
			.build()

		expect(object.name).toEqual("ProvisionOrdersState")
	});

})

that generated the following object (a valid one)
{
    "name": "ProvisionOrdersState",
    "inputCollection": "${ .orders }",
    "iterationParam": "singleorder",
    "outputCollection": "${ .provisionedOrders }",
    "actions": [
        {
            "functionRef": {
                "refName": "provisionOrderFunction",
                "arguments": {
                    "order": "${ .singleorder }"
                }
            }
        }
    ],
    "end": {
        "produceEvents": [
            {
                "eventRef": "provisioningCompleteEvent",
                "data": "${ .provisionedOrders }"
            }
        ]
    },
    "type": "foreach"
}

fails with the following error
[
  {
    instancePath: '',
    schemaPath: '#/then/required',
    keyword: 'required',
    params: { missingProperty: 'workflowId' },
    message: "must have required property 'workflowId'"
  }
]
F

Failures:
1) should xxx
  Message:
    Error: Foreachstate is invalid: must have required property 'workflowId'

Anything else we need to know?:
adding to the object construction
.usedForCompensation(false)
works fine.
Environment:

I noticed other validation failure with "oneof/required". For instance a valid Eventstate with not "transition" raises
[
  {
    instancePath: '',
    schemaPath: '#/oneOf/1/required',
    keyword: 'required',
    params: { missingProperty: 'transition' },
    message: "must have required property 'transition'"
  },
  {
    instancePath: '',
    schemaPath: '#/oneOf',
    keyword: 'oneOf',
    params: { passingSchemas: [Array] },
    message: 'must match exactly one schema in oneOf'
  }
]

I think that removing duplications in the json schema fix this error
see https://github.com/serverlessworkflow/specification/pull/381

I had a look to "conditional subschemas" https://json-schema.org/understanding-json-schema/reference/conditionals.html, apparently if the evaluated property has no value the condition is evaluated as true.

I think that removing duplications in the json schema fix this error
see serverlessworkflow/specification#381

I had that impression indeed but didn't have time to investigate yet.

I had a look to "conditional subschemas" https://json-schema.org/understanding-json-schema/reference/conditionals.html, apparently if the evaluated property has no value the condition is evaluated as true.

You are right, the doc says that exactly. So this issue isn't one (or at least not in the realm of the SDK), the validation seems to work as it should. At the specification level though, we might want to add "required": ["usedForCompensation"] to the if.

@JBBianchi
why this has change the label to wontfix ?

Because this is not an issue, is it ? The validation works as the specification says it should. If there is a fix to be made, it would be at the schema level. Am I missing something?

Because this is not an issue, is it ? The validation works as the specification says it should. If there is a fix to be made, it would be at the schema level. Am I missing something?

still is something that need to be fixed

https://github.com/serverlessworkflow/specification/pull/385

"Fixed" not really as it does what it's supposed to. But the default values in general needs to be addresses indeed. More generic version of the issue: #104

updated the json schema resolve this.
https://github.com/serverlessworkflow/specification/pull/406
https://github.com/serverlessworkflow/specification/pull/385


add push-exif command to CLI

Some people still use photosmeta due to --inplace exif update feature.  Add a similar feature to osxphotos to update the metadata of the photos in the actual library without exporting.

Ideas for how this could work:
osxphotos inplace --exiftool --person-keyword --photos-keyword "{person}"
This would add "{person}" template as a keyword in Photos and add person name as keyword to exif data using exiftool (against the original and edited images).
Could be used with or without exiftool.  Without it, wouldn't modify originals, only the keywords or description in Photos.
Use all the usual query arguments as well as the regular metadata arguments:
  --exiftool
  --person-keyword
  --album-keyword
  --keyword-template
  --replace-keywords
  --description-template
  --finder-tag-template
  --finder-tag-keywords
  --xattr-template

Also add new --photos-keywords and --photos-description to modify the keywords and/or description in Photos.

push-exif is probably a better name for this. Some of the functionality envisioned above is now present in osxphotos batch-edit. I think that modifying the Photos metadata  (batch-edit) and modifying the EXIF data in the original file (push-exif) should be separate functions.

osxphotos push-exif
osxphotos push-exif command
Pushes metadata from Photos to the exif data of the original file (and optionally edited) using exiftool.
Specify which metadata gets pushed:
osxphotos push-exif [--push|--compare] [all keywords location faces date title description favorite]
specify all or subset using one or more of:
all keywords faces date title description
e.g. osxphotos push-exif keywords,faces
--dry-run would show which files would be updated
--verbose would show each field that's written
--include-edited : also write EXIF data to edited files
--skip-original-if-edited: similar to export, skips writing EXIF data to original if file is edited.
--skip-edited: would it be better to include this than --include-edited?
What about raw? (can EXIF data be written to raw files?)
When run, first reads the metadata from the file and stores it in an undo database (like batch-edit does). Can then run with --undo to revert to the original.  This will slow down the process so could also offer a --no-undo that skips the undo database but prompt the user for this.
--compare: use instead of --push and print out a diff for those fields which are different.
Or maybe if --compare is used, it doesn't push. Only need to specify --compare when wanting to compare otherwise will push.
Undo database would use SqliteKVStore with key of UUID and value of JSON dict from reading with ExifTool.
--report to write report of what was updated. Support CSV, JSON, and SQLite as export does.
--append to append to report
See ReportWriter: https://github.com/RhetTbull/osxphotos/blob/main/osxphotos/cli/report_writer.py
Also support the following exiftool options that export supports
  --exiftool-path EXIFTOOL_PATH   Optionally specify path to exiftool; if not
                                  provided, will look for exiftool in $PATH.
  --exiftool-option OPTION        Optional flag/option to pass to exiftool when
                                  using --exiftool. For example, --exiftool-
                                  option '-m' to ignore minor warnings. Specify
                                  these as you would on the exiftool command
                                  line. See exiftool docs at
                                  https://exiftool.org/exiftool_pod.html for
                                  full list of options. More than one option may
                                  be specified by repeating the option, e.g.
                                  --exiftool-option '-m' --exiftool-option '-F'.
  --exiftool-merge-keywords       Merge any keywords found in the original file
                                  with keywords used for '--exiftool' and '--
                                  sidecar'.
  --exiftool-merge-persons        Merge any persons found in the original file
                                  with persons used for '--exiftool' and '--
                                  sidecar'.
  --favorite-rating               When used with --exiftool or --sidecar, set
                                  XMP:Rating=5 for photos marked as Favorite and
                                  XMP:Rating=0 for non-Favorites. If not
                                  specified, XMP:Rating is not set.
  --ignore-date-modified          If used with --exiftool or --sidecar, will
                                  ignore the photo modification date and set
                                  EXIF:ModifyDate to EXIF:DateTimeOriginal; this
                                  is consistent with how Photos handles the
                                  EXIF:ModifyDate tag.
  --person-keyword                Use person in image as keyword/tag when
                                  exporting metadata.
  --album-keyword                 Use album name as keyword/tag when exporting
                                  metadata.
  --keyword-template TEMPLATE     For use with --exiftool, --sidecar; specify a
                                  template string to use as keyword in the form
                                  '{name,DEFAULT}' This is the same format as
                                  --directory.  For example, if you wanted to
                                  add the full path to the folder and album
                                  photo is contained in as a keyword when
                                  exporting you could specify --keyword-template
                                  "{folder_album}" You may specify more than one
                                  template, for example --keyword-template
                                  "{folder_album}" --keyword-template
                                  "{created.year}". See '--replace-keywords' and
                                  Templating System below.
  --replace-keywords              Replace keywords with any values specified
                                  with --keyword-template. By default,
                                  --keyword-template will add keywords to any
                                  keywords already associated with the photo.
                                  If --replace-keywords is specified, values
                                  from --keyword-template will replace any
                                  existing keywords instead of adding additional
                                  keywords.
  --description-template TEMPLATE
                                  For use with --exiftool, --sidecar; specify a
                                  template string to use as description in the
                                  form '{name,DEFAULT}' This is the same format
                                  as --directory.  For example, if you wanted to
                                  append 'exported with osxphotos on [today's
                                  date]' to the description, you could specify
                                  --description-template "{descr} exported with
                                  osxphotos on {today.date}" See Templating
                                  System below.

To implement, the code from photoexporter.py that handles exiftool should be pulled out into a separate EXIFWriter class that can be used both by PhotoExporter and the new push-exif code.
Create a new ExiftoolOptions option configuration class to pass to the writer. In PhotoExporter this can be created from the ExportOptions with no need to modify the export options code. This options class will also need flags specifying which attributes to write in contrast to PhotoExporter which writes almost all the done with a couple exceptions specified by flags.
https://github.com/RhetTbull/osxphotos/blob/1bdd993a542c0fcbebddb270615492aa56a84d6c/osxphotos/photoexporter.py#L1736-L1760

Implemented in v0.63.0 as osxphotos push-exif

@all-contributors please add @Jmuccigr for ideas

@pdewost exporting to iPhone isn't a supported use case for osxphotos so I'm not sure there's a whole lot osxphotos can do. What I would try is to export the metadata to a test image then copy that image to the phone to see if the iOS version of Photos picks up the keywords etc.  If you import a photo into the Mac version of Photos that contains embedded keywords these do get added as keywords in Photos. If this does work, then push-exif might be helpful in your use case.

@pdewost exporting to iPhone isn't a supported use case for osxphotos so I'm not sure there's a whole lot osxphotos can do. What I would try is to export the metadata to a test image then copy that image to the phone to see if the iOS version of Photos picks up the keywords etc. If you import a photo into the Mac version of Photos that contains embedded keywords these do get added as keywords in Photos. If this does work, then push-exif might be helpful in your use case.

Thank you @RhetTbull for this quick reply ; last point leaves me puzzled. Imported embedded keywords are passed to Photos yet are they transferred to the iPhone Photos app when you sync using the Finder (on Sonoma) ?

Imported embedded keywords are passed to Photos yet are they transferred to the iPhone Photos app when you sync using the Finder (on Sonoma)

I'm sorry, I don't understand what you're asking. What I was suggesting is to try an experiment: sync keywords to a single photo using push-exif then copy that photo to the iPhone and see if the iPhone reads the embedded keywords when the photo is copied into the library. The Mac version of Photos does this. I do not know if the iPhone version of Photos does also.

I exported a photo with osxphotos along with its keywords, person names, including adding those to Finder tags. Then I reimported it in my Mac Photo Library before transferring it to my iPhone with cable sync. The tags do not show yet they are detected with tag search. Same for person names.
So the question becomes : the same operation with push-exif does not result in making the photo searchable on iPhone using tags or person names and I do not understand why...

Interesting. I exported an image using --exiftool which applies the same metadata as using push-exif and when I imported that photo into my iPhone (I used AirDrop on the exported image), the phone did index the keywords -- see screenshot below which shows a sample image from the OSXPhotos test library.  It took a few minutes before keywords showed up in search.
How are you copying photos to the Phone? Are you doing this from Photos? If so, it's possible Photos is exporting a version of the photo that strips metadata. In this case, it's probably better to export images using osxphotos export --exiftool then drag those into the phone.

I copy photos to the phone using the synchronization feature that was before in iTunes/Music and now is part of the Finder on macOS Sonoma. I select albums (including smart albums) and then let the sync happen, via a usb-c cable. All copied photos appear in "on my Mac" section of the iOS Photos album view yet they cannot be searched by tags or by face name.
Using osxphotos push-exif keywords,faces,persons,description --favorite-rating --person-keyword --report 'push_exif_{today.date}.csv' --append --push-edited --selected followed by syncing to the iPhone does not result in keyword indexing.
Using osxphotos export /Volumes/Samsung_X5/osxphotos2024-exports --selected --touch-file --finder-tag-keywords --person-keyword --xattr-template findercomment "{title}{title?{descr?{newline},},}{descr}" --exiftool-merge-keywords --exiftool-merge-persons --exiftool --strip --update followed by importing the photos back into macOS Photos app, then followed by syncing to the iPhone does it.
Could it be because of the fact that I do export the keywords and persons in the Finder Tags and that these are "ingested" into macOS Photos at import ?
Would there be an option for push-exif to also write Finder Tags that could make keywords indexing happen on the iPhone ?

Could it be because of the fact that I do export the keywords and persons in the Finder Tags and that these are "ingested" into macOS Photos at import ?

I would be surprised if that's it. In my test, the iPhone clearly ingested keywords from the EXIF/XMP keywords fields.
I think you need to do some some experiments to isolate certain variables to see exactly what it is. Try an export with only --exiftool, then reimport, then sync. Does that work?  Then try an export with only --finder-tag-keywords and reimport then sync. Does that work?  In each case, I would start with a "clean" photo so you know exactly what data is being copied. I am unfamiliar with the sync utility so I don't know what it is doing. In my test of using AirDrop of an exported photo, the iPhone clearly read the data from the embedded keywords.

The iPhone ingests for sure when using Airdrop. What I am trying to do is to work directly in the Photos macOS App where I manage 900Gb and 40 years and make sure that I can find the "synced" pictures in my iPhone in an easier manner than just scrolling through albums. Using the iOS Photos search feature would help if only it were capable of finding people (faces) as well as keywords (tags). So the osxphotos export to Mac and then import in iPhone is impractical...
Now I did test the following with just one image :
1/ osxphotos export /Volumes/Samsung_X5/osxphotos2024-exports --selected --touch-file --exiftool --person-keyword --exiftool-merge-keywords --exiftool-merge-persons --update . The exported photo was immediately reimported in macOS photos App along with its tags plus a face tag. After synchronizing with iPhone it can be searched by tags which was not the case of the original photo.
2/ osxphotos export /Volumes/Samsung_X5/osxphotos2024-exports --selected --touch-file --finder-tag-keywords --person-keyword --xattr-template findercomment "{title}{title?{descr?{newline},},}{descr}" --update does not keep tags at reimport.
3/ running osxphotos push-exif keywords,faces,persons,description --favorite-rating --person-keyword --report 'push_exif_{today.date}.csv' --append --push-edited --selected on the same picture and checking afterwards with the --compare option shows that the updated file's metadata has been indeed updated. Yet as the metadata are left unchanged in the macOS Photos App tags, they actually have no reason to be updated. It seems indeed that the Finder's sync method from Mac to iPhone does not transfer the files themselves, letting the iPhone rebuild its database from the EXIF tags, but rather exports the macOS Photos tags and keywords.

Tried a rebuild of the Photos Library work hoping it maybe would update the Mac's keywords and tag system with the EXIF metadata found in the pictures, yet there was no change. Photos synchronized to the iPhone are arbitralily searchable by keywords (some keywords will return 3 photos instead of dozens...) and none by person name.
As my purpose is to make photos search as easy on iPhone than it is on my Mac, I was wondering whether such dysfunctional behavior would change if I were using referenced photos instead of photos that are imported (and buried) in the Photos Library package. Maybe the export to the iPhone would leverage buried push-exif metadata ?
Sorry but this is very confusing to me...

but rather exports the macOS Photos tags and keywords.

If this is the case, then you can easily use osxphotos batch-edit to set the tags in Photos before the export.
Select one or more photos in Photos then run:
osxphotos batch-edit --keyword "{person}"
This sets the Photos keywords to include the person name.
Are the other settings like title, description, favorite status transferred?


Natgrads

This PR seeks to add natural gradients to GPJax, as well as two new Gaussian variational family parameterisations.
Please check the type of change your PR introduces:

[ ] Bugfix
[ x] Feature
[ ] Code style update (formatting, renaming)
[x ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Current state:
Code currently only works for the natural parameterisation case. Main thing (asides from the obvious simplification of the rough codebase and improvement of the API) is that we lack natural gradients for general parameterisations.
There are two notebooks associated with this PR:

natgrads.ipynb has the case the variational family is chosen as the natural parameterisation - this should work but I have not tested it since I rebased with the master branch.
Natural Gradient General case.ipynb is provided to show a rough sketch of what the general case might look like, that will involve the user defining a bijection between their parameterisation and the natural parameterisation.

There are some unit tests provided for the new variational families, and for natural_gradients.py in its current state, as well as changes made in parameters.py.
As a final note, it is likely that some of the functions defined in natural_gradients.py for stopping gradients might be better generalised and added to abstractions.py or parameters.py

@thomaspinder it would be good to get your thoughts on the code so far (some of it rather rough). I believe the implementation works. The main issue is that the notebook needs writing before merging, I'll get on with this in the meantime. I'll need to test some benchmarks against fit_batches once #99 is merged, to see if performance is up to scratch.

@thomaspinder I have rebased the branch with master and would appreciate a review.
On my end, I need to:

Update and add some tests
Write the notebook

@thomaspinder for the commits d84ede9, e0b60d4 and bd6e4aa, I have addressed many of your comments and suggestions.
Outstanding issues are to write unit tests, the notebook, and explanation of parameter optimisation order.

Hi @thomaspinder, I believe I have addressed your comments so far. I expect all functions to be covered by unit tests now (but we'll see what CodeCov says). I would appreciate a review on the latest code changes - and I expect we can improve it further.
One key thing that I dislike, is that the fit_natgrads abstraction takes it fist argument as the variational inference strategy, while fit and fit_batches take in objectives. I'm not sure if you had any thoughts on this?
I am going to start work on writing the notebook today.


Inners #945

Current coverage is 91.51%

Merging #952 into master will increase coverage by +0.05% as of 858f5c2

@@            master    #952   diff @@
======================================
  Files           80      74     -6
  Stmts         8831    8829     -2
  Branches      1709    1709
  Methods          0       0
======================================
+ Hit           8077    8080     +3
  Partial        175     175
+ Missed         579     574     -5

Review entire Coverage Diff as of 858f5c2

Powered by Codecov. Updated on successful CI builds.

Awesome. Looks like a huge amount of work!
Big step towards 2.0.0


Amount of connected devices to guest network

First of all thank you for this helpful integration!
Would be great to have a sensor to show if either someone is connected to the guest network or even to show how many devices are connected to it. So you can use this sensor for your automations without adding each "guest" to a group of device trackers.

Thanks a lot. This is awesome!


python312Packages.social-auth-core: 4.5.2 -> 4.5.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.social-auth-core is: Module for social authentication/registration mechanisms
meta.homepage for python312Packages.social-auth-core is: https://github.com/python-social-auth/social-core
meta.changelog for python312Packages.social-auth-core is: https://github.com/python-social-auth/social-core/blob/4.5.3/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.5.3 with grep in /nix/store/navw7dqk3102adc4g2cinikr5r3pqfn9-python3.12-social-auth-core-4.5.3
found 4.5.3 in filename of file in /nix/store/navw7dqk3102adc4g2cinikr5r3pqfn9-python3.12-social-auth-core-4.5.3

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
netbox
netbox_3_6
netbox_3_7
python311Packages.social-auth-app-django
python311Packages.social-auth-core
python312Packages.social-auth-core

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/navw7dqk3102adc4g2cinikr5r3pqfn9-python3.12-social-auth-core-4.5.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.social-auth-core https://github.com/r-ryantm/nixpkgs/archive/06193f2f45111faaba5718fa8aea2b5535032d84.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/06193f2f45111faaba5718fa8aea2b5535032d84#python312Packages.social-auth-core

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/navw7dqk3102adc4g2cinikr5r3pqfn9-python3.12-social-auth-core-4.5.3
ls -la /nix/store/navw7dqk3102adc4g2cinikr5r3pqfn9-python3.12-social-auth-core-4.5.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package marked as broken and skipped:

python312Packages.social-auth-core

3 packages built:

netbox (netbox_3_7)
python311Packages.social-auth-app-django
python311Packages.social-auth-core

Maintainer pings
cc @n0emis for testing.

@ofborg build python311Packages.social-auth-core


Leaderf mru  not  find  recent file

Open the file to write content and exit(:wq)
Open the file just now
:Leaderf mru     not  find the file

can you show me in more detail how to reproduce?

open an existing file

vim  hello.lua

Write some content and then save to exit

start  vim ,  then input   :Leaderf mru  not find     hello.lua

can you see the video   https://www.bilibili.com/video/BV1Gv4y1771R/

I am sorry  , I use lazy load the plug


upstream-community-operators intel-device-plugins-operator (0.20.0)

added forgotten example YAML for Intel DSA device plugin

/allow/serious-changes-to-existing

@jozzi @mvalarh This is a cosmetic change in my opinion. Can you label this PR with /allow/serious-changes-to-existing ?

/hold cancel


Annotation in browser

In addition to the icon being added after cancelling annotation .
The add note button is replaced with the edit (note) button


Refactor main committime method to reduce complexity

This should resolve the final linting error as well.
@redhat-cop/mdt

To test:

Log in to openshift (with build data present)
Start exporter. python exporters/committime/app.py
Once started, run the following and confirm you get results back: curl localhost:8080 | grep 'commit_timestamp{.*} \d\.\d+e\+\d\d'


feat: remove react-native-env

fixes #42

Exactly right, in fact, in a react-native project really there is no need to .env. for many web app projects, there is no need too. thanks for your code and simplifying.


Unify pretty print parse errors

Request description
Per feedback on #38.
"As I'm looking through StablehloOps.cpp, I see that we have a bunch of different ways to express expected vs actual mismatches: "expected, saw", "expected, got", "expected, found", etc. We'll need to sort this out at some later point."
This issue will be used to track the unification of parse error messages.
Additional context
No response

@zhouxin913 You might be interested in this ticket as well, given our discussion about verification and shape inference error messages from earlier today.

Yes, aligning errors message will not only improve user experience, but also make code clean and easy to maintain. Some quick ideas in verifiers/shape functions plan like providing macros and/or utils functions to wrap some errors for example: Expect dim i of tensor A to be same as dim j of tensor B, but got 1!=2. It's quite similar to this issue for print parse. Will share a quick design and looking forward to work on this together.

Update: this request is related to https://github.com/openxla/stablehlo/issues/154, which is work in progress addressing similar problem for type inference. Consider start this work once that one is addressed for code sharing.


fix PR

rusty breadcrumbs
working graph building; mermaid
minor changes
progress on tree view
edge sorting
fix list index
fix edge link class
Builders accumulate GraphConstructionData immediately, instead of intermediate representation

LGTM! 👍


Add Truffle tests

Added truffle tests for Counter and Wallet contracts;
Moved Solidity build folder from ./client/src/contracts to ./build because it is default and expected location.

Does fix issues #1 and #2.

Instructions should be updated at three places: ZepKit Github read.me file, ZepKit itself and https://zepkit.zeppelinos.org.

@ylv-io looks good then, feel free to merge!


username space support + vote url fix v3

kfjvnkfadkvbk i think i got it

Uhhh why would you set the victim to the pillager/attacker in the pillage command? Denied.

Also there's literally no difference in functionality in the username space support commit changes


ESC should cancel multi-carets in the script editor

Godot version
v4.0.beta.custom_build [11e1bac76]
System information
Linux Fedora - Godot Engine v4.0.beta.custom_build.11e1bac76 - https://godotengine.org Vulkan API 1.2.0 - Using Vulkan Device #0: NVIDIA - NVIDIA GeForce GTX 1080
Issue description
Currently there is no way to return to a single caret after using multiple carets by only using the keyboard.
In VSCode this is done by pressing esc.
Steps to reproduce

Open a script file in the text editor
Use shift + d to select multiple text occurrences and create multiple carets (or hold alt while clicking at different positions)
Press Esc
See that there are still more than one caret

Minimal reproduction project
No response

cc @alfredbaudisch – would you be interested in taking a look at this? :slightly_smiling_face:

@Calinou I'll take a look 🙂