Potential sRGB bug on Mac

I believe I may have found a potential bug related to using a sRGB framebuffer on Mac.
I am using the latest version of GLFW (3.2.1)
My OS is MacOS Sierra 10.12.3 - current hardware is the new 2016 touchbar MacBook Pro 13"
When using a sRGB enabled framebuffer I have an issue when in fullscreen. For an unknown reason when switching away from then back to the fullscreen window, upon arrival the window gets a red overlay that encompasses the entire viewport. This red overlay the begins to quickly flash repeatedly.
If I move my cursor to expose the toolbar at the top of the screen the red flashing goes away.
Related to this, when I create an open file dialog box, if the box overlaps with the window the area under the box will have the same issue whether is it in fullscreen or not.
I have narrowed this down to being related to sRGB because if I remove the code:
glfwWindowHint( GLFW_SRGB_CAPABLE, GLFW_TRUE );

and
glEnable(GL_FRAMEBUFFER_SRGB);

The issue goes away.
I am not sure if it is an issue related to my code, glfw itself, my drivers, or something else entirely.
Assistance with this would be greatly appreciated.
EDIT: Upon further testing, this issue seems to arise because of the retina display on my laptop. I created a very similar window using SDL as the library and the same issue arises. However I have now learned that if I disable retina scaling the issue goes away. I know this because I was able to test the application on a non retina iMac and there was no issue. Because only applications I have been developing have been having this issue I have to believe that there is something with GLFW that can be done to fix the issue.
Here is a link to a video of the issue:
https://youtu.be/OUOE4t9tYxU
Apologies for the quality of the video, for some reason when I try to record my screen using quicktime the flashing red overlay does not show up.
Here is the Code that results in the issue:
int main () {

	GLFWwindow* window_ptr;
	int window_width, window_height;
	int gl_viewport_width, gl_viewport_height;

	if ( glfwInit() ) {
		glfwWindowHint( GLFW_CONTEXT_VERSION_MAJOR, 3 );
		glfwWindowHint( GLFW_CONTEXT_VERSION_MINOR, 3 );
		glfwWindowHint( GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE );
		glfwWindowHint( GLFW_OPENGL_FORWARD_COMPAT, GLFW_TRUE );
		glfwWindowHint( GLFW_RESIZABLE, GLFW_TRUE );
		glfwWindowHint( GLFW_SRGB_CAPABLE, GLFW_TRUE );

		window_ptr = glfwCreateWindow( DEFAULT_WINDOW_WIDTH, DEFAULT_WINDOW_HEIGHT, "GLFW Window", 0, 0 );

		if ( !window_ptr ) {
			glfwTerminate();
			return -1;
		} else {
			glfwMakeContextCurrent( window_ptr );
			glfwGetWindowSize( window_ptr, &window_width, &window_height );
			glfwGetFramebufferSize( window_ptr, &gl_viewport_width, &gl_viewport_height );

			glfwSwapInterval( 1 );

			glViewport( 0, 0, gl_viewport_width, gl_viewport_height );
			glEnable( GL_DEPTH_TEST );
			glCullFace( GL_BACK );
			glEnable( GL_CULL_FACE );
			glEnable(GL_BLEND);
			glBlendFunc(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA);

			glEnable(GL_FRAMEBUFFER_SRGB);

			glClearColor( 0.5f, 0.5f, 0.5f, 1.0f );
		}
	}

	if ( window_ptr ) {
		while ( !glfwWindowShouldClose( window_ptr ) ) {
			glfwPollEvents();
			glClear( GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT );
			glfwSwapBuffers( window_ptr );
		}
		glfwTerminate();
	}

	return 0;
}

I don't know what is causing the flashing, but GLFW_SRGB_CAPABLE does nothing on macOS as all framebuffers on macOS are sRGB capable.

If you switch to the current master from this repository then you'll be able to verify on a single machine whether Retina scaling is the issue, as there is now the GLFW_COCOA_RETINA_FRAMEBUFFER macOS specific window hint.

I switched to the current master and disabled the retina scaling using:
glfwWindowHint( GLFW_COCOA_RETINA_FRAMEBUFFER, GL_FALSE );

This fixes the problem. However now with retina scaling disabled everything looks pretty bad.
From This I believe that retina scaling is definitely the issue. However the issue only arrises when both retina scaling and srgb are enabled together.
( For reference I did similar testing on the SDL library and the exact same problem exists with retina scaling and srgb. )

I was able to capture a screenshot of what the window is meant to look like compared to what it is actually like.
Correct:

Problem:

That's a really weird bug.  It may be worth contacting Apple about it.

I would like to know if the issue is related to my machine alone. (2016 MacBook Pro 13" w/ touch-bar)
If there is anyone with the same machine that can test to see if they have the same issue it would be greatly appreciated. (I can send a .app with instructions with how to reproduce the bug.)
Otherwise I may end up backing up my machine, then factory resetting it to see if the issue is still there.

I would like to know if the issue is related to my machine alone. (2016 MacBook Pro 13" w/ touch-bar)
If there is anyone with the same machine that can test to see if they have the same issue it would be greatly appreciated.

Would it be helpful to know if someone with a different Mac (e.g., a Late 2011 15" MacBook Pro) has the same issue? Or is it already known not to affect other models?

Here is a link to a dropbox folder. Included is a .app with both written and video instruction for how to reproduce the bug:
https://www.dropbox.com/sh/fbw506v7jum97yi/AAAm5Qgu9sgxWengl1l8AEGGa?dl=0
Any help at all would be great!
Personally I have tested it on a non retina iMac as well and the issue does not appear. I believe this is because there is no scaling.
The  bug is very odd in that it only appears when switching away from then back to a fullscreen window by swiping on the trackpad. Or by swiping to expose Mission control then going back to the fullscreen window.

Here is a link to a dropbox folder. Included is a .app with both written and video instruction for how to reproduce the bug

Is it possible to provide something I can build from source? I'd prefer to be able to do that. The video and text files are helpful.

Sorry I can't provide anything else. This isn't a problem specifically associated to one project. Any glfw project that I run with retina scaling and srgb results in the issue.

I'll see if I can try it on the snippet you shared in the original issue.

Here is the Code that results in the issue

FWIW, I tried to reproduce it on my 2013 MBP with a modified version of one of the examples but had no success.

I'm guessing that it is an issue with my laptop alone. I'll wait and see if anyone in the future has a similar issue. Until then I think I'll just work around it.

I just factory reset by laptop (2016 MacBook Pro) and the issue no longer seems to be there. It appears that there must of been something going wrong behind the scenes that is now fixed.
Thanks for the help!

@xslattery Glad to hear it! Is it all right to close this now?

Yep.


Finance and Purchase block

Figma design
Use V2 columns block , in a new variation V2 Columns (condensed) for example
In mobile they will be displayed after each other
Handle the block to have 2 links

NOTE: To be done after #41
UX points to be clarified:

[ ] Interactive elements on the block are not defined in the Mack core design kit; we propose to go for the defined link style, with the arrow icon.

Per discussion with Joe and Zoe, please move forward with your proposal for now for the interactive elements.

confirmed as done
as tested on https://59-horizontal-cards--vg-macktrucks-com-rd--netcentric.hlx.page/drafts/syb/cards
with the mention that some of the px values differ slightly from the figma designs as to fit on the page


suggest to add more message in log when fido client cannot connect to fido server

When fdo manufacturing client device cannot connect to fdo manufacturing server because the fido server is down or network issue, consider these two scenarios:

If use osbuild-composer to generate a fido edge image(an edge-simplified-installer image), osbuild-composer will fail to generate it, but there is no fido related error message in the log to tell user what's wrong.

the fido edge image provision will hang, but there is no output in the vm console, and there is no timeout for it.

If use osbuild-composer to generate a fido edge image(an edge-simplified-installer image), osbuild-composer will fail to generate it, but there is no fido related error message in the log to tell user what's wrong.

this isn't the case as when we build in osbuild-composer the fdo manufacturing server can be down and it's fine to be down and we don't have to notify in the build

2. the fido edge image provision will hang, but there is no output in the vm console, and there is no timeout for it.

right, this will have to change:

the fdo manufacturing client should retry with a backoff for ~1h then bail (cc @nullr0ute )
the service in the dracut module should then forward logs to console to be visible and/or just write down something under /boot that an admin can check later on after poweroff/reboot


Show version in demo

We should display the addon version in the demo somehow to make sure we have the latest version deployed.

The deploy could also be handled by travis stages like in https://github.com/adfinis-sygroup/ember-uikit and only be deployed for tags..

Fixed by #103


Postgres Compute and Storage page accessibility fixes.

Shows required indicator for worker node count.
This PR fixes #15769
Sets aria labels for information buttons.
This PR fixes #15760
Sets focus on buttons after edit.
This PR fixes #15759

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
37 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.001%) to 42.752%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/arc/src/ui/dashboards/postgres/postgresComputeAndStoragePage.ts
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/arc/src/ui/dashboards/postgres/postgresComputeAndStoragePage.ts
37
0.83%

Totals

Change from base Build<PHONE_NUMBER>:
-0.001%

Covered Lines:
26253

Relevant Lines:
55748

💛  - Coveralls


linkis初始化引擎-权限问题

Search before asking

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

Linkis Component
linkis-orchestrator
Steps to reproduce
前置：我们采用hadoop账号作为唯一账号
1、centos7： hadoop对应uid:1001
2、容器内：hadoop对应uid 1002
执行hive sql时，初始化引擎失败
772d70c5-fdb7-4a02-95f3-b88c90728ccf:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
681d4a67-5975-4893-8773-f557f6017c69:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
d63a8dbc-5b3d-4e22-91dd-d92764f07a69:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
9fdd39b3-cb05-4823-9ffa-ee56b0bb4119:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
9c079096-3bf6-4d20-8f13-ede7763eaa45:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
ea6043db-1f41-49e0-b07f-788f1712cc62:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
5822e535-ba0f-4fa6-910d-22e275a1fda2:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
60b156d0-7aba-4966-bea0-5b67e582cb6f:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
334ec38d-5fc4-492f-934c-44f02b711c8d:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
2b04a956-d00e-41cf-ad4a-564e65d5a485:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
97bb02b9-9095-442c-a4e0-fbd24e469390:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
dd9fbca1-706e-4915-afa4-e086d4c6b499:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
a6f8689d-652f-407b-84cd-cb0755e60073:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
aaabbf87-1d44-41f7-98e5-de772ebb15ba:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
30deb495-ac89-45d6-96c5-16a53668e784:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
be4e3e29-1617-4906-9844-12dc9bc66cf0:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
e14343b6-1883-4b91-8e4b-c7f4fd05b5a6:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
7ea583c6-2dcf-40a6-a6fc-049b38cf6d4c:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
45ec8aea-8dad-4f35-a7fa-712c38ad926f:sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
Expected behavior
解决思路：
chmod 0440 /etc/sudo.conf
chmod 0440 /etc/sudoers
chown root:root /etc/sudo.conf
chown root:root /etc/sudoers
chown root:root /usr/libexec/sudo/sudoers.so
chown root:root /usr/bin/sudo
问题：
执行以上命令赋权，执行一次之后，没问题，再执行一次 就出现问题
Your environment

Linkis version used: 1.1.2
Environment name and version:

cdh-5.14.2
hdp-3.1.5
hive-2.1.1
spark-3.2.1
scala-2.12.2
jdk 1.8.0_121
....

Anything else
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

建议尝试容器内配置hadoop免密sudo权限。参考链接：
It is recommended to try to configure Hadoop secret free sudo permission in the container. Reference link:
https://linkis.apache.org/zh-CN/docs/1.2.0/deployment/quick-deploy/


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 935 ms

Resolved: Bofrost.lu performance has improved in ca3238c.


[RFC]: Add C implementation for @stdlib/stats/base/dists/signrank/cdf

Description
This RFC proposes adding a C implementation, including a Node.js native addon, C benchmarks, and C examples, for the @stdlib/stats/base/dists/signrank/cdf package.
When adding support, the following tasks should be completed:

A C source implementation should be added to a src folder within the package's directory.
A native add-on interface should be added in order to call the C implementation from JavaScript.
A JavaScript file should be added to the lib folder to allow benchmarking and unit testing the native implementation from JavaScript.
A new test file should be created which includes unit tests testing against expected behavior.
C benchmarks should be added which measure performance for the C source implementation.
A file containing C examples should be added to demonstrate example usage.
JavaScript benchmarks should be added which measure performance for the native add-on.
Build and configuration files should be added to allow compiling and running the C source implementation using project make commands (as documented below).
The README should be updated to include documentation for the added C API.

To provide a concrete example of what a PR adding the desired method should contain, see https://github.com/stdlib-js/stdlib/pull/3354, which is a PR adding a C implementation for the CDF of an arcsine distribution. This should provide an idea of what is expected.
Prerequisites

Review JavaScript implementation in lib/main.js and its required modules to identify all stdlib functions used.
Verify C implementations exist for each required function.

Related Issues
#3355
Questions
No.
Other
Once the implementation is ready including C examples and benchmarks, we should be able to run the following make commands.
Build native add-on
NODE_ADDONS_PATTERN="@stdlib/stats/base/dists/signrank/cdf" make install-node-addons

Run C examples
make examples-c-files<EMAIL_ADDRESS>
Run C benchmarks
make benchmark-c-files<EMAIL_ADDRESS>
Run JavaScript benchmarks
make benchmark-javascript-files<EMAIL_ADDRESS>
Run all tests
make<EMAIL_ADDRESS>test

Notes

If you are interested in contributing a PR which addresses this RFC and are a first-time contributor or not yet familiar with our project conventions, please minimize the submission of LLM-generated code. Please consult our contributing guidelines and the associated development guide. Failure to respect project conventions will result in your PR being rejected without review. Thank you for understanding!

Checklist

[x] I have read and understood the Code of Conduct.
[x] Searched for existing issues and pull requests.
[x] The issue name begins with RFC:.

Hey @Planeshifter @domoritz @stdlib-bot, the C implementation for @stdlib/stats/base/dists/signrank/cdf/lib/weights.js does not exist. So how should I proceed?


Revert "Run proto-build automatically with GitHub Actions (#24)"

This reverts commit 95371cf40d5432194c2201037bddc90d610ec96f.
Per #62 it appears prost-build generates files with a somewhat nondeterministic ordering, triggering spurious PRs even when nothing is changed.
For an auto-rebuild to be helpful the build needs to be fully deterministic.

Closing this due to the non-determinism (see also #65)

That's an interesting suggestion and might resolve some of the problems

Will open another PR that scopes when this action runs


return realpath to fix issues with symlinks

trivial fix for a symlinked file issue

Current coverage is 65.59% (diff: 0.00%)

Merging #1725 into master will not change coverage

@@             master      #1725   diff @@
==========================================
  Files            54         54
  Lines          6168       6168
  Methods           0          0
  Messages          0          0
  Branches       1215       1215
==========================================
  Hits           4046       4046
  Misses         1908       1908
  Partials        214        214

Powered by Codecov. Last update b70a005...3c665ec

Seems fine, only affects RRD.

@edlitmus Do you know if this fixes https://github.com/graphite-project/graphite-web/issues/361?

It might: in the relevant rrdtool code it uses realpath(3) which should resolve symlinks, but we found that adding this helped us with an issue where RRDs were not getting flushed properly before graphite queried them.


exception when trying to use the software

hello,
i have this exception when i try to execute cuttlefish:
terminate called after throwing an instance of 'CThreadCancellationException'
the command i use is : cuttlefish build -l list-meta -o metacuttle  -k 31 --ref -m 1024 -t 32

HI @PandorasRed:
Thanks for using Cuttlefish! What's the type of the input files that you're trying to use here, i.e. are these FASTQ or FASTA?

its Fastq, didn't check and i was thinking i was working with fasta file, i have changed the ref to read and add the cutoff option for my test and it seems to run correctly now, thank for pointing it

Hi @PandorasRed, thanks for letting us know!


fix(runner): binary path to run

Currently shiika run is broken due to the run command tring to using out_path without ./ prefix, and this leads to let the OS tries to find the binary from PATH.

Merged! Thanks.


Can't see image preview for the NFT template.

Overview
I can't see the image preview for the NFT template.
To reproduce
Go to 'http://<IP_ADDRESS>:3000/releases', the image is just blank.
Go to 'http://<IP_ADDRESS>:3000/releases/11111', can see the image.
The image URI of the image is not correct.
Screenshots

Desktop (if applicable):

ubuntu 20

Hey @BeyondSpace609520, most likely this is due to the files not being made public in the CMS, or the CMS_URL not being a publicly accessible one. Going by your second screenshot, my guess is on the latter.

Still working through some issues running AlgoMart via docker-compose up, so for now I recommend running this via npm run dev directly instead.

Thanks for your help @smonn. I will close this issue.


Adds JSON Exporter

@zverok - I've removed the :orient option as per the review. But this now means that to_json will always return something like an Array of (nested) Hashes, rather than other (manipulation) options like Hash of Hashes or Array of Arrays. :-/

Whats the update on this issue?

@v0dro - I've added :orient and block manipulation, as per discussion on issue #10. Requires a final review.


Use locateFile in run_modularized

This changes run_modularized to specifically look in the same directory for *.wasm and *.data files as it does for their *.js wrappers. This has not been a problem until now as this is the default behaviour for *.wasm files, but with the addition of the upcoming vim recipe it is not enough. vim ships with a set of runtime config files that are packaged in a standard way in a vim.data file, and is loaded in a slightly different way by vim.js which the default behaviour doesn't cover when running in a node context as run_modularized does.
So here locateFile is specified when loading the wasm package so that *.data and *.wasm are correctly loaded. This is the same solution as used in cockle:
https://github.com/jupyterlite/cockle/blob/430ad63653e7c4a3ad9beb7267a7f4dc2c3176a9/src/commands/wasm_command_runner.ts#L104
except that the base path/URL is specified externally in cockle and here it is determined by the local path to the *.js file.

thanks!  Feel free to merge


word format of post's title

Is there a way to change title's font?
I realised that with the font style "classic" i can't put emphasis on words. So i switched back to "default".
However, titles are italic by default, is it possible to change it so i can format word appearances and put emphasis on words?

For various reasons, Academic does not support Markdown in the title of blog posts etc. The exception is the title field of homepage widgets.

Ok thanks for your clarification. Have a nice day
Il Gio 30 Ago 2018, 12:31 PM gcushen<EMAIL_ADDRESS>ha scritto:

For various reasons, Academic does not support Markdown in the title of
blog posts etc. The exception is the title field of homepage widgets.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gcushen/hugo-academic/issues/666#issuecomment-417422194,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM8FZg8vrVRplh3kJrg1oMiVLDbQVBsmks5uWC-UgaJpZM4WSu1E
.


Added Audio file- Illustration of Activity Lifecycle

Description 📜
                     05.1 Illustrations of Activity Lifecycle - ` " Added Audio File " `

Fixed #2361
Type of change 📝

[x] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)

Domain of Contribution 📊

[x] Android Dev #(Kotlin)

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Hey @rahulsain , Checkout this PR and if any mistake is not there , Kindly merge it .
Thanks


feat: Add testID props to card

Motivation
The Card component can take a testID props following the documentation : https://callstack.github.io/react-native-paper/card.html#testID

Test plan

@DCKT Thanks! I see you are really trying to push this project forward. What would you say about having write access so you can help with reviewing/merging PRs in a future? This project needs a good maintainer and I don't that much time recently to handle it on my own.

Hi @Trancever I would be happy ! I'm heavily using this library at my work & for some side-projects so it could be much faster to improve this lib. 😄

I sent you an invite. If you have any questions, feel free to ask me here or on Callstack's discord.


Add update Entity feature

Added the update Entity feature and tests

  indices: ["ParititionKey", "RowKey"]

Should be a typo, can you help update it to ParititionKey?

Refers to: src/table/persistence/LokiTableMetadataStore.ts:59 in 3221cb0. [](commit_id = 3221cb0a22e69e3b86980f7558a2ca0ac3f62da4, deletion_comment = False)

General looks good! Minor comments provided.

Take another run


Test: Remove dependency on SqlServer from EFCore.Design.Tests

With recent changes in RevEng testsing EFCore.Design.Tests now depends on SqlServer. That is due to mainly 3 tests.

ScaffoldingTypeMapperSqlServerTest - to verify if our scaffolding type mapper is working correctly.
RelationalScaffoldingModelFactoryTest - Mainly, to evaluate if we are passing correct arguments to scaffolding type mapper.
ModelSnapshotSqlServerTest - To verify generated model snapshot.

For all of above, the main reason to use SqlServer is typemapper, which is needed for ScaffoldingTypeMapper & CoreConventionSetBuilder
We can add a fake type mapper which is rich enough to allow us to test each facet and remove dependency from SqlServer.

EF Triage: We have a type mapper for testing, but we need to make it richer so we can use it for this.


not able to retrieve metadata from FAISS instance

Checklist

[X] I added a very descriptive title to this issue.
[X] I included a link to the documentation page I am referring to (if applicable).

Issue with current documentation:

Idea or request for content:
below's the code
# Categorize documents
documents_dict = {
    'amd': DirectoryLoader('/content/amd', glob="*.pdf", loader_cls=PyPDFLoader).load(),
    'engie': DirectoryLoader('/content/engie', glob="*.pdf", loader_cls=PyPDFLoader).load(),
    # Add more categories as needed
}

# Create a vector database and a retriever for each category
vector_stores = {}
retrievers = {}

class MyTextSplitter(RecursiveCharacterTextSplitter):
    def split_documents(self, documents):
        chunks = super().split_documents(documents)
        for document, chunk in zip(documents, chunks):
            chunk.metadata['source'] = document.metadata['source']
        return chunks

text_splitter = MyTextSplitter(chunk_size=1000,
                                chunk_overlap=100)

for category, docs in documents_dict.items():
    texts = text_splitter.split_documents(docs)
    vector_store = FAISS.from_documents(texts, embeddings)
    retriever = vector_store.as_retriever(search_kwargs={"k": 5})

    vector_stores[category] = vector_store
    retrievers[category] = retriever

# Answer a question related to 'Cricket'
category = 'amd'
qa_chain = RetrievalQA.from_chain_type(llm=OpenAI(temperature=0.2),
                                          chain_type="stuff",
                                          retriever=retrievers[category],
                                          return_source_documents=True)

# Format the prompt using the template
context = ""
# question = "what's the final provision of dhl?"
question = "what for it strives?"
formatted_prompt = prompt_template.format(context=context, question=question)

# Pass the formatted prompt to the RetrievalQA function
llm_response = qa_chain(formatted_prompt)
process_llm_response(llm_response)

faiss_instance = vector_stores['amd']  # Assuming this is your FAISS instance

Now, i wanna extract the metadata and see what components are present in faiss_instance. Can you help me with code?

🤖
Hey @nithinreddyyyyyy, great to see you diving into another intriguing challenge! How's everything going on your end?
To extract and view the metadata components present in your FAISS instance using the LangChain framework, you can use the docstore attribute of the FAISS instance. The docstore attribute is an instance of InMemoryDocstore which stores the documents and their associated metadata.
Here is how you can extract and view the metadata from your faiss_instance:
# Extract and view the metadata
for doc_id, document in faiss_instance.docstore.items():
    print(f"Document ID: {doc_id}")
    print(f"Metadata: {document.metadata}")

In this code, faiss_instance.docstore.items() returns a list of tuples where each tuple contains a document ID and a Document object. The Document object has a metadata attribute which contains the metadata associated with the document.
This is supported by the following code from the LangChain repository:
docsearch = FAISS.from_texts(texts, FakeEmbeddings(), metadatas=metadatas)
expected_docstore = InMemoryDocstore(
    {
        docsearch.index_to_docstore_id[0]: Document(
            page_content="foo", metadata={"page": 0}
        ),
        docsearch.index_to_docstore_id[1]: Document(
            page_content="bar", metadata={"page": 1}
        ),
        docsearch.index_to_docstore_id[2]: Document(
            page_content="baz", metadata={"page": 2}
        ),
    }
)
assert docsearch.docstore.__dict__ == expected_docstore.__dict__

In this code, docsearch.docstore.__dict__ is used to compare the actual and expected docstores, which implies that the docstore attribute of the FAISS instance contains the documents and their associated metadata.
You can find this code in the libs/community/tests/unit_tests/vectorstores/test_faiss.py file in the LangChain repository.
Please let me know if you have any other questions or need further clarification.
Sources

libs/community/tests/unit_tests/vectorstores/test_faiss.py
libs/community/langchain_community/vectorstores/faiss.py

About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
If you want to continue the conversation, start your reply with @dosu-bot.

but it has returned below error
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
[<ipython-input-17-2a5fdb7287ff>](https://localhost:8080/#) in <cell line: 2>()
      1 # Extract and view the metadata
----> 2 for doc_id, document in faiss_instance.docstore.items():
      3     print(f"Document ID: {doc_id}")
      4     print(f"Metadata: {document.metadata}")

AttributeError: 'InMemoryDocstore' object has no attribute 'items'

Can you help me with this?

🤖
Based on the error message you provided, it seems like you're trying to use the items() method on an 'InMemoryDocstore' object, which doesn't exist. The 'InMemoryDocstore' class in the LangChain framework doesn't have an 'items' method or attribute.
Instead, you can access the _dict attribute of the 'InMemoryDocstore' object, which is a dictionary that stores the documents. Here's how you can modify your code:
# Extract and view the metadata
for doc_id, document in faiss_instance.docstore._dict.items():
    print(f"Document ID: {doc_id}")
    print(f"Metadata: {document.metadata}")

This should allow you to iterate over the documents stored in the 'InMemoryDocstore' object and print out their IDs and metadata.
Please note that the _dict attribute is intended to be private and direct access to it may not be the best practice. However, given the current design of the 'InMemoryDocstore' class, this is the way to access the stored documents.
For more information about the 'InMemoryDocstore' class, you can refer to the source code in the LangChain repository.
Let me know if this helps or if you have any other questions.
Sources

libs/community/langchain_community/docstore/in_memory.py
libs/langchain/langchain/docstore/in_memory.py

About Dosu

unable to see the content, it is returning below
Document ID: f289bd42-ad08-4511-9aec-5cf054e2ed0f
Metadata: {'source': '/content/amd/1.pdf', 'page': 0}
Document ID: f1cec78c-a620-4060-aa32-7b44b165bbd7
Metadata: {'source': '/content/amd/1.pdf', 'page': 0}
Document ID: a05054ef-9d83-4265-adc6-92b55b647e0d
Metadata: {'source': '/content/amd/1.pdf', 'page': 0}
Document ID: 716134bd-dba7-414c-b87b-32f75c726022
Metadata: {'source': '/content/amd/1.pdf', 'page': 0}
Document ID: 8b63b69d-7f93-469f-ab95-5ff99c8de6b8
Metadata: {'source': '/content/amd/1.pdf', 'page': 1}
Document ID: 3b4adc9e-11ab-41cf-94e6-3f11c05e1383
Metadata: {'source': '/content/amd/1.pdf', 'page': 1}
Document ID: b7e21a48-3d93-4cd6-bffb-d540e7ae7ada
Metadata: {'source': '/content/amd/1.pdf', 'page': 1}

unable to see page_content. Can you have a look into it?


Fix: check event.defaultPrevented before handling events to avoid conflicts with other plugins

Hi, thank you for maintaining this plugin which is important for the community!
As stated in the developer documentation, a community plugin has to check event.defaultPrevented before handling editor-paste and editor-drop events to see if other plugins already handle the event.

https://docs.obsidian.md/Reference/TypeScript+API/Workspace/on_12
https://docs.obsidian.md/Reference/TypeScript+API/Workspace/on_13

So I added the two lines according to this. This change will fix conflicts with other plugins such as https://github.com/RyotaUshio/obsidian-advanced-external-links (sorry this is my plugin).

Makes sense, thanks!


cloud proxy having lag spikes on random moments

Dear,
I am experiencing lag spikes on my GKE cluster that runs a flask restplus api. I think the problem is in the cloud sql proxy that calls the database. It seems to happen on random moments and is indendent on the amount of traffic. It's the first time I am using this combination so i'm not sure if it is really cloud sql but i found similar issues online. Checking the logs gives these kinds of errors for a 20 second lag spike:
2017/11/19 05:08:28 New connection for "df002dds:europe-west1:signal-database"
2017/11/19 05:08:28 Client closed local connection on <IP_ADDRESS>:3306
2017/11/19 05:08:28 New connection for "df002dds:europe-west1:signal-database"
2017/11/19 05:08:28 Client closed local connection on <IP_ADDRESS>:3306
2017/11/19 05:08:48 New connection for "df002dds:europe-west1:signal-database"
2017/11/19 05:08:48 Client closed local connection on <IP_ADDRESS>:3306
Any ideas?
In attachment some more logs. The kubernetes commands also seem to be related to these lag spikes.

@bcoghe that might be related to https://github.com/GoogleCloudPlatform/cloudsql-proxy/issues/94

This might be caused by #94, have to say sorry that I'm just aware of this problem.  I've created an internal ticket and it will be prioritized.

Closing since this looks to be a dupe.


Documentation !

Could you be more explicit about how to link the facebook app to your faceboook page ?

Unsupported post request. Object with ID 'XXX' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api


Toggle checkbox in preview could toggle in source

Since #9, checkboxes are togglable in the preview (which is great!), but doing so has no impact on the source.
Do you think it would be possible to toggle in the source upon toggling in the preview?

Anything is possible... with a PR :)

Until (if) this is handled, maybe input should be disabled?
It's a bit confusing to toggle checkboxes in the preview without it propagating to source. Changes are lost on closing the preview tab.
This is just a suggestion! It's not breaking to me because I handle this (for the most part) with custom CSS.

As for implementing this, is there any vscode API that exposes functions in the preview? More specifically: the little bit of magic logic that goes from preview to editor on double click, dropping you on the line you clicked. The part that computes the line you clicked, is it part of an API an extension can use?
Alternatively, could you reference the part of the vscode codebase that does this? This feature may be pretty easy to implement if we use that logic as reference.
I looked into the new language service (congratz on that!) but it doesn't seem to concern preview, only the markdown document itself. Please tell me if I'm mistaken.

I had a look around about how to get this feature in, and I think one needs to use markdown.previewScripts as per official VsCode extension programming guide. I tried to look at the mermaid example they mention, but immediately got stuck failing to locate the file they specify within the repository. I guess the dist part indicates it's generated out of something else for distribution. Maybe someone with more than zero web dev experience can progress further than me.


Release version 4.2

The last python-linkedin release is more than one year old. In the meantime, you got many fixes and Python 3 support. Can you please upload the 4.2 version to PyPI? Thanks!

@ozgur thoughts?

@ozgur


Updated section titles to sentence case

Changed from title case to sentence case
https://sendgrid.com/docs/for-developers/partners/azure/

Closes #

Hello @schmeiss,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

Hello @schmeiss,Thanks again for the PR!                                         We noticed that you have earned 4 out of the 5 points needed to receive glorious SendGrid Hacktoberfest swag.                                         Please take a moment to checkout this link to find more issues to get you past the required threshold.                                         Also, please be sure that you have officially registered here.                                         Thank you and Happy Hacktobering!                                         Team SendGrid DX


Cover src/server/session.ts - Session API with tests

Since we now export Session in tslssl.js, we should add tests for its public API.

@weswigham care to send us some tests :)

@mhegazy will do

Thanks @weswigham!


Retrieving an array of rows from a table

Hi,
I want to extract from AirTable each row of my table and make it onto an array.
Each row is a bubble with different attributes (columns of my table) a name, a URL to a logo and a size.
I would like to be able to extract from AirTable all of the rows (bubbles), iterate on them like I would do with a for loop.
To be more precise : I would like to obtain an array of sub arrays that are my rows from AirTable.
I don't know how to implement that... any idea ? Thanks
PS: I need to do so in a GameScene because each row will generate a SpriteKitNode

Hi @jeadev!
Sorry for the long delay. If this is still relevant to you, I created a small example of how you can parse the records from a table in your Airtable base.
The package uses Combine as its interface for returning the status of operations performed (create, delete) or the data requested (list, get). Given that Combine is a new framework, let's say you're using closures instead of Combine on your application.
I'm considering you have a class to encapsulate communication with Airtable. You can do something like the following:
import Combine
import AirtableKit

class Service {

    private let airtable = Airtable(baseID: "<your base id>", apiKey: "<your API key>")
    private var subscriptions: [AnyCancellable] = []

    func listStudents(completion: @escaping (Result<[[String]], Error>) -> Void) {
        airtable.list(tableName: "<your table name>")
            .sink { completionEvent in
                switch completionEvent {
                case .finished:
                    // you can ignore this
                    print("successfully finished")
                case .failure(let error):
                    print("got error \(error)")
                    completion(.failure(error))
                }
            } receiveValue: { records in
                print("records \(records)")

                let content = records.map { record -> [String] in
                    // map your record/row here

                    var result = [String]()

                    if let name = record.fields["Name"] as? String {
                        result.append(name)
                    }

                    if let logo = record.attachments["Picture"]?.first {
                        let logoUrl = logo.url.absoluteString
                        let logoSize = logo.metadata["size"] as? Int ?? 0

                        result.append(logoUrl)
                        result.append("\(logoSize)")
                    }

                    return result
                }

                completion(.success(content))

            }
            .store(in: &subscriptions)
    }
}

Now to use it on your app:
let service = Service()

func getDataFromAirtable() {
    service.listStudents { result in
        switch result {
        case .success(let rows):
            // do something with rows
            print("result: success \(rows)")
        case .failure(let error):
            // handle this as you wish
            print("result: error \(error)")
        }
    }
}

I haven't written SpriteKit code for some time now, but I think you can use this as a starting point to implement what you need.
I'll close this for now, but feel free to comment and I'll see how I can help.


Wrap ContentFile in a file-like object with a filename and content_type.

We use ImageKit to scale images and Rackspace Cloud (formerly Mosso) to serve them. Unfortunately, we've found that our scaled images (spec files) are served with an incorrect Content-Type—application/octet-stream—causing browsers to download the images instead of displaying them. Our original source images, however, are served with the correct Content-Type, and they are also hosted on Rackspace Cloud. So what gives?
When users upload files to our site, Django reads the content type from the multipart MIME header and sets a content_type attribute on the UploadedFile object created to handle the uploaded file. The django-storages Mosso back-end that we use then references that content_type attribute when posting the file to Rackspace Cloud, allowing that file to be served with the appropriate Content-Type header.
ImageKit does not set such an attribute, however, so neither django-storages nor the cloudfiles storage backend can set a content type when saving the spec files out to the cloud. This patch adds an extra layer of indirection that allows us to tack some attributes (name and content_type) onto the underlying ContentFile—which we can't do with StringIO since that's a native type.
I debated whether I should modify ImageKit, django-storages, or the cloudfiles backend, but ultimately decided ImageKit was the right place since django-storages and cloudfiles already provide mechanisms to set content type (by deferring to the content_type or name of the source file), and Django accommodates that by setting a content_type attribute on uploaded files. Setting name and content_type in ImageKit seems like a simple and inexpensive solution (work-around?) to the problem.

Thanks for the pull request…and the thoughtful explanation! I agree; this seems like the easiest place to address the issue.


no output wav files

Ubuntu 18.04, titan xp. cuda10.1
./waveglow_tts filename.txt outputdir can not output any wav file

Can you share the exact output/error full-trace?

sorry  my fault. I commented out DEBUG things. and  log_d is void(). audio.log not been called. everything ok now.


read_only tests insufficient

I thought I'd open an issue. Per twitter, this test: https://github.com/tcbrindle/flux/blob/b423b21d37f510f7793b6f1bf4e6e6f187fc9a4d/test/test_read_only.cpp#L18-L35
doesn't actually test anything about read_only, since flux::ref(arr) is already a read-only sequence, so flux::read_only(flux::ref(arr)) (correctly!) just gives you back flux::ref(arr). You want flux::mut_ref(arr) there.
This also begs the question of to what extend this is a valid implementation of read_only:
 struct read_only_fn {
     template <adaptable_sequence Seq>
     [[nodiscard]]
     constexpr auto operator()(Seq&& seq) const -> read_only_sequence auto
     {
         if constexpr (read_only_sequence<Seq>) {
             return FLUX_FWD(seq);
         } else {
-            return read_only_adaptor<std::decay_t<Seq>>(FLUX_FWD(seq));
+            return flux::map(FLUX_FWD(seq), [](auto&& elem) -> const_element_t<Seq> {
+                return FLUX_FWD(elem);
+            });
         }
     }
 };

It's very nearly correct, the only thing that should break is the contiguous_sequence check in the test. The fact that read_only is a map, just one that's potentially contiguous, feels like it should be implemented like this:
template <class T>
struct cast_to_const {
    template <class U>
    constexpr auto operator()(U&& rhs) const -> T {
        return FLUX_FWD(rhs);
    }
};

template <sequence Base>
    requires (not read_only_sequence<Base>)
struct read_only_adaptor : map_adaptor<Base, cast_to_const<const_element_t<Base>>>
{
    using map = map_adaptor<Base, cast_to_const<const_element_t<Base>>>;

public:
    constexpr read_only_adaptor(decays_to<Base> auto&& base)
        : map(FLUX_FWD(base), cast_to_const<const_element_t<Base>>{})
    {}

    struct flux_sequence_traits : map::flux_sequence_traits {
        static constexpr auto data(auto& self)
            requires contiguous_sequence<Base>
        {
            using P = std::add_pointer_t<std::remove_reference_t<const_element_t<Base>>>;
            return static_cast<P>(flux::data(self.base_)); // error: self.base_ is private
        }
    };
};

But that doesn't quite work. Another approach would be to have flux::read_only just return flux::map using the appopriate cast_to_const and just have map recognize it. That feels a little backwards (why is map adding a function that is only usable for read_only) but avoids all the boilerplate too.

The test is easily fixable, so I'll do that (I think it dates from before I flipped the meaning of ref() and added mut_ref(), or maybe I just made a mistake).
Having read_only_adaptor inherit from map_adaptor is a neat idea (although I don't do it anywhere else). Does the access check work if you replace self.base_ with self.base()?

The test is easily fixable, so I'll do that (I think it dates from before I flipped the meaning of ref() and added mut_ref(), or maybe I just made a mistake).

👍

Having read_only_adaptor inherit from map_adaptor is a neat idea (although I don't do it anywhere else). Does the access check work if you replace self.base_ with self.base()?

Oh yeah, that totally works! So yeah, my ... what... 25ish line implementation above there passes all the tests (with mut_ref fixed).

I was literally just about to write that I've just tried it and it works! I'll have a PR in a couple of minutes


Tracking issue for custom-named-profile (RFC 2678)

RFC: https://github.com/rust-lang/rfcs/pull/2678
Implementation: https://github.com/rust-lang/cargo/pull/6989
Docs: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#custom-named-profiles
Summary
Adds user-defined profile names.
Unresolved questions:

[X] Bikeshedding the inherits keyword name. Decided it should be fine.
[X] Should we keep user profiles under a Toml namespace of their own? Decided to use a flat namespace for simplicity.

For example:
[profile.custom.release-lto]
inherits = "release"
lto = true

* If so, should the `inherits` keyword be able to refer to custom and pre-defined profiles differently?

[X] Profile names would collide with rustc target names under target/. Should
the output directory be also under a different namespace, e.g.
target/custom/release-lto? Decided to use a flat namespace.
[X] Do we really need pre-defined profiles for test, bench, or can we make them obsolete? Will keep them for now.
[X] Is it worthwhile keeping test and bench outputs in target/debug and target/release? Doing so would save compilation time and space. Deferred for future target layout reorg.

[X] If so, is the dir-name keyword necessary?  Alternatively, we can hand-code the output directory of bench and test to be release and debug to keep the current behavior. This may be sufficient until a "global binary cache" feature is implemented, or a per-workspace target/.cache  (related discussion).  Decided to not expose dir-name and just leave it as a special-case for the built-in profiles.

[X] Should the PROFILE environment variable in build scripts be deprecated?  Currently it only sets DEBUG or RELEASE, which isn't really useful.  Should guide users to use DEBUG and OPT_LEVEL instead. Decided to deprecate PROFILE (via documentation).
Update these commands to support custom named profiles:

[X] check
[X] rustc
[X] fix
Any others? Fixed #9685

[X] What is the interaction with the (future) build profile and unified build directories?  Reserved several names in #9685 for adding in the future.

Consider making an uber profile above dev/release where build settings could be set (root?)?

[X] How should automatic target-based profile selection work? For example, today, cargo build --all-targets automatically uses the "test" profile for tests. IIRC, named-profiles changes that behavior. I lean towards the original RFC, where it retains the original behavior, unless --profile is specified, but I am uncertain. Decided to go with a single profile per cargo invocation.
[X] test inheriting from dev is a change in behavior, will that be a problem? Decided it shouldn't be a major issue.

A few things that came up during the PR:
How should target-specific profiles be chosen?
Stable cargo uses a variety of factors to choose the profile per compilation unit:

The --release flag.
The cargo target (test, bench, etc.).
The command (mode).
Which package (for profile overrides).

Dependencies are also special, in that when building a test, the test itself will use the "test" profile, but the dependencies will use "dev". This is done under the assumption that if the test profile is different from dev, you may not want to rebuild the world. The named-profiles feature changes this so that dependencies use the same profile as what is being built. Generally for most projects, this won't matter since most projects keep the test and dev profiles the same.
Some people have found this confusing, and it is a little hard to document clearly. However, it is intended to be intuitive (test targets use the "test" profile). The addition of named profiles makes this even more complex and possibly confusing. Try to answer the question of which profile each unit should use for the following:

cargo build --test t1
cargo test --test t1
cargo test --test t1 --profile=foo
cargo build --profile=foo --all-targets

One option is to toss away the per-target logic, and use a uniform profile for everything.
Another option is to try to have some elaborate system that tries to retain something like the old behavior.
Another option is to have some sort of target-specific profiles. That is, profile.test could be marked as being the default profile for all tests.
This is a difficult problem, and I'm not really sure where to go with it.
Add named profile support to rustc, check, and fix.
This is a bit tricky, since these commands historically had their own flags:

cargo rustc:

--profile=dev: build (default)
--profile=test: test mode and profile (enables cfg(test), etc.)
--profile=bench: bench mode and profile
--profile=check: check mode

cargo check and cargo fix:

--profile=test: Enables cfg(test), does not change the actual profile.

One option is to add a new flag (--mode?) to take over the old behavior. It's questionable of how these should behave, especially considering backwards compatibility, and consistency with other commands (would cargo build --profile=test enable test mode?). The path forward isn't clear to me.

This is something l look very much forward to. Is there an estimate of when this will become stable?

Is there something stalling this feature?

@lu-zero I have updated the issue text with some things that need to be done. Someone needs to do the work to finish the implementation, and work on making decisions for some of the design issues. Also, I have not heard of anyone using this, so I do not know if it has gotten any testing.

:wave: used this for profiling with flamegraph, works as anticipated (will re-run checks with a current nightly again)

Just to point out another use-case, we want to enable overflow-checks = true only for some profiles

Wanted to point out one more use case - we want to run code coverage and atm it is recommended to customize build via RUSTFLAGS which not always works: https://github.com/rust-lang/rust/issues/78011 . It seems adding coverage profile would have helped.

Another use case: we want to enable panic = "abort" in a WASM release to reduce binary size, but in a non-WASM release, we want the default panic = "unwind".  It would be convenient if we could define [profile.release] alongside [profile.custom.release=wasm].

Posted #9685 with some updates to move this towards stabilization.

Some people have found this confusing

To give some estimate for the level of confusion: I am trying to debug an issue which depends on a particular opt-level. I have a test for it, and run it with --release. The code that misbehaves is a dev-dep of the test. Although at one point I was pretty intimately familiar with cargo profile selection logic, at this point I am feeling pretty lost and just modify all profiles together. What exacerbates the issue is that there's very little feedback about what profile is active -- it's hard to experimentally figure out what profile is used for what code.
I feel pretty strongly that we should go forward with https://github.com/rust-lang/cargo/issues/2085 and make (via edition or Cargo.toml opt-in) --release always use the release profile, for all (non-build) units.

One gotcha I hit with when using this is that the PROFILE variable is not set to match the named profile, it instead contains "release" if the named profile inherits from release, and "debug" otherwise.
Is that expected behavior? I see above that you guys are considering deprecating the PROFILE environment variable.
However, we are using that variable in build scripts that need to try to find the target dir, from the out-dir:
https://github.com/mobilecoinfoundation/mobilecoin/blob/bcb3e26cc85afd3a250f2109e9cd388c0e5c814a/util/build/script/src/env.rs#L226
What do you recommend that we do here if we also want to use named profiles? Will there be another variable that is defined to equal the subdirectory of target? Or we will have to find another approach?

@garbageslam For now, we do not intend to expose the profile name to build scripts.  Per https://doc.rust-lang.org/cargo/reference/build-scripts.html#outputs-of-the-build-script, build scripts are not intended to write or interact with directories outside of its OUT_DIR.

@ehuss one way that we currently use profiles is, we have build.rs that invoke cargo to build targets (specifically SGX enclaves) that a rust binary e.g. a server relies on at run time. (we have to have cargo calling cargo in order to prevent feature unification, the SGX targets typically build as no_std for us, while the server uses the standard library).
Because PROFILE is exposed to the build.rs, we can make sure that the inner cargo uses release if the outer cargo uses release and so on. If PROFILE will go away then we may still be able to do something by inspecting DEBUG and OPT_LEVEL but it will be messier.

I have posted a proposal to stabilize this in #9943.


feat!: remove match type argument

Pull Request Description
Description:
This PR is to remove match type argument as it can be confusing which one to use - search is sufficient and the other types can be checked as follows:

match is search pattern with '^' prefix
fullmatch is search pattern with '^' prefix and '$' suffix

Checklist

[x] I have added the appropriate prefix  to the pull request title
[x] The CI tests are passing for this pull request.
[x] The pre-commit run -a hooks are passing for this pull request.

This PR is included in version 0.5.0 :tada:


The number of consumers in consumer groups?

Can anyone tells me how to configure the number of consumers in sarama's consumer group?

The number of consumers in a consumer group is simply defined by how many clients you connect to the cluster with the same unique group name


Little Typo

Under the question "How can Bookings-associated mailboxes in Exchange be identified?", there's a nice little PowerShell script. The "Where-Object" data needs to have a wildcard on each side of the @ symbol, so that it's:
Where-Object {($_.User -like '*@*')}
Thanks!

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

ID: f7484dd4-5d94-dd6c-0dbe-551c852677c1
Version Independent ID: 257d60e2-9313-e08b-dccf-120cb4b30f5b
Content: Microsoft Bookings Frequently Asked Questions
Content Source: microsoft-365/bookings/bookings-faq.md
Service: bookings
GitHub Login: @kwekuako
Microsoft Alias: kwekua

@geektbee Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4477
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @geektbee  Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


SNOW-656580 readd geometry changes

Please answer these questions before submitting your pull requests. Thanks!

What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
Fixes #SNOW-656580

Fill out the following pre-review checklist:

[x] I am adding a new automated test(s) to verify correctness of my new code
[ ] I am adding new logging messages
[ ] I am adding a new telemetry message
[ ] I am adding new credentials
[ ] I am adding a new dependency

Please describe how your code solves the related issue.
Geometry changes were removed from main because we didn't want to release it with 1.5.1. Re-adding the changes in this PR.
Old PR: https://github.com/snowflakedb/snowpark-python/pull/873

Successful pre-commit run with this branch: https://ci-dev-142.int.snowflakecomputing.com/job/PythonStoredProcBuildPrecommitTest/407/


Fix: show python and js as open beta

Fixes applandinc/board#86
Change messages that get displayed in project picker. Show that Python and JavaScript are in Open Beta. Remove Python feature flag.

:tada: This PR is included in version 0.32.2 :tada:
The release is available on:

v0.32.2
GitHub release

Your semantic-release bot :package::rocket:


Add support for 'default' locale when TLD is not found in config

If the current TLD is not found in the configuration file, a default locale could be used.
This would be useful for development.

This might be related to #19, I'll take a look when I have some spare time!


optionally add docker host to proxy excludes in env command

This adds a --no-proxy flag to the docker-machine env command.
When set it will take care of adding (and removing) the docker host to/from the NO_PROXY environment variable.
This helps using docker-machine with docker >=1.5 with local vm providers (e.g. fusion, virtualbox) in coporate networks where an http proxy is required for internet connectivity.
Since version 1.5 the docker client picks up the HTTP_PROXY environment variable when connecting to the docker daemon. This does not work well for the local vm use case. In that case the docker host is inside a local virtual network only reachable from the workstation itself.
@ehazlett This pull request also has the intention to illicit some feedback from you regarding this PR https://github.com/boot2docker/boot2docker-cli/pull/345 :)

@SvenDowideit your thoughts?

I haven't had time to review this but @databus23 I'd suggest you please break this down into several smaller functions- that's a lot of stuff for just one function to do.

@nathanleclaire Sure. I agree its quite a lot of code for one method and can be structured better. But before I spend more time on this can we agree that there is a problem and a solution would be considered for a merge?

@databus23 yes i think this would be beneficial

@databus23 Yes, I am in favor of the feature.
I have a question: If the user wants to connect to a remote instance, they will actually want to use the proxy to enable internet connectivity, no?  How is that case handled?
Also, side note for @ehazlett : this logic is really getting hairy enough that we should eventually move to using a text/template to generate these commands instead.

+1 for text/template -- there are a couple other places that could use that too.

@nathanleclaire Yes, for remote instances the user might actually need the proxy to get to the instance. Thats why I implemented it as an optional boolean flag --no-proxy. So the user has to explicitly set it e.g. docker-machine env dev --no-proxy. An optimisation could be to automatically set it for local vm providers (fusion, virtualbox, hyperv?) where using the proxy most certainly won't work.

@databus23 Ah, of course - the flag.  I'm sorry, I'm being thick due to this recent flurry of activity.  At any rate, if you break that into a few smaller functions and especially if you add some unit tests (for these new functions - don't feel responsible for cmdEnv in general), this PR will be looking in really good shape from my end.

Some guidance on how to structure the subroutines: please pass in the values from c.Bool() calls directly, as well as machineUrl and the variable for the shell.

@nathanleclaire I'm not sure I understand your guidance, could you maybe elaborate?

I'm not sure I understand your guidance, could you maybe elaborate?

Most important thing is to parse what you need out of cli.Context struct instead of passing it around.  We are trying to stop passing c to functions since IMO it shouldn't be needed outside of the cmd* functions.

@databus23 Any followup on this?

Not yet. But I'm still interested in seeing this in machine. #1676 is a duplicate of this issue btw.

I updates the pull request against latest master. This will add the docker host ip to the no_proxy environment variable if requested via docker env $NAME --no-proxy.
The unset case is not handled, so the ip will remain in the no_proxy environment variable in case docker env $NAME --unset is used. It's not that easy to add given the current way the text template is rendered. I don't think this is a show stopper though. In almost all cases the exclucded ips will be from private address spaces used by local vm providers on virtual network interfaces. Having an old entry lurking around in the no_proxy environment variable shouldn't be a big problem.
IMHO its definitely a smaller issue than docker machine not working with local vm providers in environments where an http_proxy is mandatory for internet access.
This fixes #1676 which has ben labeled help-wanted by @ehazlett.
Thoughts?

Nice, I'll make sure to take a look.

Rebased on top of current master. Circles is still in a moody.

Rebased on current master. All green.

This is rad!  Code looks pretty good.  Could I get you to add a section to docs/env.md explaining this feature?  Otherwise I worry people will not be able to find it.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "no_proxy_env" git@github.com:databus23/machine.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

@nathanleclaire documentation added.

Alright, sorry about this but I've just merged the rather large libmachine PR as well, which will introduce some conflicts.  I'll start working on rebasing this branch (want to get it merged quite soon) to that and then making a PR on your repo, feel free to do it yourself as well if you have time.  You can reach me on IRC to ask questions about the changes if you like: nathanleclaire

Update:  I have successfully rebased so you won't need to worry about that.  I will make a PR on your repo which you can merge (as well as add a few integration tests for this feature), and then we can merge this upstream!

@nathanleclaire you beat me to it by minutes. :)

:D

Carried it in my own PR to make things a little easier :+1:


[Soroban Merge] add announcement bar about the migration

Preview is available here:http://developers-pr311.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr311.previews.kube001.services.stellar-ops.com

I don't want toerge
On Fri, Feb 23, 2024, 11:04 AM Elliot Voris @.***>
wrote:

Merged #311 https://github.com/stellar/stellar-docs/pull/311 into main.
—
Reply to this email directly, view it on GitHub
https://github.com/stellar/stellar-docs/pull/311#event-11907220671, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A5LQRFKDTYQZMW72ADCYYUTYVDR2ZAVCNFSM6AAAAABDVQPSHKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRHEYDOMRSGA3DOMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Add option to specify user agent for link crawling

I will follow this up with a PR in the chat repository to use the user agent "WhatsApp/2" by default. This is because many dynamic links and other link previews serve specific social media tags for this user agent. For example, Signal also uses this user agent to crawl their link preview data.

Thanks for the PR!


Default filter on text fields now equals

I'm submitting a ...  (check one with "x")
[x ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/ceolter/ag-grid/blob/master/CONTRIBUTING.md#question

Current behavior
In the latest version 9.1.0 the default filter type on text is "equals"
Expected behavior
In previous versions this has been "contains"
Minimal reproduction of the problem with instructions

Create a grid with a text column and add a filter/floating filter - the default selection is "equals"
What is the motivation / use case for changing the behavior?

Behaviour was different in previous versions so is confusing to users
Please tell us about your environment:

Windows, IntelliJ Ultimate

ag-Grid version: X.X.X

Issue in 9.1.0 (not in 9.0.2)

Browser:

Chrome

Language: [all | TypeScript X.X | ES6/7 | ES5]
Angular2/Typescript

Experiencing the same issue with the new version (9.1.0) when using ag-grid in React. I believe most users would expect the default filtering using contains (as it was in older versions).
Maybe the grid could provide a way of setting the default filter/floating filter type on a column to the preferred type: equals, contains etc (didn't see a way to change that and changing the filter type order doesn't seem to affect the default). This is especially useful on floating filters where the user is less likely to go and change the filter type.

Hi!
Thanks for raising this, this is tracked by AG-486, it will be available in the next release.
Thanks

AG Grid 11.0.0 has been released, but I see no mention of AG-486.
In which release will this be fixed?

Hi,
It seems like we missed this in the release notes.
In case you haven't noticed this is available now in ag-grid
Text
filterOptions: If specified, limits the amount of options presented in the filter UI, it must be a string array containing some of the following values {equals, notEqual, contains, notContains, startsWith, endsWith}
defaultOption: If specified, changes the default filter option to one of {equals, notEqual, contains, notContains, startsWith, endsWith}. If not specified the default type is {contains}, if {contains} is not available because is removed using filterOptions, then the default is the first item in the filterOptions
Number
filterOptions: If specified, limits the amount of options presented in the filter UI, it must be a string array containing some of the following values {equals, notEquals, lessThanOrEqual, greaterThan, greaterThanOrEqual, inRange}
defaultOption: If specified, changes the default filter option to one of {equals, notEquals, lessThanOrEqual, greaterThan, greaterThanOrEqual, inRange}. If not specified the default type is {equals}, if {equals} is not available because is removed using filterOptions, then the default is the first item in the filterOptions
https://www.ag-grid.com/javascript-grid-filter-text
https://www.ag-grid.com/javascript-grid-filter-number


Messaging extensions: Missing Input.ChoiceSet options in adaptive card

Versions
botbuilder v4.11.0
nodejs v13.12.0
OS Ubuntu 18.04.3 LTS
Describe the bug
A messaging extension returns from search a list of items. After selecting an item from the list, an adaptive card is rendered containing the following items :

A single select  (Input.ChoiceSet -> style: 'compact', sMultiSelect: false)
A ShowCardAction -> shows another adaptive card containing a single select

The options of the single select are missing. When clicking on the showCardAction, the options of the select in the child adaptive card are present. When pasting the card in the chat, the options of both selects are missing. When replacing the single selects with radios (Input.ChoiceSet -> style: 'expanded', sMultiSelect: false), the options are present. The same card can be returned also from the bot and then everything is rendered correctly.
Expected behavior
The single select options are present after selecting the item from the search result of a message extension and after pasting the card in the chat
Screenshots

When an item from the search result is selected ->

When the card is pasted in the chat ->

When the bot returns the same card  ->

Thank you for the report, @rmincheva. Would you be willing to provide some additional information?

Repro steps
Links to any documentation or samples you've followed
The Adaptive Card JSON
The relevant parts of your messaging extension code
The relevant parts of your app manifest

@rmincheva as kyle  mentioned - Could you please share more details?

@rmincheva as kyle  mentioned - Could you please share more details?

Preconditions
A search based messaging extension with one parameter "query" is created. After the search request is executed a list of items is returned. After an item is selected(tapped) another request is made for retrieving additional data for the item and a detailed card is shown.
Steps to reproduce

Enter a search query.
Select an item -> A card is shown, containing a select "dummySelect", but the select options are missing.
Click the "Forward" action -> Another card is shown, containing a select "forwardAssignee" -> the options are present (this is correct).
Copy the card and paste it in a chat -> The select options of the "dummySelect" in the main card are missing.
Click the "Forward" action-> The select options of the "forwardAssignee" select are missing.

Message extension code
The following function is executed when the user enters the search query->
async function searchJobs(context, action) {
    const {httpConfig} = context
    const query = action.parameters.find(parameter => parameter.name === 'query')
    const jobs = await https.searchJobs({query: query && query.value, httpConfig})
    const attachments = jobs.map(job => {
        const {descriptionId, name, locale} = job
        const card = JobThumbnailCard({name})
        card.content.tap = {
            type: 'invoke',
            value: {
                commandId: messageCommands.getJobByDescriptionId,
                parameters: {
                    descriptionId,
                    locale
                }
            }
        }
        return {...card}
    })
    return MessageFactory.createListMessage(attachments)
}

After an item from the search result is clicked the following function is executed->
async function getJobByDescriptionId(context, action) {
    const {httpConfig} = context
    const {descriptionId, locale} = action.parameters
    const job = await https.getJobByDescriptionId({descriptionId, locale, httpConfig})
     .
     .
     .
    const assignees = [
        {
            name: 'Assignee 1',
            id: '1'
        },
        {
            name: 'Assignee 2',
            id: '2'
        }
    ]
    return MessageFactory.createListMessage([JobCard({...job, assignees})])
}

The Adaptive card JSON (JobCard)
{
 "contentType": "application/vnd.microsoft.card.adaptive",
 "content": {
   "version": "1.2",
   "body": [
     {
       "weight": "Bolder",
       "size": "Medium",
       "type": "TextBlock",
       "text": "J-2735"
     },
     {
       "isSubtle": true,
       "wrap": true,
       "type": "TextBlock",
       "text": " this is a description "
     },
     {
       "id": "dummySelect",
       "choices": [
         {
           "title": "Option 1",
           "value": "1"
         },
         {
           "title": "Option 2",
           "value": "2"
         }
       ],
       "type": "Input.ChoiceSet",
       "style": "compact",
       "isMultiSelect": false
     }
   ],
   "actions": [
     {
       "title": "Forward",
       "card": {
         "body": [
           {
             "id": "forwardAssignee",
             "choices": [
               {
                 "title": "Assignee 1",
                 "value": "1"
               },
               {
                 "title": "Assignee 2",
                 "value": "2"
               }
             ],
             "type": "Input.ChoiceSet",
             "style": "compact",
             "isMultiSelect": false
           },
           {
             "id": "forwardComment",
             "isMultiline": true,
             "placeholder": "Enter your forward comment",
             "type": "Input.Text"
           }
         ],
         "actions": [
           {
             "title": "Submit",
             "data": {
               "commandId": "forwardJob",
               "instanceId": 3080,
               "locale": 0
             },
             "type": "Action.Submit"
           }
         ]
       },
       "type": "Action.ShowCard"
     }
   ]
 },
 "preview": {
   "contentType": "application/vnd.microsoft.card.thumbnail",
   "content": {
     "title": "J-2735",
     "text": " this is a description ",
     "images": [
       {
         "url": "https://picsum.photos/id/160/500"
       }
     ]
   }
 }
}

Have in mind that if the selects are replaced with radios, the options are displayed correctly:
The Adaptive card with radios
{
  "contentType": "application/vnd.microsoft.card.adaptive",
  "content": {
    "version": "1.2",
    "body": [
      {
        "weight": "Bolder",
        "size": "Medium",
        "type": "TextBlock",
        "text": "J-2735"
      },
      {
        "isSubtle": true,
        "wrap": true,
        "type": "TextBlock",
        "text": " this is a description "
      },
      {
        "id": "dummySelect",
        "choices": [
          {
            "title": "Option 1",
            "value": "1"
          },
          {
            "title": "Option 2",
            "value": "2"
          }
        ],
        "type": "Input.ChoiceSet",
        "style": "expanded",
        "isMultiSelect": false
      }
    ],
    "actions": [
      {
        "title": "Forward",
        "card": {
          "body": [
            {
              "id": "forwardAssignee",
              "choices": [
                {
                  "title": "Assignee 1",
                  "value": "1"
                },
                {
                  "title": "Assignee 2",
                  "value": "2"
                }
              ],
              "type": "Input.ChoiceSet",
              "style": "expanded",
              "isMultiSelect": false
            },
            {
              "id": "forwardComment",
              "isMultiline": true,
              "placeholder": "Enter your forward comment",
              "type": "Input.Text"
            }
          ],
          "actions": [
            {
              "title": "Submit",
              "data": {
                "commandId": "forwardJob",
                "instanceId": 3080,
                "locale": 0
              },
              "type": "Action.Submit"
            }
          ]
        },
        "type": "Action.ShowCard"
      }
    ]
  },
  "preview": {
    "contentType": "application/vnd.microsoft.card.thumbnail",
    "content": {
      "title": "J-2735",
      "text": " this is a description ",
      "images": [
        {
          "url": "https://picsum.photos/id/160/500"
        }
      ]
    }
  }
}

App manifest
.
.
 "composeExtensions": [
    {
      "botId": "15d66618-4f03-4a3a-b18d-558eea92e92d",
      "canUpdateConfiguration": true,
      "commands": [
        {
          "id": "searchJobs",
          "type": "query",
          "title": "Jobs",
          "description": "Your Jobs search query",
          "initialRun": false,
          "fetchTask": false,
          "context": [
            "compose",
            "commandBox",
            "message"
          ],
          "parameters": [
            {
              "name": "query",
              "title": "Search Query",
              "description": "Your search query",
              "inputType": "text"
            }
          ]
        }
      ]
    }
  ]
  .
  .

Followed examples and documentation

https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/javascript_nodejs/50.teams-messaging-extensions-search
https://adaptivecards.io/explorer/

Preconditions
A search based messaging extension with one parameter "query" is created. After the search request is executed a list of items is returned. After an item is selected(tapped) another request is made for retrieving additional data for the item and a detailed card is shown.
Steps to reproduce

Enter a search query.
Select an item -> A card is shown, containing a select "dummySelect", but the select options are missing.
Click the "Forward" action -> Another card is shown, containing a select "forwardAssignee" -> the options are present (this is correct).
Copy the card and paste it in a chat -> The select options of the "dummySelect" in the main card are missing.
Click the "Forward" action-> The select options of the "forwardAssignee" select are missing.

Message extension code
The following function is executed when the user enters the search query->
async function searchJobs(context, action) {
    const {httpConfig} = context
    const query = action.parameters.find(parameter => parameter.name === 'query')
    const jobs = await https.searchJobs({query: query && query.value, httpConfig})
    const attachments = jobs.map(job => {
        const {descriptionId, name, locale} = job
        const card = JobThumbnailCard({name})
        card.content.tap = {
            type: 'invoke',
            value: {
                commandId: messageCommands.getJobByDescriptionId,
                parameters: {
                    descriptionId,
                    locale
                }
            }
        }
        return {...card}
    })
    return MessageFactory.createListMessage(attachments)
}

After an item from the search result is clicked the following function is executed->
async function getJobByDescriptionId(context, action) {
    const {httpConfig} = context
    const {descriptionId, locale} = action.parameters
    const job = await https.getJobByDescriptionId({descriptionId, locale, httpConfig})
     .
     .
     .
    const assignees = [
        {
            name: 'Assignee 1',
            id: '1'
        },
        {
            name: 'Assignee 2',
            id: '2'
        }
    ]
    return MessageFactory.createListMessage([JobCard({...job, assignees})])
}

The Adaptive card JSON (JobCard)
{
 "contentType": "application/vnd.microsoft.card.adaptive",
 "content": {
   "version": "1.2",
   "body": [
     {
       "weight": "Bolder",
       "size": "Medium",
       "type": "TextBlock",
       "text": "J-2735"
     },
     {
       "isSubtle": true,
       "wrap": true,
       "type": "TextBlock",
       "text": " this is a description "
     },
     {
       "id": "dummySelect",
       "choices": [
         {
           "title": "Option 1",
           "value": "1"
         },
         {
           "title": "Option 2",
           "value": "2"
         }
       ],
       "type": "Input.ChoiceSet",
       "style": "compact",
       "isMultiSelect": false
     }
   ],
   "actions": [
     {
       "title": "Forward",
       "card": {
         "body": [
           {
             "id": "forwardAssignee",
             "choices": [
               {
                 "title": "Assignee 1",
                 "value": "1"
               },
               {
                 "title": "Assignee 2",
                 "value": "2"
               }
             ],
             "type": "Input.ChoiceSet",
             "style": "compact",
             "isMultiSelect": false
           },
           {
             "id": "forwardComment",
             "isMultiline": true,
             "placeholder": "Enter your forward comment",
             "type": "Input.Text"
           }
         ],
         "actions": [
           {
             "title": "Submit",
             "data": {
               "commandId": "forwardJob",
               "instanceId": 3080,
               "locale": 0
             },
             "type": "Action.Submit"
           }
         ]
       },
       "type": "Action.ShowCard"
     }
   ]
 },
 "preview": {
   "contentType": "application/vnd.microsoft.card.thumbnail",
   "content": {
     "title": "J-2735",
     "text": " this is a description ",
     "images": [
       {
         "url": "https://picsum.photos/id/160/500"
       }
     ]
   }
 }
}

Have in mind that if the selects are replaced with radios, the options are displayed correctly:
The Adaptive card with radios
{
  "contentType": "application/vnd.microsoft.card.adaptive",
  "content": {
    "version": "1.2",
    "body": [
      {
        "weight": "Bolder",
        "size": "Medium",
        "type": "TextBlock",
        "text": "J-2735"
      },
      {
        "isSubtle": true,
        "wrap": true,
        "type": "TextBlock",
        "text": " this is a description "
      },
      {
        "id": "dummySelect",
        "choices": [
          {
            "title": "Option 1",
            "value": "1"
          },
          {
            "title": "Option 2",
            "value": "2"
          }
        ],
        "type": "Input.ChoiceSet",
        "style": "expanded",
        "isMultiSelect": false
      }
    ],
    "actions": [
      {
        "title": "Forward",
        "card": {
          "body": [
            {
              "id": "forwardAssignee",
              "choices": [
                {
                  "title": "Assignee 1",
                  "value": "1"
                },
                {
                  "title": "Assignee 2",
                  "value": "2"
                }
              ],
              "type": "Input.ChoiceSet",
              "style": "expanded",
              "isMultiSelect": false
            },
            {
              "id": "forwardComment",
              "isMultiline": true,
              "placeholder": "Enter your forward comment",
              "type": "Input.Text"
            }
          ],
          "actions": [
            {
              "title": "Submit",
              "data": {
                "commandId": "forwardJob",
                "instanceId": 3080,
                "locale": 0
              },
              "type": "Action.Submit"
            }
          ]
        },
        "type": "Action.ShowCard"
      }
    ]
  },
  "preview": {
    "contentType": "application/vnd.microsoft.card.thumbnail",
    "content": {
      "title": "J-2735",
      "text": " this is a description ",
      "images": [
        {
          "url": "https://picsum.photos/id/160/500"
        }
      ]
    }
  }
}

App manifest
.
.
 "composeExtensions": [
    {
      "botId": "15d66618-4f03-4a3a-b18d-558eea92e92d",
      "canUpdateConfiguration": true,
      "commands": [
        {
          "id": "searchJobs",
          "type": "query",
          "title": "Jobs",
          "description": "Your Jobs search query",
          "initialRun": false,
          "fetchTask": false,
          "context": [
            "compose",
            "commandBox",
            "message"
          ],
          "parameters": [
            {
              "name": "query",
              "title": "Search Query",
              "description": "Your search query",
              "inputType": "text"
            }
          ]
        }
      ]
    }
  ]
  .
  .

Followed examples and documentation

https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/javascript_nodejs/50.teams-messaging-extensions-search
https://adaptivecards.io/explorer/

Hi @Nikitha-MSFT, do you have any updates on this issue?
Thanks

Hi @Nikitha-MSFT, do you have any updates on this issue?
Thanks

We are able to repro the issue at our end. Raised a bug.

We are able to repro the issue at our end. Raised a bug.

Hi @Nikitha-MSFT, is there a link to the bug that we can share with @rmincheva for tracking?
Thanks

Hi @Nikitha-MSFT, is there a link to the bug that we can share with @rmincheva for tracking?
Thanks

The Teams group is currently working on this Issue, but there is not ETA on a fix. Updates will be provided as they become available.

The Teams group is currently working on this Issue, but there is not ETA on a fix. Updates will be provided as they become available.

I'm migrating this issue over to the Teams folks so that they may follow up directly. Please go here for further tracking https://github.com/MicrosoftDocs/msteams-docs/issues/3556


Switch to src layout, add default data to package

Switching to a src layout is better for enabling proper testing.
The default data for the example reader is now shipped with the package instead of being parsed from the tests/data folder.
This also updates the definitions since I had to re-init the submodule.
Fixes #300

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+19.1%) to 97.611%

Files with Coverage Reduction
New Missed Lines
%

tests/dataconverter/test_writer.py
1
96.67%

Totals

Change from base Build<PHONE_NUMBER>:
19.1%

Covered Lines:
572

Relevant Lines:
586

💛  - Coveralls

I checked locally, too and everything was fine. I tried both editable and "normal" install.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

7 of 7 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+19.1%) to 97.603%

Totals

Change from base Build<PHONE_NUMBER>:
19.1%

Covered Lines:
570

Relevant Lines:
584

💛  - Coveralls


feat: add new toml parser

Motivation
Toml parsers in JS are lossy and don't preserve comments, spaces and relative order or items (see #194).
Approach
Leveraging Rust and WASM, we can create a small library that uses toml_edit crate which has an excellent support for the shortcomings of those JS equivalents.
The new library exports a TomlDocument class that can parse toml and then can be used to access arbitray keys through tomlDocument.field.anotherField or tomlDocument['field']['anotherField'] or tomlDocument.get('field.anotherField') and a value can be set using tomlDocument.field.anotherField = newValue or tomlDocument['field']['anotherField'] = newValue or tomlDocument.set('field.anotherField', newValue)
TODOs and Open Questions

[x] Integrate with the codebase

The status is failing because this PR is opened through a fork, and the token used does not support the appropriate permissions. This would be solved through a bot token, but as it is opt-in, we won't solve for it wholesale at the current time.


MaxPublicInputs limit the public proof input in groth16.move

Steps to Reproduce Issue
I am programming a porker game with zkShuffle. There will be made  public prove input which size is very large.
There is a ETooManyPublicInputs error when I want to verify the proof using the groth16::verify_groth16_proof() method.
I checked the sui source code, I found the MaxPublicInputs is 32, So the max size of Public Proof Input is 32*8=256byte.
I think the most  size of Public Prove Input will over the 256Byte.
What should I do or any suggust. Such as make the Public Proof Input smaller.
Thanks

The max number of inputs is 8, but each input is roughly 32 bytes, so your estimate is corret.
I think it should be possible to modify the circuit to not exceed this. Eg. by putting some of those inputs as private inputs and then perhaps a hash of these as public inputs? It will probably depend on the application.

I static the length of my Public proof input is 6880. Then I expect the MaxPublicInputs is 6880/32 = 215 instead of current value 8.

I have a idear, I can create layer2 network  base on sui with zk. Then I can change the MaxPublicInputs  freely.

The max number of inputs is 8, but each input is roughly 32 bytes, so your estimate is corret.
I think it should be possible to modify the circuit to not exceed this. Eg. by putting some of those inputs as private inputs and then perhaps a hash of these as public inputs? It will probably depend on the application.

Thanks. I had passed the verify function by set serial Public Proof Input to Private Input.
But I am wandoring what the effaction about this operation.


Call to a member function getPageTemplateID() on a non-object

recently started the problem: Call to a member function get Page Template ID () on a non-object do not know why it :/
concrete/src/Page/Type/Type.php
line 290

Because closed? to report something wrong or there is already an incident is good to notice right?

We can't effectively act on this report. There's no context to anything as to how it got this way, where it shows up, etc.
For bug reports like this that have not been verified as bugs and don't have a lot of information its best to post them to the concrete5.org bug tracker.
Sent from my iPhone

On Apr 14, 2015, at 6:31 AM, Kallef<EMAIL_ADDRESS>wrote:
Because closed? to report something wrong or there is already an incident is good to notice right?
—
Reply to this email directly or view it on GitHub.

All right, but it's good always tell, thank you (:


Tracking PR for moving generators from FFTField to Field

Description
We plan to move generators from FFTField to Field, which is for #276 and #472.
The current progress of this PR is that we have finished moving, but we need to supply the generators. I am currently factoring q^k-1 both by hand-waving and Sage, first for those curves in test-curves.
closes: #276

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (master)
[x] Linked to GitHub issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[ ] Wrote unit tests
[ ] Updated relevant documentation in the code
[ ] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[ ] Re-reviewed Files changed in the GitHub PR explorer

After discussion, we decided to give up---it takes a long time to factor q^2 + q + 1 for BLS12-381.

Since this is closed, are there any alternatives to exposing the generators so that even the Field trait has access to it? The only way I can think of is to combine both the Field and FFTField trait to create an overarching trait in order to get access to multiplicative generator

I think a more comprehensive solution is to make it optional to specify a generator for a field.


Feature request: Ability to open a new window with all results in search scope.

I'd love to be able to search for "https://github.com" and then with a simple small button "Move all results to new window".
Thank you for consideration.

@cocoonkid Do you mean, opening all shown results as new tabs in a new window?

yes exactly and closing them out in the current open windows.


max-height/offsetHeight Calculation Issue, Fixes #2581

Fixes #2581
If the number of items in the dropdown > this.options.size, then the following line runs:
menuHeight = liHeight * this.options.size + divLength * divHeight + menuPadding.vert;
However, liHeight is calculated wrong if the first item is hidden or if first item has text of ''.
Before adding the temporary newElement to the body to calculate height, I always show the first item (I didn't check to see if hidden), and if first items text = '', I set it to   (probably wouldn't need a check here either).

Hello Terry, thank you for your contribution, I made a quick review, please address my comments.

Done
Yes, it was only to convey it was jquery object and I was copying your style from other place.
Basically a disposable variable, but chose newElementAnchor.
Bad code ;) Fixed.
Yes, missed that b/c I had a bit different code to start where I checked if hidden, then showed.  Didn't clean up.  Sorry.

Need a little help here.  I've never had a 'review' before and pushed another commit.  Github (above) says:

Add more commits by pushing to the bug/max-height branch on terryaney/bootstrap-select.

Which I did, but I'm not sure if they are automatically pulled into the pull request or not.

Added === check and added some addition code to preserve/restore css. Let me know if anything else is needed.

@terryaney thanks, please make the linter happy (you can run it locally, too!)

@terryaney thanks, please make the linter happy (you can run it locally, too!)

I've updated.  If linter still failing, could you tell me how I run locally?  FYI, I'm editing the file in VS Code, but I'm not opening the folder or anything (just the single file).  I'll google in the meantime.

You can run it locally with npm run lint.

Doesn’t seem to be working.
Sent from Mail for Windows
From: Nicolas CARPi
Sent: Friday, January 14, 2022 3:25 PM
To: snapappointments/bootstrap-select
Cc: Terry Aney; Mention
Subject: Re: [snapappointments/bootstrap-select] max-height/offsetHeight Calculation Issue, Fixes #2581 (#2653)
You can run it locally with npm run lint.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.Message ID: @.***>

Doesn’t seem to be working.

No it's working but you need to get a proper dev env with npm i.

I guess I'm still confused because I expect there to be a "lint" script/action present inside package.json but it isn't there and I obviously don't want to edit that file.  Disclaimer, I do 99% of my dev in Visual Studio on server side code so my npm/VS Code skills are still very green.
I ran npm i in the terminal and it said it added 451 packages (recalling from memory, so could be different) and then I tried npm run lint and recieved this:
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'lint'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose stack Error: missing script: lint
4 verbose stack     at run (C:\Program Files\nodejs\node_modules\npm\lib\run-script.js:155:19)
4 verbose stack     at C:\Program Files\nodejs\node_modules\npm\lib\run-script.js:63:5
4 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:116:5
4 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:436:5
4 verbose stack     at checkBinReferences_ (C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:391:45)
4 verbose stack     at final (C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:434:3)
4 verbose stack     at then (C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:161:5)
4 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:382:12
4 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:123:16
4 verbose stack     at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
5 verbose cwd C:\BTR\OpenSource\bootstrap-select
6 verbose Windows_NT 10.0.19043
7 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "lint"
8 verbose node v12.19.0
9 verbose npm  v6.14.8
10 error missing script: lint
11 verbose exit [ 1, true ]

@terryaney Sorry it's my bad, I mixed up projects in my head. This project uses grunt, so the command is grunt lint or ./node_modules/.bin/grunt lint if your $PATH is not properly set to use node's bins.

OK, so to run it, it was simply ./node_modules/.bin/grunt (without the lint).  When I ran it with lint, I got this warning Warning: Task "lint" not found. Use --force to continue..  But it seemed to work without the lint part and all my issues are resolved.
Secondly, after running that (or maybe the npm i command), I have 87 'dist' files that changed (I checked one and it seemed it was the copyright date) along with the package-lock.json file (that just updated version from 1.13.18 -> 1.14.0-beta2).  I didn't check those in and just undid all those for now.  Let me if anything else.  Thanks for the guidance.

See https://github.com/snapappointments/bootstrap-select/pull/2681 for the dist issue (no longer an issue).
You don't have the lint grunt command because you're not using the latest code. Make sure to use the dev branch for basing your PR.

Going to start over after pulling latest code.