Relocate vdb binaries to openvdb_cmd root directory

As discussed, this moves all the binaries out into a new root directory - I've called this openvdb_cmd to match the previous name, but I don't mind changing to openvdb_binaries, openvdb_bin or something else entirely.
I also dropped the 'open' prefix in the file names and renamed the files main.cc (ie openvdb_print.cc => vdb_print/main.cc). Now all the viewer files live in the same directory as the main.cc.

lgtm! A few related test failures need fixing

Approved - is there any reason you didn't move the vdb_ax command line?

No good reason, it was just a little more complicated to move. I've moved it now as part of this PR, but if you can just verify that the (small) change in behaviour is acceptable? Now, the ax binary is only built if OPENVDB_BUILD_BINARIES=ON and OPENVDB_BUILD_AX_BINARIES=ON, whereas previously it only required the latter.

Looks good to me. If you feel like it, you could deprecate OPENVDB_BUILD_AX_BINARIES and alias it to a new  OPENVDB_BUILD_VDB_AX which matches the format of the others.
Looks like the mac tests are failing as the AX builds now build all the binaries (they're all always on at the bottom of build.sh and "bin" just turns on the parent option). No easy solution here - probably the most correct one is to add each binary as its own component in build.sh. Maybe we should deprecate the OPENVDB_BUILD_BINARIES option as well? It dosn't really do much now that vdb_print is the only one enabled.

Yeah that seems okay to change to me too

Updated this to pull in latest changes to master, this should be good to go in as-is, but here are the issues I ran into when attempting to remove OPENVDB_BUILD_BINARIES:

Early exit when nothing to build - either needs to check each binary in turn or we remove this check altogether.  (https://github.com/AcademySoftwareFoundation/openvdb/blob/master/CMakeLists.txt#L429).
If neither binaries or unit tests are built, can still fail on looking for a custom allocator that is not required (https://github.com/AcademySoftwareFoundation/openvdb/blob/master/CMakeLists.txt#L501).
May need to check all the available binaries to know if we need to find openvdb instead of building core lib ourselves (https://github.com/AcademySoftwareFoundation/openvdb/blob/master/CMakeLists.txt#L552).

Perhaps one way around these issues is to make it so that the vdb_print binary cannot be disabled (or otherwise add a trivial vdb hello world binary for this purpose?). It's small and self-contained but means the answer to the above three questions is simple. We are always building something, a custom allocator is always required and we always need a core lib to be built or available?

Early exit when nothing to build - either needs to check each binary in turn or we remove this check altogether.

We need to early exit if you just want to build the docs

If neither binaries or unit tests are built, can still fail on looking for a custom allocator that is not required
May need to check all the available binaries to know if we need to find openvdb instead of building core lib ourselves

If we checked for every binary this would be fine, correct? If we don't want to do this manually we could do something like:
get_cmake_property(ALL_VARS VARIABLES)
list(FILTER ALL_VARS INCLUDE REGEX "OPENVDB_BUILD_VDB_.*")
if(ALL_VARS)
  foreach(VAR ${ALL_VARS})
    message(STATUS "${VAR} ${${VAR}}")
    if(${${VAR}})
      set(SOME_VDB_BINARY_COMMAND_HAS_BEEN_ENABLED ON)
    endif()
  endforeach()
endif()

Otherwise (and I think this is more correct albiet more duplication) we should move the malloc/find(OPENVDB) logic into all sub components that needs it. That means the python, houdini and ax core libs would all do something like:
# if openvdb has not been built and the imported OpenVDB has not already been found, find it
if(NOT TARGET openvdb AND NOT TARGET OpenVDB)
  find_package(OpenVDB REQUIRED)
endif()

Not ideal, I even sort of prefer the first one though that has its own problems (-DOPENVDB_BUILD_VDB_NON_EXISTANT_BINARY=ON will trigger it)

Merged as-is. We can come back to trying to remove OPENVDB_BUILD_BINARIES in a separate effort.


Fixes for ghc 8.0.1

@pxqr @sergv Any update on this?

Nothing from me: the PR's still unmerged out there, the package appears abandoned FWIW.
On 9 July 2018 19:15:15 CEST, Dmitry Malikov<EMAIL_ADDRESS>wrote:

@pxqr @sergv Any update on this?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/pxqr/bencoding/pull/7#issuecomment-403552812

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

@sergv could you please proceed with 'Taking over a package' procedure then?

Sure, I'll initiate that this weekend (sorry, cannot start earlier).
On 9 July 2018 21:35:10 CEST, Dmitry Malikov<EMAIL_ADDRESS>wrote:

@sergv could you please proceed with 'Taking over a package' procedure
then?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/pxqr/bencoding/pull/7#issuecomment-403595080

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

I've made modifications fixing even more GHC versions here https://github.com/sergv/bencoding/pull/1

I've been added as a maintainer and have uploaded new version incorporating all the fixes http://hackage.haskell.org/package/bencoding-<IP_ADDRESS>. Please refer to https://github.com/sergv/bencoding to report any issues or submit a PR.


contrib/lite: spelling/code tweaks

will fix the test in a sec

fixed test, rebased to match upstream

@gunan removed issue introduced by rebase, please run test again 🎉


Get the identity server up and running

Should provide a hook to the web client and command line for user signup.

Partially done in #13. Will follow up with signup routine via CLI.


Update index.md

Updating reference of s3_force_path_style to s3_use_path_style as per deprecation here:
https://github.com/hashicorp/terraform-provider-aws/issues/23026
https://github.com/hashicorp/terraform-provider-aws/pull/23055

It has been fixed with: https://github.com/localstack/docs/pull/372
I'm sorry, I didn't notice your PR initially 😞

no problems @HarshCasper!


Mac issue with EF update

Got the following while trying to run dotnet ef database update
System.PlatformNotSupportedException: LocalDB is not supported on this platform.

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

ID: 6719f08e-3bd7-dc1a-71df-f2ef9fbca9d8
Version Independent ID: 7096fdb3-612e-9e00-bd0b-8ea4886a09ce
Content: Add a model to a Razor Pages app in ASP.NET Core
Content Source: aspnetcore/tutorials/razor-pages/model.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@phi1ipp 	great error message. You need to follow the Mac instructions which use SQLite.


Groupings-892

This is for adding padding above the reset grouping column in a grouping's preferences. This code is the same as the code that was pushed to dev-2-2-0 already for the same purpose.

likely this will also need to be ported to dev-2-2-0.

You should use Bootstrap 4, eh.

Please create another ticket referencing this one and requesting that the next iteration of the code utilize bootstrap 4.  Thanks.

I plan on creating a new ticket to have a team member perform a comprehensive review of our code to see where we aren't, but should be using bootstrap.

You just need to put something like this in the class attribute: pt-4
See here: https://getbootstrap.com/docs/4.5/utilities/spacing/


Add actual support for restarting/reloading units, change detection, dry mode

Can I get another force push to run drone here?


Slow down YouTube video payback speed

sloooooow video playback speeeeeed

more ideas:

random speed value
keep re-applying the speed, so they don't change it in the player


Created simple documentation by following the template from Catlab to compile docstrings

We need more docstrings.
Run make.jl to generate the site.
I think it can be deployed on github.io similar to how Catlab does it.

Squashed commits this time instead of having 2 tiny ones, hooray.

Note, at present, this pulls from the system's version of StockFlow.jl.  To use the particular one at the repository, replace the using StockFlow with include("../src/StockFlow.jl") using .StockFlow


[release/0.8] go.mod: Bump ttrpc to 1.1.0

This tag contains a fix for a deadlock we'd observed on Windows when multiple
requests were made in parallel. https://github.com/containerd/ttrpc/pull/94

Seems like a lot of dep changes. Was this just from running go get<EMAIL_ADDRESS>go mod tidy, go mod vendor?

@kevpar Agreed.. but yes those were the steps.

Why wasn't the other PR this long?

https://github.com/microsoft/hcsshim/blob/d726877c46badb4e9b898982c763901f171e39da/vendor/modules.txt#L147-L177
Looks like google.golang.org/protobuf wasn't used somehow on release/0.8. They're already there on master https://github.com/microsoft/hcsshim/blob/master/vendor/modules.txt#L218-L248. That's the majority of the new additions.

@dcantah maybe do a separate PR for that change then so that this PR can stay relatively the same as the one to the main branch?

@katiewasnothere It was added because ctrd uses it apparently. So it was removed when we reverted our ctrd dep to 1.4.x for this branch. https://github.com/microsoft/hcsshim/commit/07d25d4a51fb95c9d493cc1ef507be93183fae3d


Attk menu fix

Fixed magical attacks clash with ranged weapon attacks on Attacks dialog.
Silenced invalid Style search logs.

Dependent on Pull Request #1852 Going live


make each step a folder

@thibaulttabarin suggested creating a folder for stage 1 (image selection), stage 2 (workflow), etc.

pull request
https://github.com/hdr-bgnn/minnowTraits/pull/17


Add a release job to CI

The new job must:

Run on a git-tag-push
Sign generated artifacts
Upload outputs to S3 (using the same paths as the old CLI? need to check with product)

Ideally, it will also:

Use the binaries produced by our build job(s), to reduce duplicate work

Closed by #188


Add editorconfig file

I'm not sure if this is working, but is it possible to move this file to our new .github repo so that it's available to all repos at our org?

I'm not sure if this is working, but is it possible to move this file to our new .github repo so that it's available to all repos at our org?

That's for Community Health files only (except license and readme).

Okay, I just wonder how we'll keep this one in sync with other repos.

Okay, I just wonder how we'll keep this one in sync with other repos.

This file saves a similar purpose as .clang-format. It should not be necessary to clone another repo to set a few editor defaults. Maybe we can introduce a canonical copy in a central scaffold repository from which the others are synced, but that feels very over engineered to me.

Lgtm. We don't have any Makefiles anymore, right?

I removed that section before opening the PR, you must have had an older version in the cache.


feature request: RSS feed

I think I had your old blog in my feed reader. I'm mostly putting this request here so I don't forget to add this one once there's support ;)

Ahoy! Thanks for catching that -- the old blog was running on a much older version of Phoenix and they changed how views & rendering non-HTML templates work so I was putting this off!
Just implemented something quickly; please let me know if it works (deploying rn, give it a few min).
You should be able to see it here: https://vereis.com/rss
Please pardon the lazy descriptions for the mean time, I didn't want to shove the whole post body in there, or manually write summaries for every post right this moment.


error: relation "listings" does not exist

Hey, The app wasn't getting any updates for prices for a week and when I update it, I keep getting this error?
How can I solve it ?

You haven't set up the database yet or at the very least the listings table. To do so, refer to the instructions here: https://github.com/jack-richards/bptf-autopricer?tab=readme-ov-file#requirements
I would recommend that you follow the INITALIZE_DB instructions instead of going with the second database set-up option.


at_c: use size_t where unsigned long is and stdbool for booleans

Would like a discussion of making C99 our minimum C version (because stdbool is only supported in C99+). This would mean dropping support for ANSI C (C89/90).
The sprint points allocated to this ticket will consider two things:

going in and replacing unsigned long with size_t from the stddef.h header
converting from int to booleans (such as iscached and ispublic in metadata) using bool in stdbool.h

Another interesting thing to note about using type headers is it guarantees the size of the type. Example: a int may be 8 bytes in some systems as opposed to the regular 4, but using something like uint64_t from stdint.h guarantees it to be 8 bytes all the time.

@XavierChanth @cpswan Would like your input on making C99 our minimum required version.
mbedtls has their minimum version as C99.

I'm OK with us doing this, but I think we need to explain WHY? This may even justify an architecture decision record (ADR).
For mbedtls I'm very comfortable with it being our default. But I think from the beginning we wanted 'batteries included but removable' so that if customers had another TLS library it wouldn't be too much upheaval to switch. Any decision regarding C99 should probably align with ensuring we don't close off options there.

There are plenty of useful features and data types added in C99, and it seems to be the baseline for support because of this, many useful data types, static keyword, snprintf for string construction, etc.
If we need to support <C99 later, we can look at doing so, but we reduce time to market trying to do so now.

If this decision document is approved, I will go ahead with refactors.
https://github.com/atsign-foundation/at_protocol/pull/134


Auto creation of images

Feature Description
Could Gitea get some mechanism to autocreate images from repos? Or is there any workaround? Thank you!
Screenshots
No response

Talking about creation of docker image from git branch. Gitea already has docker registry, so it would just on push to repo trigger docker build and the created image would be saved to the registry.
Does it make better sense now?

I agree with @jolheiser. I think we should close this issue.

Thank you, I didn't know about Gitea actions, it is disabled by default.

No problem, glad to help. :slightly_smiling_face:
https://docs.gitea.com/usage/actions/overview


Network transient issue could lead to continuous job status file deletion

When continuous jobs run on multiple instances, each instance will write the job status (Running/Initializing/Stopped/..) to an instance-specific status file (d:\Home\data\jobs\continuous\<jobname>\status_<instanceid>).   Each instance will also hold a lock on this file by only allowing R/W but not Delete to indicate that the job is still running on this instance.  This enables the cleanup for stale status file during list webjobs api.
During network transient issue, the instance may lose the lock.   The bug is the instance will try to refresh the jobs but didn't try to re-acquire the status lock.   The list webjobs api which lands on  other instances will attempt to delete the status and succeed.   The outcome is there is no job status eventhough the job is still running on the instance.

Interesting. And I assume this is not just theoretical, and there was an actual instance of the issue?

Yes.  This was reported by a customer - I forward you the internal email.


New build doesn't work at all?

I've installed the newest build and I get warning triangles when pushing the buttons on the stream deck.  If I revert to the other version I'm back where I started.

Hey there. Not sure why that would give you issues since the change was
relatively small. Ill do some additional testing to see if I can find
anything wrong.
Per chance can you give me an example string that you are using for your
command pressed/command released. That would help in the debugging.
On Sun, Sep 4, 2022, 7:23 AM Jinx-IT @.***> wrote:

I've installed the newest build and I get warning triangles when pushing
the buttons on the stream deck. If I revert to the other version I'm back
where I started.
—
Reply to this email directly, view it on GitHub
https://github.com/Zayik/CommandSender/issues/13, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACEELKT7XSAIXKAR32RYIDTV4SWGJANCNFSM6AAAAAAQELFAMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Still working with the same strings…per your msg…here’s the strings.
Packet Sender uses regular string:
CC 8023 1 780 \r
Command Sender uses literal string and then uses html decoding for special characters:
CC 8023 1 780
A note for you though…the string you showed me in command sender (before upgrading to the latest release) doesn’t work either.  Let me clarify that the spaces between CC, 8023, 1, and 780 all matter.  The string calls for a controller change (CC) of parameter 8023 to increase (1 is increase, 0 is decrease) an amount of 780 (which equates to 1dB).  See page 8 of this doc: Composer-Control-Protocol-v7.0-080918.pdf (symetrix.co)https://www.symetrix.co/wp-content/uploads/2018/08/Composer-Control-Protocol-v7.0-080918.pdf
And to clarify again, once upgraded to the new release, the actual stream deck press fails with the warning triangle.
Sincerely,
Destry Jinks Sr.
<EMAIL_ADDRESS>407.574.6978
[jinxITsignature1]
From: David Anderson @.>
Sent: Sunday, September 4, 2022 15:37
To: Zayik/CommandSender @.>
Cc: Support @.>; Author @.>
Subject: Re: [Zayik/CommandSender] New build doesn't work at all? (Issue #13)
Hey there. Not sure why that would give you issues since the change was
relatively small. Ill do some additional testing to see if I can find
anything wrong.
Per chance can you give me an example string that you are using for your
command pressed/command released. That would help in the debugging.
On Sun, Sep 4, 2022, 7:23 AM Jinx-IT<EMAIL_ADDRESS>wrote:

I've installed the newest build and I get warning triangles when pushing
the buttons on the stream deck. If I revert to the other version I'm back
where I started.
—
Reply to this email directly, view it on GitHub
https://github.com/Zayik/CommandSender/issues/13, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACEELKT7XSAIXKAR32RYIDTV4SWGJANCNFSM6AAAAAAQELFAMQ
.
You are receiving this because you are subscribed to this thread.Message
ID<EMAIL_ADDRESS>
—
Reply to this email directly, view it on GitHubhttps://github.com/Zayik/CommandSender/issues/13#issuecomment-1236402243, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGLZTY3LVR3BAMLS53G2E3V4T25ZANCNFSM6AAAAAAQELFAMQ.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Thanks for that detailed explanation.
Given I am abandoning the concept of dealing with html encoding/decoding in favor of unifying the tool to match what others do such as Packet Sender, I am not going to worry about diving into that aspect.
That being said, I have identified two issues and have fixed them.

The package I had was unfortunately a development version which has debugging requirements in order to work. This is what caused the yellow square to appear on the stream deck. I have corrected this and successfully sent a message to a tcp server via internet using the latest package.

I resolved a bug in that if the connection was lost to the server (Server restarts), the very first message sent would fail. (This would result in the command pressed failing to send while the command release would succeed.

I hope this fix fairs much better and thanks for your patience!

So I should upgrade again, and go back to my packet sender style of commands?
Sincerely,
Destry Jinks Sr.
<EMAIL_ADDRESS>407.574.6978
[jinxITsignature1]
From: David Anderson @.>
Sent: Sunday, September 4, 2022 17:43
To: Zayik/CommandSender @.>
Cc: Support @.>; Author @.>
Subject: Re: [Zayik/CommandSender] New build doesn't work at all? (Issue #13)
Thanks for that detailed explanation.
Given I am abandoning the concept of dealing with html encoding/decoding in favor of unifying the tool to match what others do such as Packet Sender, I am not going to worry about diving into that aspect.
That being said, I have identified two issues and have fixed them.

The package I had was unfortunately a development version which has debugging requirements in order to work. This is what caused the yellow square to appear on the stream deck. I have corrected this and successfully sent a message to a tcp server via internet using the latest package.
I resolved a bug in that if the connection was lost to the server (Server restarts), the very first message sent would fail. (This would result in the command pressed failing to send while the command release would succeed.

I hope this fix fairs much better and thanks for your patience!
—
Reply to this email directly, view it on GitHubhttps://github.com/Zayik/CommandSender/issues/13#issuecomment-1236420405, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGLZT2E6DS6KOB5GAQTKPLV4UJXBANCNFSM6AAAAAAQELFAMQ.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Yes, please upgrade again and go back to the packet sender style of commands.

We have full control!  Even on a couple of double commands (muting two channels at once, with a release).  You’re awesome!
Example of double command:
Pressed: CS 8034 65535 \r\nCS 8042 65535 \r
Released: CS 8034 0 \r\nCS 8042 0 \r
Sincerely,
Destry Jinks Sr.
<EMAIL_ADDRESS>407.574.6978
[jinxITsignature1]
From: David Anderson @.>
Sent: Sunday, September 4, 2022 17:59
To: Zayik/CommandSender @.>
Cc: Support @.>; Author @.>
Subject: Re: [Zayik/CommandSender] New build doesn't work at all? (Issue #13)
Yes, please upgrade again and go back to the packet sender style of commands.
—
Reply to this email directly, view it on GitHubhttps://github.com/Zayik/CommandSender/issues/13#issuecomment-1236422407, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGLZT6BV6DYZVA2AQU5DRTV4ULS7ANCNFSM6AAAAAAQELFAMQ.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


[Question]: ERROR from llama-deploy httpx.ConnectError: All connection attempts failed

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I am working in a cloud environment; lightning ai studios and trying to launch a simple app on it.
Following is my main.py code
from src import Config
from llama_deploy import deploy_workflow, WorkflowServiceConfig, ControlPlaneConfig
from src import ReActAgent
from src.utils import download_10k_reports
from src.utils import load_hf_model
from src.utils import initialize_groq_model
from src.ingest import setup_indices
from llama_index.core import PromptTemplate
from src.query_engine import HybridRetriver, StuffedContextQueryEngine
from llama_index.core.postprocessor import SimilarityPostprocessor
from llama_index.postprocessor.colbert_rerank import ColbertRerank
from llama_index.core.tools import QueryEngineTool, ToolMetadata
from llama_index.core.indices.vector_store.retrievers import VectorIndexRetriever

async def main(local_model=False):
    download_10k_reports()
    config = Config()
    if local_model:
        hf_models = load_hf_model(config.hf_tiny_model, config.hf_embed_model)
    else:
        hf_models = load_hf_model(config.hf_tiny_model, config.hf_embed_model, embed_model_only=True)
        groq_llama_8b = initialize_groq_model("llama3-8b-8192")
        groq_llama_70b = initialize_groq_model("llama3-70b-8192")

    indices = setup_indices(hf_models['embed_model'])
    lyft_index = indices['lyft_index']
    uber_index = indices['uber_index']

    # lyft_retriever = HybridRetriver(index=lyft_index, vector_similarity_top_k=20, bm25_similarity_top_k=20, fusion_similarity_top_k=20, llm=groq_llama_8b)
    # uber_retriever = HybridRetriver(index=uber_index, vector_similarity_top_k=20, bm25_similarity_top_k=20, fusion_similarity_top_k=20, llm=groq_llama_8b)

    lyft_retriever = VectorIndexRetriever(index=lyft_index, similarity_top_k=20)
    uber_retriever = VectorIndexRetriever(index=uber_index, similarity_top_k=20)

    colbert_reranker = ColbertRerank(
        top_n=10,
        model="colbert-ir/colbertv2.0",
        tokenizer="colbert-ir/colbertv2.0",
        keep_retrieval_score=True,
    )

    postprocessors=[SimilarityPostprocessor(similarity_cutoff=0.7),
                    colbert_reranker]

    qa_prompt = PromptTemplate(
        """\
    Context information is below.
    ---------------------
    {context_str}
    ---------------------
    Given the context information and not prior knowledge, answer the query.
    Query: {query_str}
    Answer: \
    """
    )

    lyft_query_engine = StuffedContextQueryEngine(
                        retriever=lyft_retriever,
                        qa_prompt=qa_prompt,
                        llm=groq_llama_8b,
                        node_postprocessors=postprocessors
                        )

    uber_query_engine = StuffedContextQueryEngine(
                        retriever=uber_retriever,
                        qa_prompt=qa_prompt,
                        llm=groq_llama_8b,
                        node_postprocessors=postprocessors
                        )

    query_engine_tools = [
        QueryEngineTool(
            query_engine=lyft_query_engine,
            metadata=ToolMetadata(
                name="lyft_10k",
                description="Provides information about Lyft financials for year 2021",
            ),
        ),
        QueryEngineTool(
            query_engine=uber_query_engine,
            metadata=ToolMetadata(
                name="uber_10k",
                description="Provides information about Uber financials for year 2021",
            ),
        ),
    ]
    await deploy_workflow(
        ReActAgent(
            llm=groq_llama_8b,
            tools=query_engine_tools,
            timeout=120,
            verbose=False
        ),
        WorkflowServiceConfig(host="<IP_ADDRESS>", port=8000, service_name="my_workflow"),
        ControlPlaneConfig(host="<IP_ADDRESS>", port=8000),
    )

if __name__ == "__main__":
    import asyncio
    asyncio.run(main())

ERROR
Traceback (most recent call last):
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpx/_transports/default.py", line 66, in map_httpcore_exceptions
    yield
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpx/_transports/default.py", line 366, in handle_async_request
    resp = await self._pool.handle_async_request(req)
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpcore/_async/connection_pool.py", line 216, in handle_async_request
    raise exc from None
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpcore/_async/connection_pool.py", line 196, in handle_async_request
    response = await connection.handle_async_request(
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpcore/_async/connection.py", line 99, in handle_async_request
    raise exc
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpcore/_async/connection.py", line 76, in handle_async_request
    stream = await self._connect(request)
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpcore/_async/connection.py", line 122, in _connect
    stream = await self._network_backend.connect_tcp(**kwargs)
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpcore/_backends/auto.py", line 30, in connect_tcp
    return await self._backend.connect_tcp(
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpcore/_backends/anyio.py", line 114, in connect_tcp
    with map_exceptions(exc_map):
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/contextlib.py", line 153, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions
    raise to_exc(exc) from exc
httpcore.ConnectError: All connection attempts failed

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/teamspace/studios/this_studio/react_agent/src/main.py", line 100, in <module>
    asyncio.run(main())
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/nest_asyncio.py", line 30, in run
    return loop.run_until_complete(task)
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/nest_asyncio.py", line 98, in run_until_complete
    return f.result()
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/asyncio/futures.py", line 201, in result
    raise self._exception.with_traceback(self._exception_tb)
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/asyncio/tasks.py", line 232, in __step
    result = coro.send(None)
  File "/teamspace/studios/this_studio/react_agent/src/main.py", line 87, in main
    await deploy_workflow(
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/llama_deploy/deploy/deploy.py", line 198, in deploy_workflow
    response = await client.get(f"{control_plane_url}/queue_config")
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpx/_client.py", line 1757, in get
    return await self.request(
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpx/_client.py", line 1530, in request
    return await self.send(request, auth=auth, follow_redirects=follow_redirects)
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpx/_client.py", line 1617, in send
    response = await self._send_handling_auth(
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpx/_client.py", line 1645, in _send_handling_auth
    response = await self._send_handling_redirects(
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpx/_client.py", line 1682, in _send_handling_redirects
    response = await self._send_single_request(request)
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpx/_client.py", line 1719, in _send_single_request
    response = await transport.handle_async_request(request)
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpx/_transports/default.py", line 365, in handle_async_request
    with map_httpcore_exceptions():
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/contextlib.py", line 153, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/home/zeus/miniconda3/envs/cloudspace/lib/python3.10/site-packages/httpx/_transports/default.py", line 83, in map_httpcore_exceptions
    raise mapped_exc(message) from exc
httpx.ConnectError: All connection attempts failed

Does anyone have any idea as to the possible source of this error?

@BlueKiji77 fyi, we have an actual llama-deploy repo for llama-deploy issues. Moving this over there
Normally, I think this issue would occur because you didn't run deploy_core()
You can see from the error, its failing to on response = await client.get(f"{control_plane_url}/queue_config")


Implemented GET relatedId

-implemented GET '/products/:product_id/related'

Looks good, I'll probably add nodemon to mine as well.


yarn create react-app my-app2 crashes with error TypeError: BigInt.prototype.toString requires that 'this' be a BigInt

Describe the bug
yarn create react-app my-app2 crashes with error TypeError: BigInt.prototype.toString requires that 'this' be a BigInt
Did you try recovering your dependencies?

(Write your answer here.)
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment

npx create-react-app --info

Environment Info:

  current version of create-react-app: 4.0.3
  running from /Users/jsyrjala/node_modules/create-react-app

  System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
  Binaries:
    Node: 16.2.0 - /usr/local/bin/node
    Yarn: 2.4.1 - /usr/local/bin/yarn
    npm: 7.14.0 - /usr/local/bin/npm
  Browsers:
    Chrome: Not Found
    Edge: Not Found
    Firefox: Not Found
    Safari: 14.1
  npmPackages:
    react: Not Found
    react-dom: Not Found
    react-scripts: Not Found
  npmGlobalPackages:
    create-react-app: Not Found
```

### Steps to reproduce

<!--
  How would you describe your issue to someone who doesn’t know you or your project?
  Try to write a sequence of steps that anybody can repeat to see the issue.
-->

```
yarn create react-app my-app2
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 1s 95ms
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 0s 308ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 0s 946ms
➤ YN0000: Done in 2s 417ms

Creating a new React app in /Users/xxx/projects/nflow/my-app2.

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...

➤ YN0000: ┌ Resolution step
➤ YN0032: │ fsevents@npm:2.3.2: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ fsevents@npm:2.3.2: Implicit dependencies on node-gyp are discouraged
➤ YN0061: │ babel-eslint@npm:10.1.0 is deprecated: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
➤ YN0061: │ urix@npm:0.1.0 is deprecated: Please see https://github.com/lydell/urix#deprecated
➤ YN0061: │ resolve-url@npm:0.2.1 is deprecated: https://github.com/lydell/resolve-url#deprecated
➤ YN0061: │ @hapi/joi@npm:15.1.1 is deprecated: Switch to 'npm install joi'
➤ YN0061: │ @hapi/address@npm:2.1.4 is deprecated: Moved to 'npm install @sideway/address'
➤ YN0061: │ @hapi/bourne@npm:1.3.2 is deprecated: This version has been deprecated and is no longer supported or maintained
➤ YN0061: │ @hapi/topo@npm:3.1.6 is deprecated: This version has been deprecated and is no longer supported or maintained
➤ YN0061: │ @hapi/hoek@npm:8.5.1 is deprecated: This version has been deprecated and is no longer supported or maintained
➤ YN0061: │ rollup-plugin-babel@npm:4.4.0 is deprecated: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-babel.
➤ YN0061: │ chokidar@npm:2.1.8 is deprecated: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
➤ YN0061: │ fsevents@npm:1.2.13 is deprecated: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
➤ YN0061: │ fsevents@npm:1.2.13 is deprecated: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
➤ YN0061: │ core-js@npm:2.6.12 is deprecated<EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
➤ YN0032: │ nan@npm:2.14.2: Implicit dependencies on node-gyp are discouraged
➤ YN0061: │ request@npm:2.88.2 is deprecated: request has been deprecated, see https://github.com/request/request/issues/3142
➤ YN0061: │ har-validator@npm:5.1.5 is deprecated: this library is no longer supported
➤ YN0061: │ request-promise-native@npm:1.0.9 is deprecated: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
➤ YN0032: │ evp_bytestokey@npm:1.0.3: Implicit dependencies on node-gyp are discouraged
➤ YN0002: │ react-dev-utils@npm:11.0.4 doesn't provide typescript (p79ddf), requested by fork-ts-checker-webpack-plugin
➤ YN0002: │ react-dev-utils@npm:11.0.4 doesn't provide webpack (p2af19), requested by fork-ts-checker-webpack-plugin
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed in 30s 171ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ @babel/helper-validator-identifier@npm:7.14.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @babel/helper-validator-option@npm:7.12.17 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @babel/helper-wrap-function@npm:7.12.13 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @babel/helpers@npm:7.12.17 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @babel/highlight@npm:7.12.13 can't be found in the cache and will be fetched from the remote registry
➤ YN0000: ⠙ --------------------------------------------------------------------------------
node:fs:2645
      const dev = BigIntPrototypeToString(stats.dev, 32);
                  ^

TypeError: BigInt.prototype.toString requires that 'this' be a BigInt
    at Number.toString (<anonymous>)
    at gotStat (node:fs:2645:19)
    at /private/var/folders/3g/p3lk84l10ts3jt11dcd719340000gn/T/xfs-df915d72/dlx-92665/.pnp.js:5208:13

Aborting installation.
  yarnpkg add --exact react react-dom react-scripts cra-template --cwd /Users/jsyrjala/projects/nflow/my-app2 has failed.

Deleting generated file... package.json
Deleting generated file... yarn.lock
Done.

```
### Expected behavior

<!--
  How did you expect the tool to behave?
  It’s fine if you’re not sure your understanding is correct.
  Just write down what you thought would happen.
-->

Expected to create the project.

`npx create-react-app my-app` creates the project successfully.

### Actual behavior

<!--
  Did something go wrong?
  Is something broken, or not behaving as you expected?
  Please attach screenshots if possible! They are extremely helpful for diagnosing issues.
-->

Fails with this error:
```
node:fs:2645
      const dev = BigIntPrototypeToString(stats.dev, 32);
                  ^

TypeError: BigInt.prototype.toString requires that 'this' be a BigInt
    at Number.toString (<anonymous>)
    at gotStat (node:fs:2645:19)
    at /private/var/folders/3g/p3lk84l10ts3jt11dcd719340000gn/T/xfs-df915d72/dlx-92665/.pnp.js:5208:13

Aborting installation.
```

### Reproducible demo

<!--
  If you can, please share a project that reproduces the issue.
  This is the single most effective way to get an issue fixed soon.

  There are two ways to do it:

    * Create a new app and try to reproduce the issue in it.
      This is useful if you roughly know where the problem is, or can’t share the real code.

    * Or, copy your app and remove things until you’re left with the minimal reproducible demo.
      This is useful for finding the root cause. You may then optionally create a new project.

  This is a good guide to creating bug demos: https://stackoverflow.com/help/mcve
  Once you’re done, push the project to GitHub and paste the link to it below:
-->

Running `yarn create react-app my-app2` causes this behavior every time for me.

<!--
  What happens if you skip this step?

  We will try to help you, but in many cases it is impossible because crucial
  information is missing. In that case we'll tag an issue as having a low priority,
  and eventually close it if there is no clear direction.

  We still appreciate the report though, as eventually somebody else might
  create a reproducible example for it.

  Thanks for helping us help you!
-->

I have the same issue

It's a yarn 2.x version problem https://github.com/yarnpkg/berry/issues/2232
It was solved in yarn 3, so the solution is to update yarn
yarn set version stable


Errors on go install .

Seeing some errors on the installation related to package github.com/herumi/bls-eth-go-binary v1.28.1.
../go/pkg/mod/github.com/herumi/bls-eth-go-binary@v1.28.1/bls/cast.go:9:28: undefined: SecretKey
../go/pkg/mod/github.com/herumi/bls-eth-go-binary@v1.28.1/bls/cast.go:9:40: undefined: Fr
../go/pkg/mod/github.com/herumi/bls-eth-go-binary@v1.28.1/bls/cast.go:13:26: undefined: Fr
../go/pkg/mod/github.com/herumi/bls-eth-go-binary@v1.28.1/bls/cast.go:13:31: undefined: SecretKey
../go/pkg/mod/github.com/herumi/bls-eth-go-binary@v1.28.1/bls/cast.go:19:28: undefined: PublicKey
../go/pkg/mod/github.com/herumi/bls-eth-go-binary@v1.28.1/bls/cast.go:19:40: undefined: G1
../go/pkg/mod/github.com/herumi/bls-eth-go-binary@v1.28.1/bls/cast.go:23:26: undefined: G1
../go/pkg/mod/github.com/herumi/bls-eth-go-binary@v1.28.1/bls/cast.go:23:31: undefined: PublicKey
../go/pkg/mod/github.com/herumi/bls-eth-go-binary@v1.28.1/bls/cast.go:29:23: undefined: Sign
../go/pkg/mod/github.com/herumi/bls-eth-go-binary@v1.28.1/bls/cast.go:29:30: undefined: G2
../go/pkg/mod/github.com/herumi/bls-eth-go-binary@v1.28.1/bls/cast.go:29:30: too many errors

Perhaps version changed or deprecated? All in all, worth revising.

Latest version is [v1.32.0](https://github.com/herumi/bls-eth-go-binary) but I still seeing the same undefined errors.

Which computer architecture and Go version are you using?
It works for me on x86_64 Linux AMD, Go 1.20.6.

The Herumi library is a native dependency, this may be causing the compiler errors with undefined types, if your architecture/type somehow isn't supported by it. Maybe you can try bumping the dependency version, and see if newer versions work?

To replace Herumi BLS with a newer better supported BLS library (BLST or Kilic BLS), we need an alternative to PrivateKeyFromSeedAndPath from https://github.com/wealdtech/go-eth2-util which depends on https://github.com/wealdtech/go-eth2-types which uses the Herumi BLS types.

Closing this, issue seems stale, BLS library was swapped already and tool should install fine


Increment versions for providerhub releases

Increment package versions for providerhub releases

API change check
API changes are not detected in this pull request.


Create generic pipeline tutorial for JupyterLab

This PR replaces the existing/outdated hello world tutorial with an introduction to generic pipelines.
Note: The document contains several references to topics that are not yet available in the documentation's stable branch.  (They are available in the latest branch.)

[x] No upgrade to pipeline v4 is required because the tutorial does not include a pipeline file.

Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Thanks for the review. I've made the (hopefully appropriate changes). I also found a problem in the readme, which was still referring to version 2.3 instead of 3.0


data-clear with altInput issue

Hello,
Here is an example:  https://jsfiddle.net/mironim/szuw0v4a/4/
With altInput = true, reset button doesn't work, only hidden input value is reset and altInput date value no.
I think a possible fix is:
self.clear = function() {
        self.input.value="";
        self.selectedDateObj = null;

        if(self.altInput) {
            self.altInput.value = null;
        }

        triggerChange();

        self.jumpToDate();
    };

tks

I'm running into this as well. was it resolved at the time? what's the proper way to issue a clear with a alt time?


Difference between "trav_map" and "obstacle_map" in core/physics/scene.py

Hi,
I see their source image are different but I don't understand the difference between "trav_map" and "obstacle_map". Could you explain their difference?
Many thanks!

Thanks for the question.
We use two different heuristics to generate trav_map and obstacle_map (e.g. floor_trav_0.png and floor_0.png). They are used together in the code to best represent the traversability of a scene.
https://github.com/StanfordVL/iGibson/blob/822ff1a77f8ee40dc72e14439ef8af1c92a48d38/gibson2/core/physics/scene.py#L218
Essentially, we take a conservative approach and treat an area as traversable or empty only if both trav_map and obstacle_map represent that area as empty (with pixel value 255)
For example, this is the "trav_map" of a scene called "Rs".

And this is the "obstacle_map" of the same scene.

Thank you, I got it now.

Hi, just go another related question, some image has name ended with "_V3". What is the difference between the "v3" map and normal map? Thank you!

Sorry for my belated reply. I think "v3" map is generated using a slightly different heuristic. Neither of them are completely perfect. Feel free just to use the normal map and ignore the "v3" map.


[Wait for #1798] [Output] Return zero grad for empty output

Dependency of the PR

[Pending commit: #1798]

Commits to be reviewed in this PR
[Spec] Change nntrainer install dir
This patch change nntrainer install dir to /usr/prefix/*,
see also https://github.com/nnstreamer/nnstreamer/issues/3560
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>
[Test] Add test with dangling output
This patch add test with dangling output, this test passes test but
fails optimized run.
Current aim is to make this pass optimized run as well.
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>
[Const] Make incoming derivative const
As incoming derivative shall not be changed by the layer, this patch
changes runcontext::getIncomingDerivatives and runcontext::getOutputGrad
to return const.
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>
[Tensor] OutputGrad defaults to be zero if not given
This patch creates output grad(incoming) to all zero if the given output
is not trainable. This will make the given output be considered as
constant. If a user wants to check if output is constant-like(having
zero gradient as it's partner), she can easily check if
outputHasGradient
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>
[Context] out_dim -> out spec
This patch prepare migration to tensor spec v2 by substituting out
dimension to out specification inside layer_context
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>
[Manager] update requestInputs to use requestTensor
This patch update requestInputs to use requestTensor_ as a bridge.
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>
[context] Receive out conn info and use
Init Context receive out conn info (true if conn info exist, false if
not) and use it to determine given output is dangled
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>
[Clean] Remove getOutputDimensions()
This patch removes initContext::getOutputDimensions().
This function is only used in the test so removed
(It is used in network_graph but soon will be substitued)
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>
[Output] Return zero grad for empty output
Along this patchline implements returning zero grad for empty output
Particualary in this patch...

Remove manager::requestOutput
Use requestTensors instead of requestOutput to request outputs

Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1818. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1818-202112282033210.95404100418091-892a22d7abcbf489ef4d9dcd684d6bdf7d325cb8/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1818-202112282052050.25134205818176-c2b645ef5cb1a84462e57af81b8dd195ba6cc476/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1818-202112282133160.20037293434143-b84f29b2591ec6bd96e5d274b9ab87a263d69862/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1818-202112291535520.87146711349487-f552ca0d5d74c66f2a5c990c9a1143edfd3cd777/.


Get-SPOScriptFromList not recognized as command's applet

Hello,
I updated my Microsoft.Online.SharePoint.PowerShell module to version 16.0.9119.1200 because Powershell returned an error when trying to get Script from Event List. This error is the following :
Get-SPOScriptFromList : the term "Get-SPOScriptFromList" is not recognized as a command applet, function, script file nor exe. Please check the writing...
(sorry, translated from french prompt)
Why ? Is the doc updated ? Thanks !

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

ID: 49097b6c-149f-075c-3371-36055d3d7ac1
Version Independent ID: e72af23f-ac47-2fe7-5830-14998f75587f
Content: Get-SPOSiteScriptFromList (sharepoint-online)
Content Source: sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteScriptFromList.md
Service: sharepoint-powershell
GitHub Login: @trent-green
Microsoft Alias: trgreen

@officedocsbot assign @yogkumgit

Hello @Amysno
Thanks for your feedback.
I see that you ran Get-SPOScriptFromList, but the cmdlet you opened the issue for is Get-SPOSiteScriptFromList
I could verify that, that cmdlet, is present in the mentioned version of the module.

Hope this information helps you.

@get-itips  Thank you very much for the contribution and sharing this explanation. @Amysno
Hope this comment is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@officedocsbot close


[Transmogrification] Donate button and save feature

I absolutely love this pluggin and wanted to donate a few bucks your way, can you add a donate button to the page on github maybe?
Also, any idea when saving the presets will return? (if you can save them currently im not sure how as my changes revert when i login)

Glad to hear you like it so much! I'm very proud of how the UI turned out, and barring some features I've got planned, I'm extremely happy with it. I need to have a look at how GitHub's Sponsor stuff works and set something up, but I'll do that shortly.
As for save, no functionality went away. The issue with Save and Delete is they didn't do anything; editing a preset already saves it automatically. The buttons exist from a time in development where I thought I'd want manual saving, and the eventual only use for them was to move a preset to another slot.  All delete did was reset the preset back to the default state, which is pretty trivial to do manually either way. It was subsequently found that save did not work in the slightest, and so given that both buttons did basically nothing, I decided to remove them.
With issue #29, there's an interesting idea that cannot work in the current system: an IF This Then That (IFTTT) style system for dynamically swapping items. With only 4 slots to work with, it's basically unusable, removing any granularity that you may want, and even without it 4 slots just isn't enough to experiment with. For that, I've started work on expanding the preset system to support an extremely large amount (though I'm likely to cap it, it'll still be orders of magnitude higher). The UI is in place, though I'm having issues with the development; Dependency Injection is weird and somehow I've accidentally made a circle. Either way, it's in this UI that the save and delete buttons will finally have a purpose, and though they're not implemented yet, I hope I can fix this circular dependency issue before I go mad.

I've added the link. Spent way too long trying to find a suitable background :d

So I just want to update this: turns out saving was actually broken. I really don't know how I missed this, as I could have sworn I made autosaving work at some point during development. v1.1.3 has autosaving when logging out, hopping, or turning off the plugin, which should cover it for the time being.

Awesome dude, glad you caught it. Looks like it’s working now.


Windows support?

What is wrong?
Windows is not supported. Even if we never get trinity supported, just being able to run evm stuff on Windows would be nice.
How can it be fixed
Known issues:

#395 -- need a pyethash fallback (maybe native python?)
#781 -- fall back to default loop because can't use uvloop? Does trio support windows?

Let's add to this list as we discover more.
Then hunt down anything else. Probably need a Windows machine to develop this at any sort of reasonable speed.

2012 had a "may fix". I think it's highly unlikely that this is resolved. Closing this issue would definitely require confirmation.

@carver yep, I guess this was closed automatically from a commit message :+1:

I was able to install on windows using wsl https://docs.microsoft.com/en-us/windows/wsl/install

windows seems to be working now


Send the certificate and private_key with vhost reprovisions

@fancyremarker for you to review/merge please.
Fixes #185 by attaching certificate and private_key to the vhost reprovision payload. See the test.

Thanks!


Match over unit pattern in expanded macro to satisfy clippy 0.1.73

With Rust 1.73, the following code:
#![warn(clippy::pedantic)]

#[derive(Debug, thiserror::Error)]
#[metered::error_count(name = ErrorCount, visibility = pub)]
pub enum Error {
    #[error("msg")]
    Variant,
}

raises a clippy warning:
warning: matching over `()` is more explicit
 --> src/lib.rs:4:1
  |
4 | #[metered::error_count(name = ErrorCount, visibility = pub)]
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#ignored_unit_patterns
note: the lint level is defined here
 --> src/lib.rs:1:9
  |
1 | #![warn(clippy::pedantic)]
  |         ^^^^^^^^^^^^^^^^
  = note: `#[warn(clippy::ignored_unit_patterns)]` implied by `#[warn(clippy::pedantic)]`
  = note: this warning originates in the attribute macro `metered::error_count` (in Nightly builds, run with -Z macro-backtrace for more info)

This PR satisfies the clippy lint. Pattern tested with Rust 1.31.0.

Note that this most likely won't be needed in a future version of Rust once this change makes its way to stable clippy: https://github.com/rust-lang/rust-clippy/pull/11602
So unsure if worth merging this PR anymore.


Game crash, compatibility issue

The game crashes when using it with the No Realms Button mod.
Issue on No Realms Button mod: 1.21 crash
crash report
crash-2024-07-29_02.56.04-client.txt

I can't seem to reproduce this on a fresh instance with both mods installed. Do you have the entire log leading up to the crash?

This is the full log:
latest.log
With only these mods (and no resource packs)
fabric-api-0.100.7+1.21.jar
Notebook-4.0.3.jar
realmsfix-2.0.5-SNAPSHOT.jar

It turns out I installed the wrong mod, I can reproduce the issue now and will see if I can fix it

I hate to ping-pong the issue but I think this is an issue with their mod rather than this one, I would imagine there's others out there which also have this bug when installed alongside looking through their mod's source

Found a way to make the two work together and let the other mod creator know so they can improve some things with how theirs works, so will push an update out in the next 15-20 minutes or so

v4.0.4+ should no longer have this issue
https://modrinth.com/mod/notebook/version/4.0.4


[Power Automate] Remove preview tag from PA screenshots and text

Docs Build status updates of commit fe4565e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/all-files-in-folder-sample-flow-3.PNG
:white_check_mark:Succeeded
View

docs/images/email-chart-sample-flow-1.PNG
:white_check_mark:Succeeded
View

docs/images/no-xlsm.png
:white_check_mark:Succeeded
View

docs/images/power-automate-file-browser.PNG
:white_check_mark:Succeeded
View

docs/images/power-automate-return-tutorial-4.PNG
:white_check_mark:Succeeded
View

docs/images/power-automate-tutorial-5.png
:white_check_mark:Succeeded
View

docs/images/rangebasics-addrow-vid.png
:white_check_mark:Succeeded

docs/images/rangebasics-vid.png
:white_check_mark:Succeeded

docs/images/scenario-task-reminders-first-flow-step.PNG
:white_check_mark:Succeeded
View

docs/images/scenario-task-reminders-last-flow-step.PNG
:white_check_mark:Succeeded
View

docs/images/scenario-task-reminders-spreadsheet-after.png
:white_check_mark:Succeeded
View

docs/images/use-in-power-automate.png
:white_check_mark:Succeeded
View

docs/images/xlsm-in-pa.png
:white_check_mark:Succeeded
View

docs/resources/samples/automate-tasks-on-all-excel-files-in-folder.md
:white_check_mark:Succeeded
View

docs/resources/samples/email-images-chart-table.md
:white_check_mark:Succeeded
View

docs/resources/scenarios/task-reminders.md
:white_check_mark:Succeeded
View

docs/tutorials/excel-power-automate-manual.md
:white_check_mark:Succeeded
View

docs/tutorials/excel-power-automate-returns.md
:white_check_mark:Succeeded
View

docs/tutorials/excel-power-automate-trigger.md
:white_check_mark:Succeeded
View

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


Error building Ubuntu vSphere OVA node image

What happened:
Followed directions here
Everything seems to work until provisioning ansible.
Get the following error when building ubuntu vSphere ova image:
image-builder build --os ubuntu --hypervisor vsphere --release-channel 1-23 --vsphere-config vsphere-connection.json

==> vsphere: File /home/image-builder/eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi/packer_cache/48e4ec4daa32571605576c5566f486133ecc271f.iso already uploaded; continuing
==> vsphere: File [isilon-ds1] packer_cache//48e4ec4daa32571605576c5566f486133ecc271f.iso already exists; skipping upload.
==> vsphere: Creating VM...
==> vsphere: Customizing hardware...
==> vsphere: Mounting ISO images...
==> vsphere: Adding configuration parameters...
==> vsphere: Creating floppy disk...
    vsphere: Copying files flatly from floppy_files
    vsphere: Done copying files from floppy_files
    vsphere: Collecting paths from floppy_dirs
    vsphere: Resulting paths from floppy_dirs : [./packer/ova/linux/ubuntu/http/]
    vsphere: Recursively copying : ./packer/ova/linux/ubuntu/http/
    vsphere: Done copying paths from floppy_dirs
==> vsphere: Uploading created floppy image
==> vsphere: Adding generated Floppy...
==> vsphere: Set boot order temporary...
==> vsphere: Power on VM...
==> vsphere: Waiting 10s for boot...
==> vsphere: Typing boot command...
==> vsphere: Waiting for IP...
==> vsphere: IP address: <IP_ADDRESS>
==> vsphere: Using ssh communicator to connect: <IP_ADDRESS>
==> vsphere: Waiting for SSH to become available...
==> vsphere: Connected to SSH!
==> vsphere: Provisioning with Ansible...
    vsphere: Setting up proxy adapter for Ansible....
==> vsphere: Executing Ansible: ansible-playbook -e packer_build_name="vsphere" -e packer_builder_type=vsphere-iso -e packer_http_addr=<IP_ADDRESS>:0 --ssh-extra-args '-o IdentitiesOnly=yes' --extra-vars containerd_url=https://github.com/containerd/containerd/releases/download/v1.5.7/cri-containerd-cni-1.5.7-linux-amd64.tar.gz containerd_sha256=7fce75bab43a39d6f9efb3c370de2da49723f0e1dbaa9732d68fa7f620d720c8 etcd_http_source=https://distro.eks.amazonaws.com/kubernetes-1-23/releases/4/artifacts/etcd/v3.5.4/etcd-linux-amd64-v3.5.4.tar.gz etcd_version=v3.5.4 etcd_sha256=84626ef08338fffbc2c6ea8e01f5c95ca5d0a2392b0929d4fa6e75ae22758847 etcdadm_http_source=https://anywhere-assets.eks.amazonaws.com/releases/bundles/15/artifacts/etcdadm/5b496a72af3d80d64a16a650c85ce9a5882bc014/etcdadm-linux-amd64.tar.gz etcdadm_version=v0.1.5 pause_image=public.ecr.aws/eks-distro/kubernetes/pause:v1.23.7-eks-1-23-4 containerd_additional_settings= containerd_cri_socket=/var/run/containerd/containerd.sock containerd_version=1.5.7 crictl_url=https://anywhere-assets.eks.amazonaws.com/releases/bundles/15/artifacts/cri-tools/v1.24.2/cri-tools-linux-amd64.tar.gz crictl_sha256=0e69588633865bc2e3da45b51353a8b4279e104aa72e64496ddf070f4d3fc453 crictl_source_type=http custom_role= custom_role_names= disable_public_repos=false extra_debs=nfs-common xfsprogs extra_repos= extra_rpms= http_proxy= https_proxy= kubeadm_template=etc/kubeadm.yml kubernetes_cni_http_source=https://distro.eks.amazonaws.com/kubernetes-1-23/releases/4/artifacts/plugins kubernetes_cni_http_checksum=sha256:c2578ba5592befc774ff7f630820b3c7436e39f7473cdcc6470cfb9d408003a7 kubernetes_http_source=https://distro.eks.amazonaws.com/kubernetes-1-23/releases/4/artifacts/kubernetes kubernetes_container_registry=public.ecr.aws/eks-distro kubernetes_rpm_repo=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64 kubernetes_rpm_gpg_key="https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg" kubernetes_rpm_gpg_check=True kubernetes_deb_repo="https://apt.kubernetes.io/ kubernetes-xenial" kubernetes_deb_gpg_key=https://packages.cloud.google.com/apt/doc/apt-key.gpg kubernetes_cni_deb_version= kubernetes_cni_rpm_version= kubernetes_cni_semver=v1.1.1 kubernetes_cni_source_type=http kubernetes_semver=v1.23.7 kubernetes_source_type=http kubernetes_load_additional_imgs=true kubernetes_deb_version=1.20.10-00 kubernetes_rpm_version=1.20.10-0 no_proxy= python_path= redhat_epel_rpm=https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm epel_rpm_gpg_key= reenable_public_repos=true remove_extra_repos=false systemd_prefix=/usr/lib/systemd sysusr_prefix=/usr sysusrlocal_prefix=/usr/local load_additional_components=true additional_registry_images=false additional_registry_images_list= additional_url_images=true additional_url_images_list=https://distro.eks.amazonaws.com/kubernetes-1-22/releases/9/artifacts/kubernetes/v1.22.10/bin/linux/amd64/pause.tar additional_executables=false additional_executables_list= additional_executables_destination_path= build_target=virt --extra-vars guestinfo_datasource_slug=https://raw.githubusercontent.com/vmware/cloud-init-vmware-guestinfo guestinfo_datasource_ref=v1.4.0 guestinfo_datasource_script=https://raw.githubusercontent.com/vmware/cloud-init-vmware-guestinfo/v1.4.0/install.sh --extra-vars  -e ansible_ssh_private_key_file=/tmp/ansible-key936600266 -i /tmp/packer-provisioner-ansible421632417 /home/image-builder/eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi/ansible/firstboot.yml
    vsphere:
    vsphere: PLAY [all] *********************************************************************
==> vsphere: failed to handshake
    vsphere:
    vsphere: TASK [Gathering Facts] *********************************************************
    vsphere: fatal: [default]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Unable to negotiate with <IP_ADDRESS> port 39045: no matching host key type found. Their offer: ssh-rsa", "unreachable": true}
    vsphere:
    vsphere: PLAY RECAP *********************************************************************
    vsphere: default                    : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0
    vsphere:
==> vsphere: Provisioning step had errors: Running the cleanup provisioner, if present...
==> vsphere: Clear boot order...
==> vsphere: Power off VM...
==> vsphere: Deleting Floppy image ...
==> vsphere: Destroying VM...
Build 'vsphere' errored after 4 minutes 32 seconds: Error executing Ansible: Non-zero exit status: exit status 4

==> Wait completed after 4 minutes 32 seconds

==> Some builds didn't complete successfully and had errors:
--> vsphere: Error executing Ansible: Non-zero exit status: exit status 4

==> Builds finished but no artifacts were created.
make[1]: *** [Makefile:323: build-node-ova-vsphere-ubuntu-2004] Error 1
make[1]: Leaving directory '/home/image-builder/eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi'
make: *** [Makefile:205: local-build-ova-ubuntu-2004] Error 2
make: Leaving directory '/home/image-builder/eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder'
2022/08/31 05:21:06 Error executing image-builder for vsphere hypervisor: failed to run command: exit status 2

What you expected to happen:
Successful build
How to reproduce it (as minimally and precisely as possible):
N/A
Anything else we need to know?:
Environment:

EKS Anywhere Release: v0.11.1
EKS Distro Release: 0.109.0

Hello @dashkan, thanks for trying out the image-builder to build vsphere ubuntu nodes. It looks like the ssh process running on vm/machine running the image-builder, doesnt have ssh-rsa as an accepted algorithm. Please edit the sshd config at /home/$USER/.ssh/config and add the following two lines.
HostKeyAlgorithms +ssh-rsa
PubkeyAcceptedKeyTypes +ssh-rsa

This will add rsa as an accepted algorithm and allow packer to negotiate with the vm being created during image building process. Try running the image-builder command after these changes.
image-builder build --os ubuntu --hypervisor vsphere --release-channel 1-23 --vsphere-config vsphere-connection.json --force
The ssh config changes do not need ssh process to be restarted to take effect. But if you still see the problem, you can try restarting the process with systemctl restart ssh
I will also update the documentation to reflect these instructions.

That resolved the issue. Docs state to use Ubuntu 22.04 which defaults to not having ssh-rsa algorithm enabled. Maybe docs should be updated....


[RFC]: refactor blas/ext/base/sdsapxsumpw to follow current project conventions

Description
This RFC proposes refactoring @stdlib/blas/ext/base/sdsapxsumpw to follow current project conventions.
These conventions are outlined in more detail in https://github.com/stdlib-js/stdlib/issues/788. Namely, we want to migrate from C++ add-on interfaces to C add-on interfaces and then make various style and simplification changes.
Some example commits which perform most, if not all, of the requested changes include https://github.com/stdlib-js/stdlib/commit/d66d80cfcbab1da95cb5ae8cfae4a1fc4c5129d1 (saxpy),  https://github.com/stdlib-js/stdlib/commit/3c82fe7b6c0f9fd6ef02c86d6e2024d708ac8c14 (cswap), and https://github.com/stdlib-js/stdlib/commit/5b15c9675be434c0e11b1ec1e1f78d7b089abbcd (dasum).
Related Issues
Related issues #788, #1152.
Questions
No.
Other
No.
Checklist

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

@Planeshifter can I take this issue?


Add external templates on docs

I built a template for material-ui: https://github.com/alexanmtz/material-sense
I would like to make a Pull Request to add it to the docs, is that possible?
Context 🔦
I want to have my template available at Material UI docs page, as a curated template.

Hey @alexanmtz, I'm happy to see this project :). I think that we can link it in the documentation. However, something is off with the mobile breakpoint. Could you have a look at it first? Thank you.


Hadle clicks on 2 glides' slides differently

I have 2 glides and I want to only handle the clicks on one glide but not the other! right now handling the event @glide:slide-click handles both glides. shouldn't the event be launched only from the glide?

Hi @skourta
@glide:slide-click it's a custom event that provides only vue-glide, not glide.js itself. When type is carousel, glide.js clone DOM slides, these are not vue components on which you can trigger an event. https://github.com/antonreshetov/vue-glide/blob/master/src/components/Glide.js#L270
But I agree, I need to find a solution to this problem

@antonreshetov I did a workaround by wrapping the content inside a div and giving it the onclick it works on single slide view but when there 3 slides by view the one with the class glide__slide--clone" kills the event I don't know why!

@skourta should be fixed in #22

This does not seem fixed, Im still having the problem using "vue-glide-js": "^1.3.14" and "nuxt": "^2.17.0" and "vue": "^2.7.10"


Rebase upstream to get uuid update

@xdumaine Can we get this one merged?

Remind me tomorrow and I'll give you owner on this repo


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/103351

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/117911

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/120530

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/120649


Exception Mapper Logging Enhancements

Please see: #2128
Commit notes:
Date:   Wed Aug 9 16:10:01 2017 -0400

    Exception mapper logging enhancements

    1) Implemented debug logging for JerseyViolationExceptionMapper.
    2) Fixed compiler warning regarding serialization for
    JerseyViolationException.
    3) Wrapped debug statement in JsonPropcessingExeptionMapper with
    "isDebugEnabled"; this will ensure the JVM does not bother loading and
    caching the log string unless debug is actually enabled. This will also
    allow more aggressive code optimization when running the server JVM.

Coverage decreased (-0.02%) to 85.162% when pulling 773595f75aa24a6f365779ad6a3bf3bc5077e9c1 on isaki-x:master into 6a4bf5b6a478a105b3bed746f1eba1ea2e7cc266 on dropwizard:master.

Well that was unexpected. I will work on getting the code coverage up. While I'm at it, I noticed that the validation mapper and its unit test class do not share a name; is this intentional? If not, I can rename it as part of my changes.

Coverage decreased (-0.02%) to 85.162% when pulling 5870087a93aebd3c657df8abd7bcd4b2df4c11b0 on isaki-x:master into 6a4bf5b6a478a105b3bed746f1eba1ea2e7cc266 on dropwizard:master.

Coverage increased (+0.004%) to 85.185% when pulling 6d9c168f6931969291ab4a24c5f8eefeb40d127f on isaki-x:master into 6a4bf5b6a478a105b3bed746f1eba1ea2e7cc266 on dropwizard:master.

I'm not sure how to clear out the "changes requested" failure. I thought committing the requested changes would fix it.

Don't worry, it's something the reviewer has to do on their end 😄
I've approved it.

Good to know, thanks!

Would it be possible to this merged into 1.1.X as well as 1.2.X if 1.2.X is a ways out? Thanks!

@isaki-x LGTM, Thank you!

I will make a RC for 1.2 with this enhancement.


problem getting some trusty packages (octave)

Err http://archive.ubuntu.com/ubuntu/ trusty-security/main libcupsfilters1 amd64 1.0.52-0ubuntu1.5
404  Not Found [IP: <IP_ADDRESS> 80]
Err http://archive.ubuntu.com/ubuntu/ trusty-security/main libcupsimage2 amd64 1.7.2-0ubuntu1.6
404  Not Found [IP: <IP_ADDRESS> 80]
Fetched 48.3 MB in 1min 33s (518 kB/s)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/c/cups-filters/libcupsfilters1_1.0.52-0ubuntu1.5_amd64.deb  404  Not Found [IP: <IP_ADDRESS> 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/c/cups/libcupsimage2_1.7.2-0ubuntu1.6_amd64.deb  404  Not Found [IP: <IP_ADDRESS> 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
(trusty)root@localhost:/home/ted# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=56 time=163 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=56 time=162 ms
^C
--- <IP_ADDRESS> ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 162.214/162.993/163.773/0.877 ms
(trusty)root@localhost:/home/ted# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=56 time=167 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=56 time=158 ms
^C
--- <IP_ADDRESS> ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 158.508/162.923/167.339/4.433 ms
(trusty)root@localhost:/home/ted#

fixed it.

@tedm -

fixed it.

How?
Was it just a temporarynetwork glitch or was the package not there?
...Just curious...

I think it was probably there, I hadn't run apt-get upgrade in a while...

@tedm I think you mean sudo apt-get update to update your sources list.

@divx118 Yes, it was the apt-get update command that got the package to install. Thanks for the correction.


Update README.md with minor spelling fix

Fix delicious spelling

Thanks for pointing this out and fixing it!


[Discussion] Self-sandbox support with Linux Landlock LSM

🚧 This is blocked until kernel 5.19, which would allow more permissions necessary for Git to work
With this feature Gitea will limit FS access upon start to improve security. This only works on Linux 5.13 and higher with Landlock being enabled in config.
Rationale
Gitea interacts with user-supplied contents, can use external renderers for certain file types (again, files are user-supplied). So, to make the server more secure, use of mandatory access control is encouraged. Other types of LSM require administrator to set them up properly, like AppArmor and SELinux profiles. This could often be ignored when install is performed manually, so best security might not be enabled.
Solution
Linux kernel from version 5.13 onwards includes a new LSM module called Landlock, which helps user-mode processes to self-confine without any privileges necessary. Automatically enabling this with a syscall early during startup enables the sandbox on the caller process and child processes spawned by it later. The lock is permanent, so once the process has enforced its limits, it won't be able to either unlock itself nor allow something else. This makes Landlock a good measure of security, since it is automatically enabled on supported systems.
TODO:

[x] PoC
[ ] Status reporting in the admin panel
[ ] Flag to disable sandboxing in config
[ ] Show steps to enable if kernel is 5.13+ but lsm=landlock not passed
[ ] Do not set on platforms other than Linux or older kernels

(out of scope) Investigate sandboxing on other platforms, add AppArmor and SELinux

[ ] Testing

[ ] Basic functions
[ ] LFS
[ ] GPG and SSH
[ ] Custom renderers
[ ] DB engines (SQLite works, others do not write files I guess)
[ ] Run CI with sandboxing applied

Awaiting reviews on the idea, will finalize after design review.

Git operation fails with this library (https://www.kernel.org/doc/html/latest/userspace-api/landlock.html#file-renaming-and-linking-abi-1) ... Need to enable ABI v2 via another means in code and wait for kernel 5.19 to be released. Could this PR be kept open with this purpose in such case?

You'll need to make this optional and controlled by a setting.
You'll also need to make this not build on windows mode which is why drone is currently failing.

Yes, definitely. Currently this PR is only for discussion on self-configuration of sandbox, since during the implementation I found that until kernel 5.19 we won't be able to run Git as it does rename files

IMO there should be a wrapper program to setup the Landlock and then run Gitea, instead of making Gitea do more work than its goal. There could be other choices for security beside the complex AppArmor, for example, they can run Gitea in docker, which is totally isolated from the host.
And there are a lot of paths could be changed in config, although some paths are default to be in AppDataPath, but users can change their locations. And IIRC there are some hard-coded paths in Golang (eg: temp dir for uploading, the ca files in /etc). It's not an easy task to make them all work correctly in short time.

IMO there should be a wrapper program to setup the Landlock and then run Gitea, instead of making Gitea do more work than its goal. There could be other choices for security beside the complex AppArmor, for example, they can run Gitea in docker, which is totally isolated from the host.
And there are a lot of paths could be changed in config, although some paths are default to be in AppDataPath, but users can change their locations. And IIRC there are some hard-coded paths in Golang (eg: temp dir for uploading, the ca files in /etc). It's not an easy task to make them all work correctly in short time.

Wrapper program complicates the distribution and setup. My idea was to make Gitea more secure by default when possible. All the paths should be retrievable either from configuration or their constants early during startup.

There should be a build tag if it's Linux special feature. And I think we also need some tests?

It should be only build for Linux and only activated when kernel version >= 5,19 (or maybe higher, haven't tested yet).
But if the feature is wanted, I can continue effort in implementing this.

I do not think it's worth to introduce this feature to Gitea itself. Some reasons are in https://github.com/go-gitea/gitea/pull/20230#issuecomment-1174507237 . I can not see a clear and maintainable mechanism for it, there are a lot of paths.
The users (who concern security a lot) should be able to fine tune all security rules for Gitea by other programs, the POSIX philosophy is to keep things simple, make every program do what it should do, but not mix every feature into one app.

Well, yes. But Gitea has more knowledge of its own paths than a wrapper would do. Anyway, probably this solution is only worth it in case it's the default. If this would be a manually enabled feature, then why not systemd-nspawn or other mini-container system.


Changes to init.py and literal_value_generator.py

I am now able to import this using python 3.5.  I changed the reference to cStringIO and StringIO to io, and removed the from statement in init.py to only reference the module and not the specific class

Just need to test backwards compatibility of these changes. Great catch though, I haven't tested on anything > Python 2.7. Give me 24 hours...

Quick update here: This proposed change will break python 2.7 compatibility, I am working on a similar to change to support both 2.7 and 3.5.2. Stay tuned...

@travBoog I've created a branch for Python 3.5 support here
I've made some changes based on your feedback, and both problems (importing module issues & CStringIO Deprecation) have been addressed.
There are still a number of other issues with the branch not allowing functionality on python 3.5, like changes to list comprehensions (map, filter, etc...) that haven't been accounted for in this project. Please checkout this new branch, and open all future pull requests regarding python 3.5 support there!
Lastly, we need to prevent regression concerning python 2.7, so I will work on building some unit tests to allow us to test, and merge this branch back into master when we are confident it supports both 2.7 & 3.5.
Feel free to reach out to me via email<EMAIL_ADDRESS>


Patch 1

Here I changed the labels in chapter02 to make the Greek alphabets look better.

Thanks for the nice patch :)


Fix the bug in PR template

Purpose
The purpose of this PR is to fix #17
Goals
To fix the bug in PR template
Approach

Changed the directory of PR template

Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[x] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented on my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Nice job @Gimhan-minion


Bio renamed

I've renamed my bio, Can you add this? Help!

Thank you Saroj for the PR, Keep Contributing.:feelsgood:


Allow projects to register multiple metric types

Each metric probably needs to be a different class
Datasets will have to say which metric they map to
Queries should handle unit conversions and provide results in a clearly-defined metric

Example:

DPV capacity in MW
DPV profiles in h
then a query would (DPV capacity) * (DPV profiles) = DPV energy in MWh.

Another example:

Residential energy use in MWh
Number of households as a count
then (Residential energy use in MWh) / (Number of households) = Energy per household in kWh/household


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit fad9248:
:clock10: Pending: waiting for processors (24 builds ahead of you)
:warning: Docs Build is busy, currently there are 24 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit fad9248:
:clock10: Full build: the average full build time is 6 min(s) 34 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit fad9248:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


returnOrderStatus?

Hoping to get this in there:
https://docs.poloniex.com/#returnorderstatus
I'll try to write a patch myself if it's not something you can pull together quickly.
Thanks.

@swaylock, thank you for your contribution.


Wrong host_ptr set when creating images

According to the OpenCL1.2 SPEC 5.3.1(either version 1.2 or 2.x has this distriction), the parameter host_ptr of clCreateImage must be null if the parameter flags is neither CL_USE_HOST_PTR nor CL_COPY_HOST_PTR:

CL_INVALID_HOST_PTR if host_ptr is NULL and CL_MEM_USE_HOST_PTR or CL_MEM_COPY_HOST_PTR are set in flags or if host_ptr is not NULL but CL_MEM_COPY_HOST_PTR or CL_MEM_USE_HOST_PTR are not set in flags.

but here[link] a not-null pointer imageValues has been transfered into create_image_1d and clCreateImage:
else // Either CL_MEM_ALLOC_HOST_PTR or none
    {
        // Note: if ALLOC_HOST_PTR is used, the driver allocates memory that can be accessed by the host, but otherwise
        // it works just as if no flag is specified, so we just do the same thing either way
        if(gTestMipmaps)
        {
            cl_image_desc image_desc = {0};
            image_desc.image_type = CL_MEM_OBJECT_IMAGE1D;
            image_desc.image_width = imageInfo->width;
            image_desc.num_mip_levels = imageInfo->num_mip_levels;

            unprotImage = clCreateImage( context,
                                        image_read_write_flags,
                                        imageInfo->format, &image_desc, NULL, &error);
            if( error != CL_SUCCESS )
            {
                log_error( "ERROR: Unable to create %d level mipmapped 1D image of size %d (pitch %d, %d ) (%s)",(int)imageInfo->num_mip_levels, (int)imageInfo->width, (int)imageInfo->rowPitch, (int)imageInfo->slicePitch, IGetErrorString( error ) );
                return error;
            }
        }
        else
        {
            unprotImage = create_image_1d( context,
                                          image_read_write_flags | gMemFlagsToUse,
                                          imageInfo->format,
                                          imageInfo->width, ( gEnablePitch ? imageInfo->rowPitch : 0 ),
                                          imageValues, NULL, &error );
            if( error != CL_SUCCESS )
            {
                log_error( "ERROR: Unable to create 1D image of size %d pitch %d (%s)\n", (int)imageInfo->width, (int)imageInfo->rowPitch, IGetErrorString( error ) );
                return error;
            }
        }
        image = unprotImage;
    }

Besides, if set nullptr instead of imageValue, it would also needs to transfer 0 as row_pitch and slice_pitch due to OpenCL1.2 SPEC <IP_ADDRESS>:

image_row_pitch is the scan-line pitch in bytes. This must be 0 if host_ptr is NULL and can
be either 0 or >= image_width * size of element in bytes if host_ptr is not NULL.

This happened in files below:

test_conformance/images/kernel_read_write/test_iterations.cpp
test_conformance/images/kernel_read_write/test_read_1D.cpp
test_conformance/images/kernel_read_write/test_read_1D_array.cpp
test_conformance/images/kernel_read_write/test_read_2D_array.cpp
test_conformance/images/kernel_read_write/test_read_3D.cpp
test_conformance/images/kernel_read_write/test_write_1D.cpp
test_conformance/images/kernel_read_write/test_write_1D_array.cpp
test_conformance/images/kernel_read_write/test_write_2D_array.cpp
test_conformance/images/kernel_read_write/test_write_3D.cpp
test_conformance/images/kernel_read_write/test_write_image.cpp

Best regards!
Feb. 10. 2020

Closing as a duplicate of #918 that links a proposed fix.

Closing as a duplicate of #918 that links a proposed fix.


Switch to the new project system and CodeAnalysis 2.0

This switches this project to the new project system. We also reference code analysis 2.0 which allows us to add new C# 7 related features. this was the main motivation behind this. I also included @Nozziel's pull request #2319 in here to have some new C# 7 features to try this with.
The two main analyzer libraries target netstandard1.3 which is the lowest standard that the code analysis libraries work with. The Test library works with netcoreapp1.1 and the tester app with net46.
Todo:

[x] Use new project system in main libraries
[x] Switch to netstandard 1.3
[x] Update to CodeAnalysis 2.0
[x] Update xunit to an up to date version
[x] Fix all failing tests
[x] Fix package creation
[x] Fix VSIX creation
[x] Fix merge conflicts
[x] Fix Code Coverage
[x] Make sure AppVeyor works
[x] Clean up test references
[ ] (Fix all scripts in ./scripts)
[ ] (Try to make the command line build work with the vsix project by referencing Microsoft.VSSDK.BuildTools)
[ ] (Try the Churn Testing)
[ ] Consume our analyzers. This looks like a bug in the project system. It crashes the build when I try to consume the Stylecop.Analyzers package probably because there is a project in the solution with the same name.

@DotNetAnalyzers/stylecopanalyzers Can you take a look at this?

@pdelvo
I downloaded your NewProjectSystem branch as I was hoping for netcore sdk 1.0.0/netcore1.1 support.
I built your branch and installed the resulting nuget package in my project.
Building from visual studio 2017
I get no warnings
Building from the command line dotnet build
I got a load of these warnings
CSC : warning AD0001: Analyzer 'StyleCop.Analyzers.DocumentationRules.SA1642Cons
tructorSummaryDocumentationMustBeginWithStandardText' threw an exception of type
 'System.TypeLoadException' with message 'Could not load type 'System.Runtime.Se
rialization.Formatters.FormatterAssemblyStyle' from assembly 'mscorlib, Version=
<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e'.'. [C:\Users\mikes\Re
pos\Reports\src\Reports\Reports.csproj]

Superseded by #2370, in order to continue supporting Visual Studio 2015 (Roslyn 1.3 / C# 6) users.