Default pin mux option wrong for evk

The teensy appears to do some work in its bootloader to setup a few things, and avoid the setup work normally needed on imxrt chips.
In order to get my led blinking (finally did!)
I needed to change the default alt of the pads to alt0 as that is in fact the default. Teensy must be setting these up to Alt5 by default. This needs to be reconciled.
I also needed to disable a few watchdogs otherwise the chip would reset very quickly leaving the debugger and myself very confused.
Lastly the runtime for the teensy makes some assumptions that I don't think are true for the evk boards and makes debugging difficult. The default setup for mcuxpresso is to load everything in ram and run it. This is what the imxrt-rt crate I've added to this repo on my branch does. It's effectively a fork of cortex-m-rt with some modifications I needed to make to have it work.
All in all I think we need to look at how the HAL can provide the tools, but not necessarily supply the default states assumed to be there currently to account for the variations between the teensy environment and the bare imxrt1062 environment found on the EVK boards.
See the imxrt1060evk_fixes branch for everything I needed to change to make this work.

Glad to hear you got output on the EVK board!

I needed to change the default alt of the pads to alt0 as that is in fact the default.

The IMXRT1060 reference manual, section 11.7, states that the reset value for nearly all of the SW_MUX_CTL_PAD_GPIO_* registers is 0x5, or Alt5. We also see this in the SVD files, which propagate to the reset values for the IOMUXC registers (exposition only; RAL is no longer checked in). There's no additional setup in the Teensy runtime crate to set these values across the MUX registers. We've selected Alt5 as the default type state because it reflects the reset value.
From a scan of the SW_MUX_CTL_PAD_GPIO_* table, there are only eight registers that default to Alt0:

AD_B0_04
AD_B0_05
AD_B0_06
AD_B0_07
AD_B0_08
AD_B0_09
AD_B0_10
AD_B0_11

#31 exposes those eight pads in the IOMUXC. Are those eight pins used on the EVK?
I agree that those eight pads should default to an Alt0 type state. But, we're changing all of the pad type states from Alt5 to Alt0. Are we sure that's appropriate?

Well, that is great news actually! I did not see the defaults listed, something I should have looked at. I'll change the defaults to match the ref manual, this makes a lot of what I said sound silly of course. Thanks Ian. I made an assumption after seeing the register reading back 0x00 that they were all like that. This I think solves the mystery.


Python: recall method in StepwisePlan not using context

Describe the bug
When using the StepwisePlanner, context is not being passed to skills. This is manifesting when using the recall ability of the TextMemorySkill in a skill's prompt, always using the default settings (e.g. collection name, limits, etc.). This means that skills cannot be context-dependent.
To Reproduce
Steps to reproduce the behavior:

Create a new Kernel, register the TextMemorySkill, and a memory store (currently tested with Azure Cognitive Search as memory store)
Create a skill which uses the {{recall}} method inside the prompt template, and register to the kernel.
Define a new context with the name of your ACS index as the COLLECTION_PARAM for TextMemorySkill (as shown below):

context = kernel.create_new_context()
context[sk.core_skills.TextMemorySkill.COLLECTION_PARAM] = memory_collection_name
context[sk.core_skills.TextMemorySkill.RELEVANCE_PARAM] = 0.5
context[sk.core_skills.TextMemorySkill.LIMIT_PARAM] = 5

Create a new SequentialPlanner, passing in your kernel, and a question as the goal.
Invoke(invoke_async) your plan, passing in the context and memory as parameters:

result = await plan.invoke_async(context=context, memory=kernel.memory)

Review results, noting that if your ACS index is not named "generic", it will fail to retrieve the relevant memories.
Enumerate through the plan._steps, and note the outputs. You will likely see the error

Error occurred: Function `recall` execution failed. ResourceNotFoundError: () The index 'generic' for service 'YOUR ACS INDEX' was not found.

Expected behavior
The recall function should have been passed the correct collection (index) name, and returned relevant memories for the prompt to use as additional context.
Platform

OS:Windows 11
IDE: VS Code
Language: Python
Source: pip package version 0.3.13.dev0

Additional Info
Full repro code below:
import semantic_kernel as sk
from dotenv import load_dotenv
from semantic_kernel.connectors.ai.open_ai import AzureChatCompletion, AzureTextEmbedding
from requests import get
import json
import os
from Plugins.HAPlugin.Homeassistant import HomeAssistant
from semantic_kernel.planning import StepwisePlanner
from semantic_kernel.planning.stepwise_planner.stepwise_planner_config import (
    StepwisePlannerConfig,
)
from semantic_kernel.connectors.memory.azure_cognitive_search import AzureCognitiveSearchMemoryStore

load_dotenv()

kernel = sk.Kernel()

deployment, api_key, endpoint = sk.azure_openai_settings_from_dot_env()

kernel.add_chat_service("chat_completion", AzureChatCompletion(deployment, endpoint, api_key))
intentskills = kernel.import_semantic_skill_from_directory("./skills", 'IntentDetectionSkill')
kernel.add_text_embedding_generation_service("embedding", AzureTextEmbedding("embedding", endpoint, api_key))

kernel.register_memory_store(memory_store=AzureCognitiveSearchMemoryStore(search_endpoint=os.environ.get('AZURE_COGNITIVE_SEARCH_URL'), admin_key=os.environ.get("AZURE_COGNITIVE_SEARCH_APIKEY"), vector_size=1536))

memory_collection_name = 'hadocs'
kernel.import_skill(sk.core_skills.TextMemorySkill())

ask = "Can HomeAssistant split energy usage by Tarriff?"

planner = StepwisePlanner(
    kernel, StepwisePlannerConfig(max_iterations=10, min_iteration_time_ms=1000)
)

plan = planner.create_plan(goal=ask)

context = kernel.create_new_context()
context[sk.core_skills.TextMemorySkill.COLLECTION_PARAM] = memory_collection_name
context[sk.core_skills.TextMemorySkill.RELEVANCE_PARAM] = 0.5
context[sk.core_skills.TextMemorySkill.LIMIT_PARAM] = 5

result = await plan.invoke_async(context=context, memory=kernel.memory)
print(result)

for index, step in enumerate(plan._steps):
    print("Step:", index)
    print("Description:",step.description)
    print("Function:", step.skill_name + "." + step._function.name)
    if len(step._outputs) > 0:
        print( "  Output:\n", str.replace(result[step._outputs[0]],"\n", "\n  "))

Sample config.json

{
    "schema": 1,
    "description": "Answer questions related to the home automation system based on documentation",
    "type": "completion",
    "completion": {
      "max_tokens": 100,
      "temperature": 0.1,
      "top_p": 1.0,
      "presence_penalty": 0.0,
      "frequency_penalty": 0.0
    }
  }

skprompt.txt
If a user has a DocsQuestion, answer the question to the best of your ability using the memory context provided to you.
You are to be helpful and polite. If your memory does not have a relevant answer, do not make up an answer, instead say "I don't know".

context: {{recall $input}}

Please cite your answers with the description property of the memory, and the additional_metadata (listed as "headers")

For example:

Question: Which rasbperry pi hats work with z-wave?

Answer:     - Aeotec Z-Pi 7 Raspberry Pi HAT/Shield (ZWA025, 700 series)
            - Z-Wave.Me RaZberry 7 (ZME_RAZBERRY7, 700 series)
            - Z-Wave.Me RaZberry 7 Pro (ZMEERAZBERRY7_PRO or ZMEURAZBERRY7_PRO, 700 series)
            - Z-Wave.Me Razberry 2 (500 series)"

            source: "Extended instructions how to setup Z-Wave."
            headers: ["## Supported Z-Wave USB Sticks & Hardware Modules"]

Question: How do I edit my configuration.yaml file?

Answer: The easiest option to edit `configuration.yaml` is to use the {% my supervisor_addon title="Studio Code Server add-on" addon="a0d7b954_vscode" %}.

            source: "Configuring Home Assistant via text files."
            headers: ["Editing `configuration.yaml`"]

Question: {{$input}}

Answer:

Additional info: I tried instead to use the SequentialPlanner skill, defining my plan with
planner = SequentialPlanner(
    kernel=kernel,
    config=SequentialPlannerConfig(max_relevant_functions=10),
)
plan = await planner.create_plan_async(goal=ask)

This also isn't working for me - the input is always showing as an empty string, which of course then fails to be parsed. I tried passing the input with the plan.invoke_async(context=context, memory=kernel.memory, input=ask, but that didn't change anything. Am I just using the SDK wrong?

@tarockey - thanks for the details here, the team will take a look and see what is happening.

@RogerBarreto could you see what is going on here?

Any updates on this bug @evchaki ?

@evchaki, @tarockey let me work on repro'ing the issue.

Any update on this issue on python side? Need a fix, seems like I cannot call any native function from semantic prompt,

Hi @kalyankdas, apologies for dropping the ball on this. I'm going to assign this to @juliomenendez who should be able to dive in soon. We'll update you as soon as we can.

Thanks @moonbox3, I'll take a first look over the weekend. Will keep this issue up to date as soon as I can.

To add more context, :) with latest python package - Sample is broken too , where it uses recall,(https://github.com/microsoft/semantic-kernel/tree/08e2e033c5c6c7f4490fcc311bc4730288d88c69/python/notebooks)
/06-memory-and-embeddings.ipynb
Also, kernel.import_skill(sk.core_skills.TextMemorySkill()) some how it does not work either

@kalyankdas I'm trying to get a new release out that contains some fixes for the TextMemorySkill (how they context variables are defined).
Something faster to try: run poetry install if you haven't. Once you do that, and all dependencies are installed, comment out the notebook's first cell (to install the package from pip). You can then run all other cells and it will use the underlying code. I can fully run the 06-memory-and-embeddings notebook.

@kalyankdas I published a new version of the python SDK (0.4.3.dev0). The notebooks were updated to reflect this, so if you install the package via pip like the notebook shows, the TextMemorySkill errors shouldn't be there.

Hey @kalyankdas @tarockey I have a WIP PR with a fix for calling skills from StepwisePlanner. On my branch and using the provided code from the issue description I get this result:
Yes, it is possible to split energy usage by tariff in HomeAssistant using the utility_meter component. The component allows for the creation of multiple meters that track energy usage based on different tariffs. If the utility_meter component is not yet configured in HomeAssistant, we can use the save function to add the necessary configuration to the configuration.yaml file.
Step: 0
Description: Execute a plan
Function: StepwisePlanner.ExecutePlan
  It is possible to split energy usage by tariff in HomeAssistant using the utility_meter component. This component allows for the creation of multiple meters that track energy usage based on different tariffs. We can use the recall function to check if the utility_meter component is already configured in HomeAssistant. If it is not, we can use the save function to add the necessary configuration to the configuration.yaml file.
  [ACTION]
  {"action": "_GLOBAL_FUNCTIONS_.recall", "action_variables": {"input": "utility_meter component"}}
  [OBSERVATION]
  Got no result from action
  [THOUGHT]
  Since we did not get any result from the recall function, it is likely that the utility_meter component is not yet configured in HomeAssistant. We can use the save function to add the necessary configuration to the configuration.yaml file. We will need to specify the input as the configuration for the utility_meter component, and provide a unique key to associate with this configuration.
  [ACTION]
  {"action": "_GLOBAL_FUNCTIONS_.save", "action_variables": {"input": "utility_meter:\n  electricity:\n    source: sensor.energy\n    cycle: daily\n    tariffs:\n      peak:\n        cost: 0.25\n        peak: '07:00-19:00'\n      offpeak:\n        cost: 0.10\n        peak: '19:00-07:00'", "key": "utility_meter_config"}}
  [OBSERVATION]
  utility_meter:
    electricity:
      source: sensor.energy
      cycle: daily
      tariffs:
        peak:
          cost: 0.25
          peak: '07:00-19:00'
        offpeak:
          cost: 0.10
          peak: '19:00-07:00'
  [THOUGHT]
  None

Is that what you are expecting? If not, how should the correct response look?

@juliomenendez , that possibly looks correct. But, I was working on using ACS as a memory store - so the error was in trying to search ACS for documents (i.e. the RAG pattern).
that said, I'm seeing similar issues in the SequentialPlanner as well (on the latest public release, not your branch) - so the fact that I can see "input" is not empty in your output for each step is promising.

@tarockey Using this script:
import os
import semantic_kernel as sk
from dotenv import load_dotenv
from semantic_kernel.connectors.ai.open_ai import AzureChatCompletion, AzureTextEmbedding
from semantic_kernel.planning import StepwisePlanner
from semantic_kernel.planning.stepwise_planner.stepwise_planner_config import (
    StepwisePlannerConfig,
)
from semantic_kernel.connectors.memory.azure_cognitive_search import AzureCognitiveSearchMemoryStore
from semantic_kernel.utils.settings import azure_openai_settings_from_dot_env_as_dict

memory_collection_name = 'generic'

async def populate_memory(kernel: sk.Kernel):
    await kernel.memory.save_information_async(collection=memory_collection_name, id="info1", text="""The Rasbperry pi hats that work with z-wave are:
- Aeotec Z-Pi 7 Raspberry Pi HAT/Shield (ZWA025, 700 series)
- Z-Wave.Me RaZberry 7 (ZME_RAZBERRY7, 700 series)
- Z-Wave.Me RaZberry 7 Pro (ZMEERAZBERRY7_PRO or ZMEURAZBERRY7_PRO, 700 series)
- Z-Wave.Me Razberry 2 (500 series)""")
    await kernel.memory.save_information_async(collection=memory_collection_name, id="info2", text="The easiest option to edit `configuration.yaml` is to use the Studio Code Server add-on")

async def main():
    load_dotenv()

    kernel = sk.Kernel()

    aoai_settings_dict = azure_openai_settings_from_dot_env_as_dict(include_deployment=True, include_api_version=True)

    kernel.add_chat_service("chat_completion", AzureChatCompletion(**aoai_settings_dict))
    kernel.add_text_embedding_generation_service("ada", AzureTextEmbedding("embedding", endpoint=aoai_settings_dict["endpoint"], api_key=aoai_settings_dict["api_key"]))

    memory = AzureCognitiveSearchMemoryStore(search_endpoint=os.environ.get('AZURE_AISEARCH_URL'), admin_key=os.environ.get("AZURE_AISEARCH_API_KEY"), vector_size=1536)
    kernel.register_memory_store(memory_store=memory)

    kernel.import_skill(sk.core_skills.TextMemorySkill())

    await populate_memory(kernel)

    ask = "Can HomeAssistant split energy usage by Tarriff?"

    planner = StepwisePlanner(
        kernel, StepwisePlannerConfig(max_iterations=10, min_iteration_time_ms=1000)
    )
    plan = planner.create_plan(ask)

    context = kernel.create_new_context()
    context[sk.core_skills.TextMemorySkill.COLLECTION_PARAM] = memory_collection_name
    context[sk.core_skills.TextMemorySkill.RELEVANCE_PARAM] = 0.5
    context[sk.core_skills.TextMemorySkill.LIMIT_PARAM] = 5

    result = await plan.invoke_async(context=context, memory=kernel.memory)
    print(result)

    for index, step in enumerate(plan._steps):
        print("Step:", index)
        print("Description:",step.description)
        print("Function:", step.skill_name + "." + step._function.name)
        if len(step._outputs) > 0:
            print( "  Output:\n", str.replace(result[step._outputs[0]],"\n", "\n  "))

    await memory.close_async()

if __name__ == "__main__":
    import asyncio

    asyncio.run(main())

I get the following output:
Yes, it is possible to split energy usage by tariff in HomeAssistant using the utility_meter component. The component allows for the creation of multiple meters that track energy usage based on different tariffs. To configure the utility_meter component, we can use the save function to add the necessary configuration to the configuration.yaml file. The configuration should include the necessary meters for tracking energy usage based on different tariffs.
Step: 0
Description: Execute a plan
Function: StepwisePlanner.ExecutePlan
  Output:
 This was my previous work (but they haven't seen any of it! They only see what I return as final answer):
  [THOUGHT]
  It is possible to split energy usage by tariff in HomeAssistant using the utility_meter component. This component allows for the creation of multiple meters that track energy usage based on different tariffs. We can use the recall function to check if the utility_meter component is already configured in HomeAssistant. If it is not, we can use the save function to add the necessary configuration to the configuration.yaml file.
  [ACTION]
  {"action": "_GLOBAL_FUNCTIONS_.recall", "action_variables": {"input": "utility_meter component"}}
  [OBSERVATION]
  ["The easiest option to edit `configuration.yaml` is to use the Studio Code Server add-on"]
  [THOUGHT]
  Since the recall function did not return any relevant information, we can assume that the utility_meter component is not yet configured in HomeAssistant. We can use the save function to add the necessary configuration to the configuration.yaml file. We will need to specify the input as the configuration for the utility_meter component, and provide a unique key to associate with this configuration. We can use the default collection value of "generic".
  [ACTION]
  {"action": "_GLOBAL_FUNCTIONS_.save", "action_variables": {"input": "utility_meter:\n  gas_daily:\n    source: sensor.gas_meter\n    cycle: daily\n  gas_night:\n    source: sensor.gas_meter\n    cycle: daily\n    offset:\n      hours: 21\n  electricity_daily:\n    source: sensor.electricity_meter\n    cycle: daily\n  electricity_night:\n    source: sensor.electricity_meter\n    cycle: daily\n    offset:\n      hours: 21", "key": "utility_meter_config"}}
  [OBSERVATION]
  utility_meter:
    gas_daily:
      source: sensor.gas_meter
      cycle: daily
    gas_night:
      source: sensor.gas_meter
      cycle: daily
      offset:
        hours: 21
    electricity_daily:
      source: sensor.electricity_meter
      cycle: daily
    electricity_night:
      source: sensor.electricity_meter
      cycle: daily
      offset:
        hours: 21
  [THOUGHT]
  None

It looks to me that it is finding the stored information in ACS. I do see your point of the ACS index having to be named "generic" but we can talk about that separately if possible.

@tarockey my PR has been merged. Can you check this issue again? Check the sample script I provided in my previous comment where ACS is being used.

@juliomenendez apologies, I am just now seeing this comment, I will try it out ASAP, thank you!

Apologies for the late response - after testing locally, I still seem to be having issues getting the memory to be used as context for an answer. Additionally, I cannot get the service to recognize an index that isn't named 'generic'. That said, this is all on an old version of semantic kernel, I haven't had  chance to refactor to the latest versions (currently on 0.4.7.dev0). For now, it probably makes sense to close this issue since its so stale, and I can reopen if I see it again in a newer version.


how to run binexport in cmd line without cmd being blocked?

I want to batch generate .BinExport file. I run binexport in cmd line as follow,
idat64.exe -A -Sbin_export.idc bin_file_path.
After running cmd, .BinExport flie is generated. but cmd window are blocked. Is there any method to do without blocking window?
my env: win10 64, ida pro 7.5, binexport 12

I think this might be an IDA issue? Try using the "GUI" version, ida64.exe.
idat64 will change the console settings, which might be the problem.


Point to CCLX in readthedocs

Readthedocs doesn't currently link to CCLX. We should add this link so people can get easy access to the examples.

I found this already in the quickstart page: https://ccl.readthedocs.io/en/latest/source/quickstart.html
so we can close this.


Optimization and Hessian hybrid procedure

Is your feature request related to a problem? Please describe.

Currently, it is quite awkward to generate Hessain calculations on an Optimizationdataset after it has completed, this involves periodically checking each task has finished and then adding the new calculation on the final molecule.
Describe the solution you'd like

It would be great to have a procedure that could automatically generate an associated base dataset (with the same name as the optimisation dataset?) that contained the hessian calculations without manual intervention.
Describe alternatives you've considered

We could alternatively have a bot per dataset to periodically check the dataset records and submit the new calculations when ready.
Additional context

I think the short here is that we need to implement this at the pipeline layer. We will get too many of these custom objects otherwise.
Timeline is ~3 months for a beta, but that is pretty open depending on what else comes up in the meantime.

I don't have any immediate plans for a pipeline/workflow feature, although I have considered a Optimization + Singlepoint calculation as a simple workflow that covers most use cases.
Superseded by #748


per-directory-history ignores HIST_IGNORE_SPACE

I think the title says it all: the per-directory-history plugin records all history, while it should honor HIST_IGNORE_SPACE (and perhaps other history-related options).

This is now fixed in master with https://github.com/jimhester/per-directory-history/pull/26, can we merge it?

Done, thanks!


Webhook receiver component to never miss a hook

This would be really nice, maybe a place where you can see webhooks recieved.
Github is really great at delivering webhooks, but it sometimes takes much longer for it to show up in drone in 3% of the cases, and there is little to no way to know what is going on.

closing in favour of  #99


Error with both boost and SDL2 installed

Hello,
I have noticed that when you install both boost and sdl2 for some strange reason when trying to compile a simple program like:
// ConsoleApplication1.cpp : Defines the entry point for the console application.
//

#include "stdafx.h"

#include <SDL2/SDL.h>

int main(int argc, char *argv[])
{
    return 0;
}

I get the following error error LNK2019: unresolved external symbol "int __cdecl test_main(int,char * * const)" even if I do not include boost at all.
I think this can be a problem with the autolinking feature of vcpkg as when removing boost completely the SDL2 program is running fine.
I am on Windows 10 anniversary and got into the issue with both Visual Studio 2015 and 2017 RC.

@mattiascibien I have a similar problem with GLEW. I'm doing the leanopengl.com tutorial and decided to use vcpkg for dependencies management. First window and I hit a wall with error LNK2001: unresolved external symbol _glewExperimental. For some reason the IDE sees GLFW .h, .lib, and .dll (present in build output folder) files but only .h in case of GLEW.
I'm on Windows 10 Anniversary and VS2015.

Are you using glew dynamic or statically? Anyway my problem is more related to the fact that when using boost I guess that my main instead of being defined as SDLmain it gets defined as the main of a test for the boost unit testing framework. Not sure why it goes like this actually. From the IDE I find that it is defined correctly.

@mattiascibien Ok, as usual the error was between the monitor an the chair. In the tutorial I mentioned you are supposed to link statically and I did it dynamically. I removed the explicit #define GLEW_STATIC and everything started to work. I'm learning the ropes here (full time JEE dev) so sorry for spamming your post and best of luck.

No worries at all. Welcome to the wonderful world of 3d graphics :-)
Il 27 nov 2016 13:17, Bartłomiej Pietrzyk<EMAIL_ADDRESS>ha scritto:
@mattiascibienhttps://github.com/mattiascibien Ok, as usual the error was between the monitor an the chair. In the tutorial I mentioned you are supposed to link statically and I did it dynamically. I removed the explicit #define GLEW_STATIC and everything started to work. I'm learning the ropes here (full time JEE dev) so sorry for spamming your post and best of luck.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vcpkg/issues/352#issuecomment-263119099, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABPYyZTeoHYnn-pIlMmJMSE0Sp74MTGlks5rCXTQgaJpZM4K8-a5.

I'm having a bit of a hard time reproducing this (I get a different error), but we should probably move boost's unit test library out into lib\manual-link\ according to #306.

@ras0219-msft which error are you getting? I will try to test on another machine.

I'm getting
LINK : fatal error LNK1561: entry point must be defined [C:\src\project5\Project5.vcxproj]

Note though that I'm using the Empty Project template with a single source file:
// ConsoleApplication1.cpp : Defines the entry point for the console application.
//

#include <SDL2/SDL.h>

int main(int argc, char *argv[])
{
    return 0;
}

Also, @rhinox thanks for mentioning the solution to your issue! This is a place where we'd like to do better in Vcpkg; we should bake that macro directly into the header files based on the exact build configuration so users don't hit these sorts of issues.

I'm having the same problem (and same error) as @mattiascibien. Looks like both Boost.Test and SDL2 provide the main function (in boost_test_exec_monitor.lib, see here and in SDL2main.lib, see here). SDL2 also provides WinMain, so in subsystem WINDOWS everything works fine. However, when building console app there are two main functions for the linker to choose, hence the errors (I'm not sure why error messages differ though).
If someone is looking for a quick fix, looks like disabling substitution of main works great (#undef main).

it is also possible to delete boost_test_exec_monitor.lib from lib and debug/lib to temporarly fix the issue.

It sounds like both the boost test monitor and SDL2main.lib need to be moved into the manual-link directory. How hard would it be to add a check to ensure that the same symbols aren't getting defined in multiple libraries? I'd imagine it'd be relatively expensive to do the actual check (as it's doing a union of every single lib in vcpkg), so perhaps hide it behind a --verify flag or something similar?

Moving those two libs to lib\manual-link is the correct solution here.
This is also certainly something we should detect during a post-build test, along with a pre-install test.

Post-build: No library in lib\ should be exporting _main or _WinMain.
Pre-install: No library in lib\ should be exporting a symbol that another library inside lib is exporting.

We can make the test fast by writing out a log of each package's symbols -- we already do this for each package's files under installed\vcpkg\info\*.list. This is what powers the vcpkg owns command and @alexkaratarakis has recently added support for using these file lists to detect package conflicts before installing. We simply should do the same for exported symbols.


Add product filtering

I want to merge this change because it fixes #2588
Screenshots

Pull Request Checklist

[ ] Privileged views and APIs are guarded by proper permission checks.
[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Database queries are optimized and the number of queries is constant.
[ ] Database migration files are up to date.
[ ] The changes are tested.
[ ] The code is documented (docstrings, project documentation).
[ ] GraphQL schema and type definitions are up to date.
[ ] Changes are mentioned in the changelog.

I've tested the branch locally and here are a few problems that I found:

if the "Add filter" modal is open, clicking outside of it should close it
when saving a filter the name should be required (now you can save a filter without passing any name)


Hovered stream should be highlighted in "more topics"

As reported in https://github.com/zulip/zulip/pull/25535#issuecomment-1544789797, in the "more topics" view, hovering over a stream when a topic is selected does not highlight the stream name. It should get the same hover effect as hovering over topics in the stream.

hey @alya I would like to give it a try ...please assign it to me !

Hey @iks1, you can check out this to find instructions on how to claim the issue.
Also, make sure to read our Contrbutiing Guide, it will help a lot in getting started contributing.

@zulipbot claim

@zulipbot  claim

@zulipbot I don't care , I will start , you warned me before but I already finished it in 2 hours...
Others, you can assign yourself if I dont finish this one before 17 june.

@zulipbot claim

I have already started working on the issue. I edited sidebar.css file in styles and have achieved desire results. Will push the pr once tests are done locally.

I think in theory this is helpful but in practice it may not be a thing we want to do following ongoing left sidebar redesign work, so I'm closing this as wontfix. (And it'll be easier to do on top of that anyway).


Check if cas:memberOf attribute is a string

I'm encountering the issue this fixes, can this please receive attention?

For the record, this change can be simplified by only modifying line 127 in routing.py to
if "cas:memberOf" in attributes and isinstance(attributes["cas:memberOf"], basestring):

I'm running that modification on my local copy of Flask-CAS and it has resolved the issue I was having without any side effects.


To make WFCORE-1671 fix safer drop ServiceLoader config for vault rea…

…der that's provided by core since WFCORE-114
Having this META-INF/services file here means a caller could potentially try and load core's RuntimeVaultReader via this module instead of via core's server module. Which might work, or might partly work or... Since no code in full needs to load an AbstractVaultReader via this module I see no reason to support it.
The vault resources in the security subsystem do not provide an AbstractVaultReader; they provide a Service (SecurityVault being the picketbox class.)

@bstansberry Hi, I created another Jira: https://issues.jboss.org/browse/WFLY-6886 for this to make downstream Jira link relationships clearer.


There is no package_data, and the package is zip_safe.

Thanks again. :fire:

Coverage remained the same at 67.47% when pulling ba926eadff06265e5d68eb6e2929c17a5f7be2d6 on graingert:patch-1 into 8b716f54c7085f0042d0b1aaa06a7f3ae55e3969 on numberly:master.

Coverage remained the same at 67.47% when pulling ba926eadff06265e5d68eb6e2929c17a5f7be2d6 on graingert:patch-1 into 8b716f54c7085f0042d0b1aaa06a7f3ae55e3969 on numberly:master.


If the Modal is not full screen, the maximum scroll height is not enough to display all the children.

steps to reproduce
showSheet(BuildContext context) {
  Navigator.push(
    context,
    ModalSheetRoute(
      builder: (context) => SafeArea(
        bottom: false,
        child: DraggableSheet(
          initialExtent: Extent.proportional(.8),
          maxExtent: Extent.proportional(.8),
          minExtent: Extent.proportional(.8),
          child: SheetContentScaffold(
            body: ListView.builder(
              itemCount: 100,
              itemBuilder: (context, index) => ListTile(
                title: Text(index.toString()),
              ),
            ),
          ),
        ),
      ),
    ),
  );
)

version: 0.4.1
android_emulator: Pixel 8 API 34 android 14 ("UpsideDowncake") | x86_64

It is working as intended. maxExtent: Extent.proportional(.8) means that only 80% of the ListView is visible at maximum.

Thank you for your excellent work and patient answers


Authorization problem using locate parameter

Hi,
if I use this command
curlicue -f credentials 'https://stream.twitter.com/1.1/statuses/filter.json?track=pizza'

I have the related streams results.
If I had location
curlicue -f credentials 'https://stream.twitter.com/1.1/statuses/filter.json?track=pizza&locations=-180,-90,180,90'

I have "Unauthorized", HTTP ERROR: 401 error.
What's wrong in my procedure?
Thank you

I'm on a phone right now so I can't verify this, but I believe the problem is that the commas in your locations parameter are not URL-encoded (%2C). What's happening is that the signature is calculated on the literal value you passed, but the server expects a signature on the properly encoded URL.

@decklin it works, I'm stupid :)
Thank you very much


building from source fails (go1.5, test for runtime-gdb)

I tried to build go from the sources. I followed the instruction from
https://golang.org/doc/install/source
**  What version of Go are you using (go version)?
go version go1.4.2 linux/amd64
and
go1.4
**  What operating system and processor architecture are you using?
fedora 20 (Linux  3.19.8-100.fc20.x86_64 )
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    2
Core(s) per socket:    2
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 42
Model name:            Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
Stepping:              7
CPU MHz:               2103.320
CPU max MHz:           3200.0000
CPU min MHz:           800.0000
BogoMIPS:              4988.73
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              3072K
NUMA node0 CPU(s):     0-3
**  What did you do?
I did the steps as described by the installation-from-source webpage.

clone the go-language repository
execute all.bash in subdir src.

**  What did you see?
The tests failed which means, the installation failed. The following steps
went seemingly ok
Building Go toolchain using/ home/msteffen/go1.4.
Building go_bootstrap for host, linux/amd64.
Building packages and commands for linux/amd64.
The following section of the installation failed, namely the testing
Testing packages.
in particular
--- FAIL:
runtime-gdb_test.go:42: gdb version 7.7
runtime-gdb_test.go:146: print mapvar failed: $1 = map[string]string = {[<error reading variable: Cannot access memory at address 0xb5cc>] = <error reading variable: Cannot access memory at address 0xb5cc>, [<error reading variable: Cannot access memory at address 0x3>] = <error reading variable: Cannot access memory at address 0x3>}
FAIL
FAIL	runtime	41.748s
which resulted in
2015/10/03 14:54:11 Failed: exit status 1
** Go Versions:
I made the above attempt for
 git checkout master
 git checkout go1.5

both gave the same error
The compilation of go1.5 was using  go1.4.2 (which is shipped with my fedora version) and I also tried to use go1.4 (where I downloaded the binaries and moved them to ~/go1.4). In
all combinations, the result was the same.
However, when I did
  git checkout go1.4

that one went through, i.e., the go1.4 version, I was able to build from the sources.

I wouldn't worry about that gdb failure. If you temporarily remove gdb, the test will be skipped.

On 3 Oct 2015, at 09:41, Martin Steffen<EMAIL_ADDRESS>wrote:
I tried to build go from the sources. I followed the instruction from
https://golang.org/doc/install/source
** What version of Go are you using (go version)?
go version go1.4.2 linux/amd64
and
go1.4
** What operating system and processor architecture are you using?
fedora 20 (Linux 3.19.8-100.fc20.x86_64 )
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 42
Model name: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
Stepping: 7
CPU MHz: 2103.320
CPU max MHz: 3200.0000
CPU min MHz: 800.0000
BogoMIPS: 4988.73
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 3072K
NUMA node0 CPU(s): 0-3
** What did you do?
I did the steps as described by the installation-from-source webpage.
clone the go-language repository
execute all.bash in subdir src.
** What did you see?
The tests failed which means, the installation failed. The following steps
went seemingly ok
Building Go toolchain using/ home/msteffen/go1.4.
Building go_bootstrap for host, linux/amd64.
Building packages and commands for linux/amd64.
The following section of the installation failed, namely the testing
Testing packages.
in particular
--- FAIL:
runtime-gdb_test.go:42: gdb version 7.7
runtime-gdb_test.go:146: print mapvar failed: $1 = map[string]string = {[] = , [] = }
FAIL
FAIL runtime 41.748s
which resulted in
2015/10/03 14:54:11 Failed: exit status 1
** Go Versions:
I made the above attempt for
git checkout master
git checkout go1.5
both gave the same error
I also tried go1.4.2 (which is shipped with my fedora version) and I tried
go1.4 (where I downloaded the binared and moved the whole to ~/go1.4). In
all combinations, the result was the same.
However, when I did
git checkout go1.4
that one went through, i.e., the go1.4 version, I was able to build from the sources.
—
Reply to this email directly or view it on GitHub.

yes, thanks, removing gdb skipped the test and the script ran through.  ("disabling" gdb is a radical measure though....). But it did the job.

Yeah, I'm aorry about the workaround. As you probably know gdb and go don't
get along, so your not missing much.
On Sat, 3 Oct 2015 11:32 Martin Steffen<EMAIL_ADDRESS>wrote:

yes, thanks, removing gdb skipped the test and the script ran through.
("disabling" gdb is a radical measure though....). But it did the job.
—
Reply to this email directly or view it on GitHub
https://github.com/golang/go/issues/12830#issuecomment-145256854.

Sure, no problem. I simply made gdb non-executable temporily and worked just fine.

What does gdb --version print on your system?
According to #11214, gdb 7.7 is sufficient on Ubuntu, and that is what the test looks for.  Though it's possible that Ubuntu has patches that Fedora does not.

Still awaiting reply from Oct 3. Too late for Go 1.6.


Resolve node port conflict for internal docker registrey

Changes:

add action which solves the node port conflict.

/retest


Fix style prop type

The current prop type is incorrect given the namespaces expected.

@Neaox Thank you for your contribution! I don't use typescript, so I am not the best to review this. Also I do currently not maintain this package and I am unsure anyone else is.
@dylanscott Could you please review this as you seem to have added typescript support originally? Thanks!

LGTM 👍

@dylanscott Unfortunately checks failed 😞 I restarted the build, let's see if that works.


Use the 8.10.2 version of GHC

Since that is the version being installed and setup from line 85
Otherwise the cabal build does not work from line 153

Closing because we should be using ghc-8.10.4.  Documentation will be updated accordingly.


Scrub some warnings and visibility problems

Preparing to do a stable public release

Remaining warnings in :zipline production code:
> Task :zipline:compileKotlinMacosArm64
w: /Users/jwilson/Development/zipline/zipline/src/nativeMain/kotlin/app/cash/zipline/QuickJs.kt: (404, 9): Variable 'stack' is never used

This is expected; we don’t yet use this variable and therefore we lose the stack in native crashes.


Add docs to PubSub spi layer

Coverage increased (+0.006%) to 85.752% when pulling 4c12e6cafd5c868217e6fc13f7839d2714f406c0 on mziccard:pubsub-spi-docs into d487307159a44d9363725bd3045d835562ac5637 on GoogleCloudPlatform:pubsub-alpha.

/cc @lesv

LGTM - I'm happy to see this, but wonder who we expect to call these directly?

I'm happy to see this, but wonder who we expect to call these directly?

Those are not supposed to be called directly by users. But some documentation is not going to hurt :)

Sg - LGTM


0.5.11 Sodium Backport Support with the 2.1.0

I just recently switched back due to Nvidium and Nvidium does not support 0.6.0 Sodium. So I did assumed that 2.1.0 Dense Flowers would be working with 0.5.11 Sodium and well it didn't.

The whole reason why i bumped the version to 0.2 was to support 0.6 since the switch to 0.6 requires code changes.
so just use 0.1 till nvidium supports sodium 0.6 - if you run into major z-fighting issues I can backport the fix to 0.1

The whole reason why i bumped the version to 0.2 was to support 0.6 since the switch to 0.6 requires code changes.
so just use 0.1 till nvidium supports sodium 0.6 - if you run into major z-fighting issues I can backport the fix to 0.1

you mention z fighting in 0.1? Well it does z fight. im clearly sure it still had a previous code existing on the older version. 0.2 is much different than 0.1 but dont worry i would send another screenshot of z fighting possibly in 0.1


jodd.paramo.Paramo leaks stream

at jodd.util.ClassLoaderUtil.getClassAsStream(ClassLoaderUtil.java:472)
at jodd.paramo.Paramo.resolveParameters(Paramo.java:49)
Stream is opened, but never closed. ClassReader also doesn't close it, because it passes the parameter 'close' as false from this constructor
https://github.com/oblac/jodd/blob/master/jodd-proxetta/src/main/java/jodd/asm5/ClassReader.java
https://github.com/oblac/jodd/blob/master/jodd-proxetta/src/main/java/jodd/paramo/Paramo.java

Hey @JoonasVali good catch! Streams are always better when they are closed after use :)))
Thank you!


Added submission template command

Additions
Added create-x-submission-template commands with auto-completion

Need approval to kick off the creation of the auto-completion scripts


Add media player entity schemas

Schemas for new context entities that will be attached to media player events to enable:

tracking a session that groups all events coming from the same media player,
tracking ads within media,
tracking media player quality.

media_player_session (#1266)
A session groups events from the same media player using a sessionId identifier (which may be provided by the user).
A secondary role of the session is a sort of edge analytics since it provides statistics about the playback (such as the time spent playing) in order to make data modelling more efficient.
media_player_ad_break (#1268)
An ad break is a grouping of ads played back to back. The schema will identify all ad events belonging to the same ad break.
media_player_ad (#1267)
Describes an ad being played at the time of the event. Provide metadata about the ad.
media_player_quality (#1269)
Describes quality of experience for the media playback at a specific time. It will be tracked with updateQuality media player events so it will give a snapshot of the data quality rather than aggregated metrics for the whole playback.

Adding @jethron for review as well.

Update: I created a new PR #1283 where I added schemas for media player events.

Update about what has changed in the last force push:
media_player_session

rename timePlayedContent to timePlayed
rename timePlayedContentMuted to timePlayedMuted
rename contentDurationPlayed to contentWatched
add timePaused
rename totalAds to ads
rename totalAdBreaks to adBreaks
add adsClicked
add adsSkipped
add timeBuffering

media_player_quality
Decided not to create this schema because the data quality information provided by the players is different in each one of them and it’s very likely that users will need to define a custom entity anyway to fit the information provided by their player and the way that the player provides the information. Happy to reconsider this if we figure out the common properties, but I don't think that I have (every time I look at a different player, I can see that other info needs to be tracked).
Additionally, I added a timeBuffering property to the session entity which calculates the amount of time that the player was buffering – this is a universal property that can be tracked anywhere and also the tracker can track it automatically (based on the buffer start and end events).

Update:

changed the vendor for all media entities to com.snowplowanalytics.snowplow.media and renamed media_player_session to session and similar for the ad schemas.
added a new player schema that should be an updated version of the media_player schema.

added properties to it: label (used to be in events before), playerType and mediaType (used in the media dbt model but haven't had a single place before), fullscreen, pictureInPicture
made some properties optional: muted, volume, playbackRate, loop
removed the percentProgress property which is now reported in the percent progress event and I don't think it's that useful because the schema has currentTime and duration properties anyway
changed max values for currentTime and duration to<PHONE_NUMBER> (was too large before)
changed min and max for playbackRate to 0 to 16

ad_break schema – decreased max value for startTime
ad schema

removed percentProgress which is now reported in quartile, skip and click events
decreased max value for duration

Update: added a quality attribute to the player schema.

Integrated into R142 PR #1302


DomainValue for Bytes

Parse and unparse DomainValue in the Bytes sort.
After: #1238
See also: kframework/k#903

Reviewer checklist

[ ] Test coverage: stack test --coverage
[ ] Public API documentation: stack haddock

So we can now just format it as \dv without worrying about the symbol used to construct it?

That's right. I found out this is what the LLVM backend already does, even though there isn't a syntax in the frontend for Bytes literals.


Cannot add Image metadata (or other data) via Bridge

Environment

Client OS (e.g., Linux, macOS, Windows):
Keptn Version (keptn version): 0.17.1 and higher
Kubernetes Cloud Provider (e.g., GKE, AKS):
Kubernetes version (kubectl version):

Affected Component

[x] Bridge

Describe the bug

To Reproduce
keptn trigger delivery \
--project=fulltour \
--service=helloservice \
--image="ghcr.io/podtato-head/podtatoserver:v0.1.1" \
--labels=image="ghcr.io/podtato-head/podtatoserver",version="v0.1.1"

This command cannot be replicated via the bridge as there is no way to add --image via the bridge.
Expected behavior
I can trigger sequences equally from API, bridge and CLI. They should be equivalent.

Hey @agardnerIT, I am using Keptn 0.18.1 and the --image parameter can be specified in the first input field. Labels are passed in the second input field instead.


Filter box focus

Focus on filter input when opening facet more rows and when clearing the filter input

Current coverage is 100% (diff: 100%)

Merging #57 into master will not change coverage

@@           master    #57   diff @@
====================================
  Files          74     74
  Lines        1434   1438     +4
  Methods       328    329     +1
  Messages        0      0
  Branches      291    292     +1
====================================
+ Hits         1434   1438     +4
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 0e705bd...4164221


Failure to resume playback with Drag seek backwards (multiple seeks in quick succession)

Have you read the FAQ and checked for duplicate open issues?
Yes
What link can we use to reproduce this?
https://v3-0-7-dot-shaka-player-demo.appspot.com/demo/#audiolang=en-US;textlang=en-US;uilang=en-US;asset=https://storage.googleapis.com/shaka-demo-assets/sintel/dash.mpd;panel=HOME;build=uncompiled
Also on https://shaka-player-demo.appspot.com/demo/#audiolang=en-US;textlang=en-US;uilang=en-US;asset=https://storage.googleapis.com/shaka-demo-assets/sintel/dash.mpd;panel=HOME;build=uncompiled
What version of Shaka Player are you using?
v3.0.7-uncompiled
Also on v3.1.0-uncompiled
What browser and OS are you using?
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36
What did you do?

Seek backwards quickly in succession by dragging the seek bar controls to the left gradually.
What did you expect to happen?
Wherever I let go on the mouse button, it will resume playback from that point.
What actually happened?

Playback frozen (spinner sometimes)
Click on video toggles pause/resume button, but playback still frozen.
Have to seek again in order to recover.
My observations:

This seems significantly easier to recreate from v3.0.7 onwards.  However, I can occasionally get it on v3.0.6
I had originally added some notes to https://github.com/google/shaka-player/issues/3344 because I first saw this on Tizen, but now I've realised I can recreated this on Chrome too.  I've therefore separated it from Tizen specific concerns.
That ticket contains some notes and screenshots from a Tizen environment where I saw that the stall detector is not able to recover from this condition.
I created a custom UI with a button to seek back 10 seconds and a double click on that can recreate this issue.

Do you have this issue with our UI control or the browser's native controls?  (Our demo app uses our UI controls by default.)

Hi @joeyparrish I get this with the demo app UI controls... but I can also recreate on Tizen 3 with native controls.
I've captured a video of the issue at https://drive.google.com/file/d/1akPaKSFECvDLi6EBVsQciY13aQ10oh5M/view

Hi,
It's interesting that this problem occurs only on seeking back in time.
The attached image shows that while seeking backwards, multiple audio segment downloads are started and then cancelled. When we stop seeking, audio segments are loaded from segment number 68, but video from 71 (following on from the last completed video segment download. I hope this helps @joeyparrish .

Here's another example showing the end of a much longer "drag" of the seek bar:

Both these examples were using 3.0.11.
We'd really appreciate any help you can provide, as we're looking forward to introducing the features of 3.1.x, but at the moment we're unable to deploy anything newer than 3.0.6.

I think this is a duplicate of #3089.  You could work around this by setting streaming.jumpLargeGaps to true.

Hi @TheModMaker @joeyparrish,
This is not a duplicate of #3089.
When I see this issue, video stops at the point before the seek (in #3089 there is some video played after the seek). Setting jumpLargeGaps does not fix this problem.
Are you able to re-open this issue please?
Thanks.

The problem seems to have been introduced in https://github.com/google/shaka-player/commit/ec210cbe1d33f7fd2ca99e6ff728bd7af1aa4abe
It's fairly easy to reproduce from this point forward, but in the previous commit, (https://github.com/google/shaka-player/commit/7944616657eb69e104abca5369294c993fc82307) I was unable to reproduce the problem at all.

When you see the problem, what is the value of video.currentTime, player.getBufferedInfo(), and player.streamingEngine_.mediaStates_.get('video').segmentIterator?  For the last one, you need to use the debug or uncompiled library and not be using CastProxy.  Or if you are using the hosted demo, you can get the player instance with shakaDemoMain.controls_.localPlayer_.

Most of the time I've seen the problem occur with the video buffer, but in my current debug session it's the audio:
With 2 second segments:

presentationTime: 328.039485
video buffer: 326.125 - 338.124999
video segmentIterator.nextPosition: 170
audio buffer:<PHONE_NUMBER>66
audio segmentIterator.nextPosition: 171

On this occasion the problem was with the video:

Hi @joeyparrish @TheModMaker
I believe I have a solution to this issue.  Please can you assign it to me, and I'll prepare a PR.
Thanks.

Done.  Thanks!


point of this repo

Given I already have atom-nonmem? What is the reason for the fragmentation?

suggestion to delete this and I will transfer ownership of the existing package to CTM to ease access rights, however it has some additional improvements, including some additional documentaiton + example snippets

Yeah, the grammars are identical.

haha yeah thats because they came from the same tmLanguage file. I think this was @wilsonmichaelc  testing out making a package, and@vjd had forgotten I had the atom-nonmem package already. I just need to check into figure out if changing ownership from dpastoor to umctm will cause any issues with atom's package manager.

@dpastoor another option is to let me make commits to the existing atom-nonmem so I can add the autocomplete and snippets that @vjd is requesting.

@wilsonmichaelc I'd definitely be down with that then if we feel the need to migrate it 'officially' we can figure it out at that point - giving you access now...


feat: allow file input in applyTransform test util

Fixes: https://github.com/CodeshiftCommunity/CodeshiftCommunity/issues/150
This allows to define the path for the file in the transformer, for example
    const result = await applyTransform(
      transformer,
      {
        path: "src/components/Example.tsx",
        source: `
        import React, { useState } from "react";

        export default function Example() {
        const [state] = useState("Hello World");

        return <div>{state}</div>;
      }`,
      },
      { parser: "tsx" }
    );

Oh btw, could you please generate a changeset for the package so it can be automatically versioned and deployed 🙏
yarn changeset and follow the prompts 👍

Oh btw, could you please generate a changeset for the package so it can be automatically versioned and deployed 🙏
yarn changeset and follow the prompts 👍

Will do 👍

Loooks good!! Thanks again!


Change the default background color

I only found out how to change the color scheme from dark to light (though it doesn't work), but I would like to change the color itself.
I also tried using a ZStack like so:
struct ContentView: View {
    static let inputId = "file"

    var document = JSObject.global.document

    var body: some View {
        ZStack {
            Color.blue
            Text("Hello, world!")
        }
    }
}

but the color is not fullscreen.
I found out what you can use width: 100vw;, but the .frame() modifier only accepts a CGFloat.

A flexible frame should fill the screen:
.frame(minWidth: 0, maxWidth: .infinity, minHeight: 0, maxHeight: .infinity)

It doesn't work, and/because it generates invalid property values:

The only way I've found this to work is to set an explicit width and height in a nested VStack:
struct ContentView: View {

	var body: some View {

		// This ZStack will be for the main background color
		ZStack(alignment: .center) {

			VStack {
				Text("this is a text view")
					.foregroundColor(Color.white)
					.background(Color.blue)
			}
			.frame(width: 1200, height: 500)
			.background(Color(.yellow))
		}
		.frame(minWidth: 0, maxWidth: .infinity, minHeight: 0, maxHeight: .infinity)
		.background(Color(.green))

	}
}

Actually I've found another way, and this doesn't depend on defining the frame size of any subviews.
Similar to the above, except instead of the root view being a ZStack, it's HTML with a div using flexbox's centering:
struct ContentView: View {

	var body: some View {

		HTML("div", ["style": "display: flex; justify-content: center"]) {

			Text("this is a text view")
				.foregroundColor(Color.white)
				.background(Color.blue)
		}
		.fullFrame()
		.background(Color(.green))
	}
}

In the version, "0.5.0" this not happened. https://github.com/TokamakUI/tokamak-todo-example @MaxDesiatov @revolter


'Conflict with GPU', HD client wont work.

Environment :

OS: Windows 10
RuneLite version: latest

I know nothing about computers but was hyped to use the HD plugin.  I have the plugin installed, and when i hover over the bar to turn it on, it says 'Conflicts with GPU'.  If i press the bar, it goes orange for about 1 second and freezes the client, then goes back to grey and back to normal with no HD.  I understand this same thing was happening to Mac users, but i am on my windows pc.  Pretty sure i dont have a graphics card which people told me could be the problem, but if anyone can tell me why i cant use this plugin or what steps i could take to use it, that would be great, thanks.

same thing

The message Conflicts with GPU refers to the RuneLite plugin GPU, which is installed by default. 117 HD (beta) and GPU cannot be activated at once. Thus, this is not related to your issue.
Please check your latest client.log in %userprofile%. runelite\logs for any errors related to RLHD.

My issue was fixed by simply updating my windows .

I have both my gpu and 117 hd off and when i try to turn on hd it still switches right off. it's not conflicting with gpu so thats not the issue like jorisblanken said. but i will try to update my windows like omrooo1 did and see how it goes.

I have both my gpu and 117 hd off and when i try to turn on hd it still switches right off. it's not conflicting with gpu so thats not the issue like jorisblanken said. but i will try to update my windows like omrooo1 did and see how it goes.

I'm not saying the problem is that GPU is on, I'm just explaining what the message means. The message it displays is not an error.

I have both my gpu and 117 hd off and when i try to turn on hd it still switches right off. it's not conflicting with gpu so thats not the issue like jorisblanken said. but i will try to update my windows like omrooo1 did and see how it goes.

I'm not saying the problem is that GPU is on, I'm just explaining what the message means. The message it displays is not an error.

I know its not an error or bug with the plugin, im just looking for help on how to enjoy it for myself.  The gpu plugin is not on for me.  How do i check the client log?  also would re-downloading runelite help at all, thanks for your time

I have both my gpu and 117 hd off and when i try to turn on hd it still switches right off. it's not conflicting with gpu so thats not the issue like jorisblanken said. but i will try to update my windows like omrooo1 did and see how it goes.

I'm not saying the problem is that GPU is on, I'm just explaining what the message means. The message it displays is not an error.

I know its not an error or bug with the plugin, im just looking for help on how to enjoy it for myself. The gpu plugin is not on for me. How do i check the client log? also would re-downloading runelite help at all, thanks for your time

Please post your latest client.log from %userprofile%. runelite\logs in Windows 10.

Runelite HD will NOT work if your computers graphic card is intagrated. The message you get saying conflicts with GPU ISN'T to do with the GPU plug in. I repeat it's NOT working due to graphic cards that are intagrated.

Runelite HD will NOT work if your computers graphic card is intagrated. The message you get saying conflicts with GPU ISN'T to do with the GPU plug in. I repeat it's NOT working due to graphic cards that are intagrated.

The message is definitely referring to the 'GPU' plugin. Try hovering over the 'GPU' plugin's enable button, it states "Enable GPU; Conflicts with 117 HD (beta)". RuneLite is considering changing this message for more clarity.
For actual errors, consult your client.log.
Integrated graphics cards may or may not work depending on the version of OpenGL your drivers support. Newer cards tend to support at least OpenGL 4.3 (which is needed for compute shaders).

This can now be closed


Warn about mismatched Dockstore UI and webservice

Feature Request
Desired behaviour
Option 1) Automated check if ui2 tests are running against an out-of-date webservice
May need to use encrypted token, send message to funkbot or slack
Build messages channel
Option 2) Banner that shows up for developers (locally or in staging) if the ui version is expecting a webservice version that does not match (the UI essentially should know its version, if only through what version was used to generate swagger classes)

Might be able to share code with #1321

What is an out-of-date webservice version. Does this refer to any release that is not the most recent?

I think we settled on option 2 in the post mortem actually

As per the discussion this can be merged into a general banner that exists on staging to make it obvious that you are on staging.
This option could either be a field similar to launch firecloud, or we could use environment configs.

Depends on #1346

Making a note here that it seems like the version generation code for generating the versions.ts does not work if you run in sudo mode.

Hmmm, the compose setup basically runs as root too.

Ran into this with 1.5.2. hotfix release, need to revisit


Add support for cuda 11.3

As far as I can tell the only gpu  support is for cuda <=11.2

Actually: good news! The CUDA 11.1 wheel should work for 11.2 and 11.3. We're going to document this in the next release of jaxlib.
With the released CUDA 11.1 jaxlib wheel, you may need to set the environment variable XLA_FLAGS=--xla_gpu_cuda_data_dir=/usr/local/cuda/, but that should be fixed with the next release.
Please try it out and let us know if it works!

We just released jaxlib 0.1.66, which should support CUDA 11.3 without any workarounds. Install the cuda111 variant of the wheel, which should work on CUDA 11.3 without any special setup.
Hope that helps!


Select random color from the mui theme palette

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
I want to randomly select a color from my palette. I can build a function to get that but I want to know if MUI provides it or not? If not, can we have a helper function with MUI to do this?
Examples 🌈
No response
Motivation 🔦
No response

See Stack Overflow question.


After computing delayed dask from numba, opening subprocess hangs on repeated sched_yield

Summary of bug
Under a particularly specific set of circumstances, computing a dask array from a dask.delayed call based on a numba function leads any subsequent calls to subprocess.Popen to hang with 100% CPU on Linux kernel 4.12.14.  The strace command reveals a thread calling sched_yield repeatedly, apparently stuck in an infinite loop.  I'm not sure if this problem is due to numba or dask or llvm or somewhere else, I'm reporting it here because it appears since upgrading numba from 0.48 to 0.50 (it does not appear with 0.48).  If this is the wrong place, please excuse me and kindly point me to the right place :)
MCVE
The main file:
import numpy
import dask
import dask.array
import mwe_weird
import numba
dask.config.set(scheduler="threads")
nx = ny = 500
@numba.jit(nopython=True, parallel=True, cache=True)
def calc():
    return numpy.zeros((nx, ny), dtype=numpy.float32)
delayed_func = dask.delayed(calc, pure=True)
delayed_res = delayed_func()
oops = dask.array.from_delayed(
        delayed_res,
        shape=(nx, ny),
        dtype=numpy.float32)

oops.compute()
import subprocess
subprocess.Popen(["cat /dev/null"], shell=True)

The secondary file mwe_weird.py:
import numpy
import numba

@numba.jit(
        ['UniTuple(float32[:, :], 3)(float32[:, :], float32[:, :])',
         'UniTuple(float32[:, :], 3)(float64[:, :], float64[:, :])'],
        nopython=True, parallel=True, cache=True)
def calc_gradient_vector(BT_t0, BT_t1):
    (nx, ny) = BT_t0.shape
    vbtfx = numpy.zeros((nx, ny), dtype=numba.float32)
    vbtfy = numpy.zeros((nx, ny), dtype=numba.float32)
    vbtfz = numpy.zeros((nx, ny), dtype=numba.float32)

    return (vbtfx, vbtfy, vbtfz)

Clues (perhaps)
Calling the main file causes Python to hang on the subprocess.Popen call.
The problem disappears if:

The unused import mwe_weird is removed, or
The type hints inside mwe_weird are removed, or
oops.compute() is removed, or
the numba.jit decorator is removed, or
the dask scheduler single-threaded or processes is used, or
calc is replaced by a direct dask.array.zeros(...) call, or
numba is downgraded from 0.50 to 0.48 and llvmlite from 0.33 to 0.31, or
probably other circumstances I have not seen.

The problem appears during the Popen call.  Calling the script with strace -o ... -ff python mwe.py reveals one file with many repetitions of the system call sched_yield until killed (at which point it had ten million such lines):
$ tail /tmp/strace.7559
sched_yield()                           = 0
sched_yield()                           = 0
sched_yield()                           = 0
sched_yield()                           = 0
sched_yield()                           = 0
sched_yield()                           = 0
sched_yield()                           = 0
sched_yield()                           = 0
--- SIGQUIT {si_signo=SIGQUIT, si_code=SI_KERNEL} ---
+++ killed by SIGQUIT (core dumped) +++

During this time, the process uses 100% CPU.
I don't know how to get a Python traceback for more specific pointing; even when running python -X faulthandler there is no traceback after killing (which I should probably expect to be absent with such a hard kill).  Regular interrupt (ctrl+C) has no effect.  Running python -m trace --trace ..., the final lines when it's hanging are:
subprocess.py(1635):                     fds_to_keep = set(pass_fds)
subprocess.py(1636):                     fds_to_keep.add(errpipe_write)
subprocess.py(1637):                     self.pid = _posixsubprocess.fork_exec(

Versions
Dask 0.20.0, numba 0.50,1, numpy 1.18.5, llvmlite 0.33.0, Python 3.8.3.  Tested on three different Linux systems, including one openSUSE 15.0 with Linux kernel 4.12.14-lp150.12.82-default and one Ubuntu 20.04 with Linux kernel 5.40.0-40-generic.
Further context
The problem appears to occur during a very specific set of circumstances and it took quite some time to come up with the minimal working example.  I hope what I came up with is minimal enough.  I don't know enough about the internals of either numba or dask to more specifically reproduce the circumstances.  Please let me know in case you need any further information.

[x] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[x] I have included below a minimal working reproducer (if you are unsure how
to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

Thanks for the report, great detail :) Two quick questions to start with:

Are you using TBB for Numba's threading layer?
Are the machines on which this is running pretty heavily loaded?

print(numba.config.THREADING_LAYER) gives default, which I believe means no (I did not knowingly set anything different)
No, the load is low to normal.

Thanks, I think default will be tbb if you have it in your environment. We've also noticed a few issues with TBB that end up in repeated calls to sched_yield in a "blocking" routine from quite some time back, though I think this particular case is a new one. gdb backtrace:
(gdb) bt
#0  0x00007f757f2aa777 in sched_yield () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f75638d1019 in tbb::internal::market::release (this=0x7f7563817580, is_public=<optimized out>,
    blocking_terminate=blocking_terminate@entry=true) at ../../src/tbb/market.cpp:192
#2  0x00007f75638d5f93 in tbb::internal::generic_scheduler::cleanup_master (this=<optimized out>,
    blocking_terminate=<optimized out>) at ../../src/tbb/scheduler.cpp:1392
#3  0x00007f75638d03da in tbb::internal::governor::terminate_scheduler (s=<optimized out>, blocking=<optimized out>)
    at ../../src/tbb/governor.cpp:209
#4  0x00007f75638d0516 in tbb::task_scheduler_init::internal_terminate (this=<optimized out>, blocking=blocking@entry=true)
    at ../../src/tbb/governor.cpp:501
#5  0x00007f75638d0572 in tbb::task_scheduler_init::internal_blocking_terminate (this=<optimized out>,
    throwing=<optimized out>) at ../../src/tbb/governor.cpp:510
#6  0x00007f75667e67ea in prepare_fork() ()
   from <path>/numba/numba/np/ufunc/tbbpool.cpython-37m-x86_64-linux-gnu.so
#7  0x00007f757f28c8dc in __libc_fork () at ../nptl/sysdeps/unix/sysv/linux/fork.c:96
#8  0x00007f757f7d9151 in subprocess_fork_exec () at /usr/local/src/conda/python-3.7.7/Modules/_posixsubprocess.c:686
#9  0x000055f874665a30 in _PyMethodDef_RawFastCallKeywords ()

will try and look into it some more during the next release cycle.
As a work around for now, if you've got OpenMP (the LLVM/Intel one, which is likely if you are using MKL backed NumPy) then it should work fine, try setting the environment variable NUMBA_THREADING_LAYER=omp. Hope this helps?

Right.  I confirm:

The problem disappears if I set NUMBA_THREADING_LAYER=workqueue
The problem remains if I explicitly set NUMBA_THREADING_LAYER=tbb
For NUMBA_THREADING_LAYER=omp, I get a ValueError: no threading layer could be found, but perhaps that's expected as I installed numba from binary wheels on conda-forge and I suppose OpenMP may be disabled there as well as on PyPI (in any case it is unrelated to the issue I reported here).

So as a workaround I could either install numba differently which should make omp work, or use workqueue.

Right. I confirm:
* The problem disappears if I set `NUMBA_THREADING_LAYER=workqueue`

Great, I'd hope this to work as workqueue can survive a fork(2) call.

* The problem remains if I explicitly set `NUMBA_THREADING_LAYER=tbb`

Thanks, I suspect that this is the problem, either Numba's doing something invalid with TBB or there's a problem in TBB itself. The backtrace https://github.com/numba/numba/issues/5983#issuecomment-658066490 shows a __libc_fork() as the trigger and I think it's TBB blocking whilst trying to park threads that's leading to a loop where sched_yield keeps being called (I think it's just seeing if it's unblocked, if not yielding the CPU, repeat).

* For `NUMBA_THREADING_LAYER=omp`, I get a `ValueError: no threading layer could be found`, but perhaps that's expected as I installed numba from binary wheels on conda-forge and I suppose OpenMP may be disabled there as well as on PyPI (in any case it is unrelated to the issue I reported here).

Ah yes, wheels have no OpenMP support because of a bug in patchelf that is I think fixed now. xref: https://github.com/numba/numba/issues/3400

So as a workaround I could either install numba differently which should make omp work, or use workqueue.

I think so.


Add R-square (coefficient of determination)

This PR adds the R² metric.
R² is more informative for linear regressions than MSE and RMSE (Chicco et al, 2021) because the scale is dimensionless (a percentage).
I value -3 in the test is manually calculated by me. All looks good.
EDIT: It doesn't work yet in CV. I get an _check(::RSquare, Vector{Int}). I'll debug it tonight or so

I don't get it (yet):
~/git/MLJBase.jl> julia --project

julia> using MLJBase

julia> using MLJModelInterface

julia> MMI = MLJModelInterface;

julia> include("test/_models/Constant.jl")

julia> m = ConstantRegressor();

julia> X, y = make_regression();

julia> e = evaluate(m, X, y; resampling=CV(), measures=[rms]);
Evaluating over 6 folds: 100%[=========================] Time: 0:00:00

julia> e = evaluate(m, X, y; resampling=CV(), measures=[rsq]);
Evaluating over 6 folds: 100%[=========================] Time: 0:00:00
ERROR: MethodError: no method matching _check(::RSquared, ::Vector{Float64})
Closest candidates are:
  _check(::MLJBase.Measure, ::Any, ::Any, ::AbstractArray) at /home/rik/git/MLJBase.jl/src/measures/measures.jl:61
  _check(::MLJBase.Measure, ::Any, ::Any) at /home/rik/git/MLJBase.jl/src/measures/measures.jl:53
  _check(::MLJBase.Measure, ::Any, ::Any, ::Any) at /home/rik/git/MLJBase.jl/src/measures/measures.jl:57
  ...
Stacktrace:
  [1] (::RSquared)(args::Vector{Float64})
    @ MLJBase ~/git/MLJBase.jl/src/measures/measures.jl:116
  [2] aggregate(v::Vector{Float64}, measure::RSquared)
    @ MLJBase ~/git/MLJBase.jl/src/measures/measures.jl:164
  [3] (::MLJBase.var"#298#304"{Vector{RSquared}, Vector{Vector{Float64}}})(k::Int64)
    @ MLJBase ~/git/MLJBase.jl/src/resampling.jl:1157
  [4] iterate
    @ ./generator.jl:47 [inlined]

I've read measures/README.md and checked the code and tests, but still have no idea whatsoever what an "aggregation" is. So, be careful when reviewing this PR in whether the aggregation is correctly specified (by being left empty).

Codecov Report

Merging #679 (5543cf6) into dev (8b75a34) will decrease coverage by 2.59%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##              dev     #679      +/-   ##
==========================================
- Coverage   85.29%   82.69%   -2.60%
==========================================
  Files          39       39
  Lines        3414     2965     -449
==========================================
- Hits         2912     2452     -460
- Misses        502      513      +11

Impacted Files
Coverage Δ

src/MLJBase.jl
100.00% <ø> (ø)

src/measures/continuous.jl
80.39% <50.00%> (-15.45%)
:arrow_down:

src/composition/learning_networks/arrows.jl
28.57% <0.00%> (-44.77%)
:arrow_down:

src/data/datasets.jl
86.84% <0.00%> (-13.16%)
:arrow_down:

src/sources.jl
74.28% <0.00%> (-10.16%)
:arrow_down:

src/show.jl
27.85% <0.00%> (-6.93%)
:arrow_down:

src/measures/measures.jl
68.29% <0.00%> (-5.40%)
:arrow_down:

src/measures/probabilistic.jl
58.46% <0.00%> (-4.70%)
:arrow_down:

src/composition/models/inspection.jl
95.83% <0.00%> (-4.17%)
:arrow_down:

... and 27 more

Continue to review full report at Codecov.

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

I've read measures/README.md and checked the code and tests, but still have no idea whatsoever what an "aggregation" is. So, be careful when reviewing this PR in whether the aggregation is correctly specified (by being left empty).

Thanks @rikhuijzer for this PR.
"aggregation" is a concept used in resampling in two ways

To aggregate the results gotten from calling UnAggregated performance measures on observations. (see section on per_fold in documentation for evaluate! function.)  See here also.
To aggregate the results from several measures to have one common numerical value. This is useful when calling evaluate/evaluate! functions with a vector of measures.  See here for definitions of existing aggregations and how to define new ones.

Thanks both for the comments, @ablaom @OkonSamuel :smile:. I've implemented them.

Now that the weighted call is removed, should supports_weights or supports_class_weights also be set to false?

Now that the weighted call is removed, should supports_weights or supports_class_weights also be set to false?

Oops, good catch. They should both be set to false. Can you push the change?

Nevermind, I'll do it when I merge your other PR.


MediaTek Dimensity 9000 Windows 11 support please

Prerequisites

[N] Have you read the wiki?
[I think yes] Is your device in the supported list?
[N, please MediaTek] Does the device have a Snapdragon SOC which is supported in this repo?


add etpcv school

@cnlc I am sorry, this request has signs of fraud. I have to close it without merging. If you are a student of this school, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


figure out if parts of the "How We Build Software" doc should be in ODH github, as ADRs or Developer Guides

figure out if parts of the "How We Build Software" doc should be in ODH github, as ADRs or Developer Guides
(internal) doc: https://docs.google.com/document/d/16JvVzp-cPDg5jPZpAPDZ2D6-ZCj_5gUbzcICwHsUBEA/edit

Migrated to Jira: https://issues.redhat.com/browse/RHOAIENG-1649


ci: expose code coverage reports

We seem to not be reporting to codecov.io anymore

added codecov token to buildkite secret env.


Fix typo in classes_and_objects

To clarify, there was a typo in the word assigning.
asigning -> assigning


Flip Billboard orientation for TextShape

When adding a billboard to an entity with TextShape, the default behavior is for the text to appear flipped around.
We would expect to be able to read the text always, but instead it keeps turning to face the opposite direction that it should.

Although one can work around this by applying the billboard to a parent entity and having the text rotated 180 degrees, this is not a friendly solution to content creators.
The default orientation of any entity that has a Billboard component + a TextShape component should be to always keep the text readable.

Note: TextShape is facing direction 0,0,-1 and that should not be changed, so we need no invert the billboard rotation
plus we need to remove initial component rotation: https://github.com/decentraland/unity-renderer/blob/50129111f39ea1d42c33e75af6dbc744a4e178f6/unity-renderer/Assets/DCLPlugins/ECS7/ECSComponents/TextShape/ECSTextShapeComponentHandler.cs#L43

Also take the opportunity to fix this https://github.com/decentraland/sdk/issues/608


Missing/inadequate current introduction about the purpose of the service manual, including how to use it effectively

What
Missing/inadequate current introduction about the purpose of the service manual, including how to use it effectively was mentioned by external users as current gaps during the recent user testing.
Why
So external users can easily and effectively use the service manual.
Done when
We have included in the service manual:

[ ] Explanation as to the purpose of the service manual, including how to use it effectively.

[ ] Suggestions from the recent user testing sessions for inclusion were: interoperability, open source, confidentiality, use of the service manual content where it will be used incorporating one’s own brand.

#993


Breaking Changes for v4.x

The following breaking changes are going to need to be added for a v4.x release

[ ] Update network_security_rule_resource.go (upstream) to allow source_application_security_group_ids and destination_application_security_group_ids to have MaxItems: 10

This is now in master pending release


Update kubernetes-service-principal.md

Correcting typo in az aks create

@vnextcoder : Thanks for your contribution to the Azure documentation! The author, @neilpeterson, has been notified to review your proposed change.

Thanks for the fix, @vnextcoder.
PR reviewers, @neilpeterson is out of office until next week, I am signing off in his stead. Thanks, -MM
#sign-off


[BUG] Invalid assignment / no type checking between the data field of Node types

Describe the bug
The Node type does not properly validate the data field when the receiving type is more specific than the source type during assignment.
See a live version of this in the typescript playground
Steps to reproduce the behavior:

Create a variable "foo" of type Node<A>
Create a variable "bar" of type Node (or Node<any>)
Assign bar to foo: foo = bar;

Expected behavior
I expect a typescript error because the more generic type should not satisfy the more specific type parameter.
Environment (please complete the following information):

@liveblocks/client: 0.19.0
@liveblocks/node: 0.19.1
@liveblocks/react: 0.19.0
@liveblocks/zustand: 0.19.0
typescript 4.9.4 (also tested 4.7.4)

The unknown case (CurrentWithUnknown) in the playground link is using any, not unknown (my mistake). When using unknown it works as expected, however the same behavior isn't shown in vscode when unknown is used. Investigating that a little further.

Carrying the example over, replacing the definition of Node in nodes.d.ts with this yields the correct behavior:
type NodeDetails = {
    id: string;
    position: XYPosition;
    type?: string;
    style?: CSSProperties;
    className?: string;
    sourcePosition?: Position;
    targetPosition?: Position;
    hidden?: boolean;
    selected?: boolean;
    dragging?: boolean;
    draggable?: boolean;
    selectable?: boolean;
    connectable?: boolean;
    deletable?: boolean;
    dragHandle?: string;
    width?: number | null;
    height?: number | null;
    parentNode?: string;
    zIndex?: number;
    extent?: 'parent' | CoordinateExtent;
    expandParent?: boolean;
    positionAbsolute?: XYPosition;
    ariaLabel?: string;
    focusable?: boolean;
    [internalsSymbol]?: {
        z?: number;
        handleBounds?: NodeHandleBounds;
        isParent?: boolean;
    };
};
export declare type Node<T = unknown> = NodeDetails & { data: T; };

though you could also use Node<T extends unknown = unknown> to prevent the use of any altogether.

Closing this, wrong project, haha.

@dabdine hehe covariance/contravariance in typescript can be tricky! Good luck with this

Definitely. This is not the first time I've run into this type of bug (fixed one recently in remix). FWIW liveblocks typedefs are pretty robust!
Next time I just need to make sure I'm on the right project 🤦


Remove phone validation when country isnt Brazil

Coverage remained the same at 82.138% when pulling a6527a5eb9c44aee1c6b5165324dd8a49fe0e172 on fix-phone into f76065e2992f4a48526e04883c704dfd0921d4e0 on master.

Coverage remained the same at 82.188% when pulling 836e1396e45b65c38e2e781eaec9b079efe1dd71 on fix-phone into 03bd521d804dab92d4c6e9dcb251f4953d880dea on master.

Coverage remained the same at 82.188% when pulling 499edf8dfec86e34fec098d0087e200cdcf313c6 on fix-phone into 03bd521d804dab92d4c6e9dcb251f4953d880dea on master.


[google_maps_flutter] Update README.md

For GoogleMap constructor it is required to pass initialCameraPosition

Signed CLA

Thanks for noticing this!
I just simplified the sample app in the README a bit in https://github.com/flutter/plugins/pull/1271


Drop support for Ruby 2.3 and 2.4

Per discussion in #1360

No need for it to go into this PR, but what is the status of building on Ruby 3.0? Are we waiting for libraries to update to be compatible?

No need for it to go into this PR, but what is the status of building on Ruby 3.0? Are we waiting for libraries to update to be compatible?

Middleman uses the deprecated URI::escape method which was removed in Ruby 3.0, so have to wait for an upstream release there before slate can support 3.0.

Middleman uses the deprecated URI::escape method which was removed in Ruby 3.0, so have to wait for an upstream release there before slate can support 3.0.

Sorry to have missed this, but does the Gemfile need updating too?
https://github.com/slatedocs/slate/blob/e546ad54c52d56089fee9c1376f18598d6408264/Gemfile#L1

Sorry to have missed this, but does the Gemfile need updating too?
https://github.com/slatedocs/slate/blob/e546ad54c52d56089fee9c1376f18598d6408264/Gemfile#L1


How to set the parameters of RandCropByPosNegLabeld() for pancreas segmentation (Task07_Pancreas)?

Dear Sir,
I want to segment the pancreas from CT images (Task07_Pancreas), so I have taken the Jupyter notebook code 'spleen_segmentation_3d_lightning.ipynb'. But, I got the following error:
raise ValueError("The size of the proposed random crop ROI is larger than the image size.")
ValueError: The size of the proposed random crop ROI is larger than the image size.
The error were occurring in the function RandCropByPosNegLabeld(keys=["image", "label"], label_key="label", spatial_size=(96, 96, 96), pos=1, neg=1, num_samples=4, image_key="image", image_threshold=0)
Please suggest how to solve this issue.
With thanks and regards
Shyamapada Mandal
Error.pdf

Hi @Shyamapada34 ,
Thanks for your interest here.
The error is because the data shape of some images in your dataset is smaller than (96, 96, 96), so it failed to crop.
Please try to adjust the crop size of spleen dataset to your dataset.
Thanks.


New component Switch

Feature
Switch component, inspired by the one in the mantine library - https://mantine.dev/core/switch/.
https://user-images.githubusercontent.com/25725586/160872989-52bf1481-de5b-4774-a905-5fe1cb77753a.mp4
Switch examples:
<div style="display: flex; flex-direction: column; flex: 1; height: 100px; justify-content: space-between;">
	<Switch label={"This is a label"} onLabel="ON" offLabel="OFF" />
	<Switch label={"I agree with the conditions I did not read"} size={"lg"}/>
</div>

Discussion
Would like to open discussion, since I used hardcoded colors, which will not match the active theme.

Your implementation is very nice. Some points before I merge:

Did you test that events work? For example, <Switch on:click={() => console.log("hello") />
The hard coded colors will be changed once the api for colors is fleshed out. So that is fine for now, I will clean it up when the time comes

Other than that, you've done a fantastic job!

Your implementation is very nice. Some points before I merge:
* Did you test that events work? For example, `<Switch on:click={() => console.log("hello") />`

* The hard coded colors will be changed once the api for colors is fleshed out. So that is fine for now, I will clean it up when the time comes

Other than that, you've done a fantastic job!

Ah, nice catch I forgot to test this. I moved the use:forwardEvents to the input, so that the users of this component can listen for on:change, similar to what you would do to a checkbox.


site.url should not be hard-coded to http://

This breaks https sites. Instead of http://lwchkg.github.io, set it to //lwchkg.github.io please.

Protocol relative URLs are an antipattern. Is there some way for the plugin to detect if a site uses HTTPS and always use that when available?

@pathawks With reference to what you say, site.url should be hardcoded to https:// instead of http:// here. There is no need to detect whether the site use HTTPS anyway, because this repo is github specific, which automatically calculates site.url for github pages.

I believe we get this information from the server one way or another (Pages.ssl? maybe?), so we don’t want to hard-code anything here. If you’re getting this locally, it’s because the API won’t tell unauthenticated (anon) users anything about Pages by default.

@parkr I did get nothing for site.url locally with this gem, which is good. Where I get the bad results is the actual GitHub Pages, and that's why I come here for the bug report.
If we didn't hard-code anything in this repo, then yes it means something is wrong in the GitHub servers. (I forgot about the cases about custom domains in a previous comment. But the GitHub employee handling that show know the best anyway. :-) )

Agree with the above, that nothing should be hard coded. Locally, when in development mode, it should default to http://localhost'. In production, it should use the value passed by the GitHub API which takes into account if the pages has HTTPS enabled and enforced (e.g., a *.github.io` domain that a user has opted in to use HTTPs). See https://github.com/jekyll/github-metadata/blob/0a5fa43e9c477488a44f6006e95fc91d1e6f4cef/lib/jekyll-github-metadata/repository.rb#L167-L169.

if HTTPS enabled and enforced
@benbalter Oh thanks! I didn't recognize the presence of such an option exists (missed the blog posts). I'll enable the option now, and things will be fixed for my site.

Anyway, back to discussion. So the condition for the breakages are:

The site does not enforce HTTPS,
HTTPS is enabled, and
The HTTPS site is used.
(i.e. Legacy users of HTTPS site.)

And now we're certain that the problem lies on the GitHub API, which is outside this repo.
Are any of you GitHub employees, or have connections the GitHub people managing the API? If yes please help me by passing the issue to the right people. (If nobody replies within 48 hours, I assume none of you have connections, and I'll call GitHub support.)
P.S. this issue can be closed if the message is passed to the right people.

@lwchkg If a site has HTTPS enabled and a user manually types https:// to get to the HTTPS variant, but the owner does not enforce HTTPS, the user may see mixed content warnings. The workaround, as described above, is to manually specify site.url in your site's config, which this plugin will respect. GitHub can't automatically set the flag without the user opting in, as it could cause the same mixed content issues. We'd rather give the user the opportunity to make the change and test it out then potentially break a site in a way users may not understand immediately how to fix.

GitHub enable HTTPS on GitHub Pages.
https://blog.github.com/2018-05-01-github-pages-custom-domains-https/
So site.url always be wrong. Most of GitHub users will add workaround {{ site.url | replace: 'http://', '//'}}. How about to add new attribute like site.url_noscheme or something?

This library makes an API request to GitHub to get the URL. If there is no token, then it will always be HTTP. For GitHub Pages requests, the request is authenticated so site.github.url should contain https:// if you click "Enforce HTTPS" in your repository settings.


How can I provide "-include " options to the gcc

I am using Ceedling only for unit testing, mocking and coverage report generation, not for building the project.
The project is build with tools which utilize Kconfig. In order to provide the configured defines to Ceedling I am using the "-include" option of gcc to feed the autoconf.h file to all sources.
I noticed that all options added to the :defines: section in the project.yml are prepended with a '-D' before given to gcc, so I am not able to use this section for my purpose.
Is there a way to provide the "-include" somehow to gcc? (I have copied the standard definitions like "test_file_preprocessor" to my project.yml and added the option there, but I am sure there is a more elegant way to do it.

ok, finally found someone mentioning the flags section. This solves my issue:
:flags:
:test:
:compile:
:*:
- -include ../application/build/generated/autoconf.h


pre-commit hook

Hey again Todd :) Found this repo via Google, I swear.
I've been using pre-commit lately and it's pretty cool. I wonder if you think it would be useful to create a hook module for rstlint since I have had this annoying problem several times as well. I have a lot on my plate but if you're interested I could put something together when I get a chance. Let me know what you think.

Yeah, the idea is you add a line to .pre-commit-config.yaml in your git repo and pre-commit loads the hooks like a module. It's pretty much just a package manager for pre-commit hooks. Kind of a neat idea. There are some examples here. You pick and choose the ones you want.
Come to think of it, I'm not sure I actually need anything from you to do this. The modules for the hooks are their own separate repos. I'm still learning about pre-commit though and how it works. I'll try to spin something up and let you know if I get it working. I suppose you can probably close this issue.

Heh, okie doke. Yep, going to eagerly close this issue
Feel free to re-open if we find out otherwise

Refusal to add pre-commit hook seems like a good enough reason for me to avoid using this linter, even if there was a desired to add linting for that. That hook config can be found on almost all python linters and requires no maintenance at all. In fact it acts as metadata.

I think we beat the topic into the ground when we discussed it last year in this issue: https://github.com/twolfson/restructuredtext-lint/pull/51

Not sure how I missed that. Meanwhile doc8 supports it and also integrates with https://marketplace.visualstudio.com/items?itemName=lextudio.restructuredtext


Print warning if missing variables

The configure command should print meaningful messages if any of the required envars are not found. Otherwise users get cryptic message about proper CLI usage.

Fixed in commit adafd3b


Support Java 11 by backporting IntBuffer.slice(int, int)

This PR lowers the source and target JDK versions to JDK 11, fixing the missing IntBuffer#slice(int, int) method by creating a custom implementation and container class. My original intention was to extend IntBuffer, but the super constructor requires a bunch of parameters that I can't pull from the delegate

Hey, great addition, thanks! I only made it package private, since there is currently no need to expose this, I think.


windows 10 pipenv.vendor.pexpect has no attribute 'spawn'

On Windows10, Python3.6.5, pipenv 11.10.3, I get this error when I try to start a shell.
It worked fine for a while. I shared the volume to a linux instance (I know) and worked with it there. I think that's when the problems started with my Windows box.
So yeah, I probably shot myself in the foot there, but I don't see a way to start fresh again.
Can I just wipe it out and start fresh somehow?
In any case, here's the traceback:
$ pipenv shell
Traceback (most recent call last):
  File "c:\program files\python36\lib\site-packages\pipenv\core.py", line 2192, in do_shell
    c = pexpect.spawn(
AttributeError: module 'pipenv.vendor.pexpect' has no attribute 'spawn'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\program files\python36\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\program files\python36\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Program Files\Python36\Scripts\pipenv.exe\__main__.py", line 9, in <module>
  File "c:\program files\python36\lib\site-packages\pipenv\vendor\click\core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "c:\program files\python36\lib\site-packages\pipenv\vendor\click\core.py", line 697, in main
    rv = self.invoke(ctx)
  File "c:\program files\python36\lib\site-packages\pipenv\vendor\click\core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "c:\program files\python36\lib\site-packages\pipenv\vendor\click\core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "c:\program files\python36\lib\site-packages\pipenv\vendor\click\core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "c:\program files\python36\lib\site-packages\pipenv\cli.py", line 607, in shell
    three=three, python=python, fancy=fancy, shell_args=shell_args
  File "c:\program files\python36\lib\site-packages\pipenv\core.py", line 2206, in do_shell
    pew.workon_cmd([workon_name])
  File "c:\program files\python36\lib\site-packages\pipenv\patched\pew\pew.py", line 381, in     workon_cmd
    shell(env, cwd=project_dir)
  File "c:\program files\python36\lib\site-packages\pipenv\patched\pew\pew.py", line 208, in shell
    shell_name = Path(shell).stem
  File "c:\program files\python36\lib\pathlib.py", line 999, in __new__
    self = cls._from_parts(args, init=False)
  File "c:\program files\python36\lib\pathlib.py", line 656, in _from_parts
    drv, root, parts = self._parse_args(args)
  File "c:\program files\python36\lib\pathlib.py", line 640, in _parse_args
    a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not NoneType

Here's the result of pipenv.help minus the pipfile.lock contents because there's a lot.
$ python -m pipenv.help
<details><summary>$ python -m pipenv.help output</summary>

Pipenv version: `'11.10.3'`

Pipenv location: `'C:\\Program Files\\Python36\\lib\\site-packages\\pipenv'`

Python location: `'C:\\Program Files\\Python36\\python.exe'`

Other Python installations in `PATH`:

  - `2.7`: `C:\Python27\python.exe`
  - `3.6`: `C:\Program Files\Python36\python.exe`

  - `3.6.5`: `C:\Program Files\Python36\python.exe`
  - `2.7.13`: `C:\Python27\python.exe`
  - `3.6.5`: `C:\Windows\py.exe`

PEP 508 Information:

```
{'implementation_name': 'cpython',
 'implementation_version': '3.6.5',
 'os_name': 'nt',
 'platform_machine': 'AMD64',
 'platform_python_implementation': 'CPython',
 'platform_release': '10',
 'platform_system': 'Windows',
 'platform_version': '10.0.16299',
 'python_full_version': '3.6.5',
 'python_version': '3.6',
 'sys_platform': 'win32'}
```

System environment variables:

  - `ALLUSERSPROFILE`
  - `APPDATA`
  - `COMMONPROGRAMFILES`
  - `COMPUTERNAME`
  - `COMSPEC`
  - `COMMONPROGRAMFILES(X86)`
  - `COMMONPROGRAMW6432`
  - `EDITOR`
  - `EXEPATH`
  - `HOME`
  - `HOMEDRIVE`
  - `HOMEPATH`
  - `LANG`
  - `LOCALAPPDATA`
  - `LOCALDFS`
  - `LOGONSERVER`
  - `MSYSTEM`
  - `NUMBER_OF_PROCESSORS`
  - `OS`
  - `PATH`
  - `PATHEXT`
  - `PLINK_PROTOCOL`
  - `PROCESSOR_ARCHITECTURE`
  - `PROCESSOR_IDENTIFIER`
  - `PROCESSOR_LEVEL`
  - `PROCESSOR_REVISION`
  - `PROGRAMFILES`
  - `PS1`
  - `PSMODULEPATH`
  - `PUBLIC`
  - `PWD`
  - `PROGRAMDATA`
  - `PROGRAMFILES(X86)`
  - `PROGRAMW6432`
  - `SESSIONNAME`
  - `SHLVL`
  - `SYSTEMDRIVE`
  - `SYSTEMROOT`
  - `TEMP`
  - `TERM`
  - `TERM_PROGRAM`
  - `TERM_PROGRAM_VERSION`
  - `TMP`
  - `UATDATA`
  - `USERDNSDOMAIN`
  - `USERDOMAIN`
  - `USERDOMAIN_ROAMINGPROFILE`
  - `USERNAME`
  - `USERPROFILE`
  - `VBOX_MSI_INSTALL_PATH`
  - `VSCODE_CWD`
  - `VSCODE_IPC_HOOK`
  - `VSCODE_NLS_CONFIG`
  - `VSCODE_NODE_CACHED_DATA_DIR_8980`
  - `VSCODE_PID`
  - `WINDIR`
  - `_`
  - `PYTHONDONTWRITEBYTECODE`
  - `PIP_PYTHON_PATH`

Expected result
Expected the pipenv shell to start.
Actual result
Traceback above.
Steps to replicate
Not sure.

Step 1) uninstall pipenv
Step 2) reinstall it
This should fix the problem, we will have a new release out shortly as well, but let us know if this doesn't help

That worked, thanks. Now I'll try to remember to not use multiple OS's in the same repo!


Option serialization not capturing value

When Some serializes, it doesn't capture the value, e.g.:
SourceResourceId = Option<string>.Some("A")

serializes to:
"SourceResourceId": {
        "Kind": "Some"
      }

https://learn.microsoft.com/en-us/dotnet/standard/serialization/system-text-json/custom-contracts#example-serialize-private-fields

https://stackoverflow.com/questions/61869393/get-net-core-jsonserializer-to-serialize-private-members


JBDS-3656 The installer should use Vagrantfile provided by CDK.

Use cdkv2 instead of cdk_v2.

released to master