doc(hmac): Make endian_swap / digest_swap consistent

This commit revises CFG.endian_swap to be consistent to
CFG.digest_swap.
To make it clear, an example is added to the document.

@cindychip I didn't revise DV env yet. I will try to revise and merge into this PR.

#13497 #12895

@jadephilipoom can you give this a look also? I believe you initially raised this inconsistency in the CSRs as part of the D3 review.

I do not have CW310 to test the failure. Tried `//sw/device/tests/crypto:ecdsa_p256_verify_functest_sim_dv` and passed. Is this sufficient?

I do not have CW310 to test the failure. Tried //sw/device/tests/crypto:ecdsa_p256_verify_functest_sim_dv and passed. Is this sufficient?

What about //sw/device/tests/crypto:ecdsa_p256_verify_functest_sim_verilator? That one should agree with the FPGA result.


Binary of sqlite3 is not getting updated

Installed a new node version and executed rebuild on sqlite3. But sqlite won't update its binary. It stays in the old NODE_MODULE_VERSION.
installing with "--build-from-source" does not help either.
What is needed to update the binary for sqlite3?
sqlite3 is the only plugin that does not update its binary. All other DB drivers work fine,

Not sure if this is related but yarn install is erroring with node-pre-gyp http 403 https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v3.1.13/node-v72-darwin-x64.tar.gz for us.

@wsjwa @richardscarrott what are the steps to reproduce this issue? I'm not fully clear about how to check this in the original report. Also, since this is several months old, is this bug still valid since SQLite's binary has been updated since?


Some questions about FAST.Farm

Q1: In the wake dynamics module of the FAST.Farm primary input file, the value of NumRadii is 40, and value of dr is 5.0. This means 2(NumRadii-1)dr=2×39×5=390m, but it is out of the low-resolution domain in LES example, I don't understand how it works.
Q2: In the wake dynamics module of the FAST.Farm primary input file, the value of NumPlanes is 140. So what's the distance between the plane and the plane?
See the picture👇(I have not changed the parameter values)

Q3: In the visualization file generated by FAST.Farm, how can I add the visualization file of turbulence intensity and mean wind speed?
Q4: Is there a separate manual for Super Controller?  Can you send me a copy if you have one?
Those are all my questions about FAST.Farm, and I would appreciate your answers!

@jjonkman @NRELAdmin

Dear @Helloczm,
Here are my answers to your questions:

I agree with your math.  FAST.Farm permits the wake planes to extend beyond the boundaries of the low-resolution domain, or even leave the domain entirely.  But it is important for the spatial averaging to cover a wide area beyond the wake boundary (especially for larger values of Mod_Meander), so, even if portions of a given wake plane extend beyond the boundaries of the low-resolution, this is better then having the wake planes too small.

The distance between each wake plane will differ between each pair of planes, but will equal V_plane_norm*DT_Low, where V_plane_norm is the convection speed of the wake plane normal to the wake plane, calculated by spatially averaging the disturbed wind velocity field (ambient wind + wake deficits) and projecting along the unit vector normal to the plane.

I'm not sure I understand your question.

There is not a separate manual, but the super controller available in FAST.Farm is documented here and here.

Moreover, the Modeling Guidance chapter of the FAST.Farm documentation provides guidance on setting many of the FAST.Farm input parameters.
Best regards,

Dear @Helloczm,
Here are my answers to your questions:

I agree with your math.  FAST.Farm permits the wake planes to extend beyond the boundaries of the low-resolution domain, or even leave the domain entirely.  But it is important for the spatial averaging to cover a wide area beyond the wake boundary (especially for larger values of Mod_Meander), so, even if portions of a given wake plane extend beyond the boundaries of the low-resolution, this is better then having the wake planes too small.
The distance between each wake plane will differ between each pair of planes, but will equal V_plane_norm*DT_Low, where V_plane_norm is the convection speed of the wake plane normal to the wake plane, calculated by spatially averaging the disturbed wind velocity field (ambient wind + wake deficits) and projecting along the unit vector normal to the plane.
I'm not sure I understand your question.
There is not a separate manual, but the super controller available in FAST.Farm is documented here and here.

Moreover, the Modeling Guidance chapter of the FAST.Farm documentation provides guidance on setting many of the FAST.Farm input parameters.
Best regards,

Dear @jjonkman ,
Thank you very much for your answers to my questions, which are very helpful to me!
Now I want to improve on my third question:
Q3: The FAST.Farm wind visualization file I have so far only shows the wind speed, but I also want to get the average wind speed and turbulence intensity visualization file, what should I do?
Best regards,

Dear @Helloczm,
The visualization output from FAST.Farm contains the instantaneous wind velocity at each output time step.  You can derive the average wind speed, wind speed standard deviation, turbulence intensity, etc. from this via customized post-processing, but that functionality is not built into FAST.Farm.
Best regards,

Dear @Helloczm,
The visualization output from FAST.Farm contains the instantaneous wind velocity at each output time step. You can derive the average wind speed, wind speed standard deviation, turbulence intensity, etc. from this via customized post-processing, but that functionality is not built into FAST.Farm.
Best regards,

OK, thanks you very much!


Need a clear button for each row

Add a tick box for each frequency and buttons to tick and un-tick all


Excluding model media from build

I have a model containing a Filefield() that I'm trying to bake. This file is for internal use only, but I'm finding that when I run manage.py build it copies this file (which can be quite large) into my build directory. I have BuildableDetailView class configured for this model but this file isn't publicly served anywhere. How do I exclude it from being caught in the media sweep?

Nevermind. I see it just copies over the entire MEDIA_ROOT, so temporarily clearing that for the build command fixes the problem.


probe: latent jailbreak

https://arxiv.org/pdf/2307.08487.pdf
https://github.com/qiuhuachuan/latent-jailbreak

Duplicates #234


[Accessibility] ‘Road’ drop down is not getting collapsed by pressing esc key.

Keyboard user will not be able to collapse the control and cannot access the control efficiently if the control is not collapsing through by pressing Esc key.

This repo is for the V8 Code Samples code snippets, not the Bing Map SDK control itself. Please use the feedback mechanism within Bing Maps to report this issue.


future prompt should have it's own visual identity

currently using ChapterOpening component as placeholder:

Ideally, it should:

visually distinct from the ChapterOpenings
encourage people to read the full text
encourage people to not click away too quickly
encourage people to feel they have achieved something great

implemented in #142


Synchronize example app package-lock.json (#1000)

Pull request #1000 which updated some dependencies
/package-lock.json was recently merged. This synchronizes those same updates back into
the example/package-lock.json file.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Easy Dynamics Automation seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


⚠ Bofrost.at has degraded performance

In 1e2c08f, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2317 ms

Resolved: Bofrost.at performance has improved in badb443 after 25 minutes.


Multiple particles decrease frames per seconds

I am creating an effect with particles, where when passing the mouse these particles repel. The problem is that the animation of the particles is executed with low fps.
I am using Firefox Dev Edition, Windows 10, Radeon 550 Series GPU.
https://codepen.io/AlainBarrios/pen/MRXJxg?editors=0100 This is the codepen.

So I'm not on the pixi team, but I took a look, and it looks like one big performance hog is you're doing a square root 100000 times a second in your distance check, which is an expensive operation. Instead, just check if the squared distance is less than the squared radius. I updated your pen: https://codepen.io/anon/pen/wZEbob?editors=0010

Chrome also has a very good profiling tool that can help you isolate which functions are taking your CPU time.

I have removed some features and added what you said, it has improved in Chrome but in Firefox it remains the same.
Firefox

Chrome

Have you profiled it in firefox to see where your slowdown is? If not, that's where you should start.
A couple optimization ideas:

Use less particles
You're putting lots of particles on the black areas, which aren't seen, so they're wasting resources. You could use a library like opentype.js to get vectors of the letters, so that you only fill the letters.
You're moving and doing a mouse hit check for every particle every tick. If you put your particles in an optimization structure like a kd-tree, you could do a lookup for the mouse location to only get the particles that are close enough. Once a particle had returned to its original location, you could mark it as "inactive" so that it doesn't tick until the mouse comes near it again. However, the area your mouse interacts with is big enough that this might actually be slower, not sure.

I have been able to fix some frames https://codepen.io/AlainBarrios/pen/BEGYoV?editors=0010.
Thanks you!.


when i use keyuserhandler as botconrollclass instead of simpleuserhandle this error comes out

SS:https://gyazo.com/96eed29f0c3e42fda9f1915a95b35a1d

There's no "keyuserhandler" in the repo so that's probably the problem. :grinning:

@scholtzm please help me with the bot i can pay :(

@scholtzm  add me on skype:ika.diablo
steam:http://steamcommunity.com/id/james_hunter666/

#427 #527
This is an issue tracker, not your personal helpdesk. Each one of your comments generates ~200 email notifications.
You have been already told that once.


python: can't open file 'bot.py': [Errno 2] No such file or directory

how can i solve it？

download it again

Could be a lot of different reasons for this error. Once you have python installed and the dependencies, navigate to the folder and either run the Launcher.bat or enter /scripts and try double clicking on bot.py


Add tests

Merging early so that basic project information is corrected on PyPi before committing to longer term improvements.


Revisit concerns about 2 Docker files for CI and local dev

The concerns are discussed here:
https://github.com/operator-framework/rukpak/pull/102

0.3 candidate


Added Bolivian providers

Added Bolivian providers for Person, PhoneNumber and Address

@josegus bump, could you please review comments? Thanks a lot

Im going to close this PR since it has been stale for another 14 days. Feel free to raise a new PR or reopen it.
Thanks!


Update conditions files to match original NESO examples

Updates the example conditions.xml files in config_files to exactly (bar tab to space subsititutions) match the two_stream and 2Din3D-hw examples in https://github.com/ExCALIBUR-NEPTUNE/NESO/blob/main/examples/Electrostatic2D3V/two_stream/two_stream_conditions.xml and https://github.com/ExCALIBUR-NEPTUNE/NESO/blob/main/examples/H3LAPD/2Din3D-hw/hw.xml respectively.
The current files reduced the number of simulated time steps, presumably to allow for quicker iteration when testing, and for the 2Din3D-hw case was based on the simpler 2Din3D-hw_fluid_only variant. As we now support overriding the parameters when running the task, I think having the conditions match the original NESO examples for consistency makes more sense, with it still possible to quickly override the parameters when running to reduce the compute time required.

All looks good to me. I assume the other parameter that this is missing from the 2Din3D-hw/conditions.xml file;
            <!-- Turn on energy, enstrophy output -->
            <P> growth_rates_recording_step = 1 </P>

is only there for writing output, so can just be added from the command line if we need this information?

Ah good spot, looking at the blame for the original source file in the NESO repository it looks like these lines were added in a more recent commit so it looks like I didn't pull in the latest changes on NESO before copying over. I'll update this now, though I guess it's likely they will still end up diverging at some point.


Version 2.2.0

Landed in https://github.com/metarhia/metaconfiguration/commit/6172c454bae46b350e71fe5769362e25b00b829e and https://github.com/metarhia/metaconfiguration/commit/142694f79091b42a84f0882e0d9458c3158923df


combine running and releasing notebooks so the released notebooks have visualisations

Should resolve #31 although needs proper testing

I think it is going to make sense having this as a separate task, which runs indepedently of and after the run_notebooks_and_release_workspaces task.
I anticipate I am going to need to run it quite a few times to get it working properly, and therefore would also beneift from an option visualize_notebooks appearing here:

So, the task would run after the release is complete, and therefore may reclone main, push, pull etc? I know its a bit repetitive but having it baked into the release is gonna cause a lot of bugs in testing and development.
I think my most common use case is going to be wanting to run this without rerunning all the script tests and doing a release.
I also just did a quick check with a notebook, and found that including all visualization increased its size to 3MB. I think I need config files specifying notebooks in order to prioritize a subset to keep sizes under control.

OK makes sense should be doable as an independent step alongside the two original steps resposible for running notebooks and releasing notebooks

OK it's now a distinct job.

You have to explicitly set update_notebook_visualisations='true' when triggering the build for the job to run
Only notebooks named in autobuild/config/visualise_notebooks.yaml (similar to no_run.yaml) will be run


Remove comptime feature

Problem
This is a tracking issue to remove comptime from the language.
Happy Case
.
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response

Please add issues related to removing comptime here

Related:

https://github.com/noir-lang/noir/issues/280
https://github.com/noir-lang/noir/issues/1188

Related:
#445
#793

I think comptime may actually still be needed for for loops. Since in regular constrained code those are still required to terminate. I suppose we can replace it with something else like a more ad-hoc check that the for loop bounds are constant, but this would break existing code.

I just hit a use case where a comptime Field might still be helpful...
I wanted to instantiate an array with length equal to: the sum of the serialised lengths of two structs.
I.e. I have two structs. Each struct has a method which returns the comptime Field "length" of the struct (when that struct is serialised into an an array of fields).
let struct1_length: comptime Field = Struct1::get_serialised_length();
let struct2_length: comptime Field = Struct2::get_serialised_length();
let combined_length: comptime Field = struct1_length + struct2_length;
let mut combined_arr = [0; combined_length];

let mut insertion_index = 0;
spread(combined_arr, struct1, insertion_index);
insertion_index += struct1_length;

spread(combined_arr, struct2, insertion_index);

Isn't the only way to do this with comptime Fields?

I don't believe we support initializing arrays with a comptime FIeld size at all currently. It must be an actual constant instead, which is more restrictive.

Oh. Whoops. Can we generate constants from other constants at compile time? That's what this example would need. (I.e. specifying the length of an array at compile time, by doing simple arithmetic on other constants).

Not if they're stored in local variables or parameters, that's the scope of comptime. Constants are limited to the type system, globals, and basic arithmetic on those.

struct Foo { }
impl Foo {
    fn get_constant() -> comptime Field { // or constant, or something
        5 // <-- this constant isn't stored in a local variable.
    }
}

let my_arr_length = Foo::get_constant() + 1;
let my_arr = [0; my_arr_length];

^ I was trying something like this.
error: Cannot find a global or generic type parameter named `plain::my_arr_length`


[Workflow] Quickstart for Go SDK

Creating a Workflow sample in the Quickstarts based on this docs PR. https://github.com/dapr/docs/pull/3895

/assign

@mikeee - Any update on this?

I'm working through this. I still need to get the SDK finished and a release candidate cut before this can be merged.

Can be closed


Feature request: Separate accent colors for day and night theme

Is there an existing issue outlining your problem?

[X] I am using the latest version of the provided userstyle.
[X] I have searched the existing issues and they do not solve my problem.

What userstyles are you seeing the problem on?
lbl:twitter
Describe your problem.
I have Twitter switch from light to dark theme based on Windows theme, which switches based on sunrise/sunset.
I love the green accent color on the dark palettes, because it's a beautiful pastel green. I do not like the dark saturated green of the Latte palette I use during daytime, though. I would like to be able to set Catppuccin for Twitter to use Latte + Flamingo during the day and Mocha + Green during the night. I'm sure there's a hacky way I could do this, such as changing the actual hex values in the lookup table, but I feel like that would be a rather unclean way to do this, and modifying the CSS myself would result in either them being broken every update, or conversely, depriving me of updates. I'm not familiar at all with CSS pre-processors, so my attempts to try and figure out how to change it more cleanly failed.
Attach screenshots.
No response
What browser(s) are you seeing the problem on?
Vivaldi 6.7.3329.31 (Stable channel) (64-bit)
Any additional comments?
No response

The largest issue with twitter, is that the webpage is full of inline styling. This makes it take a significant amount of time to create and maintain, adding a light mode would be nice but a very strenuous task.

The largest issue with twitter, is that the webpage is full of inline styling. This makes it take a significant amount of time to create and maintain, adding a light mode would be nice but a very strenuous task.

I don't understand. Catppuccin for Twitter already has a working "dark/light" mode switch going on. It just ignores Twitter's own theme choices and simply asks you to run blue color + pure black Twitter, then rewrites the colors. Effectively, this is white theme being written over AMOLED black.
https://github.com/catppuccin/userstyles/assets/3785923/c253b23f-4a69-4954-ab62-62f54926d6f6
What I'm asking is not about that. That already works. What I'm asking is to have separate accent colors (i.e. Rosewater for Latte WHEN the "light mode" toggle is on, and Green for Mocha when the "dark mode" toggle is on). I think if it is possible to completely change the entire theme on the fly based on system's light/dark mode setting, then it should be able to do so with the accent color also, right?

Ahh, I understood it as a dark/light switcher and since the first thing I saw when moving to light mode was this

But it should be possible to do this. Curious whether its worth the effort though. I'd like to hear @uncenter views.

I should mention that I incorrectly believed I was using the latest version of the userstyle. Since I tried to make changes to it, it disabled automatic updates, most likely. The newest version doesn't have the feature I'm requesting either, but I should have checked before I hit the tickbox.

Ahh, I understood it as a dark/light switcher and since the first thing I saw when moving to light mode was this
But it should be possible to do this. Curious whether its worth the effort though. I'd like to hear @uncenter views.

I mean it is a lot more work for both updating all 80-something userstyles and just more confusing options for users to pick from. Seeing as you are the first person to request this, maybe we leave this open for a little while and see if others also want this?

I +2 this feature request, and it shouldn't be difficult at all to do:

@trinkey it's pretty clearly not about the difficulty, as we know we already have dark and light flavor options. The question is how often will people use this? If 10/1000 people want to use this, the other 990 have to then change two dropdowns just to change their accent color if they want it the same for both. How much additionally complexity are we wanting to introduce? Making this change happen is difficult with over a hundred userstyles now. This will also break existing setups and we can't easily migrate users.

I'm going to close this as not planned for now, though I don't think including this in the docs would be wise either; the usage instructions are already pretty complicated and I don't want to add more confusion/complexity, let alone how annoying it would be to change this across all the userstyles you use 😃


refactor: modify the display of proxy-selector card

This pr mainly made the following changes：

fix some code style bugs which cause “npm run lint” to report errors
change the color of the 'delete' button
Considering that time is not valuable information, the time on the card is removed, and props and time are displayed in the format of a floating card.

before:

after:


Add more support for including discordpp in other CMake projects

This will export a target called discordpp::discordpp which projects can include with find_package, and will add an alias target by the same name so that adding it as a subdirectory has the same behavior. I had to bump the minimum version to 3.8 because CMake forbids setting the cxx standard properties on interface libraries, and the cxx_std_14 feature is first available in 3.8. Additionally I have added a version range to up to 3.18 which is the version I tested on. This doesn't restrict people from using newer versions, but it sets CMake policies for versions within the range.

Hmm, that's interesting. I moved a little bit in this direction on the dev-restructure branch, I'd really prefer to keep sweeping CMake changes there for now.
Currently the plan was to merge dev-restructure for a 1.0 release once I'm happy with it with CPM support though this might be a good offering too. I'm not certain if installing a singular version of Discord++ on a system is the best idea but it's something to think about.
Are you on the Discord server?

I should PR this to that branch then. Any way to change that without recreating the PR?
I'm not in the discord server, but I can join it.

This branch has conflicts that must be resolved <- does not seem to work @JosiahWI

Could you elaborate on what doesn't work? Without steps to reproduce I can't tell what the issue is. When I tested this before initiating the PR, it worked as expected.

I need to commit one more thing before this is mergeable. I need to export the nhlomann-json target and the discordpp target, both, for this to work properly.

Could you elaborate on what doesn't work? Without steps to reproduce I can't tell what the issue is. When I tested this before initiating the PR, it worked as expected.

I think he was talking about the merge conflict after you changed branches

This is now tested with a nlohmann_json installation and configures correctly.

Closing, because I reconsidered the scope of discordpp and I don't think this is helpful to the project for all the work required to do it for every plugin.

Yeah, I'd like to put some work into making stuff work easily with FetchContent or similar. I think that's maybe more convenient.


[WIP] 1.8.9 Multipart

See #75

[x] Basic Cable
[x] Basic modem
[x] Block cable connections with mulitparts (Chisel and Bits is probably the easiest way to test)
[x] Internal cable connections (attach other nodes to network)
[x] Override item cable
[x] Forward & backward part converter
Reuse nodes from original cable - is this possible?
[x] Wireless bridge
[x] Optimisation.

I'm going to need to add a lazy NBT reader otherwise peripherals are not connected at runtime.
@ElvishJerricco Is there anything you want add?

I'd have to take a detailed look. I haven't had time for minecraft in the past month or two (as evidenced by my absence =P) so I'm not too up to date on how this API works or what had to change in this pull request. But I'll take a look over the next day or two.

Chill, I have far too much free time at the moment :stuck_out_tongue:.


After docker install there is no tokenfile in /var/lib/gpustack

Cant find /var/lib/gpustack/token file on server node to connect worker as per https://github.com/gpustack/gpustack/blob/fbb5359f2c459cf34169d3f47b401aaf450a029c/docs/tutorials/setting-up-a-multi-node-gpustack-cluster.md?plain=1#L41
Steps to reproduce

docker run -d  -p 80:80 -p 10151:10151 --ipc=host -v gpustack-data2:/var/lib/gpustack gpustack/gpustack:main-cpu -t gpustack-cpu
Connect to container "docker exec -it 6 bash"
Check for token "cat /var/lib/gpustack/token" - there is no such file
Content of /var/lib/gpustack/ is this:
cache  database.db  initial_admin_password  jwt_secret_key  log  worker_name

Result
No token file
Expected behavior
token file should be generated and used to connect worker node
Environment

GPUStack version: gpustack/gpustack:main-cpu, tried also with container gpustack/gpustack with same result
OS: Linux Rocky
GPU: CPU only

Do you see any error in container logs?

I can reproduce with the main-cpu image. The main-cpu image is still in development and it should be a bug. We will do more investigation. Thanks for reporting this.

For the time being, you can try the standard installation without docker. It will generate a token successfully. We use pipx venv for gpustack installation so it will not mess up your environment. And you can uninstall it by running the /var/lib/gpustack/unisntall.sh script.

Sorry. Made a mistake. You used
docker run -d -p 80:80 -p 10151:10151 --ipc=host -v gpustack-data2:/var/lib/gpustack gpustack/gpustack:main-cpu -t gpustack-cpu
-t is the parameter that will be passed to the GPUStack startup command, which is the token. So gpustack-cpu will be the token, and the random token will not be generated. I didn't notice this and assumed it was a -n.

Thank you, I overlooked -t as well as I was using it previously to build and tag image myself.
Closing this now


Inconsistent use of camelCase when dealing with Viper & configuration data

I was trying to help @xiaomingplus with a themes question (https://discuss.gohugo.io/t/can-hugo-t-params-custom-a-directory/2481) and got confused on the way Hugo is using Viper. It looks like Viper is not case-sensitive, so things like ContentDir are spelled differently in different parts of the code.
viper.GetString("ContentDir")

viper.GetString("contentDir")

$ hugo config | grep -i contentdir
contentdir = "content"

This was really confusing since I thought that SetDefault("ThemesDir", "themes") in hugo/hugo.go would automatically pick up ThemesDir in the config file. If I change a line in hugolib/site.go
func (s *Site) absThemeDir() string {
	return helpers.AbsPathify(viper.GetString("themesDir") + "/" + viper.GetString("theme"))
}

to use ThemesDir rather than themesDir
func (s *Site) absThemeDir() string {
	return helpers.AbsPathify(viper.GetString("ThemesDir") + "/" + viper.GetString("theme"))
}

Hugo/Viper picks up the path like I'd expect. I think that it's a bug, but I don't know which part is the bug - Viper or Hugo.

I don't think this is a bug.  All of the keys are converted to lowercase prior to lookup by Viper.  We may be inconsistent in using camelCase or TitleCase when we reference them in our viper.GetString calls, but Viper doesn't care.  See here

@mdhender,
Can we close this issue?

Steve suggested that I create a test case to determine if this is Hugo or Viper. I'm planning on doing that this weekend.

I've tried recreating it and running with the following test in hugolibs/site_test.go and can't duplicate it, so I'll close this issue.
func TestGetString(t *testing.T) {
	viper.Reset()
	defer viper.Reset()

        var myTomlExample = []byte(`

        ThemesDir = "/foo/bar/themes"
	theme = "vanilla"

        `)

        defaultValue := "themes"
        expectedValue := "/foo/bar/themes/vanilla"

        viper.SetDefault("ThemesDir", defaultValue)
        assert.Equal(t, defaultValue, viper.GetString("themesDir"))
        assert.Equal(t, defaultValue, viper.GetString("ThemesDir"))

        viper.SetConfigType("toml")
        viper.ReadConfig(bytes.NewBuffer(myTomlExample))

	assert.Equal(t, expectedValue, helpers.AbsPathify(viper.GetString("themesDir") + "/" + viper.GetString("theme")))
	assert.Equal(t, expectedValue, helpers.AbsPathify(viper.GetString("ThemesDir") + "/" + viper.GetString("theme")))
}


Update cli-utils dependency and code in thirdparty

Update the cli-utils dependency and the code from cli-utils in thirdparty.

/retest


BUG MITIGATION: .mjs should not resolve before .js files

Support for .mjs files added in #3239 did not account for npm libraries which ship native mjs files alongside js files. This accounts for this by ensuring .js files resolve before their accompanying .mjs file. Note that this is not an ideal end state since selecting a .mjs over a .js extension should be the result of whether import was used instead of require() in a node environment with native ESM support (currently via --experimental-modules). Instead, this change just always selects a .js extension before the .mjs extension if it exists.
This unbreaks support for using GraphQL (relay, apollo, etc) within create-react-app projects.

cc @gaearon @Timer - it would be great if we could get this into a point release soon

Hmm, is this a new problem (as in did these modules just now start shipping mjs and did not previously)?
This is the first we're hearing of this bug report.

Yes, some graphql packages just started releasing node-esm ready modules to npm for support with node v9's --experimental-modules and in anticipation of node v10.
Node has a new module resolution strategy which will resolve to a .mjs file from a native import statement, but continue to resolve to a .js file from a require(). To support both, npm modules can be published that have both .js and .mjs variations of each file in the bundle.
However this conflicts with react-scripts's jest-config which before this diff always resolves to .mjs if one exists before .js, even if the environment is not using native modules - which results in seeing syntax errors like reported in https://github.com/graphql/graphql-js/issues/1248
Since Jest wraps the require() flow, and not the import flow, I believe Jest doesn't have support for native node-esm just yet, however resolving .mjs files when a .js file isn't found is still a reasonable thing to do since user's source code may start using .mjs along with the babel transform (as opposed to node_modules code which is not transformed by babel)

This seems like an easy fix. We should get this intomaster as well as next.

From my understanding, this problem most likely arises because imports are happening without specifying file extension.
When Jest loads a package, we look at the main key in package.json, when webpack loads a package, we look at the module key and fallback to main.
In a normal scenario, main would contain index.js and module would contain index.mjs.
These files would respectively import etc.js and etc.mjs files, but instead, specify just etc, which falls back to our module resolve ordering which disregards the means of import.
Given this reasoning, I'd go as far to say that this isn't the fix we want -- we can release this in a 1.x.y release for compatibility reasons, but I'm against porting this to next because it's not the desired behavior.
I'd like to know how Node handles this, given an import specifying just etc, does it prefer etc.js when invoked via require and etc.mjs when invoked via import? What's the fallback look like? What happens when using import()? Does Node itself bomb out in this situation?
We definitely need to figure this out for the 2.0 release.
@leebyron can you retarget this PR to the master branch please? We'll want a different solution for next as described above.

Give me a moment to change the base - I can't do that from the github UI without wreaking havoc.
Before I do that, let me try to answer some of your questions.

I'd like to know how Node handles this

Node handles this by never attempting to load a .mjs file from a require() and never loading a .js from an import. So import "./example" may try to look for: ./example, then ./example.mjs, or ./example/index.mjs, but never ./example.js. Similarly require("./example") may look for ./example.js but would never look for ./example.mjs. In other words, the existing module resolution algorithm for require() was not changed at all, however a new module resolution algorithm was introduced for import.

Given this reasoning, I'd go as far to say that this isn't the fix we want

I definitely agree - this is a mitigation. I would argue that .mjs files should not be considered at all from a require statement in Jest - instead Jest should hook Node's new import resolution API in which case it should look for .mjs files. Though I know that we're still in the strange world of babel transpilation and so this isn't always very well defined, and that folks may choose to save their ES6+ESM files as .mjs files.
This mitigation is specifically handling the case where both ./example.js and ./example.mjs exist in the same location. The .mjs file is going to include ESM syntax, and if it happens to be found in the node_modules folder then babel isn't going to transform it. In this scenario instead of resolving the .mjs file first, we should be resolving the .js file first.
Tools like Webpack and Rollup should be doing the opposite - looking for .mjs files before .js files - since they prefer the ESM format if it exists.

When Jest loads a package, we look at the main key in package.json, when webpack loads a package, we look at the module key and fallback to main.

Yes, and node also only looks at the main key in package.json, regardless of whether require() or import was used to arrive at that package.json file - which is why this pattern of .js and .mjs files next to each other is likely to become more common as native ESM moves from experimental to shipping.

I'm trying to figure whose court the ball is in to handle this (for 2.0).
I could see arguments for us doing something complex, I could also see arguments for Jest to handle this.
It's almost as if we need a moduleFileExtensions and esModuleFileExtensions key to specify extensions for require/import.

I like the idea of a separate esModuleFileExtensions. I think this should probably be within Jest's domain. If it encounters an npm module using native ESM then Jest should be defining the right behavior. There's a bit of runway to get this right in the meantime. Node v9 only supports native ESM with --experimental-modules, so it's not going to be all that common until the major version that supports it without a flag.

Tools like Webpack and Rollup should be doing the opposite - looking for .mjs files before .js files - since they prefer the ESM format if it exists.

Just checked this out and Webpack does look for .mjs before .js

This also killed mjs efforts for the Apollo ecosystem 😢

We don't want to rush these changes out since there's not a ton of +1s.
Let me reiterate -- this is completely solvable in user land in the mean time (which shouldn't be long).
Source files just need to be updated to explicitly import their file.js or file.mjs counterpart instead of file.

@Timer so you are saying that if foo.mjs changes import bar from ./bar to import bar from ./bar.mjs it would work?

I definitely support coming up with the right long term plan, which probably incorporates adding support for native ESM to jest, however in the meantime I still would love to see this merged and released as soon as possible since it’s a low impact bug fix that unblocks using CRA with the graphql ecosystem

This definitely sounds bad. Is this only broken when running tests via Create React App? Is it only the Jest config that needs to be updated or is there also an issue with our webpack config?

I don’t think there’s anything wrong with webpack config. Their default config does the right thing since they prefer ESM for tree shaking. Only the jest config is at issue

To be clear this cannot be mitigated in user land. This blocks using the most recent version of GraphQL.js along with create react app.

This was a bad choice of words, I guess I meant package-maintainer land.

This problem is made worse within cross dependencies. Projects like Apollo and Relay shouldn’t be forced to change their imports to require(“graphql/index.js”)

I actually see this as better practice than a naked import [internally]; who's to say what someone configures their module resolve order to be?
Declaring it yourself is a safe way to make sure you get the file you meant.
As for cross-dependency, Relay/Apollo wouldn't need to require graphql/index.js because the main/module resolution is still at play.

Showing it can be mitigated:
$ npx create-react-app test
$ cd test/
$ mkdir -p node_modules/package-solvable/
$ echo '{ "name": "package-solvable", "version": "0.0.0", "main": "index.js", "module": "index.mjs" }' > node_modules/package-solvable/package.json
$ echo "module.exports = require('./a.js')" > node_modules/package-solvable/index.js
$ echo "module.exports = 'this is .js'" > node_modules/package-solvable/a.js
$ echo "export { default } from './a'" > node_modules/package-solvable/index.mjs
$ echo "export default 'this is .mjs'" > node_modules/package-solvable/a.mjs

Modify your App.js:
diff --git a/src/App.js b/src/App.js
index bb3092f..ea8a960 100644
--- a/src/App.js
+++ b/src/App.js
@@ -2,8 +2,11 @@ import React, { Component } from 'react'
 import logo from './logo.svg'
 import './App.css'

+import logMe from 'package-solvable'
+
 class App extends Component {
   render() {
+    console.log(logMe)
     return (
       <div className="App">
         <header className="App-header">

yarn start

yarn test

When you are shipping a package like graphql:
$ echo "module.exports = require('./a')" > node_modules/package-solvable/index.js

yarn start

yarn test

To implement this workaround we’re going to need a new Babel plugin for mjs which replaces import x from “file.mjs” with const {x} = require(“file.js”) - which is beyond what the Babel pipeline can do today since it does not yet support changing extensions during compile (I think there’s an issue open for how to treat compilation of ESM files). In practice library maintainers don’t manually maintain both the mjs and JS files, instead leveraging compile pipelines to support both. It would be great to fix this bug instead of standardizing around new Babel functionality for explicitly including file extensions in require or import statements, especially since they’re unnecessary in a standard node environment.
Also, your suggested mitigation actually breaks native ESM support in this step:

echo '{ "name": "package-solvable", "version": "0.0.0", "main": "index.js", "module": "index.mjs" }' > node_modules/package-solvable/package.json

The “module” field is only used by tools like webpack, while node uses the “main” field. Including the .js extensions means that this module cannot be included by native node ESM import statements, since both require() and import resolution algorithms use the “main” field, however resolve to different file extensions (in fact, this is the reason why a new file extension was introduced). To support both existing CJS and future ESM, it’s important that the “main” field can be supplied without extension so that both resolution strategies can work correctly.
To be clear the goal here is not to support webpack - that can easily be done by using the “module” field and changing the names of files. The goal is to be ready for native ESM in node

I'm sure this will affect more than just CRA users

As far as I'm aware it only affects CRA users, or more broadly it should only affect those who have configured Jest in the same way - which isn't likely to be many users since CRA has additional configuration

To piggyback on your example, here is why this mitigation strategy breaks ESM:
$ npx create-react-app test
$ cd test/
$ mkdir -p node_modules/package-solvable/
$ echo '{ "name": "package-solvable", "version": "0.0.0", "main": "index.js", "module": "index.mjs" }' > node_modules/package-solvable/package.json
$ echo "module.exports = require('./a.js')" > node_modules/package-solvable/index.js
$ echo "module.exports = 'this is .js'" > node_modules/package-solvable/a.js
$ echo "export { default } from './a'" > node_modules/package-solvable/index.mjs
$ echo "export default 'this is .mjs'" > node_modules/package-solvable/a.mjs
$ echo "import solvable from 'package-solvable'; console.log(solvable)" > index.mjs
$ node --experimental-modules index.mjs
this is .js

Despite being in ESM mode, Node saw the import of package-solvable to resolve to main, which since it was explicitly set as a .js is loaded in CJS mode, so we see this is .js where we hoped to have seen this is .mjs. To fix this, we can tell node the main can be resolved independent of extension:
$ echo '{ "name": "package-solvable", "version": "0.0.0", "main": "index" }' > node_modules/package-solvable/package.json
$ node --experimental-modules index.mjs
this is .mjs
$ echo "const solvable = require('package-solvable'); console.log(solvable)" > index.js
$ node index.js
this is .js

This configuration allows for native ESM and CJS by requiring the same module name.

i could very well be wrong, but i'm not sure this is just a jest issue. at least for issue #1734 referenced above, i'm seeing the .mjs issue with apollo client when running the build command in cra, not test
> react-scripts build

Creating an optimized production build...
Failed to compile.

Failed to minify the code from this file:

./node_modules/react-apollo/parser.mjs:13

Maybe we should just revert mjs support altogether until this stuff stabilises a bit.

Aah I get it -- to leverage Node support you are required to ignore the extension specification for your package's main (this seems like a poor design choice by the ecosystem for clarity).

Here is the relevant issue in the Jest repo: https://github.com/facebook/jest/issues/4842
Jest should probably leverage native ESM loader hooks, or use the @std/esm loader.
Also, @gaearon - I'd be in favor of reverting the mjs support altogether since I don't think it buys much other than the ability to name a file with .mjs instead of .js - there's no actual integration node or with other tools, and jest + babel cannot correctly emulate ESM mode since the node_modules directory are not transformed. I'd support either merging this or reverting the original support

Hi everyone, are there news on this topic? I'm coming from this issue, currently putting on hold related updates until this gets resolved, and I would like to avoid ejecting to fix it by myself. We have a very small dev team right now, and don't yet have the time to handle custom configs and manual updates required after ejecting.
I'm not hoping for a fix in the next hours, but a global idea of a fix date would be appreciated. Thanks for all the work you put in this project 👍

@timer If we want to fix this soon, is this PR sufficient? Why is following up with Jest important?
I’m afraid we can’t revert now because that would be a breaking change 😕

Sure, this is fine as-is.
Following up with Jest is important because the ecosystem has to catch up and add support for mjs support.
Basically, you need to have two different module resolve orders based on if you're using import or require.

Thanks, @Timer!

@timer Is anything blocking releasing this? Can I do it now?

To clarify, Lee just reported and sent a fix for this issue, we're the ones who should release it

Out in 1.1.2.

(Sorry it took me a long time)

That's correct. This fix is really just a hack. We're hoping that Jest and webpack will properly support .mjs in the near future and that we can incorporate those new versions in 2.0.

Is there a way of getting this fix into next? I'd like to use this along with babel-plugin-macros by @kentcdodds

This fix is really just a hack.

We have no plans of merging this into 2.0 unless it's the last remaining blocker for a 2.0-final release.

I agree with @leebyron here

I see a fix has been merged for this issue in 0e0f260e355f4a9017dc0127cd7e60afea3c3e42, but the latest release of next I see in npm is behind, at 66cc7a903e91777e223780b898122a4dd3491d54. Will next in npm be updated any time soon?


Update readme

https://github.com/Compile-Time/demo-tracing-in-spring-boot-2-and-3/blob/0a1d7c496a952e618c1f4640278f9d3686ad5492/sleuth-annotation-port/README.md?plain=1#L10
Micrometer team has added support for these annotations starting Springboot 3.1.0 / micrometer-tracing 1.1.0.
https://micrometer.io/docs/tracing

SB 3.1.0 is not GA yet, so thanks for the repo, would help me a lot. Kindly let me know if you have used the custom implementation in production and found any gotchas, as I am going to attempt to do the same.

Hi, thank you for the issue and the news!
I have not been in the situation yet where I needed to migrate a Spring Boot 2 tracing code base to Spring Boot 3. Therefore, I can not provide you with any insights or wisdom regarding this.
However, I pushed a new branch (feature/micrometer-1.1.0-spring-boot-3.0.0) where I tried to get Spring Boot 3.0.0 to work with Micrometer Tracing 1.1.0 by manually overriding the micrometer dependencies.
I changed/added the following dependencies.
// Needed for the SpelTagValueExpressionResolver.
implementation 'org.springframework.cloud:spring-cloud-sleuth-instrumentation:3.0.0'

// Overwrite micrometer version
implementation "io.micrometer:micrometer-tracing:1.1.0"
implementation "io.micrometer:micrometer-commons:1.11.0"

// Tracing dependencies after Spring Boot 3
implementation "io.micrometer:micrometer-tracing-bridge-brave:1.1.0"

Then I copied the example from the Micrometer docs
And created a wrapper class for the SpelTagValueExpressionResolver because in Spring Boot 3.0.0 it does not implement the ValueExpressionResolver which is needed for Micrometer Tracing 1.1.0.
public class MicrometerSpelTagValueExpressionResolverWrapper implements ValueExpressionResolver {

    private final SpelTagValueExpressionResolver spelTagValueExpressionResolver;

    public MicrometerSpelTagValueExpressionResolverWrapper(SpelTagValueExpressionResolver spelTagValueExpressionResolver) {
        this.spelTagValueExpressionResolver = spelTagValueExpressionResolver
    }

    @Override
    public String resolve(String expression, Object parameter) {
        return spelTagValueExpressionResolver.resolve(expression, parameter);
    }
}

The wrapper is then used in place of the SpelTagValueExpressionResolver in the configuration class.
@Bean
public ValueExpressionResolver valueExpressionResolver() {
    return new MicrometerSpelTagValueExpressionResolverWrapper(new SpelTagValueExpressionResolver());
}

Nonetheless, I don't think either re-implementing the Sleuth APIs or overriding the dependencies is a good idea. I think it would be better to postpone the upgrade till Spring Boot 3.1.0 goes GA or to use a release candidate if re-working you tracing code to the new API is not an option.
If you really can not wait, I think it would be quicker and better to overwrite the dependencies than to re-implement the Sleuth APIs.

Closing: The READMEs of the different branches were updated to mention the news/announcement.


Update PrefixedViewConfig to properly handle trailing dot case

Current behavior for PrefixedViewConfig is that, for a prefix of form "foo." we expect configs of form "foo..bar", which is unusual.
We update PrefixedViewConfig to properly accept prefixes of form "foo." and expect configs of form "foo.bar".

I went through the issues and I don't see any reports that match this specific bug.
I couldn't find an equivalent in Archaius 1. AFAICT, the PrefixedViewConfig is something that is specific to Archaius2. The specific change seems to have been made ~6 years ago in this change: https://github.com/Netflix/archaius/commit/6c3acc1584369c6847c83d1576ffed9431714c7f#diff-10f5c96baf2408d403c639812b33ccd7830da34e37f2a59674c716cef813569a (while changing the lambdas, the +1 was added to cover the bug from using prefix instead of this.prefix). The previous version of the file before that (https://github.com/Netflix/archaius/blame/161f437af8ab0242048bc91c97108d29395687ee/archaius2-core/src/main/java/com/netflix/archaius/config/PrefixedViewConfig.java) worked like it would following this change.

👍
Ah, got it.
PR LGTM :-)

Thanks for the review!


Use cross-spawn in tests so that they won't fail on Windows.

Quite self-explanatory :)

Should I squash the commits?

Amazing that this issue still exists tbh.


Remove single line / group from debug console

Hi all,
It would be very handy if I could take a line of debug console output and delete it.
For example, if you have lots of log / printf statements throughout an application to track how an object is manipulated from point to point (e.g. tracking changes in a Redux store or something similar), it would be very nice to be able to delete log lines pertaining to certain actions, or to remove them until you have a clear picture of what's going on.
Maybe it can be buried in a right click action on the line in question?
Other thoughts?

@isidorn request makes a lot of sense to me (and seems to be low-hanging fruit).

Yes, this is low hanging fruit. However I would only added it if more people ask for it. Thus leaving it open as a feature request.

@isidorn please count me in as another user asking for it ;-)

Hehe fair enough :-)


Report bugs

Awesome work! I tried to replace the original file at conda/lib/python3.10/site-packages/transformers/models/clip/modeling_clip.py with m_clip.py. However, there are some bugs. For example, at line 714 of m_clip.py, inputs_embeds[-1] should be inputs_shape[-1]. Besides, after fixing aforementioned bugs, I still cannot reproduce the original results in the paper. Could the authors provide more details on how to modify the source code in 'transformer' library?

What results cannot be reproduced? Adversarial prompt or FID?

Just fail to run up the code. In m_clip.py, you modify the original class CLIPTextTransformer to accept input in the form of 'text_embeds'. However, in line 226 of whitebox_attack.py and line 743 of m_clip.py, it still needs "input_ids" to get "pooled_output". This results in a NoneType error. I try to fix this by assuming the last token is "end of sequence (eos)" token. This is my solution:
    if input_ids is not None:
        pooled_output = last_hidden_state[
            torch.arange(last_hidden_state.shape[0], device=last_hidden_state.device),
            input_ids.to(dtype=torch.int, device=last_hidden_state.device).argmax(dim=-1),
        ]
    elif inputs_embeds is not None:
        pooled_output = last_hidden_state[
            torch.arange(last_hidden_state.shape[0], device=last_hidden_state.device),
            input_shape[1]-1,
        ]

I am not sure if this implementation is right. Could you please share more ideas about how to fix this? Thanks a lot.

Is your transformers==4.28.1？

Yes, I believe I strictly follow the guidance in Readme.

I updated the m_clip file, I uploaded the wrong file before, sorry for the trouble. It should work properly now.

Thanks for the very timely reply, but the problem remains. Now I can run the code. But in the main loop, CLIP classifier frequently misclassifies the generated images. The code always "skip this text" at line 163. However, CLIP zero-shot classification accuracy is about 70% in ImageNet-1K. There should not be so many misclassified images. I try to visualize the generated images. They seem unnatural. It seems that there is something wrong with the stable diffusion generation at line 157. I also try to generate images by directly input a text string, it will generate natural images. So I think it is because of the input prompt_embeds.

In config.py, change the img_size to 512

Thanks for your help. It works now.


Model Weights?

Hello!
Thank you for your incredible work here, as well as releasing your data scripts. I was wondering if you would consider releasing the model you've trained and reported metrics on in the paper? It would be great to give the model a try on new APIs!
Thank you again!

Thank you for your kind words and interest in our work. The trained models are now available on Hugging Face Hub. You can find them at the following links:

ToolAlpaca-7B
ToolAlpaca-13B

For usage and evaluation, please refer to the 'Evaluation' section in the README. I hope this helps and I look forward to any further questions or feedback you may have.


test

I don't think we would like these changes made to the workflows -- in part, this is downgrading multiple action versions. We already have golangci-lint running for all PRs/main commits. If there are some changes here you feel would be useful, please update this PR. In the meantime, I'm going to close this as I do not believe these changes are intended for Syft


bugfix(modals): don't set dismissible after open

fix absent scroll after modal

Updated on DEV and PROD


Need to add validation to packet capture, connectivity check and connection monitor

Is your feature request related to a problem? Please describe.
A lot of exception came when customer try to create new packet capture if packet capture already exists (resource with the same name). Would be great if before making a call we could validate packet capture name. For this we could try to get packet capture, and proceed to "create" call only if "get" returns null.
Another problem occurs when customer tries to test connectivity or create connection monitor for not existing source. So, before making call, would be great to validate if source exists.
Also, customers often try to test connectivity and create connection monitor for the same source and destination which cause an exception.
Describe the solution you'd like

az network watcher packet-capture create. Need to validate if the packet capture with the same name already exists.
az network watcher test-connectivity --source-resource
[--dest-address]
[--dest-port]
[--dest-resource]
[--headers]
[--method {Get}]
[--protocol {Http, Https, Icmp, Tcp}]
[--resource-group]
[--source-port]
[--valid-status-codes].  Validate if source-resource exists. Validate if source != destination.
az network watcher connection-monitor create --name
--source-resource
[--dest-address]
[--dest-port]
[--dest-resource]
[--do-not-start]
[--monitoring-interval]
[--resource-group]
[--source-port]
[--tags]. Validate if source-resource exists. Validate if source != destination

Describe alternatives you've considered
Additional context

The service error is the appropriate behavior from the CLI's perspective, so we do not plan to implement this.


Allow for persistent locking when no block passed?

Seems like there would be some advantages in allowing for persistent locking/lock checking when no block is passed to #lock. Goal would be to support something like the following use case:
def edit
  @object = SomeObject.find(params[:id])
  lock = @object.lock
  if lock
    @object.update_attribute(:locked_by, current_user)
  else
    redirect_to(object_url(@object))
    flash[:error] = "Object is currently unavailable for editing blah blah blah"
  end
end

def update
  @object = SomeObject.find(params[:id])
  if @object.locked_by == current_user
    params[:object][:locked_by] = nil
    @object.update_attributes(params[:object])
    @object.unlock
    flash[:message] = "Object updated."
  end
  redirect_to(object_url(@object))
end

I'm not opposed to this, if you whip up a pull request, I'll take a look.  Please include tests and docs.  Thanks!


addition of chromadb increased docker image size from 1.5G to 6.31G

I do like the addition of chroma-db (PR #59) to the retrieval plugin. Unfortunately Chroma has a very heavy dependency tree (e.g. because of Torch). This means that this addition has quadrupled the image size and build time. Although it is nice to have chromadb, it means that if you do not use ChromaDb you have to strip it away, to arrive a reasonable docker image size.
Any thoughts on this? (use different branches?)

I would just use the project as a template and customize to my own needs, only including used dependencies in my deployment.

+1 on this.
Transformers/Pytorch should be removed again from poetry.lock.

We're landing a fix for that shortly: https://github.com/chroma-core/chroma/pull/267
This will eliminate that entire dependency tree - the reason it currently exists is that chroma uses local sentence transformer embeddings by default. After the above change, these will be optional and we'll ship with a lightweight ONNX model.

The fix has landed - the dependencies which were causing the image to balloon are gone. Thanks for bearing with us!
https://github.com/chroma-core/chroma/pull/267

https://github.com/openai/chatgpt-retrieval-plugin/issues/292#issue-1731782640
hopefully this will help someone


Make imageset.addOnParameters consistent with metadata.addOnParameters

Removes the items field from imageset.addOnParameters, instead, array items can directly be appended to imageset.addOnParameters, similar to metadata.addOnParameters.
The OCM upsert function has been modified to append array items to the items field instead, to comply with the OCM API Spec.
Tested and verified locally against OCM stage:
❯ ./venv/bin/managedtenants --environment stage --addons-dir addons --addon-name reference-addon run --debug tasks/deploy/30_ocm_upsert.py
Loading stage...
Loading stage OK
== TASKS =======================================================================
tasks/deploy/30_ocm_upsert.py:OcmUpsert:reference-addon:stage...
OCM upsert for reference-addon
tasks/deploy/30_ocm_upsert.py:OcmUpsert:reference-addon:stage OK

gg

LGTM, thanks for this PR. I think its better to expose a uniform interface to our tenants. The addons flow is complex enough at this point lol


Spanstat: Validate that the duration is not negative when call End.

Backport #5889

This change is

test-me-please

test-docs-please

test-missed-k8s


Support IPv6

Hi,
how can i use this tool with plex server who uses ipv6?
When i change the ip adress in the serverSettings file, nothing happens or i see an error.
Greetings.

Sorry for not replying.
However, there are others who have made better apps than this one now. Theirs might work with ipv6 only servers.
I have not tried it, but you could check out this one here that looks good: PlexRipper


⚠ gorzdrav.org has degraded performance

In d8a21dc, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 3384 ms

Resolved: gorzdrav.org performance has improved in 3503fef.


Introduce FieldType, improve Field and Reference API

This PR introduces improvements to the field information, introducing new API.
New types are described below.
FieldType
TBD
Cardinality
TBD
Changes to the FieldType
TBD

@armiol, just FYI, I moved to newer API, and the build passes.
I'm not quite happy with the longer field names (e.g., field_type instead of type) I had to "invent" in order to arrange the migration.
I'd like to discuss the next step as to removal of the existing deprecated API sometime tomorrow.


: use 'time.Until', 'io.Seek' for go1.7 and 1.8

For https://github.com/coreos/etcd/issues/6174.

LGTM

@heyitsanthony This breaks in jenkins. When do we switch to go 1.8 in jenkins?
We can just wait until then.

Nuked the time.Until change and keeping go1.8 notes in README for later changes.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@3a1368d). Click here to learn what that means.
The diff coverage is 44.44%.

@@            Coverage Diff            @@
##             master    #7545   +/-   ##
=========================================
  Coverage          ?   70.27%
=========================================
  Files             ?      320
  Lines             ?    26214
  Branches          ?        0
=========================================
  Hits              ?    18422
  Misses            ?     6343
  Partials          ?     1449

Impacted Files
Coverage Δ

pkg/fileutil/lock_linux.go
76.66% <ø> (ø)

pkg/fileutil/preallocate.go
25% <0%> (ø)

wal/repair.go
48% <0%> (ø)

pkg/fileutil/fileutil.go
69.56% <100%> (ø)

wal/encoder.go
84.31% <100%> (ø)

etcdctl/ctlv3/command/snapshot_command.go
64.77% <25%> (ø)

wal/wal.go
61.81% <50%> (ø)

Continue to review full report at Codecov.

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


[docs-only] Claim update process (proxy service readme)

Fixes: #10445 ([deployment][ocis-keycloak] Both old and new group names appear in OCIS web-UI after renaming the group name from keycloak)
Add a description about the claim update process and background info.

@phil-davis mind to have a another look on the language?


Transmit Tool and Transmit Tool Testing

you don't need to add encryption feature on transmit tool. It's not suitable for the very first version.
plus the external jar you used can not be find in project. I recommend you comment out the encryption code and just test the very basic function.

JWT not a module to encrypt the content transmitted between the user and the server, it only use to verify that the request was made by the specified user. In addition, it is placed after LoadBalancer to avoid extra response time.
Thus, I decided to leave it.
If you apply Gradle on your project, it will easy to add dependency for JWT. refer: https://mvnrepository.com/artifact/com.auth0/java-jwt/4.2.1


Support gdb pretty-printing displayHint type "map" by processing map …

…children as name-value pairs.

Signing off with one minor comment.

Comments added


Alternative Rainbow Mode Option

Proposal
Second Rainbow Mode where modifier keys are not colored based on the amount of hotkeys used in the shortcut but color based on their type. Control, Command, Option and Shift each have their own identifying color in all shortcuts and letters (and symbols and non-modifiers) stay White everywhere.
Color scheme could be:
Command - Blue
Shift - Green
Option - Yellow
Control - Orange
fn - Red
I based it on how frequently each modifier is used.
Here is a colorblindness color scheme that you can add as an aditional option:
Command - #006ddb
Shift - #22cf22
Option - #ffdf4d
Control - #db6d00
fn - #920000
Alternatives
No response

And I guess for Hyperkey users make Caps Lock pink

Hey wanwindwalker,
I believe for the alternative, it would be best to let you decide (customize) which colors you want to see. Anyway, it was planned to be customizable later.

And I guess for Hyperkey users make Caps Lock pink
Technically, Caps Lock isn't recognized as a valid modifier or key. However, it can be assigned to hotkeys in some apps. The question arises whether it should be displayed as a modifier since it does function as one. Or, when assigned as a hotkey, it effectively becomes a non-modifier. Currently, there are no plans to display Caps Lock as a valid modifier or key, but it's a possibility for the future.

I'm not user of Hyperkey I didn't know it didn't function the same way. Yeah customizable is always preferable sorry if I suggest a feature that was already planned I didn't realzie it was.

Don't worry if the feature is already in plans — I appreciate all suggestions. It shows that I'm thinking in the right direction.

Hey wanwindwalker,
I've just released a new version. You can now customize these colors.


[Feature request] 'in' validator additional usecase

Hi folks, first just wanted to say that I appreciate this project.  It's been useful in applying any amount of order at all to our yaml files.
I'm trying to make a schema as follows:
---
actions: list(include('action'))
fields: list(include('field'))
coverage_map: map(map(str(), key=a field's name), key=an action's name)
---
action:
  name: str()
  description: str()
field:
  name: str()
  description: str()

Sample file:
actions:
  - name: open
    description: opens
  - name: close
     description: closes
  - name: idle
    description: idles
fields:
  - name: date
    description: date of action
  - name: which
    description: which item
# mapping incompleteness is intentional
coverage_map:
  open:
    which: one
    date: today
  close:
    which: one

The specific actions and fields defined in this sample are not likely to be anywhere close to the actions and fields that would be in a different sample, but the requirement that the top level keys should be actions and the inner keys be fields will hold true for them all.  Consequently, it would be very hard to follow the advice of the maintainer in https://github.com/23andMe/Yamale/issues/71 since the way I interpret what they're saying would imply needing to create a schema for each file, which defeats the purpose of having a schema in the first place.
Unless I'm missing something, it seems like having an 'in' validator would be the only way to make my usecase possible.  Is this something that yall would be willing to add as a built-in validator?

If the possible action and field names across the various samples are known you can use enum to solve this, i.e.:
---
actions: list(include('action'))
fields: list(include('field'))
coverage_map: map(map(str(), key=enum('date', 'which')), key=enum('open', 'close', 'idle'))
---
action:
  name: enum('open', 'close', 'idle')
  description: str()
field:
  name: enum('date', 'which')
  description: str()

where you would add all possible values to the enum validators (I only included the ones in your sample).
If you want the keys to only be one of the action and field names present in the yaml file being validated you either need a schema per file or create a custom validator/constraint.

If the possible action and field names across the various samples are known

They are not, unfortunately.  Thanks for your reply.


PR: Move PluginMainContainer and PluginMainWidget to their own modules

Description of Changes

Those classes are perhaps the most important ones of our new API, so I think it's better to move to their own modules so they are easier to find and use.
I also took the opportunity to remove unused imports in a lot of places.

Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:

Hello @ccordoba12! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/api/widgets/main_container.py:

Line 143:23: W292 no newline at end of file

In the file spyder/app/mainwindow.py:

Line 50:1: E402 module level import not at top of file
Line 52:1: E402 module level import not at top of file
Line 53:1: E402 module level import not at top of file
Line 71:1: E402 module level import not at top of file
Line 85:1: E402 module level import not at top of file
Line 87:1: E402 module level import not at top of file
Line 93:1: E402 module level import not at top of file


User Deletion of KM fails with custom workflow extensions of AM

Description
Duplicate of https://github.com/wso2/product-apim/issues/11673
Steps to Reproduce
Refer https://github.com/wso2/product-apim/issues/11673
Affected Component
APIM
Version
4.2.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

Fix https://github.com/wso2/carbon-apimgt/pull/11691

Fix test case https://github.com/wso2/carbon-apimgt/pull/11691/commits/a583548251bc455d31a6fec80db732f1f3f1c4b0


Styling cleaning [ch117199]

Related to https://app.clubhouse.io/cartoteam/story/117199/fix-home-styles

Fix conflicts after the incorporation of Oauth


srclib-java improvements

fixes #68 and #69
indexing files from androidTest Gradle source set if there is any)

@alexsaveliev LGTM


global 'document' variable is missing from the global variable list.

global variables defined by the polyfill like "global, window, self, console, process" don't include document? is this by design?

Yes, it is by design.
This polyfill is not targeting to simulate web browser environment, but providing sufficient support of environment to do server-side rendering for React (vuejs, angular 2 etc) that does not rely on DOM api when rendering on server-sider.
Meanwhile there are some stuff does not need to run on server side, so their support is limited. e.g. FormData, usually FormData is used after user input, but there is no user input when rendering on server.
In React application, document still can be used in event handler, but not in render or component lifecycle methods.

I agree that most of the time that is the case.  though for us, one of the polyfills we used in our server rendered react project, (https://github.com/chrisdickinson/raf) references document object. we try to apply the polyfills before all renders and lifecycle methods, which causes a problem during initial render.
finding out a way to omit that polyfill from the server build fixes our problem, but I figured you might want to know this use-case to make a more informed decision about the design.

Thanks for sharing.
I think if doing server-side rendering, DOM related API should be ensured that they are not called in render. Otherwise the library has to be thrown away if no walkaround. The degrade approach is to check if document exists before use it.
The reason is simple: if code throws exception because of document is undefined, then adding a fake var document = {} does not help since the code will continue to call something like document.getElementById(), but that function is undefined. It can go on and on, then it eventually require a full DOM API polyfill which is hard.


Add ERC-173/Ownable analogue

This is intended to be used by Oas721a and future contracts.

@nhynes should this be rebased and merged?


Document Index: make compatible with DocVec

Right now, Document Indexes operate on DocList for input and output of Data.
We need to extend support to DocVec.
This can be seen as a two step process:

Enable basic compatibility, by converting DocVec to DocList in BaseIndex. Just make it work
The column-based structure of DocVec should allow for some optimizations wrt to batch processing, if a backend accepts batches in column-based form. Let's implement that if we can

Enable basic compatibility, by converting DocVec to DocList in BaseIndex. Just make it work

Hey @JohannesMessner does BaseIndex stands for BaseDocIndex and if i am correct this has to be replaced in docarray/index/abstract.py file or in all other index implementations


feat: Implement a new --strict-coverage option to enforce a more strict coverage reporting mode

This PR contains the changes from #102 and #138 (contributed by @dmnd and @uforic) with the following changes applied:

renamed the new cli option to --strict-coverage
renamed config file option to strictCoverage
include strictCoverage option in the JSON summary result
add a new test case to test the expected behavior in "strict coverage" mode.

@dmnd @uforic The new --strict-coverage options has now been released as part of the new 0.5.0 release! :tada:
Thanks again for contributing this feature! :heart:

@rpl I'm still seeing non-flow files in my coverage report with --strict-coverage even though https://github.com/rpl/flow-coverage-report/pull/102 should fix  https://github.com/rpl/flow-coverage-report/issues/85

@villesau --strict-coverage doesn't exclude the "non flow annotated" files from the report, on the contrary it reports them as fully uncovered so that they are considered part of the sources that still need to be properly covered by flow types.
Having said that, I think that it would make sense to define also an additional cli option which automatically exclude them from the files which are part of the report (e.g. a new --exclude-non-flow CLI option), it was one of my initial proposals for this one, but after discussing it in #138 we determined that they are two different use case (https://github.com/rpl/flow-coverage-report/pull/138#discussion_r167562616 and the related reply comment).

Oh, thanks for the clarification! I could give a shot for --exclude-non-flow @rpl


Jogging

Switch-commands.md should be extended with this:
Jogging
The the basic pull-in command + "" can be used to exectute the required command as a burst. The jog is automatically released after the relay is pulled for 0.5 seconds.
Sending the release command + "" has no effect.
Examples
12*

Close relay 2 for 0.5 seconds and release after
Updated md is attached.
Switch-commands.zip

Sorry, * was not properly added to the md file. (Should have press preview...)
So, here it is again:
Jogging
The the basic pull-in command + "*" can be used to exectute the required command as a burst. The jog is automatically released after the relay is pulled for 0.5 seconds.
Sending the release command + "*" has no effect.
Examples
12*

Close relay 2 for 0.5 seconds and release after
Switch-commands.zip

There is such a command? Will add it later today.

Chapter 5.5 in the attached document. (Google translate is my friend!)
SR-201系列产品说明书.pdf

Now I remember! I had that document translated earlier. But I could not make sense out of the Asterix and the K-Command. Here is why:
You will probably agree, that the action
send "11*"

translates into the manual actions
send "11"
wait 500 ms
send "21"

That corresponds to the behaviour described under 5.5. But it also states that
send "21"

should translate to
do nothing

but it actually translates to
send "11"
wait 500 ms
send "21"

too. I just verified that again with my board.
Last time I stopped here, because I didn't want to document a feature I do not understand. This time I went a step further: It seams that the STATE is ignored completely. Therefore, the action
send "-X*"

which consists of an illegal BASIC_COMMAND should translate to
send "1X"
wait 500 ms
send "2X"

Which it does, indeed.
That leads to the simplification that the JOG_COMMAND consists of any one byte followed by any CHANNEL followed by an asterix.
@hobpet, by any chance, can you verify my observation?

Of course, I will test this with my board.

I can confirm that the first character is completely ignored. It even worked with some weird special ASCII characters, like ALT-0147 (“1*).

Tried to describe out observations in the Switch commands section.

Looks great, thanks!


[FEATURE] {{ DL Stepper }} - {{ Add sub steps }}

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@rotemshaham we need more info


Spotify-client package signing key has changed

https://download.spotify.com/debian/pubkey_7A3A762FAFD4A51F.gpg has replaced https://download.spotify.com/debian/pubkey_5E3C45D7B312C643.gpg
If the key is not updated we get apt errors:
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repository.spotify.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7A3A762FAFD4A51F
W: Failed to fetch http://repository.spotify.com/dists/stable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7A3A762FAFD4A51F
W: Some index files failed to download. They have been ignored, or old ones used instead.

To overcome the catch-22 users with deb-get-installed spotify-client could to this:
 curl -sS https://download.spotify.com/debian/pubkey_7A3A762FAFD4A51F.gpg | sudo gpg --dearmor --yes -o /usr/share/keyrings/spotify-client-archive-keyring.gpg

Hi @stankovictab ,  this error says you have two entries that have different signing key info for the one repo.  You can find them like this :
grep spotify /etc/apt/sources.list.d/*.list
/etc/apt/sources.list.d/spotify-client.list:deb [signed-by=/usr/share/keyrings/spotify-client-archive-keyring.gpg] http://repository.spotify.com stable non-free

But you should see two lines with another pointing to a different key location.  You need to move or delete that extra file.  Then sudo apt update should complete without errors.

Yup, that did the trick, for some reason I had both spotify and spotify-client in there,
just removed the spotify one and the problem is gone.
Thanks a lot!


Can't import distro-Installed packages inside virtualenv

Issue
When importing tkinter:
Python 3.6.7 (default, Oct 22 2018, 11:32:17)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.2.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import tkinter
---------------------------------------------------------------------------
ModuleNotFoundError                       Traceback (most recent call last)
<ipython-input-1-29b37e014535> in <module>
----> 1 import tkinter

/usr/lib/python3.6/tkinter/__init__.py in <module>
     34 import sys
     35
---> 36 import _tkinter # If this fails your Python may not be configured for Tk
     37 TclError = _tkinter.TclError
     38 from tkinter.constants import *

ModuleNotFoundError: No module named '_tkinter'

Environment
On ubuntu 18.04; python 3.6 with the python3-tk apt package installed. import tkinter works outside of the virtualenv, just not inside it.
Workaround
Find the location of the _tkinter package being used outside of the virtualenv and simlink to it inside the virtualenv.
The incantation that worked for me was: ln -s /usr/lib/python3.6/lib-dynload/_tkinter.cpython-36m-x86_64-linux-gnu.so ~/.virtualenvs/science/lib/python3.6/lib-dynload/_tkinter.cpython-36m-x86_64-linux-gnu.so. science is the virtualenv name.

Hi @thatneat. I imagine this kind of problem is actually related to Virtualenv and outside the purview of Virtualfish. Just something to perhaps keep in mind in the future.
I suspect Virtualenv is behaving precisely as designed in this case, as its primary mission is to create isolated virtual environments. This isolation usually includes modules installed via Linux distribution packaging, global system site-packages, and really anything not installed into the virtual environment itself.
Perhaps you should try creating a virtual environment with the --system-site-packages flag. You can read more about this topic here: https://virtualenv.pypa.io/en/stable/userguide/#the-system-site-packages-option
Of course, I'm not 100% certain that the aforementioned is indeed the cause of your problem, since I have never used Tkinter.
One last thought... It's usually better to avoid phrases like "doesn't work" and instead try to focus on the actual problem. As an example, have a look at how I've changed the title of this issue. Your issue was otherwise well-organized, which is a refreshing rarity. Well done. 👍

Thanks for the quick response! I don't know if I've tried any other distro-installed packages so I can't verify that your change from tkinter to "distro-installed" is correct, but I support the change from "doesn't work" to "can't import". :+1:
I considered that it might be a virtualenv issue but haven't had this issue in the past with other virtualenv wrappers, and googling didn't turn up anything so I thought filing here was the next best step. I'll try the --system-site-packages trick.

Looks like that cleared it up!
I double-checked that this is not an issue with the default settings using bare virtualenv:
>  virtualenv --version
16.4.0
> virtualenv venvtest
...
> source venvtest/bin/activate.fish
> python
Python 3.6.7 (default, Oct 22 2018, 11:32:17)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tkinter
>>>

Your suggestion with virtualfish also works
> vf new --system-site-packages vftest
...
(vftest) > python
Python 3.6.7 (default, Oct 22 2018, 11:32:17)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tkinter
>>>

BUT it also currently works without the --system-site-packages flag
> vf new vftest
...
(vftest) > python
Python 3.6.7 (default, Oct 22 2018, 11:32:17)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tkinter
>>>

So here's the best I can figure right now: The virtualenv I had the issue with was probably created before I installed the distribution's python3-tk apt package. It appears that installing the apt package didn't add the symlink to the existing virtualenv due to the way the symlinks are set up. Interesting.
For anyone coming across this in the future (yes, you!), it's probably easiest to just nuke your virtualenv and start fresh.
I think we can call this closed - as you said, it looks like it happened due to the way that virtualenv works rather than anything specific to virtualfish. Thanks!

You are most welcome. Glad to hear you got everything sorted out. Have a great weekend!


Define lines undroppable

For my case, I need to restrict droppable indexes in the list.
So I imagine I'm not the only !
Hope this help.

Why can't you selectively update your data array in onMoveEnd? Ie. do not update it if the row should not be draggable.

For UX purpose, I don't want to move the spacer (empty element) at undroppable index.
With my pull request, the spacer doesn't move at specified indexes so the user see clearly that's not possible to drop the element at these indexes.

I'd love to see this implemented. @computerjazz any chance this could be merged?


how to install this module via requirement.txt file

I am attempting to utilize a service called Cerebrium, which requires the installation of Exllama through a requirement.txt file. However, I am encountering difficulties with the original repository because it does not have a pip module.
and with this repo I'm not sure how can I use python -m pip install git+https://github.com/jllllll/exllama in the requirement.txt

Direct links to the wheels can be used along with system filters to ensure proper installation:
https://github.com/jllllll/exllama/releases/download/0.0.6/exllama-0.0.6+cu117-cp310-cp310-win_amd64.whl; platform_system == "Windows"
https://github.com/jllllll/exllama/releases/download/0.0.6/exllama-0.0.6+cu117-cp310-cp310-linux_x86_64.whl; platform_system == "Linux" and platform_machine == "x86_64"

You can also directly use the git+ format:
git+https://github.com/jllllll/exllama

thanks you so much


Actually cache handJointService in SolverHandler

Overview
There was a backing field, but it was never actually set. This now prevents the property from calling CoreServices.GetInputSystemDataProvider every time.

/azp run

/azp run


Ferdi not opening from tray after last update

Hi, guys.
I've just updated Ferdi to the latest version and since then I don't seem to make the window show when double clicking the tray icon, nor selecting the "Show Ferdi" option from the tray menu.
In order to open the window, I have to use the application's shortcut.
Windows 10 - 64 bits
Paulo

Same here. Linux Mint 20.2 Cinnamon.

Duplicate of #2147


add tabindex and handle keyboard selection

This PR fixes #12963
add tabindex to leverage the vscode global outline color: https://github.com/microsoft/azuredatastudio/blob/main/src/vs/workbench/browser/style.ts#L114
and I noticed the page number doesn't handle keyboard selection so adding it.
before:

after:

Pull Request Test Coverage Report for Build 356929796

0 of 5 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.005%) to 41.309%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/services/dialog/browser/wizardNavigation.component.ts
0
5
0.0%

Totals

Change from base Build 356915875:
-0.005%

Covered Lines:
21739

Relevant Lines:
48317

💛  - Coveralls


linter

I also noticed a missed typo "deynamic" in the README:
https://github.com/github/rust-gems/blob/e32c83dc906f8d2db2f36de220ed2ebd47c743c0/crates/bpe/README.md?plain=1#L194


Avoid libvirt deactivating on AlmaLinux9 on reboot

Description
In AlmaLinux9 when a KVM host is restarted, libvirtd disables itself during system startup.
To Reproduce
Add an OpenNebula KVM host that's based on AlmaLinux9, then restart it. There is a chance you'll experience auto-deactivation of the libvirtd service: 28 Feb 13 07:38:18 host1 systemd[1]: libvirtd.service: Deactivated successfully.
Expected behavior
The libvirtd service should not be deactivating itself.
Details

Affected Component: KVM Host, AlmaLinux9
Hypervisor: KVM
Version: 6.4+

Can not reproduce.
As long as virtproxyd.socket is enabled  and running then also new modular libvirt is working.
cat /usr/lib/systemd/system-preset/90-default.preset
...
 # Compatibility with libvirtd sockets for old clients and expose TCP sockets
enable virtproxyd.socket

So at least in AlmaLinux 9.1
rpm -qf /usr/lib/systemd/system-preset/90-default.preset
almalinux-release-9.1-1.9.el9.x86_64

After further investigation we now know what is going on! :smiling_face_with_tear:
Please take a look here ->

The work will primarily involve changes in the systemd presets related to libvirt. Currently the Fedora systemd presets enable libvirtd.service. While libvirtd does support socket activation this is not used during host startup, because the libvirtd daemon needs to be fully started in order to auto-start QEMU guests that may be configured. The current libvirtd.service uses a timeout, however, that causes libvirtd to shutdown after 2 minutes if no VM is running.

The automatic deactivation we've observed is a feature of the new modular libvirt.
Unfortunately OpenNebula currently cannot successfully deal with that, so it's required to disable systemd socket activation, please take a look here.
Steps we suggest as a workaround for AlmaLinux9 running OpenNebula ->

Mask virtqemud and its socketssystemctl mask virtqemud{.service,.socket,-admin.socket,-ro.socket} --now

Mask libvirtd's socketssystemctl mask libvirtd{.socket,-admin.socket,-ro.socket,-tcp.socket,-tls.socket} --now

Override libvirtd's systemd unit and revert the Environment=LIBVIRTD_ARGS="--timeout 120" setting$ install -o root -g root -D /dev/fd/0 /etc/systemd/system/libvirtd.service.d/override.conf <<'EOF'
[Service]
Environment=LIBVIRTD_ARGS=""
EOF

Run systemctl daemon-reload

:ok_hand:

Add a note in the Platform notes https://docs.opennebula.io/6.6/intro_release_notes/release_notes/platform_notes.html#front-end-platform-notes

When after steps 1, 2, 3, 4 your OpenNebula instance fails to successfully monitor the host, then you might want to check if there are stale virtqemud sockets in /var/run/libvirt/. If such socket files are present and virtqemud is disabled and stopped, then running virsh is likely to fail, because of the invalid socket files cannot be openned. You might want to run virsh -r -c qemu:///system capabilities on the host directly to confirm. As a workaround you can delete all virtqemud socket files.


image link is broken in page About

new branch issue-image-link-is-broken-in-page-About for the fix

merged to draft and then production


Broken link to "packager config file" in the Images guide

There's a broken link on the Images guide page:
http://facebook.github.io/react-native/docs/images
The borken link is on the this text:

You can add support for other types by creating a packager config file (see the packager config file for the full list of configuration options).

The current URL is https://github.com/facebook/react-native/blob/master/local-cli/util/Config.js#L68 which gives a 404.

This file was moved to react-native-community/cli, @thymikee any idea where the new link should go?

These should now be defined in metro.config.js file, see the docs on where to put this: https://facebook.github.io/metro/docs/en/configuration#assetexts

Thanks @thymikee!
@AlbertVilaCalvo want to submit the PR?

@rickhanlonii I've opened a PR: https://github.com/facebook/react-native-website/pull/960


Network.Contract() can be combined into Contracts()

Network.Contract() is just Contracts() plus an argument for contraction order, we suggest add this argument to Contracts() and deprecate the Network.Contract().

7931bbb


Specifying K in PML_distribution_approximate(x, K)

If the example of x = [9,3,2,1,1] is used with k>6 (6 is the estimated support size), then the empirical distribution is the pml for k = 5 concatenated with 0's, which seems to be incorrect. The same problem stays in MATLAB.

This is correct behavior.  As a smaller example, consider x = [2,1,1].  You'll see that the output is uniform on 9 elements for k = 9, but uniform on 3 elements for k = 10 with 7 trailing 0s (and the optimal k is 5, uniform on 5 elements).  To check that this is the correct behavior, you can compare just two cases: uniform on 3 elements with F0 trailing 0s versus uniform on 3+F0 elements, and you'll see that indeed the observed thing happens.
The intuition is that if you're forcing a larger-than-optimal k, you are forcing the nonzero-height bins to mix with a greater number of zero-height bins.  For large enough k, this forced mixing results in low-enough likelihood that it becomes better to keep the zero- and nonzero-height bins in separate clumps, leading to the behavior you observed.
Thanks for pointing this out, I hadn't realized this happened.  I can also provide a more detailed computation for the claims in the first paragraph here if it'll help.


App Crashes on clicking notifications

Provide a general summary of the issue.
Your Environment

Plugin version: 0.1.4
Platform: android
OS version: 11
Device manufacturer / model: all
Cordova version: 10
Cordova platform version):
Plugin config
Ionic Version: 6.20.1

Expected Behavior
Clicking on notification, should open the app
Actual Behavior
Clicking on notification causes crash
Steps to Reproduce

Schedule a notification
Notification appeas
Clicking on it causes crash (android logo appears)

Context
Use local notifications

Hi For me it also restarts the app while clicking on the notification
Cordova Android --  11
Plugin Version -- 0.1.4
Cordova version -- 10.1.2
I created a timer app that runs for 30 mins it also runs in the notification while clicking the notification the app restarts itself

For me restart app too


Verify core_bpf status on power architecture

There were some issues in the past, verify the current state of things.
Part of #1222

Actually implemented within the following sequence of commits:
https://github.com/stackrox/falcosecurity-libs/commit/e77e712d31ab9074dbfe2fa7649221fbaa2ba2a5 .. https://github.com/stackrox/falcosecurity-libs/commit/a865dbb78c795eaae0dd816675cb5120073cc55f


[UI] Create Hot Wallet > Advanced Settings > Dropdown dont show selected option.

Description
Create Hot Wallet > Advanced Settings > Dropdown dont show the sleected option.
To Reproduce

Create a Hot Wallet
Go to Advanced Setting
Select Choose Wallet Purpose.
The selected purpose is not shown in the dropdown.

https://github.com/bithyve/bitcoin-keeper/assets/18442573/fe9d2dac-fb4e-454e-8909-572596cb3230

Completed


PPDC-505 (Update Link text to PCDN under HomePage )

In this PR:

HomePage has been updated. Specifically, the link text to Pediatric Cancer Data Navigation page has changed from "Explore the Pediatric Cancer Data Navigation" to "Explore our Pediatric Cancer Data Navigation"

Related Ticket: PPDC-505

In this PR:

HomePage has been updated. Specifically, the link text to Pediatric Cancer Data Navigation page has changed from "Explore the Pediatric Cancer Data Navigation" to "Explore our Pediatric Cancer Data Navigation"

Related Ticket: PPDC-505

Ticket says change text to "Explore our Pediatric Cancer Data", not the "Explore our Pediatric Cancer Data Navigation"


Add support for snapshot testing

Describe the solution you'd like
helm-unittest as a great feature called snapshot testing.
Sometimes you may just want to check that the rendered manifest did not change between helm package version without every details asserted.
Describe alternatives you've considered
None and neither did the community, see https://github.com/orgs/gruntwork-io/discussions/780
Additional context

Hello, I just came across this issue simply because it was fresh and at the top of the page.
For context, please read this article. I believe this is how Camunda test their own Helm charts. It describes "Golden template files" and I think these are essentially snapshots.
Could be what you are looking for, or could be used for inspiration to add snapshots to this already great tool.


Feature: Personal Finance Dashboard

Issue Template
Description
Many existing personal finance tools either lack customizable tracking for personal budgets, investments, and savings goals or require complex integrations. This dashboard provides an all-in-one, simplified solution for tracking and visualizing financial data in real-time. It addresses the common challenge of fragmented financial data management, where users struggle to see a consolidated view of their finances across different categories.
Steps to Reproduce
Below is the step-by-step instructions on how to reproduce the issue:

Go to the main page of the Personal Finance Dashboard by opening index.html in the browser.
Click on the 'Budgeting' section and set a monthly budget (e.g., $1000, to be entered as 1000).
Scroll down or Navigate to the 'Expense Tracking' section and enter an expense (e.g., category: "Groceries," amount: $50).
See error: No feedback appears for missing input, or an error message displays unexpectedly in the console. Return to the 'Budgeting' section. Observe the Budget Progress bar or chart.

Expected Behavior
After adding an expense, the budget progress bar or chart should reflect the updated spending. If a $50 expense was added to a $1000 budget, the budget progress should show $950 remaining.
Actual Behavior
The budget progress bar or chart does not update, still displaying the original budget amount without considering the recent expense.
Screenshots
If applicable, add screenshots to help explain the issue.
Additional Context
Add any other context or information about the issue here.

invalid issue


Technologies without profiles need to be removed from concurrency table

I removed those specific technologies from that list. Should they also be removed from the name selection?


GPU-less install

One of the great things about Plots.jl's setup is it can install pretty much anywhere because the extra functionality is all provided by backends. I can't see getting Makie.jl to work on my friendly neighborhood cluster, while GR works fine. And then there are cases where there's no access to OpenGL (without VirtualGL), but other options like Plotly works.
Will there be a nice way to be able to install Makie in those setups? I like the GLVisualize-first approach and think it makes a lot of sense to ensure that there's a fully complete and fully Julia backend, but at the same time it limits the usefulness if it has to be directly required.

Could this work with a software renderer? https://stackoverflow.com/questions/7310885/opengl-without-a-graphics-card
Or maybe virtualgl?

There is CairoMakie now.

On a headless system without graphics card I installed software rendering and glxgears works fine.
I also installed Makie and it works fine if I use ssh -Y server.
Using xpra you can launch a virtual x server on the headless system and use that (https://help.ubuntu.com/community/Xpra) so you don't need to use ssh -Y
There was one warning:
Warning: GLFW.GLFWError(PLATFORM_ERROR::ErrorCode = 65544, "X11: RandR gamma ramp support seems broken")

You can even use a local xpra and open the display on the remote server, but mouse interaction will produce tons of error messages on the remote julia console.
Next step is to get it working inside Jupyter notebooks... I will let you know if I manage to do that.

Pretty cool you got that running - and it doesn't even sound that complicated ;)

It was not that complicated. How do I resize the window opened by Makie from within Julia? My current issue is that the window opened in xpra is tiny and therefore it is saved as a tiny png.

You could try passing a resolution to the Scene?  For example, sc = Scene(resolution = (1920, 1080))

p = Scene(resolution = (1920, 1080))
volume!(p, rand(32, 32, 32))
save("make_test.png", p)

works on my machine, but the png is still tiny on the headless machine.

Hm, the only reason it would ignore this, if it somehow thinks that Juno is there!
https://github.com/JuliaPlots/AbstractPlotting.jl/blob/master/src/display.jl#L59
If you use remote Atom, try disabling the plotpane!

I am trying to make it work with jupyter notebooks, I am not using Atom. I also tried resize! and it does not work. Maybe it has something to do with the display size (the monitor is 0mm x 0mm):
me@server:~$ xrandr -d :7 -q
xrandr:Failed to get size of gamma for output default
Screen 0: minimum 320 x 175, current 5280 x 1920, maximum 8192 x 4096
default connected 5280x1920+0+0 0mm x 0mm

... a list with all possible resolutions

I tried changing the resolution with xrandr but without success.