NXP Boards that do not build hello_world

Describe the bug
A small section of boards from boards/nxp do not seem to build hello_world.
This was tested on the latest commit of main1fe904539d32b5b7d18361d63acc7a47c9171400
imx8mn_evk/mimx8mn6/m7
imx8mq_mimx8mq6/a53
imx8qm_mek/mimx8qm6/a72
imx8qm_mek/mimx8qm6/a53
imx8qm_mek/mimx8qm6/m4
imx8qxp_mek/mimx8qx6/a35
imx8qxp_mek/mimx8qx6/m4
imx8ulp_evk/mimx8ud7/f1_dsp
imx8ulp_evk/mimx8ud7/a35
To Reproduce
west build -p always -b <board_name> /path/to/samples/hello_world
Expected behavior
A successful build of hello world for <board_name>
Impact
Delay of CI confirmation and platform testing when PR for Issue [https://github.com/zephyrproject-rtos/zephyr/issues/78353] is posted.
Logs and console output
My Environment

|
|- zephyr/*
|
|- build/

Example output:  /> west build -p always -b imx8mn_evk/mimx8mn6/m7 ./zephyr/samples/hello_world
-- west build: making build dir /home/emilio/zephyrproject/build pristine
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: /home/emilio/zephyrproject/zephyr/samples/hello_world
-- CMake version: 3.29.2
-- Found Python3: /home/emilio/zephyrproject/.venv/bin/python3 (found suitable version "3.10.12", minimum required is "3.10") found components: Interpreter
-- Cache files will be written to: /home/emilio/.cache/zephyr
-- Zephyr version: 3.7.99 (/home/emilio/zephyrproject/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: imx8mn_evk, qualifiers: mimx8mn6/m7
-- ZEPHYR_TOOLCHAIN_VARIANT not set, trying to locate Zephyr SDK
-- Found host-tools: zephyr 0.16.5 (/home/emilio/zephyr-sdk-0.16.5)
-- Found toolchain: zephyr 0.16.5 (/home/emilio/zephyr-sdk-0.16.5)
-- Found Dtc: /home/emilio/zephyr-sdk-0.16.5/sysroots/x86_64-pokysdk-linux/usr/bin/dtc (found suitable version "1.6.0", minimum required is "1.4.6")
-- Found BOARD.dts: /home/emilio/zephyrproject/zephyr/boards/common/stub.dts
-- Generated zephyr.dts: /home/emilio/zephyrproject/build/zephyr/zephyr.dts
-- Generated pickled edt: /home/emilio/zephyrproject/build/zephyr/edt.pickle
-- Generated zephyr.dts: /home/emilio/zephyrproject/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /home/emilio/zephyrproject/build/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /home/emilio/zephyrproject/build/zephyr/dts.cmake
Parsing /home/emilio/zephyrproject/zephyr/Kconfig
Loaded configuration '/home/emilio/zephyrproject/zephyr/samples/hello_world/prj.conf'
Configuration saved to '/home/emilio/zephyrproject/build/zephyr/.config'
Kconfig header saved to '/home/emilio/zephyrproject/build/zephyr/include/generated/zephyr/autoconf.h'
CMake Error at /home/emilio/zephyrproject/zephyr/cmake/modules/arch_v2.cmake:36 (message):
ARCH not defined.  Check that BOARD=imx8mn_evk, is selecting an appropriate
SoC in Kconfig, SoC=, and that the SoC is selecting the correct
architecture.
Call Stack (most recent call first):
/home/emilio/zephyrproject/zephyr/cmake/modules/zephyr_default.cmake:133 (include)
/home/emilio/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
/home/emilio/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
CMakeLists.txt:5 (find_package)
-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /usr/bin/cmake -DWEST_PYTHON=/home/emilio/zephyrproject/.venv/bin/python3 -B/home/emilio/zephyrproject/build -GNinja -DBOARD=imx8mn_evk/mimx8mn6/m7 -S/home/emilio/zephyrproject/zephyr/samples/hello_world
Environment (please complete the following information):

OS: Linux
Toolchain: Zephyr SDK
Commit SHA: 1fe904539d32b5b7d18361d63acc7a47c9171400

Interesting.... imx8, imx8x, and imx8ulp should only support the ADSP-based builds, yet the soc.yml file contains other cpu clusters as well.....

@hakehuang

@dleach02 , @EmilioCBen  those platform is not listed in the baords/nxp//board.yaml so they are not supposed to be supported, and I see #79028 is just remove those core, am I right?

It seems there was some slight confusion, but confusion none the less.
It would seem that when you build for an invalid target of the boards I have listed,
these options do come up, so I only assumed they were suppose to build. I believe #79028
will take care of this.

It seems there was some slight confusion, but confusion none the less.
It would seem that when you build for an invalid target of the boards I have listed,
these options do come up, so I only assumed they were suppose to build. I believe #79028
will take care of this. Under the same series of steps, the preview of how to generate a build
with revision of a target say "s32z2xxdc2@D/s32z270/rtu0 is not a displayed example of a target.

this is also discussed in today's test working group meeting, and #77250 is to resolve this confusion.

It seems there was some slight confusion, but confusion none the less.
It would seem that when you build for an invalid target of the boards I have listed,
these options do come up, so I only assumed they were suppose to build. I believe #79028
will take care of this. Under the same series of steps, the preview of how to generate a build
with revision of a target say "s32z2xxdc2@D/s32z270/rtu0 is not a displayed example of a target.

this is also discussed in today's test working group meeting, and #77250 is to resolve this confusion.

So  #77250 is used to fix this issue, and no need for #79028, right? Per my understand, soc.yml lists all the hardware clusters but not clusters currently have been supported.

#77250 will not solve the problem if I understand things correctly. This is an issue in hwmv2 in general, the build systems nad scripts will generate automatic board targets for clusters and consider them supported targets even if the board target was not implemented or configured. So removing the clusters is the proper solution IMO. FYI @tejlmand  @nordicjm


support abis with stateMutability

Closes #798
Introduced changes

Support ABIs with the optional stateMutability field for the function type

Alternatively, use Unknowns EXCLUDE flag for Marshmellow validation of ABI Schema
Relevant Spec PR

[ ] This PR contains breaking changes

New PR https://github.com/software-mansion/starknet.py/pull/801


Add the ability to run dgoss when the docker daemon is not local

I have a use case where I want to run dgoss but the docker daemon is not on the local machine and the file system is not shared.
My idea would be to add a flag i.e --not-local or something and run https://goss.rocks/install inside the container to be tested then docker cp the goss yaml files.

👍
I was playing with a similar concept outside of dgoss, but this seems like a good/valid use-case for it.
Implementation idea: only docker cp files instead of mounting volumes during docker run.  In theory this would make dgoss compatible against both local and remote docker daemons.

Docker cp would be interesting. It would slow down dgoss a little bit and not allow testing of the log content.. but those could be disclaimers. Maybe dgoss could have a cp vs mount mode that a user can toggle though env vars.
I probably won't get around to this, but if someone submits a backwards compatible PR, I would review/merge.

I may have some to look into this next week

Here is the script with the docker cp modifications I made. I didn't add a flag, just replaced everything with docker cp so it will need some work before it is ready for a pr https://gist.github.com/rmb938/bfc92e5cfffd69ba66aabb9bb0e656eb

Closed by #271 it's on the master branch now. I usually don't cut releases for dgoss changes, so it'll be on the github "releases" tab in the next release.


[MetadataViewer] Filter properties in for-in loop

This commit enables filtering properties in for-in loop by if statement.
ONE-vscode-DCO-1.0-Signed-off-by: Seok NamKoong<EMAIL_ADDRESS>
This is to resolve static analysis warning, which is https://rules.sonarsource.com/javascript/RSPEC-1535.
Although diff is little bit complicated, only if statements are added.

@dayo09
PTAL :D
Although diff is dirty, actual code diff is adding if :)


Added homework assignment with google doc link inside.

I would like my code integrated. I added a new file and added google doc link.

Fixed errors and clicked resolve button

Corrected the two minor issues


Update omnioutliner to 5.0.4

After making all changes to the cask:

[x] `brew cask audit --download {{cask_file}}` is error-free.
[x] `brew cask style --fix {{cask_file}}` left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as 363d38dabd2e15fadf6acbd61cd0f7acd2d4f3ba. Your contribution is still credited to you.


Sack of Holding and Double chests

I've used sacks of holding to transfer a load of double chests between bases....
Shift Rclicking on the RIGHT-HAND chest makes the entire double chest disappear even though only a single chest is held in the sack. The other chest is invisible and only shows up after restarting MC.
Shift-Rclicking on the LEFT-HAND chest puts that chest in the sack while the entire double chest still shows up. (Both chests are visible even though one's in the sack).
Using cyclic 1.7.10 in minecraft 1.10.2 using the hermitpack

Thanks for reporting this, ill look into it.
Was this in single player or multi?

Fixed in release 1.7.14, let me know if it breaks again or if theres any more issues https://minecraft.curseforge.com/projects/cyclic/files/2336276


"Pick Color" script menu option has issues.

Tested versions
Reproducible in 4.3.dev4
System information
Godot v4.3.dev4 - Pop!_OS 22.04 LTS - X11 - GLES3 (Compatibility) - Mesa Intel(R) Graphics (ADL GT2) () - 12th Gen Intel(R) Core(TM) i5-1235U (12 Threads)
Issue description
After you use Pick Color once, it starts considering the last color you picked instead of the one you right-clicked. It seems like only if the color syntax is Color(R, G, B[, A]) this updates.

The colors it produces are so crazy precise that they make the option essentially unusable if I don't copy the color from it.

Steps to reproduce
Type var lmofa = Color(), right-click "Color", and try out the things I described above.
Minimal reproduction project (MRP)
N/A

I have only a limited time to work on this, but I believe I can fix it. However, I'm not sure how to replicate the issue. Having a video recording of your actions would be really helpful.

You should type var lmofa = Color() and right-click the "Color" part. No selections, just somewhere inside the word, right-click it. There's a Pick Color option at the bottom of the right-click menu.

Perhaps this issue is platform-specific. I tested it with both the dev4 (mono and standard) versions but couldn't reproduce it on my Windows 11 system.
https://github.com/godotengine/godot/assets/53887662/1ce4d653-905e-430c-82b0-1df6ea997883

You are getting colors with 14 digits of precision.

Yes this is annoying.

And as you clicked on a Color() which is supposed to be black, you got some sort of green that you likely recently worked with

I still can't reproduce this issue, maybe it's related to how to operate?

You reproduced it in your own video.  But this doesn't happen in your video and it's a bug. Only if the color is formatted with RGB, the color picker starts off with the correct color.

You reproduced it in your own video.  But this doesn't happen in your video and it's a bug. Only if the color is formatted with RGB, the color picker starts off with the correct color.

I'm  not sure I agree with you on this and I think this would warrant a proposal. When Color() is written it might be that the user wanted black but in most cases this means he just hasn't placed any values yet. Keeping the last value is then a good thing as thanks to that you can quickly choose a color then create a new variable and modify the previous color.

Or they really wanted black, otherwise they'd duplicate it.


Handle factory-new KeepKey Connections

Overview
Upon connecting a factory-new KeepKey device to the ShapeShift web app, the user encounters the following error:

References and additional details
beta.shapeshift handles this error with the following window:

auto detected OS

updater app download url
https://github.com/keepkey/keepkey-updater/releases/latest
Acceptance Criteria
Handle an OOB (out of box) KeepKey and display to the user a prompt allowing them to download the KeepKey updater app and prompt for the detected OS.
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
1 day

@BitHighlander @pastaghost FYI

@0xdef1cafe what went wrong specifically? It was tested out by  @BitHighlander and I and it worked


[Bug] Authorization Header not being forwarded

Describe the bug
Hi. I am using the Auth JWT mode in Grafana, where the Authorization Bearer token is provided in each request and Grafana is able to validate it with the public keys that I have configured. However when I use the Forward OAuth option in the infinity plugin, I expect that this token is also forwarded in the outgoing request made by the plugin.
When I check my service which is being called by Infinity, I receive no Authorization header in the incoming request.
Steps to reproduce

Grafana UI in Iframe with host providing auth token in all requests
Grafana backend validating auth token
Infinity datasource with forward oauth

My setup is a bit special but as an example the Grafana UI makes a request to /api/ds/query?ds_type=yesoreyeram-infinity-datasource when I make this request with curl or fetch and pass the Authorization header. I expect the outgoing request from grafana backend to also contain that header.
Version Details:

Grafana version : 10.2.2
Plugin version : 2.5.0

Hi. Is there any additional information I can provide to help you understand the issue?

Hey. Thank you for your response. Understood it is not supported as of now. Would the support for JWT be added in a similar fashion to how the OAuth forwarding works at the moment?
Not sure what you mean that forwarding headers is unsupported? It is a use case as described by the Grafana docs https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/jwt/
I would be interested in potentially contributing as this should be fairly straight forward, unless I am mistaken 😅


Velocity Support

Our team make use of camel-velocity for running message transformations.  It would be great to see a camel-quarkus extension supporting velocity.

A contribution is welcome. You may want to follow https://camel.apache.org/camel-quarkus/latest/contributor-guide.html if you are interested. There is also a PR with Freemarker support under review https://github.com/apache/camel-quarkus/pull/835

I can take a look at this issue.

Happy to collaborate on this @zhfeng if I get a chance - that Freemarker pull request does look to have a lot of similarities

@dc2tom it should be very similar to the freemarker component. At first, you need to create the velocity extension by mvn cq:create -N -Dcq.artifactIdBase=velocity. The followup steps could do

enable the reflective class of the Exchanges in VelocityProcessor.javareflectiveClass.produce(new ReflectiveClassBuildItem(false, false, Exchanges.class);

so the ${exchange.properties} can be used in the vm files.
add the option of quarkus.camel.velocity.classModules=<list of the classes which could be used in the template file> in the runtime of VelocityConfig just like freemarkers and process these class just like the Exchanges class above.
add the option to scan all of the vm files and add them into the native image resources.
check the integration test and make sure it work
re-gen the docs by mvn process-resources -Pformat

anyway, you are welcome to contribute a PR. Feel free to ask here and I will try my best to help you !

Hi, I've made a start with this following the Freemarker pull request as an example.  I'm working on porting over the unit tests from camel-velocity but there is one thing I'm not getting.
When trying to run my test, against the below resource definition
@Path("/velocity")
@ApplicationScoped
public class VelocityLetterResource {

    @Inject
    ProducerTemplate producerTemplate;

    @Path("/velocityLetter")
    @POST
    @Consumes(MediaType.APPLICATION_JSON)
    @Produces(MediaType.TEXT_PLAIN)
    public String post(String message) {
        Exchange exchange = producerTemplate.request("direct:a", new Processor() {
            @Override
            public void process(Exchange exchange) throws Exception {
                exchange.getIn().setHeader("firstName", "Claus");
                exchange.getIn().setHeader("lastName", "Ibsen");
                exchange.getIn().setHeader("item", "Camel in Action");
                exchange.getIn().setBody("PS: Next beer is on me, James");
            }
        });

        return (String) exchange.getOut().getBody();
    }

public static class VelocityRouteBuilder extends RouteBuilder {
        @Override
        public void configure() {
            from("direct:a")
                    .to("velocity:org/apache/camel/quarkus/component/velocity/letter.vm");
        }
    }

I see the following failure:
Caused by: org.apache.camel.NoSuchEndpointException: No endpoint could be found for: direct://a, please check your classpath contains the needed Camel component jar.

I can't work out how the RouteBuilder is invoked - my integration tests exist in the org.apache.camel.quarkus.component.velocity.it package.. I auto generated the velocity extension as per the contribution guide.
I expected that perhaps my extension would not be able to load the .vm file as I have yet to implement the functionality, but instead it seems the RouteBuilder is not being executed.  Any advice appreciated :)

Sounds like your integration test module is missing the camel-quarkus-direct dependency.

Perfect, thanks for the quick response, I'm now in a position to work through porting the rest of the camel-velocity test over.
Hopefully I can have a pull request ready in the near future.

Any progress on this one @dc2tom? I am about to add an auto-generated JVM-only Velocity extension. If you had an integration test ready, going native would be easy.

I've created a pull request with what I had so far https://github.com/apache/camel-quarkus/pull/1634
Unfortunately due to other commitments I wasn't able to progress this further than what I've just uploaded

@ppalaga I can look at this issue, please assign it to me.

@zhfeng I've missed your involvement at this issue. Do you plan to continue with it or are you working on it? May I help?

Hi @JiriOndrusek , feel free to take this issue.

Fixed via https://github.com/apache/camel-quarkus/pull/1804


(PUP-10583) Change default digest_algorithm to SHA256

Puppet's digest_algorithm setting defaults to md5, which is outdated. This commit switches it to to sha256.
Update spec tests accordingly.

@joshcooper I skipped the following test https://github.com/puppetlabs/puppet/blob/537b0849c2bca6001b6927ca90c23aa3235606f4/spec/unit/indirector/file_bucket_file/file_spec.rb#L42 since there are no known SHA256 collisions. Should we change the default digest for this test to md5 and still run it?

The puppet agent multiple agents running exits if an agent is already running transient seems to be failing often on Windows Ruby 2.7. Not sure what's up with that, maybe ruby is raising a different exception when the error happens?

CLA signed by all contributors.

Looks good! I forgot about a couple of other areas where md5 is still referenced/used:

lib/puppet/application/filebucket.rb: the help still references md5. Maybe better to say it defaults to Puppet[:default_digest]?
lib/puppet/defaults.rb: We should move md5 to the last position in the valid_digest_algorithms array (when fips is disabled) as it is also used to define the agent's Puppet[:supported_checksum_types], which is the agent's list of preferred algorithms when it requests a catalog.
lib/puppet/file_serving/http_metadata.rb: the collect method should prefer sha256 over md5.
lib/puppet/http/service/compiler.rb: the post_catalog method references the default checksum types. Maybe delete the "currently defaults to part"?
lib/puppet/http/service/fileserver.rb: checksum_type parameter in the get_file_metadata comments need updating
lib/puppet/type/file/checksum.rb: description needs updating

@joshcooper I pushed a separate commit with the latest changes so it's easier to review. Let me know if I missed anything.
There was some non-ASCII whitespace at https://github.com/puppetlabs/puppet/pull/8315/commits/5ceb33c0cb3a1b02cee14b7a9c96793fc42b1209#diff-908b50f77db1b5645f5c125514deccd3R798 which I removed.

LGTM, also locally tested filebucket, and it works as expected.

jenkins please test this on redhat7-64a,ubuntu1804-64a,windows2019-64a with servertests

jenkins please test this on redhat7-64a,ubuntu1804-64a,windows2019-64a with servertests

Dang, I forgot there were some CI failures when running medium tests manually. Could you update these tests?
bx rake ci:test:aio TESTS=tests/parser_functions/calling_all_functions.rb,tests/puppet_apply_a_file_should_create_a_file_and_report_the_md5.rb,tests/resource/file/content_attribute.rb,tests/resource/file/source_attribute.rb,tests/ticket_6541_invalid_filebucket_files.rb SHA=e6c176914d8a1effe6920843fd05b755def07ed0 SERVER_VERSION=6.13.1.SNAPSHOT.2020.09.04T1735 TEST_TARGET=redhat7-64a OPTIONS='--preserve-hosts=always'
...
Failed Tests Cases:
 Test Case tests/parser_functions/calling_all_functions.rb reported: #<Minitest::Assertion: digest output didn't match expected value...
  Test Case tests/puppet_apply_a_file_should_create_a_file_and_report_the_md5.rb reported ...
  Test Case tests/ticket_6541_invalid_filebucket_files.rb reported:...


Tm/tm 620/windows drive init

see if we can get the initializeVolume tasks to work as this will be easier

seems this relies entirely on getting the .yaml formatting for devices correct 👍

change ec2_instance defaults for bods to use local /templates folder
add pagefile settings changes for D:\ drive as per Nart request, now set at 80% of D:\ drive

Reviewing.
On Sat, 26 Oct 2024 at 14:15, Robert Sweetman @.***>
wrote:

see if we can get the initializeVolume tasks to work as this will be
easier

You can view, comment on, or merge this pull request online at:
https://github.com/ministryofjustice/modernisation-platform-environments/pull/8466
Commit Summary

918bd9a
https://github.com/ministryofjustice/modernisation-platform-environments/pull/8466/commits/918bd9ac6a4c4ecac4d05bce9500309e3190fb3e
extend asg timeouts and test drive init
4e48d85
https://github.com/ministryofjustice/modernisation-platform-environments/pull/8466/commits/4e48d857b520bce51d6d420781d3330b191a6141
don't initialize volumes

File Changes
(3 files
https://github.com/ministryofjustice/modernisation-platform-environments/pull/8466/files
)

M
terraform/environments/oasys-national-reporting/locals_ec2_autoscaling_groups.tf
https://github.com/ministryofjustice/modernisation-platform-environments/pull/8466/files#diff-74f68c4e9d4d87aad4e8792ed82a1d17b29f48c2e213cc151596c38410ec6b44
(4)
M terraform/environments/oasys-national-reporting/locals_test.tf
https://github.com/ministryofjustice/modernisation-platform-environments/pull/8466/files#diff-8fcc691cc2544dcde6fd9de647a1d3e3d74405bee3d2ce8d792616c0b273e2d5
(3)
A
terraform/environments/oasys-national-reporting/templates/user-data-onr-bods-test.yaml.tftpl
https://github.com/ministryofjustice/modernisation-platform-environments/pull/8466/files#diff-505231d9bf13d2d9dd1394dbe0447602e5cfb4337246d11531c749c0b3f6a627
(100)

Patch Links:

https://github.com/ministryofjustice/modernisation-platform-environments/pull/8466.patch
https://github.com/ministryofjustice/modernisation-platform-environments/pull/8466.diff
—
Reply to this email directly, view it on GitHub
https://github.com/ministryofjustice/modernisation-platform-environments/pull/8466,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BIVVLHJMEU4YEGQ2V756I2LZ5OIVHAVCNFSM6AAAAABQUZR6DGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGYYTKOBWGA2TCMI
.
You are receiving this because your review was requested.Message ID:
@.***
com>


[HELP NEEDED] Add all docs

It's be really nice if we could get some more hands on this to convert the rest over. I've added all the files here, it's all readable but would look nicer in the new format (see _projects.md for an example). Tag a line below with your name to claim it, so others don't start work on it.
Running and previewing locally is as simple as cd docs; docker-compose up

[x] classifications
[x] collection preferences
[ ] collection roles
[ ] collections
[ ] memberships
[ ] organizations
[ ] project preferences
[ ] project roles
[ ] set member subjects
[ ] subject sets
[ ] subject workflow statuses
[ ] subjects
[ ] user groups
[ ] workflows

Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

Closing in favor of https://github.com/zooniverse/panoptes/pull/4212


Configuration of API

What am I doing wrong, please?
This issue is for a: (mark with an x)
- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I created a database in Cosmos DB emulator called ContosoMedApp.
I placed that database name in config.json:
"dbName": "ContosoMedApp",
I used the Mongo Connection String from Cosmos DB emulator in config.json:
"mongodbConnection": "mongodb://localhost:C2y6yDjf5%2FR%2Bob0N8A7Cgv30VRDJIWEHLM%2B4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw%2FJw%3D%3D@localhost:10255/admin?ssl=true",
I performed npm install and npm run start as per instructions.
Any log messages given by the failure

I receive the error:
connecting to cosmosdb...
C:\code\Azure Communication Sevices\Azure-Samples-communication-services-contoso-med-app-01April2021\contoso-node-api\controllers\user.controller.js:5
throw new Error("Update config.json with connection string");
^
Error: Update config.json with connection string
at Object. (C:\code\Azure Communication Sevices\Azure-Samples-communication-services-contoso-med-app-01April2021\contoso-node-api\controllers\user.controller.js:5:11)
Expected/desired behavior

I expected the API to run.
OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Windows 10
Versions

VS Code
Version: 1.55.0 (user setup)
Commit: c185983a683d14c396952dd432459097bc7f757f
Date: 2021-03-30T16:01:55.261Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042
Mention any other details that might be useful

Thanks! We'll be in touch soon.

@gc-codes can you help lockhartsoftware with this issue?

@lockhartsoftware the "connectionString" configuration should be set to the ACS endpoint connection string.
It must be present and start with "endpoint=..." for the user controller to work.


peerStore[AddressBook] missing remote endpoints of established connection.

Current version of peerStore[AddressBook] holds only addresses which was announced by the peer itself during identify phase, but did not holds remote peer address of currently established connections.
For example nim-libp2p holds this data for fully connected peer via Internet.
/ip4/<IP_ADDRESS>/tcp/32502, /ip4/<IP_ADDRESS>/tcp/32502, /ip4/<IP_ADDRESS>/udp/32503/quic-v1, /ip4/<IP_ADDRESS>/udp/32503/quic-v1

As you can see there is no globally routable IP addresses available, which i think is incorrect.

This can be achieved using https://github.com/vacp2p/nim-libp2p/blob/dc83a1e9b68f00b3be7e09febdb1a3f877321b9a/libp2p/stream/connection.nim#L35

Connection object is easily accessible and needs to be accounted in nimbus-eth2 to properly access this value, its an overhead for application, imho. This functionality should be accessible via peerStore.


move openshift templates off of EOL nodejs 8

@phracek @pkubatrh @hhorak PTAL
I've patched the templates in the openshift 4.x samples operator in the interim

LGTM. Thanks ! Version is not set properly.

clarify please @phracek
do you want them both set to 12, or both set to 10, or something else

or what that not in your sentence aboe suppose to be a now ?


Method for deduping reports

With #13, the possibility of an app connecting to a probe multiple times has been introduced.  This will allow an app to receive the same report more than once, and potentially double count.  We need to disallow this.
Options:

Make report merge fully idempotent ie r1.merge(r1) == r1 and so on
Make probes only accept one connection per app
Include a random unique id in each report, and dedupe on the app

I like (1), as it has nice properties for the future; but it is also the hardest.

Short-term we'll only accept one connection per app, based on source ip.

Closed by #56


Externalize wear slots into configuration

Wear slots are defined in a WearSlot enum. However, not every MUD is going to want the same ones. It would be helpful to define them in a configuration file and load them on startup instead of hard coding them in an enum.

Not going to do this for now.


Show Expected Results from kubectl after commands

I'm trying to diagnose problems and I don't know what success is supposed to look like from the kubernetes commandlet after running various create commands.  For example:  When I execute: "kubectl create -f cluster-issuer.yaml" I get a report back that a pod was created; but I do not see a pod when I do kubectl get pods --all-namespaces matching the name which it indicates.  What was supposed to actually show up or happen?

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

ID: ada58160-dc50-b977-d3bc-65f92406e16d
Version Independent ID: 5c596e04-fddb-effe-3b72-575f4df42d4e
Content: Configure ingress with Azure Kubernetes Service (AKS) cluster
Content Source: articles/aks/ingress.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

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

@drcrook1 I will close this and follow up with you offline.


Linker issue: Providing custom LD_LIBRARY_PATH doesn't work

Hi, I want to play with the SDK but I got stuck.
I've installed xcode, and compiled libindy following these instructions https://github.com/hyperledger/indy-sdk/blob/master/doc/mac-build.md. After I compile libindy in step 5, finishing with following output
   Compiling rust-base58 v0.0.4
    Finished dev [unoptimized + debuginfo] target(s) in 11m 12s

The artefacts are built in target subdirectory
~/dev/hyperledger/indy-sdk/libindy/target/debug (master):ls -l
total 1008368
drwxr-xr-x   32 patrikstas  staff       1024 Aug 18 18:16 build
drwxr-xr-x  227 patrikstas  staff       7264 Aug 18 18:20 deps
drwxr-xr-x    2 patrikstas  staff         64 Aug 18 18:16 examples
drwxr-xr-x    4 patrikstas  staff        128 Aug 18 18:19 incremental
-rw-r--r--    2 patrikstas  staff  118999112 Aug 18 18:20 libindy.a
-rw-r--r--    1 patrikstas  staff      11594 Aug 18 18:20 libindy.d
-rwxr-xr-x    2 patrikstas  staff   41140664 Aug 18 18:20 libindy.dylib
-rw-r--r--    2 patrikstas  staff   97980520 Aug 18 18:20 libindy.rlib
drwxr-xr-x    2 patrikstas  staff         64 Aug 18 18:16 native

So after having libindy library ready according to the step 5, I am trying to install indy-sdk NPM package.
As the artefact is not stored in /usr/lib/local or so, I  am explicitly specifying path to this directory the way it's specified on NPM page, by setting LD_LIBRARY_PATH pointing to directory containing compiled libindy libraries.
~/dev/hyperledger/indy-test:LD_LIBRARY_PATH="/Users/patrikstas/dev/hyperledger/indy-sdk/libindy/target/debug" npm install --save indy-sdk

><EMAIL_ADDRESS>install /Users/patrikstas/dev/hyperledger/indy-test/node_modules/indy-sdk
> node-gyp rebuild

  CXX(target) Release/obj.target/indynodejs/src/indy.o
./Release/.deps/Release/obj.target/indynodejs/src/indy.o.d.raw Stats {
  dev: 16777220,
  mode: 33188,
  nlink: 1,
  uid: 501,
  gid: 20,
  rdev: 0,
  blksize: 4194304,
  ino:<PHONE_NUMBER>,
  size: 2597,
  blocks: 8,
  atimeMs:<PHONE_NUMBER>000,
  mtimeMs:<PHONE_NUMBER>000,
  ctimeMs:<PHONE_NUMBER>087.317,
  birthtimeMs:<PHONE_NUMBER>905.6628,
  atime: 2018-08-18T13:08:20.000Z,
  mtime: 2018-08-18T13:08:20.000Z,
  ctime: 2018-08-18T13:08:20.087Z,
  birthtime: 2018-08-18T13:08:19.906Z }
  SOLINK_MODULE(target) Release/indynodejs.node
ld: library not found for -lindy
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [Release/indynodejs.node] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/patrikstas/.config/yarn/global/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Darwin 17.6.0
gyp ERR! command "/Users/patrikstas/.nvm/versions/node/v8.11.3/bin/node" "/Users/patrikstas/.config/yarn/global/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/patrikstas/dev/hyperledger/indy-test/node_modules/indy-sdk
gyp ERR! node -v v8.11.3
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/patrikstas/.npm/_logs/2018-08-18T13_08_20_536Z-debug.log

The strange thing is that it's actually looking for something called lindy, not libindy, or is it?
Out of curiousity, I've tried to rename all those libindy.*** files in target directory respectively to lindy.***, but without much success.
Am I doing something wrong, or is there a problem with the package? Thanks in advance!
Edit:
Well, I see now that -lindy is specified for node-gyp config here https://github.com/hyperledger/indy-sdk/blob/master/wrappers/nodejs/binding.gyp
What's lindy then?

Well, I see now that -lindy is specified for node-gyp config here https://github.com/hyperledger/indy-sdk/blob/master/wrappers/nodejs/binding.gyp
What's lindy then?

-lindy is actually -l followed by indy because the cpp linker -l argument expects no space following it.
You shouldn't need to rename any files in the target directory. The linker will expand indy to look for the OS specific naming conventions. So in your case it will prefix with lib and postfix with .dylib and find libindy.dylib
Try nuking your node_modules folder and running this again without the "
LD_LIBRARY_PATH=/Users/patrikstas/dev/hyperledger/indy-sdk/libindy/target/debug npm install --save indy-sdk

I  setup the build script to use LD_LIBRARY_PATH in a somewhat unconventional way so the " may be messing it up.

@farskipper Thank you for response Matthew. I am using bash as my shell, so the quotes are pre-processed by bash - I've gave it a shot try nevertheless, but with no success.
What turned out to be working was to actually copy libindy.* file to /usr/local/lib. I am now able to install indy-sdk
~/dev/hyperledger/indy-test: npm install --save indy-sdk

><EMAIL_ADDRESS>install /Users/patrikstas/dev/hyperledger/indy-test/node_modules/indy-sdk
> node-gyp rebuild

  CXX(target) Release/obj.target/indynodejs/src/indy.o
./Release/.deps/Release/obj.target/indynodejs/src/indy.o.d.raw Stats {
  dev: 16777220,
  mode: 33188,
  nlink: 1,
  uid: 501,
  gid: 20,
  rdev: 0,
  blksize: 4194304,
  ino:<PHONE_NUMBER>,
  size: 2597,
  blocks: 8,
  atimeMs:<PHONE_NUMBER>000,
  mtimeMs:<PHONE_NUMBER>000,
  ctimeMs:<PHONE_NUMBER>159.4302,
  birthtimeMs:<PHONE_NUMBER>988.1003,
  atime: 2018-08-22T04:00:49.000Z,
  mtime: 2018-08-22T04:00:49.000Z,
  ctime: 2018-08-22T04:00:49.159Z,
  birthtime: 2018-08-22T04:00:48.988Z }
  SOLINK_MODULE(target) Release/indynodejs.node
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>updated 1 package in 11.211s

Anyway, passing LD_LIBRARY_PATH should also work too, right? I tried to run following and your way of parsing LD_LIBRARY_PATH seems to work as expected with my input. Running command
>: LD_LIBRARY_PATH="/Users/patrikstas/dev/hyperledger/indy-sdk/libindy/target/debug" node -e "console.log((process.env.LD_LIBRARY_PATH || '').split(':').map(a => '-L' + a.trim()).filter(a => a != '-L').join(' '))"

prints
-L/Users/patrikstas/dev/hyperledger/indy-sdk/libindy/target/debug

which does indeed contains the compiled indy libraries:
ls  -lah /Users/patrikstas/dev/hyperledger/indy-sdk/libindy/target/debug

total 525712
drwxr-xr-x@  13 patrikstas  staff   416B Aug 22 13:35 .
drwxr-xr-x    4 patrikstas  staff   128B Aug 22 13:35 ..
-rw-r--r--    1 patrikstas  staff     0B Aug 22 13:28 .cargo-lock
drwxr-xr-x  140 patrikstas  staff   4.4K Aug 22 13:28 .fingerprint
drwxr-xr-x   32 patrikstas  staff   1.0K Aug 22 13:28 build
drwxr-xr-x  227 patrikstas  staff   7.1K Aug 22 13:35 deps
drwxr-xr-x    2 patrikstas  staff    64B Aug 22 13:28 examples
drwxr-xr-x    4 patrikstas  staff   128B Aug 22 13:32 incremental
-rw-r--r--    2 patrikstas  staff   113M Aug 22 13:35 libindy.a
-rw-r--r--    1 patrikstas  staff    11K Aug 22 13:35 libindy.d
-rwxr-xr-x    2 patrikstas  staff    39M Aug 22 13:35 libindy.dylib
-rw-r--r--    2 patrikstas  staff    93M Aug 22 13:35 libindy.rlib
drwxr-xr-x    2 patrikstas  staff    64B Aug 22 13:28 native

Well, my personal roadblock is removed by copying files to /usr/local/lib. If you, or someone would like to investigate this, I'll still be here to assist. Also, to reproduce the issue, make sure you remove indy libraries from any default library paths to (like  /usr/local/lib on Mac).

Few points - I did a few experiments with binding.gyp
"link_settings": {
        "libraries": [
          "-L<(module_root_dir)",
          "<!(node -e 'console.log(\"-L/Users/patrikstas/dev/hyperledger/indy-sdk/libindy/target/debug\")')",
          "-lindy"
        ]
      }

This works.
"link_settings": {
        "libraries": [
          "-L<(module_root_dir)",
          "<!(LD_LIBRARY_PATH=/Users/patrikstas/dev/hyperledger/indy-sdk/libindy/target/debug node -e \"console.log((process.env.LD_LIBRARY_PATH || '').split(':').map(a => '-L' + a.trim()).filter(a => a != '-L').join(' '))\")",
          "-lindy"
        ]
      }

This also works.
So I think the problem is that LD_LIBRARY_PATH is not defined in that given node context. I am not familiar with gyp, but I suppose the solution would be to have something likes this in the gyp file
"<!(node -e \"console.log((<@(LD_LIBRARY_PATH) || '').split(':').map(a => '-L' + a.trim()).filter(a => a != '-L').join(' '))\")",

and figure out way how to pass that variable to gyp-node?

We are using Jira to track issues now, please use this Jira IS-978 ticket for any further discussion.


Two scrollbars on one page

Hi
Having an issue when trying to have 2 scrollbar owl carousels on one page, when I have two on the page, the first one doesn't work at all.

Didi you managed to find a fix for this?


tgraf/nettools fails with permission denied when running ping6

Might be related to net.ipv4.ping_group_range setting

This seems to work, no?
docker run --cap-add NET_ADMIN -ti tgraf/nettools ping <IP_ADDRESS>

This seems to work, no?
docker run --cap-add NET_ADMIN -ti tgraf/nettools ping <IP_ADDRESS>

Yes, this works. Will fix up the test scripts.

The other options is that if you change the base image to ubuntu instead of fedora.
$ docker run -ti ubuntu apt-get install iptools && ping -c4 <IP_ADDRESS>
...
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=46 time=61.1 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=46 time=59.1 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=46 time=57.6 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=46 time=66.0 ms

--- <IP_ADDRESS> ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 57.630/60.998/66.018/3.161 ms

$ docker run -ti fedora sh -c 'dnf install -y iputils && ping -c4 <IP_ADDRESS>
...
Installed:
  iputils.x86_64 20161105-1.fc25

Complete!
sh: /usr/sbin/ping: Operation not permitted

The other options is that if you change the base image to ubuntu instead of fedora.

Is the difference that the ubuntu container image modifies net.ipv4.ping_group_range or what is the actual difference?

Actual difference is in the way both pings are installed:

in Ubuntu postinst script just runs chmod u+s /bin/ping
in Fedora setcap is used with cap_net_admin+ep,cap_net_raw+ep which makes execve() to fail:
execve("/bin/ping", ["/bin/ping", "-h"], [/* 15 vars */]) = -1 EPERM (Operation not permitted)

If we remove cap_net_admin+ep from ping then everything works:
docker run -it fedora:25 /bin/bash -c 'dnf install -y iputils && /usr/sbin/setcap cap_net_raw+ep /bin/ping && /bin/ping -c4 <IP_ADDRESS>'
...
Installed:
  iputils.x86_64 20161105-1.fc25

Complete!
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=53 time=37.9 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=53 time=38.0 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=53 time=37.9 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=53 time=37.9 ms

--- <IP_ADDRESS> ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 37.913/37.970/38.079/0.205 ms```

Thanks @mskarbek
Fixed in https://github.com/tgraf/nettools-docker/commit/862dc300dfdc20d35a380360337b3de19e726713


Presence of node_modules directory

Hi,
I have the suspect that node_modules directory was committed by mistake. Normally nodejs modules are fetched during build and should be part of .gitignore.
This creates a problem in Windows because the node_modules directory contains so many nested dependencies that I ultimately get a filename too long error when building my application.
This does not happen in Unix based machines such as Travis or the Bamboo instance internal to my company, but on my development machine it hurts a lot.
I will create a PR once I confirm removing and ignoring node_modules files solves the problem.
Thanks for your attention.

As a side node, I feel the temptation of rebasing the entire history from 94e79571e65 :smile:


renovatebot(deps): update dependency net.bull.javamelody:javamelody-spring-boot-starter to v1.78.0

This PR contains the following updates:

Package
Update
Change

net.bull.javamelody:javamelody-spring-boot-starter (source)
minor
1.77.0 -> 1.78.0

Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

 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.null seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


StateOutOfSync: Failed to apply patches

When converting this notebook (link to github gist) to a slider server notebook, the notebook returns a StateOfOutSync error after uploading a file and then trying to change the model variable. The notebook works correctly inside of a pluto notebook but fails to update after uploading a file.
The full error returned in the web console is:
#######################**************************########################
PlutoError: StateOutOfSync: Failed to apply patches.
Please report this: https://github.com/fonsp/Pluto.jl/issues adding the info below:
failing path: status_tree.subtasks.run.subtasks.evaluate.subtasks.1.finished_at
notebook previous value: Not Found
patch: undefined
#######################**************************########################
Error: [Immer] minified error nr: 15 'status_tree/subtasks/run/subtasks/evaluate/subtasks/1/finished_at'.
Find the full error at: https://bit.ly/3cXEKWf

@fonsp

This will be fixed in the upcoming Pluto release 🎉


Support for MDX files

HI there,
Does this plugin work with MDX files?
UPDATE:
I've installed the plugin and added it to my gatsby-config.js as follow:
const emoji = require(`gatsby-remark-a11y-emoji`);

{
  resolve: `gatsby-plugin-mdx`,
  options: {
    remarkPlugins: [emoji]
  }
}

But I get the following error:
TypeError: Cannot destructure property 'markdownAST' of 'undefined' as it is undefined.
- index.js:18 Function.module.exports
    [my-gatsby]/[gatsby-remark-a11y-emoji]/index.js:18:3

@iloveip I think this is because how Gatsby invokes Remark Plugins, their implementation is a bit custom. However, I have another package that is a "standard" Remark plugin: https://github.com/florianeckerstorfer/remark-a11y-emoji

Thank you very much! It works great!


Turret motion for maximum safety

This is what we should be doing to move the turret:

Look at the current Z position.
Move to Z = 0. (NOT home it.  Move to Z = 0, which is a little above above the home switch.)
--This also lets you check the position of the Z during the move and make sure that we have made it.  Homing does not allow for that.
Once we are at Z = 0, then turn the turret.
Move back to the original Z position.

Easy optimization:
If 4x/10x objectives are the only ones used, then we can skip this.
We may have to still limit tall objectives.  (i.e. turret will not turn with any objective that is present on the turret that is > 42 mm or something…).
OR: We should add objective height to the specs, and if all objectives on the turret are less than x mm, then we can spin it in place. (Or take into account the actual Z height, etc.  ). But this is all in rev 2.
(behavior update on 6/1/23)

is this the same as #234?

Yes.  I closed 234.

Fixed in https://github.com/EtalumaSupport/LumaViewPro/pull/274


fix(db-mongodb): error querying with invalid value on date field

Description
Found this bug while working on #4815. Another fix is needed to make the admin UI use the correct query.

[x] I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] I have added tests that prove my fix is effective or that my feature works
[x] Existing test suite passes locally with my changes

Closing this PR as we aren't sanitizing the query values before sending them through to the database models.
I'll be rethinking this approach.


JavaScript

changes made! thank you

Pull the latest changes on the branch you want to work on before adding anything and push right after you're done. You can check out this video and see if it is helpful: https://youtu.be/29xipesE8y4

resolved conflicts! thanks for the help

Looks great!


Monitoring & Alerting Copy Updates

"Monitoring & Alerting"
"Check Statuses", add "Notifications" Link
"Notification Endpoints"
Two sentence descriptions of what they are instead of "Looks like" @pauldix to provide

"Add a Check" with tooltip: "Add a check to monitor this data"

@pauldix to provide copy

"Configure a Check"
"Properties"
Add examples for the template language. Similar to the Alert Rule builder in 1.x Chrono

User should not have to scroll to see the CRIT option
Red X

add Org Name to match other pages, rename "Check Statuses"
Remove the ability to select, just use 50.

Add "Any" as an option
Add "and" between each section
Label should just be When, placeholder text should be Tag
Tag Filter
Notification Endpoint
Add similar template help text for template, add "Template" to the end of each field label where a template can be used.

Copy for the Monitoring and Alerting page
Check
A Check is a periodic query that the system performs against your time series data that will generate a status based on criteria you set. The status is written to a measurement named statuses in the _montitoring bucket. Statuses generated by a check have a level (OK, INFO, WARN, CRIT) and carry the same tags as the source data the Check was looking at. You can read a more detailed getting started guide and documentation here.
Notification Rule
A Notification Rule will query statuses written by checks to determine if a notification should be sent to a third party system like Slack, PagerDuty, or a generic HTTP POST. Notification Rules and Checks are loosely coupled, which means that a rule can pick up statuses from a single check or many checks. When a notification is sent, the event will be logged to the notifications measurement in the _monitoring bucket (the same bucket where statuses are logged). You can read more detailed documentation on Notification Rules here.
Notification Endpoint
A Notification Endpoint stores the information to connect to a third party service that can receive notifications like Slack, PagerDuty, or an HTTP server that will accept a POST. You can read more detailed documentation on Notification Endpoints here.
Copy for the Alerting Note Tab
Dashboard Cells can visualize the data that a Check evaluates to generate statuses. A Check is a periodic query that the system performs against your time series data that will generate a status based on criteria you set. The status is written to a measurement named statuses in the _montitoring bucket. Statuses generated by a check have a level (OK, INFO, WARN, CRIT) and carry the same tags as the source data the Check was looking at. You can read a more detailed getting started guide and documentation here.
You can also edit Checks on the [Monitoring and Alerting] page.

I broke some of these issues out into separate issues:
https://github.com/influxdata/influxdb/issues/14681
https://github.com/influxdata/influxdb/issues/14683


Refactor RaspberryPi Visitor/Worker

Refactor RaspberryPi to adhere to the structure laid out for other robots.
TASKs

[ ] Check current implementation.
[ ] Refactor relevant RaspberryPiUsedHardwareCollector*, RaspberryPiUsedMethodCollector* visitor/worker into RaspberryPiValidatorAndCollector* visitor/worker.
[ ] Remove old (separately used) nxt visitors/workers.

TESTs

[ ] Check changes by running local server.
[ ] Check changes by running integration tests.

refers to an outdated plugin.


Match input with placeholders

Fixes #1624

@zabil @NivedhaSenthil ping

I added a few comments

@saikrishna321 was going to test this. But before that just wanted to check if this will work if the input element is inside a shadow dom. I don't see anything specific to cover that condition.


Tweak cached resolution example to be more concise

Using the ~= operator is more concise here, right?

In documentation sbt team has been been migrating to using := and += almost exclusively, and as far as I can tell ~= is not even documented unless you look at sbt 0.12 documentation any more - https://www.scala-sbt.org/0.12.4/docs/Getting-Started/More-About-Settings.html
It's a neat shorthand for advanced users, and probably I should recover its documentation in some detailed topic section, but for cached resolution I think it's better to keep it verbose but easier to understand := + .value.

A fair enough - so at the moment the status of ~= is undocumented but not deprecated, is that right?

I think so. I just checked using grep:
$ rg ~=
src/dormant/Settings.md
115:`<++=`, and `~=` are convenience methods that can be defined in terms of
184:### ~=
186:`~=` is used to transform the current value of a setting. For example,
191:scalacOptions in Compile ~= { (options: Seq[String]) =>
200:libraryDependencies ~= { (deps: Seq[ModuleID]) =>
320:method used. In the case of `:=`, `+=`, `++=`, and `~=`, the type of the

src/dormant/Needs-New-Home.md
149:projectID ~= { id =>


add locale to food module

ref book module

hello,may i work on this issue?

Ok assigned

any progress?

Hi, Can i work on this module?

Sure, assigned


Blank sections of Get-Help and Help outputs for PowerShellGet cmdlets

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.

Steps to reproduce
When looking at the Get-Help <cmdlet> and  help <cmdlet> outputs from any PowerShellGet commands includes the following blank sections:

Synopsis
Description
Notes
Examples
Related Links (if applicable)

Presumably both Get-help and help commands pull from the same location for the synopsis and description. Following example is with Find-PSResource but have confirmed it is problem with all cmdlets.
Expected behavior
Non-empty help sections

Actual behavior
Get-Help Find-PSResource

NAME
    Find-PSResource

SYNOPSIS
    {{ Fill in the Synopsis }}

SYNTAX
    Find-PSResource [[-Name] <System.String[]>] [-Credential <System.Management.Automation.PSCredential>] [-IncludeDependencies] [-ModuleName <System.String>] [-Prerelease] [-Repository <System.String[]>] [-Tags <System.String[]>] [-Type {Module | Script | DscResource |
    RoleCapability | Command}] [-Version <System.String>] [-Confirm] [-WhatIf] [<CommonParameters>]

DESCRIPTION
    {{ Fill in the Description }}

RELATED LINKS
    <add>

REMARKS
    To see the examples, type: "Get-Help Find-PSResource -Examples"
    For more information, type: "Get-Help Find-PSResource -Detailed"
    For technical information, type: "Get-Help Find-PSResource -Full"
    For online help, type: "Get-Help Find-PSResource -Online"

Error details
No response
Environment data
Get-Module PowerShellGet;
ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Binary     3.0.12     beta       PowerShellGet                       {Find-PSResource, Get-PSResource, Get-PSResourceRepository, Install-PSResource…}

$PSVersionTable
Name                           Value
----                           -----
PSVersion                      7.2.1
PSEdition                      Core
GitCommitId                    7.2.1
OS                             Microsoft Windows 10.0.22000
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
Testing to confirm it is all the cmdlets in PowerShellGet:

I think this is mostly resolved as of our last release


Composer: Measure Builder.

The most common measures are, count(), count(field), field.sum(), field.avg().  The measure build should show you a list of fields and then choose the function to apply to the field and have an option to make a custom measure.

sum cumulative too :), ratio compared to the total

another very common pattern is something like
sum (x) filter (y = 5)
sum (x) filter (y > 5)
this one is tricky but very useful
for example sum(x) all , it will return the sum regardless of any filters or any grouping.

^^ this is already supported.  See example below.
https://looker-open-source.github.io/malloy/documentation/patterns/yoy.html

We are looking at something different for the ungrouped aggregate computations and filters should apply.  Shouldn't be limited to SUM.
it might look something like.
measure:
   sales is revenue.sum()
  percent_of_sales is sales/total(sales)

query: by_product is {
  group_by: product.name, product.id
  aggregate: sales, percent_of_sales
}


fix(toml): Don't double-warn when underscore is used in workspace dep

What does this PR try to resolve?
This is prep for removing them in the 2024 Edition and is part of rust-lang/rust#123754 and #13629
Particularly, I wanted to make sure I didn't make things worse and in doing so found there was room for improvement.
How should we test and review this PR?
Additional information

Thanks!
@bors r+

:pushpin: Commit 751fd47d346a127e4ccd5862cb6b67c32a1dfb56 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 751fd47d346a127e4ccd5862cb6b67c32a1dfb56 with merge 955503e1deb0ae67c67551c2411b2f5ddaf1f89a...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 955503e1deb0ae67c67551c2411b2f5ddaf1f89a to master...


Add physical tests for surface fluxes

Purpose
Add physical tests for surface fluxes based on Monin-Obukhov similarity theory
Cost/Benefits/Risks
cost: Time of a few (2) atmos team members
benefits: Surface fluxes needs some substantial refactoring, mostly for EDMF and also for the land. Having physical tests can ensure we don't break things (as we did a few times before!)
risks: We are designing our own tests as there are not many existing tests that we can follow
People and Personnel
(@ the personnel required/requested to implement the software solution)

Lead: @akshaysridhar
Collaborators: @LenkaNovak
Reviewers: @tapios @szy21

Components
see task breakdown
Inputs
N/A
Results and deliverables
Tests that are run in ci
Task Breakdown And Tentative Due Date

[ ] Test recover_profile yields logarithmic velocity and thermodynamic profiles under neutral condition, or in the stable/unstable regime but close to the neutral condition
[x] Test the sign of surface fluxes

[x] obukhov_length should be negative for unstable regime and positive for stable regime

[x] compute_bstar should be negative for unstable regime and positive for stable regime

[x] Momentum flux should be negative for positive velocity and positive for negative velocity

[x] For dry case, sensible heat flux should be positive for unstable regime and negative for stable regime, compute_buoyancy_flux should be positive for unstable regime and negative for stable regime.

[x] For moist case, evaporation should be positive if q_sfc > q_int and negative if q_sfc < q_int (Any other signs that we can check for moist case?)

[ ] Compare the magnitude of surface fluxes with Figures 5 and 7 in Nashizawa and Kitamura 2018. The results won't be exactly the same as we don't have the input values, but the magnitude should be comparable.

Proposed Delivery Date
Nov 18, 2022 (We can prioritize it if needed by EDMF)

LGTM. However, please note that the momentum flux can have either sign (depending on sign of velocity);

Akshay already has a qualitative comparison with ERA-5, but we're currently exploring whether we can easily extend this to use surface data instead of data on a pressure level, for an even better agreement. I'll defer to @akshaysridhar for the timelines, since he's leading the effort.


Login Error into BC 16.2 with Runtime App: Description for event […] cannot be found

With every update we also provide other partners with a runtime app version of our extension, so they can install and test it together with their own extensions without requiring our licence to do so. Usually that works fine, we have been using this deployment workflow since BC 13.
With BC 16.2, we're experiencing a new issue here.

the normal extension can be published and installed,enables a login and works as designed
the runtime app only allows a login if it is published without installation. If you then try to install it from within the application, the client freezes
if you publish and install the runtime app, you'll get the generic error message right away when trying to log in.

This is the event log from the container:

The description for Event ID 705 from source MicrosoftDynamicsNavServer$BC cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:
Server instance: BC
Category: Runtime
ClientSessionId: 8a4be1ed-e789-4dbd-81eb-433dce2b4772
ClientActivityId: d7970388-e782-4a01-800b-77605073289f
ServerSessionUniqueId: ba265c53-083d-497d-8a4e-5946989d3767
ServerActivityId: bf4ac4ef-ce42-4987-8c8b-82368ceca05c
EventTime: 06/15/2020 08:07:49
Message (UnauthorizedAccessException): This message had personal data removed. The original may still be in transient telemetry. Find it using the transientTelemetryId.
RootException: UnauthorizedAccessException
ExceptionStackTrace:
at System.IO.MemoryStream.GetBuffer()
at Microsoft.Dynamics.Nav.XmlMetadata.NavigationDataAggregator.CleanStreamFromInvalidChars(MemoryStream content)
at Microsoft.Dynamics.Nav.XmlMetadata.NavigationDataAggregator.CreateNavigationData(MemoryStream content)
at Microsoft.Dynamics.Nav.XmlMetadata.NavigationDataAggregator.TryGetNavigationDataFromDatabase(NavAppRuntimeMetadata appRuntimeMetadata, NavDiagnostics diagnostics, NavigationDefinition& navigationDefinition)
at Microsoft.Dynamics.Nav.XmlMetadata.NavigationDataAggregator.GetNavigationData(NavAppGroup appGroup, NavDiagnostics diagnostics)
at Microsoft.Dynamics.Nav.XmlMetadata.NavigationDataAggregator.FillDepartmentWithNavigationData(NavAppGroup appGroup, ActionContainerDefinition departments, NavDiagnostics diagnostics)
at Microsoft.Dynamics.Nav.XmlMetadata.NavigationDataAggregator.ConstructDepartmentCacheEntry(NavAppGroup appGroup, NavDiagnostics diagnostics)
at System.Lazy1.CreateValue()    at System.Lazy1.LazyInitValue()
at Microsoft.Dynamics.Nav.XmlMetadata.NavigationDataAggregator.CachedDepartmentOrConstructNew(NavAppGroup appGroup, NavDiagnostics diagnostics)
at Microsoft.Dynamics.Nav.XmlMetadata.NavigationDataAggregator.AppendExtensionNavigationData(NavigationDefinition existingDefinitions, NavAppGroup appGroup)
at Microsoft.Dynamics.Nav.XmlMetadata.MetadataProvider.GetNavigationDepartments(NavAppGroup appGroup)
at Microsoft.Dynamics.Nav.XmlMetadata.MetadataProvider.GetNavigationFrame(Int32 homepageId, Boolean applyPersonalization)
at Microsoft.Dynamics.Nav.XmlMetadata.MetadataProvider.GetNavigationFrame(Boolean applyPersonalization, NavProfileKey profileKey)
at SyncInvokeGetNavigationFrame(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.RunInTransactionCombinator(ServiceOperation innerOperation, NSServiceBase serviceInstance, MethodBase syncMethod, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.<>c__DisplayClass28_1.b__1(NSServiceBase serviceInstance, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.TransientErrorRetryCombinator(ServiceOperation innerOperation, NSServiceBase serviceInstance, MethodBase syncMethod, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.<>c__DisplayClass28_1.b__1(NSServiceBase serviceInstance, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.ErrorMappingCombinator(ServiceOperation innerOperation, NSServiceBase serviceInstance, MethodBase syncMethod, Object[] inputs, Object[]& outputs)
CallerStackTrace:
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.ErrorMappingCombinator(ServiceOperation innerOperation, NSServiceBase serviceInstance, MethodBase syncMethod, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.<>c__DisplayClass28_1.b__1(NSServiceBase serviceInstance, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.PushPopCombinator(ServiceOperation innerOperation, NSServiceBase serviceInstance, MethodBase syncMethod, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.<>c__DisplayClass28_1.b__1(NSServiceBase serviceInstance, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationTracer.TraceScopeCombinator(Category telemetryCategory, ServiceOperation innerOperation, NSServiceBase serviceInstance, MethodBase syncMethod, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.<>c__DisplayClass28_1.b__1(NSServiceBase serviceInstance, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.<>c__DisplayClass10_0.b__0()
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.PerformanceCounterCombinator(ServiceOperation innerOperation, NSServiceBase serviceInstance, MethodBase syncMethod, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.<>c__DisplayClass28_1.b__1(NSServiceBase serviceInstance, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.InitClientTelemetryIdsCombinator(ServiceOperation innerOperation, NSServiceBase serviceInstance, MethodBase syncMethod, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.<>c__DisplayClass28_1.b__1(NSServiceBase serviceInstance, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.TlsClearCombinator(ServiceOperation innerOperation, NSServiceBase serviceInstance, MethodBase syncMethod, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.<>c__DisplayClass28_1.b__1(NSServiceBase serviceInstance, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
at System.ServiceModel.Dispatcher.MessageRpc.Wrapper.Resume(Boolean& alreadyResumedNoLock)
at System.ServiceModel.Dispatcher.ThreadBehavior.ResumeProcessing(IResumeMessageRpc resume)
at Microsoft.Dynamics.Nav.Runtime.NavSynchronizationContext.<>c__DisplayClass1_0.b__0(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
ProcessId: 332
Tag: 00000HC
ThreadId: 56
CounterInformation:
CustomParameters: {
}
GatewayCorrelationId: eddb3d6c-f713-4133-b2ca-8c3b3e14eefa

We are one partner affected and need this resolved as quickly as possible, we develop on top of that package and no pipeline or test environment currently works because of this issue.

Some more details:
•      Current VSIX provided by the container was used
•	AL runtime set to current 5.2
•	Current symbols downloaded from container
•	GetRuntime of current NAVContainerHelper <IP_ADDRESS> used
The same runtime app works fine in 16.1 (no breaking changes between these versions), only 16.2 shows this behaviour.
Only after uninstalling the runtime app a login is possible again.

We are also running into a UnauthorizedAccessException when opening the client with a (custom) Base Application installed as run-time package; if we install it as a regular package then all works fine.
Installing the package did not raise any problems, but as soon as you try to use it with the client we are presented with the same screen and exception in the event log.

You have to update to 16.3 for runtime packages to work. For 16.2 no fix was provided for this issue.

Ah, so you mean it is already fixed for 16.3 and up?
The run-time packages we use are indeed currently generated from a 16.2 container. We have to upgrade anyway for other reasons as well, so if that also fixes this issue that would be nice.

We went through the same workflow as described above when 16.3 arrived, without any problems.

Same here. Problem went away with 16.3.

runtime packages also work in 16.4. I was able to install runtime apps exported from 16.2 and install them on 16.4 with no problems.

I am closing this issue because it has been resolved. Please open a new issue if you believe this has not been resolved and reference the current issue.


Add tags and category support

Maybe just port templates from other theme like feather is enough?

This is a port of an existing theme which doesn't use taxonomies so adding doesn't make sense. You can add them yourself pretty easily if wanted.
Do keep in mind that the next version of Gutenberg (https://github.com/Keats/gutenberg/pull/290) will completely revamp how taxonomies are handled


Scala 2.12

I picked up an old 2.12 branch and just compiled with 2.12.3. When I run
sbt ++2.12.3 test

There is exactly one failing test:
...
[info] Test scalaxy.streams.test.SideEffectsTest.collections started
SideEffect(scala.runtime.ScalaRunTime,Reference to scala.runtime.ScalaRunTime,Unsafe)
[error] Test scalaxy.streams.test.SideEffectsTest.collections failed: Array(Array(1)).zipWithIndex.withFilter(((check$ifrefutable$1) => check$ifrefutable$1: @scala.unchecked match {
[error]   case scala.Tuple2((a @ _), (i @ _)) => true
[error]   case _ => false
[error] })).withFilter(((check$ifrefutable$2) => check$ifrefutable$2: @scala.unchecked match {
[error]   case (x$2 @ scala.Tuple2((a @ _), (i @ _))) => true
[error]   case _ => false
[error] })).map(((x$3) => x$3: @scala.unchecked match {
[error]   case (x$2 @ scala.Tuple2((a @ _), (i @ _))) => {
[error]     val len = a.length;
[error]     scala.Tuple2(x$2, len)
[error]   }
[error] })).withFilter(((x$4) => x$4: @scala.unchecked match {
[error]   case scala.Tuple2((x$2 @ scala.Tuple2((a @ _), (i @ _))), (len @ _)) => len.$less(i)
[error] })).map(((x$5) => x$5: @scala.unchecked match {
[error]   case scala.Tuple2((x$2 @ scala.Tuple2((a @ _), (i @ _))), (len @ _)) => a.$plus(", ").$plus(len).$plus(", ").$plus(i)
[error] })) expected:<List()> but was:<List(Unsafe)>, took 0.396 sec
[info] Test run finished: 1 failed, 0 ignored, 7 total, 1.864s
...
[error] Failed: Total 449, Failed 1, Errors 0, Passed 416, Skipped 32
[error] Failed tests:
[error] 	scalaxy.streams.test.SideEffectsTest
[error] (test:test) sbt.TestsFailedException: Tests unsuccessful
[error] Total time: 171 s, completed Aug 11, 2017 4:33:28 PM

I don't understand what this is about. Need to investigate further. Any help is appreciated.

The problematic test is:
    expectSideEffectSeverities(List(),
      q"""
        for ((a, i) <- Array(Array(1)).zipWithIndex; len = a.length; if len < i) yield {
          a + ", " + len + ", " + i
        }
      """)

[error] })) expected:<List()> but was:<List(Unsafe)>, took 0.396 sec

It is expected to be not Unsafe, but it returns Unsafe. So the optimizer thinks a piece of code is unsafe even though it actually would be safe to optimize. So I think it will not do anything bad.
All other tests are running successfully. Travis only fails because it cannot deploy a PR.


Build Script Rewrite

Jumping from #1369, it is time to layout a plan for writing the build script to be easier to maintain, remove the complexity within the script, and making it easier for people new to the project to jump in and start contributing.
So what is wrong with our the current script?
Issues

The current "bus factor" of the build script
Unmaintained gear.js
Security of dependencies in gear.js
Complexity within the script

Bus Factor
I was the one to convert the old python build script to node with the goal being to make it easier to include continuous integration via Travis CI and reducing the amount of dependencies need to start to just node.js. Now that I'm not contributed as much as I use to, the concern of maintaining this script was in the forefront of mind of a while. Using libraries that actually are maintained and have good documentation would make the build script less of a black box and easier to change if there was a new requirement for it. Actual suggestions of libraries will  be continued in the "Task Management" and "Module Bunder" sections.
Unmaintained gear.js
For what we got out of it, gear.js was a good start for what our build script needed previously. Unfortunately, with the more recent security issues and the last commit for gear.js being almost a year ago, it is safe to say that we need to move away from it. It was a poor choice on my part, but it was the only build system I found that would allow me to keep the same command line interface for run certain types of builds. While others like gulp, grunt, webpack, or any of the several different build systems out them required the build file to be in the root directory.
Complexity
Most of the complexity of the script comes from having to write our own of the following:

Module bundler
Parser for comment headers
Mangler for long keyword names

There are a handful of module bundlers that alleviate this burden off our plate, but this change would make it more difficult for the site's version of the build script, which isn't using node. The parsing of starting comment header could be moved to a separate JSON file or with the help of whatever module bundler we choose, could make this part a bit easier. I haven't put much thought into this issue, but it would be nice to get some assistance on this parsing delima. And last is the mangler that can simply shift the responsibility of uglify and it's properties mangler.
Module Bundler

browserify
rollup

This is probably the biggest change as it will remove the comment header field Required and we would start using either common.js or ES6 styled importing. browserify would be the one that is using the common.js pattern and the most obvious benefit would be being able to use the project as is with node. The downside is that the bundled size would more than likely increase significantly.
The other module bundler, rollup, is something I use at work and is the one I personally prefer. Working in ES6 is the eventual future, making it an easier transition when the majority of browsers support features in ES6. The other thing I like about it is, all the module import/export information gets removed resulting in a smaller bundled size and still use the small UMD export we have currently in the core. The only downside would be actually learning ES6 modules.
And of course, like I said previously, there will be an issue with the site's differing build script not being able to correctly parse and bundle the library for either option.
Task Management

async
bluebird
co

To continue to have fast build times, we need to think about which asynchronous type we are going to use to have a consistent style throughout the build script. Both bluebird and co are libraries that handle a specific type of asynchronous flow, bluebird is focused on promise and co is on coroutines. While async is a library for cleaning up asynchronous behaviour via utility functions.
I've used both async and bluebird pretty heavily so those are the two I'm leaning toward. However, if there are other libraries out in the wild that I haven't mentioned, feel free mention them and I'll consider them in the rewrite.
In opening this issues before starting the rewrite, I'm hoping to get ideas from the team, other contributors, and people simply using highlight.js. Feel free to discuss the ideas I have laid out, and don't consider any of them set in stone. Thank you for reading.

cc: @isagalaev @Sannis @marcoscaceres

Just minor thing: for "Task Management", I don't think you need any of those libraries any more (even if we were targeting node 4.x). You have generators and promises, which basically give you all the async machinery you need to create a task runner. For example, the following 30 odd lines of code implement Async/await:
https://github.com/marcoscaceres/async/blob/gh-pages/lib/async.js
Example of usage (see any async.task(function*(){):
https://github.com/w3c/respec/blob/develop/tools/release.js

That may be true, but the reason to use these libraries is a matter of convenience. For example, if there was a non-promise interface, I would have to make sure to wrap a node callback styled function into one that returns a promise in order to use these generator functions. Bluebird help get rid of that with the promisify and promisifyAll interface. Not only that, but I can continue to use this library with generator function support via coroutines.
The suggestion of the async module might be less relevant now, but bluebird is still something I would consider.

The suggestion of the async module might be less relevant now, but bluebird is still something I would consider.

Makes sense, thanks for the clarification. Might also look into Bluebird - as I also end up promesify'ing all the things.

@isagalaev and @Sannis, any feedback on this? My main concerns about the rewrite is the change of module bundling and header parsing. Everything else isn't really going to bring any breaking changes -- as far as the site's build script is concerned.

I hope to find some time to look into this and provide my promised input as well in a few days after I'm back from a family vacation. My time is a little sparse to pay full attention right now :-)

Some unsolicited input from me, but please take a look at how we currently build highlight.js in our project (have to navigate to the install folder, call npm install in there, etc.):
"build:highlight": "cd node_modules/highlight.js/ && npm install && node ./tools/build.js -n xml javascript css http markdown xquery json && cd ../../",

https://github.com/w3c/respec/blob/develop/package.json#L51
That's not ideal, IMHO. It would be nice if once hljs is installed, I can request it to build as a command line tool - so it just generates the :
hljs --build -n xml json --output some/path

Hope that makes sense!

(fixed comment above)

I tried reading the build script and found gearjs.org is now gone. No more docs for gearjs.

ouch :(
On a different note... maybe it's time for this project to consider the pull request hack? This project is heavily relied on by a lot of people, so maybe it's time to open it up a bit more to trusted members of the community to maintain it?


Prep + Publish to PyPI

wipac-dev-tools is our guinea pig. It also has no requirements which will make this transition less painful.
Roadmap: Pre-Merge

Remove SetupShop usage in setup.py
Use copy-pasteable GH Action for generation of standardized setup/requirements

Source of Truth TBD: requirements.txt/setup.py/setup.cfg/etc.

Turn on the PyPI-publishing trigger within semantic_release's GH Action

Roadmap: Post-Merge
Proceed to update WIPAC repos in descending order of complexity. All updates:

follow backward compatibility, unless there's a good reason not to
publish to PyPI only what is needed by a client, if any

prefix all PyPI packages with wipac-

can be updated in time, there is no immediate necessary rush

Updates, in order:

Add wipac-telemetry to PyPI (PR TBA)

call it wipac-telemetry w/ v1.0.0 (no longer prototype)
has requirements, and requires wipac-dev-tools (and no other wipac packages)
follow Roadmap: Pre-Merge workflow for this repo

Add rest-tools to PyPI (PR TBA)

publish on PyPI as wipac-rest-tools
requires wipac-telemetry (and wipac-dev-tools in turn, but no other wipac packages)

TBD: Will this be an optional/extra pip feature: wipac-rest-tools[wipac-telemetry]?

Is tracing "core" to rest-tools? No.
But is it worth separating the functionality at the package level? Maybe.

follow Roadmap: Pre-Merge workflow for this repo

Add other utility repos to PyPI

MQClient (+ child repos), File Catalog (required by FC Indexer), KRS
fix requirements
publish on PyPI with wipac- prefixes
if/where PyPI is not appropriate for entire repo, then spinning-off utility repos may be wanted
- Ex: wipac-file-catalog-types, wipac-krs-utils
follow Roadmap: Pre-Merge workflow for each repo

Fix requirements for each end-stream app

MOU Dash, Skymap Scanner, LTA, IceProd
these apps are not required by any "downstream" repo/client (not-published on PyPI)
pre-merge: there may be some overlap with section above, see "spinning-off utility repos" point above

Fix requirements for each script

FC Indexer, ...
these are not required by any "downstream" repo/client (not-published on PyPI)

If you want to save some duplication efforts, you could use the tool cog along with a github action to render text into files programmatically.
An example of someone using cog to edit their build files:
https://github.com/hynek/structlog/commit/5e6ea9c04e070f7ef0106ff1256c58ef54c03686

If you want to save some duplication efforts, you could use the tool cog along with a github action to render text into files programmatically.
An example of someone using cog to edit their build files: hynek/structlog@5e6ea9c

I'm looking into https://github.com/jazzband/pip-tools


Updated code style

Changed Id -> ID
Aligned function comments with function arguments
Added linter rule to prevent unwanted future style changes to github workflows.

@ctreminiom i would recomemnd squashing my commits, always.


Use with input mask

Hi
I'm trying to use this lib with react-input-mask like the example:
material-ui + text-mask demo
But if I bu like the example, nothing happens.
Have any idea to make this work?

Hi,
your issue isn't related to this library. I guess you're talking about react-material-ui-form-validator. Please, open it there and provide more info, like your code example


@clerk/react-router using CloudFare Template

Preliminary Checks

[X] I have reviewed the documentation: https://clerk.com/docs

[X] I have searched for existing issues: https://github.com/clerk/javascript/issues

[X] I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)

[X] This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.

Reproduction
https://github.com/lydiaf/importbug
Publishable key

Description
Steps to reproduce:

Open root.tsx, and comment in and out the import rootAuthLoader, you can see app stops loading

Expected behavior:
App loads
Actual behavior:
App does not load with input
--
I am just experiencing this with Cloudflare template, not Vercel template.
Environment
-

Hello, thanks for the issue!
I've ran your reproduction and can confirm that it it fails with require is not defined.
[vite-node-miniflare error]
ReferenceError: require is not defined
    at /Users/lejoe/code/playground/importbug/node_modules/snakecase-keys/index.js:3:13

@clerk/react-router imports @clerk/backend which itself imports snakecase-keys. However, this is a quite common error with Vite bundling. snakecase-keys is CJS and you can't use require in ESM builds. So you'll need to adjust the optimizeDeps.include list.
I've got it working like this:

Change the template by following this PR change: https://github.com/remix-run/react-router-templates/pull/6

Add snakecase-keys and cookie to the list
    optimizeDeps: {
      include: [
        "react",
        "react/jsx-runtime",
        "react/jsx-dev-runtime",
        "react-dom",
        "react-dom/server",
        "react-router",
+       "snakecase-keys",
+       "cookie"
      ],
    },


Invoke-DbaWorkload -Workload Latches

Per suggestion of @wsmelton - turn these MSSQL Tiger demos into a command with workload templates
https://github.com/Microsoft/sql-server-samples/tree/master/samples/demos

These haven't been updated in years and I'm not sure I understand the value. Closing.


Intermittently working on file uploads

First, thanks for the work on this script. I'm running into an issue where photos will seemingly work sometimes and error on other times. In my testing case I am only running it against two users. I sanitized the log here...
SUCCESS: Settings Loaded
DEBUG FILE: Verifying directories ('Images/', 'CSV_data/')
INFO File: "Images/" found.
INFO File: "CSV_data/" found.
INFO File: Checks Complete. Starting Client Generation
INFO Current Student: {'client_id': '2619394', 'image_filename': '2619394_m.jpg', 'image_filetype': 'jpeg'}
Bytes Size: 18870
INFO Creating:	User -       2619394        Image:        2619394_m.jpg
INFO Current Student: {'client_id': '2791632', 'image_filename': '2791632_m.jpg', 'image_filetype': 'jpeg'}
Bytes Size: 21520
INFO Creating:	User -       2791632        Image:        2791632_m.jpg
INFO Total of 2 users created
INFO All possible users have been created. A total of 2
INFO Creating canvas object...
INFO CANVAS: initialised values:
Auth Token:
Domain:	 https://.instructure.com/api/v1
Header:	 {'Authorization': 'Bearer '}
Params:	 {}
DEBUG Starting new HTTPS connection (1): .instructure.com:443
DEBUG https://mydomain.instructure.com:443 "GET /api/v1/accounts HTTP/1.1" 200 None
INFO CANVAS: Connection Successfully Tested
INFO Successfully created canvas connection. Commencing upload.
INFO USER: Getting Canvas ID for: 2619394
INFO USER: Getting Canvas ID for: 2791632
DEBUG Starting new HTTPS connection (1): mydomain.instructure.com:443
DEBUG Starting new HTTPS connection (1): mydomain.instructure.com:443
DEBUG https://mydomain.instructure.com:443 "GET /api/v1/users/sis_user_id:2619394 HTTP/1.1" 200 None
DEBUG Starting new HTTPS connection (1): mydomain.instructure.com:443
DEBUG https://mydomain.instructure.com:443 "GET /api/v1/users/sis_user_id:2791632 HTTP/1.1" 200 None
DEBUG Starting new HTTPS connection (1): mydomain.instructure.com:443
DEBUG https://mydomain.instructure.com:443 "POST /api/v1/users/self/files HTTP/1.1" 200 None
DEBUG Starting new HTTPS connection (1): inst-fs-iad-prod.inscloudgate.net:443
DEBUG https://mydomain.instructure.com:443 "POST /api/v1/users/self/files HTTP/1.1" 200 None
DEBUG Starting new HTTPS connection (1): inst-fs-iad-prod.inscloudgate.net:443
DEBUG https://inst-fs-iad-prod.inscloudgate.net:443 "POST /files?token= HTTP/1.1" 201 1024
DEBUG Starting new HTTPS connection (1): mydomain.instructure.com:443
DEBUG https://inst-fs-iad-prod.inscloudgate.net:443 "POST /files?token= HTTP/1.1" 201 1024
DEBUG Starting new HTTPS connection (1): mydomain.instructure.com:443
DEBUG https://mydomain.instructure.com:443 "GET /api/v1/files/1327020?include%5B%5D=enhanced_preview_url HTTP/1.1" 200 None
INFO Setting canvas Avatar for: 15944 To: 2791632_m.jpg
DEBUG Starting new HTTPS connection (1): mydomain.instructure.com:443
DEBUG https://mydomain.instructure.com:443 "GET /api/v1/files/1327028?include%5B%5D=enhanced_preview_url HTTP/1.1" 200 None
INFO Setting canvas Avatar for: 14323 To: 2619394_m.jpg
DEBUG Starting new HTTPS connection (1): mydomain.instructure.com:443
DEBUG https://mydomain.instructure.com:443 "GET /api/v1/users/15944/avatars?as_user_id=15944 HTTP/1.1" 200 None
DEBUG Starting new HTTPS connection (1): mydomain.instructure.com:443
DEBUG https://mydomain.instructure.com:443 "GET /api/v1/users/14323/avatars?as_user_id=14323 HTTP/1.1" 200 None
DEBUG Starting new HTTPS connection (1): mydomain.instructure.com:443
DEBUG https://mydomain.instructure.com:443 "PUT /api/v1/users/15944?as_user_id=14323 HTTP/1.1" 403 None
ERROR Could not process user: 15944 - 403 Client Error: Forbidden for url: https://mydomain.instructure.com/api/v1/users/15944?as_user_id=14323
DEBUG https://mydomain.instructure.com:443 "PUT /api/v1/users/14323?as_user_id=14323 HTTP/1.1" 200 None
DEBUG Starting new HTTPS connection (1): mydomain.instructure.com:443
DEBUG https://mydomain.instructure.com:443 "PUT /api/v1/users/14323?as_user_id=14323&user%5Bavatar%5D%5Btoken%5D= HTTP/1.1" 200 None
DEBUG Starting new HTTPS connection (1): mydomain.instructure.com:443
DEBUG https://mydomain.instructure.com:443 "PUT /api/v1/users/14323?as_user_id=14323&user%5Bavatar%5D%5Btoken%5D= HTTP/1.1" 200 None
DEBUG Starting new HTTPS connection (1): mydomain.instructure.com:443
DEBUG https://mydomain.instructure.com:443 "PUT /api/v1/users/14323?as_user_id=14323&user%5Bavatar%5D%5Btoken%5D= HTTP/1.1" 200 None
INFO success updating user avatar for: 14323
INFO The following users were skipped:
ERROR 0 : 15944
In Canvas they either show the default no image thumbnail or an all white background image. The first time I ran it against these two users it did seem to work, granted I started one at a time in the CSV. I did confirm the images are valid.
Any thoughts? I'll keep testing and digging in the meantime.

So it looks like it is related to the as_user_id param? Looks like multiple users are trying to be updated by an as_user_id that is mostly the same?
DEBUG https://domain.instructure.com:443 "PUT /api/v1/users/16673?as_user_id=15944 HTTP/1.1" 403 None
ERROR Could not process user: 16673 - 403 Client Error: Forbidden for url: https://domain.instructure.com/api/v1/users/16673?as_user_id=15944
DEBUG https://domain.instructure.com:443 "GET /api/v1/users/16687/avatars?as_user_id=16687 HTTP/1.1" 200 None
DEBUG Starting new HTTPS connection (1): domain.instructure.com:443
DEBUG https://domain.instructure.com:443 "PUT /api/v1/users/16640?as_user_id=16687 HTTP/1.1" 403 None
DEBUG https://domain.instructure.com:443 "PUT /api/v1/users/15944?as_user_id=16687 HTTP/1.1" 403 None
ERROR Could not process user: 16640 - 403 Client Error: Forbidden for url: https://domain.instructure.com/api/v1/users/16640?as_user_id=16687
ERROR Could not process user: 15944 - 403 Client Error: Forbidden for url: https://domain.instructure.com/api/v1/users/15944?as_user_id=16687
DEBUG https://domain.instructure.com:443 "PUT /api/v1/users/14414?as_user_id=16687 HTTP/1.1" 403 None
ERROR Could not process user: 14414 - 403 Client Error: Forbidden for url: https://domain.instructure.com/api/v1/users/14414?as_user_id=16687
DEBUG https://domain.instructure.com:443 "PUT /api/v1/users/16687?as_user_id=16687 HTTP/1.1" 200 None
Running the code with just one user in the CSV seems to work.


Apigee Edge integration

It would be slick if you could create/update/delete your Apigee Edge proxy configuration using shipyardctl.

Not sure this integration will happen anymore. Closing for the time being.


Remove Ston support

Check we don't use anymore STON (still in use in somepart of Nick's internal DSL)
Remove Ston Baseline

In the Visualization class, we find elements of STON in particular in thesumOverTimeSeries: method


Fix: Superfluous response.WriteHeader call in otelhttp

This PR updates the OpenTelemetry packages to address the http: superfluous response.WriteHeader call error originating from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp/internal/request.(*RespWriterWrapper).writeHeader.
This issue is resolved in the updated OpenTelemetry version, as confirmed by the corresponding pull request in the OpenTelemetry repository: https://github.com/open-telemetry/opentelemetry-go-contrib/pull/6055.
This update ensures accurate HTTP response handling and eliminates the error message.

@felipeweb, thanks for your PR. However, your go.mod changes are quite intrusive.
Do you have an example to reproduce this issue when using weaver?
Thanks,

Robert


How to distribute a feed with different cedentials?

Hi team.
We have two feeds (Gradle) in vsts to distribute and we generate a credentials for a custom consumers but the problem is, with both credencials can access to any feeds.
For example with credentials of Feed Client1 we can access to Feed Client 2 and consume it on Android Studio.
And we think that it's not the correct funcionality, because is not secure to another feeds.
How can we establish credentials in a single feed and can not be used with another feed?

Adding @alexmullans to help out :)

You would need to create two service (non-user) accounts, ensure they have licenses to Package Management, and then add one of them as a Reader of Client1 and one of them as a Reader of Client2. Then, you would provide credentials for User1 to Client1 and credentials for User2 to Client2.


Regression? VScode portable GUI doesn't work when running from a UNC path

VSCode Version: 1.52.1
OS Version: Windows 10 1809

Steps to Reproduce:

Download vscode zip and extract it to a UNC path like \sharedfoler\mystuff\vscode
Open Code.exe
vscode's main window will open up but nothing gets drawn, no menus, no icons, only the different bars colors are visible.

Does this issue occur when all extensions are disabled?: Yes
This is what you get:

This doesn't happen if you copy the same extracted folder to a local disk. Also, creating the data folder doesn't seem to change the behavior.
This started to happen somewhere after v1.46.1, using this version everything works as expected. I haven't tried other versions in between.
Possible related issues: #53857 #66128

I cannot reproduce this trying to run latest VSCode from a local UNC: \\localhost\c$\Users\name\Downloads\VSCode\Code.exe via PowerShell.
However, we will actually not be able to support running VSCode from UNC paths going forward given limitations such as https://github.com/electron/electron/issues/25618.
You can already see this today, the process explorer and issue reporter will not appear correctly.

I cannot reproduce this trying to run latest VSCode from a local UNC: \\localhost\c$\Users\name\Downloads\VSCode\Code.exe via PowerShell.
However, we will actually not be able to support running VSCode from UNC paths going forward given limitations such as https://github.com/electron/electron/issues/25618.
You can already see this today, the process explorer and issue reporter will not appear correctly.

Hi @bpasero
Sorry for the delayed answer, I missed the notification somehow.
On one hand, If I copy the extracted folder to a local disk and use the \\localhost\c$\Users\name\Downloads\VSCode\Code.exe path VSCode's window gets drawn. So it seems that using \\localhost isn't the same as running from an actual network path.
On the other hand, if I mount the shared path as a disk (Z: for example) and run it from there, it works.
Too bad to hear that UNC support could be dropped, it's a pretty common thing on enterprises.

Hi @bpasero
Sorry for the delayed answer, I missed the notification somehow.
On one hand, If I copy the extracted folder to a local disk and use the \\localhost\c$\Users\name\Downloads\VSCode\Code.exe path VSCode's window gets drawn. So it seems that using \\localhost isn't the same as running from an actual network path.
On the other hand, if I mount the shared path as a disk (Z: for example) and run it from there, it works.
Too bad to hear that UNC support could be dropped, it's a pretty common thing on enterprises.

@ralgozino I didn't mean to say that running from UNC is unsupported entirely, I think a mapped network drive will always work just fine. What I think will not work is running explicitly from a command line that is on \\.... Even today, you will notice that *.cmd refuse to execute from UNC paths.

@ralgozino I didn't mean to say that running from UNC is unsupported entirely, I think a mapped network drive will always work just fine. What I think will not work is running explicitly from a command line that is on \\.... Even today, you will notice that *.cmd refuse to execute from UNC paths.

Sorry for the late response. The mount as a network drive workaround was enough for me, but I can imagine some limited environments where one can't have permissions to do it. But that's another issue.
I don't know if this workaround is documented somewhere, I was lucky to try it out of dispair. It would be a nice addition to the portable version instructions may be?
Thank you for your time and your answers!
Have a nice day.


python deployment fail on liunx

https://github.com/projectkudu/kudu/blob/507a2e1b3d01c144310f9a0f74db57dbe31665e0/Kudu.Core/Scripts/select_python_version.py#L25
env var SYSTEMDRIVEis not set
repro
git deploy https://github.com/patricklee2/python-sample-vscode-django-tutorial

this deployment method is deprecated in linux
follow steps here: docs.microsoft.com/en-us/azure/app-service/containers/quickstart-python


[fix][broker] Intercept REDELIVER_UNACKNOWLEDGED_MESSAGES command

Motivation
The broker misses intercept the REDELIVER_UNACKNOWLEDGED_MESSAGES command.
Modifications

Call safeInterceptCommand() to intercept the REDELIVER_UNACKNOWLEDGED_MESSAGES command

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Hi all, this PR has been changed to only intercept the REDELIVER_UNACKNOWLEDGED_MESSAGES command.

/pulsarbot rerun-failure-checks

Codecov Report

Merging #21265 (d7eb997) into master (a7acdf6) will increase coverage by 36.59%.
Report is 25 commits behind head on master.
The diff coverage is 81.42%.

@@              Coverage Diff              @@
##             master   #21265       +/-   ##
=============================================
+ Coverage     36.73%   73.32%   +36.59%
- Complexity    12220    32592    +20372
=============================================
  Files          1711     1888      +177
  Lines        130588   140247     +9659
  Branches      14227    15411     +1184
=============================================
+ Hits          47971   102837    +54866
+ Misses        76264    29346    -46918
- Partials       6353     8064     +1711

Flag
Coverage Δ

inttests
24.12% <21.42%> (-0.06%)
:arrow_down:

systests
24.66% <22.85%> (-0.02%)
:arrow_down:

unittests
72.62% <81.42%> (+40.72%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

...rg/apache/pulsar/broker/service/AbstractTopic.java
87.75% <100.00%> (+28.73%)
:arrow_up:

...rg/apache/pulsar/broker/service/BrokerService.java
81.32% <100.00%> (+25.06%)
:arrow_up:

...n/java/org/apache/pulsar/broker/service/Topic.java
36.36% <ø> (+27.27%)
:arrow_up:

...oker/service/nonpersistent/NonPersistentTopic.java
72.06% <100.00%> (+26.99%)
:arrow_up:

...g/apache/pulsar/common/protocol/PulsarDecoder.java
64.61% <100.00%> (+6.62%)
:arrow_up:

...sar/broker/service/persistent/PersistentTopic.java
79.63% <73.68%> (+27.70%)
:arrow_up:

...va/org/apache/pulsar/broker/service/ServerCnx.java
72.05% <77.14%> (+30.64%)
:arrow_up:

... and 1447 files with indirect coverage changes

Do we cherry-pick this PR to Pulsar 2.10, Pulsar 2.11 and Pulsar 3.0?

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks