Distinguish between retriable and non-retriable error When publish a …

Description
Distinguish between retrialable and non-retriable errors when publishing messages with pubsub
Issue reference

Please reference the issue this PR will close: #5136
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[x] Created/updated tests
[x] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

Do I need to change this error, it also looks like a retriable error
https://github.com/dapr/dapr/blob/a85b29fbd745e4e963594133b578f1ce685110cb/pkg/runtime/runtime.go#L1934

Do I need to change this error, it also looks like a retriable error
https://github.com/dapr/dapr/blob/a85b29fbd745e4e963594133b578f1ce685110cb/pkg/runtime/runtime.go#L1934

Yes, it seems to be retriable.

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

@SpikeWong please resolve the conflicts.

Finished

A little bit curious why there are some e2e tests failed,  because they are unstable?

@SpikeWong please fix conflicts, we'll try to get this merged right after 1.10 is out the door.

similar changes if possible needs to be added to the bulk subscribe API as well

milestone tracked by issue closed by this PR


make teuthology-openstack great again

Not only making it working again this PR contains several useful features and fixes.
Among them teuthology-openstack run several clusters per region.

This PR is supposed to be a replacement for #1028

This PR is hopefully the latest big portion of commits with features and functionality developed in suse/teuthology repo. Though, minor patches can be submitted later. After merging the suse/teutholgy master branch will be declared as legacy and renamed correspondingly, afterwards it will be a copy of ceph/teuthology master.

Hm, I wonder if we need to reintroduce buildpackages. It seems like dead code to me.

Hm, I wonder if we need to reintroduce buildpackages. It seems like dead code to me.

This is a good point, however it will be not trivial to remove it from this PR, rather than issue another cleanup commit on top of it. However, we were able to build ceph rpms package without shaman.

@susebot run deploy

@susebot run deploy

@susebot run deploy

@gregsfortytwo could you please review

@gregsfortytwo thanks, that is expected.

Following requirements.txt was proof to be working with changes in this PR.
--index-url https://pypi.python.org/simple/

-e .

boto==2.39.0
cffi==1.11.2
cliff==2.2.0
cryptography==2.7
fasteners==0.14.1
keystoneauth1==2.12.1
idna==2.6
openstacksdk==0.9.5
os-client-config==1.21.1
osc-lib==1.1.0
oslo.config==3.17.0
oslo.i18n==3.9.0
oslo.serialization==2.13.0
oslo.utils==3.16.0
pycparser==2.18
pyopenssl==16.2.0
python-cinderclient==1.9.0
python-glanceclient==2.5.0
python-keystoneclient==3.5.0
python-neutronclient==4.1.1
python-novaclient==6.0.0
python-openstackclient==3.2.0
requests==2.18.4

It needs to replace the one in master and should be include in deployment testing branch. I do not include it within this PR, because versions of packages are older than in recent setup.py/teuthology and could probably break dependencies for libcloud.
Though the current python-openstackclient has higher version in the master it is not backward compatible with this code. The corresponding separate PRs of switching to the latest and greatest openstack libraries as well as libcloud will follow.

This PR broke teuthology-lock for me on my workstation.  https://tracker.ceph.com/issues/42543

This PR broke teuthology-lock for me on my workstation. https://tracker.ceph.com/issues/42543

interesting... this may be because of this 5ac7c2f ?

This PR broke teuthology-lock for me on my workstation. https://tracker.ceph.com/issues/42543

Could you please try this on the box where you can reproduce this issue
https://github.com/ceph/teuthology/pull/1344

This PR broke teuthology-lock for me on my workstation. https://tracker.ceph.com/issues/42543

Could you please try this on the box where you can reproduce this issue
#1344

Confirmed.


Update tooling links

Fixes #4373
@scottaddie @mairaw Looks like there's a bad 🐁 in the redirect 🕰. The link:

https://technet.microsoft.com/itpro/powershell/windows/pki/new-selfsignedcertificate

... redirects to ...

https://docs.microsoft.com/powershell/module/pki/new-selfsignedcertificate

... but should go to ...

https://docs.microsoft.com/powershell/module/pkiclient/new-selfsignedcertificate?view=win10-ps

... perhaps because it changed modules without an update to their redirect file.

@guardrex,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

I'll send this to Sanketh as well to see if we can fix the redirection issue.


Channel Negative Energy - Harm Living

This ability as a base cleric is dealing 1 damage only instead of the 1d6 it is supposed to. When looking at the battle report to see the roll it says 0=1 = 1 damage dealt. I've turned off everything relating to character creation or gameplay and tried again but it is still 1 so I don't know if it's something that got broke by the mod or a base game issue. I reported this on Nexus Mods too I just wanted to make sure you guys got it.

 Apparently, it does 1 damage for the 1st level, which should be clearer, and then correct 1d6 for the 2nd.


Dependency based redecompilation

Is your feature request related to a problem? Please describe.
Any change to the state of the database causes a flushing of the decompilation cache. This is inefficient and a major pain point on large binaries and/or large functions.
Related issues are:
https://github.com/NationalSecurityAgency/ghidra/issues/1883
https://github.com/NationalSecurityAgency/ghidra/issues/1871
Describe the solution you'd like
Certain changes should instead lead to a re-decompilation (ideally, pushed to background threads, but removing them from the cache is also fine) of only some functions in the cache which depend on the changed values. The obvious candidates are:
a.) Local variables and comments -> should only affect the current function. As mentioned in https://github.com/NationalSecurityAgency/ghidra/issues/1871, directly modifying the decompile tree followed by rebuilding the XML is theoretically possible, although as an initial version I would not mind just re-decompiling the current function.
b.) Changes in the function prototype or parameter renames should change the current function and mark all decompiled callers of the function for redecompilation
c.) Mapping which functions have decompiled output dependent on a type/structure definition is probably a stretch goal, but could be possible (similar to the find use of type/field feature already in ghidra).
Describe alternatives you've considered
I have resorted to using reflection from scripts to directly interact with the decompiler cache while performing the changes outlined in (a) and (b).

I would like to add that any change to the state of one program's database causes the decompiler cache to be flushed for ALL open programs. This a royal pain when manually comparing programs.

I'm seriously considering 😄 creating a dozen or so extra github logins, just so that I could give this a few more thumbs up.

This is a big issue for large functions -- I have some pathological cases that take several minutes to decompile, and having to wait every time I add a comment or rename a variable can get frustrating.
I'm experimenting with ways to fix this, at least for my own use (as a starting point, I've modified DecompileProvider.domainObjectChanged to ignore events that surely will never affect decompilation, such as saving!) -- but it would be good to know if the Ghidra team have any work ongoing in this area, or opinions on implementation strategies.
Ultimately I don't think a perfect solution is possible with the current architecture: undo/redo actions only send DO_OBJECT_RESTORED which inherently requires a full refresh.  But the situation can certainly be improved!

A simple approach we have taken with other widgets is to mark them as potential being out-of-date.   This, along with a refresh button would prevent excessive work while still providing some signal that the data may need to be updated.

I don't think it's possible to implement cleanly in a script or extension, though, so doing this properly would involve adding some special-case handling to the core decompiler plugin.

The devil is in the details.  It is certainly possible to update the existing fields, but that would require extra logic to listen to and process events to detect those changes and update accordingly.   This is an interesting suggestion that goes with the 'stale' concept mentioned above.


Could we have Find?

Problem
I cannot find the Find in the menu.  The Browser version has it, perhaps because the Browser has it.
Proposed Solution

Additional context

Hi @frohro https://github.com/jupyterlab/jupyterlab_app/releases/tag/v3.1.13-1 is now published and the Find should be back in the menu. Thank you for reporting this issue!


nnnC VARYING converts to UCS2(nnn) VARYING instead of VARUCS2(nnn)

A definiton of a UCS2 field with varying length is not converted to VARUCS2 as it should be.

@AG1965 Please provide an example of fixed and correctly converted free format code for this.

Sorry for my multiple commits related to this issue.  I kept thinking I was doing something wrong in my commit message as the issues were linked, but not closed.  I think linking to an issue will auto-close only if you are the creator of the issue.  So, the pull request #79 from the BrianGodsend/vscode-rpgfree fork does fix this issue.


Issue with tf.py_func, tf.Tensor.set_shape and tf.Queues

This works fine:
import tensorflow as tf
x = tf.py_func(lambda: 42, [], tf.int64)
x = reshape(x, [1])
sess = tf.Session()
y = tf.train.shuffle_batch([x], 32, 64, 32)
coord = tf.train.Coordinator()
threads = tf.train.start_queue_runners(sess=sess, coord=coord)
sess.run(y)

But simply setting the shape with tf.Tensor.set_shape instead of reshaping does not work:
import tensorflow as tf
x = tf.py_func(lambda: 42, [], tf.int64)
x.set_shape([1])
sess = tf.Session()
y = tf.train.shuffle_batch([x], 32, 64, 32)
coord = tf.train.Coordinator()
threads = tf.train.start_queue_runners(sess=sess, coord=coord)  # Fails here.
sess.run(y)

2017-09-01 20:46:12.585027: W tensorflow/core/framework/op_kernel.cc:1192] Invalid argument: Shape mismatch in tuple component 0. Expected [1], got []
2017-09-01 20:46:12.585264: W tensorflow/core/framework/op_kernel.cc:1192] Invalid argument: Shape mismatch in tuple component 0. Expected [1], got []
INFO:tensorflow:Error reported to Coordinator: <class 'tensorflow.python.framework.errors_impl.InvalidArgumentError'>, Shape mismatch in tuple component 0. Expected [1], got []
	 [[Node: shuffle_batch/random_shuffle_queue_enqueue = QueueEnqueueV2[Tcomponents=[DT_INT64], timeout_ms=-1, _device="/job:localhost/replica:0/task:0/cpu:0"](shuffle_batch/random_shuffle_queue, PyFunc)]]

Even though this works fine:
import tensorflow as tf
x = tf.py_func(lambda: 42, [], tf.int64)
x.set_shape([1])
sess.run(x)

I think set_shape is just a hint to the shape inference code to fill in unknown shapes, and doesn't reshape the underlying Tensor. You should just use reshape here (which you report works). Closing for now, but please reopen if I misunderstood the issue.


awscli: 1.19.97 -> 1.20.25

Motivation for this change
Updates
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[X] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

This breaks nixops
ERROR: Package 'botocore' requires a different Python: 2.7.18 not in '>= 3.6'

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 134862 run on x86_64-linux 1

10 packages marked as broken and skipped:

awsebcli
mlflow-server
python38Packages.pathy
python38Packages.spacy
python38Packages.spacy-transformers
python38Packages.textacy
python39Packages.pathy
python39Packages.spacy
python39Packages.spacy-transformers
python39Packages.textacy

3 packages failed to build and already failed to build on hydra master:

checkov: log was empty
python38Packages.gradient: log was empty
python39Packages.gradient: log was empty

8 packages failed to build and are new build failures:

awscli2: log was empty
buildbot: log was empty
(python39Packages.buildbot): log was empty
buildbot-full: log was empty
(python39Packages.buildbot-full): log was empty
buildbot-ui: log was empty
(python39Packages.buildbot-ui): log was empty
nixops: log was empty

139 packages built:

aws-adfs (python39Packages.aws-adfs)
aws-google-auth
aws-mfa
aws-sam-cli
awscli
awslogs
barman
bash-my-aws
certbot-full
cloud-custodian
credstash (python39Packages.credstash)
deja-dup
duplicity
duply
dvc-with-remotes
elasticsearch-curator
git-remote-codecommit
home-assistant
iceshelf
lexicon
luigi
mapproxy
nimbo
python38Packages.aiobotocore
python38Packages.aws-adfs
python38Packages.aws-sam-translator
python38Packages.aws-xray-sdk
python38Packages.boto3
python38Packages.botocore
python38Packages.buildbot
python38Packages.buildbot-full
python38Packages.buildbot-ui
python38Packages.cartopy
python38Packages.celery
python38Packages.certbot-dns-route53
python38Packages.cfn-lint
python38Packages.chalice
python38Packages.credstash
python38Packages.dependency-injector
python38Packages.django-anymail
python38Packages.django-raster
python38Packages.djmail
python38Packages.ec2instanceconnectcli
python38Packages.fiona
python38Packages.flower
python38Packages.flowlogs_reader
python38Packages.fs-s3fs
python38Packages.gensim
python38Packages.geopandas
python38Packages.hass-nabucasa
python38Packages.mapbox
python38Packages.moto
python38Packages.mypy-boto3-builder
python38Packages.mypy-boto3-s3
python38Packages.osmnx
python38Packages.pyathena
python38Packages.pycognito
python38Packages.pyhiveapi
python38Packages.pynamodb
python38Packages.rasterio
python38Packages.s3fs
python38Packages.s3transfer
python38Packages.sapi-python-client
python38Packages.scrapy
python38Packages.scrapy-deltafetch
python38Packages.scrapy-fake-useragent
python38Packages.scrapy-splash
python38Packages.serverlessrepo
python38Packages.slack-sdk
python38Packages.slicedimage
python38Packages.smart-open
python38Packages.snowflake-connector-python
python38Packages.snowflake-sqlalchemy
python38Packages.tensorboardx
python38Packages.warrant
python39Packages.aiobotocore
python39Packages.aws-sam-translator
python39Packages.aws-xray-sdk
python39Packages.boto3
python39Packages.botocore
python39Packages.cartopy
python39Packages.celery
python39Packages.certbot-dns-route53
python39Packages.cfn-lint
python39Packages.chalice
python39Packages.dependency-injector
python39Packages.django-anymail
python39Packages.django-raster
python39Packages.djmail
python39Packages.ec2instanceconnectcli
python39Packages.fiona
python39Packages.flower
python39Packages.flowlogs_reader
python39Packages.fs-s3fs
python39Packages.gensim
python39Packages.geopandas
python39Packages.hass-nabucasa
python39Packages.mapbox
python39Packages.moto
python39Packages.mypy-boto3-builder
python39Packages.mypy-boto3-s3
python39Packages.osmnx
python39Packages.pyathena
python39Packages.pycognito
python39Packages.pyhiveapi
python39Packages.pynamodb
python39Packages.rasterio
python39Packages.s3fs
python39Packages.s3transfer
python39Packages.sapi-python-client
python39Packages.scrapy
python39Packages.scrapy-deltafetch
python39Packages.scrapy-fake-useragent
python39Packages.scrapy-splash
python39Packages.serverlessrepo
python39Packages.slack-sdk
python39Packages.slicedimage
python39Packages.smart-open
python39Packages.snowflake-connector-python
python39Packages.snowflake-sqlalchemy
python39Packages.tensorboardx
python39Packages.warrant
s3bro
s4cmd
snakemake
sourcehut.buildsrht
sourcehut.coresrht
sourcehut.dispatchsrht
sourcehut.gitsrht
sourcehut.hgsrht
sourcehut.hubsrht
sourcehut.listssrht
sourcehut.mansrht
sourcehut.metasrht
sourcehut.pastesrht
sourcehut.todosrht
ssm-session-manager-plugin
streamlit
tts

Result of nixpkgs-review pr 134862 at d1699efa run on x86_64-linux 1

12 packages failed to build:

awscli2
checkov
mlflow-server
nixops
python38Packages.gradient
python38Packages.pathy
python38Packages.spacy
python38Packages.textacy
python39Packages.gradient
python39Packages.pathy
python39Packages.spacy
python39Packages.textacy

11 packages skipped due to time constraints:

awsebcli
home-assistant
lexicon
python38Packages.slack-sdk
python38Packages.spacy-transformers
python39Packages.dependency-injector
python39Packages.mypy-boto3-builder
python39Packages.mypy-boto3-s3
python39Packages.spacy-transformers
python39Packages.tensorboardx
...

136 packages built successfully:

aws-adfs (python39Packages.aws-adfs)
aws-google-auth
aws-mfa
aws-sam-cli
awscli
awslogs
barman
bash-my-aws
buildbot (python39Packages.buildbot)
buildbot-full (python39Packages.buildbot-full)
buildbot-ui (python39Packages.buildbot-ui)
certbot-full
cloud-custodian
credstash (python39Packages.credstash)
deja-dup
duplicity
duply
dvc-with-remotes
elasticsearch-curator
git-remote-codecommit
iceshelf
luigi
mapproxy
nimbo
python38Packages.aiobotocore
python38Packages.aws-adfs
python38Packages.aws-sam-translator
python38Packages.aws-xray-sdk
python38Packages.boto3
python38Packages.botocore
python38Packages.buildbot
python38Packages.buildbot-full
python38Packages.buildbot-ui
python38Packages.cartopy
python38Packages.celery
python38Packages.certbot-dns-route53
python38Packages.cfn-lint
python38Packages.chalice
python38Packages.credstash
python38Packages.dependency-injector
python38Packages.django-anymail
python38Packages.django-raster
python38Packages.djmail
python38Packages.ec2instanceconnectcli
python38Packages.fiona
python38Packages.flower
python38Packages.flowlogs_reader
python38Packages.fs-s3fs
python38Packages.gensim
python38Packages.geopandas
python38Packages.hass-nabucasa
python38Packages.mapbox
python38Packages.moto
python38Packages.mypy-boto3-builder
python38Packages.mypy-boto3-s3
python38Packages.osmnx
python38Packages.pyathena
python38Packages.pycognito
python38Packages.pyhiveapi
python38Packages.pynamodb
python38Packages.rasterio
python38Packages.s3fs
python38Packages.s3transfer
python38Packages.sagemaker
python38Packages.sapi-python-client
python38Packages.scrapy
python38Packages.scrapy-deltafetch
python38Packages.scrapy-fake-useragent
python38Packages.scrapy-splash
python38Packages.serverlessrepo
python38Packages.slicedimage
python38Packages.smart-open
python38Packages.snowflake-connector-python
python38Packages.snowflake-sqlalchemy
python38Packages.tensorboardx
python38Packages.warrant
python39Packages.aiobotocore
python39Packages.aws-sam-translator
python39Packages.aws-xray-sdk
python39Packages.boto3
python39Packages.botocore
python39Packages.cartopy
python39Packages.celery
python39Packages.certbot-dns-route53
python39Packages.cfn-lint
python39Packages.chalice
python39Packages.django-anymail
python39Packages.django-raster
python39Packages.djmail
python39Packages.ec2instanceconnectcli
python39Packages.fiona
python39Packages.flower
python39Packages.flowlogs_reader
python39Packages.fs-s3fs
python39Packages.gensim
python39Packages.geopandas
python39Packages.hass-nabucasa
python39Packages.mapbox
python39Packages.moto
python39Packages.osmnx
python39Packages.pyathena
python39Packages.pycognito
python39Packages.pyhiveapi
python39Packages.pynamodb
python39Packages.rasterio
python39Packages.s3fs
python39Packages.s3transfer
python39Packages.sagemaker
python39Packages.sapi-python-client
python39Packages.scrapy
python39Packages.scrapy-deltafetch
python39Packages.scrapy-fake-useragent
python39Packages.scrapy-splash
python39Packages.serverlessrepo
python39Packages.slack-sdk
python39Packages.slicedimage
python39Packages.smart-open
python39Packages.snowflake-connector-python
python39Packages.snowflake-sqlalchemy
python39Packages.warrant
s3bro
s4cmd
snakemake
sourcehut.buildsrht
sourcehut.coresrht
sourcehut.dispatchsrht
sourcehut.gitsrht
sourcehut.hgsrht
sourcehut.hubsrht
sourcehut.listssrht
sourcehut.mansrht
sourcehut.metasrht
sourcehut.pastesrht
sourcehut.todosrht
ssm-session-manager-plugin
streamlit

4 suggestions:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/botocore/default.nix:43:3:
   |
43 |   meta = with lib; {
   |   ^

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/s3transfer/default.nix:47:3:
   |
47 |   meta = with lib; {
   |   ^

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/boto3/default.nix:40:3:
   |
40 |   meta = {
   |   ^

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/s3transfer/default.nix:50:0:
   |
50 |     description = "A library for managing Amazon S3 transfers";
   | ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

Ah, this makes sense now. I froze all the dependencies nixops has, so they are compatible with Python 2.

NixOps on master is currently broken. Otherwise this should be good now.
~/dev/nixpkgs master λ nix-build -A nixops                                                                                1 ↵
error: brotlicffi-<IP_ADDRESS> not supported for interpreter python2.7
(use '--show-trace' to show detailed location information)


VC detailed layout is not ocupying the spaces properly

Describe the bug
VC detailed layout is not ocupying the spaces properly
To Reproduce

Open app and head to home page
click on add ID and download VC
Go back to home
Open the downloaded VC card

Current behavior
The card layout not occuping the available space properly when data is lengthy.
Expected behavior
The layout should occupy the available space properly when data is lengthy.
Screenshots

Smartphone (please complete the following information):

Device: iPhone7 & iPhone XR
OS: 15.4.1
Inji app version: 0.4.0 (16) in test flight
MOSIP Version: 1.2.1
MOSIP server: qa-121.mosip.net

Additional context
Android issue is registered https://github.com/mosip/inji/issues/200

@rakhimosip The above issue was solved by increasing the number of lines in modules VcItem.tsx. I also adjusted the same problem in singleVcItem.tsx I raised PR and sent it to @Sujithbn. The code review was still pending.
Respective Screenshot

@Sujithbn @Anushree09-N The above Issue was resolved in android and raised PR(#472) and submitted.


Translations don't move to 'unused' when removed

If you change a string inside your application (maybe due to active development when no translations have been made yet), the old string still sticks in the generated po file while the new string is added. This pollutes the po files on every compile run (see #158).
The original behaviour was to comment them out and keep them for reference.

The fix I've put here is to change the extracted comment to "NO LONGER USED" rather than comment it out - I hope that has the same effect, but avoids potential problems with parsing comments

Good enough for me, if someone wants a different behavior, we can discuss their PR to that effect.


NASDAQ screener

Add support for pulling in NASDAQ screener ticker data.

This doesn't programmatically download the screener files, which would be nice. I just manually downloaded them.
Note this doesn't solve the problem of all caps comments are parts of comments causing spurious ticker counts.


SRM: Removed feature flags

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)
OPS-13475

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Removed FFs from SRM and CV docs based on the Jira ticket OPS-13475.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://655d9d8118098160bb403191--harness-developer.netlify.app


Update dependency ifdef-loader to v2.3.1

This PR contains the following updates:

Package
Type
Update
Change

ifdef-loader
devDependencies
patch
2.3.0 -> 2.3.1

Release Notes

nippur72/ifdef-loader
v2.3.1
Compare Source

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (2.3.1). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


rc return for vector::at_size_kind() is not always set

rc should be set to 0 for in bounds references if present.

I think this has been dealt with.


JSON Mode

Description of the feature request:
Didn't the announcement video specifically mention about json mode? I'm unable to find a flag for it in the API. and asking to gemini-pro to send a JSON output returns invalid json data
What problem are you trying to solve with this feature?
JSON parsable output for building apps
Any other information you'd like to share?
No response

Can you give me a reference? I can't find any mention of this.
Maybe you're referring to function calling? We're working on better documentation  and support, but it does allow you to define a function and the input schema, and if it returns a FunctionCall instead of a test response, the FunctionCall uses the described schema.
Example [WIP]: https://github.com/MarkDaoust/generative-ai-docs/blob/function-docs/site/en/tutorials/function_calling_python_quickstart.ipynb

I am probably mistaken then. The feature I was talking about is Gemini returning parsable JSON Strings for normal questions too. Makes it follow a pattern for production apps using Gemini This is something which OpenAI brought to their Client in November. Although Gemini does send Valid JSONS from my tests up until now if asked in the prompt but the Formatting of the completion is messed up.
Sometimes it adds a

Here is the JSON you requested for
"JSON ... "
And sometimes it doesn't do any of it

Which can honestly be fixed with a Regex
It would be great if there was a first party JSON mode implementation abstracting that from the developers

Can you give me a reference? I can't find any mention of this.
Maybe you're referring to function calling? We're working on better documentation and support, but it does allow you to define a function and the input schema, and if it returns a FunctionCall instead of a test response, the FunctionCall uses the described schema.
Example [WIP]: https://github.com/MarkDaoust/generative-ai-docs/blob/function-docs/site/en/tutorials/function_calling_python_quickstart.ipynb

Kinda disappointed this was missing from the launch. The models are fun to play with, but the API and client as a whole has been frustrating to work with.

The API needs to have a way to return valid JSON otherwise its a waste of time.

Why Is this even offered as a part of firebase solution, when I can't even get back a guaranteed valid JSON response?

I agree it would be great to support the response_format tag of the OpenAI schema, including JSON mode.

I'm also looking for a valid JSON format with Python SDK for chat history, if the feature still does not exist do we have any workaround to achieve the same?

@hetvi01 I was initially just using regex to fix whenever we had invalid JSONs but it kept giving more and more weird jsons so I'm just using gpt 3.5's json mode to fix the data as a fallback. You can use any of the local LLMs to achieve the same might be cheaper

I've tried feeding the invalid JSON back into a follow-up query asking basically "fix this invalid JSON".  Sometimes it works, sometimes it gives back different, but still invalid, JSON.  I'm surprised how badly the Gemini API behaves, especially as I'm trying to use it side-by-side with OpenAI api calls, and it just won't behave predictably.

right now the cleanest way is to strip the unwanted characters, literals and turn it into a valid JSON. I've even had to use dynamic properties because Gemini doesn't use consistent names for the objects returned, even when you specify to use an object name in the response

right now the cleanest way is to strip the unwanted characters, literals and turn it into a valid JSON. I've even had to use dynamic properties because Gemini doesn't use consistent names for the objects returned, even when you specify to use an object name in the response

@abdulqkhan  this would be the case if they only added unwanted characters. Sometimes they return a response with single quotes ' sometimes " double quotes inside a value isn't escaped. There are missing ,s at times properties aren't delimited with ,s. I am not sure if you have tested it enough. But unwanted characters isn't the only issue right now.

I have done a lot of testing, and have a few production apps deployed that are working fine with the manual stripping and parsing of the responses, ... are you providing a sample expected response along with your prompt?

Ofcourse I am. It hasn't broken for you probably because of the type of
content you are sending to the API. Its also running fine for me about 80%
of the times and failing for 20% for the same prompts with different content
On Tue, 20 Feb 2024, 12:04 abdulqkhan, @.***> wrote:

I have done a lot of testing, and have a few production apps deployed that
are working fine with the manual stripping and parsing of the responses,
... are you providing a sample expected response along with your prompt?
—
Reply to this email directly, view it on GitHub
https://github.com/google/generative-ai-python/issues/137#issuecomment-1953569011,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEJEA54QMPH5MVGLH6MJ75TYUQ7WLAVCNFSM6AAAAABA2TRVCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJTGU3DSMBRGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Bumping this up. Does anyone know if there is a formal feature request for the API on this?
Right now, it's a deal breaker as the JSON generation, including all manner of back flips to handle variously stripping out markdown artefacts (as noted above) and control characters (\u0000-\u001F). The actual JSON produced by Gemini is highly unreliable. This limits real-world usage for anything of any complexity.

The function_calling feature is the best way to do this. It lets you strictly describe the schema, and returns the data structure, not text you have to parse.
https://ai.google.dev/tutorials/structured_data_extraction
It doesn't use constrained decoding yet, so you can still get errors, but it's pretty good in my experience.

Sadly, this is an important feature still missing. I tried to clean the response manually but it seems there are a lot of cases.
@abdulqkhan could you share the code that is working for you? if possible.

This feature has been added to the API.
You can use it through REST right now.
We're working on the new release to include it, once 0.6.2 of google-ai-generativelanguage is out, we can merge https://github.com/google/generative-ai-python/pull/274 and make a new release.

Thanks for the update! @MarkDaoust

Making a request like this
genai.GenerativeModel("gemini-pro").generate_content(
    self.prompt,
    generation_config=GenerationConfig(response_mime_type="application/json")
)

now returns a 400 response like this
    @functools.wraps(callable_)
    def error_remapped_callable(*args, **kwargs):
        try:
            return callable_(*args, **kwargs)
        except grpc.RpcError as exc:
>           raise exceptions.from_grpc_error(exc) from exc
E           google.api_core.exceptions.InvalidArgument: 400 Json mode is not enabled for models/gemini-pro

../../../../.venv/lib/python3.12/site-packages/google/api_core/grpc_helpers.py:78: InvalidArgument

@dhruvkb > 400 Json mode is not enabled for models/gemini-pro
Not all odels support this setting try models/gemini-1.5-pro-latest.

As I recently put in this issue, JSON mode seems to have broken.

Hi, Is this done I am still struggling to get consistent Json

same the json output is still incosistent

Yes this should be working now.
See "Generate JSON from schema" in this example: https://github.com/google-gemini/cookbook/blob/674daad4057ff8c747417cb75bc4f91aed6324b8/quickstarts/JSON_mode.ipynb#Generate-JSON-from-schema
response_mime_type is just a suggestion, but setting a schema like this example activates constrained decoding, and should strictly follow the provided schema.


Use helpers for make API calls in request specs

Context
Soon, all requests will have to have a API token (https://trello.com/c/x4oJgpsK) and all POST requests  will have to send the meta data in the request body (https://github.com/DFE-Digital/apply-for-postgraduate-teacher-training/pull/289). To make this easier this commit adds a helper that we can use to add defaults to the request body and helpers. It doesn't do anything yet though.
Guidance to review
Do the method names make sense?
Link to Trello card
https://trello.com/c/x4oJgpsK

This is great. Could we add the metadata to the default post, so it's useful? I guess that will entail offering some way to override params:.

@duncanjbrown yes, but it might be better in https://github.com/DFE-Digital/apply-for-postgraduate-teacher-training/pull/289?
FWIW I'd do it something like:
def post_api_request(url, options = {})
  post url, options.deep_merge(params: { meta: [..] )
end

Sounds good — I'll rebase #289 with this enhancement when merged


[Validation] Validate navlink highlights links in a case-insensitive way

Validate that the link is highlighted when the link path is different from the casing on the url.

Waiting on a new build. Latest build from core-sdk doesn't contain the changes.

There was a missing case here, I have a fix for it, and a PR out.

Ok,
so the new fix has been merged.
Moving this issue to preview3 to redo the validation there.

I validated this with the latest nightly.


Send error with onUpdateFailed

It seems that currently the onUpdateFailed event does not pass an error to the event handler (judging from the source and docs). It would be nice to receive an error so that I can log and debug what went wrong exactly. Currently I only have the client data (browser, os, etc.), which doesn't tell me exactly what went wrong.

@ismay See https://github.com/NekR/offline-plugin/issues/243. Any contributions are welcome. Closing this as a duplicate.

Ah, didn't notice that one. Thanks!


Add cache_from command to docker compose

The local build time from docker compose is slow. To improve the build time we can use cache_from in the docker compose file.
This item is dependent on: https://github.com/open-telemetry/opentelemetry-demo-webstore/issues/78

on it 🖖


seekStation for whole freq form 0.15-30 and 30-230

As I understand this radio works on 0.15-30mHz AM and 30-230MHz FM
so I want to define only two bands:
{0, 19, 150, 30000, 28000, 3},
{1,  9, 300, 2300, 1270, 1}
As long as i use encoder this works nice, but once comes to seekStation
it only seeks within one of the predefined bands or even narrower:
760 to 900 kHz on AM and 87-108 MHz FM.
How to expand seeking on whole range without being using pin #4 of akc6955 as feedback?
Thank you!

Try to use setAM with the akc695x_am_band parameter greater than 17 (custom band). If you use setAM method with the first parameter (akc695x_am_band)  greater than 17, then the radio will be set to custom band.  Doing that, the seekStation method will consider the custom limits.
More information on API Documentation

That is how i set bands:
radio.setAM(18, 150, 30000, 27000, 3);
or
radio.setFM(8, 300, 2300, 1170, 1);
Band 18 for AM or 8 for FM should be good.
After calling
radio.seekStation(1, updateScreen);   // updateScreen is my version of your showFrequency.
I see it searching only 88-108 and some narrow AM about 800khz - 1.4mhz...
Doesn't goes beyond those limits..
May be the problem is my chip marked "AKC6951(55)" but 6951 doesn't support custom bands?
Is mine 51 or 55?
But I'm able to set  "radio.setFM(8, 300, 2300, 1170, 1);" and tune on over whole band with encoder!
Looks like I must use "tund" pin as sensing.

Your setup seems ok.
I need to check the library and also the Datasheet.  It is possible the
internal  device seek implementation (firmware) does not work for custom
bands.  My guess.  I’m traveling now. So, I can’t check it with my
prototypes.  When I back home I’ll start working on it.  For while I can
just check the code and Datasheet.
Regards.
Ricardo.
On Sun, 6 Sep 2020 at 11:17 Airrr17<EMAIL_ADDRESS>wrote:

That is how i set bands:
radio.setAM(18, 150, 30000, 27000, 3);
or
radio.setFM(8, 300, 2300, 1170, 1);
Band 18 for AM or 8 for FM should be good.
After calling
radio.seekStation(1, updateScreen); // updateScreen is my version of your
showFrequency.
I see it searching only 88-108 and some narrow AM about 800khz - 1.4mhz...
Doesn't goes beyond those limits..
May be the problem is my chip marked "AKC6951(55)" but 6951 doesn't
support custom bands?
Is mine 51 or 55?
But I'm able to set "radio.setFM(8, 300, 2300, 1170, 1);" and tune on over
whole band with encoder!
Looks like I must use "tund" pin as sensing.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pu2clr/AKC695X/issues/1#issuecomment-687801735, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVSJNEOTC625FNWTRS2MYLSEOKX5ANCNFSM4Q3AHH3A
.
--

QRZ: http://www.qrz.com/db/PU2CLR
Skype: ricardo_caratti
Mobile: +55 61 981442296

Some changes have been made that may have solved this problem.

not solved. still seek works on two predefined bands only.
hope someone will test it on true AKC6955, not AKC6951(55).

Ok. I will check this out more deeply. Also I'll bay some some AKC6955. Thanks for testing.


[Input] Rename TextInput to Input

[x] I have followed (at least) the PR section of the contributing guide.

Could you also fix up the docs page that's currently under /new/components/text-input and update the related references in the docs?


Some methods in SynchronizedMap don't use synchronization

I've looked into source code for SynchronizedMap and I'm not sure it's implemented correctly:
public LongSet keySet() {
    if ( keys == null ) keys = LongSets.synchronize( map.keySet(), sync );
        return keys;
    }
}

If multiple threads call this method at the same time, than mutliple LongSet instances might be created. They are thread-safe, so nothing bad will happen, but still it feels not right.
Moreover another method never sets the values variable:
public ObjectCollection<V> values() {
    if ( values == null ) return ObjectCollections.synchronize( map.values(), sync );
    return values;
}

Java's implementation in java.util.Collections.SynchronizedMap synchronizes the whole method:
public Set<K> keySet() {
    synchronized (mutex) {
        if (keySet==null)
            keySet = new SynchronizedSet<>(m.keySet(), mutex);
        return keySet;
    }
}

You're right, and it looks like a copy-and-paste thing, because UnmodifiableMap has the same problem.
Both "bugs" are efficiency bugs—the implementation is semantically correct. Of course the value thing must be fixed.
When I was writing these classes (like, 15 years ago? LOL), synchronization was very expensive. So it seemed to be sensible to create in some race condition two view objects (both very lightweight). I agree that the design for current JVMs should be different. I'll fix it.


Adding Gitlab support and setting Max concurrencies

@vachanalaviswanath I made some changes, can you let me know when you run the gitlab tests and I'll verify github?

One thing I forgot, we need to update the README as well

fixed two bugs

If you only configure github or gitlab, it threw a fatal error in getPats
github wasn't actually respecting the 'get me all repos' functionality of a <0 days old var, fixed it. Also discovered a bug because I assumed github paging starting at 0, it starts at 1, resulting in duplicate entries (page 0 and page 1 return the same results)

@vachanalaviswanath I made some changes, can you let me know when you run the gitlab tests and I'll verify github?

@LivingInSyn I have tested the gitlab and scan looks good to me. Thanks for refactoring my piece :)


The horizontal line fade out when adding a video

Issue:
When I add a horizontal line in SunEditor and after that add a video or image, the horizontal line fade out.
Steps to reproduce the issue:

Add horizontal line

Type space (Will add a line break before the horizontal line) )

Type the directional key top (This will change the teg hr into a p)

Add a video or an image

The 2.36.5 version has been updated.
If this issue has not been resolved, please reopen this issue.
Thank you.


Suggestion

[Enter feedback here]
"Use a local development environment -> Configuration -> Set up a Q# standalone or .NET environment"
followed by:
"Use a local development environment -> Configuration -> Set up a Q# Python environment"
is confusing for a beginner (like me)
The second subsection is essentially a subset of the first subsection.
I suggest

changing the order of the two subsections
add an explanatory note at the beginning of each subsection

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

ID: 49ab9f40-b7d0-a0b3-03b8-07af34bf1bbc
Version Independent ID: c51474b6-0c8d-c78b-294a-184ddbcd1bcf
Content: Set up a Q# standalone environment - Azure Quantum
Content Source: articles/install-command-line-qdk.md
Service: azure-quantum
Sub-service: qdk
GitHub Login: @Bradben
Microsoft Alias: brbenefield

Hi @johnehutchinson ! Thanks for your submission. We are currently working on a new article to clarify these questions that usually arise regarding the ways of running a Q# program and local development.
In the meantime, I will try to clear your doubts.
Please note that the introduction to these 2 topics can be found here Configure your local environment, the first section under  "Use a local development environment" node.
A Q# program can be run as standalone or can be invoked using a host program with Python, C# or F#.
In order to develop Q# + Python programs, one needs to install qsharp Python package, so that is the purpose of Set up a Q# + Python environment.
To run as standalone or use .NET CLI, no extra package is needed.

Thanks Sonia for the prompt reply!
I was really just pointing out some instructions I initially found somewhat confusing.
I have in fact eventually installed qsharp, using anaconda navigator, as an anaconda environment, on my university machine (mac).  It is running well, I have tested it on some of the quantum katas.
However, on my home machine, a macbook pro, the "same" qsharp environment installed in the same manner,  kills the kernel every time.  I'll try to clone the university copy of the environment, bring that home, and see if it still works.  (At guess I'll have a better chance than if trying to clone a single qubit 😀 )
John

On 10 May 2022, at 8:52 pm, Sonia Lopez @.***> wrote:
Hi @johnehutchinson https://github.com/johnehutchinson ! Thanks for your submission. We are currently working on a new article to clarify these questions that usually arise regarding the ways of running a Q# program and local development.
In the meantime, I will try to clear your doubts.
Please note that the introduction to these 2 topics can be found here Configure your local environment https://docs.microsoft.com/en-au/azure/quantum/install-overview-qdk, the first section under "Use a local development environment" node.
A Q# program can be run as standalone or can be invoked using a host program with Python, C# or F#.
In order to develop Q# + Python programs, one needs to install qsharp Python package, so that is the purpose of Set up a Q# + Python environment https://docs.microsoft.com/en-au/azure/quantum/install-python-qdk?tabs=tabid-conda.
To run as standalone or use .NET CLI, no extra package is needed.
—
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/quantum-docs/issues/543#issuecomment-1122232366, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZCE5QKETYVQGUKYP73SX53VJI5WVANCNFSM5VQOBPAA.
You are receiving this because you were mentioned.

Closing this issue as it had been addressed in the latest changes of the TOC. New article is https://learn.microsoft.com/en-au/azure/quantum/install-overview-qdk?tabs=tabid-vscode%2Ctabid-conda


Bump creekVersion from 0.2.1-SNAPSHOT to 0.3.0

Reviewer checklist

[ ] Read the contributing guide
[ ] PR should be motivated, i.e. what does it fix, why, and if relevant, how
[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage: 98.8%. Remained the same when pulling afd29351c17627c8c87b57b4c8c834aa4cf9dd5f on update-creek-v into 04d6d39f9401cc7eef9fd86375422877b1c5f40c on main.


Add version header for CmdStan

Submisison Checklist

[x] Run tests: ./runCmdStanTests.py src/test
[x] Declare copyright holder and open-source license: see below

Summary:
This PR adds a version.hpp header following the conventions of the Stan and Math libraries
Intended Effect:
The CmdStan version is currently only recorded in the Makefile, which means that any downstream users need to also include the makefiles in order to identify the version of the CmdStan headers & sources.
This allows downstream users to identify the version of the CmdStan headers/sources without needing to include & parse the makefile, improves consistency with the Stan & Math libraries
How to Verify:
Side Effects:
Documentation:
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company): Andrew Johnson
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Also tagging @serban-nicusor-toptal so he would know that there is a new file that needs updating each release!

Seems useful. Thoughts on having this be the version we put in the CSV files?

I don't see a case where the cmdstan and stan versions would diverge, but it depends on what we want to write in the file, the Stan version of the interface version. I think the Stan version?

I don't see a case where the cmdstan and stan versions would diverge

They've diverged right now (CmdStan is on 2.33.1, Stan on 2.33.0) because the latest bugfix release didn't require any changes to Stan or Math

Oh right. I don't really have a preference honestly, was just being nitpicky :)

I think given a cmdstan version, there is always a unique version of Stan shipped with that (we never update Stan without updating CmdStan) but the inverse need not be true (e.g., right now), so it seems reasonable to include the cmdstan version in the csv. It's not a big deal either way, I think


[GDScript LSP] Fix show_native_symbol_in_editor

This method does not seem to have been bound in any version since 4.0 was released
Regression from:

https://github.com/godotengine/godot/pull/36426

Can't test this myself as I don't use the LSP

Fixes: https://github.com/godotengine/godot/issues/92385

Thanks!

Thank you!


Confusing production message

When running in production:

This is literally never true, and is a silly thing to output. If blog_url is currently set as "http://my-ghost-blog.com" then it would make more sense to display a warning saying "blog url is not set" and instructions for how to set it

Gonna flag this up to @acburdine and close this. The new install process should make this problem go away :)


[Master Ticket] Add support for multi-delta reversion

Existing Work
A past sprint addressed basic support for reversion. This work currently supports reversion of a single delta. It currently has the following limitations

Poor test coverage to output impact ratio
No handling/distinction between clean/dirty reversions (More on this later)
Untested on real world data/situations

Although there are several differences between how data is stored at rest between Hecate and an OSM server, the rollback definitions and theory are relatively similar. Before reading the section of “Reversion Scenarios”, readers should have read the Change Rollback section of the OSM Wiki.
Reversion Scenarios
The following scenarios are real-work scenarios that we will encounter and need to support
Clean Reversion
Per the Change Rollback Wiki document, a clean rollback occurs when a rollback is being performed on a single “import” of deltas that have not been since modified.
Scenario

User has written an ML model to dramatically improve the geographic placement of address points in regards to building polygons
User downloads all the data in Maine, runs it through the script, performs some QA, and imports the improved data into Hecate
Discovers the next day that the ML model had very poor performance in rural areas that was missed in QA. No additional edits have been made to the data since the initial import, and the decision to rollback is made.

This form of version is by far the simplest to handle to handle as it requires the last amount of user interaction. A revert script could potentially perform the following actions to facilitate a rollback

Determination of the affected deltas

A single import of data can occur across multiple deltas when using HecateJS, due to size limitations imposed on the number of uploaded features in a given delta.
When performing large imports, these deltas can number in the 10s to 100s of unique deltas. To determine a start/end delta, the user must currently manually page through the delta listings until a start/end delta can be determined
This process could be streamlined by doing the following

Adding optional automatic paging support to the deltas list operation in HecateJS
Allow basic regex filtering of delta messages
d. The command line invocation to determine start/end delta could then look something like the following

./hecatecli deltas list --last 1000 --filter "Better US_ME Building Points"

Collection in some way of an inclusive “start” and “end” delta on which the reversion is to be performed.
./hecatecli revert --start  --end
./hecatecli reverse

The script will iterate through each delta and retrieve all features from each delta

The script will ensure unique feature IDs exist across all features to be reverted (This is  the first guarantee a “clean import” must have)

The script will iterate over each feature, retrieving the feature history of each individual feature

The script will ensure that the feature to revert is the latest version (the second guarentee of a “clean import”)

The script will perform whatever action is necessary (modify/delete/restore) to restore the previous state of the given feature and output a line delimited GeoJSON file.

The GeoJSON file is then run through QA/analysis and can be subsequently imported via the HecateJS import  process

Conflate Reversion
A conflate reversion occurs after a new data source is run through our conflate engine and imported into Hecate
Scenario

User runs a new OpenAddresses source through “lib/cache-oa” and runs the output through conflate
User uploads the output of the conflate script to Hecate
The data is determined to be subpar and a decision to rollback is made

Scenario

We lose a license to a given dataset and need to remove it

In this specific case, no reversion script is strictly necessary, although we can improve and streamline the following process, in both cases it is more straightforward to do the following:

Download all the data in the affected area using the HecateJS BBox or Bounds process
Filter the data via the source property
Add modify: delete key to each GeoJSON feature
Upload via HecateJS import process

Dirty Reversion
The dirty reversion scenario is the most complicated to handle in an efficient way. This occurs when a user uploads data to Hecate, and that data is subsequently edited before a reversion is performed.
Scenario

User performs a postcode update on all the data in US_ME and uploads the data to Hecate
A new feature is launched that includes the addition of a specific x property on each feature
The postcode update turns out to be bad and needs to be rolled back, but the new property x needs to be retained

This is the scenario that will take much more work to support. We should discuss this further and come up with a few sub-scenarios of how we would want to handle cases like this.
As a first pass we should be able to easily identify places where a dirty reversion is going to take place and warn/halt the reversion until we have better behavior/support for this style of reversion.
Next Actions
Based on our existing reversion support an our current editing velocity, I think we should work to support efficient and straightforward “clean reversions”. Based on two pass system for determining clean vs dirty reversion as described above, we can easily sandbox our current work to notify on dirty reversion and provide additional modes in the future for handling dirty reversions in different ways
Clean Reversion Tasks

Expand paging support on the Deltas to include start/limit based approach in addition to our current offset based approach. This will allow API calls to ensure that duplicates cannot be introduced into a list across multiple API calls if an additional delta is pushed while the list operation is occurring.
Write a “Feature History” module that:

Given a feature ID, retrieves the feature history
Determines if the feature has a clean reversion path
If clean, examine the existing code for generating a reversion of a single feature. It will likely need additional tests/potential modularization to tie
If dirty, generates a conflict

Write a “Delta Retrieval” module to page through all deltas between a given start/end value and ensure all ids are unique across the sample. If not, generate a conflict

We will likely want to explore caching this data to a sqlite file as almost none of the imports will be able to be stored in memory across their corresponding deltas
Once all features have been downloaded and cached, pass each feature to the “Feature History” module for reversion generation

We punted on using the delta list API and also on making any changes to it, instead simply using the fact that delta IDs are incremental to fetch deltas between a given start/end value


Quick view issue card jatin

Q
A

New sample?
yes

What's in this Pull Request?
This PR contains new cloumn json formatter sample which is used to view essential information about issues through hover cards, offering quick insights in a card format.

Thanks for the awesome sample @Jatin-patil 😍✨
This sample gives us a quick look at the content and is very useful!
I did the merge, check out the following link.
https://github.com/pnp/List-Formatting/tree/master/column-samples/generic-quickview-issue-card
Also, when merging, the content (Created By, Assigned To, etc.) was not displayed if the description was too long, so I added the overflow-y property and modified it so that the content can be viewed by scrolling.

Once again, I appreciate the excellent sample!

If you are interested, please register for the following program. When you register, you will get a digital badge!
M365 Platform & Power Platform Community Recognition Program
※Even if you register, it will not be distributed immediately. It will take some time before it is distributed.


[Bug report]: Unable to login to Ledger profile after receiving funds

Platform
Desktop
Version
Stardust 2.0-beta6
Description
Created a Ledger profile. Sent funds (SMR and T00KEN) from my "normal profile" to this newly created profile. When I logged out and tried logging into the normal profile I got to the first step of login "Initialising profile manager" and got "Something went wrong" in the lower right corner.
Error logs shows the following;

The last line says "Unable to reach the file since it is being used by another process".
Opening DevTools and console shows the following;

After restarting Firefly Stardust I was able to login to the Ledger profile, with my funds showing.
Expected behaviour
I expected to be able to login to the profile.
Actual behaviour
It stopped at the first step of logging in, threw "Something went wrong" and didnt work until restart of Firefly.
Can the issue reliably be reproduced?
No
Steps to reproduce the issue

Create a hardware profile.
Send funds from normal profile to newly created hw profile.
Log out of normal profile and try logging into hw profile.

Operating System
Windows
Diagnostics
Version
Language: en
Currency: USD
Node list: https://api.testnet.shimmer.network
Platform: win32
Platform Version: 10.0.19044
Platform Architecture: x64
CPU Count: 4
Total Memory: 8060.2 MB
Free Memory: 3565.2 MB

Developer Profile
Yes
Profile Type
Hardware (Ledger)
Staking
Never staked
Crash Status
Non-responsive
Error Messages
"Something went wrong" in lower right corner.
Error Logs
Invalid Date
undefined: Error: internal error in Neon module: error initializing account manager: Storage("IO error: Failed to create lock file: C:\\Users\\t00k\\AppData\\Roaming\\Firefly Stardust - Beta/__storage__/0aff772c92cb56240bf00b0bf28d7cfc/LOCK: Det g�r inte att komma �t filen eftersom den\r\nanv�nds av en annan process.\r\n")

Last line: "Unable to reach the file since it is being used by another process"

Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

[X] I agree to follow this project's Code of Conduct

If you open the Shimmer app on the ledger and login everything works as expected. If you logout and don´t close the Shimmer app on the ledger device and want to login a second time without closing the shimmer app the error appears.
Following steps to repro:

Open Shimmer app before login
Login to profile
Don´t close Shimmer app
Logout of profile
Login to the same profile
=> error appears

OR

Open Shimmer app after login
Don´t close Shimmer app
Logout of profile
Login to the same profile
=> error appears

The error doesn´t appear if the following steps are used:

Open Shimmer app before login
Login to profile
Close Shimmer app
Logout of profile
Login to the same profile without opening the Shimmer app
Logout of profile
Login to the same profile with Shimmer app opened
Logout of profile
Login to the same profile without opening the Shimmer app
Logout of profile
...

Can not reproduce @MiKeF05 @t00k can you reproduce on the latest beta?

Yes error is still present on the latest beta. I´m using windows 10 @nicole-obrien

Fixed in newer versions


Suspicious state from syntax checker gometalinter (using spacemacs)

Hello,
I'm using emacs 25.3 with spacemacs, up-to-date packages etc. I've installed and updated gocode and gometalinter, and ran gometalinter --install --update. However, when I open go file in project, I see the following:

Suspicious state from syntax checker gometalinter: Flycheck checker gometalinter returned non-zero exit code 3, but its output contained no errors: <?xml version="1.0" encoding="UTF-8"?> <checkstyle version="5.0">...

And XML follows with warnings description, at least I am able to read them and find mentioned warnings manually. What can be done to actually use flycheck instead of reading gometalinter XML output?
Thanks in advance

Can you reproduce the problem with vanilla Emacs and just flycheck-gometalinter installed? It is working fine for me and I'm not familiar with spacemacs.

Same error here with spacemacs.

For me the error was gone after removing or extending flycheck-gometalinter-deadline "10s" and other deadlines such as 	(setq flycheck-gometalinter-fast t) etc.


Update wasmer

Also had to ./devtools/update_crate.sh tracing because of some incompatibility between wasmer and the tracing version we were using before.
As well as bumping the minimum Rust version to 1.73
It seems we currently allow some simd float operations in the Gatekeeper. Those should be caught by the Validator in the ParsedWasm, but I moved them to the simd section of the Gatekeeper anyways (so they are now forbidden in the Gatekeeper too).
I'm also wondering if we could streamline the Gatekeeper changes a bit by using the wasmparser::for_each_operator! macro for matching whole proposals of operators. That would make it much easier to update in the future.

I'm also wondering if we could streamline the Gatekeeper changes a bit by using the wasmparser::for_each_operator! macro for matching whole proposals of operators. That would make it much easier to update in the future.

If it helps, sure. I don't this. I think the important thing is to ensure we do exhaustive matching.

update this comment

This version number wasn't bumped because the current_wasmer_module_version increased, so the cache gets invalidated already by that

Ah, that makes sense then. I didn't notice that v9 was not deployed yet


MIC-701 csip overview

Codecov Report
Attention: Patch coverage is 88.88889% with 4 lines in your changes missing coverage. Please review.

Project coverage is 91.66%. Comparing base (84b8f5a) to head (b0337b3).
Report is 1 commits behind head on main.

Files with missing lines
Patch %
Lines

...ngesupportinterventionplanapi/domain/CsipRecord.kt
0.00%
0 Missing and 1 partial :warning:

...gesupportinterventionplanapi/domain/CsipSummary.kt
80.00%
1 Missing :warning:

...rtinterventionplanapi/service/CsipRecordService.kt
66.66%
0 Missing and 1 partial :warning:

...rtinterventionplanapi/service/CsipSearchService.kt
50.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #187   +/-   ##
=========================================
  Coverage     91.66%   91.66%
- Complexity      727      741   +14
=========================================
  Files           130      131    +1
  Lines          2219     2244   +25
  Branches        160      162    +2
=========================================
+ Hits           2034     2057   +23
+ Misses          129      128    -1
- Partials         56       59    +3

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


why grpc trace wrong?

seems my grpc server use same ctx, have same traceid

Thanks for reporting. However, this issue belongs to parca-dev/parca.
We also added support for tracing to the agent-side #1684. It should help with context propagation.
I'm moving the issue to parca.


How can i disable the dragging the seek bar and remove button on seekbar ?

did you find any way to do that ?

seekBar.setUserSeekAble(false)


Upgraded to new version of angular and testcafe

Hi @AdaskoTheBeAsT, sorry for the late response.
Let me approve and merge this PR, but I'm not able to publish anymore on npmjs.com under the @politie organisation. @Bjeaurn @rkettelerij can you check this repo once in a while and keep it a up to date (and publish from time to time :))?

So sorry for the late response, I've just gotten the notification from a colleague that there's some PR's to be merged and I'm getting right to it. Let me sort these conflicts and check it out. Thanks for your work!


Gradient around the button?

Is it possible to put a gradient color around the button? From what I found so far, it's only possible to set a single color as background color.

It is not possible, sorry.


Taskbar icon menu won't close on de-focus

When right-clicking a program icon, there isn't a way to close the menu that comes up by de-focusing/clicking anywhere else. You must select one of the menu items to get it to close.

This has been fixed; please download the latest version from cairodesktop.com. Thanks!


Update Splice main to version 0.2.4-snapshot.20241001.7132.0.v15e29c45 (automatic PR)

This PR updates branch main of Splice from the latest changes as of version 0.2.4-snapshot.20241001.7132.0.v15e29c45, commit DACH-NY/canton-network-node@15e29c45b

#121


Fixes algorithm name (closes #13)

Changes algorithm name from aes256 to aes-256-cbc both in encrypt and decrypt.
Solves issue #13. After this edit, the tutorial works both with node and electron on Windows 10I didn't test it formally.

That's for the PR!
I merged this in along with some other updates to clean up the new Buffer(...) and replace it with Buffer.from(...). Also added some legacy test vectors to ensure that something like this doesn't cause breakages in the future if the output happens to change.
New version has been pushed to npm as v3.0.0.


Potential fix for Event.raiseEvent() typescript

I think this may be a fix for the Event.raiseEvent() type, as Parameters<Listener> is already a spread ...args: any[].  It looks like the additional spread operator is turning it into something like an ...any[][].
i.e. Listener extends (...args: any[]) => void so Parameters<Listener> would be an (...any[])
Issue: https://github.com/CesiumGS/cesium/issues/10498
    // before
    raiseEvent(...arguments: Parameters<Listener>[]): void;

    // after
    raiseEvent(arguments: Parameters<Listener>): void;

Thanks for the pull request @chris-cooper!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

I've just come up with a slightly terrible workaround, that I think actually kinda-sorta fixes it: https://github.com/thw0rted/cesium/tree/raiseEvent-fix
This manually replaces the invalid TS output during the Gulp post-processing phase.  I've used this crutch in the past to work around things that tsd-jsdoc can't quite do.  It's brittle, but hopefully if it breaks in the future, the simple tests I added will break and someone will notice.

Ok thanks @thw0rted .  I've tested your branch on our code and it allows removal of the @ts-expect-error s that were introduced with 1.95.  I think it would be preferable to incorporate either your workaround, or even a rollback to a more loosely typed raiseEvent() rather than imposing an incorrect type.

I've cherry-picked aee2bbfe135f77514c96170c877bce9907d81f0e and merged master in case you want to proceed with this PR, or feel free to close and open a  fresh one @thw0rted .

Thanks again for your contribution @chris-cooper!
No one has commented on this pull request in 90 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 90 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @chris-cooper!
No one has commented on this pull request in 90 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 90 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @chris-cooper!
No one has commented on this pull request in 90 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 90 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.


do not initialize Decimal from float

this avoid warnings and prefer explicit proper initialization
See https://github.com/LedgerHQ/app-bitcoin-new/pull/191

ACK 2692f7fa32d9acf6df917c97ec066b7a44333af4


profile-card sample added

Q
A

Bug fix?
no

New sample?
yes

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
This is simple user profile card built using List JSON Formatting

Thank you very much for the sample!
I adjusted a few items (see the commit log for details). Thanks again!


frozen graph convert error

Hey Hi,
Im running some sample tf-trt, i have been successfully build and compiled good, when i try to run;
python scripts/models_to_frozen_graphs.py
i got some import error, but i have downloaded all models from base source, is there anything i missed;
Traceback (most recent call last):
File "scripts/models_to_frozen_graphs.py", line 12, in
import slim.nets as nets
ImportError: No module named 'slim.nets'
Please give me some suggestion to resolve this issue, Thanks in advance

Hi varun-tangoit,
Thanks for reaching out.
It looks like the script can't find the third party 'slim' package.  Did you clone the repository with the --recursive flag set?  If not, you can just type
git submodule update --init

from inside the project.
Best,
John

From the root directory of a fresh git clone (with --recursive), can you try the following
From the terminal:
python

From within the python interpreter:
import sys
sys.path.append('third_party/models/research')
import slim.nets

If that succeeds, then calling
python scripts/models_to_frozen_graphs.py

should also succeed (provided you followed installation steps).
Let me know,
John

seems you have to switch to python2


AnimatedOpacity has erratic animation with colored Container as child (Flutter 3.13, iOS)

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
If you have an AnimatedOpacity with a colored Container as its child, it will animate erratically on iOS since the Flutter 3.13 update. In my screen recording you will see that displaying a CircularProgressIndicator makes the AnimatedOpacity animate smoothly, presumably because it forces the widget to refresh every frame.
I've noticed that an AnimatedOpacity with a different child, like FlutterLogo or Icon, does not exhibit this erratic animation problem.
Expected results
AnimatedOpacity with a colored Container child should smoothly animate its opacity.
Actual results
AnimatedOpacity with a colored Container child flashes and animates erratically.
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      title: 'AnimatedOpacity issue (Flutter 3.13)',
      home: HomePage(),
    );
  }
}

class HomePage extends StatefulWidget {
  const HomePage({super.key});

  @override
  State<HomePage> createState() => _HomePageState();
}

class _HomePageState extends State<HomePage> {
  bool isOpaque = true;
  bool displayProgressIndicator = false;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('AnimatedOpacity issue'),
      ),
      body: Column(
        children: [
          SwitchListTile(
            value: isOpaque,
            onChanged: (value) => setState(() => isOpaque = !isOpaque),
            title: const Text('Is opaque'),
          ),
          SwitchListTile(
            value: displayProgressIndicator,
            onChanged: (value) => setState(
                () => displayProgressIndicator = !displayProgressIndicator),
            title: const Text('Display progress indicator'),
          ),
          AnimatedOpacity(
            duration: const Duration(milliseconds: 1000),
            opacity: isOpaque ? 1.0 : 0.0,
            child: Container(
              color: Colors.red,
              height: 200,
              margin: const EdgeInsets.all(10),
            ),
          ),
          if (displayProgressIndicator)
            const Center(
              child: CircularProgressIndicator(),
            ),
        ],
      ),
    );
  }
}

Video demonstration
https://github.com/flutter/flutter/assets/37321068/459333b6-cc8f-4e46-af2c-3393aeae253d
Flutter Doctor output
Doctor output
Flutter (Channel stable, 3.13.0, on macOS 12.5.1 21G83 darwin-x64, locale
    en-GB)
    • Flutter version 3.13.0 on channel stable at
      /Users/mattperren/Desktop/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision efbf63d9c6 (6 days ago), 2023-08-15 21:05:06 -0500
    • Engine revision 1ac611c64e
    • Dart version 3.1.0
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/mattperren/Library/Android/sdk
    • Platform android-33, build-tools 30.0.3
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

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

[✓] Connected device (3 available)
    • iPad (mobile)   • 00008103-000D58E01E2B401E • ios            • iOS 16.1
      20B82
    • macOS (desktop) • macos                     • darwin-x64     • macOS
      12.5.1 21G83 darwin-x64
    • Chrome (web)    • chrome                    • web-javascript • Google
      Chrome 116.0.5845.96

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Thanks for filing the issue. I can reproduce this on stable channel but it seems to have been fixed on the latest master channel as I cannot reproduce it there.

Demo
https://github.com/flutter/flutter/assets/104349824/4e7213cf-6987-4b35-b3d9-75ae34b694d3

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.13.0, on macOS 13.5 22G74 darwin-x64, locale en-VN)
    • Flutter version 3.13.0 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision efbf63d9c6 (25 hours ago), 2023-08-15 21:05:06 -0500
    • Engine revision 1ac611c64e
    • Dart version 3.1.0
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 32.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (3 available)
    • iPhone (mobile) • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.7.2 19H218
    • macOS (desktop) • macos                                    • darwin-x64     • macOS 13.5 22G74 darwin-x64
    • Chrome (web)    • chrome                                   • web-javascript • Google Chrome 116.0.5845.96

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.14.0-9.0.pre.24, on macOS 13.5 22G74 darwin-x64, locale en-VN)
    • Flutter version 3.14.0-9.0.pre.24 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 8e7304bb27 (26 minutes ago), 2023-08-21 22:35:36 -0400
    • Engine revision 1ab054967c
    • Dart version 3.2.0 (build 3.2.0-94.0.dev)
    • DevTools version 2.26.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 32.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (3 available)
    • iPhone (mobile) • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.7.2 19H218
    • macOS (desktop) • macos                                    • darwin-x64     • macOS 13.5 22G74 darwin-x64
    • Chrome (web)    • chrome                                   • web-javascript • Google Chrome 116.0.5845.96

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

I'll close this issue as fixed on the latest channels. If you still experience this issue, kindly leave a comment below and I will reopen this. Thank you!

@huycozy Our app exhibits this issue pretty drastically on both Flutter 3.13.0 and 3.13.1. It is not exhibiting this issue on 3.10.x. (though not releasable because of the iOS 16.6 jank bug), nor on the master channel. Any idea when this will be made available on the stable channel so we can finally do a release using the stable branch?

You can read about it here: https://github.com/flutter/flutter/wiki/Flutter-build-release-channels#will-a-particular-bug-fix-be-provided-in-a-hotfix-release (and whole that page for more info)

@huycozy Our production healthcare app Braver is currently experiencing an embarrassing animation issue on 3.10.x that we can't fix because the fix is only available on 3.13.x, which now exhibits a new pretty ugly animation issue (this one here), that will only be available when beta/master makes it to stable, as far as I understand it.
https://github.com/flutter/flutter/assets/1283/93a2fd0c-b5ef-4b68-bc78-6f6e60c7f5db
Even if this issue is now fixed in master, we should prioritize it high enough so it eventually lands in a hotfix release, because it currently affects apps in production running 3.13.x.
In our case (and I suppose for many others), it's not an option to use beta or master channel in production, because multiple breaking changes landed there, like WillPopScope that was removed, and some deprecated-now-removed types that third-party libraries haven't yet removed.

@huycozy to be more explicit, can you put a decent priority on this issue so a hotfix can be considered? Just filing it as fixed on master is not going to make it considered at all.
Our app has become incredibly janky on iOS, it's embarassing, and we currently can't do anything about it.
/cc @Hixie

@matehat Small suggestion in case you haven't considered: If you implemented the scrim yourself, you could replace the AnimatedOpacity with an AnimatedContainer that changes color. I've found that AnimatedContainer doesn't exhibit this bug in stable.

This issue is closed so the priority would have no effect; see https://github.com/flutter/flutter/wiki/Flutter-Cherrypick-Process for instructions on how to get a hotfix applied.

This issue is closed so the priority would have no effect; see https://github.com/flutter/flutter/wiki/Flutter-Cherrypick-Process for instructions on how to get a hotfix applied.

@Hixie thanks for the pointer, but there's no commit hash identified at this point, we just know that something on main has fixed the issue. I was hoping someone more knowledgeable of Impeller would have an idea, hence why I mentioned you (sorry if I bothered you btw).

I've found that AnimatedContainer doesn't exhibit this bug in stable.

@SmashHighlights thanks for pointer, will try it out and post back if it fixes it for us too!

For the record, it doesn't fix it for us. So another issue could be at play. I'll make a minimal reproducible example (that breaks on stable but works on master) and file another issue.

The same.It runs well in 3.10, but it runs badly in 3.13(Only iOS).

In our case, after playing around with tweaks, we could make it work by doing the equivalent of replacing:
AnimatedOpacity(
  opacity: opacity,
  child: Container(
    color: someColor
    ...
  ),
)

or even
Opacity(
  opacity: animation.value,
  child: Container(
    color: someColor
    ...
  ),
)

by
Container(
  color: someColor.withOpacity(animation.value),
  ...
)


Bug: Google Social Login State Inconsistency

Describe the bug
After successfully logging in with Google authentication, the functionality works as expected. However, when I clear the user data (database, local storage and cookies) and attempt to log in again, there's an inconsistency: while the login appears successful, error messages appear in the console.
Expected behavior
It goes to social provider login then ask us to sign in again
Screenshots

I think this is cause you forgot to clear the account from the accounts table

I think this is cause you forgot to clear the account from the accounts table

Just rechecked it, after cleaning all tables, same issue. I might be missing something, I also tried from another browser and google account, the login works but account table has nothing.
auth.ts
import { betterAuth } from "better-auth";
import prisma from "./db";
import { prismaAdapter } from "better-auth/adapters/prisma";

export const auth = betterAuth({
  database: prismaAdapter(prisma, {
    provider: "postgresql",
  }),
  socialProviders: {
    google: {
      clientId: process.env.GOOGLE_CLIENT_ID as string,
      clientSecret: process.env.GOOGLE_CLIENT_SECRET as string,
      redirectUrl: "http://localhost:3000/api/auth/callback/google",
    },
  },
});

auth-client.ts
import { createAuthClient } from "better-auth/client";

export const authClient = createAuthClient({});

export const { signOut, useSession, signIn } = authClient;

sign-in.tsx
<Button
        variant="secondary"
        className="w-full gap-2"
        onClick={async () => {
          await signIn.social({
            provider: "google",
          });
        }}
      >
        Continue with Google
</Button>

The issue seems to be that userId isn't returned from Prisma after user creation. Not sure why it works on first but not on subsequent tries. If the database was fully cleared, that shouldn't happen. I've published a potential fix. Please try it out and let me know if it resolves the issue. You can install it with pnpm add better-auth@next.

Thanks for the quick update, I tried npm install better-auth@next
I have created a video of the behaviour.
https://www.loom.com/share/2992c7e90c2f46e699b08d1a73e1470f

Yes, also it's loggin in directly with google oauth, when I have deleted the data. How's it happening?

That's expected. If you use oAuth it'll create you an account if the account doesn't already exist.

understood, well then there's only this prisma issue
PrismaClientValidationError:
Invalid `prisma.account.create()` invocation:
{
  data: {
    id: "google:26262",
    accountId: "6262626",
    providerId: "google",
    userId: undefined,
    accessToken: "",
    refreshToken: undefined,
    idToken: undefined,
    expiresAt: undefined,
    password: undefined,
+   user: {
+     create: UserCreateWithoutAccountInput | UserUncheckedCreateWithoutAccountInput,
+     connectOrCreate: UserCreateOrConnectWithoutAccountInput,
+     connect: UserWhereUniqueInput
+   }
  }
}
Argument `user` is missing.

this is fixed on latest!


Component dependency diagram only shows immediate dependency.

Pet-be gateway's depenecy diagram should show controller -> [orders, customers, catalog], but the current component dependency diagram stops with controller, and next level dependencies are not shown.

When checking on this further, can see the data is returned with all level of dependency, but the graph is not updated with full data.
Data returned:
{"nodes":[{"id":"pet-be:controller","instanceKind":"Cell","components":[],"edges":[]},{"id":"pet-be:orders","instanceKind":"Cell","components":[],"edges":[]},{"id":"pet-be:customers","instanceKind":"Cell","components":[],"edges":[]},{"id":"pet-be:gateway","instanceKind":"Cell","components":[],"edges":[]},{"id":"pet-be:catalog","instanceKind":"Cell","components":[],"edges":[]}],"edges":[{"source":"pet-be:controller","target":"pet-be:customers","edgeString":"pet-be:controller ---\u003e pet-be:customers ---\u003e "},{"source":"pet-be:gateway","target":"pet-be:controller","edgeString":"pet-be:gateway ---\u003e pet-be:controller ---\u003e "},{"source":"pet-be:controller","target":"pet-be:catalog","edgeString":"pet-be:controller ---\u003e pet-be:catalog ---\u003e "},{"source":"pet-be:controller","target":"pet-be:orders","edgeString":"pet-be:controller ---\u003e pet-be:orders ---\u003e "}]}


Fix #122 Page Status Error + Update Posts Stats

See issue #122.
Also fixed Post Stats setting up a default value.

kickass dude! Thanks a ton!


Remove doc that says a comma works as a logger parameter

The console logger does not accept comma as a separator. Semicolon works.

@AArnott : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Add .NET 8 to Supported .NET runtimes for 10.1 CU3

.NET 8 support is a major feature expected by customers, we already received questions about this.

#sign-off


x11: parse vendor and model out of xcb setup information

@acrisci thanks for review, all cleaned up now.

All addressed now. Thanks for the snprintf( , "%.*s", ) hint.

Empty line removed.


esp isnt showing up ?

when i enable esp it wont show up ?

select filters and click on "esp" label to enable it. #57


Advanced Filter: "Save the Filter" checkbox got removed from the modal

Description
Save the filter checkbox got removed from the filter modal. It was there in a previous build(V1.1.6 maybe?) on 1/25 (attached a modal screenshot from that date below)
Version
Datagrid: V1.1.7
Screenshot
Spec

Modal in V1.1.7

Modal on 1/25

Never mind, Sami explained that is a configurable attribute for it now: offerFilterSaving.
Will test it out with that.


 He regularly deletes issues or closes them with comment blocking. This behaviour makes this dependency unsafe to use in your application. It is not possible to have a discussion with or contact the author.
I and company that I work with will drop usage of that library and fork it. Really it's not worth to rely on that person.

@k3nsei I simply don't deal with morons...


support stl file？

support stl file？

目前支持 stl 格式吗？ 我看js 是支持的，flutter 版本 目前没有看到

Hi @Lanlanxiao,
I have added stl loader, but I am still working on other updates before I make the pull request.
Please go to https://github.com/Knightro63/three_dart_jsm/blob/main/lib/three_dart_jsm/loaders/stl_loader.dart to see the conversion.
Hope this helps.

You could also use my package from pub.dev https://pub.dev/packages/urdf_parser.
It contains a STL + DAE loader and URDF parser.
Just add the package to your project and do:
three.Object3D stlObject = await STLLoader(null).loadAsync("path to stl file");
scene.add(stlObject);


Chore/error handling improvements

Related Issue
N/A
Description
We use several methods that pre-suppose the existence of an element. In cases where these elements do not exist (or can't be found), we receive NoSuchElementException. These failures can be a little difficult to troubleshoot, so I've added more robust exception handling as well as unit tests.
Definitely open to feedback about better exception error text, or ways to implement the exception unit tests.
Checklist

[x] Have you added an explanation of what your changes do?
[x] Have you written new tests for your core changes, as applicable?
[x] Docs have been added / updated (for bug fixes / features)

@mrk-han Do you want me to bump this to 0.19.4?


default file saving location

Squid3 Version: 1.6.5
Java Version: 1.8.0_241
OS: Windows 10 10.0
Issue details: have the default file saving location be the folder that the xml was taken from

As this was just a "dummy" issue for the workshop, I am going to close it.


Upgrade to polkadot v0.9.36

Codecov Report

Merging #864 (4edb69f) into master (dc39cfd) will increase coverage by 0.03%.
The diff coverage is 76.47%.

@@            Coverage Diff             @@
##           master     #864      +/-   ##
==========================================
+ Coverage   78.84%   78.87%   +0.03%
==========================================
  Files         102      102
  Lines       10546    10543       -3
==========================================
+ Hits         8315     8316       +1
+ Misses       2231     2227       -4

Impacted Files
Coverage Δ

asset-registry/src/lib.rs
91.86% <ø> (ø)

asset-registry/src/mock/para.rs
72.97% <ø> (+3.74%)
:arrow_up:

auction/src/lib.rs
90.32% <ø> (ø)

authority/src/lib.rs
82.35% <ø> (ø)

authority/src/mock.rs
81.25% <ø> (ø)

bencher/test/src/lib.rs
0.00% <ø> (ø)

benchmarking/src/tests.rs
96.77% <ø> (ø)

currencies/src/lib.rs
48.98% <ø> (ø)

gradually-update/src/lib.rs
88.75% <ø> (ø)

oracle/src/lib.rs
76.36% <ø> (ø)

... and 12 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Closes #861 #862

some tests for the new asset_exists implementation will be nice