GPT4All generate() TypeError 'n_ctx' since a commit on GPT4All's python binding changed arguments

System Info

langchain-0.0.222 (and all before)
Any GPT4All python package after this commit was merged. So latest: >= 1.0.1.

Note this issue is in langchain caused by GPT4All's change. We need to alter the _default_params() return values to exclude many keys that were removed from GPT4All's function kwargs.
Who can help?
@hwchase17 @agola11 👋
Information

[ ] The official example notebooks/scripts
[X] My own modified scripts

Related Components

[X] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction

Install the latest gpt4all package: pip install --upgrade gpt4all
Use the GPT4All LLM and LLMChain as normal (llm = GPT4All(model="ggml.gpt4all.xyz.bin"); chain = LLMChain(llm, prompt=any_prompt))
Run the chain: chain("prompt")
TypeError: generate() got an unexpected keyword argument 'n_ctx'

Expected behavior
Should not cause TypeError. It should not pass n_ctx from default parameters to GPT4All's generate()

Entire error traceback:
Traceback (most recent call last):
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\gradio\routes.py", line 437, in run_predict
    output = await app.get_blocks().process_api(
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\gradio\blocks.py", line 1352, in process_api
    result = await self.call_function(
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\gradio\blocks.py", line 1093, in call_function
    prediction = await utils.async_iteration(iterator)
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\gradio\utils.py", line 341, in async_iteration
    return await iterator.__anext__()
  File "langchain_gradio.py", line 214, in generate
    await output_task
  File "C:\Program Files\Python39\lib\concurrent\futures\thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "langchain_gradio.py", line 142, in run_chain_sync
    result = chain(inputs, callbacks=[stream_callback])
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\chains\base.py", line 166, in __call__
    raise e
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\chains\base.py", line 160, in __call__
    self._call(inputs, run_manager=run_manager)
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\chains\qa_with_sources\base.py", line 128, in _call
    answer = self.combine_documents_chain.run(
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\chains\base.py", line 293, in run
    return self(kwargs, callbacks=callbacks, tags=tags)[_output_key]
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\chains\base.py", line 166, in __call__
    raise e
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\chains\base.py", line 160, in __call__
    self._call(inputs, run_manager=run_manager)
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\chains\combine_documents\base.py", line 84, in _call
    output, extra_return_dict = self.combine_docs(
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\chains\combine_documents\stuff.py", line 87, in combine_docs
    return self.llm_chain.predict(callbacks=callbacks, **inputs), {}
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\chains\llm.py", line 252, in predict
    return self(kwargs, callbacks=callbacks)[self.output_key]
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\chains\base.py", line 166, in __call__
    raise e
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\chains\base.py", line 160, in __call__
    self._call(inputs, run_manager=run_manager)
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\chains\llm.py", line 92, in _call
    response = self.generate([inputs], run_manager=run_manager)
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\chains\llm.py", line 102, in generate
    return self.llm.generate_prompt(
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\llms\base.py", line 141, in generate_prompt
    return self.generate(prompt_strings, stop=stop, callbacks=callbacks, **kwargs)
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\llms\base.py", line 227, in generate
    output = self._generate_helper(
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\llms\base.py", line 178, in _generate_helper
    raise e
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\llms\base.py", line 165, in _generate_helper
    self._generate(
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\llms\base.py", line 525, in _generate
    self._call(prompt, stop=stop, run_manager=run_manager, **kwargs)
  File "f:\Projects\gpt\privateGPT\venv\lib\site-packages\langchain\llms\gpt4all.py", line 208, in _call
    for token in self.client.generate(prompt, **params):
TypeError: generate() got an unexpected keyword argument 'n_ctx'

https://github.com/hwchase17/langchain/pull/7093

Yes, I also hit this yesterday and put up / merged a PR to resolve:
https://github.com/hwchase17/langchain/pull/7093
Note: this may be a breaking change for users that upgrade LangChain, but are still using the older GPT4All client. If anyone has additional context on GPT4All client, I'd welcome a backwards compatible fix. My first time using GPT4All was yesterday and I noticed it was broken, so fixed it here but do not have a lot of context on the client.

Yeah same, I encountered it by accident after updating gpt4all. I hadn't seen the PR you created as I looked straight for the issues tab.
But anyway yeah this will force people to upgrade gpt4all package to allow the langchain wrapper to function still

Yeah same, I encountered it by accident after updating gpt4all. I hadn't seen the PR you created as I looked straight for the issues tab.
But anyway yeah this will force people to upgrade gpt4all package to allow the langchain wrapper to function still

Got it. If you see an easy way to make it backwards compatible, feel free to put up a follow-up PR. It wasn't too obvious to me other than some fairly ugly try-catch logic, but as noted I don't have a lot of context on the GPT4All client. Perhaps a warning to tell users to upgrade the package?

Yeah same, I encountered it.
use this combination of versions
Name: langchain
Version: 0.0.171
Name: gpt4all
Version: 1.0.3
It worked for me. You can try this.


Unable to override after_invite_path_for(resource) in ApplicationsController

I have defined the following method in my Application Controller.  I also would like to mention that I do not have any custom controllers for devise or devise_invitable.  I am currently running Rails 4.2 with Devise 3.4.1 and devise_invitable 1.4.2 (checked to make sure overrides were supported).  Perhaps @mwear  can provide some support?
def after_invite_path_for(resource)
    root_path
end

However when I invite a new member, I am not redirected to the correct path.

@Yanchek99 What was the issue with this? Did it ever work for you?


Windows 11 error

Not sure if it goes here but I can't run TwitchLink in Windows 11.
Simply doesn't open.

Try to describe the problem as detailed as possible.
Provide as much information about the problem as possible.
Please attach the log file with the issue.

If I click on open TwitchLink it will appear as a process on the Task Manager for a second or so and then disappear as if it had closed.
There's no log file since it doesn't even open the program for a more formal error to occur.

It seems that the program has not been installed properly. Some antivirus programs can cause such results.

Figured out, it was a conflict with a entirely different program.


Clone signers

This PR fixes #2668 by not attempting to read signers more than once. Because signers are trait objects, and so unsized, the approach here is to clone a pointer which will point to the same object in memory, not the data on the heap itself. This requires a change from Box to Rc or Arc, and I've gone with Arc. This requires corresponding changes in solana-labs/solana, so there's a temporary commit 89a6afe1ea991801ad2f7c0b91f858e5f1001d21 to allow testing, which needs to be reverted before the PR is merged (hence the WIP). I've stored the Arcs in the config struct just for convenience elsewhere; unfortunately they're needed to construct some of the other struct fields, so some of the stuff that was in config.rs has now moved into main.rs—if there's a better way of organising this, I'd be happy to make changes. I haven't dealt here with commands other than the behaviour in #2668 described with mint, but the PR could be expanded a bit if this was desired—it looks like getting the nonce authority could cause the same problem with rereading the signer for instance (so requiring a change like ef8a27b264bf3accc049671ad8fcbc64d68e5ca6).

The tests for transferring and burning with a delegate are now failing but I'm pushing anyway. As far as I can tell the delegate is being ignored because transferring more than has been approved doesn't fail. I can see that the instructions in the case with and without the delegate do differ as expected—only in the case with the delegate are there two separate addresses for the source and the owner

I'm not clear why clippy is giving these errors, as far as I can see the build fails without the imports

Great work, thanks for the contribution!


Feature/#30 duplicate and conflict style for gml

Coverage increased (+0.4%) to 82.881% when pulling f1e39176a168f8671b202cfe782bb7ca70a4f51a on feature/#30-duplicate-and-conflict-style-for-gml into 34b951b8d5e6227fb1c89fcc7e5540661d9492d5 on master.


Bugfix/LIVE-973 - Discreet mode restricted to portfolio & accounts screens

Discreet mode should only affect values displayed in the Portfolio and Account/Accounts screens.
I implemented a new Context DiscreetModeContext and its provider DiscreetModeProvider can be used to wrap entire screens that should be affected by the discreet mode. A HOC withDiscreetMode makes wrapping existing components even easier.
The specification isn't extremely detailed as it just says "only hides portfolio value and individual accounts value" but I've chosen these screens/components to be affected by the discreet mode:
Account screens: (in AccountsNavigator)

screens/Account
screens/Accounts
screens/Nft/NftGallery
screens/Nft/Collection

Operation details screen:

screens/OperationDetails

Portfolio screens:

screens/Portfolio
screens/Asset the screen that shows up when pressing an asset in the portfolio "asset allocation" section.
screens/Distribution the screen that shows up when pressing the "all" CTA in the portfolio "asset allocation" section.

In the following video I'm showing all of these screens in discreet mode, and at the end one screen (the buy flow / select account screen) to demonstrate that values outside of these screens aren't affected anymore by discreet mode.
https://user-images.githubusercontent.com/91890529/154706222-e40162d7-f45f-43e4-aed8-1673bbfb647f.mp4
Type
Bug fix
Context
LIVE-973
Parts of the app affected / Test plan

Indeed @juan-cortes, I'm going to look for a real fix for that 👍


Countdown to Qualifying

The actual countdown only shows time till race but I want to know how long it takes to next qualifying

Or countdown to next event of race weekend like training etc.

@snp88  @superpower10 checkout the latest release :)

@marcokreeft87
is this correct configuration for this ?
type: custom:formulaone-card
card_type: countdown
f1_font: true
countdown_type: race,qualifying,practice1,practice2,practice3,sprint

No you have to choose one


Implements Template Card Display Component

Implements a Component to Visualize and Explore all of the Templates in the Platform

Task linked: CU-3e69xdn Create Student Template Card Display Component (W/O Adaptative Logic)


Hide Radicle commands and UI when not applicable

Following up on #23 which introduces workspace state awareness, we should ensure that any Radicle commands or related UI that will fail given the current state should be unavailable to the user.
Specifically, we should hide all of "sync", "push" and "pull" commands from everywhere in the UI altogether.
That includes:

commands shown with Ctrl+Shift+p under the Radicle filter
welcome screens
SCM navigation group
SCM 3dot-menu
... anything else

Result:

Notice missing rad push/pull/sync command options
Similarly done for the native Source Control Manager of VS Code as per the issue description (tricky to screenshot).


Fix exercise images not being removed

A one-liner to fix exercise images not being deleted on long press. This gives image a null value instead of trying to make it absent when deleting an image, since drift doesn't seem to write absent values to the database.
I don't know much about database stuff so there might be a better solution, but from my quick testing this works fine.
Resolves #105

Thanks king all these changes have been excellent.


@valibot/i18n could not be installed

$ npm i @valibot/i18n -D
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/valibot
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@valibot/i18n
npm ERR!   dev @valibot/i18n@"*" from the root project
npm ERR!
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\Administrator\AppData\Local\npm-cache\_logs\2024-05-31T01_02_59_955Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: C:\Users\Administrator\AppData\Local\npm-cache\_logs\2024-05-31T01_02_59_955Z-debug-0.log

I'm sorry, our i18n package has not yet been updated to our new release candidate. I will work on it as soon as I officially release v0.31.0 next week. Until then, you can downgrade Valibot to v0.30.0 or keep your current version and manually add the translations you need. Reach out if you have any questions.

I have seen the official release of v0.31.0, but the corresponding translation package has not been updated synchronously yet

That's true. I will try to fix this today.

@valibot/i18n v0.15.0 is available


Add simplified Pomodoro Timer

The idea is to allow user to add notification when the pomodoro timer set time has ran out.

[ ] Add setting checkbox Enable Pomodoro Timer
If checked (show/enable) another setting Pomodoro timer interval
[ ] If Pomodoro is enabled the timer is started every time timer is started in the app.
[ ] When Pomodoro timer has ended:

Timer is stopped
App shows notification Time is up, take a break!
Notification has two buttons: Continue latest, Start new

:+1:
May be linked with https://github.com/toggl/toggldesktop/issues/1648

looks like @tanel 's taking a stab at it in Feb.  Thanks you all!

+1 for this feature, would replace my current pomodoro timer.

+1

This will help me stick to Toggle forever :D not to talk about having it also on Android :+1:

We have planned to start developing this in the end of January. Until then you could use Toggl Button Chrome extension as it already has Pomodoro timer feature. Get Toggl Button!

I just read a nice blog post about Toggle Button, thank you for the feedback! Can't wait to have it on Android and desktop! :cool:  I can handle 3 more months  :)

Windows implementation is looking good now. (Still on pomodoro)

Version 2 updates are in issue #1789


Noise is recognized as breath + noise make the state machine work not as expected

Running noise simulation doesn't send no-breath alert

Running test_sinus_simulation.py in noise_test branch will show this issue.
The test running noisy sinus and print the pressure + current state.
It can be seen that the state machine is in wrong state after several samplers


FancyZones update request

Description of the new feature / enhancement
I would love an option that I could toggle on/off that would allow me to switch window placements between zones. For example, Let's say I have my screen with 2 zones, split down the middle. Spotify on the left, Browser on the right. I would like it if I dragged Spotify into the zone on the right, it would switch my Browser window to the left zone, effectively switching them places. Similarly, if I opened a new program and placed it in a zone already containing a program but there was an empty zone available, I'd like it to move that replaced window into the empty zone, rather than have it 'underneath' the new program in the same zone.
I hope this makes sense. Your suite of tools are all absolutely incredible
Scenario when this would be used?
I think it would be useful in lots of scenarios but let's say you have Discord/Teams open in a smaller zone while whatever you're working on is in a large zone taking up most of your screen. Someone calls a conference and you want to switch Teams into the big space on your screen without overlapping your work/leaving an empty zone. You want to just quickly drag Teams into the large zone, which would automatically switch whatever you were working on into the space Teams left behind. I think it would be useful in scenarios where work has changing priorities but you still  want to be able to see it all at a glance.
Supporting information
No response

Honestly, the (example?) situation you describe would be much easier with default Windows Snap. Assuming the setting" Show what I can snap more" is on.

Fair enough. I just prefer FanzyZones in every other way and wanted to make
it "perfect" for what I want by suggesting this one feature it's missing.
I'd rather use FancyZones and just not have that feature then. Windows Snap
is limited in comparison so that one thing isn't enough to make me abandon
Zones! Thanks for replying though.
On Fri, 5 Aug 2022, 10:15 Jay, @.***> wrote:

Honestly, the (example?) situation you describe would be much easier with
default Windows Snap. Assuming the setting" Show what I can snap more" is
on.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/19764#issuecomment-1206230219,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2LTORWMOASPESPIIYP22GLVXTLU5ANCNFSM55SB4RXA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Feature Request: Change Load Shedding Zone

Two parts:
(1) Request a way to change zone without reinstalling.
(2) Request a way to change load-shedding zones without breaking existing automations.
SA being what it is, we have dodgy infrastructure. Our area has changed LS zones twice in the last 12 months as they reroute our feed to different substations when conducting repairs or waiting for parts. Our last switch lasted 6 months, but now we are "back" (for now?) on our "original" zone. This time around, however, I have many more integrations which are now based on a sensor that is named after the zone.

Automations break, because the Entity ID is unique per area and based off of the Area ID.
Home Assistant allows you to rename Entity IDs to whatever you want as long a they are unique.
To make this change for the integration will be a breaking change for everyone and will break everyone's automations and dashboards.  Will keep it in mind for a v2 as I get that this is annoying and inconvenient.
What you can try for now is to, after removing and adding the integration with a new area, Edit the Area Entity and rename the Entity ID to what the previous one was or to whatever you want to call it and then reference that in automations and dashboards.  Then you only need to rename one thing every time it changes.

@wernerhp technically you can make a change without breaking the existing user's automations etc. It will only break if the user remove and re-add the integration and a new name is then different.
The integration suggest the initial entitiy id right. So, in the future, the integration should rather suggest a generic zone name that is not based on the area id. Users will still have the option to rename it to an area id if they want, but I think a generic name is better, more re-usable and will fix the problems you describe and allow the feature request to go ahead.
And lets say you do change the name it suggests in the current version, all it takes, is for me to go rename the entity id back to what I have in all my automations. and this will only happen IF I remove and re-add the integration after such a change.

Yeah, that's true.  Thanks for pointing it out.  Will keep that in mind. It will make debugging the Area ID in use for the Entiry a bit harder, so will have to add it to the attributes or something.

The current way, if someone rename the entity id to fix their automations, you wouldn't know and in fact it will make debugging even harder if not impossible. I call this unreliable information. More reliable is having it as an attribute and part of the logging if you need it for debugging purposes.

Yup, @glibg10b I received the same email.  Not sure how straightforward it will be to update a HA config entry when handling a 404, but will see what can be done.

I do want to say that my original problem was easier to solve than I had imagined - thank you for your comments and suggestions. It turns out that while lots happens in my automations during loadshedding, most are based on my inverter reporting having electricity or not (we have regular infrastructure outages unrelated to Load Shedding where we live). So, whether it's load shedding or not, many extraneous loads are turned off during power outages. I have tried to "future proof" my automations by using intermediate helper sensors which can be updated to refer to different sensor names and provide a consistent interface for the rest of HA.
However, it is inevitable that zones will change, be added and dropped, and I would still like to see a "minimal effort" solution managed by the integration to at least allow searching for a new zone. And if nothing else has to be updated, that would be first prize!

Please help with testing the new beta
https://github.com/wernerhp/ha.integration.load_shedding/releases/tag/v1.4.0

Please help with testing the new beta https://github.com/wernerhp/ha.integration.load_shedding/releases/tag/v1.4.0

I got an error the first time I clicked "Submit" for both the API key and the search. It could just be instability on my end, though, so I won't do any further testing unless someone else has the same issue.

Please help with testing the new beta https://github.com/wernerhp/ha.integration.load_shedding/releases/tag/v1.4.0

I got an error the first time I clicked "Submit" for both the API key and the search. It could just be instability on my end, though, so I won't do any further testing unless someone else has the same issue.
As for adding and removing areas, that works perfectly fine :)
Could you trigger an integration reload after an area is added?

Please provide more info on the error. There should be details in the logs.
Are you on the free API? If so, how many of the 50 calls have you made at the timw you got the error?

@wernerhp Here's my logfile: home-assistant.log. The errors are from automations and entities that rely on the custom names I had set for load_shedding's entities. I don't see any log entries related to the errors I got.
I lost my old API key when I switched to the manual installation method, so I had to get a new one. It's working fine now, though, so I don't think that's the problem. The new key's request count is currently at 10.

Using a new key within 24h of your old key will get both banned for 24h.

Anyone able to do some testing on the 1.4.0-beta?


Mean irradience data

We've noticed that some of the Icon DWD Huggingface Irradience data is the mean, not the hourly average
Detailed Description
import xarray as xr
import ocf_blosc2
file = 'zip:///::hf://datasets/openclimatefix/dwd-icon-eu/data/2021/1/1/20210101_00.zarr.zip'
data = xr.open_zarr( f"{file}",chunks="auto")
dd = data['aswdifd_s']
dd.mean(dim=['latitude','longitude']).plot()

Context
Our model is trained on hourly average data, so this may casue the evaluation to underperform
Possible Implementation

[ ] Have transformer back to hourly data. I think you take the differences, and then times by the number of datapoints.
[x] Check live data doesnt have this problem
[ ] Check other variables dont have this problem
[x] Check other data on hugginface, do we also see this? Looks similar

Looking at the following variables

t_2m: Looks fine, hourly
tot_prec: This looks cumulative, as suggested by the name
aswdifd_s: mean since the start of forecast
aswdir_s: mean since the start of the forecast
clcl: not sure, seem to go between 0 and 100, in this forecast. Not sure if this is hourly mean or mean from the start
clcm: not sure, seem to go between 0 and 100, in this forecast. Not sure if this is hourly mean or mean from the start
clch: not sure, seem to go between 0 and 100, in this forecast. Not sure if this is hourly mean or mean from the start

I think ive managed a algorihtm to change back to average hour, rather than mean across forecast horizon
hours_steps = np.array(dd.step.values/<PHONE_NUMBER>000)
hours_steps_diff = hours_steps[1:] - hours_steps[:-1]

dd_cum_sum = dd*hours_steps[1:93,None,None]
dd_mean= dd_cum_sum.diff("step") / hours_steps_diff[:,None,None]


[🐞] Dynamic routes return 404s in static html builds

Which component is affected?
Qwik-city [routing]
... Or possibly qwik runtime
Describe the bug
I'm building for firebase hosting, so I'm doing static HTML builds.
When I have a dynamic route it's returning 404s. When I run the dev server with npm run dev they work fine. It doesn't look like it's building the html files for the dynamic routes

Reproduction
https://corrineskitchen-dev.web.app/contact/test
Steps to reproduce
Eg, I have a contact page routes/contact/index.tsx. If I make a dynamic route routes/contact/[test]/index.tsx which is just a component that returns "Hello Qwik" - so as simple as possible, I get a 404 in the production build.
The same happens if the route is only a dynamic route, eg: routes/post/[id]/index.tsx

The result from the production build

With the dev server it works fine:

System Info
System:
    OS: macOS 13.3.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 21.63 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.1.0 - /usr/local/bin/node
    npm: 9.6.4 - /usr/local/bin/npm
  Browsers:
    Chrome: 112.0.5615.137
    Edge: 112.0.1722.68
    Firefox: 112.0.2
    Safari: 16.4
  npmPackages:
    @builder.io/qwik: ^1.0.0 => 1.0.0
    @builder.io/qwik-city: ^1.0.0 => 1.0.0
    @builder.io/sdk-qwik: ^0.3.0 => 0.3.0
    undici: 5.14.0 => 5.14.0
    vite: 4.0.3 => 4.0.3

Additional Information

I've reproduced this with a fresh v1 qwik app. All I did was add a dynamic route under the /demo/flower/ route that comes with the initial setup. I've uploaded it here including the /dist folder
https://github.com/duncan1a/qwik-v1

I've run it with npm/http-server ( https://www.npmjs.com/package/http-server/v/13.0.1 )

Have the same problem !

Solved the problem by using Netlify Edge ^^

@othy54 Can you please explain here...how to solved it?

@othy54 Can you please explain here...how to be solved it? I'm also facing same issue.

npm run qwik add netlify-edge

this is because when rendering static pages you need to know how to get the data
https://qwik.dev/docs/guides/static-site-generation/#dynamic-ssg-routes

Thanks @PatrickJS for your help


Expose auth and context middleware to outside components

Some outside modules need access to these. For custom endpoints.

fixed


set the time limit for build depends to 25m

The default settings for watchdog during build depends phase is at 5 minute, but this can be in some case not enough when extracting texlive-texmf for example. So let's rise it to 25 minute

why would you alter "build" for an extraction operation
this is not clock time.  5 minutes is a multiplier
I build texlive-depends all the time and have never seen it time out

You said "some cases".  I've not seen any cases.  You need to expand on this.  In any case, the commit itself is wrong.

ah, you changed "build depends", not "build".
5 => 25 is much too big a jump.  It essentially turns off the watchdog.

It might help to run /usr/bin/time against texlive-texmf to measure actual time and then list what system and disk that's one.  (I assume a spinning disk here)

reopen to figure out better multiplier if necessary.

like time synth install categorie/texlive-texmf ?

no.  extract it yourself and time it.
/usr/bin/time -h tar -xf .... or something like that.

worst case scenario is spinning disk and no use of tmpfs.  You need to indicate your use case here.

So I am using spinning disk, use tmpfs with 4GB of ram, 2GB + 7500MB of swap (the first on hard drive, the second on usb3 key).
Synth configuration is 2 builders , 2 jobs , and use of ccache
I will put the result of time when it finish

"7500MB of swap  on usb3 key"
ouch, that sounds painfully slow.  I standard corrected, spinning disk isn't the worst case scenario.

how many builders?  If it's more than 2, then tmpfs probably shouldn't be used.

So I am using spinning disk, use tmpfs with 4GB of ram, 2GB + 7500MB of swap (the first on hard drive, the second on usb3 key).
Synth configuration is 2 builders , 2 jobs , and use of ccache
so time take
6m51,18s real		1m30,38s user		26,60s sys
so setting it to 8 min should help, or building with only one builder

really, that took nearly 7 minutes?
The multiplier should be at least 50% longer, so I think we're looking at 10 minutes here.

bump it from 5 to 11 and return the comment that it's for texlive, then I can merge it.


google/flan-t5-xxl and google/flan-t5-xl don't seem to work with HuggingFaceHub

First, when I load them I get a warning:
hf = HuggingFaceHub(repo_id="google/flan-t5-xl")
You're using a different task than the one specified in the repository. Be sure to know what you're doing :)

Then, when I use it in inference, I get gibberish.
hf("The capital of New York is")
'ew York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is'

If I run the API via requests, I get the expected answer
import requests

API_URL = "https://api-inference.huggingface.co/models/google/flan-t5-xl"
headers = {"Authorization": "Bearer api_org_xxxxxxxxxxxxxxxxxxxxxxxxxxx"}

def query(payload):
	response = requests.post(API_URL, headers=headers, json=payload)
	return response.json()

output = query({
	"inputs": "The capital of New York is",
})
print(output)
[{'generated_text': 'Albany'}]

Any suggestions?

i think its because we currently hard code the task to be text-generation (https://github.com/hwchase17/langchain/blob/e48e562ea5041b7f950435c82245b3bc201ac2b1/langchain/llms/huggingface_hub.py#L66) and flan is text2text-generation
will expose a flag to change that tonight!

thanks for the fix. This might be unrelated, but version 0.10.0 is not picking up the HF API token from the environment variable (the earlier version did with the same code); passing it in as an argument still works.


feat: add createTransactionSkeleton function

Description

[x] add createTransactionSkeleton function

resolve: https://github.com/ckb-js/lumos/issues/461
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules -->

comment of createTransactionSkeleton need to prettier


Current Accessibility Issues

'Mix Ay' should be 'Mix A' (Fixed in #7642d4b)
Submix 'Monitor' settings are unlabelled
Submenus have focus issues, don't correctly track arrows and move focus back to the Document when using NVDA
Animation Waterfall buttons aren't appropriately labelled (Potential Fix in #fd01111)
Colour Boxes need format clarification on Text inputs
Investigate ways to make the Mic Volume visualisation Accessibility friendly (potential Screen reader only input that can announce current levels)

Shoutout to Amethyst on discord for the help!

The LICENSES page is presented as an edit field. It should probably not be that, as you can't edit it either way.

Ok, I've made a tweak to the Monitor buttons being unlabelled, I've changed them from:

To:
      <div role="radio" class="button" @click="setMixMonitor" :class="{ highlight: isMixMonitored() }"
           :aria-label="`Monitor ${display}`" :aria-description="`Listen to ${display} in Headphones`"
           :aria-checked="isMixMonitored()">

Which should give some better feedback to screen readers. While they're not technically radio buttons (primarily due to the way that HTML works), they do behave as such (only one 'Monitor' can be active at a time), hopefully this will at least represent them in a way which makes more sense and is more descriptive.
Committed as a904ff29.

The LICENSES page is presented as an edit field. It should probably not be that, as you can't edit it either way.

I'll need to address this, using a text box provides a certain level of automatic formatting and scrollbars which is why it was used, but it should be simple enough to convert it into a normal HTML element.
This likely wont hit 1.1.3, but I'll keep the issue open for future developments.


Fixed application issues in Edge

Had to disable caching on all GET requests in express. Also made it so that clicking on setups doesn't do anything (it used to play the sim). #323

#351


Remove memory limits from Prometheis

How to categorize this PR?

/area scalability
/kind bug
What this PR does / why we need it:
After https://github.com/gardener/gardener/pull/9192, the limits are no longer automatically scaled by VPA. Hence, they will always remain at their static 2000Mi value, effectively causing Prometheis pods to run OOM.
To align the config with the shoot Prometheus, let's simply remove the memory limits: https://github.com/gardener/gardener/blob/55193c7184b6cc27fb5c4a86c45888e7f8eb7fcd/pkg/component/monitoring/charts/seed-monitoring/charts/core/charts/prometheus/templates/prometheus.yaml#L119-L122
Which issue(s) this PR fixes:
Follow-up of #9192
Special notes for your reviewer:
NONE
Release note:

NONE

/cherry-pick release-v1.89

/cc @ScheererJ


openvpn:latest image doesn't work with client config

Since OpenVPN 2.4, the server has apparently gotten pickier about got compression configuration and the generated client config causes errors like this for me (Viscosity, OS X):
openvpn_1  | Mon Oct 15 02:59:03 2018 host/<IP_ADDRESS>:55030 Bad compression stub (swap) decompression header byte: 42
openvpn_1  | Mon Oct 15 02:59:13 2018 host/<IP_ADDRESS>:55030 Bad compression stub (swap) decompression header byte: 42
openvpn_1  | Mon Oct 15 02:59:23 2018 host/<IP_ADDRESS>:55030 Bad compression stub (swap) decompression header byte: 42
openvpn_1  | Mon Oct 15 02:59:33 2018 host/<IP_ADDRESS>:55030 Bad compression stub (swap) decompression header byte: 42
openvpn_1  | Mon Oct 15 02:59:43 2018 host/<IP_ADDRESS>:55030 Bad compression stub (swap) decompression header byte: 42
openvpn_1  | Mon Oct 15 02:59:53 2018 host/<IP_ADDRESS>:55030 Bad compression stub (swap) decompression header byte: 42

Pinning the image to kylemanna/openvpn:2.3 in docker-compose.yml resolved this issue. I tried my hand at fixing the generated client / server config, but I am a real novice with OpenVPN and didn't get anywhere.

adding comp-lzo no to docker-for-mac.ovpn fix this issue


DJB ciphers for JCA based off Bouncycastle.

There's at least a small use case for people using this on the JVM that don';t wanna go the JNI route

Closed by #130


Sort Credit

In progress

Codecov Report

Merging #79 (24e36b1) into master (dc820e7) will increase coverage by 0.45%.
The diff coverage is 70.00%.

@@             Coverage Diff              @@
##             master      #79      +/-   ##
============================================
+ Coverage     67.67%   68.12%   +0.45%
- Complexity      513      528      +15
============================================
  Files            89       92       +3
  Lines          1717     1754      +37
  Branches        194      200       +6
============================================
+ Hits           1162     1195      +33
  Misses          472      472
- Partials         83       87       +4

Impacted Files
Coverage Δ

src/main/java/seedu/address/model/member/Tier.java
0.00% <0.00%> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
31.03% <0.00%> (ø)

...c/main/java/seedu/address/model/member/Credit.java
70.00% <70.00%> (ø)

.../seedu/address/logic/parser/ListCommandParser.java
75.00% <75.00%> (ø)

...c/main/java/seedu/address/model/member/Member.java
83.33% <77.77%> (-0.23%)
:arrow_down:

...java/seedu/address/logic/commands/EditCommand.java
96.15% <100.00%> (+0.10%)
:arrow_up:

...java/seedu/address/logic/commands/ListCommand.java
100.00% <100.00%> (ø)

...a/seedu/address/logic/parser/AddCommandParser.java
69.69% <100.00%> (+0.94%)
:arrow_up:

...ava/seedu/address/logic/parser/EzFoodieParser.java
84.61% <100.00%> (ø)

.../java/seedu/address/storage/JsonAdaptedMember.java
100.00% <100.00%> (+2.85%)
:arrow_up:

... and 2 more

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 dc820e7...24e36b1. Read the comment docs.


[Object] How to determine whether an ObjectID is a certain type of Object

When we get an Object ID, there seems to be no way to get the relationship between the ID and the Object type.
Currently it can only be determined through borrow:
public fun assert_collection_exist_of_id(collectionID: ObjectID, ctx: &mut Context){
        assert!( context::exist_object(ctx, collectionID), ECollectionNotExist);
        context::borrow_object<Collection>(ctx,collectionID);
    }

We may need a function to determine whether the ID is of a certain type:
function signature:
public fun check<T>(ctx: &mut Context, objectid: ObjectID): bool

use:
   context::check<T>(ctx, ObjectID);

exist_object only cares about the ID, and does not care about the Type.
We can make the exist_object care the Type, but
If object_id exists but not the type T, should exist_object<T>(object_id) return false?

exist_object only cares about the ID, and does not care about the Type.
We can make the exist_object care the Type, but
If object_id exists but not the type T, should exist_object<T>(object_id) return false?

Would it be better to provide two functions that can be combined by user?

exist_object only cares about the ID, and does not care about the Type.
We can make the exist_object care the Type, but
If object_id exists but not the type T, should exist_object<T>(object_id) return false?

Would it be better to provide two functions that can be combined by user?

From a usage perspective, exist_object(object_id) should be provided
Because users should know what type their Object is

Would it be better to provide two functions that can be combined by user?

How to name it? It is too complex for the user. We need to decide by the scenario.

In the Table case, the user only cares about if the key exists and does not care about the value Type. Because the user will check if the key exists and then add the key-value pair. If the raw_table::contains(key) care about the value type, will cause an error.

In the Object case, the ObjectID is generated via the system. The user can not construct the ObjectID, so the exist_object<T>(object_id) can care about the value type. But the raw_table implemention needs to refactor.

How about private a native function raw_table::borrow_option<T>(key):&Option<T>? and implement the contains function in Move.

The key_layout is for serializing the Key to vec<u8>, and putting it in  content: BTreeMap<Vec<u8>, TableRuntimeValue>. The value_layout in TableRuntimeValue.

use exists_object_with_type<T: key>(object_id: ObjectID): bool
https://github.com/rooch-network/rooch/blob/85b9502e307cee0d7ecc3f51e2b7d07ea7da2e6b/frameworks/moveos-stdlib/sources/object.move#L235-L237


Why is createEntity mutable?

Do you want to request a feature or report a bug?
Question/bug
What is the current behavior?
Calling contentState.createEntity actually modifies contentState object instead of just returning a new one.  Here is a simple fiddle: https://jsfiddle.net/FredyCr/32vo35tk/2/
What is the expected behavior?
I guess it's not a big deal, it's just little bit confusing given that almost every other operation is immutable.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
Working with the latest 0.10.1, not sure about previous versions.

That is confusing - in Draft v0.11.0 it will be immutable, and here is the reason it is quirky right now:

Originally the 'Entity' creation/deletion API was global and mutable, separate from contentState.
This was inconsistent and we decided to move it to an Immutable store inside of contentState. But to temporarily support both the old and new API, for an easy upgrade, in Draft v.0.10.0 we added the new API but under the hood call the old mutable Entity API.
In Draft 0.11.0 we will delete the old mutable Entity API and swap in the new immutable one under the hood of the new contentState API.

For more context see https://github.com/facebook/draft-js/issues/839 and https://draftjs.org/docs/v0-10-api-migration.html#content
It would be nice to clarify this in the API migration guide and docs. Would you like to take a shot at it @FredyC ?

Thanks for clarification @flarnie, it makes complete sense. I guess the confusion comes mainly from examples where you can see const contentStateWithEntity = contentState.createEntity(...). Maybe avoiding that assignment to a new variable could be enough? That way it would be clear, that nothing new is returned thus mutation is expected.
What's actual release plan for 0.11.0? Looking at the branch, it seems kinda stuck there, latest change is 4 months old.
In my opinion, it's probably not worth it do an extensive update to docs. I can create PR to update that confusing piece of code in examples. What do you think?


nuxt3: resolver.resolveModule is not a function

Thanks for this module. It makes life so much easier! I tried to use it in with nuxt3 beta, but (as expected) it's not working out of the box. Is there a plan to make this module nuxt3 ready? Thanks!
Here's what I get when using it with sass and sass-loader:
Fresh nuxt3 beta install (3.0.0-27235451.ece0e01)
Mac OSX
Node: v14.17.6
yarn dev -o
Cannot start nuxt:  resolver.resolveModule is not a function
at node_modules/@nuxtjs/style-resources/lib/module.js:35:43
at Array.reduce ()
at node_modules/@nuxtjs/style-resources/lib/module.js:34:42
at Array.reduce ()
at retrieveStyleArrays (node_modules/@nuxtjs/style-resources/lib/module.js:32:25)
at Object.nuxtStyledResources (node_modules/@nuxtjs/style-resources/lib/module.js:50:60)
at installModule (node_modules/@nuxt/kit/dist/index.mjs:1196:17)
at initNuxt (node_modules/nuxt3/dist/index.mjs:817:11)
at async load (node_modules/nuxi/dist/chunks/dev.mjs:6763:9)
at async Object.invoke (node_modules/nuxi/dist/chunks/dev.mjs:6794:5)
✔ Generated nuxt.d.ts

With Nuxt 3 this module still is not supported. Use the vite config property with preprocessorOptions option:
vite: {
    css: {
        preprocessorOptions: {
            scss: {
                additionalData: '@import "@/assets/scss/global.scss";',
            },
        },
    },
}

Source: https://vite.nuxtjs.org/misc/common-issues#styleresources

@designbydc Thanks, it works.

you can also pass the file path directly to the css option on the nuxt.config.ts file!
{
    css: [
<EMAIL_ADDRESS>    ]
}

reference

For anyone using webpack with Nuxt 3 or Nuxt Bridge, I was able to modify the plugin to use @nuxt/kit. I don't have the bandwidth to formalize this as a pull request, but I did make a gist with some directions on how to install it. The good news is that I was able to test it using both Nuxt 3 and Nuxt Bridge and everything appears to work without a hitch.
https://gist.github.com/volkipp/56655a3743bd7ebab57a6666833f3ec2
With a little effort you should also be able to make this module add to the vite preprocessorOptions  as well.  Hopefully someone here can use this as a foundation to make a formal merge request.
Cheers! 🍻

I had the same issue.
I wanted to use sass-mq in my Nuxt project. Here is my code:
// src/assets/styles/mq.scss
@use '~sass-mq' as *;
// or, @use '../../../node_modules/sass-mq' as *;
// I tried both, but neither of them succeeded.

// nuxt.config.ts
modules: [
  '@/modules/style-resources'
],
styleResources: {
  scss: ['assets/styles/mq.scss']
}

// src/pages/index.vue
.hoge {
  @include mq($from mobile) {/* */}
}

It says Undefined mixin.

 This worked:
- additionalData: '@import "@/assets/scss/global.scss";',
+ additionalData: '@use "path/to/file.scss" as *;',

stackoverflow

I have created a style-resources-module for Nuxt 3. (It doesn't support Bridge yet, though.)
Please use it if you like.
https://github.com/wattanx/style-resources-module

Will track Nuxt 3 support here https://github.com/nuxt-community/style-resources-module/issues/213 :)


Support icons in build order descriptions

New feature "notes" per build order section that allow icons IMO makes this request obsolete.


Fix policies to work with the container-selinux > 2.189.0

https://github.com/k3s-io/k3s-selinux/issues/36
1- Add policy dir for slemicro with requirement of container-selinux < 2.191
2- Add policy dir for coreos with requirement of container-selinux >= 2.191
3- Fix microos policy to remove the conflict and add  requirement of container-selinux >= 2.191
4- Add requirement for container-selinux < 2.191 for centos8 policy

Is there anything internal that's blocking this?


Set up on Jetson Nano/Xavier NX

Set up issue
Hi there,
I tried to create appropriate labels for the specific issue that I'm experiencing, but I couldn't find a way to put the proper tags, so i apologize in advance.
I’m currently trying to set up Pytorch Lightning on Jetson Nano/Jetson Xavier NX by building from source. So far, I have tried following this thread here: #695
The requirements.txt has been changed and no longer has torchvision and scikit-learn as one of the requirements. However, it seems to seek a torch version>=1.4 as a result of torchmetrics>=0.2.0 (within requirements.txt). My Jetson even has torch 1.8.0 and torchvision in its pip3 package manager. I was wondering if anyone has successfully set Pytorch Lightning up on ARM64's new requirement layout. Thanks!
Is there something I’m missing? I have also tried running setup.py to no avail. Thanks!

Expected behavior
My pip install attempt:

my pip install requirements attempt:

my pip list:

Environment
This is not a script bug as I'm only having trouble with setup using the pip package manager on Jetson/ARM64. Once again, I'm sorry for the tags!

PyTorch Version (e.g., 1.0): 1.8.0
OS (e.g., Linux): Linux
How you installed PyTorch (conda, pip, source): pip
Build command you used (if compiling from source):  pip3 install pytorch-lighting/pip3 install -r requirements.txt
Python version: 3.6.9
CUDA/cuDNN version: CUDA 10.2, cuDNN 8.0.0
GPU models and configuration:
Any other relevant information:

Additional context

Hi,
I actually never tried to set up Pytorch Lightning directly on a Jetson but people are usually more interested in the deployment side with such devices. If this is your end goal, I suggest you look into this project https://github.com/neo-ai/neo-ai-dlr.
I had a few issues compiling on sagemaker neo as a pytorch model so I suggest you convert your model to .onnx first. Depending on the Pytorch Lightning version you're using, you may also face issues with DLR, in the worst case scenario, I suggest you convert your Pytorch Lightning model into to a classic pytorch one once trained (you mainly need to slightly modify the state dictionary).
This is how I personally deploy on Jetson devices from Pytorch Lightning modules. If this is what you're looking for, I would be happy to share more details.

orch Lightning directly on a Jetson but people are usually more interested in the deployment side with such devices. If

Thank you for the response! But I have already successfully deployed with ONNX and Libtorch C++ on the Jetson Xavier. Now, I  specifically need to have the option of training on it. Thank you for the offer and project reference though, I'll definitely take a look!

I have fixed the issue but there are still some potential questions for future ARM64 developers that may be important. I may explore this question further.
The problem seemed to be that either the torch version that I possessed was not 1.4.0, or that I needed to use pip instead of pip3. For some reason, pip installed for both pip python 2 and pip3. I would invite other people to evaluate this further. This is a rundown of my documentation on the process, and will be subject to change should future updates to this library, and Jetson Hardware be put into place:
Pytorch Lightning Setup on Jetson Xavier NX
The general theme seems that we need to install pytorch lightning with the Pip package manager instead of pip3
and/or that we need to have torch 1.4.0 with its corresponding torchvision in order to pass the torch>=1.4 requirement
Not sure which, but it seemsl ike having both also works

1. We need to retrieve the Pytorch Variant 1.4.0 and torchvision 0.5.0 (Torch needs to bne >=1.4 but it seems 1.4.0 may be necessary). Prior to this, we already possessed pip3 and a torch and torchvision installation corresponding to that.
$ wget https://nvidia.box.com/shared/static/1v2cc4ro6zvsbu0p8h6qcuaqco1qcsif.whl -O torch-1.4.0-cp27-cp27mu-linux_aarch64.whl

$ git clone --branch v0.5.0 https://github.com/pytorch/vision torchvision   # see below for version of torchvision to download

2. We will need both pip and pip3 to install pytorch lightning
$ sudo apt-get update
$ sudo apt-get install libhdf5-serial-dev hdf5-tools libhdf5-dev zlib1g-dev zip libjpeg8-dev liblapack-dev libblas-dev gfortran
$ sudo apt-get install python-pip
$ sudo pip3 install -U pip testresources setuptools==49.6.0 # This step wasn't necessary but was done during the installation process for python 2 pip

3. Once we have the pip package manager, we need to install torch 1.4.0 on out python 2 environment. We also need to edit the Requirements.txt within pytorch-lightning environment
$ cd torchvision
$ export BUILD_VERSION=0.5.0
$ python3 setup.py install --user
$ cd path/to/pytorch-lightning

open requirements.txt..
Comment out the torch>=1.4 constraint as follows:
numpy>=1.17.2
#torch>=1.4 <---------------------------------------------------------------
future>=0.17.1  # required for builtins in setup.py
tqdm>=4.41.0
PyYAML>=5.1,<=5.4.1
fsspec[http]>=2021.4.0
tensorboard>=2.2.0, !=2.5.0  # 2.5.0 GPU CI error: 'Couldn't build proto file into descriptor pool!'
torchmetrics>=0.2.0
pyDeprecate==0.3.0
packaging

4. Install (The pip install seems to also install for pip3 manager)
$ pip install pytorch-lightning # Valid for both pip and pip3

5. We can continue to verify with pip list
$ pip3 list
$ pip list

It's difficult to screencap these results using shutter with highlighted similarities, but your pip and pip3 list should look the same with the following and the same versions:

Sources
Pytorch and Torchvision installation for Python 2 and 3:
https://forums.developer.nvidia.com/t/pytorch-for-jetson-version-1-8-0-now-available/72048
Python 2 pip installation:
https://docs.nvidia.com/deeplearning/frameworks/install-tf-jetson-platform/index.html
Pytorch Lightning forum post (seems correct to a degree but non-working for us):
https://forums.developer.nvidia.com/t/pytorch-lightning-set-up-on-jetson-nano-xavier-nx/177329
Pytorch Lightning installation on Jetson Xavier NX - USAEng, Note.com:


pkg/report: ignore finish_wait frame

Codecov Report

Merging #1347 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1347   +/-   ##
=======================================
  Coverage   57.76%   57.76%
=======================================
  Files         131      131
  Lines       24687    24687
=======================================
  Hits        14260    14260
  Misses       9752     9752
  Partials      675      675

Impacted Files
Coverage Δ

pkg/report/linux.go
83.65% <ø> (ø)
:arrow_up:

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 b8ceabf...e2df94b. Read the comment docs.


fix: hotkeys storage between studies and truncated patient names

Hotkeys doesn't get reset between studies
Patient name truncation fix

LGTM


Analyzer crashed

Analyzer Feedback from IntelliJ
Version information

IDEA AI-191.8<IP_ADDRESS>10548
2.7.0-dev.2.1
AI-191.8<IP_ADDRESS>10548, JRE 1.8.0_202-release-1483-b03x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1920x1080

Exception
Dart analysis server, SDK version 2.7.0-dev.2.1, server version 1.27.4, FATAL error: NoSuchMethodError: The getter 'isEof' was called on null.
Receiver: null
Tried calling: isEof
#0      Driver._captureExceptions.errorFunction (package:analysis_server/src/server/driver.dart:723:7)
#1      _CustomZone.handleUncaughtError (dart:async/zone.dart:1005:19)
#2      _CustomZone.runGuarded (dart:async/zone.dart:927:7)
#3      _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:965:23)
#4      _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#5      _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#6      _Timer._runTimers (dart:isolate-patch/timer_impl.dart:393:30)
#7      _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:418:5)
#8      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:174:12)

For additional log information, please append the contents of
file://C:\Users\joseh\AppData\Local\Temp\report.txt.

Thanks for reporting this issue! This was previously reported in #40223. Please follow along there.

Duplicate of #40223


Add dv locale

Adds locale and tests for Dhivehi/Thaana language.

Thanks for working on this! It looks good, can you please translate the escape sequences to real characters. All languages use native characters (javascript supports those). These are "easy" to read by "english" speaking people, but when you're copy-paste-searching you'll find nothing.

No problem. Done!

Merged in 19536b694678c724465abf1d94088e53c9912d30


improve actions + package toml

improve github actions

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (900f40d) to head (072320b).
Report is 24 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #14   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines           47        47
=========================================
  Hits            47        47

Flag
Coverage Δ

unittests
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Tree is not updated when a script makes changes to translated names

Clicking/selecting something in the tree immediately updates it, however

Fixed in latest build (2.0.6173)


Program runs without errors

Reading error messages carefully will help you figure out how to fix this problem
problems :

open parentheses
strings without "
and bad imports

Thanks brother , learned many new things in Python  through this @saadati944


maximum upload specified(1818091 bytes) has been reached error

When uploading a new file to vimeo
video_uri = v.upload(folder_path + board_type + str(n) + '.mp4', data={'name': hub_title + data['name'], 'description': data['notes']})
I always get the following error:
1818091 bytes uploaded ...
maximum upload specified(1818091 bytes) has been reached
What's going wrong?
Thanks,
Francesco

What you're seeing is just debug from the upload process. If you print out video_uri, you should have a URI from your uploaded video.
Example from our /example/upload.py:
Uploading: /Users/erunion/Desktop/VID_264410812_104045_324.mp4
672111 bytes uploaded ...
maximum upload specified(672111 bytes) has been reached
"/Users/erunion/Desktop/VID_264410812_104045_324.mp4" has been uploaded to https://vimeo.com/255841076
The title and description for /videos/255841076 has been edited.
The transcode status for /videos/255841076 is: in_progress


IDVA6-1153 fix flickering issue

Link to Jira:
https://companieshouse.atlassian.net/browse/IDVA6-1153
Changes:

Unnecessary font-face removed
Unnecessary link to govuk-frontend css file removed

CI: No security warnings found


How to stop an event

I am having an issue with stopping the monitor events after creating an instance data.instance = new Monitor(). The infrastructure of my application requires me to have many instances saved into an array of objects so I can detach these events once I need to. So far I tried removing the instance itself to stop the events but they are being executed even after the deletion of the instance.
data.instance = new Monitor({
  website: site.url,
  title: site.name,
  interval: site.interval,
  expect: {
    statusCode: site.statusCode
  }
});

setEvents(data.instance, site) // adding the monitor events here

monitors.push(data);

Here I'm trying to remove the instance to stop the events:
// looping through `monitors`

delete monitor.instance;

any help would be appreciated, thanks.

Hi @the94air , I think you need to stop the monitor before removing it.
Try doing this:
let monitor = monitors.find(monitor => monitor.instance. website === 'website url here');

monitor.instance.stop();
delete monitor.instance;

Hi @the94air , I think you need to stop the monitor before removing it.
Try doing this:
let monitor = monitors.find(monitor => monitor.instance. website === 'website url here');

monitor.instance.stop();
delete monitor.instance;

Oh, that's great. Thanks for the fast response. I have read the source code but I wasn't aware enough of how prototypes work. it's crystal clear now.
https://github.com/qawemlilo/ping-monitor/blob/master/lib/monitor.js#L171
Documenting this on the README is going to be so helpful :smile:. Thanks for help :smiley:

Oh, that's great. Thanks for the fast response. I have read the source code but I wasn't aware enough of how prototypes work. it's crystal clear now.
https://github.com/qawemlilo/ping-monitor/blob/master/lib/monitor.js#L171
Documenting this on the README is going to be so helpful :smile:. Thanks for help :smiley:


Is there an option to disable time?

Something like <datetimepicker show-time="false"></datetimepicker>

Yes, there is a way to disable time (see the Readme).

Sorry, I don't find it. What is the name of the attribute?

readonly-time disables the time, if you want to remove it completely use datepicker from Angular UI

You can also use the hidden-time property on this directive: http://plnkr.co/edit/zJOc40?p=preview


User listing and user creation is broken in Console

Describe the issue:

$subject
https://github.com/wso2/product-is/assets/41533942/d9feec6a-0199-46c6-9602-ffe10cb3a53a
No error logs on the terminal as well.
How to reproduce:

Refer to the screencast.
Expected behavior:

Users should be listed as expected and user creation should work as expected.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS 7 RC1 snapshot build
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

This was resolved at https://wso2.org/jenkins/job/products/job/product-is/4963/


pull request for e2e test at 12/20/2016 10:45:20

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


tmean does not work with multiple axis and limits option

Reproducing code example:
This works
from scipy.stats import tmean
tmean(np.arange(1000).reshape((10,10,10)), axis=1)

This does not
from scipy.stats import tmean
tmean(np.arange(1000).reshape((10,10,10)), limits=(1,10), axis=1)

---------------------------------------------------------------------------
AxisError                                 Traceback (most recent call last)
<ipython-input-180-91a3c8dfb8fc> in <module>()
----> 1 tmean(np.arange(1000).reshape((10,10,10)), limits=(1,10), axis=1)

~/anaconda3/lib/python3.5/site-packages/scipy/stats/stats.py in tmean(a, limits, inclusive, axis)
    543
    544     am = _mask_to_limits(a.ravel(), limits, inclusive)
--> 545     return am.mean(axis=axis)
    546
    547

~/anaconda3/lib/python3.5/site-packages/numpy/ma/core.py in mean(self, axis, dtype, out, keepdims)
   5157                                                    dtype=dtype, **kwargs)[()]
   5158         else:
-> 5159             dsum = self.sum(axis=axis, dtype=dtype, **kwargs)
   5160             cnt = self.count(axis=axis, **kwargs)
   5161             if cnt.shape == () and (cnt == 0):

~/anaconda3/lib/python3.5/site-packages/numpy/ma/core.py in sum(self, axis, dtype, out, keepdims)
   4994
   4995         _mask = self._mask
-> 4996         newmask = _check_mask_axis(_mask, axis, **kwargs)
   4997         # No explicit output
   4998         if out is None:

~/anaconda3/lib/python3.5/site-packages/numpy/ma/core.py in _check_mask_axis(mask, axis, keepdims)
   1821     kwargs = {} if keepdims is np._NoValue else {'keepdims': keepdims}
   1822     if mask is not nomask:
-> 1823         return mask.all(axis=axis, **kwargs)
   1824     return nomask
   1825

~/anaconda3/lib/python3.5/site-packages/numpy/core/_methods.py in _all(a, axis, dtype, out, keepdims)
     39
     40 def _all(a, axis=None, dtype=None, out=None, keepdims=False):
---> 41     return umr_all(a, axis, dtype, out, keepdims)
     42
     43 def _count_reduce_items(arr, axis):

AxisError: axis 1 is out of bounds for array of dimension 1

Looks like the axis gets lots in the masking/ravel operation, making it impossible to mention multiple axis at once.
Even putting limits=(None,None) or limits=(a,None) (for your favorite scalar a) does not work. Using only one value of axis instead of a tuple works (and of course I just now saw the docs says that, not that it mentions more than one is available).
New suggestion : make explicit that more than one axis is not supported and throw an error message/warning is people not reading the doc try to do it. Or support more than one axis.
Using no limits and multiple axis works somehow, probably because it won't mask anything, making it confusing.
Scipy/Numpy/Python version information:
Very old, but the master code is the same, I just checked.
import sys, scipy, numpy; print(scipy.__version__, numpy.__version__, sys.version_info)
1.1.0 1.14.6 sys.version_info(major=3, minor=5, micro=4, releaselevel='final', serial=0)

@samuelstjean This was reported again in gh-12106. Someone is working on a PR for that (gh-12143), so I'm going to add this information to gh-12106 and close this one. Thanks for reporting, and I'm sorry you didn't hear anything back about this until now.

Well as long as it's fixed it's fine, I'm not ure I would have been able to do it anyway


Bad practice with PhysicalResourceId

You should not use context.logStreamName in PhysicalResourceId response objects. The PhysicalResourceId should be akin to an ARN. If this value is changes during an UPDATE action, then the CloudFormation stack will send a DELETE signal to the Logical Resource in the template during the UPDATE_COMPLETE_CLEANUP_IN_PROGRESS lifecycle. If you do not change it, then the CLEANUP will not happen. In the presented example, this is fine, because you're just reading information, but if you were actually making resources, this would result in a lot of unexpected behavior.
Either change the implementation to use a unique request ID, or make a note to explain what the PhysicalResourceId actually does for custom resources.

@andrew-templeton Sorry, I have not been notified of this Issue for some reason.
I have updated the article to fit the code. The resources does not use this anymore because
of the issues that you write about. Also, because a new resource would be created on every update.


Jaeger Query throws Error 400 (Bad Request): all shards failed [type=search_phase_execution_exception]

Describe the bug
Jaeger UI throws Error 400 (Bad Request): all shards failed [type=search_phase_execution_exception] while all indices are GREEN. Collectors keep adding records but UI doesn't work or be able to show any traces.
To Reproduce
Steps to reproduce the behavior:
1.
2.
3.
Expected behavior
Jaeger UI should work as expected.
Screenshots
If applicable, add screenshots to help explain your problem.
Version (please complete the following information):

OS: Linux
Jaeger version: 1.21.0
Deployment: Kubernetes

What troubleshooting steps did you try?
Try to follow https://www.jaegertracing.io/docs/latest/troubleshooting/ and describe how far you were able to progress and/or which steps did not work.
Additional context
Indices are all green, ES queries work just fine. However Jaeger UI doesn't render any results.

Collectors log 2021-01-09T02:08:20.952331746Z {"level":"debug","ts":1610158100.9485595,"caller":"app/span_processor.go:149","msg":"Span written to the storage by the collector","trace-id":"245aec81734c311e","span-id":"2b1dc897b7e5c9e4"} which looks like trace data is successfully written.
But trace data is failed at ES with ```
{"type": "server", "timestamp": "2021-01-09T02:40:31,248Z", "level": "INFO", "component": "o.e.a.b.TransportShardBulkAction", "cluster.name": "jaeger-db", "node.name": "jaeger-db-es-master-0", "message": "[jaeger-jaeger-span-2021-01-09][3] mapping update rejected by primary", "cluster.uuid": "4PexpvDoQ5iYz8pUxLR6Ng", "node.id": "7Vj65I0aTkKIBriEnFCHJw" ,
"stacktrace": ["java.lang.IllegalArgumentException: mapper [flags] cannot be changed from type [integer] to [long]",
I believe,  https://github.com/jaegertracing/jaeger/blob/master/plugin/storage/es/mappings/jaeger-span-7.json#L58 must be long instead of integer.

Collectors log 2021-01-09T02:08:20.952331746Z {"level":"debug","ts":1610158100.9485595,"caller":"app/span_processor.go:149","msg":"Span written to the storage by the collector","trace-id":"245aec81734c311e","span-id":"2b1dc897b7e5c9e4"} which looks like trace data is successfully written.
But trace data is failed at ES with ```
{"type": "server", "timestamp": "2021-01-09T02:40:31,248Z", "level": "INFO", "component": "o.e.a.b.TransportShardBulkAction", "cluster.name": "jaeger-db", "node.name": "jaeger-db-es-master-0", "message": "[jaeger-jaeger-span-2021-01-09][3] mapping update rejected by primary", "cluster.uuid": "4PexpvDoQ5iYz8pUxLR6Ng", "node.id": "7Vj65I0aTkKIBriEnFCHJw" ,
"stacktrace": ["java.lang.IllegalArgumentException: mapper [flags] cannot be changed from type [integer] to [long]",
I believe,  https://github.com/jaegertracing/jaeger/blob/master/plugin/storage/es/mappings/jaeger-span-7.json#L58 must be long instead of integer.

Query doesn't work when I create templates for service and span:
{
  "index_patterns": "*jaeger-service-*",
  "settings":{
    "index.number_of_shards": 5,
    "index.number_of_replicas": 1,
    "index.mapping.nested_fields.limit":50,
    "index.requests.cache.enable":true
  },
  "mappings":{
    "dynamic_templates":[
      {
        "span_tags_map":{
          "mapping":{
            "type":"keyword",
            "ignore_above":256
          },
          "path_match":"tag.*"
        }
      },
      {
        "process_tags_map":{
          "mapping":{
            "type":"keyword",
            "ignore_above":256
          },
          "path_match":"process.tag.*"
        }
      }
    ],
    "properties":{
      "traceID":{
        "type":"keyword",
        "ignore_above":256
      },
      "parentSpanID":{
        "type":"keyword",
        "ignore_above":256
      },
      "spanID":{
        "type":"keyword",
        "ignore_above":256
      },
      "operationName":{
        "type":"keyword",
        "ignore_above":256
      },
      "startTime":{
        "type":"long"
      },
      "startTimeMillis":{
        "type":"date",
        "format":"epoch_millis"
      },
      "duration":{
        "type":"long"
      },
      "flags":{
        "type":"long"
      },
      "logs":{
        "type":"nested",
        "dynamic":false,
        "properties":{
          "timestamp":{
            "type":"long"
          },
          "fields":{
            "type":"nested",
            "dynamic":false,
            "properties":{
              "key":{
                "type":"keyword",
                "ignore_above":256
              },
              "value":{
                "type":"keyword",
                "ignore_above":256
              },
              "tagType":{
                "type":"keyword",
                "ignore_above":256
              }
            }
          }
        }
      },
      "process":{
        "properties":{
          "serviceName":{
            "type":"keyword",
            "ignore_above":256
          },
          "tag":{
            "type":"object"
          },
          "tags":{
            "type":"nested",
            "dynamic":false,
            "properties":{
              "key":{
                "type":"keyword",
                "ignore_above":256
              },
              "value":{
                "type":"keyword",
                "ignore_above":256
              },
              "tagType":{
                "type":"keyword",
                "ignore_above":256
              }
            }
          }
        }
      },
      "references":{
        "type":"nested",
        "dynamic":false,
        "properties":{
          "refType":{
            "type":"keyword",
            "ignore_above":256
          },
          "traceID":{
            "type":"keyword",
            "ignore_above":256
          },
          "spanID":{
            "type":"keyword",
            "ignore_above":256
          }
        }
      },
      "tag":{
        "type":"object"
      },
      "tags":{
        "type":"nested",
        "dynamic":false,
        "properties":{
          "key":{
            "type":"keyword",
            "ignore_above":256
          },
          "value":{
            "type":"keyword",
            "ignore_above":256
          },
          "tagType":{
            "type":"keyword",
            "ignore_above":256
          }
        }
      }
    }
  }
}

{
        "order": 0,
        "index_patterns": [
            "*jaeger-span-*"
        ],
        "settings": {
            "index": {
                "mapping": {
                    "nested_fields": {
                        "limit": "50"
                    }
                },
                "requests": {
                    "cache": {
                        "enable": "true"
                    }
                },
                "number_of_shards": "5",
                "number_of_replicas": "1"
            }
        },
        "mappings": {
            "dynamic_templates": [
                {
                    "span_tags_map": {
                        "path_match": "tag.*",
                        "mapping": {
                            "ignore_above": 256,
                            "type": "keyword"
                        }
                    }
                },
                {
                    "process_tags_map": {
                        "path_match": "process.tag.*",
                        "mapping": {
                            "ignore_above": 256,
                            "type": "keyword"
                        }
                    }
                }
            ],
            "properties": {
                "traceID": {
                    "ignore_above": 256,
                    "type": "keyword"
                },
                "process": {
                    "properties": {
                        "tag": {
                            "type": "object"
                        },
                        "serviceName": {
                            "ignore_above": 256,
                            "type": "keyword"
                        },
                        "tags": {
                            "dynamic": false,
                            "type": "nested",
                            "properties": {
                                "tagType": {
                                    "ignore_above": 256,
                                    "type": "keyword"
                                },
                                "value": {
                                    "ignore_above": 256,
                                    "type": "keyword"
                                },
                                "key": {
                                    "ignore_above": 256,
                                    "type": "keyword"
                                }
                            }
                        }
                    }
                },
                "startTimeMillis": {
                    "format": "epoch_millis",
                    "type": "date"
                },
                "references": {
                    "dynamic": false,
                    "type": "nested",
                    "properties": {
                        "traceID": {
                            "ignore_above": 256,
                            "type": "keyword"
                        },
                        "spanID": {
                            "ignore_above": 256,
                            "type": "keyword"
                        },
                        "refType": {
                            "ignore_above": 256,
                            "type": "keyword"
                        }
                    }
                },
                "flags": {
                    "type": "long"
                },
                "operationName": {
                    "ignore_above": 256,
                    "type": "keyword"
                },
                "parentSpanID": {
                    "ignore_above": 256,
                    "type": "keyword"
                },
                "tags": {
                    "dynamic": false,
                    "type": "nested",
                    "properties": {
                        "tagType": {
                            "ignore_above": 256,
                            "type": "keyword"
                        },
                        "value": {
                            "ignore_above": 256,
                            "type": "keyword"
                        },
                        "key": {
                            "ignore_above": 256,
                            "type": "keyword"
                        }
                    }
                },
                "spanID": {
                    "ignore_above": 256,
                    "type": "keyword"
                },
                "duration": {
                    "type": "long"
                },
                "startTime": {
                    "type": "long"
                },
                "tag": {
                    "type": "object"
                },
                "logs": {
                    "dynamic": false,
                    "type": "nested",
                    "properties": {
                        "fields": {
                            "dynamic": false,
                            "type": "nested",
                            "properties": {
                                "tagType": {
                                    "ignore_above": 256,
                                    "type": "keyword"
                                },
                                "value": {
                                    "ignore_above": 256,
                                    "type": "keyword"
                                },
                                "key": {
                                    "ignore_above": 256,
                                    "type": "keyword"
                                }
                            }
                        },
                        "timestamp": {
                            "type": "long"
                        }
                    }
                }
            }
        },
        "aliases": {}
    }

Query doesn't work when I create templates for service and span:
{
  "index_patterns": "*jaeger-service-*",
  "settings":{
    "index.number_of_shards": 5,
    "index.number_of_replicas": 1,
    "index.mapping.nested_fields.limit":50,
    "index.requests.cache.enable":true
  },
  "mappings":{
    "dynamic_templates":[
      {
        "span_tags_map":{
          "mapping":{
            "type":"keyword",
            "ignore_above":256
          },
          "path_match":"tag.*"
        }
      },
      {
        "process_tags_map":{
          "mapping":{
            "type":"keyword",
            "ignore_above":256
          },
          "path_match":"process.tag.*"
        }
      }
    ],
    "properties":{
      "traceID":{
        "type":"keyword",
        "ignore_above":256
      },
      "parentSpanID":{
        "type":"keyword",
        "ignore_above":256
      },
      "spanID":{
        "type":"keyword",
        "ignore_above":256
      },
      "operationName":{
        "type":"keyword",
        "ignore_above":256
      },
      "startTime":{
        "type":"long"
      },
      "startTimeMillis":{
        "type":"date",
        "format":"epoch_millis"
      },
      "duration":{
        "type":"long"
      },
      "flags":{
        "type":"long"
      },
      "logs":{
        "type":"nested",
        "dynamic":false,
        "properties":{
          "timestamp":{
            "type":"long"
          },
          "fields":{
            "type":"nested",
            "dynamic":false,
            "properties":{
              "key":{
                "type":"keyword",
                "ignore_above":256
              },
              "value":{
                "type":"keyword",
                "ignore_above":256
              },
              "tagType":{
                "type":"keyword",
                "ignore_above":256
              }
            }
          }
        }
      },
      "process":{
        "properties":{
          "serviceName":{
            "type":"keyword",
            "ignore_above":256
          },
          "tag":{
            "type":"object"
          },
          "tags":{
            "type":"nested",
            "dynamic":false,
            "properties":{
              "key":{
                "type":"keyword",
                "ignore_above":256
              },
              "value":{
                "type":"keyword",
                "ignore_above":256
              },
              "tagType":{
                "type":"keyword",
                "ignore_above":256
              }
            }
          }
        }
      },
      "references":{
        "type":"nested",
        "dynamic":false,
        "properties":{
          "refType":{
            "type":"keyword",
            "ignore_above":256
          },
          "traceID":{
            "type":"keyword",
            "ignore_above":256
          },
          "spanID":{
            "type":"keyword",
            "ignore_above":256
          }
        }
      },
      "tag":{
        "type":"object"
      },
      "tags":{
        "type":"nested",
        "dynamic":false,
        "properties":{
          "key":{
            "type":"keyword",
            "ignore_above":256
          },
          "value":{
            "type":"keyword",
            "ignore_above":256
          },
          "tagType":{
            "type":"keyword",
            "ignore_above":256
          }
        }
      }
    }
  }
}

{
        "order": 0,
        "index_patterns": [
            "*jaeger-span-*"
        ],
        "settings": {
            "index": {
                "mapping": {
                    "nested_fields": {
                        "limit": "50"
                    }
                },
                "requests": {
                    "cache": {
                        "enable": "true"
                    }
                },
                "number_of_shards": "5",
                "number_of_replicas": "1"
            }
        },
        "mappings": {
            "dynamic_templates": [
                {
                    "span_tags_map": {
                        "path_match": "tag.*",
                        "mapping": {
                            "ignore_above": 256,
                            "type": "keyword"
                        }
                    }
                },
                {
                    "process_tags_map": {
                        "path_match": "process.tag.*",
                        "mapping": {
                            "ignore_above": 256,
                            "type": "keyword"
                        }
                    }
                }
            ],
            "properties": {
                "traceID": {
                    "ignore_above": 256,
                    "type": "keyword"
                },
                "process": {
                    "properties": {
                        "tag": {
                            "type": "object"
                        },
                        "serviceName": {
                            "ignore_above": 256,
                            "type": "keyword"
                        },
                        "tags": {
                            "dynamic": false,
                            "type": "nested",
                            "properties": {
                                "tagType": {
                                    "ignore_above": 256,
                                    "type": "keyword"
                                },
                                "value": {
                                    "ignore_above": 256,
                                    "type": "keyword"
                                },
                                "key": {
                                    "ignore_above": 256,
                                    "type": "keyword"
                                }
                            }
                        }
                    }
                },
                "startTimeMillis": {
                    "format": "epoch_millis",
                    "type": "date"
                },
                "references": {
                    "dynamic": false,
                    "type": "nested",
                    "properties": {
                        "traceID": {
                            "ignore_above": 256,
                            "type": "keyword"
                        },
                        "spanID": {
                            "ignore_above": 256,
                            "type": "keyword"
                        },
                        "refType": {
                            "ignore_above": 256,
                            "type": "keyword"
                        }
                    }
                },
                "flags": {
                    "type": "long"
                },
                "operationName": {
                    "ignore_above": 256,
                    "type": "keyword"
                },
                "parentSpanID": {
                    "ignore_above": 256,
                    "type": "keyword"
                },
                "tags": {
                    "dynamic": false,
                    "type": "nested",
                    "properties": {
                        "tagType": {
                            "ignore_above": 256,
                            "type": "keyword"
                        },
                        "value": {
                            "ignore_above": 256,
                            "type": "keyword"
                        },
                        "key": {
                            "ignore_above": 256,
                            "type": "keyword"
                        }
                    }
                },
                "spanID": {
                    "ignore_above": 256,
                    "type": "keyword"
                },
                "duration": {
                    "type": "long"
                },
                "startTime": {
                    "type": "long"
                },
                "tag": {
                    "type": "object"
                },
                "logs": {
                    "dynamic": false,
                    "type": "nested",
                    "properties": {
                        "fields": {
                            "dynamic": false,
                            "type": "nested",
                            "properties": {
                                "tagType": {
                                    "ignore_above": 256,
                                    "type": "keyword"
                                },
                                "value": {
                                    "ignore_above": 256,
                                    "type": "keyword"
                                },
                                "key": {
                                    "ignore_above": 256,
                                    "type": "keyword"
                                }
                            }
                        },
                        "timestamp": {
                            "type": "long"
                        }
                    }
                }
            }
        },
        "aliases": {}
    }

@aug70 please provide the steps to reproduce this locally. FWIW, the integer type flags mapping has been around for 17 months so it's not obvious to me how this error came about.

@aug70 please provide the steps to reproduce this locally. FWIW, the integer type flags mapping has been around for 17 months so it's not obvious to me how this error came about.

hi @aug70.
I have the same issue as yours recently.
I found the reason is that we have two different versions jaeger collector at the same time, and I guessed the index mapping was created by older version of jaeger.
In my case, I upgrade all jaeger collectors then remove all previous indices, then it works.

hi @aug70.
I have the same issue as yours recently.
I found the reason is that we have two different versions jaeger collector at the same time, and I guessed the index mapping was created by older version of jaeger.
In my case, I upgrade all jaeger collectors then remove all previous indices, then it works.

That sounds odd. Would it happen during a regular upgrade from the older version to the new one as well? Would you need to delete indexes to use the newer collector? It should not be the case.

That sounds odd. Would it happen during a regular upgrade from the older version to the new one as well? Would you need to delete indexes to use the newer collector? It should not be the case.

@flf2ko it might be the case, because I had HotRod and my app creating indexes at the same time. I'm suspecting that's what caused this error. Unfortunately I have no access to the collectors, I had to have somebody to stop them so I could delete the indexes and restarted collectors. Problem solved after starting fresh. But it was an inconvenience.

Running into this again! Just upgraded to Helm Jaeger version 0.43.3 and jaeger 1.22.0
{"level":"error","ts":1617029142.5404692,"caller":"app/http_handler.go:435","msg":"HTTP handler, Internal Server Error","error":"search operations failed: elastic: Error 400 (Bad Request): all shards failed [type=search_phase_execution_exception]","stacktrace":"github.com/jaegertracing/jaeger/cmd/query/app.(*APIHandler).handleError\n\tgithub.com/jaegertracing/jaeger/cmd/query/app/http_handler.go:435\ngithub.com/jaegertracing/jaeger/cmd/query/app.(*APIHandler).getOperationsLegacy\n\tgithub.com/jaegertracing/jaeger/cmd/query/app/http_handler.go:167\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2042\ngithub.com/opentracing-contrib/go-stdlib/nethttp.MiddlewareFunc.func5\n\tgithub.com/opentracing-contrib/go-stdlib@v0.0.0-20190519235532-cf7a6c988dc9/nethttp/server.go:140\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2042\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2042\ngithub.com/gorilla/mux.(*Router).ServeHTTP\n\tgithub.com/gorilla/mux@v1.7.4/mux.go:210\ngithub.com/jaegertracing/jaeger/cmd/query/app.additionalHeadersHandler.func1\n\tgithub.com/jaegertracing/jaeger/cmd/query/app/additional_headers_handler.go:28\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2042\ngithub.com/gorilla/handlers.CompressHandlerLevel.func1\n\tgithub.com/gorilla/handlers@v1.5.1/compress.go:141\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2042\ngithub.com/gorilla/handlers.recoveryHandler.ServeHTTP\n\tgithub.com/gorilla/handlers@v1.5.1/recovery.go:78\nnet/http.serverHandler.ServeHTTP\n\tnet/http/server.go:2843\nnet/http.(*conn).serve\n\tnet/http/server.go:1925"}

@jpkrohling I don't know what other info I can provide you? Please remove the needs-info tag because there isn't anything else I can provide here...

@aug70 are you able to consistently reproduce this? If I just install Jaeger 1.22.0 using the current Helm charts on a minikube instance, will I face this issue?

@jpkrohling Yes I'm consistently reproducing this.

I may found the solution.
I created a mapping for elasticsearch index pattern jaeger-service-*
The mapping is changed from
{
    "mappings": {
        "_doc": {
            "properties": {
                "operationName": {
                    "type": "text",
                    "fields": {
                        "keyword": {
                            "type": "keyword",
                            "ignore_above": 256
                        }
                    }
                },
                "serviceName": {
                    "type": "text",
                    "fields": {
                        "keyword": {
                            "type": "keyword",
                            "ignore_above": 256
                        }
                    }
                }
            }
        }
    }
}

to
{
  "mappings": {
    "_doc": {
      "properties": {
        "operationName": {
          "type": "keyword"
        },
        "serviceName": {
          "type": "keyword"
        }
      }
    }
  }
}

, then it worked.
It could be caused by using a wildcard query on a text type field instead keyword type field.
In original mapping, we need to query on operationName.keyword instead of operationName key.

hmm..I found this error would happen when do a (wildcard) query on a text type field instead of keyword type.
I found that my elasticsearch used mapping from dynamic mapping, so it is not the same as
https://github.com/jaegertracing/jaeger/blob/master/plugin/storage/es/mappings/jaeger-span-7.json
The mapping would be something like following format, via dynamic mapping.
"operationName": {
  "type": "text",
  "fields": {
    "keyword": {
      "type": "keyword",
      "ignore_above": 256
    }
  }
}

In this case, the wildcard query should query on operationName.keyword instead of operationName.
It worked normally after I change to new mapping.
Not sure if this is the same case as your, @aug70, since I don't find any text type in your provided mapping above.

I think the Jaeger version between collectors and the rest of the system caused this error. I put a PR to upgrade collectors and problem is now solved.

Is it solved after upgrading to latest Jaeger version? Which version do I need to upgrade?

I also faced same issue.I have uninstalled jaeger and deleted jaeger indices and template and redeploy jaeger ,its started working.Mostly its happened when you change index name or shards number so very important step is to delete index template otherwise this error will come.


[9.x] Deprecation Test Improvements

throw deprecations exception only when running tests with --prefer-stable.
tests are failing now, and will starts to failed (on all builds) when Testbench Core 7.16.0 get tagged.

@crynobone I thought we already were treating deprecations as exceptions: https://github.com/laravel/framework/blob/9.x/phpunit.xml.dist#L6
This can definitely just go into the current test suite. No need for a separate workflow 👍

I thought we already were treating deprecations as exceptions

@driesvints Not in application tests that actually need to boot the framework. As Laravel boots, and HandleExceptions actually proxy those deprecations to a specific log channel, if any.
@crynobone Out of curiosity, can you point me to the exact code, on testbench, that modifies the behavior on HandleExceptions so deprecations actually get reported?

Testbench would bootstrap Orchestra\Testbench\Bootstrap\HandleExceptions  insteads of Laravel.

Hey @crynobone. I'm gonna take this one over and see if I can solve all issues. I think the right way to tackle prefer-lowest is to bump minimum versions. For anything we cannot solve through Composer we can use the already provided step here:
https://github.com/laravel/framework/blob/9.x/.github/workflows/tests.yml#L84

@crynobone I feel like we're still missing things here. For example, the first failing test I look at is:
1) Illuminate\Tests\Integration\Auth\ForgotPasswordTest::it_can_send_forgot_password_email
str_starts_with(): Passing null to parameter #1 ($haystack) of type string is deprecated

/home/runner/work/framework/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php:71
/home/runner/work/framework/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php:268
/home/runner/work/framework/framework/src/Illuminate/Auth/Passwords/PasswordBrokerManager.php:86
/home/runner/work/framework/framework/src/Illuminate/Auth/Passwords/PasswordBrokerManager.php:71
/home/runner/work/framework/framework/src/Illuminate/Auth/Passwords/PasswordBrokerManager.php:48
/home/runner/work/framework/framework/src/Illuminate/Support/Facades/Facade.php:338
/home/runner/work/framework/framework/tests/Integration/Auth/ForgotPasswordTest.php:53

But there's no str_starts_with call on that line. Is the real stack trace hidden somewhere?

Seems like it's the case in most tests: https://github.com/laravel/framework/actions/runs/3707093739/jobs/6283094947#step:9:159
1) Illuminate\Tests\Integration\Auth\ForgotPasswordWithoutDefaultRoutesTest::it_can_send_forgot_password_email_via_create_url_using
Use of "static" in callables is deprecated

/home/runner/work/framework/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php:71
/home/runner/work/framework/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php:266
/home/runner/work/framework/framework/vendor/fakerphp/faker/src/Faker/Provider/Base.php:357
/home/runner/work/framework/framework/vendor/fakerphp/faker/src/Faker/Provider/Base.php:408
/home/runner/work/framework/framework/vendor/fakerphp/faker/src/Faker/Provider/Base.php:423
/home/runner/work/framework/framework/vendor/fakerphp/faker/src/Faker/Provider/Internet.php:94
/home/runner/work/framework/framework/vendor/fakerphp/faker/src/Faker/Provider/Internet.php:48
/home/runner/work/framework/framework/vendor/fakerphp/faker/src/Faker/Generator.php:230
/home/runner/work/framework/framework/vendor/fakerphp/faker/src/Faker/Generator.php:287
/home/runner/work/framework/framework/vendor/fakerphp/faker/src/Faker/UniqueGenerator.php:48
/home/runner/work/framework/framework/vendor/orchestra/testbench-core/src/Factories/UserFactory.php:31
/home/runner/work/framework/framework/src/Illuminate/Database/Eloquent/Factories/Factory.php:446
/home/runner/work/framework/framework/src/Illuminate/Database/Eloquent/Factories/Factory.php:425
/home/runner/work/framework/framework/src/Illuminate/Database/Eloquent/Factories/Factory.php:409
/home/runner/work/framework/framework/src/Illuminate/Database/Eloquent/Concerns/GuardsAttributes.php:155
/home/runner/work/framework/framework/src/Illuminate/Database/Eloquent/Factories/Factory.php:408
/home/runner/work/framework/framework/src/Illuminate/Database/Eloquent/Factories/Factory.php:382
/home/runner/work/framework/framework/src/Illuminate/Database/Eloquent/Factories/Factory.php:276
/home/runner/work/framework/framework/tests/Integration/Auth/ForgotPasswordWithoutDefaultRoutesTest.php:78