different editor briefly flashes when debugging

@isidorn this fix (and its followups) look buggy to me
Am I mistaken or is this whats happening: clearThreads reset thread's stopped to false, focusStackFrame then goes ahead and looks for thread with stopped=true, doesnt find current thread anymore (because cleared) and thus briefly removes focus from the current thread, leading to this:

(follow up of #128415)

@gregg-miskelly how does this not happen to Visual Studio? Is there some heuristic on top? Or maybe it happens, but users are not hitting it?
Since this is the problem I outlined in this comment here https://github.com/microsoft/vscode/issues/125144#issuecomment-869641057
To solve this I can introduce a timeout before I move focus to another thread, so that fast stepping would not switch quickly like in the GIF above.

To make sure I understand, is this what is going on?

The user is debugging two processes
Process A is already stopped
A breakpoint is hit in process B
The UI immediately switches focus to process B
The user hits step
The UI switches focus back to process A
The debug adapter sends a stop event for the step completing in process B
The UI switches back to process B

In VS step 4/8 wouldn't happen - if the UI is already stopped, and a new stopping event comes in, that stopping event is queued. So instead when the breakpoint is hit, focus would stay on process A. If you didn't want to be on process A any more, the user can hit continue (or manually switch to process B), and then we would dequeue the stopping event.

The problems happens when debugging a single process with multiple threads.
When a breakpoint is hit, all threads are paused correctly.
When then singlestepping the breaked thread, onDidContinue handler resets thread's stopped bool to false in clearThreads
and then calls focusStackFrame.
The problem is that focusStackFrame searches for threads with paused=true (in getStackFrameThreadAndSessionToFocus) and doesnt find current thread anymore (because stopped bool was just reset).
(Atleast this is my understanding)

Got it. And the behavior of whatever debug adapter you are using is to break these additional threads and leave them paused after continuing the stepping thread?
Assuming that is correct: VS doesn't have a quite analogous scenario to this -- in our scenarios, the background threads would get resumed at the same time as the stepping thread. Off hand, I would guess the best behavior would be to either delay or entirely avoid swapping stack frames if there are no queued events. In other words, make the user manually select a new thread, or only automatically swap threads if say 2 seconds have elapsed without a new stopping event.

Yes, timeout should fix it, but I'm wondering if changing the order of calls in onDidContinue is also valid. Atleast it fixes the issue for me:
diff --git a/src/vs/workbench/contrib/debug/browser/debugSession.ts b/src/vs/workbench/contrib/debug/browser/debugSession.ts
index 0ca0de841ed..2d47b3c0d5c 100644
--- a/src/vs/workbench/contrib/debug/browser/debugSession.ts
+++ b/src/vs/workbench/contrib/debug/browser/debugSession.ts
@@ -949,8 +949,6 @@ export class DebugSession implements IDebugSession {
 				this.cancelAllRequests();
 			}

-			this.model.clearThreads(this.getId(), false, threadId);
-			this._onDidChangeState.fire();
 			// If there is some session or thread that is stopped pass focus to it
 			if (this.debugService.getModel().getSessions().some(s => s.state === State.Stopped) || this.getAllThreads().some(t => t.stopped)) {
 				if (typeof threadId === 'number') {
@@ -967,6 +965,9 @@ export class DebugSession implements IDebugSession {
 					}
 				}
 			}
+
+			this.model.clearThreads(this.getId(), false, threadId);
+			this._onDidChangeState.fire();
 		}));

 		const outputQueue = new Queue<void>();

Thanks a lot for the information and ideas.
I decided to go with a 800ms timeout, so only if the stop  event does not happen in 800ms we would pass the focus. I tried this out and it works fine for me. Try it out and let me know how it goes.

30d73ea fixes the problem for me. Thanks.

Great, thanks. Adding verified label.


Storage overridden unexpectedly

Hi,
I have an issue where everything was working fine but then, I added a third property to include in the sessionStorage. Instead of just adding it to the ones already there, anytime this third property is modified, the whole sessionStorage is cleared and only the third property is inside.
Here are my options (I don't show you the store's data because it is HUGE)

Here is my sessionStorage before a change occurs to pagesConfig. Notice that only the 2 first include elements are present.

Please provide more details to reproduce the issue. Thanks.

Sorry, I posted the issue with only Hi in it because of a bad shortcut. You've been to quick to jump on it 😅

Please provide more details to reproduce the issue. Thanks.

It would take me at least 1 hour to put up a minimal repo to reproduce the issue. I was expecting someone to have run into it and found a solution. For some context, I use that store with react's useContext to pass props to the store for initial values.
If I can't get any help, I'd rather spend time trying to find a workaround by myself than to create a mini repo that wouldn't necesseraly lead to a solution. Thanks anyway.

Alright. After some more digging, it ended up being quite simple. Whenever you use the set() method from Zustand, you have to set all the properties you keep in storage. Otherwise you'll just override it everytime with only the property that you changed.
For example:
set({name: newName, age: get().age})
// or
set({age: newAge, name: get().name})
// if the other property is an object, you have to spread it into a new one
set({age: newAge, details: {...get().details}})

Alright. After some more digging, it ended up being quite simple. Whenever you use the set() method from Zustand, you have to set all the properties you keep in storage. Otherwise you'll just override it everytime with only the property that you changed.
For example:
set({name: newName, age: get().age})
// or
set({age: newAge, name: get().name})
// if the other property is an object, you have to spread it into a new one
set({age: newAge, details: {...get().details}})


Create Virginia Community Colleges

@gekson This domain is blacklisted because the college allows to register an email address there even if you are not a student of the college. If you are the student of this college, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


ENH: Notebook Level Cache Task Runner

It would be nice to have a notebook level cache mechanism that tracks a hash of each In cell and stores them in order within the notebook metadata. This way we could skip execution for cells that have already run with no content change, and if a cell has changed then run all remaining cells.
this could be useful to others and is probably better as a separate project -- but could work on it here first.

@AakashGfude does the Execute processor in nbconvert allow for cell level interactions?

With the sphinx cache this kind of mechanism wouldn't offer much improvements except for very long running notebooks (with edits towards the end of the notebook). I am going to close this issue. It could be useful as a independent project.


Modify test folder

/retest

/retest

/retest

/test manila-operator-build-deploy-kuttl

The good part is that I see now the scale tests running! @gouthampacha I suspect @vhariria found the reason they were not executed!
The bad is that the test is failing [1], looks like we missed something in the 02-assert but I have to check it better
Deployment:manila-kuttl-tests/manila-api: .spec.selector.component: key is missing from map
[1] https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openstack-k8s-operators_manila-operator/135/pull-ci-openstack-k8s-operators-manila-operator-main-manila-operator-build-deploy-kuttl/1704586703257210880/artifacts/manila-operator-build-deploy-kuttl/openstack-k8s-operators-kuttl/build-log.txt

@fmount thanks for your feedback. Ack, the failures are resulted from moving the 02-x tests. These tests previously  passed in local environment.  I will update the assert, retest and update the PR as needed.

Force merging this patch as it has been already tested locally, CI is green and tempest is expected to be red until the new openstack-operator changes related to the Routes creation land.


Upcoming - release jsoup 1.14.1

I'm looking to transition my code away from the Whitelist class, to the Safelist class, which was introduced in jsoup 1.14.
More info in the Whitelist class: https://jsoup.org/apidocs/org/jsoup/safety/Whitelist.html
My code uses Maven to manage its dependencies, and the newest version of jsoup available to Maven seems to be 1.13: https://mvnrepository.com/artifact/org.jsoup/jsoup
What's the process for updating the Maven repository with a newer version of jsoup?

Hi Kevin, sorry about the confusion. 1.14.1 has not yet been released, and so that's why it's not yet in Maven.
I was rebuilding the jsoup.org site and javadocs (to fix the docs for mobile support) and that now shows the upcoming version.
Looking to release 1.14 soon (this week or so), externalities permitting.

Hi Kevin, sorry about the confusion. 1.14.1 has not yet been released, and so that's why it's not yet in Maven.
I was rebuilding the jsoup.org site and javadocs (to fix the docs for mobile support) and that now shows the upcoming version.
Looking to release 1.14 soon (this week or so), externalities permitting.

Thanks for the reply! No rush on my account, I just wanted to make sure I wasn't missing anything. Feel free to close this out, and I'll patiently wait for the new release. Thanks again!

Thanks for the reply! No rush on my account, I just wanted to make sure I wasn't missing anything. Feel free to close this out, and I'll patiently wait for the new release. Thanks again!

Regarding this code repository, is there an easy way available to find out what bugs are expected to be fixed in the upcoming release?

I was rebuilding the jsoup.org site

Just in case .. don't forget https://jsoup.org/cookbook/cleaning-html/whitelist-sanitizer!
In any case .. thank you very much for keeping Jsoup up to date :)

Is 1.14.1 being released soon?
I have been using 1.13.1 but just ran into a bug that is fixed in 1.14.1 so I'd love to upgrade:
https://github.com/jhy/jsoup/issues/1410
NPE that results when calling Element.toString() for an Element that is from Element.clone()
Thanks!

Sorry to add to the list of nagging requests, but we're hoping to adopt JSoup yet and specifically need to expose the Whitelist/Safelist as public API, so we're waiting for 1.14.1 (even a snapshot) availability in the Maven repository. Is there a timeline for this release, or blocker(s) preventing it?
Thank you!

Hi all -- wanted to let you know that I've just released jsoup 1.14.1 and it's available now.
Details at https://jsoup.org/news/release-1.14.1
Sorry it took so long -- I kind of jinxed myself with "externalities permitting" :/


ODBC 13.1 driver broken on Mac?

I followed the instructions on this page to install the 13.1 driver, including symlinking the odbcinst.ini and odbc.ini files into /etc.  However, I still get the following error when trying to use the driver from a Python script:
pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open lib '/usr/local/lib/libmsodbcsql.13.dylib' : file not found (0) (SQLDriverConnect)")

Here is my odbcinst.ini file:
[ODBC Driver 13 for SQL Server]
Description=Microsoft ODBC Driver 13 for SQL Server
Driver=/usr/local/lib/libmsodbcsql.13.dylib
UsageCount=1

The dylib file itself is there.  However, most of the dependencies seem to be broken:
% otool -L /usr/local/lib/libmsodbcsql.13.dylib
/usr/local/lib/libmsodbcsql.13.dylib:
	/usr/local/opt/msodbcsql/lib/libmsodbcsql.dylib (compatibility version 1.5.0, current version 1.9.2)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1259.11.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1)
	/usr/local/lib/libodbcinst.2.dylib (compatibility version 3.0.0, current version 3.0.0)
	/usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos (compatibility version 5.0.0, current version 6.0.0)
	/usr/lib/libcurl.4.dylib (compatibility version 7.0.0, current version 8.0.0)
	/usr/local/opt/openssl/lib/libssl.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
	/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 120.1.0)

% ls -alh /usr/local/opt/msodbcsql/lib/libmsodbcsql.dylib
ls: /usr/local/opt/msodbcsql/lib/libmsodbcsql.dylib: No such file or directory
% ls -alh /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
ls: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation: No such file or directory
% ls -alh /usr/lib/libSystem.B.dylib
ls: /usr/lib/libSystem.B.dylib: No such file or directory
% ls -alh /usr/local/lib/libodbcinst.2.dylib
lrwxr-xr-x  1 craven  admin    50B Nov  1 08:51 /usr/local/lib/libodbcinst.2.dylib -> ../Cellar/unixodbc/2.3.9_1/lib/libodbcinst.2.dylib
% ls -alh /usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib
ls: /usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib: No such file or directory
% ls -alh /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
ls: /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos: No such file or directory
% ls -alh /usr/lib/libcurl.4.dylib
ls: /usr/lib/libcurl.4.dylib: No such file or directory
% ls -alh /usr/local/opt/openssl/lib/libssl.1.0.0.dylib
ls: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib: No such file or directory
% ls -alh /usr/lib/libiconv.2.dylib
ls: /usr/lib/libiconv.2.dylib: No such file or directory
% ls -alh /usr/lib/libc++.1.dylib
ls: /usr/lib/libc++.1.dylib: No such file or directory

Any ideas?

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

ID: 1c0de6fb-19ae-ff6f-8e73-ce66fa94bd64
Version Independent ID: 34edd099-f4fe-4ac3-cdd4-abc87b35270b
Content: Install the Microsoft ODBC driver for SQL Server (macOS) - ODBC Driver for SQL Server
Content Source: docs/connect/odbc/linux-mac/install-microsoft-odbc-driver-sql-server-macos.md
Product: sql
Technology: connectivity
GitHub Login: @David-Engel
Microsoft Alias: v-daenge

@jmorrey - Thank you for your question. I would ask over in the GitHub repo for the Homebrew install formula for the driver:
https://github.com/Microsoft/homebrew-mssql-release
Someone there should be able to help you troubleshoot.
Regards,
David

@jmorrey -- Jon, thank you for your question.
@David-Engel -- David, thank you for clarifying.
I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.


New example with hooks instead of mappings.

Hi @tlian7 @hblasins @DavidBrainard @wandell.
We spoke recently about working on a new example that will address some confusing aspects of RenderToolbox4, especially around "remodeler" hook functions vs mappings.
If you're game, I'd like to manage that work with this issue.  I propose:

you could make a branch with the scene and script you have so far
I could check it out and help with debugging and commenting
we could iterate like that a few times
when we all like the example, we could make a PR and merge the branch into master

How does that sound?

Hi @benjamin-heasly,
This sounds like a great idea. I've done the following:

Created a branch in RTB4 called MoreExampleScenes.
Added three example scenes that I've been working on:

SponzaAtrium: Renders an atrium with different area light spectra and different camera types.
CrytekSponza: Renders a fancier version of the atrium at three different camera positions.
MaskAndBumpTest: Renders a simple vase in order to test the changes I've made in mPbrt that recognize opacity/mask textures and bump maps.

For the most part these scenes render for me and do the various things that I want them to do (i.e. move the camera around, rotate the light, etc.) but it would be nice to know if they render for you and if the workflow makes sense. Note: These scenes require the changes I made in a separate branch of mPbrt in order to read in the opacity and bump maps from the OBJ files.
I believe that @hblasins also has a few scenes he would like to share.

Hi @benjamin-heasly, @tlian7
I've added a scene of my own (Car) to the branch MoreExampleScenes. This model uses .TAG files, which you can now convert to .EXR if you checkout mPbrt branch exrFix, where I added this functionality.
In this example I'm trying to render a car with and without the taillights on. Unfortunately however promotion to area lights in PBRT does not work for both taillights, one seems to be fine but the other is no. I think the problem lies in some of the surface normals being flipped. I don't know when and how this is happens, as the mesh imported into Blender looks OK.

@tlian7 @hblasins -- Sweet.  These should be nice.
So I think the first thing we should do is resolve your pull requests in the other repos.  That will make it easier to play along here and try things out.
I'll go to the other repos now and make some comments.


[gtjPFvMD] Fix coll support for lists coming from Nodes or Rels.

Fixes arrays not being treated as lists in coll.elements as expected.

@Lojjs yeah it was :)


Provide a specific error for synch failed due to KongConsumers with the same username, or make the creation fail

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
When adding two or more KongConsumers with the same username field, the configuration synching blocks and prevents you from applying any further changes, but logs don't tell you what's the actual issue:
2023-11-23T08:42:00Z    error   Failed parsing resource errors  {"url": "https://<IP_ADDRESS>:8444", "update_strategy": "InMemory", "error": "could not unmarshal config error: json: cannot unmarshal object into Go struct field ConfigError.flattened_errors of type []sendconfig.FlatEntityError"}
2023-11-23T08:42:00Z    error   dataplane-synchronizer  Could not update kong admin     {"error": "performing update for https://<IP_ADDRESS>:8444 failed: failed posting new config to /config: got status code 400"}

Proposed Solution
Maybe something like this showing up in controller logs:
[...]
[timestamp]    error   Cannot have username shared between different KongConsumers [user-consumer1, user-consumer2]

Or avoid it a priori (but I don't think it's possible):
kongconsumer.configuration.konghq.com/user-consumer1 created
kongconsumer.configuration.konghq.com/user-consumer2 creation failed (username already existing)

Or even automatically deleting the last one
Additional information
Steps to Reproduce

Minikube cluster setup:

minikube start --driver=docker
minikube tunnel

CRDs installation:

kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.0.0/standard-install.yaml

echo "
---
apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
  name: kong
  annotations:
    konghq.com/gatewayclass-unmanaged: 'true'

spec:
  controllerName: konghq.com/kic-gateway-controller
---
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: kong
spec:
  gatewayClassName: kong
  listeners:
  - name: proxy
    port: 80
    protocol: HTTP
" | kubectl apply -f -

Kong installation:

helm repo add kong https://charts.konghq.com
helm repo update
helm install kong kong/ingress -n kong --create-namespace

Create 2 consumers with the same username:

echo "apiVersion: configuration.konghq.com/v1
kind: KongConsumer
metadata:
 name: user-consumer1
 annotations:
   kubernetes.io/ingress.class: kong
username: user
---
apiVersion: configuration.konghq.com/v1
kind: KongConsumer
metadata:
 name: user-consumer2
 annotations:
   kubernetes.io/ingress.class: kong
username: user # Same username of user-consumer1
" | kubectl apply -f -

Watch logs:

kubectl logs -n kong -f <kong_controller_pod>

Kong Ingress Version
KIC Release: 3.0.0
Kubernetes Version
Client Version: v1.27.3
Kustomize Version: v5.0.1
Server Version: v1.26.3
Note
I know it should be obvious that 2 users cannot share the same username, but I spent hours trying to figure out what was the issue, because I have many YAML files and the error appeared a little generic to me. Maybe something like an additional line of log addressing the specific issue could be helpful
Acceptance Criteria

[ ] As a user, I'd like to know, just by looking at the controller logs, that I have 2 KongConsumer resources with the same username

Thanks for your report.
The below not helpful log mentioned by you
2023-11-23T08:42:00Z    error   Failed parsing resource errors  {"url": "https://<IP_ADDRESS>:8444", "update_strategy": "InMemory", "error": "could not unmarshal config error: json: cannot unmarshal object into Go struct field ConfigError.flattened_errors of type []sendconfig.FlatEntityError"}
2023-11-23T08:42:00Z    error   dataplane-synchronizer  Could not update kong admin     {"error": "performing update for https://<IP_ADDRESS>:8444 failed: failed posting new config to /config: got status code 400"}

is a result of a bug in Kong Gateway. It's been reported FTI-5584. The status of it will be updated in this GitHub issue.
This wrong error message is returned only for Kong run in DB-less mode. In such case endpoint /config?flatten_errors=1
is used (option flatten_errors=1 makes an error easily parsable) and it misbehaves.
For Kong in DB mode, everything works as expected the below is logged in such case
2023-11-23T14:58:53+01:00       error   dataplane-synchronizer  Could not update kong admin     {"error": "performing update for http://<IP_ADDRESS>:8001 failed: building state: inserting consumer by username test-consumer-1: entity already exists"}

which is much more useful.
After the fix in Kong Gateway something similar will be logged for Kong run in DB-less mode too.

Kong Gateway team works on it

https://github.com/Kong/kong/pull/12167

the version of Kong Gateway that contains that fix will provide proper message when used with KIC


add check for active venv to shell scripts

Description: Add a check for existing active virtualenvs to shell scripts. This allows for users to create their own workspace for us to utilize.
Risk Level: Low
Testing: Manual runs
Docs Changes: N/A
Release Notes: N/A

Thanks for the review @htuch. I updated based your feedback. Mind taking another pass?


Set Carthage Swift version to 4.2 (Swift 4 + 5 compatibility)

Description
Update the Swift version to 4.2 in the Carthage support Xcode project
Motivation and Context
The current Xcode project specifies Swift 3. This will be incompatible with Swift 5 being released shortly in Xcode 10.2.
By specifying Swift 4.2, swift-html-entities will be compatible with both Swift 4.2 and Swift 5.
How Has This Been Tested?
Carthage build using Xcode 10.1 and Xcode 10.2 beta 3 as the set toolchains.
After reading below I will get a CLA form signed shortly!
Checklist:

[x] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

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

@djones6 Have any thoughts on this? That license CI step is stuck at yellow, not sure how to kick that over.

Not sure but I've merged for you! Thanks for the PR.


BUG: Chocolatey ".exe" replace doesn't work on ".EXE"

This should be a simple fix

Fixed in 3471a3bb1a48255ed2d0cfad2d053a415595ffdc


Improve permissions list accessibility

Permissions list was confusing for screen reader users
This PR:

fixes heading hierarchy (used to be H1, H3)
adds a heading for permissions
uses the Design System Summary List component - the recommended component for name value pairs, instead of ul (without role="list" nothing is announced for Safari/Voiceover)
uses text instead of images

Before:

After:

closed in favour of #1363


OOMKilled because of chart memory limit

I dont have the source code for Logdna Agent Helm Chart to refer to in this repository. Therefore, here are some of the steps to reproduce the problem:

Use helm pull logdna/agent. Optionally, --untar can be set to true so that the chart is downloaded to a folder
Open that folder, go to values.yaml file.

The default limit for memory is a bit underwhelming. I appreciate the ability to run logdna agent with minimal resources (as documented in here https://github.com/logdna/logdna-agent-v2/blame/master/docs/README.md#L258). However, inside the chart, the default limit is just 75Mi, which leaves logdna OOMKilled all the time (at least with our use-case)
Luckily we still have the ability to customise it without having to fork the chart, but setting a limit at 75Mi ruins the experience since following the steps over here (https://github.com/logdna/logdna-agent-v2/blob/master/docs/HELM.md) will never work if that values is not changed.
I propose changing it to request, instead of limit. Would love to make a pull request, but no source for the chart is available so I open this issue. Hopefully my concern makes sense

Per https://github.com/logdna/logdna-agent-v2#resource-limits, the memory limit is highly variable and dependent on your particular environment. An uncapped memory limit will probably not be desirable by most users so I don't think that it makes sense to remove it and just rely on the memory request parameter.
@c-nixon I see that in the above section it mentions that the agent requires at least 128 MiB, but the default in helm https://github.com/logdna/logdna-agent-v2/blob/master/docs/HELM.md#configuration is 75 MiB; can we bump that up to 128 MiB to at least be consistent?

Thanks for the feedback @jakedipity . I will close this issue since there are no further question or comment


Compatibility Symfony 5.4

Hi,
I have upgraded my project to SF 5.4. I'm using saad-tazi/g-chart-bundle version 4.0.0. It works but I have such warnings after composer install :
Class SaadTazi\GChartBundle\Tests\Chart\DataTableTest located in ./vendor/saad-tazi/g-chart-bundle/SaadTazi/GChartBundle/Tests/DataTable/DataTableTest.php does not comply with psr-0 autoloading standard. Skipping.
Class SaadTazi\GChartBundle\Tests\Chart\DataColumnTest located in ./vendor/saad-tazi/g-chart-bundle/SaadTazi/GChartBundle/Tests/DataTable/DataColumnTest.php does not comply with psr-0 autoloading standard. Skipping.
Class SaadTazi\GChartBundle\Tests\Chart\DataCellTest located in ./vendor/saad-tazi/g-chart-bundle/SaadTazi/GChartBundle/Tests/DataTable/DataCellTest.php does not comply with psr-0 autoloading standard. Skipping.
Class SaadTazi\GChartBundle\Tests\Chart\DataRowTest located in ./vendor/saad-tazi/g-chart-bundle/SaadTazi/GChartBundle/Tests/DataTable/DataRowTest.php does not comply with psr-0 autoloading standard. Skipping.

Any solution ?

Hi @cbeyer ,
It's being a long time I last used PHP and I am no longer using this bundle. If you or someone else find a solution to those warnings, please feel free to open a PR and I'll merge it.
Sorry for not being more helpful.


HOD profile: relax requirement to only form satellites when centrals are present

In the current implementation of the HOD profile, satellites can only form when centrals are present. Although mostly true, this assumption breaks in the case of (recent) mergers or smaller clusters.
Following arXiv:1909.09102 I've introduced the boolean parameter ns_independent in HaloProfileHOD which relaxes this assumption.
In essence, when ns_independent==True the satellite contribution is not multiplied by N_c (which is a smoothed step function).

The result of this, in reference to the cluster mass M is:

When M < Mmin_0 the real and fourier -space profiles are not zero anymore. (After all, there is some mass somewhere in there!)
When M > Mmin_0 the real and fourier -space profiles of an HOD instantiated with ns_independent=True are equal to an HOD instantiated with ns_independent=False.
When M = Mmin_0 due to how the heaviside function is defined in numpy, the independent case has 2x the power of the dependent case (minus 0.5).

This, too, should now be ready for merging once the checks are completed.

Pull Request Test Coverage Report for Build 899062214

10 of 12 (83.33%)  changed or added relevant lines in 1 file are covered.
32 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.08%) to 96.678%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pyccl/halos/profiles.py
10
12
83.33%

Files with Coverage Reduction
New Missed Lines
%

pyccl/boltzmann.py
10
94.07%

pyccl/core.py
22
95.91%

Totals

Change from base Build 726854113:
-0.08%

Covered Lines:
3754

Relevant Lines:
3883

💛  - Coveralls

@damonge COVERALLS is correctly picking up that I am not testing the fourier_variance method of HOD for ns_independent=True. Could you confirm that the implementation is right? I'll add it to the unit test later.


ERC721 endpoints for WH.

issueERC721Property
issueERC721Token
transferERC721Token
deleteERC721Token

:tada: This PR is included in version 1.0.0 :tada:
Your semantic-release bot :package::rocket:


kettle tweaks

About the PR

removed OrGate since i think it was breaking ci even tho its migrated???
removed (hopefully) all the funky components that shouldnt be serialized
added 2 salv spawns (people commonly spawn inside eachother) and expedition/shuttle console to salv

also fixed warning from saltern having ihs gloves
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
no cl no fun

real :trollface:

@Cheackraze FYI
Also what is that diff, had it not had new entities format saved yet.

it should have since you commited the resave command but idk

@metalgearsloth ci fixed!!!!!!!

Thanks @deltanedas I think that's the only thing on my list to update kettle for.


fix SQL rewrite issue

Fixes #ISSUSE_ID.
Changes proposed in this pull request:
-I reported an issue 4 months ago,https://github.com/apache/incubator-shardingsphere/issues/1348.
-Loxp fixed it,https://github.com/apache/incubator-shardingsphere/pull/1499.
-But it's not perfect,it has another issue. If the SQL is single routing and the pagesize is bigger than one,then the query result will return all rows,bacause the parameters has been rewrited in ParsingSQLRouter.route().

Pull Request Test Coverage Report for Build 7306

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 53.313%

Totals

Change from base Build 7305:
0.0%

Covered Lines:
8359

Relevant Lines:
15679

💛  - Coveralls

Accept. The https://github.com/apache/incubator-shardingsphere/issues/2062 is also caused by this rewrite issue.


CSS minification warnings don't contain file names, making them difficult to track down

Description
Currently, I'm looking a CSS minification warning that looks like this:
warnings when minifying css:
▲ [WARNING] Unexpected "{" [css-syntax-error]

    <stdin>:484:1:
      484 │  {
          ╵  ^

This is fairly difficult to track down, as the user needs to go one-by-one to try to figure out which module has an open brace on line 484.
Sometimes this is easier to track down, given a class name or a bit of syntax is shown in the warning, like in the following:
warnings when minifying css:
▲ [WARNING] Transforming this CSS nesting syntax is not supported in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari14") [unsupported-css-nesting]

    <stdin>:3:19:
      3 │     div[id*='app'] & {
        ╵                    ^

  The nesting transform for this case must generate an ":is(...)" but the configured target environment does not support the ":is" pseudo-class.

Position info is again pretty hard to use, but the content is at least something we can grep for without too much trouble.
This particular warning can be reproduced with the following CSS content, if it's helpful:
body {
  h1 {
    div[id*='app'] & {
      color: red;
    }
  }
}

Just stick a <link rel="stylesheet" href"./style.css"> in the HTML entry and you're good to reproduce.
(I fully appreciate this is pretty nasty CSS, I'm working to migrate some old LESS and this is what I'm workin' with at the moment)
Suggested solution
If possible, a file name in the warning message would be ideal, else, perhaps some more context in the warning, like the line above & below?
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Also stuck on this error recently.
 warnings when minifying css:
 ▲ [WARNING] Unexpected "{" [css-syntax-error]
     <stdin>:2:1:
       2 │  {
         ╵  ^

However, I'm unable to find anywhere that would explain this in our application. All of the scss files we have seem to appear correct, and most our other styling is through any 3rd party packages (like tailwind), so tracing down is about impossible without knowing more details. I can see a PR was created, but hasn't had any traction for a couple weeks.

Are you using CSS modules by chance? I seem to recall that's where I was seeing it the most. Seems like it would drop :global in some cases, resulting in those syntax errors.

For the above example, that can be switched to the following to fix it:
:global(.bar) {
  ...
}

I only found it as only a single CSS file of ours had a line 484, with this being on it.

Thanks for the tip! That will work for our case for the immediate fix.

▲ [WARNING] Expected ":" [css-syntax-error]
<stdin>:15413:41015:
  15413 │ ...isplay: none; }.\&\:\:after{--&:after !important;}.\&\:\:bef...
        │                                  ^
        ╵                                  :

Almost impossible to find


If cudo finds only 1 device it crashes app.py immidietly

def_rank in lib/sync.py does modulo by 0 error when torch.cuda.device_count() returns 0
"The cuda devices are numbered from 0 and up."
At least that is what alabanD answered about that question in https://discuss.pytorch.org/t/torch-cuda-device-count-always-return-0/135632
If there is only one GPU it will be 0, crashing immidiatly when run from app.py due to modulo by 0

I tried with a one-gpu machine, the torch.cuda.device_count() should return 1...
The question in https://discuss.pytorch.org/t/torch-cuda-device-count-always-return-0/135632 why it returns 0 is because os.environ["CUDA_VISIBLE_DEVICES"]= "3" (which means a machine with only one GPU cannot find GPU ID=3)

I guess then machine I used just cannot use Cuda.


slow production builds with react-app-rewired

hey all,
ive inherited a project that uses<EMAIL_ADDRESS>we've noticed that our production builds can take upwards of 35minutes....
"build": "CI=false react-app-rewired --max-old-space-size=8192 build ",
can anyone share what tool react-app-rewired uses under the hood to compile production builds? is it webpack?

It uses create-react-app, which underneath uses webpack.
React-app-rewired is used to be able to tweak the webpack configuration for a create-react-app project, as that configuration is not normally able to be modified. You will find the actual tweaks being made inside a file or folder in the root directory of the project called config-overrides (with either a .js or .ts extension if it's a single file).
The actual version of create-react-app will be specified inside your package.json file - look for react-scripts in there as the critical version information for identifying which version of create-react-app is currently in use.

Closing --- this given it's not a bug and no activity.

@mx2323 I'm having the same issue, did you find what was causing such slow builds?

@mx2323 Having the same issue. Did you find the solution?


DropDefaultValueGeneratorHana: add missing toDataBaseDataType()

Fixes #3

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Stephan Merker seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

I'm afraid, the auto-formatter of my IDE (Eclipse) is not compatible with your formatting. Let me know, if you perfer an unformatted version of this fix.

Merged. Thanks.


GPG key expired in runner image and block startup

When creating an image, build_tools/github_actions/runner/gcp/image_setup.sh downloads the Google Cloud SDK gpg key and stores it in the image. This key never gets updated unless we push a new version of the runner image (our latest image was created in 2022/09).
This causes the problem if the gpg key expired and we run apt-get update later in the instances. The apt-get update will fail because the cloud sdk repo can't be verified by the expired gpg key.
In build_tools/github_actions/runner/config/setup.sh, add-google-cloud-ops-agent-repo.sh executes apt-get update and ran into this issue recently.

I was premature in closing this. This isn't fixed till it rolls out

New images have been fully pushed to prod


Outline transactions idea

Discussion results:

The problem with the current DB mutex is that read operations that precede the write operations can contain outdated information due to race conditions.
Currently there are no transactions and therefore no (deferrable) constraints
We could replace the raw queries with ORM calls, do performance tests, and compare both implementations. This would enable us to implement deferrable constraints and transactions which would guarantee a consistent table after the transaction is complete.
We can add BEGIN and COMMIT statements only to the raw queries. That would also allow to add deferrable constraints. The transaction would then not span multiple queries (for example object saves) but most likely cover most of the occurring problems.


How to share language data between multiple instances

tesseract::TessBaseAPI is not thread safe, I want to create mutliple instances to serve more request, but memory usage is too high, so I want to share the language data between instances

Please you tesseract user forum for asking support


Timeout after 5SECONDS while retrieving configuration for [ROLESMAPPING] & startupProbe error on dashboards verison 2.0.0

cluster.yaml
apiVersion: opensearch.opster.io/v1
kind: OpenSearchCluster
metadata:
  name: opensearch
  namespace: opensearch-system
spec:
  general:
    serviceName: opensearch
    version: 2.0.0
    image: xxx.dkr.ecr.cn-northwest-1.amazonaws.com.cn/opensearch:2.0.0
  security:
    config:  # Everything related to the securityconfig
      securityConfigSecret:
        name:  securityconfig-secret
      #adminSecret:
      #  name:  # Name of a secret that contains the admin client certificate
      adminCredentialsSecret:
        name: admin-credentials-secret
    tls:
      transport:
        generate: true
      http:
        generate: true
  dashboards:
    enable: true
    version: 2.0.0
    image: xxx.dkr.ecr.cn-northwest-1.amazonaws.com.cn/opensearch-dashboards:2.0.0
    opensearchCredentialsSecret:
      name: admin-credentials-secret
    replicas: 1
    additionalConfig:
      #opensearch_security.auth.type: "proxy"
      opensearch.requestHeadersWhitelist: |
        ["securitytenant","Authorization","x-forwarded-for","x-auth-request-access-token", "x-auth-request-email", "x-auth-request-groups"]
      opensearch_security.multitenancy.enabled: "true"
    resources:
      requests:
         memory: "512Mi"
         cpu: "200m"
      limits:
         memory: "512Mi"
         cpu: "200m"
  nodePools:
    - component: masters-data-hot
      replicas: 2
      diskSize: "5Gi"
      NodeSelector:
      resources:
         requests:
            memory: "1Gi"
            cpu: "500m"
         limits:
            memory: "1Gi"
            cpu: "500m"
      roles:
        - "data"
        - "master"
        - "ingest"
      additionalConfig:
        node.attr.type: hot
    - component: masters-data-cold
      replicas: 1
      diskSize: "5Gi"
      NodeSelector:
      resources:
         requests:
            memory: "1Gi"
            cpu: "500m"
         limits:
            memory: "1Gi"
            cpu: "500m"
      roles:
        - "data"
        - "master"
        - "ingest"
      additionalConfig:
        node.attr.type: cold

pod status
[root@eks-test k8s_opensearch]# kubectl get pod -n opensearch-system
NAME                                                      READY   STATUS      RESTARTS   AGE
opensearch-dashboards-67db4f7f79-wgmvw                    0/1     Running     1          4m52s
opensearch-masters-data-cold-0                            1/1     Running     0          41m
opensearch-masters-data-hot-0                             1/1     Running     0          41m
opensearch-masters-data-hot-1                             1/1     Running     0          38m
opensearch-operator-controller-manager-5df696864d-tkqrd   2/2     Running     0          42m
opensearch-securityconfig-update-qxvgq                    0/1     Completed   0          41m

dashboards log
[root@eks-test k8s_opensearch]# kubectl logs opensearch-dashboards-67db4f7f79-wgmvw -n opensearch-system
{"type":"log","@timestamp":"2022-07-12T07:15:28Z","tags":["info","plugins-service"],"pid":7,"message":"Plugin \"visTypeXy\" is disabled."}
{"type":"log","@timestamp":"2022-07-12T07:15:29Z","tags":["warning","config","deprecation"],"pid":7,"message":"\"opensearch.requestHeadersWhitelist\" is deprecated and has been replaced by \"opensearch.requestHeadersAllowlist\""}
{"type":"log","@timestamp":"2022-07-12T07:15:30Z","tags":["info","plugins-system"],"pid":7,"message":"Setting up [37] plugins: [usageCollection,opensearchDashboardsUsageCollection,opensearchDashboardsLegacy,mapsLegacy,share,opensearchUiShared,legacyExport,embeddable,expressions,data,home,console,apmOss,management,indexPatternManagement,advancedSettings,savedObjects,dashboard,visualizations,visTypeVega,visTypeTimeline,timeline,visTypeTable,visTypeMarkdown,tileMap,regionMap,inputControlVis,visualize,securityDashboards,charts,visTypeVislib,visTypeTimeseries,visTypeTagcloud,visTypeMetric,discover,savedObjectsManagement,bfetch]"}
{"type":"log","@timestamp":"2022-07-12T07:15:33Z","tags":["info","savedobjects-service"],"pid":7,"message":"Waiting until all OpenSearch nodes are compatible with OpenSearch Dashboards before starting saved objects migrations..."}
{"type":"log","@timestamp":"2022-07-12T07:15:34Z","tags":["info","savedobjects-service"],"pid":7,"message":"Starting saved objects migrations"}
{"type":"log","@timestamp":"2022-07-12T07:15:34Z","tags":["info","plugins-system"],"pid":7,"message":"Starting [37] plugins: [usageCollection,opensearchDashboardsUsageCollection,opensearchDashboardsLegacy,mapsLegacy,share,opensearchUiShared,legacyExport,embeddable,expressions,data,home,console,apmOss,management,indexPatternManagement,advancedSettings,savedObjects,dashboard,visualizations,visTypeVega,visTypeTimeline,timeline,visTypeTable,visTypeMarkdown,tileMap,regionMap,inputControlVis,visualize,securityDashboards,charts,visTypeVislib,visTypeTimeseries,visTypeTagcloud,visTypeMetric,discover,savedObjectsManagement,bfetch]"}
{"type":"log","@timestamp":"2022-07-12T07:15:36Z","tags":["listening","info"],"pid":7,"message":"Server running at http://<IP_ADDRESS>:5601"}
{"type":"log","@timestamp":"2022-07-12T07:15:37Z","tags":["info","http","server","OpenSearchDashboards"],"pid":7,"message":"http server running at http://<IP_ADDRESS>:5601"}
{"type":"log","@timestamp":"2022-07-12T07:15:41Z","tags":["error","plugins","securityDashboards"],"pid":7,"message":"StatusCodeError: OpenSearchException[java.util.concurrent.TimeoutException: Timeout after 5SECONDS while retrieving configuration for [ROLESMAPPING](index=.opendistro_security)]; nested: TimeoutException[Timeout after 5SECONDS while retrieving configuration for [ROLESMAPPING](index=.opendistro_security)];\n    at respond (/usr/share/opensearch-dashboards/node_modules/elasticsearch/src/lib/transport.js:349:15)\n    at checkRespForFailure (/usr/share/opensearch-dashboards/node_modules/elasticsearch/src/lib/transport.js:306:7)\n    at HttpConnector.<anonymous> (/usr/share/opensearch-dashboards/node_modules/elasticsearch/src/lib/connectors/http.js:173:7)\n    at IncomingMessage.wrapper (/usr/share/opensearch-dashboards/node_modules/lodash/lodash.js:4991:19)\n    at IncomingMessage.emit (events.js:412:35)\n    at endReadableNT (internal/streams/readable.js:1334:12)\n    at processTicksAndRejections (internal/process/task_queues.js:82:21) {\n  status: 500,\n  displayName: 'InternalServerError',\n  path: '/_plugins/_security/tenantinfo',\n  query: {},\n  body: {\n    error: 'OpenSearchException[java.util.concurrent.TimeoutException: Timeout after 5SECONDS while retrieving configuration for [ROLESMAPPING](index=.opendistro_security)]; nested: TimeoutException[Timeout after 5SECONDS while retrieving configuration for [ROLESMAPPING](index=.opendistro_security)];'\n  },\n  statusCode: 500,\n  response: '{\"error\":\"OpenSearchException[java.util.concurrent.TimeoutException: Timeout after 5SECONDS while retrieving configuration for [ROLESMAPPING](index=.opendistro_security)]; nested: TimeoutException[Timeout after 5SECONDS while retrieving configuration for [ROLESMAPPING](index=.opendistro_security)];\"}',\n  toString: [Function (anonymous)],\n  toJSON: [Function (anonymous)]\n}"}
{"type":"log","@timestamp":"2022-07-12T07:15:41Z","tags":["warning","environment"],"pid":7,"message":"Detected an unhandled Promise rejection.\nOpenSearchException[java.util.concurrent.TimeoutException: Timeout after 5SECONDS while retrieving configuration for [ROLESMAPPING](index=.opendistro_security)]; nested: TimeoutException[Timeout after 5SECONDS while retrieving configuration for [ROLESMAPPING](index=.opendistro_security)]; :: {\"path\":\"/_plugins/_security/tenantinfo\",\"query\":{},\"statusCode\":500,\"response\":\"{\\\"error\\\":\\\"OpenSearchException[java.util.concurrent.TimeoutException: Timeout after 5SECONDS while retrieving configuration for [ROLESMAPPING](index=.opendistro_security)]; nested: TimeoutException[Timeout after 5SECONDS while retrieving configuration for [ROLESMAPPING](index=.opendistro_security)];\\\"}\"}"}
{"type":"response","@timestamp":"2022-07-12T07:15:47Z","tags":[],"pid":7,"method":"get","statusCode":404,"req":{"url":"/api/reporting/stats","method":"get","headers":{"host":"<IP_ADDRESS>:5601","user-agent":"kube-probe/1.21+","accept":"*/*","connection":"close"},"remoteAddress":"<IP_ADDRESS>","userAgent":"kube-probe/1.21+"},"res":{"statusCode":404,"responseTime":10,"contentLength":9},"message":"GET /api/reporting/stats 404 10ms - 9.0B"}

I solved this problem by changing config.yml with setting kibana server_username to admin.
dynamic:
            kibana:
              multitenancy_enabled: true
              server_username: admin
              index: '.kibana'

But dashboards startupprobe always failed with 404.
dashboards log
[root@eks-test k8s_opensearch]# kubectl logs opensearch-dashboards-67db4f7f79-25tkq -n opensearch-system  -f
{"type":"log","@timestamp":"2022-07-12T08:42:53Z","tags":["info","plugins-service"],"pid":9,"message":"Plugin \"visTypeXy\" is disabled."}
{"type":"log","@timestamp":"2022-07-12T08:42:53Z","tags":["warning","config","deprecation"],"pid":9,"message":"\"opensearch.requestHeadersWhitelist\" is deprecated and has been replaced by \"opensearch.requestHeadersAllowlist\""}
{"type":"log","@timestamp":"2022-07-12T08:42:54Z","tags":["info","plugins-system"],"pid":9,"message":"Setting up [37] plugins: [usageCollection,opensearchDashboardsUsageCollection,opensearchDashboardsLegacy,mapsLegacy,share,opensearchUiShared,legacyExport,embeddable,expressions,data,home,console,apmOss,management,indexPatternManagement,advancedSettings,savedObjects,securityDashboards,dashboard,visualizations,visTypeVega,visTypeTimeline,timeline,visTypeTable,visTypeMarkdown,tileMap,regionMap,inputControlVis,visualize,charts,visTypeTimeseries,visTypeVislib,visTypeTagcloud,visTypeMetric,discover,savedObjectsManagement,bfetch]"}
{"type":"log","@timestamp":"2022-07-12T08:42:57Z","tags":["info","savedobjects-service"],"pid":9,"message":"Waiting until all OpenSearch nodes are compatible with OpenSearch Dashboards before starting saved objects migrations..."}
{"type":"log","@timestamp":"2022-07-12T08:42:58Z","tags":["info","savedobjects-service"],"pid":9,"message":"Starting saved objects migrations"}
{"type":"log","@timestamp":"2022-07-12T08:42:58Z","tags":["info","plugins-system"],"pid":9,"message":"Starting [37] plugins: [usageCollection,opensearchDashboardsUsageCollection,opensearchDashboardsLegacy,mapsLegacy,share,opensearchUiShared,legacyExport,embeddable,expressions,data,home,console,apmOss,management,indexPatternManagement,advancedSettings,savedObjects,securityDashboards,dashboard,visualizations,visTypeVega,visTypeTimeline,timeline,visTypeTable,visTypeMarkdown,tileMap,regionMap,inputControlVis,visualize,charts,visTypeTimeseries,visTypeVislib,visTypeTagcloud,visTypeMetric,discover,savedObjectsManagement,bfetch]"}
{"type":"log","@timestamp":"2022-07-12T08:43:01Z","tags":["listening","info"],"pid":9,"message":"Server running at http://<IP_ADDRESS>:5601"}
{"type":"log","@timestamp":"2022-07-12T08:43:02Z","tags":["info","http","server","OpenSearchDashboards"],"pid":9,"message":"http server running at http://<IP_ADDRESS>:5601"}
{"type":"response","@timestamp":"2022-07-12T08:43:14Z","tags":[],"pid":9,"method":"get","statusCode":404,"req":{"url":"/api/reporting/stats","method":"get","headers":{"host":"<IP_ADDRESS>:5601","user-agent":"kube-probe/1.21+","accept":"*/*","connection":"close"},"remoteAddress":"<IP_ADDRESS>","userAgent":"kube-probe/1.21+"},"res":{"statusCode":404,"responseTime":5,"contentLength":9},"message":"GET /api/reporting/stats 404 5ms - 9.0B"}
{"type":"response","@timestamp":"2022-07-12T08:43:34Z","tags":[],"pid":9,"method":"get","statusCode":404,"req":{"url":"/api/reporting/stats","method":"get","headers":{"host":"<IP_ADDRESS>:5601","user-agent":"kube-probe/1.21+","accept":"*/*","connection":"close"},"remoteAddress":"<IP_ADDRESS>","userAgent":"kube-probe/1.21+"},"res":{"statusCode":404,"responseTime":3,"contentLength":9},"message":"GET /api/reporting/stats 404 3ms - 9.0B"}
{"type":"response","@timestamp":"2022-07-12T08:43:54Z","tags":[],"pid":9,"method":"get","statusCode":404,"req":{"url":"/api/reporting/stats","method":"get","headers":{"host":"<IP_ADDRESS>:5601","user-agent":"kube-probe/1.21+","accept":"*/*","connection":"close"},"remoteAddress":"<IP_ADDRESS>","userAgent":"kube-probe/1.21+"},"res":{"statusCode":404,"responseTime":2,"contentLength":9},"message":"GET /api/reporting/stats 404 2ms - 9.0B"}
{"type":"response","@timestamp":"2022-07-12T08:44:14Z","tags":[],"pid":9,"method":"get","statusCode":404,"req":{"url":"/api/reporting/stats","method":"get","headers":{"host":"<IP_ADDRESS>:5601","user-agent":"kube-probe/1.21+","accept":"*/*","connection":"close"},"remoteAddress":"<IP_ADDRESS>","userAgent":"kube-probe/1.21+"},"res":{"statusCode":404,"responseTime":6,"contentLength":9},"message":"GET /api/reporting/stats 404 6ms - 9.0B"}
{"type":"response","@timestamp":"2022-07-12T08:44:34Z","tags":[],"pid":9,"method":"get","statusCode":404,"req":{"url":"/api/reporting/stats","method":"get","headers":{"host":"<IP_ADDRESS>:5601","user-agent":"kube-probe/1.21+","accept":"*/*","connection":"close"},"remoteAddress":"<IP_ADDRESS>","userAgent":"kube-probe/1.21+"},"res":{"statusCode":404,"responseTime":3,"contentLength":9},"message":"GET /api/reporting/stats 404 3ms - 9.0B"}
{"type":"response","@timestamp":"2022-07-12T08:44:54Z","tags":[],"pid":9,"method":"get","statusCode":404,"req":{"url":"/api/reporting/stats","method":"get","headers":{"host":"<IP_ADDRESS>:5601","user-agent":"kube-probe/1.21+","accept":"*/*","connection":"close"},"remoteAddress":"<IP_ADDRESS>","userAgent":"kube-probe/1.21+"},"res":{"statusCode":404,"responseTime":3,"contentLength":9},"message":"GET /api/reporting/stats 404 3ms - 9.0B"}
{"type":"response","@timestamp":"2022-07-12T08:45:14Z","tags":[],"pid":9,"method":"get","statusCode":404,"req":{"url":"/api/reporting/stats","method":"get","headers":{"host":"<IP_ADDRESS>:5601","user-agent":"kube-probe/1.21+","accept":"*/*","connection":"close"},"remoteAddress":"<IP_ADDRESS>","userAgent":"kube-probe/1.21+"},"res":{"statusCode":404,"responseTime":3,"contentLength":9},"message":"GET /api/reporting/stats 404 3ms - 9.0B"}
{"type":"response","@timestamp":"2022-07-12T08:45:34Z","tags":[],"pid":9,"method":"get","statusCode":404,"req":{"url":"/api/reporting/stats","method":"get","headers":{"host":"<IP_ADDRESS>:5601","user-agent":"kube-probe/1.21+","accept":"*/*","connection":"close"},"remoteAddress":"<IP_ADDRESS>","userAgent":"kube-probe/1.21+"},"res":{"statusCode":404,"responseTime":4,"contentLength":9},"message":"GET /api/reporting/stats 404 4ms - 9.0B"}

I try to get /api/reporting/stats using curl. And I found it always returns 404. Was this path deprecated in dashboards 2.x?
[root@eks-test k8s_opensearch]# kubectl get pod -n opensearch-system -o wide
NAME                                                     READY   STATUS      RESTARTS   AGE     IP                NODE                                                 NOMINATED NODE   READINESS GATES
opensearch-dashboards-67db4f7f79-sk6g4                   0/1     Running     0          76s     <IP_ADDRESS>   ip-192-168-132-217.cn-northwest-1.compute.internal   <none>           <none>
[root@eks-test k8s_opensearch]# curl <IP_ADDRESS>:5601
[root@eks-test k8s_opensearch]# curl <IP_ADDRESS>:5601/api/reporting/stats
{"statusCode":404,"error":"Not Found","message":"Not Found"}

Then I check the deployment manifest of dashboards, I found that httpget path is "/api/reporting/stats", should it be changed when using dashboards version 2.x ?
startupProbe:
          failureThreshold: 10
          httpGet:
            path: /api/reporting/stats
            port: 5601
            scheme: HTTP
          initialDelaySeconds: 10
          periodSeconds: 20
          successThreshold: 1
          timeoutSeconds: 5

We're still in the process of shoring up the v2.0.0 support.  @prudhvigodithi may be able to provide some further insight into this.

Hey @xikunyu I dont see any issue with latest helm chart that should support 2.x
helm install opensearch-operator opensearch-operator/opensearch-operator --version 2.0.0

Cluster.yaml file
apiVersion: opensearch.opster.io/v1
kind: OpenSearchCluster
metadata:
  name: opensearch
spec:
  general:
    serviceName: opensearch
    version: 2.0.0
  security:
    config:  # Everything related to the securityconfig
      securityConfigSecret:
        name:  securityconfig-secret
      #adminSecret:
      #  name:  # Name of a secret that contains the admin client certificate
      adminCredentialsSecret:
        name: admin-credentials-secret
    tls:
      transport:
        generate: true
      http:
        generate: true
  dashboards:
    enable: true
    version: 2.0.0
    opensearchCredentialsSecret:
      name: admin-credentials-secret
    replicas: 1
    additionalConfig:
      #opensearch_security.auth.type: "proxy"
      opensearch.requestHeadersWhitelist: |
        ["securitytenant","Authorization","x-forwarded-for","x-auth-request-access-token", "x-auth-request-email", "x-auth-request-groups"]
      opensearch_security.multitenancy.enabled: "true"
    resources:
      requests:
         memory: "512Mi"
         cpu: "200m"
      limits:
         memory: "512Mi"
         cpu: "200m"
  nodePools:
    - component: masters-data-hot
      replicas: 1
      diskSize: "5Gi"
      roles:
        - "data"
        - "master"
        - "ingest"
      additionalConfig:
        node.attr.type: hot
    - component: masters-data-cold
      replicas: 1
      diskSize: "5Gi"
      roles:
        - "data"
        - "master"
        - "ingest"
      additionalConfig:
        node.attr.type: cold

kubectl get pods
k get pods
NAME                                                      READY   STATUS      RESTARTS   AGE
opensearch-dashboards-6c79bd597f-q8fth                    1/1     Running     0          2m27s
opensearch-masters-data-cold-0                            1/1     Running     0          2m27s
opensearch-masters-data-hot-0                             1/1     Running     0          2m27s
opensearch-operator-controller-manager-7477cf9cd5-95drm   2/2     Running     0          30m
opensearch-securityconfig-update--1-hbjwj                 0/1     Completed   0          2m27s

Dashboard logs
/api/reporting/stats 200 8ms - 9.0B"}
{"type":"response","@timestamp":"2022-07-13T13:27:29Z","tags":[],"pid":1,"method":"get","statusCode":200,"req":{"url":"/api/reporting/stats","method":"get","headers":{"host":"<IP_ADDRESS>:5601","user-agent":"kube-probe/1.22+","accept":"*/*","connection":"close"},"remoteAddress":"<IP_ADDRESS>","userAgent":"kube-probe/1.22+"},"res":{"statusCode":200,"responseTime":2,"contentLength":9},"message":"GET /api/reporting/stats 200 2ms - 9.0B"}

k port-forward pod/opensearch-dashboards-6c79bd597f-q8fth 5601:5601

Hey @xikunyu can please you post an update after trying with latest helm chart?

Hey @xikunyu can please you post an update after trying with latest helm chart?

There is no problem. Thank you for your help!


SILOptimizer: replace the recursive CFG walk in the RemoveUnreachable utility with a worklist algorithm.

This avoids deep stack nesting for large CFGs. It also makes the code simpler.

@swift-ci test


Pattern matching on functions? And default effects on top-level pure/ghost terms

Despite the surprising title, we're not sure this is actually a bug.
The following code works just fine.
let m (f : int -> int) : Tot int =
    match f with
    | x -> 0

This is because F* can prove (via z3!) that the match is total, since there is a single catch-all pattern. This also actually extracts correctly, since the match is optimized away.
This is a consequence of matching being very semantic in F*, but struck me and @nikswamy as very odd anyway.
I tried to get a contradiction from this, but couldn't, as really the only possible patterns one can provide for are wildcards and variables (or none). Here are some more examples, the first one being something that might desirable.
let m2 (a:Type) (_ : a == int) (x : a) =
    match x with
    | 0 -> 0
    | _ -> 1

let f (x:int) = x
let m3 =
    match f with

The last one (I believe..) has a non-sat WP (so no proof of false), although I wonder what's the inferred type for it...
Also, inlining the definition of f in m3 will complain with
Unexpected error; please file a bug report, ideally with a minimized version of the source program that triggered the error.
Ill-typed term: cannot pattern match an abstraction

meaning there are some don't-pattern-match-a-lambda checks in place.
So, putting this out here for comments. Is this just fine? Should we be aggresive in forbidding matches on function types? What to do in cases like m2, then?

Wow, this is super unintuitive. Even aside from the surprise of allowing to write these degenerate matches for function-typed terms, I had a couple of surprises.

I didn't expect m3 to typecheck. This variant rightly fails to typecheck

let m4 (f:(int -> int)) = match f with

m3 above typechecks, but it actually has a type with a precondition that is unsatisfiable. After generalization, its inferred type seems to be equivalent to:
#a:Type -> PURE a (fun post -> False)

So, if you try, say let test = m3 #unit then this fails to typecheck (correctly).
I would have expected the top-level default effect rule to kick in and reject m3 because its type is not Tot. But, somehow its getting generalized with a False wp.
If you instead write:
assume val d : unit -> Dv unit
let m3 = d(); ((match f with) <: unit)

Then you get a "patterns are incomplete" error on the match. So, the presence of the Dv effect prevents this unexpected form of generalization from kicking in.
So, yes, no unsoundness here (yet?), but it seems very weird indeed. I'm marking it as a bug, since we should at least prevent the generalization of the type of m3 and get it to behave like m4.

Yes, seems to be an issue with generalization, because this also fails:
let foo = ((match f with) <: unit)

@mtzguido, i am missing the connection with m2? even if we forbid pattern matching on functions, m2 should still work, because F* will try to prove a <: int, with a == int in gamma, so should work out?

Yes, m2 works out and we probably want it to.
My thinking was that if the SMT is invoked to see if we can match on something, we can match on functions (and anything) when in a inconsistent environment. (Although I'm not sure that's bad)
However, if we want to strictly forbid matching on functions, we need to somehow make a cut that allows for m2 but not the other examples, which might not be doable?

A similar issue, should this verify?
val foo: Type0 -> Tot int
let foo a = match a with
  | int -> 0
  | bool -> 1
  | _ -> 2

It's extraction is also strange:
open Prims
let foo = Prims.parse_int "0"

I think I remember an example similar to that, and it's just that int is being taken as a variable pattern, without any relation to the int type.

Your int here is just a variable, so you're not really case analyzing a
Get Outlook for Androidhttps://aka.ms/ghei36
From: Aseem Rastogi
Sent: Monday, June 26, 11:48 PM
Subject: Re: [FStarLang/FStar] Pattern matching on functions? (#1097)
To: FStarLang/FStar
Cc: Nikhil Swamy, Mention
A similar issue, should this verify?
val foo: Type0 -> Tot int let foo a = match a with | int -> 0 | bool -> 1 | _ -> 2
It's extraction is also strange:
open Prims let foo = Prims.parse_int "0"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FFStarLang%2FFStar%2Fissues%2F1097%23issuecomment-311268636&data=02|01|nswamy%40microsoft.com|e497c05df0ed47f3393108d4bd2881f9|72f988bf86f141af91ab2d7cd011db47|1|0|636341429058308701&sdata=37FCuE5pXOyNwI11MjV9ZHuEQzbVcCE1s4Pvj23LAdc%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF4Ln5-ASW-vCepcEQ8pud-LcV18OxC-ks5sIKW2gaJpZM4OF-1l&data=02|01|nswamy%40microsoft.com|e497c05df0ed47f3393108d4bd2881f9|72f988bf86f141af91ab2d7cd011db47|1|0|636341429058308701&sdata=7AuZtwt1COx3Q78ExMgVJRzbFBMgH4e6N3sgwXVl%2FJ4%3D&reserved=0.

Ack!

Should we really forbid matching on lambda-abstractions ? As long as we cannot do anything with the match it should be innocuous.
A little off topic, there are also interesting languages which allows matching on functions to reveal the intensional structure of the term. Not sure that we want to go to that world though.

Right, the question is what match means. Does it mean syntactic sugar for a collection of (possibly) destructuring bindings, or is it syntactic sugar for eliminators of inductives?  In the first case, it seems fine to allow (necessarily pointless) matches.  In the second case, you might restrict it to exclude function types.
F*'s matches are semantic, so it seems fine to allow it. And in fact even systems that seem more firmly in the second camp, like OCaml and Coq, do:
# match (fun x -> x) with y -> y;;
- : 'a -> 'a = <fun>

Coq < Definition a: (nat -> nat) := match (fun x => x) with y => y end.
a is defined

Coq < Print a.
a = fun x : nat => x
     : nat -> nat

(Coq reduces it away, apparently)

Ok, the only issue left here, as far as I can tell, is an issue of related to default effects. cf. (#623, #705, etc.)
We should ensure that top-level, values whose effect is in PURE/GHOST, are forced to be in effect Tot/GTot.
This is what happens for functions whose bodies happen to have PURE/GHOST effect. I see no reason to treat nullary functions any differently.
FYI, @fournet experienced a different manifestation of the same default effect issue (ik.fst)

There's a failwith in the normalizer for matches over a lambda, should we remove that? Otherwise:
This typechecks but explodes on trying to evaluate y (in the IDE)
let f x = x
let y = match f with
        | ff -> ff 0

This just explodes:
let y = match (fun x -> x) with | ff -> ff 0
(* Failure("Ill-typed term: cannot pattern match an abstraction") *)

I removed that failwith, btw.

Can we close this now? Especially also given the revised treatment of default effects at the top-level. @mtzguido @aseemr

m2 seems to have regressed and doesn't verify now:
// 114: type of pattern does not match scrutinee
// this used to succeed via SMT at some point
[@(expect_failure [114])]
let m2 (a:Type) (_ : a == int) (x : a) =
    match x with
    | 0 -> 0
    | _ -> 1

// but we can manually coerce
let coerce (#a:Type) (#b:Type{a==b}) (x:a) : b = x

let m2' (a:Type) (_ : a == int) (x : a) =
    match coerce x with
    | 0 -> 0
    | _ -> 1

I don't really mind that the original fails. I'm adding the current tests to regressions.
If you guys also think it's fine then let's close!

Closing this issue per the latest discussion on it.


fix: TLS problem in UI. Fixes #7632

Fixes #7632
PLEASE NOTE:

InsecureSkipVerify is not relevant in the context of a server, as it is for client config so "crypto/tls accepts any certificate presented by the server and any host name in that certificate". In short, this line shouldn't be here
As far as I can see, it seemed to be needed because it (as a part of tls.Config is passed into apiserver.ArgoServerOpts (seen here)
In turn, I think this InsecureSkipVerify: true is used in other areas (here for instance)
The correct way, would be that a flag was passed in here instead that simply allows the user to decide whether the clients elsewhere in the application should be able to skip verification. This would always need to be true in the case of self signed certs, unless some way could be determined that would allow the self signed certs to be trusted.

I believe it likely that this is the case, but cannot guarantee it without further testing. However, merging this pull request does put it in a better situation than before #7621 was merged.

LGTM!


fixed single day rental issue

Fixes #145 in controller, users can now create single day rentals in the future
edit: not sure if this will be used as others are working on a javascript fix for this. It should work for the upcoming milestone, however

RE: edit: not sure if this will be used, what do others think of this as a solution? @owlee @Cobchise @xliu3

@phantompatrol @owlee @cmednieks @xliu3
I think both solutions have merits, the javascript being maybe a little cleaner with less code but the controller method maybe being a little more 'robust' in my opinion.
I honestly have to say I personally prefer Charles' method just because its provides rspec testing, I like his assign_time method and I think it is a little more intuitive as we are already altering the end_time in the controller as is.
I think if we are going to approach it from javascript I'd like to redo the method I PR'd as the current one relies on the javascript only finding the first element on the page, which I don't really like. I only really put that PR there for comparison purposes.
That's my gut feel but at the end of the day both methods work so..

Closing this, since we merged the other one?


0474

Description

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

How to test

Checklist

[ ] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build 675326566

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

Totals

Change from base Build 670008531:
0.0%

Covered Lines:
2220

Relevant Lines:
7130

💛  - Coveralls


Fix(conversion): consistent interface for invalid GTINs

Attempting to convert an invalid GTIN into other formats should return an invalid GTIN object instead of raising a NoMethodError exception.
Resolves issue #5

Just an FYI: You've got Resolves issue #5 in your commit. GitHub won't auto-close #5 though, because it needs to just be Resolves #5

Just an FYI: You've got Resolves issue #5 in your commit. GitHub won't auto-close #5 though, because it needs to just be Resolves #5

Thanks, rebase to the rescue!


[bug]: onScroll prop should be passed to ScrollAreaPrimitive.Viewport by default

Describe the bug
All remaining props are passed from ScrollArea to ScrollAreaPrimitive.Root, however, onScroll should go on ScrollAreaPrimitive.Viewport.
Ideally, it should be passed to the Viewport by default to save people time figuring out why the onScroll prop is accepted on ScrollArea but has no effect.
For anyone running into this issue, it can be addressed by passing onScroll to ScrollAreaPrimitive.Viewport:
const ScrollArea = React.forwardRef<
  React.ElementRef<typeof ScrollAreaPrimitive.Root>,
  React.ComponentPropsWithoutRef<typeof ScrollAreaPrimitive.Root>
>(({ className, children, onScroll, ...props }, ref) => (
  <ScrollAreaPrimitive.Root
    ref={ref}
    className={cn("relative overflow-hidden", className)}
    {...props}
  >
    <ScrollAreaPrimitive.Viewport className="h-full w-full rounded-[inherit]" onScroll={onScroll}>
      {children}
    </ScrollAreaPrimitive.Viewport>
    <ScrollBar />
    <ScrollAreaPrimitive.Corner />
  </ScrollAreaPrimitive.Root>
))

Related issues: #1005 #1430
Affected component/components
ScrollArea
How to reproduce

Install the ScrollArea component
Use it on another component, passing an onScroll handler function
Scrolling will not trigger the handler. The only way to get it to trigger is modifying the ScrollArea component and passing the onScroll handler to the ScrollAreaPrimitive.Viewport component.

Codesandbox/StackBlitz link
No response
Logs
No response
System Info
<EMAIL_ADDRESS>
Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

+1 We need that


Table in admonition block does not work

Problem:

Proposed Solution:
I have no idea because I have never used Hugo 😢
Page to Update:

https://kubernetes.io/docs/test/
https://github.com/kubernetes/website/blob/main/content/en/docs/test.md

/area web-development
/triage accepted

Can I take care of it?

/remove-lifecycle stale

I have raised a post for support in the Hugo forums.

There is an answer on the Hugo forum stating that this is not a Hugo issue. The suggestions is to fix the CSS. Any pointers?


prototype VM resource

Initial proposal :
{
 "acl": {
    "owner": {
      "principal": "ADMIN",
      "type": "ROLE"
    },
    "rules": [
      {
        "principal": "ANON",
        "type": "ROLE",
        "right": "VIEW"
      }
    ]
  },
  "cloud": “scissor-fr1”,
  "disk": 10,
  "instanceType": "Large",
  "instanceId": "aaa-bbb-111",
  "updated": “2017-08-15T10:00:00.0Z",
  "created": "2017-08-15T10:00:00.0Z",
  "state": "Running",
  "ram": 1024,
  "id": “vm/867876-8768”,
   "resourceURI": "http://sixsq.com/slipstream/1/VM",
  "user": “test”,
  "cpu": 1
 “run”: {
        "href": run/aaa-bbb-ccc
        },

}

Do we want to have the service offer here?  If we have a run it could be extracted from there, but if it doesn't have a run (started directly), what happens?

cloud should be renamed to connector and it should be a reference: {"connector": {"href": "scissor-fr"}}
user should also be a reference
if the service offer is brought in, then the cpu, ram, disk, and instance type should be renamed with namespaces as for the service offers and moved a level down into the reference map for the service offer

Rephrased proposal including above comments  :
{
 "acl": {
    "owner": {
      "principal": "ADMIN",
      "type": "ROLE"
    },
    "rules": [
      {
        "principal": "ANON",
        "type": "ROLE",
        "right": "VIEW"
      }
    ]
  },
 "id": “vm/867876-8768”,
 "connector": {"href": “connector/scissor-fr”},
 “user”: {"href": “user/test”},
 “serviceOffer”: {"href": “service-offer/e3db10f4-ad81-4b3e-8c04-4994450da9e3”,
                    “resource:cpu” : 1,
 		    “resource:ram” : 1024,
		    “resource:disk” : 10,
                    “resource:instanceType” : “Medium”
                  },
  “run”: {"href": “run/aaa-bbb-ccc”},
  "instanceId": "aaa-bbb-111",
  "updated": “2017-08-15T10:00:00.0Z",
  "created": "2017-08-15T10:00:00.0Z",
  "state": "Running",
  "resourceURI": "http://sixsq.com/slipstream/1/VM"
}


Removing buttons from completed task list items.

This fixes #99.

Coverage decreased (-0.07%) to 46.719% when pulling ad0cdbfd8310a1308732923e3242019c1747a27c on TOA-99/remove_buttons_from_completed_tasks into c402baf98cece3202210a25615fc1de0cc118611 on development.


Logo missing

Describe the bug
we don't have a logo yet.

 temporary solution, please integrate in the website


~/.bashrc is no longer loaded automatically after moving my home directory

Your Windows build number:  (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.16299.19]

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)

I have changed my home address to /mnt/c/Users/<my username>.
My .bashrc file is located at /mnt/c/Users/<my username>/.bashrc.
When I open up a new bash it does not load my .bashrc file.

What's wrong / what should be happening instead:

It should be loading my .bashrc file at ~/.bashrc. It worked before updating Windows today.
To labour the point; the home directory contains a .bashrc file. You can get the home directory for a user using eval echo ~$USER and so running ls "`eval echo ~$USER`"/.bashrc shows that the file exists.
As a workaround:

After opening up bash on Ubuntu on Windows, and then manually run bash in the terminal, then it does get loaded correctly.
Edit the bash on Ubuntu on Windows shortcut and add --rcfile ~/.bashrc to the end of the command. For example: C:\Windows\System32\bash.exe ~ --rcfile ~/.bashrc

Before updating is build 15063 (Creators Update, version 1703), is not it?
Does ~/.bash_profile or ~/.bash_login, that doesn't load ~/.bashrc exist?
See https://github.com/Microsoft/WSL/issues/2067#issuecomment-299622057

Previously it would source the .bashrc always when the terminal was opened. Now it does not.
.bash_profile is sourced so I can also add source ~/.bashrc from there.

Facing the same issue.

I also have the same problem. I changed my home directory to a symlink to /mt/c/Users/username , now .bashrc is not source on start up

$ sudo adduser newuser # new user to play with, creates in /home/newuser like your default
$ sudo cp -aR /home/newuser /mnt/c/Users/<you>
$ sudo echo "echo 'running bashrc'" >> /mnt/c/Users/<you>/newuser/.bashrc
$ sudo usermod -d /mnt/c/Users/<you>/newuser newuser

From Windows commandline:
C:\> ubuntu.exe config --default-user newuser
C:\> ubuntu.exe

You don't need to create a new user; you can do the above with your existing default. The above just illustrates getting your paths and perms correct.
exi

@joe-askattest
Thank you !


[Feature]: Font customization

Describe the feature
Allow users to choose the font for the following items, preferably individually:

ilvl text
Currencies
Bag title text

While I realize it is superficial in nature, it allows it to better fit with the overall UI.  Perhaps this could be a part of the theming described in the readme as a planned feature, perhaps not, but figure best to document it as is.
Describe the implementation
In options under each item (bag / bank) a series of options to configure any available font (even those from sharedmedia fonts) and potentially font size to accommodate fonts that use strange kerning.

Duplicate of #137


Support UI Glitches / Missing Content

Right now the support section has padding and layout issues. Headers on all the pages are covered by the header, and there is almost no content about BCH.
This should be a minor change, and will lead to a much more polished UI.

Latest beta had a regression that broke several images on the main page.

Now images are fixed, but there is no way to go back as the back icon in the header was removed.

Thank you for your contribution, we'll improve our UI experience.


Implement phantoms for lint errors

Would be super nice to get an option to display error via phantoms, something similar to this:
https://forum.sublimetext.com/t/dev-build-3118/21270/33

I've added such hack in my local copy and been using it for a while. One thing that would have to be thought out is how to handle cases like
// TODO(me): Do something
This is highlighted in the gutter right now but if using phantoms, it should not show up for this case because then it would just duplicate the text of the TODO. So either that should be customizable per plugin or plugin should specify that. Also one plugin might want to show phantom for some errors and not for other.

@rchl could you please share your hack?

Sorry but I've stopped using it and I can't find the code anymore in my local repo.
It was annoying because phantoms were re-created every time the file was changed. That make the whole text content jump a lot if there were many issues in the file.
It needs more thought on how to do it properly and probably the phantom markers would have to bve cached so that they don't constantly appear and disappear. Would probably make sense to gray them out when linter thinks they might not be relevant anymore rather than removing them instantly.

It was annoying because phantoms were re-created every time the file was changed

Yeah, this really makes phantoms a bad fit. You could set up your linter as a build system and run it on demand like this. If setup well you'll get phantoms kind of as a todo list. This workflow is a bad fit for SublimeLinter so we're not going to use phantoms as a feedback mechanism, but it's also easily achieved without using any plugins.

@braver Are you saying it's possible to create a build for lint tools (to get phantoms)? How does sublime know where to place the phantoms?
I'm asking because I find these phantoms useful at code review so reviewees have nice visual feedback, I've been trying to use this plugin https://github.com/alexkuz/SublimeLinter-inline-errors but it runs terribly

Most linters run a utility in the background, and we pass the output of that utility to get line number, column, and message for each error. SublimeLinter is basically a plugin that allows running these utilities on the fly and on unsaved files. SublimeText build systems allow you to do something similar but on demand. Read more here: https://www.sublimetext.com/docs/3/build_systems.html. If you want help setting up build systems you can ask around on the forums.


[Bug]: The canvas gets scrolled up in the background when the user clicks on currency input dropdown.

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The canvas gets scrolled up in the background when the user clicks on currency input dropdown. it doesn't happen after deployment though
Steps To Reproduce

Drag and drop a currency input widget
Make sure its at the bottom of canvas with other widgets before it.
Click on the drop down arrow

Observe - The canvas seems getting scrolled up.
Public Sample App
No response
Environment
Release
Issue video log
https://www.loom.com/share/93d6bd2912174bf39e69d9067c06ba8a
Version
1.9.15

this is duplicate of #18561


Generating Multiple Outputs

Is there a suggested way of generating multiple image outputs given a text input, like the 9-10 outputs dalle2 produces?

@egeozsoy you could do it yourself easily by images = dalle2(['your prompt'] * num_outputs)

@egeozsoy i'm guessing you have trained something decent?

At least something that gives me some results haha. That sounds like a very easy solution, will try it out

but knowing researchers, you are probably scrambling for a paper to be written / avoid being scooped, so hearing silence is good enough signal for me haha

I am working on a very specific topic, surgical video generation. So the results are maybe not very interesting. But once I have something that works (right now, I think I am getting overfitting problems a lot), I will share :)

@egeozsoy nice! surgical video is very interesting! laparoscopy?

ok, you go do your thing

@egeozsoy very cool! and yeah 7k images isn't a lot of data
but the new Tero Karras paper https://arxiv.org/abs/2206.00364 brings in some augmentation tricks that may benefit the small data setting. i'll eventually build that into this repository and some other DDPM repositories once i see some positive results

Thanks for the suggestions, It is really about testing the limited data regime for dalle2 for now. Interested in seeing how it performs with 1000x less data :)


python3Packages.adafruit-pureio: 1.1.8 -> 1.1.9

Motivation for this change
Update to latest upstream release 1.1.9
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 128685 run on x86_64-linux 1

2 packages built:

python38Packages.adafruit-pureio
python39Packages.adafruit-pureio


Update and lightweighting of container base images

Discussed in https://github.com/cloudforet-io/community/discussions/115

Originally posted by jihyungSong February 13, 2023
Most Cloudforet's Core and Plugin container images are using python:3.8.
I suggest using python:3 instead of python:3.8 for image updates.
It is not just for the purpose of upgrading the python version, but for the purpose of updating the basic OS(debian) and libraries of the image. latest OS libraries can also resolve container image security vulnerabilities.
Along with this, if you use python:3-slim instead of regular python:3 , you can further lightweighting the image and reduce the size of the container image to less than half.

Change the base image from python:3-slim to python:3.8-slim due to a python version compatibility issue.


TaskInfo seemed to be setting executor with container data.

There seem to be some other issues, too (such as typos in method names). I'll update this branch with my fixes -- let me know if you'd like these separated out into different branches.

nice catch, @oubiwann. thanks!

Sure thing!


geoipupdate: 4.9.0 -> 4.10.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/maxmind/geoipupdate/releases.
meta.description for geoipupdate is: "Automatic GeoIP database updater"
meta.homepage for geoipupdate is: "https://github.com/maxmind/geoipupdate"
meta.changelog for geoipupdate is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.10.0 with grep in /nix/store/mz9x410ll4glznsj1qdb8a515sn6b58n-geoipupdate-4.10.0
found 4.10.0 in filename of file in /nix/store/mz9x410ll4glznsj1qdb8a515sn6b58n-geoipupdate-4.10.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
geoipupdate

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mz9x410ll4glznsj1qdb8a515sn6b58n-geoipupdate-4.10.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A geoipupdate https://github.com/r-ryantm/nixpkgs/archive/13943e2b68027819051996dfef46619a671aaae7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mz9x410ll4glznsj1qdb8a515sn6b58n-geoipupdate-4.10.0
ls -la /nix/store/mz9x410ll4glznsj1qdb8a515sn6b58n-geoipupdate-4.10.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

geoipupdate

Maintainer pings
cc @dasJ for testing.

Result of nixpkgs-review pr 193173 run on x86_64-linux 1

1 package built:

geoipupdate


Inventory

Is Inventory being worked on?
Maybe a simple editor to add e.g food or edit quantity would be a great start

hey! kinda forgot this project existed lol
i went ahead and pushed a new version that implements a basic inventory editor! let me know if you have any ideas or improvements!

Thanks. I am currently working on a own version with a interactive inventory


fix: delay setting git.username and git.email config till commit time

In https://github.com/argoproj-labs/argocd-image-updater/blob/master/pkg/argocd/git.go#L161-L167, it sets git.username and git.email config to the git client. These 2 configs are used by commit operation later. In some cases, the commit operation will not be needed, either because there are errors before the commit, or because the commit should be skipped due to absence of real changes.
This PR delays setting these 2 configs, which involves calling git command twice, till before the commit operation. In addition to the savings from skipping the 2 command calls, the logs will also be cleaner.

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

Project coverage is 74.70%. Comparing base (17a57da) to head (ab50856).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #912   +/-   ##
=======================================
  Coverage   74.70%   74.70%
=======================================
  Files          31       31
  Lines        3922     3922
=======================================
  Hits         2930     2930
  Misses        856      856
  Partials      136      136

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


Update amazon-kinesis-producer to 0.14.10

Updates com.amazonaws:amazon-kinesis-producer from 0.14.9 to 0.14.10.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "amazon-kinesis-producer" } ]

labels: library-update, early-semver-minor, semver-spec-patch

Codecov Report

Merging #212 (f1e6c9a) into main (d8c1855) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #212   +/-   ##
=======================================
  Coverage   88.85%   88.85%
=======================================
  Files          91       91
  Lines        2772     2772
  Branches       70       70
=======================================
  Hits         2463     2463
  Misses        309      309

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 d8c1855...f1e6c9a. Read the comment docs.


Xiwi command not found/possibly doesn't connect to chrome extension

I updated my crouton with xiwi, then tried to launch atom in a browser window, but it comes back with the error -su: xiwi: command not found. My chrome extension doesn't seem to connect at all, and I'm unsure how to make it do so, though this seems to be a connected issue.
Apologies on the obvious questions--I'm just new to this and trying to get it all set up.

@rmglade,
Not sure why that failed, if you added the xiwi target it should be in the 'chroot-bin'.
In your chroot it would be in /usr/local/bin/xiwi which should be in your PATH.
You should not use the sudo prefix/command in your chroot, it'll mess up permissions.
Just use xiwi in your chroot or sudo startxiwi from CrOS outside of your chroot.
Here's the syntax for xiwi in your chroot:
(trusty)denny@localhost:~$ xiwi -h
Illegal option -h
Usage: xiwi [-f] [-F|-T] APPLICATION [PARAMETERS ...]
Launches a windowed session in Chromium OS for any graphical application.
Applications launched in this way show in independent windows or tabs.
All parameters are passed to the specified application.

By default, the app is launched in a window.

Options:
    -F          Launch the APPLICATION full-screen.
    -T          Launch the APPLICATION in a tab.
    -f          Prevent xiwi from quitting automatically. (see NOTE below)

NOTE:
xiwi will normally close when the application returns. Some gui applications
fork before or during normal operation, which can confuse xiwi and cause it to
quit prematurely. If your application does not have a parameter that prevents
it from forking, and crouton is unable to automatically detect the fork, you can
use -f to prevent xiwi from quitting automatically.
xiwi will quit if you close the Chromium OS window when nothing is displayed.

A default window manager will full-screen all windows, unless APPLICATION begins
with 'start' or is 'xinit'. You can cycle through multiple windows inside the
application via Ctrl-Alt-Tab/Ctrl-Alt-Shift-Tab, or close them via
Ctrl-Alt-Shift-Escape.  If APPLICATION begins with 'start' but you still want to
use the default window manager, specify the full path of the application.

And here's the syntax for startxiwi outside of your chroot:
chronos@localhost ~ $ startxiwi -h
Illegal option -h
startxiwi [options] chroot_app [parameters]

Wraps enter-chroot to launch a window or tab in Chromium OS for any graphical application.
Applications launched in this way show in independent windows or tabs.

By default, it will use the primary user on the first xiwi-enabled chroot found and launch
the chroot_app in a window.

Options:
    -b          Fork and run the specified command silently in the background.
    -c CHROOTS  Directory the chroots are in. Default: /mnt/stateful_partition/crouton/chroots
    -k KEYFILE  Override the auto-detected encryption key location.
    -n NAME     Name of the chroot to enter. Default: first one found in CHROOTS
    -t TARGET   Only enter the chroot if it contains the specified TARGET.
    -u USERNAME Username (or UID) to log into. Default: 1000 (the primary user)
    -F          Launch the chroot_app full-screen.
    -T          Launch the chroot_app in a tab.
    -f          Prevent xiwi from quitting automatically. (see NOTE below)

NOTE:
xiwi will normally close when the application returns. Some gui applications
fork before or during normal operation, which can confuse xiwi and cause it to
quit prematurely. If your application does not have a parameter that prevents
it from forking, and crouton is unable to automatically detect the fork, you can
use -f to prevent xiwi from quitting automatically.
xiwi will quit if you close the Chromium OS window when nothing is displayed.

You can cycle through multiple windows inside the application
via Ctrl-Alt-Tab/Ctrl-Alt-Shift-Tab, or close them via Ctrl-Alt-Shift-Escape.
If the chroot_app begins with 'start' but you still want to
use the default window manager, specify the full path of the application.

Note that you have more options outside of your chroot, that's the way I usually launch apps.
Hope this helps,
-DennisL


TFR analysis with more flexibility

Addition of the tapering windows for TFR analysis
The library only contains Morelet wavelet and it does not include other wavelets. There is no way to use other tapering windows but the DPSS and Gaussian windows. Nevertheless, users can define their own wavelet series and apply them to their signals using the cwt function; this however, may degrade the integrity of the library.
Implementation
The library does include the Morelet function which returns the wavelet series for the Morelet wavelet at different scales. Other wavelets can also be defined with the same signature of this function. Then, users can compute their TFR using these wavelet series with the use of cwt function of the time frequency module.
Possible alternatives
The code can also adds an ultimate freedom to the end users by letting them define their own tapering window and the oscillatory signal. This way the function can replace the Morelet function.

@mehdikuchi you want to contribute something new? if so please do but start with small things. Maybe just add a new wavelet function?


Fix race on cleaning endpoint data

Race is with any endpoint data reading, for example /containers api.

LGTM

LGTM

It sadly creates deadlock :)

ping @calavera

ouch.
CI is :green_heart: so LGTM

LGTM


Appstudio update test-component-pac-vmtr

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-vmtr-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
15 seconds
clone-repository

✅ Succeeded
31 seconds
build-container

✅ Succeeded
29 seconds
inspect-image

✅ Succeeded
27 seconds
deprecated-base-image-check

✅ Succeeded
37 seconds
clamav-scan

✅ Succeeded
12 seconds
clair-scan

✅ Succeeded
20 seconds
sbom-json-check

✅ Succeeded
31 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary


[Feature Request] Component Names

Existing Component
Yes
Component Name
Collapse
Description
how do I find out the names of what needs to be included for each component?
adding the needed requirements to the docs page would be very helpful.
eg Table also needs Column (or TableColumn rather)
trying now to get el-collapse to work.
What is the required import? I tried
import { Collapse } from 'element-ui'
Vue.use(Collapse)

[Vue warn]: Property or method "handleChange" is not defined on the instance but referenced during render. Make sure to declare reactive data properties in the data option.
[Vue warn]: Invalid handler for event "change": got undefined
[Vue warn]: Unknown custom element: <el-collapse-item>

oh, it also needs CollapseItem
https://github.com/ElemeFE/element/blob/dev/components.json

update: even with the two components included, I still get this error below
Is this a method I need to implement myself, or is it part of another component I need to include for Collapse to work?
[Vue warn]: Property or method "handleChange" is not defined on the instance but referenced during render. Make sure to declare reactive data properties in the data option.

    <el-collapse v-model="activeNames" @change="handleChange">
      <el-collapse-item title="API output" name="api_output">
        <pre>
{{item}}
        </pre>
      </el-collapse-item>
      <LinkButton label='api output' v-bind:link='apilink'/>
    </el-collapse>

and main.js
import {
  ...
  Collapse, CollapseItem
 } from 'element-ui'

Vue.use(Collapse)
Vue.use(CollapseItem)

You didn't define handleChange in the methods. Please read the Vue docs before using Element.


TimelineEditor: Attempting to undo a change in the text editor will irreversibly delete the entire timeline

The problem
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Open a Timeline in the Dialogic editor
Switch to Text Editor mode
Click somewhere to place your cursor
Ctrl+Z, as if you are trying to undo
The entire timeline will delete itself & autosave, making it totally unrecoverable

Closing Godot without saving doesn't recover the timeline. Thankfully I have source control set up so I was able to recover it, but this will probably bite me again.
Expected behavior
My change is undone
System (please complete the following information):

OS: Windows 10 64bit
Godot Version: 4.1.1.stable.mono.official
Dialogic Version: 2.0-Alpha-9

Solutions
Workaround
Make sure that your project has source control set up so you can roll back to previous versions in case you accidentally Thanos Snap your timeline.
Possible fixes
Perhaps undo history isn't implemented yet.
Really loving Dialogic so far, lads! I appreciate the hard work. (/gen)

Here's a screenshot of the error that appears in the Output console when you press the Ctrl+Z undo shortcut