Integration stopped working in 2024.2.1

Home Assistant version
Core 2024.2.1
Supervisor 2024.01.1
Operating System 11.5
Front-end 20240207.1
SmartIR version
1.17.9
SmartIR configuration
configuration.yaml
smartir:

media_player:
  - platform: smartir
    name: TV OLED
    unique_id: tv_sala_oled
    device_code: 1042
    controller_data: remote.broadlinkcinema_remote
    power_sensor: media_player.tv_da_sala_4
  - platform: smartir
    name: Monitor Escritorio
    unique_id: monitor_escritorio
    device_code: 1062
    controller_data: remote.rmc4proescritorio

climate:
  - platform: smartir
    name: "Climatizador"
    unique_id: climatizador
    device_code: 1360
    controller_data: remote.broadlinksuite_remote
    temperature_sensor: sensor.suite_temperatura
    humidity_sensor: sensor.suite_umidade
  - platform: smartir
    name: "Ar da Cozinha"
    unique_id: arcozinha
    device_code: 1702
    controller_data: remote.broadlinksala_remote
    temperature_sensor: sensor.temperatura_cozinha
    humidity_sensor: sensor.umidade_cozinha
  - platform: smartir
    name: "Ar da Sala"
    unique_id: arsala
    device_code: 1702
    controller_data: remote.broadlinkcinema_remote
    temperature_sensor: sensor.temperatura_cozinha
    humidity_sensor: sensor.umidade_cozinha
  - platform: smartir
    name: "Ar do Escritório"
    unique_id: arescritorio
    device_code: 1241
    controller_data: remote.rmc4proescritorio
    temperature_sensor: sensor.temperatura_cozinha
    humidity_sensor: sensor.umidade_cozinha

fan:
  - platform: smartir
    name:  Ventilação quarto
    unique_id: ar_do_aquirto
    device_code: 1999
    controller_data: remote.broadlinksuite_remote

Describe the bug
Integration stopped working.
Note: I already downloaded and reinstalled.
I've already restarted the device too. (ha host reboot)
Debug log
2024-02-11 17:17:27.479 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_OSCILLATE was used from smartir, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.OSCILLATE instead, please report it to the author of the 'smartir' custom integration
2024-02-11 17:17:40.980 WARNING (MainThread) [homeassistant.setup] Setup of smartir is taking over 10 seconds.
2024-02-11 17:18:33.420 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: smartir
2024-02-11 17:19:33.530 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: smartir
2024-02-11 17:20:33.613 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: smartir
2024-02-11 17:21:33.686 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: smartir
2024-02-11 17:22:24.228 ERROR (MainThread) [homeassistant.setup] Setup of 'smartir' is taking longer than 300 seconds. Startup will proceed without waiting any longer
2024-02-11 17:22:24.231 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform 'smartir.climate': Unable to set up component.
2024-02-11 17:22:24.232 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform 'smartir.climate': Unable to set up component.
2024-02-11 17:22:24.233 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform 'smartir.climate': Unable to set up component.
2024-02-11 17:22:24.233 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform 'smartir.climate': Unable to set up component.
2024-02-11 17:22:24.234 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform 'smartir.media_player': Unable to set up component.
2024-02-11 17:22:24.235 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform 'smartir.media_player': Unable to set up component.
2024-02-11 17:22:24.235 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform 'smartir.fan': Unable to set up component.

root@core-ssh:~/config/custom_components/smartir# tree | grep -v json
.
├── __init__.py
├── __pycache__
│   ├── __init__.cpython-312.pyc
│   ├── climate.cpython-312.pyc
│   ├── controller.cpython-312.pyc
│   ├── fan.cpython-312.pyc
│   └── media_player.cpython-312.pyc
├── climate.py
├── codes
│   ├── climate
│   ├── fan
│   └── media_player
├── controller.py
├── fan.py
├── media_player.py
└── services.yaml

Additional context

When commenting the line with "smartir:" the application started working again. Like this? 🤌🤌🤌
# smartir:


OM, SM, and GM may have no reference, template, or constant

https://github.com/chrdebru/rml-core/blob/missing-test/shapes/expression_map.ttl
Implements the following:
    # Exactly one rml:template, one rml:constant, one rml:reference,
    # one rml:returnMap, or one rml:functionExecution is required.

We, however, allow no such thing for subject maps and object maps (and arguably graph maps) as well. The iterations are then used to generate blank nodes. Should we remove the mincount?

This construct you mention is to enforce that any of these options is picked (so minCount == 1) and also that you don't put multiple of these options (maxCount == 1).

allow no such thing for subject maps and object maps (and arguably graph maps)

I cannot follow here. Each of these maps must have exactly one of these options right? A subject map must have a template/constant/reference/... right?
You can enforce it more strict in the specific maps though if needed.

Rethinking this issue: is this when you have rml:termType rml:BlankNode without a template?
If that's the only 'exception' to the rule, we should maybe define this restriction:
IF termType == BlankNode
  minCount = 0
ELSE
  minCount = 1

?

Yes, but what if no rml:termType is provided? I'm also thinking about the Gather Maps, and it is difficult (impossible?) to "overwrite" shapes in SHACL. My approach is more: if no rml:template, rml:reference, and rml:constant, then the rml:termType is assumed to be rml:BlankNode. This rule would work with predicate maps as well as the inferred term type blank node violates the rml:termType rr:IRI constraint.

Yes, but what if no rml:termType is provided?

There should be a default which should be used. For SubjectMaps this is IRI. It will be a 'fun' job to actually check this in SHACL shapes...

and it is difficult (impossible?) to "overwrite" shapes in SHACL.

I'm not sure how you can overwrite things I'm afraid... It is purely an AND/OR/XOR story AFAIK. Correct me if I'm wrong.

I would argue that the default when no constant, template, or reference is provided should be blank nodes. That's the only thing that you can generate based on the iteration. Defaults can be "inferred" once you have one of them.

This depends on the final decision of #52


[BugFix][Cherry-Pick] Fix partition prune null predicate error (#17269)

Signed-off-by: Seaven<EMAIL_ADDRESS>What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

run starrocks_fe_unittest


Update extension.js

Updated extension.js for SETTINGS_ARE_TOGGLED_MESSAGE

@harshalkh Howdy! Thanks so much for this!
I haven't forgotten about this! Upon checking it out, I noticed another issue (assuming this is all good, and it's just making me aware of it).
I'm trying to work through that before a merge.

When I run this, I'm seeing some problems with the async arrow function provided to Object.forEach.
E.g., the resultObjs.some check is happening before the items are pushed into it. At least that's what appears to be happening.
I only used async on that so I could easily use await on the const resultObj = await updateMostGranularSetting(...) line.
I'm looking at changing that behavior now.

@harshalkh Since I wasn't able to push changes here (and didn't want to wait), I based some new changes on this, and merged them in.
I'll close this PR.
Since it's during Hacktoberfest, and I definitely want you to get credit for your contribution, if you'll create a pull request that adds yourself to the list of contributors in the README, I will merge that pull request!
See the existing example under Includes contributions from: in the README.md file.
Thanks again!


Fault and Deformation model interfaces + U3 refactoring

Extracted interfaces for fault and deformation model capabilities that the old UCERF3 FM/DM enums now implement. The RuptureSets utility class now works with these interfaces rather than their U3-specific instances.
I also removed the U3-specifc builder methods on FaultSystemRupSet, with their contents moved to U3InversionConfigFactory.
@chrisbc @voj, a couple changes that might impact you:

RupSetScalingRelationship now extends LogicTreeNode in order to facilitate getting it from logic tree branches in factory classes. If you have any instances that aren't also a LogicTreeNode then you'll need to add the additional branch weight method, which can return 0 or NaN if not used in a logic tree branch
Refactored some of the UCERF3-specific FSRS/FSS subclasses to prefix them with 'U3', e.g., U3SlipAlongRuptureSet. If you're still using these, please ween yourself off of them ASAP
Deleted the long-deprecated old wrapper class scratch.UCERF3.InversionTargetMFDs class that was kept for backwards compatibility when we renamed it to U3InversionTargetMFDs

I'll wait to merge until I know how much these changes impact you and I've done some additional tests/cleanup on my end.

@kevinmilner thank for checking, Kevin. It only took me a few minutes to make our repo build again 👍


Use only DATABASE_URL

the Heroku section instructs the user to add code for DATABASE_URL https://www.robinwieruch.de/graphql-apollo-server-tutorial/#graphql-server-postgresql-deployment-heroku
The DATABASE_URL env var is widely used. It would make more sense to specify this from the very beginning instead of three env vars
DATABASE=mydatabase
DATABASE_USER=postgres
DATABASE_PASSWORD=postgres

Make api only use DATABASE_URL.

Good point. Can the local PostgreSQL database be used with a database URL only even though you have set up a superuser for it?

I'm not sure. I use DATABASE_URL in two ways, postgres://localhost:5432/dbname and postgres://username:password@localhost:5432/dbname. If you need to specify the superuser use the latter, otherwise my system accepts my non-root user with the former.

Good to know. I will take this into account for the next edition of the book!


Response code 500 on the LINK Knoxville feed

What is the issue and why is it an issue?
When using the validator on a random feed (LINK Knoxville from systems.csv#L686), I realized that it returns "Sorry, this version is not yet implemented or not detectable !". However,  the filegbfs.json is conform to v2.2 when testing it against the JSON Schema.
It could be a problem for other feeds too.

gbfs.json
Output

Please describe some potential solutions you have considered (even if they aren’t related to GBFS).
I don't have a solution but I did some debugging, if it helps.
The checkAutodiscovery() method in gbfs.js catches this error:
HTTPError: Response code 500 (Internal Server Error)
    at Request.<anonymous> (/Users/fabien/GitHub/MobilityData/gbfs-validator/gbfs-validator/node_modules/got/dist/source/as-promise/index.js:118:42)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {name: 'HTTPError', code: 'ERR_NON_2XX_3XX_RESPONSE', timings: {…}, stack: 'HTTPError: Response code 500 (Internal Server…ions (node:internal/process/task_queues:95:5)', message: 'Response code 500 (Internal Server Error)', …}

But the feed loads correctly in the browser 🤔

Duplicate of https://github.com/MobilityData/gbfs-validator/issues/90


how do you know what language parameter should pass to you when use tesseract?

hi @chrismattmann
i have a question that if the image's content is not english text, it is German text and french text, tesseract need to pass language parameter in its official document introduction, if i don't call method in tika-python for tesseract, how do you know what language parameter should pass to you? how do you automatically recognize it? thanks

see my answer in #292


Set og:* properties for Facebook sharing

The default shared image for Facebook is one of the specific boards. We should add meta properties to point to a more reasonable (logo? Johnny-Five drawing?) suggestion.
Here is Facebook's debugger output for the website:
https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fjohnny-five.io
Not explicitly listed at that link, the preview image must be a minimum of 200x200.

Go for it!

Also, we could pass in a suggested image specific to each example from the J5 programs.json file for the generated example pages.

Preferably they want a 1.91:1 ratio image.  Suggested size is 1200x630.
https://developers.facebook.com/docs/sharing/best-practices#images
There doesn't appear to be anything in the repo already that would be appropriate to use for the og:image property.  Is there a graphic designer that could create one for us as the default?

@isaacdurazo ^^

@pierceray looks good to me, based on my limited understanding of the FB usage.
Is there a way to run the result through that FB debugger link before publishing it? I don't see an option for that. Maybe we could stage it somewhere and test against that before deploying?
The image is the main thing I was looking for here, so I suggest we wait for an appropriate logo, add a commit for that, then push it out.
@rwaldron do you just want the Johnny-Five logo for all pages? Or something different for the other page types: examples, API, etc?

@Resseguie not sure, that's why I pinged @isaacdurazo (he's the lead designer @bocoup)

I haven't found a way to easily stage it somewhere to run it through the debugger.  I'll if I can't find somewhere to do it tonight.
Yes, I would agree about the image, I just didn't have one available to me to add that would be appropriate.

Hey guys, would something like this work?

I think that will work great.  I'll get it integrated tonight.

@Resseguie I Iike the idea of having something different for each section (as long as it's not a ton of work to implement them), specially because the "Examples" page has a board and it's pretty damn cool.
I would say, let's use the one I just posted as the default and give me some time to work on the rest. I should have time early next week (maybe before).

Should we spin up a new issue for section images and just set everything to default for the time being?

@pierceray sounds good to me. This issue would put in the needed meta tags with default. (As your PR does)

Looks like it is good to go now.  Added the og:image and new image file.  Tested it on a temp site and the FB Object Debugger worked as expected.


[LayoutReader] eval result not aligned with readme

Describe
Model I am using (LayoutReader):
Thanks for this nice work!
Guided by the readme description, with 1）the default "4. decoding" code，2）the provided pretraining-model  and 3) the readingbank test-set (~50k), I get mean average bleu about 88.6, not aligned with 98.2 claimed in the readme.
It will be nice to have some hints，thanks!

Hi!
Thanks for your interest in our work! We are sorry to see that you couldn't produce the supposed results as we expected. All results reported in our paper are accurate and the same as what the experiment told us. We report the numbers carefully and double check them before our submission. So we assume there are likely to be some issues as to the running environment or argument setting. Please check details in your experiments and see whether the problem continues.


feat(Markdown): Add onAnchorClick prop

Overview

Adds an onAnchorClick prop to the Markdown component for passing down to <a/> tags.

PR Checklist

[ ] Related to designs:
[x] Related to JIRA ticket: REACH-453
[x] I have run this code to verify it works
[x] This PR includes unit tests for the code change

This seems reasonable for now!
Something to think about long term: what happens when people want other onClick handlers for our overrides? Buttons, maybe? I can't think of anything but maybe something to back-of-mind ruminate on...

Perhaps an onClickHandlers prop to group them, similar to overrides?
onClickHandlers: {
  onAnchorClick,
  onButtonClick,
  ...
}

📬Published Alpha Packages:@codecademy/gamut-illustrations@0.2.3-alpha.4c7247.0@codecademy/gamut-labs@7.4.4-alpha.4c7247.0@codecademy/gamut@19.3.4-alpha.4c7247.0<EMAIL_ADDRESS>
Yeah maybe! Even more generic, a pattern some libraries use is exporting the base object (in this case the default overrides) and letting people merge(overrides,otherStuff).

🚀 Styleguide deploy preview ready!https://5fd7b35731424701153cb53a--gamut-preview.netlify.appDeploy Logs


Update setup.cfg for 6.1.3 release

Because this is a repackaging of cqlsh from the official Cassandra repo, only issues / PRs related to PyPI packaging should be opened against this repo.
If you would like to contribute to cqlsh itself, find out more information here.
Otherwise, if your PR is still appropriate for this repo, then replace this warning with your PR description. And thanks for improving cqlsh!

🎉


[dart2wasm] LateInitializationError in Flutter app

Originally reported in https://github.com/flutter/flutter/issues/140110. Moving it here to keep track of all dart2wasm bugs in one place.
Clone https://github.com/tylandercasper/getx_badcompile and run flutter build web --wasm in example directory. dart2wasm crashes with:
Unhandled exception:
LateInitializationError: Field 'currentLocal' has not been initialized.
#0      CodeGenerator.visitVariableDeclaration (package:dart2wasm/code_generator.dart)
#1      VariableDeclaration.accept (package:kernel/ast.dart:10748)
#2      CodeGenerator.visitStatement (package:dart2wasm/code_generator.dart:889)
#3      CodeGenerator.visitLet (package:dart2wasm/code_generator.dart:1709)
#4      Let.accept1 (package:kernel/ast.dart:8725)
#5      CodeGenerator.wrap (package:dart2wasm/code_generator.dart:878)
#6      CodeGenerator.visitEqualsCall (package:dart2wasm/code_generator.dart:1954)
#7      EqualsCall.accept1 (package:kernel/ast.dart:6302)
#8      CodeGenerator.wrap (package:dart2wasm/code_generator.dart:878)
#9      CodeGenerator.branchIf (package:dart2wasm/code_generator.dart:1387)
#10     CodeGenerator.branchIf (package:dart2wasm/code_generator.dart:1384)
#11     AsyncCodeGenerator.jumpToTarget (package:dart2wasm/async.dart:829)
#12     AsyncCodeGenerator.visitWhileStatement (package:dart2wasm/async.dart:1229)
#13     WhileStatement.accept (package:kernel/ast.dart:9526)
#14     CodeGenerator.visitStatement (package:dart2wasm/code_generator.dart:889)
#15     CodeGenerator.visitBlock (package:dart2wasm/code_generator.dart:1011)
#16     Block.accept (package:kernel/ast.dart:9199)
#17     CodeGenerator.visitStatement (package:dart2wasm/code_generator.dart:889)
#18     AsyncCodeGenerator._generateInner (package:dart2wasm/async.dart:770)
#19     AsyncCodeGenerator._generateBodies (package:dart2wasm/async.dart:596)
#20     AsyncCodeGenerator.generate (package:dart2wasm/async.dart:542)
#21     Translator.translate (package:dart2wasm/translator.dart:349)
#22     compileToModule (package:dart2wasm/compile.dart:151)
<asynchronous suspension>
#23     main (package:dart2wasm/dart2wasm.dart:144)
<asynchronous suspension>
#24     main (file:///b/s/w/ir/x/w/sdk/pkg/dart2wasm/bin/dart2wasm.dart:7)
<asynchronous suspension>

It should be easy to fix but I'm unable to figure out how to build this with a local dart2wasm. With flutter build web --wasm --verbose I see this invocation of dart2wasm:
/usr/local/google/home/omersa/dart/flutter/bin/cache/dart-sdk/bin/dartaotruntime \
    --disable-dart-dev \
    /usr/local/google/home/omersa/dart/flutter/bin/cache/dart-sdk/bin/snapshots/dart2wasm_product.snapshot \
    --packages=.dart_tool/package_config.json \
    --dart-sdk=/usr/local/google/home/omersa/dart/flutter/bin/cache/dart-sdk \
    --platform=/usr/local/google/home/omersa/dart/flutter/bin/cache/flutter_web_sdk/kernel/dart2wasm_platform.dill \
    -Ddart.vm.product=true \
    -DFLUTTER_WEB_AUTO_DETECT=true \
    -DFLUTTER_WEB_CANVASKIT_URL=https://www.gstatic.com/flutter-canvaskit/6f499ecea6570f1b7df5c7813ef9e4456d56c426/ \
    --depfile=/usr/local/google/home/omersa/dart/getx_badcompile/example/.dart_tool/flutter_build/af0191ce039bb4770bc6a3450c7f725f/dart2wasm.d \
    /usr/local/google/home/omersa/dart/getx_badcompile/example/.dart_tool/flutter_build/af0191ce039bb4770bc6a3450c7f725f/main.dart \
    /usr/local/google/home/omersa/dart/getx_badcompile/example/.dart_tool/flutter_build/af0191ce039bb4770bc6a3450c7f725f/main.dart.unopt.wasm

To run this command with a local dart2wasm:

Remove --disable-dart-dev, it's a dartaotruntime argument that we don't support.
Similarly remove the snapshot file argument.

When I remove the platform argument:
/usr/local/google/home/omersa/dart/sdk/sdk/sdk/bin/dart2wasm \
    --packages=.dart_tool/package_config.json \
    --dart-sdk=/usr/local/google/home/omersa/dart/flutter/bin/cache/dart-sdk \
    -Ddart.vm.product=true \
    -DFLUTTER_WEB_AUTO_DETECT=true \
    -DFLUTTER_WEB_CANVASKIT_URL=https://www.gstatic.com/flutter-canvaskit/6f499ecea6570f1b7df5c7813ef9e4456d56c426/ \
    --depfile=/usr/local/google/home/omersa/dart/getx_badcompile/example/.dart_tool/flutter_build/af0191ce039bb4770bc6a3450c7f725f/dart2wasm.d \
    /usr/local/google/home/omersa/dart/getx_badcompile/example/.dart_tool/flutter_build/af0191ce039bb4770bc6a3450c7f725f/main.dart \
    /usr/local/google/home/omersa/dart/getx_badcompile/example/.dart_tool/flutter_build/af0191ce039bb4770bc6a3450c7f725f/main.dart.unopt.wasm

I get hundreds of undefined method, type etc. errors.
I also tried to remove --packages, --dart-sdk, and --depfile arguments individually and all at once, but got the same erorrs.

@mraleph showed me how to build this with a local SDK. We need to rebuild the dart2wasm_platform.dill with the same local SDK as the SDK we want to build the project with. The steps for that:

Build SDK.
In engine/src/flutter/prebuilts/linux-x64, move the dart-sdk directory to somewhere (or remove it), and symlink the local build $SDK_CHECKOUT/out/ReleaseX64/dart-sdk with the same name.
In engine/src, run flutter/tools/gn --wasm; ninja -C out/wasm_debug -v flutter_web_sdk/kernel/dart2wasm_platform.dill.
The new platform file built with the local SDK will be in out/wasm_debug/flutter_web_sdk/kernel/dart2wasm_platform.dill.

Pass the path to the new platform file as --platform=....

Smaller repro:
class PageSettings {
  String name;

  PageSettings(this.name);
}

class GetDelegate {
  PageSettings? get pageSettings => PageSettings("a");

  Future<void> popModeUntil(String fullRoute) async {
    while (pageSettings?.name != fullRoute) {
      await null;
    }
  }
}

void main() async {
  await GetDelegate().popModeUntil("");
}

Output:
Unhandled exception:
LateInitializationError: Field 'currentLocal' has not been initialized.
#0      CodeGenerator.visitVariableDeclaration (package:dart2wasm/code_generator.dart)
#1      VariableDeclaration.accept (package:kernel/ast.dart:10744)
#2      CodeGenerator.visitStatement (package:dart2wasm/code_generator.dart:892)
#3      CodeGenerator.visitLet (package:dart2wasm/code_generator.dart:1718)
#4      Let.accept1 (package:kernel/ast.dart:8721)
#5      CodeGenerator.wrap (package:dart2wasm/code_generator.dart:881)
#6      CodeGenerator.visitEqualsCall (package:dart2wasm/code_generator.dart:1963)
#7      EqualsCall.accept1 (package:kernel/ast.dart:6298)
#8      CodeGenerator.wrap (package:dart2wasm/code_generator.dart:881)
#9      CodeGenerator.branchIf (package:dart2wasm/code_generator.dart:1396)
#10     AsyncCodeGenerator.jumpToTarget (package:dart2wasm/async.dart:855)
#11     AsyncCodeGenerator.visitWhileStatement (package:dart2wasm/async.dart:1255)
#12     WhileStatement.accept (package:kernel/ast.dart:9522)
#13     CodeGenerator.visitStatement (package:dart2wasm/code_generator.dart:892)
#14     CodeGenerator.visitBlock (package:dart2wasm/code_generator.dart:1014)
#15     Block.accept (package:kernel/ast.dart:9195)
#16     CodeGenerator.visitStatement (package:dart2wasm/code_generator.dart:892)
#17     AsyncCodeGenerator._generateInner (package:dart2wasm/async.dart:778)
#18     AsyncCodeGenerator._generateBodies (package:dart2wasm/async.dart:597)
#19     AsyncCodeGenerator.generate (package:dart2wasm/async.dart:542)
#20     Translator.translate (package:dart2wasm/translator.dart:352)
#21     compileToModule (package:dart2wasm/compile.dart:151)
<asynchronous suspension>
#22     generateWasm (package:dart2wasm/generate_wasm.dart:21)
<asynchronous suspension>
#23     main (file:///usr/local/google/home/omersa/dart/sdk/sdk/pkg/dart2wasm/bin/dart2wasm.dart:10)
<asynchronous suspension>


Test/Bug: the first one in utterance was indication for logic

Selection of a list element, the [first one] was meant as the indication to include the first line of text (name, suggestions time) in the utterance:
Sure, I'll continue with [Name], [email adress].
Got it. I'll move forward with [Name], [email adress].
OK. I'll include [Name], [email adress]. as attendee.

fixed by https://github.com/microsoft/botframework-skills/pull/393


Override compiler version

How can I override, which rustc version or branch (stable/beta/nightly) to use?
Also it would be cool, if crate2nix would check for rust-toolchain files which are used by rustup to pin a specific compiler version and or branch for a repository.

You can override the rust compiler by overlays to the used nixpkgs.
I will investigate in making this easy...

Would be cool to mention this in the readme with an example.
I tried adding the mozilla overlay but I can't figure out, where do override the used compiler channel

I am using the following pattern in an overlay:
self: super: {
   rustNightlyChannel = mozilla.rustChannelOf { date = "..."; channel = "..."; };
   rustNightly = self.rustNightlyChannel.rust;
   myBuildRustCrate = super.buildRustCrate.override { rustc = self.rustNightly; };
   myPkg = (self.callPackage ./Crate.nix { buildRustCrate = myBuildRustCrate; }).rootCrate.build;
}

(adopted from my actual, more complicated, version)

Thank you. I also found this one yesterday but I didn't come around to test it, yet: https://github.com/jD91mZM2/xidlehook/blob/master/default.nix

@kolloch @vbrandl Can this be closed?

By the way, you do not have to use an overlay, buildRustCrate allows you to specify a Rust toolchain through the rust argument. See here for an example that builds a crate using nightly:
https://github.com/finalfusion/nix-packages/blob/cf8a4140d2359fb512608bde3c88ba410b5d94fb/pkgs/python-modules/finalfusion/default.nix

I wasn't able to test yet because I didn't need it anymore (since 1.39.0 landed in the unstable channel, I don't need a nightly compiler for async/await). This can be closed but I think it would be nice to have a documented example in the README that shows how to use the mozilla overlay

@andir @vbrandl @danielk I added documentation for doing this "globally" here:
https://github.com/kolloch/crate2nix#choosing-a-rust-version
I discovered one caveat: I had to use "rust" (without the c suffix) for "rustc" with a recent version of the overlay because otherwise rustc wouldn't find the std sources.
Doing this globally is often what you want, I guess. Build all your stuff with the same rust compiler. But the individual approach also has merrit. Maybe you want to add that to the documentation? You would be welcome.
@danielk for making buildRustCrate more directly overridable, see https://github.com/kolloch/crate2nix/issues/77. Tell me what you think! For "pkgs" it is not the right tool, though, since you also want to override it for all dependencies, correct?

I will close this issue for now but will gladly accept documentation fixes/extensions.


Fix sniff tests to account for changing spacy models

Amalgamation of fixes from https://github.com/allenai/allennlp/pull/3468 and https://github.com/allenai/allennlp/pull/3432.
We weren't able to simply swap in a simpler tokenizer because these tests rely on a pos tagger. Spacy is probably a sane default for that according to @DeNeutoy.
Version details for testing locally:

(allennlp-hub) brendanr.local ➜  allennlp-hub git:(fix_sniff) ✗ ipython
impPython 3.6.9 |Anaconda, Inc.| (default, Jul 30 2019, 13:42:17)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.9.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import spacy

In [2]: spacy.__version__
Out[2]: '2.2.2'
(allennlp-hub) brendanr.local ➜  allennlp-hub git:(fix_sniff) ✗ python -m spacy validate
✔ Loaded compatibility table

====================== Installed models (spaCy v2.2.2) ======================
ℹ spaCy installation:
/Users/brendanr/anaconda3/envs/allennlp-hub/lib/python3.6/site-packages/spacy

TYPE      NAME             MODEL            VERSION
package   en-core-web-sm   en_core_web_sm   2.2.5   ✔

Thanks


Needs Guidance on how to do this when using Microsoft.Identity.Web NuGet package

At the very least, the video explains the querystring parameter that is causing the unnecessary consent prompt to appear, but the fix shown isn't useful unless a developer is working with Java and is working with the bare metal for building up a URL.
I'm using the Microsoft.Identity.Web NuGet package to make all of these headaches go away, so where am I supposed to tell this middleware NOT to put in that parameter on the URL?
And if this is not a suggested practice, then why is it on by default?

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

ID: 27339f6f-c63d-d2cc-ec02-8727b5587bf0
Version Independent ID: 8edacd13-bbd1-cfc7-e686-7ca7bf4cb2ad
Content: Unexpected consent prompt when signing in to an application - Azure AD
Content Source: articles/active-directory/manage-apps/application-sign-in-unexpected-user-consent-prompt.md
Service: active-directory
Sub-service: app-mgmt
GitHub Login: @davidmu1
Microsoft Alias: davidmu

I realized that this wasn't the middleware being set up by default to do this. It was another cause.
As it turned out, I had my middleware configured to request additional scopes to consent and some permissions that weren't needed for consent were there.


Update fields for personalisation in assignment templates

Fix for some personalisation for assignment templates

We may as well bump and review the behaviour for https://github.com/communitiesuk/funding-service-design-notification/pull/258#issuecomment-2348390726 here, I'll push a commit when the release has gone through


Cloning the repo has huge space requirements.

I cloned the repo last year for the interspeech 2020 version of the dataset. Now that I'm cloning again for the Iatest version, on a new machine, I'm not able to complete the clone. I've gotten insufficient disk space errors twice already. I'm cloning onto an empty 1TB nvme drive.

I went and bought a 2TB SSD and the clone finished at 1.8TB. There's a recent issue open stating that the dataset is around 300GB. What am I missing?

When I clone repository, datasets (16k) is around 300GB, datasets_fullband (48k) is around 600GB.
.git takes another 900~GB for tracking. So I think it's OK.

Is there a way to create the dataset so that it contains less files? I'm using it for uni coursework and we don't need to train on full datasets.

Is there a way to create the dataset so that it contains less files? I'm using it for uni coursework and we don't need to train on full datasets.

I just found this for anyone wondering the same thing. https://github.com/microsoft/MS-SNSD

Please use this script with SAS_URL https://github.com/microsoft/DNS-Challenge/blob/master/dns_challenge_data_downloader.py

Is there a way to create the dataset so that it contains less files? I'm using it for uni coursework and we don't need to train on full datasets.

I just found this for anyone wondering the same thing. https://github.com/microsoft/M

Is there a way to create the dataset so that it contains less files? I'm using it for uni coursework and we don't need to train on full datasets.

I just found this for anyone wondering the same thing. https://github.com/microsoft/MS-SNSD

You are my god! thank u !!

Please use this script with SAS_URL https://github.com/microsoft/DNS-Challenge/blob/master/dns_challenge_data_downloader.py

I don't have the SAS URL. I emailed<EMAIL_ADDRESS>on March 18th and never got a response.

git clone   --depth 1  https://github.com/microsoft/DNS-Challenge.git

@Rodolfo-S we are removing all audio data from this repo and will host it elsewhere. This way, this repo will not require LFS and we will update the download scripts so you can pull the data (all or part of it) from the hosting location.

Is there a way to create the dataset so that it contains less files? I'm using it for uni coursework and we don't need to train on full datasets.

@jackhwalters
I use the following method to get less files(eg: datasets/noise)

mkdir DNS-Challenge
cd DNS-Challenge
git init
git remote add origin https://github.com/microsoft/DNS-Challenge.git
git lfs install --skip-smudge
git fetch
git pull origin master
git lfs install
git lfs pull --include="datasets/noise"

you can replace “datasets/noise” to get other files or dir

ok folks this is a non-issue now. I've removed all datasets from git so LFS is no longer required and you need at most 900GB to download the data (829GB, actually) which is 1/2 of the old git repo size.


Condition is true wrongly?

Godot version
v3.6.beta1.official [632a544c6]
System information
w10 64
Issue description
The length of the vector is not greater than 0.1, but Godot indicates that it is.
Why does Godot print "hola" if the length of the vector is not greater than 0.1?

Steps to reproduce
Play the project
Minimal reproduction project
testCuerposKinematic.zip

This is because of floating point precision errors. You cant assume that 0.1 == 0.1 in computations, especially not as the result of multiple operations like length() does.
See https://0.30000000000000004.com/
For this case, you should add an epsilon, or invert your logic.


WIP: New module for serialisation to RDF

Description:
Added a new module for serialisation an OTEAPI pipeline to RDF. The RDF produced by this module is much more readable and easier to work with compared to tripper.convert().
Planned tasks (some may be moved to new PRs):

[x] Implement serialisation to RDF using a JSON-LD context.
[x] Implement loading serialised RDF back to a dict representation.
[ ] Check that save_dataset() works with the fuseki backend -- the fuseki backend must be fixed to handle (unescaped) embedded quotes.
[x] Check that load_dataset() works with the fuseki backend -- implemented load_dataset_sparql().
[ ] Implement function that parses a YAML file to a dict-representation that can be serialised to RDF.
[ ] Implement converter from OpenModel YAML format to new YAML format.
[ ] Add documentation.

Type of change:

[ ] Bug fix.
[x] New feature.
[ ] Documentation update.

Checklist for the reviewer:

This checklist should be used as a help for the reviewer.

[ ] Is the change limited to one issue?
[ ] Does this PR close the issue?
[ ] Is the code easy to read and understand, including clearly named variables?
[ ] Do all new feature have an accompanying new test?
[ ] Has the documentation been updated as necessary?

Closing. Moved to tripper


Translation don't work

...or where do I change it? Swedish .qt file is present, but it don't translate.
SFOS v1.1.4
WHT v1.0.4

Oh my bad. I forgot to include swedish translation to the update (that's in QA at the moment). I'll have to include it next time. Sorry.
https://www.transifex.com/projects/p/working-hours-tracker/

Ok, I see.
Is there a reason for not implementing general language support? Because that way, new translators could test there translations by adding there own .qm file.

Hmm. How would that work?
I don't know what general language support means.

Well, I'm not a programmer so I can't give instructions, but I've translated several apps where I can just put my qm file in the app translation folder, and it will work out of the box.
ContactInfo is one of my latest translations where it worked, if that would be helpful.

Ok

Still no Swedish translation in v. 1.0.6 ?

Included Swedish translation into 1.0.7. Now in openrepos

Thanks


analyzer/ipc: always use fork start method; fixes crash on macOS

As of Python 3.8 the spawn start method is the default on macOS, but we currently don't support it, so ViewSB was crashing on macOS with Python 3.8. We should probably switch to using the spawn method later on (see #44), but this fixes the crash for now.

Superseded by #46.


about 'v-if' in 'v-repeat'

..........v-repeat="name" v-if="$value"  ....
'v-if' is not working ,if 'v-if' be used in 'v-repeat' (version:v0.12.16)

Use development and you will see a warning that tells you don't do this.


fix(esl-utils): fix unwrap method signature types

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Adds StorageInitialized health check

Description
This pull request introduces a new health check for storage initialization and includes related unit tests. Additionally, it updates project files to support these changes.
New Features:

src/Microsoft.Health.Fhir.Api/Features/Health/StorageInitializedHealthCheck.cs: Added a new health check class StorageInitializedHealthCheck to monitor the initialization status of storage.

Unit Tests:

src/Microsoft.Health.Fhir.Shared.Api.UnitTests/Features/Health/StorageInitializedHealthCheckTests.cs: Added unit tests for the StorageInitializedHealthCheck class to verify its behavior under different conditions.

Project File Updates:

src/Microsoft.Health.Fhir.Api.UnitTests/Microsoft.Health.Fhir.R4.Api.UnitTests.csproj: Added a conditional package reference for Microsoft.Extensions.TimeProvider.Testing when the target framework is not net6.0.
src/Microsoft.Health.Fhir.Shared.Api.UnitTests/Microsoft.Health.Fhir.Shared.Api.UnitTests.projitems: Included the new test file StorageInitializedHealthCheckTests.cs and removed an unused folder reference. [1] [2]

Dependency Injection:

src/Microsoft.Health.Fhir.Shared.Api/Modules/FhirModule.cs: Registered StorageInitializedHealthCheck as a singleton service and added it to the health checks. [1] [2]

Related issues
Addresses AB#130097
Testing
Describe how this change was tested.
FHIR Team Checklist

Update the title of the PR to be succinct and less than 65 characters
Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
[ ] CI is green before merge
Review squash-merge requirements

Semver Change (docs)
Patch

/azp run

/azp run

/azp run


Prevent extendedTimeOut from overriding the timeOut

This PR is intended to solve #314.
It seems to be working properly for me, although I have to admit that I haven't tested it for all the different options.
Changes:

If intervalId != null then there’s a scheduled timeOut interval.
If registeredDelay == true there’s a scheduled extendedTimeOut interval.
The extendedTimeOut interval checks if intervalId == null before hiding the toast, if it isn’t, the toast isn’t hidden.
The timeOut timer checks if registeredDelayed == true before hiding the toast, if it isn’t, the toast isn’t hidden. (prevents the former timeOut interval to override a extendedTimeOut interval)
The stickAround function no longer clears the timeOut interval, but the function checks for :hover before hiding.

New behaviour:
The toast isn't hidden if the added extendedTimeOut timer ends before the former timeOut timer.

:+1:

@tonyjmnz are you going to resolve conflicts and merge this fix?

I'd like to see it merged, but that's up to the project owners.

We've been pretty busy lately and working towards v3. So it might be a bit til we can get bandwidth to test these.
But what would help is you adding tests. Any change we make has to have a pass and fail test for it to keep the library's integrity

Sounds reasonable. I'll try to add them soon.

@tonyjmnz - any update here?

No update; PR is against incorrect branch.


fix duplicate money mult postgres install step

Whats new

Removes duplicate postgres install step add_money_mult

#2 Related issue

Sorry, I wasn't getting notifications for this repo :(

Ah, wait, I merged this but I shouldn't have, for the same reasons I explained here: https://github.com/ash-project/ash_money/pull/5
Can you report the issue that caused you to make this PR? For now I'm going to revert it.


pythonPackages.watchdog 2.0.0 is broken on darwin

Describe the bug
963299d8fc7afb7f0401b9e547b21236deab8bbc upgraded pythonPackages.watchdog to 2.0.0, but this version is broken on darwin:
...
creating build/temp.macosx-10.6-x86_64-3.8
creating build/temp.macosx-10.6-x86_64-3.8/src
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -DWATCHDOG_VERSION_STRING="2.0.0" -DWATCHDOG_VERSION_MAJOR=2 -DWATCHDOG_VERSION_MINOR=0 -DWATCHDOG_VERSION_BUILD=0 -I/nix/store/5vn5f6slfg1nw8q0bhapd3vgk9j7559i-python3-3.8.7/include/python3.8 -c src/watchdog_fsevents.c -o build/temp.macosx-10.6-x86_64-3.8/src/watchdog_fsevents.o -std=c99 -pedantic -Wall -Wextra -fPIC -Wno-nullability-completeness -Wno-nullability-extension -Wno-newline-eof -Wno-error=unused-command-line-argument
clang-7: warning: argument unused during compilation: '-fno-strict-overflow' [-Wunused-command-line-argument]
src/watchdog_fsevents.c:191:25: error: use of undeclared identifier 'kFSEventStreamEventFlagItemCloned'
FLAG_PROPERTY(IsCloned, kFSEventStreamEventFlagItemCloned)
                        ^
src/watchdog_fsevents.c:404:56: error: use of undeclared identifier 'kFSEventStreamEventExtendedDataPathKey'
        cf_path = CFDictionaryGetValue(path_info_dict, kFSEventStreamEventExtendedDataPathKey);
                                                       ^
src/watchdog_fsevents.c:405:57: error: use of undeclared identifier 'kFSEventStreamEventExtendedFileIDKey'
        cf_inode = CFDictionaryGetValue(path_info_dict, kFSEventStreamEventExtendedFileIDKey);
                                                        ^
src/watchdog_fsevents.c:585:40: error: use of undeclared identifier 'kFSEventStreamCreateFlagUseExtendedData'
                                     | kFSEventStreamCreateFlagUseExtendedData
                                       ^
4 errors generated.
error: command 'clang' failed with exit status 1

It appears this is because nixpkgs' macOS SDK is 10.12, but the symbols that cause problems in 2.0.0 are only available in 10.13+:
https://developer.apple.com/documentation/coreservices/kfseventstreameventextendeddatapathkey

Issue regarding newer SDK https://github.com/NixOS/nixpkgs/issues/101229.

I'm also seeing watchdog as a blocker for installing some packages.
e.g., installing was-sam-cli is broken:
% nix-env -i aws-sam-cli --show-trace
installing 'aws-sam-cli-1.23.0'
error: while evaluating the attribute 'drvPath' at /nix/store/39lgkp36x5qqpbi6rjcwg85lrc791ymc-nixpkgs-21.05pre287067.0d337eb6b77/nixpkgs/lib/customisation.nix:163:7:
while evaluating the attribute 'propagatedBuildInputs' of the derivation 'aws-sam-cli-1.23.0' at /nix/store/39lgkp36x5qqpbi6rjcwg85lrc791ymc-nixpkgs-21.05pre287067.0d337eb6b77/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:201:11:
while evaluating the attribute 'out.outPath' at /nix/store/39lgkp36x5qqpbi6rjcwg85lrc791ymc-nixpkgs-21.05pre287067.0d337eb6b77/nixpkgs/lib/customisation.nix:156:13:
while evaluating the attribute 'handled' at /nix/store/39lgkp36x5qqpbi6rjcwg85lrc791ymc-nixpkgs-21.05pre287067.0d337eb6b77/nixpkgs/pkgs/stdenv/generic/check-meta.nix:301:7:
while evaluating 'handleEvalIssue' at /nix/store/39lgkp36x5qqpbi6rjcwg85lrc791ymc-nixpkgs-21.05pre287067.0d337eb6b77/nixpkgs/pkgs/stdenv/generic/check-meta.nix:188:38, called from /nix/store/39lgkp36x5qqpbi6rjcwg85lrc791ymc-nixpkgs-21.05pre287067.0d337eb6b77/nixpkgs/pkgs/stdenv/generic/check-meta.nix:302:14:
Package ‘python3.8-watchdog-2.0.3’ in /nix/store/39lgkp36x5qqpbi6rjcwg85lrc791ymc-nixpkgs-21.05pre287067.0d337eb6b77/nixpkgs/pkgs/development/python-modules/watchdog/default.nix:42 is marked as broken, refusing to evaluate.

a) To temporarily allow broken packages, you can use an environment variable
   for a single invocation of the nix tools.

     $ export NIXPKGS_ALLOW_BROKEN=1

b) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Any work-around or fix? @lo1tuma, @cillianderoiste.
 % nix-shell -p nix-info --run "nix-info -m"
these paths will be fetched (1.46 MiB download, 7.88 MiB unpacked):
  /nix/store/3kz8p0rh7h260ky00ysjsg7q07jn41i2-bash-interactive-4.4-p23-dev
  /nix/store/6v47rygwaahny2wsmn9avnczf0sd2dn3-DarwinTools-1
  /nix/store/8c94id8pana0v7wq5ipvam6sfjwg8w1w-bash-interactive-4.4-p23-doc
  /nix/store/ff1d4zkny91w0cg8jdzfm6rlvcmpldwf-bash-interactive-4.4-p23-info
  /nix/store/gqvdmb1q5llvhccqm8ap7fxidhxfh67b-bash-interactive-4.4-p23-man
  /nix/store/i8dxjfdkf4ipnbnqr7ws4q4hjqxmiszq-bash-interactive-4.4-p23
  /nix/store/mcj5lk0cqds210nnspppynfwxnqf9ilw-readline-7.0p5
  /nix/store/sbazpkxvzplf2yfxcvq7q0f1v6qmfiva-nix-info
copying path '/nix/store/8c94id8pana0v7wq5ipvam6sfjwg8w1w-bash-interactive-4.4-p23-doc' from 'https://cache.nixos.org'...
copying path '/nix/store/6v47rygwaahny2wsmn9avnczf0sd2dn3-DarwinTools-1' from 'https://cache.nixos.org'...
copying path '/nix/store/ff1d4zkny91w0cg8jdzfm6rlvcmpldwf-bash-interactive-4.4-p23-info' from 'https://cache.nixos.org'...
copying path '/nix/store/gqvdmb1q5llvhccqm8ap7fxidhxfh67b-bash-interactive-4.4-p23-man' from 'https://cache.nixos.org'...
copying path '/nix/store/sbazpkxvzplf2yfxcvq7q0f1v6qmfiva-nix-info' from 'https://cache.nixos.org'...
copying path '/nix/store/mcj5lk0cqds210nnspppynfwxnqf9ilw-readline-7.0p5' from 'https://cache.nixos.org'...
copying path '/nix/store/i8dxjfdkf4ipnbnqr7ws4q4hjqxmiszq-bash-interactive-4.4-p23' from 'https://cache.nixos.org'...
copying path '/nix/store/3kz8p0rh7h260ky00ysjsg7q07jn41i2-bash-interactive-4.4-p23-dev' from 'https://cache.nixos.org'...
 - system: `"x86_64-darwin"`
 - host os: `Darwin 20.3.0, macOS 10.16`
 - multi-user?: `no`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.3.10`
 - channels(ldeck): `"nixpkgs-21.05pre287067.0d337eb6b77"`
 - nixpkgs: `/Users/ldeck/.nix-defexpr/channels/nixpkgs`

Still happens with<EMAIL_ADDRESS>error: Package ‘python3.8-watchdog-2.1.1’ in /nix/store/p6wjywj33a1nj7lnbsb43kar52d6dmvy-nixpkgs-src/pkgs/development/python-modules/watchdog/default.nix:42 is marked as broken, refusing to evaluate.

a) To temporarily allow broken packages, you can use an environment variable
   for a single invocation of the nix tools.

     $ export NIXPKGS_ALLOW_BROKEN=1

b) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

(use '--show-trace' to show detailed location information)
make: *** [nix-shell] Error 1

Yeah, unfortunately, I think nothing is going to change on this issue until someone has time to upgrade the macOS SDK (https://github.com/NixOS/nixpkgs/issues/101229)

That's happening at https://github.com/NixOS/nixpkgs/pull/121055 as part of https://opencollective.com/nix-macos

What if the package uses sdk_11 for now?

It needs https://developer.apple.com/documentation/coreservices/1455361-fseventstreameventflags/kfseventstreameventflagitemcloned, so maybe fine.

Talking to @LnL7, this doesn't seem so simple. The 11 SDK is only available through the Aarch64 stdenv IIUC. So maybe this package doesn't need to be marked broken for Aarch64 Darwin, could someone using native Nix on an M1 mac confirm this?
Making it available on x86_64 properly would entail as much work as bumping the SDK to 10.13 does because we have as much as possible depend on the Apple source releases rather than the SDK. So I don't think this'd be an easy workaround.
@thefloweringash would be better able to judge how practical the idea is though.

Here's what I tried, from a checkout of master:
> NIXPKGS_ALLOW_BROKEN=1 nix-build --no-out-link -E 'let pkgs = import ./. {}; apple_sdk_11_0 = pkgs.callPackage pkgs/os-specific/darwin/apple-sdk-11.0 {}; in pkgs.python3Packages.watchdog.override {inherit (apple_sdk_11_0.frameworks) CoreServices; }'
The following paths did not match any rewrite rule
  /usr/lib/libobjc.A.dylib

Errors occurred during rewrite of /nix/store/30f0jc58f542qlli3zachx2ncx17jgfa-apple-framework-CoreFoundation-11.0.0/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation.tbd
Rewrite config:
Exact mappings:
Errors occurred during rewrite of /nix/store/6dax4h9wc21h0a2h5bmqwkpyr4sgxx25-apple-framework-CoreFoundation-11.0.0/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation.tbd
Rewrite config:
Exact mappings:
Prefix mappings:
  - /System/Library/Frameworks/CoreFoundation.framework/ -> /nix/store/6dax4h9wc21h0a2h5bmqwkpyr4sgxx25-apple-framework-CoreFoundation-11.0.0/Library/Frameworks/CoreFoundation.framework/
Required prefix: /nix/store
Check existence of resulting paths: yes

Prefix mappings:
  - /System/Library/Frameworks/CoreFoundation.framework/ -> /nix/store/30f0jc58f542qlli3zachx2ncx17jgfa-apple-framework-CoreFoundation-11.0.0/Library/Frameworks/CoreFoundation.framework/
Required prefix: /nix/store
Check existence of resulting paths: yes

The following paths did not match any rewrite rule
  /usr/lib/libobjc.A.dylib
The following paths did not match any rewrite rule
  /usr/lib/libobjc.A.dylib
libc++abi.dylib: terminating with uncaught exception of type rewrite_errors: Rewriting failed
libc++abi.dylib: terminating with uncaught exception of type rewrite_errors: Rewriting failed
/nix/store/vnazyva3nawmvmhsxl8d2698wqg3743l-stdenv-darwin/setup: line 1329: 4818
3 Abort trap: 6           rewrite-tbd -p /System/Library/Frameworks/CoreFoundation.framework/:$out/Library/Frameworks/CoreFoundation.framework/ -r /nix/store "$tbd"
/nix/store/vnazyva3nawmvmhsxl8d2698wqg3743l-stdenv-darwin/setup: line 1329: 4818
2 Abort trap: 6           rewrite-tbd -p /System/Library/Frameworks/CoreFoundation.framework/:$out/Library/Frameworks/CoreFoundation.framework/ -r /nix/store "$tbd"
post-installation fixup
builder for '/nix/store/y8kvzqx49krhb8mvas81y5kb8d4m5fpq-apple-framework-CoreFoundation-11.0.0.drv' failed with exit code 134

I suspect the problem is trying to rewrite-tbd with the 10.12 darwin-stubs, which could explain missing dylibs. The usual 10.12 apple_sdk expression explicitly depends on darwin-stubs but apple_sdk_11_0 does not so I'm not able to override it. I'm not sure why this is, @thefloweringash?

Maybe it's using impure stubs from the host? Would be cool if someone running Big Sur could confirm or deny whether the above works for them.

Maybe it's using impure stubs from the host? Would be cool if someone running Big Sur could confirm or deny whether the above works for them.

I ran into the same issue on Big Sur.

That's happening at #121055 as part of https://opencollective.com/nix-macos

Just coming into this but I see this has been merged? Is there anything to be done here?
Thanks
A

@AlexMoutonNoble, sorry for causing confusion. That PR became just a bump of LLVM and the bit that was merged is just the small bootstrap-tools bump the work depends on. So this has no impact on this issue.
I continue to work on both getting LLVM updated and the Apple SDK.
You can keep an eye on  #116341 or the Nix ❤  macOS Monthly Discourse thread for updates.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/nix-macos-monthly/12330/8

I used to create a Python virtualenv with my flake.nix/shell.nix, then just install watchdog directly with pip inside that virtualenv:
I mainly use this for mkdocs, and it WAS working correctly.
          buildInputs = with pythonPackages; [
            # Python requirements (enough to get a virtualenv going).
            virtualenvwrapper
            numpy
          ];

          shellHook = ''
            # Allow the use of wheels.
            SOURCE_DATE_EPOCH=$(date +%s)
            VENV=./.virtualenv

            if test ! -d $VENV; then
              virtualenv $VENV
            fi
            source $VENV/bin/activate

            # Allow for the environment to pick up packages installed with virtualenv
            export PYTHONPATH=$VENV/${python.sitePackages}/:$PYTHONPATH
        '';

I don't have a mac currently, so can't say if it still works, but you can give it a try.


Adding coveralls

adding coverage tests
adding coveralls

Changes Unknown when pulling dab790d3f1ea306c0747f4c65f02855a559c71fe on adding-coveralls into ** on development**.

Changes Unknown when pulling 997d3c200f7afd287c45fe9ab4bc3fb895f75e61 on adding-coveralls into ** on development**.

Changes Unknown when pulling 17af27aa46e4b1de5f91e931c9bd91db61f590fd on adding-coveralls into ** on development**.


Fix encryption of string containing curly braces

Steps to reproduce:

ecrypt a string with a single closing curly brace, e.g. "ab}cd"
decrypt it
the expected result would be the same string, however the result is "cd"

The root cause is the  stripPrefix method of EnvironmentPrefixHelper class called before the encryption which is currently removing all characters until the first closing curly brace including it.
It seems the intent was to remove all {foo:bar} like expressions from the beginnig of the string, fix is looking for that pattern. Note, the implementation won't allow to enrypt texts starting with {foo:bar} sequence, where foo is not a prefix keyword. To make the implementation perfect all the known keyword:value pairs should be removed one by one.

@mnyeste Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@mnyeste Thank you for signing the Contributor License Agreement!


Error: The method 'handleSystemMessage' isn't defined for the class 'PaintingBinding'.

Compiler message:
/home/aman/Desktop/flutter/.pub-cache/hosted/pub.dartlang.org/google_fonts-0.2.0/lib/src/google_fonts_base.dart:105:28: Error: The
method 'handleSystemMessage' isn't defined for the class 'PaintingBinding'.
 - 'PaintingBinding' is from 'package:flutter/src/painting/binding.dart'
 ('/home/aman/Desktop/flutter/packages/flutter/lib/src/painting/binding.dart').
Try correcting the name to the name of an existing method, or defining a method named 'handleSystemMessage'.
  PaintingBinding.instance.handleSystemMessage({'type': 'fontsChange'});
                           ^^^^^^^^^^^^^^^^^^^

Added  google_fonts plugin in pubspec.yaml file  and restarted the already running app after doing flutter packaged get.
The app doesnt restart giving this error .

Quit the app
flutter run again
app will not build gives the same error

Flutter upgrade to latest stable build resolved the issue.


Add/replace std::OnceCell mention in the Readme

Inside the readme in section Usage: Avoid compiling the same regex in a loop is used external library. Standard library (even core crate) includes OnceCell since 1.70 so I think it should be added/replaced...

This has been requested before. I'm on mobile but please search issue tracker.


[Feature]: PyTorch Labs MoE Kernels (2.7-4.4x faster)

🚀 The feature, motivation and pitch
vLLM should adopt the PyTorch Labs Triton kernels that were developed recently since they can yield 2.7x faster for bs=2 and 4.4x for bs=512. @WoosukKwon Note that the new kernels were developed on top of the existing vLLM kernels, so they should be highly compatible.
Blog: https://pytorch.org/blog/accelerating-moe-model/?utm_content=288416924
Code: https://github.com/pytorch-labs/applied-ai/tree/main/kernels/triton/inference/col_major_moe_gemm

Alternatives
No response
Additional context
No response

@casper-hansen Thanks for bringing this up! We will reach out to the IBM folks whether they are interested in the integration.

Amazing work by @AdnanHoque @ani300 @cyang49 from IBM Research! They will be contributing this back to vLLM soon!

Great work on the MoE kernel Woosuk! Learned a lot studying it :)
We haven't done much end-to-end testing but due to things like tl.atomic_add() not supporting bfloat16 etc. these kernels may not end up something we end up contributing.
I have been working on fusing dequantization into the MoE kernel to allow for a W4A16 GPTQ path, would be great to collaborate on that front if it's something you've been looking to add!
W4A16 Fused MoE: https://github.com/pytorch-labs/applied-ai/blob/main/kernels/triton/inference/gptq/mixtral/w4a16_fused_dequant_gemm.py

https://github.com/vllm-project/vllm/pull/3905
there appear to be some correctness issues with these kernels that we need to debug


Leigh forgot the c, etc etc

👋 Hey Leigh, I'm an engineer, entrepreneur, and investor based between Venice, California and Silicon Valley. I thought a pull request would be a fun way to meet.
I'm interested in tech policy ⚙, computational social science 🍏, and health ❤.
Let me know if you want to connect.
Josh Stroud Bio
Josh Stroud's angel investor and entrepreneur bio
Find Josh Stroud on LinkedIn
One time Josh founded a startup: Sana Health investor profile on SOSV
Josh was an investor at Shenzhen Valley Ventures
AI generated investor site: sandhill5.com
Josh Stroud's academic profile at UC Berkeley College of Engineering 2010-2014: josh-stroud.com
Contact Josh via joshstroud.me


feat(atem): add stinger support

About the Contributor

This pull request is posted on behalf of the BBC.
New Behavior
Properties for the Stinger transition are exposed through tsr-types and the tsr atem integration diffs the properties as appropriate.
Status

[x] PR is ready to be reviewed.
[x] The functionality has been tested by the author.
[x] Relevant unit tests has been added / updated.
[x] Relevant documentation (code comments, system documentation) has been added / updated.

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

Project coverage is 57.38%. Comparing base (f2d9c1d) to head (d4378e1).

Additional details and impacted files
@@             Coverage Diff             @@
##           release52     #363    +/-   ##
===========================================
  Coverage      57.38%   57.38%
===========================================
  Files            160      160
  Lines          10962    10962
  Branches        2674     2674
===========================================
  Hits            6290     6290
+ Misses          4670     4287   -383
- Partials           2      385   +383

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


Update WDAV event log events for newer releases of Windows 10

It seems like this page hasn't been updated for newer releases of Windows 10. For example, WDEG ASR events appear to show up under WDAV as event ID 1121 and 1122 (ref: https://github.com/palantir/windows-event-forwarding/blob/master/wef-subscriptions/Exploit-Guard-ASR.xml ) but this page doesn't mention them. There are probably other events that should be added too. This is related to #2837 as well.

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

ID: 8b83044c-6803-4a48-92f5-c32465f86d03
Version Independent ID: c44626c5-7aa2-15e2-a532-a83ec88ab7da
Content: Windows Defender AV event IDs and error codes
Content Source: windows/security/threat-protection/windows-defender-antivirus/troubleshoot-windows-defender-antivirus.md
Product: w10
GitHub Login: @andreabichsel
Microsoft Alias: v-anbic

@officedocsbot assign @mypil

@iadgovuser1 - Thank you for submitting feedback.
I will get this issue over to the Win10 ITPro writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

events 1121-1128 are missed, according to https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-exploit-guard/event-views-exploit-guard

@iadgovuser1 , according to reply of the article's author, events 1121-1128 are not related to windows defender antivirus, they are for windows defender exploit guard, so the are out of the scope of the article

@iadgovuser1 - From our understanding, the issue has been answered by MaratMussabekov. If you feel it hasn't been resolved please re-open this issue.
Thank you for engaging with the community here for the docs.

OK, I figured they'd be included on the WDAV page because the events are logged to Microsoft-Windows-Windows Defender/Operational but I can see the author's point that they technically are WDEG events despite going to the WDAV event log. Thanks,

@officedocsbot close


Suggestions about recurrence

Scenario: A student wants to use the ModuleBook like NUSmod. He will only add tasks once a semester and make them automatically recur. He will not enter any command throughout the whole semester.
Problem: The ModuleBook will stop updating after one week. No command means no save to storage, the ModuleBook will keep updating the original date by one week, when you open the module book. Also mentioned in #108
Suggested solution: As simple as "while (!isUpToDate) recur()" when open the module book + store after updating
Scenario: A student is taking a lecture with his ModuleBook open. Now the lecture is over, he wants to know when will be the next lecture (and maybe he is really bad at calculation?)
Problem: He has no choice but to close the ModuleBook and reopen it to see the updated time.
Suggested solution: Add a refresh command that refreshes all tasks in the list, if they are recurTasks and not up to date.
The one-shot solution to the previous two problems: Add the refresh command, and execute it automatically when you open the ModuleBook.
Problem: "recur 1 r/daily" is almost identical to "edit 1 r/daily". If we still decide to keep recurCommand, we have to get prepared for criticizes such as "If they are doing a similar job, why you guys only have this particular one for recur only?" during the peer review.
Solution: Delete recurCommand or implement all the rest, I really don't think we should stay anywhere in the middle.
PS: tagCommand is different.
After fixing all of these, we should also implement all kinds of testing about recurrence.

hmm i definitely agree with you that we shouldnt stay in the middle.
When implementing the recur command, I thought it was a good to have a command on its own because:

Personally, i would have more 'one-time' tasks than recurring tasks if im using a a task manager. E.g. we would only have 1 assignment 1 in a module. So for recurring tasks, realistically speaking, it should be made into a command rather than just a normal field like 'workload' for example. This is also a justification we can give for the criticism on 'why does recur have to be a command on it's own' if we get it?

With regards to your 1st problem, I am not quite sure as to why the book will stop updating weekly? If a task is recurring weekly, it will refresh the deadline every week regardless, no? Might need some clarification there haha sorry

The second scenario is actually a v important consideration. One possible implementation can be when a user marks task as done, we can update the deadline (and remove starttime maybe), so that the user can see the next deadline already? what do you think? Another possible solution would be to maybe add a next deadline: field in the task card which is way simpler i think?

For the refresh command, i think it is a bit unsafe to add a new command with only a day left because I think quite a few changes would need to be made? and we only have (only a day at most) to implemement the feature? I am scared that it will be too tight for v1.3 deadline?
Overall, I am still fine with either though cuz for me, both ways work fine and (i think) either way can be justified hahaha

@yhtMinceraft1010X @QY-H00 @figo2127 what do u guys think?

Personally, I think that if 2 commands share the exact same functionality, we might as well keep to one single command.

I feel that its better to keep things simple, but if its too troublesome maybe we can state somewhere in the DG/UG on the 2 very similar commands. For @AiwassPrime and @umergta  2nd problem, I think the ModuleBook should check the deadlines and recurrence on every start-up so that the "updating" does not get stuck  after 2 months of not opening the app.


stale doi issue -> sparcron needs to add logic to check discover for publication events

I currently do not embed non-resolving dois in the export. However, because the dataset modified date does not get bumped when it is published (as it should) we never detect that there was a change. This means we probably need to start embedding non-resolving dois. There is some old logic lurking that the presence of a doi means that we can assume that it has resolved at least once and that a dataset has actually been published.
This also means that we need to add an additional check during our combination step to see whether a dataset has actually been published before we place it in the curation-export-published.ttl pile.
Further it means that we will no longer be able to determine publication status reliably using the json export.
I think this means that the discover database is actually the source of truth for this information, so I think I can set up a way to rerun a dataset export without fetching any new data that would allow us to run the export again when a publication happens. Then we wouldn't need to change the way we currently handle dois. This seems the safes option.

'dataset modified date' tracks changes that have happened to the data itself.  Not sure a publication event counts there. For example, there may be many changes to the publication status with no changes to the data.  Then there is no reliable timestamp for the update to the data itself.

A related issue here is that the -published files do not updated as expected.


可以支持用tinygo编译吗

用go build体积有点大，tinygo似乎可以减小很多

Thanks for your issue. The tinygo has limitation for reflects supports, on my tried one year ago.


pipe_close_stdout_read_stdin - Intermittent - PPC BE Fedora 20

Intermittent - seen once since PPC BE added to regression CI job
https://ci.nodejs.org/job/libuv+any-pr+multi/nodes=ppcbe-fedora20/230/console
pipe_close_stdout_read_stdin failed: exit code 6
Output from process pipe_close_stdout_read_stdin:
Assertion failed in test/test-pipe-close-stdout-read-stdin.c on line 86: uv_run(uv_default_loop(), UV_RUN_NOWAIT) == 0
Assertion failed in test/test-pipe-close-stdout-read-stdin.c on line 97: WIFEXITED(status) && WEXITSTATUS(status) == 0

The issues is caused when child process gets to
uv_run(uv_default_loop(), UV_RUN_NOWAIT) == 0

before the parent has closed the write end of the pipe.

Can this issue be closed?
( doesn't fail in CI https://ci.nodejs.org/job/libuv+any-pr+multi/nodes=aix61-ppc64/260/console and the fix has landed )

@iWuzHere you are mkaing me very happy today :-)


refactor: change logo section in styleguide

fix #4

Pull Request Test Coverage Report for Build 126

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

Totals

Change from base Build 121:
0.0%

Covered Lines:
434

Relevant Lines:
521

💛  - Coveralls


Azure Communication Services Email API for GA

This PR adds the GA version of Azure Communication Services Email API. This is identical to the last public preview version that was released.
Data Plane API - Pull Request

API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your engagement record.

Link to engagement record issue:

Is this review for (select one):

[ ] a private preview
[ ] a public preview
[x] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous Open API document (swagger) if applicable, and the root paths that have been updated.

Design Document:
Previous Open API Doc: https://github.com/apattath/azure-rest-api-specs-apfork/blob/main/specification/communication/data-plane/Email/preview/2023-01-15-preview/CommunicationServicesEmail.json
Updated paths:

❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

fix https://github.com/Azure/azure-rest-api-specs/issues/23047

POST /emails: send
The Operation-ID would ideally not have to be restricted to uuids only.
The default error must be the Azure error type; not "string"
GET /emails/operations/{operationId}
The docs say that operationID is "This is the ID used by the status monitor for this long running operation."
But this could be the Operation-Id value passed in by the customer too, right? It should support this.
The default error must be the Azure error type; not "string"

POST /emails: send The Operation-ID would ideally not have to be restricted to uuids only. The default error must be the Azure error type; not "string"
GET /emails/operations/{operationId} The docs say that operationID is "This is the ID used by the status monitor for this long running operation." But this could be the Operation-Id value passed in by the customer too, right? It should support this. The default error must be the Azure error type; not "string"

@JeffreyRichter - the Operation-ID was restricted to be a UUID because we use it as our correlation id and an index into the database that stores the message information. Everything in our service is designed around this being a UUID and privacy has classified it as EUPI due to the restriction we've placed on it that we'll only allow UUIDs from the customer.
As for the default error, I think you might have misunderstood. The type = string is for the "x-ms-error-code" response header, not for the response type itself.
For the GET endpoint, yes the OperationID is the value that the customer passes in. I'll update the description to read better.
Again even for this endpoint, the type = string is actually for the response header 'x-ms-error-code', not for the error type itself.

OK on the UUID.
For GET and POST, when I look at your swagger in the editor.swagger.io website, I see "default" Error with an empty JSON object {}. Maybe you're missing a default response JSON referring to the normal Azure error type?

OK on the UUID.
For GET and POST, when I look at your swagger in the editor.swagger.io website, I see "default" Error with an empty JSON object {}. Maybe you're missing a default response JSON referring to the normal Azure error type?

@JeffreyRichter - not exactly sure how editor.swagger.io website links to models that are referenced from other files using a relative path, but that might be the problem. When I opened just 'communicationServicesEmail.json' on editor.swagger.io, I also see the empty json for the Error model. It seems like that was because it can't resolve the types that I've linked in my swagger that are coming from other json files using relative paths. When I look at my swagger in VSCode preview, I'm able to see the correct types as below:

Also, I've updated the description of Operation-ID header now.

Also, I've updated the description of Operation-ID header now.

And in auto-generated SDK, it seems to be generating the models correctly.


for the 08/23 release, app service shows "could not resolve" error for AzureUSGovernment cloud

for us gov cloud, the app service extension displays error under app service: " could not resolve resource "subscriptions/xxxx"

Is there another error besides just could not resolve resource?
For example, at the bottom right corner, you may see an error like this:

in the vs code, this is the error : the subscripotion could not be found. Many of developers experience the same error.

Seems like the The subscription 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' could not be found. error is an issue in the Azure Resources extension. It was reported there by another user https://github.com/microsoft/vscode-azureresourcegroups/issues/905. They say it started with v0.9.2 and works when they use v0.9.1.

thank you for the quick response!! i didn't go all the way to 5 yrs ago, instead, tried v0.25, didn't work. tried v0.24, it works!!
Thank you!! Really look forward to the future release that can fix this issue

Could you please try updating the Azure Resources and the Azure App Service extensions? This should be fixed in both latest versions.
Make sure that you upgrade Azure Resources as well, as it controls the Azure view.


Function calls dont work with Azure OpenAI currently due to differences between OpenAI API, and AzureOpenAI

I am one of the AI Global Black Belts and have been working with AutoGPT to build some applications in the last few days. I noticed a pretty impactful bug. I have only noticed this using AzureOpenAI, but custom functions are not working. When the API returns the function call spec {"function_call"}, it triggers issues with the AutoGen create completion, as it cannot find a "Content" for the message. I tested verbatim with your demo, as well as my custom code, and the issue persists. Hopefully this is helpful! Thanks!

Thanks. Probably the same issue with #75

@OwenVanV We just fixed this problem. Can you test it to see if the error persists?

We believe this issue is solved and are closing it. Thank you for pointing it out!


Improve grammar for 1.1

Minor grammatical edits

@lche your PRs looks perfect, thanks a lot for doing this!


az functionapp create assumes referenced plan is non-Dynamics

If passing in a plan name to the az functionapp create command via the -p flag, and the plan happens to be Dynamic (Y), it will still fail because the code path attempts to switch on always on.  There should be one more check in this line to make sure the plan isn't Dynamic or Elastic Premium, as dynamic is a valid plan to reference and shouldn't have always on enabled:
https://github.com/Azure/azure-cli/blob/dev/src/command_modules/azure-cli-appservice/azure/cli/command_modules/appservice/custom.py#L1992-L1994

This is related to #8388

Is there any progress on this? If anyone knows some workaround for this?


Docs/wash installation instructions

Feature or Problem
Now that the formula installs from released binaries, it's no longer needed to tap
I also updated outdated URLs to wash

Bypassing branch protections because we're only lacking approval from examples-maintainers, and the only change I made there was to a README


Add scala client

Implemented with rediscala.
New project is using scala & akka, thus non-blocking operations are required.
This implementation uses actor model and provides async operations on codis.

Thanks @tesseract2048
I do not know scala at all, but i think we should write some tests.
We need a scala expert to review. Hi, there @dcaoyuan

Ping

Can you write more tests ?  @tesseract2048

Hi, several tests have been added.

LGTM


Multiple Guards Configuration

Im building a multi users site which I separated with different authentication Guards. I Want to use this package on both of them but by reading the documentation there is no Guard mention.
I have dealer guard (which is default ) and admin guard for admin. both need to login to access the portal.
How can I setup this?
possible like this?
photos/dealer/{dealer_id}/sub_folder/image1.jpg
photos/admin/{admin_id}/sub_folder/image1.jpg

This can be accomplished by implementing custom logic in userField(). See: https://unisharp.github.io/laravel-filemanager/config#multi-user-mode


Content Validation for OBS Translation Notes

Similar to #1199 except for OBS-TN resources

translationCore Create - v1.4.2 build 132-6493c98 works as expected.


disabledDaysOfWeek does not use firstDayOfWeek

Description
disabledDaysOfWeek does not check if firstDayOfWeek has been override. For example, in Europe for most countries the first day of the week is monday (1) and when you disable some day there is an offset of 1.
I think this array should be the number of the days whatever is the locales or the first day of week
For instance:
      :firstDayOfWeek="1"
      :disabledDaysOfWeek="[0, 1, 2, 3, 5, 6]"

Thank you guys for your awesome work!
Code sample
In this case, 'Ven' (friday) is disable, not Saturday
    hotel-date-picker(
      :firstDayOfWeek="1"
      :disabledDaysOfWeek="['Lun', 'Mar', 'Mer', 'Jeu', 'Ven', 'Dim']"
      ...
    )

Datepicker Version
2.6.4

See #108

I think is not the same but it is related.


Fasboot Compatibility

Right now ember-islands will throw an error when rendered with Fastboot. Per https://github.com/mitchlloyd/ember-islands/pull/28, there could be some interesting use cases with Fastboot and ember-islands, but I'm not sure what those are yet and what patterns would be most helpful. For starters, should this library render nothing when not in the browser or should it try to render something?

I would love to see this supported. Let me lay out the use-case we're looking to solve, and what might make sense as an alternative solution to how #28 looked at it, and hopefully that will spark some ideas.
Background
We have a large server-rendered page-based web application. There's more and more demand for more interaction and lower latency and so we're looking to move to Ember. A big-bang changeover isn't an option, so using ember-islands looks like a perfect solution because it will let us build new things using Ember and convert old things to be Ember-driven.
We have strict requirements around SEO and user experience, however, so we also need to have the initial server response contain fully rendered HTML. If we had an all-Ember app, Fastboot is exactly the solution, but it will be a while before we get everything converted.
Use Case
So the problem we're hoping to solve w/ Ember Islands being able to place nicely with Fastboot is this: How can a non-Ember, server-side-rendered application move to Ember iteratively without losing out on the benefits of being server-side-rendered?
Hopefully Ember Islands + Fastboot is the solution to that problem!
Potential Solution
Pipe the existing server-rendered pages through Fastboot (I'm not sure if this makes sense). When an Ember Island is encountered, it would render as if it was being rendered in a browser, and the entire rendered page comes out the other side.
I don't know Fastboot well enough to know if that sort of thing would even be supported / supportable, but that's how my mind initially tackled it. At first glance, supporting that kind of use-case by Fastboot is a prerequisite, but once that's there, then having Ember Islands be OK running inside the Fastboot environment makes this a workable solution for my problem.

@cdeszaq Thanks for the great write up! I agree that this use case fits with the goal of Ember Islands.
Since #28 the library has changed a little. Ember Islands should not longer attempt to render in Fastboot. At the time of that issue, it would throw an error.
So what if we did want to render something in Fastboot? This seems straightforward to me:

Remove jQuery and figure out how to query existing DOM and render over it in Fastboot. This might take some work, but it's going to be possible. Either this can use the ember-fastboot/simple-dom APIs or the excellent (but private) -in-element Glimmer API.
Provide some mechanism (configuration, function to call, or some option on {{ember-islands}}) to start the reconciliation process if you want to render before didInsertElement.

However, this is the part that I'm also unsure about:

Pipe the existing server-rendered pages through Fastboot (I'm not sure if this makes sense)

I don't know if there is a way to provide Fastboot with a per-URL html page to render into. I haven't used Fastboot before but it looks like it needs a the index.html page provided in its configuration.
If this is possible and you've got the inclination I'd like to support this case. It would be helpful if you could create a "proof of concept" repository to show whether the "per-page HTML" setup would work.


Jest icon not showing for jest.config.json

[x] I'm sure this issue is not a duplicate.

According to https://github.com/vscode-icons/vscode-icons/blob/a9eb06966d82f06444733a8fe759c40062f80c43/src/icon-manifest/supportedExtensions.ts#L233, jest icons are supported
but I'm seeing this :

VSCode version 1.16.1

I cannot reproduce on Insiders:

I'm new to VSCode, please give me steps, I confirm I'm seeing it happen right now.

Did you activated the Icon Theme like shown in the gif in the README file?

Sorry I didn't realise it was an extension 😅 so sorry, I installed and everything is working fine. What confused me was that a lot of icons (babel, ESlint, Yarn ...) were already showing by default ... What you do is awesome 👍

Alright, thanks. Welcome to our community. :)


Newsletters: add 145 (2021-04-21)

[x] Update releases/RCs @harding
[x] Add topic links @harding
[x] Client/services section @bitschmidty
[x] Bitcoin Core #21377 and #21686 @Xekyo
[x] Rust-Lightning #858 @dongcarl

My IRC is dead again, but I'm on it. :+1:

Pushed edits for my parts of the newsletter plus topic links.  No changes to the releases/RC section.  Reviewed the content by @Xekyo, @bitschmidty, and @dongcarl---it all looks good to me exclusive of @jnewbery's feedback.  Thanks all!

Made edits for what I think was all remaining feedback.  @bitschmidty I dropped the Ion announcement given the concerns voiced by @jnewbery and @ajtowns, plus I think the other items in this month's section were excellent, so it should be ok to have one fewer item.

@jonatack Thanks for the feedback, pushed commits to address some items.

Removed some unreferenced links wrt to client service ion removal, squashed, and merged!
Pleasure contributing with you gentlemen 🤝  @harding @Xekyo @dongcarl @jnewbery @jonatack @adamjonas @ajtowns


DSC (branch 386):
2021-07-19T10:20:41,314 [https-jsse-nio-8080-exec-9] WARN - Invalid input. [exception=(Unrecognized field "username" (class io.dataspaceconnector.model.auth.AuthenticationDesc), not marked as ignorable (2 known properties: "value", "key"])\n at [Source: (PushbackInputStream); line: 1, column: 58] (through reference chain: io.dataspaceconnector.model.datasource.DataSourceDesc["authentication"]->io.dataspaceconnector.model.auth.AuthenticationDesc["username"]))]
2021-07-19T10:20:41,323 [https-jsse-nio-8080-exec-9] WARN - Resolved [org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Unrecognized field "username" (class io.dataspaceconnector.model.auth.AuthenticationDesc), not marked as ignorable; nested exception is com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "username" (class io.dataspaceconnector.model.auth.AuthenticationDesc), not marked as ignorable (2 known properties: "value", "key"])\n at [Source: (PushbackInputStream); line: 1, column: 58] (through reference chain: io.dataspaceconnector.model.datasource.DataSourceDesc["authentication"]->io.dataspaceconnector.model.auth.AuthenticationDesc["username"])]

API call needs to be updated due to breaking changes:
[1] authentication: { username: 'admin', password: 'admin' },
params are now called key (=username) and value (=password).
Posting
authentication: { key: 'admin', value: 'admin' }
should work.

Third API-Call in that API-Call-Row also needs to be adjusted due to breaking change dataSourceId not beeing in the API-Call body any more but as addition API-URL-Param:
Following works for creating (updating needs to be adjusted too):

Fixed in ae350e2, but there seems to be a bug in DSC API endpoint: Issue 438


[Feedback] - Retrieving error logs when azure-webapp deployment fails.

Document Enhancement Proposal: Retrieving error logs when azure-webapp deployment fails.
Overview
This enhancement provides a step-by-step guide to improve the deployment process for Flask and React applications on Azure Web App, addressing common challenges in managing dependencies and build steps. The proposed documentation enhancement focuses on activating Oryx to handle the build process, providing alternative deployment methods, and leveraging logs for troubleshooting. This guidance aims to streamline deployment for developers by clarifying each step and providing improved error handling.
Enhancement Details
This guide will enable users to:

Activate Oryx build handling during deployment for applications with complex dependencies.
Package and deploy the application manually using Azure CLI commands.
Access deployment logs for troubleshooting.
Implement enhanced Docker configuration for better error management.

Steps for Improved Flask/React Deployment on Azure Web App

Setting the App Setting for Oryx Activation

Add the SCM_DO_BUILD_DURING_DEPLOYMENT=true setting in Azure App Settings to activate Oryx for build handling during deployment.

Manual Packaging and Deployment

Instead of relying solely on az webapp up, manually package and deploy the application using the following steps:
zip -r app.zip .
az webapp deploy --resource-group <your_resource_group> --name <your_app_name> --src-path app.zip

Verify Dependencies

Ensure that all required dependencies are correctly listed in requirements.txt for Flask and package.json for React. Missing dependencies are a common cause of deployment failures.

Access and Monitor Deployment Logs

Deployment processes produce logs in the /LogFiles directory on Azure, which contain standard output and error logs. Reviewing these logs can reveal stack traces or system errors.
Enable log streaming to monitor logs live, providing real-time insights into any issues that arise during deployment.

Justification for Documentation Enhancement
Currently, the Azure documentation provides limited guidance on the specifics of deploying complex Flask and React applications with custom configurations, leaving developers to troubleshoot build and deployment issues without sufficient support. This enhancement fills that gap by offering a structured, example-based solution that addresses common deployment errors and includes robust error-handling configurations.
Conclusion
By following this enhanced guide, users can effectively manage the deployment process for Flask and React applications on Azure Web App, making use of Oryx, manual packaging, Docker enhancements, and log streaming for a smoother and more reliable deployment experience.
Reference
Why does deploying to azure web app fails with no apparent error? How can i retrieve better error logs to fix the issue?
This documentation update will improve user experience, reduce deployment errors, and enable faster troubleshooting for developers deploying web applications in enterprise environments.

@SureshChikkam-MT
Thanks for sharing the feedback. Since this channel is for driving improvements towards Docs, could you please provide the URL of the specific documentation that your feedback is applicable to? That way, we can make sure your feedback is addressed by the right team.

@SureshChikkam-MT
We are going to close this thread , if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Caching fails on AppVeyor

Some caching doesn't seem to be working on AppVeyor:
15198Cache entry not found: C:\Users\appveyor\AppData\Local\Programs\stack\x86_64-windows\msys2-20150512
15199Cache entry not found: C:\Users\appveyor\AppData\Local\Programs\stack\x86_64-windows\msys2-20150512.installed

This might be related to what @keremispirli mentioned in https://github.com/TorXakis/TorXakis/pull/750.
But we shouldn't have to worry about the cache. I think the problem is that we build sqatt in our CI. I think it is better to build it as a separate project, and use the binaries in the CI.

So we wait...

Date was changed (from 20150512 to 20180531) should be
 15104 Cache 'C:\Users\appveyor\AppData\Local\Programs\stack\x86_64-windows\ghc-integersimple-8.2.2' - Up to date
 15105 Cache 'C:\Users\appveyor\AppData\Local\Programs\stack\x86_64-windows\ghc-integersimple-8.2.2.installed' - Up to date
 15106 Cache 'C:\Users\appveyor\AppData\Local\Programs\stack\x86_64-windows\msys2-20180531' - Updated
 15107 Cache 'C:\Users\appveyor\AppData\Local\Programs\stack\x86_64-windows\msys2-20180531.installed' - Updated
 15108 Cache '.stack-work' - Up to date
 15109 Build success


[Peter Latona] - Deploy and Interact with Smart Contracts on Celo Blockchain

Thanks for submitting this tutorial for Celo Sage
Before you hit "Create Pull Request", make sure you have read the Tutorial Contribution Guidelines and reviewed the Sample Tutorial Structure.
Please confirm the following before submitting your tutorial for review -

[x] My tutorial follows the Tutorial Contribution Guidelines.
[x] The title of the Pull Request matches the title of my tutorial.
[x] I've followed the tutorial template structure.
[x] I've proofread the tutorial for spelling and grammar mistakes.
[x] I've thoroughly explained the code, with inline code comments and text explanations.
[x] I've run a linter & prettifier to format my code blocks.
[x] I've run the tutorial to test it and the code works.

NOTE: We cannot review your Pull Request if it does not meet the standard outlined above.
Reviewers - @joenyzio & @viral-sangani

@SasaniEldis Just Fix the Headers It should be ## for headings and ### for subheading
and second thing use the https://prettier.io/playground before pushing.

Closing Celo Sage PRs


soc: gecko: Enable SWO output during SoC initialization

Enable SWO debug output during system initialization and not as part of
GPIO driver initialization. After the modification the logger output
becomes available earlier during the boot process. Also, it's not
necessary anymore to build full GPIO driver only to enable SWO. This may
be critical when building small images, e.g. mcuboot.

I verified that this works fine on the board efr32mg_sltb004a.
On question though:
The option CONFIG_GPIO_GECKO has to be enabled, to make this work, because only in that case the clock for the gpio peripheral is enabled, see https://github.com/zephyrproject-rtos/zephyr/blob/master/soc/arm/silabs_exx32/common/soc.c#L78
Is thins ok/intended?

The option CONFIG_GPIO_GECKO has to be enabled to make this work, because only in that case the clock for the gpio peripheral is enabled

@chrta Thanks, well spotted! I did verify that SWO logging backend works when CONFIG_GPIO and CONFIG_GPIO_GECKO options are disabled manually via menuconfig. However, I overlooked the fact that CONFIG_GPIO_GECKO will be selected anyway. So the gpio clock was quitely enabled and a full GPIO driver built despite the change. This should be fixed now.


[Frontend] [Neuron] Parse literals out of override-neuron-config

For now it was only possible to add string parameters, if a bool or a number was passed, the neuron initialization failed. The parsing was also inconsistent with how other composite configs were passed (see --mm-processor-kwargs).
This is not a backward compatible change, but considering that --override-neuron-config was added only recently, it makes sense even for the sake of consistency
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Adding or changing kernels
Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.

Make sure custom ops are registered following PyTorch guidelines: Custom C++ and CUDA Operators and The Custom Operators Manual
Custom operations that return Tensors require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.
Use torch.libary.opcheck() to test the function registration and meta-function for any registered ops.  See tests/kernels for examples.
When changing the C++ signature of an existing op, the schema must be updated to reflect the changes.
If a new custom type is needed, see the following document: Custom Class Support in PT2.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

Any thoughts on this @ilya-lavrenov?

@liangfu can you help with reviewing this change?


Take the infrastructure template directory location from testgrid.yaml

Description:
ATM. we have hard-coded the location of a given infrastructure provisioner within the Jenkinsfile. This is not correct.
But, we should rather read the directory location from the infrastructureConfig/provisioners[0]/dir location instead.
Affected Product Version:
0.9.0-m14
OS, DB, other environment details and versions:
N/A
Steps to reproduce:
The infrastructureRepository and deploymentRepository inputs should be the root directory of the cloned git repository. Testgrid shouldn't be aware where exactly the template files are located. These should be read from testgrid.yaml.
Related Issues:
N/A

@kasunbg Although the location is hard-coded in jenkinsfile, we take those details from Build-API as inputs. So wouldn't that sufficient? :)

This is fixed. Hence closing.


Enable dcap attestation with gsc

Signed-off-by: Veena Saini<EMAIL_ADDRESS>
Description of the changes
Details to be added soon.

How to test this PR?

This change is

@veenasai2 You closed this because it is superseded by #70?

@veenasai2 You closed this because it is superseded by #70?

Yes @dimakuv.