chore: remove ahead block from queue

When processing a gossiped dag block for which we do not have a proposal period yet, it is safe to assume that we are not pbft synced in which case there is no need to keep this block in the queue which creates a loop that creates a lot of unneeded logs as well as it eats up CPU. Drop this block and expect to receive it again when fully pbft synced.

prnet cleaned-up successfully


Support StartTLS mail servers in IMAP sensors

Description:
Being able to disable SSL lets the imap sensor work with servers expecting STARTTLS.
If this is acceptable I will update the documentation and the imap_email_content sensor as well.
Example entry for configuration.yaml (if applicable):
sensor:
  - platform: imap
    server: !secret mail_server
    port: 143
    username: !secret mail_username
    password: !secret mail_password

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass

Hmm, the SSL default depends on the selected port, only being True for "IMAP over SSL" (port 993). Setting an explicit default breaks that.
self._ssl = (port == 993) if ssl is None else ssl

Is that a bad way of doing it?

Yes. On HomeAssistant is security opt-out and not opt-in. So we need explicit deactivate SSL and default is the hight possible security options.

Right, I believed that the plaintext connection would auto-upgrade with StartTLS, but I now see that I must have been confused. I will rework this and come back with a different approach. Thanks for reviewing!

Now I reverted the entire commit and made a new one that insists on encryption. Thus, no new config value is needed.
I am unsure how to present this revised work so let me know if I should squash the commits, create a new PR or whatever.

Please add unittest for it to check if it will work

https://home-assistant.io/components/notify.smtp/

Do you want address comments?

Please reopen if you want finish it

Yeah, I lost the motivation to complete this. I disagree with an implementation that does not guess the protocol based on the port number since it will almost always guess right.
Also, notify.smtp is insecure by default so that is a bad example to follow.
I wanted to propose a security option with values:

auto (default)
ssl
starttls
none (I think that this one should not be supported)

But then you told me to write test cases for an untested area in an application that is unfamiliar to me and it ended up too much trouble to get a five line patch accepted.


Feat Error 404 page

Pull Request: Fix for 404 Error Page Issue (#144) - PenCraft Full Stack
Hi @AkshitLakhera
Description:
This PR addresses issue #144 regarding the missing or incorrectly rendered 404 error page in the PenCraft Full Stack application. The 404 page is now designed to be more user-friendly, providing a clear and consistent error message when users navigate to a non-existent page.
Changes Made:

404 Error Page Design: Improved the layout and styling of the 404 error page located in frontend/src/not-found.tsx.
Error Handling: Updated routing and error handling to ensure that invalid routes correctly lead to the custom 404 page instead of a default server error page.
Image Update: Included a relevant error image stored in frontend/public/Error404.png to enhance the user experience.

Files Modified:

frontend/src/not-found.tsx – Updated the 404 error page component with the new design and routing.
frontend/public/Error404.png – Added a custom error image for the 404 page.

New Features:

Custom error message: "Oops! The page you're looking for doesn't exist."
A navigation link back to the homepage for better user experience.
A clean, modern layout that aligns with the overall PenCraft theme.
The image Error404.png has been integrated into the page for visual appeal.

Screenshot:
Here is a screenshot of the newly designed 404 error page:
Desktop View:

Mobile View :

Testing:

Tested by manually navigating to random non-existent URLs within the app.
Ensured that invalid URLs are correctly captured by the routing logic and redirected to the custom 404 page.
Verified the error page's responsiveness across both desktop and mobile devices.

Impact:

The app will now display a user-friendly 404 error page with an informative message and visually cohesive design.
The app's overall user experience is improved by providing clear guidance when users land on non-existent pages.

To Do:

Review and merge the PR after testing on staging.
Update any related documentation regarding custom error pages.

Hi @AkshitLakhera , I ahve update the page now please look into it and let me know.

Hi @AkshitLakhera , please review my PR.

This PR has been merged by the GSSoC team
here - https://github.com/sanjay-kv/Open-source-Practice/pull/1413
Don't add labels to it now.
You'll get the points in the leaderboard update.


Unused variable might be an error

When cleaning up unused variable warnings, I noticed a few unused variables that might be an error:
https://github.com/rivosinc/veclibm/blob/0a6c0c09060579e5a7f7d1479560ac838f86d38c/include/rvvlm_tanD.inc.h#L63-L71
https://github.com/rivosinc/veclibm/blob/0a6c0c09060579e5a7f7d1479560ac838f86d38c/include/rvvlm_sinandcosD.inc.h#L64-L72
https://github.com/rivosinc/veclibm/blob/0a6c0c09060579e5a7f7d1479560ac838f86d38c/include/rvvlm_sincosD.inc.h#L75-L83
The comments seem to imply that a should be used, but it isn't. I don't know enough about the implementation to tell if this is an error, or just an unused variable that can be removed.

Thanks for spotting this. There is actually a bug here. Apparently tests did not exercise this branch of the code: where input argument is not too large but very close to integer multiples of pi. I will fix the code and also add some test infra to test special arguments.


[Epic] Search page

Add page that:

Displays nearby stops
Allows searching for Lines by name
Allows searching for stops by name

Not sure if we should reuse the FloatingPanel paradigm, or make it a master-detail style view.

Now that I've gotten started, I can outline more of todo list:
Overall tasks

[ ]  Break each pivot into its own ViewModel
[ ]  Make the parent ViewModel bind to the pivot with an ObservableCollection of the children ViewModels
[ ]  Figure out a less-buggy way to bind locations to the map
[ ]  Experiment with hanging the FloatingPanel from the top of the page

Nearby Stops & Stops

[ ] When selecting a stop, center it on the Map, and focus its MapIcon (somehow. Either swap out the bitmap, or just give up and use XAML controls on the MapControl)
[ ] Allow selection of stops by tapping on their MapIcons
[ ] Make the list of lines in the "More Details" page link to the given line
[ ] If the More Details page for a given stop has no upcoming transit stops, show a friendly "No line stops here within the next  hours" message
[ ] When viewing the "More Details" page,

Lines

[ ] (Maybe not?) Find a way of displaying some kind of schedule information here
[ ] Allow this section to receive search requests from other parts of the app


CB-10598 Azure network resource group is not deleted when "Create new…

… RG" is used
When you create a new Azure environment using the create RG option (multiple RGs) the control plane creates 4 RGs. One of them is only for the VNet and when you delete the environment it should delete the network RG as well. The problem is that currently only the single RG name is fetched during deletion.
See detailed description in the commit message.

@gergopapi2 LGTM, I've re-triggered the failing IT.

@gergopapi2 LGTM, I've re-triggered the failing IT.


Low GPU use

When running DeepIM with the gpus 0,1,2,3 flag, the GPU usage is still really low. The CPU load, on the other side, is pretty high.
I'm able to train around 6 samples per second which seems unreasonably low for 4x GTX 1080TI.
Is this kind of behavior expected?

It looks normal.


Enhancement request: add option to enable auto refresh of image

I think it would be useful to have an option to enable auto-refreshing of the heatmap as an option in settings or as a checkbox near the “refresh heatmap” button. Also if it kept a record of the previous (or past few) measurements, you could get the same effect as currently allowing you to compare “before” and “after” heatmaps, while still enabling a “live” view without needing to refresh. (Disclaimer: I have yet to install this plugin, as a long print is currently

... ongoing, so I don’t know how well this would work in practice.) (sorry for accidentally hitting submit too soon, leading to the split post)

This is actually one of the more difficult things I ran into with this plugin, and I am still not certain it's optimal (but nobody in #octoprint answered my question when I asked it there, so I went with it for now).
When the heatmap.png file gets loaded, your browser caches it. To work around this, the "reload" button tells Javascript to reload it with heatmap.png?someDateTimeStamp. This fools your browser into reloading heatmap.png instead of using cache. The downside is now you have more than one heatmap.png cached at the browser end, and if you were to use this method in an autorefresh... you can see how it gets ugly fast. :)
I am considering storing multiple images by timestamp and having the plugin give the user the option to view past results. My issue currently is I don't know the proper way OctoPrint wants me to store them. Right now heatmap.png is served up out of site-packages/octoprint_PrusaMeshMap/static/img/ directory, and I think I shouldn't be overwriting it continually, and most certainly shouldn't keep storing data there. I couldn't find any documentation on where these should be stored or how to get to them from the public facing webserver either.
So marking this one as help wanted. I will try to look at it some more, but maybe someone with more experience than me in this area can contribute. :)


Release v1.3.0

[x] Write Release note
[ ] Update pod repo

Ref #50, #64, #73
EDIT
I'm planning to release it on Dec 15.

Replace with #85


Improvements: Dynamic animations, pageTransitionService, :enter and :leave animations

Deprecate ng2-page-transition and rename to ngx-animate-routes

Pass data in routes like

const routes: Routes = [
  {
    path: 'home',
    component: HomeComponent,
    data: {
      pageTransition: {
           goBackMotion: ['toRoute1'],
           goForwardMotion: ['toRoute2']
      }
    }
  },
[...]
]

Use ActivatedRoute to get page-transition data per route and trigger transition based on fromRoutes or toRoutes or trigger default transition if no matches.

Add service to support special use cases like

showNextFriend(someId: string):void{
     this.pageTransitionService.nextRouteDo(someTransition);
     this.router.navigate('/friend/'+someId);
}

Make simple :enter and :leave transitions possible (<animated-router-outlet> ? ) -> Creates router-outlet. Wrap div around component so that it is not replaced immediately on route change and the leave transition can complete -> then remove div DOM node

pass in animations in forRoot

There is currently no possibility to do this in a clean way without accessing the DOM directly.
Not even extending the router-outlet would work unless replacing the whole thing.
See https://gitter.im/angular/angular?at=58ba0ed3872fc8ce62b2d34a and the messages up to ~ 10 hours before
See http://stackoverflow.com/questions/42583354/angular-2-router-wait-for-animation-to-complete-on-component-before-destroying-i
Upcoming changes for animations might change this situation. Probable date to know more is the ng-conf from 5th to 7th April https://www.ng-conf.org/
Closed for now.


[IOTDB-1951] Support aggregation query without value filter in new vector

adapt new vector about AlignedPath for aggregation
add IT for vector aggregation

Coverage increased (+0.03%) to 66.992% when pulling 4d0874922c9b24ceae22a01f3472d2156ad1344b on Cpaulyz:feat/aggregationWithoutValueFilterForVector into d9d8733f17878cd07e4510a7f9b3af92049863c3 on apache:master.


Cleanup incomplete

Hi!
I just tested your Software, it's works like a charm! The only thing I found not to work is the clean up - once I stopped capturing I have to physically dis- and reconnect the GCHD to start a new capture. If I try to start a new capture without reconnecting the GCHD the software just hangs and needs to be killed - ctrl + c won't do the trick.

Hi there,
unfortunately, I have no time to work on this project at the moment and have never really worked on cleanups. I was glad enough, when the video capture worked on Linux. So, I never really looked at how the Windows driver is resetting the device. My USB hardware analyzer has very limited amount of RAM, which is not enough for long captures (talking about 10+ seconds on USB High-Speed).
Probably, I'm gonna continue working on these drivers in about 3 - 4 weeks.
Cheers,
Tolga

b5e46776bbe5a44599951e162375497e4837454b fixed this. When you terminate the driver using CTRL + C, wait a couple of seconds for the driver to gracefully shutdown / reset your device. After the program has successfully terminated, you will be able to re-run it, without needing to replug your device.
Closing this issue now. Thanks for reporting!

b5e46776bbe5a44599951e162375497e4837454b fixed this. When you terminate the driver using CTRL + C, wait a couple of seconds for the driver to gracefully shutdown / reset your device. After the program has successfully terminated, you will be able to re-run it, without needing to replug your device.
Closing this issue now. Thanks for reporting!


document coding across multiple repos for ng, sdk, .. etc

let's have path dependencies documented as the main option https://python-poetry.org/docs/versions/#path-dependencies

https://github.com/threefoldtech/js-sdk/blob/baeafcf3309da586b84905e38a0cc3c2af7beec0/docs/wiki/devsetup.md#L0-L1 info added on using other repos in edit mode


[WIP] PI Auth Integration

Resolves #
<Brief description of the added features or other changes/updates (either bulletpointed list, small paragraph, etc.)>

Resolved with another PR


The scope of the unsafe block can be appropriately reduced

In this function you use the unsafe keyword for almost the entrie function body.
We need to mark unsafe operations more precisely using unsafe keyword. Keeping unsafe blocks small can bring many benefits. For example, when mistakes happen, we can locate any errors related to memory safety within an unsafe block. This is the balance between Safe and Unsafe Rust. The separation is designed to make using Safe Rust as ergonomic as possible, but requires extra effort and care when writing Unsafe Rust.
Hope this PR can help you.
Best regards.
References
https://doc.rust-lang.org/nomicon/safe-unsafe-meaning.html
https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html

cargo fmt appears to fail on CI; can you address that?


Can't install update 24.0.4 on Mac OS Catalina 10.15.7

Description
Starting DBeaver warns that update 24.0.4 is available.
After downloading it and mounting the DMG arrchive, the installation programs warns that this version requires macOS 11. Have systems requirements changed recently? If so, can you please report the correct System Requirements web page?
DBeaver Version
Community <IP_ADDRESS>404211624
Operating System
macOS Catalina 10.15.7
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

Second this.
I have the same problem.

Thank you for your report. We have reproduced the issue and are investigating.

Similar issue with old versions of Windows #34034

Same issue on version 24.1.0

Any news about this on MacOS Catalina? I am with the same situation...

Unfortunately, after upgrading to Eclipse 2024-06, the following OS are no longer supported: Windows 8, macOS 10, and Windows Server 2012. This issue is not on Dbeaver side, you can see the details here: https://github.com/eclipse-platform/eclipse.platform.swt/issues/1252.
We have already added the system requirements to the download pages and are working on ways to warn users before the update.
However, we will keep an eye on the situation and try to do something if possible.
I’m closing the current ticket as a duplicate: https://github.com/dbeaver/dbeaver/issues/34034

It's not cool to do breaking changes like this in a patch release.


Remove need for use_attr and use_proc

implements first part of https://github.com/sam0x17/macro_magic/issues/3
what it does:
import_tokens macros call themself instead of calling their related inner_sig
forward_tokens_inner_internal will add a keyword at the start of the token stream.
if import_tokens see the keyword at the start of the token stream then it call their inner_sig which is declared inlined.
tests are successful
TODO:

update docs
discuss the keyword and whereas we should expose a forward_token which doesn't add this extra token in order not to break usage of forward_token
is it correct to assume usage of extra is equivalent to having been called by an attribute macro, or should we pass along this information in another way.

This is amazing, didn't think this would be possible without a stack of macros calling each other. I will have to go over carefully to understand how you got around that!

for context, extra right now is a sort of dumping ground for things that need to be passed from the initial macro call to the final macro call that were added on as later features from the initial version. It's sort of horrible how I pass it and use string manipulation to escape it, really it should be done on the export_tokens macro itself but this was a convenient way to quickly add a few features.

I am also OK with changing / breaking the original signature of forward_tokens if needed -- I don't think anyone is using it directly and I already see this as a 0.4x thing so OK to have a breaking change

So yeah if you can get the cargo fmt to pass I can merge this and we can tackle the next pieces

yes formatted, I only have the little concern above https://github.com/sam0x17/macro_magic/pull/5#discussion_r1217807486 but the PR is ready.
I will attend buidl asia, I will not work on the other point soon I think

OK I will see if I can get the other parts working and update the docs 👍🏻


Use classes to clean up system api

Purpose
The current approach of adhoc importing of python scripts is unfortunately not very clean, modular or maintainable. Thus this PR hopes to clean this by standarising the system interface via abstract classes, as well as collating the important scripts under a single class/file for each system. Additionally this allows for usage of the parser arguments demonstrated by @sevenEng in #12.
Current limitations
Currently we can't easily check the input arguments to ensure that they are correct. Currently we pass them through to the System class which then will check them at that point, however this isn't as clean as it should be.
Notes
I'd appreciate any advice on code style etc that anyone has, since I'm mostly just hacking this together based off of the style in #12.
TODO

[x] Define standard for systems
[x] Update client_runner.py and benchmark.py to use the new classes
[x] Update etcd to use this standard
[ ] Update ocamlpaxos to use the standard

I'm using autopep8 as the auto-formatter, basically as it's the default one on vs code. Think there are other tools that could provide the formatting for the same code style, probably could even provide integration with the CI pipeline as well.

@sevenEng that would probably be a good idea to autoformat this repo's python code. Do you know how to set it up or shall I have a go at it?

As a note to myself and anyone else confused as to why this failed the CI previously, the issue was that the client would fill up its output buffer and as a result be blocked trying to write to a full pipe.
This is due to the redefinition of popen in mininet such that pipes are automatically created for the subprocess, rather than the standard semantics of the output getting destroyed.


fix: #320 missing whitespace

Here's a PR for issue #320

@kevinashworth you're right.
I fixed it :)


Unable to resize Ferdi App after maximizing whatsapp video

Bug description:
Normally my Ferdi window has a size of 30% screen width and 90% screen height. After watching, maximizing and closing a whatsapp video Ferdi stays maximized. It is not possible to reduce Ferdis size to normal again. Ferdi stays maximized at 100% screen width and height without any possibility to change this. Restarting Ferdi does not help, also changing the resolution will not help.

Steps to reproduce:

System windows 7, 3 Monitors with 3840x2160 each, Ferdi was used on Screen #1 (with windows menu)

Go to Ferdi
Size it to 30% of screen size
Select Whatsapp
Select a righ resolution Handy Video
Start watching it
Click on maximize video
Watch Video in full screen
Close video message
Ferdi stays maximized
There is no possibility to reduce Ferdis size

Expected behavior
Ferdi should resize to 30% again, or it should possible to resize Ferdi
Screenshots

Environment:
System windows 7, 3 Monitors with 3840x2160 each, Ferdi was used on Screen #1 (with windows menu)

Operating System: Windows 7

Ferdi Version: 5.6.0 (latest)

Server: Using without an account

Debug information:
Can't find any

This might be related to https://github.com/electron/electron/pull/30561 - we will need to wait for the next version of electron to test this out.


Add \smash, laps, spaces, and phantoms

Support \smash, including the optional argument from AMS.

Change \llap and \rlap so that they render in text style. Repeat: This changes KaTeX behavior.

Add \mathllap and \mathrlap. These will act as they do  in mathtools and as in previous KaTeX versions of \llap and \rlap.

Add \mathclap and \clap.

Add \hphantom and \vphantom.

Add \thinspace, \medspace, \thickspace

Add \hspace.

This work will resolve issue #270 and parts of #50 and #164.
A. Perlis has written a concise description of items 1 thru 5. Except for \smash's optional argument. It's described in the AMS User's Guide.
Item 6 also comes from the AMS User's Guide.

I've put up a test page.

Wow, these are some awesome new features! Nice work, @ronkok.

The reason why \hphantom is off a bit is b/c some of the horizontal spacing around/inside of fractions is still off a bit.
The screenshots look great.

Awesome @ronkok.
Question: Shouldn’t groupType.smash call makeVList itself? For instance, consider something like \phantom{\huge x}. In TeX this will cause the x to overlap surrounding lines. I don't think this will happen with your code, but I'm actually having trouble getting a hold of your code to confirm.

unknown repository 😟
Also, https://patch-diff.githubusercontent.com/raw/Khan/KaTeX/pull/826.patch doesn't work.  😞

@kohler and @kevinbarabash, My apologies, but I've messed up my repository. I'm going to close this PR and re-open in a new one.

@kevinbarabash Well, I've found a new glitch. To clean up the mess, my plan was to delete my repository, then re-fork and re-clone. Then drop copies of the changed files into the new local repository. So far so good. Then I hit the "commit to master" button and I get an error message:

Commit failed - exit code 1 received, with output: 'error: cannot spawn .git/hooks/pre-commit: No such file or directory'

Now I'm stuck. If you have any suggestions, let me know.

Try deleting .git/hooks/pre-commit.

Running npm install may have also fixed this.

I did run npm update and it did not fix my problem. Not sure about npm install. No matter now.

Hopefully this isn't a widespread issue.


Inconsistent docker image names between Makefile and CI

In the Makefile, this project builds a docker-device-coap-c container.
device_coap:
	    docker build \
	        -f scripts/Dockerfile.alpine \
	        --label "git_sha=$(GIT_SHA)" \
	        -t edgexfoundry/docker-device-coap-c:${GIT_SHA} \
	        -t edgexfoundry/docker-device-coap-c:${VERSION}-dev \
            .

But the Jenkinsfile builds the "device-coap" container.
https://github.com/edgexfoundry/device-coap-c/blob/main/Jenkinsfile
We should update the Makefile to use the new standard container name.

@bnevis-i , good catch. Apparently a miss when we dropped the docker- and -c from the names.

closed #37


189 variable application fields input

This adds the input for custom application fields on the event page. Field names are saved in an ordered array in the database so they can easily be output again and mapped to the user entered values, simply by maintaining the same order.
E.g.:
["Lieblingsfarbe", "Lieblingstier"] in Event.custom_application_fields
would correspond to
["Blau", "Capybara"] in ApplicationLetter.custom_fields

Coverage remained the same at 100.0% when pulling 4258cb30b6085272717e533ed999f0a143ce9b0d on 189_variable_application_fields_input into 7fecfe1c5012ca487e09cedc5df6979cfaebaa41 on dev.

Field names are saved in an ordered array in the database so they can easily be output again and mapped to the user entered values, simply by maintaining the same order.

This is how I solved it for my personal event management system years ago. It caused many errors and problems and was hard to maintain. I know it'd be more work but a proper entity schema would be a lot better. Things that can potentially break your implementation:

Custom fields are deleted after somebody already applied
Sort order of custom fields is changed after somebody applied
Another custom field is added after somebody applied.

Just my two cents.

For the record, my system has the following schema:
1 event has n questions.
1 event has n application
1 application has n answers
1 question has n answers

You also run into problems once you extend the custom fields to have parameters themselves: Whether or not a field is editable, required, only allows integers, etc. Of course you can then store arrays of arrays of field options, but it only gets more messy and messy.

In order to avoid all of those problems our PO decided that all fields are immutable after creation. Using a more sophisticated data structure later on will only require changing very little code from this MR, so I think we can go with this smaller solution for the time being.

In order to avoid all of those problems our PO decided that all fields are immutable after creation. Using a more sophisticated data structure later on will only require changing very little code from this MR, so I think we can go with this smaller solution for the time being.

I see. So when you create an event, you must be really careful not to add any wrong fields or include typos. If that's what's agreed upon for now, go ahead :)

Coverage remained the same at 100.0% when pulling 919dad7871f7b328823cfe502815876293bba9fc on 189_variable_application_fields_input into 7bd7a034f6bb655a431c50df6bc98ee7e559db3d on dev.


Add "generic" option to the "optional" configuration for handling nullable types

This is an implementation for #251, it adds a new "generic" option for the "optional" configuration, and a companion type "optional_generic_type" which is a fully qualified type with a placeholder % for the generic parameter.
I have tested this locally with a custom optional.Value[A] implementation but I'm unsure how to add tests for this without bumping the Go version from 1.16 to 1.18. I would appreciate any input on how best to achieve this. Interested in any feedback on the design before I fill out the details on documentation and changelog.
I have:

[x] Written a clear PR title and description (above)
[x] Signed the Khan Academy CLA
[ ] Added tests covering my changes, if applicable
[x] Included a link to the issue fixed, if applicable
[ ] Included documentation, for new features
[ ] Added an entry to the changelog

Here's an example of it in use https://github.com/DylanRJohnston/genqlient/compare/main...DylanRJohnston:genqlient:example

I love the concept, thanks very much for implementing it! I don't have time for a proper review today but one thing I see is we'll want tests for this -- there are snapshot tests already set up and you'll just have to make some way to skip these on versions below 1.18. I'm a bit busy right now but I'll try to get back with a full review within a week or so.

Actually, one more thought on integration tests: I'm ok just running all the integration tests only against 1.18+, I don't think there's much we really need to test against older Go versions there. Not sure if that will be enough to make it easy though, so what I said before still applies.

@benjaminjkraft I've added a snapshot test and some more documentation. Do you want the the entire integration test to be updated to use the testutil.Option or to just leave it for now?

Ok, I pulled the version upgrade into #257, so once that merges you should be able to just merge and avoid dealing with that!

I went ahead and merged main and added the changelog. Thanks again for writing this -- I'm planning on using it in a project I'm working on!

Thanks! Apologies for not pushing this over the line  myself. I just got absolutely swamped at work just after putting this pull request up. Glad to see it in main though!


Port Issue: VCMI update / video playback

Port: VCMI
Description

Update to VCMI 1.5.6 (use master branch for this) -> also have native gamepad support now
Video playback won't work (at least on Anbernic rg35xx h)

updated to 15.08.24 dev branch version with gamepad support


Membership access request

Site url: pavel.pikirenia.me

Now that is the stuff the Club is made for! Thank you for your contribution and welcome to the 250kB Club!
Your sub page will be https://250kb.club/pavel-pikirenia-me


Multiline-comment lines containing a colon are indented with each formatter run

Given a file:
<%#
Multiline comment
test: test
%>

This is the file content after running prettier for the first time:
<%#
  Multiline comment
    test: test
%>

This is the content after running prettier for the second time:
<%#
  Multiline comment
      test: test
%>

And it goes on, indenting this line with each run  😄
.prettierrc.yml:
printWidth: 100
plugins:
  - "@prettier/plugin-ruby"
  - prettier-plugin-erb

package.json:
...
"devDependencies": {
    "@prettier/plugin-ruby": "^1.5.5",
    "prettier": "2.2.1",
    "prettier-plugin-erb": "git+https://github.com/adamzapasnik/prettier-plugin-erb.git#6374074005"
  },
...

(latest master branch, as of creating this issue)

Other example, from kaminari gem:
<%# Link to the "Previous" page
  - available local variables
    url:           url to the previous page
    current_page:  a page object for the currently displayed page
    total_pages:   total number of pages
    per_page:      number of items to fetch per page
    remote:        data-remote
-%>

After formatting:
<%#
  Link to the "Previous" page
    - available local variables
      url:           url to the previous page
      current_page:  a page object for the currently displayed page
      total_pages:   total number of pages
      per_page:      number of items to fetch per page
      remote:        data-remote
-%>

After formatting again:
<%#
  Link to the "Previous" page
      - available local variables
        url:           url to the previous page
        current_page:  a page object for the currently displayed page
        total_pages:   total number of pages
        per_page:      number of items to fetch per page
        remote:        data-remote
-%>

Hey @Wowu :wave:
Good catch :stuck_out_tongue_winking_eye:
Working on a fix

should be fixed in a newly released v0.2.0


Adds nest() util

nest(...Components: Array<ReactElementType>): ReactElementType

Composes components by nesting each one inside the previous. For example:
// Given components A, B, and C
const ABC = nest(A, B, C)
<ABC pass="through">Child</ABC>

// Effectively the same as
<A pass="through">
  <B pass="through">
    <C pass="through">
      Child
    </C>
  </B>
</A>

Current coverage is 99.52%

Merging #64 into master will increase coverage by +0.02% as of 7db1698

@@            master     #64   diff @@
======================================
  Files           39      40     +1
  Stmts          204     211     +7
  Branches         0       0
  Methods          0       0
======================================
+ Hit            203     210     +7
  Partial          0       0
  Missed           1       1

Review entire Coverage Diff as of 7db1698

Powered by Codecov. Updated on successful CI builds.


tensorflow-macos cannot train model

System information

OS Platform and Distribution):macOS 12.1
TensorFlow installed from (source or binary):tensorflow-macos pip
TensorFlow version (use command below):2.6
Python version:3.8
Bazel version (if compiling from source):
GPU model and memory: AMD RX6600 8G

Unable to train model
import tensorflow as tf

mnist = tf.keras.datasets.mnist
(x_train, y_train), (x_test, y_test) = mnist.load_data()
x_train, x_test = x_train / 255.0, x_test / 255.0
w, h = 28, 28

x_train = x_train.reshape(x_train.shape[0], w, h, 1)
x_test = x_test.reshape(x_test.shape[0], w, h, 1)

model = tf.keras.models.Sequential([
    tf.keras.layers.Conv2D(filters=64, kernel_size=2, padding='same', activation='relu', input_shape=(28, 28, 1)),
    tf.keras.layers.Flatten(),
    tf.keras.layers.Dense(512, activation=tf.nn.relu),
    tf.keras.layers.Dropout(0.2),
    tf.keras.layers.Dense(10, activation=tf.nn.softmax)
])

model.compile(optimizer='adam',
              loss='sparse_categorical_crossentropy',
              metrics=['accuracy'])

model.fit(x_train, y_train, epochs=5)
model.evaluate(x_test, y_test)

Run Information
2021-11-17 16:07:45.954518: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  SSE4.2 AVX AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2021-11-17 16:07:45.955017: I tensorflow/core/common_runtime/pluggable_device/pluggable_device_factory.cc:305] Could not identify NUMA node of platform GPU ID 0, defaulting to 0. Your kernel may not have been built with NUMA support.
2021-11-17 16:07:45.955191: I tensorflow/core/common_runtime/pluggable_device/pluggable_device_factory.cc:271] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 0 MB memory) -> physical PluggableDevice (device: 0, name: METAL, pci bus id: <undefined>)
Metal device set to: AMD Radeon RX 6600

systemMemory: 16.00 GB
maxCacheSize: 3.99 GB

2021-11-17 16:07:46.368598: I tensorflow/compiler/mlir/mlir_graph_optimization_pass.cc:185] None of the MLIR Optimization Passes are enabled (registered 2)
Epoch 1/5
2021-11-17 16:07:46.584915: I tensorflow/core/grappler/optimizers/custom_graph_optimizer_registry.cc:112] Plugin optimizer for device_type GPU is enabled.
2021-11-17 16:07:46.623 python[4372:114284] -[MPSGraph adamUpdateWithLearningRateTensor:beta1Tensor:beta2Tensor:epsilonTensor:beta1PowerTensor:beta2PowerTensor:valuesTensor:momentumTensor:velocityTensor:gradientTensor:name:]: unrecognized selector sent to instance 0x600007d83720

Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)

Hi @Yuri-Su ! Could not find any issue  in 2.7 ,It was throwing AlreadyExistsError in 2.6 . Attaching Gist fore reference.
For further assistance.
Please post this issue on keras-team/keras repo.
To know more see;
https://discuss.tensorflow.org/t/keras-project-moved-to-new-repository-in-https-github-com-keras-team-keras/1999 . Thanks!

This problem was solved in the latest version 2.7, the metal version is 0.3.0. But the adam optimizer still has problems

I have the same problem: Adam optimizer would not work. Although SGD works, it does not actually optimize anything, i.e. loss does not improve over epochs.
Intel iMac 27 (2020, AMD Radeon Pro 5500 XT)
[MPSGraph adamUpdateWithLearningRateTensor:beta1Tensor:beta2Tensor:epsilonTensor:beta1PowerTensor:beta2PowerTensor:valuesTensor:momentumTensor:velocityTensor:gradientTensor:name:]: unrecognized selector sent to instance 0x60002836b9c0
Versions are as following:
tensorflow-macos: tensorflow_macos-2.8.0-cp38-cp38-macosx_11_0_x86_64
tensor flow-metal: tensorflow_metal-0.4.0-cp38-cp38-macosx_11_0_x86_64
python: 3.8
macOS: 12.3

I have also tried to roll back tensorflow-macos to 2.7 and tensorflow-metal to 0.3.0, as well as mix&match them. Nothing worked.
Meanwhile, my M1 MacBook Pro works without any problem with the following:
tensorflow-macos: tensorflow_macos-2.8.0-cp39-cp39-macosx_11_0_arm64
tensorflow-metal: tensorflow_metal-0.4.0-cp39-cp39-macosx_11_0_arm64
python: 3.9
macOS: 12.3

Since intel Mac does not have cp39 version for tensorflow-metal, I have no way to test if it is a TF2 problem, metal problem or a macOS 12.3 problem.


Shaocs paishare

Coverage decreased (-22.7%) to 49.451% when pulling 96f838ea212a352e1b637bfc5aa530e7a9362d0f on shaocs-paishare into 0922795c2e6c5c58e00a5e697e24f7c209525fbf on paishare.


[Core Branding] Update Drop Down Menu Button Divider

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

For the dropdown menu buttons, we want to change the divider color to match the appBG.

Context
cc @shawnborton, would you prefer the line to be filled with appBG or that the line is transparent?

Hmm if the line is transparent, what happens? Does the BG show through? Otherwise I think just using appBG works as well.

Here's 1px appBG

Here's 1px with transparent (there's a block underneath it that's appBG colored, so no text shows through)

I think the appBG fill ends up looking a little sharper anyways

Oh nice, thanks for breaking this down. I agree, let's go with appBG then!

This issue has not been updated in over 15 days. @shawnborton, @grgia eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

@shawnborton, @grgia, this Monthly task hasn't been acted upon in 6 weeks; closing.
If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.


Reenable cuda apriltags

Re-enable building cuda apriltags, since we'll want to try them for 36h11 tags
Add latest libraries extracted from ros2 containers, update the code to use them
Clean up assorted unused includes and cmake/package.xml dependencies

Quick test on Jetson showed that it compiled and ran, so merging


History screen. The opening of the transaction details is quite slow while list data is fetching.

Prevent opening transaction details when the next page data request is not finished yet

Possibility to open details while loading next page is blocked. Issue is fixed.


Split Bill - Error appeared only on one device out of two

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
Precondition:
Main device is Android app and secondary device is Web

Log in with the same account in the main testing device and a secondary device
Disable the internet connection in the main testing device
In the secondary device Split a bill with 2 users, this should create a new group and 2 new 1:1 conversations
In the main testing device (should be offline) create the SAME split bill with the 2 users
Enable the internet connection in in the main testing device, the split bill request will be sent and will get a response an error.

Expected Result:
The error should be appeared on both devices.
Actual Result:
The error appeared only on one device out of two
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/207970925-935d09f7-fb57-48cb-bef7-58abb9cc2af6.mp4
https://user-images.githubusercontent.com/93399543/207970932-356cc78d-eeb8-470a-86dd-c607819e478b.mp4

Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

QA team found issue when executing TestRail Steps https://expensify.testrail.io/index.php?/tests/view/3007899

This is the expected behavior. Only the main device (the one that was offline) should see the error since the Split Bill request succeeded on the main device. Closing!

Actually, gonna reopen to update the test. @kbecciv can you update step 5 to read:
5. Enable the internet connection in the main testing device. The split bill request will be sent and you will get an error in the main device only.

@kbecciv bump!

I edited the steps for the test case above. We are all good here. Closing.

@luacmartins Thank you for doing this, I don't have the power to update the TestRail.


Safari 8 Performance bug fix

Safari on iOS 8 devices was choking on the performance variable. This will allow it to still work.

Coverage remained the same at 100.0% when pulling 7472f06f9285551e045ced86cecf3b996884477d on BoldBigflank:bugfix/safari-8-performance into 21e19c1623a09a14758f3636bbb5da2dc2d72365 on straker:master.

Sorry, you'll have to rebuild and push. One of these days I need to figure out how to handle these built files better.

done

Perhaps something like Travis CI could do the building of built files before each deploy, then you only need to show your changes in the source files. I like bitbucket pipelines for stuff like this but idk what the non-bitbucket method is.


notebook cannot open .npz file

This notebook does not appear to be able to run in Watson Studio.
The *.npz files created in getdata.ipynb would need to be loaded somehow, else we get an error[1].
I tried loading them to the nodebook as object data, but get an error since the streamingdata format doesn't work as well [2].
[1]
FileNotFoundError                         Traceback (most recent call last)
 in ()
1
----> 2 train_datatrain_d  = np.load("githubtrainingdatacompressed.npz")
3 test_data = np.load("githubtestdatacompressed.npz")
/opt/conda/envs/DSX-Python35/lib/python3.5/site-packages/numpy/lib/npyio.py in load(file, mmap_mode, allow_pickle, fix_imports, encoding)
368     own_fid = False
369     if isinstance(file, basestring):
--> 370         fid = open(file, "rb")
371         own_fid = True
372     elif is_pathlib_path(file):
FileNotFoundError: [Errno 2] No such file or directory: 'githubtrainingdatacompressed.npz'
[2] AttributeError: 'StreamingBody' object has no attribute 'seek'

fixed


Issue #000 fix: Fixed get relation metadata from node

Codecov Report

Merging #512 into release-2.1.2 will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release-2.1.2     #512   +/-   ##
================================================
  Coverage            32.11%   32.11%
  Complexity            1220     1220
================================================
  Files                  172      172
  Lines                15118    15118
  Branches              2399     2399
================================================
  Hits                  4855     4855
  Misses                9537     9537
  Partials               726      726

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 3c48a7f...167758c. Read the comment docs.


Post Y9999 dates, gmtime error checking, argc > 1 default codepath

Account for post-Y9999 dates

./ud<PHONE_NUMBER>9999999999 segfaults because gmtime() returns NULL, check for gmtime() failures
Allocate space for large year numbers (the maximum that gmtime will allow is 10 bytes)

Make argv > 1 the default code path (Removes a layer of nesting)
Replace print_version() with a printf() call
Move date_string_to_unix_day() error handling into date_string_to_unix_day() (Which allows for the direct returning of the unix day).

Great, thanks! Merged.

The C program still has some surprising behavior, though.
Here is a quick test:
% python -c 'import os; [print("9" * x + ": " + str(os.system("./ud " + "9" * x))) for x in range(1, 30)]'
1970-01-10
9: 0
1970-04-10
99: 0
1972-09-26
999: 0
1997-05-18
9999: 0
2243-10-16
99999: 0
4707-11-28
999999: 0
29349-01-25
9999999: 0
275760-09-12
99999999: 0
2739877-01-02
999999999: 0
27381040-01-26
9999999999: 0
273792670-09-12
99999999999: 0
ud: Date conversion failed: Value too large for defined data type
999999999999: 256
ud: Date conversion failed: Value too large for defined data type
9999999999999: 256
ud: Date conversion failed: Value too large for defined data type
99999999999999: 256
ud: Date conversion failed: Value too large for defined data type
999999999999999: 256
ud: Date conversion failed: Value too large for defined data type
9999999999999999: 256
ud: Date conversion failed: Value too large for defined data type
99999999999999999: 256
ud: Date conversion failed: Value too large for defined data type
999999999999999999: 256
1969-12-31
9999999999999999999: 0
1969-12-31
99999999999999999999: 0
1969-12-31
999999999999999999999: 0
1969-12-31
9999999999999999999999: 0
1969-12-31
99999999999999999999999: 0
1969-12-31
999999999999999999999999: 0
1969-12-31
9999999999999999999999999: 0
1969-12-31
99999999999999999999999999: 0
1969-12-31
999999999999999999999999999: 0
1969-12-31
9999999999999999999999999999: 0
1969-12-31
99999999999999999999999999999: 0

After some quick debugging, this seems to be a result of a error from strtoll
This is solved by checking errno after strtoll is called
    int64_t date_flag = strtoll(argv[1], &end, 10);
    if (errno == ERANGE)
        err(EXIT_FAILURE, "Date conversion failed");

Another way of checking this would to see if strtoll returns LLONG_MAX (gmtime can't parse that ,and this also wouldn't require to include errno.h)
    int64_t date_flag = strtoll(argv[1], &end, 10);
    if (date_flag == LLONG_MAX)
        err(EXIT_FAILURE, "Date conversion failed");

I added you as a collaborator, btw, in case you want to make improvements without going the route through PRs.


[WIP] Refactoring

Hi,
I started refactoring the library (I want to adapt later to stream local files :smile: ).
The first goal is to split the different components (to make it nicer and more testable) and then add more features.
I already refactored mdns (chromecast discovery) and I plan to refactor the communication stack soon (already started with protocol).
What do you think?
Should I better make a fork, or work on this? (I will let the "old" libraries there to preserve backward compatibility)

Hey, looks like a good goal to aim for. However, the project was primarily intended just to function as a command line tool that I needed, so I'm not particularly interested in developing it out as a library in itself (which requires more tedious stuff like docs, etc!), so feel free to fork it.
Might also be worth picking a better name, eg 'libgocast', to make it clearer it's a standalone library? That way command line clients, etc could import the library.

Thanks for your reply!
Then I will just do a fork of your work (under the same license) : https://github.com/oliverpool/go-chromecast.
My first goal is to have a command line tool to stream local videos, but I will try to structure the code for it to be easily reusable as a library!


The taxes have to be detected based on the shipping addresses and not based on the billing addresses.

1. Why is this change necessary?
The taxes have to be detected based on the shipping addresses and not based on the billing addresses.
2. What does this change do, exactly?
Change the tax detection rules to use the shipping and not the billing addresses.
3. Describe each step to reproduce the issue or behaviour.
When you have a billing and a shipping address as a customer inside different countries, the tax will be detected based on the billing address. This is false - it must be detected based on the shipping address.
4. Please link to the relevant issues (if any).
5. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hi @acris-cp, thank you very much for your PR.
This issue was already fixed in the 6.2 and will be released with the first 6.2 patch release.
You can track it here:
NEXT-8287
Therefore I'm closing you PR, but keep on the good work !


Avoid passing options parameter to a couple of methods

Passing large hashes around makes it very unclear what the method is actually using it for: if it just wants one or two values, better to extract them explicitly.

Failure seems legit...
https://github.com/ManageIQ/manageiq/pull/6793/files#diff-74635bd5d74cef5b820c9c144dc62592R67 needs to be removed, I think.


Streaming data

Hi --,
is streaming data through pipes supported to avoid disk IO?
In AWS I can do
aws s3 cp s3://rds-bucket/backup ‐ | aws s3 cp - s3://mybucket/backup
Is this also supported by ossutil? I've tried but no success so far. Any plans to support it?

Hi --,
is streaming data through pipes supported to avoid disk IO?
In AWS I can do
aws s3 cp s3://rds-bucket/backup ‐ | aws s3 cp - s3://mybucket/backup
Is this also supported by ossutil? I've tried but no success so far. Any plans to support it?

Hi, pipeline command operator belongs to the linux shell command, as long as it meets the requirements of the pipe, it can be used. And CLI team will not change the output format for the time being. About ossutil, it is not the part of CLI project now, so we don't know the plan of ossutil.


Generalize the usage of LoopTilingAndDistributionInfo

Request description
The LoopTilingAndDistributionInfo structure is used in multiple places to pattern-match the tile and distribution loops. There is a plan to change the distribution loop nest by some explicit op, and this structure's usage also needs to be considered.
The effort is to fill the gap between IREE and the upstream way by generalizing the information represented by the structure. The best result would be to remove the structure completely.
What component(s) does this issue relate to?
Compiler
Additional context
No response

This isnt needed anymore. Closing


NGC_API_KEY variable is not set

When I try to compose the multi_turn_rag, I get the warning:
 WARN[0000] The "NGC_API_KEY" variable is not set. Defaulting to a blank string.  Cannot connect to the Docker daemon at unix:///Users/efealioksuz/.docker/run/docker.sock. Is the docker daemon running?.
Now, I have got my NVIDIA API key and export it as an environment variable as explained in the readme.file of multi_turn_rag;
export NVIDIA_API_KEY="nvapi-<...>".
However, I don't see any explanations about  "NGC_API_KEY", and where to get that.

See prerequisites: https://github.com/NVIDIA/GenerativeAIExamples/tree/main/RAG/examples/advanced_rag/multi_turn_rag#prerequisites

Steps has been provided in the README  file under NVIDIA/GenerativeAIExamples ( https://github.com/NVIDIA/GenerativeAIExamples/blob/main/README.md )
Get your NVIDIA API key.
Go to the NVIDIA API Catalog.
Select any model.
Click Get API Key.
Run:
export NVIDIA_API_KEY=nvapi-...


[linux] Cleanup npl layer in linux port.

Some minor cleanup to linux port to follow npl include patterns better.
This also fixes a build issue in the npl/example apps.
This PR is prepared as an addendum to #168.

@andrzej-kaczmarek or @ccollins476ad, can this and #168 be considered for merge?  They are small changes that only affect the Linux port and have been in the queue for 2 months.  Thank you.


Add complete support for Java annotations in SemanticDB

This PR expands the SemanticDB spec to allow for representing Annotation AST's (incl. parameters) by introducing two new types to the Tree family: AnnotationTree and AssignTree.
As AnnotationTree is binary compatible with the Annotation type, this proposal deprecates Annotation in favour of AnnotationTree, replacing its usages in SymbolInformation and AnnotatedType. Alternatively, I would also be open to adding Annotation to the Tree oneof instead, if source-level backwards compatibility is also strongly desired.
The specification doc is updated to include some more examples, given the new capabilities to also model the parameters of annotations.
Working example of rendering annotations from the structures built via the changes in this PR can be found at https://github.com/sourcegraph/lsif-java/pull/148

still relevant?

still relevant?

We've been using this in https://github.com/sourcegraph/scip-java for the past ~2 years, along with https://github.com/scalameta/scalameta/pull/2292 which also has not been merged here yet

I think the issue was the Scala binary+source-incompatible change and we never really settled if it's ok to break it. I think the biggest issue would be with Scalafix, @bjaglin do you think the breaking change for semanticdb in this PR might cause issues for Scalafix?
Maybe we could keep Annotation at least as an existing class and just AnnotationTree as a completely new thing? This might break some logic, but not break binary compat.

That change looks non-breaking from a Scalafix perspective as ScalaPB classes are not leaking to the public Scalafix API (they are all converted to case classes manually-defined in scalafix.v1).
When parameters are actually filled by semanticdb-scalac (since they don't seem in this PR?), we'd have to see if it is possible to expose scalafix.v1.AnnotationTree through  scalafix.v1.AnnotatedType in a smooth way, but that's another story.

Not sure though how things are protobug compatible

AnnotationTree, at the protobuf byte-level, is essentially just an extension of Annotation: the latter had a field at index 1 of type Type, the former also has a field at index 1 of type Type and an additional (repeated) field at index 2 of type Tree. So long we're not changing the type of any existing fields of Annotation in AnnotationTree to something that is recursively of a different type (as type names don't matter here, only their byte representation), then itll deserialize successfully. Hope that answers the question 🙂

does this mean we don't need to create a new type, and can stick with the old one? protobuf is backwards-compatible when it comes to adding new fields, is our usage of it as well?

Not sure though how things are protobug compatible

AnnotationTree, at the protobuf byte-level, is essentially just an extension of Annotation: the latter had a field at index 1 of type Type, the former also has a field at index 1 of type Type and an additional (repeated) field at index 2 of type Tree. So long we're not changing the type of any existing fields of Annotation in AnnotationTree to something that is recursively of a different type (as type names don't matter here, only their byte representation), then itll deserialize successfully. Hope that answers the question 🙂

does this mean we don't need to create a new type, and can stick with the old one? protobuf is backwards-compatible when it comes to adding new fields, is our usage of it as well?

I guess technically? I dont remember if there was a reason beyond having the naming more aligned with the rest of the *Tree types, its been a while since this was opened.
This change is byte compatible, yes, but not source compatible. Scala code would most likely complain as theyre different types in the generated code, but programs using either the old or the new schema can communicate with each other just fine


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-30-main" workflow

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

Questions ?
Please refer to the Backport tool documentation


Generate OpenApi swagger at build time.

Description
I am wondering if there is a way to generate the swagger file at BUILD time from OpenApi attributes.
We are working on a project that involves a lot of Azure Functions and we use NSwag to generate HttpClients for them. However, we have to do this manually every time because we need to run the functions and get the OpenAPI document first.
Is there a better solution for this? I would appreciate any suggestions or tips. Thank you very much.

I've also been looking for this


Remove initializers and finalizers?

Post-render hooks allow us to attach initializers and finalizers.

The problem is that it pushes a declarative solution into an imperative one best done by jQuery. Maybe that's what 0.5 wants to be and maybe that's what we have to do in this release, but I mentioned it to @puffnfresh and he did not like the idea of removing these -- let's chat more tomorrow when he's in the office (and get @garyb and @cryogenian's feedback, too).

I do think we need a better solution here, I'm not sure exactly what that looks like but it will be influenced by whatever comes out of #138. Post-render hook is a global imperative solution, what I'd really prefer is a local declarative solution.

I'm not necessarily sure there is a better solution than post-render hooks, as for the kind of initialization we use these for we need an element in the DOM to actually exist.

Well, what if Initializer i was changed to Initializer (HTMLElement -> i), for example? The library can take care to call it after the element in the DOM actually exists.


Added code to produce plot of calibration curve, calibration score code stub

This MR was mostly for me to check my understanding of how calibration curves get drawn for regression models, but I figured it would be useful to have a function in the repo for future experiments. I'd love a check to make sure I'm understanding/creating these correctly

Yeah this is exactly right for Gaussian data. You should be able to generalize this to any probability distribution over the output.


Add functions to get password/group file entry

Move getpwuid_r extern to unix level
Add struct group
Add getgrnam(),getgrgid(),getpwuid(), getpwnam(),setpwent(),getpwent(),endpwent(),

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks!


Live switching not working

Doing a rebuild switch, will create the dirs but not create the bindfs mounts.
Not sure if this is just a me issue because I use nixus, or if anyone else have this as well.

Logs
Jan 21 12:54:32 eos systemd[1]: Stopped Home Manager environment for eyjhb.
Jan 21 12:54:33 eos systemd[1]: Starting Home Manager environment for eyjhb...
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating home-manager configuration for eyjhb
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Starting home manager activation
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating checkFilesChanged
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating checkLinkTargets
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating unmountPersistentStoragePaths
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating createAndMountPersistentStoragePaths
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating writeBoundary
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating installPackages
Jan 21 12:54:33 eos hm-activate-eyjhb[20968]: replacing old 'home-manager-path'
Jan 21 12:54:33 eos hm-activate-eyjhb[20968]: installing 'home-manager-path'
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating linkGeneration
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Cleaning up orphan links from /home/eyjhb
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Creating profile generation 415
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Creating home file links in /home/eyjhb
Jan 21 12:54:34 eos hm-activate-eyjhb[20751]: Activating onFilesChange
Jan 21 12:54:34 eos hm-activate-eyjhb[20751]: Activating reloadSystemd
Jan 21 12:54:34 eos hm-activate-eyjhb[20751]: The user systemd session is degraded:
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]:   UNIT                                                          LOAD   ACTIVE SUB    DESCRIPTION
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]: ● bindMount--state-home-config-Element-.service                 loaded failed failed Bind mount '/state/home/.config/Element' at '/home/eyjhb/.config/Element'
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]: ● bindMount--state-home-config-Transmission-Remote-GUI-.service loaded failed failed Bind mount '/state/home/.config/Transmission Remote GUI' at '/home/eyjhb/.config/Transmission Remote GUI'
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]: LOAD   = Reflects whether the unit definition was properly loaded.
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]: ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]: SUB    = The low-level unit activation state, values depend on unit type.
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]: 2 loaded units listed.
Jan 21 12:54:34 eos hm-activate-eyjhb[20751]: Attempting to reload services anyway...
Jan 21 12:54:34 eos hm-activate-eyjhb[21224]: Starting: wmsetup.service bindMount--state-home-config-Transmission-Remote-GUI-.service bindMount--state-home-config-Element-.service bindMount--state-home-config-TestTest-.service
Jan 21 12:54:34 eos hm-activate-eyjhb[20751]: Activating runUnmountPersistentStoragePaths

Logs
Jan 21 12:54:32 eos systemd[1]: Stopped Home Manager environment for eyjhb.
Jan 21 12:54:33 eos systemd[1]: Starting Home Manager environment for eyjhb...
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating home-manager configuration for eyjhb
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Starting home manager activation
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating checkFilesChanged
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating checkLinkTargets
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating unmountPersistentStoragePaths
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating createAndMountPersistentStoragePaths
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating writeBoundary
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating installPackages
Jan 21 12:54:33 eos hm-activate-eyjhb[20968]: replacing old 'home-manager-path'
Jan 21 12:54:33 eos hm-activate-eyjhb[20968]: installing 'home-manager-path'
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Activating linkGeneration
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Cleaning up orphan links from /home/eyjhb
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Creating profile generation 415
Jan 21 12:54:33 eos hm-activate-eyjhb[20751]: Creating home file links in /home/eyjhb
Jan 21 12:54:34 eos hm-activate-eyjhb[20751]: Activating onFilesChange
Jan 21 12:54:34 eos hm-activate-eyjhb[20751]: Activating reloadSystemd
Jan 21 12:54:34 eos hm-activate-eyjhb[20751]: The user systemd session is degraded:
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]:   UNIT                                                          LOAD   ACTIVE SUB    DESCRIPTION
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]: ● bindMount--state-home-config-Element-.service                 loaded failed failed Bind mount '/state/home/.config/Element' at '/home/eyjhb/.config/Element'
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]: ● bindMount--state-home-config-Transmission-Remote-GUI-.service loaded failed failed Bind mount '/state/home/.config/Transmission Remote GUI' at '/home/eyjhb/.config/Transmission Remote GUI'
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]: LOAD   = Reflects whether the unit definition was properly loaded.
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]: ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]: SUB    = The low-level unit activation state, values depend on unit type.
Jan 21 12:54:34 eos hm-activate-eyjhb[21222]: 2 loaded units listed.
Jan 21 12:54:34 eos hm-activate-eyjhb[20751]: Attempting to reload services anyway...
Jan 21 12:54:34 eos hm-activate-eyjhb[21224]: Starting: wmsetup.service bindMount--state-home-config-Transmission-Remote-GUI-.service bindMount--state-home-config-Element-.service bindMount--state-home-config-TestTest-.service
Jan 21 12:54:34 eos hm-activate-eyjhb[20751]: Activating runUnmountPersistentStoragePaths

Hm, this says that the services fail, but doesn't really point at what caused it. Do the logs for the failed unit say anything?

Hm, this says that the services fail, but doesn't really point at what caused it. Do the logs for the failed unit say anything?

Couldn't find any logs that said anything more than that sadly...
Might also just be a issue I am having.
Do rebuild switch work for you @talyz ?

Couldn't find any logs that said anything more than that sadly...
Might also just be a issue I am having.
Do rebuild switch work for you @talyz ?

I've had issues with two of my mounts recently, and I found the likely causes. I've opened #38 to solve them. Maybe it's the same thing causing yours? Could you try it out?

I've had issues with two of my mounts recently, and I found the likely causes. I've opened #38 to solve them. Maybe it's the same thing causing yours? Could you try it out?

I will try on my next reboot, I have switched to the version that does symbolic linking again :)

I will try on my next reboot, I have switched to the version that does symbolic linking again :)


e2e: disable flaky etcd scale tests.

We've seen issues scaling the cluster up:
https://jenkins-kube-lifecycle.prod.coreos.systems/job/bootkube-pr-e2e-selfetcd/417/consoleFull
and scaling the cluster down:
https://jenkins-kube-lifecycle.prod.coreos.systems/job/bootkube-pr-e2e-selfetcd/406/consoleFull
(many more examples seen).
Until these issues are investigated and resolved out-of-band, disabling these tests to make submitting PRs less difficult. The tests will still stand up self-hosted clusters, so basic functionality is still covered. This is just the scaling functionality.
cc @hongchaodeng @xiang90

coreosbot run e2e

the e2e-selfetcd test failed. in this case it took ~60 seconds for the apiserver to come back instead of 30.
i'll work on developing a better checkpointer test exit criteria tomorrow.

cc @hongchaodeng @xiang90 just as heads up

oh  nm. already been pinged. sorry.

I'll hold off on this while we see if the quorum read flag added in #655 alleviates the issue.

do we have an issue tracking these disabled tests? so we can continue our discussion on the fix there.

do we have an issue tracking these disabled tests? so we can continue our discussion on the fix there.

@xiang90 I'll open one if I end up merging this PR.

Disabled scale-up in #654, filed #656 to track it. Leaving the rest of the tests enabled for now.


Azure OpenAI: 2023-02-15-preview support

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.AI.OpenAI


Enhance Debezium Data connector documentation

[x] Typo (arvo)
[x] Parameters in a table
[x] Add admonition about acceleration being required
[x] Link to acceleration documentation
[x] Add section describing secrets. Use the section from the spark documentation as inspiration

Page should have:

[x] Connector description
[x] Configuration section
[x] Secrets section / Authentication section
[x] Examples section
[x] Parameters table
[x] File format support (if applicable)

Replaced by #584


📋 [TASK] - Improvement to Lexeme Class

Parent Feature
#914
Task Description
As an AaC Developer, I want to implement the identified improvements for the Lexeme Class, so that I provide a reliable and useful tool for end users.
Acceptance Criteria

[ ] Lexeme class is modified as necessary to better support utilization.
[ ] Unit tests for the Lexeme class are updated.
[ ] Documentation about utilizing Lexemes is added to the Developer's Guide.

Unresolved questions
No response

The changes that are needed are not in the Lexeme class itself.  The lexeme class does not really have much in it, so the things that need to change are in its implementation and use by Language Error and parsing.


Queue name length and maximum message size

The queue name length limitation of 80 characters is a big issue for me.  I create queues that are based on the value of a JWT token and so these exceed the 80 character limitation.  Can this be overridden or just be made bigger?
Also the maximum message size of 65536 can be too small in some cases.  Can the maximum be overridden or increased?

No, it was missing tests and updated docs. And as it was just one like i quickly added that.


Fix #115 update detector mask for affect times

Codecov Report

Merging #183 (b516910) into master (2716443) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #183      +/-   ##
==========================================
+ Coverage   85.27%   85.30%   +0.03%
==========================================
  Files          50       51       +1
  Lines        4373     4362      -11
==========================================
- Hits         3729     3721       -8
+ Misses        644      641       -3

Impacted Files
Coverage Δ

stixcore/products/level0/scienceL0.py
83.53% <100.00%> (+0.28%)
:arrow_up:

stixcore/config/config.py
96.15% <0.00%> (-3.85%)
:arrow_down:

stixcore/io/soc/manager.py
86.66% <0.00%> (-1.67%)
:arrow_down:

stixcore/ephemeris/manager.py
90.51% <0.00%> (-1.11%)
:arrow_down:

stixcore/processing/L0toL1.py
69.69% <0.00%> (-0.80%)
:arrow_down:

stixcore/time/datetime.py
91.11% <0.00%> (-0.10%)
:arrow_down:

stixcore/data/test.py
100.00% <0.00%> (ø)

stixcore/util/singleton.py
83.33% <0.00%> (ø)

stixcore/products/product.py
80.50% <0.00%> (+0.62%)
:arrow_up:

stixcore/io/fits/processors.py
91.49% <0.00%> (+2.16%)
:arrow_up:

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 2716443...b516910. Read the comment docs.

Closes #115


Fix kubectl exec commands

#99 modified the Nokia SRL CLI command with incorrect syntax.  I do not have a CPTX image to test against but it looks like it was modified the same way.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 63.398%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1474

Relevant Lines:
2325

💛  - Coveralls


"Download File" button doesn't work at all after creating new wallet

NEX Extension version:
0.1.7
Browser:
Chrome 65.0.3325.146 (64 bit)
Reproduction steps:

Install Nex extension
Create new account
Create new wallet
Press "Download File" button

"Download File" button doesn't work at all.

+1 - manually saving and entering the last digits in the next step doesn't work also.

+1 having the same issues as well. Running Chrome Version 65.0.3325.162 on Mac. After clicking to continue, i have a confirm last 4 digits of the PK and then a blank page.


[emacs] No longer able to use melpaUnstable from nixos-unstable in a stable Emacs

Issue description
Previously, one could do:
{
  myEmacs = (pkgs.emacsPackagesNgGen pkgs.emacs25).emacsWithPackages (epkgs:
    # MELPA Unstable @ NixOS Unstable (bleedingest edge)
    (with (pkgs.nixos-unstable.emacsPackagesNgGen base).melpaPackages; [
      dante
      hayoo
    ])
    ++
    (with epkgs.melpaStablePackages; [
      # … regular stable packages here …
    ])
  );
}

Now, this fails with:
*-dante-emacs-*/nix-support/setup-hook: line 10: addEnvHooks: command not found

Cf. https://github.com/michalrus/dotfiles/commit/e6882789cd0c685b1e35df67e78e0e936c4269f7 — it worked on 1bc288591ea4fe3159b7630dcd2b57733d80a2ff, doesn’t work anymore on f607771d0f5e4fa905afff1c772febd9f3103e1a.
How to do it now?
Technical details

system: "x86_64-linux"
host os: Linux 4.9.75, NixOS, 17.09.2683.360089b3521 (Hummingbird)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 1.11.16
channels(root): "nixos-17.09.2683.360089b3521"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

@michalrus Are you still having this issue? I believe it's been fixed since.

@mattbillenstein, no, this still happens with Emacs from the newest 17.09.2905 c1d9aff56e0 and MELPA Unstable from the newest nixos-unstable 2e4aded366914d625a2f31208e8ac8548cb43a7e:
building path(s) ‘/nix/store/1nj6lchp5wjhsv4y9kda07h67sxncf18-emacs-packages-deps’
/nix/store/2l3kdnzvavyzdzyr3pz5spsqkrxi92lk-emacs-ensime-20171217.1730/nix-support/setup-hook: line 10: addEnvHooks: command not found
builder for ‘/nix/store/v42za5qxfjd1w11m44hjawarjiryg9sa-emacs-packages-deps.drv’ failed with exit code 127
cannot build derivation ‘/nix/store/7a6mfk6za3iwn6r307bqq80m6spl2n91-emacs-with-packages-25.3.drv’: 1 dependencies couldn't be built

Don't have time to look myself, but probably https://github.com/NixOS/nixpkgs/commit/0f925943fdeafd7f6813488aac587e9c989e6e91 needs to be cherry-picked to 17.09

@michalrus could you please test this on 18.03?


Multi-Policy Coverage

This is to be defined. Envision to define @Pyatakov Max, Wes, Serg.
I am a project and I want to conform to two or more policies such as Verra and Gold Standard REDD+ from separate "Methodologies" that are similar. In order to avoid double counting but create a high quality token I would do a certain amount extra work to make sure it conforms.

There are two approaches to this that initially come to mind. One is a labeling system. For example, Verra has a labelling system where VCUs may be labeled with additional standards and certifications on the Verra registry where both the VCS Program and another standard are applied. One interesting label they are currently working on is to show conformance with the requirements of Article 6 of the Paris Agreement, finalized at COP26. In that case, Project Proponents would submit additional documentation showing conformance with Article 6’s requirements, generally prior to VCU issuance.
So perhaps our solution could have a similar functionality, where offset tokens can have additional labels. The labels would having their own requirements and schema (like a sub-policy), with redundancies removed. These labels could be sort of modules of the main policy/methodology. Users could sort of construct customized policy variations, with variations such as VCS-REDD-APD-Article 6, with VCS being the main standard, REDD being the specific methodology, APD being the project activity, and Article 6 being the label.
Another approach could be separate merged policies. For example, there could be the option to select a Verra policy, a Gold Standard policy, or a Verra-Gold merged policy that covers both. If the project proponent wishes to show compliance with both, they would select the Verra-Gold merged policy.
One potential issue I see with combining Verra and Gold standard is that if a project is processed and issued VCUs through Verra as the root authority, the project VVBs and Verra may not have the authority to also verify the project against Gold Standard, unless perhaps the VVB has both Verra and Gold standard credentials.

Under constraint of using 'multi-sig' for the implementation of this functionality only the following design is feasible: multi-policy compliant tokens are only possible when there is one 'main' Standard Registry (SR) and (multiple) other 'secondary' SRs such that:

The 'main' SR would need to know in advance that its policy is designated to be 'main' in a multi-policy situation (and thus designed accordingly) and instead of minting logic would create a multi-sig contract for minting the token
The 'secondary' SRs' policies are dependent on the 'main' SR's policy that they 'contribute' signatures to the minting of a token (but don't mint their own) and they are MRV 'data input' compatible with the main policy. In practice this means that 'secondary' policies must use the same MRV schema as the 'main' policy, and use exactly the same aggregation block (or have aggregation is prohibited completely in both main and secondary policies.

The implications of the above on business case are that this would facilitate the creation of 'ecosystems' of SRs grouped around 'main' SRs, rather than bringing the main SRs closer together. This is because there is this 'main'-'secondary' dichotomy, the SRs in this model cannot be independent and of equal standing. This also means that 'secondary' SRs/policies will only have discretion to approve a subset of tokens that have been minted or submitted for minting by the 'main' SRs, i.e. they don't have the facility to approve 'more' because they don't mint any tokens of their own. Thirdly, if the multi-sig synchronisation is done in real time before  the mint of the token these 'secondary' SRs would effectively have veto powers over minting the token by 'main' SR. I think this means they should be able to 'join in' after the fact - i.e. sign already minted tokens to register their (token) compliance with their (SRs') additional requirements.


Device Request - [Zigbee Temperature and Humidity sensor] - [	_TZE204_cirvgep4] / [TS0601]

Prerequisites:

Before requesting a device addition, please ensure there is not already a request for the device among the open issues.
Make sure your Homey is upgraded to firmware v5 or higher.
You need a physical example of the device.

Device Information
Manufacturer: _TZE204_cirvgep4
Device ID: TS0601
Product Name: Zigbee Temperature & Humidity Sensor
Device ID: bf6d04f50fe2f2f89bvef1
Product Category: wsdcg
Device Description: Temperature and Humidity sensor
Link to device Image (Aliexpress): https://nl.aliexpress.com/item/1005006861229185.html
Device Interview
[
  {
    "code": "temp_unit_convert",
    "value": "c"
  },
  {
    "code": "maxtemp_set",
    "value": 40
  },
  {
    "code": "minitemp_set",
    "value": 10
  },
  {
    "code": "maxhum_set",
    "value": 90
  },
  {
    "code": "minihum_set",
    "value": 20
  },
  {
    "code": "switch",
    "value": true
  }
]

Additional Comments:
I will submit some more devices i have, work in Tuya app, not in Tuya clud for Homey.
If you need more information please contact me.
Best Regards Hakob.

Note: Provide any other relevant information or requests related to the device. Link to where you bought the device can be of help

How to interview a device

Add the device as a generic Zigbee device in Homey
Navigate to https://developer.athom.com/tools/zigbee.
Interview the device, the button for this is to the right of the device in the list of Zigbee units.
Click the copy button/icon to capture the device information.
Paste the copied information above.

Note: To be able to add more devices to the Tuya Zigbee app, we rely on community members like you to provide interviews of the devices you want to be added. Thank you for your contribution!

Hi @HakobDongian, I still need a comlete interview: https://developer.athom.com/tools/zigbee
Add device as generic Zigbee, go to dev tools, press the dots to the right of your device in the list and then press interview. Push the pair button on your device every other second until interview is complete, press copy button and paste it here.


Added Particles.js in background

Related Issue

Info about Issue or bug

fix #5300
Describe the changes you've made
A clear and concise description of what you have done to successfully close your assigned issue. Any new files? or anything you feel to let us know!
Checklist:

[ ] My code follows the style guidelines of this project.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.

Screenshots

@sairish2001 kindly review the changes

@sairish2001 I have added in newdesign.html pages if this looks fine to you then should i add it in index.html page ?

No need, soon we will shift this into index.html, as soon as all the sections will Organized

No need, soon we will shift this into index.html, as soon as all the sections will Organized

Okay :)

https://user-images.githubusercontent.com/67696867/123470375-f0f04b80-d611-11eb-8517-ef7a82bc260d.mp4
@sairish2001 Have a look at this particles design

https://user-images.githubusercontent.com/67696867/123470375-f0f04b80-d611-11eb-8517-ef7a82bc260d.mp4
@sairish2001 Have a look at this particles design

No this, not looks that much good

record_000004.mp4
@sairish2001 Have a look at this particles design

No this, not looks that much good

Okay


Unknown field (settings)

Hi,
I'm having this issue "Unknown field (settings) on table members". The field settings exist on the table members.
if I remove this code in Glorand\Model\Settings\Traits\HasSettingsField
if (!$this->hasSettingsField()) {
throw new ModelSettingsException("Unknown field ($settingsFieldName) on table {$this->getTable()}");
 }

it will work fine.
I am using laravel 6.9.0 and this package version 3.5.4.
Anyone has this issue?

If you look at the hasSettingsField method, you will see it like so:
    /**
     * @return mixed
     * @throws \Glorand\Model\Settings\Exceptions\ModelSettingsException
     */
    private function hasSettingsField()
    {
        try {
            return cache()->remember(
                config('model_settings.settings_table_cache_prefix') . '::has_field',
                now()->addDays(1),
                function () {
                    return Schema::hasColumn($this->getTable(), $this->getSettingsFieldName());
                }
            );
        } catch (\Exception $e) {
            throw new ModelSettingsException("Cache: " . $e->getMessage());
        }
    }

I have run into the same issue and I try to clear the cache after looking at the source and all you need to do is run php artisan cache:clear, maybe it is used for performance in production environment.

@SDCCardsDeveloper can you confirm that cleaning the cahe  (php artisan cache:clear) fixes the issue?

Hi @glorand @bagaskarawg
I've executed php artisan cache:clear and tried again but the same error result.

I had the same error:

ModelSettingsException with message 'Unknown field (settings) on table Users

Clearing the cache worked for me. 👍

close due to inactivity

I am still having this issue until this now. clearing cache does not solve this issue.

I am still having this issue until this now. clearing cache does not solve this issue.

Please update to the latest version

I am still having this issue until this now. clearing cache does not solve this issue.

Please update to the latest version
@glorand
I just updated to last version and the issue seems fixed. Thank you

I have updated to the latest version ( 3.6.5 ) and php artisan cache:clear , but I still have the same error :(
Exception Message:↵↵Unknown field (extra) on table roles

In version 3.6.5 I also have this error:
Glorand/Model/Settings/Exceptions/ModelSettingsException with message 'Unknown field (settings) on table companies'
And my co-workers as well... The only thing that really helps is remove- and require again with composer....
I will update this package now and get back with feedback if that solved my problem.

In version 3.6.7 I got the same error. But I now have a clue on what could be wrong: the model has a non-default database connection. My project has multiple database connection, hence.
This code from \Glorand\Model\Settings\Traits\HasSettingsField::hasSettingsField, does not take into account different database connections:
Schema::hasColumn($this->getTable(), $this->getSettingsFieldName());

Good thing that the Schema facade has a method that allows connections, this could be the solution:
    /**
     * @return mixed
     */
    private function hasSettingsField()
    {
        return Cache::remember(
            config('model_settings.settings_table_cache_prefix') . '::has_field',
            now()->addDays(1),
            function () {
                return Schema::connection($this->getConnectionName())->hasColumn($this->getTable(), $this->getSettingsFieldName());
            }
        );
    }

Do not forget to clear your cache (again).


Deprecation promotion of ResultContext to hidden level

Description
Like discussed in #104, we would like to promote the deprecation of the ResultContext type and its related declarations to a hidden level.
For doing so, we should also update the corresponding deprecation notices indicating that these declarations will be removed in the next major release (see issue #270).
Dependencies
This issue is blocked by the following ones:

[ ] #268

Checklist

[ ] Promote the corresponding declarations to hidden level.
[ ] Update the Unreleased section in changelog.

We will simplify our deprecations cycle to the bare minimum: STABLE - DEPRECATED - REMOVED.

We will simplify our deprecations cycle to the bare minimum: STABLE - DEPRECATED - REMOVED.

This issue should be implemented for following our evolution principles.

We are not ready to implement this change.


'FaxReceipt; does not contain a definition for 'json'

When you download the solution and try to run Phaxio.Examples.ReceiveCallback you get the error 'Phaxio.Examples.ReceiveCallback.Models.FaxReceipt' does not contain a definition for 'Json'.  In the FaxReceipt class, json is not defined.  It's an easy fix but I wanted to point it.

@jgranade Thanks for reporting this! I'm starting a fix now. I'll keep you posted on my progress.


Mobile compatibility

Is there a reason why isDesktopOnly is set to true?
I looked at the imports and didn't see a reason why it shouldn't work on mobile.

Yes, I tested the plugin on mobile, and found that it seemed to work except that it failed to detect when the cursor was inside math. (So snippets set to run outside math (such as "dm") worked, but none of the math-related functions worked.)
I'll do some debugging and try to get it working.

Added in 1.1.0.


Handle the case of completion of class member when member name is being edited

Fixes #17977

@mhegazy  can you please take a look


When to support Greenplum/postgresq

You can config by yourself follow by the guide.
https://edp963.github.io/davinci/deployment.html#3-数据源配置


[Blob] Added upload blob from url feature

its important to note that explicitly passed properties to upload_blob_from_url (such as content settings) take precedence over the properties of the source when we set include_source_blob_properties=True.


Support transparent background of images

Support RGBA for image backgrounds instead of just RGB.

Ratatui works in "immediate mode". The area covered by the image cannot be cleared, it must be set to be skipped instead, so that nothing draws over the image in the same render pass. Thus, if we would allow for transparency, artifacts of some previous render would be visible.

Also, icy_sixel does not seem to support transparency at the moment.


Script won't run with "Microsoft Storage Spaces SMP" and "Optimize Drives" services in Disabled state

On a highly optimised Windows Server 2016 build, the invoke-fslshrinkdisk script would not run correctly.
It would throw an error :
Get-RunspaceData : No MSFT_Partition objects found with property 'DiskNumber' equal to '1'.
The script requires the following two services to be set to manual state so they can be started up on demand.  They start when the script is running and we had these services set to disabled.
"Microsoft Storage Spaces SMP"
"Optimize Drives"

Thanks for writing this up Steve.


Discovery.yml Discussion

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3114
Originally created by @pnadolny13 on 2021-12-10 16:58:19

@aaronsteers and I had a conversation about the long term plan for discovery.yml so this issue is to document my understand.
Sources of truth:

Transformers/Utilities/Files/etc. = meltano repo. They will be split out into individual files for easier maintenance.
Tap/Target definitions = hub repo. There should be no difference between taps/targets and extractors/loaders - currently the env_alias is the only known customization which is a legacy feature now that all settings can be managed in environment variables using TAP_GITLAB_X syntax.

The ideal implementation in my mind is to still have a discovery.yml as part of Meltano but make it automatically generated vs a static versioned file. The goal is to allow stability for teams that want it but also have the most up to date settings by default (using the hub as a singer definition API). By keeping the discovery.yml and the current logic we still allow teams to pin their version for stability. By introducing logic to dynamically generate discovery.yml we can give users the most up to date settings by default based on MeltanoHub whenever without a release or version bump needed.
How it would work:

MRs to MeltanoHub to get settings updated for Singer plugins. MRs to Meltano for other plugins.
The current versioned discovery.yml is removed from the git repo. And tests are updated to point to  https://www.meltano.com/discovery.yml instead. The plugin_discovery_service logic is updated to generate discovery.yml as the second step if no pinned version found, meaning retrieve discovery.yml in this order: project pinned, generate a new one using MeltanoHub API latest singer definitions along with the discovery endpoint for other plugins (only parsing out non-singer plugins), plain discovery endpoint, /cache/ directory, or finally the build artifact in meltano.core.bundle (see next step).
On Meltano releases CI dynamically generates a discovery.yml and places it in the bundle directory as a build artifact. The challenge here is that the hub can be changing all the time and if the timing is bad and the hub had a mistake in settings at the time we created a meltano release then we are packaging a bad file with the release. Its probably a fine risk since generating it at runtime is the preferred workflow (see above) which would fix it or for people who really need stability theyll have it pinned so it wont matter.
MeltanoHub tap/target endpoints are versioned on every release to main so this endpoint can serve every version the users might want. We make a V2 endpoint that includes the version (UPDATE: a separate issue for the versioned singer metadata endpoint has since been opened)

This endpoint currently https://hub.meltano.com/singer/api/v1/taps.json, and returns:
[
    {
        "singer_name": "tap-csv",
        ...
        "variants": [{},...]
    }
]

The new endpoint has the version in the URI like https://hub.meltano.com/singer/api/v2/123/taps.json, and returns:
{
    "version": 123,
    "taps": [
        {
            "singer_name": "tap-csv",
            ...
            "variants": [{},...]
        }
    ]
}

I'm open to implementing it differently but the idea is that users always know what version of settings theyre running. For troubleshooting well want to know if they have the latest settings definition or at what version an issue was introduced.
Not immediately necessary but we might also want a mechanism for generating a discovery using a specific singer_definition version. Maybe meltano discovery_pin --singer_def_version 123 since on the fly generation always uses the latest version.
Ordered steps to get there:

Remove discovery.yml from git, generate as a build artifact, and fix tests to point to the endpoint. Just read split out files for now. https://gitlab.com/meltano/meltano/-/merge_requests/2456#note_761359255 does most of this already.
MeltanoHub singer_definition versioned endpoint
Update the discovery generator logic to pull from the new singer_definitions endpoint, remove all split out files from the meltano repo, update plugin discovery service to run generation code after not finding a pinned version.
meltano discovery_pin --singer_def_version 123 CLI command?

@tayloramurphy @aaronsteers What do you guys think about this?
Future Future:

I think this would be a lot more work but we could eventually just use the hub as an endpoint without generating a discovery.yml unless the user asks for it (aka meltano discovery_pin (or something). This would require a more sophisticated hub API to allow tap/target filtering etc. and meltano a tighter integration with MeltanoHub logic to not always look at the discovery.yml but rather just make API requests instead. This goes a bit in the opposite direction of decoupling from Singer more though.

View 4 previous comments from the original issue on GitLab


Issues with Semantic Segmentation on custom datasets

The way I do it in EVA or MMSegmentation is that I do 4 classes (1 background + 3), reduce_zero_label = False and ignore_index=0 in every loss function (CE and Dice in this case), I do those steps and and my training works in other libraries, is this method generally wrong as I can not train properly in ViT-Adapter with this? I am not seeing any error just extremely bad predictions at very easy task
I also have confusion with how stuff + things work, when I do 1 stuff and 3 things the num_classes goes to 5 instead of 4?
@czczup Please help

Have you solved this problem, I have a similar problem when I do semantic segmentation, there is no problem, it can be trained correctly on deit, but on beit+mask2former, the prediction in each category is close to 0

Nah, I never figured it out


train doesn't use detection's result

Hello, I found train doesn't use detection's result. But test use it.
train.py

demo.py

why ? Is the data cropped ?

Yes, all training images were cropped.


Framed Trim in 1.16+

add in Framed Trim like the other framed Variants you added since this is no longer part of the original Storage drawers on 1.16

Done in b1ea27bfad78e5e36b7ff8fc2df39d22739029b4

sweet thanks


cmake error "NORMALIZE_BOOL"

ngraph/src/ngraph/frontend/CMakeLists.txt:22 (NORMALIZE_BOOL)
Unknown CMake command "NORMALIZE_BOOL"
I build in windows, dldt-R3,  the error occurred !   how to solve , thanks!
how to solve this ?
when I turn the ngraph build off, it worked.
I change the thirdparty/CMakeLists.txt  line 52 :    #   include(ngraph.cmake)

#4295 should fix this issue.


bioinformatics evidence

This term is to use the result/conclusion from the automatic assertion as the
evidence for the next step. It is an output of the 'automatic assertion' that
used as a evidence.

I see that in ECO there are '* evidence used in automatic assertion'. I think
this term is different with what I intend to use.

The example for this term is that the bioinformatics software predicted miRNA
target will be considered as a candidate for experimental validation.

I want to include the validation criteria that a bioinformatics prediction is
one of the evidence to support the assertion of miRNA target.

I wonder if this is in the scope of ECO or not.

Please let me know. Welcome for further discussion.

Thanks,
Asiyah Yu Lin

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 12 Apr 2015 at 3:37

It appears this user did not see the tool-specific automatic assertion terms.