Avoid applying compiler plugin to unsupported native targets

Otherwise, we get:
e: Compilation failed: Cannot find the Composer class in the classpath

Hi team, in addition to the change above, I'd be interested in adding targets - even among those that are supported - and NOT enable compose for them. Currently this is not possible because of the error above, and the root issue is that compiler plugin application and dependencies are intentionally out of sync, one is done by the plugin, the other by the user. This can be a source of problems for some.
How could we enable this scenario? Some ideas:

Global gradle.properties flag: if found, we ignore the Cannot find the Composer class in the classpath error. But I'm not sure if possible to ignore errors in the plugins pipeline.
Gradle extension function, like needsCompilerPlugin((KotlinTarget) -> Bool), defaults to { true }. Flexible, maybe it may suffer from some race conditions.
Change compiler plugin so that instead of throwing Cannot find the Composer class in the classpath, it just returns. If you think about it long enough, I think it makes sense. If there's no Composer class, there can't possibly be any @Composable? so there's no need for the compiler plugin to run at all, but also no need to throw.

Note: if I implement any of the above, it would be in another PR and only after your feedback. So feel free to merge this.

I'm wondering in what case you see e: Compilation failed: Cannot find the Composer class in the classpath.
This erros probably means that you applied the compose plugin but didn't add implementation(compose.runtime) dependency to your source sets.

To reproduce, you can just add one of the androidNative() targets. Which don't have a runtime available.
In fact, now that coroutines have androidNative support, Compose Multiplatform could support these too, but that's a separate issue.

In fact, now that coroutines have androidNative support, Compose Multiplatform could support these too, but that's a separate issue.

Nice. We'll consider that. Besided coroutines, we need atomic-fu as well.

Let me ask more details about your intentions.
So you have multiple targets in your module and you apply compose gradle plugin to that module. Right?
Do you have a common source set in that module? If so, you don't plan to use anything Compose related in it, right?
Do you want to use Compose (I mean declare and call Composable functions) only in platform-specific source sets?

We didn't consider a use case with mixing supported and not supported targets within one module.
If you can't or don't want to use Compose for one of the targets while using it for others, the current advise is to split your module into 2+ modules.
You mentioned androidNative(), so currently you can't use Compose in it, but you want to have it as a target. Right? But do you want to use Compose in it if it was possible? Or you just want to have it as a target and make Compose plugin not complain about it?

Besides coroutines, we need atomic-fu as well.

Yeah, they are available too. All kotlinx libraries are AFAIK.

You mentioned androidNative(), so currently you can't use Compose in it, but you want to have it as a target. Right?

Right!

But do you want to use Compose in it if it was possible? Or you just want to have it as a target and make Compose plugin not complain about it?

Both.
I have a module where compose runtime is used in a non-UI way. There, I would really like to use it in androidNative.
But then I have other modules which use compose UI, where it would make no sense in androidNative, and I'd just like the plugin to not break the androidNative build.
KMP is smart enough to let me choose when to add the dependency:
kotlin {
    val composeMain by sourceSets.creating {
        dependencies { api(compose.runtime) }
    }

    // Then, select targets to depend on composeMain...
    iosArm64 { compilations["main"].defaultSourceSet.dependsOn(composeMain) } // compose
    androidNativeArm64() // no compose
}

So I'd like the same level of flexibility from the plugin application. Could be solved in many ways I think -- downgrade the error to a warning is my favourite. No runtime implies no @Composable which implies no need for plugin to run at all.

Thank you @natario1
We'll take some time to discuss how to approach such use cases and provide the flexibility to configure the plugin.

Thanks guys. @eymar let me just add something which came to mind, maybe it will simplify things.
If a target is supported by compose (say iosArm64), but I don't want to enable compose in it, there's a simple trick to avoid the error: just use compileOnly(compose.runtime) as a dependency. It's not a perfect solution, ideally the compiler plugin should not even run, but it is a workaround at least.
So if we had the androidNative runtime, all the use cases would have a solution/workaround:

for androidNative modules where I don't want to use compose, add compileOnly(compose.runtime)
for androidNative modules where I'd like to use compose, add implementation(compose.runtime)

androidNative has been recently added to all kotlinx libs, because of the tiers definition. https://kotlinlang.org/docs/native-target-support.html

@natario1 This https://github.com/JetBrains/compose-multiplatform/issues/3695 can be interesting to you. There is a workaround.
Anyway, we're working on a proper solution for this.


fix com.apple.macl protected drag and drop

You shouldn’t need this extra delete logic, there is a method called makeuploadtempfile which should do what you need. Can copy the flow for pasting an attachment into chat

I assume this if for the case for dragging an attachment in that isn’t a real file yet?

It’s a file on the file system, but with that date which adds the protection that it can only be accessed from the process that this is dropped on to.
I’ll look for that RPC in service

@chrisnojima importing os is failing here. We are only using the tmpdir here for the KBFS part. In the long run I wanna move all these KBFS upload logic to Go by having an upload manager there (similar to Files download, or chat upload). But short term is there a way to make os import work, or should I just hard code a path in there?


 The output doesn't tell me much about the origin. I can find the first string in some version includes in my code but I fail to see at the moment if this is a problem with doxygen or asciidoxy or something else altogether.

There are still some cases where the parsing goes wrong. This parsing only affects whether AsciiDoxy is able to create hyperlinks for the types. I think I need to improve these messages, and hide some of the debug details in there.

In the next version the log output will be different. It will explain what exactly the result of the issue is. See https://github.com/tomtom-international/asciidoxy/blob/develop/documentation/reference/known-issues.adoc for instructions on how to provide more information to help me fix the issues.

I become the parsing error
WARNING: Failed to parse args: Failed to parse type: Unexdpected end of nested types: (* ``
Root cause seemed to be a defined type of callback at my headerfile. I use ANSI C.
`/*****************************************************************************/
/*! function type of my Callback
*

this type defines the default callback function

\param   pvArg - User argument
\param   ulResult  - result code
*/
typedef uint32_t  (DEFAULT_CB) (void pvArg, uint32_t ulResult);`


update help of mrk_evenlyInBlocks

It says first input argument is 'mrk', but it is 'blk'.

Done.


Incorrect version of Immutable.js on http://facebook.github.io/immutable-js

Version on site is 3.3.0 while NPM version is 3.6.4  which means the website is missing some APIs like Immutable.Map#deleteIn.
To reproduce:
Go to http://facebook.github.io/immutable-js
Open console and enter the following
m = Immutable.Map()
m.deleteIn
// undefined

Thanks for the heads up! Fixed


merge from template-esm-only

LICENSE

chore(license): add year 2024

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 86.685%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
274

Relevant Lines:
312

💛  - Coveralls


how use multiple lexik_jwt_authentication in one project?

What do you mean by multiple? Please tell us more about what you need.

Closing due to the lack of feedback.


Increase default delay from 10 seconds to 60 seconds

https://github.com/jabrena/raton-loco/pull/10


Prefer qualname as a pjit_p name

If applying jit to a class method, it is often important to know the class name in the jaxpr.

Have you considered instead expanding util.fun_name that we use in a few places?

Yes, see my response to Sergei. Doing that broke tests and I'd rather make the minimal change that solves the problem I have (jaxpr readability).


add french translation

Hi
As far as I'm aware this is the current active repo
https://github.com/SDH-Stewardship/hltb-for-deck

ok thanks you


Add ppc64le support.

Checklist

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

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

@conda-forge-admin, please rerender

@ChristopherHogan It might be a good idea to have a second maintainer listed for this package -- not sure if @oskooi also works on this package but I noticed he is listed on all the other tools alongside you.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@ChristopherHogan This PR should be ready to review.

👍


[2.8] Stale secrets for impersonation user in downstream cluster

backport https://github.com/rancher/rancher/issues/44347

This issue is not fixed on v2.8-68e5d43e449fcd3ef73baf1caee98da6f0104eed-head
I still see stale secrets :
>  k get secrets -n cattle-impersonation-system | grep -i  user-h7hms
cattle-impersonation-user-h7hms-token-6r72c     kubernetes.io/service-account-token   3      3m57s
cattle-impersonation-user-h7hms-token-8kgwk     kubernetes.io/service-account-token   3      3m57s
cattle-impersonation-user-h7hms-token-tgq75     kubernetes.io/service-account-token   3      3m57s
>  k get secrets -n cattle-impersonation-system | grep -i  u-ocjra4tnyd
cattle-impersonation-u-ocjra4tnyd-token-gwf6f   kubernetes.io/service-account-token   3      4m18s
cattle-impersonation-u-ocjra4tnyd-token-n72zv   kubernetes.io/service-account-token   3      4m18s
>  k get secrets -n cattle-impersonation-system | grep -i u-b3ub6bhfl5
cattle-impersonation-u-b3ub6bhfl5-token-7snzz   kubernetes.io/service-account-token   3      4m2s
cattle-impersonation-u-b3ub6bhfl5-token-f5kzj   kubernetes.io/service-account-token   3      4m2s

This issue is partially fixed and opened a new issue for the remaining issue. I m closing this ticket as there are no regression issues with this fix. https://github.com/rancher/rancher/issues/47126


How to validate type for non array members

Hello,
I am trying to set up my model to validate non array members. I reviewed the documentation under https://romakita.github.io/ts-express-decorators/#/tutorials/ajv, and see AllowTypes can be used to specify the available types for a array, but I do not see how to do that for a non array member?
I've tried various combinations, mainly with Property and JsonProperty, and while I can get AllowTypes to return a validation error for a mismatch, my string member continues to allow number and boolean values (which end up being stringified).
Here is what my model looks like:
import { Required, Property } from "@tsed/common";

export default class Book extends Model {

 @Property()
  @Required()
  title: string

 @Property()
  @Required()
  isFiction: boolean
...
}

My endpoint:
@Post("/book")
  async postBook(@Required() @BodyParams("book") book: Book) {
   ...
  }

When I post to the endpoint, with this json:
{
	"book": {
		"title": 1111,
		"isFiction": -1

	}
}

This is what the object returned to my endpoint looks like:
{"title":"1111", "isFiction":true }

I would expect both properties to fail validation instead.
Thanks in advance for any help or information.

Thank you for your time and response.
I spent some time debugging today, and I think the actual cause of the issue is that the PrimitiveConverter is coercing these values before AJV is ever invoked.
I created a couple custom convertors like
@Converter(String)
export class StrictStringConverter implements IConverter {
  deserialize<T>(data: string, target: any, baseType: T, deserializer: IDeserializer): String | Number | Boolean | void {
    if (typeof data !== 'string')
      throw new BadRequest(`'${data}' is not a valid string.`);
    return data;
  }

  serialize(object: String | Number | Boolean): any {
    return object;
  }
}

... and now the errors thrown by the converters bubble up to the response. I can also just return the value (without testing typeof) and see AJV's exception bubbling up, but I think for now I'll leave this in the converter.
So, I guess this solves my specific issue.  If you had any interest in a change to allow this inherently in this framework, I would probably get around to making a PR :) . I'm not sure what you would have in mind as far as how it should be implemented.

I've right for the PrimitiveConverter. Is volunteer, responsability of the ConverterService is to try to converter an object to his model according the type Model description. But you're implementation
can be added as example for the documentation or in future, we can merge your work (PR) with the currents converters and provide an option to use a strict conversion.
@ServerSettings({
   converters: {
      modelStrict: true, // eq. validationModelStrict
      typeStrict: true // your options
   }
})

And an example of a converter:
@Converter(String, Number, Boolean)
export class PrimitiveConverter implements IConverter {
  typeStrict: boolean = false;
  constructor(settings: ServerSettingsService) {
     this.typeStrict = (settings.get('converters') || {}).typeStrict;
  }

  deserialize(data: string, target: any): String | Number | Boolean | void {
    switch (target) {
      case String: // example with the string
        if (this.typeStrict && typeof data !== 'string') {
             throw new BadRequest(`'${data}' is not a valid string.`);
        }
        return "" + data;

      case Number:
        const n = +data;

        if (isNaN(n)) {
          throw new BadRequest("Cast error. Expression value is not a number.");
        }

        return n;

      case Boolean:
        if (data === "true") return true;
        if (data === "false") return false;

        return !!data;
    }
  }

  serialize(object: String | Number | Boolean): any {
    return object;
  }
}

For information, Ajv Validation is ran before ConverterService.
https://github.com/Romakita/ts-express-decorators/blob/master/src/common/filters/class/FilterBuilder.ts#L21-L23
I tried this morning to configure Ajv, but I didn't find the right options...
See you,
Romain


Hover widget positioning relative to custom container (override document.body by default)

The problem
Editor may be used in custom container, non document root. As developer i want to customize this one.
Take a look at pucture with example. Hover widget are shown below line because iframe (document.body equal) does not have top offset space to show hover popup above line.

The solution
Use ariaContainerElement or add new property to standalone for override geometry calculation relative to custom container.
UPD:
allowEditorOverflow property for widgets looks like the solution, if editor container overflow is set to false the position of hover popup calculated with editor container, buy property allowEditorOverflow does not configurable in default widgets
Related to monaco editor issue https://github.com/microsoft/monaco-editor/issues/302

Hey guys! Whats up with this task? Can i make PR by myself?

Can you provide a playground example? Thanks!


Is possible to replace the json collumns in migrations for text on old versions of MySQL?

I dont think so because there are so many queries connected to those Json

@mauri870 and why do you want to do this?

Compatibility @gocanto... MariaDB for example not support the json datatype and MySQL support this natively after version 5.7.8

it would be nice tho, but There are so many modules a queries to check after this, dont u think?

Yep, many many queries :disappointed:
But is just a question :+1:

@mauri870 this is the thing. Antvel is working as it is, so we can invest that amount of time doing something else. Also, json is a MySQL feature now, so I don't see this a good idea!

I agree with you. I thought maybe it was something simple :confused:


Remove unused extras from all languages.

Remove these too?
https://github.com/osohq/oso/blob/50830cb59485afb96e576611f6932a0b57cef836/languages/python/oso/tests/parity/policies/test_api.polar#L9
https://github.com/osohq/oso/blob/50830cb59485afb96e576611f6932a0b57cef836/languages/python/oso/tests/parity/test_api_externals.py#L9-L50

I intentionally kept these / moved them into the Python test suite as part of https://github.com/osohq/oso/pull/571 since I think they do test some reasonably interesting behaviour.

https://github.com/osohq/oso/blob/50830cb59485afb96e576611f6932a0b57cef836/docs/examples/application/expenses-spring-boot/src/main/java/com/example/springboot/Authorizer.java#L4


issue: llama3.2 vision second image not being processed

Bug Report
Installation Method
docker
Environment
v0.3.35
Windows 10
Firefox 132.0.1 (64-bit)
Confirmation:

[ x] I have read and followed all the instructions provided in the README.md.
[ x] I am on the latest version of both Open WebUI and Ollama.
[ ] I have included the browser console logs.
[ ] I have included the Docker container logs.
[x ] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:
I should be able to continuously send images to vision-enabled models and have it see the attachment and describe the image.
Actual Behavior:
I start a conversation with a vision-enabled model (llama3.2-vision) and I attach an image and ask the model to describe the image attached.
The model responds correctly and describes the image.
In the same chat, if I attempt to attach another image, the model replies with "There is no image attached to your message."
Description
Bug Summary:
open-webui is not passing the image attachment to the model to be able to desribe it.
Reproduction Details
Steps to Reproduce:
start a conversation with a vision-enabled model (llama3.2-vision) and I attach an image and ask the model to describe the image attached.
The model responds correctly and describes the image.
In the same chat, if I attempt to attach another image, the model replies with "There is no image attached to your message."
Logs and Screenshots
Screenshots/Screen Recordings (if applicable):

Second.  My daughter is super sad. We're getting error 500s

Seems to be an issue with llama3.2-vision model, I'm unable to reproduce the issue with llava and other external vision models like gpt-4o.

Can confirm the image is being sent to Ollama as intended in the correct format, perhaps we might want to raise an issue on Ollama repo here.

There is a limitation with llama3.2-vision, it only accepts one image per request.  Same issue using a vLLM deployment of llama-vision model.  vLLM Docker logs provides a specific error stating the same.
Ref: https://github.com/vllm-project/vllm/issues/8826

There is a limitation with llama3.2-vision, it only accepts one image per request. Same issue using a vLLM deployment of llama-vision model. vLLM Docker logs provides a specific error stating the same.
Ref: vllm-project/vllm#8826

@davidamacey I read the other thread, but dont understand exactly what this means.  I am having the same issue where the second image is not being processed.  Does this mean to use another image you basically have to reload the model?  Many thanks for any clarification so those of us not super proficient at this can better understand.

@davidamacey I read the other thread, but dont understand exactly what this means. I am having the same issue where the second image is not being processed. Does this mean to use another image you basically have to reload the model? Many thanks for any clarification so those of us not super proficient at this can better understand.

I assumed he meant trying to attach two images to a single chat block - which actually doesn't work and throws an error for me

Ollama: 500, message='Internal Server Error',

In my opinion, his reference and my issue are separate.   What tjbck said makes sense and is likely not this app's fault.

Same here! the base64 encoded image is sent in the second request but the reply is odd

I am not sure if I should open a new issue, but I can confirm this is not due to Open WebUI. No matter what I do, llama3.2 vision focuses only on the first image. The tests at
vllm/tests/models/encoder_decoder/vision_language/test_mllama.py

nominally pass, but, if you print the model reponses, you do not get intended behavior.
The most direct way to reproduce this bug is by following PR  #9393
Serve the model
python -m vllm.entrypoints.openai.api_server \
    --device cuda \
    --model meta-llama/Llama-3.2-11B-Vision-Instruct \
    --api-key token-abc123 \
    --tokenizer meta-llama/Llama-3.2-11B-Vision-Instruct \
    --limit-mm-per-prompt image=2 \
    --max-model-len 32000 \
    --dtype=half  \
    --enforce-eager \
    --max-num-seqs 2

Then attempt a conversation
from openai import OpenAI
client = OpenAI(base_url="http://localhost:8000/v1", api_key="token-abc123")

conversation = []

def get_completion(prompt):
    conversation.append({"role": "user", "content": prompt})

    response = client.chat.completions.create(
        model="meta-llama/Llama-3.2-11B-Vision-Instruct",
        messages=conversation,
        max_tokens=150
    )

    assistant_response = response.choices[0].message.content
    conversation.append({"role": "assistant", "content": assistant_response})
    return assistant_response

chain_of_thought_steps = [
    [
      {"type": "image_url", "image_url": {"url": f"https://www.jampaper.com/media/wp-content/uploads/2014/04/cereal-box-e1397150195903.jpg"}},
      {"type": "text", "text": "Please describe this first image"},
    ],
    [
      {"type": "image_url", "image_url": {"url": f"https://cdn.awsli.com.br/600x450/1965/1965063/produto/17840338592397ef767.jpg"}},
      {"type": "text", "text": "Please describe this second image"},
    ],
    [
      {"type": "text", "text": "Compare the descriptions for the two images"},
    ],
]

for i, step in enumerate(chain_of_thought_steps):
    response = get_completion(step)
    print(f"Step {i + 1} Response: {response}")

What I get are two descriptions of cereal, despite the second image being of a doll.
I tried a myriad of other methods, such as sending both images in one message, to no avail. Would really appreciate help digging to the core of this bug. Referencing #9095 because it seems relevant.
Thank you

Same here.


Release notes for spkl task runner

I don't see any on the wiki here or at https://www.nuget.org/packages/spkl/.  Are they located somewhere?  If not, would you consider publishing some?

Thanks for the nudge! 👍  I need to get better at keeping the release notes up to date.
Here are the notes for the latest release - https://github.com/scottdurow/SparkleXrm/releases/tag/spkl-v1.0.226
There is a project board that tracks issues and enhancements - https://github.com/scottdurow/SparkleXrm/projects/1


Add support for swagger consistency checks

Usage:
be_consistent_with_swagger_at "example.com"

It will then then look at http://example.com/swagger.json, and check to make sure there are no inconsistencies.

Can you provide a definition of 'inconsistencies'? Is it just that the definitions blocks in the two swagger.jsons should match?

Kind of. The supplied uri should return a superset of all definitions, and the service being tested cannot have definitions which disagree with that source of truth.
So for example, at "example.com/swagger.json", there might be definitions:
product
category
And at the service being tested, there might be a definition:
category
This is fine, as long as the category documentation is identical between the two swaggers.

@mastfish so if I get this right you want to enforce via apivore that we use /swagger.json ?

Consider 2 services - one of them has a definition for "422Error" that refers to "product", and one has a definition of "422Error" that refers to "deal".
Then consider a third service, "api.westfield.io", that's trying to create a consistent swagger doc from both. Clearly, there's a merge conflict here, one that requires one (or both) of those services to change their "422Error" definitions.
This is designed so that trying to publish a "422Error" that disagrees with "api.westfield.io"'s swagger definitions throws an error, using it as a canonical source of truth.
It's opt-in, so upgrading apivore won't cause surprise errors, and it targets definitions only, because testing revealed that paths (should) have only one source of truth, so there's no need to cross-check them.

LGTM! Will be nice to bring all the definitions in line with each other.


don't load route planner key

The route planner key is not in the code, but can be set via configuration. For example:
https://bcgov.github.io/smk-client/debug/app/translink/?config={"tools":[{"type":"directions","routePlannerService":{"apiKey":"[key]"}}]}
Replace [key] with the route planner key
Use https://qqnluaq.github.io/smk-client/ in the url if the above doesn't work.


Include file '_includes/gauges.html' not found in _includes/after_footer.html

Hello!
I'm just going to remove this from my local version. What did this file have?
Let me know if you include this back.
Thank you!

Same as above


six-field cronlines with division syntax in the seconds field lose the beat

Howdy, thanks for building a terrifically useful gem.
Unfortunately, I've found an unexpected behavior: cronlines such as '*/10 * * * * *' exhibit a strange behavior where they lose their rhythm after a few beats.
It seems that the logic in Cronline.next_second() has a discontinuity when time.sec exceeds secs.last: it adds a minute, rather than rolling back around to secs.first.
I don't have a fix yet (apologies - still working on it) but I am about to post a PR which highlights the bug.

The PR which demonstrates this issue is PR https://github.com/jmettraux/rufus-scheduler/pull/164.

I believe the problem comes down to this line in Cronline.next_second(): https://github.com/jmettraux/rufus-scheduler/blob/master/lib/rufus/scheduler/cronline.rb#L297
It seems all of the new specs which I added, which fail, involve going through that early return logic.  All the existing specs, which pass, fall through to the bottom of the method.

Thanks a lot for the excellent report. Give me a few days.

You bet!

I fixed the issue and released 3.1.4.
Thanks a lot! Have a nice week-end!

Wow, that's awesome.  Thanks!


Fixes

Signed-off-by: Gbahdeyboh<EMAIL_ADDRESS>This PR fixes some basic issues across the whole tutorials.
It fixes the following issues:

#20
#18
#16
#17
#19

(Adding more)

@neelanjan00 @uditgaurav.
I have been taking a look at the Done button at the end of all the codelabs redirecting to a 404 page, but I've been unable to find a fix to it. It's a bit weird because it does not happen when I test the codelab using the Preview Code lab extension. It only happens after the code generation is done.
I would have edited the code, but the"Done" button is not a part of the code. A huge chunk of the UI is injected by some codelabs JS script.
I also had a look at the issues on the codelab repository, but couldn't quite find any issue around this specific problem.
I think the best I can do now is to file a new issue on the codelabs repository and hopefully someone from their community fixes it.

@neelanjan00 @uditgaurav.
I have been taking a look at the Done button at the end of all the codelabs redirecting to a 404 page, but I've been unable to find a fix to it. It's a bit weird because it does not happen when I test the codelab using the Preview Code lab extension. It only happens after the code generation is done.
I would have edited the code, but the"Done" button is not a part of the code. A huge chunk of the UI is injected by some codelabs JS script.
I also had a look at the issues on the codelab repository, but couldn't quite find any issue around this specific problem.
I think the best I can do now is to file a new issue on the codelabs repository and hopefully someone from their community fixes it.

@neelanjan00 can you lease review to see if the raised issues has been fixed?

LGTM, please fix these two typos then I will approve.

You can also fix the DCO check @Gbahdeyboh

I'm not sure why the DCO is not passing. My commits are signed-off


fix: Farming XP Progress Bar & Collection amount

Description
Fixes Farming Skill Progress bar above level 50 always being shown as 100% completed
Fixes Collections above integer limit not being shown
Examples

http://localhost:32464/stats/15h/Orange
Before

After

The Farming XP bar is working as intended, since it should be filled up when you reach your level cap since you can't progress further until you unlock the next level cap in Jacob's house. That's mainly why level cap of Farming also depends on what that perk is leveled at.
If there's something wrong with current approach, please describe it further.

Also after checking the collection thing, it's incorrectly noted as an "Collections above integer limit not being shown", since that should also be intended behavior since it only shows the collection count only collected by the user in a coop, not the total of the coop. You can actually check that by hovering on the collection.
In this case, I would rather suggest changing "Amount:" to "Total:" and by extension this wouldn't be a bugfix, but just a change of what we display.


Recognize work I used from Create-TypeScript-App

When setting up this repository and CLI, I used tons of ideas and code from create-typescript-app from @joshuakgoldberg.
@all-contributors please add @joshuakgoldberg for code, infra, ideas

#32


Computing Segmentation gives error RuntimeError: array type dtype('float16') not supported

Bug
When I ran the RGB 4 class model sat_RGB_4class_6950472 with the images included in RGB.zip I kept getting the error RuntimeError: array type dtype('float16') not supported. I believe the error is coming from skimage's resize function that is used within doodleverse_utils's do_seg function in the lineest_label = resize(est_label, (w, h)). est_label is of type float16 which is causing this bug to appear and (w, h) are both of type int so they aren't causing the problem. The bug appears for BEST and ENSEMBLE models and on all imagery I've tested it with,
I tried running the same model with coastseg and it worked just fine on these images. I cannot figure out why I'm getting exceptions here and valid results with coastseg.

RGB.zip
How I obtained the Error Message
I modified scripts/select_model_and_batch_process_folder.py to print the full traceback for the exception that occurred
import traceback
# Import do_seg() from doodleverse_utils to perform the segmentation on the images
for f in tqdm(sample_filenames):
    try:
        do_seg(f, M, metadatadict, sample_direc,NCLASSES,N_DATA_BANDS,TARGET_SIZE,TESTTIMEAUG, WRITE_MODELMETADATA,OTSU_THRESHOLD)
    except Exception as e:
![2019-01-25-18-57-02_RGB_L8](https://user-images.githubusercontent.com/61564689/206025024-6ced24f0-fbcb-4489-81f6-53c4fe6ed674.jpg)
![2019-01-25-18-57-25_RGB_L8](https://user-images.githubusercontent.com/61564689/206025027-638ba591-e27d-4833-abcf-274c2d985deb.jpg)
![2019-02-10-18-56-59_RGB_L8](https://user-images.githubusercontent.com/61564689/206025029-90331ce4-2494-4efa-b474-4fa67aa7b2e3.jpg)
![2019-02-10-18-57-23_RGB_L8](https://user-images.githubusercontent.com/61564689/206025034-e5dc2b9b-7b4c-41fc-9eca-3678c83ca5f3.jpg)

        print(e)
        print(traceback.format_exc())
        print("{} failed. Check config file, and check the path provided contains valid imagery".format(f))

Error Message
array type dtype('float16') not supported
Traceback (most recent call last):
  File "C:\1_USGS\5_Doodleverse\segmentation_zoo\segmentation_zoo\scripts\select_model_and_batch_process_folder.py", line 398, in <module>
    do_seg(f, M, metadatadict, sample_direc,NCLASSES,N_DATA_BANDS,TARGET_SIZE,TESTTIMEAUG, WRITE_MODELMETADATA,OTSU_THRESHOLD)
  File "C:\Users\Sharon\anaconda3\envs\zoo\lib\site-packages\doodleverse_utils\prediction_imports.py", line 442, in do_seg
    est_label = resize(est_label, (w, h))
  File "C:\Users\Sharon\AppData\Roaming\Python\Python39\site-packages\skimage\transform\_warps.py", line 147, in resize
    image = ndi.gaussian_filter(image, anti_aliasing_sigma,
  File "C:\Users\Sharon\AppData\Roaming\Python\Python39\site-packages\scipy\ndimage\filters.py", line 342, in gaussian_filter
    gaussian_filter1d(input, sigma, axis, order, output,
  File "C:\Users\Sharon\AppData\Roaming\Python\Python39\site-packages\scipy\ndimage\filters.py", line 261, in gaussian_filter1d
    return correlate1d(input, weights, axis, output, mode, cval, 0)
  File "C:\Users\Sharon\AppData\Roaming\Python\Python39\site-packages\scipy\ndimage\filters.py", line 133, in correlate1d
    _nd_image.correlate1d(input, weights, axis, output, mode, cval,
RuntimeError: array type dtype('float16') not supported

My Environment
OS: Windows 10
Doodleverse_utils: 0.0.16
Tensorflow: 2.11.0
Latest and up to date version of segmentation zoo
0 GPUs: on my machine. I used SET_GPU='-1'

The resize function is being passed an array of type float16 (a 16-bit floating-point number), which is not supported.
The solution is to convert the est_label array to a different data type before passing it to the resize function. You can do this using the astype method, like this:
est_label = est_label.astype('float32')
This will convert the est_label array to type float32, which should be supported by the resize function.
@ebgoldstein  thanks for the help!

This issue was fixed in doodleverse_utils 0.0.18


Out-GridView filtering via criteria in 7.4.0-preview.5 yields incorrect results

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Using the "Add criteria" and filtering that way in 7.4.0-preview.5 yields incorrect results:
@(@{"a" = '=='},@{"b"='<='},@{"c"='>='}) |ogv

Here's the correct outcome with 7.3.6:

Expected behavior
Objects matching the specified filter should be displayed.

Actual behavior
Filtering removes all objects even those matching the criteria.

Error details
No response
Environment data
Name                           Value
----                           -----
PSVersion                      7.4.0-preview.5
PSEdition                      Core
GitCommitId                    7.4.0-preview.5
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

The fundamental problem is that when we removed use of BinaryFormatter this completely broke out-gridview which depended on it as a way to copy filter rules.  The manual clone() workaround wasn't sufficient.  Tried using XmlSerializer and reflection, but neither works the same as BinaryFormatter to get an exact copy.


Reorganizing environment variables documentation

Is your request for enhancement related to a problem? Please describe.

Documentation for configuring environment variables is split across two areas: Setup and Use.
This makes it hard for the end user to find all the documentation for environment variables, with one site or the other giving the impression that it is the only source of environment variables documentation.
Describe the solution you'd like

Proposal is two-fold:

Include a link in the Configuring Zowe CLI environment variables page to a page with the more advanced configurations for environment variables.
Reorganize/split the environment variables content in the Use section so that it is separated into subject areas that make more sense to the user:

Using environment variables

Using environment variables
Formatting environment variables
Setting environment variables in an automation server

Using the prompt feature
Writing scripts

Related doc pages

From the Setup section:
https://docs.zowe.org/stable/user-guide/cli-configuringcli-ev
From the Use section:
https://docs.zowe.org/stable/user-guide/cli-using-completing-advanced-tasks
Additional context

This documentation has been completed. See the following PR:
https://github.com/zowe/docs-site/pull/2365


Ank CLI waits for server response and correct workload states

Issues: #13
When Ankaios CLI uses the set state command, it shall wait for the response for the server and for all changed workloads to reach the desired state.
Definition of Done
The PR shall be merged only if all items mentioned in CONTRIBUTING.md have been followed. In case an item is not applicable as described, please provide a short explanation in the description.

[ ] All steps in CONTRIBUTING.md have been handled

I found a couple of things while trying the feature out:

If a creation of a container fails (e.g., due to a port in use), the output get scrambled:

In case all is fine and the expected outcome is there, the indentation looks a bit strange:

If I update a workload only regarding dependencies (run a server with default_config_with_dependencies.yaml and update workload_A via ank set state to not have any dependency, s.t. it can immediately start), the CLI never exists (I suppose, because it waits for the deleted workload to be announced)

Didn't we wanted to add a watch flag to the ank get workloads? If I remember incorrectly and this was not in scope, we can create another issue for it


[Performance] Fast unmount optimisation

PR Template
Enabled fastUnmount optimisation for ES6 classes and Functional components.
This is achieved by defining componentWillUnmount as undefined for ES6 classes. Then at the time of mounting component we check if ref / componentWillUnmount / onComponentWillUnmount is defined and disable fastUnmount if any of them is.
I also added tests for fastUnmount for functional components and fixed minor issue with lifecycle.
Performance was increased about 5% rendering and 10 - 50% unmount speed. in uiBench. For both classes and functions. Filtering tests also increased about 10%
repository used for benchmarking:
https://github.com/Havunen/uibench-inferno
ES6class-uiBench.html.zip

Attached ES6 benchmark zip of uiBench with 15 iterations compared to DEV
Note: This change would show better results the longer the component chain is without unMount callbacks defined.

Awesome work man :) LGTM

Let's also let @thysultan and @nightwolfz to check it over too. It's late here, I might have missed something and this is a major refactor.

LGTM. Is there a reason we can't apply this to the other lifecycle hooks though?

what @LukeSheard said, i feel like all the other empty functions being assigned to the components prototype could be removed inc shouldComponentUpdate to further reduce overhead of instantiating a component instance. @Havunen what happens when the component doesn't have componentWillUnmount but a child in it's children has one?

@LukeSheard I feel like there won't be much benefit on other hooks because they are called on regular routine, unmount is sepcial because it has recursive logic and this "fastUnmount" short circuits it.
@thysultan if children has unMount callback defined then optimisation is disabled. I wrote test for that also.

@Havunen I don't know how inlining works with empty functions but functions do have a inherit cost of being called, which can add up. So if you create many class components this could be a cost that is paid for every component on every render for no reason, so that maybe something to look into.


Documentation missing placeholderColor in core plugin list.

Small bit of documentation missing on https://tailwindcss.com/docs/configuration/
Below text Here's a list of every core plugin for reference
It is missing placeHolderColor in the list which does appear to work as core plugin option.

I guess this should be an issue for the docs: https://github.com/tailwindcss/docs/issues


bug: confusing "doc" diff view

Version
v0.16.1
Describe the bug
I ran the /doc command (from the command palette) and saw some strange behavior with both the diff view and the "Undo" action. Loom.

The diff view tab calls it a "fixup" diff, but this is for the documentation command
The diff itself doesn't show the documentation that was added, but rather a change to the code
Clicking "undo" doesn't remove the documentation, but changes the code

Expected behavior
The only time I can imagine someone wanting to see a diff view of the documentation is if they're running the doc command on code that already has documentation, and that documentation is changing. So maybe not a super common use case?
Either way, I'd expect the diff view to represent the change to the documentation and not change the documented code at all. I'd expect "undoing" the documentation to undo the documentation and not affect the code.
Additional context
No response

Oops, one more thing I noticed. "Retry" has pretty bad UX. Loom. If we can't make it easier to read/edit the prompt, I think we should just remove "Retry" from the ghost text for the doc command.

Cc @umpox who's been working on the UX update for /doc

@taylorsperry Thanks for the videos!
I'm going to list the issues and the current state:

Diff view tab named "Fixup" -> We should change this to "Edit", then it covers all cases and makes more sense to a user.
The diff itself doesn't show the documentation that was added, but rather a change to the code -> Fixed in latest release (see video below)
Clicking "undo" doesn't remove the documentation, but changes the code -> Fixed in latest release (see video below)
Retry UX poor UX. -> We're quite limited here as VS Code doesn't provide a multi line input. I think we can keep it still because it still provides other functionality (users can easily delete the entire text and provide their own prompt - I've done this a few times). Users may also just want to re-submit the prompt. The "retry" field makes a lot more sense for user provided edits, like "comment this code" -> Retry -> "comment this code inline".

https://github.com/sourcegraph/cody/assets/9516420/cc74ed2c-44a0-4ffc-a4f8-30fe9ac53fb6

Awesome, thank you @umpox !


Release tracking

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Minor Changes

#798 af335d37 Thanks @joshfarrant! - ⚠ Breaking change: Removed all Card-icon-background/color tokens (eg --brand-Card-icon-background-blue, --brand-Card-icon-color-orange)

<EMAIL_ADDRESS>Minor Changes

#811 6331ae61 Thanks @rezrah! - River and SectionIntro link colors now default to blue (accent) for consistency with Card, Pillar and similar components that feature blue links.
:warning: This is a visual breaking change. Please manually review all usages of River and SectionIntro to ensure there is sufficient contrast with the background color.

Patch Changes

#805 2928995b Thanks @rezrah! - Disabled all transitions and auto-staggering when reduced-motion user preference is enabled

#809 bbb14ce9 Thanks @rezrah! - Updated Link underline to fill entire width

#798 af335d37 Thanks @joshfarrant! - - Fixed a bug where the Bento leadingVisual prop wouldn't honour the provided size.

Updated the Card.Icon internal implementation to use the new Icon component.

#810 774b91b0 Thanks @rezrah! - Added new background customization options to CTABanner
New props:

backgroundColor
backgroundImageSrc
backgroundImageSize
backgroundImagePosition

Also added variant prop to CTABanner.Description, to achieve higher contrast when using background images.
:link: See the documentation for more details and usage examples.

#805 2928995b Thanks @rezrah! - Removed negative margin from RiverStoryScroll when reduced-motion user preference is enabled

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Smoke test results

Breaking change: Removed all Card-icon-background/color tokens  🟢

x2 regressions observed in dotcom

Copilot Extensions

 Before  After

Will need Brand Eng to remediate. cc. @raytalks
Size discrepancy fixable by adding size="medium here

Copilot page

 Before  After

Will need Brand Eng to remediate. cc. @raytalks
Fixable by updating this line, which is using a deprecated CSS variable.
-   background-color: var(--brand-Card-icon-background-purple);
+   background-color: var(--base-color-scale-purple-8);

Updated Link underline to fill entire width 🟢

Updated the Card.Icon internal implementation to use the new Icon component  🟢

Disabled all transitions and auto-staggering when reduced-motion user preference is enabled  🟢

Added new background customization options to CTABanner 🔴
Blocking regression on all CTA banner instances where a default color isn't specified

Fallback value is incorrect. Fix is to update it to --brand-CTABanner-bgColor from --brand-CTABanner-background-color.
Will require a hotfix ⚠

Release testing status: Not ready for release 🔴

Smoke test update:

Added new background customization options to CTABanner 🟢
Regression fixed in hotfix #814


GitHub "Label" not available for Handlebars templates?

When I run auto-changelog --template json --output changelog-data.json as suggested to see all the information I can use in my Handlebars template, I note that the GitHub Labels are not available. I use those to categories PRs that I wish to subtitle and group in a changelog (like gren).  Adding and removing Labels in GitHub is an easy enough way to retroactively document what the PRs were for. Am I missing something, or is this not supported?

The tool uses information from the git CLI. It supports several version control tools and is not specific to GitHub. There is an idea to enrich the data with external sources but this is not happening any time soon.


Could README instruction have more details?

Dear Mermaid Team,
Thank you for the wonderful editor in advance, I love to use mermaid online editor.
My issue is a novice problem.
Sometimes I have no internet connection and cannot use it, in a previous issue #217
https://github.com/knsv/mermaid/issues/217
I saw one of the solutions is run it locally, but I failed in the very first step yarn install with an error msg: "-bash: yarn: command not found".
I am a non-programmer and have little knowledge about what's going on,
after I asked my friend, I tried:  npm install yarn and run yarn install again with +<EMAIL_ADDRESS>but still saw the same error msg.
Then I tried brew install yarn and finally succeeded with yarn install v1.17.0
I think it would be kind if README pointed out you have to install yarn before type yarn install and it would be kinder if add how to install yarn section.
How do you think about it?  Thank you so much.

For anyone who stumbles on this issue, the project has been moved and the new one includes a docker image you can spin up locally to get an offline editor.
See: https://github.com/mermaid-js/mermaid-live-editor#run-published-image

Thank you for replying!


Font-awesome icons no longer loading in v4_0_45

On our web application, we have been using the font-awesome library packaged with the GCWeb CDTS v4.0.45 for our icon sets. These worked perfectly fine up until about a month ago, but are now no longer loaded by the CDTS. Upon downgrading to v.4.0.44, the icons come back and work as intended.
CDTS scripts initially used (font-awesome library not loading):
<script src="https://www.canada.ca/etc/designs/canada/cdts/gcweb/rn/cdts/compiled/soyutils.js"></script>
<script src="https://www.canada.ca/etc/designs/canada/cdts/gcweb/rn/cdts/compiled/wet-en.js"></script>

CDTS scripts I tested to specify v4.0.45 (font-awesome library not loading):
<script src="https://www.canada.ca/etc/designs/canada/cdts/gcweb/v4_0_44/cdts/compiled/soyutils.js"></script>
<script src="https://www.canada.ca/etc/designs/canada/cdts/gcweb/v4_0_44/cdts/compiled/wet-en.js"></script>
<script src="https://www.canada.ca/etc/designs/canada/cdts/gcweb/v4_0_44/cdts/compiled/plugins-en.js"></script>

CDTS scripts I tested for v4.0.44 (font-awesome library loads correctly):
<script src="https://www.canada.ca/etc/designs/canada/cdts/gcweb/v4_0_44/cdts/compiled/soyutils.js"></script>
<script src="https://www.canada.ca/etc/designs/canada/cdts/gcweb/v4_0_44/cdts/compiled/wet-en.js"></script>
<script src="https://www.canada.ca/etc/designs/canada/cdts/gcweb/v4_0_44/cdts/compiled/plugins-en.js"></script>

Example of v4.0.44 with font-awesome working as intended:

Example of v4.0.45 without font-awesome working:

It would be nice to not have to downgrade our CDTS version, however, any suggested solutions would be appreciated!
Cheers, and thank you kindly.

Yes, fontawesome was intentionally removed as part of the 4.0.45 release (mentioned in CHANGELOG - the .45 release was done in May but only recently was made the /rn/ version).  Main reason for the removal was that CDTS itself does not use fontawesome for anything and yet was pulling it in many, many applications that don't use it either (we weren't even aware of any application that actually used these fonts until now).  Secondary reason is that as an external dependency it was causing problems for an application behind a network with hardened security.
We currently have no plan to bring it back unless there is important demand for it, but you can easily add it back to your app by including the following in your page's <head>:
<link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.8.1/css/all.css" integrity="sha384-50oBUHEmvpQ+1lW4y57PTFmhCaXp0ML5d60M1M7uH2+nqUivzIebhndOJK28anvf" crossorigin="anonymous">

(this is the only fontawesome-related line we removed from CDTS' source code)
Sorry for the inconvenience.  Let us know if this solution works for you.


Lazy boxes, Multiple boxes, Watch grammatically?

Question
Hello there, what is the equivalent to WatchBoxBuilder, in order to get the current values and updates events?
I am planing to use flutter_bloc as for managing state, and wish to get the data and updates throught the bloc events and state. i tried calling watch() method on a box on my bloc but that would only get the activities plus values of it, but not the already stored values.
second question, my app would store messages in many other boxes, will that be an issue on ram? say 10 boxes, with each 1000 entry?
third question, my understanding after reading docs, is that if i have many boxes and do not want to put more data into memory, i should use lazy boxes instead, but i got the error, [ERROR:flutter/lib/ui/ui_dart_state.cc(148)] Unhandled Exception: HiveError: Lazy boxes do not support type arguments.
i could open the box without specifying type, but that will not allow me to use WatchBoxBuilder, so in order to get the best of boxes and mainataine clean code and performance what should i do please?
Version

Platform: android.
Flutter version: latest
Hive version: latest

I am planing to use flutter_bloc as for managing state, and wish to get the data and updates throught the bloc events and state. i tried calling watch() method on a box on my bloc but that would only get the activities plus values of it, but not the already stored values.

I think this is related to #20. I'm not sure if it is something Hive needs to provide because it is very bloc specific and you can do it easily yourself using the box.watch() method.

second question, my app would store messages in many other boxes, will that be an issue on ram? say 10 boxes, with each 1000 entry?

This depends on the size of your messages. I would say it is still okay to have this amount of messages in RAM but it should not be much more. Consider using lazy boxes as an alternative.

i could open the box without specifying type, but that will not allow me to use WatchBoxBuilder, so in order to get the best of boxes and mainataine clean code and performance what should i do please?

Yes, like the error says, you cannot use type arguments for lazy boxes. This has nothing to do with the WatchBoxBuilder and it should work as always.

That issue is not related. What i mean is to open a box lazley, with my
model passed on, and have watchBoxBuilder for UI.
In case of not being able to use WatchBoxBuilder with lazy mode , i still
nèd a way to get box values and updates and pass them from my bloc, in this
case, with lazy box i did not know how to fetch its values without passing
my model, because i have to do some query like where on it.
For the second part my model is 5 String objects, max size of 255 chars, so
255×5 per box, x 10 boxes max.
On Tue, Nov 5, 2019, 01:54 Simon Leier<EMAIL_ADDRESS>wrote:

I am planing to use flutter_bloc as for managing state, and wish to get
the data and updates throught the bloc events and state. i tried calling
watch() method on a box on my bloc but that would only get the activities
plus values of it, but not the already stored values.
I think this is related to #20 https://github.com/hivedb/hive/issues/20.
I'm not sure if it is something Hive needs to provide because it is very
bloc specific and you can do it easily yourself using the box.watch()
method.
second question, my app would store messages in many other boxes, will
that be an issue on ram? say 10 boxes, with each 1000 entry?
This depends on the size of your messages. I would say it is still okay to
have this amount of messages in RAM but it should not be much more.
Consider using lazy boxes as an alternative.
i could open the box without specifying type, but that will not allow me
to use WatchBoxBuilder, so in order to get the best of boxes and mainataine
clean code and performance what should i do please?
Yes, like the error says, you cannot use type arguments for lazy boxes.
This has nothing to do with the WatchBoxBuilder and it should work as
always.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hivedb/hive/issues/115?email_source=notifications&email_token=AE2QCN7S7ESNZMFMTJAMNPTQSCRZHA5CNFSM4JIVEAQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDA76KQ#issuecomment-549584682,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE2QCN5BSXTKE52N2UT74ODQSCRZHANCNFSM4JIVEAQQ
.

WatchBoxBuilder has been deprecated. You can use box.listenable() or create an extension method which fits your needs.


Error while finishing compilation (linking process)

When you tries to compile it in raspberry pi 4 with raspbian buster it doesn't work (fail in linking process).
Linking CXX executable ../emulationstation
/usr/bin/ld: /opt/vc/lib/libvchiq_arm.so: undefined reference to symbol 'vcos_generic_mem_free'
/usr/bin/ld: //opt/vc/lib/libvcos.so: error al añadir símbolos: DSO faltante desde línea de orden
collect2: error: ld returned 1 exit status
make[2]: *** [es-app/CMakeFiles/emulationstation.dir/build.make:1092: emulationstation] Error 1
make[1]: *** [CMakeFiles/Makefile2:358: es-app/CMakeFiles/emulationstation.dir/all] Error 2
make: *** [Makefile:152: all] Error 2
But retropie-emulationstation compiles and works fine.
Probably this error could happen by "Makefile ld" bad configuration?
Also I compile in ArchLinux and compile and works fine, this error just appear in RP4 with 4.19.x and  5.4.x kernels

Greetings!

it just lacks the rpi libs at edition linking.
just use cmake . -DRPI or something like it and it will work.

it just lacks the rpi libs at edition linking.
just use cmake . -DRPI or something like it and it will work.

Thanks, I'm agree with you but... doesn't work :'(.
Could you please add this libraries to makefile? or... I can fork and do it if you specify exactly the library you're using.
Greetings!

Ok, I've found what parameter are you refering:
-DRPI4=1
with it in cmake process just linking continue and finish
but now there is some error that has been happening in Retropie emulationstation just before a few weeks:

After the last release in 1-2 may this error dissapears.
Have you take into account his fixes?
Greetings

With my Raspberry Pi3 I'm having the same issues with linking and the cmake . -DRPI4=1 flag doesn't work either.
Any updates?

Probably obsolete


EM example problem builder checks not all allowed pixels

Pixel (7, 7) is coherent to pixels of a rectangle, which starts at (7, 7) and ends at (10, 10).
Though, this should depend on the input pixel.
-     *    -
-  (i, j)  +
-     +    +

If we come down (first component increments), coherent for (i, j) are pixels of square (i, j - horizontal_offset), (i + vertical_offset, j + horizontal_offset).
-     *    -
+  (i, j)  +
+ (i+1, j) +

If we come right (second component increments), coherent for (i, j) are pixels of square (i - vertical_offset, j), (i + vertical_offset, j + horizontal_offset).
-    +      +
* (i, j) (i, j+1)
-    +      +

Fixed in https://github.com/char-lie/patterns_recognition/commit/12bf3e79bd50dee9d5fa60b1544fb9dd768e78e5


While custom marker adding using iconView it will hang map and memory high

    let marker = GMSMarker()

    // Creates a marker in the center of the map.
    marker.position = CLLocationCoordinate2D(latitude: trackList["lat"].doubleValue, longitude: trackList["lng"].doubleValue)
    marker.title = "Sydney"
    marker.snippet = "Australia"
    marker.map = viewGoogleMap

    marker.tracksViewChanges = false
    marker.tracksInfoWindowChanges = false

    let customInfoWindow = CustomIconView(frame: CGRect(x: 0, y: 0, width: 75, height: 75))
        customInfoWindow.imgUserPhoto.layer.masksToBounds = true
        customInfoWindow.imgUserPhoto.layer.borderWidth = 1.0
        customInfoWindow.imgUserPhoto.layer.borderColor = UIColor.green.cgColor
        customInfoWindow.imgUserPhoto.layer.cornerRadius = customInfoWindow.imgUserPhoto.frame.size.width / 2
        customInfoWindow.imgUserPhoto.image = UIImage(named: "sample")
        marker.iconView = customInfoWindow

I am displaying custom marker for google map implementation in swift. there is memory issue while using marker.iconView.
if i used (marker.icon) it will working fine.

You can try setting tracksViewChanges in the marker to false so the iconView is not redrawn on every frame as an optimization. You should then set it back to true if you need it redrawn.

Issue resolve


Unseal failing

Attempting to unseal a ski file gives an error:
$ ./kmyth-unseal -i out.ski -o out
kmyth-0.0.0 INFO - src/util/tpm2_config_tools.c(tpm2_init_connection:82) initialized connection to TPM 2.0 emulator
kmyth-0.0.0 ERROR - src/util/tpm2_kmyth_io.c(kmyth_getSkiBlock:929) unexpected delimiter ... exiting
kmyth-0.0.0 ERROR - src/util/tpm2_kmyth_io.c(tpm2_kmyth_read_ski_file:510) get PCR selection list error ... exiting
kmyth-0.0.0 ERROR - src/util/tpm2_kmyth_seal.c(tpm2_kmyth_unseal:402) error reading .ski file out.ski ... exiting
kmyth-0.0.0 ERROR - src/unseal/main.c(main:136) kmyth-unseal failed ... exiting

I haven't been able to re-create that error, but it looks like the delimiter for the "PCR Selection List" in the .ski file is not what is expected ("-----PCR SELECTION LIST-----\n"). Is there anything weird with the "Original Filename" block preceding it? Is out.ski clearly corrupted (e.g., kmyth-seal did not produce it correctly) or is something else going on?

I've done some more digging, it's caused by having a - in the original filename. We detect the start of the next ski block by looking for a -, so if there's one in the original filename it thinks that's where the next block starts. I'll give some thought to how I think we should handle it, but I'm open to suggestions too.

Ok, here's what I want to do, feel free to talk me out of it. I think we should re-do the file parsing to step between newlines (rather than stopping when it hits a -). Once it hits a newline it looks back to the character after the previous newline and checks if the string in between is the expected delimiter. If it is, process the ski block, if it isn't throw an error.
I think we can accomplish this fairly easily using one or two extra pointers to track positions in the contents array, but I also expect it will be tricky to get exactly right.

Turns out it could be done more simply than I originally thought.


-SQLiteAsync added support for ThenBy ThenByDescending

Added support to SQLiteAsync for ThenBy ThenByDescending

Cool. Does ..OrderBy(...).OrderBy(...) accomplish the same thing?

Very nice, thanks!


docs(readme): Update key features description

PTAL

LGTM, please update the git commit message according to the CI error info, i.e., change all string to lowercase


added deduplicate str lists example

1. Does this PR affect any open issues?(Y/N)

[ ] N
[x] Y

fix #165
Need reviews @Peefy

Thanks. LGTM!


Tag v0.2.1 and update CHANGELOG

So people can pull from here confidently ... working on a PR as we speak.
Currently the license agreement check fails.

Meh. Okay. Was hoping to get some stuff done before the next release but I see that it's taking too long... Open a PR, I'll merge it.

I don't think I can tag via PR anyway, and all I would do is edit the CHANGELOG to include everything change thus far (which I'm not sure I want to do not knowing the state of affairs ...)
Your call.  I've forked already so I'm cool with it either way.  Thanks for putting this together, BTW! :+1:


Bug: cannot create a new page by the shortcut key

Environment
Host

item
version

OS

GROWI
4.0.4

node.js
12.18.0

npm
6.14.4

Using Docker
yes

Using growi-docker-compose
yes

(Accessing https://{GROWI_HOST}/admin helps you to fill in above versions)
Client

item
version

OS
windows 10

browser
chrome 83

How to reproduce? (再現手順)

press c
click create

What happens?  (期待される動作)

create a new page

@hkato312 Thank you for your report.
This problem has fixed. Please wait the next release v4.0.5.


Add configuration options for board labels.

Original issue: https://github.com/julianandrews/sgf-parse/issues/17
It would be good to add an option to draw coordinate labels on all four sides of the board.
Actually, it would be good to generally support more coordinate options, so I should at least figure out what the CLI options will look like. Ideally it would be possible to specify:

Which of the four sides to draw coordinate labels on
Direction of the coordinates (for horizontal/vertical independently)

I think right now, the letters may be going reverse of what you'd expect

Maybe an option to specify the labels to use for horizontal/vertical labels

This way users could use numbers on both or letters, or could choose not to skip 'I'

This is going to require a bit of a refactor. If I remember right, there's a bit of a mess between the scaling logic and the labeling logic that doesn't make this easy.

Right now, I'm thinking this can be done with two command line options:
--label-sides:  Takes a string that's some subset of nesw, default nw that lets you specify which sides get labels
I'll need to think more on how to best handle the horizontal/vertical labels to use.

Side note - it looks as if the way I'm mapping coordinates to letters is the same thing OGS does ([qp] -> R4). So I'm going to keep that as the default, which saves me a breaking change =)

The --label-sides flag was definitely the more useful of the two issues here. I'm going to leave this bug open, because maybe someday I'll decide to fix it, but if you're wandering in from the internet and actually need the ability to change the labels, let me know and propose a command line argument format because I can't come up with a solution I think is great, and am not even sure I'd ever use it!

I'm closing this in favor of the more specific #17


React modal not content not rendered on single instance (Version 3.1.2)

I use react modal in my app and it usually works fine. The app is a widget that is placed on various different sites. Now I face an issue where the -Component is not rendered anymore. While toggling it still works as intended no matter what content I put into the  it does not appear. When checking variables I can see that the toggle actually works and there are some installations where the whole widget works as intended. I hope you can help me asking the right questions/looking in the right places to figure out the reason.
Here is my modal implementation:
<Modal
    className="questionnaire-component"
    isOpen={this.state.modalIsOpen}
    onRequestClose={() => this.setState({modalIsOpen: false})}
    style={ModalStyles}
    contentLabel="Questionnaire"
    onClick={this.closeModal}
>
    {this.state.loading ?

            <Loading type='balls' color='#3C3C3B'/>

        :

Render component

    }
</Modal>

The styles:
const ModalStyles = {
    overlay: {
        position: 'fixed',
        top: 0,
        left: 0,
        right: 0,
        bottom: 0,
        backgroundColor: 'rgba(255, 255, 255, 0.90)'
    },
    content: {
        position: 'absolute',
        top: 0,
        left: 0,
        right: 0,
        height: '100%',
        background: 'transparent',
        overflow: 'auto',
        WebkitOverflowScrolling: 'touch',
        outline: 'none'
    }
};

This might be unrelated but I also realised that tabbing through forms and close per click on backdrop do not work. I do not have any error statements (console or other). The app is build with webpack.

Hi @RT-TL, did you check if the component actually appears in the Dom tree?

hi diasbruno the  and all it contains does not appear but the ModalPortal is there.

Ok, I'll still look for errors on this example, but the best way to validate this issue is to make a reproducible example. We have a simple boilerplate on the issue template.

Here is the link https://codesandbox.io/s/mgwy6V6E. It's a bit old now, but it's simple to update.

Thanks a lot. I will try to reproduce and update as soon as I managed to do so. So far I have been unsuccessful. I currently suspect some interference with other scripts but the issue is strange for this context. Any hint where this might be coming from would be very helpful.

My only guess right now is that probably you have a condition like this.state.loading that is make it not render.

I still work on reproducing it in the sandbox but by now I know that the issue seems to appear in Chrome and Firefox, not in IE or Safari.

Any more information on this?

Sorry, not from my side. I could neither solve nor reproduce the issue.


define playlist types to simplify code

Party (time limit, autoplay next), Showcase (time limit, pause before next), Normal (full song, autoplay)
Feature songs allowed in Party and Showcase lists

closed by pull request #119


ci: add merge queue

How do you configure the default merging behavior of merge queues? Is it in settings? Is it possible to override commit messages?

merge message is decided upon merging


Updated README to include correct DockerHub link

Description
This PR fixes #47
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@fazer1929 thank you. Please see the instructions about DCO commit signing requirements in the Welcome message.
You can amend sign-off here - https://github.com/meshery/meshery-tanzu-sm/pull/48/checks?check_run_id=6013128720

Good work! If you haven't joined the Layer5 Community Slack, yet, I invite you to jump in.


Pr 10

Adds a toggle button to the author home page to allow users to switch between html/ md, maintains backwards compatibility with already downloaded author html files, and does some very small design cleanups.

Builds on top of #10


Question about static linking

Does it make sense to automatically set MSVC_RUNTIME_LIBRARY if chosen triplet is *-windows-static

set_property(TARGET maestro PROPERTY
  MSVC_RUNTIME_LIBRARY "MultiThreaded$<$<CONFIG:Debug>:Debug>")

Should vcpkg install show additional information about how to use in cmake if triplet is *-windows-static?

I think below update to message would be really helpful.
The package boost is compatible with built-in CMake targets:
+ Add `-DVCPKG_TARGET_TRIPLET=x64-windows-static` to your cmake invocation.
    find_package(Boost REQUIRED [COMPONENTS <libs>...])
    target_link_libraries(main PRIVATE Boost::boost Boost::<lib1> Boost::<lib2> ...)

Since vcpkg will automatically set the specified CRT linkage based on the triplet, the cmake configuration file generated by the port contains this information.
See triplet:
https://github.com/microsoft/vcpkg/blob/4a678aa329c0a6323d7334fdf3ad37d571600d27/triplets/x64-windows-static.cmake#L2
setting:
https://github.com/microsoft/vcpkg/blob/4a678aa329c0a6323d7334fdf3ad37d571600d27/scripts/toolchains/windows.cmake#L8-L14

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.


Problem with the build

Hi,
I'm trying to use this examples to look into Junction, but I can't build it.
is this sample still valid?
Did this:
git clone https://github.com/preshing/junction-sample.git
cd junction-sample/
cmake -G "Eclipse CDT4 - Unix Makefiles" -D CMAKE_BUILD_TYPE=Debug  .
cmake --build

Got this:
/home/rigazilla/git/junction-sample/Main.cpp: In function ‘void testMap()’:
/home/rigazilla/git/junction-sample/Main.cpp:14:11: error: ‘ConcurrentMap’ has no member named ‘insert’
     myMap.insert(14, new Foo);

Thank you!

The method insert has been rename in assign.
So seems to me that it's safe to just do do:
s/insert/assign

Yea, you're probably right, I missed that while renaming. Let me take a look.


Google Voice

https://twitter.com/michaelwilde/status/291621170816626688

Ref: Conversation #3791 / Jan

Ref: Conversation #4528 / Jan


bump dependencies

Overview: What does this pull request change?
Update pinned dependencies and as a first step, I want to see if the tests pass.
Motivation and Explanation: Why and how do your changes improve the library?
see #3241 – and in particular in my case, I want to use a newer networkx
Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

That's a familiar name; hey there @haraldschilly!
Seems like the cloup upgrade messes with the formatting of deprecated in the CLI test, nothing serious. I'm happy to merge this once the test is fixed. 👍

:wink: @behackl  … github is a small world :grinning:

cool, thx!


Responsive

Title and Issue number

Title :
Issue No. :
Code Stack :
Close #<issue_no>

Video (mandatory)

Checklist:

[ ] I have mentioned the issue number in my Pull Request.
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md if its a new page/tech stack
[ ] I have gone through the  contributing.md file before contributing

Additional context (Mandatory )
Are you contributing under any Open-source programme?

[ ] I'm a GSSOC-EXT contributor
[ ] I'm a HACKTOBERFEST contributor

@Kuldeepsinghrajpoot Resolve conflicts

error: invalid path '.github/workflows /auto-label.yml'
error: invalid path '.github/workflows /auto_labeler_on_pr.yml'
error: invalid path '.github/workflows /check-merge-conflicts.yml'
error: invalid path '.github/workflows /greetings.yml'
error: invalid path '.github/workflows /post-pr-thankyou.yml'
error: invalid path '.github/workflows /restrict_issues.yml'
When I run git pull, it shows an error. Additionally, I created a new file, but the PR (Pull Request) was not created. Also, git clone is not cloning the repository and shows a similar error. What should I do right now?

@Kuldeepsinghrajpoot do it again once!

sure it will work


[MTDSA-322] use scalafmt

Closing now until https://github.com/olafurpg/scalafmt/issues/278 is fixed.


Can multiple processes observe the same document change?

It seems by using the change feed processor library as suggested in the sample code, we cannot observe the same document change by multiple processes/clients.  Is there a way to do that?

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

ID: fdcc897a-d6df-3305-e9cb-01889a3c5d4f
Version Independent ID: 739a9fc7-3782-a860-ac6d-4194fd1ce2e8
Content: Working with the change feed support in Azure Cosmos DB
Content Source: articles/cosmos-db/change-feed.md
Service: cosmos-db
GitHub Login: @rafats
Microsoft Alias: rafats

@schenmsft But I don't think it is the exact use case you are seeking, as there is only one consumer per partition key. You are looking for multiple consumers per partition key. I suggest you make a recommendation to the Azure Cosmos DB User Voice.

The change feed is available for each partition key range within the document collection, and thus can be distributed across one or more consumers for parallel processing as shown in the following image.

@schenmsft We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

A alternative ways is that you can connect an Eventhub to the cosmosdb change feed, and eventhub uses 'consumer group' to support multiple consumers


[trade-secret] connecting to peer is unreliable

When using trade-secret it can easily fail with FailedToConnectToPeer
Retrying seems to make it work so it could just retry on connection failure

seems like it's more reliable now


Fix/hostdockerinternal

Include Secvisogram in the development / test environment

[ ] Logout with Secvisogram doesn't working. #99 give a hint on the problem.

This commit also fixes #99.


discussion of plugin validation and what lives in napari vs the plugin engine

following on from  https://github.com/napari/napari-plugin-engine/pull/15#issue-561931730 by @ziyangczi

we will allow people to run these checks in their CI/CD after the deployment step to check it is discoverable by napari

I want to address the idea of doing validation/ testing without depending on napari.
If the use case is primarily CI/ CD then I don't see being forced to depend on napari to do the test isn't that big a deal. I see a big difference between a plugin being forced to depend on napari to exist and be distributed - we don't want that - but I don't mind having to force someone to add napari to a testing environment to check that their plugin works with napari, that seems ok. In napari itself we have many packages in our testing environment that we don't have in our main environment, and napari will always be present in the environment when the package is being used as a napari plugin. We've also gone to great lengths to get napari to install well without qt, and possibly one day be truly headless without vispy too.
Even for people developing locally if they want to test napari plugin compatibility, it's not that unreasonable to force them to have napari installed for testing, as if they care about validation as a napari plugin they are probably able to install napari.
With respect to #15 I can see good reason why the plugin discovery code should live in the plugin engine and so am happy for that PR and a gradual migration, and we should probably try and test as much as possible without relying on napari, but there will be some things that won't make sense to duplicate.
For example right now the actual plugin interface (the hook specifications) are defined inside napari and I don't think we have any plans to move them in here anytime soon, though i could actually see one day how it might be nice as we could have our plugin interface versioned and released on a different timescale than napari itself. Coordinating the development across the repos would be a pain, but it might yield nice benefits long term.
cc @tlambert03 @jni

With respect to #15 I can see good reason why the plugin discovery code should live in the plugin engine

... sort of.  but the plugin engine doesn't use this code (and probably won't ever).  This is pretty much only for "internet" searching of plugins, which we do in the napari plugin gui to facilitate plugin installation.

If the use case is primarily CI/ CD then I don't see being forced to depend on napari to do the test isn't that big a deal.

definitely agree with this

check it is discoverable by napari

We could basically test this for them just by grepping "Framework :: napari" in their setup.py or setup.cfg.  This feels like one of those things where you don't need to duplicate the tests of your "dependencies", and in this case PyPI is the dependency, and I trust that if someone puts the framework Framework :: napari classifier in there, then PyPI probably will probably get the job done.

With respect to #15 I can see good reason why the plugin discovery code should live in the plugin engine

... sort of.  but the plugin engine doesn't use this code (and probably won't ever).  This is pretty much only for "internet" searching of plugins, which we do in the napari plugin gui to facilitate plugin installation.

If the use case is primarily CI/ CD then I don't see being forced to depend on napari to do the test isn't that big a deal.

definitely agree with this

check it is discoverable by napari

We could basically test this for them just by grepping "Framework :: napari" in their setup.py or setup.cfg.  This feels like one of those things where you don't need to duplicate the tests of your "dependencies", and in this case PyPI is the dependency, and I trust that if someone puts the framework Framework :: napari classifier in there, then PyPI probably will probably get the job done.

adding what I am hearing from the plugin developers, I agree that the benefit of excluding napari as a dependency in CI/CD may be negligible, overall the benefit comes from allowing developers to have a different development cycle aside from napari roadmap, and save them from the trouble of knowing what is happening in napari all the time. I believe there will be a point where we feel more comfortable having all the specifications living in here than the core (I don't think now is the time), and at that point, the code would mostly freeze in the plugin engine, so that core and plugins can go separate ways in their own direction without having to worry too much about each other.
on the pypi classifier, I agree that the best-case scenario only needs a simple test, these tools would be necessary for those outliers, we need to be ready to support more general matching than just pypi classifier, be it existing distributions that have policy/sanitary issue not accomodating classifier, or even some of the plugins in the future may not even be able to distribute via pypi for whatever reason. I believe there is value in giving people these tools so they know exactly what is expected, and we can evolve our discovery method when we need to. (Plus we can grow the number of things that can be pre-checked as well, for example the dependency conflict check is a big win)

adding what I am hearing from the plugin developers, I agree that the benefit of excluding napari as a dependency in CI/CD may be negligible, overall the benefit comes from allowing developers to have a different development cycle aside from napari roadmap, and save them from the trouble of knowing what is happening in napari all the time. I believe there will be a point where we feel more comfortable having all the specifications living in here than the core (I don't think now is the time), and at that point, the code would mostly freeze in the plugin engine, so that core and plugins can go separate ways in their own direction without having to worry too much about each other.
on the pypi classifier, I agree that the best-case scenario only needs a simple test, these tools would be necessary for those outliers, we need to be ready to support more general matching than just pypi classifier, be it existing distributions that have policy/sanitary issue not accomodating classifier, or even some of the plugins in the future may not even be able to distribute via pypi for whatever reason. I believe there is value in giving people these tools so they know exactly what is expected, and we can evolve our discovery method when we need to. (Plus we can grow the number of things that can be pre-checked as well, for example the dependency conflict check is a big win)

or even some of the plugins in the future may not even be able to distribute via pypi for whatever reason

as I mentioned in the google doc... while it is certainly possible for someone to distribute a package outside of PyPI, it is unclear if/when we will be able to install it inside the bundle using the GUI installer (i.e. they're basically on their own at that point). so these hypotheticals are all well and good, but it feels to me like we're talking about moving and modifying actively used code here, for things that feel at best a long way off.

or even some of the plugins in the future may not even be able to distribute via pypi for whatever reason

as I mentioned in the google doc... while it is certainly possible for someone to distribute a package outside of PyPI, it is unclear if/when we will be able to install it inside the bundle using the GUI installer (i.e. they're basically on their own at that point). so these hypotheticals are all well and good, but it feels to me like we're talking about moving and modifying actively used code here, for things that feel at best a long way off.

We could basically test this for them just by grepping "Framework :: napari" and "entry_points = 'napari.plugin'" in their setup.py or setup.cfg. This feels like one of those things where you don't need to duplicate the tests of your "dependencies", and in this case PyPI is the dependency, and I trust that if someone puts the framework Framework :: napari classifier in there, then PyPI probably will probably get the job done.

I love this idea, it seems very minimal and immediately useful. I know that my napari-console repo would pass as I manually added it, but my napari-animation repo would fail because I havn't. It's also the sort of test where a very clear error message could be given - please add "Framework :: napari" and/ or the entry point.
Maybe an idea for a first minimal working validation service would be a github action that simply looks to see if the framework classifier is there and the entry point is there. If you got that working @ziyangczi we could then build out more from there.

We could basically test this for them just by grepping "Framework :: napari" and "entry_points = 'napari.plugin'" in their setup.py or setup.cfg. This feels like one of those things where you don't need to duplicate the tests of your "dependencies", and in this case PyPI is the dependency, and I trust that if someone puts the framework Framework :: napari classifier in there, then PyPI probably will probably get the job done.

I love this idea, it seems very minimal and immediately useful. I know that my napari-console repo would pass as I manually added it, but my napari-animation repo would fail because I havn't. It's also the sort of test where a very clear error message could be given - please add "Framework :: napari" and/ or the entry point.
Maybe an idea for a first minimal working validation service would be a github action that simply looks to see if the framework classifier is there and the entry point is there. If you got that working @ziyangczi we could then build out more from there.

+1.  I think GitHub actions will be super useful

+1.  I think GitHub actions will be super useful


Nag for deprecation of BuildFileOption and SettingsFileOption

This should happen in 8.1 with a message that says it will become an error in 9.0.
Deprecated in 7.1 by

https://github.com/gradle/gradle/pull/16713

Deprecation in 7.1 already nags, this issue is moot, closing.


Why is this code checking the "Path" instead of the request for proof?

https://github.com/informalsystems/ibc-rs/blob/9545ccddfad78582532f1eb13f7ac201ccdac72f/relayer/relay/src/query.rs#L68-L72
This code survived a few refactors and we should implement it - or at least make it easier to understand.
As far as I understand, if the request came in with prove=true, it would be nice, if we checked that proof. But this code seems to suggest, that based on the Path there's an indication if the response should be checked.
I guess this must relate to the provableStore idea in the ICS. But as far as I'm aware, all request Paths are going to come from store/ibc/key. Or maybe I'm missing something.
Is it possible that the code is just slightly wrong and it should check the data field to see if the request contains something that's in the provableStore? (In that case I know how to deal with that.)

Here's my assumption for now:

we're going to assume we query the IBC store
a path is provable if it's in the provableStore, as indicated in ICS-024.

Just a note.

// Data that is not from trusted node or subspace query needs verification.

So obviously if we trust the node/ we set prove=false we don't verify.
The other type, subspace query, is when we query a whole subspace, which I mentioned here: https://github.com/informalsystems/ibc-rs/issues/128#issuecomment-659094702
ie. if we use a path like store/ibc/subspace we get all the keys prefixed with whatever we pass in data
I believe the idea re proofs here is that if you get a full subspace (ie. a complete merkle sub-tree), you don't need to worry about proofs, because you have all the data to construct them yourself. But you'd still need some proof to verify that the root of your subtree is in the larger tree ...


This project is dead please open issues with a fork

I periodically repost this but the only author/admin in this org has passed away one (not the only) fork is here https://github.com/pysnmp/pysnmp

You might consider closing old issues for the same purpose.
This repo is not going to die any sooner, as the original PyPI packages are still active and pointing here. It's going to take long and the package ownership request is blocked unreasonably at this moment.

#429 contains more details.


Consistent initial conditions

@tinosulzer did you need to implement a consistent initial conditions finder (initial newton solve on the algebraic equations) for lead-acid? For DFN the solver raises the error:
[IDA ERROR]  IDASolve
  At t = 0 and h = 9.53674e-11, the error test failed repeatedly or with |h| = hmin.

yes, in dae_solver.py


ZipOne on coproducts throws runtime exceptions in most cases

Coproduct ops include a ZipOne typeclass, witnessing that zipping two coproducts is the coproduct of tuples of elements taken pairwise, e.g.
ZipOne[Int :+: String :+CNil, Boolean :+: Double :+: CNil]
res0: ZipOne {type Out = (Int, Boolean) :+: (String, Double) :+: CNil

However, this evidence is clearly false, as you can't guarantee that you'll always have both elements when you zip. Matter of fact, it only compiles due to the use of  Option#get on the Coproduct head.
As a result, if you pass in anything but two Inl, it throws an exception.
Is this intended behaviour? Imho this op should either be removed, or changed to return a more meaningful type, i.e. a Coproduct of cats Ior. WDYT?

Oh! That's definitely not right!
A coproduct ZipOne can definitely be defined, analogous to the hlist ZipOne, but this very definitely isn't it. I think that it was probably intended as a step in the direction of a coproduct Transpose, as was the case with hlist ZipOne (for generalized products zip == unzip == transpose), which misfired.
I think removing it is probably the best bet, with bonus marks for actually adding coproduct transpose ;-)

I'll do a quick PR to remove it (and add transpose to my never-ending todo list ;))


optimize startup time

this work refactors the code a bit in order to optimize startup time. Nick Mitchell 7:40 AM
i think i’ve managed to shave about 125-150ms off startup time (about a 30-40% reduction?). this was mostly done for my own edification, so i can understand more deeply the bottlenecks (for future discussions, in case people are hesitant about popping up a window; but also for resource-limited proxy servers).
we could probably shave off another 20-30ms, but i think it’s not worth the effort right now.

some of the overhead is currently unavoidable, due to the implementation of the nodejs require mechanism. this part here took 8.3ms. it’s all just filesystem operations. nodejs seems to be highly synchronous w.r.t. the filesystem, at least in its require implementation.


[POS] Block rejected by peers

If at least one peer does not accept our new block in 100 seconds, we lost 100 seconds of mining, then we raise exception and start over. This should be optimized.

Maybe however 100 seconds should not happen really, it means something went wrong. But lets look at what x is doing. I'll find the code.

Regardless of what X is doing, I'd like to ask why are we waiting at all? If we continue staking from very next second, what could go wrong? We could find another block and present it to the network. Now provided that the first would be rejected, the second might also be rejected.
And the question is whether that leads to banning our node or not. If not, we will eventually get the best chain from our peers, or we will make them believe ours is best.
So in this issue I'm looking for answering

will presentation of wrong chain block lead to banning the node?
how the best chain is recognized? Is it like in POW - i.e. the chain with most work on it (i.e. sum of met difficulty targets)?

There are several banning points, if its a consensus reason the ban, I believe, is for the lifetime of the banning node (i.e. a restart is required).
Yeah its same as POW, there is a target and a block with more work (stake) is selected.
Limits of a reorg is checkpoint, but there might also be a stop limit( if a Size > N reorg was detected stop processing and just notify the user to delete the db).

New data coming - if one of the node's peers is in IBD, it is total disaster, because obviously that peer does not have its tip set to the block we just mined, so in such a case all our blocks are considered as "rejected by peers" because of this one node that is in IBD.

Ahhh well that is certainly a bug, I'd even say the whole reason I added the wait for peers to reply is just when testing POS on the c# node perhaps we may want to remove that check all together.

 [POS] Block rejected by peers

Hi guys, just to confirm what we want to do here. Try getting rid of the following code and see what happens? https://github.com/stratisproject/StratisBitcoinFullNode/blob/master/Stratis.Bitcoin.Features.Miner/PosMinting.cs#L405-L435

Yes, I think exactly those lines should be removed and it will do no harm because there is nothing useful for us anymore.

Sounds good. I might have to get you to test as I don't think I'm set up to POS stake.

We definitely need more ppl testing POS, so if you don't have it, just ask :) First what you need is testnet coins, ask @dangershony for those. You obviously need a wallet that the coins will be sent to, so start with that - for that you might appreciate installing Breeze wallet.

Ok - yeah I would like to get it working so I can see how it works.


dts/st,stm32-usb: Add use-prop-name to disconnect-gpios

Add use-prop-name to disconnect-gpios property in st,stm32-usb
yaml, in order to generate friendly name for the definitions.
Signed-off-by: Yannis Damigos<EMAIL_ADDRESS>

Codecov Report

Merging #7535 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7535      +/-   ##
==========================================
+ Coverage   55.25%   55.25%   +<.01%
==========================================
  Files         467      467
  Lines       51638    51638
  Branches     9887     9887
==========================================
+ Hits        28531    28532       +1
+ Misses      19198    19197       -1
  Partials     3909     3909

Impacted Files
Coverage Δ

lib/posix/pthread.c
69.84% <0%> (+0.5%)
:arrow_up:

Continue to review full report at Codecov.

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


Release 30.12.2021

Update versions and changelogs

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: alexworker23:x: github-actions[bot]You have signed the CLA already but the status is still pending? Let us recheck it.


improve unit test coverage in "Core" namespace

Following classes need improvements in unit test coverage.

Accumulator
Broadcast
SparkContext
RDD
StatusTracker

See code coverage numbers at https://codecov.io/github/Microsoft/SparkCLR/csharp/Adapter/Microsoft.Spark.CSharp/Core

Now the overall test coverage in Core namespace has approached 83.53%, close this issue for now.
https://codecov.io/github/Microsoft/SparkCLR/csharp/Adapter/Microsoft.Spark.CSharp?ref=9be16a5869b9c9416732781045df8b08461a2dcc

Great job. Thanks @tawan0109


RichTextBlock: disableLastBottomSpacing for PageContentRichTextBlock

We decided to remove the margins top/bottom from the Page Content Blocks. We try the "do it yourself" way and give to content creators freedom wich spacing they want to use.

Didn't we want the RichTextBlock to be an exception?
Because you would want the normal paragraph-spacing between this block and e.g. a Button 🤔

Didn't we want the RichTextBlock to be an exception? Because you would want the normal paragraph-spacing between this block and e.g. a Button 🤔

It would not be consistent this way, i think. What space would be after the button, when after the button another RichTextBlock would be placed there is also no paragraph-spacing.


settings doesn't show up on android 6.0 devices

first off I want to say major kudos for making this launcher open source! when I run it on my android tablet it does not show the settings icon when you hold down on the home screen my tablet is running android 6.0.1 I look forward to seeing this launcher grow!

Please attach screenshot

See the hassettings method and where it Is used in launcher.java you will understand why it is not showing.
In launcher3 it only had allow rotation setting so it hides the button who don't need allow rotation

@YAJATapps  You mean this:
    protected boolean hasSettings() {         if (mLauncherCallbacks != null) {             return mLauncherCallbacks.hasSettings();         } else {             // On devices with a locked orientation, we will at least have the allow rotation             // setting.             return !getResources().getBoolean(R.bool.allow_rotation);         }     }
it seems correct...

I mean usage
    // Bind settings actions
    View settingsButton = findViewById(R.id.settings_button);
    boolean hasSettings = hasSettings();
    if (hasSettings) {
        settingsButton.setOnClickListener(new OnClickListener() {
            @Override
            public void onClick(View view) {
                if (!mWorkspace.isSwitchingState()) {
                    onClickSettingsButton(view);
                }
            }
        });
        settingsButton.setOnLongClickListener(performClickOnLongClick);
        settingsButton.setOnTouchListener(getHapticFeedbackTouchListener());
    } else {
        settingsButton.setVisibility(View.GONE);
    }

Here in last second line you can see if has settings is not true then the button visibility is gone

Ah thanks sir! I will fix

sorry for the late reply do you still want me to attach a screenshot?
Please let me know :)

No thanks!

Fixed, next update 0.1.0 Alpha 54.. probably this evening!


Add docs for in-place upgrades

Issue #, if available:
Description of changes:
Add docs for in-place upgrades
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/cherrypick release-0.19

/approve


[Question] BartDecoderOp

I'm trying to use BartDecoder on its own and I'm getting a segfault.
gdb says it's on this line, the first time we try to access elements of decoder_layer_weights.
gbd also says decoder_layer_weights's elements are all null pointers, so they haven't been initialized, so trying to access say decoder_layer_weights->self_attn_layernorm_weights is impossible.
I looked at BartDecodingOp and it seems to be initializing it in these 2 lines, am I right?
decoding_weights.resizeLayer(layer_num_);
decoding_weights.setWhisperStructureDiff(
        whisper_with_bias, mwhisper, use_gated_activation, position_embedding_type);

That said, shouldn't BartDecoder and other Decoders be usable on their own outside of Decoding?

BartDecoder can be used outside of Decoding, but BartDecoderOp of pytorch is not verified.

I'm putting a lot of hours into making th/BartDecoderOp, and after a few days forward is running!
However the outputs are incorrect and I was wondering if you have particular debugging strategies or tools that make the process less tedious.

We only debug by compare the output of tensor layer by layer.

Do you use cuda-gdb? Do you cudaMemcpy to print it from the c++? Do you just write to file?

You can use print_abs_mean in cuda_utils.h to print the mean of a tensor, which is simpler to check where the error happen.
Other functions of cuda_utils.h can also save the tensor into file when you want to compare in detail.

I managed to get it to run, but comparing with a staack of huggingface decoder layers, the DecoderOp is slower :(

I managed to get it to run, but comparing with a stack of huggingface decoder layers, the DecoderOp is 1.04x of the speed :(