Text selection bugs in Firefox

See this example where I drag a selection 3 times from left (outside the element) and 1 time from right (inside the element) in Firefox 114:

Two specific issues:

Text selection breaks when selection expands across the element boundary
Selection color of CSS ::selection does not take effect, instead the default (in my case red) color is shown when selecting inside the element.

This looks to be a bug with Firefox and ShadowDOM. I have a minimal reproduction here: https://codepen.io/keithamus/pen/abRewMJ. Testing in Chrome and Safari these issue is not reproducible. Firefox Nightly seems to still have this issue.
Specifically I'd look at https://bugzilla.mozilla.org/show_bug.cgi?id=1233594 or perhaps it's worth filing a new issue with Mozilla?
I'm going to close this because it's not something we can easily fix within this component, as it's a broken behaviour with one browser in particular. Let me know if you do file any bugs with Mozilla as I'd be interested to see the progress there.

Okay, yes the first issue seems like a browser bug. The second issue with ::selection color affects Blink as well:

It's fine in Safari:

What do you think about that one? I guess those two Shadow DOM implementations may differ, but I'm not sure which one is supposed to be correct because I do recall Shadow roots represent a boundary that CSS normally can not cross.

For the first issue, I found this meta bug, so it looks like Mozilla is well aware.

As for the color issue: I conclude it as a Safari bug and Blink and Gecko are likely correct in that they don't let ::selection style cross the shadow boundary.
Overall, I think ::selection should be an exception that can cross shadow boundaries, as otherwise elements like this one would have to expose an API to let users define CSS, like a style which could then be appended to the shadow root on creation, e.g.
<relative-time style="::selection {background: hotpink}">

I’m inclined to agree that selection should cross shadow roots. I don’t think there’s any mechanism we’d want to introduce in this component, though.  It won’t be exclusive to this component and providing a solution to each and every web component seems heavy handed IMO.
I’m surprised this hasn’t come up before. Have you found any issues in Chrome/Safari trackers around these?


Add end-to-end example

Would be awesome if the docs had an example for a complete App with a Java backend (say),
to showcase Bazel's ability to build everything a developer needs.

Can you be more specific?  "I want to see an app that that has... at least x java_* rules... can serve a webpage... is a mobile app... has external dependencies... whatever?"  An example program that you think is about right?  (e.g., a todo list? libgdx?)

I probably posted this prematurely, but basically, I'd like to answer a question that's going to come up often: "why should I try Bazel? what does it give me that I don't get from Gradle or xcodebuild?"
A single build-system which builds my iOS app, my backend (written in Java) and my Android app sounds like an awesome advantage, and I wish we could showcase it :)

Done in github.com/bazelbuild/example in the tutorial folder. Also the tutorial is now on bazel.io.


vSphere: missing some data sources and resources

Error:

vm_template = d.vsphere_virtual_machine('vm_template',
AttributeError: module 'terrascript.vsphere.d' has no attribute 'vsphere_virtual_machine'

python-terrascript/terrascript/vsphere/d.py is missing the declaration for a vsphere_virtual_machine data source.
This data source is required by Terraform for cloning from an existing template. Which means for Terraform, the vsphere_virtual_machine is required as both a resource and data source.
Fix:
Adding the following fixes this issue:
# ~/vsphere/d.py
class vsphere_virtual_machine(_data): pass
virtual_machine = vsphere_virtual_machine

Additional missing data sources:
vsphere_custom_attribute
vsphere_datastore_cluster
Additional  missing resources
vsphere_custom_attribute
vsphere_datastore_cluster
vsphere_storage_drs_vm_override

See tests/test_issue35.py.


Adapt to storage-partitioned join additions in SPARK-37377

Fixes the build failures in Spark 3.3 caused by SPARK-37377.  DataSourceRDD now expects a sequence-of-sequence-of-partitions and BatchScanExec similarly has changes that require both to be shimmed.  In the process of shimming these, I went ahead and pulled in the changes from SPARK-35779 so we're better prepared to support runtime-filtering on scans, given we needed to shim GpuBatchScanExec anyway.

build

build


chore: update readme

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2202

Relevant Lines:
2202

💛  - Coveralls


Double quote delimiter in Import-Csv

Why double quote delimiter has a special behavior (skipping columns) in Import-Csv?
Is this expected/documented/RFC-defined behavior?
# Input 1.csv
# a1""a3
# v1"v2"v3

Import-csv .\1.csv -Delimiter '"'

# Output
a1 a3
-- --
v1 v3

# Input 2.csv
# a1,,a3
# v1,v2,v3

Import-csv .\2.csv -Delimiter ','

# Output
WARNING: One or more headers were not specified. Default names starting with "H" have been used in place of any missing headers.

a1 H1 a3
-- -- --
v1 v2 v3

@SteveL-MSFT Have you any information about the special behavior? Is this side affect (bug) in the code or a standard?

That's probably somewhere between a "why would you use that as delimiter" and "special case that needs dealing with". CSV entries with spaces need to be enclosed with (usually) double quotes. I don't know if there's another possible enclosing character that can be relied upon, really (single quotes maybe?)
The trouble with CSV is there isn't a concrete "standard" just a bunch of very similar implementations with some differences scattered throughout.
But I've never seen a CSV with double quotes as delimiter before... I'd be of the inclination that it be treated as a reserved character and not be permitted as a delimiter for parsing at all, but...

But I've never seen a CSV with double quotes as delimiter before...

The Issue is that we accept the delimiter and skip one column. So I'd expect that we either do not accept the delimiter or do not skip the column.

The former sounds perfectly fine to me, but I'm unsure if there's a valid reason to use a double quote as a delimiter.

Took a look at the code, as noted above, double quotes is a special character for containing whitespace so that this:

"foo,bar","apple"

becomes:

foo,bar  apple

and not:

foo  bar  apple

So using " as the delimiter breaks this.  I think that unless there's a real scenario to use the double quote as a delimiter, it's not worth making a change.  Otherwise, we'd special case if double quote is used, you cannot have whitespace as part of a value.

@SteveL-MSFT My question is should we address  scenario from my repo steps where we lost column?

@iSazonov there's probably a bug in the logic when double quotes are used as the delimiter as there's special code already to handle double quotes to preserve whitespace.  I think the question is whether it's worthwhile to spend time investigating and fixing something that is a corner case.

I think the question is whether it's worthwhile to spend time investigating and fixing something that is a corner case.

Yes, I think we can label this with Up-For-Grabs and Hackathon.


Make all pieces of loading/linting optional

In the fashion of the linters I am familiar with, we should only check what is provided/requested, and not require a full check of all things every time. What I mean is, this should technically be considered a working config file:
[org]
login = "godaddy"

It wouldn't actually check anything, except that the org exists and the token used has access to it. But it would technically work.
Also important is that the above config SHOULD NOT load any additional info. It should not load membership data, team data, application data, org settings, etc. Just the login. Nor should it call any of the checkers.
Likewise, this should be a valid config:
[org]
login = "godaddy"

[[applications]]
appId = 2740
appSlug = "renovate"
repositorySelection = "selected"
events = [
  "check_run",
  "issues",
  "issue_comment",
  "pull_request",
  "push",
  "repository",
  "status"
]

[applications.permissions]
checks = "write"
issues = "write"
members = "read"
contents = "write"
metadata = "read"
statuses = "write"
workflows = "write"
pull_requests = "write"
administration = "read"
vulnerability_alerts = "read"

The above config would load ONLY the org login name, and application installations. It would then verify that ONLY the "renovate" application is installed, and that its installation matches the config.
So in other words, if a config section exists, it triggers the appropriate loaders/checkers/fixers. If that section does not exist, those are not loaded.

should it work that way or should it have a default rule set that you can use your config file to opt-in/-out of additional rules.  e.g. maybe it runs what you currently have by default and then you can do something like
[settings]
rules = ['some', 'list', 'of', 'rules']

I feel like trying to be smart about what is in the settings file makes it easy to accidentally think its fixing more than what its actually doing (e.g. "oops I misspelled applications" so it did nothing).

Interesting thought. So maybe there could be an [orglinter] specific section, something like:
[orglinter]
# Explicit set of _included_ checkers
enable = ["org", "applications"]

# OR explicit list of _excluded_ checkers
disable = ["members", "teams"]

That would also allow for more tool-specific configuration later on down the line. And we can be very explicit about allowed keys and values in this section.

Exactly, it allows the tool to be opinionated about what you should check without forcing that.  I also think you might want to allow for CLI overrides of those as well (so a hierarchy of CLI >> my.toml >> defaults). that way you can do one-off checks without having to modify a source-control'd config file (e.g. I just want to check for demotions real quick)

Definitely agreed on the priority order. We might even toss env vars in there just for completeness. CLI > env > my.toml > defaults
But that all depends on actually setting up a proper CLI app first. I think I've mentioned that in a couple issues now. That should probably be encapsulated in its own issue... because it seems that it's becoming a blocker for a number of things now.


fix get User model in 0010 migration

@igorkud90 Could you elaborate this?

@yakky I have a custom User model. When i apply migrations on empty database, i have a error: ProgrammingError: column User.same_field does not exist. This field added in my 0004 migration in my app, but django-cms migrations perfomed before this 0004 migration. We can't import the User model directly as it may be a newer version than this migration expects. We can use the historical version.

@igorkud90 I'll merge this into support branch with a further fix for south migration.
Thanks for spotting it

Linked PR merged


Deprecate and remove cloud-controller-manager binary

backlog tracking issue for https://github.com/kubernetes/kubernetes/issues/81027

/remove-lifecycle stale

/lifecycle frozen

/close


Summarize Chain Doesn't Always Return Summary When Using Refine Chain Type

When using the refine chain_type of the load_summarize_chain, I get some unique output on some longer documents, which might necessitate minor changes to the current prompt.
Return original summary.

The original summary remains appropriate.

No changes needed to the original summary.

The existing summary remains sufficient in capturing the key points discussed

No refinement needed, as the new context does not provide any additional information on the content of the discussion or its key takeaways.

I've found the same problem with the map_reduce chain as well.

I have same problem with the refine chain
The existing summary is already comprehensive and does not require any refinement based on the additional context provided

Same here. Related to #1460
I use refine to summarize long articles and I see that the summary is actually quite good in the intermediate steps but at some point the model decides to throw away half the summary so lots is missing in the final answer.
Not sure how to adress this.

Hey guys, @CMobley7 @jinhucheung @TheDeterminator @SingTeng @thiswillbeyourgithub
Any new related to that? Did you managed to find a way out of it?
Thanks

Anyone fixed this issue?

I can see due to verbosity that the map_reduce chain writes effectively the summary, but it returns either an empty string object, or the last paragraph at best.
Tried this on a local llm with llamacpp. Again, I can see it attempts generating the summary and all, but I'm left with nothing.

Yes same here. So the issue is from the reduce prompt and not the map prompt right? I struggle to find the reduce prompt in the codebase, can you ?

I ended up apparently fixing my problem.
I basically changed a few lines to go closer to this : https://python.langchain.com/docs/use_cases/question_answering/how_to/chat_vector_db
Here's my patch:
 from langchain.chains import ConversationalRetrievalChain
+from langchain.chains import LLMChain
 from langchain.chains.qa_with_sources import load_qa_with_sources_chain
 from langchain.retrievers.merger_retriever import MergerRetriever
 from langchain.document_transformers import EmbeddingsRedundantFilter
 from langchain.retrievers.document_compressors import DocumentCompressorPipeline
 from langchain.retrievers import ContextualCompressionRetriever
+from langchain.prompts.prompt import PromptTemplate

 from utils.llm import load_llm, AnswerConversationBufferMemory
 from utils.file_loader import load_doc, load_embeddings, create_hyde_retriever, get_tkn_length, average_word_length, wpm
@@ -552,10 +554,22 @@ class DocToolsLLM:
                             base_compressor=pipeline, base_retriever=retriever
                         )

-                    chain = ConversationalRetrievalChain.from_llm(
-                            llm=self.llm,
-                            chain_type="map_reduce",
+                    _template = """Given the following conversation and a follow up question, rephrase the follow up question to be a standalone question, in its original language.
+
+                    Chat History:
+                    {chat_history}
+
+                    Follow Up Input: {question}
+
+                    Standalone question:"""
+                    CONDENSE_QUESTION_PROMPT = PromptTemplate.from_template(_template)
+                    question_generator = LLMChain(llm=self.llm, prompt=CONDENSE_QUESTION_PROMPT)
+                    doc_chain = load_qa_with_sources_chain(self.llm, chain_type="map_reduce")
+
+                    chain = ConversationalRetrievalChain(
                             retriever=retriever,
+                            question_generator=question_generator,
+                            combine_docs_chain=doc_chain,
                             return_source_documents=True,
                             return_generated_question=True,
                             verbose=self.llm_verbosity,
(END)

The repo is this one : https://github.com/thiswillbeyourgithub/DocToolsLLM


[Installation]: Build vllm environment error

Your current environment
WARNING 11-14 02:19:07 _custom_ops.py:20] Failed to import from vllm._C with ModuleNotFoundError("No module named 'vllm._C'")
Collecting environment information...

Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

did you try and set MAX_JOBS=6? also I would suggest try running pip in verbose mode with -vvv to see more fine outputs


solid spa error when navigate is called

### Description
i cloned th solid-spa example, y added a simple new page and from the index page example i imported the navigate function
and simple try to navigate to the other page
pages/index/index.page.client.jsx
import { navigate } from "vite-plugin-ssr/client/router";
import { Counter } from './Counter'

export function Page() {
  navigate('/one');
  return (
    <>

About

Solid JS SPA

      <Counter></Counter>
      <button onClick={() => navigate('/one')}>One</button>
    </>
  )
}

pages/one/index.page.client.jsx
export function Page() {
    return (
        <>

Page One

        </>
    );
}

in both calls the same error
Error Stack
Uncaught (in promise) Error<EMAIL_ADDRESS>You stumbled upon a bug in vite-plugin-ssr's source code. Reach out at https://github.com/brillout/vite-plugin-ssr/issues/new or https://discord.com/invite/qTq92FQzKb and include this error stack (the error stack is usually enough to fix the problem). A maintainer will fix the bug (usually under 24 hours). Do not hesitate to reach out as it makes vite-plugin-ssr more robust.
    at navigate (useClientRouter.js?v=642eb382:170:5)
    at Page (index.page.client.tsx:6:3)
    at @solid-refresh:10:42
    at untrack (dev.js:425:12)
    at Object.fn (@solid-refresh:10:28)
    at runComputation (dev.js:694:22)
    at updateComputation (dev.js:679:3)
    at createMemo (dev.js:238:10)
    at hmrCompWrapper (@solid-refresh:7:20)
    at dev.js:519:12
    at untrack (dev.js:425:12)
    at Object.fn (dev.js:515:37)
    at runComputation (dev.js:694:22)
    at updateComputation (dev.js:679:3)
    at devComponent (dev.js:525:3)
    at createComponent (dev.js:1227:10)
    at _default.page.client.tsx:23:37
    at dev.js:99:53
    at updateFn (dev.js:168:15)
    at runUpdates (dev.js:786:17)
    at createRoot (dev.js:176:12)
    at render (dev.js:97:3)
    at Object.render (_default.page.client.tsx:23:25)
    at hydrate (entry.js:12:31)

createErrorWithCleanStackTrace | @ | createErrorWithClean…ace.js?v=642eb382:7
-- | -- | --
  | assert | @ | assert.js?v=642eb382:25
  | navigate | @ | useClientRouter.js?v=642eb382:170
  | Page | @ | index.page.client.tsx:6
  | (anonymous) | @ | @solid-refresh:10
  | untrack | @ | dev.js:425
  | (anonymous) | @ | @solid-refresh:10
  | runComputation | @ | dev.js:694
  | updateComputation | @ | dev.js:679
  | createMemo | @ | dev.js:238
  | hmrCompWrapper | @ | @solid-refresh:7
  | (anonymous) | @ | dev.js:519
  | untrack | @ | dev.js:425
  | (anonymous) | @ | dev.js:515
  | runComputation | @ | dev.js:694
  | updateComputation | @ | dev.js:679
  | devComponent | @ | dev.js:525
  | createComponent | @ | dev.js:1227
  | (anonymous) | @ | _default.page.client.tsx:23
  | (anonymous) | @ | dev.js:99
  | updateFn | @ | dev.js:168
  | runUpdates | @ | dev.js:786
  | createRoot | @ | dev.js:176
  | render | @ | dev.js:97
  | render | @ | _default.page.client.tsx:23
  | hydrate | @ | entry.js:12
  | await in hydrate (async) |   |
  | (anonymous) | @ | entry.js:7

navigate() is only meant to be used with Client Routing, see https://vite-plugin-ssr.com/navigate.
Let me fix that error message though.

thanks, i added 'export const clientRouting = true' to 'renderer/_default.page.client.tsx' and is working as expected now


Some confusion about analysis and experiment in the paper

As I was reading the paper I had some confusion: your paper mentions that FastSAM needs at least two prompt points and on that basis compares the performance of FastSAM and MobileSAM in segment anything mode.
But as you can see from the HuggingFace demo posted by FastSAM, their approach supports a single point and has worked well in my own attempts. If it is indeed a writing error, I very much look forward to your revision and showing new experiments to effectively compare the two methods.
BTW, I am also curious how Table 7 in the paper is done exactly, and why the model performance can be proved by modifying the distance of positive and negative prompt points?

As I was reading the paper I had some confusion: your paper mentions that FastSAM needs at least two prompt points and on that basis compares the performance of FastSAM and MobileSAM in segment anything mode.
But as you can see from the HuggingFace demo posted by FastSAM, their approach supports a single point and has worked well in my own attempts. If it is indeed a writing error, I very much look forward to your revision and showing new experiments to effectively compare the two methods.
BTW, I am also curious how Table 7 in the paper is done exactly, and why the model performance can be proved by modifying the distance of positive and negative prompt points?

Thanks for your interest in our work. When we compared with their method and found that it cannot work with a single point. We will carefully read their code again to see how it works.
For the results in Table7, we do not use the distance for proving that ours is better. Distance is more or less like a hyperparameter here and we show that FastSAM has a significantly lower with all distances. More extensive comparison is on the way.

As I was reading the paper I had some confusion: your paper mentions that FastSAM needs at least two prompt points and on that basis compares the performance of FastSAM and MobileSAM in segment anything mode.
But as you can see from the HuggingFace demo posted by FastSAM, their approach supports a single point and has worked well in my own attempts. If it is indeed a writing error, I very much look forward to your revision and showing new experiments to effectively compare the two methods.
BTW, I am also curious how Table 7 in the paper is done exactly, and why the model performance can be proved by modifying the distance of positive and negative prompt points?

As stated in the paper, the mIoU was calculated with the comparsion with the mask generated by the original SAM. We set the point in the middle of the image. I suggested you to experiment with the mask with the original SAM. The mask you provided seems to be very good actually. I mean, if you try with the original SAM, you are very likely to get the same mask as the you reported. Detect small objects (window in this case) seems to be more preferable.

Thank you for your reply and discussion. I have three new questions I would like to discuss with you @ChaoningZhang :

Is it important to output like with SAM or to output real and valid objects? -- As my pictures above show, FastSAM outputs a complete bus, while MobileSAM outputs a bus window with a lot of noise (>30%), and perhaps MobileSAM is more similar to SAM in mIoU. However, I don't think "windows with a lot of noise" is more useful than "a complete bus".

Is the mIoU comparison method fair? --MobileSAM uses knowledge distillation to learn the output of the original SAM, while FastSAM is trained separately. It is well known that knowledge distillation helps make student more similar to teacher. It feels very unfair to take the original SAM as Ground Truth and compare the output of FastSAM and MobileSAM to see which is more similar to the original SAM. This seems similar to "testing on training data".

Is FastSAM really not suitable for small objects? -- I tried looking at the segmentation results of FastSAM and found that it can segment car windows well (it's just that when faced with the segmentation ambiguity problem, FastSAM tends to prioritize large objects, while SAM/MobileSAM tends to prioritize small objects. This is not superior or inferior). Using the quantitative data in the FastSAM paper as evidence, FastSAM performs due to SAM (ViT-H) on small objects and slightly inferior to SAM on large objects. I'd like to know why you think FastSAM is not suitable for detecting small objects.

Looking forward to discuss with you.

Thank you for your reply and discussion. I have three new questions I would like to discuss with you @ChaoningZhang :

Is it important to output like with SAM or to output real and valid objects? -- As my pictures above show, FastSAM outputs a complete bus, while MobileSAM outputs a bus window with a lot of noise (>30%), and perhaps MobileSAM is more similar to SAM in mIoU. However, I don't think "windows with a lot of noise" is more useful than "a complete bus".
Is the mIoU comparison method fair? --MobileSAM uses knowledge distillation to learn the output of the original SAM, while FastSAM is trained separately. It is well known that knowledge distillation helps make student more similar to teacher. It feels very unfair to take the original SAM as Ground Truth and compare the output of FastSAM and MobileSAM to see which is more similar to the original SAM. This seems similar to "testing on training data".
Is FastSAM really not suitable for small objects? -- I tried looking at the segmentation results of FastSAM and found that it can segment car windows well (it's just that when faced with the segmentation ambiguity problem, FastSAM tends to prioritize large objects, while SAM/MobileSAM tends to prioritize small objects. This is not superior or inferior). Using the quantitative data in the FastSAM paper as evidence, FastSAM performs due to SAM (ViT-H) on small objects and slightly inferior to SAM on large objects. I'd like to know why you think FastSAM is not suitable for detecting small objects.

Looking forward to discuss with you.

We are currently very busy with other ongoing works and try to answer your question in a brief manner. An important characteristic of the SAM is that it can address the ambiguity issue. With a single point, SAM can output three masks to address these issues, for which our MobileSAM follows. If a large object is more meaningful than the smaller one as you suggested, SAM can just choose the three masks that have the largest region. Obviously, this does not make sense and that's why SAM relies on a score ranking mechanism to choose the final mask. In other words, it is the model that automatically prefers the smaller object (without human bias). It seems that FastSAM ignores this ambiguity issue. It seems to me that ignoring this ambiguity issue and claiming a larger object like bus might be biased. After all, for human A, a point can mean the bus, while for human B, the same point can mean the window in this context. Do you agree?

Thank you for your reply and discussion. I have three new questions I would like to discuss with you @ChaoningZhang :

Is it important to output like with SAM or to output real and valid objects? -- As my pictures above show, FastSAM outputs a complete bus, while MobileSAM outputs a bus window with a lot of noise (>30%), and perhaps MobileSAM is more similar to SAM in mIoU. However, I don't think "windows with a lot of noise" is more useful than "a complete bus".
Is the mIoU comparison method fair? --MobileSAM uses knowledge distillation to learn the output of the original SAM, while FastSAM is trained separately. It is well known that knowledge distillation helps make student more similar to teacher. It feels very unfair to take the original SAM as Ground Truth and compare the output of FastSAM and MobileSAM to see which is more similar to the original SAM. This seems similar to "testing on training data".
Is FastSAM really not suitable for small objects? -- I tried looking at the segmentation results of FastSAM and found that it can segment car windows well (it's just that when faced with the segmentation ambiguity problem, FastSAM tends to prioritize large objects, while SAM/MobileSAM tends to prioritize small objects. This is not superior or inferior). Using the quantitative data in the FastSAM paper as evidence, FastSAM performs due to SAM (ViT-H) on small objects and slightly inferior to SAM on large objects. I'd like to know why you think FastSAM is not suitable for detecting small objects.

Looking forward to discuss with you.

We are currently very busy with other ongoing works and try to answer your question in a brief manner. An important characteristic of the SAM is that it can address the ambiguity issue. With a single point, SAM can output three masks to address these issues, for which our MobileSAM follows. If a large object is more meaningful than the smaller one as you suggested, SAM can just choose the three masks that have the largest region. Obviously, this does not make sense and that's why SAM relies on a score ranking mechanism to choose the final mask. In other words, it is the model that automatically prefers the smaller object (without human bias). It seems that FastSAM ignores this ambiguity issue. It seems to me that ignoring this ambiguity issue and claiming a larger object like bus might be biased. After all, for human A, a point can mean the bus, while for human B, the same point can mean the window in this context. Do you agree?

I close it for the moment since there are no follow-up issues. Thanks for your interest in our work again~~

I'm so sorry
El sáb., 1 de julio de 2023 10:21 a. m., Chaoning Zhang <
@.***> escribió:

Closed #13 https://github.com/ChaoningZhang/MobileSAM/issues/13 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/ChaoningZhang/MobileSAM/issues/13#event-9696689376,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAZ5WPK3APKDNO7CKEMWUT3XOA6AVANCNFSM6AAAAAAZWUIUDU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


ARROW-8369: [CI] Fix crossbow R group

@github-actions crossbow submit -g r

@github-actions crossbow submit -g r

@github-actions crossbow submit -g nightly

@kszucs @wesm A few things I've noticed:

Apparently you can't start a glob with *. Maybe that's a yaml thing? Maybe not. Didn't try to debug.
If you have a group that has a glob pattern and then something else, only the first glob is used. In the R task list above, there are two entries in the group definition, and the second one (macos-r-autobrew) was not included.
The nightly group fails (see here), my guess is that the greedy pattern matching is pulling in jobs that we weren't including previously and that don't actually work.
Y'all should do an audit of what's included and what isn't. I fixed a handful of discrepancies between what was run before and what is being run now (assuming of course that they run), but there may be more. And as (3) suggests, there may be stale, broken tasks in the yaml that should be cleaned out.

Maybe this is a good opportunity to bootstrap a small unit test suite

@kszucs @wesm A few things I've noticed:

Apparently you can't start a glob with *. Maybe that's a yaml thing? Maybe not. Didn't try to debug.
Yes, that is reserved for YAML anchors. If use enclose it with quotes then yaml will treat it as string so it will work.
If you have a group that has a glob pattern and then something else, only the first glob is used. In the R task list above, there are two entries in the group definition, and the second one (macos-r-autobrew) was not included.
That's because I renamed macos-r-autobrew  to homebrew-r-autobrew ala the existsing homebrew-cpp-autobrew - so macos-r-autobrew doesn't exists anymore.
The nightly group fails (see here), my guess is that the greedy pattern matching is pulling in jobs that we weren't including previously and that don't actually work.
I'm investigating this.
Y'all should do an audit of what's included and what isn't. I fixed a handful of discrepancies between what was run before and what is being run now (assuming of course that they run), but there may be more. And as (3) suggests, there may be stale, broken tasks in the yaml that should be cleaned out.
I'm trying to add a subcommand to validate the configuration.

Re: validation, I agree with @wesm that this sounds like something that belongs in a test suite. Make sure that all groups refer to tasks that exist, and make sure that all tasks render their templates without error.

I've added logic to test the configuration in #6875 I'll implement proper unittests for crossbow once I port it to archery.

@github-actions crossbow submit --dry-run -g r


[BEAM-13938][Playground] Increase test coverage for the graphs

[BEAM-13938][Playground] add more unit-tests for graphs

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

aw I'm sorry, this needs to be rebased : (

@pabloem done


Add needed 'redundant' checks.

Description
clang-tidy has some duplicated checks with different names. In order to suppress these checks, we have to suppress for both names.
Checklist:

[x] I have reviewed my diff in github, line by line.
[x] Every change is related to the PR description.
[ ] I have linked this pull request to the issue(s) that it resolves.
[x] There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
[x] There are no circuit changes, OR specifications in /markdown/specs have been updated.
[x] There are no circuit changes, OR a cryptographer has been assigned for review.
[ ] I've updated any terraform that needs updating (e.g. environment variables) for deployment.
[x] The branch has been rebased against the head of its merge target.
[x] I'm happy for the PR to be merged at the reviewer's next convenience.
[x] New functions, classes, etc. have been documented according to the doxygen comment format. Classes and structs must have @brief describing the intended functionality.
[x] If existing code has been modified, such documentation has been added or updated.

This is a tiny an uncontroversial PR that does not need review.


Catalog endpoint implementation

Catalog should also manage Controls (Controls do not exist outside of catalogs in the OSCAL schema).
So we need to add the supporting endpoints for Control management.
Create control:
POST /api/catalog/{catalogId}/controls
Update control:
POST /api/catalog/{catalogId}/control/{controlId}


Create NodeJS program that manages users and provides authentication.

https://medium.com/of-all-things-tech-progress/starting-with-authentication-a-tutorial-with-node-js-and-mongodb-25d524ca0359
Stores:

User Email
User Password (hashed)
UserId

Functionality:

Put
-- In: email, password
-- Out: UserId/token
Get
-- In: email, password
-- Out: UserId/token

Will implement in another issue at another time, as updated requirements are created.


Use boolean values for debug-mode(etc) not string

debug-mode {{ "on" if cookiecutter.debug_mode == "True" else "off" }}
Setting it to debug_mode: true in your yaml does not work, you have to use debug_mode: "True". I am guessing this is because cookiecutter did not support boolean values when this template was created. Changing this to require a boolean may have unexpected implications for legacy templates - an alternative would be to change the default value in cookiecutter.json to "True" to hint that it's looking for a string.

Yes, this needs improvement.

this will be fixed with v2.0, https://github.com/plone/cookiecutter-zope-instance/commit/fcfdc79e72f74028b71f8735f18ac078f6021e38


Add description for AvgSpeed extra_info

@TheGreatRefrigerator this isn't supported anymore, right?

You are right


Fix CI path for translations deploy

We checkout the repo with the qiskit prefix, so need to run qiskit/tools, not tools/.

@Mergifyio backport

@Mergifyio backport stable/0.25


Escape double quotes in query parameters recording

When recording double quotes in the query parameters are not escaped :
    .pause(2, 3)
                        .exec(
                        http("request_11")
                        .post("/search/")
                        .param("q", "[{"Id":null,"Action":"GO","description":null,"flag":false,"status":"ACTIVE","profile":null}]")
                        .param("token", "2")
                        .headers(headers_11)

Woops! I thought about fixing this, but it seems I never did it :-)
Will do as soon as I finish the big refactoring I'm in the middle of :)

not stuck I ve edited the scenario with " => "
works well
thx
Niko
2012/3/1 Stephane Landelle <
<EMAIL_ADDRESS>

@nicolashelleringer Just in case you're stuck: you can fix your scenario
very easily, use """ for protecting your string :
.pause(2, 3)
.exec(
http("request_11")
.post("/search/")
.param("q",
"[{"Id":null,"""Action":"GO","description":null,"flag":false,"status":"ACTIVE","profile":null}]""")
.param("token", "2")
.headers(headers_11)

Reply to this email directly or view it on GitHub:
https://github.com/excilys/gatling/issues/427#issuecomment-4254767


[FX-450] Increase polling timeout to 90sec

What

Why

Test Plan

✅ | ❌ Not a front-end change
✅ | ❌ iOS QA Tests passed locally
✅ | ❌ Unit Tests passed locally

How

Current dependencies on/for this PR:

main

PR #102   👈

This comment was auto-generated by Graphite.


[Missing SNMP Traps Profile] Cisco 3900 router

Device Vendor: Cisco
Device Model: 3900 Routers
Please attach BOTH a sanitized (sensitive information removed) PCAP capture of SNMP Trap samples for the device and the MIB file(s) that define the Traps this device will support. Note that the PCAP file will not work as a Gist, it needs to be attached as a file to this issue.
The MIB file will give us the enumerated names of the metrics you wish to collect, while the output of the packet capture shows the "true story" of what a device will ship via SNMP Traps and is used to ensure that our profiles are efficient and accurate for your devices.

Hi,
With this request it looks like you haven't attached the required further information. Are you currently sending these traps into your account that we could work with?


add github action for cargo machete

This PR contains an action that can be added to any github workflow.

The example in the readme is incorrect. As there is no v1 release, it has to be cargo-machete@main for now.

Thanks, fixed in main.


Macro: Selected RNA preset not discards when mouse moved on canvas and 'ESC' button is pressed

Steps to Reproduce

Open Ketcher and switch to Macro mode
Switch to RNA tab
Select any RNA Presets
Move mouse cursor to canvas and press 'ESC' button

Actual behavior
Selected RNA preset not discards when mouse moved on canvas and 'ESC' button is pressed
Expected behavior
Selected RNA preset discards when mouse moved on canvas and 'ESC' button is pressed
Screenshots
https://github.com/epam/ketcher/assets/62464241/f767c288-53a8-4464-8aa9-007628974d15
Desktop (please complete the following information):

OS: Windows 11
Browser Chrome
Version 112.0.5615.138 (Official Build) (64-bit)

Ketcher version
Version 2.18.0-rc.2

Test automated.

Tested on 2.21.0-rc.1 Fixed.
https://github.com/epam/ketcher/assets/62464241/b93e6d4b-b7db-41c9-8830-8887667bbcf1


newtype_enum! macro should have it's own crate

It is actually an incredibly useful macro for autogenerating 'enums' and their debug for various codes that you receive from outside of Rust.
It's similar in its usefulness to the bitflags! macro, and it's a shame I have to copy it to my code from here instead of using a crate.
Although I didn't really search if anyone made it (or something similar) a separate crate already

It's similar in its usefulness to the bitflags! macro, and it's a shame I have to copy it to my code from here instead of using a crate.

Agreed! Didn't realize it could be so useful outside the project as well.
As far as I know, it shouldn't be any problem for it to be published as a separate crate, as long as this is done under the same open source license. If anyone is interested in doing so, feel free to continue the discussion here.

Although I didn't really search if anyone made it (or something similar) a separate crate already

I'm not sure about this either, a double-check would be indeed useful to avoid creating something which already exists.

This crate seems like a similar idea: https://docs.rs/fake-enum/latest/fake_enum/

Here's another crate with a similar feature: https://docs.rs/open-enum/latest/open_enum/
Given that there are a few crates that do similar things, I'll go ahead and close this issue.


Fix Headings in Readme to be in Markdown so the table of contents will work

In Markdown, HTML headings don't work when having links like the table of contents. To make headings work, each heading needs an id. Another way is to just use markdown headings like:
### this is heading 3
and you link to it by doing:
[Link to the heading 3](#this-is-heading-3)
https://gist.github.com/asabaylus/3071099

The table of contents seems to be functioning as far as I can tell, but the markup should be cleaned up anyway.
I was actually planning to rewrite the whole readme in the nearish future.

That would be nice, I would like each function documented, similar to how I did the listener API. The function name, or class name, all the arguments, and a description of each argument.
I also saw some functions in the code that are not in the readme.
When I click on a link, nothing happens.

The entire readme has been rewritten, with more comprehensive documentation and proper markdown links.


[Candidate 1v1 Egyptian Oasis ZH v1] Too many chicken sounds at right side middle farm

Issue Description
Too many chicken sounds at right side middle farm.
Expected behavior
Chickens occasionally make sounds, but not all the time non-stop.
Screenshots

Deleted 2 of 3 in this area and moved one to the right border.

Fixed with https://github.com/xezon/GeneralsRankedMaps/commit/c57ce6e07c423a8bc335d5977d36cb96bead11a4


Fork refresh

Will not merge. Discussion PR for the fact I'm going to shove this into master in a little bit.
Discuss.

Updating this fork of upstream's python-neutronclient with applied patches to support roles and noauth in public cloud (required for our clients to work)

what even is this?

Exactly what was discussed in the IRC. A refresh of the fork.

hold on to your butts


Allow contributors to be verified

Overview
Allow superusers to mark contributors as verified and show that verification status on the facility detail page and the contributor profile page.
Connects #545
Demo
Public Profile

My Profile Is Unchanged

Facility Details

Admin

Notes
Adding a verified flag and a description box accessible via the Django Admin is the simplest possible version of this feature. We can grow a more complicated process from this if we discover a need. We opt the model into history tracking so that we have a log of changes to the verified status.
We have opted to show the name of the contributor as the title on the profile page rather than the static string "Profile" to emphasize what the page is about, to save some vertical space, and to provide a high-profile place on the page to show the verification badge.
AppGrid only accepts strings for its title property so we are manually
creating an <h2> with the same style so we can show an icon as well as text.
Showing the verified badge next to a contributor on the facility details page
requires us to have the verified status of contributors available in the
facility details API response. The previous implementation of the
Facility.contributors model method was returning a string representation of
the contributor. To better separate concerns, this helper now returns a list of
FacilityList objects that contributed the Facility, leaving the rendering up
to the serializer. We are now returning a list of objects that include an
is_verified flag that we use to conditionally render a verified SVG icon.
In order to reuse the same icon we used on the profile page, we are now passing
through the style prop from BadgeVerified to the internal SvgIcon in order
to adjust the size, margins, etc.
This PR also includes a unrelated change to the Contributor serializer that avoids multiple database calls. This was made before realizing that we would not need to change the Contributor serializer to implement the feature, but it is a useful change anyway.
Testing Instructions
These instructions assume your database contains fixture data.

Run migrations with ./scripts/manage migrate
Seed the new history data with ./scripts/manage populate_history --auto
Log in as a superuser, browse http://localhost:8081/admin/api/contributor/2/change/, and mark the contributor as verified.
Browse http://localhost:6543/profile/2 and verify that the verified icon is displayed and that a "Verified" tooltip is shown on hover
Browse http://localhost:6543/profile/3 and verify that no icon is displayed
Browse http://localhost:6543/ and filter by contributor 2. Select a facility and verify that the verified icon is shown next to the contributor line on the detail page
Filter by a different contributor and verify that there are no badges on the facility detail pages.
Verify that the sample response on http://localhost:8081/api/docs/#!/facilities/facilities_read matches the actual API response shape.

Checklist

[ ] fixup! commits have been squashed
[ ] CI passes after rebase
[ ] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines
[ ] Create a release issue and include a step for running ./scripts/manage populate_history --auto

AppGrid only accepts strings for its title property so we are manually
creating an  with the same style so we can show an icon as well as text.

In another context I was thinking that we may want to consider changing the title prop on this component to be a node which could either be a string or another React component. Alternatively, we could just give it a component prop that would render in a way that superseded the title if it was there.
I don't know that we have to do this here if the h2 works well enough though.

Consider giving the verification badge span element a small amount of padding:

I have a migration conflict. Will be rebasing and fixing.

I tested out the main workflows for this and everything's working as expected!

I pushed a rebase:

Fixed the migration conflict
Updated AppGrid to accept node for title
Added padding around the verified badge on the profile page
Ready for a rereview

Thanks for the review.


Feature/bucket restructure

This updates the paths according to the new bucket structure and GitHub repo link once the name is updated from harmonized-wf-dev to pmdbs-bulk-rnaseq-wf.

I'm happy that we are driving the dataset organization logic into things.   Heads up on a future PR which will try to dis-entangle the "project_id" hacks into our more utilitarian <team_name> and <dataset_name> logic.


demo resourses not work in example htmls

I cloned the res pack and found some of them works well but more of them even not work.
1,works well:
tina / ligerZero / toru / trex / vegeta / xboxavatar_dehvor
2, works,but renders only one part of the gltf.scene
ahsoka_tano / cattus / tyranitar
all these 3 gltf files has moran than one part , the gltf parse function ignored the other parts?
3, not work
1),at_rt /cherubbotpm1 / gine / jinx / ronin /
everything is OK in blender but shows the following error:
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'idx')
Uncaught (in promise) SyntaxError: Unexpected token a in JSON at position 6
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'joints')
2), readplayerme
everything is OK in blender but shows the following error:
UtilArm.js:34 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'getSkin')
3),companioncube / sword_war
gltf file has no amature and it shows error:
UtilArm.js:34 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'getSkin')
4), suzanne
gltf file can not importted into blender and it shows the following error:
Uncaught (in promise) SyntaxError: Unexpected token a in JSON at position 6

I find out maybe something wrong in threejs/lib/UtilGltf2.js

while the sub-objects of gltf file >1, there need another parser to resolve file, but failed.
This may caused gltf parts disappeared.

This is very old, new work in in ossos_next, so this can probably be closed.


404

Describe the bug
A clear and concise description of what the bug is.
When I installed Asset HDA, added Topnet, and then added the node SD_Switch_Model1, the console displayed the message:
"Error retrieving list: models"
and "Server returned: 404".

Why am I getting an error of incorrect model path?

Check if you added --api key to your webui-user.bat.
Make sure to start A1111 with webui-user.bat
Check if Houdini is not blocked in your firewall
Check the url and the port, as they can vary depending on existing web-services on your computer

I ran the application on port 7860 and followed the instructions, including the config file, and restarted Houdini.
One strange thing is that the application ran successfully on the first attempt. However, after running it again, I encountered an error of not being able to connect to the model. I don't understand what is happening.

Can you show me the config.ini file as well?

[Main]
url = http://<IP_ADDRESS>:7860
timeout = 1.2
[Authorization]
useauth = False
username = test
password = pass

Usually reinstalling will succeed the first time.
However I will try again.
Thank you very much for your enthusiasm


feat: add include_reviewers for blunderbuss

Signed-off-by: hi-rustin<EMAIL_ADDRESS>close https://github.com/ti-community-infra/tichi/issues/486
part of https://github.com/ti-community-infra/tichi/issues/394
add include_reviewers for blunderbuss

/hold

[ ] docs

/unhold
/assign @Mini256
PTAL~ Thanks!

/merge


oid caching leads to broken queries after schema changes

All of the details asked for in the template below are specified in my reproducer https://github.com/davepacheco/diesel-oid.  I'll also fill it in as requested below but I think it'll be easier to just look at the reproducer.
Setup
Versions

Rust: 1.77.0
Diesel: 2.1.5
Database: PostgreSQL 16.2
Operating System MacOS Ventura 13.6.1

Feature Flags

diesel: default + "postgres"

Problem Description
We have a program that:

runs some queries that insert rows containing user-defined types
some other program runs a schema change that's compatible with the Diesel schema but changes the type's oid (i.e., drop the type and re-add it)
runs more of those queries

After the schema change, such queries start failing with errors like type with ID 218 does not exist (CockroachDB) or cache lookup failed for type 16455 (PostgreSQL)
You could argue that this is not supposed to work?  But restarting the application or executing the queries from new connections fixes the problem.  It's the stale cache in the Diesel connection that's broken and if it didn't cache the OIDs, I think the application would work.
I don't know if PostgreSQL provides any way for Diesel to handle this without the application's help.  If not, how should an application deal with this?  Should the application have a way to disable caching?  Or maybe a way to communicate to Diesel that the cache needs to be flushed?
To make things more complicated, the application where we actually hit this proactively populates the Diesel cache with all of our user-defined types to avoid lots of tiny queries for very short-lived connections (our test suite).
Relatedly: why is the cache per-connection?  We're using a connection pool.  So even if Diesel had a way to flush the cache and re-fill it, it's hard for us to go do that on every connection.  It'd be really nice if the cache were distributed via a watch channel or something where we could update a canonical copy and then propagate that out to all the consumers that want it.  I guess that might be hard if consumers need to modify it themselves as they run into new types that they need?
What are you trying to accomplish?
We're trying to manage an application where the database schema can change over time.  We're not yet doing online schema updates, in that we're not expecting the application to work seamlessly as the schema is updated.  We do expect that we can start the program, have it wait for the schema to match what the version that it understands, and then proceed.
First, we store an integer version number for our schema in a database table.
To update our system to a new version of the software + schema, we do the following:

shut the application down ("old" application version, "old" schema version)
replace the application binaries on disk
start the application again ("new" application version)

on startup, it checks the schema version.  It'll still be the old one.  It blocks, re-checking every few seconds until the version matches what's expected.

an operator executes a separate program to perform the schema update.

this unblocks the application above

Our problem is that Diesel may have cached some types' OIDs before the schema change.  If that happens, then the application is totally broken (lots of queries fail) after the schema change.
For much more detail, see oxidecomputer/omicron#5561.
What is the expected output?
For my reproducer, I expect no "cache lookup failed" error.
What is the actual output?
For my reproducer, I see the "cache lookup failed" error.
Are you seeing any additional errors?
See reproducer README or output below.
Steps to reproduce

Set up PostgreSQL 16.2 (version probably doesn't matter much) running on <IP_ADDRESS> port 5432 with a database called dap.
Clone https://github.com/davepacheco/diesel-oid.  This fully specifies the Rust version (rust-toolchain.toml) and dependencies (Cargo.lock).
In diesel-oid, run cargo run -- postgresql://<IP_ADDRESS>:5432/dap.

I see:
$ cargo run -- postgresql://<IP_ADDRESS>:5432/dap
   Compiling diesel-oid v0.1.0 (/Users/dap/diesel-oid)
    Finished dev [unoptimized + debuginfo] target(s) in 0.44s
     Running `target/debug/diesel-oid 'postgresql://<IP_ADDRESS>:5432/dap'`
connecting to: postgresql://<IP_ADDRESS>:5432/dap
connected!
initialized schema
inserted rows: 1
found rows: [MyTable { a: 0, b: One }]
updated schema
ERROR: second insert failed: cache lookup failed for type 16455
establishing second connection
connected!
insert on second connection worked: 1
contents of table after second insert (second conn):
rows: [MyTable { a: 0, b: One }, MyTable { a: 0, b: One }]
contents of table after second insert (first conn):
Error: listing contents of table

Caused by:
    cached plan must not change result type

I'm not worried about "cached plan must not change result type" -- I get that one.  The problem is the "cache lookup failed for type 16455".  I think what's going on is:

From one connection, we successfully INSERT a row into table my_table, which has a column of user-defined type my_type. This populates Diesel’s OID cache for the type my_type.
Then we change the schema in a way that’s compatible with the Diesel definition of that schema, but with a different OID (by dropping and re-creating the user-defined type).
Then we try the INSERT again. It fails unexpectedly. It appears that what’s happening is Diesel is sending the same OID as before, from its cache, but that’s wrong now.
To prove it’s just a caching issue: we create a second connection and do the same INSERT again. It works.

Checklist

[x] I have already looked over the issue tracker and the discussion forum for similar possible closed issues.  (related issues: #2088, #2071, #2203)
[x] This issue can be reproduced on Rust's stable channel. (Your issue will be
closed if this is not the case)
[ ] This issue can be reproduced without requiring a third party crate

I am not sure how to reproduce this without diesel_derive_enum but I do not believe it's related to the problem.

Thanks for filling this bug report. It's definitively helpful to have a good minimal example for this.
That written: I unfortunately see no good way to change the current behavior without running into massive performance problems. I think this essentially boils down to: Change the schema is only supported as long as the various internal caches in the connection are not populated yet. After that it's not safe to reuse the connection again and expect it to continue to work. You need to establish connections at that point by marking your connection pool as stale and reestablish connections. After all you know at that point you are calling these queries that something might go stale, which is more than diesel knows about that particular queries.
That written: I'm open to accept contributions to improve the current behavior, but I would strongly prefer first to have a suggested design before someone starts to implement something. For me that's currently not a priority (well maybe beside just adding a documentation note about this specific behavior).

Relatedly: why is the cache per-connection? We're using a connection pool. So even if Diesel had a way to flush the cache and re-fill it, it's hard for us to go do that on every connection. It'd be really nice if the cache were distributed via a watch channel or something where we could update a canonical copy and then propagate that out to all the consumers that want it. I guess that might be hard if consumers need to modify it themselves as they run into new types that they need?

Simply because there is no pool in diesel, we just provide support for r2d2 and that does not allow to store these information in the pool itself. That only leaves storing them in the connection. I cannot really comment for other third party pool implementations here. Again that's something where I would accept contributions to change it.

I'm also encountering this issue while doing schema changes on Postgres. Some examples:

Adding a variant to an enum
Changing the type of a column (e.g. from vachar(30) to varchar)

Because of the prepared statement cache, it is currently complicated to perform these schema changes without breaking the connections.
A few options:

Implement a more complex migration path over multiple deployments, paying attention to never update any type in the schema (also considering the complexity of testing these constraints, and the impact on shipping speed).
Stop the impacted services during the deployment. In my context, high availability is more critical than high performance, and this option is not viable.
Disable the prepared statement cache. We've successfully experimented with this option (see https://github.com/ignaskar/diesel/compare/ba2f567b...c2cb6d3). Ideally, we would be able to opt-out of the prepared statement cache at service startup or at runtime -- so we could disable the cache while we run our migrations.

@fbecart Please not that this issue is not about the prepared statement cache, but about the oid type cache which is something different. So your post here is off topic. Please create a new discussion if you feel that this needs to be discussed.

Thanks @weiznich for your patience, and sorry for the mistake. I will create a separate issue to have the conversation about the prepared statement cache.


Error: corrupted size vs. prev_size

Meet error when contracting of tropical tensor network:
julia> using TropicalGEMM, TensorInference, JLD, OMEinsum

julia> tn = load("contract_order/ObjectDetection_32.jld")["tn"]
TensorNetworkModel{Int64, SlicedEinsum{Int64, DynamicNestedEinsum{Int64}}, Array{Float64}}
variables: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60
contraction time = 2^25.941, space = 2^20.0, read-write = 2^23.128

julia> most_probable_config(tn)
corrupted size vs. prev_size

[3870633] signal (6.-6): Aborted
in expression starting at REPL[3]:1

version of package
(tensorinference-vs-merlin) pkg> st
Status `~/work/probabilistic-inference-in-the-era-of-tensor-networks-and-differential-programming/scripts/benchmarks/map/tensorinference-vs-merlin/Project.toml`
  [c7e460c6] ArgParse v1.1.4
  [6e4b80f9] BenchmarkTools v1.4.0
  [336ed68f] CSV v0.10.12
  [a93c6f00] DataFrames v1.6.1
  [b732b382] JunctionTrees v0.4.2
⌃ [8314cec4] PGFPlotsX v1.5.1
  [2913bbd2] StatsBase v0.34.2
  [c2297e78] TensorInference v0.4.1
  [a4ad3063] TropicalGEMM v0.2.0
  [56f22d72] Artifacts
Info Packages marked with ⌃ have new versions available and may be upgradable.

julia> versioninfo()
Julia Version 1.10.0
Commit 3120989f39b (2023-12-25 18:01 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 64 × Intel(R) Xeon(R) Platinum 8358P CPU @ 2.60GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-15.0.7 (ORCJIT, icelake-server)
  Threads: 1 on 64 virtual cores
Environment:
  LD_LIBRARY_PATH = /opt/slurm/lib
  JULIA_PKG_SERVER = https://mirrors.nju.edu.cn/julia

ObjectDetection_32.jld.zip
This is the jld file I used.

The error also happens on server with cpu Intel(R) Xeon(R) Platinum 8378A CPU @ 3.00GHz, but did not happed on our laptop with an apple m2 chip or an i7-10510U.

This problem seems to depend on specific CPU architecture. @chriselrod do you have any clue?


Unnatural (buggy?) behavior for intransitive() dependencies in compile and runtime configurations

Context: restrict the set of (transitively imported) libraries visible in compile configuration to bare minimum, retain the full set of binaries in runtme.
Define project with the following dependencies:
libraryDependencies += "org.apache.spark" %% "spark-mllib" % "2.1.0" intransitive()

libraryDependencies += "org.apache.spark" %% "spark-mllib" % "2.1.0" % "runtime" exclude("org.slf4j", "slf4j-log4j12") exclude("log4j", "log4j")

Problem:
> show externalDependencyClasspath
[info] * Attributed(/home/kamilk/.ivy2/cache/org.scala-lang/scala-library/jars/scala-library-2.11.11.jar)
[info] * Attributed(/home/kamilk/.ivy2/cache/org.apache.spark/spark-mllib_2.11/jars/spark-mllib_2.11-2.1.0.jar)

> show runtime:externalDependencyClasspath
[...]
[info] * Attributed(/home/kamilk/.ivy2/cache/org.slf4j/slf4j-log4j12/jars/slf4j-log4j12-1.7.16.jar)

slf4j-log4j12 should not be visible in runtime.
Only after adding explicit excludes
libraryDependencies += "org.apache.spark" %% "spark-mllib" % "2.1.0" intransitive() exclude("org.slf4j", "slf4j-log4j12") exclude("log4j", "log4j")

libraryDependencies += "org.apache.spark" %% "spark-mllib" % "2.1.0" % "runtime" exclude("org.slf4j", "slf4j-log4j12") exclude("log4j", "log4j")

does slf4j-log4j12 disappear from runtime, as desired.
sbt version: 0.13.15

$ sbt "show Runtime/externalDependencyClasspath" | grep slf4j
[info] * Attributed(/Users/eed3si9n/.coursier/cache/v1/https/repo1.maven.org/maven2/org/slf4j/jcl-over-slf4j/1.7.16/jcl-over-slf4j-1.7.16.jar)
[info] * Attributed(/Users/eed3si9n/.coursier/cache/v1/https/repo1.maven.org/maven2/org/slf4j/slf4j-api/1.7.16/slf4j-api-1.7.16.jar)
[info] * Attributed(/Users/eed3si9n/.coursier/cache/v1/https/repo1.maven.org/maven2/org/slf4j/jul-to-slf4j/1.7.16/jul-to-slf4j-1.7.16.jar)

I think this is fixed in sbt 1.3.2.


Missing info on using PowerShell to dissociate the IP address from the NIC configuration

On this page, The instructions for deleting a public IP address using PowerShell says:
Set-AzPublicIpAddress to dissociate the IP address from the NIC configuration.
But it doesn’t say how to use this commandlet to do that.  The reference page for Set-AzPublicIpAddress also doesn’t say how to do that.

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

ID: 61cbb094-49e2-cf03-c1b1-a7a73b2e5697
Version Independent ID: 4a950fe7-d89b-9e40-ea77-2d8a58011c99
Content: Create, change, or delete an Azure public IP address - Azure Virtual Network
Content Source: articles/virtual-network/ip-services/virtual-network-public-ip-address.md
Service: virtual-network
Sub-service: ip-services
GitHub Login: @asudbring
Microsoft Alias: allensu

Thank you for your feedback! We will review and update as appropriate.

Hello @FeedTheHungry, Thank you for the feedback.
I have made a PR to update the command to Set-AzNetworkInterface and the commands to diss-associate IP address from a NIC are provided here
Below are the commands.
$nic = Get-AzNetworkInterface -Name <NicName> -ResourceGroup <RGName>
$nic.IpConfigurations.publicipaddress.id = $null
Set-AzNetworkInterface -NetworkInterface $nic
Remove-AzPublicIpAddress -Name <IpName>-ResourceGroupName <RGName>
I have also created a documentation request to add this example to Set-AzNetworkInterface page.

The PR was merged and the change will go live soon. Please let me know if you have any questions. Thank you!


Fixing a broken link

Why:

Closes [issue link]
What's being changed:

Check off the following:

[x] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

Thanks for opening a PR 👍 Please fill out the pull request template in the top comment in this pull request, then we'll get this up for review!

I see this change has been applied outside of this pull request


Query data from table on difference MSSQL servers

Is your feature request related to a problem? Please describe.
There is no way to join data from tables on difference MSSQL server using single command.
Describe the solution you'd like
Ability to connect to MSSQL database on difference server on single instance so you can perform cross table query on single command.
Describe alternatives you've considered
I need to open 2 db connections to both server and perform full select query on both tables and store it to memory then compare it one-by-one. This is impossible to do with table contains huge amount number of records (e.g. 100M+ records)
Additional context
It would be great if table comparison is also implemented so you can compare data on table to find difference, it will be helpful to validate data on replication server

This isn't a thing for this package, rather you want to use linked servers.


FIX: Data doesn't represent J&J vaccine accurately

Some of the data providers don't report the J&J vaccine following our definition. They only include the J&J vaccine counts in their second dose column.
This pull request simply removes the total_vaccine_initiated column until either we can figure out how to separate the J&J dose counts from other vaccines, or the data provider changes the way they report.

Hey @tlyon3 thanks for doing this as asked.
I regrouped with the rest of the team and we decided to continue to provide the data as -is (even though we know it is wrong) and put a discliamer/note on the website saying we might be underestimating the number of people with at least one dose
We'll also keep an eye on these dashboards and hope they fix things up soo


--auto-gen-config not resolving all offenses after upgrading from 0.32.1

I'm having trouble reproducing this in an isolated code base, so here's the relevant information:

1779 ruby files
many offenses listed in the .rubocop_todo.yml file, which was generated by rubocop 0.32.1
everything is green in rubocop 0.32.1, but I'm trying to upgrade
the Lint/EndAlignment cop is set to AlignWith: variable
I have no Lint/EndAlignment offenses, but Style/ElseAlignment is disabled in the todo file
I upgrade to a newer rubocop (both 0.33 and 0.34 have this behavior), and now I have some new offenses, because some new cops were introduced
(my .rubocop_todo.yml is still the one generated by 0.32.1)
I don't want to resolve all of the new offenses right now, I'd rather just regenerate the .rubocop_todo.yml file, so I run bin/rubocop --auto-gen-config and it regenerates my .rubocop_todo.yml file.

At this point, when I run bin/rubocop, there should be no offenses, right?
I start getting a bunch of Style/ElseAlignment offenses.
Before the regeneration (excerpts):
# .rubocop_todo.yml
Style/ElseAlignment:
  Enabled: false

# .rubocop.yml
inherit_from .rubocop_todo.yml
Lint/EndAlignment:
  AlignWith: variable

After the regeneration (excerpts):
# .rubocop_todo.yml
Lint/EndAlignment:
  Enabled: false

# .rubocop.yml
inherit_from .rubocop_todo.yml
Lint/EndAlignment:
  AlignWith: variable

Two interesting things:

Lint/EndAlignment is disabled even though it's got a configuration (new offenses seem to have been discovered in 0.33 related to the alignment of the end of case statements, but I'm not sure which entry in the changelog is responsible for this)
Style/ElseAlignment is no longer disabled, even though those offenses didn't go anywhere, so now I have a bunch of new offenses

Desired behavior: after running bin/rubocop --auto-gen-config, there would be no offenses

It would be great if you could run git bisect to find where the bug was introduced.
cd /path/to/rubocop_repo
git bisect start
git bisect good v0.32.1
git bisect bad v0.33.0
git bisect run /path/to/testscript.sh
git bisect reset

# testscript.sh
cd /path/to/code_base_where_problem_was_found
/path/to/rubocop_repo/bin/rubocop --auto-gen-config
/path/to/rubocop_repo/bin/rubocop

:+1: trying it now

Kind of inconclusive. It found https://github.com/bbatsov/rubocop/commit/3bc885c131634b0da487c559f428ac6021a44563 as the first bad commit, but it doesn't seem related to me

Too bad. I was going to say that https://github.com/bbatsov/rubocop/commit/d8c7c376156890220139b51897f65dda707c74ed was a prime suspect, but it was merged after 0.33.0 was released. Could you still try and see what happens if you git revert d8c7c37?

@maxjacobson What if you rm the old .rubocop_todo.yml file before generating a new one?

Yea I think we moved on from the issue by manually resolving it, but I wanted to report it in case it's a bug that can be fixed. It's not a huge deal I think

My point was, I think the problem may have been caused by the presence of the old .rubocop_todo.yml. There is another open issue in this tracker regarding a similar problem.

Ah, got it.
I was under the impression that the .rubocop_todo.yml file was temporarily ignored while generating a new one -- at least, this seems to be the behavior.
I'll revert our codebase to when I opened this issue...
OK, yep, just reconfirmed the behavior from the original report. Trying now with removing the old file before generating the new one.
No, it seems to have the same behavior. Still some offenses snuck through.

No, it seems to have the same behavior. Still some offenses snuck through.

OK, that's good to know.

Is this codebase proprietary?

Yes. If you'd like, I can try to reproduce it in a public codebase

I can try to reproduce it in a public codebase

Please do.
My technique for coming up with minimal repro:

Fresh checkout of your private repo
Create a new branch, maybe call it debug_rubocop or something
Confirm you can reproduce the problem. Set yourself up so you can reproduce it with a single, short command (maybe a script).
Start deleting subdirectories. After each deletion, confirm you can still reproduce the problem. If you can, commit the change to the debug_rubocop branch. If you can't, back out.
Start deleting individual files. Same deal; commit if you can still reproduce.
Start deleting code from the files which remain (hopefully just one). Commit each time, if you can still reproduce.
If there are more than one file remaining, try merging their contents and see if you can still reproduce.
After a few hundred iterations, each of which should be fairly fast, you should be left with 1 or 2 very small files. Obfuscate the contents if you like by renaming methods, etc.

Could this bug caused by this line?
https://github.com/bbatsov/rubocop/blob/master/lib/rubocop/cop/style/else_alignment.rb#L89
How about this instead:
end_config = config.for_cop('Lint/EndAlignment')
style = end_config['AlignWith'] ? end_config['AlignWith'] : 'keyword'

Could this bug caused by this line?
https://github.com/bbatsov/rubocop/blob/master/lib/rubocop/cop/style/else_alignment.rb#L89
How about this instead:
end_config = config.for_cop('Lint/EndAlignment')
style = end_config['AlignWith'] ? end_config['AlignWith'] : 'keyword'

I think this reproduces the bug:
.rubocop.yml:
Lint/EndAlignment:
  AlignWith: variable

test case:
def method_name
  my_var = if condition
    'thing1'
  else
    'thing2'
  end

  my_var = if condition
             'thing1'
  else
             'thing2'
           end
end

I think this reproduces the bug:
.rubocop.yml:
Lint/EndAlignment:
  AlignWith: variable

test case:
def method_name
  my_var = if condition
    'thing1'
  else
    'thing2'
  end

  my_var = if condition
             'thing1'
  else
             'thing2'
           end
end

FWIW, it might be possible to trigger similar weirdness with Style/IndentationWidth (and maybe others):
https://github.com/bbatsov/rubocop/blob/master/lib/rubocop/cop/style/indentation_width.rb#L91
Is there a general policy to ignore the configuration of cops if they're disabled (which is logical, but will lead to this weirdness when using --auto-gen)?

FWIW, it might be possible to trigger similar weirdness with Style/IndentationWidth (and maybe others):
https://github.com/bbatsov/rubocop/blob/master/lib/rubocop/cop/style/indentation_width.rb#L91
Is there a general policy to ignore the configuration of cops if they're disabled (which is logical, but will lead to this weirdness when using --auto-gen)?

I think @madwort has done a nice job reproducing it. I tried but couldn't


How to build Boost website/docs locally?

Hello, Boost Development Team.
I noticed that there are:

https://github.com/boostorg/boost/tree/master/doc
https://github.com/boostorg/asio/tree/develop/doc
https://github.com/boostorg/website
...etc

which seem related to Boost website/docs.
If I want to build the Boost website locally, including its documentation, what commands should I run? Can I use cmake to build the whole website/docs?
Besides, I want to know what tools/methods Boost use to build its website/docs? (Since most of C/C++ projects use Doxygen, Sphinx, or QDoc to do so, but it seems that Boost doesn't belong to one of them)

You might want to start here: https://www.boost.org/doc/libs/1_83_0/doc/html/boostbook.html


WSL preview doesn't open browser, maybe print URL to terminal window as workaround?

🐛 Bug Report

Environment

operating system: Windows 10 build 19013
output of rustc -V: rustc 1.36.0
output of node -v: v12.10.0
output of wrangler -V: wrangler 1.5.0

Steps to reproduce
$ wrangler preview --watch
or
$ wrangler preview
What did you expect to see?
A browser opening
What did you see instead?
First, thank you very much for making this 🙏🏻, it's really a joy to have a tool like this. 🙌🏻 I use it both on my Mac and Windows, but I'm reporting this bug/feature request as a Windows user.
The browser doesn't open. While WSL2 doesn't have xdg-open like the Linux variants, you can open the default browser using cmd.exe because of interop with Windows.

So a command of:
$ cmd.exe /c start http://example.com?foo=bar would work on WSL2 environment.
Also printing --verbose doesn't print the URL either.

I do hope you add this 🙏🏻. Also maybe an interim, have the preview URL printed, so I can copy and paste manually on the browser?

hi @thisguychris ! thank you so much for the kind words and the thoughtful issue! i actually think this shouldn't be too hard- right now we don't treat windows and WSL differently and if we can reliably detect WSL, we can make this change!
the piece of code that this runs is: https://github.com/cloudflare/wrangler/blob/master/src/commands/preview/mod.rs#L100
i don't have access to a WSL machine at the moment because i am traveling! but if you want to give this a try in a PR i'd be happy to help mentor you through it!

Hey, @ashleygwilliams 👋  I honestly haven't touched any Rust code yet, I mostly code in JS. But just hearing you mentor me, makes me really excited, I really appreciate your kind gesture.
There's nodejs library for detecting WSL (a fairly popular one), and it seems to check for the os-release if it includes "microsoft" as well as checking /proc/version output:
is-wsl https://github.com/sindresorhus/is-wsl/blob/master/index.js
I would gladly test it if you lack a WSL machine. Let me know what you prefer, I'm down on just being a tester, or make a PR (under your guidance), but I really haven't touch any rust code yet, so I don't know where to start ✌🏻

Hello 🙋🏻♂,
I want to give an update. If you set your $BROWSER variable correctly, xdg-open should work.
In my case, to open it in firefox, I just symbolic link firefox.exe via
ln -s /mnt/c/Program\ Files/Mozilla\ Firefox/firefox.exe firefox under my ~/bin directory where I have in my $PATH variable.
And set my browser variable to that symbolic link
export BROWSER=firefox
It should open on that browser, in this case, firefox. So just setting this variable would suffice, no change needed in wrangler binary.
@ashleygwilliams If you could point me where to put this in the docs, I'll gladly submit a PR to resolve this. 🙂

Hey @thisguychris - that's great news! Does this mean we can close #934?
As for the docs question, I think it would probably go really well here: https://github.com/cloudflare/workers-docs/blob/master/content/tooling/wrangler/commands.md#-preview
cc @victoriabernard92

@EverlastingBugstopper yes please, I just posted this WIP so I can ping @ashleygwilliams about the error I’m getting. I do think leveraging xdg-open is the most straightforward way to support WSL/2.
I do wish we can somehow note for WSL users how to leverage xdg-open. Let me know if I can help with documentation. 🙂


feat: use tree for bottom panel options

Description:

What does this PR do?

This PR lays the foundation for easy use of trees, and uses them for bottom panel options.

Why is this change necessary?

Over time, as the number of settings available from the editor grows, the readability of this window will diminish and using it will become difficult.
The approach introduced in this PR simplifies both the programming of this window and allows the creation of collapsible sections, which allows the creation of sections of common settings.
In addition, it might someday be possible to consider using a tree to display test results in the editor.

What issues does this PR fix/close?

N/A
Testing:

How was this PR tested?

Manual testing

Are there any known issues or edge cases?

Styling is a bit wonky
Checkbox label is not expanded to the right

Checklist:

[x] Code is formatted correctly.
[x] Documentation is updated (if necessary).
[x] Changelog is updated (if necessary).
[x] All new and existing tests passed (unit and E2E tests).

To do before merging

[ ] Unit tests
[ ] Fix tree styling
[ ] Expand checkbox label to the right

Hey @OpalSoPL, what do you think about this change to the bottom panel options?

I had never used Tree node, but it looks interesting. Current implementation is better than what I wrote.
this will make adding future settings easier, that's for sure.


style: fix linting

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Refactor/nimble

BLE library switched from ESP32 BLE Arduino to NimBLE. https://github.com/h2zero/NimBLE-Arduino/blob/master/docs/Migration_guide.md


Broken environment reflections when using render to texture

Description
When rendering a model with a secondary camera into a renderTarget, the reflections are broken.

I was able to reproduce this using a totally clean checkout against latest main and v2.1.0.  Weirdly enough the same code running on the examples website seems to work???
A video showing swapping between the main camera and secondary camera.  other assets (but not all) also show the same effect
https://github.com/user-attachments/assets/3819627c-44a2-44d9-97cf-94ad3ae68593
Steps to Reproduce

load the examples app locally
load up the render to texture example
load this model with this code

            app.assets.loadFromUrl("https://world-streaming.magnopus-dev.cloud/O2Dev/67548441877a5745676d75f6/6754846b877a5745676d75fe/1/redesign_deathclaw_lod0_lod3.glb", "container", function (err, asset) {
          const entity = asset.resource.instantiateRenderEntity({
              castShadows: true
          });
          app.root.addChild(entity);
            })

and add ContainerHandler + Basis
4.  See that the model in the render to textures is super shiny and totally broken

Interestingly this seems to work on WebGPU for me, only the WebGL has the issue.

Learnings as I investigate this:

it happens on both WebGL and WebGPU, if we set flipY to true on the render target. The issue is related to the flipping. We currently do the flipping by mirroring the projection matrix along the Y.
The issue comes from fresnel calculation. We do this:

dReflection.rgb *= getFresnel(
    dot(dViewDirW, litArgs_worldNormal), litArgs_gloss, litArgs_specularity
);

If I comment out this block, both rendering's match. So the problem is the fresnel term is incorrect in the texture. Could be either problem with viewDir, or with worldNormal.

passing -litArgs_worldNormal to that function instead of litArgs_worldNormal solves this. Just need to figure out a generic solution, other implications.


Feat/msdk 358 add pagination support

if I remove createQueryStub in the suggested changes, the tests fails

if I remove createQueryStub in the suggested changes, the tests fails

You're right. Fix the code smell and you can merge

This PR includes breaking changes. @shuffledex Please, add the commit to indicate it and a brief explanation of them in the PR description.

This PR includes breaking changes. @shuffledex Please, add the commit to indicate it and a brief explanation of them in the PR description.

its already there! https://github.com/PolymathNetwork/polymesh-sdk/pull/343/commits/60532ced6335cbe85867edae6db5c89be27bf5a8

:tada: This PR is included in version 4.0.0-alpha.27 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0-beta.2 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat(packaging): move packaging to a single "@angular/material"

Moving forward, we will only publish a single @angular/material package for the Angular2 Material project. This simplifies installation and usage for everyone, and won't increase the size of the library for people using AoT. It is also assumed that most people who use Angular Material will use most of the components so using a single UMD bundle should not increase their package size too much in JIT.
BREAKING CHANGES
People using npm install @angular2-material/COMPONENT_NAME need to remove all their @angular2-material dependencies and use a single @angular/material dependency instead.

When should we start using npm install @angular/material?

@jelbourn: this is ready to be reviewed.
Sourcemaps are still messy (they give the tsc output), but for now this will unblock you for AC. I'll improve in a subsequent PR.

Okay. Will do that when I'm back from dinner


Maximum Sum along any path in java

issue #683 in java

Update the readme also of the tree folder.


bug: KeyError: 'TERMIC_MAIL_SERVER'

Ubuntu 22.04
git clone https://github.com/spidersouris/termic.git
cd termic/
python3 -m venv .venv
source .venv/bin/activate
sudo apt install libpq-dev (https://github.com/spidersouris/termic/issues/7#issue-2628458824)
pip install -r requirements.txt
python termic.py

± |main ?:1 ✗| → python termic.py
Traceback (most recent call last):
  File "/home/damufo/dev/termic/termic.py", line 8, in <module>
    from config.mail_config import Config
  File "/home/damufo/dev/termic/config/mail_config.py", line 3, in <module>
    class Config:
  File "/home/damufo/dev/termic/config/mail_config.py", line 4, in Config
    MAIL_SERVER = os.environ["TERMIC_MAIL_SERVER"]
  File "/usr/lib/python3.10/os.py", line 680, in __getitem__
    raise KeyError(key) from None
KeyError: 'TERMIC_MAIL_SERVER'

Hi! Sorry for the late reply. I will make changes to how env vars are used/loaded for people who want to run their own version of termic. Will take a look this weekend.

OK! 🙂
Very thanks!!

You should now be able to run termic without having to specify a mail config. If some critical mail key is missing, the mail feature will be disabled. I have updated the README to reflect this. Please let me know if everything works as expected!

Not wor for me.
git pull and after:
|.venv|py-3.10.12 mybook in ~/dev/termic
± |main ?:3 ✗| → python termic.py
File "/home/myuser/dev/termic/termic.py", line 26
f"The following keys are missing: {", ".join(missing_keys)}"
^
SyntaxError: f-string: expecting '}'
|.venv|py-3.10.12 mybook in ~/dev/termic

argh, this is because I tested using Python 3.12 (which supports nested quotes for f-strings). Should be fixed now, can you try?

Very thanks! 🙂
Now start.
But not work,  database not exists. That is no error,  documentation on how to set up a sample database would be missing.
I open another issue. 🙂


Adding content to README.md

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind update

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area manifests

/area documentation

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

@vjjmiras: The label(s) area/documentation cannot be applied, because the repository doesn't have them.

In response to this:

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind update

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area manifests

/area documentation
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

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

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

7b48228 Merge branch 'falcosecurity:main' into 20220620-doc

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: vjjmiras
To complete the pull request process, please assign leogr after the PR has been reviewed.
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @vjjmiras! It looks like this is your first PR to falcosecurity/deploy-kubernetes 🎉

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: maxgio92, vjjmiras
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [maxgio92]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 2fb68529e4b3c6c9ce756db0d50b2c395a86360c

/cc @leogr


Does GPUImage expect Unpremultiplied Alpha?

I was trying to load png data into a texture with premultiplied alpha. I noticed transparent white renders more grey, meaning its not handling the premultiplied pixels correctly.
Does GPUImage expect that all image data is unpremultiplied?
I've read that with premultiplied inputs you need to have a special blend function and I haven't found that in the GPUImage source.

I have the same trouble, only completely transparent pixels are drawing actually transparent;
Semi-transparent pixels draws with additional transparent grey background;


Render Settings Previewer

Add a preview as the render settings are changed, so users don't need to use gas to see how the setings would affect their token.

http://localhost:8080/render   .   taking a look at how this is rendering..


On Safari, images tend to be blurry when zoomed in in the preview

Hi, I have a problem that is specific to Safari.
The problem is very simple: images tend to be blurry when zooming in on safari. This problem only affects the preview, not the final cropped image. Images look fine when zoomed in in Chrome and Firefox.
Step to reproduce

Download the image file provided at the bottom of this issue
Open this sandbox: https://codesandbox.io/p/sandbox/react-easy-crop-custom-image-demo-forked-ly5vr2?file=%2Fsrc%2Findex.js
Import the image
Zoom in
Compare the result between Safari and Chrome

Safari
Chrome

Investigations result
The level of added blur when compared to chrome can vary a lot based on the image quality and the screen resolution. In some situations, the difference between chrome and safari can be very small. In some other cases it's really big. The blur seems much worse with high resolution images.
Based on my investigations, the problem seems related to how safari handles CSS scaling transform.
I'm not sure that a workaround is possible, but I would like this to be at least listed as a known issue because it can be really problematic in some cases.
Thanks for your help !
You can use this image in the sandbox:

Thank you for taking the time to write such a detailed and clear issue.
This indeed seems to be a Safari specific buggy behavior. I found multiple threads related to that. It would be great to find a workaround that we could only apply to Safari.
In the meantime, I'm fine with adding a "known issues" section in the Readme. Do you want to take care of it?

My pleasure, I'm glad if it could help you. It would be nice to find a workaround but I'm not very optimistic.
I could take care of the new known issue entry in the Readme but not until the end of the week.


Pricing Page: Updated Gen AI Icon

The first icon in the list was being cutoff on the bottom. I have adjusted the viewbox of the svg to accommodate the specified sizing of the icons.
Test URLs:

Before: https://main--express--adobecom.hlx.page/express/pricing
After: https://gen-ai-icon-cutoff--express--adobecom.hlx.page/express/pricing?lighthouse=on

Let's use target branch for stage first.

Closing this one out with the extra commit and creating a new one here: https://github.com/adobecom/express/pull/184


jest framework disrupting codebases w/o spec file on keyword TEST

Version
27.5.1
Steps to reproduce
yarn add -D @nrwl/angular
npm install -D @nrwl/angular
yarn add -D @nrwl/nest
npm install -D @nrwl/nest

Using the Angular Plugin Generating an application It's straightforward to generate an Angular application:
nx g @nrwl/angular:app appName
create a nestjs app or an angular app
npx nx g @nrwl/nest:app api-koa
okay... moving on
each one creates an environments directory
if I create a new file environment configuration named environments.test.ts and add it to the environments directory (you can copy off a pre-existing one too it will suffice)
then run your test... for this Nx elite environment
nx test
jest will parse this and start barking that there are no spec files for this typescript file and fail the test run
when we rename the typescript file to environments.qa.ts test passes for this directory
no one wants to get into the business of tinkering with config paths to fix these issues on an individual basis when these are set boiler plate by elite high end schematics
Expected behavior
Honestly isn';t it a bit much to scan the entire project tree and search out folders that have keyword TEST and then start applying case logic? This is like inventing something that dont exist nor needs to exist. Its not like jest is the #1 software on the planet. I think they should lax their case logic a bit and opt for not disrupting any given codebase because then the developer has to change context switch gears and begin a new research thread on what flags exist the how why what and try to change whats being induced..
we are modifying our codebases on a large scale using schematics
this kind of interference is unwarranted and its validity questionable
my test run should pass
im sure the committer for jest wants to make sure we test everything but there are some files a bit more complicated to test like config files?
AND WHY SHOULD IT BARK IF THERE IS NO SPEC FILE THERE IN THE FIRST PLACE
Actual behavior
TEST RUN FAILS false positive which turns out to be negative
Additional context
this induced logic is presenting extraneous effort preventing developers from focusing on pure business logic and on build issues
nx run admin-api:test

 FAIL   admin-api  apps/admin-api/src/environments/environment.test.ts
  ● Test suite failed to run

    Your test suite must contain at least one test.

      at onResult (../../node_modules/@jest/core/build/TestScheduler.js:175:18)
      at ../../node_modules/@jest/core/build/TestScheduler.js:316:17
      at ../../node_modules/emittery/index.js:260:13
          at Array.map (<anonymous>)
      at Emittery.emit (../../node_modules/emittery/index.js:258:23)

Environment
nx report

 >  NX   Report complete - copy this into the issue template

   Node : 16.15.1
   OS   : darwin x64
   yarn : 1.22.18

   nx : 14.4.3
   @nrwl/angular : 14.4.3
   @nrwl/cypress : 14.4.3
   @nrwl/detox : Not Found
   @nrwl/devkit : 14.4.3
   @nrwl/eslint-plugin-nx : 14.4.3
   @nrwl/express : 14.4.3
   @nrwl/jest : 14.4.3
   @nrwl/js : 14.4.3
   @nrwl/linter : 14.4.3
   @nrwl/nest : 14.4.3
   @nrwl/next : Not Found
   @nrwl/node : 14.4.3
   @nrwl/nx-cloud : 14.2.0
   @nrwl/nx-plugin : Not Found
   @nrwl/react : Not Found
   @nrwl/react-native : Not Found
   @nrwl/schematics : 8.12.11
   @nrwl/storybook : 14.4.3
   @nrwl/web : 14.4.3
   @nrwl/workspace : 14.4.3
   typescript : 4.7.4
   ---------------------------------------
   Community plugins:
   	 @fortawesome/angular-fontawesome: 0.11.1
   	 @ionic/angular: 6.1.14
   	 @ngrx/component: 14.0.2
   	 @ngrx/component-store: 14.0.2
   	 @ngrx/effects: 14.0.2
   	 @ngrx/entity: 14.0.2
   	 @ngrx/router-store: 14.0.2
   	 @ngrx/store: 14.0.2
   	 @nxtend/capacitor: 13.0.0
   	 @nxtend/ionic-angular: 13.1.0
   	 @storybook/angular: 6.5.9
   	 angular-builder-custom-terser-options: 1.0.1
   	 @compodoc/compodoc: 1.1.19
   	 @ngrx/schematics: 14.0.2
   	 @ngrx/store-devtools: 14.0.2
   	 ngx-build-plus: 14.0.0

i guess this will continue to occur for any filename with TEST embedded in its file name anywhere within the codebase.
given high end scalable codebases being modeled with elite schematics...
we have countless generatED BY DEFAULT test.ts modules/files per library which number hundreds
thanks facebook


Make available via Alcatraz

Could you make that available via Alcatraz?

I will, but later.  This needs to be fixed. IOW find exact location where NSLigatureAttributeName is set to @0 and replace it with @1.

On hold till #2 will be fixed.

Fixed.


Typo "@provstr"→"@provstr"

Bold with escape characters
https://docs.microsoft.com/en-us/sql/connect/oledb/features/service-principal-name-spn-support-in-client-connections?view=sql-server-ver15

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Verified the update.


Build status badge link directs to 404

https://github.com/NVIDIAGameWorks/dxvk-remix/blob/1c1b6c6409de3a79425757fc12357614a19bc469/README.md?plain=1#L3
This line is linking to a 404 (at least as a user outside of the org that doesn't have access to actions)
I think if it would link to https://github.com/NVIDIAGameWorks/dxvk-remix/blob/main/.github/workflows/build.yml instead, it would work for any users.
I would've opened a PR, but I'm not too knowledgeable about your build pipeline so I wanted to create an issue first.

Fixed by enabling Actions on the repo.

awesome, thanks!


RadioBox First Steps

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
All new code requires tests to ensure against regressions

Description of the Change
I Added the Annotation @RadioBox which have 2 parameters ::
-First :: As all existing annotations the 'title'
-Second :: the titleMap which is a class that should extends 'TitleMapsAdapter'  and overrides the method 'getPossibleValues()' in which the user will decide what possible values can he return in a HashMap<String ,Object>.
This Map will be used by the 'RadioBoxGenerator' to add an ArrayNode named 'titleMap' to our field Form Definition ObjectNode. ['titleMap' defines the names and values of our RadioBoxes in the resulted Form].

Alternate Designs
---note :: This mechanism could be reused in the ComboBox.
The choice of making the HashMap supports Object types, brings more flexibility to the Adapter and leaving the choice to the user deciding the Type to put in the Radio's value.
---note :: This idea comes to me after noticing that the method 'ObjectNode.put()' can support many types as values.

Why Should This Be In Core?
This is an elementary functionality.

Benefits
The major benefit is the growing  number of the supported layouts.

Possible Drawbacks
'TitleMapsAdapter' may cause some problems.

Applicable Issues
can't find yet

Changes Unknown when pulling 1553aeb5f37333975f27fc737ecbfe6193806e41 on DhiaEddineSaidi:master into ** on JsonSchema-JavaUI:master**.