Prepare to CAPI v1alpha4

Each CAPI infra providers are required to make some changes before taking CAPI v1alpha4 in.
CAPI community is working on the document to list the changes required in provider side when moving from v1alpha3 to v1alpha4.
We can keep track of the work that needs to be done in CAPM3 in this issue.
/kind feature
/priority important-soon

/remove-lifecycle stale.

/remove-lifecycle stale

This can be closed since the CAPI uplift PR #167 got merged already.
/close


Make counterfactual_consistency work for discrete outcomes

Specifically incorporate accuracy because MSE doesn't work for classification.

It actually should work pretty easily. Since our significance test is non-parametric (randomization inference), we don't have to worry about any distributional assumptions. The only thing we need to make work is not assuming linearity. The current uses OLS, which assumes linearity. We need to replace the OLS estimation with an ELM.

We should actually change our approach here. The current methods assume that there might be a violation of this assumption because there might be multiple treatments or controls. For example, if there is one treatment group in the dataset but there were actually multiple treatments administered then this would be a violation. The method tries to generate what could be alternative treatment statuses by using Jenks breaks and comparing the model fit with the Jenks break treatment groups vs the one in the dataset. Besides not being able to handle continuous treatments, it also only accounts for one potential violation of the counterfactual consistency assumption. A simpler, more general, and probably better approach is to simulate potential outcomes that differ from the outcomes in the dataset and reestimate models with that data to see how much this changes the results.


_reactNativeDeviceInfo.default.getUniqueID is not a function

Bug
_reactNativeDeviceInfo.default.getUniqueID is not a function
Library version: 3.0.0
Steps To Reproduce
just use DeviceInfo.getUniqueID() in your app
Workaround
Downgrading:
yarn add<EMAIL_ADDRESS>

The name of the method changed, please see the migration guide https://github.com/react-native-community/react-native-device-info/wiki/V2-to-V3-Migration-Guide

Still facing issue.
"react-native-device-info": "2.3.2",

That version is old and I will not troubleshoot it, sorry. The migration guide and the docs contain how to do it for the current release. If you need information on older releases you will have to ask github to show you the code for older releases then look at the docs https://github.com/react-native-community/react-native-device-info/tree/v2.3.2

you can use getUniqueId instead of getUniqueID

Still getting the same issue ^5.3.1, calling DeviceInfo.getUniqueId().then(uid => info.uid = uid)

Try this
import DeviceInfo from 'react-native-device-info';
constructor(props)
{
super(props);
this.state = {
deviceId:''
};
}
getId()
{
var id = DeviceInfo.getUniqueId();
this.setState({ deviceId: id, });
console.log("Device Id",this.state.deviceId)
}
Thanks
G.Neeraja
On Thu, Nov 28, 2019 at 5:24 PM Mike Rodham<EMAIL_ADDRESS>wrote:

Still getting the same issue ^5.3.1, calling DeviceInfo.getUniqueId().then(uid
=> info.uid = uid)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/react-native-device-info/issues/785?email_source=notifications&email_token=AITEOFPSZIKCMOK3Q5RKH3LQV6WPBA5CNFSM4IWUP532YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFMMEKY#issuecomment-559465003,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AITEOFOK2TEHNMRTHKQ3F2DQV6WPBANCNFSM4IWUP53Q
.

you can use getUniqueId instead of getUniqueID

This work for me!!

Use getUniqueId insted of getUniqueID . It will work.


TypeScript typings missing in "keystore" branch

The bundled TypeScript typings exist in the default branch, but not in the "keystore" branch. The typings need adding into this branch aswell.

Hi @davidfarinha, PR #107 should address this issue. I'll take some time later to review the keystore branch and merge it into master if needed, I'm not even sure why it still exists

Awesome, thanks. Also it was my understanding that the "keystore" branch differs from master (uses keystore instead of shared-prefs). Is this not correct? Are there any differences between these branches?

https://github.com/mCodex/react-native-sensitive-info/compare/master...keystore?expand=1
Here we can see the diff between the two branches, and it looks like there's only a few fixes in master that are not in keystore, maybe it was merged at some point but not deleted.
@mCodex are we missing something here?


[Seeking Help] Dynamic Table Sizes

Oz is primarily based on creating all of your elements up front. Say you have the following row of a table:

Label
Input1
Input2
Input3

static_text
text_field
select_list
text_field

If we want to fill this out or validate it in anyway, we just define each of the 4 fields. No problem
However, we fill the first row and now it looks like this:

Label
Input1
Input2
Input3

static_text
text_field
select_list
text_field

static_text2
text_field2
select_list2
text_field2

If you use any sort of loop or enumerator to create elements for each and every possible field, you could wind up with hundreds of extra fields that you don't need to be validating every time. It's usually enough to validate that the next row isn't active/present.
Making it based on the keys within INPUT_DATA feels like it goes against some of Oz's patterns - namely the ability to land on a page with one data target (thus hitting create_elements) but then filling the page with a different one.
I feel like the approach should be a TableElement of sorts, but again, struggling to think of how to stick to Oz's patterns of creating all the elements of the page, but yet only validating the rows we care about.

I'm leaning toward the concept of a "validation reliant on" property. Takes an element and will only run the validation step of the current element if the one it relies on is active.
Extend ElementGroup to have a method to apply this to all elements in a group, and now you can create as many table rows as you want, but it will only care to validate a row if the element it relies on is active.
This would still validate that Row 3's elements in the above example would be deactivated, but it wouldn't care about a Row 4, 5, 6, etc.


Room screen: Hide expanded header on scroll down

fixed in
https://github.com/vector-im/vector-android/commit/328c1d50c48019ae59bc9a47a6b30880ef78b39f


Fix: S3 Bucket does not support attribute type Arn in Fn::GetAtt

Fixes #3387

Coverage decreased (-0.2%) to 94.17% when pulling aa3c4b365d4c03ab146ab88910f2e67316fac717 on bpandola:fix-3387 into 99556620a95da8fbfc7bca71e1a904f5f54f08be on spulec:master.


Implement transport

Hey there,
I'd love pino-dev to implement the v7+ transport API (https://getpino.io/#/docs/transports), allowing for programmatic use and thus making it a drop in replacement for pino-pretty.

Hi! With v3 of pino-dev there's now support for v7+ transports - thanks for the suggestion! 👍


Add actonc docs: rendering of documentation from docstrings in source files

It would be cool if actonc could parse a source file or project and output documentation in a pretty format.
We obviously already parse all the code when reading an .act file and I assume that we don't throw away docstrings but keep them in our internal syntax tree representation. So I guess this is more or less about writing a filter for the syntax tree, filtering out most of the stuff just leaving a sort of skeleton.
I would like to use orgdown (https://gitlab.com/publicvoit/orgdown) for the docstrings, that is, inside of a docstring, we should think of the content as being in orgdown format. Orgdown is like markdown but based on org-mode (a very popular Emacs mode). "org-mode" means both a syntax as well as the actual Emacs mode with all its code etc. Unlike Markdown, which might have the most unintuitive syntax on the planet, orgdown actually makes a lot more sense... in my opinion. Anyway, Haskell has the pandoc library which I think we can use to consume org and output HTML.
I think we act on a per module basis, so parse a .act file, then filter the content down to a skeleton preserving the structure, something like

module hejsan

function apa

the docstring

function bepa

another docstring

actor Foo

docstring for an actor
method FooA

docky stringy

And from there we convert the whole thing to an orgdown document, like:
* Module =hejsan=
** function =apa=
the docstring
** function =bepa=
another docstring
** actor =Foo=
docstring for an actor
*** method =fooA=
docky stringy

then pass to pandoc -> HTML or some other output. I think it would be pretty cool to output man pages as well, since those can be nicely rendered to a terminal.
Alternatively, maybe it is easier to output our skeleton doc AST to pandoc AST, for which there is a JSON representation... I guess we'd then call pandoc on each docstring to produce pandoc-json, then glue these together to form a larger json of the whole doc, then feed back to pandoc to produce the final output.

Good idea! I could make an attempt at this, unless you want to do it yourself.

@sydow feel free :) this is way over my head ;)

I forgot to include type signatures in the example above. We obviously should, so I added that. Also added in an example .act file to better illustrate the mapping from actual acton source to AST to orgdown.

@sydow not sure over whether to combine with dump or not. At one point I suggested that .ty files should contain docstrings because we would be able to read out documentation even if modules were distributed as binaries.... but, we pretty much abandoned that idea because the plan is for module/package management to deal with source code, so we are never in a situation where we only have a .ty file and not the source .act file. Thus, I dunno what the benefit would be of using the .ty file rather than the .act file.
On the other hand, I have no real strong arguments against it, so if you see a clear benefit to adding docstrings to .ty and using the dump command to render docs, then maybe that's the way forward.

I think that I jumped onto this too quickly. There are several issues to sort out:

I don't think it is advisable to allow users to write orgdown markup in docstrings and also use orgdown to mark up the whole document. This seems to be an  invitation to produce a confused document structure. There are many proposals for how to markup docstrings; maybe one should explore these more.
I don't think we should use header levels to indicate hierarchical structure. Headers of different levels are not always easy to distinguish (e.g. in plain HTML) and there is no hierarchy indicetion otherwise (e.g. no indentation). Nested lists seem better?
In your type signatures you retain the name of parameters from the source code. This may be an advantage from a documentation point of view, but they are not preserved by the type inference mechanism, so we would need to combine source code with results of type inference, doable but not trivial, in particular with the full freedom of position and keyword parameters, optional parameters and default values.

I won't argue with the first two points, they seem valid to me but I have no real insights into the problem.
Point 3, though, is actually a small misunderstanding. We really do preserve parameter type names during type inference, so that a function can be called with explicitly named arguments if so desired. It's just that the technique that would allow the same parameters to also be called using positional arguments isn't fully implemented yet, so type inference takes some (confusing) short-cuts with these for the time being. But since the issue discussed has a slightly longer timespan I thought I should point out what's actually in the pipe.

Isn't that the beauty of it? Sure it's enough rope to make a cluttered doc but also enough power to render very elegant things. I believe Haskell Haddock supports just such section headings.
I don't understand the difference between header levels vs nested lists. How it is rendered with HTML is a matter of CSS. Semantics of the document are orthogonal to how we indent or otherwise show hierarchies with HTML? so section headers vs nested lists seems quite similar to me.
Even if some info is missing, e.g. we only have name but not inferred type or only inferred type but not name, we can improve that later. While it is more important to get the other bits, with regards to orgdown etc correct, since then people can start writing docs in modules from day 1 and it'll look sort of nice, I still feel we can give ourselves some space to experiment. We can try this out and see how it feels.. We're likely going to make some changes as we go along but the fewer the better.

Here's a direct link to how to deal with section headings in Haddock https://haskell-haddock.readthedocs.io/en/latest/markup.html#section-headings
it happens to look just like org-mode heading, i.e. using asterisk to denote header1, 2, 3 etc.
If we just have a standard way of rendering a function, then isn't this all fine? Or is it specifically rendering a function/method as a heading that you oppose? I guess it could maybe be something else?

Yes, there is Haddock markup for section headings of various levels, so the user can structure the documention using this markup; but these headings are also the only ones that occur in the resulting documentation. I understood your proposal as imposing a structure on the document where the module gets a level 1 heading, each top-level declaration a level 2 heading, each method in a toplevel class/actor a level 3 heading etc. I think that would interact strangely with possible user-provided headings.
What makes Haddock work so well is partly that the document structure is guided by the top level module's export list, which can order and group (using (sub)headings) documentation of declarations in a system regardless of the code structure. Each individual declaration produces its type signature and its "docstring", but not some document-level structure element.
I am a big fan of Haddock, but I thought we were aiming for something much simpler. Haddock has a deep understanding of Haskell and its module system, which makes it possible to produce very elegant documentation. Haddock also produces its own CSS files, LaTeX style files etc. But the Haddock github repo contains 24000+ lines of Haskell code...
I would be in favour of having, as you say, a standard way of rendering a function definition, which does not involve any high-level document structure element, and allowing "docstrings" also in between top-level definitions, for providing such structure, e.g. in the form of headings. You may have had this in mind in some comment above.
Preferrably we would also have accompanying CSS files, but I do not know how to approach this if we just produce orgdown and let pandoc or some other tool do the translation to HTML.
This would need an illuminating example, but that must wait until tomorrow.

@sydow hmm, ah yes, my thinking was indeed that functions, actors, actor methods etc would produce a section heading but that the overarching structure could be controlled or modified by the user. Further, that we wouldn't have to deeply understand the content of docstrings but just "glue some stuff together". I hadn't thought that through; it might be that we would need to have some understanding of the docstring. However, I believe that is true regardless if we go with functions as section headers or as nested lists; the dilemma is the same, if someone has written a function docstring, it becomes relative to its surroundings. If it is a list;
"""There are a few groups of functions:
- the foobars
def foo():
    """My foo function is good for:
    - eating pie
    - baking cookies
    """
def bar():
    """BARRRY
    """

"""
- the bafooza
  - which are good for doing the foozba
"""

def bafooza():
    """BA
    """

It is by no means a hard requirement that functions become section headings. It was just my initial suggestion since it felt natural but as I tried illustrating above, I don't think changing to nested lists fixes it.
But perhaps we should just revisit what we set out to do. I did include an example of a docstring that contains section headers (though conveniently left out how the complete output document would look like). Maybe we just should not encourage adding extra headers, or if you do, that it should only ever be on a top level and thus a level 2 heading (** heading) or some guideline like that?
I'm not sure how much guard rails we should aim to provide, there will always be ways for users to mess things up; I think rather we should just focus on making it simple to produce good documentation.
As for HTML and CSS, I mostly want to stay away from it. pandoc will render HTML from org and I want to influence that as little as possible (I don't even know if/how it can be configured). CSS is naturally something we can do, but I'm happy to postpone that to another year ;)  our focus should be on producing a good source (orgdown) that is semantically sound.

My nested list thoughts were mainly for methods in classes and actors. Documenting them in a list subordinate to the class/actor just seems much clearer than as headers with one more asterisk.
I probably also disagree about keeping away from HTML and CSS as much as possible. I don't think it is by accident that Haddock produces HTML or LaTeX directly and not via a common lightweight markup language. We want to produce documents with very specific concepts, such as that of a function definition (with its parts name, parameter names, type and docstring).  The markup should know of these concepts, allowing to choose a suitable rendering. Then it is not enough to use only the limited structuring tools of orgdown. In HTML we have at least div's with class attributes, in LaTeX we have many more possibilities.
Maybe we could talk a bit about this tomorrow, if there are not other more urgent topics.

I think the biggest benefit to headers is that everything below the header automatically renders rather nicely. That is, if someone put a list in a function docstring, that will come out alright. If the list of functions is an org list, then another list in the function docstring will be messed up. Having org heading for functions allow more things in the function docstring.
orgdown has ways of passing through parameters to HTML export, so for example you can set CSS class on stuff, thus I think our standard export of functions etc can render org only and rely on pandoc to do the necessary.
I'd love to talk about it. I wanna talk about network IO interfaces tomorrow. Maybe we can try to keep that short (hah!). If nothing else, maybe you and I can find another slot to discuss this further!? :)

Now, the above example using org works but I'm not sure if it's the best way. We have function docstrings, where the idea is that they are in orgdown format. We want to join those docstrings together with documentation that we render from the source code, e.g. function signatures.
I see two main approaches, first one I originally suggested is:

render function signatures as org
join function signature org with docstrings into one big org doc
use pandoc of org -> html

This way, we don't have to deal with HTML at all. We need to be aware of what it will look like etc to get CSS right, but don't have to write HTML. I thought this was the natural and best choice...
I noticed pandoc has support for rendering fragments, which means it is likely just as easy to:

use pandoc to render individual function docstrings to HTML
render function signatures etc to HMTL using custom code we write
join function signature HTML with docstring HTML fragments to form entirety of HTML doc

The latter approach gives us better control of the HTML. The downside is that it is HTML specific. I had a dream about if we first assembled a complete org document we would be able to use pandoc to export it to HTML but also to groff / man pages and perhaps other formats too. If we have HTML specific stuff then I suppose we also need to write groff specific stuff if that's a format we want to support etc etc etc.
@sydow what do you think?


About OpenOCD extensions

Hi, all,
It seems standard OpenOCD can not access ICCM/DCCM, how to enable it?
There some information mentioned here, Anyone has the detail information?
Thanks.
SweRV_CoreMark_Benchmarking.pdf Page 7:
"
We added abstract commands (based on RISC-V Debug
specification 0.13) to access the ICCM and DCCM
(leverage and extend CREX OpenOCD work)
"

A few things need to be added:

A way to instruct the tool to use memory abstract commands, depending on address (for PIC DCCM/ICCM address ranges) for data dumps/updates. these accesses must be of word size and aligned. Read/Modify/Write operations should be used for smaller sizes data updates.
the same for SW breakpoints settings in ICCM
add IC invalidation code for SW breakpoint setting with a CPU dmst (0x7C4) SCR via abstract command.

See also
https://github.com/chipsalliance/Cores-SweRV/issues/65#issuecomment-657990440

Codasip has a patched OpenOCD version for SweRV that has proper support for accessing the internal memories: https://github.com/Codasip/swerv-openocd. If you'd like to try it, please see the README for instructions.
Thanks!


Fix inspections around tags closing with /}

For example, if an unknown tag is closed by /}, it says Malformed tag, missing closing }, but it has to say Unknown tag {tagName}

I am sorry if my report is not related to this issue, but I hope it is.
Some time ago we investigated (in the first version of your plugin updates) why my IDE freezes on a larger files.
We have come to a conclusion that it freezes due to the unclosed unpaired variant of the label macro. I have added the closing slashes to my code and everything worked fine.
However, the current 1.1.1-RC2 version probably behaves differently.
The closed variant is incorrectly formatted, for example, inside the condition. Plugin says "Malformed tag. Missing closing }":
{if $foo}

     {label bar /}

{/if}

Unclosed variant is well formated:
{if $foo}

         {label bar}

{/if}

@jaroslavlibal it is working correctly in 1.1.2


Update README.md

Fix README.md code examples for make vm-define-image, make vm-create-image-template and make vm-build-image that have now been parameterised with TEMPLATE_PATH.

Thanks for this, and sorry for the delay in merging (I think your PR came through while I was on vacation and then dropped from my radar). Anyway...thanks!


Add QA tests for FAQ page

Filled in some basic tests for identifying that FAQ page is functioning.

Modified structure for FAQ page tests. (Those still needing work are commented out.)


com.esotericsoftware.kryo.KryoException: java.lang.UnsupportedOperationException

SourceFunction自定义deserializer , ForwardDeserializeSchema是复制的源码.
private static class ForwardDeserializeSchema implements DebeziumDeserializationSchema {
    private static final long serialVersionUID =<PHONE_NUMBER>832211228L;

    @Override
    public void deserialize(SourceRecord record, Collector<SourceRecord> out) throws Exception {
        out.collect(record);
    }

    @Override
    public TypeInformation<SourceRecord> getProducedType() {
        return TypeInformation.of(SourceRecord.class);
    }
}

Closing this issue because it was created before version 2.3.0 (2022-11-10). Please try the latest version of Flink CDC to see if the issue has been resolved. If the issue is still valid, kindly report it on Apache Jira under project Flink with component tag Flink CDC. Thank you!


update ansible galaxy versions

The last version at Ansible Galaxy is 2.2.7 and it not has the last version of MongoDB v3.4.

+1. That or mark the project as unmaintained since open PRs are no longer receiving feedback or being merged.

+1

Missing 3.6 too now


Fixed class path missing for haxelib use

Not sure if this is the only way to fix this issue, but I went to use this in a headless application whilst installing via haxelib and wasn't able to access the package!

Thanks for that, I've been using it exclusivly with lix and a local checkout so forgot to create the haxelib file.


Ineffective generation of the project graph

I applied the plugin on a project that has 60 modules and is badly modularized (it has more than 10 levels). The generation task failed to finish under 40 minutes.
I checked the code and noticed that the algorithm can visit a specific module more than once. It goes through all the paths in the graph and collects the relations between modules and their levels. I suggest splitting this search to two searches.

Search the dependency graph in the depth and visit every node just once. Along the way collect the relations between the nodes.
Search the dependency in the breadth and collect the node levels.

This should have complexity of O(n), where n is number of modules.

@ivancarras Any news? 🙂


Add properties to each test. List of tests

Is there a way to add custom property (for example LABELS or WORKING_DIRECTORY) to each of the tests, added by pytest_discover_tests?
Looks like my tests want to be launched in the specific directory + I want to separate long-running python from gtests of my project with a labels. The ability to hack-into and get the list of all tests might be really helpful, until every feature is supported natively with this function.
Thanks!

@pprettysimpple Apologies for the delayed response. Currently, you can set a WORKING_DIRECTORY or a custom ENVIRONMENT as an option (see API Reference), but custom properties are not available yet.
I'm working on it as part of this PR: https://github.com/python-cmake/pytest-cmake/pull/46
You should be able to add custom PROPERTIES as follows:
pytest_discover_tests(
    PythonTest
    ...
    PROPERTIES
        TIMEOUT 120
        LABELS "unit_tests;fast_tests"
)

Please let me know if this meets your requirements!

Custom properties were added as part of v0.11.0, so I'm closing this ticket for now. Please re-open it if needed.

thank you, I think it fits our use case. I will try it out in a few days


vue parsing error

[Steps]

Install @nuxtjs/eslint-config-typescript: "^6.0.1" and @typescript-eslint/eslint-plugin: "^4.28.1"
Extends in eslint configuration file
extends: [
'@nuxtjs/eslint-config-typescript',
'plugin:@typescript-eslint/recommended',
]
[Currrent]
Generate vue parsing error(ref screen shote attach here

[Expect]

Should parse .vue file also

We temporarily closed this due to the lack of enough information. We could not identify whether it was a bug or a userland misconfiguration with the given info.
Please provide a minimal reproduction to reopen the issue.
Thanks.

Why reproduction is required


Update using-azure-active-directory.md Fixed top table

Fixes https://github.com/MicrosoftDocs/sql-docs/issues/9688.

@David-Engel

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

This change doesn't make sense.
The previous table layout was correct. There is a keyword name, its list of possible values, its default value, and a description column. For the Authentication keyword, the description column contains another table expanding on the values and their descriptions.
With your changes, you have duplicated the keyword across multiple rows for each possible value. This is not the way the table was meant to be laid out.

Yes, I agree. If we can make the first column not repeat that is better. I felt the existing layout was hard to read. Feel free to ignore the PR if you disagree. Thanks.

If you use the "Expand table" link, the existing layout looks much better:

I'd prefer to keep the existing layout.

You are right, the expand table makes the layout look good. Thanks.


sharable directories

Make directories shareable by automatically zipping the directory. currently this action throws an error:
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: EISDIR: illegal operation on a directory, read
    at Error (native)

Making zipping possible, the current directory could be shareable by typing share .
After successfull sharing or timeout the archive should be deleted.

issue fixed by zipping the file beforehand and piping the compressed file to share-cli
tar cf - . | share -n "filename.tar"


[Bug]: VectorStoreIndex no longer working

Bug Description
I updated my packages and now for some reason VectorStoreIndex is not working. Before, I was able to vectorize and see the progress on the chunks being vectorized when running VectorStoreIndex but now it does not even do that.
After the code ran, I was able to see the vectorized content content stored in the chroma db but since nothing is being vectorized, it is not storing the content. Could it be an issue with the packages that I just updated?
Code:
from llama_index.core import VectorStoreIndex, SimpleDirectoryReader, StorageContext, load_index_from_storage, ServiceContext
from llama_index.llms.openai import OpenAI
from llama_index.core.indices.query.query_transform.base import DecomposeQueryTransform
from llama_index.core.query_engine import MultiStepQueryEngine, CitationQueryEngine
from llama_index.core.agent import ReActAgent
from llama_index.core.tools import QueryEngineTool, ToolMetadata
from llama_index.llms.openai import OpenAI
from llama_index.core import Settings
from llama_index.legacy import LLMPredictor
from llama_index.embeddings.openai import OpenAIEmbedding
from llama_index.vector_stores.chroma import ChromaVectorStore
db_path = "chroma_db"
embed_model = OpenAIEmbedding(model="text-embedding-3-large")
print('Vectorizing Content')
db = chromadb.PersistentClient(path=db_path)
azure_documents = SimpleDirectoryReader("./Azure Docs").load_data()
azure_docs_collection = db.get_or_create_collection("azure_docs")
azure_docs_vector_store = ChromaVectorStore(chroma_collection=azure_docs_collection)
azure_docs_storage_context = StorageContext.from_defaults(vector_store=azure_docs_vector_store)
azure_docs_service_context = ServiceContext.from_defaults(embed_model = embed_model, chunk_size = 1000, chunk_overlap = 20)
azure_index = VectorStoreIndex.from_documents(azure_documents, storage_context=azure_docs_storage_context, service_context = azure_docs_service_context, show_progress=True)
print("Vector Content Loaded")
Version
0.11.18
Steps to Reproduce
Updated my packages to these versions:
llama-cloud                              0.1.4
llama-index                              0.11.18
llama-index-agent-openai                 0.3.4
llama-index-cli                          0.3.1
llama-index-core                         0.11.18
llama-index-embeddings-adapter           0.2.2
llama-index-embeddings-openai            0.2.5
llama-index-finetuning                   0.2.1
llama-index-indices-managed-llama-cloud  0.4.0
llama-index-legacy                       0.9.48
llama-index-llms-azure-openai            0.2.2
llama-index-llms-gradient                0.1.2
llama-index-llms-mistralai               0.2.7
llama-index-llms-openai                  0.2.16
llama-index-multi-modal-llms-openai      0.2.2
llama-index-postprocessor-cohere-rerank  0.2.1
llama-index-program-openai               0.2.0
llama-index-question-gen-openai          0.2.0
llama-index-readers-file                 0.2.2
llama-index-readers-llama-parse          0.3.0
llama-index-vector-stores-chroma         0.2.1
llama-parse                              0.5.10
llamaindex-py-client                     0.1.19
Then I ran the code
Relevant Logs/Tracbacks
No response

Your code seems pretty outdated. Here's what works for me, reproducible in google colab
https://colab.research.google.com/drive/1sQQw-A1PvWozajDqZeI_WUzRu9GPo9AV?usp=sharing
ServiceContext is removed in latest versions. Using Settings to control global defaults, or pass in things like embed_models and llms to local constructors
I showed both ways in the notebook

Your code seems pretty outdated. Here's what works for me, reproducible in google colab https://colab.research.google.com/drive/1sQQw-A1PvWozajDqZeI_WUzRu9GPo9AV?usp=sharing
ServiceContext is removed in latest versions. Using Settings to control global defaults, or pass in things like embed_models and llms to local constructors
I showed both ways in the notebook

Awesome! Thank you so much. Once I get the issue of cannot import name 'Settings' from 'llama_index.core' (unknown location) resolved I will use that.

Hmm, a fresh venv may help with that


[INVOCATION] There should be an option to pass headers during invocation.

At the moment, we can pass the body while performing service invocation. Headers cannot be passed. I believe the invoke function should also accept a headers parameter so that users can pass headers.

Duplicate https://github.com/dapr/js-sdk/issues/218

@shubham1172 I think the #218 issue is not solved yet. right?

That's right, @salmankhan-prs.

@shubham1172  This is something that I can figure out.

A PR is always welcome! You can refer to https://github.com/dapr/js-sdk/pull/257, it was closed due to inactivity and some comments were to be fixed.


Optimize For Ad-Hoc Usage

First of all: Thanks so much for this nice tool! I use it a lot.
It would be so nice if this tool is more optimized for single-time ad-hoc usage to quickly share a screen recording.
Currently, doing a screenrecording requires many clicks:

Start the tool
Click on Recorder
Click on Record
Click on Stop
Click on File
Click on Save as
Click on Save
Paste the recording into the github issue editor (which is what I usually do with recorded gifs)
Click on Exit
Click on Yes ("Are you sure that you want to exit?")

Ideally, my flow would look like this:

Start the tool (or press a global hotkey)
Click on Record
Click on Stop
Click on Export
Paste the recording into the github issue editor
Exit screen to gif without questions

To eliminate step 2 from the original list, you can set-up the application to start in recorder mode (Application -> Start with: Screen recorder). To eliminate step 10 you can uncheck "Ask me before closing the editor (if there's a project opened)." in Editor->General.
For the faster save/export workflow I don't know if there's anything at the moment.
For future version, I was thinking, maybe it could be done as one of the new automated tasks that run as part of the processing done when the frames are loaded? I think it could fit into the existing framework nicely.  WDYT @NickeManarin? Does it make sense to have Export/Save as one of the automated tasks?

The ideal for the near future is to compartimentalize the Editor, separating core features, leaving it possible to bypass it by using a simple workflow:
Recorder -> Save As, won't allow any edits at all.
Recorder -> Simple Editor -> Save As, will allow playback trimming and perhaps resizing.
Recorder -> Complete Editor -> Save As, always set as default.
Automatic tasks should work for all cases, if enabled.
Now, what I have in mind to do first is to migrate to .NET 5/6, then start the editor rework/redesign (that is going to take a while), then improve workflow.
The new editor should have support for multiple layers (this will need the creation of a timeline element, I already started), improve rendering (allowing a quality slider like Premier Pro, 100% -> 50% size), separated panels from main view, proper action stack for things like moving layers, altering properties, etc.
The list goes on. I just need time. ;)

Btw, the whole project system will work too. The editor will work directly on top of a project file (*.stg), still automatically created (with cache settings still in place).

Sounds great!
If you already rework/redesign this tool - what are your thoughts on supporting objects?
Currently, when adding some text, it seems you immediately render the text to all images (which I guess is why it takes so long). Couldn't you just keep track of the text object and render it on demand? That way, I could easily edit and move the text.
Ideally, properties of an object could depend on the time.

Yes, that's the main reason for the rework/redesign. To add support for layers and objects, with rendering on remand.


Dependency array does not trigger re-render on string

Hey 👋
Thanks for the great library 🙏
I've been playing around with it and found that the dependency array of useControls does not seem to trigger a re-render with primitive values? Hopefully not misusing it because it seems to work with options.
Here's a reproducable CodeSandbox. Notice that clicking the button does not change the input value:
https://codesandbox.io/s/crazy-feather-5u05k?file=/src/App.js
Thank you for taking a look!

Hi @raunofreiberg, the deps array in useControls only updates the settings, not the value. There's a set function for this. I've amended your sandbox so that it's clear for you:
https://codesandbox.io/s/zen-elgamal-lfx46?file=/src/App.js


Can't push to sandbox

when I try to push I get this message
remote: Permission to newtfire/textEncoding-Hub.git denied to argynarg.
fatal: unable to access 'https://github.com/newtfire/textEncoding-Hub/': The requested URL returned error: 403

@argynarg Sorry I didn't see this until now! It has been the busiest, most laborious Labor Day ever! But I think I see the problem: You need to accept my invitation to join this repo so that you will have permission to push to it. I just sent you a fresh invitation: You want to check your email that you used to set up your GitHub account, and I think you'll see it. A few other students have yet to accept the invitation, so at this point that includes:
@argynarg
@bwm5473
@natalyamyers
@san5281
@thompsonjosh24
All of you: go check your email and accept my invitation so you can push to this repo! :-)

I am very sorry, but I did not notice the invitation in my email before it expired.

@bwm5473 Hang on! I'll send you another invitation right now. Make sure you check the email you used to create your GitHub account...

@bwm5473 Okay! I've just sent you a new invitation. Did you receive it? Click through to "accept" the invitation.

Yes. It's taken care of now, thank you very much.


View full list of who your trust flows to, sorted by most trusted.

@plexish Just to follow up on our discussion in the discord, since it takes about half a second to calculate trust for each user the best way to do this is just to do one ET calc without the loop avoidance.  It won't be perfect, but this gives you a close estimate in a situation where it doesn't matter to much since your network will still be correct.

Hm, yeah, no loop avoidance is better than taking a minute to load, and this is the most straightforward way to do it.

It would be great to have this displayed on the website too, might want to pull @ChrisRimmer in to make the UI for that. Something like

Consolidating into #34


Fix @specs to match GenServer specs

This PR will fix all @specs
Because most of the functions are forwarded to GenServer, we need to match specs. This will make dialyzer happy.

Thanks! I agree that this should definitely be updated.
One question: Shouldn't it be changed to GenServer.server instead of GenServer.name?

@fhunleth yes, right! Will fix that.

Fixed.

Thanks!


Fix the copyright in your license

It currently reads
"Copyright [yyyy] [name of copyright owner]"
Unless your name is "[name of copyright owner]", you should probably change this.

oops! fixed, thanks.


CODEOWNERS: Add for drivers/wifi/ same reviewers as for drivers/ethernet

drivers/wifi/ is closely related to the (IP) network stack, so
shouldn't be left without owners, so use the same as for Ethernet.
Also, extend, don't replace reviewers for drivers/wifi/eswifi based
on the above change and CODEOWNERS processing order.
Also, add a reminder about this processing order at the top of file.
Signed-off-by: Paul Sokolovsky<EMAIL_ADDRESS>

Noticed that issue long ago, but kept forgetting sitting to the keyboard, finally remembered now.

@tbursztyka: Ping. Fancy doing more work (officially)? ;-)

@nashif : Please re-review.

Ping @nashif.
We have many areas in the tree not covered by CODEOWNERS. Here's another example: https://github.com/zephyrproject-rtos/zephyr/pull/12214

Or maybe ping @carlescufi ;-)


Convert ./packages/example-boards/src/boards/playground/audio.ts to Build API

This is raised as a draft PR for now while waiting for a fix to the geminiText board.


Fix build error on Windows

VS2013 has round() function and if you redefine it causes build error (see http://slicer.cdash.org/viewBuildError.php?buildid=1021062).
If you need backward compatibility with older VS versions then you can add a try_compile test for round().

Thanks for merging this. Would you also update the release branch so that the build error is fixed in Slicer nightly builds? If you prefer, I can update the extension index to point to the latest version on the master branch.

Yes, I will merge to the release branch. No need to update the ExtensionIndex.


Some headers are not encoded when using Grpc::AsyncClient

Title: Some headers are not encoded when using Grpc::AsyncClientOne line description
Description:
I am trying to write an extension that uses Grpc::AsyncClient, and sends a message to external upstream.
I am observing weird behavior where the logs show that the correct headers have been decoded, but using WireShark, I can see that practically they have empty value.
I understand that it's using a common code from HTTP and there's a low probability that there's an actual bug with the encoding layer, but I don't think WireShark lies either. Is it possible that I have misconfigured something?
Grpc::RawAsyncClientSharedPtr is created using the following code:
server.clusterManager().grpcAsyncClientManager().getOrCreateRawAsyncClient(grpc_service, server.scope(), false)
where grpc_service points to the cluster below:
request is sent using:
client_->send(service_method_, *export_request, *this, Tracing::NullSpan::instance(), Http::AsyncClient::RequestOptions());
  - name: open_telemetry_sink
    typed_extension_protocol_options:
      envoy.extensions.upstreams.http.v3.HttpProtocolOptions:
        "@type": type.googleapis.com/envoy.extensions.upstreams.http.v3.HttpProtocolOptions
        explicit_http_config:
          http2_protocol_options: {}
    load_assignment:
      cluster_name: open_telemetry_sink
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: <IP_ADDRESS>
                port_value: 6060

Logs:

router decoding headers:\n':method', 'POST'\n':path', '/opentelemetry.proto.collector.metrics.v1.MetricsService/Export'\n':authority', 'open_telemetry_sink'\n':scheme', 'http'\n'te', 'trailers'\n'content-type', 'application/grpc'\n'x-envoy-internal', 'true'\n'x-forwarded-for', '<IP_ADDRESS>'\n"

WireShark snapshot:
Frame 50: 348 bytes on wire (2784 bits), 348 bytes captured (2784 bits)
HyperText Transfer Protocol 2
    Stream: HEADERS, Stream ID: 57, Length 53, POST /opentelemetry.proto.collector.metrics.v1.MetricsService/Export
        Length: 53
        Type: HEADERS (1)
        Flags: 0x04, End Headers
        0... .... .... .... .... .... .... .... = Reserved: 0x0
        .000 0000 0000 0000 0000 0000 0011 1001 = Stream Identifier: 57
        [Pad Length: 0]
        Header Block Fragment: 8304ac60f596a49682d254d9e97aec3a4eb90f4505224f62f4953618885fb857d054d862…
        [Header Length: 199]
        [Header Count: 8]
        Header: :method: POST
        Header: :path: /opentelemetry.proto.collector.metrics.v1.MetricsService/Export
        Header: <unknown>:
        Header: :scheme: http
        Header: <unknown>:
        Header: <unknown>:
        Header: <unknown>:
        Header: <unknown>:
HyperText Transfer Protocol 2
    Stream: DATA, Stream ID: 57, Length 205
        Length: 205
        Type: DATA (0)
        Flags: 0x01, End Stream
        0... .... .... .... .... .... .... .... = Reserved: 0x0
        .000 0000 0000 0000 0000 0000 0011 1001 = Stream Identifier: 57
        [Pad Length: 0]

Was a problem with wireshark


#2 fixed

fixes #2 #3
worked on the given ui and tried my best to make it similar to intended ui and added responsive design to the layout

Looks good but need some improvements.
will be merging this but can you please make it more refined

can u please tell me the refinements you want

i made some changes , can u please review

Can you please provide a screenshot for the result?


noai in .vimrc is ignored

Since the recent upgrade to vim-8.2.1167, the set noai option in .vimrc seems to be ignored. Other options from .vimrc are working fine. I can :set noai interactive which also works but I would prefer if it's read from my config file.
Last known version where set noai in vimrc was working as expected is 8.2.0007

What's the output of :verbose set ai?

It seems to be correct:
noautoindent
Zuletzt gesetzt in ~/.vimrc Zeile 5
Even though copy and paste with middle click mouse generates intends from:
test
test
test

to:
test
        test
                test

Which works correctly after :set noai interactively. set paste is also set in .vimrc
Maybe it is not related to noai but has another root cause. It just worked fine in the previous version I have mentioned.

Try to bisect your config to find a minimal working example.

For information, here is the list of commits between 8.2.0007 and 8.2.1167 containing the keyword "indent":

8.2.0112  illegal memory access when using 'cindent'
8.2.0146  wrong indent when 'showbreak' and 'breakindent' are set
8.2.0358  insufficient testing for indent.c
8.2.0705  indent tests don't run on CI for FreeBSD
8.2.0766  display error when using 'number' and 'breakindent'
8.2.0864  pragmas are indented all the way to the left

Thanks for the hints. My config is quite minimal for testing purposes:
set mouse=
set noai
set paste

I noticed another difference. In the previous version then there is a line beginning with a tab and I hit enter, the cursor jumps to the beginning of the new line. With the new version, the cursor jumps to the newline but at the same tab position (i hope that's understandable). Maybe this could be related to the changed behavior?

Please use the issue template when you report an issue.
Does it depend on filetype? What OS? What terminal? Does your terminal support bracketed paste (:help xterm-bracketed-paste)?

Yes, the Konsole terminal supports if for quite some time.

Please answer all questions.

Yes, the Konsole terminal supports if for quite some time.

If it does support bracketed-paste mode, why do you enable set paste? For konsole
you probably need to enable it manually. IIRC, bracketed paste only gets enabled for xterms. See :h xterm-bracketed-paste
Can you please also show a (or better two for each of the problems encountered) minimal example that shows the different behaviour? Best to start with vim --clean -c ':set ai'
And if you could bisect to the patch that introduced the regression, that would be helpful.

It does not depend on the filetype. OS is Linux, as mentioned Konsole is the terminal. An you where right about the xterm-bracketed-paste, which seems to be enabled automatically on Konsole as well. Removing set paste from the configuration file solved the issue. Thanks all for your help and sorry for the noise (still not sure which change has introduced the issue I faces, but it's fine for me).


Python 3 support

This issue is to collect discussion on our Python 3 support, or lack thereof.
The major blocker for Python 3 support seems to be the avro module, which does not support Python 3. There is a separate Python 3 avro module. Both seem to be associated with the official Avro project, so it's difficult to tell if one is official and the other is not.
The problem with the Python 3 module is that it has a completely different API. For example, in the Python 2 version we have avro.schema.parse and in Python it is avro.schema.Parse. Even working around these (insanely gratuitous) changes, there seems to be deeper differences, so we'll need to choose one or the other (or neither).
Any thoughts on this?

While Flask works with Python 3, they don't recommend using it under most circumstances.  I get the sense that it's still too early to move to Python 3 so I'm -1.

It seems like there are library issues with python 3, and we don't currently support python 3, and as @diekhans says "Part of being a reference server, you get to limit your audience to people who know what they are doing."  So, why support python 3 in the first place?  Correct me if I am wrong, but I think python 2 has a much larger install base and mindshare.

Yes, python 2->3 conversion is going slowly.  In hindsight, I
think they made some mistakes in their approach [not that I
would have had a better idea].  I also think some of there
changes were not worth the breakage (like rich comparisons).
If that the libraries server depends on are not ready for python
3, then, yes avoid it.  The main point of this suggestion was to
remove having to worry about being compatible, which has been a
pain in my experience.
Mark
Danny Colligan<EMAIL_ADDRESS>writes:

It seems like there are library issues with python 3, and we don't currently
support python 3, and as @diekhans says "Part of being a reference server, you
get to limit your audience to people who know what they are doing." So, why
support python 3 in the first place? Correct me if I am wrong, but I think
python 2 has a much larger install base and mindshare.
—
Reply to this email directly or view it on GitHub.*

OK, let's shelve Python 3 support for the moment so. We can revisit when we've got a more complete implementation and see if we can replace the Avro parts we're using. Also the Flask issue is a good one, thanks @hershman.

I completely agree with shelve Python 3 for now.  If the
dependencies are not ready, it wastes time, not saves it.
sigh, maybe Python 3000 was not such a bad name..
Jerome Kelleher<EMAIL_ADDRESS>writes:

OK, let's shelve Python 3 support for the moment so. We can revisit when we've
got a more complete implementation and see if we can replace the Avro parts
we're using. Also the Flask issue is a good one, thanks @hershman.
—
Reply to this email directly or view it on GitHub.*

Jerome Kelleher<EMAIL_ADDRESS>writes:

is avro.schema.Parse. Even working around these (insanely gratuitous) changes,
there seems to be deeper differences, so we'll need to choose one or the other
Any thoughts on this?

This is much worse than insanely gratuitous; it's changing the code
to go against the common conventions.  I highly suggest filing
tickets on this.


chore: Add VSCode extension recommendations

Pull Request
Description
This change adds a .vscode/extensions.json file to the project, recommending two Visual Studio Code extensions:

"antfu.vite" - A Vite extension for VS Code
"yoavbls.pretty-ts-errors" - An extension for prettier TypeScript error messages

These recommendations will help standardise the development environment for contributors working on this project in Visual Studio Code, potentially improving productivity and code quality.
fixes #52

#50
#49  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JackPlowman and the rest of your teammates on  Graphite

Merge activity

Oct 26, 8:03 AM EDT: A user merged this pull request with Graphite.


fix: Ensure plain text response is only used for strings

It turns out when expected errors occur (eg: those defined via potential_error in an endpoint) they are still handled via the response rack_triplet method. This means the error hash was being treated as plain text instead of JSON if the endpoint specified a plain text response
This PR fixes that by only rendering a plain text response if the type is plain text and the response body is a string

@jimehk true, although in terms of how Apia uses Rack responses it won't be an issue, as we only ever send hashes or strings.
It would definitely be good to make it a bit more robust in this sense, but as Apia was originally built for JSON responses only, it'll take quite a bit of work to make it more response-type agnostic. Definitely something to keep in mind for a future Apia update though


banshee: Check if return value was written at all

The exit_code register is initialized to 0 in Banshee. If Banshee stops before writing a return value, it will look as if the execution was successful. This patch checks the LSB of the exit_code to make sure the return value was actually written. If we have debug prints enabled, it will generate a warning, otherwise, it will just set Banshee's return value to 1.

Yes, I thought about that as well, but I did not know what would be a good return value. Maybe 0xDEADBEEF or 0xBADCAB1E, but this would get lost since the shell uses decimal. Maybe just something like 1234?

I think most shells (including bash) truncate to unsigned bytes, so 0-255 is viable.
To give it a Swiss touch, how about 117, since this is illegal behavior :)

I like it. :+1:


chore: Versioned change requests

Thanks for submitting a PR! Please check the boxes below:

[x] I have run pre-commit to check linting
[x] I have added information to docs/ if required so people know about the feature!
[x] I have filled in the "Changes" section below?
[x] I have filled in the "How did you test this code" section below?
[x] I have used a Conventional Commit title for this Pull Request

Changes

If versioning is enabled, change requests will now be created with associated versions

How did you test this code?

@kyle-ssg perhaps I didn't communicate this very well, but I was under the impression that this work would also bring segment overrides into the change request workflow when versioning was enabled?

As discussed, this will be done in a separate PR.


Selenium Manual UI Testing Framework

Addressing #136 by putting basic structure and a sample in place to test roundtrip with non-developer tester on live site manually activated, automated test with Selenium.

How do I actually run the tests? I have not used Selenium before. I saw that there is a browser plugin so maybe I should load that and then probably point it at the test suite?

yes. the plugin is the easiest way to do a replay for a manual user. I need to add those steps to the readme in the selenium base. directory. I will update those link paths as well.
Selenium github: https://github.com/SeleniumHQ/selenium-ide
Have to use either the Chrome extension or Firefox extension, can get from those browsers' marketplaces or Chrome extension
Firefox Extension
I will setup to run automated tests when I get a chance...  the browser engines can run headless in selenium using the webdriver.

Is this still something that should be merged? Or are there updates needed @davidnixon and @GeraldMit?

Is this still something that should be merged? Or are there updates needed @davidnixon and @GeraldMit?

Bump @davidnixon and @GeraldMit?

Is this still something that should be merged? Or are there updates needed @davidnixon and @GeraldMit?

yes still needs those updates David pointed out

IBM Cloud toolchain: Delivery Pipeline deployed Five-Fifths-Voter to cfc-fivefifths-space, including commit 7ff075abad852622190574c86f3e85fefd08a96f


blackmagic_flash.sh updated to support osx

Hey @davidbuzz, could you please test this on OSX.

@davidbuzz fixed!

@davidbuzz should be good to go now.

@davidbuzz can we merge this now?


Consistent tabs in all pages

The tabs must be lowercase, not fully uppercase

The tab border needs to be consistent in some places it's green and in some other place it's white.
Green tabs found in workflow

This issue is not specific to Litmus-UI and it is already being addressed in Litmus.


Cmi/compiler tests clean

Duplicate of #27 with cleaned git history:
Compiler Tests working complete

use subprocess module to Run pepper on a file, and take that output to compile an executable
and compile traditionally and compare the standard output
currently a single test that checks a ".cpp" with no preprocessing directives

I fixed a typo and now I can't approve the review, but I can use admin perms to force the merge. Woot.


media doesnt play in preview?

I'm seeing this on/off... not sure why? the MP4 1080p videos play fine in VLC

I assume it's only the "usual" hickup that somestimes the videos are not played (still have no solution for this, even a new Java version did not fix this issue). Does the video play after a restart of the Studio?

I assume this issue can be closed?

It still happens sometimes, I have been ignoring it.

It's a known issue I wasn't been able to fix yet, trying several workaround and tried the newest Java version. The player sometimes crashes and it seems there is nothing I can do about this. I leave this ticket open for now. Maybe I find a solution in the original Java sources.

Java bug, unfixable right now.


Click Dropzone Programaticly

I want to dropzone must be hidden and click dropzone programaticly

What have you tried @muradsofiyev ?

I tried with Jquery but i want

@muradsofiyev Have you tried anything? Could you provide your code snippet?

this works fine for me
      dropzoneOptions: {
        clickable: '.addImages',
      }

.addImages {
  display: none;
}

$('.addImages')[0].click();

Closing due to inactivity but @vesper8 suggestion is about as good as it gets


Deny warnings in generated crates

We already --deny warnings in:

integration tests (crates generated by the codegen-{core,client,server}-test Gradle subprojects),
{client,server}IntegrationTests; and
RustWriter.compileAndTest, via the RUSTFLAGS we bake in the CI Docker image (note though that we should delete usages of RustWriter.compileAndTest https://github.com/smithy-lang/smithy-rs/issues/3193).

However, we do not deny warnings in TestWriterDelegator.compileAndTest; we generate crates with tests that have warnings.
It seems worthwhile to modify the tests so that they don't generate warnings to be consistent across the board. If a test can't be modified so as not to emit warnings, that specific test should opt-in into allowing warnings.

For the record, as of writing (cfd89422e639f53b380f8f99641df6792f7848d1), there's 210 tests in the server that fail to compile if we --deny warnings.
failing-tests.txt


Revert "Merge pull request #2574 from alphagov/table-columns-help"

The kramdown upgrade is causing errors to appear in Errbit. Needs
further investigation. Pulling this change.
This reverts commit 47bf7daba540636a05011c8cc44c3a2c701fbfcf, reversing
changes made to cccc6b4669c3dff90268b1a75b0f4b6bf965588a.

👍


I don't see the the noise_reduction_factor being used. Is this still needed?

https://github.com/jonnymaserati/welleng/blob/25d34fa8ab91e7fff9f52df8c4e469243aef90c4/welleng/survey.py#L88

This is used for gyro surveys which have not been fully implemented yet in welleng. So this is essentially a placeholder for future functionality.


Allow required children of new optional parents

If a POST/PUT/PATCH is modified to add a new optional child element that is a reference to a nested schema with required elements, that should be considered backwards-compatible.
Adding a changelog detailing this (and the 1.0.1 release).
Fixes #2.

LGTM


DataWriterQos [6563]

Created DataWriterQos
Created WriterDataLifecycleQosPolicy

Windows failed due to the data race described in #6557.
Mac failed because its HDD lost connection.

Build status:

Linux
Mac
Windows
Performance

Failures are unrelated. Merging.


DFK AFUJ003-M12

I am trying to get a DFK AFUJ003-M12 running on Linux Mint 18.
Following the Readme I installed dependencies and compiled the code in the main dir (without ARAVIS support). Then trying with gst-launch
> gst-launch-1.0 tcambin ! videoconvert ! autovideosink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstVideoConvert:videoconvert0: failed to activate bufferpool
Additional debug info:
gstbasetransform.c(1725): default_prepare_output_buffer (): /GstPipeline:pipeline0/GstVideoConvert:videoconvert0:
failed to activate bufferpool
Execution ended after 0:00:00.716662993
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

In other words, no success.
Next I tried to compile the example showcamera. Unfortunately it still assumes gstreamer-0.10, so needed a few adjustments, but I got it to compile. When starting it, it shows the correct camera model and serial. Command line shows resolutions and properties. But when I push "Start", there is no image, and this output:
Pipeline build start
The pipeline element "tisvideobufferfilter", "bufferfilter" could not be created.

(showcamera:22854): GStreamer-WARNING **: 0.10-style raw video caps are being created. Should be video/x-raw,format=(string).. now.
Module "autoexposure" is null.
Module "bufferfilter" is null.

** (showcamera:22854): CRITICAL **: Unable to link source pipeline to autoexposure
Module "image_sink" is null.

(showcamera:22854): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed
Module "image_sink" is null.

(showcamera:22854): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(showcamera:22854): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Playing

Any idea on what I am doing wrong?

Hi,
Please excuse the late reply.
What hardware are you using?
Do tools like qv4l2 or guvcview allow you to interact with the camera?
Could you give me the output of the following command:
gst-launch-1.0 --gst-debug=tcam*:5 tcambin ! videoconvert ! autovideosink

Gstreamer-0.10 is officially not supported. The showcamera will be removed with the upcoming release.

I am testing the camera on a standard desktop PC, connected to a USB3 port. If you need more specific info, please let me know which details could be useful.
I tried qv4l2 and guvcviewer now, both work (I had to reconnect the camera first).
Still no luck with gstreamer though. I attached a file with the debug output you asked for.
output.txt

Ok, the camera works as expected.
We are dealing with a gstreamer problem.
From your output we can see that the tcamsrc delivers images but videoconvert fails at activating the bufferpool. I have not yet encountered this message and did not find anything related to it, so I have to somewhat guess. We have to use try and error for this.
Could you execute these commandlines for me and give me the output/tell if they work:
gst-launch-1.0 --gst-debug-level=3 tcambin ! video/x-raw,format=GREY8 ! videoconvert ! ximagesink

gst-launch-1.0 --gst-debug-level=3 tcambin ! video/x-raw,format=GREY8,framerate=15/1,width=640,height=480 ! videoconvert ! ximagesink

gst-launch-1.0 --gst-debug-level=3 v4l2src ! bayer2rgb ! videoconvert ! ximagesink

gst-launch-1.0 --gst-debug-level=3 v4l2src ! videoconvert ! ximagesink

The first 3 didn't work, the 4th one gives some warnings, but also shows camera images. Full output here:
output_tests.txt
(The error messages on the first and second make me suspect there are errors in the formulation of this pipeline, but my experience with gstreamer is too limited to make a definitive claim.
I also suspect this is rather a gstreamer problem, since meanwhile I managed to get full resolution images from the camera using a cv::VideoCapture. Still, I guess it would be helpful and informative in general to find out the reason for the gstreamer issue.

A mistake on my side. GREY8 != GRAY8 and of course one works while the other doesn't.
gst-launch-1.0 --gst-debug-level=3 tcambin ! video/x-raw,format=GRAY8 ! videoconvert ! ximagesink

gst-launch-1.0 --gst-debug-level=3 tcambin ! video/x-raw,format=GRAY8,framerate=15/1,width=640,height=480 ! videoconvert ! ximagesink

Since the third line also causes problems and there are none of our modules involved it is definitely a gstreamer problem. Considering the output of the fourth pipeline (invalid buffer line, etc) there is something weird.
gst-launch-1.0 --gst-debug=v4l2src:5 v4l2src ! videoconvert ! ximagesink


fix: update hooks for webpack 5

Related to https://github.com/gregberge/loadable-components/issues/636

any information why this pull request was declined ?

It wasn't?

I have my own created version to fix this Issue can I submit a pull request too ?

what about this ?

testing....

testing....

Working perfectly. That's everyone for making this happen (and sorry for being 🐢 )
#689 has to be addressed before releasing a new version...

Working perfectly. That's everyone for making this happen (and sorry for being 🐢 )
#689 has to be addressed before releasing a new version...


Analysing Deep Reinforcement Learning Agents Trained with Domain Randomisation

This was a really beautiful article with some fantastic results on visual attribution. With respect to some of your hypotheses, methodology, and questions for further research, you may find the results from Analysing Deep Reinforcement Learning Agents Trained with Domain Randomisation relevant. In particular:

We apply a range of interpretability measures to understand how visual procedural generation affects DRL agents
Using domain randomisation to make the training distribution more diverse results in more interpretable features (Sec. 4.2)
In contrast to normal expectations on interpretability and generalisation, it is possible for agents trained with diverse data to "overfit" (Sec. 3.3)
In contrast to your setup, we did find that applying regularisers to activation maximisation did help (Sec. 2.2.2); it is possible that with a shallower network you might have found more interpretable maps
We study generalisation by using a basic subset of domain randomisation properties and testing against reasonable out-of-distribution settings (Sec. 3.4)
We study two tasks of differing difficulty, but this does not seem to impact interpretability (in our experiments at least)
There are 2 quantitative metrics that we use that might relate to interpretability, power spectral entropy (Sec. 2.2.4) and entanglement (Sec 2.2.8)

Thanks so much for drawing our attention to this highly relevant paper. It is very interesting to compare and contrast the two domains. I have pushed an update to the article accordingly.


Opening from S3 with credentials only via official mechanisms

@martinschorb @constantinpape switching to the new N5 libraries I cannot easily support anymore that users would enter their S3 credentials into MoBIE, but they would follow the official AWS S3 mechanisms, which I think mean to store those credentials in some special file on their computer. Is that OK?

If somehow possible it would be quite helpful to still support the direct credential entry. I am using this in a couple of projects, and it makes it much easier to explain this to collaborators, especially since the location of the credential file differs between operating system.
If there's really no other way than I guess we can do without it, but maybe there is some way to add support for a credentials provider?

I guess you could make MoBIE write to the aws credentials file. It will be a bit hacky (figure out the OS, and storage location), but why not having something like credential manager inside MoBIE that would take the project name (github URL) as ID and manage the keys (create new ones in the file if not yet existing).

@martinschorb @constantinpape
I asked chatGPT about it. It seems we could add a new AddAWSCredentialsCommand which would appear under Plugins > MoBIE > AWS > Add Credentials and contain the below code.
What do you think?

You can save AWS credentials in a credentials file that the AWS SDK for Java
will automatically detect. Here's a simple Java code example to save AWS
credentials. This example saves the credentials in the default location (
~/.aws/credentials  on Linux and macOS, or  C:\Users\USERNAME.aws\credentials
on Windows).

    import com.amazonaws.auth.profile.ProfileCredentialsProvider;
    import com.amazonaws.auth.AWSCredentials;
    import com.amazonaws.auth.AWSStaticCredentialsProvider;
    import com.amazonaws.auth.BasicAWSCredentials;
    import com.amazonaws.services.s3.AmazonS3;
    import com.amazonaws.services.s3.AmazonS3ClientBuilder;

    import java.io.File;
    import java.io.FileWriter;
    import java.io.IOException;
    import java.util.Scanner;

    public class SaveAWSCredentials {

        public static void main(String[] args) {
            Scanner scanner = new Scanner(System.in);

            System.out.println("Enter AWS Access Key ID: ");
            String accessKeyId = scanner.nextLine();

            System.out.println("Enter AWS Secret Access Key: ");
            String secretAccessKey = scanner.nextLine();

            String profileName = "default"; // Use "default" or another profile
  name as needed
            saveCredentials(accessKeyId, secretAccessKey, profileName);
        }

        private static void saveCredentials(String accessKeyId, String
  secretAccessKey, String profileName) {
            String homeDirectory = System.getProperty("user.home");
            String awsCredentialsPath = homeDirectory + "/.aws/credentials"; //
  For Linux and macOS
            // For Windows, use: String awsCredentialsPath = homeDirectory +
  "\\.aws\\credentials";

            File credentialsFile = new File(awsCredentialsPath);
            credentialsFile.getParentFile().mkdirs(); // Create the .aws
  directory if it doesn't exist

            try (FileWriter writer = new FileWriter(credentialsFile, true)) {
                writer.append("\n[" + profileName + "]\n");
                writer.append("aws_access_key_id = " + accessKeyId + "\n");
                writer.append("aws_secret_access_key = " + secretAccessKey +
  "\n");
                System.out.println("Credentials saved successfully.");
            } catch (IOException e) {
                e.printStackTrace();
            }
        }
    }

This code prompts the user for their AWS Access Key ID and AWS Secret Access
Key, then appends them to the  credentials  file under the specified profile.
If the  .aws/credentials  file or directory doesn't exist, it creates them.

Important Security Note: Storing sensitive information like AWS credentials on
your computer should be done with caution. Ensure that the credentials file
permissions are set to be accessible only by your user account to prevent
unauthorized access.

In fact I am confused now, chatGPT says:
  AWS S3 does not support protecting buckets with a password in the traditional
  sense (like password-protected files or services). Access control in AWS S3 is
  managed through AWS Identity and Access Management (IAM) and bucket policies,
  rather than individual passwords.

  For your use case, where you want to distribute access to various users, you
  could consider the following approaches:

  ### 1. IAM Users and Policies

  • Create individual IAM users for each person who needs access.
  • Attach policies to these users or their group, granting them permissions to
  access the specific S3 bucket.
  • Distribute the AWS Access Key ID and Secret Access Key to each user, which
  they can use with an AWS SDK or CLI.

  ### 2. Pre-signed URLs

  • If users just need to download or upload specific files, you can generate
  pre-signed URLs.
  • Pre-signed URLs grant temporary access to a specific S3 object, and you can
  control the expiration time of these URLs.
  • Distribute these URLs to users for uploading or downloading without giving
  them full AWS credentials.

  ### 3. Cognito for Application Users

  • If you are managing access in an application, consider using Amazon Cognito.
  • Cognito can authenticate users and provide them with temporary AWS
  credentials limited to the permissions you define, such as access to a
  specific S3 bucket.

  ### 4. Third-party Solution

  • Use a third-party solution or custom application that manages user access and
  integrates with AWS S3, where the application layer controls access to S3
  resources based on user credentials (username/password).

  ### Summary

  For directly controlling access to an S3 bucket via a single password for
  multiple users, you would typically manage this outside of AWS (e.g., through
  a custom application layer that authenticates users and then provides access
  to S3 resources based on your logic). AWS's built-in mechanisms focus on IAM
  users, roles, and policies for access control, which do not align with the
  single-password model.

I am not sure what we are currently doing...do you?

1. IAM Users and Policies
• Create individual IAM users for each person who needs access.
• Attach policies to these users or their group, granting them permissions to
access the specific S3 bucket.
• Distribute the AWS Access Key ID and Secret Access Key to each user, which
they can use with an AWS SDK or CLI.

We are using this, but using generic users instead of creating an account per user. I.e. we usually have one user with read and one user with write access, and would distribute the credentials for the user with read access to whoever just needs to access the data.

I asked chatGPT about it. It seems we could add a new AddAWSCredentialsCommand which would appear under Plugins > MoBIE > AWS > Add Credentials and contain the below code.
What do you think?

This can be done, but it's not really a clean solution. I am not sure which library you're using now for reading n5/zarr, but not being able to pass on a credentials provider (or a client initialized with the credentials provider) seems to be a major lack of functionality.
For reference, here is a simple example how to do this according to ChatGPT:

I am not sure which library you're using now for reading n5/zarr, but not being able to pass on a credentials provider (or a client initialized with the credentials provider) seems to be a major lack of functionality.

I am using the new n5 libraries from Saalfeld et al.
The most basic place where they would need to add this is here:
https://github.com/saalfeldlab/n5-aws-s3/blob/master/src/main/java/org/janelia/saalfeldlab/n5/s3/N5AmazonS3Reader.java
But we would need it also downstream in https://github.com/saalfeldlab/n5-viewer...
I think it will be hard for them to add it downstream because they are aiming for a unified interface for HDF5/N5...
AWS-S3/FileSystem.....

Sorry, I think this whole issue is false alarm!
We can, and also did, attach the credential provider into the S3Client:
        // Create the access
        AmazonS3 s3 = AmazonS3ClientBuilder
                .standard()
                .withPathStyleAccessEnabled( true )
                .withEndpointConfiguration( endpointConfiguration )
                .withCredentials( credentialsProvider )
                .build();

So, most likely everything will continue to work as is.

We have to look whether we can use an n5 reader with credentials here:
            N5URI n5URI = new N5URI( uri );

            String containerPath = n5URI.getContainerPath();
            N5Reader n5 = new N5Factory().openReader( containerPath );
            // FIXME: somehow add the credentials if this is an AWS-S3 reader...
            String group = n5URI.getGroupPath() != null ? n5URI.getGroupPath() : "/";
            List< N5Metadata > metadata = Collections.singletonList( N5MetadataUtils.parseMetadata( n5, group ) );

            final DataSelection selection = new DataSelection( n5, metadata );
            converterSetups = new ArrayList<>();
            sourcesAndConverters = new ArrayList<>();
            bdvOptions = BdvOptions.options().frameTitle( "" );

OK, nice, in fact, upon closer examination the new n5 library provides functionality for this: N5Factory().s3UseCredentials( credentials ).
    private static N5Factory getN5Factory()
    {
        String[] s3AccessAndSecretKey = S3Utils.getS3AccessAndSecretKey();
        if( s3AccessAndSecretKey != null )
        {
            BasicAWSCredentials credentials = new BasicAWSCredentials( s3AccessAndSecretKey[ 0 ], s3AccessAndSecretKey[ 1 ] );
            return new N5Factory().s3UseCredentials( credentials );
        }
        else
        {
            return new N5Factory();
        }
    }

Is there something that I could easily test this with (you could send me the credentials in the EMBL chat)?

In fact, ideal would be a real @Test for this.
Could one of you create a mobie-credentials-test bucket containing one ome-zarr that can only be read with credentials?
I would then put those credentials inside the Java code, so it would be readable for everyone.

In fact, ideal would be a real @Test for this.
Could one of you create a mobie-credentials-test bucket containing one ome-zarr that can only be read with credentials?
I would then put those credentials inside the Java code, so it would be readable for everyone.

Yes, I think that's the best solution. It's probably best if you could get a bucket on the EMBL s3 for this.


Migrate to container-based infrastructure on travis

This PR changes our .travis.yml to make use of container-based infrastructure on travis. It removes the warning This job ran on our legacy infrastructure. Please read our docs on how to upgrade (e.g. here)
See also this how-to.
Please review.

/cc @buehner & @ahennr

Nice one! Thx for the offline explanation. :facepunch:


Installation no longer works

Hi!
I tried to install the adapter following the steps in https://github.com/danmasta/ghost-gcs-adapter?tab=readme-ov-file#installation but it no longer works.
Getting a 404 not found error for: https://registry.npmjs.org/@danmasta%2Fghost-gcs-adapter
Is there an alternative way to install?
Thanks!

Hi @rob-sto, sorry about that, I just updated the readme. You can still install from github like so:
RUN mkdir -p /tmp/gcs && \
    curl -fsSL "https://api.github.com/repos/danmasta/ghost-gcs-adapter/tarball/master" | tar xz --strip-components=1 -C /tmp/gcs && \
    npm install --prefix /tmp/gcs --omit=dev --omit=optional --no-progress --loglevel error && \
    mv /tmp/gcs "${GHOST_INSTALL}/current/core/server/adapters/storage"

Thanks a lot for the quick response! Your solution works without problems.
I did not have curl installed and tried to download the release version from github the following way but could not get it working:
RUN mkdir -p /tmp/gcs
ADD https://github.com/danmasta/ghost-gcs-adapter/archive/refs/tags/v1.0.1.tar.gz /tmp
RUN tar -xzvf /tmp/v1.0.1.tar.gz --strip-components=1 -C /tmp/gcs && \
   npm install --prefix /tmp/gcs --omit=dev --omit=optional --no-progress --loglevel error && \
   mv /tmp/gcs "${GHOST_INSTALL}/current/core/server/adapters/storage"

There seems to be a difference between the master branch and release version 1.0.1
Thanks!

@rob-sto Ah I see, that would probably still work, you just need to bump the version to v1.0.2, there was a change in one of the dependencies:
ADD "https://github.com/danmasta/ghost-gcs-adapter/archive/refs/tags/v1.0.2.tar.gz" /tmp

You could also use a multi-stage build and copy the files to your final image like this:
FROM node:22-bookworm-slim AS deps

RUN apt-get update && \
    apt-get install -y --no-install-recommends \
        ca-certificates \
        curl

WORKDIR /tmp/gcs

RUN curl -fsSL "https://api.github.com/repos/danmasta/ghost-gcs-adapter/tarball/v1.0.2" | tar xz --strip-components=1 -C /tmp/gcs && \
    npm install --prefix /tmp/gcs --omit=dev --omit=optional --no-progress --loglevel error

FROM ghost:5.99.0

COPY --from=deps --chown=node:node /tmp/gcs "${GHOST_INSTALL}/current/core/server/adapters/storage/gcs"


Not Working on FireFox 55.0.3 Version. But Working on oth

Not Working on FireFox 55.0.3 Version. But Working on others version.

@Geek-in-Training hasn't made any commits since 2014, this repo is dead.


Subtle improvement for Void (distro) logo

Hello, thank you for neofetch :)
IMO, replacing the L at top right of "VOID" with a dot makes a more readable shape for the "D".

Done!


Build error with ArmNN 19.11

While building ArmNN 19.11 I get the following error:
[  107s] [  3%] Building CXX object CMakeFiles/gatordMockService.dir/tests/profiling/gatordmock/PeriodicCounterCaptureCommandHandler.cpp.o
[  107s] /usr/bin/c++  -DARMNNREF_ENABLED -DARMNN_CAFFE_PARSER -DARMNN_ONNX_PARSER -DARMNN_SERIALIZER -DARMNN_SERIALIZER_SCHEMA_PATH=\"/home/abuild/rpmbuild/BUILD/armnn-19.11/src/armnnSerializer/ArmnnSchema.fbs\" -DARMNN_TF_LITE_PARSER -DARMNN_TF_LITE_SCHEMA_PATH=\"/usr/include/tensorflow/lite/schema/schema.fbs\" -DARMNN_TF_PARSER -DBOOST_ALL_DYN_LINK -DPROTOBUF_USE_DLLS -I/home/abuild/rpmbuild/BUILD/armnn-19.11/include -I/home/abuild/rpmbuild/BUILD/armnn-19.11/src/profiling -I/home/abuild/rpmbuild/BUILD/armnn-19.11/tests/profiling -I/home/abuild/rpmbuild/BUILD/armnn-19.11/tests/profiling/gatordmock -I/home/abuild/rpmbuild/BUILD/armnn-19.11/tests/profiling/timelineDecoder -isystem /usr/lib/python3.7/site-packages/tensorflow/include -isystem /home/abuild/rpmbuild/BUILD/armnn-19.11/onnx_deps -isystem /home/abuild/rpmbuild/BUILD/armnn-19.11/third-party  -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -g -pthread -std=c++14 -Wall -Werror -Wold-style-cast -Wno-missing-braces -Wconversion  -O2 -g  -fPIC   -o CMakeFiles/gatordMockService.dir/tests/profiling/gatordmock/PeriodicCounterCaptureCommandHandler.cpp.o -c /home/abuild/rpmbuild/BUILD/armnn-19.11/tests/profiling/gatordmock/PeriodicCounterCaptureCommandHandler.cpp
[  107s] In file included from /home/abuild/rpmbuild/BUILD/armnn-19.11/tests/profiling/gatordmock/PeriodicCounterCaptureCommandHandler.cpp:6:
[  107s] /home/abuild/rpmbuild/BUILD/armnn-19.11/tests/profiling/gatordmock/PeriodicCounterCaptureCommandHandler.hpp:10:10: fatal error: ../../armnn/src/profiling/Packet.hpp: No such file or directory
[  107s]    10 | #include "../../armnn/src/profiling/Packet.hpp"
[  107s]       |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[  107s] compilation terminated.

Hi ggardet,
I've pushed a patch to fix the includes path: https://review.mlplatform.org/#/c/ml/armnn/+/2431/
Could you rebuild with the change; it should fix the issue.
Regards,
Francis.

@FrancisMurtagh-arm Yes, it does fix the build, but some UnitTestsare failing.
I opened a new issue for this: https://github.com/ARM-software/armnn/issues/312


[VS Code] The relay listener went offline, unsharing workspace. Re-share to generate a new session.

Error:
The relay listener went offline, unsharing workspace. Re-share to generate a new session.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.869

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.28.2

platformName
MacOS

platformVersion
18.0.0

Thanks for reporting this. Could you please run the command "Live Share: Export Logs" and drag-and-drop the zip or send it to<EMAIL_ADDRESS>I'm going to close this issue as a duplicate of #1124; please attach your logs to #1124 when you get them.


Modern CMake Work in Progress

As discussed in issue #54, I'm proposing moving to a modern CMake build system. This pull request is not meant to be merged but to gather feedback.

I split the build definitions for examples and tests from the library itself
I have not yet implemented CCache and build options for tests, but those will follow
I have provided options for turning off examples and tests (defaulting to ON)

Does this look like a promising direction to you?

Hi @ooxi - thanks for contributing to the project.
Yes, I think it looks like it's on the right track. I would perhaps have hoped we didn't need to change any cpp code files. But I guess it could be fine as long as examples/*.cpp files paths to CSV files are not changed, as those source files are actually "executable" under Unix-based OS'es like macOS and Linux, which restricts what CSV paths are used in those cpp files.
Btw, there's been a request to support conan packaging of rapidcsv. So eventually there may be a need to add some top-level install capability (I have yet to check how conan works with cmake). Just to let you know in case you happen to have worked with conan packaging of cmake projects. :-)

@d99kris I have only changed paths in the C++ test files, since the current working directory will change when executing tests. But I do see your point and will try to not change C++ files :-)
This will complicate the CMake files a little but should make reviewing the patch easier and can be fixed in a second commit. Thanks for your support!

There has not been much activity on this PR recently, so I will proceed to close it for now (I'm cleaning up my list of open issues/PRs to monitor).
Do feel free to re-open it when/if there are any updates. Thanks.


Headless

Moving headless into main

Will let it get all wordpress content updates automatically
We can manage all client side build scripts in one place

I know it is problematic to try to review a huge PR like this. Merging to main where it will power the prototype site headless.cannabis.ca.gov. This codebase does not yet power any production sites.


New action request: BerniWittmann/background-server-action

Action name
uses: BerniWittmann/background-server-action
Reasons
BerniWittmann/background-server-action

Intended usage
BerniWittmann/background-server-action

I have checked the internal marketplace for similar actions and couldn't find one that works for us.

[X] I have checked the internal marketplace first

:robot: Found these results:

Check
Results
Links

CodeQL on the forked repo
:x:
CodeQL run

Security scan:

Check
Result

No Dependabot configuration found
⛔

No CodeQL Init found
⛔

No CodeQL Analyze found
⛔

:robot: Found these results:

Check
Results
Links

CodeQL on the forked repo
:x:
CodeQL run

Security scan:

Check
Result

No Dependabot configuration found
⛔

No CodeQL Init found
⛔

No CodeQL Analyze found
⛔

:robot: Check completed with result: ⚠
Found 17 Dependabot security vulnerabilities:
10 where high and 7 where moderate.
Use this link to verify the alerts.


Add new books to the catalog

Add information about three new books to the books.txt file

додав фото


Dash (-) not supported in resource name

The resource and attribute names are checked against the regex /^[A-Za-z0-9_]*$/. Is it possible to also support -, i.e. resource-name-is-like-this format? It could just be as easy as changing it to /^[A-Za-z0-9_\-]*$/.

Thanks for the investigation @prshreshtha. I should have some time soon to look into adding support for disabling GraphQL.

You can already do this. graphiql: false in the options.

@queenvictoria You are correct that #256 does cover part of this issue. It is a pre-requisite to supporting dasherized names. But I don't see any work done for it.


bump version

Codecov Report

Merging #6 (954408c) into main (496fd8f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            2         2
=========================================
  Hits             2         2

Continue to review full report at Codecov.

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


Docker image scikit-learn out of date

I created a fresh docker image. Book 1 code example 1-1 asserts sklearn >=.20 but the installed version is .19.1
Running make exec then conda update scikit-learn says user does not have write permissions to /opt/conda and sudoing the command says conda command not found.

Hi @GuillaumeQuenneville ,
Ah thanks. I just updated the docker image for the first edition. I'll update the 2nd edition as well (but it's a moving target right now, as TF 2.0 is not released yet, so I'm using nightly builds).


Feature: show source code permanently in the side bar

Similar to #166, I’d like to use the large space in the side bar to show me contextual information that helps me during translation. (My screen is 1920x1280.)
When translating software, the source texts usually know where they appear in the source code. There is already a menu item to show the source code in a separate window.
I’d like to have a similar feature that permanently shows the source code of the current entry, and when I switch to another entry, the source code changes as well.
Currently, when I want to see the source code, I have to open a window for each entry, and later I have to close it again. That’s definitely possible, but also much work.

The references window already behaves like this since 9bdeafd98baf5e533d58e630d95a003189ecc843. Please check the current state of master before going on an issues-filing spree ;-)

Wow, I just tried it and it really feels great. Thank you very much. I think I’ll keep using the beta version instead of the official releases. :)


FZ.se feed not working

The feed http://www.fz.se/core/rss/fznews_rss20.xml does not work in stringer. It does however work in a few other feed readers I have tested.
I am running the latest commit of stringer.
In the stringer UI it has the red dot next to it, with the text "Error parsing (and it ain't never worked before either)".
The log contains this:
/usr/local/bundle/gems/feedjira-1.3.0/lib/feedjira/feed.rb:237: warning: uncaught exception from callback
The feed itself does contains some errors (https://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fwww.fz.se%2Fcore%2Frss%2Ffznews_rss20.xml)
Is this something related to stringer itself or should it be reported to feedjira? Or even the maintainer of the feed?

It's most likely a problem in feedjira or just a malformed feed in general.

It doesn't appear to be a problem in feedjira.
Using irb to fetch and parse the feed with feedjira gives the expected result.
irb(main):001:0> require "feedjira"
=> true
irb(main):002:0> Feedjira::VERSION
=> "1.3.0"
irb(main):003:0> url = "http://www.fz.se/core/rss/fznews_rss20.xml"
=> "http://www.fz.se/core/rss/fznews_rss20.xml"
irb(main):004:0> options = {user_agent: "Stringer (https://github.com/swanson/stringer)", if_modified_since: Time.new(2014, 1, 1), timeout: 30, max_redirects: 2, compress: true}
=> {:user_agent=>"Stringer (https://github.com/swanson/stringer)", :if_modified_since=>2014-01-01 00:00:00 +0100, :timeout=>30, :max_redirects=>2, :compress=>true}
irb(main):005:0> feed = Feedjira::Feed.fetch_and_parse(url, options)
=> #<Feedjira::Parser::RSS:0x007f826b89b418 @version="2.0", @title="Nyheter från FZ.se", @url="http://www.fz.se/nyheter/", @description="De senaste nyheterna från FZ.se. Uppdateras kontinuerligt.", @entries=[#<Feedjira::Parser::RSSEntry:0x007f826b890838 @title="Då öppnar betan för Star Wars: Battlefront", @url=

@kaksmet this feed works for me on my Stringer instance (running latest master), so it's likely not a Stringer/Feedjira issue.
It could be that fz.se is blocking requests from some popular hosting providers, like EC2.
You can verify this by curling that feed on your server and see if that works.

I'm hosting it locally and curling the feed works fine.
I am running it in a docker container though, but that shouldn't be the problem since about a dozen other feeds are working as expected.

Ok and did you run that irb session also in the container?
It could also be an encoding issue. I've seen weird encoding related stuff happen before when running in Docker containers which often times don't have proper locale configurations.

The issue was encoding related as it works if I configure a proper locale in the docker container.
@pascalw thank you for your help.


Fix README filename

Since the README was changed from .md to .rst (#46) pip install no longer works.

Thanks!


If cronjob is disabled, it should stay disabled after update

Describe the bug
I manually removed the cronjob which restarts telegram every night at 05:00 am as this triggers a notification every time and also without that restart telegram is working fine for me. But after an update each time the cronjob is activated again. Please add a check, that if the cronjob has been removed it will not be added after an update again.
Versions:

Adapter version: v1.12.2
JS-Controller version: 4.0.21
Node version: 14.19.0
Operating system: ubuntu

Please open this issue in js-controller ... this is a general topic.


how to let image center in a cell ?

there is my code:
 img = "#{Rails.root}/public#{material.image.file.url.gsub(/\?\d+$/,"")}"
 sheet.add_image(:image_src => img, :noSelect => false, :noMove => false) do |image|
    image.width = 100
    image.height = 100
    image.start_at 0, 1
 end

what i need do more for my issue , i do not find the relation code  for this ..

Its very sad to see that this issue is not resolved yet.
@songjiayang +1. Have you found any solution?

Not yet, I think there are some real difficulty.


Trailing Cursor aesthetics

Is there an existing issue for this?

[x] I have searched the existing issues

What happened?
Hello PA,
The trailing cursor feature colors can be a mismatch with the overall theme of the website and can be distracting at times. So, I want to work on experimenting and making that better.
https://github.com/user-attachments/assets/90784cd4-78be-4dd0-ac4e-4d73a6fa3871
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

This issue has been completed in PR #1240


Adding Cricket Calculator

Description
I want to add a cricket calculator in which it calculates following :
1.Batsman Strike Rate
2.Bowlers Economy Rate
3.Required Run Rate
4.Projected Score
5.Target
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[X] I am a SWOC'24 contributor.

Code of Conduct

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

Please assign me

Go ahead @GarvVirmani


integration-docs: Update Zabbix for new doc format.

Apply integration-docs' new format.
Fixes part of https://github.com/zulip/zulip/issues/29592.
Updates the following integration documentation pages:
Screenshots and screen captures:

Zabbix
Doc link

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@zulipbot add "buddy review" "area: documentation (api and integrations)"

Feedback addressed:
Moved the warning to outside the tabs.
Updated the screenshot.
Thank you for the review, @PieterCK and @adnan-td !
Please review these, @zormit
@zulipbot remove "buddy review"
@zulipbot add "mentor review"

@Niloth-p - Looks great! I pushed a few more small revisions to tighten up these instructions as they are quite long.
Updated screenshot:

Zabbix

Merged, thanks @Niloth-p and reviewers!


stateful token generation

Coverage remained the same at 22.404% when pulling 8ca19fa8683eac2cdf296ed241c0be1851f9a71e on keniamoya:master into 7e474b29b1bc1a259cd9edf482f9ac664f050e1b on chrissmejia:master.


add selection to ListView

At the moment the VNode ListView doesn't support selection of items (at least I haven't seen the possibility to do so).
This includes 2 aspects: I like to be able to define which items are selected based on the state and I like to dispatch an action when the user selects an item.
I've tried to add this functionality and to provide a PullRequest but I haven't understood how to add this with the existing builders. I think the reason is that the selection is not just a property on the ListView but instead in normal JavaFX you have to use the SelectionModel from the ListView.
If you can give me some hints on how this should be implemented I'm happy to provide a PullRequest.

That is really a good question I have not thought about until now. Have you ever used a custom implementation of SelectionModel? So far I have only used the default ones and it is not clear to me in which cases a custom implementation is needed.
I think there are two possibilities how this could be implemented. The SelectionModel could be mapped to a special, distinct node in the VirtualScenegraph. The usage would be slightly more complicated, but one could provide custom implementations of SelectionModel.
The other option would be to flatten the API and move the required properties directly into ListViewBuilder. This would be simpler to use, but it would prevent custom implementations.
Right now I do not know what the right approach would be. Option 2 would be sufficient for me, though it would certainly be a limitation compared to the JavaFX API.

I have also thought about Option 2. I don't use custom SelectionModels and I don't know any use cases either. I would ignore this until someone has an actual use case for custom selection models.
I would be happy with a flattened API for selection. Most methods of the SelectionModel is imperative API like select(T obj) or clearSelection() which we don't need for reduxfx anyway.