Facing kuala-grpc error with statusCode: UNIMPLEMENTED

Hi Team,
I am facing a issue while connecting to kuksa-val-server using kuksa-client with grpc protocol.
I have kuksa-val-server up and running and exposed ports please see in the below screenshots:

See the exposed ports in the below screenshot:

I am trying to connect to kuala-val-server using kuala-client using VSSClient as you can see in the below screenshot.
While trying to connect with python code:
from kuksa_client.grpc import VSSClient

with VSSClient('localhost', 50051) as client:
    current_values = client.get_current_values([
        'Vehicle.Speed',
    ])
    print(current_values['Vehicle.Speed'].value)

I am getting error with grpc statusCode: 12 (UNIMPLEMENTED) as shown below in the screenshot:
kuksa_client.grpc.VSSClientError: ({'code': 12, 'reason': 'unimplemented', 'message': ''}, [])

NOTE: I am able to connect to kuksa-val-server through “ws” protocol by using code shown in the screenshot below:

Thanks in Advance !

Hi,
i understand this is a bit confusing currently. Basically  there are not all combinations between client and server that work.  Maybe this helps

Server
Client
Py API
Comment

kuksa-databroker  (Rust)
databroker-cli or kuksa-client
kuksa-client, all variants , sync or async recommended
Recommended for new designs

KUKSA val-server (C++)
kuksa-client or [kuksa-viss-client](https://pypi.org/project/kuksa-client/ (deprecated)
Websocket: kuksa-client only threaded API  , Websocket and GRPC:  kuksa-viss-client  (deprecated)

An important thing is that val-server GRPC != databroker GRPC currently. In a nuthshell, it depends where you are coming from:
If you start fresh, use databroker + kuksa-client. Don't use the kuksa-val compatible threaded API, as that is the slowest. The quickstart will get you, well, started
If you have a dependency on val-server, use Websocket with kuksa-client. That is better tested than the GRPC version of val-server. By using the threaded API, it will be easy to later switch to databroker, if it fulfils your need
Maybe interesting:: If the reason for val-server is authorisation: We are working on bringing this feature - in an improved way -  to databroker currently.
If none of the solutions quite fit, what you are trying to do, please let us now, what your requirements are. Especially if you have something currently only fulfilled by val-server.
@lukasmittag : Maybe we should put something like this in the differences documentation

Thank you so much for your help @SebastianSchildt
That was crystal clear explanation and very helpful. Now its very clear to decide what to use.
I have started kuksa fresh and currently exploring. I am flexible to use whatever is recommended. I tried using kuksa-databroker with kuala-client python API but facing a issue.
I need 1 more help regarding the same.
I have tried the things listed on kuksa quickstart page. Below are the some use cases that I have tried from the kuksa quickstart page:
1. Used docker to run kuksa-databroker and kuksa-client
Ran kuksa-databroker with docker using below command
docker run -it --rm --net=host ghcr.io/eclipse/kuksa.val/databroker:master
Ran kuksa-client with docker using below command
docker run -it --rm --net=host ghcr.io/eclipse/kuksa.val/kuksa-client:master --port 55555 --protocol grpc --insecure
RESULT:  SUCCESS - Working fine and able to fire commands through kuksa-client on kuksa-databroker
2. Used docker to run kuksa-databroker and tried connecting with kuksa-client with python API
Tried running kuksa-databroker with docker using below 2 commands -
i) First tried with the simple docker command which is given on kuksa quickstart then tried kuksa-client with the python code given below.
docker run -it --rm --net=host ghcr.io/eclipse/kuksa.val/databroker:master
Used below kuksa-client python code to connect with kuksa-databroker
from kuksa_client.grpc import VSSClient
from kuksa_client.grpc import Datapoint

import time

with VSSClient('<IP_ADDRESS>', 55555) as client:
    for speed in range(0, 100):
        client.set_current_values({
            'Vehicle.Speed': Datapoint(speed),
        })
        print(f"Feeding Vehicle.Speed to {speed}")
        time.sleep(1)
print("Finished.")

NOTE: Tried with changing IP address in VSSClient as well. i.e. Used "<IP_ADDRESS>:55555" instead "<IP_ADDRESS>:55555".
with VSSClient('<IP_ADDRESS>', 55555) as client:
RESULT:   ERROR - Getting below error as
kuksa_client.grpc.VSSClientError: ({'code': 14, 'reason': 'unavailable', 'message': 'failed to connect to all addresses'}, [])
Please see screenshot below

ii) After that tried docker command which will publish port 55556 and tried setting up the environment variables to change the ip address and port of the container then tried kuksa-client with the python code given below.
docker run -it --rm --env KUKSA_DATA_BROKER_ADDR=<IP_ADDRESS> --env KUKSA_DATA_BROKER_PORT=55556 --net=host ghcr.io/eclipse/kuksa.val/databroker:master --publish 55556:55556
Used below kuksa-client python code to connect with kuksa-databroker
from kuksa_client.grpc import VSSClient
from kuksa_client.grpc import Datapoint

import time

with VSSClient('<IP_ADDRESS>', 55556) as client:
    for speed in range(0, 100):
        client.set_current_values({
            'Vehicle.Speed': Datapoint(speed),
        })
        print(f"Feeding Vehicle.Speed to {speed}")
        time.sleep(1)
print("Finished.")

RESULT:   ERROR - Getting below error as
kuksa_client.grpc.VSSClientError: ({'code': 14, 'reason': 'unavailable', 'message': 'failed to connect to all addresses'}, [])
Please see screenshot below

Is there anyway to connect from python API to the kuksa-databroker which is running in the docker container ?
Or I will have to run kuksa-databroker locally and then try to connect via kuksa-client python API ?
Please Suggest.

Hey,
I don't know if your screenshots are correct, but they seem to both use 55556 as port. Else it looks good and should work I think.

Maybe some issue with your network setup. I do see you are using
docker run -it --rm --env KUKSA_DATA_BROKER_ADDR=<IP_ADDRESS> --env KUKSA_DATA_BROKER_PORT=55556 --net=host ghcr.io/eclipse/kuksa.val/databroker:master --publish 55556:55556

You should not combine --publishwith --net==host ( I think it will ignore --publish , put also not even sure it is in the correct place. Also do nit use this --env KUKSA_DATA_BROKER_ADDR=<IP_ADDRESS> , because default is <IP_ADDRESS> (and when connecting from outisde container depending on the docker network setup it is not necessarily the case that the origin ist <IP_ADDRESS> from the perspective of the container.
I think the root cause is, you are using "Docker Desktop" (at least judging from the icon in the menu bar). I have no experience with it, but the documentation https://docs.docker.com/network/host/ says

The host networking driver only works on Linux hosts, and is not supported on Docker Desktop for Mac, Docker Desktop for Windows, or Docker EE for Windows Server.

I can say docker --net=host works for Mac OS on  https://rancherdesktop.io
With docker desktop, try starting the databroker like this
 docker run -it --rm  --publish 55556:55556 ghcr.io/eclipse/kuksa.val/databroker:master  --port 55556

I think you should be able to connect from host using <IP_ADDRESS>:55556

Thank you so much @SebastianSchildt
It’s working for me with the docker command provided above. Also thanks for quick replies and other shared knowledge.
I think we can close this issue now as I am good to move forward. Please give me go ahead to close this issue or you can close it.
Thanks again !

Good, that it works for you now. I will close this, feel free to open a new issue in case of problems


xtensa: define arch_proc_id() for xtensa

This interface is currently defined in the soc. Make it more generic and define it on the architecture level so we can use it elsewhere.

xtensa: add arch_proc_id()
intel_adsp: use arch_proc_id() instead of local function

Funny how many tests pass while some others don't compile
We all know about "DLL Hell", what is corresponding name for .h files?

#41543

c /__w/zephyr/zephyr/arch/arc/core/offsets/offsets.c
In file included from ../../../../../../include/zephyr/arch/cpu.h:12,
                 from ../../../../../../include/zephyr/kernel_includes.h:33,
                 from ../../../../../../include/zephyr/kernel.h:17,
                 from /__w/zephyr/zephyr/arch/arc/core/offsets/offsets.c:25:
../../../../../../include/zephyr/sys/arch_interface.h:436:24: error: 'arch_proc_id' declared 'static' but never defined [-Werror=unused-function]
  436 | static inline uint32_t arch_proc_id(void);
      |                        ^~~~~~~~~~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.

Funny how many tests pass while some others don't compile

the issue is clear, this is only a multi-core thing so it works fine on non-smp, other SMP architectures are looking for the implementation of the same interface, which I did not put in, this might end up as an xtensa thing after all.


REST API: optional input

Certain fields of input objects need to be optional as they are returned on GET but not neded on POST or PUT. This should be visible in the API description.
A very special case is PUT on processes/{id}/approve - there one only needs the id (present in the path) but has to provide an empty JSON object ({}), otherwise a 500 is the result.

@Weiser-R I adjusted the documentation with comments and required fields. I also removed the json input from the approve resource.


about the wide feature and deep feature

first of all. thanks for your work. I am a little confuse about the split of the wide and deep feature. embeddings_cols, continuous_cols, standardize_cols, wide_cols, crossed_cols, already_dummies. embeddings_cols is the category feature. continuous_cols is continuous feature. what's the different between standardize_cols and continuous_cols? the wide_cols feature is similar to the category feature. crossed_cols I know you want to get the interaction feature.how to select the element to constitute interaction feature? thanks in advance.

Hi @Usernamezhx
ok, let me explain. If you go here:
https://github.com/jrzaurin/Wide-and-Deep-PyTorch/blob/master/prepare_data.py#L52
you will read the following:
    embeddings_cols: List
        List containing just the name of the columns that will be represented
        with embeddings or a Tuple with the name and the embedding dimension.
        e.g.:  [('education',32), ('relationship',16)
    continuous_cols: List
        List with the name of the so called continuous cols
    standardize_cols: List
        List with the name of the continuous cols that will be Standarised.
        Only included because the Airbnb dataset includes Longitude and
        Latitude and does not make sense to normalise that

The functions in prepare_data.py are highly customised to the problem in particular. So, given this input, and for the airbnb dataset:
continuous_cols = ['latitude', 'longitude', 'security_deposit', 'extra_people']
standardize_cols = ['security_deposit', 'extra_people']

what will happen is that while 'security_deposit', 'extra_people' will be standarised, 'latitude', 'longitude' will not (because it does not make sense.
Regarding to the other column-type inputs, if you go here:
https://github.com/jrzaurin/Wide-and-Deep-PyTorch/blob/master/prepare_data.py#L128
you will read the following:
    wide_cols: List
        List with the name of the columns that will be one-hot encoded and
        pass through the Wide model
    crossed_cols: List
        List of Tuples with the name of the columns that will be "crossed"
        and then one-hot encoded. e.g. (['education', 'occupation'], ...)
    already_dummies: List
        List of columns that are already dummies/one-hot encoded

The wide columns are normally one-hot encoded and then pass through the model. However, there might be some columns that are already one hot encoded, and I call them already_dummies.
 The answer is that you have to experiment, there is no rule for that. For example, if you have a couple of features and you think that including their relation might add useful information, then is probably useful if you "cross them".  For example, directly from the tensorflow tutorials: "...If you have a feature 'favorite_sport' and a feature 'home_city' and you're trying to predict whether a person likes to wear red, your linear model won't be able to learn that baseball fans from St. Louis especially like to wear red..."
Let me know if this helps

Thank you very much for your patiently reply.


Question regarding other models (apart from sciner/scire-scibert)

Hi, I'm relatively new to the topic of relation extraction (RE) and I have a few questions you might be able to help with:

As far as I understand it, each RE-model is a classifier trained specifically on the labels from the dataset; That is, if I need other relation-types, do I need to retrain the whole network? Or is it possible to only retrain the head of the network?
Are the RE-models using the previously determined named entities with or without label? Could you use the output of an ACE-NER model as input for a SCI-RE model?

I hope you have the time to answer these questions, if not, I would also appreciate a link to a paper/website explaining these issues. Thanks for your work!

Hi,
I. I haven't done any experiments about switching relation-types. You can search for papers about transfer learning and continuous learning.
2. Since the ACE-NER type contains ['FAC', 'WEA', 'LOC', 'VEH', 'GPE', 'ORG', 'PER'] and the SCI-NER type contains ['Method', 'OtherScientificTerm', 'Task', 'Generic', 'Material', 'Metric']. The NER model for ACE cannot be used for SCI. For example, the ACE-NER model regards the Method entity as no type.  Specially, the CoNLL03-NER type contains [MISC], which means other-type entities. Hence, the CoNLL03-NER may contains more possible entities.

Thank you very much for the answers, you helped me very much :)


Oops! Something went wrong. Please try again later

I keep getting this error: "Oops! Something went wrong. Please try again later" when clicking on my map in Basic JavaScript. Also the site seems generally slow and has been for over a week.
Thanks
Dave

We recently deployed an update to the site intended to resolve the speed issues, but it may cause temporary slowdowns while migration occurs. Closing as a duplicate of #6901. Thanks and happy coding!


New Sensors not shown

Hello,
today we got a new Solar Unit added to our ETA System. The new Sensors wre shown in the API  under  /user/menu but are not shown in the ETA Integration. How can i retrigger the inital search for available entities?
Thanks for your help

Hi,
The integration currently doesn't support scanning for new ETA endpoints, because that is a very minor edge case, which won't be needed by most users.
I will see if I can find an easy way to implement this, but it may take until the end of the week, maybe even longer.
If you don't want to wait you can remove the integration and add it again to make it detect the new endpoints. Unfortunately this means you will also have to recreate all dashboards/automations in HA.


[SUGGESTION] Add a button to open the magizmo in the installer

Is your feature request related to a problem? Please describe.
Going to the desktop is too much for me
Describe the solution you'd like
I want a button that opens the new freshly installed magizmo :3
Maybe down there next to the Finish button

Additional context

Done. In the next update there should be a toggle for that in the installer/updater


Adding support in VS Code extension to submit jobs to Azure Quantum

Initial changes for the Azure Quantum job submission feature from VS Code

/azp run


Memory leaks

I've compiled examples provided with code, and valgrind shows memory leaks for all of them (both master and development versions).
valgrind_report.txt

Fixed. Thank you for reporting this issue.


Set an explicit timeout

does this make sense? I am just guessing out of the blue trying to fix the qa2 failures..


Possibility to use plugin for MatterMost

I came here after looking at different different Cypress test reporters for communications tools, and even building my own, which looks something like this:

but this is for MatterMost
However, I am interested if I could make slack-ctrf work for MatterMost too, as it really seems to outline the most important metrics for my tests, which I could also combine with other information that I already use.
From what I can tell, the only difference might be the message formatting, and replacing the incoming webhook with a MM one.

A MatterMost plug-in is a great idea, it will be published separately to the slack plugin. Please can you add a post to ctrf discussions with a plug-in request and we'll discuss further - https://github.com/orgs/ctrf-io/discussions

A MatterMost plug-in is a great idea, it will be published separately to the slack plugin. Please can you add a post to ctrf discussions with a plug-in request and we'll discuss further - https://github.com/orgs/ctrf-io/discussions

Great, glad to hear that! I will write a post there in the discussions, and please let me know if you need any help with making the plugin happen.


DNSLink chaining not resolving properly

What we did
I assume the extension is using this lib under the hood. IPFS Browser extension 0.11.0. The URL in browser (Brave) is ipns://wiki.polkadot.network , and I was also able to reproduce the error using a HTTP gateway (https://ipfs.w3f.community/ipns/wiki.polkadot.network).
Error
ipfs resolve -r /ipns/wiki.polkadot.network: could not resolve name: "wiki.polkadot.network" is missing a DNSLink record (https://docs.ipfs.io/concepts/dnslink/)
Expected behavior
browser -> _dnslink.wiki.polkadot.network -> _dnslink.polkadot-wiki.w3f.services -> resolve the wiki's hash
DNS TXT values
❯ dig +short TXT _dnslink.wiki.polkadot.network
"dnslink=/dnslink/polkadot-wiki.w3f.services"

❯ dig +short TXT _dnslink.polkadot-wiki.w3f.services
"dnslink=/ipfs/QmdncfsVm2h5Kqq9hPmU7oAVX2zTSVP3L869tgTbPYnsha"

Any misconfigurations on our part? Pretty sure we're doing it exactly how its described here. @ironoa

Hello, seems like the issue still needs to be triaged, thanks


No more sugar controller in upstream eventing

Signed-off-by: Matthias Wessendorf<EMAIL_ADDRESS>
Changes

remove sugar controller related snippets

/kind

Fixes #

Release Note

Docs

/approve


ss standardizer overhaul, sqtl adaptation of tensorQTL from gtex, wip

TBD:

check/fix dup for pseudo vcf
test the output ss with MWE
a mechanism to handle TARGET file, maybe remove from the yml but take our output by default?

The changes in each unit were tested. But the process from tensorQTL to standardized output still needs testing.
Will move on to the mock run of TensorQTL with the intron cluster first. Then come back for the overall testing.

Added the sqtl pipeline from gtex to suit our needs. It only works with leafcutter for the time being, need to develop the psi part after psi was done.

Tested with xuanhe's output, the procedure works mechanically. But the cis.map_permutation and cis.map_cis function both produce NaN result with the given data.


Feature/register component

Description
Basic setup for register component (form fields and basic 'pagination' split). Also rewriting the basic test for each component (snapshot testing made less sense right off the bat)
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Change Status

[x] Complete, but not tested (may need new tests)

How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] There are no merge conflicts

 Register Component (form)


Improve the localization handling using i18next-vue

I've built i18next-vue lib from the source and had to remove the usage of es6 import/export in that file. Instead, I tried using global variables and the Vue object provided by vue.js lib, which allows us to use i18next-vue in our app.

Added i18next.js module
Updated the app to use this new module

Good job @UtkarshSiddhpura , it's far better :+1:


Added the ability to auth via AppRole

Adds a new authentication method to allow auth via approle credentials. Useful when testing validity of approle credentials and access.

This is pending tests being written.


Readme: add commands to install dependencies on Debian and Fedora

Thanks! Let me know if you have other improvement suggestions :-)


Filter out package.documentation links to docs.rs itself

On e.g. https://docs.rs/crate/diesel/latest there's a "Documentation" link in the left-hand bar that just points to https://docs.rs/diesel. This is mainly shown for cases where a crate has external documentation, e.g. https://docs.rs/crate/diesel/0.13.0 which links to http://docs.diesel.rs/, so we should suppress showing it for cases that just link back to docs.rs.

mentoring instructions:

when loading the crate details from the database (in CrateDetails::new in web::crate_details) we also load documentation_url
here we want to ignore the documentation URL when it starts with https://docs.rs, so CrateDetails.documentation_url is None in this case
add a test for this, just on CrateDetails is fine

the interfaces already show the link only when there is an URL.


Add basic Charlieplexing scan

Hey, I just finished some basic initial code for the project.
There are some problems with the interrupt when using xpack's riscv-none-elf-gcc:

The gpio interrupt handler only runs once
The timer interrupt handler is so slow

Switching back to riscv-none-embed-gcc seems working, but the timer interrupt handler takes so much time that the main loop doesn't have enough time slice to execute.
Main changes:

Generate code from SDK
Add basic Charlieplexing scan

that is not matching coding style and unneeded

Did you mean commit 817425b? It seem nonsense but for quick testing. I'll remove it here and add changing brightness feature in another PR. How do you think?

Makefile changes

Makefile changes

954f786
4cece4e
d812e56
208b854
Which one?

Makefile changes

4cece4e

What coding style do you suggest?

I see many projects use the old style, but isn't it convenient to have this appending style? It could be

turned on/off a flag by commenting out a line
or add an end-line comment without affecting other flags.

@fcartegnie if there is no other change I think it is time to get this PR merge.

@fcartegnie if there is no other change I think it is time to get this PR merge.

You can't merge do & undos or fixs to those commits.
Please rebase -i and discard reverted and reverter code, and merge intra fix changes

You can't merge do & undos or fixs to those commits.
Please rebase -i and discard reverted and reverter code, and merge intra fix changes

Then force push or should I make a new PR?

You can't merge do & undos or fixs to those commits.
Please rebase -i and discard reverted and reverter code, and merge intra fix changes

Then force push or should I make a new PR?

use the force, luke

I could write a script to automatically download and generate StdPeriphDriver if this is considered as the optimal way.

Please keep StdPeriphDriver in the repository. I believe it would be a bad idea to have our repository depend on Code pulled in at build-time from an external source. That creates a dependency we don't want.
(admittedly I don't like the StdPeriphDriver code. I believe at some point we might want to fix/modify it.  Being able to fix it is an important reason to keep the code in our repository.)


Add tags for emphasis format.

@mitogh Nice work! :sparkles: I left a bunch of comments. Generally they are syntax (code style) fixes. Don't forget to add yourself as contributor in package.json as well! :clap:

Changes has been updated based on your feedback. Let me know your comments @IonicaBizau


Reflex Roadmap

This page is a living document outlining the major projects we're working on next for reflex 0.7.0. The projects are ordered more-or-less in the order we plan to complete them.
Feel free to comment to leave feedback or upvote any issues you'd like to see prioritized, and we welcome outside contributions for any issues.
Key Focus Areas
Stability: As we approach our 1.0 release, we're focused on making our core API stable and limiting breaking changes so Reflex can be a solid foundation for long-term projects.
Simplicity: We want to improve the out of the box experience so users can focus on their ideas rather than implementation. This includes building a 3rd party component ecosystem, as well as simplifying the APIs for many of our core components.
Speed: Reflex apps should be fast, both for the end user and for the developer. We have projects to make sure apps stay fast as they grow in size, and to improve the compile / hot-reload times so devs can iterate quickly when building.
Roadmap 0.7.0

[ ] Client Side Rendering (CSR) #3732
[ ] AG Grid Support
[ ] Builtin Auth
[ ] Reduce Dependencies
[ ] Modular Compiler
[ ] Improvements to ComponentState
[ ] Improvements to @rx.memo
[ ] Reduce hot reload times
[ ] Improve reflex init and run workflow
[ ] Improve Breakpoint Props

Roadmap 0.6.0 (Target Release: September 19 2024)

[x] Graphing Improvements
[x] Consistent Theming
[x] DataTable / DataEditor Improvements
[x] Responsive Support For All Props
[x] Decentralized Var Operations
[x] DiskStateManager to maintain state between reloads
[x] Move Chakra to Third Party

Roadmap 0.5.0 (Target Release: May 6, 2024)

[x] Substate Sharding https://github.com/reflex-dev/reflex/pull/2574
Save individual substates independently so Reflex apps stay performant as the state tree grows.
[x] Substate Access https://github.com/reflex-dev/reflex/pull/2678
Make it easier to access sibling substates
[x] Benchmarking Suite  https://github.com/reflex-dev/reflex/pull/2880
Internal benchmarks to track Reflex size and speed.
[x] 3rd Party Component Ecosystem https://github.com/reflex-dev/reflex/issues/2706
Ecosystem to publish and download third party components
[x] Loosen Requirements / Pydantic 2.0 Compatibility https://github.com/reflex-dev/reflex/pull/2796
Make Reflex more compatible with other Python libraries
[x] Support Bun on Windows https://github.com/reflex-dev/reflex/pull/2359
[x] Upgrade to Radix 3.0 https://github.com/reflex-dev/reflex/pull/3159
Update our core components to the new version of Radix

REF-2092
Please leave comments on what you think about this tentative plan.

Firstly, I :heart:  like the plans and think the three main goals are a good focusing point for 0.5.0.
One minor drop of bitterness (at least for my current code):
Remove the middleware :scream_cat: ? I would need new ideas for authorization then. I do not want to rely entirely on the routing and if-statements. What are the ideas how authorization (I don't mean solely authentication here) might be added to an app?
Other things that middleware is good for: Checking when the last action of a user had been carried out. Conditionally having fine-grained influence on states. Debugging event orders by mere printing.
Maybe there are plans to have a similar mechanism that replaces this nice (not tremendously over-documented ;) feature?

Awesome, love to see how reflex evolves! :rocket:
Is Pydantic v2 fixed on this roadmap? If so, I would offer my help regarding SQLAlchemy support and adjust my affected PRs to pydantic v2.

@abulvenz Thanks for the feedback - I will modify that project, we don't want to break any existing functionality.
We want to move certain internal events like the initial state hydration away from using middleware, but we will still have easy ways to support other use cases.

@benedikt-bartscher Yes we either want to upgrade to Pydantic v2.0 for the performance and compatibility benefits
In the long-term we can potentially remove the Pydantic dependency altogether and use Python dataclasses, since we don't use many of its features anymore internally. Though that would require moving away from FastAPI and SQLModel, so not planned anytime soon.

Hi everyone, as I have said before. I have been programming for a short time, I did a Python Bootcamp and for the final project I used Reflex when it was called Pynecone. I could have used Django or Flask, but I chose Reflex because I think it will have a future.
What would I like from Reflex 1.0?
Let's see if I can explain. I would like Reflex to be from a base agnostic of any external framework, using as it can be done now 100% html and css. So as not to depend on third party libraries, such as Astro (Javascript).
From there, when starting the project the user will be asked whether or not to use a framework or not, for example Radix-Ui, Taildwind.
Then the ability to share components with (3rd Party Component Ecosystem) seems to me great.
Good job to all the team, long life to Reflex.
Best regards.

Perhaps these thoughts help you in finding the right direction for your product.
Started to use reflex because:

wanted same coding language as most ML frameworks -> python
wanted a low code tool that's flexible. Using little code to achieve common use cases with the possibility to customize easily
wanted frontend and backend in one, allowing for a single code base that can handle auth and user management
used streamlit before, but can't build any serious project with it because customizing look of components is a pain, page randomly refreshes deleting existing state, weird logic where the code is rendered top to bottom making common use cases difficult to implement (or at least much different)
need to be able to self-host it for GDPR critical use cases

Like it even more since I started:

wrappers of 3rd party libraries like motion
askInkeep on discord
team on discord is very responsive
hosted version for non GDPR criticial use cases
lots of inbuilt components that actually do work out of the box such as file upload or scrollable area

Really like to see the "Simplicity" point here. box system is really a pita :) - thank you for Reflex!

@benedikt-bartscher Yes we either want to upgrade to Pydantic v2.0 for the performance and compatibility benefits
In the long-term we can potentially remove the Pydantic dependency altogether and use Python dataclasses, since we don't use many of its features anymore internally. Though that would require moving away from FastAPI and SQLModel, so not planned anytime soon.

@picklelo In terms of improving performance - I'm not sure how much Javascript next.js (which seems to be under the hood) uses, but have you seen Astro? Seems to be super fast because it renders static JS components as HTML. Might be a reach, but maybe there's some way to include something similar at build-time?

Thanks @picklelo, the roadmap looks awesome! I just wanted to chime in as someone who's used Streamlit in the past and has suffered from its limitations. I believe what makes Streamlit popular among the ML community is the new "AI" features they added, like the ability to build a chat UI which looks nice. I saw the chat UI demo using Reflex and I thought it would be much better if more time was spent on that. It surely would attract people who want to build fancy chat UIs. Currently, Streamlit does it in a way that's not performant but looks nice, so the higher-ups often like it. If there was some theming for chat UI, messages, etc., I think it would help Reflex a lot. Just a thought!

Possibilities of building a desktop version of reflex would be a game changer.. something on the lines of stlite.
I am thinking of trying out Briefcase, but not getting time.. Sure things may not be as straight forward, as Briefcase is all native-desktop friendly.
Atleast, perhaps an effective blog post detailing a success-story around this would definitely help the community.. Please kindly consider.

The initial boot-up of the app and hot-reload are both very time-consuming.. Sorry to keep comparing with Streamlit, but the hot-reload is almost instantaneous with it. I am finding it painful to maintain a growing streamlit app, and seeing value with migrating to Reflex, hence the ask/request/plead..

@pnsvk Okay, stick to Streamlit then. Changes in Streamlit are instantaneous because Streamlit doesn't compile (unlike Reflex which compiles to performant HTML+CSS+JS code). Streamlit was based on poor design decisions (e.g., every interaction with any widget reloads the entire page, wtf?). Recently, they've tried to fix some of them (e.g., local reloading) but the overall project is still a mess.

Small bump for anyone following this issue, 0.7.0 roadmap is available, let us know your thoughts.

Are there any plans to fully move to pydantic v2? I.e. having rx.Base subclass the v2 pydantic BaseModel instead of v1?
It seems like most packages at this point have made the transition fully to v2 and I'd really like to be able to stop thinking about v1 for good.
Before 0.6.0 I was somehow getting away with using v2 models as state attributes, but I've just tried upgrading from reflex==0.5.9 to 0.6.1 and it seems that whatever I had done no longer works. (I'm actually surprised I ever got away with it since v2 and v1 really don't play nice together...).

How dependent is the framework internally and wouldn't using something like Litestar offer better performance and allow potentially better full-stack experience in the long-run? Certain things on the roadmap like built-in auth is also included in Litestar. Might be worth taking a look.

@ruben-vanwyk We're not very coupled on FastAPI (we currently mainly use them for their Upload API, as well as exposing backend API routes) - in the future we plan to make that part of Reflex modular so people can use their own backend frameworks if they want.

Are there any plans to fully move to pydantic v2? I.e. having rx.Base subclass the v2 pydantic BaseModel instead of v1?

Is this still planned? Or do you want to migrate rx.Base to dataclasses instead?

Maybe this is mentioned somewhere: is there a tentative timeline for when 0.7 will come out (and perhaps 1.0 too)?

Are there any plans to fully move to pydantic v2? I.e. having rx.Base subclass the v2 pydantic BaseModel instead of v1?

Is this still planned? Or do you want to migrate rx.Base to dataclasses instead?

On the thread of reflex and pydantic...
The recent v0.6.6 release adds support for v2 models to be used as state vars which is very nice.


Encountering a 401 Unauthorized error while trying to authenticate on Twitter.

`import { Injectable } from '@nestjs/common';
import { PassportStrategy } from '@nestjs/passport';
import { Strategy } from '@superfaceai/passport-twitter-oauth2';
import { Config } from 'src/utils/config';
@Injectable()
export class TwitterStrategy extends PassportStrategy(
Strategy,
'twitter-strategy',
) {
constructor() {
super({
clientID: Config.TWITTER_CLIENT_ID,
clientSecret: Config.TWITTER_CLIENT_SECRET,
clientType: 'public',
callbackURL: ${Config.BACKEND_URL}/account-verification/twitter/callback,
scope: ['users.read', 'offline.access', 'tweet.read'],
passReqToCallback: true,
state: true,
});
}
async validate(
req: any,
accessToken: string,
refreshToken: string,
profile: any,
done: any,
) {
const { id, username } = profile;
const twitter: any = {};
twitter.twitterId = id;
twitter.username = username;
done(null, twitter);
}
async authenticate(req: any, options?: any) {
try {
return super.authenticate(req, options);
} catch (error) {
if (error.statusCode === 401) {
console.log('Unauthorized')
}
throw error;
}
}
}
`
I attempted different approaches to handle the 401 error, but none were successful. Could you guide me on how to effectively manage this issue in the provided code snippet?

Hi,
this is caused by either misconfigured Twitter app or wrong credentials. Did you go through the tutorial?
I suggest you to use one of our example apps  with your Twitter app & credentials.
Jan


Get rid of _MSC_VER #ifdefs

#270 introduced _MSC_VER #ifdefs in the source files.
I think it would be good if we good remove those from source files and instead configure the build tools to ignore those warnings. We should limit the platform specific macros from platform a-specific code as much as possible in my opinion. If we would do this for every platform there would be a lot of noise in the source files.
I'm not really familiar with Windows (cc @ntadej & @tdcosta100).

I think sometimes they are just unavoidable and also we should not ignore warnings globally (unless obvious ones which we already have).
I have some personal stuff to deal with that's why I've been a bit inactive lately but I can hopefully have a look next month.


PubSub subscription.pull() with return_immediately=True causes KeyError

Attempting to pull from a subscription of an empty topic with return_immediately set to 'True' causes an exception to be raised.  This should return an empty result, not raise a KeyError in the module, correct?
Example code:
#!/usr/bin/env python
from gcloud import pubsub

# Config
PUBSUB_TOPIC_NAME = 'deleteme'
PUBSUB_SUB_NAME = 'delete_me'

ack_queues = {}
client = pubsub.Client(project="joeholley-mimus01")
topic = client.topic(PUBSUB_TOPIC_NAME)
sub = topic.subscription(PUBSUB_SUB_NAME)
if not topic.exists():
  topic.create()
if not sub.exists():
  sub.create()
while True:
  recv = sub.pull(return_immediately=True,max_messages=1)
  print "Received!"

Results:
Traceback (most recent call last):
  File "db/db_worker.py", line 135, in <module>
    recv = sub.pull(return_immediately=True,max_messages=1)
  File "/usr/local/lib/python2.7/dist-packages/gcloud/pubsub/subscription.py", line 249, in pull
    self.full_name, return_immediately, max_messages)
  File "/usr/local/lib/python2.7/dist-packages/gcloud/pubsub/connection.py", line 419, in subscription_pull
    return response['receivedMessages']
KeyError: 'receivedMessages'

Expected results:
recv should contain an empty list as per http://googlecloudplatform.github.io/gcloud-python/stable/pubsub-subscription.html

Thanks for the report!  Should be fixed on master via dd38d6624465b46567b0ea1ed70f7262af891630.


Move Msaa to component

Switches Msaa from being a globally configured resource to a per camera view component.
Closes #7194
Objective
Allow individual views to describe their own MSAA settings. For example, when rendering to different windows or to different parts of the same view.
Solution
Make Msaa a component that is required on all camera bundles.
Testing
Ran a variety of examples to ensure that nothing broke.
TODO:

[ ] Make sure android still works per previous comment in extract_windows.

Migration Guide
Msaa is no longer configured as a global resource, and should be specified on each spawned camera if a non-default setting is desired.

Did you test this with multiple cameras with different MSAA modes? Iirc there are some pipeline properties that depend on it, so things might break if multiple levels are enabled at once.

Yes! Here are some foxes:

Here's a simple patch that might help alleviate the problem of having the proliferation of main textures be confusing to users who want to run split screen setups: https://github.com/bevyengine/bevy/pull/14287.

the mobile example needs to be updated, or this will fail merging on android compilation

the mobile example needs to be updated, or this will fail merging on android compilation

Should be fixed now. This PR also removes the more advanced per-window feature detection. I'd be happy to add that back in but wasn't sure where exactly it should go.

I think some things were missed here. Iirc in TAA plugin docs and meshlet plugin docs, it mentions that it automatically disabled MSAA, which is no longer true.


rename shape to shap

shape_values: The explanation information generated by shape lib
should be
shap_values: The explanation information generated by shap lib
also in code snippets
here it is ok: https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/machine-learning/service/how-to-configure-auto-train.md
(great addition btw! )

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

ID: a086a867-60ff-3f45-702d-2ea0ce0f4f0c
Version Independent ID: 38c9cb40-e4ed-1849-d7ca-9e5c9e51a94d
Content: Set up remote compute targets for automated ML - Azure Machine Learning service
Content Source: articles/machine-learning/service/how-to-auto-train-remote.md
Service: machine-learning
GitHub Login: @nacharya1
Microsoft Alias: nilesha

@rquintino Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.


Hello, do you have a complete deployment file for pinpoint1.7.3?

https://github.com/naver/pinpoint/releases/tag/1.7.3


Fabric Server With Synology Docker.

Hello, is it possible to run a fabric Server with docker for Synology. I know you can change the version from Vanille to Fabric, but when I want to start my server he will crash always, Am I overlooking something or is it not possible.

That's possible. Can you provide the container logs?

That's possible. Can you provide the container logs?

Hello, i just found it. I must place the installer jar and Accept the eula, now it's working fine.


Fix building docs locally

Following discourse I ran
julia --project=docs/ -e 'using Pkg; Pkg.develop(PackageSpec(path=pwd())); Pkg.instantiate()' [1]
This adds MaterialModels to the docs/Project.toml. Then, running
julia --project=docs/ docs/make.jl [2]
builds the documentation locally just fine.
So I guess [1] is only required the first time to generate the Manifest (and download packages if required) and [2] each time one wants to build the docs?
We could also include a compat section for documenter as in Fredrik's post above I guess...
(Sorry about the back and forth, did not realize [compat] was already there from before...)

I think for building the docs locally you still need to make sure you add MaterialModels with a path (either local, i.e. ".." or to this github repo), for me it complained that the package is not a registered package when I tried to instantiate.


Disable ALPN plugin on Java > 8

The ALPN boot classpath shouldn't be necessary starting with Java 9.  It is causing problems in the core repo examples on a modern JDK: https://github.com/http4s/http4s/pull/4226
We should detect the Java version in this plugin and disable it where it's unnecessary.

ALPN is gone.


Next 38356/visual test for shipping listing page

Description:
This ticket is part of a Proof of Concept (POC) for implementing visual tests in the shipping listing page.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Orkun Cavli seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Query about using the Jdempotent logo in a presentation for Apache Fineract

Hello,
We are preparing a formal presentation about the work that has been done and I want to add the logo of Jdempotent in the presentation and the acknowledgments.
https://docs.google.com/presentation/d/13lw2JqE9ujHVFwmynjJcVIUA3NfcDkbs729VLgadIXE/edit?usp=sharing
Please let me know if this is ok or if I should change anything
Best regards

Hello,
Very good news! There is no problem if you use it consciously that it is an MIT License.
We are always open to development. But there is a few typo in slide like JIdempotent instead of Jdempotent :)
Best regards

Thank you!!!
I have fixed the typo, added links to this Jdempotent repository and submitted the PR (draft proposal) for the Community review, I hope it can be part of the following Apache Fineract release.
https://github.com/apache/fineract/pull/1951


Geometry: Implement 'triangle'

Today, we don't have a simple way to create a Triangle primitive to use in rendering the UI.
We should create a wrapper similiar to the Quad primitive: https://github.com/bryphe/revery/blob/master/src/Geometry/Quad.re
...but for creating Triangles. This is important for implementing border-styling in #119

I think this was done in #123 but the issue didn't close so closing cc @bryphe @OhadRau (in case I'm wrong)


wrong endpoints for Followed-By User

Hello,
in the m file of InstaramEngine line 966 the method

(void)getUsersFollowedByUser:(NSString *)………

calls the endpoint :@"users/%@/follows"
I think it should call endpoint @"users/%@/followed-by"
Best Regards Andrew.

@AndreFormSpicyApps Actually, users/%@/follows is correct.


Consider using go build instead of 6g

For newer versions of Go there is a go build command that, maybe the syntax check should use that instead of calling the 64 bit compiler 6g which the system may or may not have.

I have no experience with go, but perhaps @dtjm or @bthomson may have something to say about this as they wrote the 2 current go syntax checkers.

You might be able to get away with just doing
 s/6g/go build/

I haven't touched that syntax checker in a while, but I was pretty much a copy-paste hack job on my part.

I'll try to play around with this later today, deadlines permitting, and see if go build would work for this.  If so then I will submit a patch for the current syntax checker.
My only reason for considering it is if a Go developer is building for 32Bit or ARM systems that person may not even have the 64 bit compiler (6g) installed in which case syntax checking for Go would never work in the first place.  One issue that this brings up though is that the go command isn't available for Go r60, so it will only work with Go weekly or Go tip, I'm not very familiar with vimL so writing something that would be backwards compatible with r60, if anyone still is, may be hard for me.

one way to go could be to create a new syntax checker called syntax_checkers/go/go.vim - this means the current 6g syntax checker will be left intact if anyone requires it.
If the go executable is not present, then the checker will not be loaded.

Ah thanks for that pointer

Here is one that worked for me
https://gist.github.com/1978595
I would appreciate it if someone else could maintain it as I don't have the time, otherwise I would have done the whole fork and submitted a pull request thing.


Make Config Read Environement Variables from Docker

Config should accept environement variables so it can be configured using Docker-Compose.

config can now be edited using the config file or env Variables


Make borderless move to the current monitor instead of just the primary

Some times I just want to sit in kamadan while watching a movie you know.

you can move the window with Windows key + shift + arrow key

No, it doesn't

does for me, what OS are you on?

w10

https://www.youtube.com/watch?v=dHClnU4eJTw

i use the left windows key + shift + arrow key

Welp, that works

Still think making move to the current monitor instead of primary would be a better default handling

I'm not sure about that actually. I often have gw open on my secondary monitor while afking, and for that staying in windowed mode and so showing the taskbar is a better experience. Then when I'm joining a run I press borderless and it goes to my primary monitor.

maybe a setting for which monitor then?

borderless has been implemented in the base game and we don't support it any more, closed.


Add Api trait for hooking into Instance and Device creation

Objective

Fixes #6263

Solution

I've added an Api trait and corresponding RenderApi resource that can be inserted before adding the RenderPlugin to gain control over wgpu Instance, Surface, Adapter, Device, and Queue creation.
A RenderApi using DefaultApi  is inserted automatically at RenderPlugin build time, when a RenderApi is missing.
DefaultApi uses the same wgpu functions and methods that were used before this change.

I would generally agree with you, but there are several reasons why I didn't do that:

This API will and should only be used by those who really need it. I didn't want to break existing users for this, which adding a field to RenderPlugin would do.
The RenderApi isn't solely used during initialization, but also when a surface is recreated. But I am actually not sure if surface creation should be customized. I have written this because I worked on an personal hobby renderer/game engine and I now want to integrate it into bevy and also reuse the RenderPlugin. But I also want to use some modern and largely unsupported features like raytracing, which wgpu does not support directly.
As long as RenderApi needs to stay around, due to the nature of Plugin being immutable during build time, this would require either an ugly hack like in #7682 or using Arc instead of Box. However with Box we can save an extra allocation, because types implementing Api will most likely be zero sized.
If #7687 is merged, we could provide an API like this:

impl RenderPlugin {
    pub fn with_api(self, api: impl Api) -> impl FnOnce(&mut App) -> Self {
        |app| {
            app.insert_resource(RenderApi(Box::new(api)));
            self
        }
    }
}

fn main() {
    App::new().add_plugin(RenderPlugin::default().with_api(CustomApi)).run();
}

This API will and should only be used by those who really need it. I didn't want to break existing users for this, which adding a field to RenderPlugin would do.

I would expect only the folks doing strange things with rendering already would be broken by this, so I don't think this is a concern.

This is listed as superseded in the Triage Doc. If no one disagrees, I propose we close this.


Feature FE 203 language detail edit

DO NOT MERGE, this is branched off https://github.com/SeedCompany/cord-field/pull/333
The Language Details and Edit functionality.  Copied over as close as possible from User Details and Edit.  Language Detail UI is a basic skeleton as the designs are not ready yet.
Testing
View the language Detail scene and edit the language.  You should see the same form as create language

@CarsonF will update PR when edit Language is merged but you can start reviewing this


Fixing framework not building.

Fixing scheme so it builds a framework.
This is basically reverting the changes to Typhoon.xcscheme made in b00dd8161eb2ebb34a325be08cb69111075d0215.
Verified that it builds with carthage.

thanks @akiraspeirs !


lit-html render function breaks when minifying and compiling to es5

Hi,
I am not sure if this is the right place to report this issue, but since it is a problem with the code compilation, it seems wise.
You can see below the two versions of the compiled code for the render function of the lit-html package when using the Polymer LitElement.
ES5 (not minified)
function render(result, container) {
    var templateFactory$$1 = arguments.length > 2 && arguments[2] !== undefined ? arguments[2] : templateFactory;
    var part = parts$1.get(container);

    if (part === undefined) {
      removeNodes(container, container.firstChild);
      parts$1.set(container, part = new NodePart(templateFactory$$1));
      part.appendInto(container);
    }

    part.setValue(result);
    part.commit();
}

ES5 (minified)
function render(result, container) {
    var templateFactory$$1 = 2 < arguments.length && arguments[2] !== void 0 ? arguments[2] : templateFactory,
        part = parts$1.get(container);
    part.setValue(result);
    part.commit();
}

As you can see the check of the part is missing which results to the following error TypeError: Cannot read property 'setValue' of undefined at render.
These are the contents of the polymer.json file I am using.
{
  "npm": true,
  "lint": {
    "rules": [
      "polymer-3"
    ]
  },
  "entrypoint": "src/index.html",
  "shell": "src/main.js",
  "moduleResolution": "node",
  "extraDependencies": [
    "node_modules/@webcomponents/webcomponentsjs/**"
  ],
  "builds": [
    {
      "name": "esm-bundled",
      "browserCapabilities": [
        "es2015",
        "modules"
      ],
      "js": {
        "minify": true
      },
      "css": {
        "minify": true
      },
      "html": {
        "minify": true
      },
      "bundle": true
    },
    {
      "name": "es2015-bundled",
      "browserCapabilities": [
        "es2015"
      ],
      "js": {
        "compile": "es2015",
        "minify": true,
        "transformModulesToAmd": true
      },
      "css": {
        "minify": true
      },
      "html": {
        "minify": true
      },
      "bundle": true
    },
    {
      "name": "es5-bundled",
      "js": {
        "compile": "es5",
        "minify": true, // it works if I set this to false
        "transformModulesToAmd": true
      },
      "css": {
        "minify": true
      },
      "html": {
        "minify": true
      },
      "bundle": true
    }
  ]
}

Any ideas?

@justinfagnani I've just run into this as well. Have you see it, or have any thoughts on where to go with this?
My situation is as close to exactly the same as @orestisioakeimidis as possible. If having some sort of repo based reproduction would help find a resolution to this, let me know.

It DOES seem that if the following condition:
if (first === undefined) {

is reversed to
if (undefined === first) {

That the minifier is tricked into not removing the condition again. 😕 Not to make it a lit-html issue, specifically, but certain projects are more likely to have releases than others...

Here is the repository to reproduce the error.
https://github.com/orestisioakeimidis/polymer-lit-element-repro

Appears to be a babel-minify issue. Note there is new version 0.5.0 released recently.

Good looking out @web-padawan !
It looks like the commits that maintain that are from @usergenic https://github.com/Polymer/tools/commit/676c28c3eef2b54558427b921ab31013a8b168cd and @justinfagnani  https://github.com/Polymer/tools/commit/7b7799839bc9415e69c0c73d17138118f8bb6817
I'm gonna do some research and see if at least the issues faced here are addressed by unfixing those dependencies. Not sure if there were tests created to support those decisions that will be able to back up the reality of removing them or not...one thing at a time though!

On further review, it doesn't seem that updating those packages does the work we're looking for here.
However, in accordance with https://github.com/babel/minify/issues/574#issuecomment-307390713 the addition of deadcode: false to packages/build/src/js-transform.ts in the babelPresetMinify settings on line 100 does bring back this code.
Trying to get tests to report actionable things about this locally, but might end up submitting s PR just to get those results easier. Theoretically, deadcode would only change some additional code being shipped down the wire, and nothing functionally, so it might be alright?

Further comparisons between my instance of the issue and the above description point to this specifically being about instances where options.compile === true || options.compile === 'es5'. Focusing the application of deadcode: false to that context is working well in application, the tests are running now, so hopefully that will go somewhere useful. However, that being so makes me wonder if minify as the cause here is a red herring and that there's something in this list of plugins that might be causing this... 😕
Continuing to look.

Just in case if someone is interested: I have recently updated my Webpack starter to use Terser for minification: https://github.com/web-padawan/polymer3-webpack-starter
@orestisioakeimidis @Westbrook feel free to try the config from there on your projects and see if that works for you. I would be glad to hear any feedback (as my project does not yet include lit-html).

Changing
export function render(result, container, templateFactory = defaultTemplateFactory) {
    let part = parts.get(container);
    if (part === undefined) {
        removeNodes(container, container.firstChild);
        parts.set(container, part = new NodePart(templateFactory));
        part.appendInto(container);
    }
    part.setValue(result);
    part.commit();
}

to:
export function render(result, container, templateFactory = defaultTemplateFactory) {
    let part = parts.get(container);
    const isUndefined = part === undefined;
    if (isUndefined) {
        removeNodes(container, container.firstChild);
        parts.set(container, part = new NodePart(templateFactory));
        part.appendInto(container);
    }
    part.setValue(result);
    part.commit();
}

circumvents this particular issue. It's a bit scary, as this could happen to any part of the codebase.

After more digging, it seems that this got magically fixed in lit-html 0.12.x.
Before the render function was:
function render() {}

Now it's a variable:
const render = () => {}

This magically does not trigger the dead code removal, so it resolves the issue for now. But it can pop up in other places.

Proposing https://github.com/Polymer/tools/pull/777

Also trying bumping babel-minify to more recent versions...

After bumping babel minify to latest version, I still encounter the error, where the container is not present in the parts$1 WeakMap:

Turning off deadcode removal right now appears to be the only reliable approach.

More specifically I had updated the package.json with these two lines:
    "babel-plugin-minify-guarded-expressions": "^0.4.3",
    "babel-preset-minify": "^0.5.0",

(the packages/build/package.json that is) and I even ran an npm run nuke to update all the package locks to latest versions of all-the-things but it didn't solve.


I created a monodevelop theme :)

Hi there,
I created GabLeRoux/monodevelop theme. I did not look at all the details on how the theme can be merged, but It works for me and looks great. I started from monokai for other default colors and json values. Maybe it can be improved, but it's more than enough for me :)

Let me know if I must update something.

Hey @GabLeRoux, that's awesome!
What we usually do is transferring the repository to this organization and then adding a page on the site. You would still control and maintain the repository, nothing changes :)
Let me know if you like this idea so I can send you an invitation.

And sorry for taking so long to reply :/

Sure, go on! :D
No problem for the delay, we all have many things to do, really glad this can become official! 👍

Great, let me know when you accept the invitation ;)

I did not find any invitation in my github notifications nor in project's settings, but I've added you as a contributor if it helps somehow, or do I have to transfer the repo?

Let me know if I missed something here ;)

Take a look now, invitations are sent via email and can be accepted at https://github.com/dracula

Accepted invite 🎉  Thanks

Awesome! You can now standardize the README based on the https://github.com/dracula/template and send a pull request to https://github.com/dracula/dracula.github.io/ with the new theme ;)

All done!
https://draculatheme.com/monodevelop/
https://github.com/dracula/monodevelop/commit/fc55b762354c55155c94458b3844c63cada0c505
🎉


no access to PATH in AWS Lambda

As title suggests, you can't always get access to change the PATH, AWS Lambda is one of many that come to mind (CI's, AWS ECS, many PaaS, ect).
We need to be able to tell the library which binary to use, similar to this npm library offers, https://www.npmjs.com/package/pdf-text-extract

We could package all the dependencies in the library then set the path on all functions explicitly?

Something like
process.env['PATH'] = process.env['PATH'] + ':' + process.env['LAMBDA_TASK_ROOT'] + '/bin'; process.env['LD_LIBRARY_PATH'] = process.env['LAMBDA_TASK_ROOT'] + '/bin';


Create a more efficient caching structure for location lookup

Original issue: https://charm.cs.illinois.edu/redmine/issues/1065

In the 64 bit merge, spring cleaning was eliminated in order to clean up the code and remove the large CkLocRec class hierarchy. In doing so, location lookup was changed to use a std::map, however the intent was that eventually a more efficient caching structure would be used that not only provided faster lookups, but took over some of the spring cleaning functionality by behaving similarly to a cache. The original commit can be found here: https://charm.cs.illinois.edu/gerrit/gitweb?p=charm.git;a=commit;h=337fdfc5d9628a6575fbbddba4e977d7ba9839c6

Original date: 2017-02-01 19:46:24

Change from std::map to std::unordered_map: ~~https://charm.cs.illinois.edu/gerrit/#/c/1978/~~ https://github.com/UIUC-PPL/charm/commit/ac84e2be6f63d892bf3aa9a576a16bbc27624db2
Use tr1/unordered_map on BGQ: ~~https://charm.cs.illinois.edu/gerrit/#/c/2013/~~ https://github.com/UIUC-PPL/charm/commit/806b3277cac6c0e37864c8339e1220a0770a1b54

Original date: 2017-10-27 02:18:44

Change CkLocMgr's std::unordered_map's to ska::flat_hash_map's: https://charm.cs.illinois.edu/gerrit/#/c/3170/
Need to check compiler dependencies of this, benchmark its performance with applications, and potentially write a PUP routine for it.
ska::flat_hash_map is taken from: https://github.com/skarupke/flat_hash_map
ska::flat_hash_map is described and micro-benchmarked here: https://probablydance.com/2017/02/26/i-wrote-the-fastest-hashtable/
Another hash table implementation to look at would be tsl::hopscotch_map: https://github.com/Tessil/hopscotch-map

Original date: 2017-10-27 02:20:49

There'd be no need for a pup for this particular structure - it can be completely discarded and reconstituted when the location manager instance unpacks itself.


Fix incorrect boolean logic when providing title

The title was not being set

Thx!


move benchmark tests

Move all benchmark tests in one place, currently they are located in two different directories: /benchmarking and /runtime.

Closing in favour of #406


Getting

This is my code (following the basic example without registering anything):
// index.js
var proxy = require('redbird')({ port: 80});

I'm getting this error when I run node index.js:
{"name":"redbird","hostname":"MyComp","pid":98959,"level":50,"err":{"message":"listen EACCES <IP_ADDRESS>:80","name":"Error","stack":"Error: listen EACCES <IP_ADDRESS>:80\n    at Server.setupListenHandle [as _lis
ten2] (net.js:1313:19)\n    at listenInCluster (net.js:1378:12)\n    at Server.listen (net.js:1466:7)\n    at new ReverseProxy (/Users/mycomp/Desktop/reverse-proxy/node_modules/redbird/lib/proxy.js:122:12)\
n    at ReverseProxy (/Users/mycomp/Desktop/reverse-proxy/node_modules/redbird/lib/proxy.js:24:12)\n    at Object.<anonymous> (/Users/mycomp/Desktop/reverse-proxy/index.js:1:93)\n    at Module._compile
 (internal/modules/cjs/loader.js:678:30)\n    at Object.Module._extensions..js (internal/modules/cjs/loader.js:689:10)\n    at Module.load (internal/modules/cjs/loader.js:589:32)\n    at tryModuleLoad (internal/modules/cjs/loader.js:528:12)\n    at Function.Module._load (internal/modules/cjs/loader.js:520:3)\n    at Function.Module.runMain (internal/modules/cjs/loader.js:719:10)\n    at startup (internal/bootstrap/node
.js:228:19)\n    at bootstrapNodeJSCore (internal/bootstrap/node.js:575:3)","code":"EACCES"},"msg":"Server Error","time":"2018-06-01T03:09:39.173Z","v":0}

Any idea why? I cant seem to find an answer anywhere in the issues section. Also, I dont have anything else running on port 80.

This is because you need elevated permissions to bind to anything less than port 1024, not because of redbird. Run the app as sudo or elevate your user level to root. Depending on your setup, check out https://stackoverflow.com/questions/9164915/node-js-eacces-error-when-listening-on-most-ports

ah.... alright, thanks so much!


Snap broken in distros not Ubuntu - Unable to find module repositories.

Steps to reproduce
Install Powershell using snapd
Expected behavior
Would expect to be able to download and install modules
Actual behavior
Works as expected under Ubuntu. Have tested on CentoOS, Fedora and Arch. All broken.
For example, if I attempt to install the module az under Ubuntu it works. On the distros listed above I get the following error...
PackageManagement\Install-Package : No match was found for the specified search criteria and module name 'az'. Try Get-PSRepository to see all available registered module repositories.
At /var/lib/snapd/snap/powershell/88/opt/powershell/Modules/PowerShellGet/PSModule.psm1:9508 char:21

...          $null = PackageManagement\Install-Package @PSBoundParameters

                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : ObjectNotFound: (Microsoft.PowerShel\u2026lets.InstallPackage:InstallPackage) [Install-Package], Exception
FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

Running Get-PSRepository results in...
WARNING: Unable to find module repositories..
Environment data

Name                           Value

PSVersion                      6.2.4
PSEdition                      Core
GitCommitId                    6.2.4
OS                             Linux 4.18.0-147.5.1.el8_1.x86_64 #1 SMP Wed Fe…
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Just to add to this - Ubuntu 20.04 is broken as well. After testing the snap on numerous distros, it appears to only work on Ubuntu 18.04. Why on earth are you bothering to publish a snap if it isn't going to be distro agnostic. That's like the entire point.

Also not to pile on, but there are no 20.04 packages available in the apt repository either.


Node.js Foundation Community Committee Meeting 2019-05-02

Time
UTC Thu 02-May-2019 16:00 (04:00 PM):

Timezone
Date/Time

US / Pacific
Thu 02-May-2019 09:00 (09:00 AM)

US / Mountain
Thu 02-May-2019 10:00 (10:00 AM)

US / Central
Thu 02-May-2019 11:00 (11:00 AM)

US / Eastern
Thu 02-May-2019 12:00 (12:00 PM)

London
Thu 02-May-2019 17:00 (05:00 PM)

Amsterdam
Thu 02-May-2019 18:00 (06:00 PM)

Moscow
Thu 02-May-2019 19:00 (07:00 PM)

Chennai
Thu 02-May-2019 21:30 (09:30 PM)

Hangzhou
Fri 03-May-2019 00:00 (12:00 AM)

Tokyo
Fri 03-May-2019 01:00 (01:00 AM)

Sydney
Fri 03-May-2019 02:00 (02:00 AM)

Or in your local time:

http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Community Committee+Meeting+2019-05-02&iso=20190502T16
or http://www.wolframalpha.com/input/?i=04PM+UTC%2C+May+02%2C+2019+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1B7IJXpSsCV9aDuISea4shYyiE1GpmATitK-PjjoOazE/edit

Agenda
Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/community-committee

CPC Representative Nominations #470
Discuss Collab Summit Progress #448

Invited

CommComm Members: @nodejs/community-committee

Observers/Guests
Feel free to follow along on the YouTube live stream, or attend meeting as a guest
by calling in to Zoom, using the links below. If you will be attending as a guest,
please comment on this issue to let us know you'll be joining.
Notes
The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

Link for participants: https://zoom.us/j/527273462
For those who just want to watch: https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ

@mhdawson – don't seem to have access to the google doc on this meeting anymore 🤔 Can't PR minutes in without it!

I couldn't attend today. :(

Closing because this is an old issue.


There is no option for set-only values.

We don't need to modify all environment values. Sometimes having the default be readable is sufficient.

How would you use a environment value that isn't writable? Wouldn't that always give the default value?
Or, are you referring to a private setter and a public getter? This is likely what SwiftUI also does under the hood for its built-in environmentkeys that aren't settable. You should be able to do this with this package too:
@EnvironmentStorage
extension EnvironmentValues {
    public private(set) var test: Bool = false
}

Wouldn't that always give the default value?
Yes. As I said, sometimes you just need an immutable singleton accessible in views. For example, this can't change:

extension EnvironmentValues {
  private enum MetalDeviceKey: EnvironmentKey {
    static var defaultValue: some MTLDevice { MTLCreateSystemDefaultDevice()! }
  }

  var metalDevice: any MTLDevice { self[MetalDeviceKey.self] }
}

I see!
I might be wrong, but if you want to use singletons in the environment, EnvironmentKeys might not be needed. As in, you should be able to do
extension EnvironmentValues {
  var metalDevice: some MTLDevice { MTLCreateSystemDefaultDevice()! }
}

Would such a thing work for you?

Would such a thing work for you?

Not that exactly, but there are of course many options. EnvironmentValues just canonized how to pretend like you have dependency injection of instance properties.
I have no idea how you'd find a list of which environment values SwiftUI provides are read-only, to see the precedent. They'll all generate the same error:
Key path value type 'KeyPath<EnvironmentValues, Whatever>' cannot be converted to contextual type 'WritableKeyPath<EnvironmentValues, Whatever>'
E.g.
.environment(\.pixelLength, 1)

I have no idea how you'd find a list of which environment values SwiftUI provides are read-only, to see the precedent. They'll all generate the same error:

Key path value type 'KeyPath<EnvironmentValues, Whatever>' cannot be converted to contextual type 'WritableKeyPath<EnvironmentValues, Whatever>'

This error occurs when the computed property in EnvironmentValues has no (accessible) setter. I have checked with both examples from above and they both will show this error.


RN: Checkbox - Orbit Styles

This Pull Request meets the following criteria:

[ ] Tests have been added/adjusted for my new feature
[ ] New Components are registered in index.js of my project

This is the existing Checkbox on the web:

And this is the result of this implementation:

It seems to me the alignment is different. Could you fix this?


Value changes if I click it

Hello, I have installed knob and i have blocking the value, because if I put a value with the comma, when I click change number?
Video: https://vid.me/FCNt

This video is deleted from vid.me, can you re-upload it somewhere else?


Named alleles

Better diff of test output here
Example named-allele evidence:
{
  "datasourceId": "pharmgkb",
  "datasourceVersion": "2024-01-05",
  "datatypeId": "clinical_annotation",
  "studyId": "1448104189",
  "evidenceLevel": "2A",
  "literature": [
    "16338275",
    "17329992",
    "26389554",
    "26389554",
    "27286724",
    "17178267",
    "17502774",
    "17502774",
    "21589866",
    "28723731",
    "28723731",
    "32302325"
  ],
  "genotype": "*6",
  "genotypeAnnotationText": "Patients carrying the CYP2B6*6 allele in combination with a normal or decreased function allele may have decreased clearance of methadone as compared to patients with two normal function alleles. However, conflicting evidence has been reported. Other genetic and clinical factors may also affect methadone metabolism. This annotation only covers the pharmacokinetic relationship between CYP2B6 and methadone and does not include evidence about clinical outcomes.",
  "alleleFunction": "Decreased function",
  "drugFromSource": "methadone",
  "drugId": "CHEBI_6807",
  "pgxCategory": "metabolism/pk",
  "phenotypeText": "Heroin Dependence",
  "phenotypeFromSourceId": "EFO_0004240",
  "haplotypeId": "CYP2B6*6",
  "internalHaplotypeId": "PA165818762",
  "targetFromSourceId": "ENSG00000197408"
}

Updates to schema as per this thread


Master

@patrickschneider23 Hi. Can you explain, what this PR do?

it should help merge #221
@patrickschneider23  There is conflicts in your PR.


Fix bug with docs release

Fix to address removal of notebooks from workflow-calcium-imaging
Will trigger a new release of 0.5.4 to publish to PyPI

Version 0.5.4 is now on PyPI.


Extension update notifications

Is there any autoupdate mechanism for extensions, or do they need to be updated manually?

I prefer a notification system that lets you know when updates are available (Atom has this).
So you'd have two options:

Automatically check for extension updates. (default: true?)
Automatically install extension updates. (default: false)

Plus maybe an option to specify the update check frequency.
You could also do per-extension override settings, but that would be extra work. =)

yes. this would be really important since we are already pushing updates to addins.

I think a simple "Extensions: Show Available Updates" would be useful for people who prefer to do it manually.

FYI, just merged #517 from @akamud that brings in a global action to show outdated extensions

Excellent!  That's one important piece of the puzzle.

+1 For automatic notifications (á la Atom).

+! For notification that update is available.

We did implement update notifications this release, will come with the next version.

Any chance you could point me at a PR?

#4024 is a test plan item which mentions this.


fix: tabs addable

🤔 这个 PR 的性质是？

[x] 日常 bug 修复
[ ] 新特性提交
[ ] 文档改进
[ ] 演示代码改进
[ ] 组件样式/交互改进
[ ] CI/CD 改进
[ ] 重构
[ ] 代码风格优化
[ ] 测试用例
[ ] 分支合并
[ ] 其他

🔗 相关 Issue

💡 需求背景和解决方案

📝 更新日志

fix(Tabs): 修复选项卡新增和删除在normal风格下无效 (issue #865)

☑ 请求合并前的自查清单
⚠ 请自检并全部勾选全部选项。⚠

[x] 文档已补充或无须补充
[x] 代码演示已提供或无须提供
[x] TypeScript 定义已补充或无须补充
[x] Changelog 已提供或无须提供

还有clearable的逻辑要加上

Codecov Report

Merging #921 (a586100) into develop (a0db0df) will increase coverage by 2.64%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #921      +/-   ##
===========================================
+ Coverage    57.56%   60.20%   +2.64%
===========================================
  Files          346      376      +30
  Lines        12828    14314    +1486
  Branches      2405     2666     +261
===========================================
+ Hits          7384     8618    +1234
- Misses        5200     5433     +233
- Partials       244      263      +19

Impacted Files
Coverage Δ

src/affix/affix.tsx
28.57% <0.00%> (-37.51%)
:arrow_down:

src/swiper/props.ts
68.75% <0.00%> (-31.25%)
:arrow_down:

src/dialog/props.ts
70.00% <0.00%> (-30.00%)
:arrow_down:

src/calendar/props.ts
70.00% <0.00%> (-30.00%)
:arrow_down:

src/popup/props.ts
75.00% <0.00%> (-25.00%)
:arrow_down:

src/slider/props.ts
75.00% <0.00%> (-25.00%)
:arrow_down:

src/message/props.ts
75.00% <0.00%> (-25.00%)
:arrow_down:

src/tooltip/props.ts
75.00% <0.00%> (-25.00%)
:arrow_down:

src/pagination/props.ts
75.00% <0.00%> (-25.00%)
:arrow_down:

src/steps/step-item-props.ts
75.00% <0.00%> (-25.00%)
:arrow_down:

... and 137 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 19689a4...a586100. Read the comment docs.


Fatal Bug

When I deploy the firebase functions it throws this error:
node_modules/@google-cloud/firestore/types/firestore.d.ts:117:29 - error TS1005: ']' expected.

117     {[K in keyof T & string as `${Prefix}.${K}`]+?: T[K]};
                                ~~

node_modules/@google-cloud/firestore/types/firestore.d.ts:117:48 - error TS1005: ';' expected.

117     {[K in keyof T & string as `${Prefix}.${K}`]+?: T[K]};
                                                   ~

node_modules/@google-cloud/firestore/types/firestore.d.ts:117:50 - error TS1109: Expression expected.

117     {[K in keyof T & string as `${Prefix}.${K}`]+?: T[K]};
                                                     ~

node_modules/@google-cloud/firestore/types/firestore.d.ts:117:51 - error TS1109: Expression expected.

117     {[K in keyof T & string as `${Prefix}.${K}`]+?: T[K]};
                                                      ~

node_modules/@google-cloud/firestore/types/firestore.d.ts:2278:1 - error TS1128: Declaration or statement expected.

2278 }

I have googled myself into an oblivion, I cant find a fix.
I have upgraded and downgraded my typescript versions
current package.json
{
  "name": "functions",
  "version": "1.0.0",
  "description": "",
  "main": ".eslintrc.js",
  "directories": {
    "lib": "lib"
  },
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "lint": "eslint \"src/**/*\"",
    "build": "tsc",
    "serve": "npm run build && firebase emulators:start --only functions",
    "shell": "npm run build && firebase functions:shell",
    "start": "npm run shell",
    "deploy": "firebase deploy --only functions",
    "logs": "firebase functions:log"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/cavedweller/Firebase_Functions.git"
  },
  "author": "",
  "license": "ISC",
  "bugs": {
    "url": "https://github.com/cavedweller/Firebase_Functions/issues"
  },
  "homepage": "https://github.com/cavedweller/Firebase_Functions#readme",
  "engines": {
    "node": "12"
  },
  "dependencies": {
    "@angular/fire": "^7.4.1",
    "@firebase/storage": "^0.9.9",
    "@google-cloud/tasks": "^3.0.2",
    "@sendgrid/mail": "^7.7.0",
    "axios": "^0.21.4",
    "dateformat": "^4.6.3",
    "firebase": "^9.9.3",
    "firebase-admin": "^11.0.1",
    "firebase-functions": "^3.22.0",
    "node-fetch": "^2.6.7",
    "typescript": "^4.0.5"
  },
  "devDependencies": {
    "@types/babel__core": "^7.1.19",
    "@typescript-eslint/eslint-plugin": "^5.35.1",
    "@typescript-eslint/parser": "^5.35.1",
    "eslint": "^8.23.0",
    "eslint-plugin-import": "^2.26.0",
    "firebase-functions-test": "^2.3.0"
  },
  "private": true
}

The only reason why I am running typescript version 4.0.5 is because it is the only version that shows where the issue is, the later versions just say that there is a bug and don't point me to the issue.
I have deleted my node_modules, package-lock.json and package.json about 10 times. Nothing works
Any assistance would greatly be appreciated

If you run npm update, you will see that you are using 4.8.2 as of this writing. I recommend pinning to ~4.7.4.
We have a known issue with 4.8.2 type checking in this library, and will be doing the same in our package.json.

Hi @tom-andersen, thank you for the response.
So I think I have really messed up something.
When I create a new package.jsonit changed the "main" , when I deploy the functions now it says the functions have deployed but I cannot see them in my project, in fact it says "The following functions are found in your project but do not exist in your local source code" then prompts me to delete the function, which I did but it does not upload anything after.
{
  "name": "functions",
  "version": "1.0.0",
  "description": "",
  "main": ".eslintrc.js",
  "directories": {
    "lib": "lib"
  },
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "lint": "eslint \"src/**/*\"",
    "build": "tsc",
    "serve": "npm run build && firebase emulators:start --only functions",
    "shell": "npm run build && firebase functions:shell",
    "start": "npm run shell",
    "deploy": "firebase deploy --only functions",
    "logs": "firebase functions:log"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/cavedweller/Firebase_Functions.git"
  },
  "author": "",
  "license": "ISC",
  "bugs": {
    "url": "https://github.com/cavedweller/Firebase_Functions/issues"
  },
  "homepage": "https://github.com/cavedweller/Firebase_Functions#readme",
  "engines": {
    "node": "12"
  },
  "dependencies": {
    "@angular/fire": "^7.4.1",
    "@firebase/storage": "^0.9.9",
    "@google-cloud/tasks": "^3.0.2",
    "@sendgrid/mail": "^7.7.0",
    "axios": "^0.21.4",
    "dateformat": "^4.6.3",
    "firebase": "^9.9.3",
    "firebase-admin": "^11.0.1",
    "firebase-functions": "^3.22.0",
    "node-fetch": "^2.6.7",
    "typescript": "^4.7.4"
  },
  "devDependencies": {
    "@types/babel__core": "^7.1.19",
    "@typescript-eslint/eslint-plugin": "^5.35.1",
    "@typescript-eslint/parser": "^5.35.1",
    "eslint": "^8.23.0",
    "eslint-plugin-import": "^2.26.0",
    "firebase-functions-test": "^2.3.0"
  },
  "private": true
}

I then changed my "main" back to what it was before I deleted the package.json. It now prompts me with this error - "Function failed on loading user code. This is likely due to a bug in the user code. Error message: Error: please examine your function logs to see the error cause: https://cloud.google.com/functions/docs/monitoring/logging#viewing_logs. Additional troubleshooting documentation can be found at https://cloud.google.com/functions/docs/troubleshooting#logging. Please visit https://cloud.google.com/functions/docs/troubleshooting for in-depth troubleshooting documentation."
{
  "name": "functions",
  "main": "lib/index.js",
  "scripts": {
    "lint": "eslint \"src/**/*\"",
    "build": "tsc",
    "serve": "npm run build && firebase emulators:start --only functions",
    "shell": "npm run build && firebase functions:shell",
    "start": "npm run shell",
    "deploy": "firebase deploy --only functions",
    "logs": "firebase functions:log"
  },
  "engines": {
    "node": "12"
  },
  "dependencies": {
    "@firebase/storage": "^0.9.9",
    "@google-cloud/tasks": "^3.0.2",
    "@sendgrid/mail": "^7.7.0",
    "axios": "^0.21.4",
    "dateformat": "^4.6.3",
    "firebase-admin": "^11.0.1",
    "firebase-functions": "^3.22.0",
    "node-fetch": "^2.6.7",
    "typescript": "^4.7.4"
  },
  "devDependencies": {
    "@types/babel__core": "^7.1.19",
    "@typescript-eslint/eslint-plugin": "^5.35.1",
    "@typescript-eslint/parser": "^5.35.1",
    "eslint": "^8.23.0",
    "eslint-plugin-import": "^2.26.0",
    "firebase-functions-test": "^2.3.0"
  },
  "private": true
}

Any assistance would greatly be appreciated 😎

Note the use of caret ^ instead of tilde ~ in package.json.
You have to use ~, otherwise it will simply retrieve the latest version when you run npm update or the first time you run npm install.

@tom-andersen , I truly am grateful for the responses.
So I changed the ^ to ~ for the typescript package.
I then ran update and install to double sure everything was loaded
Updated package.json
 "dependencies": {
    "@firebase/storage": "^0.9.9",
    "@google-cloud/tasks": "^3.0.2",
    "@sendgrid/mail": "^7.7.0",
    "axios": "^0.21.4",
    "dateformat": "^4.6.3",
    "firebase-admin": "^11.0.1",
    "firebase-functions": "^3.22.0",
    "node-fetch": "^2.6.7",
    "typescript": "~4.7.4"
  },

The error I have is still the same
Function failed on loading user code. This is likely due to a bug in the user code. Error message: Error: please examine your function logs to see the error cause: https://cloud.google.com/functions/docs/monitoring/logging#viewing_logs. Additional troubleshooting documentation can be found at https://cloud.google.com/functions/docs/troubleshooting#logging. Please visit https://cloud.google.com/functions/docs/troubleshooting for in-depth troubleshooting documentation.

Functions deploy had errors with the following functions:
        tw(us-central1)
i  functions: cleaning up build files...

Error: There was an error deploying functions

I have had a look at the firebase function logs and this is the output
SyntaxError: Unexpected token '?'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/workspace/node_modules/firebase-admin/lib/default-namespace.js:19:30)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)

Thank you again for your assistance 👌

What I landed up doing was running firebase init and just resetting everything, it loaded the necessary versions and it seems to be working again.
Thanks again for your assistance

I can confirm reproduction of this issue and that pegging to typescript ~4.7.4 resolved it for me.


VS Code extension not starting

Perhaps I'm missing something here, but the VS Code extension appears to not work at all?
I have cfn-lint installed and I can use the CLI as expected -
dgard@THH-TPI6674:~$ cfn-lint --version
cfn-lint 0.51.0

Initially when I start VS Code there is no output for the extension, but after I try to run the 'Preview CloudFormation as a graph' command I see the following output for 'CloudFormation linter Language Server' -
Settings have been updated...
Settings: {"cfnLint":{"enableAutocomplete":true,"validateUsingJsonSchema":false,"path":"cfn-lint","appendRules":[],"ignoreRules":[],"overrideSpecPath":""}}

It should be noted that 'Preview CloudFormation as a graph ' doesn't work either though -

Command 'Preview CloudFormation template as graph' resulted in an error (command 'extension.sidePreview' not found)

The only requirements for the extension say that cfn-lint and (optionally) pydot need to be installed, and both are available.
Any tips on how to get this working, as it seems like it might be useful.
Thanks,
David

What extension version? (latest is 0.19.0)
Also could you try re-installing the extension / restarting just to rule that out?

@PatMyron - I have version v0.19.0 of the extension. I have tried removing the extension, restarting, installing it, and then restarting again, but the same behaviour persists.
I also noticed that on subsequent attempts to run 'Preview CloudFormation as a graph' the following error is output -
preview requested: file:///home/dgard/cluster.cfn.yaml
[Error - 9:10:04 AM] Notification handler 'cfn/requestPreview' failed with message: Cannot read property 'uri' of undefined

cc @justinmk3 @bryceitoc9 @JadenSimon @gsweetwood from https://github.com/aws/aws-toolkit-vscode/graphs/contributors for awareness

@dgard1981 do you have any other extensions installed btw? Want to double check if there's any other extension that could be causing that issue

The AWS Toolkit does have different language servers for YAML files, but none are called 'CloudFormation YAML' so I'm not sure where that is coming from.

This comes from the keyboardDrummer.vscode-cloudformation, which appears to no longer exist on the marketplace (see: https://github.com/keyboardDrummer/cloudformation-ide-tooling/blob/master/vscode-extension/package.json#L48 )

@JadenSimon - Perhaps that language is baked in to VS Code these days, as you a right, it is not actually part of the AWS Toolkit extension.
So the issue appears to be that cfn-lint only works with the YAML language, and as soon as the language is switched to CloudFormation YAML (which happens automatically for files of type *.cfn.yaml), it stops working.

@dgard1981 Did you see @bryceitoc9's comment? Perhaps you have that extension 'installed' but maybe VS Code doesn't recognize it? In any case you should be able to manually override the auto-detection by adding this to your settings.json:
"files.associations": {
  *.cfn.yaml": "yaml"
}

This should stop the rogue extension from changing the language mode.

I ran into this issue with the latest versions, I can confirm that the @JadenSimon's fix/workaround was effective.


Document overriding docs json namespace in Readme

Pull example from tests/dummy/application.js and place it into the readme for easy reference

Completed


Revert "Add private_cluster_configuration instead of enable_private_e…

This reverts commit 039ea4b57edc94086b0aab77cad33394378807b4.
Seeing breaking changes in stage-1/infra

Revert lgtm. Apologies for breaking the code!

no apologies needed :) it's a good signal we could use a presubmit end to end test!


The counter text isn't visible in StateActivity due to a platform bug in dev08

The issue is related to using  a composable with elevation. It causes the composables around it that don't have an elevation to not be visible.
https://github.com/vinaygaba/Learn-Jetpack-Compose-By-Example/blob/master/app/src/main/java/com/example/jetpackcompose/state/StateActivity.kt
https://github.com/vinaygaba/Learn-Jetpack-Compose-By-Example/blob/a44eb99d13516a98ecb3d5f07eff00c6d50d7106/app/src/main/java/com/example/jetpackcompose/image/ImageActivity.kt#L273

https://github.com/vinaygaba/Learn-Jetpack-Compose-By-Example/commit/7a065d7e9a7d329eb64315e869efb654c5cb3775


Convert to promises or something async

It doesn't work for me. I'm running Ubuntu 14.10, embark 0.7.0, geth 0.9.39
This seems like a really bad way to implement it (but then, I was told it was a hack, so, eh..)
lib/deploy.js
      while ((receipt = web3.eth.getTransactionReceipt(transactionHash)) === null) {
          sleep.sleep(1);
      }

Sometimes I get "CONNECTION ERROR" (and sometimes it just quietly returned back to my shell without doing anything), I think web3 just trying over and over again to do JSON-RPC to geth. I tried to convert this into a way to use the callbacks on the .new() call to a contract that tell you the address, but then everything else broke. (Such as when it goes to write the ABI, it wasn't waiting for the transaction to finish being deployed, it was depending on this loop to repeat.)
I'm not sure what the best way to fix all of this is, unfortunately I'm not a JS expert. :-(
Good luck converting it to promises/async stuff.

Repeat of https://github.com/iurimatias/embark-framework/issues/30
I'll just put my request over there.


Walkers-ChristopherBody

This is a piece of somewhat abstract art. I wanted to express how a landscape can be defined by those who explore it. It creates a configurable amount of 'Walkers', who traverse a distance field (simple noise here) by sampling neighbouring points and depending on configuration, try to either minimize or maximize the sdf value.
I have been coding for several years and have intermediate experience coding JavaScript, python, C and C++.

A bit more abstract than what we are encouraging people to do but it looks like some thought went into the implementation.
Congrats you've earned your Blot! You can order it here.


fix: (issue #159) sidebar-item active state (fix scss class)

fix scss file for displaying active state of sidebar item component

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] 📦 New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
fix puik-sidebar-item--active scss class
📝 Checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes
[ ] The component exists on old Prestashop UIKit and my pull request on migrating documentation is accepted.

Et du coup, pourquoi ça marche dans le StoryBook?


create_network_interface() should use default VPC Security Group if no groups passed

create_network_interface() creates an invalid ENI -- missing a Security Group
ENI objects are required to have at least one Security Group, and Groups is not a required parameter. If create_network_interface is called with no Groups parameter, the VPC Default Security Group is supposed to be automatically added.
This behavior creates invalid ENI objects (with no Security Group attached), and does not match AWS EC2 behavior.

This code behaves differently when run with the moto package available or not (Python 3):

ec2 = boto3.resource('ec2')
vpc = tuple(ec2.vpcs.all())[0]
vpc_default_sg = next(_.id for _ in vpc.security_groups.all() if _.group_name == 'default')
print(f"VPC ({vpc.id}) default Security Group: {vpc_default_sg}")
eni = tuple(vpc.subnets.all())[0].create_network_interface()
eni_all_sgs = tuple(_['GroupId'] for _ in eni.groups)
print(f"ENI ({eni.id}) Security Group: {eni_all_sgs}")
eni.delete()

what you expected to happen: identical behavior for AWS EC2 and mock_ec2
what actually happens: create_network_interface creates ENIs with no security groups attached (impossible ENI irl)
python 3.6.6, moto 1.3.5

Thanks; I've changed the title and set this as a feature request for us to add.

This was implemented with #4307, and part of Moto >= 2.2.14.dev18
#4720 contains a specific unit test for this scenario to verify that it now works.


Deep links for Add Azure Storage process are broken

Related to #1494
Version
<IP_ADDRESS>327
Describe the bug
All azure storage deep links fail to load because the url which is generated is wrong (see #1494 )
To Reproduce
Steps to reproduce the behavior:

Add azure storage
Double click on the Azure Storage link

It fails to load (probably because the resourceGroup = resourceGroups and so it builds a bad url.
Expected behavior
The whole POINT of adding the resource is to let you navigate to them.
Screenshots

[bug]

Linking has changed for the Azure portal. These links all worked when first implemented then Azure decided to change them. The new links require the domain name e.g. microsoft.onmicrosoft.com whereas before they used the TenantId.
The problem with fixing this is that there does not appear to be an api that retrieves the domain name for a particular tenant/user combo.

Justin and I synced in person, right now there are a couple of things going on.

#1559 fixed the problem where the resource group was being stored incorrectly (issue #1494)

The a

the resource type used when constructing a deep link for Storage account is incorrect, it should be 'Microsoft.Storage/storageAccounts'

The id for a Storage Account saved via the emulator has all the correct information for connecting to a resource in the portal barring the tenantId.
Note: The id also contains additional information which takes a user to a different view than the simple overview for a resource when accessing via the Azure portal.

e.g.:
/subscriptions/<SUBSCRIPTION-GUID>/resourceGroups/<RESOURCE-GROUP-NAME>/providers/Microsoft.Storage/storageAccounts/<RESOURCE-NAME>/blobServices/default/containers/<DEFAULT-CONTAINER-NAME>
vs
/subscriptions/<SUBSCRIPTION-GUID>/resourceGroups/<RESOURCE-GROUP-NAME>/providers/Microsoft.Storage/storageAccounts/<RESOURCE-NAME>/overview


Rails process not running when uning with Unicorn

I run a Rails App on DigitalOcean using Dokku + nginx + PostgreSQL. The deployed App is running using WEBrick as a default server and I want to migrate to unicorn.
Gemfile
group :production do
  gem 'pg'
  gem 'unicorn'
end

I have used the Heroku configs for Unicorn
Procfile
web: bundle exec unicorn -p $PORT -c ./config/unicorn.rb

config/unicorn.rb
worker_processes Integer(ENV["WEB_CONCURRENCY"] || 3)
timeout 15
preload_app true

before_fork do |server, worker|
  Signal.trap 'TERM' do
    puts 'Unicorn master intercepting TERM and sending myself QUIT instead'
    Process.kill 'QUIT', Process.pid
  end

  defined?(ActiveRecord::Base) and
    ActiveRecord::Base.connection.disconnect!
end

after_fork do |server, worker|
  Signal.trap 'TERM' do
    puts 'Unicorn worker intercepting TERM and doing nothing. Wait for master to send QUIT'
  end

  defined?(ActiveRecord::Base) and
    ActiveRecord::Base.establish_connection
end

And this is how the log look like
root@oktobTest:~# dokku logs oktob
I, [2015-04-25T18:30:29.195191 #13]  INFO -- : Refreshing Gem list
config.ru:4:in `block in <main>': uninitialized constant ActiveRecord (NameError)
	from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/builder.rb:55:in `instance_eval'
	from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/builder.rb:55:in `initialize'
	from config.ru:1:in `new'
	from config.ru:1:in `<main>'
	from /app/vendor/bundle/ruby/2.1.0/gems/unicorn-4.8.3/lib/unicorn.rb:48:in `eval'
	from /app/vendor/bundle/ruby/2.1.0/gems/unicorn-4.8.3/lib/unicorn.rb:48:in `block in builder'
	from /app/vendor/bundle/ruby/2.1.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:764:in `call'
	from /app/vendor/bundle/ruby/2.1.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:764:in `build_app!'
	from /app/vendor/bundle/ruby/2.1.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:137:in `start'
	from /app/vendor/bundle/ruby/2.1.0/gems/unicorn-4.8.3/bin/unicorn:126:in `<top (required)>'
	from /app/vendor/bundle/ruby/2.1.0/bin/unicorn:23:in `load'
	from /app/vendor/bundle/ruby/2.1.0/bin/unicorn:23:in `<main>'

When I run the docker ps command I only see the PostgreSQL process and there is no process for the rails server.
root@oktobTest:~# docker ps
CONTAINER ID        IMAGE                     COMMAND                CREATED             STATUS              PORTS                     NAMES
fbdbb516b19c        postgresql/oktob:latest   "/usr/bin/start_pgsq   2 hours ago         Up 2 hours          <IP_ADDRESS>:49153->5432/tcp   elegant_ardinghelli

Maybe you need to require active record?

@josegonzalez Thanks so much Jose. I added active_record to config/unicorn.rb and it works
require 'rubygems'
require 'active_record'

worker_processes Integer(ENV["WEB_CONCURRENCY"] || 3)

And this is the result
Using docker ps
CONTAINER ID        IMAGE                     COMMAND                CREATED             STATUS              PORTS                     NAMES
4a43ac670998        dokku/oktob:latest        "/start web"           12 minutes ago      Up 12 minutes                                 grave_yonath
fbdbb516b19c        postgresql/oktob:latest   "/usr/bin/start_pgsq   6 days ago          Up 6 days           <IP_ADDRESS>:49153->5432/tcp   elegant_ardinghelli

Using htop

I think everything is working as expected.
Thanks