Whiptail checkbox writing results to file.

Need to figure out how to output the whiptail checkbox results to a variable that can be used to loop through instead of whiptail writing the results to a file in install.sh. For the time being the file generated by whiptail is being manually deleted by the script when exiting the script.

This is a minor non issue which does not need addressed.

Try to redirect otputs:
sel=$(whiptail --checklist "Please pick one" 10 60 5 one one off two two on  3>&1 1>&2 2>&3);
(http://stackoverflow.com/questions/1970180/whiptail-how-to-redirect-output-to-environment-variable)


rename ZMIN/ZMAX into SEAICE_zMin/zMax

What changes does this PR introduce?
small change in variable names to avoid potential conflict, when seaice and kpp use the same variable names (zmin,zmax)
What is the current behaviour?
this addresses a small issue in #685
What is the new behaviour

zmin,zmax are now exclusive parameters in pkg/kpp.

Does this PR introduce a breaking change?
I hope not
Other information:
Suggested addition to tag-index
o pkg/seaice: rename ZMIN/ZMAX into SEAICE_ZMIN/ZMAX to avoid potential conflicts with kpp variables with the same name

I would like @Shreyas911 to have a look at this, but unfortunately I cannot make him a reviewer.

@mjlosch not that it really matters, but we could decide to write these 2 arrays in a more "MITgcm" style, like "SEAICE_zMin" and "SEAICE_zMax". What do you think ?

Hi @mjlosch, this looks very good to me—nothing to add.
Best,
Shreyas

@mjlosch  It seems that seaice_evp.F does not compile when SEAICE_ALLOW_CLIPZETA is defined, a missing update to line 299 there ?

@mjlosch I bumped into an other "name" issue in pkg/seaice:
The variable SWFracB in SEAICE.h has the same name as a local variable in apply_forcing.F (+ also in old version external_forcing.F). May be it could be renamed "SEAICE_SWFrac", with or without "B", and moved to SEAICE_PARAMS.h (instead of SEAICE.h) ?
I could be done here or in a different PR, as you prefer.

We can do that for consistency, although I am not quite sure if it is necessary: SEAICE.h is not included in apply_forcing.F, so that there shouldn't be a conflict. Having said that, the variable should really be a 2D field and S/R SWFRAC should return a 2D field that depends on the local turbidity conditions, which could be estimated from a BGC model. I know that this has been done in some BGC-MITgcm models, and we should provide the general capability for this. With this SWFracB should a global variable and not a parameter. That's why I would leave in SEAICE.h. So my suggestion is to rename the variable now for safety, keep in in SEAICE.h and then later in a separate PR replace the variable by a global SWFracB field (which would require changing the subroutine SWFrac as well).
Honestly, I do not know how the zmin/max duplicates could have gone unnoticed for such a long time. KPP and SEAICE headers are included in the same routines, aren't they? E.g in forward_step.F

@mjlosch I am not sure I fully agree with all the arguments to keep SWFracB in SEAICE.h, but the advantage to keep it there is that it involves less changes, so I am fine with this.
But renaming it is still useful, because apply_forcing.F could be customized (if needed) and who knows if some pkg/seaice variables might be part of this customization.

Note that the way SWFracB (now SEAICE_SWFrac) is computed in seaice_init_fixed.F is wrong for p-coordinates. My bad. Fix here or later? I prefer here. This will likely affect seaice_global.cs32x15.in_p (haven't tried yet).

@mjlosch If you feel like fixing this P-coords thing here, please do. I did noticed also that this was not consistent with apply_forcing.F but did not dig into seaice_growth.F to find out what was right.

Should I update the reference output for global_ocean.cs32x15.in_p (from reference platform) ?

yes, please.

From my side, this PR looks ready to be merged. @mjlosch do you agree ?
If yes, will merge it tomorrow, unless someone disagree.

But I forgot: it would be good to update this PR description (with fix for P-coords) as well as suggestion for tag-index addition.

@jm-c I updated the description and the tag-index suggestion. I think this can be merged now.


integrate rooted datapacks (GSI-504)

Added function to integrate rooted datapacks to generate embedded JSON compatible objects.

Depends on #7.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

41 of 46 (89.13%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 94.197%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/schemapack/integrate.py
40
45
88.89%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
698

Relevant Lines:
741

💛  - Coveralls

You need to update the service template files due to ghga-de/microservice-repository-template#184.

Thanks @Cito, ready for another round


chef-client run giving ssl error while push jobs client installation

Cookbook version
[5.1.1]
Chef-client version
[13.1.31]
Platform Details
[centos6]
Scenario:
[I am running chef-client from node install the push job client but getting SSL error as logs below:
Uploaded the push jobs and dependent cookbooks on chef server and Add the cookbook in runlist of node. Trying the command chef-client but not working. I know why this issue is coming.
This is coming because i am on my organization network where a certificate based auth mechanism on firewall, can anybody guide me either a way to skip that certificate or where to add that certificate on node/chef server/workstation etc.]
Steps to Reproduce:
[I don't think without such env we can replicate in local]
Expected Result:
[want the pushjobs client installed]
Actual Result:
[What actually happens after the reproduction steps? Include the error output or a link to a gist if possible
chef-client.txt
.]

Does this issue still exist? That looks like it was either an errant outage or you're node is subject to some sort of intercepting proxy.

If you are still experiencing this problem please reopen with additional details.


[WIP] Add grunt init to copy assets

@katelynnobrien
This branch should get you started.
If you create a web_external/assets directory, when you run grunt init (or npm install which calls grunt init) at the top level under your girder dir, this will copy any .png files you put in assets to the static built directory for minerva.
In a Javascript file, you need to pass the staticRoot to your jade template
    this.$el.html(minerva.templates.layoutHeader({
        staticRoot: girder.staticRoot
    }));

and in a jade template (that you passed in the staticRoot variable to) you could do
img(src="#{staticRoot}/built/plugins/minerva/assets/awesome-image.png")

Closing, this was included in #325.


Run native blocking code

I'm trying out shuttle for https://github.com/anacrolix/possum. In some tests that are multithreaded, I need to call in to rusqlite code which then calls into C code which blocks the calling thread. After lots of trial and error I think I discovered that shuttle is not using native threads under the hood but its own kind of green threading. This doesn't play well with calling into code that hasn't been instrumented with shuttle primitives.
How can I call into that code? I was going to create a wrapper that spawned a native thread to run blocking code in rusqlite, then wait on the result from a shuttle mpsc channel but then I realised I can't send the result into a shuttle channel from a thread that wasn't created by shuttle.

It sounds to me like this would work if you were to use a std::sync::mpsc channel to send results from the spawned thread to the main thread which is running under Shuttle. You would do the call to your wrapper, which would spawn a thread and give you a channel to block on. Your main thread would then block on the receiving end of the channel until the spawned thread is ready with the result. Does this work or am I missing something?

I don't think you can block on a std::sync::mpsc in shuttle, it will stall everything.
I ended up trying this:
https://github.com/anacrolix/possum/blob/a37c55a1c8a781c3dfd7e921e4088ba15b7f0fe2/src/concurrency/mod.rs#L32-L54
probably not ideal, but I do a non-blocking recv from a std::sync::mpsc channel, and tell shuttle to yield if it fails. It's essentially busy waiting, I hope shuttle's scheduler can handle this effectively. It does work though.


cauldron recipes does not work in latest forge version

Describe the bug
A clear and concise description of what the bug is, including expected behavior.

steps
place a cauldron above a magma block, fill it with water, then, after the water boils, drop 4 mushrooms.
expected result
mushroom soup is crafted
actual result
mushrooms are not processed

Screenshots or crash report (if relevant)
If applicable, add screenshots to help explain your problem.
Versions (please complete the following information):

Minecraft: 1.16.1 > 1.16.5**
FORGE: 36.1.32
Mantle: Mantle-1.16.5-1.6.109
Inspirations: Inspirations-1.16.5-<IP_ADDRESS>

Does it work if you right click the cauldron with the mushrooms? Dropping was never the main way to craft.

So water only "boils" when fire is placed under the cauldron. Other heat sources doesn't make it boil. I don't know if this is an expected feature but in 1.12.2 it was

Just to clarify. Doing right click with the recipe items rather than throwing them directly into the cauldron only works when water actually boils. That only happens when fire is below the cauldron.

Magma blocks never made it boil in Inspirations, that was an addon. Sounds to me like you assumed it was boiling when it was not. If you saw bubble particles, this is a bug, but otherwise this is misunderstanding mechanics.
Currently supported sources of boiling are fire and campfires.

thanks for the info. I'd mistake dynamic surrounding particles as boiling water :'))


BLOBs with text aren't shown in Value panel

System information:

Operating system (distribution) and version win 10 x64
DBeaver version 7.3.4 EA

Connection specification:

Database name and version Oracle 12

Describe the problem you're observing:
BLOB with text aren't shown in value panel, BLOB with pictures are shown as expected.

verified


Standard deviation of stat weights looks wrong

Describe the bug
When asking the simulator to compute stat weights, standard deviation is displayed after each actual stat weight. These numbers look quite suspicious to me and I'm reasonably sure they are incorrect.
I made two tests. First test is on my feral druid. Standard deviations reported look like this:
Strength: +/- 1.79
Agility: +/- 1.79
Attack Power: +/- 1.79
Melee Hit : +/- 0.00
Melee Crit: +/- 1.79
Melee Haste: +/- 1.80
Armor Pen: +/- 1.79
Expertise: +/- 0.00
Both Melee Hit and Expertise are over cap on my simulation, which explains the lack of deviation for them. All other stats have 1.79 or 1.80, which is suspect. Also this number is simply too high to start with, it even exceeds the weight of some stats. For example, AP weight is reported as 1.00 +/- 1.79, which means it could be reasonably anywhere within range -0.79 to +2.79. Negative values are simply non-sense to start with, so this can't be correct.
Second test is on my rogue. Standard deviations reported look like this:
Strength: +/- 1.01
Agility: +/- 1.01
Spell Hit: +/- 0.00
Spell Crit: +/- 1.01
Attack Power: +/- 1.01
Melee Hit : +/- 1.01
Melee Crit: +/- 1.01
Melee Haste: +/- 1.01
Armor Pen: +/- 1.01
Expertise: +/- 1.24
This time, value 1.01 is reported almost everywhere, which is pretty suspicious. And it is still way too high. I would expect the standard deviation to be a small percentage of the stat weights, like the standard deviation of the simulated DPS itself (typically around 3% of the DPS value).
To Reproduce
Steps to reproduce the behavior:

Click on the Stat Weights button.
Click on the CALCULATE button.
Wait for the simulations to be over.
Look at the standard deviations displayed.

Expected behavior
I would expect standard deviation to be small, and vary a bit from one stat to the next. For example, I would expect Haste rating or Critical rating to incur more noise and thus have higher standard deviation, compared to AP or Strength which should have almost none, as they only change the damage in a way that does not depend on RNG or affect timings.
Desktop (please complete the following information):

OS: openSUSE Leap 15.3
Browser: Firefox
Version 102.5.0esr

Additional context
I'm not sure what exactly standard deviation is supposed to represent in the context of stat weights. How are you computing it?

I took a look at the code. I'm sorry to say I don't think the way the stat weight standard deviation is computed makes sense. Which easily explains why the numbers are way off.
As I read the code, you are computing the standard deviation on the DPS value over 3000 runs with stats unchanged, then you are computing the standard deviation on the DPS value over 1500 runs with one stat decremented. You combine these 2 numbers together using a formula that I can't make any sense of. Square root of the sum of the squared value of the standard deviation of the DPS of both series? Why? What is this quantity supposed to represent?
This is mathematically wrong. The number you obtain has nothing to do with the standard deviation of the stat change in question, it is solely related to the variation of the DPS itself over the 3000 baseline iterations and the 1500 iterations with one stat decreased.
If you really want to display the standard deviation of stat weights, you have to compute it in a way that is mathematically correct:

Run your 3000 baseline iterations.
For each baseline iteration, do an iteration with the modified stat (ideally using the same RNG seed) and store the DPS difference (1:1 comparison with the corresponding baseline iteration). You'll end up with an array of 3000 values (half negative, half positive, given the current strategy).
Compute the standard deviation over this array. That will give you the actual standard deviation for the stat change in question.
Repeat steps 2 and 3 for each stat.

That being said, I would question the value of displaying the standard deviation for stat weights. It does make sense to compute and display the standard deviation of the simulated DPS because we do expect variation there, it is clearly visible in the DPS histogram, and there are a number of factors which will affect the variation range and thus the standard deviation (for example, increasing the weapon damage range will increase the variation range, while increasing the hit rating under cap will decrease the variation range).
On the other hand, do we expect significant variation when changing one stat by a small amount? I don't think so. So I'm not sure these numbers are worth computing in the first place, and it might be better to simply drop the whole code for simplicity.

Hey thanks for the report! And an ever bigger thanks for actually looking at the code, most people don't get that far. A few clarifications:

Assuming the default 3000 iterations, both the baseline and the modified sim run for 1500 iterations. This is because we do 2 modified sims: one with +X, and one with -X.
The confusing formula you noted is how the standard deviation of a difference between two distributions is calculated: https://stats.stackexchange.com/a/186545. Your suggested strategy might still be better though.
We do hold RNG constant, and our RNG seed for each iteration is initialSeed+iterationNumber so we are using the same RNG seed for all corresponding iterations in base vs modified.

I'm planning to make another pass at stat weights soon because there are other issues with it, so I might attempt your suggestion and see how it goes. The justification for including standard deviation is to give the user some sense of whether they need to increase the # of iterations, although I'm not sure we actually accomplish that today.
If you have any other suggestions, please feel free to offer them!

Tried out your suggestion and it does work way better. Thanks! Feel free to open another issue if you see something else wrong.

Thanks for the detailed answer and the quick resolution.
Answers on Stackexchange are usually of high quality and this one was no exception. The formula mentioned for the combined variance of two series of data is correct: contrary to the popular belief, when doing a difference between two series of data which each have some variance, variances do not magically cancel each other but instead tend to add up.
However this only holds if the series are independent from each other. In the case of stat weights we are actually trying our best to make them dependent, by using the same random seed. This is why comparing the individual iterations and computing the standard deviation on these 1:1 comparisons gives more accurate results than the general formula.
Speaking of this, I have another idea that could possibly make stat weight estimation even more reliable. I'll create a separate ticket for it, as the bug reported here is already solved.


Update SHHS encoding style and missing data handling

I had some unicode decoding errors when reading SHHS data based on the windows "RIGHT SINGLE QUOTATION MARK" character. Changing the encoding to 'windows-1252' fixed this (as recommended in https://stackoverflow.com/a/40029793/3484157)
I also ran into some errors where gender or age values were missing for some rows in SHHS2 and I added the option for these parameters to be None.
I initially added logging for this, but removed it to avoid adding a new dependency (hence the multiple commits)

@cbrnr please review when you can, thanks!

Thanks for noticing and fixing these issues @adgilbert! 🚀


error handler

@wittydeveloper  do you still maintain this project? If not, please mark it as deprecated


v0.2.2 changed

update readme, put easy API reference on it
compile go reducer to JS reducer, not suit any situation
serialize state to Json format, Store::JSON() API

How to Use go2JS
$ cd go2JSreducer/
$ go build(or install)
$ ./go2JSreducer path/to/your/goreducer.go

the go2JS & serialize both are incomplete for every case.


⚠ Samsung has degraded performance

In 4621511, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2165 ms

Resolved: Samsung performance has improved in e9ab054.


Cant we create a new repo with this module??

do we also able to create repositories if not exist with this module?

No, that is currently not possible. I'm not even sure it's wanted as at least for our use-case, we also move repos from other orgs to this GitHub org. If we accidentally ran the tool with team permissions to a currently non-existing repo, it may block migrations.
With the current behaviour, we would probably just get an error on the tool's side, but it wouldn't do anything it shouldn't do.
However, please feel free to explain your use-case, or contribute a PR.

i was planning to use this tool for managing multiple team and their respective repos which also include repo permission management and creation if not exists.

OK, it might make sense, perhaps we could make this configurable.
I won't get to do this before my parental leave, so not before the end of the year. If you would like to submit a PR, I'd be happy to review.


Change origin reference point with 9-dot selector (not just for rotations)

I noticed that the "9 dots" origin-selector only applies to rotations. In, e.g., Adobe Illustrator, this also affects translation and scaling (which I think is the expected behavior).
Could Graphite be updated so that the origin is also affected for translations?
See below screenshots that illustrate what I mean. The red and blue shape should not have the same X coordinate, as I selected the reference of origin to be center-left. (also notice how the "9 dot" selector is quite difficult to see, perhaps something to adjust as well).

Thanks for the report. This is a duplicate of #1530 (although that issue has some outdated information, so disregard any inaccuracies it may have).

The yellow dot is not the origin, it is the centre of rotation.

Thanks for the quick follow up. My apologies, I did a quick search but missed that duplicate issue.

For some additional context, we have a large refactor planned for how the node graph encodes instance data and how those instances store their transforms. This will fundamentally change the limited system we currently have in place for transforms, largely with the aim of solving some of the outstanding issues like the one you pointed out. I hope it'll be done by Q1 2025.


Fix fetch-catalog when a cache directory does not exist and minor typo

What does this PR do?
This PR fixes an issue where the absence of a cache directory would cause an error by creating the cache directory if it doesn't exist. It also removes a minor typo in the readme, specifically the period in 'python fetch_catalog.py.'.

Thanks @kimx3966 ! Merging this as this looks good


[Enhancement] no need to getLabelState if an existing label is finished

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

the benefit of this pr have two aspects:

when DefaultStreamLoader.send failed, we can use the the context of existingJobStatus field in the StreamLoadResponse to replace getLabelState  http request;
In addition, if  we use sink.version = 2 and at-least-once sink semantic，we just use BE's ipAndHttpport and then DefaultStreamLoader.send  directly send data to BE node, instead of redirecting to BE  through FE , so further eliminate redirect problem.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)
[ ] I have added documentation for my new feature or new function

@szza Thanks for your PR

@szza Thanks for your PR


Searching from the image details page not working

Describe the bug
Searching for any query from the top right search bar on the image details page does not fill the grid with new images. Though, the search query makes it way to the URL and the main search bar.
Please refer to the GIF below.
To Reproduce

Go to https://search.creativecommons.org/photos/9f8f92a2-363c-4754-96e7-0f0d26ee1a8c
Search for anything from the top right search bar.
See error

Expected behavior
The new search results should fill the grid automatically. The user must not click the search icon again.
GIF

Desktop (please complete the following information)

OS: Ubuntu 19.10
Browser: Chrome v80.0.3987.122

Thanks for reporting this :) I think we should tack this onto #667 since it's pretty much the same behavior, just a slightly different situation. @DantrazTrev, I'm going to assign this to you, please include a fix for this in #667 :)

@akmadian If no one has done yet, can I re-open my PR, because I have fixes this issue in this PR #657

@abhisheknaiidu I think we're going to move ahead with the fix implemented in #667

Closing as this was fixed in March. Thanks everyone!


[ENHANCEMENT] (Expand the PowerShell Store to another versions of PowerShell (5.x/7.x/etc) )

Please confirm these before moving forward

[X] I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
[X] This improvement refers to an existing feature. If you want to suggest a new feature, please use this template
[X] This improvement is not a bug. If you want to report a bug, please use this template

Describe the improvement
The Ability to download modules for other versions of PowerShell in addition to the one installed by default in windows 10/11 (V1.0), since the additional versions have to be installed manually, I suppose the ability to manually add a path in addition to the basic one, since the commands remained the same trough the versions, it shouldn't be much too different from the V1 store
Describe how this improvement could help users.
It would help to handle modules from other versions besides the base (V1.0)

A little background: Windows, a closed-source OS, comes with the latest closed-source version of PowerShell, i.e., version 5.1. This version is ancient. Since 2016, PowerShell has become an open-source project. Its latest version is 7.4.2 (as of today).
The relation between PowerShell 5.1 and 7 is like the relation between Python 2 and Python 3.
Most people I know install and only use the latest version of PowerShell. They ignore PowerShell 5.1 completely. In the past PowerShell 5.1 was necessary because of its Remove-AppxPackage cmdlet, but WinGet has replaced it.

An additional comment. For some of us, we have to deal with Windows PowerShell (5.1) modules because the owner of such modules (in some cases, Microsoft) does not allow to use them with PowerShell (6.x, 7.x). And vice versa.
So we end with a mix of modules. And some are installed globally (Install-Module -Scope AllUsers), and some are installed for the current user only (Install-Module -Scope CurrentUser). So, checking for outdated modules is to check all sources and across both "worlds". Get-InstalledModule with Windows PowerShell (powershell.exe) and with PowerShell (pwsh.exe), should be intelligent enough to get modules from both scopes, but both processes should be used as different environments.

Very nice change, thanks!


check if there is an app installed that can handle the given intent

Currently the plugin is just firing an intent and don't cares if there is no app installed that can handle it. Nevertheless this is frequent error. Could you please extend it by this check?
 if (intent.resolveActivityInfo(mActivity.getPackageManager(), 0) != null) {
         mActivity.startActivity(intent);
} else {
        //throw error
 }

Good idea 👍 updated as suggested.


chore: run e2e tests on demand

Description of your changes
Running e2e tests on demand.
Next we will need to make sure that some following PRs handle decision made in discussion #315 .
Potential improvment
Run only when module changes with --onlyChanged --changedSince=main option on jest
How to verify this change
Check for https://github.com/awslabs/aws-lambda-powertools-typescript/actions/workflows/run-e2e-tests.yml tests run
Related issues, RFCs
#418
PR status
Is this ready for review?: YES
Is it a breaking change?: NO
Checklist

[x] My changes meet the tenets criteria
[x] I have performed a self-review of my own code
[x] I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] The code coverage hasn't decreased
[x] I have added tests that prove my change is effective and works
[x] New and existing unit tests pass locally and in Github Actions
[ ] Any dependent changes have been merged and published in downstream module
[ ] The PR title follows the conventional commit semantics

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks, this is huge!
Just left some minor suggestions to reword part of the contributing section + added a disclaimer about potential costs of running the tests.
~Only other note is that the unit tests in logger are not yet tagged so even when running test:e2e the regular unit ones are running.~ Done in e3a83ce

thx for the commit !

Please re-request my review (or ping me) when you apply these changes so I can make sure I don't make it wait.

@flochaz pushed a commit because I noticed that the "⚠ " symbol here was not rendering properly, also addressed one comment while there, hope you don't mind.


Symbol without denotation in ReactiveMongo/ReactiveMongo-BSON

Compiler version
Spotted in 3.3.0-RC4.
It will require additional work to determine if it was happening before.
Code
//> using scala "3.3.0-RC4-bin-SNAPSHOT"
//> using options "-Wunused:all"
//> using lib "org.reactivemongo::reactivemongo-bson-api:1.1.0-RC9"

import reactivemongo.api.bson.*

case class Eval()

given BSONDocumentHandler[Eval] = Macros.handler

Output
Crash of the compiler. Note that since #17316 missing denotation is not causing a crash.
The symbol that is missing denotation is a self-alias defined here
I was trying to reproduce the issue outside of the library but without success. We should return to that and investigate what is going on.

Closing it as it does not crash in 3.3.0 or any other subsequent version


Implement a scheduler and a temp ban command

[x] make the warn command's DM not show who issued the warn
[ ] basic scheduler
[ ] temp bans

close as changed branch name


Add support for Date and DateTime

Allow Date and DateTime objects to be persisted in Entity properties.

@blowmage I like the duck type detection! But we owe @timanovsky a big thanks for posting the observation about Rails adding .to_time to string! Really appreciate your help @timanovsky. Nice solution @blowmage.


Same color for airline background and vim background

when working with splits, it is hard to see where one window ends and a new one begins. It happens to me with any picture I use to generate colors. Is there an option to change it?

nevermind. Solved it.

nevermind. Solved it.

how?


Uncaught ImportError in init.py line 78

Aider version: 0.62.1
Python version: 3.11.8
Platform: Linux-6.1.112+-x86_64-with-glibc2.38
Python implementation: CPython
Virtual environment: Yes
OS: Linux 6.1.112+ (64bit)
Git version: git version 2.42.2
An uncaught exception occurred:
Traceback (most recent call last):
  File "aider", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "main.py", line 582, in main
    models.print_matching_models(io, args.list_models)
  File "models.py", line 1139, in print_matching_models
    matches = fuzzy_match_models(search)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "models.py", line 1103, in fuzzy_match_models
    for model, attrs in litellm.model_cost.items():
                        ^^^^^^^^^^^^^^^^^^
  File "llm.py", line 23, in __getattr__
    self._load_litellm()
  File "llm.py", line 30, in _load_litellm
    self._lazy_module = importlib.import_module("litellm")
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1147, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "__init__.py", line 858, in <module>
    from .cost_calculator import completion_cost
  File "cost_calculator.py", line 22, in <module>
    from litellm.llms.anthropic.cost_calculation import (
  File "cost_calculation.py", line 9, in <module>
    from litellm.utils import get_model_info
  File "utils.py", line 52, in <module>
    from tokenizers import Tokenizer
  File "__init__.py", line 78, in <module>
    from .tokenizers import (
ImportError: libstdc++.so.6: cannot open shared object file: No such file or directory

Thanks for trying aider and filing this issue.
This looks like a duplicate of #1313. Please see the comments there for more information, and feel free to continue the discussion within that issue.
I'm going to close this issue for now. But please let me know if you think this is actually a distinct issue and I will reopen this issue.


Remove id from params unless in the createable_fields

This removes :id from the params before verification.

I sent this before I wanted to. One small change coming in a minute.

This should be all set now. I submitted it a bit before I meant to, but everything is ready now.

@barelyknown, Travis is reporting a failing test:

ResourceTest#test_updateable_fields_does_not_include_id [/home/travis/build/cerebris/jsonapi-resources/test/unit/resource/resource_test.rb:81]:
Failed assertion, no message given.

Shoot. Just saw that. Fixing now.

Thanks!


[Bug] Python multi-line script exection failed on Python 3.8+

Code of Conduct

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

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the bug
Using Python 3.9.6 and the master branch with kyuubi #3782 for PySpark support, multi-line python script failed in compile of execution_python.py and throws an exception with required field "type_ignores" missing from Module message.
It might be caused by breaking change in compile method since 3.8+ , with tests on:

3.9.15【Failed】
3.8.15【Failed】
3.7.15【OK】

Tested on 3.9.6 with  the following python code:
a=10087
a

Traceback message of response:

Running execution_python.py alone with :

Affects Version(s)
master
Kyuubi Server Log Output
No response
Kyuubi Engine Log Output
[Traceback (most recent call last):
,  File "/var/folders/vn/3fb4hcv94ygd2scgnqz64pth0000gn/T/6181531906930307082/execute_python.py", line 41, in execute
    code = compile(mod, '<stdin>', 'exec')
,TypeError: required field "type_ignores" missing from Module
]

Kyuubi Server Configurations
set kyuubi.operation.language=python;

Kyuubi Engine Configurations
No response
Additional context
No response
Are you willing to submit PR?

[ ] Yes. I can submit a PR independently to fix.
[ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to fix.
[X] No. I cannot submit a PR at this time.

cc @cfmcgrady

Good job for fixing the problem so quickly. Thx. @cfmcgrady


router: add router stat for reset after downstream response

Description: Adds upstream_rq_error stat for upstream clusters.
Risk Level: Low
Testing: Added tests
Docs Changes: Updated
Release Notes: Updated
Fixes https://github.com/envoyproxy/envoy/issues/5905

@mattklein123 changed this to router level stat. Please see if this what you are suggesting.


Critical dependency warning in Next 13 (Turborepo)

Describe the bug
Hey guys,
First, I apologize for not setting up a codesandbox for this, the setup alone would take hours in my current config. So I'm really wondering if you guys might have a quick win here?
I'm getting this in my terminal on every access to the Yoga server -
 ⚠ ../../node_modules/.pnpm/@whatwg-node+fetch<EMAIL_ADDRESS>Critical dependency: the request of a dependency is an expression

Import trace for requested module:
../../node_modules/.pnpm/@whatwg-node+fetch<EMAIL_ADDRESS>../../node_modules/.pnpm/graphql-yoga<EMAIL_ADDRESS>../../node_modules/.pnpm/graphql-yoga<EMAIL_ADDRESS>./app/api/graphql/route.ts

Contents of route.ts:
import { createSchema, createYoga } from 'graphql-yoga';

import { dealerResolvers } from './resolvers/dealers';
import sharedSchema from './schema.graphql';

const schema = createSchema({
    typeDefs: [sharedSchema],
    resolvers: [dealerResolvers],
});

const { handleRequest } = createYoga({
    graphqlEndpoint: '/api/graphql',
    fetchAPI: { Request, Response },
    schema,
});

export { handleRequest as GET, handleRequest as POST };

I'm using Node v20.2 and the latest Next and Turborepo builds, and as you probably noticed the App router. Everything works as expected, but this warning is spamming my logs. It goes without saying that before Yoga my terminal was free of warnings. Wdyt?
Thanks!
Your Example Website or App
https://codesandbox.io/
Steps to Reproduce the Bug or Issue
My setup is in turborepo with a bunch of interconnected packages and applications. I'm not sure it can be replicated in a stable manner without our external services.
Expected behavior
The terminal shouldn't have dependency warnings.
Screenshots or Videos
No response
Platform

OS: macOS
NodeJS: 20.2.0
@graphql-yoga/* version(s): 4.0.5
next version(s): 13.5.3

Additional context
No response

To reproduce
git clone https://github.com/Luferov/soulmagic
pnpm i
pnpm run dev

This avoids the warning.
/**
 * @type { import("next").NextConfig}
 */
const config = {
  experimental: {
    serverComponentsExternalPackages: ["@whatwg-node"],
  },
};
module.exports = config;

This avoids the warning.
/**
 * @type { import("next").NextConfig}
 */
const config = {
  experimental: {
    serverComponentsExternalPackages: ["@whatwg-node"],
  },
};
module.exports = config;

Thank you, but unfortunately for me the warning persists. :(

We'll take a look but this is just a warning, and it shouldn't have any effect on runtime.

You're right, everything does work as it should, like I said. I will just have to filter it out of our logs specifically since it is very frequent. Thanks again!

First of all, when I open /api/graphql this error still exist.

Second of all, all GraphQL queries doesn't work. 🥲

First of all, when I open /api/graphql this error still exist.
This looks like a different error. Please create a different issue with a reproduction.

This works for me.
<EMAIL_ADDRESS><EMAIL_ADDRESS>
This avoids the warning.
/**
 * @type { import("next").NextConfig}
 */
const config = {
  experimental: {
    serverComponentsExternalPackages: ["@whatwg-node"],
  },
};
module.exports = config;


onStopped override should be forced to call parent

If the parent onStopped method is not called, the state of the SMO is never set to stopped. As a result, an SMO will try to be stopped twice. Errors will likely bet generated on the second attempt since references have already been destroyed.

[Fix: 41] onStopped, onStarted and onProcessStopped methods must require overrides to call parent.
Will be available in 1.3.0

fixed in 1.3.0


docs(readme): eslint-plugin-react peer dependencies applied

I've changed README.md of eslint-config-react-app package.
It seems #696 doesn't applied to file yet.
Thanks.

Thanks!

@gaearon this change is not showing on npm's page. People will install<EMAIL_ADDRESS>and not<EMAIL_ADDRESS>

This is because of https://github.com/npm/registry/issues/42.
We may need to use something like https://www.npmjs.com/package/lerna-npm-readme-hack.


Feature : Property level inheritance in Touch UI dialog

## Required Information

[ ] AEM Version, including Service Packs, Cumulative Fix Packs, etc: AEM 6.5, Service Pack 5
[ ] ACS AEM Commons Version: 4.1.0
[ ] Reproducible on Latest? yes

Expected Behavior
As per the current implementation of Touch UI dialog, it is not possible cancel inheritance of a particular field in a dialog. As an author it's only possible to cancel whole dialog.
1 ) Author should have the possibility to cancel only property which they want to.
2) Author should be able to see dialog property without canceling the inheritance.
Actual Behavior

Author cannot see the dialog properties without cancelling the inheritance of whole dialog.

Please describe briefly the actual behavior, i.e. when I do X, Z happens.
Steps to Reproduce

Start AEM 6.5
Go to sample We-retail implementation and open Blue print page:  http://localhost:4502/editor.html/content/we-retail/language-masters/en/experience.html
Open the dialog of Hero image component and edit any dialog property
Rollout the page
Open Live copy page : http://localhost:4502/editor.html/content/we-retail/us/en/experience.html
Try to open the Hero image dialog property , you cannot see the dialog property without cancelling the inheritance.
If you cancel the whole component inheritance but there is also no possibility to cancel only the specific property you want to do cancel inheritance

It becomes really difficult to manage for editors located into different parts of the world.
I have implemented this behaviour, if you want to include I can create a pull request.
Links
Links to related assets, e.g. content packages containing test components

Is this caused by installing ACS Commons or are you reporting a product bug that occurs irrespective to installing ACS Commons?  If it's a core component that isn't working right you can report bugs on those here: https://github.com/adobe/aem-core-wcm-components

This is not caused by ACS Commons and I also do not know whether it is a product bug or not because as per Adobe support this is by design. However I strongly believes that many content authors face this issue for which I have a solution.

Great to know!  I just wanted to make sure I understood the context of this problem.  Thank you for the additional clarification.

@badvision what do you think about this feature?


can not import

can not import caffe
I follow caffe ssd installation。But after make i still can not import caffe

If you want to be able to import caffe from python3 directly, you need to let python3 add ${HOME}/project/ssd-caffe/python as one of the paths for importing packages.  For example, you could add the following to your ~/.bashrc:
export PYTHONPATH=${HOME}/project/ssd-caffe/python

thanks a lot!


Significant Performance Gap (100x slower) between CMake vs Bazel Build on ARM64

Issue Description
When building the benchmark program on ARM64 using CMake vs Bazel, I'm observing a 30x-100x performance difference for the same inference task:

CMake build: ~1000ms per inference
Bazel build: ~10ms per inference

Build Details
CMake Build (Native on ARM64)
cmake -S . -B build
cmake --build build

Bazel Build (Cross-compiled from x86-64)
bazel build --config=aarch64 //larq_compute_engine/tflite/benchmark:lce_benchmark_model

Environment

Device: ARM64 board
Build method comparison:

CMake: Native build on ARM64
Bazel: Cross-compiled from x86-64

Hypothesis
The performance gap might be due to CMake build not properly utilizing BNN kernels for aarch64, but I'm not certain about this.
Questions

What could be causing this significant performance difference?
How can I configure the CMake build to match the Bazel build performance?
Has anyone else encountered similar performance disparities?

Additional Context
I followed the build instructions from the documentation at docs.larq.dev/compute-engine/build/arm/
Any insights or guidance would be greatly appreciated.

Could you try adding -DCMAKE_BUILD_TYPE=Release to your CMake command, i.e.:
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build

Could you try adding -DCMAKE_BUILD_TYPE=Release to your CMake command, i.e.:
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build

Thank you for your reply.
I tried this and I got 100ms per inference, but still 10x slower than the Bazel built benchmark.
CMake build
$ ./lce_benchmark_model --graph=../../iris_roi_detector.tflite
INFO: STARTING!
INFO: Log parameter values verbosely: [0]
INFO: Graph: [../../iris_roi_detector.tflite]
INFO: Loaded model ../../iris_roi_detector.tflite
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
INFO: The input model file size (MB): 0.115336
INFO: Initialized session in 23.115ms.
INFO: Running benchmark for at least 1 iterations and at least 0.5 seconds but terminate if exceeding 150 seconds.
INFO: count=4 first=242047 curr=119796 min=119778 max=242047 avg=150366 std=52931

INFO: Running benchmark for at least 50 iterations and at least 1 seconds but terminate if exceeding 150 seconds.
INFO: count=50 first=119961 curr=119900 min=119731 max=119966 avg=119840 std=59

INFO: Inference timings in us: Init: 23115, First inference: 242047, Warmup (avg): 150366, Inference (avg): 119840
INFO: Note: as the benchmark tool itself affects memory footprint, the following is only APPROXIMATE to the actual memory footprint of the model at runtime. Take the information at your discretion.
INFO: Memory footprint delta from the start of the tool (MB): init=4.32031 overall=15.5625

Bazel build
$ ./lce_benchmark_model --graph=iris_roi_detector.tflite
INFO: STARTING!
INFO: Log parameter values verbosely: [0]
INFO: Graph: [iris_roi_detector.tflite]
INFO: Loaded model iris_roi_detector.tflite
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
INFO: The input model file size (MB): 0.115336
INFO: Initialized session in 6.057ms.
INFO: Running benchmark for at least 1 iterations and at least 0.5 seconds but terminate if exceeding 150 seconds.
INFO: count=30 first=198776 curr=10385 min=10313 max=198776 avg=16676.6 std=33815

INFO: Running benchmark for at least 50 iterations and at least 1 seconds but terminate if exceeding 150 seconds.
INFO: count=97 first=10396 curr=10346 min=10328 max=11225 avg=10391.9 std=107

INFO: Inference timings in us: Init: 6057, First inference: 198776, Warmup (avg): 16676.6, Inference (avg): 10391.9
INFO: Note: as the benchmark tool itself affects memory footprint, the following is only APPROXIMATE to the actual memory footprint of the model at runtime. Take the information at your discretion.
INFO: Memory footprint delta from the start of the tool (MB): init=4.23828 overall=15.6445

Do I have to set more options for CMake native build? Or is there any required extra setup or option.

I think the problem is the compilation options.
I modified CMakeLists.txt using arm64 compilation flags from .bazelrc . And then I got 10ms inference speed.

Great that you solved it. Could you share exactly what you modified? Thanks!

I just added the following lines in CMakeLists.txt (I'm not sure of changes I've made so I would have to check this later)
# Architecture specific flags (from aarch64 config)
set(ARCH_FLAGS "-march=armv8-a -DS_IREAD=S_IRUSR -DS_IWRITE=S_IWUSR -fno-tree-pre \
    -U__GCC_HAVE_SYNC_COMPARE_AND_SWAP_1 \
    -U__GCC_HAVE_SYNC_COMPARE_AND_SWAP_2 \
    -U__GCC_HAVE_SYNC_COMPARE_AND_SWAP_8 \
    -funsafe-math-optimizations \
    -fomit-frame-pointer")

# TensorFlow specific flags
set(TF_FLAGS "-DTFLITE_WITH_RUY")

# Combine all flags
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} ${ARCH_FLAGS} ${TF_FLAGS}")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${ARCH_FLAGS} ${TF_FLAGS}")

# Define options equivalent to Bazel's build settings
add_definitions(
    -DTFLITE_WITH_RUY
    -DTF_LITE_DISABLE_X86_NEON
)

# Disable features (equivalent to --config=nohdfs --config=nonccl --config=noaws --config=nogcp)
add_definitions(
    -DNO_HDFS_SUPPORT
    -DPLATFORM_CLOUD_NONE
    -DNO_AWS_SUPPORT
    -DNO_GCP_SUPPORT
)

Those are from .bazelrc copts. I'm not sure what was the key issue, but this worked. Hope this would be helpful!

Thank you :pray:


⚠ Mobitopup has degraded performance

In 6200100, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 4465 ms

Resolved: Mobitopup performance has improved in af821cb.


Tooltips for Ionic 5/Angular 9 Apps

Does this work with Ionic 5/Angular 9 Apps

Not for me.

Not sure if this package is still maintained so I created https://github.com/jrquick17/ionic4-tooltips which supports Angular 2+ and Ionic 2+


Look into just to replace test.sh

https://github.com/casey/just

While we're at it, I really want to be able to run individual tests

Approximately completed in 27476ab09cfa8292c382aa6fbcd1970b9ef0be32 and fdb5f91bc68cd96264f5ef6d6be83ba8336af1ec


Report Referrer per Page (URL/path)

🐣 Is your feature request related to a problem? Please describe.
I want to find out where visitors to a specific page are coming from. E.g.: I get an unusual amount of traffic to page /abc/xyz, now I want to know which referrer these visitors have set.
💡 Describe the solution you'd like
A way (API only would be good enough™) to filter the getDomainsStatistics query down by path. Basically creating a new query like getDomainStatisticsForPath.
❓ Describe alternatives you've considered
I don't see any API for querying the raw records either. So I cannot really see any alternative. Doesn't have to mean there is none :)

Any progress on this feature? @ManUtopiK
Also not knowing a lot about this system internally, couldn't you bypass the API as a temporary fix, then make some advanced query?
This feature is pretty basic and very much needed for any site with lots of content as far as i can se :)

@aske-cph Yes, I'm working on it.
You can see the work in progress in the viewsPerPage branch here: https://github.com/ManUtopiK/Ackee/tree/viewsPerPage
Only the api works fine. You can fetch stats per page with:
{
  domain(id: "yourDomainID") {
    statistics {
      viewsPerPage(
        page: "thePageURL"
        interval: DAILY
        type: TOTAL
      ) {
        id
        count
      }
    }
  }
}

I will work on the UI, but I haven't worked with React for 3 years. I work with Vuejs and Svelte. React is very ugly...


Allow the allocator to track the heap changes.

This will greatly help with try-runtime's offchain_worker. I can now re-execute the last offchain worker's election code, as such, and get this nice report of heap usage:
    Finished dev [unoptimized + debuginfo] target(s) in 2m 23s
     Running `target/debug/substrate try-runtime --block-at 0x32f4f40c9bf09e7406721c562356f6b3ca718fc405a0164cbca31da6fd8ece7a --execution Wasm --url 'ws://kianenigma-archive:9944' offchain-worker live -m ElectionProviderMultiPhase`
2021-07-06 20:51:23.441  INFO main remote-ext: initializing remote client to "ws://kianenigma-archive:9944"
2021-07-06 20:51:23.517  INFO main remote-ext: scraping key-pairs from remote @ 0x32f4f40c9bf09e7406721c562356f6b3ca718fc405a0164cbca31da6fd8ece7a
2021-07-06 20:51:23.580 DEBUG main remote-ext: last page received: 6
2021-07-06 20:51:23.580  INFO main remote-ext: Querying a total of 6 keys
2021-07-06 20:51:24.928  INFO main remote-ext: downloaded data for module ElectionProviderMultiPhase (count: 6 / prefix: ede8e4fdc3c8b556f0ce2f77fc2575e3).
2021-07-06 20:51:24.928 DEBUG main remote-ext: adding data for hashed key: 26aa394eea5630e07c48ae0c9558cef7f9cce9c888469bb1a0dceaa129672ef8
2021-07-06 20:51:24.968 DEBUG main remote-ext: adding data for hashed key: 3a636f6465
2021-07-06 20:51:25.404  INFO main remote-ext: extending externalities with 0 manually injected key-values
2021-07-06 20:51:25.405  INFO main remote-ext: injecting a total of 8 keys
2021-07-06 20:51:28.527 DEBUG main wasm-heap: allocator being destroyed, max total_size 800, max bumper 1269856
2021-07-06 20:52:14.502 DEBUG main wasm-heap: allocator being destroyed, max total_size 29645680, max bumper 70057920
2021-07-06 20:52:14.505  INFO main try_runtime_cli: OffchainWorkerApi_offchain_worker executed without errors.

which shows the bumper being around 70mb, still far from the current 128mb.

bot merge


CodeView improvements

Issue: To modify and design code view for code samples of Compose & add micro features
Issue Level: Mid
Micro features: Copy to clipboard
Expected Design Style:

Thanks for this great idea! you can work on this issue @binayshaw7777


Update ESLint configuration and fix style

This PR is regarding an update on the eslint-config-opencollective library, I also updated the other eslint related libraries and then got a bunch of errors and warnings, that's why this PR is big but it's all about eslint tweaks.

I'm good with it.
Some of the rules (like the quotes or trailingComma rule) are not consensual yet within the team. This is why they were not automatically enforced so far.

@znarf to be honest I have just followed the list npx eslint '**/*.js' has generated and removed the warns and errors, I don't have any strong opinion on changing or keeping the way it is(I think it's good the way it is) but if the team agrees to change the lint later we can just update it make the code to be compliant with the npx eslint '**/*.js' once more.

Coverage remained the same at 71.121% when pulling 28f2edba58134e0098a8872b503855ff2f74eb0a on move-eslint-rule into 4c8f6326c46b7813346da0395ed3d06c3675594b on master.

@znarf ping me if you think we can merge!! Thanks in advance!

@marcogbarcellos there is now conflicts to be fixed

@znarf yes I think this will conflict with almost any new PR that's merged to master so I'll update the eslint file to included the space comment rule and will fix the conflicts to merge it.

@marcogbarcellos also don't forget publishing the package on npm (ask me or xdamman).

@znarf created a PR on the eslint project( opencollective/eslint-config-opencollective#9 ) so whenever you or xavier publish the new i will updated the package.json here, resolve the conflicts and let you know it's ready to merge.

Updated libraries in https://github.com/opencollective/opencollective-api/pull/1437
Skipping the formatting for now.


Fix OPTIONS handling in fcrepo-ldpath

Resolves: https://jira.duraspace.org/browse/FCREPO-2358

@acoburn Looks good, and is straightforward.  Were you intending to add any tests that verify OPTIONS response, either here or in fcrepo-camel-tests?

@birkland yes, there should be a test for that, and I have added one in this commit

👍


Forcing Evaluation of an AST

What's the best way to force evaluation of an AST? I tried to define an NFData instance (from Control.Deepseq) for AST dom a, but the existential types in the constructors cause problems. Is there any hope for an NFData instance? What about other ways to ensure that the tree is fully evaluated?

I think you just need an extra class for forcing symbols:
class NFSym sym
  where
    rnfSym :: sym sig -> ()

instance NFSym sym => NFData (AST sym sig)
  where
    rnf (Sym s)  = rnfSym s
    rnf (s :$ a) = rnf s `seq` rnf a


WIP: Add page listing the developer advocates

This adds a page at /developer-advocates which lists the current DAs, along with some other content.
Note: this adds an optional field to the team entries in the data directory; anyone with role = "developer-advocate" will show up on this page.
We are still working through the content, so this is a draft PR at the moment.
Signed-off-by: Matt Stratton<EMAIL_ADDRESS>

I'm going to rebase this and submit a new PR


 On other slave-sm(s) I am reading back the output of the generator sm and wait for pulse edges with wait 0 ...,wait 1 ...-instructions to synchronise the output to the generator sm. This works very well, if the slave sms are on the same pio.
If I try do run the slave-sm on the other pio.  The call of pio_gpio_init of the read back output on the other pio will kill the output of the generator sm on the generator pio.
It seems that the pio_gpio_init-call will (re)initialize the pin-direction of the output pin of the other state machine to input.
The only solution I found was to read back the output on a bridged input pin.
for the slave-sm on the other pio.
Please describe this behavour in your documentation.
My understanding of "PIO controls the output level and direction of up to 32 GPIOs, and can observe their input levels. ... ranges can overlap"
is different.

It seems that the pio_gpio_init-call will (re)initialize the pin-direction of the output pin of the other state machine to input.

https://www.raspberrypi.com/documentation/pico-sdk/hardware.html#gafa244b1be8f53a329db9d26298e054bb says "Note that this is not necessary for a state machine to be able to read the input value from a GPIO, but only for it to set the output value or output enable.", which I guess implies that you shouldn't be re-initing the GPIO on your "slave" PIO?

It sounds like @lurch has identified your issue?


scheduler: improve NodeNUMAResource handling node cpu bind policy

Ⅰ. Describe what this PR does
If the node enables label node.koordinator.sh/cpu-bind-policy and configures the corresponding value to FullPCPUsOnly or SpreadByPCPUs, then the scheduler should ensure that the allocation result corresponding to ResourceSpec.RequiredCPUBindPolicy is consistent.
And the node policy may conflict with the ResourceSpec.RequiredCPUBindPolicy defined in the Pod.  For example: the node defined the policy with FullPCPUsOnly, and the Pod required SpreadByPCPUs,  this creates a conflict that should be filtered.
If the Pod does not declare the ResourceSpec with CPUBindPolicy(either required or preferred), and the node declares the CPUBindPolicy, the scheduler should allocate CPUs by node's CPUBindPolicy, even though the Pod's QoSClass is LS. Although the previous implementation could work, but the implementation was not complete enough.
As for whether koordlet or kubelet will set the cgroup according to the scheduler allocation result on the LS Pod, I think this is a strategic issue.

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/hold

/hold cancel
PTAL

/lgtm
/approve


Allow format response to specify location of cursor

Currently, when running format operations, if it returns a huge TextEdit that replaces the whole file, the cursor gets set to the end of that TextEdit in VS Code.
It would be good to allow the server to send back an offset, so the client can set the new cursor position correctly. Prettier even has an API for this: https://prettier.io/docs/en/api.html#prettierformatwithcursorsource-options.

The LSP (except for snippets) stayed so far away from letting the server control the position of the cursor since this is IMO something the editor should control. And I still think that this is the right approach. Sending huge edits is not only bad for the cursor it also will delete breakpoints and other markers. This is why we encourage to send many small edits.
For VS Code itself I know that the format code will if it is only a huge edit replacing the full content do a diff behind the sciences and execute little edits. So if this happens there might be something wrong with the smart logic in VS Code?
I tend to close this is as something we will not implement.

I had the same problem with a formatting library I was using. I implemented a simple diff algorithm to detect which part of the text had actually changed between the original document and the formatted one. As it turns out, it was not too hard to do, and mitigates the problem very well. This would probably prove a better solution than changing the protocol.

For VS Code itself I know that the format code will if it is only a huge edit replacing the full content do a diff behind the sciences and execute little edits. So if this happens there might be something wrong with the smart logic in VS Code?

I'll try to get a repro.
@LaurentTreguier What diff library are you using?

@octref Although I first thought of using a library to do this, I ended up implementing it myself instead. It's less than 100 lines long (including blank lines and lines containing only braces), and its logic is simple but sufficient for this.


Create Angular

Hello, it looks like this pull request was a mistake? I don't see anything new here..


4254 goodid onboardflow

Description
Add the onboard component to the wallet
About #4254

@L03TJ3 whats the status here?


chore: use latest Python version

We previously fixed version 3.8 due to dependency issue.
Since it is no longer an issue,  moving beck to default,
which currently means 3.9.

"beck"  -.-


[BugFix] multiple sys_log_to_console=true entry in fe.conf every time…

Why I'm doing:
multiple sys_log_to_console=true entry in fe.conf every time fe is started with --logconsole option
What I'm doing:
fe.conf should have only single entry sys_log_to_console=true
Fixes #45850
What type of PR is this:

[X] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[X] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[X] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.3
[x] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

@rohitrs1983 do you have time to update this PR?

@mergifyio rebase

@nshangyiming can you please reivew the PR.

@mergifyio rebase

@rohitrs1983 automatic rebase doesn't work, can you manual rebase this PR to latest main branch?

@rohitrs1983 automatic rebase doesn't work, can you manual rebase this PR to latest main branch?

@kevincai rebased to latest main.


Fail to run local build

Hi,
I'm trying to run the build script on my mac (master branch)
./bin/build

and I get the following error
Building plugin for darwin...
# github.com/sclevine/forge/engine
../../../go/src/github.com/sclevine/forge/engine/container.go:107:2: cannot use <-chan container.ContainerWaitOKBody as type int64 in return argument
../../../go/src/github.com/sclevine/forge/engine/container.go:107:2: cannot use <-chan error as type error in return argument:
	<-chan error does not implement error (missing Error method)
../../../go/src/github.com/sclevine/forge/engine/container.go:107:31: not enough arguments in call to c.Docker.ContainerWait
	have ("context".Context, string)
	want ("github.com/docker/docker/vendor/golang.org/x/net/context".Context, string, container.WaitCondition)

Is it a real issue or should I build it in a different way?
Thanks,
Lidor

Hi @lidortal,
Did you run /bin/vendor first?

Hi @sclevine ,
I tried to run ./bin/vendor but it fails with the following error:
ensure Solve(): No versions of github.com/vito/go-interact met constraints:
	c5a3f51ad50e34ec101050f69383caa75082f233: "github.com/vito/go-interact/interact" imports "github.com/vito/go-interact/interact/terminal", which contains malformed code: import root "github.com/vito/go-interact" is not a prefix for the package's declared canonical path "golang.org/x/crypto/ssh/terminal"
	master: "github.com/vito/go-interact/interact" imports "github.com/vito/go-interact/interact/terminal", which contains malformed code: import root "github.com/vito/go-interact" is not a prefix for the package's declared canonical path "golang.org/x/crypto/ssh/terminal"

Any idea?

It works in CI with a fresh GOPATH, and it works on my local macOS and Linux machines.
What version of dep are you running? Can you try v0.3.1?

Hi,
Thanks! now it works.
I'd dep v0.3.2, switching to v0.3.1 solved it.
Lidor


Error: Refused to connect to 'blob:http

I am getting the following error message in Chrome
Refused to connect to 'blob:http%3A//<IP_ADDRESS>%3A8080/3547f91f-dd73-48a4-9bf1-233c183c22ed' because it violates the following Content Security Policy directive: "connect-src 'self' wss://<IP_ADDRESS> https://<IP_ADDRESS>".

_createBlob.type @ localforage.js:1036
_blobAjax @ localforage.js:1034
txn.oncomplete.getBlobReq.onsuccess @ localforage.js:1087

JS and HTML are served from http://<IP_ADDRESS>:8080

Can you include the JS you are running that's causing the error and also your server's CSP rules? This looks like a CSP directive violation, perhaps you're trying to store or retrieve data you aren't allowed to interact with in JS.
I can see the blob was retrieved successfully as the error happens inside the onsuccess handler.

tofumatt

On Sat, Sep 5, 2015 at 5:03 AM, siddo420<EMAIL_ADDRESS>wrote:

I am getting the following error message in Chrome
Refused to connect to 'blob:http%3A//<IP_ADDRESS>%3A8080/3547f91f-dd73-48a4-9bf1-233c183c22ed' because it violates the following Content Security Policy directive: "connect-src 'self' wss://<IP_ADDRESS> https://<IP_ADDRESS>".
_createBlob.type @ localforage.js:1036
_blobAjax @ localforage.js:1034
txn.oncomplete.getBlobReq.onsuccess @ localforage.js:1087

JS and HTML are served from http://<IP_ADDRESS>:8080
Reply to this email directly or view it on GitHub:
https://github.com/mozilla/localForage/issues/445

I'm having the same issue with this snippet:
<!DOCTYPE html>
<html>
  <head>
    <title>LocalForage Test</title>
    <meta http-equiv="Content-Security-Policy" content="default-src 'self'; connect-src 'self' http://conf.utahjs.com/; font-src 'self' https://fonts.googleapis.com/css/ https://fonts.gstatic.com/s/raleway/; style-src 'self' https://fonts.googleapis.com/css; child-src 'none'; object-src 'none'; img-src 'self' https://avatars.githubusercontent.com/ https://avatars.io/email/ https://avatars.io/twitter/ https://www.gravatar.com/avatar/">
    <link rel="stylesheet" href="bower_components/bootswatch-dist/css/bootstrap.css" />
  </head>
  <body>
    <script src="bower_components/localforage/dist/localforage.js"></script>
    <script src="lf-test.js"></script>
  </body>
</html>

(function () {
  'use strict';

  var store = window.localforage.createInstance({
    name: "conf"
  });

  store.getItem('schedule').then(function (err, sched) {
    if (err) {
      console.error(err);
    }
    if (sched) {
      console.log(sched);
    }
    console.log('blah');
  });

  store.setItem('schedule', {});
}());

I don't understand the security implications of adding a blanket catchall blob: to connect-src 'self' blob: https://example.com/, so I would be very hesitant to say that doing so "fixes" the problem.

How does your lf-test.js looks like?
On Sun, Sep 13, 2015, 01:50 AJ ONeal<EMAIL_ADDRESS>wrote:

I don't understand the security implications of adding a blanket catchall
blob: to connect-src 'self' blob: https://example.com/, so I would be
very hesitant to say that doing so "fixes" the problem.
—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/localForage/issues/445#issuecomment-139826217
.

--
Thodoris Greasidis
Computer, Networking &
Communications Engineer

The code I showed you is the lf-test.js

Oh, sorry, It looked confusing in my mail client :disappointed:

@coolaj86 Sadly, it may be the way around your CSP issue. localForage creates a Blob object from serialised data inside a WebSQL/localStorage database when not using IndexedDB, and retrieves the blob directly from IndexedDB otherwise.
Your CSP rules will need to allow interacting with local Blob objects. I don't think there's a way to limit this beyond "all blobs from self". I am no security expert, but I would think trusting local Blobs would be okay from a security standpoint.
If you allow the Blob from your URL (connect-src 'self' blob: https://conf.utahjs.com/ or whatnot? I'm not sure on the syntax, sorry) does it work?
If so, I won't consider this an error; it's outside the scope of localForage. :disappointed:

My browser stopped complaining ie. no error messages anymore.
I hope it'd not create any security issues.
Thanks.

Okay then, closing this for now; don't think it's a localForage issue.

I had a similar issue with an ionic app on android that uses localForage. I had to set this:
<meta http-equiv="Content-Security-Policy" content="connect-src 'self' file: data: blob: filesystem:; default-src *; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' 'unsafe-eval'"/>

As connect-src does not use wildcard for blob: you need to set everything explicitly for it.


Just added and updated events ?

Hi
I first thank you for this plugin but once installed I just find 'added' and 'updated' events.
I believed it was possible to only send the email notifications when (for example) some notes are added to a task and avoid sending notifications when the state is changed
thanks
cyril

Hi, no answer ?

Hi,
Sorry, I am not able to get your question.
Thanks to clarify.

Hi , is it now clearer please ?
thanks


Does slick work with jQuery 2?

short description of the bug / issue, provide more detail below.

I am using FoundationPress for a new project and wanted to use Slick.
It says in the docs to use jQuery 1.7+, but I am having issues getting it to work with jQuery 2
====================================================================
[  paste your jsfiddle link here  ]
use this jsfiddle to reproduce your bug:
http://jsfiddle.net/simeydotme/fmo50w7n/
we will likely close your issue without it.
====================================================================
Steps to reproduce the problem

...
...

====================================================================
What is the expected behaviour?
...
====================================================================
What is observed behaviour?
...
====================================================================
More Details

Which browsers/versions does it happen on?
Which jQuery/Slick version are you using?
Did this work before?

Yes! Definitely works with jQuery 2.0.0. Also, please try to recreate a problem you're having in a reduced test case before making an issue. There's a jsfiddle you can fork and apply whatever version of jquery you'd like. More on that in the contribution guidelines.


Add support for NixOs

This PR adds support for installing this package in NixOs using flakes.
In future, envycontrol may be added to nixpkgs. See more.

Fix url in this file after merge to use right user

Package version is not automatically picked up from envycontrol.py. Consider updating it manually

Let's watch this for v4 to properly embed the version in flake.nix. Will want it to be dynamic via GitHub action instead of hard coding the version.

I didn't catch this earlier, but FWIW Nix flakes are useful on more than just NixOS. They call their package manager Nix as well (overloaded term). I used it on Fedora and in an Ubuntu VM a year or so ago.
I was experimenting with nix develop using project specific flakes that would install everything needed for that project (e.g., tinygo, emscripten, python complied with wasi support, etc.) so I did not have to install the superset of the tools I use across all the projects I periodically work. Was kind of neat.
But the point is that the nix.flake could be useful on even macOS.


Adds release notes for upcoming 1.6 release

Signed-off-by: Fred Lifton<EMAIL_ADDRESS>

LGTM
Holding until release so these do not get pushed early.

Other than a very small comment, LGTM thanks Fred

:+1:


[BUG]: Can't create index concurrently due to transaction block

What version of drizzle-orm are you using?
0.27.0
What version of drizzle-kit are you using?
0.19.3
Describe the Bug
Creating an index with the CONCURRENTLY option throws this error: CREATE INDEX CONCURRENTLY cannot run inside a transaction block
Expected behavior
There's should be an option to run a specific migration without a transaction.
Environment & setup
Postgres 15.3

Agree, will add this option

Was this implemented?

Could the orm not be smart enough to move this step outside a transaction? That may be the better choice?
Ran into this issue and had to manually apply

The ORM should probably just include the transaction statements in the migration files. So it can enter and exit it as-needed?

Curious if anyone has a workaround for this? We have a table with over 2m rows and we keep getting deadlocks when dealing with index creations.

@Vinlock did you find a workaround?

@AndriiSherman I know that this work is being prioritized, but can you recommend any workaround? I'm dealing with a table with millions of records and the only option I can think of is to run this sql manually and then run the migration (which shouldn't run since it checks if the index exists first)
I'm trying to avoid this though

cc @L-Mario564 since i saw you were taking a look at this as well

@AndriiSherman I use a technique, where I use drizzle index generation to have a colocated, single-source-of-truth schema definition. I then have a script that extracts all CREATE INDEX ... lines from the drizzle-generated migrations to a separate custom sql file. To migrate, I use a custom migrate.ts script instead of relying on drizzle-kit. The migrate script will handle the drizzle-generated migration files (which at this point have no index definitions anymore), and then will execute the custom sql file with the indexes, ensuring that each CREATE INDEX... statement is executed as a separate transaction. Hope this helps.
schema.ts
export const profiles = pgTable(
  'profiles',
  {
    id: uuid(),
  },
  (table) => [index().on(table.id).concurrently()],
);

package.json
{
  ...
  "scripts": {
    "generate": "npx drizzle-kit generate && tsx scripts/extractIndexes.ts",
    "migrate": "cross-env DB_MIGRATING=true tsx ./migrate.ts"
  },
  ...
}

 extractIndexes.ts
import path from 'path';
import fs from 'fs';

const migrationsPath = path.join(process.cwd(), 'migrations');
const customMigrationsPath = path.join(process.cwd(), 'customMigrations');
const indexesFile = path.join(customMigrationsPath, '0000_CUSTOM_indexes.sql');

const sqlFiles = fs
  .readdirSync(migrationsPath)
  .filter((file: string) => file.endsWith('.sql'))
  .map((file: string) => path.join(migrationsPath, file));

for (const sqlFile of sqlFiles) {
  const sqlData = fs.readFileSync(sqlFile, 'utf8');

  // Find all CREATE INDEX statements (case insensitive)
  const indexLines = sqlData
    .split('\n')
    .filter((line) => /^\s*create\s+index/i.test(line.trim()))
    .map((line) => line.trim());

  if (indexLines.length > 0) {
    // Append the found CREATE INDEX statements to the custom indexes file
    fs.appendFileSync(
      indexesFile,
      `\n\n--> statement-breakpoint\n${indexLines
        .map((line) => line.replace('--> statement-breakpoint', ''))
        .join('\n\n--> statement-breakpoint\n')}`,
      'utf8',
    );

    // Remove the CREATE INDEX lines from the original file
    const updatedSqlData = sqlData
      .split('\n')
      .filter((line) => !indexLines.includes(line.trim()))
      .join('\n');

    fs.writeFileSync(sqlFile, updatedSqlData, 'utf8');

    console.log(
      `Extracted ${indexLines.length} index(es) from ${path.basename(sqlFile)}`,
    );
  }
}

migrate.ts
/* eslint-disable no-await-in-loop */
import path from 'path';
import fs from 'fs';
import { migrate } from 'drizzle-orm/postgres-js/migrator';
import { sql } from 'drizzle-orm';
import config from './drizzle.config';
import { db } from '.';

if (!process.env.DB_MIGRATING) {
  throw new Error(
    'You must set DB_MIGRATING to "true" when running migrations',
  );
}

if (
  process.env.DATABASE_URL !==
  'postgresql://postgres:postgres@<IP_ADDRESS>:54322/postgres'
) {
  throw new Error('You are running migrations in production');
}

// First run regular drizzle migrations
await migrate(db, {
  migrationsFolder: './migrations',
  migrationsSchema: config.migrations?.schema,
  migrationsTable: config.migrations?.table,
});

// Then handle custom migrations that need to run outside transactions
const customMigrationsPath = path.join(process.cwd(), 'customMigrations');
const sqlFiles = fs
  .readdirSync(customMigrationsPath)
  .filter((file: string) => file.endsWith('.sql'))
  .map((file: string) => path.join(customMigrationsPath, file));

// Use the raw connection for executing CONCURRENT index creation
for (const sqlFile of sqlFiles) {
  const sqlData = fs.readFileSync(sqlFile, 'utf8');
  const statements = sqlData.split('--> statement-breakpoint');

  // Execute each statement separately without transaction
  for (const statement of statements) {
    const trimmedStatement = statement.trim();
    if (trimmedStatement) {
      await db.execute(sql.raw(trimmedStatement));
    }
  }
}

await db.$client.end();

You can add COMMIT;--> statement-breakpoint before the CREATE INDEX CONCURRENTLY command
e.g.
COMMIT;
CREATE INDEX CONCURRENTLY "indexName" ON "tableName" ("columnName");

Another hack, to deal with drizzle auto adding BEGIN statements.
You can add COMMIT;--> statement-breakpoint before the CREATE INDEX CONCURRENTLY command
e.g.
COMMIT;--> statement-breakpoint
CREATE INDEX CONCURRENTLY "indexName" ON "tableName" ("columnName");

I'll give this a shot thank you


Jax crashes after upgrade

Description
All operations just outright crash after upgrade. For example
import jax
jax.numpy.zeros((5,5))

Outputs this error:
2023-03-28 15:01:11.001453: W external/xla/xla/stream_executor/cuda/cuda_dnn.cc:397] There was an error before creating cudnn handle: cudaErrorNotSupported : operation not supported
Array([0., 0., 0., 0., 0.], dtype=float32)

This, at least outputs array(fallback path, I presume). If I try
import jax
jax.random.normal(jax.random.PRNGKey(0),(5,5))

I get this error:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/random.py", line 137, in PRNGKey
    key = prng.seed_with_impl(impl, seed)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/prng.py", line 270, in seed_with_impl
    return random_seed(seed, impl=impl)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/prng.py", line 561, in random_seed
    return random_seed_p.bind(seeds_arr, impl=impl)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/prng.py", line 573, in random_seed_impl
    base_arr = random_seed_impl_base(seeds, impl=impl)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/prng.py", line 578, in random_seed_impl_base
    return seed(seeds)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/prng.py", line 817, in threefry_seed
    k2 = convert(jnp.bitwise_and(seed, np.uint32(0xFFFFFFFF)))
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/traceback_util.py", line 166, in reraise_with_filtered_traceback
    return fun(*args, **kwargs)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/pjit.py", line 248, in cache_miss
    outs, out_flat, out_tree, args_flat = _python_pjit_helper(
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/pjit.py", line 195, in _python_pjit_helper
    out_flat = pjit_p.bind(*args_flat, **params)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/core.py", line 2591, in bind
    return self.bind_with_trace(top_trace, args, params)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/core.py", line 362, in bind_with_trace
    out = trace.process_primitive(self, map(trace.full_raise, args), params)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/core.py", line 816, in process_primitive
    return primitive.impl(*tracers, **params)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/pjit.py", line 1269, in _pjit_call_impl
    return compiled.unsafe_call(*args)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/profiler.py", line 314, in wrapper
    return func(*args, **kwargs)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/interpreters/pxla.py", line 1934, in __call__
    results = self.xla_executable.execute_sharded(input_bufs)
jax._src.traceback_util.UnfilteredStackTrace: jaxlib.xla_extension.XlaRuntimeError: INVALID_ARGUMENT: stream is uninitialized or in an error state

The stack trace below excludes JAX-internal frames.
The preceding is the original exception that occurred, unmodified.

--------------------

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

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/random.py", line 137, in PRNGKey
    key = prng.seed_with_impl(impl, seed)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/prng.py", line 270, in seed_with_impl
    return random_seed(seed, impl=impl)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/prng.py", line 561, in random_seed
    return random_seed_p.bind(seeds_arr, impl=impl)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/core.py", line 359, in bind
    return self.bind_with_trace(find_top_trace(args), args, params)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/core.py", line 362, in bind_with_trace
    out = trace.process_primitive(self, map(trace.full_raise, args), params)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/core.py", line 816, in process_primitive
    return primitive.impl(*tracers, **params)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/prng.py", line 573, in random_seed_impl
    base_arr = random_seed_impl_base(seeds, impl=impl)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/prng.py", line 578, in random_seed_impl_base
    return seed(seeds)
  File "/home/terafo/jt/.venv/lib/python3.10/site-packages/jax/_src/prng.py", line 817, in threefry_seed
    k2 = convert(jnp.bitwise_and(seed, np.uint32(0xFFFFFFFF)))
jaxlib.xla_extension.XlaRuntimeError: INVALID_ARGUMENT: stream is uninitialized or in an error state

I've got this issue when I tried to use both local and pip cuda.
What jax/jaxlib version are you using?
0.4.7
Which accelerator(s) are you using?
GPU
Additional system info
Python 3.10 in WSL with CUDNN 8.8.1 and CUDA 12.1
NVIDIA GPU info
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 530.41.03              Driver Version: 531.41       CUDA Version: 12.1     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                  Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf            Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce GTX 1080 Ti      On | 00000000:09:00.0  On |                  N/A |
| 20%   46C    P8               13W / 250W|  10019MiB / 11264MiB |      2%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+

+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|    0   N/A  N/A        22      G   /Xwayland                                 N/A      |
|    0   N/A  N/A       487      C   /python3.10                               N/A      |
+---------------------------------------------------------------------------------------+

@hawkinsp I successfully compiled and ran one cuda sample(transpose) and one cudnn sample(mnistCUDNN) with no issues. As far as I can tell torch runs fine as well. When I used CUDA 11.8+cudnn8.6 Jax worked just fine.

I managed to get it working with CUDA 11, so problem is definitely localized to CUDA 12. Maybe it has something to do with me using Pascal GPU?

Unfortunately we don't ourselves test or support Windows or WSL2, but if you can figure out the problem we certainly would accept contributions to fix it!

Hi,
just tested jax + wsl2 and found no problem:
`
https://github.com/google/jax#installation
wsl --install -d Ubuntu-20.04
sudo su
apt update
apt -y full-upgrade
apt -y install python3-pip
pip install --upgrade "jax[cuda12_pip]" -f https://storage.googleapis.com/jax-releases/jax_cuda_releases.html
python3

import jax
jax.numpy.zeros((5,5))
Array([[0., 0., 0., 0., 0.],
[0., 0., 0., 0., 0.],
[0., 0., 0., 0., 0.],
[0., 0., 0., 0., 0.],
[0., 0., 0., 0., 0.]], dtype=float32)
jax.default_backend()
'gpu'

Window Edition: Windows 11 Pro
Version: 21H2
OS build: 22000.1696
Studio Driver
Version 531.41
NVIDIA GeForce RTX 3090
https://github.com/google/jax#installation
wsl --install -d Ubuntu-22.04
sudo su
apt update
apt -y full-upgrade
apt -y install python3-pip
pip install --upgrade "jax[cuda12_pip]" -f https://storage.googleapis.com/jax-releases/jax_cuda_releases.html
python3

import jax
jax.numpy.zeros((5,5))
Array([[0., 0., 0., 0., 0.],
[0., 0., 0., 0., 0.],
[0., 0., 0., 0., 0.],
[0., 0., 0., 0., 0.],
[0., 0., 0., 0., 0.]], dtype=float32)
jax.default_backend()
'gpu'

Window Edition: Windows 11 Pro
Version: 21H2
OS build: 22000.1696
Studio Driver
Version 531.41
NVIDIA GeForce RTX 3090
`

@mikelaud just tried same sequence with fresh install of Ubuntu 20.04. I receive the same error. Not sure what's the issue. I have 531.41 driver(though game ready), Windows 11 Pro 22H2 with build version being 22621.1413. And my GPU is 1080 Ti.

Ok, now I know that jax is broken on Pascal with WSL with any version of CUDA(less features are broken with CUDA 11, more with CUDA 12). I tested a couple of commits and figured that after XLA got upgraded from 0f31407ee498e6dba242d03f8d382ebcfcc61790 to 79ca8d03c296ede04dc9a86ce9dde79ed909dda8 all my issues started. Not sure which version of XLA is to blame, not sure how to build jax against different versions of XLA.

@terafo Well, it looks like one should create a bug within the XLA framework. After the fix on the XLA side, it will be possible to raise the version for JAX.

With recent 0.4.9 upgrade the issue is resolved since it uses more recent XLA version, in which this issue is fixed.


Unsure if this is a bug: Is gcc needed at runtime for hugo extended?

I saw that gcc is installed on an image with hugo extended: https://github.com/hugomods/docker/blob/fc7652a36b00009c67b751c48b15a213c5144a17/docker/hugo/snippets/common#L4
Is this really needed at runtime? I don't see anywhere in hugo's doc that says so.

Is this really needed at runtime? I don't see anywhere in hugo's doc that says so.

gcc is required to build Hugo extended version, but it seems a legacy issue of refactoring.

I created a PR #70, but tests fails, it's required.
https://github.com/hugomods/docker/actions/runs/8532254522/job/23373120321?pr=70
https://github.com/hugomods/docker/actions/runs/8532254522/job/23373120504?pr=70
https://github.com/hugomods/docker/actions/runs/8532254522/job/23373120645?pr=70
https://github.com/hugomods/docker/actions/runs/8532254522/job/23373121324?pr=70


cgo: inconsistent definitions for C.FaissMetricType

when I go get github.com/DataIntelligenceCrew/go-faiss . it occur.
cgo: inconsistent definitions for C.FaissMetricType.
and I have move libfaiss_c.so to /usr/lib
anyone meet this problem?

when I go get github.com/DataIntelligenceCrew/go-faiss . it occur. cgo: inconsistent definitions for C.FaissMetricType.
and I have move libfaiss_c.so to /usr/lib
anyone meet this problem?

is it faisss version problem? or golands version problem?

Probably a go version. Try updating to the latest version.

?

it`s go 1.16.9. need to update to 1.18?

Probably a go version. Try updating to the latest version.

it`s go 1.16.9. need to update to 1.18?

Probably a go version. Try updating to the latest version.

But company`s release version is go1.16.13

it `s not go version problem. it could pass at my local PC. but not Remote server.

Probably a go version. Try updating to the latest version.

I know why now.
damn it . it redeclare FaissMetricType enum in IndexFlat_c.h and IndexFlat_c.h
you could search typedef enum FaissMetricType FaissMetricType at /usr/local/include/faiss/c_api/IndexFlat_c.h(IndexFlat_c.h)
commented it out. will fix this problem.


Machine-readable results

I would like to request a feature of writing the resulting data into a machine-readable format.
Something like json, so results from different runs could be combined together.
Will you accept a merge request with this functionality?
I would replace all the calls to self.write_html_report().await?; with self.write_reports().await?;
and have a serde-serializeable structure to hold the results, which is then used to generate both the json file and the html report.

Still working on this, I made a little bit of a refactoring to avoid copying a lot of error handling regarding writing things to file, looking to finalize this probably next week


wrong type signature of custom_pydantic_encoder (with solution)

Checks

[x] I added a descriptive title to this issue
[x] I have searched (google, github) for similar issues and couldn't find anything
[x] I have read and followed the docs and still think this is a bug

Bug
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.9.0
            pydantic compiled: False
                 install path: /Users/filip/code/temp/pydantic/pydantic
               python version: 3.10.1 (main, Jan 13 2022, 15:16:24) [Clang 13.0.0 (clang-13<IP_ADDRESS>)]
                     platform: macOS-12.1-arm64-arm-64bit
     optional deps. installed: ['devtools', 'dotenv', 'email-validator', 'typing-extensions']

Pyright typecheck fails for the following implementation of custom_pydantic_encoder:
from datetime import datetime
from functools import partial

from pydantic.json import custom_pydantic_encoder

def iso_format(date: datetime) -> str:
    "Convert date to AWS ApiGateway RFC3339 format."
    return date.isoformat(timespec="milliseconds")

custom_json_encoder = partial(custom_pydantic_encoder, {datetime: iso_format})

While mypy doesn't see any issues with this code, I believe that pyright is actually correct in raising the following error:

The issue can be resolved my making the following change:
index b732cc0..8983eb4 100644
--- a/pydantic/json.py
+++ b/pydantic/json.py
@@ -90,7 +90,7 @@ def pydantic_encoder(obj: Any) -> Any:
         raise TypeError(f"Object of type '{obj.__class__.__name__}' is not JSON serializable")

-def custom_pydantic_encoder(type_encoders: Dict[Any, Callable[[Type[Any]], Any]], obj: Any) -> Any:
+def custom_pydantic_encoder(type_encoders: Dict[Type[Any], Callable[[Any], Any]], obj: Any) -> Any:
     # Check the class type and its superclasses for a matching encoder
     for base in obj.__class__.__mro__[:-1]:
         try:

Incidentally, following the change, the type signature of type_encoders is the same as the type signature of ENCODERS_BY_TYPE here - so I believe this is what was intended all along.
I'd be happy to make the PR if the change is acceptable.

Any news about this one...?


Help: selinux error during offline installation of k3s using autok3s in CentOS Linux release 7.9.2009 (Core)

[ERROR]  Failed to find the k3s-selinux policy, please install:
    yum install -y container-selinux
    yum install -y https://rpm.rancher.io/k3s/stable/common/centos/7/noarch/

time="2023-05-11T20:10:16+08:00" level=error msg="Process exited with status 1: [ERROR]  Failed to find the k3s-selinux policy, please install:\n    yum install -y container-selinux\n    yum install -y https://rpm.rancher.io/k3s/stable/common/centos/7/noarch/\n\n"

Is installing k3s selinux mandatory? It is not required in Ubuntu 18.04, and under what circumstances will k3s selinux be installed

You can see this docs: https://docs.k3s.io/advanced#selinux-support

Will support settings for environment variables


Update README.md

The existing code from the docs will result in Cannot find module 'eslint-plugin-react/configs/recommended'.  Updated the README page with a working example.

Please note, just like everywhere on github, you should be reading docs for the tagged version you're using, not just what's on main/master. For npm packages, read the published readme, not the repo's readme.

That assumption is incorrect - on almost every repo on github - whenever there are unpublished changes, as there are here.

This seems fine to close, since the readme on master is correct. Happy to reopen after the next release if there's still something that needs changing.


Make containerd dependent on mirror configuration

How to categorize this PR?

/area dev-productivity
/kind flake
What this PR does / why we need it:
Currently, the ManagedSeed e2e test is flaky, example.
In the flake, the gardenlet image cannot be pulled from the local registry because containerd is not respecting the mirror configuration and tries to pull from localhost:5001 instead, which doesn't work, obviously.
This PR introduces a dependency of the containerd unit on the mirror configuration unit to ensure containerd respects our mirror configuration.
Which issue(s) this PR fixes:
ManagedSeed Tests [It] Create Shoot, Create ManagedSeed, Delete ManagedSeed, Delete Shoot [ManagedSeed, default]
LAST SEEN   TYPE      REASON              OBJECT                            MESSAGE
19m         Normal    Scheduled           pod/gardenlet-566c4f7f7c-qfb6x    Successfully assigned garden/gardenlet-566c4f7f7c-qfb6x to machine-shoot--garden--e2e-managedseed-local-5bd79-sbkt2
19m         Normal    SuccessfulCreate    replicaset/gardenlet-566c4f7f7c   Created pod: gardenlet-566c4f7f7c-qfb6x
19m         Normal    ScalingReplicaSet   deployment/gardenlet              Scaled up replica set gardenlet-566c4f7f7c to 1
18m         Warning   Failed              pod/gardenlet-566c4f7f7c-qfb6x    Error: ImagePullBackOff
18m         Normal    Pulling             pod/gardenlet-566c4f7f7c-qfb6x    Pulling image "localhost:5001/eu_gcr_io_gardener-project_gardener_gardenlet:v1.73.0-51-ge4755962e-dirty@sha256:ed153f7736f47e2b93c0cf3316f9c975c49cecb5d3bf43ec51fcef38d61960ed"
18m         Warning   Failed              pod/gardenlet-566c4f7f7c-qfb6x    Failed to pull image "localhost:5001/eu_gcr_io_gardener-project_gardener_gardenlet:v1.73.0-51-ge4755962e-dirty@sha256:ed153f7736f47e2b93c0cf3316f9c975c49cecb5d3bf43ec51fcef38d61960ed": rpc error: code = Unknown desc = failed to pull and unpack image "localhost:5001/eu_gcr_io_gardener-project_gardener_gardenlet@sha256:ed153f7736f47e2b93c0cf3316f9c975c49cecb5d3bf43ec51fcef38d61960ed": failed to resolve reference "localhost:5001/eu_gcr_io_gardener-project_gardener_gardenlet@sha256:ed153f7736f47e2b93c0cf3316f9c975c49cecb5d3bf43ec51fcef38d61960ed": failed to do request: Head "http://localhost:5001/v2/eu_gcr_io_gardener-project_gardener_gardenlet/manifests/sha256:ed153f7736f47e2b93c0cf3316f9c975c49cecb5d3bf43ec51fcef38d61960ed": dial tcp [::1]:5001: connect: connection refused
18m         Warning   Failed              pod/gardenlet-566c4f7f7c-qfb6x    Error: ErrImagePull
4m34s       Normal    BackOff             pod/gardenlet-566c4f7f7c-qfb6x    Back-off pulling image "localhost:5001/eu_gcr_io_gardener-project_gardener_gardenlet:v1.73.0-51-ge4755962e-dirty@sha256:ed153f7736f47e2b93c0cf3316f9c975c49cecb5d3bf43ec51fcef38d61960ed"

Related to https://github.com/gardener/gardener/issues/6897
Special notes for your reviewer:
/cc @rfranzke
Release note:

NONE

/cherry-pick release-v1.73

/cherry-pick release-v1.72

/cherry-pick release-v1.71

/retest-required

/override pull-gardener-e2e-kind-ha-multi-zone-upgrade

/retest


Decide on a pattern for regularly updating config.dot or remove it

10 years ago with RUBY-868 (internal) / 26580d0eac250919cdb51a49e87a27919edf8d60, we added a config.dot file to the repo to power a diagram of the agent's configuration options.
We should decide as a group of the current value of such a diagram and either establish a pattern to keep the config.dot file up to date or remove it from the repository.

Relates to #1284


Error installing pycups lib

Trying to install the library "pycups" simply including in "pip.txt" I get the following error:
creating build/temp.linux-x86_64-3.6
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DVERSION="2.0.1" -I/usr/local/include/python3.6m -c cupsmodule.c -o build/temp.linux-x86_64-3.6/cupsmodule.o
unable to execute 'gcc': No such file or directory
error: command 'gcc' failed with exit status 1
Possibly I need to add something to the doodba configuration in order to run "gcc".
Thanks a lot.

I tried running gcc from a running doodba odoo container, and it exists.
What are the contents of the pip.txt?

I tried running gcc from a running doodba odoo container, and it exists.
What are the contents of the pip.txt?

This is my pip.txt:
git+https://github.com/OCA/openupgradelib.git@master
unicodecsv
unidecode
python-barcode
psycopg2-binary
pysftp==0.2.8
xlsxwriter
xlrd
pyOpenSSL
zeep
qrcode[pil]
xmlsig
cachetools
pycups
pycountry

This is my pip.txt:
git+https://github.com/OCA/openupgradelib.git@master
unicodecsv
unidecode
python-barcode
psycopg2-binary
pysftp==0.2.8
xlsxwriter
xlrd
pyOpenSSL
zeep
qrcode[pil]
xmlsig
cachetools
pycups
pycountry

You need to add in apt_build.txt the cups dev library and on apt.txt, the cups library, but this is not something of Doodba, but a requirement of the cups pip package that you have to do in any system.

You need to add in apt_build.txt the cups dev library and on apt.txt, the cups library, but this is not something of Doodba, but a requirement of the cups pip package that you have to do in any system.

For pycups this is the content that has worked for me from the apt.txt and apt_build.txt files, maybe it can help someone who tries to install this library.
build-essential
python3-dev
libcups2-dev

For pycups this is the content that has worked for me from the apt.txt and apt_build.txt files, maybe it can help someone who tries to install this library.
build-essential
python3-dev
libcups2-dev


Jv/update docs content 3.68.2

Description
Update docs
Checklist

[ ] Investigated and inspected CI test results

Testing Performed
See above

gke-ui-e2e-tests failure in CI looks like a flake that has since been fixed in main development branch


Apeksha patch

This Pull Request resolves Issue #
Description:
In this Pull Request we have done the following additions/edits for the code:

i claim

i claim

I claim is supposed to be commented on Issues not Pull Requests @Apeksha1997

Are there any updates here or should we close the PR and label it as spam?

spam!


Support mutable Json DOM for System.Text.Json

https://learn.microsoft.com/en-us/dotnet/standard/serialization/system-text-json/use-dom

implemented in https://github.com/mikhail-barg/jsonata.net.native/releases/tag/v2.5.0


Bump npm version

I forgot to bump the npm version in my prior Pull Request.

Please, don't forget to publish the new version.
Nice job, by the way 😄

Published, thank you for the contribution @natete


Radio buttons are unlabeled

I interviewed a company called Silktide at CSUN with a wicked cool web accessibility tool. One of the things that's built into the free Chrome extension is a virtual screen reader. You don't have to learn how to run a screen reader, because it steps through it for you.
It found that the two radio buttons for the two ways to view the generated passwords are both unableled.  I highly recommend people install this Chrome extension - you can even run in on a local repo in the browser before pushing up changes.  Really cool.
I don't think I'll have time to fix this right away so if @pricemi115 wants to work on it that's fine.

Confirmed there are now labels on the radio buttons in VoiceOver


NIFI-3149 Adding proper literal support for number operators ('-' and…

… '+') to ANTLR parser and UI highlighting

Reviewing...

+1 LGTM, tried various combinations of +/- and verified the syntax highlighting is supported. Thank you! Merging to master