Feat: FE - set checkbox required value based on sliders state

Features added with this PR:

Ability to set Humor and Offensive checkboxes question required status by humor and offensive sliders value. The question required state will be set as true when at least one humor/offensive sliders is checked and the value > 0
Fixed a styling bug: I forgot to put the styling for the component inside the parent {}, hence if we opened the DynamicAnnotation project after the AffectiveAnnotation project, the styling may conflict with each other. I apologize for the inconvenience

What's changed:

frontend/components/tasks/affectiveAnnotation/humor/HumorInput.vue: moved the styling inside .humor-input {}
frontend/components/tasks/affectiveAnnotation/offensive/OffensiveInput.vue: moved the styling inside .offensive-input {}
frontend/components/tasks/dynamicAnnotation/CheckboxInput.vue: moved the styling inside .checkbox-input {}, disabled & transparent rules, minor styling
frontend/components/tasks/dynamicAnnotation/SliderInput.vue: moved the styling inside .slider-input {}, disabled r& transparent rules
frontend/pages/projects/_id/dynamic-annotation/index.vue: set the dim required + disabled + transparent props value based on their type and their value

Screenshots:

Hello, thank you for finding the bug and sorry for the inconvenience. Both of the bugs were caused by me not handling the change event; I used the click event instead, but I forgot slider can be slided and slide event is not included in the click event. I have updated it to use the change event, can you check?

Hello, thank you for finding the bug and sorry for the inconvenience. Both of the bugs were caused by me not handling the change event; I used the click event instead, but I forgot slider can be slided and slide event is not included in the click event. I have updated it to use the change event, can you check?

Hello, thank yo

Hello, thank you for finding the bug and sorry for the inconvenience. Both of the bugs were caused by me not handling the change event; I used the click event instead, but I forgot slider can be slided and slide event is not included in the click event. I have updated it to use the change event, can you check?

Hello, thank you for very quick fix (the close and open above is due to the lagging for a moment in my PC, sorry :sweat_smile: ). The 2 bugs I mentioned above has been solved, thank you. However, I think there is still a bug with the humor section, the 1st slider Bawi/śmieszny mnie doesn't work as in the recording. I have checked database and I see it doesn't save value into table when I change that slider's value. Can you check it?
https://user-images.githubusercontent.com/17596118/231723726-a1433974-837e-4f18-b2e0-7486114e44de.mp4


add App autoScaleCfg

Codecov Report
Base: 62.15% // Head: 62.04% // Decreases project coverage by -0.10% :warning:

Coverage data is based on head (7f6a116) compared to base (cc8c96b).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #504      +/-   ##
==========================================
- Coverage   62.15%   62.04%   -0.11%
==========================================
  Files          92       92
  Lines        7773     7783      +10
==========================================
- Hits         4831     4829       -2
- Misses       2161     2172      +11
- Partials      781      782       +1

Impacted Files
Coverage Δ

api/application.go
71.45% <0.00%> (-1.31%)
:arrow_down:

server/mis_server.go
68.85% <0.00%> (-3.28%)
:arrow_down:

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

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


Add options to merge command for controlling creation of system entry and type of relationships

Adds several options to the merge subcommand for controlling if a system entry should be created, and what type should be used for the relationships created.
This enables workflow where relationships to a UUID should be created, but the system UUID was added to e.g. an SBOM repository as part of a separate file.
The more "standard" Contains relationship is used instead of the Includes relationship that apparently was unique to Surfactant merged SBOMs.
Changes

Add option for disabling the creation of a system object
Add option for specifying what type of relationship should be created for relationships to the system object; use "Contains" as the default type
Fix a bug where a System SBOM object accessed UUID using subscript notation (["UUID"]) instead of as a member variable (.UUID)

Resolves #115
Resolves #116

@nightlark I'm a bit concerned with the functionality of creating a contains relationship with a randomly generated uuid if no system uuid is present and the user specifies they don't want one added. This would create a relationship to a uuid that has no information attached to it, so a user looking at it wouldn't know if it was a system uuid, software uuid, or what. I think it would be better to require the user to provide a uuid to link to if no system uuid is present and a system object is not to be added. This would prevent floating UUIDs with no meaning attached to them. Thoughts?

@nightlark Also I typically use Includes for merges, what was the reason for changing the default to Contains?

If possible I would also add a few unit tests!

@nightlark Also I typically use Includes for merges, what was the reason for changing the default to Contains?

Mostly consistency -- I was talking with Aaron about what relationships other labs were using in their SBOMs for tying software entries to the system object, and it seems everyone else is using "Contains".

@nightlark I'm a bit concerned with the functionality of creating a contains relationship with a randomly generated uuid if no system uuid is present and the user specifies they don't want one added. This would create a relationship to a uuid that has no information attached to it, so a user looking at it wouldn't know if it was a system uuid, software uuid, or what. I think it would be better to require the user to provide a uuid to link to if no system uuid is present and a system object is not to be added. This would prevent floating UUIDs with no meaning attached to them. Thoughts?

Oof... that would be fun to figure out why an SBOM fails validation when uploading to the repository. I'll add a command line option for providing a system_uuid, and checks to make sure a relationship to a random UUID is only added if the system was also added. I'll also make so that command line options take precedence over the config file like I'd originally planned.

Mostly consistency -- I was talking with Aaron about what relationships other labs were using in their SBOMs for tying software entries to the system object, and it seems everyone else is using "Contains".

Ah got it, maybe I'm using them wrong then :D

@nightlark The fix for the random uuid looks good! The logic if random system uuid is used, you must add the system object to the sbom makes sense to me and will prevent any floating uuids from getting generated.


Min value for number.warmwasser_normal and number.warmwasser_absenk

Is your feature request related to a problem? Please describe.
If we on vacation i try to decrease the target temperature to 20 or 21°C
Describe the solution you'd like
Please allow to decrease the target temperatures below 30°C. I like to see 20°C. After setting to 20° the heatpump avoid to heat up water stoarge. If we not at home its not useful to heat it up to 30°.
Describe alternatives you've considered
.....
Additional context
I hope it is possible

Thanks, after a restart of HA it works fine, :) Will be create if you can adjust the min value in one of the next releases. 👍

Temperature ranges now are aligned with WEM portal in Version 1.0.4
We allow the same range as WEM portal. (Values outside these ranges will not be accepted by the heat pump..)

Perfect Thanks.


Update bug-bounty-list.json

Added in Antavo Loyalty Management Platforms BBP
Summary
< A quick summary of the associated pull request >
Quality Assurance Checklist
< Confirmation of this pull request meeting the following requirements, prior to merge >

Review Items
Y/N

Site has a publicly known bug bounty or vulnerability disclosure program

Disclosure policy is publicly available

Public URL

Submission follows the Diodb schema

Your Twitter handle (Optional):

Hi,
Our platform is design that way that only registered ethical hackers can see the details of the policy - accepting our Terms of service, Testing policy and Data protection policy.
Can you please advise what are the options here? Can we either use the added link or can this program be on the list with our platforms main page’s URL?
Thanks,
Csaba

Feladó: cje @.***>
Elküldte: szombat, július 17, 2021 2:37 du.
Címzett: disclose/diodb
Másolatot kap: Mészáros Csaba; Author
Tárgy: Re: [disclose/diodb] Update bug-bounty-list.json (#320)
@yesnet0 requested changes on this pull request.
Please post the link for the actual policy itself. This currently links to a list of programs. The policy needs to be publicly readable to be considered.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/disclose/diodb/pull/320#pullrequestreview-708938673, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASDNKMS5U4DEFQASM44H7LDTYF2Q7ANCNFSM5APS7CGQ.

Understood. The disclose.io Project doesn't consider what you've described as a true vulnerability disclosure policy, since VDPs should be accessible and available to anyone on the Internet who wishes to report an issue. Instead, I'd suggest adding your platform to the list here: https://github.com/disclose/bug-bounty-platforms

Yes, indeed, this is a bug bounty program not a vdp, but I thought it is also possible to list bbp here. Thanks for the other link, I will try to szbmit there.
Regards,
Csaba

Feladó: cje @.>
Elküldve: Saturday, July 24, 2021 8:37:17 AM
Címzett: disclose/diodb @.>
Másolatot kap: Mészáros Csaba @.>; Author @.>
Tárgy: Re: [disclose/diodb] Update bug-bounty-list.json (#320)
Understood. The disclose.io Project doesn't consider what you've described as a true vulnerability disclosure policy, since VDPs should be accessible and available to anyone on the Internet who wishes to report an issue. Instead, I'd suggest adding your platform to the list here: https://github.com/disclose/bug-bounty-platforms
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/disclose/diodb/pull/320#issuecomment-886008609, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASDNKMSG5U7F5ARPJ3PVLCLTZJNR3ANCNFSM5APS7CGQ.


fix: 🔥 git commit on windows

If we don't chain the commands export is not needed.

i can confirm that this solution also works on mac

On Windows 10:
PS D:\Downloads\teia-ui> npm start

<EMAIL_ADDRESS>start
REACT_APP_BUILD_COMMIT=git rev-parse HEAD react-scripts start

'REACT_APP_BUILD_COMMIT' is not recognized as an internal or external command,
operable program or batch file.

On Windows 10:

PS D:\Downloads\teia-ui> npm start

><EMAIL_ADDRESS>start

> REACT_APP_BUILD_COMMIT=`git rev-parse HEAD` react-scripts start

'REACT_APP_BUILD_COMMIT' is not recognized as an internal or external command,

operable program or batch file.

Ahhh you use Powershell, I have no clue then, can you try #27


add BITWISE_AND  Operators support at  translator   frontend

Implement the BITWISE_AND token to recognize the & operator for performing bitwise AND operations.

@Raghav-2903 will be working on this issue

@NripeshN      add BITWISE_AND Operators support at translator frontend assign me


Move pure-java code to a new repo

The pure java code should be factored out of this repo and into a new one.  The new repo should be a submodule of couchbase-lite-android and be separated into main (code used by both by pure java, and pure [or something like that] that is used only by the pure java product.  This follows the pattern established in the way that cblite-android-ee uses cblite-android.
This would also be a good time to refactor the repo directory structure, to eliminate the redundant 'android' directory.

Done


ci: trigger docs update on tag

Requires #967.
🚀 Description
When a tag is commited to this repository, Travis will trigger the job on openzeppelin-docs repo to update the docs website.
This PR depends on https://github.com/OpenZeppelin/openzeppelin-docs/pull/2, and because they have to be landed together, I haven't tested this end-to-end. I tested everything I could, but it might need some tweaking after the other one lands.

[x] 📘 I've reviewed the OpenZeppelin Contributor Guidelines
[x] ✅ I've added tests where applicable to test my new functionality.
[x] 📖 I've made sure that my contracts are well-documented.
[x] 🎨 I've run the JS/Solidity linters and fixed any issues (npm run lint:all:fix).

Thanks for the review @frangio ! It should be ready for another one.

I tested the trigger script and it resulted in the bump of 1.12.0 on the docs website:
https://travis-ci.com/OpenZeppelin/openzeppelin-docs/builds/83106581
The only thing that's missing to test is the travis trigger when there's a tag, but well, we need a travis tag for that. I'm merging this now, so we can take a look at what happens when 2.0 is released.


Add indexed_map

Adds indexed_map to allow indexing operations when mapping.
Not sure how much ceremony is required here, but I think it makes a good addition. Let me know if there's something that I should add.

Before I merge this, have you considered adding a version of this to Matrix?
I'm wondering if it makes sense to add to Matrix considering that we might end up choosing an unintuitive index ordering, i.e. (row, column) vs (column, row).

https://github.com/maplant/aljabar/pull/13/commits/70d9c826503e98791245b0b5f983a3d5818785df: I was a bit hasty when creating the PR, sorry about that. :man_facepalming:

Before I merge this, have you considered adding a version of this to Matrix?

I failed to consider anyone's needs but my own, but that does sound like a good idea!

I'm wondering if it makes sense to add to Matrix considering that we might end up choosing an unintuitive index ordering, i.e. (row, column) vs (column, row).

That is a good question … The only thing I can come up with is something like
    pub fn indexed_map_column_major<Out, F>(self, mut f: F) -> Matrix<Out, {N}, {M}>
    where
        F: FnMut(usize, usize, T) -> Out,
    {
        self.indexed_map(|(i, j), x: T| -> Out { f(j, i, x) })
    }

    pub fn indexed_map<Out, F>(self, mut f: F) -> Matrix<Out, {N}, {M}>
    where
        F: FnMut((usize, usize), T) -> Out,
    { … }

in order to be consistent with the Index implementation.

I like the idea of namespacing into row_major and column_major, although I say for now let's consider it an open question. I don't think it's a huge issue because users can just use .enumerate.


fix: pin substra-tools version in examples

To change on next release

Is it the fix for the GPU?

Is it the fix for the GPU?

No, it's suppose to fix the CI (doc examples)

End to end tests: :hourglass_flowing_sand: STARTING

/e2e --tests=doc

Is it the fix for the GPU?

No, it's suppose to fix the CI (doc examples)

Should we run /e2e?

yep you're right

@thbcmlowk it passed


feat(sdk/go): use OpenTelemetry SDK

Instead of opentracing.Tracer use trace.Tracer from opentelemetry go sdk.
Should be pretty straightforward.

Hi! The migration is planned. However, we have several internal clients using "opentracing-go", and the transition will not happen quickly.

Great, ping me when you are ready, I can help with migration if needed.

@verytable do you have any updates here?


注意：如果安装错误，注意这两个包的版本  wandb==0.11.0 protobuf==3.18.3

Error1: 如果启动异常报错 protobuf  需要更新到 protobuf==3.18.3
 _message.Message._CheckCalledFromGeneratedFile()
TypeError: Descriptors cannot not be created directly.
If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
If you cannot immediately regenerate your protos, some other possible workarounds are:
 1. Downgrade the protobuf package to 3.20.x or lower.
 2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).

More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates

Error 2: 如果启动异常报错 wandb, 需要更新到  wandb==0.11.0
 File "/usr/local/miniconda3/lib/python3.10/site-packages/wandb/proto/v3/wandb_internal_pb2.py", line 16, in <module>
    from wandb.proto import wandb_base_pb2 as wandb_dot_proto_dot_wandb__base__pb2
  File "/usr/local/miniconda3/lib/python3.10/site-packages/wandb/proto/wandb_base_pb2.py", line 6, in <module>
    from wandb.proto.v3.wandb_base_pb2 import *
  File "/usr/local/miniconda3/lib/python3.10/site-packages/wandb/proto/v3/wandb_base_pb2.py", line 21, in <module>
    __RECORDINFO = DESCRIPTOR.message_types_by_name['_RecordInfo']
AttributeError: 'NoneType' object has no attribute 'message_types_by_name'

注意最好使用下面两个老版本的 wandb 和 protobuf
## 补丁
wandb==0.11.0
protobuf==3.18.3

https://github.com/imClumsyPanda/langchain-ChatGLM/tree/9dee1f28c012d6ffacf97353c2db943679c962ab


Continuous skipping of tracks

Recently pydora stopped working, for some reason it keeps skipping tracks, I believe the tracks are not playable (python exception)j.  Do you know why this might be happening? I have a premium account with pandora and all.
Here is my config:
[user]
username =
password =
[api]
username = android
api_host = tuner.pandora.com/services/json/
encryption_key = 6#26FRL$ZWD
decryption_key = R=U!LH$O2B#
device = android-generic
password = AC7IBG09A3DTSYM4R41UJWL07VLN8JI7
default_audio_quality = highQuality
Here is sample output
:
50: Mariah Carey (Holiday) Radio
51: Christmas Radio
52: Pink Radio
53: Pink Martini Radio
54: Alternative and Relaxation
55: Easy Listening Radio
56: Luis Fonsi Radio
57: Rainbows In The Dark Radio
58: Music For Brainwave Massage Radio
59: Krishna  Radio
60: Carol Of The Bells (Instrumental) Radio
61: Lisa Shaw Radio
62: Nicki Minaj Radio
63: Yanni Radio
64: Trance
65: Deep Beat
66: Drum & Bass
67: Trip Hop
68: Liquid Drum & Bass
69: Deep House
70: Progressive/Electro House
71: Armin Van Buuren Radio
72: Milo Radio
73: Jungle Of Mirror (Scumfrog Remix) Radio
74: Silversun Pickups Radio
75: The Best Deceptions Radio
76: Thievery Corporation Radio
77: Alternative Pop/Rock
78: Alternative / Indie Rock
79: Drum'n'Bass
80: Dashboard Confessional Radio
Station: 1
The Prey by Ashes Divide
Find You There by We The Kings
Prescription Mixed Up by Snakes & Music
(This Is How I Look) When I Laugh At Death by Johnny Action Figure
Read My Mind by The Killers
Conservation Of Two by Sweet Trip
Damn Silence by Sunrise Avenue
Swinging Swords by Ben + Vesper
Radio Silence by Attention System
New Frontier by Counting Crows
Eighty-Eights by Farewell
Closer To The Edge (American Idol Performance) by James Durbin
(keeps skipping)

Emailed with @bikexcountry and it looks like Pandora is not returning audio links for certain API keys anymore. I can repro this at least for the iphone API key. In the short term using the internal-tuner keys seems to work. There are a handful of fixes to be made here:

Detect the missing audio URLs and throw an error
Update the configuration program to use the internal-tuner keys
Update the pydora CLI to warn about this issue and tell the user to re-configure
Implement #8 to avoid blowing past API limits

I'm working on these fixes but don't have an ETA right now.

It seems as if the internal-tuner key no longer works as well.

@izaclorimer can you provide some more reproduction steps? What is not working, are there exceptions or are you seeing song skips? Also can you post your config file without your username and password so I have a starting point for testing? As of right now I'm not seeing any issues with the internal tuner keys on my setup.

Using the API for the Vista Widget on the internal-tuner also continuously skips tracks. Using a free Pandora account.
https://6xq.net/pandora-apidoc/json/partners/#vista-widget

I've done a bit more digging into what's going on here. There appear to be two different issues; one impacts pydora the player and the other pydora the API. Both seem to be the root cause of your problems. In all cases I think there are patches and then all the API keys will work again.
First, it looks like Pandora varies responses based on the API key that is used. In some cases it returns a audio quality map with URLs to the audio files and in others it just returns a single URL.
For example, using the internal tuner the response format for station.getPlaylist is this (elided heavily for clarity):
{
    "items": [
        {
            "audioUrlMap": {
                "highQuality": {
                    "bitrate": "192",
                    "encoding": "mp3",
                    "audioUrl": "...",
                    "protocol": "http"
                },
                "mediumQuality": {
                    "bitrate": "64",
                    "encoding": "aacplus",
                    "audioUrl": "...",
                    "protocol": "http"
                }
            }
        }
    ]
}

This is the format the pydora API expects to work with and this works fine. However, using the Android or Windows Vista Widget API key the response is similar to this:
{
    "items": [
        {
            "audioUrl": "http://t1-2.p-cdn.com/access/?version=5&lid=476835810&token=..."
        }
    ]
}

Solving that problem is easy, I've got a working patch for it. The next problem, which only affects pydora the player, is that for all other API keys that are not the Desktop AIR client Pandora is streaming AAC SBR files which are not supported by mpg123. The fix to this one is not nearly as simple.
I've had it on my backlog for a while to make the mpg123 strategy pluggable which would allow alternate strategies like headless VLC (using the rc plugin). This would give a lot more playback flexibility without compromising the interface. I plan to keep the mpg123 backend for now but also add VLC support, which will be the default if VLC is installed.
I'll ship the first patch today but I expect the second one to take a little bit longer. Hopefully I will be able to land it this week and will keep this issue open to track that status. In the meantime using a Pandora One account with the Desktop AIR application credentials should work.

I've got a working version that uses either VLC or mpg123 as an output backend. It prefers VLC if it's installed on the system. The search backend uses your $PATH (it also supports VLC.app for Mac OS) so if you've got VLC for mpg123 on your path you should be good to go. This should support at least Linux and Mac OS X. I don't have any way to test Windows.
The changes also support the modified response formats for some API keys which allows all existing API keys to work again. I believe all changes to be backwards compatible with current behavior.
Check out the vlc-backend branch and test. It seems stable but I'd like to do some more testing myself before merging it to master and pushing a new release. Please leave feedback here if you find any issues.

The other thing the patch adds is volume control within pydora with a VLC backend using vu and vd.

This works great on my Mac laptop but doesn't work with VLC on Ubuntu. I'm not certain if it's a VLC codec issue or an external issue but I'll do some more research. I'm not ready to release this till I have at least Linux and Mac OS working.

I've done some more testing and it seems that the issue is actually that the ios API key no longer works without a very specific user-agent string (which I have not bothered to find). I'll make an update to the configuration script to prefer android instead of ios and will add a warning to the command line player. Then I think this will be ready for release.

Final changes have been made. The command line client now also blacklists the non-working ios key. Updated pydora-configure to allow it to freshen keys if a config file exists. You will have to do this at least once if you're using the default config which previously preferred the ios key.
I'm going to close this ticket and merge the changes this will be in the 1.9 release later tonight.


[Bug] [false positive] Python module causing manifest generating different results without changes

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
I have some models with incremental predicate that looks back n days only. Something like
incremental_predicates = [
            "DBT_INTERNAL_DEST.ingestion_timestamp::date >= dateadd(day, -10, " ~ var('date_parameter', modules.datetime.datetime.now()) ~ "::date)"
        ],

What we're noticing is the python module would render an actual value in the manifest file, which means the timestamp could change without the model being modified. This is causing issue cause the state:modified would pick up all models with this predicate.
Expected Behavior
We would expect the manifest to be unchanged and the models with this setup wouldn't be flagged as changed when running state:modified
Steps To Reproduce

Adding an incremental predicate to a model with module.datetime.datetime.now() in it.

incremental_predicates = ["DBT_INTERNAL_DEST.ingestion_timestamp::date >= dateadd(day, -10, " ~ modules.datetime.datetime.now() ~ "::date)"],

Run compile to generate the manifest file
The incremental predicate of the model in the manifest file would show the current timestamp
Copy the manifest file to current directory mv ..../target/manifest.json .
Switch to another branch and generate the manifest file again without changing anything
run dbt ls -m state:modified.body --state . to compare the 2 branches. It shouldn't show anything as we didn't change any model, but the model with this predicate would show up. Looking into the 2 manifest files can see the timestamps in the incremental predicate are different

Relevant log output
No response
Environment
- OS:macOS 14.7, build 23H124
- Python:3.9.6
- dbt:1.6.1

Which database adapter are you using with dbt?
snowflake
Additional Context
No response

Thanks for reaching out @james-ho-cko !
We've been addressing some case of false positives within https://github.com/dbt-labs/dbt-core/issues/9562.
Did you happen to try installing dbt-core 1.9.0b3 and see if it still has the issue or not?
For date_parameter, is it coming from vars: in dbt_project.yml or --vars passed on the command line?.

Thanks for getting back to me Doug, the epic you shared is really helpful.
We haven't upgraded to the latest version so I can't really tell. We currently get around with this by creating a macro as the predicate.
The data_parameter is what we use to be able to ad-hocly change the look back day if we needed to, so it'd be passed on the command line like --vars
I tried to add
flags:
  state_modified_compare_more_unrendered_values: true

to dbt_project.yml as the documentation suggests but seems not working. Is it only available in v1.9?

@james-ho-cko
I tried to replicate the scenario that you reported using dbt v1.6, but I wasn't able. Could you try tweaking the file and commands below to replicate your bug report?
Create this file:
models/my_model.sql
{{
  config(
    materialized = 'incremental',
    unique_key = 'id',
    incremental_strategy = 'merge',
    incremental_predicates = ["DBT_INTERNAL_DEST.ingestion_timestamp::date <= '" ~ var('date_parameter', modules.datetime.datetime.now()) ~ "'::date"],
  )
}}

select 1 as id, {{ dbt.current_timestamp() }} as ingestion_timestamp

Run these commands:
dbt compile
mv target/manifest.json .
dbt list -s state:modified --state .

I got this output:
04:04:58  Running with dbt=1.6.5
04:04:59  Registered adapter: snowflake=1.6.6
04:04:59  Found 1 model, 0 sources, 0 exposures, 0 metrics, 375 macros, 0 groups, 0 semantic models
04:04:59  The selection criterion 'state:modified' does not match any nodes
04:04:59  No nodes selected!

I think you need to change branch.
What we have is a model already in production with this predicate setup, and every time when we run CI on feature branch against the main branch's manifest, the model will show up even it's untouched.
It's a bit inconsistent when I try to replicate it locally by
dbt compile
mv target/manifest.json .

git checkout -b testing
dbt list -s state:modified --state .

This might now work as it's the same file you created locally. I think it needs to be a model that's already in 2 different branches.
Let me know if that makes sense!

@dbeatty10 try this:
Create this file:
models/my_model.sql
{{
  config(
    materialized = 'incremental',
    unique_key = 'id',
    incremental_strategy = 'merge',
    incremental_predicates = ["DBT_INTERNAL_DEST.ingestion_timestamp::date <= '" ~ var('date_parameter', modules.datetime.datetime.now()) ~ "'::date"],
  )
}}

select 1 as id, {{ dbt.current_timestamp() }} as ingestion_timestamp

Run these commands:
dbt compile
mv target/manifest.json .

Delete the model file(keep the manifest at current directory)
Switch to another branch
git checkout -b testing

Create a file with the same name and the exactly same contents:
{{
  config(
    materialized = 'incremental',
    unique_key = 'id',
    incremental_strategy = 'merge',
    incremental_predicates = ["DBT_INTERNAL_DEST.ingestion_timestamp::date <= '" ~ var('date_parameter', modules.datetime.datetime.now()) ~ "'::date"],
  )
}}

select 1 as id, {{ dbt.current_timestamp() }} as ingestion_timestamp

Run
dbt ls -m state:modified --state .

This should give you my_model. And if you compare the 2 manifest, you should be able to see the only difference is the timestamp in the predicate.

@james-ho-cko I tried the steps you outlined, but I still wasn't able to replicate what you are reporting with state:modified.
I can see that the "incremental_predicates": portions of manifest.json and target/manifiest.json are different, but I get the message:
04:27:41  The selection criterion 'state:modified' does not match any nodes
04:27:41  No nodes selected!

As an aside, I wouldn't expect changing branches to make a difference either way as it relates to state:modified.
Are you able to replicate the issue without changing branches?

Awesome @james-ho-cko !
Those commands helped me reliably replicate what you are saying. And here's an even more brief way that gave me my_model as a result without needing to do any dbt clean:
dbt parse --target-path artifacts
dbt list --select state:modified --state artifacts

However, if the same value is used for --vars across invocations, it does not show it as modified:
dbt parse --target-path artifacts --vars '{"date_parameter": "2024-01-01"}'
dbt list --select state:modified --state artifacts --vars '{"date_parameter": "2024-01-01"}'

The underlying explantation seems to be that state:modified.config is comparing the
post-rendered incremental_predicates config rather than the pre-rendered incremental_predicates config. See below for a simplified example.
Good news: starting in dbt-core v1.9, setting the state_modified_compare_more_unrendered_values flag to True changes the state:modified comparison from using rendered values to unrendered values instead 🎉
Example
The example below shows that the observed vs. expected behavior isn't due to using var or the datetime module. Rather, it is when a rendered Jinja value in incremental_predicates changes between the state directory and the current invocation.
models/my_model_table.sql
{{
  config(
    materialized = 'table',
  )
}}

select 1 as id, {{ dbt.string_literal(invocation_id) }} as invocation_id

models/my_model_incremental_predicates.sql
{{
  config(
    materialized = 'incremental',
    unique_key = 'id',
    incremental_strategy = 'append',
    incremental_predicates = ["DBT_INTERNAL_DEST.invocation_id = '" ~ invocation_id ~ "'"],
  )
}}

select 1 as id, {{ dbt.string_literal(invocation_id) }} as invocation_id

Run these commands:
dbt parse --target-path artifacts
dbt list --select state:modified --state artifacts

You'll see that my_model_incremental_predicates shows as modified whereas my_model_table doesn't.
But if you set the state_modified_compare_more_unrendered_values flag to True within dbt_project.yml and try again, then neither of them will show as modified 😎:
dbt_project.yml
flags:
  state_modified_compare_more_unrendered_values: True

Summary
Closing this as resolved by https://github.com/dbt-labs/dbt-core/pull/10487 and/or https://github.com/dbt-labs/dbt-core/pull/10675.
@james-ho-cko could you let us know if you try this in dbt-core v1.9 with the state_modified_compare_more_unrendered_values flag and it doesn't work for you?


New keyword 'Convert string to json' and some fixes

Convert string to json object using json.loads()
Fixes for python 3 support
Fix setup version lookup

@nottyo: Any news on getting Python 3 support (merged) to the robotframework-jsonlibrary mainline?

Converting string to json would be very useful. I hope it will be merged and released soon.

Will this be merged?

I'm so sorry about that since I don't have enough time to maintain this project 🙏

I'm so sorry about that since I don't have enough time to maintain this project 🙏

I'm so sorry about that since I don't have enough time to maintain this project  Anyway, I'll merge this PR thanks.

Thank you!
Could you consider think giving admin rights to someone you know who has time?
Or to robot framework foundation? This is handy library would be sad if the development stops.


No module named opensim

Hello everyone,
How can run the Python scripts in OpenSim when they use the command "import opensim as osim"? ScriptingShell Window reply "ImportError: No module named opensim".
I'm running OpenSim 4.1. and already installed python 3.7.6. I can use the commands and scripts in Python (and Anaconda), after running the setup.py but it do not fix the issue in OpenSim. I think it's not that hard, but I can't figure it out alone :-/
Best regards

Hi,
I had an already installed Anaconda (navigator version 1.9.12) on my computer and followed the instruction to installed osim-rl from the following website:
http://osim-rl.stanford.edu/docs/quickstart/
The installation went through smoothly, at least I did not see any warning or error message.
After that when I open Anaconda navigator, I can see osim-rl is added to the available environments.
when I choose osim-rl environment, it gives me two possibilities ("open terminal" and "open with python"),
if I choose "open terminal"
I run "activate opensim-rl" as instructed by the website that this must be done every time
I also run "python -c "import opensim" " and apparently this one is fine too. At least, it does not generate any error or warning message.
but when I choose "open with python" and run "from osim.env import L2RunEnv" I face an error message as mentioned in this thread.
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'osim'
I followed the conversation in this thread and tried
import org.opensim as osim
I received a similar error  "No module named 'org'"
Any suggestion here?
Best regards,
Afshin

I also met the same problem. Have you solved it? Could you tell me how it was resolved.

Hi, No. This was my sideline activity for a long time ago. I stopped working on it.


About the repo, what is the difference between the

I have a question about the Chemprop tool and its repository. Specifically, I would like to know if there have been any changes made to the tool or repository, and what the differences are compared to the original version. Can you provide me with more information or clarification on this? (I can see the new activate function beaf)

Oh I can see the change


Add users to the server

I'd like to have the ability to register new users, edit users, delete users, log in and log out through the server. This includes adding support for sessions and implementing all relevant API routes. We should also make sure to check for authorized users before performing all edit, update, or delete operations on existing routes.
I suggest we use passport and passport-session to accomplish most of the user authentication but I'm open to other solutions.
End goal here is to have a user object to associate with custom spells and spell books so we don't have to store these things in localStorage on the client side. We can move custom spells and spell books to the database after this is finished.

Note: there is a branch called add-users that is a decent starting point to adding users with passport.


fixes #268: contenteditable selector is inadequate, not compatible with ...

...HAML-generated HTML

Thanks for finding and fixing this!


install on latest scala & sbt - is it possible?

[warn] 	Note: Some unresolved dependencies have extra attributes.  Check that these dependencies exist with the requested attributes.
[warn] 		org.scala-debugger:sbt-scala-debugger:1.1.0-M3 (scalaVersion=2.12, sbtVersion=1.0)

@Pitometsu, I haven't published the plugin for sbt 1.x. The plugin is currently available for 0.13.x for Scala 2.10/2.11/2.12.


sq reformat

Type of Change
This pr is a re-submit of pr_1496 in order to explore potential ITREX ut conflicts. Please refer to the description of pr_1496 for details.
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
any library dependency introduced or removed

/azp run UT-ITREX


Window main loop crashes at processing exception.

Crashes at _logging.exception("") in _window_proc function from Window module.

Problem was in incorrect use of ctypes module.


Modified java analysis utility class to define a default file encoding. [phab:D1311]

Created by craigbarber at 2017-02-07 18:19:36:
This was done to define a standardized file encoding to be referred to uniformly by indexers. This is a temporary measure until the time which extractors are able to pass along encoding metadata through compilation unit protos.

jrtom commented inline (context lost during migration) at 2017-02-07 18:43:28:
Why even have this be a parameter to getFileNode() any more?
If you want to make the argument that we want to leave the door partially open for specifying other encodings later, that's fine, but if we aren't interested in leaving that door open then we should just get rid of the parameter and specify it more directly where it's needed.

jrtom wrote at 2017-02-07 18:43:28:
Inline comment below.

craigbarber commented inline (context lost during migration) at 2017-02-07 18:48:26:
I think this is looking forward to the AlphaSource scenario, when we will necessarily have to be sensitive to corpora which don't have standardized encodings. At that point my goal is to have the encoding information included in the compilation unit and passed to the indexers so no assumptions need to be made.

jrtom wrote at 2017-02-07 19:02:23:
LGTM

jrtom accepted this revision at 2017-02-07 19:02:23

craigbarber closed via commit 342d4c06ed82faf6ce798a57c48f8a4776a17be9 at 2017-02-07 19:17:22


fix for efr32 mg12 multi-admin

Problem

Multi admin was failing on mg12 when trying to complete commissioning with the 2nd controller

Change overview

Added missing defines and init function to properly init mbedtls for efr32 sdk

Testing

Manual testing with mg12 to validate fix
Manual testing with mg24 to validate no regressions were caused

Fast tracking, given a platform maintainer is updating their platform.


Augment metadata server stats

Include the following (ensure encrypted):

essentially everything stat returns for a file
storage servers the file was replicated to
emails of people the file was shared with
permissions of the people the file was shared with
.
.
.

This might have some dependencies on what @irfansharif is working on, since he's doing key sharing.

RIP Kura (2018 - 2018).


Fix your floats

The Issue
When publishing with a 0.01 bid, the daemon shows:
2018-06-14 18:24:20,480 INFO     lbrynet.daemon.Daemon:2152: Publish: {'claim_address': None, 'channel_id': u'', 'name': u'2avzsi111', 'claim_dict': {'version': '_0_0_1', 'claimType': 'streamType', 'stream': {'version': '_0_0_1', 'metadata': {u'license': u'None', u'language': u'en', u'title': u'decimal test', 'version': '_0_1_0', u'nsfw': False, u'licenseUrl': u'', u'thumbnail': u''}}}, 'channel_name': None, 'bid': Decimal('0.01000000000000000020816681711721685132943093776702880859375'), 'file_path': u'C:\\Users\\SoloDolo\\Desktop\\2avzsi.jpg', 'change_address': None}
Sample with 0.1:
2018-06-14 18:32:47,834 INFO     lbrynet.daemon.Daemon:2152: Publish: {'claim_address': None, 'channel_id': u'', 'name': u'html2', 'claim_dict': {'version': '_0_0_1', 'claimType': 'streamType', 'stream': {'version': '_0_0_1', 'metadata': {u'license': u'None', u'language': u'en', u'title': u'test 2', 'version': '_0_1_0', u'nsfw': False, u'licenseUrl': u'', u'thumbnail': u''}}}, 'channel_name': None, 'bid': Decimal('0.1000000000000000055511151231257827021181583404541015625'), 'file_path': u'C:\\Users\\SoloDolo\\Desktop\\html.html', 'change_address': None}
The files are actually published with the correct value, but this doesn't look good for the logs.
Steps to reproduce

Run daemon on master
Publish something with a bid value of less than 1

System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

Seems correct to me. The 0.01 is probably being sent as a float and not a decimal in the JSON (then it's turned into a Decimal by the new code but by that point it's too late). If you want to have a nice looking '0.01' decimal it would have to be passed as a string and then parsed directly by Decimal bypassing any float stuff. floats are nasty business.
Can you try changing the app to send the decimal as a string and see if you get Decimal('0.01') in the log instead of the ugly float inside a Decimal you're getting now?

One thing we could do is round the float after converting it into a decimal. But I would rather just depricate floats altogether instead of piling on hacks.

We'll give this a try on the app side. The problem worsens when you publish something with a bid like .99:
2018-06-14 18:37:56,551 INFO     lbrynet.core.Wallet:1187: Send claim: html3 for 0.9899999999999999911182158029987476766109466552734375: 080110011a650801121e080410011a0674657374203322002a0032044e6f6e6538004a0052005a001a41080110011a30bcbef283e927971b2d5150d499574239285dbd4e69840aa19f12d461a67ea6cfc29b0ba99c1b7041345667de985df4e72209746578742f68746d6c

@hackrush01 provides a work around in this pull request (i'm still on the fence if this is the best way but it does the job for now): https://github.com/lbryio/lbry/pull/1257


rendering the image

I use the code you provide to render the image,but there is no '.exr'.would you like to give me some soulutions?

I use the code you provide to render the image,but there is no '.exr'.would you like to give me some soulutions?

I use the code you provide to render the image,but there is no '.exr'.would you like to give me some soulutions?

hello, did u find the solution and share the data set


Missing SO_INCOMING_CPU compiling with armv7-unknown-linux-musleabi

Compiling socket2 v0.3.19
Running `rustc --crate-name socket2 --edition=2018 /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.3.19/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C panic=abort -C codegen-units=1 -C metadata=9516879405a31528 -C extra-filename=-9516879405a31528 --out-dir /tmp/cargo-installQyepjN/armv7-unknown-linux-musleabi/release/deps --target armv7-unknown-linux-musleabi -C linker=armv6-linux-musleabi-gcc -L dependency=/tmp/cargo-installQyepjN/armv7-unknown-linux-musleabi/release/deps -L dependency=/tmp/cargo-installQyepjN/release/deps --extern cfg_if=/tmp/cargo-installQyepjN/armv7-unknown-linux-musleabi/release/deps/libcfg_if-a21588f9f01fd146.rmeta --extern libc=/tmp/cargo-installQyepjN/armv7-unknown-linux-musleabi/release/deps/liblibc-2305531b0b6bff17.rmeta --cap-lints allow -C relocation-model=pic -C prefer-dynamic=off -C target-feature=+crt-static,-vfp2,-vfp3`
Compiling socket2 v0.4.0
Running `rustc --crate-name socket2 --edition=2018 /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.4.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C panic=abort -C linker-plugin-lto -C codegen-units=1 --cfg 'feature="all"' -C metadata=4b78b189cd4beac3 -C extra-filename=-4b78b189cd4beac3 --out-dir /tmp/cargo-installQyepjN/armv7-unknown-linux-musleabi/release/deps --target armv7-unknown-linux-musleabi -C linker=armv6-linux-musleabi-gcc -L dependency=/tmp/cargo-installQyepjN/armv7-unknown-linux-musleabi/release/deps -L dependency=/tmp/cargo-installQyepjN/release/deps --extern libc=/tmp/cargo-installQyepjN/armv7-unknown-linux-musleabi/release/deps/liblibc-2305531b0b6bff17.rmeta --cap-lints allow -C relocation-model=pic -C prefer-dynamic=off -C target-feature=+crt-static,-vfp2,-vfp3`
error[E0425]: cannot find value `SO_INCOMING_CPU` in crate `libc` --> /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.4.0/src/sys/unix.rs:1201:69 | 1201 | getsockopt::<c_int>(self.inner, libc::SOL_SOCKET, libc::SO_INCOMING_CPU) | ^^^^^^^^^^^^^^^ not found in `libc`
error[E0425]: cannot find value `SO_INCOMING_CPU` in crate `libc` --> /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.4.0/src/sys/unix.rs:1217:23 | 1217 | libc::SO_INCOMING_CPU, | ^^^^^^^^^^^^^^^ not found in `libc`
error: aborting due to 2 previous errors
For more information about this error, try `rustc --explain E0425`.
error: could not compile `socket2` Caused by:
process didn't exit successfully: `rustc --crate-name socket2 --edition=2018 /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.4.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C panic=abort -C linker-plugin-lto -C codegen-units=1 --cfg 'feature="all"' -C metadata=4b78b189cd4beac3 -C extra-filename=-4b78b189cd4beac3 --out-dir /tmp/cargo-installQyepjN/armv7-unknown-linux-musleabi/release/deps --target armv7-unknown-linux-musleabi -C linker=armv6-linux-musleabi-gcc -L dependency=/tmp/cargo-installQyepjN/armv7-unknown-linux-musleabi/release/deps -L dependency=/tmp/cargo-installQyepjN/release/deps --extern libc=/tmp/cargo-installQyepjN/armv7-unknown-linux-musleabi/release/deps/liblibc-2305531b0b6bff17.rmeta --cap-lints allow -C relocation-model=pic -C prefer-dynamic=off -C target-feature=+crt-static,-vfp2,-vfp3` (exit code: 1) warning: build failed, waiting for other jobs to finish...
error

This was originally found in https://github.com/shadowsocks/shadowsocks-rust/issues/459 .

Changed in libc is already merged. Consider fixed the lowest libc version in the next release.

Thanks for finding and solving the problem @zonyitoo.

Sorry to borrow this issue, but I found out aarch64-unknown-linux-musl and x86_64-unknown-linux-musl targets are also broken the same way and made a pull request to libc crate to get SO_INCOMING_CPU implemented there.
PR: https://github.com/rust-lang/libc/pull/2119

Until the next version of libc is released, is there a known workaround, such as pinning a specific version of libc or socket2?

@fbecart can you run cargo update, updating the libc crate? That should resolve this issue.

Thank you @Thomasdezeeuw for pointing me in the right direction. I realize the problem is currently fixed for a specific set of architectures only. I'm building for i686-unknown-linux-musl, for which an issue likely still exists. I'll redirect my attention to libc.

There are still many architectures missing SO_INCOMING_CPU in the libc crate. Could @Thomasdezeeuw make sure that all Linux-like platforms have this definition in libc?

I am not sure that target-env = "uclibc" has SO_INCOMING_CPU definition. It is left for others to make patches. :)

I think this issue is really with libc, not with socket2.

I meet this issue too.
error[E0425]: cannot find value `SO_INCOMING_CPU` in crate `libc`
    --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.4.0/src/sys/unix.rs:1201:69
     |
1201 |             getsockopt::<c_int>(self.inner, libc::SOL_SOCKET, libc::SO_INCOMING_CPU)
     |                                                                     ^^^^^^^^^^^^^^^ not found in `libc`

error[E0425]: cannot find value `SO_INCOMING_CPU` in crate `libc`
    --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.4.0/src/sys/unix.rs:1217:23
     |
1217 |                 libc::SO_INCOMING_CPU,
     |                       ^^^^^^^^^^^^^^^ not found in `libc`

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0425`.
error: could not compile `socket2`

To learn more, run the command again with --verbose.

how to work around?

@JinAirsOs you can disable the all feature for now to work around it. Otherwise I think https://github.com/rust-lang/libc/pull/2135 would fix this issue.


[Launcher] Buttons not showing when hovered with mouse

When hovered with mouse, buttons are not showing anymore.

Fixed in 0.19.0, please visit https://github.com/microsoft/PowerToys/releases/ for the latest release


FEAT: Saving intermediate images

When I generate image with 512x768px size it generates nice image but it takes long time and I was wondering if it's possible to get more images by saving intermediate images as well to a separate folder named exactly as the image generated just without .png
Why it's useful:

It allows to optimize steps parameter with different samplers and different resolutions
It allows to see how the image evolves over time

I have created the same Issue in @basujindal fork at https://github.com/basujindal/stable-diffusion/issues/75
I believe this feature could be useful in both forks. I use @basujindal fork to generate max size images on 8GB VRAM GPU and @lstein for anything else.

See https://github.com/lstein/stable-diffusion/issues/99#issuecomment-1229048855 as to why this may not be what you desire. The intermediary images aren't that different from the final image, besides being more blurry and fuzzy and unrefined.
It is possible to do though, the samplers have callbacks that could be added to save the image of every Nth step.

See #99 (comment) as to why this may not be what you desire. The intermediary images aren't that different from the final image, besides being more blurry and fuzzy and unrefined.
It is possible to do though, the samplers have callbacks that could be added to save the image of every Nth step.

I have discovered that k_euler_a never converges to one image. You will see a different result even on 10,000 steps. I made and posted a video upto 500 steps on reddit /r/StableDiffusion. You can see it keeps changing till the end. I then separately run jumps upto 5000 and 10000 and it still changes.
TL;DR, intermediate results are useful in case of k_euler_a

I added the ability to watch images get rendered in the webui here if you want to play with it. As @BlueAmulet says, intermediates aren't really useful. They're even less useful with other samplers, like the default k_lms. Here's "a dragon flying past a sunset, oil painting" with the same settings at 40-of-40 steps vs 40-of-50 steps:

I tried before latest pull locally and was getting errors on img.save saying it wasn't. Thought i should pull before diving in further. Came to github and here you have it. Thank you :)

I have discovered that k_euler_a never converges to one image.

The images in that comment are of k_euler_a. Changing the number of steps does change the resulting final image yes, but the intermediary of k_euler_a at step 50 of 100 total, does not look like the final result of k_euler_a at 50 steps total.

I have discovered that k_euler_a never converges to one image.

The images in that comment are of k_euler_a. Changing the number of steps does change the resulting final image yes, but the intermediary of k_euler_a at step 50 of 100 total, does not look like the final result of k_euler_a at 50 steps total.

Oh I now understand what you are saying. And you are right, if that's the case than they won't be of much use.


Update documentation

The README and docs are pretty sparse at the moment and we should include some high level descriptions of how XBRL parsing actually works. Most people are not very familiar with XBRL, so it would be helpful to have a brief overview of what XBRL is, how it's structured, and how we are working with it.

Added high level overview of XBRL, and XBRL extraction. Also added more detailed usage to README.


Fix 'Commit and push version increment' step in Azure DevOps

Despite ending up green, git push fails apparently due to status checks.
Tag is pushed correctly, though.
Only known workaround used in AoCHelper is disabling the Required status checks step in repo's configuration.
How about giving  admin:repo_hook permissions to that Api Key?
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   Examples/FileParserExample/FileParserExample.csproj
	modified:   NugetTest/NugetTest/NugetTest.csproj
	modified:   src/FileParser/FileParser.csproj

no changes added to commit (use "git add" and/or "git commit -a")
[master 7b94a97] Release v1.4.3
 3 files changed, 3 insertions(+), 3 deletions(-)
remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: 8 of 8 required status checks are expected.
To https://github.com/eduherminio/FileParser
 ! [remote rejected] master -> master (protected branch hook declined)
error: failed to push some refs to 'https://github.com/eduherminio/FileParser'
To https://github.com/eduherminio/FileParser
 * [new tag]         v1.4.3 -> v1.4.3
Finishing: Commit and push version increment

Release pipeline has been moved to GitHub Actions.
Required status check are kept disabled for now, though.


[Api Discussion via docs] Adding a more manual/advanced scalapb rule

In the change i made to make these rules aspect based previously it has blocked/made difficult  some of scalapb's options that don't translate well into aspects (and aren't supported in the java protobuf so don't come up there). This proposes adding another rule which would give full flexibility in invoking the scalapb to cover these use cases.
Using both rules in a repo does pose the risk of classpath conflicts of multiple implementations that are different of the same class name. Though I don't see a way around this issue in general. We could have the direct rule check to ensure none of its dependencies also contain the same class name it is emitting, to ensure it doesn't depend on an aspect for the same protobuf?
Thoughts @ittaiz @simuons @johnynek ?

@ianoc thanks for taking the time!
We are interested in the aspect approach for performance and since the current approach generates multiple copies of dependent protos (causes issues in IJ as well).
We are planning towards end of next week to prototype a suggested API on how to support multiple custom generators using toolchains and aspects. We might fail but we want to give it a try :)

In general I'm not against this if you have concrete use-cases internally you're aware of.
I think that the conflict check can be valuable depending on cost (both build time and dev time)

We don't have them internally, the use cases that were coming up are:
https://github.com/bazelbuild/rules_scala/issues/765
https://github.com/bazelbuild/rules_scala/issues/753
https://github.com/bazelbuild/rules_scala/issues/751
so if your work managed to cover these and we didn't need it at all that would be better again

Very interesting. #751 and #753  indeed sound very very similar to our needs and concerns.
This is what we'll try to solve (don't know if we'll be able to though).
Can you or @johnynek refresh my memory about why aspects are better?
My idea before the aspect approach was to separate the "to-be-generated" protos from the "classpath" protos (which I'm fairly certain is an option in protoc). This should solve the multiple copies of a proto appearing in the scala classpath later on and will also greatly improve performance (less generation and less compilation in the next step).
Am I missing something? Are these indeed the benefits but you think I'm mistaken about protoc support for this?

@ittaiz You can with protoc for sure separate out the proto's from having multiple copies. (using the internal function of src to jar thats in there now would do this). The aspects make the whole chain fully automatic which is the big win(to add the aspects to our largest scala repo i had to add the toolchain then strip the per-target options -- so a pretty simple PR, it immediately dropped 6-8 minutes off average our CI times for the repo which was super nice). Aspects make a few things better here though:

You don't need to define the scalapb targets at every step of the chain. In our case this is huge since we have cross language bazel dependencies/generated proto's and similar, so you can define the scalapb in the repo you need it/where you need it and all of the intermediate targets are automatically supplied
You don't have folks globbing protobuf files/proto_library targets out of laziness into one scalapb (well they can, but internally via the aspect thats not what will happen).
With the former two issues you can wind up with 2 scalapb's referring to the same proto_library without a bunch of tooling/convention to stop it. So the aspects ensure you don't get duplicated classes from this.
Not the aspects so much, but the fact the options are configured on the toolchain while a pain for the extra options in scalapb makes the whole repo consistent in how the scala is generated which is a plus. (Mostly here the flat_package option has caused us problems in the past)

I think mostly what I was suggesting here is pretty close to what you were thinking about doing pre-aspects here, just having a rule that wouldn't produce all the classes all the time.

@ianoc any plans to pick up work on this PR again?

No I'm afraid there didn't seem to be a consensus on design to drive it. So I've long since moved onto other things.

closing as stale, feel free to reopen


Gas calculation implementation

Those that are in is_unimplemented is not implemented... They require us to implement the "machine state" struct first.

Thanks!

are you using the nightly or beta?

okay don't worry my rustc env was running 1.15.0 which fails with this error: https://github.com/rust-lang/rust/issues/37544 this is negligible. rustc in nix-shell has no issues.


[DDW-91] fix broken styling for options bubble within select component

This PR fixes an issue with the way the OptionsSkin was included in the SelectSkin component which resulted in non-configurable styles, since always the default theme was chosen instead of the raw / configurable version.

@MarcusHurney please review these changes and fixes … maybe you have to port them over to your refactoring PR!


Improvement: Exclude ODBC Tables

We have a lot of ODBC based Tables in our access databases.
ucanaccess is unable to load the access database because it fails to load these with the following error:
UCAExc:::5.1.0 TableDefinition has no data access (Db=Test1.accdb; Table=some_odbc_table_name
As ucanaccess will probably never be able to import ODBC based tables, it should exclude ODBC tables from the list of tables.
I would propose ... function createTables in src\main\java\net\ucanaccess\converters\LoadJet.java should check if table is ODBC_LINK and not add them to the list.
Line: 1070 ...
                if (t2 != null && t != null && !tn.startsWith("~")) {

                    TableMetaData tableMetaData = t2.getDatabase().getTableMetaData(tn);
                    if (tableMetaData.getType() == TableMetaData.Type.LINKED_ODBC) {
                        logger.log(Level.WARNING, "Table {0} is linked to an ODBC table. Skipped ...", tn);
                        unresolvedTables.add(tn);
                    }else{
                        createTable(t);
                        loadingOrder.add(t.getName());
                    }
                }
...

Hi @thr27!
Thanks for raising this issue. Your suggestion sounds quite reasonable. I will look into it shortly
Markus

Hi @thr27, incorporated you suggestion. Please review

Thank you


ppc64le specific changes added to prow config

Signed-off-by: Valen Mascarenhas<EMAIL_ADDRESS>
Which issue(s) this PR fixes:

@cardil  Could you please merge this PR , if all looks good ?


AppInsights cannot link to App Service/Function App

Is your feature request related to a problem? Please describe.
When you declare an application insights instance, you need to specify a special tag that looks like
            "tags": {
                "name1": "value1",
                 // ...
                "hidden-link:/subscriptions/<subscriptionId>/resourceGroups/<rg-name>/providers/Microsoft.Web/sites/<appName>": "Resource"
            },

Since the name is a variable and the tags property is an object, you cannot specify this tag, since it must be variablized.
Describe the solution you'd like
support variables in property names (#267) or change the tags property to be an array of name/value pairs instead of an object.

This is possible in ARM so I vote to be possible in Bicep.

Is this special tag required - meaning the deployment will fail if this is not specified? This seems like a major anti-pattern..

the deployment succeeds, and i think the app service will even log into app insights, but if you go into the azure portal, and select the insights pane of the app, it acts like no insights is hooked up.  Comparing exported ARM before and after, the only difference was the hidden-link tag.  There might be other odd tags that start "hidden-" when working with app services and insights.  Googling around I don't see much documentation about the hidden tags.
https://stackoverflow.com/questions/38578122/what-does-hidden-link-mean-in-azure-resource-manager-tags
https://docs.microsoft.com/en-us/azure/azure-monitor/app/powershell#parameterize-the-template
https://winterdom.com/2017/08/01/aiarm

I see. I still do not love this pattern, but that is a fight for another day :)
We are going to allow string interpolation in property names as part of #267 as you noted @sethwenzel. I'm thinking I will close this and add this as another example to 267. Thoughts?

@alex-frankel yep very bad practice from some Azure teams. I think they do not do it anymore but of course there are some legacy stuff. I mainly have seen this on monitoring resources.

I actually feel like the name value pair sets should probably be array of 2 property objects - similar to the app service's app settings.  If you changed the tags to be array of 2 property objects, you wouldn't have to wait to develop #267.  Something fishy about using variables in property names to me.  This isn't php.

@sethwenzel It is not like we want to use it. We forced to use these kind of things either trough bad practices or because not well written RPs. Overall it is the nature of JSON that allows that so Bicep will have to inherit some of these capabilities because of that.

Also, to help anyone that stumbles across this issue trying to link their app service to application insights via bicep/ARM:
we have a workaround doing 2 deployments,
deployment 1:
bicep transpiled to JSON arm template, deployed in Complete mode
deployment 2:
raw JSON arm template to add the needed tag, deployed in Incremental mode
what happens is deployment 1 will remove the link, but deployment 2 will add it back.  The link appears to be an Azure portal thing, so I think there isn't harm in temporarily deleting it.
Here's an example ARM template resource snippet to add the needed link:
        {
            "type": "Microsoft.Insights/components",
            "apiVersion": "2020-02-02-preview",
            "name": "[variables('insightsName')]",
            "location": "[parameters('location')]",
            "kind": "web",
            "properties": {
                "Application_Type": "web"
            },
            "tags": {
                "[format('hidden-link:{0}', resourceId('Microsoft.Web/sites', variables('siteName') ) )]": "Resource"
            }
        }

Didn't understand the workaround as it is not bicep code but ARM Template code. Also deploying in complete mode is dangerous as you might wipe out other resources.


Try PATCH common-types fix

Choose a PR Template
Switch to "Preview" on this description then select one of the choices below.
Click here to open a PR for a Data Plane API.
Click here to open a PR for a Control Plane (ARM) API.

/azp run


rce fixed

What kind of change does this PR introduce?
This is a fix for the rce occured at the port of killProcessOnPort.

What is the current behavior?

killProcessOnPort("& touch vulnerable #"); is executed.

What is the new behavior (if this is a feature change)?

File vulnerable is no longer created.

Other information:

Still working for other ports.

@thppn - are you able to re-open using this template with the required bounty URL?
Cheers! 🍰

Sorry, @thppn - it looks like the maintainer has not selected your fix this time...
We appreciate your effort and look forward to seeing more of your fixes in the future! 🛠
If you have any questions, feel free to join our community Discord and a member of our team will be happy to help! 🤗


pull request for e2e test at 12/16/2016 15:26:18

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


Enable Read Only property via connection string

Currently, to mark a transaction as read only and have the driver distribute it to read members of the cluster, you need to use the method setReadOnly method (connection.setReadOnly(true);). However this is only accessible via code, if you are using a 3rd party client and don't have access to the code, there is no way to do this, making all calls go to the LEADER.
Enable a way to tell the jdbc that the statement is read only, could be via a parameter passed in the connection string or some other functionality that does not require code change in the 3rd party tools.

Hi @rhaces can you test the following jar?
You should be able to pass the readOnly flag in this way:
jdbc:neo4j:bolt://localhost?readOnly=true
neo4j-jdbc-driver-3.4.0.jar.zip

After testing the attached driver with SquirrelSQL, I don't see that the flag is working, I'm setting up SquirrelSQL as shown below and I can still send a "CREATE" cypher, where if the readTransaction is correctly being used, the cypher would fail.
Class Name: org.neo4j.jdbc.Driver and org.neo4j.jdbc.boltrouting.BoltRoutingNeo4jDriver
URL: jdbc:neo4j:bolt+routing://localhost:7627?readOnly=true
Jar file used:
$ ls -ls /home/rodrigo/Downloads/neo4j-jdbc-driver-3.4.0.jar
5848 -rw-r--r-- 1 rodrigo rodrigo 5985110 Mar  9 18:29 /home/rodrigo/Downloads/neo4j-jdbc-driver-3.4.0.jar
$ md5sum /home/rodrigo/Downloads/neo4j-jdbc-driver-3.4.0.jar
3ca3d3b94921f87992cfdeaedd25503d  /home/rodrigo/Downloads/neo4j-jdbc-driver-3.4.0.jar

After doing some additional debug, the issue is that we are calling the variable readOnly however the getProperties() for some reason brings the properties all lowercased, not sure if this is a JDBC standard or something else. See the two attached screenshots, notice how in the first one readOnly=false and when I evaluate getProperties I see  (second screenshot) readonly=true


Fixes slowness when side menu is opened

Previously, every update from the worker updated density and color state stored in the Plates component. This caused constant re-renders to occur while the side menu was opened. Now, the state of Plates is only updated by the model once, upon initialization.

I've been looking at it more. The previous densities and plate color update was definitely wrong.
It was causing that React component was updated on every single message from the model worker. I've added a log message to componentDidUpdate to confirm that. When you comment out densities and plate colors update, componentDidUpdate isn't called when new data from worker arrives.
In other words, we're triggering React re-render cycle on every message from the model worker. It's still not strictly related side menu, but well, it's a bit of UI and since it was re-rendered all the time, it could cause slowness on your machine (and perhaps some others).
If you use equality check, I think that it should solve the problem.

Thanks for thinking through this @pjanik! Good point about the problematic assumptions. I now do the updates based on an equality check, while still preventing model updating loops. I did add Underscore to the project to get deep equality checking, let me know if you have another preference.
I also snuck in a second commit that fixes an unrelated sorting bug I found in my density component.

lodash is used more often than underscore in other CC projects (and in the broader JS community), so unless there's a particular reason to prefer underscore for this, lodash might be a better choice.

I'd agree with Kirk. Or actually, if it's just for comparison, I'd just use some tiny deep equal npm package or write it myself, as it's a few lines. It's not even a deep equal (just one level).

Thanks @kswenson and @pjanik! FWIW the equality check is two levels deep since plateColor is an HSV object...I did originally write my own equality check, but figured a library would be simpler than writing something more flexible. I could try a deep equal library like this one, but I feel like we might have uses for lodash in the future? I don't have a good feel for how it affects performance to pull it in.

You can also use techniques like those discussed in https://stackoverflow.com/a/35251059 to just import the function(s) you need from lodash.

Oh great! Based on the comments at that link, Webpack 2 uses tree shaking (a new term for me) so that import { has } from 'lodash' should only import the necessary file. I assume it's alright for us to rely on that?

In any case, now using lodash instead of underscore!

@kswenson, thanks, that's really nice trick. I was reluctant to add the whole lib just for one function, but that completely solves the problem (and lodash funcs are nice).
@ekosmin,

Based on the comments at that link, Webpack 2 uses tree shaking (a new term for me) so that import { has } from 'lodash' should only import the necessary file. I assume it's alright for us to rely on that?

Not really, even though we use Webpack 3. I've checked that and import { isEqual } from 'lodash' was adding 0.6MB to the built file. import isEqual from 'lodash/isequal' added pretty much nothing. Maybe I'm missing some optimization flags, but I'd play safe and use lodash/<filename> syntax in the future. I've pushed a commit to fix that.


testing pullapprove on release branch

This PR addresses GitHub issue: #
Briefly describe the changes proposed in this PR:

...
...
...

Make sure you've followed the Contributor Guidelines. In particular (please tick to indicate you've taken care of it):

[ ] RDF4J code formatting has been applied
[ ] tests are included
[ ] all tests succeed

does this work? Approved

Approved


Blazor Hybrid tutorials to adopt dark theme

Description
The three Blazor Hybrid tutorials should adopt the dark VS UI theme.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/hybrid/tutorials/?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/hybrid/tutorials/index.md
Document ID
d5bd6238-32fa-35ee-34d1-02c193a96fbb
Article author
@guardrex

Duplicate of #30255.


Dynamic Visuals for Ride Vehicles

Idea
Please describe what you'd like to see added or changed.
An idea that I have is for the ability to pick a certain spot on the track and have the ride vehicles automatically change visuals on that spot. In my mind, it could work similar to the Advanced Track plug-in.
So if there was a Transformers-themed coaster, the ride could start with a street-race section with automobile cars and then at a set point on the ride, the cars would visually at least change to look like Optimus Prime(then there would obviously be a 2nd location where it would switch back to the original).  I know the vehicles actually changing shape mid-ride is not realistic, but my thought is this could be used to simulate a VR type ride experience, where this kind of thing would be possible.
Thanks.
Additional context
Add any other context, screenshots, related information about the feature request here.

Hey jhadenfeld93,
Thank you for your suggestion!
I like your idea, unfortunately it's currently not really possible to implement such functionality in the plugin. An important idea of this plugin is that everything you do will still work if you save the park and send it to someone who does not have the plugin. What AdvancedTrack does not fit that rule; all its features will stop working once you open the park without the plugin.
Fortunately there is an alternative that is build into RCT2/OpenRCT2 and it could work without any using plugins, by using a custom created vehicle specifically for this purpose. Each variant of that vehicle will need to specify which variant it swaps to after it will go through a log flume reverser (there's a property for this inside the object). If done correctly, then instead of just reversing the vehicle, this trick can allow you to chain together 4 different stages/variants, without any plugins at all. 😄 But because this setting is inside the object itself, it cannot be controlled by a plugin like RideVehicleEditor.
Hope it helps! If you have any more questions or suggestions, feel free to let me know. 🙂

OK.
I am working on a Pokémon themed park and I thought I could use something like this to build a Ditto Coaster that would travel around the park racing/dueling each other coaster in turn.
And when it would race a certain other Pokémon coaster, its track, color scheme, and ride vehicles would change to match its companion coaster.
I appreciate the response and I can still do the track and color scheme at least.

Why 4 variants?
Is that a property of the vehicle itself?
And are you saying the reverser log flume track just switches from 1 variant to the next?
If so, that might be workable.

@jhadenfeld93 Vehicles in the vanilla game are limited to a maximum of 4 variants. AFAIK OpenRCT2 has not yet raised this limit for custom vehicles.
The specific property I'm talking about is this one: logFlumeReverserVehicleType. It specifies which variant to switch through after entering a log flume reverser.
Hope it helps. :)

Thanks. I do have one other suggestion or request that I think would fit with your design philosophy.
Would there be a way to save the trains on a ride as a template for use later?
What I mean is I have a giga coaster with 6 trains that are each 6 cars long and most of the cars have their own unique color scheme.
So would it be possible to allow me to save the setting for all of those as a template so when I place the coaster I can simply open my template for that coaster and apply the colors all at once instead of having to go through all 36 cars individually?

@jhadenfeld93 I think that's a nice idea that could be implemented yes. Would you like to make a different issue for that or shall I make one for it? 😀

Whatever works better for you.
I ran into that issue when my Eevee ride crashed.
After resetting it, I had to go back and manually change all the colors back.
That was tedious.
But thanks.


spike test bugfix: first & last values are unknown

If abs(inp[0])>threshold or abs(inp[-1]>threshold), then the test marked that value as QC FAIL. But the spike test is not really defined for the first or last values in the array. So always set those flags to QC unknown.

@kwilcox do you have time to review? I hope this is straightforward enough. Honestly I don't know how we didn't catch this before.

Love thy neighbors, no?


Save forward transforms

In addition to saving the reverse transform, which in this case transforms light
sheet volumes into CCF space, I am also saving the forward transform, i.e. the
mapping that puts the CCF into light sheet space.
Since "warp_transforms.nii.gz" (the inverse transform) is ambiguous when two
warp transforms are saved, I have renamed it "ls_ccf_warp_transforms.nii.gz".
The forward transform is "ccf_ls_warp_transforms.nii.gz"
The affine transform is the same for both the forward and inverse transform, so
it is still only saved once.
Closes #12

FYI I haven't tested this since I don't have write permissions to the code ocean assets.

I managed to test this without pushing to s3: https://codeocean.allenneuraldynamics.org/capsule/3762229/tree.
Both transforms are there!


version 1.21

Seems that I can't set backup mode anymore
Barrys-MacBook-Pro:~ barrymurphy$ curl -sk --header "Authorization: Bearer TjrnGcgW9qE4NUE69l6ed6GOz01N7nbAoB_CEZbLbyglSpqUr2VxcTd-iqlaby2YzwJw7TZ4EDkCTRZpzfh9zA==" -X POST -d '{"mode":"backup","backup_reserve_percent":15}' http://<IP_ADDRESS>:81/api/operation
{"code":500,"error":"RealMode must be either self_consumption or backup","message":"Unable to set operational mode"}Barrys-MacBook-Pro:~ barrymurphy$

seems sending real_mode backup fixed this issue

Confirmed; real_mode resolves the 1.21 issue
Thanks @icepicknz ;)

Real_mode works for backup or self_consumption but not autonomous. It only seems possible to set that through the app now. This is the case regardless which mode the unit is currently in.
Anyone achieved a workaround?
{"code":500,"error":"RealMode must be either self_consumption or backup","message":"Unable to set operational mode"}


add Repeat Interval

@d4vidi This looks like a great addition, having repeat interval for local notifications.
Please merge :)

any progress?

@lidanh please have a quick look. @toanz, thanks - I'd really appreciate you also updating the docs!
Last but not least: what about Android?

Following up on this. What else needs to be done for this feature?

It would be useful to have this feature, is there anything else we can do or can this be merged now?

Please merge if good!?

What is the status on this .. is it available?


You can not start jumping

Start the game
Click in up arrow -> the dog doesn't jump

It's a feature, the dog starts "agachao" and you need to make them to move so if you want to jump, first you need to be on their foot


How about something like Final by Default

Probably a check which checks if the class is not marked with @Open or abstract should not have any subclasses.
On a related note, it will be a great thing to have FinalByDefault (similar to NonNullByDefault) baked in the type system via EP check or checker framework.

If it's not @Open or abstract though then what is it? Isn't final all that's left?

Fair point. Just avoiding the keyword final. It should be declared @Open or abstract. In the current check Non-final, Non-abstract classes without the @Open annotation will be marked with an error.. How about just treating them as final.

That still allows their subclassing by downstream libraries. I suppose if the type isn't effectively public then perhaps the check shouldn't apply?

Oh. Didn't think of this use case.


Create 2024-07-03-csail-network

Notification of possible ESI and MAAS service interruption on July 15, 2024

no longer needed


proxy host can be use domain

like this : PROXY_URL="socks5://host.docker.internal:7890"
fix "proxy host.docker.internal has invalid value or is not numeric"

I don't think it's a good idea to convert the domain into IP in the Dockerfile.
host=$(nslookup $host | grep -A1 'Name:' | tail -1 | awk '{print $2}')
It means the IP address will be fixed, once the container is started. However, in some cases, the results of DNS will be change.
So, is there a better way to solve this problem? Mayby, the nslookup should be used for each of the proxy connection?

I found that proxychains can only support configuration in IP format. Therefore, it is suitable to use proxychains to proxy some programs that run for a short time, but it may not be suitable for proxying web services such as ChatGPT Next.
In fact, according to the configuration requirements of proxychains, the first proxy in the ProxyList must be in IP format, while the subsequent proxies (second and third) can be in domain name format (which means that it will use the first proxy to perform DNS resolution for all subsequent domain name proxies). However, this clue is not helpful for our current problem.


Localization

Any plans to have the localized version in English?

yes, we will have English version in version 1.2.0,  currently i am developing the version 1.1.0
issue link: https://github.com/dyc87112/spring-cloud-config-admin/issues/45

@dimapasko


[feature] menu-close for swippable ion-items

Currently, when clicking on a ion-option-button element, the options don't disappear. It would be nice to have a way to close them (just like menu-close for side menus).

Greetings @arcanis!
Thank you for the feature request. We will review this further and possibly add it to our Feature Request board if we feel it is appropriate for Ionic.
Thank you for allowing me to assist you.


fix: misleading error message for prepare cmd

Fix misleading error that shows missing maxRevision.json for deployment failures

Codecov Report

Merging #851 (102e4c3) into develop (96f3421) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #851   +/-   ##
========================================
  Coverage    66.22%   66.22%
========================================
  Files           46       46
  Lines         1593     1593
  Branches       342      342
========================================
  Hits          1055     1055
  Misses         538      538

Continue to review full report at Codecov.

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


Metadata for an Asset definition

We'll have to update an asset definition example with metadata that is currently possible to add.
Current example:
import iroha2.data_model.asset as asset

time = asset.Definition(
    value_type=asset.ValueType.Quantity,
    id=asset.DefinitionId(name="time", domain_name="looking_glass"),
    # Here
    metadata={},
    mintable=False
)

According to @QuentinI, the proper keys for metadata have to be the Values and defined like that:
from iroha2.sys.iroha_data_model import Value

time = asset.Definition(
    value_type=asset.ValueType.Quantity,
    id=asset.DefinitionId(name="time", domain_name="looking_glass"),
    # Here
    metadata={"a": Value.U32(10)},
    mintable=False
)

This seems to work properly, judging by the Hyperledger Iroha Community Telegram.
I believe we'll need to discuss what Value types might be there, how those are used and add proper examples.

Initial Hyperledger Iroha Community question is located here.

https://github.com/hyperledger/iroha-2-docs/pull/104 fixes the example.

I believe we'll need to discuss what Value types might be there, how those are used and add proper examples.
There was a line that said that metadata is outside the scope of the tutorial, so for me it seems as a "nice-to-have". I'd close this issue (bc the example is fixed), and then open a new one (e.g. "Add a topic discussing metadata") marking it as an enhancement


unable to override theme of SearchDelegate

Steps to Reproduce

import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatefulWidget {
  @override
  _MyAppState createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> with WidgetsBindingObserver {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Title',
      home: Scaffold(
        appBar: AppBar(
          actions: [
            Builder(
              builder: (context) => IconButton(
                icon: Icon(Icons.search),
                onPressed: () => showSearch(context: context, delegate: CustomSearchDelegate()),
              ),
            ),
          ],
        ),
      ),
    );
  }
}

class CustomSearchDelegate extends SearchDelegate {
  @override
  List<Widget> buildActions(BuildContext context) => [
        if (query.isNotEmpty)
          IconButton(
            icon: Icon(Icons.close),
            onPressed: () {
              query = "";
              showSuggestions(context);
            },
          )
      ];

  @override
  Widget buildLeading(BuildContext context) => IconButton(
        tooltip: 'Back',
        icon: AnimatedIcon(icon: AnimatedIcons.menu_arrow, progress: transitionAnimation),
        onPressed: () => close(context, null),
      );

  @override
  Widget buildSuggestions(BuildContext context) => Text("Suggestions go here");

  @override
  Widget buildResults(BuildContext context) => Text("Results go here");

  @override
  ThemeData appBarTheme(BuildContext context) {
    final ThemeData theme = Theme.of(context);
    return theme.copyWith(
      primaryColor: Colors.white,
      primaryIconTheme: theme.primaryIconTheme.copyWith(color: Colors.green),
      primaryColorBrightness: Brightness.dark,
      textTheme: theme.textTheme.copyWith(
        title: TextStyle(fontWeight: FontWeight.normal),
      ),
      // these ↓ do not work ☹
      appBarTheme: theme.appBarTheme.copyWith(color: Colors.black12, elevation: 0),
      inputDecorationTheme: theme.inputDecorationTheme.copyWith(
         focusedBorder: OutlineInputBorder(
            borderSide: BorderSide(
            color: Colors.red,
            width: 1,
           style: BorderStyle.solid,
         ),
        borderRadius: BorderRadius.all(Radius.circular(24)),
        gapPadding: 4,
      ),
      ),
    );
  }
}

Target Platform: android
Target OS version/browser: 9
Devices:
Logs

Running "flutter pub get" in muqel-front...                         0,6s
Analyzing muqel-front...
No issues found! (ran in 2.6s)

[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Mac OS X 10.15.1 19B88, locale fr-FR)
    • Flutter version 1.9.1+hotfix.6 at /Users/fahembelili/Development/flutter
    • Framework revision 68587a0916 (2 months ago), 2019-09-13 19:46:58 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/fahembelili/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = /Users/fahembelili/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.2.1, Build version 11B500
    • CocoaPods version 1.7.5

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 41.1.2
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[!] IntelliJ IDEA Community Edition (version 2019.2.4)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

[✓] VS Code (version 1.40.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.6.0

[✓] Connected device (1 available)
    • AOSP on IA Emulator • emulator-5554 • android-x86 • Android 9 (API 28) (emulator)

! Doctor found issues in 1 category.

The error occurs, as far as I can see, because the AppBarTheme in libr/src/material/search.dart is not added to the widget tree. Instead, the AppBarTheme is obtained from the delegate using this line:
    final ThemeData theme = widget.delegate.appBarTheme(context);

From this theme the primaryColor, primaryIconTheme, primaryTextTheme, primaryColorBrightness, textTheme.title and the inputDecorationTheme.hintStyle is then used to style the AppBar and the TextField.
The information from the AppBarTheme is not used, which is why you probably got confused. The good news is that you can still customize many properties of the AppBar, the bad news is that there is no way to change the brightness, elevation and actionsIconTheme of the AppBar.
One way for you to change the elevation would be to copy the search.dart class and write your own class e.g. custom_search.dart where the elevation is taken from the theme of the delegate. The solution would be fine in the short term, but in the long term, search.dart should probably be improved.
After the Principle of least surprise, I see the following criticism of the existing search.dart code:

The delegate method is called appBarTheme, which sounds like the method should return an AppBarTheme, not a Theme.
The name appBarTheme implies that the appBarTheme is used in the appBar and not, for example, the primaryColor of the theme.
There is no way to change brightness, elevation and actionsIconTheme. In my opinion elevation is especially problematic, because according to the Material Guide the elevation can have the same elevation as the content if it's not scrolled. (In my app the elevation in the app bar is 0, until the user scrolls, except for the search (without the custom_search.dart fix).)

In my opinion the problem cannot be changed without breaking changes and is rather a minor problem. If there is interest, I could submit a PR and propose some changes.

tested with issue https://github.com/flutter/flutter/issues/56574
the issue occur in both the latest stable and the latest master

Reproducible on the latest master 1.21.0-2.0.pre.66.

flutter doctor -v
[√] Flutter (Channel master, 1.21.0-2.0.pre.66, on Microsoft Windows [Version 10.0.18362.900], locale et-EE)
   • Flutter version 1.21.0-2.0.pre.66 at C:\Development\flutter_master
   • Framework revision 54c9441723 (2 days ago), 2020-07-17 18:56:12 -0400
   • Engine revision d327828632
   • Dart version 2.9.0 (build 2.9.0-21.0.dev 9dca49e71e)

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
   • Android SDK at C:\Users\Isa\AppData\Local\Android\sdk
   • Platform android-30, build-tools 30.0.0
   • Java binary at: C:\Users\Isa\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\193.6626763\jre\bin\java
   • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
   • All Android licenses accepted.

[√] Chrome - develop for the web
   • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.6.4)
   • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
   • Visual Studio Community 2019 version 16.6.30309.148
   • Windows 10 SDK version 10.0.18362.0

[√] Android Studio (version 4.0)
   • Android Studio at C:\Users\Isa\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\193.6626763
   • Flutter plugin version 47.1.2
   • Dart plugin version 193.7361
   • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.47.2)
   • VS Code at C:\Users\Isa\AppData\Local\Programs\Microsoft VS Code
   • Flutter extension version 3.12.2

[√] Connected device (5 available)
   • SM G950F (mobile)       • ce12171c51cc001c03 • android-arm64  • Android 9 (API 28)
   • sdk gphone x86 (mobile) • emulator-5554      • android-x86    • Android 11 (API 30) (emulator)
   • Windows (desktop)       • windows            • windows-x64    • Microsoft Windows [Version 10.0.18362.900]
   • Web Server (web)        • web-server         • web-javascript • Flutter Tools
   • Chrome (web)            • chrome             • web-javascript • Google Chrome 84.0.4147.89

• No issues found!

This issue reaches far out as there are multiple ways I would like to change the delegate's app bar/text field theme but most of it just isn't supported in the current implementation which seems to cherry-pick certain theme params. The 2 open issues addressing this are
https://github.com/flutter/flutter/pull/55209
https://github.com/flutter/flutter/pull/58970
https://github.com/flutter/flutter/pull/55209 seems to be a more robust solution even though https://github.com/flutter/flutter/pull/58970 is getting the attention. Regardless I hope one of these can be implemented soon as I have multiple apps where I can't use the search delegate since it doesn't provide proper theme support.

Same issue for me, the cursorColor with SearchDelegate not working...  Flutter version 1.20.0 Stable

I'm looking to change the cursorColor on iOS. However the proposed pull request #55209 #58970 don't seem to be solving the problem in iOS because of line 1048 in text_field.dart
cursorColor ??= CupertinoTheme.of(context).primaryColor;

when fix