Reduce memory consumption of Specification NBs

Memory consumption of Specification NBs is too high.

Updates in the platform reduced the memory usage overall.


consider cluster wide configuration

maybe another config map that can be read
pass args such as tracing, kafka endpoints, otel endpoints, etc
kafka configuration

Prerequisite

Add kind field for service unit config

this should not be strictly enforced for backwards copatibility.
if not present, assume that it is service unit config with a warning

Only accept directory as hexctl arguments
Must place a file named hexagon-cluster.yaml file in the directory given as argument

Cluster Config spec

kind: ClusterConfig
All fields from pkg/api/defaults


Starter HTTP Message headers overwritten when using Message Value Setter: Request Body

Steps to reproduce

Create a Starter HTTP Message as a global variable with the contents:

POST /post HTTP/1.1
Host: <IP_ADDRESS>:9999
Content-Type: application/json
Connection: close

Create a new Rule  with a Then using Build HTTP Message: Request

Use the the starter message from step 1.
Configure a Message Value Setter which sets the Request Body to some simple text like Test
Set the destination variable

Add a Then to log the request variable from step 2.

Send a request through Burp to trigger the Rule then look in the logs.  It should be apparent that the Host and Content-Type headers from the starter message have been removed:

POST /post HTTP/1.1
Content-Length: 4

Test

Rule export
rules:
- whens:
  - !<.WhenEventDirection>
    negate: false
    useOrCondition: false
    dataDirection: "Request"
  thens:
  - !<.ThenBuildHttpMessage>
    dataDirection: "Request"
    starterHttpMessage: "{{g:TestHttpPostRequest}}"
    messageValueSetters:
    - destinationMessageValue: "HttpRequestBody"
      destinationIdentifier: ""
      destinationIdentifierPlacement: "Only"
      sourceText: "Test"
    destinationVariableSource: "Event"
    destinationVariableName: "TestRequestBody"
  - !<.ThenLog>
    text: "{{e:TestRequestBody}}"
  enabled: true
  autoRun: true
  name: "Test Dissappearing Post Headers"
webSocketRules: []
variables: []

Very interesting. It is not reproducing for me. What version of Reshaper do you have?

"extension_file":"bapps/7bcec7656b5746e9a85c427f243e6d5a/build/libs/reshaper-for-burp-2.1.0.jar"

On the Settings tab, check the box for Enable Event Diagnostics trigger the rule again, then go to the Log tab and copy the output here.
Mine looks like this:
{
  "message" : "POST /post HTTP/1.1\r\nHost: <IP_ADDRESS>:9999\r\nContent-Type: application/json\r\nConnection: close\r\nContent-Length: 4\r\n\r\nTest"
}
Request: https://example.com/
	Rule: Test Dissappearing Post Headers
				    When Event Direction('Request' equals 'Request') - PASS
				    Then Build HTTP Message(dataDirection='Request' starterHttpMessage='POST /post HTTP/1.1
Host: <IP_ADDRESS>:9999
Content-Type: application/json
Connection: close' destinationVariableSource='Event' destinationVariableName='TestRequestBody' {{message:httprequestbody}}='Test')
				    Then Log('POST /post HTTP/1.1
Host: <IP_ADDRESS>:9999
Content-Type: application/json
Connection: close
Content-Length: 4

Test')
	End Rule
End Request

Response: https://example.com/
	Rule: Test Dissappearing Post Headers
				    When Event Direction('Response' equals 'Request') - FAIL
	End Rule
End Response

{
  "message" : "POST /post HTTP/1.1\r\nContent-Length: 4\r\n\r\nTest"
}
Request: https://api.alpha-e2e.icaas.theonenetwork.ericsson.net/icaas-user-mgmt/v1/users/64d2dae0d2c89b4767fdc444/enable-user-at-login
	Rule: Test Dissappearing Post Headers
				    When Event Direction('Request' equals 'Request') - PASS
				    Then Build HTTP Message(dataDirection='Request' starterHttpMessage='POST /post HTTP/1.1
Host: <IP_ADDRESS>:9999
Content-Type: application/json
Connection: close

' destinationVariableSource='Event' destinationVariableName='TestRequestBody' {{message:httprequestbody}}='Test')
				    Then Log('POST /post HTTP/1.1
Content-Length: 4

Test')
	End Rule
End Request

Response: https://api.alpha-e2e.icaas.theonenetwork.ericsson.net/icaas-user-mgmt/v1/users/64d2dae0d2c89b4767fdc444/enable-user-at-login
	Rule: Test Dissappearing Post Headers
				    When Event Direction('Response' equals 'Request') - FAIL
	End Rule
End Response

That's very odd. Can you try a reinstall?
Otherwise, if you wish, you can try the release here by using the jar provided: https://github.com/synfron/ReshaperForBurp/releases/tag/v2.1.0
You'll need to disable the BAppStore version before installing that one. Otherwise they will conflict.

Uninstalled & reinstalled from BApp Store - Same behaviour.
Uninstalled & installed Jar from above link - Same behaviour.

Note that I changed the setter to Request URI Path and still see the headers getting removed
{
  "message" : "POST /Test HTTP/1.1\r\n\r\n"
}
Request: https://www.google.com/
	Rule: Test Dissappearing Post Headers
				    When Event Direction('Request' equals 'Request') - PASS
				    Then Build HTTP Message(dataDirection='Request' starterHttpMessage='POST /post HTTP/1.1
Host: <IP_ADDRESS>:9999
Content-Type: application/json
Connection: close

' destinationVariableSource='Event' destinationVariableName='TestRequestBody' {{message:httprequesturipath}}='Test')
				    Then Log('POST /Test HTTP/1.1

')
	End Rule
End Request

Response: https://www.google.com/
	Rule: Test Dissappearing Post Headers
				    When Event Direction('Response' equals 'Request') - FAIL
	End Rule
End Response

I just tried to run the Then Parse HTTP Message: Request on the starter HTTP message_ and can see a parsing error in the logs.

{
  "message" : "Starter Message: POST /post HTTP/1.1\nHost: <IP_ADDRESS>:9999\nContent-Type: application/json\nConnection: close\n\n"
}
{
  "message" : "POST /Test HTTP/1.1\r\n\r\n"
}
{
  "message" : "null"
}
Request: https://www.google.com/
	Rule: Test Dissappearing Post Headers
				    When Event Direction('Request' equals 'Request') - PASS
				    Then Log('Starter Message: POST /post HTTP/1.1
Host: <IP_ADDRESS>:9999
Content-Type: application/json
Connection: close

')
				    Then Build HTTP Message(dataDirection='Request' starterHttpMessage='POST /post HTTP/1.1
Host: <IP_ADDRESS>:9999
Content-Type: application/json
Connection: close

' destinationVariableSource='Event' destinationVariableName='TestRequestBody' {{message:httprequesturipath}}='Test')
				    Then Log('POST /Test HTTP/1.1

')
				    Then Parse HTTP Message('[]') - ERRORED
				    Then Log('null')
	End Rule
End Request

Response: https://www.google.com/
	Rule: Test Dissappearing Post Headers
				    When Event Direction('Response' equals 'Request') - FAIL
	End Rule
End Response

Just the defaults which came when installing

I have that fixed in https://github.com/synfron/ReshaperForBurp/releases/tag/v2.1.0-next-v2 which I haven't officially released yet.

Installed v2.1.0-next-v2  and still don't see the headers.  However, I no longer see the parse error.
{
  "message" : "POST /post HTTP/1.1\r\nContent-Length: 4\r\n\r\nTest"
}
Request: https://www.google.com/
	Rule: Test Dissappearing Post Headers
				    When Event Direction('Request' equals 'Request') - PASS
				    Then Build HTTP Message(dataDirection='Request' starterHttpMessage='POST /post HTTP/1.1
Host: <IP_ADDRESS>:9999
Content-Type: application/json
Connection: close

' destinationVariableSource='Event' destinationVariableName='TestRequestBody' {{message:httprequestbody}}='Test')
				    Then Log('POST /post HTTP/1.1
Content-Length: 4

Test')
				    Then Parse HTTP Message(dataDirection='Request' httpMessage='POST /post HTTP/1.1
Host: <IP_ADDRESS>:9999
Content-Type: application/json
Connection: close

' {{event:tmp}}='')
	End Rule
End Request

Response: https://www.google.com/
	Rule: Test Dissappearing Post Headers
				    When Event Direction('Response' equals 'Request') - FAIL
	End Rule
End Response

Gtg.
I'll test this on some other Burp installations over the coming days and make note where I'm seeing  working and broken behaviour.

T

@tomdottom Thanks for your efforts so far! Unfortunately, I'm lost on this one so far.

@tomdottom Good new. I downloaded Arch Linux and am able to reproduce the issue 😊.

That's great news.  Is it an Arch issue, or a general Linux issue?

It's actually a CRLF versus LF only issue. The spec for headers is that each header line must end in a CRLF. On Linux, the CR's are not there when copy and pasting your example starter request.  On Windows, they are there. Will need to consider the scenario with no CR.

🤦 of course.  Should have thought of that.

Reshaper is using Burp's library to get the headers from the request (HttpRequest.httpRequest(ByteArray.byteArray(request))). That returns no headers when LF is used alone. Fixing this would require not using Burp's library which will carry its own risks.

I would suggest just changing the editor.
If I could have seen \r\n when editing the stater http template I may have realised what was going on.
Or maybe there's a way to use Burps message editor?

Good suggestion. I'll see what Burp's message editor offers.

Switched to use the Burp message editor in https://github.com/synfron/ReshaperForBurp/releases/tag/v2.1.0-next-v3

The issue is addressed in Reshaper for Burp v2.2.0. The Global Variables UI has been switched to use Burp's message editor which has options to view CR and LF characters. Also added a sanity check log to warn if the missing CR situation is detected.
It will be some time for the release to reach the BApp Store because of their review process.


Cannot open the panel

Hello there,
i am having a hard time figuring out which key combination i need to press to open the control panel. Tried the one mentioned under usage but no success, using a German Keyboard Layout.

you can open the panel by clicking the new entry on main menu, or the small button aside the minimap in game, then set your own shortcut key on the panl.

So i have done something wrong since i do not have these buttons or entries.
https://imgur.com/a/Xk1XFXH

The 2 places I've mentioned above.

Yeah nothing like this available gonna re install mod manager and the mods

Okay installing everything new fixed it. Thanks for the support. Great Work


Fixes issue with incorrect order of exports in resulting package

Fixes first issue mentioned here
https://github.com/paritytech/capi/issues/990#issuecomment-1548177246

Perhaps I'm missing something, but I'm unable to tell what part of this PR fixes the (presumably webpack-related) error. Is it the DNT version bump? Can you please provide some more detail.

Gotcha, in that can you please revert all other changes. And perhaps let's add "lock": false to the deno.jsonc, as this is a lib, meant to be consumed by others who will generate their own locks.


How to download and pre-process the datasets

Hi, I included the datasets folder which was previously excluded, you can run the script create_split.py with the name of the dataset you want to download and preprocess.

Thank you very much !


Some questions about the replication of the experiment

Sorry to bother you again, Jiawei :(
I felt confused after the replication of NNSmith.
In my experiment, NNSmith generated 7686, 9730, and 23812 testcases in 4 hours for torch, ort, and TVM respectively, which exits a big difference from neuri and the report in the paper.  (In my experiment, Neuri can generate 125300 testcases for torch)
For NNSmith and Neuri, I use the docker file you provided. But I reproduced the experiment on the same linux server.
I can make sure I'm using the same hardware environment so I wonder if it's the version of NNSmith I'm using.
I found you provided two experimental instructions. One in nnsmith/experiments/README.md, the other one in docker file.
I want to know which version of the code can achieve the SOTA performance of NNSmith？
In addition, if I want to fully understand NNSmith on code aspect. Which version of the source code should I read?
Thx in advance, looking forward to your reply :D

Hi Shaoyu, thanks for your interest!
I assume you are saying in the nnsmith artifact nnsmith generate slower while in neuri's nnsmith/neuri generates much faster. IIRC this is because in nnsmith's ASPLOS artifact (as well as earlier versions of nnsmith after that), by default test-cases are generated with an image file visualizing the overall model topology using dot and graphviz. Until https://github.com/ise-uiuc/nnsmith/commit/40e725d38433535bd11544cf82a81d779ac4cca3, I turned the visualization off as I found it to be a speed bottleneck. Additionally, there has been a lot of similar optimizations and refactorings made in nnsmith after the release of the ASPLOS artifact.

I want to know which version of the code can achieve the SOTA performance of NNSmith？

That being said, I would suggest you to use the nnsmith in NeuRI's artifact if you are hoping to benchmark against the latest performance of NNSmith. Meanwhile, you may also modify the code in the ASPLOS artifact to turn off the visualization image generation. Both should work, though the first one might be the most convenient (mgen.method=symbolic-cinit is basically almost the nnsmith presented in the ASPLOS paper).
Let me know if you have more questions! Meanwhile I would suggest you to post artifact questions under the artifact repository. :D Good luck with your research!

Thx for your detailed information :)
Lastly I want to know which version of NNSmith is suitable for reading from scratch. The nightly version on GitHub?

If you want to learn about the source code implementation, the current nightly version shall be fine. Let me know if you see anything worth improving.

Thx very much indeed.,Jiawei :)
I'm looking forward to your new research work:D

You are welcome. Maybe model_gen.py is a good place to start with: https://github.com/ise-uiuc/nnsmith/blob/main/nnsmith/cli/model_gen.py

It's just what I thought. 😄
Thx again!
Have a nice day!


After installing cg3d-maya-casc, Cascadeur hasn't been successfully installed...

Hello, sir! May I ask, after I installed it, Maya already has the "Cascadeur" option. However, in the Cascadeur software, there is no option for Maya, and the "Cascadeur—commands" only has "Reload scripts-Reload commands-Delete objects" three options, the others are missing. Is there any way to handle this?

Yeah.  I'll be home shortly to write a longer response.  Are you on Windows?
On Wed, Mar 13, 2024, 10:43 AM hanna9413 @.***> wrote:

Hello, sir! May I ask, after I installed it, Maya already has the
"Cascadeur" option. However, in the Cascadeur software, there is no option
for Maya, and the "Cascadeur—commands" only has "Reload scripts-Reload
commands-Delete objects" three options, the others are missing. Is there
any way to handle this?
—
Reply to this email directly, view it on GitHub
https://github.com/Nathanieljla/cg3d-maya-casc/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALF6O5COIVYLM3D2WAO6ATYYBX3LAVCNFSM6AAAAABEUNLYDSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE4DIMZTGI2DAMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

hi Hanna, did you ever get things working?  If so, I'll close this issue.


refactor/update ascii art and layout: ergodash

I think that this artwork and layout make a more obvious connection to the physical keyboard layout. I found the thumb cluster and bottom row difficult to understand, and to a lesser degree, the inner most columns of keys. I think the original artwork was made purely to reflect the electrical matrix as fields are not indexed and filled simply "in order" top-bottom/left-right. (Note also that the ascii art is 120 characters wide which may be desirable)
This PR is consistent with #61 but with no cross-dependencies.

@yearski
Nice! Thank you!
LGTM:+1:


Have rogue configured on by default

What's this PR do?
Turns rogue on by default so that we do not need to manually do it after every deploy.
Relevant tickets
Fixes #7177
Checklist

[ ] Documentation added for new features/changed endpoints.
[ ] Tested on staging.
[ ] Pinged a PM if this is a larger PR that would benefit from some additional testing love
[ ] Post a message in #phoenix if this includes something that causes a rebuild!

I think this looks good 🎉

These look like sane defaults. Do we need to update bin/ds pull stage to disable this on local dev?


C# code gen enums: descriptions + open-endedness

There are two scenarios with enums in specs which are not supported (both elaborated on in this thread):
Enums with item descriptions
According to one of the JSON Schema maintainers, the standard pattern for this is by wrapping each case in a singleton type with a description, ie like:
myEnum:
  type: int
  oneOf:
    - enum: [1]
      title: Foo
    - enum: [2]
      title: Bar
      description: This is a bar

to translate to
enum MyEnum
{
    Foo = 1,
    /// <summary>This is a bar</summary>
    Bar = 2
}

Open-ended/extensible enums
The pattern for this as described on the thread is allegedly:
myEnum:
  type: string
  - anyOf:
    - enum:
      - foo
      - bar
    - {}

to translate, I guess, to
enum MyEnum
{
    Foo,
    Bar,
    _Other
}

or perhaps just as a vanilla string together with the generation of a class like
static class MyEnum
{
    public const string Foo = "foo";
    public const string Bar = "bar";
}

I propose that both of these patterns, and their combination (as I described on the referenced thread), are detected and supported.

+1 for second open-ended enum support.

Yes, id also like to have this. What if we generate an additional enum value Unknown and serialize to that if its not known in the enum?

I don't have a strong view on the choice of C# representation but note that the string + static class route has more flexibility to handle non-string enums too, if that's of interest. (Personally, I currently require only strings.)

@RicoSuter has any work begun on this? If not I think I can lend some time to looking at the open-ended enum support.

Not yet... we would probably need an EnumType option (Enum, EnumWithFallback, StringEnum).


Feature:Implemented User Model and Authentication Routes (Login & Register) with Zod Validation

Related Issue(s)

Fixes #89

Description
This pull request aims to implement user authentication for our backend project, including user register and LogIn functionalities. The implementation includes creating a User model, setting up authentication routes, and using Zod for input validation.
Key Features:

User Model creation using Mongoose
User register and Login routes with input validation
Password hashing with bcrypt
JWT-based authentication

Changes Made

Created user-model model in `models'  with fields for username, email, and password, including necessary validations.

Added environment variables for JWT secret and bcrypt salt rounds.

Implemented Register route (POST /api/auth/register) in routes/auth-router.js:

Validate input using Zod.
Hashes passwords with bcrypt.
Creates a new user in the database.
Returns a success message or error response.

Implemented Login route (POST /api/auth/login) in routes/auth-router.js:

Authenticates user credentials like email and password.
Returns a JWT token on successful authentication or an error response.

Implemented Zod in following folder

Created Middleware for validation in middleware/validate-middleware.js
Zod validation in folder  validators/auth-validator.js

Implemented Login and register in controllers/auth-controller.js

Define routes in routes/auth-router.js

Screenshots (if applicable)

Functionality has been tested through Postman as shown in below video

https://github.com/oxiton-foundation/click-metrics/assets/72294811/57b1b0ee-9d75-4a2e-8f26-bbf24eaae1ae
When user with same email already exist

N/A
Checklist

[x] Code follows the project's style and conventions.
[x] Code has been tested thoroughly, and all tests pass successfully.
[x] Documentation has been updated to reflect any relevant changes.
[x] All new and modified code is adequately commented for clarity.
[x] Pull request title follows the specified format: [Feature/Enhancement/Bug Fix]: Brief description of the change.

@Swarnendu0123 can you please review this PR?

@Swarnendu0123 I  mentioned it before getting it assigned and you assigned it after my message stating the same Mongo db is mentioned in issue  and also in the issue itself mongo db is mentioned  . Additionally, the documentation includes MongoDB as well.

We will be using mongodb but not for the authentication. We will be using mongodb to store generated links and qrs. We will not store mongodb to store users.

@Swarnendu0123  ok, I will use Firebase. Now I am supposed to do everything mentioned in issue but in Firebase please check the video. You want that type of work in Firebase. Please confirm same?

I am planning to use the authentication service provided by firebase in this.

here is the updated code ..Please check then I will update code and doc
https://github.com/oxiton-foundation/click-metrics/assets/72294811/848bd419-bd70-4cd0-95ee-c31101ffa4ac

Please review and label this PR @Swarnendu0123  .

@Swarnendu0123 any update???

Btw you are trying to implement server side firebase authentication. But firebase is actually designed such a way, that we can use it directly on the client. So we are trying to implement it on the client side.

I agree with you but according to #189 opened there, it is mentioned explicitly to use it this way. So I  have done it according to the issue. @Swarnendu0123

@Swarnendu0123 Could you please clarify the details of issue #189? Multiple changes have been made due to a communication gap, and a clear description would help resolve it effectively.

@Swarnendu0123 Could you please clarify the details of issue #189? Multiple changes have been made due to a communication gap

I have clearly mentioned to use firebase for authentication. But I don't want to see a large change in a single PR. If you want to integrate firebase in click matrics, first implement the auth. Then the database using mongodb. Now the firebase is made for the client side not the server side. So use it in the client side. Use MongoDB in server side.

for frontend am I supposed to use tailwind CSS?

We are already using tailwind, you should continue with that only!

Also don't tag maintainers multiple times. We understand and respect your contribution in our community, but you don't need to mention any maintainers. We will see and respond by ourselves.


Release 2023-08-30

@vadim2404 I do not see anything in this release that needs to be documented in the external release notes. Please let me know if I missed anything. Thank you.


Update readme files with Hybrid2020 Profile

Update hybrid profile for

Authorization
Commerce
Compute
DataBoxEdge
Dns
EventHubs
IotHub
KeyVault
Monitor
Network
ResourceManager
Storage
Subscription
WebSites

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

/azp run unifiedPipeline

@HarveyLink, could you take a look at the code generation error?

@HarveyLink, could you take a look at the code generation error?

Automation pipeline failed with git push authentication, no idea why this step failed. Is there anyone i can reach for help?

Talked with @PhoenixHe-msft , automation sdk errors are expected. Can we ignore these CI result?

OK to merge with failure because it updates lot of readme.md


gumath.reduce doesn't always work

>>> import xnd
>>> import gumath.functions as fn
>>> import gumath as gu
>>> x = xnd.array([5])
>>> x
array([5], type='1 * int64')
>>> gu.reduce(fn.add, x)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/hameerabbasi/anaconda/envs/uarray/lib/python3.7/site-packages/gumath/__init__.py", line 136, in reduce
    dtype = maxcast[x.dtype]
KeyError: '=q'
>>> y = xnd.array([5.0])
>>> gu.reduce(fn.add, y)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/hameerabbasi/anaconda/envs/uarray/lib/python3.7/site-packages/gumath/__init__.py", line 136, in reduce
    dtype = maxcast[x.dtype]
KeyError: '=d'
>>> gu.reduce(fn.add, x, dtype='int64')
xnd(5, type='int64')

I'm on Python 3.7.3, conda version, and running on macOS 10.14

It seems this only happens with xnd.array and not xnd.xnd:
>>> z = xnd.xnd([5.0])
>>> gu.reduce(fn.add, z)
xnd(5.0, type='float64')

Yes, xnd.array.dtype currently returns a PEP-3118 string for the dask experiments. I'll change it back to ndt, then it should work.

Ok, done.


Font spacing is wrong for Type1C font on some platforms

This is a followup of issue #434 and issue #440 where screenshots show that the font spacing is not correct. I suspect it is not visible on Linux because the font system does not care about the widths declared in the font file but only take in account the glyph charstrings.

Sorry for the late update, I was testing the same document but found the rendering very bad. Not sure the test viewer is updated with the latest code. I was testing online.

Not sure the test viewer is updated with the latest code.
I downloaded the latest code and checked with both Firefox and Chrome.
But interestingly .xpi file (plugin) works great on the same document.

http://mozilla.github.com/pdf.js/web/viewer.html has latest version of the viewer. Try this one.
Also, please provide more detailed information about your operating system and web browsers versions.

Closing since there has been no feed back in 3 months.  If there are still issues please leave a comment or open a new issue if it is unrelated to the above.


Fix syntax for inlining a function

This commit is the port of erlang/otp#5263 to this repo.

thanks!


Expose browser events via a hook function

Currently, there is no way to stream console output from the browser to Go.
This PR adds an OnEvent method to TargetHandler that sets a hook for incoming browser events. This allows the user to inspect events and react not only to console output but on other kinds of events as well.

Coverage increased (+1.0%) to 67.666% when pulling ac5b86a6b98332bb4caf69788dbfc1c193ce4879 on dennwc:expose_events into bf52fed0d3e6fc1acb7096f4748fec335fcb5547 on chromedp:master.

Coverage increased (+1.0%) to 67.666% when pulling ac5b86a6b98332bb4caf69788dbfc1c193ce4879 on dennwc:expose_events into bf52fed0d3e6fc1acb7096f4748fec335fcb5547 on chromedp:master.

CI failure seems unrelated. You might want to allow failures on tip in Travis.

Thanks for the patch. We're in the middle of a redesign for v2, so the API and internal structure might change a bit. This seems like a good idea right now, but we'd like to hold off on adding new features until v2 is done.


Period in CSV field names causes an error

This sample content
DATE,Appt. Time,# Stops,Wait
4/22/14,9:00 AM,6,16

causes an error when the CSV is added to Voyager: Vega Lite cannot parse the Appt. Title field name due to the period, despite this being a technically-valid field

That sounds like a datalib issue. Can you flag it there?

NOT a datalib issue (but maybe a Vega issue). Observe:
// In console at http://vega.github.io/datalib/:
var txt = 'DATE,Appt. Time,# Stops,Wait\n4/22/14,9:00 AM,6,16';
JSON.stringify(dl.read(txt, {type: 'csv'}));
> [{"DATE": "4/22/14","Appt. Time":"9:00 AM","# Stops":"6","Wait": "16"}]

My guess is that the problem is not the initial parsing, but downstream. In particular, I suspect an accessor function is being constructed for that field name, and the . is being parsed a field separator. If so, one workaround would be to escape any dots used within field names: "Appt\\. Time".

Okay. We generally haven't tested . and   in variable names. There is a vega lite issue for that in https://github.com/vega/vega-lite/issues/358. I bumped up its priority.


Metadata not correctly propagated to nwb bug

Description
I realized that there is a bug when writing more than one track and propagating metadata. In the code, the metadata dictionary drops the timestamps and the rate for each track. Because of python copying mechanism this means that those fields are not available for the second track metadata once they are droped. The solution is to create a local copy of the metadata before any modification. This PR fixes the bug and introduces a test for correctly propagating the rate.
Types of changes

[x] Bugfix
[ ] New feature
[ ] Refactor / Code style update (no logical changes)
[ ] Build / CI changes
[ ] Documentation Update
[ ] Other (explain)

Does this address any currently open issues?
[list open issues here]
Outside contributors checklist

[x] Review the guidelines for contributing to this repository
[x] Add tests that prove your fix is effective or that your feature works
[ ] Add necessary documentation (if appropriate)

Thank you for contributing to SLEAP-IO!
:heart:

Thanks, how do you plan to handle releases for this package?

We typically aim to release once a month and are thus very much overdue for sleap-io v0.0.2.


Remove sprocket-es6

Why:
sprockets-es6 is causing depreciation issues for Sprockets, and the gem author says that the gem will never reach v1.0.
This PR:
Removes sprockets-es6. We would like to introduce the babel-transpiler gem in the future but it requires sprockets 4. While sprockets 4 has a beta release, this seems to be causing issues with bourbon neat and bitters per https://github.com/thoughtbot/suspenders/issues/797. Until this is resolved I suggest adding ES6 support on a project by project basis.
Resolves: https://github.com/thoughtbot/suspenders/issues/793

LGTM Matt. I'd consider using babel-transpiler and a beta release for Sprockets in the short term. I wouldn't add ES6 on a project by project basis, I'd vote for building the best solution we know for ES6 in Rails apps into suspenders (even if it requires beta sprockets).
This looks good to 🚢. Thank you! :)

While sprockets 4 has a beta release, this seems to be causing issues with bourbon neat and bitters per #797.

Nevermind my idea, if we can't run on beta. Thanks!

After https://github.com/thoughtbot/suspenders/pull/796#issuecomment-257061826 I see there is no good solution yet. Read the threads in the opposite order.
This LGTM. Thank you!

I don't understand why, but I have Suspenders plus this:
% bundle | grep sprockets
Using sprockets 3.7.1
Using sprockets-es6 0.9.2
Using sprockets-rails 3.2.0

I am able to write ES6 in files with names ending in .es6, deploy to Heroku, and see those files be served as JavaScript. I've seen no deprecation warnings or Bourbon issues, too.
Before I add sprockets-es6 back to Suspenders, what should I do to see the issues raised elsewhere?


[WIP] Refactor redundant interactive logic in CupertinoSwitch

Fixes https://github.com/flutter/flutter/issues/84390
Originally found in https://github.com/flutter/flutter/pull/84374#discussion_r649510333
There appeared to be a bug in CupertinoSwitch due to an indentation error. When trying to write a test for the fix, I found that you could never actually reach it since gestures are not enabled if the switch is disabled. So I refactored instead to remove the redundant isInteractive logic. All existing test pass.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

This should have a test to verify that if this widget becomes non-interactive during an interaction, the interaction is canceled.
I believe this PR actually changes the semantics of that situation.

Ah thank you! I was skeptical of this, but I could not find what I was breaking here. Marking WIP to investigate further. :)

I'm closing this in favor of a fresh PR, I forgot about this one 😅

This should have a test to verify that if this widget becomes non-interactive during an interaction, the interaction is canceled.

So you mean if this is the switch and interaction occurs, it should not go through?
value: value, // initially set to true
onChanged: value
    ? (bool newValue) {
        setState(() {
          value = newValue;
        });
      }
    : null,

yeah, i think that's an example of what i meant


Remove support for RabbitMQ Standalone

Supporting both RabbitMQ Standalone & Managed requires managing 2 separate code paths, which requires a lot of effort.
After a discussion with RabbitMQ team, we are considering removing support for RabbitMQ Standalone.
If this impacts you, please provide context on your setup/use case here - https://github.com/rabbitmq/messaging-topology-operator/issues/135

cc @cheskayang since you mentioned y'all are using the Standalone broker here

https://github.com/knative/community/blob/main/mechanics/SUNSETTING-FEATURES.md provides a guide for what to do in this case.


Add Resin envvar info to compute readme

overview
Just adds a line to the readme that documents a gotcha which was getting in Mike's way.
This PR includes:

[ ] Chore work
[ ] Bug fixes
[ ] Backwards-compatible feature additions
[ ] Breaking changes
[X] Documentation updates
[ ] Test updates

review requests
Just want the review so everyone sees this issue and it doesn't get in anybody's way in the future.

That is a resin namespaced environment variable


Can't walk after cutscenes

So, i first bumped into this issue after talking to Barry in his house upstairs. I fixed this by restarting the game without the randomizer mod enabled, after the cutscene i walked in to a house and it automatically saved. Then i restarted the game again with the randomizer mod enabled and it worked normally. I went in to the lake, starters weren't randomized even though the names were. After doing the battle, when leaving the forest there's another cutscene with professor then it transitions to your house, after that cutscene is over i cannot move again. Very time consuming and annoying to restart the game everytime after a cutscene to save and restart again. I am only using the starter, encounters, safari and underground randomizer. Nothing else has been used.

I know this is very late but this is still an issue after I tried today. Unsure why but so far it's only after cutscenes with your mom that you get frozen and cannot do anything including pulling up the game menu. Thankfully having tinfoil installed you can changed the contents folders name real quick by adding a random character to the end and loading up the game to bypass the cut scene and then saving afterwards, change the folder name back and reloading the game. Still very annoying but still. Unsure of why this is happening but thought I should mention my findings.


Fixed Size of The Set / Imbalance

Hi,
I have a very simple example here:
I want to partition a graph in two sets. In total I have e.g. 2048 nodes, which should be partitioned in two sets (ε=0?). However, after the partitioning the sets are not balanced:

Set1: 1023
Set2: 1025

I need an exact half/half cut ... two sets with a fixed size.
As far as I understood from the documentation I have to use the KaBAPE for this kind of task:
mpirun -n 8 KaHIP/deploy/kaffpaE --k=2 --imbalance=0.0 --mh_enable_kabapE my.graph

Did I something wrong?
Best Regards

please send me an email containing the graph.
Thanks!


Add a way to disable text normalization

Currently, CodeMirror appears to manually normalize text input in a similar fashion to  elements: all carriage return (CR) characters get replaced with line feed (LF: \n).
This feature makes it impossible to paste binary data and preserve its value.
For example, setValue(String.fromCharCode(13)) will insert a line feed (that indents text as a new line).
Using getValue().charCodeAt(0) returns 10 instead.

Clarification: [contenteditable] elements allow any characters inside, while <textarea> will replace and discard any carriage return symbols.

Not sure if you found it, but the lineSeparator option can be used to customize how the editor treats line breaks.


jdk8 is not buildable in container

Podman, free type build passed, jdk configure:
configure: Found freetype include files at /home/jvanek/git/temurin-build/workspace/./build//installedfreetype/include using --with-freetype
checking for freetype includes... /home/jvanek/git/temurin-build/workspace/build/installedfreetype/include
checking for freetype libraries... /home/jvanek/git/temurin-build/workspace/build/installedfreetype/lib
checking if we can compile and link with freetype... no
configure: Could not compile and link with freetype. This might be a 32/64-bit mismatch.
configure: Using FREETYPE_CFLAGS=-I/home/jvanek/git/temurin-build/workspace/build/installedfreetype/include/freetype2 -I/home/jvanek/git/temurin-build/workspace/build/installedfreetype/include and FREETYPE_LIBS=-L/home/jvanek/git/temurin-build/workspace/build/installedfreetype/lib -lfreetype
configure: error: Can not continue without freetype. You might be able to fix this by running 'sudo yum install freetype-devel'.
No configurations found for /home/jvanek/git/temurin-build/workspace/build/src/! Please run configure to create a configuration.
Makefile:55: *** Cannot continue.  Stop.

docker, cionfigure of freetype fails:
Cloning into 'freetype'...
Note: checking out '86bc8a95056c97a810986434a3f268cbe67f2902'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 86bc8a950 * Version 2.9.1 released. =========================
./autogen.sh: line 102: aclocal: command not found
./autogen.sh: line 55: test: 1: unary operator expected
./autogen.sh: line 59: test: 1: unary operator expected
./autogen.sh: line 67: test: 10: unary operator expected
./autogen.sh: line 71: test: 10: unary operator expected
./autogen.sh: line 102: libtoolize: command not found
./autogen.sh: line 55: test: 2: unary operator expected
./autogen.sh: line 59: test: 2: unary operator expected
./autogen.sh: line 67: test: 2: unary operator expected
./autogen.sh: line 71: test: 2: unary operator expected
generating `configure.ac'
running `aclocal -I . --force'
./autogen.sh: line 15: aclocal: command not found
error while running `aclocal -I . --force'

This issue is older then the support of podman:  https://github.com/adoptium/temurin-build/pull/3796#issuecomment-2186680794

I can confirm this bug is present, along with another missing command: libtoolize


Remove Demo Workflows

This workflow [Release Demo App to Netlify] as well as the build and deploy demo app workflows can be deleted on main after we migrated
Originally posted by @gfellerph in https://github.com/swisspost/design-system/pull/2616#pullrequestreview-1875133112

Closing as won't do until all ng bootstrap components are replaced with web components


expose glide configuration

This PR exposes the configuration of the driver used by glide to the glide.driver attribute in config/twill.php.

Merged in b95ca7f6. Thank you @schaschjan! As for your updates to the documentation, this is greatly appreciated and has been included in our upcoming larger update to the docs, stay tuned!


Allow option objects of any Umple model to be serialized/deserialized to/from Json

It would be good if any object had a String toJson() method that would generate (serialize) a Json representation, and a fromJson(String) static method that would instantiate (deserialize) the object.
Since this would not be needed in every single model, my suggestion is to only generate this if -s Json is specified as a suboption on a generator.
A complication is that Umple has dates and times as primitives. We would need to use ISO8601 format. See https://www.hanselman.com/blog/OnTheNightmareThatIsJSONDatesPlusJSONNETAndASPNETWebAPI.aspx
and
http://blog.plataformatec.com.br/2014/11/how-to-serialize-date-and-datetime-without-losing-information/
Note that Umple already has  a Json generator, but it is for a representation of the model, not the instances of the model. See Generator_CodeJson.ump
Also Umple has a parser for Json. See Json_Code.ump.
For serialization, associations should probably become arrays. But some mechanism for dealing with cycles would be needed.
For the deserialization, it would seem necessary to be able to call the deserialization of associated objects, and again how to deal with cycles would seem necessary.
In both the above cases, it would seem that perhaps an objectID ought to be stored in the Json, so the same object encountered twice would result in any other attributes being stored.

Java 7 (8?) added the javax.json packages. If each generator provides it's own solutions, that'd probably be best.
Solving recursive models requires some form of "cached" identifier, the objectId approach is how Jackson solves this.
Just saw this issue in my github feed, thought I'd add some info.

Generators for json-ld https://json-ld.org  or Turtle (.ttl) https://www.w3.org/TR/turtle/ should also be considered, but for outputing instances, and also outputting class diagram schemas, perhaps compatible with Schema.org https://github.com/schemaorg/schemaorg / https://schema.org

In addition to Json, other formats should be considered.
See https://medium.com/data-science-community-srm/json-is-incredibly-slow-heres-what-s-faster-ca35d5aaf9e8
Avri
MessagePack
BSON

The JSON generator with the -s json should be available first in the Java generator, and then in the Python generator (through transpiling ....)


Add GSoC JSON files for 2020-2023 with custom tags

close #167

Added JSON files for GSoC project custom tags for the years 2020–2023.
Files are located in backend/data/project-custom-tags/.

@nitinawari  you can run it via Makerfile  using command make  check .

@yashpandey06  i run make precommit


Support Paging Library with DataSource

Feature Request
Description
LiveData with Fuel is awesome integration.
I think it will be also great with Paging Library for api pagination. (DataSource, PagedList)
Proposed Solution
data class User(val key : String)
// ...

val pageSize = 20

val staticParams = listOf("limit" to pageSize)
val request = "https://...".httpGet(staticParams)

val onLastItemLoaded = { last : User -> listOf(*staticParams, "next" to user.key) }
val config = PagedList.Config.Builder().setPageSize(pageSize).build()

val source = request.dataSource<String, User>(dynamicParams : onLastItemLoaded)

val pagedList = source.toLiveData(config)

// or

val pagedList = request.livePagedList<String, User>(config, dynamicParams : onLastItemLoaded)

Alternatives I've considered
I have no idea.
I think it can't append query parameters dynamically.
Additional context
Thanks.

Hi there,
Can you link to DataSourxr and PagedList and the Paging library?
On Mon, 26 Nov 2018, 08:39 박현기<EMAIL_ADDRESS>wrote:

Feature Request Description
LiveData with Fuel is awesome integration.
I think it will be also great with Paging Library for api pagination.
(DataSource, PagedList)
Proposed Solution
data class User(val key : String)// ...
val pageSize = 20
val staticParams = listOf("limit" to pageSize)val request = "https://...".httpGet(staticParams)
val onLastItemLoaded = { last : User -> listOf(*staticParams, "next" to user.key) }val config = PagedList.Config.Builder().setPageSize(pageSize).build()
val source = request.dataSource<String, User>(dynamicParams : onLastItemLoaded)
val pagedList = source.toLiveData(config)
// or
val pagedList = request.livePagedList<String, User>(config, dynamicParams : onLastItemLoaded)
Alternatives I've considered
I have no idea.
I think it can't append query parameters dynamically.
Additional context
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kittinunf/Fuel/issues/547, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB35WDtaCY2H30krULJyX3N7uA_BAyHWks5uy5qwgaJpZM4YyeJ4
.

https://developer.android.com/topic/libraries/architecture/paging/
here it is. thanks!

But out of the top of my head, I don't think it fits well into the Fuel repo though. I think it is more like a child repo where it should have someone who really commits to this to maintain it. I would rather leave Fuel (even the extension) as it is unless we have something really ubiquitous.

But out of the top of my head, I don't think it fits well into the Fuel repo though. I think it is more like a child repo where it should have someone who really commits to this to maintain it. I would rather leave Fuel (even the extension) as it is unless we have something really ubiquitous.

Ok thanks. I will share gist when my extensions are stable. Thanks! 👍

@HarryTylenol and let me know when you have something stable and ready to share. I am happy to provide a link from the main repo to your repo or gist for the sake of more visibility. Thanks!
I will close this, but feel free to continue the discussion if you have something.


Variable name typo error in RPN recall evaluation code on VOC dataset

Hi. I find there is a variable name typo error in the RPN recall evaluation code on the VOC dataset:
# line 84-88 in 'mmdet/datasets/voc.py'

recalls = eval_recalls(
        gt_bboxes, results, proposal_nums, iou_thr, logger=logger)
for i, num in enumerate(proposal_nums):
        for j, iou in enumerate(iou_thr):
                eval_results[f'recall@{num}@{iou}'] = recalls[i, j]

This code can induce the following error info:
Traceback (most recent call last):
  File "tools/test.py", line 220, in <module>
    main()
  File "tools/test.py", line 216, in main
    print(dataset.evaluate(outputs, **eval_kwargs))
  File "<path_to_mmdet_root>/mmdet/datasets/voc.py", line 87, in evaluate
    for j, iou in enumerate(iou_thr):
TypeError: 'float' object is not iterable

When I replace iou_thr with iou_thrs, the output is correct:
+------+-------+
|      | 0.5   |
+------+-------+
| 100  | 0.692 |
| 300  | 0.728 |
| 1000 | 0.787 |
+------+-------+
OrderedDict([('recall<EMAIL_ADDRESS>0.6919449901768173), ('recall<EMAIL_ADDRESS>0.7282907662082515), ('recall<EMAIL_ADDRESS>0.787328094302554)])

Thank you for your feedback, we will fix it soon.


[go mode] Add error as highlighted type

It is, per https://golang.org/ref/spec#Predeclared_identifiers

Thank you! Merged as 047afd2


remove the -inf row with compute confidence

#269

@Tyrest what does the final output look like?

Here is with compute_confidence=True

Here is with compute_confidence=False

This also covers #328


refactor: remove enum VirtualMachineExecutionError

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (2831e85) 68.97% compared to head (b6a9892) 71.11%.
Report is 10 commits behind head on main-v0.13.1.

:exclamation: Current head b6a9892 differs from pull request most recent head 0d647f1. Consider uploading reports for the commit 0d647f1 to get more accurate results

Additional details and impacted files
@@               Coverage Diff                @@
##           main-v0.13.1    #1453      +/-   ##
================================================
+ Coverage         68.97%   71.11%   +2.14%
================================================
  Files                58       58
  Lines              7832     8355     +523
  Branches           7832     8355     +523
================================================
+ Hits               5402     5942     +540
- Misses             1976     1987      +11
+ Partials            454      426      -28

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

crates/blockifier/src/execution/deprecated_entry_point_execution.rs line 196 at r1 (raw file):
Previously, dorimedini-starkware wrote…
we already have the object defined, no reason not to use

Done.

crates/blockifier/src/execution/entry_point_execution.rs line 290 at r1 (raw file):

    args: Args,
    program_segment_size: usize,
) -> Result<(), EntryPointExecutionError> {

Done.


Chaning bed probing parameters doesn't seem to have effect

When I enable bed probing, changing (at least) the OffsetX and OffsetY parameters and the ProbePoints doesn't have any effect in the generated JSON (and probably code). Default probing points are (0,31), (0,155), (205,31) and (205,155), OffsetX is -18 and OffsetY is -31.

Huh, are you sure? Could it be you're changing them in the wrong Configuration, or looking at the wrong one in the JSON file? Or you're expecting these to have immediate effect upon flashing the firmware while the firmware is loading stored configuration on EEPROM?

No I was only talking about the generated JSON when I press the 'export data' button. I was not in the stage of flashing and storing something in the EEPROM yet. But I think I found my 'mistake' (or at least a workaround): you first need to press 'save data' before the data can be exported.

The "export" button should export whatever is currently in the editor, the "save data" only affects what is loaded when you reload the editor.

Ah I just found out that the export button exports all data (all examples, all boards). I was changing the RAMPS bed levelling parameters and by coincidence the first section I found in the JSON was the 4pi example with completely other probepoints. Sorry for the confusion.


Add build and run instructions to README.md

Add instructions to build ppx_show and run it on example/example.ml

thanks


Scrape best available demographics data

Currently, Covasim with the usepopdata = False option uses a hard-coded age distribution from the US:
https://github.com/institutefordiseasemodeling/covasim/blob/develop/covasim/people.py#L315
We need to make this adaptable to as many different locations as possible. The best source for data o this is the UN World Pop:
https://population.un.org/wpp/
We need a simple way of being able to choose the population data (i.e., set the age_data variable) based on any country in the world, e.g. make_randpop(sim, location='ethiopia').

For US - we have
https://censusreporter.org/
https://gii.dhs.gov/hifld/content/hifld-data-catalog - I'm exploring this for country-wide state demographics, schools etc

https://github.com/neherlab/covid19_scenarios/blob/da1381c429471c3d57b02cd5a7b6dc46e645c0b3/src/assets/data/country_age_distribution.json this is useful too

@inc0, I'm pretty sure we have this data in house. @dennish737?

Have for countries, separate issue for US states


agglomeration cannot be crafted with other items at all

That is the already crafted version. Such is permanent with no way of changing or adjusting such after the fact

Given both the correct statement above which mostly invalidates this anyway and the lack of a response, I'll go ahead and close this as invalid
Cheers

huh, i must've given myself an agglomeration instead of an empty agglomeration, my apologies


Fix 'option' entry name in option_order hash

The option_order hash is used to determine the correct order of
various backend/listen configuration parameters but it contained
a misspelled "options" parameter that is really called "option". This
change fixes that and extends the spec tests for the haproxy::listen
define to catch this problem.
See the discussion in #442 for more details and the reasoning behind the
option_order hash and why option order is important in HAProxy.
Unfortunately the change in #442 also introduced the misspelled
parameter and no spec test caught it.

Hi @antaflos, thank you for submitting this PR! I hope the problem will be solved this time, cheers!


SSR Hydration Error: RAC 1.1.1 Select

Provide a general summary of the issue here
NextJS 14
emotion 11
minimal repo to reproduce:
https://github.com/agscala/aria-select-emotion-bug

NextJS in an SSR environment (react server components are disabled):
RAC's Select component fails to hydrate properly if one if its children have styles set via emotion.

I think the issue stems from the usage of the internal Hidden component here with its implementation relying on template:
https://github.com/adobe/react-spectrum/blob/main/packages/react-aria-components/src/Select.tsx#L133-L144
https://github.com/adobe/react-spectrum/blob/main/packages/react-aria-components/src/utils.tsx#L344
I think this is the correct place to file this bug, but let me know if I should reach out to emotion instead!
🤔 Expected Behavior?
Select should render and hydrate via SSR properly
😯 Current Behavior
NextJS errors during hydration, saying the client-rendered Select doesn't match the server-rendered Select
💁 Possible Solution
There may be an issue with the Hidden implementation used in Select. Possibly this should be reworked to not use a template (like withVisuallyHidden)
🔦 Context
No response
🖥 Steps to Reproduce
https://github.com/agscala/aria-select-emotion-bug
npm install
npm run dev

go to localhost:3000
The code in question is all in this page:
https://github.com/agscala/aria-select-emotion-bug/blob/main/app/page.tsx
Version
react-aria-components 1.1.1
What browsers are you seeing the problem on?
Chrome
If other, please specify.
No response
What operating system are you using?
OSX
🧢 Your Company/Team
Engineering
🕷 Tracking Issue
No response

We are having the same issue in our Next + emotion codebase. We cannot use Select in an SSR situation. We've patched it internally by returning null if we're in an SSR render, but that's suboptimal. Any updates here?


As a user, I want to view blog posts so that I can read updates about CDH and its work.

Notes for testing
Admin editor preview doesn't match the styles of published version (will have to be a later enhancement).  There are not yet styles for all variants of formatting, but Xinyi and I will work out the specifics on that.  (Feel free to note any important styles or issues we need to address in the short term.)

Blog post detail page is in decent shape, but blog post list/archive views are not yet implemented.  We should probably add separate stories to document and test that functionality.

Seems consistent with the above comments - all appear to be working


Support World of Trucks Contracts

With the WoT contracts being added, the "Time Remaining" is always 0 minutes, and expected is always at Mon 12:00.  It looks like the complete time remaining is not being returned in the API, so I'm not 100% sure how to include remaining time.
I opened a forum topic at http://forum.scssoft.com/viewtopic.php?f=41&t=197521 in regards to this. Hopefully I'll get a helpful response.

The following will be done:

If deadline is Mon 12:00 AND time remaining is 0 minutes, assume it is a World of Trucks contract. The odds of a run being due on a Monday at 12:00 and the user has 0 minutes remaining is quite rare. If issues occur, this will be rolled back.
World of Trucks contracts should hide the time remaining block and replace the text for deadline to read "World of Trucks Contract" (or WoT contract depending on space). Font color should match the blue that is used in-game.


Bump minor version

Could we list what we want in before this?

Only bug fixes @na3d and we've finished up most of them. Any more bugs will be patches and any features will be next release.


download_json_schema_task should read the schema into memory

This task has been removed as AzureDataLakeDownload already has this functionality.


Add new component to support new OAS article

2nd OAS Estimator Article
This PR includes:

A new component to support a new layout for SCLabs-Comp-Content-Image-v1 fragments named ImageVerticalLineContent.js
Modifications to the TextWithImage component, which now takes in SCLabs-Comp-Content-Image-v1 fragments and checks for their layouts and then returns the specific component for that layout
Change to project pages with articles so that they query for their articles separately instead of as a property of the project, although they can still be queried in the previous way. Reason this was done was so that even if a content designer forgets to associate the article as a property of the project, it will still be queried and found by the project page.

Test Instructions

Navigate to OAS project page
Go to updates and select the new article
See that it renders with no errors, is responsive including new component

Check out a preview of your pull request here: https://app-servicecanadalabs-dev-pr-preview-2.azurewebsites.net

Check out a preview of your pull request here: https://app-servicecanadalabs-dev-pr-preview-2.azurewebsites.net


More accurate QuickPlots with Hermite interpolation

Description
The QuickPlot class plots the results using the raw data points. With the new Hermite interpolation changes in the IDAKLUSolver, we can improve the visual appearance of plots by interpolating the data. This PR adds 100 evenly spaced interpolation time points for all sub-solutions.
For example,
import pybamm

model = pybamm.lithium_ion.SPM()
solver = pybamm.IDAKLUSolver()
sim = pybamm.Simulation(model, solver=solver)
sol = sim.solve([0, 3600])

sol.plot(output_variables=["Voltage [V]"])

Hermite interpolation (new)

Raw data (old)

Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[x] New feature (non-breaking change which adds functionality)

Key checklist:

[x] No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[x] All tests pass: $ python run-tests.py --all (or $ nox -s tests)
[x] The documentation builds: $ python run-tests.py --doctest (or $ nox -s doctests)

You can run integration tests, unit tests, and doctests together at once, using $ python run-tests.py --quick (or $ nox -s quick).
Further checks:

[x] Code is commented, particularly in hard-to-understand areas
[x] Tests added that prove fix is effective or that feature works

This won't work well if there are multiple cycles (e.g. 5 times CCCV charge/discharge). Could it be done for each step in sol or would that be too slow?

@valentinsulzer good point – I actually meant to do this, but I misunderstood solutions to be the sub-solutions and not different simulations. I just pushed this change.

Hey @all-contributors please add @MarcBerliner for code, documentation, infrastructure and maintainence

Hahah you beat me to it @arjxn-py

Hahah you beat me to it @arjxn-py

Hahah, I made a mistake 😅
@all-contributors please add @MarcBerliner for maintainance

Hahah you beat me to it @arjxn-py

Haha, I made a small mistake 😅
@all-contributors please add @MarcBerliner for Maintenance


Skip unrelated property keys from generating in docGen pt2

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to dora please


There should be better handling of chemicals changing classification

Currently, when a chemical changes its classification in the BNF, it leads to surprising and sometimes inaccurate results.
This is because our unique id for a chemical includes its classification in the unique identifier for the presentation. For example, Linaclotide was classified as a Laxative (chapter 1.6) in November 2013, and an antispasmodic (chapter 1.2) afterwards. As a consequence, searching under the old name results in graphs with a sharp cutoff, like this:
.
When such a paragraph or section is used a denominator, the problem will be less obvious, as the effect will be obscured by other things that have not moved classification.
The proper fix is tricky; as @annapowellsmith has pointed out, it would involve interpreting the raw data, which isn't something we currently do, and we're wary of; specifically, we'd have to infer a chemical had changed section by using its presentation name as a key (which might not be reliable). It's possible the changes are explicitly described in some other data source (more research needed) in which case we could potentially do this more reliably. If we felt this was possible to do reliably, we could then map prescriptions to the current classifications rather than the ones correct at the time.
We should at least look into ways of warning people when this might happen. My estimate (using variations of the query at the end of this issue) is that 336 chemicals have changed paragraph, 79 have changed section, and 33 have changed chapter (a CSV of the latter attached).
So, as a minimum, we could add a warning on the analysis page when someone does a search for something in a list that we generate of things-that-have-been-reclassified, plus a link to an FAQ.
The only way to fix the denominator-pollution problem would be to produce a normalised classification as described above. This is likely to be a few days' work so we need to establish the user need for this.

BigQuery SQL for estimating changes in classification:
SELECT * FROM (SELECT
  COUNT(DISTINCT SUBSTR(bnf_code, 0, 6)) AS paragraph_count,
  bnf_name
FROM
  [ebmdatalab:hscic.prescribing]
GROUP BY
  bnf_name
) where paragraph_count > 1

This is rather frustrating data management on the part of the data providers... chemicals don't have unique identifiers, and the point at which you need a unique identifier is the time when the thing moves...

let's put a warning in when ppl use one of the 336 chemicals with high priority and think about manual matchin on the rest if no mapping exists (L will check..)

Somewhere within the NHS, someone must have some kind of mapping between actual drugs and BNF codes at the time! @lmfrench, do you think you could do some enquiries?

will do

Summary of the problem:
For any given line in the prescribing data, the question is if we can look up that code in our BNF table (downloaded from https://apps.nhsbsa.nhs.uk/infosystems/data/showDataSelector.do?reportId=126)
There are two reasons we might not be able to look up a code.

The code for a presentation has changed. We think this is usually (always?) because it has been moved to a different section, chapter, etc.
It is a drug which is no longer in the BNF tables for the dates we have available

The correct solution is for us to be able to look up a drug by BNF code for a particular month.
Our needs would be met by any of:

A series of files which list the BNF pseudo-classification as was current at each month going back as far as possible
A list of changes to the BNF codes for each month
A list of BNF -> SNOMED mappings for each month

Another example is Relvar Ellipta which has (for example) seen its Relvar Ellipta_Inha 184mcg/22mcg (30 D) presentation switch thus:

year
from
to

2015
0301011Y0BBAAAA
0302000N0BEAABM

2017
0302000N0BEAABM
0302000V0BBAAAA


v3.1.2 - Incompatibility with application based on commonJs modules

I'm submitting a ...
[x] bug report
[ ] support request
[ ] feature request

Current behavior
usage of es2015 module on compilations option make your library unusable to someone that use commonjs module on his project.

It is not to early to integrate this compilation option ?

Hey @paulcayon I had the same issue as you, I looked back through the history of the code and saw that the module loader had been switched from "commonjs" to "ES2015":
https://github.com/ocombe/ng2-translate/commit/ebcf7e83ecb1045cd996fd18029ecf8e002d13ba#diff-e5e546dd2eb0351f813d63d1b39dbc48L4
I assumed this was done intentionally so there wouldn't be an intention to switch it back (I suppose potentially other projects would break if they did).
From what I've seen the latest beta version of webpack 2 apparently solves this issue, personally I'm still using webpack 1.x because I want to wait for 2 to come out of beta first. So instead for the meantime I just forked the project and changed the tsconfig to use commonjs modules instead until I can update to webpack 2. You can set your package.json to load your forked package from the github tarball, like so:
"ng2-translate": "https://github.com/tim545/ng2-translate/archive/v3.1.1.tar.gz"
There's just one little caveat, in the ng2-translate package.json you need to add a version property or npm will complain, and then create a release for it in github so you can get a url like the one above.
It's not a great solution but it works for now, however I would like to know if it could be switched back...?

@tim545 Thanks for answer. I will try to use webpack 2.
I can't make a dependency with a github link, because I work for a bank, and it don't allow this ... I have to use a Nexus to download dependencies. Thanks to shared your version. I'm sure that it will be useful for some other persons.

I sucessfully used webpack 1.13.2 to load the module using babel-loader with this module config :
    {
      test: /ng2-translate\/.*\.js$/,
      loader: "babel-loader?presets[]=es2015"
    }

@ocombe maybe you could document this in the README.md ?

That's a good idea.
With webpack 2 it's easy, just add "lib": ["es5", "dom"] to your tsconfig.json file (in compilerOptions)

Just one question, I've seen you're french , like me (qui ne saute pas, n'est pas Lyonnais ! ^ ^). Will I meet you at ng-europe next week ?

Sorry, I wish I could go but I have other (family) obligations :)


Idea: Finally Block

Is it nesseccery to add a final_code block similar to before_all, after_all and error block ?
fastlane : before_all, after_all, error.
I compare it with java or other languages
  try {
      before_all
      some_lane
      after_all
  }catch(Exception e){
      error
  }finally{
      final_code
  }

For example, I usually reset_git_repo whatever success or failure. so I need to add reset_git_repo action in both after_all and error , so I think it is a common need for developers

Hey @MickeyHub, this is a really nice idea! Definitely we could use something to do any final cleanup no matter the result. We will keep this marked as a feature request and close the issue for now but we will reopen it and update it as soon as we can tackle this on a new release. If you want to submit a PR with this functionality, that would also be awesome! :tangerine:


Declaration conflict between quantified variables and others

Consider the following Boogie program,
procedure foo(n:int)
{
  var q : int;
  assume n > 0 ==> (forall q: int :: q > 0);
}

Boogie will give the following warning,
test.bpl(4,27): Error: more than one declaration of variable name: q
Is this behavior expected given that the second q is bounded by a quantifier?

I believe this is a bug masquerading as a feature.  Not sure what the right fix is though.


Can caches store and retrieve results that are still being written to the cache?

At the moment cache-adding methods resolve when the full body of the response if written to the cache. That means we can reject if the body stream looks like a failure, which can be suggested by content-length https://github.com/slightlyoff/ServiceWorker/issues/362#issuecomment-49011736. This is a must due to installEvent.waitUntil(addStuffToCaches) - we can't have that resolve but ultimately fail.
However, if you have code that tries the cache, falls back to the network and adds to the cache, you can end up with multiple pages doing this with the same resource, as cache.match won't return items until it's fully cached.
Shall we change this so items are added to the underlying cache as soon as we have headers? So for cache.add(request):

Fetch request
If fetch fails, reject & abort
Add (request, response) to RequestToResponseMap
Wait for body to stream into cache
If body writing fails, remove (request, response) from RequestToResponseMap, reject the promise & abort these steps
Remove other entries in RequestToResponseMap that match request (.match can no longer reach them)
Resolve promise

If you call .match(request) and there's already a match fully-written in the cache, you'll get that rather than the in-progress one. This seems sensible to me, but we could favour the in-progress one.
If you get an in-progress response back from .match(request), that goes back to the page, it may arrive slowly, it may ultimately fail. But hey, that's the same as the network, which it ultimately is.
Questions:

Does this sound like a good idea?
It is universally a good idea, or should it be an option to .match(). I don't think it needs to be optional.

Related: #361 #362
/cc Cache-warriors @wanderview @gavinp @sicking

@jungkees
I might be reading wrong, but I think there's been a couple of regressions in the spec. Imagine a cache with 2 entries that look like this header-wise (assume each has the same URL):

Request: { "Accept": "text/html" } Response: {"Vary": "Accept"}
Request: { "Accept": "foo/bar" } Response: {}

Then if we add a new entry to the cache, Request: { "Accept": "text/html" } Response: {} (no Vary), the cache should now look like this:

Request: { "Accept": "text/html" } Response: {}

The original algorithm would delete entries from the cache that match the new entry's request. As far as I can tell, the current spec would modify the first entry in the cache, leaving the second. That means the second entry cannot be matched, since the first will always match first. Am I reading it correctly?
In a system where we allow in-flight requests into the cache, it could work like this:

Request: { "Accept": "text/html" } Response: {"Vary": "Accept"}
Request: { "Accept": "foo/bar" } Response: {}

Then if we add a new entry to the cache, Request: { "Accept": "text/html" } Response: {}:

Request: { "Accept": "text/html" } Response: {"Vary": "Accept"}
Request: { "Accept": "foo/bar" } Response: {}
Request: { "Accept": "text/html" } Response: {} (in-flight)

So nothing's deleted from the cache at this stage. .match will favour entry 1 before 3, because it goes with first match. But once the request from entry 3 completes, it removes entries from the cache that match its request, leaving:

Request: { "Accept": "text/html" } Response: {}

This mean there aren't entries in the cache that cannot be matched.
I also think it's important to keep the cache in an order where the most recently added entries are at the end. This is useful when pruning caches. Talking to Twitter last week, they were interested in adding cached items back into the cache once they'd sent them to the browser. If added entries appear at the end of the list, this helps them track which items were "last accessed", therefore which entries they should keep.

Also, sorry I was so late in getting to this :(

@wanderview

But I still find the flag on fetch() harder to reason about

Yeah, my suggestion was silly. I think you're right, this needs to go on the cache. Will open a new ticket for that once we have the other in-flight stuff defined.

So nothing's deleted from the cache at this stage. .match will favour entry 1 before 3, because it goes with first match. But once the request from entry 3 completes, it removes entries from the cache that match its request

Addressed the point: 8e76892db1e9ccbe3a65601528f4f082f5e0eb46. Thanks for spotting it and explaining the details @jakearchibald.

I believe we've done with defining the behavior for the fetching / incumbent records of caches. Closing.


Fix for #3869

We didn't truly remove all the handlers from our texture constants.

Moving to master branch


Update ru_ru.json

Please resolve conflicts, I've added some of your suggestions in #32

Thank you!

😃


Assignment 8 draft

Great work! There were some bugs because you did not include the code we added in class - so you were only checking the closest edge for collision and not each of the edges of the rectangle.
Also we have to include a return statement so that no collision info is added if we find that there is a separation (hence the separation axis theorem SAT). You have done all the tasks of the assignment except for the return statement and get 19/20 +1 for great participation in class. Well done!


Make HTML sanitization Node.js/FastBoot compatible

Replace document.createElement('div').innerText with
the same approach Ember FastBoot is using in @simple-dom/serializer.
Reference
Fixes #178

@jherdman @ivanvotti what do you think about merging this and releasing patch version with a fix?
I'm really puzzled with failures in #184 and can't reproduce on my local.

This looks good to me. I left one small idea on your associated PR. Let's try that first and see what happens.

Got tests pass in #184, closing this PR


Fix typos and improve javadocs

Description
PR #5909 introduced a class to convert bytes through the scales (B, KiB, KB, MiB, MB...); however, there are some typos in the javadocs and method names. This PR intends to fix those typos and improve the javadocs.
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

@blueorangutan package

@GutoVeronezi a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. LL-JID 225

@blueorangutan package

@DaanHoogland a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. LL-JID 232

@blueorangutan test

@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

@blueorangutan package

@weizhouapache a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. LL-JID 237

Trillian test result (tid-54)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 42489 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr6877-t54-kvm-centos7.zip
Smoke tests completed. 102 look OK, 2 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_08_upgrade_kubernetes_ha_cluster
Failure
553.92
test_kubernetes_clusters.py

test_01_redundant_vpc_site2site_vpn
Failure
752.15
test_vpc_vpn.py

test_01_vpc_site2site_vpn_multiple_options
Error
1274.51
test_vpc_vpn.py

test_01_vpc_site2site_vpn
Error
545.05
test_vpc_vpn.py

the kubernetes error is intermittent and the vpc_vpn errors are due to a template download failure at the backend; merging


Accept-Encoding q-value of 0 is not honored

When the request includes for example
accept-encoding: gzip, deflate, br;q=0
the answer is still using brotli, even though the accept-encoding header says don't send me brotli.

I'm not sure about the disconnect from this and the Google repository, however when/if a patch is received for this, it should be merged upstream so we can be standard-compliant.

Moved to the upstream


Problem with floats and RTL

Having an issue with how some RTL content is being rendered when in a floating DIV (content outside floating DIVs seems mostly fine).  I have attached 2 images, one how the RTL Arabic content is being rendered in browsers (in this case Chrome, but works fine in Firefox/IE too), and how phantomJS is rendering it (both in PNG and PDF).  This same HTML/CSS renders fine in PhantomJS when using a LTR language.
Any suggestions?

I'm experiencing the same issue with Hebrew RTL. Has anyone found any solution for this?


Limit amount of emails copied to integration

This query runs when data is getting copied to integration, currently
emails up to 14 days old are being transferred over from production, this query deletes all
emails that are older than 1 day old from the time of the query call.

It'd be good to also do this against the email_archives table as that's another brute

& I've added the same delete query for email_archives

I checked with and without an index and they both took around 15 minutes each so doesn't seem to have any significant impact.


Carthage support

This is a pull request for issue #21 that adds Carthage Support. In addition, it fixes several issues with the Project file and with the tests no longer matching the Locksmith API.
I have added comments to each of the commits for additional information.

Awesome pull request! Thanks very much 👍


Extend "optional" flag for ConfZFileSource to ignore more exceptions

See PR #50 and issue #52.
optional now makes it possible to ignore if a command line argument is not set (through file_from_cl) or if an environment variable is not present (file_from_env). If set, this also ignores errors if the file format is invalid.

Thanks a lot for your PR!
One small thing: I wouldn't allow _get_format to fail, as this does probably not reflect the intention of the user using the optional flag.

That makes sense!
It does look kinda ugly, though:
try:
    file_path = cls._get_filename(confz_source)
except ConfZFileException as e:
    if confz_source.optional:
        return
    raise e
file_format = cls._get_format(file_path, confz_source.format)
try:
    file_content = cls._read_file(file_path, file_format, confz_source.encoding)
except ConfZFileException as e:
    if confz_source.optional:
        return
    raise e

Do you think this could be written better? The order of the operations needs to stay the same, and I cannot see any other way to have get_format outside the block. I could also check inside each function, but as mentioned in the issue, this may not be more maintainable.
If this is fine with you, I will update this PR accordingly.

True, it looks a bit ugly, but I don't see a good alternative. A context manager which would catch and optionally ignore the error like with AllowException(ConfZFileException, enabled=optional): ... does not help as we would still need to change the control flow (no follow-up calls if the first one fails). So I think we can go with your proposed solution.


In Blazor component (razor page) OnInitializedAsync method fires twice.

If we NavigateTo Blazor component (razor page) OnInitializedAsync method fires twice. But in another Blazor project, it is not executing twice!

OnInitializedAsync execution happening twice (the entire process will execute again) and this issue were not happening on projects those created in the earlier preview version.
@* Remove the following line of code to disable prerendering @
@@(await Html.RenderComponentAsync())*@ I have removed the code in Host.cshtml but the navigations and screen appearing is not like earlier with the code. Could you please reopen investigate on this.

I can confirm, component OnInitializedAsync is called twice on page load.
Tested on new server side project.

I can confirm, component OnInitializedAsync is called twice on page load.
Tested on new server side project.

How to reopen this issue?

This is likely due to pre-rendering. If you think that's not the case, feel free to reopen and we'd be happy to investigate.

OnInitializedAsync execution happening twice (the entire process will execute again) and this issue were not happening on projects those created in the earlier preview version.
@* Remove the following line of code to disable prerendering @
@@(await Html.RenderComponentAsync())*@ I have removed the code in Host.cshtml but the navigations and screen appearing is not like earlier with the code. Could you please reopen investigate on this.

This is likely due to pre-rendering. If you think that's not the case, feel free to reopen and we'd be happy to investigate.

Is there any way to prevent methods multiple executions on OnInitializedAsync

Ok, in other hands, how to use pre-rendering properly?
One way is disable it, but somebody created this functionality for some reason, maybe there is some way to properly initialize component in blazor server-side ?
Here is no info about pre-rendering http://blazor-university.com/components/component-lifecycles/

What namespace does RenderMode.Server exist in?

What a silly idea to call the main entry point twice?

i confirm this issue happens in client project  i use latest preview 9 version
for me it calls the request to the api 2 times,
there's no  @(await Html.RenderComponentAsync<App>(RenderMode.ServerPrerendered)) at client side code

@pranavkm Can you please reopen?

Same here, multiple calls to OnInitializedAsync during startup are confusing, please reconsider!


Archive the repository and split its functions into other repositories

Feature Request

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)
None
Describe the feature you'd like:
We will be redesigning the sig nomination process, please see: https://docs.google.com/document/d/1OvlpU00W_LpTL09zB3gvDyQzHULz27kmNKH2O0seWCI/edit?usp=sharing
So there will be no point for this bot to continue to exist, we will redesign the database synchronization mechanism and hope it will be able to synchronize and verify data in bulk with a ci task.
Do you have any ideas on how to implement it?(Optional)

[ ] Separate data synchronization function
[ ] Migrating APIs to a new project

/cc @Mini256  FYI.

It will soon be migrated to https://github.com/ti-community-infra/community-infra.
Do you have any advice on the technical selection of API frameworks? @Mini256

Regarding the framework selection for the API, I prefer to use https://github.com/nestjs/nest. I really don't want to use go to write the API, it's too painful. Java is too heavy for us. I'd like to use rails, but the whole org already has multiple technology stacks, so it's prudent to introduce new ones.