Feeding the ServerWatchdog

Right now, if the tick time for any particular tick exceeds a configured amount, the server will report itself as crashed. However, certain plugins, such as world modification plugins, might need over a minute to complete a contiguous operation. In cases like these, the server watchdog would halt the server even though the server didn't really crash. It's simply taking a while to perform an operation.
Therefore I think there should be a way for a plugin to feed the watchdog and indicate that the server is still healthy and should continue to run, despite there being no ticks.
What do you guys think? Is the use case strong enough for something of this level of (in)sanity?

+1 for the title

A plugin should never ever stall the main thread which is the only one the ServerWatchdog cares about.
If your operation takes that amount of time, you need to figure out a mechanism of putting that off thread.

@Zidane which has a big potential for creating concurrency issues

@kinggoesgaming
There are easy strategies for doing thread interchange. @gravityfox knows how.

I do in fact know how. But there are certain operations that involve the main thread that simply cannot be broken up (Read: Pasting 20 million blocks from a schematic that has lots of notification sensitive blocks, like torches) Granted I can cancel all block notifications in the pasting area, but I don't know if I can renotify the blocks later on.

Simply put creates complications where none are needed

@gravityfox I think your main problem is that you shouldn't be trying to paste all 20 million blocks in one go.

Maybe, but i can think of a few cases where breaking up a giant schematic paste wouldn't work quite right.

Closing this as I can never see why pasting that many blocks would be done in one go. That should be broken up and then blocks notified at the end.


link fix

Summary: Missing dependency added in CMakeLists.txt
Type: Fix
Owner: Marcin Wojciechowski
Reviewers: Adam Czynszak, Luke Williamson
Coding Standard Applied: Y
Test Plan: None
Dependencies and Impacts: None
Jira: RIALTO-6

https://jenkins.code.rdkcentral.com/job/github-triggered/24516/ started

https://jenkins.code.rdkcentral.com/job/build-component/60224/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/17109/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/28825/ started.

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/130655/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/130656/


switch 5.15.80 kernel to near-ubuntu-mainline config

This PR changes the 5.15.80 kernel config, following the recipe from the recent commits in https://github.com/neondatabase/autoscaling/pull/623 where I did the same for 6.5.11 with good results for the 0-tps-issue (neondatabase/neon#5678).
Let's see whether we can solve 0-tps-issue on the 5.15.80 kernel by using this config.
Recipe:
(In the docker container set up via the instructions I added in https://github.com/neondatabase/autoscaling/pull/622 )

extract kernel config from the linux-modules deb in ubuntu: https://kernel.ubuntu.com/mainline
open `make menuconfig` and save, without any changes
default hostname + =y instead of =m for isofs
sed -i 's/=m/=n/g' ./neonvm/hack/linux-config-6.5.11; then make menuconfig
uncheck "Automatically sign all modules"
uncheck 'Enable different security model' (SECURITY=n)
  this avoids module signing stuff and other complexity we don't
  care about inside neonvm, like selinux
set empty string for 'Additional X.509 keys for default system keyring'
set empty string for 'X.509 certificates to be preloaded into the system blacklist keyring'

kernel build & push to docker under same 5.15.80 tag: https://github.com/neondatabase/autoscaling/actions/runs/6903092257

just small notice: now vmlinuz about 10Mb, before it was about 6Mb

Yeah, I think this was just used for testing and not intended to be merged, but cc @problame to cofirm

The idea was to merge & ship this if it fixes the 0-tps issue on 5.15.80 (less risk of introducing other regressions).
A few MiBs of kernel don't matter right now (neither as storage nor DRAM footprint).

@problame
I think we can close this, as we moved to 6.1.63 kernel (and it builds in ubuntu:23.10  environment)


Safari highlights icon instead of whole button

On iOS Safari when tapping an icon that's inside a button, the icon gets highlighted instead of the whole button.
When removing the event forwarders the glitch goes away.
I tried to pass the event modifiers preventDefault and stopPropagation and removing all Safari builtin styling for focused elements, but still no luck.
Keyboard events are fine, this is only affected by mouse events.

Can you provide some sample markup code so that I can reproduce the bug?

You should be able to reproduce it from the official examples. For example, I can see it on the Icon-only button.
Notice how the highlighted area is different when tapping the plus sign directly vs tapping anywhere else on the button. The glitch is more conspicuous with a ghost button, but it's still appreciable on a primary button.
I have only seen this issue on iOS. I don't have a MacOS machine at hand at the moment, but on Gnome Web, using the latest version of WebKit, I can't reproduce it, so it may be iOS specific.

Thank you, I'll take a look

@jdnavarro Indeed, on iOS Safari, there is a tap highlight color caused by the forwarded click events, as you suggested.
As a temporary workaround, I would suggest adding this CSS to make the tap color transparent:
svg { -webkit-tap-highlight-color: rgba(0, 0, 0, 0); }

Removing the forwarded events would be a breaking change. However, I do plan to remove the events anyway in the next major release. We already do this in carbon-pictograms-svelte version 11.

The CSS tip works great. I'm glad I won't have to keep around my carbon icons fork anymore :sweat_smile:. Thanks @metonym.


Question on accessing behavior methods from another behavior

Our menu has a reset method that I need to access from a different behavior.
I've successfully done this with the callMethod method
window.USCC.behaviors.callMethod(
        'usccHeader',
        document.querySelector('header'),
        'reset'
      )()

But it seems to only work intermittently and sometimes I get an error that the method is not defined. What is the recommended approach?

From what I can tell it only works locally. Maybe this function is not exposed in a non-local env?

I'd send a custom event from one behavior to the other.
So, in one behavior:
document.dispatchEvent(new CustomEvent('foo', {
  detail: {
    bar: 'baz',
  }
}));

And in another behavior:
import { createBehavior } from '@area17/a17-behaviors';

const otherBehavior = createBehavior('otherBehavior',
  {
    fooMethod(event) {
      // do thing
      console.log(event.detail.bar); // baz
    }
  },
  {
    init() {
      /*
      ...
      */
      document.addEventListener('foo', this.fooMethod, false);
    },
    destroy() {
      document.removeEventListener('foo', this.fooMethod);
    }
  }
);

export default otherBehavior;

Theres an example in the wiki: https://github.com/area17/a17-behaviors/wiki/More-examples#multiple-instances-of-a-behavior-multiple-behaviors-on-a-single-dom-node-send-messages-between-nodes

Ah ok, this makes sense. I will look at the specific ones. Thank you!


only works for button

what am i supposed to do with it if i am restricted to buttons only ????????
better not provide a library at all than incomplete one

Disintegrate works on any non-image element. Closing this as a duplicate of #2


IIIF manifest and canvas cache eviction is asynchronous and could led to unexpected responses

References
Add references/links to any related issues or PRs. These may include:

Fixes #8243

Description
Short summary of changes (1-2 sentences).
Used cache eviction or invalidation methods which guarantee synchronous execution.
List of changes in this PR:

dspace-api/src/main/java/org/dspace/iiif/consumer/CanvasCacheEvictService.java evictSingleValue method uses evictIfPresent method for eviction
dspace-api/src/main/java/org/dspace/iiif/consumer/ManifestsCacheEvictService.java evictSingleValue method uses evictIfPresent method for eviction
dspace-api/src/main/java/org/dspace/iiif/consumer/ManifestsCacheEvictService.java evictAllCacheValues method uses invalidate method for eviction

Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.
The only evidence of impact of reported problem emerged during parallel builds on same machine. It is possible to run in parallel two or more builds and check that IIIFControllerIT.findOneWithCacheEvictionAfterBitstreamUpdate and IIIFControllerIT.findOneWithCacheEvictionAfterItemUpdate are not failing anymore.
Checklist

[X] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
[X] My PR passes Checkstyle validation based on the Code Style Guide.
[X] My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
[X] My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
[ ] If my PR includes new, third-party dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[ ] If my PR modifies the REST API, I've linked to the REST Contract page (or open PR) related to this change.

@mspalti : Would you be willing to give this a quick code review/test, as you wrote much of this IIIF code?

@tdonohue,  sure,  I'm happy to review this.  I'll get to it soon.


[FLINK-9702][State Backends, Checkpointing] Improvement in (de)serialization of keys and values for RocksDB state

What is the purpose of the change
When Flink interacts with state in RocksDB, object (de)serialization often contributes significantly to performance overhead. In particular, currently every state has to serialize the backen's current key before each state access. This PR wants to  reduce this effort by sharing serialized key bytes across all state interactions.
Verifying this change
This change is already covered by existing tests
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

cc @StefanRRichter

Thanks for your help in finishing this issue! If you don't mind, I will add some more commits from my original branch https://github.com/StefanRRichter/flink/commits/serialiation-improvements that are not included here and then finalize and merge this.

@StefanRRichter Thank you for your reply. It's ok for me.


fix notification related eslint errors

Signed-off-by: Tianle Huang<EMAIL_ADDRESS>Description
Run lint and fix complaints. Turn off the async one for now.
Issues Resolved
[List any issues this PR will resolve]
Check List

[x] Commits are signed per the DCO using --signoff

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

Fixing the lint issue of this merged PR https://github.com/opensearch-project/opensearch-dashboards-functional-test/pull/206
One issue which is fixed is the missing definition of BASE_PATH. However, the latest test code of Notification plugin still keeps failing
https://github.com/opensearch-project/opensearch-dashboards-functional-test/runs/6243355097?check_suite_focus=true
cc @seraphjiang

Notification tests are failing consistently. https://github.com/opensearch-project/opensearch-dashboards-functional-test/runs/6243355097?check_suite_focus=true
cc @peterzhuamazon @qreshi

Notification tests are failing consistently. https://github.com/opensearch-project/opensearch-dashboards-functional-test/runs/6243355097?check_suite_focus=true
cc @peterzhuamazon @qreshi

For two of the errors, I think they're happening because the Notification Cypress tests were originally depending on the specs being run in a certain order by chance (because they were defined that way in the cypress.json). This is not conventional and should be changed but will require some test refactoring.
For the third failure, it's not able to find the label data-test-subj="create-channel-description-input" which was added in the PR that updated these tests then backported to branch 2.0. It was passing locally so it's possible that the most recent version of Notifications is not being used here?

For the third failure, it's not able to find the label data-test-subj="create-channel-description-input" which was added in the PR that updated these tests then backported to branch 2.0. It was passing locally so it's possible that the most recent version of Notifications is not being used here?

Thanks @qreshi for checking this. The latest url is parsed to build number 3015. (https://github.com/opensearch-project/opensearch-dashboards-functional-test/runs/6243355097?check_suite_focus=true)
Run wget https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/2.0.0-rc1/latest/linux/x64/tar/dist/opensearch-dashboards/opensearch-dashboards-2.0.0-rc1-linux-x64.tar.gz
--2022-05-01 00:39:35--  https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/2.0.0-rc1/latest/linux/x64/tar/dist/opensearch-dashboards/opensearch-dashboards-2.0.0-rc1-linux-x64.tar.gz
Resolving ci.opensearch.org (ci.opensearch.org)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to ci.opensearch.org (ci.opensearch.org)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: /ci/dbc/distribution-build-opensearch-dashboards/2.0.0-rc1/3015/linux/x64/tar/dist/opensearch-dashboards/opensearch-dashboards-2.0.0-rc1-linux-x64.tar.gz [following]
--2022-05-01 00:39:35--  https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/2.0.0-rc1/3015/linux/x64/tar/dist/opensearch-dashboards/opensearch-dashboards-2.0.0-rc1-linux-x64.tar.gz

@peterzhuamazon I think this is the build number what infra team wants OSD and plugin teams to sign off.
So, the question for Notification team is
if create-channel-description-input shall be included in this release, then you may need to work with infra to trigger a new build.
Or if it shall not be included in this release, then you may need to remove the Cypress test against it.

For the third failure, it's not able to find the label data-test-subj="create-channel-description-input" which was added in the PR that updated these tests then backported to branch 2.0. It was passing locally so it's possible that the most recent version of Notifications is not being used here?

Thanks @qreshi for checking this. The latest url is parsed to build number 3015. (https://github.com/opensearch-project/opensearch-dashboards-functional-test/runs/6243355097?check_suite_focus=true)
Run wget https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/2.0.0-rc1/latest/linux/x64/tar/dist/opensearch-dashboards/opensearch-dashboards-2.0.0-rc1-linux-x64.tar.gz
--2022-05-01 00:39:35--  https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/2.0.0-rc1/latest/linux/x64/tar/dist/opensearch-dashboards/opensearch-dashboards-2.0.0-rc1-linux-x64.tar.gz
Resolving ci.opensearch.org (ci.opensearch.org)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to ci.opensearch.org (ci.opensearch.org)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: /ci/dbc/distribution-build-opensearch-dashboards/2.0.0-rc1/3015/linux/x64/tar/dist/opensearch-dashboards/opensearch-dashboards-2.0.0-rc1-linux-x64.tar.gz [following]
--2022-05-01 00:39:35--  https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/2.0.0-rc1/3015/linux/x64/tar/dist/opensearch-dashboards/opensearch-dashboards-2.0.0-rc1-linux-x64.tar.gz

@peterzhuamazon I think this is the build number what infra team wants OSD and plugin teams to sign off.
So, the question for Notification team is
if create-channel-description-input shall be included in this release, then you may need to work with infra to trigger a new build.
Or if it shall not be included in this release, then you may need to remove the Cypress test against it.

OS 2695 OSD 3015 for the release candidate now.

If OSD build 3015 was done before late Friday, then yeah, it won't have that label. You can edit the 'edits channels' test in channels.spec.js for this repo to pass once the other tests are taken care of if we wish to proceed as-is for now.

If OSD build 3015 was done before late Friday, then yeah, it won't have that label. You can edit the 'edits channels' test in channels.spec.js for this repo to pass once the other tests are taken care of if we wish to proceed as-is for now.

My intention of this PR is to just fix the eslint related issues. Also I am oncall this week and do not have additional bandwidth to handle the actual test logic. Could you help fix the third failure together with the first 2 failures? @qreshi

close given https://github.com/opensearch-project/opensearch-dashboards-functional-test/pull/215


hello, can i change the detectnet to change the camera resolution in v4l2 camera and print the frame size to the console using print?

hello, can i change the detectnet to change the camera resolution in v4l2 camera and print the frame size to the console using print?

Hi @EvaBarret1, you can try setting the camera resolution with --input-width=N and --input-height=N options:   https://github.com/dusty-nv/jetson-inference/blob/master/docs/aux-streaming.md#input-options

and which variable is responsible for the output of what is in 'input'

The output resolution is based on the input resolution, unless you manually add code to resize the input image (i.e. using cudaResize(), cudaCrop(), or similar)

yes, I would like to know which variable in the "Detectnet" code is responsible for displaying this data

i need
gst camera video options

Are you using C++ or Python?   You can call videoSource.GetOptions() and in Python it will return a dict of the options, and in C++ it will return you the videoOptions struct:  https://github.com/dusty-nv/jetson-utils/blob/2ded2cec9de416ecc9e9c5a69f7010593d86817d/video/videoOptions.h
There are also convenience functions in videoSource like videoSource.GetWidth(), GetHeight(), GetFrameRate(), ect:   https://github.com/dusty-nv/jetson-utils/blob/2ded2cec9de416ecc9e9c5a69f7010593d86817d/video/videoSource.h#L293

Hello @dusty-nv,
I have an issue when trying to write options:
camera = videoSource("/work/input_resized.mp4", options= {'CodecType': 'CODEC_CPU'})
display = videoOutput("file://work/output_py.mp4", options= {'CodecType': 'CODEC_CPU'})
I got this error:
 camera = videoSource("/work/input_resized.mp4", options= {'CodecType': 'CODEC_CPU'}) TypeError: 'options' is an invalid keyword argument for this function

Hi @AhmedL99, it would seem like your jetson-inference code is outdated (from before options was added to the Python bindings), or if you are running a container that container needs rebuilt.   Also the correct syntax should be options= {'codecType': 'cpu'}

Thank you @dusty-nv  for your fast response!
This is weird, I cloned the repo a week ago! I will try to rebuild the container then.
What about the --headless flag, is it configurable in Python script?


Implement Users Info

Reference: https://api.slack.com/methods/users.info
Acceptance Criteria:

[ ] Spring Slack Client is extended with given method
[ ] Spring Slack Test Client is extended with given method
[ ] JavaDoc/KDoc is added

Already implemented


java.lang.UnsupportedOperationException: missing SMTLib translation for Map:lookup

Dear Dwight,
When running untyped-kool.k with ex01.kool from exercises/private-members/tests, an UnsupportedOperationException is returned.
Implementation has been sent to your e-mail.
Best,
Michael

If I delete the [function] annotation, the exception disappears. However, my lookup member rules still get stuck.

Can you try to update to the latest version of K and let me know if the most recent changes to the framework make it clearer to you what the problem is? I believe the issue is likely to be that some function rule has failed to apply.

I updated K but the error message does not change.

This is quite strange. Are you sure you updated correctly? The latest version of the K framework should not cause this error unless you are passing the --symbolic-execution flag to krun, which I suspect you are not. What does "krun --version" show?

Closing from lack of activity. Also this was a student question and the semester is over. Please feel free to reopen if you are still interested in this though.


TPM lockout authorization - inaccurate description and misleading terminology

Starting with Windows 10, version 1607, or Windows 11, Windows will not retain the TPM owner password when provisioning the TPM. The password will be set to a random high entropy value and then discarded.

On Windows 10 20H2 and Windows 11 with TPM 2.0, I found that the TPM's ownerAuth and endorsementAuth are both just a 0-byte sequence. Authorization for the SRK (Storage Root Key) is also a 0-byte sequence.
lockoutAuth is stored as a 20-byte sequence encoded in base64 format in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TPM\WMI\Admin\OwnerAuthFull, and this agrees with the statement in the "Important" section:

For Windows 10 versions newer than 1703 the default value for this key is 5. For TPM 2.0, a value of 5 means keep the lockout authorization.

I can confirm that the above values are correct as I am able to use them to successfully change the authorization values to my own ones. So none of the authorization values here are unknown and/or discarded.
In addition, the page talks about "owner password", giving the impression that it's referring to ownerAuth. However it goes on to state:

The TPM owner password allows the ability to enable, disable, or clear the TPM without having physical access to the computer, ... The TPM owner password also allows manipulation of the TPM dictionary attack logic.

Clearing the TPM and manipulating the TPM dictionary attack logic requires lockoutAuth, not ownerAuth (as per TPM Library Spec).

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

ID: 589107e3-caf8-797e-391e-41457437e5c1
Version Independent ID: acce4c69-e822-f7e9-8341-06b6d3061c57
Content: Change the TPM owner password (Windows) - Windows security
Content Source: windows/security/information-protection/tpm/change-the-tpm-owner-password.md
Product: m365-security
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@Dansimp Please help us in resolving this issue. Thanks

@aczechowski Please help us in resolving this issue. Thanks

This article has been removed (it was orphaned anyway), so I'm closing the issue.


Messaging test shouldn't use an internal util class from Undertow as …

…now it's gone

Linux with security manager Build 1636 is now running using a merge of ccbeab84c3a700f317c64e0441ec7205ce37fe14

Windows Build 1810 is now running using a merge of ccbeab84c3a700f317c64e0441ec7205ce37fe14

Linux Build 6735 is now running using a merge of ccbeab84c3a700f317c64e0441ec7205ce37fe14

Linux with security manager Build 1636 outcome was SUCCESS using a merge of ccbeab84c3a700f317c64e0441ec7205ce37fe14
Summary: Tests passed: 856, ignored: 322 Build time: 0:06:21

Linux Build 6735 outcome was SUCCESS using a merge of ccbeab84c3a700f317c64e0441ec7205ce37fe14
Summary: Tests passed: 2880, ignored: 395 Build time: 0:47:32

Windows Build 1810 outcome was SUCCESS using a merge of ccbeab84c3a700f317c64e0441ec7205ce37fe14
Summary: Tests passed: 2880, ignored: 395 Build time: 0:48:57


build-failing

The current state of the project is experiencing a build failure, hindering the successful compilation and deployment of the project. This issue needs urgent attention to ensure the project's continued development and stability.

fixed Unit Testing


委员申请：youyou

introduce：I have been engaged in the Internet e-commerce industry for more than two years, and have worked as PM project for many times during this period, led the team to fight many battles, and had certain project experience in the development of DAPP
github: https://github.com/xiaozhu001
参与Conflux项目：
https://github.com/Conflux-Chain/conflux-nft-contract
本人愿意承担一年期的 技术委员会 的治理工作。

+1


High Sierra 10.13.4 command + shift not refering

in mac high sierra 10.13.4
I want to use command + shift for switch between language input like windows but this simple code not working:
https://gist.github.com/vsalex/eac8c27bc7cf428ba8e19671cdb34142
I think apple not allow to use command + shift for doing some thing.
any solution?

Your code works on my machine.
Can you confirm the configuration changes your left_command + left_shift on EventViewer?


Missing primary dice function

This dice bot is lacking a primary dice rolling function for narrative role-play gaming systems.
Cultural significance: https://en.wikipedia.org/wiki/Fudge_(role-playing_game_system)#Fudge_dice

You can get Fudge functionality by using "4d3-8".
In this case you're -2 from each d3.  So a roll of 1 is 1-2 or  a "-". A roll of 2 is 2-2 or a roll of " ". Finally, a roll of 3 is 3-2 or a roll of "+". The final given total will be the sum of "-" "+" and " " that you roll.


transitous: Move Latvia to anyCoverage

We are missing LTG Link services there, so shouldn't claim complete data

LGTM


Add This Was My Life by Megadeth

Song Name
This Was My Life
Artist Name
Megadeth
Source
Youtube
Youtube Link
https://www.youtube.com/watch?v=muoHUavIyMU
Direct File Link
No response
Song ID
467339
Start Offset [ms]
11000
Extra
Created from Auto Nong.
Created for level: 10565740

reject
apparently the song and level id linked to bloodbath so is unrelated


Add details about integer overflow

CC #9

I asserted that arithmetic overflow indicates programmer error, which is stronger than the claim in RFC 560. However, I do point users at the wrapping_xxx inherent methods for programmers to annotate and explicitly ask for wrapping arithmetic.
I remained confused after reading the RFC about Rust's overflow semantics. It seemed to indicate two's complement, wrapping overflow is the default if the compiler doesn't insert dynamic checks, but it also indicated an implementation could insert static or dynamic checks at any time to panic or prevent this behavior, excepting of course uses of the wrapping primitives.

r? @steveklabnik

@steveklabnik ping

Hey @mrhota sorry about this.

I remained confused after reading the RFC about Rust's overflow semantics. It seemed to indicate two's complement, wrapping overflow is the default if the compiler doesn't insert dynamic checks, but it also indicated an implementation could insert static or dynamic checks at any time to panic or prevent this behavior, excepting of course uses of the wrapping primitives.

My understanding is that it's like this:

overflow is a "programmer error", that is, not UB, but not well-formed.
In the case of overflow:

When debug_assertions are enabled, implementations are required to panic at runtime.
When they are not enabled, implementations are allowed to panic or not panic.
If they choose to not panic, overflow is well-defined as two's compliment overflow.

If overflow is a desired behavior, then using the wrapper types is the proper way to do it.

So, it seems like this PR is correct, though maybe not complete, exactly. Thoughts?

@steveklabnik that's very helpful. I'll clarify what I have written.

@mrhota ping!

@steveklabnik OK, give these changes a shot. I hope it clarifies things

Looks great, thank you!


Migrate to latest zola API

The new taxonomies api (in zola v0.5.0) uses page.taxonomies instead of page.tags

Deploy failed maybe because of netlify uses an old version of gutenburg?

https://github.com/getzola/zola/blob/v0.5.1/netlify.toml

Now this deploy issue is fixed. The tags are available in pages again.
See https://deploy-preview-15--zola-even.netlify.com/some-other-article/


⚠ Processors has degraded performance

In 5675aac, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 114 ms

Resolved: Processors performance has improved in 7464f02.


[DO NOT MERGE til 786xx] ff relnotes for 786xx release

When this release is a go, UPDATE DATE (currently XX) on release notes before merging

Preview environment: https://hdh.pr.harness.io/pr-891

Preview environment: https://hdh.pr.harness.io/pr-891

Preview environment: https://hdh.pr.harness.io/pr-891

Preview environment: https://hdh.pr.harness.io/pr-891


Add go to integration testsuite

Sorry, opened the PR on the wrong repo. Just wanted to test against my fork for now :)


Hermes telemetry requirements

Crate
ibc and ibc-telemetry
Summary
Following from #868 and recent discussions, we need to expand on the metrics we expose via our telemetry mechanism.
Problem Definition
We have been talking about parsing log files to obtain information regarding metrics that could easily be tracked by our telemetry system (i.e. Prometheus).
Proposal
Let's:

Use this issue to discuss and gather all of the metrics that would be useful for us to expose.
List them in the Acceptance Critera section of this issue.
Prioritize the metrics.
Implement as many of them as we can according to priority. Ideally only one metric per PR to ensure quick review.

Acceptance Criteria
When the following metrics are exposed:

Done
Metric name
Description
Meter type

error_websocket_reconnect
Number of times Hermes had to reconnect to the WebSocket endpoint
Counter

time_to_relay
Interval between when Hermes receives an event until the messages in the event are sent to the destination chain, per message
ValueRecorder

tx_failed
Total number of failed txs processed
Counter

tx_retry_failed
Total number of failed retries when submitting txs
Counter

trusting_periods_left
How many trusting_periods are left (metrics on whether an update is required)
UpDownCounter

relay_chains_num
Number of chains the relay is connecting to
UpDownCounter

rpc_query_count
Number of RPC queries issued to chain
Counter

rpc_query_latency
Latency of RPC queries issued to chain
ValueRecorder

grpc_query_count
Number of gRPC queries issued to chain
Counter

grpc_query_latency
Latency of gRPC queries issued to chain
ValueRecorder

✅
tx_msg_ibc_recv_packet
Total number of IBC packets received
Counter

✅
tx_msg_ibc_acknowledge_packet
Total number of IBC packets acknowledged
Counter

✅
ibc_timeout_packet
Total number of IBC timeout packets
Counter

✅
ibc_client_misbehaviour
Total number of client misbehaviours
Counter

tx_successful
Total number of successful txs processed
Counter

tx_count
Total number of txs processed
Counter

error_rpc
Number of RPC errors encountered
Counter

ibc_transfer_send
Total number of IBC transfers sent from a chain (source or sink)
Counter

ibc_transfer_receive
Total number of IBC transfers received to a chain (source or sink)
Counter

relay_clients_num
Number of clients the relay is connecting to
UpDownCounter

relay_connects_num
Number of connections the relay is connecting to
Counter

relay_channels_num
Number of channels the relay is connecting to
Counter

UP
Program exit flag
ValueRecorder

For Admin Use

[x] Not duplicate issue
[x] Appropriate labels applied
[x] Appropriate milestone (priority) applied
[x] Appropriate contributors tagged
[x] Contributor assigned/self-assigned

Closing in favor of #2112 which will take a more fine-grained, incremental approach to adding metrics.


VM mesh-expansion does not work with versioned (revision) Istiod

Bug description
Virtual machine mesh expansion is not possible on a versioned Istio installation e.g.: 1-6-8
The same setup works flawlessly when Istio is not installed using revisions.
2020-09-07T09:01:46.972433Z     info    Subchannel Connectivity change to TRANSIENT_FAILURE
2020-09-07T09:01:46.972487Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc000ad91b0, {TRANSIENT_FAILURE connection error: desc = "transport: authentication handshake failed: read tcp <IP_ADDRESS>:60072-><IP_ADDRESS>:15012: read: connection reset by peer"}
2020-09-07T09:01:46.972520Z     info    Channel Connectivity change to TRANSIENT_FAILURE
2020-09-07T09:03:25.361349Z     info    Subchannel Connectivity change to CONNECTING
2020-09-07T09:03:25.361440Z     info    Subchannel picks a new address "istiod.istio-system.svc:15012" to connect
2020-09-07T09:03:25.361861Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc000ad91b0, {CONNECTING <nil>}
2020-09-07T09:03:25.361890Z     info    Channel Connectivity change to CONNECTING
2020-09-07T09:03:25.364244Z     info    grpc: addrConn.createTransport failed to connect to {istiod.istio-system.svc:15012  <nil> 0 <nil>}. Err: connection error: desc = "transport: authentication handshake failed: EOF". Reconnecting...
2020-09-07T09:03:25.364266Z     info    Subchannel Connectivity change to TRANSIENT_FAILURE
2020-09-07T09:03:25.364317Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc000ad91b0, {TRANSIENT_FAILURE connection error: desc = "transport: authentication handshake failed: EOF"}
2020-09-07T09:03:25.364324Z     info    Channel Connectivity change to TRANSIENT_FAILURE
2020-09-07T09:05:38.836288Z     info    Subchannel Connectivity change to CONNECTING
2020-09-07T09:05:38.836376Z     info    Subchannel picks a new address "istiod.istio-system.svc:15012" to connect
2020-09-07T09:05:38.836704Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc000ad91b0, {CONNECTING <nil>}
2020-09-07T09:05:38.836718Z     info    Channel Connectivity change to CONNECTING
2020-09-07T09:05:38.838558Z     info    grpc: addrConn.createTransport failed to connect to {istiod.istio-system.svc:15012  <nil> 0 <nil>}. Err: connection error: desc = "transport: authentication handshake failed: EOF". Reconnecting...
2020-09-07T09:05:38.838608Z     info    Subchannel Connectivity change to TRANSIENT_FAILURE
2020-09-07T09:05:38.838672Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc000ad91b0, {TRANSIENT_FAILURE connection error: desc = "transport: authentication handshake failed: EOF"}
2020-09-07T09:05:38.838680Z     info    Channel Connectivity change to TRANSIENT_FAILURE

Affected product area (please put an X in all that apply)
[ ] Docs
[x ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ x] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[x ] Virtual Machine
[ ] Multi Control Plane
Expected behavior
Mesh expansion works on a revision install like on a non revision install
Steps to reproduce the bug

install Istio  as revision -r 1-6-8
create certs
install sidecar .deb on VM
set /etc/hosts
place certs
start service

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
client version: 1.6.8
control plane version: 1.6.8
data plane version: 1.6.8 (2 proxies)

Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.8", GitCommit:"9f2892aab98fe339f3bd70e3c470144299398ace", GitTreeState:"clean", BuildDate:"2020-08-13T16:12:48Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.13-gke.1", GitCommit:"688c6543aa4b285355723f100302d80431e411cc", GitTreeState:"clean", BuildDate:"2020-07-21T02:37:26Z", GoVersion:"go1.13.9b4", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
cat <<EOF > values.yaml
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  components:
    ingressGateways:
      - name: istio-ingressgateway
        enabled: true
        k8s:
          service:
            type: NodePort
  values:
    global:
      meshExpansion:
        enabled: true
EOF

curl -L https://istio.io/downloadIstio | ISTIO_VERSION=1.6.8 sh -

cd istio-1.6.8
bin/istioctl install -f ../values.yaml -r 1-6-8

Environment where bug was observed (cloud vendor, OS, etc)
Cluster: GCP/GKE 1.16.13-gke.1
VM: ubuntu-1804

Looks like it's trying to connect to istiod service - if using  revision the service name will be different and you'll need to modify the config to point to this service

@howardjohn, I assumed that too and tried to set the Pilot env. var as well as the ca_address in the cluster.env.
Then you an see the istiod-1-6-8.istio-system.svc set as discoveryAddress, but the handshake still targets istiod.istio-system.svc and fails.
Is this hard coded somewhere, or how can I override this?

It would be great if we can get some details on this, we are using VM mesh expansion heavily since Istio 1.0.
It was pointed out that the recommended way of upgrading is to do revisions, but if that breaks the mesh expansion option it should get pointed out somewhere.
That would actually be a blocker for revision upgrades in expanded meshes.
If there are special steps to take to get expansions running with revisions, it would also make sense to extend the current VM mesh expansion documentation with a revision section, to reflect those needed steps.

@irisdingbj , I just lined you in because you gave very valuable information that last time we had a similar topic.
@howardjohn,
How can we confirm if VM mesh expansion is currently (not) working with a revision of Istiod?
It is an important topic for us, as it will influence our future upgrade strategy:

If we can go for the recommended way of doing revisions updates.
Or if we are bound to do in place upgrades as revisions are may not supported for VMs in expanded meshes.

It would be nice if we can get some feedback on this, also to verify that isn't a simple configuration issue or an error on our side.
Best regards

@peter-fe I haven't looked into this, but there is nothing fundamentally blocking revisions and VMs. The only difference on the VM is a different address is exposed. We likely just need to fix some docs or make some tiny config tweaks.

@howardjohn,
I'm assuming the same, but changing the pilot address to reflect the revision service name had no impact. I also tried recreating the certs to match the revision host name and setting a host record with the revision service name. It seems like connectivity is given but the cert handshake fails with that awkward "EOF" error.

@howardjohn,
I got it working finally, but it seems to be a bug though.
When creating a revisioned Istiod installation the service name including the revision e.g. istiod-1-6-8 doesn't get reflected everywhere throughout the manifests.
In this case, causing the VM expansion issues, the destination rule "meshexpansion-dr-istiod" and the virtual service "meshexpansion-vs-istiod" are referring to "istiod.istio-system.svc.cluster.local" instead of "istiod-1-6-8.istio-system.svc.cluster.local".
Everything starts working, as soon as this gets adjusted to reflect the revision.
DestinationRule & VirtualService created by istioctl install -f ../values-1-6.yaml -r 1-6-8
apiVersion: networking.istio.io/v1beta1
kind: DestinationRule
metadata:
  labels:
    install.operator.istio.io/owning-resource: installed-state-1-6-8
    install.operator.istio.io/owning-resource-namespace: istio-system
    operator.istio.io/component: IngressGateways
    operator.istio.io/managed: Reconcile
    operator.istio.io/version: 1.6.8
    release: istio
  name: meshexpansion-dr-istiod
  namespace: istio-system
spec:
  host: istiod.istio-system.svc.cluster.local
  trafficPolicy:
    portLevelSettings:
    - port:
        number: 15012
      tls:
        mode: DISABLE
    - port:
        number: 15017
      tls:
        mode: DISABLE
---
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  labels:
    install.operator.istio.io/owning-resource: installed-state-1-6-8
    install.operator.istio.io/owning-resource-namespace: istio-system
    operator.istio.io/component: IngressGateways
    operator.istio.io/managed: Reconcile
    operator.istio.io/version: 1.6.8
    release: istio
  name: meshexpansion-vs-istiod
  namespace: istio-system
spec:
  gateways:
  - meshexpansion-gateway
  hosts:
  - istiod.istio-system.svc.cluster.local
  tcp:
  - match:
    - port: 15012
    route:
    - destination:
        host: istiod.istio-system.svc.cluster.local
        port:
          number: 15012
  - match:
    - port: 15017
    route:
    - destination:
        host: istiod.istio-system.svc.cluster.local
        port:
          number: 443

Working versions after manual adjustment
apiVersion: networking.istio.io/v1beta1
kind: DestinationRule
metadata:
  labels:
    install.operator.istio.io/owning-resource: installed-state-1-6-8
    install.operator.istio.io/owning-resource-namespace: istio-system
    operator.istio.io/component: IngressGateways
    operator.istio.io/managed: Reconcile
    operator.istio.io/version: 1.6.8
    release: istio
  name: meshexpansion-dr-istiod
  namespace: istio-system
spec:
  host: istiod-1-6-8.istio-system.svc.cluster.local
  trafficPolicy:
    portLevelSettings:
    - port:
        number: 15012
      tls:
        mode: DISABLE
    - port:
        number: 15017
      tls:
        mode: DISABLE
---
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  labels:
    install.operator.istio.io/owning-resource: installed-state-1-6-8
    install.operator.istio.io/owning-resource-namespace: istio-system
    operator.istio.io/component: IngressGateways
    operator.istio.io/managed: Reconcile
    operator.istio.io/version: 1.6.8
    release: istio
  name: meshexpansion-vs-istiod
  namespace: istio-system
spec:
  gateways:
  - meshexpansion-gateway
  hosts:
  - istiod-1-6-8.istio-system.svc.cluster.local
  tcp:
  - match:
    - port: 15012
    route:
    - destination:
        host: istiod-1-6-8.istio-system.svc.cluster.local
        port:
          number: 15012
  - match:
    - port: 15017
    route:
    - destination:
        host: istiod-1-6-8.istio-system.svc.cluster.local
        port:
          number: 443

@howardjohn,
Any news on this, as it seem to be a bug, can we get that confirmed/triaged?

And another one get's rotten.
Really sad that obvious bugs get ignored that way and it's no single case. We see that happen regulary in the past year. Why users should invest time in documenting issues when they get ignored anyways? On the long run people will stop contributing, and well ... there it goes

@peter-fe Sorry, about the bot marking it as stale. I removed the label now.

@ramaraochavali, could you remove the stale label again pls?
Or was there any progress adding the missing resources?


Release Year on y axis?

Would be really cool if we could see the release dates alongside the browser versions. May help with better judgement of what features to implement.

Duplicate of #202. Personally I feel the amount a version is being used (e.g. use the usage relative mode or the slider under Settings) is better for dictating whether or not it should be supported.


Extensions not loading in vscode 1.89.1

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

Just installed vscode April release and extensions tab not loading the extensions.
The extensions are loading when I reinstalled version 1.87.0 and I dont know why

VS Code Version:
OS Version:

/needsMoreInfo

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

Vscode version 1.89.1
Os version Windows_NT 10.0.19045
On Fri, May 24, 2024, 10:15 PM John Murray @.***> wrote:

VS Code Version:
OS Version:

/needsMoreInfo
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/213428#issuecomment-2130432616,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATMRIFTPHQKIMFHJF6SIMQLZD63YJAVCNFSM6AAAAABIIIV2V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZQGQZTENRRGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Can you please share following log

F1 > Open View... > Shared

Same for me, updated from 1.83 to 1.89 and extensions are not loading in the extensions tab.
VS Code Version: 1.89.1
OS Version: MacOS Sonoma 14.1.1 (apple silicon)

Can you please share following log

F1 > Open View... > Shared

@sandy081 can you elaborate on how to share the log? When I open the F1 menu I see this

After entering "Open View" there's no "Shared"

Can you please share the screenshot of Open View list?

I ended up reinstalling vscode and now extensions are loading and "Shared" appears under "Open View"

Ok. I believe a Restart would have worked instead of Reinstalling. I also suspect you are having similar issue like this - https://github.com/microsoft/vscode/issues/212664


fix: fix exporting of dharma as default

@chrismin can you both export it as a node module an es6 module?

@saturnial this accomplishes that; i can explain more thoroughly in person.


Brought up a 2-node cluster, two different clusters...

I brought up a 2-node cluster using the same cloud-config file and ended up with two different clusters somehow. Here's my cloud-config. When I fleetctl list-machines on either of the nodes, they only show that specific machine in the cluster, not both. I checked the output of journalctl -u etcd on both machines and they both show the same discovery token, but they both state they changed themselves to the leader. Any help would be greatly appreciated.

@iamthemuffinman Setting up a two node cluster is not a good idea. See this guide for more details: https://coreos.com/docs/cluster-management/scaling/etcd-optimal-cluster-size
As to why you are having this issue, I need to take a look at the cloud configs and maybe the logs from both etcd machines. Happy to help figure this out in IRC too.

Doh! Didn't see that. I'm gonna rebuild the cluster using 3 nodes this time and see if I still have the issue. I'll report back later today.


Add the ability to set a refresh token

I am not sure if I am missing something...but I don't see an option to set a refresh token. I noticed that the node version offers that option. Considering that the spotify api requires authentication for all api access this would be great to have since the keys expire after an hour.
reference: https://github.com/thelinmichael/spotify-web-api-node

I also notice that.
I think that the web-api-js cannot have it because it is impossible to set a refresh token in the client side.

I'm fairly certain @igorPhelype is correct.
To make that request, you need send your client_id and client_secret. We don't want to expose those values in the front end because of security concerns. You can't retrieve a token from the front-end for the exact same reason.

If you're building a front-end heavy/ single page app, one possible solution would be to have a back end microservice handle this auth stuff for you, and then pass your front end the access token.

@orangemooncreative,
Take a look at this gist:
https://gist.github.com/igorPhelype/68239ecab9afcc50230ce0c61c3bac2f
And I did this simple webapp just for learning react, you can see the implementation:
https://github.com/igorPhelype/Spotigorfy
You can use my method, or follow @ntaylor89's recomendation, because I honestly think that my aproach is not that perfect.

Nice. I also have been building a webapp that uses spotify to learn React.
Note that Spotify's API allows 3 authentication types (all from the OAuth2 standard)

Authorization Code flow
Client Credentials flow
Implicit Grant

The Authorization code flow has to happen in the backend. It will allow you to access a users data, and gives you a way of extending the token use after it expires.
The Client credentials flow still happens in the backend, but doesn't require users to login. This allows you to get faster API rates and access the public data not available without authentication. You can still get refresh tokens. But you can't access users data.
The Implicit grant flow happens in the front end. Users login and you can get access to their personal data. However, there is now way to extend the token. When it expires, they will have to login again.
That's why you see this limitation: It's dictated by Spotify (who is following the OAuth2 Standard).
My guess is that you're using the implicit grant flow, so you can get the initial token from this repo, but you'll never be able to get a refresh token.

If you need longer access to the api without re-authentication, then you'll need to either use the Authorization Code Flow or the Client Credentials Flow in the backend.
For my side-project, I need users to login, so I went the the Authorization Code flow. I've been working on a microservice to make this a bit easier: https://github.com/ntaylor89/micro-spotify
The idea is that you spin up that microservice on now.sh, point users to it for authentication, and you'll get back an access token. I still haven't implemented a refresh flow yet, but you can use it as an example of how to do auth in the back end.

Thank you very much everyone who helped supporting @orangemooncreative! As mentioned, this library is intended to be used client-side and it doesn't support refreshing the token. https://github.com/thelinmichael/spotify-web-api-node is the option for server-side token exchange if you are using node.
I'll close this ticket. Feel free to reopen it if there was something missing.

I came across this closed subject, because I had the same question. Still I need to get something clear.
My current idea so to do the authorization flow (will use PHP for this) and in that way obtain an accessToken and refreshToken.
Well that accessToken I can use of course within this wrapper, I was thinking to store it in sessionStorage.
However why can't I store the refreshToken also in sessionStorage, and do a client site request to obtain a new assessToken? What is the added security risk in this case (suppose I use https and everything)?
My work around would be to store the refreshToken in a PHP session and request a new token in that way. But I'm interested why it wouldn't be possible client side.

@kasperkamperman ever found the answer to that question ?

I came across this closed subject, because I had the same question. Still I need to get something clear.
My current idea so to do the authorization flow (will use PHP for this) and in that way obtain an accessToken and refreshToken.
Well that accessToken I can use of course within this wrapper, I was thinking to store it in sessionStorage.
However why can't I store the refreshToken also in sessionStorage, and do a client site request to obtain a new assessToken? What is the added security risk in this case (suppose I use https and everything)?
My work around would be to store the refreshToken in a PHP session and request a new token in that way. But I'm interested why it wouldn't be possible client side.

I think you can do that indeed. I'm no security specialist. But with https
and other measures it wont harm I think.
On Mon, 30 Dec 2019, 10:20 Daniel<EMAIL_ADDRESS>wrote:

@kasperkamperman https://github.com/kasperkamperman ever found the
answer to that question ?
I came across this closed subject, because I had the same question. Still
I need to get something clear.
My current idea so to do the authorization flow (will use PHP for this)
and in that way obtain an accessToken and refreshToken.
Well that accessToken I can use of course within this wrapper, I was
thinking to store it in sessionStorage.
However why can't I store the refreshToken also in sessionStorage, and do
a client site request to obtain a new assessToken? What is the added
security risk in this case (suppose I use https and everything)?
My work around would be to store the refreshToken in a PHP session and
request a new token in that way. But I'm interested why it wouldn't be
possible client side.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JMPerez/spotify-web-api-js/issues/63?email_source=notifications&email_token=AANN22ALUV5GQ7IEZGC4G43Q3HYP7A5CNFSM4DN6GT72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH2JHGI#issuecomment-569676697,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANN22DLH2IJYJ7CCQARFS3Q3HYP7ANCNFSM4DN6GT7Q
.

If you want to do it secure, you could use a proxy. So run all the calls
over your own server, if the token is expired request a new one with the
refresh token you have stored server side. Im using the PHP spotify library.
https://github.com/jwilsson/spotify-web-api-php
On Mon, 30 Dec 2019, 10:20 Daniel<EMAIL_ADDRESS>wrote:

@kasperkamperman https://github.com/kasperkamperman ever found the
answer to that question ?
I came across this closed subject, because I had the same question. Still
I need to get something clear.
My current idea so to do the authorization flow (will use PHP for this)
and in that way obtain an accessToken and refreshToken.
Well that accessToken I can use of course within this wrapper, I was
thinking to store it in sessionStorage.
However why can't I store the refreshToken also in sessionStorage, and do
a client site request to obtain a new assessToken? What is the added
security risk in this case (suppose I use https and everything)?
My work around would be to store the refreshToken in a PHP session and
request a new token in that way. But I'm interested why it wouldn't be
possible client side.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JMPerez/spotify-web-api-js/issues/63?email_source=notifications&email_token=AANN22ALUV5GQ7IEZGC4G43Q3HYP7A5CNFSM4DN6GT72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH2JHGI#issuecomment-569676697,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANN22DLH2IJYJ7CCQARFS3Q3HYP7ANCNFSM4DN6GT7Q
.


AnnAssign with typing.List fails for all langs except Julia

After basic annassign syntax fixes with https://github.com/adsharma/py2many/pull/71, the next challenge is more typical cases such as using typing.List in an AnnAssign, which causes compilation problems on all languages except Julia.
from typing import List

def show():
    items : List[str] = ["a", "b", "c"]
    for val in items:
    	print(val)

if __name__ == "__main__":
    show()

Julia happy processes items : List[str] = ["a", "b", "c"]
Rust error:
error: expected one of `!`, `(`, `+`, `::`, `;`, `<`, or `=`, found `[`
 --> for.rs:4:16
  |
4 | let items: List[str] = vec!["a", "b", "c"];
  |                ^ expected one of 7 possible tokens

dart:
  ╷
5 │ List[str] items = ["a", "b", "c"];
  │         ^
  ╵
Info: Compiling without sound null safety
cases/for.dart:5:6: Error: Getter not found: 'str'.
List[str] items = ["a", "b", "c"];
     ^^^
cases/for.dart:5:9: Error: Expected ';' after this.
List[str] items = ["a", "b", "c"];
        ^

etc,etc
If just using items: List = ... , dart and julia are happy.  But others are not.
e.g. rust
error[E0412]: cannot find type `List` in this scope
 --> for.rs:4:16
  |
4 |     let items: List = vec!["a", "b", "c"];
  |                ^^^^ not found in this scope

https://paste.ubuntu.com/p/KjYXshGpnP/ fixes rust for List case.
For List[int] we will need to special case around visit_Assign where
List and int are separately type mapped and combined into Vec<int>.
-Arun
On Fri, Apr 16, 2021 at 11:53 AM John Vandenberg @.***>
wrote:

After basic annassign syntax fixes with #71
https://github.com/adsharma/py2many/pull/71, the next challenge is more
typical cases such as using typing.List in an AnnAssign, which causes
compilation problems on all languages except Julia.
from typing import List
def show():
items : List[str] = ["a", "b", "c"]

for val in items:

	print(val)

if name == "main":
show()

Julia happy processes items : List[str] = ["a", "b", "c"]
Rust error:
error: expected one of !, (, +, ::, ;, <, or =, found [
--> for.rs:4:16
|
4 | let items: List[str] = vec!["a", "b", "c"];
|                ^ expected one of 7 possible tokens
dart:
╷
5 │ List[str] items = ["a", "b", "c"];
│         ^
╵
Info: Compiling without sound null safety
cases/for.dart:5:6: Error: Getter not found: 'str'.
List[str] items = ["a", "b", "c"];
 ^^^

cases/for.dart:5:9: Error: Expected ';' after this.
List[str] items = ["a", "b", "c"];
    ^

etc,etc
If just using items: List = ... , dart and julia are happy. But others
are not.
e.g. rust
error[E0412]: cannot find type List in this scope
--> for.rs:4:16
|
4 |     let items: List = vec!["a", "b", "c"];
|                ^^^^ not found in this scope
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/adsharma/py2many/issues/72, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFA2A7LZHV6FSPKJ3EGG63TJCBRLANCNFSM43CBO7MQ
.


Update links demo.opengeo.org to geoserver.ics.perm.ru

Please update links in tasmania example. It took me a while to recognize that links in an example are different from a readme file.
From: http://demo.opengeo.org/geoserver/ows to: http://geoserver.ics.perm.ru/geoserver/ows

It is mistake


add flag to forward specific env vars (while isolation remains enabled)

The flag is called -Zmiri-env-forward=<var>, but I am open to bikeshedding. ;)

Sgtm. Although include would be more consitent, it makes very little sense on its own. forwars is very clear
@bors r+

:pushpin: Commit ceec2b3cebab9072beccd65c678b5bc51f830b5d has been approved by oli-obk

:hourglass: Testing commit ceec2b3cebab9072beccd65c678b5bc51f830b5d with merge 926af6493beca5abc0ea0f8ce2a1894fdc103513...

:sunny: Test successful - checks-actions
Approved by: oli-obk
Pushing 926af6493beca5abc0ea0f8ce2a1894fdc103513 to master...


Improved code quality & added Tribonacci.java

Added new Tribonacci.java file.
Added Switch Case statement to Lucas.java to improve readability and speed.
Divide class code into separate methods in Lucas.java, Polite.java, and Fermat.java.
Added try/catch blocks to catch InputMismatchExceptions in Lucas.java, Polite.java, and Fermat.java.

Thank you for your contributions


Crew-3 update info

Kayla Barron will be the fourth member. This is the patch.

Still missing Barron and patch. Booster should be B1067 (maybe it will be used by Inspiration4)

Whoops, missed that first update

No probs Jake!


[Feature] Show the project build log in Web UI

What problem does this PR solve?
Issue Number: close #1578
Problem Summary:
Keep the latest build log in the streampark workspace dir, and web UI always can view the latest build log. It's very useful when the build is failed.
What is changed and how it works?
Proposal: xxx
Feel free to ping committers for the review!
Contribution Checklist

Make sure that the pull request corresponds to a GITHUB issue.

Name the pull request in the form "[Feature] [component] Title of the pull request", where Feature can be replaced by Hotfix, Bug, etc.

Minor fixes should be named following this pattern: [hotfix] [docs] Fix typo in README.md doc.

Purpose of this pull request
Keep the latest build log in the streampark workspace dir, and web UI always can view the latest build log. It's very useful when the build is failed.

Looks good, Thanks for your contribution, I'll review later

Hi @lvshaokang , thanks for your review. I have addressed all comments, please help take a look in your free time.

The original way is that the log can be transmitted to the front-end in real-time through websocket for the front-end to view, which is very useful for the task build. But the current way directly cancels the function of logs that can be viewed in real-time, this not we want. The way we expect is:

@1996fanrui +1. As i can see,  the current way seem to have lost the ability to automatically view real-time build logs, which is not expected.
About this point, i thought of 2 solutions to discuss:
1.Keep the origin way(websocket) to view logs, meanwhile, flush the log stream to disk.
2.Use the scroll way to view logs, if not end, continue reading, it may have a short delay, but i think it's within the acceptable.
what do you think of it?
cc @wolfboys @MonsterChenzhuo @xinzhuxiansheng

The original way is that the log can be transmitted to the front-end in real-time through websocket for the front-end to view, which is very useful for the task build. But the current way directly cancels the function of logs that can be viewed in real-time, this not we want. The way we expect is:

@1996fanrui +1. As i can see, the current way seem to have lost the ability to automatically view real-time build logs, which is not expected. About this point, i thought of 2 solutions to discuss:
1.Keep the origin way(websocket) to view logs, meanwhile, flush the log stream to disk.
2.Use the scroll way to view logs, if not end, continue reading, it may have a short delay, but i think it's within the acceptable.

Hi @wolfboys @lvshaokang , thanks for your sincere review. It really affects the user experience. I have addressed the problem using the solution 2: When the project is building, the incremental log is queried according to the offset every 500 milliseconds.

The original way is that the log can be transmitted to the front-end in real-time through websocket for the front-end to view, which is very useful for the task build. But the current way directly cancels the function of logs that can be viewed in real-time, this not we want. The way we expect is:

@1996fanrui +1. As i can see, the current way seem to have lost the ability to automatically view real-time build logs, which is not expected. About this point, i thought of 2 solutions to discuss:
1.Keep the origin way(websocket) to view logs, meanwhile, flush the log stream to disk.
2.Use the scroll way to view logs, if not end, continue reading, it may have a short delay, but i think it's within the acceptable.

Hi @wolfboys @lvshaokang , thanks for your sincere review. It really affects the user experience. I have addressed the problem using the solution 2: When the project is building, the incremental log is queried according to the offset every 500 milliseconds.

looks good

Thanks for your hard work, I have tested it, it's ok


My very descriptive commit

Some text, such as this adds a demo script that prints hello world

Closed as a demo PR during the hackathon


Migrate to pydantic v2

Overview
We migrate pydantic from v1 to v2.
Supported Versions and Compatibility

⚠ Important Note:

Pydantic v1 will not be supported for dbt 1.9 or later.
To parse dbt 1.9 or later, please migrate your code to pydantic v2.
We will reassess version compatibility upon the release of pydantic v3.

Version
Supported dbt Version
Supported pydantic Version

0.7
dbt 1.5 to 1.8
pydantic v2

0.6
dbt 1.5 to 1.8
pydantic v1

0.5
dbt 1.5 to 1.7
pydantic v1

@OnkarVO7 I haven't caught up with updates of OpenMetadata for a while. But, if it still use the package, please make sure the compatibility in pydantic. We won't support pydantic v1 any more after v0.7.0.
https://github.com/yu-iskw/dbt-artifacts-parser?tab=readme-ov-file#supported-versions-and-compatibility
https://github.com/yu-iskw/dbt-artifacts-parser/releases/tag/v0.7.0

Thanks for informing @yu-iskw we'll be updating to pydantic v2 by next release.
Till then we'll use the previous version of the package


[CWS] Adding new bind event

New bind event.
For now it only support AF_INET and AF_INET6 address families, and it exposes:

the used socket as integer: bind.socket
the address family as string (using unix constants): bind.addr_family
ip as string: bind.addr
and port as integer: bind.addr_port

New SECL rules can be written like: bind.port != 1234 && bind.addr_family == AF_INET && bind.addr != "<IP_ADDRESS>"
We do not filter bind unsupported address families (in a sense where we do not export related sockaddr fields), but we still send them (with addr_port == 0 and addr == "").
Also, for now all calls to binds that fails will be send, no matter the related error code (only filtering EACCESS looks pity for bind)
Functional tests were added:
inv -e security-agent.functional-tests --testflags "-test.v -test.run TestBindEvent"
TODO:

Adding more address family coverage (and find a nice way to do it without having all the possible fields on the same event json schema, with different empty fields on each event)
Define which errors we want to discard
Add listen too?

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

HI @kayayarai, yes those files are generated and will be fixed as well grace to your other suggestions. :)


Trezor Multisig issue:

https://github.com/bithyve/bitcoin-keeper/assets/62699947/35b401c7-a888-461a-bb8a-96e5793497ed

Trezor MultiSig is not available. However, if we add the device by keeping Trezor(singlesig) in multisig  the app is crashing.

Closing as outdated


GUI > Routing: No config option to add "default-information originate" to the OSPFv3 configuration

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
Missing configuration option in the GUI. No option to add default-information originate [always] [metric] to the frr config from the OSPFv3 configuration GUI
Plugin: os-frr
GUI: Routing > OSPFv3

No checkbox for  Advertise Default Gateway
No checkbox for Always Advertise Default Gateway
No checkbox for Advertise Default Gateway Metric

In frr 7.5.1 it appears that IPv6 default gateway distribution may be picked up implicitly by specifying default-information originate in the router ospf config block through the OSPF GUI pages.
In 23.1 with frr 7.5.1 the default-information originate command doesn't exist under  router ospf6, but ospf6d will distribute the IPv6 default gateway if default-information originate is specified in the router ospf config block.
After upgrading to 23.7 (which upgrades to frr-8.5), default gateway distribution must be explicit defined for both under both router ospf and router ospf6.
Adding via vtysh solves the IPv6 default route distribution problem, but does not persist.
To Reproduce
Steps to reproduce the behavior:

OPsense 23.7
Install plugin os-frr
Routing > OSPFv3 > General
No Advertise Default Gateway or Always Advertise Default Gateway checkboxes, and no Advertise Default Gateway Metric field (or other methods) to add the default-information originate [always] [metric] command to the router ospf6 config block

Expected behavior
Advertise Default Gateway and Always Advertise Default Gateway checkboxes, and Advertise Default Gateway Metric field that will add default-information originate [always] [metric] to the router ospf6 config block.
Describe alternatives you considered
Uninstalling os-frr and installing frr as a manual package then configuring through the CLI directly with vtysh gets around the persistence issue. However, this removes the useful GUI diagnostics and would be a temporary workaround rather than a permanent fix.
Screenshots
N/A
Relevant log files
N/A
Additional context
The default-information originate command for ospf6 was added to frr-8.0 in March 2021 - https://github.com/FRRouting/frr/pull/8057
Overall it looks like there needs to be a review and some rewrites of the Routing GUI pages with the update of the OPNsense plugin to frr-8.5 as the frr conf file is now very different. But I can appreciate that's a bigger task.
Environment
OPNsense 23.7 (amd64, OpenSSL).
frr8.5 (os-frr 1.34)

I have the same issue. I use DHCPv6 PD from OPNsense to an L3 switch using a link-local transit network (no DHCPv6 assigned address on the L3 switch). I use OSPFv3 to advertise the delegate prefix from the L3 switch back to OPNsense (since the route to the delegated prefix does not get installed in OPNsense if the L3 switch doesn't request a DHCPv6 IPv6 address).
Since I don't use autoconfiguration on the transit link either, there is no default route installed on the L3 switch through Router Advertisement. I want to use OSPFv3 to advertise the default gateway to the L3 switch.

Same issue. In general the OSPFv3 GUI really needs some love or a way to just add extra config options.

@imjustmatthew as emailed, https://github.com/opnsense/plugins/pull/3575 contains the proposed changes. To test on the current version, use:
opnsense-patch -c plugins a1138ec

Thanks! That patched worked for me on 23.7.3 with no negative impacts.
I tested with Brocade L3 switches if that matters to anyone else following this.

Merged in https://github.com/opnsense/plugins/commit/a477a672a582ef57f6bad65c82f1064c334dbfbe including revision and model update as reported by @mimugmail


Feature/home page typo

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


Markdown extension isn't support  and  tags

Looks like *.md file isn't support  <details> <summary> and  parse them as code block.
*.mdx extension supports them and I can collapse/expand it.
If *.md extension supported it too, it would be amazing.
<details open>
<summary>Shopping list</summary>
      bla-bla
</details>

pr welcome


include: driver: sensor: add tank level channel in units of percent

Provides an enum for tank level sensor drivers.
Signed-off-by: Nick Ward<EMAIL_ADDRESS>

Is there a driver coming next? Would prefer to wait to introduce a new channel until we have something that uses it.

Not at this time unfortunately.  We have custom tank level sensing hardware that there is no external reference for.  We do want to use the sensing API interface for the out of tree  driver we are developing so we were hoping this channel could be added if it was deemed a common sensing property.

You can use custom channels for your out-of-tree driver. See https://github.com/zephyrproject-rtos/zephyr/tree/main/include/drivers/sensor for examples.

@MaureenHelm, @henrikbrixandersen - is that a nak? @nwsetec - please close the PR if that's the case. I can see it being useful personally.

Thanks @cfriedt, I'll put a basic tank level sensor driver together @MaureenHelm and @avisconti.
These Adafruit sensors should be appropriate: https://cdn-shop.adafruit.com/product-files/3828/3828_standard_datasheet.pdf

Just a comment: This could be useful if used with an ultrasonic level indicator, I have seen this being used on LPG storage tanks.
Billy..


Update and modernize CI

Update and modernize CI.

Generally reduce the amount of testing on C++17 in favor of retaining C++14 and C++20.
Runners on *-latest should generally switch language standard C++2a to C++20.
Consider removing some older compilers, as these don't seem to be needed in CI.
Runners exercising gcc-12-clang-14-* should simply switch to *-latest and use gcc-clang-native-*.

Goal is (hopefully significantly) under 30 minutes for a typical CI run on GHA.

PRs #390 and #391 brought simplifications. CI is down under or around 20 minutes now on GHA


React Todo App

In this update, the following were implemented;

Using React components.
Use of state and props.
Use of hooks; useState, useEffect, useContext.
Use of React Router package.
Use of ProtectedRoute

@preciousbetine Thank you for your review.
I can't find where suggested changes are required. Can you please refer me to these sections?
Thank you.


UltraNest support

Would you be interested to add support for https://johannesbuchner.github.io/UltraNest/ ?
The interface should be very similar to dynesty.
UltraNest is a very reliable tuning-parameter-free algorithm. It can be faster than dynesty, especially if you take advantage of vectorization.
It also supports resuming from disk and MPI parallelisation, if that is useful to you.

@JohannesBuchner Thank you for bringing UltraNest to my attention. I am interested in trying out different samplers with MINESweeper. I will look at your code and see how easy it would be to have user-selected drop-in samplers.


64-bit renderdoc tries to load 32-bit renderdoccmd when using global hook

I've built latest renderdoc v1.x locally, when I run it and try to enable global hook it says it failed. If I look at the log the output message is:
RDOC 017292: [13:34:55]             core.cpp( 298) - Log     - RenderDoc v1.0 x64 Release (027a7e951b4e03e2b05fdfa272688595786898b5) loaded in replay application
QTRD 017292: [13:34:55]       qrenderdoc.cpp( 101) - Log     - QRenderDoc initialising.
RDOC 017292: [13:34:56]          android.cpp( 313) - Log     - COMMAND: adb 'devices'
RDOC 017292: [13:34:56]    win32_process.cpp( 475) - Log     - Running process adb
RDOC 017292: [13:34:56]    win32_process.cpp( 492) - Warning - Process adb could not be loaded.
RDOC 017292: [13:34:56]    win32_process.cpp( 933) - Warning - Couldn't launch process 'adb'
RDOC 017292: [13:34:59]    win32_process.cpp(1528) - Error   - Can't launch 32-bit renderdoccmd from 'C:\Users\redorav\Desktop\renderdoc\Win32\Release\renderdoccmd.exe'
If I build the 32-bit version of renderdoc it all works fine.

To clarify, are you saying the global hook only works if you run the 32-bit version? Or that you need to build both 32-bit and 64-bit versions before you can run the 64-bit global hook?
The latter is by design, that's what the error message is saying. Distributed builds include the 32-bit renderdoc.dll and renderdoccmd.exe to allow this, on local builds I just enforce that the project is built with both versions.

Yeah sorry, what I meant to say is that by compiling the Win32 version, the 64-bit version works. If this is by design then there's not much to look at here. Thanks!


sslaccept=accept_invalid_certs seems to not be the default

Bug description
I am trying to connect to a MySQL database, with a user that has the REQUIRE SSL option set.
The following error appears:
[1657368933547] FATAL: Startup failed
    err: {
      "type": "PrismaClientInitializationError",
      "message": "Authentication failed against database server at `[omitted]`, the provided database credentials for `[omitted]` are not valid.\n\nPlease make sure to provide valid database credentials for the database server at `[omitted]`.",
      "stack":
          Error: Authentication failed against database server at `[omitted]`, the provided database credentials for `[omitted]` are not valid.

          Please make sure to provide valid database credentials for the database server at `[omitted]`.
              at [omitted]/node_modules/@prisma/client/runtime/index.js:45403:20
      "clientVersion": "4.0.0",
      "errorCode": "P1000"
    }

The MySQL server uses a self-signed certificate.
How to reproduce
You need a MySQL server which allows SSL connections and uses a self-signed certificate. This is the default behaviour in MySQL.

Enable the REQUIRE SSL option for your MySQL user: ALTER USER 'myuser'@'myhost' REQUIRE SSL
Start your prisma application

Expected behavior
The connection should be successfully established using default options.
According to the docs, sslaccept=accept_invalid_certs is the default. However, this does not seem to be the case, because the connection does not work.
When I manually add ?sslaccept=accept_invalid_certs to the database URL, the connection gets established successfully.
Prisma information
Not working database url: mysql://myuser:mypassword@dbhost:3306/database
Working database url: mysql://myuser:mypassword@dbhost:3306/database?sslaccept=accept_invalid_certs
Environment & setup

OS: MacOS 12.3
Database: MySQL 8.0.29
Node.js version: 16.13.0

Prisma Version
prisma                  : 4.0.0
@prisma/client          : 4.0.0
Current platform        : darwin
Query Engine (Node-API) : libquery-engine da41d2bb3406da22087b849f0e911199ba4fbf11 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli da41d2bb3406da22087b849f0e911199ba4fbf11 (at node_modules/prisma/node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core da41d2bb3406da22087b849f0e911199ba4fbf11 (at node_modules/prisma/node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt da41d2bb3406da22087b849f0e911199ba4fbf11 (at node_modules/prisma/node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash    : da41d2bb3406da22087b849f0e911199ba4fbf11
Studio                  : 0.465.0

👋 we're cleaning up our backlog of issues and are closing everything older than two years. If you still feel that this issue is relevant, please feel free to re-open and our team will take a look. Thank you!

Hey @P4sca1,
The documentation outlines the expected behavior, so this might be a bug with the ORM. I've created an issue for it here: https://github.com/prisma/prisma/issues/25801.
I'm closing this issue, but please keep an eye on the linked issue in the Prisma repository. Thanks again for reporting this!


Unable to decode ITS message IVIM from TS 19321 with asn1c - failed to decode optional part

Hello,
I have been trying to decode a UPER encoded ITS message called IVIM Infrastructure to Vehicle Information Message using asn1c without much success.
The official schema is available here: https://standards.iso.org/iso/ts/19321/ed-2/en/ISO19321(2019)IVIv2.asn
I get the following error when I try to decode the message, which unfortunately does not tell me why the decoding fails. Note that I have compiled the decoder program with debug mode enabled:
Decoding member "optional" in IviStructure (constr_SEQUENCE.c:1170)   [PER got  3<=1322 bits => span 201 +8[9..1328]:1b (1319) => 0x7] (asn_bit_data.c:139) Preparing to fetch 7+1 elements from IviContainers (constr_SET_OF.c:949) SET OF IviContainer decoding (constr_SET_OF.c:967)   [PER got  1<=1319 bits => span 202 +9[2..1320]:d2 (1318) => 0x1] (asn_bit_data.c:139)   [PER got  7<=1318 bits => span 209 +9[9..1320]:d2 (1311) => 0x25] (asn_bit_data.c:139) Failed to decode element IviContainer (constr_CHOICE.c:882) IviContainers SET OF IviContainer decoded 2, 0x55b096f4e7b0 (constr_SET_OF.c:971) Failed decoding IviContainer of IviContainers (SET OF) (constr_SET_OF.c:986) Freeing IviContainer as CHOICE (constr_CHOICE.c:1065) Failed decode optional in IviStructure (constr_SEQUENCE.c:1180) Failed decode ivi in IVI (constr_SEQUENCE.c:1180) AD: decode(0) consumed 0+0b (190), code 2
The full decoder output is attached: output.txt
The relevant part of the ASN.1 schema is below:
`IviStructure::= SEQUENCE{
mandatory       IviManagementContainer,
optional        IviContainers OPTIONAL
}
IviContainers ::= SEQUENCE (SIZE (1..8,...)) OF IviContainer
--Definition of Containers
IviContainer::= CHOICE {
glc     GeographicLocationContainer,
giv     GeneralIviContainer,
rcc     RoadConfigurationContainer,
tc      TextContainer,
lac     LayoutContainer,
...,    -- original extension indicator of V1
[[ -- Extension in V2
avc     AutomatedVehicleContainer,
mlc     MapLocationContainer,
rsc     RoadSurfaceContainer ]]
}
`
Any help to debug the issue is much appreciated!

Anyone? I'm kind of at a roadblock here..

I believe this issue is related to #407 because IVIM message format uses also extensions markers in size constraints such as IviContainers ::= SEQUENCE (SIZE (1..8,...)) OF IviContainer.
@sandman Have you found a fix or simply abandoned asn1c when closing this issue ticket?


Stopped working with the latest insider builds

Hi,
I was using that great extension for a few weeks now.
A few days ago it stopped working though. I don't see an error, just no matching indicator appears.
I'm using the latest vscode insider build that is updated daily, so I can't sadly point to the latest working release. The version I'm currently using is:
Version 1.22.0-insider
Commit ec3c083444c084394ee0cd936074019c1bc0b321
Datum 2018-03-14T06:14:24.748Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architektur x64
OS is Ubuntu 17.10.
Is there any workaround to get it back working or to give you more info?
Thanks,
Torsten.

Here's the error I get in the developer console:
Error activating extension "rafamel.subtle-brackets": TypeError: Cannot assign to read only property 'borderColor' of object.

Hi there, Torsten, I finally had some time to look this error over. I haven't been able to test it out on v1.22, but I have a theory as to what is causing it. If it's what I think, the PR #9 wouldn't solve the underlying problem. Could you please test out on your computer the branch fix-readonly of this repo and let me know if the error still occurs?
Thanks for the help!
Rafa.


Cannot resolve const [imagemin, webp] = await Promise.all([import('imagemin'), import('imagemin-webp')]);

https://github.com/adamlui/js-utils/blob/23b8bbb60944f8207e9793ad3ec021ffedb39f9e/img-to-webp/img-to-webp.js#L18C1-L18C94 results in
Error:   18:55  error  Unable to resolve path to module 'imagemin'       import/no-unresolved
Error:   18:75  error  Unable to resolve path to module 'imagemin-webp'  import/no-unresolved

Are these packages installed locally?

Indeed they are via package.json dependencies
...
  "dependencies": {
    "imagemin": "^9.0.0",
    "imagemin-webp": "^8.0.0"
  }
...

The issue then, seems to be that both of these packages lack a main, and use type: module, and this package doesn't support the exports field yet.
I'd suggest putting them in import/ignore in the meantime.

I already did but maybe you should add a feature to auto-detect unsupported pkg types to not false positive in the meantime for better UX

Due to the way resolvers are implemented, that would probably take almost as much time as the support itself.


sunsetting 1-tap? is OAuth supported?

Any Update here @truecaller ? I want to integrate true caller auth to a new flutter project, but can't as I can't create new projects, and there is no flutter sdk for the new auth mechanism.

@shubhral @praphull  @sreedeepkesav @singhalyogesh  @lannannanna  Any update ? Same waiting for more than 1 month.


uTP listener fix

Make the utp listener send the ListenerResponse from the listening socket.

This change is

r? @vinipsmaker
(maidsafe_highfive has picked a reviewer for you, use r? to override)

crossbeam::scoped doesn't create a thread. It lets you use the scope to spawn threads that can borrow data from outside the call to scope (in this case &udp_socket),

crossbeam::scoped doesn't create a thread. It lets you use the scope to spawn threads that can borrow data from outside the call to scope (in this case &udp_socket),

Could we leave the loop of the udp listener thread and destroy the socket to only then let the second thread use the (destroyed) socket?

Nope, the purpose of crossbeam::scope is to allow you to safely share borrowed data between threads without overhead and without having to use Arc or try_clone or anything like that.
All it does it call the closure that it's given then block until any threads that were created inside of it (using the Scope) have exited. That way, the spawned threads can be tied to the lifetime of the Scope instead of having to be 'static.
It's basically safe hack to relax the borrow checker.

Still... is there any reason why you avoided udp_socket.try_clone()? It'd be much simpler.

To me using crossbeam seems simpler. Rather than duplicating a file descriptor (and having to handle the case that it might fail) just tell the compiler that it's fine if both threads use the same socket.

You nested much more code just to do a udp_socket.clone(). It's not simpler code, but the main problem is the lack of uniformity. Why did you give different treatment for udp_socket and mapping_context. To me it looks like we taking different approaches to implement as many techniques as we can just to make the code more confuse.

You nested much more code just to do a udp_socket.clone(). It's not simpler code,

Except I didn't do a clone. There's one reference to a socket and both threads are using it. This is conceptually simpler than having to clone a socket, it's exactly like using the same pointer from two threads in C/C++. It's just a side-effect of rust's borrow checker that you need to indent an extra block to do it.

but the main problem is the lack of uniformity. Why did you give different treatment for udp_socket and mapping_context.

That's a good point, the other variables could be moved to outside the scope aswell so they don't have to be cloned (except for event_tx because it's not Sync). However cloning an Arc isn't the same as cloning a UdpSocket. Cloning an Arc just increments a reference count and always succeeds whereas cloning a UdpSocket does a sytem call which creates a new file descriptor and can fail.
If you feel strongly about it I'll change it but I disagree it's more complicated. Our current approach of using Arc everywhere is slow, bug-prone and risks leaking threads. We should be using scopes and sharing stack data between threads whereever possible.

You nested much more code just to do a udp_socket.clone(). It's not simpler code,

Except I didn't do a clone. There's one reference to a socket and both threads are using it. This is conceptually simpler than having to clone a socket, it's exactly like using the same pointer from two threads in C/C++. It's just a side-effect of rust's borrow checker that you need to indent an extra block to do it.

 Your approach incurs more concepts. I still disagree with you on this one. I do believe it's more complex.

If you feel strongly about it I'll change it but I disagree it's more complicated.

Never mind. Your approach saves one file descriptor. We had problems allocating them on OSX in the past because OSX have rather low limits. I don't mind complexity if it spares resources.

Can you rebase your branch against master (remember to ping me back as GitHub won't notify me of new commits added to PR)?

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io


Move sdk permissions into pike/permissions module

/sdk/src/permissions.rs was split apart into two separate files,
"/sdk/pike/permissions/mod.rs" which contains the PermissionChecker
implementation, and "/sdk/pike/permissions/error.rs" which contains the
PermissionCheckerError implementation. This means also that the import
path changed from grid_sdk::permissions to grid_sdk::pike::permissions,
so the handler files requesting permissions has also updated.
Signed-off-by: Kevin Johnson<EMAIL_ADDRESS>

This needs to be rebased because of conflicts.

Can I get eyes on this? Checks are passing, and changes requested have been satisfied.


"finishAll" functionality

Adds an option to finish all animations on an element's queue, not
just the currently-running one.

Why so many changes in the jQuery shim part?

I think the original had inconsistent line endings.
On Sunday, August 30, 2015, Yehonatan Daniv<EMAIL_ADDRESS>wrote:

Why so many changes in the jQuery shim part?
—
Reply to this email directly or view it on GitHub
https://github.com/julianshapiro/velocity/pull/570#issuecomment-136130063
.

@julianshapiro perhaps you're to blame in all this line endings fiesco? :stuck_out_tongue:

There's a git option to ignore line endings, technically it would be everyone pushing without that option set that's at fault ;-)

:+1:


Remove RC when talking about Astro v1

What kind of changes does this PR include?

New or updated content

Description
I did remove the text with the Release Candidate. However I still added:

The Astro v1.0 (and all the Release Candidates for it) introduces some changes [...]

However maybe we could even remove that little notice as normally you don't install a RC when there's the actual release already.

LGTM! Going to merge so that new readers see this in the migration guide and don't get confused

Great! Thanks for merging and good change you did btw.


Remove placeholder from validarion rules when there is no matching variable

Description
When we use a placeholder in validation rules and there is no data provided to replace the placeholder, we can end up with something like {variable} as a parameter. This can cause issues for developers like in is_unique validation method.
In this case, when we have rules like: is_unique[user.email,id,{id}] we can produce the query like:
SELECT 1
FROM "user"
WHERE "email" =<EMAIL_ADDRESS>AND "id" != '{id}'
LIMIT 1

In MySQL it would be a mistake we probably could live with, but in PostgreSQL this will produce an error: invalid input syntax for integer since this DB engine checks the field types.
Either way, I would call the current behavior a bug.
This pull request fixes this by removing placeholders that can't be replaced by provided variables.
Related to #2812
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPdocs
[x] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

travis seems failure in 2 places:

CodeIgniter\Validation\FormatRulesTest::testRegexMatch
CodeIgniter\Validation\ValidationTest::testSplitRulesTrue

Thanks @samsonasik , it's fixed now.

With this we are destroying legitimate placed "{data}" in there not allowing us to have custom rules containing regex , as it will destroy them. Or rules matching that literal string in e.g. in_list, sure that placeholder can be changed by the developer.
Personally I'm not a fan of deleting random data in case a math not found in $data.

From my point of view {data} syntax is reserved for placeholders. Custom rules with regex still are possible but not as parameters since they might be problematic. Sure, there are some trade-offs of this approach, but for me they're reasonable.
Anyway, if this won't be accepted, then we still have #2916 ready to go.

I reopened https://github.com/codeigniter4/CodeIgniter4/pull/2916 as alternative

@michalsn That's just why I have strings with {} syntax saved and validated. And a rule with regex as a placeholder that detects {} in a string. It checks if there are any {} not using the correct format. I have made it universal with said regex instead of hard coded it in. Don't know if other people do custom regex function, but that can cause issues.
And regarding #2916 are that really a problem, as you are missing said Id in the post itself? Sure it dies as it's not valid (throwing an error you can catch), for that database type. But this are also killing strings with {} that can contain real data.
At the moment the function does what it's ment to do, replace placeholder with data provided. These PR will manipulate / alter said data if it does what it's supposed to do.

I'm just saying that I would expect that placeholders should work a little differently - let's say just like variables in a template system. If there is no variable in a template, you won't en-up with a visible placeholder.
But this is just my expectations.
I understand the idea that we should explicitly provide empty values for variables that are not present. But in reality, in day-to-day use, it's very inconvenient. And it forces us to write unnecessary code. I'm trying to change it somehow.
The more I think about it the more I see that my implementation probably isn't the right way. But maybe someone will have some ideas on how to improve this?

EDIT: Ok, it's a create call, not having an actual ID in it. So we need to do a check for something like this. Only killing what it's supposed to find. But that will of course only work if they are named the same. 🤔
if ($ignoreValue === "{{$ignoreField}}")
{
	return false;
}

Yeah... unfortunately, something like this doesn't guarantee anything. I will keep thinking.

Ok, I think I will close this PR since it will introduce BC changes anyway. If we are strict about it, then sadly #2916 is also not a way to go.
I guess we should stick with the current implementation but I personally think it will create many confusions in the future.
Developers that use MySQL database probably won't be aware of what query is actually produced when variable for the placeholder is not available. And developers that use PostgreSQL will have no choice but to write some additional code to handle this. Also, these last guys probably will produce a lot of tickets here and threads on forums.

Hi, I'm not saying you are wrong about pointing out flaws in the system, but it may brake some design concepts. That's why I mentioned it. I don't have any real solutions to the problem itself (PostgreSQL), the ignoreValue === ignoreField only works if we "hard limit" it by giving it a note in the user guide.
But for me #2916 will remove all keys that's named as a translation string, that users can translate themselves. It's not checking is_unique at the moment, as they can't add things. Only update.

Key
Translation

{pages.nextPage}
Next page

{pages.previousPage}
Previous page

Yes, thank you for pointing all these things our, really. My solution was far from perfect.
I'm just a bit frustrated that we weren't able to find any reasonable solution for this issue.

I hear ya! Hopefully we can put our heads together and think of something, at the moment I'm totally blank.


"Save File" dialog is not visible in KDE after upgrade to 1.94.0

Does this issue occur when all extensions are disabled?:
Disabling all extensions (with --diable-extensions option on command line) didn't help.
Reverting VSCode snap to 38c31bc7 (which is 1.93.1) fixes things.

Probably related to #230454
Pinging @deepak1556 in case this report provides additional clues.

The problem seems to be with --title=Save As, which should be quoted or have the space escaped, as it ends up interpreting "As" as the location to open.

Please try https://github.com/microsoft/vscode/issues/230454#issuecomment-2396957450 and confirm if the crash persists.

Please try #230454 (comment) and confirm if the crash persists.

Here is what I did:
$ snap run --shell code
$ ls $SNAP_USER_DATA/.local/share/mime/
aliases      audio  generic-icons  globs2  image  magic    mime.cache  multipart  subclasses  treemagic  version  x-content  XMLnamespaces
application  font   globs          icons   inode  message  model       packages   text        types      video    x-epoc
$ rm -rf  $SNAP_USER_DATA/.local/share/mime/

and the issues is still there 8(

I can reproduce it in an empty basic electron app ( template: electron/electron-quick-start )
with electron v30.5.1 ( upto v32.1.2)
 const dialogOptions = {
    title: "test",
    buttonLabel: "open",
    pickFiles: true,
    properties: ['multiSelections', 'openDirectory', 'openFile', 'createDirectory'],
    filters: "*",
    defaultPath: "/home"
  };

  dialog.showOpenDialog(mainWindow, dialogOptions);

but works with v30.4.0

I simply cloned the  electron examplerepo, made the addition to main.js and npm install & npm start

Thanks, yeah that does confirm relation to https://github.com/microsoft/vscode/issues/230454
Can you try the steps in https://github.com/microsoft/vscode/issues/230454#issuecomment-2401454665 and provide the results. Thanks!

I upgraded to Kubuntu 24.10 and the problem is gone

KDE Plasma is affected by the same MIME info infinite loop issue that is mentioned in https://github.com/microsoft/vscode/issues/230454.
See https://bugs.kde.org/show_bug.cgi?id=494160
It is fixed, but the version shipped on Kubuntu 24.04 is too old to have the fix. 24.10 does have the fix

KDE Plasma is affected by the same MIME info infinite loop issue that is mentioned in #230454.

So, this is a bug on Plasma's end, not on vscode's?

I've observed this bug on my system, KDE Ubuntu 24.04 LTE.
In case somebody follows my steps, I rolled back to the code snap 169 rev, it's working.
snap refresh code --revision 169
I tried to rollback from 172 to 171, 170—they are all broken for me.
To stop the automatic refresh of code, and without a timer:
snap refresh --hold code

As mentioned in #231310 - enabling "Simple Dialog" mode in settings, suits as a workaround.

I have similar issue when opening a folder (and all other actions that use this).
I also remove snap's VSCodium and installed it from APT. the dialog now opens but without the option to click ok on the folder; it only allows to keep opening folders.
I confirm that enabling "Simple Dialog" provides a good workaround.

Related to https://github.com/electron/electron/pull/42045#issuecomment-2484841772, bug is in the runtime detection for kde dialogs.


Add status LED to instance table

Get your bikeshedding on! Must have LEDs in instance table!

My rendition.


Wholesome memes

You have a load of meme communities there, but this one is missing:
<EMAIL_ADDRESS>

We already have a community with the same theme from the same instance in the directory. Your suggested community is not only very little active but also has multiple times less subscribers.

Not sure if it's a good idea to add it. If it was from a different instance then I would be for it because LW is kind of too big but both of those are in the same place.
https://lemmy.world/c/lemmybewholesome

Actually I think it was lemmybewholesome I was thinking of. I didn't see anything like that in the list but must have missed it.