Cannot follow the example

I am trying to use your example on setting a variable. When I add an action 'Variable' is not an option

So far every example I see to use Logic Apps on the internet doesn't match at all what I see in Azure

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

ID: 3aac6209-b1d7-3837-6e4e-966c523fce0b
Version Independent ID: c0ae406c-7f69-285a-b83d-d7b5cd7b4c10
Content: Create and manage variables for storing and passing values - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-create-variables-store-values.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

Hello @stevechanis, thank you for providing the feedback. The option will show up when you search for variables instead.

We have assigned this issue to the author to review further and take the next course of action.
Hello @ecfan we might need to update the screenshots on this doc to reflect the new UI experience. Thank you!

Thanks for your help with this

@stevechanis, thanks for reaching out!

All the Variables operations are built-in operations, which run natively in Azure Logic Apps. So, whether you're using the designer for Standard or Consumption plan-based workflows, the Variables operations appear under the Built-in category. They won't appear under Azure connector category in the Standard-based experience, nor under the Standard or Enterprise connector categories in the Consumption-based experience.

The current screenshots apply to Consumption plan-based workflows and hasn't yet caught up with the designer experience for Standard plan-based workflows. However, these screenshots are planned for updates.


Tags not editable

I have set .png to profile 'Simple' which contains System.Keywords (which I understand it to be tags). However, after closing and restarting Explorer, I don't see tags in the details panel, despite having them set to be viewable there. When I open the properties of the .png file, I see the tags option, but I am unable to edit the tags, and it's just stuck being blank.
Any idea how to fix this? Am I missing something?

This is also the case for other files (like .ico) and other properties (like Comments and Rating)

I just tested on some more .png files, for some reason some work and others don't???

I have applied the simple Office profile to PNG files on my Windows 1903 system, and I am able to add and edit tags and comments quite happily.
I can make these properties unchangeable on selected PNG files by marking them as read only, however. This is the only way that I can think of of coming up with a mixed outcome.
Dijji


Rip out the deprecated Image components

We have a bunch of fields like squareImage, widescreenImage, superWidescreenImage, which are used in the codebase but have been removed from the Prismic model – so they'll always be empty.
Once we've finished moving everything to TypeScript (https://github.com/wellcomecollection/wellcomecollection.org/issues/7302), we should go through and remove all this code and the components that rely upon it.

We should double check this – I don't seem them in the Prismic model, but I do see them in exhibition content. 🤔


etcdctlv3: Readme.md updated

Under PUT example the put command was mentioned in capital which will
give the below error:
Error:  unknown command "PUT" for "etcdctl"
Hence corrected the same.
The lease id is mentioned with 0x to denote hex but since its an
example, copy pasting the command will give the below error:
Error:  bad lease ID (strconv.ParseInt: parsing "0x1234abcd": invalid
syntax), expecting ID in Hex
Hence modified the same to a sample correct value so that a user new to
etcd does not get confused.
A user new to etcd may not know that the lease will need to be
generated first before attaching it to the key and may get error as
specified below:
Error:  etcdserver: requested lease not found
Hence added a refernce to lease grant for a new user to refer it under
the OPTIONS section.
The command ./etcdctl range foo does not work and gives the below
error:
Error: unknown command "range" for "etcdctl"
Hence corrected the same

Command example fixup looks OK to me.
I don't think the reference to LEASE GRANT fits in with the rest of the document, though (e.g., why don't delete/get/watch have references to put? why doesn't member list have a reference to member add? etc). Probably better to keep the documentation short instead of trying to cross-reference everything if possible.

@heyitsanthony sure will do changes as per your suggestion. Will remove the reference section. Just needed your opinion if we can just mention in the same line on the part that "Lease needs to be created before it can be attached to the key." or better to remove it completely.

@sinsharat We really need to update pull request instead of closing it and creating a new one next time. There are more than 700 people watching on this repo. We shall try our best not creating noise. Thank you in advance.

@xiang90 sorry. I didn't realise this will cause issue. Actullay i really tried squashing it but didn't find a way. But i assure you will not happen next time. Will contact one of the commiters in huawei and figure out exact way to do it.
Thanks.


Git fix attempt

Description

Could the git fix be that simple? I was able to rebase other branches on top successfully.
Checklist

[ ] I have added tests that prove my fix is effective or that my feature works

[ ] I have updated the CHANGELOG-PENDING file with my change

[ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version

I'm not sure I understand what we're fixing, what is this? The net diff of the two commits is a no-op. Is the code on main not working properly for you

I'm not sure either, but it worked locally, closing.


News repost unavailable, but it does work

Category

[x] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Observed Behavior
On some tenants /_api/sitepages/pages/reposts/iscontenttypeavailable returns false while the "Repost page" contenttype is there. How does Sharepoint determine this state?
Because of this the news webpart cannot repost, it shows a message "The contenttype Repost page is missing" (or something like this). If I use Fiddler to replace this false response with true the news webpart works fine.
So it seems there's nothing wrong with the contenttype, but the API somehow thinks there is.

Not clear what you're asking... are you saying there's an issue with the News web part?

On some tenants /_api/sitepages/pages/reposts/iscontenttypeavailable returns the incorrect status.
As a result, the news webpart doesn't fully work.

In that case, that's more of an OOTB product issue that can't be addressed here.
Thank you for your submission. This GitHub issue list is targeted only for SharePoint development issues. If this is a capability question/discussion, please use the SharePoint TechCommunity.
If it is an issue is related to out-of-the-box capabilities of SharePoint or not related to SharePoint, we cannot process is through this channel. Please submit your finding using the Tenant administrator support channels in your tenant or using Premier support, if that’s available for you. Sorry for the inconvenience.


Delete OpsWorks resources

WHY
At #231 OpsWorks supports were introduced. However this patch lacked tests. There was no way to verify the behavior of exporting OpsWorks resources.
I tried to add tests for them recently and I found several bugs in OpsWorks Stack resource. It may be take more time to cover OpsWorks resources (stack / custom layer), so I decided to omit OpsWorks resources from next release.
Sorry for my failure.
WHAT
Delete and remove all OpsWorks resources from Terraforming code.

Coverage increased (+2.6%) to 99.95% when pulling c034bf3a8faf964b9da2e1a19dc1a499f14671fd on delete-opsworks into 72c96ee039b9382267ee388760895fbabd4fab87 on master.

Coverage increased (+2.6%) to 99.95% when pulling c034bf3a8faf964b9da2e1a19dc1a499f14671fd on delete-opsworks into 72c96ee039b9382267ee388760895fbabd4fab87 on master.

Hi @dtan4 - I would like to help with this, since I am using OpsWorks, and would love to manage everything with terraform.
Could I please ask for more details about the bugs that you found? I will be using this in production, so I can help to maintain this going forward.


cache poet certifier info

Motivation
To avoid querying the same poet /v1/info endpoint many times in the 1:N setups.
Description
The poet service caches the obtained certifier info for 5 minutes by default (configurable).
Test Plan
added tests
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[ ] Update documentation as needed
[ ] Update changelog as needed

Bors merge


Convert BooleanList to IndexList.

The __str__ and __repr__  methods do not work as expected, see https://github.com/PyO3/pyo3/discussions/2212


Add test fixtures

Fixes #13

Since this project is still in alpha status, I will go ahead with merging, once the CI is green.


[Compute ]Add new parameter community-gallery-info  and --permission Community options to az sig create, add new command az sig share enable-community

Description

create a gallery with community sharing info: az sig create --gallery-name --community-gallery-info publisherUri,publisherEmail,eual,publicNamePrefix
share a gallery to community: az sig share enable-community
https://github.com/Azure/azure-cli/issues/19882

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

This PR is included by #20129, so close this one


Add engine docs

This pr fixes several typos in docstrings that specify non-existent sphinx sections. For example Usage and Example have been converted to Examples. Note has been converted to Notes. Returns: has been converted to Returns. Several minor fixes, for example if there are not enough formatting ~ under a title.
Create a Pipeline subsection for built-in factors. The factors have been organized alphabetically.
Include Factor methods such as winsorize in documentation. Currently only some are listed and they are all useful to users.
Include documentation and subsection for PipelineEngine.
Two non-existent classes have been removed zipline.assets.AssetFinderCachedEquities and zipline.pipeline.data.EarningsCalendar.

Coverage remained the same at 87.75% when pulling bb74a0e994d96361f186c8e27ceb7315ebe9a0d7 on add-engine-docs into cabe0b691cd47b41ffb3cd314d4a46865853ee53 on master.


[CVP-2652] Parse infrastructure feature annotations from CSV

/LGTM

One issue was revealed while running a sample operator job:
http://external-ci-coldstorage.datahub.redhat.com/cvp/cvp-redhat-operator-bundle-image-validation-test/e2e-test-operator-bundle-container-8.0-11/6453aeb0-9ef6-4635-984a-14e9d420cf58/operator-metadata-preparation-bundle-image-output.txt
here is a solution: https://github.com/ansible/ansible/issues/74851#issuecomment-852203455
I used ignore_errors and it works now

/LGTM


Development

Merge development into master, making 5.0.0 the new stable

@eddy-minet-holis I think I don't understand, does release 5.0.0 fix the issue you described with the code challenge?

@jorenvandeweyer I added three missing files that were removed by merge-override. Master should not again point to the same HEAD as development. From here we should work keep up working on development and merge into the respective target branches.

Approved it again.
@jankapunkt  I also suggest we stop using release-x.y.z branches and only use releases. I think this is a better way to manage our releases since there will never be any new commits to a released branch.
So to clarify

master will be the stable 5.x release
development is the development branch and will be merged into master for each release
4.x will be the support branch for security fixes. We can create this from the existing release-4.3.0 branch.

new 4.x.x+1 patches will be started from this branch.

I suggest we clean up and delete all our branches

stale branches (eg. promisify, v4.3.0-dev)
any branches from the original repository (eg. v5-dev, security)
feature branches which are merged (eg. remove-util-inherits)

@jorenvandeweyer  I fully agree with your proposal.

@eddy-minet-holis I think I don't understand, does release 5.0.0 fix the issue you described with the code challenge?

Yes. And I think the fix should be applied for 4.3 users.
Actually the workaround is easy when using the lib, but without it the PKCE flow just can't work :
req.body.code_challenge = req.query.code_challenge;
req.body.code_challenge_method = req.query.code_challenge_method:
const oauthReq = new oauth2.Request(req);
const oauthRes = new oauth2.Response(res);
...

@eddy-minet-holis I published a fix as 4.3.3, feel free to test and please file an issue if this still not fixes things.
@jorenvandeweyer in concordance with your proposed branch structure I also aligned the NPM tags:

next - development and RC releases
latest - latest stable releases from the current stable major (currently v5)
maintenance - the maintenance-mode releases, currently v4

see: https://www.npmjs.com/package/@node-oauth/oauth2-server?activeTab=versions

@eddy-minet-holis I published a fix as 4.3.3, feel free to test and please file an issue if this still not fixes things.

Works great in 4.3.3, thanks!


Tenants

Describe the feature
I would like to use Houdini in the project I am currently working on. The system with the GraphQL API the client would connect to have different tenants. A client must set the header X-Tenant with the ID of the tenant to use a specific tenant when making a request. The tenant the user is using is decided by the URL, as each path is prefixed with /tenant/[tenantID]. This works very nicely with SvelteKit, as every page simply is located under /src/tenant/[tenantID].
However, I do not see any obvious way to pass the tenant ID to the fetchQuery function in client.js. I have thought about a few workarounds, but everyone has failed since certain users have access to more than one tenant and they need to be able to switch between tenants within the SPA. This creates a case where Houdini’s built-in caching need to be aware of what tenant the users are requesting data for so that responses can be cached separately for each tenant.
One method I have tried is to get the tenant from the URL in the Variables function and set it as a variable. However, this would mean that some logic needs to be implemented to set the tenant in each GraphQL query that is made, which is repetitive. Additionally, not all queries will have variables, which would mean variables need to be added unnecessarily. Also, in principle, a tenant ID is not really a variable as it is not passed as a variable to the GraphQL query on the server but handled using different logic.
To me, metadata looks like a good match for a location where the tenant could be located. However, I am using the standard declarative form of defining that a page requests a query, i.e:
import type { PageData } from "./$houdini";
export let data: PageData;
$: ({ GetEntities } = data);

// When using the data in the view.
$GetEntities.data?.entities

You have a guide on your website where you describe that metadata can be used when using the more imperative .fetch() method but I cannot find any information about the standard declarative form. I have researched your source code to some extent and to me, it looks like this is currently not possible.
Also, does the caching mechanism regard metadata? Because, if not, then using metadata to specify the tenant would not be possible.
Preferably, I would like an API where it would be possible to add the tenant ID to the metadata in a load function located in /src/tenant/[tenantID]/+page.ts as this would mean the tenant would be cascaded to all pages.
As a plan B, would it be otherwise possible to have a middleware where a variable could be injected? This would preferably be in /src/tenant/[tenantID]/+page.ts just as with the case described above. However, a global middleware would be fine if it is invoked each page change not just on the server but also on the client as well. It would be okay for me with such a solution even though a tenant ID is not a variable in principle.
I am going to continue investigating your source code and might propose a solution if I find one.
Criticality
waiting for it to switch all my project to Houdini

I researched the code further and found out that only the variables are used when caching and not the metadata. Thus, it seems like some kind of variable middleware would be needed.

Oh, very interesting 🤔 I'll have to think a little bit about how to support this. You're correct that there isn't an immediately obvious solution.
Are the IDs globally unique across tenants? Once we do have a way to point your queries to the right API, we need to make sure that the IDs are unique so the cache doesn't get confused.

The IDs for the entities belonging to a certain tenant are globally unique across tenants in our backend implementation, as they refer to database keys of rows that also each have a foreign key to a tenant. However, I need to support operations that does not include a key, such as listing all entries of a certain entity within the tenant (with or without pagination). In this case, no ID is included as a query variable. Additionally, a popular alternative to the described tenant implementation is to have one database per tenant, which means the entry IDs would not be unique.
I researched the code further and saw that logic exists to only cache variables that are used by the query, so even though I have managed to inject the tenant ID in the variables, it won’t be cached. Yet, as I’ve understood it, we users can pass any arbitrary data as metadata, so if the metadata is cached and can be provided from /src/tenant/[tenantID]/+page.ts, it could be a good match for specifying a tenant ID.
I am going to investigate how metadata could be cached today. I would like to propose that two callbacks could be injected: one to add or modify the metadata and one to compare two metadata objects so that the caching mechanism could differentiate between two metadata instances and cache the results separately. Additionally, since probably only a subset of the library’s users will use this functionality, I propose that metadata caching only would be done if a comparator callback has been provided. What do you think about this?

Sorry, I just realized what you are talking about. Since you cache the result on an entry basis, errors would be introduced if you just looked at the IDs of the individual entries without regarding the tenant. Simply “caching the metadata” as I proposed would not work here. In my case, this would not be an issue since the IDs are unique anyway, but it would not work if the tenants were stored in different databases. I guess each entry would have to be identified using a pair containing the tenant ID and the entity ID.
Nevertheless, I think being able to inject metadata when using the declarative form would still be a good idea, as it would mean the metadata feature would be accessible with this type of syntax and not just from .fetch().

I have managed to create a solution where it’s possible to inject variables through a middleware while ensuring that these extra variables are included in the cache key. You can see it at this link: https://github.com/oborgen/houdini Only packages/houdini-svelte/src/runtime/stores/query.ts and packages/houdini/src/runtime/cache/stuff.ts have been updated. Notice that entries with the same ID in different tenants would probably not work.

@AlecAivazis Have you thought anything more about this? I have a proposal: The file packages/houdini/src/runtime/cache/index.ts currently contains a global instance of Cache. This could be replaced with an object that maps tenants (as strings) to Cache instances. Then, getCache() would have to accept a tenant, which it could use to look up the correct Cache instance. This would ensure isolation between tenants from what I can see. However, each time anything is queried, mutated, subscribed to, etc, the tenant would have to be specified (with a default value of course as most users will not have to deal with tenants).
It would be quite nice to have some way to set the tenant once (based on what page is loaded, etc) instead of having to set it on each request. One way this might be possible would be to use Svelte's setContext/getContext, which would mean users could set the tenant with setContext when a page is loading and then getCache could get it using getContext so that the right cache could be returned. However, an immediate roadblock to this is that LayoutSessionStore.getConfig calls getCache outside of any component initialization, which causes an exception to be thrown when calling getContext. The configuration could probably be something the Cache instances could share but I haven't investigated how that currently works.
Another potential problem with setContext/getContext might be that many stores seem to be created as global instances, which might cause problems. However, to me, most of them seem to be bound to specific pages, which possibly could make it so the correct tenants would be returned from getContext. What’s your opinion on this?

Sorry i haven't reponded here @samuel-utbult-oborgen. I've been super busy with work and the 1.0 release. My overall feeling is that your situation is very specific and it's hard to imagine that there would be a universal way to address this as part of houdini's core.
I think the best approach would be to put together a custom plugin that does whatever is necessary. One thing you could explore is having a plugin that changes the logic of the generated runtime. That would let you customize the behavior to fit your exact needs. Let me know if that sounds like something you want to explore and we can talk through the options/steps.

It's fine. I have been busy with other things as well. My current workaround is to put data-sveltekit-reload on any link that changes which tenant the user is currently using. This effectively means the cache is cleared when switching tenants. As you write, some kind of plugin could be useful as long as it could overwrite the behavior of getCache to maintain separate cache instances for the different tenants. Do you have any plans to introduce support for plugins to the library? I am not a Javascript-expert, but as far as I understand, patterns like monkey-patching can be used to interfere with the behavior of existing functions. I can look into that when I have time.

Do you have any plans to introduce support for plugins to the library?

Yes! In fact, the svelte bindings are one such plugin to the core houdini infrastructure. There are already a few people in the wild who have custom plugins to fit their needs so it's definitely doable. Only big hurdle is that it's not really documented yet since I want to reserve the ability to change it but if this is something you want to explore I can point you in the right direction (or we can chat on discord if that works better for you).

In https://github.com/HoudiniGraphql/houdini/tree/main/packages, you can already see a few plugin examples:

houdini-svelte
houdini-plugin-svelte-global-stores (not released yet)

Thank you. I can look into how those plugins work to see how a tenants plugin could be implemented.

Awesome! For a better overview of all of the hooks that a plugin can implement, here is a diagram that should be up to date: https://app.excalidraw.com/l/5mJ4nb9Inaz/7QsnYkLMbK3


bug: Default font doesn't work with Pages Router + Tailwind

Provide environment information
System:
OS: Linux 6.6 Pop!_OS 22.04 LTS
CPU: (16) x64 AMD Ryzen Threadripper 1900X 8-Core Processor
Memory: 16.88 GB / 31.19 GB
Container: Yes
Shell: 5.8.1 - /usr/bin/zsh
Binaries:
Node: 18.19.0 - /usr/local/bin/node
npm: 10.2.3 - /usr/local/bin/npm
pnpm: 7.33.4 - ~/.local/share/pnpm/pnpm
bun: 1.0.22 - ~/.bun/bin/bun
I'm using npm & node.
Version: 7.26.0
Describe the bug
The tailwindcss config file sets "var(--font-sans)" as the first font used. But --font-sans is only available in App Router template (Inter, provided by next/font) here
This causes browsers (at least Chrome and Firefox on Linux) to not try other fonts and just skip the font-family as invalid due to having an empty/invalid value. Not even moving it to second helps as it makes the whole property value invalid.

Reproduction repo
https://github.com/raikasdev/t3-app-fonts-problem
To reproduce

Create a new app with Tailwind and decline App Router.
Do the normal shenanigans, push db etc
Start npm run dev and open in browser

Additional information
I was able to fix this by copying the Inter code from App Router to the index.tsx. Probably using a layout would be a better solution, but yeah.

Good catch, should add the following in _app.tsx:
import { Inter } from "next/font/google";

const inter = Inter({
  subsets: ["latin"],
  variable: "--font-sans",
});

const MyApp: AppType = ({ Component, pageProps }) => {
  return (
    <main className={`font-sans ${inter.variable}`}>
      <Component {...pageProps} />
    </main>
  );
};

export default MyApp;

Opened a PR to fix this: #1778


add name and desc to ci and update readme

Description

adds name and description to the pipeline
also syncs sections of main readme

Check the relevant boxes:

[ ] Bug fix (nonbreaking change that fixes an issue)
[ ] New feature (nonbreaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Examples or tests (addition or updates of examples or tests)
[x] Documentation update
[x] CI related update (pipeline, etc.)

Checklist

[ ] If relevant, a test for the change has been added or updated as part of this PR.
[ ] If relevant, documentation for the change has been added or updated as part of this PR.

Merge

Merge using "Squash and merge".
Make sure to use a relevant conventional commit message that is based on the PR contents. The commit message determines whether a new version of the modules needs to be released, and if so, which semver number to use).

Not a module we own, so adding @jvallexm as reviewer

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix build issues on node

This does two things:

changes what gets included in npm so that a backup build can proceed. I have tested this in docker linux arm64.

adds some info that will hopefully cause prebuildify to correctly cross compile for linux-arm64

Fixes #377

:tada: This PR is included in version 2.10.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Issue #15 | Update stellar-sdk package

Pull Request Description: Update to @stellar/stellar-sdk
Objective of the PR
This pull request aims to update the imports from the stellar-sdk library to @stellar/stellar-sdk. The new @stellar/stellar-sdk library is the updated and maintained version by Stellar, which includes the latest improvements, bug fixes, and compatibility with new features of the Stellar protocol.
Changes Made
Replacement of the Library

Library Replacement:

The use of stellar-sdk was replaced with @stellar/stellar-sdk in all project imports.
This ensures integration of updates and improvements from the new version of the Stellar SDK.

Comprehensive Code Review

Code Review:

The entire codebase using stellar-sdk was reviewed to ensure compatibility with @stellar/stellar-sdk.
The review included verification of imports, data types, and methods used, ensuring no disruptive changes to functionality.

Testing and Validation

Testing and Validation:

Extensive testing was conducted on the application to validate that all functionalities related to the Stellar library continue to operate correctly with @stellar/stellar-sdk.
Tests confirmed that no breaking changes were found as a result of this update, and the application continued to function normally after the change.

Justification and Benefits

Maintenance and Support: @stellar/stellar-sdk is the recommended and maintained version of the Stellar SDK, ensuring better support and future updates.
Improvements and Features: The new version offers improvements in stability, new features, and better performance compared to the old version.

Conclusion
Switching to @stellar/stellar-sdk ensures that the project stays aligned with current best practices and is prepared to leverage improvements in the Stellar ecosystem. This PR has been carefully reviewed and tested, ensuring that the transition does not affect the existing functionality of the application.
We request a review of this PR to validate the changes made and confirm that there are no negative impacts on the application's functionality. We appreciate any feedback you can provide.

Hello @chopan123 ! Any review on this PR?

you only modified 1 line in 1 file, there is more...

Yes, sorry, I didn't realize that the import was missing in the "env_config.ts" file.
Is there any other file missing? I just checked and it doesn't seem to be missing any other than the one I just mentioned, but I'm still asking just to be sure.


Restriction to parent

Hi @beizhedenglong
when you try to drag the crop area outside of the parent container (same size defined from props 'width' and 'height') it dont stop.
I have see your code and i see that you use interactjs and i have found a possible solution in his documentation,
interact('.draggable')
  .draggable({
    // enable inertial throwing
    inertia: true,
    // keep the element within the area of it's parent
    modifiers: [
      interact.modifiers.restrict({
        restriction: "parent",
        endOnly: true,
        elementRect: { top: 0, left: 0, bottom: 1, right: 1 }
      }),
    ]
)

let me know

see this issue https://github.com/beizhedenglong/react-multi-crops/issues/5

thanks


Question About topology

Hi ! team.
I asked about the question of a topology, the question number is 2605。
For this problem, what changes have you made,?Modified those files?
can you provide them? Thank you！

It is a feature missing.
Patch number is here.
https://github.com/naver/pinpoint/commit/6f44a94502412ba7b688d3c4574bf35ec2f24bbf


Transfer Alias Transaction is not being previewed

Is your feature request related to a problem? Please describe.
As the title says when transferring an alias the transaction preview is missing when signing/confirming with XT.
Additional context
Technically,  an alias on private sale with 0 as price immediately transfers the alias to the receiver.
Describe the solution you'd like
Show the preview when transferring alias at the moment of signing/confirming a transaction.

This is the raw payload
{
  "type": 1,
  "subtype": 6,
  "timestamp": 270559361,
  "deadline": 1440,
  "senderPublicKey": "6e1a0abea0cbacdc8c77a7de2868360d3e667b276a2f32bb847579d126d63e78",
  "recipient": "1673574549656521245",
  "recipientRS": "TS-LLJX-7YEQ-4C4S-3VFGG",
  "amountNQT": "0",
  "feeNQT": "1000000",
  "attachment": {
    "version.AliasSell": 2,
    "alias": "6442930183499063033",
    "priceNQT": "0"
  },
  "attachmentBytes": "02f99e1aa4dde269590000000000000000",
  "sender": "8929712165307955075",
  "senderRS": "TS-NFW5-WWDU-Y3BE-9P7VR",
  "height":<PHONE_NUMBER>,
  "version": 2,
  "ecBlockId": "15654874362130940225",
  "ecBlockHeight": 522320,
  "cashBackId": "8952122635653861124",
  "verify": false,
  "requestProcessingTime": 2
}

this is actually the sell alias transaction... and I fixed it


fix: trust private network proxies

If the downstream is inside a private network, the api will assume that
client is the first ip it doesn't recognise as being part of the
network.
Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

This makes req.ip return the 'real ip', i.e. the address of the requesting client.  As such, express-rate-limit's default keygen will work.
Related https://github.com/freeCodeCamp/freeCodeCamp/pull/49194

What if we want to use something other than the default keygen? What if we want to change to a custom strategy because we can't use IP addresses at all?

I see what you're saying, but getting the client IP from the rightmost (non-trusted) IP in x-forwarded-for is the defacto standard. We can deviate from that standard, but doing so increases the chance that we introduce a vulnerability.
The problem with using all of x-forwarded-for as a key is that we now have to overwrite it before it reaches the api and remember to keep rewriting it whenever we change the infrastructure. Failing to do so could introduce subtle vulnerabilities.  In contrast, if we use the rightmost IP then those same infra changes are more likely to cause an outage (i.e. we accidentally rate-limit a load-balancer or similar) than create a vulnerability. An outage is bad, of course, but we'd immediately know about it, unlike a vulnerability.
I can go into more details on the specifics, if you like. Also, I highly recommend having a skim of https://adam-p.ca/blog/2022/03/x-forwarded-for/ It is quite excellent (and the first paragraph summarizes it well).

The problem with using all of x-forwarded-for as a key is that we now have to overwrite it before it reaches...

Precisely what we should be doing for any header that is supposed to be used server side. This is like SecOps 101 because if you are not trusting the value, it might as well have been spoofed. So the key needs to be overwritten from a trusted source (not revealing it here for reasons of security, but you know the header we can use to overite the x-forwarder-for).
Long story short, follow standards or not – it all goes out the window if you do not follow common sense.

That is precisely what we should be doing for any header that is supposed to be used server side. This is like SecOps 101 because if you are not trusting the value, it might as well have been spoofed.

The safe way to figure that out is the following. Only trust the parts of x-forwarded-for that either come from a trusted source or that we set ourselves. It's the fact that we do trust these proxies that allows us to use the first IP we do not recognize, because that must be the one we want. That's exactly what NGINX does (right now) whenever it receives a request.

So the key needs to be overwritten from a trusted source (not revealing it here for security reasons, but you know the header we can use to overwrite the x-forwarder-for)

It's is fair to say that we should not trust all the IPs in x-forwarded-for, because the ones on the left can be spoofed. However, I'm not suggesting we do that. Also, to reiterate, it's not necessary to overwrite the key because the bits we care about have been set by a trusted source.
It's tricky to go deeper without talking about the details of our infra. If you're still not convinced, let's discuss this on a call.

because the bits we care about have been set by a trusted source.

That is NOT true. I want to avoid getting into the discussion of why.
Anyways,
I understand what you are saying, but you are getting ahead of yourself here.
The discussion is NOT about trusted proxies, or best practices, or any of that. You need to include the point that we may not (or probably can't) depend on IP addresses, which makes this discussion moot and a waste of time.
I am explicitly saying that IP addresses are just one of the Signals, and we may need more (like email addresses or some other criteria), which dictates the use of a custom keygen handler.
With #49194, we are picking up the value from a header WE KNOW can't be spoofed and setting it to X-FORWARDER-FOR "as a standard" without increasing the blast radius beyond the endpoint and the middleware.
That is not the case with this PR, hence this can be closed.

because the bits we care about have been set by a trusted source.

That is NOT true. I want to avoid getting into the discussion of why.

It has to be true. We should discuss this privately, though, due to the security implications.

I am explicitly saying that IP addresses are just one of the Signals, and we may need more (like email addresses or some other criteria), which dictates the use of a custom keygen handler.

I understand that, but neither PR uses any signals beyond client IP, so let's discuss that when we use them.

We should discuss this privately, though, due to the security implications.

Sure, We should when we have more time to discuss general knowledge share and stuff. Maybe in the de-team meetings. :)

I understand that, but neither PR uses any signals beyond client IP, so let's discuss that when we use them.

Correct.
#49194 starts the groundwork with the custom handler that, yes, uses an IP address right now but may be expanded or completely refactored with minor impact later if needed. This PR has zero scope for such a change.
So, what do you mean here?

Yep, we can discuss in the meeting or before if you'd like to move forward before then.
I didn't add it here because req.ip is what keyGenerator returns by default.
i.e. I could have done
    keyGenerator: req => {
      return req.ip;
    },

but it already does that. If you'd rather it's explicit, that's fine by me.

I see you continue to keep missing these points:

We need the custom handler (for reasons I have mentioned already) – it doesn't matter if it is explicit or implicit because we can't rely on req.ip only. Period.
This PR adds a change that affects the whole of API, whereas #49194 does not.

It is mu humble opinion that we can move on (without needing to discuss the trusted proxies feature) because the above points are what we need.

It's clear we will need a custom keygen in the long term. I never said otherwise. This is not the long term. As I keep saying, we don't need it yet, because the default does what the custom one would do. They are (in the short term) identical.
It's really not a big deal, but that's what it is.
It's also clear this can affect more than just the mobile auth, but that's an argument for careful QA, not for abandoning the approach.

It is my humble opinion that we can move on (without needing to discuss the trusted proxies feature) because the above points are what we need.

Unfortunately not, because the keygen is contingent on how the IP arrives at the api. The latter is what we need to discuss privately.

but that's an argument for careful QA

Sure.
I am happy to sit on this for weeks and months as long as @Sembauke and @Nirajn2311 are fine with the extended delays – there is no way it is getting past me with a quick QA because it affects my daily tasks.
If you can guarantee that the change is NOT going to affect remotely with a proper report of all the endpoints that are in the play and what effects it has I am happy to move forward.

The latter is what we need to discuss privately.

The discussion is pertinent to using just the IP address. I am saying we need more. You are jumping into the implementation.
We can discuss the needing more (additional signals) bit here – I have laid out my points here.

Let's continue this discussion after we've talked about the security considerations in private. There's nothing to be gained by talking here until we've done that.

I am happy to sit on this for weeks and months as long as @Sembauke and @Nirajn2311 are fine with the extended delays – there is no way it is getting past me with a quick QA because it affects my daily tasks.

we were hoping to get this out by the end of this month

Let's continue this discussion after we've talked about the security considerations in private.

The considerations only matter if we use IP addresses "only", since we may not there is no point discussing.

After a bit more thought, I realised I was wrong about the parts of XFF we can trust. Nothing changes about what we should do upstream (i.e. this PR), but we have to be very careful about the XFF we send to the api.
Sorry about that @raisedadead, I'll explain what I misunderstood in the call today.

Having weighed up the pros and cons, we decided to go with https://github.com/freeCodeCamp/freeCodeCamp/pull/49194 i.e. an XFF header that we're overwriting.
For posterity.

the pro of this PR are that the api is less likely to become vulnerable to XFF spoofing when the infrastructure changes
the con is that we have to remember and account for the api's XFF handling when we change infrastructure

Ultimately, since both approaches introduce coupling between the api and the infra and both require caution when making changes, there was not a perfect choice, but we had to choose one.


Eliminate redundant transposes

We really need to figure out what to do with canonicalizations to stop adding hacks like this. This is what Mehdi was asking in stablehlo discord.
Missed that in discord but replied to Eugene's email. All the HLO canonicalizations have to move somewhere, if not to stable HLO.


Layer refactoring, Full Feature/Vector layers support, Selection features

Full support for vector layers
Refactoring of Layer to support Shapes per Layer
Shape/Drawing and Marker Layer are added on demand part of Layers collection
Shape Selection feature with events on Layer
Automatic update on a parameter change on layers and shapes

Also fixes #62

Major refactoring to use StyleOptions only for full customization


Breaking Change Intoduced with the Removal of Player Attributes via the Integration

What version of Music Assistant has the issue?
2.3.2
What version of the Home Assistant Integration have you got installed?
2024.11.4
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
A breaking changed was introduced in integration version 2024.11.0 that removed the following attributes from media_player entities in home assistant that broke automations:

queue_index
items_in_queue

How to reproduce
Add items to a queue of a music assistant player, check the media_player attributes in the developer tools of home assistant.
Music Providers
Tried:

Spotify
Music Assistant
Radio Browser

Don't have access to other providers.
Player Providers
Tried:

Chromecast
Slimproto
Didn't try other players because I do not have devices that connect via those platforms.

Full log output
music-assistant.log
Additional information
Would it be possible for these attributes to be re-added? These attributes were used for specialized sleep timers. Music assistant is being run as an addon on a windows Hyper-V VM running Home Assistant OS.
What version of Home Assistant Core are your running
2024.11.1
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Alternative

These were removed due to HA policies with the imminent move to core. Have you looked at the new get_queue action? It provides all that you have requested and.more

Thank you. I was not aware of the addition.

Also, congraduations on the accomplishment.


bug: How to make multiline form fixed to top with list

Type: bug
Platform: all
I cannot find a way to make ionic to have header, multiline subheader and ionic list to work together. How I can make it?

Greetings @vlados!
My sensors indicate that you have created an issue on our tracker requesting usage help, rather than an actual error with Ionic framework.
This GitHub issue tracker is used to track framework features, problems, and development.
If you wish to get help using the framework itself, the recommended place is the forum. There are many humans there who would be happy to offer sage advice.
Thank you for allowing me to assist you.


Raspberry PI and old node versions

The following errors occurred when installing old node versions (simple nvm install $VERSION) on an RPi4 with the default Raspbian flavor of Linux:

[ ] 0.12 (nvm tries v0.12.18)
[ ] 0.8 (nvm tries v0.8.28 -- same error but different line numbers)

$>./configure --prefix=/home/pi/.nvm/versions/node/v0.12.18 --without-snapshot<
Traceback (most recent call last):
  File "./configure", line 1009, in <module>
    configure_node(output)
  File "./configure", line 539, in configure_node
    o['variables']['gcc_version'] = 10 * cc_version[0] + cc_version[1]
IndexError: tuple index out of range

[ ] 0.6 (nvm tries v0.6.21)

/usr/bin/g++ -o obj/release/accessors.o -c -fno-rtti -fno-exceptions -Wall -W -Wno-unused-parameter -Wnon-virtual-dtor -Wno-abi -pedantic -mfloat-abi=softfp -O3 -fomit-frame-pointer -fdata-sections -ffunction-sections -ansi -DCAN_USE_VFP_INSTRUCTIONS -DUSE_EABI_HARDFLOAT=0 -DV8_TARGET_ARCH_ARM -DENABLE_DEBUGGER_SUPPORT -I/home/pi/.nvm/.cache/src/node-v0.6.21/files/deps/v8/src /home/pi/.nvm/.cache/src/node-v0.6.21/files/deps/v8/src/accessors.cc
In file included from /usr/include/features.h:448,
                 from /usr/include/arm-linux-gnueabihf/bits/libc-header-start.h:33,
                 from /usr/include/stdio.h:27,
                 from /home/pi/.nvm/.cache/src/node-v0.6.21/files/deps/v8/src/../include/v8stdint.h:33,
                 from /home/pi/.nvm/.cache/src/node-v0.6.21/files/deps/v8/src/../include/v8.h:41,
                 from /home/pi/.nvm/.cache/src/node-v0.6.21/files/deps/v8/src/v8.h:52,
                 from /home/pi/.nvm/.cache/src/node-v0.6.21/files/deps/v8/src/accessors.cc:28:
/usr/include/arm-linux-gnueabihf/gnu/stubs.h:7:11: fatal error: gnu/stubs-soft.h: No such file or directory
 # include <gnu/stubs-soft.h>
           ^~~~~~~~~~~~~~~~~~
compilation terminated.
scons: *** [obj/release/accessors.o] Error 1
scons: building terminated because of errors.
Waf: Leaving directory `/home/pi/.nvm/.cache/src/node-v0.6.21/files/out'
Build failed:  -> task failed (err #2):
        {task: libv8.a SConstruct -> libv8.a}

If any additional install parameters are found to fix it, I'd be more than happy to add them to nvm so it can automate them.

The 0.8 and 0.12 errors stem from a cc invocation whose meaning has changed:

0.12: https://github.com/nodejs/node/blob/v0.12/configure#L483
0.8: https://github.com/nodejs/node/blob/v0.8.28/configure#L330

Older gcc versions used to print semver with the -dumpversion flag.  Now -dumpversion prints major version and -dumpfullversion prints semver, so ideally nvm would run -dumpversion and somehow intercept and rewrite the call.

Is there any way to fix this now?

@BenMake since the issue is still open, you can assume there’s not.

@BenMake I take a creak at it.

Encountered the same issue trying to install node 12 on RPi4, any way to work around this?


Refactor tests

[ ] Move existing tests -> integration, run them consistently

[ ] Write new unit tests for internal functions

[ ] Cover main.py

[ ] Cover cli.py

[ ] Update default ignore options

[ ] Exclude tests in .coveragerc?

[ ] Pull more boilerplate test code out -> conftest.py

[ ] Restructure tests from record-oriented to match type-oriented (more in line with how feature development/breaking works)?

The above is fine, but I think the big one is restructuring tests of ETL classes to simply confirm that data is correctly being uploaded into the DB. Right now, we check this indirectly by having test cases use the query module to run searches, but that's really just an indirect test (more of an integration). Instead, we should be testing that ETL classes upload data in the correct way, and then, that given a particular test DB, the query class can look it up correctly.


Project: Email Automation

Project name
Email Automation
Description
In the corporate world, emails are key tools for the work of companies.
In this project, the idea is to create routines by receiving emails such as:

Filter your emails by specific email (From) or subject

Filter specific attachment file with email and save in OneDrive.

Create Todo task.

Create Calendar event

Repo URL
https://github.com/teleginski/hack-together
Team members
teleginski

Thank you for your submission @teleginski! Would you be willing to record a short video to demonstrate the app? It's not required for the hackathon but it would help us showcase your work internally at Microsoft and publicly in the community 😊


remote.process.argv has an extra arg in osx when opening file with app from Finder

When opening my Electron app in osx by opening it with a file from Finder, remote.process.argv has an additional arg e.g. ["/Users/me/code/repo/LightTable/builds/lighttable-0.8.0-alpha-mac/LightTable.app/Contents/MacOS/Electron" "-psn_0_12340164"]. This additional arg appears to be an apple event. This additional arg makes process.argv unreliable/unusable for opening files from the commandline. Have you seen this before and is this expected behavior?
I'm seeing this for OSX 10.10.4 for Electron 0.31.1 and 0.34.5

Are you want open electron app with a file?

This argument is appended by Finder and there is no way to tell Finder not to do it, usually people are just removing the argument starts with -psn.

@zcbenz Good to know. Thanks!


chore: update capitalization guideline

SUMMARY
Update capitalization guideline to exempt user inputs from cap transformation.
Based on the discussion here: https://github.com/apache/superset/issues/12343#issuecomment-756482628
cc @mihir174
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
N/A
TEST PLAN
N/A

Codecov Report

Merging #12828 (e534bae) into master (e3db935) will decrease coverage by 3.60%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12828      +/-   ##
==========================================
- Coverage   66.65%   63.05%   -3.61%
==========================================
  Files        1021     1021
  Lines       50125    50104      -21
  Branches     5190     5190
==========================================
- Hits        33411    31591    -1820
- Misses      16575    18299    +1724
- Partials      139      214      +75

Flag
Coverage Δ

cypress
?

javascript
62.00% <ø> (ø)

python
63.74% <ø> (-0.36%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Codecov Report

Merging #12828 (e534bae) into master (e3db935) will decrease coverage by 3.60%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12828      +/-   ##
==========================================
- Coverage   66.65%   63.05%   -3.61%
==========================================
  Files        1021     1021
  Lines       50125    50104      -21
  Branches     5190     5190
==========================================
- Hits        33411    31591    -1820
- Misses      16575    18299    +1724
- Partials      139      214      +75

Flag
Coverage Δ

cypress
?

javascript
62.00% <ø> (ø)

python
63.74% <ø> (-0.36%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Related: https://github.com/apache/superset/issues/12829

Related: https://github.com/apache/superset/issues/12829


Update deployment.toml configs for Berlin Toolkit

This PR is to update the docs with the deployment.toml configs for Berlin toolkit.

@aka4rKO @Akila94  please verify the tags on https://docs.google.com/document/d/17_QebQ-cfeKNbPqcTVnhLmwtY-sHW32YRks2hJD1NJA/edit# as well.


Rework NumberTextStyle to use inout Cache

Introduction
#108 makes it possible to decrease the cost of NumberTextStyle.
Details
It should be made into a message that may or may not resolve per differentiation.
Comments
No more ~300k unique-by-definition styles shoved into an NSCache per XCTestCase/test.

This rework will be painful. I can already feel it 😣

I’m considering a rework along the lines of protocol composition. Given that the DiffableTextStyle implementation already exists, its apparent that it can be reduced to some (pseudo) protocol like this:
protocol Resolved {
    var format:    Format    { get }
    var bounds:    Bounds    { get }
    var precision: Precision { get }

    func snapshot(String) -> Snapshot
    func characters(Format, Number, Value) -> String

    func value(Number) throws -> Value
    func number(Snapshot, (some Kind).Type) throws -> Number?
    func number(Proposal, (some Kind).Type) throws -> Number?
}

It could also be grouped and divided as needed to accommodate each style variant. It is, for example, known that the only difference between the number, percent and currency style lies in the implementation of precision and the snapshot method.

Gonna start working on this now...

 It turn out that it’s a lot easier to design something when you can focus on it rather than spending all your effort on figuring out why some FormatStyle.Strategy can't parse some localized currency. Who’d a thunk it?

I haven’t enable all tests, yet, but the rework is essentially complete in 331f58a297f19f4046e66940f82cb9a6de0baa59.


[DNDeviceUser networkProfileID]: unrecognized selector sent to instance 0x7fb6815df730'

Receiving this issue in what appears to be the appDelegate during launch
+[DNModuleHelper addModule:toModuleList:subscription:] [line 30] INFO: Module DRLogicMainController is already subscriped to RichMessage
2016-07-15 11:22:40.996 atlantis[26861:15398934]
+[DNModuleHelper addModule:toModuleList:subscription:] [line 30] INFO: Module DRLogicMainController is already subscriped to SyncMessageRead
2016-07-15 11:22:40.996 atlantis[26861:15398830]
+[DNModuleHelper addModule:toModuleList:subscription:] [line 30] INFO: Module DRLogicMainController is already subscriped to SyncMessageDeleted
2016-07-15 11:22:40.998 atlantis[26861:15398678] -[DNDeviceUser networkProfileID]: unrecognized selector sent to instance 0x7fb6815df730
2016-07-15 11:22:41.001 atlantis[26861:15398678] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[DNDeviceUser networkProfileID]: unrecognized selector sent to instance 0x7fb6815df730'
*** First throw call stack:
(
	0   CoreFoundation                      0x000000010cfced85 __exceptionPreprocess + 165
	1   libobjc.A.dylib                     0x000000010bf9adeb objc_exception_throw + 48
	2   CoreFoundation                      0x000000010cfd7d3d -[NSObject(NSObject) doesNotRecognizeSelector:] + 205
	3   CoreFoundation                      0x000000010cf1dcfa ___forwarding___ + 970
	4   CoreFoundation                      0x000000010cf1d8a8 _CF_forwarding_prep_0 + 120
	5   atlantis                            0x000000010941eb6a -[DNUserDetails initWithDeviceUser:] + 218
	6   atlantis                            0x0000000109457ad7 +[DNAccountController currentDeviceUser] + 263
	7   atlantis                            0x0000000109455143 +[DNAccountController registrationDetails] + 83
	8   atlantis                            0x000000010942e82d -[DNDonkyCore initialiseWithAPIKey:userDetails:success:failure:] + 189
	9   atlantis                            0x000000010955dbd0 _TFC8atlantis11AppDelegate11applicationfTCSo13UIApplication29didFinishLaunchingWithOptionsGSqGVs10DictionaryCSo8NSObjectPs9AnyObject____Sb + 2224
	10  atlantis                            0x000000010955e294 _TToFC8atlantis11AppDelegate11applicationfTCSo13UIApplication29didFinishLaunchingWithOptionsGSqGVs10DictionaryCSo8NSObjectPs9AnyObject____Sb + 180
	11  UIKit                               0x000000010a5a39ac -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 272
	12  UIKit                               0x000000010a5a4c0d -[UIApplication _callInitializationDelegatesForMainScene:transitionContext:] + 3415
	13  UIKit                               0x000000010a5ab568 -[UIApplication _runWithMainScene:transitionContext:completion:] + 1769
	14  UIKit                               0x000000010a5a8714 -[UIApplication workspaceDidEndTransaction:] + 188
	15  FrontBoardServices                  0x00000001109c58c8 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 24
	16  FrontBoardServices                  0x00000001109c5741 -[FBSSerialQueue _performNext] + 178
	17  FrontBoardServices                  0x00000001109c5aca -[FBSSerialQueue _performNextFromRunLoopSource] + 45
	18  CoreFoundation                      0x000000010cef4301 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
	19  CoreFoundation                      0x000000010ceea22c __CFRunLoopDoSources0 + 556
	20  CoreFoundation                      0x000000010cee96e3 __CFRunLoopRun + 867
	21  CoreFoundation                      0x000000010cee90f8 CFRunLoopRunSpecific + 488
	22  UIKit                               0x000000010a5a7f21 -[UIApplication _run] + 402
	23  UIKit                               0x000000010a5acf09 UIApplicationMain + 171
	24  atlantis                            0x0000000109568342 main + 114
	25  libdyld.dylib                       0x000000010ec4a92d start + 1
	26  ???                                 0x0000000000000001 0x0 + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException
(lldb)

@dolbex is this with the latest release of the SDK?  Can you confirm any calls you're making on startup please?

Yes, this is upgrading the latest release of the modules folder.
here is my didFinishLaunchingWithOptions
func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {
        // Override point for customization after application launch.
        Fabric.with([Crashlytics.self])

        createAlertMessageLabel()

        DCAAnalyticsController.sharedInstance().start()
        DRIMainController.sharedInstance().start()
        DRLogicMainController.sharedInstance().start()
        DNDonkyCore.sharedInstance().initialiseWithAPIKey(globalConfig.strongviewApiKey, userDetails: nil, success: { (response) -> Void in

                NSLog("Donky successfully initialised");

                PushNotificationManager.pushManager().delegate = self
                PushNotificationManager.pushManager().handlePushReceived(launchOptions)
                PushNotificationManager.pushManager().sendAppOpen()
                PushNotificationManager.pushManager().registerForPushNotifications()

            }, failure: { (error) -> Void in
                NSLog("Donky init failed: \(error)")
            }
        )

        let apiRequest = ApiRequest()
        apiRequest.registerDevice()

        return true
    }

Not quite sure what I did but fiddled with it some more and got it working. Must have been something with updating the files.


Text Input

Add the ability for text input in addition to speech. This will allow for other programs to easily communicate with jasper and simplify testing.
This is currently being worked on in the main fork - # 280. Will wait for functionality to be added there.

Use --local arg to use manual input for testing. Will utilize this to allow other programs to interact with Nikita


(OraklNode) Setup host and pubsub from New()

Description
host and pubsub was part of App type structure of aggregator, yet it was initialized on calling Run. it seems more natural to be initialized on New
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

Deployment

[ ] Should publish npm package
[ ] Should publish Docker image

test code error due to removal of all time.Sleep from merge conflicts, there's awaiting PR solving this issue by updating message bus package


Telemetry integration

The telemetry library aims to be a unified metrics reporting system for the BEAM ecosystem. It's currently used by Ecto and Phoenix
It could be good for Rihanna to support it so that people can hook into it for their monitoring of Rihanna.
https://github.com/beam-telemetry/telemetry
Possibly events:
[:rihanna, :job, :done]

We could also add some pollable metrics https://github.com/beam-telemetry/telemetry_poller
[:rihanna, :jobs_queued_count]
[:rihanna, :dead_job_count]
[:rihanna, :jobs_running_count]

Other events:
[:rihanna, :job, :failed]
[:rihanna, :job, :retried]
[:rihanna, :job, :enqueued]

Closing this since it's integrated as of 2.0


[windows] update ffi and win32 dependencies

The current dependency locks are on older versions of win32 (2.70 available) and ffi packages (2.0.0 available)
https://github.com/bitsdojo/bitsdojo_window/blob/master/bitsdojo_window_windows/pubspec.yaml#L16
This prevents developers from updating their own dependencies.
Thanks

ffi now updated to 2.0.0 and win32 to 3.0.0


getAlbumsToQueue, pageContainsAlbums and hasQueueSupport are undocumented

The getAlbumsToQueue, pageContainsAlbums and hasQueueSupport functions are undocumented. Usage of them can be found in the myhentaicomics ripper.
These need to be documented

These have been documented in the wiki


check_periodic should waiting while as less one pair in progress

while test i saw when check_periodic run check_start while prevision paring still in progress
this can produce incorrect nomination
fix like this
    def check_periodic(self) -> bool:
 +       for pair in self._check_list:
 +          if pair.state == CandidatePair.State.IN_PROGRESS:
 +              return True

        # find the highest-priority pair that is in the waiting state

I don't think this is correct. According to the RFC, the periodic timer triggers new checks whenever it fires, I don't see anything saying the checks must be performed one after another. This would make the process very slow when you have many candidate pairs to test.
Am I reading the RFC wrong?

Hello?

I was test on windows with 4 candidates
rfc didnt precise about this case
but rfc says about in order send test
aioice uses logic from pjproject ice, where have case in periodic when candidate in progress, just resend transaction
In many implementation of ice, periodic timer related with transaction stun timer
but it will be interesting ask to authors of ice rfc


Run scenarios on a daily schedule

Currently the scenario runs are started by hand.
We should run them automatically scheduled by cron.

Fixed by https://github.com/raiden-network/scenarioplayer.ci.raiden.network/pull/5


Potential etcd liveness issue in joint consensus

as reported by PingCap
https://github.com/etcd-io/etcd/issues/12359
there is already a PR being reviewed, but it has been stuck in the queue for 6 months+
https://github.com/etcd-io/etcd/pull/12435

This issue is in the upstream library. It is extremely unlikely to be triggered even in long term.

This issue has minimal impact on us for the next 12 months.

joint consensus has been disabled for now.

joint consensus is not used atm.


When spring cloud  deploy by WAR,how could i use zuul visit eureka service don't need application name?

Spring Cloud is registered with Eureka, The service ID is service-appuser, The service is deployed to Tomcat via War. Its War name/ID is appuser. It zuul configuration is：
zuul:
sensitive-headers:
routes:
api-appuser:
path: /api-appuser/**
serviceId: service-appuser
I have to use ‘http://localhost:8080/zuul/api-appuser/brain-service-appuser/dataSummary’, and add War name to the api-appuser in order to visit the service-appuser via zuul. How could I access it without adding the War name?like this:'http://localhost:8080/zuul/api-appuser/dataSummary'

So http://localhost:8080/zuul/api-appuser/brain-service-appuser/dataSummary works?  This sounds like a Tomcat configuration issue more than something to do with Zuul.

So http://localhost:8080/zuul/api-appuser/brain-service-appuser/dataSummary works? This sounds like a Tomcat configuration issue more than something to do with Zuul.

Yes.
I get it. but Is it possible to achieve this through the configuration of Eureak registration?

So http://localhost:8080/zuul/api-appuser/brain-service-appuser/dataSummary works? This sounds like a Tomcat configuration issue more than something to do with Zuul.

Yes.
I get it. but Is it possible to achieve this through the configuration of Eureak registration?

Sorry,i make a mistake,the url should is http://localhost:8080/zuul/api-appuser/service-appuser/dataSummary  and it works
And when i use Feign visited service 'service-appuser',i must use @FeignClient(value = "service-appuser/appuser")

Do you have have zuul.stripPrefix=true?

Do you have have zuul.stripPrefix=true?

No,but this property default value is true,so i add zuul.stripPrefix=flase,nothing has changed.
Probably spring boot?
Property server.contextPath  does not work.

Server context path doesn't apply when deployed as a war

Server context path doesn't apply when deployed as a war

Ok, thank you very much!

To be honest I am not sure what else we can do, maybe you can write a custom filter to manipulate the path to work for your use case.

To be honest I am not sure what else we can do, maybe you can write a custom filter to manipulate the path to work for your use case.

ok,
thank you for your advice!I'll try

Closing this due to inactivity. Please re-open if there's more to discuss.


ServiceKit 2.0

Removes ServiceCache

Singletons can still be registered using Services.instance(...). The service cache is unnecessary if services are injected at initialization time.

Removes service Config

Only one service can be registered against a given protocol now. If multiple services are registered to the same protocol, the last registered service will be used. The goal behind this change is to make services easier to reason about and reduce possible runtime error cases.

Adds Services.extend()

Non-singleton services can now be extended using Services.extend
s.extend(Commands.self) { commands, c in
    try commands.add(c.make(MigrateCommand.self), named: "migrate")
}

This gives service providers more power to configure applications.

Renames module to ServiceKit.
Removes Service protocol.

This protocol is no longer required since the Services registration methods now have unique names. Removing this empty protocol requirement should make it easier to get started using services.

Removes ServiceType protocol.

Services no longer support registering services against an Any.Type interface. While this change greatly improves type safety and internal consistency, it is no longer possible to use ServiceType since it relied on an array of [Any.Type] interfaces. It's possible to update the protocol to only register Self.self as a supported interface, but I'm not sure how useful that would be.

Removes all dependencies besides SwiftNIO.

NIO is still required since Container must hold a reference to EventLoop. This is a fundamental part of how ServiceKit works, since many services (like HTTPClient, Databases, etc) require an event loop to initialize.

Hey @tanner0101, you just merged a pull request, have a coin!
You now have 1030 coins.


account_id is a required param

Traceback (most recent call last):
File "/home/informer-master/app/bot.py", line 35, in
raise Exception('informer.py <account_id> - account_id is a required param')
Exception: informer.py <account_id> - account_id is a required param
but i already finished the informer.env

I directly assign the account_id of /homeyinformer-master/app/bot'py to the exact id, instead of getting it from the metric

sqlalchemy.exc.InterfaceError: (mysql.connector.errors.InterfaceError) 2003: Can't connect to MySQL server on 'docker.for.mac.localhost:3307' (111 Connection refused)
(Background on this error at: http://sqlalche.me/e/rvf5)
new issue came out

I solved the problem by installing mysql locally and running it, and changing the informer.env port to the default 3306

new problem here:
Traceback (most recent call last):
File "/home/informer-master1/app/bot.py", line 42, in
informer = TGInformer(
File "/home/informer-master1/app/informer.py", line 145, in init
self.loop.run_until_complete(self.bot_interval())
File "/usr/lib/python3.10/asyncio/base_events.py", line 646, in run_until_complete
return future.result()
File "/home/informer-master1/app/informer.py", line 642, in bot_interval
self.client = TelegramClient(session_file, self.account.account_api_id, self.account.account_api_hash)
File "/usr/local/lib/python3.10/dist-packages/telethon/client/telegrambaseclient.py", line 262, in init
session = SQLiteSession(session)
File "/usr/local/lib/python3.10/dist-packages/telethon/sessions/sqlite.py", line 47, in init
c = self._cursor()
File "/usr/local/lib/python3.10/dist-packages/telethon/sessions/sqlite.py", line 228, in _cursor
self._conn = sqlite3.connect(self.filename,
sqlite3.OperationalError: unable to open database file
I created my own informer_db database in mysql under the root user.
Maybe that's the problem.

https://stackoverflow.com/questions/76620568/when-i-use-https-github-com-paulpierre-informer-for-this-project-i-encountere
I have been able to run the software successfully, I suggest you refer to this link to troubleshoot the error

So far I can still only run quick_start.sh

after i run ./start.sh
INFO:root:init_monitor_channels: Monitoring channels: []
app_informer    | INFO:root:Channel METADATA: {}
app_informer    | INFO:root:### {count} Running bot interval
app_informer    | INFO:root:init_keywords: Monitoring keywords: [
app_informer    |     {
app_informer    |         "id": 1,
app_informer    |         "name": "Binance",
app_informer    |         "regex": "(binance|bnb)"
app_informer    |     }
app_informer    | ]
app_informer    | INFO:root:init_keywords: Monitoring keywords: [
app_informer    |     {
app_informer    |         "id": 1,
app_informer    |         "name": "Binance",
app_informer    |         "regex": "(binance|bnb)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 2,
app_informer    |         "name": "Huobi",
app_informer    |         "regex": "(huobi)"
app_informer    |     }
app_informer    | ]
app_informer    | INFO:root:init_keywords: Monitoring keywords: [
app_informer    |     {
app_informer    |         "id": 1,
app_informer    |         "name": "Binance",
app_informer    |         "regex": "(binance|bnb)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 2,
app_informer    |         "name": "Huobi",
app_informer    |         "regex": "(huobi)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 3,
app_informer    |         "name": "Bittrex",
app_informer    |         "regex": "(bittrex)"
app_informer    |     }
app_informer    | ]
app_informer    | INFO:root:init_keywords: Monitoring keywords: [
app_informer    |     {
app_informer    |         "id": 1,
app_informer    |         "name": "Binance",
app_informer    |         "regex": "(binance|bnb)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 2,
app_informer    |         "name": "Huobi",
app_informer    |         "regex": "(huobi)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 3,
app_informer    |         "name": "Bittrex",
app_informer    |         "regex": "(bittrex)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 4,
app_informer    |         "name": "Bitfinex",
app_informer    |         "regex": "(bitfinex)"
app_informer    |     }
app_informer    | ]
app_informer    | INFO:root:init_keywords: Monitoring keywords: [
app_informer    |     {
app_informer    |         "id": 1,
app_informer    |         "name": "Binance",
app_informer    |         "regex": "(binance|bnb)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 2,
app_informer    |         "name": "Huobi",
app_informer    |         "regex": "(huobi)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 3,
app_informer    |         "name": "Bittrex",
app_informer    |         "regex": "(bittrex)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 4,
app_informer    |         "name": "Bitfinex",
app_informer    |         "regex": "(bitfinex)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 5,
app_informer    |         "name": "Coinbase",
app_informer    |         "regex": "(coinbase)"
app_informer    |     }
app_informer    | ]
app_informer    | INFO:root:init_keywords: Monitoring keywords: [
app_informer    |     {
app_informer    |         "id": 1,
app_informer    |         "name": "Binance",
app_informer    |         "regex": "(binance|bnb)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 2,
app_informer    |         "name": "Huobi",
app_informer    |         "regex": "(huobi)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 3,
app_informer    |         "name": "Bittrex",
app_informer    |         "regex": "(bittrex)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 4,
app_informer    |         "name": "Bitfinex",
app_informer    |         "regex": "(bitfinex)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 5,
app_informer    |         "name": "Coinbase",
app_informer    |         "regex": "(coinbase)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 6,
app_informer    |         "name": "Kraken",
app_informer    |         "regex": "(kraken)"
app_informer    |     }
app_informer    | ]
app_informer    | INFO:root:init_keywords: Monitoring keywords: [
app_informer    |     {
app_informer    |         "id": 1,
app_informer    |         "name": "Binance",
app_informer    |         "regex": "(binance|bnb)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 2,
app_informer    |         "name": "Huobi",
app_informer    |         "regex": "(huobi)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 3,
app_informer    |         "name": "Bittrex",
app_informer    |         "regex": "(bittrex)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 4,
app_informer    |         "name": "Bitfinex",
app_informer    |         "regex": "(bitfinex)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 5,
app_informer    |         "name": "Coinbase",
app_informer    |         "regex": "(coinbase)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 6,
app_informer    |         "name": "Kraken",
app_informer    |         "regex": "(kraken)"
app_informer    |     },
app_informer    |     {
app_informer    |         "id": 7,
app_informer    |         "name": "Poloniex",
app_informer    |         "regex": "(poloniex)"
app_informer    |     }
app_informer    | ]

nothing happened in mysql tables.


Add a check for duplicate neighbouring cells within the theory pair counters (periodic)

Is your feature request related to a problem? Please describe.
When periodic boundary conditions are enabled, Corrfunc should be able to calculate separations out to the maximum possible separation. Instead, Corrfunc might fail with the following error message
*Error message:
../../utils/gridlink_utils_float.c> ERROR: nlattice = 4 is so small that with periodic wrapping the same cells will be counted twice ....exiting
../../utils/gridlink_utils_float.c> Please reduce Rmax = 100.000000 to be a smaller fraction of the particle distribution region = 205.000000

Describe the solution you'd like
While adding a new neighbouring cell, add a check for duplicate neighbouring cells. A similar check is already performed here. Easiest option would be to package those lines of code into a function within gridlink_utils.c.src and call that function from all relevant assign_ngb calls.
Describe alternatives you've considered
N/A
Additional context
Reported by @JonLoveday in #69

@JonLoveday I pushed a fix via  e53bce3050139337dae5723a3601e707f1f37920. Should not be too long before we can merge this into master.
If possible, would you please checkout the code_quality branch and see if the issue is resolved?

@JonLoveday The fix is now on the master branch - I am closing this issue.
If the fix does not solve your case, please feel free to re-open this issue.

This is not fixed - see #210

This is done / superseded by #277


Link handler not firing

VSCode Version: master

I register the following link handler:
regexp: /^([^\s].*)\((\d+|\d+,\d+|\d+,\d+,\d+,\d+)\):\s+(error|warning|info)\s+(TS\d+)\s*:\s*(.*)$/
matchIndex: 1
no validator.
However no link is computed in the following terminal output:
> tsc -p .
Press any key to close the terminal
HelloWorld.ts(3,17): error TS2339: Property 'loog' does not exist on type 'Console'.

However IMO it should match the line.

I couldnät even get a simple case like this to work: /(error|warning|info)/
Can you provide me with an example how to use the API to match an error message like
HelloWorld.ts(3,17): error TS2339: Property 'loog' does not exist on type 'Console'.

This worked fine for me:
registerLinkMatcher(/^([^\s].*)\((\d+|\d+,\d+|\d+,\d+,\d+,\d+)\):\s+(error|warning|info)\s+(TS\d+)\s*:\s*(.*)$/, console.log, 1)

Note that you need to hold ctrl/cmd now and also that the hover doesn't yet apply to custom link handlers (this is a bug which I'll fix up now).

Should work including the hint now:

OK. Sorry for the noise then. I was expecting to see a blue underling link indication when hovering over it.

@dbaeumer this changed to align with the editor as much as possible. I didn't want to underline links by default due to lesser line-height than the editor and it could conflict with terminal styles.

I found out why this isn't working for me. See #23262 and #23263


How to open vlc on a non-primary display?

I have a question about Vlc.DotNet.
Generic information

Vlc.DotNet version : 2.2.1
Vlc.DotNet project used : Core
libvlc version : (3.0.6) (x64) nuget package
.net version : 4.7.1
Project language : C#
Project build architecture : x64
Operating system : Windows 10 (x64)

Is it possible to render/open vlc on a monitor/display that is not primary?
I ask this because vlc command prompt has arguments like "--directx-device=" and "--qt-fullscreen-screennumber=". Also, there is an option called Fullscreen video device in Tools>Preferences>Video of vlc app.

@jeremyVignelles thank you for the reply. I managed to do that by using winapis - EnumWindow, GetWindowThreadProcessId, GetWindowText, GetWindowTextLength and MoveWindow.

Can you share a sample code for the future developers?

Sure. Below is the code I used to do that. Also I referred to this stack overflow post.
However, the catch is that this code will move the window after it has opened (and not before/at the time of instantiation).
Warning: As this is a sample code it might not have good memory management.
`
    internal class Video
    {
        [DllImport("user32.dll", SetLastError = true)]
        static extern uint GetWindowThreadProcessId(IntPtr hWnd, out int lpdwProcessId);

        [DllImport("user32.dll")]
        [return: MarshalAs(UnmanagedType.Bool)]
        static extern bool EnumWindows(WndEnumProc lpEnumFunc, IntPtr lParam);

        [DllImport("user32.dll", CharSet = CharSet.Auto, SetLastError = true)]
        static extern int GetWindowText(IntPtr hWnd, StringBuilder lpString, int nMaxCount);

        [DllImport("user32.dll", SetLastError = true, CharSet = CharSet.Auto)]
        static extern int GetWindowTextLength(IntPtr hWnd);

        [DllImport("user32.dll", SetLastError = true)]
        internal static extern bool MoveWindow(IntPtr hWnd, int X, int Y, int nWidth, int nHeight, bool bRepaint);

        private delegate bool WndEnumProc(IntPtr hWnd, IntPtr lParam);
        private VlcMediaPlayer mediaPlayer;

        private List<IntPtr> GetWindowsForProcessId(int processId)
        {
            List<IntPtr> windowsHandle = new List<IntPtr>();
            List<IntPtr> childWindowsHandle = new List<IntPtr>();

            GCHandle gcHandle = GCHandle.Alloc(windowsHandle);

            if (EnumWindows(EnumWindowProc, (IntPtr)gcHandle))
            {
                if (windowsHandle.Count > 0)
                {
                    foreach (IntPtr handle in windowsHandle)
                    {
                        int pId;

                        GetWindowThreadProcessId(handle, out pId);

                        if (pId == processId)
                        {
                            childWindowsHandle.Add(handle);
                        }
                    }
                }
            }

            gcHandle.Free();

            return childWindowsHandle;
        }

        private bool EnumWindowProc(IntPtr hWnd, IntPtr lParam)
        {
            GCHandle handle = (GCHandle)lParam;
            List<IntPtr> windowHandles = handle.Target as List<IntPtr>;

            windowHandles.Add(hWnd);

            return true;
        }

        private void MoveVlcWindow()
        {
            int processId = Process.GetCurrentProcess().Id;

            List<IntPtr> handles = GetWindowsForProcessId(processId);

            foreach (IntPtr handle in handles)
            {
                int length = GetWindowTextLength(handle);

                StringBuilder str = new StringBuilder(length + 1);

                GetWindowText(handle, str, str.Capacity);

                if (str.ToString().CompareTo("VideoTitle") == 0)
                    MoveWindow(handle, 1920, 0, 1920, 1080, true);//Hard coded to move to the second screen. One can use EnumDisplayMonitors winapi function to get all available displays and their rects and use rect values here.
            }
        }

        private void PlayVideo()
        {
            var libDirectory = new DirectoryInfo("Path\To\Vlc.dll");

            mediaPlayer = new Vlc.DotNet.Core.VlcMediaPlayer(libDirectory, new string[] { "--video-title=VideoTitle", "--no-video-title-show" });

            mediaPlayer.SetMedia(new Uri(link));

            mediaPlayer.Play();
        }

        internal Video()
        {
            PlayVideo();
            MoveVlcWindow();
        }
    }

`


Font update

Added Montserrat font files
Replaced the Gotham sets to be Montserrat
Removed Gotham font files

Built successfully and netlify preview appears to be correct


npm install does not verify shrinkwrap correctness

When you do npm install in a folder which has an npm-shrinkwrap.json file it will only verify that top level dependencies have the same version as per node_modules & npm-shrinkwrap.json
It does not recursively verify that your node_modules tree and npm-shrinkwrap.json file agree.

2950 ended up being rejected in favor of https://github.com/npm/npm/issues/6928


add new threePoints

could you take a look @javierarce

Thanks @javierarce take a look

@javierarce fixed

:+1:


Copy specific parts of collection (with history) to another collection

I'm try to do something like this:
{
    "TelemetryEnableTrace": true,
    "Source": {
        "Collection": "http://<IP_ADDRESS>:8080/tfs/Collection1/",
        "Name": "Dev/Src/App/AddPdfBookmark"
    },
    "Target": {
        "Collection": "http://<IP_ADDRESS>:8080/tfs/Collection2/",
        "Name": "Dev/Src/App/AddPdfBookmark"
    },

    ...
}

I just want to copy the source code from one collection to another and maintain the full history. I'm not sure which Processor I should use nor am I sure if your code even does what I'm trying to do.
Any tips?
Thanks,
Darren

@fdncred, I don't have any processors for Source Code as that is well covered by Git-TFS (https://github.com/git-tfs/git-tfs) and the focus here is all of the other things that need copied.
Check the documentation on http://vsts-bulk-editor.readthedocs.io/en/latest/ for what we do support.

@MrHinsh Unfortunately it's not as well covered as I need it to be. So I wrote my own.  Thanks for answering.


Updated to work with Engine Version 4.13

replaced deprecated AttachTo() with SetupAttachment(),
renamed PSConstants and PSVariables to PSConstant and PSVariable (?)
I don't really know why the renaming was necessary, but it worked.

Hey.
Cool, thanks!

Hey, just for everyone's information - the reason the rename is necessary for 4.13 is because "PSConstants" and "PSVariables" are used by OculusStressTests.cpp now.
You can give them any other unique name and they work :) .

kekeke, typical :3


Updated notebooks/experimental storage

Not sure how you want to manage it, but I updated the gromacs tps example to use the experimental SimStore. It works. As currently CVs are under 'storable_functions' I make a dict then select for choosing named cv's. Other than that it's been dropped in.
cv_dict = {fn.name:fn for fn in list(flexible.storable_functions)} # Extract the cv's from storage where they're under storable_functions
phi = cv_dict['phi']
psi = cv_dict['psi']

Obviously don't accept this pull request. I'm doing it to highlight the commit, which may be useful to you.

As currently CVs are under 'storable_functions' I make a dict then select for choosing named cv's.

I fixed this this morning, literally just a couple hours before your commits. I haven't even opened the PR yet. I'll be combining it with some additional testing for SimStore. Here's the commit: https://github.com/dwhswenson/openpathsampling/commit/6ef1284de458d863093283985e66d946719cb5a5
We'll keep this on hold until that can get merged in (I expect to open the PR on that tomorrow; probably to be merged by end of weekend).

With #985 merged in, could you try against that? It should now work without needing to build the cv_dict (that should now be in storage.cvs).


Hit an assert in CollisionBody::~CollisionBody

Hi,
I am hitting an assert when destroying a collision body in a dynamics world.
Assertion failed: (mContactManifoldsList == nullptr), function ~CollisionBody, file ext/reactphysics3d/src/body/CollisionBody.cpp, line 54.
See:

https://github.com/andreasdr/tdme2/blob/reactphysics3d-current/src/tdme/engine/physics/RigidBody.cpp
https://github.com/andreasdr/tdme2/blob/reactphysics3d-current/src/tdme/engine/physics/World.cpp

Best regards
Andreas

JFI: I am adding a collision body in a frame and then just remove it after several frames(means after several world.update() calls). So nothing special at all.

I think I have fixed this issue with this commit in the develop branch.
Can you confirm that it is also fixed on your side in the develop branch ?

Hi,
This seem to work! Thank you.
Best regards
Andreas

Seems to be fixed. Thank you.

Ok Thanks. The fix is now merged in the master branch.


FPGA refactor #1560

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


display date user created account in Account Details

What's the problem this feature will solve?
Sometimes we maintainers want users with very old accounts to test a new feature, because old accounts have weird properties (see #3632). But if users don't know how old their accounts are, they don't know whether they should make a special effort to test the thing.
Describe the solution you'd like
A logged-in user should be able to see "Account created on date" in the Account Details section of their Account Settings page.
Additional context
(This would help me with testing 2FA right now).

Good First Issue: This issue is good for first time contributors. If you've already contributed to Warehouse, work on another issue without this label instead. If there is not a corresponding pull request for this issue, it is up for grabs. For directions for getting set up, see our Getting Started Guide. If you are working on this issue and have questions, feel free to ask them here, #pypa-dev on Freenode, or the pypa-dev mailing list.

I've added the good first issues label to this issue.

I will work on this from Pycon2019 Mentor Sprints :)

I'm also at Pycon2019 working with theb10n707 on this issue.

I think this already exists? I think the problem is we just don’t have that data before Warehouse took over registration, so a lot of uses have a null date.
Sent from my iPhone

On May 4, 2019, at 4:07 PM, Ward Fenton<EMAIL_ADDRESS>wrote:
I'm also at Pycon2019 working with theb10n707 on this issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

The timestamp exists, but we don't surface it in the logged-in UI.

Looks like it is already available in the public profile. I will add it to the account settings page as well.

@theb10n707 how is this going? Need any help?

Fixed in #5786.


Improving inference time

Hi,
I came across this trick for improving inference time. https://github.com/opencv/opencv/pull/14827#issuecomment-568156546
While converting yolov4.cfg to tensort engine file, The cfg file that Used did not have nms-threshold=0 set in all yolo layers.
I do see some code in this repo for nms boxes etc.
Will i get any speedup in inference time of yolov4 if I add the values in cfg file? Or is this already taken care of while building trt engine?
Thanks

Thanks for raising the question.  But that does not apply to the code in this repo.
If you can read CUDA code, you'd see that I don't do NMS in the yolo_layer plugin.
https://github.com/jkjung-avt/tensorrt_demos/blob/8b81bbc3921da74b59731ab77a3fb2d33ceb0f13/plugins/yolo_layer.cu#L198-L249
Instead, I do NMS with python as shown below.  The NMS code is written in python and indeed could be slow.  You might improve FPS by optimizing this part (for example, replace it with C++ code).
https://github.com/jkjung-avt/tensorrt_demos/blob/8b81bbc3921da74b59731ab77a3fb2d33ceb0f13/utils/yolo_with_plugins.py#L139-L146

Thanks for raising the question.  But that does not apply to the code in this repo.
If you can read CUDA code, you'd see that I don't do NMS in the yolo_layer plugin.
https://github.com/jkjung-avt/tensorrt_demos/blob/8b81bbc3921da74b59731ab77a3fb2d33ceb0f13/plugins/yolo_layer.cu#L198-L249
Instead, I do NMS with python as shown below.  The NMS code is written in python and indeed could be slow.  You might improve FPS by optimizing this part (for example, replace it with C++ code).
https://github.com/jkjung-avt/tensorrt_demos/blob/8b81bbc3921da74b59731ab77a3fb2d33ceb0f13/utils/yolo_with_plugins.py#L139-L146

Thanks for the detailed explanation. I'll think about optimizing the NMS code part with C++ code.
I think it will be a fun and proud work.

Thanks for the detailed explanation. I'll think about optimizing the NMS code part with C++ code.
I think it will be a fun and proud work.


How to make a mutate request with multipart/form-data

Description
Hi, I'm trying to make a mutate request with multipart/form-data, but it's not working. I need to upload a file to this endpoint.
Request:

Response:

Thanks in advance for your help.

It's working.
I need just to put the value in a key:
mutate[0]operation -> mutate[0][operation]
mutate[0]attributes[user_id] -> mutate[0][attributes][user_id]


Choosing an architecture using tdlib

Leo I have the opportunity to build a project according to the following scheme
frontend(angular(0) || react(1) || vue(2)) + tdlib + backend(api on python(0) || api on php(1) || api on ruby(2))
Which of the tools is best used for maximum performance? (on all the stacks there is an opportunity to write cool). Particularly interested in frontend(which tools will be more convenient to support?). Computer power is enough.
It is also interesting to know the opinion of professionals about this bundle:
frontend(angular(0) || react(1) || vue(2))  + tdlib + p2p (either partially p2p. i think in this case it is necessary to expand tdlib)
Technology for the future development of the project.
I read a lot of best practices, but did not understand what kind of high-load project they want to create. Help please

And yet I like these madmen. Technologically cool.
Very grateful for the early reply

Crazy house.
Leo can you help determine the choice of the stack?

Use relatively independent means. I like the vue + ruby. But everyone has his own taste.


Cannot be used with TypeScript(ts-loader)

@twada @zoncoen Looks like webpack loaders cannot convert transpiled TS code due to the change of the extension name. How can you unassert such transpiled code? Or can you add an webpack unassert plugin?

I could work this loader. But got an error. Maybe the modern syntax is not supported.

Didn't work. This loader just got TS code, not transpiled JS code.

I tried the next configs with webpack 5 but didn't work.
        module: {
          rules: [
            {
              test: /\.ts$/,
              exclude: /node_modules/,
              use: [
                {
                  loader: 'ts-loader',
                  options: {
                    compilerOptions: {},
                    onlyCompileBundledFiles: true,
                  },
                },
                {
                  loader: 'webpack-unassert-loader',
                },
              ]
            },
          ],
        },

        module: {
          rules: [
            {
              test: /\.ts$/,
              exclude: /node_modules/,
              loader: 'ts-loader',
              options: {
                compilerOptions: {},
                onlyCompileBundledFiles: true,
              },
            },
            {
              test: /\.js$/,
              loader: 'webpack-unassert-loader',
            },
          ],
        },

I found that the correct order is REVERSED.
        module: {
          rules: [
            {
              test: /\.ts$/,
              exclude: /node_modules/,
              use: [
                {
                  loader: 'webpack-unassert-loader',
                },
                {
                  loader: 'ts-loader',
                  options: {
                    compilerOptions: {},
                    onlyCompileBundledFiles: true,
                  },
                },
              ]
            },
          ],
        },


Automated version bumping and pypi package building

This PR adds automated version bumping capabilities to the repo. Now whenever a PR is merged that isn't plugin-only, it will automatically trigger a version-bumping pipeline.
The current versioning system is v.major.minor.patch; merging a PR with no update label will cause the patch version to be updated, adding the minor update label will increment the minor version, and adding the major update label will increment the major version.
After the version is bumped, 2 different jobs run:

Release notes are generated that outline what has changed, and identify the contributor(s) of the changes.
The updated package is built and published to PyPI.

NOTE: Everything has been tested locally and on a fork, with the exception of the final publishing step to PyPI which will be tested on the merging of this PR.

Also LGTM, quick question: what is the default tag for a non plugin-only PR now? minor? As in any change that is not just a plugin will be a minor, unless otherwise specified to be major via the major tag?

All PRs without a minor or major tag will be just added as a patch!

LGTM, will this workflow need to be implemented in the other repos?

Yes, after this is PRed will implement something similar in core!


Added with the new Design

Fixes Issue
Closes #1780

Changes proposed

Screenshots

Note to reviewers

Summary by CodeRabbit

New Features

Integrated Firebase Crashlytics for enhanced crash reporting.

Bug Fixes

Corrected package naming inconsistencies from com.example.vigybagg to com.example.vigybag.

Style

Updated UI elements and color schemes, including drawable resources and font references.

Chores

Updated dependencies and Gradle configurations for improved build management.
Added Maven repository configuration for additional dependency management.

Kindly solve merged conflict


boards: frdm_mcxc444: Add i2c support

Enable i2c and configure it to read accelerometer sensor on the board. Test it using sample.sensor.accel_polling.

@NeilChen93 ping -- this too needs rebasing

Please add this to the release notes

Please add this to the release notes

As briefly discussed in a recent release meeting, this level of detail might not be desirable and @fabiobaltieri and I are currently working on a proposal to slightly revamp release notes, and we're thinking that "board changes" like this one here possibly don't belong to the release notes. I wouldn't delay this PR since release notes can always be added later

@NeilChen93 thanks for rebasing- there is unfortunately another merge conflict :/, it needs another rebase


Can't resolve node builtin modules

Bug report

What is the current behavior?
<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: Can't resolve 'url' in '/Users/keenwon/Test/webpack-test'
<w> while resolving 'url' in /Users/keenwon/Test/webpack-test as file
<w>  at resolve esm file url
<w>  at file dependencies /Users/keenwon/Test/webpack-test/webpack.config.mjs
<w>  at file /Users/keenwon/Test/webpack-test/webpack.config.mjs
<w>  at resolve commonjs /Users/keenwon/Test/webpack-test/webpack.config.mjs

If the current behavior is a bug, please provide the steps to reproduce.
works fine, no warnings

What is the expected behavior?

Other relevant information:
webpack version:  5.70.0
Node.js version: v14.19.0
Operating System: macOS 12.3
Additional tools:
demo
repo https://github.com/keenwon/webpack-test, switch to node-prefix branch

node: doesn't work either

Duplicate https://github.com/webpack/webpack/issues/14166

Please use https://github.com/webpack/webpack/issues/14166#issuecomment-923840210

your config should be
externals: { 'node:X': 'commonjs2 X' }

where X is used module (url, path etc)

I have committed to the node-prefix branch(repo)

ok, I understand what you are doing.. please use url and path modules in webpack.config.. (without node: prefix)
settings with externals works only for bundling code, not webpack config..

Yes, that's the weird part. the url also not works
(Please see the first picture of this issue)

I found a problem.. For now I can suggest to use commonjs config format..

solved in https://github.com/webpack/webpack/pull/15611