user should be able to set storage_account_name on a persistent disk

so that we can make sure that persistent disk uses specific storage account
users will say something like this:
persistent_disk_pools:
- name: large
  cloud_properties:
    storage_account_name: premiumsotre

and then CPI will receive create_disk CPI call with cloud_properties filled in (https://github.com/cloudfoundry-incubator/bosh-azure-cpi-release/blob/master/src/bosh_azure_cpi/lib/cloud/azure/cloud.rb#L207).
storage_account_name on disk should take precedence over any other configuration (global or VM one).
cc @cppforlife

@pronoiac When you create VMs on premium storage account, the persistent data disks will be put on the same premium storage account. You do not need to specify storage account name in persistent_disk_pools.
resource_pools:
- name: vms
  network: private
  ...
  cloud_properties:
    storage_account_name: <your_storage_account_name>

thats not ideal since disk configuration doesnt really relate to vm info. in fact i may want to create disk on premium storage and create_disk doesnt receive vm id. vm id in create_disk cpi call is on best effort basis.
Sent from my iPhone

On Mar 30, 2016, at 6:22 PM, Chou Hu<EMAIL_ADDRESS>wrote:
@pronoiac When you create VMs on premium storage account, the persistent data disks will be put on the same premium storage account. You do not need to specify storage account name in persistent_disk_pools.
resource_pools:

name: vms
network: private
...
cloud_properties:
storage_account_name: <your_storage_account_name>
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub


Upgrade to php 8.2

@Jeroen-G
When will this PR merged version be released? When I try to install this package on PHP 8.2 environment, I got following errors:
composer require jeroen-g/explorer

Cannot use jeroen-g/explorer's latest version 3.3.1 as it requires php 8.0.*||8.1.* which is not satisfied by your platform.
./composer.json has been updated
Running composer update jeroen-g/explorer
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - jeroen-g/explorer[v1.0.0, ..., v1.2.0, v2.0.0, ..., 2.6.0] require illuminate/support ~7|~8 -> found illuminate/support[v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
    - jeroen-g/explorer[3.0.0, ..., 3.3.1] require php 8.0.*||8.1.* -> your php version (8.2.1) does not satisfy that requirement.
    - Root composer.json requires jeroen-g/explorer * -> satisfiable by jeroen-g/explorer[v1.0.0, v1.0.1, v1.1.0, v1.2.0, v2.0.0, ..., 2.6.0, 3.0.0, ..., 3.3.1].

You can also try re-running composer require with an explicit version constraint, e.g. "composer require jeroen-g/explorer:*" to figure out if any version is installable, or "composer require jeroen-g/explorer:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Although there is a workaround for this:
composer require jeroen-g/explorer:"dev-master"

But if you officially release the update, that would be wonderful😃

Does your application work on dev-master without any issues?

@Jeroen-G
So far, yes.
I mainly use this package to create index data for Elasticsearch from my Laravel models so that not all features are tested.
BTW, while using search function, php gives a warning:
PHP Deprecated: Creation of dynamic property Laravel\Scout\Builder::$must is deprecated in /vendor/jeroen- g/explorer/src/ExplorerServiceProvider.

Hmm, can you make that a new issue? 🤔
If possible with the whole stack trace if you have that.

https://github.com/Jeroen-G/Explorer/releases/tag/3.4.0
Enjoy! 🚀

Hmm, can you make that a new issue? 🤔 If possible with the whole stack trace if you have that.

OK, I created this new issue.


Remove API Doc generation commands for a single ballerina file and -o flag

Purpose

Remove single ballerina file APPI doc generation commands and anything related to -o flag

Fixes #22019
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #22585 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #22585   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1411     1411
  Branches      219      219
=======================================
  Hits          206      206
  Misses       1189     1189
  Partials       16       16

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dc19640...b6c77c0. Read the comment docs.


test: Cypress - Flaky Fix

Description
Fixed below flaky tests

Radio2_spec.ts
Video2_Spec.ts

Type of change

Flaky test fix

How Has This Been Tested?

Cypress test runs

Checklist:
QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ci-test-limit

/ci-test-limit runId=6249259280

/ci-test-limit runId=6249259280


Quick question: RLhF, three model on GPU?

Hi,
I am running your stacklamma RLHF script. Just a quick question, if I do full model training (I.e., no peft), do you put the reference model (SFT model) on CPU or GPU?
I ask this question because I wanna know/calculate the rough GPU memory you need if doing RLHF. I understand that the learning model is on GPU, the reward model is usually on GPU. From the PPO trainer code, it looks like you just create a reference model by deep copying of the learning  model, does this mean that it is on CPU "by-default"?

Try OpenRLHF, which solves this problem perfectly using Ray: https://github.com/OpenLLMAI/OpenRLHF

@hijkzzz thanks! Is it easy to migrate over? I am trying to train 7B model full scale (no Lora) on A100

@hijkzzz thanks! Is it easy to migrate over? I am trying to train 7B model full scale (no Lora) on A100

Yes, the OpenRLHF is fully compatible with HF transformers.

Yes, all models are on GPU, although you can put the Reward model wherever you want as you have control over it outside the RLHF loop. If you want to save a bit more memory for the reference model you can share the first few layers between the reference and active model and only treat the last few layers separately. See here.


Fixed non-PNG decoding in thumbnail save (Fixes #2341)

Fixes #2341.
Borrowed the same fix from #2142:
str_replace('data:image/png;base64,', '', $imgData)
became
preg_replace('/data:image\/(png|jpeg);base64,/', '', $imgData, 1)

thanks!


Testing graph-theory-planar

Testing https://github.com/NixOS/nixpkgs/pull/211137

@vbgl there is an unrelated CI failure here in smtcoq for 8.13 that is present in nixpkgs/master and might went under the radar before. AFAIU cvc4 is at fault.

@vbgl there is an unrelated CI failure here in smtcoq for 8.13 that is present in nixpkgs/master and might went under the radar before. AFAIU cvc4 is at fault.

@vbgl I got it wrong for graph-theory-planar, but still, there is an issue with cvc4

Again? What a pain…

Git bisection lead to https://github.com/NixOS/nixpkgs/commit/aae36e6869162e97b6ff02b6bdfdeb23e55f3c5d
So the version of cvc4 that is needed for smtcoq cannot be built with bash 5.2.
I don’t have a solution (yet).


Added support for specifying the JRE/JDK versions via the Build Plan TOML metadata

Summary
Added support for specifying the JRE/JDK versions via the Build Plan TOML metadata
Use Cases
executable-jar buildpack (https://github.com/paketo-buildpacks/executable-jar/pull/99) could request specific JVM version, based on the metadata of the JAR/WAR files (with which version it was built).
Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[x] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

Right now that logic is encapsulated in libjvm and is fairly simple and testable. If we put it in the buildplan, that opens up the possibility that one or more buildpacks now want to set a version, and we need more complicated rules to define how we select the version, like if two buildpacks both want different versions.

Fair point. I could imagine instead of specifically setting the version to a fixed value, the executable-jar buildpack (and potentially other buildpacks) could set a semver range like versionRange: >=11 (see https://docs.npmjs.com/cli/v6/using-npm/semver#ranges, there are go implementations for this available) and the libjvm would then pick the best match or fail, if there is none.
Alternately, we could go for a simple minimumVersion, resolving conflicts there would be very easy: just take the maximum of all minimumVersions
Moving everything into the libjvm seems wrong to us, but if this is preferred by you we are willing to adapt the PR accordingly.

Side question. Is Build-Jdk-Spec part of some Java specification, or is that something Maven is just setting as a convention? I ask because I do see this in some of my Maven projects, but I do not see it in some of my Gradle projects. Just trying to understand the audience for this feature.

Good point, we did some additional research: This is indeed specific to maven. Even specific to the maven-jar-plugin. When building war files (with maven-war-plugin) there is Build-Jdk instead. Gradle does not seem to include something similar at all.
As an alternative, we could read the Java version from the Main Class file. This would be a little more complex, as we would need to maintain a mapping between Java Class Versions and compatible JVM Version, see https://docs.oracle.com/javase/specs/jvms/se17/html/jvms-4.html#jvms-4.1-200-B.2. Currently, it works by subtracting 44, but that's not guaranteed, so having a hard-coded map[int]int or similar might be the safer bet.

Moving everything into the libjvm seems wrong to us, but if this is preferred by you we are willing to adapt the PR accordingly.

Can you expand on this? I'd like to understand why you feel this way.

As an alternative, we could read the Java version from the Main Class file. This would be a little more complex, as we would need to maintain a mapping between Java Class Versions and compatible JVM Version, see https://docs.oracle.com/javase/specs/jvms/se17/html/jvms-4.html#jvms-4.1-200-B.2. Currently, it works by subtracting 44, but that's not guaranteed, so having a hard-coded map[int]int or similar might be the safer bet.

This seems like a reasonable idea to me. If you are building your code against a particular version of Java, then it's reasonable to assume that you'd want to run with the same version. Plus, you can always override that version with BP_JVM_VERSION.
When thinking about this approach in the past, I got stuck trying to determine which class file to you examine. You could pick the first one, or a specific one, or every file (What if there's a conflict?), or something else? It seems clear that we have to pick a class file from the user's application, cause you wouldn't want to pick a class file from a JAR that could have been compiled with some other Java version (normally that wouldn't be an issue, but for Spring Boot executable JARs this could be a concern). I'm not sure the best way to do that. I'd be curious to get your thoughts on how you'd see the implementation working.
This would also only work for apps that have pushed pre-compiled Java code. If you were pushing source code, then you'd still need to specify that in some other way. But the same would apply for Build-Jdk-*.

We tried detecting the used version of the JVM inside the libjvm go library. It worked out pretty good, but we came to the conclusion, that it might just not work out correctly in all cases. For example we found multiple class file versions for the same project (some coming from dependencies and others from the sources).
Would a specific implementation only for maven (utilizing Build-Jdk and Build-Jdk-Spec) be worth a contribution from our side?

Would a specific implementation only for maven (utilizing Build-Jdk and Build-Jdk-Spec) be worth a contribution from our side?

Sure. That should still apply to a large subset of apps. I would still prefer to keep that in libjvm. There is a utility in there already for reading MANIFEST.MF.
I'd say in order of highest priority to lowest priority:

BP_JVM_VERSION
Build-Jdk
Build-Jdk-Spec
Buildpack default

I have no preference regarding Build-Jdk or Build-Jdk-Spec. I just picked that order cause we have to put them in some sort of order.


Focus improvements

Focus style updates displays immediately
The focus_order example always keeps your focus on the buttons
Add KEYBOARD_NAVIGATABLE ability to allow for focusable elements that are not in the tab order (the equivalent of tabindex="-1" in html)
Buttons get focused on click (this triggers the focus pseudo class which equivalent behaviour to html - html also has the :focus-visible pseudo class to only show the style when using keyboard navigation which we may also want)

Related to #55


Updated mysql Package to support the change of root password of the mysql-server

Ensure Databases and User does not work if the root password has changed
Motivation for this change
Trying to use mysqlBackup with changed root password. ... not working
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ x] Fits CONTRIBUTING.md.

Please improve the commit title to describe what Nixpkgs attribute is modified, and what the change is roughly about.

Done

(triage) closing this PR.

It targets the previous stable release, which is not supported anymore.
Changes should first happen on master, then be backported

If the change is still wanted, please re-open a new PR, targeting master. Thanks again for wanting to contribute, though!


Unity: Automatically convert referenced images to "Sprite" while importing the .scml

[I tried to do this in Spriter2UnityDX] (https://github.com/Dharengo/Spriter2UnityDX/blob/master/Assets/Spriter2UnityDX/Editor/ScmlPostProcessor.cs), it mostly works, but there are some bugs, but this is how I do it, basically.

Thanks for the tip!


the problem is in the deploypath attribute of the module.xml file

the problem is in the deploypath attribute of the module.xml file
If in the file DeployPath="${cspdir}"
...

Installing cleans up the csp directory. The system portal is broken.

There should be restrictions on DeployPath to avoid this outcome.


Add a third button option, for three-way dialogs

Thanks for the contribution @johan-weitner !
Unfortunately, I can't merge this PR and I explained why here and here

if i want click the altactionButton to trigger a function,how can i do,please give me an example,thanks!


Adding a base_url parameter to the recognize_whisper_api function.

Just that. I would like to use the Groq API (https://groq.com/), but to do that I had to change the library's code. It's a simple fix, actually.

Groq provides whisper models. I see...
https://console.groq.com/docs/speech-text

Yes, exactly. That's why i need the base_url parameter. To use groq i need to put their url there and their api key.

Hey, could you merge the PR?

Thanks the PR, but I want to use groq library.
Draft: https://github.com/Uberi/speech_recognition/pull/797/commits/a0999389c38f986abd6bd29bd4c73e16a55a3b47
In Groq documentation, groq library is used.
From my viewpoint, openai library with base_url seems kind of hack for workaround.

@amosdevstudio Try SpeechRecognition 3.12.0, which supports Groq.
python -m pip install SpeechRecognition==3.12.0
>>> # NOTICE: export GROQ_API_KEY before launching Python interpreter
>>> import speech_recognition as sr
>>> r = sr.Recognizer()
>>> with sr.AudioFile("english.wav") as source:
...   audio = r.record(source)
>>>
>>> r.recognize_groq(audio)
' One, two, three.'

Great! I love to see this.


Fixed problems with layout transitions and color formats.

Fixed problems with layout transitions in deferred and deferredshadows samples. Fixed mismatched color formats of attachments/render passes/framebuffers. Removed unused variables.

Hi. Any update on this pull request? Did You have time to test it? Without these modifications deferred* samples don't work on Intel graphics.

Sry, totally forgot about this PR. I didn't realize that this is required on Intel graphics, as all the examples run fine on my Haswell Ultrabook running Ubuntu with the MESA drivers.
While most changes look fine, the changes to the depth/stencil final layout (https://github.com/SaschaWillems/Vulkan/pull/238/files#diff-bb472eedb08baf1328e3fe24fbe53158R218) causes validation layer errors for the layered depth map.
Is that change really required to get these running on Intel graphics (I guess this affects windows only?).

I will check it with the newest version of validation layers and try to
figure out why they are compaining. In general. these changes are required,
because the layout images are transitioned to is different than the one
specified inside render pass. And proper transitions are necessary in case
of Intel graphics (but the MESA part You mentioned about is interesting).
2016-11-04 11:04 GMT+01:00 Sascha Willems<EMAIL_ADDRESS>
Sry, totally forgot about this PR. I didn't realize that this is required
on Intel graphics, as all the examples run fine on my Haswell Ultrabook
running Ubuntu with the MESA drivers.
While most changes look fine, the changes to the depth/stencil final
layout (https://github.com/SaschaWillems/Vulkan/pull/238/files#diff-
bb472eedb08baf1328e3fe24fbe53158R218) causes validation layer errors for
the layered depth map.
Is that change really required to get these running on Intel graphics (I
guess this affects windows only?).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SaschaWillems/Vulkan/pull/238#issuecomment-258388744,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ6PZ010g-P0_PI_renFtubpw87KbEroks5q6wNDgaJpZM4KCx0f
.

Hello.
I've analyzed the deferredshadows sample once again. I'm wondering if the error You mentioned is reported correctly.
In the deferredshadows You have 3 render passes: 1st for depth data, 2nd for color and 3rd for final deferred pass. In the 1st pass depth/stencil texture needs to be in DEPTH_STENCIL_ATTACHMENT_OPTIMAL layout if we want to render into the texture. But in the 3rd render pass the same image/texture is sampled, fragment shader reads from it. So it can't have DEPTH_STENCIL_ATTACHMENT_OPTIMAL layout. For reading/sampling we should use DEPTH_STENCIL_READ_ONLY_OPTIMAL layout (or SHADER_READ_ONLY_OPTIMAL layout). And the final layout of the 1st render pass is the only reasonable place in which this layout transition should occur.
What do You think?

Any news? As I have written, I think validation layers are wrong here. Spec clearly states in descriptor updates section about layouts: "imageLayout is the layout that the image will be in at the time this descriptor is accessed". And, unfortunately, in the deferred samples, other layout is specified in the descriptor set updates and images are transitioned to other layouts. It does work on Nvidia, but it is a violation of the spec, nevertheless.

I'm currently checking this on AMD hardware to ensure that the changes won't break anything and will be going to check with a recent build of the validation layers to see if the warnings persist.

Just checked on an AMD GCN CPU and I think you're right with the validation layers being wrong. With the current code the shadow attachment is garbled on AMD (but no validation errors), with your changes (that are obviously correct) the shadows render fine but I get validation layer errors, so this may really be an error in the validation. I'll take a deeper look at this (hopefully sometime this week) and see how to report it.

Good news - that I (probably) didn't make any mistake in the PR, and that You agree with my opinion, and that Your code works as expected on the AMD hardware with my modifications. ;-)
Bad news that validation layers are wrong here. This is very confusing for everyone that wants to jump into Vulkan API... :-/
Nevertheless, thanks for the info. I'm waiting for more news from You.

Just a quick note that I'm still actively looking into this and as of now I'm no longer sure if it's really a validation problem. Doing some manual image layout transitions fixes the validation messages, so I think the render pass setup of the example may be wrong.

I think there really may be a problem with validation layers. When the above changes are applied to the code, validation layers report problems only with a layered depth image (the one storing depth values for each light source). There are no problems with layout transitions of other images reported by validation layers.
I've reported an issue on the LoaderAndValidationLayers Github page, maybe they will fix it (and the problem with image layouts in descriptor sets not being tracked).

Thank you very much for reporting this in such detail at the LoaderAndValidationLayers  repo 👍

@Ekzuzy Just checked with the recent valdiation layer fixes and with your changes applied, the messages are gone. Do you want to submit another PR, or is it okay if I apply your changes (the ones that still haven't made it into master) to my current code?

Thanks! :-) I have a newer version of code changes, so You don't have to resolve the conflict. It also fixes problems with SSAO sample. I will prepare a new PR tomorrow at work.

Closing - new PR request will be prepared.


PBR base color export issue

Importing this model... https://sketchfab.com/models/de3051373c3b48bb8280a8ffa61af10e ... on the current master branch gives a correct result in Blender, but incorrect on export.

before
after

Losing AO is expected per #123 but I think there's more happening than that. Compare these ORM textures:

before
after

I took a screenshot of your two ORM maps above, and separated the channels in GIMP.  The red channel has been lost, but green and blue look the same when isolated.
Check your base color images.  I was able to reproduce this, and some of my exported base color textures have extremely bright yellow in them, which appears to be the main cause of the problem here.

Ah you're right, that looks like the cause. Maybe related to https://github.com/KhronosGroup/glTF-Blender-IO/issues/130 and re-rendering textures when we should just copy them?

before
after

This model also has vertex colors — I didn't check to see how/if they're used, but per https://github.com/KhronosGroup/glTF-Blender-IO/issues/127 that's another known issue.

Here's the shader graph generated by the importer:

The vertex colors are certainly one problem.  Search the Sketchfab download for the following string:
    "material": 0,

You will find eleven occurrences of material zero.  Some of the meshes that use it have COLOR_0 vertex colors, and some do not.  This is legal, in glTF, but unfortunate.  I know we fixed a bug in Cesium some time ago, internally splitting materials like this into two, one for the vertex-colored primitives and one for the non-vertex-colored primitives.  Babylon and Three are likewise able to handle this correctly.
But the Blender importer here uses only a single Blender material, and wires up the nodes for vertex colors.  Some of the colors are missing, for example the top of the back of the Llama has no vertex colors, so looks black in the Blender preview.

I suspect this is a separate issue from the base color channel configuration export issue.  The Cyberllama may be displaying multiple bugs.

@emackey You're right, there is maybe a problem in importer linked to material / vertex color, because vertex color is store at primitive level. This is a problem I started to understand in #30

We revisit the bug, if it comes to the export part again.

Also, for the exporter, it would be much more convenient, if the color attribute is just multiplied with the base color.

Problem of material sometimes uses vertex color and sometimes does'nt (#30) is now fixed

Seems problem of exporting is still there
Original glb (in Don's viewer):

In blender after import:

In Don's viewer after glb exporting:

@McNopper You're request about using multiply with color base will be done as part of #78
Will try to do it ASAP

@UX3D-nopper It's done for base color ( texture with or without factor).
Note that it's still TODO for emissive & for extensions

I can not reproduce this on the current master, both the glTF and glb export look fine in Don's viewer.


Readme: Make edits to grammar and fix the typos.

If you would prefer a single commit with the changes, please let me know.

Thanks @lightwavefeesh ! I'll take a look at this soon.

Much appreciated @lightwavefeesh !


[Enhancement] print cpu_cores & mem_limit it clusterStatistics

Fixes #issue
Print cpu_cores and mem_limits in cluster statistics printer.
What type of PR is this:

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

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 the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 24 / 24 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/clone/BackendLoadStatistic.java
22
22
100.00%
[]

:large_blue_circle:
com/starrocks/clone/RootPathLoadStatistic.java
2
2
100.00%
[]

Should also log in BackendCoreStat::setNumOfHardwareCoresOfBe.

[FE PR Coverage Check]
:heart_eyes: pass : 18 / 18 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/clone/BackendLoadStatistic.java
17
17
100.00%
[]

:large_blue_circle:
com/starrocks/clone/RootPathLoadStatistic.java
1
1
100.00%
[]


Nothing happens

Tried the extension but nothing happens :/
It shows up in chrome://extensions/ but nothing happens when I browse csv merges in github.
I can see the tabular UI (from normal github) here
https://github.com/theodi/test-data/blob/master/data.csv
But I only see text there, where I expected to see the UI from csvhub
https://github.com/theodi/test-data/commit/9f391e6e35963b96aa0eed56c20ccd70f326e1f7
Chrome version: 42.0.2311.90 m
Please let me know how can I find more helpful details.

got this in Chome's console:
Uncaught Error: CSVDataError: Illegal Quote [Row:1][Col:1](anonymous function) @ jquery.csv-0.71.js:570$.csv.parsers.parseEntry @ jquery.csv-0.71.js:501$.csv.toArray @ jquery.csv-0.71.js:618(anonymous function) @ csvhub.js:21

Is this project dead?

Not dead, but not getting a lot of time spent on it as it was only ever really a prototype. I admit I hadn't actually noticed this issue, sorry about that; I was away and ignoring all my email at the time! I might have chance to look into it in a couple of weeks, but if anyone else has time before I do, I'll happily merge PRs.

@Floppy any updates?

I've not had chance yet unfortunately. It's becoming obvious that more and more people are actually using this tool though (to my great surprise), so I'll try to get it fixed soon!

Thanks for the update. I'm also interested in using this.

Having the same issue here - would love to be able to use this tool! Thanks :-)

@Floppy Bump! :D.

Apologies for the delay on this. Github had just changed the CSS selectors again. I've got it working again and uploaded a new version. You should get it through autoupdate soon.

Thanks @Floppy! Looking forward to testing it out.

Great stuff, thanks @Floppy , it works again :)


change the comments of Annotation Class [org.apache.dubbo.config.spring.context.annotation.EnableDubboConfig]

In Annotation Class org.apache.dubbo.config.spring.context.annotation.EnableDubboConfig, we can see  the current comments  is:
/**
* It indicates whether binding to multiple Spring Beans.
*
* @return the default value is false
* @revised 2.5.9
/
we know after version 2.6.6, the default value of multiple is true, so the comments need to update, otherwise it will cause confusion, so change it to:
/*
* It indicates whether binding to multiple Spring Beans.
*
* @return the default value is true
* @revised 2.6.6
*/

Codecov Report

Merging #6311 into master will decrease coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #6311      +/-   ##
============================================
- Coverage     60.87%   60.82%   -0.05%
+ Complexity      493      491       -2
============================================
  Files           999      999
  Lines         39930    39930
  Branches       5752     5752
============================================
- Hits          24306    24288      -18
- Misses        12927    12942      +15
- Partials       2697     2700       +3

Impacted Files
Coverage Δ
Complexity Δ

...bo/config/event/listener/LoggingEventListener.java
37.50% <0.00%> (-25.00%)
0.00% <0.00%> (ø%)

...ava/org/apache/dubbo/config/DubboShutdownHook.java
63.82% <0.00%> (-10.64%)
0.00% <0.00%> (ø%)

...e/dubbo/remoting/transport/netty/NettyChannel.java
55.68% <0.00%> (-4.55%)
20.00% <0.00%> (-1.00%)

...ache/dubbo/remoting/transport/mina/MinaClient.java
56.92% <0.00%> (-1.54%)
8.00% <0.00%> (-1.00%)

.../exchange/support/header/HeaderExchangeServer.java
66.98% <0.00%> (-0.95%)
0.00% <0.00%> (ø%)

.../dubbo/registry/integration/RegistryDirectory.java
75.43% <0.00%> (-0.87%)
0.00% <0.00%> (ø%)

.../apache/dubbo/config/bootstrap/DubboBootstrap.java
52.34% <0.00%> (-0.57%)
0.00% <0.00%> (ø%)

.../remoting/transport/netty4/NettyClientHandler.java
59.32% <0.00%> (+1.69%)
0.00% <0.00%> (ø%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0743042...cec2aac. Read the comment docs.

Duplicated


Can it be used to hook imports in react app

Expected Behavior
Integerate it in a react app to hook axios but the logic is not being executed. Expected "in Hooks" to logged.
import Hook from "import-in-the-middle"
Hook(["axios"], (exports, name, baseDir) => {
  console.log("in hook of axios")
})
import axios from 'axios';

Actual Behavior
Nothing is logged.
Steps to Reproduce the Problem
Specifications

Version:
Platform: React.js
Subsystem:

@re-Tick Note that the loader hook must be used, i.e. --loader=import-in-the-middle/hook.mjs. By putting your example in a file and running it with this command-line parameter, I was able to see the log message.
I'll close this, but please feel free to comment again if you think it's not yet resolved.


Use print() function in both Python 2 and Python 3

Legacy print statements are syntax errors in Python 3 but print() function works as expected in both Python 2 and Python 3.

Looks like just changing the base to dev adds some merge conflicts.  Would it be easier to make your changes against that branch?


MRTK line renderer fix

Fixes: #3580

@keveleigh I'm confused about this one. According to the mrtk_development branch, the merge is empty. But this commit shows one file change.

@keveleigh should I create another pullrequest or can this be fixed? This change is definitely missing in mrtk_development, even though it's avaiable here.

should I create another pullrequest or can this be fixed? This change is definitely missing in mrtk_development, even though it's avaiable here.

I think you'll need to create another PR. This looks to be caused by the same thing that happened in #3579, where the commit (and a revert commit) was included in a different PR (in this case, #3584).


Build Command Failed

Hello Sir when i import this sample its fire this error:
Build command failed.
Error while executing process F:\AndroidStudio\android_sdk\cmake\3.6.4111459\bin\cmake.exe with arguments {--build E:\CurentWork\AndroidFaceDetectOpenCV-master\AndroidFaceDetectOpenCV-master\app.externalNativeBuild\cmake\debug\armeabi-v7a --target native-lib}
ninja: error: '../../../../src/main/jniLibs/armeabi-v7a/libopencv_java3.so', needed by '../../../../build/intermediates/cmake/debug/obj/armeabi-v7a/libnative-lib.so', missing and no known rule to make it
How to shortcut this issue? I didn't understand exact mistake.

I am having same error. Please tell us the solution

I will check, sorry for the delay, wait for news

Hello guys,
I made several changes to the project including upgrading the version of the OpenCV SDK and Android. Please review the project README for execution. Any questions just let me know. It is very important to follow the steps of the README mainly those listed below:

Make sure you have Android SDK up to date, with NDK installed
Download OpenCV SDK 3.4.3 for Android from OpenCV.org and decompress the zip file.
Clone this project
Create a symlink named jniLibs in app/src/main that points to ${YOUR_HOME_OPENCV_SDK}/sdk/native/libs
In app/CMakeLists.txt change line 9 to points to ${YOUR_HOME_OPENCV_SDK}/sdk/native/jni/include
Sync gradle
Run the application


Log only specific network requests

Right now FLEX is logging every single network call in my App, including different Google Analytics calls and other network calls from libs that I'm using. I would like to have only those requests and responses logged, that are called against the App's backend. Is there any easy way of doing that?
Thanks
EDIT:
I found out there is a blacklisting feature in the current branch, but this is not included when I install from cocoapods...

You can specify a branch in your podfile


Correct name of docs extra, bump to Python 3.10

Closes #7

Codecov Report

Merging #8 (531e2f9) into dev (1b42ce6) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##             dev      #8   +/-   ##
=====================================
  Coverage   50.0%   50.0%
=====================================
  Files          1       1
  Lines          6       6
=====================================
  Hits           3       3
  Misses         3       3

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1b42ce6...531e2f9. Read the comment docs.


mapProps leads to undefined props.value on a custom control

Hi,
great to see v1 is is already there! Thx. 👍
Just created a custom control and figured out on v1.01 it do no longer pass the value to my custom component when mapProps is used. Here my simple example:
class CustomInput extends Component {

    constructor(props) {
        super(props);
    }

    render() {
        console.log('value: ', this.props.value); // will be undefined when using in conjunction with mapProps
        return (
            <input type="text" {...this.props} />
        );
    }
};

// somewhere else
<Control
    model={'checkoutStart.test'}
    component={CustomInput}
    mapProps={{
        error: (props) => (!!props.errors), // any kind of mapProps
    }}
/>

If the <Control /> do not have a mapProps prop it seems to work ...

Just added the ability in fbe3ee8 to extend existing mapProps if you define your control like this:
-<Control
+<Control.text
    model={'checkoutStart.test'}
    component={CustomInput}
    mapProps={{
        error: (props) => (!!props.errors), // any kind of mapProps
    }}
/>

Otherwise, you have to explicitly map { value: (props) => props.viewValue } in the props, and here's why (updated the docs with the below answer):

One important thing to keep in mind is that there is no single value for a <Control>; rather, there are two types of values (that are equivalent, more often than not):

modelValue - the exact value of the model in the store's state
viewValue - the displayed value of the model in the component's state

For example, if a text control has updateOn="blur", its viewValue will represent what is being typed in the input, whereas the modelValue will represent the persisted value, once the input is blurred.
Because of this, you will want to map the viewValue to a custom control's value if you wish to externally update the value:
const CustomInput = (props) => (
  <div className="custom-input">
    <input type="text" {...props} />
  </div>
);

const CustomInputControl = (props) => (
  <Control
    component={CustomInput}
    mapProps={{
      value: (props) => props.viewValue,
    }}
    {...props}
  />
);

Alternatively, you can just assign existing mapped props to your custom control:
// the prop mapping of Control.text is used below:
const CustomInputControl = (props) => (
  <Control.text component={CustomInput} />
);

Okay. Yes, I saw the two differences but I think my issue is, that the value is undefined even if I map it with mapProps like: { value: (props) => props.modelValue }.  I logged the props within a map-function and saw modelValue is undefined.
I've set the initial-state for formReducer and modelReducer but props.modelValue in the mapProps-function is undefined.
In my case I want to accomplish two things:

Have an custom control which should display the modelValue initially. I tried to pass a initial-state to the modelReducer and the formReducer. This works when I use props.fieldValue.value within my mapProps-function but won't work with props.modelValue?
Is it by design?

My custom control uses validators which seem to run after mount. The validation always fails even if I set a valid value with the initial-state. I'm not sure if this is by design ...

What does your store look like?

Basically something like:
const combinedReducer = combineReducers({
    myForm: modelReducer('example', {
        inputValue: '500.00',
    }),
    myModel: formReducer('example', {
       inputValue: '500.00',
    })
});

// ...

// ...
myForm: modelReducer('example', {
// ...

Make sure that the model, which is the first argument to modelReducer, is the exact path to the model's state in the store. So in the above example, it should be 'myForm' or whatever you named your model.

Thank you, that was my issue!


Correct example

Closes https://github.com/MicrosoftDocs/office-docs-powershell/issues/7210

@Kateyanne Please merge this PR. Thanks

Docs Build status updates of commit 32ffc69:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Remove-CsOnlineApplicationInstanceAssociation.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 4215cd2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Remove-CsOnlineApplicationInstanceAssociation.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Bump version 0.2.29

Coverage remained the same at 94.415% when pulling 07ea40e06f3c5f53d9491db0b16511152ef87045 on app_access_token_by_get into 1fe599e6580349d36663e49f9ec3c4b997442e01 on master.


Changing icon colors

There doesn't seem to be a way to change or disable the icon colors. Is that right?

yep, currently, the related modules (header/modules/socials and footer/modules/socials) do not support disable or change icon's colors.
but I could add some parameters to disable all social icons colors, not sure if it fit your need.but I could add some parameters to disable all social icons colors, not sure if it fit your need.
PR are welcome if you think some icon color are incorrect.

But I could add some parameters to disable all social icons colors, not sure if it fit your need.

This is actually what I want to do. I'd like to disable the color on all of the icons. I personally find the colored icons add visual noise that I'd like to avoid in my use case.

Available since github.com/hbstack/footer/modules/socials v0.2.0, in short:
params:
  hb:
    footer:
      socials:
        _color: false
        # ...

See the footer socials module for details.
The header socials module is non-colorful, no need to change.

Thanks! That works great!
I think the author page social icons is the only one missing this feature now. I'm not sure which HB module that one is.

I think the author page social icons is the only one missing this feature now

Ah, I forgot that, will create a PR later.

Available since github.com/hbstack/blog v0.13.0, same format as above (author page's front matter).

Thank you!


Remove hard coded strings

Use string resources instead, so it will be easier to translate the app into other languages

How can i work on this project and i want to contribute on it , and i am a new bie in android development.

Hi @myselfdeepdas,
thanks for your interest. Really appreciate it!
This issue was created because most of the strings for the UI are hard coded. We should use string ressources instead. The task is: Moving these strings into string ressources.
If you want to contribute, just fork the repository and work on the issue. After finishing the task, please create a merge request here.
You can find a step by step guide on setting up your environment in the wiki. Unfortunatly the wiki is only available in German right now. We will be translating it to English later. But there are also some screenshots which will help you.
Feel free to ask if you have any more questions :)
Thanks and regards!

Hi. So I forked the project to solve the issue of hardcoded strings. I copied the ids of textviews, buttons and named is as string-name in resources. But the problem I am facing is that I encountered textviews with SAME id but DIFFERENT texts. So can you advise me what I should do about that? Should I change the ids of these textviews by myself?

Hi @sdarshil6,
thanks for contributing! You will have to give them other names. That should fix it. Can you please show me the error you get?

Hi @sdarshil6,
thanks for contributing! You have to give them other names. That should fix it. Can you please show me the error you get?

Oh! I can give it other names. Thanks. I thought I had to ask you what names I should give. Good. I will do that. The error is that I can't gives two string resources the same names.

Hi @sdarshil6,
thanks for contributing! You have to give them other names. That should fix it. Can you please show me the error you get?

Oh! I can give it other names. Thanks. I thought I had to ask you what names I should give. Good. I will do that. The error is that I can't gives two string resources the same names.

Hi @sdarshil6,
thanks for contributing! You have to give them other names. That should fix it. Can you please show me the error you get?

THIS IS THE ERROR THAT I AM FACING :


sqlite: consider dropping upsert for replace

Background in slack.
Do we need upsert, or would replace be good enough?
https://github.com/iterative/sqltrie/blob/99ee92982aefbe99d42eff40161aa2a828efa3eb/src/sqltrie/sqlite/sqlite.py#L164-L167
It would be nice to work with older sqlite versions.
cc @efiop

Related https://github.com/iterative/sqltrie/pull/10
We had some problems with views and INSERT OR REPLACE before, but now it view using original connection it might actually be enough.

Ah, still can't use it, unfortunately. REPLACE deletes old record and so always updates id(rowid), which is breaking the table. We'll have to go with either two queries or a trigger.


Connect PSALoadingIcon shared component to selector #723

Integrated the shared Loading Spinner

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.


Using attribute name in function with same name

Hey Jens,
I got a model that has the attribute "features" in it's mongo document. Now I create a public function within the model which is called features(). If I now use $this->features inside this function I receive the following error:
Undefined property: xxx\FooBar::$features (View: /var/www/xxx/resources/views/foobar.blade.php)

I figured that it might be related to the magic function calling from Laravel. Do you know more regarding this topic? I would love to call that function this way since it's merging some data from joined Models so I can't work on the attribute $foobar->features directly.
at HandleExceptions->handleError('8', 'Undefined property: xxx\FooBar::$features', '/var/www/xxx/app/Foobar.php', '45', array()) in Foobar.php line 45
at Foobar->features() in Model.php line 240
at Model->getAttribute('features') in Model.php line 3263
at Model->__get('features') in Foobar.php line 45
at Foobar->features() in f916cf457953d0604c10d415ab79e8c3 line 7

$this->attributes['features']

Thanks spawn-guy. But that does not explain why I can't use the same name.
Is it better to always use $entity->attributes['features'] instead of $entity->features? Or is there not difference at all?

@daPhantom i dont know why you u make a make a function with the same name as your attribute, but what i can say is, __get magic in model will call Model->getAttribute('features');
that have a function like this
`public function getAttribute($key)
{
$inAttributes = array_key_exists($key, $this->attributes);
	// If the key references an attribute, we can just go ahead and return the
	// plain attribute value from the model. This allows every attribute to
	// be dynamically accessed through the _get method without accessors.
	if ($inAttributes || $this->hasGetMutator($key))
	{
		return $this->getAttributeValue($key);
	}

	// If the key already exists in the relationships array, it just means the
	// relationship has already been loaded, so we'll just return it out of
	// here because there is no need to query within the relations twice.
	if (array_key_exists($key, $this->relations))
	{
		return $this->relations[$key];
	}

	// If the "attribute" exists as a method on the model, we will just assume
	// it is a relationship and will load and return results from the query
	// and hydrate the relationship's value on the "relationships" array.
	if (method_exists($this, $key))
	{
		return $this->getRelationshipFromMethod($key);
	}
}`

now you see there is
if (method_exists($this, $key)) { 	return $this->getRelationshipFromMethod($key); }
that will check your model class when u call $this->features , the selection code above will add relations attribute to model, hope it answer your question =D

@daPhantom to understand recursion you need to understand recursion.
also this is not a Moloquent issue.

Well this is kind of a recursion issue - you are right. However you are not right in pointing out that this isn't a Moloquent issue since it is. Check the code provided by darkeus and read the comment regarding the last if:
   // If the "attribute" exists as a method on the model, we will just assume
   // it is a relationship and will load and return results from the query
   // and hydrate the relationship's value on the "relationships" array.

But what I don't get is that the first if should already be returning the value instead of the last if returning the relation and therefore perform an early exit.
The error I receive in the end is total useless and does not point to the root of this issue which is reflection.

@daPhantom sorry i have a few code that i forget to post here, the function getAttribute i post above is from \Illuminate\Database\Eloquent\Model.php and yet i dont notice there is a override function in \Jenssegers\Mongodb\Model ,here the code
/**
 * Get an attribute from the model.
 *
 * @param  string  $key
 * @return mixed
 */
public function getAttribute($key)
{

    // Check if the key is an array dot notation.
    if (str_contains($key, '.'))
    {
        $attributes = array_dot($this->attributes);

        if (array_key_exists($key, $attributes))
        {
            return $this->getAttributeValue($key);
        }
    }

    $camelKey = camel_case($key);

    // If the "attribute" exists as a method on the model, it may be an
    // embedded model. If so, we need to return the result before it
    // is handled by the parent method.
    if (method_exists($this, $camelKey))
    {

        $relations = $this->$camelKey();
        // This attribute matches an embedsOne or embedsMany relation so we need
        // to return the relation results instead of the interal attributes.
        if ($relations instanceof EmbedsOneOrMany)
        {
            // If the key already exists in the relationships array, it just means the
            // relationship has already been loaded, so we'll just return it out of
            // here because there is no need to query within the relations twice.
            if (array_key_exists($key, $this->relations) && !$this->serialized)
            {
                return $this->relations[$key];
            }

            // Get the relation results.
            return $this->getRelationshipFromMethod($key, $camelKey);
        }
    }

    return parent::getAttribute($key);
}

you see in moloquent it is checking the method first then return the method value if exists, but on \Illuminate\Database\Eloquent\Model.php getAttribute() it will check the attribute first instead of method_exists function, this is because moloquent extends from \Illuminate\Database\Eloquent\Model.php and using it parent function at the end of function , instead of adding some logic like its parent
$inAttributes = array_key_exists($key, $this->attributes);

// If the key references an attribute, we can just go ahead and return the
// plain attribute value from the model. This allows every attribute to
// be dynamically accessed through the _get method without accessors.
if ($inAttributes || $this->hasGetMutator($key))
{
    return $this->getAttributeValue($key);
}

// If the key already exists in the relationships array, it just means the
// relationship has already been loaded, so we'll just return it out of
// here because there is no need to query within the relations twice.
if (array_key_exists($key, $this->relations))
{
    return $this->relations[$key];
}

before the
    $camelKey = camel_case($key);

    // If the "attribute" exists as a method on the model, it may be an
    // embedded model. If so, we need to return the result before it
    // is handled by the parent method.
    if (method_exists($this, $camelKey))
    {

        $relations = $this->$camelKey();
        // This attribute matches an embedsOne or embedsMany relation so we need
        // to return the relation results instead of the interal attributes.
        if ($relations instanceof EmbedsOneOrMany)
        {
            // If the key already exists in the relationships array, it just means the
            // relationship has already been loaded, so we'll just return it out of
            // here because there is no need to query within the relations twice.
            if (array_key_exists($key, $this->relations) && !$this->serialized)
            {
                return $this->relations[$key];
            }

            // Get the relation results.
            return $this->getRelationshipFromMethod($key, $camelKey);
        }
    }

so yeah to avoid confusion, you better use $this->attribute['features'] instead of $this->features, too much magic called when you call $this->features

Thanks @darkeus! That makes a lot more sense actually than with the previous code snipped.
So as a rule of thumb you can say that you should always stick with $this->attributes['key'] instead if $this->key when not using a relation. Yet alone to avoid magic functions, reflection and unnecessary additional execution time.

@daPhantom yep $this->key is  better used outside of the Model class, well you can use the $this->key but you should know what it do, then again if you want to make a function that will act like an attribute you better use acessor way getKeyAttribute($value) , using this will make your model accessible like $model->key, it's on getAttribute() magic logic.
And if you actually want to make features as a function then yes to call an attribute inside model class better use $this->attribute['key'], but if you actually want to make features() function as accessor then that is a wrong way.
sorry my bad english =p

@darkeus Yes. It is kind of an accessor but it combines features from multiple relations instead of just FooBar. Just like this:
public function features() {
    return array_merge($this->relationOne->attributes['features'], $this->attributes['features']);
}

Thanks again for your help. I like magic functions and reflections but sometimes it's not bad to avoid them and just stick to direct functions. Most of the time "magic" is CPU intensive.

@daPhantom oh actually in your case you can write it like this
public function features() {
    return array_merge($this->relationOne->features, $this->attributes['features']);
}

because relationOne magic wont affect your current model magic, unless your relationOne have another features() function, and actually i dont know magic is CPU intensive. from the magic logic it is quite good and direct, maybe the "intensive" refers to how PHP engine call the magic function?

@darkeus You are right but as I pointed out earlier I would like to stick to a fixed scheme then. First to avoid magic and second to have it stringent throughout the project. This way I know instantly if it is a relation or an attribute ;)

@daPhantom  i see that's answer all my question =) good luck


Linear Progress Indicator does not match the material spec

The material spec calls for a height of 4dp but it is currently set to 6dp (with no way to change it).

Regarding the Linear Progress Indicator's material specs here and here, the animation duration is actually 2000 ms while in flutter's implementation it's 1800 ms.
Is this intentional ?


Feature Request: Custom Style for Notebooks

I use jupyter notebook in vscode, and seeing the font setting also applies to font for notebooks is awesome (I didn't find a way to do that)!
(I'm not sure if it's already possible, but) It would be good to provide some setting options or guides to further customize the look of notebooks. E.g., what I want to change most is to make the markdown headers bold and numbered.
Thanks for the great work!

Open dev tool
Find desired element/part
apply the style
  "apc.imports": [ "/path/to/style.css" ]

or
  "apc.stylesheet": {
    ".notebook-editor .mtk1": "font-weight: bold; color: red"
    }

while your example works as expected, the exact example doesn't work (also why I was stuck):
the cell needs to be markdown and needs to be rendered (before/after rendering):

before rendering it's similar except that it's mtk11 and it's working;
after rendering it's like this, and the selectors there seems not working.

Could you help give some hints?

sorry never used notebook
after "render" becomes iframe
unfortunately, until I find a suitable way to insert styles inside iframes, customization  is not possible

https://github.com/drcika/apc-extension#apciframestyle
"apc.iframe.style": "/Users/path/style.css",

h1 {
  color: red
}

only applies inside iframes
but also on all iframes such as extension view
keep that in mind when writing styles

Looks nice and will try it out!
One more question: is it possible to directly write styles in settings.json, just like apc.stylesheet?

it complicates things a lot, and settings.json is already too bulky
I follow the changes in the custom file, it is only necessary to open the tab again

seems I failed to make it running:

extension v0.2.3,
created a file as the example above and saved to (win10) D:\vscode_notebook.css,
added setting of "apc.iframe.style":"/D:/vscode_notebook.css",
reopening notebook tab and the h1 rendered title doesn't change.

somehow they managed to protect themselves on windows, it should work now
but it has a small limitation
if a tab with an iframe is open when starting vscode, the tab needs to be reopened for the styles to apply

doesn't seem to be working anymore


Updating websockets example and readme

Updating Websocket Example Documentation
Changes

Adding a README for the websocket service

Includes how to get setup and started

Moved the websocket requirements.txt file to the root of the project and renamed it
Updated how events are added to the queue and logged to the console
Created a run_websockets script, usage is in the websocket-service README
Updated the setup script to accept a --websockets flag and install the websockets requirements text file if provided.

QA

Run through the setup and getting started steps in the README docs, any failures should be fixed in this PR prior to merging

cc: @synesthesiam


Remove TCE steps from release checklist

Turns out for now we still need to do this. Will re-open when we know the TCE stuff is gone forever.


Make 'chai' and 'protractor' peer dependencies.

Apologies for the failing build - I'm on a Windows environment and the build/tests simply don't run locally, so I couldn't test beforehand. The prinicple is sound though - since this is a plugin for both Protractor and Chai, both should be defined as peer dependencies (see https://nodejs.org/en/blog/npm/peer-dependencies/). This should fix the type error I mentioned in my commit comment, as chai-smoothie should use whichever version of protractor the user is running.
I'm in the office now so don't have more time to fiddle with it now, but will try to get back to this at some point.

Hey @mdaniline and thanks for the PR! The failing build seems to be caused by protractor introducing breaking changes to its public APIs while forgetting to change their major version number...
I agree with your point, but I'm not sure

All good after changing the min version of protractor to 4.0.9. Thanks for the PR 👍


internal/contour: add support for TCP Forwarding

Updates #787
This PR adds preliminary support for forwarding TLS encapsulated TCP
sessions.
This is supported only on ingressroute objects with a new spec.forward
key. The presence of spec.forward causes contour to ignore the contents
of spec.routes, although spec.routes must be present to pass validation.
spec.forward permits multiple services, although currently only one is
used.

Signed-off-by: Dave Cheney<EMAIL_ADDRESS>

thanks a lot


Please add support for "MI Push", the most popular message push server like GCM in China

this is link https://dev.mi.com/console/doc/detail?pId=1252
By some reason of connecting of Google, MI Push is the most popular message push server in China, just like GCM in other place. It will greatly helpful to popularize Flutter in China.
It's very appreciate for Flutter's work!

is it possible for supporting that?

cc @Hixie

Closing as out of scope; this is something that would be best served by a community-owned plugin.


Update "onceSharerReadyForOffer_" behaviour in remote-instance.ts.

Fixes https://github.com/uProxy/uproxy/issues/1297
Instead of keeping one promise (onceSharerReadyForOffer_) which tracks if RemoteConnection's rtcToNet_ is ready AND if the next signal to be handled is an offer, this is now split into two promises: onceNextSignalIsOfferFromClientPeer_ and connection_.onceSharerCreated (i.e. once rtcToNet_ created)
I realize the variable names are getting pretty long, please lmk if you have naming suggestions!
Ran grunt test and tested manually.

  Is it really needed to have this extra Promise along with its fulfill and reject methods to generate errors if we get a CANDIDATE before an OFFER?  I believe rtcToNet will already fail in that case so it doesn't seem like we should be trying to so hard to fail gracefully there

Comments from the review on Reviewable.io

src/generic_core/remote-instance.ts, line 200 [r2] (raw file):
This seems a little weird, because receivedOtherSignalFromClientPeer_ is set elsewhere to a reject function.  That means for a typical proxy session, we would first fulfill the promise, then call reject on the promise (since a CANDIDATE message will arrive after the OFFER).  I think this will probably leave the Promise in a Fulfilled state but I could imagine it getting weird in other environments (e.g. tests which use a different Promise library).

src/generic_core/remote-instance.ts, line 288 [r2] (raw file):
This name is just too crazy

Comments from the review on Reviewable.io

Note: socks-to-rtc should never generate/send a candidate before an offer - if it does, that is a bug. I'm not sure I understand the issue here - lets chat later.

src/generic_core/remote-instance.ts, line 200 [r2] (raw file):
We should discuss with Lucas a bit more - I'm hoping we might be able to remove some of this extra checking and just rely on socksToRtc and rtcToNet to do the right thing regarding message ordering....but one other idea I had is that if we do still want checks in remote-instance.ts, this seems like a case where we might do better with a boolean (something like "hasSeenOffer") than a Promise

Comments from the review on Reviewable.io

Thanks for taking a look + the helpful comments -- I think you're right and a simple hasSeenOffer boolean will simplify everything significantly -- let me try!

Comments from the review on Reviewable.io

Just tested manually and ran grunt test with the new changes -- ptal, thank you!!

:+1:


Inital Setup

Name of the PR
:recycle: Current situation & Problem
Link any open issues or pull requests (PRs) related to this PR. Please ensure that all non-trivial PRs are first tracked and discussed in an existing GitHub issue or discussion.
:gear: Release Notes
Add a bullet point list summary of the feature and possible migration guides if this is a breaking change so this section can be added to the release notes.
Include code snippets that provide examples of the feature implemented or links to the documentation if it appends or changes the public interface.
:books: Documentation
Please ensure that you properly document any additions in conformance to Spezi Documentation Guide.
You can use this section to describe your solution, but we encourage contributors to document your reasoning and changes using in-line documentation.
:white_check_mark: Testing
Please ensure that the PR meets the testing requirements set by CodeCov and that new functionality is appropriately tested.
This section describes important information about the tests and why some elements might not be testable.
:pencil: Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[ ] I agree to follow the Code of Conduct and Contributing Guidelines.

Reviewing 🙌
Feel free to push any updates in case you have to, but please inform me on slack after you update

@Basler182 @eldcn I suspect we will close this PR in favor of #2 and #3 as we move along with the repo setup?

yes, we will close it once all conversations are solved.


🎮 Game Request
Be fast enough to clean the area before it get really crowded. Only few rules: simple move the colored boxes through the wall with the same color. You can use both mouse and touch-screens.
Point down the features
To get more points simple try to swipe simultanously. Have fun!
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @S-ishita !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @S-ishita ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Support for Nest 2FA?

Hello,
First, thank you for making this plugin for Homebridge available. I was curious if support for the OAUTH / 2FA authentication that is in homebridge-nest might be brought into this project?

Yeah, I'm seeing:
[2018-2-10 08:04:33] [Nest-cam] Initializing Nest-cam platform...
[NestCam]Failed to request access token. The username and password do not match

Presumably, this requires a "username" and "password", instead of the "token" from the other library. Bit of a bummer. 😞

I would also like to see token support added like Homebridge-nest supports. Thanks.

I don't think this can happen, stepping through the code it looks like this plugin depends on a deprecated API that existed when these were still Dropcams. Only the camera v1 API can tell you how to pull video from a nest cam, the new APIs do not.  The only documentation for this API I could find is in the patent filing:
https://patents.google.com/patent/US9788039
I'm kind of surprised Google hasn't killed this off yet actually.

This is the API the app is using I believe.
Sent from my iPhone

On Mar 19, 2018, at 1:22 PM, Ted Potma<EMAIL_ADDRESS>wrote:
I don't think this can happen, stepping through the code it looks like this plugin depends on a deprecated API that existed when these were still Dropcams. Only the camera v1 API can tell you how to pull video from a nest cam, the new APIs do not. The only documentation for this API I could find is in the patent filing:
https://patents.google.com/patent/US9788039
I'm kind of surprised Google hasn't killed this off yet actually.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Just to clarify this thread, does this plugin not support fully secured Nest accounts (ie 2 factor)? And based on the API limitations the plugin would not be possible when using more modern/secure API?
Was thrilled to see Nest Cam is now supported since love Nest and Nest Protect integration with Homebridge and Cam's was the one omission though of course wouldn't be able to disable 2FA since then anyone who guessed/found the login would have full access to our home making it probably the most important account to have 2FA on other than maybe email. Thanks!


Cannot use treesit-langs on Emacs 30 (last commit)

Hello,
Thank you for this package,
I presume that this package is in an early stage, but I wonder if it is usable?
I'm trying to use it with Emacs 30, compiled with tree-sitter support, I can download the grammars (the version in the package 0.12.0 doesn't match the version in the repo 0.12.12, I installed it manually).
However, I didn't get so much from it, for example, if I call the command treesit-hl-enable in, let's say c-mode or c-ts-mode, I get treesit-hl-enable: No query patterns for c. I get the same message in any other mode. Even if the queries are available and the binaries are installed correctly.
Edit 1
A sub-problem was that the (treesit-langs--hl-query-path lang) was returning a file which doesn't exist. When I tracked this down, It turned out that the queries directory was available in the straight/repos directory but not the straight/build one, I fixed this by changing straight's recipe. Now the treesit-hl-enable seems to be happy (no more No query patterns... message. However, I didn't notice any difference in the syntax highlighting before and after calling it!
(use-package treesit-langs
  ;; Using this recipe fixes the queries problem
  :straight (:host github :repo "kiennq/treesit-langs" :files (:defaults "*"))
  :config
  (treesit-langs-install-grammars :skip-if-installed "0.12.12"))

Edit 2 (MAYBE SOLVED!)
I was using treesit-hl-enable on X-mode, but when I switched to the X-ts-mode, it worked. I guess I can close this issue. However, I would like to know if I'm guessing right: Is treesit-hl-enable only supports the new X-ts-modes, or it can support the classic X-modes?.

Here is my config:
(use-package treesit-langs
  :quelpa (treesit-langs :repo "kiennq/treesit-langs"
                         :fetcher github
                         :files ("treesit-*.el" "queries"))
  :defer t
  :hook ((prog-mode text-mode) .
         (lambda ()
           (ignore-errors
             (treesit-hl-enable))))
  :custom
  (treesit-langs-grammar-dir (expand-file-name ".cache/tree-sitter/" user-emacs-directory))
  (treesit-langs-git-dir nil))

If you don't have any parser, this package should download the latest version from the Github release, else you can download the latest parsers (on-demand) by using C-u M-x treesit-langs-install-grammars without having to go to Github to check

Thank you for the answer, I'm using it side-by-side with the tree-sitter-langs, it works fine with X-ts-modes.
Thanks again!

@abougouffa I've fixed the issue of not highlighting in non -ts-mode. You can try it if you want now


Streaming data?

Is it possible to stream some text data from generator?
falcon example
flask example

I solved this issue by code below
@hug.format.content_type('text/csv; charset=utf-8')
def format_as_csv_stream(data, request=None, response=None):
    now = datetime.now().strftime('%Y-%m-%d %H:%M:%S')
    response.append_header('Content-Disposition',
                           ('attachment; filename="Download %s.csv"' % now))
    response.stream = data

@hug.post("/test", output=format_as_csv_stream)
def csv_test():

    return some_data_stream

Does anyone have a working example of this working.  I can't make the above work.
Traceback (most recent call last):   File "/usr/lib/python3.5/socketserver.py", line 313, in _handle_request_noblock     self.process_request(request, client_address)   File "/usr/lib/python3.5/socketserver.py", line 341, in process_request     self.finish_request(request, client_address)   File "/usr/lib/python3.5/socketserver.py", line 354, in finish_request     self.RequestHandlerClass(request, client_address, self)   File "/usr/lib/python3.5/socketserver.py", line 681, in __init__     self.handle()   File "/usr/lib/python3.5/wsgiref/simple_server.py", line 138, in handle     handler.run(self.server.get_app())   File "/usr/lib/python3.5/wsgiref/handlers.py", line 144, in run     self.close()   File "/usr/lib/python3.5/wsgiref/simple_server.py", line 36, in close     self.status.split(' ',1)[0], self.bytes_sent AttributeError: 'NoneType' object has no attribute 'split'
I'd also be happy to see an example of non streaming return of CSV data.
Thanks


Support deploy Lambda application from source code

What this PR does / why we need it:
With this PR, I did

Introduce two Lambda cloudprovider client's methods: CreateFunctionFromSource and UpdateFunctionFromSource and refactor Lambda clooudprovider client code follow DRY idea.
Update Lambda function manifest and update Lambda executor build logic to support zip packing function code for Lambda deployment.

Which issue(s) this PR fixes:
Part of #2605
Does this PR introduce a user-facing change?:

Add ability to deploy Lambda application from source code

We know the context of why we need this kind of change, but it would be so helpful if you could mention the review point, what part we should focus on 😸 (especially in the case that the linked issue covers nothing at all)

Thanks for comment, just updated the issue content for context of this change 😉

Looks good. Let's merge and see how it works.
/lgtm


A few misc. touchups

The first fixes #239 and the latter two are just tidiness.

:eyeglasses: @bradengroom @pacejackson


Does not send 2FA code request

Describe The Bug:
While setting up for the first time, entering the email address for a valid account and clicking the “REQUEST 2FA CODE” button does not send the code.
To Reproduce:
Attempt to set up the plug in for the first time, fill in an email with a valid account, and click the “REQUEST 2FA CODE” button
Expected behavior:
A code should be sent.
Logs:
There is no information shown in the logs

Plugin Config:
{
    "platform": "CyncLights",
    "name": "CyncLights"
}

Screenshots:

Environment:

Plugin Version: 1.5.1
Homebridge Version: 1.7.0
Node.js Version: 18.17.0
NPM Version:
Operating System:  	Raspbian GNU/Linux Bullseye (11)

I'm not able to reproduce this on my real installation or development homebridge.  Can you enable debug logging and try again?  Do you see the blue box in the corner saying that the code was sent?  Can you send me a HAR file from your browser so I can see what communications are happening with the homebridge server?

I am experiencing the same issue.
Plugin version: 1.5.2
Homebridge version: 1.7.0
Node.js version: 20.10.0
Operating system: Windows 10 VM install
Neither the send 2fa nor the submit buttons seem to do anything. The browser network tools show nothing at all when either button is pressed. Referring to your above comment, there is no blue box in the corner. Nothing retains on the logs because it seems the buttons do not actually trigger any sort of event at all.

Found the issue.  Should be fixed in 1.5.3

You're the man thank you for your work on this.


dxDataGrid with webapi

Hi team,
This project simulates a webapi service returning a data promise.
Why dxDataGrid does not show the data the first time?
I need to click the refresh button to display the data, but with it he repeated the trip in "simulated webapi".
How to work?
Best regards!

Hello,
The Load method should return promis.
In your example, the method returns "undifined" until data is loaded
For example:
    return this.heroService.getHeroes()
},```

```getHeroes() {
    return new Promise<Hero[]>(resolve => resolve(HEROES));
  }```

Hi,
thank you dxvladislavvolkov!


Pipelines Host Environment - Doesn't work until environment is converted to managed

I tried deploying the Power Platform Pipelines to an environment with Pay-as-you-go enabled. But it does work after I enable the environment to be managed. Does the host environment need the license as well? If so, please update the documentation.

Assigning to @caburk since this seems to be related to Overview of pipelines in Power Platform


Adding support for annotated health states

Add the ability to display details regarding a health state, whether it be text or a link to another resource, such as a particular Splunk log/report.
Server:

Change the data model to support an AnnotatedHealthState object
Refactor the codebase in response to the data model change
[Possible] offer endpoint CRUD access for the AnnotatedHealthState entity
Client
Select and display details on the Node details pane

Willie said that server(3) was unnecessary, because we shouldn't allow an agent to query for all AnnotatedHealthStates - they will always be requested in the context of a Node.

Re (3) above: more like right now there's no use case for repo access, and so I don't want to commit the API to supporting that at this time. If such a use case emerges then of course we would add the repo.

Also, we are going to need to coordinate this with Eos as it will be a breaking change.

Done


Include the directory we tried in tmpDir error

This error is currently hard to debug, because we don't actually include which temporary directory didn't exist.

@swift-ci please test


files selection is no longer reflected in the URL

We used to get URLs like
https://gui.dandiarchive.org/#/folder/5e60c14f81bc3e47d94aa012/selected/item+5e60c19381bc3e47d94aa014
with multiple items listed in the url if multiple files were selected.  That allowed to copy/paste such urls into dandi download invocation to streamline getting specific files.  Currently, with https://gui.dandiarchive.org/#/file-browser/folder/5e7160163da50caa9adafe6c UI it seems no longer possible.  That in effect disables  ability to download any specific file (or selection of them) via client.  There is Download (zip) for a the selection but likely it would be gone (#267)

+1 to having multi-select download via the cli.

This is now tracked in https://github.com/dandi/dandi-cli/issues/183.


[BUG] OpenSearch Reporting CLI Lambda not evaluating certain environment variables

What is the bug?
When using the OpenSearch Reporting CLI Lambda function, the following environment variables are not evaluated correctly.  Instead they are using the default values.

OPENSEARCH_EMAIL_SUBJECT
OPENSEARCH_EMAIL_NOTE

How can one reproduce the bug?
Follow the instructions here (https://opensearch.org/docs/latest/dashboards/reporting-cli/rep-cli-lambda/) and set any of the above environment variables on the Lambda function instead of passing them as the event object.
What is the expected behavior?
Expectation is that the email sent by the Lambda function would contain a non-default subject and note.
What is your host/environment?
N/A
Do you have any screenshots?
See description for observed behavior.
Do you have any additional context?
It appears the following code function causes bypass of the environment variables: https://github.com/opensearch-project/reporting-cli/blob/af8d3073ec5488d487410f6e70a626f970399f05/src/arguments.js#L78

Hi @aaronbrighton, this will be fixed in next release v1.1.0.
If you would like to try/test before the release, you can refer to doc for building docker image from source code https://github.com/opensearch-project/reporting-cli/blob/main/docs/examples/lambda_container_image_from_source.md.


fix: ensure the normal Basic CC values are only exposed if they should be, even with the compat event enabled

fixes: https://github.com/zwave-js/node-zwave-js/issues/5784

@zwave-js-bot automerge

Hello,
I have devices ( Heatit TF016 / TF021) where I need basic CC for automation. In the past I used the basic number entity and later the light entity, now there are no basic entity. How could I change this?

Hello, I have devices ( Heatit TF016 / TF021) where I need basic CC for automation. In the past I used the basic number entity and later the light entity, now there are no basic entity. How could I change this?

Did you get to the bottom of this? I also have the TF021 (v1.92) with no relay status to the controller. There is a issue https://github.com/zwave-js/node-zwave-js/issues/4688 that also handles this issue if still interested?

Yes,
@AlCalzone solved it by making changes to the code, I now have sensors for each device which reports if the relay is on or off through basic commands. You need to add on/off group between each thermostat and the gateway in zwave-js.

My bad,
Below is a better example. No, I tried v1.92, but reverted to 1.8 for som reason I cannot remember why.

Tried those group settings noe (and several times before), no luck. Could it be that the changes applies to the TF016 only(019b 0001 0001 is the one you have), it just that v1.92 behaves different to v1.8. The advantage with v1.92 is the capability to control update rate.

Here are the "device functionality":

I would expect to read the value in one if the highlighted lines.

The "Binary Switch v1" can control the relay, but not report it.
The "Basic V2" looks just like a mess...seems to be somethng wrong.

Your screenshot shows Basic CC support on the other endpoints, which means endpoint 0 is hidden.
Do you know if they have any useful functionality on those?

This might be what you ask for:

On this screen shot:

the message comes from these settings:

You could possibly "take" group 2 (denoted as Endpoint1 in Zwave JS UI) if you need an endpoint for a fix?

Pleae note that what was fixed in this issue was for the Thermostat TF016, but the I have is TF021(with fw v1.92). Interview logs etc for TF021 v1.92 can be found here https://github.com/zwave-js/node-zwave-js/issues/4688

@AlCalzone I have established communicaton of sorts with Heatit support, and asked them for details on how they have implemented the "relay reporting". Do you have any spesific questions you say would help making the v1.92 work if answered by Heatit?

Hi
By changing the COMPAT-section to:
**"compat": {
// The device reports its relay state via the Basic CC
//"mapBasicReport": false,
"mapBasicSet":"report",
"preserveRootApplicationCCValueIDs": true,
"commandClasses": {
"add": {
			"Multilevel Sensor": {
				"endpoints": {
					"0": {
						"isSupported": true
					}
				}
			}
		},

"remove": {
			"Supervision": {
				"endpoints": "*"
			}
		}
	}
}**

I now get "relay updates" and "temparature updated" when setting the appropriate associations in end point 1 an 4. For the "relay status" it looks kind of messy(but works):

I have the feeling that this looks more like awork around than a proper solution. Even so, I will use it in my system unless a "better" config shows up in a future release.

This goes in the direction I would probably have taken, too.
Maybe the Basic values for endpoints 1-4 can be hidden, but I'll have to look at that next week. Too much other stuff that has priority right now.

@nesheimt
Did you manage do get feeback on the relay state? and if so would you recommend upgrading from FW1.8 to 1.92?

Remember to set the associations to this(for floor senso):

But my config file might also work for air-sensors, but havn't tried. Change the associations accordingly.

Thank you for sharing!
This sounds good. The reason I want to try to upgrade again is that when configured to use  i.e.: ext sensor air sesnsor, maximum and minimum floor temperature setting is not respected. I know this works fine with later generation heatit thermostat, hence I'm hoping this will work with 1.92. I will give it a try on one of my devices, if I can remember where I put the cable for flashing the firmware.

Bwt...you might want to change this:
from:       "removeEndpoints": [2,3,4],
to:           "removeEndpoints": "*",
If you enncounter problems using air-sensor...remove the whole "removeEndpoints"-statement. You also might have to re-interview several times. If there is aninterrupt (messing up the interview) the system will assume some settings instead if using the right one. An interview that is successful using my settings/configs should end up in this:


 I think the browser intercepts those and takes you out of full screen and stuff.

Are we even able to detect Escape key presses? I think the browser intercepts those and takes you out of full screen and stuff.

is there an event for exiting fullscreen?

works fine here


CST should be a dependency

Fixes a problem raised in #120.

@brzpegasus: Can we have a patch release for this?


Add groundingdino&segment-anything, Edit LightningApp import type

Describe your changes and approach used

for Issue #38
include folder of groundingdino and segment_anything, so remove that line in environment.yml
 segment-anything==1.0 , groundingdino==0.1.0

for Issue #39
change import lightning as L into from lightning.app import LightningApp

Fixes #38, fixes #39
Checklist before requesting a review

[X] I have performed a self-review of my code.
[X] I have performed linting on my code.
[X] I have linked the related issue.
[X] The code is documented accordingly.
[X] If it is a core feature, I have added thorough tests.

Hi @riverallzero! Appreciate the PR :)
While it is a working solution, I dont think it will be a good idea to just clone both the repos inside lang-sam (heavy, clunky and somehow misleading of what this project is about). Maybe adding a Dockerfile with the working env will help people even more.


v2.1.0-beta3 Email not sending

First the Task scheduler  points now to the good folder and wacs.exe, see #1234.
Sending e-mails is nogo.
In the default setting there are brackets in the ReceiverAdresses :
   "ReceiverAddresses": [],
So I did:
    "ReceiverAddresses"<EMAIL_ADDRESS>Then I get:
[VERB] Sending e-mails False
[EROR] Email notifications not enabled. Input an SMTP server, sender and receiver in settings.json to enable this.

When I fill in with one of the two (what  is the correct use of this field ?)
"ReceiverAddresses"<EMAIL_ADDRESS>or
"ReceiverAddresses"<EMAIL_ADDRESS>
No error, but no e-email is sent, get:
[VERB] Sending e-mails True
[INFO] Sending test message
[INFO] Test message sent!

The mail server   gets nothing from Wacs, not even connecting to the server. Tried different values SmtpServer
Config:
  "Notification": {
    "SmtpServer": "<IP_ADDRESS>",
    "SmtpPort": 25,
    "SmtpUser"<EMAIL_ADDRESS>,
    "SmtpPassword": "......",
    "SmtpSecure": false,
    "SenderName": "Wacs Steffen",
    "SenderAddress"<EMAIL_ADDRESS>    "ReceiverAddresses"<EMAIL_ADDRESS>    "EmailOnSuccess": false
  },

Ps. I run on the same box also a Mailserver, that SmtpServer <IP_ADDRESS> works with all other applications.
Nice page https://pkisharp.github.io/win-acme/ but can you also mention Apache ?
Like this: ...install certificates for a local IIS server or to create for Apache server

This has been fixed in beta3a. The correct format for the receiver is<EMAIL_ADDRESS>for a single address and<EMAIL_ADDRESS><EMAIL_ADDRESS>for multiple addresses, and theses examples will be added to the documentation upon release.

Working now,
Thanks!
Little thingy:
In the test mail is the version <IP_ADDRESS>
If you are reading this, it means you will receive notifications about critical errors in the future.
Sent by win-acme version <IP_ADDRESS> from AL

That will be fixed before the final release as well, thanks for bringing it to my attention!

Email notifications were working for years. Then last month i switched to the .dotnet, auto updated version of wacs.exe and it no longer send emails anymore.
The logs simply say "Send email: false" even though the settings json file is configured properly. It's as if this .dotnet version is reading from some other config entirely.

The verbose log should also reveal where it's reading the settings.json from

Most helpful,  thank you.
The original settings.json has a "config path" option, but the runtime logs only showed a "resource path". I thought they were different things - they are not.
*If you switch to the .Net version, your new settings.json file will be located deep within your system's .dotnet/tools/... directory.


VSTS Free account users

Hello,
Can you please confirm how many users do the subscribers get in the VSTS account? I know that they get Basic level accounts, that provide 5 free users, however, I was under the impression that if the benefit comes from a Cloud subscription, instead of a Standard subscription, you get unlimited users on the account. Could you please verify this?
Thanks in advance!

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

ID: 34c186b2-096e-e066-ed2c-6ae725c5eff1
Version Independent ID: b93a5dea-8d1f-eb84-0248-5b1fbf2f7638
Content: VSTS benefits for Visual Studio subscribers
Content Source: subscriptions/vs-vsts.md
Service: unspecified
GitHub Login: @evanwindom
Microsoft Alias: jaunger

@Nathan-Tarin Thanks for your inquiry and apologies for the late reply.
@evanwindom @prrana Is this something that you could help the customer with?

It would be nice if github users could use their github accounts to log into VSTS as well. :thinking: Or even their microsoft accounts to log into github (like only if their microsoft account is linked to their github). Just a thought I am just placing here for now.

@Nathan-Tarin   Thanks for your question.  Here's some info from the Billing FAQ that answers your question:
Q: What kind of volume discounts are available for Visual Studio subscriptions?
A: You get a 5% discount on the 6th and all subsequent subscriptions within each type of subscription:
•Visual Studio Professional monthly
•Visual Studio Professional annual
•Visual Studio Enterprise monthly
•Visual Studio Enterprise annual
Also, the discount only applies to charges in a given monthly billing period. So if you buy 5 Visual Studio Professional annual subscriptions in one month, and then you buy 5 more the next month, you'll pay the regular price on all 10 subscriptions.
So, in short, the first five users are included with cloud subscriptions.

@AraHaan Thank you for your suggestion.  I have forwarded your comment to the engineering team for their consideration.

So to confirm and clarify, "So, in short, the first five users are included with cloud subscriptions." means I only get 5 free access to VSTS just like anyone else who does not have paid MSDN subscription?

@jongdaelee Thanks for your question.  I think my initial response may have caused some confusion.  There are volume discounts for cloud subscriptions, and a tiered pricing model for VSTS.  To answer your question directly, the number of users is the same, but the capabilities of VSTS in the paid subscriptions can vary from the free accounts.  Visual Studio Enterprise standard, as well as monthly and annual cloud subscriptions include Test Manager, Package Management and Private Pipelines, which are not included in free accounts.  For more information on what's included in the subscription levels, please visit  https://visualstudio.microsoft.com/vs/pricing/.


fix #2581

This PR fixes a minor bug:  #2581  ( fix #2581 )
(This PR is re-introducing a previous bug (#2505) and a better resolution is being investigated by @StasJ and Sam.)

@shaomeng please add "fixes @2582" or "closes #2581", etc. so that the PR and issue get linked. Thanks!

@StasJ I believe I fixed the regression and also achieved the desired behavior. Please feel free to provide any review.


task 4.4: create image enricher

This PR is the second part for https://github.com/GonzaloPardoVillalibre/TFG/pull/5 that was mergged by error

TO DO:

Add optional FFT calculation
Add zipable option for image builder and image enricher

I'll leave the task for this PR here, although data augmentation must be added BEFORE fft is calculated, then the feet must be applied for each image including the new ones after augmentation (more less lines 64 and 74).


fix: class action 统一使用keywords包裹

这个 PR 实现什么功能/修复什么问题:
class action 统一使用keywords包裹
是否需要 backport 到之前的 release 分支:

release/2.12

/area region
/cc @swordqiu

Codecov Report

Merging #5490 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master    #5490   +/-   ##
=======================================
  Coverage    6.88%    6.88%
=======================================
  Files         609      609
  Lines      103036   103036
=======================================
  Hits         7093     7093
  Misses      95372    95372
  Partials      571      571

Flag
Coverage Δ

#aFlag
6.88% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/cloudcommon/db/db_dispatcher.go
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fc94e90...bb8ccd2. Read the comment docs.

/lgtm

/lgtm

/approve


fix: Consider user namespace first, then standard namespaces

Hi. Trying to install multiple instances of Jenkins X. At this moment without luck. Just fixed a tiny issue.
EXAMPLE CASE SCENARIO:
- Installed JX v3 in a standard way (with jx-git-operator in standard namespace)
- Want's to try to install a second jx-git-operator together with second JX v3
- PREVIOUSLY: It will find an "old" operator in standard namespace
What do you think? Is this OK with conception? Could operator be installed in a separate namespace at all?

No, multiple instances of Jenkins X in one cluster will fail in so many ways.


Extract the code to process the storage response completeness and error.

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

Reopen in #261


HSEARCH-2071 Support EmbeddedId

https://hibernate.atlassian.net/projects/HSEARCH/issues/HSEARCH-2071
I checked the test EmbeddableIdTest and ProgrammaticEmbeddedItTest and they won't work with elasticsearch for the following reasons:

the field bridge used for the id is not a MetadataProvidingFieldBridge; because of this, the new fields are not defined during the schema creation and this causes some errors when we need to create them;
the fields name contain a . ;

I've created new tests without this limitations and checked that the Lucene and Elasticsearch backend are consistent. This resulted in another test failure because on Lucene a field was store not analyzed while in Elasticsearch was stored analyzed.
I tried to fix the issue by adding some information in the BridgeDefinedField. Let me know if it makes sense.

@DavideD why is this assigned to you? Please give yourself advice in how to proceed :)

Problem solved :)

ouch :) :+1:

Jenkins, please retest this

Jenkins, retest this please

Couple of typos in one of the commit message:

HSEARCH-2071 Use correct defaults for fields provided by field bridges
Custom field bridges in the Lucene backend can create new fields using as default
the settings for property accessor,

s/,/./

For example, if the fieldbridge is called for an id, the custom fields won't be analyzed; when
used an a normal field they are going to be analyzed.

s/fieldbridge/field bridge/
s/used an a/used as a/

Finished with the review. Feel free to ping me if there's something unclear.

Fixed the remarks, added the analyzer name and rebased

@DavideD I'm not convinced it's a good idea to add the analyzer and the analyzed/not analyzed information to the BridgeDefinedField.
IIRC, in the Lucene case, the only bridge defined field inheriting from the analyzer definition is the one having the same name of the default name. The other fields are not analyzed.
If I'm correct on this, I think we should stick with it for now and have the exact same behavior in Elasticsearch.
That being said, I would really like to revisit this but in this case, we also need to add the ability to override the analyzer definition when the bridge defined field is defined.
So for now, I'll stick to the behavior we already have in Lucene and create a JIRA with the additional patch attached (or a link to one of your branches) so that we can build on it later. I had a couple of thoughts in this area, I have to dig a bit more a bug I found and I'll write something on the list.
By the way, looks like your new tests are not passing.

@gsmet I've force-pushed  some changes:

I've removed the part related to the analyzer name
Added a new test for core and elasticsearch that make sure that the defaults applied are the same (there is duplication and it might be improved but I don't want to spend more time on it). The default analyzer is used as yuo says.

I think we need a new JIRA to allow to set an analyzer for custom field. WWDYT?

Merged! Thanks @DavideD!


Nested Frontmatter

Example of a particular use case on Healthcare.gov:
questions:
  1:
    - am-i-eligible-to-get-insurance-through-the-marketplace
    - how-much-will-coverage-cost
  2:
    - how-do-i-apply-for-marketplace-insurance
  3:
    - what-will-marketplace-insurance-plans-cover

Would be great to have this type of formatting available through the Prose ui.

Hello and thank you for this issue report. There have been several point releases in Prose since this issue was opened and there has not been much discussion here. I wanted to ask if you could please assist in confirming this is still an issue in the latest version of the product. If it is fixed, please close this issue :-)
Since this project is looking for new maintainers (#743), it will be helpful if users can double check the old issues and delete ones that are fixed. This will be super helpful for the new team that works on moving this project forward.
I'm sorry this message is impersonal. And thanks for your help!

I've got the same need for our site. We're doing event posts and most object structures has been flattened without too much hassle. But we're offering an optional frontmatter for venue which is too many attributes to be flattened and will become hard to check presence if it's flattened.
Our current logic is:
{% if page.venue %}
  # Use provided venue
  # {{ venue.name }}, {{ venue.address }}, {{ venue.coord.lat }} ...
{% else %}
  # Use default venue configured in {{ site.data.business }}
{% endif %}

Our workaround for this right now is to create a collection containing known venues and then make a dropdown with keys referring to the collection objects.
But the learning curve for a non-developer to be able to enter ad-hoc venue data is a bit steep.

An idea could perhaps be to just support path names in the name attribute?
- name: "coord.lat"
  field:
    element: "number"
    label: "Latitude"

- name: "coord.lng"
  field:
    element: "number"
    label: "Longitude"

Render flat but store it as
coord:
  lat: 12.34
  lng: 56.78


Port Envoy Go WAF to the HTNN

Description
No response
Use Scenes
Envoy Go WAF: https://github.com/mosn/envoy-go-waf
Advice
We can split it into multiple PRs, as this project is big. See https://github.com/mosn/htnn/blob/main/CONTRIBUTING.md#communication

CC @Axkea

plz assign this issue to me

Done