Trouble adding the OpenAI API key

I'm having trouble adding the OpenAI API key. It's showing a warning sign. Can you help me fix this?
Thanks in Advance

I have reviewed all the models, including the 3.5 turbo, 4, and 4.0 versions. Additionally, I attempted to resolve the issue on a PC by installing the software locally, but the problem persisted there as well.
Thanks

When I enter the API key, only a warning sign appears (image attached in first post), and no error message is displayed. Upon beginning work, it says no models are associated with this account.

Please try out the new version, which displays error messages in the user interface. You can install the new version (0.1.3) with the following command (or using pip install data-formulator --upgrade)
pip install data-formulator==0.1.3
For example, an openai key related errors will be displayed in this way:

I upgraded data formulator but still problem persist.
Again I tried all the model 3.5 turbo, 4 & 4o but no luck
I don't have azure openai access

This looks like an OpenAI model name issue!
You can use the following command to list models available to your openAI key (based on https://platform.openai.com/docs/api-reference/models/list)
curl https://api.openai.com/v1/models \
  -H "Authorization: Bearer $OPENAI_API_KEY"

And then find a model exist with your key and type it into the Model field. :)


twister: add --report-summary switch

Added a switch that show failed/error report from the last run.
Default shows 10 items. However, you can specify the number of items
(e.g. --report-summary 15).
It also works well with the --outdir switch

when there is nothing to show, i.e. no errors/fails, it would be nice to have a message saying that, otherwise the output can be confusing.

@golowanow
Currently, the default value is 0, which displays all found issues. I think this is a good way to apply all the changes you suggested.


[5.7][RemoteMirror] Put a limit on pointer-chasing loops to avoid infinite loops. Report Slab's Next pointer as a separate chunk.

Cherry-pick https://github.com/apple/swift/pull/42369 to release/5.7.
When iterating over linked lists in the target process, bugs or corrupt data might cause us to enter an infinite loop. Limit these loops to a fixed number of iterations so that we fail more gracefully. These limits should be set to a level that no healthy program will approach.
Report Slab's Next pointer as a separate chunk in asyncTaskSlabAllocations. This lets tools see it as a pointer and see the connection to the next slab.
rdar://91289920

@swift-ci please test

@swift-ci please test linux platform

https://github.com/apple/swift-integration-tests/pull/100
@swift-ci please test linux platform


kubectl label: Inconsistent messaging when both adding and removing labels

What happened:
What you expected to happen: kubectl label should produce a consistent, accurate message when labels are both removed and added at the same time (maybe just "labels modified" for simplicity?).
How to reproduce it (as minimally and precisely as possible):

$ kubectl label pod mypod a=b aa=bb
pod/mypod labeled

$ kubectl label pod mypod a- ee=ff
pod/mypod labeled # because the new label is textually longer

$ kubectl label pod mypod aa- e=f # same operations as above
pod/mypod unlabeled # different message, because the old label is textually longer

Anything else we need to know?: The problem seems to be the use of a length comparison in this function: https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/kubectl/pkg/cmd/label/label.go#L399-L408. That might be reliable if labels could only be added OR removed by an operation, but as in the examples above, both are possible at once.
Environment:

Kubernetes client and server versions (use kubectl version): Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.2", GitCommit:"5835544ca568b757a8ecae5c153f317e5736700e", GitTreeState:"clean", BuildDate:"2022-09-21T14:25:45Z", GoVersion:"go1.19.1", Compiler:"gc", Platform:"darwin/arm64"}
Cloud provider or hardware configuration: n/a
OS (e.g: cat /etc/os-release): n/a

/sig cli
Fixed by https://github.com/kubernetes/kubernetes/pull/110124

Although there is no direct relation but to distinguish label/unlabel message also causing this issue https://github.com/kubernetes/kubectl/issues/1265 as a symptom. If we decide to just say modified, this issue will also be fixed.

Got it, will fix it in PR https://github.com/kubernetes/kubernetes/pull/110124

/triage accepted
/priority backlog
/assign @astraw99

/remove-lifecycle stale

/assign

/remove-lifecycle stale

/remove-lifecycle stale


Adapter breaks iobroker Windows installation

When the tradfri adapter is installed on an iobroker installation that is setup using the Windows installation package following errors appear in the log and the iobroker instance stops working:
	info	Restart adapter system.adapter.tradfri.0 because enabled
	error	instance system.adapter.tradfri.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
	error	Caught by controller[1]: at process._fatalException (internal/bootstrap/node.js:497:27)
	error	Caught by controller[1]: at process.emit (events.js:198:13)
	error	Caught by controller[1]: at process.onUnhandledError (C:\Program Files\iobroker\TG24QA\node_modules\iobroker.tradfri\build\main.js:752:13)
	error	Caught by controller[1]: TypeError: Cannot read property 'log' of undefined
	error	Caught by controller[1]:
	error	Caught by controller[1]: ^
	error	Caught by controller[1]: adapter.log.error("unhandled exception:" + getMessage(err));
	error	Caught by controller[1]: \main.js:752
	error	Caught by controller[0]: C:\Program Files\iobroker\TG24QA\node_modules\iobroker.tradfri\build
	info	instance system.adapter.tradfri.0 started with pid 6816
	info	"system.adapter.tradfri.0" enabled

This is reproducible all the time also on a fresh installed instance with no other (non default) adapters. Uninstall does not solve the issue, following error is displayed in that case:
Error: Cannot find module 'core-util-is'
--
  | at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
  | at Function.Module._load (internal/modules/cjs/loader.js:562:25)
  | at Module.require (internal/modules/cjs/loader.js:692:17)
  | at require (internal/modules/cjs/helpers.js:25:18)
  | at Object.<anonymous> (C:\Program Files\iobroker\TG24QA\node_modules\verror\lib\verror.js:9:19)
  | at Module._compile (internal/modules/cjs/loader.js:778:30)
  | at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
  | at Module.load (internal/modules/cjs/loader.js:653:32)
  | at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
  | at Function.Module._load (internal/modules/cjs/loader.js:585:3)

Seems unlikely that this adapter is the root issue, since it does nothing special.
@Stabilostick any idea if this has to do with the Windows installer?

@Stabilostick any idea if this has to do with the Windows installer?

Yes. Seen this several times. npm starts suddenly to uninstall modules during installation of ioBroker.tradfri.

Do you know why? Is this something that might be fixed with the new installer?

Must be something with npm & package-lock or cache. New installer is going to address this.

Closing, since this is a general issue with the Windows installation


removed ws command since it was not in use and is not inbuild

Basically the new elysia version does not have ws, thats why I removed it.

2 additional updates, preparing for an additional example (swagger docs)


Issue Dtrabase and Phpmyadmin ( Windows Verison )

Windows Version:
MariaDB not working ( user root  pass: root )
MariaDB and Mysql very slow for access Phpmyadmin

Use PhpWebStudy to download and start Mariadb. The database folder will be initialized during the first startup. And initialize the user adn password as root root. If the first attempt fails to start successfully. Send out the log information

The problem of slow of phpMyAdmin. Copy config.sample.inc.php to config.inc.php and modify

$cfg['Servers'][$i]['host'] = 'localhost';

to
$cfg['Servers'][$i]['host'] = '<IP_ADDRESS>';

port: 3307
modify mariadb's config file. change port from 3307 to 3306. then restart mariadb

If you use a VPN, try turning off the VPN first. Some VPN Apps will handle domain names. This causes this problem
Is there this domain name in the system hosts file?

Is PWS hosts enabled?

Is there this domain name in the system hosts file?

Is Apache start success?  if start success. conf file should includes this block in the file begin

Is conf file has this? this load all PWS's site vhost file.

Have you commented out these two lines in site's vhost file?  This is required and cannot be commented.

There are many reasons why this problem occurs.  eg：

Add a .user.ini file to the project root directory

Set a wrong folder in the .user.ini file.

Restart php. then will get 'No input file specified.' issues

Site log has the error message

https://www.alibabacloud.com/help/en/ecs/support/what-do-i-do-if-the-no-input-file-specified-error-is-returned-when-i-access-websites-deployed-on-an-ecs-instance
So, these are all configuration issues. Everyone's situation is different. These are not things that PWS can solve. The most effective way is to look at each log. Then follow the prompts to solve the problem


Vague error of 422 Client Error: Unprocessable Entity

Describe the bug
I am getting a vague error when using HuggingFaceH4/zephyr-7b-alpha with the conversational task: 422 Client Error: Unprocessable Entity
It would be good to provide a more human-friendly error message, stating that the conversational task is unsupported.
Reproduction
from huggingface_hub import InferenceClient

client = InferenceClient(model="HuggingFaceH4/zephyr-7b-alpha")
output = client.conversational("Hi how are you?")

Logs
/Users/user/code/repo/venv/bin/python /Users/user/code/play/a.py
Traceback (most recent call last):
  File "/Users/user/code/repo/venv/lib/python3.11/site-packages/huggingface_hub/utils/_errors.py", line 261, in hf_raise_for_status
    response.raise_for_status()
  File "/Users/user/code/repo/venv/lib/python3.11/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 422 Client Error: Unprocessable Entity for url: https://api-inference.huggingface.co/models/HuggingFaceH4/zephyr-7b-alpha

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/user/code/play/quick_play_2.py", line 9, in <module>
    hi = client.conversational("Hi how are you?")
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/code/repo/venv/lib/python3.11/site-packages/huggingface_hub/inference/_client.py", line 388, in conversational
    response = self.post(json=payload, model=model, task="conversational")
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/code/repo/venv/lib/python3.11/site-packages/huggingface_hub/inference/_client.py", line 238, in post
    hf_raise_for_status(response)
  File "/Users/user/code/repo/venv/lib/python3.11/site-packages/huggingface_hub/utils/_errors.py", line 303, in hf_raise_for_status
    raise HfHubHTTPError(str(e), response=response) from e
huggingface_hub.utils._errors.HfHubHTTPError: 422 Client Error: Unprocessable Entity for url: https://api-inference.huggingface.co/models/HuggingFaceH4/zephyr-7b-alpha (Request ID: <redacted>)

System info
- huggingface_hub version: 0.17.3
- Platform: macOS-13.5.2-arm64-arm-64bit
- Python version: 3.11.5
- Running in iPython ?: No
- Running in notebook ?: No
- Running in Google Colab ?: No
- Token path ?: /Users/user/.cache/huggingface/token
- Has saved token ?: False
- Configured git credential helpers: osxkeychain
- FastAI: N/A
- Tensorflow: N/A
- Torch: 2.1.0
- Jinja2: 3.1.2
- Graphviz: N/A
- Pydot: N/A
- Pillow: N/A
- hf_transfer: N/A
- gradio: N/A
- tensorboard: N/A
- numpy: 1.26.1
- pydantic: 2.4.2
- aiohttp: 3.8.6
- ENDPOINT: https://huggingface.co
- HUGGINGFACE_HUB_CACHE: /Users/user/.cache/huggingface/hub
- HUGGINGFACE_ASSETS_CACHE: /Users/user/.cache/huggingface/assets
- HF_TOKEN_PATH: /Users/user/.cache/huggingface/token
- HF_HUB_OFFLINE: False
- HF_HUB_DISABLE_TELEMETRY: False
- HF_HUB_DISABLE_PROGRESS_BARS: None
- HF_HUB_DISABLE_SYMLINKS_WARNING: False
- HF_HUB_DISABLE_EXPERIMENTAL_WARNING: False
- HF_HUB_DISABLE_IMPLICIT_TOKEN: False
- HF_HUB_ENABLE_HF_TRANSFER: False

Yes, good idea to have better error messages. I opened https://github.com/huggingface/huggingface_hub/pull/1755 to add them. Thanks for suggesting it :)


Avoid Model 1, Model 3 etc

Hi,
When I describe a route with hapi-swagger with the route.config.plugins['hapi-swagger'].responses['200'] field set for example with :
{
  'description': 'test',
  'schema': Joi.object({a: Joi.string()}).label('a test')
}

like in the https://github.com/glennjones/hapi-swagger#status-codes example.
What i get for this response object (not the schema object but the one containing it) is an ugly "Model #" in definitions where # is a number that increment with the number of anonymous models.
I suspect that the object containing the description and schema is considered as anonymous and labeled by hapi-swagger.
The problem is that I can't label this object and that the code generators for clients refuse to generate it.
If I create a Joi.object around the response object the swagger validator is not happy either ...
Do you know a workaround?
Thank you!
Edit: i just tried with the hapi-swagger/bin/test-server and i have the same behaviour on GET /v1/store/

There are some problems with labels at the moment. One has already been identified by @dylancwood in #277. To be honest I am upset these issue where not picked up by my tests. Another area where more the tests are needed.
In some cases extending the labels to all the major objects helps. So below adding a label to both the array and its child object.
const usersModel = Joi.array().items(Joi.object({
   firstname: Joi.string().label('firstname'),
   lastname: Joi.string().label('lastname')
}).label('User')).label('Users');

I need a couple of full days to review this whole area, but the next clear slot I have is second/third week of July. Sorry but is will be a few weeks both I can look at this.

I took a look a look at the code and it seems it's looking up and caching $ref models in the definitions collection. Shouldn't it just be looking up the base definition and if it's there make a reference and return it without adding it to the collection?
For each model, in my "definitions" I have:
    "Foo" : { ... },
    "Model X": {
      "type": "object",
      "$ref": "#/definitions/Foo"
    }

I have rewritten the code for handling response objects in v7.0.0 It should limit the use of wrapping object in the JSON output.
If you could update to v7.0.0 and try it out.  You should label() all your objects. Could you also set the plugin option reuseDefinitions to false

Thanks Glenn. I updated and it fixed the "Model X" problem I was having (without setting  reuseDefinitions which is in the docs but not allowed in the code.)
It introduced a new little problem for me where it creates a new class for an empty Joi.object() I have. To make it worse, it thinks it's the same empty object in another field so it uses the wrong name.

I spoke too soon. It's also making new Models for arrays which is not good.

Hi,
is it possible to change the autogenerated label to avoid space ? An underscore or no-space at all would be much more code generator friendly.
Thanks a lots for this great plugin!

Hi!
I finally had time to check on that and it's working great!
Thank you so much :)
There is only one case left ... The label is not used when it's applied to an array of nested objects.
But If i remember well I saw somewhere that the definition lookup is done by iterating over the definitions and comparing them.
I guess the nested def is not accepted there?

Yes, that's correct, I think, and still open.
The label is not used when it's applied to an array of nested objects.
For example...
const SubSchema = Joi.object().keys({ ... })
  .label('SubObject'); // NOT WORKING

const SubListSchema = Joi.array().items(SubSchema)
  .label('SubObjects'); // works

const MainSchema = Joi.object().keys({
   ...
  subs: SubListSchema,
}).label('MainObject'); // works

const MainListSchema = Joi.array().items(MainSchema)
  .label('MainObjects'); // works

It would be fantastic if this could be fixed as well. Thanks. :-)

I checked this again, and as far as I can tell, everything is working fine.

I think this is resolved. Closing.


feat(autoware_lidar_centerpoint): added the cuda_blackboard to centerpoint

Description
This PR is part of a series of PRs that aim to accelerate the Sensing/Perception pipeline through an appropriate use of CUDA.
List of PRs:

https://github.com/autowarefoundation/autoware.universe/pull/9454 (pointcloud preprocessing)
https://github.com/autowarefoundation/autoware.universe/pull/9455 (concatenation)
https://github.com/autowarefoundation/autoware.universe/pull/9453 (centerpoint)
transfusion (TODO)
OGM (TODO)
https://github.com/tier4/aip_launcher/pull/348 (aip_launcher)

To use these branches, the following additions to the autoware.repos are necessary:
  vendor/cuda_blackboard:
    type: git
    url: git@github.com:knzo25/cuda_blackboard.git
    version: main
  vendor/negotiated:
    type: git
    url: https://github.com/osrf/negotiated.git
    version: master

Depending on your machine and how many nodes are in a container, the following branch may also be required:
https://github.com/knzo25/launch_ros/tree/fix/load_composable_node
There seems to be a but in ROS where if you send too many services at once some will be lost and ros_launch can not handle that.
Related links
Parent Issue:

Link

How was this PR tested?
The sensing/perception pipeline was tested until centerpoint for TIER IV's taxi using the logging simulator.
Notes for reviewers
The main branch that I used for development is feat/cuda_acceleration_and_transport_layer.
However, the changes were too big so I split the PRs. That being said, development, if any will still be on that branch (and then cherrypicked to the respective PRs), and the review changes will be cherrypicked into the development branch.
Interface changes
An additional topic is added to perform type negotiation:
Example: input/pointcloud -> input/pointcloud and input/pointcloud/cuda

Effects on system behavior
Enabling this preprocessing in the launchers should provide a much reduced latency and cpu usage (at the cost of a higher GPU usage)

@knzo25 Thank you for your great work :tada:
Do you have any documentation for the cuda_blackboard package? Just a simple API references and overall design in a readme would be helpful to review the PRs.

@kminoda
Yes, sorry. I am adding some results (processing time, memory consumption, cpu use), documentation, etc as of now, but wanted to open the PRs before to the the ball moving

@kminoda
Added the cuda_blackboard documentation in https://github.com/knzo25/cuda_blackboard.
As discussed internally, I will create an issue to manage and discuss about this series of PRs


Feature: [Color effect] Multiply

Multiply:
result = color * effect;

relate #50
ColorMode.None means ColorMode.Multiply.


No more args[]

The primary goal of this PR was to remove all uses of the args[string] pattern, where we treat args as this giant black boxed blob that we just pass around to any function that needs an argument.
Instead, this uses Python's keyword arguments features to allow the functions to require arguments.
# This function will require that it is called with the named
# parameters `a` and `b` explicitly set to something. It
# will error if you try to use them as positional args.
def function(*, a, b):
    pass

This PR also splits massage_args into three functions: get_students, get_assignments, and compute_stogit_url, each of which now has a single responsibility, instead of the previous
situation where massage_args had all three jobs.

Oh, come on. You worked locally.

Oh. Or I might have been running my tests on master, by accident.

Coverage increased (+0.9%) to 70.11% when pulling 9b04ac66bd31bc00a8c9ad0d594e17a041145e8f on no_more_args into e1cd098d6dcf637bb7f4a2b121784b306f4c25b0 on master.


Version 0.22.1 will not build :-(

Hi,
When I add this version and run a build command I get an error in:
github.com-1ecc6299db9ec823\positioned-io-0.3.1\src\raf.rs:78:29
The error is:
78 |         let pos = file.seek(SeekFrom::Current(0))?;
|                             ^^^^^^^^ use of undeclared type SeekFrom
Is there some other configuration required?

For me the following commands work:
$ cd /tmp
$ mkdir merkle                                                                                $ cd merkle
$ cargo init
$ cargo add merkletree
$ cargo build

Could you please provide the commands you ran and I'll have a look.

You can also take a look at our CI showing successful builds: https://app.circleci.com/pipelines/github/filecoin-project/merkletree?branch=master

I close this issue as not reproducible.


Passive Data Sample doesn't work

Hello guys, I faced the issue when the sample app displays 0 heart rate.
I think PassiveDataService doesn't catch HEART_RATE_BPM, so I modified code and added passiveListenerCallback, but even there I don't receive heart rate. But when I replaced HEART_RATE_BPM with STEPS_DAILY, there weren't problems with receiving steps though.
I don't think the issue in my watch, because in Google Fit app I can see my heart rate (min, max, etc.). But for your information it's Fossil Gen 6 (Wear OS 3).
Any thoughts what's wrong? Any help would be helpful, thank you!

With some devices, it may take several minutes for a value to be returned and displayed. About how long did you wait for the sample to return a heart rate value after toggling "Enable"?

@breanatate I think 2 days, with short breaks to apply changes, so it wasn't full 2 days of work for the app

@ZhEgor Are you wearing the device when testing? Some data types are only returned when device is on a wrist (there's some separate "on body" detection hardware). Interesting that Fit works though. Does Samsung's Heart rate tile show the heart rate?

Sorry--obviously not Samsung! Is there an equivalent Fossil app (not Fit)?

@ithinkihaveacat oh cool, I tried again and now it works 😵💫, don't know why this time it worked but I'm fine with that 😅. I think an issue is clossed. Thank you guys for your help.
Just in case anyone is facing the same problem: I removed the sensor permission for the Wellness app (default Fossil app) and reinstalled this app, don't know how it helped, but it did, matter of fact I had already reinstalled the app before, but it did nothing. Maybe there were some special circumstances...

@ZhEgor Great, thanks for the update!


Plan TIKI SDK Android to TIKI Trail 3.0

Update TIKI SDK Android to use the same APIs defined in TIKI Trail 3.0 and the Platform Channels APIs defined in https://github.com/tiki/tiki-sdk-platform-channel/issues/18
This issue is to go through all the necessary updates and create the required GH issues for updating.
Refer to https://github.com/tiki/tiki-trail/pull/318 for the latest version

done in #178


fix: don't overwrite global jQuery

The this.$ = jQuery... stuff caused window.$ to be overwritten in Violentmonkey Beta <IP_ADDRESS> and above. Closes #440 (at least as far as I can fix it).
If any other script is doing this.$ = ... (which I'm not sure why I was doing it, I guess I copied it from somewhere else), ECAU will still break, but we can't do much about that except for asking others to change this too when we find the conflicts.
I was going to drop jQuery altogether but at this point it's been so long since I've looked at these scripts that I might break too many things if I try, so I'll postpone that until an "eventual" TS rewrite.

Hmm. Didn't test it with GM but I don't see any reason why these changes would break compatibility with GM (if such compatibility even existed in the first place). There should still be a script-local version of jQuery available through the global const.
I guess the reason why a separate jQuery was necessary for GM was the whole page context vs content context that we needed to fix for ECAU (getFromPageContext and cloneIntoPageContext).

Since I haven't tested with VM Beta: Is this PR not going the fix the issue at all or not unless all the other userscripts are also fixed? If there are only scripts in murdos repo which also have to be fixed in the same way, we could simply do that (I even have write access there). Otherwise I would prefer to ask for option two, yet another jQuery hack should be our last resort 😅


appending data to table deletes labels

Environment details

OS: MacOS
Node.js version: 10
npm version: 6.9
@google-cloud/bigquery version: 4.7

Steps to reproduce
Appending data to an existing table with a label, will delete label.

Add label to table in BigQuery web UI
Append data to table using:

const bigquery = new BigQuery();

const metadata = {
      sourceFormat: "NEWLINE_DELIMITED_JSON",
      autodetect: true,
      writeDisposition: "WRITE_APPEND",
};
const [job] = await bigquery
      .dataset("dataset")
      .table("tablename")
      .load("example.json", metadata);

@maxwell8888  I tried with above given steps and mentioned version, but I could not reproduce it.

I wasn't able to reproduce this either using 4.7 or the latest release. I'm going to close for now, but if the issue still exists, please provide further instruction on how we can more accurately represent your environment in which you're seeing the failure.


Update builder base image to latest

Issue #, if available:
The PR for base image update from PR bot seems to be raised before we added the new release branch support for 1-30. So the pre-submits for 1-30 have been failing on that PR. This change manually updates the builder base image tag to latest and updates the corresponding prow jobs.
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve


Q: feature select

After filtering out the natural resource related peace agreements, how to select the feature that border related?

According to the "PA-X" codebook, Find the state definition, and choose the StBor and StXbor to analyze, because only both of them related to the border.

And should do some test to select which one of them or both of them to analyze.

Yeah, finding the related column is definitely a good way, and maybe you should more into the geographic location.

Yeah, finding the related column is definitely a good way, and maybe you should look more into the geographic location.

Yeah, finding the related column is definitely a good way, and maybe you should look more into the geographic location.


refactor: share environment idependent specs

Currently there are many duplicated specs for protractor and testbed environment.
Most are equal, some are missplaced, some are slightly different.
Sharing those tests ensures the same tests exists as unit tests and as e2e tests.
Further it reduces code duplication.
Prerequisite #19709 (will need to test equal behavior)

Thanks for reviewing, labeling and approving. What's the next step?

It should be merged this week


error TS2688: Cannot find type definition file for 'mime'.

I keep getting this error on "npm run build"

Node version : 16

How can I resolve this conflict and ensure I have the correct type definitions for the versions of 'mime' being used?
Is there a specific way to manage multiple versions of 'mime' and their type definitions?

Not sure what happened but it looks like mime's type definitions were deprecated through 4.0.0
In case it can help, I ended up using package.json resolution as a workaround.
"resolutions": {
    "@types/mime": "^3 || ^1"
},

Just ran into this at work and remembered seeing this issue.
It appears that<EMAIL_ADDRESS>is deprecated now. I dont know why yet, the message on NPM says that mime ships it's own types now.
I'll keep this open for now bc folks will likely come looking, but there isn't anything we can do over here, it's an upstream issue.

This should be resolved with https://github.com/DefinitelyTyped/DefinitelyTyped/pull/69231
Closing, let me know if something goes awry.


Optimize LbWeight normalization

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hzxuzhonghu
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [hzxuzhonghu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
7be507ef815180b5710913ab1b7f904ca32fdeab
link
/test e2e-mixer-no_auth

prow/e2e-mixer-no_auth-mcp.sh
7be507ef815180b5710913ab1b7f904ca32fdeab
link
/test e2e-mixer-no_auth-mcp

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

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hzxuzhonghu, ymesika
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [hzxuzhonghu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Much better

/test e2e-mixer-no_auth


Test against PHP 7.4 through legacy PHP 5.4

Updated to fix all build errors, this is now ready for review :shipit:


BR: Packet to local AS through remote AS

Fixes #1928

This change is

Final agreement is to drop packets when we can detect such paths, see #1937.


Allow Mixins

I'm getting the error below and assume it is expected. I kind of need to use mixins. Can we put as feature request?
[SEVERE] floor_generator:floor_generator on lib/db/database.dart:
Entities and views are not allowed to inherit from mixins.

Hi! What's your use case for mixins in database entities?

I have entities that inherit from another generic class. The generic class allows me to access common fields across the board such as name & id. A few (a subset) of these entities share common fields that I would like to be able access in a sound manner (ensuring code linkage) in the same way I access the generic class. If I don't use mixins, I have no option but to get the fields by string, which can eventually break the code.
Example
class Animal{int getAge()}
class Dog extends Animal{}
class Cat extends Animal{}
class Bird extends Animal{}
I can:
print(Animal().getAge())
I cannot:
print(FlyingAnimal().getFlyingTime())
I believe I could use multiple levels of inheritance but haven't tried yet and not sure what is the rational to prevent the use of mixins as it would make more sense in my case to inject the methods I need. Another option is to add getters to a new generic Dao, but seems very entity/instance related to me.

I also used mixin in entity to apply EquatableMixin of equatable package. I know I can extends from Equatable class, but the use of EquatableMixin leaves the freedom to inherit from other classes.
It would be helpful if these limitations were stated in doc. I did not imagine that the application of a mixin, without fields, was not allowed.

I also used mixin in entity to apply

I also want to use Equatable library in my project just to not having to override == operator, hashCode and toString.


build on openjdk8

Problem: Travis build validation doesn't work anymore because oracleJDK8 isn't supported anymore
Solution: Migrate to openjdk8
Effect: Working PR validation

Codecov Report

Merging #288 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #288   +/-   ##
========================================
  Coverage    71.65%   71.65%
========================================
  Files           50       50
  Lines         1397     1397
  Branches        50       31   -19
========================================
  Hits          1001     1001
  Misses         396      396

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 f868ba1...d0bbbf5. Read the comment docs.

Thank you!


Multi wasmi

This is a preliminary PR that brings wasmi 0.34 into soroban for protocol 22 and also enables "multi-wasmi" execution -- running older contracts on 0.31 and newer ones on 0.34. There are two reasons for this:

The new wasmi has a completely different execution engine, so even the exact same wasm code run on 0.34 with the exact same cost model as we ran a contract on 0.31 will not always cost the same, and in particular will not run out of gas at the exact same points. So we have to run old contracts on old wasmi and new ones on new wasmi. Hopefully in the future this won't happen a lot more times -- it will depend to some extent on how often wasmi changes their internal representation. I've talked to @robbepop about trying to work on a stable gas-consumption interface at least, but wasmi's not there yet.
The type structure / API surface of wasmi changed a bit, enough that we need a bunch of switching shims in between the two even if they had exactly the same execution engine. But they don't anyways.

The good news is that this enables two significant sources of performance improvement:

The new register machine runs straight-line wasm code something like 2x faster than the old stack machine on computationally intensive benchmarks (eg. coremark)
The new engine supports lazy compilation which means VM instantiation only does a quick pre-parse of the module and then parses/validates/translates code on demand as functions are called. This is ideal for smart contracts since usually each transaction only calls a fraction of the code in a module, so we should see fairly dramatic improvements in contract startup overhead from this.

I don't have concrete numbers on realistic contracts yet unfortunately, and there's probably lots of tidying to do here, I haven't even reviewed the unified diff yet to look for FIXMEs, but I at least have the testsuite passing now locally (it'll probably break somehow in CI) so I figured I'd post this as progress.

I have not (yet) looked into the changes in detail though I looked into the changes done to Wasmi v0.34.0:
https://github.com/stellar/wasmi/commit/c5b7c4315db549b01755a387fb142a12fcbe1148
Particularly there are changes to the Wasmi fuel API to provide total fuel which probably was done to mirror the behavior of the old Wasmi. I think it would be better to do it conversely and instead host the total amount on the host side if possible. The reason is that the Wasmi v0.34.0 fuel API likely won't change in the future and it is way simpler than the old fuel API. Hosting the total fuel on the host side would maybe imply minor changes to the old Wasmi version interopt but would get rid of this particular change to all future Wasmi versions.
Furthermore there might be room for even more optimizations:
Lazy + Unchecked Compilation
At Parity where Wasmi was originally used the smart contracts life cycle is divided into three stages.

upload_code: Uploads the smart contract code onto the chain. Here validation and compilation is performed fully and eagerly.
instantiate: Here a previously uploaded code is going to be instantiated to make it possible to interopt with the resulting smart contracts. This sets up initial state by calling the deploy function of a smart contract.
execute: This executes a previously instantiated smart contract with some parameters and returns the result of the execution.

For stages 2. and 3. it is possible to rely on the fact that stage 1. already fully validated and compiled the smart contract and thus can use lazy compilation combined with unchecked compilation thus skipping validation entirely and only lazily compile the contract. Lazy unchecked compilation is roughly twice as fast as lazy checked compilation.
Linker Builder
As demonstrated in the blog post linked by @graydon the LinkerBuilder was introduced to improve setup time of host functions by a huge amount. With 50 host functions we saw 120x improvement. If it is possible to setup a LinkerBuilder once and re-use it for stage 2. and 3. above it will get rid of most of the overhead associated to those stages for setup. Maybe soroban already solves this problem in another way though of which I am unaware.
Version 0.35.0
This update further optimizes Wasmi module creation and in particular for lazy compilation scenarios. The speed-up is due to decreased locking calls (Mutex/RwLock) for the Wasm function section and improved data structures, e.g. getting rid of a whole BTreeMap during module creation. Also v0.35.0 fixes the long-standing dead-lock with module creation in host functions. In local benchmarks I saw improvements of up to 23% in lazy+checked benchmarks.
Stable Fuel Metering
I have not (yet) started working on stable fuel metering for Wasmi though I have had the idea that it should be possible to have a (somewhat) stable fuel metering if fuel metering was based on Wasm instructions instead of Wasmi instructions. While this very likely yields higher fuel costs because we must no longer depend on optimizations performed by Wasmi it would be independent of Wasmi internals. At least that's the idea. The even better idea though is to make this a Wasm standard across Wasm engines. There seems to be quite some people who are very interested in getting this into multiple Wasm engines so that fuel metering could even be stable across Wasm engines in an ideal world.

FYI: In case the Linker is too inefficient for the purposes of Soroban and the LinkerBuilder cannot be used, I just released Wasmi v0.36.0 with the new Instance::new API similar to the one found in Wasmtime.
This is rather low-level compared to using the Wasmi Linker, but also has the potential advantage of not having to use the Linker and instead take driving the import resolution process into the users hands if needed.

we're not going to pursue this direction. went with https://github.com/stellar/rs-soroban-env/pull/1442 instead. closing.


chore: update fluvio to v0.10.13

Updates to Fluvio v0.10.13 and automatically use version logger

bors r+

Closing given that its outdated/stale


Global Averaging Map Size in Inception_ResNet_v2

In the implementation of inception_resnet_v2, the penultimate layer is a global average layer.
 x = AveragePooling2D((7,7))(x)

Why the pooling size window is not (8,8) as inception_resnet_v1?

That was a mistake. Corrected in the last commit.
On Jul 21, 2016 13:10, "Pai Peng"<EMAIL_ADDRESS>wrote:

In the implementation of inception_resnet_v2, the penultimate layer is a
global average layer.
x = AveragePooling2D((7,7))(x)
Why the pooling size window is not (8,8) as inception_resnet_v1?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/titu1994/Inception-v4/issues/1, or mute the thread
https://github.com/notifications/unsubscribe-auth/AC6EmgWiqXz_Kp34W44MXftWeZGpmD1Wks5qXyJvgaJpZM4JRhpL
.


[SPARK-32314][SHS] Add config to control whether log old format of stacktrace

What changes were proposed in this pull request?
Avoid writing old format of stacktrace to event log to save space
Why are the changes needed?
Old format stacktrace info is duplicated and cause huge event log
Does this PR introduce any user-facing change?
No
How was this patch tested?
Manually tested.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@sarutak @gengliangwang could you help take a look?

@HeartSaVioR Could you help take a look?

It might be only me, but even we are trying to guarantee backward/forward compatibility with event logs, I wouldn't think it's for covering two major versions, even not latest one for 1.x.
IMHO the config is not needed and we can just remove the compatibility, but again that's only me, and it'd be nice to initiate discussion thread in dev@ list to reach consensus though. Could you go through the dev@ mailing list? I guess the discussion thread won't hold too long, as it might be just obvious.

@warrenzhu25
Thank you for the contribution but I don't think the compatibility for 1.2.0 and before is needed too. Considering our versioning policy, it's too old to support.
http://spark.apache.org/versioning-policy.html

@warrenzhu25
Thank you for the contribution but I don't think the compatibility for 1.2.0 and before is needed too. Considering our versioning policy, it's too old to support.
http://spark.apache.org/versioning-policy.html

Do you mean I can just remove the config?

@sarutak @gengliangwang I removed the config directly. Could you help take a look again?

I agree with @HeartSaVioR - compatibility with 1.2.0 is not required.

Briefly looking at spark code, this is currently still in use - looks like that comment in TaskEndReason might not be valid anymore.
See here for example.
There are other uses as well, given that I am not in favor of this change. If it had been a truely dead code, I would have been more inclined to cleanup (with a caveat that this is part of public api, and so we need to be careful with breaking behavior).

Briefly looking at spark code, this is currently still in use - looks like that comment in TaskEndReason might not be valid anymore.
See here for example.
There are other uses as well, given that I am not in favor of this change. If it had been a truely dead code, I would have been more inclined to cleanup (with a caveat that this is part of public api, and so we need to be careful with breaking behavior).

Thanks for comment. For this example, it's about how to create ExceptionFailure. This pr is only about when writing into event log, also affecting TaskEndReason after replay event. And there is no api directly use stackTrace: Array[StackTraceElement], this only used in below:
  override def toErrorString: String =
    if (fullStackTrace == null) {
      // fullStackTrace is added in 1.2.0
      // If fullStackTrace is null, use the old error string for backward compatibility
      exceptionString(className, description, stackTrace)
    } else {
      fullStackTrace
    }

To clarify what I meant:

ExceptionFailure is a public api.
History server is not the only consumer of event files.
There are code paths which are populating stackTrace in ExceptionFailure

Given all of these, setting stack trace to empty is backwardly incompatible against current spark versions, and breaks compatibility.
I would have been in favour of the change if (3) above was not the case.
Given all of these three conditions currently applying, this is a breaking change and I am not in favor of it.

To clarify what I meant:

ExceptionFailure is a public api.
History server is not the only consumer of event files.
There are code paths which are populating stackTrace in ExceptionFailure

Given all of these, setting stack trace to empty is backwardly incompatible against current spark versions, and breaks compatibility.
I would have been in favour of the change if (3) above was not the case.
Given all of these three conditions currently applying, this is a breaking change and I am not in favor of it.

Could you show me one example code path which is populating stackTrace in ExceptionFailure?


the crash handler doesnt compile

i have installed all the libraries but still
the crash handler doesnt compile
could you please help me?

Duplicate of #32.


Backslashes in Target.Arguments are vanished on exit

Repro

Create target, in the Arguments field put something with backslashes. For example D:\glTF-Sample-Assets\Models\Sponza\glTF\Sponza.gltf. You can run the target just fine, application receives correct arguments.
Close and open RAD Debugger again
All backslashes disappear. (example turns into D:glTF-Sample-AssetsModelsSponzaglTFSponza.gltf).

By the way, great debugger. Wish one day I'll be able to debug on all the platforms without using clunky VS.

This was fixed in d560f8c734ba87fd1ea79e2dd5fefb6e3031fe00, and will be in the next release.


add 1-5, 1-6, 3-4, 4-1, 4-2

add a way of addressing checkers that require multiple calls of the llm.
add utility.py to refactor some of the calls including count_words and word_reverse_text
add 1-5, 1-6, 3-4, 4-1, 4-2 (I evaluated on ChatGPT Chinese)
add output texts from the LLM for 1-5, 3-4, and 4-1 if the answer is not correct to make the explanation more useful (since they require the second call of the LLM and the user was not able to see the response of the second call).

Greatly appreciate the contributors who initiated this repository! The riddles provided are both enjoyable and educational, and deserving of wider dissemination. I've added a few more problems to complement the list. Please don't hesitate to reach out if you have any questions.

@TianyiPeng
Thank you for your contribution.
However, there is currently an issue—when LLM is called multiple times in a question, each return result of LLM is not displayed in the LLM answer (although in some questions, it appears in the explanation). Some necessary modifications are needed regarding this.

@TianyiPeng
Thank you for your contribution.
However, there is currently an issue—when LLM is called multiple times in a question, each return result of LLM is not displayed in the LLM answer (although in some questions, it appears in the explanation). Some necessary modifications are needed regarding this.

@HansBug, totally makes sense! I realized this and took the hack by showing them in the explanation part. The following is a picture of this. I personally found the hack acceptable and pushed it to meet the urgency of making the list complete (I do find it a bit annoying while I shared the link with friends and they found the problem set was not complete yet).

Here is a temporary link you can play with: https://22ad06b8cbe44cfb6e.gradio.live/. Any feedback is welcome! If a change of interface is needed, I am also happy to work on that (but it may take a bit longer time).
Best!


Add support to Prometheus

Now we can provide a port (for example, in /etc/overlaybd-snapshotter/config.json, we set monitorPort: 9099) for prometheus to monitor some metrics like GRPC APIs latency or error count.
(from https://github.com/containerd/accelerated-container-image/issues/140)
Signed-off-by: Haoqi Miao<EMAIL_ADDRESS>

@HileQAQ  remove this binary? cmd/overlaybd-snapshotter/overlaybd-snapshotter


Read / write operation failed in HomeKit scripts after several minutes

Analysis
When checking occupancy for these sensors in HomeKit scripts and iOS shortcuts, I get a Read/Write operation failed error after the child bridge has been running for a few to several minutes. Upon restarting the child bridge, everything works again for a few minutes.
I see this error in the plugin logs; not sure if it’s relevant, but it seems worth noting:
(node:14447) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 packets listeners added to [EventEmitter].
I have 14 Airport Expresses plus two Homebridge Minis, in case the plugin assumes a smaller number of devices.
Thank you for any advice/suggestions on resolving this.
Expected Behavior
HomeKit scripts and iOS shortcuts should get occupancy value from plugin accessory without an error being generated.
Steps To Reproduce
Install plugin. Allow it to run for a few to several minutes. Check occupancy status of one of the plugin accessories via HomeKit automation script or iOS shortcut.
Logs
(node:14447) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 packets listeners added to [EventEmitter].

Configuration
{
            "name": "Airport Express Connected",
            "update": {
                "refreshRate": 3,
                "ignoreGroupWithLeadingDevice": true,
                "unreachable": {
                    "ignore": false,
                    "threshold": 30,
                    "reportDisconnected": true
                }
            },
            "discovery": {
                "enabled": true,
                "always": false,
                "intervals": 30,
                "whitelist": {
                    "list": [],
                    "enabled": false
                },
                "blacklist": {
                    "list": [],
                    "enabled": false
                },
                "discardKnownDevices": false
            },
            "_bridge": {
                "username": "xx:xx:xx:xx:xx:xx",
                "port": 44803
            },
            "platform": "AirportExpressConnected"
        },

Environment

OS: unraid 6.12.8 server
Docker: 24.0.9
Homebridge: 1.7.0 UI 4.55.1
Airport Express Connected: 1.3.0 (have also tried latest beta and 2 earlier versions)
Node: 20.11.1
npm: 10.4.0

Additional Context
No response

Yeah, this is an issue with the current architecture that occurs when using the plugin with a lot of AirPort Expresses.
I am planning to fix that issue eventually. I will update you here. Currently, I cannot give you a timeframe.

Thank you. I’ll sit tight for now.


SRIOV - syncVMI try to plug an SRIOV interface that is not in the pod

What this PR does / why we need it:
Avoid SyncVMI errors in case it is known in advance the SRIOV plug will fail.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note:

NONE

/test pull-kubevirt-build
/test pull-kubevirt-build-arm64
/test pull-kubevirt-generate
/test pull-kubevirt-manifests
/test pull-kubevirt-unit-test
/test pull-kubevirt-e2e-k8s-1.27-sig-network
/test pull-kubevirt-e2e-kind-1.27-sriov

/test pull-kubevirt-build
/test pull-kubevirt-build-arm64
/test pull-kubevirt-generate
/test pull-kubevirt-manifests
/test pull-kubevirt-unit-test
/test pull-kubevirt-e2e-k8s-1.27-sig-network
/test pull-kubevirt-e2e-kind-1.27-sriov

@AlonaKaplan in what scenario it is known in advance that SRIOV hotplug will fail and result in sync error?

/approve
Raising two lgtms to approve

/cherry-pick release-1.1


copying and pasting code from wiki results in two onloads

https://github.com/mapzen/electron-quick-start/wiki/How-to-Electron-Workshop#lets-add-a-map
The template and this step results in there being town onloads, so the map does not display. Just needs a few text tweaks to give the context of where to paste the code without ending up with duplication.
https://github.com/mapzen/electron-quick-start/blob/master/index_renderer.js#L4

Add a global map variable just above the page loading handler function and a call to initMap() inside the loading handler.

const api_key = 'mapzen-xxxxxxx';
let map; // <--- global map variable

// handle window loading event
document.getElementById('body').onload = function () {
  console.log('good news: index window is loading!');

  initMap(); // <--- initialize your map
};

PS - this was great! Thanks, @dianashk!


docs 02 : domain model diagram thingy

also actual domain model diagram thingy

Originally posted by @corbeau217 in https://github.com/corbeau217/cpp_opengl_vehicles/issues/16#issuecomment-2171092575
what? this?

also actual domain model diagram thingy

Originally posted by @corbeau217 in #16 (comment)
what? this?

ye bc cardinality

also actual domain model diagram thingy

Originally posted by @corbeau217 in #16 (comment)
what? this?

ye bc cardinality

also builds into docs 03 for the class diagram for the actual maker

we kinda got a lazy one


EXCEPTION CAUGHT BY FOUNDATION LIBRARY

Steps to Reproduce

Execute flutter run on the code sample.
Click ExpansionTile and scroll the CupertinoPicker.
Click ExpansionTile again to close CupertinoPicker.
Click ExpansionTile to open CupertinoPicker again and scroll it.

Expected results:
Nothing error to show.
Actual results:
EXCEPTION CAUGHT BY FOUNDATION LIBRARY（See Logs）.

Code sample
import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

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

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

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(),
    );
  }
}

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

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _selectedFruit = 0;

  final List<String> _fruitNames = <String>[
    'Apple',
    'Mango',
    'Banana',
    'Orange',
    'Pineapple',
    'Strawberry',
  ];

  @override
  Widget build(BuildContext context) {
    return Scaffold(body: Center(
      child: ExpansionTile(
          title: Text('Your choice is ${_fruitNames[_selectedFruit]}'),
          children: [
            SizedBox(
              height: 130,
              child: CupertinoPicker(
                scrollController:
                FixedExtentScrollController(initialItem: _selectedFruit),
                squeeze: 1.2,
                useMagnifier: true,
                magnification: 1.3,
                itemExtent: 32,
                onSelectedItemChanged: (int selectedItem) {
                  setState(() {
                    _selectedFruit = selectedItem;
                  });
                },
                children: List<Widget>.generate(
                  _fruitNames.length,
                      (int index) {
                    return Center(
                      child: Text(
                        _fruitNames[index],
                      ),
                    );
                  },
                ),
              ),
            )
          ]),
    ),);
  }
}

Logs

           ══╡ EXCEPTION CAUGHT BY FOUNDATION LIBRARY ╞════════════════════════════════════════════════════════
           The following assertion was thrown while dispatching notifications for FixedExtentScrollController:
           'package:flutter/src/rendering/object.dart': Failed assertion: line 3093 pos 12: '!_debugDisposed':
           is not true.

           Either the assertion indicates an error in the framework itself, or we should provide substantially
           more information in this error message to help you determine and fix the underlying cause.
           In either case, please report this assertion by filing a bug on GitHub:
             https://github.com/flutter/flutter/issues/new?template=2_bug.md

           When the exception was thrown, this was the stack:
           #2      RenderObject.markNeedsSemanticsUpdate (package:flutter/src/rendering/object.dart:3093:12)
           #3      _RenderCupertinoPickerSemantics._handleScrollUpdate (package:flutter/src/cupertino/picker.dart:479:5)
           #4      ChangeNotifier.notifyListeners (package:flutter/src/foundation/change_notifier.dart:351:24)
           #5      ChangeNotifier.notifyListeners (package:flutter/src/foundation/change_notifier.dart:351:24)
           #6      ScrollPosition.notifyListeners (package:flutter/src/widgets/scroll_position.dart:985:11)
           #7      ScrollPosition.setPixels (package:flutter/src/widgets/scroll_position.dart:281:9)
           #8      ScrollPositionWithSingleContext.setPixels (package:flutter/src/widgets/scroll_position_with_single_context.dart:78:18)
           #9      ScrollPositionWithSingleContext.applyUserOffset (package:flutter/src/widgets/scroll_position_with_single_context.dart:122:5)
           #10     ScrollDragController.update (package:flutter/src/widgets/scroll_activity.dart:386:14)
           #11     ScrollableState._handleDragUpdate (package:flutter/src/widgets/scrollable.dart:671:12)
           #12     DragGestureRecognizer._checkUpdate.<anonymous closure> (package:flutter/src/gestures/monodrag.dart:483:55)
           #13     GestureRecognizer.invokeCallback (package:flutter/src/gestures/recognizer.dart:253:24)
           #14     DragGestureRecognizer._checkUpdate (package:flutter/src/gestures/monodrag.dart:483:7)
           #15     DragGestureRecognizer.handleEvent (package:flutter/src/gestures/monodrag.dart:330:9)
           #16     PointerRouter._dispatch (package:flutter/src/gestures/pointer_router.dart:98:12)
           #17     PointerRouter._dispatchEventToRoutes.<anonymous closure> (package:flutter/src/gestures/pointer_router.dart:143:9)
           #18     _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:617:13)
           #19     PointerRouter._dispatchEventToRoutes (package:flutter/src/gestures/pointer_router.dart:141:18)
           #20     PointerRouter.route (package:flutter/src/gestures/pointer_router.dart:127:7)
           #21     GestureBinding.handleEvent (package:flutter/src/gestures/binding.dart:460:19)
           #22     GestureBinding.dispatchEvent (package:flutter/src/gestures/binding.dart:440:22)
           #23     RendererBinding.dispatchEvent (package:flutter/src/rendering/binding.dart:337:11)
           #24     GestureBinding._handlePointerEventImmediately (package:flutter/src/gestures/binding.dart:395:7)
           #25     GestureBinding.handlePointerEvent (package:flutter/src/gestures/binding.dart:357:5)
           #26     GestureBinding._flushPointerEventQueue (package:flutter/src/gestures/binding.dart:314:7)
           #27     GestureBinding._handlePointerDataPacket (package:flutter/src/gestures/binding.dart:295:7)
           #28     _invoke1 (dart:ui/hooks.dart:167:13)
           #29     PlatformDispatcher._dispatchPointerDataPacket (dart:ui/platform_dispatcher.dart:341:7)
           #30     _dispatchPointerDataPacket (dart:ui/hooks.dart:94:31)
           (elided 2 frames from class _AssertionError)

           The FixedExtentScrollController sending notification was:
             FixedExtentScrollController#37891(one client, offset 19.2)
           ════════════════════════════════════════════════════════════════════════════════════════════════════

Analyzing untitled...
No issues found! (ran in 1.5s)

[✓] Flutter (Channel stable, 3.3.4, on macOS 12.6 21G115 darwin-arm, locale
    zh-Hant-TW)
    • Flutter version 3.3.4 on channel stable at /Library/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision eb6d86ee27 (6 days ago), 2022-10-04 22:31:45 -0700
    • Engine revision c08d7d5efc
    • Dart version 2.18.2
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/chien/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • ANDROID_SDK_ROOT = /Users/chien/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

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

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

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

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

[✓] Connected device (4 available)
    • SM A5360 (mobile)           • R5CT8024XET   • android-arm64  • Android 12
      (API 31)
    • sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64  • Android 13
      (API 33) (emulator)
    • macOS (desktop)             • macos         • darwin-arm64   • macOS 12.6
      21G115 darwin-arm
    • Chrome (web)                • chrome        • web-javascript • Google
      Chrome 105.0.5195.125

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

@a1573595 This issue is reproducible on the stable channel. But it seems to have been fixed on the latest master channel. Please see the demo.

Demo
https://user-images.githubusercontent.com/104349824/195062693-1cf1b58b-6cde-4e35-b07b-ed109a8aeb34.mov

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.3.4, on macOS 12.6 21G115 darwin-x64, locale en-VN)
    • Flutter version 3.3.4 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision eb6d86ee27 (23 hours ago), 2022-10-04 22:31:45 -0700
    • Engine revision c08d7d5efc
    • Dart version 2.18.2
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

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

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

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

[✓] IntelliJ IDEA Community Edition (version 2022.2.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 70.0.5
    • Dart plugin version 222.4167.21

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

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

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 12.6 21G115 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 105.0.5195.125

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 3.5.0-6.0.pre.4, on macOS 12.6 21G115 darwin-x64, locale en-VN)
    • Flutter version 3.5.0-6.0.pre.4 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6e5f95bc3c (15 minutes ago), 2022-10-10 22:57:32 -0400
    • Engine revision 593ae56f04
    • Dart version 2.19.0 (build 2.19.0-298.0.dev)
    • DevTools version 2.18.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

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

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

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

[✓] IntelliJ IDEA Community Edition (version 2022.2.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 70.0.5
    • Dart plugin version 222.4167.21

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

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

[✓] Connected device (4 available)
    • Pixel 3a (mobile)      • 964AY0WL20                           • android-arm64  • Android 12 (API 32)
    • iPhone 14 Pro (mobile) • 7CB497D7-2159-4F84-BDBE-D79330FA1E48 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-0 (simulator)
    • macOS (desktop)        • macos                                • darwin-x64     • macOS 12.6 21G115 darwin-x64
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 106.0.5249.103

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Please try running app again on the latest master channel and confirm if this issue is fixed.

@a1573595 This issue is reproducible on the stable channel. But it seems to have been fixed on the latest master channel. Please see the demo.
Demo
flutter doctor -v (stable and master)
Please try running app again on the latest master channel and confirm if this issue is fixed.

Thanks, I will try it later.

it works well on the master channel, thanks for your help.


Consider bower publishing

Maybe?

Untile someone wants it, I’m closing it.

+1 for Bower

Really? :o

Yes please. I primarily use bower with Codekit.

Yep!

Alright, alright. :)

Thank you!

Done.

Yay!

Many thanks again!


fix sort

since the logic depeneds on the values being sorted correctly (arrayA[ai] < arrayB[bi]) and .sort is not stable and even gives a wrong result according to decimal computation( [14,2].sort() = [14,2], so we must at least give the compareFunction for simple cases

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


feat: add methods to Dask backend

Since #272  we have really minimal support for Dask DataFrame
Expr methods should go in narwhals/_dask/expr.py. For tests, you should use existing tests, and just remove the
    if "dask" in str(constructor):
        request.applymarker(pytest.mark.xfail)

part. If you can remove that, and the test passes, it means you've done it correctly
Not too hard
Examples of Expr methods which we should add (see here for the full list):

Expr.__sub__
Expr.__mul__
Expr.shift
Expr.cum_sum
Expr.is_between

Note: we should not add anything which modifies the index. So, the following should not be added, even though they appear on the list in the link above:

Expr.sort
Expr.head
Expr.tail

Harder

DataFrame.group_by
DataFrame.filter
get things started with namespaces (e.g. Expr.dt, Expr.str, ...)

General guidelines:

please don't ask for the issue to be assigned to you
please don't ask for permission to work on this issue
if you're  a first time contribute, please choose 1 method at a time to implement, and leave a comment noting which method you're working on (if you've contributed to Narwhals before, feel free to choose multiple)
have fun 🥳

Example pull request: https://github.com/narwhals-dev/narwhals/pull/731/files
contributing guide: https://github.com/narwhals-dev/narwhals/blob/main/CONTRIBUTING.md

An easy way to check if something still needs doing is to look for tests with
    if "dask" in str(constructor):
        request.applymarker(pytest.mark.xfail)

Then:

try removing those two lines
run the test, check that it fails
implement this functionality for Dask
check the test passes

I'll take Expr.sub

I'll take Expr.is_between

Taking Expr.__mul__

Take Expr.sum

@MarcoGorelli I have a couple of questions:

Could you expand a little bit more, here or somewhere else on the following:

we should not add anything which modifies the index

Should we refer to this issue also for dataframe methods? i.e. not Expr only?

hey!
in pandas, some Series methods such as Series.sort_values change the index:
In [3]: s
Out[3]:
0    3
1    2
2    1
dtype: int64

In [4]: s.sort_values()
Out[4]:
2    1
1    2
0    3
dtype: int64

pandas / Dask would then auto-align on the index, which is what we want to avoid. in pandas we can just check the index values, as it's already eager, but in dask we don't have a way to do this (though I have opened an issue about this https://github.com/dask/dask-expr/issues/1112)
yup, dataframe methods too 😎

I'm assuming Expr.min/Expr.max have also to be done, so I'll take those

(Asking for a friend 👀) how much cheating are we allowed to? Specifically, pandas-like translate_dtype should apply one-to-one for dask.

😄 should be fine to reuse that one

I'll look into len and round

I'll try drop_nulls and count(not sure about count since it returns a Scalar)

thanks! we have others that return scalars here, such as sum / min / ...

I will add Expr.abs

will take Expr.all

I'll take Expr.std and Expr.null_count

Ill take is_unique

Just to give a sense of how far we have gone and what's still missing.
DaskExpr methods (those marked with * at the end means that modify the index and require evaluation of #743 before implementing):

[ ] arg_true
[ ] cast
[ ] cat (depends on ExprCatNamespace)
[ ] diff
[ ] filter (*)
[ ] gather_every (*)
[ ] head (*)
[ ] is_duplicated
[ ] is_in
[ ] is_unique
[ ] null_count
[ ] over
[ ] quantile
[ ] sample (*)
[ ] tail (*)
[ ] unique (*)

ExprDateTimeNamespace methods:

[ ] to_string
[ ] total_microseconds
[ ] total_milliseconds
[ ] total_minutes
[ ] total_nanoseconds
[ ] total_seconds

ExprCatNamespace is missing entirely.

I'm working on null_count and quantile.

will work on dt.to_string

I will take a look at cast with some assumption on Dask dtypes as discussed on discord

will work on total_microseconds

I will take diff

I'll pick up quantile!

I'll take cast

I'll take concat if nobody else has yet!

Closing this for now as the only methods which are left modify the index and #743 has just been closed


Grafana Documentation

Pushing Grafana Documentation

This needs to be rebased (or probably simpler, cherry-picked into the main branch). Also, note that it is now targeted for the main branch. This is appropriate -- just be sure to backport or cherry-pick it into all appropriate release branches.


Partridge claim for which year

Alternative approach to legend on claim-for-which-year page

Not needed - going with hidden leg end


Graphql is an invalid property path ', status='null', description='null', errors=null}

I am using this library to test the graphql and I followed the document as well.
I observed that some details are missing in the documents.
I have added the arguments and sending the request but while build the query I am getting Graphql invalid property path error.

I am using this library to test the graphql and I followed the document as well.
I observed that some details are missing in the documents.
I have added the arguments and sending the request but while build the query I am getting Graphql invalid property path error.

Did you find a solution for this ?

Can you see if this article helps? https://americanexpress.io/graphql-for-the-jvm/
It has some examples defining arguments on nested paths. If you still face that error please post your models and the path you are using.
Likely it is some typo, a missing or extra level in the path, or a renamed object with the class name instead of property name being used.


Kavyakunder update readme

Description
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixed #(issue_no)
Replace issue_no with the issue number which is fixed in this PR
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Documentation Update

Checklist:

[ ] My code follows the style guidelines(Clean Code) of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added screenshots(if any) that prove my fix is effective or that my feature works

@bislara Please do have a look now.

@all-contributors please add @kavyakunder for code, doc


Boundary traversal of binary tree in cpp

🚀 Feature
I would like to add the problem - Boundary traversal of binary tree In cpp
Have you read the Contributing Guidelines on Pull Requests?
Yes

/assign


[feature]:issue15 - add try-catch for run migrations

Fix for issue15

Any tests for it?

Tests were modified.
Error patterns were used from PR12 thanks for @aywan .


Overview map draggable area is sticky if draw interaction is enabled

When the overview map is opened and the draw interaction is activated, the drag of the red area inside the overview map becomes slow and sticky.
Fiddle with bug: http://jsfiddle.net/igoroctaviano/4y0dzn5t/
Expected behavior
Drag should be smooth like without drag interaction active.

Your fiddle is using version 5.2 but 6.5 http://jsfiddle.net/f1ogejk8/ has the same problem.

Good catch. I created this one based on an old fork but I have spotted the issue in the actual code which has the newer version. So yes, same problem

Just because I was having trouble seeing the issue, I've added a checkbox to your fiddle to turn the line control on and off, so you can quickly see the difference between normal behaviour and 'sticky' behaviour - http://jsfiddle.net/u2gw7hd8/ - Just in case its useful to anyone

A workaround, based on this example https://openlayers.org/en/latest/examples/vector-tile-info.html, is to place the map in an external div, and then place that div on top of the map using css http://jsfiddle.net/4z5vLhtg/


Logo for Span should be Spanatee the Manatee

It has become clear that the new Span<T> type needs a logo. Every good type should have a logo.
I have two highly artistic ideas to toss around for the official logo of the Span<T> type. It revolves around the character of Spanatee the Manatee (it rhymes, and "Spanatee" sounds like "Span of T").
I will post each idea as its own comment so that people can vote on it. Feel free to post additional ideas (one per comment) for voting. This is not final artwork; we would presumably hire a world-renowned artist to do the final artwork.

Idea 1: Bracketed manatees showing the generic shape of <T>:

Idea 2: Spanatee the Manatee him/herself with <T> on its body:

Clearly should be a manatee drinking a cup of tea. Preferably with a top hat and monocle

Clearly we should ask Roland Tamayo if we may use his manatee as a mascotte for Span<T>

(Source: https://www.instagram.com/p/BB8L6jnQDIo/)

This one even has "the cloud" in the background. Though what's with all the pollution? Shouldn't it be kittens and flowers be coming out of the chimneyspiplelines.

Maybe it's a visual representation of the new System.IO.Pipelines namespace? (https://github.com/dotnet/corefxlab/pull/980).. +1 on the kittens & flowers

Though, what's up with all the pollution

Isn't pollution, its the air being "on fire" due to the high speed...

"Span: the 8th wonder of the 21st century. It makes even manatees fly really really fast."

Unless there is more bounds checks... then they lose speed and can't
generate enough lift and die... wont someone please think of the poor
Manatees!
On 29 Nov 2016 4:46 p.m., "Krzysztof Cwalina"<EMAIL_ADDRESS>wrote:

"Span: the 8th wonder of the 21st century. It makes even manatees fly
really really fast."
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/corefxlab/issues/1034#issuecomment-263626037,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APpZuZ65HHOAkbAuUiZCVSokEjb_G4oZks5rDFbOgaJpZM4K-mcs
.

nice mspaint skills @Eilon! 😄

@Eilon I think you are looking at this all wrong. I think of it more as referring to the incredible wingspan of the timeless Mr. T.

@mmanela I can't believe I didn't think of that!

Mr T is already taken by MRT, the managed runtime :-)

Coincidentally Spant in German is a ship frame, which, after all, "gives the ship its shape and strength".
Very fitting (pun intended).

Related: can we use OhTheHugeSpanOfTException when the requested size is too large?

Spants - the superior pants.

Now that Span moved to the corefx repo, we lost the ability to have logos for individual types, and so we cannot have a logo for Span.
Corefx does support one giant logo for all types. In this logo, some special types got 24 pixels (logolets) to use for their individual logo needs. You might want to talk to all the .net stakeholders, convince them that Span deserves a logolet, get the pixels allocated, and then come up with a way to represent a manatee in 24 pixels.
It's just better like this. The logo architecture was painstakingly designed over the last few years, and we concluded many logos are bad. Yes, the architectural we settled on results in blank reserved spaces in the giant logo, but we have plans to throw NotSupportedException when this part of the logo is decoded using our image manipulation libraries. Also, it might be hard to convince the stakeholders that your type deserves the logolet, so your type might not end up in the logo for many years, or ever.

I am disappointed.
😆


Missing az devops security permission update

In the tools used to set permissions there is no mention to the az devops security permission Azure CLI.

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

ID: aa32191d-6d0a-058f-2ffe-3ce1b58e2c59
Version Independent ID: 858d1ed3-b2af-699f-9d51-86ac0962086b
Content: How are permissions and groups defined? - Azure DevOps
Content Source: docs/organizations/security/about-permissions.md
Product: devops
Technology: devops-security
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@jessehouwing - Thank you for this feedback. I will update the article to reflect usage of the az devops security commands which are documented here: Add and manage security groups and Manage tokens and namespaces.


Default scale for date values

Hey,
Me again ;)
I'm neither fluent in ES6 nor d3 so I'm not doing any changes myself for now but maybe in the future when I'm more confident.
When creating the default scale for date values, you only specify one value for the domain instead of a range [min, max]
See https://github.com/codesuki/react-d3-components/blob/master/src/DefaultScalesMixin.jsx line 89.
Any reason for that? Because for my specific case, the graph looks much better with a [min, max] scale and I don't see how the current implementation could be better in other cases:
var data= JSON.parse("{\"label\":\"\",\"values\":[{\"x\":\"2015-02-07T23:00:00.000Z\",\"y\":2},{\"x\":\"2015-02-22T23:00:00.000Z\",\"y\":1},{\"x\":\"2015-03-04T23:00:00.000Z\",\"y\":2},{\"x\":\"2015-03-08T23:00:00.000Z\",\"y\":3},{\"x\":\"2015-03-10T23:00:00.000Z\",\"y\":1},{\"x\":\"2015-03-11T23:00:00.000Z\",\"y\":1},{\"x\":\"2015-04-04T22:00:00.000Z\",\"y\":2},{\"x\":\"2015-06-27T22:00:00.000Z\",\"y\":1},{\"x\":\"2015-07-31T22:00:00.000Z\",\"y\":2},{\"x\":\"2015-11-15T23:00:00.000Z\",\"y\":1},{\"x\":\"2015-12-29T23:00:00.000Z\",\"y\":1}]}");
<LineChart data={data} width={840} height={500} margin={{top: 10, bottom: 50, left: 50, right: 10}}, xAxis={{tickFormat: d3.time.format("%y-%m-%d")}} />

gives this graph (a zoom on the first date of the next chart):

Now,
var data= JSON.parse("{\"label\":\"\",\"values\":[{\"x\":\"2015-02-07T23:00:00.000Z\",\"y\":2},{\"x\":\"2015-02-22T23:00:00.000Z\",\"y\":1},{\"x\":\"2015-03-04T23:00:00.000Z\",\"y\":2},{\"x\":\"2015-03-08T23:00:00.000Z\",\"y\":3},{\"x\":\"2015-03-10T23:00:00.000Z\",\"y\":1},{\"x\":\"2015-03-11T23:00:00.000Z\",\"y\":1},{\"x\":\"2015-04-04T22:00:00.000Z\",\"y\":2},{\"x\":\"2015-06-27T22:00:00.000Z\",\"y\":1},{\"x\":\"2015-07-31T22:00:00.000Z\",\"y\":2},{\"x\":\"2015-11-15T23:00:00.000Z\",\"y\":1},{\"x\":\"2015-12-29T23:00:00.000Z\",\"y\":1}]}");
var dates = _.map(data.values, function(val){ return val.x; });
var minDate = _.min(dates);
var maxDate = _.max(dates);
var scale = d3.time.scale().domain([minDate, maxDate]).range([0, innerWidth]);
<LineChart data={data} scale={scale} width={840} height={500} margin={{top: 10, bottom: 50, left: 50, right: 10}}, xAxis={{tickFormat: d3.time.format("%y-%m-%d")}} />

gives this chart:

Am I missing the general case here?

Sorry for the late response. You are correct. According to the D3 documentation it should be possible if amount of X values matches amount of Y values but that might not work out in all cases, also I just tested it and it didn't work. I will change the code to just set min,max date as in your code and also the example.html which already used a custom time scale. Thanks for reporting!


Floating Status Line Showing Running Events

Is your feature request related to a problem? Please describe.
Whenever one is using macros, it's hard to tell whether it is recording or for instance one starts a macro and forgets it's still recording.
Describe the solution you'd like
Heavily inspired solution from incline would be noice.
Describe alternatives you've considered
Override incline in an instance of a macro or show it in the mini, like a persistent fidget.
Additional context
Add any other context or screenshots about the feature request here.

I am not familiar with incline, but there are multiple solutions
Please check this page of the wiki, specifically showmode section. You can customize that snippet to show the output in any view you want

Okay cool, will give it a try. Incline just hovers above the winbars, far right showing the file name

Exactly what I was looking for, I should have done more research.  Thanks
require("lualine").setup({
  sections = {
    lualine_x = {
      {
        require("noice").api.statusline.mode.get,
        cond = require("noice").api.statusline.mode.has,
        color = { fg = "#ff9e64" },
      }
    },
  },
})


primary failure and timeline change can lead to replica failure which is not respected correctly

Configuration and Cluster overview
Our cluster consists of 3 replicas (cluster-2, cluster-5 and cluster-7).
This is our configuration:
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: postgres-cluster
spec:
  imageName: ghcr.io/cloudnative-pg/postgresql:15.1
  instances: 3
  minSyncReplicas: 2
  maxSyncReplicas: 2
  storage:
    storageClass: csi-cinder-sc-retain
    size: 10Gi
  affinity:
    enablePodAntiAffinity: true
    topologyKey: failure-domain.beta.kubernetes.io/zone
  replicationSlots:
    highAvailability:
      enabled: true
  backup:
    retentionPolicy: "60d"
    barmanObjectStore:
      destinationPath: s3://storage
      endpointURL: https://s3-compatible-object-store
      s3Credentials:
        accessKeyId:
          name:  s3-postgres-backup
          key: ACCESS_KEY_ID
        secretAccessKey:
          name: s3-postgres-backup
          key: SECRET_ACCESS_KEY
  postgresql:
    parameters:
      shared_buffers: 256MB
      max_connections: '200'
  bootstrap:
    initdb:
      database: db
      owner: db
      secret:
         name: postgresql-creds

Observed behavior
The Primary instance (cluster-2) failed and cluster-5 was selected as the new primary. The failover went as usual.
cluster-5 now decided to switch the timeline (from 38 to 39)
{"level":"info","ts":"2023-09-15T20:06:20Z","logger":"postgres","msg":"record","logging_pod":"postgres-cluster-5","record":{"log_time":"2023-09-15 20:06:20.253 UTC","process_id":"31","session_id":"650001d4.1f","session_line_num":"15","session_start_time":"2023-09-12 06:14:44 UTC","virtual_transaction_id":"1/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"selected new timeline ID: 39","backend_type":"startup","query_id":"0"}}

cluster-7 acknowledged this change
{"level":"info","ts":"2023-09-15T20:06:29Z","logger":"postgres","msg":"record","logging_pod":"postgres-cluster-7","record":{"log_time":"2023-09-15 20:06:29.934 UTC","process_id":"254432","session_id":"6504b945.3e1e0","session_line_num":"1","session_start_time":"2023-09-15 20:06:29 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"fetching timeline history file for timeline 39 from primary server","backend_type":"walreceiver","query_id":"0"}}

cluster-7 is missing wal files though
{"level":"info","ts":"2023-09-15T20:07:23Z","logger":"postgres","msg":"record","logging_pod":"postgres-cluster-7","record":{"log_time":"2023-09-15 20:07:23.014 UTC","process_id":"25","session_id":"65001585.19","session_line_num":"55","session_start_time":"2023-09-12 07:38:45 UTC","virtual_transaction_id":"1/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"new timeline 39 forked off current database system timeline 38 before current recovery point AF/3D000000","backend_type":"startup","query_id":"0"}}

cluster-7 attempts to get the wal file from cluster 5 which also does not possess it.
{"level":"info","ts":"2023-09-15T20:07:09Z","logger":"postgres","msg":"record","logging_pod":"postgres-cluster-5","record":{"log_time":"2023-09-15 20:07:09.695 UTC","user_name":"streaming_replica","process_id":"259270","connection_from":"<IP_ADDRESS>:43428","session_id":"6504b96d.3f4c6","session_line_num":"1","command_tag":"START_REPLICATION","session_start_time":"2023-09-15 20:07:09 UTC","virtual_transaction_id":"11/0","transaction_id":"0","error_severity":"ERROR","sql_state_code":"XX000","message":"requested starting point AF/3D000000 on timeline 38 is not in this server's history","detail":"This server's history forked from timeline 38 at AF/3C000000.","query":"START_REPLICATION SLOT \"_cnpg_scrumlr_postgres_cluster_7\" AF/3D000000 TIMELINE 38","application_name":"scrumlr-postgres-cluster-7","backend_type":"walsender","query_id":"0"}}

cluster-7 now tries to find the wal files in the s3 but also fails
{"level":"info","ts":"2023-09-15T20:07:26Z","logger":"wal-restore","msg":"WAL file not found in the recovery object store","logging_pod":"postgres-cluster-7","walName":"00000028.history","options":["--endpoint-url","https://object-store.","--cloud-provider","aws-s3","s3://path","postgres-cluster"],"startTime":"2023-09-15T20:07:26Z","endTime":"2023-09-15T20:07:26Z","elapsedWalTime":0.883701889}

At this point the pod stales and constantly attempts to read the wal files.
{"level":"info","ts":"2023-09-16T19:08:21Z","logger":"postgres","msg":"record","logging_pod":"postgres-cluster-7","record":{"log_time":"2023-09-16 19:08:21.663 UTC","process_id":"25","session_id":"65001585.19","session_line_num":"63667","session_start_time":"2023-09-12 07:38:45 UTC","virtual_transaction_id":"1/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"waiting for WAL to become available at AF/3D000018","backend_type":"startup","query_id":"0"}}

cluster-2 has rejoned the cluster and is running smooth as a replica.
The issue
Now that cluster-7 has become stale the operator marks it as "Standby (file-based)". The cluster shows up as healthy.
This is an issue as we have configured quorum-based replication. The cluster needs at least 3 replicas to write but cluster-7 can not respond (its stuck in wal recovery).
This can become an even bigger issue (as it happend to us) if the 2 other replicas somehow fail the file-based Standby is deemed to be the most in sync and promoted to a primary. Suddenly you are writing on top of potentially 1-2 days old data if you havent configured quorum-based replication.
Expected Behavior
The Operator Should never mark a replica as healthy that is looping wal recovery and out of sync.
You could force terminate the replica and have a new one join the cluster (as the other 2 replicas are in agreement that everything is fine).
The Operator should never ever select a stale file-based replica as a new primary especially not if its heavily out of sync.
If you need any more information (logs or other intel) Id be happy to provide them to you (we have all logs).
Thanks for making and maintaining this awesome operator (startup and docs are <3).
Just unfortunate that we have been running into this issue twice this week now.

We are also having this same issue. It's been putting our cluster in a precarious state.
This is making me reconsider whether or not I should continue using CloudNative-PG in production.

@BlakeB415 can you reproduce this issue by using the strategy outlined here
For now scaling your cluster down to 2 replicas should circumvent this issue (at least it does for us).

The symptom you are seeing (file based replication) is not the cause. Simply, cluster-7 has no way to attach via streaming to the primary, so PostgreSQL uses the fallback method to fetch the file. Hence the plugin thinks that the standby is in file based replication.
This is very strange and we would really love to work with you on fixing this. We should use the next office hours if possible, or we can organize a meeting.

This might be related to #2910

All our database replicas completely failed on us due to this issue. Our cluster was undergoing maintenance and some of the nodes were stopped. The failover worked, but when we brought the node back online, the pods started crashing.
What is currently the best way to recover from this issue...?

@BlakeB415 would be nice to know what error you are seeing on the crash loopin replicas

@BlakeB415 would be nice to know what error you are seeing on the crash loopin replicas

This is the error before it crashes.
{"level":"info","ts":"2023-10-06T20:05:53Z","logger":"postgres","msg":"record","logging_pod":"vanillo-db-9","record":{"log_time":"2023-10-06 20:05:53.687 UTC","process_id":"20","session_id":"65206896.14","session_line_num":"6","session_start_time":"2023-10-06 20:05:42 UTC","transaction_id":"0","error_severity":"FATAL","sql_state_code":"XX000","message":"requested timeline 20 is not a child of this server's history","detail":"Latest checkpoint is at 92/49000060 on timeline 19, but in the history of the requested timeline, the server forked off from that timeline at 8D/901FAA8.","backend_type":"startup","query_id":"0"}}

@BlakeB415 would be nice to know what error you are seeing on the crash loopin replicas

This is the error before it crashes.
{"level":"info","ts":"2023-10-06T20:05:53Z","logger":"postgres","msg":"record","logging_pod":"vanillo-db-9","record":{"log_time":"2023-10-06 20:05:53.687 UTC","process_id":"20","session_id":"65206896.14","session_line_num":"6","session_start_time":"2023-10-06 20:05:42 UTC","transaction_id":"0","error_severity":"FATAL","sql_state_code":"XX000","message":"requested timeline 20 is not a child of this server's history","detail":"Latest checkpoint is at 92/49000060 on timeline 19, but in the history of the requested timeline, the server forked off from that timeline at 8D/901FAA8.","backend_type":"startup","query_id":"0"}}
Please make sure all the data you want is on the current primary to avoid data loss.  This will lead to a fresh replica joining the cluster wich will bootstrap correctly.

@BlakeB415 would be nice to know what error you are seeing on the crash loopin replicas

This is the error before it crashes.
{"level":"info","ts":"2023-10-06T20:05:53Z","logger":"postgres","msg":"record","logging_pod":"vanillo-db-9","record":{"log_time":"2023-10-06 20:05:53.687 UTC","process_id":"20","session_id":"65206896.14","session_line_num":"6","session_start_time":"2023-10-06 20:05:42 UTC","transaction_id":"0","error_severity":"FATAL","sql_state_code":"XX000","message":"requested timeline 20 is not a child of this server's history","detail":"Latest checkpoint is at 92/49000060 on timeline 19, but in the history of the requested timeline, the server forked off from that timeline at 8D/901FAA8.","backend_type":"startup","query_id":"0"}}
Please make sure all the data you want is on the current primary to avoid data loss.  This will lead to a fresh replica joining the cluster wich will bootstrap correctly.

I've done this, and the result is the same. Every replica I create in this cluster has the same issue.

I am really sorry @BlakeB415 that you moved to another operator, as CloudNativePG is a production ready operator.
I still suspect that the issue is due to using the default timeout values (which have all been changed and raised in the last patch release - see https://cloudnative-pg.io/documentation/current/installation_upgrade/#upgrading-to-1210-1203-or-1195).
We recommended to change those values based on the existing environment, but noticed that most users were not doing that - hence why we took that step. With the current default settings, those issues should not happen anymore.

@Lennart01 ok to close this ticket?

@gbartolini I would like to retest this issue with the new release. I will report back.

Could not reproduce this with the latest version. I'm closing this.
Thanks for the help 🥳


save embedding failed: ' {"message":"Error inserting: TypeError: fetch failed 0 "}. while uploading pdf

Getting this error-  save embedding failed: ' {"message":"Error inserting: TypeError: fetch failed 0 "}. while uploading pdf.
I tried recreating superbase DB but it didn't helped.

after redeploying to vercel facing this issue- save embedding failed: ' An error occurred with your deployment FUNCTION_INVOCATION_TIMEOUT .

same issue

after redeploying to vercel facing this issue- save embedding failed: ' An error occurred with your deployment FUNCTION_INVOCATION_TIMEOUT .

Have you solved this problem now? How was it resolved?


Add node pattern methods to handle dependency audits in a better way

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

#569 and #2662
RuboCop has pattern searching macros which simplify searching/matching nodes in AST.
Found documentation for same in the source of node_pattern.rb
This PR updates depends_on audits to use such pattern matching methods, so code becomes more readable and also fixes bug in previous code which wasn't detecting dependencies.
(there is however one edge case where the value of a depends_on hash is an array, I know how exactly to implement that and will deal with that later)
Edit: How did I derive those patterns?  By running the below commands and looking at the AST.
$ ruby-parse -e 'depends_on :x11 => optional'
$ ruby-parse -e 'depends_on "readline" => :recommended'
cc @ilovezfs

Thanks again @GauthamGoli!