Filter sbol3.Components by role

I want to filter sbol3.Components by its role.
This is what I have set up to obtain this information:
import sbol3
import tyto

strains = []
components = [component for component in sbol_doc.objects if type(component) == sbol3.Component]
for component in components:
      if tyto.NCIT.get_uri_by_term('Organism Strain') in component.roles:
           strains.append(strain)

Is there a method that exists to do this kind of task? If not, I would like to request one. I would like to use this features for quickly filtering out Components that have a specific role.

I think this method would be nice too.
In the meantime, I'd note that you can make this more elegant by turning your for loop into a another list comprehension (something I've been enjoying learning about myself recently. :-)

Document.find_all() is probably what you want. It takes a callable as an argument, and then searches the entire document (not just the top level objects) gathering all objects for which the passed callable returns True. The typed signature is:
find_all(predicate: Callable[[Identified], bool]) -> List[Identified]

Here's how I would write your example using Document.find_all():
def find_by_role(doc: sbol3.Document, role: str) -> List[sbol3.Identified]:
    def has_role(obj: sbol3.Identified) -> bool:
        return isinstance(obj, sbol3.Component) and role in obj.roles

    return doc.find_all(has_role)

strains = find_by_role(sbol_doc, tyto.NCIT.get_uri_by_term('Organism Strain'))

Document.find_all() was added in pysbol3 1.0 alpha 7.

This would be useful to me as a user if this is supported in pysbol3. I believe other users adopting sbol would also find it useful as well to see this type of feature supported in the library.

@tramyn I've added this to the desired features list for beta. In the mean time, any time that you find yourself writing a useful helper function, it would be awesome if you contribute it back into the library via a pull request. @tcmitchell can then tweak and style-massage if needed to finalize.

Sorry, I'm confused. Document.find_all() is supported in the pysbole3 module. It is in the current version, 1.0a7. If you don't see it, maybe you need to update. My example above will work with the current version of pysbol3.

It's been a week with no updates. @jakebeal @tramyn is this ok to close? Are you using Document.find_all() to find Components by role?

@jakebeal  @tcmitchell , Do we need a fix here to implement what you described here:

def find_by_role(doc: sbol3.Document, role: str) -> List[sbol3.Identified]:
    def has_role(obj: sbol3.Identified) -> bool:
        return isinstance(obj, sbol3.Component) and role in obj.roles

    return doc.find_all(has_role)

as a method of Component class itself as Component.filter_by_roles() ?

@mohitdmak We've marked this with the "sbol-utilities" label, which means it ought to go as a function in sbol_utilities.component.py instead.


Specify Schema locations using filename

Heyho,
it seems like there is currently no way to specify schema files by their filename. Instead it is only possible to configure directories.
From GraphqlProperties.java:
private String[] appendSlashIfNecessary(String[] locations) {
			return Arrays.stream(locations)
				.map((location) -> location.endsWith("/") ? location : location + "/")
				.toArray(String[]::new);
		}

Hence this is impossible:
spring.graphql.schema:
    locations:
        # Subgraph's schema
        - classpath:schema/schema.graphqls
        # Federation-specific directives (shared across subgraphs)
        - classpath:schema/federation.graphqls
        # Common types (shared across subgraphs)
        - classpath:schema/Accommodation.graphqls
        - classpath:schema/AccommodationDeal.graphqls

I encountered this obstacle when trying to migrate from DGS to Spring GQL

Hello @bjoernmayer
Yes that's correct, those are meant to be locations, not fully resolved resources. I'm not sure I understand the use case though. Why point directly to resources and not locations? Are there schema resources in the same location that are not meant to be used? Why?

Hi @bclozel,
thank you for looking into this.
The main reason is Federation.
We are working with subgraphs in a Mono Repository. We have all of our shared types in a shared library. Each subgraph then picks only the types, that it needs and should expose in its schema.


Use usr/bin/env instead of /bin/bash for build script

please open with a fix if still relevant and will merge


Add CheckboxGroup component

🙋 Feature Request
We have a Checkbox component already, but it would be nice to support a CheckboxGroup component to more easily create a group of checkboxes, similar to RadioGroup. It should support labeling the entire group of checkboxes, along with controlling the selection state of the checkboxes as a group rather than individually.
💁 Possible Solution
API should be similar to RadioGroup. The value prop could accept an array of values, matching the value prop on each individual Checkbox. Many other props can be applied to the group and propagate to each individual checkbox (e.g. disabled/readonly state, validation state, etc.).
import {ValueBase, InputBase, Validation, LabelableProps} from '@react-types/shared';

interface CheckboxGroupProps extends ValueBase<string[]>, InputBase, Validation, LabelableProps {
  /** Name for the checkboxes when submitting via HTML form. Applies to all checkboxes automatically. */
  name?: string
}

interface CheckboxGroupState {
  /** Current selected values. */
  value: string[],
  /** Sets the selected values. */
  setValue(value: string[]): void,
  /** Adds a value to the set of selected values. */
  addValue(value: string): void,
  /** Removes a value from the set of selected values. */
  removeValue(value: string): void,
  /** Toggles a value in the set of selected values. */
  toggleValue(value: string): void
}

declare function useCheckboxGroupState(props: CheckboxGroupProps): CheckboxGroupState;

interface CheckboxGroupAria {
  /** Props for the checkbox group label element. */
  labelProps: HTMLAttributes<HTMLElement>,
  /** Props for the group element */
  groupProps: HTMLAttributes<HTMLElement>
}

declare function useCheckboxGroup(props: CheckboxGroupProps): CheckboxGroupAria;

We may also want to support additional Spectrum-specific options like layout orientation, emphasized visual state, labeling visual options, etc.
Example:
<CheckboxGroup label="Favorite sports">
  <Checkbox value="running">Running</Checkbox>
  <Checkbox value="swimming">Swimming</Checkbox>
  <Checkbox value="soccer">Soccer</Checkbox>
</CheckboxGroup>

HTML structure:

Favorite Sports

In terms of CSS, we should be able to use the Spectrum FieldGroup CSS for this (same as used in RadioGroup).
🧢 Your Company/Team
RSP

I can look into this next week. I'm mostly interested in @react-aria and @react-stately parts of this though.

@Andarist that would be awesome! There's no requirement to implement the Spectrum-specific parts. You could just make a basic example component using the hooks and use that in the storybook/tests for now, and we can take care of the Spectrum part later. 😄

I've started working on this but I've encountered conceptual problems.
Right now useCheckbox & co are implemented on top of useToggle & co. The problem is that because of this interfaces of useRadio & useCheckbox differs quite a bit - useRadio requires RadioGroupState while useCheckbox requires ToggleState (which is intended to handle standalone toggle/checkbox).
Given the architecture of @react-aria project and how things work together, I have 2 ideas on how we could solve this:

accept groupState in useToggle and compute returned { isSelected, setSelected } based on it, with an addition of using useControlledState differently when groupState is provided. It ain't perfect because useToggleState already handles controlled/uncontrolled scenarios based on the first argument (props)
introduce a new hook - useGroupedCheckbox which would accept groupState and return the same interface as useToggleState, so that could be fed to useCheckbox. This would probably result in a more dedicated API and thus its implementation would be more intuitive.

Thoughts?

Good questions. Could you implement it by making the checkboxes controlled? e.g. pass isSelected={state.isSelected(value)} and an onChange handler to each checkbox in the group, where state.isSelected is a function that returns whether a given value is selected? Or you could use a context consumed in the Checkbox component that gets the group state and passes isSelected and onChange options to useToggleState maybe, as if it were controlled?


[Feature Request] ".lcr all" include IDs

Please make it so .lcr all includes IDs with each response.
Example:
{
    "Trigger": "!!bread",
    "Responses": [{
      "text":"https://i.imgur.com/gD804x2.jpg",
     "ID": 120}
    ]
  },

Warning: That image is NSFW. Open at your own risk. ¯\_(ツ)_/¯
As for formatting...I don't know how you'd need to set it, just offering a random (probably shitty) example.

done babe


Update dependencies to support Apple M1, fix Windows CI LLVM paths

Motivation
Ublock development on Apple M1.

Solution

Update dependencies.

Related Issues

https://github.com/ZcashFoundation/zcash_script/pull/20
https://github.com/rust-rocksdb/rust-rocksdb/pull/506#issuecomment-814675349

Same windows clang issue as in zcash_script https://github.com/ZcashFoundation/zcash_script/pull/20 🤦 Will do proper fix there first.

It looks like it might be a while before GitHub has M1 CI runners:
https://github.com/actions/virtual-environments/issues/2187
But we can test manually until then.

Yeah, M1 still not publicity available in GitHub CI 😞
I think it's okay for some time do not to test on M1 in CI. At least these changes allow to use M1 for development.

Updated to latest crates 🎉

Let's fix the hard-coded block name, and then we're good to merge.
You can also move the lexical-core change to #2026 if you want, but I don't want to block on that.

Oops sorry this review was meant for #2018. I'll just go fix that all up now.

Thanks for all your hard work on this PR, and the zcash_script PR!

I uodated the title to describe what the merged PR actually does, so our changelog is accurate.
There's no need to match the dependabot title format for future PRs. Having different PR titles from dependabot actually helps us identify manual changes in the changelog.


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-k8s-27-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3973

Questions ?
Please refer to the Backport tool documentation


No animation and arrows, when not included in calculations.

@JonahKr I managed to get your fantastic card to work exactly as I wanted it to.
Impressing card indeed, it now matches how my energy is created and used and stored on the grid.
I explain the Icons, for better understanding of my request.
Solar is what is currently produced by my solar cells
Grid is what is currently sendt to grid, (green) or collected from grid (red)
From/Solar is what is directly outside grid, currently used of the produced energy  from my solar cells
(Fase 3) as my Solar cells are only 2 fases, the 3rd fase always draw power from the grid, no matter what is produced from solar cells.
Home is the total energy consumption currently taking place.
Now to the isssue:
Grid/Bank, is what I have stored on the grid, green in my favor, red in the energy company's favor.
As you can see the measurement is kWh, and this field is not included in any calculations, as it is a pure figure, that constantly updates, according to production/energy usage, to from the grid.
This is a special Danish solution, where if your sun cells were ordered before november 2012, you could use the grid for storage of the production you currently not use, and draw from this when the sun is down. (This solution does not exist anymore), but in my case is valid for another 12 years.)
Now to the request:
I would really like a feature to turn the arrows off, when not including the Icon data in the calculations. Meaning that it only will contain the figures, and not the triangles.
So it looks like this:

Hey there @pesor 👋 ,
Glad you still enjoy my card 😉
I think i know what you mean and actually like it alot. This should be easily implementable so maybe i get it done later today.
Thanks for the Idea and take care!
Jonah

Hey there @pesor 👋 ,
Glad you still enjoy my card 😉
I think i know what you mean and actually like it alot. This should be easily implementable so maybe i get it done later today.
Thanks for the Idea and take care!
Jonah

Okay this should do the job. However it isn't centered as nicely as in your example. This will change automatically once i refactor the CSS part.

Okay this should do the job. However it isn't centered as nicely as in your example. This will change automatically once i refactor the CSS part.


[BUG] Default tutorial doesn't run once containerized

Describe the bug
A clear and concise description of the bug.
The default tutorial here https://github.com/microsoft/promptflow/ creates a basic chat flow. This can be run locally. Once it's built and converted into a container it will not run
How To Reproduce the bug
Steps to reproduce the behaviour, how frequent can you experience the bug:

Follow the tutorial to create the flow and create connection/ref deployment to LLM (in my case AZ AI Service), then build the flow to create "dist" folder
Use Docker to build an image from the dist folder
Docker run to test the built image

Expected behaviour
A clear and concise description of what you expected to happen.
Simple flow runs through UI access
Screenshots
If applicable, add screenshots to help explain your problem.
Following shows the error (see context below)
{'node_name': 'chat', 'error_type_and_message': "(EmptyLLMApiMapping) LLM api mapping is empty, please ensure 'promptflow-tools' package has been installed."}
(note the connection is created and the flow will run in VS Code locally e.g. through pf test)
Running Information(please complete the following information):

Promptflow Package Version using pf -v: [e.g. 0.0.102309906]
promptflow                       1.1.1
Operating System: [e.g. Ubuntu 20.04, Windows 11]
W11
Python Version using python --version: [e.g. python==3.10.12]
Python 3.11.3
Additional context
Add any other context about the problem here.

2023-12-08 15:56:08 start promptflow serving with worker_num: 8, worker_threads: 1
2023-12-08 15:56:09 [2023-12-08 15:56:09 +0000] [22] [INFO] Starting gunicorn 20.1.0
2023-12-08 15:56:09 [2023-12-08 15:56:09 +0000] [22] [INFO] Listening at: http://<IP_ADDRESS>:8080 (22)
2023-12-08 15:56:09 [2023-12-08 15:56:09 +0000] [22] [INFO] Using worker: sync
2023-12-08 15:56:09 [2023-12-08 15:56:09 +0000] [23] [INFO] Booting worker with pid: 23
2023-12-08 15:56:09 [2023-12-08 15:56:09 +0000] [25] [INFO] Booting worker with pid: 25
2023-12-08 15:56:09 [2023-12-08 15:56:09 +0000] [24] [INFO] Booting worker with pid: 24
2023-12-08 15:56:09 [2023-12-08 15:56:09 +0000] [26] [INFO] Booting worker with pid: 26
2023-12-08 15:56:09 [2023-12-08 15:56:09 +0000] [27] [INFO] Booting worker with pid: 27
2023-12-08 15:56:09 [2023-12-08 15:56:09 +0000] [28] [INFO] Booting worker with pid: 28
2023-12-08 15:56:09 [2023-12-08 15:56:09 +0000] [29] [INFO] Booting worker with pid: 29
2023-12-08 15:56:09 [2023-12-08 15:56:09 +0000] [30] [INFO] Booting worker with pid: 30
2023-12-08 15:57:31 [2023-12-08 15:57:31,820][promptflow][ERROR] - Promptflow serving app error: {'message': "Tool load failed in 'chat': (EmptyLLMApiMapping) LLM api mapping is empty, please ensure 'promptflow-tools' package has been installed.", 'messageFormat': "Tool load failed in '{node_name}': {error_type_and_message}", 'messageParameters': {'node_name': 'chat', 'error_type_and_message': "(EmptyLLMApiMapping) LLM api mapping is empty, please ensure 'promptflow-tools' package has been installed."}, 'referenceCode': <ErrorTarget.EXECUTOR: 'Executor'>, 'code': 'UserError', 'innerError': {'code': 'EmptyLLMApiMapping', 'innerError': None}}
2023-12-08 15:57:31 [2023-12-08 15:57:31,823][promptflow][ERROR] - Promptflow serving error traceback: Traceback (most recent call last):
2023-12-08 15:57:31   File "/opt/conda/envs/promptflow-serve/lib/python3.9/site-packages/promptflow/executor/_tool_resolver.py", line 146, in resolve_tool_by_node
2023-12-08 15:57:31     return self._resolve_llm_node(node, convert_input_types=convert_input_types)
2023-12-08 15:57:31   File "/opt/conda/envs/promptflow-serve/lib/python3.9/site-packages/promptflow/executor/_tool_resolver.py", line 225, in _resolve_llm_node
2023-12-08 15:57:31     raise EmptyLLMApiMapping()
2023-12-08 15:57:31 promptflow.executor._errors.EmptyLLMApiMapping: LLM api mapping is empty, please ensure 'promptflow-tools' package has been installed.
2023-12-08 15:57:31
2023-12-08 15:57:31 The above exception was the direct cause of the following exception:
2023-12-08 15:57:31
2023-12-08 15:57:31 Traceback (most recent call last):
2023-12-08 15:57:31   File "/opt/conda/envs/promptflow-serve/lib/python3.9/site-packages/flask/app.py", line 867, in full_dispatch_request
2023-12-08 15:57:31     rv = self.dispatch_request()
2023-12-08 15:57:31   File "/opt/conda/envs/promptflow-serve/lib/python3.9/site-packages/flask/app.py", line 852, in dispatch_request
2023-12-08 15:57:31     return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
2023-12-08 15:57:31   File "/opt/conda/envs/promptflow-serve/lib/python3.9/site-packages/promptflow/_sdk/_serving/app.py", line 102, in score
2023-12-08 15:57:31     app.init_invoker_if_not_exist()
2023-12-08 15:57:31   File "/opt/conda/envs/promptflow-serve/lib/python3.9/site-packages/promptflow/_sdk/_serving/app.py", line 65, in init_invoker_if_not_exist
2023-12-08 15:57:31     self.flow_invoker = FlowInvoker(
2023-12-08 15:57:31   File "/opt/conda/envs/promptflow-serve/lib/python3.9/site-packages/promptflow/_sdk/_serving/flow_invoker.py", line 64, in init
2023-12-08 15:57:31     self._init_executor()
2023-12-08 15:57:31   File "/opt/conda/envs/promptflow-serve/lib/python3.9/site-packages/promptflow/_sdk/_serving/flow_invoker.py", line 106, in _init_executor
2023-12-08 15:57:31     self.executor = FlowExecutor._create_from_flow(
2023-12-08 15:57:31   File "/opt/conda/envs/promptflow-serve/lib/python3.9/site-packages/promptflow/executor/flow_executor.py", line 233, in _create_from_flow
2023-12-08 15:57:31     resolved_tools = [tool_resolver.resolve_tool_by_node(node) for node in flow.nodes]
2023-12-08 15:57:31   File "/opt/conda/envs/promptflow-serve/lib/python3.9/site-packages/promptflow/executor/flow_executor.py", line 233, in
2023-12-08 15:57:31     resolved_tools = [tool_resolver.resolve_tool_by_node(node) for node in flow.nodes]
2023-12-08 15:57:31   File "/opt/conda/envs/promptflow-serve/lib/python3.9/site-packages/promptflow/executor/_tool_resolver.py", line 158, in resolve_tool_by_node
2023-12-08 15:57:31     raise ResolveToolError(node_name=node.name, target=e.target, module=e.module) from e
2023-12-08 15:57:31 promptflow.executor._errors.ResolveToolError: Tool load failed in 'chat': (EmptyLLMApiMapping) LLM api mapping is empty, please ensure 'promptflow-tools' package has been installed.
2023-12-08 15:57:31

Hi @bengimblett ,
Thanks for your feedback, promptflow-tools is indeed a necessary package when using promptflow, you can see they are both mentioned in the default installation guideline:

Thanks @0mza987 ... yes ... as a 'newbie' to this I wasn't sure if the "promptflow-tools" was only required for the developer and not the distribution. Thank you for confirming

@bengimblett You're welcome! We appreciate receiving feedback from the community, and we're always open to hearing more. Feel free to share any additional feedback or suggestions you may have. We value your input and look forward to hearing from you again soon.


Cannot connect SSH with Putty private key (converting to OpenSSH .pem works)

Hey there,
Im trying to connect to my Unraid Server via SSH and Key(.ppk) with passphrase.
I got no issue with the Apps like WebSSH and Terminal to connect but i cannot get it to work with codeapp
In the Codeapp itself i get: Authentication Error
and the following log on my unraid server
1. May 10 23:56:37 UNRAID sshd[6004]: Connection from <IP_ADDRESS> port 49952 on <IP_ADDRESS> port 22 rdomain ""
2. May 10 23:56:37 UNRAID sshd[6005]: Connection from <IP_ADDRESS> port 49953 on <IP_ADDRESS> port 22 rdomain ""
3. May 10 23:56:37 UNRAID sshd[6005]: Received disconnect from <IP_ADDRESS> port 49953:11: NMSSH: Disconnect [preauth]
4. May 10 23:56:37 UNRAID sshd[6004]: Received disconnect from <IP_ADDRESS> port 49952:11: NMSSH: Disconnect [preauth]
5. May 10 23:56:37 UNRAID sshd[6004]: Disconnected from authenticating user root <IP_ADDRESS> port 49952 [preauth]
6. May 10 23:56:37 UNRAID sshd[6005]: Disconnected from authenticating user root <IP_ADDRESS> port 49953 [preauth]

SOLVED: I fixed the issue by converting the key to openssh(.pem) and it just works

Thanks for sharing this. I will take a look why Putty key does not work as expected.


Fix crash when g_expr is used in lazy variable

https://github.com/serge-sans-paille/pythran/pull/883/commits/05cdeb467b4b32d52e69e09d1789ebac76936058#diff-7f333f9dcc1324cccd0622fd5396cae3R760
Duplicate test?

Thans @diorcety

No problem. Thanks to you


Corrections with SBC Names in Multi-Tenant Failover section

The the last section, regarding multi-tenant failover, the following naming conventions are given that do not match the article above:
customer1.sbc1.contoso.com
customer1.sbc2.contoso.com
To match the naming convention in the rest of the article, these could read:
customer1-sbc1.customers.contoso.com
customer1-sbc2.customers.contoso.com
Also the section has a type and currently says "muti-tenant" instead of "Multi-tenant"

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

ID: 1cb0c2ef-6274-9167-ecc6-3695d7460a8d
Version Independent ID: aacf7318-02fc-a1c3-369c-65e6936fdb3c
Content: Configure Session Border Controller - Multiple tenants - Microsoft Teams
Content Source: Teams/direct-routing-sbc-multiple-tenants.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

@thecathcart Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@thecathcart . Thanks for pointing out. I wille fix these today


Problems getting internal and external access to work

Hello!
I just found REMI this week and am really excited about it. My goal is to create a little gui for a python script running on my raspberry pi. The raspberry pi is behind a router and has dyndns domain like subdomain.ddns.net.
My problem is that I managed to set up REMI to either be able to access remi html server from outside via the dyndns subdomain or internally (at home) from another pc via the ip adress of the raspberry (<IP_ADDRESS>:8081).
The two variants I came up with:
start(myApp, debug=False, address='<IP_ADDRESS>', port=8081, update_interval=0.1) --> internal access, but no external access possible
start(myApp, debug=False, address='<IP_ADDRESS>', port=8081, update_interval=0.1, host_name='subdomain.ddns.net') --> external but no internal access possible
I tried more or less all settings and didn't come up with a solution for both access ways. Could you please help me with this or is it just not possible?
Thank you very much and kind regards!

Hello @shirtomatik, both start calls are ok, the second one of course allows access by hostname. If the hostname gets not resolved locally, it could be a router config problem. However a pretty simple test you can do is:
-replace host_name param value with your public external ip address
-connect to that public ip
You should be able to connect from everywhere.

Hello @dddomodossola,
thank you for your fast answer. In the meantime I am pretty sure that it has something to do with my speedport router. I read something about that it doesn't allow external access from internal pc (nat loopback).
The weird thing is that if I ping the different addresses I always get an answer. Sometimes I also can open the server, but the websocket can't be open so that the blue loading screen stays there forever.
Here are the results from my tests:
start(MyApp, debug=True, address='<IP_ADDRESS>', port=8082, host_name='subdomain.ddns.net')
--> internal access via <IP_ADDRESS>:8082: screen with blue loading icon, app in background, websocket error, event code: 1006
--> external access via subdomain.ddns.net:8082: possible and working
start(MyApp, debug=True, address='<IP_ADDRESS>', port=8082)
--> internal access via <IP_ADDRESS>:8082: possible and working
--> external access via subdomain.ddns.net:8082: screen with blue loading icon, app in background
start(MyApp, debug=True, address='<IP_ADDRESS>', port=8082, host_name='PUBLIC_IP')
--> internal access via PUBLIC_IP:8082: not possible, connection refused
--> external access via PUBLIC_IP:8082: possible and working
Unfortunately I see no chance to create a workaround for this issue. Is there a possibility for REMI to work like the first and second option with one start config? That means the server would be accessible via internal ip or trough external address. Otherwise I will have to decide which access is more important for me...

@shirtomatik I now made an update to automatically detect the host to connect to. The parameter host_name is now deprecated. It should solve your problem.
Please let me know if this works for you ;-)

@shirtomatik This is a long shot, but do you remember the final start() config you used to get both external and internal access working?


Missing dependency 'typing_extensions'

Expected Behavior

When installing dapr sdk, a project using sdk should run with all required dependencies
Actual Behavior

A project using the sdk do not run because of a missing dependency
Steps to Reproduce the Problem

Use a fresh computer without any pre-installed python libraries
Follow the doc until https://docs.dapr.io/getting-started/quickstarts/pubsub-quickstart/#step-4-publish-a-topic
Following the step 4, the application cannot start

Release Note

RELEASE NOTE: FIX dependencies resolution
Note for maintainers
I am not a python developer, I do not know how pip resolve dependencies. So I cannot propose quickly a PR to resolve this issue.
Anyway, thanks for your job !

Sorry for the delay - I am releasing Dapr Python SDK 1.9.1 right now to address this.

Created #546 to avoid this in the future.
This was closed by #545, right?

Created #546 to avoid this in the future.
This was closed by #545, right? And #544 is a duplicate of this one.

Correct. This is resolve in SDK 1.9.1


ServiceTemplate to provide Service type and annotations

Be able to provide a Service template in the MariaDB CRD to customize how it is exposed in the cluster. For example, if we wanted to expose it using Metallb:
apiVersion: mariadb.mmontes.io/v1alpha1
kind: MariaDB
metadata:
  name: mariadb
spec:
    ....
    service:
       type: LoadBalancer
       annotations:
            metallb.universe.tf/address-pool: sandbox

It should default to type ClusterIP and not annotations.

Hi @mmontes11 ,
Can I raise a PR for this?
Thanks

@ksankeerth yes please, go ahead!
Give me a shout if you need help with anything, happy to help!


follow LoggerSilence changes

LoggerSilence have to invoke after_initialize. (from activesupport v4.2.6)
https://github.com/rails/rails/blob/v4.2.6/activesupport/lib/active_support/logger_silence.rb#L14

@level instance variable is not change at LoggerSilence.silence block. (from activesupport v4.2.6)
https://github.com/rails/rails/blob/v4.2.6/activesupport/lib/active_support/logger_silence.rb#L31
https://github.com/ruby/ruby/blob/trunk/lib/logger.rb#L421

Errors on travis depend on #24.

ping

It was agreed that the logger silence changes were a mistake, it should be reverted. The correct place to fix this is in Rails and not here I opened an issue to track the issue in Rails https://github.com/rails/rails/issues/24263

While we're waiting on that to get resolved, we can fix this in Rails by switching to a happier path. Instead of using the stdlib logger, let's use the ActiveSupport::Logger instead, it already has those modules included and the correct interface implemented. Can you make that change?

@schneems Sure. but it seems already done by @tagliala :yay:

Thank you all for your help changes have been released in 0.0.5


Update docs

Update docs to reflect recent changes

i dont know how to append data to arrays or strings too((...
like that?
shotz.1?[1].title.append(self.titlexample)
thanks

I'm not sure what youre trying to do, could you provide more info?

i trying to create app which should view shots ,with description and titles ,user should be able to like them, commenting etc
i have problems viewing information . i need to save commands like shotz.1?[1].title  respond into string, or, save the images urls at array .
i try create string title , and storage there result of shotz.1?[1].title by adding .append but its not work

why not save the data received in array and use it according (in a collection or tableView)? The example below is using a UICollectionView (there's plenty of tutorials on the internet on how to use a collectionview or tableview)
  var shots = [ShotsDS]()

//View did load or whatever your loading the data from
    ShotsDS.getShots(perPage: 50, page: page){
      data in
      if let shts = data.1{
        shts.forEach{
          self.shots.append($0)
        }
        self.collectionView?.reloadData()
      }
    }

//Collectionview

  override func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell {
let cell = collectionView.dequeueReusableCell(withReuseIdentifier: "cell", for: indexPath) as! ImageCell

let url = shots[indexPath.row].images.normal
//Set your image
cell.titleLabel.text = shots[indexPath.row].title
}


Reduce unused exports

@rebornix and I were wondering if there is any dead code in the VS Code codebase, and one idea was to detect unused exports across the codebase, since unused variables are flagged by the compiler but unused exports are not.
I ran ts-unused-exports on our sources and generated the following list. I've already done a pass to remove some false positives but apologies if several remain.
NB: The primary purpose of this issue is to identify unused functions and classes which aren't being picked up by the compiler because they're exported and which can be safely deleted from our sources to reduce our bundle size. A secondary benefit is to remove unused types and interfaces, e.g. anything which was exported at one point and then ceased to be referenced from other files (which more impacts compile time for dev workflows and pipeline runs, and maybe TS server analysis time, but has no direct impact on bundle size since types are erased).
If you export a type or interface that is not currently actively imported, but is used in the public API of a class that you expose, then it's quite likely that you want to keep that type/interface exported and need not un-export it as part of this issue.
Please feel free to remove your assignment if you find that this isn't valuable.

For the other files attached to my name, I removed the export, but those symbols are all still used.

I wenrt through the list. Removed the ones I marked with :heavy_check_mark:.  I kept the ones I marked with 'api', as these are types that are part of an exported API and should stay available. They are also just types and interfaces, so have no impact on the built bits


Make breaking changes called out in the CHANGELOG

This is currently scheduled for Ambassador 0.40 or Monday, August 13, 2018, whichever is earlier.
The Ambassador CHANGELOG calls out some breaking changes that we've wanted to make for awhile:

Change the use_default_address default to True
Remove all legacy support for the authentication Module (everyone has hopefully switched to the AuthService resource type)
Drop the statsd container from our default YAML
Drop support for TLS configuration in the ambassador Module (all TLS configuration should happen in the tls Module)

This is currently scheduled for Ambassador 0.40 or Monday, August 13, 2018, whichever is earlier.

Can this be closed?

Closing. We've done almost all of this; I'll open a new issue for the last bit of TLS config since it's actually not so much "execute this breaking change" as "we need to figure out what's missing".


iPad: tapping on story loads different story

See this video. Fresh launch, tapping on a story that isn't in the first page of stories loads the wrong story.
https://github.com/samuelclay/NewsBlur/assets/44229/64c6930f-6d97-4afc-b9c8-e0eeb1e060b8

I'm unable to reproduce this; no matter how many times I launch and/or scroll to load more then select a row (with the same unread intelligence mode as you), it displays the correct story.
Does this happen regularly for you, or was this a one-off? Any clues on how to reproduce it?

Just a note, this is happening on macOS at exactly the same frequently, which is to say not particularly often, but at least once a week on daily usage.

It feels like a race condition between loading another page of stories and recalculating which story goes where in our "controller" array.

Is this fixed in version 13.1.6 (build 297), thanks to #1920 (Wrong story being selected)? It feels like a similar situation.


combining both points and lines into a unified framework

Hi, thanks for sharing your work.
In the paper, you mentioned combining both points and lines into a unified framework.Is this work you are doing? What do you think are the difficulties of this work

Yes, I am currently investigating this unified approach, together with someone else. We will probably release the final version on Github soon and I can let you know about it.
The challenges are mainly to keep a compact network, while maintaining the performance of the points or lines only approaches.

Are there any relevant papers available for reference?

Not that I know of...

Yes, I am currently investigating this unified approach, together with someone else. We will probably release the final version on Github soon and I can let you know about it.
The challenges are mainly to keep a compact network, while maintaining the performance of the points or lines only approaches.

I am also interested in this matter and I think it makes a lot of sense. May I ask if you are working on the SOLD2 code? Will there be a corresponding paper published for the upcoming code release?

For now it is a student project that I am supervising, and there is no targeted publication. I don't see enough novelty to publish it for now, so it might just end up as a released code on Github. Part of it is re-using ideas of SOLD2 and other previous baselines as well.

Hi @2017DEVIL , I forget to notify you, but the joint point and line framework has been released here: https://github.com/hkkkpang/Joint-PL-network
I hope this kind be useful to you!


fix: cli output trunc

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

fix https://github.com/kcl-lang/kcl/issues/1739
fix: cli output trunc

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 14.607%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/options/run.go
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>7:
0.0%

Covered Lines:
91

Relevant Lines:
623

💛  - Coveralls


Size of feature_names error, should equal with total number of features

Please search your question on previous issues, stackoverflow or other search engines before you open a new one.
For bugs and unexpected issues, please provide following information, so that we could reproduce on our system.
Environment info
Operating System: win10 64bit
CPU: i5
R version: microsoft R 3.32
when i run the demo:
require(lightgbm)
require(methods)
data(agaricus.train, package = "lightgbm")
data(agaricus.test, package = "lightgbm")
train <- agaricus.train
test <- agaricus.test
class(train$label)
class(train$data)
print("Training lightgbm with sparseMatrix")
bst <- lightgbm(data = train$data,
label = train$label,
num_leaves = 4,
learning_rate = 1,
nrounds = 2,
objective = "binary")
Error Message:
Error in lgb.call("LGBM_DatasetCreateFromCSC_R", ret = handle, private$raw_data@p,  :
api error: Size of feature_names error, should equal with total number of features
i had succedd in runing this program ever, so, what is the problem?
thank you!

Just test it on latest code, and it runs successfully.
Can you try re-install the latest code and restart R, then test again ?

        Ok I wii try, thank you very much Sent from Mail Master
        On 05/22/2017 18:43, Guolin Ke wrote: Just test it on latest code, and it runs successfully.

Can you try re-install the latest code and restart R, then test again ?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/Microsoft/LightGBM","title":"Microsoft/LightGBM","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/Microsoft/LightGBM"}},"updates":{"snippets":[{"icon":"PERSON","message":"@guolinke in #540: Just test it on latest code, and it runs successfully. \r\nCan you try re-install the latest code and restart R, then test again ? "}],"action":{"name":"View Issue","url":"https://github.com/Microsoft/LightGBM/issues/540#issuecomment-303064854"}}}

        I need to install version v2?Sent from Mail Master
        On 05/22/2017 18:43, Guolin Ke wrote: Just test it on latest code, and it runs successfully.

Can you try re-install the latest code and restart R, then test again ?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/Microsoft/LightGBM","title":"Microsoft/LightGBM","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/Microsoft/LightGBM"}},"updates":{"snippets":[{"icon":"PERSON","message":"@guolinke in #540: Just test it on latest code, and it runs successfully. \r\nCan you try re-install the latest code and restart R, then test again ? "}],"action":{"name":"View Issue","url":"https://github.com/Microsoft/LightGBM/issues/540#issuecomment-303064854"}}}

@yangdi92 the latest master branch.


fix: move vendor back into src

What does this change?

moves vendor back under src, with a __ prefix to keep it separate from our own code
converts vendor files to JS, since TS isn't catching anything in there

Why?
multiple rootDirs in the tsconfig meant everything was published under the directory it lives in (src, vendor etc). this broke importing.
@ioanna0 and i mulled this over and decided we could either do this or change the main/module paths. that felt wrong, since it's not src at that point, it's our compiled artefact.
also, vendor code is source code of this package, just not ours.
this attempts to mark it as such while keeping a clean published artefact
we should probably add some validation for the built package before publishing it

:tada: This PR is included in version 0.8.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Evinse support for java with gradle project - part 2

Testing procedure
Let's focus on only java with gradle projects to start with.
git clone https://github.com/CycloneDX/cdxgen
git checkout feature/evinse-gradle
npm install
export CDXGEN_DEBUG_MODE=debug

# Build the java project with gradle
cd <path to code>
mvn compile

# Generate an SBoM for a Java project with cdxgen
node bin/cdxgen.js -t java -o bom.json <path to code>
# Ensure java >17 is installed. Needed for any language type.
node bin/evinse.js -i bom.json -o bom.evinse.json <path to code>
# Interact with repl
node bin/repl.js bom.evinse.json

# Try some repl commands
# .print
# .occurrences

What to report

[ ] Crashes/hangs when collecting evidence for Java projects
[ ] SQLite3 installation errors
[ ] Slow performance. Report the first scan time you see with the number of components in SBoM and lines of code in the application
[ ] If any package was not listed under evidence.occurrences or has incorrect filenames or line numbers

@theold190 I have rewritten the logic for maven-cache. Could you test your use case with this branch and let me know how it looks?
https://github.com/CycloneDX/cdxgen/issues/441

@prabhu thanks for the fixes! I am on vacations right now, so not able to do the tests. Can check after 28th of August when I am back from vacations.

I have tested v9.6.1 of the tool and it produces the list of dependencies. A huge improvement comparing to v9.3.1 for our project, Thanks for the fix!


cython  prange

Describe the bug
I need to compute a big matrix. I want to use prange in cython to speed up the for loop.
The raw data is a numpy object consisting of an irregular array. (Array of object type, np.ndarray[object, ndim=1])
The raw data is shown below:

Each row is an array. Each data has a different number of rows but the same number of columns. such as 10×36, 5×36, 19×36, 105×36……
At compile time, the following error occurs:

Code to reproduce the behaviour:
# example code

for m in range(nSeg):
for n in prange(m, nSeg, nogil=True, schedule='static'):
distmat[m, n] = calculate_distance_C(SegParas[m], SegParas[n], sigma)
Expected behaviour
I wanted to speed up the calculations with prange.
OS
Windows，Linux
Python version
3.10.12 / 3.11.5
Cython version
3.0.0
Additional context
No response

The bug tracker is for bug reports or feature requests - please ask support questions on the cython-users mailing list
It is not possible to operate on Python objects in a nogil block so this won't work. You might consider using c++ (via Cython) and vector[vector[double]] for an irregular array instead.


Updates option docs with little hints

This pull request includes a

[x] Docs improvement

The following changes were made

adds some notes where to find data structure when using ajax

Kind regards
Florian

Thanks! I've added something similar to the docs.


Error when archiving in XCode: EMFILE

This error has been reported before, but the solution did not help me.
Description
I am seeing this error when archiving from XCode. I have not encountered this issue before and have tried reverting my code:
node /.../node_modules/react-native/cli.js bundle --entry-file index.js --platform ios --dev false --reset-cache --bundle-output ... --assets-dest ...

warning: the transform cache was reset.
                 Welcome to React Native!
                Learn once, write anywhere

events.js:288
      throw er; // Unhandled 'error' event
      ^

Error: EMFILE: too many open files, watch
    at FSEvent.FSWatcher._handle.onchange (internal/fs/watchers.js:127:28)
Emitted 'error' event on NodeWatcher instance at:
    at NodeWatcher.checkedEmitError (/Users/.../node_modules/sane/src/node_watcher.js:143:12)
    at FSWatcher.emit (events.js:311:20)
    at FSEvent.FSWatcher._handle.onchange (internal/fs/watchers.js:133:12) {
  errno: -24,
  syscall: 'watch',
  code: 'EMFILE',
  filename: null
}

I have tried the following steps to fix:

Reinstall Watchman (sudo port uninstall watchman, sudo port install watchman, reboot) (this has been the solution on similar issues but has not helped me)
Reset Cocoapods (Deintegrate, rm Pods/, reinstall etc)
Reset Watchman Cache (watchman watch-del-all)
Clean Build Folder in XCode

If I run the bundle command manually from terminal it succeeds, it only seems to have a problem when archiving from XCode.
I also run npx react-native doctor and there is a ✅ next to Watchman
Versions:
Environment: macOS Catalina
React Native CLI Version: 4.10.1
Node Version 12.16.1
React Native Version: 0.63.2
Watchman Version: 4.9.0

Interesting development. If I manually run the xcodebuild command the archive succeeds:
xcodebuild -workspace ... -scheme ... archive

Isn't this basically identical to Product > Archive in XCode? Are there any explanations for this.

same issue ...

I am getting the same error.  The program builds fine in the command line but has this error when built in xCode.

Same issue here.

still exist RN 0.64. tried nodejs 14 / 16. Watchman installed. OS BigSur. chip M1
ulimit -a:
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
file size               (blocks, -f) unlimited
max locked memory       (kbytes, -l) unlimited
max memory size         (kbytes, -m) unlimited
open files                      (-n) 524288
pipe size            (512 bytes, -p) 1
stack size              (kbytes, -s) 8176
cpu time               (seconds, -t) unlimited
max user processes              (-u) 2000
virtual memory          (kbytes, -v) unlimited

Same issue on Macbook M1. The issue in my opinion is that the metro bundler does not start up inside a separate new terminal like it does when I am archiving in my intel macbook. The metro bundler attempts to start inside the xcode where it does not let watchman work properly so this error gets thrown.

This got fixed recently in newest version of watchman. The problem was with bug in fsevents library for mac m1 which got fixed in latest release. Update your watchman, reinstall your project, pods everything and things should work

@ekram21 I upgraded watchman, yarn install, and npx pod-install and I am still getting the same error.  Am I missing something?

@ekram21 I upgraded watchman, yarn install, and npx pod-install and I am still getting the same error. Am I missing something?

I don't know your environment and what device you are using but I will list the things to keep in mind:

This is for MAC M1 Silicon
Latest Versions of Node, React Native being used
Latest Versions of Watchman and Brew being used
I did not use Yarn. NPM install used to install all node modules and navigated to iOS folder and just used pod install - consult these thread if pod install doesn't work: https://github.com/CocoaPods/CocoaPods/issues/10349
Make duplicate terminals with one running on Rosetta and the other native.
Brew should be installed with native terminal, and then watchman after
After this you need open Settings - Security Preference and give complete disk access to xcode, watchman, terminal and any other tools being used in your environment.
Your project cannot be under desktop or downloads. Make sure it is under /Users/myname/

Also look at this thread: https://github.com/facebook/metro/issues/668
These are the steps I followed to make the project archive in xcode. Note that the project would compile fine in simulator outside of xcode before but the above steps finally got it to archive in xcode where it was failing

@ekram21 which watchman version are you using?

any updates on this issue?
I am getting the same issues
`events.js:377
throw er; // Unhandled 'error' event
^
Error: EMFILE: too many open files, watch
at FSEvent.FSWatcher._handle.onchange (internal/fs/watchers.js:178:28)
Emitted 'error' event on NodeWatcher instance at:
at NodeWatcher.checkedEmitError (/Users/chaohuichen/Desktop/PCC/fillup/node_modules/sane/src/node_watcher.js:143:12)
at FSWatcher.emit (events.js:400:28)
at FSEvent.FSWatcher._handle.onchange (internal/fs/watchers.js:184:12) {
errno: -24,
syscall: 'watch',
code: 'EMFILE',
filename: null
}
`

Interesting development. If I manually run the xcodebuild command the archive succeeds:
xcodebuild -workspace ... -scheme ... archive

Isn't this basically identical to Product > Archive in XCode? Are there any explanations for this?
Another note: Another much smaller RN app archives successfully in XCode on my machine.

Works for me with same error on latest version of watchman error.

still

I started having this issue after upgrading to yarn 2

Still

same here, currently on Venture 13.1 trying to run yarn test


feat: add support to NOT LIKE operator

SUMMARY
Change get_sqla_query method of  helpers.py  to support NOT_LIKE operator
TESTING INSTRUCTIONS
All tests should pass
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[x] Introduces new feature or API
[ ] Removes existing feature or API

Running CI 🤞

I don't understand why fail front end test, my changes not affect to failed tests

Re-running that one... it might just be flaky, I've seen this one fail randomly before.

I no have option to re-run

@rusackas  please your help with the pipeline, in my local server all test run OK, I don't understand why fail in test that files that not changed from master

Running it again... ping me if it flakes out :)


Guess object type when not annotated

I think it would be quite easy to get an object's annotation with annotation = type(obj) when it is not annotated.

Duplicate of #59


Add Share buttons for each project

Partners are looking to share their project pages to their community we need to add clickable icons that allows them to share their projects with their audiences easily - LinkedIn, FB, Twitter and just 'copy link' icon would be great.

Where did the buttons go? 🤷♀


Write empty args as an empty file

If the capabilities doesn't specific extra arguments, we get an error trying to access a missing file. So always write the extra args, even if they're empty.

I don't think this is necessary, actually.


Improve UI of Palindrome checker project.

After changes

Please assign this issue to me.

@Jiya-garg9971 Assigning this to you!

close as complete in #61


docs: Clarify that you can override parameters locally

Clarify that you can override parameters locally in conjunction with using parameter files.
Closes #83

Thanks @tomkerkhove for the contribution.


Option to sort matches with n-grams or pass custom filtering/sorting method.

The current filtering is highly inaccurate although suitable for simple task. Unfortunately it matches some very arbitrary things (especially when it comes to numeric comparisons). Current solution is going to be extending the component to override the comparison operation.
Would it be possible to build in n-grams or allow a comparison and sorting function be passed in?

Hi, the search functionality is a mesh search, i.e the keyword is matched with all the key value pairs in the object of the array. So you might see list with only the label but might not match with the search keyword, but it must have matched with other properties in the same object.

Ah, alright that makes sense. Still, it might be useful to allow the filtering and sorting be overridden. It's very confusing from a UX perspective when results appear that don't seem remotely related to what I've typed.

Advanced and custom search / search API is in pipeline for this weeks release.

Advanced search. "searchBy" configuration available in v2.9.0


Feature Suggestion: Blast Resistant Conduits

I use a mod called Matter Overdrive. Well the anomaly seems to eat conduits if they are too close or if the anomaly is too big. Also It's very easy to accidently break the conduits sometimes if place a powered spawner and the mob shoots out fireballs and stuff.
It would be cool if there was a conduit that couldn't be removed or very difficult unless you wrenched it.
Also blast resistant so that it couldn't be blown off by accident. I don't think anyone would mind the same texture.

pretty sure there's blastproof conduit facades

There are


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1145 ms

Resolved: Bofrost.lu performance has improved in 0828248 after 6 minutes.


Some Hungarian accents (ő, ű) not available

Description of the new feature / enhancement
If I want to write the Hungarian long accents (ő, ű) it doesn't offer it, coming from "o" and "u".
Also, on a German keyboard, it should offer (ő, ű) by pressing "ö" or "ü", which are keys in the German layout.
Scenario when this would be used?
That it important for everyone who wants to write Hungarian without a Hungarian keyboard.
Supporting information
No response

/duplicate #20425


rethink old metadata file deletion

Currently previous versions of targets are deleted as the new one is created. This creates a situation where the repo is invalid until snapshot is updated.
Try to leave the old files in place, and only remove them during the snapshot update. This way the target update can be merged and the repo is valid while snapshot is getting updated.
tufrepo verify must be able to handle this and should recognise the issue ("the repo is valid but there are metadata files that are not included in snapshot")

I think verify should be able to recognize these situations:

valid root, valid but expired timestamp: can be fixed with timestamp update
valid root, valid timestamp, expired snapshot: can be fixed with snapshot update
a metadata file is part of delegation tree, but not part of snapshot (either completely new role or version is > version in snapshot): updating snapshot should work. Should make sure metadata version is reasonable though: can be fixed with snapshot update
ERROR: metadata file exists that is not part of delegation tree AND not part of snapshot (old metadata is allowed to be part of snapshot but not part of delegation tree): unrecoverable situation
delegation tree is valid and all metadata is part of the snapshot: no action needed

https://github.com/theupdateframework/tuf/pull/1524 will allow handling all cases I believe.


Find solution to unify interfaces between Set and Map

insert for Map and Set have different number of arguments. Because of that it's extremely hard to unify them into single interface and have decent type inference.
We need to discover solution for this problem.

Looks like it's not possible and probably not a good idea. See this instead:

https://github.com/kowainik/containers-backpack


[7.x] Add delimiter option for route prefix

Currently there is no option to customize the route prefix delimiter which is / 99% of the time and it totally made sense that Laravel had it hardcoded.
However this made it hard for users who are in needs to customize the delimiter in different cases.
This PR aims to provide a delimiter option to the prefix method with / as the default delimiter.
Usage would be:
Route::prefix('chat', '.')
  ->group(function () {
     Route::post('send', 'ChatController@send');
  });

And the route would be registered as POST /chat.send

Hi @CaliCastle, first of all we can't do this on a stable branch because of all the breaking changes.
Secondly, I don't think a dot is a valid delimiter for an url.
I'd just prefix the routes like this: Route::post('chat.send', 'ChatController@send');


add timeout to bcp connect

will hopefully fix out MAC OS X connect races with BCP on startup

Coverage decreased (-0.07%) to 89.115% when pulling def76494bc78c05834e3019cc00c358fab852c5a on add_timeouts_to_bcp_connect into 42db27ca10cf33a1c1d8e7a3ee748f261377f6a5 on dev.


Commit terraform.lock.hcl into GitHub

Hi guys,
I want to commit the terraform.lock.hcl file when running GitHub Actions in opeville/opeville-aws-terraform so that the version remain locked but I'm having some issue achieving that. Please any suggestion on how to achieve this when running GitHub Actions.

Hi,
to commit changes can be re-used existing actions like add-commit or explicitly "git add / commit" , however, commiting terraform.lock.hcl can lead to issues on execution in different platforms

@denis256 Thanks for your response but having in mind the issues that can arise from committing terraform.lock.hcl,how would i reference that so that github actions can commit that when running?

@denis256 my use case will only apply to a single platform(Ubuntu)

Hi,
a simplified approach will be to remove from .gitignore if present terraform.lock.hcl, and to have a step to commit file:
      - name: Commit lock file
        run: |
          git config --global user.name 'Your Name'
          git config --global user.email<EMAIL_ADDRESS>          git add terraform.lock.hcl
          git commit -m "Persisting lock file"
          git push


New version: sigoden.Dufs version 0.39.0

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.5 schema?

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335187 2024-01-11 02:02:42.851 [FAIL] Installer failed security check. Url: https://github.com/sigoden/dufs/releases/download/v0.39.0/dufs-v0.39.0-x86_64-pc-windows-msvc.zip Result: 0x80004005 MSI (s) (80:84) [02:02:30:314]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X64 Minimum Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. MSI (s) (80:F0) [02:02:31:487]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. [1A84:1440][2024-01-11T02:02:27]w363: Could not create system restore point, error: 0x80070422. Continuing... Installation failed with exit code -1978334972

(Automated response - build 557.)

Hi @SpecterShell,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 557.)

/AzurePipelines run

Automatic Validation ended with:

Installation failed with exit code -1978334972

(Automated response - build 570.)

Manual Validation ended with:

1:09:36 PM: 2024-01-15 13:09:35.396 [FAIL] Installer failed security check. Url: https://github.com/sigoden/dufs/releases/download/v0.39.0/dufs-v0.39.0-x86_64-pc-windows-msvc.zip Result: 0x80004005

(Automated response - build 567.)

Hi @SpecterShell,
The installation isn't unattended. Is there an installer switch to have the package install silently?
(Automated response - build 571.)

Hi @SpecterShell,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 571.)

/AzurePipelines run

Automatic Validation ended with:

Installation failed with exit code -1978334972

(Automated response - build 586.)

@wingetbot waivers Add Validation-Installation-Error


README.md: touch-ups by a native English speaker

Grammar, spelling, squelch trailing spaces, and especially change Mhz to MHz
@Dolu1990 I watched your 37c3 talk twice.  Looks fantastic!
I'm struggling to understand how all the pieces of NaxRiscv fit together.
Maybe later I can give actual technical contributions, but until then, maybe this simple copy-editing can help.

Thanks :D

I'm struggling to understand how all the pieces of NaxRiscv fit together.Maybe later I can give actual technical contributions,

Hmm if you are interrested, i'm now trying to push https://github.com/SpinalHDL/VexiiRiscv
Being in order, its complexity is more aprochable i would say ? Also, as its framework is one iteration after Nax, so it is generaly cleaner.
Let's me know :)


Fix browser-cookies error in clientOnly mode

Fix #77 without tests
It fix clientOnly mode parsing undefined variables and fix modals not showing because
of undefined variables
Check bed6b3b commit message for more info

Thanks @betoharres - I'll review this today 👍

Thanks a bunch! I was starting in React/ES6 world when I wrote that commit
if you need anything you can post a comment or send me an email

Any update on this?

I don't think so. Are you still facing the same probelms?

@betoharres Yeah :(

@jclif could you create a test repo so I can clone to see what can I do?


treewide: Pass self when overriding Python

Things done
Adds self to all overriden Python interpreters.
Otherwise references to the Python interpreter inside the set are wrong, as demonstrated by:
with import <nixpkgs> { };
let
  python' = python3.override {
    packageOverrides = final: prev: { requests = prev.requests.overridePythonAttrs(old: { version = "1337";  }); };
  };
in python'.pkgs.python.pkgs.requests

which returns the non overriden requests.
And the same with self:
with import <nixpkgs> { };
let
  python' = python3.override {
    self = python';
    packageOverrides = final: prev: { requests = prev.requests.overridePythonAttrs(old: { version = "1337";  }); };
  };
in python'.pkgs.python.pkgs.requests

which returns the overriden requests.
This can manifest itself as file collisions when constructing environments or as subtly incorrect dependency graphs.
Description of changes

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Do we know why this caused any rebuilds at all?

Do we know why this caused any rebuilds at all?

I took a quick look at why it happend to Samba:
Diffing derivations before and after:
nix-diff /nix/store/niarsxwdjhrnz5h19h80wqw2zncv89xx-samba-4.20.1.drv /nix/store/x44h0f1qlqwnvwmq63hgn0j9fzqrjbh9-samba-4.20.1.drv:
- /nix/store/niarsxwdjhrnz5h19h80wqw2zncv89xx-samba-4.20.1.drv:{out}
+ /nix/store/x44h0f1qlqwnvwmq63hgn0j9fzqrjbh9-samba-4.20.1.drv:{out}
• The input derivation named `wrap-python-hook` differs
  - /nix/store/bxp4rm12i6sgxy4glkkxhh4bj8gswdsb-wrap-python-hook.drv:{out}
  + /nix/store/b2zhcpyxhb0vz7hgfnwhnln4syhbvvww-wrap-python-hook.drv:{out}
  • The environments do not match:
      executable=''
      /nix/store/l014xp1qxdl6gim3zc0jv3mpxhbp346s-python3-3.12.4/bin/python3.12/nix/store/vl5j97ch2vjdscsw1gvxkmpk1lr4bwsd-python3-3.12.4/bin/python3.12
  ''
• Skipping environment comparison

Looking further at the Python inputs:
nix-diff $(nix-store --query --deriver /nix/store/l014xp1qxdl6gim3zc0jv3mpxhbp346s-python3-3.12.4/bin/python3.12) $(nix-store --query --deriver /nix/store/vl5j97ch2vjdscsw1gvxkmpk1lr4bwsd-python3-3.12.4/bin/python3.12)
- /nix/store/zakf7g0dmhlx4qbvv8h157d9d0k2r591-python3-3.12.4.drv:{out}
+ /nix/store/qcdh27fxgcq91hln1nrx735ilxlzkz0h-python3-3.12.4.drv:{out}
• The input derivation named `libxcrypt-4.4.36` differs
  - /nix/store/y0ik6r07dxvfi9wbdr6z1598dp1chfq0-libxcrypt-4.4.36.drv:{out}
  + /nix/store/kf5fww9m782yvnr43ww0xidafjk5lycd-libxcrypt-4.4.36.drv:{out}
  • The environments do not match:
      configureFlags=''
      --enable-hashes=strong--enable-hashes=all --enable-obsolete-api=glibc --disable-failure-tokens --disable-werror
  ''
• Skipping environment comparison


Compiler Panic "constructor must be known in the indexable type if we are exhautiveness checking"

I've found a compiler panic with roc_nightly-linux_x86_64-2024-03-16-49862da
thread '<unnamed>' panicked at 'constructor must be known in the indexable type if we are exhautiveness checking', crates/compiler/can/src/exhaustive.rs:211:41
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

The following code reproduces the issue, along with two comments with changes that fix the panic and get back to normal compiler errors for bad code like this.
My understanding of what's happening is that the second pattern match when command is has a pattern that can't exist in the definition of command and there are a bunch of patterns in the definition of command that aren't covered in the pattern matching. The combination of both issues is what is breaking the compiler. Fixing either issue (via the commented changes) allows the compiler to give useful feedback again.
I'd hope this isn't a normal situation. I got into this situation by copying and pasting code and only modifying part of it. A more helpful error message here would certainly help newcomers who make the same mistake.
app "panic"
    packages {
        cli: "https://github.com/roc-lang/basic-cli/releases/download/0.8.1/x8URkvfyi9I0QhmVG98roKBUs_AZRkLFwFJVJ3942YA.tar.br",
    }
    imports [
        cli.Stderr,
        cli.Task.{ Task, await },
    ]
    provides [main] to cli

main : Task {} I32
main = runTask |> Task.onErr handleErr

handleErr : _ -> Task {} I32
handleErr = \err ->

    errorMessage = Inspect.toStr err

    {} <- Stderr.line "$(errorMessage)" |> Task.await

    Task.err 1

runTask : Task {} _
runTask =

    command =
        when (input, model.state) is
            (KeyPress Up, _) -> MoveCursor Up
            (KeyPress Down, _) -> MoveCursor Down
            (KeyPress Left, _) -> MoveCursor Left
            (KeyPress Right, _) -> MoveCursor Right
            (KeyPress Enter, HomePage) -> UserToggledScreen
            (KeyPress Enter, ConfirmPage s) -> UserWantToDoSomthing s
            (KeyPress Escape, ConfirmPage _) -> UserToggledScreen
            # Fix one: comment out next line and uncomment the following one
            (KeyPress Escape, _) -> Exit
            # (KeyPress Escape, _) -> Quit
            (KeyPress _, _) -> Nothing
            (Unsupported _, _) -> Nothing
            (CtrlC, _) -> Exit
            (CtrlS,_) | (CtrlZ,_) | (CtrlY,_) -> Nothing

    modelWithInput = { model & inputs: List.append model.inputs input }

    # Action command
    when command is
        Nothing -> Task.ok (Step modelWithInput, NoOp)
        Quit -> Task.ok (Done { modelWithInput & state: UserExited }, NoOp)
        MoveCursor direction -> Task.ok (Step (Core.updateCursor modelWithInput direction), NoOp)
        # Fix two: uncomment next line
        # _ -> Task.ok (Step {modelWithInput}, NoOp)

Let me know if you need any more information.

I also ran into this issue while doing library dev in Roc quite a few times. This is the simplest I can get the above example down to:
app "panic"
    packages {
        cli: "https://github.com/roc-lang/basic-cli/releases/download/0.9.0/oKWkaruh2zXxin_xfsYsCJobH1tO8_JvNkFzDwwzNUQ.tar.br"
    }
    imports [
        cli.Stdout,
        cli.Task.{ Task },
    ]
    provides [main] to cli

# This type annotation doesn't change whether the compiler panics
main : Task {} I32
main =
    when nextColor Red is
        Red -> Stdout.line "The next color is red."
        # This also fixes the issue by making Blue a valid variant
        # Blue -> Stdout.line "The next color is blue."

# This type annotation fixes the issue, in that the compiler knows what's wrong
# nextColor : [Red] -> [Red]
nextColor = \color ->
    when color is
        Red -> Blue

It seems that when we don't tell the compiler that Red is the only option that nextColor can return via the type annotation, then it assumes that Blue must be a valid output variant. This constraint is imposed in the "Closed Union" matching in main, and adding a blue arm to the when clause also fixes the issue.
An easy patch would be to throw an actual compilation error that links this GitHub issue instead of panicking, but then the issue remains.
Better would be to somehow reconcile unannotated (e.g. inferred) function return types with exhaustive when matches. My expected user experience would assume correctness at nextColor (being an atomic code unit), whose inferred type is [Red] -> [Blue] and say that the matched [Red] variant doesn't match nextColors [Blue]. I expect that may collide with the expected Roc user experience, so I'd like to hear the team's opinion before we move forward with fixing this.
If the above proposed solution is good for the team, then I nominate myself to try fixing this issue. I don't have experience making changes to the Roc compiler, so if you'd rather leave this to a more experienced contributor, I take no offense.

I also ran into this issue while doing library dev in Roc quite a few times. This is the simplest I can get the above example down to:
app "panic"
    packages {
        cli: "https://github.com/roc-lang/basic-cli/releases/download/0.9.0/oKWkaruh2zXxin_xfsYsCJobH1tO8_JvNkFzDwwzNUQ.tar.br"
    }
    imports [
        cli.Stdout,
        cli.Task.{ Task },
    ]
    provides [main] to cli

# This type annotation doesn't change whether the compiler panics
main : Task {} I32
main =
    # This fixes the issue by (I think) constraining what the `when` expects
    # color : [Blue]
    color = Blue

    when color is
        Red -> Stdout.line "The color is red."
        # This fixes the issue by making Blue a valid variant,
        # though we still get a compiler error since `Red` isn't expected
        # Blue -> Stdout.line "The next color is blue."

It seems that when we don't tell the compiler what variants color can be, it gets confused between the constraints that:

color is inferred to at least be [Blue]a.
The when exhaustively matches only [Red].

While finding Red's constructor (during reification?), it assumes it will be present, but only sees [Blue], so it panics.
The two possible fixes outline the two possible compiler errors we could add here:

Adding the type annotation to color lets the compiler know that the when's [Red] mismatches with color's [Blue]. If we wanted to throw the compiler error here, we'd need to prioritize the when clause's exhaustive variants, and if we can't find a variant, we throw an error at the source of the issue, a.k.a. the definition of color in this example. This moves the error away from what seems to be the real location, so I prefer the second compiler error.
Adding another arm to the when clause with either a Blue case or a catch-all (e.g. _other ->) means the when is matching over an open union [Red]*, and won't fail when it sees blue. I suggest that when we fail to find a constructor for a when enum variant, we show an error saying:

"The when clause here exhaustively checks the type [Red], but the value it matches over is at least [Blue]. Consider adding either cases for the missing variants or a catch-all arm _ -> ... to handle the other variants."
This should be easier to implement and give developers better colocation of the issue and the compiler error

If the second proposed solution is good for the team, then I nominate myself to try fixing this issue. I don't have experience making changes to the Roc compiler, so if you'd rather leave this to a more experienced contributor, I take no offense.

I think the second solution is ideal. The fix for this particular instance should be pretty straightforward; in particular, I think it should be sufficient to remove the assertion
https://github.com/roc-lang/roc/blob/c1d0c24194764fabb49e53dc8cfd03b13f74fe00/crates/compiler/can/src/exhaustive.rs#L223
and gracefully handle the missing constructor.
In general I believe the modeling of this could be better (#4440), but that is probably a story for another day. If it would be helpful any time during your implementation, feel free to message on Zulip!
Thanks for the great analysis and volunteering!

I got the same bug with the following code:
app [main] {
    pf: platform "https://github.com/roc-lang/basic-cli/releases/download/0.15.0/SlwdbJ-3GR7uBWQo6zlmYWNYOxnvo8r6YABXD-45UOw.tar.br",
}

import pf.Stdout

table = Dict.fromList [
    ("AUG", Methionine),
    ("UAA", Stop),
    ("UUC", Phenylalanine),
]

translate = \codons ->
    codons
    |> List.walkUntil [] \protein, codon ->
        when table |> Dict.get codon is
            Ok Stop -> Break protein
            Ok aminoAcid -> Continue (protein |> List.append aminoAcid)
            Err NotFound -> Break []

main =
    translate ["AUG", "AUG", "UUC", "UAA", "UUC", "AUG"]
        |> Inspect.toStr
        |> Stdout.line!

The error message is:
thread '<unnamed>' panicked at crates/compiler/can/src/exhaustive.rs:211:41:
constructor must be known in the indexable type if we are exhautiveness checking
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

If you replace NotFound with KeyNotFound in my code, then everything works fine. But it took me an hour to figure it out: instead of a panic, there should have been a clear error message.


Replace KeyValueEntry with formatted JSON

Replace KeyValueEntry with formatted JSON.
Issue https://github.com/TappNetwork/filament-webhook-client/issues/3

Thank you @andreia !
Non-blocker comment: The ViewEntry components will probably get quite long now. You may want to add this
->stickyModalFooter()
->stickyModalHeader()

... to your View action.
Again, thanks lot for your support!

@willcastillo Sweet, thanks for the suggestion :)
I applied it and merging now


{Azure-sdk-for-go} fixing redundant documentation

Fixes https://github.com/Azure/azure-sdk-for-net/issues/21637

[x] The purpose of this PR is explained in this or a referenced issue.
[x] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

This is duplicate PR


Autocomplete support

KeyboardKit should have autocomplete support, so that the keyboard can request auto complete suggestions from a autocomplete suggestion provider.

Autocomplete support is added in KeyboardKit 2.3.0.


cannot generate hid descriptor with LOGICAL_MAX

The implementation of the gen_hid_descriptor macro seems lack logical_max field, is that right? How can i do to add logical_max field?
code here: https://github.com/twitchyliquid64/usbd-hid/blob/master/macros/src/spec.rs#L129

Looks like when I added the logical_min field, logical_max wasn't added.
b1a3a78a91f646b96078100be6297bf9c8a7a154 + 7dffba02672b4cac2cf15df880751e03d2ded85a
It will probably be something like this: https://github.com/haata/usbd-hid/tree/add_logical_maximum
This will require a test case, do you have an example that needs a logical_max?

This will require a test case, do you have an example that needs a logical_max?

sorry, I do not have an example for this.
I currently set Logical Maximum field to 255 by default, it just works 😃

usbd-hid actually sets logical_maximum for you, so in your particular case it would be very helpful if you could share your hid descriptor.

@haata here is my hid descriptor:
    0x05, 0x01,                /* Usage Page (Generic Desktop Ctrls)     */
    0x09, 0x02,                /* Usage (Mouse)                          */
    0xA1, 0x01,                /* Collection (Application)               */
    0x09, 0x01,                /*   Usage (Pointer)                      */
    0xA1, 0x00,                /*   Collection (Physical)                */
    0x85, HID_REPORT_ID_MOUSE, /*     Report ID (0x01)                   */
    0x05, 0x09,                /*     Usage Page (Button)                */
    0x19, 0x01,                /*     Usage Minimum (0x01) (Button 1)    */
    0x29, 0x08,                /*     Usage Maximum (0x03) (Button 8)    */
    0x15, 0x00,                /*     Logical Minimum (0)                */
    0x25, 0x01,                /*     Logical Maximum (1)                */
    0x95, 0x08,                /*     Report Count (8)                   */
    0x75, 0x01,                /*     Report Size (1)                    */
    0x81, 0x02,                /*     Input (Data,Var,Abs)               */

I don't see your logical maximum 0xFF in that descriptor?
Are you trying to use Logical Minimum (0) -> Logical Maximum (255) for the X,Y,Wheel parameters?

I don't see your logical maximum 0xFF in that descriptor?

The descriptor I gave is what's cannot be generated using gen_hid_descriptor now.
I can provide an example of current behavior as well:
fn main() {
    use usbd_hid::descriptor::generator_prelude::*;

    #[gen_hid_descriptor(
        (collection = APPLICATION, usage_page = 0xFF00, usage = 0x60) = {
            (usage = 0x62, logical_min = 0x0) = {
                #[item_settings data,variable,absolute] input_data=input;
            };
        }
    )]
    pub struct KeyboardReport {
        pub input_data: [u8; 32],
    }

    println!("{:02X?}", KeyboardReport::desc());
}

The generated descriptor is:
[06, 00, FF, 09, 60, A1, 01, 09, 62, 15, 00, 26, FF, 00, 75, 08, 95, 20, 81, 02, C0]

15, 00, 26, FF, 00 part are the logical minimum and logical maximum


Add support for call hierarchies

Problem
Hi,
I develop in ruby from time to time, and I really miss the possibility to search for a function call hierarchy.
From ignorance, would it be feasible to add support for it?
Reference:
LSP spec Call Hierarchy #468
Proposed solution
I'm sorry not be able to add any.

👋 Hi @kikeenrique,
I think this issue is a duplicate of https://github.com/sorbet/sorbet/issues/2130.


[Proposal] Surface "critical" changes that happen in dapr weekly to the community

With the growth of dapr project and the community, there are multiple changes that happen in parallel across multiple repos in the dapr project.
Not all changes can be followed by anyone. This proposal is to see if we can provide a concise summary of changes say new proposal created, proposal accepted, critical changes made to  runtime/contrib or SDKs e.g.: addition of a new feature, changes in preexisting criteria(say new requirements needed for a component to be certified stable).
As it exists right now most of the conversations happen across multiple repos and in either different issues or PRs. Also there are certain conversations that happen in discord that are then reflected as PR contributions in dapr.
Keeping track of all these changes/ going back and being able to search for some important issue that has been agreed upon and closed etc. is hard.
This proposal is to identify categories of the information that should be surfaced to the community on a weekly basis that provides visibility into changes happening in the project.
Some of the categories can be tracked and surfaced on a weekly basis :

New API code changes
New criteria/process definition
Proposals in review, Accepted. proposals
"Large", "impactful" code change in runtime repo -- can be a large refactor, internal behavior change etc. based on pre-identified critical paths

pkg/http, pkg/diagnostics change in runtime
tests/conformance change in components-contrib repo

Breaking changes that will be part of the next milestone

These are just some broad categories by which we can identify changes in dapr project. We can add action commands that maintainers and approvers can use to tag certain PRs that should be surfaced. We can also automate the daprbot to identify proposals, acceptance of the same, changes of files in certain paths of the repo which have been pre-identified as critical code paths etc.
daprbot can potentially be augmented to post a weekly summary defined under these categories to a channel in Discord.
Benefits :

Provide a broader visibility into changes happening across the project
Provide visibility into tracking progress of milestone issues
Provide a single place to track broad impactful changes to the project
Provide visibility to the community
Provide visibility of repo maintainers of changes that happen in other repos that might impact the repo that they are maintainers of

This is no means a substitute to general everyday triaging, pr reviews and issues reviews that is done. But it shall complement those efforts also.
cc @dapr/maintainers-community @dapr/maintainers-dapr Thoughts?

I think this is a good proposal that addresses a real need of the community.
As for its execution, I am not a fan of a bot just sending links on Discord. The reason is that those would lack context and could be perceived as "spammy". Just posting links without context usually leads to a very low CTR.
I would recommend that there be some sort of curation here, in which someone (maybe a maintainer) posts a message with links to the issues/PRs AND a 1-sentence explanation of why that is relevant and we need from the community. For example, this person could write that we are sharing issue X because we are seeking feedback on a proposal, or we are highlighting possible breaking changes, or... This will also highlight why it's important for the community to chime in.
This way, it feels more personal, more actionable, and will see higher CTR and better engagement.

I would recommend that there be some sort of curation here, in which someone (maybe a maintainer) posts a message with links to the issues/PRs AND a 1-sentence explanation of why that is relevant and we need from the community. For example, this person could write that we are sharing issue X because we are seeking feedback on a proposal, or we are highlighting possible breaking changes, or... This will also highlight why it's important for the community to chime in.

I like this proposal and I agree with this more curated way of posting the updates. Without context this information could be confusing to other community members. I'd be happy to work out a place to post this info and take ownership for getting it shared w/ the community.
@msfussell, @dapr/maintainers-community  Any thoughts here?

@ItalyPaleAle I can understand that providing more context for some the changes would be great. And @nyemade-uversky Thanks for volunteering for this.
If we can build in more automation for the context also, that would be great. But we can start with manually curating it for now.
@dapr/maintainers-community @dapr/maintainers-dapr Any thoughts on proceeding forward with this?

@mukundansundar  @johnewart - where do preview features come in. Can the criteria be included in the proposal?

@mukundansundar @johnewart - where do preview features come in. Can the criteria be included in the proposal?

@akhilac1 Please add comment in dapr/proposals#1 ...

@mukundansundar - What are you thoughts on keeping this issue open? Can this be resolved now?

No longer relevant and addressed in new processes in weekly ship rooms


[Feature Request] Change more things

I hope that we can replace the sprite of something in Dontdestroyonload, like super spitter in Collector's Jar,that's really fun

and how can I skin some boss like xero in RestingGround

I have not checked them specifically, but swapper should allow skinning both of these. have you tried with it?

Yes,I tried named the image"ghost warrior xero",but it doesn't work

And I cant swap things from GlobalPool like super spitter in GG_Collector_V

Just checked, it seems xero is not part of the main scene and that might be causing this i'll look into both this and Dontdestroyonload. thanks for letting me know about this!


feature](insert)implement hive table sink plan

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

issue: https://github.com/apache/doris/issues/31442

run buildall

run p0

run buildall

run buildall

run buildall

run buildall

run buildall


Angular CLI compatibility

Hi,
I'm using the image uploader in conjunction with an Angular CLI generated project, after importing the component into my app.module.ts, and adding it to a component for testing I'm running into some build issues.

Error encountered resolving symbol values statically. Calling function 'ImageUploadModule', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AppModule in..

My app.module.ts looks like this:
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { FormsModule } from '@angular/forms';
import { HttpModule } from '@angular/http';
import { RouterModule } from '@angular/router';
import { AlertModule } from 'ng2-bootstrap';
import { ImageUploadModule } from 'angular2-image-upload';

import { AppComponent } from './app.component';
import { ArticlesComponent } from './articles.component';
import { ArticlesService } from './articles.service';
import { ImageService } from './images.service';

import { CarouselModule } from 'ng2-bootstrap';

import { AppRoutingModule } from './app-routing.module';
import { LoginComponent } from './login/login.component';

@NgModule({
  declarations: [
    AppComponent,
    ArticlesComponent,
    LoginComponent
  ],
  imports: [
    BrowserModule,
    FormsModule,
    HttpModule,
    AlertModule.forRoot(),
    AppRoutingModule,
    CarouselModule.forRoot(),
    ImageUploadModule.forRoot()
  ],
  providers: [
    ArticlesService,
    ImageService
  ],
  bootstrap: [AppComponent]
})
export class AppModule { }

Hi Mantisen,
I tried to reproduce this error but unsuccessfully. I thought that the root of the problem is ImageService because there is a service with the same name in ImageUploadModule, but when I added it to my AppModule same way as you did I got no errors while building.
Here's my AppModule code:
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { FormsModule } from '@angular/forms';
import { HttpModule } from '@angular/http';
import { ImageUploadModule } from 'angular2-image-upload';
import { ImageService } from './image.service';
import { RouterModule } from '@angular/router';

import { AppComponent } from './app.component';
import { AppRoutingComponent } from './app-routing/app-routing.component';
import { AppRoutingModule } from './app-routing/app-routing.module';

@NgModule({
  declarations: [
    AppComponent,
    AppRoutingComponent
  ],
  imports: [
    BrowserModule,
    FormsModule,
    HttpModule,
    RouterModule,
    AppRoutingModule,
    ImageUploadModule.forRoot(),
  ],
  providers: [
    ImageService,
  ],
  bootstrap: [AppComponent]
})
export class AppModule { }

First of all, try to rename ImageSevice and if this will solve your problem I'll rename ImageService in the library to avoid the collision. If this will not help maybe something wrong with the CLI itself, try to update it and build again.
If nothing helps give me more instructions on how to reproduce the error.

I got this error too but I did not import image service before . Here is my app module :
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { FormsModule } from '@angular/forms';
import { HttpModule } from '@angular/http';
import { AppComponent } from './app.component';
import { MaterialModule } from '@angular/material';
import { Routes, RouterModule } from '@angular/router';
import { MessageComponent } from './message/message.component';
import { HomeComponent } from './home/home.component';
import { CKEditorModule } from 'ng2-ckeditor';
import { ApiConnectorService } from './api-connector.service';
import { RedeemableComponent } from './redeemable/redeemable.component';
import {ImageUploadModule} from "angular2-image-upload";
const appRoutes: Routes = [
{ path: 'home', component: HomeComponent },
{ path: 'message', component: MessageComponent },
{ path: 'redeemable', component: RedeemableComponent }
];
@NgModule({
declarations: [
AppComponent,
MessageComponent,
HomeComponent,
RedeemableComponent
],
imports: [
MaterialModule.forRoot(),
ImageUploadModule.forRoot(),
BrowserModule,
FormsModule,
HttpModule,
RouterModule.forRoot(appRoutes),
CKEditorModule
],
providers: [ApiConnectorService],
bootstrap: [AppComponent]
})
export class AppModule { }

Hi, I have the same problem.

Is there anything new with that?
Got the same error....

@kobikd Looks like it's bound to the latest angular build. I'll figure out how to solve it in a week.

Fairly certain this is related: https://github.com/angular/angular/issues/11262

<EMAIL_ADDRESS>

Anyway for all experiencing this issue, its not only with Image Upload module, many other modules are also having the same problem with newer versions of Angular 2 core and CLI..
It is best not to use the latest versions of these at the moment, I have restored compatibility to all my modules by using Angular 2.2.1, and CLI version 1.0.0-beta.19-3
Package.json is like this:

"@angular/common": "~2.2.1",
"@angular/compiler": "~2.2.1",
"@angular/core": "~2.2.1",
"@angular/forms": "~2.2.1",
"@angular/http": "~2.2.1",
"@angular/platform-browser": "~2.2.1",
"@angular/platform-browser-dynamic": "~2.2.1",
"@angular/router": "~3.1.0",

@flintcreativestudio
I got this error while trying to compile with --aot
error TS5023: Unknown compiler option 'aot'.

Hi
We've tried updating  Angular  and Angular CLI  to the versions that flintcreativestudio said are working,  and we're still running into this problem.
Any ideas?

any update for this error ?

@f1k2c I'm thinking about creating an issue in the angular 2 repo to attract ng developers' attention to this problem.

Please help me about this problem because I am waiting solution about this problem

Hi, any update about this issue ?

ERROR in Error encountered resolving symbol values statically. Calling function 'ImageUploadModule', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AppModule in /home/sonu/Angular2/lst-front/src/app/app.module.ts, resolving symbol AppModule in /home/lodo/Angular2/lst-front/src/app/app.module.ts
i got this  errror too

Resolved by #27. Thanks to our savior @UncleDave.