Arlo alarm_control_panel cannot be armed_away or armed_home successfully

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
Hassio - 0.56.2
Python release (python3 --version):
(whatever version is baked into hassio 0.56.2)
Component/platform:
Arlo
alarm_control_panel
Description of problem:
Only using the alarm_control_panel for Arlo.  The sensor and camera components for Arlo are disabled.  Upon restart, all seems well - no errors or warnings beyond the "taking longer than 10 seconds" on a few components, but they dissipate.  The Arlo alarm panel state reflects appropriately - armed_home for instance.
If I then call the alarm_arm_away service through the alarm_control_panel domain, the state of the panel flips to 'unknown' and a reoccurring warning begins to take place...
2017-10-30 15:31:23 WARNING (MainThread) [homeassistant.helpers.entity] Update of alarm_control_panel.living_room is taking over 10 seconds
2017-10-30 15:31:45 WARNING (MainThread) [homeassistant.components.alarm_control_panel] Updating arlo alarm_control_panel took longer than the scheduled update interval 0:00:30
2017-10-30 15:32:25 WARNING (MainThread) [homeassistant.helpers.entity] Update of alarm_control_panel.living_room is taking over 10 seconds
2017-10-30 15:32:47 WARNING (MainThread) [homeassistant.components.alarm_control_panel] Updating arlo alarm_control_panel took longer than the scheduled update interval 0:00:30
2017-10-30 15:33:27 WARNING (MainThread) [homeassistant.helpers.entity] Update of alarm_control_panel.living_room is taking over 10 seconds
The initial call to arm is successful to Arlo - I can see that the mode of the base station changes to Armed.  However, any subsequent calls to arm through the alarm_control_panel domain are unsuccessful and the state of the panel remains at 'unknown'.  The only remedy is to restart hass.
Expected:
Calling the alarm_control_panel to arm_away, arm_home, or disarm are successful through Arlo APIs and reflected appropriately in hass during any attempt and not just the first one.
Problem-relevant configuration.yaml entries and steps to reproduce:
#############################
# TURN ON ARLO              #
#############################
arlo:
  username: !secret arlo_user
  password: !secret arlo_pass

#############################
# ENABLE ARLO ARLARM PANEL  #
#############################
alarm_control_panel:
  - platform: arlo
    home_mode_name: Home

#############################################
# ENABLE ARLO CAMERAS - currently disabled  #
#############################################
#ffmpeg:
#camera:
#  - platform: arlo
#    ffmpeg_arguments: '-pred 1 -q:v 2'

Set Arlo mode to your home_mode_name reflected in the configuration via the Arlo app
Restart hass
Through the services developer tool, set the domain to alarm_control_panel, service to alarm_arm_away, set the appropriate entity ID, and hit 'call service' button
Review the state of the panel and see that it has flipped from armed_home to unknown

Traceback (if applicable):

Additional info:
I have also tested this with setting the initial state to armed_away and calling the service alarm_arm_home.  The results are the same - unknown state, constant warning to logs, unable to call service again unless hass is restarted

I have ' in the home_mode_name, have you tried if that makes any different?
alarm_control_panel:
  - platform: arlo
    home_mode_name: 'Home'

No change, same issue.  I did just go look at the documentation again and see that an away_mode_name section was added.  Do you have that set?  I'm doing some testing around that.
Are you not having the same troubles I'm seeing?  Would you mind going into any detail on your Arlo mode setup? Are you on 0.56.2?

This is my setup
configuration.yaml
arlo:
  username: !secret arlo_username
  password: !secret arlo_passwd

camera:
  - platform: arlo
    ffmpeg_arguments: '-pred 1 -q:v 2'

alarm_control_panel:
  - platform: arlo
    home_mode_name: 'baksidan'

Note that the home_mode_name must be exactly the same as the mode in Arlo you want to arm/disarm
This is my action in the automation part where I Arm my home_mode_name

We have very similar setups, I don't know what the deal is.  I'll do some testing with a more obscure name perhaps - my home mode name is just 'Home'.  I also tried out the away_mode_name and that didn't do me any good.

Wrong button :)

I made some major headway - had a secondary account setup in Arlo that I configed in hass.  Upon setting the arlo component in hass to use the primary account tied to Arlo, I'm able to arm_home, arm_away, and disarm without any issue.  That's interesting given the recommendation in the arlo component documentation to use a secondary account.
Hey @Nicxe - are you using a secondary account for the arlo component per the hass recommendation or the primary account tied to Arlo?

I am using the secondary account. Have you ticked the box in Arlo so the secondary user have access to set the custom modes?

Yeah - I have access right ticked.  I even went and setup another account and tested it.  Same results.

@djchen I know this sounds crazy, but have you tried removing the cameras from your config?  The cameras battery state issues were causing all of my arlo components to act up.  I removed the cameras and was immediately able to set states without any problems.  With the cameras in my config however I can't do anything with the arlo components.  Now if I could just get triggering the alarm to work! :D

@bcl1713 I think you meant that for @djmcp :)

Indeed.  Sorry!

@bcl1713 - yeah, I've disabled all Arlo sensors and cameras for the time being because of issues myself and others have had.  I just have the alarm_control_panel option for arlo configured at the moment.
My testing around using my primary account seemed very promising - was able to use it when testing direct domain/service calls as well as adding it to some scripts and testing with automations.  Unfortunately, this only lasted 30 minutes or so until the dang state went from armed_home to unknown and began throwing the "took longer than the scheduled update..." messages again.
@bcl1713 - do you have a similar setup going on as myself and Nicxe?  Are you using your primary arlo account or a secondary account you gave access to?

@djmcp I am using a secondary account in home assistant that has been granted access to the base station as well as my cameras.  Mine is now reporting as "unknown" almost all of the time. :/  It was working.  My log is also getting flooded with the "took longer than the scheduled update..." spam.

I too am seeing 'this only lasted 30 minutes or so until the dang state went from armed_home to unknown and began throwing the "took longer than the scheduled update..." messages again.'
Each time I restart hass, my alarm_control_panel for arlo works correctly for ~0.52 hours and then goes to unknown. I've also seen the arming state of my actual arlo (as viewed in the netgear UI) go from armed to disarmed at the same time as the hass alarm_control_panel's ->unknown transition.
This feels like netgear backend is deciding that the 30s polling of the API is abusive and is serving errors after a certain amount of time or query budget. I've got an inquiry in to netgear support about what kind of polling of their API is acceptable. If I hear anything useful from them I'll update here. Not holding my breath though.
I'll also try increasing the arlo scan_interval to 60s or higher to see if this alleviates the problem. If so, that would support the theory that netgear is limiting the API.

Hey @bcl1713  - you should try testing your primary account and seeing if stays consistent.  I'm having more luck with this.
@smroid  - I've been throwing darts and finally got one to stick.  I just had alarm_control_panel enabled to limit any other factors as I've been working through this issue - i.e. I had commented out camera and sensor components for arlo.  Last night, I enabled both sensor and camera components while continuing to have my primary arlo account configured.  This is the relevant config...
arlo:
  username: !secret arlo_user
  password: !secret arlo_pass

ffmpeg:

camera:
  - platform: arlo
    ffmpeg_arguments: '-pred 1 -q:v 2'

alarm_control_panel:
  - platform: arlo
    home_mode_name: 'Home'

sensors:
  - platform: arlo
    monitored_conditions:
      - captured_today

Because of the battery level issues, I'm just monitoring captured_today.  With this setup, I've had a handful of drops to 'unknown' but they only last for a minute.  I've restarted hass several times to deal with other config and alarm_control_panel is still working and no problems with automation.  It's basically where I want it minus the fact that I have to use my primary arlo account instead of one of the secondary ones I've created.

@smroid I don’t have this issue

@djmcp - your dart worked for me.
Previously, my arlo config was just:
arlo:
username: !secret arlo_username
password: !secret arlo_password
alarm_control_panel:

platform: arlo
home_mode_name: 'Family Room'

And I would reliably see the arlo armed state go to unknown 0.52 hours after hass restart.
Per @djmcp's report, I added:
sensor:

platform: arlo
monitored_conditions:

total_cameras

and now my arlo alarm_control_panel is working reliably.
This feels like a bug in the arlo platform or arlo alarm_control_panel impl.

I just had another transition of arlo alarm_control_panel to 'unknown' state.
@tchellomello, any suggestions about what can we do (e.g. to enable richer logging) to help figure out what's causing the problem?

@tchellomello,  I had an automation trigger whose action is to disarm the arlo alarm_control_panel. The arlo did not disarm, and the home-assistant.log file has:
2017-11-03 21:39:53 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/core.py", line 1026, in _event_to_service_call
yield from service_handler.func(service_call)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/alarm_control_panel/init.py", line 129, in async_alarm_service_handler
yield from getattr(alarm, method)(code)
File "/usr/lib/python3.5/asyncio/coroutines.py", line 210, in coro
res = func(*args, **kw)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/alarm_control_panel/arlo.py", line 88, in async_alarm_disarm
self._base_station.mode = DISARMED
File "/srv/homeassistant/lib/python3.5/site-packages/pyarlo/base_station.py", line 374, in mode
if mode not in self.available_modes:
File "/srv/homeassistant/lib/python3.5/site-packages/pyarlo/base_station.py", line 237, in available_modes
return list(self.available_modes_with_ids.keys())
File "/srv/homeassistant/lib/python3.5/site-packages/pyarlo/base_station.py", line 244, in available_modes_with_ids
[(m.get("type", m.get("name")), m.get("id")) for m in modes]
TypeError: 'NoneType' object is not iterable

Hello guys, it seems that this problem has been already addressed on the new rebase and code changes made on PR https://github.com/home-assistant/home-assistant/pull/9892 which is currently under progress.
If that PR does not fix this issue, please feel free to reopen or create a new issue for it.

Created a new issue after 0.58
https://github.com/home-assistant/home-assistant/issues/10679

This works for me. The issues was solved just a a few releases after the issue was created

I seem to be having a similar problem with 0.65.5
I was using a secondary account, which at some point even stopped showing the Arlo cameras in HA. I tried switching to my main account, and that allowed me to see the cameras in HA, but mode switching doesn't work...
Not sure what data I can provide that would be helpful?


Update api_keys.py

keys cannot be published in the repository. Clone and use own your keys locally.


No case sensitive option

Hi,
Can you add option - no case sensitive?

It looks a good idea, yes, I will do it, thnak you!

Version 2.2.0 is now available with its new case sensitive option. Take a look!


Tree widget: Bad layout in Categories tree when hierarchy level is filtered with no matches

Notice the layout of "eye" and expander icons.
Good:

Bad:

@saskliutas notes this is likely due to horizontal scroll. However, I'd question why the "eye" icon moved to the left - it should stay in place.


Process Documentation: Nivenly, project, trade, and community working relationships

What Nivenly:

Promises to projects
Promises to community
Promises to trade orgs

What projects:

Promise to Nivenly
Promise to community
Promises to trade orgs

What trade orgs:

Promise to Nivenly
Promise to community
Promise to projects

What community / general members:

Promise to Nivenly
Promise to projects
Promise to trade orgs

The scope of this is an ethos to state how all each of the above promise to work with each others. For example, community and trade orgs can promise to give constructive criticism to projects relevant to each of their domains (no trolling, combative, etc. behavior). This would mean that:

Nivenly promises to respond to requests for information in a timely manner -> In scope ✅
Nivenly promises to provide governance support -> Out of scope ❌ (it's true, just not this document)

To put it another way, this is how all the members / groups interface with each other, rather than the tangibles of what each provides.


build: move results to separate step

:tada: This PR is included in version 0.15.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Sending a message when a user joins the group?

I made a bot using this to create a rules bot (prints rules on /rules) for a group chat I am in (a rather big chat). How do I make it so when a new user joins, the bot prints the rules?

AFAIK the bot is not notified when a user joins a group. So you can't.

See #25 seems like there was some success on this front.


Add support for determining the license from an arbitrary URL

Allows you to pass an arbitrary URL to determine the license for the content at that URL. I've also resolved all of the current lint warnings.
If you want me to remove the .vscode/launch.json I can, it just enables easy debugging for anyone using Visual Studio Code.

@willbar Thanks for this. Can you explain a bit more about the problem you're trying to solve? If you have the URL to the file, would curl URL | licensee work, or do you need the data in Ruby-land?
The general implementation looks good, although I'm a bit concerned about making remote HTTP calls by default. We use Licensee in production at GitHub.com, and I can imagine some edge cases where an unsanitized or network path might make it's way to Licensee.
How would you imagine this being used? Being pointed at the URL to a text file? An entire Git repo? A GitHub repo? Part of the value of the project is being able to determine the LICENSE file, which may be LICENSE-MIT, COPYING, etc.

@benbalter Sure, when registering open source projects we need to determine the license the project is under, for projects that are in a GitHub repository we do call the GitHub API today to get that information (leveraging all of the goodness you mention today) but in other cases we just have a URL to some random file and we need to be able to determine the license. We need to be able to do this in a service so shelling out isn't ideal.
What if I changed the code to allow you to opt-in that project type?

What if I changed the code to allow you to opt-in that project type?

Makes sense, and thanks for the additional context.

@benbalter What I ended up doing was adding a allow_remote arg (similar to detect_packages) that defaults to false. The command line (bin\licensee) sets it to true so you can do URL lookups from the command-line. I'm assuming the GitHub API uses the library not the command-line, correct?
The advantage of adding it as an arg is if you add new project types in the future that might do remote calls they can use the arg to determine if that capability is enabled or not.
Does this feel like it's on the right track? I need to add some more unit tests but I wanted to validate the approach with you first.


Choose a name for the software

A name for the software (ideally that isn't already taken on https://pypi.org/ or as an org/user name on github) should be chosen at some point.
Once we have a name:

[ ] rename repo (and possibly create org and move repo there)
[ ] add to pypi / gha pypi release on tagged commits
[ ] add documentation on readthedocs
[ ] add sonar integration
[ ] add code coverage integration

resolved by #184 #185 #190


XlaRuntimeError: UNIMPLEMENTED: Only 1 computation per replica supported, 8 requested.   In call to configurable 'train' (<function train at 0x7f364f9c11f0>)

i meet this error . Can anyone slove it ? Thank you very much........

Is anybody here ? Help me.......


setting hyperlink，can't  modify text

Hello, when setting hyperlink, why can't you modify the text while changing the link after clicking? Most of the time the text needs to be modified, which causes inconvenience

I'm having the same problem, can react-quill customize the popup for editing links please...


[DBZ-PGYB] Initial commit for PG connector parity

This PR contains the initial changes which are required to make the Debezium Connector for Postgres work with YugabyteDB as source.

@vaibhav-yb Hi, intersting initiative. Could you please share more details? Is it a planned replacement for https://github.com/yugabyte/debezium-connector-yugabytedb or a planned extension? Thanks a lot

Hi @jpechane This is a planned extension for the existing https://github.com/yugabyte/debezium-connector-yugabytedb. As of the given moment, I do not have much information to share as we are in our initial phases. I will definitely keep you in loop as and when we reach a presentable form. Thank you so much! 😄
PS. We'll be opening a PR against the upstream repository later. This was the very initial commit for which I accidentally opened up a PR here, sorry for the confusion.

@vaibhav-yb Thanks, good luck with the work!


Examples should use css reset

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Examples should use CssBaseline component - otherwise, some functionality might be broken.
Expected Behavior 🤔

Codesandbox examples should use explicitly CssBaseline, because if you try to run example on your own machine some functionality might be broken - for example drawer component should looks like:

Current Behavior 😯

Codesandox uses css-reset under the hood, so example looks properly, but if you try to run it in your own machine some functionality might breaks. For example drawer looks like:

Steps to Reproduce 🕹

Create a simple app, just copy&past example: https://codesandbox.io/s/qkmklzx3xj
Start app

@gtktsc Could you guide us a bit more. How did you end up with a broken output? I mean. What's the example? The codesandbox looks good to me. It's using the CSS reset (the CssBaseline component).


error: package com.swmansion.gesturehandler.react

Hello,
I installed this plugin, link it with command 'react-native link'
then I get error

import com.swmansion.gesturehandler.react.RNGestureHandlerPackage;
^
C:\Users\XXX\Documents\Projects\React Native\shelfmint_mobile\android\app\src\main\java\com\moonsite\shelfmint\MainApplication.java:44: error: cannot find symbol
new RNGestureHandlerPackage(),
^

Did you install the https://github.com/kmagiera/react-native-gesture-handler package ?

Please open a new issue according to the issue template.

Thank you @jvandenaardweg  It works.


Can't run crawlee in electron

Which package is this bug report for? If unsure which one to select, leave blank
@crawlee/puppeteer (PuppeteerCrawler)
Issue description

Code sample
async onCreateProfile() {
    const crawler = new PuppeteerCrawler({
      launchContext: {
        // !!! You need to specify this option to tell Crawlee to use puppeteer-extra as the launcher !!!
        launcher: puppeteerExtra,
        launchOptions: {
          headless: false,
          args: [],
          ignoreDefaultArgs: ["--enable-automation"],
          userDataDir: "./user_data/new-1",
          ignoreHTTPSErrors: true
        },
      },

      maxRequestsPerCrawl: 50,
      async requestHandler({ request, page, enqueueLinks, log }) {
        log.info(`Processing ${request.url}...`);
      },

      // This function is called if the page processing failed more than maxRequestRetries+1 times.
      failedRequestHandler({ request, log }) {
        log.error(`Request ${request.url} failed too many times.`);
      },
    });

    await crawler.addRequests(['https://iphey.com']);

    // Run the crawler and wait for it to finish.
    await crawler. Run();
  }

Package version
3.3.0
Node.js version
16
Operating system
No response
Apify platform

[ ] Tick me if you encountered this issue on the Apify platform

I have tested this on the next release
No response
Other context
No response

@xTRiM @rarous @iloveitaly @mnmkng

Why do you use puppeteerExtra?

Closing as this does not seem to be a problem with crawlee, we don't depend on merge-deep at all, not even transitively.


strange problems when migrate to new version

hi @felangel
what I has was:
class ThemeBloc extends HydratedBloc<ThemeEvent, ThemeState> {

  @override
  ThemeState get initialState =>
      super.initialState ??
      ThemeState(
        palette: Green(),
        isLight: true,
      );

  @override
  Stream<ThemeState> mapEventToState(ThemeEvent event) async* {
    yield* event.when(
      change: (palette, isLight) async* {
        yield state.copyWith(
          palette: palette ?? state.palette,
          isLight: isLight ?? state.isLight,
        );
      },
    );
  }

  @override
  ThemeState fromJson(Map<String, dynamic> json) {
    try {
      final state = ThemeState.fromJson(json);
      return state;
    } catch (_) {
      return null;
    }
  }

  @override
  Map<String, dynamic> toJson(ThemeState state) => state?.toJson();
}

but when I migrate to V5 , the toJson and fromJson always return null.
what I have done is to add:
ThemeState(
        palette: Green(),
        isLight: true,
      )

in the super constructor of my ThemeBloc  in V5.
but I don't know what is the problem.

Hi @mohammadne 👋
Thanks for opening an issue!
Can you please provide a link to a sample app which illustrates the issue? I'm happy to take a look 👍

migrated to https://github.com/felangel/bloc/issues/1419


Monokai traceback highlighting

(Original issue 1377 created by None on 2017-09-18T16:10:11.047702+00:00)
Hi,
can you please help me modifying the molokai theme such that it renders more readable stacktraces in qt console?
Please see this SO post for details: https://stackoverflow.com/questions/46023242/how-to-change-monokai-pygments-style-in-qtconsole-with-jupyter

(Original comment by marcel_liker on 2017-09-18T16:11:43.516919+00:00)
Sorry, forgot to login before posting

Python tracebacks are properly rendered with Monokai theme on my blog, which relies on Pygments 2.7.2:

https://kevin.deldycke.com/2015/11/pip-install-ssl-error/
https://kevin.deldycke.com/2010/09/convert-lotus-notes-nsf-files-mbox-nlconverter/
https://kevin.deldycke.com/2010/09/ultimate-guide-lotus-notes-mail-migration/

So I guess this issue can be closed.


The Download link is not accessible

The Download link for xeasy tool is not accessible.
As an alternative, it would be helpful if we can know the process about how to build form Source.

src/dist - you can clone this project and go to "src/dist" to goto download the binary. working on the update to read me file and push the changes soon. thank you!


[PL-51586] Removing repeated content for Account Admin : Custom RG Doc

PL-51586
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

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://6659ab658484c01a43e4501a--harness-developer.netlify.app

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://66600909461e20bc371daf7a--harness-developer.netlify.app


validate DDO metadata before form submission

Following the issue which led to #367, we should generally expose all possible metadata errors before the user can submit anything. The reason for that is the publish process which only puts the DDO on-chain, from which Aquarius is supposed to pick it up and index it, but fails if it finds metadata errors.
For this purpose, Aquarius has a validate endpoint we can make use of for this: https://docs.oceanprotocol.com/references/aquarius/#assetsddovalidate
The implemented flow could be:

Upon form submission we first check the transtormed data against this endpoint
When it succeeds we can start with the submission process
When it fails we should expose through the form errors the place in the form where the error was caused and then display it

please delay this for a couple of days, those functions will be avaiable in ocean.js

seems to be a solution looking for a problem. We already have form model validations going on, and it seems validating all this data again with API request is only really useful for developers but not for end users


Bad Link

Describe the bug
Methods link is broken
To Reproduce
Steps to reproduce the behavior:

Go to "https://docs.microsoft.com/en-us/windows/win32/api/d3d11_3/nn-d3d11_3-id3d11fence"
Click on methods link
Go to https://docs.microsoft.com/en-us/  which is not all related.

Expected behavior
Go to related methods information
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Win10
Browser chrome

Thanks for reporting this issue. This is a known issue that is affecting many class and interfaces across the SDK documentation. We have a work item tracking a fix for this issue which requires an update to our production code. The ETA for the fix isn't known for certain, but we will push it out as soon as we can. Thanks again for helping us to improve the docs!


Add control plane upgrades for Hypershift cluster

This is the only supported mode for Hypershift cluster at the moment. We also enforce that upgrades will start immediately, no scheduling possible in the first phase.
Examples:
rosa upgrade cluster -c ad3 --control-plane
? Version: 4.12.8
? IAM Roles/Policies upgrade mode: auto
I: Ensuring account and operator role policies for cluster '22oaveu9j278qh79814p2aug5ahtvl2h' are compatible with upgrade.
I: Account roles/policies for cluster '22oaveu9j278qh79814p2aug5ahtvl2h' are already up-to-date.
I: Operator roles/policies associated with the cluster '22oaveu9j278qh79814p2aug5ahtvl2h' are already up-to-date.
I: Account and operator roles for cluster 'ad3' are compatible with upgrade
? Are you sure you want to upgrade cluster to version '4.12.8'? Yes
? Node draining: 1 hour
I: Upgrade successfully scheduled for cluster 'ad3'

rosa describe upgrade -c ad3
                ID:                         5cbfc13c-ce36-11ed-9dda-0a580a8308f5
		Cluster ID:                 22oaveu9j278qh79814p2aug5ahtvl2h
		Next Run:                   2023-03-29 13:43:00 +0000 UTC
		Upgrade State:              started
                Version:                    4.12.8

Related: SDA-8472

Just not fond of a lot of conditionals within the flow like that, but lgtm. We can refactor it later as there are other commands like that already 👍

agree! The idea here was to break the big function in smaller blocks to make it more comprehensible.
Then yes we need a generic task to review the flow handling with hypershift in the whole ROSA CLI

Rebased on master branch and verified also for the managed policies flow:

oadler@fedora:rosa ((c136cb84...))$ ./rosa upgrade cluster -c oadler-chk-2 --control-plane
? Version: 4.12.8
? IAM Roles/Policies upgrade mode: auto
I: Ensuring account and operator role policies for cluster '22plgaisr5ki61ifv2es9neh2vmk2mng' are compatible with upgrade.
I: Account roles with the prefix 'oadler-check' have attached managed policies.
I: Cluster 'oadler-chk-2' operator roles have attached managed policies
I: Account and operator roles for cluster 'oadler-chk-2' are compatible with upgrade
? Are you sure you want to upgrade cluster to version '4.12.8'? Yes
? Node draining: 1 hour
I: Upgrade successfully scheduled for cluster 'oadler-chk-2'

/lgtm


M doesn't get updated when self.diag is true, does it?

Shouldn't this line start with self.M = to store the returned value of einsum in self.M?
https://github.com/aradha/recursive_feature_machines/blob/a89c96e4dc729415f19ffad732c080a4d84f0752/rfm/recursive_feature_machine.py#L175

Fixed in commit ad9bdf5


update the protocole and add a link

@XeniaMonika, I made a few edits and went ahead and merged this. Thanks for taking care of the protocol.


Run planner.on.mac os

@michaelkleinhenz As discussed here: https://stackoverflow.com/questions/402377/using-getopts-in-bash-shell-script-to-get-long-and-short-command-line-options search for "# NOTE: This requires GNU getopt.  On Mac OS X and FreeBSD, you have to install this
separately; see below."
I've added it as a pre-requisites for macOS

@corinnekrych snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1947-fabric8-planner.int.rdu2c.fabric8.io


Add Python for RaspberryJamMod and others?

Hi, I really love your minecraft-server docker image! One suggestion: how about adding python packages, so that you can use e.g. a FORGE type server with e.g. the RaspberryJamMod (https://github.com/arpruss/raspberryjammod) to run python scripts in Minecraft?
I've tried it in my own image based on yours and it worked like a charm. All I've added was
RUN apk --update add python2 python2-dev py-setuptools

That's like a good feature. I'll just double check that it doesn't grow the image size too much.

Cool :) Here are the image sizes I got when adding python in my derived image after adding the three packages:

@smxsm can you try out the latest image I pushed? apk was acting a little odd for me, so I ended up adding python and python-dev; however, I was able to run some of the RaspberryJamMod sample scripts.

Works perfectly, thank you very much for adding! 👍

Awesome, thanks.
I'll leave this issue open to track merging the same to the Debian branch.

...and added for debian tag: https://hub.docker.com/r/itzg/minecraft-server/builds/bkpt8b6rkkvumvuacnrdpyi/


Add support for gmail to msmtp

Fix for issue https://github.com/tiredofit/docker-freepbx/issues/18

Hi @joeyberkovitz - Thanks for this!
I'm not going to accept this actual PR, but have made some of the changes inside this image, and the base image it relies on. I've given you credit none the less. Thank you.


Add rootPath check for connect etcd command

See also #98
/kind improvement
Signed-off-by: Congqi Xia<EMAIL_ADDRESS>

/lgtm


Pennsylvania updates 4/5

Adjusted phase 1b (added high risk individuals, essential workers)
Recreated phase 1c (duplicated 1b and added more essential workers)
Set 1b as active for state, 1c active for Philly
Also made phase 2 for later updates

[{"key":"pennsylvania","type":"regions","value":{"philadelphia":{"vaccination":{"content":{"activePhase":"1c"}}}}},{"key":"pennsylvania","type":"vaccination","value":{"content":{"activePhase":"1b","phases":[{"id":"1a","qualifications":[{"question":"c19.eligibility.question/healthcare_worker","moreInfoText":"c19.eligibility.moreinfo/healthcare_worker.pa.1a"},{"question":"c19.eligibility.question/long_term_care_resident"},{"question":"c19.eligibility.question/exposure_to_infectious_material.do","moreInfoText":"c19.eligibility.moreinfo/exposure_to_infectious_material.do.pa.1a"},{"question":"c19.eligibility.question/age.65_up"},{"question":"c19.eligibility.question/age.are_you_age","moreInfoText":"c19.eligibility.moreinfo/age.are_you_age.pa.1a"}]},{"id":"1b","qualifications":[{"question":"c19.eligibility.question/healthcare_worker","moreInfoText":"c19.eligibility.moreinfo/healthcare_worker.pa.1b","moreInfoUrl":"https://www.health.pa.gov/topics/disease/coronavirus/Vaccine/Pages/Vaccine.aspx"},{"question":"c19.eligibility.question/long_term_care_resident.are"},{"question":"c19.eligibility.question/essential_worker","moreInfoText":"c19.eligibility.moreinfo/essential_worker.pa.1b","moreInfoUrl":"https://www.health.pa.gov/topics/disease/coronavirus/Vaccine/Pages/Vaccine.aspx"},{"question":"c19.eligibility.question/age.65_up"},{"question":"c19.eligibility.question/health.1b.pa"},{"question":"c19.eligibility.question/congregate"},{"question":"c19.eligibility.question/health","moreInfoText":"c19.eligibility.moreinfo/age.are_you_age.pa.1b","moreInfoUrl":"https://www.cdc.gov/coronavirus/2019-ncov/need-extra-precautions/people-with-medical-conditions.html"}]},{"id":"1c","label":"1C","qualifications":[{"question":"c19.eligibility.question/healthcare_worker","moreInfoUrl":"https://www.health.pa.gov/topics/disease/coronavirus/Vaccine/Pages/Vaccine.aspx","moreInfoText":"c19.eligibility.moreinfo/healthcare_worker.pa.1c"},{"question":"c19.eligibility.question/long_term_care_resident.are"},{"question":"c19.eligibility.question/essential_worker","moreInfoUrl":"https://www.health.pa.gov/topics/disease/coronavirus/Vaccine/Pages/Vaccine.aspx","moreInfoText":"c19.eligibility.moreinfo/essential_worker.pa.1c"},{"question":"c19.eligibility.question/age.65_up"},{"question":"c19.eligibility.question/health.1b.pa"},{"question":"c19.eligibility.question/congregate"},{"question":"c19.eligibility.question/health","moreInfoUrl":"https://www.cdc.gov/coronavirus/2019-ncov/need-extra-precautions/people-with-medical-conditions.html","moreInfoText":"c19.eligibility.moreinfo/age.are_you_age.pa.1c"}]},{"id":"2","label":"2","qualifications":[{"question":"c19.eligibility.question/age.16_up","moreInfoText":"c19.eligibility.moreinfo/age.16_up.pa.2"}]}]}}},{"key":"pennsylvania","type":"strings","value":{"content":{"c19.eligibility.moreinfo/healthcare_worker.pa.1b":{"en-us":"Health care personnel including, but not limited to:\n- Emergency medical service personnel\n- Nurses\n- Nursing assistants\n- Physicians\n- Dentists\n- Dental hygienists\n- Chiropractors\n- Therapists\n- Phlebotomists\n- Pharmacists\n- Technicians\n- Pharmacy technicians\n- Health professions students and trainees\n- Direct support professionals\n- Clinical personnel in school settings or correctional facilities\n- Contractual HCP not directly employed by the health care facility"},"c19.eligibility.moreinfo/essential_worker.pa.1b":{"en-us":"These include:\n- People in congregate settings not otherwise specified as long-term care facilities, and persons receiving home and community-based services\n- First responders (including Law enforcement and Firefighters)\n- Correctional officers and other workers serving people in congregate care settings not included in Phase 1A  \n- Food and agricultural workers\n- U.S. Postal Service workers\n- Manufacturing workers  \n- Grocery store workers  \n- Education workers \n- Clergy and other essential support for houses of worship \n- Public transit workers\n- Individuals caring for children or adults in early childhood and adult day programs"},"c19.eligibility.moreinfo/age.are_you_age.pa.1b":{"en-us":"This includes:\n- Cancer\n- Chronic kidney disease\n- Chronic lung diseases, including COPD (chronic obstructive pulmonary disease), asthma (moderate-to-severe), interstitial lung disease, cystic fibrosis, and pulmonary hypertension\n- Dementia or other neurological conditions\n- Diabetes (type 1 or type 2)\n- Down syndrome\n- Heart conditions (such as heart failure, coronary artery disease, cardiomyopathies or hypertension)\n- HIV infection\n- Immunocompromised state (weakened immune system)\n- Liver disease\n- Overweight and obesity\n- Pregnancy\n- Sickle cell disease or thalassemia\n- Smoking, current or former\n- Solid organ or blood stem cell transplant\n- Stroke or cerebrovascular disease, which affects blood flow to the brain\n- Substance use disorders"},"c19.eligibility.moreinfo/healthcare_worker.pa.1c":{"en-us":"Health care personnel including, but not limited to:\n- Emergency medical service personnel\n- Nurses\n- Nursing assistants\n- Physicians\n- Dentists\n- Dental hygienists\n- Chiropractors\n- Therapists\n- Phlebotomists\n- Pharmacists\n- Technicians\n- Pharmacy technicians\n- Health professions students and trainees\n- Direct support professionals\n- Clinical personnel in school settings or correctional facilities\n- Contractual HCP not directly employed by the health care facility"},"c19.eligibility.moreinfo/essential_worker.pa.1c":{"en-us":"These include:\n- People in congregate settings not otherwise specified as long-term care facilities, and persons receiving home and community-based services\n- First responders (including Law enforcement and Firefighters)\n- Correctional officers and other workers serving people in congregate care settings not included in Phase 1A  \n- Food and agricultural workers\n- U.S. Postal Service workers\n- Manufacturing workers  \n- Grocery store workers  \n- Education workers \n- Clergy and other essential support for houses of worship \n- Public transit workers\n- Individuals caring for children or adults in early childhood and adult day programs\nTransportation and logistics workers\n- Water and wastewater workers\n- Food service workers\n- Housing construction workers\n- Finance, including bank tellers workers\n- Information technology workers\n- Communications workers\n- Energy, including nuclear reactors workers\n- Legal services workers\n- Federal, state, county and local government workers, including county election workers, elected officials and members of the judiciary and their staff\n- Media workers\n- Public safety workers\n- Public health workers"},"c19.eligibility.moreinfo/age.are_you_age.pa.1c":{"en-us":"This includes:\n- Cancer\n- Chronic kidney disease\n- Chronic lung diseases, including COPD (chronic obstructive pulmonary disease), asthma (moderate-to-severe), interstitial lung disease, cystic fibrosis, and pulmonary hypertension\n- Dementia or other neurological conditions\n- Diabetes (type 1 or type 2)\n- Down syndrome\n- Heart conditions (such as heart failure, coronary artery disease, cardiomyopathies or hypertension)\n- HIV infection\n- Immunocompromised state (weakened immune system)\n- Liver disease\n- Overweight and obesity\n- Pregnancy\n- Sickle cell disease or thalassemia\n- Smoking, current or former\n- Solid organ or blood stem cell transplant\n- Stroke or cerebrovascular disease, which affects blood flow to the brain\n- Substance use disorders"},"c19.eligibility.moreinfo/age.16_up.pa.2":{"en-us":"All individuals not previously covered who are 16 and older and do not have a contraindication to the vaccine (note that at this time, only the Pfizer-BioNTech product is approved for those age 16 and 17)"}}}}]


local.functions.nhost.run  --> local.functions.local.nhost.run transition incomplete?

Describe the bug
At some point, the local development URLs went from
https://local.functions.nhost.run
to
https://local.functions.local.nhost.run
So this broke my application, and in trying to fix it, there are places internally where the former is still used, e.g. the docker-compose.yaml generated by nhost
The @nhost/nhost-js module is the latest version, and it returns https://local.functions.nhost.run for the functions URL, not the latter.
So which URL to use? Is the goal to be consistent? Or are there places where one is used and not the other?
The app especially breaks when there are communication between services and those URLs need to be known ahead of time.
To Reproduce
Start the nhost stack and you see:
Nhost development environment started.
URLs:
- Postgres:         postgres://postgres:postgres@localhost:5432/local
- Hasura:           https://local.hasura.local.nhost.run
- GraphQL:          https://local.graphql.local.nhost.run
- Auth:             https://local.auth.local.nhost.run
- Storage:          https://local.storage.local.nhost.run
- Functions:        https://local.functions.local.nhost.run
- Dashboard:        https://local.dashboard.local.nhost.run
- Mailhog:          https://local.mailhog.local.nhost.run

Then look in the docker-compose. The urls will be the older form
Get the nhost.functions.url from the NhostClient from the module<EMAIL_ADDRESS>It returns the former not the newer latter.
Expected behavior
All URLs are in the newer form.
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS:macos
Browser Chrome
Version: 128.0

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
❯ nhost --version
nhost version v1.24.0

Hello,
thanks for raising the issue.

At some point, the local development URLs went from

Here you can see it in the release notes:
https://github.com/nhost/cli/releases/tag/v1.22.1
We also announced it on discord and it's in the dashboard under "Latest announcements".
I understand it is virtually impossible to read the release notes of every software you update but I'd advise reviewing them if something unexpected happens. We usually add lots of warning emojis to make them stand out when there is something that could have some impact.

So this broke my application

This is unexpected as old URLs should still work. Could you detail how this broke your application?

there are places internally where the former is still used, e.g. the docker-compose.yaml generated by nhost

I am looking at the docker-compose file and all I see is that both the old and the new URL should work:

this is in the functions container:

        labels:
            ...
            traefik.http.routers.functions.rule: (HostRegexp(`^.+\.functions\.local\.nhost\.run$`) || Host(`local.functions.nhost.run`))&& PathPrefix(`/v1`)
            ...

which should cause it to respond to both urls.

this is in every container:

        extra_hosts:
            ...
            - local.functions.local.nhost.run:host-gateway
            ...
            - local.functions.nhost.run:host-gateway
            ...

So every container should know how to reach both urls.

The @nhost/nhost-js module is the latest version, and it returns https://local.functions.nhost.run for the functions URL, not the latter.

This is explained in the docs

So which URL to use? Is the goal to be consistent? Or are there places where one is used and not the other?

The goal is to migrate but nothing should break and both are currently supported while people transition.

The app especially breaks when there are communication between services and those URLs need to be known ahead of time.

As mentioned before, this is unexpected so if you can provide more information and steps to reproduce that would be greatly appreciated as based on our tests things should work.
Thanks again for raising the issue. Please, let us know how to reproduce this because the goal was to make things backwards compatible for the time being. If it's not too much of a hassle a repo reproducing the issue would be greatly appreciated (or even just a PR making the issue obvious in the "test project" we have in the cli repo: https://github.com/nhost/cli/tree/main/examples/myproject

Has this been updated for local dev javascript libraries such as '@nhost/react-apollo' and "@nhost/nextjs" ? It appears they still call the old urls. I fixe by adding both old and new urls to hosts file. But definitely a bit confusing to debug.

Has this been updated for local dev javascript libraries

There is nothing to update, please, read my previous message and, in particular, the linked release noted.

I fixe by adding both old and new urls to hosts file

Which hosts file? You shouldn't need to edit anything.

But definitely a bit confusing to debug

What was broken? Which error were you getting? How can we reproduce?

Got it, thanks. You can close this issue. Yes, I did not read the release notes, since I assumed this was a bug since it was confusing. Appreciate the detailed response 👍🏻

Ok, cool, if you have more questions don't hesitate to let us know.


Authorization.hasPermission always returns FALSE

Hello! Help me Please! Authorization.hasPermission("") in .....Grid.ts  always returns FALSE. Granted permissions to the user and role. ((
in UserEndpoint.cs changed "ScriptUserPermissions:" on "UserPermissions:", did not help.
In ...Row.cs for fields works without problems.
protected getColumns() {
..........
           alert(Authorization.hasPermission("Role:FRP"));
            alert(Authorization.hasPermission("Razr"));
            alert(Authorization.hasPermission("Role:RP"));
            alert(Authorization.hasPermission("FRP"));
.......
}

I also set up LDAP Authorization

Don't change anything, open a new Serene project, check what you changed to break it.

In another project without LADA, everything works fine. When connecting LDAP I used the instruction
https://volkanceylan.gitbooks.io/serenity-guide/content/howto/how_to_authenticate_with_active_directory_or_ldap.html

It changes nothing.

Hooray! Found! Precisely calculate and describe.


0.4.3 not tagged on github

it's listed here:
http://www.lihaoyi.com/fastparse/#ChangeLog
would be nice to easily find the tag on github.

lol I don't remember which commit was 0.4.3 -.-
I guess I'll have to go dig for it

Maybe I should go publish a new release 0.4.4 and hope nobody notices

I assume it's 0.4.3 is https://github.com/lihaoyi/fastparse/commit/dcb44cc0ec73d0d680bc29322afb47625316a68e but don't remember for sure...

If you upgrade to 0.4.4,then I will upgrade too:)

I've tagged 0.4.4 and 1.0.0, both if which should be identical to 0.4.3 except for publishing bits and pieces for scala-native. You can depend on those if you want more certainty about what code is actually running


Implementing specific NumPy functions in CuPy

As a part of a course project, I'd like to contribute to CuPy. I reached out to @kmaehashi who told me I could start by implementing simple functions which are not yet present in CuPy according to this Comparison Table.
I would like to start by implementing numpy.argwhere in CuPy. It would be great if someone could guide me on what I can do to implement it.
Thanks!

Sorry I haven't responded here after replying to you via email...
Closing as this issue is not active for months.
For those who need support when contributing to CuPy, please join the Gitter chat so that we can help you.


[Bug]: Templates - Customer messaging tool template gives resource not found error

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When I generate page from the Customer messaging tool template - i get a resource not found error
Steps To Reproduce

Login to release
Go to an existing app or create a new app
Generate a page from template
Use Customer Messaging Tool template and try to add selected pages
An error comes up - Resource not found

Public Sample App
No response
Issue video log
No response
Version
Release

Resolved by @jacquesikot


[AutoTransform][Crawler] Crawl transformer files

Use OpenAI model to improve code quality
ADDED AUTOMATICALLY BY AUTOTRANSFORM
Learn more about AutoTransform here
Schema and batch information for the change below
<<<Automation Info Gist: 436c2f162593671f7c0cf231792dae5a>>>

Interesting issues here. It seems to get very confused about the new line stuff. I wonder if I should add Commands as well, that would let me run black on the file before linting/mypy on it. Could save some back and forth cycles.


RUN TESTS or Submit the Code not woking

When I am trying to submit the code no action takes place, the screen remains still as it is. I have tried numerous waypoints to see if a particular one is not working, but the same problem still exists. ASAP
Thank You

@CrypticGuy : Check if your brpwser has coookies enabled, also clear your browser cache.
You should also refer : https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/Help-I've-Found-a-Bug
If issue still persists, please post screen shots, and detailed steps.
Thanks.

I'm having this issue now on both firefox and chrome. It seems to apply only to Waypoint 37 for me in "HTML5 and CSS" since I've completed way points both before and after that specific one. I've cleared the cache on both browsers but the problem remains.

If you are still experiencing this problem please reopen with more details and repro steps. Thanks and happy coding!


[routing-manager] treatment of domain prefixes

I see some issues with the current code (because the code in 'main' already changed I think since the merge of this PR, I used the 'main' code branch as a reference for routing-manager).  Basically the question of whether a prefix is a valid OMR prefix is separate from whether the prefix should be advertised in a RIO. Per the spec <IP_ADDRESS>, a Domain Prefix (P_dp=1) is a valid OMR prefix. Current method IsValidOmrPrefix() is not compliant with that.   Separate from the valid OMR prefix question, a Domain Prefix is just never advertised in RIO because it's considered as on-link on the backbone link.
https://github.com/openthread/openthread/blob/main/src/core/border_router/routing_manager.cpp#L888
Originally posted by @EskoDijk in https://github.com/openthread/openthread/issues/7900#issuecomment-1210523831

Thanks @EskoDijk .

Submitted https://github.com/openthread/openthread/pull/8014 for this.

Ok, looks good - thanks.


Display exception when using iframe

demo: https://codesandbox.io/s/react-slick-playground-forked-qmwfv8

react-carousel CSS is not imported in the demo


Support Aqua S2 Lock and Aqara Curtain

All code was tested on real devices, The lock still have Latch and door state not decode, i will finish later. About the curtain if use on/off it will report state like light/switch if use upOpen/downClose it will report state of genWindows but now could not read. Lift is standard for curtain (but i have not tested it) and dim is Xiaomi custom but some time it not report state back so we will use both for complete solution. So you can merge those code

Could you respond to the questions in the TODO comments? I need this to properly integrate it with zigbee2mqtt/homeassistant.

I tested some of it now:
ZNCLDJ11LM_control_percentage  works for opening and closing the curtain by giving a percent value (0-100), where 100 means fully open and 0 is fully closed.
I do not know what ZNCLDJ11LM_curtain_lift is for, as it does not seem to work.
upOpen and downClose is a standard for blind and curtain motors (hence up/open and down/close).
For ZNCLDJ11LM_control I had to change to lookup code to
const lookup = {
                'open': 'upOpen',
                'close': 'downClose',
                'stop': 'stop',
                'on': 'upOpen',
                'off': 'downClose',
            };

            value = value.toString().toLowerCase();
            if (lookup[value]) {
                value = lookup[value];
            }

I will test the fromZigbee part soon and would really like to get this converter to be finalized.


Gemini 1.5 Flash: Candidate was blocked due to RECITATION when responseMimeType is json

Description of the bug:
When responseMimeType: 'application/json', a request is failing with error:
[GoogleGenerativeAI Error]: Candidate was blocked due to RECITATION.
However, without responseMimeType, the same prompt works (returns a markdown with json).
The exact same instructions and prompt work on the AI Studio, even with output in JSON on.
// The error happens even if safety settings are set to block none.
const safetySettings = [
  {
    category: HarmCategory.HARM_CATEGORY_HARASSMENT,
    threshold: HarmBlockThreshold.BLOCK_NONE,
  },
  {
    category: HarmCategory.HARM_CATEGORY_HATE_SPEECH,
    threshold: HarmBlockThreshold.BLOCK_NONE,
  },
  {
    category: HarmCategory.HARM_CATEGORY_SEXUALLY_EXPLICIT,
    threshold: HarmBlockThreshold.BLOCK_NONE,
  },
  {
    category: HarmCategory.HARM_CATEGORY_DANGEROUS_CONTENT,
    threshold: HarmBlockThreshold.BLOCK_NONE,
  },
]

const model = this.genAI.getGenerativeModel({
  model: 'gemini-1.5-flash-latest',
  systemInstruction: instructions,
  safetySettings,
})

const generationConfig = {
  temperature: 0,
  topP: 0.95,
  topK: 64,
  maxOutputTokens: 8192,
  responseMimeType: 'application/json', // fails only if this option is sent.
}

const chatSession = model.startChat({
  generationConfig,
})

const result = await chatSession.sendMessage(prompt)
const text = result.response.text() // throws [GoogleGenerativeAI Error]: Candidate was blocked due to RECITATION.

Actual vs expected behavior:
Actual: Throws [GoogleGenerativeAI Error]: Candidate was blocked due to RECITATION
Expected: Return the same result as in the AI Studio.
Any other information you'd like to share?
No response

Hi @marian2js, sorry for the troubles. Does every prompt cause this, or only specific prompts? If it's a specific prompt, are you able to share the prompt so we can try to reproduce it?

Hi @ryanwilson. The issue happens only with a very specific prompt that I cannot share publicly. I've been trying to remove the personal data from it, but as soon as I do, it starts working.
I noticed that when I remove the responseMimeType, the JSON returned in the markdown is invalid as it has a js variable: { "key": value }. However, with a different prompt the model returned the invalid json, so I don't know if the issue is related to that.
I am sorry for not being of more help.

No worries! Out of curiousity, do you run into the same issue if you use sendMessageStream instead of sendMessage? That could be the difference with AI Studio, where the response is streamed.

Hi @ryanwilson, the bug doesn't happen with sendMessageStream. I made changes to my prompt, so this bug is not triggered anymore for me. But I can confirm the bug is still happening with my old prompt and sendMessage.

Hi guys,
I'm experiencing the exact same problem as @marian2js. We're using Gemini with Vertex to extract structured data (as JSON) from job offer listing PDFs.
Here's what I've tried so far:

Using the 1.5 Pro model instead of the Flash model
Switching to sendMessageStream from sendMessage
Using 1.0 Pro (works, but the output is non-usable)

Oddly enough, the issue seems to only happen when processing non-English documents. When I upload PDFs in French, I always run into the RECITATION problem.
On the flip side, if I use Google Vision for OCR on the PDF, and then use the Vercel AI SDK with chat and Gemini 1.5 Flash, it works perfectly with the same prompt, but on the OCR data (string) instead of the inline PDF.
Hope this info helps in figuring out the issue!

Hi folks,
Running into the same problem as @marian2js (with almost identical API call settings but with Golang - model conf, generationConfig, SafetyConfig all the same). Again parsing a plaintext file with a big prompt to output JSON (where the plaintext was originally converted from PDF).
Setting model.GenerationConfig.ResponseMIMEType = "application/json" hits the "blocked: candidate: FinishReasonRecitation" resp with no PromptFeedback value, annoyingly, so flying a bit blind as to the cause.
If it's helpful the content is senior school syllabus so shouldn't be anywhere close to hitting any of the harm response thresholds either way.
Commenting ResponseMIMEType with a slight prompt modification gets a usable (yet obviously inconsistent) result.
Much appreciated!

Experiencing same issue as well, same setup as others above.

Changing to stream mode worked for me as well:
const safetySettings = [
   {
     category: HarmCategory.HARM_CATEGORY_HARASSMENT,
     threshold: HarmBlockThreshold.BLOCK_NONE,
   },
   {
     category: HarmCategory.HARM_CATEGORY_HATE_SPEECH,
     threshold: HarmBlockThreshold.BLOCK_NONE,
   },
   {
     category: HarmCategory.HARM_CATEGORY_SEXUALLY_EXPLICIT,
     threshold: HarmBlockThreshold.BLOCK_NONE,
   },
   {
     category: HarmCategory.HARM_CATEGORY_DANGEROUS_CONTENT,
     threshold: HarmBlockThreshold.BLOCK_NONE,
   },
];

try {
           const chatSession = this.model.startChat({
               generationConfig: {
                   temperature: 1,
                   topP: 0.95,
                   topK: 64,
                   maxOutputTokens: 8192,
                   responseMimeType: "text/plain",
               },
               history: history,
               systemInstruction: systemMessage,
               safetySettings: safetySettings
           });

           var stream = true;
           if (stream) {
               const result = await chatSession.sendMessageStream(currentMessage);
             for await (const item of result.stream) {
                   console.log("Stream chunk: ", item.candidates[0].content.parts[0].text);
               }
               const aggregatedResponse = await result.response;
               return aggregatedResponse.text();
           } else {
               const result = await chatSession.sendMessage(currentMessage);
               return result.response.text();
           }
       } catch (error) {
           console.error("Error during chat session:", error);
           throw error; // Re-throw the error after logging or handle it as needed
       }

I started to receive this today as well, didn't get it at all yesterday and I made hundreds of calls, now today a significant number of them are receiving the error.

Also getting this error.

Any updates on this? As it stands at the current moment, using Gemini Pro 1.5 for RAG-base Q/A with chat history is incredibly unreliable.
Simply ask 2-3 questions about a document with some overlap, and you will encounter a RECITATION error almost guranteed.
I.e, using LangChain:
const chatTemplate = ChatPromptTemplate.fromMessages([['system', 'You are a helpful assistant. Answer all questions to the best of your ability.'], new MessagesPlaceholder('history'), new MessagesPlaceholder('input')]);
	const chain = chatTemplate.pipe(pdfModel).pipe(new StringOutputParser());

const chainWithHistory = new RunnableWithMessageHistory({
		runnable: chain,
		getMessageHistory: () => chatHistory,
		inputMessagesKey: 'input',
		historyMessagesKey: 'history',
		config: { configurable: { sessionId: decodedToken.uid } }
	});

	const response = await chainWithHistory.invoke({ input: input });

If you simply ask the model to recite a specific section of a file/PDF twice in a row, you will get a Recitation error GURANTEED (whether you pass the input File in once at the beginning of the conversation, only in the latest message, or as part of every message input is irrelevant).

I'm getting the same error.
Isn't there a way to know in advance if the input contains something which might cause this error, and then skip that ??

Hi @ryanwilson, the bug doesn't happen with sendMessageStream. I made changes to my prompt, so this bug is not triggered anymore for me. But I can confirm the bug is still happening with my old prompt and sendMessage.

I have tried the same, it seems the issue still persists with sendMessageStream as well.
One more interesting thing I found was, when using sendMessageStream, along with some tools, it is producing 500 Internal Server Error.

I have the same problem, I'm sending the screenshot of a PDF, it works in some cases but not in others

i also have the same problem.
i ran 1.0 pro vs 1,5 flash (as i got the email for it becoming deprecated soon) - i tried 1.5 pro as well
when running 1.0 & 1.5 pro, i have zero issues, no matter how many time i retry the same content generation in a row, or how many times i send (assuming im not limited)

yet, when i run gemini-1.5-flash, exact same prompt, exact same code, i would randomly get the recitation error (that i am currently not handling in catch to just see it easily on console)

thing is, its not even particularly faster than the 1.0 pro. the 1.5 pro also does not give this error.
i am running the free version so im comparing 1.0 pro and 1,5 flash mostly as they both have similar request limitations.

i also have the same problem.
i ran 1.0 pro vs 1,5 flash (as i got the email for it becoming deprecated soon) - i tried 1.5 pro as well
when running 1.0 & 1.5 pro, i have zero issues, no matter how many time i retry the same content generation in a row, or how many times i send (assuming im not limited)

yet, when i run gemini-1.5-flash, exact same prompt, exact same code, i would randomly get the recitation error (that i am currently not handling in catch to just see it easily on console)

thing is, its not even particularly faster than the 1.0 pro. the 1.5 pro also does not give this error.
i am running the free version so im comparing 1.0 pro and 1,5 flash mostly as they both have similar request limitations.
i did not change any settings, didnt set up safety or response type or anything, so all there should be the default

By any chance, have you tried using tools? And experimented with various models?
Also, any work done on sendMessage & sendMessageStream?

By any chance, have you tried using tools? And experimented with various models? Also, any work done on sendMessage & sendMessageStream?

i am unsure what 'tools' is, so probably havent tried it.
i have tried different things with the different models, in prompt form, length, sending same one in a row vs sending different ones in a row, only Flash has the problem, and if pops up no matter what prompts im sending, usually after 2-3 sends, sometimes ca last to 4-5 without error but not as common.
as for sendMessage and sendMessageStream, i am mostly sending unrelated prompts, which is why i preferred using generateContent over openChat and sendMessage, and so i havent tried them for now.

@hsubox76 just wanted to page contributors here, this is a MAJOR bug, especially when you guys are sunsetting 1.0 pro and moving everyone to 1.5 flash. It is literally unusable right now with this recitation error. This is the only reason we cannot migrate over from other foundation models. You are losing out on customers.
Is anyone on the team looking at this?

Same problem here using Gemini 1.5 Pro

I have this problem using gemini-1.5-flash. If I send the same prompt a second time it shows me this error:
[GoogleGenerativeAI Error]: Candidate was blocked due to SAFETY
Prompt example:
Write a romantic sentence that includes the number '5' written exactly as '5'. Make sure the number appears in numerical format and not in words.
If you send the same thing but changing only the number, it generates the error. For example:
Write a romantic sentence that includes the number '73' written exactly as '73'. Make sure the number appears in numerical format and not in words.

Same issue! Looks like this issue is stock under the backlog pile.

This does seem like a serious issue - unfortunately it's beyond the ability of us to fix in the SDK. We're asking anyone to bring issues with the service or the models to the discussion forum: https://discuss.ai.google.dev/ where it will be more likely to reach those who cover the models themselves.
If posting in the forum, feel free to link back to this issue as it contains a lot of info and examples of the problem which might be helpful background, and if someone opens a thread in the discussion forum, please link it here so that all the JS SDK users facing this issue can add to that thread and hopefully get it looked at.
We will also try to get some answers internally but it's probably best for us to use all channels, including the discussion forum.

Hey folks, following up, we are investigating this and will share more details as soon as we have an update on our end!

Hey folks, following up, we are investigating this and will share more details as soon as we have an update on our end!

Hi Logan, any updates on this?

fyi - Here is a recitation failure I find reproducible and strange, the behavior/error differences between nodejs and console may be telling, perhaps the listing/encoding causes sensitivity but no changes to parameters can prevent error -
NO ERROR - CHESS OPENINGS - instructions prompt -
System: You are a service that returns tidy, single line list of domain items responses to prompts. Your response is only a comma seperated lists of items like 'item1, item2, item3..'. List as many items as performantly possible to enrich the data. If prompted for a list of fruits, you respond with 'apple, pear, banana, ..'. Do not include ‘..’ in the response, instead add as many items (10-50) as needed to fulfil the request in a timely manner. \n\nHuman: Given these instructions, the prompt asks for a comma separated list of chess openings, return your tidy response of items. \n\nAssistant: Here is the requested list of comma seperated domain items;
RECITATION ERROR - POKEMON - instructions prompt -
System: You are a service that returns tidy, single line list of domain items responses to prompts. Your response is only a comma seperated lists of items like 'item1, item2, item3..'. List as many items as performantly possible to enrich the data. If prompted for a list of fruits, you respond with 'apple, pear, banana, ..'. Do not include ‘..’ in the response, instead add as many items (10-50) as needed to fulfil the request in a timely manner. \n\nHuman: Given these instructions, the prompt asks for a comma separated list of pokemon, return your tidy response of items. \n\nAssistant: Here is the requested list of comma seperated domain items;

I am facing the same issue. Following this thread.

Facing the same issue with 1.5 Pro.

Facing the same issue for a RAG use case using gemini-1.5.pro. It's very unpredictable as the error depends on the output and not always the context/prompt.

Ran into this issue as well today.

Having the same issues with flash and pro. Impossible to use them in production.

having this same problem

Same issue here, although i am summarizing books from PDF provided by me. Could it be something about Authors' rights?

same issue here

Hey folks, following up, we are investigating this and will share more details as soon as we have an update on our end!

Logan any update?

can confirm same issue still

Hey folks, I am going to declare an internal code red on this until it is resolved, sorry it has taken so long. Will provide updates twice a week until it is resolved.

Update: We have found what we believe to be part of the problem when sending requests with JSON mode enabled. Potential fix in the works, will share more on the timeline once we see how it goes.
Note that it's not clear everyone in this thread has the same issue, the current fix we are looking at is for specifically requests sent with JSON mode enabled using 1.5 Flash and 1.5 Pro.

Update: We have found what we believe to be part of the problem when sending requests with JSON mode enabled. Potential fix in the works, will share more on the timeline once we see how it goes.
Note that it's not clear everyone in this thread has the same issue, the current fix we are looking at is for specifically requests sent with JSON mode enabled using 1.5 Flash and 1.5 Pro.

You're the best Logan! Appreciate the urgency! 👏

Update: We have found what we believe to be part of the problem when sending requests with JSON mode enabled. Potential fix in the works, will share more on the timeline once we see how it goes.
Note that it's not clear everyone in this thread has the same issue, the current fix we are looking at is for specifically requests sent with JSON mode enabled using 1.5 Flash and 1.5 Pro.

Just pointing out significant amount of examples with errors do not have JSON mode enabled.

Just pointing out significant amount of examples with errors do not have JSON mode enabled.

Yes echoing this statement. We found it happening with both JSON mode enabled and disabled.

Hi, I'm also suffering from the RECITATION problem when using Gemini Pro 1.5 with llamaIndex CondensePlusContextChatEngine. The problem only occurs (for me) on subsequent turns of the chat, not the first. Whether an exception is thrown seems to be dependent on the RAG and the user question, but is repeatable for the same conversation sequences. Looking forward to your fix - thanks very much!

Update: we discovered a bug related to JSON Schema mode and recitation checks, we rolled out the change yesterday and are monitoring the impact. This should help the issue of recitation errors when in JSON mode.
Note that as mentioned, this doesn't capture all of the recitation comments in this thread which is a mix of different use cases. We have not identified any known issues with other parts of the recitation checking at this time but are still investigating.

We have not identified any known issues with other parts of the recitation checking at this time but are still investigating.

If sending problematic prompts helps troubleshooting, I think everyone in this thread and on the bug tracker (https://issuetracker.google.com/issues/331677495?pli=1) would be more than happy to send a few ;)

The inconsistent but frequent occurrence (almost daily) of this error effectively makes the API useless for our use-case and we switched back to Claude.

Same here. I'm still hoping for the bug to be fixed at some point but it looks like this is somehow expected behaviour (?) if no issue with the recitation checker has been found.

Thanks @logankilpatrick! We have been fighting with this over past week trying to pull glossary terms out some documents we use for work. Almost to point where was going to have to consider changing LLMs.
I changed some of our prompting around today and did not get the error where we usually do (json mode enabled using 1.5 pro). Thought was my prompting but maybe was this change. Will test further.

Can confirm that previous test examples (gemini flash 1.5 in JSON mode) that used to cause the error, no longer cause issues

Our users get hundreds of RECITATION errors a day, with JSON mode disabled. Luckily we fallback to other LLM APIs who do not suffer from such a glaring flaw, and can handle the exact same prompts fine. Typically, the error occurs when the prompt requests that the LLM repeat something from earlier in the conversation, with some formatting change, for example. Many such prompts result in RECITATION errors. Is this the intent behind the RECITATION blocker? That it prevents the model from repeating text strings from earlier in the chat conversation? If this is the case than it greatly reduces the utility of the API. I was under the impression that the intent was to block reciation of training data.

Any update on this? it is back to blocking us now. We are trying to use gemini to extract key terms/glossary from documents. There are some docs that it fails nearly 100% of time with, even with some of the creative prompting.

hi, is there any update on this?

I faced this issue now with JSON mode disabled. The use case is code generation which seems pretty basic.

This model cannot be used with RAG nor perform OCR on book pages because of the recitation restrictions.

YOU GUYS CAN TRY THIS CODE IT WORKED FOR ME AND GENERATING THE RESULTS
I HAVE USE NPM
import { GoogleGenerativeAI, HarmCategory, HarmBlockThreshold } from "@google/generative-ai";
// Fetch your API_KEY
const API_KEY = "";  // Replace with your actual API key
// Initialize the AI model
const genAI = new GoogleGenerativeAI(API_KEY);
const model = genAI.getGenerativeModel({ model: "gemini-1.5-flash" });
// Define safety settings
const safetySettings = [
{
category: HarmCategory.HARM_CATEGORY_HARASSMENT,
threshold: HarmBlockThreshold.BLOCK_NONE,
},
{
category: HarmCategory.HARM_CATEGORY_HATE_SPEECH,
threshold: HarmBlockThreshold.BLOCK_NONE,
},
{
category: HarmCategory.HARM_CATEGORY_SEXUALLY_EXPLICIT,
threshold: HarmBlockThreshold.BLOCK_NONE,
},
{
category: HarmCategory.HARM_CATEGORY_DANGEROUS_CONTENT,
threshold: HarmBlockThreshold.BLOCK_NONE,
},
];
document.getElementById("generate").addEventListener("click", async () => {
const prompt = document.getElementById("prompt").value;
const codeDiv = document.getElementById("code");
const contentDiv = document.getElementById("content");
codeDiv.innerHTML = "";
contentDiv.innerHTML = "Generating...";
try {
    const chatSession = model.startChat({
        generationConfig: {
            temperature: 1,
            topP: 0.95,
            topK: 64,
            maxOutputTokens: 8192,
            responseMimeType: "text/plain",
        },
        safetySettings: safetySettings
    });

    var stream = true;
    let resultText = '';

    if (stream) {
        const result = await chatSession.sendMessageStream(prompt);

        // Process the streaming response
        for await (const chunk of result.stream) {
            if (chunk.candidates && chunk.candidates[0].content && chunk.candidates[0].content.parts) {
                resultText += chunk.candidates[0].content.parts.map(part => part.text).join('');
            }
        }

        // Finalize the result
        contentDiv.innerHTML = `<pre>${resultText}</pre>`;
    } else {
        const result = await chatSession.sendMessage(prompt);
        resultText = await result.response.text();
        contentDiv.innerHTML = `<p>${resultText}</p>`;
    }
} catch (error) {
    console.error("Error generating content:", error);
    contentDiv.innerHTML = handleErrors(error);
}

});
function handleErrors(error) {
if (error.message.includes("RECITATION") || error.message.includes("content blocked")) {
return "The generated content was blocked. Please try a different prompt or adjust your input.";
} else {
return An error occurred: ${error.message}. Please try again later.;
}
}

We just shipped another update which should help reduce recitation blocks in cases where the context was sent in the request (RAG situations).

We just shipped another update which should help reduce recitation blocks in cases where the context was sent in the request (RAG situations).

Are you planning to do the same with OCR implementations?
I'm giving Gemini flash a book's page image for it to return the text in it and it's giving me the recitation error making it unusable.
It doesn't make any sense since this book was written by Tolstoy (War and peace), no copyright infringement whatsoever.

I will look into this ^
We also have another change in the works that should decrease the chance you get a recitation block on a simple code sample, it will take about ~2 weeks to fully roll this out, but stay tuned!

We just shipped another update which should help reduce recitation blocks in cases where the context was sent in the request (RAG situations).

I am trying gemini-1.5-pro-001 with pdf's and have used all sort of block levels, including BLOCK_NONE for the safety settings. And every time run into the error: he candidate is likely blocked by the safety filters......  "finish_reason": "RECITATION",

Is this error particularly bad with pdf's or does it not matter?

This issue is the only thing preventing me from using Gemini. Very sad...
On Sat, Aug 10, 2024 at 6:04 PM meheli-basu @.***>
wrote:

We just shipped another update which should help reduce recitation blocks
in cases where the context was sent in the request (RAG situations).
I am trying gemini-1.5-pro-001 with pdf's and have used all sort of block
levels, including BLOCK_NONE for the safety settings. And every time run
into the error: he candidate is likely blocked by the safety filters......
"finish_reason": "RECITATION",
erroe.PNG (view on web)
https://github.com/user-attachments/assets/d82f997e-3bb3-4042-be85-efeba1150376
Is this error particularly bad with pdf's or does it not matter?
—
Reply to this email directly, view it on GitHub
https://github.com/google-gemini/generative-ai-js/issues/138#issuecomment-2282335935,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATGSZ5LNJ5BY4VRBD5TJSWTZQ22BLAVCNFSM6AAAAABHYJ3WM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSGMZTKOJTGU
.
You are receiving this because you commented.Message ID:
@.***>

Hey @logankilpatrick! Has this change rolled out yet?

fyi, i tried streaming too for OCR, but it stops due to RECITATION. Are you planning to solve this ?

I have the same issue with OCR @logankilpatrick. I am providing with public research papers and it suddenly stops and says

Really disappointing to see a great model become absolutely unusable on so many use cases.

Just chiming to add that for almost all OCR tasks I am getting this error.

Trying to condense some PDF content down into manageable markdown summaries and this RECITATION error is just a complete dealbreaker using Flash. Random, annoying, and silly. Temperature set to 1. Pro seems to work better but still throws the RECITATION error, just a little less often.
Going to have to use PyPDF probably and switch to a different product. Unusable for my business.

Google doesn't seem to realize just how many people this one bug is turning
away.
On Wed, Aug 28, 2024, 2:54 PM Brandon Foltz @.***>
wrote:

Trying to condense some PDF content down into manageable markdown
summaries and this RECITATION error is just a complete dealbreaker using
Flash. Random, annoying, and silly. Temperature set to 1. Pro seems to work
better but still throws the RECITATION error, just a little less often.
Going to have to use PyPDF probably and switch to a different product.
Unusable for my business.
—
Reply to this email directly, view it on GitHub
https://github.com/google-gemini/generative-ai-js/issues/138#issuecomment-2316313721,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATGSZ5NYP54ZF2EKZY5BLU3ZTZBLDAVCNFSM6AAAAABHYJ3WM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJWGMYTGNZSGE
.
You are receiving this because you commented.Message ID:
@.***>

Literally. I wanted to switch from Claude 3.5 Sonnet to Gemini 1.5 Pro in my app, but I couldn't run the test because 9 times out of 10 returns an error between RECITATION or SAFETY (for things that are totally safe 😅)
Not realiable = immediate turn off

I’m using the Gemini 1.5 Pro EXP model API with the image shown below, but I’m encountering the same issue. Here’s the error I’m receiving:
Response:
python
GenerateContentResponse(
    done=True,
    iterator=None,
    result=protos.GenerateContentResponse({
      "candidates": [
        {
          "finish_reason": "RECITATION",
          "index": 0
        }
      ],
      "usage_metadata": {
        "prompt_token_count": 407,
        "total_token_count": 407
      }
    }),
)

Here’s the code I’m using:
import google.generativeai as genai
import os
import PIL.Image
from dotenv import load_dotenv
from google.generativeai.types import HarmCategory, HarmBlockThreshold

load_dotenv()

# Configure the API key
genai.configure(api_key=os.environ["GEMINI_API_KEY4"])

# Define generation configuration
generation_config = {
    "temperature": 0,
    "top_p": 0.95,
    "top_k": 64,
    "max_output_tokens": 8192,
    "response_mime_type": "text/plain",
}

# Create a GenerativeModel instance
model = genai.GenerativeModel(
    model_name="gemini-1.5-pro-exp-0827",
    generation_config=generation_config,
    safety_settings={
        HarmCategory.HARM_CATEGORY_HATE_SPEECH: HarmBlockThreshold.BLOCK_NONE,
        HarmCategory.HARM_CATEGORY_HARASSMENT: HarmBlockThreshold.BLOCK_NONE,
        HarmCategory.HARM_CATEGORY_SEXUALLY_EXPLICIT: HarmBlockThreshold.BLOCK_NONE,
        HarmCategory.HARM_CATEGORY_DANGEROUS_CONTENT: HarmBlockThreshold.BLOCK_NONE,
    },
    system_instruction="""
    Extract questions and their corresponding options (if applicable) from an image of a question paper, including any directions, instructions, and question numbers. The extracted content should be formatted in LaTeX code, preserving the original structure and layout of the question paper.

    - **Questions**: Format each question with its number.
    - **Options**: Use the enumerate environment for multiple-choice options, labeling each option as (a), (b), (c), etc.
    - **Diagrams**: If a question includes a diagram, use the TikZ package to recreate the diagram in LaTeX. The TikZ code should be appropriately placed within the LaTeX document, ensuring the diagram aligns with the relevant question.
    """
)

# Path to the images folder
images_folder = "images"
image_files = [f for f in os.listdir(images_folder) if f.endswith('.png')]

# Process each image file
for image_file in image_files:
    image_path = os.path.join(images_folder, image_file)
    sample_image = PIL.Image.open(image_path)

    # Generate content based on the image
    response = model.generate_content([sample_image])

    # Print the generated LaTeX code or handle the response as needed
    print(response)

When I use the same image and system instruction in the Gemini AI Studio Playground, I receive the correct response. You can see the following images:
1.The first image shows the API response.

The second image shows the Gemini AI Studio Playground response.

The third image shows the safety settings.

The fourth image is the sample image to process.

Just re-echoing my sentiments in https://github.com/google/generative-ai-docs/issues/257#issuecomment-2327587546
Asking what are the 12 star signs? also triggers recitation error. At this rate, nearly all general knowledge in Gemini's data set would have triggered recitation error.

Using the relatively new responseSchema parameter for JSON in the API seems to trigger RECITATION errors... never had them before.

It seems the recitation problem has been fixed with the latest models. In my tests, answer generation no longer stops prematurely. Before I resume a project on hold due to this issue, I'm gathering feedback from other users about their experiences with this and the new models. Does anyone still see 'finish_reason: RECITATION' in those triggering requests when switching to the new models?

Yeah it seems to have stopped with the latest models now, not tested it comprehensively but it seems better now.

It seems the recitation problem has been fixed with the latest models. In my tests, answer generation no longer stops prematurely. Before I resume a project on hold due to this issue, I'm gathering feedback from other users about their experiences with this and the new models. Does anyone still see 'finish_reason: RECITATION' in those triggering requests when switching to the new models?

They've improved it but the recitation filter is still fundamentally broken and will randomly block requests in an unpredictable manner. Just ran into another case a minute ago while doing some testing.

After doing some tests, it doesn't seem that the recitation has been fixed. I'm still getting ton of recitation errors when trying to extract data from provided input. All the requested data to extract is already in the input (law texts and attachments), so nothing sensitive or related to copyright.

Here's an example I'm seeing in my own enviroment:
    let result = await chatSession.sendMessageStream("Respond in  Markdown. Give me Tic Tac Toe in java.");

Sometimes it works sometimes it does not:
Error: [GoogleGenerativeAI Error]: Candidate was blocked due to RECITATION\n    at response.text (file:///D:/mais/mais-svc-gemini/node_modules/@google/generative-ai/dist/index.mjs:454:23)\n    at <anonymous> (D:\\mais\\mais-svc-gemini\\src\\index.ts:73:31)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"

Not acceptable.

I've been hitting this too. I'm trying to feed in an image of a page of a PDF and then running this prompt against it:

Convert this image into markdown. If there are multiple columns on the page turn them into a linear list. Keep any references and put them in a <span class=reference> tag. For images and charts and figures return a <div name="title of figure" data-bbox="ymin, xmin, ymax, xmax">alt text description of that image</div> where those are the bounding box coordinates, and place that div in the relevant location between the paragraphs of text.

Having this issue too. Using Gemini Pro 1.5 for OCR via JSON. I found a temporary work-around by adjusting the image. My use case is the user manually snips a part of a larger image/PDF for upload to Gemini, the workaround is to take a new snip image but intentionally make it larger than the target to trick the AI into thinking this is a totally new image. The trick only works for one response, then the RECITATION error occurs again.  It's also not 100%, but did resolve some instances.

i proved a pdf and asked to extract the data, i see the RECITATION error :(

I am also getting this error, any found some fix?

I've also run into a similar refusal issue with JSON mode and created a reproducible example here https://github.com/kym6464/gemini-spii-sample

category: HarmCategory.HARM_CATEGORY_UNSPECIFIED,

@vedtam HARM_CATEGORY_UNSPECIFIED is a returned harm category from the API. You should not send it in the API call.
The error message you had, can be roughly translated as:

One of your category in safetySettings, is not a valid category. The valid categories are:

HARM_CATEGORY_HATE_SPEECH
HARM_CATEGORY_SEXUALLY_EXPLICIT
HARM_CATEGORY_DANGEROUS_CONTENT
HARM_CATEGORY_HARASSMENT
HARM_CATEGORY_CIVIC_INTEGRITY

Thanks @altbdoor, that worked! Still, such a unintuitive error, they could just as easily print the bad category's name. The source code clearly lists UNSPECIFIED as a valid category:
/**
 * Harm categories that would cause prompts or candidates to be blocked.
 * @public
 */
export declare enum HarmCategory {
    HARM_CATEGORY_UNSPECIFIED = "HARM_CATEGORY_UNSPECIFIED",
    HARM_CATEGORY_HATE_SPEECH = "HARM_CATEGORY_HATE_SPEECH",
    HARM_CATEGORY_SEXUALLY_EXPLICIT = "HARM_CATEGORY_SEXUALLY_EXPLICIT",
    HARM_CATEGORY_HARASSMENT = "HARM_CATEGORY_HARASSMENT",
    HARM_CATEGORY_DANGEROUS_CONTENT = "HARM_CATEGORY_DANGEROUS_CONTENT"
}

i'm getting this too in cline (prev. Claude-Dev).

Asking Cline to place example json data for a Google Service account json file elicited this error on Gemini Pro.

Hi, I had this same problem, almost half of my request were returning the 'RECITATION' finish reason. I noticed I was using the model "gemini-1.5-flash", and just switching to the model "gemini-1.5-flash-002" seems to have solved the problem.

Just tested both flash and pro 002 versions, unfortunately still getting tons of recitation errors when prompting to extract data from my own input.

Same issue here :(

I was baffled to see citations of parts of the text that were blocked due to the recitation reason work perfectly fine in the gemini app with the same sources cited. What gives google the authority to recite someone else's work while people like us can't?? If you cite and say I got the text from this site, please extend us the same courtesy where you give us the text and let us do the citations.

Try adding the following in the prompt:
You are allowed to quote text from the document in order to provide the information requested but only if the quote is less than 8 words.

The problem is still present in the latest experimental models.

I have this problem with gemini-exp-1206 but not gemini-2.0-flash-exp


[IntelliJ Plugin] Update version and release notes

Purpose
$subject.
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[x] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #23210 into ballerina-1.2.x will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           ballerina-1.2.x   #23210   +/-   ##
================================================
  Coverage            14.59%   14.59%
================================================
  Files                   51       51
  Lines                 1411     1411
  Branches               219      219
================================================
  Hits                   206      206
  Misses                1189     1189
  Partials                16       16

Continue to review full report at Codecov.

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


[istio-service-deletion] Istio doesn't handle Service deletion correctly

Bug description
We saw the following weird behavior with Istio:

Start server pod with netcat server.
Create Service and a ClusterIP for the server pod.
Create client pod and connect to server through ClusterIP. Connection succeeds.
Delete service.
From client pod, connect to server through ClusterIP which no longer exists. Connection succeeds.

We were afraid that there was some caching delay going on. Then, we tried to see what happens when the endpoints of a Service change:

Start 2 server pods with sidecars.
Create server-1 Pod to match service selector.
Connect from client with sidecar. Confirm it connects to the right one.
Update server-2 Pod to match service selector and server-1 Pod to not match it.
Connect from client with sidecar. Confirm it connects to the new one.
Update both Pods to not match service selector.
Connect from client with sidecar. Confirm it doesn't connect anywhere.

This worked as expected. We then repeated the same experiment and changed the Service selector instead of the Pod labels, that worked as well. So the only problematic case seems to be Service deletion. Does Istio handle it properly?
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
When deleting a Service, connections to the deleted Service's ClusterIP should fail.
Steps to reproduce the bug

Start server pod with netcat server.
Create Service and a ClusterIP for the server pod.
Create client pod and connect to server through ClusterIP. Connection succeeds.
Delete service.
From client pod, connect to server through ClusterIP which no longer exists. Connection succeeds.

Version (include the output of istioctl version --remote and kubectl version --short and helm version if you used Helm)
Istio:
client version: 1.5.7                                                                                cluster-local-gateway version:                                                                                ingressgateway version: 1.5.7                                                                                pilot version: 1.5.7                                                                                data plane version: 1.5.7 (16 proxies)

Kubernetes:
Client Version: v1.16.4
Server Version: v1.16.15

How was Istio installed?
profile.yaml
Environment where bug was observed (cloud vendor, OS, etc)
Minikube

Hmm I forgot the area in the first message, let's try again:
[x] Networking
/area networking

Can you update to a supported version? See https://istio.io/latest/news/support/announcing-1.5-eol-final/

@howardjohn to answer:

Can you update to a supported version? See https://istio.io/latest/news/support/announcing-1.5-eol-final/

Yes, this is what we're doing. However, I thought this might still be of interest to upstream. Perhaps the issue is still here, or someone else bumps into it.


Severity.error Server does not support SSL, but it was required.

The command to reproduce the error: dart run stormberry migrate

@schultek

Put DB_SSL=false before running dart run strormberry migrate
You can copy full command here:
DB_SSL=false dart run stormberry migrate


Practice Lab 3.3 command bar - patch formula has invalid arguments

Module: 3
Lab/Demo: 3.3 Command Bar
Exercise: 1
Task  1.1 / Step 12
Description of issue - I have followed the instructions to enter the formula, however i have an error message on the formula (it doesn;t seem to recognise project outcomes as the source - please advise on the fix.
Repro steps:

The steps to add the Outcome Completed Date column are in Lab 1.5 - Columns, Exercise 5, Task 5.1 Steps 11-14. https://github.com/MicrosoftLearning/PL-200-Power-Platform-Functional-Consultant/blob/master/Instructions/Labs/LAB[PL-200]_M01L05_Columns.md#:~:text=Enter Outcome Completed Date for Display name
The Project Outcomes table should be created in Lab 1.4 Tables, Exercise 3, Task 3.1
This course is designed to completed in order, so each lab is a prerequisite to the next.


added option --with-index

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x ] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[ x] Searched the bugtracker for similar pull requests

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x ] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[ ] New extractor
[ x] New feature

Description of your pull request and other information
Manually sorting and renaming files after downloading a playlist is a pain.
Using the flexible -o (output format) option is too much for people who hates reading documentation.
For this purpose it should have a friendly option to download videos with index number in their file name.

"Too much" is adding a duplicate functionality. Rejected.


Explain the origins of the name

We are frequently asked what "Factory Girl" means, so this information
may be good to have in the README.

Resolved via https://github.com/thoughtbot/factory_girl/pull/943

I know this is an old issue but I think I may have an answer for people who are curious about the origins of this term.
Factory Girl is a name which is used in the UK, most notably in Ireland. It is used to refer to working-class women who worked in factories during the 1900's when women were introduced into the workplace fulfilling roles which were typically held by men (e.g. factory work).
During World War I and II almost all men in the United Kingdom were conscripted and sent over to France/Germany to fight in the war. This left an enormous deficit in the workforce as very little people were left to keep the country running and functioning. As a result, the women who were left behind inherited the responsibility of filling in for the depleted workforce taking up jobs in farming, factory work and other labor-intensive jobs typically assigned to men. Also, the mass production of weapons and ammunition that was required for the war effort were constructed by a female workforce. The significant shift in gender in this typically male profession gave birth to the nickname "Factory Girls".
The nickname "Factory Girl" has always been used as an extremely endearing and empowering term for working women. Icons such as Rosie the Riveter stood as a proud symbol of a generation of strong, capable, willing and highly respected women in history who rose up to prove women were capable of stepping up to overcome the harsh situations of war to support the men fighting the war, do their part in protecting and defending their countries and families, and prove the perceived capabilities of the genders false. After the war, working-class women continued to work in such factory jobs and eventually were fully assimilated into the workplace as equals to men, taking an enormous step forward for women's rights, a truly incredible time in our nations history to be celebrated as both genders worked together (and emerged triumphant) in a common goal to defend the nation and prevent the NSDAP gaining more power in the world, ending the atrocious war crimes being committed.
Unfortunately, a stark contrast to the feminist outlook we see in the modern era after it was hijacked by the middle class to sell music videos and T-shirts, sell ads though clickbait Buzzfeed articles mainly complaining about how men are the problem to { print grievanceWithExBoyfriend }, pushing to widen the gender divide we are now all unwillingly part of, bloggers and gender studies dropouts sitting around complaining that they haven't been approached with a job offer to be CEO of Google yet etc etc.
Now it seems we require to cause completely unnecessary technical complications due to people pretending to be offended by the word "girl" and all the guys who are pathetically posturing to girls because they self-identify as having no other value as a man to display than fake valiant white knight-ing. Censoring the term "Factory Girl" in the name of feminism marks the slow death of intelligent thought in the IT industry and we should speak out against this growing trend if we ever wish to remove this toxic, unintelligent, uneducated and nonsensical style of thought from our industry, our generation, and our wider society in general.

I believe AI (AI-driven) bots will generate much more discrimination claims in a very close future and you will have to rename again..


Add screenshots to the doc

Add at least one screenshot to the readme and to the docs/index.md to show what this theme generates.

Done in https://github.com/Paul-Riviere/mkdocs-curriculum-vitae/issues/33