How do I get rotated MTIImage ?

let device = MTLCreateSystemDefaultDevice()!
let option = MTIContextOptions()
let context = try! MTIContext(device: device, options: option)
let transformFilter = MTITransformFilter()
let angle = CGFloat(90 / 180 * Double.pi)
let tranform = CATransform3DMakeRotation(angle, 0, 0, 1)
transformFilter.transform = tranform
transformFilter.inputImage = MTIImage(cgImage: image.cgImage!, options: [.SRGB: false], alphaType: .alphaIsOne)
let outputImage = transformFilter.outputImage

assumed size of inputImage is 720 * 1280
I was expected that size of outputImage became  1280 * 720, but it's still same size of inputImage
How do I get rotated outputImage ?

Can you add one more method for MTIImage ?
/* Returns a new image representing the original image transformeded for the given CGImagePropertyOrientation */
    @available(iOS 11.0, *)
    open func oriented(_ orientation: CGImagePropertyOrientation) -> CIImage

added a func oriented(_ orientation: CGImagePropertyOrientation) -> MTIImage method on MTIImage. https://github.com/MetalPetal/MetalPetal/blob/master/Frameworks/MetalPetal/Filters/MTIImage%2BFilters.m#L22


Add testing to PushBits

I added a few tests, let's discuss if this is the approach we want to use.
I tried to make the tests as lightweight as possible - without any fancy testing suites or so. A description on how to use them is appended to the Readme.
The new "tests" module holds helpers for initializing tests.

Well, one part I did not think about is the automatic testing in the action. It will not work as there is no config.yml provided with e.g. matrix credentials. Should we just skip those tests when no config is provided or do we want to somehow get those credentials into the action?

This is related to #12.

Hey @CubicrootXYZ, thanks for this pull request!
I think unit tests make the most sense for now; great idea to have a separate mockup module.
As for your question: I'm not yet certain what tests fail exactly. Either way, I would "assume" the library to function properly, so we only need to test what calls are made. Maybe we can setup the tests in a way so the function calls are actually made to a module of our own instead to the library? That way, we would just "emulate" a connection and check if correct calls were made. What I would refrain from is having credentials used in the tests: it's best to be able to perform the tests without Internet connection anyway.

Only part that needed credentials was the dispatcher - replaced him with a generic one that does nothing. Now the tests run without any external information needed.

Looking good! Is this ready to merge?

Yes :)


Incompatible default for argument "cfg_path" (default has type "None", argument has type "Path")

While running tox the mypy classification_model checks fail.
Error:

test_package: OK ✔ in 3.99 seconds
checks: commands[0]> flake8 classification_model tests
checks: commands[1]> isort classification_model tests
Fixing C:\Users\krish\titanicSurvival\production-model-package\classification_model\pipeline.py
checks: commands[2]> black classification_model tests
checks: commands[3]> mypy classification_model
classification_model\config\core.py: note: In function "fetch_config_from_yaml":
classification_model\config\core.py:57: error: Incompatible default for argument "cfg_path" (default has type "None", argument has type "Path")  [assignment]
classification_model\config\core.py:57: note: PEP 484 prohibits implicit Optional. Accordingly, mypy has changed its default to no_implicit_optional=True
classification_model\config\core.py:57: note: Use https://github.com/hauntsaninja/no_implicit_optional to automatically upgrade your codebase
Found 1 error in 1 file (checked 12 source files)
checks: exit 1 (0.50 seconds) C:\Users\krish\titanicSurvival\production-model-package> mypy classification_model pid=28348
  test_package: OK (3.99=setup[0.06]+cmd[1.76,2.16] seconds)
  checks: FAIL code 1 (2.26=setup[0.04]+cmd[0.86,0.28,0.58,0.50] seconds)
  evaluation failed :( (6.78 seconds)

Update the [testenv:checks] in tox.ini as following:

[testenv:checks]
envdir = {toxworkdir}/checks
deps =
	-r{toxinidir}/requirements/typing_requirements.txt
commands =
	flake8 classification_model tests
	isort classification_model tests
	black classification_model tests
	{posargs:mypy classification_model --implicit-optional}

Note that we added --implicit-optional in the last command: posargs
Results:

checks: commands[3]> mypy classification_model --implicit-optional
Success: no issues found in 12 source files
  test_package: OK (3.81=setup[0.09]+cmd[1.72,2.00] seconds)
  checks: OK (3.25=setup[0.02]+cmd[0.81,0.27,0.58,1.58] seconds)
  congratulations :) (7.66 seconds)

Thanks @Krishna2709 ! I face the same error and the command --implicit-optional help mypy to pass the type-checking to optional variables which may be missing or have inconsistent types.


Branch on new local repo fails

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.85.0 (user setup) commit af28b32d7
OS Version: Windows_NT x64 10.0.22621

Steps to Reproduce:

Create new folder and enter folder: mkdir test1 && cd test1

Open vscode: `code . --disable-extensions

Use activity bar to initialize new repo

Create new text file but don't check it in

Use command palette to create new branch Git: Create Branch with name test

Get error - "Error: Git: fatal: Head is not a commit and a branch test cannot be created from it"

Show git command:
> git checkout -q -b test --no-track HEAD
fatal: 'HEAD' is not a commit and a branch 'test' cannot be created from it

Reproduce branch in terminal: git checkout -b test => success

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.85.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!


Toggle notification sound from app settings

I want to allow the user to opt for notification sound from app settings but apparently there's no property in createNotification method to enable/disable sound per notification basis. Currently this can only be done per channel via playSound property which means channel would need to be recreated for this purpose. Is it possible to make this option per notification?

Hi! Sorry for taking so long to respond to your issue on GitHub. I was focused on releasing the new 0.7.0 version of awesome_notifications and awesome_notifications_fcm and i didn't had time enough to do both. But now I can answer all your questions.
So now i'm asking you to recreate this topic using the new issue template. There's a lot of missing informations that i need to understand your problem, and all the instructions are already in the new issue template. Also, remember to check beforehand if your issue was posted by another user.
So I will automatically close all previous issues so far.
Sorry for the inconvenience and i will be waiting for your new issue request.
Thank you so much for your support!


Query not emit result with where _tp_time > condition

following query does not emit result
SELECT
  window_start, count(*) AS count, hash, geohash_decode(hash) AS hash_decode, hash_decode.1 AS long, hash_decode.2 AS lat
FROM
  tumble(v_flows_source_locations, 1s)
WHERE
  _tp_time > (now() - 2m)
GROUP BY
  window_start, hash

when removing the where condition, it works
SELECT
  window_start, count(*) AS count, hash, geohash_decode(hash) AS hash_decode, hash_decode.1 AS long, hash_decode.2 AS lat
FROM
  tumble(v_flows_source_locations, 1s)
GROUP BY
  window_start, hash

or adding seek_to works as well
SELECT
  window_start, count(*) AS count, hash, geohash_decode(hash) AS hash_decode, hash_decode.1 AS long, hash_decode.2 AS lat
FROM
  tumble(v_flows_source_locations, 1s)
WHERE
  _tp_time > (now() - 2m)
GROUP BY
  window_start, hash
settings seek_to = '-2m'

the problem is that the first SQL should work, even tho that will not backfill any data
refer to this https://dev.timeplus.cloud/tp-financial/console/query?sql=SELECT+
++window_start%2C+count(*)+AS+count%2C+hash%2C+geohash_decode(hash)+AS+hash_decode%2C+hash_decode.1+AS+long%2C+hash_decode.2+AS+lat
FROM+
++tumble(v_flows_source_locations%2C+1s)
WHERE+
++_tp_time+>+(now()+-+2m)
GROUP+BY+
++window_start%2C+hash
settings+seek_to+%3D+'-2m' for reference

Under settings enable_backfill_from_historical_store =false, we can get the results quickly
but if enable_backfill_from_historical_store=true, will be slowly get the results
It should be a filtering problem of historical queries and needs to be optimized. it seems that pre-filter (prewhere) is not work


Update airtable.py

Hello, as said in the request.request, a timeout should be specified.
I have an unstable internet connection, and this connector will hand for an unspecified amount of time.
Putting the timeout parameter solves this problem.

@johruss don't you need to include the param in the call to requests session?

@johruss don't you need to include the param in the call to requests session?

I had a blonde moment :)
Sorry. I've corrected that.

Actually, not sure hard coding different defaults for timeouts here is the best way to go about this.
Maybe we can store a Airtable._timeout tuple that can be configured by the user during init.
table = Airtable(..., timeout=(10,30))

ps: that's how pyGithub did it
https://pygithub.readthedocs.io/en/latest/github.html#main-class-github

Yes, this may be better.
Is this something you could do?


[RCA Repair Item]Retried deletes should ignore 404 errors

Description:
This pull request aims to resolve the reported issue related to Azcopy, where it erroneously reports failures in cases of a 404 error, despite a successful background delete operation. The proposed fix involves disregarding 404 errors and treating them as successful operations.
Changes:

Implemented a comprehensive fix to address the observed behavior, ensuring Azcopy operates correctly even when a 404 error is reported.
Added validation checks to enhance the overall reliability of Azcopy.
Added Testing Support for this functionality.

Don't forget to change the base branch to main btw!


[beam-12737] add API to handle failed rows in the collection due to sql query runtime error

The problem
When calling to
collection.apply(SqlTransform.query(query))

There are cases that a query can have some errors for a small amount of events in the collection, for example UDF can produce runtime error when it gets some invalid input data.
Current behaviour is that query is failed and records are retried forever, and huge pipeline can have backlog just because 1-2 invalid events.
We need an option to send failed rows to some DLQ and continue processing the rest of the data.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

I haven't looked at the actual implementation but I do have a high-level question about the API:
        input.apply(SqlTransform.query(query)
                .withErrorsTransformer(new  BeamSqlErrorTransformer())
                .registerUdf("func1", Func1.class)
                .registerUdf("func2", Func2.class)

This API looks odd to me. I think it could be more familiar to Beam users if there were an option to make SqlTransform return a tagged PCollection, with one of the PCollections representing error information for failed records.

@TheNeuralBit

This API looks odd to me. I think it could be more familiar to Beam users if there were an option to make SqlTransform return a tagged PCollection, with one of the PCollections representing error information for failed records.

Agree, that's was my first intention, but since we already return rows from this transform, we will need to break the API and return 2 tuple tags, rows and errors, or we can create another SqlTransform with error handling (which I less prefer because I think it will be hard to maintain 2 sql transforms )

Oops, I intended to squash commits. Looks like I may have hit the wrong button.


Add support for Django 2.1 and Python 3.7

Django 2.1 was released August 1, 2018.
https://docs.djangoproject.com/en/2.1/releases/2.1/
Python 3.7 was released June 27, 2018.
https://docs.python.org/3/whatsnew/3.7.html

Codecov Report

Merging #536 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #536   +/-   ##
=======================================
  Coverage   87.81%   87.81%
=======================================
  Files           5        5
  Lines         509      509
  Branches       85       85
=======================================
  Hits          447      447
  Misses         49       49
  Partials       13       13

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 568a0bd...fc3480d. Read the comment docs.


Release zAppBuild 3.0.1

This release is

removing logic as well as definitions of the removed DependencyResolver and ImpactResolver APIs
adds dependencySearch configurations as a required build property
slightly refactoring the utilities by dropping the ResolverUtilities.groovy which was used to preserve backward compatibility in the previous releases
minor updates of the zunit test framework

Please note, this release is performed from a fork of a code owner. The branch was build on upstream/develop but cherry picked two commits to leave the update of the MQ for the next release.
A separate PR will be opened just to get the git history in develop back into sync.

For everyone's awareness. This is the second PR for release 3.0.1. The initial PR #298 for release 3.0.1 got indeed merged to main and got reverted by the code owner due to too many cherry picked commits (different histories between develop and main).
The intention of the cherry picking is to leave #245 on develop for the next release 3.1.0.


Discovery drops on a non-existent label

This same rule is found across various modules as the first discovery.relabel rule. It does a keep based on labels that the pod has a port name defined or one named metrics, is running and ready. But it also checks that the container is not an init container. The problem I have is that I don't have the label for init containers on any of my scrapes. So I'm getting a lot of stuff dropped that shouldn't be. This came to light because I can't get the kube_dns scrape in the core module to work and removing this fourth label from the keep caused it to start working.
I'm happy to submit a PR, but I'm wondering if the right move is to remove this last keep requirement for __meta_kubernetes_pod_container_init ... we could add a drop rule after this rule for if __meta_kubernetes_pod_container_init=true to solve what I think this is trying to do. Can anyone confirm my solution is correct and I'll get it PRd to all the places this exists?
  // kube_dns relabelings (pre-scrape)
  discovery.relabel "kube_dns" {
    targets = discovery.kubernetes.kube_dns.targets

    // keep only the specified metrics port name, and pods that are Running and ready
    rule {
      source_labels = [
        "__meta_kubernetes_pod_container_port_name",
        "__meta_kubernetes_pod_phase",
        "__meta_kubernetes_pod_ready",
        "__meta_kubernetes_pod_container_init",
      ]
      separator = "@"
      regex = coalesce(argument.port_name.value, "metrics") + "@Running@true@false"
      action = "keep"
    }

  // kube_dns relabelings (pre-scrape)
  discovery.relabel "kube_dns" {
    targets = discovery.kubernetes.kube_dns.targets

    // keep only the specified metrics port name, and pods that are Running and ready
    rule {
      source_labels = [
        "__meta_kubernetes_pod_container_port_name",
        "__meta_kubernetes_pod_phase",
        "__meta_kubernetes_pod_ready",
      ]
      separator = "@"
      regex = coalesce(argument.port_name.value, "metrics") + "@Running@true"
      action = "keep"
    }

    // drop any init containers
    rule {
      source_labels = ["__meta_kubernetes_pod_container_init"]
      regex = "true"
      action = "drop"
    }

#40

PR merged


Visual Recognition v3

This pull request adds support for Visual Recognition v3 using the RestKit architecture.

All tests pass.
The merge conflict is with the "project.pbxproj" file. Whoever is responsible for merging this pull request into rest-kit should resolve the merge conflict using the rest-kit branch's project file, then use Xcode to add these files to the project. (Be sure to specify the correct target!)


your readme is bad and you should feel bad

how do I even use this library? Is this a joke to you?

Fixed in https://github.com/Hoenn/go-hn/commit/763ef85c4fc007a6a21e041517b92092d43101c1
This should be enough to get you started.


Support array input for any arbitrary environment variables

Adds a feature to set arbitrary environment variables using the env input. Simply provide each variable in KEY=VALUE format, one per line:
- uses: hydephp/action@master
  with:
    deploy-to: "pages"
    env: |
      CUSTOM_VAR=value
      DEPLOY_SHA=${{ github.sha }}

The environment variables will be available during the build process. Note that if you're using sensitive information, you should use GitHub Secrets instead of hardcoding the values. Also make sure your input is valid "dotenv" syntax.
Fixes https://github.com/hydephp/action/issues/43

As a side note: this works just fine if you just want to set one value:
env: CUSTOM=ENV


cms.changelist.js thinks my static files are local (?)

I just attempted to upgrade from Django-CMS 3.0.3 to 3.2 and hit a snag. When I try to load my page, the toolbar looks like it has no styling applied to it, and Chrome's console tells me that bundle.admin.changelist.min.js is trying to load some CSS from the URL:
http://my-origin-dns-name.comhttp//my-s3-bucket/cms/js/jstree/themes/default/style.css
Digging into the javascript, I think the problem is line 379 of cms/static/cms/js/modues/cms.changelist.js, which reads:
path: origin + that.options.settings.staticPath + 'cms/js/jstree/',
I think that staticPath gets set to my STATIC_URL in cms/templates/admin/cms/page/tree/base.html. Since I set my STATIC_URL to my S3 bucket, the line
path: that.options.settings.staticPath + 'cms/js/jstree/',
would work just fine. But the actual code prepends origin to it, even though I don't host my static files on my origin server.
 A I doing something wrong, or have I found a problem?

thanks a lot for the report!
first problem (no styling) might be related to https://github.com/divio/django-cms/issues/4808
the page tree styles being loaded from incorrect place is a bug

Fixed by #4933.


support immediate query cancellation

@begelundmuller thanks for the comments. I was thinking of removing Query and Exec methods from connection and statement files altogether thats why did not remove the duplication. Not sure if someone might be directly using them, what do you think ?

@begelundmuller thanks for the comments. I was thinking of removing Query and Exec methods from connection and statement files altogether thats why did not remove the duplication. Not sure if someone might be directly using them, what do you think ?

I also thought about that. It's very likely fine to remove them, though they're also easy to keep (can just call the context equivalent using context.Background()). Maybe remove them to keep things clean?
Just to clarify, my comment above about duplication referred to the duplicated logic in ExecContext and QueryContext.

though they're also easy to keep

Its not straightforward to call as xxxContext accepts driver.NamedValue where as regular methods accept driver.Value so will have to convert between these before calling the corresponding xxxContext methods.
Will clean pup duplicate logic.

I can have something like this to convert between the two
func valueToNamedValue(values []driver.Value) ([]driver.NamedValue, error) {
	args := make([]driver.NamedValue, len(values))
	for n, param := range values {
		args[n].Value = param
		args[n].Ordinal = n + 1
	}
	return args, nil
}


Waybar crashes when swicthing to tty with X session

Waybar crashes when I move to a tty with a X session running (and back to sway)
Error message:
(waybar:4350): GLib-GIO-WARNING **: 19:49:58.479: Received property ToolTip with type s does not match expected type (sa(iiay)ss) in the expected interface

** (waybar:4350): ERROR **: 19:49:58.479: Failed to create DBus Proxy for org.kde.StatusNotifierItem-4065-1 /StatusNotifierItem: std::bad_cast

Waybar v0.6.3

Tray issue, @alebastr any idea?

Already fixed in #339. Apparently g_error is a wrong way to log recoverable errors, as it calls abort() internally.

Oh ok got it, thanks!


Position Legend View

As a user I want the legend view to be displayed by default on the top left so I can remind myself of what I’m looking at.
Acceptance Criteria

[x] The Legend is displayed on the top left of the page on load.
[x] The legend can be minimised on request.
[x] Follow the accepted prototype design
[x] Design should match the current style of the frontend
[x] Code is commented
[x] Testing - Check whether the legend is displayed on page load

This has been implemented with #21


Enable websocket support?

I'm trying to get websockets working but it looks like it's not enabled. When I try to upgrade to a websocket connection I get ssl handshake errors currently.
The envoy docs indicate we should be able to enable it like so:
https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/route/route.proto.html#envoy-api-field-route-routeaction-use-websocket
Nginx handles websocket endpoints like this:
https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/websocket

In nginx-ingress it's available by default and then you probably need to tweak proxy-{read,write}-timeout in order to keep it really persistent.
@davecheney I can submit a PR once you validate the how.
Proposals:

Always on. Need to check which are the default read/send timeout values.
Configurable through annotations, which annotation?

NGINX Inc. ingress uses nginx.org/websocket-services: "service1[,service2,...]"
Kubernetes ingress uses nothing because it's always-on but most of the times websocket ping frequency is greater than 60s (which is the default for read/send timeouts) which required the use of ingress.kubernetes.io/proxy-read-timeout & ingress.kubernetes.io/proxy-send-timeout in order to avoid socket from being closed.

I'm not sure the nginx method is correct. As I understand it, websocketness is a property of the route; ie /ws, not the backend service.
If anything this should be
a. contour.heptio.com/websocket-routes: "/route1,[route2,...]" on the ingress
b. contour.heptio.com/upstream-protocol.ws: "port,[port]" on the service.

I'm not sure the nginx method is correct. As I understand it, websocketness is a property of the route; ie /ws, not the backend service.

Yes.

If anything this should be
a. contour.heptio.com/websocket-routes: "/route1,[route2,...]" on the ingress
b. contour.heptio.com/upstream-protocol.ws: "port,[port]" on the service.

AFAIK the second one is not needed at all. Envoy works in the same way other proxies do, forwards the upgrade (in case it exists) to the upstream and this should follow the ws handshaking: https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/websocket
Will send a PR.

Hi @marcoskichel - Websockets have been enabled for the new IngressRoute CRD that is part of the upcoming 0.6.0 release.  Documentation can be found here: https://github.com/heptio/contour/blob/master/docs/ingressroute.md#websocket-support
If you'd like to test one of the beta releases, you can update your Contour image to gcr.io/heptio-images/contour:v0.6.0-beta.2

Thank you!


Don't Force the Interface Type While Checking Isolation

Asking for Sendable conformances on this path is going to lead to
a traversal of the stored properties of the type. If there is an
interface type computation ongoing, as is very likely the case, this
traversal can wind up causing a cycle when it forces the interface type
of a member once again.
Request only the non-structural conformances to break the cycle.
rdar://77189542

@swift-ci smoke test


correct bookmark format

Description
Wrong bookmark format causes the bookmark text to be displayed incorrectly on the front-end page.
递归服务器场景-recursive-server-scenarios

/check-cla

/esaycla

Please squash your commits into a single one.

/approve

/lgtm


H4/H7 HiSky airline - lack of seatmap

Hello Team,
We encounter many issues with lack of seat map for H4/H7 HiSky airline. In the past week we had this issue for approximately 20% of the cases. Could you please check it on your side?
Here is the example:
{,…}
flight
:
{id: "1", airlineCode: "H4", flightNo: "422", departureDate: "2024-02-04", departure: "IST",…}
airlineCode
:
"H4"
arrival
:
"RMO"
cabinClass
:
"E"
departure
:
"IST"
departureDate
:
"2024-02-04"
endRow
:
30
flightNo
:
"422"
id
:
"1"
passengerType
:
"ADT"
planeCode
:
""
startRow
:
1
lang
:
"EN"
units
:
"metric"
Thank you in advance.
Best regards,
Aleksandra

Dear @aleksandrajendrzejczak
this issue is related to the lack of a schedule for flight: H4-422.
For flight H7-422 we have data, please try:
{
  "id": "111",
  "airlineCode": "H7",
  "flightNo": "422",
  "departureDate": "2024-02-04",
  "departure": "IST",
  "arrival": "RMO",
  "cabinClass": "E",
  "planeCode": ""
}


Update OpenVINO archive links in GenAI build docs

Update archive links from 2024.2 prerelease to 2024.3 prerelease
Change unzip to tar -xf in Windows instructions because tar is included by default on Windows and unzip is not
For Linux and macOS, add note with links to other archive versions

I see that links are already updated in master. I followed instructions from https://github.com/openvinotoolkit/openvino.genai/blob/master/src/README.md and that led to 2024.2 branch instructions with the old links. I'll create a PR to update that page.


Blog post announcing project lead change

@rhauch Just seeing that it's still open. You want me to push it?

@gunnarmorling I got it. Just got too busy to do it.

No worries, just wanted to make sure we are not waiting on each other :)


Release 2.1.83

On the docket:

[ ] Support local requirements with lockfiles #1696

Maybe:

[ ] Decouple PEX runtime interpreter selection from buildtime interpreter selection. #1020

Unlikely / backlog:

[ ] PEX_INHERIT_PATH+default shebangs don't interact well with virtualenvs #1344
[ ] Pex interpreter cache is not upgrade / downgrade safe. #1176
[ ] Provide a better resolve error message for a Platform DistributionTarget when --resolve-local-platforms. #1070
[ ] Remove PEX_PYTHON_PATH from build time interpreter selection. #1075

Split off from "Release 2.1.82 #1728" to make way for a hotfix of the fix in #1727.


TUT 1 - Troubleshooting section

@nyameko please close this issue if you satisfied with the push I made regarding this section.

@ZamaZethu  thanks for resolving this issue, and @mmhashatsi thanks for raising ut


aspirate generate gives following error:  Unknown property targetPort in placeholder [PORT, {nextjs.bindings.http.targetPort}].

🔥 aspirate generate command gives following error:  Unknown property targetPort in placeholder [PORT, {nextjs.bindings.http.targetPort}].
As the title suggests, when I try the following command:
aspirate generate

It produces the error shown below
Here is the exception:
Error executing action 'SubstituteValuesAspireManifestAction':
System.InvalidOperationException: Unknown property targetPort in placeholder [PORT, {nextjs.bindings.http.targetPort}].
  at void Aspirate.Processors.PlaceholderSubstitutionStrategies.ResourceBindingsSubstitutionStrategy.Substitute(
     KeyValuePair<string, string> placeholder, Dictionary<string, Resource> resources, Resource resource) in
     /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Processors/PlaceholderSubstitutionStra
     tegies/ResourceBindingsSubstitutionStrategy.cs:52
  at void Aspirate.Processors.BaseResourceProcessor.HandleEnvironmentalVariables(Resource resource, Dictionary<string,
     Resource> resources) in /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Processors/
     BaseResourceProcessor.cs:179
  at void Aspirate.Processors.BaseResourceProcessor.ReplacePlaceholders(Resource resource, Dictionary<string, Resource>
     resources) in /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Processors/
     BaseResourceProcessor.cs:152
  at void Aspirate.Commands.Actions.Manifests.SubstituteValuesAspireManifestAction.ProcessPlaceholders(
     Dictionary<string, Resource> resources, IEnumerable<KeyValuePair<string, Resource>> resourcesToProcess) in
     /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Commands/Actions/Manifests/
     SubstituteValuesAspireManifestAction.cs:29
  at void Aspirate.Commands.Actions.Manifests.SubstituteValuesAspireManifestAction.ReplacePlaceholdersInParsedResources(
     Dictionary<string, Resource> resources) in
     /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Commands/Actions/Manifests/
     SubstituteValuesAspireManifestAction.cs:21
  at Task<bool> Aspirate.Commands.Actions.Manifests.SubstituteValuesAspireManifestAction.ExecuteAsync() in
     /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Commands/Actions/Manifests/
     SubstituteValuesAspireManifestAction.cs:9
  at async Task<int> Aspirate.Commands.Actions.ActionExecutor.ExecuteCommandsAsync() in
     /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Commands/Actions/ActionExecutor.cs:65

🔍 Steps to Reproduce the Bug
i added a node project
Here is the setup in the app host.
var builder = DistributedApplication.CreateBuilder(args);

var identity = builder.AddProject<Projects.authenticationservice>("authenticationservice");

builder.AddNpmApp("nextjs", "../my-app-template", "dev")
    .WithReference(identity)
    .WithHttpEndpoint(targetPort: 3000, env: "PORT")
    .PublishAsDockerFile();

builder.Build().Run();

Does aspir8 have support for node applications at the moment ?

Could you share the manifest.json file that was produced in the AppHost directory please
I'll debug locally
Thanks

Actually - I worked with your AppHost above
For me it does execute successfully - Can you ensure you are on 0.5.3-preview and not 0.5.2-preview please
There does seem to be an issue with image name generation though in the produced manifest - which I'll look at today

Just fixed the dockerfile image name generation - its going out in 0.5.4-preview in a few mins

I updated the version to 0.5.4 preview. when i try the generate command with --skip-build it works fine.
aspirate generate --skip-build

but when i try it without --skip-build it gives following error:
Error executing action 'BuildAndPushContainersFromProjectsAction':
System.Text.Json.JsonReaderException: 'j' is an invalid start of a value. LineNumber: 0 | BytePositionInLine: 0.
  at void System.Text.Json.ThrowHelper.ThrowJsonReaderException(ref Utf8JsonReader json, ExceptionResource resource,
     byte nextByte, ReadOnlySpan<byte> bytes)
  at bool System.Text.Json.Utf8JsonReader.ConsumeValue(byte marker)
  at bool System.Text.Json.Utf8JsonReader.ReadFirstToken(byte first)
  at bool System.Text.Json.Utf8JsonReader.ReadSingleSegment()
  at bool System.Text.Json.Utf8JsonReader.Read()
  at void System.Text.Json.JsonDocument.Parse(ReadOnlySpan<byte> utf8JsonSpan, JsonReaderOptions readerOptions, ref
     MetadataDb database, ref StackRowStack stack)
  at JsonDocument System.Text.Json.JsonDocument.Parse(ReadOnlyMemory<byte> utf8Json, JsonReaderOptions readerOptions,
     byte[] extraRentedArrayPoolBytes, PooledByteBufferWriter extraPooledByteBufferWriter)
  at JsonDocument System.Text.Json.JsonDocument.Parse(ReadOnlyMemory<char> json, JsonDocumentOptions options)
  at JsonDocument System.Text.Json.JsonDocument.Parse(string json, JsonDocumentOptions options)
  at void Aspirate.Services.Implementations.ContainerCompositionService.ValidateBuilderOutput(ShellCommandResult
     builderCheckResult) in
     /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Services/Implementations/
     ContainerCompositionService.cs:250
  at async Task Aspirate.Services.Implementations.ContainerCompositionService.CheckIfBuilderIsRunning(string builder) in
     /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Services/Implementations/
     ContainerCompositionService.cs:245
  at async Task<bool> Aspirate.Services.Implementations.ContainerCompositionService.BuildAndPushContainerForProject(
     ProjectResource projectResource, MsBuildContainerProperties containerDetails, ContainerParameters parameters, bool
     nonInteractive, string runtimeIdentifier) in
     /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Services/Implementations/
     ContainerCompositionService.cs:18
  at async Task Aspirate.Processors.Resources.Project.ProjectProcessor.BuildAndPushProjectContainer(KeyValuePair<string,
     Resource> resource, ContainerParameters parameters, bool nonInteractive, string runtimeIdentifier) in
     /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Processors/Resources/Project/
     ProjectProcessor.cs:77
  at async Task<bool> Aspirate.Commands.Actions.Containers.BuildAndPushContainersFromProjectsAction.ExecuteAsync() in
     /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Commands/Actions/Containers/
     BuildAndPushContainersFromProjectsAction.cs:29
  at async Task<int> Aspirate.Commands.Actions.ActionExecutor.ExecuteCommandsAsync() in
     /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Commands/Actions/ActionExecutor.cs:65

https://github.com/prom3theu5/aspirational-manifests/pull/150 this pr fixes the issue


Fix: Prevent solc-backend panic when non-existent path is passed to it as argument. (Fixes issue #641)

What was wrong?
As stated in #641 , the solc-backend panics when a non-existent path is passed to it as an argument because unwrap was called directly on entry assuming that it is always Ok and not an Err. (in other words, directory errors were unhandled)
How was it fixed?
Just added a checker before calling unwrap, this would exit the process with code 1 and avoids panic.
for entry in walker {
        if entry.is_err() {
            eprintln!("Error: {}", entry.unwrap_err());
            std::process::exit(1)
        }
        let entry = entry.unwrap();
      .......

Every item returned by the iterator is of type Result<walkdir::DirEntry, walkdir::Error>, so entry.is_err() check  needs to be called for each item. An alternative solution would be to check if the path exists before the for loop, but that would not guarantee that every item in the iteration is always of type Ok(walkdir::DirEntry), because an Err can happen for so many reasons.  Also the error message obtained from entry.unwrap_err() is self-descriptive by itself, so no need to print anything extra from our side:
Error: IO error for operation on wrong_path: No such file or directory (os error 2)

looks good! appreciate the contribution


Revert "Fix login error messages not being shown"

Reverts edx/edx-app-android#757
Whoops, this change belongs on the rc/2.5.0 branch. We don't need it in master because it's fixed by https://github.com/edx/edx-app-android/pull/728

Thanks for the pull request, @bguertin! I've created OSPR-1324 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams.
Feel free to add as much of the following information to the ticket:

supporting documentation
edx-code email threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will still be done via the GitHub pull request interface. As a reminder, our process documentation is here.
We can't start reviewing your pull request until you've submitted a     signed contributor agreement     or indicated your institutional affiliation.     If you like, you can add yourself to the AUTHORS      file for this repo, though that isn't required.     Please see the CONTRIBUTING     file for more information.

👍

@brianguertin happy last-day off-by-one error from the bot! :)


Background is smaller than expected

I'm creating a DMG file to distribute my app, but the image is shrunk to a very small size.
This is the command I'm invoking:
create-dmg --volname "Kosmorro installer" \
           --background build/distrib/darwin/dmg-background.jpg \
           --icon Kosmorro.app 100 100 \
           --window-size 640 320 \
           --app-drop-link 500 100 \
           $(distmacdmg) \
           dist/dmg

The created DMG archive looks like the following:

The original dmg-background.jpg image dimensions are 1280 × 640. Everything else works as expected.
What am I missing?

Can you share the background or the DMG? I can only think of a retina issue, but your numbers feel ok...

No problem, you can get them just here:

Background picture
DMG file

Using a TIFF with the two sizes fixes the issue for you? I don't have a retina screen to test.
Background.tiff.zip

Forget that, the problem is the resolution of your image. It's 300 and it should be 72.

Anyway you can still create a TIFF containing both a 640x320 and a 1280x640 representations (both at 72 resolution) if you want it to show properly on retina and not retina displays.
dmg-background.zip

It works like a charm! Thanks!

For anyone else looking how to make tiffs from pngs...
tiffutil -cathidpicheck background.png<EMAIL_ADDRESS>-out background.tiff

saved u some headache


[5.3] Switch from Superclosure to Opis closure

Switching from Superclosure to Opis closure was already mentioned a while back, before the 5.2 release (see https://github.com/laravel/framework/pull/9619) but wasn't discussed after the 5.2 release.
This PR switches the closure serialization library to Opis, simply out of performance reasons.
The Opis closure analyzer is nearly twice as fast as the Superclosure analyzer without losing any features.

Would be slightly more comfortable making this change on master branch for next release. Thanks!


Added photo section

Created a photo section added three images from unsplash.com.

They are lol! I'll resize them in another PR.

@DrWatson111 Looks good. Only thing was I added the / onto the relative image paths. They were images/... and actually needed to be /images... with the slash before it, because its a folder. I corrected those and am merging this PR. Remember to switch back to the main branch and do a git pull to pull down the latest changes before doing any other work. Thanks, and looks great!!


⚠ Jenkins Plugins Artifactory has degraded performance

In 85254c5, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1333 ms

Resolved: Jenkins Plugins Artifactory performance has improved in c7588cb after 12 minutes.


The image preview node returns to the last interim image when you swap groups

I can't reproduce this - can anyone help?

I was going to tell you to do this:

Open the default workflow
Replace Save Image with Image Preview and add it to a Controller
Generate an image
In the Controler, right click the Image Preview to "save as" ( you will get a PNG file ) - as expected
Open another workflow, without closing this one
Return to the initial workflow In the Controler,
Right click the Image Preview to "save as" ( you will get a JFIF file, with the Sampler live preview) - BUG

But I can reproduce it with these steps !
This bug happened in a more complex workflow ( with 5 controllers ). I will try with that and report back.

I tried the workflow where I've found the bug, and It worked as expected - NO BUG

But I think I know what's going on !
It may be related to a different bug. That JFIF file is a "Fake Image"
I tried a 3 stage workflow, with stages 2 and 3 bypassed. It worked well. - NO BUG
Then I enabled stage 2 ( "Refiner" ), and its Preview Image node got filled with the live preview ( JIFIF file ). - "Fake Image"
This happened even before I generated any image with that stage. - different  BUG
But after generating an image with stage 2 ( "Refiner" ), it's Image Preview got a real PNG image.
And I can still get it, after switching workflows. - NO BUG

OK - raised #280 and marking this one as done - I think it's been fixed in other work


_HIDP_PREPARSED_DATA structure

[Enter feedback here]
All links to the _HIDP_PREPARSED_DATA points to the page for HidD_GetPreparsedData function (hidsdi.h). Thus it's impossible to know how _HIDP_PREPARSED_DATA is constructed.

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

ID: affec3d7-565b-c71c-9e26-088760ab74a1
Version Independent ID: 59e81dc7-a6a3-716c-7948-0c0a433e3920
Content: HidD_GetPreparsedData function (hidsdi.h) - Windows drivers
Content Source: wdk-ddi-src/content/hidsdi/nf-hidsdi-hidd_getpreparseddata.md
Product: windows-hardware
Technology: wdk-api-reference
GitHub Login: @mhopkins-msft
Microsoft Alias: mhopkins

Hi @Kinkyboo,
Thank you for contacting us with your question.
The _HIDP_PREPARSED_DATA structure is opaque, by design. You can use the HidP_* methods defined in the hidpi.h header to interact with the values from a _HIDP_PREPARSED_DATA structure returned by the HidD_GetPreparsedData function.
For more information, see the Preparsed Data article. I hope this helps.
Thanks,
~ Mark


Original ImageJ launcher

The ImageJ Launcher purported to be able to launch the original ImageJ even from a plain ImageJ installation. Let's make a separate TOML for this.

Addressed by 2e443d9701e3f302c0660f6c8aa092cad96c08c0


Fix bt chams standing render

This fixes the backtrack chams rendering when a player is standing still. This time it is done better. I am checking for a difference in head origin, and velocity, and if they are jumping.
It is important that we check for velocity and origin. If the player is stutter stepping the origin difference will be 0 at times while they are still moving. Checking for if they are moving AND the difference isn't 0 prevents this issue. The jumping check is to fix an odd issue where the chams only render when the player is falling if standing still.

LGTM 😁


Cannot read properties of null (reading 'substring')

When a user receives an email with invitation and accepts it, they are redirected to a page where the message is:
Cannot read properties of null (reading 'substring')
That has been happening since this morning. I haven't changed anything in the code.

I see lots of these same errors in the server log though so there is probably some situation where it happens. If it happens again please feel free to forward me the invite mail that leads to this error.


vscode-extensions.dbaeumer.vscode-eslint: add metadata

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This package is at version 2.3.0. Do you want to upgrade as well?

This package is at version 2.3.0. Do you want to upgrade as well?

That would be the subject of another PR. But I did not do it because 2.3.0 is labeled as a pre-release.

This package is at version 2.3.0. Do you want to upgrade as well?

That would be the subject of another PR.

It is fine to upgrade and add meta in the same PR.

But I did not do it because 2.3.0 is labeled as a pre-release.

Understood.


Stand up banner for event and other events

Did you need me to design this? It wasn't clear but I'd be happy to do it
if someone can give me size dimensions, information, and dpi.
On Tue, Aug 8, 2017 at 9:42 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/505, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ADQ6gkP4EPPFT3X_UmXxOQ9NB3663gx8ks5sWQ6OgaJpZM4OxflU
.

I didn't want assume. :)
Dimensions are 82" tall by 36" wide. I'd like the Code for Raleigh Logo and
NC OpenPass, CityCamp NC, and NC DataPalooza "and maybe "Building Community
for a Better Tomorrow through civic design, technology and data."
high enough dpi to look good at that scale.
You should have the three event logos and I have the CFR logo on my home
computer - I will upload. Let me know about if the format doesn't work for
you and I will reach back to person who designed it.
Chris Mathews
On Wed, Aug 9, 2017 at 2:00 PM, carsi<EMAIL_ADDRESS>wrote:

Did you need me to design this? It wasn't clear but I'd be happy to do it
if someone can give me size dimensions, information, and dpi.
On Tue, Aug 8, 2017 at 9:42 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/505, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/ADQ6gkP4EPPFT3X_
UmXxOQ9NB3663gx8ks5sWQ6OgaJpZM4OxflU>
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-321334130,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOGtZzag7zZXeOeas8tPbPNSCpmxCd9ks5sWfPDgaJpZM4OxflU
.

Serial comma and caps: "Building community for a better tomorrow through
civic design, technology, and data."
On Wed, Aug 9, 2017 at 2:14 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

I didn't want assume. :)
Dimensions are 82" tall by 36" wide. I'd like the Code for Raleigh Logo and
NC OpenPass, CityCamp NC, and NC DataPalooza "and maybe "Building Community
for a Better Tomorrow through civic design, technology and data."
high enough dpi to look good at that scale.
You should have the three event logos and I have the CFR logo on my home
computer - I will upload. Let me know about if the format doesn't work for
you and I will reach back to person who designed it.
Chris Mathews
On Wed, Aug 9, 2017 at 2:00 PM, carsi<EMAIL_ADDRESS>wrote:

Did you need me to design this? It wasn't clear but I'd be happy to do it
if someone can give me size dimensions, information, and dpi.
On Tue, Aug 8, 2017 at 9:42 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/505, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/ADQ6gkP4EPPFT3X_
UmXxOQ9NB3663gx8ks5sWQ6OgaJpZM4OxflU>
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-
321334130>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAOGtZzag7zZXeOeas8tPbPNSCpmxCd9ks5sWfPDgaJpZM4OxflU>

.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-321337864,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADgoV3b7zRfQnchQO9oV4it4s03sUIXwks5sWfcPgaJpZM4OxflU
.

@ChrisTheDBA @jhibbets OK

I've uploaded the CFR logos I have to GOogle Drive

@carsi  Do you need anything else to begin this?

What should be the output for this banner?
On Mon, Aug 14, 2017 at 7:31 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

@carsi https://github.com/carsi Do you need anything else to begin this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-322337663,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADQ6gksWv0w4j6oqVm4ZvxQJLFkDQrNxks5sYNjMgaJpZM4OxflU
.

I would think whichever has the resolution to not look bad when BIG :)
We support a variety of file formats for uploaded designs.
Adobe Acrobat 9 Document (.pdf) (recommended)
Adobe Illustrator CS3 Artwork (.ai) (recommended)
Adobe Photoshop CS3 Image (.psd) (recommended)
Bitmap Image (.bmp)
GIF Image (.gif)
JPEG Image (.jpg,.jpeg)
Microsoft PowerPoint 2010 Document (.ppt)
Microsoft Word 2010 Document (.doc)
PCX Image (.pcx)
PICT Image (.pic,.pict,.pct)
PNG Image (.png)
PostScript Document (.ps)
TIFF Image (.tif,*.tiff)

Resolution is different from file output. Thanks!
On Tue, Aug 15, 2017 at 11:59 AM, Chris Mathews<EMAIL_ADDRESS>wrote:

I would think whichever has the resolution to not look bad when BIG :)
We support a variety of file formats for uploaded designs.
Adobe Acrobat 9 Document (
.pdf) (recommended) Adobe Illustrator CS3 Artwork (.ai) (recommended)
Adobe Photoshop CS3 Image (
.psd) (recommended) Bitmap Image (.bmp)
GIF Image (
.gif) JPEG Image (.jpg,
.jpeg) Microsoft PowerPoint 2010 Document (.ppt)
Microsoft Word 2010 Document (
.doc) PCX Image (.pcx)
PICT Image (.pic,.pict,
.pct) PNG Image (.png)
PostScript Document (
.ps) TIFF Image (.tif,*.tiff)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-322509809,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADQ6gnQ7OYwEag-nMYQE0YTb70UD-LRXks5sYcBWgaJpZM4OxflU
.

Here are three options:

I had wanted the logos and Code for Raleigh bigger and above.I the middle
and then the left.I guess I am looking for a Code for Raleigh with the
events secondary and since civic spark is durham not include that
Chris Mathews
On Tue, Aug 15, 2017 at 6:22 PM, carsi<EMAIL_ADDRESS>wrote:

Here are three options:
[image: screen shot 2017-08-15 at 6 21 30 pm]
https://user-images.githubusercontent.com/3422850/29339113-bc27dda6-81e6-11e7-8eb9-8a5edb12145b.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-322606019,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOGtYuOBXB-p1qgaBoK8N_d_KPtYFuUks5sYho5gaJpZM4OxflU
.

I like the middle one too!
On Aug 15, 2017 6:36 PM, "Chris Mathews"<EMAIL_ADDRESS>wrote:

I had wanted the logos and Code for Raleigh bigger and above.I the middle
and then the left.I guess I am looking for a Code for Raleigh with the
events secondary and since civic spark is durham not include that
Chris Mathews
On Tue, Aug 15, 2017 at 6:22 PM, carsi<EMAIL_ADDRESS>wrote:

Here are three options:
[image: screen shot 2017-08-15 at 6 21 30 pm]
<https://user-images.githubusercontent.com/3422850/
29339113-bc27dda6-81e6-11e7-8eb9-8a5edb12145b.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-
322606019>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AAOGtYuOBXB-p1qgaBoK8N_d_KPtYFuUks5sYho5gaJpZM4OxflU>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-322608467,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADgoVwyAmKt4xQye-NpRSELyhRh85TGVks5sYh2AgaJpZM4OxflU
.

Each logo is already at least 24 inches wide so we should not make them bigger so there is enough space between the logos.
Also, this is for NC Open Pass, right? If so, NC Open Pass should be the dominant logo and Code for Raleigh secondary. Civic Spark Day is part of NC Open Pass, Raleigh or not.
On ncopenpass.com, there is a blurb at the bottom that reads "NC Open Pass is a partnership between Code for Cary, Code for Durham, Code for Raleigh, and NC DataPalooza." Is this still accurate? If so, should we include Code for Cary and Code for Durham as well?

No, I have been talking all this time about a Code for Raleigh banner, Similar to the one I showed that Code for Greensboro has. Sorry about the confusion.

What is the use case for this banner?
On Wed, Aug 16, 2017 at 10:52 AM, Chris Mathews<EMAIL_ADDRESS>wrote:

No, I have been talking all this time about a Code for Raleigh banner,
Similar to the one I showed that Code for Greensboro has. Sorry about the
confusion.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-322797580,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADQ6gsJCDxkD7iS6K2S_5_JXMOG46fBrks5sYwJBgaJpZM4OxflU
.

Don't mean this to be snarky, but...let people know who we are when we are
at events. Some specifics are Brigade Congress in Philly, ATO, Creative
Mornings, Raleigh Chamber, Innovate Raleigh,
Chris Mathews
On Wed, Aug 16, 2017 at 11:51 AM, carsi<EMAIL_ADDRESS>wrote:

What is the use case for this banner?
On Wed, Aug 16, 2017 at 10:52 AM, Chris Mathews<EMAIL_ADDRESS>wrote:

No, I have been talking all this time about a Code for Raleigh banner,
Similar to the one I showed that Code for Greensboro has. Sorry about the
confusion.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-
322797580>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/ADQ6gsJCDxkD7iS6K2S_5_JXMOG46fBrks5sYwJBgaJpZM4OxflU>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-322815941,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOGtZ5Zt1yv9Ss7E4Si1UujQpLm7i8Wks5sYw_xgaJpZM4OxflU
.

I'll add that it's Chris, Tracy, and sometime me at the table/booth. So
it's code for raleigh specific,  hence the ask for specific logos.
On Aug 16, 2017 12:30 PM, "Chris Mathews"<EMAIL_ADDRESS>wrote:

Don't mean this to be snarky, but...let people know who we are when we are
at events. Some specifics are Brigade Congress in Philly, ATO, Creative
Mornings, Raleigh Chamber, Innovate Raleigh,
Chris Mathews
On Wed, Aug 16, 2017 at 11:51 AM, carsi<EMAIL_ADDRESS>wrote:

What is the use case for this banner?
On Wed, Aug 16, 2017 at 10:52 AM, Chris Mathews <
<EMAIL_ADDRESS>wrote:

No, I have been talking all this time about a Code for Raleigh banner,
Similar to the one I showed that Code for Greensboro has. Sorry about
the
confusion.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-
322797580>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/ADQ6gsJCDxkD7iS6K2S_5_JXMOG46fBrks5sYwJBgaJpZM4OxflU>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-
322815941>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAOGtZ5Zt1yv9Ss7E4Si1UujQpLm7i8Wks5sYw_xgaJpZM4OxflU>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/505#issuecomment-322827300,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADgoVzpOdfgQePB8zQIxtFKalsODIaeeks5sYxkfgaJpZM4OxflU
.

ordered


[FEATURE] Can you please add the generate image feature in the v1 SydneyQt? Thanks!!

Checks

:white_check_mark: I confirm that I have searched existing issues and couldn't find a similar proposal.
:white_check_mark: I have read the documentation and test the software carefully and confirmed that this is not an existing feature.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I want to have the image create feature as well in v1 sydneyqt
Describe the solution you'd like
A clear and concise description of what you want to happen.
I want to have the image create feature as well in v1 sydneyqt
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
here are some codes I previously wrote but still strugling in implementing it.
from main.py:
elif msg_type == "GenerateContentQuery":
                            if message['contentType'] == 'IMAGE':
                                replied = True
                                #todo needs approve
                                # try:
                                # image = sydney.GenerateImageResult()
                                url = "https://www.bing.com/images/create?" + urllib.parse.urlencode({
                                    "partner": "sydney",
                                    "re": "1",
                                    "showselective": "1",
                                    "sude": "1",
                                    "kseed": "8500",
                                    "SFX": "4",
                                    "q": urllib.parse.quote(message["text"]),  # Ensure proper URL encoding
                                    "iframeid": message["messageId"],
                                })
                                generative_image = sydney.GenerativeImage(message["text"], url)
                                image = await sydney.generate_image(proxy, generative_image, cookies)

from sydney.py:

_HEADERS_INIT_CREATIMG = {
    "authority":                 "www.bing.com",
    "accept":                    "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7",
    "accept-language":           "en-US,en;q=0.9",
    "cache-control":             "no-cache",
    "referer":                   "https://www.bing.com/search?q=Bing+AI&showconv=1",
    "upgrade-insecure-requests": "1",
    "user-agent":                "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/112.0.1722.46",
    "x-forwarded-for":           _FORWARDED_IP,
    "Sec-Fetch-Dest":            "iframe",
}

@dataclass
class GenerativeImage:
    text: str
    url: str

@dataclass
class GenerateImageResult:
    generative_image: GenerativeImage
    image_urls: list[str]
    # duration: float  # Representing time.Duration in Python

import re
import asyncio
async def generate_image(
    proxy: str | None = _PROXY,
    generative_image: GenerativeImage | None = None,
    cookies: list[dict] | None = None,
) -> (GenerateImageResult, Exception | None):

    formatted_cookies = {}
    if cookies:
        for cookie in cookies:
            formatted_cookies[cookie["name"]] = cookie["value"]

    async with aiohttp.ClientSession(
        headers=_HEADERS_INIT_CREATIMG, cookies=formatted_cookies
    ) as session:
        try:
            async with session.get(generative_image.url, proxy=proxy) as resp:
                resp.raise_for_status()
                text = await resp.text()

                # Extract result ID
                matches = re.findall(
                    r"/images/create/async/results/(.*?)\?", text
                )
                if not matches or len(matches) < 2:
                    return None, Exception("Cannot find image creation result")
                result_id = matches[1]

                # Await image creation
                result_url = f"https://www.bing.com/images/create/async/results/{result_id}?q={urllib.parse.quote(generative_image.text)}&partner=sydney&showselective=1&IID=images.as"
                for _ in range(15):
                    await asyncio.sleep(3)
                    async with session.get(result_url, proxy=proxy) as result_resp:
                        result_resp.raise_for_status()
                        text = await result_resp.text()

                        # Check for rejection
                        if "Please try again or come back later" in text:
                            return None, Exception("Prompt rejected by Bing")

                        # Extract image URLs
                        image_urls = re.findall(r'<img class="mimg".*?src="(.*?)"', text)
                        if image_urls:
                            return GenerateImageResult(
                                generate_image=generative_image,
                                image_urls=image_urls,
                            ), None

        except aiohttp.ClientError as err:
            return None, err

    return None, Exception("Image creation timeout")

v1 is no longer maintained.


compile envoy on Ubuntu 18.04 failed

I compile envoy of master branch, but I got the error message,
I use the command
bazel build -c dbg  //source/exe:envoy-static
the error message is below
ERROR: /home/linuxlover/C++/envoy-master/source/exe/BUILD:27:1: Linking of rule '//source/exe:envoy-static' failed (Exit 1) envoy_cc_wrapper failed: error executing command /home/linuxlover/.cache/bazel/_bazel_linuxlover/00b64e74972e87e1f22d73a2a071beb5/external/local_config_cc/extra_tools/envoy_cc_wrapper -o bazel-out/k8-dbg/bin/source/exe/envoy-static -pthread ... (remaining 67 argument(s) skipped)
Use --sandbox_debug to see verbose messages from the sandbox
/usr/bin/ld.gold: internal error in write_build_id, at ../../gold/layout.cc:5542
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Target //source/exe:envoy-static failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 24.947s, Critical Path: 24.60s
INFO: 0 processes.
FAILED: Build did NOT complete successfully

I encountered the same error building it on Ubuntu 18.04 in WSL. The build process is a quite tricky in this one for someone new to these tools and bazel does not help much unless you really know what to look for. Anyways, after digging quite a bit and playing here and there, I managed to get a successful build.
Output for lsb_release -a
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:        18.04
Codename:       bionic

Output for uname -a
Linux DESKTOP-XXXXXX 4.4.0-18362-Microsoft #10000-Microsoft Fri Jun 21 11:23:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux

Outout for uname -m
x86_64

The solution in my case was to comment out _envoy_stamped_linkopts() for linkopts in envoy_cc_binary which is in bazel/envoy_binary.bzl file.
To simplify, in bazel/envoy_binary.bzl
change the following line
linkopts = linkopts + _envoy_stamped_linkopts()

to
linkopts = linkopts #+ _envoy_stamped_linkopts()

This give me a successful build. Now the reason for doing this is that if you run bazel with -s, it tells outputs the command it runs
If you run the following without commenting out  _envoy_stamped_linkopts()
bazel build -s //source/exe:envoy-static

It should give the big error but before error, it will print the full command it ran - the whole command will be wrapped in parenthesis. The important part of that full command is the following, I've split the command in multiple lines for easy understanding
envoy_cc_wrapper
-o bazel-out/k8-fastbuild/bin/source/exe/envoy-static
-pthread '-Wl,--hash-style=gnu' -static-libstdc++ -static-libgcc
<EMAIL_ADDRESS>-Wl,-S '-fuse-ld=gold' -Wl,-no-as-needed -Wl,-z,relro,-z,now -pass-exit-codes
<EMAIL_ADDRESS>
Now running the same bazel command after commenting out  _envoy_stamped_linkopts()
bazel build -s //source/exe:envoy-static

would produce a successful build and produce the following command
envoy_cc_wrapper
-o bazel-out/k8-fastbuild/bin/source/exe/envoy-static
-pthread '-Wl,--hash-style=gnu' -static-libstdc++ -static-libgcc
-Wl,-S '-fuse-ld=gold' -Wl,-no-as-needed -Wl,-z,relro,-z,now -pass-exit-codes
<EMAIL_ADDRESS>
If you compare this with the one for failed build above, you would notice that the line
<EMAIL_ADDRESS>
is not there for the command that resulted in successful build.
Looking at the definition of _envoy_stamped_linkopts in bazel/envoy_binary.bzl indicates that similar issue happens on macOS and there is a fix already in place i.e. the select condition to do differently on macOS. Ubuntu 18.04 in WSL is expected to work like any other Linux system but apparently it does not.
def _envoy_stamped_linkopts():
    return select({
        # Coverage builds in CI are failing to link when setting a build ID.
        #
        # /usr/bin/ld.gold: internal error in write_build_id, at ../../gold/layout.cc:5419
        "@envoy//bazel:coverage_build": [],
        "@envoy//bazel:windows_x86_64": [],

        # macOS doesn't have an official equivalent to the `.note.gnu.build-id`
        # ELF section, so just stuff the raw ID into a new text section.
        "@envoy//bazel:apple": [
            "-sectcreate __TEXT __build_id",
            "$(location @envoy//bazel:raw_build_id.ldscript)",
        ],

        # Note: assumes GNU GCC (or compatible) handling of `--build-id` flag.
        "//conditions:default": [
            "-Wl,@$(location @envoy//bazel:gnu_build_id.ldscript)",
        ],
    })

Hope this helps!
P.S. I am still trying to wrap my head around all this build system for envoy so just a beginner. I haven't tested the binary that I get after the successful build so not sure if it breaks anything or not. There should be a proper solution to this instead of just commenting out like above, may be something like what has been done for macOS.

Sorry this somehow was buried in my inbox so I didn't take a look on it.
Can you paste what is in the file bazel-out/k8-fastbuild/bin/external/envoy/bazel/gnu_build_id.ldscript?

This is what I have in bazel-out/k8-fastbuild/bin/external/envoy/bazel/gnu_build_id.ldscript
--build-id=0x

@msamad which version of Bazel are you using?

that file should be like:
--build-id=0x3e63182c3e74e0d517d2f0d1fc2ee950bbfe21e1

which reflecting the git sha you're building.

@msamad which version of Bazel are you using?

Build label: 0.26.0
Build target: bazel-out/k8-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Tue May 28 08:35:14 2019<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>

that file should be like:
--build-id=0x3e63182c3e74e0d517d2f0d1fc2ee950bbfe21e1

which reflecting the git sha you're building.

I see, let me do a clean build and see what I get

@msamad Try use the same version of envoy in .bazelversion file, or if that file doesn't exist, what you get from running ci/run_envoy_docker.sh "bazel version" (sorry this requires docker).

ok, I managed to get a successful build.

Updated repo to the latest commit 8b549bd994a1256fb1913d5dce050a016ed63877
.bazelversion file has 0.28.1
ci/run_envoy_docker.sh "bazel version" returns

Bazelisk version: v0.0.8
WARNING: --batch mode is deprecated. Please instead explicitly shut down your Bazel server using the command "bazel shutdown".
Build label: 0.28.1
Build target: bazel-out/k8-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Fri Jul 19 15:19:51 2019<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>

Updated my system bazel version to 0.28.1 based on above info

Cleaned up the working directory with bazel clean --expunge

Ran bazel build //source/exe:envoy-static

The build was successful.

Only strange part is that when I checked bazel-out/k8-fastbuild/bin/external/envoy/bazel/gnu_build_id.ldscript file after the successful build, it was not there. Is that expected?

that file should be like:
--build-id=0x3e63182c3e74e0d517d2f0d1fc2ee950bbfe21e1

which reflecting the git sha you're building.

Thank you!
I think the key part is this line: https://github.com/envoyproxy/envoy/blob/795ca0e1a30695d660f2648e6039957a4aa962f8/.bazelrc#L18
The script get_workspace_status let Bazel populate bazel-out/volatile-status.txt file with BUILD_SCM_REVISION.
And Envoy populates gnu_build_id.ldscript based on bazel-out/volatile-status.txt file, see https://github.com/envoyproxy/envoy/blob/49425f55aa9212a64b3390909160c41dc22ff349/bazel/BUILD#L40-L52

Note. If you build from a tarball instead of the git repo, you need to create the SOURCE_VERSION file via
python3 tools/github/write_current_source_version.py

since tarball cannot get the git commit SHA.


docs: update maintaining-dependencies.md on major update

Update doc/contributing/maintaining/maintaining-dependencies.md on major V8 updates. Marked as draft in order to wait for https://github.com/nodejs/node/pull/48081 to land

Thanks for the PR! The changes look good to me, but unfortunately we can't do them in updateVersionNumbers because it won't end up in the right commit (this task is very specific and creates the commit src: update NODE_MODULE_VERSION to XXX).
Could you move the code to a new task that is run between majorUpdate and commitUpdate in index.js? It would need to make the change and git add it.

@targos I have moved the task between majorUpdate and commitUpdate. I'm not familiar with this repo hope it's ok

landed https://github.com/nodejs/node/pull/48081


Ignore closed partitions on REFRESH TABLE

Fixes https://github.com/crate/crate/issues/6846

Codecov Report

Merging #6857 into master will decrease coverage by 0.09%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##             master    #6857     +/-   ##
===========================================
- Coverage     83.08%   82.98%   -0.1%
- Complexity    13281    13285      +4
===========================================
  Files          1528     1528
  Lines         49392    49392
  Branches       5938     5938
===========================================
- Hits          41036    40990     -46
- Misses         5556     5608     +52
+ Partials       2800     2794      -6

Impacted Files
Coverage Δ
Complexity Δ

.../src/main/java/io/crate/analyze/TableAnalyzer.java
87.5% <100%> (-1.39%)
3 <0> (ø)

.../main/java/io/crate/metadata/doc/DocTableInfo.java
95.87% <100%> (+0.04%)
48 <1> (+1)
:arrow_up:

...n/java/io/crate/exceptions/JobKilledException.java
0% <0%> (-66.67%)
0% <0%> (-1%)

...main/java/io/crate/auth/user/AlterUserRequest.java
47.36% <0%> (-42.11%)
5% <0%> (-2%)

...cution/engine/aggregation/statistics/Variance.java
66.66% <0%> (-33.34%)
5% <0%> (-2%)

...in/java/io/crate/lucene/match/CrateRegexQuery.java
43.47% <0%> (-30.44%)
4% <0%> (-4%)

...ine/aggregation/impl/GeometricMeanAggregation.java
59.09% <0%> (-21.22%)
11% <0%> (ø)

...n/engine/aggregation/impl/VarianceAggregation.java
64.7% <0%> (-15.69%)
11% <0%> (ø)

...aggregation/impl/StandardDeviationAggregation.java
66.66% <0%> (-13.73%)
11% <0%> (ø)

...a/io/crate/execution/dml/TransportShardAction.java
79.62% <0%> (-9.26%)
13% <0%> (-1%)

... and 34 more

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 b861e2b...ff23942. Read the comment docs.


Proof of concept showing simplicity of NSCoding

So yeah, I got annoyed with all the bugs we have saving/loading triggers and stuff, so thought I'd do a proof-of-concept on using NSCoding. Who'd have thought it would only take me 40 minutes, and result in fewer lines of code? (when we're properly done, we can remove all the stupid dictionaryRepresentation stuff, which will remove hundreds of lines)
With this branch, only triggers are archived at the moment. Of course the goal would be to archive everything we write to disk (shelves, QSCommands, catalogs) but this is just a proof of concept at the moment.
I haven't tested too much, but it seems to work nicely. The other side effect of this working is that quicksilver/elements.trigger.event-qsplugin#2 is now way less complicated (no need to use value transformers - we can just save QSObjects! :)
The downsides...
The reason I never did this before was because it's completely backwards incompatible (without a lot of extra work on our part). After seeing quicksilver/elements.trigger.event-qsplugin#2 though and just how much sidestepping we've been doing over the years I got fed up and figured that backwards incompatibility isn't a problem. We just bump QS to v2.0 and be done with it.
So timescale... I'm kind of lost as to where v1.2.0-dev is, but does it include the UTI stuff? If so, then that's pretty backwards incompatible... so maybe we should just bump to v2.0 now?
warning: back up your triggers.plist before trying

To solve the backwards-incompatible thing, we could just have a check on startup that looks at whether the trigger is in the old format. If so, then save a new file called "triggers-v1.plist" and then update the current triggers file

Closing this for now. I implemented NSCoding today. It doesn't do anything yet, but the next step would be to switch triggers to use that. To answer my 6 year younger self:

To solve the backwards-incompatible thing, we could just have a check on startup that looks at whether the trigger is in the old format. If so, then save a new file called "triggers-v1.plist" and then update the current triggers file

No. What we should do is keep the triggers.plist the same, but make a new triggers-v2.plist. That won't break backwards compatibility. On startup, we check for triggers-v2.plist, if it doesn't exist, we read from triggers.plist using the obsolete method, then just save to triggers-v2.plist going forwards.


Escape colon

Detailed description
When I create an example with a value that contains a colon like this:
range:
  summary: Bla bla bla
  value:
    range: '4:23'

speccy resolve command converts the range value string in a value without quote:
range:
  summary: Bla bla bla
  value:
    range: 4:23

and in SwaggerHub editor I see this:
{
  "range": 263
}

Possible implementation
When quotes are used to define the value of a variable, speccy resolve command can consider the quotes and apply them to the generated file
Your environment
Include as many relevant details about the environment you experienced the bug in and how to reproduce it.

Node Version: v10.16.3
Operating system and version (e.g. Ubuntu 16.04, Windows 7): macOS High Sierra 10.13.6

@MikeRalphson this might a thing for oas-resolver?

This is unrelated to oas-resolver. This is purely due to Speccy's yaml parsing and serialization functions. 4:23 cannot be interpreted as a boolean, number or null, therefore it is a string by default and does not require any quoting. Probably a bug in SwaggerHub.

I'm having a similar issue with a date. I have the following
example: '2019-10-10'

That speccy transforms to
example: 2019-10-10

But I want the example to be treated as a string, is there any way I can force speccy to respect this quote? It should respect it by default right?

2019-10-10 cannot be interpreted as a boolean, number or null, therefore it is a string by default and does not require any quoting. Probably a bug in SwaggerHub.

It can be interpreted as a date, which is what's happening. That's why the quotes should be preserved in this case (might be a js-yaml bug)
js-yaml issue where it's mentioned that 2019-10-10 is read as a date https://github.com/nodeca/js-yaml/issues/198
swagger-ui issue where a similar case is mentioned with the solution being to add the quotes https://github.com/swagger-api/swagger-ui/issues/5061#issuecomment-445286984

Another option from the YAML spec is to use tags like example: !!str 2019-10-10 but speccy resolve also deletes the !!str part

From the OpenAPI spec:

In order to preserve the ability to round-trip between YAML and JSON formats, YAML version 1.2 is RECOMMENDED along with some additional constraints:

Tags MUST be limited to those allowed by the JSON Schema ruleset.
Keys used in YAML maps MUST be limited to a scalar string, as defined by the YAML Failsafe schema ruleset.
The JSON Schema ruleset does not include the date type.

Oh it's because of the JSON Schema then. It's not a bug then as you said. Thanks!
For anyone that ends up here I used this workaround to preserve the quotes:
example: |
  2019-10-10

I think this issue can be closed then, right?

I said it was probably a bug in SwaggerHub. If they're not limiting their yaml parsing to the JSON Schema ruleset, then that's a bug.

All issues here should be closed. Speccy is unmaintained.

I mean that it's not a problem with speccy

Ah, apologies for misreading.

no problem, could have been more clear :)


Xbox availability

Hey, I read your README stating that it is shipped with the console version by default, but it is unfortunately not for me. Do you have a fix for that, like reinstalling or something? Thanks in advance! Good work though!

Hey, I read your README stating that it is shipped with the console version by default, but it is unfortunately not for me. Do you have a fix for that, like reinstalling or something? Thanks in advance! Good work though!

What @Vikijaka probably means is that this filter is still in an initial stage, as it hasn't even been a week since the Path of Exile 2 Early Access has launched, so it isn't shipped with the game as of now.
The README piece of text - "This script (NeverSink's Filter) is shipped on the console versions of the game." - where you got that information is probably just copied and pasted from NeverSink's PoE1 item filter (it even calls it "NeverSink's Filter" and not "NeverSink's PoE2 Lite Filter"), so it is kind of  misleading.
Hopefully, it will be integrated once both the game and the filter are a more advanced stage of development.

Yeah, I read the README, and I did not assume that it was for PoE. It's absolutely fine if it's not working, I did not expect it to, I was just curious, because I'd like to use filters on xbox. Thanks for the replies, I'm closing this for now.


Save trained models using .mlnet or .model file extension

Is your feature request related to a problem? Please describe.
Since the initial versions of ML.NET, the file extension used to save models has been .zip. To my knowledge, this is convention rather than a hard requirement. A .zip file may imply it's something you can open and inspect. For ML.NET, while you can open the zip file, it's not easy to inspect its contents unless you use something like Netron. Therefore, zip may be a misnomer and confusing.
Describe the solution you'd like
Use a file extension other than .zip for model files like .mlnet or .model similar to how Model Builder uses .mbconfig for its configuration file.
Other than clarity on what the contents of the file represent, there may be an opportunity to leverage tooling to generate schema classes. (i.e. In VS, Right-click mymodel.mlnet > Create input & output schema).
Here are some sample models using the .mlnet extension from @bartczernicki
https://github.com/bartczernicki/MLDotNet-BaseballClassification/tree/master/MLDotNet-BaseballClassification/Models/Final

I have always used the default .zip. I think something like .mlnet would make a lot of sense and be an easy differentiator for viewing in a file explorer.

I have always used the default .zip. I think something like .mlnet would make a lot of sense and be an easy differentiator for viewing in a file explorer.

I wonder if something can also be made or added into Netron to recognize the .mlnet files to be able to double click on them.

I would prefer .mlnet file extension. And it should have a good file extension icon for easy recognition on a solution explorer.

Thanks for the feedback everyone!
@luisquintanilla I think we can move forward with this - .mlnet

A good move to get away from a generalized(.zip) to a specific(.mlnet) file extension.

*.zip doesn't provide an intuition of what is present.
*.zip can be easily interpreted as a compressed set of files
*.mlnet is explicit in expression(type, technology)
*.mlnet is easy to filter out from a set of given files which will eventually reduce error in applicatons.

Excited to see this change coming.

@luisquintanilla note to self: This is part of the improve code gen story

@luisquintanilla How do you envision us incorporating this into the improve generated code? You want to start using .mlnet instead of .zip in the saved model?

You want to start using .mlnet instead of .zip in the saved model?

Yup. That's right. As a first step it would be just changing the extension name.


bug: https://turbo.t3.gg/ down after latest commits

Provide environment information
I'm on a Mac, tried in Chrome, Firefox, and Safari.
Howdy! Just a heads up, I happened to be integrating the awesome Create T3 Turbo into my project so I noticed. After the last two commits to the main branch, the https://turbo.t3.gg/ site has an Application error: a server-side exception has occurred.
Describe the bug
Application error: a server-side exception has occurred (see the server logs for more information). Digest:<PHONE_NUMBER>
Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error. window.console.error @ 568-81c095348dda3b0e.js:1
Link to reproduction
https://turbo.t3.gg/
To reproduce
Current behavior:

Go to https://turbo.t3.gg/
Application crashes on load as per the above

Expected behavior:

Go to https://turbo.t3.gg/
Application rocks, like it usually does

Additional information
Thanks for your contributions to the OSS community and making the rest of us look so bad!

Closed in https://github.com/t3-oss/create-t3-turbo/commit/cea783769692a5d5911a372209aef74dedccf4a3


Policy: performance vs compatibility

Context: https://github.com/cupy/cupy/pull/2483#discussion_r328074119
There are cases where we have to make a choice between performance vs compatibility.
In the case above, scipy.ndimage.convolve (cupyx.scipy.ndimage.convolve) internally casts the weights to float64 for better precision. #2483 is (tentatively) implemented in the same manner to achieve the same precision as SciPy's counterpart, but it might cause performance problem in GPUs as float64 operations in GPUs are normally slow.
It would be nice to have a general policy for this kind of tradeoffs, to make future decisions easier.
As a side note, as pointed out by @anaruse (https://github.com/cupy/cupy/pull/2483#discussion_r328452718), the performance characteristic may be different depending on the actual GPU device. Perhaps we may want a mechanism (as in #2436) for users to choose between tradeoffs.

FWIW the same could be said of SciPy's implementation today. It may be something that can be solved across the broader community to preserve compatibility while improving performance 🙂


Initial support and classes for Skaffold run configuration type

Progress towards #12, #13.
Adds initial, empty implementation of Skaffold run configuration type extension, which will register future single/continuous run configuration factories and provide actual run configuration implementations.
For runIde target, pre-selects IDEA Community of the latest release version as a test IDE, making sure we're not targeting features of paid Ultimate version.
Initializes UI resources infrastructure (messages and icon) for Skaffold module.
TODO: We need to request real Skaffold icon from their team. For now, generic Google Cloud Icon is used.
Result:

No tests for now as this is purely declaration code with almost no real functionality.

@etanshaul Please let me know how do we invite Kotlin team for our initial reviews?

@ivanporty there is a kotlin group that we can send messages to and request reviews.
I suggest that we go through an internal review first to iron out any non language style things, and then bring in some Kotlin language reviewers.
I'll start looking at this.

g/kotlin-readability


40 join event - Event detail card changes

Changes made:

A individual event pulls event description data from supaBase and displays it within a description box on its own card.

The visual elements on a event details page are more in line with the Figma designs created previously. Styling for:

Start and end dates
Event type
Description box
Register Button
Top 5 Teams list
Event sheet pop-up

Implementation of "Register" button, and functionality. (** In Progress ** )

Clicking the register button brings up a styled sheet (used through Tamagui) which displays two options for registering
for that particular events teams. You can either join an existing team by clicking the "Join" button, or create your own by
clicking the "Create" button.
Clicking either button will update the information on the sheet.
-> If the Join button is clicked, the sheet's data will update and display a list of teams represented as cards, with
their names, number of teammates, and a "join" button to join that particular team.
-> If the Create button is clicked, the sheet's data will update and display a text entry box for the user to create a
team name, a profile picture that can be updated, and a share button for the user to send to invite teammates in
their contacts.
=> Currently working on pulling team data for the display of current teams for an individual event. I have already
implemented a little  bit of the functionality and styling associated with clicking the "Join" button on the
registration popup, but still have more work to do.

Hey Aidan. I am about to review your PR but I saw you list a few things still "in progress." Is this PR ready to go? Just let me know and I will get you a review! Thanks.

Hey Aidan. I am about to review your PR but I saw you list a few things still "in progress." Is this PR ready to go? Just let me know and I will get you a review! Thanks.

Hey Steph, I am still finishing pulling the team data and displaying it on the popup sheet. I think I'll terminate this PR so I can make the changes, then create a new PR.


Bug: xstate@5 beta It's not possible to rehydrate a nested state correctly

Description
I added  some tests to the example that shows working with persisting states. This example is not working as expected atm.
https://github.com/statelyai/xstate/pull/4102
examples/deep-persistence-with-restore/rehydrationIssue.test.ts
There's one failing test that uses the correct persisted state, but it runs into a timesout.
 it('when using with the correct persistedState actorRef should start with failing {Up: "Step2"} state and stop in final {Up: "Done"}', async () => {
    const workingActors = await createActors(runServiceMachine, 0);

    //const persistedState = JSON.parse(history[2])
    console.log(history);

    // currentPersistedState has the correct value for "src":"fromPromise2". This breaks the test with a timeout.
    // by replacing  "src":"fromPromise2" with "src":"Whatever" it will start working as expected
    const currentPersistedState = JSON.parse(
      '{"value":{"Up":"Step2"},"done":false,"context":{},"historyValue":{},"_internalQueue":[],"children":{"step2":{"state":{"value":"running","done":false,"context":{"errorCount":0,"threshold":3},"historyValue":{},"_internalQueue":[],"children":{"upDownService":{"state":{"status":"active"},"src":"upDownService"}}},"src":"fromPromise2"}}}'
    );
    console.log(currentPersistedState);
    expect(currentPersistedState.value).toStrictEqual({ Up: 'Step2' });

    const actorRef = interpret(
      parentMachine.provide({
        actors: workingActors
      }),
      { state: currentPersistedState }
    );

    actorRef.subscribe({
      next: (state) => {
        console.log('---next', state.value);
      },
      complete: () => {
        console.log('---complete');
      },
      error: (error) => {
        expect(error.message).toBe(
          'Cannot stop child actor step2 of x:0 because it is not a child'
        );
      }
    });

    actorRef.start();

    const stateStep2 = waitFor(actorRef, (s) => s.matches({ Up: 'Step2' }));
    expect((await stateStep2).value).toStrictEqual({ Up: 'Step2' });

    const stateDone = waitFor(actorRef, (s) => s.matches({ Up: 'Done' }));
    return expect((await stateDone).value).toStrictEqual({ Up: 'Done' });
    // actorRef.stop()
  });

What was unexpected that if you change the valid src in the test with something invalid, the test will work as expected.
Looks like something in the rehydration process is broken.
Expected result
rehydration should work with nested state
Actual result
rehydration does not work with nested state
Reproduction
examples/deep-persistence-with-restore/rehydrationIssue.test.ts
Additional context
No response

do you think this would be the same as not being able to restore a machine using xstate/react library.  pam_service from below does not go to a running state nor does it restart already spawned actors running on the parent
const [state, send, pam_service] = useActor(parentAppMachine, {
state: restoredState
})
the documentation says this functionality is available or it it theoretical or still in progress
"In XState v5 beta, actors are now deeply (recursively) persisted. Invoked/spawned actors will be persisted, as well as actors invoked/spawned from those actors, and so on.
In the following example, the state of the mainActor will be persisted, as well as the state of the invoked someCounter actor. When the restoredActor is started, it will start at the persisted state of mainActor, which includes the persisted state of someCounter:"

I believe that this particular issue has been solved by https://github.com/statelyai/xstate/pull/4330 . If you could confirm that the whole thing matches your expectations right now - it would be greatly appreciated

@Andarist Sorry for not coming back earlier. The tests have now two failing tests, which is better than before, because I didn't expect the second test to pass. But it still runs into a timeout.
However, when running main.ts it now returns an Error: An inline child actor cannot be persisted.. I'm just not sure if I should change the code somewhat or if there's an issue with the way the machine, submachine, actor gets persisted.
13:34 $ yarn start
yarn run v1.22.15
$ vite-node --script ./main.ts
Expected to fail, second service is not available
        Building it up
---next Init
---next { Up: 'Step1 system1' }
No history states found.
---rs:  done up-step1-system1
---next { Up: 'Step2 system1' }
---rs: error up-step2-system1
---rs: error up-step2-system1
---rs: error up-step2-system1
---rs: error up-step2-system1
---rs:  notDone up-step2-system1
---next NotDone
---complete
Event "xstate.done.actor.up-step2-system1" was sent to stopped actor "x:0 (x:0)". This actor has already reached its final state, and will not transition.
Event: {"type":"xstate.done.actor.up-step2-system1"}
a little later, back to normal. Pick up where we left
{
  value: { Up: 'Step2 system1' },
  status: 'active',
  historyValue: {},
  _internalQueue: [],
  context: {},
  children: { 'up-step2-system1': { state: [Object], src: 'up-step2-system1' } }
}
        Resuming failed step
---next { Up: 'Step2 system1' }
---next { Up: 'Step2 system1' }
/home/rainer/github/xstate/examples/deep-persistence-with-restore/node_modules/.pnpm/xstate@5.0.0-beta.35/node_modules/xstate/dist/interpreter-5c4e6634.development.esm.js:145
    throw err;
    ^

Error: An inline child actor cannot be persisted.
    at Module.getPersistedState (/home/rainer/github/xstate/examples/deep-persistence-with-restore/node_modules/.pnpm/xstate@5.0.0-beta.35/node_modules/xstate/dist/raise-cdcdf834.development.esm.js:1426:13)
    at StateMachine.getPersistedState (/home/rainer/github/xstate/examples/deep-persistence-with-restore/node_modules/.pnpm/xstate@5.0.0-beta.35/node_modules/xstate/dist/xstate.development.esm.js:593:12)
    at Actor.getPersistedState (/home/rainer/github/xstate/examples/deep-persistence-with-restore/node_modules/.pnpm/xstate@5.0.0-beta.35/node_modules/xstate/dist/interpreter-5c4e6634.development.esm.js:764:42)
    at Object.next (/home/rainer/github/xstate/examples/deep-persistence-with-restore/main.ts:41:37)
    at Actor.update (/home/rainer/github/xstate/examples/deep-persistence-with-restore/node_modules/.pnpm/xstate@5.0.0-beta.35/node_modules/xstate/dist/interpreter-5c4e6634.development.esm.js:494:24)
    at Actor.start (/home/rainer/github/xstate/examples/deep-persistence-with-restore/node_modules/.pnpm/xstate@5.0.0-beta.35/node_modules/xstate/dist/interpreter-5c4e6634.development.esm.js:586:10)
    at builtIt (/home/rainer/github/xstate/examples/deep-persistence-with-restore/main.ts:62:21)
    at /home/rainer/github/xstate/examples/deep-persistence-with-restore/main.ts:81:7
    at ViteNodeRunner.directRequest (file:///home/rainer/github/xstate/examples/deep-persistence-with-restore/node_modules/.pnpm/vite-node@0.31.4/node_modules/vite-node/dist/client.mjs:328:5)
    at ViteNodeRunner.cachedRequest (file:///home/rainer/github/xstate/examples/deep-persistence-with-restore/node_modules/.pnpm/vite-node@0.31.4/node_modules/vite-node/dist/client.mjs:186:14)

Node.js v18.16.0

@Andarist: No worries. Glad that this is working with v5 https://github.com/statelyai/xstate/pull/4102, so that I can start refactoring it for production . Keep up the good work.


Feature Request: Dish orientation control

Feature Request:
If you can accomplish the Stow functionality, perhaps you can also allow for manual orientation control.
Problem It Solves:
In the mountainous backwoods of the inland Northwest, there are peculiar locations with very limited LOS.  Trees rise over 100ft and rising elevations limit placement within range of the required power source.  Range can be increased and power can be extended to a point but there are still sometimes limited placement options.
I'm speculating, but the orientation of Dishy appears to be a function of pointing the dish up and making an initial connection (after BOOTING->SEARCHING).  Everybody has LOS directly up, right?  Because there is incomplete coverage of Starlink currently and this kind of location has a suboptimal FOV, we have LOS but there's no satellite there so getting that connection can take hours or days even with the fancy antenna.
Only after making the initial connection does it apparently obtain the computed optimal angle for coverage and reveal the wedgeFractionObstructedList.  Iteratively trying to find an optimal placement location for Dishy is complicated by this initial connection delay in the more challenging environment.  It appears that after either a GPS change or missing several predicted satellites, it returns to vertical and tries to get a new orientation recommendation (which is often very similar to the last one).
With manual orientation control, we can externally compute the optimal Dishy orientation (or hazard a guess based on past success) and apply it, or even schedule changes to it at different times of the day as needed, completely overriding the Starlink recommendations if we so choose.  The end user community may come up with some better algorithms for odd use cases, like the backwoods holler or the canyons on mars.
It also enables some fun synchronized Dishy dance routines that will make Elon smile.

That's actually a pretty compelling argument for why such a thing may be useful. Unfortunately, it doesn't matter, because it's just not possible given the service interface the dish provides.
The interface includes a dish_stow request which takes no parameters, and none of the other available requests appear to be related to moving the dish position. In fact, the set of implemented requests is pretty much the exact set of functionality that the Starlink app supports, so if the app doesn't include some functionality, it's unlikely the tools in this repository would be able to do it, either.
So SpaceX would have to implement support for this in the dish software first, and I doubt they want people messing with the dish position. That being said, if they ever do add such a thing to the service interface, I'd be happy to add support for it in the tools. In the mean time, though, I'm going to close this out as unimplementable.

That's actually a pretty compelling argument for why such a thing may be useful. Unfortunately, it doesn't matter, because it's just not possible given the service interface the dish provides.
The interface includes a dish_stow request which takes no parameters, and none of the other available requests appear to be related to moving the dish position. In fact, the set of implemented requests is pretty much the exact set of functionality that the Starlink app supports, so if the app doesn't include some functionality, it's unlikely the tools in this repository would be able to do it, either.
So SpaceX would have to implement support for this in the dish software first, and I doubt they want people messing with the dish position. That being said, if they ever do add such a thing to the service interface, I'd be happy to add support for it in the tools. In the mean time, though, I'm going to close this out as unimplementable.


Changes to localise strings in creating groups (Site Info tool)

Thanks for the contribution @mateullas  however could you review the guidelines for making contributions


arrays.initial

Gets all but the last element of a the array
Checklist

[ ] implementation
[ ] tests
[ ] jsdoc

Details

References

_.initial

Even for this library, implementing this operator using reduce would be incredibly inefficient.


R038: Consider configuration for minimum number of bids

A tenderer that participates 1-4 times (especially 1 time) might easily be an outlier for disqualified bids.
In DR, 80% of the flagged tenderers were disqualified 100% of the time. I haven't checked, but I assume most submitted once. Another 10% have a very even 0.66... so they probably submitted 3 times.
cc @camilamila

Similar, but for buyers/procuring entities: #37

I've set the minimum number of bids to 2, because every bidder who only bid once and got disqualified gets flagged otherwise, and that's like 7% of all bidders in the dataset, and 71% of the flagged bidders if the minimum is 1.