test: migrate all packages from Flutter driver to integration tests

Description
The integration_test package is the new way to write e2e tests. Therefore, this PR migrates the tests from driver tests to integration tests.
As side effect, we see that the Android CI e2e tests pipeline is way more stable.
ToDos:

[ ] Migrate cloud_firestore
[x] Migrate cloud_functions
[x] Migrate firebase_analytics
[x] Migrate firebase_app_installations
[x] Migrate firebase_auth
[x] Migrate firebase_core
[x] Migrate firebase_crashlytics
[x] Migrate firebase_database
[x] Migrate firebase_dynamic_links
[x] Migrate firebase_in_app_messaging
[ ] Migrate firebase_ml_model_downloader
[ ] Migrate firebase_remote_config
[x] Migrate firebase_messaging
[ ] Migrate firebase_storage
[ ] Migrate firebase_firestore_odm
[ ] Migrate firebase_performance
[ ] Delete driver tests (test_driver/ folder)
[ ] Remove drive as dependency
[ ] Mark drive dependency on pub.dev as discontinued?
[ ] Check if CI is flaky (run CI 50 times)
[ ] Update docs on how to run integration tests

Related Issues
Closes #8909
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

finally

Hey @nilsreichardt, I've fixed the merge conflicts for you. Let me know if you need any further assistance 🙏

Thanks, @russellwheatley 🙏

Hey @russellwheatley, could you again merge the master into this branch?

Done, @nilsreichardt 😄

I started from scratch and opened a new PR where I migrated all packages in one PR: https://github.com/firebase/flutterfire/pull/9649


BoxPlot does not render correctly

Description
Following is a modified sample box-lot with only one time-series and random generated 10 float values.
At least 3rd quartile and max value are incorrectly displayed.
I've tried other random samples, but got mostly incorrectly rendered plots.
https://codepen.io/nineclue/pen/oNQmbgp
Steps to Reproduce
var options = {
  series: [
    {
      type: "boxPlot",
      data: [
        {
          x: "Jan 2015",
          y: [12.2, 16.5, 16.8, 17.0, 17.0, 21.7, 25.7, 26.1, 26.5, 29.2]
        }
      ]
    }
  ],
  chart: {
    type: "boxPlot",
    height: 350
  },
  title: {
    text: "Basic BoxPlot Chart",
    align: "left"
  },
  plotOptions: {
    boxPlot: {
      colors: {
        upper: "#5C4742",
        lower: "#A5978B"
      }
    }
  }
};

var chart = new ApexCharts(document.querySelector("#chart"), options);
chart.render();

Expected Behavior
max value should be 29.2 and 3rd quartile should be around 25~6
Actual Behavior
both of them are less than 20
Screenshots

Reproduction Link
https://codepen.io/nineclue/pen/oNQmbgp

I just found that boxplot data should be pre-calculated 5 numbers (min, 1st quartile, median, 3rd quartile, max - handleCandleStickBoxDataFormat function in Modules/Data.js)
https://github.com/apexcharts/apexcharts.js/blob/127b6d5c3feda721356c5862b525a769227241d5/src/modules/Data.js#L311
I'll close the issue.


SVG performance issues in Firefox

We use LayerImage to show SVG picture on map and we rotate SVG picture in "prerender".
You can check code here https://codesandbox.io/p/sandbox/openlayers-9-2-4-svg-issue-forked-lrct37?file=%2Findex.js%3A35%2C43
Everything works fine in Chrome but zoom or pan of map is lagging in Firefox.
If rotation is turned off then zoom or pan is not lagging anymore in Firefox.
Set Rotation to 0 to try example without rotation:

Do you please have some advice how to improve code to enhance performance in Firefox? Did we implement rotation of SVG picture correctly?
Thanks

That is caused by the very poor performance of the Firefox ctx.drawImage() method when drawing an SVG image if the context has a rotation or skew applied.  It can also be seen when rendering a large number of rotated SVG icon styles.  To make it useable (with poor quality) in Firefox while working as normal in other browsers you could set the loader according to the browser, for example load: FIREFOX ? decode : load,.  A better method would be to use a custom layer (such as adapting https://openlayers.org/en/main/examples/svg-layer.html to your needs, see https://github.com/openlayers/openlayers/issues/14788#issuecomment-1576837349).

I tried your suggestions. SVG has really poor quality with "decode" so it is useless. Your second proposal looks better but SVG is blurry for couple of seconds in Firefox. It is acceptable but sometimes it doesn't get sharp. I need to pan/move map to get it sharp. You can try it in your example https://openlayers.org/en/main/examples/svg-layer.html but it is better visible here https://github.com/openlayers/openlayers/issues/14788#issuecomment-1576837349. How can I make SVG sharp without pan/move map?


Temporal Client send signal to different namespace

Is your feature request related to a problem? Please describe.
I have to send signal to different namespaces, but temporal client only allows to send signal to workflows in same namespace
Describe the solution you'd like
SignalWorkflow just passes the namespace of client. May be we can encode the namespace to context (WtihWorkflowNamespace, just like workflow version), and use namespace in SignalWorkflow function (if exists).
Describe alternatives you've considered
Current solution to send signal to different namespace using custom workflow, where I send the signal to different namespace.
Additional context
It is possible to send the signal to different namespaces within workflow, using WithWorkflowNamespace. We could have same functionality for client.

One simple function to change namespace property of Client would be just fine too.

With #641, you will be able to use the gRPC service directly to send signals in any way to any namespace. I will update when implemented.

This has been implemented. You can now use the gRPC service directly to make whatever calls you want. Does this solve your need?

Yes @cretz.


fix: PERCENTAGE WIDTH bugfix on iOS safari

Some bugs created on iOS safari because of movable touch container.
I would finished running karma and testing on iPhone 6 :)

Works for me fine... thanks

LGTM, just change the commit msg to something like: fix: PERCENTAGE WIDTH bugfix on iOS safari ... that semantic-release can do the release.
Max

@meandmax I changed it, thanks.


colon gets added in media query

Using command line with "stylusSupremacy.insertColons": false option
@media (min-width 100px) gets converted to @media (min-width: 100px)
Both works for stylus, but I was expecting colons to get removed, not added

This will be fixed in v2.14.2 or newer.


Issue #14 Replace mx.ui.action with mx.data.action

@michel-jump thank you so much for you contribution. Please when making PR for fixes, change only necessary lines the fixed the issue, without changing formatting, like line ending, quotes, trailing commas and indents. Especially if the divert from the Mendix standard. Single line changes are easier to merge and release.

If a new pull request is made that changes only the mx.ui.action to mx.data.action, will it be accepted? If so, how long will it take for the widget to be updated in the app store?


feat(conf) add handle_errors to config

Summary
We would like to able to present errors resulting from Kong (and ultimately upstreams) in a consistent manner.
Currently, internal/NGINX errors are handled via https://github.com/Kong/kong/blob/next/kong/error_handlers.lua through use of the error_page directives at https://github.com/Kong/kong/blob/ce43f03d67c52c1b8612240cfce6e26438ffb783/kong/templates/nginx_kong.lua#L87-L88
This nicely wraps up the error and returns it in the format specified via the accept header. However, any plugins, including core Kong code (e.g. route matching) make use of kong.response.exit() instead which results in the response being returned directly to the calling application through use of ngx.print(body).
For our own plugins, we could adjust the response we send via kong.response.send however, it is unfeasible to do this for all responses on all plugins we may use. Thus, for us to be able to handle, and return, errors to a calling application in a consistent manner we would need to override both error_handlers.lua and pdk/response.lua. By introducing a new config item handle_errors where, when set, Kong would not make use of ngx.print, we can ensure that any HTTP error (set in the error_page directives) are ultimately handled by error_handlers.lua. error_handlers.lua can, in turn,  easily be customised and overriden to provide a consistent error response for any 400+ status generated within Kong.
In addition, it becomes fairly trivial to handle upstream errors in the same fashion through use of a plugin operating on header_filter. E.g.
function ProxyErrorsHandler:header_filter(conf)
  ProxyErrorsHandler.super.header_filter(self)

  local status = kong.response.get_status()
  if kong.configuration.handle_errors and status >= 400 and not ngx.ctx.ERROR_HANDLED then
    local error_message = kong.response.get_header(conf.custom_error_header)

    if error_message then
      ngx.ctx.error_body = { message = error_message }
    end

    return ngx.exit(status)
  end
end

In doing so, this enables us present consistent errors for all requests proxied via Kong and, to be able to pass error context from the upstream to a standard error handler - something that is not possible using the standard nginx directive proxy_intercept_errors.
Full changelog

Add boolean config option handle_errors - defaulted to false/off
Before sending response, check handle_errors config. If set to true and ngx.config.subsystem == "http" and status >= 400 then set ctx.error_body and ctx.error_headers and exit without writing to response.
Attempt to read ctx.error_body and ctx.error_headers within error handling and set message and headers accordingly if these are populated.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

A couple notes for the time being pending initial review of concept:

I am aware that I haven't added tests for this. Would be happy to do so, if someone can point me in the right direction
Documentation updates will also be required?

@thibaultcha any chance you've managed to give this PR some thought?

@hishamhm, @kikito, @bungle - sorry to ping all of you but not sure who to contact here. Am sure everyone has lots on their plate but the lack of any form of feedback/commentary to this PR after 1.5 months makes me wonder if it has slipped through the cracks? Can anyone provide some form of feedback on this request? Is the feature something you would consider, or perhaps are even looking into but would rather take a different approach? Or, is this just a hard no?

@Tieske, sorry to be spamming you today, but this one came up again during my upgrade to 1.4.0 and the attempt to get rid of any forked code. Back at the summit we had a discussion regarding community engagement and this PR as I wanted to try to understand how you and the rest of the team wanted/preferred to interact with community. Your suggestion to me back then was to ping folks if time dragged on. I have now tried that and have run out of ideas once again. All I'm really looking for is acknowledgement from someone at Kong that this is either not something you're interested in or something you're interested in but need time to get to it or, even, would rather take a different/your own approach. At least then I can weigh up my own options going forward. But the complete lack of any form of communication around this PR after almost 2 months is frustrating and somewhat of a mystery to me and so I'm hoping you can perhaps help me resolve that?

You see, I am not totally in love with handler_errors boolean config option.

Yeah, I agree with you. I didn't particularly like this either but given that I don't have a good view of the bigger picture I though it would be best to approach this in a way that it wouldn't introduce any breaking changes and that seemed like the easiest option from my point of view at the time.
Your point regarding plugins not wanting to respect the accept header is certainly a good one. Even in the HTTP spec observance of the accept header is optional. Ultimately what error_handlers.lua is doing now is a very simple form of proactive content negotiation (https://tools.ietf.org/html/rfc7231#section-3.4) and we are looking to extend that functionality to all responses generated by Kong code/plugins.
With that said, I do still wonder if the situation where a plugin wishes to ignore the accept header is more of an exception than the norm. I am also hesitant to go with a solution based around the exceptions for the sake of avoiding a breaking change. Of course, I may be completely wrong here in what the norm vs the exception really is. My preference would be to go with sensible defaults whilst providing existing implementations a mechanism to maintain current functionality if so desired. To that end I wonder if I couldn't suggest:
Option 4
Existing kong.response.exit/send is altered to attempt to satisfy the supplied accept header, whilst also providing the calling code the option to explicitly state the returned content type. If kong.response.exit were to check for the existence of the content-type header prior to looking at the accept then the OAuth plugin (and any others that require this functionality) could be adjusted to maintain current functionality by calling
return kong.response.exit(401, {
  error = "invalid_token",
  error_description = "The access token is invalid or has expired"
}, {
 ["WWW-Authenticate"] = "...",
 ["Content-Type"] = "application/json"
})

Alternatively the content type could be made an explicit method parameter - perhaps less "magical"?
Not to introduce too much scope creep, but in addition to this, it may be worth reconsidering the current implementation of setting the content type in error_handlers.lua. If I'm not mistaken, this currently ignores the priority rules and so, if the accept header were set to text/html, application/json;q=0.9, */*;q=0.8 then the code would currently return JSON instead of html. In adjusting this, one could also adjust the default to application/json rather than the current text/plain. If the code defaults to application/json, then with this change the only situation I can think of which could be seen as "breaking" is when:

user agents request a non-json response (e.g. text/html)
the plugin wishes to return a specific content type and is not changed to explicitly set the returned content type

In this "breaking" scenario the user will now actually receive what they asked for instead of application/json which the plugin would have returned previously.
On a side note, one side effect (benefit?) of this which I had not considered before is that this functionality would not be limited to error statuses (in comparison to this PR and the other options presented). Thus it could even be used by a plugin that wanted to return a 200 with a "correctly formatted" response.

If you really want to avoiding a breaking change then I'd agree that Option 2 does seem like a fair approach here. Although, given that @bungle correctly mentions that this only really affects HTTP traffic I guess this means that kong.response.error would need to contain some branching logic that ends up calling kong.response.exit/send where plugins may be designed to operate on multiple traffic types (if that's even possible)?
@kikito - is there a particular reason why you changed the table parameter in kong.response.exit to a string in kong.response.error? The table parameter would seem more flexible to me if user's do want to provide additional content. Although perhaps that does complicate the rendering of html content?

Finally, if I may just go back to the goal

The goal: consistent error reporting.

In my response I mentioned "easily overridable rendering of responses". I just want to expand on this slightly to ensure this isn't overlooked. I would really like to ensure that the end user has the ability to override/control the method used to write the response. I currently do this with the code contained in this PR by mounting a custom error_handlers.lua. In this custom version we provide default messages/bodies for the additional statuses (which could easily be done by default as already suggested in this thread). More importantly, we also inject content across all errors. To give you a couple examples of why we do this:

For all content types, we currently inject a request/correlation id into the response. This helps from an observability standpoint as the end user can supply this to our support teams who can then use this to look up the request and see more details about where the error happened
For html content we apply custom branding so that we have consistent looking error pages across both Kong errors and all upstreams.

If I'm not mistaken, this currently ignores the priority rules and so, if the accept header were set to text/html, application/json;q=0.9, /;q=0.8 then the code would currently return JSON instead of html

You are correct, the priority rules are not honoured, it only checks if string starts with something. So it will be served as text/html. But blaa/blaa, application/json;q=0.9, */*;q=0.8 will be served as plain.

is there a particular reason why you changed the table parameter in kong.response.exit to a string in kong.response.error? The table parameter would seem more flexible to me if user's do want to provide additional content. Although perhaps that does complicate the rendering of html content?

Ultimately I think kong.response.error should be able to handle both a string and a table. Candidates for rules:

When the content-type is json:

if msg is a table, return it transformed into json
if msg is a string, convert to the json table { "message": <msg> }

When the content-type is NOT json:

if msg is a string, it will be sent "as is".
if msg is a table, it will be transformed into json prior to sending.

So making the transformation (from table to plain string) will have no impact when content-type is JSON, but will render more nicely in txt/html (it will avoid json-inside-html or json-in-txt).

@hishamhm Can you help here?

I am closing this because we went through an alternative implementation (#5562) . This PR was very influential on getting to that solution and we are very grateful for the feedback and work which went into it. Thanks!


[RELEASE] Release 3.11

Work Plan
Create release 3.11 :
Prior to the release work

[x] slack post advising of upcoming release & linking to issue
[x] advance warning in developer/community call
[ ] final agreement to start branch in team call & identification of outstanding issues
[ ] Agree required updates/versions for additional repos including egeria-ui, egeria-reactui, connectors etc

Branching & Correcting versions

[ ] Create branch
[ ] Reassign any issues not being worked on to the next release
[ ] Update version for master (ie x.y-SNAPSHOT > x.y+1-SNAPSHOT)
[ ] Update version for branch (ie x.y-SNAPSHOT -> x.y)

Final updates to the release

[ ] Ensure any remaining fixes are merged into branch (and vice-versa to master)

Generate a release image for testing

[ ] Start release pipeline manually to generate container image

Updating the React UI (as this is part of the notebook test). Note egeria-ui is out of scope other than inclusion of current release

[ ] Create branch
[ ] Update version in master
[ ] Update version in new branch
[ ] Ensure new container image is available for testing (there is no distinct release pipeline)

Updating the Helm Charts (egeria-charts repo)

[ ] checker correct container images are on docker.io & quay.io (these are built by the 'merge' build of a release)
[ ] update image versions for helm charts (egeria-charts repo) (using -prerelease for chart version)

Final tests

[ ] Check swagger doc renders (no regressions)
[ ] Verify odpi-egeria-lab chart (pods active/ready)
[ ] Verify egeria-base chart (pods active/ready)
[ ] Check notebooks (config, start, data catalog at a minimum)
[ ] Check polymer UI (only possible to check it runs - no demo scenario for more)
[ ] Check React UI (rex, tex, glossary author)
[ ] CTS - graph
[ ] CTS - inmemory

Final Docs

[ ] Update release notes in egeria-docs

Final build and publish

[ ] Run 'release' pipeline on branch to push candidates to oss.sonatype.org
[ ] 'close' staging repo & Validate artifacts ok (number, structure, validations) on oss.sonatype.org
[ ] Create final github releases for egeria (add link to egeria docs)
[ ] Close repo on oss.sonatype.org (once updated) for egeria, release
[ ] Check 'release' repo on oss.sonatype.org has artifacts
[ ] Update final versions of egeria-charts to release ie x.y
[ ] Publish that release is now shipped via slack #egeria-announce
[ ] Additional posts to social media
[ ] Communicate to other repo owners ie for connectors so that they can be rebuilt/shipped as needed

Additional components

ReactUI

[ ] Create final github release

Egeria Dev Projects

[ ] Update project & dependency versions to new release

Get Ready for next release

[ ] Open Release Issue for next release

I propose to branch for release 3.11 on Thu 25 August, for a release ~1 Sep

For our helm charts:
@lpalashevski @sarbull I assume we are staying with egeria-ui 3.2.0 (old) and @davidradl we stick with egeria-react-ui 3.8.0.
The new Jupyter notebook environment will be used cc: @mandy-chessell

As per slack discussion, the release branch is now targeted as the morning of 30 August.
The release should be available early September

Egeria branch and release work now underway

@lpalashevski @davidradl As above, presuming no change in versions for either UI component compared to release 3.10

lab notebooks generally OK
React UI same as previously - bugs, but already reported
Business UI - NOT WORKING (nginx appears to close connection immediately)
CTS - running

CTS clean apart from 1 intermittent issue seen for a few releases with:
                     "unsuccessfulAssertions": [
                            "Unexpected Exception Exception : CTS test repository-entity-reference-copy-lifecycle caught exception EntityNotKnownException from method getEntityDet
ail whilst trying to retrieve an entity of type APISchemaType.  Exception message was : OMRS-REPOSITORY-404-002 The entity identified with guid 772bce12-0e80-4766-b7ef-3432f5b7320
4 passed on the getEntityDetail call is not known to the open metadata repository tut.  Method was invoked with parameters: entityGUID : 772bce12-0e80-4766-b7ef-3432f5b73204"

This is believed to be timing related                         ]

Opened https://github.com/odpi/egeria-charts/issues/187 to track issue with Business UI not loading

Issue was with LoadBalancer. Now tested ok on openshift & rancher using port-forward.


How to run C++ examples

Hi, I honestly can't work out how to run a C++ example. I can run Python ones but I just don't understand how to do the C++ ones. I've compiled them using the official dlib steps using Cmake (ie. I have a file called "build" under "Examples" with two folders called "CMakeFiles" and "dlib_build" together with .vcxproj and .vcxproj.filters file for each .cpp example). Am I supposed to have a .exe file somewhere? I would like to run the dog hipsterizer example, what do I need to supply to the command line? I have put the mmod_dog_hipsterizer.dat file in the "Examples" folder, I then made a file called "dnn_mmod_dog_hipsterizer" and put the relevant .vcxproj, .vcxproj.filters and .cpp file in that. So in the "Examples" folder and supply the following to cmd:
./dnn_mmod_dog_hipsterizer mmod_dog_hipsterizer.dat faces/dogs.jpg
but it doesn't work. I tried without creating the folder with: dnn_mmod_dog_hipsterizer.cpp mmod_dog_hipsterizer.dat faces/dogs.jpg and that just opens the .cpp file in VS.
Please help me :( I've done a bit of Python but nothing in C++ - I'm just wanting to go from the HOG detector to the DNN MMOD one in C++. Thanks for any help, I really appreciate it! I'm running the newest version of dlib (19.22), CMake 3.18.4 and VS 16 2019 installed with C++ tools.

No worries, I worked it out. For anyone wondering, just follow the proper dlib instructions! I didn't have any .exe files and the VS build files were in debug mode and not release for some reason.


Attributeerror: 'torch.device' object has no attribute 'device'

Hi, I was running the code but this problem occurs, here is the complete error message:
Traceback (most recent call last):
File "/media/SSD/user1/QueryDet-PyTorch-main/train_coco.py", line 15, in
launch(
File "/media/SSD/user1/QueryDet-PyTorch-main/detectron2/engine/launch.py", line 82, in launch
main_func(*args)
File "/media/SSD/user1/QueryDet-PyTorch-main/train_tools/coco_train.py", line 158, in start_train
return trainer.train()
File "/media/SSD/user1/QueryDet-PyTorch-main/apex_tools/apex_trainer.py", line 227, in train
self.run_step()
File "/media/SSD/user1/QueryDet-PyTorch-main/apex_tools/apex_trainer.py", line 249, in run_step
loss_dict = self.model(data)
File "/home/user1/.conda/envs/sr/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/media/SSD/user1/QueryDet-PyTorch-main/models/querydet/detector.py", line 165, in forward
return self.train_forward(batched_inputs, just_forward)
File "/media/SSD/user1/QueryDet-PyTorch-main/models/querydet/detector.py", line 187, in train_forward
all_anchors, all_centers = self.anchor_generator(all_features)
File "/home/user1/.conda/envs/sr/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/media/SSD/user1/QueryDet-PyTorch-main/utils/anchor_gen.py", line 30, in forward
anchors_over_all_feature_maps, centers_over_all_feature_maps = self._grid_anchors(grid_sizes)
File "/media/SSD/user1/QueryDet-PyTorch-main/utils/anchor_gen.py", line 20, in _grid_anchors
shift_x, shift_y = _create_grid_offsets(size, stride, self.offset, base_anchors.device)
File "/media/SSD/user1/QueryDet-PyTorch-main/detectron2/modeling/anchor_generator.py", line 43, in _create_grid_offsets
shifts_x = move_device_like(
File "/home/user1/.conda/envs/sr/lib/python3.9/site-packages/torch/jit/_trace.py", line 1118, in wrapper
return fn(*args, **kwargs)
File "/media/SSD/user1/QueryDet-PyTorch-main/detectron2/layers/wrappers.py", line 146, in move_device_like
return src.to(dst.device)
AttributeError: 'torch.device' object has no attribute 'device'
How can I resolve this? Many thanks
I have already tried different version of environments, I used cuda 10.1+ torch 1.8.1 + python 3.7 and this problem still exists.

It seems that you need to use detectron2 v0.2.1

It seems that you need to use detectron2 v0.2.1

Thank you very much! The program can run properly now.
Turns out I need detectron2 v0.2.1 +  fvcore 0.1.1
pip install fvcore==0.1.1.dev200512


devfile validation fails if folder name is not valid

/kind bug
What versions of software are you using?
Operating System:
MacOs
Output of odo version:
odo 2.0.3
How did you run odo exactly?
odo push
Actual behavior
When I run odo push on a folder with devfile. devfile validation fails with the following.
the staticHTML is the name of the folder and I never set a component name.
I think odo is setting the component name from folder name without converting it to be vaid.
❯ odo push

Validation
 ✗  Failed to start component with name staticHTML. Error: Failed to create the component: component name "staticHTML" is not valid, component name should conform the following requirements:
- Contain at most 63 characters
- Contain only lowercase alphanumeric characters or ‘-’
- Start with an alphanumeric character
- End with an alphanumeric character
- Must not contain all numeric values

Expected behavior
validation does not fail
Any logs, error output, etc?

I think odo is setting the component name from folder name without converting it to be vaid.

Yes, that is what is happening here :-(
odo needs to convert the directory name into the always valid component name.
odo needs to do the following  cleanup before using value as a component name:

convert to lowercase
remove all non-alphanumeric characters except -
if it is all numeric values, prepend it with x
remove all leading and trailing non-alphanumeric characters (because of the previous step, this can be only -)

I can take a look at this


Add support to generate nodejs output.

The node grpc plugin currently has a hard coded assumption that the message file
to go with a certain service file is "../foo/foo_pb.js". This is not always the
case, but for now we try to ensure the --js_out argument is set to match what
the grpc plugin expects.

Found this project a long while back through a blog post from namely btw :)

Stick with node. It differentiaties between browser compatible code and a
node just runtime-specifically the c layer.
On Wed, Mar 21, 2018, 10:36 PM sundbp<EMAIL_ADDRESS>wrote:

Found this project a long while back through a blog post from namely btw :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/namely/docker-protoc/pull/51#issuecomment-375159710,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFkGjLkgBIHjBn5ue2KjtWYRYpIbqgmks5tgw40gaJpZM4S2RMc
.

I built and pushed a new namely/protoc-all container image.
Thanks again for the contribution! We really appreciate it 👍

Did you use the 1.9 tag?
On Thu, Mar 22, 2018, 9:06 AM Martin Kess<EMAIL_ADDRESS>wrote:

I built and pushed a new namely/protoc-all container image.
Thanks again for the contribution! We really appreciate it 👍
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/namely/docker-protoc/pull/51#issuecomment-375297979,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFkGnxB5puhygkSmZiwwvaQeHMAAK1Bks5tg6G8gaJpZM4S2RMc
.

Thanks! Much appreciated - I've found it a sane way to develop with protobuf and gRPC.


Updating the creditcoin build guide

Creditcoin now requires that Nightly rust isn't any newer than 2024-02-04.
This is because Creditcoin uses the feature stdsimd which was removed in newer Rust versions.

Since you are working in this repo you can also fix the MegaLinter failures by making the following changes:
actions-rs/toolchain@v1 -> gluwa/toolchain@dev
actions-rs/cargo@v1 ->  gluwa/cargo@dev
see https://github.com/gluwa/creditcoin3/pull/396 and CSUB-1174 for more context.

I grappled for a while with attempting to add a rust-toolchain.toml file.
Docker and a few of the CI checks were intractably unhappy with that. So I'm going with referencing ci/env in building.md instead.


FUSETOOLS2-778 - support Camel K modeline on several lines

one part to cover later is to support diagnostic across the lines.
Currently, it only validates line by line
Given the size of the PR, i think it is better to handle it in another task. No regression, it is just another new enhancement.

one example on second line:

I'm a little confused by the test file camelk-with-duplicated-traits-in-modeline-written-secondline.java since the modeline is only on a single line.

this file is only for the diagnostic test. it doesn't care what are on other lines (another Camel K modeline or not).  For diagnostic, it doesn't cross-check between lines as mentioned in initial description https://github.com/camel-tooling/camel-language-server/pull/497#issue-514733255

Is there another test with the dual dependency approach that you provided in the PR description?

given that there is no cross-line reference anywhere. I wasn't lead to that.
I will modify few tests with that. it will be closer to real-world.


test(weaver/sdk/node): fix flake - InteroperableHelper cryptographic fn

Description

On an unrelated PR (e.g. it didn't change anything related to this job) the unit_test_weaver_node_sdk_local job failed.
I re-executed it and then it worked fine.

Full Error Logs
2024-06-19T13-16-15-weaver-flaky-unit-tests.log
Error Logs Snippet
2024-06-19T13:17:30.4147489Z   52 passing (11s)
2024-06-19T13:17:30.4148156Z   1 failing
2024-06-19T13:17:30.4148459Z
2024-06-19T13:17:30.4151570Z   1) InteroperableHelper
2024-06-19T13:17:30.4152456Z        cryptographic functions
2024-06-19T13:17:30.4153640Z          encrypt and decrypt a message with default 128-bit AES key:
2024-06-19T13:17:30.4155558Z      AssertionError: expected [Function] to not throw an error but 'AssertionError: expected [Function] t…' was thrown
2024-06-19T13:17:30.4159424Z       at Context.<anonymous> (test/InteroperableHelper.js:154:22)
2024-06-19T13:17:30.4160622Z       at processImmediate (node:internal/timers:476:21)
2024-06-19T13:17:30.4161562Z

Acceptance Criteria

Test is consistently passing.

cc: @VRamakrishna @sandeepnRES

Is this task still open?

@Dozie2001 Yes. The caveat: We don't know how to reproduce this.


PX/Px being converted to rem when inside calc()

I need a pixel value to remain a pixel value inside of a calc function. I have made sure that the value is -17.4359PX before the postcss-pxtorem processes. After processing, this is converted to -1.08974rem.
Is there a specific reason by the plugin ignores PX/Px inside of a calc()?
Is there a workaround?

I added a test for the case-sensitivity of px and included calc() in #35. I didn't seem to have the same issue that you are having.

Do you have a pre-processor running on your CSS before it gets to postcss? Maybe something is converting the PX to px.

After some further testing, it appears that the following example causes the issue:
margin: 12px calc(12PX + 2PX)
In this example the 2 upper case pixel values get converted to rems.

Do you happen to be using a pre-processor like Sass or Less? I feel like something is lowercasing the px before it reaches postcss.

@mdmccarley89 Nevermind, you are correct. I think I know the issue too. I'll put out a fix soon.

@mdmccarley89 published<EMAIL_ADDRESS>

Thanks so much Jonathan!


arm-none-eabi toolchain output and test executable

Hi,
I am currently working on integrating unit tests using Ceedling for a NRF52832 system. It uses the arm-none-eabi toolchain which seems to be creating an issue when executing test outputs. After linking the output file, it "runs", displaying the .out file in the text editor, containing completely illegible contents. When the file is closed, the following is displayed in the shell:
ERROR: Test executable "test_util.out" failed.
> Produced no output to $stdout.
> And exited with status: [0] (count of failed tests).
> This is often a symptom of a bad memory access in source or test code.
rake aborted!

Interestingly, i altered the :tools: section of the YAML for the temp_sensor example to match, and encountered the same issue.
My :tools: section of the YAML is:
:tools:
  :test_compiler:
     :executable: arm-none-eabi-gcc              #exists in system search path
     :arguments:
        - -c ${1}
        - -I"$": COLLECTION_PATHS_TEST_TOOLCHAIN_INCLUDE               #expands to -I search paths
        - -I"$": COLLECTION_PATHS_TEST_SUPPORT_SOURCE_INCLUDE_VENDOR   #expands to -I search paths
        - -D$: COLLECTION_DEFINES_TEST_AND_VENDOR  #expands to all -D defined symbols

        - -c ${1}                       #source code input file (Ruby method call param list sub)
        - -o ${2}                       #object file output (Ruby method call param list sub)
        - -I"$": COLLECTION_PATHS_TEST_TOOLCHAIN_INCLUDE               #expands to -I search paths
        - -I"$": COLLECTION_PATHS_TEST_SUPPORT_SOURCE_INCLUDE_VENDOR   #expands to -I search paths
        - -D$: COLLECTION_DEFINES_TEST_AND_VENDOR  #expands to all -D defined symbols
  :test_linker:
     :executable: arm-none-eabi-gcc
     :arguments:
        - --entry=0x23000
        - ${1}               #list of object files to link (Ruby method call param list sub)
        - --specs=nosys.specs
        - -o ${2}            #executable file output (Ruby method call param list sub)

I was hoping I could receive some advice on making my output human readable, preferably in the shell.
Thanks,
Jake

Can we close this?


⚠ Bofrost.fr has degraded performance

In ca3963e, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 942 ms

Resolved: Bofrost.fr performance has improved in c747f53 after 20 minutes.


Add named groups for python

🤔 What's changed?

Expression matching now returns a tuple: the value as before and an optional name if the expression has a name or the regex uses a named capture group.
The format for the Cucumber Expression when specifying name AND type is:
"There are {step_count:int} steps."

Where the part before the colon is the name of the arg, and after is the type we are currently using for Cucumber Expressions.
⚡ What's your motivation?

Python (in particular pytest-bdd) uses other args in the step definitions, such as fixtures and reserved args for "datatable" and "docstring", so just mapping step arg values to step args in the expressions is not reliable or user-friendly.  It is a blocker currently for adopting Cucumber Expressions into the pytest-bdd framework.
🏷 What kind of change is this?

:boom: Breaking change (incompatible changes to the API)

♻ Anything particular you want feedback on?

Approach, public API changes, format of the named args, whether it's acceptable in general!
📋 Checklist:

[x] I agree to respect and uphold the Cucumber Community Code of Conduct
[X] I've changed the behaviour of the code

[ ] I have added/updated tests to cover my changes.

[X] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[X] Users should know about my change

[ ] I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

This text was originally generated from a template, then edited by hand. You can modify the template here.

This is just my first draft where I made sure that everything "works", but I still need to do tests, documentation, etc., if we agree, but I thought it more prudent to share the current approach I am suggesting before doing these things!
Feedback most welcome!


Errors on 2.0.3 with Xcode 9.3

One of my projects is using Swish 2.0.3. I updated Xcode to 9.3 and I started to see a couple errors. It would be great to get a quick fix for Swish 2.0 out if possible. Unfortunately, we're not able to migrate to Swish 3.0 at this time. Here are the errors I'm seeing:
Swish/Source/Models/APIClient.swift:10:108: Struct 'JSONDeserializer' is internal and cannot be referenced from a default argument value

(can't use internal type in default arg)
and
Swish/Source/Protocols/Request.swift:29:21: Missing argument for parameter #1 in call

(needs another() inside .success())
I've forked and branched from what looked like a good point for 2.0: 4c9233c. I don't want to open a PR onto master here -- is there a good branch I could PR with these updates? My changes are here:
https://github.com/gstro/Swish/tree/2.0-fixes . Could there be a 2.x release branch? Would love to have this updated on CocoaPods soon too.

@gstro How are you pulling in Swish? I'm not seeing the .success(()) error locally in 9.3 😕

I used CocoaPods. I just confirmed this issue with

New "Single View App" iOS project
Create a Podfile with Swish 2.0 below:

target 'SwishTest' do
  use_frameworks!
  pod 'Swish', '~> 2.0'
end

Run pod install
Open the .xcworkspace file
Build

This gives me the two errors I mentioned in the first post of this thread (internal JSONDeserializer, and missing () argument). Hope this helps.

Cool, that's what I assumed you were doing but wanted to confirm. Interesting that the missing () error doesn't show up when compiling the project directly in xcode...

@gstro if you have a min to test against gfontenot/2.0-fixes and confirm that it fixes your issues, I'll merge that PR and get a release up asap.

Confirmed fixed! Thanks for that quick turnaround.


Missing small but important logging information when using watch

I had problems locating which file was throwing an error:
Using hugo -w mode and -verboseLog, the following logging appears on log file:
INFO 2017/07/13 14:14:01 Using config file:
INFO 2017/07/13 14:14:01 /var/www/html/hugo/static/ is the only static directory available to sync from
INFO 2017/07/13 14:14:01 syncing static files to /var/www/html/hugo/public/
LOG:   2017/07/13 14:14:01 Started building sites ...
ERROR 2017/07/13 14:14:04 unable to read frontmatter at filepos 364: EOF
HERE HUGO FINALLY CRASH AND IS BEING RESTARTED BY A CRON JOB
INFO 2017/07/13 14:15:14 Using config file:
INFO 2017/07/13 14:15:14 /var/www/html/hugo/static/ is the only static directory available to sync from
INFO 2017/07/13 14:15:14 syncing static files to /var/www/html/hugo/public/
LOG:   2017/07/13 14:15:14 Started building sites ...
ERROR 2017/07/13 14:15:16 unable to read frontmatter at filepos 364: EOF
When I use start manually hugo (without -w mode), I also get the same error but it's finally followed by a very useful information in the console, the file which causes the error ;-)
Started building sites ...
ERROR 2017/07/13 14:31:54 unable to read frontmatter at filepos 364: EOF
Error: Error building site: Errors reading pages: Error: unable to read frontmatter at filepos 364: EOF for actualitedanslereseauboyeratoursle26aout2016-tours-37000-182528.md
HERE HUGO FINALLY CRASH BUT I DONT CARE, I KNOW WHERE TO SEARCH
should be very nice if logging could log the file name even in watch mode.

I haven't noticed, but thanks a lot for the report -- this we should fix.

I'll have a look at this one.

@bep How come this keeps getting pushed back through releases?


Bypass login requirements when downloading from proxy server

Is it possible to relax the login requirements when downloading from the proxy server to make it easier for the sync admin.

I like this idea.
Currently the login credentials aren't saved at all on the tablet so they have to be entered repeatedly for every upload/download. Perhaps a caching mechanism of a few hours could be used to minimize this. Obviously, we don't want to store credentials on the device, but temporarily storing the authentication on the proxy server (maybe for a few hours) would be a reasonable solution if it's possible. This would allow a single login to authenticate all the uploads and downloads without allowing malicious data to be uploaded by tablets that are have been lost and minimizes the number of times the users have to login (ideally no more than twice a day).

This feature has been implemented on the proxy side. The sync logic in the app needs to allow a user to start a sync without using the login screen and only be presented with the login if a 401 is returned.


Inconsistant use of <IP_ADDRESS> and localhost in startup

Vite says
  VITE v3.0.4  ready in 2051 ms

  ➜  Local:   http://<IP_ADDRESS>:3000/
  ➜  Network: use --host to expose
  ➜  Inspect: http://<IP_ADDRESS>:3000/__inspect/

We say
  > Page Routes:
     http://localhost:3000/*404
     http://localhost:3000/:offset
     http://localhost:3000/bookmarks
     http://localhost:3000/

Obviously very minor and in practice has no difference but just a small little usability thing

I'm going to see about if this can just be made much prettier in general


Use "parse_file" in class "ConversationBufferMemory" raise a ValidationError

System Info
Platform:Windows
LangChain:0.0.335
python:3.9.12
Who can help?
@eyurtsev @hwchase17 @hwchase17
Information

[ ] The official example notebooks/scripts
[X] My own modified scripts

Related Components

[ ] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[X] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
Here is my code:
from langchain.memory import ConversationBufferMemory
import langchain.load
ChatMemory = ConversationBufferMemory()
ChatMemory.chat_memory.add_ai_message("Hello")
ChatMemory.chat_memory.add_user_message("HI")
tojson = ChatMemory.json()
with open('E:\memory.json', 'w') as file:
file.write(tojson)
file.close()
ParserChatMemory = ConversationBufferMemory.parse_file('E:\memory.json')
Expected behavior
Regarding the parse_file method in ConversationBufferMemory, there is not much introduction in the document, and I have not found a similar problem description. However, saving Memory into a file/or generating it from a file is a normal requirement, but when I execute parse_file This method throws a "ValidationError", the complete description is as follows:
ValidationError: 1 validation error for ConversationBufferMemory
chat_memory
instance of BaseChatMessageHistory expected (type=type_error.arbitrary_type; expected_arbitrary_type=BaseChatMessageHistory)
If there is any violation of my operation, please tell me, thank you very much

@dosu-bot
Your answer doesn't work

I have a similar error. I implemented a custom chat history. Calling outputs an error.
issubclass(type(history),BaseChatMessageHistory) #output: True

ConversationBufferMemory(chat_memory=history,
                         memory_key='chat_history',
                         return_messages=True)

gives this error:
ValidationError: 1 validation error for ConversationBufferMemory
chat_memory
  instance of BaseChatMessageHistory expected (type=type_error.arbitrary_type; expected_arbitrary_type=BaseChatMessageHistory)

I also have this problem. I'm trying to use
history: BaseChatMessageHistory = StreamlitChatMessageHistory(key="messages")
with
memory: ConversationBufferMemory = ConversationBufferMemory(memory_key="chat_history",
                                                            return_messages=True,
                                                            chat_memory=history)

and get the same error:
This error was raised: 1 validation error for ConversationBufferMemory
chat_memory
  instance of BaseChatMessageHistory expected (type=type_error.arbitrary_type; expected_arbitrary_type=BaseChatMessageHistory)


Private variables explicit typing fix

Fixed: using a private variable with explicit type leads to an error:

Not sure if it's a correct fix, but it seems to work fine.

Technically works, but giving Ace empty-named auto-completion items is undefined behaviour so it's best to just check if an item exists - lest someone comes up next time I update Ace with an auto-completion menu full of mystery items.


upgrade Graphite to 1.0.2

Tested on VM cluster.
Currently testing on physical cluster...
Please don't merge.

Tested on DNJ2-JR.

Due to https://github.com/graphite-project/graphite-web/issues/2012
Need to replace webapp/graphite/finders/init.py with the following file
https://raw.githubusercontent.com/leochen4891/graphite-web/bfc5bd0484c1084ee41b0329dd61a9160e543a01/webapp/graphite/finders/__init__.py

Before and after the PR was applied and services restarted around 23:25
We can see afterwards the unstable graphite-to-zabbix queries started to be stable.

@vt0r thanks for the review, PR updated.

(To be backported to 3.0)


CRUD tasks for pod operations

Create tasks: ListPods, DeletePod, GetPod, and CreatePod.

Task ListPods was done as part #16

Task DeletePod was done as part of #17

Task GetPod was done as part of #18

Task CreatePod was done as part of #20


[charts/gateway] Pmtagger tolerations

Description of the change
add tolerations to pmtagger
Benefits
enable assigning pmtagger pod to designated node pool with taints
Drawbacks
none
Applicable issues

fixes #

Additional information
Checklist

[] Chart version bumped in Chart.yaml according to semver.
[] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [charts/gateway])
[] If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files

@Gazza7205 i was intending to reuse the same nodeSeletor and tolerations values from gateway; that's why there is no additional values file update.
please confirm if reuse is ok or if you prefer separate values?
e.g. values.tolerations applies to both gateway and pmtagger, or
values.tolerations - gateway only, then values.pmtagger.tolerations

@Gazza7205 i was intending to reuse the same nodeSeletor and tolerations values from gateway; that's why there is no additional values file update. please confirm if reuse is ok or if you prefer separate values? e.g. values.tolerations applies to both gateway and pmtagger, or values.tolerations - gateway only, then values.pmtagger.tolerations

I think separate nodeSelector/tolerations given it's a separate optional deployment make sense.
#184 has that update - if you're happy to proceed I'll merge it into this branch.

merged #184 and added another fix in the if conditions.
please do a final review and merge this pr if ok


How to specify custom announce urls?

This doesn't work for me...I'm probably not specifying the announce urls properly but I don't really know what they should be.
    const client = new window.WebTorrent()

    client.add(this.torrent.magnet, {
      announce: [
        'http://router.bittorrent.com:6881',
        'http://dht.transmissionbt.com:6881'
      ]
    }, (torrent) => {
      console.log(torrent)
      const file = torrent.files[0]
      console.log(file)
      file.appendTo('body')
    })

Using browser version from CDN.

Why do you say it doesn't work?
Is this in the browser or Node?
Do you get any errors?

I'm doing it in browser, via cdn js
callback never fires even when using example torrent from http://webtorrent.io
    const magnet = 'magnet:?xt=urn:btih:6a9759bffd5c0af65319979fb7832189f4f3c35d&dn=sintel.mp4'
    console.log('play!', magnet)
    const client = new window.WebTorrent()

    client.add(magnet, {
      announce: [
        'wss://tracker.openwebtorrent.com',
        'wss://tracker.btorrent.xyz'
      ]
    }, function (torrent) {
      console.log(torrent)
      torrent.on('download', () => {
        console.log('downloadSpeed', torrent.downloadSpeed)
        console.log('timeRemaining', torrent.timeRemaining)
      })

      torrent.on('upload', () => {
        console.log('uploadSpeed', torrent.uploadSpeed)
      })

      console.log(torrent)
      const file = torrent.files[0]
      console.log(file)
      file.appendTo('main')
    })

    const magnet = 'magnet:?xt=urn:btih:6a9759bffd5c0af65319979fb7832189f4f3c35d&dn=sintel.mp4'
    console.log('play!', magnet)
    const client = new window.WebTorrent()

    client.add(magnet, {
      announce: [
        'wss://tracker.openwebtorrent.com',
        'wss://tracker.btorrent.xyz'
      ]
    }, function (torrent) {
      // this never fires
      console.log(torrent)
      torrent.on('download', () => {
        console.log('downloadSpeed', torrent.downloadSpeed)
        console.log('timeRemaining', torrent.timeRemaining)
      })

      torrent.on('upload', () => {
        console.log('uploadSpeed', torrent.uploadSpeed)
      })

      console.log(torrent)
      const file = torrent.files[0]
      console.log(file)
      file.appendTo('main')
    })

If you find out any info about why it took so long, please share.

The only difference I can see is I'm using vue.js -- perhaps that is causing severe slowdown?
I'm using the same bootstrap socket servers you are. So its very odd. I will do a simple test w/o vue.js and see if that's the issue.

It could be because webtorrent.io is using a web seed as a fallback. Try adding this to your magnet link:
&ws=https%3A%2F%2Fwebtorrent.io%2Ftorrents%2Fsintel-1024-surround.mp4

I don't know. I just tried again and it still never loads although it does start to download but does not play right away. I'm guessing it has to wait for the entire file to download for some reason.
<!doctype html>

Play

	Magnet URL:
	<input type=text id=magnet name=magnet>
	<button onclick=play()>play</button>

magnet:?xt=urn:btih:6c1fe48331262be9e257a5998e7b9c1e558abc98

magnet:?xt=urn:btih:6a9759bffd5c0af65319979fb7832189f4f3c35d&dn=sintel.mp4

magnet:?xt=urn:btih:6a9759bffd5c0af65319979fb7832189f4f3c35d&dn=sintel.mp4&ws=https%3A%2F%2Fwebtorrent.io%2Ftorrents%2Fsintel-1024-surround.mp4

Above is a simple test which rules out vue.js being my problem. I tried the 3rd url (with ws fallback) and it still seems to not play until the entire file is downloaded (i did not wait that long).
If I do webtorrent 'magnet:?xt=urn:btih:6a9759bffd5c0af65319979fb7832189f4f3c35d&dn=sintel.mp4' --vlc it starts playing in VLC immediately and it plays on webtorrent.io immediately.
The above test.html seems to be missing some options perhaps? I could not tell by looking at webtorrent.io source what options (if any) you are passing to client.add()

I did not see this error with console all showing. but when I clicked on errors tab I can see there are some errors:
Not allowed to load local resource: blob:null/7f22f81e-4a71-49b1-ae03-17520713fa35
webtorrent.min.js:6 Uncaught (in promise) DOMException: The element has no supported sources.
a @ webtorrent.min.js:6
webtorrent.min.js:6 Uncaught (in promise) DOMException: The element has no supported sources.

Ahh, are you running this page with a file:// url? That will block Blob URLs for security reasons (which I do not understand). That prevents Mediasource streaming from working.

Yeah. I realized that right away. I am using http-server from npm and it does load the movie (sometimes). It is really inconsistent, flaky and slow. After around 10 tries it loaded.
Like i said cli interface starts playing right away in VLC. I even cloned the repo and built the debug version to make sure I have the latest.
I'm curious if you want that test and paste in the magnet does it work consistently for you?
The webtorrent.io site works fine and so does instant.io but not when web server is running locally.

Only diff i could find is that you're adding this tracker option with ice servers. What is that?
var client = window.client = new WebTorrent({
  tracker: {
    rtcConfig: rtcConfig
  }
})
client.on('warning', onWarning)
client.on('error', onError)

torrent = client.add(TORRENT, onTorrent)
graph.add({ id: 'You', name: 'You', me: true })

rtcConfig (ice servers)
{
    "iceServers": [{
        "urls": "stun:<IP_ADDRESS>"
    }, {
        "username": "xxx",
        "credential": "xxx",
        "urls": "turn:global.turn.twilio.com:3478?transport=udp"
    }, {
        "username": "xxx",
        "credential": "xxx",
        "urls": "turn:global.turn.twilio.com:3478?transport=tcp"
    }, {
        "username": "xxxx",
        "credential": "xxx",
        "urls": "turn:global.turn.twilio.com:443?transport=tcp"
    }]
}

When I tried adding this your demo movie plays right away for me. But other magnet urls I try still suffer from same problem where downloading never starts.
What are these ice servers used for and where can I read more about setting one up?

Sounds like you're on a network with a restrictive firewall or NAT. This makes it harder for peers to connect to you. Those "ice servers" are also known as TURN servers and they're a way to help WebRTC connections succeed even when there's a firewall or NAT that is preventing the direct P2P connection from working.
You can make an account with Twilio and sign up for this service (https://www.twilio.com/stun-turn) and they'll run the server for you. That's what I currently do. You can also try to install a TURN server yourself, but I hear it's tricky. If you include these in the rtcConfig option, then webtorrent will include them in the RTCPeerConnection (webrtc constructor) option, so the WebRTC connections are more likely to succeed.
TURN servers are only used as a fallback, when P2P connections fail. TURN is essentially a central server.


Fixed Login

Description
I have fixed the login problem in the website now the user can be easily loging
Fixes #1018
Replace issue_no with the issue number which is fixed in this PR
Screenshots
https://github.com/user-attachments/assets/d457733d-6352-48e2-b342-f24693fdcac4
Checklist

[ ] Tests have been added or updated to cover the changes
[ ] Documentation has been updated to reflect the changes
[ ] Code follows the established coding style guidelines
[ ] All tests are passing

@thestarsahil  Sir i have fixed the login problem of the website

Well Done  @Ayushmaanagarwal1211
Kudos !

Thank you sir

We have to need that data from user end
So need that part user.database
 localStorage.setItem("userUid", userData.id);

We have to need that data from user end So need that part user.database
 localStorage.setItem("userUid", userData.id);

Sir i am only setting the is

We have to need that data from user end So need that part user.database
 localStorage.setItem("userUid", userData.id);

sir for the signing with email and pass the code taking data from localstorage  here localStorage.getItem(userUid)

And if user already logged in so i am just storing that uid because it is getting undefined so we need to store userUid in the localstorage

We have to need that data from user end So need that part user.database
 localStorage.setItem("userUid", userData.id);

Ok sir i am finding another way

@thestarsahil  Sir is the login is fixed now can you pelase check again actually in my laptop i am still unable for login


Document what happens if .listen() isn't called before .join()

I was going through the kappa workshop and noticed that the example code didn't use .listen() and was wondering why this wasn't needed.

oh good point @ralphtheninja . I think it's because the workshop was intended to be done locally on your computer (two terminals) via mdns -- perhaps no listen is needed for that...


fix so that dev on linux doesn't rebuild entire project

Description
On linux currently, debug builds rebuilds everything due to the contents of pumpkin/build.rs

Testing
Tested so that the issue no longer occurs.

Checklist
Things need to be done before this Pull Request can be merged.

[x] Code is well-formatted and adheres to project style guidelines: cargo fmt
[x] Code does not produce any clippy warnings cargo clippy

I just found out, that tauri-winres uses embed-resource instead of rc.exe or windres.exe and ar.exe
Switching to it will probably speed up adding the icon and metadata. It should also make Cross-compiling easier again.
But I think this is something for another PR :D

LGTM.
Thanks @Bryntet 👍


Improve createInput types and behavior

I've been thinking about this as I was writing the docs and I've realized that createInput should also allow for "void" inputs... So, I think that this is the behavior that I would like to have on createInput. @voliva thoughts?

but it's something that the consumer can add when needed

In fact, it's something that will get automatically added later on when they connect the observable :slightly_smiling_face:


[BACKLOG-3047] - SAP HANA bulk loader step: During selection table an…

…d schema, popup menu for schema should not exist
@kcruzada please review

@kcruzada please review

@brosander maybe you can take a look?

@kcruzada @brosander please review this


Delete yarn.lock

Won't run outside of Uber. Refers to Uber internal dependencies. App builds fine without the lock file.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Cleanups, typings fixes, documentation improvements and tsc lint fixed

Cleaned up redundant code, fixed some typings, implemented better documentation and fixed all the tsc lint issues.

hehe 69 lol

🤔

Nice pull request ID

I don't see why you have modify emoji code before modify channel or anything

I don't see why you have modify emoji code before modify channel or anything

I didn't make that method so i just formatted it, not changed its position


[Linux] Run only one GLib main event loop

Problem
When Linux platform uses WiFi (wpa_supplicant) and BLE (BlueZ) it runs one GLib main event loop per remote D-Bus service (one for wpa_supplicant and one for BlueZ). It is possible to handle all D-Bus related processing in one event loop - it's not required to start new thread for every D-Bus connection (D-Bus socket messages are handled in only one context any way - D-Bus connection is shared). Also, new WiFi address changer thread is started every time the PlatformManagerImpl::_InitChipStack() is called, but previous one is not terminated when calling PlatformManagerImpl::_Shutdown() - thread leakage can be seen when running ./tests/TestPlatformMgr test.
Changes

run only one GLib main event loop per Matter SDK
stop GLib main event loop thread when calling PlatformManagerImpl::_Shutdown()
added workaround for TSAN false positive when initializing CHIP stack (fix related to #14710)
run WiFi IP address change listener in GLib main loop
remove unused functions/defines

Testing
Tested locally with chip-tool and lighting-app.
CI should also check correctness of this PR.

From the history in MainLoop.cpp, it was added for python support.

OK, thanks for info. I'll check that.

Problem
When Linux platform uses WiFi (wpa_supplicant) and BLE (BlueZ) it runs one GLib main event loop per remote D-Bus service (one for wpa_supplicant and one for BlueZ). It is possible to handle all D-Bus related processing in one event loop - it's not required to start new thread for every D-Bus connection (D-Bus socket messages are handled in only one context any way - D-Bus connection is shared). Also, new WiFi address changer thread is started every time the PlatformManagerImpl::_InitChipStack() is called, but previous one is not terminated when calling PlatformManagerImpl::_Shutdown() - thread leakage can be seen when running ./tests/TestPlatformMgr test.

@Arkq ,
I suspect this fixes https://github.com/project-chip/connectedhomeip/issues/9214.  Can you confirm?

@msandstedt It will definitely "fix" that issue, because the MainLoop::EnsureStarted() is gone :D
Right now there will be only one thread started and it's joined in the PlatformManagerImpl::_Shutdown() so there should be no leakage (as long as _Shutdown() will be called before calling _InitChipStack() again, but I assume that calling _InitChipStack() twice or more should be treated as programmer error).

Yes, such pattern is possible. Twice or trice in a row I should say :)

If using glib main loop, can't initChipStack in GUI application, such as Qt/Gtk

@yzm157 what do you mean "can't initChipStack in GUI application"? There is a deadlock, segfault, etc. Do you got any logs?

@yzm157 what do you mean "can't initChipStack in GUI application"? There is a deadlock, segfault, etc. Do you got any logs?

I created an application using pyqt5,
failed to exit after calling chip.native.Init(0), it seems to be deadlocked.
This issue was not found on the v1.0-branch branch

Can you attach to deadlocked process with gdb and dump backtraces of all threads gdb -p <PID> -ex 'thread apply all bt' ?

@arkq
Looks like it's caused by mutex lock, could removing the lock cause other problems?
CHIP_ERROR PlatformManagerImpl::_InitChipStack()
{
#if CHIP_DEVICE_CONFIG_WITH_GLIB_MAIN_LOOP

    mGLibMainLoop       = g_main_loop_new(nullptr, FALSE);
    mGLibMainLoopThread = g_thread_new("gmain-matter", GLibMainLoopThread, mGLibMainLoop);

//    {
//        std::unique_lock<std::mutex> lock(mGLibMainLoopCallbackIndirectionMutex);
//        CallbackIndirection startedInd([](void *) { return G_SOURCE_REMOVE; }, nullptr);
//        g_idle_add(G_SOURCE_FUNC(&CallbackIndirection::Callback), &startedInd);
//        startedInd.Wait(lock);
//    }

#endif

#if CHIP_DEVICE_CONFIG_ENABLE_WIFI
    ReturnErrorOnFailure(RunWiFiIPChangeListener());
#endif

    // Initialize the configuration system.
    ReturnErrorOnFailure(Internal::PosixConfig::Init());

    // Call _InitChipStack() on the generic implementation base class
    // to finish the initialization process.
    ReturnErrorOnFailure(Internal::GenericPlatformManagerImpl_POSIX<PlatformManagerImpl>::_InitChipStack());

    // Now set up our device instance info provider.  We couldn't do that
    // earlier, because the generic implementation sets a generic one.
    SetDeviceInstanceInfoProvider(&DeviceInstanceInfoProviderMgrImpl());

    mStartTime = System::SystemClock().GetMonotonicTimestamp();

    return CHIP_NO_ERROR;
}

Yes, however, this block of code is more or less required. Right now I've got some other important work to do, but I'll try to investigate this issue tomorrow. Sorry for inconvenience.
One thing you can check is whether the [](void *) { return G_SOURCE_REMOVE; } is executed, and if yes, on which thread - simply add ChipLogError into that lambda.

One thing you can check is whether the [](void *) { return G_SOURCE_REMOVE; } is executed, and if yes, on which thread - simply add ChipLogError into that lambda.

No, not executed


Where is the type of an config argument used?

Consider this excerpt from train.py:
config = Configuration()

# training loop arguments
# (...)
config.add_argument('initial_variables', list, required=False, default=None)

Now, I'd like to fix the type annotation on this to be coherent with the training_loop function type annotation. I could not find any place in the code, where this argument is checked. So my question is this. I've tested that I can do this (and already have done it in the PR that fixes variable initialization):
config.add_argument('initial_variables', Union[List[str], str],
                    required=False, default=None)

If there is none, should we implement some configuration checking mechanism which would be based on typing module annotations?

I don't think we need this annotations any more. They are (I hope it's still there) checked by isinstance which, however, can't check the types from typing properly. The arguments of training_loop are later checked by typeguard (aren't they?), so I believe there is no need to keep this coarse type checking.

I don't think they are checked, because the Union[List[str], str] type went through with no problem. but I agree we don't need this if the checking is done in training loop.


[Sema/CSApply] Make sure that the member type references created for a type(of: x).A expression are visible to the SourceEntityWalker

For code like
  _ = type(of: x).A.self

the A type reference is written explicitely by the user, but the AST created using TypeExpr::createImplicitHack is hiding such a reference,
making the reference invisible to semantic functionality like 'rename'.
rdar://56885871

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - d8283a9ebe8c2e7cb1b8a7d8e745c25106878cc0

@swift-ci test linux platform

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - d8283a9ebe8c2e7cb1b8a7d8e745c25106878cc0

Build failed
Swift Test OS X Platform
Git Sha - d8283a9ebe8c2e7cb1b8a7d8e745c25106878cc0

@swift-ci test linux platform

@slavapestov Since you have approved - why is it okay to set a type in the cache different from what is expected by TypeExpr, metatype vs. its instance type?


SGX v4x updates

Closes: #487

@ipuustin @rojkov ready for "official" review.

Codecov Report

Merging #507 (817120b) into master (dea64f3) will increase coverage by 0.08%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #507      +/-   ##
==========================================
+ Coverage   56.70%   56.79%   +0.08%
==========================================
  Files          30       30
  Lines        2028     2032       +4
==========================================
+ Hits         1150     1154       +4
  Misses        807      807
  Partials       71       71

Impacted Files
Coverage Δ

cmd/sgx_plugin/sgx_plugin.go
76.00% <100.00%> (+2.08%)
:arrow_up:

Continue to review full report at Codecov.

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


Refactor ByteBuf release method

Fixes #19350

Master Issue: #xyz

PIP: #xyz

Motivation

Modifications

Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

Thanks for your contribution.
This topic is still under discussion in the community. I am setting 'request changes' now because I am not sure that this is needed and/or it is the right way to go

@eolivelli ok, already a brother reminded me，is that asking me to close this pr? Or wait for the outcome of the discussion before making a decision.

Closing this since using safeRelease would hide real issues.


Real Debrid invalid token while accessing content

Have tried both ways api and authorizing. While trying to access content it says invalid token. The api is correct as I use the same for others and it works fine there.

Hi @rijoymanghat are you still facing the error?

@mhdzumair thanks much for checking back and sorry to not report back. I tried what you said and this time it worked fine. Thanks again !


Add methods and test to KE2CTMC

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 40.251%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5834

Relevant Lines:
14494

💛  - Coveralls


Nuxt with multiple websites. Slow development because of compiling.

Version : Up-to-date version. 2.14.6 (Nuxt)
What I am expecting : Faster development with lots of pages, and components.
What is actually happeening:
I am using Nuxt to run multiple websites with one server. Not sure why no one mentions a big app built by one Nuxt server, but I have 100+ components  200+ pages. Components and pages include logos, SVGs, editors (Qulli & Code mirror), custom helpers, admin pages, and etc... I may, and will add more to this pile of assets as I am willing to open another website on this Nuxt app.
With all those resources, I have a 20mb+ vendor script that loads on my dev server. Not to mention the compile is slow, but the load time is slow too. The initial 'run dev' takes about 40s /client & 5s /server to compile the files, but when you save the code, and the hot reloads runs it takes 3-4s for client, and 1-2s for server.( I tested a basic .vue page without anything in template.) I did some tunings to reduce the vender script, and the size reduced to 7mb, but the hot reload compile is still slow (babel-loader seems to take long during the hot reload compile).
I am not exactly sure if it was the same thing when I started Nuxt, and added the first page to the app, but I remember it was fairly slow compared to Vue cli. Is this expected? Would there be anything I can do to reduce the time, so I can develop as fast as it allows?
Thanks for reading!
Just so you know I have no issues on the production build, and I am really happy with it. Keep up the good work! :)

Maybe this is not a bug. I am closing this issue as it looks like Nuxt compiles at the almost equivalent speed even on the initial state of the project. I guess it's an expected behavior with all these modules built in Nuxt, specifially Nuxt SSR, but I heard a bit more about Vue Vite that accelerates the development speed I am not sure if this is a thing now for Nuxt at the current level of development. I will definitely continue using Nuxt. Thanks anyways for the hard work.


"Add this filter" button links to AdBlock Plus, not uBlock Origin

If I have AdBlock Plus or AdBlock installed, it adds the filter for those. If I don't, it does nothing. Is there a way to do a magic link for uBlock Origin, or does it require manual setup?

Hi!
In my opinion, one should not use AdBlock or AdBlock Plus. These projets are receiving money from advertisements companies to allow some ads.
Moreover, AdBlock doesn't support strict website blocking, and only blocks secondary resources. That's why this filter is not compatible with AdBlock.
I won't make this filter more compatible with Adblock. However cosmetic filters on search engine results might work with AdBlock, but I didn't checked.
You can install uBlock here : https://github.com/gorhill/uBlock and then use any filter from this projet.

@quenhus, I agree, I also prefer uBlock Origin. The links in the README should therefore be updated to be uBlock Origin links, not AdBlock Plus.

To create filter subscriptions in uBO you have two options: with ubo:// protocol or with https://subscribe.adblockplus.org (see https://github.com/gorhill/uBlock/blob/1ff3878a4920e31791547238e3e879a32357914f/src/js/scriptlets/subscriber.js#L58)
On Github, you can't create link with ubo://, so I use the second method with https://subscribe.adblockplus.org

I see, thank you!


doc: Replace version with latest for jobserver link

What does this PR try to resolve?
I prefer the  link with latest,  it will always jump to the latest version link for crate.
There is a bot called renovate to update the version for crate, So it's ok to use latest link.
How should we test and review this PR?
Additional information

:pushpin: Commit 41f7dc2b353f5fa07c99d610cf41379b20d59c8a has been approved by epage
It is now in the queue for this repository.

:hourglass: Testing commit 41f7dc2b353f5fa07c99d610cf41379b20d59c8a with merge cf8d1ae4a54de4a23de723c2628fdfefb5a32673...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing cf8d1ae4a54de4a23de723c2628fdfefb5a32673 to master...


[backport]: from 2.6 to 2.7  (#173)

fix(trustyai): prometheus rules for probe
update(trusty): prometheus to use job instead of instance name for record rules

this is missed to get into main before 2.7 branch out


JStorm-runner: Remove unnecessary WARN log which might case confusion, when translating composite PTransform

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

@peihe
The WARN log here might cause confusion for user.
If the transform can not be translated finally, an exception will be thrown when translating primitive transform. So I don't think we need to print any WARN log when translating composite transform.

Changes Unknown when pulling 03cc311cfbabd92390d7a848a135b59d9d80530c on bastiliu:jstorm-runner into ** on apache:jstorm-runner**.


[test] Fix the flaky browser tests

Fixed all the issues reported by vitest during test runs:

Switched to ESM build
Replaced v8 coverage engine to Istanbul. This solves the dependency optimization warning and makes the browser coverage report more correct

Also updated vitest and related packages to the latest version.

All the warnings are gone and I haven't seen any issues with the tests in a while. Let's merge this and see if it helps for good.

As the test coverage is now calculated differently (using istanbul instead of v8), the codecov/project failure is expected.


what the point of "> *"?

Just want to know

$breakpoint: (
  xl : "",
  lg : "(max-width: 1024px)",
  md : "(max-width: 768px)",
  sm : "(max-width: 667px)"
);

Is that what you asked ?

I'm talking about that
 .wrap > * {   display: inline-block;   }
Maybe I just don't know something about this CSS feature, but I didn't see any reson to use this. Can you explain or just post a link to some article?

Sorry for the late response.
This col is a feature. "float: left;" is used instead. It is required for responsive.
Please check through a compiled view.
http://flexible.gs/learn/wrap/?framework=bem#wrap-bem (normal wrap)
http://flexible.gs/learn/table/?framework=bem#table-bem (table wrap)
http://flexible.gs/learn/flexbox/?framework=bem#flexbox-bem (flexbox wrap)

Thank you for the response. It seems clearly now.


Bruno/quadbox refactor

It might be better to get inside this branch and check it in the IDE
Big PR since it has the quadbox/filterbox/filterswitchbox refactor.
#7403

seeing this as well

also dropdown should be hidden when search is on

also this market is missing my unsigned orders alert for some reason

can we add market counts here

favorites have an arrow that doesn't do anything

toggling is very broken in portfolio
looks like this:

then when I click the top quad expand it becomes this:

so there is no way to even out the space

this is broken as well. shows in reporting as open


Change prompt to user-like prompt

The current prompt in the terminal is root@localhost:~/tutorial#
Would it be possible to change this prompt to a more user-like prompt?

replace # by $
change user from root to robert, alice or bob...

Changing the login user might be the ultimate solution. It will also ensure the starting directory is /home/robert/tutorial instead of /root/tutorial that is not realistic.

Also changing localhost to sandbox could be nice ;-)

Good idea, I wonder if it would be too slow to create creating custom users with useradd at runtime.
Changing localhost to sandbox is definitely doable :)
For the image issue mentioned in https://github.com/IFB-ElixirFr/sandboxbioscenarios/issues/21, I would recommend updating <img> to <Image>, I just pushed this change: https://github.com/sandbox-bio/sandbox.bio/commit/3de2d966cc05c7cf816f9949254f5e66c4b939dd. This makes the image larger and you can click on it to zoom it, as you can see at https://sandbox.bio/tutorials/ifb-linux-basics-2/1.

To change the prompt, you can always just type:
PS1="$ "    # or use whatever your favorite prompt is.
Not sure about the login user setup and whether a file is retained between sessions to store a change more permanently.


Include page libraries in testing harness

Q
A

Bug fix?
[x]

New feature?
[ ]

New sample?
[ ]

Related issues?
partially #475

What's in this Pull Request?
To help see this issue in the test harness, be sure that the 'Site Pages' library is shown as an option

@HiltonGiesenow - could you please resolve the conflicts?
Thanks!

Of course, apologies for that, didn't see that it had happened.


Change Chat Button label in EntryWidget

What was solved?
According to design, chat button label needs to be just "Chat"
Release notes:

[ ] Feature
[X] Ignore
[ ] Release notes (Is it clear from the description here?)
[ ] Migration guide (If changes are needed for integrator already using the SDK - what needs to be communicated? Add underneath please)

Additional info:

[ ] Is the feature sufficiently tested? All tests fixed? Necessary unit, acceptance, snapshots added? Check that at least new public classes & methods are covered with unit tests
[ ] Did you add logging beneficial for troubleshooting of customer issues?
[ ] Did you add new logging? We would like the logging between platforms to be similar. Refer to Logging from iOS SDKs → Things to consider for newly added logs in Confluence for more information.

Screenshots:

Thank you @EgorovEI  and @igorkravchenko for pointing those issues out. Issues have been fixed a2ab2ea


[tracking]  Create results for clusters that are part of different organizations

https://github.com/RedHatInsights/insights-results-aggregator-mock/issues/84

Implemented in https://github.com/RedHatInsights/insights-results-aggregator-mock/pull/164


Set DefaultSocketConfig with socket timeout

Currently we use only RequestConfig, which is applied
after the connection is establish. However in certain
situations (i.e. when connected throughout proxy)
connecting include making requests, in such situations
defaultSocketConfig on ConnectionManager is used.
Fixes #335

Coverage decreased (-0.05%) to 81.649% when pulling 2b8a884488eb5afd91f88163508a9b8f0542bb46 on so-timeout into 6b055e0175c27ae7e03fc1e32c3885ffb7462bf5 on 2.0.0-RC.


Many CSI sequences are ignored (discarded) in a prompt

What happened, and what did you expect to happen?
We know that Elvish parses CSI sequences in a prompt into Text objects instead of writing raw output. It's cool, though introducing a defect. There are many CSI sequences (e.g., a \x1b[21m sequence that typically means disabling bold intensity text style on several terminals) being ignored (discarded) during the parsing via ui.ParseSGREscapedText. However, prompt engines like Oh My Posh, depend on utilizing these control sequences to construct flexible and awesome prompts. The drawback leads to incomplete or unexpected styled text rendered on a terminal.
Output of "elvish -version"
0.21.0+official
Code of Conduct

[X] I agree to follow Elvish's Code of Conduct.

FWIW, the relevant code is ui.StylingFromSGR that is invoked by ui.ParseSGREscapedText
Notice that quite a few of the SGR parameters documented at Wikipedia ANSI SGR parameters, including 21, are not handled by that function. Some of the known SGR parameters can be ignored because they are unlikely to ever be relevant for Elvish; e.g., 20, 26, 50, etc. It's also not clear how to support some parameters, such as 11 thru 19 which select an alternative font, but it seems unlikely those SGR parameters need to be supported by Elvish.
SGR parameter 21 (the focus of this issue) is interesting in that its official meaning (double-underline) is different from its de-facto meaning (disable bold intensity). But there is a more general issue since none of the negative SGR parameters are currently supported. For example, 22 (not bold or faint intensity), 23 (not italic), 24 (not underlined), etc. are also not currently supported by Elvish. But it should be straightforward to enhance ui.StylingFromSGR to support the negative parameters since the core Elvish text styling code supports the concept. See https://github.com/elves/elvish/blob/ce19c91dee982d7b6413e8f2ddd4347df7a9d2db/pkg/ui/styling.go#L91-L96
Here is an example:
> put (styled b bold) (styled (styled x bold red) no-bold)
▶ (ui:text (ui:text-segment b &bold=$true))
▶ (ui:text (ui:text-segment x &fg-color=red))

Someone just needs to write the code and add appropriate unit tests. It might also be useful if a command similar to styled was added that allows Elvish programs to explicitly convert strings containing SGR sequences to styled sequences. If nothing else that would make interactive testing easier of how SGR sequences are converted implicitly by the Elvish prompt code.


Replace lists for sets when contains is required

Found some places where we are calling .contains() on list of items which can be optimized to use sets instead. I assumed that order is not needed, let me know if there are areas that order is important and can update to a linked hashset

IIRC there may be some tests that can be flaky if ordered collections aren't used. But if you aren't seeing tests failures after a number of runs then that isn't an issue here.

Order is important im some cases but I don't know all the sports. Also the lists should be mostly small in some of the cases.


[question] Why all node modules don't have x86-64?

Only have i686-linux, aarch64-linux, aarch64-darwin. Like https://search.nixos.org/packages?channel=unstable&from=0&size=50&sort=relevance&type=packages&query=prettier

Is the plan to close 946 and re-open this one?

Somd packages still miss: https://search.nixos.org/packages?channel=22.05&show=gdu&from=0&size=50&sort=relevance&type=packages&query=gdu


Freeciv: enable on darwin

This should get the GTK client of FreeCiv working at least. Not sure how to get the SDL one though.

Success on x86_64-linux (full log)
Attempted: freeciv, gtk2
Partial log (click to expand)
shrinking /nix/store/s932v9j19gf8wjbk63l2zy0rwcznfmi4-freeciv-2.5.11/bin/freeciv-server
shrinking /nix/store/s932v9j19gf8wjbk63l2zy0rwcznfmi4-freeciv-2.5.11/bin/freeciv-manual
shrinking /nix/store/s932v9j19gf8wjbk63l2zy0rwcznfmi4-freeciv-2.5.11/bin/freeciv-mp-cli
shrinking /nix/store/s932v9j19gf8wjbk63l2zy0rwcznfmi4-freeciv-2.5.11/lib/libfreeciv.so.0.0.0
shrinking /nix/store/s932v9j19gf8wjbk63l2zy0rwcznfmi4-freeciv-2.5.11/lib/libfreeciv-srv.so.0.0.0
gzipping man pages under /nix/store/s932v9j19gf8wjbk63l2zy0rwcznfmi4-freeciv-2.5.11/share/man/
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/s932v9j19gf8wjbk63l2zy0rwcznfmi4-freeciv-2.5.11/lib  /nix/store/s932v9j19gf8wjbk63l2zy0rwcznfmi4-freeciv-2.5.11/bin
patching script interpreter paths in /nix/store/s932v9j19gf8wjbk63l2zy0rwcznfmi4-freeciv-2.5.11
checking for references to /build in /nix/store/s932v9j19gf8wjbk63l2zy0rwcznfmi4-freeciv-2.5.11...

Success on x86_64-linux (full log)
Attempted: autojump, enet, freeciv, gtk2, nvidia-texture-tools, sfml, spidermonkey_38
The following builds were skipped because they don't evaluate on x86_64-linux: wireguard-go
Partial log (click to expand)
shrinking /nix/store/abym5ffw8k8npwdbyp5s1rrrzi28a31c-freeciv-2.5.11/lib/libfreeciv-srv.so.0.0.0
shrinking /nix/store/abym5ffw8k8npwdbyp5s1rrrzi28a31c-freeciv-2.5.11/bin/freeciv-server
shrinking /nix/store/abym5ffw8k8npwdbyp5s1rrrzi28a31c-freeciv-2.5.11/bin/freeciv-sdl
shrinking /nix/store/abym5ffw8k8npwdbyp5s1rrrzi28a31c-freeciv-2.5.11/bin/freeciv-manual
shrinking /nix/store/abym5ffw8k8npwdbyp5s1rrrzi28a31c-freeciv-2.5.11/bin/freeciv-mp-cli
gzipping man pages under /nix/store/abym5ffw8k8npwdbyp5s1rrrzi28a31c-freeciv-2.5.11/share/man/
strip is /nix/store/mgyvr3kil9qv0mywikpi0dbli061bpg4-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/abym5ffw8k8npwdbyp5s1rrrzi28a31c-freeciv-2.5.11/lib  /nix/store/abym5ffw8k8npwdbyp5s1rrrzi28a31c-freeciv-2.5.11/bin
patching script interpreter paths in /nix/store/abym5ffw8k8npwdbyp5s1rrrzi28a31c-freeciv-2.5.11
checking for references to /build in /nix/store/abym5ffw8k8npwdbyp5s1rrrzi28a31c-freeciv-2.5.11...

Failure on x86_64-darwin (full log)
Attempted: freeciv, gtk2
Partial log (click to expand)
clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [Makefile:1305: freeciv-sdl] Error 1
make[3]: Leaving directory '/private/tmp/nix-build-freeciv-2.5.11.drv-0/freeciv-2.5.11/client'
make[2]: *** [Makefile:1460: all-recursive] Error 1
make[2]: Leaving directory '/private/tmp/nix-build-freeciv-2.5.11.drv-0/freeciv-2.5.11/client'
make[1]: *** [Makefile:817: all-recursive] Error 1
make[1]: Leaving directory '/private/tmp/nix-build-freeciv-2.5.11.drv-0/freeciv-2.5.11'
make: *** [Makefile:721: all] Error 2
builder for '/nix/store/8jmf3hfswcnsvgq8jc6l2mizvvpkb3v8-freeciv-2.5.11.drv' failed with exit code 2
error: build of '/nix/store/8jmf3hfswcnsvgq8jc6l2mizvvpkb3v8-freeciv-2.5.11.drv' failed

Homebrew disables some gtk tests for freeciv: https://github.com/Linuxbrew/homebrew-core/blob/730680cb01e966ea83c7924c8957cf76be1282a6/Formula/freeciv.rb#L55

Failure on aarch64-linux (full log)
Attempted: autojump, enet, freeciv, gtk2, nvidia-texture-tools, sfml, spidermonkey_38
The following builds were skipped because they don't evaluate on aarch64-linux: wireguard-go
Partial log (click to expand)
shrinking /nix/store/lw6jc3fp823nmikcsw9gsazy75zhvdad-freeciv-2.5.11/bin/freeciv-sdl
shrinking /nix/store/lw6jc3fp823nmikcsw9gsazy75zhvdad-freeciv-2.5.11/bin/freeciv-server
shrinking /nix/store/lw6jc3fp823nmikcsw9gsazy75zhvdad-freeciv-2.5.11/lib/libfreeciv-srv.so.0.0.0
shrinking /nix/store/lw6jc3fp823nmikcsw9gsazy75zhvdad-freeciv-2.5.11/lib/libfreeciv.so.0.0.0
gzipping man pages under /nix/store/lw6jc3fp823nmikcsw9gsazy75zhvdad-freeciv-2.5.11/share/man/
strip is /nix/store/8yfik687kfccisxnad42j19lfb7ij9b4-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/lw6jc3fp823nmikcsw9gsazy75zhvdad-freeciv-2.5.11/lib  /nix/store/lw6jc3fp823nmikcsw9gsazy75zhvdad-freeciv-2.5.11/bin
patching script interpreter paths in /nix/store/lw6jc3fp823nmikcsw9gsazy75zhvdad-freeciv-2.5.11
checking for references to /build in /nix/store/lw6jc3fp823nmikcsw9gsazy75zhvdad-freeciv-2.5.11...
error: build of '/nix/store/5z9r8p1ykppk1671r8j09vjcazwi0qyd-nvidia-texture-tools-2.1.0.drv' failed

Tests are currently disabled anyway. I bet we will have to disable those if they break in headless environments though.


Reformat Models: Software

This change is being split out from #420 and it:

Cleans up the model look a bit

@guidow, PTAL

Looks ok


improve eval performance by caching per-repo/version conda environments

Describe the feature
Right now running an eval (e.g., using the SWE-agent evaluation/evaluation.py script) runs in such a way that a temporary conda environment is created each time you run an eval. It seems like the conda environments could be created once per repo/version, and then reused again and again across different evaluations.
Potential Solutions
One way to do this (for which I'll attach a PR) is to simply configure a reaonable path_conda in the eval args; e.g.,
args.path_conda = os.path.join(testbed, "conda", repo.rsplit('__', 1)[-1], version)

I believe Auto Code Rover has an implementation of this in which they group non-redundant conda environments and cache them.


Recent Blogs are out of date

the links to recent blogs are over 1 year old, it would probably be better to just remove them and have one link to an appropriate location that is maintained regularly.

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

ID: 321a32c0-b7fa-67bf-a2bf-788e9071a1a2
Version Independent ID: 86926078-20a0-34bd-6e53-17f71d957912
Content: Conditional Access adoption kit - Azure Active Directory
Content Source: articles/active-directory/conditional-access/howto-conditional-access-adoption-kit.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@DeanGross
Thanks for your feedback! We will investigate and update as appropriate.

I made a pull request to remove these, and agree that these can probably be updated or kept as a non-static link.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/98233
I am closing this out but the feedback has been passed along to the content team. CC: @MicrosoftGuyJFlo


GeoJSON download of Germany, France or Spain shows error "string_too_short"

When I select for example Germany, France or Spain and try to download the GeoJSON data...

...I get this error message:

I guess it expects something like DE instead of just D, FR instead of F, or ES instead of E.
Brazil on the other hand works fine (because it has BR).

Looks like something went wrong with the code for Germany etc., I'll fix it very soon today! Thanks!

Forgot to close the issue, this has been already fixed a few days ago, sorry! :slightly_smiling_face:


Ordinal numbers exercise

Provive excercise for ordinal numbers.
https://en.wikipedia.org/wiki/Ordinal_numeral

@neenjaw I'd love to contribute more. I got some more exercises in the pipe 😉 Of course I can also help with improving the existing exercises.
I am currently doing the php exercises on the platform itself to get a complete overview.

3 things left then let's get this merged!!


Cant use my own Api key

Describe the bug

To reproduce
docker run --name sqlchat --platform linux/amd64 --env OPENAI_API_KEY=MYKEY-p 3000:3000 sqlchat/sqlchat
Additional context
hello i am trying to deploy Self-host with Docker i put my api key in parameteres but I got this error:  Please sign up to get free quota or supply your own OpenAI key.

Fixed https://github.com/sqlchat/sqlchat/commit/42bad976a4bd4d9b16a62bb8813555b55e6ffd1b


Add style guidelines to CONTRIBUTING file.

Also, add a link to google-java-format, which should help with keeping
samples within the style guidelines.
For internal bug 28395294.
@lesv PTAL

Current coverage is 48.92% (diff: 100%)

Merging #313 into master will not change coverage

@@             master       #313   diff @@
==========================================
  Files            73         73
  Lines          2242       2242
  Methods           0          0
  Messages          0          0
  Branches        158        158
==========================================
  Hits           1097       1097
  Misses         1115       1115
  Partials         30         30

Powered by Codecov. Last update 7cec9ea...ccbb014

LGTM


Improve devworkspace status

The devworkspace status field is currently lacking for many use cases. I'd like to propose adding a few fields that are common to other k8s objects in order to support management better.
New fields:

.status.conditions - Type corev1.Condition[], stores information about various aspects of workspace state (c.f. .status.conditions on Pods.)
.status.phase - String valued, stores current "phase" of workspace (e.g. running, started, stopped, failed)

The struct for conditions would be the common Kubernetes condition struct type.
Use cases
Conditions can be used to share information about progress in a workspace start process -- e.g. "storage ready", "deployment created", "deployment ready". They can also be used to give more detailed information about the last observed state of a workspace (e.g. the workspace deployment isn't ready because we're pulling images)
Phase is useful to track the status of the workspace -- if e.g. a routing class that is unsupported is specified, a workspace can be marked as "failed". If another service is waiting to show mainIdeUrl to the user, it needs to know the workspace is in a running state.
Proposal
status:
  condition:
  - lastTransitionTime: "2020-05-06T23:21:55Z"
    status: "True"
    type: ServiceAccountReady
  - lastTransitionTime: "2020-05-06T23:21:55Z"
    status: "True"
    type: RoutingReady
  - lastTransitionTime: "2020-05-06T23:21:55Z"
    status: "True"
    type: DeploymentReady
    reason: "OneWordReasonForTransition"
    message: "User-readable message about transition"
  - lastTransitionTime: "2020-05-06T23:21:55Z"
    status: "True"
    type: ComponentsReady
  phase: Running
  mainIdeUrl: https://my-workspace.my-cluster.com
  workspaceId: workspace-id
  additionalInfo: {}

Supported Phases:

Running: Workspace is fully operational and can be accessed
Starting: Workspace is currently being started
Stopped: Workspace exists but is not running
Stopping: Workspace is currently stopping (potentially waiting on preStop actions, e.g.
Failed: There is an issue preventing this workspace from entering the Running phase.

For conditions, I don't have a concrete proposal for categories. Currently, in the che-workspace-operator (which would adopt this API), we use
const (
	WorkspaceComponentsReady     WorkspaceConditionType = "ComponentsReady"
	WorkspaceRoutingReady        WorkspaceConditionType = "RoutingReady"
	WorkspaceServiceAccountReady WorkspaceConditionType = "ServiceAccountReady"
	WorkspaceDeploymentReady     WorkspaceConditionType = "DeploymentReady"
)

but I don't view this list as complete.

I am +1 for that. @davidfestal ?

100 % +1 for this as well. We should probably think a bit more about conditions, possibly so that the last condition (corresponding to the Running phase) would be the Ready condition: it would make it more consistent with POD conditions for example, and more intuitive when waiting for the workspace to be ready with the  kubectl wait command.

Fixed in PR https://github.com/devfile/kubernetes-api/pull/65


support for rooms

Thanks a lot for this really cool piece of software!
I'm aware of issue #817, where it states, that rooms are currently no supported.
Nevertheless, would it be possible to implement support for rooms in the near future?
There are several reasons why I ask:

I really would like to use the official Hue-App (iOS), since it has Siri support, as well as Apple Watch complications. I know there are other Hue-Apps, but I was not able to find a really working one for iOS.
I integrated several non-hue lights into the ha-bridge (Homematic dimmer devices via FHEM and a ESP-controlled LED-strip) which I also would like to control with the Hue-App. Right now this is not possible, because the Hue-App does not work with the ha-bridge.

It is probably not necessary to implement the full Room-API, rather just create one default room that all lights belong to. Or there might be an easy-to-implement way to add some rooms manually via the config-file.
Would be really nice, if there would be some way...

This is #354

Well, IMHO #354 is not the same issue. I'm not asking for a workaround to get the Hue-App somehow working, I'm asking to implement basic support for at least 1 native room.