[BUG] Discrepancies in Pinecone index query results between REST API, custom Python.

Hi there!
First of all, as we're dealing with open source, big kudos to the maintainers and to @igiloh-pinecone and @izellevy who have been responsive in the past on some questions!
My use case is that I would really need to capture the different sources / vectors that were used making the final response, which is currently only possible by making the ChatEngine call in the code instead of using the built-in REST API of canopy-server.
The issue I'm facing is that based on the same Pinecone index and namespace, I'm getting very different responses using the built-in REST API and the proposed code from the library.md docs.
Configuration
For simplicity sake, I'll stick to 1 example:

Pinecone configuration: serverless, with about 320k vectors in it
Python: 3.9.12
chunk size: 4000 (Is this too big? I thought I saw it as the default for chunking in the canopy code)
Canopy version 0.7.0 - both the canopy REST API and the canopy code imports are based on the same package, as far as I can tell
The question that is prompted: "what can you tell me about superconducting magnetic energy storage?"
The (at least 1) piece of relevant vector contains the following meta-data:

source: https://energy-nest.com/energy-storage-technologies,
text: In another type of electrical energy storage, so-called superconducting magnetic energy storage, a direct current from a rectifier flows through a coil made of superconducting material such as compounds of iron, phosphorus, lanthanum or oxygen. This creates a magnetic field in which the energy is stored.

After the accumulator is loaded, the power supply is interrupted and a switch made of likewise superconducting material is actuated. This switch is responsible for disconnecting the coil from the inverter. The circuit is then reconnected to the inverter to discharge the stored energy. In this way, alternating current is generated from the direct current.

The efficiency of this type of energy storage system for generating direct current is around 97 percent. However, considerable cooling requirements need to be taken into account, which often stand in the way of the technology’s economic industrial use.

The code of the "advanced" way of using canopy, following the library docs

       Tokenizer.initialize()

        pinecone_index = os.environ['PINECONE_INDEX']
        pinecone_namespace = os.environ['PINECONE_NAMESPACE']

        kb = KnowledgeBase(index_name=pinecone_index)
        kb.connect()

        context_engine = ContextEngine(kb)

        llm = OpenAILLM()
        chat_engine = ChatEngine(context_engine=context_engine, llm=llm)

        response = chat_engine.chat(messages=messages, stream=False, namespace="pinecone_namespace")
        print("-----------------")
        print(response.debug_info) # Used to make the findings below in the issue post

Scenario output
Scenario 1: Using the built-in Canopy REST API endpoint
Q: what can you tell me about superconducting magnetic energy storage?

A: Superconducting magnetic energy storage (SMES) is a type of electrical energy storage technology. It involves the use of a coil made of superconducting material, such as compounds of iron, phosphorus, lanthanum, or oxygen. A direct current from a rectifier flows through this coil, creating a magnetic field in which the energy is stored. The stored energy can be discharged by reconnecting the circuit to an inverter, which converts the direct current back into alternating current. The efficiency of SMES in generating direct current is around 97 percent. However, the technology's economic industrial use is limited due to significant cooling requirements. SMES has potential applications in the field of electricity transmission and can significantly reduce the materials used for energy transmission compared to conventional power cables. Superconducting transmission technology is expected to be commercially available by around 2030. It is also worth mentioning that SMES is a form of energy storage that has to compete with other alternatives, including chemical batteries and physical storage systems. (Source: https://energy-nest.com/energy-storage-technologies, https://worth.com/new-electric-grid-batteries-turn-heat-into-light/, https://www.currenteurope.eu/efficient-electricity-grids-are-key-for-a-net-zero-industry-and-managing-demand-for-critical-raw-materials)

Scenario 2: Using the python code mentioned above - varies from either no response or a response made up solely by the LLM
Q: what can you tell me about superconducting magnetic energy storage?

A: Superconducting Magnetic Energy Storage (SMES) is a technology that uses superconducting coils to store electrical energy in the form of a magnetic field. This technology relies on the principle of superconductivity, where certain materials exhibit zero electrical resistance at low temperatures.

SMES systems consist of a superconducting coil that is cryogenically cooled using liquid helium to maintain its superconducting state. When electrical energy is supplied to the system, the current flows through the superconducting coil, creating a strong magnetic field. This magnetic field stores the energy.

SMES systems can deliver stored energy back to the grid when needed by reversing the process. The magnetic field collapses, generating a current that can be converted back to electricity and supplied to the grid.

SMES offers several advantages as an energy storage technology, including high power density, fast response times, and a high energy storage capacity. It can be used to address power quality issues such as voltage and frequency fluctuations and can provide backup power during grid outages.

Source: Adapted from multiple sources, no specific source provided in the context.

Scenario 3: Using the python code mentioned above - but with only the 1 relevant document in the pinecone index
Q: what can you tell me about superconducting magnetic energy storage?

A: Superconducting magnetic energy storage (SMES) is an electrical energy storage technology. In SMES, a direct current from a rectifier flows through a coil made of superconducting material such as compounds of iron, phosphorus, lanthanum, or oxygen. This creates a magnetic field in which the energy is stored. After the energy is loaded into the accumulator, a switch made of superconducting material is actuated to disconnect the coil from the inverter. The circuit is then reconnected to the inverter to discharge the stored energy, converting it into alternating current. The efficiency of SMES for generating direct current is around 97 percent. However, it is important to note that SMES requires significant cooling, which often hinders its economic industrial use.
(Source: https://energy-nest.com/energy-storage-technologies)

Findings
Difference in retrieval by the built-in canopy REST API then in the example
By logging the debug info, it looks like scenario 2 fetches all kinds of unrelated vectors, having nothing to do with the initial question, the scores for those documents are around 0.06. Checking out the scores for Scenario 3, it did find the content - as it was the only document in the pinecone index for that scenario - and the score of the document wass -0.03 roughly.
So it seems it gets the retrieval part "wrong", but what is odd is that the built-in canopy server, which afaik uses default values just like in the code example, does get the retrieval part right. So my assumption is very likely wrong, and I'm missing some sort of addition initialisation or configuration.
This is where I'm kind of hard stuck and would greatly appreciate any pointers and I'll be more than happy to make a PR making the library.md more complete!

@coreation from the top of my mind, two immediate thoughts:

Chunk size of 4000 is actually quite large. Chunk size is usually set in the area of 256-512 tokens. It would be very hard for an embedding model to represent such a long text into a single semantic representation. This might explain the poor retrieval results.
You mentioned changing some default parameters (e.g. chunk_size). How did you change these parameters? By setting them in a config file? If so - when you tested manually with Python code, have you used the same config file and\or the same parameter values? Otherwise it had probably used the built-in defaults.

@igiloh-pinecone thanks for the quick thoughts,

I found it a bit large as well, but I found the default in this file. The chunk_size there is set to 4000... Am I reading this wrong?

I'm not using the embedding via canopy directly as I need to embed some things coming from a database, so I used the splitter, and thus the "4000" chunk size and then did the embedding and storing myself in Pinecone. I'll try to use 1024 as I've read a couple of articles, amongst which this one that point out there's no real "good size", but 1024 seems to be a good sweet spot. I'll re-embed everything and see if things get better.

@igiloh-pinecone , it looks like the "chunk_size" in the splitter is actually referring to the amount of characters... I'm using the OpenAI tokenizer online to see how many tokens my pieces of text have and they're all around 700 tokens instead of 4000. So I've misinterpreted "chunk size" for "token size".
So the code to split up my text is as the default is described in the LangChain text splitter:
RecursiveCharacterTextSplitter(chunk_size=4000, chunk_overlap=200)

@igiloh-pinecone I've received a Github comment update but I don't see your update here on the thread. But just to answer the question you wrote, I'm using indeed the LangChain Recursive splitter, which I believe does take the parameter in terms of "characters", not tokens. If I take random samples of my vectors, the text is around 700 tokens.
Is your suggestion to lower that amount and use the Canopy Chunker?

I noticed your previous message where you stated that you use langchain directly, so I deleted mine as it was irrelevant.
My main point wasn't actually about the chunk size itself (I guess ~700 tokens is workable) - but rather a question of how do you configure your canopy server versus how did you configure the direct python ChatEngine. Are you sure you've used the same config \ params?
On more suggestion - can you please try repeating the same question 2-3 times in each scenario (server API vs direct python class)? Could it be that the underlying LLM is simply a bit "noisy", answering the same question differently every time?

hey @igiloh-pinecone what you see in the code example is the only configuration I use, it's the same as the variables I export before I star the canopy server. So that's simply the pinecone API key, OpenAI API key and index/namespace.
I've tried repeating the questions, but it seems like it's the same thing.
Do you guys offer any paid support by chance? I'm sort of knowledgeable on a high-level about a couple of RAG frameworks, this is the first that does away with a lot of fluff because it's more tailored towards a use case. I can try again using LangChain, but the state of LangChain for someone who isn't day-in day-out on top it, is just too much to keep up with.

@igiloh-pinecone perhaps not unimportant, the "text" property in Pinecone is often displayed as type "[]" instead of text, is this because of the new lines from the chunking?

@igiloh-pinecone ... I found the issue after letting the code ponder in the back of my head :) The default encoder has changed to the latest openai embedding (small) model, while my embeddings were still on ada embeddings. I see that in a previous canopy install, in all likelihood, the one running canopy server, the default encoder is still pointing to ada-002... So that explains the trash results my knowledge base gave me, while at the same time the built-in canopy server is returning decent RAG based results.
I'll see if I find the time to make a documentation PR so that the encoder is explicitly passed in the advanced example in the library.md.

The default encoder has changed to the latest openai embedding (small) model, while my embeddings were still on ada embeddings.

Thanks for the detailed response @coreation !!
That's definitely an oversight by us. We shouldn't have changed the default like that without at least highlighting it as a breaking change. I will change the issue's name to make it more discoverable by other users encountering the same problem.

Gist for other people encountering this problem:
Before version 0.7.0, Canopy's default RecordEncoder was OpenAI(model_name=text-embedding-ada-002). In version 0.7.0, the default was changed to use OpenAI's new embedding model (text-embedding-3-small).
If you have inserted your documents in the past using an older Canopy version, then upgraded Canopy and tried using the query() or chat() functionality - your newly loaded instance would be using a different embedding model than the one the documents were inserted with.
To fix this problem:

run canopy create-config <path> command to generate Canopy's default config templates in your desired <path>
Edit the default.yaml file, changing the [embedding model_name](https://github.com/pinecone-io/canopy/blob/50414f5e1a19d0ed86aa5edeece955ef7d5b44f7/src/canopy/config_templates/default.yaml#L115totext-embedding-ada-002`.
Run canopy with the new config - canopy start --config <path>/default.yaml


Update Azure Maps to V3

Updated Azure Maps to V3, see also https://learn.microsoft.com/en-us/azure/azure-maps/release-notes-map-control

@cschotte Thanks for the PR, I appreciate the update! Is there any known breaking changes between the V2 and the V3 which would require a new major version of this library ?

Forget my question, I just realised this would only be a change on the blazor application itself. All good then :)


Unable To Use The Dependency On Xcode 9-beta

I am using Xcode 9-Beta for development. And I've not been able to utilize the TRON library. Most of the errors are coming from the Alamofire library. I could modify the libraries to work, but it's a project being worked on by more than one person. So, is there a way to have this fixed or I've to go migrate my codebase back to 3.1?
I installed Alamofire 4.4 and it's working fine. But, the one bundled with TRON is failing when building.
Thanks

How are you installing TRON, using Carthage or CocoaPods?

@DenHeadless Cocoapods

So, @DenHeadless I had to work from this commit
There was an error in the UploadAPIRequest file. Which I had to fix for the mean time. It basic and pretty straight forward
Previous
let multipartConstructionBlock: (MultipartFormData) -> Void = { requestFormData in
            self.parameters.forEach { (key,value) in
                requestFormData.append(String(describing: value).data(using:.utf8) ?? Data(), withName: key)
            }
            multipartFormDataBlock(requestFormData)
        }

After
let multipartConstructionBlock: (MultipartFormData) -> Void = { requestFormData in
            self.parameters.forEach { (arg) in

                let (key, value) = arg
                requestFormData.append(String(describing: value).data(using:.utf8) ?? Data(), withName: key)
            }
            multipartFormDataBlock(requestFormData)
        }

Well, yeah. For now the goal is to be compatible with Swift 3.0 - Swift 3.2.
This error you are mentioning will get reverted in future Xcode 9 beta releases and final release - there's active discussion about this right now -<EMAIL_ADDRESS>I would recommend you to use Swift 3.2 for now, if you want to do Xcode 9 development.
That said, next release of TRON, that is planned for autumn release, will hopefully have support for Swift 3.1 - Swift 4, so that you would be able to use it with any toolchain and Swift version you need.
It's also possible that we'll make a minor release somewhere around beta 3 - beta 4, to make Xcode 8 - Xcode 9 release that is compatible with both versions without warnings. And probably somewhere around that time we'll create a swift4 branch to develop next release.
Let's leave this issue open for now, since this might be a common question for people trying to develop with Xcode 9 right now.

TRON 3.1.0 should be compatible with Xcode 8 and Xcode 9(beta 6), Swift 3.1, 3.2 and 4. Closing.


Send email to predefined email address

Overview
Support sending an email to a predefined email address.
It is based on PR #138 and PR #67, fixes issue #487.

@valioz thanks for helping us with that!
On which applications did you tested your changes? (Outlook, Gmail, etc )

I have tested it on a Gmail (Android)

This looks good to me. You can please update your base branch with the master version @valioz ?

HI @valioz , you can updated your base branch with the last changes on master? I tested this on both Android/IOS and it looks fine.

@valioz thanks! 🎉

On iOS with the default email app (mail), the TO field is not working correctly, it's not being fill at all


Signal Handler Interface

We need to create a global signal handler, that will reference an interface. Each reconciler should implement said interface so that we can handle POSIX signals globally.
If you are interested in coding we should talk, because I would want to hear your ideas! Otherwise I might just code this.

CC @geojaz because you are already in sighandler land 😄

Yes I'm interested! :)

There are a lot of examples of interfaces all over the repo if you want to follow an existing pattern I am using.. otherwise we just need a way to specify a global signal handler interface that every reconciler can implement - so that we only have to write the signal catching portion of the code once.. and tell it which implementation to use :)

LMK if you need a hand/want to jump on a call

@xmudrii you may or may not write an interface depending on how you approach the problem - close this accordingly please


click handler misses

About 25% of my clicks don't do the thing they're supposed to do.  Highlighting tracks, laying head and tail points, and everything else on the video window does nothing about a quarter of the time.
I don't know if this is a problem with this app or GeoJS's event hander.  I use an apple Magic Trackpad, so I wonder if the slight movement of my cursor during a click is causing the click events to get interpreted as drags.  Maybe the threshold for lateral movement during a click can be tuned?

Same issue utilizing a mouse for clicking.  Movement while clicking is not registering properly, which can sometimes cause unintentional missed clicks when trying to swap between tracks.

Within the annotator.js there  is a function which sets up the annotator options.
interactorOpts.click.cancelOnMove = false; if added will prevent some of the weirdness with slight movements and missing clicks.  It's a flag which causes any mouseClick to cancel itself if there is movement detected.  I kind of wish it was more of a variance for amount of movement instead of a boolean.
When this is turned off any sort of movement before the 'mouseup' is ignored.  It breaks panning unless you include a duration for the mouse click event.
 interactorOpts.click.duration = 100;
The number is going to need to be fiddled with to get a perfect setting.  That number will now be the delay between clicking/dragging for panning and the pan actually occurring.  I think somewhere between the 50-100ms range is good but I would want others to try it and confirm.

I've updated this into the new in progress Track-Centric branch, when that is merged this will be resolved.


I18n fix DO NOT MERGE

Closing in favor of https://github.com/jakala-na/next-contentful-starterkit/pull/63


Is it fully async for metrics update and metrics exposure

Hello,
I'm currently using aioprometheus but facing an issue the metrics exposure is blocking my entire FastAPI app https://github.com/claws/aioprometheus/issues/98
Do you think I won't face this issue with Pytheus?
Thank you in advance

Hi there,
For a FastAPI application with this lib you should try the rust based backend, it's documented here: https://pythe.us/rust_backend/
With that you just create a normal sync view to expose the metrics and it won't block your application
@app.get('/metrics')
def pytheus_metrics():
    return generate_metrics()

note: there is an issue in multiprocess applications where a scrape will only get data for the instance it hits, this means it might get a couple of scrapes to update some values, depending on your use case it might be a problem or not

https://github.com/Llandy3d/pytheus-backend-rs/issues/4

Closing this issue as there doesn't seem to be an actionable problem 😄
The issue with multiprocessing above has been fixed with https://github.com/Llandy3d/pytheus-backend-rs/pull/6


Project endpoint allows changing the organization through the update call

This should not be happening. A project should not be reassignable once it exists.

Belongs to #26.


[doc] Fix the documents for the config advertisedAddress

Motivation
The default value of advertisedAddress has been changed to InetAddress.getLocalHost().getCanonicalHostName() in https://github.com/apache/pulsar/pull/6235, but the documents are not updated.
Modifications
Update the documents.
Verifying this change

[ ] Make sure that the change passes the CI checks.

This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[ ] doc-not-needed
(Please explain why)

[x] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

I think that this is correct. @michaeljmarshall please confirm

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


gh-2157 Operations implement equals()

#2157
Added equals and hashcode to all operations tested by OperationTest.
Fixed test code for some special cases where new Class() would result in null exceptions for certain fields.
Ran checkstyle fixes, these have picked up extra cases in other files however/

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@5c8405b). Click here to learn what that means.
The diff coverage is 41.15%.

@@            Coverage Diff             @@
##             develop    #2161   +/-   ##
==========================================
  Coverage           ?   65.08%
  Complexity         ?     2443
==========================================
  Files              ?      901
  Lines              ?    31272
  Branches           ?     3786
==========================================
  Hits               ?    20353
  Misses             ?     9218
  Partials           ?     1701

Impacted Files
Coverage Δ
Complexity Δ

...ulostore/operation/handler/AddElementsHandler.java
81.81% <ø> (ø)
0 <0> (?)

...ation/handler/utilities/AggregateDataForGroup.java
89.36% <ø> (ø)
0 <0> (?)

...er/store/operation/handler/compare/MaxHandler.java
82.35% <ø> (ø)
0 <0> (?)

...er/store/operation/handler/compare/MinHandler.java
73.52% <ø> (ø)
0 <0> (?)

...re/operation/handler/FederatedValidateHandler.java
100% <ø> (ø)
0 <0> (?)

...k/gov/gchq/gaffer/hbasestore/utils/TableUtils.java
58.86% <ø> (ø)
0 <0> (?)

...n/java/uk/gov/gchq/gaffer/cache/impl/JcsCache.java
93.1% <ø> (ø)
11 <0> (?)

...tore/operation/handler/export/ExportToHandler.java
41.66% <ø> (ø)
0 <0> (?)

...ffer/store/operation/handler/join/JoinHandler.java
72.72% <ø> (ø)
0 <0> (?)

...erialisation/json/RoaringBitmapJsonSerialiser.java
75% <ø> (ø)
3 <0> (?)

... and 130 more

Continue to review full report at Codecov.

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


Assembla script update

Assembla have made a product update recently which have caused issues with the toggl button.
These changes fix it :)

Merged with fixes 4896d693e10db5911557cf553d8b1c68692344b7 and fdbbb3d02d9c4b72aaa0f6899fa68d2d38c10b3d
Thank you for your contribution.


Agents Event Missing Properties?

Hello,
I noticed that there is a difference in the documentation between what's here on GitHub and the SandCastle Documentation and wanted to know which version of AgentsEvent is the current documentation?
I'm trying to use the NuGet in VisualStudio which seems to match the SandCastle Doc and I wanted to be sure.
If the SandCastle Doc is the latest I'd also like to ask if the other properties in the AgentsEvent class, like Exten specifically, will be brought in or not, or what previous version had them if they were already brought in before?

I am not sure what you mean, the Exten property is in the AgentsEvent class.
So what are you having issues with?

I keep getting this Error when trying to use the Exten property of AgentsEvent:
Error CS1061 'AgentsEvent' does not contain a definition for 'Exten' and no accessible extension method 'Exten' accepting a first argument of type 'AgentsEvent' could be found (are you missing a using directive or an assembly reference?)

Are you sure you are referencing all the needed DLL files then? The code for that class is the same in both the NuGet and in the GitHub version, since it has not been changed since the last release.

I was looking for what was going on and through testing the only properties my code could see were those listed in the SandCastle Documentation for AgentEvents rather than those listed here on GitHub.

I don't know what you are trying to say with this. You already said that the documentation matches the NuGet package. And as I already said, the Exten property does exist in both versions of the code.
Code link: https://github.com/AsterNET/AsterNET/blob/c4df9d8ecb578460d6442f7cd673b9b11763fadd/Asterisk.2013/Asterisk.NET/Manager/Event/AgentsEvent.cs#L128
documentation link: https://asternet.github.io/AsterNET/html/Properties_T_AsterNET_Manager_Event_AgentsEvent.htm


feat: search archived message uses edi b2c web api

Description
Update to use Edi B2C web api for searching and loading archived messages.
Story:
https://app.zenhub.com/workspaces/mosaic-60a6105157304f00119be86e/issues/gh/energinet-datahub/opengeh-edi/219
https://app.zenhub.com/workspaces/mosaic-60a6105157304f00119be86e/issues/gh/energinet-datahub/opengeh-edi/220
References

https://github.com/Energinet-DataHub/opengeh-edi/pull/634
https://github.com/Energinet-DataHub/dh3-infrastructure/pull/688

Codecov Report
Attention: 113 lines in your changes are missing coverage. Please review.

Comparison is base (8227dfb) 10.05% compared to head (0a66b45) 16.57%.
Report is 39 commits behind head on main.

Files
Patch %
Lines

...Api/Clients/EDI/B2CWebApi/V1/EdiB2CWebAppClient.cs
0.00%
79 Missing :warning:

...taHub.WebApi/Clients/EDI/ArchivedMessagesSearch.cs
0.00%
19 Missing :warning:

...ts/MarketParticipant/V1/MarketParticipantClient.cs
0.00%
7 Missing :warning:

...Hub.WebApi/GraphQL/Types/CreateMarketPartyInput.cs
0.00%
5 Missing :warning:

...h/api-dh/source/DataHub.WebApi/GraphQL/Mutation.cs
0.00%
2 Missing :warning:

...ebApi/Clients/EDI/ArchivedMessageSearchCriteria.cs
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2274      +/-   ##
==========================================
+ Coverage   10.05%   16.57%   +6.52%
==========================================
  Files          84      102      +18
  Lines        4168     4621     +453
  Branches      778        0     -778
==========================================
+ Hits          419      766     +347
- Misses       3739     3839     +100
- Partials       10       16       +6

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


Fix serde

Motivation
Fix the bug in Block serialize and deserialize

@vicsn
In current test cases, we sample a couple of genesis blocks which's cumulative_weight is 0 to make tests on serialize and deserialize.
I don't think any adjustments are necessary, but we need to check if the types used in snarkVM are unsupported by JSON

@ghostant-1017 great find! Would it be possible to add some of the failing test cases to this PR?

@d0cd
To my knowledge, only the RPC interfaces related to /block/ have been affected by serialization.

In current test cases, we sample a couple of genesis blocks which's cumulative_weight is 0 to make tests on serialize and deserialize.

I think a clean approach to testing could be to add a function similar to sample_genesis_block(, which uses Block::from_unchecked to construct a random invalid block to test serialization/deserialization on.
If you're not interested to add the test, just let us know and I'll close this PR, adding the test in a new one.

Nice find. Why did test_serde_json below not catch any issues? Can any of the underlying test logic be adjusted so it would have failed earlier? And as a result, would we need to re-evaluate any other test_serde_json functions in snarkVM?

serde-json by default deserializes directly to an f64 if it finds an integer that can only be represented by the u128 type.
The Number enum in serde-json without the arbitraryprecision flag can hold a u64, i64, or f64. Thus without the arbitraryprecision flag it isn't capable of holding a u128 directly. The arbitraryprecision flag creates an alternative Number enum that represents higher precision with two u64s, i64s, or f64s.
If we're not using that flag we'll have to handle every u128 in a struct with code that handles it.

@vicsn I will make some changes according to @iamalwaysuncomfortable , and add the test case sir.

check-clippy finishes fine, in 34s. It is just CircleCI being its usual garbage.


safe"a"area ?

Hi the AndroidManifest.xml,
https://github.com/capacitor-community/safe-area/blob/master/example/android/app/src/main/AndroidManifest.xml
The "package" and "android:name is com.capacitorjs.community.plugins.safeAArea.
While is the strings.xml you have "safearea".
Is that normal ?

Fixed in latest version.
See this comment for more info: https://github.com/capacitor-community/safe-area/pull/2#issuecomment-2092723752


Copy https://github.com/XENONnT/straxen/pull/457

Keep a copy of https://github.com/XENONnT/straxen/pull/457 since git might have tricked me

Create a new commit for merge


Maintenance patch.

Ran the standard battery of checks and fixed up deprectaed issues, clippy warnings etc.
cargo update
cargo outdated
cargo fmt
cargo clippy

Lots of packges updated. In particular lightningcss moved from 47-55(alpha) This is a essential first step in resolving outstanding lightningcss issues.
Hightlights :-

Clippy now making use of .flatten()

Fixed 5 deprecated issues of all of the form :-
```console warning: use of deprecated macro assert_display_snapshot: use assert_snapshot!() instead --> src/compile/tests.rs:62:5 |
62 |     assert_display_snapshot!(cargo, @"cargo build --package=example --bin=example --no-default-features --features=ssr");
|     ^^^^^^^^^^^^^^^^^^^^^^^
|
= note: #[warn(deprecated)] on by default

PS Notify is 2 major number behind .. I am going to create a separate PR with Notifty only changes.

Just making notes while I figure this out....
Here are two errors related to the window build
I dont have  a window machine, so I can recreate the issue locally -
So I am going to have to think my way through the problem
error[E0432]: unresolved import `winapi::shared::winerror`
  --> C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\notify-4.0.17\src\windows.rs:11:21
   |
11 | use winapi::shared::winerror::ERROR_OPERATION_ABORTED;
   |                     ^^^^^^^^ could not find `winerror` in `shared`

   Compiling reqwest v0.12.4
error[E0308]: mismatched types
   --> C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\notify-4.0.17\src\windows.rs:276:29
    |
276 |         overlapped.hEvent = request_p;
    |         -----------------   ^^^^^^^^^ expected `winapi::ctypes::c_void`, found `libc::c_void`
    |         |
    |         expected due to the type of this binding
    |
    = note: `libc::c_void` and `winapi::ctypes::c_void` have similar names, but are actually distinct types
note: `libc::c_void` is defined in crate `core`
   --> /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04\library\core\src\ffi\mod.rs:173:1
note: `winapi::ctypes::c_void` is defined in crate `winapi`
   --> C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\winapi-0.3.9\src\lib.rs:38:5
    |
38  |     pub enum c_void {}
    |     ^^^^^^^^^^^^^^^

Reverse engineering the break
Change to "brotli" triggers changes to "flexilogger"
Changes to "flexilogger" triggers changes to "chrono"
Change to "chrono" triggers changes to "windows_targets"
So I think reverting to the change to brotli would fix the issue
But I want somthing cleaner.

The last commit is experimental .. more work is required.

I’m on Windows 10 and I can confirm the winapi build issue. Installing martinfrances107@98ca5bed works, but it looks like watching files isn’t functional, or at least isn’t functioning correctly, because I see a lot of these events without any sort of rebuilding:
       Event { kind: Modify(Any), paths: ["C:\\Media\\src\\my\\hledger-web-rs\\src\\app.rs"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }

Updated version of notify is a major change.
In this new regime "Rename" events can supply a variable number of files.
Now notify is cross platform and has lots of new fine grained events.
I am not sure I have preserved the intent of the original.. I am still looking at this.

Just chiming in once more to say that cargo leptos watch still isn’t responding to file changes for me with martinfrances107@558bef52. My apologies if this is out of scope; I only started using Leptos with this branch, so I don’t know whether it’s changed behaviour or not.

I will have another look, this issue started as a maintence patch.
I tried to do the changes associated with the notfiy crate in an isolated PR as it was a project in itself.
I am a big fan of keeping PRs small and isolated to one issue... BUT... here the slowly increasing complexity is justified.
regarding the changes in notify.rs try_new() -- it lacks associated tests.
So NEXT .. I am going to add the smallest test to trigger on change of file contents.

The next PR is a outline of the test
// Overivew :-
//
// SETUP: create a file in a valid project.
//
// 1) Construct watching mechanism.
//
// 2) Modfify the file.
//
// 3) Assert the mechanism observed a valid event.
//
// TEARDOWN: delete the file.
#[ignore]
#[test]
fn change_file_contents() {
  /// ....
}

I am currently "#[ignore]ing" the new test - its not passing, I am in the middle of debugging it.
But I see enough detail to cause an architectural discussion in the background.
from the commit log -
"A structural issue, if no event is generated
then the test hangs."
I am going the have to insert a timeout mechansim that says
after N ms -- The event is declared overdue and a fail issued.
Making test dependant on a minimim execution time is borderline
bad practise ... We are making assumption about the resouces
given to the testing infrasture..
But in this case I think an exception has to be made?

The new test passes on Linux,
The new test can be viewed a framework for drilling down and identifying the Events that windows is issuing and I am not seeing on my OS.
My current thought is there are lots of fine grained Events like ModifyKind::Other
which windows is issuing and we are not handling correctly

Nuts, I thought I had covered all the corner cases...
At the moment I can't see a way forward...
More on the weekend.

The expected debug is missing from build artefacts - implying no events are emitted.
This warning/filename conflict is interesting -- could the file creation / modification be silently failing !!!
warning: output filename collision.
The bin target `project2` in package `project2 v0.1.0 (D:\a\cargo-leptos\cargo-leptos\examples\workspace\project2)` has the same output filename as the lib target `project2` in package `project2 v0.1.0 (D:\a\cargo-leptos\cargo-leptos\examples\workspace\project2)`.
Colliding filename is: D:\a\cargo-leptos\cargo-leptos\examples\workspace\target\debug\deps\project2.pdb
The targets should have unique names.
Consider changing their names to be unique or compiling them separately.
This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
```

I am about to publish a new commit.
The only clue in the test artefacts is a "project conflict" [ project2 ] which I was reusing for the new test.
So my response is to hive off a new cargo project, named "notify" and use that soley for the test [ change_file_contents()].
In terms of review .. I think that this is going to have to be refactored .. but I want something that passes.

So after that isolation refactor .. those conflict warnings persist,  and so they are not related to the new test..
The debug message I added shows "events" are being generated...
So it looks to me, the root problem is a "window" specific misconfiguration
Hmm, I am not sure what to try next.

@gbj The published version works perfectly with --locked, which I hadn’t tried before. It detects changes as it should. Without --locked, I get the winapi error above.

Checked cargo outdated again ... fixed a couple of issues.

From my comments above

I am going the have to insert a timeout mechansim that says
after N ms -- The event is declared overdue and a fail issued.
Making test dependant on a minimim execution time is borderline
bad practise ... We are making assumption about the resouces
given to the testing infrasture..

I have now set the watchdog timeout to 4s .. this well above what I think is reasonable.

Hmm, that maybe a intresting data point
Now the new test fails in "macros-latest"  ... that is  when I updat  the dependencies within the examples directory.  I wonder if I can use this is identify the sub-module that is causing the failure on windows but not on linux....Hope fully it will be a small list.

Do you think this is ready for merge?

Do you think this is ready for merge?

No,  the only remaining issues is why does the new test "change_file_contents()" pass on ubuntu but timesout of Windows.
PS thanks for all the micro merges recently .. The PR here is smaller. I need more time to reason this out..

#295 has just demonstrated that bumping for zip isolation is problematic for Windows targets only.
The next step here is to back out changes to the zip crate  so they can be dealt with in isolation
.. on sec

Hi shivjm,
I have put some debug into latest commit "[Adding debug so I can track down specific event.]"
Can I ask you to download it and copy and paste the event debug here so I can see what is going wrong.
Thanks M

ModifyKind::Name(RenameMode::Any)
| ModifyKind::Name(RenameMode::Other) => {}
regarding the second path maybe it does not exist
and convert(&event.paths[1], proj)? is returning a error unexpectedly.

Here you go, @martinfrances107:
2024-06-26T10:23:18.524263Z  INFO hledger_web_rs: listening on http://<IP_ADDRESS>:3000
try_new() event.kind Modify(
    Any,
)

To produce this output, I started my application with cargo leptos watch and ran touch src/app.rs once it was running (as signalled by the first line of the logs). Is there anything specific I should try?

@shivjm thank you

I am still working on this as and when I get a new idea.
Sorry if it coming out in slowly and with so much experimentation
Here is the current state of things.
based on shivjm reporting .. on his setup windows issues an event which we consume correclty ... It the windows tests only, which are broken.For some reason  no event is generated.
So that has me looking the notify crates doc for windows specific config that I may be missing
this new test is the first tokio test ( see  #[tokio::test] )
Maybe instead of windows specific it is tokio specific?
one sec will submit a new commit based on
https://docs.rs/notify/6.1.1/notify/#crossbeam-channel--tokio


argocd: upgrade and add fish completions

argocd: upgrade to 2.13.2
argocd: add fish completions

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I'm hoping it's okay to have tested without sandbox=true because the CI is happy and I'm not really writing any new code


Add make-pbs.py script

Codecov Report

Merging #889 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #889   +/-   ##
=======================================
  Coverage   89.17%   89.17%
=======================================
  Files         105      105
  Lines       11966    11966
  Branches     2377     2377
=======================================
  Hits        10671    10671
  Misses        997      997
  Partials      298      298

Continue to review full report at Codecov.

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

merged.


Logging - ensure consistent application logging output

This is a follow-on to #240
Review and update Logback configuration (in logback.xml files) across all PASS Java projects to ensure log output has a standard and consistent format. Also ensure that logging is consistently set to INFO level for all projects, in both logback config and in docker config.

closing in lieu of #460


Regarding QKV in vision transformer

Tutorial: -15
Hi
In this tutorial tutorial 15 for vision transformer in pytorch
I observed query, key and value being same in the attention block.
x = x + self.attn(inp_x, inp_x, inp_x)[0]
In tutorial 6 ,  the query, key and value are recieved from a projection.
qkv = self.qkv_proj(x)
In another vision transformer implementation https://towardsdatascience.com/implementing-visualttransformer-in-pytorch-184f9f16f632 the queries, values and keys are received from a projection.
I tried to find the source code of pytorch function multiheadattention. It seems like projection for query value and key is  not applied in definition as input tensor is same for query, key and value.
I wanted to know if I should manually project the input embedding to query, key and value them before forward passing to attention.
Thanks

Hi, the MultiHead Attention layer in PyTorch integrates this projection directly in the same layer. You can find the code here: https://pytorch.org/docs/stable/_modules/torch/nn/modules/activation.html#MultiheadAttention
If the input tensor is of the same size for query, value and keys, this layer defines one weight to project the input to query, key and value:
self.in_proj_weight = Parameter(torch.empty((3 * embed_dim, embed_dim), **factory_kwargs))
This is the same strategy as used in Tutorial 6 and is usually more efficient for common embed_dim values. Therefore, you don't need to manually project the input in this layer.

Sounds good, thank you.


Add -Xdump NPE option to jdk_lang_j9 for debug

Help diagnose https://github.com/eclipse/openj9/issues/8972
Signed-off-by: Peter Shipton<EMAIL_ADDRESS>

@smlambert or @llxia can you review pls.
Tested via https://ci.eclipse.org/openj9/view/Test/job/Grinder/1084


Configuration is lost, and I cannot re-add it.

The integration lost track of my gem controller. I can still log into the GEM interface and see all the data, but the integration is saying that everything is unavailable. The device serial number is not in the configure per-monitor options list is empty.
I've tried reloading the integration, but it had no effect. I now have one hub that has nothing in it and cannot be edited.
Looking at the diagnostic, the entities seem to have been deleted but still exist in the "deleted_entities" category. I've tried removing the integration, and starting over, but I've had no luck. I even re-entered the old style gem configuration in homes that this integration would find it and reload the data. No luck.

Drag and drop your downloaded diagnostics file here:
Debug Logs
config_entry-greeneye_monitor-62aea2d9cfb20eae29060abac08e45c1.json.txt

Drag and drop your downloaded log file here:
home-assistant_greeneye_monitor_2023-09-04T17-48-40.984Z.log

The diagnostics show that no monitors have connected to your Home Assistant instance. I would suggest double-checking your GEM's configuration to make sure it's still sending packets to the right place (did the IP address of your Home Assistant change, maybe?). Make sure you click "Exit Setup Mode" and see the message saying it exited successfully or else it won't resume sending packets.

Oddly enough, after several reboots of home assistant, the values came back.

Discovered the source of the issue. When Home Assistant boots, the GEM integration is unavailable. I have to go into the GEM web interface on the device, go into setup mode, view a page, leave setup mode, then close the window I used to view the GEM web interface. At that point, the GEM devices and sensors in Home Assistant move from unavailable to reporting data.

Usually for me the packets start flowing within a few seconds after startup, but I've definitely seen the GEM take a few minutes to get reconnected before. Doing what you describe gives it a nudge, but ideally you shouldn't have to do it every time you restart. If your GEM is not on the latest COM and ENG firmware versions, you might try upgrading those in case that helps.

The odd thing is, this just started happening about two days ago. I've been
successfully using the GEM for over a year now.
On Mon, Sep 4, 2023 at 6:49 PM Jonathan Keljo @.***>
wrote:

Usually for me the packets start flowing within a few seconds after
startup, but I've definitely seen the GEM take a few minutes to get
reconnected before. Doing what you describe gives it a nudge, but ideally
you shouldn't have to do it every time you restart. If your GEM is not on
the latest COM and ENG firmware versions, you might try upgrading those in
case that helps.
—
Reply to this email directly, view it on GitHub
https://github.com/jkeljo/hacs-greeneye-monitor/issues/33#issuecomment-1705802972,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG4XJQTJ7EYEVDD2AF2MRDXYZZKTANCNFSM6AAAAAA4KW3HDI
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


ARROW-11806: [Rust][DataFusion] Optimize join / inner join creation of indices

This PR implements two optimizations

Change the way we create an array of indices for an inner join to avoid generating a null bit map. It seems currently not really ergonomic to do this with Arrow without resorting to an iterator (which would be hard to do here). This is around 3% difference
Allow to reuse allocations in create_hashes when possible. This is around 2% faster.

In total this gives a small (5%) speedup to query 5:
This PR:
Query 5 iteration 0 took 169.3 ms
Query 5 iteration 1 took 156.0 ms
Query 5 iteration 2 took 157.5 ms
Query 5 iteration 3 took 158.0 ms
Query 5 iteration 4 took 157.3 ms
Query 5 iteration 5 took 163.4 ms
Query 5 iteration 6 took 167.6 ms
Query 5 iteration 7 took 171.5 ms
Query 5 iteration 8 took 167.4 ms
Query 5 iteration 9 took 164.5 ms
Query 5 avg time: 163.26 ms

Master:
Query 5 iteration 0 took 177.6 ms
Query 5 iteration 1 took 169.6 ms
Query 5 iteration 2 took 171.8 ms
Query 5 iteration 3 took 175.1 ms
Query 5 iteration 4 took 167.2 ms
Query 5 iteration 5 took 171.1 ms
Query 5 iteration 6 took 174.2 ms
Query 5 iteration 7 took 178.1 ms
Query 5 iteration 8 took 167.9 ms
Query 5 iteration 9 took 172.0 ms
Query 5 avg time: 172.46 ms

The integration test failure in https://github.com/apache/arrow/pull/9595/checks?check_run_id=1998235390 seems to be the same as was fixed in https://github.com/apache/arrow/pull/9593
I also pulled this branch locally, and re-ran the tests and everythings looks good to me

Thanks @alamb resolved the incosistent naming.

Codecov Report

Merging #9595 (2869040) into master (0f64726) will increase coverage by 0.04%.
The diff coverage is 78.72%.

@@            Coverage Diff             @@
##           master    #9595      +/-   ##
==========================================
+ Coverage   82.33%   82.38%   +0.04%
==========================================
  Files         245      245
  Lines       56407    57134     +727
==========================================
+ Hits        46443    47068     +625
- Misses       9964    10066     +102

Impacted Files
Coverage Δ

rust/datafusion/src/physical_plan/hash_join.rs
84.16% <77.77%> (+0.64%)
:arrow_up:

rust/datafusion/src/physical_plan/repartition.rs
81.21% <100.00%> (-0.14%)
:arrow_down:

...datafusion/src/physical_plan/string_expressions.rs
73.38% <0.00%> (-3.62%)
:arrow_down:

rust/arrow/src/array/equal/utils.rs
75.49% <0.00%> (-0.99%)
:arrow_down:

rust/arrow/src/datatypes/field.rs
55.47% <0.00%> (-0.66%)
:arrow_down:

rust/datafusion/src/physical_plan/parquet.rs
87.83% <0.00%> (-0.22%)
:arrow_down:

rust/benchmarks/src/bin/tpch.rs
38.33% <0.00%> (ø)

...datafusion/src/physical_plan/crypto_expressions.rs
52.45% <0.00%> (ø)

...integration-testing/src/flight_server_scenarios.rs
0.00% <0.00%> (ø)

...-testing/src/flight_server_scenarios/middleware.rs
0.00% <0.00%> (ø)

... and 10 more

Continue to review full report at Codecov.

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

@Dandandan  on no! It now seems to have failed rust fmt linting

@alamb ha, thanks, fixed!


Does not work when used in virtual directory

When running in IIS or IIS Express, specifying an application root directory as anything other than "/", authentication always fails.  Kestrel behind IIS is smart enough to know what the application base url is, and can separate it into Request.PathBase and Request.Path.  Also, these properties are of type PathString, which override Equals and op_Equals, to provide case insensitive comparisons.  And, the definition of HandleRequestAsync in RemoveAuthenticationHandler compares Request.Path with Options.CallbackPath.
The first problem is that HandleRemoteAuthenticateAsync compares the CallbackPath with the concatenation of Request.PathBase and Request.Path.  The problem here is that now my application is not deployment portable.  If I develop with http://localhost:5000/, but deploy to https://domain/app/, then, during development, CallbackPath will be compared with /signin-wsfed, while in production it will be compared with /app/signin-wsfed.  Rather, if only Request.Path is used, then it would be compared with /signin-wsfed in both cases.
The second problem is that RemoteAuthenticationHandler is already doing exactly this.  Thus, in the production case of having the application hosted in https://domain/app/, when I use a CallbackPath of /signin-wsfed, HandleRequestAsync compares /signin-wsfed with /signin-wsfed, which succeeds, and continues the code down HandleRemoteAuthenticateAsync, which then compares /signin-wsfed with /app/signin-wsfed, which fails, causing authentication to be skipped.  If I alter CallbackPath to instead be /app/signin-wsfed, HandleRequestAsync compares /app/signin-wsfed with /signin-wsfed, which fails, and the entire process is skipped.
I believe the correct solution here is to not compare CallbackPath with Request.Path at all in HandleRemoteAuthenticateAsync, because, if that method is being called, then the work has already been done to determine whether or not to skip handling authentication based on the current path.  Also, in a future release of Microsoft.AspNetCore.Authentication, it appears that a method called ShouldHandleRequestAsync will be added, allowing a derived class to choose itself how authentication requests should be filtered.

If you would like to submit a pull request, that would be great. I designed
this middle ware after the open id one which is where that comparison came
from I believe.
On Thu, Jun 22, 2017 at 1:47 PM TheJayMann<EMAIL_ADDRESS>wrote:

When running in IIS or IIS Express, specifying an application root
directory as anything other than "/", authentication always fails. Kestrel
behind IIS is smart enough to know what the application base url is, and
can separate it into Request.PathBase and Request.Path. Also, these
properties are of type PathString, which override Equals and op_Equals, to
provide case insensitive comparisons. And, the definition of
HandleRequestAsync in RemoveAuthenticationHandler compares Request.Path
with Options.CallbackPath.
The first problem is that HandleRemoteAuthenticateAsync compares the
CallbackPath with the concatenation of Request.PathBase and Request.Path.
The problem here is that now my application is not deployment portable. If
I develop with http://localhost:5000/, but deploy to https://domain/app/,
then, during development, CallbackPath will be compared with /signin-wsfed,
while in production it will be compared with /app/signin-wsfed. Rather, if
only Request.Path is used, then it would be compared with /signin-wsfed in
both cases.
The second problem is that RemoteAuthenticationHandler is already doing
exactly this. Thus, in the production case of having the application hosted
in https://domain/app/, when I use a CallbackPath of /signin-wsfed,
HandleRequestAsync compares /signin-wsfed with /signin-wsfed, which
succeeds, and continues the code down HandleRemoteAuthenticateAsync, which
then compares /signin-wsfed with /app/signin-wsfed, which fails, causing
authentication to be skipped. If I alter CallbackPath to instead be
/app/signin-wsfed, HandleRequestAsync compares /app/signin-wsfed with
/signin-wsfed, which fails, and the entire process is skipped.
I believe the correct solution here is to not compare CallbackPath with
Request.Path at all in HandleRemoteAuthenticateAsync, because, if that
method is being called, then the work has already been done to determine
whether or not to skip handling authentication based on the current path.
Also, in a future release of Microsoft.AspNetCore.Authentication, it
appears that a method called ShouldHandleRequestAsync will be added,
allowing a derived class to choose itself how authentication requests
should be filtered.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/chrisdrobison/aspnetcore-wsfed/issues/10, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABu24cqs7rwoG1SLEC-UutUWAV7_xegEks5sGsS8gaJpZM4OCwsg
.

I won't be able to get to it now, but I have done the work already, so it shouldn't take much to fork and apply the changes when I can get around to it.


APT whitelist request for Xvfb

There is xvfb on the list, but it's lowercase. So I'm not sure if it's a bug?
Check my build log.

Closing as per #4954


Typo in docs site

https://docs.acorn.io/authoring/containers#startup-probes
"type: "startup"
There should not be a quotation before type.

for a documentation change, no need to open an issue. can just open a pr to fix...unless you opened this issue because you couldnt fix right away and didnt want to lose track, in which case, opening an issue is fine


[WIP]: adding TESS light curve classes

This PR does the following:

Codecov Report

Merging #25 into master will decrease coverage by 0.41%.
The diff coverage is 64.86%.

@@            Coverage Diff             @@
##           master      #25      +/-   ##
==========================================
- Coverage   90.01%   89.59%   -0.42%
==========================================
  Files          14       14
  Lines        1322     1298      -24
==========================================
- Hits         1190     1163      -27
- Misses        132      135       +3

Impacted Files
Coverage Δ

lightkurve/tests/test_lightcurve.py
98.01% <ø> (-0.08%)
:arrow_down:

lightkurve/targetpixelfile.py
81.41% <100%> (+0.11%)
:arrow_up:

lightkurve/utils.py
89.18% <100%> (+0.3%)
:arrow_up:

lightkurve/lightcurve.py
84.52% <62.85%> (-1.23%)
:arrow_down:

Continue to review full report at Codecov.

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


goredo: 1.31.0 -> 2.0.0

Description of changes
Major changes

Improve speed of dependency calculation by orders of magnitude
New format of dependency records from GNU recfile (text) to binary
When called in a .do file, redo-if* commands treat all arguments as targets.

Changelog

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Updated to 2.1.0

Updated to 2.2.0

Update to 2.3.0

Updated to 2.4.0.

Hi, will gladly help with review.
I would also suggest posting the PR to https://discourse.nixos.org/t/prs-ready-for-review/3032/ and to https://app.element.io/#/room/#dev:nixos.org

Result of nixpkgs-review pr 259824 run on x86_64-linux 1

2 packages built:

goredo
goredo.info

Removing backport due to 2 reasons:

Major updates shouldn't be backported
23.05 is about to reach EOL and 23.11 has just been cut.


process queue cannot handle a large number of events in Google Chrome

tl;dr - Chrome doesn't handle Array#shift in an efficient manner for large arrays. Causing workerQueue to not handle lots of events in a quick manner.
Our application uses EventSource to stream output from an external process. The EventSource is modeled as a subscription, with each event triggering a new message.
On some streams, we can received hundreds of thousands of events, which creates a new process for each event on the elm process queue. On Google Chrome, the process queue does not get processed in a timely manner. On Firefox, however, it is near instantaneous. We were able to find with the Performance developer tool in Chrome that a lot of time is spent in work.
We've been able to find that Array.shift in Javascript is inefficient in Google Chrome for large arrays. This causes workQueue to choke on a large amount of processes.
With @zwilias help there is a SSCCE example. It doesn't use EventSource, but does demostrate the slow processing of a large number of processes. Try it in Chrome and then FF. Such wow, amaze!

For reference, a fairly simple fifo queue implementation that only has enqueue and dequeue operations like this one make performance on chrome manageable. (It basically cheats by acting as if dequeued elements are no longer in the array, periodically slicing the start off in a batch.)


face-detection-retail-0004 fails to forward() with dldt 2018_R5

If I am trying to use it with 2018_R5:
net = cv2.dnn.readNet('face-detection-retail-0004.xml', 'face-detection-retail-0004.bin')
face = (np.random.rand(480, 320, 3) * 255).astype(np.uint8)
blob = cv2.dnn.blobFromImage(img, 1, (300, 300))
net.setInput(blob)
net.forward()

>>opencv/modules/dnn/src/op_inf_engine.cpp:555: error: (-215:Assertion failed)
Failed to initialize Inference Engine backend:
Incorrect number of input edges for layer mbox_conf_reshape in function 'initPlugin'

With 2019_R1 all is good. I think that few month ago it was working on 2018_R5.

IRs produced by different versions of Model Optimizer are, generally, incompatible. So, you should use the model optimizer from the same release as the library. For the history of generated IRs for intel models, you can refer to https://download.01.org/openvinotoolkit/


CLI: Create a cmd/common package for methods used across the CLI

For example, the printWorkflow method is used in different parts of the CLI. cmd/argo/get.go and cmd/argo/archive/get.go.
Currently, the method is duplicated in the two files, which is undesirable. Furthermore, importing the method from the commands package would create a circular dependency.
We should extract these functions under a common package so that they can be imported across the CLI.

For example, the printWorkflow method is used in different parts of the CLI. cmd/argo/get.go and cmd/argo/archive/get.go

This was completed as part of https://github.com/argoproj/argo-workflows/pull/8166#discussion_r829542134


Messages shows from bottom to top and limit the size of collection view? Advice appreciated

In my project, I am trying to put a view under the JSQMessagesCollectionView and set the background color of JSQMessagesCollectionView to be clear color.

I want to limit maximum height of the collectionView to certain number, for example 120pt because I don't want the collectionView taking all the spaces. Currently I am achieving this by set the topContentAdditionalInset = self.view.frame.height - collectionViewContentSize self.keyboardController.currentKeyboardFrame.height. collectionViewContentSize needs to be calculated based on the number of message and height of each message cell. Any advice for better approach for setting the height of collectionView or calculating the collectionViewContentSize?

Also instead of showing message from top to bottom, I want to show the messages from bottom to top. Old message still is above new message, but the first message shows right above the keyboard. By solving problem 1, problem 2 should not be a problem. But I am wondering if there is better solution for this.

Also, while solving problem 1, I found I need to override some methods defined in JSQMessagesViewController.m but I was unable to unless I move the definition to the .h file. For example, I want to override the JSQMessagesKeyboardControllerDelegate implementation and being able to reuse existing implementation by calling super. related methods. I don't want modify the source code if I can avoid it. Are there other ways to extend the functionality without modify existing source code of JSQMessagesViewController?
Any help is appreciated.

Hey @zwang :smile:
I'm cleaning up old issues and trying to finish the next release of the library. I'm sorry I don't have time to respond to all questions.
I'm going to close this issue, but the community should feel free to continue the discussion.
Other ways to get help:

Ask on StackOverflow with the jsqmessagesviewcontroller tag
See the FAQ
Search previous questions


GeoMakie doesn't work with Theme

Hi,
It seems GeoMakie doesn't really work with Theme.  A bunch of properties that I can set with Theme using a regular axis--figure resolution, background color, axis limits, etc--no longer work if use a GeoAxis. Am I missing something?  Thanks!
Jonathan

You would have to theme GeoAxis explicitly unfortunately - I will look into how GeoAxis could inherit from the axis theme though!


Show httpWorker in host.json as warning

httpWorker in host.json is defined as a property for custom handler feature (still in preview) in following doc.
https://docs.microsoft.com/en-us/azure/azure-functions/functions-custom-handlers#configuration
Otherwise vscode shows warning when the property is in host.json as following.

Is this caused by that httpWorker definition isn't in https://json.schemastore.org/host ?

httpWorker will be deprecated soon and obsolete before custom handlers is GA. We'll be changing it to a customHandler section. We'll update schemastore after the change is complete.

Thanks @anthonychu !
I look forward to the update

Closing since this repo doesn't own the schema for host.json and sounds like Anthony is already on it


[FEAT] Blank section on the Home page

Image:

Suggestion:
The blank section on the home page does'nt look good. We can add Trending books (Most used from the website) in that section.

I want to work on this issue please assign it to me

I can work on this issue.

it's used for serach results. submit issues to https://github.com/EbookFoundation/free-programming-books-search/


Compress freezes with nested objects

Expected Behavior
Compresses query string
Current Behavior
freezes browser
Steps to Reproduce (for bugs)

Put this query string

mutation{
  updateProducts(payloads: [{
    creative_id: "3333",
    product_type_slug: "print",
    scores: {
      sales_hotness_product: {

      }
    }
  }]){
    error
    error_count
  }
}

Click "Compress"

Thanks for reporting! I'll look into this issue.


Transition doesn't work when immediate child is a component

The clone method only applies Feature modifications on the first render. A temporary solution is to make the immediate child a div and embed children inside that. I'll try that for now.

Closed by fb39c8b


[plock-10]: Attempted fix for dropped chars

(quick fix at lunch...)
@kengoodridge @pentamassiv
I managed to get it working with this approach. Note the 19 character chunks... Did not work with 20. 🤯
Also the newline fix... @kengoodridge, also seemed necessary - I added a space before every newline, which fixed it for me, but checking if a text chunk started with one was not enough.
We'll figure out the right way to get you credit @kengoodridge - maybe I'll open my PR as a modification of yours...
@pentamassiv - does this fix make any kind of sense to you?
I tried sleeps as you suggested to no avail, I also noticed the 2ms sleep was outside of the chunked loop, which seemed wrong as a HID signal was being sent, potentially with no delay.

FWIW the easiest way to reproduce this issue is to cat a large text file and use diff command.

Sorry, I was going to comment on this yesterday, but it was already late at night so I decided to reply today after some sleep. Now it is late at night again :P
If I understand your changes correctly, you needed to reduce the length of the chunks to 19, because you replace each \n with space+\n, so they can get longer after making the chunks. This can potentially push a new line character to the start of a new chunk in the text function. The workaround should work in most cases, but would fail for strings where there are multiple newlines, (e.g "123456789012\n\n\n\nerr").
The beginning and end of chunks are marked with a | char
input:<PHONE_NUMBER>12\n\n\n\nerr
plock A:  |123456789012\n\n\n\nerr|
plock B:  |123456789012 \n \n \n \nerr|
enigo:    |123456789012 \n \n \n |\nerr|  <-- new chunk starts with a newline

I think you could improve the workaround by using
replacen("\n", " \n", 1) to only replace the first occurrence of a newline. Then the chunks(19) should always work reliably.
The proper fix has to be in enigo, but I don't have a suspicion where to look right now. I am also traveling and sick, so it might take some time before I look into it :/

@pentamassiv totally true. Great catch.

I noticed that you removed the hack to type strings starting with a newline. However you are still splitting the strings in chunks of 19 characters. This should not be necessary. Enigo does that internally for you.

@pentamassiv i was going to remove it, but it provides a way to cancel the operation. I haven't spent the time to come up with a better way yet 😅 - is there a concept of an interrupt signal in enigo?

Interesting, why do you need that? I guess it is because you sometimes want to type a lot of text and it might take too long due to enigo using sleep on macOS?
I'd like to get rid of the sleep and then it should be instantaneous just like on Windows so in the future there should be no need for an interrupt.

Enigo will release all held keys when you terminate the program, but that's it. Since you only enter text it does not seem relevant to your use-case though. Chunking the text is the only option there is to stop it mid way.


Hadoop Cluster

Closes #44
Checklist:

[x] Added activities for learners
[x] Didn't give the solutions to the added activities straight away
[x] Followed a LearnByDoing approach
[x] Clean and well documented code (if source code files are involved)
[x] Added images for better understanding if deemed necessary

@all-contributors kindly add @Nitesh-thapliyal for:

[x] code
[x] content
[x] ideas
[x] doc

@Nitesh-thapliyal Kindly showcase your new MicroByte on our slack workspace using this template. Also if you've got ideas that'll further improve this MicroByte, you are free to open up some issues on which you or the community can contribute.


mariadb service does not start with trident volume while dockerhost have public IP

Describe the bug
mariadb container does not  start mariabdb service while dockerhost have a public ip, everything else looks good. The volume is visible the volume is mapped into the container to /var/lib/mysql. Data is accessible. Rights are correct. Volume is read write.
the container is running only the mariadb service doenst come up. Changing the dokerhost IP back to internal ip
the mariadb service starts without any issues.
thats the only log entry:
docker logs guacamole-mariadb-1
2024-10-04 16:30:58+02:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.5.2+maria~ubu2404 started.

Environment
we ar not using kubernetes only docker, docker-compose with trident plugin

Trident version:  latest from this month

Trident installation flags used: [e

Container runtime: 20.10.24+dfsg1, build 297e128

docker-compose version: version 1.29.2, build unknown

OS: Debian12

NetApp backend types: Netapp AFF A400

Other:

To Reproduce
changing dockerhost to public ip
trident config
{
"version": 1,
"storageDriverName": "ontap-nas-economy",
"storagePrefix": "trident_eco_prod_labs_",
"managementLIF": "<IP_ADDRESS>",
"dataLIF": "<IP_ADDRESS>",
"svm": "corp_trident",
"username": "USER",
"password": "PASSWORD",
"aggregate": "n01_aggr1",
"limitVolumeSize": "300g",
"log-level": "debug",
"debug": true
}
docker-compose.yml
---
services:
  guacd:
    image: guacamole/guacd
    networks:
      - local

  guac-serve:
    image: guacamole/guacamole
    links:
      - guacd:guacd
      - mariadb:mysql
    ports:
      - 8080:8080
    environment:
      - MYSQL_LOG_CONSOLE=true
      - MYSQL_HOSTNAME=mariadb
      - MYSQL_DATABASE=guacamole
      - MYSQL_USER=guacamole
      - MYSQL_PASSWORD=PASSWORD
      - GUACD_HOSTNAME=guacd
      - GUACD_PORT=4822
    networks:
      - local

  mariadb:
    image: mariadb:11.5
    environment:
      - TZ=Europe/Berlin
      - MYSQL_ROOT_PASSWORD=PASSWORD
      - MYSQL_DATABASE=guacamole
      - MYSQL_USER=guacamole
      - MYSQL_PASSWORD=PASWORD
    volumes:
      - debian12_guacamole:/var/lib/mysql
    networks:
      - local

volumes:
  debian12_guacamole:
    driver: trident_eco:latest  # Ensure this matches your plugin name
#    driver_opts:
#      size: "30G"

networks:

  local:
    driver: bridge

hi wonderland thank you for your answer. The problem ist that this issue does not make sense at all. thats why I try to figure out whats going on. The only thing is that creating the stack directly with Dockerhost having its  Internet IP the unix permissions are wrong.
bash-5.1# ls -ld /var/lib/mysql
drwxrwxrwt 2 mysql mysql 4096 Sep 20 13:39 /var/lib/mysql
thats why I also search in direction to trident


Replace PostLocalSGDOptimizer with a dedicated model averaging component

What does this PR do?
This is an improvement of https://github.com/PyTorchLightning/pytorch-lightning/pull/8967.
Replace PostLocalSGDOptimizer by a dedicated model averaging component that can run after optimizer_step in lightning.py.
The previous implementation can cause data races and fail the training for some cases. For example, if the data loading phase also involves allreduce (e.g., for checking if the input data stream has reached the end), and such allreduce can be kicked off during optimizer.step(). Therefore, the implementation in this PR can fix such issue.
Proposal: https://github.com/pytorch/pytorch/issues/59699
There are two options to enable post-local SGD by using vanilla PyTorch:

Post-LocalSGD Comm Hook + Periodic Model Averager
https://github.com/pytorch/pytorch/blob/master/torch/distributed/algorithms/model_averaging/averagers.py#L48-L78

This option requires 1-line addition (such as averager.average_parameters(model.parameters())) in the training loop.

Post-LocalSGD Comm Hook + Post-LocalSGD Optimizer
https://github.com/pytorch/pytorch/blob/master/torch/distributed/optim/post_localSGD_optimizer.py#L15-L48

This option does not need any code change in the training loop. I tried this option earlier. However, one limitation is that if there is another phase such as data loading that also runs some communication like allreduce and overlaps with optimizer_step(), then this can cause potential data race and fail the training. Since such concurrent phase like data loading is out of the control of model averaging, I didn't choose this implementation.
Does your PR introduce any breaking changes? If yes, please list them.
None.
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

It's ready to review.

Close this obsolete PR to favor the replacement https://github.com/PyTorchLightning/pytorch-lightning/pull/12378 from @daniellepintz


feat: Exclude extensions with remote_directory

Description
This enhancement gives the ability to include an array of file
extensions that should not be purged. Extremely useful if shipping a
python module via chef since .pyc files will be created. However, as
files get changed, renamed, moved, etc. the directory will become dirty
without the purge option.
exclude_extensions is optional and takes an array:
['.tmp', '.pyc']

I am still trying to figure out how/where to add this as a test.
Issues Resolved
n/a
Check List

[ ] New functionality includes tests
[ ] All tests pass
[ ] RELEASE_NOTES.md, has been updated if required (not required for bugfixes, required for API changes)
[x] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

Use the existing Chefignore file system instead?

Also for this specific instance you can use export  PYTHONDONTWRITEBYTECODE=1 or python -B. This behavior is also much improved in Python 3.

This is hugely beneficial to managing macOS.

@coderanger macOS ships with Python 2 and this assumes that the python code can be modified or even ran in another context.

If we were going to do this it should probably be an array of either globs or regexps rather than being hardwired to extensions. But I'm 👎 as an over-use of cookbook file distribution. If you want to ship python code in a cookbook, include the wheel and pip install it before use.

@coderanger pip install is not a valid use case here and is ultimately an even poorer tool with other issues, which only adds complexity.
People who manage macOS and use chef commonly distribute python libraries/other python tools that can create pyc files - a very common use case is PyObc files. These python tool might be sub tools inside a larger tool that invokes these files (thereby creating the pyc files).
The remote_directory is a perfect use case for installing these files, but ultimately causes chef-runs to update resources that aren't needed.

@coderanger I think there is som confusion. They are not talking about python modules, they are talking a few python scripts. let's say a dir called 'mac_tools' with a handful of py files, deployed with remote_dir. With purge set it will manage the state of that dir. but each run if the scripts were ran, it must clean up the '.pyc' each run. Does that help?
But also I could think of plenty of situations where you would want to manage an entire directory, but exclude one file type, or like you mention, a glob.

remote_directory is not intended to replace proper file deployment systems like git, or tarballs, or Mac pkg installers. As such we try to keep cookbook_file and remote_directory very simple. My personal opinion is this crosses the line of what we are targeting, but will have to see if other maintainers disagree :)

@coderanger fair, but package based installers have no idea if the files have changed (either by accident or nefariously). Same for tarballs and unless someone wrote a deletion/git clone script it wouldn't work either.
The files in this case are pretty important and should be tracked by chef, but again the pyc files get in the way.

As the author of the Chef+Python world, I would highly recommend turning your scripts into packages and installing them via normal pip mechanism. It's a small amount of work up-front to do the conversion, but worlds easier to manage.

Pip doesn't address the files changing.
In the world of servers this makes sense, but when managing user devices that drift every minute of every day, things like this are not only better, but more secure.

yeah i don't particularly like this from the perspective of creeping featurism on the remote_directory resource.
this should probably be a feature on the zap cookbook and that cookbook should be made to work with remote_directory (although the latest version might?  i suspect that the way that remote_directory doesn't properly use_inline_resources prevents it from working though).
and if instead we're going to go down this route it needs to be engineered to allow arbitrary file specification from the start so that we don't keep adding more properties to solve the same problem in different ways one by one.  only solving the problem for file extensions is limiting and not enough (which is another reason why i think it needs to go into zap).

Alright thanks for the feedback. I'll continue using this as a custom provider.


How can I reference images when using a google sheet?

I am using the google sheet option but where do I need to place the mentioned images in that sheet? Where is the app looking for the image?

it's looking in that google sheet directory IF I have it locally it seems


Gitea Leaving Defunct Process On container crash

Description
Gitea failing to start, upon being restarted, ignores the shutdown signal and leaves defunct processes, have left the stuck container running overnight and does not resolve on it's own.
here is the deploy template  for reference
here is the custom dockerfile, the additions are just to add the root CA cert for my CA
Gitea Version
1.18.0-rootless
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
https://gist.github.com/gerethd/706ebcdd20b4ec895cfe5beaae610602#file-gitea-console-log
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
kubernetes, via containerd
Database
PostgreSQL

Additional debugging on my part has led me to find that <gitea_data_dir>/data/indexers/issues.bleve/store is returning a IO error on access, which is definitely an issue on my part but it would be nice if gitea could handle IO errors a bit more gracefully


Port CommunityToolkit.Diagnostics docs

This PR ports the Diagnostics docs. Haven't updated the links to the generated docs yet, as I think that's for later?

Learn Build status updates of commit 03a9e9f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/diagnostics/Guard.md
:white_check_mark:Succeeded
View

docs/diagnostics/Introduction.md
:white_check_mark:Succeeded
View

docs/diagnostics/ThrowHelper.md
:white_check_mark:Succeeded
View

docs/TOC.yml
:white_check_mark:Succeeded
View

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

Learn Build status updates of commit 03a9e9f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/diagnostics/Guard.md
:white_check_mark:Succeeded
View

docs/diagnostics/Introduction.md
:white_check_mark:Succeeded
View

docs/diagnostics/ThrowHelper.md
:white_check_mark:Succeeded
View

docs/TOC.yml
:white_check_mark:Succeeded
View

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

Learn Build status updates of commit 832032e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/diagnostics/Guard.md
:white_check_mark:Succeeded
View

docs/diagnostics/Introduction.md
:white_check_mark:Succeeded
View

docs/diagnostics/ThrowHelper.md
:white_check_mark:Succeeded
View

docs/TOC.yml
:white_check_mark:Succeeded
View

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

Learn Build status updates of commit 043aec7:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed]

Cannot sync git repo to specified commit because ref +refs/pull/146/merge has been deleted or has been force pushed.
 If this is pull request, please ensure it is mergeable (no merge conflict) and open (not closed).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Hey @michael-hawker, could you take a look at this and #147 when you have a minute?
We'll also need to find a way to setup those redirects, do you know who we should be reaching out to? 😄

Learn Build status updates of commit 043aec7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/diagnostics/Guard.md
:white_check_mark:Succeeded
View

docs/diagnostics/Introduction.md
:white_check_mark:Succeeded
View

docs/diagnostics/ThrowHelper.md
:white_check_mark:Succeeded
View

docs/TOC.yml
:white_check_mark:Succeeded
View

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


wget to external resource fails in installation

Hi,
I tried to install bcbio-nextgen master a couple of times now, and the install seems to be stuck in bcbio/genomes/Hsapiens/GRCh37/txtmp/ggd-run.sh, more specifically :
--2019-08-23 09:17:02--  https://nc.hartwigmedicalfoundation.nl/index.php/s/a8lgLsUrZI5gndd/download?path=%2FHMF-Pipeline-Resources&files=GC_profile.hg19.1000bp.cnp.gz
Resolving nc.hartwigmedicalfoundation.nl (nc.hartwigmedicalfoundation.nl)... <IP_ADDRESS>
Connecting to nc.hartwigmedicalfoundation.nl (nc.hartwigmedicalfoundation.nl)|<IP_ADDRESS>|:443... connected.
 HTTP request sent, awaiting response... 404 Not Found                                                                                2019-08-23 09:17:02 ERROR 404: Not Found.                                                                                gzip: stdin: unexpected end of file

Isolating the wget command that errors,
wget --no-check-certificate -O - 'https://nc.hartwigmedicalfoundation.nl/index.php/s/a8lgLsUrZI5gndd/download?path=%2FHMF-Pipeline-Resources&files=GC_profile.hg19.1000bp.cnp.gz' | gunzip -c > $gc/GC_profile.1000bp.cnp

fails as well, as could be expected with error404.
As this is something that is out of your hands, would it be possible to catch these errors and log them afterwards instead of making the install fail?
Kind regards,
Simon

Hi Simon,
Sorry about that-- it looks like they took those down; I'm not sure if it temporary or not. We have other copies of them on an AWS bucket, let me just make sure they are the same files and if so we can download from there instead.


Runtime error restoring mydumper backup with pscale db restore-dump

I made a backup with mydumper that contained a file named employees-schema-triggers.sql. The triggers file is empty, there are no triggers in the origin database. Maybe mydumper creates this file by default.
When I attempt to restore the backup via pscale I get this error every time:
~$ pscale db restore-dump employees main --dir minimal
Starting to restore database employees from folder minimal
⠇ Restoring database ...panic: runtime error: index out of range [1] with length 1

goroutine 54 [running]:
github.com/planetscale/cli/internal/dumper.(*Loader).restoreTable(0xc0001b6a50, {0xc0002c6360, 0x27}, 0xc0002bc168)
	github.com/planetscale/cli/internal/dumper/loader.go:244 +0x996
github.com/planetscale/cli/internal/dumper.(*Loader).Run.func1()
	github.com/planetscale/cli/internal/dumper/loader.go:88 +0x85
golang.org/x/sync/errgroup.(*Group).Go.func1()
	golang.org/x/sync@v0.2.0/errgroup/errgroup.go:75 +0x64
created by golang.org/x/sync/errgroup.(*Group).Go
	golang.org/x/sync@v0.2.0/errgroup/errgroup.go:72 +0xa5

If I remove the employees-schema-triggers.sql file the restore succeeds.
Here's a dump directory that reproduces the issue: minimal.zip

Fixed in https://github.com/planetscale/cli/pull/698


Fix text color in rules image source

currently the text around the link is white on white
btw. we should probably think about making the color definitions more general and not view specific to avoid redundandcy.

:+1: the perfect is the enemy of the good ;-)


Fix broken headings in Markdown files

GitHub changed the way Markdown headings are parsed, so this change fixes it.
See bryant1410/readmesfix for more information.
Tackles bryant1410/readmesfix#1

Coverage remained the same at 95.376% when pulling f788912a71053387bc52aa52b68bc4096fcc68fe on bryant1410:develop into 34fd38787763fc676dc65c8eb35774391036e7b5 on apolukhin:develop.

Thanks for the fix!


one problem occurred when trainning  fcn-xs,the log as follows.I have no idea what happend,and I just did it according to readme. how to fix it, would someone like to help me out,thanks so much.

dl@dl:~/mxnet/example/fcn-xs$ ./run_fcnxs.sh
INFO:root:Namespace(epoch=74, init_type='vgg16', model='fcn32s', prefix='VGG_FC_ILSVRC_16_layers', retrain=False)
/home/dl/mxnet/example/fcn-xs/data.py:79: VisibleDeprecationWarning: using a non-integer number instead of an integer will result in an error in the future
img = img[:, rand_start : rand_start + min_hw]
/home/dl/mxnet/example/fcn-xs/data.py:80: VisibleDeprecationWarning: using a non-integer number instead of an integer will result in an error in the future
label = label[:, rand_start : rand_start + min_hw]
INFO:root:Start training with gpu(0)
[13:04:12] /home/dl/mxnet/dmlc-core/include/dmlc/logging.h:235: [13:04:12] src/operator/./crop-inl.h:117: Check failed: (static_cast(param_.offset[0])) <= (data_shape[2]-out_shape[2]) offset[0] should be less than the residual space of height
[13:04:12] /home/dl/mxnet/dmlc-core/include/dmlc/logging.h:235: [13:04:12] src/engine/./threaded_engine.h:306: [13:04:12] src/operator/./crop-inl.h:117: Check failed: (static_cast(param_.offset[0])) <= (data_shape[2]-out_shape[2]) offset[0] should be less than the residual space of height
An fatal error occurred in asynchronous engine operation. If you do not know what caused this error, you can try set environment variable MXNET_ENGINE_TYPE to NaiveEngine and run with debugger (i.e. gdb). This will force all operations to be synchronous and backtrace will give you the series of calls that lead to this error. Remember to set MXNET_ENGINE_TYPE back to empty after debugging.
terminate called after throwing an instance of 'dmlc::Error'
what():  [13:04:12] src/engine/./threaded_engine.h:306: [13:04:12] src/operator/./crop-inl.h:117: Check failed: (static_cast(param_.offset[0])) <= (data_shape[2]-out_shape[2]) offset[0] should be less than the residual space of height
An fatal error occurred in asynchronous engine operation. If you do not know what caused this error, you can try set environment variable MXNET_ENGINE_TYPE to NaiveEngine and run with debugger (i.e. gdb). This will force all operations to be synchronous and backtrace will give you the series of calls that lead to this error. Remember to set MXNET_ENGINE_TYPE back to empty after debugging.
./run_fcnxs.sh: line 3:  5298 Aborted                 (core dumped) python -u fcn_xs.py --model=fcn32s --prefix=VGG_FC_ILSVRC_16_layers --epoch=74 --init-type=vgg16

now I can locate the problem,"" pred = mx.nd.array(output_buff["softmax_output"].asnumpy().reshape(pred_shape[0],
pred_shape[1], pred_shape[2]*pred_shape[3]))"" in solver.py. Is there anyone have the same problem, I need help!

@zhenzhen1022 i'll check it this week.

@zhenzhen1022 https://github.com/dmlc/mxnet/pull/3654

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


Arrow keys are acting different for different components on same page

The > icons means different things depending on where or what component your in.  We should be consistent on what directions we are using and what they mean.  Currently:

The one for the cluster list doesn't work and is always facing >
For Namespace control, ^ means open and v means closed
For Left Navigation, v means open and > means closed.

v should closed, ^ should be open hinting at what direction next action will be.

https://github.com/rancher/dashboard/pull/365 fixed but cluster dropdown needs to function @vincent99

Fixed


Add capability report loop support

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
design-specs #1
Special notes for your reviewer:
Release note:

Coverage decreased (-0.5%) to 58.463% when pulling 968a35d4341994798b80ed6c67d81d5bbc1094a9 on leonwanghui:capability_report into 2742cd03b1ecf4ed9a2a7735c9180aa43fba10c0 on opensds:development.

Coverage decreased (-0.5%) to 58.463% when pulling 968a35d4341994798b80ed6c67d81d5bbc1094a9 on leonwanghui:capability_report into 2742cd03b1ecf4ed9a2a7735c9180aa43fba10c0 on opensds:development.

/lgtm


Updating kafka service write location

These PR changes are made to resolve the issue #90
Kafka write location needs to be updated to ensure that the mount point in helm charts and kafka service topics/partitions write location are not same to avoid known issue of lost+found directory https://github.com/ches/docker-kafka/issues/28
These changes are backward compatible as we are creating a sub folder under /opt/pega/kafkadata
Refer BUG-575909 for more details.

Starting pipeline for PR validation -> PR-87-1

Starting pipeline for PR validation -> PR-87-2

Starting pipeline for PR validation -> PR-87-3

Starting pipeline for PR validation -> PR-87-1

Starting pipeline for PR validation -> PR-87-2

Starting pipeline for PR validation -> PR-87-3

Starting pipeline for PR validation -> PR-87-3

Starting pipeline for PR validation -> PR-87-3

Starting pipeline for PR validation -> PR-87-3

Starting pipeline for PR validation -> PR-87-4

Starting pipeline for PR validation -> PR-87-4

#90

#90


In-game time flow speed

Hello,
I would like to adjust the in-game time flow speed. For example, I want to make the time pass at double the normal speed. Is there a built-in parameter or method in Mineland that allows for modifying the time scale, such as time_scale or similar? If not, could you suggest a recommended way to implement this, either by tweaking the environment settings or by manipulating the simulation steps?
Thank you in advance for your help!

MineLand has no method to implement "make the time pass at double the normal speed".
MineLand provides a parameter "ticks_per_step", which only affects the time taken by mland.tick() and cannot modify the time scale. MineLand also provides a parameter enable_auto_pause, but this function isn't stable and we don't recommend to use it.
BTW, Minecraft doesn't support this function. To implement this, we must develop a mod using Fabric or Forge. It's a bit difficult.

Thanks for your reply！


Hard refresh or first page load select problem

When first loading a page or doing a hard refresh on a page with a form associated with a document, the select inputs won't properly update to the values of the document.
I suspect the problem is linked to the fact that Semantic-UI hijacks some of the update/change events.
I don't have much time to investigate at the moment, any ideas appreciated!
#33 #37

Hmm... I'm not seeing this behavior.


Chinese doc translation issue.

Hi @bebraw and @TheLarkInn.
We are recently having trouble with managing our translation docs. As we know, webpack doc repo does not keep loader and plugin docs itself. So we have to translate docs under generated folder which  makes us harder to make a diff.
Would you think of keeping those docs under content folder ? i.e., run a program to regularly update docs from each loader and plugin.

There's also the possibility to doing Kron jobs on Travis. Thoughts?

A cron job would have to perform sync commits against master. I'm not sure if that's a smart idea.
Would it make sense to set up an intermediate repository like that? You would generate the directory there, and whenever you want to update the translation, you would trigger the generation script against that, get a diff, and then translate. I think this might give you the information you need to keep it up to date without complicating the setup of the main site.

We are having this repo for translation.
That would be great if we could have such an intermediate repo. Then we could run a script to update the content ourselves.  I think it would also help if other developers want to translate the doc into other languages.

@lcxfs1991 Ok, I'll try to set up one below webpack-contrib once I find a bit of time. I'll add you to the project too so you can update it etc.

Thank you so much.
Please also add dear-lizhihua who also leads the translation project.

Thanks @bebraw. 🙇

hey @bebraw.
We have another suggestion  that a new branch translation can be created under webpack.js.org based on branch master.
In branch translation, we can manage a script to update docs from loaders/plugins manually. On the one hand, we can update major docs of webpack if master branch is updated. On the other hand, once there is an update from loaders/plugins doc, we can merge content from translation to our translation repository.
Managing another branch may be easier than another new repository.

@lcxfs1991 Is it enough if I set up a branch with proper rights for you to handle then? That sounds simpler, yeah.

yes man.

@lcxfs1991 Ok. I set up the branch and sent you an invite. You should be able to write to the branch.

thanks!