[TypeScript] Can't use array-like syntax with PaletteColor

The interface PaletteColor doesn't contain a definition for array-like syntax and it's clearly possible.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
I have this in the makeStyles function:
{
 avatar: {
      backgroundColor: theme.palette.primary[800],
      color: theme.palette.getContrastText(theme.palette.primary[800]),
    }
}

This doesn't let TS compile as the interface doesn't have array-like declaration enabled.
Expected Behavior 🤔
It shouldn't throw an error as this works perfectly fine:
avatar: {
      backgroundColor: (theme.palette.primary as any)[800],
      color: theme.palette.getContrastText((theme.palette.primary as any)[800]),
    },

Context 🔦
I have several themes on the site, and I'd like to use the more "darker" version other then just theme.palette.primary.dark because it doesn't look good on the UI.
Your Environment 🌎

Tech
Version

Material-UI
v4.8.0

React
16.12.0

Browser
Firefox Nightly

TypeScript
3.7.3

@dev-cyprium Check the TypeScript documentation regarding extending the default theme structure: https://material-ui.com/guides/typescript/#customization-of-theme


[lexical-react] remove editor__DEPRECATED that has been deprecated for two years

Description
The editor__DEPRECATED prop has been deprecated for two years (#1407), this PR removes it.
Test plan
There were no tests for this feature, and its absence does not need new tests.

I just recalled Chriss @montlebalm was mentioning use case with reusing editor instance via this prop: https://github.com/facebook/lexical/issues/4986
Wonder if it's used by other folks too and (although it was marked as deprecated forever) it worth having explicit exception when it's passed

use

@fantactuka FWIW we're also using the same workaround described in the issue internally and that's not going away anytime soon

@fantactuka I can't think of a good reason to render a LexicalComposer when you already have the editor instance, LexicalComposerContext.Provider can be used instead


crypto is not defined when calling bus.publish()

node: 18.18.2
sst: 3.1.10
Hello
In my lambda function crypto is well defined and I can use it without problem
only when I call bus.publish() I get the following error.
err: {
    "type": "ReferenceError",
    "message": "crypto is not defined",
    "stack":
        ReferenceError: crypto is not defined
            at hmac (/home/john/workspace/app/node_modules/aws4fetch/dist/aws4fetch.esm.mjs:219:21)
            at AwsV4Signer.signature (/home/john/workspace/app/node_modules/aws4fetch/dist/aws4fetch.esm.mjs:181:27)
            at AwsV4Signer.authHeader (/home/john/workspace/app/node_modules/aws4fetch/dist/aws4fetch.esm.mjs:173:34)
            at AwsV4Signer.sign (/home/john/workspace/app/node_modules/aws4fetch/dist/aws4fetch.esm.mjs:160:52)
            at AwsClient.sign (/home/john/workspace/app/node_modules/aws4fetch/dist/aws4fetch.esm.mjs:52:57)
            at AwsClient.fetch (/home/john/workspace/app/node_modules/aws4fetch/dist/aws4fetch.esm.mjs:65:40)
            at Object.publish (/home/john/workspace/app/node_modules/sst/dist/aws/bus.js:35:29)
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
            at <anonymous> (/home/john/workspace/app/apps/auth/src/v2/verify.ts:162:5)
            at async file:///home/john/workspace/app/.sst/platform/dist/nodejs-runtime/index.js:96:16
  }

It seems related to aws4fetch specifically to https://github.com/mhart/aws4fetch/issues/61
After some tests I've found that adding  global.crypto = require('crypto'); to the top of sst/aws/bus.js fix the issue
We could integrate this fix until aws4fetch figure it out that would make Bus usable

I've switched to using this instead
import crypto from 'crypto';
global.crypto = crypto

with global.crypto = require('crypto'); the require() is messing with ES module scope
@jayair @thdxr can you reproduce the issue ?

It'll work with Node 20


Figure out why MoveToOrigin doesn't achieve full reward

Episodic return tops out at less than 0.5. The env is trivial and something very close to 1.0 should be achievable so there has to be a bug somewhere, either in the env or ppo train loop.

Fixed by adding feature normalization: https://github.com/entity-neural-network/incubator/pull/31


3D convolution tunable example

Based on the 2D convolution from CLTune. I extended it in the third dimension and added a "Sliding plane" algorithm.
It still takes too much time to generate the tuning space due to all parameters and constraints, so it is necessary to cut it before tuning.

Hello,
thanks for the PR. I'll hopefully have time to review it during ths weekend. Yesterday, I commited a fix which should make generating of configurations faster, it is available on development branch.
Did you manage to try it, and if so, is there any noticable performance gain?

I tried it, this is based on that commit. It may be working well for some simpler space, but it still doesn't get me down to minutes for the whole space.

I guess with parameter space this large, it might be better to generate configurations on-the-fly rather than all at start. This will however require some larger code modifications.

Indeed this modification is not easy. It is not a high priority task now, but we can focus to solve it in the future. The ATF framework has faster tuning space generation: https://onlinelibrary.wiley.com/doi/abs/10.1002/cpe.4423, so we can also get some inspiration there.


Update README with credits and flashing hints

After finding out some flashing quirks, I put them into the readme. Also linked our usernames.

Oh, and we have a License file AND have the license plastered all over every file.
I know putting the license into the source file is a C thing, but generally I prefer only having the license file and that is it. It is legally the same. But I guess in the source files I do not care, my IDE hides it. :P
But the README does not need it.


Invalid Address

Issue description
I recently installed the Firefly wallet and when I attempt to send IOTA from my Binance Wallet, the address copied from Firefly shows as invalid.  I am very new to crypto.  What am I doing wrong?
Firefly version
1.2.0
OS details
Windows 10
Can the issue be reliably reproduced?
Yes
Steps to reproduce the issue

copy the receive wallet address from firefly
paste into the send address in the IOTA asset send
address shows a invalid address
...

Expected behaviour
send IOTA to firefly wallet
Actual behaviour
can't send IOTA to invalid address
Errors
invalid address

Do you have any screenshot?
My guess is you selected the Binance Chain (BEP-20) to withdraw your funds.
Binance chain is incompatible with IOTAs mainnet.

No screen shots but I did select miotac iota.
Sent from my iPhone

On Dec 16, 2021, at 10:22 PM, svenger87 @.***> wrote:

Do you have any screenshot?
My guess is you selected the Binance Chain (BEP-20) to withdraw your funds.
Binance chain is incompatible with IOTAs mainnet.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.

Oh yeah, Thats wrapped IOTA on Binance Chain. You can´t transfer those to firefly.

Any way around it?
Sent from my iPhone

On Dec 16, 2021, at 10:37 PM, svenger87 @.***> wrote:

Oh yeah, Thats wrapped IOTA on Binance Chain. You can´t transfer those to firefly.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.

To get tokens to Firefly one needs IOTA tokens that reside on IOTA's network (called the Tangle). To achieve this, send the tokens back to Binance and withdraw them to the Tangle network.
Should Binance have issues with withdrawals, get in touch with Binance's support.

I'm going to close this as it is a non-Firefly issue. Best of luck with withdrawals!

I am also having this issue on Bitfinex. Add the Firefly wallet address and it is triggering the invalid address error.


Fix non deterministic test of tsbuild

Merging this to verify this fixes the non deterministic nature of the build.


[Bug]: Login and sign up page is not working well.

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
When we try to sign up with a new email, it's not working.
Expected behavior
To make a proper sign up and login page
Add ScreenShots
No response
On which device are you experiencing this bug?
Chrome
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

I want to work on the[Bug]: Login and sign up page is not working well. #433 issue .Please Assign it for me .You can check my recent works on my github profile .... Thanks


Widget: Seriously injured & killed in Bicycles and Scooter accidents-Line chart

Name
Widget display the numbers of cyclists and scooters injuries who were seriously injured or killed in a selected road section.
Seriously_injured_killed_in_Bicycles_Scooter
Title
מקטע/ עיר ושם רחוב רוכבי אופנים וקורקינט שנפצעו קשה או נהרגו
Visualization

Visualization explanation
Visualization contains Line Graph display sum of injuries etch year in in a selected road section.
2 types of injuries: seriously injured and killed.
3 types of vehicle: bicycles, electric bicycles and electric scooter. Those 3 types reflect what is consider as “soft mobility”.
Years are between “year lower bound” (2008) and “year upper bound” (2022)
I recommend to display 10 years 2012-2022
Use case
This infographic should be displayed when:

bicycles, electric bikes or scooter are mention in news flash.
When the input is only a location (considering those are mainly urban accidents) display the widget if at least half of the included years have data.

SQL query
SQL query for line chart (Actually, the location and starting year should be taken from the infographic query.)
The query has the flowing parameters:

Yishuv Symbol (same as city code) the output will be Yishuv name in Hebrew.
Year lower bound (currently 2008)
Year upper bound (change over time)
(make sure we are counting pepole and not accidents)

Additional context
Bicycles: vehicle_type=15
Electric Bicycles: vehicle_type = 23
Electric Scooter: vehicle_type = 21
Information :
מספר נפגעים שנפצעו קשה או נהרגו בתאונות אופנים, אופנים חשמליים וקורקינט

Hi @ziv17
Thanks for your feedbak. In light of this, I have updated the "use case"  section and link to the sql query.
Hope this helps...

Hi @MichalOren

There are mismatches between the text and the query (e.g. location). Should I assume the text is the correct option?
regarding when to display, I assume you mean half of the years in the period that used. Also when none occurred in recent years?
in the information, to write motorcycle, although we take also bicycle and קורקינט?

Hi @ziv17

Im not sure what you mean... The query expect Number to identify Yishuv, is that our input ?
Yes. In 2008 there was sparce data on scooters and electric bicycles, I expect it would be more common in recent years.
I have fixed the "Information" text.

Hi @MichalOren , regarding 1, I mean that actually the query will use the infographic location, which is either yishuv & street, or road segment.

Hi @MichalOren , I updated the description comment (added a comment to the query, and changed the text of when to display.)
Is it OK?

Json Structure:
{
"name": "seriously_injured_killed_in_bicycles_scooter",
"data": {
    "items": [
        {
            "label_key": 2018,
            "value": 3
        },
        {
            "label_key": 2019,
            "value": 4
        },
        {
            "label_key": 2020,
            "value": 20
        },
        {
            "label_key": 2021,
            "value": 43
        },
        {
            "label_key": 2022,
            "value": 74
        },
    ],
    "text": {
        "title": "רוכבי אופניים וקורקינט שנפגעו קשה או נהרגו",
        "subtitle": "במקטע צומת טבריה - צומת כפר נחום"
    }
},
"meta": {
    "rank": 32,
    "information": "Ask Product"
}
},

Ask Product regarding the information field

Hi @tkalir
Information text :
מספר הנפגעים שנפצעו קשה או נהרגו בתאונות אופנים, אופנים חשמליים וקורקינט

@MichalOren it's not exactly the same string since subtitle has the addition of "במקטע" or "ברחוב"
We can create standartization and make sure that we use location info and subtitles from meta section only, for example (perhaps standartization that will include organizing titles and subtitles)
If so I suggest we'll perform it in a different issue and pr, and not in this pr.
@ziv17 what do you think?

@MichalOren in urban resolution - should we filter both street and yishuv or only yishuv?

Hi @atalyaalon @tkalir
Good point, in urban resolution, probably there will not be enough data per street+yishuv. Lets go with only Yishuv.
Regarding Titles and Subtitles - i will rase this issue in our next meeting

@MichalOren
Making sure - the title & subtitle in Hebrew are
"רוכבי אופנים וקורקינט שנפגעו קשה או נהרגו"
"ב(שם הישוב)" / "בכביש (מספר) במקטע (שם)"
and in English "Severely injured or killed in bike, e-bike, or scooter accidents"
"in (yishuv name)" \ "in road (number) in segment (name)"
?

Hi @tkalir
Road number is in rigth side of the widgets. no need to include
"רוכבי אופנים וקורקינט שנפגעו קשה או נהרגו"
"ב(שם הישוב)" / במקטע (שם)"
and in English "Severely injured or killed in bike, e-bike, or scooter accidents"
"in (yishuv name)" \ "in segment (name)"

Hi  @tkalir
Great job & well done (:
Some feedback
reproduce
https://anyway-infographics-staging.web.app/newsflash/133673

Need update "title" and "information"- in hebrew
"title": "רוכבי אופנים וקורקינט שנפגעו קשה או נהרגו",
"subtitle": ברחוב הזיתים בגבעת שמואל
"information": מספר נפגעים שנפצעו קשה או נהרגו בתאונות אופנים, אופנים חשמליים וקורקינט

"subtitle" should contain "location_text" withour road number ( take example from killed_and_injured_count_per_age_group

"text": {
"title": "Number of severely injured or killed in bike, e-bike, or scooter accidents",
"subtitle": "בגבעת שמואל"
}
},
"meta": {
"widget_digest": "4ce0cd19dce03af188b332db430c8349",
"rank": 32,
"information": "Severely injured or killed in bike, e-bike, or scooter accidents"
welcome to ask me if something is not clear

Reopen due to coding completion


Label Vertebrae Errors in SCT v402 and v405

I ran sct_vertebrae_label using beta versions 4.0.0-beta.2 and 4.0.0-beta.5 (master branch) in a t1w imaging.
For both versions I had the same error at C4 vertebra (please, look figures in attached). I am also sending the processed files in order to reproduce the same error.

v402.zip
v405.zip

Hi @thiagojrezende:

did you experience similar issues with 3.2.7?
can you try with -scale-dist 0.8?

Hi @jcohenadad ,
Both strategies provides worse labeled vertebrae.
This is the version 3.2.7

This is with -scale-dist 0.8

could you try with -scale-dist 0.6?

Not worked as well.

0.7?

Not worked again.

Issue closed because the vertebrae labels used in this study will be C2 and C3. Less than 5% of all processed images showed problems in to identify the vertebrae label.


feat(cli, introspection,migrate,sdk): add npm/yarn/npx in front of suggested commands

Closes https://github.com/prisma/prisma/issues/3210

I'm checking to do it in NodeEngine too

Not done in JavaScript files like preinstall postinstall (because JS).

What does that mean?

Not done in JavaScript files like preinstall postinstall (because JS).

What does that mean?

That my script is in TypeScript so I would need to do a variant for JavaScript here.

Not done in JavaScript files like preinstall postinstall (because JS).

What does that mean?

That my script is in TypeScript so I would need to do a variant for JavaScript here.

Do we output any commands here for users to pick up from it?

Yes we do so we should find a way to do it there too I guess

https://github.com/prisma/prisma/issues/3328


Not working and I cannot understand why

I have clearly gone code blind here because I have specified the filters I want, the diagnostic output says the files changed satisy at least one of the filters, and yet they are all set to "false".  Somebody put me out of my misery please :)
Run dorny/paths-filter@v2
  with:
    filters: path_check: |
    - '.github/workflows/cypress-tests.yml'
    - '.github/workflows/composites/**'
    - 'common/**'
    - '!common/docs/**'
    - 'helios/**'
    - '!helios/documents/**'
  test_check: |
    - 'helios/apps/web/**'
  test_check2: |
    - 'helios/apps/web/**/*.*'

    token: ***
    list-files: none
    initial-fetch-depth: 100
Fetching list of changed files for PR#74 from Github API
  Invoking listFiles(pull_number: 74, page: 1, per_page: 100)
  Received 13 items
  [modified] .github/workflows/build-test-install-helios.yml
  [modified] .github/workflows/composites/pre-job-checks/action.yml
  [modified] .github/workflows/cypress-tests.yml
  [modified] .github/workflows/end-to-end-tests.yml
  [modified] .github/workflows/system-tests.yml
  [modified] helios/apps/web/public/fontawesome-free-5.0.6/advanced-options/use-with-node-js/fontawesome-free-brands/package.json
  [modified] helios/apps/web/public/fontawesome-free-5.0.6/advanced-options/use-with-node-js/fontawesome-free-regular/package.json
  [modified] helios/apps/web/public/fontawesome-free-5.0.6/advanced-options/use-with-node-js/fontawesome-free-solid/package.json
  [modified] helios/apps/web/public/fontawesome-free-5.0.6/advanced-options/use-with-node-js/fontawesome/package.json
  [modified] panoptes/modules/panoptes-rails/public/fontawesome-free-5.0.6/advanced-options/use-with-node-js/fontawesome-free-brands/package.json
  [modified] panoptes/modules/panoptes-rails/public/fontawesome-free-5.0.6/advanced-options/use-with-node-js/fontawesome-free-regular/package.json
  [modified] panoptes/modules/panoptes-rails/public/fontawesome-free-5.0.6/advanced-options/use-with-node-js/fontawesome-free-solid/package.json
  [modified] panoptes/modules/panoptes-rails/public/fontawesome-free-5.0.6/advanced-options/use-with-node-js/fontawesome/package.json
  Invoking listFiles(pull_number: 74, page: 2, per_page: 100)
  Received 0 items
  All changed files has been fetched from GitHub API
Detected 13 changed files
Results:
Filter path_check = false
Filter test_check = false
Filter test_check2 = false
Changes output set to []

Even the very simple test_check filter is false when it clearly states it found a change on that path.

Ahh - my filter definition had a typo and it didn't error - just threw all the filters our of whack.


Change errors library

Until now we used https://github.com/juju/errors, this was a (failed) expirement to get better error messages. The code in this PR vendors and uses the much better library from https://github.com/pkg/errors. Among others, it allows printing stack traces for errors created with errors.New().
The code also adds a check to run in the integration tests which tests for packages importing the errors stdlib package. This is forbidden by now, the new github.com/pkg/errors package should be used.
Sample:
$ restic cat pack aec070645fe53ee3b3763059376134f058cc337247c978add178b6ccdfb0019f
hash of data does not match ID, want
  aec070645fe53ee3b3763059376134f058cc337247c978add178b6ccdfb0019f
got:
<PHONE_NUMBER>365fc7a3dd7840fd3d56f29306cd30c0f2c13cb500fe79617290ff

main.CmdCat.Execute
        /home/fd0/shared/work/restic/restic/src/cmds/restic/cmd_cat.go:163
main.(*CmdCat).Execute
        <autogenerated>:18
github.com/jessevdk/go-flags.(*Parser).ParseArgs
        /home/fd0/shared/work/restic/restic/vendor/src/github.com/jessevdk/go-flags/parser.go:278
github.com/jessevdk/go-flags.(*Parser).Parse
        /home/fd0/shared/work/restic/restic/vendor/src/github.com/jessevdk/go-flags/parser.go:154
main.main
        /home/fd0/shared/work/restic/restic/src/cmds/restic/main.go:34
runtime.main
        /usr/lib/go/src/runtime/proc.go:183
runtime.goexit
        /usr/lib/go/src/runtime/asm_amd64.s:2086

Hm, that's a bit too verbose at the moment:
$ bin/restic-debug cat x
debug enabled
type or ID not specified, Usage: [pack|blob|tree|snapshot|key|masterkey|config|lock] ID
main.CmdCat.Execute
        /home/fd0/shared/work/restic/restic/src/cmds/restic/cmd_cat.go:37
main.(*CmdCat).Execute
        <autogenerated>:18
github.com/jessevdk/go-flags.(*Parser).ParseArgs
        /home/fd0/shared/work/restic/restic/vendor/src/github.com/jessevdk/go-flags/parser.go:278
github.com/jessevdk/go-flags.(*Parser).Parse
        /home/fd0/shared/work/restic/restic/vendor/src/github.com/jessevdk/go-flags/parser.go:154
main.main
        /home/fd0/shared/work/restic/restic/src/cmds/restic/main.go:34
runtime.main
        /usr/lib/go/src/runtime/proc.go:183
runtime.goexit
        /usr/lib/go/src/runtime/asm_amd64.s:2086


better way of hooking up Format::addFormatToContext to script nodes

If you look at GafferImage::Display::hashFormat and GafferImage::Display::computeFormat, you'll see todos about the format mechanism being broken.
The node expects a context entry called "image:defaultFormat", which originates on a plug on the script node called "defaultFormat", and makes its way into the context via a callback called Format::addFormatToContext(). Currently, this callback gets added by the "Format::addDefaultFormatPlug()" method, which gets called from a couple of methods in the Format class, and also from parentChanged callbacks in the ImageNode/ImageStats classes. The latter sometimes fail through being unable to find the script node, meaning that a lot of the time "image:defaultFormat" is missing from the context. This leads to annoying errors when you view our interactive render nodes, which sometimes interfere with the UI.
I've got a slightly annoying workaround for it which only works in Caribou at the moment, but if there was a static signal that got triggered every time a ScriptNode was created, it'd be quite easy to make sure this callback always gets hooked up.

Closing this as a duplicate of #888.


Rename Accept Chat Button

"Accept" is confusing in a need-offer scenario, thus we need to rename the button label.
Other labels that come to mind:

Accept Chat
Chat
Start Chat
...

Issue related to old, deprecated prototype.


Deprecate values.yaml trustDomain setting

Part of https://github.com/istio/istio/issues/27734
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
71ee1911bf92f3f4a825263b6ee7d2cb71422e76
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@linsun @sdake @costinm PTAL

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
71ee1911bf92f3f4a825263b6ee7d2cb71422e76
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
71ee1911bf92f3f4a825263b6ee7d2cb71422e76
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
8bb722fd90cc90e0caf49ab2c9e2efdd43a1d78e
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
63f169e62901bbf52b656ba26d40fbc849a1d0ae
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


DEV: TOPIC_NEEDS_EXPERT_POST_APPROVAL is no longer a boolean

Marking the tests as pending until a fix can be made.

Spec failure is relevant.


[react-presence]: Reduce requestAnimationFrame logic

This work all stemmed from an issue with Checkbox indeterminate state in our stories. There was a FOUC during its indicator unmount phase due to these requestAnimationFrames in Presence and the fact that our Checkbox stories assume "unmounted" means "unchecked".
I've updated the story to more explicitly target states for styles as I don't think it's a good idea to assume that when it is not indeterminate it is unmounted or checked. A new state could be added so the logic should be more explicit. Plus, "unchecked" and "unmounted" are conceptually different things that could happen at different times (like this).
This PR:

Reduces the amount of logic wrapped in requestAnimationFrame to try ease these sorts of issues. I want to try remove/improve the one around the send('UNMOUNT') too which is the main culprit here but that's proving more difficult. I'll look into it separately.
Potential bug fix I spotted which helped clean up some logic: Adds MOUNT: 'mounted' event to unmountSuspended state since users should be able to re-mount during the animation/transition phase.
Updates Checkbox.stories to more explicitly target states for styles as described above.

Can you also give me an overview of what we're trying to achieve with the refactor otherwise?

I'm trying to reduce the amount of code that executes inside the waitForNextFrame stuff because we didn't need it all in there and the more we can reduce delayed code, the better. Doing this uncovered some issues elsewhere so I've added/removed/moved code to fix those. Let me know if you wanna have a quick call to go over this in more detail 🙂


Removed call to _filter_params_keys in create_tree

I had a go at refactoring _filter_params_keys to filter arrays inside of hashes, but it was a bit hairy. Better to get this API function working at first and then work out a solution for filtering keys.

Right, I have refactored _filter_params_keys helper to work on arbitrarily nested hashes including array values. I've also added specs for blobs and trees apis as well as done some manually testing which results are documented in a wiki page.
The current github_api -v 0.3.8 should work for you.
Best
Piotr

Right, I have refactored _filter_params_keys helper to work on arbitrarily nested hashes including array values. I've also added specs for blobs and trees apis as well as done some manually testing which results are documented in a wiki page.
The current github_api -v 0.3.8 should work for you.
Best
Piotr

Thanks! I'll give it a try and let you know if I find any problems.

Thanks! I'll give it a try and let you know if I find any problems.


PreventGradients in SoftmaxCrossEntropyWithLogit ops

SparseSoftmaxCrossEntropyWithLogits cannot take second order gradients (It's not a beautiful hack, and I am not sure how much computational speed up it will bring).
Adding PreventGradient node in the gradient graph seems to contaminate the computation graph structure, e.g. I am doing custom forward-mode automatic differentiation.
Reference: https://github.com/tensorflow/tensorflow/blob/r1.0/tensorflow/python/ops/nn_grad.py#L334

@renmengye I am not sure what you are asking? Is the node preventing from attempting autodiff?
CC: @vrv

For example, I cannot take tf.gradients() on a gradient node to compute second order derivatives.
y = sparse_softmax_cross_entropy_with_logits(logits=z, labels=y_)
grad_z = tf.gradients(y, z)
grad_grad_z = tf.gradients(y, grad_z) # This returns [None], thus no second order derivative can be taken.

@girving any ideas?

The solution is to port the trick from the nonsparse case (https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/nn_grad.py#L393).

I'm trying to port the nonsparse solution to this case. Seems easy enough for my first contribution :)

This had to be rolled back, unfortunately, because in eager mode the gradient computation accidentally inserts hessian gradients as it can't tell that the input op is a Zeros or ZerosLike.  We'll have to fix this first.

We have an internal solution for better handling of second derivatives with tf.custom_gradient; will try modifying the non-sparse xent gradient to use that and report back here.

Thanks, @ebrevdo! Any updates on second derivatives with tf.custom_gradient?

@renmengye,
I can see there are multiple PR's raised and merged for this feature. With the PR's #22231 and #31553, the changes were happened and again those were rolled back because in eager mode the gradient computation accidentally inserts hessian gradients as it can't tell that the input op is a Zeros or ZerosLike.
With the PR #31700, the Hessian was implemented for the sparse softmax cross entropy and also find the changes in the nn_grad.py file
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/nn_grad.py#L539
Thank you!


Several ListView related issues

Currently the ListView has several issues.
The Items property cannot be used to set items (e.g. directly within XAML). Binding the ItemsSource seems to feed in items which can also be seen on the Items collection then.
ItemsPanelTemplate seems to be ignored. The list view ignores for example the stackpanel as configured below. (Running on Windows 10 the list view has exactly the 200 pixels height. Under Android it's always just the space required by the items.
<ListView.ItemsPanel>
   <ItemsPanelTemplate>
      <ItemsStackPanel Orientation="Vertical" Height="200" />
   </ItemsPanelTemplate>
</ListView.ItemsPanel>

In general I did not yet get any of my existing code working at all. I have styled item containers, etc. and my list view does not even get a size. Got only green field projects with simple list views working. :(
Tested on Android.

Just a note that ItemsStackPanel and ItemsWrapGrid are 'special' panels in Uno, as described here. Their properties are forwarded to the native ListView layouters on each platform; they don't actually exist in the visual tree.

ItemsContainerStyle should be working, but UWP seems to implicitly template-bind the Content to the ContentPresenter, which Uno doesn't do. You need to add 'Content="{TemplateBinding Content}"' like so:

<Style TargetType="ListViewItem" x:Key="TestListViewItemStyle">
				<Setter Property="Template">
					<Setter.Value>
						<ControlTemplate TargetType="ListViewItem">
							<ContentPresenter Content="{TemplateBinding Content}" />
						</ControlTemplate>
					</Setter.Value>
				</Setter>
			</Style>

Deriving from ListView is supported, but you run into a general limitation with derived controls in Uno which is that they don't currently detect the default Style of the base class. As a workaround, you can copy-paste the default ListView style from here and use it as the default Style for your derived class (changing the target types of the Style and the template).

@Dissolute That's what my ItemContainerStyle already looks like... there seems (again) to be unexpected  behavior. I reduced my XAML to a minimal sample (listview with item container style having the contentpresenter on red background, data template with just a text box on blue background)
What I discovered: If I set the item container style, the item template is ignored (red background), without container style I get the blue items.

Yes, I forgot to mention that ContentTemplate (and ContentTemplateSelector) have the same limitations. You actually need the following:
<ContentPresenter Content="{TemplateBinding Content}"
				  ContentTemplate="{TemplateBinding ContentTemplate}"
				  ContentTemplateSelector="{TemplateBinding ContentTemplateSelector}"/>

Nope, container remains red, still no blue content for my items. :(

@queequac could you share a sample of what you're trying to achieve, using the quickstart sample as a base ?

@jeromelaban Finally got it working, was some fault in my sample. So ItemContainerStyle seems to work. Sorry for the confusion. :)


Solution-Code-for-Sorting-the-Sentence-Problem

Hi @saurabh47 @maheshmnj ,
Thanks for accepting my previous contribution, looking forward to make more in future. Kindly please merge this pull request as well.


README-tr.md

Can you add it?

[Further suggestion]
https://github.com/kubernetes/website/blob/main/README.md
[As-is]
## Localization `README.md`'s

| Language                   | Language                   |
| -------------------------- | -------------------------- |
| [Chinese](README-zh.md)    | [Korean](README-ko.md)     |
| [French](README-fr.md)     | [Polish](README-pl.md)     |
| [German](README-de.md)     | [Portuguese](README-pt.md) |
| [Hindi](README-hi.md)      | [Russian](README-ru.md)    |
| [Indonesian](README-id.md) | [Spanish](README-es.md)    |
| [Italian](README-it.md)    | [Ukrainian](README-uk.md)  |
| [Japanese](README-ja.md)   | [Vietnamese](README-vi.md) |

[To-be]
## Localization `README.md`'s

| Language                   | Language                   |
| -------------------------- | -------------------------- |
| [Chinese](README-zh.md)    | [Polish](README-pl.md)     |
| [French](README-fr.md)     | [Portuguese](README-pt.md) |
| [German](README-de.md)     | [Russian](README-ru.md)    |
| [Hindi](README-hi.md)      | [Spanish](README-es.md)    |
| [Indonesian](README-id.md) | [Turkish](README-tr.md)    |
| [Italian](README-it.md)    | [Ukrainian](README-uk.md)  |
| [Japanese](README-ja.md)   | [Vietnamese](README-vi.md) |
| [Korean](README-ko.md)     |  |

/check-cla

Hey there! @AdemCanCertel, looks like you haven't signed the CLA yet. Could I please have you do that? https://github.com/kubernetes/community/blob/master/CLA.md

/check-cla

We need a signed CLA to accept proposed changes, including to review them.
I can say that we don't yet have a Turkish localization team so there would be a second barrier after the CLA as well.
@AdemCanCertel if you wanted to start a Turkish localization, SIG Docs can help you. A localization team is always a minimum of two people.
/close


Sensitive content reporting flow guidelines

Start Date
Project Lead
Actual Ship Date

2023-02-13
@sarayourfriend
TBD

Description

This project creates the sensitive content reporting flow guidelines.
Documents

[x] #1176
[ ] #1965
[ ] #1966
[ ] #1967
[ ] #1968
[ ] #1969
[ ] #1970

Prior Art

Required work to enable the DAG for reported media pending review created at WordPress/openverse-catalog#513. I noticed it hadn't run yet.

@AetherUnbound has started on the first implementation plan for this project. We probably need to get the next implementation plan also started. The project proposal shows that the API cache management and the initial Django access control implementation plans can be started at any time. If any @WordPress/openverse-maintainers do not currently have an implementation plan they are working on or can take on a new one, please volunteer for one of the ones for this project.
I will start working on https://github.com/WordPress/openverse/issues/1969 next week.

#2126 is pending review from the requested reviewers, @dhruvkb and @krysal. @zackkrida given the delay, do you think it's appropriate for my review of the implementation plan to serve as one of the two approvals for go ahead? @dhruvkb and @krysal, can y'all share an ETA of when you'll be able to review the implementation plan? It's been in the decision round much longer than the expected time span.
I was going to start working on the #1969 IP, but that hasn't happened due to recent incidents and high priority retrospective items taking up lots of time followed by MSR. I hope to be able to start that implementation plan next week.
The recent Redis memory consumption issue has brought to attention that the fine-grained cache IP will need to consider Redis memory usage.

After starting to work on the fine-grained cache implementation plan, I opened a discussion about our approach to caching generally: https://github.com/WordPress/openverse/discussions/2453
In that discussion we've decided to explore significantly reducing our cache TTL, potentially low enough such that needing fine-grained cache invalidation on the search endpoint would no longer be necessary. Therefore, I will stall work on the implementation plan to further investigate how changes to the cache will effect performance, especially Elasticsearch and Postgres resource consumption. This is possible now that the thumbnails service is live and we have confirmed that API instability was due almost entirely to long-running thumbnails requests.
Other implementation plans may move forward, such as the Django admin access control and baseline changes, which would unblock several other implementation plans.

This project is currently on hold, but I've created the issues associated with the first IP for this work as part of this milestone: https://github.com/WordPress/openverse/milestone/18

The project has been on hold since we started to consider the data dump project. That's done now and we've reprioritised it. I still need to catch up on how the remaining implementation plans will be prioritised, in particular, but we're also waiting to get clarification on who will work the moderation queue specifically and to confirm that Django Admin, rather than needing to integrate with some other tool, is fine.

The implementation plans are still being prioritised. We've made no further progress that I am aware of.

Apologies for the lack of updates here. The project was essentially on hold during the API response time mitigation work. The implementation plans are still in the todo column with no further progress other than https://github.com/WordPress/openverse/issues/1967 is now assigned (:tada:).
I closed #1969 with an explanatory comment. I'll share a proposed alternative next week for us to consider. I chose to close the issue to avoid anyone picking it up and working on the implementation plan, just in case it ends up not being the direction we choose. Closing the issue should not be taken as an indication that the plan is changed now. I'm just trying to be cautious about accidentally planning complex work that we wouldn't end up needing. I don't expect this to delay things because the other parts of the project are at times more significant (like the underlying Django admin changes to support a moderation queue to begin with).
By the way, @stacimc, the implementation plan you've picked up is tightly related to https://github.com/WordPress/openverse/issues/1966. I'd suggest re-reading the relevant part of the project proposal if you haven't yet just to make sure the scope of the bulk moderation plan is clear to you (please ask for clarification if not) and that the planned implementation is flexible enough to fit into whatever Django admin tools we build to execute the bulk moderation actions.

Access control and basic feature implementation plan is ready to go! The milestone with issues is here: https://github.com/WordPress/openverse/milestone/22

Staci's bulk actions implementation plan got approval, and she's merged it and created new and updated existing issues to reflect the plan in the IP.
Dhruv's IP for moderation metrics is still under review, awaiting a response from @AetherUnbound, who hasn't commented yet on it: https://github.com/WordPress/openverse/pull/3760
Madison, can you add a comment in the PR clarifying when you'll be able to review the plan?

Dhruv's IP for moderation metrics is still under review, awaiting a response from @AetherUnbound, who hasn't commented yet on it: #3760
Madison, can you add a comment in the PR clarifying when you'll be able to review the plan?

I was originally randomly assigned as a reviewer when @dhruvkb initially opened the PR. I was expecting for Dhruv to provide some explanation on why reviewers were chosen (as is typically done for IPs) and had ignored the PR while he continued to work on it. While I was team lead, I didn't believe I had the capacity to be an IP reviewer, so I was not expecting to be assigned review in general. I probably should have removed myself initially when the random assignment chose me, apologies for not doing that. @dhruvkb would you still like me to be an reviewer for that IP? I can try to prioritize it over the next day or two if so. Also, do you mind updating the PR description for it to use the proposal template so we can see the project-related information there?

Work on the moderation decision and new admin views is underway, with https://github.com/WordPress/openverse/issues/3634 recently closed to add the new admin view for user preferences.
We've also continued discussions behind the scenes regarding who will do the moderation. It is my understanding we have an answer on this question, but I'll ping @zackkrida here to clarify if that is the case. If we now have a definitive answer, do you think it's worth documenting that in this project thread?
I've been focused almost exclusively on https://github.com/WordPress/openverse/issues/2037, but folks have been picking up issues and reviewing IPs here and there. We only have one IP left to write for this, and once the openverse.org migration for the API and Airflow is finished, I'll be able to put some more time towards helping implement this project.

We've also continued discussions behind the scenes regarding who will do the moderation. It is my understanding we have an answer on this question, but I'll ping @zackkrida here to clarify if that is the case. If we now have a definitive answer, do you think it's worth documenting that in this project thread?

We don't yet have an answer but should by the end of this month. I will update the project thread here and ping you when that occurs!

@sarayourfriend We will move forward with a sub-set of volunteers from @WordPress/openverse-maintainers handling content moderation.

Apologies for missing an update on this.
@dhruvkb's got a very cool PR for the "locking" of reports, so that moderators know when someone is reviewing a work or not: https://github.com/WordPress/openverse/pull/4374
I also opened a related issue, that will sit outside the project, for us to consider different ways of logging into Django admin that could make user management and permissions a bit easier: https://github.com/WordPress/openverse/issues/4342. That is out of scope for this project, and we do not realistically need, nor would benefit from all that complexity. The plan right now does not involved a large number of moderators, nor would they change often, so we don't benefit from making user management overall easier, if the underlying implementation is complicated.
I intended to start working on some issues for this project this week, but got pulled away to things related to an API incident. Hopefully I'll wrap those up early next week and be able to work on some of the issues from this milestone: https://github.com/WordPress/openverse/milestone/22
Krystle's picked up the computer vision labelling implementation plan. Looking forward to seeing that one, especially with the ongoing work in #431 in the works.

To reduce scope and help make more time/room in our schedule for projects important to search, we're cutting the computer vision and metrification aspects of this project. They were always considered "nice to have", and while I'm disappointed @dhruvkb's IP for the metrification part won't be implemented right away, the work is planned and available for us to work on later. It is less critical now that we know who will be doing the moderation. The visibility we'll have with the basic features after we've implemented bulk moderation will be more than sufficient to ensure reports are reviewed in a timely and consistent manner, as monitored by the moderators themselves (following self-accountability, if it needs to be more explicit).
The computer vision aspect would also be nice to have, and a continuation of #4040, but ultimately not necessary for MVP.

@zackkrida do you think we should close the issues in the milestone, or leave them as is?

I've just peeked at the milestones for the project. I closed the IP milestone, and the two remaining milestones look to contain the correct issues.
Django admin access control and basic functionality changes: WordPress/openverse/milestone/22
Bulk moderation actions: WordPress/openverse/milestone/24
Perhaps you've already made changes, @sarayourfriend? In any case, it all looks good to me.

I meant specifically about the metrification issues. There are only three, and they're arguably unnecessary with the current plan of who will do the moderation. I'll close them as won't do for now, and we can revisit our needs in the future once we actually need it.

Ah thanks! I saw that those weren't part of the project's milestones so figured they'd be acceptable to keep as low priority for a rainy day, but you're totally right given our set of moderators.

Oops! I thought I'd left an update here two weeks ago! Apologies.
A single issue remains in the initial milestone, https://github.com/WordPress/openverse/issues/3640, assigned to @dhruvkb. That one does not block work on the bulk moderation issues, so we could start on those issues as soon as we like.
The backfill had one small issue with foreign keys, fixed in https://github.com/WordPress/openverse/issues/4512. We ran it in production, and have now dropped the status column in production. The new model for report decision tracking is fully operational!

@dhruvkb do you mind contributing this update while @sarayourfriend is AFK?

Issue #3640 from milestone https://github.com/WordPress/openverse/milestone/22 has an associated PR #4603, that has been reviewed by @sarayourfriend and the changes that Sara requested have been addressed. Since Sara is AFK, I have requested a review from WordPress/openverse-api team.
Also I have started working on issue #3840 from milestone https://github.com/WordPress/openverse/milestone/24 and a PR for that will be up very soon.

All milestones for this project have now been completed, so the project has been moved to the "🚢 Shipped" column.

@WordPress/openverse-maintainers this project will be marked a success after the tooling has actually been used in a two-week trial by the sub-group of maintainers who will perform moderation.
Feedback from this trial may inform further improvements or changes.

It would be great to split feedback between bugs with the functionality implemented for this project and with iterative improvements and additional features, just so we don't accidentally expand the scope of this project beyond its original goals for the foundational functionality.

@zackkrida do you know when the two-week trial will start, and if so, can you share the details here? If not, how can I help get that moving forward?
Nothing to add in the way of an update beyond that, though.

@sarayourfriend given upcoming team AFK and travel, I think the trial should take place from October 14-25th.
Additionally, I think we should stop sending reminder pings for shipped projects:
https://github.com/WordPress/openverse/issues/4912

See https://github.com/WordPress/openverse/issues/383#issuecomment-2344133502
Also, I opened a PR to stop these pings on shipped projects as suggested by Zack: #4993.


[Feature request] Option to 'show only key-values with different values' when using Compare tool

Currently there is only the option to 'Show key-values with different content only'. This isn't helpful when comparing across labels because it shows all the key-values as having different 'content' because the labels are different.

Thank you for reporting this issue. The fix is already in progress.
Closing as duplicate of issue#457


modifies ORT to correctly parse api 1.3 for revalidation.

Updates ORT to work with the revised 1.3 update status API.  If the use_reval_pending flag is not present, reverts to the UI code update page.
Requires https://github.com/apache/incubator-trafficcontrol/pull/2157.

This is updated to not worry about backwards compatibility and only checks to be sure the updated 1.3 api is present.  If not found, it exits.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1463/
Test PASSed.


docs: Remove ansible and terraform line

Description

docs: Remove ansible and terraform line
Removes Ansible and Terraform mentions as means to integrate with ecctl,
since it's a confusing statement.
Related Issues

Resolves #261
Types of Changes

[x] Documentation

Closing in favor of #264


US 02.03.01

As an owner, I want to select items from the list of items and delete the selected items.
Requirements/Prerequisites:

US 02.01.01: At least a partial implementation of a display list must already be in place
Long-touch on any item activate multi-select
Multi-select must have a slightly different view from standard list display with indicators on each item for if it is selected
Delete button must appear on bottom left
After pressing delete all items selected must be removed from view and from the database
There must also be a cancel button in the bottom right which will go back from multi-select view to regular list view
Finally there must be a space left for a tag select element in the bottom middle, this does not need to be implemented but there should be a dummy element for the layout.

Need to potentially readjust the inventory list item xml, currently I did a basic implementation that also works

I added the multi delete function, however there is a bug, whenever you delete all items, with the list having more than two items, the oldest item will reappear in the view but not be present in the database.
Please help!

Bug fixed just write a unit test and you are done

Multi delete has a test, however selection and canceling needs a custom matcher to check for background colour in the item list, however if we decide to change or revise or implementation of selection it will not require this matcher


chore(go): rename jsii-experimental directory to jsii-runtime-go

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: c47e8dce8436cca942b50b63d394124a85c70295
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: c47e8dce8436cca942b50b63d394124a85c70295
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: fb90d4c3707d93f121d8b3e22ae827389cb80d1d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: fb90d4c3707d93f121d8b3e22ae827389cb80d1d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 7e8f77ca3cafcea057f9cbdf383ddba7f6441a22
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 7e8f77ca3cafcea057f9cbdf383ddba7f6441a22
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Chapter 4 - database output

I didn't see any reference to this in the chapter, but after following the suggested exercise to move the mysql configuration into a module and deploy for prod (pg 116), the webserver-cluster deployments will fail as the address and port outputs aren't being called by the prod and stage configurations. You need to add an outputs.tf to both prod and stage configurations for mysql so that the webservice-cluster deployments can read the values from the mysql remote state.

Not sure I fully understand! The database module has an outputs.tf in chapter 3... If you add a staging DB, you should of course copy that outputs.tf. Is there something in the book that is suggesting otherwise or misleading?

Thanks, I think the confusion I'm seeing is mostly based off of the fact that the database module was mentioned as a bonus exercise, and this chapter is mostly focused on the webserver_cluster module. I do see a mention of the environment-specific outputs.tf on page 122, but I don't recall reading anywhere that the module's outputs.tf should be copied into the environment's directory. Maybe for future editions just having a note somewhere around this section to keep in mind that the Terraform State won't include any module outputs unless they're also added to the environment outputs could be helpful?

Thx for the feedback!

I do see a mention of the environment-specific outputs.tf on page 122, but I don't recall reading anywhere that the module's outputs.tf should be copied into the environment's directory.

If you want to have outputs available in your state, you must add output variables, which, by convention, live in outputs.tf.

Fair enough, I think I was over (or under) thinking it a little bit. I
appreciate the discussion!
On Tue, Dec 31, 2019 at 1:06 PM Yevgeniy Brikman<EMAIL_ADDRESS>wrote:

Thx for the feedback!
I do see a mention of the environment-specific outputs.tf on page 122,
but I don't recall reading anywhere that the module's outputs.tf should
be copied into the environment's directory.
If you want to have outputs available in your state, you must add output
variables, which, by convention, live in outputs.tf.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/brikis98/terraform-up-and-running-code/issues/44?email_source=notifications&email_token=ABYOBGUBWGHMGY7XWJJ36ZTQ3OC4HA5CNFSM4KABSIKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH4QJ4A#issuecomment-569967856,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYOBGWEYYRXC7W4Y2HN47DQ3OC4HANCNFSM4KABSIKA
.

I believe this issue was resolved. Closing.

For Googlers:
Error: Unsupported attribute
│
│   on ../../../modules/services/webserver-cluster/main.tf line 148, in data "template_file" "user_data":
│  148:     db_address = data.terraform_remote_state.db.outputs.address
│     ├────────────────
│     │ data.terraform_remote_state.db.outputs is object with no attributes
│
│ This object does not have an attribute named "address".
╵
╷
│ Error: Unsupported attribute
│
│   on ../../../modules/services/webserver-cluster/main.tf line 149, in data "template_file" "user_data":
│  149:     db_port = data.terraform_remote_state.db.outputs.port
│     ├────────────────
│     │ data.terraform_remote_state.db.outputs is object with no attributes
│
│ This object does not have an attribute named "port".

ch4/modules/services/data-stores/mysql/outputs.tf
output "address" {
  value = aws_db_instance.example.address
  description = "Connect to the database at this endpoint"
}

output "port" {
  value = aws_db_instance.example.port
  description = "The port the database is listening on"
}

ch4/stage/services/data-stores/mysql/outputs.tf
output "address" {
  value = module.data_stores.address
  description = "Connect to the database at this endpoint"
}

output "port" {
  value = module.data_stores.port
  description = "The port the database is listening on"
}


driver.context("Native_APP") no longer works in io.appium java-client 9.0

I changed the java-client version to 9.0.0 which was originally version 7.6.1 which previously could use driver.context("Native_APP") to change the apps context to native on Flutter apps. please tell me the changes in java client 9.0.0 to change the context to native
thanks.

Please attach the full appium server log. I guess you should set NATIVE_APP (case sensitive)
The client has migration guides.  They could help I guess.
https://github.com/appium/java-client?tab=readme-ov-file#v8-to-v9-migration
https://github.com/appium/java-client?tab=readme-ov-file#v7-to-v8-migration


Added ToS on outgoing packets

I added the ability to set ToS on outgoing packets.
It would be nice to get the received ToS but I think all should be ported on RAW socket to have the IP header.

Hi, yes as default value is zero.
Inviato da iPhone

Il giorno 5 feb 2019, alle ore 17:38, Ben Kochie<EMAIL_ADDRESS>ha scritto:
@SuperQ commented on this pull request.
In ping.go:

}

func (p *Pinger) sendICMP(conn *icmp.PacketConn) error {
var typ icmp.Type
if p.ipv4 {
typ = ipv4.ICMPTypeEcho

conn.IPv4PacketConn().SetTOS(p.Tos)

Is it the correct thing to do to set this to a default of 0x0 if there's no explicit setting?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks for the contribution @webfrank
I don't see any reason why not to merge this, but can I ask why you need the ToS header? From my experience this field is very rarely used. It also seems to have gone away in IPv6.

We've discussed this internally on our Slack channel a bit and have decided to close I'm afraid. The consensus was that it's doubtful anyone actually honours the TOS packet header seriously so there's little point in merging this.


Array Declaration in Python

Replicate the Array function in python

replicate all other relavant files as well, then and then i can merge it to main, along with that, try comparing your branch with main branch


How to run Huginn behind a proxy

I could configure my local server with Ubuntu 16.04 to run behind a system-wide proxy. In other words, if I run "curl ipinfo.io/ip", it returns my proxy server's public IP, not my public IP from my ISP.
But, when I run a Website Agent from Huginn, it could somehow bypass my system-wide proxy. I could confirm this by using a Website Agent to fetch, for example, "http://ipinfo.io/ip".
Any way that I can run Huginn behind a proxy?

Setting the HTTP_PROXY variable in your .env file should enforce all connection are going through that proxy.

Many thanks! This works!

Is there a way to make it easier? For example instead of re-exporting the .env just to put a http_proxy to the website-agent (similar to user_agent)? Thanks.

Add http_proxy instead of HTTP_PROXY. The HTTP_PROXY seems to be ignored by typhoeus which is the default FARADAY_HTTP_BACKEND in huginn.

Can we set proxy at an agent level? I'd like to only use the proxy with certain agents. (Yahoo Japan, who today blocked access to UK & Europe)

I don't know, I've never tried.  The only thing that comes to mind I'm afraid is using a Shell Agent calling wget or curl with the appropriate command line switches.

I read in another issue that you can simply use "proxy" key on the WebAgent, it works.


.Net ConversationSummary Plugin doesn't work for gpt-35-turbo-16k v0613

I have two Azure OpenAI model deployments, gpt-35-turbo v0301 and gpt-35-turbo-16k v0613. The ConversationSummary plugin works for gpt v301 but not v0613.
To Reproduce
This is the code I used for both models:
kernel.ImportPluginFromType<ConversationSummaryPlugin>();

string input = @"I'm a vegan in search of new recipes.
I love spicy food! Can you give me a list of breakfast
recipes that are vegan friendly?";

var result = await kernel.InvokeAsync(
    "ConversationSummaryPlugin",
    "GetConversationActionItems",
    new() {{ "input", input }});

Console.WriteLine(result);

Expected behavior
Expected the output to be the same between both models.
Output
Using v0613
{
    "actionItems": []
}

Same code using 0301:
{
    "actionItems": [
        {
            "owner": "",
            "actionItem": "Provide a list of vegan-friendly spicy breakfast recipes",
            "dueDate": "",
            "status": "Open",
            "notes": ""
        }
    ]
}

Platform

Windows
VS Code
C#, Python
Microsoft.SemanticKernel.Plugins.Core, Version=<IP_ADDRESS> (Also on Version=<IP_ADDRESS>)

@buzahid, it looks like this is an issue with the underlying prompt; we likely need to do some prompt engineering to make it work for the latest model. Would you be able to do some experimentation to see what the "correct" prompt should be for the plugin?

I'm the same issue. I can help experiment with different prompts if you still want to do that.

I experienced the same behavior (i.e. the empty actionItems array) while I was following the same Learn content already mentioned.  Since I'm new to SK, it really confused me and threw me for a loop.  I didn't know if I had done something wrong or otherwise.  I was never able to make it work, not on gpt-35-turbo v0301 or gpt-35-turbo-16k v0613.  I'm using Microsoft.SemanticKernel.Plugins.Core 1.10.0-alpha.
Can we fix either the plug-in or the Learn content?

confirming @buzahid above - i had a project and  kernel.InvokeAsync returning empty action items - created new deployment using model gpt-35-turbo which was (at the time of this writing) ver 0301 and my code worked. I suspect if you do same, you code above will work as well.

The issue is still present using current prerelease version 1.13.0-alpha of package Microsoft.SemanticKernel.Plugins.Core and current default version 0613 of model gpt-35-turbo-16k.
I have raised an issue for learning module Create plugins for semantic kernel on Microsoft Learn, suggesting to substitute function GetConversationActionItems with function GetConversationTopics for the purpose of the exercise to not throw off students by this issue.

I encountered the same problem. When I tried to look into the root cause, I found the problem actually was related to the prompt.
The prompt was more used to understand the chat style conversation, unlike the one mentioned in the problem description:
I'm a vegan in search of new recipes.  I love spicy food! Can you give me a list of breakfast  recipes that are vegan friendly?
(Which is btw also being used in one if the MS learning path code samples)
I have initiated this PR with the improvement in prompt.
it became a bit tricky, as it also tried to extract action item from simple statements. For example, for given input I'm a superhero. I go out for super walk. It started extracting going out for walk as action item. Hence I had to add "Guidelines" section in prompt to counter that

Fixed via https://github.com/microsoft/semantic-kernel/pull/6722


Screen goes black after display change on Windows 10

While on any screen, whether its ScreenGameplay or ScreenSongSelect, if another monitor is disconnected or connected or a screen resolution change happens on any monitor, Etterna will show a blank screen until the game is restarted. Etterna can still receive input from any device and gameplay can still happen, but there is no video output in the window. This does not happen on stock StepMania 5 so it is not a game engine related issue. This will only happen on Etterna.

This can be fixed on the fly by toggling fullscreen and windowed with alt+enter or some other combo.


Assign User Rights

File Location:
https://github.com/aldefouw/redcap_cypress/blob/master/cypress/integration/core/pre-requisite/assign_user_rights.js
Task:
Write the test specs as outlined in manual test script
Please see CORE Validation Test Scripts project for more info:
https://github.com/aldefouw/redcap_cypress/projects
Contact Adam De Fouw<EMAIL_ADDRESS>with any questions.

On my machine, this test intermittently fails.  I think what we might want to institute is some cy.wait() functoinality that monitors an intercepted route using cy.intercept().

Still need to finish these:
https://github.com/aldefouw/redcap_cypress/blob/v9.1.3/cypress/integration/core/pre-requisite/assign_user_rights.js#L83-L97
https://github.com/aldefouw/redcap_cypress/blob/v9.1.3/cypress/integration/core/pre-requisite/assign_user_rights.js#L191-L201


Missing keyed

Love this lib, pairs awesome with S.js.  I am not getting keyed.js when I do a yarn add stage0.   Any ideas?

Is it latest version?
I just checked and everything is there.
yarn could cache some old version, you should try to update stage0 to the latest one
https://yarnpkg.com/lang/en/docs/cli/upgrade/

Holy cow, for some reason I was working on a really old version of stage0 0.0.2!   Didn't check my package.json before submitting this.   This, not sure how that happened.  Again, thanks for the awesome lib!

You're welcome)


OSX Crash when creating a Tray icon

Using the latest (0.21.3) Darwin release, I'm getting an app crash if I try to create a Tray icon
var Tray = require("tray")
global.tray = new Tray(path.join(__dirname, "images/gtray.png"));

Is the offending code - png exists - NOT using asar - suspect this is a pathing issue tho???
Crash looks like this (no idea how to cut/paste/save that on OSX) - and yes, that's a Hackintosh cos I don't own a Mac - but remove those 2 lines and it works OK (as does the default_app)
https://dl.dropboxusercontent.com/u/1164739/osxcrash.png
Error is a generic 'Error (1000) creating CGSWindow' - NSException NSInternalInconsistencyException etc.
If I can provide more details and someone more OSX savvy can tell me how to get the whole report/dump - that would be awesome - and perhaps how to path to Tray
Demo project here
https://github.com/shrewdlogarithm/atom-shell-crash-demo

Just a thought: Try it without setting it to a global object. tray = new Tray( ...

Doesn't fix it here - I removed the path.join(__dirname bit and got a
different error entirely (not a crash, a JS error) but I cannot seem to
fathom what directory it wants (and I think the crash happens when it
actually DOES find the file!) ??
On 11 March 2015 at 13:29, Benjamin Winkler<EMAIL_ADDRESS>wrote:

Just a thought: Try it without setting it to a global object. tray = new
Tray( ...
—
Reply to this email directly or view it on GitHub
https://github.com/atom/atom-shell/issues/1237#issuecomment-78262330.

From reading your answer I'm not sure if you knew what i meant:
~~global.~~tray = new Tray(path.join(__dirname, "images/gtray.png"));
If you've tried that, please ignore this comment.

This doesn't have to do with anything, just wanted to let you know: In your atom-shell-crash-demo in main.js on line 17 you have ... true: false});

Fixed the silly true: false thing - still unsure how to proceed with the Tray tho, I'm pretty sure the crash is because I have the RIGHT path to the icon (and without it, no Tray?)

thats cause of NSApplication event loop wasnt setup, initialise either on will-finish-launching or ready . @zcbenz should this be a bug ?
app.on('will-finish-launching', function() {
	global.tray = new Tray(path.join(__dirname, "images/gtray.png"));
})

@deepak1556 We should throw error when users try to create Tray before ready event, like BrowserWindow.


Bazel Build Issue

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Kubuntu 20.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): Source
TensorFlow version: 2.3.1
Python version: 3.8
Installed using virtualenv? pip? conda?:
Bazel version (if compiling from source): 3.1.0
GCC/Compiler version (if compiling from source): 8.4
CUDA/cuDNN version: 11.1/8
GPU model and memory: 2070 / 8GB

Describe the problem
Trying to install tensorflow from source, I get the following error
ERROR: /home/pablo/.cache/bazel/_bazel_pablo/73a3c430b087017173c0bbcfb3b9758b/external/llvm-project/llvm/BUILD:1852:1: C++ compilation of rule '@llvm-project//llvm:Core' failed (Exit 1)
external/llvm-project/llvm/lib/IR/Function.cpp:46:10: fatal error: llvm/IR/IntrinsicsVE.h: No such file or directory
#include "llvm/IR/IntrinsicsVE.h"
^~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 64.162s, Critical Path: 26.84s
INFO: 593 processes: 593 local.
FAILED: Build did NOT complete successfully
Provide the exact sequence of commands / steps that you executed before running into the problem
Tensorflow configuration went ok, no problems. I compile with Bazel, and I get the error: bazel build --config=cuda //tensorflow/tools/pip_package:build_pip_package
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Can you clone again please? It is likely you have cloned at a time when LLVM dependency (coming via MLIR) broke us.

Yes, it works now, thank you!

@parayamelo,
Thank you for the update. Marking the issue as closed, as it it resolved. Please feel free to re-open the issue if necessary.


Use journey category and number instead of name, to see bus numbers and such

Hi! Thanks for this application! I'm using it all the time on my "Librem5".
I thought the journey name never appears to show useful information (every time I tried it was a string of numbers like 06823), but category+number is much more useful. Category says whether it is a bus, a train, a tram, or which kind of train (IC, R, S, ...). And number is really important when taking a bus because there are no platform numbers at bus stations.
Cheers!

Thanks for the contribution. I merged a slightly modified version of your PR with 22b795584fabff28b7ccfcd0a614ec7936c025bb into main.


Sandbox Site is not showing images (404s)

Issue Summary
When visiting the Sandbox site some of the images are returning a 404
Steps to Reproduce

Visit https://latest.oscarcommerce.com/en-gb/catalogue/
Notice most of the images are missing
Open up the Javascript Console and you will 404s

The site should load images and not show 404s. ;)

Nice.  Thanks!


Isloated Currency Reserves

Currency reserves/unreserves are not isolated.
This means modules can potentially interfere with each other's reserved amounts creating various bugs.
https://github.com/cennznet/cennznet/issues/421

There's no timeline on the substrate trait change afaik.
Urgency here is that we need the separation of reserved balances to happen before more modules start reserving/unreserving things. after that a migration to another approach will be straightforward


CueLang

Your code is a little bit low code type of architecture.
I was thinking about also using Cuelang with it.  This would mean that you dont have to have types everywhere.
Types can be used at runtime. But you can also generate JSON, YMAL, OPENAPI, and a ton more things with Cue.
https://cuelang.org/
https://cuelang.org/docs/usecases/ is a good place to start.
https://github.com/cue-lang/cue is golang ... Its even has the equivalent go.mod and go.sum.. Its really cool.
There are a ton of golang coders using it around github etc.
https://github.com/cueblox/blox
https://github.com/eonpatapon/tree-sitter-cue

How do you see that being used within this project?

Closing due to inactivity.


Task retries without until parameter

Proposal:
Author: Rastislav Barlik <@barlik>
Date: 2018-07-20

Status: New
Proposal type: core design
Targeted release: 2.7
Associated PR: https://github.com/ansible/ansible/pull/43128
Estimated time to implement: already done

Motivation
Make task retries simpler and more intuitive. I've recently used URI module to write tens of API calls all of which needed a couple of retries and I've realized that every task has a register: out and until: out is successful parameters although I don't really need the out variable.
Problems
Task retries parameter is silently ignored when until parameter is not specified. Until parameter is not always needed so using just retries parameter should be enough for some tasks.
What problems exist that this proposal will solve?

I want to retry a task until it succeeds and don't want to write extra register and until parameters.

Solution proposal
Allow to omit until parameter from a task and still respect retries parameter. The task will be retried specified amount of times until it is successful.
    - name: Retry URL call up to five times until we get 200 status code
      uri:
         url: https://httpbin.org/ip
         status_code: 200
      retries: 5

The above example looks correct, but at the moment it will only ever run once as retries parameter is silently ignored because there's no until parameter. To make it work as expected we need to add:
      register: uri_call
      until: uri_call is successful

which seems unnecessary and moreover registers an extra variable that is not needed.
Testing (optional)
Unit tests to verify expected behaviour.
Documentation (optional)
The documentation update is needed.

If it was up to me (see #30957), this would be possible:
    until: this is successful

@dagwieers That's not a bad suggestion. I would still prefer until: this is successful to be implicit though.

discussed in IRC meeting and we all agree on proposed feature, comments on implementation in PR incoming.

Any updates?

Implemented in https://github.com/ansible/ansible/pull/81531


Food explorer error

Error in food explorer on buildkite
File "/var/lib/buildkite-agent/builds/etl-build-1-10/our-world-in-data/etl-full-private-rebuild-nightly-master/etl/steps/data/explorers/owid/2021/food_explorer.py", line 631, in <module>
--
  | & (population_gap.year >= dates["min"])
  | File "/var/lib/buildkite-agent/builds/etl-build-1-10/our-world-in-data/etl-full-private-rebuild-nightly-master/.venv/lib/python3.10/site-packages/pandas/core/ops/common.py", line 72, in new_method
  | return method(self, other)
  | File "/var/lib/buildkite-agent/builds/etl-build-1-10/our-world-in-data/etl-full-private-rebuild-nightly-master/.venv/lib/python3.10/site-packages/pandas/core/arraylike.py", line 62, in __ge__
  | return self._cmp_method(other, operator.ge)
  | File "/var/lib/buildkite-agent/builds/etl-build-1-10/our-world-in-data/etl-full-private-rebuild-nightly-master/.venv/lib/python3.10/site-packages/pandas/core/series.py", line 6243, in _cmp_method
  | res_values = ops.comparison_op(lvalues, rvalues, op)
  | File "/var/lib/buildkite-agent/builds/etl-build-1-10/our-world-in-data/etl-full-private-rebuild-nightly-master/.venv/lib/python3.10/site-packages/pandas/core/ops/array_ops.py", line 287, in comparison_op
  | res_values = comp_method_OBJECT_ARRAY(op, lvalues, rvalues)
  | File "/var/lib/buildkite-agent/builds/etl-build-1-10/our-world-in-data/etl-full-private-rebuild-nightly-master/.venv/lib/python3.10/site-packages/pandas/core/ops/array_ops.py", line 75, in comp_method_OBJECT_ARRAY
  | result = libops.scalar_compare(x.ravel(), y, op)
  | File "pandas/_libs/ops.pyx", line 107, in pandas._libs.ops.scalar_compare
  | TypeError: '>=' not supported between instances of 'str' and 'int'

To reproduce
subprocess.CalledProcessError: Command '['prlimit', '--as=17179869184', 'poetry', 'run', 'run_python_step', 'data://explorers/owid/2021/food_explorer', '/var/lib/buildkite-agent/builds/etl-build-1-10/our-world-in-data/etl-full-private-rebuild-nightly-master/data/explorers/owid/2021/food_explorer']' returned non-zero exit status 1.

False alarm.


move ContainmentMode to h3api.h

fixes #956

coverage: 98.784%. remained the same
when pulling fdf1370c909953723e874452139a2e0d45379357 on isaacbrodsky:move-mode-enum-public
into d5af2344e0fac9bad0f13cba66cb5d1b8f1c87ac on uber:master.


Refactor open interest and oi shares reduction

liquidate() and unwind() functions share a considerable amount of code. This PR creates an internal function to avoid these duplicates. Thanks Uncle Bob.
Merge after #133

pending tests

Used brownie test for this PR since its a refactor and not a new feature.


Add missing \ for InputLegacyModule path in csproj file

Describe the bug
There is a missing \ in the path for the InputLegacyModule in the csproj file.  This prevents building this cloned repo on a separate computer.
Expected behavior
Include a \ so the path is correct.

Resolved in commit 31f38f1b7b95b500ebb61a3653639306a8949fae.


Remove dependency on SharpZipLib

Fixes #2735

It's difficult for no reason to track changes when functions are completely removed and then added back in later with an additional obsolete tag. The solution that @bdukes started was much cleaner for the removal of SharpZipLib.

Nah, I am good with it, my concern was with build packaging, but that part is not distributed, so good to go.


[EMB-233] Updates for accessibility

Purpose
Eliminate the majority of the remaining a11y linting errors, and hopefully all of the errors that aren't embedded in third-party components.
Summary of Changes
In short: Make things more contrasty, add labels, and add roles.

Add aria labels to quickfiles file-browser filtering controls
Make the color of the mfr file download url darker
Change quickfiles file-detail sharing popup tabs to buttons, because ember-bootstrap doesn't seem to have the supporting parent container role working properly
Add aria labels to most of the things in the quickfiles file-detail sharing popup
Make the institutions carousel tab-index equal to 0, because the tab-index of a carousel can't be greater than 0
Make the placeholder text darker on the new project modal
Make the aria labels for social icons in the footer i18n compliant (oops)
Add menuitem roles to the menu items in the navbar
Un-mute the text in the project selector's project select text
Instead of making the h3 element effectively empty before we know the user's name, don't add the element until we have a name (the rendering flash isn't terrible)
Override ember-power-select's placeholder text color
Move the variables.scss to the top of the app.scss so that it can override variables lower down
Upgrade ember-a11y-testing to 0.5.1, which upgrades the axe package to fix one of the other things I couldn't do from my original PR.
Add translation strings for all the new labels

Side Effects / Testing Notes
Moving the variables so that they actually override things may cause some CSS color changes that weren't active before to become active. There are less invasive ways to do this, but I think this is the proper way, and I didn't see weird color changes.
Ticket
https://openscience.atlassian.net/browse/EMB-233
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] ~changes described in CHANGELOG.md~

Coverage decreased (-0.02%) to 54.363% when pulling 8f2e713b2d8597a22e39b2f0d1c3b1d16f1be17b on brianjgeiger:feature/more_accessible into a3d3ea88aa5363ecdfbba4ef1665b52b86085881 on CenterForOpenScience:develop.


unityhub: cannot create new project

Describe the bug
I installed the Unity game engine through the Unityhub program. However, when creating a new project, the hub closes/crashes.
I cannot find a way to actually create a project and use unity. The engine cannot be started without creating a project first.
Steps To Reproduce

Install unityhub
Login and download 2022.1.23f1
Create a new project

Expected behavior
A new project gets created and the engine opens.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
❱ unityhub-2.3.2
Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
Checking for update
Found version 3.4.1 (url: UnityHub.AppImage)
Downloading update from UnityHub.AppImage
updater cache dir: /home/me/.cache/unityhub-updater
No cached update info available
Error: Error: APPIMAGE env is not defined
    at newError (/nix/store/ywdfa4rmvnnjkqzxy0x97g05nbygzf00-unityhub-2.3.2-extracted/resources/app.asar/node_modules/builder-util-runtime/out/index.js:212:17)
    at Object.task (/nix/store/ywdfa4rmvnnjkqzxy0x97g05nbygzf00-unityhub-2.3.2-extracted/resources/app.asar/node_modules/electron-updater/out/AppImageUpdater.js:106:52)
    at AppImageUpdater.executeDownload (/nix/store/ywdfa4rmvnnjkqzxy0x97g05nbygzf00-unityhub-2.3.2-extracted/resources/app.asar/node_modules/electron-updater/out/AppUpdater.js:741:25)

Notify maintainers

@tesq0
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.9, NixOS, 22.11 (Raccoon), 22.11.20230204.8e82401`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.1`
 - channels(root): `"nixos-22.05"`
 - nixpkgs: `/nix/store/f30dcvgm875ksqbhmp97wqvxmrzlbbjc-source`

Can you try again with the updated unityhub version 3.4.1?

Experiencing the same issue on Unity Hub 3.4.2

It worked for me after moving to the nightly unityhub version.

@mainrs awesome!
@FlafyDev if there's nothing that stands out in the console logs, can you send the log file located at ~/.config/unityhub/logs/info-log.json too?


Update vars.json

add picture html tag https://www.w3schools.com/tags/tag_picture.asp

Yeah, looks good to me.

@jaeh Thank you. This package has moved to @hyperapp/html. I've added a picture function there as well. :wave:


Misconfigured 'assemblyOutputPath' can be dangerous

Hello,
In a complete PEBKAC moment I essentially did
assembly / assemblyOutputPath := file(".")

which resulted in sawing off the proverbial and also literal branch I was sitting on.
I don't believe this is the behavior anyone would ever intend.
Shootout to IntellIJ IDEA's local history feature.

Also relates to #216


Update NPM plugin and hardcode versions of Node / NPM to use

The plugin we were using before was a bit old (last updated in March
2019) and this one is newer, updated, and updates the package-lock file
with the new dependency upgrades

This change is

Cool, we got the dependencies updated and the build works now. PTAL?


set "value" props doesn't change input value

Hi. It seems like setting value as in the controlled component cannot change text value. Like this code, I set japan as the default value but the component shows blank instead.
I know I can set it in defaultValue but in my real use case, I cannot use defaultValue, since data can be manipulated by outside action and defaultValue won't change.
Or if this is intended, can you suggest how to handle controlled component?
"use client"
import React, { useState } from 'react'
import {
AutoComplete,
AutoCompleteInput,
AutoCompleteItem,
AutoCompleteList,
AutoCompleteCreatable
} from "@choc-ui/chakra-autocomplete";
const Page = () => {
const countries = [
"nigeria",
"japan",
"india",
"united states",
"south korea",
];
const [select, setSelect] = useState("japan")
console.log(select)
return (
<AutoComplete openOnFocus value={select} onChange={(e)=>setSelect(e)}>

{countries.map((country, cid) => (
<AutoCompleteItem
key={option-${cid}}
value={country}
>
{country}

))}

)
}
export default Page
Thank you

Hi @Pupun2542,
I was able to get this working by passing the value prop directly to the AutoCompleteInput component.  Try that and let me know if it works for your use case.

Hi @Kysluss,
With a bit of a workaround, I managed to get it to work. Thank you for a hint.


some quesions in code

Hello, your code is very helpful to me. I am working in an urgent situation and need a complete code. It would be better if you could have the code of PyTorch framework.

Hello, a PyTorch version of this model with some extensions is currently maintained (privately in the laboratory by my former colleagues). Unfortunately, it is expected to be published only after next several months (maybe summer or later).

@nguyetn89
Do you have pytorch version of the code? Kindly help


Missing commits in repo

data-easy-0.6 is released but this repo still has version 0.5, unpushed commits?

Oops.. you're right, thanks for the tip!
Should be fixed now


Error when installing go lsp

Hello, I just met a problem when I try to installing go language server
E5108: Error executing lua ...ack/packer/start/nvim-lspinstall/lua/lspinstall/util.lua:7: module 'lspconfig/configs' not found:
        no field package.preload['lspconfig/configs']
        no file './lspconfig/configs.lua'
        no file '/home/runner/work/neovim/neovim/.deps/usr/share/luajit-2.1.0-beta3/lspconfig/configs.lua'
        no file '/usr/local/share/lua/5.1/lspconfig/configs.lua'
        no file '/usr/local/share/lua/5.1/lspconfig/configs/init.lua'
        no file '/home/runner/work/neovim/neovim/.deps/usr/share/lua/5.1/lspconfig/configs.lua'
        no file '/home/runner/work/neovim/neovim/.deps/usr/share/lua/5.1/lspconfig/configs/init.lua'
        no file '/home/kyle/.cache/nvim/packer_hererocks/2.1.0-beta3/share/lua/5.1/lspconfig/configs.lua'
        no file '/home/kyle/.cache/nvim/packer_hererocks/2.1.0-beta3/share/lua/5.1/lspconfig/configs/init.lua'
        no file '/home/kyle/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/luarocks/rocks-5.1/lspconfig/configs.lua'
        no file '/home/kyle/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/luarocks/rocks-5.1/lspconfig/configs/init.lua'
        no file './lspconfig/configs.so'
        no file '/usr/local/lib/lua/5.1/lspconfig/configs.so'
        no file '/home/runner/work/neovim/neovim/.deps/usr/lib/lua/5.1/lspconfig/configs.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
        no file '/home/kyle/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/lua/5.1/lspconfig/configs.so'

I'm not sure if this is a bug or it's just something wrong with my configuration.

In addition, I've already installed lspconfig, and there was no problem when I install c++ language server

Have you updated neovim and lspconfig? Does the problem still persist?


Translate TKET1 boxes and controlled operations

Blocked by https://github.com/CQCL/tket2/issues/308


Is there a way to use the datepicker without the input field?

I'm using the datepicker in various places in my app. In one place it would be great to directly display the calendar without the input and the need to click.
Is that possible?

Not currently, since it depends on positioning itself relative to the input, and changes size between year/month/day picker views. I'm not sure how to implement this elegantly, but I'd be open to PRs


Require and Webpack

Hi,
I tried to integrate lazyload (npm package) inside my project webpack 3.3.0 based. Here's the call I have inside a vendor. js file:.
// npm components
var Mustache = require("Mustache");
var enquire = require("enquire.js");
var Cookies = require("js-cookie");
var lazyload = require("lazyload");

I use a "vendor. js" file in which, as you can see, I already correctly integrate other plugins like this one and that Webpack manages in its modules.
However, when I open the page, in console, this error appears:
Uncaught TypeError: this. init is not a function
at Object. LazyLoad (vendor. min. js: 654)
at Fzlib. vendor. 50. defaults. src (vendor. min. js: 590)
at Object.  (vendor. min. js: 597)
at Object. 50 (vendor. min. js: 751)
at webpack_require (vendor. min. js: 21)
at Object. 49 (vendor. min. js: 404)
at webpack_require (vendor. min. js: 21)
at Fzlib. vend. 0. module. exports. isFunction (vendor. min. js: 64)
at vendor. min. js. at vendor. min. js: 67
Analyzing the code it seems that the error shots on the call to "this.init()", a method found in its prototype. Has it happened only to me?

I'm having the same issue right now this.init is not a function lazyload:66
I tried to use new webpack.ProvidePlugin, than import lazyload from 'lazyload'; and result is the same error.


[11.x] Add QueriedBy attribute

Along the same vein as the recently added CollectedBy attribute (#53122), I propose to add the QueriedBy attribute which allows users to configure which Builder class to use without having to override the newEloquentBuilder method.
#[QueriedBy(PostBuilder::class)]
class Post extends Model
{
    // ...
}

The implementation is basically a carbon copy of the CollectedBy attribute, with memoizing via a static array variable on the Model class.

Let me sit on this one a bit. I feel like custom query builders are much, much more rare than custom collections, which are also rare I think. 😅

I really hope this gets re-opened. I would love to see this in. I use custom eloquent builders in every project.

@taylorotwell at least for those of us who follow @timacdonald for enough time, I guess dedicated query builders are way more common than custom collections, based on this post
https://tim.macdonald.au/dedicated-eloquent-model-query-builders
I do use 3 custom collections, on a single project. Mostly because there are lots of aggregated reports with different filters on the same view, that benefit from custom filters on those collections.
But since that post came out, in 2019, all of my projects use dedicated query builders for almost every single model.

I also wanted to chime in with my experience. I've never made a custom Collection while I heavily use custom Builders---the primary reason is for better static analysis / IDE autocompletion and to slim down the models by moving the scopes to the builders.
Larastan does support both custom Collections and Builders, but there's a lot more tests, logic, and discussions centered around the custom Builders

I would also use this a lot more than  CollectedBy for the reasons stated in the comments before.
So, I hope you can reconsider this Taylor.

Stumbled upon this pull request as with the recent addition of CollectedBy immediately thought about an attribute for a custom query as I tend to use custom query builders more than custom collections.
Fingers crossed on this to be reopened.

I have been using custom query builders for years now as well as custom collections, but if I had to decide which one of them to choose I would go for the builders all the time.
Custom builders are very powerful and make the models a lot cleaner especially if you are using a lot of query scopes and provides better support for static analysis and typing as well.
It reduces the model classes to almost only attributes and actions, without changing their interface in any way. This is a no-brainer for me and should be used a lot more than it obviously is.
I think people discussing here are probably aware of the pros, but I just wanted to add my two cents to emphasize that adding custom query builders is more than some neat sugar feature with little value that nobody uses.
That being said, I wouldn't actually need the attribute for this, it would just be the logical step since collectBy is already there.
While I understand the reasons given against integrating this attribute, I personally find them less convincing, especially considering the benefits custom query builders bring.
We should be moving people in the direction of using custom builders rather than portraying it as something very special - and the attribute could the help with that.

Yes, it just doesn't make sense to include attributes like ScopedBy, CollectedBy and ObeservedBy, but omit this one. Out of all these four, QueriedBy would be the one I would use the most.
What is the main arguments against adding this? The maintenance burden? Performance? Wouldn't that apply to the three others as well?

At the risk of piling on... I use tons of custom query builders and no custom collections. I would love having this attribute in the core framework. Hoping you'll reconsider @taylorotwell.

Taylor doesn't usually look at closed PR's, so I think someone needs to send in a new PR and summarize everything that have been added here since it's closing.


Work around Gradle modifying system properties at configuration time

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle help

Currently, the following commands are supported:
@bot-gradle test <BuildTrigger1> <BuildTrigger2> ... <BuildTriggerN> [without PTS] [on linux]
Add without PTS to run the build with full test coverage.
Add on linux/windows/macos to run the build on specific OS (only support stage trigger).

A trigger is a special build for this PR on TeamCity, common triggers are:

SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/PullRequestFeedback/ReadyForNightly/ReadyForRelease
Shortcuts: SC/CA/QFL/QF/PRF/RFN/RFR
Specific builds:

BD: BuildDistributions/BuildDocs so that you can preview the generated docs/distribution.
PT: PerformanceTest, all performance tests for Ready For Nightly stage.
APT: AllPerformanceTest, all performance tests, including slow performance tests.
ACT: AllCrossVersionTests, all cross version tests in ReadyForNightly and ReadyForRelease.
AST: AllSmokeTestsPullRequestFeedback
AFT: AllFunctionalTestsPullRequestFeedback
ASB: AllSpecificBuildsPullRequestFeedback
ACC: AllConfigCacheTestsPullRequestFeedback
ACTN: AllCrossVersionTestsReadyForNightly
AFTN: AllFunctionalTestsReadyForNightly
ACTR: AllCrossVersionTestsReadyForRelease, alias of ACT
AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle squash

Squash the current pull request into a single commit. The squash message will come from the pull request body, with:

All Signed-off-by: lines kept.
All authors being Co-Authored-By:

@bot-gradle merge

Enqueue this PR into GitHub merge queue for merging.

GitHub will create a merge commit from your PR branch HEAD and the target branch
A GitHub Merge Queue Check Pass build will be triggered on the merge commit
When the build passes, the target branch will be fast-forwarded to this merge commit (i.e. merge the PR)

@bot-gradle squash and merge

Squash the current pull request into a single commit as described in squash command above,
then enqueue this PR into GitHub merge queue as described in merge command above.

@bot-gradle cherrypick to <branch>

Cherrypicks the current PR to another branch.
A new PR will be created and a build will triggered automatically if there is no conflict.

@bot-gradle cancel

cancel a running build in GitHub merge queue and remove the PR from the queue

@bot-gradle clean

clear the conversation history

@bot-gradle help

display this message

To run a command, simply submit a comment.  For detailed instructions see here.

@bot-gradle test ACC without PTS

I've triggered the following builds with parameters: -DenablePredictiveTestSelection=false for you. Click here to see all build failures.

All ConfigCache Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)

@bot-gradle test ACC without PTS

I've triggered the following builds with parameters: -DenablePredictiveTestSelection=false for you. Click here to see all build failures.

All ConfigCache Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)

@bot-gradle test ACC

I've triggered the following builds for you. Click here to see all build failures.

All ConfigCache Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

Pull Request Feedback (Trigger) (Check)


Invalid call. Nonexistent function 'is_action_just_pressed' in base 'InputDefault'.

Godot 2.1.3 in openSUSE Leap 42.2
	elif (Input.is_action_just_pressed("ui_accept")):

this version is designed for 2.2
In 2.1.3 there is no such function


chore(deps): bump alloy

alloy core 0.8 breaking changes

https://github.com/alloy-rs/core/pull/694

ref #8771

Merged into #8771


[bug]: [Enhancement][knowhere] range search remove topk parameter

knowhere range search is to take all vectors in the range that match and return them all.
Containing topk is ambiguous, so it is recommended to remove it.

/assign  @cydrain

range search already support execute without param 'topk'

/close


Quest for Orthologs

bench marking standard
https://github.com/qfo/benchmark-webservice
https://orthology.benchmarkservice.org/proxy/

https://academic.oup.com/nar/article/50/W1/W623/6584783

link #36


refactor: use type synonyms to reduce repetition

The Result<..., TokenError> and Result<..., SyntaxError> are repeated a lot. Creating type synonyms to reduce repetition and provide a consistent interface.

The name ’Result‘ is kind of ambiguous.
The result type also demonstrate it clearly that it may return an TokenError or Syntax Error，maybe we should shorten the entire type Result<Option<Box<Expression>>, SyntaxError> to SyntaxResult

The module hierarchy already disambiguates lexer:Result and parser:Result. And according to the naming conventions[rfc-356], it is not good practice to use prefixes here.
I think it is a good idea to define an Error to enumerate all possible error kinds so that users of the library can do pattern matching on errors to figure out the reason.

Ok, so would you like to help define an Error to do so?
I' ll merge it first.

:ok_hand: I will do it later.


Malformed xref Match qualifier lines

Need to make these two changes to the terms below:
xref: EC:<IP_ADDRESS> {xref="skos:exactMatch"} ->  xref: EC:<IP_ADDRESS> {source="skos:exactMatch"}
xref: RHEA:16301 {xref="skos:broadMatch"} -> xref: RHEA:16301 {source="skos:broadMatch"}
id: GO:0102915
name: piperitol synthase activity
namespace: molecular_function
def: "Catalysis of the reaction: H+ + (+)-pinoresinol + NADPH + O2 = (+)-piperitol + NADP + 2 H2O." [EC:<IP_ADDRESS>, PMID:16785429]
xref: EC:<IP_ADDRESS> {xref="skos:exactMatch"}
id: GO:0061809
name: NAD+ nucleotidase, cyclic ADP-ribose generating
namespace: molecular_function
def: "Catalysis of the reaction: NAD+ + H2O = nicotinamide + ADP-ribose, in a two steps reaction: first an ADP-ribosyl cyclase reaction, followed by a cyclic ADP-ribose hydrolase reaction." [GOC:dph, GOC:pad, GOC:PARL, GOC:pde, PMID:11866528]
xref: RHEA:16301 {xref="skos:broadMatch"}

Done?

Now done!