StandardHeaderExtensions uses time since startup rather than epoch

[X] I am at the right place and my issue is directly related to ROS#. General technical questions I would post e.g. at ROS Answers or Stack Overflow. For library-specific questions I would look for help in the corresponding library forums.
[X] I have thoroughly read the Contributing Guideline and writing this issue is the right thing to do in my case.

I have a question!

[X] I searched the Wiki, open and closed issues for an answer. I tried my best to find the answer by myself without success. I believe that the discussion we will have in this issue, and the solutions we might find, will help me, and likely other community members who have a similar problem.

Here is my question:
Your implementation of the standard header message type creates a timestamp based on seconds since startup. However, the std_msgs/Header documentation for ROS states that the timestamp should be seconds since epoch

Two-integer timestamp that is expressed as:

stamp.sec: seconds (stamp_secs) since epoch (in Python the variable is called 'secs')

I'm interested in the reasoning behind this implementation. Won't this require additional work to keep everything in sync?

@emnes There is no big reson behind it. It is simple, the time since the unity simulation epoch and did its job for all our applications so far. If you need to sync between ROS and Unity, you'll have to make adjustments here.

@emnes  please have alook at pull request #200 .
It seems to resolve your issue.

pull request #200 merged. closing.


will schemarama validate html documents?

i use schema properties inside html documents.

anatol

will schemarama validate my html documents?

It seems to work with your example, yes
screenshot here: https://twitter.com/danbri/status/1324420811223158788
using the test version at http://gnomus042.com/

@Gnomus042 reminds me to say "yes but... the current set of shapes we have probably won't give you the full validation experience you're hoping for"...

It seems to work with your example, yes
screenshot here: https://twitter.com/danbri/status/1324420811223158788
using the test version at http://gnomus042.com/

@danbri I think gnomus042 has been hacked as the browser is redirected to a scammy web site.

Hi @ziodave ,
We moved the test website to https://schemarama-demo.site/, you can try this one


feat: make resume page be in /resume + redirect

This way we open the room to home page at some point. Right now just building the CV

Current dependencies on/for this PR:

main

PR #134   👈

This comment was auto-generated by Graphite.


Enable Sphinx configuration caching

What's the new feature?
Properly handle #561 to permit caching.
What value does this add?
Allows proper caching.
Is there an alternative you've considered?
No response
Additional context
No response

Blocked by #664, pending next major Sphinx release


feat/added dark-light theme and toggle button

Title and Issue number
#393 Add dark and light mode for the host application
Title: feat/ dark - light theme and toggle button
Issue No. : #393
Code Stack: Js, CSS
Close #<393>
Description:-

Using Lucid for icons instead of Fontawesome found it better.
Used Context for switching theme.
Example in a video.
https://github.com/sadanandpai/frontend-mini-challenges/assets/53713926/cf020e72-100f-404c-9d68-850d1c63468a

conflicts

@Dev-AkshatGupta

conflicts

@Dev-AkshatGupta

Hey Sadanand I added WIP for the same I know why it's happening and rectified it locally. Just having some trouble with the git configuration I am figuring that out. Will sqash all commits in one. Thanks for reviewing.

Opened a new pr with conflicts solved and commits squashed
https://github.com/sadanandpai/frontend-mini-challenges/pull/419


Cutscene Video Code Where?

Describe your problem here.
I need help finding the code or something to make videos play on the startup of songs in specific weeks. Like how week 7 did it.
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
nuh uh

playVideo = true;
playDialogue = true;

function onStartCountdown()
	if isStoryMode and not seenCutscene then
		if playVideo then --Video cutscene plays first
			startVideo('insert your video name here'); --Play video file from "videos/" folder
			playVideo = false;
			return Function_Stop; --Prevents the song from starting naturally
		elseif playDialogue then --Once the video ends it calls onStartCountdown again. Play dialogue this time
			startDialogue('dialogue', 'breakfast'); --"breakfast" is the dialogue music file from "music/" folder
			playDialogue = false;
			return Function_Stop; --Prevents the song from starting naturally
		end
	end
	return Function_Continue; --Played video and dialogue, now the song can start normally
end

Put this script on your song data


Remove SPM Manifest

Summary
Apple is building SPM into Xcode so the manifest is no longer needed to future proof SPM compatibility
Review Checklist

[x] I have responded to reviews and made changes where appropriate.
[x] I have tested the code
[x] I have updated comments / documentation related to the changes I made.
[x] I have rebased my PR branch onto xi-mac/master.

thank you!


Fix an invalid memory allocation function

A memory block allocated with malloc() at https://github.com/openssl/openssl/commit/75e2c877650444fb829547bdb58d46eb1297bc1a#diff-baca3d0b945f277b98ef9b654387b6bfR191 is later freed with  OPENSSL_clear_free() at https://github.com/openssl/openssl/commit/ddc6a5c8f5900959bdbdfee79e1625a3f7808acd#diff-baca3d0b945f277b98ef9b654387b6bfR240.  This breaks applications that use CRYPTO_set_mem_functions().
CLA: trivial

We have lots of clear_free calls in OpenSSL; why is this one a problem?  Looking at the code it should do the right thing, it's just a wrapper that calls OPENSSL_cleanse and CRYPTO_free.

There is nothing bad with using CRYPTO_free() as long as its parameter was allocated with CRYPTO_malloc().  CRYPTO_set_mem_functions() allows to substitute OpenSSL's memory allocation functions with custom ones.  OpenSSL crashes when it tries to allocate a memory block with malloc() and then free this block with a custom memory allocator.

Of course you're right, I misread the diff.
Can you sign our CLA or put "CLA: trivial" in the commit text and force-push an update?
I agree this is trivial.

oh!  This is also fixed in #4100 which is in review, so I am going to close this.  Thanks!

Wouldn't it be better to merge this trivial (yet critical) fix now, and update #4100, which is quite complex and may need a long time to get merged?

Well, let's see what happens first.  My bet is on the other one :)

Resolved in #4100, closing.


Resolved 2 of the TODO points

Hello @AndroidDeveloperLB, currently (as you know) I'm using your base FastScroller in my FlexibleAdapter library.
I don't know if I will continue to keep your base FastScroller or to change to another one, however, it now works when changing LayoutManager (switching from Linear to Grid and viceversa) and also with GridLayoutManager (probably it always worked with Grid).
In my version you will find more features: I had to customize it and improve it in order to fit in combination the adapter animations and beyond. Details are in my code.
Maybe if we work together we can add some nice features like the library I have found (see my issue).

I have actually never tried. Please do a pull request if you can. I wish to make this library as minimal as possible, yet work well.


Login reloop issue when using msal-angular wrapper

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.14.1
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
2.0.5
Public or Confidential Client?
Public
Description
@jasonnutter Using Angular Wrapper, after sometime when accessing the application, loginRedirect goes into loop then I have to delete cookies to make it work. What's the trick to make it work. it works fine for the first time. Appreciate your help.
Error Message
No response
Msal Logs
No response
MSAL Configuration
auth: {
      clientId: clientid
      authority: authority,

    },
    cache: {
      cacheLocation: BrowserCacheLocation.LocalStorage,
      storeAuthStateInCookie: isIE // set to true for IE 11. Remove this line to use Angular Universal
    },
    system: {
      loggerOptions: {
        loggerCallback,
        logLevel: LogLevel.Info,
        piiLoggingEnabled: false
      }
    }

Relevant Code Snippets
msalService.loginRedirect(singIn)

Reproduction Steps

Logged in with properly user and did not logged out
Logged in after 24 hrs and logging with different user
The Application looping back to multiple time until the user explicitly delete the cookies

Expected Behavior
once user logs in after token expiry then it should navigate to authentication screen and once he logs in the user should be login with new token
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
Edge
Regression
@azure/msal-browser: "2.19.0"
Source
Internal (Microsoft)

@supriyaGannvi Are you able to provide verbose logs of this behavior?

@jo-arroyo this is what we get console

@supriyaGannvi Please send verbose logs. You can turn on verbose logging by changing the logLevel in the configurations as follows:
auth: {
      clientId: clientid
      authority: authority,

    },
    cache: {
      cacheLocation: BrowserCacheLocation.LocalStorage,
      storeAuthStateInCookie: isIE
    },
    system: {
      loggerOptions: {
        loggerCallback,
        logLevel: LogLevel.Verbose, // Change to Verbose here
        piiLoggingEnabled: false
      }
    }

I can confirm this. After the refresh token is expired (I have this issue that logs out the user even if the user has conditional access policies, 24 hours refresh token for SPA) and I try to log in the another user: redirects to the first user asking for password. You either have to delete the cookie or sign out the first user.

@ionut-gheorghe  Did u got any solution for this issue

None for my 2 issues: interactive login after 24 hours and the loop when sign in a new user.

@jo-arroyo could u help us how can we reslove this issue

@ionut-gheorghe Needing to login interactively after 24 hours is expected behavior. Refresh tokens used in single page apps and with the authorization code flow are limited to 24 hours. Once outside the 24 hour window, it is supposed to fail and require interactive login. While we recognize that this is not the best user experience, the 24 hour limit was chosen for security reasons for single-page apps. Please see this document about refresh tokens lifetimes and this document about refresh tokens and the auth code flow.
@supriyaGannvi Please provide verbose logs, per above.

@jo-arroyo i have send u the screen shot verbose logs

@supriyaGannvi Please upgrade to the latest versions of msal-angular and msal-browser, and let me know if you are still experiencing this behavior.

@jo-arroyo
Still the issue persist and recent upgardation @azure/msal-angular :2.4.1 @azure/msal-browser : 2.28.1

And this issue happens only if we are logging with different user

@bmahall  could u please help how can we resolve this issue

@supriyaGannvi Thanks for upgrading to recent version of msal-browser . Do you experience the looping issue with acquireTokenPopup() API as well?
It would be more helpful if you can kindly provide the logs in a text format using notepad, in place of screenshots as suggested above too.

@ionut-gheorghe Please feel free to open a separate issue in case of any further questions. Thanks!

@bmahall its only happening while we are using loginRedirect

@bmahall could u please help us out

@supriyaGannvi Can you please share code snippet(masking any critical auth data) where you are calling loginRedirect() and handling the response?
It is possible that the application logic is improperly using the handleRedirect() Api. Please refer to this document which explains the point:- Angular -looping when redirect.
You can use getActiveAccount() and setActiveAccount() APis to manage multiple accounts:-
The msal-browser instance exposes getActiveAccount() and setActiveAccount() for active accounts.
We recommend subscribing to the inProgress$ observable and filtering for InteractionStatus.None before retrieving account information with getActiveAccount(). This ensures that all interactions have completed before getting account information.
We recommend setting the active account:
After any action that may change the account, especially if your app uses multiple accounts. See here for an example of setting the account after a successful login)
Link: Managing multiple accounts.
Please let me know if you have any questions. You can also share the source code over the email mentioned on my Github profile.

@bmahall  still the issue persist

@bmahall We have added the $Inprogress and handle the active account as suggest by you still we could see the login redirect issue

@bmahall  could u please helps us out

@supriyaGannvi Can you please share the fiddler trace and verbose logs on the email on my Git profile? Thanks

@supriyaGannvi Meanwhile , please refer to a couple of points : -

Are you able to reproduce the behavior with local Storage , rather than session storage?
Please confirm the version(s) of msal-angular with which you are facing this issue
Redirects must be handled either with the MsalRedirectComponent or with calling handleRedirectObservable(). See our docs on redirects here for more information. Additionally, any interaction or account validation should be done after subscribing to the inProgress$ observable and filtering for InteractionStatus.None.
For more details on the above, please refer to the sample

Kindly share your source code wherein you are calling loginRedirect on my email.
Thanks for your patience!

@supriyaGannvi Please use tjhe following code in place of  this.msalBrodcastService.inProgress$   .pipe(filter((status: InteractionStatus) => status === InteractionStatus.None))   .subscribe(() => {     this.setLoginDisplay();   });
`
this.msalBroadcastService.inProgress$
.pipe(
filter((status: InteractionStatus) => status === InteractionStatus.None),
takeUntil(this._destroying$)
)
.subscribe(() => {
this.setLoginDisplay();
this.checkAndSetActiveAccount();
})
}
setLoginDisplay() {
this.loginDisplay = this.authService.instance.getAllAccounts().length > 0;
}
checkAndSetActiveAccount(){
/**
* If no active account set but there are accounts signed in, sets first account to active account
* To use active account set here, subscribe to inProgress$ first in your component
* Note: Basic usage demonstrated. Your app may require more complicated account selection logic
*/
let activeAccount = this.authService.instance.getActiveAccount();
if (!activeAccount && this.authService.instance.getAllAccounts().length > 0) {
  let accounts = this.authService.instance.getAllAccounts();
  this.authService.instance.setActiveAccount(accounts[0]);
}

}
`

@bmahall  we cannot add the $destory for the service

@bmahall we cannot add the $destory for the service

Why not? Can you also please confirm that you are handling the redirect response as described by @bmahall above? Are you able to reproduce your issue with one of our samples here?


Programs linked with SDL 2.26.0 do not start.

For details see https://github.com/libsdl-org/SDL/issues/6610.

Fixed.


Extension Error when used in the pipeline

Hi, Having an issue using this extension on our Project pipeline. I have followed all the doc and I'm getting this error:
...........
Start reviewing apps/Rebuspay/RebuspayDev.sln ...
invalid json response body at https://.openai.azure.com/openai/deployments/AOSTextDavinci3/completions?api-version=2022-12-01 reason: Unexpected token U in JSON at position 0
Here is the snapshot of the pipeline task settings:

Looks like a problem parsing the OpenAI service response, Can  you guide us on how to resolve it ?
Thanks.

Hi, Having an issue using this extension on our Project pipeline. I have followed all the doc and I'm getting this error: ........... Start reviewing apps/Rebuspay/RebuspayDev.sln ... invalid json response body at https://.openai.azure.com/openai/deployments/AOSTextDavinci3/completions?api-version=2022-12-01 reason: Unexpected token U in JSON at position 0
Here is the snapshot of the pipeline task settings:

Looks like a problem parsing the OpenAI service response, Can you guide us on how to resolve it ?
Thanks.

Sorry, I realized the problem, I had the wrong URL, OpenAI URL was missing  ../chat/completions


Clarify "free trial" quota and model-order

Validations

[x] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[x] I'm not able to find an open issue that requests the same enhancement

Problem
Hi
I've been playing with this extension on and off, but wanted to find out more about the "free trial" re: GPT4, Phind, Gemini.
How do we know when this is up, or exceeded?
I can't find anything here in issues, in the docs, or on the website.
Only this line, which is pretty vague:
Once you are using Continue regularly though, you will need to add an OpenAI API key that has access to GPT-4 by following these steps:
I was trying to figure something out today, and noticed suddenly suggestions were all wrong. Asked the model which model it was, and it responded with GPT3.
If it's going to degrade model, what's the order of degradation?
If GPT4 quota was up, should it silently go to 3, or provide feedback to the user than it's moving the 3? There is no GPT3 in the settings/json. If it's using 3 I would expect to see that reflected in the UI.
Or should it degrade silently to the next model in queue, for example Phind (which it doesn't appear to be doing currently).
Finally, on any of the options for trial, how do we know how that quota is proceeding?
Basically looking for more detailed information on
a) how this may compare to something like Cody that has a set number of completions inc per month on the hobby/free tier
and
b) how we know "for sure" what model is being used in Continue since it appears to degrade/change silently with no visual/message cue.
Thanks
Solution
No response

@EmmaWebGH We don't ever degrade the model (what you see is what you get). However gpt-4 is known to respond by saying that it is gpt-3 or "based on gpt-3", as you could validate in the OpenAI playground like below.

The free trial gives you 250 free requests and there will be a progress bar that shows up once you get to 125. I just checked and found that there was a bug in displaying this progress bar, which is why you might not have seen it. This is getting fixed right away.

Thanks for this reply, true I couldn't see a progress bar anywhere!
Amazingly I must not have done 250 requests yet, as I've never seen that "limit reached" box. Though I thought "surely I must have by now", as I've been playing with it on and off for about a month. :)
Thanks for explaining about GPT4 being confused about it's identity as well.
I wish ALL models would be more accurate about the name of their own file. Many times (even with local LLMs) I've tried to double check what model I'm working with by asking it, and they never know! Ha.


Metabolomics > LC-MS preprocessing : going from "Under dev" to "available"

Hi there,
With so much delay, here come the final modifications to make this "LC-MS preprocessing : advanced" training material a proper available-to-all tutorial.
I am looking forward to seeing it appearing in the tutorial list!
Hope everything is fine. I checked it again and again, but clumsiness is always waiting to catch me out.

@melpetera thanks a lot!
For the links to the slides, you can add a name: tag to the slides, and then reference them by that name instead of slide number
e.g.
---
name:raw-to-matrix

## From raw files to data matrix

![](../../images/lcmspreproc_slides_1.1.png)
---

and then link to it like [check this slide](../../tutorials/lcms-preprocessing/slides.html#raw-to-matrix)
This way the slides will point to the correct place even if the slide numbers change in the future (e.g. because you added a slide to the beginning)

@shiltemann Thank you for the review!
I did not know this was possible. It is way more convenient!
Suggestion applied in b3cd694

Hi Melanie!
Thank you a lot for this meticulous review and all the suggestions. I hope the changes made are ok for you!
I will investigate the 'xcms process history' issue: it seems indeed something is not right with the module (independently of this tutorial).
Thank you again!
Mélanie

@melpetera if you remove this optional-non-working step for the time being, I guess we can merge this awesome work!

Sorry for the delay. In b9418f5 I removed the case of CAMERA RData that is currently not supported to leave the XCMS RData only (which is working properly).
Is it ok for you @bgruening this way? Thank you very much for the review!

@melpetera there are some errors in the testing: https://travis-ci.org/github/galaxyproject/training-material/jobs/721928672#L1969
Can you have a look at this, otherwise I'm ready.

@bgruening I tryed to understand the error and see what the problem is but I could not find out. I can see that it comes from the slide referencing, but I do not see why. The path seems correct to me and the way it is referenced feels right. I guess it is out of my league - I do not even know how I could test it instead of simply looking at the lines...
I need help on this! :dizzy_face:

Hi @melpetera, yea, the links look correct, our testing framework just doesn't handle references to named slides correctly (since slides are rendered on the fly by remarkjs). I will have a look at fixing the tests to not give these false errors, but that shouldn't hold up this PR :)

ok, @melpetera @bgruening test are passing now :+1:

Awesome! Thanks a lot everyone!

Yeah! :sparkles: Thank you very much everybody!

Cool ! Wunderbar !


Decide on speaker gifts

We need to decide on what these will be before buying them.

What do you think about gifts for the judges?  City Camp -5, ATO -3 &
DataPalooza -5
On Sat, Aug 19, 2017 at 3:29 PM, Leo Suarez<EMAIL_ADDRESS>wrote:

We need to decide on what these will be before buying them.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/563, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AQ6IxsKs70E_Mp-d-NkEHVVZWg5ppU5Pks5sZzeKgaJpZM4O8bCi
.

--
Zach Ambrose
<EMAIL_ADDRESS>919-438-2752 (office)
919-616-9969 (cell)
www.AmbroseStrategy.com
https://www.linkedin.com/in/zambrose

We should acknowledge them with something...same as lightening talk
speakers?
On Sun, Aug 20, 2017 at 9:08 PM zachambrose<EMAIL_ADDRESS>wrote:

What do you think about gifts for the judges? City Camp -5, ATO -3 &
DataPalooza -5
On Sat, Aug 19, 2017 at 3:29 PM, Leo Suarez<EMAIL_ADDRESS>wrote:

We need to decide on what these will be before buying them.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/563, or mute the
thread
<
https://github.com/notifications/unsubscribe-auth/AQ6IxsKs70E_Mp-d-NkEHVVZWg5ppU5Pks5sZzeKgaJpZM4O8bCi
.

--
Zach Ambrose
<EMAIL_ADDRESS>919-438-2752 (office)
919-616-9969 (cell)
www.AmbroseStrategy.com
https://www.linkedin.com/in/zambrose
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/563#issuecomment-323624598,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARrpxtpkFLpFZuFIp1PG3U6tCanEi8sIks5saNh1gaJpZM4O8bCi
.

something from HoS, local coffee

Let's nail down who gets a gift. I'm tracking it and other notes here:
https://docs.google.com/document/d/1ohFfKMatoZS6LTri3J2Eo-BDOBpWutUFUV-gSSpamgw/edit?usp=sharing
Please add, I've started with Zach's suggestion.
On Mon, Aug 21, 2017 at 3:03 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

something from HoS, local coffee
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/563#issuecomment-323824758,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB3Ie9ptNsU-wS8JJVbZZ0_asdntZ2OJks5sadR4gaJpZM4O8bCi
.

Coffee purchased

gifts already decided? If not consider small swell bottle with NC Open Pass/CityCampNC, etc., etc., etc. logo applied. Cost  <$20/ea. Underscores eco-friendly intent. Available through Amazon; arrival in plenty of time.

What is the actual unit cost? link?
Chris Mathews
On Mon, Sep 11, 2017 at 11:27 AM, suzanneccnc<EMAIL_ADDRESS>wrote:

gifts already decided? If not consider small swell bottle with NC Open
Pass/CityCampNC, etc., etc., etc. logo applied. Cost <$20/ea. Underscores
eco-friendly intent. Available through Amazon; arrival in plenty of time.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/563#issuecomment-328565494,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOGtUT5EpLKGh2a2mE80PEgxiyxcdxcks5shVFcgaJpZM4O8bCi
.

Here is the link to Amazon. Several are listed, some with supplier logo, some without. https://www.amazon.com/Simple-Modern-Stainless-Insulated-Double-Walled/dp/B01GINGFUQ/ref=sr_1_5?ie=UTF8&qid=1505143461&sr=8-5&keywords=swell+bottle+s'ip

Got some Raleigh themed gifts from House of Swank


[DRAFT] Add virtual eve deployment doc draft

This PR adds a document about important notes and instructions on how to deploy virtual eve for testing purposes especially in a scenario when hardware is not available.
Some images to describe the overall high level workflow if required
https://raw.githubusercontent.com/bayupw/eve/virtual-eve-deployment-images/docs/pics/deploying-in-virtualbox-and-vmware.png
https://raw.githubusercontent.com/bayupw/eve/virtual-eve-deployment-images/docs/pics/deploying-in-gcp.png

I do like this! It just needs links from the DEPLOYMENT.md doc.

I've missed the VBoxManage script to enable nested-hw-virt
VBoxManage modifyvm eve-vm1 --cpus 1 --memory 1024 --nic1 nat --hwvirtex on --vtxvpid on --vtxux on --firmware efi --nested-hw-virt on
Will combine update with other feedback for this doc

@eriknordmark let me know if that looks better, thank you!

Looks like a very good start. Let's see if yetus finds any issues.

I agree, looks like a good start. @bayupw , there are some Yetus errors that must be fixed. Also, please, squash your commits, we shouldn't have specific commits related to changes in the PR, made during the review to address reviewer comments. In the case of this PR, you can provide the new documentation file in only one single commit (the first one).

Looks like a very good start. Let's see if yetus finds any issues.

I agree, looks like a good start. @bayupw , there are some Yetus errors that must be fixed. Also, please, squash your commits, we shouldn't have specific commits related to changes in the PR, made during the review to address reviewer comments. In the case of this PR, you can provide the new documentation file in only one single commit (the first one).

Thanks @rene I'll take a look at the Yetus error and will resolve them. Will fix the commits as well


Pad %(playlist_index)s with zeroes 2

I am reopening this issue because not fixed entirely:
https://github.com/rg3/youtube-dl/issues/4157
(Tested with version 2<IP_ADDRESS>)
Here is a context where a padding would be useful:
I want to download this playlist https://www.youtube.com/playlist?list=PLE30F9d9cZayucP7UqdO37kjo3gtf989s
composed of 121 vidéos at the moment. So I start downloading it with a filename containing %(playlist_index)s. So this program creates the files 001, 002 ... Then there is an error, or the time is too long so I have to stop the download and restart it later with --playlist-start NUMBER. But if I use --playlist-start 22 or more, then there are less than 99 épisodes to download, so the %(playlist_index)s is written on 2 digits.
The first problem is that there is no coherence between the name of the first episodes and the last ones.
The second problem is that as I stopped the first download, it most probably stopped in the middle of the download of one episode, so when it restarts it doesn't find the .part file and starts the download of the current episode from the beginning.
It might be useful to be able to give the format in the --playlist-start in the following way:
--playlist-start 1 => file 1, 2 ... 10 ... 222 ... 99999
--playlist-start 01 => file 01, 02 ... 10 ... 222 ... 99999
--playlist-start 001 => file 001, 002 ... 010 ... 222 ... 99999

FYI, not related to this issue: 2015.03.09 is out

I've just tested with version 2015.03.09, and there is still the same problem.
Try the 2 following commands (provided there are still 121 vidéos in the palylist and not any new one):
youtube-dl --get-filename --playlist-start 22 -o "%(playlist)s - %(playlist_index)s - %(title)s.%(ext)s" https://www.youtube.com/playlist?list=PLE30F9d9cZayucP7UqdO37kjo3gtf989s
youtube-dl --get-filename --playlist-start 23 -o "%(playlist)s - %(playlist_index)s - %(title)s.%(ext)s" https://www.youtube.com/playlist?list=PLE30F9d9cZayucP7UqdO37kjo3gtf989s

Instead of deciding automatically how many zeros to use, we could just allow in the output template %(playlist_index)04d, which would produce 000x.

download the source and open file "youtube_dl\YoutubeDL.py"
find function             def prepare_filename(self, info_dict)
find line                    template_dict['playlist_index'] = '%0*d' % (len(str(template_dict['n_entries'])), template_dict['playlist_index'])
add code                  template_dict['playlist_index'] = template_dict['playlist_index'].zfill(2) after the line
and the result filename will be 01xxx,02xxx,03xxx,you can change the zfill parameter what you want

I think the approach by @jaimeMF would be better than mine in #9929.
The string formatting in python 3 doesn't support it directly . Do I see it correctly, that currently -o directly specifies the format string used, without modification? I guess we'd have to parse it ourselves, or does someone have an idea how that can be done in a better way?

I still have this issue in version 2020.02.16


SignalR HubContext User Is Null

I added a new SignalR hub to my project but the hub context user is coming through as null.  Do I need to do something specific with my app configuration or hub connection to pass things around correctly?

Sorry for the late response, It's been crazy at job.
Regarding this issue it should be now resolved with latest release as now it exposes the


Toggle Animation not working for react native web

Describe the bug
The toggle inner circle is not moving to right at all in web
To Reproduce
Steps to reproduce the behavior:

Run the react native app for web
Click on toggle.
The toggle inner circle is not moving from left to right. Just stays at left.

Expected behavior
Toggle needs to move from left to right.
Screenshots

Desktop (please complete the following information):

OS: [iOS]
Browser [safari]
Version [e.g. 14.1.2]

I checked my codesandbox and it works fine on web.
But I totally understand the issue because I experienced this issue while developing this project few month ago. Are you still experiencing this issue?

@yujong-lee Unfortunately yes! We still do experience the issue for react-native-web

@jenipharachel  Thanks. after you kindly do that for me, I'll be working on it!


ARCHIVE FAILED: Exit status: 65, Gym failed

I am able to build archive using xcode successfully.
When i run $ fastane do_everything_dev
i get below error for last 5 days. The same code was working before without any code change.
ARCHIVE FAILED **
[19:55:48]: Exit status: 65
+---------------+-------------------------+
|            Build environment            |
+---------------+-------------------------+
| xcode_path    | /Applications/Xcode.app |
| gym_version   | 2.205.1                 |
| export_method | ad-hoc                  |
| sdk           | iPhoneOS15.2.sdk        |
+---------------+-------------------------+
[19:55:48]: ▸     cd /Users/mdmozammil/core/productapp/ios-mobiquity-consumer-core-app
[19:55:48]: ▸     /usr/bin/touch -c /Users/mdmozammil/Library/Developer/Xcode/DerivedData/MobiquityConsumer-gwhebhwduquhohgsnwhfrgwhxoku/Build/Intermediates.noindex/ArchiveIntermediates/DEV/InstallationBuildProductsLocation/Applications/mobiquity\ Pay\ DEV.app
[19:55:48]: ▸ /Users/mdmozammil/core/productapp/ios-mobiquity-consumer-core-app/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.2.99. (in target 'SwiftEventBus' from project 'Pods')
[19:55:48]: ▸ /Users/mdmozammil/core/productapp/ios-mobiquity-consumer-core-app/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.2.99. (in target 'FSCalendar' from project 'Pods')
[19:55:48]:
[19:55:48]: ⬆  Check out the few lines of raw xcodebuild output above for potential hints on how to solve this error
[19:55:48]: 📋  For the complete and more detailed error log, check the full log at:
[19:55:48]: 📋  /Users/mdmozammil/Library/Logs/gym/mobiquity Pay-DEV.log
[19:55:48]:
[19:55:48]: Looks like fastlane ran into a build/archive error with your project
[19:55:48]: It's hard to tell what's causing the error, so we wrote some guides on how
[19:55:48]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[19:55:48]: Before submitting an issue on GitHub, please follow the guide above and make
[19:55:48]: sure your project is set up correctly.
[19:55:48]: fastlane uses xcodebuild commands to generate your binary, you can see the
[19:55:48]: the full commands printed out in yellow in the above log.
[19:55:48]: Make sure to inspect the output above, as usually you'll find more error information there
[19:55:48]:
+------------------+-----------------------+
|               Lane Context               |
+------------------+-----------------------+
| DEFAULT_PLATFORM | ios                   |
| PLATFORM_NAME    | ios                   |
| LANE_NAME        | ios do_everything_dev |
| BUILD_NUMBER     | 20                    |
+------------------+-----------------------+
[19:55:48]: Error building the application - see the log above
+------+------------------------+-------------+
|              fastlane summary               |
+------+------------------------+-------------+
| Step | Action                 | Time (in s) |
+------+------------------------+-------------+
| 1    | default_platform       | 0           |
| 2    | Switch to ios clean    | 0           |
|      | lane                   |             |
| 3    | clear_derived_data     | 0           |
| 4    | Switch to ios          | 0           |
|      | build_beta_dev lane    |             |
| 5    | automatic_code_signin  | 0           |
|      | g                      |             |
| 6    | increment_build_numbe  | 2           |
|      | r                      |             |
| 💥   | gym                    | 650         |
+------+------------------------+-------------+
[19:55:48]: fastlane finished with errors
[!] Error building the application - see the log above
MCKL-7364:ios-mobiquity-consumer-core-app mdmozammil$ fastlane env
[✔] 🚀
[20:12:47]: fastlane detected a Gemfile in the current directory
[20:12:47]: However, it seems like you didn't use bundle exec
[20:12:47]: To launch fastlane faster, please use
[20:12:47]:
[20:12:47]: $ bundle exec fastlane env
[20:12:47]:
[20:12:47]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[20:12:49]: Generating fastlane environment output, this might take a few seconds...
swift-driver version: 1.26.21 🚫 fastlane environment 🚫
Stack

Key
Value

OS
12.2.1

Ruby
2.6.8

Bundler?
false

Git
git version 2.32.0 (Apple Git-132)

Installation Source
/usr/local/bin/fastlane

Host
macOS 12.2.1 (21D62)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
13.2.1

Swift Version
5.5.2

System Locale

Error

No Locale with UTF8 found 🚫

fastlane files:
`./fastlane/Fastfile`
default_platform(:ios)

platform :ios do

desc "clean"
lane :clean do
  clear_derived_data(derived_data_path: "./fastlane/builds/")
end

  desc "Create dev ipa"
  lane :build_beta_dev do
    enable_automatic_code_signing
    increment_build_number
    gym(scheme: "DEV")
  end

  desc "Upload dev to Firebase"
  lane :upload_firebase_dev do
  firebase_app_distribution(
    ipa_path: "./fastlane/builds/mobiquity Pay.ipa",
    app: "<Firebase app id>",
    groups: "<groupname>",
    release_notes: "Mobiquity Subscriber DEV"
  )
end

desc "Create uat ipa"
  lane :build_beta_uat do
    enable_automatic_code_signing
    increment_build_number
    gym(scheme: "UAT")
  end

  desc "Upload uat to Firebase"
  lane :upload_firebase_uat do
  firebase_app_distribution(
    ipa_path: "./fastlane/builds/mobiquity Pay.ipa",
    app: "<Firebase app id>",
    groups: "<groupname>",
    release_notes: "Mobiquity Subscriber UAT",
  )
end

desc "Create aws ipa"
  lane :build_beta_aws do
    enable_automatic_code_signing
    increment_build_number
    gym(scheme: "PVG")
  end

  desc "Upload dev to Firebase"
  lane :upload_firebase_aws do
  firebase_app_distribution(
    ipa_path: "./fastlane/builds/mobiquity Pay PVG.ipa",
    app: "<Firebase app id>",
    groups: "<groupname>",
    release_notes: "Mobiquity Consumer AWS"
  )
end

desc "build and upload dev to firebase"
  lane :do_everything_dev do
      clean
      build_beta_dev
      upload_firebase_dev
  end

desc "build and upload uat to firebase"
  lane :do_everything_uat do
      clean
      build_beta_uat
      upload_firebase_uat
  end

desc "build and upload aws to firebase"
  lane :do_everything_aws do
      clean
      build_beta_aws
      upload_firebase_aws
  end

end

`./fastlane/Appfile`
  app_identifier(ENV['BUNDLE_IDENTIFIER']) # The bundle identifier of your app
  apple_id("<email.com>") # Your Apple email address
  team_name ("<Name>")

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.205.1
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-firebase_app_distribution
0.3.3
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.3.0

atomos
0.1.3

claide
1.1.0

colored2
3.1.2

nanaimo
0.3.0

rexml
3.2.5

xcodeproj
1.21.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.8.0

terminal-table
1.8.0

plist
3.6.0

public_suffix
4.0.6

addressable
2.8.0

multipart-post
2.0.0

word_wrap
1.0.0

optparse
0.1.1

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

artifactory
3.0.15

babosa
1.0.4

colored
1.2

highline
2.0.3

commander
4.6.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

faraday-multipart
1.0.3

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.0

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.4

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.6

gh_inspector
1.1.3

mini_magick
4.11.0

naturally
2.2.1

rubyzip
2.3.2

security
0.1.3

xcpretty-travis-formatter
1.0.1

dotenv
2.7.6

bundler
1.17.2

simctl
1.6.8

jwt
2.3.0

uber
0.1.0

declarative
0.0.20

trailblazer-option
0.1.2

representable
3.1.1

retriable
3.1.2

mini_mime
1.1.2

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.16.1

googleauth
1.1.2

httpclient
2.8.3

google-apis-core
0.4.2

google-apis-playcustomapp_v1
0.7.0

google-apis-androidpublisher_v3
0.16.0

google-cloud-env
1.5.0

google-cloud-errors
1.2.0

google-cloud-core
1.6.0

google-apis-iamcredentials_v1
0.10.0

google-apis-storage_v1
0.11.0

digest-crc
0.6.4

google-cloud-storage
1.36.1

emoji_regex
3.2.3

aws-eventstream
1.2.0

aws-sigv4
1.4.0

aws-sdk-kms
1.55.0

aws-sdk-s3
1.113.0

CFPropertyList
3.0.5

excon
0.92.0

unf_ext
<IP_ADDRESS>

json
2.6.1

webrick
1.7.0

rake
13.0.6

aws-partitions
1.568.0

jmespath
1.6.1

aws-sdk-core
3.130.0

forwardable
1.2.0

logger
1.3.0

date
2.0.0

stringio
0.0.2

ipaddr
1.2.2

openssl
2.1.2

zlib
1.0.0

mutex_m
0.1.0

ostruct
0.1.0

strscan
1.0.0

io-console
0.4.7

fileutils
1.1.0

etc
1.0.1

libxml-ruby
3.2.1

psych
3.1.0

fastlane-plugin-firebase_app_distribution
0.3.3

generated on: 2022-03-28

[20:12:52]: Take notice that this output may contain sensitive information, or simply information that you don't want to make public.
[20:12:52]: 🙄  Wow, that's a lot of markdown text... should fastlane put it
into your clipboard, so you can easily paste it on GitHub? (y/n)
y
[20:12:56]: Successfully copied markdown into your clipboard 🎨
[20:12:56]: Open https://github.com/fastlane/fastlane/issues/new to submit a new issue ✅

I have same issue. If call same xcodebuild command from log, all works fine

Can you explain a little bit more, how are you calling xcodebuild?

I'm only try call command from the fastlane build log.
set -o pipefail && xcodebuild -workspace <ProjectName>.xcworkspace -scheme <ShemeName> -destination 'generic/platform=iOS' -archivePath /Users/ios/Library/Developer/Xcode/Archives/2022-03-29/<ProjectName>\ 2022-03-29\ 09.44.23.xcarchive  archive | tee /Users/ios/Library/Logs/gym/<ProjectName>.log | xcpretty
But preffer to use fastlane. Did you try to use previous fastlane version?

okay, let me directly use xcodebuild command.
No i didn't try with previous fastlane version. i'll try and let you know.

same here :(
The following build commands failed:
        PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/wowzaaa/Library/Developer/Xcode/DerivedData/uHubs-blnerskrnxheerfjcwzjslxniczt/Build/Intermediates.noindex/ArchiveIntermediates/Dev/IntermediateBuildFilesPath/Pods.build/Development.Release-iphoneos/FBReactNativeSpec.build/Script-097CEF56F0CD5FFE4BF04151896369A2.sh (in target 'FBReactNativeSpec' from project 'Pods')
(1 failure)
[16:44:19]: Exit status: 65

in my case it was a react-native issue https://github.com/react-native-community/upgrade-support/issues/138

Has anyone found a solution to this? I've updated my mac and Xcode now gym is failing. Unsure what it could be.

Seeing a similar issue here, was working a few days ago but has failed today without any changes

I had an exit code 65 looking over my logs I found I had a custom script that was copying a env file. For some reason that started causing a build error in the new xCode. I deleted that script by editing the scheme config.
Unsure this will be related to your issue but might be a cause for someone in the future.

For me it was a combination of downgrading from xcode 13.3.1 to 13.2.1 & downgrading ruby to 3.0.3 from 3.1.3, which was the last combination that worked for me.. Hope this helps someone else.

I'm having the exactly same issue building with Github Actions. same as https://github.com/fastlane/fastlane/issues/20276
I'm able to build with my Mac (M1) just fine.

For the people that have this issue:
Check the output file that's mentioned in your log.
If it contains
error: symbols referenced by indirect symbol table entries that can't be stripped
It's may be an issue with linker flags conflicting with symbol stripping, try removing -interposable, we've removed
					"-Xlinker",
					"-interposable",
					"-Xlinker",
					"-undefined",
					"-Xlinker",
					dynamic_lookup,

and it started working correctly.

Facing the same issue in CI for a month now and we can't figure out what's causing the error.
Command PhaseScriptExecution failed with a nonzero exit code

It just means that command that was being run in PhaseScriptExecution wasn't successful, you have to check detailed logs from the execution. The location of the log is probably mentioned somewhere in the fastlane output.

I had the exact same problem and finally found out that the cause of this error because i haven't put my .env file onto my root project. I had pre-action script to read the env file as i am using react-native-config for different schemes, that's why i'm getting error if i dont have the .env file. So my solution is to put base64 string of the env file to github secret and then copy & decode it in the github workflow. After that everything works like a charm. Maybe this can help someone :)

I just solved this issue by opening Xcode and found out that in the iMac (where I got the error) the project did not have In-App Purchases capabilities and the signing team was none, so I had to login into Apple to assign a team. For some reason, the new setup erased my previous configs..

This solved my problem: https://stackoverflow.com/questions/73765469/signing-for-googlesignin-googlesignin-requires-a-development-team.

In my case, there was no error message in fastlane or xcode build's output when archive failed. If you encounter the same situation, this SO answer pointed to where the missing error message can be found.

I was having this issue on GitHub actions while trying to run fastlane with match to deploy iOS app to TestFlight, what fixed for me was disable_automatic_code_signing before calling match.
    disable_automatic_code_signing(
    team_id: "",
    profile_name: "",
    code_sign_identity: ''
  )

Add
gym(
....
xcargs: "CODE_SIGN_STYLE=Manual DEVELOPMENT_TEAM="
}

Resolved the issue for me

When using match + gym on Fastlane. Using update_code_signing_settings before match ins what did the trick, the resulting operations look like this:
update_code_signing_settings(
    use_automatic_signing: false,
    team_id: team_id,
    targets: [target],
    code_sign_identity: "*****",
    profile_name: "your_profile_name",
    path: PROJECT_PATH
  )

  match(
    username: options[:username],
    git_url: certificates_url,
    app_identifier: app_identifier,
    type: "appstore",
    team_id: team_id
  )

  gym(
    project: PROJECT_PATH,
    export_method: "app-store",
    configuration: "Release",
    scheme: scheme,
  )

In my case, it has something to do with the provisioning files, certificates I chose to build. Some of the certificates is missing in one of my machines, and it lead to this error.

In my case, it has something to do with the provisioning files, certificates I chose to build. Some of the certificates is missing in one of my machines, and it lead to this error. And there's no error message related to certificates or provisioning files in Fastlane console. The errors show when I archive on Xcode.

@LoyaltyWu could you explain last sentence in detail? The errors show when I archive on Xcode.
how can I get error from xcode?

Same here, when running locally everything's fine, but on GitHub Actions it fails with exit status 65

For me this was an issue with provisioning profiles. The app_identifier I was passing to match was for my production app and building my "beta" app (different bundle ID) was failing with exit code 65 because it was trying to use the wrong profile. It was running fine locally for me because I have both profiles installed on my machine, but on CI it was failing because it installs the profiles fresh.
Frustrating that a more helpful error message isn't spit out, but hope this helps someone else out. Ultimately I noticed this by looking at the output of match.

Taka a look at these, might help:

https://github.com/fastlane/fastlane/issues/20626#issuecomment-1238364705
https://github.com/fastlane/fastlane/issues/20810#issuecomment-1481639397

I also encountered a similar problem. After reading the log, I found more detailed reasons, which were caused by certificate conflict

I received this issue after upgrading to xcode 14.
First answer solved it for me:
https://stackoverflow.com/questions/74275390/fastlane-with-xcode-14-archive-failed

I received this issue after upgrading to xcode 14. First answer solved it for me: https://stackoverflow.com/questions/74275390/fastlane-with-xcode-14-archive-failed

This fixed my error as well, thanks!

Had this problem, struggled for days to solve it. Putting my solution here too for posterity:
I'm using Flutter, but I think this applies globally. If you introduce a new iOS build target into your app, and that target required you to add a new identifier, your fastlane instance probably needs a 2nd mobile provision referenced.
For example, my original project reference com.company.project, but then I added a target that used com.company.project.Broadcast-Extension. My fastlane builds started failing with Exit Status 65, but XCode was still able to build it.
Check https://developer.apple.com/account/resources/identifiers/list to see if a new identifier got added to your project. For me, I had created a Broadcast Extension to enable screen-share on LiveKit.io. As part of the process, I had to create a new Upload Broadcast Extension target in my XCode project. I did so without updating fastlane with a second mobile provision, and my builds began failing.
The solution was to create a second provisioning profile for my broadcast extension at https://developer.apple.com/account/resources/profiles/list with the new identifier. Then, install both my provisioning profiles with:
install_provisioning_profile(path: <insert_path_to_mobile_provision>)

Finally, create an ExportOptions.plist file based off this template which specifies what mobile provisioning profile should be used for each target. Ensure each name/identifier pair EXACTLY matches your provisioning profile as seen in at https://developer.apple.com/account/resources/profiles/list and identifier as seen in https://developer.apple.com/account/resources/identifiers/list. Reference the ExportOptions.plist file by passing its path to
build_app(
      [...]
      export_options: <Path to ExportOptions.plist>,
    )

For CI/CD, I recommend using https://github.com/yukiarrr/ios-build-action which massively simplifies the iOS build process headache.
I hope this helps fellow engineers!

I only have this problem when i run my fastlane command with a runner, when i use the same environment and execute the command on the host directly it works, does anyone have a clue?

I only have this problem when i run my fastlane command with a runner, when i use the same environment and execute the command on the host directly it works. It worked with the same runner before the xcodee 14 update. Does anyone have a clue?

i fixed it by changing the environment, i guess it was export LANG=en_US.UTF-8 but I'm not sure

Flutter dev here. I had to login again in XCode with my Apple account after a year or so...

I got this after adding Sign In with Apple . It was a provisioning profile issue as well--I fixed it by adding the sign in capability to the App ID in the developer portal and regenerating the provisioning profile.


Server crash - Block detector on Interface

Issue description:
I want to put a crystallized canola seed into a detector block. As soon as I do so, my server crashes with this error. Restarting the server produces the same error from then on. I can only resolve this by loading the world in MCEdit and removing the block detector. The crash is reproducable (I've tried this 3 times now with the same result - instant crash as soon as the seed goes into the gui slot of the block detector).
Version (Make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge: 2151
Refined Storage: 1.2.4

Does this issue occur on a server? [yes/no] Yes
If a (crash)log is relevant for this issue, link it here:
Same as above. Let me know if you need any other logs.
Edit:
I've tested this scenario in a few different settings. To start off with, I simply placed the block detector elsewhere and then tried inserting different items. I had no issues there, not even with the cyrstalized canola seeds. I then placed the block detector back on its original location - on top of an interface - and the crash reoccured by inserting an item in the GUI slot. This was reproducable for any item. So it seems like the crash isn't caused by canola seeds specifically but rather by the block detector's location and - more probably- its relation to/interaction with the surrounding blocks.
I made a short Youtube video to demonstrate how I can cause this crash to happen.

This is a lumien.randomthings issue:
Caused by: java.lang.NullPointerException
    at lumien.randomthings.tileentity.redstoneinterface.TileEntityRedstoneInterface.getRedstonePower(TileEntityRedstoneInterface.java:50) ~[TileEntityRedstoneInterface.class:?]
    at lumien.randomthings.handler.AsmHandler.getRedstonePower(AsmHandler.java:303) ~[AsmHandler.class:?]


Automatically update version and tag from Github action

Description
Add github action to update version and tag repository.
Alternatives
Currently we use the manual make bump version=... and make release
Additional context
Precursor to contrailcirrus/pycontrails#3

Closed in #30


scrollIntoView: Skip overflow:hidden elements

Fixes #5355

/botio-linux preview

Seems to work just fine. After the nit is addressed, I'm fine with this solution. I'll leave the final review for @brendandahl once the nit is addressed.

/botio-linux preview

@brendandahl Looks good to me. Could you do the final review?


feat(dblclick): allow for double clicks to be performed with cy.realClick({ clickCount: 2 })

I'm slightly unsure how this works under the hood - since both mousePressed & mouseReleased expects this parameter. I don't know what actually happens if you configure a different clickCount for each of those but I've tested that both are required to make this work.

@dmtrKovalenko the CI has failed but it looks that this might be unrelated to the PR - maybe you would have more insight into this

We have a flaky CI :)
thanks for this feature, will try to release it soon

@dmtrKovalenko friendly 🏓 😉

Yup, sorry for long delay

No worries, I know how it is - just reminding you about this, if you don't have time right now, that's fine too - I can ping you again sometime later if this won't get merged in until then.

Working on this now, going to release new version today :)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Updated expect API docs with .resolves and .rejects

Follow-up from PR #3068. This PR updates the docs to incorporate the new .resolves and .rejects keywords in the expect API.

Some of our docs note that features became available in Jest 19, would you mind adding the same note for these with "Jest 20"? :)

No problem, I updated the API docs accordingly:)

Codecov Report

Merging #3172 into master will increase coverage by 7.75%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3172      +/-   ##
==========================================
+ Coverage   61.72%   69.47%   +7.75%
==========================================
  Files         174      157      -17
  Lines        6555     5550    -1005
  Branches        3        3
==========================================
- Hits         4046     3856     -190
+ Misses       2508     1693     -815
  Partials        1        1

Impacted Files
Coverage Δ

packages/pretty-format/src/plugins/ConvertAnsi.js
0% <0%> (-100%)
:arrow_down:

packages/jest-cli/src/TestRunner.js
29.8% <0%> (-3.53%)
:arrow_down:

packages/pretty-format/src/plugins/ReactElement.js
97.77% <0%> (-2.23%)
:arrow_down:

packages/jest-cli/src/reporters/VerboseReporter.js
30% <0%> (-0.62%)
:arrow_down:

packages/jest-jasmine2/src/jest-expect.js
0% <0%> (ø)
:arrow_up:

packages/jest-jasmine2/src/index.js
0% <0%> (ø)
:arrow_up:

packages/jest-cli/src/runJest.js
0% <0%> (ø)
:arrow_up:

packages/jest-runtime/src/index.js
75% <0%> (ø)
:arrow_up:

packages/jest-cli/src/jest.js
0% <0%> (ø)
:arrow_up:

...ges/jest-haste-map/src/lib/getPlatformExtension.js
100% <0%> (ø)
:arrow_up:

... and 23 more

Continue to review full report at Codecov.

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

Thanks for taking a look @hramos! I have updated the PR:)

Strange, the CI is failing from the tiny change I made. Is this an issue with jest?

These are markdown-only changes, I don't think the Travis failures are related.


[WIP] Fix upgrade issues with ipv6

High-level description
This patch fixes couple of issues with ipv6 overlay implementation

Fixes the issue wherein after upgrade ipv6 address wasn't configured on vtep interface which
led to the failure of the entire ipv6 configuration
Fixes the issue wherein master overlay module would not recover once ipv6 is disabled after it was enable earlier

Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS-34536 Virtual networking remain broken after upgrade to 1.11.1

Checklist for all PRs

[x] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review):
https://github.com/dcos/dcos-net/compare/c2cd727c7d52829a0960116229ea537b831210ce...70b142acc2e380506650405fd761796d416a3ad8
https://github.com/dcos/dcos-mesos-modules/compare/af814bf5c7cbe42d10644f3214f1ad2a450390da...e1c47cb157b0f5adac086568eccf183b3e814ee2

[ ] Test Results: [link to CI job test results for component]
[x] Code Coverage https://codecov.io/gh/dcos/dcos-net/pull/50?src=pr&el=continue

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

This repo has @mesosphere-mergebot integration. You can interact with the following commands.
@mesosphere-mergebot override-status
@mesosphere-mergebot merge-it
@mesosphere-mergebot label [Ready For Review |Holding |Request For Comment |Ship It |Work In Progress]
@mesosphere-mergebot bump-ee

PR creators can apply one of  [Ready For Review |Work In Progress]. Owners can apply any label.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label Ready For Review

@urbanserj @orsenthil

@mesosphere-mergebot bump-ee

@mesosphere-mergebot override-status teamcity/dcos/test/azure/arm DCOS_OSS-3539

@mesosphere-mergebot override-status teamcity/dcos/test/aws/cloudformation/simple DCOS_OSS-2115


cocoapods missed version

cocoapods still install version 2.0.0

I've forgotten some processes and now I updated. Thanks!


↩ [1.9] DCOS-16191: Skip non-string values in env var parsers

ℹ  This is a back port of #2253

This PR makes DC/OS parsers to parse string values for environment variables and let the plugins parse/reduce the rest.
To test:
Create a secret and give it a hard time with a lot of Env vars and secrets. Switching between JSON editor and form. Add a var in the form edit in the JSON, delete in the form, add in the JSON. You know the grind.

@Poltergeist ping!

Great Job! ⚒ 💯


Test more puppet and ruby versions

We should test puppet-syntax on more puppet and ruby versions.

@deanwilson I've updated the .travis.yml to only test the latest versions of each major branch

Looks good. Merge when ready.


Update readme and translation files

Updated README file to use uk.react.dev instead of react.dev
Updated TRANSLATION file with new info, common translation rules and glossary fixes

@bkatsevych are you available for review?


Help-me

Dashboard: Internal Server Error
Console: Error: secretOrPrivateKey must have a value

Make sure jwtSecret has a value, this value can be anything random

when I click "open panel" and then authorize it returns again to the authorization page

There's no "open panel" anywhere? What do you mean with that?

when I click the open dashboard button and authorize the application, it simply returns to the authorization page and the following error: Error: payload is required

This might be an issue related to that Discord is experiencing some issues at the moment, I suggest trying in a few hours, if it still doesn't work let me know.

ok thanks.


Scripts that are prefixed with network should overwrite when generating client

Is your feature request related to a problem? Please describe.
Scripts that are prefixed with network should overwrite the other script with the same name in generating client
e.g.
./scripts
   ├──getInfo.cdc
   └──mainnetgetInfo.cdc

The client should take mainnetgetInfo for mainnet and getInfo for testnet and emulator

Agreed


Regen

Part of https://github.com/gtk-rs/gir/issues/845
cc @sdroege @EPashkin

Next PRs will come in the next days. :)

So empty line can't be added?
Then IMHO sourceview-sys need update too.
👍

I'll check into toml directly but not in this PR. :)

And sourceview-sys will be updated in any case. :)


Fixes SSMS Heading inside of the Note above

Heading was rendered inside of the Note above

@Univream : Thanks for your contribution! The author, @stevestein, has been notified to review your proposed change.

@Univream - Thanks for the fix!

#sign-off


(k9s) outdated

Checklist

[X] I have checked the moderation queue that no new version has been submitted (only visible when logged in), or the submitted package version has failed the automated checks.

Please navigate to the following link to view the moderation queue.

[X] I have verified that the new version is a stable release.
[X] I have looked to see if there are any Bug reports that prevents a new version being submitted and that no existing Outdated Reports have been created.
[X] I have verified the new version has a Windows binary (EXE or MSI installer, Zip or other archive, etc).

New Software Version
0.26.6
Download location
https://github.com/derailed/k9s/releases/tag/v0.26.6
Package Page
https://community.chocolatey.org/packages/k9s

Related: #2007

@brogers5 Any update on this? K9s is several revs out now and my users are not too happy about it.
Not sure what I can do to help since I did not commit the original recipe. Thank you!!

@derailed, to be clear, I'm not a core maintainer of this repository. I simply wanted to call attention to the fact that this package is simply one among many others that were affected by a breaking change introduced by GitHub.
If you're willing to take a crack at it, you could refer to PRs for the packages that have already been fixed to get an idea of what needs to be done.

Created a new PR to fix this issue since the original one was closed due to lack of updates. Which can be found here: https://github.com/chocolatey-community/chocolatey-packages/pull/2170


python310Packages.aiohomekit: 2.2.16 -> 2.2.17

Description of changes
https://github.com/Jc2k/aiohomekit/releases/tag/2.2.17

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 199871 run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.homekit_controller
python310Packages.aiohomekit
python39Packages.aiohomekit


default redirect_url/target_url after login

If using authorization code grant, when go to login page directly and login (through bookmarking login page), user will be redirected to an error page with message "You should not see this page. Setup your redirect URI".
I understand the problem is due to unknown redirect uri.
UAA's /oauth/authorize route should pass the redirect uri when it redirects the user to the login page. Therefore when user bookmark the login page, it includes the redirect_url and redirect the user back to the correct application after login. The redirect url should match the redirect url list that is set per client.

@clementchi This implementation is on the same lines SAML redirects. Book marking intermediate login page redirects is not supported. The user should only be bookmarking the Application URL which is capable of redirecting to UAA with the proper client id and redirect uri


Q: Does it still function ?

Is it possible to provide some more detailed readme of how it is suppose to work?

It just crashed after trying cmd+alt+r c. Does this package still function? Is it still maintained?

Hi,
I stopped using atom, but still fixed some last issue with regex. On latest version 1.18 running on linux I can't reproduce your problem. Alt+ctrl+r c does exactly what is suppose to do.
I no longer run mac, so there is no way for me to test there.
Thanks


Placeholder text incorrect on the https://polyfill.io/v3/url-builder/ page in the callback text input

Bug Report
What
On the url-builder page, I noticed that the placeholder text for the callback input reads 'Type to filter by name'. This is the same placeholder text as the above filter input. Is this correct? Should it read something like 'Enter callback name'?
Details
Can be seen on thi page of the polyfill.io website: https://polyfill.io/v3/url-builder/
Thanks for providing such an awesome service!

Thanks for spotting this!


feat: Add more specific tags

Description
This PR will allow this module to add tags on :

load balancer only
all taget groups
specific target group

Motivation and Context
Sometimes, we want to add tags only in a specific resource, and not to all resources. Example, a target group description tag like "use for admin acess".
Breaking Changes
Nothing.
How Has This Been Tested?
Make a terraform plan on tests
terraform plan -out /tmp/plan.out examples/complete-alb
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

data.aws_route53_zone.this: Refreshing state...
data.aws_vpc.default: Refreshing state...
data.aws_subnet_ids.all: Refreshing state...

------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_pet.this will be created
  + resource "random_pet" "this" {
      + id        = (known after apply)
      + length    = 2
      + separator = "-"
    }

  # module.acm.aws_acm_certificate.this[0] will be created
  + resource "aws_acm_certificate" "this" {
      + arn                       = (known after apply)
      + domain_name               = "terraform-aws-modules.modules.tf"
      + domain_validation_options = (known after apply)
      + id                        = (known after apply)
      + subject_alternative_names = []
      + validation_emails         = (known after apply)
      + validation_method         = "DNS"
    }

  # module.acm.aws_acm_certificate_validation.this[0] will be created
  + resource "aws_acm_certificate_validation" "this" {
      + certificate_arn         = (known after apply)
      + id                      = (known after apply)
      + validation_record_fqdns = (known after apply)
    }

  # module.acm.aws_route53_record.validation[0] will be created
  + resource "aws_route53_record" "validation" {
      + allow_overwrite = true
      + fqdn            = (known after apply)
      + id              = (known after apply)
      + name            = (known after apply)
      + records         = (known after apply)
      + ttl             = 60
      + type            = (known after apply)
      + zone_id         = "Z04759191PM0ISO1FPE5A"
    }

  # module.acm.aws_route53_record.validation[1] will be created
  + resource "aws_route53_record" "validation" {
      + allow_overwrite = true
      + fqdn            = (known after apply)
      + id              = (known after apply)
      + name            = (known after apply)
      + records         = (known after apply)
      + ttl             = 60
      + type            = (known after apply)
      + zone_id         = "Z04759191PM0ISO1FPE5A"
    }

  # module.alb.aws_lb.this[0] will be created
  + resource "aws_lb" "this" {
      + arn                        = (known after apply)
      + arn_suffix                 = (known after apply)
      + dns_name                   = (known after apply)
      + drop_invalid_header_fields = false
      + enable_deletion_protection = false
      + enable_http2               = true
      + id                         = (known after apply)
      + idle_timeout               = 60
      + internal                   = false
      + ip_address_type            = "ipv4"
      + load_balancer_type         = "application"
      + name                       = (known after apply)
      + security_groups            = (known after apply)
      + subnets                    = [
          + "subnet-88059fd2",
          + "subnet-8c3169ea",
          + "subnet-f2ae86ba",
        ]
      + tags                       = (known after apply)
      + vpc_id                     = (known after apply)
      + zone_id                    = (known after apply)

      + subnet_mapping {
          + allocation_id = (known after apply)
          + subnet_id     = (known after apply)
        }

      + timeouts {
          + create = "10m"
          + delete = "10m"
          + update = "10m"
        }
    }

  # module.alb.aws_lb_listener.frontend_http_tcp[0] will be created
  + resource "aws_lb_listener" "frontend_http_tcp" {
      + arn               = (known after apply)
      + id                = (known after apply)
      + load_balancer_arn = (known after apply)
      + port              = 80
      + protocol          = "HTTP"
      + ssl_policy        = (known after apply)

      + default_action {
          + order            = (known after apply)
          + target_group_arn = (known after apply)
          + type             = "forward"
        }
    }

  # module.alb.aws_lb_listener.frontend_https[0] will be created
  + resource "aws_lb_listener" "frontend_https" {
      + arn               = (known after apply)
      + certificate_arn   = (known after apply)
      + id                = (known after apply)
      + load_balancer_arn = (known after apply)
      + port              = 443
      + protocol          = (known after apply)
      + ssl_policy        = (known after apply)

      + default_action {
          + order            = (known after apply)
          + target_group_arn = (known after apply)
          + type             = "forward"
        }
    }

  # module.alb.aws_lb_target_group.main[0] will be created
  + resource "aws_lb_target_group" "main" {
      + arn                                = (known after apply)
      + arn_suffix                         = (known after apply)
      + deregistration_delay               = 10
      + id                                 = (known after apply)
      + lambda_multi_value_headers_enabled = false
      + load_balancing_algorithm_type      = (known after apply)
      + name                               = (known after apply)
      + name_prefix                        = "h1"
      + port                               = 80
      + protocol                           = "HTTP"
      + proxy_protocol_v2                  = false
      + slow_start                         = 0
      + tags                               = {
          + "InstanceTargetGroupTag" = "baz"
          + "MyGlobalTargetGroupTag" = "bar"
          + "Name"                   = "h1"
          + "Project"                = "Unknown"
        }
      + target_type                        = "instance"
      + vpc_id                             = "vpc-cad23db3"

      + health_check {
          + enabled             = true
          + healthy_threshold   = 3
          + interval            = 30
          + matcher             = "200-399"
          + path                = "/healthz"
          + port                = "traffic-port"
          + protocol            = "HTTP"
          + timeout             = 6
          + unhealthy_threshold = 3
        }

      + stickiness {
          + cookie_duration = (known after apply)
          + enabled         = (known after apply)
          + type            = (known after apply)
        }
    }

  # module.alb.aws_lb_target_group.main[1] will be created
  + resource "aws_lb_target_group" "main" {
      + arn                                = (known after apply)
      + arn_suffix                         = (known after apply)
      + deregistration_delay               = 300
      + id                                 = (known after apply)
      + lambda_multi_value_headers_enabled = true
      + load_balancing_algorithm_type      = (known after apply)
      + name                               = (known after apply)
      + name_prefix                        = "l1-"
      + proxy_protocol_v2                  = false
      + slow_start                         = 0
      + tags                               = {
          + "MyGlobalTargetGroupTag" = "bar"
          + "Name"                   = "l1-"
          + "Project"                = "Unknown"
        }
      + target_type                        = "lambda"
      + vpc_id                             = "vpc-cad23db3"

      + health_check {
          + enabled             = (known after apply)
          + healthy_threshold   = (known after apply)
          + interval            = (known after apply)
          + matcher             = (known after apply)
          + path                = (known after apply)
          + port                = (known after apply)
          + protocol            = (known after apply)
          + timeout             = (known after apply)
          + unhealthy_threshold = (known after apply)
        }

      + stickiness {
          + cookie_duration = (known after apply)
          + enabled         = (known after apply)
          + type            = (known after apply)
        }
    }

  # module.security_group.aws_security_group.this_name_prefix[0] will be created
  + resource "aws_security_group" "this_name_prefix" {
      + arn                    = (known after apply)
      + description            = "Security group for example usage with ALB"
      + egress                 = (known after apply)
      + id                     = (known after apply)
      + ingress                = (known after apply)
      + name                   = (known after apply)
      + name_prefix            = (known after apply)
      + owner_id               = (known after apply)
      + revoke_rules_on_delete = false
      + tags                   = (known after apply)
      + vpc_id                 = "vpc-cad23db3"
    }

  # module.security_group.aws_security_group_rule.egress_rules[0] will be created
  + resource "aws_security_group_rule" "egress_rules" {
      + cidr_blocks              = [
          + "<IP_ADDRESS>/0",
        ]
      + description              = "All protocols"
      + from_port                = -1
      + id                       = (known after apply)
      + ipv6_cidr_blocks         = [
          + "::/0",
        ]
      + prefix_list_ids          = []
      + protocol                 = "-1"
      + security_group_id        = (known after apply)
      + self                     = false
      + source_security_group_id = (known after apply)
      + to_port                  = -1
      + type                     = "egress"
    }

  # module.security_group.aws_security_group_rule.ingress_rules[0] will be created
  + resource "aws_security_group_rule" "ingress_rules" {
      + cidr_blocks              = [
          + "<IP_ADDRESS>/0",
        ]
      + description              = "HTTP"
      + from_port                = 80
      + id                       = (known after apply)
      + ipv6_cidr_blocks         = []
      + prefix_list_ids          = []
      + protocol                 = "tcp"
      + security_group_id        = (known after apply)
      + self                     = false
      + source_security_group_id = (known after apply)
      + to_port                  = 80
      + type                     = "ingress"
    }

  # module.security_group.aws_security_group_rule.ingress_rules[1] will be created
  + resource "aws_security_group_rule" "ingress_rules" {
      + cidr_blocks              = [
          + "<IP_ADDRESS>/0",
        ]
      + description              = "All IPV4 ICMP"
      + from_port                = -1
      + id                       = (known after apply)
      + ipv6_cidr_blocks         = []
      + prefix_list_ids          = []
      + protocol                 = "icmp"
      + security_group_id        = (known after apply)
      + self                     = false
      + source_security_group_id = (known after apply)
      + to_port                  = -1
      + type                     = "ingress"
    }

Plan: 14 to add, 0 to change, 0 to destroy.

terraform plan -out=/tmp/plan.out examples/complete-nlb
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

data.aws_route53_zone.this: Refreshing state...
data.aws_vpc.default: Refreshing state...
data.aws_subnet_ids.all: Refreshing state...

------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # aws_eip.this[0] will be created
  + resource "aws_eip" "this" {
      + allocation_id     = (known after apply)
      + association_id    = (known after apply)
      + domain            = (known after apply)
      + id                = (known after apply)
      + instance          = (known after apply)
      + network_interface = (known after apply)
      + private_dns       = (known after apply)
      + private_ip        = (known after apply)
      + public_dns        = (known after apply)
      + public_ip         = (known after apply)
      + public_ipv4_pool  = (known after apply)
      + vpc               = true
    }

  # aws_eip.this[1] will be created
  + resource "aws_eip" "this" {
      + allocation_id     = (known after apply)
      + association_id    = (known after apply)
      + domain            = (known after apply)
      + id                = (known after apply)
      + instance          = (known after apply)
      + network_interface = (known after apply)
      + private_dns       = (known after apply)
      + private_ip        = (known after apply)
      + public_dns        = (known after apply)
      + public_ip         = (known after apply)
      + public_ipv4_pool  = (known after apply)
      + vpc               = true
    }

  # aws_eip.this[2] will be created
  + resource "aws_eip" "this" {
      + allocation_id     = (known after apply)
      + association_id    = (known after apply)
      + domain            = (known after apply)
      + id                = (known after apply)
      + instance          = (known after apply)
      + network_interface = (known after apply)
      + private_dns       = (known after apply)
      + private_ip        = (known after apply)
      + public_dns        = (known after apply)
      + public_ip         = (known after apply)
      + public_ipv4_pool  = (known after apply)
      + vpc               = true
    }

  # random_pet.this will be created
  + resource "random_pet" "this" {
      + id        = (known after apply)
      + length    = 2
      + separator = "-"
    }

  # module.acm.aws_acm_certificate.this[0] will be created
  + resource "aws_acm_certificate" "this" {
      + arn                       = (known after apply)
      + domain_name               = "terraform-aws-modules.modules.tf"
      + domain_validation_options = (known after apply)
      + id                        = (known after apply)
      + subject_alternative_names = []
      + validation_emails         = (known after apply)
      + validation_method         = "DNS"
    }

  # module.acm.aws_acm_certificate_validation.this[0] will be created
  + resource "aws_acm_certificate_validation" "this" {
      + certificate_arn         = (known after apply)
      + id                      = (known after apply)
      + validation_record_fqdns = (known after apply)
    }

  # module.acm.aws_route53_record.validation[0] will be created
  + resource "aws_route53_record" "validation" {
      + allow_overwrite = true
      + fqdn            = (known after apply)
      + id              = (known after apply)
      + name            = (known after apply)
      + records         = (known after apply)
      + ttl             = 60
      + type            = (known after apply)
      + zone_id         = "Z04759191PM0ISO1FPE5A"
    }

  # module.acm.aws_route53_record.validation[1] will be created
  + resource "aws_route53_record" "validation" {
      + allow_overwrite = true
      + fqdn            = (known after apply)
      + id              = (known after apply)
      + name            = (known after apply)
      + records         = (known after apply)
      + ttl             = 60
      + type            = (known after apply)
      + zone_id         = "Z04759191PM0ISO1FPE5A"
    }

  # module.nlb.aws_lb.this[0] will be created
  + resource "aws_lb" "this" {
      + arn                              = (known after apply)
      + arn_suffix                       = (known after apply)
      + dns_name                         = (known after apply)
      + enable_cross_zone_load_balancing = false
      + enable_deletion_protection       = false
      + id                               = (known after apply)
      + internal                         = false
      + ip_address_type                  = "ipv4"
      + load_balancer_type               = "network"
      + name                             = (known after apply)
      + security_groups                  = (known after apply)
      + subnets                          = (known after apply)
      + tags                             = (known after apply)
      + vpc_id                           = (known after apply)
      + zone_id                          = (known after apply)

      + subnet_mapping {
          + allocation_id = (known after apply)
          + subnet_id     = "subnet-88059fd2"
        }
      + subnet_mapping {
          + allocation_id = (known after apply)
          + subnet_id     = "subnet-8c3169ea"
        }
      + subnet_mapping {
          + allocation_id = (known after apply)
          + subnet_id     = "subnet-f2ae86ba"
        }

      + timeouts {
          + create = "10m"
          + delete = "10m"
          + update = "10m"
        }
    }

  # module.nlb.aws_lb_listener.frontend_http_tcp[0] will be created
  + resource "aws_lb_listener" "frontend_http_tcp" {
      + arn               = (known after apply)
      + id                = (known after apply)
      + load_balancer_arn = (known after apply)
      + port              = 81
      + protocol          = "TCP_UDP"
      + ssl_policy        = (known after apply)

      + default_action {
          + order            = (known after apply)
          + target_group_arn = (known after apply)
          + type             = "forward"
        }
    }

  # module.nlb.aws_lb_listener.frontend_http_tcp[1] will be created
  + resource "aws_lb_listener" "frontend_http_tcp" {
      + arn               = (known after apply)
      + id                = (known after apply)
      + load_balancer_arn = (known after apply)
      + port              = 82
      + protocol          = "UDP"
      + ssl_policy        = (known after apply)

      + default_action {
          + order            = (known after apply)
          + target_group_arn = (known after apply)
          + type             = "forward"
        }
    }

  # module.nlb.aws_lb_listener.frontend_http_tcp[2] will be created
  + resource "aws_lb_listener" "frontend_http_tcp" {
      + arn               = (known after apply)
      + id                = (known after apply)
      + load_balancer_arn = (known after apply)
      + port              = 83
      + protocol          = "TCP"
      + ssl_policy        = (known after apply)

      + default_action {
          + order            = (known after apply)
          + target_group_arn = (known after apply)
          + type             = "forward"
        }
    }

  # module.nlb.aws_lb_listener.frontend_https[0] will be created
  + resource "aws_lb_listener" "frontend_https" {
      + arn               = (known after apply)
      + certificate_arn   = (known after apply)
      + id                = (known after apply)
      + load_balancer_arn = (known after apply)
      + port              = 84
      + protocol          = (known after apply)
      + ssl_policy        = (known after apply)

      + default_action {
          + order            = (known after apply)
          + target_group_arn = (known after apply)
          + type             = "forward"
        }
    }

  # module.nlb.aws_lb_target_group.main[0] will be created
  + resource "aws_lb_target_group" "main" {
      + arn                                = (known after apply)
      + arn_suffix                         = (known after apply)
      + deregistration_delay               = 300
      + id                                 = (known after apply)
      + lambda_multi_value_headers_enabled = false
      + load_balancing_algorithm_type      = (known after apply)
      + name                               = (known after apply)
      + name_prefix                        = "tu1-"
      + port                               = 81
      + protocol                           = "TCP_UDP"
      + proxy_protocol_v2                  = false
      + slow_start                         = 0
      + tags                               = {
          + "Name"    = "tu1-"
          + "tcp_udp" = "true"
        }
      + target_type                        = "instance"
      + vpc_id                             = "vpc-cad23db3"

      + health_check {
          + enabled             = (known after apply)
          + healthy_threshold   = (known after apply)
          + interval            = (known after apply)
          + matcher             = (known after apply)
          + path                = (known after apply)
          + port                = (known after apply)
          + protocol            = (known after apply)
          + timeout             = (known after apply)
          + unhealthy_threshold = (known after apply)
        }

      + stickiness {
          + cookie_duration = (known after apply)
          + enabled         = (known after apply)
          + type            = (known after apply)
        }
    }

  # module.nlb.aws_lb_target_group.main[1] will be created
  + resource "aws_lb_target_group" "main" {
      + arn                                = (known after apply)
      + arn_suffix                         = (known after apply)
      + deregistration_delay               = 300
      + id                                 = (known after apply)
      + lambda_multi_value_headers_enabled = false
      + load_balancing_algorithm_type      = (known after apply)
      + name                               = (known after apply)
      + name_prefix                        = "u1-"
      + port                               = 82
      + protocol                           = "UDP"
      + proxy_protocol_v2                  = false
      + slow_start                         = 0
      + tags                               = {
          + "Name" = "u1-"
        }
      + target_type                        = "instance"
      + vpc_id                             = "vpc-cad23db3"

      + health_check {
          + enabled             = (known after apply)
          + healthy_threshold   = (known after apply)
          + interval            = (known after apply)
          + matcher             = (known after apply)
          + path                = (known after apply)
          + port                = (known after apply)
          + protocol            = (known after apply)
          + timeout             = (known after apply)
          + unhealthy_threshold = (known after apply)
        }

      + stickiness {
          + cookie_duration = (known after apply)
          + enabled         = (known after apply)
          + type            = (known after apply)
        }
    }

  # module.nlb.aws_lb_target_group.main[2] will be created
  + resource "aws_lb_target_group" "main" {
      + arn                                = (known after apply)
      + arn_suffix                         = (known after apply)
      + deregistration_delay               = 10
      + id                                 = (known after apply)
      + lambda_multi_value_headers_enabled = false
      + load_balancing_algorithm_type      = (known after apply)
      + name                               = (known after apply)
      + name_prefix                        = "t1-"
      + port                               = 83
      + protocol                           = "TCP"
      + proxy_protocol_v2                  = false
      + slow_start                         = 0
      + tags                               = {
          + "Name" = "t1-"
        }
      + target_type                        = "ip"
      + vpc_id                             = "vpc-cad23db3"

      + health_check {
          + enabled             = true
          + healthy_threshold   = 3
          + interval            = 30
          + matcher             = (known after apply)
          + path                = "/healthz"
          + port                = "traffic-port"
          + protocol            = "HTTP"
          + timeout             = 6
          + unhealthy_threshold = 3
        }

      + stickiness {
          + cookie_duration = (known after apply)
          + enabled         = (known after apply)
          + type            = (known after apply)
        }
    }

  # module.nlb.aws_lb_target_group.main[3] will be created
  + resource "aws_lb_target_group" "main" {
      + arn                                = (known after apply)
      + arn_suffix                         = (known after apply)
      + deregistration_delay               = 300
      + id                                 = (known after apply)
      + lambda_multi_value_headers_enabled = false
      + load_balancing_algorithm_type      = (known after apply)
      + name                               = (known after apply)
      + name_prefix                        = "t2-"
      + port                               = 84
      + protocol                           = "TLS"
      + proxy_protocol_v2                  = false
      + slow_start                         = 0
      + tags                               = {
          + "Name" = "t2-"
        }
      + target_type                        = "instance"
      + vpc_id                             = "vpc-cad23db3"

      + health_check {
          + enabled             = (known after apply)
          + healthy_threshold   = (known after apply)
          + interval            = (known after apply)
          + matcher             = (known after apply)
          + path                = (known after apply)
          + port                = (known after apply)
          + protocol            = (known after apply)
          + timeout             = (known after apply)
          + unhealthy_threshold = (known after apply)
        }

      + stickiness {
          + cookie_duration = (known after apply)
          + enabled         = (known after apply)
          + type            = (known after apply)
        }
    }

Plan: 17 to add, 0 to change, 0 to destroy.

terraform plan -out /tmp/plan.out examples/disabled
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

------------------------------------------------------------------------

No changes. Infrastructure is up-to-date.

This means that Terraform did not detect any differences between your
configuration and real physical resources that exist. As a result, no
actions need to be performed.

Can you please review this PR ?

Thanks @quentin9696 !
v5.4.0 has been just released.

Thanks @antonbabenko !


python311Packages.google-cloud-datacatalog: 3.17.0 -> 3.17.2

Changelog: https://github.com/googleapis/google-cloud-python/blob/google-cloud-datacatalog-v3.17.2/packages/google-cloud-datacatalog/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 281123 run on aarch64-linux 1

4 packages marked as broken and skipped:

python311Packages.dbt-bigquery
python311Packages.dbt-bigquery.dist
python311Packages.google-cloud-bigquery
python311Packages.google-cloud-bigquery.dist

2 packages built:

python311Packages.google-cloud-datacatalog
python311Packages.google-cloud-datacatalog.dist


$input-height-inner isn't a valid CSS value

Are we missed something after latest upgrade? Before was ok...
Module build failed (from ./node_modules/sass-loader/lib/loader.js):

$input-height-inner:                    calc(#{$input-line-height * 1em} + #{$input-padding-y * 2}) !default;
                                                                                ^
      1.222em*em isn't a valid CSS value.
      in /Users/.../.../node_modules/bootstrap/scss/_variables.scss (line 491, column 100)

@MartijnCuppens We probably need to rewrite this to move the operator and math outside the escaped variable.

This looks like a duplicate of https://github.com/twbs/bootstrap/issues/28240, but with em. If you remove the em from the line-height (1.222em), you should be fine.


Add MigIdentity CRD for non-admin UX improvement

We need a new CRD MigIdentity which will contain a user's identity token to be consumed by a MigPlan. Today we are simply using a secretRef, but we want the controller to reconcile on the MigIdentity objects to validate whether they can currently authorize against the given cluster. This will be used to determine if a user's oauth token has expired.

The MigIdentity CRs will be created in the tenant's namespace. it should contain at least the following spec fields:
type MigIdentitySpec struct {
  identitySecretRef kapi.SecretReference
  migclusterRef kapi.ObjectReference
  type: string // The type of identity token this is (oauth/serviceaccount)
  expired: boolean // Only used with oauth, but could also indicate an SA token has been deleted
}

There will be a 1-1 mapping of MigIdentity to MigCluster. The controller will be responsible for reconciling on the migIdentitys at a predetermined length of time (5-10 mins?) or on the change of the identity secret. If an oauth token has expired, set the spec field accordingly.
Prior to running a migration, all migIdentities should be validated once more to ensure the token hasn't expired and is valid.

@dymurray closing this issue since it is checked in #388. Please re-open if required. Thanks


feat: Allow inline configuration in addition to JSON files

Currently the only way to pass additional configuration is by passing a JSON file path. However, this means that folks have to introduce another configuration file to their projects, even for the smallest changes to the default configuration. It also means that it is not possible to run JavaScript over the config if using .eslintrc.js.
It should be simple enough to change the customRuleConfig function to just return the parameter if it's an object and to only construct a path for and parse JSON when it is a string.
This would also ease testing different configurations as the configurations could live inline with the tests rather than needing multiple files.

Good idea. At the end it'll be anyway a fatigue - either a long eslint config file or yet another config file. ;-)
I'm taking a stab via #9.

@saramarcondes v1.2.0 published to npm! Thanks again for the contribution!