Add documentation note clarifying shallow wrapper prop functions

Fixes #397
As many others have stated, the documentation for .props & .prop(key) are fairly ambiguous on which props are being return for shallow wrappers. It's unclear that the props that are actually being returned are from the parent element of the component, since it's easy to mistakenly assume that props() would return the props you would recieve from a React component as with this.props
Changes proposed:

Add notes to both .prop(key) and .props() documentation in the ShallowWrapper API warning newcomers about what props are being returned & what props are not

Add references to instance() to show how to retrieve the instance props as with the usual React this.props pattern.

Update examples for both pages to demonstrate the key difference between the props returned & the instance props.

Added a couple comments - I'd like to remove the confusing term "parent element" since that describes something different.

Thanks @ljharb for the comments! Went ahead and added your suggestions in the latest commit ea7eb4e to correct the terminology used by referring to "root node" instead.

Revisiting this PR! Thoughts on this, @ljharb?

@kevinzwh if you'd mind rebasing onto latest master, so there's no merge commits, I think this should be good to go.

@ljharb sure - rebased onto latest master without merge commits ✅

LGTM


Re-enable --no-restore

Restoring is what caused mass test failures
And it seems it's not strictly required.

@Tratcher approved offline. Merging to fix tests.


[New Sample] - Bot-Configuration Node Js

Build Pipeline -

Build Pipeline -
https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/6049400439


Contributing with recipe 'barona-sso'

I created this by accident (it's all nonsense right now), I thought there would be another confirmation. Can be closed.


DiscordAPIError[50035]: "Invalid Form Body
content[BASE_TYPE_MAX_LENGTH]: Must be 2000 or fewer in length." in command "wiki"

Reported by floarmy<PHONE_NUMBER>17028147) with bot<PHONE_NUMBER>02710047
DiscordAPIError[50035]: Invalid Form Body
content[BASE_TYPE_MAX_LENGTH]: Must be 2000 or fewer in length.
at handleErrors (/home/container/node_modules/@discordjs/rest/dist/index.js:687:13)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async SequentialHandler.runRequest (/home/container/node_modules/@discordjs/rest/dist/index.js:1072:23)
at async SequentialHandler.queueRequest (/home/container/node_modules/@discordjs/rest/dist/index.js:913:14)
at async _REST.request (/home/container/node_modules/@discordjs/rest/dist/index.js:1218:22)
at async TextChannel.send (/home/container/node_modules/discord.js/src/structures/interfaces/TextBasedChannel.js:162:15)
at async Message.customReply (/home/container/Utils/prototypeRegisterer/message_customReply.js:23:19)

possibly fixed in b25597e


Ask to be part of NestJS awesome list

https://github.com/juliandavidmr/awesome-nestjs#components--libraries

And add appropriate badge to readme

Waiting for this PR to be processed: https://github.com/juliandavidmr/awesome-nestjs/pull/124

Need to add the badge in order to close this one.


Add a minor note about usage of MATCH with multiple columns

Popped up while reviewing Academy content where MATCH(name, description) is used without explicitly saying that those are indexed with FULLTEXT.
I played around locally and without FULLTEXT columns fall to exact match logic ie no fulltext logic/zero matches.
It sometimes works as "true fulltext" with best fields if at least some columns are FULLTEXT and matches are in those FT columns but listing all those combinations is too verbose.
The shortest would be just explicitly say "make all cols fulltext if want to be same as composite index"

Maybe worth adding that linked MATCH docs kinda shorty say that it depends on the index type but

it's not that explciit
most importantly, page being updates is called FULLTEXT and first way to search across multiple cols behaves as "true" fulltext - so think we need that small details to align both ways behavior.


Exception Handling Fix

Handle the case where the underlying library throws an exception so that RenewTransportAsync is called

@NicolasDorier this change exists in both pull requests but even if the other pull request is not accepted, this one is important for existing code.

Please, fix RenewTransportAsync instead to not throw. If we catch here we are suppressing any important information to the debugger.

There's nothing wrong with RenewTransportAsync. The problem is when the underlying layer throws and exception. If you want to keep the information, it needs to go in a log.

The other option is to deal with it at a higher level but the library is explicitly designed to handle failure by calling RenewTransportAsync

What should happen is the following: If you call and it throws, it should then try to renew the transport.
If this time it throws, you should not attempt to catch it.

That's exactly what I did. If the underlying layer throws an exception, it will catch it and return null. If null is returned, it will trigger RenewTransportAsync. That's how the original code works. The change makes the code work the original code works.

This is ugly, what about try/catch inside the Exchange method, and only for the first call to ExchangeCore? So we don't catch potentially important errors from underlying provider.

It's up to you.

@nicolasdorier I completely agree that exceptions should not be swallowed. I agree that if the library throws an exception, the highest level code should be given a choice what to do. For example, if the app sends a message and there is no response, the app should decide what to do.
Reconnect?
Tell the user there was an error?
Log it?
Reconnect and send the same message?
All these things are legitimate.  What this does is removes control from the highest level code and removes visibility of any underlying problems. It makes the assumption that the ledger is still connected when maybe it's not there...

So the no response was specific of hid.dll. What does HidLibrary.NET throw if it get disconnected and you try to read it?

It's not specific to hid.dll per se.  HidLibrary seems to return null in that case, but Hid.Net will throw an exception. It's because, if something goes wrong, the highest level code should decide what to do immediately, and the low level code shouldn't try to continue...
But, I can change Hid.Net so that there is no exception thrown. That way the catch block is not necessary for most situations. However, if some unexpected scenario comes up, an exception may be thrown for some other reason. The high level code should definitely do something about it.

@MelbourneDeveloper what type of exception? A catch all is really bad.

Good point. I think it's probably just an Exception. But, it should be a better exception. I will change Hid.Net to throw a more useful exception.
However, your code should be agnostic of my code. If you handle my exception, it will be tying your code to my code even more closely. You will need to do even more abstraction.

I can also just return null like HidLibrary...
But, I don't really like this approach.

A catch all is necessary because if someone is using a different library, there is no way to know what it will do... It might return null, it might throw and exception. Anything could happen.

Or just do like the Read where you catch HIDDeviceException if anything else is thrown, this is a bug and should be handled inside the IHidDevice implementation.

please just do like I did in the read, catching the HID exception.

@NicolasDorier, sorry I'm not going to get a chance to work on this for a while, but feel free to change what I've done.

will check today

ah ok actually just package update now


broken gradient propagation when do sampling

Hi,
Just a little confusion, for the codes below:
https://github.com/openai/spinningup/blob/2e0eff9bd019c317af908b72c056a33f14626602/spinup/algos/vpg/core.py#L71-L73
will the multinomial sampling operation  break the gradient back propagation? We have re-parametrization trick for continuous distribution, but we have done nothing here.
Besides, why don't we get the logp and logp_pi by indexing from the logp_all when given a and pi? Is it because index operation will also break gradient propagation?
Thanks

We don't need to backpropagate through the action-sampling procedure for VPG, so no backprop is broken by this. We just need to know the log probability of the action that got sampled, which this provides. :)


ci: Add new owners

Add new owners.

/hold
for discussion

Created issue about it https://github.com/openshift/oadp-operator/issues/1258
Please do not reopen this PR


For myself/use binfmt qemu bionic

The failed cases https://travis-ci.org/vicamo/docker_buildpack-deps/jobs/446002241 and https://travis-ci.org/vicamo/docker_buildpack-deps/jobs/446002249 indicate outdated vicamo/debian:jessie-<arch> docker images were used in the build. Created https://github.com/vicamo/docker-brew-debian/issues/38 for this.


x/pkgsite: Invalid content of an example that contains a block comment

What is the URL of the page with the issue?
https://pkg.go.dev/github.com/goyek/goyek/v2#example-package
What is your user agent?
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Screenshot

What did you do?
I have an example test like this:
https://github.com/goyek/goyek/blob/v2.0.0-rc.11/example_test.go
What did you expect to see?
Proper content taken from the example.
What did you see instead?
The example has a strange ending. The */ is duplicated together with some other symbols.

I can also see that extra
closing comment symbol at tail end.


Modify: EclipseAdoptium.Temurin.21.JDK version <IP_ADDRESS>

Microsoft Reviewers: Open in CodeFlow

Close with reason: Duplicate of #185467;


Support for File Sync

If only you supported File Sync/ InitializeFileSyncContext, and removed the Console.Write methods...

@makerofthings7 good call.  I'll try to get around to doing it, but I'm also happy to accept pull requests ;)

Source
Simple Demo
Detailed Demo


Could not fetch catalog entities on a all new deployment

Hello,
I'd like to run backstage in my local environment. To do this, I'm following the steps in the gettings-started guide.
Unfortunately, when the app is starting, I have an error :

While I see no errors in the logs of the backend :

N.B : I have the following error in my local environment but I get this error in multiple environments :

Kubernetes through helm charts deployment
Yarn deployment on a company VM behind a proxy
In my local environment in a WSL withtout any proxy.

The reason why I was talking about my local environment is because this is the environment where I made any modifications just the commands below
Steps to reproduce
npx @backstage/create-app ## Create local-backstage app
cd local-backstage && yarn dev

Environment

Ubuntu 20.04 in WSL 2 on Windows 10

Please let me know if you miss informations
N.B: Backstage seems really great and IMHO could help A LOT of teams growing up 👍

I see the backend starting up, and I see techdocs successfully reading entities (but getting zero entities out).
What's in your browser's console and network inspector? Could a corporate policy or browser plugins block you?

Hello @freben
I'm a bit confused ... I restarted my server and get the exact same error page as above.

When I open my brower console to show you the console, just a refresh of the page made it work.
So I restart my server, again the error page. F5 --> Still the error page. Once again F5 --> Got the correct page ....

Any idea what could lead to this state ?

So is it just a case of your backend starting up slower than your frontend? That would explain it, and we don't really have a check for that honestly.

We have hot reloading of most things - most of the time you don't have to restart as you develop. That may alleviate the problem somewhat.

@freben Ok it seems to be what you say.
The problem appears to multiple browsers (tested on Chrome and Firefox).
It appears that the when the logs lines prefixed by [1] appears my problem disappear. So the backend seems to be slower to start the backend and my impatience to test backstage seems to be the biggest problem here :)
Thanks !

Thanks for confirming.
I'm surprised that we haven't seen this happen in more instances. I have actually not seen reports about this before. I made a slimmer issue focused on a fix for this particular case, and I'll close this one for now to focus the discussion there going forward. We probably won't get around to working on this one in the very near term, but all suggestions and contributions in that ticket are welcome!

I am also facing the same issue. There is no issue while running the application on local machine. But the docker image build using the documentation https://backstage.io/docs/deployment/docker is giving same error.

@mustafazeya Hi were you able to resolve this?

@mustafazeya Hi were you able to resolve this?I am facing exact same issue.Thanks

Yes, it was configuration issue in app-config.yaml file.

@mustafazeya What issue was that?could you please clarify?Thanks

We weren't getting issue locally ( if you used npx to create initial version,you shouldn't get into any issue).
When we were deploying docker image with a custom url,we were getting this issue.
We had some cache problem in browser and we changed frontend and backend url to same and then everything worked perfectly fine.
I hope this helps!

estou enfrentado o mesmo problema porém na Vm, quando vou registrar um componente ou algo relacionado aparece o seguinte problema.

Em minha maquina virtual está da seguinte forma em meu , estou usando a fedora (Linux).
Alguém poderia me ajudar a solucionar ?
estou enfrentando ele a semanas..

Hello, maybe @LvffY had a cache problem, but I can't make it work either, I'm having the same error, with the same setup in a local machine, following the getting starter guide. None of the instructions in the getting started guide seem to work as intended, is that documentation up to date?

I got the same issue.
For me the error was that the CORS-url did not match the frontend URL

I am facing the same issue, how i can resolved this?

I installed on aws ec2 instance but when i installed on oracle box ubuntu vm and there is working properly.

I'm stuck in this too :(

@jethers  Did you manage to solve your issue ?
I am facing this issue as well and I am deploying via helm chart following the instructions here
https://github.com/backstage/charts

Hi,
I solved it doing this: https://github.com/backstage/backstage/issues/14874
Thanks
Em qua., 14 de dez. de 2022 às 16:44, Anderson Soares <
@.***> escreveu:

@jethers https://github.com/jethers Did you manage to solve your issue ?
I am facing this issue as well and I am deploying via helm chart following
the instructions here
https://github.com/backstage/charts
—
Reply to this email directly, view it on GitHub
https://github.com/backstage/backstage/issues/10323#issuecomment-1352054189,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHNYJGYCMZ7YSLWI552EKNLWNIPQXANCNFSM5RD4E5NA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@mustafazeya What issue was that?could you please clarify?Thanks

We weren't getting issue locally ( if you used npx to create initial version,you shouldn't get into any issue).
When we were deploying docker image with a custom url,we were getting this issue.
We had some cache problem in browser and we changed frontend and backend url to same and then everything worked perfectly fine.
I hope this helps!

Subject: Issue with Custom Domain on Backstage via Traefik Ingress - Assistance Required
Hello @mustafazeya
I am facing an issue with my app-config.yaml file after making custom domain changes. I have attached a screenshot of the error for your reference. Below is a summary of the problem:
Issue: I am using Traefik Ingress to route requests. When I use port forwarding on the pod, the application loads successfully on localhost:7007. However, I encounter issues when accessing the application via the custom host with a subpath using Traefik Ingress.
Could you please help me identify what I might be missing in my configuration?
Thank you for your assistance!

Error: Could not fetch catalog entities
Failed to load entity kinds
TypeError: NetworkError when attempting to fetch resource.

app:
title: Scaffolded Backstage App01
#baseUrl: http://localhost:3000
baseUrl: https://dummy-backstage.com:3000/backstage/

organization:
name: My Company

backend:

baseUrl: https://dummy-backstage.com:7007
listen:
  port: 7007

auth:
  dangerouslyDisableDefaultAuthPolicy: true
csp:
  connect-src: ["'self'", 'http:', 'https:']

cors:
  origin:
    - http://localhost:3000
    - https://dummy-backstage.com:3000

  methods: [GET, HEAD, PATCH, POST, PUT, DELETE]
  credentials: true
  Access-Control-Allow-Origin: '*'

Hello I am getting same error
[1] node:internal/modules/cjs/loader:453
[1]       throw err;
[1]       ^
[1]
[1] Error: Cannot find module 'P:\Scania-dev-portal\scania-dev-portal\node_modules<EMAIL_ADDRESS>Please verify that the package.json has a valid "main" entry
[1]     at tryPackage (node:internal/modules/cjs/loader:445:19)
[1]     at Module._findPath (node:internal/modules/cjs/loader:716:18)
[1]     at Module._resolveFilename (node:internal/modules/cjs/loader:1131:27)
[1]     at Module._load (node:internal/modules/cjs/loader:986:27)
[1]     at Module.require (node:internal/modules/cjs/loader:1233:19)
[1]     at require (node:internal/modules/helpers:179:18)
[1]     at Object. (P:\Scania-dev-portal\scania-dev-portal\node_modules@azure\identity\dist\index.js:13:23)
[1]     at Module._compile (node:internal/modules/cjs/loader:1358:14)
[1]     at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
[1]     at Object.newLoader [as .js] (P:\Scania-dev-portal\scania-dev-portal\node_modules\pirates\lib\index.js:121:7) {
[1]   code: 'MODULE_NOT_FOUND',
[1]   path: 'P:\Scania-dev-portal\scania-dev-portal\node_modules\<EMAIL_ADDRESS>[1]   requestPath: '@azure/abort-controller'
[1] }
[1]
[1] Node.js v20.14.0
[0] webpack compiled successfully


Collapse all button not working in C++ debugging

VSCode Version: 1.44.1
OS Version: Ubuntu 18

Steps to Reproduce:

Write a program in C++.
Debug it and try collapse all button.

Does this issue occur when all extensions are disabled?: Yes/No

Thanks for filling this issue. I can not reproduce this. Can you reproduce using Visual Studio Code Insiders https://code.visualstudio.com/insiders/

This

Can you reproduce using Visual Studio Code Insiders code.visualstudio.com/insiders

No, I couldn't reproduce it here either.
I will get back with more info about the issue and the extensions I use.

If you can not reproduce with vscode insdiers taht means it is fixed. Thus closing


Add CSS for home page

Chelle is our resident front end developer, but anyone can help tackle this. Please do it using classes which will automatically add correct CSS using the tailwind CLI we developed.
Navbar and header should be made pretty. Each food and wine should be in cards. Everything should be intuitive and well placed.


feat(kleros): add withdraw and transfer functions

Pull Request Test Coverage Report for Build 733

4 of 184 (2.17%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 16.642%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/contracts/implementations/PNK/MiniMePinakion.js
0
2
0.0%

src/contracts/implementations/arbitrator/Kleros.js
3
181
1.66%

Totals

Change from base Build 729:
-0.2%

Covered Lines:
193

Relevant Lines:
949

💛  - Coveralls


Add linting for SCSS

Add linting for SCSS. Will assist in enforcing BEM & other best coding practices.
Addresses #149

+1 from me.

+1

+1


Rewrite Go imports and directory structure for new custom import path.

This starts using the new custom import path added in #3691. After this is merged, everyone with a repo checked out will need to move their vitess directory:
mv $VTROOT/src/github.com/youtube $VTROOT/src/vitess.io

Also, anyone who vendors packages from our repo will need to use the new import path when they update beyond the point where this PR merged.
The first commit is entirely mechanical, using the command listed in the commit message. The rest of the commits were manual changes. I did not update instances that are actually links to GitHub's website, since the repo hasn't been moved to its new location yet. We'll need a separate PR to update those links after the repo move.
Note: After merging this, we'll need to push new Docker images. That step may have the potential to break anyone using the :latest tag instead of a pinned version tag or image hash.

LGTM

Looks like codeclimate caught a few things


[Suggestion] Allow disabling ore-doubling in your factory

This is related to mekanism also. As we want the Players to use the Mekanism Chain of ore processing, we do not want them to use any other means, we would Need to also Balance out. We already were able to remove every other method of ore-doubling, but it seems yours can't be disabled.

I highly recommend CraftTweaker (I fell like I may have recommended this on an earlier topic). Using that mod's scripts, you can edit NC's recipes in any way you like.

Yeah, if MalisisCore wasn't incompatible with it in the only Version it is incompatible with Sponge, i would try to do that ...

Ah, well that sucks... okay, I'll add a config option - should be simple enough.

Added a config option that allows you to disable the Manufactory and Melter ore processing recipes :)


Add support for CLI stacking

Fix #880

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

16 of 104 (15.38%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.6%) to 84.531%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mirar/processors/utils/image_loader.py
14
27
51.85%

mirar/pipelines/winter/run.py
0
75
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.6%

Covered Lines:
10869

Relevant Lines:
12858

💛  - Coveralls


Example Source Code

Is the source code for the following example shown in the README public somewhere cause that's exactly what I am looking for:
https://github.com/airbnb/react-native-maps#using-the-mapview-with-the-animated-api (the first gif)

This should help. https://github.com/react-community/react-native-maps/issues/209#issuecomment-350907665


Fix for GCC / Linux build

Fix GCC build issue on Linux
-Add MapServerEvents BitStream include in event_gen/main.cpp

This may relate to the register_MapEvents() to register_MapServerEvents() you (Nem) helped me with in MapEventRegistry.cpp.
Maybe a bad merge left some changes behind?

    if(group_name=="MapEvents")
    {
        tgt_stream << "#include \"GameData/chardata_serializers.h\"\n";
        tgt_stream << "#include \"GameData/clientoptions_serializers.h\"\n";
        tgt_stream << "#include \"GameData/gui_serializers.h\"\n";
    }

This piece of code was meant to provide the mapserver's generated file with some additional headers it might've needed ( since noone complained, we could probably remove this whole if ) :)

    if(group_name=="MapEvents")
    {
        tgt_stream << "#include \"GameData/chardata_serializers.h\"\n";
        tgt_stream << "#include \"GameData/clientoptions_serializers.h\"\n";
        tgt_stream << "#include \"GameData/gui_serializers.h\"\n";
    }

This piece of code was meant to provide the mapserver's generated file with some additional headers it might've needed ( since noone complained, we could probably remove this whole if ) :)

I will remove these and give it a test run tomorrow

@nemerle @broxen Removing that if block the build passes. Any specific testing I should be doing here or is a passing build good enough for now?

Nha, If the build passes we're good :)

Thanks, should be good to merge @broxen


Epic: Observability Improvements to aid reliability efforts

Exact done criteria TBD, but the common thread is fixes that will help our telemetry and errors to give us a clearer picture of how the FF is operating.  e.g. there will be some overlap with #6686.
Reincarnated as #8689 for the new year! Open issues moved there unless otherwise noted
Telemetry consumption
How do we and our partners use our telemetry, and improving the experience around specific use cases

[x] #6976  (Design Required)

Telemetry Instrumentation
Specific bugs around how logs or errors are instrumented

[x] #7802
[x] #7778
[x] #7984
[x] #7391
[x] #7598
[x] #6551

Perf Telemetry Instrumentation

[x] #7967
[x] #8071

Some moved to #8687
Error shape and propagation

[x] #7763
[x] #7800
[x] #8102
[x] #6980

Some moved to #8260
Information to ODSP

[x] #6483
[x] #8035
[x] #8182

Perf Info API
Moved to #8687

Planning to close this out after December, ensuring that all remaining items are tracked in other Epics tracking tighter scenarios.

This is still here going into first week of Jan, but as part of firming up Jan plan and beyond, I do still think this can be broken down into more specific Epics.
One in particular to split out for Jan is the "Error shape and propagation" section.  I have a write-up started and working through it with @vladsud, then will share more broadly and move onto implementing.

Remaining open items were moved to other epics, e.g. #8689, #8260, and #8687


Proof / Screenshots of application pages

Add some images showing the flow of the application and actually show that it works.

GIF added!


DNS Resolve fails Spring Boot macOS

Bug Description
User complains that their Spring Boot service fails to resolve DNS.
Steps to Reproduce
Use this repository, have a Redis server in the cluster with service name redis-man
https://github.com/aviramha/issue-1458
Backtrace
No response
Relevant Logs
2023-05-25 04:04:03.602 ERROR [progression-svc,,] 89301 --- [           main] i.n.r.d.DnsServerAddressStreamProviders  : Unable to load io.netty.resolver.dns.macos.MacOSDnsServerAddressStreamProvider, fallback to system defaults. This may result in incorrect DNS resolutions on MacOS. Check whether you have a dependency on 'io.netty:netty-resolver-dns-native-macos'. Use DEBUG level to see the full stack: java.lang.UnsatisfiedLinkError: failed to load the required native library

Caused by: io.lettuce.core.RedisConnectionException: Unable to connect to keydb.island-milestone-infra.svc/<unresolved>:6379
        at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:78)
        at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:56)
        at io.lettuce.core.AbstractRedisClient.getConnection(AbstractRedisClient.java:330)
        at io.lettuce.core.RedisClient.connect(RedisClient.java:216)
        at org.springframework.data.redis.connection.lettuce.StandaloneConnectionProvider.lambda$getConnection$1(StandaloneConnectionProvider.java:115)
        at java.base/java.util.Optional.orElseGet(Optional.java:364)
        at org.springframework.data.redis.connection.lettuce.StandaloneConnectionProvider.getConnection(StandaloneConnectionProvider.java:115)
        at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory$ExceptionTranslatingConnectionProvider.getConnection(LettuceConnectionFactory.java:1595)
        ... 86 more
Caused by: io.netty.resolver.dns.DnsResolveContext$SearchDomainUnknownHostException: Failed to resolve 'keydb.island-milestone-infra.svc' and search domain query for configured domains failed as well: [router]

### Your operating system and version

macOS

### Local process

Spring Boot

### Local process version

_No response_

### Additional Info

_No response_

This appears to be related to Netty's DNS resolver which uses additional native libraries on macOS: https://github.com/netty/netty/tree/4.1/resolver-dns-native-macos
This issue doesn't appear when Netty's DNS resolvers are excluded from the application, but that's a temporary workaround at best.

Seems like netty resolves itself and we don't intercept the socket.

Okay, debugged it further - it seems that it requires sendto which means we need to support non-connected UDP sockets
https://github.com/metalbear-co/mirrord/issues/647


Update testdata set to latest version

As product irs
I want to use the latest testdata set 1.7.0 with bugfixes
so that I am compatible with latest bugfixes
Hints / Details

[x] PartInstance: https://confluence.catena-x.net/download/attachments/98566737/CX_Testdata_v1.7.0_PartInstance 1.zip?version=1&modificationDate=1712212375623&api=v2
[x] PartType: https://confluence.catena-x.net/download/attachments/98566737/CX_Testdata_v.1.7.0_PartType.json.zip?version=1&modificationDate=1712212575007&api=v2

Acceptance Criteria

[x] IRS is updated to newest testdata set for PartInstance and PartType https://confluence.catena-x.net/display/PL/Test+Data+Info+page
[x] Insomnia collection is updated with all contained aspects

Out of Scope

...

@jzbmw  This works as expected.


DecodeExtrinsic error on runtime 26

Recovering from panic in DecodeExtrinsic error is: Not find Extrinsic Lookup 0a00, please check metadata info

please check weight type, maybe set u64 can fix it

Weight is  "Weight": "u64",

Weight is  "Weight": "u64",, I found the decode the block 2436698 will have the error.

@crossle  oh, I know why, you can notice that this block is a runtime upgrade, it needs to use the previous version of metadata

@crossle oh, I know why, you can notice that this block is a runtime upgrade, it needs to use the previous version of metadata

YES, it's the runtime upgrade. Thanks, I just ignore the error.


Callbacks for animation started and animation ended events

Hello,
  First of all it's a great library. Will it have integrated callback functions for animation events ?

Thanks.

Agreed. I'm waiting for this feature so far!

Hey, yes @glodynator :) Please follow #17 This is already implemented. I'm finishing new Readme and will be released soon.


Added dask and netCDF4 to requirements.txt

Overview
Dask and netCDF4 are required to run yodapy.
Related to https://github.com/oceanhackweek/ohw18_yoda_im/issues/27

Pull Request Test Coverage Report for Build 176

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

Totals

Change from base Build 175:
0.0%

Covered Lines:
342

Relevant Lines:
761

💛  - Coveralls

Interesting that xarray doesn't pull these two.. hmm.. Thanks!


when set Failover PromotionRules, auto failover  action  not same as expected

Hi
I ask a question for a  help.
My test topology  as following

I set  ofa7 node  as candidate master ,and shut down 03f0,
after failover , new topology  as following

I thought if auto failover success,  we should remove 03f0 node from  current cluster.
How should i do  to  force  removing old master from current  cluster.

can u paste your orchestrator.conf.json here?

:wave: you can either set the config option UnseenInstanceForgetHours to a short time and it will disappear automatically or you could use the client to forget the host. There is also an option in the web interface. If you want the host forgotten automatically you could set one of the Post*FailoverProcesses to run the client to forget the host.

@tomkrouper   thanks.
when set Failover PromotionRules, i saw failover log from web ,

RecoverDeadMaster: applying RESET SLAVE ALL on promoted master: success=false

and login mysql  for executing reset slave all,
returns:
ERROR 3081 (HY000): This operation cannot be performed with running replication threads; run STOP SLAVE FOR CHANNEL '' first
I   stop slave  first and execute  reset slave all , several seconds later, the topology of current culster is correct.
But,  how to let orchestrator do this automaticly.
@shlomi-noach

@ Voltron-Patcher As per https://github.com/github/orchestrator/blob/master/docs/configuration-recovery.md#promotion-actions, set ApplyMySQLPromotionAfterMasterFailover: true

@ Voltron-Patcher As per https://github.com/github/orchestrator/blob/master/docs/configuration-recovery.md#promotion-actions, set ApplyMySQLPromotionAfterMasterFailover: true

Hi
this is true default, which in sample config file.

@Voltron-Patcher sorry, I missed the comment about the error log. orchestrator does stop slave before running reset slave. Is there anything in your own infrastructure (vitess?) that automatically attempts to issue start slave?

@Voltron-Patcher sorry, I missed the comment about the error log. orchestrator does stop slave before running reset slave. Is there anything in your own infrastructure (vitess?) that automatically attempts to issue start slave?
no, this env is for test purpose.
and  masterRecoveryType is  MasterRecoveryPseudoGTID.
if  mysql enabled GTID,  it works as expected.

I have no immediate idea.

I have no immediate idea.

Waiting for your repy

If you can meanwhile reproduce this and look into the logs (run the orchestrator service with --debug), perhaps we can see something there.

i'll do it


🐛 Endless Poll Creation Loop Displays Multiple Results

Area
Proposal Pillar
Domain
dev-sanchogov.tools
Which wallet were you using?
No response
Context
While attempting to view the poll results for a proposal, I noticed that after closing a poll, the "Add Poll" button becomes visible. This allows a new poll to be added, which generates another set of results. Repeating this process results in an endless loop where multiple poll results are displayed.
Steps to reproduce

Connect your wallet.
Create a new proposal or navigate to an existing one.
Add a poll.
Close the poll.
Notice that the "Add Poll" button reappears and allows a new poll to be added.
Repeat the process and observe that each cycle generates a new poll result.

Actual behavior
The system allows multiple poll results to be generated as polls can be repeatedly added and closed.
https://dev-sanchonet.govtool.byron.network/proposal_discussion/2029

Expected behavior
The "Add Poll" action should be restricted by the API once the poll has been closed, preventing further additions. Alternatively, only the latest poll result should be visible, and multiple results should not be displayed.

@nebojsajsimic any update on this ? I am still able to reproduce this issue
https://dev-sanchonet.govtool.byron.network/proposal_discussion/2176
CC: @bosko-m

Can you test now @kneerose ?

@bosko-m , I am still able to reproduce this
https://dev-sanchonet.govtool.byron.network/proposal_discussion/2433

I'll check this again, fix on alternative way so we will display only last created poll.

@nebojsact I am still able to reproduce this issue:

The "Add Poll" button is visible even after the poll has been closed.
Additionally, the API allows the creation of a new poll, regardless of whether the previous poll is closed or not.

Dev Environment
https://dev-sanchonet.govtool.byron.network/proposal_discussion/2521

Preview Environment
https://preview.gov.tools/proposal_discussion/683

CC: @bosko-m

@kneexpected, so you can open and close polls, this is expected behavior,
change was that only the last closed pool is visible instead of a bunch of
opened and closed.
So yes, you can open new when you close the old one.
On Mon, Dec 9, 2024 at 5:28 AM Niraj Duwal @.***> wrote:

@nebojsact https://github.com/nebojsact I am still able to reproduce
this issue:

The "Add Poll" button is visible even after the poll has been closed.
Additionally, the API allows the creation of a new poll, regardless
of whether the previous poll is closed or not.

Dev Environment
https://dev-sanchonet.govtool.byron.network/proposal_discussion/2521
image.png (view on web)
https://github.com/user-attachments/assets/dc2611f6-7779-4e86-bf13-65acf8971c3c
Preview Environment
https://preview.gov.tools/proposal_discussion/683
image.png (view on web)
https://github.com/user-attachments/assets/3c42e7aa-f1aa-4e35-8fd2-42e67c170528
CC: @bosko-m https://github.com/bosko-m
—
Reply to this email directly, view it on GitHub
https://github.com/IntersectMBO/govtool/issues/2357#issuecomment-2526863148,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKSYINBVPZKO5T3FNVKWBC32EUL7JAVCNFSM6AAAAABRNA25S2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRWHA3DGMJUHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@nebojsact , does this mean a user can vote on multiple polls for the same proposal? For instance, if a user has already voted on one poll and the poll owner closes it, then opens a new poll, can the same user vote again on the new poll for the same proposal?
Additionally, based on your comments, if the poll owner closes a poll with more responses and subsequently opens and closes a new poll, does this mean the results of the old poll will be discarded?

The API currently allows the creation of a new poll even if the previous poll remains open. As a result, using the API to create multiple polls causes the "Close" button to appear multiple times for each poll created. The API should enforce a restriction to block the creation of a new poll for the same proposal if an existing poll is already open and not closed.

https://www.loom.com/share/19f879a3df854c879c1d9ff7277fb5de?sid=de71a437-ade5-4050-987e-8d3605cd223c

@kneerose as the logic for the poll was in place for opening and closing, I suppose that was made by request and description of functionality, yes if the user closes the poll, edit proposal and open new poll it is normal that old will be discarded. So @bosko-m can you help us with this logic?
@kneerose also please open a new bug for new request and close this if everything from the initial request was resolved. Thanks!

@kneerose @nebojsact
Here is the expected behavior:

There can only be one poll active at the time (if thats not the case, please create the new ticket as it goes outside of the scope of this bug).
The last closed poll should be shown
Once the proposal has been submitted on chain, no new polls can be created and commenting should be off too.
Let me know if you have any questions.

@nebojsact  ,
I have created a separate ticket for the backend poll creation issue #2507.
Current behaviour of proposal poll on frontend

When a proposal owner adds, edits, and closes a poll, and then adds a new poll, the UI renders as

If the owner closes the new poll, the poll results are updated to reflect the new poll's results

NOTE: If this is the expected and intended behavior for the UI, this ticket can be considered closable.
CC: @bosko-m

@bosko-m , after closing the new poll, the results are updated, and only the updated poll results are displayed.

All good, understood.
Thank you @kneerose


async/await upgrade

Not working yet. Just having this PR visible to illustrate progress.
Currently blocked on reqwest Response::text and Response::error_for_status not playing nice together in 0.10. I need to call both, and the text is used along with error_for_status to make a nicer error. Dropping error_for_status usage.

Next problem. Log is a trait that requires async-trait, changing to this is relatively straight forward:
diff --git Cargo.toml Cargo.toml
index 0b525381..1c68c70d 100644
--- Cargo.toml
+++ Cargo.toml
@@ -28,6 +28,7 @@ url = "2.1.0"
 log = "0.4.8"
 time = "0.1.42"
 either = "1.5.3"
+async-trait = "0.1.17"

 [features]
 default = []
diff --git src/api/typed.rs src/api/typed.rs
index a2d92de7..222c513a 100644
--- src/api/typed.rs
+++ src/api/typed.rs
@@ -3,6 +3,7 @@
 use either::{Either};
 use serde::de::DeserializeOwned;
 use std::marker::PhantomData;
+use async_trait::async_trait;

 use crate::api::{
     RawApi,
@@ -42,13 +43,15 @@ pub struct Api<K> {
     pub(in crate::api) phantom: PhantomData<K>,
 }

+#[async_trait]
 pub trait LogOperation {
-    fn log_operation(&self, name: &str, lp: &LogParams) -> Result<String>;
+    async fn log_operation(&self, name: &str, lp: &LogParams) -> Result<String>;
 }

+#[async_trait]
 pub trait Log: LogOperation {
-    fn log(&self, name: &str, lp: &LogParams) -> Result<String> {
-        Ok(self.log_operation(name, lp)?)
+    async fn log(&self, name: &str, lp: &LogParams) -> Result<String> {
+        self.log_operation(name, lp).await
     }
 }

@@ -118,15 +121,15 @@ impl<K> Api<K> where
     }
 }

-// TODO: async trait functions?
-/*impl<K> LogOperation for Api<K> where
+#[async_trait]
+impl<K> LogOperation for Api<K> where
     K: Clone + DeserializeOwned + KubeObject
 {
-    fn log_operation(&self, name: &str, lp: &LogParams) -> Result<String> {
+    async fn log_operation(&self, name: &str, lp: &LogParams) -> Result<String> {
         let req = self.api.log(name, lp)?;
-        self.client.request_text(req)
+        Ok(self.client.request_text(req).await?)
     }
-}*/
+}

 /// Scale spec from api::autoscaling::v1
 #[derive(Deserialize, Serialize, Clone, Debug)]

However, this now puts a limitation on K needing tom implement both Send and Sync... This is overkill.

Alright, some examples work! Had to rewrite the Log trait from #50 (which resulted in the same Api, but without having to import an extra trait).

All examples work on this branch now. Now we just need a way to swap out the awkward sleep calls.

Alright, internals are OK. Still a few awkward sleeps in closures in examples (async closures is not a thing yet), but whatever.
Now to think about stream interfaces...

[circleci/rust](https://hub.docker.com/r/circleci/rust/tags).await?

Works on stable. Merging anyway.


Snapdragon: Start logger before estimator outputs data

Especially for a replay we need to make sure that we are not missing any data from the sensors. Right now the logger is the last app to start.

@tumbili this means we are logging all the time?

Yes, for replay we are not waiting to be armed.

@julianoes Also we need to make sure that the dsp apps are not running before the logger runs on the posix side.

I can add a wait_on_topic command to block until a topic is published. This would require the logger to publish an "logger_running" topic.


Add tx_failure_reason to the Error from waitForTx

Currently, we can't display to users any details about failure transactions. We only have a status code. But get_transaction_status also sends us the tx_failure_reason, and I think we should be able to read this reason

thanks for bringing it up!
I think it's mostly just typing the response in typescript. PR's very welcome!


Broken developer doc links

Please select the area your bug applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[ ] Workspace.  VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup.  Dendron's Lookup Command
[ ] Views.  Dendron Preview, Tree View, Side Panels in the UI
[ ] Schema.  Dendron Schemas
[ ] Pod.  Data import from / export to Dendron
[ ] Publish.  External Site Publish
[ ] Markdown.  Markdown features, such as syntax support and features
[X] Documentation

Describe the bug
Both developer and user guide links are broken here.
To Reproduce

Go to this link: https://github.com/dendronhq/dendron/blob/master/docs/README.md
Click on either User Guide or Developer Guide.
Witness the glory of the broken link.

Expected behavior
The respective documentation to show.

Thanks for letting us know. We'll fix this right away :)

@kevinslin I see a few changes to this file recently from you but can't figure out what you were trying to do here. looks like you were trying to link it to root.md on both vaults but both those files don't contain useful information for the repo.

Could please fix the dev doc link as soon as possible?
Currently the cost is a bit high for me to understand Dendron ...

fixed!


Add new section where you can add contact information

Motivation
We want to add a new section where you can add contact information.
Proposed Solution

Add a section where contact information can be added
Link from page form, event form and poi form to the contact information

Alternatives

Additional Context
This needs further specification
Design Requirements

What kind of further information is needed? Anything we can help with?
This issue would probably solve the translations' problem we have with automatic translations translating addresses as well.

@osmers could you please provide some user stories? :-)

As a CMS user I want to be able to centrally manage contact information in order to minimize work when information changes
As a CMS user I want adresses to be non-translateable without having to mark each address as "do not translate" in order to have consistency and minimal work
As a CMS user I want the same layout incl. icons for all addresses in order not to worry about consistency
As a user I want all addresses to be in the same format so that I can always find all necessary information in the same space
@karthik-integreat @nassabay @dkehne can you see if you have any other user stories for this?

I would add:

as a CMS user i want to be able to place the contact information flexibel in the content area
as a CMS user it should be intuitive to me how i can add/remove the contact information section
as a CMS user i want to be able to control the design (e.g. sorting of contact information [centrally configured for the region])
as an APP user i just want to see the contact information in the text that are maintained with content / filled

Are there any questions remaining - should we ask Toni for UI/UX input?
With more and more languages a central contact management would make changing information easier (yes, they can simply translate a page again, but I get that for just one phone number or name it's a bit sad to use translation budget, plus the central management eliminates mistakes and makes the layout consistent) - so I would like to move the issue to a milestone within 2024. Maybe @svenseeberg @timobrembeck @JoeyStk can write any other questions they have here.

I don't know why this issue is blocked. To me it looks like it could be worked on. Maybe we can discuss in the next grooming if we can maybe split this is up, but for now AFAIK it's good to go?

@JoeyStk yes, let's discuss this in the next grooming, plus maybe this issue: https://github.com/digitalfabrik/integreat-cms/issues/1878 since we can maybe combine them in some way?

Is this still blocked and are there still questions? Let's discuss in issue grooming today.

For next issue grooming: Provide a to list with everything that needs to be done and discuss how this could be separated into multiple issues

Blocked by the corresponding design ticket

Closed as succeeded by #2955

I have a little remark for the input of the website in the "Kontaktdaten verwalten" section. Atm it is mandatory that the user writes "http://www...." otherwise an error message occurs. Can we change it, so that it is sufficient to write the website without "http://". Thanks!

I have a little remark for the input of the website in the "Kontaktdaten verwalten" section. Atm it is mandatory that the user writes "http://www...." otherwise an error message occurs. Can we change it, so that it is sufficient to write the website without "http://". Thanks! @MizukiTemma

That's a nice idea 😸
We can probably show "https://www." like "https://integreat.app/" here and automatically prefix it at saving.


fix signedAngle function & create new skeleton function

Closes #757

[x] Running yarn lint does not trigger any linter errors
[x] The test of the method you have fixed is passing
[x] You have written a new skeleton method for someone else to work on!
[x] You have written tests to accompany your skeleton method
[x] I Also Wrote some edge tests, that have been fixed.

@ktilcu can you please review this & close the issue


BUILD FAIL

CMake Error at src/CMakeLists.txt:92 (install):
install TARGETS given no LIBRARY DESTINATION for shared library target
"workflow-shared".
-- Configuring incomplete, errors occurred!
See also "/home/wjp/workflow/build.cmake/CMakeFiles/CMakeOutput.log".

我们昨天正在改Cmake文件，这个报错看起来应该在install()里加一项LIBRARY就可以了。我们今天会继续修复一下，如果你着急使用可以先使用前天的代码或者release 0.9.9

感谢反馈～请问你是什么系统下的呢？
我们昨天正在改Cmake文件，这个报错看起来应该在install()里加一项LIBRARY就可以了。我们今天会继续修复一下，如果你着急使用可以先使用前天的代码或者release 0.9.9

感谢反馈～请问你是什么系统下的呢？ 我们昨天正在改Cmake文件，这个报错看起来应该在install()里加一项LIBRARY就可以了。我们今天会继续修复一下，如果你着急使用可以先使用前天的代码或者release 0.9.9

明白，谢谢大佬

https://github.com/sogou/workflow/pull/733 麻烦有空了帮忙验证一下这个PR是否可以解决你的问题，或者是否还有其他的问题～感谢小伙伴～


Non-standard colors in theme data throw an illusive exception

 Setting primary color to something non-standard like below:

 theme: ThemeData(
          primaryColor: Colors.black54,
          accentColor: Colors.greenAccent,
          textTheme: TextTheme(bodyText2: TextStyle(color: Colors.white70))
      ),

 causes this:
The following assertion was thrown building WidgetsApp-[GlobalObjectKey _MaterialAppState#c3710](dirty, state: _WidgetsAppState#77ca7):
'package:flutter/src/widgets/title.dart': Failed assertion: line 24 pos 15: 'color != null && color.alpha == 0xFF': is not true.

accentColor is of type Color object
Colors.greenAccent return MaterialAccentColor object not Color
Its a type mismatch error. Change Colors.greenAccent to just Colors.green or use different shade Colors.green[500]

@ShaseOfBase
Check above comment and possible solution to see if it works for you.

Perfect, sorted, thanks guys.


Directory mappings only contain native lib directories

I am trying to write a Wix installer for a single project WPF app. The problem appears to be the inclusion of LibGit2Sharp, which pulls in LibGit2Sharp.NativeBinaries. Wax seems to be confused by the presence of the .\lib directories under .\bin\debug.
This can easily be reproduced. Create an empty .Net Framework WPF application. Build it. Add a Wix v3 setup project. Open up the Wix Setup Editor. All looks normal. Add the LibGit2Sharp NuGet package to the WPF project's references. Build it. Go back to the Wix Setup Editor and refresh.  The (5) File mappings table is all red, contains all the files in the .\lib directories which are labeled Unmapped, does not scroll, and nothing can be selected.

You must first fix (4) by adding the directory before you can add files (5)

I am new to Wix, and could not figure out how to add the (4) Directory mappings. I have tried adding new elements to the  element. Unfortunately, there do not seem to be any examples on the web [6 results] that have more than the single element without a key.
  <DirectoryMappings>
    <Item Key="" Value="INSTALLFOLDER" />
  </DirectoryMappings>

My attempts using hardcoded values, or using Wix variables such as $(var.MyWpfProject.ProjectDir) do not add the directory as you are suggesting.
  <DirectoryMappings>
    <Item Key="" Value="INSTALLFOLDER" />
    <Item Key="debug" Value="d:\Projects\MyWpfProject\MyWpfProject\bin\debug" />
  </DirectoryMappings>

Could you please provide a more explicit example of how to add another directory, or perhaps a link on How to add the directory? Thank you.

Just click the + symbol

Just click the + symbol

And don't touch the .wax file


Add missing --set to docker app upgrade example

Proposed changes
I just fixed the example of  docker app upgrade command.

Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit d2161ecc78fa445aa578c74fae898459d676000f
https://deploy-preview-9195--docsdocker.netlify.com


Create Code of Conduct. md

Hi,
I found that this project repository is not having a code of conduct file in this repository, kindly assign me this issue and I would like to contribute a well-formatted code of conduct file as you know code of conduct is a necessary file which the contributors need to follow so that everyone follows a decorum.

I would love to work on this issue as a part of DWOC. Kindly assign me

Hey @muthuannamalai12 thanks for taking time to open up this issue. But we already have the code of conduct fille here, so closing this issue

Ok Thank you.


"bare metal" pull request #854 might be preventing Vale from running

Closed pull request  #854 seems to be causing an issue with running the Vale prose linter. Here is an example linting from stdin:
$ lbv "bare metal is the way to go"
E201 Invalid value [/vale_app/styles/RedHat/TermsErrors.yml:22:4]:

  21    "(?<!self-)hosted engine|hosted-engine": self-hosted engine
  22*   "bare metal( clusters?| compute| configuration| controls?| environments?| equipment| events?| hardware| hosts?| infrastructure| installations?| installers?| machines?| media| nodes?| provisioning| servers?| workers?)": bare-metal $1
  23    "bare-metal(?! clusters?| compute| configuration| controls?| environments?| equipment| events?| hardware| hosts?| infrastructure| installations?| installers?| machines?| media| nodes?| provisioning| servers?| workers?)": bare metal
  24    "[bB]asic [aA]uth": Basic HTTP authentication|Basic authentication

capture group not supported; use '(?:' instead of '('

Execution stopped with code 1.

Here, lbv is a local alias for running Vale from a Docker container. I rebuilt this container today after the pull request was committed and got this error. If I take the container's "sync" step back to a locally cached version from before the pull request, the error goes away. The sync step I believe "grabs" packaged style rules. I don't know if that is significant here or not.
Hope this report is helpful and that I have provided enough details. Happy to do more if needed.

Can you give me more information? This error is because you are using an older version of vale in your container.
$ podman run quay.io/rhdevdocs/devspaces-documentation vale -v
vale version 3.7.0

You need Vale 3.7+

https://github.com/errata-ai/vale/releases/tag/v3.7.0

Ah! Indeed, that is the problem for me. My container was based on an older Vale version (jdkato/vale:v2.x.x). Thank you for the reply and apologies for the noise.


Warning about the deprecation of primitives V1

It took me some time to find a warning that primitivesV1 is going to be removed. Making it more visible.
https://github.com/Qiskit/qiskit-ibm-runtime/pull/1798 is the api equivalent of this PR.

August 15 is, indeed, not earlier than July 15 :) The deprecation policy uses the formula "not earlier than X" to allow X+n to happen. However, if @jyu00 can confirm that the removal will be on August 15, I think the user will appreciate that extra precision. Once confirmed, I happy to replace   "will be removed no earlier than 15 July 2024" by "will be removed on 15 August 2024".

However, if @jyu00 can confirm that the removal will be on August 15,

Yeah the removal is planned for August 15.

Change done in 7842ee9d96db7fddc7a4680aca83382199eddb0f with the confirmed removal date. Thanks!


Enumerate device fonts

Font.enumerateFonts(true) should enumerate device fonts (like in C:\Windows\Fonts). It outputs only TTF fonts.
Windows, neko and Hashlink work! I have not tested Mac and Linux yet.
There is room for improvement for the future, for e.g: cache all the fonts for next time enumerateFonts(true) is called.

It should be easy to review, test and merge this. How can I help?
I'm using this in my editor to make all fonts available to user like in Animate, Photoshop, etc.
@Dimensionscape @joshtynjala

Looks good to me.


Code review

[ ] Please move this line below all const definitions.

https://github.com/valantic/webpack-dependency-hint/blob/93089bcc7f7459aea88dc2014c96c0e88a08aff8/index.js#L5

[ ] You need to define this packages as dependencies. Else they will not be installed by default.

https://github.com/valantic/webpack-dependency-hint/blob/93089bcc7f7459aea88dc2014c96c0e88a08aff8/package.json#L6

[ ] Did you try to show this, when the webpack process starts? I think it would show up more prominent.

https://github.com/valantic/webpack-dependency-hint/blob/93089bcc7f7459aea88dc2014c96c0e88a08aff8/index.js#L30

[ ] Please check if your package is also compatible with webpack 5.

Please also test it with webpack 5 in vue-template :-)

@janwidmer @patric-eberle Works well with webpack 5


Test coder modules

Test each of the submitted modules individually and ensure screenshots and examples have been added

[x] code-server @kylecarbs I assume you have tested code-server

[x] test
[x] screenshots
[x] examples

[x] vscode-server

[x] test
[x] screenshots
[x] examples

[ ] JupyterLab

[ ] test
[x] screenshots
[x] examples

[ ] KasmVNC

[ ] test
[x] screenshots
[x] examples

[x] GCP regions

[x] test
[x] screenshots
[x] examples

[x] AWS regions

[x] test
[x] screenshots
[x] examples

[ ] Azure regions

[ ] test
[ ] screenshots
[ ] examples

[ ] Fly.io regions

[ ] test
[ ] screenshots
[ ] examples

[x] VS Code Desktop

[x] test
[x] screenshots
[x] examples

[x] JetBrains Gateway

[x] test
[x] screenshots
[x] examples

[ ] JFrog

[ ] test
[ ] screenshots
[ ] examples

[x] Personalize

[x] test
[x] screenshots
[x] examples

[x] Dotfiles

[x] test
[x] screenshots
[x] examples

[x] git clone

[x] test
[x] screenshots
[x] examples

[ ] git config

[ ] test
[ ] screenshots
[ ] examples

cc: @bpmct, @stirby, @kylecarbs, please add/update the list if you contribute

@stirby please update the status of the modules you are working on.


HttpRouter with overlapping routes fails silently

What version of Effect is running?
3.11.3
What steps can reproduce the bug?
https://effect.website/play/#103e73793389
import { HttpApp, HttpMiddleware, HttpRouter, HttpServerResponse } from "@effect/platform"
import { Effect } from "effect"

const RouteA = HttpRouter.all(
  "*",
  Effect.gen(function*() {
    console.log("RouteA")
    return HttpServerResponse.html("RouteA")
  })
)

const RouteB = HttpRouter.all(
  "*",
  Effect.gen(function*() {
    console.log("RouteB")
    return HttpServerResponse.html("RouteB")
  })
)

export const Router = HttpRouter.empty.pipe(
  RouteA,
  RouteB,
  HttpRouter.use(HttpMiddleware.logger)
)

const handler = HttpApp.toWebHandler(Router)

handler(new Request("http://localhost:8080/"))
  .then(console.log)

What is the expected behavior?
The response is generated by first matched handler. If first handler returns 404 or some kind of an empty response, next match is executed until succesful response is returned.
What do you see instead?
Response is empty has status=500. No handler function is called as there are no logs.
Additional information
There was no error printed or thrown (I tried Effect.tapError)

One option is to allow handlers fail with Effect.fail(new RouteNotFound({ request: req })). Router.empty already have this error tag.

Same behavior can be observed with two wildcard routes using distinct methods:
export const router = HttpRouter.empty.pipe(
  HttpRouter.head("*", ViteDevHttpRouteHandler),
  HttpRouter.get("*", ViteDevHttpRouteHandler),
)

We can have it not throw when you have duplicate routes. Currently it will error like this:
import { HttpMiddleware, HttpRouter, HttpServer, HttpServerResponse } from "@effect/platform"
import { NodeHttpServer, NodeRuntime } from "@effect/platform-node"
import { Layer } from "effect"
import { createServer } from "http"

const router = HttpRouter.empty.pipe(
  HttpRouter.all("*", HttpServerResponse.text("first")),
  HttpRouter.all("*", HttpServerResponse.text("second"))
)

HttpServer.serve(router, HttpMiddleware.logger).pipe(
  Layer.provide(NodeHttpServer.layer(createServer, { port: 3000 })),
  Layer.launch,
  NodeRuntime.runMain
)

If you want to create a middleware that rescues from a route not found:
import { HttpMiddleware, HttpRouter, HttpServer, HttpServerError, HttpServerResponse } from "@effect/platform"
import { NodeHttpServer, NodeRuntime } from "@effect/platform-node"
import { Effect, Layer } from "effect"
import { createServer } from "http"

const isRouteNotFound = (u: unknown): u is HttpServerError.RouteNotFound =>
  HttpServerError.isServerError(u) && u._tag === "RouteNotFound"

const someMiddleware = HttpMiddleware.make((httpApp) =>
  httpApp.pipe(
    Effect.catchIf(isRouteNotFound, () => HttpServerResponse.text("fallback"))
  )
)

const router = HttpRouter.empty.pipe(
  someMiddleware
)

HttpServer.serve(router, HttpMiddleware.logger).pipe(
  Layer.provide(NodeHttpServer.layer(createServer, { port: 3000 })),
  Layer.launch,
  NodeRuntime.runMain
)

I ended up with following work around:
/**
 * Runs each route sequentially and returns first successful one.
 */
const FallbackHandler = pipe(
  [
    SolidSsrHandler,
    ViteDevHttpRouteHandler,
  ],
  Arr.map((route) =>
    route.pipe(
      Effect.andThen(
        (res) =>
          res.status === 404
            ? Effect.andThen(
              HttpServerRequest.HttpServerRequest,
              (request) => Effect.fail(new RouteNotFound({ request })),
            )
            : res,
      ),
    )
  ),
  Effect.firstSuccessOf,
)

export const router = HttpRouter.empty.pipe(
  HttpRouter.get("/", HttpServerResponse.text("yo")),
  HttpRouter.all("*", FallbackHandler),
)


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/95622

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/95629

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/121922

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/121920


[Feature Request]: beam.io.writetopubsub supporting ordering key

What would you like to happen?
Hi
I am using beam to build a realtime pipeline. The output of the pipeline is publish pubsub message for other usages.
I am using beam.io.WriteToPubSub, it will be helpful if it is supporting ordering_key.
Thank you!
Issue Priority
Priority: 3 (nice-to-have improvement)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Hi, thanks for reaching out. Could you please provide additional details what are you trying to accomplish and what isn't working? I haven't tried this recently, but I am seeing ordering_key defined already here: https://github.com/apache/beam/blob/98210d99b8530346b66fcffe66b893924c910bea/sdks/python/apache_beam/io/gcp/pubsub.py#L83

friendly ping. Thanks!

Closing due to lack of response. Please feel free to reopen : )

.reopen-issue

Hello @tvalentyn, I am facing the same issue using apache-beam 2.49.0 with python sdk 3.11.
Basically, following the steps described in the official documentation , I have created a PubsubMessage object providing also the ordering_key.
The finale result is that messages are correctly sent to PubSub but without any ordering key assigned: the ordering_key is always not visible on PubSub UI while if you use a different client, for example the google cli, I am able to see it in the messages.
Do you have any idea of what could be the issue?
Following the code snippet used:
| "Convert encoded message to PubsubMessage Object" >> beam.Map(lambda encodedMessage:beam.io.PubsubMessage(data=encodedMessage, attributes={"name":"test"}, ordering_key="testKey"))

| "Publish message to PubSub" >> beam.io.WriteToPubSub(
            topic=f"projects/{configs['project']}/topics/{topic}", with_attributes=True)
)


Feature/braintree web dropin

Proof of Concept: braintree web dropin, presumable needs backend changes too
feel free to criticize ;)
Screenshots

Pull Request Checklist

[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] The changes are tested.
[ ] The code is documented (docstrings, project documentation).
[ ] Changes are mentioned in the changelog.

Test Environment Config

API_URI=https://master.staging.saleor.rocks/graphql/

rebased to master closing pull request


Rename armPelionEdge to PelionIoT

@x85446 @ygoyal18 We are starting to do the work to convert everything from armPelionEdge to PelionIoT. We noticed that some of the build paths are hard coded, and therefore once this change goes into effect, all distros (snap, docker, meta) will need to change.
Just wanted to open up the discussion on when and how we wanted to move forward with this

@x85446 @ygoyal18 We are starting to do the work to convert everything from armPelionEdge to PelionIoT. We noticed that some of the build paths are hard coded, and therefore once this change goes into effect, all distros (snap, docker, meta) will need to change.
Just wanted to open up the discussion on when and how we wanted to move forward with this

PR is out of date and its easier for me to just make a new PR rather than try and adjust merge conflicts. Look for a new PR shortly

PR is out of date and its easier for me to just make a new PR rather than try and adjust merge conflicts. Look for a new PR shortly

@x85446 @ygoyal18 We are starting to do the work to convert everything from armPelionEdge to PelionIoT. We noticed that some of the build paths are hard coded, and therefore once this change goes into effect, all distros (snap, docker, meta) will need to change.
Just wanted to open up the discussion on when and how we wanted to move forward with this

@mray190 Do we have a ticket for this work? I think we can prioritize this for next Pelion Edge release.

@x85446 @ygoyal18 We are starting to do the work to convert everything from armPelionEdge to PelionIoT. We noticed that some of the build paths are hard coded, and therefore once this change goes into effect, all distros (snap, docker, meta) will need to change.
Just wanted to open up the discussion on when and how we wanted to move forward with this

@mray190 Do we have a ticket for this work? I think we can prioritize this for next Pelion Edge release.

@mray190 @ygoyal18 If they're GItHub clone paths, the internal rename symlink that GitHib maintains wrt Org names should keep it working.

@mray190 @ygoyal18 If they're GItHub clone paths, the internal rename symlink that GitHib maintains wrt Org names should keep it working.


support token-based upload to PyPI

Hi! PyPI's getting ready to add upload tokens to its API, so packagers can upload using tokens instead of username/password.
I thought you might want to test and verify that flit's upload works with this. Instructions for testing the pull request: https://github.com/pypa/warehouse/issues/994#issuecomment-512634222
It would be great if you could leave a comment on https://github.com/pypa/warehouse/pull/6084 telling us whether it works for you! This will help us avoid headaches when we roll out the feature on pypi.org.

Thanks. I'm just about to go offline for a week, and then it will be another few days while I dig myself out from the emails that build up. But I'll try to get round to it.

Please do enjoy your offline time! And if someone else would like to do the testing -- maybe @flying-sheep? -- that would, of course, be fine!

This beta feature is now live on PyPI and Test PyPI: https://pypi.org/help/#apitoken

Tried it; worg great. Just set FLIT_USERNAME='@token' and FLIT_PASSWORD='<yourtoken>'.
One question we may want to adress is how we pick which token for which project if not in an env variable.

Brainstorming how the UI could work:
If I'm trying to publish a release of austin and my ~/.pypirc says:
[pypi]
repository: https://upload.pypi.org/legacy/
username: takowl

Then flit could use the first it finds of:
# Project scoped token
keyring.get_password("https://upload.pypi.org/legacy/", "pypi-project-token:austin")

# User scoped token
keyring.get_password("https://upload.pypi.org/legacy/", "pypi-user-token:takowl")

If it doesn't find either of those, it would ideally connect as my user, prompting me for any necessary credentials, and then obtain and save a project-scoped token to use for uploads. If that's not possible, it might fall back to uploading with username & password as it currently does.
Does that scheme fit in with how you'd like to use tokens? Of course, it could all be overridden by env variables for CI - I'm just thinking about the upload-from-local case.

cc @di and @ewdurbin and @dstufft to answer this question. @woodruffw as an FYI.

The idea would work with me I had something similar in mind wihtout exact details; I'd just like the inerface to be (more or less) standardized across tools that can publish packages. That give us a chance to – at some point  – have a tools to list and manipulate tokens.
Thus I could not trust flit ; and do somehting like pip add-token austin <token>, and flit would be able to pick it up.

It would certainly be good if we could ensure different tools can use the same credentials. I think flit and twine can currently use the same usernames & passwords in keyring, since there's one obvious way to store that. It might take a bit more coordination for tokens. Or maybe flit can just use twine.

Hi - this feature is now out of beta, so I hope you can officially support it!

Changed the title to reflect that this is now a feature and documentation request.

Tried it; worg great. Just set FLIT_USERNAME='@token' and FLIT_PASSWORD='<yourtoken>'.

I had to use FLIT_USERNAME=__token__

I had to use FLIT_USERNAME=__token__

Yep, this makes sense: the @token name was removed before the beta ended.

Is there some documentation planned for this?

This is currently documented at https://packaging.python.org/specifications/pypirc/?highlight=token#using-a-pypi-token and https://pypi.org/help/#apitoken

FYI, I do this in a Github action (triggered by a tagged release), so you can then keep the token in a repository secret:
  publish:
    name: Publish to PyPi
    needs: [pre-commit, tests]
    if: github.event_name == 'push' && startsWith(github.event.ref, 'refs/tags')
    runs-on: ubuntu-latest
    steps:
    - name: Checkout source
      uses: actions/checkout@v2
    - name: Set up Python 3.7
      uses: actions/setup-python@v1
      with:
        python-version: 3.7
    - name: install flit
      run: |
        pip install flit~=3.0
    - name: Build and publish
      run: |
        flit publish
      env:
        FLIT_USERNAME: __token__
        FLIT_PASSWORD: ${{ secrets.PYPI_KEY }}

see for example: https://github.com/executablebooks/mdformat-tables/blob/a83ba37580c8f6c1827bce59a285ea62f47f56d5/.github/workflows/tests.yml#L74

For crosslink I'm going to add https://github.com/pypa/twine/issues/496 and https://github.com/pypa/twine/issues/565 as relevant.
In particular I'm when creating a token warehouse display this example for twine:
[distutils]
  index-servers =
    pypi
    PROJECT_NAME

[pypi]
  username = __token__
  password = # either a user-scoped token or a project-scoped token you want to set as the default

[PROJECT_NAME]
  repository = https://upload.pypi.org/legacy/
  username = __token__
  password = # a project token

I've added some instructions on how to publish a package using PyPI token. https://github.com/pypa/flit/pull/602


Race condition when testing SagaStateMachine

Is this a bug report?
Yes
Can you also reproduce the problem with the latest version?
yes with 8.0.6.
Environment

Dotnet version: 6.0.400
Operating system: ubuntu 20.04
IDE (Rider, VS Code, Visual Studio): Rider  2022.2.1

Steps to Reproduce

(Write your steps here:)
I'm writing tests for my SagaStateMachine. But somehow the saga harness won't await for consumed events?
Maybe this is intended, and we should never check consumed events before an exists check?
I made a simplified code example in which the fault occurs, depending whether you include the Task.Delay or not.
In my actual code this task delay isn't present of course, but the saga publishes 5 messages at once at some point.
Expected Behavior

I would expect that if I call await sagaHarness.Consumed.Any<EventB>() that it waits until the event was consumed (given a certain timeout).
So this should assert always to true, given the saga is ready to accept EventB:
await harness.Bus.Publish(new EventB(sagaId));
Assert.True(await sagaHarness.Consumed.Any<EventB>(), "Should consume eventB");

My code example will explain it better probably.
Actual Behavior

Test fails on Assert.True(await sagaHarness.Consumed.Any<EventB>(), "Should consume eventB");
Reproducible Demo

using System;
using System.Threading.Tasks;
using MassTransit;
using MassTransit.Testing;
using Microsoft.Extensions.DependencyInjection;
using Xunit;

namespace Hiltermann.Unit.Tests.Hiltermann.CIA.Core.KredietAanvragen.FinancialLease;

public class MySagaInstance : SagaStateMachineInstance
{
    public string CurrentState { get; set; }
    public Guid CorrelationId { get; set; }
}

public record EventA(Guid CorrelationId) : CorrelatedBy<Guid>;

public record EventB(Guid CorrelationId) : CorrelatedBy<Guid>;

public class MySagaStateMachine : MassTransitStateMachine<MySagaInstance>
{
    public MySagaStateMachine()
    {
        InstanceState(x => x.CurrentState);

        Initially(When(EventA).TransitionTo(SomeState));

        During(SomeState, When(EventB).Then(_ => { }));
    }

    public State SomeState { get; private set; }
    public Event<EventA> EventA { get; private set; }
    public Event<EventB> EventB { get; private set; }
}

public class MyTest
{
    [Fact]
    public async Task Why()
    {
        await using var provider = new ServiceCollection()
            .AddMassTransitTestHarness(cfg => { cfg.AddSagaStateMachine<MySagaStateMachine, MySagaInstance>(); })
            .BuildServiceProvider(true);

        var harness = provider.GetRequiredService<ITestHarness>();
        await harness.Start();
        var sagaHarness = harness.GetSagaStateMachineHarness<MySagaStateMachine, MySagaInstance>();

        var sagaId = Guid.NewGuid();
        await harness.Bus.Publish(new EventA(sagaId));
        Assert.True(await sagaHarness.Consumed.Any<EventA>(), "Should consume eventA");
        await sagaHarness.Exists(sagaId, s => s.SomeState);

        await Task.Delay(4000); // Succeeds without the delay, but fails with it.

        await harness.Bus.Publish(new EventB(sagaId));
        Assert.True(await sagaHarness.Consumed.Any<EventB>(), "Should consume eventB"); // This assert fails
    }
}

You have a period of inactivity in your test, four seconds. The default inactivity timeout is much less than that. You can adjust it to accommodate the delay:
var harness = provider.GetRequiredService<ITestHarness>();
harness.TestInactivityTimeout = TimeSpan.FromSeconds(5);
await harness.Start();

Adjust as needed.

Allright, I wasn't aware of the test inactivity.
If I understand it right the timer restarts every time something happens on the bus, correct?
This is why my demo test fails of course. But in my real test other messages are published by the saga. So this shouldn't trigger the TestInactivityTimeout right?
Probably somehting else is wrong in my setup. I'll look further into it and will close this issue for now.

There might be something else at play under the hood, but in the example above, the inactivity timeout would need to be adjusted either way.

So the test that keeps failing is related to this StateMachine code:
 During(Submitted,
            Ignore(Submit),
            When(Pay)
                .Then(x => x.Saga.IsPayed = true)
                .TransitionTo(PaymentReceived)
                .Publish(x => ..)
                .Publish(x => ..)
                .Publish(x => ..)
                .Publish(x => ..));
                ```

My tests does the following:

        ...
        await _harness.Bus.Publish(submit);
        await sagaHarness.Exists(id, x => x.AanvraagSubmitted);
        Assert.True(await sagaHarness.Consumed.Any<Submit>());

        await _harness.Bus.Publish(Pay);
        await sagaHarness.Exists(id, x => x.PaymentReceived);
        Assert.True(await sagaHarness.Consumed.Any<Pay>()); // this one fails

When exactly is an event considered consumed? Only after all state machine logic is handled? But then I would expect that it would wait for this.

Could this trigger the inactivity timeout? Even when the saga publishes to the bus?

I'm logging the `InactivityToken.IsCancellationRequested` now, and it does trigger on my ci pipeline. But I don't fully understand why or how I can prevent it (aside from increasing the TestInactivityTimeout of course)

A complete unit test that fails would be needed. Otherwise, I can't reproduce it.

Unfortunatly it doesn't fail all the time. I only see it fail on my ci pipeline sometimes.
But I managed to make a better example which resembles the real code and does fails sometimes:
using System;
using System.Threading.Tasks;
using MassTransit;
using MassTransit.Testing;
using Microsoft.Extensions.DependencyInjection;
using Xunit;

namespace Hiltermann.Unit.Tests.Hiltermann.CIA.Core.KredietAanvragen.FinancialLease;

public class MySagaInstance : SagaStateMachineInstance
{
    public string CurrentState { get; set; }
    public Guid CorrelationId { get; set; }
    public bool Something { get; set; }
}

public record EventA(Guid CorrelationId) : CorrelatedBy<Guid>;

public record EventB(Guid CorrelationId) : CorrelatedBy<Guid>;

public record EventC(Guid CorrelationId) : CorrelatedBy<Guid>;

public record EventD(Guid CorrelationId) : CorrelatedBy<Guid>;

public record EventE(Guid CorrelationId) : CorrelatedBy<Guid>;

public record EventF(Guid CorrelationId) : CorrelatedBy<Guid>;

public class MySagaStateMachine : MassTransitStateMachine<MySagaInstance>
{
    public MySagaStateMachine()
    {
        InstanceState(x => x.CurrentState);

        Initially(When(EventA).TransitionTo(SomeStateA));

        During(
            SomeStateA,
            Ignore(EventA),
            When(EventB)
                .Then(x => x.Saga.Something = true)
                .TransitionTo(SomeStateB)
                .Publish(x => new EventC(x.Saga.CorrelationId))
                .Publish(x => new EventD(x.Saga.CorrelationId))
                .Publish(x => new EventE(x.Saga.CorrelationId))
                .Publish(x => new EventF(x.Saga.CorrelationId)));
    }

    public State SomeStateA { get; private set; }
    public State SomeStateB { get; private set; }
    public Event<EventA> EventA { get; private set; }
    public Event<EventB> EventB { get; private set; }
}

public class MyTest
{
    [Fact]
    public async Task Why()
    {
        await using var provider = new ServiceCollection()
            .AddMassTransitTestHarness(cfg => { cfg.AddSagaStateMachine<MySagaStateMachine, MySagaInstance>(); })
            .BuildServiceProvider(true);

        var harness = provider.GetRequiredService<ITestHarness>();
        await harness.Start();
        var sagaHarness = harness.GetSagaStateMachineHarness<MySagaStateMachine, MySagaInstance>();

        var sagaId = Guid.NewGuid();
        await harness.Bus.Publish(new EventA(sagaId));
        await sagaHarness.Exists(sagaId, s => s.SomeStateA);
        Assert.True(await sagaHarness.Consumed.Any<EventA>(), "Should consume eventA");

        await harness.Bus.Publish(new EventB(sagaId));
        Assert.True(await sagaHarness.Consumed.Any<EventB>(), "Should consume eventB"); // This assert fails
    }
}

This test never fails for me when using the latest -develop build.


Support for schema type: JSON

Hello,
We are test-driving Schema Registry and really like it. According to http://registry-project.readthedocs.io/en/latest/competition.html Hortonworks' Registry supports (or will support) JSON schema. When are you expecting to add support for JSON Schema?
Thank you

@eparisca Thanks for your interest in this project. JSON schema is not supported yet, but it can be added with the existing framework in a similar way it is done for Avro. You can raise respective Github issues after going through the code. You can also let us know if you need any help in getting started with that.

@satishd I would love to help. How do I get started? Any special recommendations?
I'm already walking through the Avro code in the framework in registry/schema-registry/common/src/main/java/com/hortonworks/registries/schemaregistry/avro/
Looking at https://github.com/everit-org/json-schema as a potential good fit for the Schema validator. Thoughts?
Thank you.

@eparisca Good that you are going through avro support implementation in registry. You need to implement SchemaProvider for jsons and register as it is done for avro here
You can start with implementing SchemaProvider to address the below

checking for compatibility between versions.
generating finger print using normalized form of schema.
generating resultant schema if it supports any schema imports/includes.
effective serialization/deserializtion of json payloads.

You can start exploring either  jackson based or https://github.com/everit-org/json-schema for validator etc.

@eparisca , Are you looking into this?

@kkarthikpsgtech No, sorry. I took a new job and am no longer using Schema Registry.

@satishd can you assign this ticket to myself? I have started working on it

Could you kindly clarify what the scheme types are supported in lastest 0.8.0 RC3 release?

From this page https://registry-project.readthedocs.io/en/latest/competition.html, I see registry supports AVRO/PROTOBUF/JSON
But this JIRA is still open.

Can you support JSON in any format?

{
"field": [{
"name": "age",
"type": "string"
}, {
"name": "name",
"type": "string"
}]
}

{"hello":"world"}


fix: change taxcloud api endpoint

Two weeks ago, the gem stopped working. We're receiving a Connection reset by peer - SSL_connect when we try to fetch taxcloud services.
I've opened a ticket with them, and they said:

The issue here is the asmx.taxcloud.com domain name. Please update to api.taxcloud.com and I believe api connections will resolve correctly.

This PR changes the base address to the one suggested by their support team.
I didn't update the tests, I wasn't able to run them locally. Some of them are broken, and the cassettes are not been updated for 3 years.

Add to CHANGELOG.md and let's ensure tests pass? You can bulk replace the URL in the cassettes, no need to re-record them.

I release 0.5.0 with this change.

@mrmarcondes if you're going to be using this library consider picking up some of the long outstanding items, I don't think any of the original owners are using it actively, including myself, given that we haven't dine a release in years, and we don't want it to go unmaintained :)

Thank you, @dblock. i'm going on vacation. i'll look at them after.


Update dependencies and move build outputs out of vcs

Please update package.json file and bump all dependencies to latest version

Please bump all dependcies in package.json to latest version

Please revert commit bb3f5967d8045c19271bb949064896bd31376389


Support pasting a file into VS Code

in macOS Finder select a file and from the context menu do a Copy "file"
in the VS explorer select a folder and open the context menu

Observe:
the "Paste" action is dimmed (disabled)
Since it is possible to drag-n-drop a file from the Finder into VS Code, doing the same with "Paste" should be supported as well.

I think there is not electron api for us to do this.
Since dragging a file from the finder fills in the correct drag data which we can extract.
However the Copy "file" command does not do that, and we have no access to the copy clipboard from electron.
Though I might be wrong so assignign to September to investigate
fyi @bpasero @deepak1556

I have not looked into this for a while, but see https://github.com/microsoft/vscode/issues/164 as related/duplicate.

Yeah dup of that. Assigning myself to that one and to September to investigate if we can improve seomthing there


Apply to become an OCM member

Application
Community Participant
I have been actively contributing to the OCM community for a considerable period of time, and I am eager to apply for OCM membership.
My aspiration is to make both public and private contributions through my involvement in documentation, website development, blogging, and presentation materials.
This will enable me to further promote cloud-native technologies within the community and ensure a broader awareness among a wider audience.
Requirements
Have made multiple contributions to the project or community. Contribution may include, but is not limited to:

https://github.com/open-cluster-management-io/open-cluster-management-io.github.io/pull/377
https://github.com/open-cluster-management-io/open-cluster-management-io.github.io/pull/378
https://github.com/open-cluster-management-io/open-cluster-management-io.github.io/pull/379
https://github.com/open-cluster-management-io/open-cluster-management-io.github.io/pull/381
https://github.com/open-cluster-management-io/open-cluster-management-io.github.io/pull/382

Checklists

[x]  Enabled [two-factor authentication] on their GitHub account.
[x]  Contributing to community discussions (e.g. meetings, Slack, mailing list discussion).
[x]  Subscribed to [https://groups.google.com/g/open-cluster-management].
[x]  Have read the contributor guide.
[x]  Actively contributing to 1 or more subprojects.

Sponsors

@mikeshng

invitation sent, Thanks!

/close


Subsidiary nodes are not included in the node limits

Subsidiary nodes are not included in the node limits, that is there are (potentially) more nodes in the query-result than are allowed.

This is a duplicate of #276


Universal app 8.1 release build resources not found

From codeplex: https://fluentvalidation.codeplex.com/workitem/7214
"I was trying to use this library in a universal windows app 8.1, which is working fine until I use Release mode to deploy the app.
There seems to be a problem with the location of resource files, I believe microsoft changed the way these work (not sure). In universal apps resw files should be used instead of resx so far I know.
This is the following error I get when deploying:
Error: Compile filter argument specified non-existent file: ...\obj\ARM\Release\MSIL\da\FluentValidation.resources.dll
I checked the folder and indeed its not there, but it is in ...\obj\ARM\Release\MSIL\FluentValidation.resources.dll
Instead of each language in a separate folder.
Does anyone know a fix for this or will this require a new fluentvalidation package for universal apps?"

Also having this issue. It does not happen, though, when cloning the Git tree and building from source code and then referencing the project. So something is probably wrong with the NuGet packaging.


feat: add contentful-commerce to the repo

Purpose
Add the Contentful Commerce app. This application helps creating a product catalog schema within Contentful, which then allows to leverage external Commerce Engines (such as Commerce Layer) for purely the transactional element of it.
Approach
I built it using the App SDK, in particular the content management APIs to spin up the content model. Any edits we only allow is the name of the content types.
Testing steps
First install

Install the application.
Configure labels for individual content types (optional).
Hit "Save" to let the app create the content types.
Check the content model tab to verify content types have been created.

Consequent changes

Visit the app configuration page.
Change any of the labels.
Hit "Save".
Check the edits are reflected in the content model (but not the ID).

Breaking Changes
First submission.
Dependencies and/or References
In the README file.
Deployment
It's pretty straight forward. I already have uploaded the app using the upload script.

Hello @alexcanessa. Thank you for your submission here - I am going to close this PR given the communicated status of the app. Please let me know if you have any questions.


tests fail: cannot find -lnlohmann_json

/usr/bin/c++  -O2 -pipe -fno-omit-frame-pointer -fstack-protector -fno-strict-aliasing -fno-omit-frame-pointer -Wunused-parameter -Wextra -Wreorder -Wconversion -Wsign-conversion -march=native -std=c++14 -O2 -pipe -fno-omit-frame-pointer -fstack-protector -fno-strict-aliasing -fno-omit-frame-pointer  -fstack-protector CMakeFiles/test_xtl.dir/main.cpp.o CMakeFiles/test_xtl.dir/test_xbase64.cpp.o CMakeFiles/test_xtl.dir/test_xbasic_fixed_string.cpp.o CMakeFiles/test_xtl.dir/test_xcomplex.cpp.o CMakeFiles/test_xtl.dir/test_xcomplex_sequence.cpp.o CMakeFiles/test_xtl.dir/test_xclosure.cpp.o CMakeFiles/test_xtl.dir/test_xdynamic_bitset.cpp.o CMakeFiles/test_xtl.dir/test_xhash.cpp.o CMakeFiles/test_xtl.dir/test_xhierarchy_generator.cpp.o CMakeFiles/test_xtl.dir/test_xiterator_base.cpp.o CMakeFiles/test_xtl.dir/test_xmeta_utils.cpp.o CMakeFiles/test_xtl.dir/test_xoptional.cpp.o CMakeFiles/test_xtl.dir/test_xtype_traits.cpp.o CMakeFiles/test_xtl.dir/test_xproxy_wrapper.cpp.o CMakeFiles/test_xtl.dir/test_xvariant.cpp.o  -o test_xtl  -Wl,-rpath,/usr/local/lib -lnlohmann_json /usr/local/lib/libgtest.so /usr/local/lib/libgtest_main.so -pthread && :
/usr/bin/ld: cannot find -lnlohmann_json

nlohmann-json is a headers-only library:
$ pkg info -l nlohmann-json-3.1.2
nlohmann-json-3.1.2:
        /usr/local/include/nlohmann/json.hpp
        /usr/local/lib/cmake/nlohmann_json/nlohmann_jsonConfig.cmake
        /usr/local/lib/cmake/nlohmann_json/nlohmann_jsonConfigVersion.cmake
        /usr/local/lib/cmake/nlohmann_json/nlohmann_jsonTargets.cmake
        /usr/local/share/licenses/nlohmann-json-3.1.2/LICENSE
        /usr/local/share/licenses/nlohmann-json-3.1.2/MIT
        /usr/local/share/licenses/nlohmann-json-3.1.2/catalog.mk

and there should never be -lnlohmann_json for it.

nlohmann_json is an optional dependency but is still required for the test target.
This was reported earlier this week. We should either specify that it is required for the test target or skipp the corresponding tests when missing.

... or skipp the corresponding tests when missing.

It is always missing as a .so library, because it is a headers-only library.

I don't think so. This is just that when it does not find a target, cmake assumes that you are trying to link with a library.

Why can't it find the target? nlohmann-json-3.1.2 is installed.

@yurivict Any chance you installed nlohmann-json from the master branch? The nlohmann-json project adapted it's targets to the more modern namespaced style with this PR https://github.com/nlohmann/json/pull/1048 . However there has been no release since then. The travis etc. tests work because they use the target nlohmann-json if you pull from the master branch you need to link against the new target nlohmann_json::nlohmann_json. I've got an upcomming PR that fixes those issues.

nlohmann-json is of version 3.1.2.

Building in the test subdirectory.

That'll be the issue, you could try changing
if (CMAKE_CURRENT_SOURCE_DIR STREQUAL CMAKE_SOURCE_DIR)
    project(xtl-test)

    find_package(xtl REQUIRED CONFIG)
    set(XTL_INCLUDE_DIR ${xtl_INCLUDE_DIRS})
endif ()

in CMakeLists.txt to
if (CMAKE_CURRENT_SOURCE_DIR STREQUAL CMAKE_SOURCE_DIR)
    project(xtl-test)

    find_package(xtl REQUIRED CONFIG)
    find_package(nlohmann_json QUIET)
    set(XTL_INCLUDE_DIR ${xtl_INCLUDE_DIRS})
endif ()

That'll be the issue, you could try changing ...

This helped, thank you!


generate of dynamic routes running too quickly: delay needed

The backend I'm fetching data from in each page of a dynamic route crashes if queried too frequently. Since I have no control over the server I need some way to force a delay between calls to renderRoute.

Can you post a code snippet about your queries for generate option to help you?

This is my dynamic route (I have about 400 of them).
// pages/articles/_id.vue
async asyncData ({ params, error }) {
     var article = await backend.getArticle(params.id)
     return { article }
}

in my nuxt.config.js I have generate: { routes: function() {/* promise that generates about 400 routes */}
so when I run npm run generate the script slams my backend with 400 calls, causing it to crash. If I could force a delay between each of the 400 calls, of say 100ms, the script would take longer to execute but my server would probably survive. My sysadm is too busy to stabilise the server :(

@Atinux @alexchopin Is this features works already? I don't have any delays between generating calls.

You have to use generate.interval now (See https://github.com/nuxt/nuxt.js/blob/dev/lib/common/options.js#L122)


Documentation for new python client

Current coverage is 93.80% (diff: 100%)

Merging #41 into master will not change coverage

@@             master        #41   diff @@
==========================================
  Files            14         14
  Lines          1178       1178
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1105       1105
  Misses           73         73
  Partials          0          0

Powered by Codecov. Last update 85de25b...a8103a2

Merged into https://github.com/scrapinghub/python-scrapinghub/pull/38.


:sparkles: Setup monorepo using pnpm

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Requires_grad of src_pred_mask

When num_iter>3, src_pred_mask becomes a tensor that requires gradient, and then an error will be reported in the  function generate_overlap_mask
RuntimeError: logical_not(): functions with out=... arguments don't support automatic differentiation, but one of the arguments requires grad.

Hi,
Have you changed any code in this repo? I haven't found the same error. src_pred_mask is used in a hard way since the argmax operation will change it to a binary map. Besides, the functiongenerate_overlap_mask is just used to generate the ground truth masks at each iteration, which have no need to require gradients or gradients backward.

Hi,
Have you changed any code in this repo? I haven't found the same error. src_pred_mask is used in a hard way since the argmax operation will change it to a binary map. Besides, the functiongenerate_overlap_mask is just used to generate the ground truth masks at each iteration, which have no need to require gradients or gradients backward.

Sorry, there may be differences in the pytorch versions we use. I added a detach to src_pred_mask, which should solve the problem, thank you

Okay. I will close this issue.


TypeError: interpolate() got an unexpected keyword argument 'recompute_scale_factor'

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
1.
2.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows, Ubuntu 18.04]
This repository version [e.g. pypi 0.3.1 or branch/commit ref]
PyTorch version w/ CUDA/cuDNN  [e.g. from conda list, 1.7.0  py3.8_cuda11.0.221_cudnn8.0.3_0]

Additional context
Add any other context about the problem here.

info not filled out, you are probably pytorch < 1.6

Yes I ma using PyTorch 1.4

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
1.
2.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows, Ubuntu 18.04]
This repository version [e.g. pypi 0.3.1 or branch/commit ref]
PyTorch version w/ CUDA/cuDNN  [e.g. from conda list, 1.7.0  py3.8_cuda11.0.221_cudnn8.0.3_0]

Additional context
Add any other context about the problem here.

Just a work around take out the recompute scale factor argument  on Line 151

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
1.
2.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows, Ubuntu 18.04]
This repository version [e.g. pypi 0.3.1 or branch/commit ref]
PyTorch version w/ CUDA/cuDNN  [e.g. from conda list, 1.7.0  py3.8_cuda11.0.221_cudnn8.0.3_0]

Additional context
Add any other context about the problem here.

Just a work around take out the recompute scale factor argument  on Line 151