How to setup a clickable for a row?

In the sample app (hosted online). I'm able to click a row. i.e. the cursor changes to a hand symbol when hovering over a row.
But, I'm not able to find a way to enable or add a clickable to a row.
One more thing I noticed, whenever I change the page, an API call happens. isn't there a way to use the cached data when switching pages?
On clicking the default refresh, is there a way to receive a callback for that?

The online demo was outdated until now (if you still see the older version, clear your cache for that page).
An old version of the package supported cached data but was removed in favor of you caching your data, it is more consistent and it's better to leave the developer to handle how to cache the data.
There is no way to receive a callback when clicking the default refresh. If you need it for some specific reason, I can consider to include it in the next version

Thanks for the reply. It is good to leave it to the client to decide about caching data. But, comparing it to a List, where we do pagination & scrolling back (up) doesn't fetch the results, the List internally maintains it. So a built-in similar behavior to a paginated List will be really beneficial IMHO. Otherwise it will be steep learning curve for newbies.
A callback for a refresh or any actions (interactions) happening in the table is always welcome, we would use it to log/track or do something.
You haven't said anything about clicking a row which was there in the online demo. My use-case is simple, provided a row is clickable, I just want to take the user to another screen (a detailed screen). this would be a common use case for most.

Thanks for the reply. It is good to leave it to the client to decide about caching data. But, comparing it to a List, where we do pagination & scrolling back (up) doesn't fetch the results, the List internally maintains it. So a built-in similar behavior to a paginated List will be really beneficial IMHO. Otherwise it will be steep learning curve for newbies.

I think I don't understand you here. Can you explain it again, please?

A callback for a refresh or any actions (interactions) happening in the table is always welcome, we would use it to log/track or do something.

Nice, I will consider it for the next release.

You haven't said anything about clicking a row which was there in the online demo. My use-case is simple, provided a row is clickable, I just want to take the user to another screen (a detailed screen). this would be a common use case for most.

Clicking on a row only selects it, it does not allow doing something when you "single" click it. That is what the property says rowsSelectable. It can be a good feature to add tho

I think I don't understand you here. Can you explain it again, please?
If I compare your table with a ListView pagination.
I maintain a List in my state & add keep adding items to the list. whenever state changes, flutter updates the widgets and the list goes on. Let's say each page has 10 items, likewise user has scrolled down to 10 pages, now 100 items.
If a user scrolls up to item 0. we are not making API call again to get the previous page items. the state contains the List. Similar to a facebook feed screen.

Similarly, in the table, when user clicks next, I'll make API call with page number or offset and append the items to my List in the state. Then, when user presses back, I would expect to show the previous items from my list.
See this code:
fetchPage: (pageToken, pageSize, sortBy, filtering) async {
          var result = await RepositoryProvider.of<LeadRepository>(context)
              .fetchLeadPaginatedList(pageToken, pageSize);
          return PaginationResult.items(
              elements: result.items, nextPageToken: result.nextPageToken);
        },

Currently, when user presses previous or next this callback is getting invoked, that 's why API call is happening even for previously fetched items, since you decided to let the developer decide the caching logic.
But, if we go with the approach similar to a ListView pagination concept (the widget is backed by a growing list of items). It would be intuitive  IMHO.
Also, I use BLoC architecture (https://bloclibrary.dev/), so I don't want to expose my Repository to the view layer. But, with your approach, I ended up making the API (i.e exposing the repository) in the view layer itself.

I understand. But we end up talking about including cache in the table.
I don't think the paged_datatable approach forces you to expose the repository layer to the view, what is the problem with using Bloc in the fetchPage callback? I have never used Bloc, but with other state management libraries you are not forced by paged_datatable to expose the repository layer to the view

I'm relatively new to Flutter development, so when I started using this library. I was expecting it to be similar to ListView pagination, where I just give a list of data to the widget & it takes care of rendering & I get a callback to load more (return type void). But in your library, the fetchPage callback expects to return the updated list. For comparison, you can refer to this example: https://pub.dev/packages/infinite_scroll_pagination/example.
The BLoC is based on events (fire & forget), we can't await for an event to update the state (there could be workarounds, which I'm currently exploring).

It does not expect to return an updated list, it expects you to return a list with all the elements that match the current page token, filters, sorting, etc.
But now I understand better your issue. If you find a workaround for the problem using Bloc, share it here if you want

Thanks for the reply. Definitely. Kindly provide support for a clickable row & callback for all the possible user interactions.


Server::Base broadcasting test added

Hi, this is my first contribution attempt to rails community.
I created a simple test to check if a message is delivered to Redis, I used Minitest::Mock to isolate the server. Not quite sure if ActionCable::Server::Configuration should be mocked.
I would like to have some feedback, so I can move forward to add more tests.

Hey, welcome, and thanks for the contribution!
We shouldn't need to mock the config. That one can be created on its own and assigned to ActionCable::Base.config =.

Let's stub Rails. Action Cable is not intended to be useful outside the context of Rails at the moment.

New PR #38  opened using a feature branch.


Distribution App on Google Play and AppStore

Describe the solution you'd like
HockeyApp currently has an on Google Play and the AppStore. This app provide a list of all the apps and their build history. Our QA department finds it useful to quickly access previous builds.
Describe alternatives you've considered
The alternative we are using now is a public download page from AppCenter. This is more or less a suggestion as this alternative is currently working.

@tmdues There is actually already an app on Google Play: https://play.google.com/store/apps/details?id=com.microsoft.hockeyapp.testerapp&hl=en
Even though it is branded as "HockeyApp", the app version with the pink icon is already using App Center underneath and you should be able to see all your apps that you can get from the website today.
There was never a HockeyApp app on the Apple App Store, due to issues with the store's submission guidelines but we're always exploring better solutions for our iOS users too 🙂


Fix and prettify references to compile-time size determination

Replaced [#sec-determin] with (Section [#sec-determin]) globally
Also, sec-determin doesn't exist. I think it should have been sec-minsizeinbits?

I just looked here recently https://p4.org/p4-spec/docs/p4-16-working-draft.html and noticed that there are a few more broken links, maybe you can take a look at all of them?

They show up as "#" in the text.

Yep, I was going to do that next. Just breaking things down into small pieces for easy review... though, maybe too small :-)


Pascal 3.2 Runtime

This PR creates a runtime for Pascal 3.2 (with some caveats)!
Reference
https://github.com/appwrite/appwrite/issues/4023
Caveats
Caveats:

StdOut and StdErr are not returned to the program after the first execution
Installing dependencies is not implemented yet. Preinstalled units can be used right off the bat (which includes most of the useful ones, I suppose?)
Custom types / classes are not implemented (yet?), I think. I have not tested them yet but I believe that type definitions may not be in the middle of the implemented procedures, although I haven't tried it out

I think a lot of this could be improved by creating a unit from this and loading that instead but I felt like that kind of defeated the idea of a function runtime if you had to write essentially a library file including all the fuzz around it. It might be doable similar to how the Java 8.0 runtime does it, wrapping the function in a class with imports and package definition and stuff?
I hope though that this implementation covers the (probably rare) usecases there are for a Pascal function runtime.

Thank you so much for the PR 🤩. We're adding the hacktoberfest-accepted label to ensure this PR counts towards your Hacktoberfest contributions count. With that said, please stay active on this PR to address any comments once you receive a review. Happy Hacktoberfest! 🎃

@geisterfurz007 thanks a lot for your contributions during Hacktoberfest 2022!
Please reach out to me on our Discord server if you would like to claim your Appwrite swags! As a way of saying thank you, we would also love to invite you to join the Appwrite organization on GitHub. Please share your GitHub username with us on Discord.

Thanks Christy, I have already received my swag a couple weeks back :) I rebased this PR again to resolve the conflict in the .travis.yml; if there are any other changes needed, let me know!

Hey there 👋
We are about to release Open Runtimes V3 which brings some changes to both how we structure runtimes internally, as well as changes to some interfaces that developers inteact with. We did this to allow new features and bring Open Runtimes closer to HTTP standards ✨
We value your contribution and want to ensure all changes can be merged to the main branch. However to make it possible we request you to update the PR to follow the V3 structure and syntax. You can refer to V3 Pull Request and take a look at Node.JS 18.0  runtime specifically. Some biggest changes are:

Helper scripts (build, start)
Folder renaming for build & start process
context object instead of previous req and res
HTTP server to accept any method and any path
Headers were introduced for logs and errors
Safe timeout was introduced

v3 branch also has many new end to end tests to ensure proper integration, so please sync with that and target your branch against v3 branch.
Please let us know if you are interested in working on this 🙏

Ho boi... Honestly, I am not sure @Meldiron! I enjoyed the challenge last October and found some nostalgia in dabbling with Pascal again but I would lie if I said it wasn't a pain to get running 😄 I am also questioning whether there is an actual target audience for an Open Runtime for Pascal; the language is slightly dated, poorly documented and really, I cannot see anyone picking up something that has been designed to support serverless functions while sticking to something like Pascal.
If there is an actual desire to have this become a thing, I can maybe look at this near end of July or start of September; everything in between is packed with stuff.


[BUGFIX]: inverse problem examples dont suppress plots

figures for BIP v SIP example show on screen instead of just saving quietly. I was rushing and using an environment without a DISPLAY variable, so I didn't catch it.
do the if not save, then show, and save by default in the run_inv() method.

maybe have a --show flag?


re-implement semaphore for API limits

I just removed it in pull request #4, but from doing some local testing there should still be a semaphore to limit concurrent Genius API calls.

PR #6 uses a buffered stream and keeps the API calls in the same process, avoiding the need for a semaphore


Maintainers?

Are you interested in getting help maintaining logxi? I'd be happy to help with the outstanding issues if you are open to letting other people help you. There is little activity here and I'd preferably not fork the original project.
@mgutz

I'm interested in this as well.  I'm starting a new Go project and looking at log libraries. Would be nice to clear out a few of the open issues here.
@KidLinus given that it's been six months since you wrote this, perhaps we get a fork going and start merging in PRs.  If @mgutz has time and wants to re-upstream our work then we can close out the fork.  Seem reasonable?

@AlbinoGeek has volunteered to merge PRs (see: #21) so I'd suggest we all head over here:
https://github.com/AlbinoGeek/logxi


[Explorer] Remove CLI code

Need

The cli is no longer needed in the explorer repo

Approach

delete cli module
update tests
update config instantiation to no longer check for args passed in via the cli
update docs

DOD

There are no references to the cli application in the explorer repo

@MDunitz Under single-cell-explorer/backend/test/test_czi_hosted/ I'm only seeing invocations of cellxgene launch in single-cell-explorer/backend/test/test_czi_hosted/unit/cli/test_launch.py which will be obsolete upon removal of cli code. Or am I missing some instances that are invisible to search, such as arrays of arguments that get joined a la ["cellxgene", "launch"] or something... regex search suggests they aren't on the same line together anywhere else

I think I see what you're saying now. The client tests rely on cellxgene launch.


Removed dependency on NODE_PATH for grommet path resolving.

Grommet documentation said "make sure you set the NODE_PATH to point the node global modules install directory". This can be problematic, as explained in this nvm issue.
Using a relative path to the current module is safer and simpler.

Interesting approach @rstuven. I will test that tomorrow :+1:

Thanks for your contribution @rstuven, everything looking ok.


Publish sourcemaps for production

Type of issue
Feature Request
Description
Publish meaningful sourcemaps for production instead of empty-sourcemaps. Sourcemaps do not get loaded until devtools are open and they are a useful debugging tool.
Current behavior
Production sourcemaps are empty
Expected behavior
Production sourcemaps should not be empty
Steps to reproduce

Your environment

fusion-cli version:

Node.js version (node --version):

npm version (npm --version):

Operating System:

Source maps are created in production. Do you mean you want source map comments in production JS files?

Closing in favor of a new ticket


CB-22154 Change the extra host group names in EDL from HG to…

_scale_out, which more readable to the customer

this should go to the next release. Risky change..

this should go to the next release. Risky change..

All these changes are related to EDL. This PR has updated the names of extra hostgroups nothing more. Why do you think it is risky?
We disabled EDL on the PROD to get the names right before customers can use it.

@RokolyA94 Can you squash the commits?

This goes to 2.73 is this the correct branch?

retest this please!


media_player.kodi failing with unexpected mimetype 'text/html'

Home Assistant release (hass --version):
0.52.0
Python release (python3 --version):
Py3.4.2
Component/platform:
media_player.kodi
Description of problem:
After upgrading from 0.48 to 0.52, integration Kodi is no longer working for me. An exception is being raised regarding an unexpected mimetype in the the response (see traceback below). Kodi version is 17 on Openelec 8.0.4; I haven't upgraded anything on the Kodi side since it was known working.
All my settings for the Kodi webserver are default and I have all the remote control settings turned on, again same as since it was known working.
Expected:
It works.
Problem-relevant configuration.yaml entries and steps to reproduce:
media_player:
    - platform: kodi
      host: http://<ip address>

I've also tried adding enable_websocket: false with no luck. The media_player.kodi entity does not appear in the frontend at all. With logging set to debug, the only error message I get is the traceback below.
Traceback (if applicable):
2017-08-27 14:57:21 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 235, in _step
    result = coro.send(value)
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/entity_component.py", line 381, in async_process_entity
    new_entity, self, update_before_add=update_before_add
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/entity_component.py", line 210, in async_add_entity
    yield from entity.async_update()
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/media_player/kodi.py", line 415, in async_update
    self._players = yield from self._get_players()
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/media_player/kodi.py", line 363, in _get_players
    return (yield from self.server.Player.GetActivePlayers())
  File "/root/.homeassistant/deps/lib/python3.4/site-packages/jsonrpc_async/jsonrpc.py", line 41, in send_message
    response_data = yield from response.json()
  File "/usr/local/lib/python3.4/dist-packages/aiohttp/client_reqrep.py", line 730, in json
    headers=self.headers)
aiohttp.client_exceptions.ClientResponseError: 0, message='Attempt to decode JSON with unexpected mimetype: text/html'

Thanks as always, Home Assistant is great. Lemme know if you need more info.

Hmm well ok it looks like the component is showing up intermittently or maybe it just takes a while (at least half an hour), but it always shows up as 'off'.

 I had this leftover from when the config option used to be url, I'm not sure why it suddenly stopped working but either way that fixed it.


xtheadvector: Move intrinsics into the XTheadVector chapter

There is no strong reason to separate the intrinsic specification from the ISA specification. So let's make that a subchapter.

LGTM. However, it might be due to me merging a new patch first, causing this patch to have conflicts. Could you please rebase it and submit again?

Rebased.


Add a 2 weeks expiration on the published nightly builds on Quay

What do you want to improve?
There is a nightly build every day that will publish images to Quay. We don't need to keep these images for more than 2 weeks (14 days). We should be able to add an expiry on the nightly images.

https://access.redhat.com/documentation/en-us/red_hat_quay/3/html/use_red_hat_quay/working_with_tags#tag-expiration
https://www.geeksforgeeks.org/docker-label-instruction/

What is the current behavior?
The images never expire
What is the new behavior?
The nightly builds will expire after 14 days.

I will be happy to get assigned this issue please


Typo in Azure key vault

Kindly review this paragraph “Azure Machine Learning service does store any passwords or keys “ , seems we are missing a not to complete the do not store

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

ID: e5c3bce1-2494-6caf-728c-53127ae85329
Version Independent ID: acdd8494-76aa-d47b-9735-7aea72613a95
Content: Enterprise security - Azure Machine Learning service
Content Source: articles/machine-learning/service/concept-enterprise-security.md
Service: machine-learning
Sub-service: core
GitHub Login: @aashishb
Microsoft Alias: aashishb

@ignaciofls Thank you for the feedback! We are investigating this and will get back to you shortly.

@ignaciofls The update is now complete by a PR. This change should be reflected in the documentation in the next 24 hours.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag @RohitMungi-MSFT in your reply. We will gladly continue the discussion and we will reopen the issue.


[salt] runner actions

Context
Stackstorm is not installed on the Saltstack master but needs to execute Salt Runner Modules
Proposed Solution
This action allows for the execution of various Salt Runner Modules through the Salt NetAPI.
Explicit Runner Actions Included

[x] jobs: active, list_jobs
[x] pillar: show_pillar, show_top
[x] manage: up, down, versions, status
[x] cloud: action, full_query, list_images, list_locations, list_sizes, profile, select_query,
[x] cache clear_all, clear_grains, clear_mine, clear_mine_func, clear_pillar, grains, mine, pillar
[x] thin: generate

Generic Runner Action
For example:
st2 run salt.runner module=manage.down

Additional Notes

This was developed against Salt version 2014.7+
Given limitations of the NetAPI, runners that require positional arguments have been omitted.

@jfryman :eyes:

@jfryman @DoriftoShoes @manasdk Is there anything else left to chance on this PR? Is it suitible for merging?

I am fine with this approach.
+1

:+1:


[Rendering] Allows to use in-memory generated materials as blend layers

PR Details

Description
By querying the Material.Descriptor property first an in-memory generated material can be used in blend layers.
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Do you directly invoke the Material.New yourself?
I wonder if we want to make this behavior default (we probably want to get rid of unused data, and also you never know if user might mutate this descriptor to create multiple materials).

I could live without the Material.New - we could simply assign the descriptor on our own after calling it. However the lookup was important I remember - to not rely on having the material as an asset.

I just updated the PR and added a comment in code.


Low performance of service bus queue receive

https://github.com/Azure/azure-service-bus-java/issues/324

Expose properties concurrency and prefetch-count service bus queue binder to help tune performance. Please refer https://github.com/Microsoft/spring-cloud-azure/tree/master/spring-cloud-azure-stream-binder/spring-cloud-azure-servicebus-queue-stream-binder


docs: import from layerchart using alias

Sean, awesome talk! Noticed you were using different imports for your docs than users need to use. I have the same situation in Kitbook and using an alias solves it. So then you can import from layerchart which just happens to be an alias to your lib directory. In mine I do 'kitbook': 'src/lib' but in yours I had to do 'layerchart': 'src/lib/index.js'. I'm not sure why, but it works. Anyhow you can see how I changed your Arc docs to utilize it. If you like it, you can spread it across the rest of your examples. :)
And yes, let's talk more if you ever decide to use Kitbook. There's a some glaring features missing from it like view source code which would be almost trivial to add as I have the raw strings from each component already, I just haven't taken the time to do it. 1 thing at a time you know. But it sure would make it easier for you in some spots like how you're writing your getting started page in html, not markdown.
Oh, and Kitbook has no dark mode support or any theme for that matter and you've blown it out of the water. So that's another thing you might want to see in Kitbook first. Not sure what's important to you.

Any reason you don't add "dev": "pnpm --filter=layerchart dev", to your root package.json file and avoid the need to change directories?

Sean, awesome talk!

Thanks, and same to you!  I loved your talk and looked into Kitbook, although I need to dig in deeper when things calm down (do they ever though 😁).  It looks very robust and I see it solving some pain points I've encountered in LayerChart and Svlete UX's docs.

Noticed you were using different imports for your docs than users need to use. I have the same situation in Kitbook and using an alias solves it. So then you can import from layerchart which just happens to be an alias to your lib directory. In mine I do 'kitbook': 'src/lib' but in yours I had to do 'layerchart': 'src/lib/index.js'. I'm not sure why, but it works. Anyhow you can see how I changed your Arc docs to utilize it. If you like it, you can spread it across the rest of your examples. :)

Using different imports between the examples has always been a pain point and even have a note about it in the Getting Started section (which we will be able to remove 🎉)

The alias solution looks great! TBH it's something I meant to investigate as a solution but was concerned going through the top-level index with all it's re-exporting and would be painful for development and not allow Vite to optimize on initial startup (and possibly impact HMR).  If it works out for you, I think proceeding with the rest of the examples would be awesome, and we'll just be mindful of any development performance regressions and evaluate solutions as needed.  I know barrel index files are always a bundlers worst nightmare and typically frowned upon, but the DX is hard to beat.  I used to feel this pain a lot early on in development (first with Snowpack, then early versions of Vite), but I know Vite continues to make big improvements here.
Btw, the explicit src/lib/index.js reference is needed to support NodeNext packages (see: https://github.com/techniq/svelte-ux/issues/280) and was handled in https://github.com/techniq/svelte-ux/pull/281

And yes, let's talk more if you ever decide to use Kitbook. There's a some glaring features missing from it like view source code which would be almost trivial to add as I have the raw strings from each component already, I just haven't taken the time to do it. 1 thing at a time you know. But it sure would make it easier for you in some spots like how you're writing your getting started page in html, not markdown.

That sounds great and I would love to see where each project can learn from one another.  I rolled my own docs mostly because I wanted more control over the experience than I could get from other solutions at the time, but it's not without it's own challenges.  I have an issue to track some of my ideas on how to improve the docs if you want to see where my head is.  Documentation, types, accessibility, and internationalization are always areas that could be improved (along with making great functioning libraries 😁).
Most of the docs were in markdown originally (mdsvex with some extra processing) but I encountered challenges with working in markdown with Svelte code examples that outweighed the ergonomic benefits, but some of these are probably from my own ignorance 🤣.  I ended up re-writing most back to regular old Svelte files.  See the docs issue for more context, but a few of the issues were

Type checking
Prettier formatting
Cryptic compile-time errors

Oh, and Kitbook has no dark mode support or any theme for that matter and you've blown it out of the water. So that's another thing you might want to see in Kitbook first. Not sure what's important to you.

Theming is very important, although it's also kind of specific to the implementation.  Ultimately it's leveraging Tailwind classes driven by CSS variables and LayerChart's docs are powered by Svelte UX's theming (which is a Tailwind plugin).  LayerChart isn't tied to Svelte UX in general (works with other frameworks like Skeleton or shadcn-svelte, or even standalone) but I do treat it as a companion library that complements one another.
Personally I would love to piecemeal some of the capability of kitbook (similar to how I leverage sveld ATM) to handle some of the challenging aspects but it might be difficult to fully replace the docs (at least in the relative near future).
Speaking of sveld, I use it to parse Svelte props/etc which works OK at best, but struggles more times with Typscript only types unless I also add JSDoc comments (and I really want Typescript to be the source of truth and not have to "double define").  If you have a solution here I would love to hear it :).  I'm also looking to document non-components such as Svelte stores (at least until they are converted to runes), actions, and utils.  These are mostly a Svelte UX need, although there are a few in LayerChart as well (some of which are undocumented at this time).
Thanks again for the PR and I would love to proceed with using the alias (and hopefully we don't hit any performance bottlenecks).  Svelte UX is going to be the true test 😁

@jacob-8 Thanks so much for starting this effort.  I finished it in https://github.com/techniq/layerchart/pull/192


Add -p flag from go build

Limits the number of parallel builds.

Have you tried the custom flag -parallelpackages?
gotestcover runs the go test command with only one package (the go test command doesn't support coverage with multiple packages).
The custom flag -parallelpackages controls the number of parallel executions:
https://github.com/pierrre/gotestcover/blob/master/gotestcover.go#L117-L129
The default value is GOMAXPROCS.
Do you think I should add the -p flag and alias it to -parallelpackages?
Should I deprecate -parallelpackages?
Many flags from go build are not supported in gotestcover.
Do you know a way to forward flags?


OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv3 read finished A: sslv3 alert certificate unknown

I am getting below error when try to send the push notifications, its working fine couple of times but when I tried after some time its not working:

OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv3 read finished A: sslv3 alert certificate unknown
Please suggest how can I fixed that issue. My app is hosted on heroku.
Thanks

Is your certificate active?


Retrieve Specmatic Text Error Messages for setExpectationJson

What: Retrieve Specmatic Text Error Messages for setExpectationJson
Why: Since Specmatic returns error messages in text format, retrieving detailed error information from _specmatic/expectations in the setExpectationJson method has been challenging. Previously, only the error code was captured, making it difficult to identify which fields were incorrect or missing according to the OpenAPI specifications. This update addresses the issue by capturing and logging the full text error message, enabling more precise troubleshooting.
How: Added error handling to return error message also along with error code.
Checklist:

[ ] Documentation added to the README.md
[X] Tests
[ ] Typescript definitions updated
[X] Ready to be merged

Screenshot:

It will be very helpful if we get error message also in console when running consumer driven contract tests.

@harikrishnan83 pranavgawri
can you pls review this request

@harikrishnan83 @StarKhan6368 Reminder !! Could you please review this PR

@harikrishnan83 @StarKhan6368 Reminder !! Could you please review this PR

Done, @StarKhan6368 and I reviewed it. Looks good to us except for a minor comment. Kindly have a look and address the same so that we can go ahead merge it. Thanks.

@harikrishnan83 Addressed your review comment, Thanks !!

@harikrishnan83 One quick question, when are these changes published as new npm version?

@harikrishnan83 One quick question, when are these changes published as new npm version?

We will be putting a out a release this week. Your changes will be part of the same. Thanks.

@Rajaneeshkumar your changes are part of release 2.0.38. Thanks.

@Rajaneeshkumar your changes are part of release 2.0.38. Thanks.

Just a quick doubt — generally, aren't changes typically mentioned under the What's Changed section?

@Rajaneeshkumar your changes are part of release 2.0.38. Thanks.

Sorry to disturb, Just a quick doubt — generally, aren't changes typically mentioned under the What's Changed section?

Good point, thanks for highlighting it. I have updated the release notes.


Allow setting of path

I am currently receiving the error:
error while loading shared libraries: libjvm.so: cannot open shared object file: No such file or directory

I understand I can manually set an LD_LIBRARY_PATH to prevent that, however this is burdensome for developers. I would much prefer to:
    if env::var("LD_LIBRARY_PATH").is_err() {
        if let Ok(path) = which("java") {
            let lib = path.canonicalize().unwrap().parent().unwrap().parent().unwrap().join("lib").join("server");
            println!("lib={}", lib.display());
            env::set_var("LD_LIBRARY_PATH", lib);
        }
    }

But even when I call that code as the first line of my test, I see I get the error before my code gets hit. Is it possible fs-hdfs3 is trying to load libraries in a lazy_static block or something? Is there another option for me to make this zero-setup for the devs on my team?
Thanks!

The dependent path may vary on different OS. Therefore, I prefer to set it manually rather than in code.


feat: filter messages by dates (if provided)

Resolves #609
Duplicates/replaces #639
In this PR:

Filter messages by goLiveDate and expireDate if dates are provided
If no dates provided, show the messages
Break up some logic for the sake of separation of concerns

Contributor License Agreement adherence:

[x] This Contribution is under the terms of Individual Contributor License Agreements (and also Corporate Contributor License Agreements to the extent applicable) appearing in the Apereo CLA roster.

Closing due to duplication


New Feature Request: Add Shopify event to past events

Request
Let's add Shopify event to past events
https://event.webinarjam.com/register/25/py524cxx
URL(s)
https://techqueria.org/past-events
Why did you make this request?
All past events should be reflected

@FrancesCoronel when did this event happen? Can't seem to find that info on https://event.webinarjam.com/register/25/py524cxx

Friday, April 24, 2020
Time: 3 PM - 4 PM PT


clear error output from notebook cell

Why are these changes needed?
Related issue number (if any).

LGTM


Viscosity

Tracking issue for supporting evolution of the Extended GRMHD equations of Chandra+ 2015.
This would be a foundation for any scheme requiring implicit per-zone solution of a system, e.g. moment-base radiation.

[x] Batched linear forward solve using kokkos-kernels, performance prototype
[x] Nonlinear solve
[x] Automated Jacobian construction
[x] New tests from Chandra+ 2017 test suite
[x] Performance optimizations: index reordering for locality, nested parallelism, etc.

Feel free to add tasks & discuss here, also see #10 for implementation PR & discussion.

Remaining work toward viscous runs with KHARMA for 2022:

[] EMHD shock test
[] Hydrostatic conducting atmosphere
[] Viscous Bondi flow
[] Full Fishbone-Moncrief torus

Remaning features:

[] EMHD signal speed/timestep calculation
[] Normalization of residuals
[] Closure terms for new problems, including torus

I'm going to close this issue, as all the features it tracked are in place, pending separate bug-fixes.  Those should either be solved soon, or opened as a separate issue.


added MAPE metric

Added 3 time series specific metrics...

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Hi @kashif, thanks for adding this - the implementation looks great! There seems to be an issue with the example in the docstring, maybe rounding the results would help.
Also, could you add a requirements.txt and README.md? You can for example look at metrics/accuracy for how to add those!
Let me know if you need any help!

thanks @lvwerra let me fix it!

@lvwerra would be happy for another review

the tests seems to be failing due to something else I believe


When using BrowserCompatible, BigDecimal in the Double range behaves the same as Double. for issue #3123

What this PR does / why we need it?
Summary of your change
public static boolean isJavaScriptSupport(BigDecimal decimal) {
        boolean jsSupport = decimal.precision() < 16 || isJavaScriptSupport(decimal.unscaledValue());
        if (!jsSupport && decimal.scale() != 0) {
            //Use double for comparison
            //double and javascript number have the same precision
            //In extreme cases, precision loss may occur.
            //There will be a loss of precision between [4.9e-324, 5e-324), which will be converted to 5e-324 by JavaScript.
            //This situation can be ignored
            double doubleValue;
            try {
                doubleValue = decimal.doubleValue();
            } catch (Exception ex) {
                return false;
            }
            jsSupport = decimal.compareTo(BigDecimal.valueOf(doubleValue)) == 0;
        }
        return jsSupport;
    }

Please indicate you've done the following:

[x] Made sure tests are passing and test coverage is added if needed.
[x] Made sure commit message follow the rule of Conventional Commits specification.
[x] Considered the docs impact and opened a new docs issue or PR with docs changes if needed.

这个没解决Double输出的问题吧

这个没解决Double输出的问题吧

double 和 javascript 的 Number 范围相似，只有在±[4.9e-324, 5e-324)范围内会被转为±5e-324，这种情况可以忽略了


Debug: on stop the current line is not read out

Environment Details:
VSCode Version : 1.25.0
OS Version : Win10
Additional Details:
NVDA,MAS1.3.1
Repro Steps:
1.Launch Visual Studio code desktop application.
2.Navigate to "Plain Text" of "StatusBar"->Enter "PowerShell" in "Select Language Mode"combobox->Write the PowerShell Code in plain editor->Save the editor.
3.Write powershell code in the editor screen
4.Apply the breakpoint in editor using F9
5.Press F5 to start debugging.
6.Press F11 to stepinto the code of editor.
7.Observed that when the user press F11 to step into then nvda is not reading data.
Actual:
When user uses F11 to step into code then nvda is reading it as "Debugging Paused,reason step untitled-2.ps1 7"
eg if Invoke-Retestmethode is selected then nvda is reading it as "Debugging Paused,reason step untitled-2.ps1 7" but not reading text i.e "Invoke-Retestmethode "
Expected:
When user uses F11 to step into code then nvda should read the selected data text.
Recommendations:
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/Pages/browse-fixes.aspx
User Impact:
If the nvda is not announcing the selected data then user will not understand on which function the keyboard focus stepinto.
MAS Reference:
MAS1.3.1-https://microsoft.sharepoint.com/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}
Attachment For Reference:
[Accessibility]A11y_PowerShellEditorServices_Editor_Screenreader.pptx
Does this issue occur when all extensions are disabled?: Yes

Works fine in latest

Currently when the debugger stops we only read out that it stop on a line number something .
Assigning to may to fix then.

Adding bug so we verify.
Verifier: make sure that when you are debugging and you step or the program stops that we read out the content on the stopped line
fyi @neurrone for possible feedback


selenium.common.exceptions.WebDriverException

What version of selenium driver you test your script with?
I keep getting Element  is not clickable at point (113, 592)

I was using the latest version of selenium python driver. However,  an issue has been reported that the script is no longer work for the updated Front-end Master UI.
https://github.com/li-xinyang/OS_FrontendMaster-dl/issues/10

The script is updated. Please try again. Thanks


Remove usage of runBlocking from AbstractArcHost

Turns out this was fairly straightforward, all usages of methods
containing a runBlocking were already called from a coroutine.

One more cl to unblock this: cl/331616675


feat(api): add register static method #45

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves: #45
Summary:

AuroDatetime.register is to easily register the element without extra importing
import "@aurodesignsystem/auro-datetime" will still register this element to
import { AuroDatetime } from<EMAIL_ADDRESS>wont register this element until AuroDatetime.register gets called
Fixed the typo on Recommended Use and Version Control. clement -> element

Type of change:
Please delete options that are not relevant.

[x] New capability
[ ] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team
Summary by Sourcery
Add a static method 'AuroDatetime.register' for manual element registration and update documentation to reflect this change, including a typo correction. Update the build configuration to include demo index examples.
New Features:

Introduce a static method 'AuroDatetime.register' to allow manual registration of the auro-datetime element.

Bug Fixes:

Correct a typo in the documentation from 'clement' to 'element'.

Build:

Add a new Rollup configuration for building demo index examples.

Documentation:

Update documentation to reflect the new 'AuroDatetime.register' method and correct a typo.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Interrupted downloads are not detected properly

While downloading a file, if the connection gets interrupted, it seems that java.net.HttpURLConnection doesn't report an error (I'd like to come up with a reproducible test for that… - I consistently ran into that at work…). okhttp is fine on the other hand, throwing if it can't read the whole response body.
Incomplete files can end up in the cache because of that…
Enabling okhttp by default should address that (needs Java >= 7 IIRC).

Thanks @alexarchambault. Mark as related to #780

Now that Java 8 is required, the okhttp module could be added to the sbt plugin and the cli by default to address that (it wasn't because it needed Java >= 7).

Related to https://github.com/scalameta/metals/issues/647

Fixed by https://github.com/coursier/coursier/pull/1273 (with a manual check of Content-Length).


feat(TFD-582): Add a REST endpoint to compute dependencies.

Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)

What is the current behavior? (You can also link to an open issue here)
Add an endpoint in order to retrieve the (maven) dependencies of any Definition (Components, Datastore or Dataset)
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:

Pull request test result: failure :x:

I am closing this PR in order to get a build by creating a new one.


Create the Layout for Training and Grooming HTMLs

Match the HTML layout to the wireframe created.

Completed the layout for both pages as they will house similar content.


"panzoompan" fires when not zoomed and panOnlyWhenZoomed is true

Describe the bug
Set panOnlyWhenZoomed to true. Don't zoom but try to pan and drag over image. "panzoompan" will be fired even if not actually panning.
Your environment

Version of panzoom: 4.4.2
Browser and browser version: Chrome Version 94.0.4606.71 (Official Build) (64-bit)

Expected behavior
Don't fire event if not actually panning.
Steps to reproduce
https://jsfiddle.net/viseshrp/zjwuLfy8/5/

Thanks for opening an issue. Looks like a bug.


Adjust count check

Currently if you have a count of 0, it returns the singular version.
eg. 0 entry, where it should be 0 entries.
Now only a count of 1 gets the singular version.

All good! Travis is happy, and we are all happy.


Automatically determine dimensionality of input data stream.

For graphing. Not sure how to do this.

Fixed by https://github.com/damellis/sensors/commit/fc4dc11a57f46edbf7d7c18b6fa4ea9ab920e2fe
(This still requires the user to specify the number of dimensions in some cases, specifically w/ ASCIISerialStream.)


Great work! How can I only reconstruct face domain without background?

As the title.

Hi!
Thanks for your attention.
Unfortunately, I did not address the background separation in Dr.3D.
I think you can consider some work of separating background from foreground such as NeRF++, MipNeRF360, DreamFusion, PanoHead and so on.


DBZ-2408 Fix build errors with oracle documentation

https://issues.redhat.com/browse/DBZ-2408
This PR fixes a 2 mistakes when doing prior backports of commits to the 1.1 branch for the Oracle.  This should resolve the warnings the documentation build gets when pulling in branch 1.1.

Thx!


Update Linux requirements

Glibc 2.26+ (we use 2.35) require Linux kernel 3.2 or later - see https://sourceware.org/pipermail/libc-announce/2017/000017.html.
Remove GCC requirement given I don't think it matters for bottles (we install GCC ourselves if too old) and is probably wrong for the build-from-source case.

Everything besides glibc is relocatable, with that now supporting it's own bootstrapped GCC.
For non-x86_64 platforms which don't use the bootstrap, the minimum GCC is 6.2.
Given this, we could remove compiler support for < GCC 6 from brew, though we perhaps want to wait until the end of the gcc@5 deprecation period, which is no earlier than 9th December.

Remove libxcrypt-compat requirement given we don't use libcrypt.so.1 anymore.

Review period will end on 2022-10-18 at 00:00:00 UTC.

We will also want a corresponding change to the glibc formula which currently requires the 2.6.32 but should require 3.2 as noted here.  It's a trivial syntax only change so no changes to the bottle are needed.

Yeah that probably should just pick up OS::Linux::Kernel.minimum_version.

Given this, we could remove compiler support for < GCC 6 from brew, though we perhaps want to wait until the end of the gcc@5 deprecation period, which is no earlier than 9th December.

I'm fine with deprecating this in brew nowish (or at least: next major/minor release).

Yeah that probably should just pick up OS::Linux::Kernel.minimum_version (though this is currently private API).

Fine with me to make this public 👍🏻

Or maybe flip it so we can extract it the other way round somehow given this version is tied to the version of glibc we ship.

Also fine with me 👍🏻

Review period ended.


Missing ability to list/discover extensions on object (e.g. email message)

https://graph.microsoft.com/v1.0/users/{{userId}}/messages/{{messageId}}/extensions throws ErrorInvalidRequest.
https://graph.microsoft.com/v1.0/users/{{userId}}/messages/{{messageId}}?$expand=extensions throws ErrorGraphExtensionExpandRequiresFilter, and the only acceptable filter seems to be of the form Id eq {{extensionId}}. (This restriction doesn't seem to be documented anywhere.)
This makes it impossible for an application to list or discover extensions on an object.
If bandwidth usage is a concern, hopefully something like https://graph.microsoft.com/v1.0/users/{{userId}}/messages/{{messageId}}/extensions?$select=Id or https://graph.microsoft.com/v1.0/users/{{userId}}/messages/{{messageId}}?$expand=extensions($select=Id) could be an acceptable solution.

Thanks for raising this @Googulator
As this repo is mainly intended for metadata related issues, any chance you can create a request at the link below to give feedback for the API owners?
https://aka.ms/graphfeedback

Submitted https://feedbackportal.microsoft.com/feedback/idea/54ed3b01-3f14-ef11-989a-6045bdbb573a on the subject.


Improved UI Experience for Hundreds of Tables or Column

@iampiyush can you please look into this?

Once we implement search/auto-complete for Features ... use it here too.

Closing and waiting for customer feedback.


Players with high ping get falsely accused a lot

This player had over 300 ping when this happened

I've also seen it happen with timer hacks in the past.
Also I'm not sure if this player is actually hacking. It seems pretty sus that this all happened in the span of 1 second. However, with the timer hacks, it was confirmed that the player wasn't hacking. (mightve been fixed tho)

Timer hack is disabled atm, that's why it isn't throwing any detections :) ...
Thanks for reporting. I see I'll have to do more testing with clumsy.


NIFI-604: Custom Argument Delimiters ExecuteStreamCommand / ExecuteProcess

Unified the way ExecuteStreamCommand and ExecuteProcess handle arguments. This enables
the ExecuteStreamCommand to use semicolons as part of arguments.

Argument delimiters can now be specified. Their default being what they were using before (ExecuteStreamCommand -> ';' , ExecuteProcess -> ' ')

There's one thing I would like to call attention to. Users of the StreamCommand who were using \n \r or \t characters outside of quotes might have unexpected results since the ExecuteProcess command used those as delimiters in addition to the space delimiter. It's doubtful that a lot of people were doing this, but it's something to consider.
One option is to have a "Use Default Delimiters" checkbox that's enabled by default on the ExecuteProcess and disabled by default on the ExecuteStreamCommand.


Rancher agent not connecting to Rancher server on same host with "Custom" Add Host

I am running Rancher server in the provided container on DigitalOcean (exposing 8080) and the admin seems to work fine.  My firewall rules seems reasonable:
$ sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
OpenSSH                    ALLOW       Anywhere
80/tcp                     ALLOW       Anywhere
2376/tcp                   ALLOW       Anywhere
3376/tcp                   ALLOW       Anywhere
500/udp                    ALLOW       Anywhere
4500/udp                   ALLOW       Anywhere
OpenSSH (v6)               ALLOW       Anywhere (v6)
80/tcp (v6)                ALLOW       Anywhere (v6)
2376/tcp (v6)              ALLOW       Anywhere (v6)
3376/tcp (v6)              ALLOW       Anywhere (v6)
500/udp (v6)               ALLOW       Anywhere (v6)
4500/udp (v6)              ALLOW       Anywhere (v6)

But when I want to add the same host, as an agent, it hangs on attempting to connect to the master.
I click through the admin interface for "custom", and it tells me to do:
$ docker run -d --privileged -v /var/run/docker.sock:/var/run/docker.sock rancher/agent:v0.7.11 http://<ip>:8080/v1/scripts/328B791E15E99D370F1D:1438639200000:8aQ7dtSOvfPpOLb1OzuWIMsOKoQ

When I run that locally, I get logs in the container like:
INFO: Running Agent Registration Process, CATTLE_URL=<ip>:8080/v1
INFO: Checking for Docker version >= 1.6.0
INFO: Found Server version: 1.7.1
INFO: docker version: Client version: 1.6.0
INFO: docker version: Client API version: 1.18
INFO: docker version: Go version (client): go1.4.2
INFO: docker version: Git commit (client): 4749651
INFO: docker version: OS/Arch (client): linux/amd64
INFO: docker version: Server version: 1.7.1
INFO: docker version: Server API version: 1.19
INFO: docker version: Go version (server): go1.4.2
INFO: docker version: Git commit (server): 786b29d
INFO: docker version: OS/Arch (server): linux/amd64
INFO: docker info: Containers: 6
INFO: docker info: Images: 46
INFO: docker info: Storage Driver: aufs
INFO: docker info: Root Dir: /var/lib/docker/aufs
INFO: docker info: Backing Filesystem: extfs
INFO: docker info: Dirs: 58
INFO: docker info: Dirperm1 Supported: false
INFO: docker info: Execution Driver: native-0.2
INFO: docker info: Kernel Version: 3.13.0-57-generic
INFO: docker info: Operating System: Ubuntu 14.04.2 LTS
INFO: docker info: CPUs: 2
INFO: docker info: Total Memory: 1.955 GiB
INFO: docker info: Name: beefydrop
INFO: docker info: ID: AG5H:ECGI:PIYD:HJO4:S7FY:WBPC:YWSB:YJ2H:FGO2:6A5I:7TGR:IHXE
INFO: docker info: Http Proxy:
INFO: docker info: Https Proxy:
INFO: docker info: No Proxy:
WARNING: No swap limit support
INFO: docker info: Labels:
INFO: docker info: provider=digitalocean
INFO: Attempting to connect to: http://<ip>:8080/v1
WARNING: No swap limit support
ERROR: http://<ip>:8080/v1 is not accessible

I managed to add another host fine.  What's going on?  Other issues (https://github.com/rancher/rancher/issues/872) suggested -e CATTLE_AGENT_IP=<ip>, but that didn't work for me.

If you are SSH'd into the host, is curl -i http://<IP_ADDRESS>:8080/v1 working?

Looking into it @nathanleclaire

Ok, I reproduced and adding ufw allow 8080/tcp to the firewall rules fixed the problem.
The questionable thing was why were you able to get to the UI/API via the browser. Long story short, the iptables rule that was created when you did docker run ip 8080:8080 ... was taking allowing external traffic in, but not internal traffic. Internal traffic was being blocked by ufw.

I closed, by actually I leave open for awhile to give @nathanleclaire a chance to confirm adding that ufw rule fixed his problem.

The questionable thing was why were you able to get to the UI/API via the browser. Long story short, the iptables rule that was created when you did docker run ip 8080:8080 ... was allowing external traffic in, but not internal traffic. Internal traffic was being blocked by ufw.

Ah yes.  I am not sure the exact iptables magic Docker is doing behind the scenes, but I am pretty sure it will happily punch a hole through your firewall to expose the port to outside when you do -p port:port.
I'll add another rule and confirm when it works for me!

It works, thanks @cjellick !

Please reopen this case.
I've created a new EC2 instance using this ami ID on AWS EC2: rancheros-v0.4.2-hvm-0 (ami-53045239). After the instance is reachable through ssh, I've setup the rancher server container on it using this command:
[root@ip-172-30-2-89 ~]# docker run -d --name=rancher-server --restart=always -p 8080:8080 rancher/server

After the rancher server's container is running, I've installed a nginx container for proxy requests on HTTPs/443 to 8080 of rancher server's container:
mkdir -p /opt/nginx/ssl

cat <<EOF> /opt/nginx/rancher.conf
upstream rancher {
    server rancher-server:8080;
}

server {
    listen 443 ssl;
    server_name ranchermgmt.mydomain.com;
    ssl_certificate /etc/nginx/ssl/ranchermgmt.mydomain.com.crt;
    ssl_certificate_key /etc/nginx/ssl/ranchermgmt.mydomain.com.key;

    location / {
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Port $server_port;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass http://rancher;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

server {
    listen 80;
    server_name ranchermgmt.mydomain.com;
    return 301 https://$server_name$request_uri;
}

EOF

docker run -d -p 80:80 -p 443:443 -v /opt/nginx/ssl:/etc/nginx/ssl/:ro -v /opt/nginx/rancher.conf:/etc/nginx/conf.d/rancher.conf:ro --link='rancher-server' nginx

With these two containers running, I was able to connect to https://ranchermgmt.mydomain.com using SSL/443 with my own certificate using any browser.
Very well, now I want to add this EC2 instance as a host to the rancher server container that is running inside it. For doing it, I've first enabled a local authentication on rancher server, by using it's web ui. After that, I've did the procedure described here: http://docs.rancher.com/rancher/rancher-ui/infrastructure/hosts/custom/#adding-hosts-to-the-same-machine-as-rancher-server, but the procedure not works.
 But, even using iptables directly, I think it isn't necessary because iptables INPUT Chain in openned by default:
[root@ip-172-30-2-89 ~]# iptables  -L -n -v
Chain INPUT (policy ACCEPT 18960 packets, 170M bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination
 165K   42M DOCKER     all  --  *      docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
82471   35M ACCEPT     all  --  *      docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ctstate RELATED,ESTABLISHED
 160K   33M ACCEPT     all  --  docker0 !docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
  242 14520 ACCEPT     all  --  docker0 docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
    0     0 DOCKER     all  --  *      docker-sys  <IP_ADDRESS>/0            <IP_ADDRESS>/0
    0     0 ACCEPT     all  --  *      docker-sys  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ctstate RELATED,ESTABLISHED
    0     0 ACCEPT     all  --  docker-sys !docker-sys  <IP_ADDRESS>/0            <IP_ADDRESS>/0
    0     0 ACCEPT     all  --  docker-sys docker-sys  <IP_ADDRESS>/0            <IP_ADDRESS>/0

Chain OUTPUT (policy ACCEPT 13561 packets, 1958K bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain DOCKER (2 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 ACCEPT     tcp  --  !docker0 docker0  <IP_ADDRESS>/0            <IP_ADDRESS>           tcp dpt:8080
81865 6789K ACCEPT     tcp  --  !docker0 docker0  <IP_ADDRESS>/0            <IP_ADDRESS>           tcp dpt:443
   29  1638 ACCEPT     tcp  --  !docker0 docker0  <IP_ADDRESS>/0            <IP_ADDRESS>           tcp dpt:80

[root@ip-172-30-2-89 ~]# iptables  -L -n -v -t nat
Chain PREROUTING (policy ACCEPT 29173 packets, 2004K bytes)
 pkts bytes target     prot opt in     out     source               destination
11311  678K DOCKER     all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match dst-type LOCAL

Chain INPUT (policy ACCEPT 8 packets, 424 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 307 packets, 23653 bytes)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DOCKER     all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match dst-type LOCAL

Chain POSTROUTING (policy ACCEPT 11828 packets, 715K bytes)
 pkts bytes target     prot opt in     out     source               destination
    0     0 MASQUERADE  all  --  *      docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match src-type LOCAL
28964 1992K MASQUERADE  all  --  *      !docker0  <IP_ADDRESS>/16        <IP_ADDRESS>/0
    0     0 MASQUERADE  all  --  *      docker-sys  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match src-type LOCAL
    0     0 MASQUERADE  all  --  *      !docker-sys  <IP_ADDRESS>/16        <IP_ADDRESS>/0
    0     0 MASQUERADE  tcp  --  *      *       <IP_ADDRESS>           <IP_ADDRESS>           tcp dpt:8080
    0     0 MASQUERADE  tcp  --  *      *       <IP_ADDRESS>           <IP_ADDRESS>           tcp dpt:443
    0     0 MASQUERADE  tcp  --  *      *       <IP_ADDRESS>           <IP_ADDRESS>           tcp dpt:80

Chain DOCKER (2 references)
 pkts bytes target     prot opt in     out     source               destination
    3   180 DNAT       tcp  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            tcp dpt:8080 to:<IP_ADDRESS>:8080
11275  677K DNAT       tcp  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            tcp dpt:443 to:<IP_ADDRESS>:443
    8   380 DNAT       tcp  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            tcp dpt:80 to:<IP_ADDRESS>:80

I need a solution for this if possible....

I've fixed! The problem is with my certificate. In the server logs, these messages where being displayed every second:
time="2016-01-06T11:24:23Z" level=fatal msg="Unable to create event router" error="Get https://ranchermgmt.socialbase.com.br/v1: x509: certificate signed by unknown authority"
time="2016-01-06T11:24:24Z" level=info msg="Setting log level" logLevel=info
After correcting the certificate issue, restarting the server, go to UI, adding a host again and re-run the agent with this command, the issue was fixed:
docker run -e CATTLE_AGENT_IP=<IP_ADDRESS> -d --privileged -v /var/run/docker.sock:/var/run/docker.sock rancher/agent:v0.8.2 https://ranchermgmt.socialbase.com.br/v1/scripts/11A1DA6CF21B26A360AF:1452078000000:QD6RuI30vvfrzRiMlvJk0T4k

ufw allow 8080/tcp fixed it for me

@galindro , I see the same error. Tell me, please, what was wrong with your certificate?

@soundman666 the problem is that I didn't included the intermediate chain on the certificate file.

@galindro Thank you very much. This is it!

run into the same issue, i think an environment variable for the agent to ignore ssl errors would be great

@MichaelErmer Are you trying to run rancher-server with SSL? If so, how would ignoring the errors help?  Wouldn't that prevent Rancher to be able to run SSL?

My server is running behind an nginx that does the SSL, the nodes are connecting trough said nginx as well, however there might be an intermediate chain missing on nginx which is no problem for chrome/firefox etc. but it seems to prevent the agent from connecting to the server.

NVM, sorry the problem was my nginx not upgrading websockets properly

I have also some problems with the local host... Can't add it any way I tried (cattle ip, revproxy, unmodified, ...). Other hosts work fine!

@pwFoo What version of Docker are you running and on what type of OS?

RancherOS 0.4.5 on each host.

@pwFoo What is your host registration URL?

Hello @deniseschannon ,
I changed my setup and image back to latest instead of stable. Add hosts work fine again, but there is still a problem with the Rancher LBs at the host with also Rancher Server running (different issue)
I tested all possible registration urls (public ip, private ip, installed an revproxy between, cattle ip added, ...), but it doesn't work (again) in my old setup. Initial host add works fine, but I removed (because of the LB problem) and added it again without success.
With my new setup I use private ip addresses and added an openvpn service between the hosts. That works. But all hosts were reachable in the old setup too! It wasn't an network issue.
So the problem is solved for me at the moment.


Link to document no longer being updated

https://docs.microsoft.com/en-us/archive/blogs/sqlcat/migrating-from-sql-server-to-azure-sql-database-using-bacpac-files
Heading of the document at this link is : We're no longer updating this content regularly. Check the Microsoft Product Lifecycle for information about how this product, service, technology, or API is supported.
Not seeing the value of this.

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

ID: 5c0b8c1d-41ff-f7ab-bc23-72a48fc46e1e
Version Independent ID: dfb8cad9-6233-f97f-c849-1820ad642c7c
Content: Export an Azure SQL Database to a BACPAC file (the Azure portal) - Azure SQL Database & Azure SQL Managed Instance
Content Source: articles/azure-sql/database/database-export.md
Service: sql-db-mi
Sub-service: data-movement
GitHub Login: @stevestein
Microsoft Alias: sstein

@langstonj We are checking this and will get back to you.

@langstonj Can you please confirm what you mean by the you are not seeing value for this. Please elaborate for us.

@langstonj Please help with this info to work further on this,

In searching for current topic information I will follow listed links.  When getting over to the page for this one one in question there was a notation at the top of the page that the material was no longer being maintained (rather than being kept up-to-date).

@langstonj These are blog archives so the messaging in this way. You can check these docs for more details -https://docs.microsoft.com/en-us/azure/azure-sql/database/database-import?tabs=azure-powershell

@langstonj Please let me know if you need further info.


Add Velammal Bodhi Campus

Velammal Bodhi Campus

@xts-velkumars Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

@xts-velkumars You might miss my previous comment. Please react.

@xts-velkumars I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


feat: rework useTransition

⚠ More testing required. Weird behavior probably exists.
This PR is a rewrite of useTransition from scratch in hopes of simplifying both the API and the internals. Here's an example of the new API:
import {animated, useTransition} from 'react-spring'
const MyComponent = ({ items, ...props }) => {
  const transition = useTransition(items, props)
  return transition((values, item) => (
    <animated.div style={values}>{item}</animated.div>
  ))
}

Once #670 is merged, you can pass a deps array and you'll get the set and cancel functions returned to you:
const [transition, set, cancel] = useTransition(items, props, [...deps])

Notable changes

No more keys argument
Returns a transition function instead of a transitions array

Pass a render function to it and you'll get the animated values for each item
The element you return has its key prop set for you automatically

Now safe to use in concurrent mode
Unique mode is the new default (and the unique prop was removed for simplification)
Items are now ordered based on when they were last added, instead of trying to find old siblings of deleted items. Note: When an item is re-added before its leave transition finishes, the item has its position preserved.
Lazy mode is the new default (and the lazy prop was removed in favor of expires)
Event props cannot be passed directly (eg: props.onFrame), but you can still pass them in specific phases (eg: props.enter.onFrame)
The reset prop now uses the initial prop if it exists
The onDestroyed prop was removed (was there a good use case for this?)

New expires prop
For controlling when deleted items are dismounted after their leave animation finishes. Set to 0 for immediate dismount. By default, they avoid dismounting until all transitions are resting. Any value above 0 is treated as "milliseconds to wait before dismounting is forced".

Notes

We need a demo that uses z-index to overcome the lack of DOM order guarantee.
Currently, "expired" transitions are dismounted whenever the component re-renders, even if other controllers are still animating. Is this good or bad? 🤔


Request hangs if ReasonPhrase contains new line character

This sample code demonstrates the issue
public class Program
{
    private static void Main()
    {
        using (var host = new NancyHost(new Uri(...),
                                        new DefaultNancyBootstrapper(),
                                        new HostConfiguration {UrlReservations = new UrlReservations {CreateAutomatically = true}}))
        {
            host.Start();
            Console.ReadLine();
        }
    }
}

public class Module : NancyModule
{
    public Module()
    {
        Get["/"] = _ => Negotiate.WithStatusCode(HttpStatusCode.BadRequest)
                                 .WithReasonPhrase("\n");
    }
}

packages.config
<packages>
  <package id="Nancy" version="0.23.2" targetFramework="net45" />
  <package id="Nancy.Hosting.Self" version="0.23.2" targetFramework="net45" />
</packages>

@grumpydev https://github.com/NancyFx/Nancy/issues/1630#issuecomment-50317407 =) Close ?

No one else has reported this issue and this issue seems dead. If not putting the new line doesn't cause it to hang then we shouldn't worry about trying to handle a deviation of the specification. IMO.
Closing for now.

+1 FWIW 😊


Fix verification_HitsChargeTime.C

Three remarks on the script verification_HitsChargeTime.C:

This one is a fairly straightforward bug:
In line 227, the for loop should do nevents2 iterations (which is the number of events in the 2nd root file), instead of nevents iterations (which is the number of events in the 1st file). In particular, if the second root file contains fewer events than the first one, this will cause an interpreter error.

I’m not quite sure about this one:
The for loop starting on line 246 iterates over the subevents of a given superevent. It calculates the average hit time and charge (in line 267/268), but they are added to the histograms only after that for loop. I.e. if an event has multiple subevents, only the average hit time and charge of the final subevent are added to the histograms.
This should probably be fixed by moving the curly bracket from line 269 to after line 271 — unless I’m missing something?

This one just seems weird to me:
Line 261:
int tubeNumber     =  (wcsimrootcherenkovdigihit->GetT(),wcsimrootcherenkovdigihit->GetTubeId());
This code gets the hit time, discards it(?) and then assigns the TubeID to a variable which is not actually used anywhere. Does this code have some sort of useful side effect that I’m missing? I couldn’t find any hints what this might have been used for in the commit history.

I’ll submit a pull request for 1. shortly. Regarding 2. and 3., I’d like to wait for comments before I change/remove the code.
(Also, note that 2. and 3. apply equally to lines 144 and 160.)

One more thing to note regarding 2. is that the loop variable index is never actually used inside the loop, so each iteration adds up the charge/time of the first sub-event. It seems that this is done right in sample_readfile.C, so I fixed this accordingly in my PR.

Regarding 3., after thinking about it a few more times, it seems most likely to me that this is simply an artefact and was copied over from another sample root file. I have removed both lines in my PR.

Closed after merging #170


Wrong [Estimated time left] of a normal withdrawal

[Estimated time left] should be about 7 days

The bug is caused by the wrong time display format. Originally we didn't think we were going to change the block_finality to 7 days, so the estimated time left is only displayed up to "minutes".
The issue should be fixed in this PR:

https://github.com/nervosnetwork/light-godwoken/pull/169


NBT encoding

Are these files encoded with a custom NBT format?
It looks like the name and string length values are stored in a byte instead of 16 bits.
Are they varints?
I haven't seen this format before and our (Amulet) nbt parser can't open it.

The format is described here: https://github.com/pmmp/BedrockBlockPaletteArchive#file-format

That doesn't mention that it is a custom NBT format other than a series of compound tags.
I did a little more digging and found the BedrockData readme that mentions it is a varint format like I thought. I assume this is a format you created since I haven't seen this anywhere else.
https://github.com/pmmp/BedrockData#canonical_block_statesnbt

That would be useful. I should look into your tools as they would make it much easier to programmatically extract the data we need.
Up to now I have been using the private betas to generate the palette but that is only useful if the palette is the same as the full release.

I recommend taking a look at this repository if you're interested in extracting this data from release binaries: https://github.com/pmmp/bds-mod-workspace
The tools in here work on both private partner builds and public release builds.

I've updated the README with details on the format differences: https://github.com/pmmp/BedrockBlockPaletteArchive/commit/a445f4ad86f4e5267e1ed2465ec306ec78a3091d

thanks


[RuntimeError]

Is your feature request related to a problem? Please describe.
RuntimeError: CUDA error: an illegal memory access was encountered
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.
Solutions
我仅仅是 让这个模型一直运行，没有存储历史数据，用了两张卡来运行的。怎么解决？
Additional context
No response

mark , same problem , have you find a solution ? @Dhaizei


Make TAP reporter TAP13-capable

Description of the Change
The TAP reporter has been made to conform with TAP13.
Changes to the actual reporter are small: a version string is emitted as the first line, and error message and stack are both emitted inside a YAML block to be parsed by any TAP Consumer.
A quite large integration test has been added that encodes the expectations of the TAP13 spec, and the existing TAP reporter unit tests have been updated to be compatible with the new spec.
Finally 'reporters.fixture.js' was added to have something to run that generates test results with varying properties.
Original discussion can be found in Tobias Mollstam's PR #3452.
Issue #2410 remains at large from what I can tell.
Alternate Designs
It was considered to add either a new reporter (e.g. tap13) or hide the new spec under a reporter option but since there are no breaking changes in TAP13 this was deemed unnecessary.
Why should this be in core?
Mocha relies on a default selection of usable reporters. A bunch of TAP Consumers that Tobias surveyed are poorly written and expect TAP13, or will otherwise break thus rendering the current TAP reporter in Mocha less useful.
Benefits
A larger ecosystem of tools that are only compatible with TAP13 are made available to use together with Mocha. Taking a step back, benefits in the TAP13 vs. TAP12 spec are inherited, such as being able to encode richer error information in the now-allowed YAML block in the TAP report is a Good Thing.
Possible Drawbacks
Many TAP Consumers are not as flexible as one might wish so it is possible they don't fully conform to the old v12 spec, thus not being compatible with the TAP13 spec resulting in undefined behaviour. For example, currently in mocha the error stack is simply inserted into the report following the failed test, something that is allowed by the v12 spec as an "unknown" line that shouldn't be an error and may be handled by the test harness in any way. If a test harness handles mocha's stacks by using regex, it will probably break now that the stack is wrapped in what TAP13 calls a "YAML block".
Applicable issues
Fixes #2149
Closes #3452
Fixes #1257
semver-minor

Coverage increased (+0.1%) to 90.499% when pulling b060a14880363f5fdb3bc67c41b7a04bbd427b6e on mollstam-reporter-tap-v13 into be17ea5beecfb6fb4dfebcd584a19e0493c77aa5 on master.

@plroebuck Is this breaking even if version 12 is the default?

aside: why is TAPProducer#writeFail implemented? where is it used?

L220, L261
Thought we were gonna have a TAP14 as well earlier...

Is this breaking even if version 12 is the default?

Actually, no. Had just copied the existing PR.
But we modified the original  game plan, and stuck with TAP12 as default. TAP13 is opt-in.

Looks good. 👍

@mollstam, wanted to get this into upcoming release, and you had gone dark -- never responded to several questions.
Still need to know about:

pending tests in summary
showing test timings

ready to go


Could not resolve placeholder 'login.serviceProviderKey' in value "${login.serviceProviderKey}"

I'm trying to deploy uaa (version 45) with bosh director (version 262.3).
As described in http://bosh.io/jobs/uaa?source=github.com/cloudfoundry/uaa-release&version=45, the following properties are deprecated:
      login:
        saml:
          serviceProviderKey: ((uaa_service_provider_ssl.private_key))
          serviceProviderKeyPassword: "" # TODO: Remove this when UAA defaults this value
          serviceProviderCertificate: ((uaa_service_provider_ssl.certificate))

So I modified them to the recommended ones:
      login:
        saml:
          activeKeyId: key1
          keys:
            key1:
              key: ((uaa_service_provider_ssl.private_key))
              certificate: ((uaa_service_provider_ssl.certificate))
              passphrase: ((login_saml_passphrase))

But the uaa job failed to start, reporting error:
org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'identityZoneConfigurationBootstrap' defined in ServletContext resource [/WEB-INF/spring-servlet.xml]: Could not resolve placeholder 'login.serviceProviderKey' in value "${login.serviceProviderKey}"; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder 'login.serviceProviderKey' in value "${login.serviceProviderKey}"

When I changed back to the deprecated properties, there was no problem. I wonder if the properties are really deprecated?

We'll be including the fix in the next release. The old method will still work for backwards compatibility purposes. We will support the recommended options going forward to allow for SAML key rotation.


Make synapse openshift-compatible by adding start.sh and EXPOSE

Signed-off-by: Patrick Uiterwijk<EMAIL_ADDRESS>

Merged with a few changes: https://github.com/ilianaw/dockerfiles/compare/8d31325...ecc0035
Let me know if you have concerns.


Made requested changes

I made the changes you wisely suggested! Hopefully it looks good now feel free to add any more ideas or critics

FYI -- The tests noticed that you've renamed the business search function from search to businessSearch. I've reverted this change so that it doesn't break existing users of this library.
Updates have been published to npm


What is .terminfo for Windows Terminal?

Can you share .terminfo for Windows Terminal? I tried to start Midnight Commander from msys command prompt, the keyboard and mouse are not working at all. A usual way to solve it is just to compile .terminfo and set TERM to the corresponding value.
Environment
Microsoft Windows NT 10.0.18363.0
Windows Terminal: 1.0.1401.0

Steps to reproduce
& c:\msys64\usr\bin\bash.exe --login -i
$ export TERM=xterm-256color
$ mc

Same with mc -x.
Expected behavior
I expect Midnight Commander to work
Actual behavior
Midnight Commander doesn't response on any keyboard our mouse input.

If youa re using an msys runtime version earlier than cygwin-3.1, you're hitting cygwin's emulation layer. There's nothing we can do about that, and changing your TERM value will not help.
The cygwin emulation layer was finally replaced in cygwin-3.1 with something that detects when the Windows Console (and therefore Terminal) support VT encoded data.

you're hitting cygwin's emulation layer

I am not using cygwin, what are you talking about?
Can you share .terminfo for Windows Terminal?

msys is based on the cygwin runtime. 😓
I am not sharing the .terminfo for Windows Terminal because changing the TERM value in msys will not fix your problem. Windows Terminal is xterm-256color compatible.

The one that I am using doesn't have any cygwin DLLs.
Whatever, I will compose .terminfo by deciphering your source code.
Thanks.

You're not really listening to me.
https://github.com/msys2/MSYS2-packages/blob/master/msys2-runtime/0002-Rename-dll-from-cygwin-to-msys.patch
That patch, which is part of the msys2 runtime code, changes the dll name from cygwin to msys2. Msys2 is Cygwin.
I cannot stress this enough:
There is nothing that the terminfo can do to work around msys2's translation layer, which it got from Cygwin.

There's nothing we can do

Everything is fully functional in ConEmu, thus it is possible to do.

Hey so we're maybe getting a tad bit off the rails here - lets start from the top.
@intractabilis:

What version of msys are you using?
Does mc work inside WSL for you?

I just upgraded msys2. Now msys-2.0.dll is 3.1.4 (funny, it's pi). It indeed helped somewhat: the keyboard works.
However, mouse clicks just output escape codes to console as text. Obviously the escape codes are not what ncurses is set to recognize as mouse events. Still no .terminfo?

I don't have WSL.

There's not really a terminfo for the Windows Terminal - by all accounts, we're attempting to emulate xterm256-color. If input isn't working for you, then there's probably some other thing that's causing this than just the Terminal.
Using WSL's mc would be a handy way for us to either narrow the issue down to msys, or verify that this is a broader issue with the Terminal

Adding this in case it helps someone:
I haven't tried this fix with Midnight Commander (I didn't even know what it was until 10 minutes ago), but I had a somewhat similar issue with Gradle output and setting export TERM=cygwin helped me. See https://github.com/gradle/gradle/issues/13279
But then I also ran into an issue with zsh, resulting from that:

zle-line-finish:echoti:1: no such terminfo capability: rmkx
zle-line-init:echoti:1: no such terminfo capability: smkx

I managed to fix that by overriding those functions, as described by https://bbs.archlinux.org/viewtopic.php?id=151738

TERM value for Windows 10 terminal - Super User
export TERM=ms-terminal

TERM value for Windows 10 terminal - Super User
export TERM=ms-terminal

Still no mouse in mc.

We don't maintain a ms-terminal term info value. Anything you find in there is probably outdated and unofficial.
My recommendation has always been to use xterm-256color as our TERM value. Anything in there we don't support is a bug on us that needs fixing.
Mouse support has worked in the Terminal for some time now. It works best in WSL applications. There are some caveats for .exe's using mouse support. https://github.com/microsoft/terminal/issues/10321#issuecomment-855083607 has some details. But, if y'all are asking about TERM values, I'm assuming the win32 caveats don't apply ☺

Mouse support has worked in the Terminal for some time now.

I just checked in msys2 with all latest updates. Mouse doesn't work. At least in mc.

Windows-Terminal is a bit overconfident about its compatibility, they are missing some xterm features.
If your system has no terminal info for ms-terminal on your system, you could add it to your .termcap:
# add this line to ~/.termcap to add support for TERM=ms-terminal
ms-terminal:mi@:IC=\E[%d@:ei@:ic=\E[@:im@:tc=xterm-new:

# if you do not want to change TERM,
# and make it work with the default TERM=xterm-256color add
xterm-256color:mi@:IC=\E[%d@:ei@:ic=\E[@:im@:tc=xterm-new:

This at least fixes the overtyping/partial update problems I get on some systems.
It would be great to actually supply a terminal config that specifies the real capabilities…

@TypedLambda I'd much rather focus on implementing the missing features. Which ones are you missing? IRM was just implemented in 1.17, which is likely the source of any overtyping you may have seen.


Add types

I realized the only exported function from the main index file seems to be one function so I just made a quick definition file, just to fix the import errors in the examples. Everything else seems to be internal and does not really need to be typed yet for the consumer of the package. Maybe a starting place for #29 before (if) it gets converted to TypeScript.

I made some changes https://github.com/karolis-sh/electron-snowpack/pull/31 and released this with 0.7.0


Display beneficiary information in the subscription details

Is your feature request related to a problem? Please describe.
Display beneficiary information in the subscription details from the Fulfilment API
Describe the solution you'd like
Able to see beneficiary information
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Merged PR linked


Lesson 1 challenge

This is the coding challenge of lesson 1

This is the link: https://colab.research.google.com/drive/1iSTUkWT7o7tPY4hS30Dv-scMUBFs3BT-?authuser=2#scrollTo=LIAuQhFfoxpR
Should I clone the entire repository and add the change to the new branch I created (Reinforcement-Learning-Curricilum)?


Fixing Typo

I'm not native English, but I think "in" is correct, isn't it?
ChatGPT agrees:

In English, we typically use the preposition "in" when referring to the availability of a package in a package manager. Therefore, the correct phrase would be: "This package is available in [package manager]."


Transparency for custom widgets

Is your feature request related to a problem? Please describe.
For a widget I'm working on, a common use for it will involve it being pinned over top of a game, but since widgets can't be transparent, the area taken up by our widget will completely obscure that area of the screen. Any attempt to adjust opacity of controls just reveals a white background.
Describe the solution you'd like
The solution we would like to see is to let us have the option to remove the background for the frame so that we can have control over the transparency of our widget and its controls, like the Performance widget already does.
Describe alternatives you've considered
We could not come up with any alternatives. Either the widget has transparency and doesn't obscure part of the screen, or it doesn't have transparency.
Additional context
Example of the Performance widget's transparency.
We do know that the widget does not become a part of the Game Bar layout, and is instead a remote view. We confirmed that opacity changes in the Game Bar layout through debugging also affect the white background. Additionally we confirmed that our widget does not contain a background as part of it's layout that could explain the white background. This leads us to suspect that the remote view does not support an alpha channel.

We're evaluating how to enable this functionality, but haven't committed to a date for delivery.

Today we're publishing the prerelease version of the 20.06 release which includes support for transparency. Check out the changelog for more information, along with the accompanying documentation. The samples for this early look are in the origin/prerelease branch. Be sure to update your Game Bar build with the latest from the SDK flight ring.

FYI - the 20.06 release date has been tentatively moved to 6/24 in order to work through a recently discovered issue. Please continue to hold any app submissions that depend on the 5.3 SDK until it has been released.
Sorry for the inconvenience.


Training with pillarvfe

At present, VFe is using meanvfe, but it can't be training with pillavfe. What changes need to be do? It seems that Shencheng headmap doesn't match.

Contrast voxelnet backbone,the results didn't look very good for pp backbone,what can be done to make the result better

I have no clue. This is also the reason why I didn't provide a PP config on KITTI

Hello @coolzhangfeng, what are your evaluation results on kitti of centerpoint with pointpillars backbone?
Can you post your results here? Thanks


No Notifiers (env var / docs issue)

Hi, I just realized there's been a few breaking changes in the last two weeks and my notifications have been missing. I turned on debugging to figure out what has been going on and I realized these environment variables are no longer optional and I'm not sure if that is intentional. They seem to be optional in the sense that they must be set even if they're empty like SMTP_USERNAME: "" but a notifier won't be created if aren't defined.
For example I don't use authentication for my smtp server so I'd assume not setting these environment variables would be fine as the docs say No authentication is used if unset
DEBUG   notifier         SmtpNotifier configuration invalid, skipping creation
DEBUG   notifier                SMTP_USERNAME is not set and no default value provided
DEBUG   notifier                SMTP_PASSWORD is not set and no default value provided

Apprise Tag also seems to no longer be optional (unless set to APPRISE_TAG: ""):
DEBUG   notifier         trying to create AppriseNotifier
DEBUG   notifier         AppriseNotifier configuration invalid, skipping creation
DEBUG   notifier                APPRISE_TAG is not set and no default value provided

If possible it might be nice to up the log notification level if a notifier fails to be created when one environment variable is set?
Thanks again for your app and time!

Hi, thanks for the report.
I can confirm your issues, sorry about that.
The first issue you reported is a regression from a recent change to remove dependencies from dolce. I fixed the bug now, so if you check out version 3.0.2 or latest/master you should be able to create the smtp notifier now without specifying the empty strings.
Your second issue is cased by the SMTP lib I used no longer being supported.  I'll keep you updated if the new version is released.

Ok, this was quicker than I expected but I was nerdsniped.
In release 3.1.0 everything should be working again as expected. Let me know if you encounter other problems

Everything works great now, thank you. I just have to note that you do have to unset environment variables when they are empty otherwise it will assume that's valid credentials like SMTP_USERNAME: ""


Fix: Clean up .gitignore

This PR

[x] cleans up .gitignore
[x] removes checked-in PhpStorm files

I have never published a library before. Whats the common practise here ?

@Jan0707
I think https://contao.org/files/conference/2018/papers/Contao-Konferenz-2018-Composer-in-Depth.pdf by @naderman sums it up:

@Jan0707
I"ll propose a PR!

Thank you, @Jan0707 and @Jean85!


gparyani: Watch clickbait

gparyani requests the watch of the watch_keyword clickbait. See the Metasmoke search here and the Stack Exchange search here.

clickbait has been seen in 4 true positives, 0 false positives, and 0 NAAs.

You sure?  https://stackexchange.com/search?q=clickbait

Potential sockpuppetry by a suspended user on MSE. See Tavern on the Meta. (@NobodyNada )

!!/approve


Implement CD pipeline

Test CI/CD by changing frontend text.
Test CI/CD by changing frontend text.

Codecov Report

Merging #52 (58096ef) into main (69ec415) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #52   +/-   ##
=======================================
  Coverage   95.43%   95.43%
=======================================
  Files           5        5
  Lines         285      285
=======================================
  Hits          272      272
  Misses         13       13

Continue to review full report at Codecov.

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


storage: add an EscapedByteSlice convenience wrapper

This may be helpful for debugging.

@zbuc I added this after seeing test output like
 insert nonconsensus change: [115, 99, 116, 47, 115, 116, 117, 98, 47, 115, 116, 97, 116, 101, 95, 99, 111, 109, 109, 105, 116, 109, 101, 110, 116, 95, 116, 114, 101, 101] -> [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 32, 0, 0, 0, 0, 0, 0, 0, 192, 180, 162, 133, 154, 38, 152, 23, 92, 175, 29, 115, 76, 223, 47, 11, 57, 3, 107, 124, 187, 99, 63, 190, 34, 149, 163, 200, 221, 245, 123, 13]

in the tests for #2429. Maybe it would be easier to read if we put this into the StateDelta as a tracing event using EscapedByteSlice at trace level or something?


fix(@angular/cli): correctly build completion with blueprints and options

before, if both blueprints and options are present, a space was missing between
them, resulting in "service--dryrun" instead of "service --dryrun"

loop inside extractOptions does nothing, are there tests for this one?

@sumitarora @catull can you review please?

@filipesilva Tonight, from home.
Don't have nodeJS installed in the office etc.

Whenever suits @catull, I appreciate you taking the time to look at it.

@catull anything more to do to get this merged?

Please also correct docs/documentation/stories/autocompletion.md.
That document still describes the one-off static generation of completion to be fed to ~/.bash_profile and ~/.zshrc.
Other than that, LGTM.

Merged, and big thanks to @georgmu, @catull and @chrisnoringovo for keeping this feature working well!


Transactions stuck in the starmask queue

Workaround method to fix:

backup starmask and reinstall the starmask, and import account.

sequence number is empty

one solution：
close chrome，and reopen， all transactions that state is APPROVED will be reseted to FAIL on boot up


Process stucked at a certain episode

So i started downloading Jujutsu Kaisen s01 and i observed dl Stucked at episode 18 and after that i did a new start again and now its stucked at episode 8 and i did it again now it Stucked at episode 21
crunchy archive -o "Jujutsu-Kaisen-S01-mkv/{series_name} (呪術廻戦) S{season_number}EP{relative_sequence_number} {title} {height}p.mkv" -r 1080p -t 1500 --audio te-IN --audio ta-IN --audio hi-IN --audio en-US --audio ja-JP --subtitle en-US --merge audio https://www.crunchyroll.com/series/GRDV0019R/jujutsu-kaisen[S1]

I think this is related to: https://github.com/crunchy-labs/crunchy-cli/issues/310

My current fix is to rerun it with [S1Efailed_at] IE: https://www.crunchyroll.com/series/GRDV0019R/jujutsu-kaisen[S1][S1E21] this will redownload starting at episode 21, or you can just add the flag --skip-existing to start where you failed as well.

Yes currently i am doing the same but you know it annoys me because now i am not able to dl seasons properly

Duplicate of #310, closing in favor of it


selectionFollowsActiveCell not reseting selectionBounds on keydown

Expected behavior and actual behavior.
SelectionBounds to be in sync with selections on key navigation.
Steps to reproduce the problem.
selectionFollowsActiveCell = true
Shift select a few cells with keyboard navigation.  Then just use the keyboard to navigate without shift or ctrl and the selectionBounds will be the previous selection.
Specifications like the version of the project, operating system, or hardware.

Looking through the keydown event, I think the fix is as simple as changing:
ev = {
   selectedData: self.getSelectedData(),
   selections: self.selections,
   selectionBounds: self.getSelectionBounds()  // was self.selectionBounds
};

I see, so the event is showing a function instead of the selection bounds?  While this is getting fixed and deployed you can get at the same, and hopefully correct data using grid.selectionBounds.
If you are sure that fixes the problem, feel free to make a PR.  I'll fix it myself in short order if you're not feeling like it.
And thanks for finding the bug!

Seems to be working.


Upgrade Rails to v<IP_ADDRESS>

Context
:gem: We're upgrading Rails from v7 to v7.1 :steam_locomotive:
Release Notes: https://guides.rubyonrails.org/7_1_release_notes.html
Upgrade Guide: https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-7-0-to-rails-7-1
Incremental upgrade options: https://github.com/rails/rails/blob/6f0d1ad14b92b9f5906e44740fce8b4f1c7075dc/railt[…]/templates/config/initializers/new_framework_defaults_7_1.rb.tt
Changes proposed in this pull request
This is a minor version upgrade of the Rails framework.

Zeitwerk now autoloads the lib directory
Add config.autoload_lib(ignore: %w(assets tasks generators rubocop))
AWSIpRanges needs changes because Zeitwerk doesn't like how it's inflected.

config.cache_classes = true is now config.enable_reloading = false

Running bin/rails app:update generates double quotes, make that default

ActionDispatch::HostAuthorization middleware is not guaranteed to be present
We don't populate the config.hosts property in production so the middleware is not used.
We need to choose another middleware to insert middlewares relative to.

form_for and form_with refactoring in Rails caused a bug in RejectionsWizard
Remove the implementation of #to_model in the RejectionsWizard. Implementing #to_model to return the underlying object puts too many dependencies on Rails internals.
Rails 7..7.1 fixes for #to_model
https://github.com/rails/rails/pull/43421
https://github.com/rails/rails/issues/44326
https://github.com/rails/rails/pull/44468

Guidance to review
Options to enable?
Annotate rendered view with file names
  # Annotate rendered view with file names.
  config.action_view.annotate_rendered_view_with_filenames = true

Link to Trello card
Trello Ticket

 Upgrading Rails to 7.1

Tested the review app, overall I couldn't identify anything wrong. All good :)


Auto-generate X-road services based on WSDL

AS AN Architect
I WANT XTR services to be generated automatically based on (almost) any of X-Road's WSDL
SO THAT XTR could provide X-Road services without (minimal) manual interference
Acceptance Criteria

[ ] (Almost) any WSDL can be used as source
[ ] XTR-compatible services are generated for all of the WSDLs within unprocessed folder
[ ] XTR-compatible services can be used as REST endpoints

Won't do as for deprecated version of XTR


Move ViewportOffset to its own file

There aren't any interdependencies with the rest of sliver.dart, and that file
is already quite complex.

@Hixie


Made it work with package manager

Hello. I found it annoying that I had to download, drag n drop the files so I turned it into a package.
I hope it's not a problem that I used your name in package.json.
If you don't care about merging I can remove your name and credit you some other way

Forgot to say, I also did it with the other branches.

Won't merge as there's some spelling mistakes, but I've now made changes myself to support the package manager.
(Currently only on the master branch. Will probably add it to the DrawMesh branch when I next update / merge it)