Support type predicate "asserts" with no "is"

Supports parsing code that looks like the following:
class Test {
    test(): asserts this { // apparently valid typescript code...
    }
}

function assert(condition: any, msg?: string): asserts condition {
  if (!condition) {
    throw new Error(msg);
  }
}

https://ts-ast-viewer.com/#code/MYGwhgzhAEAqCmEAu0DeAoaXpMUgFAJQBc0kE8ATkjEgBYCWMG20Avuh+gGYCuAdsCQMA9vzJQqBYGIAmDYWNJh+ATwA00ALYQA5gH5SySg366SEitRgz+8xeJbQG3aPgCEt+6P6E0mbHpKEQB3aH54MIBRSmDKfB1zAG4AjjYgA
https://www.typescriptlang.org/play/?ssl=1&ssc=1&pln=10&pc=2#code/MYGwhgzhAEAqCmEAu0DeBYAUNH0mKQAoBKALmkgngCckYkALASxg21wF8svMsAzAK4A7YEiYB7IRSg0iwSQBMmYyeTBCAngBpoAWwgBzAPzlk1JkINlpVWjHlClKqWxxM+0QgEIHTiUOI0LFw8BmpxAHdoIXgogFFqcOpCfSsAbmDoHg4gA

ThNk you for the pr!
Can you run cergo fmt --all ?

Hmmm... works on my machine. Seems like there's some version mismatch on the CI.

@dsherret  Oh.. you are right.

I've published a new version.

Exciting!! Thanks @kdy1!


Parser bug while typing Vector constructor referencing another vector component

Godot version
4.0.beta4
System information
macOS 12.6.1
Issue description
While harmless I've run into a parser bug error I can reproduce in the code editor: Every time I type a specific code pattern I get this error in the console:
"Parser bug (please report): Trying to check compatibility of unset value type"
It happens as I type and doesn't block anything
Steps to reproduce
Basically it seems to affect all Vector constructors (like Vector2, Vector3, Vector2i etc) and happens if you start typing a constructor, referencing in the first component a component of another Vector.
For example:
var vectorA:Vector2
var vectorB:Vector2
vectorB = Vector2(vectorA.x

Note that the last row is unfinished, so that will give you another error if you don't finish it. The point is that it's at this point in typing the Parser error is triggered
Minimal reproduction project

Open a new script file
in the _ready function type the following:

var vectorA:Vector2
var vectorB:Vector2
vectorB = Vector2(vectorA.x

I get the same error using other vector types as well, and you can probably get them for other cases as well

Related to https://github.com/godotengine/godot/issues/44375.

Tested and I'm no longer getting this parser error in 4.0 beta 10. The related issue is also closed so I'm assuming this is fixed and I'm closing this issue.

It seems I was unfortunately a bit hasty closing this, after testing again I was still able to get the same error as described above in the Output log.

Looks like this is fixed in 4.0.stable, closing this


Tye on Podman with Postgres couldn't inject environment variables

Describe the bug
With Podman, when we run the Postgres container (postgres:12-alpine), the container can start, but down immediately due to environment variables couldn't inject into -e param when run on tye. When checked a logs then I found
[postgres_1c29ada2-8]: docker run -d -e "PORT=5432" -e "PROXY_PORT=5432:5432" -e "POSTGRES_USER=myuser" -e "POSTGRES_PASSWORD=P@ssw0rd" -e "POSTGRES_DB=mydb" -e "CONNECTIONSTRINGS__POSTGRES=Server=<IP_ADDRESS>;Port=5432;User Id=myuser;Password=P@ssw0rd;" -e "APP_INSTANCE=postgres_1c29ada2-8" -e "CONTAINER_HOST=<IP_ADDRESS>" -p 5432:5432 --name postgres_1c29ada2-8 --restart=unless-stopped postgres:12-alpine
[postgres_1c29ada2-8]: 66a072b3f81ae09f20154ab572bfbf579937613f2f78827fa12da36f7bd6fc58
[postgres_1c29ada2-8]: Error: Database is uninitialized and superuser password is not specified.
[postgres_1c29ada2-8]: You must specify POSTGRES_PASSWORD to a non-empty value for the
[postgres_1c29ada2-8]: superuser. For example, "-e POSTGRES_PASSWORD=password" on "docker run".
[postgres_1c29ada2-8]:
[postgres_1c29ada2-8]: You may also use "POSTGRES_HOST_AUTH_METHOD=trust" to allow all
[postgres_1c29ada2-8]: connections without a password. This is *not* recommended.
[postgres_1c29ada2-8]:
[postgres_1c29ada2-8]: See PostgreSQL documentation about "trust":
[postgres_1c29ada2-8]: https://www.postgresql.org/docs/current/auth-trust.html
.....

It should be a problem with tye when run the docker run -e <...>
When I copy the generated script by tye as following
podman run -d -e "PORT=5432" -e "PROXY_PORT=5432:5432" -e "POSTGRES_USER=myuser" -e "POSTGRES_PASSWORD=P@ssw0rd" -e "POSTGRES_DB=mydb" -e "CONNECTIONSTRINGS__POSTGRES=Server=<IP_ADDRESS>;Port=5432;User Id=myuser;Password=P@ssw0rd;" -e "APP_INSTANCE=postgres_1c29ada2-8" -e "CONTAINER_HOST=<IP_ADDRESS>" -p 5432:5432 --name postgres_1c29ada2-8 --restart=unless-stopped postgres:12-alpine

And run it right in the podman on wsl2 - Ubuntu host, then it can work correctly. I can remote login into Postgres db and manipulate schema and data in it
To Reproduce
Create tye.yaml
name: bff-auth
containerEngine: podman

services:

- name: postgres
  image: postgres:12-alpine
  env_file:
    - .env
  bindings:
    - port: 5432
      connectionString: Server=${host};Port=${port};User Id=${env:POSTGRES_USER};Password=${env:POSTGRES_PASSWORD};

And .env file
POSTGRES_USER=myuser
POSTGRES_PASSWORD=P@ssw0rd
POSTGRES_DB=mydb

Then run

tye run

Everything run well, but when we check logs of Postgres at http://localhost:8000, then we found the error logs as below
[postgres_1c29ada2-8]: docker run -d -e "PORT=5432" -e "PROXY_PORT=5432:5432" -e "POSTGRES_USER=myuser" -e "POSTGRES_PASSWORD=P@ssw0rd" -e "POSTGRES_DB=mydb" -e "CONNECTIONSTRINGS__POSTGRES=Server=<IP_ADDRESS>;Port=5432;User Id=myuser;Password=P@ssw0rd;" -e "APP_INSTANCE=postgres_1c29ada2-8" -e "CONTAINER_HOST=<IP_ADDRESS>" -p 5432:5432 --name postgres_1c29ada2-8 --restart=unless-stopped postgres:12-alpine
[postgres_1c29ada2-8]: 66a072b3f81ae09f20154ab572bfbf579937613f2f78827fa12da36f7bd6fc58
[postgres_1c29ada2-8]: Error: Database is uninitialized and superuser password is not specified.
[postgres_1c29ada2-8]: You must specify POSTGRES_PASSWORD to a non-empty value for the
[postgres_1c29ada2-8]: superuser. For example, "-e POSTGRES_PASSWORD=password" on "docker run".
[postgres_1c29ada2-8]:
[postgres_1c29ada2-8]: You may also use "POSTGRES_HOST_AUTH_METHOD=trust" to allow all
[postgres_1c29ada2-8]: connections without a password. This is *not* recommended.
[postgres_1c29ada2-8]:
[postgres_1c29ada2-8]: See PostgreSQL documentation about "trust":
[postgres_1c29ada2-8]: https://www.postgresql.org/docs/current/auth-trust.html
.....

Further technical details

Include the output of tye --version:  0.11.0-alpha.21629.1+c55a663e44390be98935d11375d4248738a376fd, and it also got this issue when run with tye 0.10.xxx
If possible rerun the command with -v debug and include the output:

❯ tye run -v debug
Loading Application Details...
Restoring and evaluating projects
Restore and project evaluation took: 256.116ms
Launching Tye Host...

[14:59:22 INF] Executing application from D:\github\bff-auth\tye.yaml
[14:59:22 INF] Dashboard running on http://<IP_ADDRESS>:8000
[14:59:23 INF] Docker image postgres:12-alpine already installed
[14:59:23 INF] Running image postgres:12-alpine for postgres_1c29ada2-8
[14:59:23 INF] Application bff-auth started successfully with Pid: 31856
[14:59:24 INF] Running container postgres_1c29ada2-8 with ID 66a072b3f81a
[14:59:24 INF] Replica postgres_1c29ada2-8 is moving to a ready state
[14:59:24 INF] Collecting docker logs for postgres_1c29ada2-8.

The platform (Linux/macOS/Windows): Windows 11

When we tried with RabbitMQ, then we have got the same issue, we couldn't set username and password for RabbitMQ via variable environments. So I thought that this bug happen for all containers run on Podman with tye :|

@thangchung Can you describe your setup a bit more?  Are you testing in WSL2, or are you testing on Windows using a podman remote client that's connected to podman running in WSL2?  I'm not seeing this issue when testing against podman running on my Mac, nor in WSL2 on my Windows machine.  I've not tested the remote client configuration, however.

The same issue is with Podman and WSL2; tried with environment file or provide environment variables in Yaml file but cannot start the container with correct variables

@philliphoff  Yes. I would like to confirm that this bug has happened on the remote client. I thought that was the bug in the Podman client and there is a PR to fix it, and hope after the release in a new version, I can re-visit to see whether it works with tye or not? See it https://github.com/containers/podman/pull/12503


Mandatory slash at the end of oauth_callback URI is incompatible with Google Dev Console credential settings

Mandatory slash at the end of oauth_callback URI is incompatible with Google Dev Console credential settings. In Google Dev console Credential one cannot register a call back URL that end with a slash. But oath client inserts the slash, leading to Error: redirect_uri_mismatch
The slash shouldn't be mandatory in oath2 client. Or should be allowed in Google Dev Console settings.
This can be reproduced by running any example for python api client, e.g.
https://github.com/youtube/api-samples/blob/master/python/upload_video.py
The issue is in tools.py:
    if not flags.noauth_local_webserver:
        oauth_callback = 'http://{host}:{port}/'.format(
            host=flags.auth_host_name, port=port_number)

Thank you for creating this issue, however, this project is deprecatedand we will only be addressing critical security issues. You can read moreabout this deprecation here.
If you need support or help using this library, we recommend that you ask yourquestion on StackOverflow.
If you still think this issue is relevant and should be addressed, pleasecomment and let us know!


Support initialization of registries via BARTOC API types

BARTOC collects information about vocabulary APIs with two fields for each:

API url
API type

cocoda-sdk should support initialization of a registry with this data. See https://github.com/gbv/bartoc.org/blob/main/vue/utils.js for current implementation in BARTOC. Maybe cdk should internally support a registry cache as well?

My suggestions on how to implement this:

The "registries" as currently used stay exactly the same.
This issue is about accessing data for a certain concept scheme, right? So how about we add an initializeScheme method that takes as an input a concept scheme with the API field and adds certain methods to that object (like this, but I now see that it's missing some important scheme-related methods). After that, you'll be able to use scheme._getTop() to query the top concepts of that scheme, for example.
Change adjustSchemes in a way that if the API field is given for a certain scheme, it will call initializeScheme for it. With this, we could register the BARTOC API in cocoda-sdk once (the old way) and all methods returning a scheme will adjust it so that data is coming from the API defined in API if available.

What do you think?

@nichtich I've started to implement this and encountered an issue that will probably affect many of BARTOC's vocabularies that have to API field set. The issue is that some (many?) APIs require using a particular vocabulary URI. For example, for STW the default URI is http://bartoc.org/en/node/313 (of course since it's BARTOC). but the API expects http://zbw.eu/stw.
I saw that in BARTOC, you used a workaround by requesting top concepts for each possible scheme URI and then remembering which one returned a result. Unfortunately, this is neither feasible (requires multiple requests) nor useful (what if a scheme doesn't have top concepts?).
Do you have an idea on how to get around this? One idea I've yet to try is to use the getSchemes method of the same provider and then remembering the main URIs for the supported schemes. If another request is made then and we need to know which of the URIs to use, we can find the correct URI in that list. This is only feasible if API only has a limited amount of schemes though because we need all of them.

I submitted the first implementation in branch issue-34. The current workaround I used for the above issue is the following: Each provider for schemes (i.e. ConceptApi and SkosmosApi) now keeps track of main scheme URIs for all supported schemes. If for a certain scheme it is unknown whether it's supported, we request information about that scheme from the API. If information is available, it is saved in a "approvedSchemes" cache (so later we only need to retrieve the main scheme URI from that cache). If no information is available, it is assumed that the scheme is unsupported by the API and it is saved in a "rejectedSchemes" cache.
There is also an example usage under examples/bartoc.js which shows how easy cocoda-sdk can be used with the feature if using the BARTOC api. With minimal setup, we can request both schemes from the BARTOC API and concepts from the respected APIs for the schemes, if available.

I've tried the example but it failed with EuroVoc because BARTOC did not include the URI http://eurovoc.europa.eu/domains used to identify BARTOC at the corresponding Skosmos instance.

Found scheme EuroVoc, it was initialized with SkosmosApi (https://bartoc-skosmos.unibas.ch/rest/v1/)
Loading top concepts for EuroVoc...
(node:101586) UnhandledPromiseRejectionWarning: InvalidOrMissingParameterError: Invalid or missing parameter: scheme (Missing or unsupported scheme or VOCID property on scheme)

I think the result is saved in rejectedSchemes. To make use of it applications need to catch the error and show a message or whatever is appropriate.
Looks ok except the handling of different providers in registryForScheme (https://github.com/gbv/cocoda-sdk/blob/issue-34/providers/base-provider.js#L485-L495) could be moved to the individual provider classes (ConceptApi and SkosmosApi) e.g. as method registryConfigForScheme(scheme).

I will look into the EuroVoc issue.

Looks ok except the handling of different providers in registryForScheme (https://github.com/gbv/cocoda-sdk/blob/issue-34/providers/base-provider.js#L485-L495) could be moved to the individual provider classes (ConceptApi and SkosmosApi) e.g. as method registryConfigForScheme(scheme).

I think it would make even more sense to move the registryForScheme method to the CocodaSDK class and then do it like you're suggesting with a method on each provider class.

I think the result is saved in rejectedSchemes. To make use of it applications need to catch the error and show a message or whatever is appropriate.

You added the appropriate URI to the BARTOC entry and now it works, right? Because I couldn't reproduce the error.
With the other change from my previous comment, I now (not yet pushed) changed the registryForScheme to cycle through all entries in scheme.API and use the first one that returns an initialized registry. The issue with this is that we don't want to throw an error because the next entry might work. Also, the code is called in adjustScheme which is called for every scheme returned by getSchemes, so I would say throwing an error wouldn't be appropriate.
However, we do need a way to detect errors when using API types. Any suggestion how to do this?

However, we do need a way to detect errors when using API types. Any suggestion how to do this?

The current way (throwing an error) seems fine.

The current way (throwing an error) seems fine.

Ah, I only now understood that the error occurred during getTop, not in registryForScheme. So that's okay then. 👍 What I meant is that we currently don't have any way to detect errors in registryForScheme because it will try multiple things and we don't want to throw an error prematurely. In theory, we could keep track of the errors and if in the end nothing succeeds, we could throw an error containing an array of errors. Something like that.

Merged into dev, will be included in the next release.


Guild stats not working for big servers

\guild stats command does not work for big servers.
The looping over the user data in server quits after 140 iterations.
Solution: Tracking/Saving user join and quits data.

Storing data in JSON files is inconsistent.
Trying to find an alternative way to store data, maybe SQLite.


iamdhrutipatel

[X] I have read the Code Of Conduct.

[X] I have followed all the steps of submission properly.

Thanks, @iamdhrutipatel , for opening the pull request! 👏
Star ⭐  this project and tweet about your contributions and tag @clubgamma.
Also join the Discord Server
Ready to merge your PR!!!


User profile color.

Like nostrudel we can use the user's public key first 6 chars to create a hex color and put it around their profile. Then scammers can't make similar accounts easily.

Like nostrudel we can use the user's public key first 6 chars to create a hex color and put it around their profile. Then scammers can't make similar accounts easily.

Good idea!


[ISSUE:] Overlay shown on top of searchfield

if  maxSuggestionsInViewPort value exceeds screen height and showOverlay is true ,then overlay is shown at top of the searchfield.

maxSuggestionsinviewPort should have a  constraint

I'm still having this problem, even if I set maxSuggestionsInViewPort as 1, and itemHeight as 10. Any solutions?

@karacaemre as a temporary workaround, you can specify your custom offset, this way the overlay is always shown at a fix position and is not dynamically positioned
 offset: Offset(0, 50),

Released v0.7.2 which adds a new property suggestionDirection which should give you more flexibility to position the suggestions.
However, searchfield should support the dynamic positioning of suggestions based on the available space, this is being tracked here https://github.com/maheshmnj/searchfield/issues/56


How does TARS implement https in go language?

How to use crt and key certificate files? Specifically, when deploying on TARS, how to load these certificates?

如何使用crt和key等证书文件？具体到TARS上部署的时候，如何加载这些证书？

It can be made into remote configuration, pulled to the local, and then loaded; or packaged with the bin file for release.

可以做成远程配置, 拉取到本地, 然后加载；或者和bin文件打包到一起发布。


Add execute_request.extra for extra code-cell params

cc @andypetrella @maasg

Shall we call this context for instance (I know there are implications and we can delay this renaming if necessary ^^)


Please provide sample code for SPA -  ASP.NET Blazor Web Assembly

Please provide documentation and sample code for SPA type of application ASP.NET Blazor Web Assembly using Microsoft Graph etc.
https://learn.microsoft.com/en-us/aspnet/core/blazor/hosting-models?view=aspnetcore-7.0#blazor-webassembly

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

ID: f90ca42e-b36c-1d67-b635-1bb4750968b1
Version Independent ID: 01bcb6b2-cc5a-ef80-4550-822d22b34250
Content: Code samples for customer tenants - Microsoft Entra
Content Source: articles/active-directory/external-identities/customers/samples-ciam-all.md
Service: active-directory
Sub-service: ciam
GitHub Login: @msmimart
Microsoft Alias: mimart

@hkusulja
Thanks for your feedback! We will investigate and update as appropriate.

Hi @hkusulja
Here is a link to the official Microsoft documentation for building a Blazor WebAssembly app that signs in users and calls a protected API using the Microsoft identity platform and Microsoft Graph
https://docs.microsoft.com/en-us/azure/active-directory/develop/tutorial-blazor-webassembly.
This tutorial walks you through the process of creating a new Blazor WebAssembly app configured to use Azure AD for authentication and authorization, and then retrieving data from a protected web API, in this case, Microsoft Graph1. It also includes sample code and step-by-step instructions.
I hope this helps! Let me know if you have any further questions.

@hkusulja
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation

but this code is not example of requested link - https://learn.microsoft.com/en-us/azure/active-directory/external-identities/customers/samples-ciam-all?tabs=apptype
for external identities - customers.

@msmimart
Can you please check and add your comments on this doc update request as applicable.

@hkusulja
I'm going to assign this to the document author so they can take a look at it accordingly

Fyi @henrymbuguakiarie

Hello @hkusulja,
Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response.
The request for "documentation and sample code for SPA type of application ASP.NET Blazor Web Assembly using Microsoft Graph" is not in our plan for FY24. However, I have created an internal work stream to explore whether we can provide this request in FY25.
I'm going to close this GitHub issue since we are moving away from using GitHub issues, as announced in Announcing a new way to give feedback on Microsoft Learn.

#please-close


update compute package to 0.7.3

Coverage remained the same at 100.0% when pulling 7a1f42173dfc36e1cf4b06eb63e8bc1679bb5c0d on ashleyschuett:updateCompute into a622ad29941f0b2ec1fc9ff1b2855525b573b1b4 on GoogleCloudPlatform:master.

Thanks! Released<EMAIL_ADDRESS>with the Project:get API addition.


Another loading issue: No module named 'ldm.modules'; 'ldm' is not a package

Hi
any chance you can help me with this issue?  the following is from the log file; the node won't load for me.
Many thanks

E:\SD\ComfyUI_windows_portable\python_embeded\lib\site-packages\huggingface_hub\file_download.py:659: FutureWarning: 'cached_download' is the legacy way to download files from the HF hub, please consider upgrading to 'hf_hub_download'
warnings.warn(
Loading pipeline components...: 100%|████████████████████████████████████████████████████| 6/6 [00:00<00:00, 10.16it/s]
Traceback (most recent call last):
File "E:\SD\ComfyUI_windows_portable\ComfyUI\nodes.py", line 1735, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 883, in exec_module
File "", line 241, in call_with_frames_removed
File "E:\SD\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-AnimateDiff-Evolved_init.py", line 2, in
from .animatediff.nodes import NODE_CLASS_MAPPINGS, NODE_DISPLAY_NAME_MAPPINGS
File "E:\SD\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-AnimateDiff-Evolved\animatediff\nodes.py", line 17, in
from .motion_module import InjectorVersion, eject_params_from_model, get_injected_mm_params, inject_params_into_model, load_motion_lora, load_motion_module
File "E:\SD\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-AnimateDiff-Evolved\animatediff\motion_module.py", line 4, in
from ldm.modules.diffusionmodules import openaimodel
ModuleNotFoundError: No module named 'ldm.modules'; 'ldm' is not a package
Cannot import E:\SD\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-AnimateDiff-Evolved module for custom nodes: No module named 'ldm.modules'; 'ldm' is not a package

Just to add - yes I have updated ComfyUI and installed the latest repo of this addin.  So any actual info on what ldm.modules relates to would be of help

Same problem.

I think the issue is with some of the import statements currently not including full comfy version, which might cause issues 0.0001% of the time depending on your environment. Should have a fix for this in the next 24 hours. A ComfyUI update just happened to broke stuff anyway, so I'll try to get to this once I have things working again.

I merged a PR that should (hopefully) fix the issue you're experiencing. Pull the latest version, (and make sure your ComfyUI is updated too - it had an update yesterday that I had to update AnimateDiff-Evolved code for), and let me know if you still get that error!

Thank you, this works fine now, much appreciated.


Retrieve coordinates of current active window

Short overview
Provide functionality to retrieve coordinates (x,y,w,h) of the currently active window
Use case
Limit actions like e.g. image search or OCR to a specific window
Detailed description
When performing image search or OCR one might want to limit the search space to a single window to reduce possible false positives.
libnut should provide functionality to retrieve the absolute on-screen coordinates (x,y,width,height) for the currently active window

Closed by #23


several fixes and optimizations for compaction

Added code to add dependency jars to distributed cache.
In Mapper class, created method populateRecord to replace AvroUtils.convertRecordSchema, which is more efficient, since AvroUtils.convertRecordSchema needs to serialize the record to byte array and then deserialize it.
For Avro key schema, created method removeUncomparableFields to replace getAllFieldsExceptMap, since we not only need to remove MAP fields, but also need to remove ARRAY and ENUM fields, as well as UNIONS that contain one of those types. Also, getAllFieldsExceptMap was not recursive, which is now fixed.

The reason to remove those fields in Avro key schema is that a schema that contains these fields cannot be used as the dedup key.

@ibuenros please review

I'm a bit confused, shouldn't gobblin-runtime itself handle the distributed cache?

@ibuenros Compaction does not use Gobblin runtime. It's something completely independent, similar as Camus daily sweeper..

@ibuenros updated

LGTM


[dependencies.package] replacement leads to TOML parse error

Hi Luca 👋
very useful little tool, thanks for open-sourcing it! 🙏
Just tried running it on our codebase and there's two little things I noticed (will open a second issue for number 2).
this one was really easy to fix manually, so no biggie, but still wanted to point it out. :)

This is indeed a bug, thanks for reporting it!

Fixed with #27


Parse error with URL like 'response.json'

Asking for URL like response.json will cause error. I tracked down this error to a parseUrl
function of InMemoryBackendService. The problem is, that the collectionName gets seen as base, and the collectionName then is empty, and it throws.
I tried to add slash before the URL, but it ends up with same result.
export class InMemoryDataService implements InMemoryDbService {
    createDb() {
        let response= {
            prop: 'string',
            ...
        }
        return {
            'response.json': response
        }
    }
}

I suppose so. It's looking for something like api/response.json.  A plain / is simply removed before it gets to that line.
I'd welcome a PR for an improved parseUrl. Otherwise, please work around it on your end as we are unlikely to get around to fixing this to suit your need. It is just a demo tool.

I think, that this issue shouldn't be closed, as the error is not on my part. Maybe add an label?
And also, I thing this tool is great thing for testing, and not just a demo thing for Angular 2 docs.

@Akxe One thing that I often do is to use a configuration service (or something of the like). You can have a base URL in the service that is based on the environment, maybe /api for development, and / for production. I use this alot actually, as URLs are so common in the app. Not just for use the in-memory-web-api, but for most cases, I keep the URL (or it's base) configurable by environment

We can't anticipate every request url scheme. The v.0.1.6 version lets you override the parseUrl method with your own implementation. Have fun.


Add a built-in clipboard manager

Check for existing issues

[X] Completed

Describe the feature
First, I want to say that Zed is slowly turning into one of my favourite editors ❤
That being said, I am migrating from a JetBrains IDE, and one missing feature in Zed that I had gotten so used to is the ability to hit CMD + SHIFT + v to open a built-in clipboard editor with a stack of the last items copied to the clipboard. I understand this could be achieved in the future using a plugin, but I think it would be a great quality of life feature especially for users who delete often into the clipboard using either CMD + x or VIM.
Keep up the great work!
If applicable, add mockups / screenshots to help present your vision of the feature
Mockup:

I think many third-party tools can implement this function. Such as Maccy

I think the idea of having it built-in is that it only keeps buffers copied from Zed in its stack.


Possible bug + fix for s_loop_name_transfer in output_funcs

Hello!
I'm currently using the ZigZag tool for my masters thesis. While simulating a fixed architecture, variable loop unrolling and temporal mapping the following error occured.

Traceback (most recent call last):
File "/users/start2017/r0653464/Documents/Thesis/zigzag-master/output_funcs.py", line 493, in print_xml
spatial_mapping_W.tail = str(s_loop_name_transfer(cost_model_output.spatial_scheme['W']))
File "/users/start2017/r0653464/Documents/Thesis/zigzag-master/output_funcs.py", line 70, in s_loop_name_transfer
TypeError: 'int' object is not subscriptable

By debugging these errors. I think I found the source and a possible solution.
In the s_loop_name_transfer function, the variable mapping is given as an input. An example of this, with the correct structure is [[], [[3, 7], [5, 8], [1, 3]], [], []]
The function consists of 3 for loops which all go 1 level deeper in the nested array. At the end the fucntion  post_mapping[-1][-1].append((loop_name[va[0]], va[1])) is called. The va variables however are the integers inside the nested for loops. These are accesed again like an array, which is not possible.
A fix is to delete the final for loop and to switch va[0], va[1] with inner_li[0], inner_li[1].
I think this is the intended solution  because it switches the first integer with the respective loop name.
Best regards,
Mike Storms

Hi Mike,
Thank you for selecting our tool for your master thesis!
I have tested the code and cannot repeat the same problem you have. To fix it, you can do the following quick checks:

Are you using the newest version of the code? If not, rerun it with the newest version. If the error is still there, go to 2.
The correct data format that function s_loop_name_transfer  expects is like [[], [[[3, 7], [5, 8]], [[1, 3]]], [], []] or [[], [[[3, 7]], [[5, 8], [1, 3]]], [], []], which not only indicates which loops are unrolled at which arch level, but also tells which loops are unrolled along which PE array dimension (row or colunm). For example, [[], [[[3, 7], [5, 8]], [[1, 3]]], [], []] means loop 3 (OX) and loop 5 (C) are unrolled along the row 7 and 8 times resp., and loop 1 (FX) is unrolled along the colunm 3 times (in this case, the active PE array size is 56 x 3). To make this transfer, from [[], [[3, 7], [5, 8], [1, 3]], [], []] to [[], [[[3, 7], [5, 8]], [[1, 3]]], [], []], function spatial_loop_same_term_merge  in the output_funcs.py is called, which incorporate such unrolling layout information into spatial mapping from a parameter called cost_model_output.flooring. You need to check why this function is not triggered in your situation (e.g. put some breaking points and check the code execution flow). Most likely, I guess, your spatial-mapping-related input settings are not fully correct.
If the issue is still there, you can post or email me your 4 input setting files. I will have a look.

Best regards,
Linyan

Thank you, it seemed the version i was using was not up to date. Weird, as other networks did compute, nevertheless its fixed now!

ok!


Feature request: case without curly braces

To avoid something like this:
switch ($foo) {
    case 'bar': {
        // ...
    }
}

:+1:
(I would like have a fixer to do the reverse, so I could base it on the one you want ;)  )

wow, any framework uses braces for case?
just curious

don't know of any major framework, I just keep using those ^-^

ok, I'm good with it ;)
btw, you need to break a case before closing } ?

btw, you need to break a case before closing } ?

not needed, this;
<?php
$a = 0;
switch($a) {
    case 0 : {
        echo '0';
    }
    break;
    default : {
        echo 'test';
    }
}

acts the same as:
<?php
$a = 0;
switch($a) {
    case 0 : {
        echo '0';
        break;
    }
    default : {
        echo 'test';
    }
}

so you still need the break, if you could ommit it (if closing } acts as break) it would be cool ;)

Actually, these extra braces can appear anywhere, not only around case body (example). This is why having the break statement inside or outside the braces has the same result.
AFAIK, these braces have no special meaning (no variable scope or something similar) and I think the fixer should be aware of that and remove them all.

just be aware of $array{$index} :D

Closed by #2929


No matching export

×  utils/auth.ts:5:9: No matching export in "../../node_modules/.pnpm/lucia-adapter-dynamodb<EMAIL_ADDRESS>for import "DynamoDBAdapter
package.json:
{
    ...
    "dependencies": {
        ...
        "lucia": "^3.2.0",
        "lucia-adapter-dynamodb": "^2.1.0",
        "oslo": "^1.2.0",
        "ulid": "^2.3.0"
    }
}

auth.ts:
import { Lucia } from "lucia";
import { DynamoDBAdapter } from "lucia-adapter-dynamodb";
import { DynamoDBClient } from "@aws-sdk/client-dynamodb";

export const dynamoDBClient = new DynamoDBClient({
    credentials: {
        accessKeyId: "xxx",
        secretAccessKey: "verysecret",
    },
    region: "xx-xx-#",
});

export const dynamoDBAdapter = new DynamoDBAdapter(dynamoDBClient, {
    tableName: "AuthTable",
    pk: "PK",
    sk: "SK",
    gsi1Name: "GSI1",
    gsi1pk: "GSI1PK",
    gsi1sk: "GSI1SK",
    gsi2Name: "GSI2",
    gsi2pk: "GSI2PK",
    gsi2sk: "GSI2SK",
});

Hi @schwjustin , I published a new version (2.2.0) to update the Lucia version. Please try if that solves the issue

with /dist it works just fine

Yes, since the index.js and index.d.ts files are inside that folder.
I found a problem in the previous package.json file where the types field was not properly set, and published a new version (v2.2.1) to fix that. Please try if that one solves the issue. Also please try reset the node_modules folder to clear previous versions.


Fixed code fragments in WPF controls overview

Fixed code fragments in WPF controls overview
Related to dotnet/samples#1015
Fixes #8563

Closing and reopening to begin new build after dotnet/samples#1015 was merged.


Support for sending commands

Includes changes from https://github.com/JohNan/pyelectroluxgroup/pull/2 because of the cli.py shenanigans.
Adds  (rather naive, as in we don't check validity of the commands client side. This could be easily added if we're fine with assuming that all the command calls must match one of the keys returned from the /state endpoint) support for sending commands to the appliances. Also extends the CLI arguments to distinguish between listing appliances and sending out commands.

Rebased on top of https://github.com/JohNan/pyelectroluxgroup/pull/2 and added a fixup for the infinite recursion during token refresh.


[BEAM-8137] Refactor External Worker Service to be part of sdks-java-harness

Move external worker service from runners/portability/java to sdks/java/harness
Move external worker service depdended classes from runners/java-fn-execution to sdks/java/fn-execution
In order that external worker service can be launched in worker container's boot script where only beam-sdks-java-harness is initially included in the image.
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java PreCommit

Run Java PreCommit

@ibzib could you help take a look ?

Run Portable_Python PreCommit

Run Java PreCommit

Run Java PreCommit

Run Java PreCommit


Integration with mypy?

I saw that your package has a validate decorator to ensure the data frame during run time,
Is there a way for it to integrate with mypy for static code analysis?

When I looked at this as I developed this module, I couldn't find an easy way to integrate. I haven't checked since, so in case you have any pointer on how that would be possible, I'd be happy to check it out

I would also love to use this together with mypy (thanks for the package by the way ❤ ).
It might be possible to implement using mypy plugins 🤔
Never worked with it, but recently saw this video, maybe this helps.


Add Activity Feed

I'd like to have a few features as part of this:

An Activity Feed, pretty similar to AniList's, e.g. when updating your hours played for games you'd add an activity feed entry like ''Connor played Half-Life for 5 hours"
Activity Feed entries should be able to be disabled.
Activity Feed entries should be deletable.
No freeform text, just updates about games being added to your library and such.
Following other users?
Per-user activity feed, following activity feed, and global activity feed.

Prior works:

AniList's activity feed
public_activity gem
Kitsu's feed

Maybe create a model for Events? Events would have a relation to the user performing the event and the game purchase that the event is being performed on. I guess we should only have specific changes create events?
Then the activity feed would just list the most recent events. For now I'll just have a global activity feed, following other users can be done afterward.

The last part of this, following/followers has been split into its own issue: #653
This can be closed now :)


Make an instalation more clear

There is a dedicated section in README.md about supported versions. I'm not sure how it's not clear already


Failed to find assets path for flutter_assets

I am trying to embed a Flutter module into iOS app. But when I tap the button that will show the FlutterViewController, a blank screen shows up and this is printed on the console:
Failed to find assets path for "flutter_assets"
[VERBOSE-2:engine.cc(111)] Engine run configuration was invalid.
[VERBOSE-2:FlutterViewController.mm(462)] Could not launch engine with configuration.
flutter: Observatory listening on http://<IP_ADDRESS>:54632/

I followed this tutorial https://github.com/flutter/flutter/wiki/Add-Flutter-to-existing-apps
I added a FLUTTER_ROOT to my build settings
This erros happens with FlutterViewController.
When using a FlutterAppDelegate, nothing happens (no blank screen, nothing).

Flutter doctor:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, v0.9.4, on Mac OS X 10.14 18A391, locale en-BR)
[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 10.0)
[✓] Android Studio (version 3.2)
[✓] IntelliJ IDEA Community Edition (version 2018.1.5)
[✓] Connected devices (1 available)

• No issues found!

I solved it by changing to master channel and it solved.

To change channel use the cli flutter channel master
After that I deleted the ".ios" folder inside the flutter project and run a flutter build --ios to force Flutter to re-generate the .ios folder.
Then I did a pod install in my native iOS app.

Is this a dup of #23980 ?

Duplicate of #23980


Is there really no way to use my own UI??

I sign up for clerk and all I can do is make "applications", which reroutes me to this screen:

Is there really no way to use the auth capabilities of this lib without it shoving it's UI down my throat?

The docs here explain how to setup custom sign-in/up pages:
https://clerk.com/docs/authentication/custom-flows/password

Hello @Johnrobmiller :)
As @DatKyle mentioned above, you can find information for creating custom flows using the following link: https://clerk.com/docs/authentication/custom-flows
If this was helpful, could you close this issue? Otherwise, I suggest you join our Discord channel and ask for more information.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


feat(#185): Add Unit Tests for XmlClass#constructors

Add unit tests for XmlClass#constructors() method.
Closes: #185.

History:

feat(#185): add unit test for XmlClass#constructors
feat(#185): fix all qulice suggestions

PR-Codex overview
Focus of the PR:
This PR focuses on adding unit tests for the constructors method in the XmlClass class.
Detailed summary:

Added unit tests for the constructors method in the XmlClass class.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@maxonfjvipon Could you have a look, please?

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 3min)


Commiting deleted files breaks lint-staged

If I delete a file, and then I try to commit the deletion. The linter throws an error in the pre-commit hook, because it tries to lint the deleted file that doesn't exists anymore.
Running eslint on git staged files: **/*.@(js|jsx)
Running jscs on git staged files: **/*.@(js|jsx)
Error: Path internals/scripts/clean.js was not found.
    at .<anonymous> (node_modules/jscs/lib/checker.js:188:19)
    at Array.<anonymous> (node_modules/vow/lib/vow.js:712:39)
    at Immediate.callFns [as _onImmediate] (node_modules/vow/lib/vow.js:23:35)
    at tryOnImmediate (timers.js:543:15)
    at processImmediate [as _immediateCallback] (timers.js:523:5)
pre-commit:
pre-commit: We've failed to pass the specified git pre-commit hooks as the `lint:staged`
pre-commit: hook returned an exit code (1). If you're feeling adventurous you can
pre-commit: skip the git pre-commit hooks by adding the following flags to your commit:
pre-commit:
pre-commit:   git commit -n (or --no-verify)
pre-commit:
pre-commit: This is ill-advised since the commit is broken.
pre-commit:

From: https://github.com/mxstbr/react-boilerplate/issues/397

Thanks @mxstbr. I'm already started working on #8 in a 1.0 branch. Hopefully, this one should be also resolved when I'm done.

Is there any ETA? It's a critical bug that prevent us from linting files on pre-commit...

I'm working on an experimental branch that should help solving this. Can't give any ETA yet.

Just dittoing my anticipation for a solution. And, wondering if this was merged into the master because if it did I am still running into an issue with it as well. Thanks for all the hardwork okonet!

What version are you using? It was fixed and released 4 months ago.


Add basecamp3 webhook integration.

Lack of the documentaiton

Automated message from Dropbox CLA bot
@TomaszKolek, it looks like you've already signed the Dropbox CLA. Thanks!

@TomaszKolek it looks like you added documentation etc. now; is this ready for review?

@timabbott Yeah, I was waiting for tests to be sure that everything is OK and that's why I didn't remove WIP label.
I think its ready.

One note:
Basecamp has a lot of events and no documentation about them - so I was playing around the system but I'm sure I omitted some - so we need to be aware that in the future we'll discover new things ;-)

Yep, makes sense.  Merged, thanks @TomaszKolek!


When will Queue storage be avaliable in v3 Azurite

When will Queue storage be avaliable in v3 Azurite? Right now im still using azure storage emulator to host my queue for local function with queue trigger.

Close this for duplicated issue of #230


Solve some issues with QString compatibility with emojis

Description of Changes
Attempt to correct some of the problems that arise from the string length difference between QString and Python3 str

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[ ] Included a screenshot or animation (if affecting the UI, see Licecap)

Issue(s) Resolved

Fixes #
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:

Hello @impact27! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/utils/syntaxhighlighters.py:

Line 582:80: E501 line too long (82 > 79 characters)
Line 605:80: E501 line too long (86 > 79 characters)
Line 627:80: E501 line too long (80 > 79 characters)
Line 1189:80: E501 line too long (86 > 79 characters)


Look into Zap missing email info

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1653
Originally created by @bencodezen on 2020-01-30 21:02:47

it looks like maybe the Typeform info isn't posting through to a new account issue... maybe an issue with the zap. See https://gitlab.com/meltano/account-management/issues/206 for an example

View 2 previous comments from the original issue on GitLab


The CDK should remember my window position

I carefully position my CDK window where I want it for effective debugging (relative to things like source windows, game client window, and devtools window).  The devtools window position is remembered, but I have to reposition the CDK window any time I've closed the CDK and reopened it.
It'd be nice if the CDK would remember my window position.  It'd probably be ideal if it remembered a unique position per project.
This is a very minor issue.

Yea it's super annoying that it doesn't do this.

Fixed in the linked commit


cbmc: 5.91.0 -> 5.95.1

Description of changes

https://github.com/diffblue/cbmc/releases/tag/cbmc-5.95.1
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 309880 run on aarch64-linux 1

1 package built:

cbmc

please mark broken no x86_64-darwin
https://hydra.nixos.org/job/nixpkgs/trunk/cbmc.x86_64-darwin

please mark broken on x86_64-darwin https://hydra.nixos.org/job/nixpkgs/trunk/cbmc.x86_64-darwin

Done

fixes https://hydra.nixos.org/build/202332940 hence zhf https://github.com/NixOS/nixpkgs/issues/309482


⚠ ECDC Shop has degraded performance

In 3974656, ECDC Shop (https://shop.memmingen-indians.de) experienced degraded performance:

HTTP code: 200
Response time: 5123 ms

Resolved: ECDC Shop performance has improved in 6ea8bbb after 17 minutes.


[request]: Separate, stable crate for AttributeValue

A note for the community

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue, please leave a comment

Tell us about your request
Currently aws_sdk_dynamodb::model::AttributeValue and aws_sdk_dynamodbstreams::model::AttributeValue are distinct types, even though they are identical.
The definition for these two hasn't changed since aws-sdk v0.0.23-alpha.
Tell us about the problem you're trying to solve.
The ecosystem currently has at least 5 different definitions of AttributeValue.

aws_sdk_dynamodb::model::AttributeValue
aws_sdk_dynamodbstreams::model::AttributeValue
aws_lambda_events::dynamodb::attributes::AttributeValue
rusoto_dynamodb::AttributeValue
rusoto_dynamodbstreams::AttributeValue

That number is much larger if you consider that rustc considers each version to be a different type (e.g. aws_sdk_dynamodb::model::AttributeValue from aws_sdk_dynamodb version 0.9 is distinct from aws_sdk_dynamodb::model::AttributeValue from aws_sdk_dynamodb version 0.8).
I believe it would be hugely beneficial for the community if there were one definition of AttributeValue in a standalone stable (1.0) crate, so that every crate that works with attribute values could depend on it and use AttributeValues interoperably.
To avoid a https://xkcd.com/927/ situation, I haven't created a standalone crate for this. I'm impartial about who maintains it. It seems most reasonable to me that the aws-sdk-rust team would own it. But I would also be happy to extract the aws-sdk-rust code into a separate crate and maintain it if aws_sdk_dynamodb would use it.
Are you currently working around this issue?
I maintain serde_dynamo, the library for converting complex AttributeValues into structured data.
We work around this issue by creating feature flags to support every different version of AttributeValue. See (https://docs.rs/serde_dynamo/latest/serde_dynamo/#features)[https://docs.rs/serde_dynamo/latest/serde_dynamo/#features] for more information on the approach.
Right now, we have to track all 5 crates and make a new release, with new feature flags, every time one of them updates.
We use macros to derive the various implementations because, although aws_sdk 0.8's AttributeValue and aws_sdk 0.9's AttributeValue (for example) are exactly the same, they are distinct according to the compiler, so we need separate implementations.
If there were a standalone stable 1.0 crate that contained the definition of AttributeValue, then serde_dynamo would have only one implementation, no need for feature flags, and no need for the implementation macros. And more importantly, support wouldn't need to be added to serde_dynamo after a new release of aws_sdk (a task that isn't hard or all that time consuming from a technical perspective, but still a chore that needs to get done and doesn't always get done immediately).
Users of serde_dynamo would benefit significantly because 1/ support for the new version of aws_sdk would be available the second that aws_sdk has a new version, and 2/ they wouldn't have to bump a feature flag every time they bumped their version of aws_sdk.
Additional context
If the aws-sdk-rust team is interested in this proposal, I will also try to work with the aws lambda events team for the benefit of the community.
I will also work with the rusoto team, but as rusoto is in maintenance mode, I could understand them not adopting.
I'd be willing to submit a PR to make this happen if requested.

The reason for the separation of these types is that they're only the same right now. If we unify these types, that's a commitment to keep them unified for the rest of the lifetime of AWS Rust SDK v1. These types are controlled by the various service teams and we (the Rust SDK team) are not comfortable making a commitment that these types will always be identical. However, given that this isn't a great user experience, I'll convene a team meeting and see if we can come up with a better way to do things.

This has been brought up before: #75

Is there a plan in place for how to proceed on this issue? The From impl suggestion in #75 sounds promising.


What color format imgui uses?

(sorry i posting that in this repo i can't post it to official imgui repo it says You can't perform this action at that time)
In imgui demo i see following code lines
            if (strstr(item, "[error]"))          { color = ImVec4(1.0f, 0.4f, 0.4f, 1.0f); has_color = true; }             else if (strncmp(item, "# ", 2) == 0) { color = ImVec4(1.0f, 0.8f, 0.6f, 1.0f); has_color = true; }             if (has_color)                 ImGui::PushStyleColor(ImGuiCol_Text, color);
but what color format is it? it not rgba or cmyk i dont have any ideas

Colors are stored in a 4-element vector, where each element is a 32-bit float encoding a normalized color value (e.g. the values span from 0.0 to 1.0). RGBA order.


scala: Add tests, update script

Motivation for this change
Add tests, update script
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[X] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Hi @NeQuissimus, before this change we were able to call scala_2_12.override { jre = … }. However, this no longer works since scala_2_12 no longer has an override attribute. What’s the recommended way of handling this?

I fixed that in 7f50f98298643639f8844b5332693f8a2a667e85

Awesome, thank you very much for the quick fix!


--build-native-deps specify different image or image build script

func azure functionapp <app name> --build-native-deps

I am trying to deploy a Python package with mysqlclient as a requirement. It fails due to a lack of libmysqlclient-dev installed.
So is it possible to give a custom build script or change the image itself?

@sridhar562345
It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!

@AjayBathini-MSFT
Here is the documentation I followed.

@sridhar562345
Thanks for your feedback! We will investigate and update as appropriate.

Hello, @sridhar562345 - Python functions that bind with SQL are supported through Extensions Bundle, as documented here -- it sounds like you aren't using this SQL binding? Also, are you deploying a Python Function App or a Python package to the Function app? I'd be happy to help but could you elaborate with more details in a new post on the MS Q&A channel instead?
Closing for now since the issue doesn't point to/determine any faulty step in the doc referenced.


added Netlify badge to readme

Add Netlify Badge to README for rapid Netlify build-deploy status info.

Merged-in PR #74 to bring this PR up to date.


Please update opera add-on

Always warns me to update but there is no update in web store.

Unfortunately Opera decided to not review their addons for months now. Not just for this addon, but for many others (if not all) too. So at least for now, the development of Opera version of this addon has been discontinued.
This is very frustrating for me too. If you don't want to see the message, i believe you can turn off the errors display in the options. Your info won't be recorded in db, but at least you'll still be able to use that old version of addon.
FF and Chrome are still being updated in case you want to switch browsers too of course.

here's one of forum threads on the topic, some people are waiting for more than 10 months. https://forums.opera.com/topic/16609/very-long-extension-moderation-process/156

you can also try using this extension to install the addon from Chrome Addon Store:
https://addons.opera.com/en/extensions/details/install-chrome-extensions/

The third solution works! Thanks for your suggestion and thanks for your tools.  I will share your tool with my friends, let more people know it. Thanks again and happy hunting.


capslock as ctrl, escape and ctrl + hjkl

Hey,
Thank you for  creating this program.
anyway, I kind of have a stupid question. How can I use capslock as ctrl, escape and also make ctrl + hjkl as up down left right?

*

[main]

# Maps capslock to escape when pressed and control when held.
capslock = overload(control, esc)
control = layer(vim)

[vim]
k = up
j = down
h = left
l = right

# Remaps the escape key to capslock
esc = capslock

i tried this but this only works with the left contrll key and not the capslock key.
Thank for your time.

I would also like to know how I can disable certain keybindings on certain applications like for example in vim I would like the ctrl + hjkl functionality to not work.  Thanks again

sounds good thanks so much !


tailwind plugin breaks with tailwind 4 (alpha)

Provide a general summary of the issue here
I know it's an alpha release, but I wanted to give a heads up!
🤔 Expected Behavior?
successful migration to v4
😯 Current Behavior
error
💁 Possible Solution
I don't know when they plan to release the migration guide for plugin authors, but I updated the plugin inside my node_modules folder with this and it worked.

Looks like you don't need to check for that future flag anymore, as it's the default in tailwind v4
🔦 Context
No response
🖥 Steps to Reproduce
You can try this with any codebase running tailwind@v3 + tailwindcss-react-aria-components
$ npx @tailwindcss/upgrade@next -c ./tailwind.config.ts
≈ tailwindcss v4.0.0-alpha.30

│ Could not load the configuration file: Cannot read properties of undefined (reading 'length')

Version
latest
What browsers are you seeing the problem on?
Other
If other, please specify.
No response
What operating system are you using?
mac
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

We should still make this work in Tailwind itself without changing it for backward compatibility, thanks for flagging!

@adamwathan i saw that the related PR was merged but still some issues with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>this is a minimal repro for what is breaking for me, removing the plugin make it work
<sidebar data-collapsed="" className="group">

</sidebar

or using RAC compnoents this also should work
<Checbox className="group">

 {/* indicator*/}
</Checkbox>


Cannot import D:\ComfyUI\custom_nodes\ComfyUI_cspnodes module for custom nodes: cannot import name 'export_to_video' from 'diffusers.utils'

I do believe cspnodes isn't compatible with Comfy UI updates. I was using these nodes without problem until just recently. I get these exceptions now and the node fails to load.
Traceback (most recent call last):
  File "D:\ComfyUI\nodes.py", line 1864, in load_custom_node
    module_spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "D:\ComfyUI\custom_nodes\ComfyUI_cspnodes\__init__.py", line 1, in <module>
    from .cspnodes import NODE_CLASS_MAPPINGS, NODE_DISPLAY_NAME_MAPPINGS
  File "D:\ComfyUI\custom_nodes\ComfyUI_cspnodes\cspnodes.py", line 4, in <module>
    from diffusers.utils import export_to_video
ImportError: cannot import name 'export_to_video' from 'diffusers.utils' (D:\ComfyUI\venv\lib\site-packages\diffusers\utils\__init__.py)

Cannot import D:\ComfyUI\custom_nodes\ComfyUI_cspnodes module for custom nodes: cannot import name 'export_to_video' from 'diffusers.utils' (D:\ComfyUI\venv\lib\site-packages\diffusers\utils\__init__.py)

Same issue after I updated now I am getting this error...
File "D:\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_cspnodes_init_.py", line 1, in
from .cspnodes import NODE_CLASS_MAPPINGS, NODE_DISPLAY_NAME_MAPPINGS
File "D:\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_cspnodes\cspnodes.py", line 4, in
from diffusers.utils import export_to_video
ImportError: cannot import name 'export_to_video' from 'diffusers.utils' (D:\ComfyUI_windows_portable\python_embeded\Lib\site-packages\diffusers\utils_init_.py)
Cannot import D:\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_cspnodes module for custom nodes: cannot import name 'export_to_video' from 'diffusers.utils' (D:\ComfyUI_windows_portable\python_embeded\Lib\site-packages\diffusers\utils_init_.py)


Type parameter of Vm.prevrandao as uint256

In Solidity, block.prevrandao is typed as uint256, so there is no need to type it as bytes32.
Even its predecessor, block.difficulty was typed as uint256, so I don't understand the shift.

Confirmed this is the case in the Solidity docs, maybe this was oversight? cc @mattsse

Maybe we add a uint256 overload to avoid breaking changes

just an oversight I believe, let's overload it
internally uint256 or bytes32 doesn't matter

Thanks, guys :-)


[Bug]: Decompilation output is not written to decompiled.sol

Component
Heimdall Modules
Version
0.1.5
Please check the following

[X] This is not a duplicate issue
[X] I have checked the wiki and tried troubleshooting the issue

Operating System
Linux
Describe the issue you are facing
Should these lines in output.rs be uncommented to make it work?
// write_lines_to_file(
//     &decompiled_output_path,
//     decompiled_output
// );
//
// logger.info(&format!("wrote decompiled solidity to '{}' .", decompiled_output_path).to_string());

The decompile module is in beta, and the decompiled.sol output is not ready for production.
Once it is I'll enable outputting the solidity :)

Let us know when you enable it :)


fn case_set*: Simplify and make safe fn case_set*s as struct CaseSet::{one,many}

Algorithm
The case_set* fns, from what I can tell, are glorified/heavily optimized memsets.  They are optimized to work on short memsets, where they do aligned writes of larger integers up to u64.  Curiously, they seem to multiply every byte by 1, and I'm still not sure the point of that.
The optimizations that I see in the case_set* fns that I considered preserving are mainly:

larger writes for small power of 2 lengths
aligned writes for the above

The former is easy to preserve in Rust, but the latter is difficult to do so without overhead, as unaligned writes are UB, and so we'd need to at runtime check if they're aligned (a runtime-determined offset is used, so we can't reasonably ensure this at compile-time).  That said, the assembly generated for x86 and x86_64 appear to at least be largely the same (or more optimized for the larger than u64 cases), so I'm not sure this matters.
Since I assume the original case_set* code was written this convoluted way for some reason, I wanted to preserve as much of it as reasonably possible, and that's why I have cases for the small power of 2 lengths, rather than just using .fill, which compiles to a call to libc's memset.
However, in cursory benchmarking (I'm not sure what a good way to do this is (@fbossen, do you know?), but I timed the argon tests), none of the approaches seem to make a difference, as they all take between 1:12 and 1:16, where the approaches are:

original case_set*s
safe CaseSet with small powers of 2 optimization
.fill/libc memset

Note that libc's memset is probably already doing this optimization, and may have even more such optimizations.  The main difference for that is inlining, as the first 2 approaches are fully inlined, while libc's memset cannot be.
@fbossen, do you know why the optimizations done in the original case_set* fns were done?  Were they benchmarked?  Is there a way I can better benchmark my changes here?
I think the cautious approach would be to keep the CaseSet with small powers of 2 optimization approach, but I wonder what the downside of just calling memset is.
API
I've also simplified, consolidated, and genericized the API a bit.
UP_TO and WITH_DEFAULT are now const generic parameters on CaseSet, allowing there to just be a single function.  This is a separate struct with methods so these 2 generic parameters can be manually specified while the ones on the methods are inferred.
The API is generic over the element type rather than hardcoding u8.  In practice, the only other type used is i8.
Rather than having to specify the set_ctx closure separately when making multiple case set calls, now there's a many method that you give arrays of each arg so 1) they are grouped together and 2) you can specify set_ctx inline easily.  The dir/dirs arg is also made a generic T now, rather than &mut T, meaning you can put anything there, including the diridx or any other vars.  This is utilized in some of the calls that previously had separate case set closures and now can be consolidated into one while still keeping all the call orders the same.

@fbossen, I would request you as a reviewer, but the permissions still aren't set up right for that, so I'm tagging you here instead.

For benchmarking it is generally preferable to use a larger bitstream than a bunch of tiny ones (such as the argon test bitstreams). Some benchmark results were provided in the dav1d commit introducing the caseset macro https://code.videolan.org/videolan/dav1d/-/commit/e3b5d4d044506f9e0e95e79b3de42fd94386cc61.

For benchmarking it is generally preferable to use a larger bitstream than a bunch of tiny ones (such as the argon test bitstreams). Some benchmark results were provided in the dav1d commit introducing the case_set macro https://code.videolan.org/videolan/dav1d/-/commit/e3b5d4d044506f9e0e95e79b3de42fd94386cc61.

That makes sense, and thanks for finding the commit that introduced case_set; that helps a lot.
I'm not sure how to test "decoding first 1000 frames of Chimera (1080p, 8bit)", though.  If you let me know what the command to run that is, I can benchmark things to check my safe Rust implementation.

I see now that in the e3b5d4d044506f9e0e95e79b3de42fd94386cc61 commit introducing case_set, BlockContext's fields were all 8-byte aligned.  So it's possible that the alignment there was helpful for performance and we need to keep taking advantage of it.  In Rust, we can only safely do aligned writes if we're sure they are aligned, which can't statically verify since there are runtime offsets used.  To avoid the runtime cost, one idea I have is to mask off the lower 3 bits but only check the lower 3 bits are 0 in debug mode.  Like this:
let align = 8;
let mask = align - 1;
debug_assert!(offset & mask == 0, "{offset} is not {align}-byte aligned");
let aligned_offset = offset & ~mask;

Hopefully the & would be cheap enough compared to 2 &s and a predicted branch.
Alternatively, the aligned fields of BlockContext may be helpful enough on their own, as then they'd fit into cache boundaries much better, and so maybe we don't need aligned writes.
I'd like to see what benchmarking has to say more definitely about this.

I'm not sure how to test "decoding first 1000 frames of Chimera (1080p, 8bit)", though. If you let me know what the command to run that is, I can benchmark things to check my safe Rust implementation. Mainly I'm not sure where "Chimera" is, but a full command to run would be perfect, too. Thanks!

You would run a command such as time target/release/dav1d -i chimera_8b_1080p.ivf -l 1000 -o /dev/null multiple times (say 3 or 5) and pick the median or best time. I shared the "Chimera" file in the Slack channel on March 9.

Here are the benchmarks with hyperfine:
Original case_set:
Benchmark 1: ./target/release/dav1d -i ./tests/large/chimera_8b_1080p.ivf -l 1000 -o /dev/null
  Time (mean ± σ):      1.650 s ±  0.008 s    [User: 14.936 s, System: 0.693 s]
  Range (min … max):    1.632 s …  1.659 s    10 runs

Using small_memset as in this PR:
Benchmark 1: ./target/release/dav1d -i ./tests/large/chimera_8b_1080p.ivf -l 1000 -o /dev/null
  Time (mean ± σ):      1.642 s ±  0.011 s    [User: 14.958 s, System: 0.702 s]
  Range (min … max):    1.624 s …  1.658 s    10 runs

Using only memset (i.e. .fill):
Benchmark 1: ./target/release/dav1d -i ./tests/large/chimera_8b_1080p.ivf -l 1000 -o /dev/null
  Time (mean ± σ):      1.687 s ±  0.013 s    [User: 15.274 s, System: 0.655 s]
  Range (min … max):    1.664 s …  1.710 s    10 runs

Using only memset is clearly slower (1.687 s), but the safe Rust version using small_memset but no aligned writes (1.642 s) is slightly faster than the original case_set (1.650 s).  Given that, I think the small_memset version in this PR is the best, as it's the fastest and relatively simple.

Updated benchmarks after freeing up disk space as they were previously very full (see https://github.com/memorysafety/rav1d/pull/285#issuecomment-1579310135) and I don't want that to interfere with anything.  The results are mostly very similar, though:
Original case_set:
kkysen in 🌐 donna in rav1d on  kkysen/preparation-for-safe-fns-case-set is 📦 v0.0.0 via 🦀 v1.71.0-nightly via 🐏 4GiB/63GiB | 108MiB/2GiB took 17s457ms
at 11:56:19 AM ❯ c b -r && hyperfine './target/release/dav1d -i ./tests/large/chimera_8b_1080p.ivf -l 1000 -o /dev/null'
    Finished release [optimized] target(s) in 0.01s
Benchmark 1: ./target/release/dav1d -i ./tests/large/chimera_8b_1080p.ivf -l 1000 -o /dev/null
  Time (mean ± σ):      1.659 s ±  0.010 s    [User: 15.025 s, System: 0.648 s]
  Range (min … max):    1.647 s …  1.683 s    10 runs

Using small_memset as in this PR:
kkysen in 🌐 donna in rav1d on  kkysen/safe-fns-case_set is 📦 v0.0.0 via 🦀 v1.71.0-nightly via 🐏 4GiB/63GiB | 108MiB/2GiB took 21ms
at 11:54:56 AM ❯ c b -r && hyperfine './target/release/dav1d -i ./tests/large/chimera_8b_1080p.ivf -l 1000 -o /dev/null'
   Compiling c2rust_out v0.0.0 (/home/kkysen/work/rust/rav1d)
    Finished release [optimized] target(s) in 0.78s
Benchmark 1: ./target/release/dav1d -i ./tests/large/chimera_8b_1080p.ivf -l 1000 -o /dev/null
  Time (mean ± σ):      1.638 s ±  0.008 s    [User: 14.925 s, System: 0.674 s]
  Range (min … max):    1.624 s …  1.652 s    10 runs

Using only memset (i.e. .fill):
kkysen in 🌐 donna in rav1d on  kkysen/case-set-as-memset is 📦 v0.0.0 via 🦀 v1.71.0-nightly via 🐏 3GiB/63GiB | 108MiB/2GiB took 13ms
at 12:08:18 PM ❯ c b -r && hyperfine './target/release/dav1d -i ./tests/large/chimera_8b_1080p.ivf -l 1000 -o /dev/null'
   Compiling c2rust_out v0.0.0 (/home/kkysen/work/rust/rav1d)
    Finished release [optimized] target(s) in 0.81s
Benchmark 1: ./target/release/dav1d -i ./tests/large/chimera_8b_1080p.ivf -l 1000 -o /dev/null
  Time (mean ± σ):      1.692 s ±  0.010 s    [User: 15.333 s, System: 0.688 s]
  Range (min … max):    1.679 s …  1.709 s    10 runs

The PR and the benchmarks LGTM. At this point in time I don't think it's worth trying to further optimize to take advantage of alignment.

My two cents (after taking a quick look):

The PR has lots of commentary but the code to be merged does not. I don't think it is good to introduce small_memset without explaning why a regular memset isn't optimal. @kkysen please don't rely on folks reading the PR message, the code should be able to stand on its own.

I'm not sure results from one machine justifies rolling our own memset given that these low-level routines can vary greatly from one C library implementation to another, from one compiler to another, from one architecture to another. I would have used whatever the standard library provides absent any strong evidence to the contrary. That would save you from having to document your hand-rolled small_memset and keep things as simple as possible.

The replacement code for case_set is a lot more compact but I'm not sure it is as easy to grok. I would optimize for readability over compactness. This is a general comment. I've seen you fold/compact code with macros elsewhere and I personally don't think it is worth it. I realize this is a matter of taste but I don't like having to mentally expand macros in my head to understand what is going on.

If it was up to me, you'd take action on 2. Failing that, I think small_memset deserves a comment before merging.

I'll add the explanations from the PR description as comments in the code.  I had written that after opening the PR and forgot to go back and add it.

This definitely needs to be documented in the code. This is complex enough that no one is going to understand what this is doing or how to use it without comments. Otherwise it does look correct, afaict.

The PR has lots of commentary but the code to be merged does not. I don't think it is good to introduce small_memset without explaning why a regular memset isn't optimal. @kkysen please don't rely on folks reading the PR message, the code should be able to stand on its own.

I've now added the documentation from the PR description to the code (and a little bit more) in 15b4d6eafb61efc7077311b5fa5646f2dc1156c2.

I'm not sure results from one machine justifies rolling our own memset given that these low-level routines can vary greatly from one C library implementation to another, from one compiler to another, from one architecture to another. I would have used whatever the standard library provides absent any strong evidence to the contrary. That would save you from having to document your hand-rolled small_memset and keep things as simple as possible.

There does seem to be strong evidence to the contrary, though, from both my benchmarks on donna in Rust, and the benchmarks done in e3b5d4d044506f9e0e95e79b3de42fd94386cc61 on some other machine in C.  In both, the small powers of 2 optimization done in small_memset, the unsafe Rust case_set* fns, and the C case_set* macros are faster than just calling memset.  Had my benchmarks shown little difference between the implementations, I would've liked to choose memset, but that's not what I nor the dav1d authors observed.  Given they did they did this optimization for a reason and I'm able to reproduce the benchmarks, I think we should preserve them in Rust.

The replacement code for case_set is a lot more compact but I'm not sure it is as easy to grok. I would optimize for readability over compactness. This is a general comment. I've seen you fold/compact code with macros elsewhere and I personally don't think it is worth it. I realize this is a matter of taste but I don't like having to mentally expand macros in my head to understand what is going on.

I've tried to make it a bit simpler to read by using an as_array inner fn rather than the more confusing set! macro in 7cc882869e4bc73c840a1ced59d50ec4446e7b5f.  Is it also easier to read for you this way?  Even with the set! macro, I did already think it was far easier to understand than the previous case_set* code, which took a very long time to properly understand, and which I still do not fully understand (like the multiplying bytes by 1).

If it was up to me, you'd take action on 2. Failing that, I think small_memset deserves a comment before merging.

I've also documented small_memset in 15b4d6eafb61efc7077311b5fa5646f2dc1156c2 now.

It's common to have a specialized memset function in code like this (i.e., a video decoder) to maximize processing speed.

Sorry, just saw this.  It's pushed now: kkysen/case-set-as-memset.

@thedataking, I've made the optimization docs a lot more concise in b846093ac808b6c56de371d4fc3094143f053a7d.  Does that look better?

It's pushed now: kkysen/case-set-as-memset.

Thanks. I ran tests with some more sequences and CPU configurations. The specialized small_memset is consistently faster than the generic memset although the amount by which it is faster varies a bit.


Phone number styling

Please find all instances of the phone number for the company and follow the styling I've set for it in the sidebar.

Done in this commit 703c7528889862b88df90519fdcbe5720d507d52.


Is there anyway to use panic_semihosting with this crate?

Every example declares its own #[panic_handler] function.
When I use only panic_semihosting crate, I get an error stating:
  = note: arm-none-eabi-ld: /home/pi/.rustup/toolchains/nightly-armv7-unknown-linux-gnueabihf/lib/rustlib/thumbv7m-none-eabi/lib/libcore-c83b634e1f0ecbbe.rlib(core-c83b634e1f0ecbbe.core.2smtzb3g-cgu.0.rcgu.o): in function `core::panicking::panic_fmt':
          /rustc/043eca7f0b34d12e61c44206beca740628647080//library/core/src/panicking.rs:85: undefined reference to `rust_begin_unwind'

If I use both on the same time, I obviously get the duplicate error.
Right now, I have only been able to succeed with self-decleared panic-handler function.

I think the example declares its own panic_handler to avoid pulling in more dependencies, you don't need to define it yourself for this crate to work.


double-beep: Watch fortune.com

double-beep requests the watch of the watch_keyword fortune\.com. See the MS search here and the Stack Exchange search here.

fortune\.com has been seen in 1 true positive, 1 false positive, and 0 NAAs.

I'm going to close this PR. fortune.com is a legit site for Fortune magazine. It would be reasonable to watch the specific URL path that's in the question, but watching the domain is a bit excessive. There are also about 250 legit hits for the domain on SE.


Force panic=unwind for sysroot

This fixed #3313 partially for me. Previously, none of the miri tests could even build. Now they all pass :).
There is a lingering issue that I don't quite understand yet, which is that attempting to do miri test with another crate can still having aborting behavior.
The motivating example I have is https://github.com/PSeitz/lz4_flex, and how I found the issue to begin with. I can now build the test binaries, but now it immediately fails upon test execution with (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION) (Windows).
It appears something is still being build with panic="abort" somewhere, but adding it to the other cargo invocation did not seem to solve it
https://github.com/rust-lang/miri/blob/92110c2c9353d70db7146c661b087f53c033075d/cargo-miri/src/phases.rs#L115 somewhere after here I unconditionally put -Cpanic=unwind as a test but the abort still occurred. And to note, the tests run fine without touching the cargo config and running cargo test.

Can we set of build profile of "miri_sysroot" so that if people changed things about their "release" profile that just doesn't affect us?

Can we set of build profile of "miri_sysroot" so that if people changed things about their "release" profile that just doesn't affect us?

Probably? Now that you say that I think this PR probably isn't the way to go.


In map view, when going to fullscreen map, map disappears and just a detailed grid appears

An example is when in the camera folder, with say 300 photos, I go to map view and the map loads very fast displaying all the photo icons on the map. The next step in inconsistent in that it doesn't happen every time but it happens frequently and that is when clicking the map to go full screen view, the map and icons disappear and you are left looking at just a grid pattern. Pinching and zooming doesn't bring the map back nor does waiting for a minute or so. You then have to touch the map again to go back to the smaller view. Now if you touch the map again and go to the full view it will appear correctly. This can happen multiple times and I haven't been able to narrow it down to be 100% reproducible.
On map view, click the screen to go to full map view.
Only a grid appears.
Touch the screen again to go back to normal map view. Sometimes this doesn't work and you have to pinch and zoom, then click again to return to normal map view.
The app never crashes and other features work normally.
I expect the normal map go to full screen map view, every time, when clicking on the map.
Aves version: 1.6.4-play (Build 70)
Flutter version: 2.10.4 (Channel stable)
Android version: 12 (SDK 32)
Android build: SP2A.220405.004
Device: Google Pixel 6 Pro
Google Play services: ready
System locales: en_AU
Aves locale: system -> en
Installer: com.android.vending

Thanks for the report.
Sadly, I'm already aware of it and I don't have a solution at the moment. I believe it's a bug in the framework I'm using.
Related bugs:

https://github.com/flutter/flutter/issues/28493
https://github.com/flutter/flutter/issues/40284

Ok thanks. Hopefully this will formalise the bug on Aves and other people
won't need to add it again.
On Mon, 25 Apr 2022 at 12:11, Thibault Deckers @.***>
wrote:

Thanks for the report.
Sadly, I'm already aware of it and I don't have a solution at the moment.
I believe it's a bug in the framework I'm using.
Related bugs:

flutter/flutter#28493
https://github.com/flutter/flutter/issues/28493
flutter/flutter#40284
https://github.com/flutter/flutter/issues/40284

—
Reply to this email directly, view it on GitHub
https://github.com/deckerst/aves/issues/241#issuecomment-1107991091, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AVNKTEJYI6WT3VOND473J43VGX5MHANCNFSM5UHDXL7A
.
You are receiving this because you authored the thread.Message ID:
@.***>

The good news is that upgrading to the latest version of the framework (Flutter v3.0.0) fixes this. The transition is still glitchy sometimes, but at least the map doesn't disappear.
The bad news is that the map is now completely broken on older devices (API <=22).
Related bug: https://github.com/flutter/flutter/issues/103630
So I'm delaying the current release of Aves, while I ponder whether to downgrade or wait for a patch in the framework.

Reopening. The previous workaround no longer works with the latest version of Flutter -_-
Native plugin issues are still popping up with Flutter 3:

https://github.com/flutter/flutter/issues/103686
https://github.com/flutter/flutter/issues/107313

On the plus side, Google Maps layers are now working again on Android Lollipop (API 21 and 22).


Clean up terse or misspelled exception messages in ODBC backend

For example:
"Commiting"
"into type pre_fetch"
"Binding"

None of these seems to be present in the latest version, so I assume this had been already done.


potential null pointer in condition; AYAI9l8k5Irk9_td-cXb

Description
This PR fixes a sonar finding: https://sonarcloud.io/project/issues?issues=AYAI9l8k5Irk9_td-cXb&open=AYAI9l8k5Irk9_td-cXb&id=apachecloudstack

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[x] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@DaanHoogland can you rebase and target it to the 4.16 branch?

done @nvazquez

Thanks @DaanHoogland
@blueorangutan package

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 3104

@blueorangutan test centos7 vmware-67u3

@nvazquez a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests

Trillian test result (tid-3848)
Environment: vmware-67u3 (x2), Advanced Networking with Mgmt server 7
Total time taken: 35855 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr6237-t3848-vmware-67u3.zip
Smoke tests completed. 92 look OK, 0 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

@rohityadavcloud , before we merge, how/where do we see the sonar score improve? ;)

LGTM

@DaanHoogland let me explore how we can setup per-PR sonar build/analysis runs. For now, you'll need to build and upload the quality stats (a jacoco xml or csv file). I can do that manually once the PR passes, alt you can create a dummy org for yourself and upload manually.

@DaanHoogland ran another build/run for the sonar/jacoco analysis, you can check the issue in say about an hour if it shows up as resolved on the dashboard. I'll setup a daily run on main branch in Jenkins (soon) so sonar gets updated, for per-PR integration it requires setting up a Github secret - which I'll explore if it's at all possible.

great, it shows as 'closed' now


Added "files" to package.json

This PR adds some more files to: https://github.com/ngrok/ngrok-nodejs/pull/100 from @neonexus
> npm pack
npm notice
npm notice 📦<EMAIL_ADDRESS>npm notice === Tarball Contents ===
npm notice 2.5kB  CHANGELOG.md
npm notice 3.3kB  CODE_OF_CONDUCT.md
npm notice 595B   CONTRIBUTING.md
npm notice 11.4kB LICENSE-APACHE
npm notice 1.1kB  LICENSE-MIT
npm notice 13.7kB README.md
npm notice 36.2kB index.d.ts
npm notice 19.7kB index.js
npm notice 2.0kB  package.json
npm notice === Tarball Details ===
npm notice name:          @ngrok/ngrok
npm notice version:       0.9.0
npm notice filename:      @ngrok/ngrok-0.9.0.tgz
npm notice package size:  22.2 kB
npm notice unpacked size: 90.5 kB
npm notice shasum:        ab9d4dc3e22316cd28155533def5f73050e819ce
npm notice integrity:     sha512-5Wn/wIlRTgPK6[...]JaCQYLcUO7C3Q==
npm notice total files:   9
npm notice
ngrok-ngrok-0.9.0.tgz

The README and package.json are automatic, and don’t need to be included in the “files” listing.

The README and package.json are automatic, and don’t need to be included in the “files” listing.

Aye, just being explicit.

The README and package.json are automatic, and don’t need to be included in the “files” listing.

Aye, just being explicit.

@bobzilladev You know, I appreciate being explicit for a few reasons, I still have to ask: is adding the name of the file that is being read, to determine what files to include TRULY necessary? "Hey bro, I heard you like package.json..."

I like that files has a list of everything that will be packaged 😄

Fair enough.
On the plus side, this small addition dropped the package size from 1.03 MB in 149 files, down to 91KB and 9 files. MASSIVE improvement!


Failed to get registration from op code RANDOM_STANDARD_NORMAL

Hi,
I modified the official micro speech example of tflite-micro to run inference with a custom (VAE) Variational Auto Encoder model on linux_x86_64_default. After replacing the tflite file and modifying the micro_speech_test.cc, the make build returns the following error message:
Didn't find op for builtin opcode 'RANDOM_STANDARD_NORMAL' version '1'. An older version of this builtin might be supported. Are you using an old TFLite binary with a newer model?

Failed to get registration from op code RANDOM_STANDARD_NORMAL

So it seems that the „RANDOM_STANDARD_NORMAL“ is not implemented – at least it does not appear in all_ops_resolver.cc.
I am using TensorFlow version 2.9.1 and the latest version of tflite-micro framework from 15.8.2022. This operation (= generating random numbers) would be important for several other applications too! Is there some related work in progress or could anyone provide me with an alternative?
Best regards,
Christoph

@advaitjain How we can add custom ops like RANDOM_STANDARD_NORMAL to the all_ops_resolver.cc?
@christophsiegl did you find any solution for this issue?

@deepaksharma36 I did not find any solution so far. But there exists a porting reference which describes how to port TF Lite opcode to TF Lite Micro: https://github.com/tensorflow/tflite-micro/blob/main/tensorflow/lite/micro/docs/porting_reference_ops.md
So far I have not tried to do this by myself ...


Gas reporting

What was wrong?
We weren't tracking how much gas is used in our integration tests.
How was it fixed?
We track it now.
To-Do

[ ] OPTIONAL: Update Spec if applicable
[ ] Add entry to the release notes (may forgo for trivial changes)
[x] Clean up commit history

Codecov Report

Merging #693 (7a98298) into master (edba011) will decrease coverage by 0.07%.
The diff coverage is 85.33%.

:exclamation: Current head 7a98298 differs from pull request most recent head 9755dd5. Consider uploading reports for the commit 9755dd5 to get more accurate results

@@            Coverage Diff             @@
##           master     #693      +/-   ##
==========================================
- Coverage   82.12%   82.05%   -0.08%
==========================================
  Files         125      125
  Lines       10849    10881      +32
==========================================
+ Hits         8910     8928      +18
- Misses       1939     1953      +14

Impacted Files
Coverage Δ

crates/analyzer/src/traversal/functions.rs
96.00% <ø> (-0.03%)
:arrow_down:

crates/abi/src/builder.rs
93.05% <33.33%> (-2.60%)
:arrow_down:

crates/analyzer/src/db/queries/functions.rs
90.37% <64.00%> (-3.88%)
:arrow_down:

crates/analyzer/src/namespace/types.rs
72.65% <100.00%> (+0.61%)
:arrow_up:

crates/analyzer/src/traversal/call_args.rs
95.65% <100.00%> (+0.98%)
:arrow_up:

crates/analyzer/src/traversal/expressions.rs
80.76% <100.00%> (-0.19%)
:arrow_down:

crates/lowering/src/mappers/functions.rs
99.41% <100.00%> (+<0.01%)
:arrow_up:

crates/lowering/src/mappers/module.rs
85.36% <100.00%> (+0.18%)
:arrow_up:

crates/parser/src/ast.rs
88.53% <100.00%> (+0.06%)
:arrow_up:

crates/parser/src/grammar/functions.rs
90.52% <100.00%> (+0.12%)
:arrow_up:

... and 5 more

Continue to review full report at Codecov.

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


Better indent migrate warnings and errors

Problem
Migrate warnings and errors formatted in lists have no indentation after the first line.

Suggested solution
Format these messages with indentation after the first line:
- Lorem ipsum dolor sit amet consectetur adipiscing elit, urna consequat felis
  vehicula class ultricies mollis dictumst, aenean non a in donec nulla.
- Phasellus ante pellentesque erat cum risus consequat imperdiet aliquam,
  integer placerat et turpis mi eros nec lobortis taciti, vehicula nisl litora tellus
  ligula porttitor metus.

The wrap width would need to be based on the terminal width.
Alternatives
Leave things as they are.

Hi there,
As part of our effort to clean up our GitHub repo, we’re closing this issue to help focus on features and improvements that align with our focus areas and those of our community.
This issue was originally created for internal tracking purposes, but if you feel this is important to you, feel free to reopen the issue and get like-minded users to upvote as we will prioritize fixing issues based on community interest.
For more insight into our priorities and how we’re thinking about the future of Prisma, please see our blog post: https://www.prisma.io/blog/prisma-orm-manifesto.
Thank you for your understanding and support!


To discuss: Strandard handling of service version

We are missing a standard handling of service versions. At this time developers have to make custom logic and beans to implement the versioning in their way causing everybody writing the same code and config repeatedly.
I would like to discuss about handling service versioning in

Authoring a service;

allow defining service version as a bootstrap property
use the version number as webapp context to prefix version number to all services automatically
the version number will not be prefixed to actuator if its enabled.

Discovery client;

Send service version as appropriate property if the actual discovery client supports it, otherwise fallback to serviceName-versionNumber convention as a serviceId

Config client;

Lookup up config using the specific service version, fallback to nearest or non version config if specific version is not found..

And further projects that can use the version property.

Is this specifically to do with versioning APIs?

Yes. I reckon every project will need to version the API and at this time they have to create custom solutions for it. I hope ultimately, we may define/choose conventions for versioned service registration, discovery, central configuration. But to begin with, the bootstrap should let services define their version along with the application name as a separate property.

Anything we do would have to work across multiple systems: eureka, consul, zookeeper, cloudfoundry and from incubator: kubernetes and etcd. I think your request has some specifics to zuul. Any specific strategy will not be a silver bullet to everyone, so whatever happens it needs to be flexible.

Yes, the specific versioning strategies will be contained in the relevant implementations. But as the first base, we have to define the optional version-number property for the bootstrap. The implementation can be updated to use this property if its defined later/gradually and we can discuss each implementation separately.
Until we change the implementations, there will be no impact anywhere.

I'm also saying that any specific strategy (ie version number in URL or versioned accept header) won't be ideal for everyone, that will have to be generic.

I am also not sure the enforcing these versioning patters (with context root, and service name) will be necessary for everyone.

I am of the opinion that without the version handling, the projects are not production ready and sort of incomplete. One must research for most popular way for version handling and match it with their needs and finally be forced to build it in. We can provide a starting point.
Yes, I agree that everybody may not be using the same strategy. I am just after providing some defaults, which will be the most sensible or useful to most of the users.
To keep it simple and limit the scope, for the service implementations, I proposed adding support for URL based versioning and using webapp context to force in the version number. But, also ensuring that users can override these defaults with their configuration just like everywhere else on Spring boot.  If this makes sense, we may just choose some other handling as default.
Similar choices will need to be made for every implementation that may need to use the version number and can be discussed one at a time.

I am of the opinion that without the version handling, the projects are not production ready and sort of incomplete.

That's a valid opinion. Assuming "the projects" means this one or other spring cloud project, they are in production in various places already.
Some kind of versioning scheme would be necessarily opt-in.


Improper HTML rendering

Expected behaviour
I get emails chock full of HTML, pictures, and formatting from Home Depot. On my desktop client, Thunderbird, everything renders fine.
Actual behaviour
I cannot see all of the content in the body of the email in K9. There is also no way to scroll to the right where the information is located.
Steps to reproduce

Get a Home Depot email
Notice you cannot pan images to the right and see content
See this message:
INBOX)42260.txt

Environment
K-9 Mail version:
5.008
Android version:
5.1.1
Account type (IMAP, POP3, WebDAV/Exchange):
IMAP

Do you have Display->Auto-fit messages selected.
In the meantime I signed up for their spam, so if they send another broken e-mail I'll have a go at debugging it.

I tried both settings and it didn't change
On April 1, 2016 8:01:40 AM CDT, Philip<EMAIL_ADDRESS>wrote:

Do you have Display->Auto-fit messages selected.
In the meantime I signed up for their spam, so if they send another
broken e-mail I'll have a go at debugging it.

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/k9mail/k-9/issues/1244#issuecomment-204390051

I can forward you the offending message and you can hopefully see it. If I get an actual email from you privately I can do that. I think it would help to see the rendering issue firsthand. In the one I am thinking of, there is a coupon to the right of a promotion image. The coupon cannot be seen or clicked on. Other things to the right are also invisible.

Huh, this looks like a HtmlCleaner issue in light of recent stuff.
Assigning to @cketti as he's looking at using JSoup.

We have made quite a few changes related to HTML rendering. Please create a new issue if this is still a problem.