how to get and set pose parameters (roll/pitch/yaw angles) in python demo.py?

I successfully built the python module. The demo.py worked fine that I can see the isomap it generated. However there is two questions:

Why is the isomap rotated CCW 90 degrees?
how can I get and set the pose parameters (RPY) in demo.py eos.fitting.fit_shape_and_pose()?

I appreciate this great project and your help!

Hi,
1.: I think this may just be a case of what library you use to display it. It may interpret the data as row-major storage when it is col-major, or vice versa. If you use cv2.imshow(...), I think it should display correctly.
2.: In demo.py they're contained in the returned pose variable (link). This is an instance of the class RenderingParameters and it has getters to get the rotation or the model-view and projection matrices. I think if on a Python console you do help(pose) or help(eos.fitting.RenderingParameters) you should get a documentation.
I'm going to close this, feel free to re-open if you discover that there is any bug or issue with the eos library or the Python bindings.


Exception with HtmlDocument.ParseDocumentAsync

Bug Report
Prerequisites

[x] Can you reproduce the problem in a MWE?
[x] Are you running the latest version of AngleSharp?
[x] Did you check the FAQs to see if that helps you?
[x] Are you reporting to the correct repository? (there are multiple AngleSharp libraries, e.g., AngleSharp.Css for CSS support)
[X] Did you perform a search in the issues?
Yes, #452 But was nothing wrong.

For more information, see the CONTRIBUTING guide.
Description
Exception when parsing a 'document'.
System.ArgumentOutOfRangeException
  HResult=0x80131502
  Message=Index must be within the bounds of the List. (Parameter 'index')
  Source=System.Private.CoreLib
  StackTrace:
   at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
   at System.Collections.Generic.List`1.Insert(Int32 index, T item)
   at AngleSharp.Html.Parser.HtmlDomBuilder.HeisenbergAlgorithm(HtmlTagToken tag)
   at AngleSharp.Html.Parser.HtmlDomBuilder.InBodyEndTag(HtmlTagToken tag)
   at AngleSharp.Html.Parser.HtmlDomBuilder.InCell(HtmlToken token)
   at AngleSharp.Html.Parser.HtmlDomBuilder.<ParseAsync>d__23.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at AngleSharp.Html.Parser.HtmlParser.<ParseAsync>d__28.MoveNext()

Steps to Reproduce
await new HtmlParser().ParseDocumentAsync(await new HttpClient().GetStringAsync("http://www.artfiles.org/netlib.org/blast/blast-nearterm"));

Expected behavior:
That it handles the input without exception.
Actual behavior:
Something internally goes wrong.
Environment details:
.NET Core 3.1 on Windows 10 Pro 2004
Possible Solution
It looks like it must be something with list management. Hopefully it's clear and quick to fix.

Yeah unfortunately the given thing is no HTML.
Have you checked out http://www.artfiles.org/netlib.org/blast/blast-nearterm ?
While this is indeed a bug (thanks for creating the issue!) I think you don't want to parse the given source as HTML.

Haha, yes, it's a load of MIME, sorry, forgot to mention.
And indeed, they only reason for creating the issue was that it should not 'crash'. It's an unintentional parse (a result of the 'directory' above it). Np and thanks.

And indeed, they only reason for creating the issue was that it should not 'crash'

Indeed - apparently it hits one of the rare edge cases (heisenberg algorithm ;D) - which is tested, but obviously not under the given conditions. So its a great case!
Thanks for issuing! Fix incoming!

Fix available in the preview and in devel.

Thanks, 'verified'! 👍


feat(storybook): add theme toggle

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Description
This PR provides a slightly improved theme toggle functionality.

It works out of the box for all stories - there is no need to wrap an individual story in some kind of provider.
Theme can be toggled from the toolbar, as opposed to selecting it from the props
The functionality is build on the top of built-in Backgrounds addon

Old

New

Full preview
https://user-images.githubusercontent.com/58401630/142761717-8dbd93c6-9e88-4227-a2b4-c09827cb712a.mov
cc: @ahmadabdolsaheb

Thank you for implementing the theme toggle from the preview. This is much better than what we have now.


[change] exercise

@exercism/clojure , added "change" exercise

Could you please rebase and force push to get rid of the merge commits?

Sure! Do you have some improvement notes on the source code?


[STM32XX] Fix timer interrupt handler

Some of the targets use only the flag and some other only the interrupt source to check which channel of the master timer has triggered an interrupt in an interrupt handler.
The flag can be set by hardware even if the interrupt is disable and two interrupt can be enable, for one triggered, in the same handler so we need a double check here.
The major issue is that some interrupt_x handler code can be execute even if the interrupt_x have been disable.

These commits make all of the st targets checking both int source and flag for the master timer.

Please merge this after these ones, I will rebase:

[x] #2077 NUCLEO_F429ZI
[x] #2039 NUCLEO_F446ZE

Is this ready to be merged? Both PR referenced here were integrated

Rebase done and ready to merge.

@mbed-bot: TEST
HOST_OSES=windows
BUILD_TOOLCHAINS=ARM,GCC_ARM,IAR
TARGETS=ALL

I am getting stuck in while(1) loop in RTC_Alarm_IRQHandler while using Ethernet on STM32F746G Discovery board. Could it be related?

The fix concern only the timer irq. To me, it can't be related.

manually merged


PythonDocstrings.i regenerated to update docs

Updated ITK documentation and an updated doxy2swig.py script
were used to regenerated the PythonDocstrings.i file.

Great! Thank you.


refacroring(project): merge activity,client, and workflow plugins

Reason for This PR

architectural decision.

Description of Changes

Merge plugins.

License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the MIT license.
PR Checklist
[Author TODO: Meet these criteria.]
[Reviewer TODO: Verify that these criteria are met. Request changes if not]

[ ] All commits in this PR are signed (git commit -s).
[ ] The reason for this PR is clearly provided (issue no. or explanation).
[ ] The description of changes is clear and encompassing.
[ ] Any required documentation changes (code and docs) are included in this PR.
[ ] Any user-facing changes are mentioned in CHANGELOG.md.
[ ] All added/changed functionality is tested.

Codecov Report

Merging #136 (a235140) into master (85b555b) will decrease coverage by 1.50%.
The diff coverage is 68.53%.

@@            Coverage Diff             @@
##           master     #136      +/-   ##
==========================================
- Coverage   65.58%   64.07%   -1.51%
==========================================
  Files          18       13       -5
  Lines        1043      810     -233
==========================================
- Hits          684      519     -165
+ Misses        266      230      -36
+ Partials       93       61      -32

Impacted Files
Coverage Δ

config.go
63.63% <ø> (ø)

metrics.go
66.66% <ø> (ø)

internal/data_converter/converter.go
52.63% <50.00%> (ø)

internal/codec/proto/proto.go
50.78% <50.78%> (ø)

rpc.go
32.00% <66.66%> (ø)

plugin.go
68.75% <68.75%> (ø)

activity/activity.go
69.33% <69.33%> (ø)

workflow/workflow.go
72.00% <72.00%> (ø)

workflow/handler.go
75.30% <75.30%> (ø)

internal/protocol.go
46.66% <100.00%> (ø)

... and 5 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 85b555b...a235140. Read the comment docs.


[BEAM-11165] Async ZetaSQL Calc

Use futures to defer results within the context of a bundle. Nexmark benchmarks take 1.2x-3.1x as long without this change.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @robinyqiu
I've tested this internally, it passes.

R: @robinyqiu
I've tested this internally, it passes.

R: @kennknowles Tell me if what I'm doing here that is unsafe.

R: @kennknowles Tell me if what I'm doing here that is unsafe.


Autocompletion list is too low height when only one result

Autocompletion list is too low height when only one result.

Fixed in version 0.7.0


cannot execute binary file: Exec format error

Hi,
When running
 export GORKVERSION=$(wget -q -O - https://api.github.com/repos/owulveryck/goMarkableStream/releases/latest | grep tag_name | awk -F\" '{print $4}') wget -q -O - https://github.com/owulveryck/goMarkableStream/releases/download/$GORKVERSION/goMarkableStream_${GORKVERSION//v}_linux_arm.tar.gz | tar xzvf - -O goMarkableStream_${GORKVERSION//v}_linux_arm/goMarkableStream > goMarkableStream chmod +x goMarkableStream ./goMarkableStream
I get the following error: cannot execute binary file: Exec format error.
Any idea of what's wrong ? I'm on Arch linux x64.

Hello,
Those commands are supposed to be
run directly on the remarkable.
You gain access via ssh.

Run in your archlinux
scp ./goMarkableStream root@<IP_ADDRESS>:/home/root/

to copy the downloaded executable into your remarkable, then log into it
ssh<EMAIL_ADDRESS>
and inside the newly appeared prompt run ./goMarkableStream.


Network packet schema

Hi,
there are some tools offering a JSON or otherwise parsed representation of network packet data (tshark for example). is there any appetite to come up with a standard schema for network packets in OCSF?
I can see it being very useful to store TLS handshake information, RDP sessions and other high-value connection information (just like DNS which is available in OCSF today)

Interesting idea - given packet data could be quite varied, do you have any thoughts on what an packet object might entail?

Thanks for the reply. I manage gopaacket, and in there there are quite a few layer 7 connections that are getting parsed. SIP, TLS, SSH, etc. that we can take a look at for start.
OCSF already has "network connection" metadata as a field so I don't see the point of adding lower level packet info beyond that. I'm mostly interested in adding the higher level protocols such as TLS Handshake, SSH client/server connections etc.

if there is interest in this, @awick's Arkime can be used as a good starting point


UI: Modify MP Qualification Add/Edit Pop Out

Expected Behavior:
Given a user navigates to the MP qualifications sections
When a user selects a qualification type code from the drop-down
Then the record creation should only be able to exist under the corresponding table

[ ] User should not see all Qualification tables in pop-out after a type code has been selected. The type code drop-down select should drive which qualification can be created

Restrict the Qualification Type Code dropdown to Qual Types that have a group of PCT, LEE, LME, or CPMS only.
Qualifications should be restricted to PCT, LEE, LME, & CPMS based on the Qualification Type Code dropdown.
Group to Qual Type Mapping

LEE = LEE
CPMS = CPMS
PCT = PK,SK,GF
LME = LMEA, LMES

If the Qualification Type is LEE then LEE quals are the only records that can be created/edited
If the Qualification Type is CPMS then CPMS quals are the only records that can be created/edited
If the Qualification Type is LMEA or LMES then LME quals are the only records that can be created/edited
If the Qualification Type is PK, SK, or GF then PCT quals are the only records that can be created/edited
NOTE: Once the qualification record is created the qual type cannot be changed. You can edit other data but cannot change the qual type

@mosesdeeCVP

Qualification LEE
Private Zenhub Image

Qualification LMEA
Private Zenhub Image
Qualification LMES
Private Zenhub Image

Qualification Percent - PK
Private Zenhub Image
Qualification Percent - SK
Private Zenhub Image
Qualification Percent - GF
Private Zenhub Image

MP Qual Dropdown?
Private Zenhub Image

Work has been completed


Null check for sequences comparison

[x] Have you signed the Contributor License Agreement?
[x] Are you working against an Issue?

Resolves #429

The exception is thrown at https://github.com/microsoft/winget-create/blob/44a102acd07793d89be2c1bf5e135d04ae17488c/src/WingetCreateCore/Common/GitHub.cs#L155
then
https://github.com/microsoft/winget-create/blob/44a102acd07793d89be2c1bf5e135d04ae17488c/src/WingetCreateCore/Common/Serialization.cs#L100
The installer manifest contains dependencies object with some null List sequences (WindowsFeatures, WindowsLibraries, ExternalDependencies). The Equals() method for Dependencies seems to be used externally while serializing the manifest and because null values are not handled properly, an exception is thrown.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-create/pull/432&drop=dogfoodAlpha

/azp run

/azp run


Build succeeds but file is unusable on alpine/docker

Hi, thank you for making this! I'm trying to essentially make a runner that builds the app from source and outputs it. Sadly, the output is not usable as of now:
Error
"Exception in thread "main" java.lang.NullPointerException: Cannot invoke "org.slf4j.Logger.error(String, java.lang.Throwable)" because "org.mustangproject.commandline.Main.LOGGER" is null
        at org.mustangproject.commandline.Main.main(Main.java:442)"

and
no main manifest attribute, in original-Mustang-CLI-3.0.0-SNAPSHOT.jar

Expected behavior
The app runs normally
Steps to reproduce

sudo docker run --rm -it alpine
apk add openjdk21 maven git --no-cache &&
git clone https://github.com/ZUGFeRD/mustangproject.git &&
cd mustangproject &&
mvn clean install
cd Mustang-CLI/target
java -jar Mustang-CLI-3.0.0-SNAPSHOT.jar
see error "Exception in thread "main" java.lang.NullPointerException: Cannot invoke "org.slf4j.Logger.error(String, java.lang.Throwable)" because "org.mustangproject.commandline.Main.LOGGER" is null
at org.mustangproject.commandline.Main.main(Main.java:442)"
java -jar original-Mustang-CLI-3.0.0-SNAPSHOT.jar
see error "no main manifest attribute, in original-Mustang-CLI-3.0.0-SNAPSHOT.jar"

thanks I just fixed that. However, the master is not yet stable, maybe you rever to the branch of a release version?


Migrate useful code from mothAI repository

Migrate useful code from the mothAI repository.

@adityajain07 I updated the title for this ticket. I think this is what you mean!


Kill or restart?

Sorry if this is obvious, but does this kill and not start the worker back up, or will it do a restart. Thanks

Hi @randy-girard
It doesn't restart, you may have to do it manually or have a monitor tool like upstart or monit to restart Sidekiq automatically.

@randy-girard if you are using Heroku, restarts are automated as well :)
I don't think we could handle a restart since the process is kind of killing itself: we are generating a child thread from sidekiq process, and it is this thread that sends SIGTERM, and then dies as well...

Thanks yall.


[ISSUE #4357]Support register AsyncPutMessageExecutorService

What is the purpose of the change
fix #4357
CompletableFuture thenAccept or thenApply will execute in the complete thread.
in dledger mode. this thread is QuorumAckChecker which response for process raft message commit.
the code for put message callback should not execute in the QuorumAckChecker thread. use putMessageFutureExecutor instead.
Brief changelog
Support register AsyncPutMessageExecutorService
Verifying this change
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Nice try, have you done a performance comparison?

Codecov Report

Merging #4356 (1176226) into develop (82a48be) will decrease coverage by 0.20%.
The diff coverage is 63.15%.

@@              Coverage Diff              @@
##             develop    #4356      +/-   ##
=============================================
- Coverage      48.18%   47.98%   -0.21%
+ Complexity      5082     5055      -27
=============================================
  Files            642      642
  Lines          42770    42792      +22
  Branches        5597     5599       +2
=============================================
- Hits           20609    20534      -75
- Misses         19655    19747      +92
- Partials        2506     2511       +5

Impacted Files
Coverage Δ

...n/java/org/apache/rocketmq/store/MessageStore.java
0.00% <0.00%> (ø)

...org/apache/rocketmq/store/DefaultMessageStore.java
55.34% <50.00%> (-0.23%)
:arrow_down:

...a/org/apache/rocketmq/broker/BrokerController.java
46.90% <100.00%> (+0.27%)
:arrow_up:

...ocketmq/broker/processor/SendMessageProcessor.java
40.10% <100.00%> (+0.30%)
:arrow_up:

...org/apache/rocketmq/common/stats/StatsItemSet.java
41.79% <0.00%> (-8.96%)
:arrow_down:

...org/apache/rocketmq/store/ha/WaitNotifyObject.java
66.07% <0.00%> (-5.36%)
:arrow_down:

...e/rocketmq/client/impl/consumer/RebalanceImpl.java
40.23% <0.00%> (-4.30%)
:arrow_down:

...ketmq/common/protocol/body/ConsumerConnection.java
95.83% <0.00%> (-4.17%)
:arrow_down:

...nt/impl/consumer/ConsumeMessageOrderlyService.java
46.83% <0.00%> (-3.53%)
:arrow_down:

...lient/impl/consumer/DefaultMQPushConsumerImpl.java
40.84% <0.00%> (-3.00%)
:arrow_down:

... and 24 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 82a48be...1176226. Read the comment docs.

Coverage decreased (-0.1%) to 52.028% when pulling<PHONE_NUMBER>d307f60e53f28a562ca991f97b8daa on WJL3333:fix_use_dledger_quorum_ack_checker_to_execute_put_callback_logic into 82a48be00a6d9def14abb871a40cb68cf8a041e9 on apache:develop.

Coverage decreased (-0.1%) to 52.028% when pulling<PHONE_NUMBER>d307f60e53f28a562ca991f97b8daa on WJL3333:fix_use_dledger_quorum_ack_checker_to_execute_put_callback_logic into 82a48be00a6d9def14abb871a40cb68cf8a041e9 on apache:develop.

@RongtongJin @Cczzzz can you take a look ?

Nice try, have you done a performance comparison?

not yet. just from the code anlysis, hope community will help. : - )


Accents Problem

Hello
it seems that Lapce does not show accents in my language (Greek).
Thank you
Lapce Version: 0.2.5
System information: Void Linux (Latest Linux Kernel)

Same here (portuguese brazil)
Lapce Version: 0.2.8
System information: Ubuntu 23.10


Implement Donations tests

Resolves a part of https://github.com/LiveChurchSolutions/ChumsApp/issues/13

Lets fix this one https://github.com/LiveChurchSolutions/ChumsApp/issues/33 and then merge this PR


Make vue available to other libraries without having to import it

Title needs work, idk what to call this.
What problem does this feature solve?
Writing a component library with typescript requires importing Vue so you can use Vue.extend(...) to get typings. This causes problems when webpack decides to load a different instance of vue.
See https://github.com/vuetifyjs/vuetify/issues/4068
What does the proposed API look like?
Local registration to accept a function that synchronously returns a component, calling it with the parent vue instance.
The library can then do:
export default function MyComponent (Vue: VueConstructor) {
  return Vue.extend({ ... })
}

And be used like:
import MyComponent from 'some-library'

export default {
  components: { MyComponent }
}

Of course that would then cause other problems, particularly where we use methods directly from other components. Maybe something that adds types like Vue.extend() but doesn't have any runtime behaviour would be better instead?
// When used, this will behave the same as a bare options object, instead of being an entire vue instance
export default Vue.component({
  ...
})

You may want to use https://github.com/ktsn/babel-plugin-remove-vue-extend

👌
How does that handle stuff like mixins (usage) or directly calling methods?

The plugin doesn't work on everything, it seems to assume that all exports are Vue.extend()

I'm fine with having to use Vue.extend, it's just not ideal that it creates a standalone instance. It would be nice if vue still resolved component references and everything else the same way as with bare options objects. It isn't really a problem anyway unless one of our users messes up and somehow ends up with two different vue imports.

Alternatively we may try to detect duplicate Vue imports.

Yeah that would be helpful, the current errors don't really indicate what's actually going on very well. Is our current setup likely to be a problem with vue-test-utils and createLocalVue though? vuejs/vue-test-utils#532 seems similar to this one.

A few months ago I have asked for help with an issue related to this one on stackoverflow.
I've been unhappily living with my temporary solution since then (passing the Vue instance to the library initializer, and not importing Vue in the library), but I'm not very happy about it and now I'm stuck because Vuetify, also started to typescript and creates a separate Vue instance and it's not clear how to tell to webpack (or to Vue) that it's always the same instance that has to be used.
The solution provided at the top of this thread does not help me much, since I'm not using babel.
Are you aware of an existing solution to have a package and dependencies, all written in typescript and compiled with webpack, to share the same Vue instance?

The solution should also allow to use .vue files in packages, which, with the original proposal at the top of this thread would probably not be possible.

After giving a hard look at the problem, the only solution that I found at the moment (with webpack) is to add vue as an external import wherever you import it.
In webpack.config.js
externals: {
    vue: 'Vue'
},

and then import vue.js with a script tag (or an equivalent solution) in your html file.
This avoids that vue is instantiated more than once. Depending on your package and subpackage structure, you probably need to import your subpackages and or vuetify also as external modules.
That means that you have to pack them as standalone libraries, with, in webpack.config.js
    output: {
        path: 'path/to/your/output',
        filename: 'build.js',
        library: 'LibraryName',
    },

and in tsconfig.json
"compilerOptions": {
    ...
    "module": "es2015"
    ...
}

As a side effect with this solution you can also work with vue files in your libraries. The proposed solution at the top of this issue would in any case not allow that, because you cannot inject the vue constructor in a vue file (as far as I understand).
If you are working with tests suites like karma and phantomjs you need to inject vue and the other external libraries there as well.
This is now a workaround and a better solution would be if vue would have at initialization an option to detect if there is another VueConstructor outside the actual bundle and use it (as an option, because that may or may not be desired).

I use this to make sure the same file is always loaded, you can omit the path.resolve if there's no symlinks or other weird directory setup being used.
resolve: {
  alias: {
    'vue$': path.resolve(__dirname, '../node_modules/vue/dist/vue.runtime.esm.js')
    // 'vue$': 'vue/dist/vue.runtime.esm.js'
  }
}

I had this problem in a monorepo project using Lerna, and it seems to be related to using npm link or yarn link. My project has a shared component package that multiple apps import, including an Electron app and a browser extension. It seems that lerna bootstrap uses symlinks, which ultimately leads to some bundle confusion, in which Vue is separately imported for the main repo and the dependency, which causes the '$listeners and $attrs are readonly' errors.
The general solution seems to be to mark your dependency as an 'external' in whatever build configuration you're using.
I'm using Electron with electron-builder and @vue/cli. I solved this problem by adding this to my vue.config.js:
module.exports = {
  pluginOptions: {
    electronBuilder: {
      // List native deps here if they don't work
      externals: ['my-shared-components'],
    }
  }
}


Fix visitorsviewloading + simple access managment

When you pasted a uri for the post-view while the page already was loaded (thus after the initialPageLoad action was created and dispatched) the need wouldn't get loaded. The assumption before was that pasting and entering always triggers a page-reload. However when the base-url matches, the browser only "jumps" to the new fragment-identifier, without reloading and thus without triggering initialPageLoad.
This patch adds a listener to route-changes and causes the post to be loaded if the user would run into an unitialized post-view.
This branch also include simple access managment.
Check the following behaviours:

once logged in and once logged out do:

reload on posts-overview
while on some other view (e.g. landing-page): paste link to posts-overview
reload on post-detail view
while on some other view (e.g. landing-page):paste link to post-detail view

log-out on posts-overview
log-out on posts-view (probably still redirects incorrectly)

you should always have data in those views and when you try accessing the overview while logged out you should land on the last page you were on or the landing page if this is the first in the app you accessed.

if you sign up from the landingpage without ever been signed in (with any other user) the routing will not be changed (there is a reroute loop)
See follow Log-Snippet:
Not sure about login-status -- will reinitialize route-change once it's been clarified.
configRouting.js:193 Tried to access view that won't workwithout logging in. Blocking route-change. Error: transition prevented(…)(anonymous function) @ configRouting.js:193
configRedux.js:10 action:   Object {type: "@@reduxUiRouter/$stateChangeStart", payload: Object}
configRedux.js:11 changing state from  Object {config: Object, router: Object, user: Object, messages: Object, lastUpdateTime:<PHONE_NUMBER>774…}
configRedux.js:15 changed state to  Object {config: Object, router: Object, user: Object, messages: Object, lastUpdateTime:<PHONE_NUMBER>780…}
configRouting.js:180 Not sure about login-status -- will reinitialize route-change once it's been clarified.
configRouting.js:193 Tried to access view that won't workwithout logging in. Blocking route-change. Error: transition prevented(…)(anonymous function) @ configRouting.js:193
configRedux.js:10 action:   Object {type: "@@reduxUiRouter/$stateChangeStart", payload: Object}

*Fixed* :)
(see detailed commit-msg)


mill 0.11.2 does not resolve the javax.media maven organization properly.

Reproduction steps:

Create a project with a dependency on https://mvnrepository.com/artifact/org.geotools/gt-main
Attempt to compile the project.

In mill 0.11.1, the project compiles properly.
In mill 0.11.2, the project fails with an unresolved dependency:
___.resolvedIvyDeps Failed to load dependencies
  not found: https://repo1.maven.org/maven2/javax/media/jai_core/1.1.3/jai_core-1.1.3.jar

The correct URL should be javax.media, not javax/media

The URL to jar_core is correct. The URL exists: https://repo1.maven.org/maven2/javax/media/jai_core/1.1.3/ but there is no binary jar, only a pom and a javadoc jar. This is not a issue in Mill but with Maven central repo1. The pom states <packaging>jar</packaging> but there is no jar file.
In Maven repositories, dots in organization names are replaces by path separators. This is a difference to Ivy repositories.

It's possible it's a different issue.  I can confirm that the symptom is there: The project compiles correctly under mill 0.11.1, but not under .2

There is probably a related issue in coursier: https://github.com/coursier/coursier/issues/2377

https://github.com/okennedy/mill_jai_repro
 okennedy  athena  ~  Desktop  JaiTest  main  $  mill version
[1/1] version
0.11.1
 okennedy  athena  ~  Desktop  JaiTest  main  $  rm out
rm: cannot remove 'out': Is a directory
 okennedy  athena  ~  Desktop  JaiTest  main  $  rm -r out
 okennedy  athena  ~  Desktop  JaiTest  main  $  mill version
[build.sc] [41/49] compile
[info] compiling 1 Scala source to /home/okennedy/Desktop/JaiTest/out/mill-build/compile.dest/classes ...
[info] done compiling
[1/1] version
0.11.1
 okennedy  athena  ~  Desktop  JaiTest  main  $  mill jaitest.compile
[33/33] jaitest.compile
 okennedy  athena  ~  Desktop  JaiTest  main  $  coursier uninstall mill
Uninstalled mill
 okennedy  athena  ~  Desktop  JaiTest  main  $  coursier install mill:0.11.2
https://repo1.maven.org/maven2/io/get-coursier/apps/maven-metadata.xml
  No new update since 2023-08-16 10:52:10
Wrote mill
 okennedy  athena  ~  Desktop  JaiTest  main  $  mill jaitest.compile
[build.sc] [43/52] compile
[info] compiling 1 Scala source to /home/okennedy/Desktop/JaiTest/out/mill-build/compile.dest/classes ...
[info] done compiling
[22/33] jaitest.resolvedIvyDeps
1 targets failed
jaitest.resolvedIvyDeps Failed to load dependencies
  not found: https://repo1.maven.org/maven2/javax/media/jai_core/1.1.3/jai_core-1.1.3.jar

@okennedy You could try to remove the relevant path in your coursier cache and re-try.

No effect:
 okennedy  athena  ~  Desktop  mill_jai_repro  main  $  coursier uninstall mill
Uninstalled mill
 okennedy  athena  ~  Desktop  mill_jai_repro  main  $  coursier install mill:0.11.2
https://repo1.maven.org/maven2/io/get-coursier/apps/maven-metadata.xml
  No new update since 2023-08-16 10:52:10
Wrote mill
 okennedy  athena  ~  Desktop  mill_jai_repro  main  $  rm -rf ~/.cache/coursier/v1/https/repo1.maven.org/maven2/javax
 okennedy  athena  ~  Desktop  mill_jai_repro  main  $  mill jaitest.compile
[build.sc] [43/52] compile
[info] compiling 1 Scala source to /home/okennedy/Desktop/mill_jai_repro/out/mill-build/compile.dest/classes ...
[info] done compiling
[22/33] jaitest.resolvedIvyDeps | Downloading [3/3] artifacts (~35607/35607 bytes)
1 targets failed
jaitest.resolvedIvyDeps Failed to load dependencies
  not found: https://repo1.maven.org/maven2/javax/media/jai_core/1.1.3/jai_core-1.1.3.jar
 okennedy  athena  ~  Desktop  mill_jai_repro  main  $  coursier uninstall mill
Uninstalled mill
 okennedy  athena  ~  Desktop  mill_jai_repro  main  $  coursier install mill:0.11.1
https://repo1.maven.org/maven2/io/get-coursier/apps/maven-metadata.xml
  No new update since 2023-08-16 10:52:10
https://repo1.maven.org/maven2/javax/enterprise/cdi-api/1.0/cdi-api-1.0.pom
  100.0% [##########] 1.4 KiB (46.7 KiB / s)
Wrote mill
 okennedy  athena  ~  Desktop  mill_jai_repro  main  $  rm -rf ~/.cache/coursier/v1/https/repo1.maven.org/maven2/javax
 okennedy  athena  ~  Desktop  mill_jai_repro  main  $  mill jaitest.compile
[build.sc] [41/49] compile
[info] compiling 1 Scala source to /home/okennedy/Desktop/mill_jai_repro/out/mill-build/compile.dest/classes ...
[info] done compiling
[33/33] jaitest.compile
 okennedy  athena  ~  Desktop  mill_jai_repro  main  $ 


Add raids items overlay WIP

Overview
The raids items overlay assists raiders by displaying the items required to complete the raid.
Current State
The interface is populated based on the rooms that are scouted. Each room that requires has an item type (ex: "Pickaxe" for Guardians or "Antipoison" for Lizardman Shamans) and a list of items that fulfill the requirement (ex: any pickaxe bronze-rune for Guardians). If the player has the item, the first matching item found in their inventory will display on the interface in green. If the player does not have the item, the item "type" will show in the interface in red.

Future State
Future releases will add recommended items and potentially a list of custom items that the player can enter in a text field. This will allow a more robust and customized user experience based on the player's preferred loadout.

I recall that it is possible to do a highlight stroke around the relevant inventory item.
However, I also recall that it is very hard to highlight such.
Maybe something to look into?


Transparency bug on Path of Building App

Hello, I'm experiencing an issue where the context menus, background and everything on the path-of-building-community app is transparent, and so my background makes it nearly impossible to read it in a good way.

I'm on Gentoo and the ebuild for this app was created by me, I tested in a vm and it works normally on dwm, tested on real hardware and it works as intended on Gnome Wayland too.
I'm using both Hyprland and hyprpaper 9999 (git version).
hyprctl clients spits out:
Window f1312d20 -> Unnamed build (Scion) - Path of Building:
	at: 7,28
	size: 1906,1045
	workspace: 3 (3)
	floating: 0
	monitor: 1
	class: pobfrontend
	title: Unnamed build (Scion) - Path of Building
	pid: 4237
	xwayland: 0
	pinned: 0
	fullscreen: 0
	fullscreenmode: 0
	grouped: 0
	swallowing: 0

The package is also available on the AUR and also as flatpak community.pathofbuilding.PathOfBuilding, though I'm not the maintainer of neither of those.
Any more info needed I'm glad to help!

do you have blur_xray on by any chance?

I don't. It should default to false too, according to wiki.
I do have ```
windowrule = noblur, pobfrontend
windowrule = noshadow, pobfrontend
windowrule = noanim, pobfrontend
on my config though. I enabled those because i thought it would fix it.

To note, it happens when floating and when tiled.

its that one bug then. blame xwayland.

what bug? are you sure it's running on xwayland? it says 0

wait, it's not xwayland?  Ugh.

for reference, these are the links that constitute the main part of the package.
https://github.com/PathOfBuildingCommunity/PathOfBuilding
https://gitlab.com/bcareil/pobfrontend#branch=luajit
Is it fixable?

Is it fixable?

Yes, but annoying

actually, can you tell me whether this happens on sway?

It doesn't happen on sway 1.7. Works as intended.

not sure if it's related, but, obs has some transparency bugs as well

you can use the forcergbx windowrule tho to fix this, no?

actually, i'm not really sure how, but obs transparency bugs are gone, maybe an update to hyprland fixed it, or something else. I don't really use Path of Building anymore so I'll close this one out. Also thanks for pointing out that rule, didn't know about it.


Pass data to component from route

It would be nice if it was possible to pass arbitrary data to a component via a data object.
this.$router.go({name: '/signout', data: {message: 'Token expired'}});

Which would then be available to the component in the usual format.

I'm in general against this type of ad-hoc data passing - it's better to manage the state explicitly somewhere (e.g. in a store)

I would like to reopen this feature-request,
I am making a CSS Documentation, the documents should share the same components,
cause documents all look the same, but I cannot pass data from vue-router to component,
so what I can only do is like this:

but If I can pass the data from router to components,
I can use it like the following paths without creating new components with the same contents but just require different datas.

@YamiOdymel Why not store the data into the meta key?

PAssing this kind of data defeats the purpose of a router: The URL should determine the state of the application.
If you pass this data in the route object, your application will error out (or behave differently) when you enter /element/container directly (so the data in the route is missing), versus when you navigate there from another view which has set the data in the route.
So this should be avoided.
{
path: '/elements/:elementType',
component: require(../views/Doc)
}

use the param to render the correct component..
<template>
  <component :is="$route.prarams.elementType"></component>
</template>

...or get the correct items (noe example I have no´idea about your data setup).

Hi guys,
I have similar question,
Is it possible to pass additional 'static' params to component?, for example I have routes:
{ name: 'news',  path: '/news/:id?', component: require('./page')},
{ name: 'articles',  path: '/articles/:id?', component: require('./page')},
{ name: 'other',  path: '/:othertype/:id?', component: require('./other')}

and as result I have to pass (somehow) page type (news or articles) to 'page' component
I thought it could be solved as (due to order priority)
{ name: 'page',  path: '/:pagetype/:id?', component: require('./page')},
{ name: 'other',  path: '/:othertype/:id?', component: require('./other')}

but as result 'page' component will catch all required routes
Is it possible?
{ name: 'news',  path: '/news/:id?', params: {type:'news'}, component: require('./page')}

or something like
{ name: 'news',  path: '/:type(article|news)/:id?', component: require('./page')},
{ name: 'other',  path: '/:othertype/:id?', component: require('./other')}

If I understood well, you can use the new props feature: https://github.com/vuejs/vue-router/blob/dev/docs/en/essentials/passing-props.md
Next time, please, ask questions in the forums 🙂

Please refer to the documentation about meta data in route definitions.

@posva, @LinusBorg  Thanks a lot!
both 'meta' and 'props' can solve my problem,
but passing 'props' is exactly for my case )
I will use forums next time  :slightly_smiling_face:

I believe there should be a mechanism which allows you to pass data into a route. It's up to you to implement the fallback if the route was navigated to directly.
Consider a list of users, /users. Now you open a single user profile, /users/:id. Since you were on the page /users, you already have the data needed for the page /users/:id. As you cannot pass data to a route you're navigating to, now you have to do the API call again, even though the data is actually in the memory.
If we could send data through the router (basically what meta is now, just not configuration-time, but dynamic during run-time), we could ask if that data is defined and use it. If it's not, we do the API call (that's the case when a user navigates directly to /users/:id by typing that in the browser).
OP's usecase is also not uncommon. There is a page, it exists on its own, but based on where you're coming from it can look a little bit different than coming straight to the URL.

Consider a list of users, /users. Now you open a single user profile, /users/:id. Since you were on the page /users, you already have the data needed for the page /users/:id. As you cannot pass data to a route you're navigating to, now you have to do the API call again, even though the data is actually in the memory.

that's what state management solutions like vuex are for. This does not fall into the domain and responsibility of the router.

Hmm. I'm not sure why routes are treated that differently than child components.
Child routes are almost like a chain of v-else-if in order to determine which component will be shown based on a string. You can pass data into children components. Why not pass data into children routes? Data still flows downwards.
I understand that Vuex is the solution if the application has a lot of shared state. But I'm not sure that implementing whole application in Vuex style because of this use-case is justified, either.
Angular solves this with services which can be injected into multiple components and thus share data, even they are not on the same route. Is there really no way to share data between two unrelated components without going full Vuex? Would $emit work at least? If I $emit data from source route, and subscribe in the destination route on its component's creation, is the order of execution guaranteeed and will it "catch" sent data?

Hmm. I'm not sure why routes are treated that differently than child components.

They are not. You can pass props to child router-views, so you can pass data down if you are so inclined.
However having the ability of passing data from any location in the component tree to some (possibly very distant) route component (which I understand is what you're asking for) is not following the data-down approach - it's what this approach wants to get rid of.
You obviously have shared state, so don't send it from one component to the other, keep it in one place.

Is there really no way to share data between two unrelated components without going full Vuex?

Have a look at my previous post, maybe my quick edit of the last paragraph wasn't quick enough and you missed it, already reading the previous, unedited version. Also, feel free to have a look at our awesome-vue repo - vuex is not the only state management solution, there are other ones out there, and not all are as "verbose" as vuex.,

Hi guys,
I'm new to vue js. i want to know about how to pass the service router-link <router-link :to></router-link> <router-link v-bind:to="'/newsDisplay/' + i.id"></router-link>.  i have the news list. when i click the news list item calling newsDisplay page through list ID.  i want to call service in router-link. ``

Please use forum.vuejs.org for questions.


Future methods getNow() and cause() now throw on incomplete futures

Motivation:
Since most futures in Netty are of the Void type, methods like getNow() and cause() cannot distinguish if the future has finished or not.
This can cause data race bugs which, in the case of Void futures, can be silent.
Modification:
The methods getNow() and cause() now throw an IllegalStateException if the future has not yet completed.
Most use of these methods are inside listeners, and so are not impacted.
One place in AbstractBootstrap was doing a racy read and has been adjusted.
Result:
Data race bugs around getNow() and cause() are no longer silent.
This PR is based on #11575

@chrisvest I only reviewed the last commit... This makes a lot of sense to me as discussed offline!

This makes sense to me.

huge +1 as discussed offline!

Converted to draft until #11575 is merged.

Rebased

Hopefully the build goes green now.

Makes sense. The old API was easier to make a mistake for sure. :+1:


BUGFIX: return correct error codes and add tests

In https://github.com/cert-manager/cmctl/pull/33, a bug was introduced in the exit code calculation.
This PR fixes that bug and adds tests that check the error code.

/approve

For anyone wondering, here is the context:
This bug was revealed while publishing cmctl to Homebrew: a test assertion was changed from 1 to 129, which led to led to a discussion in person (see the assertion change here).
If you install 2.0.0, you will see that cmctl unexpectedly returns the exit code 129 instead of 1 for most errors. For example:
$ cmctl status certificate --kubeconfig=nonexistant; echo $?
error: stat nonexistant: no such file or directory
129
$ cmctl check api; echo $?
error: error finding the scope of the object: failed to get restmapping: failed to get server groups: Get "https://<IP_ADDRESS>:58484/api": dial tcp <IP_ADDRESS>:58484: connect: connection refused
129

Before 2.0.0, cmctl used to return 1 on normal errors, and would exit 128 + signal number when cmctl was terminated mid-flight due to a signal.
I don't think this bug will have affected anyone. The only case where checking whether the exit code is 1 or 130 (due to a SIGINT caused by ctrl+C) or 143 (SIGTERM) would make sense would be when cmctl is run for a long time, which is only true for cmctl check api.
/lgtm


chore(npm): clean-up scripts

Coverage remained the same at 100.0% when pulling 13acfae2f143c24b4b0f8b77bc8beb5e81625e28 on chore-clean-up-package-json-scripts into 7466c451d953fcac395b27b761133c0e18bc10cd on main.

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


feat/ini reward system

perf: ini staking rewards and curation based on graph
chore: update
perf: ini proxy mock
perf: ini upgradeable storages
chore: update

Codecov Report

Merging #115 (8c44e33) into main (38eb8a6) will increase coverage by 16.90%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##            main     #115       +/-   ##
==========================================
+ Coverage   1.61%   18.51%   +16.90%
==========================================
  Files        570       40      -530
  Lines       4526      351     -4175
  Branches     876       45      -831
==========================================
- Hits          73       65        -8
+ Misses      4297      277     -4020
+ Partials     156        9      -147

Impacted Files
Coverage Δ

apps/app/src/atoms/assetTransition.ts

...ps/app/src/components/ProfileBoardSection/index.ts

apps/app/src/components/ToastError/ToastError.tsx

apps/app/src/components/Web3Provider/index.ts

apps/app/src/hooks/useEnsAddress/useEnsAddress.ts

apps/app/src/hooks/usePoapActions/index.ts

...app/src/components/BannerProfile/BannerProfile.tsx

...s/app/src/components/ProfileBoardItemPoap/index.ts

apps/app/src/components/HeaderPillConnect/index.ts

...onents/FollowListFollowing/FollowListFollowing.tsx

... and 520 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Substantially overhaul metrics.

This is in service of https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1504839 (combining telemetry from Node world and C++ world)
Functional changes:

The UserConfig file will be created when flushing metrics to disk for submission rather than early in process start up.
Help text for the no longer existent feature flag --enable-manifests is no longer present.
If we ever printed CTime using the formatting infrastructure, we no longer add a needless .0.

Notable non-functional changes:

LockGuarded is gone.
Locking and unlocking associated with metrics is now confined to metrics.cpp.
The quasi-global-but-not state of struct Metrics is no more. All global state is confined to one Meyers singleton.
UserConfig is renamed to MetricsUserConfig and merged into metrics, reflecting that it is used effectively only for metrics.
track_feature is no more; use track_bool instead.
Unit testing metrics submission infrastructure is now possible since forming payloads can now be fed synthetic data.

Future work:

I can see an argument that what is now called MetricsSubmission should now get the name Metrics? Easier to review this way for now.
Deglobalize the metrics collector to enable metrics emitted by components to be unit tested.
Actually add the interprocess communication with node world I came here for.

This PR changes the order of buildnames_1 and buildtimes from insertion order (build/topological order, I believe) to order by "name". But this change should have no impact for our current telemetry.

It's a JSON document so if the order of keys mattered in an object that would be .... bad

This PR changes the order of buildnames_1 and buildtimes from insertion order (build/topological order, I believe) to order by "name". But this change should have no impact for our current telemetry.

It's a JSON document so if the order of keys mattered in an object that would be .... bad

I meant the underlying store for buildtimes/buildnames, this changes them from vectors where values were inserted in build/topological order to maps where they're sorted by spec hash.  As I said, this is a non-issue though.


Integration tests do not work when response is a subclass of List

Just starting out with Fast Endpoints (and, well, with C# and .NET as well). I thought I'd like to have an explicit response class instead of List<SomeDTO>, so that looking at the files it would be easy to discover what the response was. However, the problem is that in my integration test I get a null response.
My response object looks like this:
internal class MyOperationResponse : List<SomeDTO>
{
    public MyOperationResponse(IEnumerable<SomeData> data) : base(data) { }
}

Endpoint definition:
internal class MyOperationEndpoint : EndpointWithoutRequest<MyOperationResponse>
{
    // ...

Call in the test:
        (HttpResponseMessage? httpResponseMessage, MyOperationResponse? result) =
            await Fixture.Client.GETAsync<MyOperationEndpoint , MyOperationResponse>();
        Assert.NotNull(result); // <--- fails

It works when executing through Swagger (I get a list of JSON objects as response, as expected), but as said, does not work when running the tests - a null is returned.
By replacing all usages of MyOperationResponse with List<SomeDTO> the test starts to work as well.
Is this a bug or am I just not supposed to subclass List in responses?

I don't recommend subclassing List but rather wrapping it. So your response would look like this:
internal class MyOperationResponse
{
  public List<SomeDTO> DTOs { get; set; } = new();
}

This is a much more flexible approach and I suspect it will work better with your tests. Can you try it?

Hi @ardalis , thanks for the response.
Your suggestion works, but it also wraps the response in an object and uses the "dtos" as a key for the list. I suppose this was intentional from your part, and by flexibility you mean that now the response can now be expanded with other properties without breaking compatibility with older clients? Thanks, I might do that.
I'm okay with this / don't need more help, but I'm leaving this open in case this is considered a bug to be fixed.

Right you can add other properties, such as metadata for paging or the date when the information was last updated, etc. Having a custom DTO, rather than inheriting from List gives you many potential options with very little lost (your result is now not in the root of the payload... that's it). Good luck!

@ardalis is spot on with the advice to not subclass a list, and i recommend everyone to follow it.
however, i dug a bit deeper into why exactly it wasn't working and found out that it's because STJ is throwing internally due to not being able to find a parameterless constructor on your dto.
so if you really must, just add a default ctor and it will work.
also starting v<IP_ADDRESS>-beta, the exception will no longer be swallowed.


fix(string-template): preserve number type for fields prefixed keys

Summary
The introduction of string template support for the relation widget caused a bug where values in int fields are converted to strings.
This PR fixes #3709.

Test plan

Added a relevant test case and ran yarn format and yarn test without any errors.

Thank you for reviewing the PR. I think that's a great idea! Messing with compileStringTemplate didn't seem ideal because of all the changes that followed. Localizing the change to the relation widget is a much better approach.

Replaced by https://github.com/netlify/netlify-cms/pull/3850


WIP: (PUP-4080) accept s3 URLs as file source

Hi Guys,
Hoping to get some feedback at an initial stab at building in support for s3 URLs as a source for the puppet file type resource.  I have modeled the code heavily on PR-3372 by @ffrank.
I am yet to add spec tests and will do some work on it.  Is this something that would likely be merged into Puppet?  I am new to ruby programming and originally tried to add the code to the puppetlabs-aws module (@garethr @Iristyle) however I could not work through the issues accessing internal puppet classes??
Thoughts, suggestions?
Even though it does not have any spec tests yet it is in a usable state.  To test:

Create an S3 bucket, file in the bucket and setup access permissions

(On your development machine)
2. Pull down the code
3. Install the aws-sdk-core ruby gem
4. Setup your s3 credentials (see the aws-sdk-core documentation)
5. Create a puppet manifest eg:
file { '/tmp/example.txt':
source => 's3://foo-bucket/bar.file',
region => 'ap-southeast-2',
}

bundle exec puppet apply manifest.pp

Waiting for CLA signature by @pjfoley
@pjfoley - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppetlabs.com/
Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppetlabs.com/community/trivial_patch_exemption.html

CLA signed by all contributors.

Hi @pjfoley - thanks for the contribution!
I'm a little short on time at the moment, but I can tell you that is something that is unlikely to be merged into core Puppet.
As part of the 4 release, we have been trying to remove any non-essential types and providers, and place them into modules. For one, this makes it easier for us to ship updated modules easily out of band from releases of Puppet itself. It also simplifies or dependency trees and packaging efforts.
That said, the AWS module is probably where we would extend with something like this, though the implementation might get a little tricky.  I'll discuss with my colleagues some more when I get to the office.

Hi @Iristyle thanks for the feedback, I originally was trying to work out how to add the capability to the puppetlabs-aws module so happy for it to go there (it just makes sense (tm)).
I understand that you are busy with the 4 release but hoping you might have a couple of minutes to provide some comments.  This will help me to work out how to try to build it into the puppetlabs-aws module.
Do you envisage it working in a similar way to how puppet manages hiera backends?
So the module would implement (similar to how file sources are managed):

Metadata function
Return the content function

How would the user signal to use a module provided source?  Something like how a user can choose a provider for the package type? ie something like the below:
file { '/tmp/example.txt':
source   => 's3://foo-bucket/bar.file',
provider => 'aws',
region    => 'ap-southeast-2',
}
This would allow a puppet user to specify different providers per-file type.

FWIW, there was a lengthy discussion during the PR hangout. Sadly, the
recording at YouTube
doesn't seem to work.

I was just reading through http://docs.puppetlabs.com/guides/custom_functions.html and I thought I would flag something for your discussion internally.
Whatever solution developed must allow the agent to be the machine that pulls file source.
This is to allow for the use of amazon IAM roles to protect access to the s3 bucket.  Ie only a certain machine running the puppet agent with the right credentials allocated can pull the file out of the s3 bucket.
I assume that both hiera and the package provider code only runs on the puppet master?

Thanks for the heads up @ffrank I will keep an eye on the youtube link to watch it when it is posted.

On 03/09/2015 01:07 PM, pjfoley wrote:

I assume that both hiera and the package provider code only runs on the
puppet master?

The problem is that we have no file provider at this time. The type
code does everything. Both type and provider code runs on the agent side.
Parser functions will not come into play, I reckon.
Implementing such support in a module will make it necessary to ship
some type and/or provider code that ties in seamlessly with the file
resource type.

@ffrank @pjfoley The link should be https://www.youtube.com/watch?v=IRwEVuX_7GY for the PR triage from 2015-03-4

Thanks @melissa I had found a wrong entry through youtube search, apparently.
Pertaining discussion is towards the end.

Hi Guys,
Just watching the latest triage video that Melissa posted.  Regarding the region extension to the puppet type (+ 30 minutes into the video) I was following the convention used in the puppetlabs-aws module (see https://github.com/puppetlabs/puppetlabs-aws#ec2_instance).  Happy for it to be built into the source property if that makes it easier.

Well, that discussion belongs on the mailing list, I believe, but FWIW, I think that the file resource will need a generic parameter akin to package's install_options for passing information that pertains to certain files only (e.g., such that are to be retrieved from s3).

That sounds ideal! Obviously each source provider may provide different options

@branan just following up on your reference to your s3file module and how via a defined type it fetches files from s3 (+ 30 minutes in the triage video).  When originally trying to work out how to pull protected files out of s3 I looked at your module.
One thing that was not clear to me (I admit I could not work out how to do it with your module) was accessing files from secured s3 buckets (ie non-public).
By using the Amazon supported gem (aws-sdk-core) it automatically sources credentials available to it (see http://docs.aws.amazon.com/sdkforruby/api/#Credentials).
For my example in response to @ffrank I want to use the instance credential allocated against a IAM role for the ec2 instance (unique for each ec2 instance) which the aws-sdk-core gem will automatically source from the metadata service.

@pjfoley I didn't realize pulling content from protected buckets was a requirement in your design, so yeah - using the gem is better in that case.

Given your PR against puppetlabs-aws, should we close this one?

@branan in my opinion no.  Unfortunately the PR against puppetlabs-aws is majorly inefficient.  It does not check the metadata to see if it needs to download the content of a file.
For my use case it would be managable (a couple of Kb per private key) but for those who use it to download larger files it would soon add up in costs.
Also as noted in the PR message, I am not sure if it is by design, a bug or a limitation in the puppet language.  If in the file resource I set "replace => false" it will still call the function and download the content.
solution I have

I'm going to close this out. I'm leaving the ticket open, and have also filed PUP-4368 to track adding the appropriate extension points so that this can be implemented in a module.


doc: add some comments for keys & rename keys -> key

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?

See https://github.com/singularity-data/risingwave/pull/3700/files#diff-2b8f52f88a4b68d52744d240d51f436cc58b37b572fbf797c194e39edf91ed9b for the added comments
rename keys -> key: a key is a whole, consisting of multiple columns. So we should call it key instead of keys

rename keys -> key: a key is a whole, consisting of multiple columns. So we should call it key instead of keys

At least the keys in expand's subset is not following this definition ... It was used as a synonym of "column index" ... I will take care of fixing the naming there.


Docker Support

Are there any plans to add docker support?

@jwmoss I have no plans to add Docker containers to the project because I see that as an installation and packaging issue outside the scope of what I'm doing here. Also, I have no expertise in that area.
However, one user has already created a Docker container:
https://github.com/rcarmo/docker-other-video-transcoding
I haven't tried installing it and have no plans to do so. And obviously I can't speak to the capabilities and quality of that container.
It's possible that @ttyS0, one of my collaborators, will create a Docker container soon. In fact, I've encouraged him and other folks on the team to do so because I'm sure other users (Ta da! like yourself :) would be interested.
Keep in mind that access to hardware encoders from within a Docker container is problematic. It's a solvable problem but it may not be solvable in a completely portable way.
But @ttyS0 can explain these issue much better than me so I'll leave that to him.
Thanks for opening this issue so we could start a discussion!

Hi @jwmoss,
The biggest issue with Docker in the context of this project is, as @donmelton mentioned, the hardware component. Since Docker requires a Linux system (I'm disregarding Windows containers, since they are still very experimental), using a Docker container on either a Windows or macOS system involves the use of a Linux VM where the Docker engine runs. Both Docker for Mac and Docker for Windows install such a VM, but it's not easily accessible or directly configurable, since it's only intended to run the Docker engine. That means for hardware acceleration on those platforms to work with a Docker container, the hardware GPU has to first be passed into the Linux VM installed by (and for) Docker, and then passed to a Docker container. Jumping through those hoops doesn't provide any obvious advantage since @donmelton's software is already able to run natively on all those platforms with minimal installation effort.
From my perspective a Docker container becomes useful in the context of automated scheduling of transcoding jobs with hardware assist. That presupposes nodes with the requisite hardware, and a scheduling system like Hashicorp Nomad, Kubernetes, or similar. The scenario I'm specifically focussing on is Kubernetes.
In short, if you're looking to run the hardware transcoder in a Docker container on a single system, such as a desktop or laptop, you're going to be best served by just running the software directly on the system. If, however, you're looking at making a hardware transcoder pipeline, then when I get something that's not too terrible to look at up and running, I will definitely add a comment into this issue so you can get notified.
As to it being done soon ... well, as a vastly smarter person than I once said, "the future is long". 😎

@ttyS0 That's an awesome response! Thanks!

Hi @ttyS0,
Thanks for the response! I currently run docker containers in unRAID and passthru QuickSync and can understand how that can be challenging in regards to this project. Thanks for the thorough reply. I await to see what you end up doing with this soon 😄

@jwmoss If you're wanting to use VAAPI hardware acceleration (i.e. Intel GPU), I have a functioning container for Don's other-transcoding over here: https://github.com/ttyS0/docker-transcode-vaapi
I still have to write out the documentation, but I'm pushing the image to GitHub, and it can be pulled from there. For basic usage, assuming you're in a directory foo, and have a source file in foo/bar/file.mkv, the command to transcode it with the Docker container is:
docker run --device /dev/dri:/dev/dri -v $(pwd):$(pwd) -w $(pwd) docker.pkg.github.com/ttys0/docker-transcode-vaapi/other-transcode-vaapi:0.2.0 bar/file.mkv
I have some other work to do to get it ready for a K8s environment, and I may end up putting a script as the ENTRYPOINT, but the basic functionality is there. If you run into troubles, feel free to give a yell! A container with Nvidia support will be coming .... ahem ..... soon. 😎

@ttyS0 This is awesome! Thank you so much, sir!

@jwmoss I'm closing this now because I finally remembered to check in the link to @ttyS0 's awesome Docker container into the "README" document. D'oh!

@jwmoss Just thought I'd mention that, in this case, soon meant .... about 3 months? 😎
There's an NVidia Docker container for other-transcode now: https://github.com/ttyS0/docker-transcode-nvidia
To use it on a Linux system (I've only tested on Ubuntu 18.04), you'll need the latest NVidia drivers (440.64), Docker-CE (not the Docker bundled with the distro) 19.03 or later, and nvidia-container-toolkit. Once all those things are in place, running the container with the --gpus all option will hook it onto the NVidia card.
For example, the following will encode src/file.mkv using HEVC:
docker run --gpus all -v $(pwd):$(pwd) -w $(pwd) ttys0/other-transcode-nvidia:v0.3.0 --hevc src/file.mkv
😸


📏 Range Component

Double slide component for range input.
Should emit the two values separately. No need for two-way binding.

The handles do not update positions properly.


CNS hands out duplicate IP's to CNI in race condition

What happened:
goldpinger-deploy-8f8746dbb-qq6h5   1/1     Running   2          5d      <IP_ADDRESS>    aks-nodepool1-25205300-vmss000001   <none>           <none>
goldpinger-deploy-8f8746dbb-wv564   1/1     Running   2          5d      <IP_ADDRESS>    aks-nodepool1-25205300-vmss000001   <none>           <none>

There are two pods running at the same time with duplicate IP's.
What you expected to happen:
How to reproduce it:
When CNI calls CNS to free an IP, CNI only presents the name of the pod and pod namespace to CNS to free the IP.
Race condition can happen in this scenario:

Containerd restart.
Tries to remove all previous containers but there's lockcontention so it takes 10's of seconds
Tries to add all new containers
One of the adds gets the lock before one of the deletes cause there is no fair queuing.
We delete a valid running container

Orchestrator and Version (e.g. Kubernetes, Docker):
Operating System (Linux/Windows):
Kernel (e.g. uanme -a for Linux or $(Get-ItemProperty -Path "C:\windows\system32\hal.dll").VersionInfo.FileVersion for Windows):
Anything else we need to know?:
[Miscellaneous information that will assist in solving the issue.]

closed in #875


Update request: graalvm-ce 22.3.1 -> jdk-21.0.0

Package name: graalvm-ce
Latest released version:

Current version on the unstable channel: 22.3.1
Current version on the stable/release channel: 22.3.1

[x] Checked the nixpkgs pull requests

Notify maintainers

@bennyandresen @hlolli @glittershark @babariviere @ericdallo @thiagokokada (of course :P)

Note for maintainers: Please tag this issue in your PR.

So I took an early look at this bump and there is a bunch of changes upstream that we will need to adapt. To start they changed the way they do versions so this is why it seems that we are "downgrading" the version instead of upgrading: the versions now match the JDK version that GraalVM is based on. Also, thanks to this change all URLs are changed.
Also, each of the sub-products (e.g.: GraalPy) are now released independently from the GraalVM main releases and have their own version (it is on 23.1.0 right now, but I expect that they diverge in the future). They also seem to be self contained and not rely in having GraalVM installed anymore, so we can just stop bundling all the packages together in a "super" derivation as we do right now and just split each sub-product in its own package. Thanks to this change, they also don't ship jar anymore, they are all in .tar.bz2 format that should make our lifes easier.

Hello @thi


is it possible to archive te repo instead of deleting

i saw this text in the readme and i thought deleting is a litle bit too brutal and for transparency and legacy reasons archiving would be better

STM is currently rebuilding external PHY Ethernet support for Arduino_Core_STM32.

This situation has not changed since 4 years ago.
STM will probably never support external PHY Ethernet.

but if it changes could you archive this repo instead of deleting it


Bug Report: PowerShell deployment runs forever or fails

Describe the bug
Deploy ALZ reference implementation with PowerShell doesn´t work
Steps to reproduce

New-AzTenantDeployment -Name "ALZ-Deployment-$(Get-Date -Format 'yyyyMMddTHHMM')" -Location "westeurope" -TemplateUri "https://raw.githubusercontent.com/Azure/Enterprise-Scale/2024-09-03/eslzArm/eslzArm.json" -TemplateParameterFile ".\ALZ-Portal-parametersFile.json" -WhatIf
Getting the latest status of all resources... forever

Seems to me that there is the same error/behaviour in the "Test Portal experience" workflow in this repo ?
Screenshots

Is this a general problem with PowerShell deployment at the moment ?

@jdrepo I'm busy testing the release of Policy Refresh and have had many issues today. I don't think it's a PowerShell issue, looks like the ARM engine is throttling or having issues. Can I ask you to try again after a bit?
There is some another issue currently impacting testing that we're investigating - its authentication related.

@Springstone Thanks for your reply, yes I can test it again later, I also had the problem yesterday and I also think it has nothing to do with PowerShell, as the problem also occurs with azure cli deployments, so then probably a fundamental problem with the ARM backend

@jdrepo are you still experiencing issues or can we close the issue?

Hi @Springstone
didn't try it again. I'm currently out of office, will try it tomorrow and give then a feedback.
Please hold the issue open. Thanks

Hi @Springstone, tried again today and the issues still occur, seems to me nothing has changed, deployment runs forever if deploying with PowerShell

@jdrepo could you try run the same deployment without the -WHATIF (we suspect recent changes in pre-flight processes are causing a problem). I will validate as well the WHATIF process as well - as per the screenshot above, the WHATIF process is failing for us due to timeout.

@Springstone Will give it another try, it seems to me that it depends on the template parameter file, i just tried it with a "small" parameter file with only the enterpriseScaleCompanyPrefix parameter in it , then the -whatif run succeeds. But with a full blown parameter file ( with all parameters set - more than 700 lines ) the deployment times out again.
What did you set in your parameters.json in your last test ?

@Springstone Did some more tests and I think found the cause: If I change the deployment location to another region than westeurope  the what-if deployment  runs without any problems.
I did a test with swedencentral or eastus or northeurope like you did and had no problems (sometimes it took some minutes, sometimes it runs under 60 seconds ), so it seems to me that there indeed some issues with the ARM backend in my preferred region westeurope
Can you try to run your last deploynment against the westeurope region ?

@jdrepo yes, looks like it is westeurope that is having issues with whatif. It actually looks like PowerShell hangs, as I can't terminate/break the deployment either, and running with -debug indicates it hangs pretty quickly. Might be related to restrictions in that region?
You may want to open a support ticket for this, and we'll see on our end if we can get someone from engineering to investigate.

@Springstone yes, I can observe the same behaviour. PowerShell hangs and can´t be terminated. I let the task running and after approx. 1 hour it came back with a lot of error messages

I have no idea why the germanywestcentral region is involved when I deploy the template against the westeurope region.
Maybe it reroutes the ARM request to this region, because I´m located in Germany.
Earlier this morning I tried it against the germanywestcentral region that did run without any problem.
Now I tried it again and it hangs again, very strange.
I can try to open a support ticket but I don´t know if this environment is covered by a support plan...
`DEBUG: ============================ HTTP RESPONSE ============================
Status Code:
OK
Headers:
Cache-Control                 : no-cache
Pragma                        : no-cache
x-ms-ratelimit-remaining-tenant-reads: 249
x-ms-request-id               : 502dc99b-81a6-4865-89d9-5519e99ef8c1
x-ms-correlation-request-id   : 502dc99b-81a6-4865-89d9-5519e99ef8c1
x-ms-routing-request-id       : GERMANYWESTCENTRAL:20241015T093338Z:502dc99b-81a6-4865-89d9-5519e99ef8c1
Strict-Transport-Security     : max-age=31536000; includeSubDomains
X-Content-Type-Options        : nosniff
X-Cache                       : CONFIG_NOCACHE
X-MSEdge-Ref                  : Ref A: 7F43E0C7BFB649B7A1D874C76F40E3E0 Ref B: FRA231050415021 Ref C: 2024-10-15T09:33:38Z
Date                          : Tue, 15 Oct 2024 09:33:38 GMT
Body:
{
"status": "Failed",
"error": {
"code": "DeploymentWhatIfTimeout",
"message": "The request to predict template deployment changes to scope '/' has timed out. Diagnostic information: timestamp '20241015T093337Z', tracking id '57bceef4-2bc1-4523-9dd3-350f66db0e2b', request correlation id 'd69a9d3c-6b34-4fdc-8c59-7f02c3f48e86', location 'germanywestcentral'."
}
}
DEBUG: 11:33:42 - [ResourceManagerCmdletBase.ExecuteCmdlet] Caught unhandled exception: Microsoft.Rest.Azure.CloudException:
DeploymentWhatIfTimeout - Long running operation failed with status 'Failed'. Additional Info:'The request to predict template deployment changes to scope '/' has timed out. Diagnostic information: timestamp '20241015T093337Z', tracking id '57bceef4-2bc1-4523-9dd3-350f66db0e2b', request correlation id 'd69a9d3c-6b34-4fdc-8c59-7f02c3f48e86', location 'germanywestcentral'.'
at Microsoft.Azure.Commands.ResourceManager.Cmdlets.SdkClient.NewResourceManagerSdkClient.ExecuteDeploymentWhatIf(PSDeploymentWhatIfCmdletParameters parameters)
at Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.CmdletBase.DeploymentWhatIfCmdlet.ExecuteWhatIf()
at Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.CmdletBase.DeploymentCreateCmdlet.OnProcessRecord()
at Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.ResourceManagerCmdletBase.ExecuteCmdlet()
DEBUG: 11:33:42 - [ConfigManager] Got nothing from [EnableErrorRecordsPersistence], Module = [], Cmdlet = []. Returning default value [False].
New-AzTenantDeployment:
DeploymentWhatIfTimeout - Long running operation failed with status 'Failed'. Additional Info:'The request to predict template deployment changes to scope '/' has timed out. Diagnostic information: timestamp '20241015T093337Z', tracking id '57bceef4-2bc1-4523-9dd3-350f66db0e2b', request correlation id 'd69a9d3c-6b34-4fdc-8c59-7f02c3f48e86', location 'germanywestcentral'.'
DEBUG: 11:33:42 - [ConfigManager] Got nothing from [DisplayBreakingChangeWarning], Module = [], Cmdlet = []. Returning default value [True].
DEBUG: 11:33:42 - [ConfigManager] Got nothing from [DisplayRegionIdentified], Module = [], Cmdlet = []. Returning default value [True].
DEBUG: 11:33:42 - [ConfigManager] Got nothing from [CheckForUpgrade], Module = [], Cmdlet = []. Returning default value [True].
DEBUG: AzureQoSEvent:  Module: Az.Resources:7.5.0; CommandName: New-AzTenantDeployment; PSVersion: 7.4.5; IsSuccess: False; Duration: 01:02:29.6872120; SanitizeDuration: 00:00:00; Exception:
DeploymentWhatIfTimeout - Long running operation failed with status 'Failed'. Additional Info:'The request to predict template deployment changes to scope '/' has timed out. Diagnostic information: timestamp '20241015T093337Z', tracking id '57bceef4-2bc1-4523-9dd3-350f66db0e2b', request correlation id 'd69a9d3c-6b34-4fdc-8c59-7f02c3f48e86', location 'germanywestcentral'.';
DEBUG: 11:33:42 - [ConfigManager] Got [True] from [EnableDataCollection], Module = [], Cmdlet = [].
DEBUG: 11:33:42 - NewAzureTenantDeploymentCmdlet end processing.`

@jdrepo not to worry, I've opened an internal engineering ticket to investigate the WHATIF issue. However, I do believe that if you remove the WHATIF flag the deployment will proceed/succeed. If you find otherwise, please do let me know.

@Springstone yes as assumed the "real" deployment does start, so it´s indeed only an issue with --whatif deployments.
But during the deployment I now encountered some deployment errors, seems to me that there is a problem with the management groups hierarchy syncronization during the deployment flow. Is that a known issue ?

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"InvalidCreatePolicyAssignmentRequest","message":"The policy definition specified in policy assignment 'Deny-MgmtPorts-Internet' is out of scope. Policy definitions should be specified only at or above the policy assignment scope. If the management groups hierarchy changed recently or if assigning a management group policy to new subscription, please allow up to 30 minutes for the hierarchy changes to apply and try again."}]}

@jdrepo any errors that include the text please allow up to 30 minutes for the hierarchy changes to apply and try again. are related to delays in the policy engine registering the policy. We had a mitigation in place to minimize this, but seems the ARM/Policy engines are struggling to keep up - so will be extending the deployment wait time to help minimize this issue.
TLDR Policy isn't available for assignment yet. If you re-run the deployment with the same parameters, it will succeed.

@Springstone can you give me short notice how and if I can extend deployment wait time ?
For the what-if issue:
Did you get an response from internal engineering ? I`ve opened a support call and would it be helpful to link these calls ?

@jdrepo you can't change the wait time yourself, but we've pushed through a patch to increase the wait time an additional couple of minutes, use the latest release (https://github.com/Azure/Enterprise-Scale/tree/2024-10-14).
I am working with engineering on the WHATIF issue but seems something has changed as it suddenly started working this morning. Could you confirm that it is working for you?

@Springstone isn'it possible to change the wait time if I modify the parameter "delayCount" in the template parameter file ?
Did another WHATIF deployment against the "westeurope" region and the issue still occurs ?
What I can´t understand if I start the deplyment against the "westeurope" region, why I get an error message mentioning the "switzerlandnorth" region ?

@jdrepo yes, you can increase the delayCount, did see it in the portal deployment parameters file - I've been working with other template param files :) for testing that don't include those parameters.
I've confirmed with PG this is a transient issue, which is why it sometimes works and sometimes doesn't (very inconsistent). I ran this on the weekend and 9/10 worked fine, one time it failed with a similar error.
I wouldn't worry about the SwitzerlandNorth, as it could be that an RP or part of ARM is running from there - the error message doesn't indicate an actual issue with deployment, just that it's a long running operation (basically it's timed out).


Add feature to mock image selection

Describe your idea
It would be nice if one could test the image handling behaviour of ones app.
Theoretically the emulators offer a couple of example images but these are hard to use in automated tests.
Instead of opening a real image selector it would be nice if detox could mock this behaviour.
proposed syntax:
interface MockImageOptions {
    //make android intent filters customizable here
}

//This would make all image pickers return this image until another one is defined.
device.setMockImage(image: Buffer, mime: string, options?: MockImageOptions);

//Turns off the mocking. The App will behave normally.
device.clearMockImage();

Implementing this for Android looks straight forward with: https://developer.android.com/training/testing/espresso/intents
On Ios it seems as it might be possible to mock the picker at compile time like this: https://github.com/yonat/MockImagePicker

I'd be willing to invest some time into this, but this has no high priority for me right now. So this would take some time to implement. Help would be welcome.
What are your general thoughts regarding this?

Hi @mauricedoepke,
Thanks for the suggestion to add the ability to mock image pickers to Detox. While Detox does not have the ability to be involved in the compilation process, it is possible to use libraries like MockImagePicker to mock this behavior within the app itself.
If you're working with a React Native app, you can also use Detox's mock utils or mock the respective module in your app to achieve this behavior. Please note that Detox does not provide any mocking functionality itself, but rather provides a framework where you can use tools like these. See our mocking guide: https://wix.github.io/Detox/docs/next/guide/mocking.
If you're interested in implementing this mock for use in Detox tests, we'd be happy to help and consult. You might also consider contributing your solution as open source to benefit the community.

Hey @asafkorem Thanks for your response.
I think having this directly built into detox would make this much more accessible than having to fiddle around with 3rd party libs.
At least for android it should not be too hard to implement as the required features are available via espresso.
I would try to work on that after the setDatePicker is done.
Regarding IOS. I thought detox would be at least partially compiled into the app to take the commands from javascript. At least that's how I understood this section:

https://wix.github.io/Detox/docs/articles/how-detox-works/
Detox native client (iOS & Android): A component that gets seamlessly integrated into the tested app on the tested device, right as Detox starts executing. It synchronizes with the app, matches user queries, executes user commands (e.g. taps, scrolls) and validates expectations.

Is this correct or was this a false assumption?
My hope was that this would maybe allow to optionally compile a similar mock approach as MockImagePicker into the app along with detox to support this feature.

@mauricedoepke, you were incorrect in your assumption that Detox is compiled into the app on iOS. Detox is actually integrated into the app on iOS at runtime using DYLD_INSERT_LIBRARIES (see: https://github.com/wix/Detox/blob/master/detox/src/devices/common/drivers/ios/tools/AppleSimUtils.js#L410). However, there are other ways to mock things, even on the native side, such as using ObjC swizzling for UIImagePickerController methods.
I'd like to continue this discussion, especially regarding the API itself in our Discord server 😎

@mauricedoepke thanks for this proposal. We've discussed this internally for a bit and we largely agree that this type of mocking could be provided in ways similar to the standard mocking that we offer in our mocking guide - albeit network-focused.


[RFC FS-1017] Allow all inferrable SRTP constraints to be written in signatures

This implements RFC FS--1017. A niggling language issue reported by @drvink quite a long time ago.
Basically it allows statically resolved member constraints to include a type - rather than a type parameter - in the list of items by which the constraint can be solved.
     .. when (Ty or  ^Typar) : (static member ... :  ...) =

This both fixes a "hole" where soome types could be inferred and printed, but not written in signatures, and also increases the utility of the statically-resolved-type-parameter (SRTP) mechanism.
The implementation is very straight-forward.

RFC PR at fsharp/FSharpLangDesign#103.

other than commented out code looks fine to me.

I've updated this PR with a fix for https://github.com/Microsoft/visualfsharp/issues/1306

Transient AppVeyor failure (unrelated to PR).  AppVeyor have changed their hardware recenty which may explain a change in test timings for non-deterministic tests.  There is either a bug lurking or an unstable test
[00:40:44] 1) Error : FSharp.Core.Unittests.FSharp_Core.Microsoft_FSharp_Control.AsyncModule.Async.Choice specification test
[00:40:44] System.Exception : Falsifiable, after 43 tests (0 shrinks) (StdGen (15424488,296180491)):
[00:40:44] Original:
[00:40:44] ChoiceWorkflow
[00:40:44]   ([NoneResultAfter -8; NoneResultAfter 9; SomeResultAfter 2;
[00:40:44]     SomeResultAfter -18; ExceptionAfter 12; ExceptionAfter -8;
[00:40:44]     NoneRes
[00:40:44] ultAfter -15; NoneResultAfter 2],Some 8)
[00:40:44] with exception:
[00:40:44] NUnit.Framework.AssertionException:   Expected: 4000
[00:40:44]   But was:  6000


Hover state on icons/glyphs?

Hey y'all.
We have a "launch" icon (glyph?) that is clickable in our product. We're trying to figure out

If it should have a hover state, when it is used as part of a hyperlink.
If so, where should the style be set for the hover state (by Carbon? By our team?)

See the comment here: https://github.ibm.com/alchemy-containers/armada-ui/issues/1810#issuecomment-5582715
From @jpomero:
"Color: The carbon bx--link class only updates the color of the link, not the fill color for any SVG elements. Our fix would be to override their class so therefore this should get punted to carbon.
Size: We are using the correct icon, but we are setting a size of 15x15 on it. I don't have a strong feeling about making this 16x16 as long as it looks fine. Also, this should be the same thing we're doing anywhere this icon is displayed, not specific to this link."
What do you think?

@carbon-design-system/design If a link is wrapping an SVG, should the hover styles also be applied to the icon? I'm guessing if we would add this, it would get the hover-primary-link styles?

Yes, the associated icon should also have the same hover style applied.


"Jump to..." global interaction?

After looking at #1500, I wished I could instantly navigate to Moya/Moya#1565 in GitHawk. Search is a little jank right now b/c you can't search issues, but even then, that requires changing tabs (not visible from an issue on iPhone), searching, then tapping the result (if found).
However if you already know your destination, maybe it'd be better to let people textually navigate to stuff?
Imagine something like shaking the app or swiping up from the bottom to show a text field. Once focused on the field, you get an input accessory view w/ / and # shortcuts. You type in moya/moya#1565 and we push that issue VC onto the stack.
You could also just type moya/moya to go to that repo.
Thoughts on this? Would you use it?

This would be super powerful for tablets with a physical keyboard and a keyboard shortcut similar to Slack (Cmd K)/Xcode (Cmd Shift O)/Many apps
I think if it was easy to access then I probably would use it, maybe if we could get a bit of an autocomplete where if you start typing Moya/Mo it would sort of preview ahead of the cursor of the best match where you can press tab or something to use that?
Just trying to think of efficiencies here!
As your simple solution though, can't hurt!

Imagine something like shaking the app or swiping up from the bottom to show a text field. Once focused on the field, you get an input accessory view w/ / and # shortcuts.

Sounds pretty cool to me 👌
Maybe we can leverage a user's bookmarks here? Like if you have Moya/Moya bookmarked maybe you can get some extra autocomplete benefits 🤔


[jk] Show logs in reverse chronological order

Summary

See title.

Tests

We should click the button at the top show older logs.


how to get the registration object after install

Doc says to install service worker use runtime.install(options:Object), but i want the registered reg object so that i will make push manager use of it  as specified in the doc https://developers.google.com/web/fundamentals/getting-started/push-notifications/step-06?hl=en , so here how i will get the .then(function(){}) after registering the serviceWorker using the runtime.

navigator.serviceWorker.ready.then((reg) => {
  // ....
})

https://developers.google.com/web/updates/2015/03/push-notifications-on-the-open-web

Thanks for that doc.

No problem :-)


devicesToPublishAsAccessoriesSwitch not working as expected

Describe the bug
I get two switch buttons. Both default in state Powered Off.
One of them can only power off and the other can only power on.
Both have the same description (the correct name of the device).
State of the switch is not persisted.
To Reproduce
Steps to reproduce the behavior
"devicesToPublishAsAccessoriesSwitch": [
"Harman Kardon AV-ontvanger"
],
Expected behavior
A clear and concise description of what you expected to happen.
I expected  toggle On/Off switch or two switches with the correct description.
Screenshots
If applicable, add screenshots to help explain your problem.

 Please do not post your whole config and especially with logins / passwords !
"devicesToPublishAsAccessoriesSwitch": [
"Harman Kardon AV-ontvanger"
],
Additional context
Add any other context about the problem here.
Possibly related to #308

Please could you be more explicit and fill in correctly the bug report template ? I d'ont understand what is the problem there

@nicoduj I tried to clarify the description and added screen dump. Hope this helps.
I use your plugin for some time in basic config and I'm now trying some of the advanced features.
I apologize if I'm misunderstanding the feature.

Device switches are always stateless, since harmony does not provide device state.  I t will publish a powertoggle or poweron / off switches depending of the device in harmony app.
The fact that you have 2 switches with same name suggest your config is exposing 2 powertoggle, would need your whole harmony setting (launch in debug and retrieve the json) to investigate.

Did you manage to check / get your hub config please ?

thank, that was what was expected but there must be a bug there, will check. But at first you had allready renamed them no ?
they did not have Harman Kardon in their name, they should at least take the name of the device ...

I only added Aan and out.
I notice that in the tiles on the home screen Harmon Kardon is in the name and in the Room this is missing.

Will try to reproduce, not really sure what happened there.

can't reproduce, not sur eto have the whole info however. Having harmony hub config would help to understand the devices / controls since I d'ont really understand the names provided (seems to be 2 different deivces/ or maybe renamed in home app)

can't reproduce, not sur eto have the whole info however. Having harmony hub config would help to understand the devices / controls since I d'ont really understand the names provided (seems to be 2 different deivces/ or maybe renamed in home app)


Border Color is not visible

Description
Border Color is not visible for the first event in event list.
Screenshots

Additional information
No response

Can you assign me to this issue?

Hey i would like to work on this issue

I think I can handle that.

hey i looked into the problem at https://linkfree.io/events and will love to work on it as a guy who works with tailwind css

Hi there ,
I would love to contribute in this project , and fix this error

Can you assign me to this issue?

@anikdhabal I have assigned this to you as you were the first to request. In future if you would like to work on an issue that you have created, feel free to mention this in the Additional Information of the issue template.

Can you assign me to this issue?

@anikdhabal I have assigned this to you as you were the first to request. In future if you would like to work on an issue that you have created, feel free to mention this in the Additional Information of the issue template.

okk

Can you assign me to this issue?

@anikdhabal I have assigned this to you as you were the first to request. In future if you would like to work on an issue that you have created, feel free to mention this in the Additional Information of the issue template.

okk

@anikdhabal are you still working on this ? otherwise I would like to give this a try @SaraJaoude !

@anikdhabal are you still working on this ? otherwise I would like to give this a try @SaraJaoude !

yes I am working on this.

anikdhabal are you still working on this ? otherwise I would like to give this a try @SaraJaoude !

@vishalsingh2972 please avoid putting pressure on assignees especially when they have been assigned the issue less than two weeks ago.In future also please avoid tagging a specific maintainer for generic questions as this adds noise and extra notifications - all maintainers receive the project's notifications and can deal with these. I would suggesting looking at our Contributing Guide.

Closing issue as it is superseded by #7840


Vaporware?

Hello,
I'm interested in a Node binding for the C/C++ MySQL replication API. Did you get anywhere with this?
Thanks,
Jeff

My friend @nevill built a pure js binlog listener package names 'zongji'. We use it now.
Sent from my iPhone

在 2015年10月4日，10:10，Jeffrey<EMAIL_ADDRESS>写道：
Hello,
I'm interested in a Node binding for the C/C++ MySQL replication API. Did you get anywhere with this?
Thanks,
Jeff
—
Reply to this email directly or view it on GitHub.


Add option to turn off deduping

You should probably elaborate on why.

What initially prompted me to do this was an issue with the livereactload library and things being incorrectly deduped. In general though, I think it is useful for debugging. Deduping is not an easy thing to do (just look at npm3 for example). When weird things are happening with builds, it would be useful to be able to turn off deduping to help diagnose/isolate the issue.

Sorry! I think I accidentally closed the PR when I commented on it last time. Still interested in getting this merged if it looks good.

This patch looks good to me, it merely exposes features that are already available in sub-modules.


Issue109

Thanks to @gmanfunky, a couple of issues was found and better handling of systems where systemctl doesn't work was implemented.
Fixes #109

Test /etc/systemd/system/${SERVICE}, first then use systemctl, and if that fails fall back to /usr/lib/systemd/system/$SERVICE.
I prefer to include systemctl show because things might not wind up where one would expect.
$ systemctl show -p FragmentPath docker.socket
FragmentPath=/lib/systemd/system/docker.socket


purchase.getProducts() is empty

I have installed the plugin and successfully run products.init() in my app.component.ts
But when I call getProducts is returns empty array.
  ngOnInit() {
    console.log("Purchases: ", JSON.stringify(purchase));
    purchase.getProducts().then((products: Array<Product>) => {
        console.log("I'm in: ", JSON.stringify(products));
        products.forEach((product: Product) => {
            // does not get here
        });
    });
...
}

Hey @sl1der , have you added your products to the Google Play/iTunes Connect consoles. Also note the plugin currently only supports in-app purchases, so if you have added subscriptions, those will not be listed.

In the init I passed in
"offandpacing_10k_coins"

And have added this product name to the app in the iTunes connect console. It is a consumable product.

Have you followed the instructions for sandbox testing your purchases like explained here?

I think this can be due to an incomplete "Paid Application" contract in iTunes Connect:
http://stackoverflow.com/questions/14957328/is-an-active-paid-applications-contract-required-for-testing-in-app-purchase


feat: rum-api-client v2 with customer specific domain key support

This PR introduces:

rum-api-client v1 to v2 upgrade
rum-api-client@v1 is imported as @adobe/spacecat-shared-rum-api-client-v1 via npm aliases for the legacy audits using older rum-api-client version
Since we currently are not using a "global" domain key for v2, a utility getRUMDomainkey function introduced to fetch domainkeys from AWS for specific pilot customers

Related Issues
Thanks for contributing!

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

v1.18.0
GitHub release

Your semantic-release bot :package::rocket: