Firefox stream error on reload

If a rpc stream is active when reloading Firefox, the stream's onError handler is called with this error:
{
code: "INTERNAL",
details: null,
message: "Error in body stream",
meta: {},
methodName: "ChatQuery",
name: "RpcError",
serviceName: "ChatService"
}

this doesn't happen on Chrome though.
Is there a way to avoid it?

To clarify: You have an open server-stream, and reload the page in Firefox, then an error is raised?
My guess is that Firefox closes the connection (in a not very friendly way) before shutting down the JavaScript on the page. I think it might be quite difficult to distinguish that specific case from other errors in the stream. It might be helpful to look at the error produced by fetch() itself (we are unfortunately losing this information by wrapping in our own error).

that's right, it's a chat service that gets messages as a stream. If I reload the page while the stream is connected, I get the error.
I'm using this hack
if (
        error.code === 'INTERNAL' &&
        error.message === 'Error in body stream'
      ) {
        // firefox error on reload while stream is active. Do nothing
      } else {
        // report error (e.g.: Sentry)
      }

It works for now, but it's not ideal

Looks like this was a filed as a bug on Firefox once: https://bugzilla.mozilla.org/show_bug.cgi?id=1675699
You can catch this with an interceptor. An example for a server streaming interceptor is given here: https://github.com/timostamm/protobuf-ts/blob/41faab08b42cd459ce7f70faaa0811daa9b10541/packages/runtime-rpc/src/rpc-interceptor.ts#L37-L58
You can inspect the error and omit response.notifyError(error); if you are sure it's the FF bug.
But this might not be sufficient, because an error in the response stream will also reject the promises for status and trailer:
https://github.com/timostamm/protobuf-ts/blob/41faab08b42cd459ce7f70faaa0811daa9b10541/packages/grpcweb-transport/src/grpc-web-transport.ts#L170-L173
You can just leave those two dangling (i.e. wrap those promises in your interceptor, and never resolve/reject them if it's the FF bug).
I'd at least check the user agent though, so that the interceptor does not swallow errors it shouldn't. It might even be an option to listen to the reload event, and only activate the interceptor then.


Request to give installaion walk-through

Dear,
I humbly request you to give step-by-step clean walk-through tutorial as to how to install. There is lot of confusion in the current shown approach.
Please, it is a request.

Sure. Watch #4, I think we will be working on a simple tutorial there. :)

(Duplicate of #4, closed.)


[Errno 104] Connection reset by peer

When I tested your program, I found it could not run.
For a small sample size, it can run smoothly,such as
 star_list=['Gaia DR3<PHONE_NUMBER>44191232','Gaia DR3<PHONE_NUMBER>317863040', 'Gaia DR3<PHONE_NUMBER>104329216', 'Gaia DR3<PHONE_NUMBER>08035328', 'Gaia DR3<PHONE_NUMBER>826903680']
p2=madys.SampleObject(star_list,id_type='DR3',ext_map=None)
p2.phot_table

but for a large sample size, it cannot obtain data，such as
f='1000stars.csv' #1000 random stars
p1=madys.SampleObject(f,id_type='DR3',ext_map='leike',verbose=0) #collects data
p1.phot_table
ConnectionResetError: [Errno 104] Connection reset by peer
During handling of the above exception, another exception occurred: ConnectionError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
Is it because the sample size is too large to refuse data query, or is it because of my network?

Thank you so much! Confirming what we were saying, I've just noticed that accessing https://tapvizier.u-strasbg.fr// returns a 503 error. I hope they fix it soon.

yeah！I just tested it, It's working now.
Thanks a lot!  :)

Great! Thanks for informing me about the problem :) I'll add a connection check before the query to return an explicit message, should it happen again.


Relax domain requirementrs for DITA to XDITA conref

Expected Behavior
Conref content from a DITA topic to an XDITA topic.
Actual Behavior
Transform does not conref and gives the following error message:
"[DOTX012W]: When you conref another topic or an item in another topic, the domains attribute of the target topic must be equal to or a subset of the current topic's domains attribute. Put your target under an appropriate domain. You can see the messages guide for more help."
Possible Solution
Relax domains to allow conref. Ask @robander for his opinion/proposed solution.

Discussed previously with Carlos, but this isn't really a DITA / XDITA thing -- that's just where it has come up because of the domains mismatch.
Back in DITA 1.0 the original idea for conref validation envisioned 1) an environment where every team had different shells and different domains, together with 2) a lot of reuse between those teams, which would require 3) complex tooling that would perform any required generalization on any reused element that required it. In addition, the expectation was that if you had a case where content reuse pulled in something that was not valid, this would be prohibited, and Everyone Would Be Happy. For many reasons this is not really how things turned out.
The latest conref language in the spec describes how domains are compared to ensure validity, but does not say that reuse should be prohibited in case of mismatch -- it says we should tolerate specializations and generalize when we can:

When pulling content with the conref mechanism, if the referenced element is the same type as the referencing element, and the set of domains declared on the @domains attribute in the referenced topic or map instance is the same as or a subset of the domains declared in the referencing document, the element set allowed in the referenced element is guaranteed to be the same as, or a subset of, the element set allowed in the referencing element.
...(conref push info) ...  processors resolving conrefs SHOULD tolerate specializations of valid elements and generalize elements in the pushed or pulled content fragment as needed for the resolving context.

There is an additional topic on processing documents with different domains, which does imply that constraints would prohibit a content reference -- but even that should only apply to strict constraints. Adding the emphasis here:

When a copy operation is unsafe, processors MAY compare the copy source to the copy target to determine if the copy source satisfies the constraints of the copy target. If the copy source meets the copy target constraints, the copy operation can proceed. Processors SHOULD issue a warning that the copy was allowed but the constraints are not compatible. If the copy source does not meet the constraints of the copy target, processors MAY apply generalization until the generalized result either satisfies the copy target constraints or no further generalization can be performed. If the copy operation can be performed following generalization, the processor SHOULD issue a warning that the constraints are not compatible and generalization had to be performed in order to complete the copy operation.

In the end -- the only case where the spec demands that we not resolve a conref is when the referencing document has incompatible strict constraints. In the case Carlos described of DITA / XDITA, there are no constraints in place, so we should not prohibit reuse. I do think it's valid to issue a warning about incompatible domains, because you may be pulling in something unexpected. But we should still resolve the content reference, instead of ignoring it as we do today.


feat: Force workspace removal

Description
Adds a force flag to daytona delete [workspace]. This option would ignore any errors arising from the deletion process and proceed to forcibly delete the workspace and related entries to the daytona database.

[ ] This change requires a documentation update
[ ] I have made corresponding changes to the documentation

Related Issue(s)
This PR addresses issue #576
/claim #576
Closes #576
Screenshots
If relevant, please add screenshots.
Notes
Please add any relevant notes if necessary.

@Tpuljak Also I can't seem to create a workspace for some reason. I try installing the docker provider, I get a prompt saying that they are already installed. On trying to set the target, I get an error saying that there are no providers installed. Here are the screenshots:
Running target set:

@Tpuljak Also I can't seem to create a workspace for some reason. I try installing the docker provider, I get a prompt saying that they are already installed. On trying to set the target, I get an error saying that there are no providers installed. Here are the screenshots:
Running target set:

@mobley-trent please post the result of dtn server logs.

@Tpuljak here is the screenshot for the server logs

I recommend you execute code ~/.config/daytona/server/config.json and then add "registryPort": "3988" to the json structure.

Do not check out an older branch. Please checkout from main, do what I quoted above and then start the server and try to create a workspace.

I recommend you execute code ~/.config/daytona/server/config.json and then add "registryPort": "3988" to the json structure.

Do not check out an older branch. Please checkout from main, do what I quoted above and then start the server and try to create a workspace.

I did this but still got the same result

On what architecture are you running Daytona? Are you on Windows/Mac/Linux and Arm/Intel?

Ubuntu Linux WSL

@mobley-trent Hi, this seems to be an issue with your installation - I have some experience with WSL - can you first send me the entire log you get with cat ~/.config/daytona/server/daytona.log? Have you rebuilt the devcontainer at any point since you first built it?

@mobley-trent Hi, this seems to be an issue with your installation - I have some experience with WSL - can you first send me the entire log you get with cat ~/.config/daytona/server/daytona.log? Have you rebuilt the devcontainer at any point since you first built it?

No I havent. I have to mention that I installed the software using curl prior to setting up the dev environment, so that I could experiment with the software first. I removed the curl version before cloning the repo. I don't know if this has the potential to interfere with the dev environment
Here are the logs:
daytona_logs.txt

What do you get when you run uname -m in your windows terminal?
In the devcontainer, please tell me the response you get after running the provider directly with ~/.config/daytona/providers/docker-provider/docker-provider

I'm getting x86_64 and [1]    34925 segmentation fault  ~/.config/daytona/providers/docker-provider/docker-provider respectively @idagelic

Hard to guess the reason for this since it worked outside of devcontainer as you said.
Can you try removing everything and starting from scratch?
In devcontainer:
Stop the serve process
rm -rf ~/.config/daytona
dtn serve

Hi @Tpuljak I feel as though the latest changes to the delete.go file brought some breaking changes to the API. Fixing the merge conflicts with rebasing is proving quite difficult. Is it cool if I reopen this PR afresh and integrate the changes from there 🙏 ?

@mobley-trent of course, feel free to close this an open up a new one.


Add Map showing distribution of data

See Neil's work: https://heliconius-maps.github.io/index.html.
There are also plotly packages for mapping: https://plotly.com/python/maps/.

This will go in the distribution section with a Map View vs Chart View button to toggle.
Map View will include Color By Species, Subspecies, View, Sex, Hybrid Status, and Additional Taxa Info.
Question: Can we have Sort By for legend on the map?

Used plotly, see PR #19


Update super-linter version and reinstate GitHub Action linting

Description
tldr - waiting on a super-linter release after v4.9.2 here
While working on #1721, the latest version of super-linter had a version of actionlint that was incorrectly flagging errors relating to outputs from the GitHub script step.
The actionlint issue was resolved in 1.6.11 of actionlint.
At the time of creating this issue, the super-linter code on main  had been updated to 1.6.12 of actionlint, but the latest released super-linter image only seems to have actionlint 1.6.10.
(Tracked here on super-linter)
Note: in the meantime, the .github/scripts/run-test.sh script includes the actionlint checks)
Acceptance criteria

Update  the super-linter version
Set VALIDATE_GITHUB_ACTIONS: true in build_validation_develop.yml
Linting passes for the workflows (can run make lint locally)

@stuartleeks 4.9.3 is now out and I tested and saw that within superlinter all actions are passing. I thought to remove the linting step from the run-test.sh script, but it also doesn't heart keeping it there... thoughts?

I'm in favour of keeping the linter in run-test.sh as I found that it gives a very tight feedback loop when developing locally 😄

Thanks @stuartleeks . Closing per prior conversation above.

I think it's still worth updating the version of super-linter used in CI and re-enabling the GH actions linting there? I see the actionlint in run-tests.sh as a developer convenience vs the safety net of checks in CI


API endpoint not found.

Hi,
Followed https://github.com/swagger-mock/swagger-mock#how-to-use with remote file (Docker container) and I'm hitting INFO[0014] <IP_ADDRESS> {259ms} 404 GET http://localhost:8080/pets but there is no response. What am I doing wrong?

Hello! This is because swagger mock uses server urls for routing. Valid request is GET http://localhost:8080/v1/pets.

Thanks for quick feedback, I've tried api/pets. Closing then.


Fix deleted beatmaps being allowed to be added to a multiplayer room

Deleted beatmaps shouldn't be allowed to be used in multiplayer. As discoverd in https://github.com/ppy/osu/discussions/17106#discussioncomment-2599163.

Need to check whether osu-web also checks this (looks like it may not?): https://github.com/ppy/osu-web/blob/44103cdc243af886c2eda99856ef34b2696966a6/app/Models/Multiplayer/PlaylistItem.php#L41-L54 @nanaya

There's a default scope on osu-web on the model to filter out deleted maps.


Unable to retrieve indexes

If an index is created but the reference to it is lost (either by reassignment, or between sessions), it is not possible to retrieve it for further appending to or querying. This makes it very difficult (impossible?) to manage multiple indexes, for example where each instance of a Rails model may have its own index to query.
I have started on a very rudimentary implementation of a RetrievedIndex class (see here) but I'm struggling to find a way to recapture the parameters passed to Redis at index creation time (for instance FT.INFO doesn't seem to return much of use to the Index class) and so a general solution is evading me right now.
Any help is appreciated!

Hi @cdwsn, the way to retrieve an index is to initialize an index object.
index = Neighbor::Redis::HNSWIndex.new("items", dimensions: 3, distance: "l2")

The current design expects index parameters to be kept in code (rather than stored in Redis on index creation, which would require an additional query to Redis on instantiation).

Hi @ankane
I've abandoned the previous approach and added serialization / deserialization methods (and a couple of tests) to my fork.
This is a bit of a quick fix, but it'll do just fine for my needs. Let me know if you'd be open to a pull request to your repo.
Another approach could be to allow the definition of index parameters ahead of time in a config, and then use those to create and retrieve indexes by name alone. I might look into this, too.

Thanks for sharing. For now, I'd like to stick with the current approach.


[Selenium] Update selenium to standalone latest version

This PR update usage of 2 containers of selenium-hub and node-chrome with one standalone.
node-chrome released 3 years ago and has old version of chrome.
After update node-chrome to latest I faced with problems.
Standalone container contain both hub and chrome driver.

@davidalger Thanks for review. PR updated

@Den4ik Everything looks good. Appreciate it.

@Den4ik Are you sure that Magento Functional Testing framework supports the latest version?

@Den4ik Are you sure that Magento Functional Testing framework supports the latest version?

Yes, I used it when worked on https://github.com/magento/magento2/pull/32090

Wow. That's awesome!


feat: improved memory management during long split pdf processing

This PR:

improves the memory management by freeing the memory early when processing larger files, thus holding the data in memory for a long time
instead, it uses tempfiles to keep:

pdf_chunks for split_pdf_page functionality
partial response elements as json files

FYI: Added more optimizations and on 1k pdf file the memory usage dropped from ~250MB to ~120MB (<100MB if not reading the contents of a file).
Next steps include feature flag for memory optimizations using tmp files caching (as @jordan-homan mentioned - it might be a problem for some users).

before merging we should squash into one commit so that it's easy to follow in the public git history

before merging we should squash into one commit so that it's easy to follow in the public git history

Isn't it the default setting? I'm not sure what's the squash commit message setting in this repo (It should be the PR description I guess)

Isn't it the default setting? I'm not sure what's the squash commit message setting in this repo (It should be the PR >
sounds good!


Drawables Size Optimized

#262 (Part-2)
All non sharp drawables has been reduced in size using tinypng  and  sharp drawables has been replaced by vector drawables  wherever possible.
Raw file Size Decreased by 2 MB (from 3.7 MB to 1.7 MB) for Drawables in Apk Size Distribution.

@opticod I have checked each and these need modification - library, group, assignment, input. I am changing it, please review.

@codingblazer , Mistake, revert back for 3

Assignment (all dpi)
Input (all dpi)
Record_voice(all dpi)

And can you add vector for ic_keyboard_capslock_black_down_24dp.png as u have did for ic_keyboard_capslock_black_24dp.png?

@codingblazer, Lets fix this, and freeze a version for testing.

@opticod I am doing this only right now. Will take max 5-10 min.

@opticod Done. Also added the Caps_down you asked for.


Question about beta

Thank you for your work. I have learned a lot from it, but I have a question.
From the screenshot of the paper：

Full_light_end_y and light_end_y denote w/2 and 5*w, respectively.
But the code is:
    full_light_end_y = int(math.sqrt(beta) + 0.5)
    light_end_y = int(math.sqrt(beta * 20) + 0.5)

What is the correspondence between parameter beta and w?
Looking forward to your reply, thank you

Thank you for your reply. I would also like to ask whether the formula w = 2 * int (math.sqrt (beta) + 0.5) is also an experimental value. How did you get 2 and 0.5?
Looking forward to your reply, thank you

Nope, either 2 or 0.5 is not an experimental value.
Actually, the experiment starts with the beta, but considering width could be easier to be understood, so we use the width (w) in the paper.
The formula w = 2 * int (math.sqrt (beta) + 0.5), in which:
0.5: int(x+0.5) is a common quantization method.
2:  int (math.sqrt (beta) + 0.5) defines the distance between the current point and axis, thus it is half of the width.
Hope it helps~

Thank you for your work. I have learned a lot from it, but I have a question.

How the thick laser beam in the picture is generated?


Using AD Fuzzer for lane change scenario

Hello @AIasd , I am doing an automated testing of scenarios in CARLA simulator (CARLA 0.9.13)  and the scenarios are in openscenario format. For example, I have a lane change scenario which I have written in python script and converting that to openscenario and running in CARLA with the help of scenario runner module. So is there any possibility that I can use your AD fuzzer implementation to find the parameters where my scenario fails?

Hi @arjunsk07 , currently there is no automatic conversion from openscenario. In order to use the fuzzer, you might consider to define the parameters you want to search for and then only run the fuzzer part for parameter selection.


needed vulkan to execute

On running ./ladybird.sh run ladybird i got
"error while loading shared libraries: libvulkan.so.1: cannot open shared object file: No such file or directory".
To fix, i installed vulcan-sdk by following https://vulkan.lunarg.com/doc/view/latest/linux/getting_started_ubuntu.html
Does this need to be put in Documentation/BuildInstructionsLadybird.md ?
also, is there a more compact alternative than entire vulkan-sdk (>300mb) ?

On ubuntu, the mesa-vulkan-drivers package seems to provide the required libs. Or just libvulkan1 itself. But I'm not sure how my install ended up with these libs... I assumed one of the already specified dependencies would have installed it. e.g. the Qt6 ones, or libgl1-mesa-dev

should've be fixed by https://github.com/LadybirdBrowser/ladybird/commit/22d7aa53fa52bdf71eef667eb58d142b10d4ba74


Allow to set optimization level for codegen

Why is optimization level hard-coded to -O3?
https://github.com/ponylang/ponyc/blob/c76e5900a3453c6f922d68a3e78bb6e0dafeb971/src/libponyc/codegen/genexe.c#L361
I’d expect to be able to specify optimization level using CLI argument for ponyc.

In the sync call, @kulibali mentioned that the actual place for setting optimization level for LLVM codegen is here: https://github.com/ponylang/ponyc/blob/master/src/libponyc/codegen/genopt.cc#L1366
The line shown above is only for the linker.
@mfelsche is going to read about whether it would be a good idea to allow lowering the linker optimization level.

The -O flag here is only setting a linker optimization level … this is only used for optimizing the output file size …

That’s actually what I’m currently interested in, to optimize size of the output binary (i.e. compile with -Os).


To domain events

Refactored BbEvents into DomainEvents. It's mostly a class name change.
@RuaidhriMcDonnell make sure you're OK with all the naming!

New structure, @RuaidhriMcDonnell can you take a glance and poke me if it doesn't match what we talked about yesterday?

Looks good.


Index all Devfile Services related documents

/kind user-story
Which area this user story is related to?

all
User Story
As a devfile user it would be beneficial if I can access all the devfile related documents from a document index rather than visiting/navigating the google drive of the team.
Currently, we navigate the Google Drive or create bookmarks for specific Google documents. This is inefficient even though we do organize documents and files in Google drive to a degree.
It would be nice if there was an index much like how the index of a book tells us the page number of a chapter.
We should document the index at here
There are few approaches that we have identified in the team meeting. For example, it would be cumbersome to list A-Z documents in the index. It would be much more efficient if we put all the Education Module documents in a Education Module directory in Google Drive and document the Google Drive directory link in the Index document.
Similar for the other sections of the documents.
Acceptance Criteria

[ ] Capture all documents related to devfiles
[ ] Preference over organizing related documents in a Google Drive dir and linking that dir
[ ] Index document should be easily navigable with topics or topic alphabet

created the document, available on local google drive folder.


Register numpy arrays and output numpy arrays

I've got two numpy arrrays one is smaller than the other it captures only a portion (a ROI) of the sample that is captured with the other. I would like to register them and to return a numpy array.
import numpy as np
import SimpleITK as sitk

#TEST DATA
testarray = np.array(range(36)).reshape(6,6)
croparr = testarray[2:,4:]
zero = np.zeros(36).reshape(6,6)

#Fixed
ta = sitk.GetImageFromArray(testarray)
#Small array to register
tb = sitk.GetImageFromArray(croparr)
#Same dimension of the fixed array but zeros in others positions
zero[:4,:2] = croparr
tc = sitk.GetImageFromArray(zero) #same dimension of ta

import SimpleITK as sitk

elastixImageFilter = sitk.ElastixImageFilter()
elastixImageFilter.LogToConsoleOn()
elastixImageFilter.SetFixedImage(ta)
elastixImageFilter.SetMovingImage(tb)
elastixImageFilter.SetParameterMap(sitk.GetDefaultParameterMap("rigid"))
elastixImageFilter.Execute()
res = elastixImageFilter.GetResultImage()
hi = sitk.GetArrayFromImage(res)

But I've got this error:

Traceback (most recent call last):
File "", line 1, in
runfile('/home/opdate/Desktop/Python Script/SimpleITK_example.py', wdir='/home/opdate/Desktop/Python Script')
File "/usr/lib/python2.7/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 699, in runfile
execfile(filename, namespace)
File "/usr/lib/python2.7/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 81, in execfile
builtins.execfile(filename, *where)
File "/home/opdate/Desktop/Python Script/SimpleITK_example.py", line 32, in
elastixImageFilter.Execute()
File "/usr/local/lib/python2.7/dist-packages/SimpleITK/SimpleITK.py", line 10102, in Execute
return _SimpleITK.ElastixImageFilter_Execute(self)
RuntimeError: Exception thrown in SimpleITK ElastixImageFilter_Execute: /home/opdate/SEla/SimpleElastix/Code/Elastix/src/sitkElastixImageFilterImpl.cxx:208:
sitk::ERROR:
itk::ExceptionObject (0x4dfb7b0)
Location: "unknown"
File: /home/opdate/SEla/build/Elastix/src/Core/Main/elxElastixFilter.hxx
Line: 240
Description: itk::ERROR: Self(0x3a29f90): Internal elastix error: See elastix log (use LogToConsoleOn() or LogToFileOn()).

Thanks for your help.
Best regards,
GM

Hi @giacomomarchioro ,
Do you execute this script in a standard python console or in iPython ?
You should find more details in the ElastiX log, that output to the (standard) python console when using elastixImageFilter.LogToConsoleOn().
If needed you can use elastixImageFilter.LogToFileOn() that should create a log file in your output directory.
Come back with these info and debugging will (probably) be easier :)

For anyone that lands here..  and wants to reproduce this example
https://github.com/SuperElastix/SimpleElastix/issues/86
sitk.ElastixImageFilter() is no more, it is now called with sitk.SimpleElastix()


Converting back to CommonJS

This was just a diagnostic test to see what files I needed to change in order to create the CJS branch.


Unable to handle non-success responses

Problem statement
Go Swagger Client generation only handles 2xx responses (success) but does not handle the other responses and cast them as error.
Swagger specification
{
  "swagger": "2.0",
  "info": {
    "description": "**API documentation for Participant Service**",
    "title": "Participant Service",
    "version": "1.0.0"
  },
  "host": "localhost",
  "basePath": "/core/api/v1/participants",
  "schemes": [
    "https"
  ],
  "paths": {
    "/participant-types": {
      "get": {
        "produces": [
          "application/json"
        ],
        "parameters": [
          {
            "default": 50,
            "description": "Number of items to return.",
            "in": "query",
            "maximum": 100,
            "minimum": 1,
            "name": "limit",
            "required": false,
            "type": "integer"
          },
          {
            "default": 0,
            "description": "Number of items to skip from start.",
            "in": "query",
            "minimum": 0,
            "name": "offset",
            "required": false,
            "type": "integer"
          },
          {
            "collectionFormat": "csv",
            "description": "Specifies list of attributes to be included in response. If not specified, all attributes are included in response.",
            "in": "query",
            "items": {
              "enum": [
                "name",
                "isSystem",
                "isActive",
                "ttl"
              ],
              "type": "string"
            },
            "minItems": 0,
            "name": "select",
            "type": "array"
          },
          {
            "description": "Query criteria. Refer following links for more details:
 - [match](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-match-query.html)
 - [multi_match](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-multi-match-query.html)
 - [term](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-term-query.html)
 - [terms](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-terms-query.html)
 - [range](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-range-query.html)
 - [regexp](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-regexp-query.html)
 - [exists](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-exists-query.html)
 - [fuzzy](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-fuzzy-query.html)
 - [prefix](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-prefix-query.html)
 - [wildcard](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-wildcard-query.html)
 - [match_phrase](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-match-query-phrase.html)
 - [match_phrase_prefix](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-match-query-phrase-prefix.html)",
            "in": "query",
            "name": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Participant Types",
            "schema": {
              "$ref": "#/definitions/ParticipantTypesResponse"
            }
          },
          "400": {
            "description": "Error Occurred",
            "schema": {
              "$ref": "#/definitions/ErrorResponse"
            }
          },
          "401": {
            "description": "Error Occurred",
            "schema": {
              "$ref": "#/definitions/ErrorResponse"
            }
          },
          "404": {
            "description": "Error Occurred",
            "schema": {
              "$ref": "#/definitions/ErrorResponse"
            }
          },
          "500": {
            "description": "Internal server error",
            "schema": {
              "$ref": "#/definitions/ServerErrorResponse"
            }
          }
        },
        "tags": [
          "Participant Type"
        ],
        "operationId": "getParticipantTypes",
        "summary": "Get configuration of all participant types"
      }
    }
  },
  "definitions": {
    "BaseParticipantType": {
      "properties": {
        "name": {
          "$ref": "#/definitions/ParticipantTypeName"
        },
        "ttl": {
          "$ref": "#/definitions/TimeToLive"
        }
      },
      "required": [
        "name"
      ],
      "type": "object"
    },
    "ServerError": {
      "description": "Server Error Information",
      "properties": {
        "additionalInfo": {
          "description": "Additional information related to the error",
          "type": "object"
        },
        "code": {
          "description": "Error code",
          "type": "string"
        },
        "description": {
          "description": "Error description",
          "type": "string"
        }
      },
      "required": [
        "code",
        "description"
      ],
      "type": "object"
    },
    "Error": {
      "description": "Error Information",
      "properties": {
        "additionalInfo": {
          "description": "Additional information related to the error",
          "type": "object"
        },
        "code": {
          "description": "Error code",
          "type": "string"
        },
        "description": {
          "description": "Error description",
          "type": "string"
        }
      },
      "required": [
        "code",
        "description"
      ],
      "type": "object"
    },
    "ServerErrorResponse": {
      "properties": {
        "error": {
          "$ref": "#/definitions/ServerError"
        },
        "request": {
          "$ref": "#/definitions/Request"
        }
      },
      "type": "object"
    },
    "ErrorResponse": {
      "properties": {
        "error": {
          "$ref": "#/definitions/Error"
        },
        "request": {
          "$ref": "#/definitions/Request"
        },
        "data": {
          "$ref": "#/definitions/ParticipantTypeReadOnlyProperties"
        }
      },
      "type": "object"
    },
    "ParticipantType": {
      "allOf": [
        {
          "$ref": "#/definitions/ParticipantTypeReadOnlyProperties"
        },
        {
          "$ref": "#/definitions/BaseParticipantType"
        }
      ],
      "description": "Participant Type"
    },
    "ParticipantTypeName": {
      "properties": {
        "plural": {
          "description": "A unique plural name of a participant type. This is used as collection name in resource URL for this participant type.",
          "maxLength": 16,
          "minLength": 1,
          "pattern": "^[a-zA-Z]{1-16}$",
          "type": "string"
        },
        "singular": {
          "description": "A unique **singular name** of a participant type. This is used as participant id prefix.",
          "maxLength": 16,
          "minLength": 1,
          "pattern": "^[a-zA-Z]{1-16}$",
          "type": "string"
        }
      },
      "required": [
        "singular",
        "plural"
      ],
      "type": "object"
    },
    "ParticipantTypeReadOnlyProperties": {
      "description": "Readonly properties of participant type",
      "properties": {
        "id": {
          "type": "string"
        },
        "isActive": {
          "type": "boolean"
        },
        "isSystem": {
          "type": "boolean"
        }
      },
      "type": "object"
    },
    "ParticipantTypesResponse": {
      "properties": {
        "data": {
          "properties": {
            "participantTypes": {
              "items": {
                "$ref": "#/definitions/ParticipantType"
              },
              "type": "array"
            }
          },
          "type": "object"
        },
        "error": {
          "$ref": "#/definitions/Error"
        },
        "request": {
          "$ref": "#/definitions/Request"
        }
      },
      "type": "object"
    },
    "Request": {
      "properties": {
        "body": {
          "type": "object"
        },
        "queryString": {
          "type": "string"
        },
        "uri": {
          "type": "string"
        }
      },
      "type": "object"
    },
    "TimeToLive": {
      "description": "Time to live. Time string in days, hours, minutes and seconds. Example - 30m, 1d 12h, 1d 12h 30m 45s etc.",
      "minLength": 2,
      "pattern": "^\\d*(?:d\\s*)?\\d*(?:h\\s*)?\\d*(?:m\\s*)?\\d*(?:s\\s*)?$",
      "type": "string"
    }
  },
  "x-components": {
    "parameters": {
      "Duration": {
        "default": 1,
        "description": "Number of days for which change log is to be returned.",
        "in": "query",
        "maximum": 31,
        "minimum": 1,
        "name": "Time duration",
        "required": false,
        "type": "integer"
      },
      "PageOffset": {
        "default": 0,
        "description": "Number of items to skip from start.",
        "in": "query",
        "minimum": 0,
        "name": "offset",
        "required": false,
        "type": "integer"
      },
      "PageSize": {
        "default": 50,
        "description": "Number of items to return.",
        "in": "query",
        "maximum": 100,
        "minimum": 1,
        "name": "limit",
        "required": false,
        "type": "integer"
      },
      "ParticipantId": {
        "description": "Unique id of participant.",
        "in": "path",
        "name": "participantId",
        "required": true,
        "type": "string"
      },
      "ParticipantTypeId": {
        "description": "Unique id of Participant Type.",
        "in": "path",
        "name": "participantTypeId",
        "required": true,
        "type": "string"
      },
      "ParticipantTypePluralName": {
        "description": "Plural name of the participant type.",
        "in": "path",
        "minLength": 1,
        "name": "participantTypePluralName",
        "required": true,
        "type": "string"
      },
      "Query": {
        "description": "Query criteria. Refer following links for more details:
 - [match](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-match-query.html)
 - [multi_match](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-multi-match-query.html)
 - [term](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-term-query.html)
 - [terms](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-terms-query.html)
 - [range](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-range-query.html)
 - [regexp](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-regexp-query.html)
 - [exists](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-exists-query.html)
 - [fuzzy](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-fuzzy-query.html)
 - [prefix](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-prefix-query.html)
 - [wildcard](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-wildcard-query.html)
 - [match_phrase](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-match-query-phrase.html)
 - [match_phrase_prefix](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-match-query-phrase-prefix.html)",
        "in": "query",
        "name": "query"
      },
      "SelectParticipantFields": {
        "collectionFormat": "multi",
        "description": "Specifies list of attributes to be included in response (id is always included in response). If not specified, all attributes are included in response.",
        "in": "query",
        "items": {
          "type": "string"
        },
        "name": "select",
        "type": "array"
      },
      "SelectParticipantTypeFields": {
        "collectionFormat": "csv",
        "description": "Specifies list of attributes to be included in response. If not specified, all attributes are included in response.",
        "in": "query",
        "items": {
          "enum": [
            "name",
            "isSystem",
            "isActive",
            "ttl"
          ],
          "type": "string"
        },
        "minItems": 0,
        "name": "select",
        "type": "array"
      },
      "StartDateTime": {
        "description": "Start time of the change log in unix epoch format.",
        "in": "query",
        "name": "from",
        "required": true,
        "type": "integer"
      }
    },
    "responses": {
      "ServerErrorResponse": {
        "content": {
          "application/json": {
            "schema": {
              "$ref": "#/definitions/ServerErrorResponse"
            }
          }
        },
        "description": "Error Occurred"
      },
      "ErrorResponse": {
        "content": {
          "application/json": {
            "schema": {
              "$ref": "#/definitions/ErrorResponse"
            }
          }
        },
        "description": "Error Occurred"
      },
      "ParticipantTypesResponse": {
        "content": {
          "application/json": {
            "schema": {
              "$ref": "#/definitions/ParticipantTypesResponse"
            }
          }
        },
        "description": "Participant Types"
      },
      "SuccessResponse": null
    }
  }
}

Steps to reproduce
The above json spec will generate the following code in participant_type_client.go:
func (a *Client) GetParticipantTypes(params *GetParticipantTypesParams, opts ...ClientOption) (*GetParticipantTypesOK, error)

Not that the GetParticipantTypes only return GetParticipantTypesOK interface and not other responses, which can be GetParticipantTypesNotFound, GetParticipantTypesBadRequest, GetParticipantTypesUnauthorized or GetParticipantTypesInternalServerError, which will have similar payload here and cast them as go native error.
Instead it should had been handled as:
func (a *Client) GetParticipantTypes(params *GetParticipantTypesParams, opts ...ClientOption) (*GetParticipantTypesOK, *GetParticipantTypesError, error)

Or,
Handled as:
func (a *Client) GetParticipantTypes(params *GetParticipantTypesParams, opts ...ClientOption) (*GetParticipantTypesOK, *GetParticipantTypesNotFound, *GetParticipantTypesBadRequest, *GetParticipantTypesUnauthorized,  *GetParticipantTypesInternalServerError, error)

I looked at go-swagger tests and this handling happens only for 2xx codes
Environment
swagger version: v0.27.0 (commit: 43c2774170504d87b104e3e4d68626aac2cd447d)
go version: go version go1.16.3 linux/amd64
OS:     Ubuntu 20.04.2 LTS

Non-2xx http responses struct will be returned in error return, and there is no special return positions generated for them.
You can use type assertion on error return to determine which error has occurred.


Device B: Notice conflict, resolve to local journal.
Device B: Connectivity failure, flush pauses.
Device A: Perform QR.
Device B: Re-run conflict resolution on top of QR.
Device B: Flush new MD to server.

Unfortunately, the new MD pushed in the last step still had the root block pointer from the QR's MD.  Basically, the folder_update_prepper didn't do anything interesting in the final CR because the real conflicts had already been resolved in the previous MD, and as a result, it never updated the root block pointer to what it had previously computed.
To get around this, if we pull in an update from a previous unmerged resolutionOp, update the root block pointer on the new MD if it matches that pointer.
Also introduce a test that reproduces the issue without this fix.
Issue: keybase/client#8832

@songgao: The issue was that the root block pointer listed in the current MD was already archived and deleted, because it was unreferenced.  So reading the folder resulted in a "block does not exist" error, which is translated to an EIO.


Wrong layout

@nuno @m1ga  thanks for resolving previous issues.
now if I set all items with the same height it's okay. but when I'm trying to set one item with different height it looked like this.
The layout should be formed before it appears in the list view not when scrolling.
Another question I'm set renderDirection="DIRECTION_RIGHT_TO_LEFT" layout="LAYOUT_WATERFALL" in the listView and there was no change.

@AhmedMohamed2014 sorry, can't help your there since I'm not using it, just made it work with the latest SDK 😄

@m1ga no, I just wanted to say thanks for helping me with first issues 😄.

I think "LAYOUT_WATERFALL" is just for ios, no?
Sorry  I'm not using it too :(
Like @m1ga I  just tried to make it work for you guys!

No problem guys. thanks at all @nuno, but where is the module master.


how to modify the app version?

Electron version:0.36.10
Operating system:OS

i use electron-packager to pack the app. after it ,display the electron.app's information.i see the version is 0.36.10.please tell me how to modify the version as my package.json said(eg:1.0.0).
this is the result:

Add --app-version=1.0.0

Thanks for the answer @walltex
Closing this out.


[DOCS] Reorganizes Overview and Installation chapters

Overview
This PR:

revises the overview section,
adds an installation section.

Preview
Table of Contents

@elasticmachine update branch

@elasticmachine test this please


Add support for preprocessor conditionals

Adds support for preprocessor conditionals #ifdef and #ifndef. Borrowed the grammar structure from tree-sitter-c.
One question I have is which preprocessor conditionals are supported by the grammar spec. I don't know where specifically you look for the official spec, I tried looking at the Zephyr docs but didn't find anything super specific. Basically do we need to support #else, #elif, etc.?

The Zephyr docs don't specify because it's not actually devicetree. It's just the C preprocessor, so if we add any of them, we should add all of

#if
#ifdef
#ifndef
#elif
#else
#endif

@joelspadin I updated the PR to use the full preprocessor conditional grammar from tree-sitter-c along with more tests.

How are the *_in_node versions used?

@nickcoutsos Because the list of possible members is different for top level items and nodes, the preprocessor rules need to be separate to account for that difference. The _in_node stuff is aliases so it produces the same resulting types.
https://github.com/joelspadin/tree-sitter-devicetree/pull/12/files#diff-919ac210accac9ecc55a76d10a7590e3d85ca3f0e165b52d30f08faee486d0cbR168-R169
Hope that makes sense.

Because the list of possible members is different for top level items and nodes

Maybe I'm misunderstanding what you mean, but the C preprocessor doesn't know or care whether preprocessor commands are at the top level or inside a node. I would expect all the preprocessor commands to work everywhere. (They could even appear inside of a multi-line parameter, but I don't think it's worth the effort to support that.)

Okay, the distinction I think I'm seeing is that preproc statements appearing at the top level can wrap other _top_level_item elements whereas the in-node variety is expected to contain other elements of _node_members.
Does this need to account for preprocessor statements "interrupting" devicetree grammar? Or is that a question to be answered down the road?

@joelspadin Any additional thoughts on this PR?  @nickcoutsos is correct about the reason for the top level and node level preprocessor nodes due to the possible children for top level and nodes being different.

Okay, that does make sense. I think I was originally thinking about this as each #if line being its own isolated thing rather than a scope inside which other things would fit. I'll try to find some time to review this later.

Sorry for the long wait on this. This all looks good to me. Thanks!


Fix year 2038 problem at BridgeState#compareUniqueId().

I added compareUniqueId() in last pull-request(#210).  This method will
overflow after January 2038.  Because, it used int/Integer for epoch time.  Sorry.

thanks.


add SegPos and TrimPos support

add SegPos and TrimPos support

Codecov Report

Merging #39 into master will decrease coverage by 2.48%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #39      +/-   ##
==========================================
- Coverage   90.79%   88.31%   -2.49%
==========================================
  Files           9        9
  Lines         641      659      +18
==========================================
  Hits          582      582
- Misses         44       62      +18
  Partials       15       15

Impacted Files
Coverage Δ

gse.go
56.71% <0.00%> (-20.84%)
:arrow_down:

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 5bc5058...1866e7e. Read the comment docs.


portico-pages: A round of design quality control.

This is a round of design quality control relating to the portico pages that fixes obvious design issues.

Automated message from Dropbox CLA bot
@brockwhittaker, it looks like you've already signed the Dropbox CLA. Thanks!

Merged, thanks @brockwhittaker!


Documentation for 'Edit instance-level information' wrong?

This permission (Edit instance-level information) lists permission like create and modify areas & iterations.
But when I give this permission on organization level to a specific user. The only difference I can see is, that this user can edit permissions on other users and security groups.
Is the documentation wrong or the business logic of Azure DevOps

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

ID: c399d3d3-3442-91a7-eb72-f0451b735cd1
Version Independent ID: 5c4f77ec-5ef8-afe7-8e96-f1b4238f8f44
Content: Permissions and role lookup guide - Azure DevOps
Content Source: docs/organizations/security/permissions-lookup-guide.md
Product: devops
Technology: devops-security
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@SebastianSchuetze - Thank you for your inquiry. I will check with the product team and update the relevant documentation soon.

@@SebastianSchuetze - just a follow up, you are correct. The Edit instance-level information was wrong. It primarily supports allowing a user to add/remove security groups and permissions.

Cool. Has the documentation been updated or should I PR this myself?


[🐛] Checkout without having enough money :)

:bug: Bug report
Description

You can use UI-Bypass on checkout to get a negative wallet (To pay without having enough money)
(It could also get a nice Challange :)
:microscope: Minimal Reproduction

Add products to your basket
Make all steps up to the Payment-Method option
Select "Pay using wallet"
Remove class and disabled attribute from the "Pay x" button
Press the button
Checkout with "Place your order and pay"

:deciduous_tree: Your Environment

v12.18.3
6.14.8

Thanks for this nice find! As we already have so many payment related challenges and also at least two where DOM-manipulation is a possible path, we might just want to fix this instead.

I'd like to work on this one.


Client v0.4.0 Release

This issue documents the process of releasing client v0.4. Following are the tasks planned for the release.

[x] Release 0.4.0.dev9 client to pypi for internal testing.
[x] Create a release/0.4 branch
[x] Change version to remove dev tag
[x] After testing approval, release 0.4.0 client to pypi
[x] Mark 23.2.0 server image as latest
[x] Update main branch with internal development code for 0.5 client (current dev version is dev2). Release dev client to pypi.

This client is released to go with the release of 2023R2.

All tasks related to release of 0.4.0 client have been completed


TermControl: force all ambiguous glyphs to be narrow

From Egmont Koblinger:

In terminal emulation, apps have to be able to print something and
keep track of the cursor, whereas they by design have no idea of the
font being used. In many terminals the font can also be changed runtime
and it's absolutely not feasible to then rearrange the cells. In some
other cases there is no font at all (e.g. the libvterm headless terminal
emulation library, or a detached screen/tmux), or there are multiple
fonts at once (a screen/tmux attached from multiple graphical
emulators).

The only way to do that is via some external agreement on the number
of cells, which is typically the Unicode EastAsianWidth, often accessed
via wcwidth(). It's not perfect (changes through Unicode versions, has
ambiguous characters, etc.) but is still the best we have.

glibc's wcwidth() reports 1 for ambiguous width characters, so the de
facto standard is that in terminals they are narrow.

If the glyph is wider then the terminal has to figure out what to do.
It could crop it (newer versions of Konsole, as far as I know), overflow
to the right (VTE), shrink it (Kitty I believe does this), etc.

See Also:
https://bugzilla.gnome.org/show_bug.cgi?id=767529
https://gitlab.freedesktop.org/terminal-wg/specifications/issues/9
https://www.unicode.org/reports/tr11/tr11-34.html
Salient point from proposed update to Unicode Standard Annex #11:

Note: The East_Asian_Width property is not intended for use by modern
terminal emulators without appropriate tailoring on a case-by-case
basis.

Fixes #2066
Fixes #2375
PR Checklist

[x] Closes stuff
[x] written by an employee
[x] Testing sorta done
[ ] ~Requires documentation to be updated~
[x] I've discussed this with core contributors already. AT LENGTH.

Validation Steps Performed
This one has some followup issues. I went wild on it, but it does still have some issues. It makes #900 worse, and introduces a debug break you hit when the renderer and the column counter disagree. It might make the renderer discard the rest of the line it was working on.

@zadjii-msft i can produce a table of all the emoji that exist, and which ones are miscolumned. Would that be sufficient evidence to move #900 forward, do you reckon?

@DHowett-MSFT Probably. I'm probably not going to be the one solving #900 though, that seems more like @miniksa's wheelhouse

@zadjii-msft Mike Griese FTE i can produce a table of all the emoji that exist, and which ones are miscolumned. Would that be sufficient evidence to move #900 forward, do you reckon?

@DHowett-MSFT Dustin Howett FTE Probably. I'm probably not going to be the one solving #900 though, that seems more like @miniksa Michael Niksa FTE's wheelhouse

I'm fine with building such a table, @DHowett-MSFT and resolving the columns. It looks like in #900 that Fcharlie already did something like that


Upload PDF's to Digital Ocean Spaces

Description - upload PDF's to digital ocean so they can be sent to whatsapp as media url via Twilio

Testing - Tested in dev environment and file successfully uploaded to Digital ocean by calling Test Whatsapp PDF as below

Result of test

Screenshot from Digital Ocean Spaces

Technical Debt - However, we will need to check that if a file already exists, it is not reuploaded to Digital Ocean. This might require checking for file. metadata and if we get a response of 200 we do not attempt to upload the file again - files will be unique based on date generated e.g. File uploaded https://foodprintweb.fra1.digitaloceanspaces.com/FoodPrint_ProducePrice_2022-07-04.pdf and perhaps we can add province in the future to the filename.

possible code
// DO Check if file exists by returning metadata /* import HeadObjectCommand from aws-sdk const config = {} const input = {     Bucket: 'your-bucket',     Key: 'test.txt' } const client = new S3Client(config) const command = new HeadObjectCommand(input) const response = await client.send(command) console.log(response) */

@DanielmAaron check this and new env variables


Iter23

⚠ GitGuardian has uncovered 2 secrets following the scan of your pull request.

this is intentional. needed only for testing


fix prettier

@peterjah what does this PR fixes?

@peterjah what does this PR fixes?

It fixes the config of as-prettier which was prettifying 0 files.
It also adds linting of typescript files and json


Parameter annotations (@*Param) from the Jersey2 should be supported in constructor(field)-level injections

Jersey2 parameter annotations won't be added to JSON
Resource:
@Path("/resource/{id}")
@Api(value = "/resource", description = "Summary of injections resource")
@Produces({"application/json", "application/xml"})
public class ResourceWithKnownInjections {

    private Integer constructorParam;
    @QueryParam("fieldParam")
    private String fieldParam; // injection into a class field
    @BeanParam
    private Pagination pagination;

    // injection into a constructor parameter
    @Inject
    public ResourceWithKnownInjections(Integer constructorParam) {
        this.constructorParam = constructorParam;
    }

JSON:
"paths": {
  "/resource/{id}": {
    "get": {
      "tags": [
        "resource"
      ],
      "operationId": "get",
      "produces": [
        "application/xml",
        "application/json"
      ],
      "parameters": [
        {
          "name": "fieldParam",
          "in": "query",
          "required": false,
          "type": "string"
        },
        {
          "name": "methodParam",
          "in": "query",
          "required": false,
          "type": "string"
        }
      ],

Fixed in develop_2.0.


merge problem in Illuminate/Foundation/Console/ModelMakeCommand.php

Laravel Version: 5.5

there's a merge problem on this file : https://github.com/laravel/framework/blob/master/src/Illuminate/Foundation/Console/ModelMakeCommand.php
made by this commit : https://github.com/laravel/framework/commit/5ac005a0fb7d9f2520172869024ea57c03c383e4
and the error was noticed by styleci : https://styleci.io/analyses/Xpg0b2
    protected function getOptions()
    {
        return [
<<<<<<< HEAD
            ['all', 'a', InputOption::VALUE_NONE, 'Generate a migration, factory, and resource controller for the model'],

            ['controller', 'c', InputOption::VALUE_NONE, 'Create a new controller for the model'],

            ['factory', 'f', InputOption::VALUE_NONE, 'Create a new factory for the model'],
=======
            ['force', 'f', InputOption::VALUE_NONE, 'Create the class even if the model already exists.'],

            ['migration', 'm', InputOption::VALUE_NONE, 'Create a new migration file for the model.'],
>>>>>>> 5.4

            ['migration', 'm', InputOption::VALUE_NONE, 'Create a new migration file for the model'],

            ['resource', 'r', InputOption::VALUE_NONE, 'Indicates if the generated controller should be a resource controller.'],
        ];
    }
}

See #19939

Thanks for reporting :)


Handling empty slash slots in URL (Double slash)

What version of Hono are you using?
4.4.5
What runtime/platform is your app running on?
Node
What steps can reproduce the bug?
Opening a URL on Hono with a double slash, like http://localhost:3001/api//account. It doesn't find the route at /api/account.
What is the expected behavior?
I expect the // to be normalized to /.
What do you see instead?
No response
Additional information
It can be solved with a RegEx like:
Find: /\/+/g
Replace: /
OR
Find: /\/{2,}/g
Replace: /

Hi @movahhedi
The router separates paths with /, so supporting it on the routers will be hard. But you can use getPath() function:
https://hono.dev/docs/api/routing#routing-with-hostname
@usualoma Any thoughts?

I am aware that some frameworks treat consecutive "/" as a single "/", but others do not.
I, too, think that in Hono, users can deal with getPath(), so there is no need to change the functionality.

We may be able to remove the extra /s before reaching the routers.
We can also make this optional, which can be set like this:
const hono = new Hono<IHonoEnv>({
	strict: true,
	removeEmptySlots: true,
})

Nevertheless, It can be a functionality of strict: false. So if it's false, it removes the extra /s, and if it's true, it doesn't.

@movahhedi
As mentioned above, we don't have to add a new function. You can use getPath option. Try the following:
import { Hono } from 'hono'
import { getPath } from 'hono/utils/url'

const app = new Hono({
  getPath: (request) => {
    const path = getPath(request)
    return path.replace(/\/+/g, '/')
  },
})

app.get('/api/account', (c) => c.text('/api/account'))

const res = await app.request('/api//account')
console.log(res.status) // 200


Feature Request: Use codegen in headless mode seperate from push

Is your feature request related to a problem? Please describe.
When setting up the build configuration for multiple frontend environments with a shared backend, I have the need to make the build process use amplify pull to get the most up-to-date metadata to connect to the backend (e.x. the aws-exports.js file for a React webapp). However, to use any of the GraphQL statements generated by amplify codegen, it seems like I need to store a copy of the statements in each one of the frontend repositories in order to use them. It would be preferable if I could generate the statements during/after pulling to reduce manually duplicating the same files across multiple repositories.
Describe the solution you'd like
I think either one of these proposed solutions would work, though the latter would most likely be easier to implement.

Give an option when running amplify pull to generate the GraphQL statements if a GraphQL API is detected in the backend (possibly only on the first pull). Something like

The current backend environment has a GraphQL API. Would you like to generate new GraphQl statements? (Y/n)

Along with the other prompts which appear when running amplify codegen. For headless mode, it would work similarly to how it does for amplify push by providing a --codegen flag to the command.

Give amplify codegen add a headless mode, similar to that suggested in aws-amplify/amplify-cli#2005 and aws-amplify/amplify-cli#852. This would allow for automated statement generation if I use amplify pull to get the entire backend definition, which would include the schema. Alternatively, I could just include the schema file in each repository, which would at least minimize the number of files that need to be manually copied and maintained across each one.

Describe alternatives you've considered

Using amplify pull to get the entire backend definition and then using amplify push --codegen in headless mode. This doesn't work in this case since just pulling the backend means there are no changes and thus amplify push doesn't run. Even if it did, it wouldn't be ideal to allow the build process to potentially change the backend since it doesn't need to do so.

up :)

Hi all! 👋  Is there any update on this? I do see there's a PR attached but is in draft now.
I'm trying to use github actions to build and test my app, but it's not working since I cannot generate these files.
Is there another way to have these files generated during a workflow in github? So far the Amplify auth service it's working fine but because it does have a headless interface.
I was trying to use an env variable for the app id inside of .graphqlconfig.yml file and just run amplify codegen in the action but doesn't seem to work neither, so I'm kinda stuck now.

Do you need anything besides code generation from Amplify?
You can use graphql-codegen to generate TS types and React hooks, if that's what's the only thing you need.

I don't need more than code & types generation, but does that mean that I'll need to track graphql/schema.json file? I'm not sure if I would want to track that file since its a large file, is there a way to get the file directly from amplify? like using an url?


Update docker-1.13.0-changelog.md

原文是：
Add capability to specify images used as a cache source on build. These images do not need to have local parent chain and can be pulled from other registries #26839

Oh, a few of my friends have figured out the issue. While I have merged the previous one. If we should keep this, I am afraid that a rebase is needed. WDYT?

Currently, the two combined PR did not change code at all. PTAL

I will close this. Please feel free to tell me if you need any help.


Connect to wireguard through proxy

Wireguard is blocked in Russia so I cannot connect directly.
I want to connect to it through SOCKS4/5 or HTTP proxy:
Me -> Proxy -> Wireguard server -> Internet
How can I connect like this?

Try Amnezia VPN https://github.com/artem-russkikh/wireproxy-awg


Update ingest

Add basic auth, multi-threading, and retry logic to ingest. Add fedora repository initialization command to cli. Fix PCDM hasFile bug.

Coverage decreased (-9.2%) to 88.452% when pulling cce0b33f956e4cc60136d3d92ce83e27d04c9110 on update_ingest into ebdd6279bb9ba550cef62ba99a7a89bf05f9fab3 on master.


wikitude plugin properly added

Thanks for your work on this. One issue:
src/plugins/wikitudePlugin.js
  line 18  col 77  'success' is defined but never used.

Here's the full output:
[00:34:56] Using gulpfile ~/build/driftyco/ng-cordova/gulpfile.js
[00:34:56] Starting 'jshint'...
[00:34:56] Starting 'jscs'...
[00:34:56] Finished 'jscs' after 112 ms
src/plugins/wikitudePlugin.js
  line 18  col 77  'success' is defined but never used.
✖ 1 problem
[00:34:59] 'jshint' errored after 2.63 s
[00:34:59] Error in plugin 'gulp-jshint'
Message:
    JSHint failed for: src/plugins/wikitudePlugin.js
npm ERR! Test failed.  See above for more details.

You can use gulp jscs to run the style checker.

Jshint issue fixed

Drop the dist/ng-cordova.js change and you'll be fine. Just remember when you build to have the commit ignore changes in the dist/* folders

Fixed up! and jscs task executed without error.
Regards.

The only remaining issue is that you shouldn't have any changes in the dist/* folders (reason being, that's an artifact folder and changes there are really hard to merge in; so we make changes there when we release).

@gortok sorry I forgot that part, is ready.

Unfortunately you can't just add the .gitignore to the dist/ folder, since we do rely on that folder; it's a build artifact that is used in master to allow for bower installs.

Ok sure, sorry about that, but how can i do it?

revert the files you changed in dist/ to their previous state (before you messed with them) http://stackoverflow.com/questions/215718/reset-or-revert-a-specific-file-to-a-specific-revision-using-git

Finally achieved, I hope ..

@yailPeralta Your commit still shows the dist change: https://github.com/driftyco/ng-cordova/pull/1278/files
Isn't Git fun?


kdeconnect: fix empty buttons

Motivation for this change
on xfce at least, some buttons in kdeconnect are completely blank because of a missing icon theme.
Things done

[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"
[ ] 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
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 122859 at 223d3c0c run on aarch64-linux 1

1 package marked as broken and skipped:

libsForQt512.kdeconnect-kde

2 packages built successfully:

libsForQt5.kdeconnect-kde (libsForQt515.kdeconnect-kde ,plasma5Packages.kdeconnect-kde)
libsForQt514.kdeconnect-kde


Could not find type "SteamMultiplayerPeer" in the current scope.

Tried upgrading to 0.2 and I can't find anything online about how to fix this.
I've tried deleting .godot and reloading editor.
Anyone else get this error? Am I missing something about how to install this? It was working fine before I upgraded

had to do this again!
https://github.com/expressobits/steam-multiplayer-peer/issues/23


How to adjust the size of the image

from torchvision.models.feature_extraction import create_feature_extractor
import random
import seaborn as sns
import matplotlib.pyplot as plt
return_nodes = ['blocks.0', 'blocks.10', 'blocks.20', 'blocks.23']
feat_ext = create_feature_extractor(model, return_nodes=return_nodes)
with torch.no_grad():
out = feat_ext(inps[0])
fig, ax = plt.subplots(4, 5, figsize=(25, 20))
Pick 4 random feature maps from each layer
for i, layer in enumerate(return_nodes):
feat_maps = out[layer].numpy().squeeze(0)
feat_maps = random.sample(list(feat_maps), 4)
ax[i][0].imshow(imgs[0])
ax[i][0].set_xticks([])
ax[i][0].set_yticks([])
for j, feat_map in enumerate(feat_maps):
sns.heatmap(feat_map, ax=ax[i][j+1], cbar=False)
ax[i][j+1].set_xticks([])
ax[i][j+1].set_yticks([])
ax[i][j+1].set_title(f'{layer}: ({feat_map.shape[0]} x {feat_map.shape[1]})')
Got this error
IndexError                                Traceback (most recent call last)
 in
21     ax[i][0].set_yticks([])
22     for j, feat_map in enumerate(feat_maps):
---> 23         sns.heatmap(feat_map, ax=ax[i][j+1], cbar=False)
24         ax[i][j+1].set_xticks([])
25         ax[i][j+1].set_yticks([])
3 frames
/usr/local/lib/python3.8/dist-packages/numpy/ma/core.py in masked_where(condition, a, copy)
1927     (cshape, ashape) = (cond.shape, a.shape)
1928     if cshape and cshape != ashape:
-> 1929         raise IndexError("Inconsistent shape between the condition and the input"
1930                          " (got %s and %s)" % (cshape, ashape))
1931     if hasattr(a, '_mask'):
IndexError: Inconsistent shape between the condition and the input (got (1024, 1) and (1024,))

I don't think there is any bug here related to timm, and usage wrt to timm is not actually clear (but this approach should work for getting feature maps, just be aware the feature maps are B, N, C (where N is flattened token sequence, so need to reshape to H, W)


Fix AmbiguousExpander (Issue #1214)

Fixes #1214.
Surprisingly, this bug has been around since 0.6.6.

Wow, that's almost 4 years ago! Wild.
Thanks for fixing it!!


langchain: minimal update to OpenAIModerationChain for openai >1.0.0

Description: OpenAIModerationChain() is not compatible with openai v1.0.0+. This minor change tries the v1+ format first, then falls back to the old code.
Issue: Fixes https://github.com/langchain-ai/langchain/issues/13685. Avoids the more extensive edits proposed in https://github.com/langchain-ai/langchain/pull/14317 and maintains compatibility with older versions.
Dependencies: None.

Will this be available in the next langChain release?

Thank you for this. We merged another implementation (https://github.com/langchain-ai/langchain/pull/18537) as unfortunately there were some duplicates and I didn't see this one.
This was released in langchain 0.1.20, please test it out. Closing this PR but let me know if you continue to run into issues.


Introduction transition to watched status marks by profile

Check if this PR fulfills these requirements:

[x] My changes respect the Kodi add-on development rules
[x] I have read the CONTRIBUTING document.
[x] I made sure there wasn't another one Pull Requests opened for the same update/change
[x] I have successfully tested my changes locally

Types of changes

[ ] New feature (non-breaking change which adds functionality)
[ ] Feature change (non-breaking change which change behaviour of an existing functionality)
[x] Improvement (non-breaking change which improve functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Description

Before or after it was mandatory to do it,
we need to distinguish watched status marks between the profiles,
this will allow the best integration with a future implementation with the watched status of netflix,
this also prevents the data from the kodi database from being mixed between the profiles.
Unfortunately many users will complain, they will lose all their watched status marks
for the moment i left the choice to the user to activate or not this option (in expert settings)
and even after the add-on update, you will be asked the choice at the first time you start the addon.
Unfortunately this choice for the users will be temporary because in the next versions the transition will be permanent!
❕So i suggest users to start to mark any important tv show episodes already seen❕
Issue Ref. #135
In case of Feature change / Breaking change:
Describe the current behavior

Describe the new behavior

Screenshots (if appropriate):

So i suggest users to start to mark any important tv show episodes already seen
On Netflix page or in addon?

when you browse the lists in the addon,
so not in kodi library, and not in netflix website


Update Go version to 1.18

Currently, the project is based on the 1.14 Go version. Let's upgrade the Go version to 1.18
Also, golang.org/x/net v0.0.0-20220706163947-c90051bbdb60 package has the vulnerability

Please assign the issue to me. Thanks

The go version i go.mod is the minimum-supported version, and we want to keep it as is. See https://go.dev/doc/modules/gomod-ref#go


fud Fails to Run xclbins Targeted for Hardware on FPGAs

Seems like I was wrong in saying that fpga execution was working. Some configurations I thought were making my xclbin compilations target hardware were not doing that, but rather still targeting hardware emulation. Sorry about the mixed messages.
PYNQ is failing to find active_devices and is raising a RuntimeError as a result. Spent some time digging at this but unfortunately some suggestions I found don't seem to solve things. Some things went a bit over my head but I will dig more into them and see what I can come up with.
cc @sampsyo as the last person to work on this AFAIK.

For sake of completeness, sharing some steps to repo and some error logs. There is a new error compared to initial issue. Now Havarti is "failing to lock device."
An xclbin was created targeting hardware. This required changing part of the fud configuration to
[stages.xclbin]
mode = "hw"
device = "xilinx_u50_gen3x16_xdma_201920_3"
temp_location = "/tmp"
ssh_host = ""
ssh_username = ""

(Everything included for completeness, relevant line is mode = "hw".)
Afterwords, invoking the following:
fud e dot-product-hw-mode.xclbin --to fpga --from xclbin -s fpga.data <path>/examples/dahlia/dot-product.fuse.data -vvv
Leads to the following stacktrace
Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/scratch/nrn25/data/calyx_fpga/lib/python3.8/site-packages/fud/xclrun.py", line 144, in <module>
    xclrun()
  File "/scratch/nrn25/data/calyx_fpga/lib/python3.8/site-packages/fud/xclrun.py", line 136, in xclrun
    out_data = run(Path(args.bin), in_data)
  File "/scratch/nrn25/data/calyx_fpga/lib/python3.8/site-packages/fud/xclrun.py", line 81, in run
    ol = pynq.Overlay(str(xclbin.resolve(strict=True)))
  File "/scratch/nrn25/data/calyx_fpga/lib/python3.8/site-packages/pynq/overlay.py", line 348, in __init__
    self.download()
  File "/scratch/nrn25/data/calyx_fpga/lib/python3.8/site-packages/pynq/overlay.py", line 428, in download
    super().download(self.parser)
  File "/scratch/nrn25/data/calyx_fpga/lib/python3.8/site-packages/pynq/bitstream.py", line 168, in download
    self.device.download(self, parser)
  File "/scratch/nrn25/data/calyx_fpga/lib/python3.8/site-packages/pynq/pl_server/xrt_device.py", line 541, in download
    self._xrt_download(data)
  File "/scratch/nrn25/data/calyx_fpga/lib/python3.8/site-packages/pynq/pl_server/xrt_device.py", line 522, in _xrt_download
    raise RuntimeError("Could not lock device for programming - " + str(err))
RuntimeError: Could not lock device for programming - -19

Tried looking for error code -19 but a brief google search did not find much w.r.t xrt error codes.

Cool; this really could be worse! It kinda feels like it could be a permissions issue or something.
Anyway, I might recommend trying to debug this outside of fud. That means executing xclrun manually, doing something like this:
$ source /scratch/opt/Xilinx/Vitis/2020.2/settings64.sh
$ source /opt/xilinx/xrt/setup.sh
$ python3.8 fud/xclrun.py <something> foo.xclbin

(You can probably get the actual xclrun command, in the last line, from a verbose fud execution.) One random thing to try would be just doing that under a sudo to see if it wants you to be the root user to access the real FPGA. Another could be to try confirming that XRT can see the FPGA device at all… for example, XRT's xbtop command is supposed to just list the attached cards:
https://xilinx.github.io/XRT/2023.1/html/xbtop.html
Maybe poking around at some of those commands would reveal if there's something obviously wrong with the whole FPGA setup in havarti?

I ended up with a moment to look into this! I reproduced stuff as described above, and I first ran into the same issue about the XCL_EMULATION_MODE environment variable as you, @nathanielnrn. I embarrassingly did not notice that you had a fix on a branch and ended up recreating the same idea myself, with some extra bells and whistles, in #1728. If that looks right to you, @nathanielnrn, please merge at will.
Then I went about reproducing your "Could not lock device for programming" trouble. The TL;DR is that you can work around this problem on havarti by setting this in your fud config:
[stages.fpga]
xrt_location = "/opt/xilinx/xrt"

Details below.

The key was indeed running xclrun "by itself," which amounted to this command:
XRT_INI_PATH=`pwd`/xrt.ini bash -c 'source /scratch/opt/Xilinx/Vitis/2020.2/settings64.sh ; source /scratch/opt/xilinx/xrt/setup.sh ; python3.9 -m fud.xclrun lti.hw.xclbin examples/tutorial/data.json'

That revealed a new, more specific error before the Python program crashed:
[XRT] ERROR: Failed to open /sys/bus/pci/devices/0000:3b:00.1//kds_numcdmas for reading: No such file or directory

Clearly, something is going wrong when the XRT user-space library tries to communicate with the PCI card (via its associated kernel driver). I investigated a little bit and found that a file there called kds_numcdma exists, but not the plural. Curious!
A little googling lead me to https://github.com/Xilinx/XRT/pull/6056, the XRT PR where this changed on the user-space side. (Thank goodness this library is open source; I might otherwise never have figured it out.) The clear conclusion is that we are dealing with a version mismatch: the kernel module is old (using kds_numcdma) and the user-space library is new (using kds_numcdmas).
While I don't exactly know why this happens, there is a conspicuous underlying reason. Havarti has two versions of the XRT library installed on it, at /opt/xilinx/xrt and /scratch/opt/xilinx/xrt. The former is old (2.8.743, aka 2020.2) and the latter is newer (2.13.0, built 7/28/2022). I guess the former must be the one whose kernel modules are currently active.
A good way to fix this would be to just install a fresh 2023 version of XRT and make sure that all its pieces are up to date, and maybe delete the old versions if we're sure we don't need them. (If either @nathanielnrn or @evanmwilliams wants to take this thankless task up, that would be awesome.) But a lazy solution is just to switch to using the old version of the XRT userspace library, by changing your fud config as depicted above.

This is great! Thank you for looking into this. I spent much of yesterday looking into a EINVAL (22) Invalid argument error but this seems to have short circuited the need to look into that. I will try to look into fresh-installs of xrt but that may be a few weeks out at this point.


doc/nixos-rebuild(8): add Nix options to summary

Motivation for this change
It seems as the sentence at the bottom of the option summary about
Nix-specific options isn't enough, it's probably more helpful to list
those options in the synopsis as well.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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 nix-review --run "nix-review wip"
[ ] 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)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build manpages


Json from url function

Hello.
I think your application is really cool and yours is EXACTLY THE ONE I was looking for.
One thing, I assume it would be more cool if data could be retrieved from server directly.
So I edited your main, command-line-interface file to make it able to.
And I am also considering about automatic file including to xcodeproject when the model file created. What do you think?

Thanks but I'm not going to merge this into my project. Supporting network access is a slippery slope. It starts with simple HTTP(S) calls, but then people will want FTP, and passing POST body data, and query parameter serialization, etc.


Crash when changing georeferences

Sorry of the "unspecific" description, I just want to note this here, and it has to be investigated further:
While trying out a tutorial, I made some mistake and started moving and deleting some geo references that I accidentally duplicated (I think by moving actors between sublevels). At some point, UE crashed:
Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000000

UE4Editor_CesiumRuntime!ACesiumGeoreference::TransformUeToEcef() [c:\users\travis\build\cesiumgs\packages\cesiumforunreal\hostproject\plugins\cesiumforunreal\source\cesiumruntime\private\cesiumgeoreference.cpp:623]
UE4Editor_CesiumRuntime!AGlobeAwareDefaultPawn::Tick() [c:\users\travis\build\cesiumgs\packages\cesiumforunreal\hostproject\plugins\cesiumforunreal\source\cesiumruntime\private\globeawaredefaultpawn.cpp:372]
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Core
UE4Editor_Core
UE4Editor_Core
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_UnrealEd
UE4Editor_UnrealEd
UE4Editor
UE4Editor
UE4Editor
UE4Editor
UE4Editor
kernel32
ntdll

I'll have to figure out how exactly this can be reproduced, but it likely means that at https://github.com/CesiumGS/cesium-unreal/blob/908a34fbfff2b81f32d81d4704ccb19702205519/Source/CesiumRuntime/Private/CesiumGeoreference.cpp#L622 , either the World (or less likely, the OriginLocation) had been nullptr for some reason.

To keep the record here: The issue can be reproduced reliably when deleting a georeference (and ignoring the message about the brken references). The intended behavior after deletion may not be entirely clear, but ... "it should not crash" is the baseline :-)
According to a comment by @xuelongmu

Doing an IsValid(GeoreferenceActor) check on whatever code is invoking the GeoreferenceActor methods will ensure that the GeoreferenceActor is a) not null and b) not pending kill (aka removed from world and will be cleaned up on the next garbage collection cycle). I agree that checking IsValid(this->GetWorld) in the TransformUeToEcef function call is a good idea as well.

the check should not only be a null check (because that wouldn't consider pending removal), but a dedicated IsValid check, so I'd add that soon.

This is strongly enough related to mention it here: Whe setting the georeference of a tileset to None (the default), and pressing "Play", the UE crashes. And this crash is remarkably hard. It does not even show a crash message. It's just gone.
The reason for that is that the "simple" solution of just adding null/IsValid checks (as in https://github.com/CesiumGS/cesium-unreal/blob/main/Source/CesiumRuntime/Private/Cesium3DTilesetRoot.cpp#L88 ) has a ripple effect: When this is done, some matrix remains 0, and this matrix is used to transform some vector (which becomes 0), and this vector is used as a normal vector for the view volume computation, and this creates a Plane, and the constructor of Plane throws up in this case ...
However, the georeference is used quite a lot in the pawn and tileset classes, and I'll try to wrap these usages into IsValid checks. But there may be cases where this raises a question, and this is broadly: What to do in the else case? I assume that much of this can be solved by "just using the identity matrix", but it may not always be that simple and obvious.

The changes in the PR should prevent the crashes, at least insofar that deleting the georeference causes the Unreal message about broken references, but it is still possible to "Play" without crashing. (Of course, deleting the Georeference only on either one tileset or the pawn causes no valid rendering, but I'd say this is anticipated).
Generally, the Georeference that is used in the pawn or tileset can become null (or invalid) ~"at any point in time", and this is now handled by checking IsValid(this->Georeference), and trying to fall back to some sensible default. But there doesn't seem to be a sensible solution for the remaining usages, mainly around https://github.com/CesiumGS/cesium-unreal/blob/main/Source/CesiumRuntime/Private/GlobeAwareDefaultPawn.cpp#L343 where the georeference is used for updating the rotation during a flight.
(In doubt, one could just "end the flight" when the georeference becomes invalid - I'm not sure whether this code path can even be reached when the georeference is not valid)

But more broadly, while adding the fixes until now, I wondered: Should actors and pawns without a georeference work sensibly in general? I think this could be accomplished generically and elegantly, by just saying: If you don't have a georeference, then everything is ~"in Unreal World coordinates". This may be desirable for some cases - if somebody just wants to walk around on a tileset, but does not really care about its location on the globe - but I'm not sure whether this can be implemented consistently. Specifically, it might mean that some latitude/longitude would brutally be interpreted as x/y coordinates in some cases. And if this is a goal, I still have to wrap my head around some geospecialities...

Fixed in #329.


add attribute to injection symbol

This attribute is used by the llvm backend to decide how to implement the triangle axiom.

Jenkins: test this please

Jenkins: test this please


Redirect from other domains

made request to ISP, can take up to 48 hours for https redirect to work. leaving open until i confirm.

working already!


Update INSTALLING.md

Ticket
(https://github.com/tenstorrent/tt-metal/issues/15499)
Problem description
Numbered lists flowing into different steps, confused hierarchical levels.
What's changed
Numbered list fixed, options assigned to lower hierarchical level.
Checklist

[ ] Post commit CI passes
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] Device performance regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

Why doc_cat: ttnn ? Just a minor question


Implement Java version of the stable marriage problem.

@Gustorn Have you had time to look over the changes? Just realized this has been sitting untouched for some weeks now.

I reviewed the changes you made and found everything like @Gustorn requested it. I also went ahead and checked that everything displays properly on the website. I'll go ahead and merge this.


Add Payment Delegation Commands to CLI

Description
Allow validator payment delegation to be managed via the CLI

add support to allocate a fraction of rewards by delegating to a named
beneficiary from the cli
new cli commands for get, set, and delete within account
add cli documentation
expose functionality available in Accounts.so

Other changes
None
Demo
Here is a video demo of this pull request
Testing

Exploratory testing against a local development node to run each newly introduced cli command and can successfully set and then get the fraction associated with an account, delete clears. See demo above.
Added unit tests to match the flow described above and demo.

Related issues
See this pull request introduced by @m-chrzan which are the contract methods the cli calls into
Backwards compatibility
NA No existing code was edited
Documentation
The following docs fork will be updated to reflect all functionality here and a PR opened once this PR has been merged.
https://github.com/spiralsprotocol/celo-org-docs/tree/spirals/expose-payment-delegation-in-cli

Added a video demo — view here

Hey @m-chrzan @jcortejoso I think I fixed the circleci that had failed by checking in generated md file related to account.md which had been updated.
Would one of you kick off the circle ci tests once more?
Thank you!!!

Rebased my commits on top of master for clarity

@jcortejoso Is this command live? Which celocli version? I've upgraded to 1.6.3 and it hasn't appeared yet.

@jcortejoso Is this command live? Which celocli version? I've upgraded to 1.6.3 and it hasn't appeared yet.

It looks like it was merged right after the release was cut.
Gonna do another release next week

Just commenting here for visibility to those subscribed to this issue.
I'm attempting to use this function to delegate to Spirals, however there is a check that the beneficiary is a registered Account. Why is this? Shouldn't we be able to delegate to any valid EOA or contract address? Just questioning that restriction on the final solution, as I imagine many people would like to use this not only for giving purposes to Spirals, but for practical accounting reasons - to automate the sweeping of 100% of their rewards to an EOA or exchange contract every epoch.

Hi @aaronmboyd! Thanks for the comment. We'll look into this.

Forgot to mention, it fails trying this with Spirals because their multi-sig is not a registered Account and cannot be a beneficiary for this function.

Thank you @aaronmboyd! I'll take a close look this week


Travis failure in 1.1.1

Travis is failing on s390x with the following error:
In file included from test/handshake_helper.c:23:
test/handshake_helper.c: In function 'do_handshake_internal':
test/testutil.h:291:31: error: 'alpn_protos_len' may be used uninitialized in this function [-Werror=maybe-uninitialized]
  291 | # define TEST_int_eq(a, b)    test_int_eq(__FILE__, __LINE__, #a, #b, a, b)
      |                               ^~~~~~~~~~~
test/handshake_helper.c:640:16: note: 'alpn_protos_len' was declared here
  640 |         size_t alpn_protos_len;
      |                ^~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:9106: test/handshake_helper.o] Error 1
make: *** [Makefile:174: all] Error 2

Do we have reason to believe this is anything other than the usual -Wmaybe-uninitialized flakiness?

Do we have reason to believe this is anything other than the usual -Wmaybe-uninitialized flakiness?

It's only in the last 3 builds, so it's at least new.

It's only in the last 3 builds, so it's at least new.

But the code doesn't seem to have changed -- did the compiler version change?

Only those 3 builds used gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
while previous builds used gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0


Shop Management System

You are now blessed with Open Source Super Powers!

You are now blessed with Open Source Super Powers!


Optimized API call, query timing for the table aws_ec2_instance_type and added support to accept the wildcard pattern(t2*) for instance type. Closes #2292

Integration test logs

Logs
N/A

Example query results

Results
> select instance_type, instance_type_pattern from aws_ec2_instance_type where instance_type_pattern = 'c7i.*'
+----------------+-----------------------+
| instance_type  | instance_type_pattern |
+----------------+-----------------------+
| c7i.16xlarge   | c7i.*                 |
| c7i.xlarge     | c7i.*                 |
| c7i.large      | c7i.*                 |
| c7i.metal-48xl | c7i.*                 |
| c7i.4xlarge    | c7i.*                 |
| c7i.2xlarge    | c7i.*                 |

Changes Overview:
API Call Optimization:

The table now makes 2 API calls per query, compared to earlier where it made API calls for each row.
Query execution time has been reduced by ~75%.

Performance Comparison:
Earlier (73.8s):
> select count(*) from aws_ec2_instance_type;
+-------+
| count |
+-------+
| 11403 |
+-------+

Time: 73.8s. Rows returned: 1. Rows fetched: 11,380. Hydrate calls: 11,403.

Now (12.2s):
> select count(*) from aws_ec2_instance_type;
+-------+
| count |
+-------+
| 11403 |
+-------+

Time: 12.2s. Rows returned: 1. Rows fetched: 11,403. Hydrate calls: 0.

Wildcard Search Support:

Added a new column: instance_type_pattern to enable wildcard pattern searches.
In the query select * from aws_ec2_instance_type where instance_type = 't2*', the API returned empty rows due to PostgreSQL-level filtering.

The instance_type column contains exact values like 't2.small', not 't2*', causing a mismatch between the column value and the wildcard pattern.
To address this, the instance_type_pattern column was introduced to allow proper filtering using wildcard patterns.

Example Query:
> select instance_type, instance_type_pattern from aws_ec2_instance_type where instance_type_pattern = 'c7i.*';
+----------------+-----------------------+
| instance_type  | instance_type_pattern |
+----------------+-----------------------+
| c7i.16xlarge   | c7i.*                 |
| c7i.xlarge     | c7i.*                 |
| c7i.large      | c7i.*                 |
| c7i.metal-48xl | c7i.*                 |
| c7i.4xlarge    | c7i.*                 |
| c7i.2xlarge    | c7i.*                 |
| c7i.metal-24xl | c7i.*                 |
| c7i.8xlarge    | c7i.*                 |
| c7i.12xlarge   | c7i.*                 |

Time: 1.3s. Rows returned: 176. Rows fetched: 176. Hydrate calls: 0.

Scans:
  1) aws_ec2_instance_type.aws: Time: 1.2s. Fetched: 176. Hydrates: 0. Quals: instance_type_pattern = 'c7i.*'.

The above query fetched and displayed 176 rows in just 1.3 seconds.

@e-gineer / @misraved, your feedback on the table design and suggestions regarding the column naming for instance_type_pattern would be greatly appreciated.
Thank you!

@misraved, thank you for the suggestion! I’ve updated the logic to optimize the API call using the limit query parameter.