Failed to activate the markdown-document package

[Enter steps to reproduce below:]

...
...

Atom Version: 1.9.0
System: Linux Mint
Thrown From: markdown-document package, v0.2.0
Stack Trace
Failed to activate the markdown-document package
At Cannot read property 'onDidStopChanging' of undefined

TypeError: Cannot read property 'onDidStopChanging' of undefined
    at new MarkdownDocumentView (/home/jan/.atom/packages/markdown-document/lib/markdown-document-view.coffee:250:13)
    at Object.module.exports.MarkdownDocument.activate (/home/jan/.atom/packages/markdown-document/lib/markdown-document.coffee:21:33)
    at Package.module.exports.Package.activateNow (/usr/share/atom/resources/app.asar/src/package.js:183:20)
    at /usr/share/atom/resources/app.asar/src/package.js:795:25
    at Function.module.exports.Emitter.simpleDispatch (/usr/share/atom/resources/app.asar/node_modules/event-kit/lib/emitter.js:25:14)
    at Emitter.module.exports.Emitter.emit (/usr/share/atom/resources/app.asar/node_modules/event-kit/lib/emitter.js:125:28)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app.asar/src/command-registry.js:241:20)
    at /usr/share/atom/resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:580:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:388:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/usr/share/atom/resources/app.asar/src/window-event-handler.js:98:36)
    at HTMLDocument.<anonymous> (/usr/share/atom/resources/app.asar/src/window-event-handler.js:3:61)

Commands
     -0:00.0 markdown-document:toggle (div.markdown-preview.native-key-bindings)

Config
{}

Installed Packages
# User
markdown-document, v0.2.0 (inactive)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.51.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.43.0 (inactive)
base16-tomorrow-dark-theme, v1.1.0 (inactive)
base16-tomorrow-light-theme, v1.1.1 (inactive)
one-dark-ui, v1.3.2 (active)
one-light-ui, v1.3.2 (inactive)
one-dark-syntax, v1.2.0 (active)
one-light-syntax, v1.2.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.5.2 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.1 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.0 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.0 (active)
bookmarks, v0.41.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.38.1 (active)
fuzzy-finder, v1.3.0 (active)
git-diff, v1.1.0 (active)
find-and-replace, v0.198.0 (inactive)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.1 (active)
image-view, v0.58.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v0.53.1 (active)
notifications, v0.64.1 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.238.0 (active)
snippets, v1.0.2 (active)
spell-check, v0.67.1 (active)
status-bar, v1.4.0 (active)
styleguide, v0.46.0 (active)
symbols-view, v0.113.0 (inactive)
tabs, v0.98.0 (active)
timecop, v0.33.1 (active)
tree-view, v0.208.0 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.34.0 (active)
whitespace, v0.32.2 (active)
wrap-guide, v0.38.1 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.0 (active)
language-csharp, v0.12.1 (active)
language-css, v0.36.2 (active)
language-gfm, v0.86.0 (active)
language-git, v0.13.0 (active)
language-go, v0.42.0 (active)
language-html, v0.44.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.22.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.0 (active)
language-less, v0.29.3 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.0 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.68.5 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.52.0 (active)
language-shellscript, v0.22.3 (active)
language-source, v0.9.0 (active)
language-sql, v0.21.1 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.8 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

I, too am getting this sort of message. I'm running the newest Atom with minimal packages.

There may be an issue with markdown-document and atom 1.9 and greater. I'm currently slammed and will be for the next three weeks. If you wish to try fixing this yourself, I'll be happy to grant you the necessary access. I apologize for the incovenience. KC

any progress on this? I sadly never did any atom package dev, maybe I can have a look nevertheless.

Can anyone post another stack trace? I'm trying to reproduce on Atom 1.12.7 (Ubuntu 14.04 LTS) with no luck.


Using a font with an unsupported font weight leads to flaky behavior

A Googler found this issue when debugging flaky tests.
Steps to Reproduce
The test includes font weights of 500 and 700 for Roboto.
When the test code uses font weight 600, rendering becomes flaky as sometimes 500 is chosen and other times 700.
Expected Behavior
Either:

Flutter throws an error or a warning to indicate an unsupported font;

Or:
2) Flutter chooses a nearest font weight in a deterministic way.

fandeng@marshmallow:~$ flutter doctor -v
[✓] Flutter (Channel beta, v1.4.9-hotfix.1, on Linux, locale en_US.UTF-8)
• Flutter version 1.4.9-hotfix.1 at [reducted]
• Framework revision 88fa7ea403 (6 days ago), 2019-04-11 14:01:46 -0700
• Engine revision 4737fc5cd8
• Dart version 2.2.1 (build 2.2.1-dev.4.0 None)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at [reducted]
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-stable, build-tools 28.0.3
• Java binary at: /opt/android-studio-with-blaze-3.3/jre/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
• All Android licenses accepted.
[✓] Android Studio (version 3.3)
• Android Studio at /opt/android-studio-with-blaze-3.3
• Flutter plugin version 32.0.1
• Dart plugin version 182.5215
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
[✓] IntelliJ IDEA Community Edition (version 2018.3)
• IntelliJ at /opt/intellij-ce-2018.3
• Flutter plugin version 34.0.2
• Dart plugin version 183.5912.23
[✓] Connected device (2 available)
• Nexus 5X      • [reducted] • android-arm64 • Android 8.1.0 (API 27)
• Pixel Android • emulator-5554    • android-x86   • Android 8.0.0 (API 26) (emulator)
• No issues found!

This is especially problematic when using TextStyle.lerp between styles with different font sizes.


Ability to host files

From __main__.py

Ill try implement this tonight

I have an idea. we can use message.attachements to get the URL to the attached file, if that is what you want and then request.get().raw or something those URLs and store it in like userFiles/userName.
I can help out with the downloading part if you want so @Skippy404. Probably should make this a module though.


Train own dataset

Hey,
thanks for this great work and the release of the code.
I would like to train on my own data, but I can't find a train.py file. So I would like to ask, how can I train on my own data?

Hi,
for a minimal example of training code, please refer to this issue.
Best,
D

Hey,
thank you for your quick reply. I will take a look there.
best regards,
lte91


Build failed.

Try to build operator local follow the document.
operator-sdk version
operator-sdk version: "v1.23.0", commit: "1eaeb5adb56be05fe8cc6dd70517e441696846a4", kubernetes version: "1.24.2", go version: "go1.18.5", GOOS: "linux", GOARCH: "amd64"

go version
go version go1.17 linux/amd64
try to build, got the error, Output:
make build manifests
/go-workspace/opensearch-k8s-operator/opensearch-operator/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..."
 output:crd:artifacts:config=config/crd/bases
Error: unable to parse option "crd:trivialVersions=true,preserveUnknownFields=false": [unknown argument "trivialVersions" (at <input>:1:16) extra arguments provided: "true,preserveUnknownFields=false" (at <input>:1:17)]
Usage:
  controller-gen [flags]
...

What's the problem?

Hi @chenyg0911. Can you please check the version of controller-gen being used? bin/controller-gen --version should show Version: v0.4.1.
And fyi: This project does not use operator-sdk.

thanks @swoehrl-mw . Build with controller-gen v0.4.1, it's OK!


examples-generated contain terraform variables in the yaml that are not meaningfully consumable

What happened?

Upjet generates examples in the examples-generated folder to make it easy for users to create managed resources. However, the examples can include Terraform variables that are not meaningfully consumable by Crossplane and result in the generated examples not to work.
Some examples of included variables are as follows:
examples-generated/apm/retentionfilterorder.yaml:    - ${datadog_apm_retention_filter.foo.id}
examples-generated/authn/mapping.yaml:    role: ${data.datadog_role.ro_role.id}
examples-generated/dashboard/list.yaml:    - dashId: ${datadog_dashboard.time.id}
examples-generated/dashboard/list.yaml:    - dashId: ${datadog_dashboard.screen.id}
examples-generated/datadog/role.yaml:    - id: ${data.datadog_permissions.bar.permissions.monitors_downtime}
examples-generated/datadog/role.yaml:    - id: ${data.datadog_permissions.bar.permissions.monitors_write}
examples-generated/datadog/serviceaccount.yaml:    - ${data.datadog_role.ro_role.id}
examples-generated/datadog/user.yaml:    - ${data.datadog_role.ro_role.id}
examples-generated/datadog/slocorrection.yaml:    sloId: ${datadog_service_level_objective.example_slo.id}
examples-generated/integration/gcpsts.yaml:    clientEmail: ${google_service_account.datadog_integration.email}
examples-generated/integration/confluentresource.yaml:    accountId: ${datadog_integration_confluent_account.foo.id}
examples-generated/integration/fastlyservice.yaml:    accountId: ${datadog_integration_fastly_account.foo.id}
examples-generated/logs/indexorder.yaml:    - ${datadog_logs_index.sample_index.id}
examples-generated/logs/pipelineorder.yaml:    - ${datadog_logs_custom_pipeline.sample_pipeline.id}
examples-generated/logs/pipelineorder.yaml:    - ${datadog_logs_integration_pipeline.python.id}
examples-generated/logs/archiveorder.yaml:    - ${datadog_logs_archive.sample_archive_1.id}
examples-generated/logs/archiveorder.yaml:    - ${datadog_logs_archive.sample_archive_2.id}
examples-generated/sensitivedatascanner/rule.yaml:    groupId: ${datadog_sensitive_data_scanner_group.mygroup.id}
examples-generated/team/membership.yaml:    teamId: ${datadog_team.foo.id}
examples-generated/team/membership.yaml:    userId: ${datadog_user.foo.id}
examples-generated/team/permissionsetting.yaml:    teamId: ${datadog_team.foo.id}
examples-generated/team/link.yaml:    teamId: ${datadog_team.foo.id}
examples-generated/webhook/webhook.yaml:    customHeaders: '${jsonencode({ "custom" : "header" })}'
examples-generated/webhook/webhook.yaml:    payload: '${jsonencode({ "custom" : "payload" })}'

How can we reproduce it?

This can be reproduced as follows:
- git clone git@github.com:upbound/provider-datadog.git
- git checkout bootstrap
- make submodules
- make clean; make gen-clean; make generate
- make e2e

Once a cluster is up and configured `kubectl apply -f examples-generated/team/membership.yaml'. The membership resource status message will include the following due to the variables:
observe failed: cannot run refresh: refresh failed: Reference to undeclared resource: A managed resource "datadog_team" "foo" has not been declared in the root module. Reference to undeclared resource: A managed resource "datadog_user" "foo" has not been declared in the root module.

This is very confusing to new users and generates a fair number of questions in Slack.  Generated examples should be usable "as is" and not require translation of terraform-specific formats and data references.


Guide versioning note on ES-latest tracking

Because Duktape tracks the latest Ecmascript specification, semantics corrections to match newer specification version can also be made in minor releases. The semantic changes are usually relatively small; if they weren't, they'd also be an issue for web Javascript.

@fatcerberus How would you find the changed description re: versioning guarantees?
What I'm trying to do is explain up front that semantic fixes are not under strict versioning guarantees as far as the minor version is concerned, but patch versions won't change semantics unless that's really necessary to fix a bug.
Hopefully a compromise like this would allow minor releases to still make sense. Because if not, almost every release would be major :-o

That sounds good. It's about what I'd expect for a scripting engine using semantic versioning.  Perhaps a bit inconvenient for those using Duktape in their backend (rather than the frontend, like minisphere), but like you said if the changes were a significant compatibility issue they'd also be an issue for the web, so there shouldn't be a problem in practice.
I do like the strict guarantees for the Duktape API by the way - it ensures I can upgrade to a new minor release and get new features without having to change a bunch of call sites.  I personally don't mind Ecmascript changes as much because it's easier to change a JS script to align compared to C code (there's no compile step for the former).

Ok, good to hear. From a practical viewpoint I think the best way to proceed is that:

If a later specification adjusts semantics in a way that's unlikely to impact call sites, then the change can be made in a minor version. For example, the Object constructor coercion changes are unlikely to break code because they only affect cases that would have thrown errors in the past. While it's possible to rely on that, it's not very likely.
If a later specification adjusts semantics in a way that is likely to impact call sites, e.g. changes success path behavior or affects a known idiom, it's probably preferable to make the change in a major version.

This is far from clear cut or ideal, but is pragmatic in the sense that minor version upgrades should be unlikely to break call sites, while major version upgrades don't have similar expectations.

Note that from what I've seen, Ecmascript itself sometimes specifies an error throw as a placeholder exactly so that implementing meaningful behavior later doesn't create a compatibility issue.  For example this note in ES7 for String.prototype.includes():

Throwing an exception if the first argument is a RegExp is specified in order to allow future editions to define extensions that allow such argument values.

Right, but it's still possible for code to depend on the error throw. One can rely on error throwing (on purpose or by accident) for validation for example.


Preserve top level comments on update of imports

Fixes #54

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


Connect with Google Sheet error

Hi when i try connect superset with Google Sheet i got this error
ERROR: Could not load database driver: gsheets
And the google sheet table in my superset shows an error like this
    Traceback (most recent call last):

File "/root/reqmon/lib/python3.8/site-packages/flask/app.py", line 2447, in wsgi_app
response = self.full_dispatch_request()
File "/root/reqmon/lib/python3.8/site-packages/flask/app.py", line 1952, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/root/reqmon/lib/python3.8/site-packages/flask/app.py", line 1821, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/root/reqmon/lib/python3.8/site-packages/flask/compat.py", line 39, in reraise
raise value
File "/root/reqmon/lib/python3.8/site-packages/flask/app.py", line 1950, in full_dispatch_request
rv = self.dispatch_request()
File "/root/reqmon/lib/python3.8/site-packages/flask/app.py", line 1936, in dispatch_request
return self.view_functionsrule.endpoint
File "/root/reqmon/lib/python3.8/site-packages/superset/utils/log.py", line 70, in wrapper
value = f(*args, **kwargs)
File "/root/reqmon/lib/python3.8/site-packages/flask_appbuilder/security/decorators.py", line 109, in wraps
return f(self, *args, **kwargs)
File "/root/reqmon/lib/python3.8/site-packages/superset/views/core.py", line 706, in explore
"datasource": datasource.data,
File "/root/reqmon/lib/python3.8/site-packages/superset/connectors/sqla/models.py", line 602, in data
data = super().data
File "/root/reqmon/lib/python3.8/site-packages/superset/connectors/base/models.py", line 266, in data
"select_star": self.select_star,
File "/root/reqmon/lib/python3.8/site-packages/superset/connectors/sqla/models.py", line 596, in select_star
return self.database.select_star(
File "/root/reqmon/lib/python3.8/site-packages/superset/models/core.py", line 435, in select_star
eng = self.get_sqla_engine(schema=schema, source=utils.QuerySource.SQL_LAB)
File "/root/reqmon/lib/python3.8/site-packages/superset/utils/core.py", line 165, in call
value = self.func(*args, **kwargs)
File "/root/reqmon/lib/python3.8/site-packages/superset/models/core.py", line 359, in get_sqla_engine
return create_engine(sqlalchemy_url, **params)
File "/root/reqmon/lib/python3.8/site-packages/sqlalchemy/engine/init.py", line 500, in create_engine
return strategy.create(*args, **kwargs)
File "/root/reqmon/lib/python3.8/site-packages/sqlalchemy/engine/strategies.py", line 61, in create
entrypoint = u._get_entrypoint()
File "/root/reqmon/lib/python3.8/site-packages/sqlalchemy/engine/url.py", line 172, in _get_entrypoint
cls = registry.load(name)
File "/root/reqmon/lib/python3.8/site-packages/sqlalchemy/util/langhelpers.py", line 267, in load
raise exc.NoSuchModuleError(
sqlalchemy.exc.NoSuchModuleError: Can't load plugin: sqlalchemy.dialects:gsheets
I use ubuntu 20 and python 3.8
Thanks Before

Hi,
Please make sure you have installed gsheetsdb>=0.1.9


wip: add daprd job metrics

Description
Adds job metrics to daprd metrics endpoint

success jobs count
failure jobs count
job latency

Issue reference
https://github.com/dapr/dapr/issues/8160

Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

@cicoyle , have added some basic integration tests as suggested. It was a good learning experience, Thank you !

@cicoyle have done the changes suggested, could you please take a look ?

@titanventura see the failing static check

its a proto linter update and if you run gofumpt -w <filename> that should fix the other issue

Thanks @cicoyle. Can you please add the hacktoberfest label to this PR or issue ?

Thanks @cicoyle. Can you please add the hacktoberfest label to this PR or issue ?

Hey @titanventura - thanks for making this happen! Was there a reason you were wanting the hacktoberfest label on? I believe that was from a prior year, not current.


Use Swift 5.9.1 and LLD 17.0.5 by default

These are the latest versions that we should use by default to get recent bug fixes included in produced Swift SDKs.

@swift-ci test


metallic atoms

Is possible to do calculations (Electrostatic potential) in proteins with metallic atoms? (Ni, Fe, etc)

Hi @Marr575,
Yes, it's possible. You'll have to parameterize them somehow (assign a charge and atomic radii), as I'm not sure is pdb2pqr will be able to do it by default. You can either run pdb2pqr with your own force field that contains information for metallic atoms, or add them by hand on the .pqr file.


Use upstream proto

Description
Let's remove private fork and bump to latest release.
Testing Performed
CI

This won't work as we depend on custom features

@misberner what features?

Oh, I see we are not on master but on -rox branch. Why we are using 1.2.2 then and not 1.3.2?


Catch empty field exceptions

Should probably sweep the app to catch places where there are fields being entered so it doesn't crash

We should look into implementing native Android form validation before resorting to patching over exceptions :)

Yeah, something like this would be great

Perhaps we can leverage setError with something like FluentValidation?


Cannot open image files (other file types work perfectly fine) from Windows to Android

Describe the bug
Whenever I want to send images from Windows to Android, the image won't open. It keeps throwing 'Could not open "[file location]". Has this file been moved, renamed or deleted?' . But other file types from Windows to Android (and vice versa) would work perfectly, and sending images from Android to Windows works too.
Doesn't matter if I change the Android app's file path ("Save to folder") or use the default one, it throws the same error with the same file path (/data/user/0/org.localsend.localsend_app/cache/[image file name]). But if I send other file types from Windows to Android (e.g pdf or C language), they would be saved in the file path I set.
To reproduce

Send image(s) from the Windows app (whether it's from manual, drag and drop, or the context menu's "Send to")
Select the Android device
On Android, tap "Open" or "Show in folder"
The error 'Could not open "/data/user/0/org.localsend.localsend_app/cache/[image file name]". Has this file been moved, renamed or deleted?' occurs.

Expected behavior
The image files should be openable or shown in folder.
Screenshots

Desktop (please complete the following information)

OS: Windows 11
Version: 24H2 (Release Preview OS Build 26100.2454)

Smartphone (please complete the following information)

Device: Xiaomi 12T
OS: Android
Version: 14 (HyperOS <IP_ADDRESS>.ULQIDXM)

Additional context
No response

Yeah, it should open the gallery because "Save media to photos" is likely enabled.

Same here. Do you actually have the image file in the destination folder? I checked, and there’s no such file there.

Yes i have checked will revert it soon cant access due to lack of network
issue will do by tomorrow..
On Mon, 30 Dec 2024 at 7:02 PM, Shiroha @.***> wrote:

Same here. Do you actually have the image file in the destination folder?
I checked, and there’s no such file there.
—
Reply to this email directly, view it on GitHub
https://github.com/localsend/localsend/issues/2078#issuecomment-2565489618,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BLHMSJI7IQRE5APWOFRSS2L2IFDNTAVCNFSM6AAAAABSJ4YVS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVGQ4DSNRRHA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Align score test cases

Reviewer: @Tanmay-97
Estimate: 1 hrs

Added new test cases for guardrails to ensure llm response is consistent with context provided
Ticket
Fixes: AAQ-252
Description, Motivation and Context
In the spirit of Test-Driven-Development, I wanted to raise this PR with test cases for the guardrail to check.
@Tanmay-97 - Would you be able to look through these and see if you agree with the "True" and "False" labels I have provided?
Changes
Test data and new placeholder test cases.
How Has This Been Tested?
You can run the read_test_data function but really no testing is needed since it is mostly just data.
Next up

Guardrails functionality using GPT-4
Guardrails functionality using AlignScore
Docs

Checklist:
This checklist is a useful reminder of small things that can easily be forgotten.
Put an x in all the items that apply and remove any items that are not relevant to this PR.

[x] My code follows the style guidelines of this project
[x] I have reviewed my own code to ensure good quality
[x] I have tested the functionality of my code to ensure it works as intended
[x] I have resolved merge conflicts
[x] I have updated the automated tests (if applicable)
[x] I have written [good commit messages][1]
[ ] I have updated the README file (if applicable)
[ ] I have updated affected documentation (if applicable)

At a high-level, how would these rails help make LLM responses safer? Because the test cases are like GRE's Reading Comprehension questions. We know already that GPT-4 passes that with flying colors. I need to read a bit more on guardrails, but we could we think about corner/edge cases in the context_ where the LLM operates e.g. maternal health

So what these do is make sure LLM is only answering from the context and not using it's pre-training or other sources. So for example, if the context provided is in conflict with it's pre-training, it should prefer context over pre-training. This give me an idea for another test case with made up context that is wrong and see if it adheres to it.

Also, I wonder if it's worth introducing trinary logic. Some question are better answered with unclear from the para instead of True or False

If it is unclear, then it should say "False". We don't want the LLM response to say things that it is not confident about. What "confidence" means will be a parameter. Look out for the next PR!


[Popup] - popups in menu

http://codepen.io/Biggrecian/pen/vOdwLd
Popups don't work in a menu when they are inline or a non sibling popup.
They do work when the attribute is set. though.
See Code pen on right menu.  Number "1" works.  Number "2" does not.
OK not sure why but when I reloaded the pen it worked SoI must have done something - this now closed.

I'm still having issues getting popups working properly when triggered by items within menus.


Production having warnings about firestore backend

[2023-12-06T04:01:51.682Z]  @firebase/firestore: Firestore (10.6.0): Could not reach Cloud Firestore backend. Backend didn't respond within 10 seconds.
This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend.

Shows up on any load after the first from a fresh profile.
I thought this originally was caused by the storage outage, but it persists after that.
Cards created in this state do show up on the server viewer, although the warning spooks me (and also incidentally means that suggestions don't work because the cards never get fully loaded)

See also #665.

https://github.com/firebase/firebase-tools/issues/6162 I thought was causing this at first (because I was also running into this after a failed deploy, but that's since been cleaned up.)

It seems like there are two issues: 1) an erroneous error showing up because it takes a long time to validate the large corpus (this is a guess) and 2) a "cards not fully loaded" error that happens due to a timing error.
There's been a long-time bug where we signal expectUnpublishedCards once, but then there are three distinct unpublished cards types, and some code paths that return an empty one will bail early before reporting that they did indeed get downloaded. This is a race that is now resolving differently due to the size of the payload (I guess)
Anywhere that takes unpublished : boolean should take type CardPublishedType = 'published' | 'unpublished_all', 'unpublished_editor', and 'unpublished_author'. And then  disconnectLiveUnpublishedCardsForUser should unregister if there's a need to. And updateCards() shoud take CardPublishedtype, and send an empty object if necessary... which the reducer should note there are no items and then unset the flag of that type.

I think the recent timing change broke the "make a new working notes card" flow.
Now when you hit the working notes button or use the shortcut, it creates a card, then navigates to it outside a collection, and then doesn't open it for editing. I wonder if it's the logic for selectCardsLoaded, which I noted might be overly simplified in the change.
This also triggers the #684 more often (or it's possible that was created by that issue)

Bisect confirms it was ba3f7c84cfc39f61edfbe3599c0ba91bfe92085c that broke it

A bug: if you create a new card before the final computed state of the last edited card settles (e.g. before all new fingerprints are calculated), it seems to navigate to the new card outside the collection (and not open for editing). Some kind of race condition that didn't used to exist.


[Feature] Add FLAG_KEEP_SCREEN_ON for keeping screen on

I propose to add the flag FLAG_KEEP_SCREEN_ON for keeping screen on when the user is in the queue.

Hi Kevin,
Thank you for using our SDK and your suggestion here.
We think that this change could lead to kind of an unwanted default behavior in our customers app and affect their end users.
Best regards,
Reza Aziztabar
Queue-it Development team

Hi @Reza-0,
If I made a proposition with an opt-in option to enable it (not by default), could this feature be considered?

Hi @Kevinrob,
Our development team is busy now. This means we can not spent time on this for now.
We will put this in our todo list, but I can not share any ETA for it.
Best regards,
Reza Aziztabar
Queue-it Development team


Added css variables for typography colors

Related issue #2839

This was certainly missing 😅! I will test that it works and then we'll have to make a new release of eds-tokens.
Be aware though, that the process that will eventually lead to this "figma-broker" (along with the current eds-tokens) being deprecated has started, but it is likely to take a good while to figure out and implement the new token system. That will also cause the naming of css-variables coming from tokens to change, so will be a large breaking change when that time comes for people using these 😬.


What is the best practice to work with global persistent state, like authorisation data?

I think it is very frequency situation, when you want to have some global persistent state without Redux Injectors. But i didn’t find any information about this in docs. What is the best way to do that?

Its no different than managing a 'redux toolkit slice'. Just make a state for example called 'appState' and instead of injecting just do this. Or you can inject it in your root component as well. All the state (injected or not) are persistent.
Ps: It's bit weird to expect documentation for everything. This isn't a beginner level boilerplate that handles everything for you. If you read the redux toolkit docs then you can definitely answer this question of yours easily ;)

Thank you for answer, i just wanted to know if there is a better way to do this)
PS: great boilerplate 👍


Auto name teleport out

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14187/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14187/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14187/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14187/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14187/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14187/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14187/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14187/merge#BCU1XR#0


example 0 pulls a csv from a strange url

this isn't great, it would be nicer if it came from an unquestionable source

this has been resolved, and this is also now a chance to demonstrate a try-catch


How do you create solr collection?

I've created the solrconfig.xml in var/solr/data/testcore/conf
I've imported the schema using the admin interface ->Core "testcore" -> Documents - > solr cmmand raw xml - > Submit document.
I get the following error.
3/23/2016, 10:26:50 AM

ERROR

null

SolrCore

org.apache.solr.common.SolrException: undefined field: "doctype"
3/23/2016, 10:26:50 AM

ERROR

null

SolrCore

org.apache.solr.common.SolrException: undefined field: "doctype"
3/23/2016, 10:26:51 AM

ERROR

null

SolrCore

org.apache.solr.common.SolrException: undefined field: "doctype"
3/23/2016, 10:28:21 AM

ERROR

null

ShowFileRequestHandler

Can not find: admin-extra.menu-top.html [/var/solr/data/testcore/conf/admin-extra.menu-top.html]
3/23/2016, 10:28:21 AM

ERROR

null

ShowFileRequestHandler

Can not find: admin-extra.menu-bottom.html [/var/solr/data/testcore/conf/admin-extra.menu-bottom.html]
3/23/2016, 10:28:21 AM

ERROR

null

ShowFileRequestHandler

Can not find: admin-extra.html [/var/solr/data/testcore/conf/admin-extra.html]

Meteor shows:

> 20160323-10:26:51.341(-5)? Request method: GET
> I20160323-10:26:51.341(-5)? Status code: 400 - Bad Request
> I20160323-10:26:51.341(-5)? Request headers:
> I20160323-10:26:51.341(-5)? accept: application/json; charset=utf-8
> I20160323-10:26:51.341(-5)? host: localhost:8983
> I20160323-10:26:51.341(-5)? Response headers:
> I20160323-10:26:51.342(-5)? cache-control: no-cache, no-store
> I20160323-10:26:51.342(-5)? pragma: no-cache
> I20160323-10:26:51.342(-5)? expires: Sat, 01 Jan 2000 01:00:00 GMT
> I20160323-10:26:51.342(-5)? last-modified: Wed, 23 Mar 2016 15:26:51 GMT
> I20160323-10:26:51.342(-5)? etag: "153a415e3ca"
> I20160323-10:26:51.342(-5)? content-type: text/plain; charset=UTF-8
> I20160323-10:26:51.342(-5)? transfer-encoding: chunked
>
> ```

Did you add the schema.xml file alongside the solrconfig.xml file? The doctype field is defined in the schema.xml.

TY, Ok imported the schema and added the schema.xml file to the dir. I get this error now, which I'm unsure.
` Exception while invoking method 'App.methods.autosuggest.getSuggestions' Error: failed [500] {"responseHeader":{"status":500,"QTime":4},"error":{"msg":"suggester was not built","trace":"java.lang.IllegalStateException: suggester was not built\n\tat org.apache.lucene.search.suggest.analyzing.AnalyzingInfixSuggester.lookup(AnalyzingInfixSuggester.java:533)\n\tat org.apache.lucene.search.suggest.analyzing.AnalyzingInfixSuggester.lookup(AnalyzingInfixSuggester.java:452)\n\tat org.apache.solr.spelling.suggest.fst.AnalyzingInfixLookupFactory$1.lookup(AnalyzingInfixLookupFactory.java:121)\n\ta...
`

Ah yes, the Solr suggester can be a pain - the easiest way to work around this is to call suggest.build=true to build the suggestions. So something like:
http://localhost:8983/solr/testcore/suggesthandler1?suggest.q=something&suggest.build=true

Sorry @hwillson  I'm trying to understand this whole thing. How would I insert data into Solr, so that I can test out the search. All I get now is search not found (*).

No problem at all - I just pushed a few test docs into the repo under /private/solr/data. Copy these files somewhere that your Solr install can see them, then run something like the following to add them into the collection:
post -c testcore /opt/solr_test_docs/*.xml

Thanks @hwilson got it going. Still getting error with autosuggestion. So, If I have a meteor collection of PDF's can I hook this up to work with the solr fairly easily you think?

After you import your docs you'll likely need to regen the suggestions, using something like:

http://localhost:8983/solr/testcore/suggesthandler1?suggest.q=something&suggest.build=true

Regrading the collection of PDFs, are they stored in Mongo? If so I'd recommend indexing them directly from Mongo itself, to get them into Solr. I've never tried indexing directly from Mongo, but this might help:
http://blog.mongodb.org/post/29127828146/introducing-mongo-connector


Probably a bug.

Well, the function format_phone always return with the country code +1, when I explicitly entered +91- for my country code, but it would always return as +1 and striped the +91- from database. (I used the sql file included by you and changed only the data)
Is it wrong in the way I store the database or this probably be a bug.

fixed :)


Spike: integrating Polygon's POS into Nightfall for block proposers

Research the effort and method required to integrate POS into Nightfall for block proposers

This is the staking contract in which Polygon base their SDK:
https://github.com/0xPolygon/staking-contracts/blob/main/contracts/staking.sol
I don't know for sure if we want to implement a PoS protocol that could be based on that contract and implement the operations for the proposers to stake/unstake and be the current proposer based on some rules from a list of staking proposers and a kind of epoch.
Or on the other hand we want to base the proposers list and current proposer based on the MATIC staked in the Polygon network discussed with @Westlad. Basically being a Polygon Staker should entitle you to be a Nightfall Proposer, and that will be done mainly through an integration at smart-contract level.
Another question is what we do with Challengers and Liquidity providers - do we leave these open for anyone or do we constrain them to be Polygon Stakers too? Something to be debated.

Hari found some other repo of Polygon/MATIC network: https://github.com/maticnetwork/contracts. The one I found is only for Polygon SDK as I see.
Here is also some documentation about staking:
https://github.com/maticnetwork/matic-docs/blob/master/docs/home/architecture/contracts/staking.md

Contrast the round robin proposer selection approach with Polygon’s validator selection
If it is a good solution, steps to replace the round robin proposer selection approach with Polygon’s validator selection
Staking using MATIC
contrast Polygon's stake, bond, slashing mechanism and incentive mechanism against Nightfall's
If these are a good solution, steps to replace Nightfall's with Polygon's

As for consensus mechanism, we’re relying on Ethereum’s consensus PoW and soon PoS currently because our transactions are submitted to Ethereum mainnet not Polygon sidechain. As a result, our consensus will definitely have to be Ethereum’s

NF_POLY_POS.pptx
Sharing deck following my study on Polygon POS integration and useful links for reference

How does Polygon's POS deal with idle proposers?

Shared hackmd document  for the proposal of the different parts of the Nightfall PoS based on the Polygon PoS information:

https://hackmd.io/m_85iGlMTzGkc4hZSElTKQ

How does Polygon's POS deal with idle proposers?

The proposers are required to sign the checkpoint every 30 minutes. Failure to sign or double sign results in slashing and jailing of proposer initiated by the slashmanager contract. However , there does not seem to be slashing of proposer stakes when a proposer does not produce blocks when its elected as leader assuming the difficulties  to differentiate when the proposer intentionally slowed network or whether there were no transactions in that period ( similar to issue #96 ).
While initiating a checkpoint based slashing , its important to look at possible attack vectors. One easy argument is performing DDOS on the elected proposer. This can also be extended to any proposer to stop them from signing checkpoints and thereby loose stakes. Tendermint claims to solve this partially by using a sentry node which acts like a proxy between the proposer and public world there by not revealing ip of proposers.

After discussing the approach suggested by @daveroga, this solution seems to be a good fit that will be explored and implemented in a future sprint. #464 has been created for this.


SuspiciousFileOperation when uploading file

Received below message when trying to upload any file in django. This also shows on the user-side (browser) as bad request 400.
Environment:

Request Method: POST
Request URL: http://<IP_ADDRESS>:8000/uploads/create_experiment/

Django Version: 3.2.4
Python Version: 3.8.10
Installed Applications:
['grappelli',
 'django_markdown2',
 'django.contrib.admin',
 'django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 'debug_toolbar',
 'basicviz',
 'annotation',
 'massbank',
 'options',
 'registration',
 'uploads',
 'decomposition',
 'ms1analysis',
 'django_extensions',
 'motifdb']
Installed Middleware:
['debug_toolbar.middleware.DebugToolbarMiddleware',
 'debug_toolbar_force.middleware.ForceDebugToolbarMiddleware',
 'django.middleware.security.SecurityMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.middleware.clickjacking.XFrameOptionsMiddleware']

Traceback (most recent call last):
  File "/home/joewandy/.local/share/virtualenvs/ms2ldaviz-yVayVtg0/lib/python3.8/site-packages/django/core/handlers/exception.py", line 47, in inner
    response = get_response(request)
  File "/home/joewandy/.local/share/virtualenvs/ms2ldaviz-yVayVtg0/lib/python3.8/site-packages/django/core/handlers/base.py", line 181, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/joewandy/.local/share/virtualenvs/ms2ldaviz-yVayVtg0/lib/python3.8/site-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view
    return view_func(request, *args, **kwargs)
  File "/home/joewandy/git/ms2ldaviz/ms2ldaviz/uploads/views.py", line 26, in create_experiment
    new_experiment.save()
  File "/home/joewandy/git/ms2ldaviz/ms2ldaviz/basicviz/models.py", line 142, in save
    super(Experiment, self).save(*args, **kwargs)
  File "/home/joewandy/.local/share/virtualenvs/ms2ldaviz-yVayVtg0/lib/python3.8/site-packages/django/db/models/base.py", line 726, in save
    self.save_base(using=using, force_insert=force_insert,
  File "/home/joewandy/.local/share/virtualenvs/ms2ldaviz-yVayVtg0/lib/python3.8/site-packages/django/db/models/base.py", line 763, in save_base
    updated = self._save_table(
  File "/home/joewandy/.local/share/virtualenvs/ms2ldaviz-yVayVtg0/lib/python3.8/site-packages/django/db/models/base.py", line 842, in _save_table
    values = [(f, None, (getattr(self, f.attname) if raw else f.pre_save(self, False)))
  File "/home/joewandy/.local/share/virtualenvs/ms2ldaviz-yVayVtg0/lib/python3.8/site-packages/django/db/models/base.py", line 842, in <listcomp>
    values = [(f, None, (getattr(self, f.attname) if raw else f.pre_save(self, False)))
  File "/home/joewandy/.local/share/virtualenvs/ms2ldaviz-yVayVtg0/lib/python3.8/site-packages/django/db/models/fields/files.py", line 302, in pre_save
    file.save(file.name, file.file, save=False)
  File "/home/joewandy/.local/share/virtualenvs/ms2ldaviz-yVayVtg0/lib/python3.8/site-packages/django/db/models/fields/files.py", line 88, in save
    name = self.field.generate_filename(self.instance, name)
  File "/home/joewandy/.local/share/virtualenvs/ms2ldaviz-yVayVtg0/lib/python3.8/site-packages/django/db/models/fields/files.py", line 321, in generate_filename
    filename = validate_file_name(filename, allow_relative_path=True)
  File "/home/joewandy/.local/share/virtualenvs/ms2ldaviz-yVayVtg0/lib/python3.8/site-packages/django/core/files/utils.py", line 18, in validate_file_name
    raise SuspiciousFileOperation(

Exception Type: SuspiciousFileOperation at /uploads/create_experiment/
Exception Value: Detected path traversal attempt in '/home/joewandy/git/ms2ldaviz/ms2ldaviz/media/experiment_1377/Beer_3_T10_POS.mzML'

As a workaround, I downgraded django to the latest version known to work (==3.0.6)


Fixed unnecessary warning when using IRModel

Fixed unnecessary warning when using IRModel.When you use Multiple validation datasets with IRModel, 'Multiple validation datasets are only supported by SRModel' will appear, but will still work, so it is redundant.

Thanks!


[PORT] Add OnContinueConversation trigger and ContinueConversationLater action

Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/4063

Add PostActivityAsync method to BotFrameworkHttpClient to make it easy to post secure EventActivity to your bot
Add OnContinueConversation trigger
Add ContinueConversationLater action to BotBuilder.Azure
Add unit tests, etc.

Changed projects

Microsoft.Bot.Builder.Azure
Microsoft.Bot.Builder.Dialogs.Adaptive
integration
Microsoft.Bot.Builder.Azure.Tests
Microsoft.Bot.Builder.Tests

[changes required]

@luhan2017, @joshgummersall and I want to sync with you regrading this issue. We have some questions about the specific deliverables and their timeframe 😄


Installing Zabbix 6.x and partitioning PostgreSQL 14.x

Hi @Doctorbal,
I read that Zabbix has changed few things concerning database:

So, when following your instructions for partitioning PostgreSQL 14.x, I think "Create Empty history* and trends* Tables" has to be modified, unfortunately I am not even good with DB stuff.
Thank you for your time.
Omar

@elekgeek ,
I have not had the time to do this and will most likely not get to it for a while.
I still have an outstanding issue that addresses upgrading Zabbix to 5.x and using PostgreSQL v12 that I haven't got to!
I would warmly get some feedback and see others commit changes to this repository though! So if you are going down this route right now I would be very grateful for your insight and feedback on how what needs changing in PostgreSQL v14 with Zabbix 6.x. This would save myself a lot of time in the future!
Thanks & Best Regards,
Andreas

I will try to install it myself and see how it goes :- )

This worked for me. zabbix 6.2 and PostgreSQL 14
-- history
CREATE TABLE public.history
(
itemid bigint NOT NULL,
clock integer DEFAULT 0 NOT NULL,
value double precision DEFAULT '0'::double precision NOT NULL,
ns integer DEFAULT 0 NOT NULL,
CONSTRAINT history_pkey PRIMARY KEY (itemid, clock, ns)
) PARTITION BY RANGE (clock);
-- history_log
CREATE TABLE public.history_log
(
itemid bigint NOT NULL,
clock integer DEFAULT 0 NOT NULL,
"timestamp" integer DEFAULT 0 NOT NULL,
source character varying(64) DEFAULT ''::character varying NOT NULL,
severity integer DEFAULT 0 NOT NULL,
value text DEFAULT ''::text NOT NULL,
logeventid integer DEFAULT 0 NOT NULL,
ns integer DEFAULT 0 NOT NULL,
CONSTRAINT history_log_pkey PRIMARY KEY (itemid, clock, ns)
) PARTITION BY RANGE (clock);
-- history_str
CREATE TABLE public.history_str
(
itemid bigint NOT NULL,
clock integer DEFAULT 0 NOT NULL,
value character varying(255) DEFAULT ''::character varying NOT NULL,
ns integer DEFAULT 0 NOT NULL,
CONSTRAINT history_str_pkey PRIMARY KEY (itemid, clock, ns)
) PARTITION BY RANGE (clock);
-- history_text
CREATE TABLE public.history_text
(
itemid bigint NOT NULL,
clock integer DEFAULT 0 NOT NULL,
value text DEFAULT ''::text NOT NULL,
ns integer DEFAULT 0 NOT NULL,
CONSTRAINT history_text_pkey PRIMARY KEY (itemid, clock, ns)
) PARTITION BY RANGE (clock);
-- history_uint
CREATE TABLE public.history_uint
(
itemid bigint NOT NULL,
clock integer DEFAULT 0 NOT NULL,
value numeric(20,0) DEFAULT '0'::numeric NOT NULL,
ns integer DEFAULT 0 NOT NULL,
CONSTRAINT history_uint_pkey PRIMARY KEY (itemid, clock, ns)
) PARTITION BY RANGE (clock);
-- trends
CREATE TABLE public.trends
(
itemid bigint NOT NULL,
clock integer NOT NULL DEFAULT 0,
num integer NOT NULL DEFAULT 0,
value_min double precision DEFAULT '0'::double precision NOT NULL,
value_avg double precision DEFAULT '0'::double precision NOT NULL,
value_max double precision DEFAULT '0'::double precision NOT NULL,
CONSTRAINT trends_pkey PRIMARY KEY (itemid, clock)
) PARTITION BY RANGE (clock);
-- trends_uint
CREATE TABLE public.trends_uint
(
itemid bigint NOT NULL,
clock integer NOT NULL DEFAULT 0,
num integer NOT NULL DEFAULT 0,
value_min numeric(20,0) DEFAULT (0)::numeric NOT NULL,
value_avg numeric(20,0) DEFAULT (0)::numeric NOT NULL,
value_max numeric(20,0) DEFAULT (0)::numeric NOT NULL,
CONSTRAINT trends_uint_pkey PRIMARY KEY (itemid, clock)
) PARTITION BY RANGE (clock);

Fantastic @ents-hqx ! Thanks for sharing!


Unix time 2038 problem

Q
A

New feature?
✔

Using int type for date don't have unix time 2038 problem.

Using int type for date don't have unix time 2038 problem.

What if working with db?
replace int with bigint?

Using int type for date don't have unix time 2038 problem.

What if working with db? replace int with bigint?

This is problem of implementation AssignmentsStorageInterface and ItemsStorageInterface. In concrete implementation we can convert int value to need format.

This is problem of implementation AssignmentsStorageInterface and ItemsStorageInterface. In concrete implementation we can convert int value to need format.

Sorry if I took your time
I got a great skill out of this job. (more precisely from these comments :)
Thank you. :)


Are type annotations available somewhere?

If I run mypy it complains
error: No library stub file for module 'pymemcache.client.base'
note: (Stub files are from https://github.com/python/typeshed)

I'm afraid we don't have official stubs to share at this time, but they would be great to have.


[FEAT] [New Query Planner] Add logical plan hashing, rule batches, fixed-point policies, early optimizer termination, and optimization cycle detection.

This PR adds support for logical plan Hash/Eq, optimization rule batches + fixed-point policies per batch, early optimizer termination, and catches optimization cycles.
When refactoring the optimizer to support rule batches, I also changed the optimization methods to represent an optimization attempt with Transformed<Arc<LogicalPlan>> instead of the previous Option<Arc<LogicalPlan>>, which made things a bit cleaner.

@xcharleslin Ah shoot I just rebased onto main, saw that Project::try_new() was missing and so I implemented, and now it looks like you've recently pushed a commit to main that implements it too, so looks like I've got some more conflicts to fix! 🤦

@xcharleslin Ok PR is updated on latest main!


Update tasmota to tasmota-lite 9.1.0

Congrats Tuya-convert team
Please find a PR to upgrade Tasmota to v9.1.0
I also changed the reference fromtasmota-wifiman to  tasmota-lite as the 1st one doesn't exist any more.
Thanks

Thanks for your PR @barbudor!
I'll merge this as soon as we can get confirmation from at least two other members that this worked for them.

Hi
Any update ?
The Tasmota release is now 9.2.0
Keeping an old versions with Tuya-convert increase the risk for users to brick their devices when upgrading to last version without following the strict upgrade path.
Thanks


Jaguar can't monitor two ports on Windows

@Informaticore reports that Windows doesn't support two different jag monitor -p <com-port> on windows.

I tried it again to post the error "serial busy" but it does work now 🤷

Closing for now. Please reopen if it happens again.


Update jQuery?

Started at:
https://github.com/elkarte/Elkarte/issues/2557#issuecomment-222525399
IIRC Elk is still using 1.x update could be slightly less easy than just change the version numbers. Due to the (AFAIR) massive changes from 1.x to 2.x we'd have to be sure all the plugins we ship are able to work with the most recent versions of jQuery.
Honestly I don't know what milestone set for this one.

cough
https://github.com/elkarte/Elkarte/commit/746c5cfadf1d926c84d1121e2bf1eb640e550250

ROFL!
/me reminds everybody that he hates javascript and doesn't look at it unless strictly necessary. :angel:

I hate jQuery, but Javascript is awesome. =P
Anyhoo, do we want to drop the browser support that jQuery 3.x drops?

2.x dropped ie8 support ...  I don't think 3.x dropped additional ones?
The problems with 3.0 will probably be with the editor, which has been dead in the water for almost a year now.  We could fix other issues with our code, but I sure as heck never want to "own" the editor.
I also, as a matter of course, avoid any jQuery that starts with .0 unless you enjoy significant pain in the can.

jQuery 2.x officially supports Opera/Presto. A much more difficult browser to let go than IE8. ;-) That being said, jQuery 3.x should probably still be fine for the most part; I haven't checked.
 Bleurgh.
Anyway, I'll take a look later this week, maybe tomorrow, just to see how much breaks. It might not be too bad.

Opera 12 users should be moving to Vivaldi. What with the buyout announcement I am going to be letting my own Opera using members know at least.

I hate jQuery, but Javascript is awesome. =P

I concur. I  like JS more than PHP.

At a first quick glance nothing seems to be broken in jQuery 3, including in Opera 12, nor is the migrate plugin spitting out any warnings. Quick edit, SCEditor in source & rich text view, and YouTube embedding are working just fine.
@live627 Yup, I like JS much more than PHP, especially with strict mode. To be fair, PHP has improved a lot. It's much better in PHP 5.2+ or so compared to PHP 2/3.

So, worth considering for 1.1?

There is an issue with the editor and 3.0 ... specifically 3.0 "Removed deprecated event aliases .load, .unload, and .error, deprecated since jQuery 1.8, are no more. Use .on() to register listeners."  Someone is going to do a PR for the editor to fix it but as it stands its broken.

You are right, there is an issue open for that: https://github.com/samclarke/SCEditor/issues/525

#2682
SCE and atwho still use the old syntax. (jQuery is for chumps)


docs: more build docs

Transforming the adapters document into a more general build doc
Closes #8436
The alternative to this is to introduce another top level document (keeping the adapter doc as is) - I'm fine with that, too.
Maybe I actually prefer that; opened #8501 for comparison
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[ ] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

I really hate that we have to bump the adapter packages everytime we update their docs. Maybe we should take this opportunity to move their docs from the READMEs to the docs folder?
That gives me another idea which would be to create a Building Your App section. Within that could live the new page, the general adapters docs, and docs for each individual official adapter.

closing in favour of #8531


Why is cChocoInstaller.InstallDir required?

Why is InstallDir required when Chocolatey installer has default value?

No idea.

I mean, I see this but I'm not a maintainer of cChoco so I'm not privy to how it was designed. It could be the chocolatey install directory, but I'm not sure.

DSC resources require a key property of some sort; they can't exist without something being mandatory.  I suspect that in this case, there just wasn't a better candidate.

@dlwyatt exactly my logic, it meets the key property constraint and felt like the best choice at the time.
Happy to tweak if we can find a better candidate?

IMO, it's not worth the breaking change even if you did find a "better" option later.  Works fine as-is.  :)

That makes sense then.
I would propose version as a candidate with special handling for 'latest'. But as you say it would be a breaking change and not really worth it.

I know this is long closed, but how do I then determine chocolatey's default installdir from within a dsc config? I do want to keep the default.

$env:ChocolateyInstall ?

I presume $env:ChocolateyInstall doesn't exist before chocolatey is installed. I assume it should be $env:ProgramData\chocolatey?

@trueqbit That's correct.


Add prefix to slurm logs

option to add a prefix to slurm logs (could be useful when tokenizing multiple sources in the same logging_dir)

I would generally advise against running different jobs in the same directory, as the completion folder, the logs and stats would get overwritten between jobs. It's usually cleaner to change the logging_dir directly by appending the prefix to it

Ok that makes sense, closing the PR


[cinder-csi-plugin] Update CSIDriver object version to v1

storage.k8s.io/v1beta1 CSIDriver object has been deprecated
Update to use v1.

What this PR does / why we need it:
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

/lgtm
/approve


Representing enums in the ui

I've opened this Issue to continue the discussion about this from #751 and zulip
Currently druid does not offer a good solution to representing enums in the ui.
While structs can be split up into their different fields using Lens, no such feature exists for enums.
Considering how prevalent enums are in Rust, I would argue that druid should provide a good solution for this.
The ideas so far are

Extending Lens to work with enums
Introducing a new derive specifically for enums
Using an immediate mode widget (#751)

I've implemented (examples of) those three here,
also @cmyr expressed similar ideas on #751
My preferred solution would be number 2, introducing a new Match derive similar to Lens which adds a ::matcher() -> MyTypeMatcher function to the deriving type (MyTypeMatcher would be generated).
For example if Option would derive Match:
Option::matcher()
    .some(|| make_widget_some())

Having the matcher as a function on the type should be more intuitive than having to know that there is now also a separate struct called OptionMatcher, especially when exporting (pub use) it.
This matcher would provide one method per variant, as well as a default method to mimic _ =>.
Of course this does not event get close to the power match provides but it should be good enough for most cases. Would be nice if  we could collect some ideas here and come up with something truly satisfying.

I'd like to try and be more explicit about exactly what problem we're trying to solve. To me, it feels like in the general case a given widget should expect a specific form of data.
Given this, the most natural form I can imagine for a widget that is displaying an enum is for that widget to be like a generalization of the current Either widget; it would be a container that managed a child, with the type of the child determined by the variant.
Importantly, this means that given say an enum like,
enum Wat {
    One(String),
    Two(usize),
}

Our outer widget would be a Widget<Wat>, and its inner widget would be either a Widget<String> or a Widget<usize>, depending on the variant.
One thing jumps out immediately: there is a distinction, for the sake of Data, between when the data has changed and when the enum variant has changed. If the data changes from Wat::Two(5) to Wat::Two(42), this should be transparent to the inner widget; it should just look like a normal update. If, however, it changes from Wat::Two(_) to Wat::One(_), we need to replace the inner widget, and likely do the WidgetAdded dance.
I think this means that one thing our custom macro needs to do is add some sort of same_variant method to our enum.
The other thing we need to is come up with some way of letting the user describe the widget that will be returned for each variant.
A current hurdle, for me, is that (I think) ideally the enum should be transparent to the inner widget. That is, the inner widget should have some concrete Data type that is not the enum, but is the contents of some variant of the enum. This is easy enough for a unit or a tuple variant (we just have the data be () or some tuple) but it's annoying for struct variants; we either have to generate a variant automatically (which will be annoying, because it will have some generated name) or we will need to provide some mechanism for the user to describe what type the outer type should be converted into.
It may be that we disallow struct variants, and ask people to use a tuple enum with a struct field, as in:
// boo
enum One {
    Thing { face_count: usize, face_length: f64 },
}

// yay
enum Two {
    Thing(Thing),
}

Thing { face_count: usize, face_length: f64 }

... or something.
I think this is a solvable problem, but I would like the solution to be one that really fits the druid model; my main reservation with the immediate mode idea is that we really lose out on the power of Data. That said, I think that if we figure something out here it will end up being a very powerful tool.
This isn't something I'm going to personally be spending much time on in the immediate future, but I'm glad that you're interested in it and I'm happy to provide whatever guidance and moral support I can.

I think I'll implement a simple version of such a proc-macro and see how it works out.
More ideas / opinions are still very much welcome though.

I'm happy to do a call or something if you want to talk through some of this.
I think the place to start would be a sketch of what code we want the proc macro to produce.
Then try and figure out what the components are. For instance: I think we are going to want some sort of 'unwrapping variant lens', that extracts a given variant from an enum.

I'm happy to do a call or something if you want to talk through some of this.

Sounds good :+1:

Writing down the ideas which came up:

Lens for enums
#[derive(Clone, Data, Lens)]
enum Event {
    Click(f32, f32),
    Key(char),
}

fn event_widget() -> impl Widget<Event> {
    // Matcher recreates its child whenever its determinant changes
    // Matcher::new takes Fn(&T) -> impl Widget<T>
    druid::Matcher::new(event_widget_impl)
}

fn event_widget_impl(event: &Event) -> impl Widget<Event> {
    // standard Rust code and behaviour such as exhaustiveness
    match event {
        Event::Click(_, _) => Label::dynamic(|data, _| {
            format!("x: {}, y: {}", data.0, data.1)
        }).lens(Event::click),
        // IT'S A TRAP! The `Label` will not update when 'char' changes
        Event::Key(char) => Label::new(format!("key: {}", char))
            .lense(Even::key),
    }
}

A proc-macro match
Based on Lens for enums
fn event_widget() -> druid::Matcher<Event> {
    match_widget! { Event, // could this type hint be ommited?
        Event::Click(x, y) => Label::dynamic(|data, _| {
            format!("x: {}, y: {}", data.x, data.y) // named touple?
        }),
        Event::Key(_) => Label::dynamic(|data, _| format!("key: {}", data))),
    }
}

fn event_widget() -> impl Widget<Event> {
    match_widget! { Event,
        Event::Click(x, y) => Label::dynamic(|data, _| {
            format!("x: {}, y: {}", x, y) // not valid or changed to data.x?
        }),
        _ => Label::dynamic(|data: &Event, _| format!("key: unhandled"))),
    }
}

A proc-macro derive
#[derive(Clone, Data, Match)]
enum Event { .. }

fn event_widget() -> impl Widget<Event> {
    Event::matcher()
        .click(Label::dynamic(|data, _| {
            format!("x: {}, y: {}", data.0, data.1)
        ))
        .key(Label::dynamic(|data, _| {
            format!("key: {}", data))
        })
}

fn event_widget() -> impl Widget<Event> {
    Event::matcher()
        .key(Label::dynamic(|data, _| {
            format!("key: {}", data))
        })
        .default(Label::new("Unhandled Event"))
    }
}

fn event_widget() -> impl Widget<Event> {
    // Will emit warning for missing variant
    // Event::Click at runtime
    Event::matcher()
        .key(Label::dynamic(|data, _| {
            format!("key: {}", data))
        })
    }
}

@cmyr I think those were the most fundamental ideas I'll explore for now, if I missed something that came up please remind me, my head is a bit overflowing with ideas right now :sweat_smile:

There is approach which might be worth considering/thinking over, which is to generate an auxiliary unitary enum, and using discriminator values, to make some kind of array of widgets.
Discriminator values can be set up by arbitrary constant functions even, here is basically a silly example, anyhow there might be an custom derive approach which generates these kind of enum VariantIDEnum as an associated trait.
Anyhow another thing to mull over, as though there weren't enough of those :dagger:
https://gist.github.com/rust-play/14f8c850f09f9cf8d0829a6e87806b8a

Sorry but I can not follow what you mean :sweat_smile:
You mean something like this https://doc.rust-lang.org/stable/std/mem/struct.Discriminant.html?

array of widgets

Something in this direction?

Sorry, I'm not terribly clear as I haven't thought through the whole thing entirely,
In general the thought was: enum Foo { A(u32), B(String) } cannot have discriminators because they have non-unitary variants... but we could still derive a custom
impl Foo {
  enum FooVariantID {
     A = Foo::Widgets::WidgetID1,
     B = Foo::Widgets::WidgetID1
```
mapping some collection of widgets to the original enums variants. I think mem::Discriminant is opaque and we need transparency here so we can map an widget->enum variant via the discriminant.

Anyhow, it is what came to mind...

Okay, looking these over:

the basic impl with no macro looks right to me
the proc macro is a bit trickier; the use of the macro will be distinct from the generating of the lenses, so in the tuple case we can't use names; it will have to be data.0, data.1, etc. If we really wanted to get magical I guess we could probably map from the numbered fields to the names that were used? I think this will be confusing, though, if the user wants to do anything fancier than this. So I think it is best to be explicit about the fact that we're creating tuples under the covers.

about discriminants: I'd totally overlooked mem::discriminant. This will solve one problem.

I've setup a repo where I'll push my progress on this:
https://github.com/Finnerale/druid-enum-helpers
(right now it's just the proc-macro setup stuff)

Short update on this:
I've decided to go with a derive macro, as it turned out to be simpler implementation wise and more robust in practice.
To make using it easier, I set up a new repo for just this macro here: https://github.com/Finnerale/druid-enums
So far it supports any enums with unit or tuple variants that also implement Data.
(thanks @derekdreery for implementing most of it.)
It is still missing support for generics, good docs and tests.
I'm not sure though, whether I should publish it as a separate crate, or leave it as a repo until it reaches a quality where it can be merged into Druid.

Aah I was going to post my fork, but you are already using it - perfect. :)


Inconsistent Source Code

'Full Source' section is inconsistent with guide and it's recommendations for configuring the body tracking app

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

ID: 50f08064-28da-6415-1e57-858760b31c64
Version Independent ID: ff491440-06d2-b9a0-12d0-deb3d1a68b6c
Content: Quickstart - Build your first Azure Kinect body tracking application
Content Source: articles/kinect-dk/build-first-body-app.md
Product: kinect-dk
GitHub Login: @qm13
Microsoft Alias: quentinm

Thanks for the feedback! We are currently investigating and will update you shortly.

@josephmwells Thanks for reaching out! Would you please provide more detail about how it is not consistent with guide or What changes need to be made to improve this document?

Hi @josephmwells just trying to understand the feedback a little better, would you please provide more detail? adding content author for awareness @qm13

@josephmwells just touching base to see if you can please elaborate more on your feedback? Thank you :)

@josephmwells I see that the code described in the steps doesn't match the full source. When it should be the outcome of following the steps. Thanks again for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Fixed

@qm13 Thanks for the fix.
@josephmwells We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Make packaging (freezing) apps with PyInstaller easy

Should be easy, since Flexx and all its dependencies are pure Python.
Maybe add App.make_pyinstaller() or something.

I would recommend testing this by making a single module application that depends on flexx, e.g. an example, and trying to package it with pyinstaller using the most basic spec file:
# -*- mode: python -*-

block_cipher = None

a = Analysis(['myflexxapp.py'],
             pathex=['.'],
             binaries=[],
             datas=[],
             hiddenimports=[],
             hookspath=[],
             runtime_hooks=[],
             excludes=[],
             win_no_prefer_redirects=False,
             win_private_assemblies=False,
             cipher=block_cipher)
pyz = PYZ(a.pure, a.zipped_data,
             cipher=block_cipher)
exe = EXE(pyz,
          a.scripts,
          exclude_binaries=True,
          name='myflexxapp',
          debug=False,
          strip=False,
          upx=True,
          console=False)
coll = COLLECT(exe,
               a.binaries,
               a.zipfiles,
               a.datas,
               strip=False,
               upx=True,
               name='myflexxapp')

I'm not sure why you would need a function like App.make_pyinstaller()?

I tested this, it actually seems to work (the packaging part). Flexx is having trouble retrieving sources once the distribution is frozen though. See the following link for example traceback:
https://github.com/Korijn/flexxtodo

PyInstaller does not have an option to include the original sources. It does have a feature to include "data files", so I just registered the original sources as data-files. Now I just need to be able to tell flexx where to look for sources.
This if getattr(sys, 'frozen', False): check can be used to detect that we are running from a bundle instead of sources, and sys._MEIPASS is then the path to the bundle folder. Can we get flexx to work with that?

Can we get flexx to work with that?

I am afraid that this is not trivial. Flexx uses inspect to get the source code. So we would need to do (more of) that ourselves so that we can map the filenames to another path...
What I do with Pyzo is copy the whole source directory. The script being frozen is aware of this and will do some sys.path magic so that Pyzo gets loaded from source instead of from the packaged .pyc files. (I think it exports 2 exes, one stub one to bring all dependencies in, which I remove later, and the one that does the loading.)
But I have a feeling that we might need more because a user might use functionality in JS from any module, how do we know what modules need to be distributed in source form?
It would be easiest if we could just include all sources as .py files instead of .pyc. We can also consider some sort of post-processing step in which we replace all .pyc files with .py files. It would be nice if PyInstaller had a flag for this :)  but from the issue you linked above I have a feeling that they would be reluctant to add something like this :)

#559 makes it easier still


RawImage proto file frame of reference is not matching the comment

Description
In the RawImage.proto file here https://github.com/foxglove/schemas/blob/f8d19d032541f8241b5e1576dd833fa09545bf40/schemas/proto/foxglove/RawImage.proto#LL14C1-L14C196 there is a comment that indicates a frame of reference but the parameter is just a string frame_id. I'm not sure which of these is supposed to be there but we would like to have an actual frame of reference parameter on images.

You can see some example code in nuscenes2mcap which is used to make our sample dataset:

The image is positioned in 3D space based on the FrameTransform messages with the corresponding frame_id.
I confirmed that Studio actually doesn't use the image's frame_id in the app right now, but rather the frame_id of the chosen Camera Info topic. You can find relevant discussion at https://github.com/foxglove/schemas/issues/59. The Image's frame_id is there for completeness and so users can cross-reference raw data to make sure the right topics are being used.


esp_timer_get_time() is inaccurate if called in short sequence (IDFGH-3142)

Environment

Development Kit: custom board
Module or chip used:  ESP32-WROOM-32
IDF version: v4.1-beta1-112-g4fe18a925
Build System: CMake
Compiler version: xtensa-esp32-elf-gcc (crosstool-NG esp-2019r2) 8.2.0
Operating System: Linux
Using an IDE?:  VSCode

Problem Description
Calling esp_timer_get_time() in short sequence (20ms or less) may occasionally return the same value twice, or generally values too close to each other.
Expected Behavior
The returned time should be accurate
Actual Behavior
See problem description
Steps to reproduce
Run the following code in a test application. On my setup it fails about 30% of times.
TEST_CASE("esp_timer_get_time() burst", "timer")
{
        int64_t t[100] = {};
        for (uint8_t i=0;i<100;i++) {
                t[i] = esp_timer_get_time();
                vTaskDelay(pdMS_TO_TICKS(10));
        }
        for (uint8_t i=1;i<100;i++) {
                ESP_LOGI(TAG,"%lld,%lld",t[i-1],t[i]);
                TEST_ASSERT_EQUAL(0,t[i-1]/1000==t[i]/1000);
        }
}

Please let me know if you need more details

Hi @maikeriva!
I see this is the old report. I tried to run this code (using v4.1-beta1-112-g4fe18a925 ) but it does not fail. It works well. I suppose there is some special to reproduce it. Could you share the sdkconfig file?
Thanks.

Hi @maikeriva! This case is not related to esp_timer. I did some experiments with the Tick rate (Hz) and I see that this behavior happens when CONFIG_FREERTOS_HZ = 100.
vTaskDelay(pdMS_TO_TICKS(10));
...
#define pdMS_TO_TICKS( xTimeInMs ) ( ( ( TickType_t ) ( xTimeInMs ) * configTICK_RATE_HZ ) / ( TickType_t ) 1000 )

pdMS_TO_TICKS(10) gives 1. 1 tick = 10ms.
100Hz Tick rate does not provide a good resolution for your goal. For vTaskDelay it is possible to get not accurate delay (even less than 1ms).

Thanks for reporting, feel free to reopen.


Tags should be listed alphabetically and show number of posts in ()

Implement in this commit:
https://github.com/smohadjer/blog/commit/4024dd3c5dc921d1ecdebd3e64304a6cb3984d79


AuthorizationService.AuthorizeAsync doesn't fail in any case

I have added this action to ContentAPiController in Orchard.Demo module:
 public async Task<IActionResult> GetAuthorizedById([FromServices] IContentManager contentManager, int id)
        {
            var contentItem = await contentManager.GetAsync(id);

            if (!await _authorizationService.AuthorizeAsync(User, Permissions.ViewContent, contentItem))
                return Unauthorized();

            if (contentItem == null)
            {
                return NotFound();
            }

            return new ObjectResult(contentItem);
        }

Problem is that no matter if I'm logged in or I'm anonymous AuthorizeAsync never returns false.
Maybe this issue is related with this other one https://github.com/OrchardCMS/Orchard2/issues/194

In this case, ViewContent permission is actually available on all roles, even Anonymous. Try with a more restrictive permissions. Or remove it from the anonymous user (the controller is not yet implemented for this)

You are right.


Stream closed error

I am using Capybara for web page scraping and I have a module that executes this line of code when I want to close the phantomjs.
@session.driver.quit
This line of code works fine 90% of the time but when the scraping task takes hours (6 or more) that line of code make my code crash.
The error on the sidekiq.log:
2016-03-16T09:07:04.368Z 28285 TID-ch1b4 WARN: closed stream
I really don`t know what is happening because it works most of the the time.

I was able to reproduce this error, every time I exectute @session.driver.quit this line of code kills phantomjs but if I run it again the line of code throw the close stream error.

Why do you need to call quit twice?

Closing due to lack of response


Nuxt Project Stopped Working During Windows 11 Development

Environment
Windows 11
Node 20.8
Nuxt version: 3.12

{
"name": "nuxt-app",
"private": true,
"type": "module",
"scripts": {
"build": "nuxt build",
"dev": "nuxt dev",
"generate": "nuxt generate",
"debug": "nuxi dev --inspect",
"preview": "nuxt preview",
"postinstall": "nuxt prepare"
},
"prisma": {
"seed": "node prisma/seed.js"
},
"dependencies": {
"@nuxtjs/tailwindcss": "^6.12.1",
"@pinia/nuxt": "^0.5.1",
"@prisma/client": "^5.16.2",
"bcrypt": "^5.1.1",
"google-auth-library": "^9.11.0",
"jsonwebtoken": "^9.0.2",
"nuxt-vue3-google-signin": "^0.0.11",
"pinia": "^2.1.7",
"vue": "latest",
"vue3-draggable-next": "^4.1.4",
"zod": "^3.23.8"
},
"devDependencies": {
"autoprefixer": "^10.4.19",
"nuxt": "^3.12.3",
"postcss": "^8.4.39",
"prisma": "^5.16.2",
"tailwindcss": "^3.4.5"
},
"overrides": {
"vue": "latest"
}
}
Here is my nuxt.config.ts:
// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
compatibilityDate: '2024-04-03',
devtools: { enabled: false },
debug: true,
// colorMode: {
// preference: 'light', // default value of $colorMode.preference
// },
plugins: ['/plugins/prisma.js', '/plugins/auth.js'],
sourcemap: {
server: true,
client: true,
},
runtimeConfig: {
// Keys within public are also exposed client-side
public: {
apiBase: '/api',
},
jwtSecret: process.env.JWT_SECRET,
googleClientId: process.env.GOOGLE_CLIENT_ID,
},
modules: [
'@nuxtjs/tailwindcss',
'@pinia/nuxt',
'nuxt-vue3-google-signin',
],
css: ['~/assets/css/main.css'],
postcss: {
plugins: {
tailwindcss: {},
autoprefixer: {},
},
},
googleSignIn: {
clientId: process.env.GOOGLE_CLIENT_ID,
},
});
Please help fix the issue promptly, as I am unable to continue an important project of mine built with Nuxt 3.
Thanks for all helpers.
Reproduction
Windows 11 normal development
Describe the bug
An error appears in my console which stops me from being able to continue development as my local server isn't working.
tried re-installing, what not.
nothing seems to impact the issue.
Additional context
No response
Logs
No response

Solved, recreated node_modules from scratch.
Bug closed.


Feature: Add X-Stormpath-Agent header

Adds the X-Stormpath-Agent header to all API requests.
How to verify

Checkout this branch.
Link it ($ npm link).
Clone the React example app.
Link to the feature branch ($ npm link react-stormpath).
Start the app ($ npm start ).
Navigate to the login page.
Open up the network console and try to login.
Assert that the POST request to /login contains the header X-Stormpath-Agent: react-stormpath/0.5.0.

Fixes #30.

I've verified that this works as expected in Chrome, Safari, and Firefox :+1:
But please see my comment regarding also including the React version. And also, Robert excluded this header for CORS requests from the Angular SDK. Will you save that for when you add CORS support?

@timothyej Thanks!
I don't think it's necessary to exclude the header for CORS requests since it only requires the users to add add support for that header.

Yes, but then it also requires them to do that in order to get it to work, which adds more friction since it doesn't provide any value for the user. I guess that was @robertjd's thoughts as well?

@typerandom please remove the header if the request is cross-domain.  Otherwise, the user will have to add our custom header to their server-side configuration.  We don't want to burden the developer with this.  See DOM API usage here.  Thanks!

@robertjd Sure, will fix that.

@robertjd This is now fixed. I refactored a few things at the same time. The important line to review is this one: https://github.com/stormpath/stormpath-sdk-react/pull/31/files#diff-12ab8b19aebc183c7b26d5fe0f102c6bR60

@timothyej Please review again :)

I've verified that this works as expected in Chrome, Safari, and Firefox :+1:

\o/ thanks!


Mocha should also report tests that couldn't run due to failure in before/beforeEach block

Is your feature request related to a problem or a nice-to-have?? Please describe.
This request is related to problem, we face while generating full report of failed/passed/ignored tests. Mocha shows all tests perfectly if before/beforeEach block runs without any error/exception but if there is some error/exception in before/beforeEach block during execution then it just throw exception of before block and comes out of describe block. Problem is that it doesn't show any information of tests status defined in particular describe block. It is all manual effort to get list of all tests for which before/beforeEach block has failed.
Describe the solution you'd like
Throwing exception is perfectly fine but I would expect to have information of all tests as Not Executed something like that in report part. It will help us to understand and get list of all tests cases that couldn't execute due to failure in before/beforeEach block.
Additional context
sample describe block which is take from mocha smoke.spec.js

Output of execution

@sahunitin thank you.
There are already several issues on the same topic eg. #4392.


Add response check for Java automated testing.

GAX PR: https://github.com/googleapis/gax-java/pull/98

LGTM

That is, after the Travis test is fixed


Upgrades do not use SSL if SSL is enabled on the site

Description of bug
upgrade does not use SSL if SSL is enabled
Steps to reproduce
List the steps to reproduce the behavior:

upgrade.wizard without putting in HTTPS for the address
You will be directed to a non SSL page

Current result
page directs to a non-ssl page
Expected result
if the site has SSL enabled the upgrade wizard should use SSL since it is asking for credentials.

@thabaum - this is an implementation issue rather than a bug in DNN Platform.
Moving forward, would you mind asking questions on dnncommunity.org forums for clarity and education prior to opening GitHub issues?  It is vital to our continued success that issues opened on GitHub are clear, accurate and actionable.  Thanks!

trying to use the forums more... I just feel if you have SSL enabled DNN should use it.  I always accidently miss that it is non-SSL makes me upset, change my password and stuff :) wish this was fixed but I guess I will just talk about it.
I wish there was a setting to make all pages SSL enabled.  I know the file manager is getting redone so I wont go there.
I type in the upgrade url and it gives me a non-SSL page... bugs the hell out of me for years now.  No worries I can go rant about it on the forums :)

@thabaum there is a distinction in DNN between SSL being Enabled and Enforced.  Also, most implementations utilize a CDN or IIS to handle an automatic redirect from HTTP to HTTPS.
You do bring up a good point about being able to manage each page's SSL settings in a more global fashion.  That would make a worthy "issue" in my opinion, but please keep the scope light and succinct so that someone can easily understand the enhancement idea and hopefully submit a pull request for it.
Thanks!

There was an RFC #2808 open since may, lots of discussions/ideas but no contribution came in. This is also something very complex because of different setups, one can have SSL redirect in IIS, others may have SSL termination on a reverse proxy or load balancer, a specific page needs to not be enforced because of some service or iframe, lockout possibility if the certificate fails, needing to install before setting up ssl, etc. It is complex for sure.
Another thing that comes to mind is that the install/upgrade wizard is kinda different than the rest of Dnn pages, it does not go through the same pipeline that would allow Dnn itseft to enforce it and may need to be done only in IIS.
The only way currently I see the upgrade using ssl is to enforce https redirection at the iis level like this https://stackoverflow.com/questions/9823010/how-to-force-https-using-a-web-config-file
But that could not work if the ssl termination is not in IIS and the communication is only encrypted between the outside world and the load balancer and is http internally... Something that is unfortunately common.


Dev environment web server should return index.html for any request

It's unproductive to develop single page apps where a request to a route means the server should return index.html and the page should render based on the route.

This has been fixed here:
https://github.com/ReidWilliams/hello-react/tree/e768f4fb4c77106acc43e41a2707720637c60d39
Needs to be replicated here.


fix(main): Add typescript declarations

Adds support for typescript usage.

Hey, these types looks great, but after reviewing the component type files, I noticed a bunch of the types are inaccurate (could be if they were auto-generated). I am actually almost done writing types as a part of the 5.1.0 update so combining these would cause a lot of conflicts. Expect types to be added in the 5.1.0 update along with the added new features that will be coming in 5.1.0. Thanks!


Port weave network profile/protocol baseline to CHIP

Per Rendezvous TT + Service & Device Management TT Provisioning joint meeting in Aug 17,2020, with broad agreement, we decide to port weave network profile/protocol baseline to CHIP.
Later, we will convert the GAP/improvement we discussed to github ticket and address one by one.

We'll need to see how this fits into the existing CHIP code, given the network profile won't work as is. Are there documents and/or specs we can share with developers?


Ingesting existing data

I merely put the paradisi_ image file into the mytest folder when running the first notebook of the guide, but it still ended up copying the file rather than just keeping it with its original name.

I've just tested it extensively with multiple different files, locally and on cloud. I'm pretty sure it doesn't copy the file. Could you show me how you did it?


Rotational.ElastoBacklash Miscalculation

Reported by JustinKGriffiths on 31 Jan 2008 20:10 UTC
I believe there is a mistake in the Standard Library.  Currently I’m using version 2.2.1 but it is also in the latest release, version 2.2.2.  In the …Rotational.ElastoBacklash model the torque function has a mistake.  The function currently reads as follows,
tau = if b2 > b_min then (if phi_rel > b2 then c*(phi_rel - phi_rel0 - b2)
+ d*w_rel else (if phi_rel < -b2 then c*(phi_rel - phi_rel0 + b2) + d*
w_rel else 0)) else c*(phi_rel - phi_rel0) + d*w_rel;
At first glance this all looks fine but when both the backlash (b2) and phi_rel0 are non-zero then issues arise.  Take for instance if b2 > 0 and phi_rel0 > 0 and phi_rel > b2 then (phi_rel – phi_rel0 – b2) < 0 which causes phi_rel to increase instead decrease.  The same happens on the negative side when phi_rel < -b2 and  phi_rel0 < 0.  I believe the function should read,
tau = if b2 > b_min then (if phi_rel – phi_rel0 > b2 then c*(phi_rel - phi_rel0 - b2)
+ d*w_rel else (if phi_rel – phi_rel0 < -b2 then c*(phi_rel - phi_rel0 + b2) + d*
w_rel else 0)) else c*(phi_rel - phi_rel0) + d*w_rel;
This will remove the discontinuities from the equation.

Migrated-From: https://trac.modelica.org/Modelica/ticket/44

Comment by otter on 7 Feb 2008 20:37 UTC
The reported bug has been fixed in the maintenance version of the Modelica Standard Library 2.2.2.
In the coming version 3.0, component Backlash is completely newly implemented, to fix non-physical effects (e.g. "pushing" torque).

Comment by otter on 7 Feb 2008 20:39 UTC
The fix was performed with 89c81e5d791b58b3a6df3feeaae665ecf5e0555c. In version 3.0, the bug was not present, since already taken care off with the new implementation.


Scanning an invalid QR code continues to connection modal

When scanning an invalid QR code, it takes you to the "Just a moment while we make a secure connection..." modal. It then lags there until the home button appears to get out.
https://images.zenhubusercontent.com/429950091/7ff8dce2-be8f-47b4-9965-83c1d35abcd0/20220224_1639522277.mp4

I checked and this bug seems to be fixed on both Android and iOS


Update Github workflows for php 7.4 up to 8.2

Update the github workflow tun for php 7.4 up to 8.2

This was partially addressed on #5


Updated to better support running docker on Mac OS X hosts

Is this worth putting in release notes? Seems interesting enough to me :)

+1 - I think we normally update release notes when we release - updating as we go actually seems like a better pattern to me though.

Oh, I meant the normal sprintly release notes. There's a process for me to get words in there.

Oh. Well I stand by my statement as well 😄

@damccorm, @jpricket , @stephenmichaelf  - I ended up adding a lot more changes than I intended  getting linux containers to work on Windows. I would greatly appreciate another pass through over this PR. I will remember next time to not try and do multiple things in one PR.


Inconsistency in Fedora wiki page

That page states that there are generally three ways to get the RootFS tarball, but then only two ways are mentioned. That is, unless the mirror in kernel.org is the third way. In that case, the text is confusing.

The wiki page was created by @Biswa96 and I guess he counted mirror.kernel.org as the third way.

I just updated the wiki pages and this page has been removed.

Though you deleted all wiki pages, I've seen that you are now working with downloading distro tarballs :+1:
Do you want to extend that distro list? I've many more in my repo ( see .md file).

You may build Linux tarball in appveyor and deploy those in your repo so that user can download the tar.gz file directly from release.

@Biswa96 Actually I've considered the Win APIs were used for installation. But it doesn't make sense now because most if not all of the tar files provided by various distros have been supported.


comma separated import

There's a very popular Discord add-on for managing signups called Raid-Helper (https://raid-helper.com). This Discord bot allows event managers to export the signup list, but it comes as a comma separated list of names (all one line) instead of one-name-per-line. It'd be great if RaidInviteClassic supported both. Raid Helper has it's own in-game addon, but its far less featured than this one. 👍

Hey, good idea. I already implemented this in v0.3.1 I think. Can you try updating to the latest version and importing a list to try it out?

@malagul Is this issue resolved for you? I assume it is because you didn't reply again, and it's implemented in the current version to use comma, colon and newline characters to separate the names during text import.


Prepare for Spring Cloud Azure 5.10.0 release

Description
Prepare for Spring Cloud Azure 5.10.0 release
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.