[rom_ctrl,doc] Weaken description of what pwrmgr is expected to do

Sorry, @tjaychen! I assigned this to you, rather than adding you as a reviewer (whatever that means). Anyway, it now looks like I intended :-/

sounds good, i should push to this one also and add some language on the pwrmgr side.


Building a windows release with the hexpm/elixir docker image missing elixir.bat

If a mix release is compiled with a docker image such as hexpm/elixir:1.13.1-erlang-24.1.7-alpine-3.14.2 it seems to be missing the expected releases\<VERSION>\elixir.bat file.
In the mix release output I see this output: "skipping elixir.bat for windows (bin/elixir.bat not found in the Elixir installation)"
I suspect that the hexpm images may not have the windows-specific .bat files present (I think mix release is searching for it in "/usr/local/lib/elixir/bin"). Perhaps burrito should substitute it in?

Same result with the official Elixir image, which is also missing that file in the bin directory. ASDF-installed Elixir seems to be alright though, so I'm exploring that as a workaround.

Thanks Ben!
I think it's a reasonable thing to vendor out our own elixir.bat file based on how infrequently it changes. We already produce our own startup scripts anyways.

Please open up an issue (or send a PR) to https://github.com/hexpm/bob. We should include the windows files IMO, exactly for cross-compilation purposes. :)

This is fixed now that we launch directly from zig!


Add option to draw extra cells for paddingBottom/paddingRight

Right now paddingBottom and paddingRight doesn't draw anything in the "padded" region
https://user-images.githubusercontent.com/94077014/152489535-43094683-ced4-4ce5-b676-4d7d9249172e.mp4
but in my case I'd like the empty cell lines to still be drawn in these areas.
https://user-images.githubusercontent.com/94077014/152489554-a5bee1ec-d03a-4d85-aebb-e6a67c5fcf8b.mp4
Terminology-wise, I think the first case would make more sense as marginBottom and marginRight, and paddingBottom and paddingRight would include the drawn lines. Alternatively maybe there could be some other boolean (or booleans) to control if/which of these areas are drawn in.
https://github.com/glideapps/glide-data-grid/blob/0916a62916d0e5a1ee3e5ae091d0567b1e1a34d8/packages/core/src/scrolling-data-grid/infinite-scroller.tsx#L116-L121
-            width: el.clientWidth - paddingRight,
-            height: el.clientHeight - paddingBottom,
+            width: el.clientWidth,
+            height: el.clientHeight,

I too, like the idea!! Do you plan on or already have a PR open for the suggested addition?

I can make one, but it'd be good to settle on terminology/approach first

I went ahead and put up a proposal for this in #160
https://user-images.githubusercontent.com/94077014/152608583-6ab100f6-9a4a-4784-b3ba-800316b5f711.mp4

Thanks for the PR @pzcfg!
We figured that the behavior you want could be achieved without breaking changes.
Here's the PR with the relevant change. https://github.com/glideapps/glide-data-grid/pull/164


Gooder paths

Less hardcoding because It was hurting my brain
I highly encourage @jsiek to make sure the Makefile still works before merging, mainly making sure that it's correctly finding python as it's not in your path.

Would you please write a couple sentences that summarize the changes?

The changes all concern the Makefile, in that a lot of paths were hardcoded, and if I so muhc as renamed a file everything would break.
$(PYTHON) used to be at "/opt/homebrew/bin/python3.10", however it's now determined by "$(shell command -v python3)", which should automatically locate Python for us, instead of having to update the Makefile when we clone the repository, or switch branches, and then reupdating before pushing. This change is my primary reason for wanting you to test out the file before merging it in, as I want to make sure that the command will work on Mac.
All tests used to be in a directory called "test", and in the Makefile there were tons of lines such as $(PYTHON) ./deduce.py test/theorem_true.p, however now every file is either in the root directory of the repository, in "test/should-pass", or "test/should-error", and are run through a for loop in the Makefile.


Adding var-dumper as require-dev dependency

📚 Description
Sometimes is really useful to have the "var-dumper Symfony Component" to be able to "dump" some values during run time for debugging purposes. This dependency provides you with two really nice functions:

dump(...$var): it nicely dumps anything (in a beautiful format, actually!)
dd(...$var): it dumps and dies, similar to the previous dump 😄

The fact that it's a require-dev dependency shouldn't affect the prod run time for the final consumer/client.
🔖 Changes

Adding symfony/var-dumper as require-dev dependency

It's merged now!


=> Bluesky: link preview embeds sometimes fail or contain raw HTML

Ugh. Example: https://bsky.app/profile/pcottle.threads.net.ap.brid.gy/post/3lczzpgrtsep2

From #microformats:

[snarfed] has anyone ever wanted to disable mf1 backcompat in an mf2 parser?
[snarfed] I'd like that option
[snarfed] example of bad results for parsing mf1 backcompat: https://pin13.net/mf2/?url=https://www.popsci.com/science/chain-reaction-the-hopeful-history-of-uranium-book-excerpt/
[tantek] those are some really weird false positives
[tantek] should we add "h-full" to our item blocklist?
[aaronpk] The php parser has that option https://github.com/microformats/php-mf2?tab=readme-ov-file#classic-microformats-markup
[snarfed] re h-full, sure, but I expect most/many mf2 consumers at least look for specific types they're interested in, so h-full wouldn't bother them too much...?
[snarfed] the real problem is the h-entry content there, at least for me
[snarfed] it may not technically be wrong, but it's not great
[tantek] yeah it's pretty bad
[tantek] I wonder if we could tweak it with some backcompat algo tweaks, e.g. if there's only a synthetic e-content (no author or name properties) then perhaps we should drop the entire synthetic h-entry?
[tantek] [snarfed] do you think such "reduce noise" efforts would be sufficient?
[tantek] or would this end up being a continuous patching exercise?
[snarfed] maybe!
[snarfed] honestly I don't know the ecosystem well enough to say
[gRegor] Some more discussion about those Tailwind classes in https://github.com/microformats/microformats2-parsing/issues/59
[gRegor] [snarfed], is the problem the lack of the mf1 entry-title?
[gRegor] The entry-content looks mostly correct, though it includes the little holiday promo at the bottom which it probably shouldn't
[snarfed] yeah I don't have a crisp clear problem statement here, I just don't like it 😎
[snarfed] afaict this ugliness - even if it's technically correct - caused the URL and HTML in the link preview in https://bsky.app/profile/ScienceDesk.flipboard.social.ap.brid.gy/post/3lcgk6msncg42 instead of human-readable text, but I don't exactly understand how yet

More examples with h-full, must be the same or similar CMS:

https://pin13.net/mf2/?url=https%3A%2F%2Fnetflixlife.com%2Fthe-six-triple-eight-is-film-we-should-all-watch-learn-from
https://pin13.net/mf2/?url=https://audiophix.com/shocking-news-music-fans-2024-year-end-chart-list


Shorten URL for gcloud-java link

gcloud-java is in the midst of cleaning up it's gh-pages branch, and part of that is making the URL shorter. The link on ruby's website to gcloud-java should be modified to http://googlecloudplatform.github.io/gcloud-java/ (removing "site/latest/").

@blowmage It seems like lib/rdoc/generator/gcloud/_header.html.erb in the gcloud-rdoc branch controls the link to gcloud-java from the docs pages.  However, if I modify the gcloud-java link in that file, that won't update the existing docs pages' links, right?  Do you have a recommendation on how to best modify the links in the existing docs pages?

I'll take care of it, no problem. I was distracted all afternoon on another issue. :)

Great, thanks!

K, the site links and the documentation links are updated now. Thanks for the heads up!


Visual Studio Code extremely slow

I updated today on the recent version of vscode and since that it gut unusable because its incredible slow - call it frozen most of the time..even dialogs to visual feedback "clicks" or menu selection take a minute or more.

redhat.java-unresponsive.cpuprofile.txt
Looking into the taskmanager there are enough resources .- can't say where this interrupts coming from. Everything else in my system is running at "normal" speed at the same time.

Rolling back from plugin 0.74.0 (which was working vscode before 1.53.1 )  to 0.73.0 ..vscode is not completly unusable  but not acceptable usable (only if your boss pays your to have a coffe after each click or key stroke to wait for vscode to react)

/duplicate https://github.com/microsoft/vscode/issues/116017

Why is this closed?? The bug is still unresolved. The problem is not the plugin. The issue started with vscode 1.53.1. Wth prior versions all works as expected, no matter which version of the redhat plugin. Even not sure if redhat plugin is the root cause at all. Maybe its juts the only plugin that was fast enough to complain by error message before the whole thing is froozen and i need to kill the process.
Pleas reopen my issue. This is a blocker.. and no dupe of Appl1 MC stuff. I haven neither Apple nore do i see more than 23% cpu usage ..while the issue freezes my VsCode. i can't any longer use vscode.

Do you have the issue when you run with --disable-extensions ? If so, please provide the output of code --status and also the following profile https://github.com/microsoft/vscode/wiki/Performance-Issues#profiling-the-renderer-process


Add Wiseconnect submodule in Matter

Problem
Silicon_Labs Wiseconnect SDK is cloned separately from CHIP
Change overview
It Add Silicon_Labs Wiseconnect SDK as submodule
Testing
Tested manually on EFR32MG12 + rs9116 board

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


Modified report-song-page

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📷 Screenshots

Original
Updated

Make requirements red. Make it red even on hover, only be a hyperlink when requirements is tapped.

Yeah okay

remove the underline from "Requirements".

Sure

@Shalini469717 - thanks for your contribution.


support integer arithmetic

seems like it would be interesting to check if an algorithm was implemented correctly. my conjugate gradient implementation doesn't seem to converge very well and was wondering if it's just due to floating point error or something else.

how would field operations work with integers?

data types are required to be Copy and Pod since that's used for many optimizations.
so heap allocated multiprecision floats are unsupported. you can implement stack allocated big floats, but that is out of scope for faer and should be done in a separate library.
regarding conjugate gradient, there is currently a working implementation in src/linop/conjugate_gradient.rs that you can use to compare with yours, or wait until the next version is released

Oh, cool, will try that...

tried cg and bicgstab. I know I'm probably doing something wrong, but I'm not very impressed with the results of krylov methods so far. (bicgstab doesn't converge even for the simplest matrices, and cg seems to take longer than the theoretical matrix dim). I guess I'll stick to direct methods for now as they're probably much faster and more reliable for small problem sizes even if the matrix is sparse. (the main reason I was interested in krylov methods is because it seemed like they could theoretically achieve a better accuracy than direct methods since they could be as accurate as computing the residual allows)

can you share the code you tried?

#[derive(Debug)]
struct Sparse(SparseColMat<usize, c64>);
impl LinOp<c64> for Sparse {
    fn nrows(&self) -> usize {
        self.0.nrows()
    }

    fn ncols(&self) -> usize {
        self.0.ncols()
    }

    fn apply_req(
        &self,
        _rhs_ncols: usize,
        _parallelism: Parallelism,
    ) -> Result<StackReq, SizeOverflow> {
        Ok(StackReq::empty())
    }

    fn apply(
        &self,
        out: MatMut<'_, c64>,
        rhs: MatRef<'_, c64>,
        parallelism: Parallelism,
        _stack: PodStack<'_>,
    ) {
        matmul::sparse_dense_matmul(
            out,
            self.0.as_ref(),
            rhs,
            None,
            c64::new(1., 0.),
            parallelism,
        );
    }

    fn conj_apply(
        &self,
        out: MatMut<'_, c64>,
        rhs: MatRef<'_, c64>,
        parallelism: Parallelism,
        _stack: PodStack<'_>,
    ) {
        matmul::sparse_dense_matmul(
            out,
            self.0.as_ref().adjoint().to_col_major().unwrap().as_ref(),
            rhs,
            None,
            c64::new(1., 0.),
            parallelism,
        );
    }
}

#[allow(unused)]
fn solve_bicgstab(a: SparseColMat<usize, c64>, y: Col<c64>) -> Result<(Col<c64>, SolutionInfo)> {
    println!("{a:?} x = {y:?}");
    let dim = y.nrows();
    let precond = IdentityPrecond { dim };
    let a = Sparse(a);
    let mut params = BicgParams::default();
    params.max_iters = dim;
    let mut pod_buffer = GlobalPodBuffer::new(
        bicgstab_req::<c64>(&precond, &precond, &a, 1, Parallelism::None).unwrap(),
    );
    let podstack = PodStack::new(&mut pod_buffer);
    let mut x = Col::zeros(dim);
    let info = bicgstab(
        x.as_2d_mut(),
        precond,
        precond,
        a,
        y.as_2d_ref(),
        params,
        Parallelism::None,
        podstack,
    )
    .map_err(|e| anyhow::anyhow!("{:?}", e))?;
    let info = SolutionInfo {
        abs_residual: info.abs_residual,
        rel_residual: info.rel_residual,
        iter_count: info.iter_count,
    };
    Ok((x, info))
}

[
  (0, 0, 1.0 + 0.0 * I), (1, 0, -1.0 + 0.0 * I), (2, 0, -1.0 - 0.0 * I),
  (0, 1, 0.0 + 0.0 * I), (1, 1, 1.0 + 0.0 * I), (2, 1, 1.0 + 0.0 * I),
  (0, 2, 0.0 + 0.0 * I), (1, 2, 1.0 + 0.0 * I)
] x = [
  [0.0 + 0.0 * I],
  [0.0 + 0.0 * I],
  [1.0 + 0.0 * I],
]
thread 'main' panicked at src/main.rs:10:33:
called `Result::unwrap()` on an `Err` value: NoConvergence { abs_residual: 1.0, rel_residual: 1.0 }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thanks! i'll look into it soon and report back

@dvc94ch the code seems to be correct. the problem comes from the original bicgstab algorithm that seems to perform a division by zero in the first iteration due to the residual and its image by A being orthogonal. the same thing happens in the eigen and scipy implementations as well, which i guess makes bicgstab not that good of a solver in the general case

Ah thought it was a general solver. What would work better? bicgstab(n) which if I understand correctly uses gmres every few iterations to stabilize? Or restarted gmres? I thought the main advantage over gmres was that it doesn't need more memory every iteration.
Was building a linear elasticity solver to modulate the infill in slicing of 3d parts, but got side tracked building a toy circuit simulator to practice some numerical methods. The above matrix is a modified nodal analysis matrix for a 1V source and 1ohm resistor. I think for linear elasticity cg works well, but for a circuit simulator need something more general.

im still relatively new to iterative solvers so i don't know what would be better. but once i implement gmres i'll check if it also has any weird edge cases.
in any case if your system can be solved by a direct solver, that's what i would recommend, as they're both faster and usually more accurate


image not preview

Hello guys, i face in problem. i using visual studio code, but image not preview, the coding and source folder is correct but still not show image in browsers.
can anyone write the solution.

/needsMoreInfo


Sheduled codegen

JY and I are breaking this PR down into others. Closing this and will reopen new ones.


chore(package): update codelyzer to version 3.0.0-rc.2

https://greenkeeper.io/

rc.2 appears to have been pulled, it's a beta version again now


[BUG]: Wrong column name when using PgEnum.array()

What version of drizzle-orm are you using?
0.30.6
What version of drizzle-kit are you using?
0.20.14
Describe the Bug
Given the following enum definition:
export const playerPosition = pgEnum("player_position", ['defender', 'midfield', 'attacker'])

I'm defininying this table, notice the column name being position:
export const players = pgTable("players", {
	id: serial("id").primaryKey().notNull(),
	position: playerPosition("position").array(),
});

Running drizzle-kit push:pg results in a correctly created table with id and position columns.
If I am to run drizzle-kit introspect:pg the position column gets renamed into playerPosition as if matching the enum name:
export const players = pgTable("players", {
	id: serial("id").primaryKey().notNull(),
	playerPosition: playerPosition("position").array(),
});

This only happens if I'm using a PgEnum.array() as a value, without using .array() it works as expected.
Expected behavior
Running drizzle-kit introspect:pg should keep the correct column name:
export const players = pgTable("players", {
	id: serial("id").primaryKey().notNull(),
	position: playerPosition("position").array(),
});

Environment & setup
No response

@realmikesolo any updates on this? I'm willing to look into it but I only found a mirror repository for drizzle-kit. Where should I be looking for the source code?

@dancamdev hey, I'll fix that in the next release. This one is fast fix, so shouldn't be a problem. Thanks a lot for your ticket!

@AndriiSherman thank you for the effort! I'll be waiting on the fix - do you have an ETA?

Any update on this guys?

This should be fixed in<EMAIL_ADDRESS>If you still encounter this issue, please reopen the ticket


Windows 11 Export-StartLayout & Import-StartLayout

Recently was playing around with Windows 11 & start menu layouts for learning & possible Autopilot deployment when the time comes.
I exported a layout with Export-StartLayout -Path "C:\LayoutModification.json" - created the file fine. The start menu was completely blank. Here is the .json from that export.
{"pinnedList":[]}
I imported that file into %localappdata%\microsoft\windows\shell\LayoutModification.json and deployed the image.
The deployed image did seem to run some as the start menu was missing some icons, however, the now blank thumbnails were still working. Could right click, uninstall, launch, pin, etc.
Is this intended, or a bug?
The json had nothing pinned, so why would any apps remain pinned?

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

ID: 31b7cb77-3889-f738-4e72-e5a263a00775
Version Independent ID: 60cd8847-a46f-67a7-6b98-e9a40862fefa
Content: Import-StartLayout (StartLayout)
Content Source: docset/winserver2019-ps/startlayout/Import-StartLayout.md
Product: w10
Technology: windows
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

The issues section of this repository is intended for documentation problems.
Please consider checking any relevant resources and asking the community about your problem via the following link.
PowerShell Community
Also feel free to reply if there is anything else that could be done to improve the document itself.
Thanks.


[Backport] [2.x] Routine dependency updates: Netty 4.1.91.Final, ASM 9.5, ByteBuddy 1.14.3 (#6981)

Backport of https://github.com/opensearch-project/OpenSearch/pull/6981 to 2.x

@reta I didn't check it thoroughly but is there any reason we have the number of files changed different than the PR on mainand here?

@reta I didn't check it thoroughly but is there any reason we have the number of files changed different than the PR on mainand here?

Yes, we don't have http2 support in 2.x, so the relevant netty dependencies are removed, thanks @owaiskazi19 !


After a scene is created we should flow to the content editor for that scene

The SceneComponent, when creating a new scene, just sits there after the scene is created.

Closed on #100
Instead of flowing right into the editor from the scene component, we just give feedback that the scene is loaded and they can decide what to do next.


open in terminal fails with TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'.

VSCode Version: 81e812c x64
OS Version: Windows 10 x64

TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'.

Steps to Reproduce:

Right click any file and choose "Open in terminal"

Reproduces without extensions: Yes

I'll fix try this up before the next build on Sunday evening.
/cc @cleidigh

@Tyriar
just saw this , sounds like a separate issue from the hyperlinks within the terminal.
Will re-sync once you do a commit...

@cleidigh I think it's related to the bottom padding


Possible to suppress empty messages?

I am dealing with a system that is mapping an internal database to arbitrary path elements in gNMI where keys are part of the elem path string, instead of actually being filterable keys.  As a result, I am doing a LOT of filtering on events, and in some cases, end up with messages (lists of Events) that are comprised of just empty events after using the event-drop filter to delete unwanted data.  The file output looks like this:
[
  {}
]
[
  {},
  {}
]
[
  {}
]
[
  {},
  {}
]
[
  {},
  {}
]
[
  {},
  {}
]
[
  {}
]
[
  {},
  {}
]

Is it possible to completely remove empty events from the message, and drop/suppress empty messages instead of writing them to outputs further downstream?

I think it should be doable to add a knob under the output, something like ignore-empty: true

would like this setting added also.

@bewing , @Sparc0  #61 makes the drop processor remove matching messages from the events list. The messages won't make it to the downstream outputs.


Test Package with different Architectures

Slightly related to #65, I would like to test the package with different architectures.

Closing this, as we currently don't support arm64 and don't need to test it.


Feature request: inspection utils

Hey all,
A couple weeks ago I published this article on Hacker Noon and have since been asked if it is possible to make a github repo out of this idea.  Obviously the article is way too much of a hack, but I would like to try to make the work presentable. However, I would need to do it in a way that does not hack redux saga's internal API.
My idea is to create util classes in redux-saga that can determine what objects are (i.e. isPut, isCall) and get values associated with them (i.e. getFn, getArgs).  Then, I'd create a separate redux-saga-teller project that takes it from htere.  Does this seem like a reasonable addition to the code base?  It is minimally invasive and would be pretty easy to update as the API changes. If so, I can make a PR.

Isnt asEffect what you are looking for mostly?

Yup! The only thing then that we'd need is a public API function to get actions for PUT, functions and arguments for CALL and FORK, etc.. Also, asEffect is currently not documented in the API section - is it supposed to be public?

Closing due to inactivity.  If this is still an issue then please reply and I will reopen and try to help.  Thanks!


Support --txpool.nolocals to disable local exemptions for locally submitted transactions

Describe the feature
Currently, local transactions are exempt from several checks:
https://github.com/paradigmxyz/reth/blob/afdb0a314845a80c83d99d946007585229174d83/crates/transaction-pool/src/pool/txpool.rs#L1277-L1277
https://github.com/paradigmxyz/reth/blob/afdb0a314845a80c83d99d946007585229174d83/crates/transaction-pool/src/validate/eth.rs#L238-L238
This is not feasible if the send_rawTransaction endpoint is public.
Therefor we need a setting to effectively disable local transaction checks
TODO

add CLI argument
add to PoolConfig https://github.com/paradigmxyz/reth/blob/afdb0a314845a80c83d99d946007585229174d83/crates/transaction-pool/src/config.rs#L22-L22
Integrate in validator https://github.com/paradigmxyz/reth/blob/afdb0a314845a80c83d99d946007585229174d83/crates/transaction-pool/src/validate/eth.rs#L462-L462
update checks, see above

see also geth --txpool.nolocals
Additional context
No response

i take this

@mattsse assign me please


avsnr.wrong.account.py

You only need ID + token  My goal is to publish unencrypted information, it's for education and if you're smart about it, you'll use it.  Developer: @avsnr

Closing as off-topic. This is not related to dev containers or setting up a dev environment.


[Installation] Fix the Cocoapods command to not require the library to be linked manually

This is going to require Lookback to add the vendored_frameworks option to their podspec.


Adding regex for comprehensive match for compiler names

Adding regex for comprehensive match.
It should match with hcc and /opt/rocm/bin/hcc

So to handle this we need to only link libhip_hcc.so, but not add the -hc flag.

That is what the hip::host target is for. The hip::hip_hcc target should not add hccrt as a dependency. That is incorrect and inconsistent with make install(which does do it corrrectly).
The PR#1860 should fix that, and there should be no need to check for the compiler name.

Closing since PR #2010 has been merged.


High-level API for multimodality

Is your feature request related to a problem? Please describe.
Current high-level implementation of multimodality is relying on a specific prompt format.
Describe the solution you'd like
Models like Obsidian work with llama.cpp server and have a different format. It would be nice to have a high-level API for multimodality in llama-cpp-python to be able to pass image/images as an argument after initializing Llama() with all the paths to required extra-models, without relying on a pre-defined prompt format such as Llava15ChatHandler.
Describe alternatives you've considered
Alternatively, a custom prompt format class that supports images can be implemented, where prompt string is passed as an argument.

I'll consider adding the multi-modal args to the Llama class but I'm worried about growing the API surface too much too quickly.
For now, I can definitely implement an Obsidian chat handler and maybe abstract out some of the Llava stuff to make it easier to make this generic in the future.
Also thank you for bringing that model to my attention, definitely have to give it a try now!

This seems like an apt place to ask this; How can I supply a local image file to use with multimodal images? Looks like the example assumes an image is being hosted at a url somewhere?

@JoshuaFurman good question, I'll update the docs to include this. It works the same as the OpenAI gpt-4-vision-preview you can pass the image as a base64 encoded data url:
import base64

def image_to_base64_data_uri(file_path):
    with open(file_path, "rb") as img_file:
        base64_data = base64.b64encode(img_file.read()).decode('utf-8')
        return f"data:image/png;base64,{base64_data}"

# Replace 'file_path.png' with the actual path to your PNG file
file_path = 'file_path.png'
data_uri = image_to_base64_data_uri(file_path)

Then just pass that in place of the data url

Oh fantastic thank you! And this can be done without running the server right? I'm looking to add this directly into an application

Yup, you just need  to pass the Llava15ChatHandler to Llama like in the README example so that the class knows how to format the chat with images.

Great thanks so much! Happy thanksgiving :)

@JoshuaFurman good question, I'll update the docs to include this. It works the same as the OpenAI gpt-4-vision-preview you can pass the image as a base64 encoded data url:
import base64

def image_to_base64_data_uri(file_path):
    with open(file_path, "rb") as img_file:
        base64_data = base64.b64encode(img_file.read()).decode('utf-8')
        return f"data:image/png;base64,{base64_data}"

# Replace 'file_path.png' with the actual path to your PNG file
file_path = 'file_path.png'
data_uri = image_to_base64_data_uri(file_path)

Then just pass that in place of the http url

Thanks this works

Closed this by mistake, though will be solved in #1147


Added Code of Conduct

Fixes #10

@xp4xbox Add your email in the code of conduct after merging this PR in place of [Your email Address]
Screenshot:

Thanks. Looks good after some small changes.


SAMZA-2222: Documentation for async API

@prateekm Addressed your comments. Some of the language used initially was done with the notion of keeping up consistency within the document.
The page still has some implementation detail and we may want to make it consistent. Will file a follow up JIRA.


ATO Renewal

The statement "If your current ATO is going to expire, you’ll need the ATO to be renewed. Follow the usual steps for getting an ATO. You should be able to reuse most of your existing ATO materials, assuming they have been kept up-to-date."
I think  should be changed to: Many ATOs are issued with a time limit, often this expiration is between one and three years. When an ATO nears expiration going to expire, you’ll need the ATO to be renewed. Follow the usual steps for getting an ATO. You should be able to reuse most of your existing ATO materials, assuming they have been kept up-to-date."

Made changes w/ Pull Request https://github.com/opencontrol/atos/pull/27
#27


Missing nop between lh/lui (ASPSX v2.21)

https://decomp.me/scratch/ssfgq
maspsx omits a nop at 1cc:

Thanks for raising the bug, it should now be fixed - see https://decomp.me/scratch/NRtsT.

Thanks!
I think this issue extends to registers besides v0 as well. I'm seeing it locally with v1 and a2 for example, and with s0 in this scratch at a3c: https://decomp.me/scratch/z8hns

This should also be fixed on master now (I'll get it deployed to decomp.me shortly). Out of interest, what game/library are you working on? There's not been a lot of testing against ASPSX 2.21 so you are providing valuable help by identifying these deficiencies in maspsx - thank you :)

Vandal Hearts, presumably PsyQ 3.4. And glad I can help! maspsx will vastly simplify my builds as well.
Found a couple variations still missing the nop:
https://decomp.me/scratch/uiu32
https://decomp.me/scratch/REDMb (4a0)
Note the second one may be less reliable since it doesn't work with psyq-obj-parser as-is (Unknown relocation type 30)


TDK-7908: Modify dsHost hal header

Reason for change: Added @post tag in dsHost interface file
Risks: Low
Test Procedure: Check the code

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

duplicate PR
Refer this issues
https://github.com/rdkcentral/rdk-halif-device_settings/issues/50


MGMT-19028: IBI only apply the first resource in a file with multiple resources added as extra manifests

IBI only apply the first resource in a file with multiple resources added as extra manifests
Issue / Requirement / Reason for change
https://issues.redhat.com/browse/MGMT-19028
Solution / Feature Overview
The issue is fixed by updating the ReadYamlOrJSONFile function to decode until it reach EOF This ensures the code read the entire file in case we get multiple definitions in a single file

/lgtm

/cherrypick release-4.17


make PodSecurity admission enforce restricted globally

Also removes the warn and audit levels as these are driven
by the enforcement policy.
/assign @ibihim
/assign @deads2k

supersedes https://github.com/openshift/cluster-kube-apiserver-operator/pull/1339

/test e2e-aws-serial

/approve

/lgtm, matches the changes of https://github.com/openshift/cluster-policy-controller/pull/81

/hold
until we fix ovn

/hold
Source PR may have taken out CI. Investigating.

/retest

/test all

/test k8s-e2e-gcp
this should be an unrelated failure

/test k8s-e2e-gcp
installation failed :disappointed:

/retest
503 on registry service

/retest
I assume somebody broke something upstream. e2e-aws-serial should be fixed now and the upgrade tests should not be broken.

/retest-required
Testes are now being skipped for k8s-e2e-gcp

/test k8s-e2e-gcp

/test all

/test e2e-aws-ovn
cluster install issue

/hold cancel


Password policy phase2

A grab-bag of security-tastic treats to warm your risk mitigating heart.

A user may not use any of their previous 10 passwords
A user may not change their password more then once in a 24 hour period
Passwords expire after 90 days
a new model for temporary lockouts (currently only get created after some number of login failures, but we may find other uses for it)

I relocated some of the lockout-handling code into form methods, and similarly, moved some things out of 'messages' and into ValidationError's.
@kave @kurtw @richaagarwal

Hmm I seem to be getting errors for every model class
/Users/wallk/v1/cfgov-refresh/cfgov/v1/models/demo.py:17: RemovedInDjango19Warning: Model class v1.models.demo.DemoPage doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9.   class DemoPage(CFGOVPage):

I saw that-- but it's not an error, it's a warning ;)

committed fixes for the spacing issues and the unknown user case

That warning is interesting-- apparently something is causing those models to be imported before the app is officially initialized-- which isn't a problem now, but will break in 1.9

The code that creates new PasswordHistoryItem entries now lives in a signal handler, so it'll catch password changes whereever they happen-- even an administrator changing a password in django-admi.
Another thing I had to learn about: AppConfig's.

After a user's password expires, there's should probably be something that directs them to a Reset Password view or an automatic redirect.

The above comment should apply to the lockout error as well.
Other than that, I tested everything out and it's clear! Good work @rosskarchner! :+1:

minor comments, looks to me :+1:

OK, I've edited those errors with a link to the password reset page.


Missing STORAGE-ACCESS-KEY in bosh.yml

The page https://bosh.io/docs/init-azure.html references STORAGE-ACCESS-KEY in Step 2 but the sample manifest does not contain that placeholder.

i think this is resolved via bosh-deployment usage.


Restart KafkaOpenMetadataEventConsumer if thread dies

We have been having problems where, for whatever reason the KafkaOpenMetadataEventConsumer thread dies.  When this happens, the sync processing completely stops.  In order for our product to continue functioning when this happens, we need the KafkaOpenMetadataEventConsumer thread to be restarted if it dies.
There is already similar logic for restarting the KafkaOpenMetadataEventProducer if that thread dies.  The mechanism needs to be extended to also apply to the consumer.

FYI, I'm working on a PR for this.

What are the reasons for the thread dying - should there be some additional error handling in place to prevent it dying?

@wbittles What we saw was that that thread died during what appeared to be a transient out of memory issue.  We are looking at that, but to us this is really about resiliency.  If the thread dies, we are pretty much dead in the water, so we need to do everything we can to keep it alive.  In our scenario, the memory issue resolved itself but the kafka consumer thread remained dead.

@mandy-chessell ^^

@jnhagelberg
Resiliency shouldn't be valued over functional integrity, there is little value in restarting a thread if it's behaviour is indeterminate.
My understanding is that OOM is a Java JVM Error , where the JVM has already decided that it's in an error state and that the JVM needs to be shut down.
My fear is that this JVM Error has been caught and translated into an Exception which is allowing Egeria to ignore the state of the JVM, and Egeria is in effect just limping along in an error state.
To resolve OOM errors usually involves allocating more memore via the JVM command line options and it's unclear how we are going to avoid the need to shut the JVM and down and restart with an increased heap ?

@wbittles - Completely agree... In fact in this case I would suggest that the JVM must be restarted - for example in a k8s environment this could be to intentionally let the server 'die' (shut itself down) and exit, and k8s will restart it elsewhere - clean environment, new jvm etc

@planetf1 @wbittles I agree that we should probably restart the JVM.  However, to this is more about resiliency.  We cannot guarantee that the JVM will be restarted.  If it does not restart we need to make a best effort attempt to keep functioning.
There is already logic for handling of the event producer dies, and there also needs to be logic to handle of the consumer dies.  This is not a theoretical issue.  We have customers whose systems are out of sync because the consumer thread died.  This is further complicated by the fact that in our implementation code we have no way of detecting and responding to instances where the kafka consumer thread dies.  The thread lives in egeria, so the fix must go in egeria.  Restarting the thread in cases like this is very easy in the egeria side, but nearly impossible for us to do on our side.
I do not understand what your concern is.  If there is some specific aspect of the fix you are concerned about, please let us know and we will address it.  We need egeria to robust, and we need for it to be updated when we find problems.  We have even provided the code that fixes this particular problem.

We are also looking into the cause of the OOM issue.  I suspect that it is the queue of unprocessed messages.  Probably the size ("event_bus_max_queue_size") is configured to be too big in their system.  That definitely does need to be fixed.  However, that is separable from this issue.  It is also separable from the fact that we have no good way of detecting and reporting the status of the producer and consumer threads.  I think that all of these need to be fixed.  This issue is just fixing one piece of that, the piece where we attempt to recover when faced with unexpected errors.

I see the PR is closed now so I believe this can be closed.
I have also looked through the code and understand the design. The code does as you intended - though we may need to look again at whether some exceptions should be treated as fatal (ie I am concerned around OOM), but they can be raised in a new issue when we have action.
For now therefore I propose we close the issue


time scale

Hey there! was wondering if it is possible to change the time interval for this library. Seems like for now it only support daily data ? will it support hourly or minute data ?

turns out need to put datetime as timestamp 🙏

@apawitan1995 bro Have you figured out how to do it , I have that you told but those bars but i see only one bar , and it seems like they are stacked on top of each other please help..

@Anshufi
You can pass in a timestamp instead of "business day" for the time field of that series. It is timestamp in seconds according to Tradingview's documentation here: https://tradingview.github.io/lightweight-charts/docs/3.8/api#time

@tysonwu Thanks for the reply brother, its working , and i want to some more help

chart is plotting but only date shows on timescale
how to change the color of line series on conditional basis , have some values and i want to change the color of moving average when value is greater than 0 green else red
how to create a sub plot in the chart like atr and sync them and how make my crosshair moves freely..

@Anshufi You can pass in a timestamp instead of "business day" for the time field of that series. It is timestamp in seconds according to Tradingview's documentation here: https://tradingview.github.io/lightweight-charts/docs/3.8/api#time
chart is plotting but only date shows on timescale , this is the timestamp '1609731900'

@tysonwu
Just want to confirm that this will only plot daily data and not minute timeframe data right?
Looking to plot minute-to-minute data


[SUPPORT]spark-sql MOR query error with org.apache.avro.SchemaParseException: Cannot parse  schema

Describe the problem you faced
Write new data with config
hoodie.avro.schema.validate=true;
hoodie.datasource.write.schema.allow.auto.evolution.column.drop=true;
hoodie.datasource.write.reconcile.schema=true;
query with config :
set hoodie.schema.on.read.enable=true;
set hoodie.datasource.write.reconcile.schema=true;
set hoodie.avro.schema.validate=true;
The new data is written normally, but query is error.
Check the schema file is with the latest_schema.
extraMetadata : {
schema : "{"type":"record","name":"ods_api_test_case_record","namespace":"hoodie.ods_api_test_case","fields":[{"name":"_hoodie_commit_time","type":["null","string"],"doc":"","default":null},{"name":"_hoodie_commit_seqno","type":["null","string"],"doc":"","default":null},{"name":"_hoodie_record_key","type":["null","string"],"doc":"","default":null},{"name":"_hoodie_partition_path","type":["null","string"],"doc":"","default":null},{"name":"_hoodie_file_name","type":["null","string"],"doc":"","default":null},{"name":"gmt_create","type":["null","long"],"default":null},{"name":"owner","type":["null","string"],"default":null},{"name":"last_status","type":["null","long"],"default":null},{"name":"description","type":["null","string"],"default":null},{"name":"offset","type":["null","long"],"default":null},{"name":"last_run","type":["null","long"],"default":null},{"name":"env","type":["null","string"],"default":null},{"name":"gmt_modified","type":["null","long"],"default":null},{"name":"created_by","type":["null","string"],"default":null},{"name":"run_ignore_fail","type":["null","long"],"default":null},{"name":"test_type","type":["null","long"],"default":null},{"name":"tags","type":["null","string"],"default":null},{"name":"dt","type":["null","string"],"default":null},{"name":"ct","type":["null","long"],"default":null},{"name":"partition","type":["null","string"],"default":null},{"name":"name","type":["null","string"],"default":null},{"name":"only_me","type":["null","long"],"default":null},{"name":"id","type":["null","long"],"default":null},{"name":"region","type":["null","string"],"default":null},{"name":"status","type":["null","long"],"default":null}]}",
latest_schema: "{"max_column_id":24,"version_id":20230619064139757,"type":"record","fields":[{"id":0,"name":"_hoodie_commit_time","optional":true,"type":"string","doc":""},{"id":1,"name":"_hoodie_commit_seqno","optional":true,"type":"string","doc":""},{"id":2,"name":"_hoodie_record_key","optional":true,"type":"string","doc":""},{"id":3,"name":"_hoodie_partition_path","optional":true,"type":"string","doc":""},{"id":4,"name":"_hoodie_file_name","optional":true,"type":"string","doc":""},{"id":5,"name":"gmt_create","optional":true,"type":"long"},{"id":6,"name":"owner","optional":true,"type":"string"},{"id":7,"name":"last_status","optional":true,"type":"long"},{"id":8,"name":"description","optional":true,"type":"string"},{"id":9,"name":"offset","optional":true,"type":"long"},{"id":10,"name":"last_run","optional":true,"type":"long"},{"id":11,"name":"env","optional":true,"type":"string"},{"id":12,"name":"gmt_modified","optional":true,"type":"long"},{"id":13,"name":"created_by","optional":true,"type":"string"},{"id":14,"name":"run_ignore_fail","optional":true,"type":"long"},{"id":15,"name":"test_type","optional":true,"type":"long"},{"id":16,"name":"tags","optional":true,"type":"string"},{"id":17,"name":"dt","optional":true,"type":"string"},{"id":18,"name":"ct","optional":true,"type":"long"},{"id":19,"name":"partition","optional":true,"type":"string"},{"id":20,"name":"name","optional":true,"type":"string"},{"id":21,"name":"only_me","optional":true,"type":"long"},{"id":22,"name":"id","optional":true,"type":"long"},{"id":23,"name":"region","optional":true,"type":"string"},{"id":24,"name":"status","optional":true,"type":"long"}]}"
}`
To Reproduce
Review code and debug.

org.apache.hudi.internal.schema.utils.InternalSchemaUtils.searchSchema

Expected behavior
A clear and concise description of what you expected to happen.
Environment Description

Hudi version :0.13.1

Spark version :3.2.1

Hive version :3.2.1

Hadoop version :3.2.2

Storage (HDFS/S3/GCS..) :s3

Running on Docker? (yes/no) :no

Additional context
Add any other context about the problem here.
Stacktrace
Add the stacktrace of the error.
Caused by: org.apache.avro.SchemaParseException: Cannot parse  schema
at org.apache.avro.Schema.parse(Schema.java:1633)
at org.apache.avro.Schema$Parser.parse(Schema.java:1430)
at org.apache.avro.Schema$Parser.parse(Schema.java:1418)
at org.apache.hudi.common.util.InternalSchemaCache.getInternalSchemaByVersionId(InternalSchemaCache.java:225)
at org.apache.spark.sql.execution.datasources.parquet.Spark32PlusHoodieParquetFileFormat.$anonfun$buildReaderWithPartitionValues$2(Spark32PlusHoodieParquetFileFormat.scala:159)
at org.apache.hudi.HoodieDataSourceHelper$.$anonfun$buildHoodieParquetReader$1(HoodieDataSourceHelper.scala:71)
at org.apache.hudi.HoodieBaseRelation.$anonfun$createBaseFileReader$2(HoodieBaseRelation.scala:569)
at org.apache.hudi.HoodieBaseRelation$BaseFileReader.apply(HoodieBaseRelation.scala:637)
at org.apache.hudi.HoodieMergeOnReadRDD.compute(HoodieMergeOnReadRDD.scala:87)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:373)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:337)
at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:52)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:373)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:337)
at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:52)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:373)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:337)
at org.apache.spark.shuffle.ShuffleWriteProcessor.write(ShuffleWriteProcessor.scala:59)
at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:99)
at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:52)
at org.apache.spark.scheduler.Task.run(Task.scala:133)
at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:506)
at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1474)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:509)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

@zyclove Can you try the following -

Try reading the data without setting hoodie.schema.on.read.enable=true;
Do you need to set - schema.allow.auto.evolution.column.drop. Do you need column to be dropped? If not can you write with default configurations.
Keep all params as it is as you are using now and keep hoodie.schema.on.read.enable=true while writing the data also.

@zyclove If you can create a reproducible script with fewer columns , it will help us a lot for triaging.

@zyclove Can you try the following -

Try reading the data without setting hoodie.schema.on.read.enable=true;
Do you need to set - schema.allow.auto.evolution.column.drop. Do you need column to be dropped? If not can you write with default configurations.
Keep all params as it is as you are using now and keep hoodie.schema.on.read.enable=true while writing the data also.

I do it.
but just set hoodie.schema.on.read.enable=true not works,
only set hoodie.datasource.read.extract.partition.values.from.path=true; it works ok.

@zyclove Just a thing to notice -
hoodie.datasource.read.extract.partition.values.from.path=true
will get the partition details from the file system and not from hudi files. So sometimes it may return the deleted partitions as hudi will not delete the partition from file system(in order to support point in time queries) when you drop a partition.
It would be great help if you can try reproducing the issue with the sample data. It will help us to fix the issue.

@xushiyan @ad1happy2go
After upgrading hudi 0.13.1, it can be executed normally after adding the above two configurations, but it failed again today, and still reports the same error.
Can you take a look at this issue first, thank you.
23/06/27 12:16:18 ERROR Executor: Exception in task 3.0 in stage 7.0 (TID 99)
org.apache.avro.SchemaParseException: Cannot parse <null> schema
        at org.apache.avro.Schema.parse(Schema.java:1633)
        at org.apache.avro.Schema$Parser.parse(Schema.java:1430)
        at org.apache.avro.Schema$Parser.parse(Schema.java:1418)
        at org.apache.hudi.common.util.InternalSchemaCache.getInternalSchemaByVersionId(InternalSchemaCache.java:225)
        at org.apache.spark.sql.execution.datasources.parquet.Spark32PlusHoodieParquetFileFormat.$anonfun$buildReaderWithPartitionValues$2(Spark32PlusHoodieParquetFileFormat.scala:159)
        at org.apache.hudi.HoodieDataSourceHelper$.$anonfun$buildHoodieParquetReader$1(HoodieDataSourceHelper.scala:71)
        at org.apache.hudi.HoodieBaseRelation.$anonfun$createBaseFileReader$2(HoodieBaseRelation.scala:569)
        at org.apache.hudi.HoodieBaseRelation$BaseFileReader.apply(HoodieBaseRelation.scala:637)
        at org.apache.hudi.RecordMergingFileIterator.<init>(Iterators.scala:188)
        at org.apache.hudi.HoodieMergeOnReadRDD.compute(HoodieMergeOnReadRDD.scala:100)
        at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:373)
        at org.apache.spark.rdd.RDD.iterator(RDD.scala:337)
        at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:52)
        at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:373)
        at org.apache.spark.rdd.RDD.iterator(RDD.scala:337)
        at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:52)
        at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:373)
        at org.apache.spark.rdd.RDD.iterator(RDD.scala:337)
        at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:90)
        at org.apache.spark.scheduler.Task.run(Task.scala:133)
        at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:506)
        at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1474)
        at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:509)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)```

@zyclove Closing this out as looks like you opened a new one for the same issue. Please let us know once you try with 0.12.3.
Lets track on this new issue - https://github.com/apache/hudi/issues/9119

@ad1happy2go This problem still exists in version 014, how to solve it?


added uws_req_get_case_sensitive_method in C API

added getCaseSensitiveMethod featured in v20.28.0 Latest

Can you decide a license and put in the top of your files

Can you decide a license and put in the top of your files

Done

If you want MIT license it would be:
Copyright 2022 Ciro Spaciari
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Copyright 2022 Ciro Spaciari

Sorry i updated again


Backbone dihedral features

Thanks for your meaningful work.
I am wondering how you calculate the dihedral angle of the protein termini residues as features. It seems that NaN values may occur.

Thanks for your interest! You're absolutely right. NaNs will occur wherever there are chain breaks, including the terminal residues. After I compute the dihedrals, I transform the NaNs into 0s here so that it doesn't affect the model.


Microsoft Integrations overview

Status
Ready
Related Issues
fixes: #37147
Description
This document should organize the knowledge we have about Microsoft integrations, and emphasize differences between similar integrations

@Arsenikr doc review completed.  Need to add link to Microsoft Intune Indicator Feed integration README at a later time.


install error: dir /srv/modoboa/instance/media/webmail not exist

hi
few days ago i installed modoboa on a live ub1604 system with no problem.
now trying to install it in a local (virtualbox ub1604) network i get

Installing modoboa
Traceback (most recent call last):
File "./run.py", line 73, in
main()
File "./run.py", line 63, in main
scripts.install("modoboa", config)
File "/home/user1/modoboa-installer/modoboa_installer/scripts/init.py", line 21, in install
getattr(script, appname.capitalize())(config).run()
File "/home/user1/modoboa-installer/modoboa_installer/scripts/base.py", line 151, in run
self.post_run()
File "/home/user1/modoboa-installer/modoboa_installer/scripts/modoboa.py", line 157, in post_run
self.apply_settings()
File "/home/user1/modoboa-installer/modoboa_installer/scripts/modoboa.py", line 132, in apply_settings
utils.mkdir(d, stat.S_IRWXU | stat.S_IRWXG, pw[2], pw[3])
File "/home/user1/modoboa-installer/modoboa_installer/utils.py", line 79, in mkdir
os.mkdir(path, mode)
OSError: [Errno 2] No such file or directory: '/srv/modoboa/instance/media/webmail'

???
thanks a lot (also for the great work)

Could you please move your issue to the appropriate repository? (https://github.com/modoboa/modoboa-installer)

Thank you.

sorry! wrong place for this issue.


[Doc Improvement][update add API connection]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/add-API-connection.md
81
29
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit cf4d37b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/add-API-connection.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/resources/bot-v3/bots-with-tabs.md
88
9
link
:white_check_mark:

msteams-platform/toolkit/add-API-connection.md
81
29
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 377d91a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/resources/bot-v3/bots-with-tabs.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-API-connection.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/resources/bot-v3/bots-with-tabs.md
88
9
link
:white_check_mark:

msteams-platform/toolkit/add-API-connection.md
81
28
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit acb4122:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/resources/bot-v3/bots-with-tabs.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-API-connection.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a0f93a2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:white_check_mark:Succeeded
View

msteams-platform/resources/bot-v3/bots-test.md
:white_check_mark:Succeeded
View

msteams-platform/resources/bot-v3/bots-with-tabs.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-API-connection.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
88
20
link
:white_check_mark:

msteams-platform/resources/bot-v3/bots-test.md
82
22
link
:white_check_mark:

msteams-platform/resources/bot-v3/bots-with-tabs.md
88
9
link
:white_check_mark:

msteams-platform/toolkit/add-API-connection.md
81
28
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.


Hotfix - Infra Security Group Incoming traffic

Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-pDO66x4b9gEu
Commit ID: 31776b864e63918475d9ce7d3941c7d09f43de4e
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Implementing DB and personalization

What issue are you solving? (Give #issuenumber)
I solved the issue #31 and the issue #36
How do you solve it? (please write this so a human can understand it - bulletpoints are okay)

I made a file db.py that do all the job on the sqlite3 database
obs: i can change this, depending on the changes or other pull request i can put it inside prog-o-meter.py as well

I made some changes to the prog-o-meter.py file so it uses the new implemented db

Made a new Window inside the prog-o-meter.py a GUI for personalization
obs: didn't had a lot of idea of how to do it maybe any suggestion of changing it would be welcome

If there is something specific in your solution, that you would like the reviewer to give feedback on, tell us here:
This is still WIP but i want you to check it out Because it is working but:

I still need to remove and change a lot of ugly code

I didn't change functions names , it may look strange and confusing

I didn't put any docstrings or comments so if the code if confusing ask me, i will add comments and docstrings as soon as i can
obs: i wont have a lot of time these days but i will try to do these as i can.

There is a lot of pull requests already so i may want to change as the files change

I tried to make the function and variables names easy to understand but it looks messy and ugly

any feedback is appreciated
If this is your first pull request to the prog-o-meter project, we would really appreciate it if you would fill out this Google form.
This lets us know more about our contributors, and what we can do to make it easier and nicer to contribute to the prog-o-meter project.
Please submit your answer here and put an 'x' in the box below.

[ ] It is my first pull request to prog-o-meter, and I have answered the survey

Hey, awesome that we are making progress on the database.
I am sorry it has taken me a while to get to your PR. In the meantime I have merged in the new user object, so there is now a user class, with all the functions related to the user. I am sorry that unfortunately that means that we need to rewrite some of the database work.
The new userobject is in the file user.py - let me know if you would have time to update the database implementation to work with the new object.

For the personalization I think setting the two colors and a motivational phrase is nice for now. We have talked about letting the user add a text for their "next goal", which we can add at a later point.

I expected that, but i only made this so you can take a look at it as it works.
I will try to adjust to the changes but right now i wont have much time since i am working on a more personal project.
I want to know if i should put it together to the user.py or another file the code is really messy right now and i need to add comments and etc to make the code understandable, i will try to do it once i can. My priority right now is finishing at least the main part of my own project, thanks for the feedback!

And for the way to set up Colors do you think HEX is alright or maybe another way?
Using only one button to apply all of the changes might be better as well.
Also about the start when the user checks I have a Meter and inputs a unknown name,
i needed to make a workaround, but i think a simple warning would be better to fix it

Hey, no stress, we all have plenty of other things to work on, so take your time.
I don't have much experience with databases, but the your code is easy to read even without, so that is a really big plus for our project.
I think you can make a database.py file if you prefer, but if you think adding it to the user.py file makes more sense, then that is olay with me.

Sorry if i have been unclear about my last question, i just said i needed to create a new user if the user name wasn't on the database, if that is okay.
About the colors, i thought the same


ui: change icon for "restart service" to fa-repeat

Too many times I find myself clicking on "Refresh", but accidently choosing "restart service" instead. Is it possible to change the restart icon?

Change it to what exactly? https://fontawesome.com/v4.7.0/icons/

I'm not an expert, and have no experience in UI/UX, but maybe something like that?
https://www.onlinewebfonts.com/icon/487163

I posted the link to the relevant font awesome for a reason. We are likely not adding another font library.

Ok, so how about changing the "restart service" to one of the following options? It just needs to be different...
https://fontawesome.com/v4.7.0/icon/retweet
https://fontawesome.com/v4.7.0/icon/repeat

Just to complete the circle from a reddit discussion :
Restart icon can be overloaded in the main.css with:
.fa.fa-refresh.fa-fw::before {content: "\f079";} - retweet icon
.fa.fa-refresh.fa-fw::before {content: "\f01e";} - repeat icon
.fa.fa-refresh.fa-fw::before {content: "\f110";} - spinner icon
Beauty is in the eye of beholder, but:

spinner icon is a no-go as we already use its animated version to signal to wait (for API call returns)
repeat icon makes it even more similar to a browser refresh icon
retweet icon is commonly used to RETWEET stuff - and we don't want to retweet the Unbound status!

Maybe, but anything is better than two IDENTICAL icons, very close to each other, with completely different purpose...

I don't mind fa-repeat if it brings us an inch closer to the optimal solution.

Today I powered off a customer Firewall instead of rebooting. Things happen when your not focused. Quite sure it may happen to others also when Icon changes. But indeed, same Icons on same area are confusing.
Confirmaton warning when hitting restart? :)

Confirmaton warning when hitting restart? :)

On the service or the firewall? oO

Service Icon in screenshot. A bootstrap warning asking If you really want to restart the service

The worst thing that could happen is remote lockout. ;) Let’s start with the icon and see what happens.

@fichtner what are your thoughts to refresh the iconset to a bit younger fontawesome? New duotone icons look amazing:

These are still conceptually the same icons we have right now? Color-coding helps distinguish, but also makes it harder to explain/document.

The same set as the good ol' v.4.7 we have today, except this one is from v.6.0 font.
How about I bake the new style into one OPNsense theme and then you be the judge if we push it to the main branch?

Attached is a theme that is identical to the default OPNsense theme, except it includes FontAwesome 6 icons. The disabling of current FontAwesome 4 happens in theme.js alongside with injection of three checkboxes that you will see in the top right corner:

no checkboxes set: Solid icons (.fas)
first checkbox set: Duotone icons (.fad)
second checkbox set: light icons (.fal)
third checkbox set: regular icons (.far)

I believe that the new FontAwesome icon pack includes much better/diverse choices for icons than what we are constrained to today. Few screenshots:

fontawesome6.zip

Updating to newer bootstrap is certainly a good idea, although a bit out of scope for this issue. Happy to review a minimal patch for the core theme although that won’t be included in 21.1.x for sure. We have to make sure all older themes still work and all icons are gracefully replaced (network time seems to be gone).

there is a shims.css included in FontAwesome 6 - and it remaps most (but not all) old icons into new ones.
If there is interest, I can create a Pull Request with a theme that can help us fully validate and test the new FontAwesome and Bootstrap library.


Update split version

Thanks for the pull request. This repository is now dormant as a record of the class as it was in 2022. Please see the current live version at https://github.com/msp-strath/cs316-functional-programming


Add retry logic to S3FileSystem

S3FileSystem should have some retry behaviour if ObjectsDelete fails. I have seen such example in our job where 1 item from the delete batch cannot be deleted due to S3 InternalError causing the whole job to restart. The source code I am referring to:
https://github.com/apache/beam/blob/8a88e72f293ef7f9be6c872aa0dda681458c7ca5/sdks/java/io/amazon-web-services/src/main/java/org/apache/beam/sdk/io/aws/s3/S3FileSystem.java#L633

The retry logic might be added to other S3 calls in S3FileSystem as well.
Imported from Jira BEAM-6031. Original Jira may contain additional context.
Reported by: pawelbartoszek.

All AWS clients implement automatic retries, this behavior is enabled by default. Adding another level of retries won't do any good...
While possible, it's currently not straight forward to customize the retry policy for the S3 file system. It can be done by setting a custom s3ClientFactoryClass in S3Options. This factory would then delegate to ClientBuilderFactory.defaultFactory with a ClientConfiguration containing a customized RetryConfiguration.
https://github.com/apache/beam/blob/5520fe064fc3b7196998d4597746119691eb6681/sdks/java/io/amazon-web-services2/src/main/java/org/apache/beam/sdk/io/aws2/common/ClientBuilderFactory.java#L151-L155


Deduplicate Field implementations in ts

We currently have two Fr implementations, one in bb.js and one in Foundation. These are incompatible with each other, since one uses Uint8Arrays to store the field value, and the other bigint. The Fr and Fq in bb.js also differ in this.
Given that the Uint8Array implementation is more efficient, we should ensure both Fr and Fq in bb.js use that, and then remove the implementations in Foundation and just re-export the bb.js ones. Note that this may break avm field arithmetic, that depends on fields being bigints right now, so we'll need to re-convert fields into bigints before running these operations.
More context here.

Tried tackling this one today and it's way trickier than I originally expected (how unexpected in software engineering).
The issue is that all the serialization in foundation package expects Buffer type and everything in BB expects Uint8Array. Given that we would want to stick to Uint8Array (since introducing Buffer to BB seems incorrect due to it not being natively supported in browsers) the only correct approach seems to be to also deduplicate all the serialization functionality and use the one from BB (e.g. BufferReader in BB works with Uint8Array, then there is a duplicate class in foudnation working with Buffer type) and consequently update everything in aztec-packages/yarn-project.

A solution proposed by Alex:
"IIUC, a stopgap solution would be to convert between Uint8Array and Buffer for serialisation purposes? Then
Node's Buffer extends Uint8Array so a buffer instance should be accepted by any function that expects a Uint8Array. Converting from Uint8Array to a Buffer can done quite cheaply by sharing the memory. BufferReader in foundation already handles both buffers and Uint8arrays
https://github.com/AztecProtocol/aztec-packages/blob/52ce25d1abcc5a8cff7ec360acf23806cb317b57/yarn-project/foundation/src/serialize/buffer_reader.ts#L39-L41 "


429 Error (Too Many Requests)

Your question here...
Hi there! I've been using Instaloader for a while now but starting Monday, it is now throwing a 429 error after about a hundred or so requests and continues to do so. I've waited to let the IP cool down, changed out the IP, etc. but nothing has helped.
I've also looked through the other threads regarding 429 errors and neither of those seem to help either / come to a full conclusion. Is there something I can tweak to avoid these errors?

I found you can get more requests by logging in. Are you doing that?

Sorry I cant help you. From my recent experience, you can get a limited number of anonymous requests, then you are locked out until the next day, or until you log in. Good luck.

I have the same error. Did you manage to solve it?


Updates the Regex pattern do identify dates

Changed the Regex pattern to make the comma between the date and the time optional.
Also, I used the re.split function to split the date and the time since it allows two different separators. This is important so it can be properly split either with or without the comma.

Hi @otavio-s-s
Thanks for showing your interest in this project 👏 .
Please, open an issue here on which bug or feature you are working on. I will see your contribution and inform you.

@otavio-s-s  did you check on your local system after making these changes. Please take a look at the split part of dateTime string.

I did, yes. It's working fine:

Yes, the | in split will create a problem, if the time is not in 24-hour format. Such as "14/03/19, 9:05 am".

Oh, gotcha! I think the best solution would then be to use the normal split and then use replace to remove the comma from the date.

What I think is if there is no comma then add there and let the previous split do his job (split using , ).

But hey, the time is the 24-hour format in both English and Portuguese versions, isn't it?

Not necessary, In my area time is not in 24-hour format 😄 .

Oh, ok! I thought with some standard pattern form WhatsApp, I'm sorry. How would you suggest checking for the comma?

I think, leave the split part as it is and add code if there is no comma in dateTime then replace first space with this , .

Done!

Congratulations @otavio-s-s 🎉 on your contribution to WhatsApp Chat Analyzer. Soon you will see its effect on the app.


fix(hybrid) more robust clustering connection and thread management

Summary
Implements a more robust websockets connection and thread management for
clustering endpoint.

Tries to properly close the connection and notify the client
Tries to properly kill the started threads on reconnection
Adjusts so that expected events are not logged as errors

Timeouts
Closing of connection

Checks websocket status while looping

Fixes an issue reported by other team.

Hold off on merging for a moment, pending sync up with @bungle.

What's the status on this one?

@kidd, well... I guess you forked our test suite at some point, but then have not synched the changes. So this issue is partly because of not synching your suite. The main culprit is here:
https://github.com/Kong/kong-ee/blob/next/2.2.x.x/spec-ee/02-integration/14-hybrid_mode/01-synch_spec.lua#L51-L59
That file was copy pasted from:
https://github.com/Kong/kong/blob/master/spec/02-integration/09-hybrid_mode/01-sync_spec.lua
See what we added there:
https://github.com/Kong/kong/blob/next/spec/02-integration/09-hybrid_mode/01-sync_spec.lua#L24
So if you want quick solution, just add that while we figure out what to do with this PR.

Ah I see! I guess we created an ee-only test, but then if defaults changed we didn't notice it.
Unfortunately, we don't have any way to sync at that level.
We're going to add that today so we can keep merging in. Thanks for unblocking!
cc @mikefero

Might need to rebase onto master as well.


Update master with branch 0.11

This brings in changes from the 0.11 branch and replaces master's impl of heartbeat in crust

This change is

r? @vinipsmaker
(maidsafe_highfive has picked a reviewer for you, use r? to override)


Apply some automatic fixes

There are certain classes of errors where the error points immediately to the solution. Certain language extensions are easy to turn on and obvious when required, and for certain functions you know where they live and could add an import. I'm particularly interested in cases where currently I have to go to the top of the file, as that's annoying and breaks my flow, and is usually just boilerplate. (It goes without saying, this would have to be opt-in.) Some examples of errors we could catch:
Illegal `..' in record pattern
Use -XRecordWildCards to permit this

Or:
Not in scope: `when'

Or:
The import of `Data.List' is redundant
  except perhaps to import instances from `Data.List'
To import instances alone, use: import Data.List()

One way to trigger automatic fixes would be to do something like save the file, add a ?, then save the file again. Editors could then automate that interaction if they wanted. We could have a flag --auto=? so people could change to something else.

I +1 for some --auto stuff flag
I think it makes sense for ghcid to {be aware of / handle} file modifications trigger since

it already watch for *.hs changes and have the machinery for file watching
it might affects when to :reload things / when to trigger things / when not :reload stuff.
for example, if a trigger return an exitcode of -1, ghcid could decide to consider not to reload the file (dumb exemple, just for illustration)
it's easier than configuring some buggy https://atom.io/packages/save-commands plugin specific to each editor / running manual shell commands (with platform specific tools) alongside ghcid

I personally use scripts to automate hlint + apply-refact  and stylish-haskell like
for file in **/*.hs; do
	stylish-haskell -i {file} && hlint -v --refactor --refactor-options="-i" {file};
done

I would be happy to change it to
ghcid {--on-change | --auto | --pre-reload | --pre...}="stylish-haskell -i {file} && hlint -v --refactor --refactor-options="-i" {file};"
alos, a --post trigger command would be great to have (so we can ring bell, show system notification, etc)

You can already run commands you want on a successful reload with the --test flag - e.g. --test=:!stylish-haskell -i *.hs. I'm wary about going too far down the watching and applying route - what you've got above is pretty simple, and wiring it into ghcid means it only applies for files currently loaded - not files that are not loaded due to importing an error.

indeed, and I completely forgot about ghci :!, thanks for pointing that out


Build for Android SDK 25

Hi,
Could you check if this PR is OK for you? I had troubles with latest SDK so I made quick changes but I'm not sure if it's OK.
Regards,

Hello,
Thanks for the pull request.
Can you remove the node_modules directory, the yarn.lock and local.properties files please ?
Regards.

Done

Pull request merged, and a new release 1.0.3 is available.
Thanks for your contribution.


is there a way to play a video underneath the ui? ive tried multiple ways but they don't work!

Describe your problem here.
so basically, i want to make a song that instead of using sprites, a bg and stuff, uses just a .mp4 video for graphics, with the ui on top of the video.
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, i only made a data folder for the song and put the music files in the correct folders.

Pues yo hago esto:
function onCreate()
startVideo('gunsCutscene')
runHaxeCode([[
FlxG.cameras.add(game.camHUD, false);
FlxG.cameras.add(game.camOther, false);
]])
setProperty('inCutscene', false)
end
https://github.com/user-attachments/assets/50480a82-f536-444e-8d15-77fdbd7b6925


Common uncaught errors

I went through the uncaught errors looking for patterns. I know there are some we see over and over. It would be nice to dig into these.
These are ordered by apparent frequency.
Permission / file doesnt exist / file in use issues
These just need better error messages. e.g.

https://github.com/atom/atom/issues/4797
https://github.com/atom/atom/issues/4850

Should be an easy fix, difficulty is catching all the cases.
Error from pathwatcher
Seems like a path is being watched, then something happens to that file, and pathwatcher freaks out
https://github.com/atom/atom/labels/error-from-pathwatcher
No trace; At fs.js:75

EBUSY open: https://github.com/atom/atom/issues/4735
EBUSY unlink: https://github.com/atom/atom/issues/4805
ENOENT unlink: https://github.com/atom/atom/issues/4874

Unable to watch path

https://github.com/atom/node-pathwatcher/issues/39 (windows)
https://github.com/atom/atom/issues?q=is%3Aissue+is%3Aopen+unable+to+watch+path

Seems almost entirely linux based. Not sure how to fix.
Spawn /atom/dir/atom ENOENT
Again, mostly linux. But a handful in OSX too. We need to figure out how to reproduce.

linux: https://github.com/atom/atom/issues/4505
osx: (these might be different?) https://github.com/atom/atom/issues/4538, https://github.com/atom/atom/issues/4754, https://github.com/atom/atom/issues/4538

EEXIST .atom/storage exists
Again, we need to reproduce
https://github.com/atom/atom/issues?q=is%3Aissue+EEXIST+storage+is%3Aopen

Just created another fs.js no trace bug, #5272.

There's still a large number of these issues being created, which is a suboptimal user experience and it's also hard to triage these issues because it's not really clear why some are happening and some are impossible to reproduce. For example, there's more than 30 ENOENT issues open right now:
https://github.com/atom/atom/issues?utf8=✓&q=is%3Aissue+is%3Aopen+enoent

Closing in favor of #7740


mujoco

Hi there, my Ubuntu failed to compile mujoco200,so I installed mujoco210 along with mujoco200 and encountered the same problem when testing mujoco-py. I would be grateful if you know where to modify mujoco versions.
Many thanks~

It works fine with mujoco210

Hey, could you please write a follow up on how you used mujoco 210 when it is asking for mujoco 200 when building?


Repokid should provide the ability to remove a specified permission.

Similar to the repokid find_roles_with_permission <permission> call, repokid should support a new command line function to repo a certain permission across all roles.
repokid remove_unused_permission <permission>
This would be dependent on #1 as it would require CloudTrail data.

This has been completed in #213 .
WOO HOO


Spin off container into its own repo & host it on Docker / GitHub Packages

A follow-up to #80.
We made the container work the way we want it to, but as a result that means we're doing a lot of building ourselves, which increases the time to spin up a new dev environment.
Instead, we should have a container already built, e.g blog-in-a-box:ruby2.7.3-node16.15.0 that we can pull from, so that all the building is already done when someone needs it and the container is guaranteed to do what we want (e.g. not suffer a failure from pulling packages, which could confuse an end-user).

The beginning of this work is now happening in https://github.com/excellalabs/blog-in-a-box-container/pull/1


Cache TagCollector data

Impact of the bug
ReqMgr2
Describe the bug
It looks like we are not using any caching mechanism for the releases XML data (TagCollector) used to validate CMSSW and ScramArchs during request creation (and/or assignment).
How to reproduce it
Not easily reproducible
Expected behavior
We should either use the Services caching mechanism or MemoryCache and avoid unneeded http queries. Setting the cache to 1h should be enough.
Additional context and error message
Traceback from ReqMgr2:
[23/Sep/2019:00:39:07]  Updating request "None" with these user-provided args: {u'PrepID': u'task_EXO...
WARNING:root:Http request failed, retrying once again..
WARNING:root:The cachefile <cStringIO.StringO object at 0x7f9725971a08> does not exist and the service at https://cmssdt.cern.ch/SDT/cgi-bin/ReleasesXML/ raised a error(111, 'Connection refused') when accessed
ERROR:root:About to raise exception <@========== WMException Start ==========@>
Exception Class: WMSpecFactoryException
Message: [Errno 111] Connection refused
        ModuleName : WMCore.WMSpec.WMWorkloadTools
        MethodName : _validateArgFunction
        ClassInstance : None
        FileName : /data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/WMSpec/WMWorkloadTools.py
        ClassName : None
        LineNumber : 102
        ErrorNr : 0

Traceback:
  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/WMSpec/WMWorkloadTools.py", line 93, in _validateArgFunction
    if not valFunction(value):

  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/WMSpec/StdSpecs/StdBase.py", line 1030, in <lambda>
    "ScramArch": {"validate": lambda x: all([y in architectures() for y in x]),

  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/ReqMgr/Tools/cms.py", line 224, in architectures
    return TC.architectures()

  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/Services/TagCollector/TagCollector.py", line 88, in architectures
    for row in self.data():

  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/Services/TagCollector/TagCollector.py", line 67, in data
    data = self._getResult()

  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/Services/TagCollector/TagCollector.py", line 53, in _getResult
    verb=verb, contentType=contentType)

  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/Services/Service.py", line 205, in refreshCache
    self.getData(cachefile, url, inputdata, incoming_headers, encoder, decoder, verb, contentType)

  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/Services/Service.py", line 318, in getData
    raise he

<@---------- WMException End ----------@>
[23/Sep/2019:00:39:07]  Error: Traceback (most recent call last):
  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/ReqMgr/Service/Request.py", line 193, in validate
    self._validateRequestBase(param, safe, validate_request_create_args)
  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/ReqMgr/Service/Request.py", line 88, in _validateRequestBase
    workload, r_args = valFunc(args, self.config, self.reqmgr_db_service, param)
  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/ReqMgr/Utils/Validation.py", line 101, in validate_request_create_args
    request_args)
  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/WMSpec/StdSpecs/StdBase.py", line 915, in factoryWorkloadConstruction
    self.masterValidation(schema=arguments)
  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/WMSpec/StdSpecs/StdBase.py", line 940, in masterValidation
    self.raiseValidationException(str(ex))
  File "/data/srv/beHG1909e/sw/slc7_amd64_gcc630/cms/reqmgr2/1.2.6.pre4/lib/python2.7/site-packages/WMCore/WMSpec/StdSpecs/StdBase.py", line 952, in raiseValidationException
    raise WMSpecFactoryException(message=msg)
WMSpecFactoryException: <@========== WMException Start ==========@>

@khurtado Kenyi, this is also a good candidate for you, especially because you've just implemented the same mechanism for DBS datatiers.
I didn't check, but I think there is a caching already in place by using global variables or so. If possible, let's get rid of of that as well.


GeoViewUserToDisplayToGraphicLayer -  sortedDatas : nil exception on shape

I had a nil exception (gShapeA is nil) on method graphicalOrderSortBlock of GeoViewUserToDisplayToGraphicLayer.
Maybe due to concurrent access : comes from another thread (not UI).

Normally this is fixed in #16.
Can you confirm?

@LANDAISB can I close?


Feature/new packfile parser

Needs #896
It needs tests and index writer is still not complete:

64 bit offsets
Index checksum

Some improvements can be done changing the cache to hold byte slices and index by offset. We can also skip reading headers in resolveDeltas phase.

Now it supports 64 bit offsets but needs more testing. Index checksum is already generated by the encoder.


Remove Cloud from mobile builds

This change also "short-circuits" the invite pane if there is
only one network, and instead goes directly into that network's
login flow.
I've also changed to a unified freedom-module.json for mobile
dev and dist builds, to make sure we are testing the same
behavior that we are releasing.

This change is

Inspired by @jab's #2656, I decided to try an alternative approach to this idea.

👍  from me on this approach. Just closed #2656 in favor of this.

To be clear, we don't have consensus to land this change yet, so this is in limbo for now.


Error

http2: response body closed

maybe your urls have some bad encoding chars or something ..
trynna fix this condition later inshallah

hi
# runtime/internal/sys
/usr/local/go/src/runtime/internal/sys/consts.go:13:7: StackGuardMultiplier redeclared in this block
        /usr/local/go/src/runtime/internal/sys/arch.go:27:7: other declaration of StackGuardMultiplier
/usr/local/go/src/runtime/internal/sys/consts.go:16:7: DefaultPhysPageSize redeclared in this block
        /usr/local/go/src/runtime/internal/sys/arch.go:36:7: other declaration of DefaultPhysPageSize
/usr/local/go/src/runtime/internal/sys/consts.go:20:7: PCQuantum redeclared in this block
        /usr/local/go/src/runtime/internal/sys/arch.go:40:7: other declaration of PCQuantum
/usr/local/go/src/runtime/internal/sys/consts.go:23:7: Int64Align redeclared in this block
        /usr/local/go/src/runtime/internal/sys/arch.go:43:7: other declaration of Int64Align
/usr/local/go/src/runtime/internal/sys/consts.go:30:7: MinFrameSize redeclared in this block
        /usr/local/go/src/runtime/internal/sys/arch.go:50:7: other declaration of MinFrameSize
/usr/local/go/src/runtime/internal/sys/consts.go:34:7: StackAlign redeclared in this block
        /usr/local/go/src/runtime/internal/sys/arch.go:54:7: other declaration of StackAlign

it`s problem in my go? thx.


publish the latest version on bower

current version is 0.0.4 on bower.

Running bower info returns the latest 0.0.5 version. Is it different for you?

bower info is same with the screenshot. But there is the different of the "getPolylineLength" function when I checkout the source by bower install

Just created a new empty directory and ran bower install. Inspected the source and found the same code there. Is there a problem animating polylines for you?

Same issue for me, it's not 0.0.5 after bower install, but I set the version is 0.05 in bower.json.
Prolblem is polyline doesn't draw on Safari

Okay, thanks for the update. I'll investigate more.


Update line-height behavior to respect token value, size headings relative to body text

Why:

So that assigned line-heights match expectations based upon the available token options, not influenced by either font family or scale
So that heading line-heights can be smaller than body content, but only in the case that the actual value would be greater than that of body text (and in all other cases, using the body line-height for headings)

Note that this diverges slightly from original decisions to use a line-height value of 1.33 for headings. USWDS includes a line-height token for 1.35. Previously, due to normalization, this value would never take effect. However, with this pull request also removing the normalization behavior, the 1.35 actual value for headings can be used. Since this is very close to 1.33, and avoids circumventing USWDS tokens, would we be okay with this value, or should we force it to 1.33?
Live preview URL: https://federalist-2f194a10-945e-4413-be01-46ca6dae5358.app.cloud.gov/preview/18f/identity-style-guide/aduth-normalize-heading-line-heights/utilities/typography/
Effective difference in line-height:

Heading
Before
After

h1
1.4
1.35

h2
1.4
1.35

h3
1.4
1.5

h4
1.4
1.5

h5
1.4
1.5

h6
1.4
1.5

Screenshots:

Before
After

Okay w/ 1.35 as the value for both H1 and H2.
@anniehirshman-gsa Any preference?


[NOMRG] Replace deprecated AutoNonVariableTypeMode with AutoDispatchBelowADInplaceOrView

Fixes #3771

I've kicked the builds again and looks like the failures are due to old PyTorch packages being picked, see for example
https://circleci.com/api/v1.1/project/github/pytorch/vision/579783/output/108/0?file=true&allocation-id=609f9b1c5c8d7a75b0bdb83a-0-build%2F504B8F3A
which shows
    pytorch-1.9.0.dev20210415  |py3.8_cuda10.1_cudnn7_0       886.8 MB  pytorch-nightly

or https://app.circleci.com/pipelines/github/pytorch/vision/8114/workflows/a335771b-a7fb-4138-ba0d-d01c8a10cad4/jobs/579742
which shows
    pytorch-1.9.0.dev20210415  |py3.8_cuda10.1_cudnn7.6.3_0       676.4 MB  pytorch-nightly

@seemethere is that a known issue that some of the PyTorch nightlies are as old as 1 month old?

I think it's the fact we use the cuda10.1 version instead of the 10.2 version which is now officially supported.

So if we are dropping support for CUDA 10.1 in Pytorch, then we should remove it from CI?

Yes, I think we should replace 10.1 with 10.2.
@seemethere Is this something you could help us with? I had a look and it seems that this requires knowing exactly which image versions we should use.


Add support for futureProofEnums with enumsAsConst in @graphql-codegen/typescript

Description
Currently setting futureProofEnums with enumsAsConst has no effect. This commit adds support for this combination so the type exports include the %future added value string.
Related #9551

Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Added an additional test case to the typescript tests.
Test Environment:

OS: macOS 13.4.1
@graphql-codegen/typescript: 4.0.1
NodeJS: 18.16.1

Checklist:

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

Does this add support for enumsAsConst in the client preset?

@paynecodes I don't beleive so, looking at the preset it doesn't specify that option. Happy to add it, but given this has been open since July, I'm unsure if/when it might be merged and released.


Fix remote profile

Please provide a description of this PR:

Fix inconsistent usages of global.externalIstiod (this setting should only be used in the primary cluster and should not affect remote clusters at all)

Modify the charts so that the istiod service is always called istiod, even in remote clusters. This simplifies things and prevents bugs, such as referring to the wrong service name in webhooks.

Modify the charts so that .Values.istiodRemote.enabled determines whether  istio-reader-clusterrole gives access to configmaps and webhooks.

Hi @luksa. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

/ok-to-test

@bleggett Yeah, I had a feeling that was the case - I was confused why the flag was used on both sides. I'll remove the flag. What should we do with the Service name? IMHO it should be istiod-remote so that it's immediately clear that it points to an external control plane. Of course, we also need to update the reference to the service in the webhook. You agree?

Hmm, maybe it's safer to always use istiod as the service name. If we use a different name based on whether istiod is local or not, we'll always have to keep this in mind whenever we reference the service by name (e.g. in the mutating webhooks).

@bleggett Yeah, I had a feeling that was the case - I was confused why the flag was used on both sides. I'll remove the flag. What should we do with the Service name? IMHO it should be istiod-remote so that it's immediately clear that it points to an external control plane. Of course, we also need to update the reference to the service in the webhook. You agree?

I think we have tests that expect the service naming to go both ways (-remote suffix vs no), and I think that's all the flag really controls, meaningfully.
I have no preference, I would pick whichever one requires the least integ/doctest churn.

@luksa: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
5fcfd49afb1a7e2178f15bf51b666a6ce650d5fe
link
true
/test integ-distroless

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

/retest

@luksa: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
eb2e707bafe77d8ba3f36ccbf117299f9bd381be
link
unknown
/test unit-tests-arm64

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

/retest