Unable to assign config file

Hi
I had a statsdaemon running on my server 2 days back. It was having issues sending metrics so I decided to reinstall it. But ever since I trying to assign a config file to it, I am getting the below error
Could not read config file: /tmp/statsdaemon/statsdaemon.ini is not a valid TOML file. See https://github.com/mojombo/toml
I see a couple of commits made yesterday. Is anyone seeing the same issue

New config lines were added that do not exist
#prefix_m20_rates = ""
#prefix_m20_counters = ""
#prefix_m20_timers = ""
#prefix_m20_gauges = ""

So the issue seems to be the numbers in the key.
put this in the ini file
prefix_m20 = "dasf"
../build/statsdaemon -config_file statsdaemon.ini  -debug
Could not read config file: **prefix_m** is not a valid config setting

So for some reason the numbers are getting lopped off.

looks like there was a bug in the toml library we're using.
As per commit above, it should be fixed now. please confirm.

confirmed solved.


Create Compute Studio app for OG-USA

OG-USA should run on Compute Studio.

I can't wait for OG-USA to have a webapp. Taking care of #491 first should make this straightforward. @MattHJensen suggested just doing steady state calculations while we are getting started. Does that seem reasonable?
Let me know if there's anything I can do to help out with this.

@hdoupe Yes, good idea to start with the steady-state calculations to make sure everything is up and running smoothly.

@hdoupe Do I need an ogusa package on Anaconda to get things working on Compute Studio?   I've had some trouble building an ogusa package with Package Builder lately...

Nope, Tax-Cruncher is installed with git: https://github.com/PSLmodels/Tax-Cruncher/blob/master/compconfig/install.sh

@hdoupe Great!  I'll get the Compute Studio stuff up before I mess with Package Builder again!

Resolved with PR #496.  Thanks for the help @hdoupe !


Updated .travis.yml

Updated .travis.yml to use Xcode 7.

@ClementPadovani there is something seriously messed up with the tests or something. Need to check that out.

I tried xit-ing the failing test and it still craps out :(

@markohlebar The tests work some of the time actually lol

Actually it’s xctool that’s crashing


[Mobile][NUI] Sample geofence

Rewriting Geofence sample from Xamarin to NUI

@bchrescionko @dongsug-song would you review & update this PR?


[BEAM-6950] Upgrade spotbugs to version 4.0.3

R: @pabloem

Run Java PreCommit

Run JavaPortabilityApi PreCommit

Run JavaPortabilityApiJava11 PreCommit

lgtm given that the we can get precommit to pass before merging


Config References dropdown truncates the full config name

Describe the bug
If a lengthy (approximately 20 characters) Config names are used, then attempting to select one within the ConfigWizard -> Sim Variable (tab) -> Config References, is difficult as you have to enumerate each option manually to see the full name.
Steps To Reproduce
Steps to reproduce the behavior:

Enter a number of config items with long names
Edit any one, and attempt to select another one in a Config References dropdown

Expected behavior
The dropdown is sufficiently wide to display longer names.
Actual behavior
The dropdown width is short and prevents easy selection:

Details

MobiFlight Version: 9.0.0

Additional context
Config names are often prefixed to ensure that they are grouped logically when sorting by name. This is also driven by the fact if you sort by any column you lose the original config order (as entered) and have no provision to return to the original sorting.
This could be addressed by increasing the width of the dropdown shown within the Configure References.

Agree !
Thats a point also in some other spots.....   ( I thought to report as Bug many times in the past myself)
I know these things will be much more better in a future full reworked GUI....  But maybe its also time NOW to temporary solve this also for now.
In upper example we  see there is still a lot of Space right of the Config Symbols.....   So it would be no big deal to increase  this whole field ( include Dropdown) by 100-200%  ....  No mater if the Symbols move fully to the right corner !
Additional we could also enlarge the whole MF Window up to HD 1920-1080 Full screen if we like this.
May its no longer "State of the Art" to work with these small Windows.

@ssewell
About temporary solution ( like i do) ....  Simply reduce name Length by cleanout all unless text!
In your case the whole Config File pretty sure is for a Airbus A320.....   So the Information "A32NX" is not needed.
Also the Area "FCU" can be used as a simple Single Character....  A-Z means 26 individual Areas.
So in your example....  Current Name "A32NX FCU - 31-"  need 16 Chars (Including not needed Spaces).
If you use "A31-" You need 4 Chars instead ..... "A" represent e.g. FCU ....  Number remains the same .
You see.... 12 Chars more of the real Config name without a disadvantage . Better result in same GUI !

@pizman Here's what it would look like if updated to take up more of the available realestate. Would definitely address the issue.

Perfect!
Is this just a Photoshop Rework OR  Do you script this in a custom Version ??
If scripted.... Please give this data to Sebastian and contact him
This will be a nice new feature/rework for V9.1

Closing this to submit a cleaner pull request without superfluous commit history.


Bern features: Labels of a category belonging to a series can only be edited in the video where it was created

When I create a category that belongs to a series in video A and then edit this category in video B, changes in the title of the category do appear in video A (of course after a refresh/reload). Which is fine.
But when I change labels, these changes only get saved temporarily and locally. When I reload the page after having made changes in video B, the changes are lost and the labels are the same as before. Also the changes do not get transferred to video A.
All changes that I make in video A get transferred to video B.
Solution: Please make sure that all changes to category titles and labels are always saved permanently and do alsways get transferred to the other videos of the same series.

Good catch, thanks.
With the most recent commit fe10fe1 to the PR #414, all changes to labels made on video B should now persist and transferred to other videos of the same series.
Have you found anything else that does not get transferred besides from video B to other videos besides the labels (and of course scales, as we are currently not allowing scales on series categories)? For example category name or color.

Changes of category name and color do get transferred. Everything what I do with labels does NOT get transferred: Edit label name, add label, remove label

Looks fine and can be closed. Thx!


Add Entity Builder

This PR introduces an EntityBuilder which helps users create entities and cuts down the verbosity required to do so.
It includes:

Forcing a user to provide a position (required component).
Automatic building of the EntityACL component (required component).
Making users specify a write-access layer when adding a component.
Providing special methods for other well-known components (Metadata and Persistence).

These four features makes it much less error-prone when creating entities. However, there is still one place to trip up on:

Setting read layers is still done in a separate method. This is easy to mess up (by omission). We could make this part of the EntityBuilder constructor to force users to pass this in, but the constructor will start to get very long.

Note that there is a little bit of hackery in the implementation as we need to "access" code generated types (Position, EntityAcl, Metadata, EntityAcl) but do not have the generated code available at compile time. To get around this, we manually serialize the data (since its a well known shape) then deserialize inside the Entity itself. (At runtime we do expect to have these types defined). Do we expect the add_serialized method on Entity to be used elsewhere? Or can it be folded into the EntityBuilder as an implementation detail?
Fixes #25

An example of the EntityBuilder API:
    let entity = EntityBuilder::new(0.0, 0.0, 0.0, "rusty")
        .add_component(
            example::Rotate {
                angle: rng.gen_range(0.0, 2.0 * f64::consts::PI),
                radius: rng.gen_range(20.0, 100.0),
                center_x: rng.gen_range(-50.0, 50.0),
                center_y: 0.0,
                center_z: rng.gen_range(-50.0, 50.0),
            },
            "rusty",
        )
        .add_component(
            improbable::Metadata {
                entity_type: "Rotator".to_owned(),
            },
            "rusty",
        )
        .set_read_access(&["rusty"])
        .set_write_access(EntityAcl::ID, "rusty")
        .build()
        .unwrap();

Ah heck, looks like you're running into exactly the sort of issue #56 is intended to fix! Unfortunately, my work on that isn't nearly far enough along for it to be worth waiting on, so I think moving forward with the hacky stuff here makes sense. Once #56 is closed we'll be able to remove add_serialized entirely.

Is there a meaningful difference between Entity and EntityBuilder? Entity already has the add method for attaching components (which EntityBuilder is using internally), so it seems like Entity builder just changes/extends the API of Entity, in which case would it make more sense to change Entity directly to have the improved API?

So there's one thing that would stop me from merging the two APIs - when would we serialize the EntityAcl?
You could have a build_acl() method, but nothing stops a user adding more components afterward and shooting themselves in the foot. Its an instance where not only do you have to remember to call a specific method, it has to be at a specific time.
(On that topic, we may want to remove the public facing add_component method on Entity to prevent similar errors here)
In theory #56 solves that issue since you never have to serialize, but I'm not 100% convinced that we should have a crate contain the generated code and user code which operates on that generated code (a discussion for another day).

Ah, building the EntityAcl is a good point! In that case, I agree that it would make more sense to remove the public Entity::add method (or at least make it private to the crate) and make it so that EntityBuilder is the only way to construct the serialized representation of an entity.
That would also address a concern I'd been having about Entity, that it's current purpose is a bit unclear. It's both used to create the serialized representation of an entity, but it's also used to read serialized entity data sent from the runtime (which can't be modified). But if Entity represents the immutable, serialized version of data, with EntityBuilder creating the data in the worker or already-serialized data coming in from the runtime, I think that makes for a pretty clean API :+1:

Would it make sense to automatically build read_permissions from layers that are given write access to the components? i.e. if you don't call set_read_access, it defaults to given read access to any layers that are given write access to one of the component types? I imagine it's pretty rare to give a layer write access to a component on an entity without giving that layer read access to the entity.
Actually, is that ever a valid thing to do? Should we have EntityBuilder always give read access to any layer that has write access to one of the components? We could then change set_read_access to something like add_read_access to allow users to grant additional layers read access without allowing them to forget to give read access to layers that have write access. I haven't used SpatialOS enough to know if this makes sense, though. Thoughts?

I think you are correct, write access should imply read access - there is one edge case I can think of, but I'm not sure what the load balancer would do in that case:
If you have an entity which you delegate read access to a specific worker (i.e. - workerId: RustWorker-1) but then delegate write access to its entire layer (rusty). I don't know if the load balancer can resolve that. Obviously, if you were doing this, you'd just delegate write access to that specific worker as well - but the previous configuration could also be valid..?

We could then change set_read_access to something like add_read_access to allow users to grant additional layers read access without allowing them to forget to give read access to layers that have write access.

This does seem sensible though

For the edge case you're imagining, is that a valid use case or indicative of a configuration error on the part of the user?
Also, I can vaguely imagine a case where it makes sense to grant write-only access to a component (maybe for the purpose of security and information hiding), but I think it makes sense to disallow doing so until we have a concrete use case, since it seems too easy to do by mistake and end up creating an invalid configuration.

@randomPoison So I've made the following changes:

Made add_component internal to the crate on Entity.
Removed the builder method chaining from the EntityBuilder.
Changed set_write_access to set_entity_acl_write_access.
Whenever a layer is added as write access, it is added as read as well.
Changed set_read_acess to add_read_access


Change localhost to server IP address

Hi,
I was able to set up azkaban solo server on my laptop and access it via http://localhost:8081/ without any problem.
Is there a way how to set the solo server on AWS EC2 instance and access it from outside (my laptop's browser)? I would assume I have to change localhost to server IP address but I do not know how or even if this is the right approach.
Thanks for any help!

you should check your computer whether can connect your server like this:
telnet  ip 8081。
maybe firewall stop your connection....


Max Stack Size displays in new update

Since the recent update, Max Stack Size is showing up again. Previously, there was no display for max stack size, it would instead only display the current stack.

Fixed in #3

Since the recent update, Max Stack Size is showing up again. Previously, there was no display for max stack size, it would instead only display the current stack.

Fix in 1.1.1


[WIP] Permissions Grants for MessagesGet

Codecov Report
Attention: Patch coverage is 52.94118% with 112 lines in your changes are missing coverage. Please review.

Project coverage is 97.49%. Comparing base (40567c9) to head (ab3ebf2).

Files
Patch %
Lines

src/core/messages-grant-authorization.ts
34.93%
95 Missing :warning:

src/handlers/messages-get.ts
77.33%
16 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #748      +/-   ##
==========================================
- Coverage   98.53%   97.49%   -1.04%
==========================================
  Files          71       72       +1
  Lines       10646    10835     +189
  Branches     1548     1556       +8
==========================================
+ Hits        10490    10564      +74
- Misses        150      264     +114
- Partials        6        7       +1

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


yarn.lock immutability broken by bin

Hello,
first, thank you for this great tool !
when a package.json is containing a bin section, the generated package.json try to change the yarn.lock on yarn install

Can you share a small example package.json? So that I can also add a test case

Also, which version of yarn are you using?

{
"dependencies": {
"tiged": "^2.12.4"
},
"bin": "./bin/my-executable",
}
yarn 3.5.0

here is the PR: https://github.com/rohit-gohri/yarn-lock-to-package-json/pull/3


model_vqa_science.py not found

Hi! Thank you for your very helpful work!
When I run the pmc_vqa.sh, llava.eval.model_vqa_science.py is missing.
Looking forward to your reply! Thank you!

Thanks for pointing that out, It's been added in. I apologize for the issue, we were trying to make the codebase as lean as possible and missed that eval code. Let us know if you run into any other issues.

Hi! Thank you for your reply.
When I run the quilt_red_vqa.sh, quiltvqa_red_test_wo_ans.jsonl is missing. I download the red_circle.zip, but there isn't the missing file.
Looking forward to your reply! Thank you!


Add dependabot

This is a test pr to be deleted

The test was completed successfully.
I am deleting this branch as required.


⚠ Bofrost.at has degraded performance

In 061a0cc, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1256 ms

Resolved: Bofrost.at performance has improved in ceb9271.


Willing to accept a PR if I add a setup option "default commentstring"?

Hi,
I find it kind of annoying when I frequently encounter filetypes that are unknown to Comment.nvim, including plain text files without a set filetype, where it just says [Comment.nvim] Invalid commentstring for ! Read :h commentstring\ for help.
The editor Micro just has a default comment string of # %s for unknown filetypes, and I think that's especially useful because often times configuration files don't have a specific extension like .conf, and in that case, most often the comment string is #.
For my own use case, I'd really like to just set the default to # %s when the filetype is not known to Comment.nvim. But since this would be significantly changing the plugin's behavior, I'm not sure whether it's appropriate to set this as the default, or if it should be a configuration option, like require('Comment').setup({ default_comment_string = '# %s' }). I'm happy to try and do the implementation myself and update the docs, but I figured I'd ask first to see what you think about which implementation is most appropriate for the way you want the plugin to behave (and if you're fine with the change in the first place).
Thanks!

I think you can just do something like this to set a default commentstring yourself?
vim.api.nvim_create_autocmd("FileType", {
   pattern = { "*" },
   callback = function(event)
       vim.api.nvim_buf_set_option(event.buf, "commentstring", vim.api.nvim_buf_get_option(event.buf, "commentstring") or "# %s")
   end,
   group = vim.api.nvim_create_augroup("commentstring", { clear = true }),
})

I think you can just do something like this to set a default commentstring yourself?
vim.api.nvim_create_autocmd("FileType", {
   pattern = { "*" },
   callback = function(event)
       vim.api.nvim_buf_set_option(event.buf, "commentstring", vim.api.nvim_buf_get_option(event.buf, "commentstring") or "# %s")
   end,
   group = vim.api.nvim_create_augroup("commentstring", { clear = true }),
})

@Amzd Thanks for the suggestion! I just tried this, but it doesn't seem to be working quite as expected. I put it inside my init.lua, and added a print statement:
    vim.api.nvim_create_autocmd("FileType", {
      pattern = { "*" },
      callback = function(event)
        print("Hello world, my commentstring is: " .. (vim.api.nvim_buf_get_option(event.buf, "commentstring") or "# %s"))
        vim.api.nvim_buf_set_option(
          event.buf,
          "commentstring",
          vim.api.nvim_buf_get_option(event.buf, "commentstring") or "# %s"
        )
      end,
      group = vim.api.nvim_create_augroup("commentstring", { clear = true }),
    })

and I get the "hello world" when loading files like .lua, .py, .js, etc. but if I have a plaintext file, or something like test.conf or test.filetypeunknown, the message doesn't print to the console. Could it be that the FileType event doesn't fire for files of an unknown type? Any idea if there's another way to accomplish this?


Fix LED color order in the demo page.

Thank you so much, good catch. I'm sorry, I wasnt getting notices for this repo or I would have merged earlier.


Implement the Central Bank of the Republic of Uzbekistan Service

The PR provides a service for fetching UZS exchange rates directly from the Central Bank of the Republic of Uzbekistan.

Thanks @uguurozkan !!!


⚠ Bofrost.lu has degraded performance

In c004305, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1107 ms

Resolved: Bofrost.lu performance has improved in 827c83c after 6 minutes.


How to ignore particular test case (DataRow)

Description
I am trying to ignore one test case by adding Ignore keyword for DataRow attribute:
[TestClass]
public class MathTests
{
    [TestMethod]
    [DataRow(1, 1, 2)]
    [DataRow(2, 2, 3), Ignore]
    public void Sum_Test(int a, int b, int expectedSum)
    {
        var sut = new Math();

        var sum = sut.Sum(a, b);

        Assert.IsTrue(sum == expectedSum);
    }
}

public class Math
{
    public int Sum(int a, int b)
    {
        return a + b;
    }
}

but it ignores the whole test:

I also asked this on StackOverflow: How to ignore particular test case in MSTest.
Expected behavior
Only Sum_Test(2,2,3) test case should be ignored.
Actual behavior
It ignores both test cases.
Environment

Operating system: Windows 10 Pro
Target: .NET 6
MSTest.TestFramework: v2.2.8

Looks like there is no such option. The most appropriate option is just comment DataRow statement.
However, would be good to have something like this [SkipDataRow("because this edge case is postponed", 2, 2, 3)], thus enabling to specify ignore reason.

Hi @adamshakhabov,
I'd like to understand why you would prefer to have a property/different attribute... to skip a DataRow instead of simply commenting it out? Are you interested in building some analyzer or tracking number of skipped tests?

Hello @Evangelink,
thank you for the reply🙂
"DataRow" is a piece of code. Commenting on code is not allowed in our team. I believe it is not a rare case. And yes, in the test result, I would like to have an opportunity to track the number of test cases that were skipped.

@adamshakhabov it perfectly makes sense and you are not the only team with such rule. I just wanted to confirm the intent so we could think about how to implement it.

My case is that I have tests that take a long time (>2 mins) I would like them to not run by default but I would like to be able to run them sometimes without having to change the code.

@tymtam2 Thanks. I would probably recommend for your case to have different tests and use categories to split tests you want to run.

We have failing test cases we'd like to ignore with messages indicating ticket number for resolution of the issues. We'd like to ignore rather than comment to maintain visibility of them in our test reporting.

Any updates on this issue? We're having temporary problems with an integrationtest where some datarows will fail due to problems within the called api. While we're waiting for a hotfix on the api-side, we would like to keep these datarows "alive" with the Ignore-attribute in order to fix them later. Commenting them out will increase the risk to forget about them even when the hotfix is pushed.


[MRG] Adding AverageTFR.plot_joint() method

See issue https://github.com/mne-tools/mne-python/issues/3801
Adding aggregate to plot method in averageTFR class

Added aggregate (mean or rms) and exclude arguments to averageTFR.plot

Set picks argument to default None

Created internal _plot method called by averageTFR.plot

Added automatic title option in _plot method

Implementing plot_joint method in AverageTFR class

Timefreqs and timefreqs_average arguments to specify values to be used

for topomaps.

Timefreqs can be iterable of tuples or 'peaks', where topomap is

plotted for maximum peak in tfr

exclude and aggregate arguments in plot_joint

Added contour argument in plot_tfr_topomap

Moved connection_line method to viz/utils from viz/evoked and added y

argument.

Adding test_joint_plot

Looks great!
What about the units for the cbar?

@hubertjb great work! It seems we're close to finishing this :)

@jona-sassenhagen should we add a unit argument in plot_joint? This argument is used in average_tfr.plot_topomap to set the colorbar title for individual topomaps

Can't units be inferred?
'units' seems like something that 1. should be supplied as a default during the call to plot_topomap, 2. with user overried via topomap_args.

from itertools import cycle

timefreqs_average = (1, 1) if timefreqs_average is None else timefreqs_average
for map_ax_, (time, freq),  av in zip(
    map_ax, timefreqs, cycle(timefreqs_average)):
    time_half_range, freq_half_range = (x / 2 for x in av)

I think this'll save a lot. Becomes even simpler with dicts:
for map_ax, (time, freq) in zip(map_ax, timefreqs):
    time_half_range, freq_half_range = (x / 2 for x in timefreqs_average.get((time, freq), (1, 1))

... ok. Maybe this is golfing it.

Circle CI crashes into some case where for some reason no data is selected:
/home/ubuntu/mne-python/tutorials/plot_sensors_time_frequency.py failed to execute correctly:Traceback (most recent call last):
  File "/home/ubuntu/mne-python/sphinx-gallery/sphinx_gallery/gen_rst.py", line 475, in execute_code_block
    exec(code_block, example_globals)
  File "<string>", line 4, in <module>
  File "<string>", line 2, in plot_joint
  File "/home/ubuntu/mne-python/mne/utils.py", line 707, in verbose
    return function(*args, **kwargs)
  File "/home/ubuntu/mne-python/mne/time_frequency/tfr.py", line 1378, in plot_joint
    colorbar=False, show=True, **topomap_args_pass)
  File "/home/ubuntu/mne-python/mne/time_frequency/tfr.py", line 1700, in plot_topomap
    contours=contours)
  File "/home/ubuntu/mne-python/mne/viz/topomap.py", line 1098, in plot_tfr_topomap
    idx = np.where(_time_mask(tfr.times, tmin, tmax))[0]
  File "/home/ubuntu/mne-python/mne/utils.py", line 2360, in _time_mask
    % (orig_tmin, orig_tmax, times[0], times[-1]))
ValueError: No samples remain when using tmin=1 and tmax=1 (original time bounds are [-0.998976065792, 2.98102393421])
________________________________________________________________________________

@jona-sassenhagen concerning units, it looks like AverageTFR.plot() doesn't yet have an argument for units either.
I guess the units might differ based on which TFR function was applied, as well as on the original unit of the time series. Would we want to cover all possible cases?

Units: personally I'd chose the easiest possible path for now and go about fixing it for both as soon as this one is merged.

Codecov Report

Merging #4134 into master will decrease coverage by 0.12%.
The diff coverage is 83.21%.

@@            Coverage Diff             @@
##           master    #4134      +/-   ##
==========================================
- Coverage   86.18%   86.05%   -0.13%
==========================================
  Files         354      356       +2
  Lines       63737    64176     +439
  Branches     9711     9770      +59
==========================================
+ Hits        54933    55228     +295
- Misses       6128     6246     +118
- Partials     2676     2702      +26

@hubertjb as we're almost done, want me to take over?

@jona-sassenhagen this commit should answer your latest comments.

You see I have a bunch of very superficial comments, but there might be a bigger problem here: it seems you did a merge commit. I think we don't do that, ever (we rebase). I'm not sure what the correct response is though, maybe you have to roll back?
@Eric89GXL ..?

Besides for that, I think we're largely done. The Travis error is just one doc problem. @hubertjb if you think this is ready, we'd need  reviews from somebody else - maybe @jaeilepp or @mmagnuski ?

@jona-sassenhagen I see, the merge was unnecessary at this point. I should be able to just revert the merge and wait for the branch to be ready for a rebase. Also, I'll address @jaeilepp's and your latest comments. I guess after that I can change the title of the PR to [MRG], right?

@jona-sassenhagen the best way to get rid of that merge seems to be a git reset to the previous commit, and then a force push. Do you think that makes sense? I could also do a git revert, but that would leave a trace in the git history.

I guess after that I can change the title of the PR to [MRG], right?

Yes, go for it.

Do you think that makes sense?

I don't know :(
I think so I guess.

Note to self (and to @mmagnuski https://github.com/mmagnuski ): when this one is done, the code should be refactored and reused for evoked.plot_joint_image.

I'm not sure why Travis failed here... Could that come from the rebase?

Seems unrelated. I restarted the job.

Green.

Cool, thanks @jaeilepp!

There's something weird with the yticks. Check this:
%matplotlib inline
import mne
from mne.datasets import testing
from mne.time_frequency import tfr_morlet

data_path = testing.data_path()
fname = data_path + "/EEGLAB/test_raw.set"
montage = data_path + "/EEGLAB/test_chans.locs"

event_id = {"rt":1, "square":2}
eog = {"FPz", "EOG1", "EOG2"}
raw = mne.io.eeglab.read_raw_eeglab(fname, preload=True, eog=eog,
                                    montage=montage, event_id=event_id)
events = mne.find_events(raw)
picks = [idx for idx, ch in enumerate(raw.ch_names) if ch not in eog and ch != 'STI 014']

epochs = mne.Epochs(raw, events=events, event_id=event_id, picks=picks, tmin=-1, tmax=2)
tfr = tfr_morlet(epochs, np.arange(3, 20), n_cycles=3, return_itc=False, n_jobs=-2)
tfr.plot_joint(baseline=(None, 0), show=False);

Not catastrophic, but could be better.
Also, is the colorbar scaled correctly?
Annnnnnd lastly, for some plots I'm getting truncated colorbar vlims:

See what I mean?

All in all I think it looks great, and I'm happy with the API.
timefreqs = {(.4, 3): (.1, .2),
            (.6, 11): (.1, .2)}
tfr.plot_joint(baseline=(None, 0), show=False, timefreqs=timefreqs, title="EEGLAB Squares");

@jona-sassenhagen the figures look good, indeed. The yticks placement is a known problem, I wanted to correct this for some time, I'll try to make a PR tonight.

@jona-sassenhagen I'm not sure I understand what you mean with the colorbar scaling and truncated vlims. The topoplots' color range depends on the vmin and vmax of the TFR plot, and so does the colorbar indirectly, so they should all have the same color range.

What I mean is, it looks like the topomap vlims aren't the data limits, but narrower, so you have the big red surface. Particularly here.

@jona-sassenhagen I see. A way to fix this would be to look at the vmin and vmax of each topomap and of the TFR plot, and then decide on the colorbar boundaries by aggregating them somehow. Currently only the vmin and vmax of the TFR plot are used.

I don't get why they're different ... is this maybe because TFR.plot in this case aggregates and passes the aggregated data (which will have smaller max and min)?

@jona-sassenhagen
The default is to aggregate across all picks with mean - tf_data, the reduced data, is used for setting vmin and vmax. In most cases this will make the limis different (especially for the frequencies with most pronounced changes wrt the baseline). Maybe the topos should have a separate colorbar? Because setting the limits of tfr to match the limits in the topo may make the tfr look pale (or - in other cases - the topo would go pale).

	I guess it doesn't make much sense to share the vlims.

Right, it would be more informative to have separate colorbars. Do we want one colorbar by element (TFR plot, and each topomap) then? If so I'll add that and update the PR.
Also, would we want to keep an option to have a single colorbar and share vlims across the different elements? I guess it could be useful for a quick visual comparison between e.g., the TFR of a single channel and the other channels as seen on the topomaps.

	Hm. Can't we have one colorbar, just different vlims? Maybe the tfr will look pale, so be it.

Unless we actually have different unit, eg when the tfr isn't the mean, but the gfp. I'm not sure.

Ok, so if I understand well:

If the TFR plot is an average (and not the RMS), have the colorbar scale with the largest vlims of all subplots (including topomaps and the TFR plot). This might make the TFR plot look pale, but the topomaps will be more informative.
If the TFR plot is the RMS, we might have to do things differently. However, the units should still be the same, right? I understand the scale could be very different though. Maybe in that case multiple colorbars would be necessary?

I'm not sure :(

Currently my intuition is the colorbar should only be valid on the topomaps. E.g., don't have a colormap for the image (which is an average anyways).
Does that simplify things?

@jona-sassenhagen Sorry for the delay!
OK, just double-checking before I implement. Here's what I'll do:

For each specified timefreqs interval, find vmin and vmax. I'll make a new utils function, similar to the first few lines of topomap.py:plot_tfr_topomap(), that extracts and aggregates the data in the right time and frequency range, and returns the min and max of the array.
Aggregate all topomaps' vmins and vmax. In the simplest case, the final vmin and vmax are the smallest and biggest of all vmins and vmax, respectively.
For each specified timefreqs interval, plot a topomap with previously found vmin and vmax. This is identical to what we already have, except that we wouldn't use the vmin and vmax of the TFR plot anymore, but the ones that come from the topomaps instead.
Draw the colorbar using the previously found vmin and vmax.

Also, I was thinking the arguments vmin and vmax could also accept a string, letting the user choose the source of the vmin and vmax. For example, it could take value 'tfr' if the user wants everything to use the vmin and vmax of the TFR plot, or value ''topomap' if the user wants the colorbar to reflect the aggregated vmin and vmax of the topomaps. Would that be worth it?

@mmagnuski what do you think of this solution?

For each specified timefreqs interval, find vmin and vmax. I'll make a new utils function, similar to the first few lines of topomap.py:plot_tfr_topomap(), that extracts and aggregates the data in the right time and frequency range, and returns the min and max of the array.
Aggregate all topomaps' vmins and vmax. In the simplest case, the final vmin and vmax are the smallest and biggest of all vmins and vmax, respectively.
For each specified timefreqs interval, plot a topomap with previously found vmin and vmax. This is identical to what we already have, except that we wouldn't use the vmin and vmax of the TFR plot anymore, but the ones that come from the topomaps instead.
Draw the colorbar using the previously found vmin and vmax.

Looks sensible to me.

Also, I was thinking the arguments vmin and vmax could also accept a string, letting the user choose the source of the vmin and vmax. For example, it could take value 'tfr' if the user wants everything to use the vmin and vmax of the TFR plot, or value ''topomap' if the user wants the colorbar to reflect the aggregated vmin and vmax of the topomaps. Would that be worth it?

Maybe, but I'd do the other stuff first.

@mmagnuski do you perhaps have time to finish this one up? Would be nice to finally have it.

@jona-sassenhagen I should have time next week (starting tomorrow) for some mne stuff, so I can try :)

I miss this function every day. Would like to take over and finish this great code, if that's ok with everyone.

@jona-sassenhagen From my side: sure, would  be great!

@jona-sassenhagen it would be great, thanks!


mistralai[patch]: enforce stop tokens

@efriis I don't suppose we have guidelines about how chat models should be have with respect to stop tokens?

Not at the moment but given it's part of the base interface I feel like it makes sense to respect them. Happy to discuss

Should the stop token itself be dropped or only what follows it?
If we drop it we need to make sure parsing logic can be implemented with runnables (I think it cannot be?)

Leave as warning for now. Maybe implement enforcement as an output parser / transform type thing.


Updated Travis configuration.

Updated the building script according to the change of introducing
CocoaPods.

it seems the current version of CocoaPods in Travis build slave VM does not support the 'use_frameworks!" parameter, this issue will get fixed after the CocoaPods version in Travis get updated.


do statement in complex ? : chain of operations generates bad code

do statement in complex ? : chain of operations generates bad code.  For example:
      $result =
        $type eq '&' ? 1 :
        $type eq '$' ? 2 :
        $type eq '@' ? 3 :
        $type eq '%' ? 4 :
        $type eq '*' ?  5 :
        do { require Carp; Carp::croak("Bad type") };

This turned out to be an issue caused by the issue 176 fix


4 channel mixer, no solo/mute function

The Solo/Mute buttons on the 4-channel mixer are non-functional ( VCV 1.1.0, MacOSX 10.8.5 )
I tested the 9-channel mixer, and it works fine.

Ok thanks for the info, I will look into it.

Same here, on MacOS 10.12.6. This little mixer is now my go-to mixer, so hope it's a little commenting error that can be easily fixed. Love your work!

Confirmed on Linux VCV Rack v1.1.1. MIX 24 and MIX 9 working fine. ;)
But having MIX 9 as in-line mixer somewhere is okay for me. ;)

Should be fixed now, thanks for the help

Yes, and thanks so much!


Number of seconds that a round can last can be passed as a parameter in the body of the request to the lobby creation endpoint to change the duration of the round from the default

32b02a950af018cc84f21118d515aaa5d4ad2c2d


Export to CSV - Duplicate 'Use Case' tabs

Describe the bug
When exporting to CSV there are duplicate 'Use Case' tabs
To Reproduce

Click 'Catalog'
Then, click the 'Export to CSV' Icon

Expected behavior
Tabs should not be duplicated
Screenshots

Additional context
Add any other context about the problem here.

Not related to the Parasol workshop but to the demo system UI.

Raised as feedback on the Parasol Demo site.


Optional chaining form

We probably should allow a.b?.::c(), like how we allow a.b?.c() and a.b?.(). I will amend the specification later.

I'd expect a.b::c?.(), but since :: is not a property access, I'm not sure I understand why it'd need to be optional.


Add create-stack action.

Summary
This PR adds a new action to create stacks. The behavior of this action is a superset of what currently exists in various workflows (create-release, test-pull-request, etc); it adds support for providing secrets.
In addition to providing new functionality, it also enables reduction of duplication of the existing logic in the existing workflows.
This PR intentionally does not update the workflows to use this action - that will come in a future PR once each workflow has been validated to work with this action.
Use Cases
This PR enables workflows to provide secrets when creating stacks, as well as reduces duplication of stack creation across workflows.
Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@robdimsdale to be clear, this will refactor lines like these?
https://github.com/paketo-buildpacks/github-config/blob/438ff51ad4871b9cb9c540dc154350dead3e5621/stack/.github/workflows/create-release.yml#L144-L153
https://github.com/paketo-buildpacks/github-config/blob/438ff51ad4871b9cb9c540dc154350dead3e5621/stack/.github/workflows/test-pull-request.yml#L21-L30
With the added benefit of being able to using secrets?

The action environment will have access to a docker daemon, right? When I run this action locally I run into issues with the Docker daemon but I realize that's because Docker isn't running on the container.


Killing mojdsd

We need to discover what is left within MoJDSD and determine what is important.

Stale.


Fix LONGTEXT column type migration for MySQL

Without this fix LONGTEXT column type is converted to TEXT type
which isn't big enough to store large data like allowlist.
Signed-off-by: Karel Srot<EMAIL_ADDRESS>

You can't update an existing migration with changes because it won't work on existing installs. You must create a new migration for that.

I think it is fine because it is currently broken, so nobody could have a working install with that. We already did something similar here: https://github.com/keylime/keylime/pull/815
The test is failing because of an upstream issue: https://github.com/sqlalchemy/alembic/issues/982

I can confirm it is currently broken (for a MySQL test installation).

It's only broken if they try to use large allowlists. Maybe they were doing signatures before, or had small allowlists and large exclude lists (focusing only on the kernel or something else). Doing the fix like this instead of as a new migration will mean they will have to destroy their database, then upgrade and let keylime recreate the schema. I'm against any fix that requires something like this which can just be a new migration and upgrade like any other.

It's only broken if they try to use large allowlists.

Oh, I thought it was fully broken for MySQL. If not then I agree that we need to add an migration on top of this fix to also change it current installations.

Would that be just another file with different name? Or is it more complicated?

Would that be just another file with different name? Or is it more complicated?

You need to create a new migration file with alembic:
alembic -c keylime/migrations/alembic.ini revision -m "Added account table"

Alembic can be a tricky tool to use as it's not in the normal development flow. I don't mind taking a crack at it if you'd like @kkaarreell

@mpeters I have some free time now and can do that... whomever does it, please keep in mind that the mb_refstate column needs to be fixed too

Alembic can be a tricky tool to use as it's not in the normal development flow. I don't mind taking a crack at it if you'd like @kkaarreell

Please do @mpeters or @maugustosilva . Thank you.

@mpeters I have some free time now and can do that... whomever does it, please keep in mind that the mb_refstate column needs to be fixed too

@maugustosilva would you mind taking a crack it since you want this other change in there as well?

Certainly, on it

Should I close this PR?

I am sorry, I am already OOO, will check it tomorrow. Eventually, you can check it using tests from pgsql branch of keylime-tests. Either on Fedora system with tmt or by modifying the test to run additional SQL command and creating PR for keylime-tests repo.

@kkaarreell while attempting to deploy with MySQL, I see the allowlist column is already of type LONGTEXT, but mb_restate is not. Are you seeing differently in PostgreSQL?

To clarify, the problem I was observing was with mariadb on F35. PostgreSQL didn't manifest that problem with insufficient field size for allow list.

New migration was added to fix this in https://github.com/keylime/keylime/pull/871


ORC-318. Change KeyProvider API to separate createLocalKey

Separate createLocalKey from decryptLocalKey in HadoopShims.KeyProvider.
It also:

changes HadoopShims.KeyMetadata from an interface to a concrete class
creates a NullKeyProvider for Hadoop versions < 2.7

Ok, I significantly updated this patch.

I added tests for both the InMemoryKeyProvider and the Hadoop-based KeyProvider.
I allowed the user to pass in a Random implementation for the KeyProvider. That allows me to control the random for tests.
I added a lot of documentation about what I was doing and why.
I fixed an issue where the HadoopShimsFactory wasn't creating the right version of the shim.
I changed the InMemoryKeyProvider to use AES/CBC/NoPadding to encrypt and decrypt the local keys. Thus like the AWS KMS, the operations for encryption and decryption aren't symmetric.


[DIR-209] set live status on workflow

Preview
This adds the ability to turn the workflow active / inactive.
It's implemented on top of the branch for the workflow settings page in PR #447.
I made the dropdown trigger variant="primary" as well, but that doesn't look good when the main button is inactive:

So I changed the dropdown trigger to "outline", but only when the other button is inactive. It's not 100% logical to have the dropdown button active in the second example, but that way it blends in naturally with the main button.

[x] should we add a tooltip to the button when the workflow is inactive? I think the button is already pretty self-explanatory (at least when you investigate and click on the dropdown)

I know it's still a draft, but I already went through the code and reviewed it. Looks very good to me!

should we add a tooltip to the button when the workflow is inactive? I think the button is already pretty self-explanatory (at least when you investigate and click on the dropdown

I think we don't need a tooltip here

So I changed the dropdown trigger to "outline", but only when the other button is inactive. It's not 100% logical to have the dropdown button active in the second example, but that way it blends in naturally with the main button.

I'm not 100 % sure about the design yet. Mostly because the ButtonBar was not optimized for a primary button (In dark mode the primary button gets a border, which it never has, and it looks kind of weird) and the inactive button next to an active button somehow just looks broken :D  What do you think about solving it pragmatically with just two buttons (the icon one would need a tooltip, though).

@stefan-kracht thanks for the feedback, I'd actually forgotten to mark it as ready for review.
I've implemented the suggested change with the separate button. I agree it looks cleaner (the code feels cleaner too).
I've marked it as ready for review now.


Refactor typing system to fix &mut types

Mutably borrow types will not work with the current type system. This is because an eval() call will return a Repl with a type parameter of Data. If this type parameter is &mut then the reference lifetime will follow through, such that once given some data Data, rust thinks the lifetime is still valid for the Read return value (as it is captures Data as well).
I will have to move back to typing the reference type, NoRef, Brw, and BrwMut.

I believe I can use the current macro implementation. See the example below.
macro_rules! tst {
	(&mut $type:ty) => {{
		println!("a mutable reference type");
		stringify!($type)
		}};
	(&$type:ty) => {{
		println!("a reference type");
		stringify!($type)
		}};
	($type:ty) => {{
		println!("just a type");
		stringify!($type)
		}};
}

fn main() {
	dbg!(tst!(String));
	dbg!(tst!(&String));
	dbg!(tst!(&mut String));

	dbg!(tst!(&mut String));
	dbg!(tst!(&&String));
	dbg!(tst!(&mut &mut String));
}

Rust's macros can give me the information about reference type, by matching a pattern of &mut Type or & Type above just Type. The system doesn't hold up well with double references. Might have to test that later.

fixed on dev branch


Allow for leading '@' character in $resource paramDefaults

Not sure if this has been resolved after doing some searching of the issues so I decided to post it here.
This would be a feature to allow for a leading '@' character in a string when using the paramDefaults of the $resource factory. Currently, any string with a leading '@' character is interpreted as being an attribute of the data object and not as a string. This causes problems when trying to use it as part of GET (and presumably HEAD) requests.

I don't see how this can be a problem for GET/HEAD requests. Can you post an example?

Sure, here's quick example.
$resource('api/users', { filter : '@nts' })['get'];

In the example above, I want use a GET request to search for users whose names have '*@nts' in it. However, AngularJS seems to interpret that as the property 'nts' of the data I pass and not as filter variable whose value is '@*nts'.

I see. You are right, you can't (unless you pass the parameter on each call.
The only semi-decent way I can think of for solving this, is saying that we are going to strip a specific character if founf at the beginning of the param value (e.g. \). So, people will be able to send a literal @id, by doing {foo: '\\@id'}. The caveat is that if anyone wants to actually send a value starting with \, they need to prepend an extra \.
This would be a breaking change, but I don't expect it to affect many users.
Other ideas ?
(PRs are also welcome, btw :wink:)

I would simply suggest adding a property to the required options parameter of the $resource factory, called ignorePrefix maybe, which would allow you to bypass the @ prefix while also not causing any breaking changes.
I'm not very familiar with the AngularJS code base outside of documentation, but I could look into creating a PR for this.

That's an optiion too. But it is less flexible, since you can't have some params that use @ normally and some that use it as a literal value.

@Blackbaud-StacyCarlos, would you like to give it a shot and submit a PR.
Even the ignorePrefix approach is better than what we have now :smiley:

Sure, I will attempt it. I will also consider a more flexible design.


MyAccount scope validation is not implemented properly

Describe the issue:
The scope validation defined for the MyAccount in the deployment.toml as follows is not honored.
[myaccount.personal_info.scopes]
create =  ["internal_application_mgt_create"]
read = []
update = ["internal_application_mgt_update"]
delete = ["internal_application_mgt_delete"]

It's being written properly to the MyAccount deployment.config.json as follows.
...
"personalInfo": {
                "disabledFeatures": [
                    "profileInfo.mobileVerification"
                ],
                "enabled": true,
                "scopes": {
                    "read": [
                    ],
                    "update": [
                            "internal_application_mgt_update"
                    ],
                    "create": [
                            "internal_application_mgt_create"
                    ],
                    "delete": [
                            "internal_application_mgt_delete"
                    ]
                }
            },
...

As per the above configuration, only the users who're entitled to get the defined scope should be able to modify the user profile section. However, it's not honored and all the users can update their user profile.
Expected behavior:

If the above configuration is added, a new user without having any roles should not be able to update their user profile from MyAccount.
User should also be prevented from updating the profile picture.

Environment information

Product Version: IS 5.11.0

Related issues:
#11574

There should be an additional validation in this line. For reference, take a look at this implementation.


Code not easily searchable

Issue Description
The code was not easily identifiable, making it more difficult to maintain or identify areas for modification.
E.g. https://github.com/chvancooten/NimPlant/blob/ff66479f26995da58998ede5edfdc5e7337fc5ef/server/util/listener.py#L27
For some reason the Server header is encoded in hex. If it was in just plain text we could grep for the string and change it.

Improvement
Put the cleartext server header in the code instead of the hex representation because it's running on the server anyways.
Also, what was the reason to use base16 on it? It's unlikely anyone would run this on the target system with Python installed, so obfuscation isn't really necessary.

Hi Vincent, that Server header was encoded like that on purpose, exactly so that people can't just grep for it to change it 😉. Motivation being that people should actually go through the code at least a bit and make appropriate modifications before deploying.
Closing this as a won't-fix issue. Feel free to open a new issue or PR if you have any other suggestions!

Got it!


Remove February 22 plain language training

Introduction to plain language for the public sector lists all upcoming training dates. The February 22 date has passed and needs to be removed. @YeseniaGtz approved doing this update outside the release cadence.

Page updated. Workflow run: https://github.com/cagov/hub.innovation.ca.gov/actions/runs/8072602753


[ADP-2564] Improve documentation for DB

This pull request improves a couple of comments in the DB code.
Issue number
ADP-2564

bors merge

bors merge


[bug]: ente.dev mirrors are timing out

Presently, the ente.dev mirrors are down, and seem to have been so for a couple days. Guessing Cloudflare config changes might be to blame?

Heya, firstly, sorry for the downtime!
I've been aware of the issue, but the last few weeks have unfortunately been very stressful for me.
I, as well as many others as I recently learned, have been having issues with NginxProxyManager and both of my reverse proxies were running it.
Due to that, both were affected by the same bug and went down, hooray!
Now the reverse proxies are diversified, and all server VMs are running in a High-Availability Proxmox Cluster with Ceph.
Also as a last resort I'll be setting up a co-location as fallback in the next few days just in case anything happens.
Will keep you updated in #10 ^-^
Last, but not least, I'm sorry for the silence, that won't happen again.


Add Kubernetes multi-cluster support

Added Kubernetes multi-cluster support.
Make fraction digits configurable
Add additional query parameters
Make the base URL configurable to be shown in the Kubecost plugin

@phac008 I would like to contribute with these changes to this project.


Enhancements for Interop.

Reverse channel mask bit string in THCI.
Processing channel mask bits from left-side.
Host swap Ticks field of Timestamp in big-endian order.
Reset frame counter for key Id mode 2 method after each successful processing.

This PR help pass the interop test cases with NXP (including 9.2.12, 9.2.14, 9.2.17, bidirection). @jwhui Please have a check first. And thanks much for @chshu 's suggestion and help to locate the issues.

Current coverage is 58.73% (diff: 66.66%)

Merging #1189 into master will decrease coverage by 13.07%

@@             master      #1189   diff @@
==========================================
  Files           128         72     -56
  Lines         18384      11537   -6847
  Methods        2578       1674    -904
  Messages          0          0
  Branches       2221       1456    -765
==========================================
- Hits          13202       6776   -6426
+ Misses         4356       4252    -104
+ Partials        826        509    -317

Powered by Codecov. Last update 50ba50e...6c70ed3


Open bug appears in "Shipped" section

See https://fugu-tracker.web.app/#:~:text=Introduce api for standardized database access, which appears in the "Shipped" section, but its bug https://crbug.com/1250207 is not fixed.

The logic is probably that the bug has label "M-95" which is "in the past".
Updating the heuristic to do something sensible when there's a mismatch (but still open but date has passed) would be good.
I'll update the bug to drop that milestone, so it'll probably disappear from the dashboard.

Fixed for now.


Migrate documentation of special cases to use math directives

The documentation of special cases in API documentation predates the specification's embrace of reST and GitHub support for mathematical equations in Markdown. As such, special cases use code blocks for numerical values and mathematical symbols. We should migrate to using math directives for better and more succinct rendering.
Adoption of math directives needs to be coordinated with the array API test suite, which, TMK, relies on special cases being described in a particular format within narrative content. Migration to math directives would thus break the test suite's current parsing logic for extracting special values and the associated expected result.
During this migration, we may want to consider providing structured data (e.g., as JSON) describing special cases which can be more readily consumed by downstream consumers, such as the array API test suite, and prevent implicit dependencies on how narrative content is written.

Structured data would be great (c.f. #49).


Add custom-codecs integration tests into test manifiest

Description
Add custom-codecs integration tests into test manifiest
Issues Resolved
Part of https://github.com/opensearch-project/opensearch-build/issues/3971
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@gaiksaya @peterzhuamazon fyi folks :)


Validation of alpha values

Does this work for alpha values? It's failing for me.

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

ID: 84480f6c-693c-f9dc-f518-40327bee20f0
Version Independent ID: 3544a89a-79ef-2467-d787-9ed717faeeb1
Content: Validate expected values
Content Source: articles/fin-ops-core/dev-itpro/perf-test/rsat/rsat-validate-expected.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @robadawy
Microsoft Alias: robadawy

The operator '>' is not recoginized for comparison operations
( That's how it's spelled in the error details.)

@kristyler, thanks for posting here.
@robadawy, please review and update the content, as necessary.

Bug 408194 has been logged to track this issue.


Support request: How do I change the install version of ruby?

I'm trying to change Ruby version form 1.9.3p484 to 2.x. How do I do that?
I see a node config version option nodejs_version:, but I don't see a way to change Ruby version.
Thanks!

There's a ruby_version variable within the upstream role.
https://github.com/geerlingguy/ansible-role-ruby/blob/master/defaults/main.yml#L14
Adding that to your config.yml file, adjusting the value and re-running vagrant provision should work.

Exactly as @opdavies said; though you also need to make sure to set ruby_install_from_source to true and make sure the ruby_download_url downloads the right version too; see https://github.com/geerlingguy/ansible-role-ruby
You will need to run vagrant provision after configuring that.

Thanks guys! We figured out another way, but this way is much easier. We are at the Drupal Toronto Camp and we were running a BOF on testing speed on Sass preprocessing within the VM so when we share the DrupalVM files, all developers would have everything installed within the VM.
Compile time was a bit slow comparing to compiling within the host machine. I'll keep testing and see how we can improve that.
Thanks!


Finalized state from debug/state API is incorrect on epochs with empty slots in the end

Description
We return finalizedAnchor in debug/state API, though if this state is associated with block which is not the last in finalized epoch, finalized state should be transitioned through empty slots to the end of the epoch. It sounds logical for this kind of id and state API endpoint and is default behavior of the other clients.

Internal discussion: https://consensyssoftware.atlassian.net/wiki/spaces/PEG/pages/399517614166/Starting+from+transitioned+AnchorPoint+discussion

I have tried to replicate this with Kurtosis and we're reporting the same the same state as lighthouse.
Managed to get an empty slot on the last slot of the epoch.

Logs from Lighthouse:
2024-10-21 14:41:14 Oct 21 04:41:14.000 INFO Synced                                  slot: 351, block:    …  empty, epoch: 10, finalized_epoch: 8, finalized_root: 0xdcca…9ac0, exec_hash: 0xa4dd…3578 (verified), peers: 1, service: slot_notifier
2024-10-21 14:41:14 Oct 21 04:41:14.000 INFO Ready for Electra                       info: ensure the execution endpoint is updated to the latest Electra/Prague release, service: slot_notifier
2024-10-21 14:41:20 Oct 21 04:41:20.001 INFO Prepared beacon proposer                parent_root: 0x511ff680ea5cf3d0fd292adc146c7b834cd231d0858f1c0adc3713b0b946f489, validator: 42, prepare_slot: 353, service: beacon
2024-10-21 14:41:20 Oct 21 04:41:20.003 ERRO No valid eth1_data votes, `votes_to_consider` empty, outcome: casting `state.eth1_data` as eth1 vote, genesis_time:<PHONE_NUMBER>, earliest_block_timestamp:<PHONE_NUMBER>, lowest_block_number: 0, service: deposit_contract_rpc
2024-10-21 14:41:20 Oct 21 04:41:20.016 INFO Signed block published to network via HTTP API, publish_delay_ms: 0, slot: 352
2024-10-21 14:41:20 Oct 21 04:41:20.025 INFO Valid block from HTTP API               slot: 352, proposer_index: 43, root: 0x8d9b…bacf, block_delay: 15.60722ms
2024-10-21 14:41:20 Oct 21 04:41:20.030 INFO Prepared beacon proposer                parent_root: 0x8d9bddf9f5cb3104f2e6004b809b416827b281be3814d7814bc5d5a76cfdbacf, validator: 42, prepare_slot: 353, service: beacon
2024-10-21 14:41:26 Oct 21 04:41:26.000 WARN Low peer count                          peer_count: 1, service: slot_notifier
2024-10-21 14:41:26 Oct 21 04:41:26.000 INFO Synced                                  slot: 352, block: 0x8d9b…bacf, epoch: 11, finalized_epoch: 9, finalized_root: 0x6a16…a0e9, exec_hash: 0xa379…3993 (verified), peers: 1, service: slot_notifier

Logs from Teku:
2024-10-21 14:41:12 2024-10-21 04:41:12.001 INFO  - Slot Event  *** Slot: 351, Block:                                                        ... empty, Justified: 9, Finalized: 8, Peers: 1
2024-10-21 14:41:12 2024-10-21 04:41:12.014 INFO  - Validator   *** Published sync_signature     Count: 32, Slot: 351, Root: 60a0ab7bade704755f58c5f9c79c9a6649fb70cab168bd9a50c8d15db05cf5f0
2024-10-21 14:41:12 2024-10-21 04:41:12.018 INFO  - Validator   *** Published attestation        Count: 1, Slot: 351, Root: 60a0ab7bade704755f58c5f9c79c9a6649fb70cab168bd9a50c8d15db05cf5f0
2024-10-21 14:41:15 2024-10-21 04:41:15.153 INFO  - Retrying execution of block 511ff680ea5cf3d0fd292adc146c7b834cd231d0858f1c0adc3713b0b946f489 (350)
2024-10-21 14:41:15 2024-10-21 04:41:15.192 INFO  - Execution Client is responding to requests again after a previous failure
2024-10-21 14:41:16 2024-10-21 04:41:16.035 INFO  - Validator   *** Published aggregate          Count: 1, Slot: 351, Root: 60a0ab7bade704755f58c5f9c79c9a6649fb70cab168bd9a50c8d15db05cf5f0
2024-10-21 14:41:16 2024-10-21 04:41:16.059 INFO  - Validator   *** Published sync_contribution  Count: 18, Slot: 351, Root: 60a0ab7bade704755f58c5f9c79c9a6649fb70cab168bd9a50c8d15db05cf5f0
2024-10-21 14:41:20 2024-10-21 04:41:20.005 INFO  - Epoch Event *** Epoch: 11, Justified checkpoint: 10, Finalized checkpoint: 9, Finalized root: 6a166860d99cf7a8b623e713bf1f06848011e41adace5cdf05cb296334bda0e9
2024-10-21 14:41:20 2024-10-21 04:41:20.006 INFO  - Block performance: epoch 10, expected 16, produced 15, included 15 (100%)
2024-10-21 14:41:20 2024-10-21 04:41:20.006 INFO  - Sync committee performance: epoch 10, expected 8192, produced 8192, correct 7936, included 7936 (97%)
2024-10-21 14:41:20 2024-10-21 04:41:20.039 INFO  - Attestation performance: epoch 9, expected 32, produced 32, included 32 (100%), distance 1 / 1.00 / 1, correct target 32 (100%), correct head 32 (100%)
2024-10-21 14:41:20 2024-10-21 04:41:20.042 WARN  - Failed to publish attestation(s) for slot 352 because no peers were available on the required gossip topic
2024-10-21 14:41:20 2024-10-21 04:41:20.042 INFO  - Validator   *** Published attestation        Count: 2, Slot: 352, Root: 8d9bddf9f5cb3104f2e6004b809b416827b281be3814d7814bc5d5a76cfdbacf
2024-10-21 14:41:20 2024-10-21 04:41:20.043 INFO  - Validator   *** Published sync_signature     Count: 32, Slot: 352, Root: 8d9bddf9f5cb3104f2e6004b809b416827b281be3814d7814bc5d5a76cfdbacf
2024-10-21 14:41:24 2024-10-21 04:41:24.001 INFO  - Slot Event  *** Slot: 352, Block: 8d9bddf9f5cb3104f2e6004b809b416827b281be3814d7814bc5d5a76cfdbacf, Justified: 10, Finalized: 9, Peers: 1

When calling the endpoint /eth/v2/debug/beacon/states/finalized I get this from Lighthouse and this from Teku, which present no difference.


Fixed width sidenav

Select one ...  (check one with "x")
[ ] bug
[ ] feature request
[ x ] enhancement

Expected behavior
Side nav menu should at least have option not to scale horizontally (fixed width). Right now, there is word warp occurring on nav elements with long text. Seems like it would be better design to allow fixed width menus.
Actual behavior
https://vmware.github.io/clarity/documentation
Reproduction of behavior
https://vmware.github.io/clarity/documentation
Environment details

Angular version: 2.0.X

Clarity version:

OS and version:

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

This issue hasn't been updated in a while. If you have more details that clarify the questions please re-open and add in the details that clarify the changes needed here.


Add touchstart handler for mobile browsers

Added touch events to allow for use on mobile devices or touch enabled laptops.

Thanks!


Update OWNERS_ALIASES for oussemos

/assign lledru

/assign @rekcah78

/approve

/approve

/lgtm

/assign @zacharysarah
/lgtm

/lgtm

/assign @zacharysarah

@sieben It looks like @oussemos needs to join the Kubernetes org before this PR can merge.

Hello @zacharysarah, I created an issue https://github.com/kubernetes/org/issues/508 to join the org.

I've already joined the org, a kind reminder for this PR :)

/lgtm
/approve

/lgtm

/approve

/lgtm


Update contributor's guide (PR reviewer's guide?) for Asaad to review and approve any PR with CSS changes

Per Feb 14, 2017 platform discussion.

PR is here

PR (#1052) merged


Wipe login data

This is the PR as per issue #34
It will clear login info from local storage for all logged in accounts after the user enters a confirmation sentence.
cc @HPaulson

anything else needed in this @maebeam @lazynina
bunch of people got hacked yesterday due to using extensions and having old accounts logged in.
not being able to clear local storage easily makes this worse when it happens.

@tijno I'd like to make this a separate component e.g. /logout
Which extensions were compromised?

ok will make it separate component.
not sure which ones - @HPaulson looked into that side of the hacked accounts. I could see about 20 likely affected.

thank you!

Has anyone provided any proof or identified specific extensions? Seemed like some opportunist FUD to me.
"Someone sent all my CLOUT to an anon address." Please donate. 😂

Has anyone provided any proof or identified specific extensions? Seemed like some opportunist FUD to me.
"Someone sent all my CLOUT to an anon address." Please donate. 😂

I had so much loosing money then asking people in discord to help. Its laugh for you because you are not a from third world country.  And mentioning as I asking for something that wasn't mine.

@tijno if you have some time I'd love to get this merged

ill do my best this weekend.

I'd like to make this a separate component e.g. /logout

time to learn some angular.

I might have time to split this out into a separate component this afternoon. I'll post here before I do just in case you get to it first @tijno

earliest i will get to it is sunday

@tijno ok I'm starting it today 🙂 I'll see how far I can get.
Couple clarifying questions –

The work left is just a matter of splitting the 'clear' logic into a separate component (e.g. clear-account), right?
Are we thinking this is a separate route as well or just part of log-in?

@akutch
yes separate component
and i think separate route too as "signup" for example from memory is a separate route too. So keep consistent with that.

The changes are ready for review here: https://github.com/bitclout/identity/pull/51

included in PR mentioned above by @akutch so closing this one.


Support DMARC and DKIM

Thanks for the docker image.
Would like to know if it is possible to add support for DMARC and DKIM into docker image?
Currently, the email I reply to anonymously most likely will go to spam folder at the first time, till the receiver while-list the email address.
I manually add DKIM and DMARC to the image, but the DKIM always not been signed when I reply.
Or if there is a way that I can add this from the image?
Thanks.

@M96268004 Now available in latest image

@M96268004 Now available in latest image


Failed to execute: azds connect: Connect operation failed: Value cannot be null

Describe the bug
Trying out connecting my dev box to our AKS cluster from VS Code as described here but I keep getting this error:
Connect operation failed: Value cannot be null.
Parameter name: source

I have never enabled Dev Spaces for this repo or this cluster before. Very first time. I assumed this would work for any repo and any K8s cluster as long as prerequisites are met?
Logs reveal this:
Logging handled exception: System.ArgumentNullException: {"ClassName":"System.ArgumentNullException","Message":"Value cannot be null.","Data":null,"InnerException":null,"HelpURL":null,"StackTraceString":"   at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source)\r\n   at Microsoft.Azure.DevSpaces.Client.LocalConnect.LocalConnectService.CollectServicesToRoute(List`1 serviceList, String namespaceName, IEnumerable`1 services) in E:\\A\\_work\\755\\s\\src\\client\\LocalConnect\\LocalConnectService.cs:line 740\r\n   at Microsoft.Azure.DevSpaces.Client.LocalConnect.LocalConnectService.GatherContainerWorkloadInfo(IKubernetes kClient, IProgress`1 progress, String serviceResolutionSpace, CancellationToken cancellationToken) in E:\\A\\_work\\755\\s\\src\\client\\LocalConnect\\LocalConnectService.cs:line 658\r\n   at Microsoft.Azure.DevSpaces.Client.LocalConnect.LocalConnectService.StartRemoteAgentAsync(String containerIdentifier, String targetSpace, ContainerIdentifierOption containerIdOption, IProgress`1 progress, CancellationToken cancellationToken) in E:\\A\\_work\\755\\s\\src\\client\\LocalConnect\\LocalConnectService.cs:line 183\r\n   at Microsoft.Azure.DevSpaces.Cli.Commands.Service.ServiceConnectCommand.ExecuteInnerAsync(ContainerIdentifierOption containerIdOption, IDevSpacesControllerConnectionDetails connectionDetails, Action`1 workloadStartedHandler, CancellationToken cancellationToken) in E:\\A\\_work\\755\\s\\src\\cli\\Commands\\Service\\ServiceConnectCommand.cs:line 406\r\n   at Microsoft.Azure.DevSpaces.Cli.Commands.Service.ServiceConnectCommand.ExecuteInnerAsync(ContainerIdentifierOption containerIdOption, IDevSpacesControllerConnectionDetails connectionDetails, Action`1 workloadStartedHandler, CancellationToken cancellationToken) in E:\\A\\_work\\755\\s\\src\\cli\\Commands\\Service\\ServiceConnectCommand.cs:line 472\r\n   at Microsoft.Azure.DevSpaces.Cli.Commands.Service.ServiceConnectCommand.ExecuteAsync() in E:\\A\\_work\\755\\s\\src\\cli\\Commands\\Service\\ServiceConnectCommand.cs:line 347\r\n   at Microsoft.Azure.DevSpaces.Cli.DevSpacesCliApp.RunCommandAsync(String[] args, CancellationToken cancellationToken) in E:\\A\\_work\\755\\s\\src\\cli\\DevSpacesCliApp.cs:line 179\r\n   at Microsoft.Azure.DevSpaces.Cli.DevSpacesCliApp.ExecuteAsync(String[] args, CancellationToken cancellationToken) in E:\\A\\_work\\755\\s\\src\\cli\\DevSpacesCliApp.cs:line 138","RemoteStackTraceString":null,"RemoteStackIndex":0,"ExceptionMethod":null,"HResult":-2147467261,"Source":"System.Linq","WatsonBuckets":null,"ParamName":"source"}

To Reproduce

Install all prerequisites and open our my on VS Code
From the command palette choose Azure Dev Spaces: Redirect an existing Kubernetes service to my machine [Preview]
Select my service from the list
Select Replace: Redirect an existing Kubernetes service to my machine [Preview]
Enter port 3000
Extension states "AZDS Connect: Connecting to sessions/sessions-dpl-59bb566689-5qnkl..."
The extension presents the following output on VS Code:

Connecting to target-controller ...

Deployment sessions/sessions-dpl patched to run azds agent.

Found container sessions-dpl-59bb566689-kbzv7/sessions-ctr.

Connecting to sessions/sessions-dpl-59bb566689-kbzv7...

Connect operation failed: Value cannot be null.
Parameter name: source

Stop workload and clean up.

Restore: Deployment 'sessions-dpl' restored to original state.

Oops... An unexpected error has occurred. A report of the error will be sent to Microsoft.
For diagnostic information, see Azure Dev Spaces logs at 'C:\Users\julioct\AppData\Local\Temp\Azure Dev Spaces'.

Failed to execute: azds connect --container sessions/sessions-dpl-74695fd7c4-2sc5t/sessions-ctr --script C:\Users\julioct\AppData\Local\Temp\tmp-37524fPNnLGI4LbKU.env.cmd --env C:\Users\julioct\AppData\Local\Temp\tmp-37524fPNnLGI4LbKU.env --ppid 37524 --local-port 3000 --control-port 53219. Error: Connect operation failed: Value cannot be null.
Parameter name: source
Stop workload and clean up.
Oops... An unexpected error has occurred. A report of the error will be sent to Microsoft.
For diagnostic information, see Azure Dev Spaces logs at 'C:\Users\julioct\AppData\Local\Temp\Azure Dev Spaces'.
. For more information please visit https://aka.ms/azds-connect."

Expected behavior
Some sort of connection success?
Logs
Attach logs from the following directory:
For Windows: %TEMP%/Azure Dev Spaces
For OSX/Linux: $TMPDIR/Azure Dev Spaces
azds-cli-2020-02-24-22-52-37-37016.txt
azds-sdk-2020-02-24-22-52-38-37016.txt
Environment Details
Client used: VS Code
CLI:
Azure Dev Spaces CLI
1.0.20200218.4
API v3.2
VS Code: code --list-extensions --show-versions | find "azuredevspaces.azds"
<EMAIL_ADDRESS>Client's version: VS Code 1.42.1
Operating System: Windows 10 1909 (OS Build 18363.657)
Additional context
Add any other outputs from the clients or context you would like to share.

Hi @julioct, thanks so much for reporting this! I'm logging a bug for the team to investigate.  We'll follow back up on this thread once the issue has been identified.

We will be roliing out a fix for this next week. Closing this thread.

The fix is now available in the latest version of the Dev Spaces CLI.


Mapping capture groups usable in the tag

Is your feature request related to a problem? Please describe.
Capture variables defined in the mapping regular exrpressions, should be usable for the tag.
The tag should be configurable for multiple variables, a suffix, a prefix and a concatenator.
Describe the solution you'd like
The tag definitions should be:
    tag:
      captures:
         - quality
      prefix: ' ['
      suffix: ']'
      concat: '|'

concat is only If you have multiple capture variables.
captures  should be a list of variables names used in the regular expressions for mapping.
Example:
^\s*(FR)?[: |]?TF1!delimiter!!quality!\s*$

@kumy: please check the new functionality. i have pushed the changes.,
this is an example mappings.yaml file:
Please consider the change of templates.key attribute to templates.name
mappings:
  - id: France
    tag:
      captures:
         - quality
      prefix: ' ['
      suffix: ']'
    match_as_ascii: true
    templates:
      - name: delimiter
        value: '[\s_-]*'
      - name: quality
        value: '(?i)(?P<quality>HD|LQ|4K|UHD)?'
    mapper:
      - tvg_name: TF1
        tvg_names:
          - '^\s*(FR)?[: |]?TF1!delimiter!!quality!\s*$'
        tvg_id: TF1.fr
        tvg_chno: "1"
        tvg_logo: https://emojipedia-us.s3.amazonaws.com/source/skype/289/shrimp_1f990.png
        group_title:
          - FR
          - TNT
      - tvg_name: TF1 Séries Films
        tvg_names:
          - '^.*TF1!delimiter!Series?!delimiter!Films?(!delimiter!!quality!)\s*$'
        tvg_id: TF1SeriesFilms.fr
        tvg_chno: "20"
        tvg_logo: https://emojipedia-us.s3.dualstack.us-west-1.amazonaws.com/thumbs/120/google/350/shrimp_1f990.png
        group_title:
          - FR
          - TNT

Sorry, I had an accident nothing really grave in the end... I ll be available in a few days to test the new code ;) Thanks for your work on that project, see U later

I wish you get well soon.

Hi @euzu, I'm back at home since some days now. I have difficulties to concentrate for long period, it took me ages to create the file in PR #6.
Thanks for your work on this issue, I've used it and it seems to work fine.
I'll create individual issues from https://github.com/euzu/m3u-filter/issues/3#issuecomment-1382123985 as well as I can, depending on my exhaustion.

I hope you will recover quickly, don't stress yourself and just take everything slowly for the beginning.


run php artisan koel:init, i got this<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=8.9.0". Got "6.17.1"

Describe the bug
when i run php artisan koel:init, i got this<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=8.9.0". Got "6.17.1"
Environment

Koel version [ v4.2.1]
Node version [ v6.17.1]
npm version [3.10.10]
yarn version [1.19.2]

yarn install --ignore-engines, with --ignore-engines, yarn will not checkout your node engine.  so you can add this param at app/Console/Commands/InitCommand.php file, then you serch " yarn install", then you find two match,  now you just add  --ignore-engines to it and save, then run php artisan koel:init again, this time the error was gone. it work for me

Ignoring engines is hardly a good idea. It's better to use a more recent Node version (6.x is too old I'm surprised it worked for you).


Difference in DNS caching between execute() and enqueu() methods

Good bug reports include a failing test! Writing a test helps you to isolate and describe the problem, and it helps us to fix it fast. Bug reports without a failing test or reproduction steps are likely to be closed.
Here’s an example test to get you started.
https://gist.github.com/swankjesse/981fcae102f513eb13ed
We invoke downstream application using host name  which is resolved to an Load Balancer and it is mapped to different IP addresses.
When we invoke Synchronous request using execute() method, then okhttp client is able to identifiy the new active ip address which is attached to the load balancer and gets the response back.
But when we invoke Asynchronous request using enqueue() method, then okhttp client is taking the IP address from the cache and goes to the ip address which is not currently attached to load balancer.
Is there dns caching done in enqueue() which is not done in execute() method and if so, how to resolve the dns caching that is being done in enqueu() method as we need to resolve the DNS for the host and go against the active IP which is attached to the load balancer and not to the inactive ip which would be available in the cache.

The enqueue and execute both treat Dns the same way.  There can be some differences between connection reuse if you execute them at the same time, so there can be other reasons.
We can't really offer 1:1 support for issues like this.  I suggest making a reproducible example and posting to stackoverflow.
Or reopen with a bug reproduction.


Problems with the generated K8S CustomResourceDefinition

The k8s definitions that are built by cdk8s, botht he default and custom (e.g. cdk8s import<EMAIL_ADDRESS>-l typescript)
Do not seem to generate the full, or even correct, definitions of CustomResourceDefinition
The docs specify that CustomResourceDefinition.spec.additionalPrinterColumns should be a type of CustomResourceColumnDefinition, which includes a field named JSONPath
However, the generated imports/k8s.ts tells me it should be jsonPath; This is incorrect capitalization because it shows up in the synth as jsonPath instead of JSONPath.
I am trying to port over this code to cdk8s: https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/docs/install/v2_0_0_full.yaml#L12
From imports/k8s.ts:

Additionally, the CustomResourceDefinition resource should have a field named "status" that is of type CustomResourceDefinitionStatus - however, in the import/k8s.ts, their is no support for the status field and my importing of a CRD from the same project (aws-load-balancer-controller) will fail due to the specification of the status field.
This is the status field I would like in my CRD: https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/docs/install/v2_0_0_full.yaml#L182 but the cdk8s import of the k8s library (apparenlty regardless of version, i've tried a few), the CustomResourceDefinitionOptions interface only includes metadata and spec, and is missing status.
Environment:
cdk8s 0.33.0
ubuntu 20.04

Keep


The setting of "Notify Malicious" is disabled by default on GPO and Intune, but this setting is enabled by Windows 11 default.

Could you add a note about the setting of "Notify Malicious" is enabled by Windows 11 default?
This page said the setting of "Notify Malicious" is disabled by default on GPO and Intune.
If you disable or don't configure this policy setting, Enhanced Phishing Protection doesn't warn users if they type their work or school password into one of the malicious scenarios described above.
However I know this setting is enabled by "Windows 11 default".
That is announced below official page.
Source: https://support.microsoft.com/en-us/topic/protect-your-microsoft-password-from-being-phished-e4e8e611-e4b3-4be9-914c-db1657c337cf
Once the app is open, scroll down to Phishing protection and select the settings you want. By default, you are only protected against entering your password into malicious content.
Best regards.

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

ID: d860e9d3-0ead-86d4-c3b9-138cbd37ee62
Version Independent ID: d860e9d3-0ead-86d4-c3b9-138cbd37ee62
Content: Enhanced Phishing Protection in Microsoft Defender SmartScreen - Windows Security
Content Source: windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/enhanced-phishing-protection.md
Product: windows-client
Technology: itpro-security
GitHub Login: @vinaypamnani-msft
Microsoft Alias: vinpa

Hey @kash1064, "Notify malicious" is off by default for Commercial customers, but for consumers it is indeed on by default. I'll add a note to this document to clarify this further.


Liquid is placable in claims

https://www.youtube.com/watch?v=KLxuhlUbiaU
It seems that when the block isn't highlighted, you are able to place buckets in claims.
Not really easy to explain it, so here is a video.
The liquid is able to be placed in claims.
This has been used to grief several claims on my server, and is quite easy to do.
I consider this a "critical bug".

@inklit Is this resolved with latest build?

See issue #78

I'm not having this issue on GP B10 and SF1509, however, the 'no permission to place water' message is a bit off.. http://prnt.sc/bmfiwm

@SnowBlitzz should be fixed in B10.

You mean B11? since I was on B10 with that screenshot.


Add tutorial showing DD strategies

What is happening?
Show all Superstaq DD strategies.
What are the current alternatives?
No response
Any additional context?
No response

Closing. Adding this task to #761.


Rename Spark master actor resource config and apply to both actors

PR https://github.com/oap-project/raydp/pull/287 only set spark master resource to spark master actor. There is another actor which comprised the driver infra RayAppMaster doesn't has the config. It is possible that actor scheduled on worker node and get killed with the worker, causing Spark job stuck with following error:
23/03/02 01:55:38 ERROR TransportClient: Failed to send RPC RPC<PHONE_NUMBER>779296894 to /<IP_ADDRESS>:45851: io.netty.channel.StacklessClosedChannelException
io.netty.channel.StacklessClosedChannelException
	at io.netty.channel.AbstractChannel$AbstractUnsafe.write(Object, ChannelPromise)(Unknown Source)
23/03/02 01:55:38 WARN ExecutorAllocationManager: Unable to reach the cluster manager to request more executors!

This PR does the following changes:

Renames config spark.ray.raydp_spark_master.resource.* to spark.ray.raydp_spark_master.actor.resource.* to make it a bit less confusing as we have two actors.
Set the custom resources to both driver actors.
Fix a bug in the raydp jar package in setup.py
Fix a bug in startUpAppMaster where sparkProps might be a python dict containing Dict[str, Any]

LGTM


python3Packages.crytic-compile: 0.1.9 -> 0.1.12

Motivation for this change
Update to latest upstream release 0.1.12.
Change log: https://github.com/crytic/crytic-compile/releases/tag/0.1.12
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 108851 1

6 packages built:

python37Packages.crytic-compile
python37Packages.slither-analyzer
python38Packages.crytic-compile
slither-analyzer (python38Packages.slither-analyzer)
python39Packages.crytic-compile
python39Packages.slither-analyzer

Result of nixpkgs-review pr 108851 1

6 packages built:

python37Packages.crytic-compile
python37Packages.slither-analyzer
python38Packages.crytic-compile
slither-analyzer (python38Packages.slither-analyzer)
python39Packages.crytic-compile
python39Packages.slither-analyzer

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108851 run on x86_64-darwin 1

4 packages failed to build and are new build failures:

python37Packages.slither-analyzer: log was empty
slither-analyzer: log was empty
(python38Packages.slither-analyzer): log was empty
python39Packages.slither-analyzer: log was empty

3 packages built:

python37Packages.crytic-compile
python38Packages.crytic-compile
python39Packages.crytic-compile

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108851 run on x86_64-darwin 1

4 packages failed to build and are new build failures:

python37Packages.slither-analyzer: log was empty
slither-analyzer: log was empty
(python38Packages.slither-analyzer): log was empty
python39Packages.slither-analyzer: log was empty

3 packages built:

python37Packages.crytic-compile
python38Packages.crytic-compile
python39Packages.crytic-compile

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108851 run on x86_64-linux 1

4 packages failed to build and are new build failures:

python37Packages.slither-analyzer: log https://termbin.com/v6rw
slither-analyzer: log https://termbin.com/oihha
(python38Packages.slither-analyzer): log was empty
python39Packages.slither-analyzer: log https://termbin.com/od9s

3 packages built:

python37Packages.crytic-compile
python38Packages.crytic-compile
python39Packages.crytic-compile

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108851 run on x86_64-linux 1

4 packages failed to build and are new build failures:

python37Packages.slither-analyzer: log https://termbin.com/v6rw
slither-analyzer: log https://termbin.com/oihha
(python38Packages.slither-analyzer): log was empty
python39Packages.slither-analyzer: log https://termbin.com/od9s

3 packages built:

python37Packages.crytic-compile
python38Packages.crytic-compile
python39Packages.crytic-compile


sidr with same page anchors

Hi all,
Awesome plugin. I'm using it to navigate to different anchors on the same page. But when you click to go, the menu stays open. Is there an easy way to make it close on-click?

Thanks @geage


New command to get the used config for a scenario

New command Get-BicepNetConfig, closes #34
Dependency script change to allow for preview versions of .NET
Version bump

See if Get-BicepNetConfig matches the expectations. It needs a path, and returns an object with two properties:

Path - The path to the .bicep file to use for finding the config to use, or "Default" if no bicepconfig.json was found.
Config - The contents of the configuration. Not sure if we want to expose this for the user (Bicep CLI specifically has a comment in their version of the file regarding this), and if we do we should maybe consider returning the "fully merged" configuration if the user has only provided a partial config file (such as only specified the module registry parts).

and if we do we should maybe consider returning the "fully merged" configuration if the user has only provided a partial config file (such as only specified the module registry parts).

I like the idea of returning the fully merged config. It makes sense to show the current config.

Works great!  At least I would like to have the option to get the default config in a simple way.

Have a look at the changes now! I added a -Default switch, which is not mandatory (so you can run just Get-BicepNetConfig on its own), and the output is now merged with the default config, so you always see the full configuration of your command.

After offline discussions:

Add -Scope parameter with local, default and merged  as allowed values

The -Default parameter is now replaced by -Scope which allows three different values.

Default - Gets the built-in configuration.
Merged - Combines any found configuration file with the built-in configuration.
Local - Gets only the configuration from a found configuration file.

Running only Get-BicepNetConfig will set the scope to Default. Running Get-BicepNetConfig with the -Path parameter will set the scope to Merged.


camera orbit

would be nice to implement the same camera orbit system that can be found in blender called Auto depth, just checks what is under mouse cursor and uses that as a point of reference to rotate around, would make camera orbit much nicer to use when inspecting meshes

Duplicate of #17517, which has more information about the feature.


Move picker into left bottom corner return hexvalue #-1-1-1

Try to open the picker and try to select black color #000000
Color Code will be #-1-1-1

Awesome, looking forward to it.
On Wed, 7 Nov 2018 at 11:22, Simon<EMAIL_ADDRESS>wrote:

Hm, seems like a rounding arrow... I should take TDD into consideration 😅
I'll fix it later today!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Simonwep/pickr/issues/46#issuecomment-436576320, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAjeIUzsObvONXlF9TG53lzv-ctg3He-ks5usrRTgaJpZM4YSFGJ
.

--
Nils Drescher

Dipl.-Ing. Nils Drescher
(Geschäftsführer)
Mobil: 0177 / 961 47 58
Tel.: 0521 / 44 81 44 10
Web: www.qrcode-generator.de
E-mail<EMAIL_ADDRESS>Networks: XING, Facebook
Egoditor UG (haftungsbeschränkt)
Am Lenkwerk 13
33609 Bielefeld
Amtsgericht Bielefeld - HRB 39655
Geschäftsführung: Nils Drescher, Nils Engelking

Fixed in a529283e3f5f5735f4c23251fc1fa4de6a32af26 / try it out :)


Add support for setting up Git Credential Manager [PR possibility]

Context
In some cases I want to use the git credential manager, rather than the git URI rewrites that are currently done when using gitPrivateToken. For example, to work around any issues and edge cases, e.g. as described in #430.
Suggested solution
A new build parameter called gitPrivateUser (name suggestions welcome). When gitPrivateUser and gitPrivateToken are both provided, GameCI will set up the Git Credential Manager instead of git URI rewrites.
Considered alternatives
Initially I tried to resolve the underlying bug for this problem (an issue similar to #430), but sadly I don't have the experience and time to do as such. However, setting up the git credential manager was a quick addition that resolved the permission issues we were having, and are planning to use for our projects.
Originally I wanted to switch to pull in the packages via SSH, but my senior pushed back on this given the extra setup required for all developers on the team, which is why we'd prefer to use HTTPS.
Additional details
Link to discussion on the Discord server:  "Bad Credentials when resolving packages with git-lfs"
Existing implementation in our fork of Unity Builder: https://github.com/Psylaris/unity-builder/commit/5f814eb1823b297d9361c645e02fcfe04c23537b (I can make a PR if requested.)

@webbertakken Should we backport this into builder before v3?

This feature looks like something that we should support to me.
It doesn't look like a breaking change to me though. Unless I'm mistaken, we can also add it after the initial v3 release.
That said, if you feel this is something we can merge in somewhat quickly then I don't see why not.

@Auroriax Just took a look at your implementation and was wondering if you could explain what the git credential helper line is doing as I've never seen that format before: git config --global credential.helper '!f() { sleep 1; echo "username=$GIT_PRIVATE_USER"; echo "password=$GIT_PRIVATE_TOKEN"; }; f'
It would be good to have this for both Windows and Linux so I just need to know if it's cross-compatible.

If I remember correctly, I was looking for a way to set up the credential manager programatically and I stumbled upon this StackOverflow answer: https://stackoverflow.com/a/59890061 . Based on their explanation I don´t think it'll work on Windows (since essentially it's a shell script) but I don´t know for sure.
(I'm on a holiday at the moment and can help out more in ~2 weeks, if still needed!)

Thanks for the details! I think you're right about this not working on windows as we run using powershell so I don't think it's compatible. This probably won't make it in the initial v3 release then as I thought it would be a simple port but the windows side will likely be some work to convert and verify.

Hey, I've just stumbled upon this exact issue - what needs to be done to get it merged in to the current release? Happy to help if I can.  I followed along in the discord but it also seems to have hit a dead end.
For context, this is my error output:
An error occurred while resolving packages:
  Project has invalid dependencies:
    com.atteneder.gltfast: Cannot checkout repository [https://github.com/atteneder/glTFast.git]:
      Error when executing git command. WARNING: Multiple 'url.*..insteadof' keys with the same alias<EMAIL_ADDRESS>      Downloading Documentation~/Images/Unity-glTF-workflows.png (59 KB)
      Error downloading object: Documentation~/Images/Unity-glTF-workflows.png (aa50e39): Smudge error: Error downloading Documentation~/Images/Unity-glTF-workflows.png (aa50e3980f8e9a99e53b8347cdde7e293fe37ffb5e1469640379d802ef304541): batch response: Resource not accessible by personal access token
      WARNING: Multiple 'url.*..insteadof' keys with the same alias<EMAIL_ADDRESS>
      Errors logged to /github/workspace/Library/PackageCache/.tmp-289-9gHhnk9V2pJE/clone/.git/lfs/logs/20240517T003318.352323914.log
      Use `git lfs logs last` to view the log.
      error: external filter 'git-lfs filter-process' failed
      fatal: Documentation~/Images/Unity-glTF-workflows.png: smudge filter lfs failed


Remove autopep8 dependency?

Using autopep8 seems to be overkill for formatting the Django client template: https://github.com/jazzband/django-silk/blob/6b7e85a9326a05700e6ce147e944d73c1e599451/silk/code_generation/django_test_client.py#L9-L15
(autopep8 requires also pycodestyle)

Should be a dev dependency instead... it means any project that depends on django-silk right now also depends on autopep8... and I have a particular syntax checker I use that depends on a different version of autopep8 than django-silk.

I believe so

Oh my bad... autopep8 is used for production code.

Indeed autopep8 is used in silk.code_generation.django_test_client.gen which is used in silk.views.request_detail.RequestView.get so it looks like this issue can be closed.


Candid v0.10.1

I cannot bump Candid in Juno because ic-certification still requires v0.9.0.
Therefore openeing this issue. Would be nice if you could upgrade/release one of those day.

Thanks David. Support for candid ^0.10 has been released in v2.2.0: https://github.com/dfinity/response-verification/releases/tag/2.2.0.

Super, thanks. I'll bump Juno 😃.


refactor: convert NetworkingModuleTest to kotlin

Summary:
Migrated NetworkingModuleTest to kotlin (part of #38825)
Changelog:
[Android] [CHANGED] - NetworkingModuleTest.java -> NetworkingModuleTest.kt
Test Plan:
./gradlew :packages:react-native:ReactAndroid:test

I was unable to fix last 3 tests - testCancelSomeCallsInvalidate, testCancelAllCallsInvalidate, testMultipartPostRequestBody
@cortinico, @mdvacca I would greatly appreciate the reviews from you

@KrzysztofMoch Thanks for working on this one!
I see there are three test clauses that god disabled in the conversion process - those must be fixed before this can be merged.

@KrzysztofMoch Thanks for working on this one!
I see there are three test clauses that got disabled in the conversion process, however - those must be fixed before this can be merged.

Ah, I've just realized that the whole suite was ignored before conversion and none of the tests were executed.
Those test would fail before the conversion as well, so it's not your change's fault.

Yeah, I tried to fix them but wasn't able to. Can we left it as it is, or should I do something with it ?

No, it's alright, let's leave them like that for now, it's better be done as a follow up.
You've effectively enabled a bunch of tests running, not disabled, so kudos :)

Cool 🙌, let me know if you will need something


"riff delete --all" should not fail if topic is not found

If I delete a function where the topic test was already deleted using the "--all" option, I don't get an error and the function is not deleted. All I see is:
$ riff delete -n uppercase --all
Deleting topics.projectriff.io test:

This scenario can easily happen when I chain foo and bar with a shared topic and then delete both using the "--all" option.

I think another question we should ask ourselves first is "should it be possible to end up in this scenario", ie "should we allow deletion of topics that are bound to functions"?