How to pass user info at runtime?

I have read docs on booting with user info. As per my understanding this needs to be done in the public client JavaScript code.
How do I pass entire user object values from my botkit controller, maybe before start hearing on.

@Purus WDYM by booting with user info ?

In my understanding we need to pass on user information to store them along
work message. Please correct me if I am wrong.
On Thu, May 31, 2018, 11:03 PM Ouadie Lahdioui<EMAIL_ADDRESS>wrote:

@Purus https://github.com/Purus WDYM by booting with user info ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/howdyai/botkit/issues/1364#issuecomment-393611981,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABBx5-UM5Q3fMpjQRvbYdx5e8FO2PtQOks5t4ClxgaJpZM4USs3Q
.

which one are you using (FB, SLack, WS, Web ...) ?

I am using web platform.
On Fri, Jun 1, 2018, 3:11 PM Ouadie Lahdioui<EMAIL_ADDRESS>wrote:

which one are you using (FB, SLack, WS, Web ...) ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/howdyai/botkit/issues/1364#issuecomment-393829411,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABBx57IZycIbIdpbdyvtitBBHNNHr5aaks5t4QwugaJpZM4USs3Q
.

@Purus take a look at these docs for dealing with user data on the web client https://github.com/howdyai/botkit-starter-web/blob/master/docs/botkit_web_client.md#share-user-accounts--profile-data-with-botkit

I have the same issue, can I by any means pass some values from the javascript where I embedded my bot on the web and use it in the controller to say validate the user and then respond accordingly?

@Purus @sudk97 you can add more keys: values to the object that you send to botkit from the frontend and then manage them with a middleware in botkit.

Any example on how to do this will be helpful.
On Mon, Jun 4, 2018, 3:52 PM Adán Toscano<EMAIL_ADDRESS>wrote:

@Purus https://github.com/Purus @sudk97 https://github.com/sudk97 you
can add more keys: values to the object that you send to botkit from the
frontend and then manage them with a middleware in botkit.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/howdyai/botkit/issues/1364#issuecomment-394306638,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABBx56xvcSsYqOQ0iN-kjEU1N98SJ2dwks5t5QpWgaJpZM4USs3Q
.

https://github.com/howdyai/botkit-starter-web/blob/e0cead4da1e0cf84ab9b12f432508e2d4365e865/public/client.js#L70
I copied the function from here and add the following...
        that.deliverMessage({
          type: 'message',
          text: text,
          user: this.guid,
          channel: this.options.use_sockets ? 'socket' : 'webhook'
          custom: 'Purus rocks!'
        });

then in botkit use middleware
controller.middleware.receive.use(function(bot, message, next) {
  console.log(message.custom); //Puru rocks!
  next();
});

How do I capture the key: value pair passed from frontend onto my skills code? Is there any specific variable that it's stored in or some mustache value?

Thanks a lot @adantoscano, worked for me :+1:


Add 1.31 E2E tests for Nutanix

Issue #, if available:
#2399
Description of changes:
Add kubernetes v1.31 E2E tests for Nutanix provider
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/test eks-anywhere-presubmit

/test eks-anywhere-cli-attribution-presubmit

/lgtm

/test eks-anywhere-presubmit


[Question]Whether T-MAC supports mixed-precision LLM?

Just like the model weight contains I2, I3, I4 quantization type
I checked the documentation and script, and it seems that it is not supported yet?
thanks!

Both the inference kernel and the convert script already supported mixed precision quantization by detecting bits of each layer. However, I don't know if there are any tools to generate a mixed precision GPTQ model. If there is such a model, T-MAC can support it.

Both the inference kernel and the convert script already supported mixed precision quantization by detecting bits of each layer. However, I don't know if there are any tools to generate a mixed precision GPTQ model. If there is such a model, T-MAC can support it.

i have see t-mac tune kernel on shape 、bits and so on; compiled llama.cpp kernel only support one bit and net; how to support mixed network?(forexample: tuned and compilered llama.cpp can run 2bit, but they run other bits will meet error）


Weird interaction with the levels module

Context:
I already brought this bug up with the author of the levels module theripper93 and they said this seems to be a problem with the pf2e module so I brought this up here instead.
Version: 4.3.4
Describe the bug
As a DM when you select a NPC Token (with the vision enabled not checked under the tokens vision options) on a lower elevation, all tokens on higher levels of elevation can be seen. By going to the tokens on the higher elevation and disable and re-enable link to actor size under appearance the tokens from the higher levels disappear again from the lower levels, but can still be selected and glitch in and out when you select a token from a lower elevation but disappear when hovered over again.
To Reproduce

Have the actual version of the levels module installed.
Create a scene with different elevations.
Put a tile as floor for the higher elevation.
Put a token on that floor.
Go to a lower elevation.
Put a token on that elevation.
Go back to the higher elevation floor and select the NPC see that the token on the lower elevation is not shown.
Go to a lower elevation and see that that the token in the higher elevation is shown.
Go to appearance on the higher elevation token and disable and re-enable link to actor size.
Token on the higher elevation is no longer shown on the lower elevation.
In addition when clicking on a tokens on the lower elevation, the tokens on the higher elevation will appear again on the lower level but disappear when hovered over.

Expected behavior
When you go to a level you should only see the token on that level and also not should only be able select the tokens on that level
Screenshots
high elevation

lower elevation

token on the lower right had been changed by going to appearance and disable and re-enable link to actor size.
Browser:
Firefox
Foundry Version:
v10.288

Weird interactions with modules are module issues, sorry.


Update Teaching “index”

Automatically generated by Netlify CMS

👷 Deploy Preview for ross-cms processing.

Name
Link

🔨 Latest commit
8a69b41b9899c971224b193c432d008e95a96ea2

🔍 Latest deploy log
https://app.netlify.com/sites/ross-cms/deploys/65daaccfefad3f00082235fc


Adding tutorial prerequisites and correcting routes

Resolving issue #421 - Tutorials should include prerequisite reminders.

Oracle CLA Bot
Thank you for your submission, we really appreciate it. Like many open source projects,
we ask that you sign our [Contributor License Agreement](http://www.oracle.com/technetwork/community/oca-486395.html) before we can accept your contribution.

@wbleonard

Oracle CLA Bot
Thank you for your submission, we really appreciate it. Like many open source projects,
we ask that you sign our [Contributor License Agreement](http://www.oracle.com/technetwork/community/oca-486395.html) before we can accept your contribution.

@wbleonard

CLA BotThank you for your submission!
It appears that the following authors have not signed our Contributor License Agreement:

Please do so now by following this link. We are working on modernizing the CLA process into a digital signature but it isn’t quite ready yet.
Once complete, let us know in our community Slack  and we’ll send you an Fn T-shirt.
Thank you for being a part of the Fn Community!

CLA Bot
Thank you for your submission!
It appears that the following authors have not signed our Contributor License Agreement:

Please do so now by following this link. We are working on modernizing the CLA process into a digital signature but it isn’t quite ready yet.
Once complete, let us know in our community Slack  and we’ll send you an Fn T-shirt.
Thank you for being a part of the Fn Community!

LGTM, please rebase your patch and sign CLA to get this merged, thanks.

cla approved, will automatically clear soon. there are conflicts now though.


Add SplitResponseProcessor to Search Pipelines

Description
Adds a new SearchResponseProcessor implementation that splits a field, comparable to the Ingest Pipeline Split Processor.
Related Issues
Part 2 (of 2) of #14758
Documentation PR (for both this and #14785)

https://github.com/opensearch-project/documentation-website/pull/7767

JSON examples were the result of actual testing of this PR code

https://github.com/opensearch-project/opensearch-api-specification/pull/440

Check List

[x] Functionality includes testing.
[x] API changes companion pull request created, if applicable.
[x] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

LGTM, thanks for the change! I'm linking this pr to the feature request issue - https://github.com/opensearch-project/OpenSearch/issues/14758

@dbwiddis this also needs api specs in https://github.com/opensearch-project/opensearch-api-specification please.

@dbwiddis this also needs api specs in https://github.com/opensearch-project/opensearch-api-specification please.

I don't see the names of the existing response processors in the current docs:

a search for rerank has no code results.  Similarly for rename_field.
It does look like these used to be part of the smithy spec. but that code has been removed.
It looks like some of the request processors are included in https://github.com/opensearch-project/opensearch-api-specification/blob/main/spec/schemas/search_pipeline._common.yaml but I don't see any of the response types there

this may be a typo
It looks like all of the response processors possibly got missed and need to be added?

@dbwiddis this also needs api specs in https://github.com/opensearch-project/opensearch-api-specification please.

Opened https://github.com/opensearch-project/opensearch-api-specification/issues/437 to track this

It looks like all of the response processors possibly got missed and need to be added?

Yes.

Is there automation to do that from the old smithy spec that can be run first?

@nhtruong will know more, but I believe that we exhausted all automation options when we switched

Will answer Spec related questions in https://github.com/opensearch-project/opensearch-api-specification/issues/437

@dbwiddis similar to 40_rename_response.yml, could we add some yaml test cases for this new processor?

@dbwiddis similar to 40_rename_response.yml, could we add some yaml test cases for this new processor?

@gaobinlong Are we still using the rest-api-spec?  I thought we were doing yaml tests at opensearch-api-specification where I have already submitted a PR.  The checklist does not refer to writing tests here; if this is to be a requirement it's going to duplicate efforts to write tests there.
Because I really want to get this PR merged before 2.16.0 code freeze I'm going to submit a test as you requested, but I'd really like @dblock and you to identify one place for API testing.  Writing multiple of the same tests in multiple languages/formats is a disincentive for anyone to contribute here.

but I'd really like @dblock and you to identify one place for API testing. Writing multiple of the same tests in multiple languages/formats is a disincentive for anyone to contribute here.

To me they don't conflict, we can add more tests in rest-api-spec to verify different use cases, but still need @dblock to clarify whether we don't need rest-api-spec anymore, and if we need it then we can add some yaml tests in later release.

To me they don't conflict

To me they are duplicate effort.
If yaml-rest-test is mandatory it should be added to the PR template.  We are less than 24 hours from code freeze, I have other priorities, and I have burned over 2 hours of late night weekend personal time fighting against what is likely a bug in yamlRestTest which is itself poorly documented.
Tell me what's wrong with my assertion? No amount of square brackets fixes this.  I'm convinced there's a bug.
  - match: { hits.hits.0.fields: { "a": ["one1, two2, three3, "], "b": ["one", "two", "three"] } }

Actual result:
         "hits" : [
           {
             "_index" : "test",
             "_id" : "1",
             "_score" : 1.0,
             "fields" : {
               "a" : [
                 "one1, two2, three3, "
               ],
              "b" : [
                 "one",
                 "two",
                 "three"
               ]
             }
           }
         ]

Error no matter what I do:
java.lang.AssertionError: Failure at [search_pipeline/90_split_response:113]: hits.hits.0.fields didn't match expected value:
                hits.hits.0.fields:
                                   a: expected String [one1, two2, three3, ] but was ArrayList [[one1, two2, three3, ]]
                                   b:
                                     0: same [one]
                                     1: same [two]
                                     2: same [three]

If solving this is a blocker to getting this merged, I give up.

To me they don't conflict

There should be one (1) spec.
Requirements for submitting PRs should be clearly specified in the CONTRIBUTING guidelines and also in the issue template.
I'm immensely frustrated that an additional requirement is being added for a PR I submitted 5 days ago when we are less than 24 hours from code freeze and I have multiple other competing priorities so I am up past midnight attempting to address this last-minute undocumented request, fighting against a poorly-documented test suite.
I love testing. I really really really do.  I want to write tests.
Once.

Flaky test tracked by:

https://github.com/opensearch-project/OpenSearch/issues/14311

I'm merging this PR even though we didn't really resolve the open question around API specification tests. For now they are somewhat split between rest-api-spec and the opensearch-api-specification repository. I don't think we need to define new things in both places and we should ultimately converge towards a single place for such tests, however I don't think we need to block this PR on that discussion.

Ah @andrross! I missed publishing the comments by few seconds


Linking to current spec

Trying to make it easier for people to find the actual spec.

Since we're about to publish it would make sense to coordinate and link to spec.openapis.org from the start.

Thanks @ralfhandl, this looks like a better way of doing it!


Remove some hardcoded use cases and organize hf_config/hf_utils

Describe your changes
Remove some hardcoded use cases and organize hf_config/hf_utils

Move static function in HfConfigMixin to ht_utils
Add new function to get the hf model type
Removed hardcoded reference to setup/restore Llama layers

Checklist before requesting a review

[ ] Add unit tests for this change.
[x] Make sure all tests can pass.
[ ] Update documents if necessary.
[x] Lint and apply fixes to your code by running lintrunner -a
[ ] Is this a user-facing change? If yes, give a description of this change to be included in the release notes.

(Optional) Issue link

/azp run


Projects should only be loaded into the Game folder when editing

Need to make the edit button available for all project types. If you hit open it will just play the game but if you select edit, it should load it into a special folder you can work from in the Workspace folder.

Archives are now loaded directly from the zip in memory and never saved to the Workspace folder unless the user clicks on the button to edit them.


Multiple onlyExistingGroup(groupId) checks

Describe the improvement you're thinking about
validateProof() checks for existing group which then calls verifyProof() which agains ensures group's existence.
Remove onlyExistingGroup(groupId) modifier on validateProof()
Additional context
PSE audit.

Assigned to @zkfriendly


关于开发环境下的webView不显示问题

Describe the bug
最近开发一个移动Hybrid的（原生+webView），在开发环境下，webView是无法显示的，浏览器下是正常显示的。但通过build后发布服务器就可以正常显示页面
Reproduction
web端之负责渲染，数据来源于移动端
System Info
在webview中不显示页面，没有信息输出

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Developing in the web view requires the latest OS/browser version used by the device/simulator, for the Vite dev server to work as it uses evergreen features. I also have a webview that works with the Vite dev server by using the latest iOS/Android simulator. So if you upgrade yours too it should work fine.
For builds, that may likely be because some syntax has been transpiled to work on lower browser versions.

Thank you. Just use the latest emulator


EmailTransport and trait objects

I am using lettre and lettre_email in a rewrite of rss2email.
I would like to use a trait object but:
error[E0038]: the trait `lettre::EmailTransport` cannot be made into an object
   --> src/main.rs:137:22
    |
137 |     let mut sender2: EmailTransport = match &settings.mail {
    |                      ^^^^^^^^^^^^^^ the trait `lettre::EmailTransport` cannot be made into an object
    |
    = note: method `send` has generic type parameters

Because of this, I am currently using an ugly hack with enum
Any thought on this ?

No generic type parameters anymore in 0.9+


Create Autolayout mockups of all the components

In order to validate the light mode variables, and make it easier to create dark mode, we need to create a mockup of all (or most of) the components using auto layout and variables.

duplicate of https://github.com/equinor/eds-core-team-workshop/issues/12


Finalize v1.0.0 Refactor

Added

Mixing (plugin) & tests
Parsing tests
More Type Guards (even if not implemented yet)
Types to color Records so that they give intellisense

Fixed

Improved parsers
README to cover refactor differences
Documentation

Changed

Coverage threshold to 95% minimum
Moved types into index in types folder for easier access

Removed

Redundant files

Codecov Report

Merging #16 (ad0089f) into master (4295579) will increase coverage by 11.19%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           master       #16       +/-   ##
============================================
+ Coverage   88.80%   100.00%   +11.19%
============================================
  Files          19        18        -1
  Lines         411       336       -75
  Branches      112       100       -12
============================================
- Hits          365       336       -29
+ Misses         46         0       -46

Impacted Files
Coverage Δ

src/conversions/hex.ts
100.00% <ø> (ø)

src/conversions/hsl.ts
100.00% <ø> (ø)

src/conversions/hsv.ts
100.00% <ø> (ø)

src/conversions/lab.ts
100.00% <ø> (+81.81%)
:arrow_up:

src/conversions/lch.ts
100.00% <ø> (+66.66%)
:arrow_up:

src/conversions/rgb.ts
100.00% <ø> (+36.53%)
:arrow_up:

src/conversions/xyz.ts
100.00% <ø> (+75.00%)
:arrow_up:

src/enums/colors.ts
100.00% <ø> (ø)

src/parsers/hex.ts
100.00% <ø> (+6.66%)
:arrow_up:

src/parsers/hsl.ts
100.00% <ø> (ø)

... and 22 more

Continue to review full report at Codecov.

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


[Feature/multi_tenancy] Handle controller index 404 on remote client

Description
When deleting a model, its model controller must be deleted, but this is not required in multitenancy.
The ResourceNotFound exception was handled for the local (Node) client case. This PR handles the appropriate OpenSearchException with 404 status returned from the remote client.
It is likely a similar fix will be required for the DynamoDB client.
Related Issues
Cherry-picked from #2818
Check List

[x] New functionality includes testing. (Covered by #2818)
[x] Commits are signed per the DCO using --signoff.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

This is flaky in most of my recent flood of PRs:
REPRODUCE WITH: ./gradlew ':opensearch-ml-plugin:integTest' --tests "org.opensearch.ml.rest.RestMLGetTaskActionIT.testGetTaskAPI_Success" -Dtests.seed=CF7A082EB109AF3F -Dtests.security.manager=false -Dtests.locale=ar-QA -Dtests.timezone=America/Caracas -Druntime.java=21

org.opensearch.ml.rest.RestMLGetTaskActionIT > testGetTaskAPI_Success FAILED
    org.opensearch.client.ResponseException: method [POST], host [http://<IP_ADDRESS>:45491/], URI [/_plugins/_ml/_train/sample_algo?async=true], status line [HTTP/1.1 500 Internal Server Error]
    {"error":{"root_cause":[{"type":"m_l_limit_exceeded_exception","reason":"m_l_limit_exceeded_exception: Memory Circuit Breaker is open, please check your resources!"}],"type":"m_l_limit_exceeded_exception","reason":"m_l_limit_exceeded_exception: Memory Circuit Breaker is open, please check your resources!"},"status":500}


Add OVC to video gallery storybook

What
Add OVC to video gallery storybook
Why
This is part of the OVC dod item
How Tested
Tested with storybook
Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

I think we need to clean up the snippet. There is extra empty lines I dont think we need?


Idea: add flag to test all feature flag permutation w/ a max # of simultaneous feature flags

maybe --feature-powerset --depth 2.
Tokio has too many features to test the power set. However, most issues can be reproduced by testing at most 2 features simultaneously. It would be nice to have a feature that tested all permutations of at most N simultaneous feature flags. This would catch most problems.

Added in cargo-hack 0.3.14 (#59).


Null ouput?

Program without editing is outputting
Destination was initially ' '
Destination reads ' '
srcArray is not used after it is initialised ? I can't see src Array referenced anywhere else in the code. Is it supposed to output destination reads 'hello world'?

Is it possible that the addresses have changed for raspberrry pi 3. wusing the bcm2837 rather ran the bcm2835?

UPDATE: works if all adresses are set to start with 3F000000 rather than 20000000 for pi versions 2 and 3

Thanks so much for providing a solution @Kroltez! I've had a number of people report this issue in a sister project, and have long-since suspected the issue was an address change, but I couldn't find definitive info.
I went ahead and made new Make targets for rpi2 and rpi3 based on this info. I wouldn't be surprised if more changes need to be made for the Pi v3 since its CPU is 64-bit but the DMA structs are using 32-bit address fields, so look out for some latent bugs on that front unless you can find something conclusive in the documentation.
If you get a chance, confirmation that the new code works would be much appreciated, but I understand if you're unable to test it for any reason.

You couldn't give me a hand could you? I'm trying to do a DMA transfer to
and from SPI say every 5ms. But at the moment I am having trouble even
doing 2 different DMA messages by running your program twice in the same
code. Do you know how to do multiple DMA transmissions?, If there is a way
of doing a "wait for" or "check done" rather than the sleep command ?
On Mon, Sep 5, 2016 at 10:44 PM, Colin Wallace<EMAIL_ADDRESS>wrote:

Thanks so much for providing a solution @Kroltez
https://github.com/Kroltez! I've had a number of people report this
issue in a sister project, and have long-since suspected the issue was an
address change, but I couldn't find definitive info.
I went ahead
https://github.com/Wallacoloo/Raspberry-Pi-DMA-Example/commit/3f076a01b61ece9eb71fec8a347f12d402287a11
and made new Make targets for rpi2 and rpi3 based on this info. I
wouldn't be surprised if more changes need to be made for the Pi v3 since
its CPU is 64-bit but the DMA structs are using 32-bit address fields, so
look out for some latent bugs on that front unless you can find something
conclusive in the documentation.
If you get a chance, confirmation that the new code works would be much
appreciated, but I understand if you're unable to test it for any reason.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Wallacoloo/Raspberry-Pi-DMA-Example/issues/1#issuecomment-244814357,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AU-0sE-DmafJY-HEOnOXsEb_XZYqkprGks5qnI0ggaJpZM4J02W8
.

Ideally for now I would like it to count up in a loop.
Any help would be appreciated.
regards
Kieron
On Tue, Sep 6, 2016 at 9:06 AM, Kieron Holt<EMAIL_ADDRESS>wrote:

You couldn't give me a hand could you? I'm trying to do a DMA transfer to
and from SPI say every 5ms. But at the moment I am having trouble even
doing 2 different DMA messages by running your program twice in the same
code. Do you know how to do multiple DMA transmissions?, If there is a way
of doing a "wait for" or "check done" rather than the sleep command ?
On Mon, Sep 5, 2016 at 10:44 PM, Colin Wallace<EMAIL_ADDRESS>wrote:

Thanks so much for providing a solution @Kroltez
https://github.com/Kroltez! I've had a number of people report this
issue in a sister project, and have long-since suspected the issue was an
address change, but I couldn't find definitive info.
I went ahead
https://github.com/Wallacoloo/Raspberry-Pi-DMA-Example/commit/3f076a01b61ece9eb71fec8a347f12d402287a11
and made new Make targets for rpi2 and rpi3 based on this info. I
wouldn't be surprised if more changes need to be made for the Pi v3 since
its CPU is 64-bit but the DMA structs are using 32-bit address fields, so
look out for some latent bugs on that front unless you can find something
conclusive in the documentation.
If you get a chance, confirmation that the new code works would be much
appreciated, but I understand if you're unable to test it for any reason.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Wallacoloo/Raspberry-Pi-DMA-Example/issues/1#issuecomment-244814357,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AU-0sE-DmafJY-HEOnOXsEb_XZYqkprGks5qnI0ggaJpZM4J02W8
.

On the original Pi, there is no elegant way to do what you want without sleeping/spinning, though it is possible to do it in an ugly way. On the Pi 2/3, there may be a better solution which I don't know of. Anyway:
What most people did for the Pi 1 is to use a "paced DMA transfer". Certain peripherals, specifically the PWM and PCM peripherals, consume data at a specific (and usually configurable) rate when active, and maintain their own 4-entry buffers. If you attempt to feed them data while their buffer is full, they will stall the DMA transfer until they consume the next entry.
Furthermore, the Pi's DMA engine allows chaining DMA control blocks (via the NEXTCONBK control block field). i.e. I can create one DMA control block ("block B") that copies data from the SPI and writes it somewhere, and then another one ("block A") which stalls for, say, 5 ms via transferring some amount of data into the PWM/PCM peripherals. Then I can configure block A such that block B is run immediately after completion.  The result is that exactly 5 ms after initiating the DMA sequence, the SPI peripheral is read.
The technical detail for creating the block that stalls 5 ms is to configure either PWM or PCM to read at some frequency F, and then creating a control block where DEST_AD=<PWM/PCM FIFO address>, .SRC_AD=<any *valid* physical address>, TXFR_LEN = 5 ms/1000 ms * f and the TI field ("Transfer Info") is such that DEST_INC=0 so that the write address remains at the buffer's head and DEST_DREQ is set to the appropriate value based on whether PWM or PCM or some other timer-based peripheral is pacing the transfer. These values are found on page 61 here.
Checkout dma-gpio.c. It uses PWM to pace the transfers in a very similar way as I just described.
There are some obvious downsides to this method that could warrant more research for the Pi 2/3 though: paced transfers prevent any other application (e.g. userland audio) from using whichever peripheral you choose to do your pacing (PWM/PCM). The DMA channel you use is continually active, potentially slowing down other DMA operations (network, screenbuffer, SD card operations) and wasting electrical energy. The latter is probably not much of an issue for you since you can easily drive the PWM/PCM module at its minimum clock rate.

file:///home/pi/code/DMA-Example/dma-example.txt
This code is essentially your code running in a loop so that it says hi world:1, hi world:2 ... ect however it does hi world 1: and then it doesn't change. Is because the page is cached ? Or am I not resetting something correctly?

dma-examplev1.txt
Or more simply here I have just copied and pasted the relevent code bellow so now it should say hellow world the say hello earth. but the second time it outputs hello world again

@Kroltez I think you're right about it being a cache problem, as what you have looks fine to me. Perhaps you can try using the makeUncachedMemView function from dma-gpio.c and writing to srcArray / reading from destArray through the uncached views?

I'm new to low level programming, what do you mean by writing ang reading
though the unchached views ? Copy the function over and call it using
destArray = makeUncachedMem(srcArray, PAGE_SIZE, memfed, pagemapfd); ?
On Wed, Sep 7, 2016 at 4:20 PM, Colin Wallace<EMAIL_ADDRESS>wrote:

@Kroltez https://github.com/Kroltez I think you're right about it being
a cache problem, as what you have looks fine to me. Perhaps you can try
using the makeUncachedMemView
https://github.com/Wallacoloo/Raspberry-Pi-DMA-Example/blob/master/dma-gpio.c#L526
function from dma-gpio.c and writing to srcArray / reading from destArray
through the uncached views?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Wallacoloo/Raspberry-Pi-DMA-Example/issues/1#issuecomment-245315505,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AU-0sJuF9xk3dtbatiIUdP4WJ5wlShqeks5qntZQgaJpZM4J02W8
.

ok btw just been told by someone that makeVirtPhysPage() doesnt work very
well on Rasp V2 and V3 and eh thinks that might be the problem
On Wed, Sep 7, 2016 at 4:48 PM, Kieron Holt<EMAIL_ADDRESS>wrote:

I'm new to low level programming, what do you mean by writing ang reading
though the unchached views ? Copy the function over and call it using
destArray = makeUncachedMem(srcArray, PAGE_SIZE, memfed, pagemapfd); ?
On Wed, Sep 7, 2016 at 4:20 PM, Colin Wallace<EMAIL_ADDRESS>wrote:

@Kroltez https://github.com/Kroltez I think you're right about it
being a cache problem, as what you have looks fine to me. Perhaps you can
try using the makeUncachedMemView
https://github.com/Wallacoloo/Raspberry-Pi-DMA-Example/blob/master/dma-gpio.c#L526
function from dma-gpio.c and writing to srcArray / reading from destArray
through the uncached views?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Wallacoloo/Raspberry-Pi-DMA-Example/issues/1#issuecomment-245315505,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AU-0sJuF9xk3dtbatiIUdP4WJ5wlShqeks5qntZQgaJpZM4J02W8
.

@Kroltez Sorry for the delay. That's indeed what I meant though. Any data that both your C code and the DMA engine are going to be reading/writing should be addressed in a way that bypasses the L1 cache.
In the Pi 1, the addressing scheme issuch that any address < 0x20000000 corresponds to a request from the L1 cache, which will query the actual RAM on your behalf . Then the various peripherals are given addresses between 0x20000000-0x40000000. 0x40000000-0x600000 corresponds to the L2 cache, then there are some more memory-mapped devices, and finally the physical RAM is accessed directly by 0xc0000000-0xe00000.
The DMA engine cannot communicate with the L1 cache, but it can use the L2 cache. Therefore, all the addresses that need to be used by your C code and the DMA engine should be modified to be in the range 0x40000000-0x600000. Because the operating system uses virtual addresses, you need to allocate virtual memory for both srcArray and destArray (i.e. malloc()), determine their physical address (virtToPhys()), add 0x40000000 to get a new physical address that bypasses L1, give that physical address to the DMA engine, and then map it to another virtual memory page so that your C code can use it (since all memory accesses in your program have to be to virtual memory), using mmap(). This is essentially what makeUncachedMemView() does.
Given that the bus addresses of all the peripherals changed in the Pi 2/3/zero, the bus address of the L1 cache probably also changed and may be responsible for the failures seen. This is especially likely in the Pi 3, since it comes with double the RAM. If I were in your shoes, I would track down the bus address of the L1 cache and alter the virtToUncachedPhys function so that it adds that value to the physical address (with L1 previously located at 0x40000000, I was able to just bitwise-or the value, but if the new bus address isn't a power of two, you'll have to add that offset).
If you can't find this information in any documentation, you can potentially brute-force solve it by writing a value to some physical ram address, addr, flushing the cache, and then seeing if a read from addr+0x50000000 gives the same value, then test addr+0x60000000, and so on.

I got it working here: https://github.com/Kroltez/PI-DMA-Counter
Just need to connect it to SPI, I have set up the TI on the control block
to do a DREQ on channel 6 but that where I'm at. I have a program that
polls the CPU and get a pretty accurate tick so I am using that rather than
the PWM whatsit you suggested.
On Fri, Sep 9, 2016 at 4:27 PM, Colin Wallace<EMAIL_ADDRESS>wrote:

@Kroltez https://github.com/Kroltez Sorry for the delay. That's indeed
what I meant though. Any data that both your C code and the DMA engine are
going to be reading/writing should be addressed in a way that bypasses the
L1 cache.
In the Pi 1, the addressing scheme issuch that any address < 0x20000000
corresponds to a request from the L1 cache, which will query the actual RAM
on your behalf . Then the various peripherals are given addresses between
0x20000000-0x40000000. 0x40000000-0x600000 corresponds to the L2 cache,
then there are some more memory-mapped devices, and finally the physical
RAM is accessed directly by 0xc0000000-0xe00000.
The DMA engine cannot communicate with the L1 cache, but it can use the
L2 cache. Therefore, all the addresses that need to be used by your C code
and the DMA engine should be modified to be in the range
0x40000000-0x600000. Because the operating system uses virtual addresses,
you need to allocate virtual memory for both srcArray and destArray (i.e.
malloc()), determine their physical address (virtToPhys()), add
0x40000000 to get a new physical address that bypasses L1, give that
physical address to the DMA engine, and then map it to another virtual
memory page so that your C code can use it (since all memory accesses in
your program have to be to virtual memory), using mmap(). This is
essentially what makeUncachedMemView() does.
Given that the bus addresses of all the peripherals changed in the Pi
2/3/zero, the bus address of the L1 cache probably also changed and may be
responsible for the failures seen. This is especially likely in the Pi 3,
since it comes with double the RAM. If I were in your shoes, I would track
down the bus address of the L1 cache and alter the virtToUncachedPhys
function so that it adds that value to the physical address (with L1
previously located at 0x40000000, I was able to just bitwise-or the
value, but if the new bus address isn't a power of two, you'll have to add
that offset).
If you can't find this information in any documentation, you can
potentially brute-force solve it by writing a value to some physical ram
address, addr, flushing the cache, and then seeing if a read from
addr+0x50000000 gives the same value, then test addr+0x60000000, and so
on.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Wallacoloo/Raspberry-Pi-DMA-Example/issues/1#issuecomment-245946902,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AU-0sFSyzw_1QFfB95Wc2yypnw6l0-59ks5qoXrTgaJpZM4J02W8
.


[feature] New example: MAE pretraining on ImageNet 1000 dataset

Colossal-AI implementation of MAE, arxiv.
As an example, we just cover the pretrain phase with ImageNet 1000 mini dataset. Helpers under subdir util/ are from facebookresearch/deit,
under Apache License 2.0.
About the coding style
The coding style might be a little different from other examples like run_resnet_cifar10_with_engine.py, the configuration config/pretrain.py handled rich initialization logic and default values.
The DeiT and MAE code has a really complicated and intertwined initialization process. By making full use of Colossal-AI's dynamic python configuration ability, we can keep things simple enough for newcomers to understand.

Hi, as we want to support hybrid parallel MAE, can you try to support TP and PP as well? You can refer to the tutorial.

Pure DP MAE with colossal has been finished by https://github.com/lucasliunju/mae-colossalai

Okay, thank you for the help! I might be a beginner and I'm glad to check those links.

Hey everybody! I managed to support (limited) Tensor Parallelism, check it by running:
torchrun --standalone --nnodes 1 --nproc_per_node 4 main_pretrain.py --config ./config/pretrain_1d_tp2.py

I tune the model inside models_mae_tp.py. More information in README.md

Add save & load model functionality, with colossalai.utils.checkpointing.

Hi @ofey404, thank you for your contribution! Would you please provide train logs in different parallelism settings?

Hi @ofey404, thank you for your contribution! Would you please provide train logs in different parallelism settings?

Several epochs or a full run? A full 800 epochs run might take a long time to finish...

Hi @ofey404, thank you for your contribution! Would you please provide train logs in different parallelism settings?

Several epochs or a full run? A full 800 epochs run might take a long time to finish...

Perhaps you could consider providing some basic validation first, such as on CIFAR or a subset of ImageNet, eg. ImageNet100. As well as using the idle time of server at night to verify 30% epochs of ImageNet. So, we can provide this to users with confidence to some extent.
Finally, you can complete the convergence verification.

ImageNet100 on kaggle is 16 GB while ImageNet1000 I used is only 2 GB. CIFAR10 might be a good candidate for basic validation.
The problem is that, the original pretrain part of MAE doesn't contain a validation part, only the main training process has validation. So I'd better implement the main process too.


Error with a command with @ in xypic

I used apxproof.sty for a recent joint paper.
Thanks to this package, our time is saved a lot. I appreciate the developers.
During writing the paper, we have faced an unexpected compile error.
The following example cannot be compiled:
\documentclass{article}
\usepackage[all]{xy}
\usepackage{apxproof}
\begin{document}
\section{First Section}
\begin{toappendix}
\begin{displaymath}
<EMAIL_ADDRESS>& B}
\end{displaymath}
\end{toappendix}
\end{document}

Indeed, if I save this as bad.tex and try to compile it by
pdflatex -halt-on-error bad.tex
then I get the following error:
! Argument of \next@ has an extra }.
<inserted text>
                \par
l.5<EMAIL_ADDRESS>& B}

!  ==> Fatal error occurred, no output PDF file produced!

I'm using the latest apxproof.sty v1.20, pdfTeX Version 3.14159265-2.6-1.40.20 (TeX Live 2019), and Xy-pic version 3.8.9.
The use of \xymatrix should be correct, since the following example can be compiled successfully:
\documentclass{article}
\usepackage[all]{xy}
\usepackage{apxproof}
\begin{document}
\section{First Section}
\begin{displaymath}
<EMAIL_ADDRESS>& B}
\end{displaymath}
\end{document}

If there is no @, then the error is not caused.
The following example can be successfully compiled:
\documentclass{article}
\usepackage[all]{xy}
\usepackage{apxproof}
\begin{document}
\section{First Section}
\begin{toappendix}
\begin{displaymath}
  \xymatrix{A\ar[r]_f & B}
\end{displaymath}
\end{toappendix}
\end{document}

Actually, we have found a workaround of this.
Any @ inside an expanded macro does not seem to cause an error.
The following example can be successfully compiled:
\documentclass{article}
\usepackage[all]{xy}
\usepackage{apxproof}
<EMAIL_ADDRESS>\begin{document}
\section{First Section}
\begin{toappendix}
\begin{displaymath}
  \xymatrix{A\dottedarrowr_f & B}
\end{displaymath}
\end{toappendix}
\end{document}

We used this in the recent paper, but it was a bit tiring to do.
Could you solve this?

I've just found another workaround.
The following is successfully compiled:
\documentclass{article}
\usepackage[all]{xy}
\usepackage{apxproof}
\begin{document}
\section{First Section}
\begin{toappendix}
\makeatother
\begin{displaymath}
<EMAIL_ADDRESS>& B}
\end{displaymath}
\makeatletter
\end{toappendix}
\end{document}

I guess I've managed to solve this. Please see the pull request.

Fixed by #37. Thanks again for the bug report, and for the solution.


Error when running tsc in Quartz Project Folder

when i run
tsc
in my Quartz repo i get the an error on the following code:
const tagRegex = new RegExp(   /(?:^| )#((?:[-_\p{L}\p{Emoji}\p{M}\d])+(?:\/[-_\p{L}\p{Emoji}\p{M}\d]+)*)/,   "gu", )
Error: "quartz/plugins/transformers/ofm.ts:133:24 - error TS1530: Unicode property value expressions are only available when the Unicode (u) flag or the Unicode Sets (v) flag is set.
133   /(?:^| )#((?:[-\p{L}\p{Emoji}\p{M}\d])+(?:/[-\p{L}\p{Emoji}\p{M}\d]+)*)/,"
Why is it doing this and what do i do to fix it?
Thanks!

you're missing this commit https://github.com/jackyzha0/quartz/commit/2154d36d9993e128faaa6471cdae305cca3d810d

git remote -v
origin	git@github.com:quasaur/thoughts.git (fetch)
origin	git@github.com:quasaur/thoughts.git (push)
upstream	https://github.com/jackyzha0/quartz.git (fetch)
upstream	https://github.com/jackyzha0/quartz.git (push)
git fetch upstream
...will this command resolve the issue?

RESOLVED...grabbed and inserted the new file contents from your code.


Policies for controlling leaseholder location

Background: https://airtable.com/tblD3oZPLJgGhCmch/viw8IfZMg9Up8SP33/reclZqRmshwJNaq4S
PM: @awoods187
Eng Partner: @a-robinson

PR: https://github.com/cockroachdb/cockroach/pull/28261
From release notes:

The ability to set lease placement preferences in replication zones is now fully supported. Existing lease placement preferences will continue to function as in v2.0. [#28261][#28261] {% comment %}doc{% endcomment %}

@rmloveland, this is ready, and it's a very useful feature, so we should prioritize it.


Better TypeScript types for inherited methods

I have started using immutable.js within a TypeScript (1.5.3) project and it is working great save for one small annoyance.
Please excuse me if this has already been asked before or if there is something obvious that I am missing.
import { List } from 'immutable';

function printNiceList(listOfStrings: List<string>): void {
  console.log(listOfStrings.pop().join(', ') + ', and ' + listOfStrings.last());
}

var countries = List(['USA', 'UK', 'Ukraine', 'Uzbekistan']);

// This works nicely:
printNiceList(countries);

// This does not pass the type check:
printNiceList(countries.rest());
// TSC errors with:
// error TS2345 Argument of type 'Iterable<number, string>' is not assignable to parameter of type 'List<string>'.
// > TS2324 Property 'set' is missing in type 'Iterable<number, string>'.

// The type needs to be explicit to get it to work:
printNiceList(<List<string>>countries.rest());

// Same issue with all inherited methods like: slice, splice, skip, concat, e.t.c

Since I work with List<Blah> a lot I end up having to insert <List<Blah>> all over the code which is a little annoying.
Would it be possible to redefine the inherited method types in the .d.ts file so that these methods' return type is List<Blah> vs Iterable<number, string> ?

rest() returns a Seq, not a List, so you'll need to accept something more generic. I'd recommend:
printNiceList(listOfStrings: IndexedIterable<string>)

Hi @leebyron ,
Thank you for the reply.
You can not change the type signature of printNiceList because it calls pop. You would get an error of error TS2339 Property 'pop' does not exist on type 'IndexedIterable<string>'.
I am not sure what you mean when you say that rest() does not return a list as the return type of it certainly behaves like a list by having the pop method and satisfying List.isList (as one would expect).
var countries = List(['USA', 'UK', 'Ukraine', 'Uzbekistan']);
console.log(List.isList(countries.rest())); // => true

As far as I can see Immutable's logic is solid, it is only the TS type definition that is lacking as it is indication a more generic return type (and that too is only a small cast inconvenience).

Closing this aging issue - latest in master has excellent types which will be released soon


Updating Security Measures

Dear @david-berthelot ,
Hope you're doing well 😄 !
I found out this project and immediately realised its potential. I want to update the project with some secure syntax. Can I get the names of thePython files which are standalone and not being imported to other files so that I can create a dedicated PR ? Thanks in advance 👍
PS :: I will try my best to make this project a success.

This is not a project meant for collaboration, this is a snapshot of the source code associated with the LAG paper. Basically it is a reference, if you want to improve it or add modifications to it, I suggest that you fork it. Thanks.

So, for creating a dedicated PR can I have the list to make the PR more recently available.  😃

Sorry I don't have the information you are asking readily available. I'm not sure what you are trying to do but could probably grep the imports or something like that. Typically research code is open sourced so that people can ask technical questions related to the method itself. Here it seems you're trying to customize the code and it's outside of  the scope of what we can feasibly support. Thanks for your understanding.

No worries, I'm not grep-ing the imports. I'm refactoring the code with the currently securest syntax which resolves some runtime errors and some security vulnerabilities.
So, can I work on that ?

I think the best option in this case is to make your own fork in your own repo with all the changes you desire to make. This code is provided as-is as a way of reproducing results from the paper, it won't be updated, sorry to repeat myself but it's just a snapshot.


endpoint:qingstor: Support specify zone for used in intranet

Close for implemented in https://github.com/yunify/qscamel/commit/397243b50a3ad83e5b75b9af0e4faa6fdb5e3059 .


Error: ENTITY_NOT_FOUND DATASET_CONFIGURATION

Which connector were you using?
GKE Usage Metering
What's going wrong with this connector?
Attempting to create a new report after creating and configuring a datasource with the GKE Usage Metering connector causes the following error:
)]}'
{"reason":5,"errorStatus":{"reason":5,"code":5,"reasonStr":"ENTITY_NOT_FOUND","errorCategoryStr":"DATASET_CONFIGURATION","category":5,"uniqueErrorCode":"a8576333"},"params":{"errorId":"a8576333"}}

This issue should now be fixed. Can you try again and let me know if you're still facing this issue?

Works now, thanks.


Tags are not updated in dashboard.

No tags are update after dashboard creation.  Removing or adding tags, creates terraform changes but applying them has no effect on the dashboard.

There are separate endpoints on the API for updated tags on Alerts and Dashboards. I've add an issue on go-wavefront to add support for this. We can then add support for managing tags to the provider


How to run a job "right now", then do it again after 24 hours, then again after 24 hours...

I read the "Interval" section in the documentation. The provided example is "@every 1h30m10s". But the job only executes the first time AFTER 1h30m10s from the moment I run main.go. What if I want it to execute immediately after I run main.go, then execute again every 1h30m10s? I do not want it to wait 1h30m10s before executing the first time.
Please help, thank you!

I have a similar situation. The fact is that this library can't trigger a job immediately.
But you can run your job or func directly. Just like this:
//go yourFunc()
go yourJob.Run()

Exactly ^


Add logout button UI

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Used the shared Button component to make a styled component for the Log out button, tweaked a part of the UI structure of the header to place the items as needed., and updated the tests to cover the rendering of the Log out button.
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[x] Manually (please, describe, if necessary)
[x] Unit checks
[ ] Integration checks
[ ] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)

@rAzizbekyan let's do a redirect to "/logout", that's it


Conway’s Game of Life

As promised the Life app. Thanks for your help with making it responsive.

Looks great, thanks!
What's the reasoning behind jekyll-theme-minimal though?

A mistake when I made the repository pages  public to test it. Do I need to redo the pull request?
Sent from my iPad

On 4 Jun 2020, at 08:46, Gordon Williams<EMAIL_ADDRESS>wrote:

Looks great, thanks!
What's the reasoning behind jekyll-theme-minimal though?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

That's perfect - thanks!


fix the "Basic cookbooks" link

PR Summary
I found a mistake on the PowerShell Web Docs: Basic cookbooks link, but searching on the documentation, the only link that mention "cookbook", is the suggested.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[x] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

It's right? Is any file missing?

Appveyor CI temporary failed.

@iSazonov how can I help to solve the AppVeyor error?

@vmsilvamolina I restarted build on AppVeyor as it's not related to your changes

I had to restart AppVeyor again.  Ping me if I don't update the PR within a day.

@TravisEz13 This looks ready for merge.

@vmsilvamolina Thanks for your contribution!


Handle file permissions for data/upload creation

Currently in app.cfg we have the following configuration that is not be utilized:
GLOBUS_BASE_FILE_USER_NAME = ''
GLOBUS_ADMIN_FILE_USER_NAME = ''
GLOBUS_GENOMIC_DATA_FILE_GROUP_NAME = ''
GLOBUS_CONSORTIUM_FILE_GROUP_NAME = ''

These are currently being implemented here: https://github.com/sennetconsortium/ingest-api/blob/e8f3d6a0d02d173dfbd943909a1159993da06143/src/lib/ingest_file_helper.py#L130
The issue is that setfacl is not working against the AWS filesystem:
https://github.com/sennetconsortium/ingest-api/blob/e8f3d6a0d02d173dfbd943909a1159993da06143/src/lib/ingest_file_helper.py#L175
The directories and files within should have the permissions of drwxr-x--- but currently set to drwxr-xr-x.

[ ] All protected directories (all Uploads and protected datasets) need to be manually modified using the following command:

chmod 750 <dirname>

[x] Remove the GLOBUS_ properties and all instances in the code and modify the setfacl line to set the permissions as stated above

Commenting this here for future: https://chmod-calculator.com/


Fully support (Upstream|Downstream)TlsContext config in QUIC

Currently not all config knobs in https://github.com/envoyproxy/envoy/blob/main/api/envoy/extensions/transport_sockets/tls/v3/tls.proto take effect in QUIC listener. Below are the ones which do not take effect and are not hidden behind #not-implemented-hide:
UpstreamTlsContext:
allow_renegotiation: not supported by QUICHE.
max_session_keys: needs plumbing. Envoy is hard-coded with the QUICHE default kDefaultMaxEntries (1024) in quic_client_session_cache.cc
DownstreamTlsContext:
require_client_certificate: needs plumbing. Explicitly disabled by https://github.com/envoyproxy/envoy/pull/24011
one of session_ticket_keys, session_ticket_keys_sds_secret_config, disable_stateless_session_resumption: needs plumbing. Session resumption is currently disabled by the default EnvoyQuicProofSource implementation.
session_timeout: not applicable, the boring SSL interface is only used for TLS 1.2 or earlier.
ocsp_staple_policy: OCSP response is not supported by QUICHE.
full_scan_certs_on_sni_mismatch: needs plumbing. Envoy always picks the first cert chain in the config.
CommonTlsContext:
tls_(minimum|maximum)_protocol_version: not applicable as QUIC only supports TLS 1.3.
ecdh_curves: needs plumbing. QUICHE supports the same default ones.
alpn_protocols: not applicable as the QUIC version supported in Envoy only allows "h3".
custom_handshaker: not applicable. Envoy can config similar feature via a custom quic crypto stream and proof source.
key_log: boring SSL keylog is not supported by QUICHE.

This needs a non-stale bot!


org settings: Handle floating point durations better.

Fixes: #9253.
Tests: Added node tests.
(Casper may fail, I'll fix them once below points are addressed)
Needed feedback about:

Up to what precision we want to handle floating point value as there are various problems in converting minutes in decimal to seconds and vice-versa beyond a single floating point. Currently, I've limited it to one floating point.
I guess there should be a minimum value below which we don't need to set edit limit like don't allow value set below 10 sec and maybe we should enforce this in backend and frontend both, thoughts?
There is a small bug if the limit is set to <0.05 it get converted to 0.0 and automatically set to "Any time". This bug will get fixed once above point is addressed.
How we want to show pure integer time: 100 or 100.0

@timabbott @rishig  FYI.

I think these should be integer only. We don't enforce things on a 6 second accuracy anyway; e.g. we give something like a 10 second grace period.


Added Logic to Manually Remove VLANs for OS9 Runner

This adds what we talked about @naved001 and @tzumainn. Tested on newest firmware OS9 switch for different port configs:

One with VL623 and other tagged VLANs
Just VL623
No VLANs but still switchport
No switchport

The steps are:

Run command on switch to get vlan info
Parse the actual strings we need from that output using regex
Check if we found untagged/tagged vlans and set variables accordingly
If tagged vlans are found, parse the range string into a list of strings (without ranges)
Remove untagged and tagged vlans from ports

@larsks I'm adding you as a reviewer on this as well. There are some relatively fancy data parsing going on here in ansible, I'd love to find out if there's a simpler way to do any of this.

@naved001 that solution seems to break error handling. We would have to ignore errors on that task since it spits out an error for each non-existent vlan/port combination. So if the task fails with vlans we actually want to remove we won't know about it. Do you think it makes sense to trade the complexity of the solution in this PR with that? I'm not really leaning any specific way

@hakasapl we still plan to run the default interface <port-name> command after we remove the VLANS. So, if we somehow fail to remove the VLANs then the default command would fail (or remove the VLAN) and we would know.
@larsks @tzumainn any thoughts on this?

I do like @naved001's solution just because it doesn't require any complex parsing of switch output. Losing per-vlan error reporting seems like a reasonable price to pay. Instead of ignoring errors we could use failed_when so that the task errors out if we see anything other than a No such port in Vlan error.


Show description of alert if available

Pull Request Test Coverage Report for Build 1420

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.007%) to 86.476%

Totals

Change from base Build 1413:
0.007%

Covered Lines:
3646

Relevant Lines:
4041

💛  - Coveralls


PromiseKit 8

Hello.
Thank you for CloudKit.
PromiseKit 6 -> PromiseKit 8.

Hello @mxcl
Can you give write access here, please?

You should have it now


simplified code with ternary operator

I agree this is a nice improvement!  However, I tend to avoid using ternary operators in my examples to be friendlier to beginners.


Theme button in footer incorrectly italicized

Environment

Python version: 3.9.6
Nautobot version: 1.4.0-alpha

Steps to Reproduce

The "Theme" button in the footer is italicized, whereas all other buttons in the footer are not.  This was a mistake on my end from a previously submitted PR (that has already been closed).

Expected Behavior
The button should not be italicized.

Observed Behavior
The button is italicized.

Closed by #1816


Remove or document methodology in docs folder

There's a fairly empty qmd file in the docs folder. Do we need it? Can we remove it?

Yes. It is supposed to hold the code to create the tree diagram or org chart. Moved it to LAN.

Fixed in merge


Explain add mv rewrite info

Proposed changes
in query rewrite by mv, we want know the mv rewrite process info
such as materializedView used by rewrite, which materializedView rewrite success, and
chosen which materializedView by cost finally.
we can run sql as following to see the mv rewrite process summary info
explain <query _sql>
materializedView rewrite info is under the MATERIALIZATIONS,
example as following:
we can see the mv2_3 materializedView is rewritten successfuly and chosen finally.
and mv2_4 and mv1_3 is failed,

========== MATERIALIZATION'S ==========

========== AVAILABLE MATERIALIZATION'S ==========
[
mv2_3
mv2_4
mv1_3
]
========== REWRITTEN SUCCESS MATERIALIZATION'S ==========
[
mv2_3
]
========== CHOSEN MATERIALIZATION'S ==========
[
mv2_3
]

if want to see detail info,we can also run sql as following to see the mv rewrite process info
explain memo plan as <query _sql>
materializedView rewrite info is under the MATERIALIZATIONS,
example as following:
we can see the mv2_3 materializedView is rewritten successfuly and chosen finally.
and mv2_4 and mv1_3 is failed with fali reason.

========== MATERIALIZATIONS ==========
materializationContexts:

MaterializationContext[mv1_3] ( rewriteSuccess=false, failReason=[
ObjectId : ObjectId#257.
Summary : Match mode is invalid.
Reason : matchMode is VIEW_PARTIAL.

ObjectId : ObjectId#260.
Summary : Match mode is invalid.
Reason : matchMode is VIEW_PARTIAL.

ObjectId : ObjectId#251.
Summary : Match mode is invalid.
Reason : matchMode is VIEW_PARTIAL.

ObjectId : ObjectId#254.
Summary : Match mode is invalid.
Reason : matchMode is VIEW_PARTIAL.

] )

MaterializationContext[mv2_4] ( rewriteSuccess=false, failReason=[
ObjectId : ObjectId#257.
Summary : The graph logic between query and view is not consistent.
Reason : graph logical is not equal, query join edges is [<{0} --LEFT_OUTER_JOIN-- {1}>],
query filter edges is [<{0} --FILTER-- {}>, <{1} --FILTER-- {}>[[] , [<{0} --LEFT_OUTER_JOIN-- {1}>]]],
view join edges is [<{0} --LEFT_OUTER_JOIN-- {1}>],
view filter edges is [<{0} --FILTER-- {}>, <{1} --FILTER-- {}>[[] , [<{0} --LEFT_OUTER_JOIN-- {1}>]]]
inferred edge with conds {}
with error edge <{1} --FILTER-- {}>[[] , [<{0} --LEFT_OUTER_JOIN-- {1}>]]=[(o_orderdate#20 = 2023-12-01)].

ObjectId : ObjectId#260.
Summary : The graph logic between query and view is not consistent.
Reason : graph logical is not equal, query join edges is [<{0} --LEFT_OUTER_JOIN-- {1}>],
query filter edges is [<{0} --FILTER-- {}>, <{1} --FILTER-- {}>[[] , [<{0} --LEFT_OUTER_JOIN-- {1}>]]],
view join edges is [<{0} --LEFT_OUTER_JOIN-- {1}>],
view filter edges is [<{0} --FILTER-- {}>, <{1} --FILTER-- {}>[[] , [<{0} --LEFT_OUTER_JOIN-- {1}>]]]
inferred edge with conds {}
with error edge <{1} --FILTER-- {}>[[] , [<{0} --LEFT_OUTER_JOIN-- {1}>]]=[(o_orderdate#20 = 2023-12-01)].

ObjectId : ObjectId#251.
Summary : The graph logic between query and view is not consistent.
Reason : graph logical is not equal, query join edges is [<{0} --LEFT_OUTER_JOIN-- {1}>],
query filter edges is [<{0} --FILTER-- {}>, <{1} --FILTER-- {}>[[] , [<{0} --LEFT_OUTER_JOIN-- {1}>]]],
view join edges is [<{0} --LEFT_OUTER_JOIN-- {1}>],
view filter edges is [<{0} --FILTER-- {}>, <{1} --FILTER-- {}>[[] , [<{0} --LEFT_OUTER_JOIN-- {1}>]]]
inferred edge with conds {}
with error edge <{1} --FILTER-- {}>[[] , [<{0} --LEFT_OUTER_JOIN-- {1}>]]=[(o_orderdate#20 = 2023-12-01)].

ObjectId : ObjectId#254.
Summary : The graph logic between query and view is not consistent.
Reason : graph logical is not equal, query join edges is [<{0} --LEFT_OUTER_JOIN-- {1}>],
query filter edges is [<{0} --FILTER-- {}>, <{1} --FILTER-- {}>[[] , [<{0} --LEFT_OUTER_JOIN-- {1}>]]],
view join edges is [<{0} --LEFT_OUTER_JOIN-- {1}>],
view filter edges is [<{0} --FILTER-- {}>, <{1} --FILTER-- {}>[[] , [<{0} --LEFT_OUTER_JOIN-- {1}>]]]
inferred edge with conds {}
with error edge <{1} --FILTER-- {}>[[] , [<{0} --LEFT_OUTER_JOIN-- {1}>]]=[(o_orderdate#20 = 2023-12-01)].


Scan Crop results in wrong position and scale

I prepare an area to crop like this:

After hitting "Preview Scan" in "Pixel Type and Bright", I get the following:

Relevant system information:
Windows 10 Pro
Scanner: CanoScan LiDE 220
Driver: CanoScan LiDE 220 Scanner Driver Ver.1.02 (Windows) (TWAIN-Compatible)

I'm experiencing the exact same problem, with a Epson LiDE 110 scanner.
I tested it with Windows 10, Windows 7, GTS 2.4 and 2.3, a desktop and a notebook.
In all combinations it shows that behavior.

Same here, I scan crop first and after the preview it becomes blank. Also, when I then scan crop again, it shows the wrong crop area:

Canon Pixgma MG5250

Just updated all my drivers and got the latest version.
The bug still remains, GTS remains unusable for me because of this bug.

@LaylConway
Just so you know...
I've got an Epson GT-1500 scanner and it worked perfectly.


Beautify NSError cases when thrown 💄

Ensures the NSError case is handled in MessageInfo and attempts to resolve #270
Checklist

[x] I've added at least one test that validates that my change is working, if appropriate
[x] I've followed the code style of the rest of the project
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary

@swift-ci Please test

@swift-ci Please test


DBZ-7903 Improve blocking snapshot reliability in case of restart

closes: https://issues.redhat.com/browse/DBZ-7903
Tasks:

[X] Change on main relational connectors
[x] Change on MongoDB
[x] Address others connectors
[x] Evaluate if incremental snapshot can be moved to SnapshotType enum too

/packit test --labels oracle

/packit test --labels oracle

For MongoDB I just added the test case checking that the current implementation is not affected by the issue since the implementation differs. As of now I think it is not worth to invest time to align it. @jpechane WDYT?

/packit test --labels oracle

/packit test --labels oracle

@jpechane Tests failures is not related.

@jpechane can you have another look?

@mfvitale Applied, thanks a lot! Please keep an eye on non-core connector CI builds to make sure eferything fits together.

@mfvitale OK, it seems that the method rename did not get into the all non-core repos. Could you please fix it and merge it on your own? Thanks


Add readme for grails plugin

This adds a readme file for the grails plugin as requested in #7175

Good job!

Thanks for merging and tidying up the PRs.


Hundred and

This commit adds code to conditionally include the "and" conjunction to the "hundred" phrase of the number whenever there is a remainder in the hundred portion of the number. For example the number 503,600 will be read as "five hundred and three thousand, six hundred".

can it spell 500.000.000
five hundred million
or it will say five hundred and million?


HUDI-170 Updating hoodie record before inserting it into ExternalSpillableMap

Added MergeHandle unit-test to #777

@n3nash @vinothchandar : Please review when you get a chance.


Go to definition broken in latest version of VS Code (1.5) + older TypeScript

VSCode Version: 1.5
OS Version: OS X Yosemite

Steps to Reproduce:

Open up project
Click the cursor over a method
Click F12 to try to go to definition and nothing happens
Switch to using VS Code 1.4 and repeat steps 1-3 and everything works as expected

This feels like a really bad bug as it makes the latest version of VS Code pretty much unusable for me unless there is some workaround that I'm not aware of. Also, it would be nice if there was an official download source to downgrade to a prior version. Fortunately, I found one in my trash this time, but I will definitely be disabling auto update because of this for future releases.

I'm a team member of Davids.  We're still using TS 1.6.  If we select to use 1.6 at the popup during start, we get no code completion/navigation.  If we select to use 1.8 everything works.

@waderyan Do you know if we support back compat for typescript versions?

hey @DavidRigglemanININ thank you for opening this issue.
I broke off your other request into its own issue - https://github.com/Microsoft/vscode/issues/11796
This issue falls into TypeScript language service, so I will migrate to them.

@ramya-rao-a yes you can use different TypeScript versions. See docs here.

@ramya-rao-a yes you can use different TypeScript versions. See docs here.

This issue was moved to Microsoft/TypeScript#10821

@dbaeumer this is the issue we have discussed over mail. I have recreated the issue using TS 1.6.0-dev.20150825.
Code is as follows.
Person.ts
class Person {

    constructor(private name: string) {}
}

export default Person;

test.ts
import * as p from './Person';

When using TS 1.8 and above I can do Go To Definition by right clicking on p in test.ts.

this version feels very broken to me.  No more for loop code completion.  no Command-e.  Command-p find shows too many results.  How do I go back a version?

@tdekoekkoek Could you open a separate issue for cmd+p showing too many results? (The announcement for 1.4 has links near the top to the 1.4 downloads if you want to go back to that.)

This one bad version of vs code, I will go back to 1.4.
This problem occurred also in JavaScript.
Current status: looking for an alternative editor.

I tested this under VS Code 1.4 and 1.6.0-dev.20150825 doesn't work there either. None of the requests send to the tsserver return. So there is something seriously broken with that version of TS.
@DavidRigglemanININ @joebehymer in 1.5.x we added behavior that asks you whether you want to use the local TS version in our workspace instead of the bundled one. Could it be that with < 1.5.0 you always used the bundled version (which was 1.8.10) and only in your external tools used 1.6.0. This would explain why it stopped working with 1.5.x.

So somehow things seem to be working again on 1.5.3. Maybe somewhere along the line I told VS Code to use 1.8 by accident (or rather omitted one click to keep using 1.6). If there's any I can do to verify versions, let me know. I guess the above scenario you mentioned could be a possible explanation. It doesn't look like we 1.6 hardcoded in the settings.json file, just in our package.json config

This explains it then. If you don't have typescript.tsdk in the settings.json pointing to the local 1.6 TS then VS Code always used 1.8.10 for code complete, error checking, ...
@DavidRigglemanININ please be aware that VS Code 1.6 will ship with TS 2.0.3 in the box. So you might see additional errors since the compiler got more precise. If you need to go back to 1.8.10 then you can install 1.8.10 on your machine (must not be in the workspace to not conflict with 1.6 TS) and use typescript.tsdk to point to the 1.8.10 version
I will close the issue.

I'm really not sure this should be closed.  What I had was a working version of VSCode and then it does an automatic update which I didn't ask for and then is no longer working.  Should I have to go hunting down which version of typescript is running or change a setting in a config file I've never touched before?  Shouldn't there be some warning?  All I know right now is that prior versions of VSCode worked better than my current version and also standard shortcuts that I have been used to using like Command+E disappeared.

@tdekoekkoek your issue is very likely not cause by a dev version of a TSServer. Can you please open a separate issue with steps to reproduce them. Mixing problems in one issue is always very complicated since it will lead to the fact that we never can close an issue :-)

I'm not sure that the point made by @tdekoekkoek isn't valid. The symptoms are exactly the same issue I had and I agree with his point. On an upgrade, things should just work and existing behavior should not be broken. If some new prompt to select a TS version is added, and choosing one option breaks functionality, then that needs to be made much more obvious to the end user (like a warning as mentioned). Also, I'm a little unclear on where use of the dev version of TSServer comes in. Prior to my upgrade to VS Code 1.5, I was using TS 1.6.2. Did the new version of VS Code somehow bundle the dev version of 1.6 and then present it as an option to the end user? That doesn't feel right? Also, given we didn't even have the config file point to to 1.6 (typescript.tsdk was set to null), how did VSCode even know to suggest that. Does it look at the package.json file, where we do have TS 1.6.2 specified.

@tdekoekkoek complained about several things containing Command e and Command p not working. These two are not powered by TypeScript and therefore a different version of the TS compiler can hardly break them. We do take is problems serious so. That is why I ask him to file a separate issue.
Regarding your specific issue: yes we do look into the node_modules folder now to see if we can find an installed TypeScript. If this is different from the one we bundle then we show the message.
In the past we didn't which confused a lot of people. They for example install TypeScript in their workspace or even got the version to use via a generator (e.g. for example Angular) however we didn't honor that. We decided against automatically using the one out of the workspace since it might cause a different set of problems.
So prior to the upgrade you used TypeScript 1.8.10 but I guess you were assuming you used 1.6-dev-xxx. When you decided to use 1.6-dev things stopped to work since that version of the tsserver isn't functional at all (it doesn't work with 1.4.x either).
I see your point but all I can think of improving this is to make it more clear in the message which version you used before. Would it helped if we would told you that you used 1.8.10 before?
In general I think making you aware of this 'misconfiguration' is the right thing to do. And in your specific example choosing 1.8.10 would have kept you in your 'previous' state in which everything worked.


Clean filter before remove.

This PR clean the dataview's filter before removing it.

CR @alonsogarciapablo
cc @xavijam

Some tests pending.

You are right @alonsogarciapablo, sorry for missing a clearer context. Right now, if you have a widget and apply a filter on it, the map obviously reacts showing the data properly. If the user removes that widget, it's removed properly but the filter is still applied to the data. So this PR tries to fix that, clear the filter before deleting the dataview.

Thanks for the explanation @nobuti 😄 !

If the user removes that widget, it's removed properly but the filter is still applied to the data.

How is that possible? If the widget is removed, its dataview should be removed and the filter shouldn't be sent to the Maps API in the next request (this is the code where cartodb.js gets the filters that will be sent to the Maps API)...

I think the problem is in how we remove the dataview-base-model: https://github.com/CartoDB/cartodb.js/blob/v4/src/dataviews/dataview-model-base.js#L328-L341
If filter is not empty, we reload the vis before to trigger the remove event. AFAIK, the event triggered from this.filter.remove do nothing because it's not inside a collection and I can't see anything listening that event. So reloading the vis check for filters again, returning the same vis we already have.

💡 💡 💡  I think we could simplify this by just doing something here.
// src/vis/vis.js

...

_initBindsAfterFirstMapInstantiation: function () {
  ...
  this.listenTo(this._dataviewsCollection, 'remove', this._onDataviewRemoved);
},

...

_onDataviewRemoved: function (dataviewModel) {
  if (dataviewModel.isFiltered()) {
    this.reload({
      sourceId: dataviewModel.getSourceId()
    });
  }
}

Much simpler now @nobuti! Thanks!

Revamped test but now it's red because an unrelated tests, and I have no clue why, could you take a look @alonsogarciapablo?

Feel free to ignore that test @nobuti. I'll fix it in the future if we encounter it again. Thanks! 👏

Or if you want to fix it, we should change this to something Yahoo will not be able to geocode.

retest this please

retest this please

retest this please

🚀


Authentication for Timeseries Insights using Managed Service Identity

Is it possible, or will it be possible to authenticate using MSI when communicating with TSI ?
Suppose I have an Azure Function or Azure WebApp which needs to interact with Timeseries Insights, would I be able to authenticate using the System Assigned or User Assigned Identity of that Function or Web App ?

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

ID: 2f1c1d09-3921-2730-1b7b-2cc2d601bdd4
Version Independent ID: 71c02dae-2cb2-07c2-dfa4-96990fee3389
Content: API authentication and authorization - Azure Time Series Insights
Content Source: articles/time-series-insights/time-series-insights-authentication-and-authorization.md
Service: time-series-insights
GitHub Login: @deepakpalled
Microsoft Alias: shresha

@fgheysels We are checking this and we will get back to you.

Hello @shreyasharmamsft Could you please look into this question?

Hi @fgheysels,
Yes you can absolutely do that. In that case, you'd follow the Azure AD guidance on how to acquire tokens for resources as an MSI. Please see the documentation here. The resource would be https://api.timeseries.azure.com/ and one of the optional properties is required. Note that you'd also have to first grant the MSI either the reader or contributor role for your TSI environment.

Hi @lyrana
Thanks.
I just did a first quick test and this looks promising
var azureServiceTokenProvider = new AzureServiceTokenProvider();
accessToken = await azureServiceTokenProvider.GetAccessTokenAsync("https://api.timeseries.azure.com/");

gives me an access token that I can use to query TSI.
Should the documentation here be updated or extended to show how MSI authentication to TSI can be done ?

Hello @fgheysels Thanks for the feedback on this documentation. Please let us know if we are good to close this issue?

@SatishBoddu-MSFT I have an answer to my question, but I think the documentation on authenticating to TSI should be extended with a topic on how MSI authentication can be used .

Hello @fgheysels Thanks for the feedback on enhancing this document.
I have assigned the issue to the content author @shresha for further review and update the doc as appropriate.
Cc: @lyrana , @deepakpalled

Hi @SatishBoddu-MSFT  @lyrana @deepakpalled
Any news already regarding updated documentation for MSI authentication ?

Hi @SatishBoddu-MSFT  @lyrana @deepakpalled
Any news already regarding updated documentation for MSI authentication ?

There's one thing I don't quite understand here.   When authenticating to TSI using clientid/clientsecret, the app registrations needs to have the permission to query TSI by adding that permission explicitly.
When using MSI to authenticate, that is not necessary ?

That is still necessary—the MSI would need to be granted either the reader or contributor role as a one-time step, just like any other user or service principal. You can do that programmatically by making a rest call or by using Power Shell or Az CLI.

True, I also see this on my access policies list :')  Don't know what I was thinking ....   I indeed create an access policy for my API via my Azure Devops pipeline .... My mistake here.

@fgheysels no need to apologize, we always welcome hearing from you. You'll be glad to hear that updates to this doc to mention and link to MSIs (and recommend them as best practice) are in the PR review process. You won't be able to view the PR, but linking here so that I can close this open issue
https://github.com/MicrosoftDocs/azure-docs-pr/pull/148072
PRs take 1-4 days, and then the docs build and release process can be up to a day.
#please-close


Add Allex1 as an approver

Proposal to add @Allex1 as an approver for opentelemetry-helm-charts.
Alex has been a driving force for the operator chart and helps review PRs across the repo.

https://github.com/open-telemetry/opentelemetry-helm-charts/pull/297
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/289
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/285
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/278
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/276
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/268
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/266
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/265
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/258
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/256
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/255
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/253
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/251
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/249
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/245
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/244
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/240
https://github.com/open-telemetry/opentelemetry-helm-charts/pull/235

@Allex1 Let me know if I've got your information correct in the readme. Thanks again for all your help!
cc @open-telemetry/helm-approvers

@TylerHelmuth updating maintainers list requires a version bump :)

@TylerHelmuth updating maintainers list requires a version bump :)

lol!

@Allex1 you'll get an invite to  https://github.com/orgs/open-telemetry/teams/helm-approvers  shortly.  Welcome aboard!


Migrate Configurable to ExecutionException [ECR-4072]

Overview

Migrate Configurable to ExecutionException.

By now you must know which commits to review 🙃

See: https://jira.bf.local/browse/ECR-4072
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

Coverage decreased (-0.2%) to 86.145% when pulling a0debcb60fa538a96c0ed5a89340c1a46693322d on dmitry-timofeev:migrate-configurable-to-exec-exc-ECR-4072 into 0fa1979de32da5bcea112a05dc270618a44bc9ab on exonum:master.


adding support for vJunos-switch

This is a PR to add support for Juniper's vJunos-switch image that emulates an EX2914. vJunos Labs is a recent initiative that features lab images vJunos-switch and vJunosEvolved, the latter I am working out some kinks and will add this in a later PR. I used the below topology file with containerlab for testing. Once this is verified and upstream for vrnetlab I will make the PR for containerlab as well.
name: demo

topology:
  nodes:
    n1:
      kind: srl
      image: ghcr.io/nokia/srlinux
      startup-config: srl.cfg

    vswitch0:
      kind: vr-vjunosswitch
      image: vrnetlab/vr-vjunosswitch:23.2R1.14
      startup-config: vjunos.cfg

  links:
    - endpoints: ["n1:e1-1", "vswitch0:eth1"]

The existing Juniper nodes (vSRX, vMX, vQFX) feature some send/wait type logic on the Junos CLI to configure the nodes with their bare minimum configs enforced by vrnetlab (such as user, password, various set commands, etc). Instead of using this logic, I used the shipped make-config.sh shell script featured in the support.juniper.net site that creates a disk image based on a juniper.conf file (this is where the various bare minimum configs lie) and then mounts this disk to the main vJunos-switch VM image.

Hi @akielaries
thank you. I believe a matching PR should be opened against containerlab with the added kind

thanks @akielaries


Pull file upload file type specifiers from config

Description
File upload used a hard-coded accept list of file type specifiers. It was brought to my attention that a new program now live in Seattle requires applicants to submit a spreadsheet filled out from a template supplied by the program.
This change just allows setting the value from the config file.
Release notes
There is a new, optional, configuration value to control the types of files that applicants are allowed to upload on file upload questions.
The default options remain as images and PDFs. To customize set the FILE_UPLOAD_ALLOWED_FILE_TYPE_SPECIFIERS. This uses any valid file type specifiers. Multiple are separated by commas.
Checklist
General
Read the full guidelines for PRs here

[x] Added the correct label: < feature | enhancement | bug | under-development | dependencies | infrastructure | ignore-for-release | database >
[x] Assigned to a specific person, civiform/developers, or a more specific round-robin list
[x] Performed manual testing (Chrome and Firefox if it includes front-end changes)
[x] Extended the README / documentation, if necessary. For user-facing features, consider updating the user docs. For "under-the-hood" changes or things more relevant to developers, consider updating the dev wiki.

Lgtm! Just one question about if we need the defaults in multiple places. I'm also curious if/how you tested this change?

I tested it manually in these system states:

multi-file upload off and northstar off (so the current single file upload)
with multi-file upload on and northstar off
with multi-file upload on and northstar on

In search system state, I opened a program with a file upload and clicked upload to show the file upload dialog checking that the files I want were listed and that I could upload them. Then added an addition file type, refreshed the page, and did the same process to make sure I could see and upload the new type.


Allow retrieving additional columns with multiple rows

Would you be willing to accept a PR that would allow specifying additional columns to populate with retrieving multiple rows using All, ByPartitionKey, or ByCustomFilter? This module works great for me except for needing some additional columns. Rather than copying the work you've done here to work correctly across different Azure PowerShell modules, I would love to just contribute.

Looks as though this is unnecessary.


Docs 13004 asset lifecycle states bsj

Closing because I merged and squashed this into W-10786053-DOCS-13004-lc-states-verified-bsj. This was necessary because the original PR had some unverified commits.


You can only bless reagents if it's in a beaker

Description

Stuff like water should be able to be blessed whether or not its in a beaker (so it works in any container like a bucket for example).

water tank

well probably not that so its not abusable

Could also have it work on other blood types. Copper blood at least. Maybe zombie/demon?


React Spinner Can not used similary if i use mui chart, full calendar etc. i am sharing the screenshot.

import BaseLayout from '../../components/layout/BaseLayout'
import { ClockLoader } from "react-spinner";
export const Home = (): JSX.Element => {
return (

Home

  Home, sweet home 🏠.
</BaseLayout>

)
}
this is the code sample i used and now i am getting this error.

is there any way by which i can use these packages and still have the ssr.

is there any way by which i can use these packages and still have the ssr.

Yes, in your  vite.config.ts file, add this:
export default defineConfig({   plugins: [     react(),     cjsInterop({       dependencies: ['react-spinners'],     }),   ], })
And then just import the the react-spinners library normally.
Further reading:
https://vike.dev/broken-npm-package#workaround

@NileshJain82
I have created a separate branch with the solution for you here: https://github.com/hoosierhuy/vite-react-server-side-render/tree/with-react-spinner
Please give it a star if it works for you.

I tried using your project and then added the mui date picker and getting the error :- |
This is the code for the home page :-
import BaseLayout from '../../components/layout/BaseLayout'
import dayjs from 'dayjs';
import { DemoContainer, DemoItem } from '@mui/x-date-pickers/internals/demo';
import { AdapterDayjs } from '@mui/x-date-pickers/AdapterDayjs';
import { LocalizationProvider } from '@mui/x-date-pickers/LocalizationProvider';
import { DatePicker } from '@mui/x-date-pickers/DatePicker';
import { MobileDatePicker } from '@mui/x-date-pickers/MobileDatePicker';
import { DesktopDatePicker } from '@mui/x-date-pickers/DesktopDatePicker';
import { StaticDatePicker } from '@mui/x-date-pickers/StaticDatePicker';
export const Home = (): JSX.Element => {
return (

Home
Home, sweet home 🏠.

)
}
function ResponsiveDatePickers() {
return (

<DemoContainer
components={[
'DatePicker',
'MobileDatePicker',
'DesktopDatePicker',
'StaticDatePicker',
]}
>

<DesktopDatePicker defaultValue={dayjs('2022-04-17')} />

<MobileDatePicker defaultValue={dayjs('2022-04-17')} />

<DatePicker defaultValue={dayjs('2022-04-17')} />

<StaticDatePicker defaultValue={dayjs('2022-04-17')} />

);
}
and here's the vite config file.
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react-swc'
import { cjsInterop } from 'vite-plugin-cjs-interop'
// https://vitejs.dev/config/
export default defineConfig({
plugins: [
react(),
/**
* https://vike.dev/broken-npm-package#workaround
* Work around for:
* SyntaxError: [vite] Named export 'ClockLoader' not found.
* The requested module 'react-spinners' is a CommonJS module,
* which may not support all module.exports as named exports.
*/
cjsInterop({
dependencies: ['react-spinners', "@mui/x-date-pickers", "mui/x-date-pickers"],
}),
],
})
i tried both ways @mui/x-date-pickers and mui/x-date-pickers
please look into the issue

Hello buddy,
Clock loader is working fine. But while using the mui date picker in your
own repo's code i am not able to move ahead.
On Sat, 5 Oct, 2024, 7:36 am hoosierhuy, @.***> wrote:

Closed #1
https://github.com/hoosierhuy/vite-react-server-side-render/issues/1 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/hoosierhuy/vite-react-server-side-render/issues/1#event-14526500381,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4OAZH6Z6UHXO4IXR3N23R3ZZ5CTJAVCNFSM6AAAAABPCQUKMOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGUZDMNJQGAZTQMI
.
You are receiving this because you were mentioned.Message ID:
<hoosierhuy/vite-react-server-side-render/issue/1/issue_event/14526500381@
github.com>


test: Fix jest snapshot drifts

Our custom serializer returned string as-is. This confused the hell out
of jest's indentation detection algorithm and caused the drift of the
snapshots on every update we all know and love.
Default snapshot serializer wraps strings in quotes and I do the same
for this PR. This seems to fix the drift, for the price of having to
update every single inline snapshot we have.

Looks like a few more snapshot updates are necessary, due to quote symbols in snapshots

@Jolg42 this should be fixed now

ci test all


Swiping between to a new message and back leads to a different message

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.301
Where did you get the app from?
F-Droid
Android version
12
Device model
Pixel 4a
Steps to reproduce
I suppose that's connected with sorting unread messages on top (and perhaps additionally thread view?).
Opening a message, swiping right (to a message that's unread... I don't know how to set this up, but I continuously trigger that setup accidentally), swiping back left confusingly leads to a different message than you started at. This is especially bothersome if you triggered the swipe gesture only accidentally and just wanted to go back.
The path to fix this is to swipe right again, mark that message as unread and then left again.
Expected behavior
Swiping back and forth gets you back to the message you started from.
Actual behavior
See above
Logs
No response

If you enable split screen mode you can see what's going on.
Opening a message will mark it as read and update the message list to reflect this change. If your message list is sorted by read/unread, the position of the currently opened message changes in the list. Moving to the next/previous message is consistent with that new list position (but not what users would expect).
Thunderbird on desktop handles this differently. When sorting by read/unread the app will only sort the list when opening the folder. Subsequent changes to the message read state will not change the position of that message in the list. That nicely sidesteps this problem.
However, it requires keeping track of all messages. I was hoping we could use dynamic paging for the message list in the future (so not all messages will be loaded into memory, only the ones currently displayed in the list, plus some extra before and after).
What we could do is keep the old position of the currently opened message. That way the previous and next message won't change when marking the message as read on opening. However, the message would change its position in the list once you navigate away from it. So, when reading unread messages, swiping right to open the next message and then swiping left again won't open the previously displayed message.
Any other ideas on how to fix this?

I've implemented a "sort cache". Currently only the last 3 opened messages are remembered.
https://user-images.githubusercontent.com/218061/188182565-72282c30-6e21-4751-b69a-0f4f0e70ba7f.mp4
@Bubu: What do you think?


Valid json files are being declared "not json" if it doesn't have a json extension

This is probably minor but files that are valid json don't need a json extension (or if they do that should be documented).

Reclassifying this as an enhancement, as the json file extension check was intended behaviour.
I have addressed it in PR #37, so it just needs merging and publishing to npm by @himynameisdave :smile:


Feature: Support merging arrays of plain objects with no unique key

After testing this locally with our repos, I think this still needs some work


Login flow socket logic rework

Create flow as described in document:
https://docs.google.com/document/d/1xctIuJ1Wn18MX2mtWwgTzDDcdmcVCLjVkGrBmOC_ng0/edit

This has been live a while, ticket was not updated


Array assignment

WBN to extend the oso "assign" to be able to assign arrays in one instruction.  This isn't allowed in OSL at the moment, but happens implicitly if you do structure assignment and the structure contains an array.  Making it one assignment, instead of the current code generation for element-by-element copy, will make more compact oso's as well as make it very easy for the LLVM IR generation to turn it into a simple memcpy.
We could also open debate on whether we should allow assignment of arrays in the OSL source language.  (The only important counter-argument is simply that C does not allow it, and we try to minimize gratuitous differences from C unless they are significant improvements or specializations for shader programming in particular.)

The problem with C is that it treats arrays and pointers the same in terms of element access. This is why it cannot allow direct array assignment. OSL doesn’t have such an issue, but when you make a language “C-like”, this is the price you pay.
Let me suggest a separate syntax indicating explicit array assignment: how about empty brackets? E.g.
arr1[] = arr2[];


Add making quartz blocks in the aesthetics factory

Useful for large builds made of quartz, shouldn't cause any balance changes as quartz blocks can't be crafted back into quartz.

I have no problem with making Quartz easier to obtain for building in quantity, but I think that the more preferable option would be to make more quartz blocks out of raw quartz instead of unrelated blocks, as this still keeps the nether requirement for it.

That sounds fine. What are you thinking rates-wise?

Wait a minute, we should already have this recipe in the nether smelter for 3x return rate, no?

Yeah, if you use silk touch and combine the bonuses the nether quartz ore --> quartz pieces recipe and the quartz pieces --> quartz blocks recipes give then quartz blocks are roughly 6x easier to obtain than the vanilla recipe. Also quartz is insanely abundant. If you've done any large scale mining in the nether (for example for debris) then you should have a large surplus

My line of thinking was that we already have things like the sea lantern, red to normal sand, and dark prismarine recipes, adding a reasonable yield way to do something similar with another aesthetic block makes sense.
It is more of a perspective thing though, if you spend more time in the nether you'll probably have a lot of quartz. I personally don't, so I have very little.

Tbh you don't even have to spend that much time in the nether to have a ton of quartz blocks. Plus quartz is a by-product of producing netherite. There is no other way to get prismarine/dark prismarine/sea lanterns as there are no guardian temples in the game. Just as an idea of how abundant quartz is, with a day and a half of mining for debris in the nether I've mined enough quartz ore for 81 stacks of quartz blocks.

Favorable quartz smelting is available in the Nether Smelter as noted above, this is intentional to drive a portion of resource collection to the nether (as quartz is sourced from the nether), we don't want to bypass this. If you want to make an argument for adjusting the rates in the nether smelter, please open a new PR for that


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-22-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 919

Questions ?
Please refer to the Backport tool documentation


Settings UI text input cannot handle fast text input

Issue Type: Bug

Open settings preview
Find a setting that accepts text input (e.g. files.defaultLanguage)
Reset the setting to empty string
Type in the setting quickly (e.g. markdown)

Letters will be overwritten and reordered. You will get something like: mrkdoaw
VS Code version: Code - Insiders 1.24.0-insider (bfd155e6039f64d2795c6b514a029ebd01a33527, 2018-05-29T05:16:50.002Z)
OS version: Windows_NT x64 10.0.17134

Better now but https://github.com/Microsoft/vscode/issues/55803 exists


[Issue #24] Add translation draft for user-guide/secret.md

See #24.

这篇内容比较多，最好其他人也能review一下 @linfan @iT2afL0rd @resouer

@hurf  @linfan : I've made some adjustments based on your review.

Almost done, just a few minor changes needed.

@hurf : Already made some minor changes.

Well done, thanks!


Update templates with new dropdown menubar

@DrDrij @mmcky Let me know when we should merge this one in.

@arnavs I have merged this on the python side this morning.

OK, sounds great.


(german) merge

This doesn't appear to have any changes in it.

I have to admit I don‘t understand it either, I‘ll close this one and add it to my next effective changes.