🐛 [Bug report]: Deep Linking for the Plays fails. It shows a blank page.

Describe the bug
If you hit any play URL directly, it gives a blank page. It should show the play details page.
To Reproduce
Steps to reproduce the behavior:

Open your browser
Paste this URL: https://www.reactplay.io/plays/social-card and hit enter
You will see a blank screen
Error in the browser console

Expected behavior
The Play should be accessible with deep linking
Screenshots
A clear and concise description of what you expected to happen.
Desktop (please complete the following information):
All
Smartphone (please complete the following information):
All
Additional context
Moving to play detail from the play list works well.

I have worked on a fix for this issue. I will open a PR.


Fix broken link of IntelliJ IDEA Setup Guide

Why are the changes needed?
close https://github.com/apache/incubator-kyuubi/issues/2511
fix link of IntelliJ IDEA Setup Guide
How was this patch tested?

[x] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[x] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

cc @pan3793
do we have plan to unify the docs for latest version and master unreleased version?

Codecov Report

Merging #2512 (d653d8f) into master (6187321) will increase coverage by 0.10%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2512      +/-   ##
============================================
+ Coverage     63.45%   63.55%   +0.10%
  Complexity       69       69
============================================
  Files           371      371
  Lines         17585    17710     +125
  Branches       2348     2358      +10
============================================
+ Hits          11158    11256      +98
- Misses         5392     5408      +16
- Partials       1035     1046      +11

Impacted Files
Coverage Δ

...ache/kyuubi/operation/KyuubiOperationManager.scala
85.24% <0.00%> (-9.20%)
:arrow_down:

...engine/trino/operation/TrinoOperationManager.scala
82.60% <0.00%> (-3.76%)
:arrow_down:

...la/org/apache/kyuubi/session/AbstractSession.scala
97.11% <0.00%> (-2.89%)
:arrow_down:

...ine/flink/operation/FlinkSQLOperationManager.scala
82.92% <0.00%> (-2.08%)
:arrow_down:

...ine/spark/operation/SparkSQLOperationManager.scala
82.22% <0.00%> (-1.87%)
:arrow_down:

.../apache/kyuubi/client/KyuubiSyncThriftClient.scala
88.58% <0.00%> (-1.24%)
:arrow_down:

.../org/apache/kyuubi/session/KyuubiSessionImpl.scala
75.34% <0.00%> (-1.05%)
:arrow_down:

...apache/kyuubi/engine/hive/HiveProcessBuilder.scala
84.31% <0.00%> (-0.80%)
:arrow_down:

...a/org/apache/kyuubi/jdbc/hive/KyuubiStatement.java
26.80% <0.00%> (-0.57%)
:arrow_down:

...in/scala/org/apache/kyuubi/config/KyuubiConf.scala
96.51% <0.00%> (-0.12%)
:arrow_down:

... and 12 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 6187321...d653d8f. Read the comment docs.

thanks, merged to master


Installation Documentation: add requirement "Prometheus"

Description
We installed the reference implementation in a plain Kubernetes Cluster following the given installation instructions from here and everything worked as expected.
Great work!  :-)
But when deploying the ProductCatalog Component from testData, the Component is stuck in "In-Progress-CompCon".
Looking at the APIs it is to see, that the metrics API has no Endpoint:
$ kubectl get api -n components

NAME                                              API_ENDPOINT                                                                                IMPLEMENTATION_READY
prodcat-productcatalog-metrics
prodcat-productcatalog-partyrole                  http://component.oda.cluster2.de/prodcat-productcatalog/tmf-api/partyRoleManagement/v4
prodcat-productcatalog-productcatalogmanagement   http://component.oda.cluster2.de/prodcat-productcatalog/tmf-api/productCatalogManagement/v4

Looking at the component-operator logs the error can be found:
[2023-07-10 15:30:45,022] APIOperator          [WARNING ] [prodcat-productcatalog|api/prodcat-productcatalog-metrics|apiStatus|createOrPatchServiceMonitor] Exception when calling CustomObjectsApi: (404)
Reason: Not Found
HTTP response headers: HTTPHeaderDict({'Audit-Id': '88ebb104-5b04-4f19-ac81-d856ff0cd3c2', 'Cache-Control': 'no-cache, private', 'Content-Type': 'text/plain; charset=utf-8', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '634973d2-0aef-4132-8d29-82b20728d129', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'cbb9e6e3-0a27-4677-98dc-2ca78baddbac', 'Date': 'Mon, 10 Jul 2023 15:30:45 GMT', 'Content-Length': '19'})
HTTP response body: 404 page not found

[2023-07-10 15:30:45,023] kopf.objects         [ERROR   ] [components/prodcat-productcatalog-metrics] Handler 'apiStatus' failed temporarily: Exception creating ServiceMonitor.
[2023-07-10 15:31:45,175] kopf.objects         [ERROR   ] [components/prodcat-productcatalog-metrics] Handler 'apiStatus' failed permanently: Handler 'apiStatus' has exceeded 5 retries.

Some CustomResource for configuring the Prometheus ServiceMonitor does not exist and the API endpoint creation fails.
Looking at the component.yaml it is to see, that this is not an OpenAPI endpoint but an Prometheus endpoint:
apiVersion: oda.tmforum.org/v1alpha4
kind: component
  ...
spec:
  ...
  management:
    - name: metrics
[*]   apitype: prometheus
      implementation: {{.Release.Name}}-{{.Values.component.name}}-sm
      path: /{{.Release.Name}}-{{.Values.component.name}}/metrics
      port: 4000
  ...

We installed Prometheus using the bundled prometheus-grafana-stack:
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo update
helm upgrade --install kube-prometheus-stack --namespace grafana --create-namespace prometheus-community/kube-prometheus-stack

Versions:

Chart: kube-prometheus-stack-47.5.0
App: v0.66.0

Now the endpoint for the metrics API gets successfully created and the component reaches the desired "Complete" status.
Our expectation for the documentation would be to mention, that Prometheus is a necessary requirement for the oda-canvas. And, as it was done for Istio, an example deployment could be given.
Thanks, best regards,
feri
PS: One small note: The Cert-Manager Version "v1.20" mentione In the requirements is wrong. v1.20 does not exist. The latest version is v1.12, using the canvas-oda charts "v1.11" is installed.

PPS: Another useful hint for keycloak, if admin login is stuck and shows "Loading the Admin UI" forever:

The problem ocurrs, if there is a LoadBalancer which edge-terminates the HTTPS request and forwards it as an HTTP request to the keycloak service (reverse proxy).
As documented here
... In order to proper expose the administration console, you should make sure that your proxy is setting the X-Forwarded-* headers ...

The funny part was, that my reverse proxy (nginx) worked well, but istio envoy changed the "X-Forwarded-Proto" header back from "https" to "http".
As a workaround I added the desired value directly in the virtual-service, which I created for keycloak:
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: keycloak-vs
  namespace: canvas
  ...
spec:
  gateways:
  - ...
  hosts:
  - ...
  http:
  - match:
    - uri:
        prefix: /
    route:
    - destination:
        host: canvas-keycloak.canvas.svc.cluster.local
        port:
          number: 8083
      headers:
        request:
          set:
            X-Forwarded-Proto: https

Now the admin console works.


Socket Rooms

I love your react codemirror collab implementation.
Could you add support for socket rooms? Instead of emitting the data to all connected clients, the data is emitted to clients in a particular room. socket.to("room 1").emit(...)
Look forward to hearing from you soon.

Sure, I can implement socket rooms. This makes sense to do. It shouldn't be hard to implement this in the current, multi-docs branch. I'll just need a day or two to do so since I'm pretty busy right now.

Wow! That would be great @BjornTheProgrammer
I tried to add the room functionality in the cursors branch but the cursor positions were not updating in real-time as before. I gave up lol.
socket.to(roomId).emit(...) on the server side prevented the CodeMirror editor from rendering as the event was not firing.
io.to(roomId).emit(...) worked but the cursor behavior was lagging and the socket connection was not persistent. I had to refresh the page each time this happens to get it working again

Well, upon thinking about it, it doesn't necessarily make sense to use socket rooms. You stated that "instead of emitting the data to all connected clients, the data [should be] emitted to clients in a particular room." However, in the current implementation, there are no broadcast emits, which means that data is only emitted directly from client -> sever and server -> client. There are no updates sent to other connections. Adding rooms wouldn't add any benefit to the code base from my understanding.
Additionally, since the push and pull methods from the peerExtension function/class in frontend/src/utils/collab.ts relies on the current state of the document in order to get updates, to me it seems impossible to use broadcast updates of any sort using the @codemirror/collab package.
async push() {
	let updates = sendableUpdates(this.view.state);
	if (this.pushing || !updates.length) return;
	this.pushing = true;
	let version = getSyncedVersion(this.view.state);
	await pushUpdates(socket, docName, version, updates);
	this.pushing = false;
	// Regardless of whether the push failed or new updates came in
	// while it was running, try again if there's updates remaining
	if (sendableUpdates(this.view.state).length)
		setTimeout(() => this.push(), 100);
}

async pull() {
	while (!this.done) {
		let version = getSyncedVersion(this.view.state)
		let updates = await pullUpdates(socket, docName, version)
		let newUpdates = receiveUpdates(this.view.state, updates)
		this.view.dispatch(newUpdates)
	}
}

If you haven't already I recommend checking out the multi-docs implementation, as it adds pseudo-rooms functionality with just client -> sever and server -> client emits.
If I'm misunderstanding or missing a benefit, please let me know, I'll see if it's possible while utilizing the collab package for CodeMirror.

Additionally, the multi-docs branch has cursor support built-in.

Yeah, I looked at the socket.io docs already. I think the point of confusion here is the fact that there is no emitting data to all the connected clients currently. socket.emit(...) does not emit data to all connect clients, just to the client which requested. If you want to send data to all other connected clients you would use socket.broadcast.emit(...).
Hence, what you are describing as a problem, currently is not. There is no place in the codebase where it would make sense to implement a socket room, since we don't want to send data to any other connected clients, only to the one which requested.

I agree with you, @BjornTheProgrammer.
However, I was able to modify the codebase in the multi-docs branch to mimick socket rooms connection.
Thanks.

Sounds good,
Have a great rest of your day!


Cannot build when NSG has deny-all rule

Hello,
We are trying to deploy AIB in an existing subnet.
We followed every step introduced in the documentation to prepare the networking environment.
But we found that we are encountering the error like:
[ERROR] WinRM connection err: unknown error Post "https://<IP_ADDRESS>:5986/wsman": context deadline exceeded
With troubleshooting we found in the NSG flow log that it's proxy VM to build VM port 5986 getting denied by our NSG rule Deny-All-Any-Any.
Only when we add the rule Allow-VNet-VNet-5986 we got the image built successfully.
Same for inbound rules and outbound rules.
However in the documentation there was only the rule of Allow-LB-VNet-60000,60001-Inbound.
Please kindly add below to the documentation to avoid the time wasted for other customers:
If you have Deny-All rule in your NSG, make sure that you add Allow-VNet-VNet-22/5986 for both inbound and outbound rules.

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

ID: c7d8336b-37eb-614b-53c3-ed4501a5740d
Version Independent ID: 6fa1ee51-5752-3a18-984e-c582adf7c363
Content: Create a Windows VM with Azure Image Builder using an existing VNET - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/image-builder-vnet.md
Service: virtual-machines
GitHub Login: @kof-f
Microsoft Alias: kofiforson

@JustinDyt , thank you for your feedback. We have shared the same with the content author(s). This will now be visible in their backlog.

#please-close Looks like instructions for the NSG rule for 5986 have been added.


Allow service data to be passed to shell_command

Description:
Remove the shell command schema so that service data can successfully be passed to the shell command.
Parse args with shlex instead, allowing spaces to be used in the variable data that is passed.
Related issue (if applicable): fixes #2268
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#
Example entry for configuration.yaml (if applicable):
shell_command:
  garage_opened: './garage_opened.sh --device="{{ device }}" --door={{ door }}'

automation:
  alias: Garage Door is Open
  trigger:
    platform: state
    entity_id: sensor.garage_door
    state: 'open'
  action:
    service: shell_command.garage_opened
    data:
      device: Garage Door
      door: 1

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

That's better ;-)


Add Class to Input-Group & Incorporate bootstrap-datetimepicker

This is a (multiple allowed):

[ ] bug

[x] enhancement

[ ] question

CakePHP Version: 3.6

What you did
While using bootstrap-datetimepicker I had to append  to my date input and I needed to add a class of "date" to the input-group that is created. So I had no choice but to use some jquery to add the class.
What happened
No option to add the class to appended input-group
What you expected to happen
The option to add classes to appended input-group
Better Solution
Incorporate http://eonasdan.github.io/bootstrap-datetimepicker/ into these form helpers

I may add a way to customize classes of the input group.
There are tons of date(time) pickers for Bootstrap out there, each one with their own configuration, I cannot incorporate all of theses in the helpers.
I may, however, add a specific template for custom datetime pickers that user would be allowed to customize. I would, however, have to check how CakePHP deals with date/time inputs at a request level.


Add support for rank-n tensors to tilize and untilize

Ticket
https://github.com/tenstorrent/tt-metal/issues/15165
What's changed

Adds support for rank-n tensors to the tilize and untilize ops. In particular this introduces support for 5D tensors.
We support rank-n tensors by first squeezing to a supported rank <= 4, then performing the tilize/untilize, then unsqueezing back to the original shape/rank.
Adds tests for a handful of 5D cases to both the untilize and tilize unit test suites.

Checklist

[ ] Post commit CI passes
[x] Model regression CI testing passes
[x] Device performance regression CI testing passes
[x] New/Existing tests provide coverage for changes

I messed up a few of the tilize tests with an unnecessary refactor. Re-running post-commit to be safe then should be able to merge.


Remove big logs in action templates

Description
Relates to https://github.com/adobe/aio-lib-runtime/issues/44

Avoid big logs in template actions that will show an error message in runtime + take up logging ressources
Reduce response payload of default generic action

Types of changes

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

Checklist:

[x] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

cc @Himavanth @sandeep-paliwal @purplecabbage @rajarju @shazron @meryllblanchet


Added info in liqoctl status

This PR adds some information to the liqoctl status command output.
That info has been divided into two sections:
Local Cluster Informations
Contains information about the local cluster, available from installation, without the cluster being connected to another.
In particular those info are:

Cluster ID
Cluster Name
Cluster Labels
Network Configuration

Pod CIDR
External CIDR
Service CIDR

Remote Clusters Informations
Contains information about local and remote clusters, available only after peering.
In particular those info are:

Local Network Configuration

cluster name

Original Network Configuration

Pod CIDR
External CIDR

Remapped Network Configuration

Pod CIDR
External CIDR

Remote Network Configuration

cluster number

Original Network Configuration

Pod CIDR
External CIDR

Remapped Network Configuration

Pod CIDR
External CIDR

Tunnel Endpoints

cluster association

Gateway IP
Endpoint IP

ToDo

[x] Implement new status infos
[ ] Implement tests
[x] avoid remote clusters checker if there aren't foreign clusters

Preview

/test

/build

/test

/test

/merge


Update libreoffice to 5.4.3

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Travis is 🍏 , just hasn't updated status.


[BUG] Using url scheme to load font in CSUI

What happened?
When trying to load a font into CSUI using PlasmoCSConfig, importing the font source with url rather than data-base64 results in errors.
export const config: PlasmoCSConfig = {
  css: ["font.css"]
}

I've tried the following two approaches:
@font-face {
  font-family: "Matter";
  font-style: normal;
  font-weight: 400;
  src: url(url:~assets/fonts/Matter/Matter-Regular.woff) format("woff");
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA,
    U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215,
    U+FEFF, U+FFFD;
}

Results in 404: {domain}/Matter-Regular.6760eac3.woff. It seems like it didn't prepend the chrome extension.
When manually attempting to prepend the chrome extension, an error also occurs.
@font-face {
  font-family: "Matter";
  font-style: normal;
  font-weight: 400;
  /* font-display: swap; */
  src: url(chrome-extension://{ID}/Matter-Regular.6760eac3.woff)
    format("woff");
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA,
    U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215,
    U+FEFF, U+FFFD;
}

Results in GET chrome-extension://invalid/ net::ERR_FAILED
Version
Latest
What OS are you seeing the problem on?
MacOSX
What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
(OPTIONAL) Contribution

[ ] I would like to fix this BUG via a PR

Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

@AntonOtaner I think this should be labeled as a feature, not a bug. The docs specifically mention base64 for this case because of the error you're observing:
https://docs.plasmo.com/framework/content-scripts-ui/styling#custom-font
Would love to know if you found a way to load the font via URL directly!


Documentation 404

Any chance the readme could be updated with a bit of documentation? This library seems great but I'm not sure where to start with it :)

I'll see if I can put something in it at some point in the future. In the meantime, take a look at https://github.com/aetrion/erl-dns - it is a full-blown authoritative name server that uses this lib for all of the DNS packet construction and parsing.

Thanks :+1:

Hi, is this bug about updating the links of http://github.com/andrewtj/dns_erlang/? Or should I file one separately for this?

@tfarina This issue was more about documenting dns_erlang a bit to show how it can be used in your applications, so I'd open a separate ticket with details about where outdated links are.


support chunks in open_groups and open_datatree

In trying to support chunks the way we do for open_dataset I had to add a lot of parameters to the top-level open_datatree and open_groups functions.
I'm also still looking for the equivalent of _protect_dataset_variables_inplace, and finally _dataset_from_backend_dataset has been the place to call set_close, while #9651 pushed this to the backends for datatree.
No tests yet, and I also want to improve the docstrings before merging.
(the chunked array methods – chunk, load, compute, and persist – should be a separate PR)

[x] complete docstrings
[x] Tests added

cc @TomNicholas, @shoyer

Thanks for doing this @keewis!

I've copied over the docstrings and changed the code of _datatree_from_backend_datatree to both copy over _close and to protect the data against modifications. Which means this should be ready for another round of reviews and possibly merging.

I'm happy to merge this @keewis ?

I'm happy to merge this @keewis ?

me too! Feel free to go ahead and merge.


[C++][Parquet] Add option to parquet::arrow to read columns in parallel using a thread pool

For Parquet file reading that is not IO-bound, we can go faster by reading columns in multiple threads (assuming underlying the IO source is threadsafe). The code will be very similar to that in https://github.com/apache/arrow/blob/master/python/src/pyarrow/adapters/pandas.cc#L1193
Reporter: Wes McKinney / @wesm
Assignee: Wes McKinney](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wesm) / @wesm
Note: This issue was originally created as PARQUET-835. Please see the migration documentation for further details.

Wes McKinney / @wesm:
Issue resolved by pull request 222
https://github.com/apache/parquet-cpp/pull/222

Wes McKinney / @wesm:
PR: https://github.com/apache/parquet-cpp/pull/222


publish to jsr

Thanks to @sigmaSd for getting this off the ground!
I vendored the last version of deno-snapshot_preview1 available (v0.206.0),
added very basic type definitions for Deno, and sprinkled in some as <type>
annotations into the vendored copy. Tests and docs appear to build.
I've also merged the "jsr publish" into the release workflow, reserved the namespace
on jsr, and linked this repository on jsr.

Thanks, the readme also need some changes to mention jsr for deno
One suggestion: I chose @extism/sdk name because maybe in the future you want to add @extism/pdk name

@sigmaSd Thanks again for your work, this is great! I really appreciate it.

Thanks, the readme also need some changes to mention jsr for deno

Ooh, good catch, thanks!

One suggestion: I chose @extism/sdk name because maybe in the future you want to add @extism/pdk name

A ha, yeah – I ended up changing it to @extism/extism to match the npm package. The PDK acts more like a runtime platform in itself (the pdk bundles quickjs.) As a result it seems unlikely that we'll publish the pdk as a package to npm or jsr. (Having now written that down, I may live to eat my words on this, haha 😅)


Else statement highlight

If a comment is added immediately after the else keyword, the comment is not highlighted properly and next line is highlighted as invalid. Picture below illustrate the error.

@pedro-ricardo can you provide plain text snippet as well so I can debut the syntax and don't have to type everything again.

Had you try the else statement alone?

Yes, Without that comment in front, it works just fine.... I had some busy weeks but i'm planning to look into this today.

Solved by #68


DTPhotoViewerController crashes the application

My application crashes if I use the full size image in the following delegate:
func photoViewerController(_ photoViewerController: DTPhotoViewerController, configurePhotoAt
index: Int, withImageView imageView: UIImageView) {
     imageView.image = images[index].image
}

But if I reduce the size of image, the problem is not there. It crashes after I scroll about 50 images. The console says that out of memory. So I think the application is out of memory when I am using heavy images.

Sorry for late reply. I've been busy with my company project but now I am back. Anyway, thank you for your report, I will check it and figure out what could be wrong.

@tungvoduc Did you get time to investigate the issue?

@amrit42087 Sorry for getting back so late. I will be maintaining this project more often from now. I just checked it with the demo project and created 100 heavy images, everything works fine. In fact, the photo view controller does not take much memory. Can you check your memory management in your code?


Fix for issue #36

Removed ready hook (unnecessary) and called setCustomLanguage on renderChatLog.

Thanks again for being amazing and maintaining the module for me! :)


bump named-lock version to 0.2.0

bump named-lock version to 0.2.0
Motivation
In order to resolve the lock_api security issue like this https://github.com/starcoinorg/starcoin/security/dependabot/14
In the current package dependency graph is like
move-package-manager v1.11.11 -> move-cli v0.1.0 -> move-package v0.1.0 -> named-lock v0.1.1 -> parking_lot v0.10.2 -> lock_api v0.3.4
And after update named-lock to v0.2.0, the dependency graph will be named-lock v0.2.0->parking_lot 0.12.1->lock_api v0.4.7
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
cargo test -p move-package

现在使用的分支是starcoin-main分支不是main分支

@nkysg Thanks for the feedback. It's my fault, I should started from the branch of starcoin-main other than main.


lxc list --columns does not work with --format=yaml or json

I'm running lxc list 2.21 and have experienced the same issue with older versions of LXD. LXC list works great with specific columns when specifying format as "table" or "csv" but when using json or yaml it ignores the columns requested and dumps everything.
 lxc list --columns="nbSs" --format="table"  (works)
 lxc list --columns="nbSs" --format="csv" (works)
 lxc list --columns="nbSs" --format="json" (outputs every column in the book)
 lxc list --columns="nbSs" --format="yaml" (outputs every column in the book)

@stgraber I see your point from a datatype perspective.
Is there a way to get a listing of your servers in JSON that isn't massive? I'm looking to return "nbSs" (basic server stats) in JSON using Ansible to put results into a database and then to dashboard. I'd rather not pull a massive list from hundreds of servers for the convenience of format. I see no reason why --columns and --format couldn't work together.

Either way this limitation in functionality should be mentioned in the lxc list --help.

Face palm -- you're right, I had to scroll up to see it at the top of the docs.
Thanks again!


skip trailing slash tests in starlette < 0.13

The behavior that we test was only introduced in 0.14

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: [Pull request #980 opened]

Start Time: 2020-11-23T07:50:16.981+0000

Duration: 24 min 26 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
12135

Skipped
8375

Total
20510

:green_heart: Flaky test report
Tests succeeded.

Expand to view the summary

Test stats :test_tube:

Test
Results

Failed
0

Passed
12135

Skipped
8375

Total
20510


Update vr_datapath.c

vlan->vlan_tag should be ntohs, before &0xfff.

All OpenContrail changes need to be submitted through our gerrit system (review.opencontrail.org). Please use 'git review' to submit this diff.


Some review feedback

two modules with the same source text but different URLs should probably not be equal according to ModuleSourcesEqual: we don't coalesce imports to two modules with the same URL just because they have the same text
there is a typo in the new requirement of HostLoadImportedModule (necesasry)

separately, it would probably be cleaner to have this new requirement just as a new host hook, since we don't expect the host to be able to return a separate module record

we cannot throw for import(randomObject)
suggestion: the AO names are very hard to read, because we have both Modules and Module Sources, and given that they are AO names there are no spaces to disambiguate. What about calling sources just "Source" in all those AO? i.e. module.SourcesEqual(module2), module.GetSourceName(), GetSourceModuleRecord() (this last one is the currently worst named one)

two modules with the same source text but different URLs should probably not be equal according to ModuleSourcesEqual: we don't coalesce imports to two modules with the same URL just because they have the same text

As discussed in the meeting today, this is the design of the method.

there is a typo in the new requirement of HostLoadImportedModule (necesasry)

Thanks, fixed in https://github.com/tc39/proposal-esm-phase-imports/pull/36.

separately, it would probably be cleaner to have this new requirement just as a new host hook, since we don't expect the host to be able to return a separate module record

As discussed in the meeting today - this is not a requirement and it is possible (and expected to meet the host hook requirement) to coalesce into a different module record.

we cannot throw for import(randomObject)

Thanks, also fixed this in https://github.com/tc39/proposal-esm-phase-imports/pull/36.

suggestion: the AO names are very hard to read, because we have both Modules and Module Sources, and given that they are AO names there are no spaces to disambiguate. What about calling sources just "Source" in all those AO? i.e. module.SourcesEqual(module2), module.GetSourceName(), GetSourceModuleRecord() (this last one is the currently worst named one)

As discussed in the meeting the term "ModuleSource" is supposed to clearly mean we are referring to the terminology used for a "Module Source Object". So seeing these two words together is the noun of operation for the methods. I think this terminology is consistently used, and allows us to clearly distinguish module source object operations. We could include some notes to clarify this disambiguation if necessary perhaps?


Fix DEPRECATION WARNING: TimeWithZone#to_s(:short)

Rails has deprecated passing a parameter to to_s and
now expects to_formatted_s to be used instead.
This is the full error I see:
DEPRECATION WARNING: TimeWithZone#to_s(:short) is deprecated. Please use TimeWithZone#to_fs(:short) instead. (called from to_s at /ice-cube-ruby/ice_cube/lib/ice_cube/occurrence.rb:89)

Looks like this is now an error in newer versions of Active Support:
Failures:

  1) IceCube::Occurrence to_s accepts a format option to comply with ActiveSupport
     Failure/Error: expect(occurrence.to_s(:short)).to eq time_now.to_s(:short)

     ArgumentError:
       wrong number of arguments (given 1, expected 0)
     # /Users/user/.rvm/gems/ruby-3.0.2@pro/gems/activesupport-7.1.3/lib/active_support/time_with_zone.rb:200:in `to_s'
     # ./spec/examples/occurrence_spec.rb:31:in `block (3 levels) in <top (required)>'
     # ./spec/spec_helper.rb:76:in `block (3 levels) in <top (required)>'
     # ./spec/spec_helper.rb:75:in `block (2 levels) in <top (required)>'

After applying these changes locally, they pass though :+1:


Record new gif/videos for how to start a git repo/project

Closed w/ https://github.com/srvanderplas/unl-stat850/commit/a64d243dd2629ccf58678f9fdb54da16652875e3


Adding more comprehensive tests across the API.

Still in draft mode. Some minor changes to the API expected.

Codecov Report
Attention: Patch coverage is 14.28571% with 6 lines in your changes are missing coverage. Please review.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files
Coverage Δ

src/esgpt_task_querying/summarize.py
40.00% <14.28%> (-0.57%)
:arrow_down:


Camera doesn't start in full screen mode on UWP

Showing the camera on UWP is not full screen.  The modal presentation style only applies to iOS.  There should be a property that defaults the camera to full screen mode if it does not do it by default.
Bug Information
Version Number of Plugin:  <IP_ADDRESS>
Device Tested On:  Surface Pro 3 - Fall Creators Build
Simulator Tested On: Windows 10 Fall Creators Build
Version of VS: Visual Studio 15.7
Version of Xamarin: <IP_ADDRESS>0146
Versions of other things you are using:
Steps to reproduce the Behavior
Use the camera on UWP from a Xamarin Forms app
Expected Behavior
The camera app should open in full screen mode or have an option to do so.  According to the tooltip the modal presentation style only applies to iOS.
Actual Behavior
The camera app is not in full screen mode.
Code snippet
Screenshots

This is as designed as I call to UWP itself.


Extremely high V3 API usage when using paths filtering

Given (1) a github repo with two files:
- frequently_updated_file.txt
- rarely_updated_file.txt

and (2) a resource that is configured to emit new versions of PRs that modify rarely_updated_file.txt:
- name: pr-branch
  type: pull-request
  source:
    access_token: ((github-token))
    paths:
    - rarely_updated_file.txt
    repository: example-user/example-repo

and (3) a large number (30+) of open PRs affecting frequently_updated_file.txt, but not rarely_updated_file.txt,
then, every instance of a check of this resource will result in a very large number of V3 API calls. These calls seem to specifically be related to checking for modified files, https://github.com/telia-oss/github-pr-resource/blob/master/github.go#L181. Adding a debug line after this response indicates the response.Rate decrementing multiple times per check
We've run in to this issue when trying to use this resource-type on several pipelines for projects that live in a monorepo, which use paths: to limit to PRs that affect a certain pipeline's project. Rarely updated projects end up continually re-polling every unrelated new PR to check for modifications.
This seems thorny, and I'm not sure how to work around it, short of emitting occasional "fake" versions that the downstream pipeline would need to check for and ignore. It seems like a problem with Concourse's resource API design?

On further investigation, I believe this can be mitigated by caching github API responses in the persistent Check container.

It looks like caching is how the jtarchie version of this resource handled
this problem, and adding caching seems to have entirely resolved the issue
for us. we're not using webhooks, though.
was there some poor interaction between caching and webhooks that motivated
this resource to not use caching?
On Wed, Sep 4, 2019, 05:22 Kristian<EMAIL_ADDRESS>wrote:

Hi @YenTheFirst https://github.com/YenTheFirst and thanks for #143
https://github.com/telia-oss/github-pr-resource/pull/143 , sorry I've
taken so long to respond.
[...] every instance of a check of this resource will result in a very
large number of V3 API calls. These calls seem to specifically be related
to checking for modified files [...]
This is correct. When using paths and ignore_paths each discovered
version (new/latest commit to an open PR) will require at least N V3 API
calls where N >= 1 (its one API call per 100th changed file for pagination).
Unfortunately I don't think there are any good ways to remedy this either.
Unless Github's GraphQL API allows us to filter the PRs by modified files
directly, we'll always need to get a complete list of the changed files in
order to do the filtering on our end. Even if we use the
PullRequestChangedFile
https://developer.github.com/v4/object/pullrequestchangedfile/
connection for the PullRequest
https://developer.github.com/v4/object/pullrequest/ object in the
GraphQL API, the cost will be the same, it will just count against a
different rate limit (so arguably it's better to keep it split).
That being said, I don't think caching is a good solution either, at least
not in the resource itself - perhaps it's possible to write a separate task
to do that particular filtering? 🤔
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/telia-oss/github-pr-resource/issues/142?email_source=notifications&email_token=AADMPY26QJONBS7IIR2XEQ3QH6R7TA5CNFSM4IN55BT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD53MCII#issuecomment-527876385,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADMPY57HV63OEMQQGYDBLDQH6R7TANCNFSM4IN55BTQ
.


Support installation with the latest versions of python

Short description of the MR
Use --system-site-packages option to venv to handle cases where setuptools is an external lib
List of things to check before making a MR
Before merging your code, please check the following:

[x] you have added a line describing your changes to the Changelog;
[x] you have added unit tests for any new or improved feature;
[x] you have checked pdi/docs/CheckList.md
you have checked your code format:

[x] you have checked that you respect all conventions specified in CONTRIBUTING.md;
[x] you have checked that the indentation and formating conforms to the docs/formating.astyle;
[x] you have documented with doxygen any new or changed function / class;

you have correctly updated the copyright headers:

[x] your institution is in the copyright header of every file you (substantially) modified;
[x] you have checked that the end-year of the copyright there is the current one;

you have updated the AUTHORS file:

[x] you have added yourself to the AUTHORS file;
[x] if this is a new contribution, you have added it to the AUTHORS file;

you have added everything to the user documentation:

[x] any new CMake configuration option;
[x] any change in the yaml config;
[x] any change to the public or plugin API;
[x] any other new or changed user-facing feature;
[x] any change to the dependencies;

you have correctly linked your MR to one or more issues:

[x] your MR solves an identified issue;
[x] your commit contain the Fix #issue keyword to autoclose the issue when merged;

[x] you have added to this file any other check that was missing.

Replaced by #464 that solves the issue in a cleaner way


Refactor code

Make use of helper functions
Add test functions
Add dependencies (pyproject.toml)
Adhere to linting

@dataclass can be helpful in the definition and reading of data

Remove matplotlib from dependency and leave the plots as an optional tool.

scipy makes Python version to be lower than 3.12.
I think only the refractive index of silicon for temperature and wavelength depends on this 2d interpolation. Check this post to see if I can make it without scipy:
https://stackoverflow.com/questions/43772218/fastest-way-to-use-numpy-interp-on-a-2-d-array

This will be superseded by this project: https://github.com/lnacquaroli/thin_film_optics


updated depreciated react functions createClass and PropTypes

Used the advised updates for React.createClass and React.PropTypes.
I also Linted The whole thing.
Now there is no javascript warning message and you will be able to use newer versions of react without issue.

Hmm. I use Standard JS linting, so the semi-colons actually would throw an error.
https://standardjs.com
I will incorporate the CreateClass changes at some point.
Thanks, I appreciate it.

Ah, I was just doing this! Thank you!

Sorry this took so long.
I just went ahead and made it ES6 class syntax, since that's what I am doing for the project I'm using it on now. I figure this is the ideal "React way" to do things now, and that CreateClass was just a stop-gap anyway.
I tagged it 1.2.0 to reflect the changes.
https://github.com/nathansmith/unsemantic/tree/1.2.0

Should these files be transpiled to ES5 prior to npm publish?
When building with Webpack/babel-loader, we exclude: /node_modules/ as most packages are already transpiled. If we don't use this, we get a slew of errors.


WIP: Feature/aws pcluster 380 - oneapi 2024.0.2

WIP
Summary
Describe the changes made in this PR and why they are needed.
Testing
Describe the testing done for this PR.
Applications affected
List all known applications (UFS WM, JEDI, SRW, etc.) intentionally or unintentionally affected by this PR.
Systems affected
List all systems intentionally or unintentionally affected by this PR.
Dependencies
If there are PRs that need to be merged before or along with this one, please add "- [ ] waiting on LINK_TO_PR" for each of them
Issue(s) addressed
Link the issues addressed or resolved by this PR (use Fixes #??? for fully resolved issues)
Checklist

[ ] This PR addresses one issue/problem/enhancement, or has a very good reason for not doing so.
[ ] These changes have been tested on the affected systems and applications.
[ ] All dependency PRs/issues have been resolved and this PR can be merged.

I am going to replace this soon with a new PR


Update libraries and dependencies

Summary
Updates libraries and dependencies including RN to 0.72.7 and WatermelonDB this last one includes breaking changes so we need to update the imports.
Release Note
NONE

Tested and calls still works. Though I think I'd want Dylan to do a more thorough smoke test if there's a chance this could break things.

Added @DHaussermann as requested

@cpoile I'm going to merge the PR and let @DHaussermann test on his own time.. I think you did a smoke test and this PR is large enough. If anything comes up, let me know so I can help.


Clean up checkstyle config.

to address @JessicaLHartog's comments from #65.

@brndnmtthws Could youalso do the same thing for GenericWhitespace at the end of checkstyle.xml? Looks like it's not really configurable, and the proposed change just makes error messages go from something like this:
<file path>:<line number>:<column number>: GenericWhitespace '<' is followed by whitespace.

to something like this:
<file path>:<line number>:<column number>: '<' is followed by whitespace.

Sure! Done.

Awesome LGTM. :+1:


Feature Request: Cross-platform way to start active Godot installation

The management of the Godot installation is great, but one thing that doesn't seem to be covered much in the docs is how you run the currently active Godot installation. On my Macbook I use open $GODOT; for Windows CMD I think it's start %GODOT%, and for Linux... I'm not even sure. 😅
I would love to see a cross-platform command to open the installed Godot Engine
Since this project is built in C#, you can probably leverage the Process API (or something similar) to run an executable in a platform-agnostic way. This could then be exposed as a command, so that a user can open Godot the same way independent of their system.
Example:
# Install and switch to Godot 4.3
godotenv godot install 4.3.0
godotenv godot use 4.3.0

# Opens Godot 4.3
godotenv godot start

The underlying symlink/environment variable should still stay, so that users have full control over how to run the executable, but this would be a nice QoL to help folks working across OSes.

This can be closed, I didn't realize that GodotEnv sets the godot command to point at your active Godot version. 🤦 Might still be nice to have that documented in the README for dense folks like me.
For those wondering, you can just open the editor with godot -e or godot -p.


Access_token network issue

Based on China's network environment and political factors, as a developer, when using your company's oauth2 service integration, after obtaining the authorization code issued by the provider, I found that I can't obtain the access_token through the http connection provided by you. Is it optimized for this problem? Thank you  very much.
ps. intelliJ IDEA 2019.1+win10

Thanks for getting in touch, but it feels like this is a question that would be better suited to Stack Overflow. As mentioned in the guidelines for contributing, we prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add some more details if you feel this is a genuine bug.


[Feature Request]: End-to-End Integration of Rental, Lease, On sale products

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
This feature introduces a fully integrated system to manage agricultural products available for rent, lease, and sale with backend integration to securely manages product data, owner details, and contact information, ensuring smooth transactions and data consistency across all listings.
Use Case
End-to-End Integration of Rental, Lease, On sale products
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

I would like to work on this, kindly assign me this issue.

i want to work on this issue .assign me this project


Some sort of track changes/audit log would be helpful

It might be good to start with a simple "edited by this person at this time" and eventually incorporate some more serious "track changes" features using text diffing via difflib

It would also be good to understand the scope of this request -- tracking changes down to forever would probably be pretty hard, but keeping single save-to-save individual changes (so current state - 1 changeset) would be a bit easier. Doing line-by-line changes might also be non-trivial, as opposed to having some sort of overlay similar to the way github does it (see here) for an example.


Sqlite support

Hello
Thanks for this amazing project really love it
On RubyVideo I have chosen to explore a very simple stack based on SQLite and the Litestack gem.
As a poor man analytics I have implemented this but would love to replace it by Ahoy_captain. Of course I totally understand that Posgresql is the major player and I might be asking for something exotic.
Just in case you plan to support SQLite at some point I will be more than happy to provide a set or real-world data if that can help.
have a good day

Hi Adrien!
I'd be happy to explore the idea. If you'd be able to get me a nice database dump of real-world data I'd be more than happy to take a look. There are only a few queries that I'd be worried about, and getting a nice adapter pattern in place would be important too, but it's certainly something that's worthy of my time. :)

Great to read that 🎉
If you can DM me on Twitter so that I send you the file (unable to DM you with those new X rules 😄 )


Perf/use fela props

Description
This pull requests makes the following suggestions
Optimizations
In many simple use cases, the useFela hook will be used without any props passed to it, and will only make the theme available to the rule callbacks in the returned css function. In light of that,
this commit makes two optimizations:

Only merge props into the object that is passed to css's callbacks when props are actually passed.
Merge props into the propsWithTheme object using mutative Object.assign, as it is by far the most performant way of doing so. See: https://jsperf.com/object-assign-vs-spreading/3

In addition, combineRules() is now only used when more than one rule is passed and it is actually needed.
These may seem like micro optimizations, but since useFela is a hot
path that could potentially run thousands of times, I think this is
of value in this case.
DX
The useFela hook now throws an error with a helpful message when it is used in a component that isn't a descendant of a RendererProvider
Packages
react-fela
Versioning
Patch
Checklist
Quality Assurance

You can also run yarn run check to run all 4 commands at once.

[x] The code was formatted using Prettier (yarn run format)
[x] The code has no linting errors (yarn run lint)
[x] All tests are passing (yarn run test)
[x] There are no flow-type errors (yarn run flow)

Changes
If one of the following checks doesn't make sense due to the type of PR, just check them.

[x] Tests have been added/updated
[x] Documentation has been added/updated
[x] My changes have proper flow-types

Not sure why tests are failing in the CI env, they all pass locally

Sorry, my bad. Fixed now

I hate mutating like that too, but it's an object we create and completely control, so the perf gains in a hot-path seem worth it.


ROX-11564 Policy Reader

Description
This PR provides a way to inject policies en local-sensor
Create the policies.json file containing the policies:
curl -k -u admin:$ROX_ADMIN_PASSWORD -H "Content-Type:application/json" https://$ROX_CENTRAL_ADDRESS/v1/policies > $tmpf
# and then
# for each id
curl -k -u admin:$ROX_ADMIN_PASSWORD -H "Content-Type:application/json" https://$ROX_CENTRAL_ADDRESS/v1/policies/$id >> $fname

Checklist

[ ] Investigated and inspected CI test results
~[ ] Unit test and regression tests added~
~[ ] Evaluated and added CHANGELOG entry if required~
~[ ] Determined and documented upgrade steps~
~[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

If any of these don't apply, please comment below.
Testing Performed
go run tools/local-sensor/main.go -replay -replay-in=trace.jsonl -resync=10s -delay=0s -central-out=central-out.json -with-policies=policies.json

Check that alerts are being sent in central-out.json

/test all

/retest

/retest go-unit-tests

/test go-unit-tests


Buffer Behavior for Looped Videos

What version of Shaka Player are you using?

v2.0.0-5-gc21c62f

Can you reproduce the issue with our latest release version?

I haven't tried.

Can you reproduce the issue with the latest code from master?

That's what I'm using.

Are you using the demo app or your own custom app?

Custom app.

If custom app, can you reproduce the issue using our demo app?

Not sure.

What did you do?

Used Shaka player to play a looped DASH video.

What content did you load?

https://dev.internet-class.org/background/manifest.mpd
- If custom asset, what manifest and license server URIs?

See above. This is unlicensed content.

How did you interact with the content, if at all?

I did not.

What did you expect to happen?

I expected the buffer to eventually fill with high-quality content as the bandwidth estimate stabilized over repeated looped viewings.

What actually happened?

It didn't.
With the default parameters and looped videos the player would repeatedly prune content from the buffer due to bufferBehind having a default of 30s. (The video I'm playing is ~60s in length.) That would eventually fill the buffer with high quality content, but meant that the player would continue to consume unnecessary bandwidth as it sat there repeatedly downloading the same segments.
When I upped the bufferBehind parameter the buffer would not repeatedly fill, but gets wedged with lower-quality content loaded on the initial page visit. It seems like the bandwidth estimator takes a few 10s of seconds to converge to the correct (and highest) setting, at which point the rest of the buffer is filled with the good stuff. But the first 10–15s remains stuck with lower-quality content.
Perhaps this is something I missed, but it would be nice to have a way to reload the buffer for looped videos but only if the newer content would be higher quality. That said, perhaps this is a bit of an odd use case.
Thanks for the nice player.

Hi Geoffrey,
Here's the problem.  When we adapt resolutions or bitrates, we can't clear everything without an interruption in playback.  If we clear what's under the playhead, playback must stop.
When we adapt down, we don't clear at all, because we want to leave the high quality content in buffer as much as possible.  When we adapt up, we clear most of what's buffered, starting 2 segments ahead of the playhead.
We introduced the 2-segment rule in a8ac3142ef515c14275f548af6905066b22198c2, and we just sped up ABR decisions in 8152e649f1fda29c1792020e05378033ab56a7f8.  With the latest code using our 60-second clip on loop, I see the first 8 seconds (2 segments) at 360p, while the rest is at 576p.  Hopefully, this is an improvement over what you were seeing before.
If you want to get everything cleared, we would have to clear behind the playhead once it progressed into the high res part of the buffer.  Doing this just to optimize looping on a short clip doesn't make much sense for us.
Here are some ideas.  I would guess that any one of these would help in your scenario:

Set bufferBehind small at first, then up it to the length of the clip after the first loop is complete.
If you have some prior knowledge of the user's bandwidth, set bufferBehind large and set abr.defaultBandwidthEstimate to give us a hint on which track is the best one to use.
For a short clip, choose a track explicitly with player.selectTrack() (which will disable ABR) and set bufferingGoal and bufferBehind both to the length of the clip.  Once the clip buffers, it will stay in memory and loop without downloading anything.
Make sure the segments are cacheable by the browser and leave bufferBehind small.  When we loop, the first 2 segments will be new requests for the high bandwidth version, but after that, all segments will be served by the browser's cache from then on.  Disable ABR one the second loop starts, so that the cache responses don't change the bandwidth estimate and cause another track to be selected.

Does this help?

Closing due to inactivity.  If you are still having trouble with this, let us know and we can reopen.


Expand home dir

#702  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @alanvardy and the rest of your teammates on  Graphite


Typescript development problem: Is specialized knowledge required to solve fourslash errors?

Acknowledgement

[X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment
I have a pull #56281 which involves changing src/lib/rs5.d.ts.
I think because it changes that file, there are a few fourslash errors similar to this one:
         fourslash tests
           tests/cases/fourslash/completionListInTypeParameterOfClassExpression1.ts
             fourslash test completionListInTypeParameterOfClassExpression1.ts runs correctly:
     AssertionError: At marker "4": expected [ 'D', 'any', 'Array', …(138) ] to deeply equal [ 'D', 'any', 'Array', …(137) ]
      at _TestState.verifyCompletionsAreExactly (src/harness/fourslashImpl.ts:1213:16)
      at _TestState.verifyCompletionsWorker (src/harness/fourslashImpl.ts:1074:18)
      at _TestState.verifyCompletions (src/harness/fourslashImpl.ts:1009:25)
      at Verify.completions (src/harness/fourslashInterfaceImpl.ts:251:31)
      at eval (completionListInTypeParameterOfClassExpression1.js:8:8)
      at runCode (src/harness/fourslashImpl.ts:4607:9)
      at runFourSlashTestContent (src/harness/fourslashImpl.ts:4565:5)
      at runFourSlashTest (src/harness/fourslashImpl.ts:4548:5)
      at Context.<anonymous> (src/testRunner/fourslashRunner.ts:60:39)
      at processImmediate (node:internal/timers:478:21)

They don't go away after hereby baseline-accept.
Does this require changing the LKG?
Otherwise, how to inspect the differences and modify the baseline?

If you read the test case, you'll see it mention globalTypesPlus, which depends on https://github.com/microsoft/TypeScript/blob/73bc0eba5fd35c3a31cc9a4e6d28d3e89564ce6f/src/harness/fourslashInterfaceImpl.ts#L1108 and would need to be updated. Most (nearly all) PRs do not modify the globals in such a way that this hardcoded list changes.

However, needing to modify this may indicate that something is wrong with the PR (which I have not read; I am not sure anything has changed to make filter(Boolean) any more doable than before.

However, needing to modify this may indicate that something is wrong with the PR (which I have not read; I am not sure anything has changed to make filter(Boolean) any more acceptable than before).

I had added a BooleanConverter interface which has only the conversion with no constructor, to use as filter predicate.  The idea being to be as specific as possible.  However, based on your advice about the cost of changing globals, which I agree with, I have removed it now, and it is using BooleanConstructor without issue.


add license header

license header is inside Go template comment markers ( {{/* ... */}}) to keep it from appearing in end-user visible text (the usage message generated from NOTES.txt).

I think it's a generated NOTICE.txt during helm deployment. I wonder if we need header in NOTICE.txt.

hold off on merging this for a few minutes.  working on an improvement as suggested by Daisy.

added the NOTICE.txt block as suggested by Daisy.  When we deploy with Helm, the user will now see the text below.
daves-mbp-3:helm dgrove$ helm install . --namespace=openwhisk --name=owdev -f owkubedev.yaml -f owkubedev-cloudant.yaml
NAME:   owdev
LAST DEPLOYED: Tue Jun 12 09:44:09 2018
NAMESPACE: openwhisk
STATUS: DEPLOYED

RESOURCES:
....
lots of text omitted
...
NOTES:

Apache OpenWhisk
Copyright 2016-2018 The Apache Software Foundation

This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).

To configure your wsk cli to connect to it, set the apihost property
using the command below:
  $ wsk property set --apihost ow-kube-dev.us-south.containers.mybluemix.net:443

Your release is named owdev.

To learn more about the release, try:

  $ helm status owdev
  $ helm get owdev


Feature/load overlay maps in the tile server #75

Currently left as greyscale. Changing color of XYZ is a little more involved as cannot specify styles. XYZ needs to be source of raster layer. That rasterlayer then has to be source for an ImageLayer

https://github.com/openlayers/openlayers/issues/10470


MTB: add test for Block modification of multi-tenancy resources (MTB-PL1-BC-CPI-2)

Add automated test case for:
https://github.com/kubernetes-sigs/multi-tenancy/tree/master/benchmarks/e2e/tests/block_multitenant_resources

/remove-lifecycle stale

/assign @phoenixking25

@JimBugwadia  Need some help in the cmd you mentioned i.e.
kubectl --kubeconfig=tenant-a -n a1 get all -l <key>=<value>
And above this mentioned to run this as cluster-administrator, so i think there's some conflict.
Run the following commands to retrieve the list of resources managed by the cluster administrator

closing as the project is being restructured


Bling Desktop 0.1.21 - Viewer 0.1.20 - 2FA Issues & Video Downloads

Hi!
Thanks again for this application, its been very useful.
Since the latest update, I've started having issues again.
2FA no longer works, during login I normally am sent an email with the code, this no longer happens. What is odd is that if I terminate the program and close it down, then re-open it, I can see the cameras without this code.
The other problem is that video downloads have stopped again. I fully deleted the install folder and My documents folder and downloaded the latest version here (which is from May), then installed it.
After install, I get prompted to upgrade to 0.1.21 however this again fails saying its not a valid application (seen in the closed issues as well). I then close the processes and restart it, the version then shows as Desktop 0.1.21 and Viewer as 0.1.20.
Again during login the 2FA can be bypassed and no email is ever sent.
I have re-added the INI file but nothing has downloaded since last week.

Thanks!

Re 2FA: If I have passed 2FA once I can restart Bling Desktop without needing to do it again until some time has elapsed. Maybe not a bug.
Re Video Downloads: Used to work, now they don't - all on <IP_ADDRESS>. It's possible the trouble began after I updated to Windows 10 2004 but I can't confirm this. I did note the following in the Windows Application log:
"The program or feature "??\C:\Users\John\Documents\Bling.exe\Download\Versions\Desktop\0.1.21.exe" cannot start or run due to incompatibity with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available." If I try to launch the file manually, it fails with similar error warnings.

Re 2FA: If I have passed 2FA once I can restart Bling Desktop without needing to do it again until some time has elapsed. Maybe not a bug.
Re Video Downloads: Used to work, now they don't - all on <IP_ADDRESS>. It's possible the trouble began after I updated to Windows 10 2004 but I can't confirm this. I did note the following in the Windows Application log:
"The program or feature "??\C:\Users\John\Documents\Bling.exe\Download\Versions\Desktop\0.1.21.exe" cannot start or run due to incompatibity with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available." If I try to launch the file manually, it fails with similar error warnings.

Hi John,
I am aware that is possible, once logged in the authentication token is valid for 24h and during that time you can close and re-open as many times. One of the problems I have is that I don't even need to enter a 2FA code, it will prompt for one, but if I terminate the application and re-open, I gain access to the cameras without ever needing to enter this.


Adding protobuf bundle support to sign-blob and attest-blob

Summary

This pull requests addresses the first part of #3139: adding protobuf bundle support for cosign sign-blob and cosign attest-blob.
You can test this by generating the new bundles, for example signing a local file with a cosign provisioned key (requesting a signed timestamp to corroborate):
go run cmd/cosign/main.go sign-blob --bundle="test-bundle.sigstore.json" --new-bundle-format=true --key="cosign.key" --tlog-upload=false --timestamp-server-url="https://timestamp.githubapp.com/api/v1/timestamp" ../sigstore-go/examples/sigstore-go-signing/hello_world.txt

Or using Fulcio to get a signing certificate for an attestation:
go run cmd/cosign/main.go attest-blob --bundle="pgi-bundle.sigstore.json" --new-bundle-format=true --fulcio-url='https://fulcio.sigstore.dev' --rekor-url='https://rekor.sigstore.dev' --identity-token='...' --type=something --predicate="../sigstore-go/examples/sigstore-go-signing/intoto.txt" ../sigstore-go/examples/sigstore-go-signing/hello_world.txt

You can then verify the public good instance bundle using sigstore-go doing something like:
go run cmd/sigstore-go/main.go -artifact examples/sigstore-go-signing/hello_world.txt -trustedrootJSONpath public-good-trusted-root.json -expectedIssuer "https://token.actions.githubusercontent.com" -expectedSANRegex ".+" ../cosign/pgi-bundle.sigstore.json

Release Note

NONE - we probably want to finish #3139 (especially the more comprehensive conformance testing!) before we announce this as released.
Documentation

N/A - same as above

@steiza can you rebase? Just to check, anything else here or any other testing, or is this good to merge?

Just to check, anything else here or any other testing, or is this good to merge?

I think this is good to merge!


Consider a handler outstanding until it returns and its AckHandler is used

Currently we consider a handler no longer outstanding when the AckHandler::ack() or the AckHandler::nack() call is made.  But as discussed in #5141 this can make the code unnecessarily surprising. We should wait until both the handler returns and its AckHandler is used before declaring the request as "no longer outstanding".

@devbww said (elsewhere):

Thanks. It seems, then, that this could be more easily reproduced (and hence any fix tested) by temporarily sleeping after the ack().

Good idea.

Maybe we should consider a handler outstanding until both the handler return and the AckHandler is used

Sounds reasonable, but perhaps could be seen as too pessimistic. Maybe we should just make it clear(er) that any state that needs to be visible after the get() has to be set before the ack()/nack().

I fear that this is too subtle.  Meaning I wrote the #$%^ code, and still managed to use it incorrectly... 😖


feat(besu): erc-20 HTLC

Is your feature request related to a problem? Please describe.
We need a Cactus plugin for executing atomic swaps via HTLCs for ERC-20 tokens There's a separate task for ETH tokens that is otherwise the same task as this.
Describe the solution you'd like
Some inspiration could be taken from this, but the solidity code itself is just the tip of the ice-berg since we have to work within the plugin architecture and work out other bells and whistles such as contract deployment so that the overall experience for a developer using Cactus as a framework is pleasant rather than overwhelming.
There's a lot more information in the parent issue where the common theme is set for all these sub-tasks related to HTLC development for Cactus.
On a high level the solution should consist of

the solidity code and the boilerplate to make that solidity code callable via the Cactus API clients:
The plugin package under ./packages/cactus-plugin-htlc-eth-besu (naming things is a difficult problem, feel free to suggest better names)
OpenAPI spec json file (in the plugin package)
Generated API client in Typescrit (based on the OpenAPI spec)
The plugin has to be able to deploy the solidity code to the underlying ledger (solidity code to be embedded as a JSON resource, see parent issue for explanation)

Describe alternatives you've considered
N/A
Additional context
Parent: feat(core-api): atomic swaps with HTLCs #510
Sibling: feat(besu): eth HTLC #512
cc: @takeutak @sfuji822 @hartm @jonathan-m-hamilton

@petermetz this is a great idea and very relevant - with Cactus, the deployment and management of instances of HTLCs could be automized. I would say this constitutes a business logic plugin because it implements well-defined logic using a connector/validator pair (Besu). Now,  this poses a problem in terms of organization: will we see the number of packages escalate indefinitely? Are we accounting for "core" business logic plugins, that should be separated from the rest? This is probably good material for being discussed in the next meeting.

@petermetz this is a great idea and very relevant - with Cactus, the deployment and management of instances of HTLCs could be automized. I would say this constitutes a business logic plugin because it implements well-defined logic using a connector/validator pair (Besu). Now,  this poses a problem in terms of organization: will we see the number of packages escalate indefinitely? Are we accounting for "core" business logic plugins, that should be separated from the rest? This is probably good material for being discussed in the next meeting.

@petermetz this is a great idea and very relevant - with Cactus, the deployment and management of instances of HTLCs could be automized.

@RafaelAPB Thank you very much! :-)

I would say this constitutes a business logic plugin because it implements well-defined logic using a connector/validator pair (Besu).

My take (and I'm willing to be wrong here as usual): It is closer to BLPs than let's say the connector plugins (which are clearly not BLPs) but still, one has to ask, if the HTLC plugin is a BLP, then what is the exact business use case it's implementing? And my answer to that is that there is none because it's still more of a core/generic plugin, a lower level primitive that can be used by BLPs but do not itself carry any business logic.

Now, this poses a problem in terms of organization: will we see the number of packages escalate indefinitely?

My hunch is that the number of plugins will be a function of the number of ledgers supported which (hopefully) will continue to increase indefinitely, yes, but as DLTs mature, maybe we'll reach a stable equilibrium, regarding this I'm definitely just guessing.
I have given this (specifically the plugin count) some thought in the past and concluded that eventually we'll have to start storing plugin packages in dedicated git repositories to be able to scale. A case study I can offer where this strategy was successful is the ansible project where they broke out the main repo into smaller repos (and the reason they could do it is because they also have a plugin architecture in place).
Their justification there was that at any given time there would be 2 thousand open bugs on the GH issue tracker regardless of how much effort was spent on closing them, the newly added plugins and their related issues were just growing quicker than they could close the old ones. I'm looking forward to us having that problem one day and I think we'll be in a good position to fix it as well (and maybe we don't wait until things get that bad but instead keep it steady with a gradual unloading of plugins to their own repos/maintainers).

Are we accounting for "core" business logic plugins, that should be separated from the rest? This is probably good material for being discussed in the next meeting.

May have partially commented on this above as well, but wanted to add an additional thought here and in the upcoming meeting!
I think the optimal recipe to decide how many/which plugins to put in their own repos is to let the community drive these decisions.
Example 1: If there's not much interest from people in being maintainers for certain plugins then we should either keep those in the main cactus repo or just straight up deprecate them if they are not really used by anyone.
Example 2: If there's 100 plugins and there are people willing to maintain some of those in separate repos, then we could break those out so that issue management/PR reviews can become easier. I also want to note here though that streamlined processes could be created with the labeling system that ensures that things go smoothly even if we reached critical mass.

@petermetz this is a great idea and very relevant - with Cactus, the deployment and management of instances of HTLCs could be automized.

@RafaelAPB Thank you very much! :-)

I would say this constitutes a business logic plugin because it implements well-defined logic using a connector/validator pair (Besu).

My take (and I'm willing to be wrong here as usual): It is closer to BLPs than let's say the connector plugins (which are clearly not BLPs) but still, one has to ask, if the HTLC plugin is a BLP, then what is the exact business use case it's implementing? And my answer to that is that there is none because it's still more of a core/generic plugin, a lower level primitive that can be used by BLPs but do not itself carry any business logic.

Now, this poses a problem in terms of organization: will we see the number of packages escalate indefinitely?

My hunch is that the number of plugins will be a function of the number of ledgers supported which (hopefully) will continue to increase indefinitely, yes, but as DLTs mature, maybe we'll reach a stable equilibrium, regarding this I'm definitely just guessing.
I have given this (specifically the plugin count) some thought in the past and concluded that eventually we'll have to start storing plugin packages in dedicated git repositories to be able to scale. A case study I can offer where this strategy was successful is the ansible project where they broke out the main repo into smaller repos (and the reason they could do it is because they also have a plugin architecture in place).
Their justification there was that at any given time there would be 2 thousand open bugs on the GH issue tracker regardless of how much effort was spent on closing them, the newly added plugins and their related issues were just growing quicker than they could close the old ones. I'm looking forward to us having that problem one day and I think we'll be in a good position to fix it as well (and maybe we don't wait until things get that bad but instead keep it steady with a gradual unloading of plugins to their own repos/maintainers).

Are we accounting for "core" business logic plugins, that should be separated from the rest? This is probably good material for being discussed in the next meeting.

May have partially commented on this above as well, but wanted to add an additional thought here and in the upcoming meeting!
I think the optimal recipe to decide how many/which plugins to put in their own repos is to let the community drive these decisions.
Example 1: If there's not much interest from people in being maintainers for certain plugins then we should either keep those in the main cactus repo or just straight up deprecate them if they are not really used by anyone.
Example 2: If there's 100 plugins and there are people willing to maintain some of those in separate repos, then we could break those out so that issue management/PR reviews can become easier. I also want to note here though that streamlined processes could be created with the labeling system that ensures that things go smoothly even if we reached critical mass.

I'm working on this, I'm currently generating end-to-end test


Problem with url generation when the fragment contains some symbols

In Language/iterating.pod6, this link  L<C<^> twigil|/syntax/$CIRCUMFLEX_ACCENT#(Traps_to_avoid)_twigil_^>
was translated (in language/iterating) to this link
https://docs.raku.org/syntax/$CIRCUMFLEX_ACCENT#(Traps_to_avoid)_twigil_$CIRCUMFLEX_ACCENT
where as the appropriate section is at  https://docs.raku.org/syntax/$CIRCUMFLEX_ACCENT#(Traps_to_avoid)_twigil_^
So either the index entries in each document must be translated, or the fragments in the url generation must be left untranslated.
I have found a few links that involve ^ that do not redirect to the appropriate section.
L<this page|/language/variables#The_^_twigil> in Language/5to6-perlvar.pod6
L<placeholder|/language/variables#The_^_twigil> in Language/control.pod6
L<.^|/language/operators#methodop_.^> in Language/typesystem.pod6
L<More information|/language/operators#infix_(^),_infix_⊖> in Language/setbagmix.pod6
I am not sure which symbols (other than ^) are being translated. So there might be more.

That's done in Documentable. It's probably better if the issue is raised there. Thanks for providing these examples.

The issue seems to have been raised here https://github.com/Raku/Documentable/issues/149 .
Should I close this ?

The issue seems to have been raised here Raku/Documentable#149 .
Should I close this ?

If you're so kind to add the examples included here as additional info, I would appreciate it.
The fact that it's not been solved is actually more convoluted than that. We don't have a principled way of generating URLs. This PR was created with that intention, but then stalled.
So having more information that can be turned into tests will certainly help. But the solution is not easy, and will not come fast, I'm afraid.

Closing this, as the issue is begin tracked here: https://github.com/Raku/Documentable/issues/149


Show Picture

User Story
As a user
I want  to see a picture of my dog
So that It is always clear which dog it is
AC

[ ] a picture that shows the dog
[ ] the picture shown on the homepage

Desig

n/Wireframe
Tasks

[ ] create a new branch
[ ] create a component for the picture
[ ] input mock picture
[ ] apply basic styling

Complexity
S

👍
Just two little typos:

So that "it" is always clear which dog it is
The "n" of Design has somehow slipped under the picture

Thanks!


[Windows 7][Desktop]: Unable to input chinese from TextFormField widget on win7 OS

Steps to Reproduce
Always fail on win7 system，win10 is ok，see the gif：

Expected results:
TextFormField input：“好的”
Actual results:
TextFormField input：“hd”

Logs

flutter doctor -v
[√] Flutter (Channel stable, 2.5.3, on Microsoft Windows [Version 10.0.17763.2183], locale zh-CN)
    • Flutter version 2.5.3 at D:\thirdsdk\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (5 days ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[!] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\Users\wujing\AppData\Local\Android\sdk
    X cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    X Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.10.4)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.10.31515.178
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2020.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[√] VS Code (version 1.61.1)
    • VS Code at C:\Users\wujing\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.27.0

[√] Connected device (2 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.17763.2183]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 94.0.4606.81

! Doctor found issues in 1 category.

When I try to reproduce this with Sogou, the candidate list disappears when a candidate is selected, but the composing text is also removed from the field (if I started typing with an empty field, it remains empty once I select a candidate). The candidate text does appear in the field while the candidate list is up.
If I use the Windows IME (PRC Simplified, "New Experience" mode), then things appear to operate correctly (although I'm far from an experienced IME user).
(Windows 7 Professional SP1)


fix directory listing

fixes an issue whereby if the length of the longest filename plus one is an integer divisor of the screen width then you would get extra lines between rows of files in the directory display

closing this as this fix will be rolled into #46


New package: BanyanArrays v0.1.0

Registering package: BanyanArrays
Repository: https://github.com/banyan-team/banyan-julia
Created by: @calebwin
Version: v0.1.0
Commit: eb9a86083ebbf3e2dafc486404f90735b9711724
Git reference: v0.1.0

I understand that the name is similar to Banyan.jl which was just published (I submitted it for publishing). I would like for any package with the prefix Banyan to have that prefix ignored in determining package similarity.
Banyan.jl is a framework for annotating existing libraries in a way that allows them to automatically scale to massive datasets and workloads. So I want to be able to publish pacakges of annotated libraries with names like BanyanArrays, BanyanDataFrames, BanyanLightGraphs, etc. Can that be made possible?


Settings gear can be cut off

Might have been caused by addition of account icon?

Main issue is fixed.
nit: Ideally instead of removing the gear's bottom margin the ... would appear then.


Linodes Grid View

Adds

Toggle between list view and grid view
Linode Card component
Distro Icon indicator
Linode specs long-format formatter
Region indicator
Presentation functions factored out from Linode List

Changes

Documentation HOC container component
Side menu width

Coverage decreased (-8.9%) to 48.76% when pulling 76b64493a7bfa164705be82ba814f7b8920057eb on asauber:M3-22-grid-view into 4696e4134b3da9e1e6a5ded574bd53251b15713b on linode:voldemort.


Refactor package scanner

Refactor the package scanner
Checks for:

if the Git Repos actually exist.
if the *.nimble file actually exist.
if the Alias relate to an existent Name.
Blacklisted tags, like nim, nimrod, etc.
Empty strings on fields.
Unwanted whitespaces on tags.
Too much tags, too few tags.
Packages with duplicated URLs.
Enforce required keys.
Maximum number of tags.
Maximum length of tags.
More precise checking of the JSON.
Other minor cases observed on the current JSON.

Other features:

Updated for Nim 0.19.0.
Everything can be Configured or Disabled from a const.
Self-documented, now nim doc works (to attract more contributions).
Works online/offline, ( when defined(ssl) it will go Online and check all repos).
Uses proper logging instead of echo.
Overall is an improvement over the previous one.

To be defined:
So this "Linter" finds more errors on the current JSON, I see 2 options:

Enable all checking, fix the JSON errors.
Disable some checking, keep the JSON with some errors.

So basically you can pick and choose on the Strictness.
Feel free to use the Suggestions feature of GitHub to suggest improvements.
:cat:

Things I see immediately: camelCase and also test shouldn't fail.
But this is great, thank you!

Tests are expected to fail, because of the mentioned imperfections on the current JSON, as explained above.
:slightly_smiling_face:

What are the next steps to get this merged?
Having a report of all issues for every package will be helpful - then each package owner can be asked to update their package. If no update is provided in a stipulated amount of time, we can then disable it.

Feel free to use the Suggestions feature of GitHub to suggest improvements.

I searched for but couldn't find the Suggestions GitHub feature.
I'll add a suggestion or idea over here instead (for now). Some kind of ongoing CI against dev and stable (and maybe stable-1) for the packages.
This might make more sense after Nim 1.0 comes out.
Some kind of auto-maintained record of "last known to be good" combination of packages and compiler versions would also be a very nice artifact to generate - I'm thinking along the lines of how Haskell's Stackage service works, and their "nightly" snapshots).
There's probably some overlap between this idea, and what the nimble.directory service already does. eg, if we look at NimBorg on there:
https://nimble.directory/pkg/NimBorg

@dom96 Can you check again please :question:
is all updated for 0.20.0 and green. :slightly_smiling_face:

We are starting to get into the infamous problem of library fragmentation that affects some other languages. I think we should encourage people not to publish tiny libraries. One way is to add a check on codebase size here or in Nimble and politely warn the developer where needed.

I understand the idea about a capitalization linter thing, and the idea about size checking,
but I think those can come on a future PR, the diff is already huge, is working and green,
so maybe merge this and more improvements can come on the future, on other PR.
:slightly_smiling_face:

@dom96 Let me know any other feedback.

We still have unresolved feedback here. Please comment on each why you disagree with me or fix it.

@dom96 Check again, let me know if you see any problem.

@dom96 Let me know if something is still missing...
:thinking:

I closed it because https://github.com/nim-lang/packages/pull/2027 is merged.


v3.8.2 tarball checksum changed?

We're attempting to update Homebrew's version of Go at Homebrew/homebrew-core#83413.
While testing the new version, CI produced the following error:
==> brew install --build-from-source baidupcs-go
==> FAILED
==> Downloading https://github.com/qjfoidnh/BaiduPCS-Go/archive/v3.8.2.tar.gz
==> Downloading from https://codeload.github.com/qjfoidnh/BaiduPCS-Go/tar.gz/v3.8.2
Error: SHA256 mismatch
Expected: 3f6c95b82a769fb7c947a181d8f57ae60344acabba0a27a33249b9abbf365601
  Actual: 65d5482bc2a82cb244b978b8e1369bd5b1c429afce74651e5aea28e057a78ae3

I can update the sha256 associated with BaiduPCS-GO, but CI will come back to me with the following error:
baidupcs-go:
  * stable sha256 changed without the url/version also changing; please create an issue upstream to rule out malicious circumstances and to find out why the file changed.

Can I confirm that the change in checksum was intentional? Thanks.

This seems to have been addressed in #102, but it'd help to get confirmation in case I did Google Translate wrong 🙂

Yes, you're right, the owner replaced the 3.8.2 with a new package.

Thanks! Was there a problem with the original version of 3.8.2? i.e. should users who installed the earlier one update to the newer one?

It's about a serious bug in upload function, so update, I suggest.

Ok, thanks again!
By the way, it'd be very helpful for your downstream package managers for you to not re-publish tags after they've already been released. Bug fixes should ideally be reflected by a new version. See the Git docs for a discussion of this -- they actually have some pretty strong words about it.


winget list should be able to show hidden apps

Description of the new feature/enhancement

A minor issue (major if sysadmin) with the current implementation of winget list is that it does not show manually hidden apps from the program install list. Programs are hidden officially using the registry via installers and manual tweaking, but they can also be hidden manually by the user using Hide from Uninstall List and similar programs.
i.e.

Hidden programs cannot be upgraded as of the current version of winget.
Ideally programs should be visible via winget list regardless of status (shown/hidden), or at the very least visible when combined with a flag (winget list -hidden) or winget is run as an admin.
Additionally, it would be nice to have the ability to toggle the visibility of apps from winget.
Proposed technical implementation details (optional)

Previous comment from @ecovio1
a -hidden flag will be nice from a running as admin shell.

AFAIK, this is mostly done per app basis via
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall
or
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

under a program folder ,
creating a new dword value , where Value Name is SystemComponent and Value Data is 1.
or manually renaming the program's DisplayName key to anything else random.

or hiding the whole "Programs and Features page" completely per user basis
from GPolicy>User Configuration > Administrative Templates > Control Panel > Programs.

[Policy] Command-List


Add version cli option to the linter

Resolves #80

Add command line option to the linter to display the version declared in the package.json.
Also added .editorconfig to allow for consistent code style with the rest of the code base.

Additional Question:
I used NPM 5.3.0 which now generates a package-lock.json and suggests you should commit it to the repo. I have not as of yet, but can do if you like.
Testing

All existing tests pass
Tested locally by running the following commands:
node ./bin/dockerfilelint -v : Shows the version in package.json
node ./bin/dockerfilelint -version : Shows the version in package.json
node ./bin/dockerfilelint --help : Shows help with the new version cli option included (see below)

Usage: dockerfilelint [files | content..] [options]

Options:
  -o, --output   Specify the format to use for output of linting results. Valid
                 values are `json` or `cli` (default).                       [string]
  -j, --json     Output linting results as JSON, equivalent to `-o json`.   [boolean]
  -v, --version  Show version number                                        [boolean]
  -h, --help     Show help                                                  [boolean]

Examples:
  dockerfilelint Dockerfile         Lint a Dockerfile in the current working
                                    directory

  dockerfilelint test/example/* -j  Lint all files in the test/example directory and
                                    output results in JSON

  dockerfilelint 'FROM latest'      Lint the contents given as a string on the
                                    command line

  dockerfilelint < Dockerfile       Lint the contents of Dockerfile via stdin

Coverage remained the same at 99.156% when pulling 40740b10ffb30ded57a5a2f6dfac4f009788247f on TheYorkshireDev:AddVersion into 2976eaa837f39c5a5c716a82eaab562f2c8725fb on replicatedhq:master.

Coverage remained the same at 99.156% when pulling 40740b10ffb30ded57a5a2f6dfac4f009788247f on TheYorkshireDev:AddVersion into 2976eaa837f39c5a5c716a82eaab562f2c8725fb on replicatedhq:master.

@nexdrew @marccampbell Hi guys do you mind looking at this PR?

@TheYorkshireDev Sorry for the long delay! Looking into this now.

@TheYorkshireDev Merged with #87. Thanks for the contribution!


Runpod - How to add Lora without link in Stable Diffusion ?

In folders - where do we need to upload the LORA files ? I want to add multiple LORAs - Can someone clearly define the path to the LORA adding folder ?
I went in extentions and added there but it doesn't show up when I run SD webui.
Please help.

the lora folder is /workspace/sd/stable-diffusion-webui/models/Lora

the lora folder is /workspace/sd/stable-diffusion-webui/models/Lora

Thanks so much Ben :)

the lora folder is /workspace/sd/stable-diffusion-webui/models/Lora

Hi Ben - When I load the models in this folder they dont show up in the webui. Only when I put a drive link in Lora "link", it shows in the webui after loading. And in the Lora link - i can put only one link right ? is there a way i can add more links in the Lora link part so it loads multiple Loras ?

the lora folder is /workspace/sd/stable-diffusion-webui/models/Lora

Hi Ben - When I load the models in this folder they dont show up in the webui. Only when I put a drive link in Lora "link", it shows in the webui after loading. And in the Lora link - i can put only one link right ? is there a way i can add more links in the Lora link part so it loads multiple Loras ?

Anyone can help on this please ?

Make sure you're putting the lora inside the right folder, use a link first, then check the right folder where it was downloaded to, then use that folder for other loras

Yes i did use the right folder and the after I upload the additional Lora - it doesn't show up in the Sd webui - am I supposed to restart the webui or something like that ?

yes, try restarting

I refreshed the webui page but it doesnt show...Do i run the code from start to restart ? wont the loaded loras go away then ?

So I loaded the Lora in the same folder but when I refresh then the new LORA doesn't show in the webui.
I also tried refreshing the link. Also tried running the code from the Lora part and the Load Model part but it doesn't run. When I do that then nothing loads so I have to end the pod and then restart the whole procedure to get it running with only one Lora as earlier.
Is there any way I can add multiple Loras by putting the links of the drive there so it automatically loads up in the Lora folder ?


CI build and release pipelines

What is the goal of this PR?
We added CI build and release pipelines and checkstyle tests.
What are the changes implemented in this PR?

Add .factory/automation.yml
Add checkstyle_tests across the repo, and checkstyle coverage test
Add build, deploy-crate-snapshot, deploy-github and deploy-crate-release CI jobs
Add dependency-analysis in CI

Do NOT merge until typedb-protocol is updated to @vaticle


Formatting issues in the docs

This is a list of things to fix in the documentation

[x] Links in the notebooks
[x] Find out how the api should really be documented (modules?)
[x] Some legal stuff somewhere?
[x] Links to how to get a Gurobi license
[ ] Format links to gurobipy things and other python packages in the same way
[x] Output of gurobi in the notebooks (there's an ugly trick now...)
[x] Explicitely mention supported versions of sklearn/tensorflow/pytorch

I really can't see anyway to have a consistent way of formatting intersphinx links and our links


Analyze if Task is neither awaited nor returned

See #4: this PR adds the ability to check for statements invoking an asynchronous method without await or return.
It contains the following changes:

Port the existing plugin so that it follows the official JetBrains template. This enables easier local debugging and build simplifications.
The new MissingAwait analyzer
GitHub actions CI and Release

Reviewing may be easier if the port to the official template and the added functionality were two distinct PRs.

push @avonwyss


Added mcu variants in defines

Hi,
Checked with Microchip Studio 7, added the relevant mcus variants. Just in case someone wants to use those .
regards,

Thank you.  I'm going to add the NRWWSTART information to the compiler in cpuinfo.pas as the bootstart value.  However this information is still required for the 3.2.x series compiler.


On restarting a headless server with an existing world no world is retrieved from the game manifest

What you were trying to do
Test something unrelated, by which I ended up restarting a headless server.
What actually happened
The restart failed to bring the game server back up
How to reproduce

Start a headless server with any config (like just starting the headless run config in IntelliJ)
Stop the server (can potentially skip steps 1 & 2 if you can reproduce with an existing save)
Start the server again

On InitialiseWorld line 100 the failure occurs. The gameManifest loads but has no entries in its worlds list
Log details and game version
Latest develop
16:48:21.601 [main] INFO  o.t.w.c.b.ExtraBlockDataManager - Extra data slots registered:
16:48:21.604 [main] ERROR o.terasology.engine.TerasologyEngine - Uncaught exception, attempting clean game shutdown
java.lang.NullPointerException: null
	at org.terasology.engine.modes.loadProcesses.InitialiseWorld.step(InitialiseWorld.java:101)
	at org.terasology.engine.modes.StateLoading.update(StateLoading.java:243)
	at org.terasology.engine.TerasologyEngine.tick(TerasologyEngine.java:458)
	at org.terasology.engine.TerasologyEngine.mainLoop(TerasologyEngine.java:421)
	at org.terasology.engine.TerasologyEngine.run(TerasologyEngine.java:397)
	at org.terasology.engine.Terasology.main(Terasology.java:145)
16:48:21.604 [main] INFO  o.terasology.engine.TerasologyEngine - Shutting down Terasology...

Theory
Either the game isn't correctly saving the world in the first place or the game manifest isn't correctly figuring out where the actual world went so it can list it. Might relate to some of the multi-world changes, although that was a few months ago. Since it works fine the first time you launch a headless server maybe we somehow missed it this long.
Also works partially with a client/server hosting a fresh game, exiting, then re-hosting. No crash, although when I tried it the client loaded into a black screen with no world visible (did have toolbar items etc)

Never mind! Looks like this is already fixed via #3534! Thank you @fishfred! :-)


parameter sizes not checked in log_density_gradient

The log_density_gradient function doesn't check we get the right number of parameters in a call.
Here's a simple reproducible example.
bs.stan
parameters {
  vector<lower=0, upper=1>[2] alpha;
}

Running it with too small, just right, and too large array of parameters:
import bridgestan as bs
import numpy as np
model = bs.StanModel('bs.stan')
lp1, grad1 = model.log_density_gradient(np.array([0.3]));
lp2, grad2 = model.log_density_gradient(np.array([0.3, 0.5]));
lp3, grad3 = model.log_density_gradient(np.array([0.3, 0.5, 0.1]))
print(f"{lp1=} {lp2=} {lp3=}")
print(f"{grad1=} {grad2=} {grad3=}")

No errors, just this output, which looks like it ignores extra parameters and treats missing parameters as having value 0.
>>> print(f"{lp1=} {lp2=} {lp3=}")
lp1=-2.795004850056945 lp2=-2.8568644572972675 lp3=-2.8568644572972675

>>> print(f"{grad1=} {grad2=} {grad3=}")
grad1=array([-0.14888503,  0.        ]) grad2=array([-0.14888503, -0.24491866]) grad3=array([-0.14888503, -0.24491866])

I think it'd be useful to check input size here.  This came to my attention as a bug in someone's code they were showing me that BridgeStan didn't catch.

Correct, the only sizes we currently check are on output parameters, not inputs.
The checks are easy to add, but do lead to a performance cost that all users would have to pay

We could add an input check behind a flag which allows the performance oriented to disable the check, ya?

If you're the kind of user who cares about disabling the input check, the cost of simply branching to decide whether or not that check gets run probably bugs you. I've seen people provide foo and foo_unchecked for this purpose, but of course that increases your API surface

Is the cost of checking the input length really something that matters in any circumstances? That should be many orders of magnitude smaller than any logp evaluation anyway?

Is the cost of checking the input length really something that matters

It can.  Branch point misprediction is really hard on cache.  And we're talking about Python here.  It'd be nice if we could provide branch point prediction hints like we can in C++, because we don't care about the cost on failure.
@WardBrian:  Is this an issue because our C++ class doesn't check the length of its input?  I know it reads it like a stream, so I was at least expecting an error when it was too small.

It just gets a double* pointer. We could also pass the length if we wanted to "check" in C++ (I use the scare quotes because of course there's no way to be sure said number is actually the size of the buffer once we're down there)
What it does when it's too small will be system dependent. You might read zeros, uninitialized memory, or segfault.
I'm trying to time the difference now. If it's in the single digit percents it is probably worth doing unconditionally

The density can be arbitrarily expensive, so you can drive this down to whatever fraction you want based on model size.  So it'd be interesting to test the impact on the smallest possible unidimensional normal example, I think.


Add fix for get si npe

@shawn-hurley and I discovered a panic this morning. If for some reason the catalog has a bunch of instances that the broker is unaware of, the broker will try to lookup the instance, fail to find it, and panic when trying to deref the spec off a nil value. This correctly checks the error.

Pretty soon we can start to write tests for the broker if we want. We have mocked for dao and we just need to figure out the mocks for apb.Executor/async engine. Just a thought for later