HTTP params are included in the file names of downloaded files

Consider the following hypothetical deploy (copied from examples.md). The URIs have parameters appended, which is a requirement of my online file storage service, in order to have secure URIs.
I've found that Singularity saves these files with file names that include the parameters. For example, the jar file name is "helloworld-1.0-SNAPSHOT.jar?accessKey=123" after download. In stderr, I see "Error: Unable to access jarfile helloworld-1.0-SNAPSHOT.jar"
The version on my server is 0.4.2-SNAPSHOT.
Thanks in advance for your help. Let me know if you require any further details to reproduce.
{
    "deploy": {
        "requestId": "mesos-dropwizard-service",
        "id": "1",
        "command": "java -jar helloworld-1.0-SNAPSHOT.jar server example.yml",
        "resources": {
            "cpus": 0.1,
            "memoryMb": 128,
            "numPorts": 0
        },
        "uris": [
            "https://myCDNExample.com/releases/download/1.0/helloworld-1.0-SNAPSHOT.jar?accessKey=123",
            "https://myCDNExample.com/releases/download/1.0/example.yml?accessKey=123"
        ],
        "skipHealthchecksOnDeploy": false
    }
}

Hey @rwalsh849 -- this is actually a "feature" of the default Mesos executor (which just blindly downloads whatever URI(s) you provide). Here's a couple of workarounds you could try:

Try using a glob in your command (i.e. helloworld-1.0-SNAPSHOT.jar*)
Try bundling your files in a tarball -- the executor should automatically untar them for you, thus preserving the original filenames
Try using our custom SingularityExecutor instead -- it provides many benefits over the default executor, including:

embedded artifacts (i.e. directly embed the contents of your config YAML in the Deploy object)
downloads from S3 without having to generate a temporary URL

I'm personally biased towards using the SingularityExecutor, but it takes a little extra setup on your slaves in order to work. Check out https://github.com/HubSpot/Singularity/blob/master/Docs/slave_extras.md for more info, or feel free to ping me if you have specific questions.

Thanks @tpetr, these are all great suggestions for working around this. I just tested the glob approach and it works for me.
Thanks also for pointing me at the extras document, I'll consider this as a more sustainable solution.


VS Code doesn't remember find settings (actions.find)

VSCode Version:
1.8.0

OS Version:
Windows 10

Steps to Reproduce:

Press Ctrl+F, then Alt+C, Alt+W, Alt+R to toggle the options
Restart VSCode
Ctrl+F to inspect the settings again

Sublime, Notepad++ will keep the settings by default, at least we can get the option to save the settings in vscode.

I'm bringing this issue because of https://github.com/Microsoft/vscode/issues/8869, Ctrl+D behavior is  linked to these settings.

Let's track the setting persistence in #6158


Add CurtinSingapore

Please verify this university.

University official website URL: https://curtin.edu.sg/
Mail<EMAIL_ADDRESS>

@ShiYee01 First stage of verification passed, official domain is curtin.edu.sg as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@ShiYee01 Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Install sdf/1.8 to versioned path

🦟 Bug fix
Fixes a mistake from merging forward in #808.
Summary
The SDF_MAJOR_VERSION variables were all replaced with PROJECT_VERSION_MAJOR in https://github.com/ignitionrobotics/sdformat/pull/780, but when merging forward in #808, this replacement was forgotten in the sdf/1.8 folder, which did not exist in the sdf10 branch. This causes conflicts between the sdfomat-X packages on Ubuntu.
Checklist

[X] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[X] codecheck passed (See contributing)
[X] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Codecov Report

Merging #890 (2382182) into sdf11 (b0647c9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            sdf11     #890   +/-   ##
=======================================
  Coverage   88.91%   88.91%
=======================================
  Files          73       73
  Lines       11094    11094
=======================================
  Hits         9864     9864
  Misses       1230     1230

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 b0647c9...2382182. Read the comment docs.

Looks good. I wonder if we should alias SDF_MAJOR_VERSION to PROJECT_VERSION_MAJOR?

we still have it in the C++ API, but I thought we had eliminated all instances of it. I was wrong of course, but I don't see any more instances of it now, having checked again on these future branches

This pull request has been mentioned on Gazebo Community. There might be relevant details there:
https://community.gazebosim.org/t/new-ignition-releases-2022-03-25-fortress-edifice-citadel/1343/1

This pull request has been mentioned on Gazebo Community. There might be relevant details there:
https://community.gazebosim.org/t/new-ignition-releases-2022-04-13-fortress-edifice/1367/1


how to run an example on the arm-compute-library built for bare metal on windows?

Platform: armv7a
Operating System:
windows 10

Problem description:

Hi @irkingmaker
Examples are disabled for the bare_metal target because they require many system calls only present in operating systems.
Please take a look at the documentation for more details: https://arm-software.github.io/ComputeLibrary/v19.02/index.xhtml#S3_4_bare_metal

Thanks for the help.
Presently i am trying to build link independent binary of the arm_compute library using scons and arm-none-eabi-g++(version 8). The scons command is used for armv7, cortex-a9. I am facing the following issues-
1.(.text._ZN11arm_compute16NEConvolution3x3D2Ev[_ZN11arm_compute16NEConvolution3x3D5Ev]+0x30): undefined reference to vtable for arm_compute::INESimpleFunction' 2. (.text._ZN11arm_compute19NEConvolutionSquareILj5EED0Ev[_ZN11arm_compute19NEConvolutionSquareILj5EED5Ev]+0x1c): undefined reference to arm_compute::TensorAllocator::~TensorAllocator()

Hi @irkingmaker
This suggests that the linker can't find the symbols mentioned above in your comment, these missing symbols are part for the runtime library (  https://arm-software.github.io/ComputeLibrary/v19.02/architecture.xhtml#S4_1 ).
Could you please share the commands for building the library and your code using it?

Please find the attachments for the scons script(SConstruct.txt), linker description(CoreML.ld.txt) and the compilation issues i am facing. The compilation issues are present in error.txt. I have edited the code of neon_cnn example a little and saved it as TestCtrl_RunArmCompute.cpp.
Sconstruct.txt
coreML.ld.txt
error.txt

Hi @irkingmaker
I'd try to fix the first linker error:

From your build command:
arm-none-eabi-g++ -o CoreML_Binary.elf -Wl,-no-undefined --verbose -mcpu=cortex-a9 -mfloat-abi=hard -Bstatic -Ttext=0x7DA0000 -e_main_cust -ffunction-sections -fdata-sections -Xlinker --gc-sections --specs=nosys.specs "-LLibs-Wl,--start-group -lgcc -lc -lg -lm -lstdc++ -larm_compute_core-static -larm_compute-static -Wl,--end-group" -Wl,-TcoreML.ld begina.o Misc.o TestCtrl_RunArmCompute.o
It seems both TestCtrl_RunArmCompute.o and Misc.o were built with different setting from the ones you use for CoreML_Binary
Hope this helps.

I was previously using version 7 arm-none-eabi compiler. But after using version 8, the first linker error is solved. I am still facing issues with the other errors.
New Text Document (2).txt

The undefined reference errors were because of inappropriate order of linking of the libraries. In scons, i was not able to change the order of linkage of the libraries. Hence, by using make, I was able to build the library.
Now, while i am going through the example code of neon_cnn.cpp. I am not able to figure out how to initialize the layers with custom weights generated from a trained model?

Hi @irkingmaker
Good to know you fixed the linker errors, unfortunately for some toolchains the order in which you list the dependencies matters.
In order to help you, please provide more context for your question. Why are you not able to initialise the layers? What's actually the problem?

I am not able to understand how are weights inferred from a model loaded into layers in arm compute library. For example, in neon_convolution in conv3x3.configure-it is loading gaussian3x3 weights defined in the same file. How do we load weights from a different file ?

Hi @irkingmaker
The example you mention, examples/neon_convolution.cpp, does not load weights. It's just a 2D convolution where you can specify the transformation.
I'd suggest you take a look at examples/neon_cnn.cpp, although in this example the weights are not loaded from a file. You should copy the values from your weights file to the weights tensor after the call to allocate().

How do we copy the values from my weights file to weights tensor?

Hi @irkingmaker
Please take a look at the code examples showing how to copy data from/to ACL's tensors:
https://arm-software.github.io/ComputeLibrary/v19.02/architecture.xhtml#S4_6_4_working_with_objects
This assumes you have already loaded your weights from a file into a buffer.

How do i load the weights from .npy or .csv file ? i am not able to find the documentation or example to load the weights from .npy or .csv file to a convolution layer(or any other function)?
-I have got the .npy files from the python script provided by ACL for conversion of a pretrained model into .npy files.

Hi @irkingmaker
You should use libnpy to read the data from a file into a buffer and then copy that to an ACL tensor.
Take a look at libnpy https://github.com/llohse/libnpy and ACL NPYLoader: https://github.com/ARM-software/ComputeLibrary/blob/master/utils/Utils.h#L318

Closed by inactivity, reopen it or open a new issue if in need of support.


uses standard magento to get helper for supporting CE1.6

Pulling this change back into my repo because it's a handy one to have :)

+1 to merge this pull request.


Download videos only if they are with IMU signals

Thank you for creating and sharing this large-scale and high-quality dataset.
Is it possible to only download the subset videos with IMU signals rather than downloading all videos? I'm still waiting for the approval so haven't started the downloading process. I think one way to do that is firstly downloading the IMU data, collect the sample ids and use the ids to filter the full video dataset. But I wonder if there is any easier way than that.
Also, any info about the size of the subset videos with IMU signals?
Thank you in advance.

Hi! I'm not an author, but from my experience:

Is it possible to only download the subset videos with IMU signals rather than downloading all videos? I'm still waiting for the approval so haven't started the downloading process. I think one way to do that is firstly downloading the IMU data, collect the sample ids and use the ids to filter the full video dataset. But I wonder if there is any easier way than that.

If you're looking for ego data, both RGB and IMU come together in a .vrs file (check here). There is a tutorial with projectariatools in this repository.

Also, any info about the size of the subset videos with IMU signals?

Yes, it's here, there are sizes for each part within the table.
I hope I've been helpful 😄

For EgoExo4D: every video has IMU as @Peipi98 suggests.
For Ego4D: you will have to read the ego4d.json metadata file and retrieve the set of video uids with IMU (use the field has_imu). With this you can use the flag: --video_uids <video_uid_list> or save the list to a text file (each line has the video uid) and use --video_uid_file <file>; see here: https://ego4d-data.org/docs/CLI/#detailed-flags

Thank you! Yes, I downloaded the data by parsing ego4d.json.


trio.run_sync_in_worker_thread is deprecated

app_1  | /starbelly/starbelly/extractor.py:81: TrioDeprecationWarning: trio.run_sync_in_worker_thread is deprecated since Trio 0.12.0; use trio.to_thread.run_sync instead (https://github.com/python-trio/trio/issues/810)

A whole bunch of warnings while running tests:
/home/mhaase/.cache/pypoetry/virtualenvs/starbelly-T_MFzqrn-py3.7/lib/python3.7/site-packages/trio_asyncio/_base.py:20
  /home/mhaase/.cache/pypoetry/virtualenvs/starbelly-T_MFzqrn-py3.7/lib/python3.7/site-packages/trio_asyncio/_base.py:20: TrioDeprecationWarning: trio.hazmat is deprecated since Trio 0.15.0; use trio.lowlevel instead (https://github.com/python-trio/trio/issues/476)
    from trio.hazmat import wait_for_child

/home/mhaase/.cache/pypoetry/virtualenvs/starbelly-T_MFzqrn-py3.7/lib/python3.7/site-packages/rethinkdb/net.py:21
  /home/mhaase/.cache/pypoetry/virtualenvs/starbelly-T_MFzqrn-py3.7/lib/python3.7/site-packages/rethinkdb/net.py:21: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
    import imp

tests/test_downloader.py::test_http_get
tests/test_downloader.py::test_http_proxy_get
  /home/mhaase/code/hyperiongray/starbelly/starbelly/downloader.py:264: DeprecationWarning: verify_ssl is deprecated, use ssl=False instead
    session_args['connector'] = aiohttp.TCPConnector(verify_ssl=False)

tests/test_downloader.py::test_socks_proxy_get
  /home/mhaase/.cache/pypoetry/virtualenvs/starbelly-T_MFzqrn-py3.7/lib/python3.7/site-packages/aiohttp_socks/connector.py:76: DeprecationWarning: SocksConnector is deprecated. Use ProxyConnector instead.
    username=username, password=password, **kwargs)

tests/test_downloader.py::test_socks_proxy_get
  /home/mhaase/.cache/pypoetry/virtualenvs/starbelly-T_MFzqrn-py3.7/lib/python3.7/site-packages/aiohttp_socks/proxy/socks5_proxy.py:41: DeprecationWarning: Parameter family is deprecated and will be ignored.
    family=family

tests/test_extractor.py::test_crawl_extractor
  /home/mhaase/code/hyperiongray/starbelly/starbelly/extractor.py:81: TrioDeprecationWarning: trio.run_sync_in_worker_thread is deprecated since Trio 0.12.0; use trio.to_thread.run_sync instead (https://github.com/python-trio/trio/issues/810)
    extracted_urls = await trio.run_sync_in_worker_thread(

tests/test_login.py::test_login_form
tests/test_login.py::test_login_with_captcha
  /home/mhaase/code/hyperiongray/starbelly/starbelly/login.py:178: TrioDeprecationWarning: trio.run_sync_in_worker_thread is deprecated since Trio 0.12.0; use trio.to_thread.run_sync instead (https://github.com/python-trio/trio/issues/810)
    forms = await trio.run_sync_in_worker_thread(partial(

tests/test_login.py::test_login_form
  /home/mhaase/.cache/pypoetry/virtualenvs/starbelly-T_MFzqrn-py3.7/lib/python3.7/site-packages/sklearn/linear_model/_logistic.py:764: ConvergenceWarning: lbfgs failed to converge (status=1):
  STOP: TOTAL NO. of ITERATIONS REACHED LIMIT.

  Increase the number of iterations (max_iter) or scale the data as shown in:
      https://scikit-learn.org/stable/modules/preprocessing.html
  Please also refer to the documentation for alternative solver options:
      https://scikit-learn.org/stable/modules/linear_model.html#logistic-regression
    extra_warning_msg=_LOGISTIC_SOLVER_CONVERGENCE_MSG)

tests/test_storage.py::test_storage
  /home/mhaase/code/hyperiongray/starbelly/starbelly/storage.py:98: TrioDeprecationWarning: trio.run_sync_in_worker_thread is deprecated since Trio 0.12.0; use trio.to_thread.run_sync instead (https://github.com/python-trio/trio/issues/810)
    body = await trio.run_sync_in_worker_thread(functools.partial(


[interop] Unexpected cross-language object printing behavior

When objects from Python (and possibly other languages) are printed (either directly in the console or via console.log()), the other language's printing behavior is expected. However, Graal.js uses a custom format for printing foreign objects. The same is also true the other way around: JS objects are printed in Python without consulting toString(). This is unexpected behavior from the user's point of view. Maybe the new interop messages (e.g. toDisplayString()) can help to make this more consistent
Repro session
$ polyglot --jvm --shell
GraalVM MultiLanguage Shell 20.1.0
Copyright (c) 2013-2019, Oracle and/or its affiliates
  JavaScript version 20.1.0
  Python version 3.8.2
python> class A:
      +   def __repr__(self):
      +     return "Hello from Python"
      +
python> A()
Hello from Python
python> print(A())
Hello from Python
python> str(A())
'Hello from Python'
python> js>
js> Polyglot.eval("python", "A()")
{} # `Hello from Python` expected
js> console.log(Polyglot.eval("python", "A()"))
{} # `Hello from Python` expected
js> class B { toString() { return "Hello from JS" } }
js> console.log(new B())
Hello from JS
js> python>
python> import polyglot
python> polyglot.eval(language="js", string="new B()")
<foreign '{}'> # `Hello from JS` expected
python> print(polyglot.eval(language="js", string="new B()"))
<foreign object at 0xeabecf5> # `Hello from JS` expected

/cc @timfel @eregon @LeonBein @teresalasarow

As a data point after discussion with @timfel @fniephaus and a few others this is what made sense for Ruby:

foreign.to_s returns InteropLibrary#toDisplayString()
foreign.inspect tries to format the foreign object as if it was Ruby, notably showing members and their value, without recursion (with extra info to show it's foreign, since inspect is "debugging output")

The current implementation in TruffleRuby is here.
toDisplayString(rubyObject) does rubyObject.inspect (if side effects allowed). Which isn't really consistent with the other direction, but far more useful in practice than calling to_s.
Python's to_s is str()and inspect is repr().
Not sure about JS, does it have only toString()?
One consideration I had (more relevant if a language only has one conversion to string) is if we can't find anything useful to show in inspect then calling toDisplayString might be good. Also played with just always appending toDisplayString() in inspect, but that gets kind of verbose/repetitive, e.g., for an array. "Array" is basically the only clear "interop type" right now, so maybe simply including toDisplayString() except for arrays (which likely don't have much extra info besides the array elements) might be a good compromise.
cc @woess

As a note, it's useful for polyglot programmers to both see the foreign's view of an object (to get the full information about the foreign object) and the current language's view of the object (e.g. to find which members are available, integrate better with local objects, etc).


Update maintainer list

Adding @CalCraven as a maintainer of this feedstock.

@conda-forge-admin, please update team


Modified arlo object to make smarter HTTP requests for an async envir…

…onment (conn pool, blocking)
Description:
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hi @mwd102,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

No description 🤔

This also looks like something that needs to be fixed upstream in the pyarlo package.

Ok. This was the related issue https://github.com/home-assistant/home-assistant/issues/13176

We should fix this upstream. If upstream package is dead as the other issue describes, we should switch package to one with an active maintainer.


Update docs

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 86.246%

Files with Coverage Reduction
New Missed Lines
%

mirar/utils/pipeline_visualisation.py
1
90.48%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
9958

Relevant Lines:
11546

💛  - Coveralls


Reduce the number of digits shown in UI

It probably doesn't make much sense to include fractions in the numbers displayed in the UI.
ref: https://news.ycombinator.com/item?id=29596537

I think we probably do want one or two fractional digits, at least for larger units like seconds, but definitely not 4 like we have currently.

Can we just vary the fraction so that we aim for 3 significant figures total when the non-fractional part is less than 1000? (And when its >= 1000, then the fractional part should be hidden.)
Is that the wrong way to look at this?

not directly related, but we probably also want to format durations over one or two minutes as minutes + seconds, rather than as a large number of seconds, which it looks like std::time::Duration's fmt::Debug implementation doesn't do. So, at some point, we're definitely going to end up writing our own duration formatter, and we can probably implement significant figures logic there as well?

I think we probably do want one or two fractional digits, at least for larger units like seconds, but definitely not 4 like we have currently.

Depends... 5m20s maybe, but 3.245ms... probably not. I think 3ms would make more sense there.


Latest osmnx

Update to work with latest version of osmnx, issue #1

@dwastberg Thanks very much for these commits and the pull request. I'd love to know why you're interested in osmuf. Closes #1


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1009 ms

Resolved: Bofrost.lu performance has improved in c9f8c63 after 9 minutes.


why the memory is not work? who can help me!

Issue you'd like to raise.
`
class SimpleChat:
    def __init__(self) -> None:
        self.llm = ChatOpenAI(
            temperature=0,
            model="gpt-4-0613",
            openai_api_key="sk-",
            openai_api_base = "https://---",
        )
        self.memory = ConversationBufferMemory(memory_key="chat_history", return_messages=True)

    def get_tools(self):
        return [
            Tool(
                name="Search",
                func = Tooluse().get_google().run,
                description="useful for when you want to search for something on the internet",
            )
        ]

    def get_agent(self):
        conversational_agent = initialize_agent(
            agent=AgentType.CHAT_CONVERSATIONAL_REACT_DESCRIPTION,
            tools=self.get_tools(),
            llm=self.llm,
            verbose=False,
            memory=self.memory,
        )
        sys_prompt = """You are a chatbot for a Serverless company AntStack and strictly answer the question based on the context below, and if the question can't be answered based on the context, say \"I'm sorry I cannot answer the question, contact<EMAIL_ADDRESS>        prompt = conversational_agent.agent.create_prompt(
            system_message=sys_prompt,
            tools=self.get_tools(),
        )
        conversational_agent.agent.llm_chain.prompt = prompt
        return conversational_agent

    def chat_with_bot(self,input_message):
        agent = self.get_agent()
        print("agent",agent)
        response = agent.run(input_message)
        return response

this is my code,and why the memory is not work?? anyone can help me, thanks!
Suggestion:
the doc of langchain is so sucked!

You need to pass in the MessagesPlaceholder for the memory variable:
prompt = conversational_agent.agent.create_prompt(
    system_message=sys_prompt,
   extra_prompt_messages=[MessagesPlaceholder("history")],
    tools=self.get_tools(),
)

@keenborder786 it cant work for me,and i use the https://python.langchain.com/docs/modules/agents/how_to/add_memory_openai_functions demo, its not work too, here is my code:
class SimpleChat:
    def __init__(self) -> None:
        self.llm = ChatOpenAI(
            temperature=0,
            model="gpt-3.5-turbo-0613",
            openai_api_key="sk-",
            openai_api_base = "https://",
            )
        self.agent = self.get_agent()

    def get_tools(self):
        search = SerpAPIWrapper(serpapi_api_key="")
        llm_math_chain = LLMMathChain.from_llm(llm=self.llm, verbose=True)
        return [
            Tool(
                name="Search",
                func=search.run,
                description="useful for when you need to answer questions about current events. You should ask targeted questions",
            ),
            Tool(
                name="Calculator",
                func=llm_math_chain.run,
                description="useful for when you need to answer questions about math",
            )
        ]

    def get_agent(self):
        agent_kwargs = {
            "extra_prompt_messages": [MessagesPlaceholder(variable_name="memory")],
        }
        memory = ConversationBufferMemory(memory_key="memory", return_messages=True)
        agent = initialize_agent(
            self.get_tools(),
            self.llm,
            agent=AgentType.OPENAI_FUNCTIONS,
            verbose=True,
            agent_kwargs=agent_kwargs,
            memory=memory,
        )
        return agent

    def chat_with_bot(self,input_message):
        print("agent",self.agent)
        response = self.agent.run(input_message)
        return response

###and when i use chat_with_bot function,here is the AI response:
【user】: hi
【ai】: Hello! How can I assist you today?
【user】: my name is bobyang
【ai】: Hello Bob! How can I assist you today?
【user】: whats my name?
【ai】: I'm sorry, but I don't have access to personal information.

i dont know why?

I fixed it, it was my fault... I shouldn't have put the memory inside a function, that way the memory would be cleared every time. It's better to put the memory as a global variable in the class.


Not all functions are part of namespace

I am not sure why but there are many functions that are not found in the exported namespace.

All of the functions had '@export added at their start, and while this does modify the namespace, it is apparently insufficient to generate the necessary md files in the MAN folder.  I added titles and descriptions to all of the missing functions, and they all now show up.  Feel free to improve the documentation wherever you can, and claim the functions your wrote by adding your name as an author.


error at server start up

Did you try these troubleshooting steps?
Yes
Hardware/Software

iPhone: X
iOS: 14.0.2
Apple Watch: Serie 6 44mm
watchOS: 4.0.2
Windows: Windows 10 Home 1909
App: unknown
Server: unknown

To Reproduce
I've downloaded the Github-Folder and the Windows executable into the same folder.
Upon executing the HDS-Overlay-win.exe it shows the following lines:
Error: listen EACCES: permission denied <IP_ADDRESS>:8080
at Server.setupListenHandle [as _listen2] (net.js:1296:21)
at listenInCluster (net.js:1361:12)
at Server.listen (net.js:1447:7)
at Function.listen (C:\snapshot\apple-watch-health-data-server\node_modules\express\lib\application.js:618:24)
at Object. (C:\snapshot\apple-watch-health-data-server\public\app.js:73:18)
at Module._compile (pkg/prelude/bootstrap.js:1320:22)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1218:10)
at Module.load (internal/modules/cjs/loader.js:1047:32)
at Function.Module._load (internal/modules/cjs/loader.js:935:14)
at Function.Module.runMain (pkg/prelude/bootstrap.js:1375:12) {
code: 'EACCES',
errno: -4092,
syscall: 'listen',
address: '<IP_ADDRESS>',
port: 8080
}
The application has crashed. If you need help, please create an issue on the GitHub page.
Expected behavior
Startup server to connect the Watch-app to
Additional context
node-version is v12.19.0

You only need the executable not the source code.
Are you running another server on port 8080? It's weird that you're getting an EACCESS error instead of an EADDRINUSE error.  Everything works great now. Thank you!


[Bug]: Dialog - Using aria-describedby="undefined" triggers warning

Environment
Using Stackblitz for reproduction, after trying on macOS with Firefox.
Link to minimal reproduction
https://stackblitz.com/edit/5nwtfn?file=src%2FApp.vue
Steps to reproduce

Open the Dialog demo code
Removing the <DialogDescription> component in the template
Warning in the console, which is expected
Setting aria-describedby="undefined" in the <DialogContent>
Warning stills there

Describe the bug
I would like to be able to build a Dialog without any DialogDescription inside (visible or not). The doc says that by putting aria-describedby="undefined" in DialogContent it should be ok. (https://www.radix-vue.com/components/dialog.html#description)
Expected behavior
According to the docs, I was expecting a warning when removing it. But I expected the warning to go with the aria-describedby="undefined" on the DialogContent.
Context & Screenshots (if applicable)
No response

@Ericlm Was this issue solved for you after updating to V1.9.6, please? Because I have updated the package and I get the following warning:

And here's my code:

From the warning, I read that this is the DialogPortal that have "aria-describedby" attribute.
Everything is working well with the aria-describedby on the dialog content only 🙂

The base "DialogContent" component you get from 'Shad-cn/vue" uses the "DialogPortal" in its template. When passing "aria-describedby" to the "DialogContent" component it's also passed to the "DialogPortal" for some reason. I'm unsure if it's an issue or was intended as such.


DS1074Z/DS1104Z working features

In the list of working features it lists "discovery" as working. Does that mean both via mDNS and LXI?
I am asking because I'm able to discover it via LXI, but not via mDNS. Could very well be  a network issue on my side though.

It means one or the other or both.
If I remember correctly, the Rigol DS1000Z series does not feature mDNS discovery.

Hmm interesting. It does sort of seem to have the port open (but it is UDP, so not entirely sure).
But that does answer my question


[8.x] Adds first-level test traits setUp/tearDown (opt-in)

What?
Allows the developer to include and reuse traits that automatically set-up and tear-down in each test, when declared at first-level.
Given a reusable test WithExamplePost:
namespace Tests\Feature\Concerns;

use App\Models\Post;

trait WithExamplePost
{
    protected $post;

    protected function setUpWithExamplePost()
    {
        Post::factory()->createOne();
    }

    protected function tearDownWithExamplePost()
    {
        $this->post = null;
    }
}

The test class implementing InitializeTraits, will automatically call setUpWithExamplePost after the application is created, and tearDownWithExamplePost before is destroyed.
<?php

namespace Tests\Feature;

use App\Models\User;
use Illuminate\Contracts\Testing\InitializeTraits;
use Illuminate\Foundation\Testing\RefreshDatabase;
use Tests\TestCase;

class PostTest extends TestCase implements InitializeTraits
{
    use RefreshDatabase;
    use Concerns\WithSubscribedUser;

    public function test_post_is_visible()
    {
        $this->get('post/' . $this->post->id)->assertOk();
    }
}

Since this is an additive opt-in feature, no test will break unless the interface is added on tests classes.
Why?
There are three keys for this implementation:

Reusable traits out of the box, no need to implement the feature by the developer.
Opt-in
Runs after the application is created, and before it's destroyed.
Only works for first-level traits. Nested traits are not affected (like in PHPUnit), so initialization is controllable.

BC?
Nope, opt-in additive.
Notes
I decided to use an interface-check in the TestCase rather than adding a trait because:

Avoids getting the trait into the initializers array (or even alone by itself, making no sense)
Avoids polluting a test properties or methods if it were to check them.

Didn't I see this before?
Kinda

I think this would be a nice addition. I did want to mention that you can accomplish this right now with the following:
trait MyTrait
{
  /** @before */
  protected function setUpMyTrait()
  {
    $this->afterApplicationCreated(function() {
      // Perform setup (must happen in afterApplicationCreated because
      // everything with the @before annotation runs BEFORE setUp() is called
    });
  }

  /** @after */
  protected function tearDownMyTrair()
  {
    // Perform tear down (no need for closure, because this runs before tearDown()
  }
}

But I think the confusion about how the @before and @after hooks are ordered makes it a pain—it'd be nice for it to just be handled by the framework.

I also do it in some of my testing traits but feels less straightforward using annotations.

Ah I didn't immediately remember that you could do this using the annotations. In that case I wouldn't add this to the core framework. There's also a slight chance of breakages with this PR if people have already defined such methods.

If there is a minimal collision risk, I can push this to 9.x then, and remove the interface.

Ah I didn't immediately remember that you could do this using the annotations. In that case I wouldn't add this to the core framework. There's also a slight chance of breakages with this PR if people have already defined such methods.

I still feel like the @before and @after annotation behavior is confusing due to the way they're applied. Adding framework-level support for dynamically applying traits in a predictable way would be great (it's something I proposed a few years ago, as well)
I suppose another option would be to add a new @afterApplicationCreated and @beforeApplicationDestroyed annotation that's Laravel-specific…

I actually just dug around some more and I was wrong, the @after annotation will cause the method to be called after the test class' tearDown() method, which means you won't have access to any of the mocked Laravel app. You're better off adding afterApplicationCreated and beforeApplicationDestroyed closures inside a @before hook if you need the Laravel app to still be set up.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Monitoring Jaeger

Opening this in the Operator repository instead of the main repo, as the outcome might involve changes to the operator.
Currently, the Jaeger Operator adds some annotations to the Jaeger deployments it creates (Collector, Agent's DaemonSet, Query), like:
https://github.com/jaegertracing/jaeger-operator/blob/83aafae113f63c2bf4808c44471f610dbe38d5ee/pkg/deployment/all-in-one.go#L48-L53
While this works out of the box with the Prometheus instance brought by Istio, it requires extra configuration when the Prometheus Operator is used, even with kube-prometheus.
Right now, the only way I could get it working with Prometheus from kube-prometheus is by manually creating a ServiceMonitor resource, with an accompanying extra Service (with simplest as the Jaeger instance):
apiVersion: v1
kind: Service
metadata:
  labels:
    app: jaeger
    app.kubernetes.io/component: service-collector
    app.kubernetes.io/instance: simplest
    app.kubernetes.io/managed-by: jaeger-operator
    app.kubernetes.io/name: simplest-collector
    app.kubernetes.io/part-of: jaeger
  name: simplest-collector-monitoring
  namespace: monitoring
spec:
  ports:
  - name: admin-http
    port: 14269
    protocol: TCP
    targetPort: 14269
  selector:
    app: jaeger
    app.kubernetes.io/component: all-in-one
    app.kubernetes.io/instance: simplest
    app.kubernetes.io/managed-by: jaeger-operator
    app.kubernetes.io/name: simplest
    app.kubernetes.io/part-of: jaeger
  type: ClusterIP
---
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: simplest-pm
  namespace: monitoring
spec:
  endpoints:
  - interval: 30s
    port: admin-http
  selector:
    matchLabels:
      app: jaeger

Questions:

Is the current state enough? Is it acceptable to ask users to create a Service + ServiceMonitor in order to monitor Jaeger with kube-prometheus?
Should we create an extra service automatically? Should we create a ServiceMonitor automatically if the CRD is present in the cluster?
@objectiser mentioned that Istio is transitioning to Prometheus Operator, so, a properly configured ServiceMonitor could be sufficient, without requiring an extra service

@objectiser mentioned that Istio is transitioning to Prometheus Operator, so, a properly configured ServiceMonitor could be sufficient, without requiring an extra service

If the Service is shipped with Isitio in the future, then yes, you might not need to create that, but you obviously need some Service to use ServiceMonitors.
As a user, I'd probably would be fine with adding a ServiceMonitor manually for now, given you provide and example. That's pretty much how the entire kube-prometheus project works.

If we can get it to work, looks like PodMonitors would be better, as would enable scraping of sidecars (e.g. jaeger agent) - based on discussion here: https://discuss.istio.io/t/prometheus-operator-podmonitor/2695

Yes. Indeed, if you would only need the Service for metrics and for nothing else, then you can skip that step with PodMonitors now. Make sure you have Prometheus Operator v0.31+ available, before starting to work on that.

With the help from @metalmatze, I was able to get PodMonitor working, once a fix similar to https://github.com/coreos/kube-prometheus/pull/159 was applied.
We have then two ways to monitor Jaeger:

When Istio is present, it builds the proper configuration to scrape data out of Jaeger based on the pod annotations
Manually creating a PodMonitor like the following:

apiVersion: monitoring.coreos.com/v1
kind: PodMonitor
metadata:
  name: simplest
  namespace: monitoring
spec:
  podMetricsEndpoints:
  - interval: 5s
    port: "admin-http"
  selector:
    matchLabels:
      app: jaeger

Right now, there's no action to be taken from the Jaeger Operator's perspective, so, I'm closing this one.


Set default console log level to "warn"

Something a bit more sensible for normal use

i think the default level should remain trace, as thats the default level in the gcloud logger https://github.com/bedrockio/instrumentation/blob/main/src/loggers/pino.js#L57 but well you could update them both to info ?

Sorry yes "warn" doesn't make sense, "info" does.
The gcloud logger is different as it's interested in logging everything (well, arguably... I'm honestly not sure if it should be but in theory you might want it to log everything... at least it's configurable I guess that's the point).
For the console you don't want to log everything, no tool has "verbose mode" as the default.
While I'm on it what's the difference between "trace" and "debug"? If it's to maintain parity with the gcloud logger then I guess I get it but the use case isn't really clear.


Spigot 1.17 jar structure changes

In the 1.17 update, the spigot jar structure changed for nms (craftbukkit is still the same), you now don't need reflection. Instead everything being in one package with name of the version, it's now structurized in different packages.
Before

After

You can get the nms (and craftbukkit) by implementing org.spigotmc:spigot:1.17.1-R0.1-SNAPSHOT and also including the mavenLocal() repository in gradle


I'm begging you guys! Please add Mario and Luigi voice clips!

I know you guys have gotten issues like this one. But i'm begging you, PLEASE PLEASE add voice clips for the characters as a last update! I've been wanting this since I started playing. Plus I've seen the files in the commits that you guys do, so I know you guys have them. So pretty please add them in!

we have not gotten the sound system functioning and don't plan to until vanilla is finished.

Ok, that makes sense actually. Bc you're trying to get everything from vanilla into MMO, right?


update axi full examples with correct rx_buffer size

use this document to update the examples with correct buffer size
https://github.com/chipsalliance/aib-protocols/blob/main/axi4-st/doc/axi4_latency_rx_buffer_sizing_guide.pdf

Updated RX FIFO size based on axi4_latency_rx_buffer_sizing_guide.


Does not Formatter work well on single-line/multi-line block?

(Please excuse my poor English.)
I think there is no similar issues, but I'm sorry if there is duplicate.
$ crystal -v
Crystal 0.22.0 (2017-04-20) LLVM 4.0.0

I think crystal tool format does not work well in the following cases on block.
case1: single-line block with newline
crystal tool format does not work in the following cases.
a = [1, 2, 3].map { |i|
  i * i
}

# or

a = [1, 2, 3].map do |i|
  i * i
end

In both cases above, I expect the following because the block has single-line.
a = [1, 2, 3].map { |i| i * i }

case2: multi-line block with braces
In following case,
a = [1, 2, 3].map { |i|
  j = i + 1
  j * j
}

I think prefer do...end over  {...} because the block has multi-line.
a = [1, 2, 3].map do |i|
  j = i + 1
  j * j
end

Is there the reason that crystal tool format dose not work well in the above cases?

Are you asking for the formatter to be opinionated on whether blocks span multiple lines or not, and whether they use do/end instead of {}? I'm for that change, but I don't think there's a robust way to figure out whether a 1-line block can be collapsed into an inline block. I would like to enforce do/end for non-inline blocks and {} for inline blocks in the formatter though.

See also "The Semantic Rule": https://github.com/bbatsov/ruby-style-guide/issues/162. The semantic rule says to use {} for any block that returns a value (e.g.,map, reduce, etc.), and do...end for all other blocks (each, etc.).
I don't wholeheartedly agree with the rule, but bbatsov's comment about enforcing such rules seems pertinent to me. Often times, the choice between do...end and {} is more than just the line-count or size, and I think there are enough users on each side that trying to enforce one style (however idiomatic) would annoy/alienate many of them.
There's also the issue of left-/right-association of blocks, where the difference is actually semantic, not just stylistic:

The difference between using do ... end and { ... } is that do ... end binds to the left-most call, while { ... } binds to the right-most call.

tl;dr: I don't think having the formatter modify the syntax used for the block is a good idea ({} vs do...end).

I'd much rather have a rule that can be enforced using crystal tool format than no rule like we have currently. I really enjoy using crystal tool format heavily as part of my development cycle and the stricter it is the better. gofmt has had a lot of acclaim for being really strict and i'm inclined to agree with them: I don't need to worry about formatting any more, it's not my job - it's the formatters - and what it says goes. This approach works best if everyone uses the strict formatter, and go seems to be achieving that goal. So i'd rather this kind of strictness was included in the crystal default formatter.

I'm not sure the formatter should be changed. In general the formatter only inserts whitespace and newlines, and removes more than two consecutive newlines to just two. But text is never changed. The few cases I can think now is removing extra () in calls like foo.bar(), or adding trailing commas in array literals that span multiple lines.
Imagine I want to write a block with multiple lines. I'll use | as the cursor:
[1, 2, 3].map do |x|
  a = x + 1
  |
end

I want to continue writing after that, but I have this OCD where I press Ctrl+S to save the code very often (in fact I tend to do that a lot ^_^). The formatter sees that there's only one line and changes it to:
[1, 2, 3].map { |x| a = x + 1 }

Arrrghh...! The formatter is getting in my way. I don't think this is nice.
This is the reason why the formatter only changes stuff that doesn't get in your way, and I think it should continue to behave like that.
I do, however, think that the formatter could change { ... } to do ... end if it sees that it spans multiple lines. So this:
[1, 2, 3].map { |x|
  x + 1
}

would automatically change to:
[1, 2, 3].map do |x|
  x + 1
end

Right now the formatter inserts newlines when you write do ... end. This:
[1, 2, 3].map do |x| x + 1 end

is changed to this:
[1, 2, 3].map do |x|
  x + 1
end

With this new rule the formatter will make sure that do ... end always appears in separate lines, and that { ... } can never appear in separate lines (they will be transformed to do ... end).
In general, I think this about code with { ... } and do ... end:
# good (simple inline { ... })
array.map { |x| x + 1 }

# bad ( { .. } with multiple lines, should use do/end or be in the same line, the formatter will do the former )
array.map { |x|
  x + 1
}

# good ( do/end in multiple lines, it doesn't bother that there's just one expression in it )
array.map do |x|
  x + 1
end

# good ( do/end in multiple lines with multiple expressions )
array.map do |x|
  a = x + 1
  a * a
end

# bad ( do/end in a single line, the formatter splits into multiple lines )
array.map do |x| x + 1 end

With the proposed change there will never be "bad" code.
What do you think?

I'm quite a fan of conveying additional intention via the choice of do/end vs {}. Similar to Weirich's rule I often use it to communicate whether I care about the callled methods return value or its side-effect. While this heavily correlates with single and multiline blocks in my experience, that's not always the case. Also I do format side-effect blocks with a single line over three lines usually, which has the benefit of giving them a higher visibility.
I would hate for the formatter to destroy such additional hints, and even make it impossible to add such nuances.
Sent from my OnePlus A0001 using FastHub

I want to continue writing after that, but I have this OCD where I press Ctrl+S to save the code very often (in fact I tend to do that a lot ^_^).

This is huge for me. I ended up disabling the formatter in Sublime less than and hour after the first time I wrote Crystal code because it was making changes that I didn't expect, and caused me to repeat space characters constantly. Worse yet, when I would repeatedly save in a medium-sized project, the formatter wouldn't have run the 2nd time by the time I "fixed" the file, so I would make a change and it would suddenly be reverted as soon as the second format run finished. Not a good experience, at all. I don't remember what these changes were, though. Likely space-before-bracket for blocks, like map{ becomes map {. Personal preference, but a strong enough one that I would disable formatting for.
I would be okay with the formatter making more changes if it wasn't happening as I was writing the code. Or perhaps there could be different "levels" of formatting aggressiveness, so that only minor things like indentation change when I save in my editor, and then I can run a more aggressive formatter as a pre-commit hook or something.

@asterite that was pretty much exactly what I was proposing. I see the reasons for not transforming blocks from single/multi line now but I agree with you on the do/end and braces transformation.

@jhass I think formatting based on semantics is a bad idea. It's usually pretty obvious whether the block contains a side effect or an expression by reading it's contents. On top of that it means that I have to think about one more thing when writing my code. Formatting is pretty seperate from what I usually think about when writing code so it'd be hard to remember to context-switch into formatting mode every time I wrote a block. On top of that, this rule cannot be enforced automatically which makes it easy to miss when you've got it wrong in code reviews. Perhaps it's fine when you're working on a personal project but I don't know of any large project which uses this rule. In fact I had never heard of it before you linked it to me.
Most people who write ruby stick to the ruby style guide's recommendation to use {} for inline blocks and do/end for non-inline blocks. Most people who write crystal keep this tradition. If the formatter was changed to replace {} with do/end, it would help me immensely when refactoring single-line blocks into multi-line blocks because I could just press return at the beginning of the block contents, save, and the block would be formatted correctly and consistently. For that reason, I think that automating consistent formatting for the many is a better default than protecting semantic formatting for the few.

@faultyserver I just fixed a bug in the formatter where it would remove a newline if it had spaces in it. I switched to another computer where the text editor wasn't configured to automatically trim whitespace from newlines and it was driving me a bit crazy :-P. So maybe that's why it was annoying for you, I don't know. Let's see if in the next release you find the formatter a bit less annoying.

@asterite Oh thanks for this, in retrospect I think i've been hitting this bug and not realising it!

Thank you for a lot of opinions.
I think case1 is transformed too much, so I agree with @asterite's proposal (https://github.com/crystal-lang/crystal/issues/4504#issuecomment-305985504).
However I would like to hear the opinions of others a little more, too.

FYI https://github.com/crystal-lang/crystal/pull/4517#issuecomment-310840350
Since #4517 was reverted either this should be demilestoned/reopen or have a other closing reason.

This should be reopen.

The milestone is already past due. Can we relabel this please?


Fix highway safety demo bugs

For #3396
Change List

Fix crashing bug in PathTesselator when a path consists of two identical points; add test case
Fix AttributeTransitionManager handling of normalized attributes

Coverage increased (+2.7%) to 82.857% when pulling 277ae6c476ab81916f4b60d65ed660c92cab6572 on x/path-layer-fix into 2adcf3ad095faffa7392c18b83abcfa2922aeeed on master.


consistentHash is not working if traffic to pod is tls

consistentHash is not working if traffic to pod is tls, same configuration works OK using http
Affected product area (please put an X in all that apply)
[X] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
This request should always hit the same pod, but it only does if I use http and not htts to connect from envoy to the pod.
curl -vk -H 'X-User: Peter' -H 'X-Workload-Selector: sticky' https://<IP_ADDRESS>:31390/
sticky.zip
Use attached configuration to reproduce, one uses tls and the other one does not.
Version (include the output of istioctl version --remote and kubectl version)
istioctl version --remote
client version: 1.3.0
control plane version: 1.3.0
kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:54Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:05:50Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
How was Istio installed?
helm template install/kubernetes/helm/istio --name istio --namespace istio-system | kubectl apply -f -
Environment where bug was observed (cloud vendor, OS, etc)
Local virtual machines running CentOS 7
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.

I'm experiencing the same issue. Is there any update on this???

@jaesquivel  I have some updates.
I applied the following yaml:
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  labels:
    name: https-example
  name: originate-tls-and-stickiness
spec:
  host: https-svc
  trafficPolicy:
    portLevelSettings:
    - port:
        number: 8443
      tls:
        mode: SIMPLE
      loadBalancer:
        consistentHash:
          httpHeaderName: client-id

applying the consistentHash in portLevelSettings the configuration worked.
I'm terminating the TLS on the gateway, but I'm adding this tls origination rule, which also is applying the stickiness now.


document.compareDocumentPosition A great method to determine if one element contains another for goa...

document.compareDocumentPosition
A great method to determine if one element contains another for goals such as resolving duplicate id scenarios.

This issue was imported from Google Moderator
Moderator votes: +3
Issue added by JAB Creations on 2013-01-22
To vote this issue up or down, simply include +1 or -1 in your comment.

+1

Now available at http://caniuse.com/#feat=comparedocumentposition


Rename repo to NbodyGradient.jl

Should rename to keep with Julia conventions.
Also, we could add to the package registry: https://github.com/JuliaRegistries/Registrator.jl/#registrator

@langfzac  I have a repository with the name NbodyGradient.jl.  Can you remind me what happened with that?

@ericagol I think that was the first attempt at packaging the code. We ended up making too many changes to this repo, so I just decided to start over by forking this one. It should be fine to archive or delete entirely.

Okay, I've deleted.  I'm happy for you to rename this repo.

Hmm, I can still navigate to ericagol/NbodyGradient.jl. Are you sure it's been deleted? I just removed my fork.

Oh, sorry, I just deleted it locally.
Eric

On Mar 20, 2021, at 10:28 AM, Zach Langford @.***> wrote:

Hmm, I can still navigate to ericagol/NbodyGradient.jl. Are you sure it's been deleted? I just removed my fork.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@langfzac Okay, I changed it to https://github.com/ericagol/NbodyGradient_legacy.jl
We can delete later!
I'll change NbodyGradient -> NbodyGradient.jl

Okay, done!


images position fixed

position of images inside category is changed

is this my fault ? i dont think so if there please tell me what happened


Minimap plugin doesn't seem work with MediaElement

I tried to implement wavesurfer library with minimap plugin but it seems it only works fine with WebAudio backend, don't draw the waveforms and process with WebAudio backend.
Is it any known issue and any solutions? I will dig into the issue but if anyone faced it and have any solution already.
My use-case is one main player on footer and waveforms with progress showing on listing and actions will be sync.

@meathanjay can you provide sample code you're using?

For me, the Minimap plugin did work with a MediaElement backend.

no feedback, closing.


Feedback for “Assets”

Is there an endpoint that shows all supported networks and their identifier for the Mintscan API? I have tried /v1/:network/assets using some networks like akash, axelar, kava, quicksilver but keep getting the NOT_SUPPORTED_CHAIN message. Would be helpful if there was an easy way to retrieve this.

@samuel-poon
Sorry for the late answer.
Thank you for providing feedback.
I have added the mentioned content to the document.
https://docs.cosmostation.io/apis


Moving towards tests independent of legacy GUI output

This is a follow-up to #221  and related to #233, edited as we move towards a PR.
In order to write good tests for the new external drives API, we should decide on gold standard datasets. The current implementation uses HNN GUI output based a params-file that generates a fixed sequence of _ArtificialCells (and thus corresponding gids; the _legacy_mode flag in Network is needed to match this behaviour).
Some questions to answer here, in no particular order:

[ ] At what level should seeding occur? Would it be reasonable for each drive to have a unique seed (e.g. based on its unique name)? This would allow adding drives in any order, yet retaining the event times. Alternatively, there should be a global seed for each Network (not the current gid-based seeds).
[x] What do we consider proof-positive that hnn-core can replicate GUI results? Are the current (#221) examples sufficient? Do we need more cases before we are satisfied that the new API can replace the old?
[ ] Should we have a single dpl.txt-file generated using all the possible drives (and biases) turned on? Or rather create several test datasets based on realistic use cases such as one for evoked, one for poisson (PING gamma example, includes tonic bias), one for bursty (possibly a new beta-example), etc. ?
[ ] ???

Or rather create several test datasets based on realistic use cases

I think this would be great to have!!

Do we need more cases before we are satisfied that the new API can replace the old?

I would let folks use it for a bit. Would be great if we can use it in a class for teaching or something and see what issues people face. One thing we need to fix definitely is #239 before even talking about any replacements ;-) We can change the default to use the new API but still leave the option for the old behavior for a couple of months at least.

Would it be reasonable for each drive to have a unique seed

I like this option better because the order of adding the drives will not matter then ...

Or rather create several test datasets based on realistic use cases

I think this would be great to have!!

Do we need more cases before we are satisfied that the new API can replace the old?

I would let folks use it for a bit. Would be great if we can use it in a class for teaching or something and see what issues people face. One thing we need to fix definitely is #239 before even talking about any replacements ;-) We can change the default to use the new API but still leave the option for the old behavior for a couple of months at least.

Would it be reasonable for each drive to have a unique seed

I like this option better because the order of adding the drives will not matter then ...

I like the idea of having multiple test datasets. Here's a list of possible ground-truth test datasets based off of drives/biases explored in the tutorials that we could create. Obviously, we don't need to test every combination of drive types so I've marked the examples I think we should use as the minimal number of necessary test datasets with *. Feel free to modify or add to this list.

evoked*
poisson (gamma via random excitation and intrinsic network E/I interactions)
poisson + tonic bias (gamma modulated by tonic bias)*
single bursty (gamma via rhythmic drive)
single bursty (alpha via prox. rhythmic drive)
multiple bursty (beta via coincident prox. and dist. rhythmic drive)*

I like the idea of having multiple test datasets. Here's a list of possible ground-truth test datasets based off of drives/biases explored in the tutorials that we could create. Obviously, we don't need to test every combination of drive types so I've marked the examples I think we should use as the minimal number of necessary test datasets with *. Feel free to modify or add to this list.

evoked*
poisson (gamma via random excitation and intrinsic network E/I interactions)
poisson + tonic bias (gamma modulated by tonic bias)*
single bursty (gamma via rhythmic drive)
single bursty (alpha via prox. rhythmic drive)
multiple bursty (beta via coincident prox. and dist. rhythmic drive)*

To what extent is this issue still relevant? Modify the issue title and move to 0.4 if still relevant?

Maybe we can consolidate all of these seed + legacy mode related issues under one issue?

Agree!


Bug while deleting birthday/wedding anniversary fields in contact

Hi all,
we are using the EWS-Api and have a problem when deleting the fields Birthday and WeddingAnniversary in contacts.
If we set the birthday date using the EWS-Api the birthday can be deleted.
When setting the birthday in outlook and we use EWS to delete the birthday nothing happens, the birthday isn't deleted in the contact.
Setting the birthday in outlook this automatically creates a recuring appointment "Birthday of ...". This isn't created when setting the birthday using EWS.
The exact same happens when using the WeddingAnniversary.
To get an idea where the problem is located we tested the following:
We created a contact and set the birthday using EWS, the WeddingAnniversary was entered in outlook.
Than we deleted both fields. The birthday was deleted, the WeddingAnniversary was not.
Here is the xml snippet which was sent to the exchange server:
	<t:DeleteItemField>
		<t:FieldURI FieldURI="contacts:WeddingAnniversary"/>
	</t:DeleteItemField>
	<t:DeleteItemField>
		<t:FieldURI FieldURI="contacts:Birthday"/>
	</t:DeleteItemField>

Response from exchange server:
	<m:ResponseMessages>
		<m:UpdateItemResponseMessage ResponseClass="Success">
			<m:ResponseCode>NoError</m:ResponseCode>
			...
			<m:ConflictResults>
				<t:Count>0</t:Count>
			</m:ConflictResults>
		</m:UpdateItemResponseMessage>
	</m:ResponseMessages>

As you can see both fields should be deleted, but only the birthday is.
Seems that the problem is located on the exchange server.
Any ideas or suggestions?
Many thanks, Christoph

It's not a bug. When deleting the three fields Birthday, BirthdayLocal and the EntryID of the recurring appointment the brithday will be removed.
See:
https://social.technet.microsoft.com/Forums/office/en-US/18d2fbd2-caac-4ba2-9a13-f02cadace739/bug-while-deleting-birthdaywedding-anniversary-fields-in-contact-using-ews-api?forum=exchangesvrdevelopment


Delete button confirmation

The delete button on the admin panels does not have any "CONFIRM". This is kinda(very) bad. If someone makes a mistake webkom would need to shell to fix it, and that's not very confidential.

Update: The delete button on the admin panel does in fact require confirmation, and always has. Issue solved:)


Scrolling Native Video Element on Android

The Cordova OpenTok plugin uses the native OpenTok SDKs and places native iOS and Android views for the Publisher and Subscriber on top of a WebView. On Android, when you scroll on the WebView, the native video element does not and the video is stuck in its initial position.

@msach22 Do you have a bit of an idea what should be done here to get this fixed? Maybe if you point us into a direction we can take a look and send a PR.

Fixed by: https://github.com/opentok/cordova-plugin-opentok/pull/28


added test wgs reads

The reads in mt_1.fq.gz and mt_2.fq.gz comes from the normal sample of the synthetic dataset 3 of the ICGC-TCGA DREAM challenge. Reads aligning to the mitochontrion were extracted from the aligned BAM file, and converted to fastq format. The dataset is 2x101 paired illumina reads, In total 4597 read pairs. Average coverage after removing duplicate is around 110x, but varies wildly. This provides suffcient depth to test variant calling downstream.

Hi @dakl,
This is brilliant, thanks!


raft: fix race in WaitGroup usage

Add to zero-valued WaitGroup must be called before Wait. Also without
Lock this code is can process request after n.stop().

Current coverage is 55.27% (diff: 100%)

Merging #1458 into master will increase coverage by 0.02%

@@             master      #1458   diff @@
==========================================
  Files            82         82
  Lines         12832      12835     +3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           7090       7095     +5
+ Misses         4763       4761     -2
  Partials        979        979

Powered by Codecov. Last update 5270b79...0a8eeec

LGTM


Roll engine 5ded729f6aa6..bb2bfe67baad (1 commits)

git@github.com:flutter/engine.git/compare/5ded729f6aa6...bb2bfe67baad
git log 5ded729f6aa6..bb2bfe67baad --no-merges --oneline
2019-10-24<EMAIL_ADDRESS>Roll src/third_party/skia 3f4e52c4071b..d0b2029c2d7c (3 commits) (flutter/engine#13328)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Auto-roller completed checks. About to merge.


Renesas rcar: move PINCTRL config to drivers Kconfig

Move PINCTRL config activation from SoCs defconfig to drivers Kconfig for Renesas rcar socs
I was only able to test serial driver functioning  (on h3ulcb board) but I enabled the config for all rcar drivers using pinctrl API.
I'd like to get some feedback from the A cores support team (@lorc @xakep-amatop ) before these changes to be merge.
Fixes: #78619

@aaillet Shouldn't the changes be in one commit instead of two?
Because if I stay on the first commit, some code will become unbuildable. It’s generally better to ensure every commit leaves the repository in a working state.


 I should have used apache-arrow-15.0.1 tag or maint-15.0.1 branch to run dev/release/05-binary-upload.sh. (I used main instead.)
I'm re-running dev/release/05-binary-upload.sh on apache-arrow-15.0.1 to fix verify-rc-binaries-apt-linux-amd64.

Done. Re-run verify-rc-binaries-apt-linux-amd64.

There seems to be a different error for Windows builds on test_dateutil_tzinfo_to_string:
         tz = dateutil.tz.gettz('Europe/Paris')
>       assert pa.lib.tzinfo_to_string(tz) == 'Europe/Paris'
E       AssertionError: assert 'Europe/Monaco' == 'Europe/Paris'
E         - Europe/Paris
E         + Europe/Monaco

@jorisvandenbossche @AlenkaF have you seen this error before?

There seems to be a different error for Windows builds on test_dateutil_tzinfo_to_string:
         tz = dateutil.tz.gettz('Europe/Paris')
>       assert pa.lib.tzinfo_to_string(tz) == 'Europe/Paris'
E       AssertionError: assert 'Europe/Monaco' == 'Europe/Paris'
E         - Europe/Paris
E         + Europe/Monaco

@jorisvandenbossche @AlenkaF have you seen this error before?

I haven't seen it before and also can't reproduce it on MacOS.
As mentioned on Zulip channel, there was a new release of the dateutil package. The version of python-dateutil:

on AppVeyor build is 2.8.2:
https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/49256840?fullLog=true#L465
on verify-rc-binaries-wheels-windows build is 2.9.0
https://github.com/ursacomputing/crossbow/actions/runs/8103088008/job/22164107523#step:6:208

I do not see how the changes in the new dateutil version would affect the Windows builds though ...

@ursabot please benchmark

The benchmarks failed because they couldn't build the pyarrow wheel due to https://github.com/apache/arrow/issues/40386.

Thanks @austin3dickey ! I am creating the 15.0.2 release which only contains 4 fixes at the moment, 3 of them are CI/build issues that won't affect performance.
I will run the benchmarks there.


Rename "name" in Zone model to "id"

Fixes #14, but not sure if this breaks something elsewhere 🤔

It's mostly down to just testing this properly 😊 No ETA unfortunately
Any chance you could give it a shot in your project as well? That everything still works? Would be hugely appreciated!  If you're using composer, you could e.g. replace the Zone.php file in vendor/upcloudltd/upcloud-php-api/lib/Model/Zone.php with this one from this branch: Zone.php

Awesome. Just tested, works perfectly:

Great to hear, and thanks for testing! We will run some internal automated tests and hopefully those pass and we can merge this

The Travis CI build is canceled. It seems to be fixed.

Is there any ETA on this? I still have it hardcoded but would really like to change this.

Sorry for the delay! Thanks for testing this @Cannonb4ll (and others) 😊 Merging!

Thank you @Darep, will there be a release published with this PR?

Yes! Though, not just yet! I don't have access to packagist so will have to consolidate with others and hopefully will have new release later this week :)

Version 1.0.3 now released :)

@Darep Thank you, can confirm it fully working, will be updating our hardcoded code into the API call in Ploi.


Release notes for 2.0.58

Changes for 2.0.58

OPS Build status updates of commit 054ddf1:
:clock10: Preparing: average preparing time is 56 sec(s)

OPS Build status updates of commit 054ddf1:
:clock10: Incremental building: average incremental building time is 13 min(s) 37 sec(s)

OPS Build status updates of commit 054ddf1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/release-notes-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

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.

OPS Build status updates of commit a4e7942:
:clock10: Preparing: average preparing time is 56 sec(s)

OPS Build status updates of commit a4e7942:
:clock10: Incremental building: average incremental building time is 13 min(s) 37 sec(s)

OPS Build status updates of commit a4e7942:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/install-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

docs-ref-conceptual/release-notes-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

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.


error The widget with key "groq_model_name" was created with a default value but also had its value set via the Session State API.

I received this error in the sidebar: The widget with key "groq_model_name" was created with a default value but also had its value set via the Session State API.
I also received this error only when crew starts with groq: litellm.exceptions.BadRequestError( # type: ignore
litellm.exceptions.BadRequestError: litellm.BadRequestError: LLM Provider NOT provided. Pass in the LLM provider you are trying to call. You passed model=llama3-8b-8192
Pass model as E.g. For 'Huggingface' inference endpoints pass in completion(model='huggingface/starcoder',..) Learn more: https://docs.litellm.ai/docs/providers

ok solved
crewBot.md


base16-bytestring out of bounds

See https://github.com/commercialhaskell/stackage/issues/5649.
I note that I am the "owner" of hie-bios on Stackage. That feels wrong. @jneira - feel free to tag yourself in my place.

I was just about to point to @fendor as a good candidate for this :wink:


input value doesnot change (no response) when click to select a date

The datapicker widget shows up, but clicking got no response, the  value does not change at all.
Besides, language not working.
    <?= $form->field($model, 'birth_date')->widget(
        DatePicker::className(), [
            // inline too, not bad
             'inline' => true,
            // 'language' => Yii::$app->language,
             // modify template for custom rendering
            'template' => '
{input}
',
            'clientOptions' => [
                'autoclose' => true,
                'format' => 'yyyy-MM-dd'
            ]
    ]);?>

@zhanglianchengdotcom the language needs to be set according to the locales that the jquery plugin has not Yii::$app->language. Please, check your browser for the error.
Probably you have an error on your javascript thats why values are not changing. On another note, this is an inline calendar, autoclose won't work.

@tonydspaniard
Thank you very much!
I don't know why it doen't work or why it works, but finally it works indeed. :smile:


On edit and cancel, edit handles decouple from polygon/line

I have this strange behaviour with polylines and polygons (but not with other shapes) where the edit handles decouple from the polygon/line.
Using leaflet 0.7:
Draw a line, then go to edit it.  Drag one of the handles, then "cancel" the edit - the line goes back to where it was originally and the handles disappear (as expected).
If I go into edit again, I find the handles are where they were when I cancelled the edit.  The line itself is where it was originally.  See attached.
Any idea how this can happen?  I've taken all custom code relating to leaflet.draw out of my project.  It could be some other js interfering, but I can't find any.

I made this happen once and I didn't remember how to replicate it. Thank you!
This is a bug, it's centered around how the intermediary shapes are saved in edit mode.

I notice it doesn't happen on the demo, so wondered if it was something I had done, but have searched endlessly and can't find anything.  Is it environmental?  I'm on Chrome 55 btw.

I think the demos are not getting the updated cdnjs files. That's a publish process thing I didn't anticipate.

I mean it may be. I know there is something not updating. It might just be the jsfiddles.

I have the same issue, the following seems to reproduce

Create a polyline and finish
Select the Edit option
Edit the polyline, moving the vertexes at the latlngs on the polyline works ok
Moving the intermediate vertexes causes the issue

I have also noticed that setting "window.L_NO_TOUCH = true" to get the smaller DivIcons for the vertexes (I am not keen on the larger icons when using a mouse) then clicking on the last vertex does not end the drawing and the only way to end the line is to click on the Finish option.  Even with the large touch vertexes it appears the click has to be direct in the centre so perhaps the tolerance is slightly out.
On the up side this is an excellent plugin and I thank you for all your efforts in creating it.

I get the same problem ( line disconnected from the handles) when I grammatically do a setLatLngs() on my line.

I get the same problem ( line disconnected from the handles) when I grammatically do a setLatLngs() on my line.

I get the same problem ( line disconnected from the handles) when I grammatically do a setLatLngs() on my line.

Anyone got a work around for this?  Or an ETA for a fix?
Thanks!


New feature: reverse translate

Hi nice library, it could be a nice feature enabling Jovanotti to translate from its slang.
Input Feffantafei => Sessantasei.
Jovanotti Will thanks us all.

I'd like to work on this but in order to avoid turning proper f's to proper s' I think we need a dictionary-based lookup to increase accuracy 😬


feat: add umi create4everlandUploader

add an uploader implementation relying on 4EVERLAND

Hi there, thank you for you contribution.
However, whilst we implemented some storage plugins as reference implementations, the idea is that each storage provider can create and maintain their own Umi plugins without having to inject code into the Umi monorepo.
This encourages the growth of the Umi ecosystem and helps us focus on the core development of the Umi framework.
Thank you for your understanding.


Do not work.    rm !(.foo|.bar|*.baz) bash: !: event not found

Hi,  I found this did not work when I tested on my Mac. The result is as follow.
bash-3.2$ rm !(*.foo|*.bar|*.txt)
bash: !: event not found

bash-3.2$ ls
1gist-project.md        2test.md                4text.txt

bash-3.2$ rm !(*.md)
bash: !: event not found

➜   zsh --version
zsh 5.2 (x86_64-apple-darwin16.0)
➜   rm !(*.txt)
zsh: no matches found: !(*.txt)

Using bash version 4.3.46(1) on Ubuntu  is ok.

It works but only for a specific version of the shell.


Fix push-create SSH bugs

Fix #10142
Fix #10143
Shamelessly taking advantage of Drone to run the tests instead of setting up an SSH environment locally. :eyes:

Codecov Report

Merging #10145 into master will increase coverage by 0.02%.
The diff coverage is 76.92%.

@@            Coverage Diff             @@
##           master   #10145      +/-   ##
==========================================
+ Coverage   43.39%   43.42%   +0.02%
==========================================
  Files         576      576
  Lines       79628    79640      +12
==========================================
+ Hits        34558    34583      +25
+ Misses      40791    40782       -9
+ Partials     4279     4275       -4

Impacted Files
Coverage Δ

cmd/serv.go
2.84% <0%> (-0.05%)
:arrow_down:

routers/private/serv.go
35.39% <100%> (+2.06%)
:arrow_up:

services/pull/pull.go
32.43% <0%> (-1.51%)
:arrow_down:

models/gpg_key.go
55.37% <0%> (+0.55%)
:arrow_up:

modules/queue/workerpool.go
46.61% <0%> (+1.06%)
:arrow_up:

modules/queue/unique_queue_disk_channel.go
54.48% <0%> (+1.92%)
:arrow_up:

routers/repo/http.go
41.32% <0%> (+2.56%)
:arrow_up:

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 7dcd305...8bb2c12. Read the comment docs.

@jolheiser please send backport


fix: 修复浏览器窗口多次放大后表格渲染模糊 close #2884

👀 PR includes

🐛 Bugfix

[x] Solve the issue and close #2884

📝 Description

系分 VisualViewport resize 场景下 Mac 触控板和浏览器窗口的区分, 避免相互冲突设置错误的 DPR
🖼 Screenshot

Before
After

🔗 Related issue link

🔍 Self-Check before the merge

[ ] Add or update relevant docs.
[ ] Add or update relevant demos.
[ ] Add or update test case.
[ ] Add or update relevant TypeScript definitions.

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

Project coverage is 80.81%. Comparing base (ecdc9c8) to head (ed89cfd).
Report is 432 commits behind head on next.

Additional details and impacted files
@@            Coverage Diff             @@
##             next    #2897      +/-   ##
==========================================
+ Coverage   75.77%   80.81%   +5.03%
==========================================
  Files         257      180      -77
  Lines       11994    10412    -1582
  Branches     2464     2360     -104
==========================================
- Hits         9088     8414     -674
+ Misses       1398      554     -844
+ Partials     1508     1444      -64

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

:tada: This PR is included in version @antv/s2-v2.0.0-next.28 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


PT Run activation shortcut, replace Window Search

Summary of the Pull Request
This PR adds a new mode for PT Run that allows it to act more like a Windows Search replacement. It was implemented in a way to try to not interfere in any way with the current model, as some really like the way it is.
This new mode DOES require elevated PT (Just like some of the other global shortcuts). That is why in this mode you don't need to pick any other options/settings, and that's nice.
This is the DEFAULT mode:

Here it is "Power Search", mode:

Also, the message and view of the warning/info will change based on whether PT is currently elevated:

Verbiage/naming needs work.
PR Checklist

[X] Closes: #17906
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Dev docs: Added/updated

Detailed Description of the Pull Request / Additional comments
I understand this is not a simple PR because some people might not want this functionality.

Since (the great!) Windows Vista, Start Menu and Windows Search have been joined. This was a great thing, but it changed what "windows key" did fundamentally. Some people use it to bring up the menu, other use it to be the fastest way to search.
Using this new "Power Search" mode, does not prevent access to "Windows Search". It's still there with Win+S.
An essential goal was/is to make sure 100% previous Win modifiers still work. E.g. Win+E, Win+X, ...

@htcfreek, @jaimecbernardo, @stefansjfw
This might be a divisive PR. Please let me know what it takes to get this one accepted!

I zhink the default mode should be the custom hotkey. As I understand currently you made it the other way.
We should have a warning bar or some other type of hint that replacement needs elevation.

And please update the PR description based on our current template!! The checkboxes have valid use cases.

I zhink the default mode should be the custom hotkey. As I understand currently you made it the other way.

Yes, the legacy mode certainly would be the default. I swapped the images, I will correct that.

We should have a warning bar or some other type of hint that replacement needs elevation.

We should, but we then also need that for the other plugs.  I will address this!

What is happening if you choose replacement mode and start PT without elevation. Does the code fallback in this case?

So far as I can tell, all of the hotkeys (shortcut guide and others?) just don't work, and the user is never told. To be clear, elevated is not needed for the hotkey to work in general. It's just that the hotkey will not work if you have an elevated program in the foreground and PT is not also elevated. This will be explained in the "warning bar" you requested above.

And please update the PR description based on our current template!! The checkboxes have valid use cases.

Sure thing. I can.

We should have a warning bar or some other type of hint that replacement needs elevation.

We should, but we then also need that for the other plugs.  I will address this!

What is happening if you choose replacement mode and start PT without elevation. Does the code fallback in this case?

So far as I can tell, all of the hotkeys (shortcut guide and others?) just don't work, and the user is never told. To be clear, elevated is not needed for the hotkey to work in general. It's just that the hotkey will not work if you have an elevated program in the foreground and PT is not also elevated. This will be explained in the "warning bar" you requested above.

In this case I am not sure if we need the info bar. Misunderstood you first and thought the shortcut only works in admin mode.

Come on @jaimecbernardo, greenlight this thing!

Misunderstood you first and thought the shortcut only works in admin mode.

I don't want to beat this into the ground but, I think that if something works and also does not work, based on the foreground apps permission level, it's confusing enough to say, "it does not work".
I will say this another way, BOTH the current custom shortcut and new mode will always work if you never have an elevated app in the foreground. I think this is hard enough to convey to the end user that we really should say PT Run requires elevated PT, and that is the default method.
Inverting the PT admin setting means that it will use it by default and if a user decided NOT to use the default, then only then warns that something might not work.
In any case, all the above is just icing on the cake and verbiage, I am not good with. So, I have made some changes to these messages, seen in the screenshot above. I am happy with the above but if this is not what we want, I am certainly happy change based on some specific suggestions.

Misunderstood you first and thought the shortcut only works in admin mode.

I don't want to beat this into the ground but, I think that if something works and also does not work, based on the foreground apps permission level, it's confusing enough to say, "it does not work".
I will say this another way, BOTH the current custom shortcut and new mode will always work if you never have an elevated app in the foreground. I think this is hard enough to convey to the end user that we really should say PT Run requires elevated PT, and that is the default method.
Inverting the PT admin setting means that it will use it by default and if a user decided NOT to use the default, then only then warns that something might not work.
In any case, all the above is just icing on the cake and verbiage, I am not good with. So, I have made some changes to these messages, seen in the screenshot above. I am happy with the above but if this is not what we want, I am certainly happy change based on some specific suggestions.

Let's have a look from @jaimecbernardo and wait for his opinion and thoughts.

This personally breaks my workflow since I use <win> to open start menu without intending to search. Why did you choose binding to <win> compared to something like javascript -> URI as seen in @krlvm/BeautySearch?

As mentioned in the issue, this is something that's likely not going to be accepted.
It's been discussed before and at the time the decision was not to do it.

Yes, just wishful thinking as I felt the implementation was both "good" and "optional". But I totally understand! In fact, if this mode of operation is deeded not inline project goals, that's not a terrible thing. Because maybe a fork, trimmed down to just PT Run running in this mode is simpler for a lot of people that just want either "Start Menu" replacement or just "better Windows Search".
I am of course not wanting to maintain that project. That sounds like real work!

The team's looking into the 0.60 release cycle right now, as this PR is something that needs further discussion after that.
Please have a little patience ;)

I understand and will chill out, unless crying like a baby helps this get into 0.60, because I'll do it =)
So, thanks for your (and team's) patience with me.

This personally breaks my workflow since I use <win> to open start menu without intending to search.

You are right and I understand. If you don't want this mode (because you use the Windows Start Menu) then you should ignore this option and use the default. Like many PowerToys settings, if you don't want/need to alter you experience, don't enable that PowerToys option.  This is the spirit of PowerToys. I actually have most of the PowerToys tricks disable. Just like you, I like my current workflow in many regards.

Why did you choose binding to <win> compared to something like javascript -> URI as seen in @krlvm/BeautySearch?

This seems like something that just makes the Windows Search look better but be the same. PT Run has much more power.

I just want to bump this again, to see where it stands. Also, to reiterate, this will be off by default, so nobody is affected by default.

I just want to bump this again, to see where it stands. Also, to reiterate, this will be off by default, so nobody is affected by default.

Sorry for the wait. This is still in consideration. Overriding Start Menu is not something that we can release lightly ;)

Hi, @jefflord ,
The decision here is that there might be too many unintended effects from overriding the Windows key.
So this can't really be accepted.
Other shortcuts, like Win+S (search) or Win+R (run) can be overridden, but overriding the Windows key is a no go design wise for PowerToys.

Thanks for the update.
I certainly understand that making this a "supported" feature or configuration is not without risks and "breaking Windows" is just not an option. I do appreciate the consideration.
As a last-ditch effort, hear me out... Is there a place in PT/PTRun for experimental or unsupported features? Features or options that do not normally appear on the settings screens and not supported when in use?
I ask because, I would love to know if there is a way hide this new "activation mode" option from the settings menu, but enable it via some other means?
So, is it possible that we could update this PR, hiding this option from the interface, and provide a hidden way to enable it?
Side note: As you can see, I will be sad to see this dream die. I am getting used to my custom activation shortcut of Win+Space, but I have ask, how did ALT+Space become the default?

This wouldn't be accepted as a change in the repo, but if you want to try it locally, how about turning centralized keyboard hooks on and then changing "%localappdata%\Microsoft\PowerToys\PowerToys Run\settings.json" to have this config for the shortcut?
"open_powerlauncher":{"win":false,"ctrl":false,"alt":false,"shift":false,"code":91,"key":""} (91 is the left win key)
It works for me on Win 10.

@jaimecbernardo
Hmm, thanks but I am not looking for a way to do this. The PR does this, and it does it correctly.
The suggestion that you have will not work because it will have every single side effect you can think of. It breaks all "Windows logo key keyboard shortcuts". This is why this PR was so tricky to do and why I expect it has not been done before. The PR does MORE than just change the UI to allow the user to set the binding you mentioned.
It was imperative that using Win alone to activate PT Run should never-ever break any "Windows logo key keyboard shortcuts". Based on you suggested hack, maybe that was not clear.
The PR I have allows all "Windows logo key keyboard shortcuts" to still work.
The fact that you sent such a rudimentary non-solution as a suggestion makes me think the PR was never even examined.
I won't try to drag this out, but will say, this is a feature that has been requested before me and likely will be requested again after me, and this PR implements it properly and in a 100% optional way. It would be sad to see it be killed based out of misunderstanding.
Site note: I originally updated the UI to allow selecting just Win as the activation shortcut (something you know it does not allow right now). However, I decided to leave that 100% alone and make it a completely new option (seen above). The reason it was done this way was to..

Make sure it cannot affect the current code or users in any way, at all.
Cannot be "accidentally" enabled without understanding it's a new "activation mode".
Removes the odd questions regarding "centralized shortcut" and "full screen" that most users don't understand.

Since this feature was asked for by more than just me, has been implemented as an optional feature with no "unintended effects" (that I am aware of), perhaps we can reconsider this PR?

This feature is optional, and would not break my workflow. There are also multiple methods to access to the standard Win start menu, even using "Win" to activate PT Run.

We've brought this back to discussion to check if it was possible to consider this PR if it was done in a way that was JSON-activated only, was well isolated and made it clear in the logs that it was being used.
However, it's been decided against, since this is something that the development team would be asked to support and deal with possible unintended consequences, after consulting with other teams.
Thanks for the effort 😄 , but our hands are tied here. 🤷

@jaimecbernardo thanks for the update and I agree that the total cost of ownership here is hard to calculate. Dreams are crushed... (JK 😉!)
Anyway, if this PR were accepted, it actually might not be seen in the proper light because it can exacerbate our elevated-process/focus bugs, which are troubling me. I think all are related.
https://github.com/microsoft/PowerToys/issues/19687
https://github.com/microsoft/PowerToys/issues/19182
https://github.com/microsoft/PowerToys/issues/19152
https://github.com/microsoft/PowerToys/issues/18450
Again, thanks!


Temporary workaround to re-enable single-channel throughput tests

Make BIG smaller until we figure out big message issues

FWIW, I think that this temporary workaround will not need to last long. I think that #6412 is a guide for what to do next.

is this still needed?

Not sure. Let me determine if it is.
On Thu, May 5, 2016 at 7:57 PM Jan Tattermusch<EMAIL_ADDRESS>wrote:

is this still needed?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/6403#issuecomment-217337124

After changing scenario_config.py significantly, this change needs to be basically rewritten. Unassigning myself for now.


Flannel will not work unless UDP ports 8285 and 8472 are allowed for …

…all hosts
When using udp backend, flannel uses UDP port 8285 for sending encapsulated packets.
When using vxlan backend, kernel uses UDP port 8472 for sending encapsulated packets.
Make sure that your firewall rules allow this traffic for all hosts participating in the overlay network.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Please delete this note before submitting the pull request.
For 1.15 Features: set Milestone to 1.15 and Base Branch to dev-1.15
For Chinese localization, base branch to release-1.12
For Korean Localization: set Base Branch to dev-1.14-ko.<latest team milestone>
Help editing and submitting pull requests:
https://kubernetes.io/docs/contribute/start/#improve-existing-content.
Help choosing which branch to use:
https://kubernetes.io/docs/contribute/start#choose-which-git-branch-to-use.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/assign @zacharysarah

/unassign

/approve
Ping @kubernetes/sig-network-pr-reviews for a technical LGTM

LGTM for technical review.

/lgtm


✨ Re-export Starlette's WebSocketException and add it to docs

✨ Re-export Starlette's WebSocketException and add it to docs

Gracias :)


Automatically update planet sidebar information every now and then

Fix for the planet sidebar not updating as mentioned in #30
I added a define in config.h to determine how often the sidebar should update the text (every frame looks a bit too hectic IMO).

Very nice :) to be honest though, I reckon the interval is still a bit too small - how about a second?

Changed to 1 second. I think it's better now :)

Cool - thanks


[WIP] Upgrade webpack to v5

[WIP]
current progress

[x] Track and remove DeprecationWarning in latest webpack v4.
[x] Upgrade webpack to v5
[x] Remove @types/webpack as webpack v5 has type bulit in.
[x] Update webpack.main.ts

[x] Remove progress-bar-webpack-plugin not compatible with webpack v5, and can be replaces with webpack --progress.
[x] Upgrade ts-loader from v7 to v8 to avoid DeprecationWarning in webpack v5.
[x] Upgrade webpack-node-externals from v1 to v2 to avoid DeprecationWarning in webpack v5.
[x] Update devtool (in webpack.main.ts) for webpack v5: "cheap-eval-source-map" > "eval-source-map"
[x] Update externalsPresets/externals  (in webpack.main.ts) for webpack-node-externals v2/webpack v5, see https://github.com/liady/webpack-node-externals/issues/82

externalsPresets: { node: true },
externals: nodeExternals(),

[x] Update webpack.renderer.ts

[x] Upgrade mini-css-extract-plugin to v1.3.1 to avoid DeprecationWarning in webpack v5.
[x] Upgrade terser-webpack-plugin to v5.0.3 to avoid DeprecationWarning in webpack v5.
[x] Remove TerserPlugin options cache:true is not valid in v5.0.3, remove parallel:true which is default, remove sourceMap: true as it should be enabled via devtool.
[x] Upgrade html-webpack-plugin to v5 to avoid DeprecationWarning [warning: alpha version]
[x] Remove library:'' as webpack throws configuration[0].output.library should be an non-empty string
[x] Remove warning DeprecationWarning: config.stats.warningsFilter is deprecated in favor of config.ignoreWarnings
[x] Pin @babel/runtime at v7.12.5 avoid 'Module not found' errors
[x] Fix webpack warning require.extensions is not supported by webpack. Use a loader instead.

[x] update webpack.extensions.ts

[x] Set minimize: false and transpileOnly: true to speed up build, as the output will not be used in production/runtime
[x] Add babel-loader to fxi lingui related issues

[ ] update extensions/*/webpack.config.js

Signed-off-by: Hung-Han (Henry) Chen<EMAIL_ADDRESS>

stuck at this error
index.js:7 Uncaught SyntaxError: Illegal return statement
    at ./node_modules/mac-ca/index.js (LensDev.js:35138)
    at Object.options.factory (LensDev.js:80325)
    at __webpack_require__ (LensDev.js:79781)
    at fn (LensDev.js:80012)
    at eval (system-ca.ts?dc0e:3)
    at ./src/common/system-ca.ts (LensDev.js:15752)
    at Object.options.factory (LensDev.js:80325)
    at __webpack_require__ (LensDev.js:79781)
    at fn (LensDev.js:80012)
    at eval (lens-app.tsx?31be:1)

Stopped by a strange issue, similar to https://github.com/pmmmwh/react-refresh-webpack-plugin/issues/247 might related to webapck-dev-server which is at 4.0.0-beta0


:sparkles: added queue container

added circular queue container

style: make sure the Queue class is named according to the style guide, it should be snake_case.

Sure Luke. I have updated the file name and class name accorsdingly.


Completely migrate rp2040_local_i2c_init to rtic v2

I amended the rp2040_local_i2c_init example to work with the latest version of the rtic v2 alpha.

Thanks for the PR :) I've migrated the V2 examples into the main RTIC repo and forgot to check the PRs before doing so. Would you mind re-opening the PR there? If you don't want to, LMK and I will perform the changes myself.

Any update on this? :)

This was completed in https://github.com/rtic-rs/rtic/pull/736


chore: bump lychee to 0.16.1

Thanks. There are some additional changes needed. Since I was already on it, I made them in a separate PR, so closing this in favor of https://github.com/lycheeverse/lychee-action/pull/249. Hope that's okay.