Fix documentation link to reference man3

Was helping someone find their way around the SHA-3 EVP documentation and ran into this link error (stolen from https://www.openssl.org/docs/manmaster/man3/EVP_DigestInit.html):

New applications should use the SHA-2 (such as EVP_sha256(3)) or the SHA-3 digest algorithms (such as EVP_sha3_512). The other digest algorithms are still in common use.

After this change this particular documentation area is generated properly (built from openssl/master locally):

New applications should use the SHA-2 (such as EVP_sha256(3)) or the SHA-3 digest algorithms (such as EVP_sha3_512(3)). The other digest algorithms are still in common use.

Checklist

[X] documentation is added or updated

BTW, I would say this is a trivial fix.  If you agree with that and don't want to sign a CLA just for this, we're asking that you modify the commit message by adding the following line:
CLA: trivial

The easiest way to modify a commit message is this (from command line):
git commit --amend

Then force push the result:
git push -f    # maybe git push -f github HEAD

Thanks for the quick review!

Merged!  89f66fe2bc4fc9bf5eb17a377cd9561f46985222
Thank you!


Use correct ca_certs path in signing section

In older versions where PKI token signing was used, signing section
was using the same cert/key paths as ssl but ca_certs attribute was not
updated.

@JanZerebecki this repo doesn't have per-release branches. The condition is explicit in the code.


📃: Addition of Deep Sea Diver Game

🔴 Title: Deep Sea Diver
🔴 Tech stack: HTML, CSS, JavaScript
🔴 Objective: Collect treasures while avoiding sharks in the deep sea.
🔴 Summary: In "Deep Sea Diver," players control a diver to collect treasures while dodging sharks. The player navigates through the ocean, increasing their score by collecting treasures. Sharks pose a constant threat, and the player must avoid them to keep playing.

✅ Details to Include When Taking the Issue:
Name : V Pratheek
Participant Role: Contributor at GSSOC and Hacktoberfest

Happy Contributing! 🚀
Wishing you all the best on your open source journey. Enjoy! 😎

@iamrahulmahato Please assign it to me ASAP , I will start working on it immediately....Thanks :)


no file output when exit() is reached

When executing a multiWriter as part of a try catch if I have the program run an exit() as part of the error handling I get no output into a file if I comment out the exit it will write to the file as expected however execution will continue which in the case of a config file I don't want to happen... I'm not sure if I'm doing something wrong or if there is something else at play here.

Hi, could you please add some code which showcases your problem?

We experience the same issue. We have a logger configured which outputs to stdout and a file. The output to stdout is fine when using exit() while the file does not contain the last log lines.

sorry was on vacation when you replied
catch (e) {
    if (e is TomlException) {
      multiLogger(e.toString(), Level.wtf, 'TOML Error');
      exit(13);
    } else if (e is MySQLException) {
      multiLogger(e.toString(), Level.wtf, 'MySQL Error');
      exit(13);
    } else if (e is PathNotFoundException || e is PathAccessException) {
      multiLogger(e.toString(), Level.wtf, 'Path not found');
      exit(2);
    }

and then multilogger just calls the logger from the library so i didn't have to set it up in each of the different bits of the files
Future multiLogger(String? event, Level level, [String? message]) async {
  final logfile = io.File('tessera.log');
  var logger = Logger(
      filter: ProductionFilter(),
      printer: HybridPrinter(
        PrefixPrinter(SimplePrinter(colors: false, printTime: true)),
        error: PrefixPrinter(
            PrettyPrinter(colors: false, printEmojis: true, printTime: true)),
        warning: PrefixPrinter(
            PrettyPrinter(colors: false, printEmojis: true, printTime: true)),
        wtf: PrefixPrinter(
            wtf: 'FATAL',
            PrettyPrinter(colors: false, printEmojis: true, printTime: true)),
      ),
      output: MultiOutput([
        ConsoleOutput(),
        FileOutput(
          file: logfile,
          overrideExisting: false,
          encoding: utf8,
        ),
      ]));
  logger.log(level, event, message);
  logger.close();
}

I guess I found your problem.
The output is probably missing due to FileOutput being silently async, which can probably never finish flushing your logs because of your exit call.
The async functionality is implemented in 2.0.0 and will make logger.close() await-able.
More information: #20


Remove the uncessary \

Remove the additional "" in the ext auth doc, which was added by accident.  :-)

/retest


Store Channel Info: Channel Category Name :: Stops whole action sequence if null.

If a channel category is null the store channel info: channel category name will stop and break the rest of the action sequence.

https://github.com/Discord-Bot-Maker-Mods/DBM-Mods/blob/86a1267f08e79d23dd2cb144a9f576257effc940/actions/store_channel_info.js#L231
Change the line above to:
result = targetChannel.parent && targetChannel.parent.name;


A note about upgrading dependencies from version 9 version 10

If your library (or a dependency) depends on v9 and you're trying to upgrade to v10
Let's say you want to help upgrade an open source package that depends on Highlight.js v9.  You'd like to help upgrade it to v10 because it's a dependency of your project but the maintainer seems busy, or no longer around - but you know JavaScript and you have some time to work on a PR.  And of course even if the fix is easy if the author is no longer around getting that fix on NPM might require republishing the library or some such, but if so that'd just be what had to be done.  Best case is the author is around (just busy) and could merge a PR if you could submit one.
So this can be SUPER easy or it can be insanely difficult - all depends on the library.  lowlight is a popular dependent of Highlight.js.  In prior versions (v9) they pretty much maintained their own fork of the library - because that's what they had to do to hook into the internals they needed.  Not a trivial upgrade scenario.
Yet several of the libraries I've see at a glance just call our public API (highlight, highlightAuto, etc)...  Our public API between v9 and v10 was remarkably stable.
It's possible some of these libraries might actually "just work" with ONLY a version bump:
# fetch the library
git clone older-library
cd older-library
# install the latest v10 version of Highlight.js
npm install highlight.js@latest
# run tests maybe?
git commit
# make PR request

Obviously knowing a little about NPM and JavaScript will go a long ways if you wanted to help out here.  If anyone has any specific questions about the process of upgrading or any of the breaking changes mentioned below, I'm happy to help as I can.  I just don't have time to update all the possible dependents because NPM says that's almost 3000 packages. :-)
The biggest thing is we no longer support IE11 on the client-side... but if you're only using our library on the server-side that wouldn't matter at all.
Reference:

https://github.com/highlightjs/highlight.js/blob/master/VERSION_10_UPGRADE.md
https://github.com/highlightjs/highlight.js/blob/master/VERSION_10_BREAKING_CHANGES.md

Who's genius idea was it to add this warning in a patch release?

✋🏻 Though it's not "just" a patch release.  It's the last release in the series, EOL announcement, etc.

FYI it's massive bad practice to do this in a patch.

What would you say is the best practice for something like this?  We wanted everyone to see it and it's possible that some package maintainers pinned the minor version... so issuing a new minor release might not have had any effect for those users.
And just to be clear are you referring to the post-install or the console.log (it's a console.log now, not a warning)?

You can add the warning during yarn install or npm install ...

Yes, we also did those things also (though I was going to allow a small time window before deprecating 9.18.5)... though I don't have a strong reason - I'm just playing this by ear.  I've also been told yarn hides post-install output.
Technically v9 was "theoretically" EOLed (made obsolete) back in April with the release of 10 and our official dropping of support for IE11 (the only real argument not to switch to v10).  But I'm not sure everyone got that message (I'd say the fact that we're having these discussions now shows not) - so hence our wanting to do it now very loudly so that everyone possible knows and we aren't still talking about v9 in 2021.
We can't of course stop anyone from continuing to use it, but we can make it clear we feel it's a bad idea.   Re: Deprecate.  So many people I've spoken with pretty much ignore it completely, so it didn't seem a great "primary" choice.  I wholly agree warn vs log was a blunder on my part. :-)
Out of curiosity is the console.log causing you any particular problem with your setup or you just wanted to add a not on best practices?

You can add the warning during yarn install or npm install ...

Also we've had a LOT of people tell us "please don't do that"... so it seems not everyone is on the same page on this. :)  Unless you specially mean ONLY deprecate when you say warning - but back to my point about people just ignoring that... it's hard to discuss these things without being 100% clear.

https://github.com/highlightjs/highlight.js/issues/2881
If you have any specific thoughts on how to clearly communicate EOL to users of NPM packages and wanted to share on that thread we're very willing to learn for when the 10 -> 11 transition comes around.  I'm not sure that's even really a thing in the NPM/Node.js culture though. deprecate seems not much used and the API a bit buggy in my experience.  I look on NPM and find packages (including our own) with versions going back years and years - some with serious and not so serious security issues.   We still had our 1.0.0 on there until just the other day.
And while we could perhaps issue CVEs (or just advisories) against old versions - that's a bit more nebulous (correct me if I'm wrong) when we're confident there are issues (or strong potential issues) but you don't know exactly what they are.

You have to understand your users. There is no benefit to upgrade in most cases; for example, markdown-it includes your dep and is now throwing the error for me. I honestly don't care about what version or highlight.js is being used

To be clear I don’t know what you mean “throwing the error“. 9.18.5  does not throw any errors.

You have to understand your users. There is no benefit to upgrade in most cases;

Even if (just for the sake of discussion) I agreed with your second statement... you have to realize the opposite is also true - there are absolutely some [serious] benefits in some use cases to upgrade.  In such cases there are also very real downsides and potential costs for not upgrading. Some users care very, very much.
The the last 9.18 update should not have broken anyones projects.  The fact that it did (via writing to STDERR) has been resolved (the same day) and 9.18.5 should be a drop-in replacement for 9.18.3.  If you're on 9.18.5 and seeing a specific regression compared to 9.18.x you'd need to provide additional details.

Closing this in favor of it's mention at https://github.com/highlightjs/highlight.js/issues/2877.

Good

Good


Bug: WindowService doesn't exist in @foblex/core 1.2.5 and 1.2.4

Description
When I tried to install @foblex/f-flow on a new project, I got the following error:
✘ [ERROR] TS2305: Module '"@foblex/core"' has no exported member 'WindowService'. [plugin angular-compiler]

    node_modules/@foblex/flow/f-draggable/domain/convert-computed-to-pixels/convert-computed-to-pixels.execution.d.ts:2:9:
      2 │ import { WindowService } from '@foblex/core';
        ╵          ~~~~~~~~~~~~~

After a quick investigation, the root cause is that the @foblex/core dependency does not contain WindowService.
Is it possible to fix this, please? Also, could you please move @foblex/core to your account at https://github.com/Foblex?"
Steps to Reproduce

Create new angular project
Install @foblex/f-flow
Start server

Expected Result
Angular server will not start because we will have compilation error
Actual Result
compilation error
✘ [ERROR] TS2305: Module '"@foblex/core"' has no exported member 'WindowService'. [plugin angular-compiler]

    node_modules/@foblex/flow/domain/update-item-and-children-layers/update-item-and-children-layers.execution.d.ts:4:9:
      4 │ import { WindowService } from '@foblex/core';
        ╵          ~~~~~~~~~~~~~

Environment Details
@foblex/flow 12.6.1 and 12.6.0
Screenshots or Videos
No response
Additional Context
No response

@fouad-j Thank you for bringing this issue to our attention. We’ve identified and fixed the problem with the missing WindowService in @foblex/core. To resolve the error, please reinstall @foblex/f-flow in your project:
1.	Remove the existing @foblex/flow and @foblex/core packages from your node_modules directory and package.json.
2.	Run npm install @foblex/flow to install the latest version with the fix.

@siarheihuzarevich Thanks. It resolves the issue


ART-1962: Protect resolving public upstreams with lock

Per discussion https://coreos.slack.com/archives/GDBRP5YJH/p1592890124250700, use a lock to protect resolving public upstreams in order to simplify the logic and prevent potential race conditions.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@57c138c). Click here to learn what that means.
The diff coverage is 10.34%.

@@            Coverage Diff            @@
##             master     #230   +/-   ##
=========================================
  Coverage          ?   25.79%
=========================================
  Files             ?       26
  Lines             ?     5671
  Branches          ?     1126
=========================================
  Hits              ?     1463
  Misses            ?     4160
  Partials          ?       48

Impacted Files
Coverage Δ

doozerlib/runtime.py
27.44% <10.34%> (ø)

doozerlib/gitdata.py
18.51% <0.00%> (ø)

doozerlib/olm/bundle.py
0.00% <0.00%> (ø)

doozerlib/repos.py
45.05% <0.00%> (ø)

doozerlib/exceptions.py
100.00% <0.00%> (ø)

doozerlib/model.py
54.28% <0.00%> (ø)

doozerlib/exectools.py
51.81% <0.00%> (ø)

doozerlib/constants.py
100.00% <0.00%> (ø)

doozerlib/__init__.py
62.50% <0.00%> (ø)

doozerlib/pushd.py
95.65% <0.00%> (ø)

... and 17 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 57c138c...5d1635a. Read the comment docs.


Put modal and its content under (zIndex) Header?

Hi, I am working on a project and am finding it very difficult to get the modal to be put underneath (in a zIndex / elevation manner) the Header that I have. The header is in Native Base so I don't know if this is an issue with Native Base or react-native-modal.

That is what it currently looks like and it seems that no matter how I adjust the zIndex or elevation of the components, I cannot get anything to really go on-top of the modal... any help would be appreciated.

Hello @kylanhurt !
Could you try swapping the react-native-modal with react-native's modal and see if the problem persists?

@mmazzarolo The problem persists. The only way I can figure out to do it is to us the native modal, give it transparency and then put a marginTop equal to the height of the header. It seems very hacky, IMO and even more hacky when you consider that I cannot get the modal to "slide" in from the top especially when you consider that it will have to slide on-top / over the header.
Very disappointing.

@kylanhurt that's sad :(
Maybe you should try open an issue in the react-native official repo? You can link this issue if needed.
Is adding a customizable top margin prop to react-native-modal really that bad in your opinion? 🤔


Fix of Android SDK validation (>= 21) error not available with the npm package

Hi,
I use this Nativescript plugin, it's very a good job, congratulations. But the fix of the problem mentioned here : #12 for this error : ERROR Error: java.lang.NoSuchFieldError: no static field with name='LOLLIPOP' signature='I' in class Landroid/os/Build$VERSION_CODES; is not available with the npm package.

same to me


Allow safely probing for surrounding _InheritedNestedScrollView

Use case
I find myself often using NestedScrollView.sliverOverlapAbsorberHandleFor lately, as I am adding SliverAppBars to my App.
An immediate problem presents itself:
I always have to manually inject a SliverOverlapAbsorber and a SliverOverlapInjector whenever I am in a NestedScrollView,
because there is no convenient way to automatically detect a surrounding NestedScrollView and inject a SliverOverlapAbsorber with a NestedScrollView.sliverOverlapAbsorberHandleFor.
This is because, were I to access NestedScrollView.sliverOverlapAbsorberHandleFor  in a context where no NestedScrollView is present, an AssertionError is thrown.
Proposal
It would be really nice and convenient if there was an inbuilt way for me to check for an enclosing NestedScrollView.
Preferrably, this check would rely on looking for a _InheritedNestedScrollView in the tree.
I can of course right now do a very slow Widget tree search for a NestedScrollView manually, and then based on that decide to access NestedScrollView.sliverOverlapAbsorberHandleFor.
Ideally, there would be something like a NestedScrollViewSliverOverlapAbsorber and a accompaning NestedScrollViewSliverOverlapInjector, which both conditionally inject the required sliver widgets when used inside a NestedScrollView, but I would also be okay writing those myself.
Basically I am trying to reduce the boilerplate of getting a SliverAppBar setup in a NestedScrollView, without having to crawl through the widget tree and ruining my render performance.

were I to access NestedScrollView.sliverOverlapAbsorberHandleFor in a context where no NestedScrollView is present, an AssertionError is thrown.

Maybe what we need here is a NestedScrollView.sliverOverlapAbsorberHandleMaybeFor method that has a nullable return type? That way you would know whether or not to insert the overlap injector.

Certainly, that would be a solution.
Unfortunately, neither SliverOverlapAbsorber nor SliverOverlapInjector take a nullable callback, so I will have to conditionally insert or remove them.


streamEvents does not properly work on RemoteRunnable

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain.js documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain.js rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
Chain
from langchain_core.prompts import ChatPromptTemplate
from langchain_openai.chat_models import ChatOpenAI
from langchain_core.output_parsers import StrOutputParser

OPENAI_API_KEY = "your API key"

chain = (
    ChatPromptTemplate.from_template("Tell me a joke about {input}")
    | ChatOpenAI(model="gpt-3.5-turbo-1106", api_key=OPENAI_API_KEY)
    | StrOutputParser()
)

LangServe app
from fastapi import FastAPI
from langserve import add_routes
import chain

app = FastAPI()
app.add_middleware(
    CORSMiddleware,
    allow_origins=["*"],
    allow_credentials=True,
    allow_methods=["*"],
    allow_headers=["*"],
    expose_headers=["*"],
)

add_routes(app, chain, path='/remote-chain')

if __name__ == "__main__":
    import os
    import uvicorn

    HTTP_PORT = 8081
    uvicorn.run(app, host="<IP_ADDRESS>", port=HTTP_PORT)

RemoteRunnable#streamEvents in JS
import { RemoteRunnable } from '@langchain/core/runnables/remote';

const remoteChain = new RemoteRunnable('remote-chain');

async function streamEvents() {
  const stream = remoteChain.streamEvents({ input: "programming" }, { version: "v1" });

  for await (const event of stream) {
    console.log('event', event);
  }
}

Expected this code to produce stream of events that one can expect from streamEvents and a POST request to /stream_events, but it hits POST /stream and the event stream/response looks like a regular stream response that uses SSE.
import chain
import asyncio

if __name__ == "__main__":
    async def run():
        events = chain.astream_events(dict(input="programming"), version='v1')

        async for event in events:
            print(event)

    asyncio.run(run());

This code properly streams all the events, proving that the chain itself is streamable.
Error Message and Stack Trace (if applicable)
No response
Description
streamEvents called on RemoteRunnable does not seem to properly stream the events and instead posts regular /stream endpoint.
The chain is streamable for sure (verified in python).
I also noticed that the chain.streamEvents function definition that i inspect on real chain instance in the browser debug console does not look like the definition i verify in code, but instead looks like the definition for Runnable._streamEvents:
chain.streamEvents

Runnable._streamEvents

RemoteRunnable.streamEvents

System Info
pnpm show langchain
<EMAIL_ADDRESS>| MIT | deps: 18 | versions: 269
Typescript bindings for langchain
https://github.com/langchain-ai/langchainjs/tree/main/langchain/

keywords: llm, ai, gpt3, chain, prompt, prompt engineering, chatgpt, machine learning, ml, openai, embeddings, vectorstores

dist
.tarball: https://registry.npmjs.org/langchain/-/langchain-0.1.36.tgz
.shasum: 2f201f681d83fb265716e28e7dfcfe61fbeef2c2
.integrity: sha512-NTbnCL/jKWIeEI//Nm1oG8nhW3vkYWvEMr1MPotmTThTfeKfO87eV/OAzAyh6Ruy6GFs/qofRgQZGIe6XvXTNQ==
.unpackedSize: 4.0 MB

dependencies:
@anthropic-ai/sdk: ^0.9.1
@langchain/community: ~0.0.47
@langchain/core: ~0.1.60
@langchain/openai: ~0.0.28
@langchain/textsplitters: ~0.0.0
binary-extensions: ^2.2.0
js-tiktoken: ^1.0.7
js-yaml: ^4.1.0
jsonpointer: ^5.0.1
langchainhub: ~0.0.8
langsmith: ~0.1.7
ml-distance: ^4.0.0
openapi-types: ^12.1.3
p-retry: 4
uuid: ^9.0.0
yaml: ^2.2.1
zod-to-json-schema: ^3.22.3
zod: ^3.22.4

maintainers:
- nfcampos<EMAIL_ADDRESS>- jacoblee93<EMAIL_ADDRESS>- andrewnguonly<EMAIL_ADDRESS>- davidduong<EMAIL_ADDRESS>- hwchase17<EMAIL_ADDRESS>- basproul<EMAIL_ADDRESS>
dist-tags:
latest: 0.1.36
next: 0.2.0-rc.1

published a week ago by jacoblee93<EMAIL_ADDRESS>
Platform: Linux
Node: v21.5.0
pnpm: 8.14.1

@dosu can you confirm that RemoteRunnable should have full support for streamEvents and it should include all the events from the sub-runnables from the remote runnable?

@dosu in what circumstances one cannot use streamEvents or it is unfeasible to use it?

@dosu i am pretty sure we are onto something.
When remote chain is RunnableSequence, its sub-runnables will not be included in the streamEvents, and only events with name==RunnableSequence will be streamed.
how one can target the inner rrunnables of RunnableSequence, when the sequence chain is exposed as langserve remote runnable and consumed in JS?

@dosu you tripped into the vague mumbo jumbo
tell me details about implementation of streamEvents for RunnableSequence so i can understand its limitations

@dosu it is still not helpful.
search for code that implements streamEvents for RunnableSequence and explain to me step by step how it works

I have this issue as well with an AgentExecutor, the /stream endpoint is called but I get all the chunks at once, like invoke. steamEvents is the same.

In my case, I believe the issue boils down to a couple of things. My RemoteRunnable ends up piped in and out of some RunnableLambdas to help support input and output formatting as it is used in other chains It seems RunnableLambda does not implement its own streamEvents method, and therefore uses the implementation from Runnable. In looking at the implementation, it seems that for v1 events, the system uses streamLog:
https://github.com/langchain-ai/langchainjs/blob/main/langchain-core/src/runnables/base.ts#L961C24-L961C34
And then for v2 events, it is using stream:
https://github.com/langchain-ai/langchainjs/blob/main/langchain-core/src/runnables/base.ts#L898C38-L898C54
This is what seems to be causing the system to call the /stream endpoint when running with version 2. When streamEvents is called on the RunnableLambda, it is converted to a this.stream call, and causes RemoteRunnable to call the /stream endpoint?
Should the base implementation of v2 event streaming be calling outerThis.streamEvents instead of just .stream?
I believe this issue would occur with a RemoteRunnable that is piped with any of the core runnable types that rely on the base streamEvents implementation... Like RunnableSequence, RunnableMap, RunnableAssign and so on.
@dosu thoughts?

Well, in hindsight, it makes sense, outerThis.streamEvents seems to put everything in an endless loop, so that probably isn't the solution. I don't know enough about the inner workings of langchainjs to really knokw what the right solution is here.
The issue only arises with RemoteRunnable in the chain.
@dosu Do you have thoughts on how to fix the issue with a lot of the core Runnables switching to stream on streamEvents and causing RemoteRunnable to call the wrong endpoint?


Update Swap

Closes #298

I wonder if we should rather have a static factory for ExchangeRateProvider instead of the current solution.
@florianv your feedback is very welcome.

Thanks @sagikazarmark for taking initiative on that!
This looks ok to me, nothing to add 👍

Thanks for the feedback @florianv


relative paths or not valid when trying to connect to an absolute path with "/" folder delimiters

When trying to open a file with h5pyd.File the call returns relative paths or not valid when trying to connect with an absolute path (e.g. /a/b/c.h5 - the same call works fine when called with . as folder delimiters instead (e.g. a.b.c). The culprit seems to lie on lines 185-186 in _hl/files.py:
if domain.find('/') > 0:
    raise IOError(400, "relative paths or not valid")

This check seems not to provide the intended functionality as it prohibits any opening of / sperated paths.
The check should probably be:
if domain.find('/.') > 0:
or
if domain.find('/..') > 0:

Hey,
There's a bit of legacy-related logic to this.  Originally in the development of the REST API we had the idea to use DNS style paths.  E.g. a domain could have posix-style of "/myfolder/myfile" or a DNS style: "myfile.myfolder".  The idea was to somehow route requests to a HSDS instance like DNS names get assigned to IPs.
Anyway, that never came to fruition, and on the whole is rather confusing.  Also, it was hard to support filename extensions like ".h5".   HSDS itself still supports the DNS pattern, but I don't think h5pyd does.
So I checked in a h5pyd change that just verifies the first character of the domain name is a  '/'.  This means paths like "a.b.c" will raise the "relative paths are not valid" error.
Paths like '/myfolder/myfile.h5' should have worked before though.  It's not clear to me why the absolute path would be rejected.   Anyway, try out the last master branch update.
If anyone has a case to retain the DNS-style functionality, please respond here!

Hello,
So DNS style paths will not be supported in the future? because with h5pyd < 0.8.4 DNS style paths worked just fine.
'/myfolder/myfile.h5' is definitely considered invalid by h5pyd according with the previously mentioned check. Even if this is working as intended I would change the error message to reflect more clearly on the issue.
Also I obiously filed this issue under the wrong project (hsds instead of h5pyd).

Hello again,
Finally got around to updating our hsds server to the newest master branch and i no longer encounter this error. Seems like it was fixed or just a user error. Thanks for the help!


[1.x] Update to 1.15.5

Checklist

[x] Used a personal fork of the feedstock to propose changes
Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Needed for https://github.com/conda-forge/apache-beam-feedstock/pull/53


[BUG]: PowerBI Dashboard -  Top App Maker Cities shows Warrington in the USA rather than Warrington England

Describe the bug
PowerBI Dashboard - The Top App MAker Pane on the Overview - PowerApps Tab Shows Warrington in the USA rather than Warrington in England
Component (please tell us which flow or app you are experiencing issues with):

Solution- Core
Version - 1.54
PowerBI -  Dashboard-PowerPlatformAdminDashboard_2020-07-07

To Reproduce
Steps to reproduce the behavior:

Go to 'the Overview - PowerApp Tab.'
See error

Expected behavior
Should show Warrington England not Warrington USA
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Hi Manuela
I followed your instructions and If I right click on the Bing Map I see Column Country, City has a value United Kingdom, Warrington.
But the Bing Map is just of the whole world.
What have I done wrong ?  (I have also set the data category of the Country, City field to “City” as per the article.)
Regards
Nigel
From: Manuela Pichler<EMAIL_ADDRESS>Sent: 30 July 2020 13:33
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: PowerBI Dashboard - Top App Maker Cities shows Warrington in the USA rather than Warrington England (#400)
Huh! I blame Americans for stealing our city names.
I followed the Solution 1 in this articlehttps://www.biinsight.com/how-to-overcome-map-related-issues-in-power-bi-power-view-and-power-map/ and I think it works now. We'll include that with the next release, in the meantime if you want to change it locally on your end.

Open the .pbix file in Power BI Desktop
Select App under Fields
[image]https://user-images.githubusercontent.com/55705669/88922883-b4349c80-d268-11ea-84a5-fef6907ac595.png
Select Table Tools > New Column
[image]https://user-images.githubusercontent.com/55705669/88922919-c3b3e580-d268-11ea-98db-ea35f043ea72.png
Enter the following formula for your Column: Country, City = RELATED(Maker[admin_country])& ", " & RELATED(Maker[admin_city]) and then select Column Tools > set Data Category to Place
[image]https://user-images.githubusercontent.com/55705669/88922982-e2b27780-d268-11ea-9f8f-a905cd00fa68.png
Select the Overview - Power Apps page of the dashboard, highlight the Map visual and replace the fields from City to the new Country, City field (complete the same for Overview - Flow)
[image]https://user-images.githubusercontent.com/55705669/88923053-fe1d8280-d268-11ea-9a00-7bfa27c8e7e4.png

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/400#issuecomment-666336230, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUGGS37Q3G7HMMQTQBDR6FR6XANCNFSM4PLPT7FA.

I have had the same, and had to set mine to Place (instead of City) and then it worked.

Yes, that worked.
From: Manuela Pichler<EMAIL_ADDRESS>Sent: 30 July 2020 18:58
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: PowerBI Dashboard - Top App Maker Cities shows Warrington in the USA rather than Warrington England (#400)
I have had the same, and had to set mine to Place (instead of City) and then it worked.
[image]https://user-images.githubusercontent.com/55705669/88957279-8ebe8780-d296-11ea-8d18-daf406b83d3a.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/400#issuecomment-666565348, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUB34DPOCL3VDRPCO2LR6GYDRANCNFSM4PLPT7FA.

Fantastic, thanks for confirming! I'm glad it worked for you, and thanks for reporting an issue that has gone unnoticed for a long time. It'll be included with the next version, too.

I have one glitch – as well as united kingdom, Warrington I also have “ . “ ie a blank record which now gets plotted on the map in a random place.
From: Manuela Pichler<EMAIL_ADDRESS>Sent: 30 July 2020 19:05
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: PowerBI Dashboard - Top App Maker Cities shows Warrington in the USA rather than Warrington England (#400)
Fantastic, thanks for confirming! I'm glad it worked for you, and thanks for reporting an issue that has gone unnoticed for a long time. It'll be included with the next version, too.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/400#issuecomment-666569217, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUCRZVUXJHGTQAY3233R6GY3TANCNFSM4PLPT7FA.

If you select the Maker table and then show Data and scroll to the admin_city and admin_country column, do all of your makers listed there have a City and Country? And if one is blank, could you verify if they have a City and Country in their Office 365 Profile - that's where we pull the information from

Hi Manuela
Its their Office 365 which is the problem there is no city or country there in Delve.
Regards
Nigel
From: Manuela Pichler<EMAIL_ADDRESS>Sent: 30 July 2020 19:12
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: PowerBI Dashboard - Top App Maker Cities shows Warrington in the USA rather than Warrington England (#400)
If you select the Maker table and then show Data and scroll to the admin_city and admin_country column, do all of your makers listed there have a City and Country? And if one is blank, could you verify if they have a City and Country in their Office 365 Profile - that's where we pull the information from
[image]https://user-images.githubusercontent.com/55705669/88958456-659ef680-d298-11ea-9d08-f05f2bbe66bb.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/400#issuecomment-666574276, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUBNBYUYCYUTFFVE2J3R6GZYNANCNFSM4PLPT7FA.


Allow to use bubuku with zookeeper

Right now bubuku wants to use exhibitor, but it must be possible to use it with Zookeeper only.

Not needed anymore


As a user, I'd like to be able to set my address verification settings at the user or profile levels

Unfortunately, we made the address verification settings protected, which means users cannot see or edit them. We need to change them to be public, but it seems like the package does not allow you to do that. We may have to create new ones and deprecate the old ones.

We made them public because the security review told us to do so.


specPath cannot be a directory, causes errors. Referencing other spec files from spec also causes errors.

Describe the bug
Using a directory in specPath results in an error:
Error: This doesn’t look like an OpenAPI document.
However, documentation states that this may be a directory.
Why I am trying to use a directory is because I am trying to reference other spec files from the main spec. However doing so causes issues as well:
Could not find resolver for "g:/[somepath...]/ApiCommons.yml%22"
SyntaxError: Unexpected token u in JSON at position 0
WARNING: the following OpenAPI spec returned undefined: G:/[somepath...]/Api.yml

Reference in Api.yml is:
$ref: "./ApiCommons.yml#/components/parameters/objectId/description"
It seems to turn the # into a sanitized string causing it not to find the referenced spec file.
Expected behavior
Either for directory to work (which I am trying to get to work to see if that solves my $ref issue. Or being able to reference other specs from a spec file.
Current behavior
Error when trying to use a directory or reference another spec file.
Steps to reproduce
Trying to run
yarn docusaurus gen-api-docs all
in
https://github.com/ApparyllisOrg/SimplyPluralApiDocs
But I suspect a simpler repro step to be:

Create first spec file for OpenApi 3.0
Create second spec file for OpenApi 3.0
Create parameters or schema in second
Attempt to reference the schema or parameter in first spec file
Set first spec file as the specPath in docusaurus openapi settings

Context

Your Environment

Version used: Docusaurus openApi 2.0.0-beta, Docusaurus 2.4.0
Environment name and version: Firefox, node v18.15.0
Operating System and version (desktop or mobile): Windows

Ended up being a rogue " in a spec path somewhere. Created a PR to improve error reporting to resolving refs: https://github.com/PaloAltoNetworks/docusaurus-openapi-docs/pull/560


Export/import library folder structure using a json file

@pkbullock should I split this into two samples , one for export and one for import ?

Looks fine to submit as one, you can always have two blocks of PowerShell one for export and in pop e for import. Anyway makes it simple?
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: Kasper Larsen @.>
Sent: Friday, November 10, 2023 11:21:57 AM
To: pnp/script-samples @.>
Cc: Paul Bullock @.>; Mention @.>
Subject: Re: [pnp/script-samples] Export/import library folder structure using a json file (Issue #617)
@pkbullockhttps://github.com/pkbullock should I split this into two samples , one for export and one for import ?
—
Reply to this email directly, view it on GitHubhttps://github.com/pnp/script-samples/issues/617#issuecomment-1805543762, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACC7Z4JQH6Q5GPLEQYU63QTYDYE5LAVCNFSM6AAAAAA7CWK2GWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBVGU2DGNZWGI.
You are receiving this because you were mentioned.Message ID: @.***>

Reference #619
Thanks Kasper, closing this.


Added checks to make sure specific cookie exists before manipulating it

Thanks a lot @azurebrd and @sweng66 for the debugging session!


Update blob_file_size unit MiB to bytes.

This refers to #612

I think this change makes sense since we didn't release them yet, so it won't have the breaking change. cc @ShooterIT

Is there some background of this change, e.g., a linked issue?

Thanks for @tisonkun remind, I can add the related issue to explain the background.

I wait this PR long time😂, @git-hulk yes, i agree, we already have thought blob_file_size uses byte unit but config file describe wrong unit, we should change it into byte unit.

@WyattJia please check all places where we use blob_file_size, and make sure not to multiple MiB In SetBlobDB, still RocksDB.blob_file_size * MiB
void Storage::SetBlobDB(rocksdb::ColumnFamilyOptions *cf_options) {
 ...
  cf_options->blob_file_size = config_->RocksDB.blob_file_size * MiB;
 ...
}

Thanks for reminding, I've checked unit about blob_file_size , @tisonkun @ShooterIT please check and review my changes, extremely grateful!

Perhaps tests/config_test.cc L74 should be updated from 256 to 268435456 also?

Yep, I updated.

Hi @WyattJia as #612 says, we also want to change max_bytes_for_level_base into byte unit instead of MiB, so do you also want to change it?

@ShooterIT I think it should be covered by #610.

oh, yes, thanks @tisonkun

@WyattJia Thanks for your contribution! Merging...


This error occurs when running the command

Traceback (most recent call last):
File "E:\project\segment-anything-main\scripts\amg.py", line 238, in
main(args)
File "E:\project\segment-anything-main\scripts\amg.py", line 221, in main
masks = generator.generate(image)
File "E:\project\segment-anything-main\venv\lib\site-packages\torch\autograd\grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "e:\project\segment-anything-main\segment_anything\automatic_mask_generator.py", line 164, in generate
mask_data = self._generate_masks(image)
File "e:\project\segment-anything-main\segment_anything\automatic_mask_generator.py", line 210, in _generate_masks
crop_data = self._process_crop(image, crop_box, layer_idx, orig_size)
File "e:\project\segment-anything-main\segment_anything\automatic_mask_generator.py", line 242, in _process_crop
self.predictor.set_image(cropped_im)
File "e:\project\segment-anything-main\segment_anything\predictor.py", line 60, in set_image
self.set_torch_image(input_image_torch, image.shape[:2])
File "E:\project\segment-anything-main\venv\lib\site-packages\torch\autograd\grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "e:\project\segment-anything-main\segment_anything\predictor.py", line 89, in set_torch_image
self.features = self.model.image_encoder(input_image)
File "E:\project\segment-anything-main\venv\lib\site-packages\torch\nn\modules\module.py", line 889, in _call_impl
result = self.forward(*input, **kwargs)
File "e:\project\segment-anything-main\segment_anything\modeling\image_encoder.py", line 112, in forward
x = blk(x)
File "E:\project\segment-anything-main\venv\lib\site-packages\torch\nn\modules\module.py", line 889, in _call_impl
result = self.forward(*input, **kwargs)
File "e:\project\segment-anything-main\segment_anything\modeling\image_encoder.py", line 174, in forward
x = self.attn(x)
File "E:\project\segment-anything-main\venv\lib\site-packages\torch\nn\modules\module.py", line 889, in _call_impl
result = self.forward(*input, **kwargs)
File "e:\project\segment-anything-main\segment_anything\modeling\image_encoder.py", line 234, in forward
attn = add_decomposed_rel_pos(attn, q, self.rel_pos_h, self.rel_pos_w, (H, W), (H, W))
File "e:\project\segment-anything-main\segment_anything\modeling\image_encoder.py", line 358, in add_decomposed_rel_pos
attn.view(B, q_h, q_w, k_h, k_w) + rel_h[:, :, :, :, None] + rel_w[:, :, :, None, :]
RuntimeError: CUDA out of memory. Tried to allocate 1024.00 MiB (GPU 0; 6.00 GiB total capacity; 4.60 GiB already allocated; 0 bytes free; 4.67 GiB reserved in total by PyTorch)

It seems that your gpu is out of memory. Maybe try a smaller image as input?

Now I'm using a 90kb image

Hello, I have the same issue. Did you find a solution? Thank you

I have done some reverse engineering,
You have to try the different combinations of  dtype (dtype= has multiple combinations, look the code https://github.com/pytorch/pytorch/blob/main/torch/nn/modules/module.py )  Also non_blocking combination
Example: torch.float16, torch.float32, torch.float64, torch.half, torch.cdouble, torch.complex128 ...) :
sam = sam_model_registry[KEY_model_type](checkpoint=sam_checkpoint)
gpu1 = torch.device("cuda:1")
sam.to(gpu1, dtype=torch.half, non_blocking=True)

It also helps to change the max_split_size_mb, also try different combinations.
Example: 512, 256,128....
import os
os.environ['PYTORCH_CUDA_ALLOC_CONF']='max_split_size_mb:512' #'garbage_collection_threshold:0.8,max_split_size_mb:512'

It may also help to clear the cache at startup.
import torch
#https://stackoverflow.com/questions/59129812/how-to-avoid-cuda-out-of-memory-in-pytorch
torch.cuda.empty_cache()
torch.cuda.memory_summary(device=None, abbreviated=False)
import gc
gc.collect()

FINALLY , if nothing works,  if you have a very small GPU (2gb) you have to switch it to CPU. take 3min per image but works
device = "cpu" # "cuda"
sam = sam_model_registry[KEY_model_type](checkpoint=sam_checkpoint)
sam.to(device=device)


New StdLib function getCommonEdge

Or maybe just commonEdge
Used like
const extrude001 = extrude(100, sketch001)
  |> chamfer({
       length: 30,
       tags: [
         seg01,
         commonEdge(faceTag1, faceTag2)
       ]
     }, %)

Will leverage the following engine feature that was recently merged https://github.com/KittyCAD/engine/issues/2662
Motivation: We're going to run into limitations with getAdjacentEdge style queries that are very specific to the type of geometry. edges are much more unwieldy in terms of how many get created from a given interaction
For example add one chamfer, and then chamfering one of the edges created by the chamfer creates 6 edges

But the faces that come from an operation are much more predictable, so having a mechanism that selects edges from two faces should be much more robust.
Note this complements https://github.com/KittyCAD/modeling-app/issues/4069 as commonEdge(faceTag, "END") makes no sense, which extrude "END" is being referred to here?

Btw slack thread on this
https://kittycadworkspace.slack.com/archives/C06P9L5MCUD/p1726721534218969


Missing actions when loading the plugin [2.0 alpha 1]

Only background and call node actions are visible when loading the plugin, and icons look huge

After reloading godot all appears, but icons remain giant

OS: Windows, Linux 10
Godot Version: 4 alpha 14
Dialogic Version: alpha1

so the first part where it doesn't show up is unfortunately something that cant be avoided, Godot has to be reloaded to completely load the plugin after installing and enabling it
the icons being big thing, I don't remember offhand, but I believe I remmebred seeing something about that being a Godot bug that a fix was merged recently? so hopefully the next Godot alpha should have that resolved

Maybe we can close this? The icons are fixed I think, the reload cannot be worked around I think.


[Docker Open Source] Deprecate Docker App

Tell us about your request
The Docker App project started in mid-2018 with the goal of providing a packaging solution for Compose-based applications for our enterprise customers. With the company split at the end of 2019, we found that Docker App didn’t have a clear deployment story anymore. This led us to pause the project. We would now like to formally deprecate the project.
If you are an active user of Docker App, please let us know here about what you're using it for and how it's helping you.
Which service(s) is this request for?
Docker App
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Introduce more clarity about which open source tools we are developing actively, focus on tools that are being used and have active communities.
Are you currently working around the issue?
We are not maintaining this actively, but have not made it clear what the status and roadmap is.
If you'd like to continue using CNAB for packaging your applications, check out https://porter.sh

If anyone has questions about CNAB or migrating to Porter, definitely reach out on our mailing list, slack or forum. I’m a maintainer for both and am happy to help out however I can.

Here is a tutorial that walks you through the migration. It took me about 5 minutes to swap from Docker App's bundle definition file to Porter's, so hopefully it's a smooth transition for others as well!

i really liked the idea of packaging docker-compose apps in a single image

https://github.com/docker/app has now been deprecated and archived.

are there alternatives to Docker App out there other than Porter? The project seems to be losing interest from the community.
The choice of the name "Docker App" is a bit unfortunate since it makes google search much harder.
My use case is simple: i want to distribute docker applications on low-resource devices, where i cannot afford to install K8s / Helm. I thought Docker App could be a suitable candidate .. until it was deprecated.
Which tools can i use to achieve my goal? Another option could be using Puppet / Chef, but they come in with their own complexities ...

This is also unfortunate. I quite liked the way docker app was shaping up when it was introduced as a beta feature only a few releases back.
Porter I'm said to see looks like it's really geared/focused towards public cloud and all things k8s so it's completely unsuitable for my use cases.

@prologic Porter can work with any tool or environment really. People are using it for edge/iot, on-premise bare metal, VMs, containers and yeah kuberentes.
We have mixins out of the box for some common activities, and the set of mixins represent what people felt like contributing, not the limitations of what is supported. The Docker Compose mixin provides the same functionality as Docker App. If you need more and there isn't a custom mixin, you can always edit the Dockerfile to install the tools you need and write a bash script to use it.
I don't want to derail this thread with stuff about Porter, so if anyone has questions, please reach out on our mailing list, discussion forum or slack.

@carolynvs The problem I have with this is that Porter has basically become a tool for everything and everyone 😢
As I said here this is really disappointing to see this. I already use Terraform and Packer for a lot of our Infrastructure, I don't really need yet-another Infrastructure management tool (Porter).
That being said, I have a general question. Will the Docker Hub and OCI registries continue to support CNAB bundles aswas originallyy specified by this project and the CNAB / App bundle specification? If so, I'm going to revive this project as it directly solves my needs (or it did before Docker decided to drop the ball here :/)
Kind regards

Ok. Sorry for the inconvinenece! Please unsubscribe if you are not using the current subscription.
Thanks!
Skickades från E-posthttps://go.microsoft.com/fwlink/?LinkId=550986 för Windows
Från: James @.>
Skickat: den 8 april 2022 07:41
Till: @.>
Kopia: @.***>
Ämne: Re: [docker/roadmap] [Docker Open Source] Deprecate Docker App (#209)
@carolynvshttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcarolynvs&data=04|01|bedamati.mohanty%40tietoevry.com|b4b40266b3d54fddd11e08da19225ce3|cbede638a3d9459f8f4e24ced73b4e5e|0|0|637849932616783536|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=tggk6MnyMN9czgb6GqqWMgAPJkZlC46h7GDiHtIDYn4%3D&reserved=0 The problem I have with this is that Porter has basically become a tool for everything and everyone 😢
As I said herehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdocker%2Froadmap%2Fissues%2F209%23issuecomment-894600580&data=04|01|bedamati.mohanty%40tietoevry.com|b4b40266b3d54fddd11e08da19225ce3|cbede638a3d9459f8f4e24ced73b4e5e|0|0|637849932616783536|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=imYK7R%2FSyj06dnGut7SZasJAxJG4MYvK%2FVrgzKw89uw%3D&reserved=0 this is really disappointing to see this. I already use Terraform and Packer for a lot of our Infrastructure, I don't really need yet-another Infrastructure management tool (Porter).
That being said, I have a general question. Will the Docker Hub and OCI registries continue to support CNAB bundles aswas originallyy specified by this project and the CNAB / App bundle specification? If so, I'm going to revive this project as it directly solves my needs (or it did before Docker decided to drop the ball here :/)
Kind regards
—
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdocker%2Froadmap%2Fissues%2F209%23issuecomment-1092461046&data=04|01|bedamati.mohanty%40tietoevry.com|b4b40266b3d54fddd11e08da19225ce3|cbede638a3d9459f8f4e24ced73b4e5e|0|0|637849932616783536|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=eiev7K0I5DQjW0Hl0NNawXb2%2FDzC9ix%2Fs0vZxFnghsM%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUSZYDJOIVEJ5JIVSW5NHNLVD7BGLANCNFSM427SPB3Q&data=04|01|bedamati.mohanty%40tietoevry.com|b4b40266b3d54fddd11e08da19225ce3|cbede638a3d9459f8f4e24ced73b4e5e|0|0|637849932616783536|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=7R1TETsqk9WFZAmXWx8EUUrUsXPSbmbSqK3jcgd9RSA%3D&reserved=0.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Registries that support the OCI distribution spec work with CNAB and isn't something that needs to be explicitly supported.

I would like to voice my opinion about this deprecation. I tried Porter in my scenario but it doesn't perfectly fit my need. Here is a comparison between both and why I think the deprecation is sad:

docker app is native to docker, no need for further installations especially if you only want to run docker commands, porter requires a separate installation
docker app supports swarm out of the box, porter does not have a swarm mixin as of today and you are only left with docker run or docker compose up, both do not achieve any orchestration
docker app supports all known architectures that docker itself supports, porter only supports three so it has to be run on a separate machine, something not ideal for air-gapped environments (e.g. Raspberry Pis with limited connectivity).

I would like to voice my opinion about this deprecation. I tried Porter in my scenario but it doesn't perfectly fit my need. Here is a comparison between both and why I think the deprecation is sad:

docker app is native to docker, no need for further installations especially if you only want to run docker commands, porter requires a separate installation
docker app supports swarm out of the box, porter does not have a swarm mixin as of today and you are only left with docker run or docker compose up, both do not achieve any orchestration
docker app supports all known architectures that docker itself supports, porter only supports three so it has to be run on a separate machine, something not ideal for air-gapped environments (e.g. Raspberry Pis with limited connectivity).

My sentiments exactly. I also operate several non-small Swarm clusters and Porter is not a good fit for anything I need. That being said, I think we're in a bit of a hopeless position here with this particular issue. We may just have to band-together as a community and come up with a solution that works for our specific use-cases. If you're interested, feel free to teach out to me, I'm looking to solve this for my day job's needs as well as my own personal needs and that of several (growing) communities I manage as well.

i honestly think that there is a lot of hype and research going on for cloud-level solutions (most importantly based around k8s) but the "edge" is a bit left behind.
Orchestrating containers / deployments in an low-resources, low-power based, and ethereogeneous environments (64bits, 32bits, etc..) seems not to be in the focus these days.
I find Porter useful in some of my applications but i agree with your opinion @prologic. Is anyone of you aware of not over-engineed alternatives to what we are looking for here? OR at least some project candidates?
Any blog articles on the matter?

I'm not aware of any other alternative solutions but I do plan to build one 👌

I'm not aware of any other alternative solutions but I do plan to build one 👌

If docker app is the right fit, what about taking its code outside docker core and maintaining our own plugin/cli?

I'm not aware of any other alternative solutions but I do plan to build one 👌

If docker app is the right fit, what about taking its code outside docker core and maintaining our own plugin/cli?

I haven't looked into doing that (yet); is that doable? If so, more than happy to spend my up and coming long weekend getting that codebase up-to-scratch.

I'm not aware of any other alternative solutions but I do plan to build one 👌

If docker app is the right fit, what about taking its code outside docker core and maintaining our own plugin/cli?

I haven't looked into doing that (yet); is that doable? If so, more than happy to spend my up and coming long weekend getting that codebase up-to-scratch.

I would say why not? Do you mean for licensing reasons? Maybe @chris-crone can answer?

Hi @hammady 👋
It's rewarding to hear that people love what we built with Docker App 😃
The Docker App code is Apache 2 licensed so you and others are welcome to use it so long as you respect the license. One thing to note is that you cannot use the "Docker" name for any fork as Docker Inc. has a trademark on it.

This is done, closing it out!


drivers: clock_control: nrf: Add option to use external LF source

Extended clock configuration to allow usage of external clock
source for nrf52 series.
Signed-off-by: Krzysztof Chruscinski<EMAIL_ADDRESS>

I am a little bit concerned about the following code in ext/hal/nordic/nrfx/hal/nrf_clock.h:
#if defined(NRF52810_XXAA) || \
    defined(NRF5283 2_XXAA) || defined(NRF52832_XXAB) || \
    defined(NRF52840_XXAA)
// Enable support for external LFCLK sources. Read more in the Product Specification.
#define NRF_CLOCK_USE_EXTERNAL_LFCLK_SOURCES
#endif

This shows the SOCs for which the new macros, NRF_CLOCK_LFCLK_Xtal_Low_Swing and NRF_CLOCK_LFCLK_Xtal_Full_Swing are defined. So, the Kconfig dependencies need to reflect this constraint; now there is an inconsistency, because nRF52811 is not in that list, while it is included in the nrf52 series.

If I understand correctly, if you compile for nRF52811 and set in Kconfig one of the two options, you will get a build error, no?

@ioannisg yes, that is correct but then that is a bug in nrfx. I will push nrfx guys to fix it there. Question what should we do about it here. I'm afraid that workaround code here will stay for long even after fix in nrfx. An option is to not use enum but mask directly from bitfields.

@ioannisg yes, that is correct but then that is a bug in nrfx. I will push nrfx guys to fix it there. Question what should we do about it here. I'm afraid that workaround code here will stay for long even after fix in nrfx. An option is to not use enum but mask directly from bitfields.

Well, we could also patch the nrfx, here, ourselves; is this a "standard" policy? And of course, wait to be notified about the fix from the nrfx team. This is the simplest solution, but introduces a workaround.
Not use the enum; this implies by-passing the nrfx, and use the MDK directly.
I don't know what is worse; patching or by-passing and "re-inventing" nrfx :)
After all, nrfx is here to help us....
I vote for a patch in nrfx, but we can quickly discuss it here and conclude. FYI @anangl @carlescufi

@ioannisg i've patched nrfx. I thought that it already comes through west as external repo that's why i haven't thought of patching it. Meanwhile I've already prepared patch in nrfx. so it will be in official nrfx in next release.

@nordic-krch thanks

Regarding the changes in nrfx, I'd add a note in the commit message that this is a temporary fix only, and it is supposed to be replaced by the next update of nrfx.

Yeah, good point

@anangl @ioannisg updated commit message.


[WIP] Decouple the data leaves from the rest of the tree

Placeholder WIP notes:

DiskMmapStore allows to offload its underlying store to reduce memory usage.

The use of the MT (from the rust-fil-proofs perspective) is clearly divided between the use of the leaves (its data to be encoded) and the rest of the internal nodes to generate a proof (gen_proof).

There's an asymmetry: data encoding doesn't need the other top half but proof generation does need the bottom data (from where it's starts), although only a single leave (that may be cached if the same operation is repeated or it can be hinted in advanced by the consumer).

The first iteration of this feature should provide a separation of the current MerkleTree.data in two separate Stores (or alternatively this could happen at the Store level). The  offload function should offload both sides (keeping the current behavior) but the reload should happen in separate stages, delaying reloading the top half as much as possible.

This change should be transparent to the consumer (with only additional optional hint mechanisms, that wouldn't be required for correct operation of the MT, and should only be additions —and not breaking changes— to the current API).

Related to https://github.com/filecoin-project/rust-fil-proofs/issues/481.


Add support for s390x

This is to add support for linux-s390x (Linux on Z)

I am able to run the following sample code to verify conda-mirror functionality on s390x.
conda create -y -n mirror_env
conda activate mirror_env
conda install -y conda-mirror

export CHANNEL_URL=<My_URL_with_http>

conda-mirror -vv --ssl-verify false --upstream-channel $CHANNEL_URL --target-directory $HOME/zconda-mirror --platform linux-s390x
conda-mirror -vv --ssl-verify false --upstream-channel $CHANNEL_URL --target-directory $HOME/zconda-mirror --platform noarch

conda index $HOME/zconda-mirror

Are there any non-Anaconda channels that support linux-s390x?

Thanks! Can you please add a news item: https://regro.github.io/rever-docs/news.html

@scopatz if the only place where you can get these linux on Z packages is from an official Anaconda channel, then adding this capability to conda-mirror feels like probably not a great idea, especially given the recent changes to the Anaconda TOS. Thoughts?

I don't know. It seems like anyone could set up a channel with the platform.  IIRC this is the platform name in conda itself, so the change here just makes it compatible with conda, not Anaconda per se.

@ericdill  conda is the first community that's been looked at to support s390x platform at this point in time.

I would be happy to merge this.  CI seems to be failing though...

Anaconda's defaults channel has s390x conda packages now.

Am not sure what this error in CI build means
The command "coverage report -m" exited with 0.

1.82s$ make format-check

black --check .

would reformat conda_mirror/conda_mirror.py

Oh no! 💥 💔 💥

1 file would be reformatted, 10 files would be left unchanged.

Makefile:27: recipe for target 'format-check' failed

make: *** [format-check] Error 1

The command "make format-check" exited with 2.

0.81s$ make lint

flake8

The command "make lint" exited with 0.

This means that you should format your code changes with black. Running black . locally should fix this.


Histogram with empty family labels creates unparseable metrics output

I'm loosely following the actix example to add prom metrics for my simple webapp which doesn't need additional family labels on its metrics for now. However, when I tried removing the family labels, I get unparseable output from the metrics endpoint:
$ curl localhost:8080/metrics
# HELP requests Count of requests.
# TYPE requests counter
requests_total{} 1
# HELP elapsed Histogram of elapsed.
# TYPE elapsed histogram
elapsed_sum{} 10.0
elapsed_count{} 1
elapsed_bucket{le="0.0",} 0
elapsed_bucket{le="+Inf",} 1
# EOF

The extra comma in the label list for each bucket causes this to be unparseable by prometheus, resulting in the following error:
expected label name, got "BCLOSE"

Is this intended behavior? Or is there a better way to create metrics without family labels? I boiled my issue down to a small app which I'll include below, along with a test case and patch that I've found fixes the issue for me locally. I'd be happy to submit a PR with the fix if desired.
Test app source:

use std::sync::Mutex;

use actix_web::{web, App, HttpResponse, HttpServer, Responder, Result};
use prometheus_client::encoding::text::encode;
use prometheus_client::metrics::counter::Counter;
use prometheus_client::metrics::family::Family;
use prometheus_client::metrics::histogram::{Histogram, linear_buckets};
use prometheus_client::registry::Registry;

pub struct Metrics {
    requests: Family<(), Counter>,
    elapsed: Family<(), Histogram>,
}

pub struct AppState {
    pub registry: Registry,
}

pub async fn metrics_handler(state: web::Data<Mutex<AppState>>) -> Result<HttpResponse> {
    let state = state.lock().unwrap();
    let mut body = String::new();
    encode(&mut body, &state.registry).unwrap();
    Ok(HttpResponse::Ok()
        .content_type("application/openmetrics-text; version=1.0.0; charset=utf-8")
        .body(body))
}

pub async fn some_handler(metrics: web::Data<Metrics>) -> impl Responder {
    metrics.requests.get_or_create(&()).inc();
    metrics.elapsed.get_or_create(&()).observe(10f64);
    "okay".to_string()
}

#[actix_web::main]
async fn main() -> std::io::Result<()> {
    let elapsed_hist: Family<(), Histogram> = Family::new_with_constructor(||
        Histogram::new(linear_buckets(0f64, 1f64, 1)));

    let metrics = web::Data::new(Metrics {
        requests: Family::default(),
        elapsed: elapsed_hist,
    });

    let mut state = AppState {
        registry: Registry::default(),
    };

    state
        .registry
        .register("requests", "Count of requests", metrics.requests.clone());
    state
        .registry
        .register("elapsed", "Histogram of elapsed", metrics.elapsed.clone());
    let state = web::Data::new(Mutex::new(state));

    HttpServer::new(move || {
        App::new()
            .app_data(metrics.clone())
            .app_data(state.clone())
            .service(web::resource("/metrics").route(web::get().to(metrics_handler)))
            .service(web::resource("/handler").route(web::get().to(some_handler)))
    })
        .bind(("<IP_ADDRESS>", 8080))?
        .run()
        .await
}

Output:
$ curl localhost:8080/handler; curl localhost:8080/metrics
okay# HELP requests Count of requests.
# TYPE requests counter
requests_total{} 1
# HELP elapsed Histogram of elapsed.
# TYPE elapsed histogram
elapsed_sum{} 10.0
elapsed_count{} 1
elapsed_bucket{le="0.0",} 0
elapsed_bucket{le="+Inf",} 1
# EOF

Fix patch with unit test: https://github.com/prometheus/client_rust/compare/master...tylerlevine:client_rust:histogram-empty-family-labels-fix
The idea behind the fix is that the trailing comma behind the additional labels is only added if the encoding of the family labels is non-empty. I'm not very familiar with this library so maybe there's a better approach here.
With this change the metrics output appears as expected, with no extraneous commas in the bucket label lists:
$ curl localhost:8080/handler; curl localhost:8080/metrics
okay# HELP requests Count of requests.
# TYPE requests counter
requests_total{} 1
# HELP elapsed Histogram of elapsed.
# TYPE elapsed histogram
elapsed_sum{} 10.0
elapsed_count{} 1
elapsed_bucket{le="0.0"} 0
elapsed_bucket{le="+Inf"} 1
# EOF

Thank you for digging into this. Let's discuss on #175.


recovery words FAQ - new screen

What would you like to be added:
From Create Guidelines screen - View Recovery words
Some things to consider: It should be reusable component (as it will be used on other screens). Also, it  should be a screen that can be called from anywhere (as we will consolidate them from Settings -> Knowledge Base).

[x] Accordion from description
[x] German translations

Why is this needed:
https://www.figma.com/proto/SDIpZciuxJlUf4xf8yheiY/Light-Wallet?page-id=287%3A11410&node-id=642%3A17182&viewport=241%2C48%2C0.8&scaling=scale-down&starting-point-node-id=642%3A17235&show-proto-sidebar=1

Acceptance Criteria: Updated design for Recovery Word FAQ
Android:

[ ] Check for any typo

iOS:

[ ] Check for any typo


Allow Civil Twilight duration setting

Hello, I use Small Time with Simple Calendar running for have seasonal changes in sunrise and sunset times, day by day.
I would like to set the duration of the civil twilight, the time before dawn or after dusk in which is possible to see without artificial lights.
Currently I could mess with the Darkness threshold for toggling Unrestricted Vision Range, but, IMHO, it's not what I would like to see in action.
The option I suggest is kinda this:
Civil Twilight enable/disable
Civil Twilight duration n minutes
E.g. if enabled and its duration set to 30 minutes, then, after sunset, Small Time will begin to raise the darkness value and after 30 minutes it will reach the threshold value for disabling Unrestricted Vision Range.
Viceversa for the dawn.
That way you could have neverending twilights like the ones that happens around the Poles in summer and "normal" ones.
Thank you.

Hi there! So this sounds like a neat idea, but it's definitely beyond my intended scope for this module. If you're into implementing it and submitting a PR, I'd consider incorporating it.

Hi there! So this sounds like a neat idea, but it's definitely beyond my intended scope for this module. If you're into implementing it and submitting a PR, I'd consider incorporating it.

I'm studying JS, so in the future, this will be definitely a thing I would like to develop. Thank you for your answer.


Msw 100766496 update email app text

Update Email Notification With App Name

Update and Refactor Mailer
Update SMS Module
Add Notification Class

[Finished: #100766496]

@ericcf Thanks!

@michaelwehrley Nice job on the refactoring. Your code is much more cohesive and less tightly coupled with your Notification class abstraction.


sshfuse commands are not allowed in new version

The following command is not allowed any more:
"cmd": "sshfs xxx@xxx.xxx.com:/home/user/public_html/ ~/MountingPoints/Servername -olocal,reconnect,defer_permissions,noappledouble,negative_vncache,volname=Servername; exit",

Are you getting any error messages?

@andreasisaak Regarding this issue I think its related to #153 are you getting the same error as #153 ?

This should be fixed in release v.1.2.6 pull #165


CIAC-12067

Status
Ready/In Progress/In Hold (Reason for hold)
Related Content Pull Request
Related PR: link to the PR at demisto/content
Related Issues
Related: https://jira-dc.paloaltonetworks.com/browse/CIAC-12067
Description
A few sentences describing the overall goals of the pull request's commits.

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

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


DllNotFoundException for gdal_wrap in Unity with GDAL Package

Environment:

Unity version: [2022.3.16f1]
Operating System: [Windows 11]
Visual Studio version [Visual Studio 2022]

Issue Description:
I am encountering a DllNotFoundException when trying to use the GDAL package in Unity. The specific error is for gdal_wrap. This issue arises when attempting to initialize GDAL using Gdal.AllRegister(); in a C# script.
Error Message:
DllNotFoundException: gdal_wrap assembly: type: member:(null)
OSGeo.GDAL.GdalPINVOKE+SWIGExceptionHelper..cctor () (at ./Library/PackageCache/com.virgis.gdal@e85ead4664/Runtime/Scripts/gdal/GdalPINVOKE.cs:139)
Rethrow as TypeInitializationException: The type initializer for 'SWIGExceptionHelper' threw an exception.
OSGeo.GDAL.GdalPINVOKE..cctor () (at ./Library/PackageCache/com.virgis.gdal@e85ead4664/Runtime/Scripts/gdal/GdalPINVOKE.cs:159)
Rethrow as TypeInitializationException: The type initializer for 'OSGeo.GDAL.GdalPINVOKE' threw an exception.
OSGeo.GDAL.Gdal.AllRegister () (at ./Library/PackageCache/com.virgis.gdal@e85ead4664/Runtime/Scripts/gdal/Gdal.cs:861)
S57Reader.Start () (at Assets/myscript.cs:10)
Steps to Reproduce:

Installed the GDAL package in Unity via Unity Package Manager and the git link after adding scopedRegistries to manifest.json.
Created a C# script to utilize GDAL functionalities.
Encountered the error upon running the Unity scene with the script.

I would appreciate any guidance or suggestions to resolve this issue. Thank you!

Update: Issue Resolved
I wanted to provide an update on this issue. After further investigation, I discovered that the problem was related to the Conda installation. Once I addressed the Conda setup, the DllNotFoundException for gdal_wrap was resolved.

Thanks for the issue and the update. I was about to say that this issue is almost certainly due to the conda configuration.
Using Conda does introduce some complexity - but it solves even more problems with dependencies with GDAL and with updates so it is worth it :)
Thanks for using the package


Update attime to use timezones properly

The problem: parseTimeReference is not time-zone aware, preventing users from rendering graphs with their requested time zone on the x-axis properly. See #1407 for more.
The yak: parseTimeReference does some ... timezone unfriendly ... manipulations of a naive time object, preventing us from simply passing tzinfo into it in lots of edge cases.
The solution: make parseTimeReference internally work in UTC, and then have parseATTime localize the output into the requested (or default) timezone. (as recommended by http://pythonhosted.org/pytz/#problems-with-localtime)

Hrm. Tests run differently on Travis. Will investigate.
AssertionError: datetime.datetime(2015, 3, 8, 2, 0, tzinfo=<DstTzInfo 'America/Los_Angeles' LMT-1 day, 16:07:00 STD>)
!=
datetime.datetime(2015, 3, 8, 3, 0, tzinfo=<DstTzInfo 'America/Los_Angeles' PDT-1 day, 17:00:00 DST>)

@mleinart @obfuscurity @deniszh @brutasse - this is tidied, tests updated, and ready for review.

We're now running this branch in our environment, and I can confirm it's working as intended :zap:

Nice, thanks @bmhatfield! :icecream:


Fix URL for Windows installation guide

The current URL is 404.

Thank you, this was fixed with another incorrect link as well. We also updated the documentation site to redirect on the broken URL.


Allow handles with 'copy' fate to persist to firebase

Ensure that cloning a handle into a firebase-collection persists.
re-add btoa/atob on firebase keys to prevent invalid keys being generated.

Fixes #1699


POC for the Slack managed data source

In this POC we implement most of the things discussed in the Managed Data sources Design Doc.

Add a "add slack data source" button in the data sources main page.
Support for the Oauth flow using nango.dev
Creation of the managed data source after coming back from the OAuth flow by calling POST /api/data_source/[user]/managed, which does:

Create a data source with pre-filled parameters
Create a system level API key
Trigger a Slack sync by enqueuing a Temporal job

There are a bunch of things to know :

I added nodemon and ts-node to this project because this is how temporal execute the typescript code. Until today we were executing everything using the nextjs wrapper, which is not compatible. I followed a Temporal integration guide specifically designed for our context (running a Temporal workflow in a nextjs project).
I tried to maintain a clear separation of concerns between the existing front code base and the front/connectors code. front/connectors defines clear and simple interface and need just that to work. It does not require anything from ../

This looks great! Will review more thoroughly and leave comments tomorrow 🔥🔥🔥

Let’s close?


Random input Step MVP: Get through a simple form by generating random input

MVP:

[x] input field
[x] textarea
[x] checkbox
[x] radio button
[x] continue button

Stretch:

[x] date field
[x] number field
[x] Custom birthdate
[x] Custom three-part-date

Others?
Edit:
(#591)
Left to do for MVP:

[x] Give each screenshots folder a time-stamped name in case the dev gets clever and use the same Scenario to run multiple randomized tests.
[x] Make sure we can fail on actual errors - situations where there's a complete page or server error. Includes making an interview to test that is missing a variable definition or something.

MVP closed by #591


include command-line entry points in pyproject.toml

Short description of the changes:
Just a new section in the pyproject.toml for custom terminal commands
Check list for the pull request

[ ] I have added tests for my changes
[x] I have updated the documentation accordingly

Check list for the reviewer

[ ] I have read the [CONTRIBUTING]
[ ] I have verified the proposed changes
[ ] best software practices

[ ] all internal functions have an underbar, as is python standard
[ ] clearly named variables (better to be verbose in variable names)
[ ] code comments explaining the intent of code blocks

[ ] All the tests are passing
[ ] The documentation is up to date
[ ] code comments added when explaining intent

Manual test for the reviewer

References

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 3.70%. Comparing base (5a8cdce) to head (f18429c).

Additional details and impacted files
@@          Coverage Diff          @@
##            main     #12   +/-   ##
=====================================
  Coverage   3.70%   3.70%
=====================================
  Files          5       5
  Lines        135     135
=====================================
  Hits           5       5
  Misses       130     130

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


Docs build on docs.rs is failing

See example failure here: https://docs.rs/crate/ibc-types/0.6.1/builds/915166
[INFO] [stderr] warning: Target filter specified, but no targets matched. This is a no-op
[INFO] [stderr]     Checking bytes v1.5.0
[INFO] [stderr]     Checking serde_bytes v0.11.12
[INFO] [stderr]     Checking serde_json v1.0.107
[INFO] [stderr]     Checking ed25519-consensus v2.1.0
[INFO] [stderr]    Compiling safe-proc-macro2 v1.0.36
[INFO] [stderr]    Compiling crunchy v0.2.2
[INFO] [stderr] error[E0422]: cannot find struct, variant or union type `LineColumn` in crate `proc_macro`
[INFO] [stderr]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-6f17d22bba15001f/safe-proc-macro2-1.0.36/src/wrapper.rs:485:33
[INFO] [stderr]     |
[INFO] [stderr] 485 |                 let proc_macro::LineColumn { line, column } = s.start();
[INFO] [stderr]     |                                 ^^^^^^^^^^ not found in `proc_macro`
[INFO] [stderr]     |
[INFO] [stderr] help: consider importing one of these items
[INFO] [stderr]     |
[INFO] [stderr] 1   + use crate::LineColumn;
[INFO] [stderr]     |
[INFO] [stderr] 1   + use crate::fallback::LineColumn;
[INFO] [stderr]     |
[INFO] [stderr] help: if you import `LineColumn`, refer to it directly
[INFO] [stderr]     |
[INFO] [stderr] 485 -                 let proc_macro::LineColumn { line, column } = s.start();
[INFO] [stderr] 485 +                 let LineColumn { line, column } = s.start();
[INFO] [stderr]     |
[INFO] [stderr]

Looks like we should bump proc-macro2 within the deps.

PR should resolve it. Looks like the docs.rs build process is using a version of proc-macro2 that's a bit too old. We don't commit lockfiles for these libraries, so instead I added a recent version of proc-macro2 to the deps of ibc-types-core-channel. However, we won't know the problem is fixed until we post another release, thereby triggering the docs.rs build.

Still failing:

Hey, this is coming from safe-proc-macro2(dependency of safe-regex) which was using removed proc_macro::LineColumn. It is not related to proc-macro2.
The author has made a new release. If you're not using cargo.lock, the next release should publish just fine on docs.rs. Otherwise just do a cargo update to fetch the latest safe-proc-macro2.

Thanks for explaining! We're not using a lockfile, since these crates are libraries, not binaries, and that's what the cargo book recommends. It's not clear to me how to force docs.rs to run cargo update in the build environment, but I'll look into that next.

No worries for lockfile. I just didn't check if you're using it or not. But in the downstream, if you have a binary crate with rust docs, then you have to run cargo update to update its lockfile.
For the docs.rs, crate-owners can not trigger a fresh cargo doc build for a failed one ... yet. So you have to wait till the next release on crates-io.

Docs no longer failing, closing.


[9.x] Added withoutCount method in Eloquent Builder

Added withoutCount method in Eloquent Builder
Sometime we have to ignore the withCount property in runtime that's why I've added a method in eloquent builder which is withoutCount
Usage

$categories = Category::latest()->withoutCount('articles')->get();
// or
$categories = Category::latest()->withoutCount('articles', 'votes')->get();
// or
$categories = Category::latest()->withoutCount(['articles', 'votes'])->get();

Need to update this PR more, so I just draft this.

Is there any other alternative to run a Model query without the withCount ? For the with we can use query()->setEagerLoads([]).


Running dbt w/ multiple threads on Redshift slow due to exclusive lock

Describe the bug
This issues is similar to #3112, but not limited to only RA3 nodes or views.
We are running our dbt pipeline in our company's quite loaded Redshift cluster with 'regular' DC2 nodes, where DDL may take quite a bit of time to run especially on Monday mornings. With the intention of reducing our lead time we bumped up the number of dbt threads to run more of our base relations (which included views, tables, incrementals) in parallel as they were the main bottleneck. By doing this we found out not only that we didn't get much of a speedup, but also we observed a quite interesting behaviour on the running times of the models, where a large amount of models started at the same time but finished in a sequential fashion (picture below). There was also no correlation between the number of rows/table size and the running time here, some of the slowest tables had less than 10 fields and a couple thousand rows, and incremental tables happened to consistently be the fastest despite usually having to load more data than regular tables (and of course views).
Digging a bit deeper into this we found out in Redshift logs that there was a huge time gap between any 'DROP' transaction and the previous one in the same model. By checking Redshift connection's implementation we found out that class RedshiftConnectionManager implements an process-level exclusive lock to avoid DROP ... CASCADE conflicts, which essentially prevents two models running in different threads as part of the same dbt run to execute DROP transactions at the same time. Because running a table/view model requires several DROP operations to clean backup and temporary relations and as no two models can DROP at the same time because of the exclusive lock, it seems that models running in parallel can (very often actually) spend a significant amount of time competing among themselves to acquire the lock several times, which would explain the pattern in the model execution finish times. Also, because incremental models require fewer DROPs, it would explain why they finish faster.
To test this we ran each model in parallel in separate dbt run commands (using Airflow) and the issue disappeared completely, with models running much faster and taking longer when they had to move more data.
Steps To Reproduce
On a Redshift cluster execute dbt run in multiple threads in a project with many relations. Might require a relatively large number of threads or a relatively loaded cluster to observe it properly.
Expected behavior
Most relations finish at roughly the same time, taking longer depending on the table size
Potential workarounds
In our case we dealt with this by dramatically reducing the number of table/views and using more ephemeral models, but this is not ideal (forced us to make our pipeline much leaner though) as we still can observe this happening especially at the beginning of the pipeline where more models are running in parallel. As the lock exists to prevent concurrent delete issues I'm not sure how this could be averted, but an override option would be nice for 'safe' sections of the pipeline that could run without the lock (for example all our views are late binding and we do not have additional objects depending on the pipeline relations)
Screenshots and log output
Model execution time gantt chart obtained by parsing the output of dbt run when running multiple threads. x-axis is time.

System information
Which database are you using dbt with?

[ ] postgres
[x] redshift
[ ] bigquery
[ ] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
installed version: 0.18.1
   latest version: 0.19.0

Plugins:
  - bigquery: 0.18.1
  - postgres: 0.18.1
  - redshift: 0.18.1
  - snowflake: 0.18.1

The operating system you're using:
Ubuntu 20.04
The output of python --version:
Python 3.7.5
Additional context
N/A

@Beetelbrox Thanks for the detailed description. Overall I agree with your assessment that this seems closely related to the one in #3112, and it's quite possible that workarounds (= hacks) we develop for one issue may serve to ameliorate the other.

To test this we ran each model in parallel in separate dbt run commands (using Airflow) and the issue disappeared completely, with models running much faster and taking longer when they had to move more data.

This is the bit I find surprising. Why would dbt's lock-and-drop transactions compete only when running across multiple threads within the same invocation, but not when running across multiple different invocations (as triggered by Airflow)?

As the lock exists to prevent concurrent delete issues I'm not sure how this could be averted, but an override option would be nice for 'safe' sections of the pipeline that could run without the lock (for example all our views are late binding and we do not have additional objects depending on the pipeline relations)

Yes, I think a possible resolution here is for dbt to differentiate between relations requiring a safe drop transaction—because they have bound dependent views, or because someone could be querying them concurrently—and relations that have no dependencies, are unlikely to be queried, and can be dropped simply (no cascade) and without opening a new locking transaction.
The proposed remedy for #3112 is to try this for the temp and backup relations, which are necessary for the atomic rename-swap materialization logic but not used for anything else. While not removing the need for locking drop-cascade transactions entirely, it would be a definitely improvement.

Model execution time gantt chart obtained by parsing the output of dbt run when running multiple threads. x-axis is time.

This is a really cool visualization! Could you help me understand what exactly you're seeing here? Are you in fact running dbt with dozens of threads? While it depends on your cluster / WLM settings, I know that Redshift only supports a set number of concurrent connections, so many of those may be queued/delayed for other reasons.
I'm happy to keep this issue open, but at this point I'm reading it as a clarification of the impact of #3112, rather than a recasting of the problem or a reason to think differently about proposed solutions (except that both view and table materializations are implicated). Are you thinking about this differently?

@jtcohen6 Thanks!

This is the bit I find surprising. Why would dbt's lock-and-drop transactions compete only when running across multiple threads within the same invocation, but not when running across multiple different invocations (as triggered by Airflow)?

As far as I can tell, the drop_lock in dbt is implemented as a process-wide lock using the python multiprocessing package. Unless I'm missing some detail on how it works, this has the effect of different threads in the same invocation (aka process) will be competing for acquiring the parent process' single lock. Running each model in separate dbt runs (eg via airflow) concurrently will spawn different processes with a different lock for each one, hence the different behaviour.

Yes, I think a possible resolution here is for dbt to differentiate between relations requiring a safe drop transaction—because they have bound dependent views, or because someone could be querying them concurrently—and relations that have no dependencies, are unlikely to be queried, and can be dropped simply (no cascade) and without opening a new locking transaction.

The proposed remedy for #3112 is to try this for the temp and backup relations, which are necessary for the atomic rename-swap materialization logic but not used for anything else. While not removing the need for locking drop-cascade transactions entirely, it would be a definitely improvement.
Indeed, we've observed that every drop takes a while so every bit helps!

This is a really cool visualization! Could you help me understand what exactly you're seeing here? Are you in fact running dbt with dozens of threads? While it depends on your cluster / WLM settings, I know that Redshift only supports a set number of concurrent connections, so many of those may be queued/delayed for other reasons.

Oops, sorry for the lack of clarification here. This is a Gantt chart of the dbt model execution time for each one of our models executed concurrently, x axis is time, y axis are the models. Timestamps for start and end were parsed out from the dbt run output. We can see how we have a bunch of models that start at the same time and some of them take much longer to load than others, the interesting part here is that the longer-running models are all small table models while the fastest ones are incrementals that have to load much more data at each incremental batch.
Regarding the level of concurrency, we found out that it was taking a long time just to run all of them with 4/8 threads, so we tried with 1 thread/source model (around 50) and then observed this behaviour. Just for the records, for the rest of the pipeline we use 8 threads.
Regarding the WLM & other redshift workload configs we initially thought them to be the source of the slowness, but we checked and we had 0 time in the various queues. All that Redshift registered was a very long gap between each DROP transaction submission and the previous one.

I'm happy to keep this issue open, but at this point I'm reading it as a clarification of the impact of #3112, rather than a recasting of the problem or a reason to think differently about proposed solutions (except that both view and table materializations are implicated). Are you thinking about this differently?

Indeed, at the moment of the initial writing the conversation in #3112 had not yet progressed to the lock situation and was only restricted to views, so I wanted add our findings too. Feel free to close it if appropriate. Thanks a lot!

I'm going to consider this resolved by #3468


[Subtask] Display information of all application through Cli

Code of Conduct

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

Search before asking

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

Describe the subtask
Display the information of all servers through the Cli command such as uniffle-cli --list application
Parent issue
#758
Are you willing to submit PR?

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

@smallzhongfeng Can you assign this issue to me? Thank you very much!

@smallzhongfeng Can you assign this issue to me? Thank you very much!

We usually use rest api to control admin service. If we need add api, we would better add rest api. Could we keep consistent with other operation. You can refer to https://github.com/apache/incubator-uniffle/pull/684

@jerqi Thank you very much for your suggestion, I will finish this pr as soon as possible. Sorry for the late reply.


docs(quickstart): add a section to installing typings manually

We can add this warning until we can move to TS2 and @types/
/cc @naomiblack

On master


FileNotFoundError in the normal inference

Hi, the FileNotFoundError is raised when I infer the FLARE22 image with normal mode (the fast mode works smoothly). Seems like some intermediate files are failed to save, do you have any ideas of this issue?
Here is the command I used:
TotalSegmentator -i FLARE22/imagesTr/FLARE22_Tr_0039_0000.nii.gz -o total_pred/FLARE22/FLARE22_Tr_0039_0000_normal

Here is the log:
Resampling...
Predicting part 0 of 5 ...
Traceback (most recent call last):
  File "xxx/anaconda3/envs/totalseg/bin/TotalSegmentator", line 122, in <module>
    main()
  File "xxx/anaconda3/envs/totalseg/bin/TotalSegmentator", line 102, in main
    seg = nnUNet_predict_image(args.input, args.output, task_id, model="3d_fullres", folds=folds,
  File "xxx/anaconda3/envs/totalseg/lib/python3.9/site-packages/totalsegmentator/nnunet.py", line 154, in nnUNet_predict_image
    (tmp_dir / "s01.nii.gz").rename(tmp_dir / "parts" / f"s01_{tid}.nii.gz")
  File "xxx/anaconda3/envs/totalseg/lib/python3.9/pathlib.py", line 1382, in rename
    self._accessor.rename(self, target)
FileNotFoundError: [Errno 2] No such file or directory: 'xxx/partial_test/FLARE22/imagesTr/nnunet_tmp_IOZ1UFCG/s01.nii.gz' -> 'xxx/partial_test/FLARE22/imagesTr/nnunet_tmp_IOZ1UFCG/parts/s01_251.nii.gz'

The test file can be downloaded from https://drive.google.com/file/d/1URovTKT_icuMNeNmMvHOfr4SW9YBz-pK/view?usp=sharing

The problem is related to this issue: https://github.com/SimpleITK/SimpleITK/issues/1433
You can see the error message by turning on the verbose mode in TotalSegmentator using the flag -v.
You can solve it by using an older version of SimpleITK:
pip install SimpleITK==2.0.2

Unfortunately SimpleITK did not publish a fix for this yet.

i run pip install SimpleITK==2.0.2;but the same bug: 'D:\Code\TotalSegmentator\nnunet_tmp_MKQI\s01.nii.gz' -> 'D:\Code\TotalSegmentator\nnunet_tmp_MKQI\parts\s01_251.nii.gz'
i set      num_threads_preprocessing = 0
num_threads_nifti_save = 1

Could you run it again with the option -v and post the complete standard output of the command as well as the complete error message?

i run it again with option -v,i run the ,\TotalSegmentator.py in win10 and here is the com:
(seq) D:\Code\TotalSegmentator>python TotalSegmentator.py -i D:\Code\TotalSegmentator\ct.nii.gz -o segmentations -v
Resampling...
from shape (294, 192, 179) to shape (294, 192, 179)
Predicting part 0 of 5 ...
using model stored in  C:\Users\YangXuesong.totalsegmentator\nnunet\results\nnUNet\3d_fullres\Task251_TotalSegmentator_part1_organs_1139subj\nnUNetTrainerV2_ep4000_nomirror__nnUNetPlansv2.1
This model expects 1 input modalities for each image
Found 1 unique case ids, here are some examples: ['s01']
If they don't look right, make sure to double check your filenames. They must end with 0000.nii.gz etc
number of cases: 1
number of cases that still need to be predicted: 1
emptying cuda cache
loading parameters for folds, [0]
using the following model files:  ['C:\Users\YangXuesong\.totalsegmentator\nnunet\results\nnUNet\3d_fullres\Task251_TotalSegmentator_part1_organs_1139subj\nnUNetTrainerV2_ep4000_nomirror__nnUNetPlansv2.1\fold_0\model_final_checkpoint.model']
starting preprocessing generator
starting prediction...
inference done. Now waiting for the segmentation export to finish...
WARNING! Cannot run postprocessing because the postprocessing file is missing. Make sure to run consolidate_folds in the output folder of the model first!
The folder you need to run this in is C:\Users\YangXuesong.totalsegmentator\nnunet\results\nnUNet\3d_fullres\Task251_TotalSegmentator_part1_organs_1139subj\nnUNetTrainerV2_ep4000_nomirror__nnUNetPlansv2.1
Traceback (most recent call last):
File "TotalSegmentator.py", line 123, in
main()
File "TotalSegmentator.py", line 103, in main
seg = nnUNet_predict_image(args.input, args.output, task_id, model="3d_fullres", folds=folds,
File "D:\Code\TotalSegmentator\totalsegmentator\nnunet.py", line 156, in nnUNet_predict_image
(tmp_dir / "s01.nii.gz").rename(tmp_dir / "parts" / f"s01{tid}.nii.gz")
File "D:\ProgramData\Anaconda3\envs\seq\lib\pathlib.py", line 1359, in rename
self._accessor.rename(self, target)
FileNotFoundError: [WinError 2] 系统找不到指定的文件。: 'D:\Code\TotalSegmentator\nnunet_tmp_4KQZ\s01.nii.gz' -> 'D:\Code\TotalSegmentator\nnunet_tmp_4KQZ\parts\s01_251.nii.gz'

Unfortunately TotalSegmentator does not work on Windows. You have to use Linux. Or you can try our online tool: https://totalsegmentator.com/

ok，i konw the BUG，its the preprocess_multithreaded，Because win10 does not support multithreading well。i use this
“if 'win' in sys.platform:
# fix for pickling errors on Windows platforms
import pathos
Process = pathos.helpers.mp.Process
Queue = pathos.helpers.mp.Queue”
put it into nnunet\inference\predict.py.it works.
Thank you for your work. It's very helpful to be me

ok，i konw the BUG，its the preprocess_multithreaded，Because win10 does not support multithreading well。i use this
if 'win' in sys.platform:
#fix for windows platform
import pathos
    Process = pathos.helpers.mp.Process
    Queue = pathos.helpers.mp.Queue

@CedarYang  Could you tell me exactly where to put this code in nnunet\inference\predict.py ?
Thank you.

Thank you  @CedarYang. Very helpful for Windows users.


[WIP] Mark non-rails workers as stopped

Currently any worker using the 'run_single_worker' script has an ensure that destroy the current record, but as we add workers that don't use run_single_worker we need to be able to delete worker records when those services exit.
If a non-rails worker record is "stopping" and the underlying pod/process/service is gone then we can mark the worker record as "stopped" and allow it to be cleaned up normally.
Required for https://github.com/ManageIQ/manageiq-providers-embedded_terraform/pull/2
Depends on:

[x] https://github.com/ManageIQ/manageiq/pull/22942

Merged  #22942; can you rebase?


Disable page and crop orientation

Hi @felixdittrich92 ,
I've merged your changes from disable orient prototype and slightly modified the function extract_rcrops which works better according to some of my internal tests.

Hi @milosacimovic :wave:
Thanks i will have a look asap :+1:

API test fail is fine will success after merge

@milosacimovic Could you fix the mypy issue please https://github.com/mindee/doctr/actions/runs/11067610457/job/30751370517?pr=1735

Overwrites: #1723

CC @nikokks
Using now with the ocr_predictor and assume_straight_pages=False and/or straighten_pages=True and/or detect_orientation
disable_crop_orientation=True,  # if all the text on doc is only horizontal
disable_page_orientation=True, # if your doc contains only small rotations (~ -45 -45)

Should also speed up processing a lot :)