Allow not unwrapping refs when using store

What problem is this solving
So when you use a store, it wraps it in a reactive, which is helpful since you don't have to use .value and it means composition and options stores are the same. But it's also really annoying because it's not what you expect it to be if you're returning refs and you can't destructure them. It's quite annoying to have to use storeToRefs or computed when it's not really necessary.
Proposed solution
Solution 1: Allow passing an options object when you create the store, including the two current options, plus an option to not unwrap refs. This would be harder because wrapping it is done when you define it, at least that's what it looks like when I look at the source code.
Solution 2: Make this an option when you define the store instead of when you create it. This is easier, but it's probably not as good since it isn't obvious when you use it, you'd have to look at the definition or maybe the types.
Describe alternatives you've considered
No response

For now, there is no intention of shipping this feature with the existing ones because it makes things different when using the store, while it is not explicit why things are not unwrapped anymore (still same useStore() call). In practice, I've played with both ideas, and I rarely extract refs from the store, I use the store directly, as a whole, as a service. You don't need to use storeToRefs().
It's also worth noting that this can be implemented in user land with a custom defineStore that calls storeToRefs().
That being said, I don't want to give up the idea yet completely, so I will move it to Discussions and see if the community comes up with other arguments


Iink to blurred image broken?

Thanks for sharing code with public.  Is the link to blurred image still good?  I am not able to access the lnk.
Thanks
C. Chien

Does https://people.eecs.berkeley.edu/~hendrycks/blurry_images.tar not
work? It works for me.
On Tue, Aug 31, 2021 at 4:36 PM chyphen7 @.***> wrote:

Thanks for sharing code with public. Is the link to blurred image still
good? I am not able to access the lnk.
Thanks
C. Chien
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hendrycks/imagenet-r/issues/3, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACZBITVGM36UGLEAX4YUMVDT7VRQBANCNFSM5DFGFUJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


hideSecretFromPropertiesFile not working!

I got this error when read data from credentials.properties file
$: gradlew hideSecretFromPropertiesFile -PpropertiesFileName=credentials.properties -Ppackage=com.sample.test
FAILURE: Build failed with an exception.

What went wrong:
Task '.properties' not found in project ':app'. Some candidates are: 'properties'.

Hello @mehdi-salehi did you find the issue ? I think there is an error in your command line because it is not interpreted as expected.


Remove statement fields from Merkle proofs

Fixes #67. Does not address #48.
Removes "statement" (i.e. what you're trying to prove) fields from Merkle proof structs. Also clarify ordering of hashes. Leaf-to-root order was chosen to conform to https://tools.ietf.org/html/rfc6962#section-2.1.1.
Thanks to @fubuloubu for the discussion that led to this clarification (https://twitter.com/jadler0/status/1362432558382936067).

Since the NebulousLabs library starts from the leaf, I'm ok with starting from the leaf and being consistent there for all Merkle tees.


Not showing up on iPhone safari

Hi,
first off what an amazing script you got here. Great job on this!
I was able to successfully display the waves in firefox and chrome, desktop and android devices.
But for some reason the waves do not appear on safari iPhone.
I'm running an icecast server and displaying the waves via audio tag like so..
<audio id="radio" crossorigin="anonymous">
       <source src="https://mystation.com/stream" type="audio/mpeg" />
       <source src="https://mystation.com/stream.ogg" type="audio/ogg" />
</audio>

and I am triggering the playing of the audio like this..
var player = document.getElementById('radio');
player.load();
player.play();

I have a canvas html element on the page like this..
<canvas id="wavesCanvas" height="250" width="500"></canvas>
The waves is set like this..
var wave = new Wave();
var options = {type:"shockwave", colors: ["#6c2a99", "#e01919", "#b4751d"]};
wave.fromElement("radio","wavesCanvas",options);

The audio plays on all devices including safari on iPhone.
The wavesjs shows on all browsers except safari on iPhone.
I should note that I have not tested on safari on a mac because I do not own a mac at the moment.
Is this a known issue?
Is there any special configurations needed for this to work on safari?

Yes, this is a known issue. I have tried to fix this in the past but I dont own a apple product so I cant confirm if my changes work. I believe the issue is with the AudioContext instance, which is used to get the frequency information from the audio. Safari wont let you create it, or start an analysis, unless the user has interacted with the window first.

Which wouldn't be a problem, because the user interacts with the window by clicking play.
What APIs are vital for Wave.js?
I'm not able to get the example to work with the current desktop Safari. The APIs should be supported. Do you have a small and verbose test-scenario?

You should be able to run "npm run test" in the root of the project and see if waves will render, this does not have error logging though. The API's used are the Canvas API and the Audio Context API. Safari just does not react the same way chrome or firefox does with these API's. The issue is likely with the Audio Context API. Most likely the Analyzer Node is not able to read the frequency information.

@foobar404 Thank you for the info.
I will update if I figure out a work around.

Not showing up in Safari on smartphones, tablets and desktop.
This link from apple developer may help you @foobar404 to find out how to make it work on Safari ?
Safari HTML5 Audio and Video Guide
Scroll down to paragraph called "Listing 3-1  A simple synthesizer and audio spectrum visualizer"

@fffiloni Do you see any error logged in the developer console?

I have no errors. Using an audio stream from icecast broadcast give me zeros in the Uint8Array data.
It seems to work with files tho.
I was able to understand it while playing with this simple fiddle here : https://jsfiddle.net/6y0dp9e2/ . Fiddle's author wrote that in safari we need to declare audio context after user interaction with audio.
Using a file works fine in the Uint8Array for Safari, but do not with stream or element listening to icecast adress.
——
I found someone who figured out how to make it work using rtc stream, you can read his publication about it HERE

I have no errors. Using an audio stream from icecast broadcast give me zeros in the Uint8Array data.
It seems to work with files tho.
I was able to understand it while playing with this simple fiddle here : https://jsfiddle.net/6y0dp9e2/ . Fiddle's author wrote that in safari we need to declare audio analyzer after user interaction with audio.
Using a file works fine in the Uint8Array for Safari, but do not with stream or element listening to icecast address.
——
I found someone who figured out how to make it work using rtc stream, you can read his publication about it HERE
Hope it helps

Could you check in my repo if the change is fixing your case? branch stream-problem-safari
You just have to clone this branch, install the dependencies and to run npm run example-from-stream

@korbav -- thanks for all your development, bud! -- is there a way to apply your safari fixes to the original wave.js?

@korbav -- thanks for all your development!
i tried your rewrite, and unfortunately i still can't get waveforms to work in iOS or desktop Safari :/

Hi @jailbrokebloke , thanks for your feedback, then it means that the problem was not related (or at least not only) to the user interaction issue, because this attempt explicitly waits for user interaction to create the Audio Context.
Could you please elaborate a bit on what happens exactly? is there any error/warning, does the browser complain?
About the rewrite, we need to discuss this with @foobar404, I personally think it would be an interesting step for Wave.js to get into it since it brings modern features and probably constitutes a cleaner usage.

Did you take a look to the publication about rtc sream on Dwayne’s blog ? He gives a reference linked here : https://mdn.github.io/voice-change-o-matic/
This example works on safari, maybe useful to explore the way they built it

Did you take a look to the publication about rtc sream on Dwayne’s blog ? He gives a reference linked here : https://mdn.github.io/voice-change-o-matic/
This example works on safari, maybe useful to explore the way they built it

I'm gonna give a try to it. Before all, can you confirm that the problem is not related to the access to the microphone?

I don't think it's related to the prompt, because using a broadcast link from a webradio for example using the "fromElement" method in wave.js give us no change in the Uint8Array for Safari, but works with a ismple mp3 file.
I think it can't analyze audio coming from stream for the moment.

I don't think it's related to the prompt, because using a broadcast link from a webradio for example using the "fromElement" method in wave.js give us no change in the Uint8Array for Safari, but works with a simple mp3 file.
I think it can't analyze audio coming from stream for the moment.

You should create a codesandbox.io demo with your Safari-non-working code. I can't see more without it.

Just adding this for anyone stumbling across this and having issues with Icecast/HLS streams and createMediaElementSource .
This has been an outstanding bug on webkit for ages https://bugs.webkit.org/show_bug.cgi?id=180696.

Hey there 👋
I opened a pull request with a fix for this issue at #84

@rogeriochaves You were able to get data out of the analyser with that code? I've got a page where I wait to create and connect until the user presses a button, the audio plays in all browsers but getByteFrequencyData returns all zeroes in Safari. I'll take a closer look at where our scripts differ


User is able to designate an asset as control plane

User selects which asset or assets will make up the control plane
There are no minimum requirements that an asset must meet to be available for selection
A control plane can consist of one or more assets - there are no max number of nodes but 3 is the recommended number
K3S may have master - agent combo or more traditional control plane with additional worker node set up
User has ability to add further assets to control plane post cluster creation
A worker node is one asset machine
Worder nodes in the cluster use the Default node pool (for now)

UX Design:
https://www.figma.com/design/bIr4DqrLF38gqtcWCurVHu/colony?node-id=990-27405&t=oo9LUMaOWhxaNpQf-4


Investigate scaling/offsets from PAL60 switch

We moved a lot of games from PAL60 to PAL with 5× scaling/crop in https://github.com/amigavision/AmigaVision/commit/062da0505ed7f5cd95a0883c504e8ae6e12a99ac, here are some known issues:

1869 is listed as ECS for the international versions, fix
Battle Squadron NTSC will run as PAL, fix
Lemmings 1+2 seems to explicitly have preferred version as NTSC, fix — maybe others
Mortal Kombat 1+2 have wrong offsets, fix
Should the Strike games run in NTSC since they are MegaDrive ports?
Flink may default to the NTSC version, offset is in any case wrong, fix
Check scaling on Puzznic
Top Gear 2 has bad offsets?

Darkseed has bad offsets:
game--darkseed--darkseed
game--darkseedfr--darkseedfr
game--darkseedcd32--darkseedcd32
game--darkseedes--darkseedes
game--darkseedde—darkseedde


Redo the whole thing

Using ansible, upgrading to Jenkins 2 and standardizing on Debian stretch.
TODO:

[x] gpg config
[x] swap space
[x] teach scabot about new jenkins
https://wiki.jenkins.io/display/JENKINS/Remote+access+API#RemoteaccessAPI-CSRFProtection
[x] harden config (disable crontab, log more, ..)
[x] rotate jenkins logs
[ ] move to Pipeline (@retronym is working on it)
[ ] test 2.11 build
[ ] S3 upload IAM profile needs some work in the AWS account that owns the bucket
[ ] test a release

Later:

enable CSRF, once scabot implements
move log files out of root volume, so they don't bring the instance down when they get big

I manually hardened the config on jenkins master a bit, disabling cron, keeping logs a bit longer,...  Based on https://github.com/virtadpt/ubuntu-hardening/tree/master/16.04-lts

I'm going to merge this and create tickets for the remaining items.


wrapList / toggleList eliminates nodes it shouldn't?

If the container of the list is inside another block node, the behavior of wrapList seems incorrect.  If, for example, your schema looks like section -> paragraph -> unordered-list. Calling wrapList when the cursor is in the paragraph will eliminate the entire section node.

What's the suggested fix for this? Wouldn't it need to be implemented in the users codebase? E.g. in my editor that i implement this plugin I would need to update my schema to allow for un ordered and ordered lists inside section and/or paragraph @riosn-n ?


Can serviceMonitor do something like prometheus-adapter does?

Can serviceMonitor do something like prometheus-adapter does?
Like the metricsQuery we set in prometheus-adapter.
Or serviceMonitor just forwards all the metrics from the pods?

Can you elaborate please? What is your use case?
Generally the ServiceMonitor is just a definition to tell Prometheus which targets to scrape.

Oh, I see.
I think I misunderstood the role for the serviceMonitor.
Thank you.


Rework invite ui

Fixes #2181

Codacy is wrong I am right I used lombok and codacy does not know that

Please re-add inviting by pressing enter and keyboard navigation of the invite list. It helps a lot when you want to invite multiple people.

Can we also add some tests for it?

Yes wanna make sure you are ok with the change first

This should be good but still needs tests

yeah

Are tests going to be added?

on it

Codacy saidly does not know about Lombok

Yeah I am always surprised they haven't add detection for that yet

Testwise there is not much else I could test in a meaningfull manner


express_ref macro: https://github.com/metanorma/metanorma/issues/122

Moved to standoc

Moved to standoc


Change Author language to Presenter language on Conference Presentation submission forms

Change "I am an Author" to "I am a Presenter", and "Add Author" to "Add Presenter".

Pull request submitted to resolve this issue.


How to ignore expanded components

I see the last time this question was asked was approximately 3 years ago, but that issue didn't really solve my problem.
Essentially when I use component_function I am able to write specific methods that can look at the filetype using &ft and decide when I want to and show hide certain components.  This isn't the same for component_expand.  I want to hide the lineinfo when I have things up like NERDTree or help documents because it doesn't really help me at all in those times.  You can take a look at https://github.com/sethen/dotfiles/blob/master/os/init.vim#L203 to see how I am doing this in component_functions -- I want to do the same for component_expand for certain things.
Is there any way to write functions in component_expand and hide them in specific situations or is just an all or nothing approach?

If the function returns empty string, the component should be hided. This should behave as same with component_expand. By the way I'm afraid the function LightlineLineInfo is missing in your configuration.

If the function returns empty string, the component should be hided. This should behave as same with component_expand. By the way I'm afraid the function LightlineLineInfo is missing in your configuration.

Right, it's not there because when I wrote the function and put it in component_expand it didn't work correctly.  Let me write the function and push it up and I will update this issue with the new method so you can see.

@itchyny Okay, so here is the missing method: https://github.com/sethen/dotfiles/blob/master/os/init.vim#L317
If you were to use this in nvim, the lineinfo gets shown in places where it shouldn't be shown.  All of the other methods that are in component_function work fine in regards to hiding things by returning an empty string and not showing them in NERDTree, help and startify.
Applying the same logic with component_expand does not work.  When I am focused on the buffer where the lineinfo should be shown I am able to see lineinfo in an inactive state that should be hidden in NERDTree, help and startify.

If you want to hide the lineinfo component using component_function, try
function! LightlineLineInfo()
  if IsIgnoringStatus()
    return ''
  endif

  return printf('%d:%-2d', line('.'), col('.'))
endfunction

I think you don't need to use expanded component for hiding the lineinfo in specific buffers.
The functions in component_expand are evaluated before setting to &statusline and never be re-evaluated until some window focus changes. The functions are called on windows are created so it might not work when you use filetype information, which may be set after lightline sets the statusline. You can call lightline#update() to re-evaluate them.

Ah, I see!  Well the code you provided is working so I thank you for that.  I wasn't aware of the lightline lifecycle so thank you for bringing that to my attention!  All is good!


[Feature] Support OpenKruiseGame as addon

Is your feature request related to a problem? Please describe.

Ref: https://github.com/openkruise/kruise-game/blob/master/docs/en/getting_started/installation.md
Describe the solution you'd like

Describe alternatives you've considered

Additional context

ping @MdSahil-oss are you interested in this?


install script doesn't work correctly with ubuntu

install.sh only checks for linux, but it should detect debian and download that release.
curl -fsSL https://wush.dev/install.sh | sh

Downloading wush from https://github.com/coder/wush/releases/download/v0.2.1/wush_0.2.1_linux_arm64.tar.gz...
Extracting wush...
wush installed successfully!

wush serve
bash: /usr/local/bin/wush: Operation not permitted

The container is on a docker host on an Mac M3
uname -m
aarch64

Thus it tries to bring down ..._linux_arm64.tar.gz
I manually wget ...linux_amd64.tar.gz or ...linux_amd64.deb and wush works

Good find, interesting that it shows aarch64 even in the Docker vm. Will fix

Unless the container is started using the --platform flag, it should be an ARM64 OS running in it.  The Docker VM has to match the host architecture and then emulation kicks in for platform switching. Seems unexpected for you to get an architecture mismatch in this case.

Yeah, pulled out my M2 and wasn't able to reproduce

Installed newest Docker desktop
Pulled latest ubuntu image
Ran docker run -it --rm ubuntu:latest /bin/bash
Ran curl -fsSL https://wush.dev/install.sh | sh in the container
Observed that wush seems to work correctly after installing

Maybe I accidentally fixed this with other changes? If not, could you run file $(which wush) and let me know what it returns?

I use colima which wouldn't surprise me if that is part of the problem. I specifically start colima and docker with arm so am royally confused.

@coadler after manually installing wush in the container (which overrode the amd one I had installed), I confirmed I get the
within the colima vm
colima ssh
uname -m
aarch64

within the container (based on parent codercom/enterprise-base:ubuntu
uname -m
aarch64

wush
bash: /usr/local/bin/wush: Operation not permitted

file $(which wush)
/usr/local/bin/wush: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, Go BuildID=xyYqC0eps8VRp6k55vNw/5C2t6R3IgNULHG0BL97r/RckZuEQI_Y1kiuWraPkS/bP7fGdEQZaqncc_i5g61, stripped

no worries about debugging or helping, just strange.


refactor SpringValueProcessor extract duplicate code

What's the purpose of this PR
refactor SpringValueProcessor extract duplicate code.

I have read the CLA Document and I hereby sign the CLA


Added database assembly to admin guide

Added database assembly to admin guide
https://issues.redhat.com/browse/RHIDP-3475

/cherrypick 1.2.x


use web-inventory

use https://github.com/ImHarvol/mineflayer-web-inventory to make inventories

see #10


Better handling of YouTube methods before player is ready

@Fauntleroy has found that play() can sometimes be called before this.player.playVideo exists. https://github.com/CookPete/react-player/commit/f18792a2da3167f775d48481aa8eae150b747d4d prevents errors for the time being, but doesn't really fix the problem.
From this discussion.

@CookPete I think I found the culprit: this.getSDK() can get called more than once. It's initially called for the blank video load, but it will be called again if you load another video before the SDK loads.


fix(ci): cleaned up circle config

swapped npm i for yarn install (there is a yarn.lock)
corrected cache key usage to avoid compounding deps
from other open branches
aliased a few commands
added yarn cache to circle cache

@hipstersmoothie gifsicle requires a library that I didn't have installed. I added a note to the README about it. I also regen'ed the lock file because it looks like there may have been internal endpoints listed in the file.

swapped npm i for yarn install (there is a yarn.lock) (awesome ✅)
corrected cache key usage to avoid compounding deps from other open branches (gonna move this to my other configs! ✅)
added yarn cache to circle cache ✅

questions:

aliased a few commands

In this you move the lint step from ints own container to the install. I don't really like this because if the lint fails the user will see the install check fail. I like that the containers can tell me what failed without having to actually see why it failed. In the past if the lint task failed I would just run the lint locally. Now i would have to see the logs to see that it was actually a linting error. Why did you choose to move this here?

@hipstersmoothie Oops, force of habit. I don't usually make separate jobs for all my steps. I can fix that.


Animation issues when going from last to first item.

When I try to animate the slide transition with some opacity, everything works fine except when I go forward from last to first element. Even when I go backward from first to last it works fine.
.gif of the issue
The gif is a bit more glitchy than the actual result but we can clearly see that when going from slide "4" to "1" the animation skips. But not when going from slide "1" to "4".
[  https://jsfiddle.net/b5bqk68j/6741/  ]
====================================================================
Steps to reproduce the problem

Initialize a slick slider with the following config
let sliderConfig = {
    centerMode: true,
    centerPadding: '400px',
    infinite: true,
    slidesToShow: 1,
    prevArrow: $prevArrow,
    nextArrow: $nextArrow
};

Add transition to slide or element in the slide.
in my case:
.slick-animate {
    opacity: 0.5;
    transition: opacity 0.48s ease-in-out;
}
.slick-center {
    .slick-animate {
       opacity: 1;
   }
}

Use any means of going forward through the slides and see the effect.

====================================================================
What is the expected behaviour?
Every slides animates properly (like when going backwards).
====================================================================
What is observed behaviour?
When going from last to first the animation is glitching. (probably because of the slide cloning/switching)
====================================================================

I had this same issue. I ended up replacing line 2356 https://github.com/kenwheeler/slick/blob/master/slick/slick.js Line 2356
allSlides 	.eq(_.slideCount - 1 - _.options.slidesToShow) 	.addClass('slick-center');
with
allSlides 	.eq( indexOffset + _.slideCount + 1 ) 	.addClass('slick-center');

Thanks for answering.  😄
Unfortunately I just tried switching out that line but it doesn't seem to change the end results.
I made sure the proper version of the file was loaded and not a cached version but nothing.

I updated the code, maybe you used my previous one. Let me know if it works

Oh nice that did fix it! Thank you 👍

This should be reopened so it's fixed in the library itself. maybe @explorador can send a PR for this?

I see the same behavior again, does anyone have the same issue?
I've applied:
    .slick-slide
      img
        transition: all 0.5s
    .slick-center
      img
        transform: scale(1.8)

and I see the transition ok in all slides except when it restarts from the beginning, the whole sliding animation works fine but the scale is applied only on animation end

This saved my ass, thanks eleven59!

You just saved my day @eleven59. Thanks a lot!


Annotations can't capture high level functions

The current annotation language cannot capture the classification of high level functions like xargs.
For example, $IN | xargs cat applies the cat command on $IN and is hence stateless while $IN | xargs ls applies ls on $IN and is hence side-effectful.

@DanielSongShen We're collecting annotation-related issues in the relevant section of the README file! :-)


export IOutputData and IOutputAreaSizes interfaces

Export IOutputData and IOutputAreaSizes interfaces in order to import them from angular-split and not from angular-split/lib/interface.

Because the maintainer of angular-split clearly lost interest in maintaining it, and does seem to be interested in adding collaborators, I decided to fork this awesome library.
The fork is called ngx-split. Check the homepage, npm package and repo .
Feel free to submit PR's and I'll consider merging them! 🙏
@eranshmil I've exported the interfaces in my fork.

Hey @eranshmil, thanks for your contribution. This commit has landed in ac8b255 and should be released soon.


history trade data can generate renko?

can you have good idea?

I'm not sure I understand correctly but, you can generate a renko chart with historical market data using this library. The library cannot create visual graphics but you can generate the data (open and close prices and direction of renko bricks).

Thanks，i see  how to using this library. k line data can not explain "maoci" phenomenon. pls，you can see this picture with bule box.

Okay, got it. This feature is not yet available. I will add it as soon as possible.

666, if this library can supporting history trade data  input, this is something meaningful. i also do it haha.

Working on it.

i see you code carefully,  your code can support history trade data.  but you can solve "maoci" phenomenon. it is perfect . haha

The accuracy problem can be solved by using method “decimal” library.

you can add date of some kline data in bricks data.this infomation can confirme generate each bricks rightly.

Ok, I updated the code. The wicks are available in the output as "low" or "high" values. Also the decimals are reduced to two digits. I also added a test case "test_checkrenko.py". This test is for checking the accuracy of bricks and wicks. It compares the open, high, low and close values with tradingview's renko chart. For that, you must give first initial values manually. Here is the code description:
https://gist.github.com/aticio/604d5a6971fa79e469793dedd482b886


Thumbnails of audio/video

Description
Thumbnails of audio/video -- image that represents the video, then sub-thumbnails for time based ranges.  For video, and for ranges / different shots.
Variation(s)

Thumbnail as frame vs thumbnail as separate image.   [related to summaries]
Animated gif as a thumbnail
Summaries with key-shots etc. [related to thumbnails]

Proposed Solutions
Use existing mechanisms for association of thumbnails with Manifest, Sequence, Canvas, Range etc. Question of how to deal with more structured sets of thumbnails for key-frames etc - use annotation list of images, might need paging for many images (e.g. every 5s for a few hours).
Additional Background
Source: BL workshop notes
Interest: 100%

This has two pieces. We need a way to extract a still image out of a video in a similar way that we are able to extract a tile from a large image. This is the AV-API. I had thought that a URL like the following would work:
/identifier/temporal-slice/region/size/rotation/quality.format
This could work for still images, but what would a URL structure look like for an animated GIF? Or is that not really the still image part of the AV-API, but also part of requesting a video--whatever that video request URL might look like--but just with the format ".gif" instead of ".mp4" and then the server, if it supports that, returns whatever animated GIF it can?
The other part is the Presentation API where a still image or animated GIF could be associated with various parts of a manifest as described in the proposed solution.
Is there a case where what you want back as a summary of a section of a video is not a still image or animated GIF, but actually a video compressed in the temporal dimension? So frames could be dropped in order to do this. I know a video would be a better experience, higher quality, and with greater compression than an animated GIF. How would the AV-API support returning this kind of video summary? How would the Presentation API support using a video as a "thumbnail"?

Again, commenting here—if we define temporal slices as a start moment and a duration, this becomes a lot easier.  Then it's just <id/moment:5-duration:0/full/full/none/default.jpg>


[Feature request] More detailed collisions events

Play along also with https://github.com/MissingDeadlines/iolite/issues/16

Available in v0.5.0-beta3. Check out commit d6b9f69 for details.


Uniform setter bug in 4.1.5 (float matrix size check fails always)

Removed release 4.1.5 from pypi

https://github.com/cprogrammer1994/ModernGL/blob/master/src/UniformSetters.cpp#L717


⚠ Bofrost.es has degraded performance

In 37a1bbe, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1641 ms

Resolved: Bofrost.es performance has improved in cacf8d3 after 9 minutes.


Profile request for bencoveney

I'd like to have my profile on ghuser.io, thanks!

here you go :) https://ghuser.io/bencoveney

Awesome thanks 👍


Test mgpi

This dramatically changes the structure of the python move group tutorial so that it is testable.

live


Added support for raw queries and container-type: size

Would love to see this implemented!
I thought using an arbitrary value on the container utility class (@container-[size]) would work but for some reason, it doesn't add the CSS class. The TailwindCSS Intellisense plugin shows the correct CSS property though.

The arbitrary value not working is a bug I confirm. They have the code for it and the test code suggests this case is covered as well, although their test result expectation is missing the class, and the test is giving a false pass.
A feasible workaround for now is using arbitrary CSS:

I agree, btw, that it'd make much more sense to support all the types without the square brackets.

@container-[size] seems to work now.


Improve network briefs

Part of #335
Note: please merge #289 first, then I will resolve merge conflicts in this PR
Merge requirement checklist

[x] CONTRIBUTING.md guidelines followed.
[x] CHANGELOG.md updated for non-trivial changes.
[x] ~schema-next.yaml updated with changes to existing conventions.~

@trask https://github.com/open-telemetry/semantic-conventions/pull/289 is now merged, all good to merge this one now?


fix(code-snippet): update skeleton story info and spacing

The style wasn't really adding any space between the 2 skeleton components in the CodeSnippetSkeleton story, so I removed it and added a
 instead.
Also noticed the info was missing some text, so added that.
Changelog
Changed

remove style from CodeSnippetSkeleton, use
 instead
update CodeSnippetSkeleton info.

👋 Hello
I'm on react.carbondesignsystem and I can't seem to see that styling bug. I'm seeing the 8px margin being applied (at cursor). But I could totally just be missing something.

Hey @dakahn! I think my wording was a little ambiguous -- there's a padding being applied, not a margin. As a result, there's no "visual" spacing that I think was originally intended here?

Ah, I see. Should we add a margin attribute instead of the less-semantic
 element? Could be easier to debug in the future.

@dakahn Update is in 👍


ADD: set environment variable CSCS_APPS_PATH

I am not happy about the fact, that the path is 100 times hardcoded, but trust me I tried everything to change it and it unfortunately doesn't work...

launch jenkins icon@master%pgi

launch jenkins icon@nwp%pgi


Trigger LanguageServer recompilation on module changes

Closes #678

Subscribe to didChangeWatchedFiles notifications and trigger recompilation of any dependent files if necessary.
Trigger recompilation on documentSync notifications for dependent files where necessary.
Introduce a Workspace class to share SyntaxTree instances where possible in the Language Server.

Codecov Report

Merging #712 into main will increase coverage by 0.65%.
The diff coverage is 96.12%.

@@            Coverage Diff             @@
##             main     #712      +/-   ##
==========================================
+ Coverage   94.38%   95.04%   +0.65%
==========================================
  Files         268      268
  Lines       11150    11279     +129
  Branches       12        0      -12
==========================================
+ Hits        10524    10720     +196
+ Misses        626      559      -67

Flag
Coverage Δ

#dotnet
95.04% <96.12%> (-0.13%)
:arrow_down:

#typescript
?

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

Impacted Files
Coverage Δ

src/Bicep.Core/SemanticModel/SemanticModel.cs
95.83% <0.00%> (-4.17%)
:arrow_down:

src/Bicep.LangServer/Program.cs
0.00% <0.00%> (ø)

src/Bicep.Core/TypeSystem/TypeAssignmentVisitor.cs
98.94% <80.00%> (-0.13%)
:arrow_down:

src/Bicep.Core/FileSystem/InMemoryFileResolver.cs
95.00% <90.00%> (+20.00%)
:arrow_up:

src/Bicep.LangServer/Server.cs
92.30% <90.00%> (+0.87%)
:arrow_up:

...ntegrationTests/Helpers/MultipleMessageListener.cs
95.83% <95.83%> (ø)

....IntegrationTests/Helpers/IntegrationTestHelper.cs
96.42% <96.29%> (-0.87%)
:arrow_down:

src/Bicep.Cli.IntegrationTests/ProgramTests.cs
100.00% <100.00%> (ø)

src/Bicep.Cli/Program.cs
92.50% <100.00%> (ø)

...Core.IntegrationTests/Emit/TemplateEmitterTests.cs
100.00% <100.00%> (ø)

... and 30 more


If this and that, merge this pull-request bot

I was briefly surfing and observing, is there bot which merges based on labels and conditions?
I mean when there are labels like these, would make sense to have bit control over merging.
Auto-merge iirc can do only when approvals are there which are more from code perspective and all tests are green, but won't tell anything about breaking UX or visuals.
If you have any ideas, hit this up with suggestions and I will pick it up whenever

Something like @polkadot-js-bot, or Mergify

It has GPT-inside? https://github.com/polkadot-js/apps/issues/9571#issue-1751770388


Fix pager with stdin

When stdin is supplied without file names, display the stdin in the pager instead of opening a file.

Fixed with 18aa2c2900c57009fd9c2f73c933cad1c8ce51e0.


tiltfile: make entrypoint an optional parameter

Still waiting to be able to test this on master before I call it "done done".

A consequence of this PR is that we no longer try to validate that things are set up correctly for k8s to execute the manifest. The philosophy than @dbentley imparted on me is that we should be transparent enough about what k8s is doing that it will be obvious why it has failed, rather than try to predict every failure case.

I'm going to merge this now because, technically, it is a backwards compatible change.


AsyncProcess: Apply @Sendable annotation to address compiler warning

@swift-ci test

Does this also fail because of outdated CI?

I think so, I believe we downgraded that to a warning at some point.


refactor: Structural output Android models describe

Fixes #1846
Test Plan

How do we know the code works?

Code is refactored according to #1846
Android describe models command works like previously

Checklist

[x] Unit tested

small required change from @pawelpasterz

@Sloox fixed


Please update SCSS files.

The SCSS code does not match the LESS code. For example, the "icono-next" class:
/* next.less */
.icono-next{
    width: 0;
    height: 0;
    border: @10 solid transparent;
    border-left: @10 solid;
    border-right: none;
    margin: @7 @14 @7 @10;
    box-shadow: @4 0;
}

/* next.scss */
.icono-next{
    width: 0;
    height: 0;
    border: $U10 solid transparent;
    border-left: $U10 solid;
    margin: $U7;
    &:before{
        position: absolute;
        left: 0;
        top: -$U10;
        width: 0;
        height: 0;
        border-width: $U10 $U3 $U10 $U3;
        border-style: solid;
    }
}

I was wondering why my icon wasn't rendering correctly - then I went into the developer console, changed styles to match the LESS rules, and it worked. Don't know why bad styles are left over in the SCSS code, but it would be great if they stayed in sync.
Perhaps there should be a build-time test script that checks if the SCSS and LESS compiled output are identical, and displays a warning if not.

I preferred add Stylus version


Apparent framework build errors

Description
Getting Apparent framework build errors for ios, which may be impacting gesture recognition.
A simple test that I have shaved down to the below will pass without the tap() line (so the element is visible) but times out with it:
  await expect(element(by.id('landing-welcome-screen'))).toBeVisible();
  await expect(element(by.id('login-button'))).toBeVisible();
  await element(by.id('login-button')).tap();

test video shows that the button actually is tapped successfully and the app then moves to the next screen as expected - behavior is all correct.
log trace shows at timeout:
12:41:22.493 detox[39990] INFO:  [APP_STATUS] The app is busy with the following tasks:
• Run loop "Main Run Loop" is awake.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
• The event "Gesture Recognizer" is taking place with object: "<LROTouchShim: 0x600002632500; baseClass = UIGestureRecognizer; state = Possible; cancelsTouchesInView = NO; delaysTouchesEnded = NO; view = <UIWindow 0x7ff4ec91a650>>".

12:41:23.159 detox[39990] WARN:  [PENDING_REQUESTS] The app has not responded to the network requests below:
  (id = 7) invoke: {"type":"action","action":"tap","predicate":{"type":"id","value":"login-button"}}

That might be the reason why the test "Billing Methods: Credit Card should allow adding a credit card, that is set to default" has timed out.
Seems the gesture recognizer is broken.  Which makes my framework build log, below, interesting.  I have some setting off it seems, or at least that would be an easy answer - any pointers on getting it right much appreciated.
cat ~/Library/Detox/ios/e17b1e09a76e6b007a64badff57423ef49ef2e5c/detox_ios.log
Xcode 12 and above; using modern script for building the framework to support Apple Silicon
Using -UseNewBuildSystem=YES
2022-04-10 08:44:01.145 xcodebuild[68041:15448382] XType: com.apple.fonts is not accessible.
2022-04-10 08:44:01.145 xcodebuild[68041:15448382] XType: XTFontStaticRegistry is enabled.
/Users/builder/Library/Developer/Xcode/DerivedData/Detox-awkysymaalbifmciinhfkayhhhev/Build/Products/Release-iphonesimulator
2022-04-10 08:44:41.409 xcodebuild[68146:15448898] XType: com.apple.fonts is not accessible.
2022-04-10 08:44:41.409 xcodebuild[68146:15448898] XType: XTFontStaticRegistry is enabled.
/Users/builder/work/detox/ios/COSTouchVisualizer/Classes/COSTouchVisualizerWindow.m:187:21: warning: enumeration values 'UITouchPhaseRegionEntered', 'UITouchPhaseRegionMoved', and 'UITouchPhaseRegionExited' not handled in switch [-Wswitch]
            switch (touch.phase) {
                    ^
/Users/builder/work/detox/ios/COSTouchVisualizer/Classes/COSTouchVisualizerWindow.m:187:21: note: add missing switch cases
            switch (touch.phase) {
                    ^
1 warning generated.
error: the following command failed with exit code 0 but produced no further output
CompileC /Users/builder/Library/Developer/Xcode/DerivedData/Detox-awkysymaalbifmciinhfkayhhhev/Build/Intermediates.noindex/COSTouchVisualizer.build/Release-iphonesimulator/COSTouchVisualizer.build/Objects-normal/i386/COSTouchVisualizerWindow.o /Users/builder/work/detox/ios/COSTouchVisualizer/Classes/COSTouchVisualizerWindow.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in target 'COSTouchVisualizer' from project 'COSTouchVisualizer')
error: the following command failed with exit code 0 but produced no further output
CompileC /Users/builder/Library/Developer/Xcode/DerivedData/Detox-awkysymaalbifmciinhfkayhhhev/Build/Intermediates.noindex/COSTouchVisualizer.build/Release-iphonesimulator/COSTouchVisualizer.build/Objects-normal/arm64/COSTouchVisualizerWindow.o /Users/builder/work/detox/ios/COSTouchVisualizer/Classes/COSTouchVisualizerWindow.m normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in target 'COSTouchVisualizer' from project 'COSTouchVisualizer')
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingRuntime.cpp.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingFile.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingWriter.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingPlatformDarwin.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingMerge.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingBiasVar.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingBuffer.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingNameVar.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfiling.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingUtil.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingValue.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingMergeFile.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingInternal.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingVersionVar.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingRuntime.cpp.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingFile.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingWriter.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingPlatformDarwin.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingMerge.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingBiasVar.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingBuffer.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingNameVar.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfiling.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingUtil.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingValue.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingMergeFile.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingInternal.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
ld: warning: object file (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.profile_iossim.a(InstrProfilingVersionVar.c.o)) was built for newer iOS Simulator version (9.0) than being linked (8.0)
note: Using new build system
note: Planning
note: Build preparation complete
note: Building targets in parallel
/Users/builder/work/detox/ios/COSTouchVisualizer/Classes/COSTouchVisualizer.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.0.99. (in target 'COSTouchVisualizer' from project 'COSTouchVisualizer')

Your environment
Detox version: 19.6.4
XCode 13.3
React Native version: 0.64.3
Node version: 16.13
Device model: iPhone Max Pro
OS: Mac OS 12.2.1
Test-runner (select one): XXXXjest-circusXXXX / jest+jasmine / mocha / other
This is Expo built with EAS, which I know you do not support, but it is a production build not Expo-go so I think that it doesn't matter, except that I have little control over project build settings.

@asafkorem I'm not sure what's really behind:
The event "Gesture Recognizer" is taking place with object: (...)

Which resource does this refer to?

Thanks for looking at this.
This is using vanilla https://callstack.github.io/react-native-paper/ for the button, and in general that framework certainly works with Detox, so I don't think it is a general low level Apple related implementation issue.
You don't think is related to the framework build errors on the mismatched linkage between 8.0 and 9.0 targets?

Don't have easy access to the Podfile since this is Expo.  But for whatever reason, the upgrade to Expo SDK 45 fixed this, thanks for looking into it.

Don't have easy access to the Podfile since this is Expo. But for whatever reason, the upgrade to Expo SDK 45 fixed this, thanks for looking into it.

Oh, I see.. that's great 😄
I'm closing this issue. Please let me know if you need any further help with that.


fix image build failure

Running ldconfig seems to fix last build issue(vpu plugin image):
...
# pkg-config --cflags  -- libusb-1.0
pkg-config: error while loading shared libraries: libglib-2.0.so.0: cannot open shared object file: No such file or directory
...
##[error]Process completed with exit code 2.

This blocks a lot of pending PRs, so please review & merge. Thanks.
Fixes #336

@mythi feel free to remove it when the issue is fixed. However, for now I'd prefer not to have master broken and PRs pending in red status.

@bart0sh you're right, thanks for this PR!


fix(curriculum): replace instance of var with let

Checklist:

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

Closes #48554

Replace instance of var with let in javascript global scope challenge, ENGLISH ONLY.

Should the files in other languages also be updated?


Issues pagination

@otech47 I tested this PR and it's working. Didn't understand the last comment you did, if you could explain me

Shouldn't we have defaults here if these are not provided? They would be undefined no?


MacOS: "Window: Click Through Inactive" does not work for creating new files/folders

VS Code Version: 1.73.1
OS Version: 12.5

A setting to allow single-click window activation was added to VS Code in 2018 (#24634); however, this feature doesn't apply to the creation of new files and folders within the Explorer.
Steps to Reproduce:

Ensure another window is active (i.e. the browser)
Right-click in the Explorer and click New File or New Folder. This works, but typing focus is not given to the file/folder name field, so it is not possible to actually create the file/folder.

Attempting to click into the file/folder name field in order to give it focus just makes it disappear.

\duplicate https://github.com/microsoft/vscode/issues/149818

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Warning: React does not recognize the transitionAppear prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase transitionappear instead.

I am using the redux-form-material-ui DatePicker as described in the docs. However it just throws these errors.
React does not recognize the transitionAppear, transitionAppearTimeout, transitionEnter and transitionEnterTimeout props on DOM element...
I checked it in the developer tools and these transition properties are actually passing down to the child div from it's parent CSSTransitionGroup.
Due to this, the DatePicker dialog is not working as expected. I have already spent more than a day on this but can't seem to get it working. Please help me out!

What version of React / MUI you're using?

@mihirsoni
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

I'm having the same issue.
i got the following versions:
<EMAIL_ADDRESS><EMAIL_ADDRESS>

@dsaket
It seems this issues should be on MUI side and not on this lib. If you look at code this lib doesn't manipulate any props.
https://github.com/erikras/redux-form-material-ui/blob/6cb4fcefb51204a2a8ac51fed30aa1806fd7fc09/src/DatePicker.js#L5-L19

@julianklumpers

If you're using MUI beta then you should be using next version of this lib
Calendar is not yet implemented in this lib, I will take some time on weekend or if you could send PR would be great.

I do have same problem. Do you have any suggestion?

I can reproduce this as well using material-ui 1.x and 5.0+ version of this lib.

I have published new version on next, let me know if issue still persist.
Closing this for now, feel free to reopen if issue still persist.


install flask-cors - enable in www/app.py

installing flask-cors module and enabling in app.py allows a web-based script (such as IOS shortcut to running javascript) to access the rig's local web server for retrieving JSON information such as BG records, IOB, COB, Temp Basal/Duration, Battery Percentage, etc.

I added two more json endpoints for the web service.
cgm - the xdripjs cgm pill json record
hostname - the hostname of the rig. This is important for ensuring the calling application / script is accessing the correct rig and can display the rig hostname to the user. Since many use multiple rigs per person and multiple family members with rigs, it is important to know which rig the data is coming from.

Anyone know why Travis integration tests are failing? I can't tell by looking at the details what I did to break them.

Tested out good for me.

Yes, it's all working for me in my tests from my browsers on my laptop and from my phone.


Link Component — renders an absolute URL as a relative href

[ ] Docs
[x] Tests

Testing Strategy:
run yarn bug-report-test

Thanks @thomasverleye!  I confirmed this is fixed if I update Remix to use<EMAIL_ADDRESS>which includes your fix over there.  Since we've got it tested over in the router I'm going to close this out 👍


Fix download links for translation test data.

The test data appears to have moved. Updated the links with the current location.

On Monday we can find more permanent links which are not into github... but these links should last us a few weeks at least ;)

This file works locally... merging.


Mod not marked as supporting 1.12.2

Hi, this mod is not marked as 1.12.2. I assume it works on that version since there's a 1.12 marked version.
https://minecraft.curseforge.com/projects/more-overlays/files
please mark the 1.12 file as 1.12.2 too.
This "broke" my updater script.

I see you fixed it, thanks!


OnePiece.Commanded.Event with JsonbSerializer and events evolution

Problem Statement
Sorry for bringing it up here, I tried to find OnePiece.Commanded-related discussions on ElixirForum but didn't find any, and this is quite specific one, so I decided to give a shot here.
I'm trying to use OnePiece.Commanded to my new project and evaluating an option to use its JsonbSerializer. It expects to have all events built agains the Event module or at least have a new!/1 function.
As I understand, the idea of the ObjectValue sitting underneath the Event is to use Ecto to deserialize supported types into a runtime event struct, and this is totally legit and sound.
The question is what scenario you think would be the best in the feature when it is necessary to evolve events?
Solution Brainstorm
I'm not a big fan of keeping old structures just to support legacy, it brings a lot of confusion and mistakes during development, especially when a team is big enough. With the Upcaster protocol implementation it is possible to update some event's fields to the new shape or even build a completely new current runtime event representation. But if we keep only the current shape of the event structure it would break casting: either silently when some fields just don't get their way into a pre-upcasted structure or loudly, when fields just can't be casted anymore. The original Commanded JsonDecoder protocol gives the power to cast specific values to the event-specific implementation. But if we enforce casting right after reading an event from the event store - it won't work. And yes, it is possible to redefine the new!/1 method to do things there, but then it replaces the Upcaster protocol in many ways and requires using internal ValueObject implementation functions to continue casting.
I understand that it is possible to just continue to use the original scenario with Commanded JsonDecoder, but I would kindly ask to share your thoughts on the topic if you don't mind.

Can you share the precise up-casting you would like to perform? So, we set the proper context, which narrows down the decision-making.
Sometimes, it is a matter of documenting a different perspective.

Sorry for bringing it up here; I tried to find OnePiece.Commanded-related discussions on ElixirForum but didn't find any, and this is quite specific one, so I decided to give a shot here.

I am not active in ElixirForum and barely check there. You could bring the problem here!

I think it is worth sharing the intent of why it was left out; I am not saying I am right, nor am I opposed to changing it, to be extra precise.
I believe "the past can never change." This implies that you must handle the past as is, with no breaking changes ever.
Up-casting practices "mask" the past, and I found that it is much more troublesome sometimes than not.
In practice, if we mess up badly, we cut a v2 stream because of such an unreliable stream and remove the problems altogether. That does not mean we changed the past, but we agree that moving forward, we should not do anything about that past or ignore it.

I'm not a big fan of keeping old structures just to support legacy,

I think this is where we disagree. My intent was that you never remove such Events. You could ignore them, but you must keep them around and Up-Cast to whatever you want. But, at the very least, your code shows the past. It does not hide it behind transformation that "does require" understanding the past anyway. So even if you remove such old structure, it is still there, just that it is even more confusing, hidden behind runtime code that can not be statically analyzed. More problems than keeping them data structures around.

evaluating an option to use its JsonbSerializer.

Side note: I can take an implementation to be JSON and bytes; there is no reason not to do that either!

Thanks for the answer!

Side note: I can take an implementation to be JSON and bytes; there is no reason not to do that either!

I believe that jsonb is the best option for now. Sometimes it is necessary to work with raw data when debugging or doing one-time investigation of something, and jsonb allows to make queries and get indexes to do it faster. The bytea and term_to_binary has one huge downside which we recently hit: the resulting binary can change in the future versions. It`s not a big problem for events as long as it is possible to decode them to the same structure, but still a bit risky: compatibility guaranteed for two OTP major versions only.

I believe "the past can never change." This implies that you must handle the past as is, with no breaking changes ever.
Up-casting practices "mask" the past, and I found that it is much more troublesome sometimes than not.

I agree with the idea that "the past never changes" and it doesn't (I mean, you can't go back and change a fact), but I think that events are not "the past", it's just a model, a perception or a projection of what happened. And with time we can realize that our perception was incomplete or incorrect. And thus, we don't change the representation we had before, but from some point we should start to work with a new representation. It is inevitable: things are changing, in the real life as well.
For example, we realized that it is not enough to register a date only, we need a timestamp. We would change the field type in the event schema, I believe nobody would create a new event with all the fields for that.
Another a bit less simple example: we had an address as a string, but then our business process changed, and now to better represent it we need a structure with separated country, zip, city and street. From now on the runtime will issue the new events with an address as a struct. But what to do with the old ones? We can't request all consumers to support both versions, it would be a nightmare.
I thought about a solution quite much, all options have cons, there is no the ideal one exists, but I found that adding an __event_version__ field to the event struct is a good trade-off: we don't clutter the code with Event, EventV1, EventV2 etc (from my experience: someone will definitely use the wrong version if it is possible to choose from, or forget to update to the newest one if the old one is still in the system; but changing types in the current version would break tests, so it is much more noticeable). I wrote a simple wrapper which is using the TypedStruct underneath, got a guard and a version alter function to hide implementation, and now it is possible to define an event like this:
defmodule SomeEvent do
   use EventStruct

  event_struct enforce: true do
    field :user_id, String.t()
    field :address, String.t()
  end
end

this will add an additional field to the struct with the default value 1.
Then when you need to evolve the event you can just change the default version and define the Upcaster implementation:
defmodule SomeEvent do
   use EventStruct

  event_struct enforce: true, version: 2 do
    field :user_id, String.t()
    field :address, map()
  end
end

defimpl Commanded.Event.Upcaster, for: SomeEvent do
  import EventStruct, only: [increment_version: 1, version: 1]

  def upcast(%SomeEvent{} = event, _metadata) when version(event) == 1 do
    %{event | address: tranfsorm_address_to_struct(event.address)}
    |> increment_version()
  end

  def upcast(event, _metadata), do: event

  defp tranfsorm_address_to_struct(address) when is_string(address), do: %{}
end

The main downside is that now we get a field inside each event which has only technical meaning. But that's fine for me: it clearly shows the evolution of the event. And this approach delegates all responsibility to build the correct current representation of an event to the event module itself. Commanded.Serialization.JsonDecoder is also delegates that responsibility to the event module and the event-specific implementation of the protocol.
Currently my team is using a custom serializer, which works quite well with some precaution, but I don't like that approach, it keeps implementation details inside events themselves (like struct names etc). As any module renaming will hurt in this case (unless mapping is specified in the deserializer itself) we decided to reduce usage of external structures to the bare minimum, but anyway, it doesn't scale well in the long run from my point of view. So, I'm trying to find another solution for my pet project, and if it works - to bring it to the bigger production scale.
I thought a lot about using Ecto casting to deserialize events, but exactly the problem I started with stops me from that. So, I'm trying to find a solution.
A side note too: anyway, I'm starting a new pet project with OnePiece.Commanded primitives (with the only addition is that I also made a similar VerionedEctoSchema module to add the version field and automatically generate types for the schema itself) and will see where it brings me. As all of that are the runtime things, it is easy to change implementation later. Maybe I will try to use PolymorphicEctoEmbed lib, but this would require external modules and I'm not sure it would work all together.

@vheathen any updates about your experience? I would love to learn from it if possible

@yordis Sorry, somehow, I missed the previous message.
I can't tell much for now. I haven't got a chance to evolve events, but I found a way to do that if necessary while keeping only last schemas. It isn't completely pretty, but at least gives a chance to do the trick.
Also, I introduced OnePiece.Commanded to my team, and they are actually quite happy about some conceptions in it. So, I can thank you for this library again, this time from them :)

@vheathen btw, related to the topic https://youtu.be/W7mpfjW7nhw?si=cSEbhYO2leYygs4k&t=2491 timestamp: 41:31

@yordis
I've looked at the upcaster part of that episode, thank you, very interesting!
I can't tell I completely agree though.
I believe that there is more than the only one "right" way to do things. We are developers, and we use approaches which suit better for the purpose. The only part actually "carved in stone" is our events, we should not change them, and we don't change them [until there is really no other way to do that, but this is another topic]. The runtime code is flexible, in theory we can ditch all of it and rewrite in a different language, with different approach if necessary. We have our history in the event streams containing original events, inside the event store.
And we always have trade-offs.
One place to deal with changes or multiple places? We need to remember that every new projection would need to support all history of these similar events. Do we actually need all of the changes in all subscribers? If not, and if we just use a new version of the same event, in most cases we don't even need to modify projections which don't need those changes (let's think about registration of a new user and a projection which needs only name/email, for example, and don't care about any other info like birth date or address or eye color).
Does the event change its meaning or just gets additional information we didn't think we need before (either because of bad design or new requirements/business process updates)?
Do we get a new field (or multiple), or we need to modify an existing one (birth date vs address representation)?
And, at the end, how do we name those new events in case the meaning is the same? Do we add "version" suffix to the new events?
One of the most important things from my point of view: do we think it worth to add additional cognitive load to the developers? Sometimes it's really hard to understand which events are actual, and which are not. Keeping only actual event versions runtime can reduce that load much, I can tell that from my own experience.
But my main idea is to use tools the most suitable for the task. So, in some cases this would be adding a new event along with the current one, in other cases it can be event upcasting.


fix: change isTSX option to opt-in

🔗 Linked issue
Fixes: https://github.com/nuxt/bridge/issues/1063

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
If you add isTSX, you cannot use angle-bracket syntax.
We would like to change it to opt-in as it would be inconvenient for users who do not use tsx.
(If it were possible to replace esbuild, I would replace it.)

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

It can also be resolved at https://github.com/nuxt/bridge/pull/1065.
I will open this if the migration to esbuild does not work.

Shouldn't we stick to simple fixes like this one instead of migrating the whole build to esbuild? The latter sounds risky and I'm not sure if adding more work to Nuxt 2 which is in maintenance mode makes sense.

Is it possible to enable this plugin per webpack rule so that we can target the one without isTSX for typescript files and one with isTSX for jsx/tsx?
Though maybe vue files would still be problematic since those don't explicitly state whether they are using tsx or not. But then the opt-in could be for vue files only rather than global.

Shouldn't we stick to simple fixes like this one instead of migrating the whole build to esbuild?

Yes, I agree.
I am planning to introduce the migration to esbuild to reduce the differences with Nuxt 3.
(Nuxt Bridge is an upward compatible library)


Revert: reducing scope of informer

Reverts this PR https://github.com/grafana/beyla/pull/1210
We did the wrong assumption that global entities were only required for Network Metrics. But service graph metrics also require being decorated from cluster-wide pods.
Since we are working on a definitive solution based on external informers caches, I'm just reverting this change to avoid bugs and simplifying the code.

Codecov Report
Attention: Patch coverage is 90.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 53.16%. Comparing base (8c3c9db) to head (27ca29f).

Files with missing lines
Patch %
Lines

pkg/internal/kube/informer_provider.go
0.00%
1 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (8c3c9db) and HEAD (27ca29f). Click for more details.
HEAD has 3 uploads less than BASE

Flag
BASE (8c3c9db)
HEAD (27ca29f)

oats-test
1
0

k8s-integration-test
1
0

integration-test
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1245       +/-   ##
===========================================
- Coverage   81.89%   53.16%   -28.74%
===========================================
  Files         137      137
  Lines       11489    11470       -19
===========================================
- Hits         9409     6098     -3311
- Misses       1544     4976     +3432
+ Partials      536      396      -140

Flag
Coverage Δ

integration-test
?

k8s-integration-test
?

oats-test
?

unittests
53.16% <90.00%> (+0.04%)
:arrow_up:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

But service graph metrics also require being decorated from cluster-wide pods.

Oh shoot! Agree on having one solution for this problem.


Adopt VS Code's 'asWebviewUri' API

Hi, I maintain VS Code's Webview API
Issue
Our telemetry suggests that your extension uses webviews and may be loading resources in these webviews using hardcoded vscode-resource: URIs. These URIs have some important limitations and don't work properly when VS Code is run in a browser. We are also making changes in the desktop version of VS Code that may cause these URIs to not work properly in future versions of VS Code.
While we are making our best effort to continue support existing webview extensions that use vscode-resource: URIs on desktop versions of VS Code, we will not able to fully support all uses cases.
Fix
To ensure that your extension continues to work in as many environments as possible—including on web and remotely—please:

Switch to use the Webview.asWebviewUri function for loading resources.

Switch to use the Webview.cspSource property in content security policies.

These APIs shipped around 2 years ago so they should be available in all modern versions of VS Code. You can find additional information about the issue here: https://github.com/microsoft/vscode/issues/97962
Let me know if you have any questions about this change

We don't have hardcoded vscode-resource:. We will cache the final html on the hard disk, I think your telemetry just scanned the cached result.

Please just make sure that any html use by your webviews does not use vscode-resource anymore


Price Elasticity endpoint is added

#423

@ighoshsubho please review my pr

Great @shraddha761, Your PR got merged! Keep contributing like this in GSSOC'23!


swift3 branch only support iOS10, how can it integrate on deployment target of iOS8?

AFAIK Alamofire is supporting iOS 9.0 and up because they're dropping support for the two year-old iOS 8.0 in Alamofire version 4.0. So either you can stay on the commit before "update podspec" or you can use the master branch for now (before it gets bumped to 4.0 too). The median solution would be to deploy your app for iOS 9


Improve unit testing

Unit testing is now easier to implement thanks to #125, which also introduced a suite of unit tests that take advantage of PyTest. The test suite is still underdeveloped and could use some additional work.

Leaving this comment as reminder to implement codecoverage and identify sections of the code that would benefit from improved unit testing


Automate releases

Current releases are fully manual (which includes manual version update, manual workflow execution, etc.). In addition, we don't use GitHub releases.
So, ideally if we have the following:

Repository admin creates a new release on GitHub
We start workflow which updates repository version according to release (how?) - that is needed for badges.
We publish artifacts to Gradle Plugin Portal and documentation to GitHub.io.
3.1. Ideally if we can patch documentation without a release.

Note #54

We should also automate the creation of a GitHub Release and Tag as well 👍


Forcing a square crop view

Forcing an always square crop view would a nice addition :-)

I would also appreciate this option

I also will appreciate!
it seems that this fork repository has the option.
https://github.com/apshoemaker/PhotoTweaks


Vendor latest container/storage to fix overlay mountopt

Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

bot, restest this please

@rh-atomic-bot r+


Derive stringly and numeric ToVariant for fieldless enums

Adds the #[variant(enum = "repr")] and #[variant(enum = "str")] item-level attribute to the Variant conversion derive macros for fieldless enums.

#[variant(enum = "repr")] - convert through the numeric type specified using #[repr].
#[variant(enum = "str")] - convert through string representations of the variant names.

Close #546.

Should be ready for review now!

Ah yes, thanks for reminding me! Got a bit lazy with the rebase here. I'll make a PR for the docs later.


Call static methods on momentjs in the correct locale.

The moment service allows the user to set a locale for the app, but it doesn't change the global moment locale. Instead, it sets a locale in the service and the the service.moment() method applies the locale and timezone every time it's called.
Is this behaviour (not changing the global locale) intended? Why?
Assuming it is, now to the real question. MomentJS has a few "static" methods that are locale-dependent. By example, for getting the name of the days of the week you can do moment.weekdays(). Note that this methods cannot be called on a moment instance, they are methods on the global.
I need those methods to be locale-dependent, so I resorted to this helper function:
function withLocale(locale, fn) {
  let returnValue;
  if (locale) {
    let previousLocale = moment.locale();
    moment.locale(locale);
    returnValue = fn();
    moment.locale(previousLocale);
  } else {
    returnValue = fn();
  }
  return returnValue;
}

Then, when I want to call a static method in, I do:
withLocale('fr', () => moment.weekdaysShort());

Would to consider such static method to be on the moment service so it uses the set locale automatically?
Example:
momentService.localize((moment) => moment.weekdays());

The implementation would be something like:
localize(fn) {
  let returnValue;
  let locale = this.get('locale');
  if (locale) {
    let previousLocale = moment.locale();
    moment.locale(locale);
    returnValue = fn(moment);
    moment.locale(previousLocale);
  } else {
    returnValue = fn(moment);
  }
  return returnValue;
}

Sounds good?

Is this behaviour (not changing the global locale) intended? Why?

The scope of the locale stays scoped to the app instance versus being an app global.  I feel this has some benefits for testing, instances where someone might have multiple Ember apps running, etc.
That said, I'm still opened to consider setting the global and/or your recommendation for a localize service utility method..

Assuming it is, now to the real question. MomentJS has a few "static" methods that are locale-dependent. By example, for getting the name of the days of the week you can do moment.weekdays(). Note that this methods cannot be called on a moment instance, they are methods on the global.

@cibernox - With regard to the weekdays() method, this might help, I was able to grab the weekdays in the correct locale without as much of a work around doing this: momentService.moment().localeData().weekdaysShort()[index]
@jasonmit - I'm using the moment service in my application and where I'm running into the issue of not having the global locale changed is with the helpers because those reference the global instance of moment. I see where you'd want to keep the locale scoped to the service because of testing, however, anywhere the helpers are used it is using a different reference. It may be helpful to convert the helpers to using the service instead of global moment.

7.3.0 resolves this


Support Sonoff L1 LED Strip

It would be awesome with Sonoff LED strip. I'm sorted by most requested functions.

On/Off
Change color
Brightness
Mode

Coloful
Sync to music
Coloful Gradient
...

@ebattulga I don't have this one. Could you send some debug logs?

From another Sonoff-integration that I tried.
Mode 1: Colorful
Mode 2: Colorful gradient
Mode 3: Colorful Breath
Mode 4: DIY Gradient
Mode 5: DIY Pulse
Mode 6: DIY Breath
Mode 7: DIY Strobe
Mode 8: RGB Gradient
Mode 9: RGB Pulse
Mode 10: RGB Breath
Mode 11: RBG Strobe
Mode 12: Sync to music
sonoff.L1.txt
sonoff-debug.txt
Hope it can help!

@AcidSleeper I see firmware version 2.7.0.
Devices of this version should work in local mode only with the Internet turned off.
Have you blocked your device Internet?
Is there a newer firmware version?

No newer version in eWeLink app.
After installing integration in Home assistant via HACS and putting minimum requirements in configuration.yaml the device dont appear.
The .sonoff.json file that gets created indicates it downloads the Sonoff L1 from server but dont appear in Home assistant

@AcidSleeper can you:

enable debug log
block Internet
restart device and HA
switch strip through remote
check your logs

Code for debug you want?
Block internet for Sonoff L1?
Switch strip? On/Off?

Enable debug logs:

  default: info
  logs:
    custom_components.sonoff: debug```

2. Yes. Block Internet for Sonoff L1?

3. Yes. On/Off

Nothing happens!
HA dont produces a log!

@AcidSleeper do you have telegram? Can you write to me there?

Discord?

This is whats get created in .sonoff.json
{"1000990af7":{"settings":{"opsNotify":0,"opsHistory":1,"alarmNotify":1,"wxAlarmNotify":0,"wxOpsNotify":0,"wxDoorbellNotify":0},"group":"","online":false,"shareUsersInfo":[],"groups":[],"devGroups":[],"_id":"5d85d8ec8ff123e94fe13da9","name":"Sonoff Led1","type":"10","deviceid":"1000990af7","apikey":"REDACTED","extra":{"extra":{"uiid":59,"description":"20190703002","brandId":"5c4c1aee3a7d24c7100be054","apmac":"REDACTED","mac":"REDACTED","ui":"律动灯带","modelInfo":"5c700fabcc248c47441fd241","model":"PSF-BTA-GL","manufacturer":"深圳松诺技术有限公司","staMac":"REDACTED"},"_id":"5d1c529c2fb3e272ea638b13"},"createdAt":"2019-09-21T08:01:48.995Z","__v":0,"onlineTime":"2020-02-10T11:02:54.221Z","ip":"<IP_ADDRESS>","location":"","params":{"sledOnline":"on","rssi":-67,"fwVersion":"2.7.0","staMac":"REDACTED","switch":"on","light_type":1,"colorR":255,"colorG":255,"colorB":255,"bright":100,"mode":2,"speed":100,"sensitive":10},"offlineTime":"2020-02-15T15:20:44.294Z","deviceStatus":"","sharedTo":[],"devicekey":"REDACTED","deviceUrl":"https://eu-api.coolkit.cc/api/detail/5c700fabcc248c47441fd241_en.html","brandName":"SONOFF","showBrand":true,"brandLogoUrl":"https://eu-ota.coolkit.cc/logo/Q4RJzznuKEeDgFXbgyS9OClbyEDR7gXd.png","productModel":"L1","devConfig":{},"uiid":59}}

@AcidSleeper Discord: AlexxIT#0816

Here #31

Is there any new progress in the project? I have an L1 light strip. What do I need to do?

{"1000a2ac7d":{"settings":{"opsNotify":0,"opsHistory":1,"alarmNotify":1,"wxAlarmNotify":0,"wxOpsNotify":0,"wxDoorbellNotify":0,"appDoorbellNotify":1},"group":"","online":true,"shareUsersInfo":[],"groups":[],"devGroups":[],"_id":"5db6cd68eafb2786263c3515","name":"主卧灯带","type":"10","deviceid":"1000a2ac7d","apikey":"8c236797-5fa2-4854-ae0b-c8101facadd4","extra":{"extra":{"model":"PSF-BTA-GL","ui":"律动灯带","uiid":59,"description":"20190814007","manufacturer":"深圳市阳溢电子商务有限公司","mac":"d0:27:01:45:56:4a","apmac":"d0:27:01:45:56:4b","modelInfo":"5ba1dcf777db4c0c7324041a","brandId":"5a03b77c6ed24cfc5975198e","staMac":"D8:F1:5B:8C:24:70"},"_id":"5d54ff6613451dda060dd489"},"createdAt":"2020-02-01T10:40:11.679Z","__v":0,"onlineTime":"2020-04-12T07:33:45.952Z","ip":"<IP_ADDRESS>","location":"山东","params":{"sledOnline":"on","rssi":-69,"fwVersion":"2.7.0","staMac":"D8:F1:5B:8C:24:70","switch":"off","light_type":1,"colorR":255,"colorG":183,"colorB":0,"bright":57,"mode":1,"speed":30,"sensitive":2,"bindInfos":{"aligenie":["8c236797-5fa2-4854-ae0b-c8101facadd4_33d17855f659bbea8279ac74a01f24f196a929bb"],"miot":["8c236797-5fa2-4854-ae0b-c8101facadd4_ewelink-miot-v1"]},"timers":[],"partnerApikey":"55b441f6-f692-438d-82f0-3338da3baef8"},"offlineTime":"2020-04-12T07:33:21.599Z","deviceStatus":"","sharedTo":[],"devicekey":"4c9bf94b-a7a8-4368-be46-c1a04dbbd857","deviceUrl":"","brandName":"ABC","showBrand":false,"brandLogoUrl":"","productModel":"2.0-led","devConfig":{},"uiid":59}}

2020-04-15 22:40:00 DEBUG (MainThread) [custom_components.sonoff.utils] Init zeroconf singleton
2020-04-15 22:40:00 DEBUG (MainThread) [custom_components.sonoff] Update device config 1000a2ac7d
2020-04-15 22:40:00 DEBUG (MainThread) [custom_components.sonoff.utils] Generate zeroconf singleton
2020-04-15 22:40:02 DEBUG (SyncWorker_17) [custom_components.sonoff.utils] Use zeroconf singleton

Try new version #99

Supported


pymethods: prevent methods sharing the same name

This PR tweaks the #[pymethods] code generation so that the generated functions have meaningful names and are members of the associated class.
In general, the structure of generated code has changed from
unsafe extern "C" fn __wrap(...) { ... }

to
impl SomeClass {
    unsafe extern "C" fn __pymethod_foo__(...) { ... }
}

There are a few nice benefits that this brings:

As the generated function names are based on their names exposed to Python, and they share the struct's namespace, it's not possible to have multiple pymethods with the same #[pyo3(name = "foo")].
We have a hack to replace_self to remove Self from generated code; we don't need this now the generated code is associated with the class.
Stack traces will be nicer in panic messages etc, because the frames will have meaningful names rather than __wrap (that was actually what motivated me to try this today as I was struggling to debug #2302; this idea's been in the back of my mind for a while)

Thanks, this should make reading cargo expand output a bit nicer too :)

Also true! While working on this I also realised that (with some extra work) it might be possible to rearrange the generated code so that we just add all these generated methods in a single impl SomeClass block, which might reduce the visual complexity of the generated output further.


refactor: Use controller-runtime client to read crd's

:tada: This PR is included in version 3.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Adding explicit code for deleting ApiServer resource when service instance deletion is successful

With previous changes in BoshTaskStatusPoller codeflow, deletion of ApiServer resources was not happening at the end of service instance deletion operation.

In this PR, explicit code to delete the corresponding ApiServer resource at the end of deletion is added.

Pull Request Test Coverage Report for Build 2043

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.146%

Totals

Change from base Build 2039:
0.0%

Covered Lines:
8281

Relevant Lines:
8989

💛  - Coveralls


Create Subscription

 Code Climate has analyzed this pull request.

I think you can change the name this Subscription class to something like SubscriptionPlan.


Support RTL languages natively

Is your feature request related to a problem? Please describe.
Out of the box, the theme doesn't support right to left languages like Arabic, Persian, and Hebrew.
To be able to use the theme for my personal website, both versions (English and Arabic), I had to do some CSS workarounds to make the theme work nicely with RTL content (still has many things that doesn't).
But I think having native compatibility with RTL would be a huge plus for our theme.
Describe the solution you'd like
Ideally, we can do the following:

Add a LanguageDirection variable, that should be ltr by default, and rtl if the user set the language to be so.

<html lang="{{ .Site.LanguageCode }}" dir="{{ default `ltr` .Language.LanguageDirection }}">

Update some CSS properties in the theme to use logical properties to show stuff correctly for both of LTR and RTL like:

margin/padding/border-right to margin/padding/border-inline-end
margin/padding/border-left to margin/padding/border-inline-start
left to inset-inline-start
right to inset-inline-end

Make fa-chevron-circle-down in posts navigation show in the correct directions.
Make sure that codeblocks are kept LTR
Add some example page for RTL content, like markdown page in French example site.

Describe alternatives you've considered
Some CSS that isn't nice at all here
Additional context
I am ready to work on this or help with it if you prefer to work on it.
Inspired by https://github.com/CaiJimmy/hugo-theme-stack/pull/519 and https://github.com/adityatelange/hugo-PaperMod/pull/47

I didn't know about RTL, it may be implemented by Bootstrap built-in RTL functionality easily. I can create a PR for that tonight. PR are also welcome.

I'm just wondering that should all elements be RTL? Such as top-app-bar, layout etc.

@razonyang
I have gave a try to what I listed here yesterday and the results are promising with minor visual problems in the rtl version, will draft a PR.
The layout is fine to be as is, the post in the right then the side bar on the left, same for the top bar.

@yshalsager I'm looking forward to your PR, I'll review it if it's ready.


Maven Dependency spring-cloud-config-client causes issues with spring-boot-autoconfigure in Cloud Foundry

Summary
I was trying to get a spring-cloud-configuration-server running in our cloud environment. When extending an existing component with the maven dependency spring-cloud-configuration-client to make it consume the configuration from the configuration server, the application startup failed with the following error:
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT ***************************
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT APPLICATION FAILED TO START
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT ***************************
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT Description:
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT Failed to configure a DataSource: 'url' attribute is not specified and no embedded datasource could be configured.
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT Reason: Failed to determine a suitable driver class
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT Action:
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT Consider the following:
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT     If you want an embedded database (H2, HSQL or Derby), please put it on the classpath.
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT     If you have database settings to be loaded from a particular profile you may need to activate it (no profiles are currently active).
   2018-10-10T09:28:51.91+0200 [APP/PROC/WEB/0] OUT Exit status 1

I've created the minimal application to reproduce the error. See steps below.
Steps to reproduce
Step 1
Create a minimal spring-boot application using a database:
pom.xml
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>com.example</groupId>
    <artifactId>spring-config-demo</artifactId>
    <version>1.0-SNAPSHOT</version>

    <parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>2.0.5.RELEASE</version>
    </parent>

    <dependencies>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-web</artifactId>
        </dependency>

        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-data-jpa</artifactId>
        </dependency>
        <dependency>
            <groupId>org.mariadb.jdbc</groupId>
            <artifactId>mariadb-java-client</artifactId>
        </dependency>

    </dependencies>

    <build>
        <plugins>
            <plugin>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
            </plugin>
        </plugins>
    </build>

</project>

DemoApplication.java
package com.example.spring_config_demo;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class DemoApplication {

    public static void main(String[] args) {
        SpringApplication.run(DemoApplication.class, args);
    }
}

DemoController.java
package com.example.spring_config_demo;

import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestMethod;
import org.springframework.web.bind.annotation.RestController;

@RestController
@RequestMapping("/")
public class DemoController {

    @RequestMapping(method = RequestMethod.GET)
    public String helloWorld() {
        return "Hello World";
    }
}

Step 2
Build and deploy application to your cloud foundry environment. Create a MariaDB service and bind it to the application. Restart the application and check if the logs are fine.
Step 3
Add the dependency spring-cloud-configuration-client to the pom.xml, build and deploy the application
Dependency:
<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-config-client</artifactId>
    <version>2.0.1.RELEASE</version>
</dependency>

Expected result
The application should start up without any change in behavior.
Actual result
The startup of the application fails with the following message:
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT 2018-10-10 07:28:51.827 ERROR 8 --- [           main] o.s.b.d.LoggingFailureAnalysisReporter   :
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT ***************************
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT APPLICATION FAILED TO START
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT ***************************
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT Description:
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT Failed to configure a DataSource: 'url' attribute is not specified and no embedded datasource could be configured.
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT Reason: Failed to determine a suitable driver class
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT Action:
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT Consider the following:
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT     If you want an embedded database (H2, HSQL or Derby), please put it on the classpath.
   2018-10-10T09:28:51.82+0200 [APP/PROC/WEB/0] OUT     If you have database settings to be loaded from a particular profile you may need to activate it (no profiles are currently active).
   2018-10-10T09:28:51.91+0200 [APP/PROC/WEB/0] OUT Exit status 1

Actions taken

Aligned the versions of the dependencies (using spring-boot-starter-parent version 2.0.1.RELEASE)
Rebinding the service
Setting the driver with the property spring.datasource.driver-class-name

Additional Information

I attached the full log of the failed application startup startup.log
As far as I can tell we are using cloud foundry with these versions: Portal 4.10.6 - EXT API 4.10.1 - CF API 2.121.0
MariaDB version: 10.1.22

@Huo12345 can you update us on whether this is still effecting you?

Currently we have no impact, but we are planning to put a microservice using a DB and the cloud config server life towards the end of Q1 2019. Then this will affect us.

I still am having a hard time reproducing the problem locally.  Everything seems to work fine for me when I have mariadb running locally and running your sample.  I am not sure exactly how to figure out the right solution without a way to reproduce this.

Maybe there's a way to run with the Java build pack code locally, @nebhale?

Yep, you absolutely can.

Thanks @nebhale!
@Huo12345 can you give us a sample the reproduces the problem when running the buildpack locally?

Will do after christmas holidays.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.

Ping @Huo12345

Had some issues running the build pack locally but managed to do it now with cflocal. I’ll need to run some more tests to make sure I have the same behavior. Should be by Monday.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.

Try to add this dependency

org.springframework.cloud
spring-cloud-starter-bootstrap

Try to add this dependency

org.springframework.cloud
spring-cloud-starter-bootstrap

This problem existed long before that starter did, so it is not a solution

This problem existed long before that starter did, so it is not a solution


Improvement - Board rescan button

Problem summary
There is no way to rescan the boards connected to the PC from inside MF.
MF Version
Latest
Steps to reproduce

Start MF
Connect new board to PC
MF does not do anything

Expected result
It would be nice to have a button to rescan for any boards newly connected to the PC.
Actual result
There is no way to rescan, so only solution is to exit and restart MF.
Further details

[Issue created by jaime709: 2021-05-07]
[Last updated on bitbucket: 2021-06-08]
[Comment created by tigert: 2021-06-08]
This could be in the dropdown menu that lists your boards on the status bar:
| Modules (v) | Sim status | SimConnect Status |
        |    `-------------------------.
        | Autopilot / SN-11f-10b       |
        | Switch panel / SN-A5d-32c    |
        +------------------------------+
        | Re-scan connected modules    |
        `------------------------------'

I'd like to add my vote for this feature please

closed in favor of #1091 - there won't be the need for a button once #1091 is implemented


More juice httpd collector

Reporting the Total Apache Acceses per Second as a metric, as well as adding stats on CPULoad of the apache process and the memory usage of the workers *resident set size and virtual memory size".

Could you please provide a short description?

Unfortunately the code of the httpd collector is poorly structured, but it's inherited from diamond and I don't see this review as the right place to fix it (even though it adds a lot more complexity to the collector).
The direct consequence of this fact is that adding tests for these new functionalities would be very painful :(
Having said that, I am in favor or merging this PR
+1

@poros I don't think changing the structure of the collectors, even we think they are poorly structured, is a good idea. This is due to that fact that we want to upstream the least changes to the core diamond core architecture as much as possible, we just append new functionalities to it. That is the way I see it at leat, which could be complete non-sense.
Let me know what you think about that.
As for the complexity, I don't really get what you referring to, can you be more concrete on that?

With complexity I mean that you are adding functionality to this collector (you're adding a metric which requires state and you're spawning a subprocess). It's all legit, but it would be great if we were able to test them easily. We are not, sadly.
About the fixing the poor structure, I agree with you, that's why I +1ed the PR. I am unsure about the plans to contribute to/pull from new versions of diamond. It's something that has never been addressed until now.

+1

Signed off. Merging!