[Question]: Can not parsing files using local Ollama embedding models

Describe your problem
I installed Ollama locally and set up Ragflow using Docker. I downloaded the Qwen2 7b model and two different embedding models through Ollama. Then I created a knowledge base, config embedding model to be the one in Ollama, and uploaded files, but they couldn't be parsed. What could be the issue, and how can I resolve it?

Does this error matters?

I guess some process of ragflow did not execute well.
Could you paste the log by removing -d for docker compose?

I have the same issue

My environment: apple macbook, arm, docker in vm

The following is log:

~/Documents/git_repos/ragflow/docker$ docker compose up
WARN[0000] The "MACOS" variable is not set. Defaulting to a blank string.
[+] Running 6/6
✔ Network docker_ragflow    Created                                                                                0.0s
✔ Container ragflow-mysql   Created                                                                                0.1s
✔ Container ragflow-redis   Created                                                                                0.1s
✔ Container ragflow-minio   Created                                                                                0.1s
✔ Container ragflow-es-01   Created                                                                                0.1s
✔ Container ragflow-server  Created                                                                                0.1s
Attaching to ragflow-es-01, ragflow-minio, ragflow-mysql, ragflow-redis, ragflow-server
ragflow-redis   | 1:C 23 Aug 2024 10:19:10.959 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
ragflow-redis   | 1:C 23 Aug 2024 10:19:10.959 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started
ragflow-redis   | 1:C 23 Aug 2024 10:19:10.959 * Configuration loaded
ragflow-redis   | 1:M 23 Aug 2024 10:19:10.960 * monotonic clock: POSIX clock_gettime
ragflow-redis   | 1:M 23 Aug 2024 10:19:10.960 * Running mode=standalone, port=6379.
ragflow-redis   | 1:M 23 Aug 2024 10:19:10.960 * Server initialized
ragflow-redis   | 1:M 23 Aug 2024 10:19:10.960 * Loading RDB produced by version 7.2.4
ragflow-redis   | 1:M 23 Aug 2024 10:19:10.960 * RDB age 21 seconds
ragflow-redis   | 1:M 23 Aug 2024 10:19:10.960 * RDB memory usage when created 0.97 Mb
ragflow-redis   | 1:M 23 Aug 2024 10:19:10.960 * Done loading RDB, keys loaded: 0, keys expired: 0.
ragflow-redis   | 1:M 23 Aug 2024 10:19:10.961 * DB loaded from disk: 0.000 seconds
ragflow-redis   | 1:M 23 Aug 2024 10:19:10.961 * Ready to accept connections tcp
ragflow-minio   | MinIO Object Storage Server
ragflow-minio   | Copyright: 2015-2023 MinIO, Inc.
ragflow-minio   | License: GNU AGPLv3 https://www.gnu.org/licenses/agpl-3.0.html
ragflow-minio   | Version: RELEASE.2023-12-20T01-00-02Z (go1.21.5 linux/amd64)
ragflow-minio   |
ragflow-minio   | Status:         1 Online, 0 Offline.
ragflow-minio   | S3-API: http://<IP_ADDRESS>:9000 http://<IP_ADDRESS>:9000
ragflow-minio   | Console: http://<IP_ADDRESS>:9001 http://<IP_ADDRESS>:9001
ragflow-minio   |
ragflow-minio   | Documentation: https://min.io/docs/minio/linux/index.html
ragflow-minio   | Warning: The standard parity is set to 0. This can lead to data loss.
ragflow-mysql   | 2024-08-23T10:19:11.142918Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
ragflow-mysql   | 2024-08-23T10:19:11.143580Z 0 [Note] mysqld (mysqld 5.7.18) starting as process 1 ...
ragflow-mysql   | 2024-08-23T10:19:11.146013Z 0 [Note] InnoDB: PUNCH HOLE support available
ragflow-mysql   | 2024-08-23T10:19:11.146071Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
ragflow-mysql   | 2024-08-23T10:19:11.146084Z 0 [Note] InnoDB: Uses event mutexes
ragflow-mysql   | 2024-08-23T10:19:11.146093Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
ragflow-mysql   | 2024-08-23T10:19:11.146118Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
ragflow-mysql   | 2024-08-23T10:19:11.146125Z 0 [Note] InnoDB: Using Linux native AIO
ragflow-mysql   | 2024-08-23T10:19:11.146723Z 0 [Note] InnoDB: Number of pools: 1
ragflow-mysql   | 2024-08-23T10:19:11.146827Z 0 [Note] InnoDB: Using CPU crc32 instructions
ragflow-mysql   | 2024-08-23T10:19:11.148866Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
ragflow-mysql   | 2024-08-23T10:19:11.154151Z 0 [Note] InnoDB: Completed initialization of buffer pool
ragflow-mysql   | 2024-08-23T10:19:11.155544Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
ragflow-mysql   | 2024-08-23T10:19:11.172572Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
ragflow-mysql   | 2024-08-23T10:19:11.192782Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
ragflow-mysql   | 2024-08-23T10:19:11.192852Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
ragflow-mysql   | 2024-08-23T10:19:11.210930Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
ragflow-mysql   | 2024-08-23T10:19:11.211498Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
ragflow-mysql   | 2024-08-23T10:19:11.211511Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
ragflow-mysql   | 2024-08-23T10:19:11.211797Z 0 [Note] InnoDB: Waiting for purge to start
ragflow-mysql   | 2024-08-23T10:19:11.262166Z 0 [Note] InnoDB: 5.7.18 started; log sequence number 246681350
ragflow-mysql   | 2024-08-23T10:19:11.262482Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
ragflow-mysql   | 2024-08-23T10:19:11.262719Z 0 [Note] Plugin 'FEDERATED' is disabled.
ragflow-mysql   | 2024-08-23T10:19:11.268025Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
ragflow-mysql   | 2024-08-23T10:19:11.268097Z 0 [Warning] Failed to set up SSL because of the following SSL library error: TLS version is invalid
ragflow-mysql   | 2024-08-23T10:19:11.268397Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
ragflow-mysql   | 2024-08-23T10:19:11.268464Z 0 [Note] IPv6 is available.
ragflow-mysql   | 2024-08-23T10:19:11.268469Z 0 [Note]   - '::' resolves to '::';
ragflow-mysql   | 2024-08-23T10:19:11.268484Z 0 [Note] Server socket created on IP: '::'.
ragflow-mysql   | 2024-08-23T10:19:11.270852Z 0 [Note] InnoDB: Buffer pool(s) load completed at 240823 18:19:11
ragflow-mysql   | 2024-08-23T10:19:11.273835Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
ragflow-mysql   | 2024-08-23T10:19:11.273864Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
ragflow-mysql   | 2024-08-23T10:19:11.273914Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
ragflow-mysql   | 2024-08-23T10:19:11.273959Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
ragflow-mysql   | 2024-08-23T10:19:11.286518Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
ragflow-mysql   | 2024-08-23T10:19:11.307744Z 0 [Note] Event Scheduler: Loaded 0 events
ragflow-mysql   | 2024-08-23T10:19:11.307955Z 0 [Note] Execution of init_file '/data/application/init.sql' started.
ragflow-mysql   | 2024-08-23T10:19:11.308796Z 0 [Note] Execution of init_file '/data/application/init.sql' ended.
ragflow-mysql   | 2024-08-23T10:19:11.308868Z 0 [Note] mysqld: ready for connections.
ragflow-mysql   | Version: '5.7.18'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
ragflow-mysql   | 2024-08-23T10:19:11.308877Z 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check.
ragflow-mysql   | 2024-08-23T10:19:11.308878Z 0 [Note] Beginning of list of non-natively partitioned tables
ragflow-mysql   | 2024-08-23T10:19:11.332534Z 0 [Note] End of list of non-natively partitioned tables
ragflow-minio   |
ragflow-minio   |  You are running an older version of MinIO released 8 months before the latest release
ragflow-minio   |  Update: Run mc admin update
ragflow-minio   |
ragflow-minio   |
ragflow-es-01   | Created elasticsearch keystore in /usr/share/elasticsearch/config/elasticsearch.keystore
ragflow-es-01   | Aug 23, 2024 6:19:15 PM sun.util.locale.provider.LocaleProviderAdapter
ragflow-es-01   | WARNING: COMPAT locale provider will be removed in a future release
ragflow-es-01   | {"@timestamp":"2024-08-23T10:19:15.824Z", "log.level": "INFO", "message":"Java vector incubator API enabled; uses preferredBitSize=256", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"main","log.logger":"org.apache.lucene.internal.vectorization.PanamaVectorizationProvider","elasticsearch.node.name":"es01","elasticsearch.cluster.name":"docker-cluster"}
ragflow-es-01   | {"@timestamp":"2024-08-23T10:19:16.251Z", "log.level": "INFO", "message":"version[8.11.3], pid[175], build[docker/64cf052f3b56b1fd4449f5454cb88aca7e739d9a/2023-12-08T11:33:53.634979452Z], OS[Linux/6.10.0-linuxkit/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/21.0.1/21.0.1+12-29]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"main","log.logger":"org.elasticsearch.node.Node","elasticsearch.node.name":"es01","elasticsearch.cluster.name":"docker-cluster"}
ragflow-es-01   | {"@timestamp":"2024-08-23T10:19:16.252Z", "log.level": "INFO", "message":"JVM home [/usr/share/elasticsearch/jdk], using bundled JDK [true]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"main","log.logger":"org.elasticsearch.node.Node","elasticsearch.node.name":"es01","elasticsearch.cluster.name":"docker-cluster"}

0.14.0 improved system healthy monitoring. Please upgrade.


Types are not enforced with typescript 5.5.3

Description
types are not enforced with typescript 5.5.3
Reproduction
src/repro.ts
import createClient from 'openapi-fetch';
import type { paths } from 'petstore'; // generated via npx openapi-typescript https://petstore3.swagger.io/api/v3/openapi.yaml -o src/petstore.d.ts

const client = createClient<paths>();

void client.POST('/store/order', {
  headers: {
    'Content-Type': 'application/json',
  },
  body: {
    // should result in "TS2322: Type 'boolean' is not assignable to type 'number'."
    id: true,
  },
});

tsconfig
tsconfig.json
{
"compilerOptions": {
  "lib": ["ES2023"],
  "module": "commonjs",
  "target": "ES2022",
  "strict": true,
  "declaration": true,
  "removeComments": true,
  "emitDecoratorMetadata": true,
  "experimentalDecorators": true,
  "allowSyntheticDefaultImports": true,
  "esModuleInterop": true,
  "sourceMap": true,
  "outDir": "./dist",
  "baseUrl": ".",
  "incremental": true,
  "skipLibCheck": true,
  "strictNullChecks": true,
  "noImplicitAny": true,
  "noUncheckedIndexedAccess": true,
  "strictBindCallApply": true,
  "forceConsistentCasingInFileNames": true,
  "noFallthroughCasesInSwitch": false,
  "resolveJsonModule": true
},
"include": [
  "src/**/*",
],
"exclude": ["node_modules", "dist"]
}

Expected result
npx tsc --noEmit should result in something along the lines of:
repro.ts:12:5 - error TS2322: Type 'boolean' is not assignable to type 'number'.

12     id: true,

This does work as expected with typescript 5.4.5. If you run npx tsc --noEmit with typescript 5.5.3 no error is reported (which should not be the case).
I saw that the project dependency on typescript is still on the 5.4 release. I am assuming there is some incompatibility with typescript 5.5 and this is one of the symptoms.
I took a quick look at the changed in TS 5.5 and found Control Flow Narrowing for Constant Indexed Accesses. I thought this might be related but it is just a gut feeling.
Checklist

[x] I’m willing to open a PR (see CONTRIBUTING.md)

Thanks for the great work ❤

Upgraded to typescript 5.5.3 from 5.4.5 today, and found similar issue.

I'm not able to repro with 5.5.3. I see:
$ npx tsc --noEmit
test.ts:12:9 - error TS2322: Type 'boolean' is not assignable to type 'number'.

12         id: true,

I just tested again with the latest version of openapi-typescript (7.1.0) and openapi-fetch (0.10.2) - still not getting any error (except when using ts version 5.4.5).
I also added the tsconfig.json that I used - hope this helps to reproduce it

Even with your tsconfig.json, I still can't repro. Can you make a docker image that repros issue?

I was struggling with this in a test node 20 project using @tsconfig/node20 tsconfig.json
I found if I deleted the entire "lib": [ "es2023" ], property, the type enforcement worked again.

I am on Windows 11 Pro 22H2 using Node v20.10.0.  Attached is my repo -
repo.zip
Hopefully this helps

I am running into the same issue. Multipackage repo. Upgraded to typescript 5.5.4 and some valid type errors on arguments to calls of the openapi-fetch client methods disappeared.

FYI: openapi-fetch v0.10.4 includes the fix


Legacy Authentication Tile VS Sign-ins clarification

In the definition of Legacy Auth there needs to be clarification between when the tile will show up vs a legacy auth sign-in
"The tile only shows counts of legacy auth sign in with associated session risk present, whereas the blade displays all the legacy auth sign ins."

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

ID: 2205b2a1-125a-6861-eeb4-40c30bf20bac
Version Independent ID: f63a21d1-7bbe-cfdc-6017-93ff9b872d10
Content: Azure Active Directory Identity Protection security overview
Content Source: articles/active-directory/identity-protection/concept-identity-protection-security-overview.md
Service: active-directory
Sub-service: identity-protection
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@404cruX Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

@cloudhandler Thoughts on this?

Opening an item to clarify in portal


Add Arabic translation

Description
Added Arabic language

Hi @SSekaiking  new section "Export Account" is added recently, so it would be great if there's translation for it as well. Would you be able provide it? Thanks.


add certificate pinning warning

@MikeBazMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

@MikeBazMSFT -- Unsure why this PR closed, but we've integrated your proposed changes to this PR with some edits: https://github.com/MicrosoftDocs/azure-docs-pr/pull/194737


parsing error on numerical expression

I don't know if this is related to something else, but here it is. Using Crystal 0.26.1
The code that uses this expression compiles (using --release) without errors but when run it hangs.
( d >>= ( 1 + ((d>>1) & 1)^1) ) if d.even?

However, both of these compile AND operate correctly when run.
( d >>= (((d>>1) & 1)^1) + 1 ) if d.even?

or

x = ((d>>1) & 1)^1; d >>= (1 + x) if d.even?

It seems the problem is correctly parsing the expression ((d >> 1) & 1)^1.
Here is what the correct output should be (trailing '0's are stripped off last two bits.):
     d in  | d out
-----------|-------
 7 = xx111 |   7 = xx111
 6 = xx110 |   3 = xxx11
 5 = xx101 |   5 = xx101
 4 = xx100 |   1 = xxxx1
 3 = xx011 |   3 = xx011
 2 = xx010 |   1 = xxx01
 1 = xx001 |   1 = xx001

I found what the problem was (though kind of subtle).
The original code that hung was this (minus the unnecessary outside parenthesis).
d >>= (1 + ((d>>1) & 1)^1) if d.even?

Taking away the outside parenthesis also causes the same problem.
d >>= 1 + ((d>>1) & 1)^1 if d.even?

Adding a left parenthesis solved the problem.
d >>= 1 + (((d>>1) & 1)^1) if d.even?

It seems that: 1 + ((d>>1) & 1)^1 parses to this: [1 + ((d>>1) & 1)] ^ 1.
This also hangs: ((d>>1) & 1)^1 + 1, and probably parses to this: ((d>>1) & 1) ^ [1 + 1].
This behavior is also consistent in Ruby.
So it was my misunderstanding|forgetting about operator precedence.
Maybe in the docs examples like this can be highlighted more to emphasize this type of gotcha.
So it wasn't a parsing error it was me, and you can close this now.
Thanks.

What do you mean "hangs"?

@asterite presumably never reaching the termination condition of a loop, with the loop code not shown.


refactor(global_plugins): kong to apisix global rules module

Codecov Report

Merging #31 (bbebb7a) into main (487b9ef) will increase coverage by 0.87%.
The diff coverage is 66.00%.

:exclamation: Current head bbebb7a differs from pull request most recent head 0824c0b. Consider uploading reports for the commit 0824c0b to get more accurate results

@@            Coverage Diff             @@
##             main      #31      +/-   ##
==========================================
+ Coverage   67.86%   68.73%   +0.87%
==========================================
  Files          13       13
  Lines         557      611      +54
==========================================
+ Hits          378      420      +42
- Misses        112      124      +12
  Partials       67       67

Impacted Files
Coverage Δ

pkg/kong/kong.go
24.13% <0.00%> (-1.67%)
:arrow_down:

pkg/kong/globalrules.go
50.00% <50.00%> (-20.59%)
:arrow_down:

pkg/kong/service.go
79.24% <50.00%> (-2.76%)
:arrow_down:

pkg/kong/route.go
64.81% <55.55%> (-2.46%)
:arrow_down:

pkg/kong/plugin.go
75.86% <75.86%> (+25.86%)
:arrow_up:

pkg/kong/consumer.go
84.61% <100.00%> (-2.06%)
:arrow_down:

pkg/utils/utils.go
47.61% <0.00%> (-2.39%)
:arrow_down:

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 487b9ef...0824c0b. Read the comment docs.


Missing Web Page Functionality.

I have the raspi-sump up and running...
The issue I have is seeing historical days - like what is shown here: https://raspisump.linuxnorth.org/todaychart/
I only have a link that says "past water readings" but when clicked just goes to a directory .
Seems if there is missing html pages/coding.. when comparing to : https://raspisump.linuxnorth.org/todaychart/

The web functionality with raspisump is just a bare bones view of past water readings.  The graphing you see on my web page is not part of raspisump. Those graphs are uploaded to an offsite webserver and have some programming behind them to display monthly graphs.
On the raspberry pi itself I just wanted something very bare bones that someone could see what's up with their graphs and also have access to older ones.
Making the web server display something nicer is something I would like to do, or hopefully one day a good web designer would use raspisump and see fit to contribute that part.  :-)

What external/offsite webserver are you using, if i may ask? Thank you.

I have a personal website that I host on a rented server.   I transfer my graphs there and have a web app that I wrote to display the graphs.


Fixed some build issues and updated nugets

Hi @omidkrad, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

@omidkrad, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

Thanks -- I'll take a look when I get time next week.

Looks like merging from dev to master has fixed these issues. I'll close this. Thanks.


Fix icon updating on secondary outputs

Should fix https://github.com/swaywm/sway/issues/1372#issuecomment-345648415
For https://github.com/swaywm/sway/pull/1431
Thanks you!

Thanks a lot for looking into this!

@4e554c4c Done, thank you!

Thanks!


RouteNet Problem

The output channel of RouteNet is 1, why the prediction image in the guidance document is color

Because a color map is used to plot the image. The original prediction is 1 channel.


Getting issue "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections" after running the mvc web app after deployment to aci

Getting issue "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections"
I followed same steps as in article to deploy the images to ACI

Hey @vinitgadre - are you able to connect to it through SSMS? I just want to rule out using the incorrect connection string/credentials in the application. An easy way to test that is to make sure you can connect to the database through SSMS to verify username, password, connection string.

Hi @vinitgadre , I am closing this issue as of now as it's inactive for sometime now. Please feel free to reopen it, if you have any further questions.
Thank you.


New org: Palisade research

https://palisaderesearch.org/team

Check https://github.com/riceissa/aiwatch/commit/294eebcd94c27070ac851f90d6d976e121beec58


Use PropertyPlaceHolder for parameter substitutions in RecipeSearchResult

Based on CR feedback from @jkschneider and @tkvangorder I didn't get to in #427

We haven't had a use-case compelling enough to get around to actually implementing this yet. Closing until we do.


Search fails to register keypresses with combo box closed

If the user tabs into a closed ui-select combo box and types quickly the keypresses may not register.  The behavior gets worse the longer the list, though it doesn't take many items for the behavior to become consistent.
For example, the attached plunkr is the Basic example from the ui-select home page with $scope.people modified to be significantly longer.  To replicate the issue place the cursor in the "Enter an address" field, press Tab then type "adr" quickly and notice the d and r often do not register.
It appears under the hood ui-select is reverting the search string.  Debugging in the propsFilter shows it will search for "a" then "ad" then "adr" then "a" again.
Link to minimally-working plunker that reproduces the issue:
http://plnkr.co/edit/VBPQvQdsQ7bNUymNHLwp?p=preview
Version of Angular, UI-Select, and Bootstrap/Select2/Selectize CSS
Directly from the Basic demo plunkr
Angular: 1.5.0
UI-Select: 0.19.5

Can you tell me it this is for all themes of the ui-select?

Yes, it affects all themes.

Here is some additional information that will hopefully expedite a fix.  When the combo is closed (tab into it) and a key is pressed it is handled by
focusser.bind("keyup input", function(e){...}
If the rest of the search is typed slowly then all of the key inputs are received by
ctrl.searchInput.on('keydown', function(e) {...})
but if the rest is typed quickly the keydown handler is never called and $watch on $select.search is never triggered.

+1

I have huge issues with this as well. Many people complain that their characters get eaten away when typing when the dropdown is closed. So if anyone has some kind of workaround that I could implement to solve it, let me know. It is especially frustrating because this dropdown is used in a form that gets used very frequently, and thus efficiency is quite important. The form it is based in is also completely tab optimized to reduce the total number of keypresses needed.


sandcastle example text styling

Fixes #5267. Cleaned up a few legibility issues also.
Part of #5270 too!

Thanks @rahwang!  @emackey do you want to look at this?

Looks good, thanks @rahwang!


Import relative images to markdoc file

is there any way to make the preprocess import relative images and videos... to the markdoc file
something like mdsvex-relative-images

I have a PoC ready here #81 - however I wanted to implement it with the enhanced image feature.
Unfortunately it is current not possible to do this. I will look into allowing it without the enhanced image feature 👍🏻

https://github.com/TorstenDittmann/svelte-markdoc-preprocess/releases/tag/2.0.0 should be working now :)


FE: route test room asset preview page

added https://github.com/webaverse/webaverse.com/compare/fcadc5ff178b...5edef71f846c

added https://github.com/webaverse/webaverse.com/compare/fcadc5ff178b...5edef71f846c


Leshan Bootstrap new Sequence mode

Question
Some of devices DO NOT handle the DISCOVER operation during the Bootstrap Sequence. Unfortunately, we do not know in advance if a device will support it or not.
Currently in Leshan, you can choose between 2 modes:

Mode A) Leshan does NOT perform any DISCOVER and uses the instance number 0 as the one used for Bootstrap Server.

Mode B) Leshan does a DISCOVER in order to get the information on what is the instance number used by the device to hold Bootstrap Server informations. This is the Opt area named autoIdForSecurityObject == true below

Our problem is that it is difficult to know in advance if a specific device will supports the Bootstrap Discover correctly or not. Which is quite impossible to know in advance if we should use Mode A) or Mode B).
We would like to implement a new mode, which can be summarized in this way:

Mode C) Leshan do start with Mode B), but if the DISCOVER fails, then it continue as a failover to Mode A) instead of failing the Bootstrap Sequence.

Yep, I get the issue.
The current idea in Leshan :
There is 2 ways to provide "requests to apply during a bootstrap session" :

a pretty simple way but feature limited via BootstrapConfigStore interface.
a full feature one via BootstrapTaskProvider interface.

And also, if you just want to do minor changes you can just extend default Leshan implementation of those classes.
A solution at short term :
You can create your own BootstrapConfigStoreTaskProvider and change the default behavior.
FMPOV, this is OK to do that. I mean I don't see that as a workaround but a normal usage of API.
Leshan does not plan to support all cases but try to have an open enough API to change behavior.
The remaining question:
Do we want to add this mode C) to BootstrapConfigStore API ?
I'm must confess that I don't know...
This is always a trade-off between "providing more feature" and "limit the scope to try to keep the library maintainable".
In this particular case, this is not too much of code, so maybe we can add it ...
Another solution is to change BootstrapConfigStoreTaskProvider to make easier to customize the way discover response is handled ?

I prepared this PoC . (apologies for the frontend part - not too familiar with vue :wink:  ) What do you think - can we implement something similar in Leshan ?

Yep this is what I understood when I read your very well described issue.
But I'm still not sure this should be in Leshan library like I explained just above :point_up:
So I would like to clarify this before.
On your side Is it a behavior  :

you need in production / real life ?
or something you think it would be good to add to Leshan to make it better ?
or both ?

I know it seems I always try to limit new additions in Leshan but my goal is to limit the scope as much as possible at the LWM2M specification itself. Adding too many features makes maintenance or future refactoring harder. Here this sounds small changes but last time I rewrite the UI completely,  all the small feature makes the migration very long. (I even decide to remove some of them)
Anyway, I'm counting on you to help me to keep the scope of Leshan small enough to be maintainable :pray:
About this new mode I have some concerns:

if you don't know how to bootstrap your device in production, the mode "NONE" auto mode could lead to serious problem : see https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/522 and https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/523. So a mode which fallback on it sounds not so good.
I'm not sure we want to multiply the number of mode as I said BootstrapConfigStore is the very simple API. The full feature one is BootstrapTaskProvider

(not too familiar with vue)

Me too :sweat_smile:


Incorporate FIELDimageR feedback

Task to do
Incorporate FIELDimageR feedback from Alpha tester
Reason
Improve useability
Result
README, and possible app, changes
see: agpipeline/issues-and-projects#341,  agpipeline/issues-and-projects#349,  agpipeline/issues-and-projects#350

Closing since the referenced issues are completed and closed


Get only one pot file as output.

Hello, the output of poextractor is a POT template for each project, which can be a bit annoying at times, especially when using POEdit to translate strings. It might be worth considering an option to generate a single POT file as output instead. If this feature is welcomed, I will look into implementing it.

Feel free to submit a PR

So if you invoke the command with "-s messages.pot" you will get a single file as output.

Don't forget that "messages" could be found in multiple projects

So if you invoke the command with "-s messages.pot" you will get a single file as output.

Don't forget that "messages" could be found in multiple projects

What do you mean? By "-s messages.pot", I mean the single output file.
Let me clarify: imagine we have this structure:

src

Project1
Project2

If you run "dotnet poextractor ./src ./src", you will find "Project1.pot" and "Project2.pot" in the src directory.
With this feature, if you run "dotnet poextractor ./src ./src --single messages.pot", you will find "messages.pot" in the src directory, containing all the msgIds retrieved from Project1 and Project2.

Got it, the output could be {culture}.pot

Got it, the output could be {culture}.pot

Why you would specify culture for the pot file?
POT files are the template files for PO files. They will have all the translation strings left empty. A POT file is essentially an empty PO file without the translations, with just the original strings.
So they are "CultureInvariant" :)

Waiting for your PR then we could see


Cant add folder from mounted network drive to workspace

VSCode Version: 1.47.3
OS Version: Window 10 x64

Steps to Reproduce:

Map a network drive
Add folder to workspace
Only local drives are available, network drives do not show in the "select folder" window

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

For real? It's the window that opens to select the folder to add to workspace.
There is no network drive in it.

We do not control this dialog, it originates from Windows. I suggest you report an issue against Windows support.

Any other window not opened from VSCODE shows the mapped folder.


(DOCSP-26295) Adds annotations for more than one example

Proposed changes
We decided to hold off on doing io-code-blocks with outputs for now, but I still wanted to make a few improvements to the way we show examples in the autogenerated docs. These changes add annotations for additional examples, which will display in their own code block. An additional PR has been filed for mongodb-atlas-cli, but that PR needs to be rebased after this one merges.
I have tested this change locally.
_Jira ticket: https://jira.mongodb.org/browse/DOCSP-26295
Checklist

[] I have signed the MongoDB CLA
[] I have added tests that prove my fix is effective or that my feature works
[] I have added any necessary documentation (if appropriate)
[] I have run make fmt and formatted my code

Question: I have reduced the cyclomatic complexity as much as I can (from what I can tell) and it's still more than 16, is that a blocking error?
Still working on adding tests, getting some errors with that but hope to get it resolved soon

@gssbzn Reducing the complexity got rid of that error! Thanks for the advice on that.
For the test: it won't let me add Example more than once, but it also doesn't like me formatting it like the annotations. I will give the test another shot when I have time but I have confirmed that the examples look as expected when looking at what is generated by make gen-docs using my local cobra2snooty file for files with 0-5 examples and with/without # symbol.


[BUG] Qdrant didn't follow metadata search filter

Describe the bug
Upserting two txt documents marked by a different "source" metadata (following this  approach), and setting in Qdrant filtering parameters the correct structure as defined here, in any case only a single document information is retrieved during the chat, always the same document. Tested both with Claude and GPT, checked and Qdrant has correctly saved the data with their metadata.
To Reproduce
Steps to reproduce the behavior:

Use attached flow, change the system prompt in English
Use attached txt (apologize they are in Italian, but doesen't matter with the multilanguage LLMs like Claude)
Ask about the content of the document, will be always answered about the Neanderthal even if in the Qdrant filter is set habilis as source

Expected behavior
Since the source is set "habilis" I expect will answer questions regarding the habilis document.
Screenshots
Ask anything
Flow
Attached
Setup

Installation npx flowise start
Flowise Version 1.6.5
OS: linux
Browser Firefox
Qdrant 1.9.0 image running locally using
docker run -p 6333:6333 -p 6334:6334     -v $(pwd)/qdrant_storage:/qdrant/storage:z     qdrant/qdrant

Additional context
Habilis.txt
Neanderthal.txt
Two document Qdrant test Chatflow.json

@davide445 thanks for the bug! PR to fix that - https://github.com/FlowiseAI/Flowise/pull/2285
Reason being the filter was not passed to the VectorStore To Document node


Add "my dashboard" link in top nav bar on patient screens

@NerdyGirl537 and @lwaldsc said on Monday that it wasn't terribly clear to them how to get from the pregnancy edit form back to the main dashboard. Is there some merit to adding some explicit nav text in the top bar?

Still needs design work. What will it say and where will it go?

(Changing this to a design issue.)

Adding this to the wireframes and invisio soon:

Turned into dev issues and just waiting on tests at this point -- I think we can consider this resolved from a UX perspective.


Yew crashes when receiving websocket messages.

Problem
Yew app crashes with RuntimeError: invalid malloc request and RuntimeError: unreachable.
App is UI which opens websocket connection and listen to it. It crashes after many websocket messages received. The rate of receiving messages is not high just about 2 messages per second. Still it crash sometimes in few minutes e.g. 5.
WS connection is open all the time and browsers keep receiving messages after the crash and each message keeps raising two errors.
Steps To Reproduce
I Have problems reproducing, even on my local computer it takes hours to force the Yew app to crash.
Basically, I took the dashboard example and modified it to receive async_graphql WebSocket messages. The more messages come, the sooner it crashes. So at beginning of project, there were no crashes at all.
Expected behavior
No crash or crash showing my code in the stack trace.
Logs
wasm_bg.wasm:0x5a80b4 Uncaught RuntimeError: unreachable
    at rust_oom (https://macmini.local:4001/www/wasm/wasm_bg.wasm:wasm-function[26850]:0x5a80b4)
    at __rg_oom (https://macmini.local:4001/www/wasm/wasm_bg.wasm:wasm-function[27094]:0x5a929c)
    at __rust_alloc_error_handler (https://macmini.local:4001/www/wasm/wasm_bg.wasm:wasm-function[27077]:0x5a91c1)
    at alloc::alloc::handle_alloc_error::h67f29d7cba135f71 (https://macmini.local:4001/www/wasm/wasm_bg.wasm:wasm-function[27093]:0x5a9290)
    at alloc::alloc::exchange_malloc::h940980a6ffc8d77c (https://macmini.local:4001/www/wasm/wasm_bg.wasm:wasm-function[5468]:0x3dba3f)
    at yew::html::scope::Scope<COMP>::update::hec3de0a42d64622c (https://macmini.local:4001/www/wasm/wasm_bg.wasm:wasm-function[1153]:0x2576c1)
    at yew::html::scope::Scope<COMP>::send_message::h89a8d6d6103cea14 (https://macmini.local:4001/www/wasm/wasm_bg.wasm:wasm-function[1581]:0x2a03c8)
    at yew::html::scope::Scope<COMP>::callback::{{closure}}::h113ef30a27c9fc7e (https://macmini.local:4001/www/wasm/wasm_bg.wasm:wasm-function[3122]:0x346934)
    at yew::callback::Callback<IN>::emit::h9afdae078505f23b (https://macmini.local:4001/www/wasm/wasm_bg.wasm:wasm-function[2520]:0x310848)
    at yew::services::interval::IntervalService::spawn::{{closure}}::h63466f5fe438f00d (https://macmini.local:4001/www/wasm/wasm_bg.wasm:wasm-function[22948]:0x5820ad)
rust_oom	@	wasm_bg.wasm:0x5a80b4
__rg_oom	@	wasm_bg.wasm:0x5a929c
__rust_alloc_error_handler	@	wasm_bg.wasm:0x5a91c1
alloc::alloc::handle_alloc_error::h67f29d7cba135f71	@	wasm_bg.wasm:0x5a9290
alloc::alloc::exchange_malloc::h940980a6ffc8d77c	@	wasm_bg.wasm:0x3dba3f
yew::html::scope::Scope<COMP>::update::hec3de0a42d64622c	@	wasm_bg.wasm:0x2576c1
yew::html::scope::Scope<COMP>::send_message::h89a8d6d6103cea14	@	wasm_bg.wasm:0x2a03c8
yew::html::scope::Scope<COMP>::callback::{{closure}}::h113ef30a27c9fc7e	@	wasm_bg.wasm:0x346934
yew::callback::Callback<IN>::emit::h9afdae078505f23b	@	wasm_bg.wasm:0x310848
yew::services::interval::IntervalService::spawn::{{closure}}::h63466f5fe438f00d	@	wasm_bg.wasm:0x5820ad
<dyn core::ops::function::FnMut<()>+Output = R as wasm_bindgen::closure::WasmClosure>::describe::invoke::h03ad3f3745367f24	@	wasm_bg.wasm:0x40ce5d
__wbg_adapter_22	@	wasm.js:241
real

wasm.js:842 Uncaught Error: invalid malloc request
    at imports.wbg.__wbindgen_throw (wasm.js:842)
    at wasm_bindgen::throw_str::h5423696a78b19a26 (:4001/www/wasm/wasm_…ion[20434]:0x55fc66)
    at wasm_bindgen::__rt::malloc_failure::h6a44efb96848400b (:4001/www/wasm/wasm_…ion[26847]:0x5a8066)
    at __wbindgen_malloc (:4001/www/wasm/wasm_…tion[3109]:0x345869)
    at passStringToWasm0 (wasm.js:87)
    at imports.wbg.__wbindgen_string_get (wasm.js:829)
    at wasm_bindgen::JsValue::as_string::h4700afe3e41a6a13 (:4001/www/wasm/wasm_…ion[14938]:0x502084)
    at yew::services::websocket::process_text::h4cc89e9e2f9b049a (:4001/www/wasm/wasm_…tion[1136]:0x253d8d)
    at yew::services::websocket::WebSocketService::connect_text::{{closure}}::h78e1bd6fc71b5b24 (:4001/www/wasm/wasm_…ion[12138]:0x4c391b)
    at <dyn core::ops::function::FnMut<(&A,)>+Output = R as wasm_bindgen::closure::WasmClosure>::describe::invoke::h820eeadb6b7c14b7 (:4001/www/wasm/wasm_…tion[4239]:0x3960ba)
imports.wbg.__wbindgen_throw	@	wasm.js:842
wasm_bindgen::throw_str::h5423696a78b19a26	@	wasm_bg.wasm:0x55fc66
wasm_bindgen::__rt::malloc_failure::h6a44efb96848400b	@	wasm_bg.wasm:0x5a8066
__wbindgen_malloc	@	wasm_bg.wasm:0x345869
passStringToWasm0	@	wasm.js:87
imports.wbg.__wbindgen_string_get	@	wasm.js:829
wasm_bindgen::JsValue::as_string::h4700afe3e41a6a13	@	wasm_bg.wasm:0x502084
yew::services::websocket::process_text::h4cc89e9e2f9b049a	@	wasm_bg.wasm:0x253d8d
yew::services::websocket::WebSocketService::connect_text::{{closure}}::h78e1bd6fc71b5b24	@	wasm_bg.wasm:0x4c391b
<dyn core::ops::function::FnMut<(&A,)>+Output = R as wasm_bindgen::closure::WasmClosure>::describe::invoke::h820eeadb6b7c14b7	@	wasm_bg.wasm:0x3960ba
__wbg_adapter_25	@	wasm.js:255
real	@	wasm.js:201

Environment:

Yew version:0.17.4
Rust version: stable 1.49, 1.50
Target, if relevant: [e.g. wasm32-unknown-emscripten]
Build tool: wasm-pack
Build OS: Linux and MacOS
Browser: Firefox and Chrome

Questionnaire

[ ] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[ ] I don't have time to fix this right now, but maybe later

I'm interested in fixing this myself but don't know where to start

The example mentioned here used to use WebSocketService which has been removed. Also, there really isn't enough information for this to be actionable. Can this be closed now?


Update readme

This updates the readme to add the new options available in <relative-time>

:wave: Hello and thanks for pinging us! This issue or PR has been added to our inbox and a Design Infrastructure first responder will review it soon.

:art: If this is a PR that includes a visual change, please make sure to add screenshots in the description or deploy this code to a lab machine with instructions for how to test.
:fast_forward: If this is a PR that includes changes to an interaction, please include a video recording in the description.
:warning: If this is urgent, please visit us in #primer on Slack and tag the first responders listed in the channel topic.


In chains with multiple sub-chains, Is there a way to pass the initial input as an argument to all subsequent chains?

In chains with multiple sub-chains, Is there a way to pass the initial input as an argument to all subsequent chains?
Can we assign variable names to outputs of chains and use them in subsequent chains?

I am trying to get additional information from an article using preprocess_chain. I would like to send the original article and the additional information to an analysis_chain.
# Chain1 : To get additional info about an article
preprocess_template = """Given the article. Derive additional info
% Article
{article}

YOUR RESPONSE:
"""
prompt_template2 = PromptTemplate(input_variables=["article"], template=stakeholder_template)
preprocess_chain = LLMChain(llm=llm, prompt=prompt_template1)

#Chain2: Would like to pass both original article and response of chain1 to chain2
analysis_template = """Analyse the article in context of additional Info.
% Article
{article}           ### Need help adding this variable here

% Additional info
{additionalInfo}

YOUR RESPONSE:
"""
prompt_template2 = PromptTemplate(input_variables=["article","additionalInfo"], template=stakeholder_template)
analysis_chain = LLMChain(llm=llm, prompt=prompt_template2)

overall_chain = SimpleSequentialChain(chains=[preprocess_chain,analysis_chain], verbose=True)
overall_chain.run(articleText)

Sequential chain lets me do this. Thanks.
https://python.langchain.com/en/latest/modules/chains/generic/sequential_chains.html


Remove unnecessary internal debugging traces

Goal

Testing

Release Notes

WHAT:
WHY:
WHO:

Current dependencies on/for this PR:

master

PR #92

PR #93   👈

This stack of pull requests is managed by Graphite.


Customer Freeman Health: Revisit implementation on product implementation for storage of empty array and empty map vis-a-vis Sailpoint API spec versus std JSON API spec

Existing product implementation for storage of empty array and empty map specified in JSON config for following API calls:
POST and PUT /v3/service-desk-integrations:
Denali (Abhishek team) DevRel persists the following in JSON config correctly:
{
"empty array": [],
"empty map": {}
}
However, JSON config then currently incorrectly persisted in underlying XML by Platform DevEx (Alex Peda) (Org Portal) as:

Required to be correctly persisted in XML by Platform DevEx (Alex Peda team) (Org Portal) in order for XML to represent empty array and empty map accurately:

Subsequently, in order for Platform connectivity (Pradeep team) in ccg product code to serialize application XML provided to ccg correctly into config java object for attr vals as:
"emptyarray", new ArrayList()
"emptymap", new HashMap()

/v3/service-desk-integrations -> Denali team.
Correct Specs and clarification on what should happen in case of:
{
"empty array": [],
"empty map": {}
}
-> DevRel team
How object XMLs are displayed in org-management portal -> PLTTOOLS/Devex team
How ccg product code to serialize data from either CIS or API call -> Platform connectivity


Is there a significant difference in training results for the SeperationBlock and SeperationBlock_stateful?

I saw that you have written two forms of SeperationBlock. The only difference between them is whether to return the hidden state out. What's the point of doing this? And which implementation has better performance? thank you for your response.

@c8x1  "hidden state out" is for realtime enhance, which process trunk  by trunk, it has better performance when in inference

看到你好像是中国的，那就不用蹩脚英语了 :D.
所以stateful的就只是用来推理的咯？
我之前也有试过把hidden传出来的训练方式，目的是把这batch的hidden state作为下一个batch的hidden state初始值，避免训练的片段比较短，实际推理又比较长的RNN泛化问题，跟这个是两回事是吧？

对的， 应该是两个问题。

感谢哈，你的模型实现简洁易懂！

@c8x1  谢谢， 我们有问题再交流


Add Domain for Sungava College

@AvisarBhandari First stage of verification passed, official domain for Sungava College is sungavacollege.edu.np as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@AvisarBhandari Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


[Feature Request] Want to add an anchor component

Existing Component
否
Component Name
Anchor
Description
You need to show anchor links that can be jumped on the current page, and jump quickly between anchors.
like this

https://ant.design/components/anchor-cn/#components-anchor-demo-basic

pr welcome.


Add reCaptcha support to the contact us form

This feature would be for unregistered users for now.  There have been some spam submissions through the demo app making this feature seem to be a good idea.

I've just found this awesome boilerplate! I am currently self-isolating with nothing better to do, so if @sahat is accepting PR's I'll add this when I get a second.

PRs are welcome for this.  A couple of potential requirements:

I think it would be reasonable to require it only for unknown users though https://github.com/sahat/hackathon-starter/blob/master/views/contact.pug#L9 .
If I recall correctly for using reCaptcha the server needs to have an API key.  A potential issue with requiring an API key for a basic feature is that it may slow down devs that would like to get started quickly, especially in the context of a hackathon.  I'm not sure if there is a way to do a professional-looking captcha without an API key or if there is a way to define a fallback where the captcha is skipped if there is no valid API key.

@YasharF thanks for the heads up on this. I've not used pug before o I'll do a little reading up on the templating first, but it should be easy enough to integrate something with a default switch to off.
I notice GA is added inside https://github.com/sahat/hackathon-starter/blob/37034e6724a656f912e61a7444cb1ea8588cab5b/views/layout.pug#L29 to keep google in one place I could add a var in here for reCAPTCHA which can be tested in contact.pug then load the recaptcha if its been included in the layout?

It is not a layout component, the frontend needs to stay within contact.pug

Support added by https://github.com/sahat/hackathon-starter/commit/ab05ce661c037daeeea06b8ee34a44db942fbd24


Improve Attribute Value error message

Improve the error message when an error occurs during the creation of values from attributes.
Previously if an error occurred during the population of the Values object from the attributes, then the error message was sometimes very obscure.  For example if an array is passed where a string was expected then the error message would be a ClassCastException with no explanation of what attribute.  This change is intended to capture those errors and add information for debugging the problem

Looks good for me :-), thanks


Missing paper and datasets query.

Hi there,
In the README file it states "Please cite our paper below if you utilize these data sets". As far as I can see, there is no paper, please can you confirm it is meant to be this one: https://ieeexplore.ieee.org/document/10194079
Also, where are the benchmark datasets? The repository contains the README file and the LICENCE file, but nothing else. I would like to make use of the dataset for a university project.
Many thanks,
Phil.

Hi Phil,
Thank you for reaching out.  Yes, that's the right paper.  We will work to add that to the README file.
The benchmark datasets are in https://github.com/Boeing/sdr-hazards-classification/tree/main/src/sdr_hazards_classification/data.  That's our official repo that covers all types of hazards including depressurization.
Please let us know if you have more questions.

Closed


test/helpers module to store AppendRandomString helper fn

Fixes: #226
I have added the helper functionAppendRandomString into test/helpers module (helpers being a new module), sample usage:
package pkg

import (
	"github.com/knative/pkg/test/helpers"
	"testing"
	"strings"
)

func TestAppendRandomString(t *testing.T) {
	s := helpers.AppendRandomString("myprefix")

	if !strings.HasPrefix(s, "myprefix") {
		t.Fatalf("Failed to verify prefix: %s", s)
	}

	if len(s) != 18 {
		t.Fatalf("Failed to verify string size: %d", len(s))
	}

	t.Logf("---%s---", s)
}

I was looking for a first good issue and this one looked simple enough :)

/ok-to-test

/assign @jessiezcc

the same function exists at https://github.com/knative/serving/blob/master/test/crd.go already.
But it makes sense to move it out of serving to pkg. Added comments in code.

/hold

/hold cancel
/lgtm

/approve


PyPi czml3 release is outdated

Please push a new version to PyPi. We want to obtain new changes in the master branch with pip. I can help with this if you give me access. Thanks.

Thanks for the nudge @mixxen, will do this week 🙏🏽

Let me know if I can help with pushing a new version.

I've made a pull request #108  for this.

PR #108 has been merged. I recommend pushing a new version to pypi and closing this.

Somebody wants to contribute a release workflow using github actions? I'll fill it with my PyPI token of course.

Why not do a manual upload to PyPi?
In any case, are you referring to something like this?

https://github.com/poliastro/czml3/issues/112


Update app-service-custom-domain-name-migrate.md

When dealing with wildcard validations I found out that docs were not clear on how it works.
This PR is intended tries to give insight with very minor key detail and prevent users to get into a pitfall.

@Bartmax : Thanks for your contribution! The author, @cephalin, has been notified to review your proposed change.

@apurvajo Can you please take a look at this change?

#sign-off


Client Unable to Read Terminal Output After Update to Version 2.2.2

Which API Provider are you using?
Anthropic
Which Model are you using?
Claude 3.5 Sonnet
What happened?
We have been using the Client for a while, and everything has worked smoothly until now. In the last few days, the transition between the Terminal and the Client functioned perfectly. However, since updating to version 2.2.2 yesterday evening, the Client can no longer read the Terminal output.
Steps to reproduce
Update the Client to version 2.2.2.
Attempt to use the Client to interact with the Terminal.
Observe that the Client sends commands successfully but cannot read the Terminal output.
Relevant API REQUEST output
mainThreadExtensionService.ts:78 [saoudrizwan.claude-dev]Promise timed out after 4000 milliseconds
mainThreadExtensionService.ts:79 TimeoutError: Promise timed out after 4000 milliseconds
	at c:\....\.vsco…tension.js:777:5670
	at new Promise (<anonymous>)
	at Cxe (c:\....\.vsco…tension.js:777:5371)
	at Jd (c:\....\.vsco…tension.js:777:6479)
	at Xue.runCommand (c:\....\.vsco…tension.js:920:1741)
	at RJ.executeCommandTool (c:\....\.vsco…tension.js:2003:605)
	at async RJ.presentAssistantMessage (c:\....\.vsco…tension.js:2040:870)

Additional context
Expected Behavior:
The Client should be able to both send commands to and read outputs from the Terminal, as it did before the update.
Actual Behavior:
The Client successfully sends commands to the Terminal.
The Terminal processes the commands and generates output.
The Client, however, cannot read the Terminal's output.

Troubleshooting Steps Taken:
Tried different shell configurations.
Restarted both the Client and the Terminal.
Uninstalled and reinstalled the Client.
Verified the issue persists across all attempts.

Environment:
Client version: 2.2.2
Operating system: [Your OS and version, e.g., Windows 10, macOS 13, etc.]
Shell type: [e.g., Bash, Zsh, etc.]

This issue only started after updating to version 2.2.2. Prior to the update, the Client functioned flawlessly in this regard.

I want to second this.
SYSTEM INFORMATION
Operating System: Linux 6.8
Default Shell: /bin/bash
As additional information: vs cide gives me an error that looks like this:

After asking CLINE where the information about the starting directory comes from it said that it is provided in the system message. So my guess is that the system message accidently sets the relative path to the repo instead the default path of the terminal as "Working directory",

I'm having a similar issue

I resolved the problem. It was partially my fault. Let me explain:
I used some git extensions for Azure Repos and Github, which evidently do not check out the  repo you select, but work with it in some kind of "online" way. This led to the path of the repo reported to CLINE being a relative path in the repo (Azure, Github), which does not work for the terminal, which expects a local path. So that was one problem. The solution was not to use vs code extensions but to check out the projects locally with an external git software (such as "git").
Secondly, i installed "fish" as terminal and set it as default for vs code. Now the problems are resolved.

Fixed it by using older Powershell Version

Thank you @Jenscaasen @mprofi for reporting back, shell integration problems like this are not uncommon so if you run into anything else please use https://github.com/saoudrizwan/shell-integration-problems to create a min reproducible environment that we can send to the vscode team.


Refactor QPDF object cache and xref table

This PR contains some preparatory work for ensuring that the object cache only contains null entries for deleted objects.
As the approach taken may be controversial some early feedback would be useful.
(This is a very early draft with obvious omissions, eg deleting constructors, controlling access, etc)

Just FYI, I am not going to distract myself from pages work until I get it into a sustaining place.

You'll have to describe verbally what you're trying to achieve and why. I don't want to spend time trying to reverse engineer your thoughts from the code. As you know, I'm not inclined to get distracted by architectural changes while I'm doing pages work, but I want to start looking at better support for incremental update as a step on the path toward digital signature support of some type, and I feel like what you're doing here may be relevant to that.

I am only looking for feedback on two points at the moment:

are you ok with moving QPDF::Members (and other inner classes that expose Members in inline methods) into a private header file (which I have named QPDF_private), and

are you ok with encapsulating the object cache and xref table into their own classes and restricting access to their underlying containers to those classes?

The immediate driver for this work is the multiple generations for a single object id problem. The one way to ensure that there are never multiple generations for the same id in the object cache and xref table is to index them by id only rather than by objgen, and making the gen part of the value.
However, changing the xref table and object cache is made difficult by the fact that they are accessed directly in numerous places in QPDF.cc and QPDF_xxx.cc as well as (through copies) by QPDFWriter. The current work tries to address that difficulty by eliminating the direct access and replacing it by access through a limited number of specific methods. Those methods can then be modified to implement the desired changes, as well as any future changes that will be required.
There are two complications that affect this work:

access to the object cache is performance critical, and
there is a close connection between the object cache and the private QPDFObject  and QPDFValue classes.

To make the encapsulation viable a number of methods that include access to private classes need to be in-lined and therefore
can not live in a public header file.
In addition to dealing with the multiple generations issue, encapsulating access and/or changing the key from objgen to id only should provide a number of benefits and future opportunities:, e.g.

Implementation of a flag for unchanged objects should be easier. (This could be extended to other flags, eg validated. Clearly an object that has been validated does not need to be re-validated unless it has been changed).

The underlying container type for both tables could be changed from map to vector. This should reduce runtime and, except for files with an extremely high proportion of deleted objects, footprint.

More methods could be cleanly exposed to the rest of qpdf without making it part of the public API. A public inline method implemented in a private header file can't be called from outside qpdf.

Direct access to QPDFObject and QPDFValue can be moved to those inner classes that really need it, reducing or eliminating such access by QPDF itself.

What you're describing sounds fine in principal, and these seem like good, worthwhile changes. That said, I really want to focus on pages work while I still have time to devote to it, and I don't want to distract myself on this issue right now, so there is some risk that if you do it, it will sit for a long time and that you will deal with merge conflicts. This may be on the minor side because I don't think my pages work will touch the QPDF object itself that heavily.
Also, I am thinking about incremental updates. A good part of that work will be modifying QPDFWriter, but my current thinking is that QPDF will need to somehow represent incremental updates. What I'm thinking is having QPDF objects be layerable in very much the same way PDF files are. This would not always be on. Most of the time, QPDF would be have as it does today, but I would want the option of having an incremental update QPDF. My thought is that it would have a "previous" that it would resolve objects that were unknown with some semantics to allow an incremental update to create a new generation without deleting the old one (an error, but it happens). Having the object cache and xref table be based on object ID only would be an important aspect of this, but obviously there has to be a way to make sure you only get a hit when the generation is right. Consider:

Original creates object 8 0
First incremental update deletes 8 setting the next gen to 1
Second incremental update defines 8 1

We'd have three QPDF objects that are stacked in some way with bidirectional knowledge. An attempt to resolve 8 0 R from even the original QPDF would have to result in null, but the 8 0 object definition would have to remain in that file so that, when it is written incrementally, it will still be there. This will require a QPDFWriter mode that preserves object IDs (a feature that has been requested anyway) or that renumbers consistently and has generation awareness. QPDFWriter currently never writes a generation > 0.
PLEASE don't go off and try to implement what I just described. I am not prepared to have this aspect of qpdf evolve through someone else's work. That will cause me to lose track even further of the internals, and I already feel like it's slipping through my fingers with all your work. I'm sharing this with you in hopes that, if you work on refactoring the xref table and object cache, you do so in a way that at least doesn't make what I've described harder than it already is. When I get to this, I will welcome your participation and support, but I don't want you to run off and build it on your own. Going through the process of designing and building a solution is an integral part of my maintaining an accurate mental model, and I need the insights I gain by doing it wrong and fixing it over multiple increments to optimize how I create future feature enhancements.

I did not spot a requirement to write an increment update when deleting an object before it can be reused. A logical conclusion of such a requirement would seem to be that an application that updates a pdf file (not incrementally) must always renumber objects.

I don't understand this comment.

I am not sure I understand this. My expectation was that to support incremental updates, QPDFWriter would copy the original file and then write the updates. For this it needs to know what objects are used in the original file but would not need to know how to recreate the objects. What am I missing?

The ability to look at incrementally updated files in QDF mode or to perform other updates for inspection purposes. That would invalidate signatures, etc., but is still a useful case that people have asked for.

Only one generation of an object is allowed to exist. In practice, if object a b exists, then any a c where c < b should be treated as null regardless of whether there are any explicit deletes. As far as I recall from previous experimentation, this is how all readers work. Adding a deleted object to the xref table allows you to delete the object without immediately reusing it and stores the next generation that should be used so that reusing the object doesn't accidentally resurrect any dangling references to the old generation. I probably misspoke and it's probably valid to reuse with deleting, but I haven't reread that part of the spec in a while. It doesn't matter though. In practice, the correct behavior is to treat the highest generation as valid and anything as null, and this definitely means obj_cache and xref_table should be indexed by object id only but have awareness of generation. I was on the verge of making that change myself and it probably would be the next thing I would do after pages unless you do it first. I would want to create some manual examples of things like adding a lower generation in an incremental update to see what various readers do, but I'm reasonably certain that is the highest generation that wins.

I probably will beat you to it.

Closed as this is very much out of date


add req + pep8 changes

Small changes

Thanks for the PR and sorry for the inactivity. Please resolve conflicts with master first.

Hi there,
we got rid of the pandoc requirement entirely with our fork at [1], so we might want to close this.
With kind regards,
Andreas.
[1] https://github.com/hiveeyes/dwdweather2


Specify vsphere template in latest release tests

Description of changes:
Ubuntu doesn't support autoimport anymore so we can't rely on it to set
the template when creating clusters using the latest minor release.
Bottlerocket doesn't strictly need this but making the same change as
well for consistency. Plus it's a more robust solution since it doesn't
need to write to vsphere, avoiding race conditions with other test runs.
Using env vars for consistency with the rest of the input data. The env
var name is constructed from the OS and EKS-D version. These env vars
need to be set prior to running the tests.
When we release a new eks-a version with new eks-d versions, we need to
import template for those and add new variables for the tests to work
properly.
New variables that we need to add:
T_VSPHERE_UBUNTU_KUBERNETES_1_20_EKS_19
T_VSPHERE_UBUNTU_KUBERNETES_1_21_EKS_17
T_VSPHERE_UBUNTU_KUBERNETES_1_22_EKS_9
T_VSPHERE_UBUNTU_KUBERNETES_1_23_EKS_4

T_VSPHERE_BOTTLEROCKET_KUBERNETES_1_20_EKS_19
T_VSPHERE_BOTTLEROCKET_KUBERNETES_1_21_EKS_17
T_VSPHERE_BOTTLEROCKET_KUBERNETES_1_22_EKS_9
T_VSPHERE_BOTTLEROCKET_KUBERNETES_1_23_EKS_4

Testing (if applicable):
Ran a couple of ubuntu and a bottlerocket tests.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold until I prepare CI for this

/unhold


basic example question / issue - 0 ios apps 0 android apps

I am trying to get the basic example working:
In the server console I get:
GCM configured

I call a server side method to do the push:
 sendNotification: (beer) ->
    if Roles.userIsInRole(Meteor.user(), ["editor", "admin"])
        title = beer.name + ' is now on tap.'
        Push.send
          from: "Tin Whiskers Brewing"
          title: title
          text: "We've got one waiting for you."
          # badge: 12
          query: {}

and then in the console I get:
Sent message "PushTest Beer is now on tap." to 0 ios apps 0 android apps

My config.push.json has what I belive to be the required fields:
{
  "apn": {
    "passphrase": "XXXXXXXX",
    "key": "prodAPNkey.pem",
    "cert": "prodAPNCert.pem"
  },
  "gcm": {
    "apiKey": "XXXXXXXXXXXXXXXXX",
    "projectNumber": "32933758074"
  },
  "production": true,
  "sound": true,
  "alert": true,
  "vibrate": true
}

Do I have to call something from the client to "register" device with the server or why might pushing to 0 devices be symptomatic of? There are a number of people with the app downloaded including myself.
Thanks for any help in advance!

I think in your query, you need to include a userID. Or, if you want to send multiple, you can instead use
tokens: array of appId's or tokens

@adam-hanna you are probably correct. Looking at it again I think maybe sending with
query: {}

might be valid and send to all users (if I was using accounts and userIds). I am hoping not to make users have to sign-in to get push notifications since they are just simple updates.
So then as you mention tokens might be the way to go. I am not sure I understand what the correct way to go about that is. Looking at the issue you filed it looks like you use Push.addListener on the client and server to set/update a token by inserting/updating the user profile. Would I just then make a collection to store all registered tokens in or is there a better way?

The user will have to sign in at least once in order to generate a token. Tokens are generated by apple and google. It's how they know who to send push notifications to. You should definitely store these somewhere. I store them in my user document, but the raix:push package also has a collection that is used for storage as well.

While I think adding accounts might fix the issue I don't think having accounts is supposed to be absolutely necessary to do push notifications. If you provide a blank query then as far as I can tell its just supposed to match all tokens stored in appCollection.
I'm a terrible programmer so forgive me if none of this makes sense but my reading of the code makes me believe those tokens should still be pushed into appCollection regardless of the use of the accounts base package.
I think that the problem may lie in the fact that the client side Push.Configure is the only thing that calls initPushUpdates(options.appName) which in turn calls [reportTokenToServer ] https://github.com/raix/push/blob/master/lib/client/client.js#L77). So if I don't do Push.Configure on the client side the token never get reported to the server.
Maybe this could have something to do with the funkyness you experienced with push.config.json in your issue?
@raix does what I say above actually make any sense?

I havent read it all but you can pin clients on Push.id() instead of user id - you can also just add metadata and query that. Its pretty flexible, unfortunately I havent time for support/documentation at the moment - feel free to pr wiki and readmes

Tracking this in the Doc team issue, closing this


Model Details about KnowEvolveANHP

Hi Team,
Thank you so much for sharing this amazing framework for event prediction!
When I am trying to go through your code, I see you are using the class "KnowEvolveANHP" to train the base event sequence model. From your paper, I saw you mentioned both KE and ANHP are state-of-the-art event sequence models. So I wish to understand if KnowEvolveANHP is a combination of these two models, or what the relationship is between the implementation of KnowEvolveANHP and these SOTA event sequence models.
Thanks a lot for your time and consideration!

Hi,
Yes, KnowEvolveANHP is a combination of the two models, which simply refers to add attention structure to the original KnowEvolve model.

Thanks a lot, Team. This helps a lot!


Multiple Pipelines causing failures to each other

We have encountered an issue with our deployment pipelines, specifically in the frontend stage of the first pipeline and the deploy action of the second pipeline. The second pipeline fails during the deploy action with the following error in the deployment account:
The following resource(s) failed to create: [ElasticSearchProxyHandlerDBDE7574, LambdaGraphQL1131F2C3, AWSWorkerAA1523CA].
As a result, this failure causes the first pipeline to fail in the frontend stage during the deploy frontend action. Both the pipelines lie in the same region rather they deploy to different regions in the deployment account. Following is the error log from codebuild in 2nd pipeline.
[Container] 2024/02/09 07:46:40.796140 Running command aws s3 sync build/ s3://$bucket --profile buildprofile
Traceback (most recent call last):
...
ImportError: cannot import name 'is_s3express_bucket' from 'botocore.utils' (/root/.pyenv/versions/3.9.17/lib/python3.9/site-packages/botocore/utils.py)
...
[Container] 2024/02/09 07:46:41.204028 Command did not exit successfully aws s3 sync build/ s3://$bucket --profile buildprofile exit status 1
[Container] 2024/02/09 07:46:41.208841 Phase complete: BUILD State: FAILED
[Container] 2024/02/09 07:46:41.208865 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: aws s3 sync build/ s3://$bucket --profile buildprofile. Reason: exit status 1
ERROR: Error while executing command: aws s3 sync build/ s3://$bucket --profile buildprofile. Reason: exit status 1
How to Reproduce

Deploy codepipeline_1 handling the default environment. Wait for it to complete.
Deploy codepipeline_2 handling another environment in the same region.
Observe the failure during the deploy action of codepipeline_2.
On triggering the 1st pipeline, observe the subsequent failure in the frontend stage of codepipeline_1.

Expected behavior
Both pipelines (codepipeline_1 and codepipeline_2) should run successfully without errors, completing their respective stages and actions.
Your project
No response
Screenshots
No response
OS
MacOS
Python version
3.10
AWS data.all version
2.0.0
Additional context
No response

As of today, similar pipeline in another AWS account failed at front-end stage.
[Container] 2024/02/09 07:46:40.796140 Running command aws s3 sync build/ s3://$bucket --profile buildprofile
Traceback (most recent call last):
...
ImportError: cannot import name 'is_s3express_bucket' from 'botocore.utils' (/root/.pyenv/versions/3.9.17/lib/python3.9/site-packages/botocore/utils.py)
...
[Container] 2024/02/09 07:46:41.204028 Command did not exit successfully aws s3 sync build/ s3://$bucket --profile buildprofile exit status 1
[Container] 2024/02/09 07:46:41.208841 Phase complete: BUILD State: FAILED
[Container] 2024/02/09 07:46:41.208865 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: aws s3 sync build/ s3://$bucket --profile buildprofile. Reason: exit status 1
ERROR: Error while executing command: aws s3 sync build/ s3://$bucket --profile buildprofile. Reason: exit status 1

Hi @anandsumit2000 thanks for the detailed summary. I think the issues have different sources.

first pipeline that fails in frontend stage: the issue is the one described in #1051 related to boto3 and botocore mismatches
second pipeline failure in deploy stage: it fails in CloudFormation, do you have the logs in CloudFormation of the failed resources (ElasticSearchProxyHandlerDBDE7574 ....)?

Hi @anandsumit2000 are you still facing this issue?

Closing this due to inactivity and not able to reproduce, feel free to reopen if you are still facing the issue and have any questions or need more assistance.


Kernel isn't configured for semaphores

I tried running my toy program which uses semaphores and it gave back an invalid argument error which is unusual since my Ubuntu VM runs fine. When running ipcs, Bash states:
Kernel not configured for shared memory
Kernel not configured for semaphores
Kernel not configured for message queues
I'm guessing this part of the Bash on Windows system is incomplete?

@alandao - Your understanding is correct. Currently, support for these features is very limited to none. We will be tracking\prioritizing which features to light up next by looking at the feedback provided at the wpdev portal. So, please do provide your feedback there as well:
https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo

#16 is about the same problem.

System V shared memory and semaphore support is making its way to insider builds. Closing this out as this issue has bene open for a very long time.
root@BENHILL-X1:/mnt/c/Users/benhill# ipcs

------ Message Queues --------
key        msqid      owner      perms      used-bytes   messages

------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status

------ Semaphore Arrays --------
key        semid      owner      perms      nsems


bug fix regexp function fallback to re2 failed

Proposed changes
mysql [test_query_qa]>select k7 from baseall where (k7 regexp '[0]^[0-9]+.{0,1}[0-9]+$') = 1;
ERROR 1105 (HY000): errCode = 2, detailMessage = (<IP_ADDRESS>)[CANCELLED][CANCELLED]UDF ERROR: hs_compile regex pattern error

before this sql exectue failed, as the hyperscan  report error: Embedded start anchors not supported.
But it's should be fallback to re2, when hyperscan failed, and this sql should be running normal.
mysql [test_query_qa]>select k7 from baseall where (k7 regexp '[0]^[0-9]+.{0,1}[0-9]+$') = 1;
Empty set (0.05 sec)

Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


grain: update assembly and make accumulate inlinable

Signed-off-by: Eric Lagergren<EMAIL_ADDRESS>

cc: @greatroar

On my x86_64 MBP I get ~124 MB/s using assembly, ~95 MB/s using Go.
On my M1 MacBook Air I get ~150 MB/s using Go (and 102 MB/s using assembly through Rosetta).

Auth-8               109MB/s ± 1%
AuthGeneric-8       96.7MB/s ± 1%

The question is whether it's the assembly doing the magic now, though, or just the unrolling of the loop.

It's very likely loop unrolling. The instructions are nearly the same. The only additional improvement I can immediately think of is reordering the instructions to eliminate false dependencies or stalls or whatever.
Unrolling the Go code should make it equally quick, I think. Could generate it with a small program.


Extra keys not allowed error when the notification pressed

Received invalid webhook payload: extra keys not allowed @ data['os_name']. Got 'Android'

Hmmm... They removed that key from API. Strange...

What is your Home Assistant version?

The latest stable (0.97.2)

I have the same version and can't reproduce it. Could you please describe the exact steps please. The is on a background when notification arrives?

I send a notification through services including title and message. When I tap the notification this error occurs in HA. It happens if the client runs in the foreground or background.

It seems that it happens even if the lifecycle of the app resumes

Ok, I see. Thanks


correct the directory string on windows

Bit confused by line 415.  Those should be doing equivalent things in python no?  os.pathsep = ';' on windows and ':' else.


Task: Invocation of interface 'Configure' of role 'Cloud\Fabric\SQL' failed. Step 60.62.101

Any Suggestions here.  Trying to deploy ASDK 2005.  All of the roles seem to be up.  Not sure what direction I should go.
`2020-11-04 14:22:55 Verbose  Step:Skipping task 'Deployment-Phase3-DeployADFS' of role 'Cloud' because it was skipped or run successfully previously.
2020-11-04 14:22:55 Verbose  5> Creating action host for action Deployment-Phase3-DeploySQL.
2020-11-04 14:22:55 Verbose  5> Found the role 'Cloud' in the current configuration.
2020-11-04 14:22:55 Verbose  5> Using the existing expanded action definition for action Deployment-Phase3-DeploySQL.
2020-11-04 14:22:55 Verbose  5> Creating action host for action Deployment-Phase3-DeploySQL.
2020-11-04 14:22:55 Verbose  5> Action host for action Deployment-Phase3-DeploySQL has been created.
2020-11-04 14:22:55 Verbose  5> Update the actionTask definition with the new nested actionHost definition for Cloud - Deployment-Phase3-DeploySQL.
2020-11-04 14:22:55 Verbose  5> Task: Running action type 'Deployment-Phase3-DeploySQL' of role 'Cloud'.
2020-11-04 14:22:55 Verbose  5> Action: Running action Deployment-Phase3-DeploySQL.
2020-11-04 14:22:55 Verbose  5> Action: Running action plan 'Deployment-Phase3-DeploySQL'.
2020-11-04 14:22:55 Verbose  5> The following steps are currently ready: 60.62.101.
2020-11-04 14:22:55 Verbose  5> Processing step: 60.62.101.
2020-11-04 14:22:55 Verbose  5> Executing step: 60.62.101.
2020-11-04 14:22:55 Verbose  5> Checking if any of the in progress steps are complete. The following steps are currently in progress: '60.62.101'.
2020-11-04 14:22:55 Verbose  5> The following steps are currently ready: .
2020-11-04 14:22:55 Verbose  5> No steps are ready for execution. Waiting for any of the currently-running steps to complete. The following steps are currently in progress: '60.62.101'.
2020-11-04 14:22:55 Verbose  5> Step: Running step 60.62.101 - (FBI) Setup SQL VMs
2020-11-04 14:22:55 Verbose  5> Task: Running interface 'Configure' of role 'Cloud\Fabric\SQL'. Attempt #1 of 3
2020-11-04 14:22:55 Verbose  5> Loading CustomerConfiguration for interface 'Configure' of role 'Cloud\Fabric\SQL'.
2020-11-04 14:22:55 Verbose  5> Task: Interface 'Configure' is getting created.
2020-11-04 14:22:55 Verbose  5> Interface: Path to module: C:\CloudDeployment\Classes\SQL\SQL.psm1
2020-11-04 14:22:55 Verbose  5> Interface: Running interface Configure (Classes\SQL\SQL.psm1, SQL:Configure)
2020-11-04 14:22:55 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Entering throttling instance, enqueue for waiting. Priority '0', Weight '10'.
2020-11-04 14:22:55 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Validating availability to start task.
2020-11-04 14:22:55 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Task available to start.
2020-11-04 14:22:55 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Parallel task count increased by '10' to '10'.
2020-11-04 14:22:55 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Throttling instance dequeued from waiting. Priority '0', Weight '10'.
2020-11-04 14:22:55 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] TotalVirtualMemoryMB: [131071.55078125], FreeVirtualMemoryMB: [58925.70703125], FreePhysicalMemoryMB: [59237.52734375].
2020-11-04 14:23:08 Warning  5> [SQL:Configure] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:23:10 Warning  5> [SQL:Configure] The names of some imported commands from the module 'NetworkHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:23:10 Warning  5> [SQL:Configure] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:23:15 Warning  5> [SQL:Configure] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:23:16 Warning  5> [SQL:Configure] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:23:16 Warning  5> [SQL:Configure] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:23:17 Warning  5> [SQL:Configure] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:23:22 Warning  5> [SQL:Configure] The names of some imported commands from the module 'NetworkHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:23:22 Warning  5> [SQL:Configure] The names of some imported commands from the module 'SQL' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:23:23 Warning  5> [SQL:Configure] The names of some imported commands from the module 'SQL' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:23:23 Verbose  5> [SQL:Configure] Execution start of New-Sql.
2020-11-04 14:23:30 Verbose  5> [SQL:Configure] Prepare nodes for clustering: 'AzS-Sql01.azurestack.local'
2020-11-04 14:23:33 Verbose  5> [SQL:Configure] Enabling client/diagnostic event log on AzS-Sql01.azurestack.local
2020-11-04 14:23:40 Verbose  5> [SQL:Configure] Clean up the AD computer object AzS-SqlCl and its DNS record
2020-11-04 14:23:40 Verbose  5> [SQL:Configure] Removing DNS resource record for name 'AzS-SqlCl' with IP 'True' under zone name 'azurestack.local' on the domain controller 'AzS-DC01'.
2020-11-04 14:23:45 Verbose  5> [SQL:Configure] Record for 'True' (A) not present.
2020-11-04 14:23:45 Verbose  5> [SQL:Configure] Removing DNS resource record for name 'AzS-SqlCl' with IP 'True' under zone name 'azurestack.local' on the domain controller 'AzS-DC01'.
2020-11-04 14:23:45 Verbose  5> [SQL:Configure] Record for 'True' (AAAA) not present.
2020-11-04 14:23:45 Verbose  5> [SQL:Configure] Creating the cluster 'AzS-SqlCl'.
2020-11-04 14:24:08 Verbose  5> [SQL:Configure] Collecting client/diagnostic event log on AzS-Sql01.azurestack.local
2020-11-04 14:24:32 Verbose  5> [SQL:Configure] ECE PowerShellHost Script End
2020-11-04 14:24:32 Verbose  5> Interface: PowerShell job terminal state is Failed for interface 'Configure'.
2020-11-04 14:24:33 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Exiting throttling instance. Priority '0', Weight '10'.
2020-11-04 14:24:33 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Parallel task count decreased by '10' to '0'.
2020-11-04 14:24:33 Warning  5> Task: Invocation of interface 'Configure' of role 'Cloud\Fabric\SQL' failed:
Type 'Configure' of Role 'SQL' raised an exception:
There was an error adding node 'AzS-Sql01.azurestack.local' to the cluster
The computer 'AzS-Sql01.azurestack.local' is joined to a cluster.
Command          Arguments

Add-GuestCluster {Parameters=CloudEngine.Configurations.EceInterfaceParameters, RunAsUserID=Fabric}
New-Sql          {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, Verbose=True}
{}
    {CloudEngine.Configurations.EceInterfaceParameters}
    {C:\CloudDeployment\CloudDeployment.psd1, CloudEngine.Configurations.EceInterfaceParameters, 1111131...
at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 63
at Add-GuestCluster, C:\CloudDeployment\Roles\Common\RoleHelpers.psm1: line 390
at New-Sql, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 55
at Configure, C:\CloudDeployment\Classes\SQL\SQL.psm1: line 19
at , : line 56
at , : line 54
2020-11-04 14:24:33 Warning  5> Task: Retrying interface 'Configure' of role 'Cloud\Fabric\SQL'...
2020-11-04 14:24:33 Verbose  5> Task: Running interface 'Configure' of role 'Cloud\Fabric\SQL'. Attempt #2 of 3
2020-11-04 14:24:33 Verbose  5> Wait for 60 seconds before attempting retry.
2020-11-04 14:25:33 Verbose  5> Loading CustomerConfiguration for interface 'Configure' of role 'Cloud\Fabric\SQL'.
2020-11-04 14:25:33 Verbose  5> Task: Interface 'Configure' is getting created.
2020-11-04 14:25:33 Verbose  5> Interface: Path to module: C:\CloudDeployment\Classes\SQL\SQL.psm1
2020-11-04 14:25:33 Verbose  5> Interface: Running interface Configure (Classes\SQL\SQL.psm1, SQL:Configure)
2020-11-04 14:25:33 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Entering throttling instance, enqueue for waiting. Priority '0', Weight '10'.
2020-11-04 14:25:33 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Validating availability to start task.
2020-11-04 14:25:33 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Task available to start.
2020-11-04 14:25:33 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Parallel task count increased by '10' to '10'.
2020-11-04 14:25:33 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Throttling instance dequeued from waiting. Priority '0', Weight '10'.
2020-11-04 14:25:33 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] TotalVirtualMemoryMB: [131071.55078125], FreeVirtualMemoryMB: [58910.1015625], FreePhysicalMemoryMB: [59238.4453125].
2020-11-04 14:25:40 Warning  5> [SQL:Configure] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:25:41 Warning  5> [SQL:Configure] The names of some imported commands from the module 'NetworkHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:25:41 Warning  5> [SQL:Configure] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:25:47 Warning  5> [SQL:Configure] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:25:48 Warning  5> [SQL:Configure] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:25:48 Warning  5> [SQL:Configure] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:25:49 Warning  5> [SQL:Configure] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:25:53 Warning  5> [SQL:Configure] The names of some imported commands from the module 'NetworkHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:25:53 Warning  5> [SQL:Configure] The names of some imported commands from the module 'SQL' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:25:54 Warning  5> [SQL:Configure] The names of some imported commands from the module 'SQL' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2020-11-04 14:25:54 Verbose  5> [SQL:Configure] Execution start of New-Sql.
2020-11-04 14:25:59 Verbose  5> [SQL:Configure] Prepare nodes for clustering: 'AzS-Sql01.azurestack.local'
2020-11-04 14:26:02 Verbose  5> [SQL:Configure] Enabling client/diagnostic event log on AzS-Sql01.azurestack.local
2020-11-04 14:26:04 Verbose  5> [SQL:Configure] Clean up the AD computer object AzS-SqlCl and its DNS record
2020-11-04 14:26:04 Verbose  5> [SQL:Configure] Removing DNS resource record for name 'AzS-SqlCl' with IP 'True' under zone name 'azurestack.local' on the domain controller 'AzS-DC01'.
2020-11-04 14:26:08 Verbose  5> [SQL:Configure] Record for 'True' (A) not present.
2020-11-04 14:26:08 Verbose  5> [SQL:Configure] Removing DNS resource record for name 'AzS-SqlCl' with IP 'True' under zone name 'azurestack.local' on the domain controller 'AzS-DC01'.
2020-11-04 14:26:08 Verbose  5> [SQL:Configure] Record for 'True' (AAAA) not present.
2020-11-04 14:26:08 Verbose  5> [SQL:Configure] Creating the cluster 'AzS-SqlCl'.
2020-11-04 14:26:19 Verbose  5> [SQL:Configure] Collecting client/diagnostic event log on AzS-Sql01.azurestack.local
2020-11-04 14:26:39 Verbose  5> [SQL:Configure] ECE PowerShellHost Script End
2020-11-04 14:26:39 Verbose  5> Interface: PowerShell job terminal state is Failed for interface 'Configure'.
2020-11-04 14:26:39 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Exiting throttling instance. Priority '0', Weight '10'.
2020-11-04 14:26:39 Verbose  5> [PSTask Concurrency] [113>SQL:Configure] Parallel task count decreased by '10' to '0'.
2020-11-04 14:26:39 Warning  5> Task: Invocation of interface 'Configure' of role 'Cloud\Fabric\SQL' failed:
Type 'Configure' of Role 'SQL' raised an exception:
There was an error adding node 'AzS-Sql01.azurestack.local' to the cluster
The computer 'AzS-Sql01.azurestack.local' is joined to a cluster.
Command          Arguments

Add-GuestCluster {Parameters=CloudEngine.Configurations.EceInterfaceParameters, RunAsUserID=Fabric}
New-Sql          {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, Verbose=True}
{}
    {CloudEngine.Configurations.EceInterfaceParameters}
    {C:\CloudDeployment\CloudDeployment.psd1, CloudEngine.Configurations.EceInterfaceParameters, 1211131...
at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 63
at Add-GuestCluster, C:\CloudDeployment\Roles\Common\RoleHelpers.psm1: line 390
at New-Sql, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 55
at Configure, C:\CloudDeployment\Classes\SQL\SQL.psm1: line 19
at , : line 56
at , : line 54`

Update after debugging all day yesterday.

Yesterday we found that the ASDK baseline installer script did not add the SQL cluster name DNS A record and IP to the DNS.  It also did not add the SQL cluster name computer object to the AD.  The script was looking for both of those and will fail if they are not there.  Once we added them, then the rerun of the script progressed.
Last night the script ran from 5pm to around 10p and is now in a hung state.  It did not exit and return to c prompt but seems to be  hung.  It is having issue with the storage accounts. It seems to be hung for around 12 hours now.
a.	The failover cluster manager events shows a recurring error.
Cluster resource "Virtual Machine AzS-ACS01" of type "Virual Machine" in clustered role failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on
the this node or move the group to another node and then restart it.
Check the resouce and group state using failover cluster manager or the Get-ClusterResource Windows PowerShell cmdlet.
b.	The last stage on the PS console shows the below.  The create logs statement C:\MASLogs\StorageAccounts_CreateStorageAccounts_20201105-022653.log on the server  AzS-Xrp01.azurestack.local is 0 bytes empty.  So not able to find anything.  I am not sure what to do at this stage.

STARTING: Task Cloud\Fabric\StorageAccounts - Configure
VERBOSE: 1> Interface: Path to module: C:\CloudDeployment\Classes\StorageAccounts\StorageAccounts.psm1 - 11/5/2020 2:25:53 AM
VERBOSE: 1> Interface: Running interface Configure (Classes\StorageAccounts\StorageAccounts.psm1, StorageAccounts:Configure) - 11/5/2020 2:25:53 AM
VERBOSE: 1> [PSTask Concurrency] [63>StorageAccounts:Configure] Entering throttling instance, enqueue for waiting. Priority '0', Weight '10'. - 11/5/2020 2:25:53 AM
VERBOSE: 1> [PSTask Concurrency] [63>StorageAccounts:Configure] Validating availability to start task. - 11/5/2020 2:25:53 AM
VERBOSE: 1> [PSTask Concurrency] [63>StorageAccounts:Configure] Task available to start. - 11/5/2020 2:25:53 AM
VERBOSE: 1> [PSTask Concurrency] [63>StorageAccounts:Configure] Parallel task count increased by '10' to '10'. - 11/5/2020 2:25:53 AM
VERBOSE: 1> [PSTask Concurrency] [63>StorageAccounts:Configure] Throttling instance dequeued from waiting. Priority '0', Weight '10'. - 11/5/2020 2:25:53 AM
VERBOSE: 1> [PSTask Concurrency] [63>StorageAccounts:Configure] TotalVirtualMemoryMB: [131071.55078125], FreeVirtualMemoryMB: [59127.4296875],FreePhysicalMemoryMB: [59655.9296875]. - 11/5/2020 2:25:53 AM
WARNING: 1> [StorageAccounts:Configure] The names of some imported commands from the module 'StorageAccounts' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the
Verbose parameter. For a list of approved verbs, type Get-Verb. - 11/5/2020 2:26:21 AM
VERBOSE: 1> [StorageAccounts:Configure] Initializing remote powershell session on AzS-Xrp01.azurestack.local with common functions. - 11/5/2020 2:26:51 AM
VERBOSE: 1> [StorageAccounts:Configure] Transcript started, output file is C:\MASLogs\StorageAccounts_CreateStorageAccounts_20201105-022653.log - 11/5/2020 2:26:54 AM
VERBOSE: 1> [StorageAccounts:Configure] Registering the admin subscriptions [abaf2eb8-71b9-4d50-9c30-0c32668f6703 6d8d45aa-3e27-4914-96bb-23706ad8a66b] with the 'Microsoft.Storage' namespace - 11/5/2020 2:26:54 AM

The installer that seemed to hang finally failed after 17 hours at step 60.140.148.
We restarted/reset the AzS-XRP01 Role Node (Infrastructure management controller for Microsoft Azure Stack, including the Compute, Network, and Storage resource providers). And started the Installer again with the -rerun flag.  It is now progressing again, and has moved passed the 60.140.148 step.  Will see if it finishes.
error_step_60-140-148.txt

has it completed this time?


Upgrade to Diffusers 0.17.0

Diffusers is due for an update soon. #3512
Opening up a PR now with the required changes for when the new version is live.
I've tested it out on Windows and nothing has broken from what I could tell. I'd like someone to run some tests on Linux / Mac just to make sure. Refer to the PR above on how to test it or install the release branch.
pip install diffusers[torch]==0.17.0

Feel free to push any other changes to this PR you see fit.

@lstein @GreggHelt2 @hipsterusername Diffusers 0.17.0 is out and I think we can safely upgrade.

@lstein Should we merge this in?


[e2e]: generic schedule main multi-uses slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7706119371
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.multi-uses.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.multi-uses.slsa3.yml
Trigger: schedule
Branch: main
Date: Tue Jan 30 04:08:17 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7721041937
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.multi-uses.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.multi-uses.slsa3.yml
Trigger: schedule
Branch: main
Date: Wed Jan 31 04:08:25 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7736101178
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.multi-uses.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.multi-uses.slsa3.yml
Trigger: schedule
Branch: main
Date: Thu Feb  1 04:46:41 UTC 2024
Tests are passing now. Closing this issue.