/run/secrets/kubernetes.io/serviceaccount directory is not created in pods.

Workload Type：Stateful set of 1 pod
Port Mapping：Node Port,Cluser IP
Node Scheduling：Run all pods for this workload on a specific node（select Node(Worker)）
Health Check：None
Volumes：Add 1 volume
Command：/sbin/init
Privileged：Yes: container has full access to the host
3．Launch
Results:
1．I executed the ls command in the container.
/run/secrets/kubernetes.io/serviceaccount The directory could not be found.
Do I need to set up Rancher to create a directory?

@portfield-slash Please remove Command：/sbin/init and try again

@loganhz
Thank you for your help.I tried but it didn't work.
If necessary, other logs are also provided.

@portfield-slash Can you provide your yaml file for the deployment?

/sbin/init is still in your yaml. Can you try the following, please?

Click Deploy
Input a name
Click Launch

Then you can go to the shell to check /run/secrets/kubernetes.io/serviceaccount folder.

@loganhz
Sorry.This one.
I tried but I couldn't find the folder.
apiVersion: apps/v1beta2
kind: StatefulSet
metadata:
  annotations:
    field.cattle.io/creatorId: user-xqll2
    field.cattle.io/publicEndpoints: '[{"addresses":["192.168.XXX.XXX"],"port":30264,"protocol":"TCP","serviceName":"default:test-nodeport","allNodes":true}]'
    kubectl.kubernetes.io/last-applied-configuration: '{"apiVersion":"apps/v1beta2","kind":"StatefulSet","metadata":{"annotations":{"field.cattle.io/creatorId":"user-xqll2","field.cattle.io/publicEndpoints":"[{\"addresses\":[\"192.168.XXX.XXX\"],\"port\":30043,\"protocol\":\"TCP\",\"serviceName\":\"default:test-nodeport\",\"allNodes\":true}]"},"creationTimestamp":null,"generation":1,"labels":{"workload.user.cattle.io/workloadselector":"statefulSet-default-test"},"name":"test","namespace":"default","selfLink":"/apis/apps/v1beta2/namespaces/default/statefulsets/test"},"spec":{"podManagementPolicy":"OrderedReady","replicas":1,"revisionHistoryLimit":10,"selector":{"matchLabels":{"workload.user.cattle.io/workloadselector":"statefulSet-default-test"}},"serviceName":"","template":{"metadata":{"annotations":{"field.cattle.io/ports":"[[{\"containerPort\":3306,\"dnsName\":\"test-nodeport\",\"kind\":\"NodePort\",\"name\":\"3306tcp01\",\"protocol\":\"TCP\",\"sourcePort\":0},{\"containerPort\":3306,\"dnsName\":\"test\",\"kind\":\"ClusterIP\",\"name\":\"3306tcp02\",\"protocol\":\"TCP\",\"sourcePort\":0}]]","workload.cattle.io/state":"{\"aXRrYmRvYzE=\":\"c-ppdgd:m-ffc4c7e082b8\",\"aXRrYmRvYzI=\":\"c-ppdgd:m-8ce177ae5a24\"}"},"creationTimestamp":null,"labels":{"workload.user.cattle.io/workloadselector":"statefulSet-default-test"}},"spec":{"affinity":{},"containers":[{"args":["/sbin/init"],"image":"test:1.0","imagePullPolicy":"IfNotPresent","name":"test","ports":[{"containerPort":3306,"name":"3306tcp01","protocol":"TCP"},{"containerPort":3306,"name":"3306tcp02","protocol":"TCP"}],"resources":{},"securityContext":{"allowPrivilegeEscalation":true,"capabilities":{},"privileged":true,"readOnlyRootFilesystem":false,"runAsNonRoot":false},"stdin":true,"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","tty":true,"volumeMounts":[{"mountPath":"/var/lib/mysql","name":"db"}]}],"dnsPolicy":"ClusterFirst","hostname":"test","nodeName":"testhost","restartPolicy":"Always","schedulerName":"default-scheduler","securityContext":{},"terminationGracePeriodSeconds":30,"volumes":[{"name":"db","persistentVolumeClaim":{"claimName":"test"}}]}},"updateStrategy":{"type":"RollingUpdate"}},"status":{"replicas":0}}'
  creationTimestamp: 2018-06-27T08:50:10Z
  generation: 2
  labels:
    workload.user.cattle.io/workloadselector: statefulSet-default-test
  name: test
  namespace: default
  resourceVersion: "277941"
  selfLink: /apis/apps/v1beta2/namespaces/default/statefulsets/test
  uid: 19964b3b-79e7-11e8-a8ee-000c29f16195
spec:
  podManagementPolicy: OrderedReady
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      workload.user.cattle.io/workloadselector: statefulSet-default-test
  serviceName: ""
  template:
    metadata:
      annotations:
        field.cattle.io/ports: '[[{"containerPort":3306,"dnsName":"test-nodeport","kind":"NodePort","name":"3306tcp01","protocol":"TCP","sourcePort":0},{"containerPort":3306,"dnsName":"test","kind":"ClusterIP","name":"3306tcp02","protocol":"TCP","sourcePort":0}]]'
        workload.cattle.io/state: '{"aXRrYmRvYzE=":"c-ppdgd:m-ffc4c7e082b8","aXRrYmRvYzI=":"c-ppdgd:m-8ce177ae5a24"}'
      creationTimestamp: null
      labels:
        workload.user.cattle.io/workloadselector: statefulSet-default-test
    spec:
      affinity: {}
      containers:
      - image: test:1.0
        imagePullPolicy: IfNotPresent
        name: test
        ports:
        - containerPort: 3306
          name: 3306tcp01
          protocol: TCP
        - containerPort: 3306
          name: 3306tcp02
          protocol: TCP
        resources: {}
        securityContext:
          allowPrivilegeEscalation: true
          capabilities: {}
          privileged: true
          readOnlyRootFilesystem: false
          runAsNonRoot: false
        stdin: true
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        tty: true
        volumeMounts:
        - mountPath: /var/lib/mysql
          name: db
      dnsPolicy: ClusterFirst
      hostname: test
      nodeName: testhost
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30
      volumes:
      - name: db
        persistentVolumeClaim:
          claimName: test
  updateStrategy:
    type: RollingUpdate
status:
  collisionCount: 0
  currentReplicas: 1
  currentRevision: test-584b7f998c
  observedGeneration: 2
  readyReplicas: 1
  replicas: 1
  updateRevision: test-584b7f998c


Serialization exception for Metrics endpoint

Expected Behavior
Using micronaut-management and the /metrics endpoint should work with micronaut-serialization
Result using micronaut-jackson-databind
{
"names": [
"executor",
"executor.active",
"executor.completed",
"executor.pool.core",
"executor.pool.max",
"executor.pool.size",
"executor.queue.remaining",
"executor.queued",
"jvm.buffer.count",
"jvm.buffer.memory.used",
"jvm.buffer.total.capacity",
"jvm.classes.loaded",
"jvm.classes.unloaded",
"jvm.gc.live.data.size",
"jvm.gc.max.data.size",
"jvm.gc.memory.allocated",
"jvm.gc.memory.promoted",
"jvm.gc.pause",
"jvm.memory.committed",
"jvm.memory.max",
"jvm.memory.used",
"jvm.threads.daemon",
"jvm.threads.live",
"jvm.threads.peak",
"jvm.threads.states",
"logback.events",
"process.cpu.usage",
"process.files.max",
"process.files.open",
"process.start.time",
"process.uptime",
"system.cpu.count",
"system.cpu.usage",
"system.load.average.1m"
]
}

Actual Behaviour
The metrics endpoint result in
Caused by: io.micronaut.core.beans.exceptions.IntrospectionException: No serializable introspection present for type MetricNames. Consider adding Serdeable. Serializable annotate to type MetricNames. Alternatively if you are not in control of the project's source code, you can use @SerdeImport(MetricNames.class) to enable serialization of this type.
The /health endpoint now works from RC1
Steps To Reproduce

Use https://github.com/lind/serialization
Start app
http://localhost:8080/metrics

Environment Information
OS: MacOS
JDK: openjdk 17.0.2 2022-01-18
Example Application
https://github.com/lind/serialization
Version
3.3.3

A workaround is to add @SerdeImport(MetricsEndpoint.MetricNames.class) to the Application class.


[Event Request] Report::"Whse. Get Bin Content" - OnBinContenOnAfterGetRecordOnAfterCalcShouldSkipReportForQty

Describe the request
I need new parameters in the publisher Report::"Whse. Get Bin Content" OnBinContenOnAfterGetRecordOnAfterCalcShouldSkipReportForQty
Additional context
trigger OnAfterGetRecord()
var
DummyItemTrackingSetup: Record "Item Tracking Setup";
ShouldSkipReportForQty: Boolean;
begin
if BinType.Code <> "Bin Type Code" then
BinType.Get("Bin Type Code");
if BinType.Receive and not "Cross-Dock Bin" then
CurrReport.Skip();
            QtyToEmptyBase := GetQtyToEmptyBase(DummyItemTrackingSetup);
            ShouldSkipReportForQty := QtyToEmptyBase <= 0;

           OnBinContenOnAfterGetRecordOnAfterCalcShouldSkipReportForQty("Bin Content", ShouldSkipReportForQty, DestinationType2, WhseWorksheetLine, WhseInternalPutawayLine, ItemJournalLine, TransferLine, InternalMovementLine);

           OnBinContenOnAfterGetRecordOnAfterCalcShouldSkipReportForQty("Bin Content", ShouldSkipReportForQty, DestinationType2, WhseWorksheetLine, WhseInternalPutawayLine, ItemJournalLine, TransferLine, InternalMovementLine, PostingDate, DocNo);
          if ShouldSkipReportForQty then
              CurrReport.Skip();

          case DestinationType2 of

[IntegrationEvent(true, false)]

local procedure OnBinContenOnAfterGetRecordOnAfterCalcShouldSkipReportForQty(var BinContent: Record "Bin Content"; var ShouldSkipReportForQty: Boolean; DestinationType2: Enum "Warehouse Destination Type 2"; WhseWorksheetLine: Record "Whse. Worksheet Line"; WhseInternalPutawayLine: Record "Whse. Internal Put-away Line"; ItemJournalLine: Record "Item Journal Line"; TransferLine: Record "Transfer Line"; InternalMovementLine: Record "Internal Movement Line")

local procedure OnBinContenOnAfterGetRecordOnAfterCalcShouldSkipReportForQty(var BinContent: Record "Bin Content"; var ShouldSkipReportForQty: Boolean; DestinationType2: Enum "Warehouse Destination Type 2"; WhseWorksheetLine: Record "Whse. Worksheet Line"; WhseInternalPutawayLine: Record "Whse. Internal Put-away Line"; ItemJournalLine: Record "Item Journal Line"; TransferLine: Record "Transfer Line"; InternalMovementLine: Record "Internal Movement Line"; PostingDate: Date; DocNo: Code[20])

begin
end;
Internal work item: AB#557531

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 26919.


Improve icons / thumbnails scaling

the icons and thumbnails do not scale very well, when they are large the quality is very bad
Windows File explorer VS. Files UWP:

Maybe this is useful? https://devblogs.microsoft.com/oldnewthing/20140120-00/?p=2043

@XPoppyX This appears to be resolved with v1.0, can you let us know if it's still an issue on your end?

@XPoppyX This appears to be resolved with v1.0, can you let us know if it's still an issue on your end?

Yes, it looks much better. Now this is the only thing I notice:
They look a bit pixelated compared to the native file explorer
Files:

File explorer:

Files:

File explorer

It is even more noticeable in other images
I don't know if I should open a new issue about this, what do you think?

Yes, it looks much better. Now this is the only thing I notice:
They look a bit pixelated compared to the native file explorer
Files:

File explorer:

Files:

File explorer

It is even more noticeable in other images
I don't know if I should open a new issue about this, what do you think?

@XPoppyX Hey Richard. I'm going to close this since we fixed the larger issue. I believe the pixelation is due to very slight differences in how the xaml image for the icons are stretched vs the thumbnail size requested. It doesn't look very noticeable to me, but if you find a scenario which has icons rendered in an unacceptable way please open a feedback item for it.

@XPoppyX Hey Richard. I'm going to close this since we fixed the larger issue. I believe the pixelation is due to very slight differences in how the xaml image for the icons are stretched vs the thumbnail size requested. It doesn't look very noticeable to me, but if you find a scenario which has icons rendered in an unacceptable way please open a feedback item for it.


Add an E-Commerce Sneaker Site

Sneaker Site
Project Description

A really cool shoe site with a lot of features, eg: By clicking on "Buy Now" a modal opens in which the user can enter their information.
Checkout the site here

Demo:
https://user-images.githubusercontent.com/78037846/156029925-d16a69f3-fc60-4a6a-b0de-206b2e6367da.mp4
Stack:

[] Html
[] CSS
[] JavaScript

Hey @Adit0507 , i want to work on this , assign it to me under gssoc'22.

I'm a contributor, and I raised the issue so I wish to work on this

@Adit0507 you have raised many issue. But at a time , only 3 issues will be assigned to a contributor.

Hey @Adit0507 , i want to work on this , assign it to me under gssoc'22.

@Anish1411 you can create any other issue.

@Adit0507 you have raised many issue. But at a time , only 3 issues will be assigned to a contributor. First you can complete those issue, then I will assign it to you.

Yes

I have finished my previous 3 issues, now you can assign me this one


No whitespace after if/for/foreach/while etc

Currently whitespaces are added for:

if ()
for ()
foreach ()
while ()
catch ()
...

This is not true. I'm pretty sure you accidentally ran the PSR-2 fixer script. Our CS fixer does not change this (but it doesn't enforce anything either).

Should we enforce it then? :)

But… it's not consistent everywhere. So we should create a new fixer for that :-p.

Yup, would be nice to have it cleaned up everywhere :)

:+1: for a fixer ;)

Ok @fruux/developers, this aint right.
For some reason I:

Never have a space after while, foreach, do, for.
always have a space after if.

I don't know why either, but removing the space after the if looks very ugly to me :S It would be a bit weird to exclude if from the list, so how about we do the opposite anyway? Consistently add a space after every control structure.

As long as it's consistent, it's fine for me. :)
There may be a built-in fixer than that is able to do that.

+1 for adding space!

Spaces everywhere please. Else, it's not consistent :-].

I think you guys need to make up your mind about the rules first, make a final decision and then someone should implement it. ;)
/cc @fruux/developers

Simple. Make a vote.

whitespace after structure controls, so:

```php
if ()
elseif ()
foreach ()
switch ()
while ()
…
```

no whitespace after structure controls, so:

```php
if()
elseif()
foreach()
switch()
while()
…
```

I vote :one:.

I vote :one:.
And if I understand @evert comment correctly, he would go for it, too. (If only he doesn't want to remove the whitespace in if ():

I don't know why either, but removing the space after the if looks very ugly to me :S It would be a bit weird to exclude if from the list, so how about we do the opposite anyway? Consistently add a space after every control structure.

If it ends up being one, there's #15.

Also vote 1

Closed via #15.


A.16.IR21.temporal.reference.node

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685
Comment
Ambiguity: This testcase as written now is already covered by test case A.15.IR20. It seems that this test case should be about the temporal extent (as a period).
Also, as it is no, it is not clear under which conditions this test case fails.
This test case only needs to be executed in the context of 'scenario 2'.
Proposed Change
Merge with test case A.15.IR20 and clarify in which cases (creation date, publication data, date of last revision, temporal extent) the test should fail. Please note that the combination of the requirements from the INSPIRE Metadata IR and ISO19115 make that the presence of temporal extent does not affect the outcome of the test.
NB: also in IR21, the word temporal extent should be added (as it is implied).

Not sure if IR 21 is the same as IR 20 (there is an ambiguity issue with 20 that needs resolution first).
IR 21 only applies to a scenario 2 response, but IR 20 may apply to either scenario.
As IR 21 explicitly mentions WMS 1.3.0 what are the implications for a service using WMS 1.1.1?

Rephrased test method as follows:
Check that if a TemporalExtent element exists, that it is contained within the TemporalReference node of the ExtendedCapabilities section.
This way the test case for IR21 is distinctly different from the one for IR20.
Also, implemented precondition that test case metadataURL.node must indicate scenario 2


Color icon is not shown when a color value selected in CSS

VSCode Version: Alpha
OS Version: OSX 10.11.5

Steps to Reproduce:

Open a CSS file
Under a rule set, type a rule say color: red;

Expected: To see the red icon before red label
Actual: Not seeing any color icon
Additional Information: Color icon is getting rendered if I reopen the file or tabbing to another file and tabbing to the css file.

@aeschli I am wondering if it used to work before

I checked and it is a regression. It is working as expected here - 5d2d6530905ed13c6d534c3c8a020f650d7ac015

@alexandrudima Alex, can you have a look? 8913a2 introduces the problem.
The _contentChangedScheduler is no longer fired when typing.

Adding
						case editorCommon.EventType.ModelContentChanged2:
							this.emit(editorCommon.EventType.ModelContentChanged2, e);
							break;

in the comonCodeEditor.ts, line 860 seems to fix the issue.

Yes, that is the problem. Great catch!

Verified


Preserve tool-specific config files

closes #384

Codecov Report

Merging #410 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #410   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           11        11
  Lines          507       515    +8
=========================================
+ Hits           507       515    +8

Impacted Files
Coverage Δ

nbqa/__main__.py
100.00% <100.00%> (ø)

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 bef2ffc...727b62d. Read the comment docs.


Blacklist does not work on Amazon website

New Issue Checklist (tick off like this: [x])

[x] I checked existing issues (open and closed) for possible duplicates
[x] I can reproduce the problem on the latest stable version (not nightly!)
[x] If you have a problem a specific website: adding the domain to your no-skip-urls-list does not solve the problem
[x] The issue is not about adding entries to the default no-skip-urls-list

What is your browser?

[x] Firefox
[ ] Chrome

What is your operating system?

[ ] Linux
[ ] Mac
[x] Windows

Description (please include examples/screenshots where applicable)
I want to sort Amazon search results by price in ascending order. E.g. https://www.amazon.de/s?k=bluetooth+headset+in+ear&rh=p_72%3A419117031&s=price-asc-rank&dc
If Skip Redirect is turned off, this will work. When Skip Redirect is turned on, it does not work.
After I put "/www.amazon" in the blacklist, the sorting is still not done. Also "www.amazon" does not work.
If the sample seems to work, change the sorting and it will fail.

If anything, it's probably amazon.de you need to add, but for me sorting results doesn't work at all with Chrome, even without extensions.


fix(sem-rel): Adding semantic release to Travis

:tada: This PR is included in version 1.1.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


pl.stringx fixes

This PR fixes some tiny bugs, removes some unused things, adds some functionality for consistency (last argument for lfind, array of prefixes as argument for startswith), fixes documentation, adds tests, etc. See diffs and commit messages for details.
It seems there are some issues with various functions for splitting, and I'm not sure how to fix them as intended behaviour deviates from similar functions in Python's standard library. For instance, stringx.splitlines deliberately returns {""} when splitting an empty string (link) which contradicts Python's docs: 2.7 3.4.

Any comment on this?

Thanks, Peter: sorry for taking my time.  I see the stringx.splitlines issue and note that it is a workaround, not a good thing to find in any code base! I will review this. Generally conforming to the Python docs seems a good idea.

No problem. I think there are a lot of little fixes like this that can be applied to PL itself and related areas like cleaning up old github issues and pull requests, adding automated testing with travis-ci, updating README, etc. I'm glad that you are more active now, but perhaps you could get more maintainers anyway. Maybe keplerproject team could help, and I'd be willing, too.


Not able to load Project List

Hi Good day, I have followed the setup described but currently am not able to load any projects.
Meaning, on the project tab the list is empty and I am seeing error messages like
"You don't have any drawings in your package."
Is there anything I am doing wrong, or how should I make sure the app sees the projects.
I am able to access the projects in the appsettings.json from my browser and can download them but I am not able to load them in the system.
please assist.
Thanks

Hi @Gnyasha , I would like to ask you if you could provide me more information about your problem. I tried it on my machine and cannot reproduce it. If you can send me your report Log file and a screenshot of the error that will help us to understand the problem.
Thank you a lot


The insert_doc_table method of PGvectorConnection in ogbujipt.embedding_helper doesn't take advantage of native string escaping

The PG Vector embedding helper is very helpful for inserting corpora embeddings into Postgres instances and I have been using it for this purpose.  However, it doesn't seem to able to handle text such as:

Structure of visceral layer of Bowman's capsule is a glomerular capsule structure and a structure of epithelium.

In particular, it looks like the apostrophe is an issue causing the raising of the PostgresSyntaxError error:

File [..]ogbujipt/embedding_helper.py:208, in PGvectorConnection.insert_doc_table(self, table_name, content, permission, title, page_numbers, tags)
205 SQL_page_numbers = "{{{}}}".format(", ".join(map(str, page_numbers)))
206 SQL_tags = "{{{}}}".format(", ".join(map(str, tags)))
--> 208 await self.conn.execute(
209     INSERT_DOC_TABLE.format(
210         table_name = table_name,
211         embedding = content_embedding,
212         content = content,
213         permission = permission,
214         title = title,
215         page_numbers = SQL_page_numbers,
216         tags = SQL_tags
217         )
218     )
File [..]asyncpg/connection.py:317, in Connection.execute(self, query, timeout, *args)
314 self._check_open()
316 if not args:
--> 317     return await self._protocol.query(query, timeout)
319 _, status, _ = await self._execute(
320     query,
321     args,
(...)
324     return_status=True,
325 )
326 return status.decode()
File [..]/asyncpg/protocol/protocol.pyx:338, in query()
PostgresSyntaxError: syntax error at or near "s"

Looking at the way that method is implemented against asyncpg's usage documentation, which shows how SQL query parameters can be sent to the connection execute method (a bonus step towards protection against SQL injection), it seems the insert_doc_table method should be modified to execute parameterized postgres queries to handle situations like this rather than naive, python string formatting of the SQL INSERT query

Yeah, we absolutely should not be using basic Python string formatting to construct queries. I still haven't had a chance to code review the PGVector bits, so good catch.

@chimezie you working on this, or do you want me to have a go?

Can you give it a go?  I tried the change below earlier:
diff --git a/pylib/embedding_helper.py b/pylib/embedding_helper.py
index 620842d..0df8c3c 100644
--- a/pylib/embedding_helper.py
+++ b/pylib/embedding_helper.py
@@ -72,14 +72,7 @@ INSERT INTO {table_name} (
     title,
     page_numbers,
     tags
-) VALUES (
-    '{embedding}',
-    '{content}',
-    '{permission}',
-    '{title}',
-    '{page_numbers}',
-    '{tags}'
-);\
+) VALUES ($1, $2, $3, $4, $5, $6)
 '''

 SEARCH_DOC_TABLE = '''\
@@ -199,24 +192,14 @@ class PGvectorConnection:
             raise ConnectionError('Connection to database is closed')

         # Get the embedding of the content as a PGvector compatible list
-        content_embedding = list(self._embedding_model.encode(content))
+        content_embedding = self._embedding_model.encode(content)

         # Get the page numbers and tags as SQL arrays
         SQL_page_numbers = "{{{}}}".format(", ".join(map(str, page_numbers)))
         SQL_tags = "{{{}}}".format(", ".join(map(str, tags)))
+        await self.conn.execute(INSERT_DOC_TABLE.format(table_name=table_name), content_embedding.tolist(), content,
+                                permission, title, SQL_page_numbers, SQL_tags)

-        await self.conn.execute(
-            INSERT_DOC_TABLE.format(
-                table_name = table_name,
-                embedding = content_embedding,
-                content = content,
-                permission = permission,
-                title = title,
-                page_numbers = SQL_page_numbers,
-                tags = SQL_tags
-                )
-            )
-
     async def search_doc_table(
             self,
             table_name: str,

But still get:

File "/home/chimezie/miniconda3/envs/OgbujiPT-py-3.10/lib/python3.10/site-packages/ogbujipt/embedding_helper.py", line 200, in insert_doc_table
await self.conn.execute(INSERT_DOC_TABLE.format(table_name=table_name), content_embedding.tolist(), content,
File "/home/chimezie/miniconda3/envs/OgbujiPT-py-3.10/lib/python3.10/site-packages/asyncpg/connection.py", line 319, in execute
_, status, _ = await self._execute(
File "/home/chimezie/miniconda3/envs/OgbujiPT-py-3.10/lib/python3.10/site-packages/asyncpg/connection.py", line 1659, in _execute
result, _ = await self.__execute(
File "/home/chimezie/miniconda3/envs/OgbujiPT-py-3.10/lib/python3.10/site-packages/asyncpg/connection.py", line 1684, in __execute
return await self._do_execute(
File "/home/chimezie/miniconda3/envs/OgbujiPT-py-3.10/lib/python3.10/site-packages/asyncpg/connection.py", line 1731, in _do_execute
result = await executor(stmt, None)
File "asyncpg/protocol/protocol.pyx", line 183, in bind_execute
File "asyncpg/protocol/prepared_stmt.pyx", line 197, in asyncpg.protocol.protocol.PreparedStatementState._encode_bind_msg
asyncpg.exceptions.DataError: invalid input for query argument $1: [0.0005201358580961823, -0.0375559926033... (expected str, got list)

And

asyncpg.exceptions.DataError: invalid input for query argument $1: array([ 5.20135858e-04, -3.75559926e-02,... (expected str, got ndarray)

When I directly pass in the instance of numpy.ndarray directly output from encoding the text (using the 'all-MiniLM-L12-v2' embedded model ), even though this suggests that asyncpg should be able to handle lists as parameterized query arguments.  I don't see a vector in the list of PostgreSQL types in that table, but the original code is able to insert embeddings of text without characters needing escaping, so I'm not sure at this point, and I have done a decent amount of digging.

Installing pgvector-python and using its register_vector method seemed to do the trick.  Once I registered the vector with the DB connection, I was able to call a parameterized execute method on the connection, passing in the arguments directly (including the nparray embedding of the text), removing the tag and page number escaping, etc.
I had to implement it in a separate code and will post a diff back here.  I can put this solution in a separate branch with a test case.

As a separate note/bug/feature request, PGvectorConnection should have an insert_doc_tables (plural) method that leverages the connection.executemany(..) to efficiently insert multiple embeddings at once, which I imagine will be the primary use case.

I had to implement it separately and can post a diff here or put this solution in a separate branch with a test case.

Hey, sorry, just sitting down to look at this now. Sure, could you create a new branch off this ticket? I actually I just did that. Could you do:
git fetch origin
git checkout 45-pgvector-insert

And commit those changes there? I'll review, and maybe add to the test cases. Thanks!
Also, sounds like we have a new dependency? I think we might want now to have a requirements-pgvector.txt

Working on this, and I'm thinking of refactoring PGvectorConnection. ISTM it is mainly encapsulating 3 things: PG connection, embedding_model & table name. The latter is kinda submarined by being a required parameter for each call, and that was the first thing that I found itchy.
I think what I want is to rename PGvectorConnection to PGvectorHelper (reluctantly doing the HumpCase) be initialized with all three of these params, but as a convenience for the case where you do* want to share an embedding & connection but have multiple table names, etc., have a new_helper() method which allows you to create the same setup, but with a different table name.
Just jotting down the idea for any feedback, esp. from @choccccy & @chimezie. If no objections I'll finish up in the morning.

That would be a good idea.

The changes look good to me.  There was one issue with docDB.insert_docs() that I fixed, tested, and pushed to be4ce30.  Seems to be working with that fix

i added a job to .github/workflows/yaml that spins up a pgvector docker container that allows the testing suite to connect to a mock pgvector database. I added a simple mock test to test_pgvector.py that mirrors the actions in test_text_w_apostrophe.ipynb. It's failing currently, but other tests still pass as expected. I'm leaving test_PGv_embed_poem() alone for now, will take another look at it tomorrow.

Closing now that @choccccy and I are done and the tests are passing with new changes.


Remove mentions of exclude_paths

Exclude paths have been deprecated for some time. To avoid confusion, I
think it's time we remove them completely.
This justifies a version bump to 0.2.0 as well, I think.

LGTM cc: @mrb

@wfleming I'm +1 on the change and the bump to 0.2.0, but I think we need to read through the whole SPEC again to make sure it's coherent with this change - did you do that or should I do a run through as well?

@mrb I was focused mainly on the flow between the Input & Which files to analyze sections, but I did do a quick read through of the rest of the doc as well. I didn't notice anything that conflicted with this,


(HTTP code 404) unexpected - {"message":"manifest for fecshop/fecshop:latest not found"}

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

i can search this image ,but i can not install it.

the keyword is "fecshop"

I tried to download the image "cakephp" but got the same problem.
Why is listed if you get an error 404?

Go to https://hub.docker.com/r/fecshop/fecshop/tags/
Observe no latest tags were created for that image
Select a different tag in Kitematic (if one exists)
🎉  enjoy container running.

Ideally you open an issue with the repo owner to let them know how frustrating it is that they don't have a latest image tagged


aws cli expects AWS_DEFAULT_REGION

Very useful tool, just discovered one small thing, it appears the expected env var is AWS_DEFAULT_REGION instead of AWS_REGION.
p.s. also discovered a neat bonus feature, that if you're juggling multiple accounts (e.g. home, work) and want to use a profile besides default, you can invoke assume-role like:
AWS_PROFILE=your-non-default-profile assume-role your-account your-role your-code

Great stuff, thanks!

Hey, thanks for pointing out the bug. I am currently, writing a PR to fix the issue, should have that out today.
Also great demonstration of another way to use the tool.
Cheers!

I also stumbled into this. It might be useful for it to print which profile it's using as it took me a bit to realize I had to set that for this. It might also be nice to be able to specify the profile to use as an arg/flag.


Allow the same OIDC configuration target multiple HTTPRoutes

Initially raised by @sadovnikov in https://github.com/envoyproxy/gateway/issues/2913. Spit it out since it's another issue.
The biggest inconvenience for us is the need to register in IDP additional allowed redirect URIs for every new service deployment, which can happen even from a fix/feature branch. And, of course, the cleaning up IDP upon removal of the temporary deployments.
Attaching OIDC security policies to Gateways (all HTTP Routes of the gateway) will lead to finding a way to detach them from HTTP Routes, which do not require oauth2 authentication. These are "welcome" pages with invitations to log in. Other examples are health and metrics probes, covered or not by JWT security policies.
I tried a workaround with a fallBack HTTP route on / and a fallback security policy with the identical configuration of the OIDC issuer. It failed with "too many redirects" because, I think, the two filters used different cookies and hmac secrets.
Gateway
  HTTPRoute /myapp
  FallBackRoute /. (using service without any endpoints)

  SecurityPolicy
    target:  HTTPRoute
    OIDC:
      issuer ...
      redirectURL  https://www.example.com/oauth2/callback     # without /myapp in the path

  SecurityPolicy (fallback)
    target:  FallBackRoute
    OIDC:
      issuer ...
      redirectURL  https://www.example.com/oauth2/callback     # without /myapp in the path

Should OIDC configuration be extracted into a separate resource? Then, security policies can reference both HTTP Route and the filter

Gateway API is changing support multiple targetRefs. However, using selector on labels instead of targetRefs[] is more in Kubernetes style and would allow pre-configuring the security policy for HTTP Routes, which can be created later.

Gateway API is changing support multiple targetRefs. However, using selector on labels instead of targetRefs[] is more in Kubernetes style and would allow pre-configuring the security policy for HTTP Routes, which can be created later.

I prefer to keep it aligned with gateway API, but let's discuss it in next week's meeting.

Close this as both TargetSelectors and TargetRefs have been supported in the SP target.


Enhancement: Preferred kernel auto picking

Currently in VS Code when users open a notebook document, they don't need to pick a kernel manually only in following two scenarios:

The notebook was opened before and users run the notebook against a kernel already. That kernel will be picked automatically, no other kernel would replace it unless users pick one manually.
There is only one kernel contributed to this notebook.

When users run a cell, and there is still only one kernel, the kernel will be used.
Before users run any cell, and there are more than one kernel, the kernel picker will not show any active kernel info (it shows "Select kernel" instead).

Above two scenarios cover two use cases: open an existing notebook, or work on single controller notebook (e.g., GitHub issue notebook). However this doesn't cover two common workflow

Users open their existing Jupyter notebook (created through other Jupyter frontend/service) in VS Code
Users create new Jupyter notebooks when they have already specified their preferred kernel

Especially that VS Code is still growing to be one of data scientists' Jupyter frontend/editor, almost every new users will run into workflow 1 and do manual kernel picking though often Jupyter has a good guess which kernel is preferred for current document, and also every existing would run into workflow 2.
The concrete issues reported:

[AZML/Open in VS Code] on AZML website, click open in VS Code, it opens a remote window and opens the notebook document in the editor. No kernel is not picked though users already specify one in AZML website.
Create notebook A in File Explorer, pick a kernel. Create notebook B in File Explorer, the kernel info is back to "Select Kernel" again. https://github.com/microsoft/vscode/issues/134830#issuecomment-987075441
Create untitled notebook in Editor Area, pick a kernel and run. Save as a new notebook document on disk, the new document has no selected kernel. https://github.com/microsoft/vscode-jupyter/issues/9512
Julia. Create a notebook in JuliaLab, specify a kernel. Open the notebook then in VS Code, preferred kernel not selected. https://github.com/microsoft/vscode/issues/131370

Proposals
For AZML/Julia users, they are mostly working on single language notebook (other than polyglot), meaning the notebook serializer is the ipynb extension we ship out of the core, and kernels/controllers are contributed by a single notebook extension installed from the marketplace (Julia, or .NET, or Jupyter). If this is the case, we can pick the kernel whose affinity is the only highest without prompting users to pick one.
cc @jrieken @mjbvz @DonJayamanne @roblourens

Had discussions with @mjbvz about this. In addition to the proposal mentioned above (optimizing the single extension contributing multiple kernels scenario), another idea came out of our discussions:

Allow users to choose the default kernel. One example is users have both Jupyter and Julia extensions and both of them contribute notebook controllers for Julia execution. Users might have their preference for the default kernel, allowing them to specify which kernel should be the default can help avoid users picking the default kernel in every newly opened notebook.

I thought about filing a new feature request on this. But it seemed better to keep the discussion contained here, at least for now. In particular it relates to the last comment about selecting a default kernel as well as the Gear icon for the notebook controller. Speaking personally, the majority of my issues with kernel selection would be alleviated by the ability to select a kernel to be my default, auto-selected kernel at both the global level with the ability to override it at the workspace / resource level, just like the rest of VS Code settings.
All the rest of selection could work like it currently does. But I want the ownership to be able to explicitly specify kernel selection with some type of manual affordance that always trumps any type of heuristics or metadata or forcing a manual selection. At a surface level I like it as just a setting, but the issue here is that controller IDs are not something that's exposed to the User. The Gear icon might be the right place to surface this, and might have even been what the Gear icon did before (it does nothing now for me in insiders).

But I want the ownership to be able to explicitly specify kernel selection with some type of manual affordance that always trumps any type of heuristics or metadata or forcing a manual selection. At a surface level I like it as just a setting, but the issue here is that controller IDs are not something that's exposed to the User

Agree 100%. Even though we could save the controller id to settings when users use the gear icon, it's not great as users won't be able to read or tweak this specific setting as the controller ids are not always human readable.
With that said, we could tackle this differently to archive the same thing, instead of asking controller id, we could ask users if they want to use the lastly used controller, use a controller suggested by extensions always, use a controller which matches the workspace stats the most (use Julia controller if the workspace stats are all around Julia files).

Agree 100%. Even though we could save the controller id to settings when users use the gear icon, it's not great as users won't be able to read or tweak this specific setting as the controller ids are not always human readable.

Yeah, that's the challenge here. Controller ids aren't nice to read and not guaranteed to be constant. A better concept is user state, e.g mementos, which also roam across machines. Something already exists but it isn't utilised properly and might need further tweaking. The NotebookKernelService knows and persists what kernel was used most recently for what notebook type. Maybe it's enough to make more brave kernel selections based on that information


Upgrade fs2 to 0.10.0-M9

Everything compiles, but tests needs updated jawn-fs2 and fs2-reactive-streams.

[ ] jawn-fs2
[x] fs2-reactive-streams

This looks good to me.  I agree with your comment on gitter:

there’s a lot of Chunk[Byte] around that are from before segment was introduced
since we rarely do index-based access, I think those should be Segment[Byte, Unit] instead

jawn-fs2-0.12.0-M4 is released.


Enable CSI testing for GCP

driver: pd.csi.storage.gke.io for volumeSnapshotClass
storageClassName: standard-csi

Codecov Report

Merging #744 (6a82523) into master (5b41bea) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #744   +/-   ##
=======================================
  Coverage   36.96%   36.96%
=======================================
  Files          16       16
  Lines        3219     3219
=======================================
  Hits         1190     1190
  Misses       1926     1926
  Partials      103      103

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 5b41bea...6a82523. Read the comment docs.

/test 4.10-operator-e2e-aws

/LGTM


Bug: Curly brace deprecation

Upcoming 7.4 changes:
system/Entity.php, line 605: Array and string offset access syntax with curly braces is deprecated

@MGatner can you please merge above PR?

Yep! Thanks for this.

Resolved by #2432


Fixing bug that made masked view unresponsive after re-attaching

Overview

When including a masked-view in one route (using a library like react navigation), and the user navigates to a new route on the stack and presses the back button, the masked-view will not rerender any more.
The problem is that the bitmap invalidation does not happen when the view is attached to the window. Causing calls of React native to dispatchDraw to not actually draw, keeping this component in a permanent state of mBitmapMaskInvalidated = false;

@Naturalclar This fixes a critical bug that was caused by #98 , it would be great if this can be merged quickly 😄

@tdekoning thanks for the ping! I'll try to take a look at this tonight

This fix has been published in v0.2.2 :tada:


Lack of TripletLoss.py ?

It seems there is no 'TripletLoss.py' in the folder. Could you upload this python file?

Hi, I think I missed this file when I first committed. I've uploaded it.


Add cli lint option to treat warnings as errors

Add option treat warnings as errors for pipeline linter

should fail and pass after  #4372 merged ...

https://ci.woodpecker-ci.org/repos/3780/pipeline/22592/34 FAILED SUCCESSFULLY


Language suggestion: shorter function declaration with only one parameter and one line expression

It's just a suggestion for Dart lang, not a bug report. I did not find a way to publish my suggestion, so I file this here.
Arrow functions are good, but it can be shorter when there is only one parameter by using underscore _.
function greeting(name) {
  print("Hello ${name}! How old are you, ${name}?");
}

// It can be shorter using a shorthand syntax.
var foo = (name) => print("Hello ${name}! How old are you, ${name}?");

greeting('John');   // Hello John! How old are you, John?

It can be shorter using underscore _ without (_) => syntax.
var foo = print("Hello ${_}! How old are you, ${_}?");
// same as
var foo = (_) => print("Hello ${_}! How old are you, ${_}?");

When an expression using underscore _, it returns a function which will take only one parameter and pass it to the express. You can use the same parameter in the expression as many times as you want. It might be useful for functional programming.
[1, 2, 3, 4].map((_ + 1) * _);   // [2, 6, 12, 20]
// same as
[1, 2, 3, 4].map((_) => (_ + 10) * _);

This suggestion is reminiscent of https://github.com/dart-lang/language/issues/265 (and a number of other language requests in the language repository). So, it is something we are aware of.
One issue with the proposed syntax is that it's not clear where to insert the implicit (_) =>.
In [1, 2, 3, 4].map((_ + 1) * _), it is possible to insert it in many places, including:

[1, 2, 3, 4].map((_) => (_ + 1) * _)
[1, 2, 3, 4].map(((_) => _ + 1) * (_) => _)
[1, 2, 3, 4].map((((_) => _) + 1) * (_) => _)
(_) => [1, 2, 3, 4].map((_ + 1) * _)

Most of these can be rejected from the type, but it's dangerous to have a syntax where you can't parse until you have typed the syntax, because typing usually depends on the parsing.
We need to insert an implicit delimiter, and without any guidance, there is a lot of places where it can be inserted. That's why it's a good idea to require the user to tell us where it goes.

@lrhn, Thanks for your reply!


Create: 0101-symmetric-tree.java

File(s) Modified: 0101-symmetric-tree.java
Language(s) Used: java
Submission URL: _https://leetcode.com/problems/symmetric-tree/submissions/1184662294_ _https://leetcode.com/problems/symmetric-tree/submissions/1184662451_

Important
Please make sure the file name is lowercase and a duplicate file does not already exist before merging.

Do I need to make some modifications, or is this ok?

Hi, thank you for the contribution. Sorry for the late catch up. Looks like other PR have already filled in for the solution. So, let me close this PR this time. We will be looking forward to be able to merge other missing solutions!


NEVER MERGE: Show how mondo-edit based subclass sync would look like

Shows how mondo-edit based subclass sync would look like. The subclass-sync pipeline is run using the updated mondo-ingest confirmations which only use mondo-edit, not mondo.owl.

Closed in favour of #7801


feat: dynamically adjust disk buffer size according file size

This PR can reduce disk I/O

Codecov Report
Attention: Patch coverage is 0% with 5 lines in your changes are missing coverage. Please review.

Project coverage is 88.62%. Comparing base (844721e) to head (01e07f0).
Report is 1 commits behind head on main.

Files
Patch %
Lines

.../cache/data_store_cache/memdisk/data_store/disk.rs
0.00%
1 Missing and 4 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #51      +/-   ##
==========================================
- Coverage   88.80%   88.62%   -0.18%
==========================================
  Files          17       17
  Lines        2170     2171       +1
  Branches     2170     2171       +1
==========================================
- Hits         1927     1924       -3
- Misses        130      131       +1
- Partials      113      116       +3

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


[Collections] Export PackageCollectionsSigning as library

We will add signing to the set of collections tools, and for that we'd need PackageCollectionsSigning.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


Jim/who is in the sydney office right now

Fixes #435 Fixes #428

Figure: Change 1: Add a datetime entity for intent redirect. It's used for calculating "today"

Figure: Change 2: Use client now for "today" query

Codecov Report

Merging #436 (13f4142) into main (16f19e1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #436   +/-   ##
=======================================
  Coverage   32.86%   32.86%
=======================================
  Files          76       76
  Lines        2127     2127
=======================================
  Hits          699      699
  Misses       1428     1428

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 16f19e1...13f4142. Read the comment docs.


REPO-4672: Fix URL properties for T-Engines

 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.


Additional fields added to chargeback for container projects

Might fix #8721 and #8722
New Fields:

@gtanzillo Please review
cc @simon3z @sergio-ocon

@miq-bot add_label darga/yes, chargeback, ui, providers/containers

@miq-bot assign zeari

:+1:
@dclarizio @h-kataria @epwinchell can you review?

Closed/reopened PR to kick off Travis

@gtanzillo @chessbyte @simon3z I believe this is mergeable.


Images not showing in rating

i give correct path to the src but images not display

Weird... Could you please reproduce it on a CodePen?
Check this example.

Can't reproduce the issue.


:DevdocsFetch raises "nvim-devdocs: Error when fetching registery, exit code: 2"

I have an error when running the command :DevdocsFetch
First message: "Fetching DevDocs registery..."
And then error message: "nvim-devdocs: Error when fetching registery, exit code: 2"
Setup using Lazy with default config
NVIM v0.9.1
OS: Windows 10 Pro 22H2

The plugin is using curl for making requests and it seems to be an internal error according to this
2 - Failed to initialize. This is mostly an internal error or a problem with the libcurl installation or system libcurl runs in.

I found out that there is a problem with ssl certificates.
Unfortunately, I have not been able to solve it. Is it possible to manually download the necessary files and save them to the appropriate directory?

It's not possible because of the fetched data still needs to be processed before being written to the disk. I'll see if I can do something to fix this.

The problem is solved. Damn antivirus. Issue can be closed

How did this get solved?


Incompat with VeryManyPlayers causing server crash

Describe the bug
More or less what it says on the box! Server crashes and deadlocks on startup, presumably because of a mixin conflict with VMP
To Reproduce
Steps to reproduce the behavior:

Install Carpet, Carpet-fixes, and Very Many Players on a server
Start server
Crash and deadlock, server is unable to stop itself properly and has to be force-stopped (killed)

Expected behavior
No crash, server starts normally and both mods work as intended
Screenshots
n/a
Minecraft Version:

1.18.2
Carpet-Fixes Version:
v1.7.9
Carpet Version:
v1.4.69

Additional context
Server did not generate a crashlog as it didn't properly stop, but here's the spot in the logs where it died: https://mclo.gs/oavKH2T

Should be fixed in the latest release

Ahh, unfortunately that version is for 1.19 and i'm sticking with 1.18.2 for now! Was hoping that there was a fix available for that version but alas not.
Thank you!

I already released a 1.18.2 version with the fix. v1.7.10

Don't worry, I got u xD

Ah! Must not have seen it, completely my bad tysm!

Crashes with a "requires 1.19" error D:
I definitely grabbed the 1.18 one!

Just released v1.7.11 which should fix everything

Thank you! Very sorry for the trouble, i really appreciate this

All good, have fun!


[SEDONA-178] Correctness issue in distance joins

Did you read the Contributor Guide?

Yes, I have read Contributor Rules and Contributor Development Guide

Is this PR related to a JIRA ticket?

Yes, the URL of the assoicated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-178. The PR name follows the format [SEDONA-178] my subject.

What changes were proposed in this PR?
Sedona SQL doesn't rely on Circle for distance joins. Correct results are now produces for all geometry types.
Performance could be improved but would require some refactoring of the spatial partitioning code.
See the jira for discussion.
How was this patch tested?
All unit tests pass. New tests added.
Did this PR include necessary documentation updates?

Yes, I have updated the documentation update.

It locks like r-lib/actions removed the branch "master"
https://github.com/r-lib/actions
https://github.com/r-lib/actions/issues/639

I changed the GitHub Action to r-lib new master branch but failed at some other issues. I will merge this PR anyway as it passed all other tests.


StatefulWidget is not satisfied

Hi, I'm also a Rust Newbie. Not sure if you can help me out, but I get this error when trying to use the throbber:
error[E0277]: the trait bound `Throbber<'_>: StatefulWidget` is not satisfied
   --> src/ui.rs:79:41
    |
79  |             rect.render_stateful_widget(full, chunks[0], &mut throb_state);
    |                  ---------------------- ^^^^ the trait `StatefulWidget` is not implemented for `Throbber<'_>`
    |                  |
    |                  required by a bound introduced by this call
    |
    = help: the following other types implement trait `StatefulWidget`:
              List<'a>
              tui::widgets::Table<'a>
note: required by a bound in `tui::Frame::<'a, B>::render_stateful_widget`
   --> /Users/dreed/.cargo/registry/src/github.com-1ecc6299db9ec823/tui-0.17.0/src/terminal.rs:131:12
    |
131 |         W: StatefulWidget,
    |            ^^^^^^^^^^^^^^ required by this bound in `Frame::<'a, B>::render_stateful_widget`

It doesn't make sense to me. I can clearly see that throbber uses the StatefulWidget trait

This is not clear enough. How are rect, full and throb_state declared?
Maybe it is a lifetime issue.

I upgraded tui from 0.17 to 0.19 and it started working

That was good. Thank you for your service.


Please update the documentation

Hi,
I have recently encountered an issue with the very same symptoms as in https://support.f5.com/csp/article/K26203562.
This was a result of - my guess - providing the public ssh key together with the userpass authentication details.
Is the Public Key parameter still mandatory? The provided examples do not have it declared, however, the documentation still states that it is mandatory.
Could you please update the documentation section: https://github.com/F5Networks/terraform-azure-bigip-module#required-input-variables? Probably this part was omitted in the previous Readme updates, when the key-based authentication was the only way to go (my guess, again).
Cheers

Created [INFRAANO-798] for internal tracking


panic: "we declared a dependency on a crate that doesn't exist in the metadata"

Steps to reproduce the bug with the above code
github.com:steven-omaha/pacdef.git, b6c2ccaf48
cargo semver-checks check-release --workspace --baseline-version 1.1.0
Actual Behaviour
panic
Expected Behaviour
works
Generated System Information
Software version
cargo-semver-checks 0.20.1
Operating system
Linux 6.2.12-arch1-1
Command-line
/home/xxxxxxxx/.cargo/bin/cargo-semver-checks semver-checks --bugreport

cargo version
> cargo -V
cargo 1.69.0 (6e9a83356 2023-04-12)

Compile time information

Profile: release
Target triple: x86_64-unknown-linux-gnu
Family: unix
OS: linux
Architecture: x86_64
Pointer width: 64
Endian: little
CPU features: aes,avx,avx2,bmi1,bmi2,cmpxchg16b,f16c,fma,fxsr,lzcnt,pclmulqdq,popcnt,rdrand,sse,sse2,sse3,sse4.1,sse4.2,ssse3,xsave,xsaveopt
Host: x86_64-unknown-linux-gnu

name = "cargo-semver-checks"
operating_system = "Arch Linux Rolling Release [64-bit]"
crate_version = "0.20.1"
explanation = """
Panic occurred in file '/home/xxxxxxxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-semver-checks-0.20.1/src/rustdoc_cmd.rs' at line 136
"""
cause = "we declared a dependency on a crate that doesn't exist in the metadata"
method = "Panic"
backtrace = """

   0: 0x5594bb2ecbd1 - core::panicking::panic_display::ha103dd28e5023b08
                at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/panicking.rs:147
   1: 0x5594bb2ecb7b - core::panicking::panic_str::h940bf021f492dc8c
                at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/panicking.rs:131
   2: 0x5594ba69fe46 - core::option::expect_failed::h09b982639336e7ea
                at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/option.rs:2045
   3: 0x5594ba7ba0d6 - cargo_semver_checks::rustdoc_cmd::RustdocCommand::generate_rustdoc::he2ad17e5dd8f0b58
   4: 0x5594ba719acb - cargo_semver_checks::rustdoc_gen::generate_rustdoc::ha07547514a3f9461
   5: 0x5594ba71baab - <cargo_semver_checks::rustdoc_gen::RustdocFromProjectRoot as cargo_semver_checks::rustdoc_gen::RustdocGenerator>::load_rustdoc::h8fefc6f3d7b5808e
   6: 0x5594ba843902 - cargo_semver_checks::generate_versioned_crates::hf2793db4cfe56b01
   7: 0x5594ba704746 - <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::fold::haeeebee3bd84e116
   8: 0x5594ba83314d - <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter::h27a4c89c70b7eeeb
   9: 0x5594ba842f39 - cargo_semver_checks::Check::check_release::he1bf3574b10bd9b9
  10: 0x5594ba6b44bf - cargo_semver_checks::main::h441765c803be6ecf
  11: 0x5594ba6aeca3 - std::sys_common::backtrace::__rust_begin_short_backtrace::h06558ff1b73777ff
  12: 0x5594ba6a9dcd - std::rt::lang_start::{{closure}}::hdcffdd593721e77a
  13: 0x5594bb2bd5ac - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::hd6efcd3bec896f2c
                at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/ops/function.rs:287
                 - std::panicking::try::do_call::hce04e543bb1f4cbb
                at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:487
                 - std::panicking::try::h3342dd4e1f680968
                at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:451
                 - std::panic::catch_unwind::h148ce1e59ac0cee7
                at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panic.rs:140
                 - std::rt::lang_start_internal::{{closure}}::h25f9dda2057a67fe
                at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/rt.rs:148
                 - std::panicking::try::do_call::h7caaaeaf9401650b
                at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:487
                 - std::panicking::try::he7d15285746cbbc2
                at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:451
                 - std::panic::catch_unwind::h89fb4f50c0301fe0
                at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panic.rs:140
                 - std::rt::lang_start_internal::h078acd489417d3c1
                at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/rt.rs:148
  14: 0x5594ba6b9625 - main
  15: 0x7f8cf6423850 - <unresolved>
  16: 0x7f8cf642390a - __libc_start_main
  17: 0x5594ba6a04c5 - _start
  18:        0x0 - <unresolved>"""

Build Configuration
[registries.crates-io]
protocol = "sparse"

[target.x86_64-unknown-linux-gnu]
rustflags = ["-Ctarget-cpu=native"]

Additional Context
No response

Hi, thanks for opening the issue and sorry for the bug. pacdef is a cool idea, I'm glad it exists!
This seems to be the same problem as #451, and happens because cargo-semver-checks accidentally attempts to semver-check a bin crate (in this case, pacdef itself).
You should be able to work around this for now by adding --exclude pacdef to your command. When this bug is fixed, will be implied for any crates without a lib target.
If you might be interested in helping fix this bug, I'd be happy to advise and point you in the right direction!

Thanks for the quick reply!

I'm now getting another error that I don't understand. Do you want me to open another issue, or should we keep it here?
$ cargo semver-checks check-release -vvv --workspace --baseline-version 1.1.0 --exclude pacdef
    Updating index
     Parsing pacdef_core v1.2.0 (current)
 Documenting pacdef_core v1.2.0 (/home/ratajc72/rust/pacdef/crates/pacdef_core)
    Finished dev [unoptimized + debuginfo] target(s) in 0.50s
     Parsing pacdef_core v1.1.0 (baseline, cached)
    Checking pacdef_core v1.1.0 -> v1.2.0 (minor change)
    Starting 37 checks, 6 unnecessary
        PASS [   0.001s]       major        auto_trait_impl_removed
        PASS [   0.001s]       major        constructible_struct_adds_field
        PASS [   0.000s]       major        constructible_struct_adds_private_field
        PASS [   0.000s]       major        constructible_struct_changed_type
        PASS [   0.001s]       major        derive_trait_impl_removed
        PASS [   0.000s]       major        enum_marked_non_exhaustive
        PASS [   0.000s]       major        enum_missing
        PASS [   0.000s]       major        enum_repr_c_removed
        PASS [   0.000s]       major        enum_repr_int_changed
        PASS [   0.000s]       major        enum_repr_int_removed
        PASS [   0.000s]       major        enum_struct_variant_field_added
        PASS [   0.000s]       major        enum_struct_variant_field_missing
        PASS [   0.000s]       major        enum_tuple_variant_field_added
        PASS [   0.000s]       major        enum_tuple_variant_field_missing
        PASS [   0.000s]       major        enum_variant_added
        PASS [   0.000s]       major        enum_variant_missing
        PASS [   0.000s]       major        function_const_removed
        PASS [   0.000s]       major        function_missing
        PASS [   0.000s]       major        function_parameter_count_changed
        PASS [   0.000s]       major        function_unsafe_added
        PASS [   0.001s]       major        inherent_method_const_removed
        PASS [   0.000s]       major        inherent_method_missing
        PASS [   0.001s]       major        inherent_method_unsafe_added
        PASS [   0.001s]       major        method_parameter_count_changed
        PASS [   0.000s]       major        sized_impl_removed
        PASS [   0.000s]       major        struct_marked_non_exhaustive
        PASS [   0.000s]       major        struct_missing
        PASS [   0.000s]       major        struct_pub_field_missing
        PASS [   0.000s]       major        struct_repr_c_removed
        PASS [   0.001s]       major        struct_repr_transparent_removed
        PASS [   0.000s]       major        struct_with_pub_fields_changed_type
        PASS [   0.000s]       major        trait_missing
        PASS [   0.000s]       major        trait_unsafe_added
        PASS [   0.000s]       major        trait_unsafe_removed
        PASS [   0.000s]       major        tuple_struct_to_plain_struct
        PASS [   0.000s]       major        unit_struct_changed_kind
        PASS [   0.000s]       major        variant_marked_non_exhaustive
   Completed [   0.015s] 37 checks; 37 passed, 6 unnecessary
     Parsing pacdef_macros v0.1.1 (current)
 Documenting pacdef_macros v0.1.1 (/home/ratajc72/rust/pacdef/crates/pacdef_macros)
    Finished dev [unoptimized + debuginfo] target(s) in 0.28s
Error: Version pacdef_macros of crate 1.1.0 not found in registry```

Besides #454, maybe we could also make the --help messages more clear? Currently they are written with an assumption that the --baseline-* flags affect a baseline, not necessarily all baselines in a workspace. I'm also wondering, are there any scenarios where the --baseline-* flags are useful in the context of a workspace? Maybe --baseline-version, but I feel it confuses more than it helps...

Some projects are designed to be multi-crate but versioned in lockstep (so all crates have the same version), and in that case --baseline-version makes sense in a workspace.
We could mark --baseline-rustdoc as mutually exclusive with --workspace, I don't see it being useful. --baseline-rev and --baseline-root could work well in a workspace if the CLI was smart about picking the matching crate name in the workspace as the baseline, but I'm not sure if it does that right now.
And I'm always in favor of improving confusing help and error messages.
Please open PRs :)


Emits a counter value for every unique view of the hashring

What changed?

Why?

How did you test it?

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018dbdd3-4616-44e6-811b-e83083c08a1e
Details

-17 of 49 (65.31%)  changed or added relevant lines in 4 files are covered.
52 unchanged lines in 8 files lost coverage.
Overall coverage decreased (-0.007%) to 62.737%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/server/cadence/server.go
0
2
0.0%

common/metrics/tags.go
0
6
0.0%

common/membership/hashring.go
30
39
76.92%

Files with Coverage Reduction
New Missed Lines
%

service/history/queue/timer_queue_processor_base.go
1
78.23%

common/task/weighted_round_robin_task_scheduler.go
2
88.06%

common/util.go
2
91.69%

service/history/task/transfer_standby_task_executor.go
2
87.42%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
3
59.55%

common/persistence/sql/workflowStateMaps.go
8
86.21%

service/history/execution/mutable_state_task_refresher.go
14
59.81%

common/persistence/nosql/nosqlplugin/cassandra/workflow_parsing_utils.go
20
82.02%

Totals

Change from base Build 018db582-cf6a-4726-8ce9-adba3d0a8053:
-0.007%

Covered Lines:
92641

Relevant Lines:
147666

💛  - Coveralls

since we don't have integration test to validate emitted metrics, did you test locally and checked the emitted metrics?

I deployed and tested it, yes


Juniper Mist Dockerization

As a DevOps engineer, I want to be able to run this script with 100% confidence. By building it in docker, we can run this within the team with a high degree of confidence it will work.
DOD:
Docker build local (package the script)
Docker run (Run the script)
Docker run unit tests (Run the unit tests)
Docker IDE integration

PR for this work
https://github.com/ministryofjustice/juniper-mist-integration/pull/6

related to parent ticket
https://github.com/ministryofjustice/juniper-mist-integration-spike/issues/4

https://github.com/ministryofjustice/juniper-mist-integration/pull/6/files


Old build is run in watch mode

Operating System: MacOS
Node Version: v10.14.1
NPM Version: 6.4.1
webpack Version: 4.27.1
karma-webpack Version: 4.0.0-rc.5

Scenario

Run karma in watch mode: npm run test
Wait for the bundle to be built and tests to run. The tests should succeed.
Now modify the spec file such that the tests would fail: sed -i 's/toBe([0-9])/toBe(9)/p' src/one.spec.js.

Expected Behavior
After step 3, the new bundle should be run and fail:
HeadlessChrome 71.0.3578 (Mac OS X 10.13.6) one should equal 1 FAILED
	Error: Expected 1 to be 9.
	    at <Jasmine>
	    at UserContext.it (webpack:///./src/one.spec.js?:7:58)
	    at <Jasmine>
HeadlessChrome 71.0.3578 (Mac OS X 10.13.6): Executed 1 of 1 (1 FAILED) ERROR (0.003 secs / 0.003 secs)

If re-run npm run test command, I see the expected result: the tests fail.
Actual Behavior
Although I can see that webpack recompiled the bundle and the reported hash changed, the build succeeds as if it would run the original (unmodified) tests.
Code
// karma.conf.js
module.exports = config => {
  config.set({
    frameworks: ['jasmine'],

    files: [ 'index.js' ],

    preprocessors: {
      '*.js': [ 'webpack' ],
    },

    webpack: {
      entry: './index.js',
      mode: 'development',
    },

    webpackMiddleware: {
      // stats: 'minimal',
    },

    reporters: ['progress'],
    port: 9876,
    colors: true,
    logLevel: config.LOG_INFO,
    autoWatch: true,
    browsers: ['ChromeHeadless'],
    singleRun: false,
    concurrency: Infinity,
  });
};

// index.js
const testCtx = require.context('./src', true, /\.spec\.js$/);

testCtx.keys().forEach(testCtx);

// src/one.js
export default 1;

// src/one.spec.js
import one from './one';

describe('one', () => {
  it('should equal 1', () => {
    expect(one).toBe(9);
  });
});

How Do We Reproduce?

Checkout the repo: https://github.com/korya/karma-webpack-watch-mode-issue
Run the scenario steps:

Run karma in watch mode: npm run test
Wait for the bundle to be built and tests to run. The tests should succeed.
Now modify the spec file such that the tests would fail: sed -i 's/toBe([0-9])/toBe(9)/' src/one.spec.js.

Full Log
$ npm run test

><EMAIL_ADDRESS>test /Users/korya/dev/webpack-context-require
> karma start ./karma.conf.js

13 12 2018 14:08:29.056:WARN [karma]: No captured browser, open http://localhost:9877/
ℹ ｢wdm｣: Hash: da049fc7bf26ee608e7b
Version: webpack 4.27.1
Time: 15ms
Built at: 2018-12-13 2:08:29 p.m.
   Asset      Size  Chunks             Chunk Names
index.js  5.81 KiB   index  [emitted]  index
 main.js  5.81 KiB    main  [emitted]  main
Entrypoint main = main.js
Entrypoint index = index.js
[./index.js] 97 bytes {main} {index} [built]
[./src sync recursive \.spec\.js$] ./src sync \.spec\.js$ 178 bytes {main} {index} [built]
[./src/one.js] 18 bytes {main} {index} [built]
[./src/one.spec.js] 116 bytes {main} {index} [optional] [built]
ℹ ｢wdm｣: Compiled successfully.
13 12 2018 14:08:29.072:INFO [karma-server]: Karma v3.1.3 server started at http://<IP_ADDRESS>:9877/
13 12 2018 14:08:29.072:INFO [launcher]: Launching browsers ChromeHeadless with concurrency unlimited
13 12 2018 14:08:29.076:INFO [launcher]: Starting browser ChromeHeadless
13 12 2018 14:08:29.448:INFO [HeadlessChrome 71.0.3578 (Mac OS X 10.13.6)]: Connected on socket PCQ1DpJMsd9hi8fGAAAA with id 22158802
HeadlessChrome 71.0.3578 (Mac OS X 10.13.6): Executed 1 of 1 SUCCESS (0.001 secs / 0.001 secs)
TOTAL: 1 SUCCESS

##### Run 'sed -i 's/toBe([0-9])/toBe(9)/' src/one.spec.js

ℹ ｢wdm｣: Compiling...
ℹ ｢wdm｣: Hash: 740e0db875c82d372f14
Version: webpack 4.27.1
Time: 13ms
Built at: 2018-12-13 2:09:13 p.m.
   Asset      Size  Chunks             Chunk Names
index.js  5.88 KiB   index  [emitted]  index
 main.js  5.88 KiB    main  [emitted]  main
Entrypoint main = main.js
Entrypoint index = index.js
[./index.js] 97 bytes {main} {index}
[./src sync recursive \.spec\.js$] ./src sync \.spec\.js$ 178 bytes {main} {index} [built]
[./src/one.js] 18 bytes {main} {index}
[./src/one.spec.js] 141 bytes {main} {index} [optional] [built]
ℹ ｢wdm｣: Compiled successfully.
HeadlessChrome 71.0.3578 (Mac OS X 10.13.6): Executed 1 of 1 SUCCESS (0.001 secs / 0 secs)
TOTAL: 1 SUCCESS

^C
$ npm run test

><EMAIL_ADDRESS>test /Users/korya/dev/webpack-context-require
> karma start ./karma.conf.js

13 12 2018 14:09:26.554:WARN [karma]: No captured browser, open http://localhost:9877/
ℹ ｢wdm｣: Hash: 740e0db875c82d372f14
Version: webpack 4.27.1
Time: 14ms
Built at: 2018-12-13 2:09:26 p.m.
   Asset      Size  Chunks             Chunk Names
index.js  5.88 KiB   index  [emitted]  index
 main.js  5.88 KiB    main  [emitted]  main
Entrypoint main = main.js
Entrypoint index = index.js
[./index.js] 97 bytes {main} {index} [built]
[./src sync recursive \.spec\.js$] ./src sync \.spec\.js$ 178 bytes {main} {index} [built]
[./src/one.js] 18 bytes {main} {index} [built]
[./src/one.spec.js] 141 bytes {main} {index} [optional] [built]
ℹ ｢wdm｣: Compiled successfully.
13 12 2018 14:09:26.570:INFO [karma-server]: Karma v3.1.3 server started at http://<IP_ADDRESS>:9877/
13 12 2018 14:09:26.570:INFO [launcher]: Launching browsers ChromeHeadless with concurrency unlimited
13 12 2018 14:09:26.579:INFO [launcher]: Starting browser ChromeHeadless
13 12 2018 14:09:26.948:INFO [HeadlessChrome 71.0.3578 (Mac OS X 10.13.6)]: Connected on socket -OKokGONWWP4Z2SPAAAA with id 24758883
HeadlessChrome 71.0.3578 (Mac OS X 10.13.6) one should equal 1 FAILED
	Error: Expected 1 to be 9.
	    at <Jasmine>
	    at UserContext.it (webpack:///./src/one.spec.js?:7:58)
	    at <Jasmine>
	Error: Expected 1 to be 9.
	    at <Jasmine>
	    at UserContext.it (webpack:///./src/one.spec.js?:8:58)
	    at <Jasmine>
HeadlessChrome 71.0.3578 (Mac OS X 10.13.6): Executed 1 of 1 (1 FAILED) ERROR (0.002 secs / 0.002 secs)
^C

Are you using karma v3.1.3? If so this is not a karma-webpack bug. See https://github.com/karma-runner/karma/issues/3226

OK. Thanks. Indeed v3.1.1 works just fine. I am closing the issue.


Add regexp_count function

Which issue does this PR close?
Closes #12079 and part of #11946. Followup to PR #12080 by #xinlifoobar with some additional work (documentation, minor fixes, scalar test fixes).
Rationale for this change
Add an additional useful regexp function to datafusion
What changes are included in this PR?
Code, tests, documentation.
Are these changes tested?
Yes.
Are there any user-facing changes?
Docs updated to include the new udf.

Note this PR does not resolve the performance degradation seen in this function as compared to regexp_match or regexp_like. (see https://github.com/apache/datafusion/pull/12080#issuecomment-2316755718 for a benchmark) I believe that should be looked at in a followup ticket.

FYI @xinlifoobar

Note this PR does not resolve the performance degradation seen in this function as compared to regexp_match or regexp_like. (see #12080 (comment) for a benchmark) I believe that should be looked at in a followup ticket.

Filed https://github.com/apache/datafusion/issues/13011


Windows testing exiting with code 1 and no reason

Multiple windows systems are failing with an exit status 1 and no logging of any sort to indicate the failure:
https://buildkite.com/chef/chef-chef-master-omnibus-release/builds/1186#22c54fae-ec3b-46f0-86d6-9585f5930a76/109-721

those were suspected to be due to the parallelizer on ruby 3.0

Related to https://github.com/chef/chef/issues/10911


Do we support chrome debugger?

Failed to create a new MMKV instance, the native initializer function does not exist. Is the native MMKV library correctly installed? Make sure to disable any remote debugger (e.g. Chrome) to use JSI!

Seems your package use JSI like RN reanimated 2, and they already fixed that issue by this
Can you fix it to support a chrome debugger? Or any plan for it?

Hey!
No, that's not supported. See the "Limitations" section in the README:

As the library uses JSI for synchronous native methods access, remote debugging (e.g. with Chrome) is no longer possible. Instead, you should use Flipper.

The way Reanimated works, is by using a pure JS implementation. This does not work for MMKV, there is no pure JS implementation of a synchronous key/value storage. That's part of the reason why MMKV is so nice 😄
You can mock it using a simple in memory Map<K, V>, but that obviously doesn't persist to storage.

i see this, https://github.com/ammarahm-ed/react-native-mmkv-storage/issues/221, which could be something to support too. basically what you're saying, but would be nice to have it in the lib.

This should already work with a minor change to the import script (we need to skip the native install() call), but then it will use the Web implementation (localStorage).
Either way, the Chrome Debugger is not recommended anyways, and will fail in the future because more and more modules will use JSI. On RN with Fabric enabled it won't work at all.
So I recommend:

either debug with Safari debugger (that runs on device!)
or use the Flipper debugger (recommended by facebook)

oh snap. safari debugger? i didnt know that.. ill try. flipper is cool, but there is no breakpoint debugging with it.

VSCode also has a RN Debugger, that has breakpoints.

VSCode also has a RN Debugger, that has breakpoints.

Hi @mrousavy, I've tried the react native tools in VSCode, but it also didn't work if i integrated react-native-mmkv in my project.
when I toggle on the debug mode in the dev menu, the console output this error log:
error: Failed to create a new MMKV instance: React Native is not running on-device. MMKV can only be used when synchronous method invocations (JSI) are possible. If you are using a remote debugger (e.g. Chrome), switch to an on-device debugger (e.g. Flipper) instead.
So the flipper is the only way to debug my app, is that right?

Hello! What about the case if i need to set breakpoints and flipper is already deprecated?

Therr are alternatives to flipper. RN IDE for example

I started using VSCode React Native Tools  extension. Quite simple as for me


Auto optimizations for Bundles

Hello all. I created issue for JSPM a month ago where i talk about this problem. And one of guys linked me to this project.
I have a suggestion about this problem, maybe you find it useful for yourself.
It may be better to transfer all rights about configuring bundles to System.js Builder? Now we have some Bundle arithmetic approaches what gives us ability to add or remove modules from own bundles. But perhaps more correct to provide the entire process of assembling bundles to Builder?
Only one thing what needs from users - its a specify a list of modules that you need to create bundles. Mabye, create a some array in System.js configuration for this? :)
And create code in Builder what automatically resolves all conflicts in bundles and removes collisions from its, and etc, etc. Like in webpack, as i sayed in my previous issue about this problem.
If you do everything so that - you will no longer need in bundle arithmetics, i hope.

Making this easier is the general direction things are headed, but it's difficult to prioritize as a single issue. It is possible to build a wrapper around SystemJS Builder that can perform automatic bundle chunking strategies. Projects that do this can certainly make it easier for users to get advanced bundling workflows.

I would be great to see enhancements here, but I love bundle arithmetic.


Does not seem to wait for findAll call in setupController

Ember 2.2
Ember Data 2.1
I'm doing something like this to load product data in setupController so it does not block rendering the template.
  setupController(controller) {
    this.store.findAll('product').then((data) => {
      controller.set('products', data);
    });

    this._super(...arguments);
  },

However, after installing this add-on (and restarting ember-cli), it does not seem to be waiting for products to load.
  page.visitFiltered();

  andThen(() => {
    // Assertion fails
    assert.equal(
      page.productFilterTag().text(),
      'Product: Product 1 (All Variants)'
    );
  });

I've also tried wrapping the assertion inside a run.next inside the andThen to be sure that it's running after a render loop. I have tested the behavior manually and it appears to be working as expected. The text is Product: ... when the product is not loaded, and then Product: Product 1 (All Variants) when products finish loading.
Any idea what I'm doing wrong? Is the waiter resolving after model and before setupController?

I'd do that in the model hook, since that waits for promises.


fix: output optional viewable

:tada: This PR is included in version 1.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[FINK-7417] Create flink-shaded-jackson

Create flink-shaded-jackson in flink-shaded for com.fasterxml.jackson

I found there's PR https://github.com/apache/flink-shaded/pull/23 for flink-shaded-jackson, I'll close this one, thanks @zentol


Custom wallet API

This PR adds a concept of a "managed account", which is an account whose private keys are known by Flowser.
Managed accounts can be created and used to automatically authorize/send transactions through our new wallet API.
Changes

Implement a simple wallet API that allows us to:

execute transactions without manual authorization by the user (with fcl-dev-wallet we used previously)
create new managed accounts that can be used to authorize transactions automatically

automatically import managed accounts from project's flow.json config
other improvements & fixes

Wallet API
Create account
This creates a new "managed account" and returns its info.
http POST localhost:6061/api/wallets/accounts

Send a transaction
This will send a transaction given the authorizer/payer/proposer account addresses and Cadence source code.
All the provided account addresses must be "managed accounts".
http POST localhost:6061/api/wallets/accounts/transaction \
  proposerAddress=0x01cf0e2f2f715450 \
  payerAddress=0x01cf0e2f2f715450 \
  authorizerAddresses:='["0x01cf0e2f2f715450"]' \
  cadence='transaction { prepare(signer: AuthAccount) { log(signer.address) } }'

Implemented in the scope of https://github.com/onflow/developer-grants/issues/150


SVG images ending up under fonts

Using a bower plugin.
SVG image could not be found because it appears in globs.fonts instead of globs.images.
Anyway to make sure only SVG fonts go to fonts and SVG images go to images?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/13492928-svg-images-ending-up-under-fonts?utm_campaign=plugin&utm_content=tracker%2F8853550&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F8853550&utm_medium=issues&utm_source=github).

For now I'm using this work around, although it's not ideal. And the .SVG still ends up in my fonts folder as well.
[...]
    "images": {
      "files": [
        "../bower_components/photoswipe/dist/default-skin/default-skin.svg",
        "images/**/*"
      ]
    }

[...]

There also seems to be an issue with .gif types. i used this workaround but it was also and issue with the package set up itself.
#27

Been thinking about this. Pretty sure I'm going to have it read the SVG real quick and determine if it's a font from the content of the SVG. I'll probably make a separate npm module to do this.

@austinpray just recently used something like that to check for SVG fonts vs SVG images:
var _      = require('lodash');
var filter = require('gulp-filter');
var gulp   = require('gulp');

// Check for "<font id" string in given file
function isSVGFont(file) {
  return file.contents.toString().indexOf('<font id') > -1;
}

// Fonts
return gulp.src(fonts)
.pipe(filter(function(file){
  if(_.endsWith(file.path, '.svg')) {
    return isSVGFont(file);
  } else {
    return true;
  }
}))
.pipe( // Continue pipe...

// Fonts
return gulp.src(images)
.pipe(filter(function(file){
  if(_.endsWith(file.path, '.svg')) {
    return !isSVGFont(file); // <-- Invert boolean here
  } else {
    return true;
  }
}))
.pipe( // Continue pipe...

Despite that I'm not using asset-builder in this case (using NPM over Bower) I figured it might still be of interest to you.

The lazyweb delivers! Thank you @JvanderHeide.

Just ran into the same problem, I notice that types.json is also incomplete, no .svg (or .tiff, etc) in the images key, and the fonts seems a little broad. MIME type detection might have been more correct, but I'm not sure whether there are different mime types for SVG fonts/images (as they are one and the same).


render deletes comments from Kptfile

Expected behavior
When I run kpt fn render on a package, comments in the Kptfile should not be dropped.
Actual behavior
render drops comments from Kptfile
Refer to https://github.com/GoogleContainerTools/kpt/pull/2295#discussion_r655395904 for an example.

This is no longer true as we don't format Kptfile anymore. This is fixed.


DIAGNOSTIC re CI failures: Release/v0.12.1 state

This is a diagnostic PR to investigate https://github.com/alan-turing-institute/sktime/issues/3103
Purpose: see whether the tests complete at v0.12.1 state.
If the theory is correct that recent migrations in the GitHub cloud are the culprit, this should fail. Otherwise, it would pass.

Sorry,  didn't want to convert this to ready. Can someone every back to draft?

done

failure on mac, similar to the one reported in #3103. no similar failures were reported before 0.13.0 release.

and failing again. Could it be different by time of day??


fh-joanneum-iit-thesis:2.0.5

I am submitting

[ ] a new package
[x] an update for a package

Changed: numbering style for headings
Fix: use of *.csl for citations

Thank you.

Mini-question: Is there anything I could/should do to solve problems with deploy job (fh-joanneum-iit-thesis:2.0.5 (#1325) #1152 https://github.com/typst/packages/actions/runs/12026718528 ): Canceling since a higher priority waiting request for 'deploy' exists


Selection range

Selection range

This issue was imported from Google Moderator
Moderator votes: +10
Issue added by Bjarke on 2011-12-20
To vote this issue up or down, simply include +1 or -1 in your comment.

Related to #1070?

See my PR #1696

Duplicate of #1070  (#1696 covers this mostly, but need to investigate the selection part specifically)


[Bug]: Embedded object in root model

What happened?
It is not possible to use an Embedded object in a model.
Repro steps

Create model with embedded objects.
Create configuration with schema of root model.
Run code.

Version
Flutter 3.3.8, Realm 0.8.0+rc
What Realm SDK flavor are you using?
MongoDB Atlas (i.e. Sync, auth, functions)
What type of application is this?
Flutter Application
Client OS and version
Android 11
Code snippets

Configuration:
final flxConfig = Configuration.flexibleSync(user,[Topic.schema]));
Stacktrace of the exception/crash you're getting
Exception has occurred.
RealmException (RealmException: Error opening realm at path /data/user/0/com.app.test/app_flutter/mongodb/db_topics.realm. Error code: 18 . Message: Schema validation failed due to the following errors:
- Property 'Topic.logo' of type 'object' has unknown object type 'TopicLogo'
- Property 'Topic.attachment' of type 'array' has unknown object type 'Attachment')

Relevant log output
No response

Did you remember to add TopicLogo.schema and Attachment.schema when creating your configuration?

Did you remember to add TopicLogo.schema and Attachment.schema when creating your configuration?

When I to add TopicLogo.schema and Attachment.schema in configuration.
I am getting an error on the Mongo DB Atlas side. You can see below.
`missing properties in object schema (ProtocolErrorCode=225)
Logs:
[
"Received client-originated schema change instruction to apply in Development Mode",
"Adding a new primitive field to table in application schema",
"Existing Table Name: TopicLogo",
"New Field Name: id",
"New Field Type: string",
"New Field Collection Type: None/Single",
"New Field Is Required: true"
]`
My topic schema looks like this:
{   "title": "topic",   "required": [     "_id",     "name",     "timestampCreated",     "timestampLastUpdated",     "ownerIds",     "userIdCreated"   ],   "properties": {     "_id": {       "bsonType": "objectId"     },     "activityTypes": {       "bsonType": "array",       "items": {         "bsonType": "objectId"       }     },     "attachment": {       "bsonType": "array",       "items": {         "bsonType": "object",         "properties": {           "authorId": {             "bsonType": "string"           },           "fileExtension": {             "bsonType": "string"           },           "id": {             "bsonType": "string"           },           "link": {             "bsonType": "string"           },           "name": {             "bsonType": "string"           }         }       }     },     "description": {       "bsonType": "string"     },     "logo": {       "bsonType": "object",       "properties": {         "id": {           "bsonType": "string"         },         "link": {           "bsonType": "string"         }       }     },     "name": {       "bsonType": "string"     },     "ownerIds": {       "bsonType": "array",       "items": {         "bsonType": "string"       }     },     "priorities": {       "bsonType": "array",       "items": {         "bsonType": "objectId"       }     },     "statuses": {       "bsonType": "array",       "items": {         "bsonType": "objectId"       }     },     "timestampCreated": {       "bsonType": "timestamp"     },     "timestampLastUpdated": {       "bsonType": "timestamp"     }   } }
Topic schema has fields:

logo (Object)
attachment (Array Object)

What am I doing wrong?
Do I need to create separate collections for TopicLogo and Attachment?

Sorry, I accidentally closed it. It is not solved.

@RedFox64 Sorry, this fell between two chairs.
The issue is that your server side schema doesn't match your client side models. Fx. Attachment.id is a non-nullable String hence the server side schema would need to make it required. Same goes for all the other properties on Attachment


Mock.patch not working

when i run the pytest in the neovim, the mock patch can't find the module src.server, but when i run outside the nvim it works.

I have absolutely no idea what your project looks like or how to reproduce this. Please provide a repo so that I can reproduce

I think its a wrong configuration of pyenv or venv :thinking: I recreated my environment and now it works


RuntimeError: The ray global state API cannot be used before ray.init has been called.

Hi Team,
I have python flask application, here i am using modin.pandas and ray packages.
ray==0.8.4
modin==0.7.3

Below is my code
import modin.pandas as pd
import ray
os.environ["MODIN_ENGINE"] = "ray"
ray.init(plasma_directory="/", object_store_memory=10**10,ignore_reinit_error=True)

But i am getting runtime error
spawned uWSGI worker 4 (pid: 8, cores: 1)
/usr/local/lib/python3.6/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.8) or chardet (3.0.4) doesn't match a supported version!
  RequestsDependencyWarning)
/usr/local/lib/python3.6/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.8) or chardet (3.0.4) doesn't match a supported version!
  RequestsDependencyWarning)
/usr/local/lib/python3.6/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.8) or chardet (3.0.4) doesn't match a supported version!
  RequestsDependencyWarning)
/usr/local/lib/python3.6/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.8) or chardet (3.0.4) doesn't match a supported version!
  RequestsDependencyWarning)
Traceback (most recent call last):
  File "/usr/src/audiencemangement/WSGI.py", line 1, in <module>
    from filter_service import app
  File "/usr/src/audiencemangement/filter_service.py", line 11, in <module>
    import getMasterData
  File "/usr/src/audiencemangement/getMasterData.py", line 2, in <module>
    import modin.pandas as pd
  File "/usr/local/lib/python3.6/site-packages/modin/pandas/__init__.py", line 242, in <module>
    num_cpus = ray.cluster_resources()["CPU"]
  File "/usr/local/lib/python3.6/site-packages/ray/state.py", line 1209, in cluster_resources
    return state.cluster_resources()
  File "/usr/local/lib/python3.6/site-packages/ray/state.py", line 884, in cluster_resources
    self._check_connected()
  File "/usr/local/lib/python3.6/site-packages/ray/state.py", line 146, in _check_connected
    raise RuntimeError("The ray global state API cannot be used "
RuntimeError: The ray global state API cannot be used before ray.init has been called.
unable to load app 0 (mountpoint='') (callable not found or import error)
Traceback (most recent call last):
  File "/usr/src/audiencemangement/WSGI.py", line 1, in <module>
    from filter_service import app
  File "/usr/src/audiencemangement/filter_service.py", line 11, in <module>
    import getMasterData
  File "/usr/src/audiencemangement/getMasterData.py", line 2, in <module>
    import modin.pandas as pd
  File "/usr/local/lib/python3.6/site-packages/modin/pandas/__init__.py", line 242, in <module>
    num_cpus = ray.cluster_resources()["CPU"]
  File "/usr/local/lib/python3.6/site-packages/ray/state.py", line 1209, in cluster_resources
    return state.cluster_resources()
  File "/usr/local/lib/python3.6/site-packages/ray/state.py", line 884, in cluster_resources
    self._check_connected()
  File "/usr/local/lib/python3.6/site-packages/ray/state.py", line 146, in _check_connected
    raise RuntimeError("The ray global state API cannot be used "

Can anyone help me how to fix this?

The only change that is needed in this code is to import modin.pandas after ray.init call.

Thanks @gshimansky ,
Now i am not getting that error. but response i am not getting. I am getting below warning.
UserWarning: User-defined function verification is still under development in Modin. The function provided is not verified.
2020-06-04 08:56:12,086 WARNING worker.py:1072 -- The actor or task with ID 45b95b1c8bd3a9c4ffffffff0100 is pending and cannot currently be scheduled. It requires {CPU: 1.000000} for execution and {CPU: 1.000000} for placement, but this node only has remaining {node:<IP_ADDRESS>: 1.000000}, {CPU: 4.000000}, {memory: 4.589844 GiB}, {object_store_memory: 6.396484 GiB}. In total there are 1 pending tasks and 0 pending actors on this node. This is likely due to all cluster resources being claimed by actors. To resolve the issue, consider creating fewer actors or increase the resources available to this Ray cluster. You can ignore this message if this Ray cluster is expected to auto-scale.

Looking at parameters that you pass to Ray, are you sure that / directory is writable?
You can try to figure out Ray failures in /tmp/ray/session_latest/logs.

Yes, @gshimansky is right about checking permissions "/" as the plasma directory.
I also notice that Ray is saying that all resources are occupied by Actors. Is there Ray related code occupying all of the resources?
Ray cannot schedule new tasks on existing occupied resources. Ray does not allow sharing of existing Actors.

@gshimansky thank you for your reply.
Just want to know this plasma_directory director is using for writing the file ? And it should have permission to write in to this ?
If I remove this plasma_directory parameter from init function then what will be impact ?
Actually I am new to this module. So I am asking all these things here

In my experience you will not see any files created in plasma_directory but you will see disk space occupied in on that filesystem while you have running Ray processes. So you need write permission and you need enough disk space. Files are memory mapped and are invisible.

Please, reopen the issue if you still have problems.


Replacing ByteStringer with ByteString.Output where appropriate

This allows ByteStringer to be moved to bigtable-hbase.

This change looks good. I'd like to know why ByteStringer still needs to exist so we can see if we can obviate the usage in those contexts as well.

I'm not sure what the API stability guarantee of these libraries are, but this is a breaking change to the API surface (ByteStringer was/is public).  We use this in a bunch of places in our own code as well because its generally useful.  There are alternatives now in protobuf as well iirc, so its not the end of the world to have to refactor, but I just wanted to point it out.  Maybe you can include it as a breaking change in the release notes?

@steveniemitz, I guess we'll need to revert the change.
@danielweis: ByteStringer was required for performance reasons.  Extracting byte[]s from ByteStrings and creating ByteStrings from byte[] are expensive CPU operations at the throughput that Cloud Bigtable supports.  Some users reported a 10X increase in overall throughput once we added ByteStringer to our read path that extracts byte[].

fwiw I don't really mind having to refactor my stuff, we actually use a vendored version of this anyways from most places in our code.  I just wanted to point out that it is a public API and a breaking change by moving it.

@sduskis That makes sense. What I'm aiming for is whether alternative APIs like ByteString.Output will suffice for your other use cases. We introduced UnsafeByteOperations for the use cases where there are no alternatives so it's okay to use, with the caveat that if used incorrectly, your application will break in "spooky-action-at-a-distance" ways. Consequently I much prefer folks using alternative APIs wherever possible.


Add Pytests

Should probably exhibit good practices lol oops

I think I should include a github pipeline setup so that these tests must pass to merge. COVER YOUR ASS

`import unittest
from unittest.mock import AsyncMock, MagicMock
from discord.ext import commands
class MyBotTests(unittest.TestCase):
def setUp(self):
self.bot = commands.Bot(command_prefix='!')
def test_greet_command(self):
    ctx = AsyncMock()
    self.bot.get_command = MagicMock(return_value=self.bot.command(name='greet'))

    @self.bot.command()
    async def greet(ctx):
        await ctx.send('Hello!')

    self.bot.add_command(greet)

    with self.assertRaises(commands.CommandInvokeError):
        # Simulate calling the command
        await self.bot.invoke(ctx)

    # Verify the bot's response
    ctx.send.assert_called_with('Hello!')

if name == 'main':
unittest.main()
`

should cover testing each command ideally


CAMEL-11136: Create camel Pubnub component

Here is the PubNub component for reveiw.
The component is upgraded to the latest PubNub release, and refactored a bit.
There are still some 'missing' features that could be added later if needed.
From the top of my head

Subscribe to multi channels using lists
Subscribe filtering
Limiting results using timestamps
Extend doc to include operations

Besides that there is the usual osgi wrapping stuff.

Looks good to me. We still miss the Karaf feature, but we can add it later.
@davsclaus what do you think?

Thanks for the review.
The review comments should be fixed now.

Thanks for the PR it has been merged. Do you mind closing this?