Translate values for campaigns

WDYT about using names without _id postfix for named values?
account_status: :pending <-> account_status_id: 3
This reads more intuitive, but on the other side allows for ambiguity when both attributes are passed.

I like the idea, since then we don't need to inspect the value at all and can always assume that with _id suffix it's numeric and without it's human readable.

can always assume that with _id suffix it's numeric

We already fell into that trap. For example tax_id is not numeric, but rather something like DE123123. There are a few others. Not sure if this applies here, just wanted to warn you 😉

What I mean ist that keys, that are present in Const::CONSTS, but are passed without the _id suffix, need translating. The others can be ignored.

There are some that still cannot be ignored, since they don't have an _id suffix, but still... WDYT?

🍄


Kebibyte should be kibibyte

Just for your interest, the proper name is kibibyte, not kebibyte, which I noticed in your code.
https://en.wikipedia.org/wiki/Kibibyte
Best regards! :)

This is fixed in the 3.0 release on Nuget. It's been a long time, but thanks for the correction!


Allow openssldir to be configured.

This PR addresses the discussion from #162 given the unresponsiveness of the author of that PR.
It won't directly resolve #161, but once this is merged, a subsequent PR can be made to the openssl-sys crate to allow propagation of the openssl dir to this code.

I'll do a release when https://github.com/alexcrichton/openssl-src-rs/pull/217 is merged


Flow errors about react-native and fbjs

Hey!
Version: 1.1.1
I still got errors about react-native and fbjs, even with the recent commits.

It's a problem already invoked here (fbjs) and here (react-native).
My .flowconfig
[ignore]
<PROJECT_ROOT>/node_modules/fbjs/.*                       // needed for create-react-app
<PROJECT_ROOT>/node_modules/styled-components/src/.*

[options]
unsafe.enable_getters_and_setters=true
suppress_comment=.*\\$FlowIssue

Not sure but maybe we could just add \\$FlowIssue to fix those last errors?
Thanks for the help.

You also need to add some settings to the libs section. See flow-support docs for more info

I had tried these settings but without installing flow-typed. 😅
So now that fixes the react-native errors but I still have the fbjs errors.
For your info: there are several types missing in the Lodash types definition (I got errors on find and map). These types are also missing in the original file. I'll submit a PR on flowtype/flow-typed.

Could you post the whole .flowconfig?

Here it is:
[ignore]
<PROJECT_ROOT>/node_modules/fbjs/.*
<PROJECT_ROOT>/node_modules/styled-components/src/.*

[libs]
flow-typed
node_modules/styled-components/flow-typed/react-native.js
node_modules/styled-components/flow-typed/glamor_vx.x.x.js
node_modules/styled-components/flow-typed/inline-style-prefixer_vx.x.x.js

[options]
unsafe.enable_getters_and_setters=true
suppress_comment=.*\\$FlowIssue

And the errors:

You should also add:
node_modules/styled-components/flow-typed/fbjs_vx.x.x.js

This should probably land in docs as well.

Actually this line
[ignore]
<PROJECT_ROOT>/node_modules/fbjs/.*

is not needed anymore with Create-React-App.
By removing this line, I got rid of the errors.
I think we can close! 🎉


[express generator] handle endpoints in __package__.yml

Currently endpoints in package.yml cause the express generator to throw Cannot generate register() because fern filepath is empty

closing as no customer has asked for it


Any elegant way to override the style of Control, specifically, the DataGridRow?

I tried to hide some of the rows in the DataGrid through DataBinding by changing the RowStyle.
<DataGrid.RowStyle>
    <Style TargetType="DataGridRow">
        <Setter Property="Visibility" Value="{Binding Path=Visibility}"/>
    </Style>
</DataGrid.RowStyle>

While adding the code above into routine would prevent other predefined RowStyle developed by Mahapps work correctly.
What I do now is to copy all the code related to the DataGridRow from Controls.DataGrid.xaml and add them with the above code together into my routine. This time works.
I would like to know if there is an elegant way to change the style without copying&pasting a bunch of code from the source code.
Thanks!

Thank you so much.The double inherit worked for me.


fix: fastfetch to use HOST_ARCH

fastfetch package release naming was changed.
HOST_CPU resolves to x86_x64, but the fastfetch releases now have amd64 which is HOST_ARCH
fixes #1130
closes #1131

Thanks. This is a duplicate of #1131 and fails to mention that it fixes #1130 (and so is not linked and would not close by reference if merged).


fix drift sign in the PDSP-specific service provider initialization

Extend the fix of
https://github.com/LArSoft/lardataalg/commit/009551b1203bb03546db94060354e54fcacec6db
that didn't make it in to the ProtoDUNE-SP specific version of the DetectorPropertiesData initialization.  The commit above fixes the DetectorPropertiesStandard version but not the PDSP-specific version.  Fix is here.

Here are some plots showing the symptoms and fix.  These are the X locations of pandora2 track trajectory points in v09_92_00, v10 before this PR, and v10 after this PR.  v09_92_00 has around 50 anab::T0's in the first event in the CI test file, while v10 without this PR has zero.  With this PR, the anab::T0's are restored.


Add support for RethinkDB

Related: https://github.com/travis-ci/travis-ci/issues/2048

@nviennot can't see any obvious conflicts, but perhaps trying to clear that up will help get this in faster?

+1

@mbroadst I've updated the branch :)

:+1: +1 here

:+1:
Prevents me from moving off of the legacy infrastructure since I'm installing this dependency via apt to make my builds work.

+1 Bump

+1 Bump... need RethinkDB for the new Travis architecture

:+1: Is there anything we can do to get this merged? Anything missing?

+1 as well

+1

No longer needed.
Just add:
addons:
  rethinkdb: "2.3"

https://docs.travis-ci.com/user/database-setup/#RethinkDB


Move Coords to Client Side Settings

Don't default everything to a spoofer map. Move Coords to client side settings.

no problemo! let me know if I did it right this time.

Could it be that this is completly disabling the possibility to disable that feature for the admin?
For me e.g I would nerver give user the possibility to show the coords

Someone can PR something like this:
https://github.com/WatWowMap/ReactMap/blob/main/server/src/services/ui/clientOptions.js#L96-L98

like this i build this morning?
https://github.com/ReuschelCGN/ReactMap/blob/666ce7194a090f1e8144f746efa26eac75ca4155/server/src/services/ui/clientOptions.js#L106


include train length

new real-time allows this

Nice! Maybe we should think about like including a features: {} with like the flags rather than just having it on the root object?

double decker, ev ...

this would expand to train sets, eg sydney, tangara waratah etc


NIFI-10250 Added query string as attribute in ListenHTTP processor

Summary
Extends the ListenHTTP processor by adding the query string of incoming requests as an attribute to the flow file.
NIFI-10250
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[ ] Build completed using mvn clean install -P contrib-check

[ ] JDK 8
[ ] JDK 11
[ ] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[x] Documentation formatting appears as expected in rendered files

I have spent the whole day trying to build the main branch (or the rel/nifi-1.16.3 tag) and I am giving up on this now. I don't think my change is related to the tests failing but you never know..
In case anyone wants to have a look at this, the code (more like the code line) can be found here: https://github.com/meppig/nifi/tree/NIFI-10250


Beginners question (probably)

When copying and pasting in the examples into an html file and running it in a browser (chrome version 60) and of course linking to the transpiled version (lit-html.js). Chrome reports errors about the export keyword not being recognized.. (SyntaxError: Unexpected token export)..
Even when running it in NodeJS by just require('lit-html') after npm installing it shows this same error...
What am I missing here?

You will need Chrome 61 and <script type=module>.

You can also use a module bundler like Webpack or Rollup.
That way, it will work in any browser.

Tried that with webpack with no success. Could that be because the tsconfig for lit-html is set to target es2017?

Maybe lit-html should not publish those src files (ts, build config) to npm.

@JohnGorter can you share your webpack config? Webpack should be able to handle standard ES6 I hope.
@nicolasparada I can remove the .ts files from npm

I have the same problem with webpack only running babel es2015.

try to post it tomorrow.. away from work now... sorry.

Module support is spreading, so this should be easier to try out. Please repopen is we need further details on using modules.


Build-size's resolve link should force a recheck

Eg, https://github.com/ampproject/amphtml/pull/23442/checks?check_run_id=173583540. The "resolve" link (https://amp-bundle-size-bot.appspot.com/) should allow us to force the build-size bot to recheck the GH approvals.

That makes sense. I wonder if the PR approval model is the best way, or whether we should move to an explicit approval of the check using an action button (which is a relatively new feature for GitHub Apps, that's why it wasn't considered before)
wdyt?

I like being able to approve a PR with a general PR approval, though. Would this require me to hit a second button?

It would (from the PR you'd have to click the Details link on the check, and then the Approve link). So you prefer the current approach

Hmm... the problem with re-running the check to verify the approvals is that it can't tell these two scenarios apart:

bundle-size approval is required → PR is approved → some error causes the approval not to be registered
bundle-size approval is required → PR is approved → commit is pushed → bundle-size approval is required again

One advantage of separating general PR approval from size-increase approval is that a reviewer who happens to be a bundle-size owner a review a PR without inadvertently allowing the size increase to sneak through. I'll defer to @danielrozenberg's judgement on this, since he's more aware of the corner cases.
While on the topic of approvals, I'd like to make a case for #141, which proposes that we switch the size increase approvers from a hard-coded list to the runtime working group. WDYT?

Shouldn't it be checking the order of commits/approval?

I'll have to check whether the API supports that, but it does complicate the app's code 1,000× >__>

We discussed this offline in the infra team and came to agree that fixing this is not worth the effort, given the rarity of the root cause (GitHub API/webhook failures) - the easiest solution in those cases is to rebase the last commit or close/reopen the PR. I'm going to close this issue as a won't-fix


Allow for configurable registration url

This enables the combustion script to perform the SCC registration against an RMT/SUMA

Thank you for your PR!


Pause/resume Spotify media_player before/after Chime TTS notification

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
This feature request is based on the comment made by @dbullendsl.
When the announce parameter is enabled, Spotify media_players paused before Chime TTS notifications, however they are not resumed once the notification ends.
Spotify media_players can only play audio from Spotify and cannot play arbitrary files (neither local files nor remote URLs) - so they cannot currently be used as a media_player for Chime TTS notification playback. However, it would be useful to have them be paused/resume before/after Chime TTS notification playback.
My idea is to include them in the list of target media_players sent to the chime_tts.say service, and have Chime TTS identify them as Spotify media_players and handle the pause/resume (when announce is true).
Describe the solution you'd like
Spotify media_players should automatically resume playback once the notification from Chime TTS is complete.

After using chime_tts.say_url to generate the audio file I turn down the volume on my music (actually fade it over 1 second with another script) and then play the file, fading the music back up after the playback is complete.
That said, I play all of my voice notifications through Google minis and all of my music via Google Chromecast audios, so they are separate devices.

You should already be able to do this in chime_tts.say by setting announce: true.


Editing a previously saved draft cannot be saved again

Create a new object
Save it as a draft
Go back to edit the draft
Try and save the draft again - it does not appear to save.
Look at the javascript errors in the console

This is because the response from the controller on update is:
"attached_files_attributes"=>{"0"=>{"label"=>"two", "_destroy"=>"", "hide"=>"0", "id"=>"302"}}

ArgumentError (Could not find or build blob: expected attachable, got #<ActiveStorage::Attached::One:0x00007fa796b081b0 @name="file", @record=#<AttachedFile id: 302, label: "two", hide: false, work_id: 384, created_at: "2020-11-09 20:10:18", updated_at: "2020-11-09 20:10:18">>):


Full trace information

For deep analysis having an IR slice of all instructions that interacted with labels is important to get accurate information about what went on during execution. Not having it means we are just guessing, and that might not be good enough if we want to collect accurate invariants about the parser.
This means instead of logging input_bytes/cmp_bytes we will have logs in the form
cmp (label 1, const)
cmp (label 1, label 2)
etc etc
We don't even need to store this entire log in memory, but instead can be dumping to disk as we need. This would be an improvement over keeping track of input_bytes/cmp_bytes in memory and its another thing we can shove to post processing.

We might want to have this issue block on #84.


feature request: Sync secret to target ns

I would like to use the operator to simply sync an already existing secret from ns A to B.
kind: ClusterSecret
apiVersion: clustersecret.io/v1
metadata:
  namespace: ns-A
  name: default-wildcard-certifiate
matchNamespace:
  - ns-B
avoidNamespaces:
  - supersecret-ns
#  data: # Commented-out means transparent sync of all fields
#    tls.crt: BASE64
#    tls.key: BASE64

Let me know what you think here, I might dig deeper in the code if you think it's doable.

This is already possible using the Value from Secret functionality
kind: ClusterSecret
apiVersion: clustersecret.io/v1
metadata:
  namespace: <destination-namespace>
  name: <secret-name>
matchNamespace:
  - <destination-namespace>
avoidNamespaces:
  - <avoid-namespace>
data:
  valueFrom:
    secretKeyRef:
      name: <source-secret>
      namespace: <source-namespace>```

Thank you, this is awesome!

One more question here: what happens to the target Secret if it already exists? Will it get overwritten?

@mihaigalos Im sorry to ask but have you read the documentation? Both of your questions are answered there. (I am a user not a developer on this project - the same as you).
https://clustersecret.com/config/

replace_exisiting
This enviroment variable is set the behaviour when an existing secret with same same conflicts. Default is to ignore it and do nothing (to not loose any unintentional data) But in some cases we want ClusterSecret to update/reeplace it. In that case set this varaible to 'true'.

I searched for overwrite before asking. Didn't see this flag. Thank you.


Updated: start early if we have internet connection

quite annoying when you have to wait 60 seconds every time you want to update even if you have already been online for awhile

@adeebshihadeh what do you think of something like this? after this pr https://github.com/commaai/openpilot/pull/30492 you have to wait 60 seconds after going offroad to be able to check for updates, which is quite frustrating since you've already had internet connection for awhile by that point


Display back links to issues that have noted this issue

List of issues that links to this issue is very useful in Web interface. Please show the same in app

Unfortunately the API doesn't provide that information [1], so we can't implement it.
We already show all the issue events the API supports.
[1] https://developer.github.com/v3/issues/events/

Yesterday I've sent suggestion
"Issue event for case where issue was referenced in other issue. Web
interface display this kind of back references and this are very useful.
But issue events api does not provide such information. Please add them"
to<EMAIL_ADDRESS>and today have an answer:
"I agree that would be useful -- I'll pass your suggestion to the API team
to consider, but can't make any promises about if/when this might be
available. Thanks for expressing interest!"

Awesome!
Please ping this issue if you get any response.

Done!


Top toolbar will overflow, when width is too small

Thank you for your feedback. Will try to fix it in next update.


Force language on prompts

Is your feature request related to a problem? Please describe.
I have my vault in multiple languages (spanish and English) sometimes when I use Nostradamus or Agatha Christie, it randomly uses one language or the other for it's response, more commonly english, since that's the prompt language I assume.
Describe the solution you'd like
Describe alternatives you've considered
Force the language of the plugin responses (the classic: write your answer in spanish.) Globally, both in plugin settings and in a command, so I can change fast via ctrl - p the language I want Arcana to answer me with.
Additional context
This could also potentially interfere with other agents that work best with just one language or to act dynamically, not one forced language, like the tags or metadata agent, so this would need some testing, mainly I find this useful with Nostradamos for titles and agatha Christie for text generation

This is a good idea, will triage and try to make time.


Allow modifying the text in the terminal to perform a translation.

Just like with the "New Terminal" mod, have the ability to change English texts to another language for a customized translation.

Resolved in future versions of the project that should allow other mods to modify related text safely.


Add fuzz testing targets

This PR adds fuzz targets for the JSON and Rust backends.
The JSON backend is very small and basically glues existing libraries together. As such, it's the one that should "just work" and so far, it seems solid.
The Rust backend is full of our own code and the fuzzer there immediately found two small bugs: #32 and #33.
We can work on enabling the fuzzer when they're a bit more stable.

Nice ! It will be useful to complete the analyzer and make sure nothing unsupported gets to the compiler.
Would it be possible to keep the fuzz targets inside the pdl-compiler crate ?
I think it would make some sense,  but feel free to object.

Nice ! It will be useful to complete the analyzer and make sure nothing unsupported gets to the compiler.

Yes, it's a magic machine that finds corner cases very quickly :smile:

Would it be possible to keep the fuzz targets inside the pdl-compiler crate ? I think it would make some sense, but feel free to object.

The layout here is what cargo fuzz init gives you. I would not touch that since I dont' really know what it needs or requires from the layout. cargo fuzz run backends_rust_generate compiles the crate with special flags and runs the binary with some arguments to read/write to fuzz/artifacts/backends_rust_generate/.
Because the fuzz binaries are separate from the main crate, I turned the crate into a library. I think it's nice in any case to have pdl-compiler be a library since it allows others to reuse parts of it in other contexts.
Did you have other thoughts here?

The layout here is what cargo fuzz init gives you.

Ok ! Let's keep it that way then.
No other objection on my side


[WIP] MINOR: Find threads leak2

More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Perhaps also try adding verifyNoUnexpectedThreads at the start and end of test which use:
@ExtendWith(value = ClusterTestExtensions.class)

If those tests are the culprit, they would fail immediately hinting that they are leaking tests. I would suggest to start with FeatureCommandUnitTest, DeleteRecordsCommandTest and MetadataQuorumCommandTest.

We might be able to register a JUnit extension that automatically adds follow-up logic for every test without having to add an @After or @AfterAll annotation to individual test suites.


Update Nuke render name with OCIO color space

In GitLab by @support-bot on Mar 31, 2023, 10:32

From Thibault Martegani

Need
We would like to update the name of the render to that :

078_0100_comp_scene_ACEScg_main_v002.0091.exr
[shot_name]_[task]_[colorspace]_[variant]_[version].[frame].[ext]

Softwares concerned
Nuke, Fix

Hello,
I update Anatomy > Templates > Render > File in OpenPype settings
Before : {asset}_{subset}_{<EMAIL_ADDRESS>After : {asset}_{task[short]}_{subset}_ACEScg_{<EMAIL_ADDRESS>
I kept the subset token

I tried a render in Nuke, now we got this :


Create 0059-spiral-matrix-ii.java

File(s) Modified: 0059-spiral-matrix-ii.java
Language(s) Used: java
Submission URL: https://leetcode.com/problems/spiral-matrix-ii/submissions/1131427387/

Important
Please make sure the file name is lowercase and a duplicate file does not already exist before merging.

@a93a could you please take a look into this?

@AmitSaha15  This looks OK, the logic is the same as NeetCode showcased but structured a little bit differently.
I will merge this for now, but I would suggest if you could change the structure of the code to look a bit more similar to the code by NeetCode. Alternativly, you could provide a separate solution in the same file (seperated by comments) where the code is similar to the video code.
Thanks!


MacOS x86_64 testing

I need someone to run the intel-based artifacts and report back. I only have an M1.
https://github.com/savaughn/pokerom-trader/suites/16764383826/artifacts/957354406

if it doesn't work then someone will probably open an issue. closing.


More complete explanations

This PR fleshes out the explanations to a point where most folks should be able to follow them.

This probably needs a run through by someone and can then be merged!

I went through this and fixed one tiny sentence thing from my original commits, and also some logic that was looking for the wrong file name.
Thank you @hectorsector for making this better!
I'm going to merge this, and make the course public. It still needs to be made open source, but it should be ready to take for participants! cc @mattdavis0351 @crichID @carolynshin @a-a-ron

Running into some problems, but I'll open an issue in learning-lab.


Imperative semantics

Non-Ott imperative semantics and typing relation.
Still missing class and method typing, as well as a Countable instance for tasks.

@Aqissiaq it looks like this builds on top of the changes in #18, can you confirm?
I'm thinking it could be a good idea try to fix up #18, merge it to master, and then rebase this PR? The diff would probably be a lot cleaner.

Yes, this builds on #18. I will have a look at that either tonight or tomorrow

I plan to take a look at #18, but then let's aim to get that PR merged before I do a larger review of this one. In particular, I think a lot of the equality decision procedures are not necessary.

@Aqissiaq would be great if this could be rebased on top of new master, so the diff is easier to review.

I thought I did it right, but it still looks a bit messy. The diff for the last commit looks much nicer, at least.

@Aqissiaq ah, I think I see now what the problem is, there is a lot of diverging history. I think what may be easiest is to "re-add" the imperative changes on top of current master, let me do a quick attempt at this.

Closing since superceded by #22


Update README

Add Droidcon fr 2015 and Android Makers Paris 2017 to "Who is using"

Amazing. Thank you :)


bump julia version in ci

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 89.474%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
221

Relevant Lines:
247

💛  - Coveralls


experiment(red_list): changing name of fasttrack dataset

Hey @Marigold is it possible to change fasttracked variable names via the etl or elsewhere after they have been uploaded?

Hey @Marigold is it possible to change fasttracked variable names via the etl or elsewhere after they have been uploaded?

(I'm assuming you're using "super"-fast-track and uploaded it via csv). In general, changes to titles are fine, but you'd have to be very careful when changing short names (I'd avoid that at all... they're not shown anywhere anyway). Changing short name could raise an error if the old variable is using any charts.
As for this PR, changing DRAFT Table 5  Threatened species in each major group by country - show all (1) to Threatened species by country (IUCN, 2022) in YAML (both in snapshot and grapher step) works fine, but as I said, I'd keep the original short names. Same for variables.

Ah I see - I haven't used fasttrack before and I didn't realise I was using super fasttrack. Is it possible to delete this dataset so I can upload it via regular fast track?

Deleting existing datasets is not possible yet, so just create a new one for now and I'll delete this one when I implement it.

Deleting existing datasets is not possible yet, so just create a new one for now and I'll delete this one when I implement it.

Okay that's good to know, thanks!


Omada install script not getting latest version due to filename change

✅ Have you read and understood the above guidelines?
yes
📜 What is the name of the script you are using?
Omada Controller LXC
📂 What was the exact command used to execute the script?
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/omada.sh)"
📝 Provide a clear and concise description of the issue.
The Omada install script runs "grep -o 'https://.*x64.deb'" to find the latest downloadable package from the TP Link listing of Omada downloads. However, it looks like for the latest version (<IP_ADDRESS>) has switched to a different filename: https://static.tp-link.com/upload/software/2024/202412/20241205/omada_v<IP_ADDRESS>_linux_x64_20241128140044.deb
This results in the script downloading the prior version. Manually downloading the file and installing it via dpkg works fine.
⚙ What settings are you using?

[X] Default Settings
[ ] Advanced Settings

🖥 Which Linux distribution are you using?
Debian 12
🔄 Steps to reproduce the issue.
Attempt to update Omada but latest version is not downloaded
❌ Paste the full error output (if available).
n/a
🖼 Additional context (optional).
No response

work fine for me:

Hi @MickLesk, installation works but does not install the latest version. Can you check what version it installed for you? When I used the script it installed 5.14, not 5.15.

The script was always downloading the older version because the URL structure had changed, and the script was still looking for older patterns. By updating the URL extraction to handle the new format, it now correctly fetches the latest version.


feat: port Algebra.Ring.Regular

mathlib SHA: 4e42a9d0a79d151ee359c270e498b1a00cc6fa4e
Porting Notes:

Basically no errors. Only needed to fix some lambdas having implicit arguments.

bors merge


Update joi dependency to<EMAIL_ADDRESS>for<EMAIL_ADDRESS>compatibility. Fixes #15

Just published https://www.npmjs.com/package/joi-extract-type as @15.0.0
Thanks


Updating <*>

Original:
public func <*> <A, B>(f : (A -> B)?, a : A?) -> B? {
	return f.flatMap({ a.map($0) })
 }

What do you think about updating it so that it uses <^>?
New:
public func <*> <A, B>(f : (A -> B)?, a : A?) -> B? {
	return f.flatMap { $0 <^> a }
 }

That is much cleaner.  Submit this as a pull request, please.

@CodaFi Done :+1: , See #44


build simple emitting suns for cosmic map (they're running hot)

Actually not possible without bloom or atmo pass.


Meta Tags

Description
Please include a summary of the change and which issue is fixed.
Please also include relevant motivation and context.
List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

[x] New feature (non-breaking change which adds functionality)

[x] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas

Reviewer: Vinit Shahdeo

@anmolkaur18 It has conflicts, can you please resolve?


feat: extended move so that it separates out CRDs from cluster resources for scenarios where cluster resources depend on CRDs

Hi @chrismellard. Thanks for your PR.
I'm waiting for a jenkins-x or todo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign rajdavies
You can assign the PR to them by writing /assign @rajdavies in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

/ok-to-test

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@chrismellard: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr
6e90303012aa9a0c9580e19f2579653e525b26a3
link
/retest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@chrismellard: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr
6e90303012aa9a0c9580e19f2579653e525b26a3
link
/retest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

looks like it causes this failure:
--- FAIL: TestUpdateNamespaceInYamlFiles (0.26s)
  | move_test.go:19: generating output to /tmp/351631442
  | move_test.go:33:
  | Error Trace:	move_test.go:33
  | Error:      	unable to find file "/tmp/351631442/cluster/jx/lighthouse/lighthousejobs-crd.yaml"
  | Test:       	TestUpdateNamespaceInYamlFiles
  | move_test.go:34: generated expected file /tmp/351631442/cluster/jx/lighthouse/lighthousejobs-crd.yaml
  | move_test.go:34: generated expected file /tmp/351631442/namespaces/jx/lighthouse/foghorn-deployment.yaml
  | FAIL

maybe just need to modify that test to look in the new folder location?

New changes are detected. LGTM label has been removed.


Snap installation not working

Hello. I installed moonlight via snap. However, I have this error when starting:
$ moonlight
+ case "$SNAP_ARCH" in
+ ARCH=x86_64-linux-gnu
++ glxinfo
++ grep 'OpenGL vendor'
Error: unable to open display :0.0
+ VENDOR=
+ export VDPAU_DRIVER_PATH=/snap/moonlight/96/usr/lib/x86_64-linux-gnu/vdpau
+ VDPAU_DRIVER_PATH=/snap/moonlight/96/usr/lib/x86_64-linux-gnu/vdpau
+ export LIBVA_DRIVERS_PATH=/snap/moonlight/96/usr/lib/x86_64-linux-gnu/dri
+ LIBVA_DRIVERS_PATH=/snap/moonlight/96/usr/lib/x86_64-linux-gnu/dri
+ [[ '' == *\N\V\I\D\I\A* ]]
+ [[ '' == *\X\.\O\r\g* ]]
+ exec /snap/moonlight/96/usr/bin/moonlight
00:00:00 - Qt Warning: QXcbConnection: Could not connect to display :0.0
00:00:00 - Qt Critical: Could not connect to any X display.

My system is Xubuntu 18.04 64-bit. I have integrated GPU: Intel HD 500.

Thanks for the report. I'm unable to reproduce. Are you running X, or Wayland? Anything unusual about your setup? Do other graphical snaps work in your env? E.g. most snaps featured at https://snapcraft.io/store are high-profile GUI apps.
Please help me debug by providing the following info about your environment:
snap info moonlight
snap version
echo $XDG_SESSION_TYPE
echo $DISPLAY
glxgears  # just double checking

And let's run a few commands inside the snap container as well:
snap run --shell moonlight
(snap)$ source $SNAP/snap/command-chain/snapcraft-runner  # setup snap env, PATH, etc
(snap)$ echo $XDG_SESSION_TYPE  # value should be same as above
(snap)$ echo $DISPLAY  # value should be same as above
(snap)$ glxgears  # this should work

The first log:
nuno@nuno-pc:~$ snap info moonlight
name:      moonlight
summary:   Play games remotely from your NVIDIA GameStream-enabled PC
publisher: Maximiliano Bertacchini (maxiberta)
contact:   https://github.com/maxiberta/moonlight-snap/issues
license:   GPL-3.0+
description: |
  Moonlight can stream games and other applications from a PC with an NVIDIA GeForce GTX 600-series
  or higher GPU and GeForce Experience installed.

  Features include:
  - Streaming at up to 4K resolution
  - Support for up to 120 FPS streaming (high refresh rate monitor recommended)
  - Hardware accelerated video decoding with VAAPI and VDPAU support
  - 5.1 surround sound audio support
  - HEVC support for better video compression efficiency
  - Gamepad support with SDL mapping compatibility

  [Main website](https://moonlight-stream.org/)
commands:
  - moonlight
snap-id:      I0j9pDLWv9Sr1reqhjuLJyr8WVhGkAb9
tracking:     stable
refresh-date: today at 20:15 WET
channels:
  stable:    0.9.1            2019-02-19 (96) 74MB -
  candidate: 0.9.1            2019-02-19 (96) 74MB -
  beta:      ↑
  edge:      0.9.1-2-ge32bc1a 2019-02-21 (98) 74MB -
installed:   0.9.1                       (96) 74MB -
nuno@nuno-pc:~$ snap version
snap    <IP_ADDRESS>+18.04
snapd   <IP_ADDRESS>+18.04
series  16
ubuntu  18.04
kernel  4.15.0-45-generic
nuno@nuno-pc:~$ echo $XDG_SESSION_TYPE
x11
nuno@nuno-pc:~$ echo $DISPLAY
:0.0
nuno@nuno-pc:~$ glxgears  # just double checking
307 frames in 5.0 seconds = 61.300 FPS
301 frames in 5.0 seconds = 60.003 FPS
301 frames in 5.0 seconds = 60.003 FPS
301 frames in 5.0 seconds = 60.000 FPS
^C

And the second log:
snap run --shell moonlight
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

nuno@nuno-pc:/home/nuno$ source $SNAP/snap/command-chain/snapcraft-runner  # setup snap env, PATH, etc
nuno@nuno-pc:/home/nuno$ echo $XDG_SESSION_TYPE  # value should be same as above
x11
nuno@nuno-pc:/home/nuno$ echo $DISPLAY  # value should be same as above
:0.0
nuno@nuno-pc:/home/nuno$ glxgears  # this should work
Error: couldn't open display :0.0
nuno@nuno-pc:/home/nuno$

Thanks. Are you able to run any other snap with a GUI?

Same issue here. Using Lubuntu 18.10 with Intel HD Graphics 620 (rev 02).
I checked Foobillard-plus Snap - works like a charme.
If you need more details, let me know.

Hm, are all interfaces connected?
$ snap interfaces moonlight
Slot                     Plug
:desktop                 moonlight
:desktop-legacy          moonlight
:home                    moonlight
:joystick                moonlight
:network                 moonlight
:network-manager         moonlight
:opengl                  moonlight
:pulseaudio              moonlight
:screen-inhibit-control  moonlight
:unity7                  moonlight
:wayland                 moonlight
:x11                     moonlight

I'm able to reproduce the issue if x11 and unity7 are disconnected... which is unexpected as these interfaces should be auto-connected on install.
Let's look for any relevant apparmor confinement logs. Please, run the following command in a different terminal, and then run moonlight as usual:
$ sudo journalctl --output=short --follow --all | sudo snappy-debug.security scanlog moonlight

Finally, please try the snap in devmode to rule out any confinement issues:
$ sudo snap remove moonlight
$ sudo snap install moonlight --devmode
$ moonlight

Thanks!

Hey,
thanks for fast reply.
Well ... it's weird:

I switched to Linux Mint 19.10. (due to some other issues with Lubuntu 18.10 itself)
after first try with moonlight: same error (even after reboot)
I installed some stuff like google chrome and Kodi as a media center
... then I wanted to begin your suggested commands - and huh? moonlight is running now.

So, for me this issue is solved ;)
Thank you anyway!

Thanks. Are you able to run any other snap with a GUI?

Hello. Sorry for late reply. Yes, i tested VLC snap and it worked.

@excelsi0r can you check the x11 and unity7 interfaces are connected, and look for any relevant confinement errors, as described in my comment above, please? Thanks!

Linux Mint 19.1, Nvidia.
pawel@DeskLinux-P:~$ snap interfaces moonlight
Slot  Plug
-     moonlight:desktop
-     moonlight:desktop-legacy
-     moonlight:home
-     moonlight:joystick
-     moonlight:network
-     moonlight:opengl
-     moonlight:pulseaudio
-     moonlight:screen-inhibit-control
-     moonlight:unity7
-     moonlight:wayland
-     moonlight:x11

pawel@DeskLinux-P:~$ moonlight
2019/03/15 08:00:37.550690 system_key.go:132: cannot determine nfs usage in generateSystemKey: cannot parse /etc/fstab: expected between 3 and 6 fields, found 7
+ case "$SNAP_ARCH" in
+ ARCH=x86_64-linux-gnu
++ glxinfo
++ grep 'OpenGL vendor'
Error: unable to open display :0
+ VENDOR=
+ export VDPAU_DRIVER_PATH=/snap/moonlight/96/usr/lib/x86_64-linux-gnu/vdpau
+ VDPAU_DRIVER_PATH=/snap/moonlight/96/usr/lib/x86_64-linux-gnu/vdpau
+ export LIBVA_DRIVERS_PATH=/snap/moonlight/96/usr/lib/x86_64-linux-gnu/dri
+ LIBVA_DRIVERS_PATH=/snap/moonlight/96/usr/lib/x86_64-linux-gnu/dri
+ [[ '' == *\N\V\I\D\I\A* ]]
+ [[ '' == *\X\.\O\r\g* ]]
+ exec /snap/moonlight/96/usr/bin/moonlight
00:00:00 - Qt Warning: QXcbConnection: Could not connect to display :0
00:00:00 - Qt Critical: Could not connect to any X display.

@pajew I'd appreciate if you check for relevant confinement errors, as described in my comment above, please? Thanks!

After installing:
sudo snap install snappy-debug
and running:
sudo journalctl --output=short --follow --all | sudo snappy-debug.security scanlog moonlight
I lunched Moonlight from start menu and it worked :)
I stopped debugging  and lunched Moonlight again and it worked.
After:
pawel@DeskLinux-P:~$ sudo snap remove snappy-debug
snappy-debug removed

I lunched Moonlight and it works. Strange. I tried to lunch Moonlight just before snappy-debug installation without success.

The problem origins from snap permissions.
When you install sudo snap install snappy-debug it results in reconfiguration of access permissions for snaps. And after that everything works.

@ajvengo care to elaborate, please? How would the installation of a snap affect the permissions of a different snap? Thanks!

I will try to find out how. Currently don't know. Not a pro in snap. Need to read documentation.

I believe this snapd bug is the culprit. Basically, if you only install core18-based snaps, such as moonlight, the core snap is not installed and some basic interfaces are unavailable, including x11.
For the time being, please install the core snap manually.

snapd 2.39.2 is available in bionic-updates now, so this can be closed now.

Indeed, the snap's interfaces are now auto-connected on install. Tested on a clean ubuntu 18.04. Thanks for the update!


Remove hashsum_download plugin

Remove the girder hashsum_download plugin in order to provide a performance baseline as we start to upload files.
This is a "migration" style PR that should be followed up with a removal of the state:absent section.

but it will be brought back later on, right? (I have hopes to later integrate with datalad, and being able to request by the sha512 would make implementation much leaner/easier)


COCOMO Project Anaylsis

Review calculated COCOMO models for hosted projects; get TAC feedback

Deck presented:
COCOMO Analysis of ASWF Projects.pdf

Additional information on the SLOCCount and how it applies the Basic COCOMO method.
https://dwheeler.com/sloccount/sloccount.html#cocomo
Note we could make adjustments on some of the parameters to get a truer estimate; see the options at https://dwheeler.com/sloccount/sloccount.html#options


Use Django model field API to process value model property

Apparently tests did not pass for entity attributes.

Closing due to lack of activity - please feel free to reopen if you are able to finish work on this proposed change.


[KeyboardDatePicker] TypeInfo requires onChange, onBlur & onFocus to be defined.

Environment

Tech
Version

@material-ui/pickers
v3.2.2

@material-ui/core
v4.9.5

TypeScript
v3.8.2

React
v16.12.0

Steps to reproduce
Use KeyboardDatePicker without defining onChange, onBlur or onFocus:
import { KeyboardDatePicker } from '@material-ui/pickers';
import React, { FunctionComponent } from 'react';

type Props = { name: string; value: Date; };

const Element: FunctionComponent<Props> = ({ name, value }) => (
  <KeyboardDatePicker name={name} value={value} />
);

Expected behavior
No error messages (onChange, onBlur and onFocus should be optional).
Actual behavior
Error Message when only onChange missing:
Property 'onChange' is missing in type '{ name: string; value: Date; }' but required in type 'BaseKeyboardPickerProps'.

Error Message when only onBlur missing:
Property 'onBlur' is missing in type '{ name: string; value: Date; onChange: (date: MaterialUiPickersDate) => void; onFocus: () => void; }' but required in type 'Pick<KeyboardDateInputProps, "ref" | "label" | "select" | "style" | "title" | "mask" | "className" | "innerRef" | "key" | "defaultChecked" | "defaultValue" | ... 273 more ... | "rifmFormatter">'.

Error Message when only onFocus missing:
Property 'onFocus' is missing in type '{ name: string; value: Date; onChange: (date: MaterialUiPickersDate) => void; onBlur: () => void; }' but required in type 'Pick<KeyboardDateInputProps, "ref" | "label" | "select" | "style" | "title" | "mask" | "className" | "innerRef" | "key" | "defaultChecked" | "defaultValue" | ... 273 more ... | "rifmFormatter">'.

Live example
https://codesandbox.io/s/elated-platform-swzeq

onChange is required and must be required – there is no sense in datepicker if you are not handling its value.
But onBlur and onFocus are not required - https://codesandbox.io/s/peaceful-sun-df3ux
Closing as invalid

@dmtrKovalenko I believe that:

there is a use case for server-side form submission
none of the core components force the onChange prop, it would be more consistent
react-hook-form might be used without an onChange handler, only looking at the value of the DOM input.
if the input the is disabled or readonly, providing a onChange doesn't make sense.

So, I think that removing such a requirement would help

@oliviertassinari I cannot agree with that,

react-hook-form doing completely wrong if they are attaching handlers right to the dom, because updating dom is side-effect for us when user is picker value from calendar.
I don't like such tricky behaviors like when there is a value and there is no onChange  or inverted. When there is no onChange – always question appears how it is changing value. It is much easier to provide a do nothing function onChange={() => { }}
It is more "proper" and "strict" way from the type system perspective

@dmtrKovalenko What's your take on 1.?

Make <DatePicker disabled onChange={() => {}}
It is clear enough that there is no action appears on changing value, yes its more words inside, but it is clear and expressively

Typescript must help developers to not make a mistake. If there is no onChange provided it is in 98% a mistake so we need to make it clear

@dmtrKovalenko From my perspective, it's nor ours call to make, it would be best to stick to the typing React uses for its input. onChange isn't required? Fine, so shouldn't it be for @material-ui/core nor @material-ui/lab, etc.

@oliviertassinari f9r text-field maybe. For Datepicker - definitely no

Sorry for my bad with onBlur and onFocus. This issue I was having with them seems to already be fixed in v3.2.10, I was using v3.2.2 (can't believe I forgot to check whether or not I was using the latest version).

Typescript must help developers to not make a mistake.

@dmtrKovalenko I do fully agree with this.
TypeScript should just provide type information to developers; this in turn then helps developers to not make mistakes.
If the KeyboardDatePicker works fine without the onChange prop being defined (i.e. the underlying code can handle the case of onChange === undefined), then TypeScript should not enforce it to be defined.

TypeScript should just provide type information to developers; this in turn then helps developers to not make mistakes.

In our case, the prop types and TypeScript types should match, right?

Yes and proptype for onChange in picker should be required

@dmtrKovalenko In my opinion, it should be a linter that enforces onChange be set; not TypeScript itself.


support for xhr uploads.

Extracted the ProgressEventTarget interface into a superclass since both
XMLHttpRequest and XMLHttpRequestUpload objects emit the same series of
events (loadstart, progress, load, abort, loadend)

Can you talk about this particular approach. It's not jumping out to me as obvious.

We're testing an application uploads to the server using an XHR, but FakeXMLHttpRequest does not currently have an upload property.
http://www.w3.org/TR/XMLHttpRequest/#interface-xmlhttprequest
The upload property is an instance of XMLHttpRequestUpload which extends the XMLHttpRequestEventTarget interface and tracks the transfer of bytes to the server in much the same way as the primary XMLHttpRequest track bytes coming from the server. In fact, both interfaces extend XMLHttpRequestEventTarget, and so this pull request extracts the implementation of this interface into the perhaps poorly named ProgressEventTarget and makes both the upload object and the request object inherit from it.
This way, you can test both your uploads and downloads.

Ah, makes more sense now. I thought ProgressEventTarget was a mock of ProgressEvent itself, but no?

This seems fine. Let me know when you feel this is ready for merge.

Ok thanks! I'll integrate your suggestions, and let you know. cheers!

I'm using ember-cli-mirage and ember-uploader that internally uses pretender and I found a dead end trying to upload files.
I faced this very same problem today. I patched pretender with a single line:
function interceptor(pretender) {
  function FakeRequest(){
    // super()
    FakeXMLHttpRequest.call(this);
  }
  // extend
  var proto = new FakeXMLHttpRequest();
+ proto.upload = {};
  proto.send = function send(){

But my patch was just a hack. Is this PR still alive? I can work on this if necessary. It's blocking me hard.

Just for the record, this due to the ES6-fycation of the codebase this branch is not trivial to merge/rebase. I tried.

@cibernox this is the effect of very long running branches. I'm closing since this has sat mostly idle for a while. Maybe someone will try in the future.

I'll try myself to implement this then.


First run failed (webpack-hot-client ?)

Bug Report
When I try to run docz for the first time (the only thing I did was yarn add -D docz), it compiles but then throw this error:

Then, after I think "this is not zero-config", I install the webpack-hot-client and try to run docz again typing yarn docz dev in my terminal and it throws me this:

My index.mdx file looks like this:
---
name: Deudas
---

import { Playground } from 'docz'
import { StatusLabel, STATUSES } from './debtsList'

# StatusLabel

<Playground>
  {STATUSES.map(({ id, label, tagType }) => (
    <StatusLabel key={id} label={label} tagType={tagType} />
  ))}
</Playground>

I don't know if I'm missing something and this is my fault but it happens in my both laptops
To Reproduce

run yarn add -D docz in the terminal in the project folder
create an index.mdx file with the code pasted above
run yarn docz dev
See error

Enviroment

OS: [e.g. OSX 10.13.45]
Node/npm version: [e.g. Node 8.9.4/npm 5.6.0]

Additional context/Screenshots
my package.json :
{
  "name": "rtd-frontend",
  "private": true,
  "description": "Servir de frontend para interactuar con __RTD API__ para los ARD y Negociadores.",
  "standard": {
    "parser": "babel-eslint"
  },
  "husky": {
    "hooks": {
      "pre-commit": "lint-staged"
    }
  },
  "lint-staged": {
    "linters": {
      "*.{js, scss}": [
        "prettier-standard",
        "git add"
      ]
    }
  },
  "dependencies": {
    "accounting": "^0.4.1",
    "axios": "^0.18.0",
    "bulma": "^0.6.2",
    "bulma-accordion": "^1.0.1",
    "bulma-pageloader": "^1.0.1",
    "bulma-steps": "^1.0.2",
    "bulma-timeline": "^2.0.1",
    "chai": "^4.1.2",
    "classnames": "^2.2.5",
    "enzyme": "^3.0.0",
    "enzyme-adapter-react-15": "^1.0.0",
    "events": "^1.1.1",
    "jsdom": "^11.2.0",
    "jsoneditor": "^5.9.6",
    "lodash": "^4.17.10",
    "mobx": "^4.1.0",
    "mobx-react": "^5.0.0",
    "mocha": "^3.5.3",
    "moment": "^2.17.1",
    "prop-types": "^15.6.1",
    "query-string": "^4.3.2",
    "react": "^15.3.2",
    "react-addons-test-utils": "^15.6.2",
    "react-addons-update": "^15.4.2",
    "react-alert": "^2.4.0",
    "react-async-loader": "^0.1.2",
    "react-datepicker": "^0.52.0",
    "react-document-title": "^2.0.2",
    "react-dom": "^15.3.2",
    "react-google-login": "^2.9.3",
    "react-image-zoom": "^0.7.0",
    "react-router": "^3.0.2",
    "react-select": "^1.0.0-rc.5",
    "react-toastify": "^3.4.2",
    "react-tooltip": "^3.3.0",
    "recharts": "^0.21.2",
    "sinon": "^4.0.0",
    "stackdriver-errors-js": "^0.4.0",
    "store": "2.0.3",
    "validator": "^7.0.0",
    "validatorjs": "^3.14.2"
  },
  "scripts": {
    "deploy": "rm -rf build && mkdir build && npm run css && cp -R ./public/. ./build && npm run build",
    "build": "node_modules/cross-env/dist/bin/cross-env.js NODE_ENV=production node_modules/webpack/bin/webpack.js -p",
    "deploy-sandbox": "rm -rf build && mkdir build && npm run css && cp -R ./public/. ./build && npm run build-sandbox",
    "build-sandbox": "node_modules/cross-env/dist/bin/cross-env.js NODE_ENV=sandbox node_modules/webpack/bin/webpack.js -p",
    "test": "NODE_ENV=test mocha --compilers js:babel-register --require ./test/helpers.js --require ./test/dom.js --recursive",
    "tdd": "npm test -- --watch",
    "css": "node_modules/node-sass/bin/node-sass public/css/src/main.scss public/css/main.css --output-style compressed"
  },
  "devDependencies": {
    "babel-cli": "^6.26.0",
    "babel-core": "^6.26.3",
    "babel-eslint": "^8.2.3",
    "babel-loader": "^7.1.4",
    "babel-plugin-transform-decorators-legacy": "^1.3.4",
    "babel-preset-env": "^1.7.0",
    "babel-preset-react": "^6.24.1",
    "babel-preset-stage-1": "^6.24.1",
    "copy-webpack-plugin": "^4.0.1",
    "cross-env": "^3.0.0",
    "css-loader": "^0.28.11",
    "docz": "^0.2.4",
    "ejs-loader": "^0.3.0",
    "extract-text-webpack-plugin": "^2.1.0",
    "file-loader": "^0.10.1",
    "html-webpack-plugin": "^3.2.0",
    "husky": "^1.0.0-rc.6",
    "jest": "^21.1.0",
    "lint-staged": "^7.1.2",
    "node-sass": "^4.9.0",
    "prettier-standard": "^8.0.1",
    "react-test-renderer": "^15.6.2",
    "sass-loader": "^7.0.3",
    "standard": "^11.0.1",
    "style-loader": "^0.21.0",
    "url-loader": "^0.5.7",
    "webpack": "^3.11",
    "webpack-dev-server": "^2.11.1"
  }
}

I've also had this issue #24, I now realize it might have something to do with Docz needing webpack 4?

For sure @danburzo, you need to use webpack 4 and babel 7 to get it running!

It would be nice to have this information on the docs


Setting string lists with cfg_setopt() does not work

Ran into this with Inadyn today. Tried to write a migrate-deprecated-setting function today for string lists, did not bite.  The code does not seem to support it?
https://github.com/martinh/libconfuse/blob/master/src/confuse.c#L646

Have a look at how cfg_opt_setmulti() calls cfg_setopt().
Cheers,
Peter

@peda-r Thanks!
This can be greatly improved ...

cfg_setopt() is just too low-level when it comes to lists and sections and can't really be used for those except if you also abuse libconfuse internals. It really is a plumbing function that just happens to do the right thing for the simpler option types.

Hmm, I'm beginning to realize as much ... what I wanted was something along the lines of:
 value = cfg_get_optval(cfg, "old-setting");
 cfg_set_optval(cfg, "new-setting", value);

Which would transparently handle all different types.  I'm looking at whipping something up.

The tough nut to crack is what the type of "value" should be. Since you didn't mention cfg_getopt() I take it that you did not mean that it should be cfg_opt_t *value?

Well anything better than this troglobit/inadyn@5a679d9 ... would be good if Confuse could wrap this for our users.  Basically I just want to "rename" an option, or move its values to a new option of the same type.
(This is the first time I get to practise this, but I've predicted many more such exercises for future projects at work, where we also use libConfuse.)


Use ctxhttp to execute HTTP calls to external CF service broker APIs

The cfV2BrokerClient has methods that make calls to CF service broker APIs. We should use ctxhttp to ensure that a call that hangs for any reason (no connection timeout, etc...) is cancelled. ctxhttp is a very convenient mechanism for doing these cancellations.

I second this.

/remove-lifecycle rotten
/lifecycle frozen

This project is being archived, closing open issues and PRs.
Please see this PR for more information: https://github.com/kubernetes/community/pull/6632
/close


Call for comments: fewer allocations, faster destroy, slower each

A lighting call for comments about a change I'm working on.
The idea is to get rid of the available vector in the registry and replace it with an identifier that acts as an entry point of an implicit freelist within the entities vector.
Put aside the details of the internal changes that are probably not so appealing, these are the benefits:

Fewer allocations for obvious reasons.
The destroy member function gets a x4 in terms of performance (results of a preliminary test), that is an incredibly boost!

The member functions involved by this change are:

create: apparently it's not affected at all in terms of performance.
destroy: gets a x4, it's worth it definitely.
Registry::each: I've not yet tested it, but it could be slightly affected. However this function is already pretty slow by design and its intended use is mainly for serialization, so I wouldn't bother much for that.

As a side note, each member functions of views aren't affected at all.
From my point of view, the change is worth it. Fewer allocations and a faster destroy are something I'd like to have.
Unless someone comes with a good reason not to do it, I'm finalizing the change and merging it during the week.
The API of EnTT won't be affected at all.

does it mean that the entities vector is not tightly packed? Not an issue at all, just want to understand.
Is it gonna be something similar to http://bitsquid.blogspot.com/2011/09/managing-decoupling-part-4-id-lookup.html ?
I implemented a similar lookup table for my frameworks and the performance and level of control on the memory was totally worth it.

Here it is (7baf608). Unless someone gives me a good reason not to merge it with master, I'll do it tomorrow.
Affected functions:

create (creating 10M entities: 0.0388s -> 0.0423s)
destroy (destroying 10M entities: 0.0828s -> 0.0221s)

Registry::each has been slightly affected, but I've not benchmarks for it. However, the performance hit is probably minimal and I prefer a faster destroy than a faster Registry::each.
All the other functions around have not been involved by this commit.

Looks like a nice bit of extra performance. Thanks :)

@reworks
I tried to figure out why in EnTT everything was much faster than with other well known ECS while the destroy was so slower.
Moreover I focused on the available vector because it looked to me like I was wasting memory for no benefits and I guessed how to get rid of it.   Fortunately both the answers where in the same place. :-)

So far, so good. I'm going to merge the PR with master because it seems a widely accepted tradeoff. Time to close the issue.
Thank you all for your feedback.

Just to mention it (I don't want to create an issue for that).
Another improvement is almost ready to merge. I'm working on it in my free time, so the schedule is hard to set.
It's a speed up on standard multi component views. For those that care about memory usage and do not create persistent views all around the codebase, it will give a boost from 20% up to 50% (how much mostly depends on the number of components of the view).
Not that bad, isn't it? :-)


MDC-101 Typo in name of Node.js

A recent version of NodeJS (which comes bundled with npm, a JavaScript package manager).

Emphasis mine. "NodeJS" should be spelled "Node.js" across many codelabs.

Thanks for pointing out the typo. I've fixed the prose and sent publish requests for all of the MDC Web codelabs to fix it.

Thanks for reporting this!


reset chat store on route change start

fix #1891

If you go to the home page, but don't go into another room, I don't want the chat to be cleared. Chat should only be cleared upon joining a room you weren't already in.


[Issue #665 fix] Fixed overflow of XO Editor on wide screens

Fixes #665. I have added a break-point for width at 750px in the resize event listener, up to which the resizing seems responsive.

Not an issue and not at all in the spirit of the activity.


apple-mobile-web-app-capable needs to be yes

On iOS 9 and 10, manup.js was injecting the value of the manifest file, eg. <meta name="apple-mobile-web-app-capable" content="fullscreen">
However it must be 'yes', ie. <meta name="apple-mobile-web-app-capable" content="yes"> for iOS to respect it and other settings.
I had to remove manup.js to get fullscreen working on iOS as it overrides existing tags. So a generalised fix might be for manup to check for existing tags before injection; although that's slow. Otherwise there needs to be a catch to translate the iOS values from manifest values to yes.

I think the latter will work (without much cost to perf).  I'm planning do some clean up here soon, I'll make sure I fix this.


How To Change My Name On DELTA Flight Ticket? {Auto~Correction#Name}

Description

Steps to reprHow to Change name on 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ?
𝒯𝑜 𝒸𝒽𝒶𝓃𝑔𝑒 𝓉𝒽𝑒 𝓃𝒶𝓂𝑒 𝑜𝓃 𝒶 𝓓𝓮𝓵𝓽𝓪  𝓉𝒾𝒸𝓀𝑒𝓉, 𝓋𝒾𝓈𝒾𝓉 𝓉𝒽𝑒 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 𝓌𝑒𝒷𝓈𝒾𝓉𝑒 𝑜𝓇 𝒸𝑜𝓃𝓉𝒶𝒸𝓉 𝒸𝓊𝓈𝓉𝑜𝓂𝑒𝓇 𝓈𝑒𝓇𝓋𝒾𝒸𝑒 𝓉𝒽𝓇𝑜𝓊𝑔𝒽 ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (𝒪𝒯𝒜) 𝒪𝑅 +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (𝒪𝒯𝒜) 🔰(𝒪𝒯𝒜) 𝑜𝓇 ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (𝒪𝒯𝒜). 𝐿𝑜𝑔 𝒾𝓃 𝓉𝑜 𝒻𝒾𝓃𝒹 𝓉𝒽𝑒 "𝒞𝒽𝒶𝓃𝑔𝑒 𝒩𝒶𝓂𝑒 𝒪𝓃 𝓓𝓮𝓵𝓽𝓪  𝒯𝒾𝒸𝓀𝑒𝓉" 𝑜𝓅𝓉𝒾𝑜𝓃 𝒶𝓃𝒹 𝒻𝑜𝓁𝓁𝑜𝓌 𝓉𝒽𝑒 𝓅𝓇𝑜𝓋𝒾𝒹𝑒𝒹 𝒾𝓃𝓈𝓉𝓇𝓊𝒸𝓉𝒾𝑜𝓃𝓈 𝒻𝑜𝓇 𝒶 𝓈𝓂𝑜𝑜𝓉𝒽 𝓉𝓇𝒶𝓃𝓈𝒶𝒸𝓉𝒾𝑜𝓃.
𝒞𝒶𝓃 𝓅𝒶𝓈𝓈𝑒𝓃𝑔𝑒𝓇 𝒸𝒽𝒶𝓃𝑔𝑒 𝓉𝒽𝑒𝒾𝓇 𝓃𝒶𝓂𝑒 𝑜𝓃 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮? 𝒴𝑒𝓈, 𝓎𝑜𝓊 𝒸𝒶𝓃 𝒸𝒽𝒶𝓃𝑔𝑒 𝓎𝑜𝓊𝓇 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 𝓉𝒾𝒸𝓀𝑒𝓉 𝓃𝒶𝓂𝑒 𝑜𝓃𝓁𝒾𝓃𝑒 𝑜𝓇 𝑜𝒻𝒻𝓁𝒾𝓃𝑒. 𝒰𝓈𝑒 𝓉𝒽𝑒𝒾𝓇 𝓌𝑒𝒷𝓈𝒾𝓉𝑒 𝑜𝓇 𝓂𝑜𝒷𝒾𝓁𝑒 𝒶𝓅𝓅, 𝑜𝓇 𝒸𝑜𝓃𝓉𝒶𝒸𝓉 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 𝒶𝓉 ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (𝒪𝒯𝒜) 𝒪𝑅 +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (𝒪𝒯𝒜) 🔰 𝑜𝓇 ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (𝒪𝒯𝒜) 𝒻𝑜𝓇 𝑔𝓊𝒾𝒹𝒶𝓃𝒸𝑒 𝑜𝓃 𝓇𝑒𝓆𝓊𝑒𝓈𝓉𝒾𝓃𝑔 𝒶 𝓃𝒶𝓂𝑒 𝒶𝒹𝒿𝓊𝓈𝓉𝓂𝑒𝓃𝓉.
To change or correction a name on an 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ticket, contact their customer service at ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA). They will guide you through the name correction process and applicable fees.
Here are the simple methods to change a name on an 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ticket:
Contact Customer Service: Call ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) for assistance. Visit the Website: Log in to your account on the 𝓓𝓮𝓵𝓽𝓪  +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 𝒜𝒾𝓇𝓁𝒾𝓃ℯ𝓈 website, go to "Manage Reservations," and request a name correction. Airport Ticket Counter: Visit an 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ticket counter at the airport for +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 in-person assistance. Travel Agent: If booked through a travel agent, contact them to make the necessary changes.
How To Change Name With 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮?
When you need to change the Name on your 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ticket, simply visit their website or contact their customer service ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA). Enter your booking information in the "My Trips" section and select the flight you want to modify. Choose the option to change the flight Name, follow the instructions to complete the process, and pay any applicable fees. After making the changes, expect to receive a confirmation email from 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮.
How Do I Change Name On 𝓓𝓮𝓵𝓽𝓪  Ticket Using Online Mode?
Go to the 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 website to begin the process of changing the Name on your online ticket. Go to "Manage Travel" or "My Trips" +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 and enter your booking details to log in. Find your itinerary and click on the Name of flight change option. To select a new Name and complete the adjustments,+𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 adhere to the instructions. If you find any issue while making the changes, feel free to communicate with its customer support team at ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA)
How To Change Flight Name On 𝓓𝓮𝓵𝓽𝓪  Air Ticket?
𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 renders your various approaches to amend the Name on your flight ticket. Majorly you can either initiate the process by heading to the official 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 website or connect with its customer support team ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA). Moreover, navigate to the “Manage My Booking” section. Enter your booking information and select the flight you want to change. Follow the instructions to choose a new Name and pay any required fees. Once confirmed, you'll receive an email from 𝓓𝓮𝓵𝓽𝓪  confirming your upNamed travel details.
How To Change Name On Plane Ticket 𝓓𝓮𝓵𝓽𝓪 ?
To change flight Name on plane ticket 𝓓𝓮𝓵𝓽𝓪 , you need to log in to their official website or get in touch with their customer support staff by dialing ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA). Locate your booking under "My Trips," input your reservation details and confirmation code. Select the flight you need to change and select the option to adjust the Name. If you are confused, then you can communicate with the staff and get your doubts and issues resolved in no time.
How To Change Your Name On A 𝓓𝓮𝓵𝓽𝓪  Ticket?
There are a few different ways to change the Name on a 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ticket. You can change your flight Name through 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮' official website. Log into your account, navigate to the "My Trips" section, enter your booking details and confirmation code. Alternatively, Contact 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮' customer service directly via phone ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA). Provide your booking information and request to change your flight Name through a customer service representative.
Can A Passenger Change Name On 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮?
Yes, passengers can change the Name of their 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight. They can do so by visiting the 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 website or contacting customer service ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) directly. Navigate to the "My Trips" section, input your booking details and reference code, and select the flight you wish to change. Choose the option to modify your flight Name, complete any required fee payment, +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 and await confirmation from 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 via email.
Can You Change The Name On A 𝓓𝓮𝓵𝓽𝓪  Airline?
Yes, changing the Name of your 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight is possible. Access their official website or call ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA), their customer service directly. Locate your booking under "Manage My Trip," input your reservation information, and choose the flight Name +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 change option. Ensure you settle any relevant Name adjustment charges and await confirmation from 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 upon completing the process.
How to Change Passenger Name on 𝓓𝓮𝓵𝓽𝓪  Ticket
How do I change my Name on the 𝓓𝓮𝓵𝓽𝓪  ticket?
Name Correction on 𝓓𝓮𝓵𝓽𝓪  flight Ticket
Change Name on 𝓓𝓮𝓵𝓽𝓪
Name Correction on 𝓓𝓮𝓵𝓽𝓪  Ticket
how do I change my Name on 𝓓𝓮𝓵𝓽𝓪  ?
Can I Change the Name on the 𝓓𝓮𝓵𝓽𝓪  flight Ticket
How to Change Name on 𝓓𝓮𝓵𝓽𝓪
How do I change my Name on the 𝓓𝓮𝓵𝓽𝓪  NameReservation?

Name Correction on 𝓓𝓮𝓵𝓽𝓪  Reservation
How can I change my Name on a 𝓓𝓮𝓵𝓽𝓪  ticket?
Can I change my Name on a 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight ticket?
How to Change Name on 𝓓𝓮𝓵𝓽𝓪  Ticket
Can I change the Name on my 𝓓𝓮𝓵𝓽𝓪  ticket?
change passenger Name on 𝓓𝓮𝓵𝓽𝓪  ticket
How do I change the Name on my 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight boarding pass?
How do I change a passenger's Name on a 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight flight?
How do I change the Name on my 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight ticket?
Can I change the Name on my 𝓓𝓮𝓵𝓽𝓪  s reservation?

Name Correction on 𝓓𝓮𝓵𝓽𝓪  flight Ticket
How can I change my Name on a 𝓓𝓮𝓵𝓽𝓪  ticket?
Name Correction on 𝓓𝓮𝓵𝓽𝓪  Boarding Pass
Can I change my Name on a 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight ticket?
Name Correction on 𝓓𝓮𝓵𝓽𝓪  flight Reservation
Name Correction on 𝓓𝓮𝓵𝓽𝓪  Ticket
Change Name on 𝓓𝓮𝓵𝓽𝓪  ticket
How to change the Name on 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ticket
How to Change Passenger Name on 𝓓𝓮𝓵𝓽𝓪  Ticket
Can I change the Name on my 𝓓𝓮𝓵𝓽𝓪  ticket?
How do I change the Name on my 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight boarding pass?
How do I change a passenger's Name on a 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight flight?
How do I change the Name on my 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight ticket?
How do I change my Name on a 𝓓𝓮𝓵𝓽𝓪  ticket?

Change Name on 𝓓𝓮𝓵𝓽𝓪  flight Ticket
replace passenger Name on 𝓓𝓮𝓵𝓽𝓪  flight ticket
How Can I Modify a Passenger's Name on a 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 Ticket?
The "Manage My Booking" area can be accessed by first visiting the official 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 website. Entering their reservation data, choosing the flight they want to change, and changing the Name as necessary may all be done from here. As an alternative, customers can call 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 customer service directly ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) and ask for a Name modification. With 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮, both options guarantee convenience and adaptability when modifying travel arrangements.
How Can My 𝓓𝓮𝓵𝓽𝓪  Airline Flight Be change name ?
Is the Name of your 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight being upNamed? Go to their website or contact customer service ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA). Navigate to "Manage Travel," fill out the details of your reservation, and choose the flight that requires modification. Just follow the directions and pay the applicable fees to reschedule. A confirmation email from 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 with your upNamed trip details should arrive soon.
Can I Change My 𝓓𝓮𝓵𝓽𝓪  Name Reservation Name?
Reach out to customer service or visit the ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ ++𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) website. After login in, select "My Trips" and input the booking information and confirmation code. Find the button to edit your reservation after selecting your flight. Choose a new Name and pay any necessary fees by following the instructions. To finish the procedure, make sure you get an email or notice on their website confirming the adjustments you made.oduce

Expected behavior

Actual behavior

Diagnostic logs

Environment

How to Change name on 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ?
𝒯𝑜 𝒸𝒽𝒶𝓃𝑔𝑒 𝓉𝒽𝑒 𝓃𝒶𝓂𝑒 𝑜𝓃 𝒶 𝓓𝓮𝓵𝓽𝓪  𝓉𝒾𝒸𝓀𝑒𝓉, 𝓋𝒾𝓈𝒾𝓉 𝓉𝒽𝑒 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 𝓌𝑒𝒷𝓈𝒾𝓉𝑒 𝑜𝓇 𝒸𝑜𝓃𝓉𝒶𝒸𝓉 𝒸𝓊𝓈𝓉𝑜𝓂𝑒𝓇 𝓈𝑒𝓇𝓋𝒾𝒸𝑒 𝓉𝒽𝓇𝑜𝓊𝑔𝒽 ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (𝒪𝒯𝒜) 𝒪𝑅 +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (𝒪𝒯𝒜) 🔰(𝒪𝒯𝒜) 𝑜𝓇 ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (𝒪𝒯𝒜). 𝐿𝑜𝑔 𝒾𝓃 𝓉𝑜 𝒻𝒾𝓃𝒹 𝓉𝒽𝑒 "𝒞𝒽𝒶𝓃𝑔𝑒 𝒩𝒶𝓂𝑒 𝒪𝓃 𝓓𝓮𝓵𝓽𝓪  𝒯𝒾𝒸𝓀𝑒𝓉" 𝑜𝓅𝓉𝒾𝑜𝓃 𝒶𝓃𝒹 𝒻𝑜𝓁𝓁𝑜𝓌 𝓉𝒽𝑒 𝓅𝓇𝑜𝓋𝒾𝒹𝑒𝒹 𝒾𝓃𝓈𝓉𝓇𝓊𝒸𝓉𝒾𝑜𝓃𝓈 𝒻𝑜𝓇 𝒶 𝓈𝓂𝑜𝑜𝓉𝒽 𝓉𝓇𝒶𝓃𝓈𝒶𝒸𝓉𝒾𝑜𝓃.
𝒞𝒶𝓃 𝓅𝒶𝓈𝓈𝑒𝓃𝑔𝑒𝓇 𝒸𝒽𝒶𝓃𝑔𝑒 𝓉𝒽𝑒𝒾𝓇 𝓃𝒶𝓂𝑒 𝑜𝓃 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮? 𝒴𝑒𝓈, 𝓎𝑜𝓊 𝒸𝒶𝓃 𝒸𝒽𝒶𝓃𝑔𝑒 𝓎𝑜𝓊𝓇 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 𝓉𝒾𝒸𝓀𝑒𝓉 𝓃𝒶𝓂𝑒 𝑜𝓃𝓁𝒾𝓃𝑒 𝑜𝓇 𝑜𝒻𝒻𝓁𝒾𝓃𝑒. 𝒰𝓈𝑒 𝓉𝒽𝑒𝒾𝓇 𝓌𝑒𝒷𝓈𝒾𝓉𝑒 𝑜𝓇 𝓂𝑜𝒷𝒾𝓁𝑒 𝒶𝓅𝓅, 𝑜𝓇 𝒸𝑜𝓃𝓉𝒶𝒸𝓉 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 𝒶𝓉 ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (𝒪𝒯𝒜) 𝒪𝑅 +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (𝒪𝒯𝒜) 🔰 𝑜𝓇 ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (𝒪𝒯𝒜) 𝒻𝑜𝓇 𝑔𝓊𝒾𝒹𝒶𝓃𝒸𝑒 𝑜𝓃 𝓇𝑒𝓆𝓊𝑒𝓈𝓉𝒾𝓃𝑔 𝒶 𝓃𝒶𝓂𝑒 𝒶𝒹𝒿𝓊𝓈𝓉𝓂𝑒𝓃𝓉.
To change or correction a name on an 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ticket, contact their customer service at ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA). They will guide you through the name correction process and applicable fees.
Here are the simple methods to change a name on an 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ticket:
Contact Customer Service: Call ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) for assistance. Visit the Website: Log in to your account on the 𝓓𝓮𝓵𝓽𝓪  +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 𝒜𝒾𝓇𝓁𝒾𝓃ℯ𝓈 website, go to "Manage Reservations," and request a name correction. Airport Ticket Counter: Visit an 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ticket counter at the airport for +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 in-person assistance. Travel Agent: If booked through a travel agent, contact them to make the necessary changes.
How To Change Name With 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮?
When you need to change the Name on your 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ticket, simply visit their website or contact their customer service ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA). Enter your booking information in the "My Trips" section and select the flight you want to modify. Choose the option to change the flight Name, follow the instructions to complete the process, and pay any applicable fees. After making the changes, expect to receive a confirmation email from 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮.
How Do I Change Name On 𝓓𝓮𝓵𝓽𝓪  Ticket Using Online Mode?
Go to the 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 website to begin the process of changing the Name on your online ticket. Go to "Manage Travel" or "My Trips" +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 and enter your booking details to log in. Find your itinerary and click on the Name of flight change option. To select a new Name and complete the adjustments,+𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 adhere to the instructions. If you find any issue while making the changes, feel free to communicate with its customer support team at ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA)
How To Change Flight Name On 𝓓𝓮𝓵𝓽𝓪  Air Ticket?
𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 renders your various approaches to amend the Name on your flight ticket. Majorly you can either initiate the process by heading to the official 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 website or connect with its customer support team ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA). Moreover, navigate to the “Manage My Booking” section. Enter your booking information and select the flight you want to change. Follow the instructions to choose a new Name and pay any required fees. Once confirmed, you'll receive an email from 𝓓𝓮𝓵𝓽𝓪  confirming your upNamed travel details.
How To Change Name On Plane Ticket 𝓓𝓮𝓵𝓽𝓪 ?
To change flight Name on plane ticket 𝓓𝓮𝓵𝓽𝓪 , you need to log in to their official website or get in touch with their customer support staff by dialing ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA). Locate your booking under "My Trips," input your reservation details and confirmation code. Select the flight you need to change and select the option to adjust the Name. If you are confused, then you can communicate with the staff and get your doubts and issues resolved in no time.
How To Change Your Name On A 𝓓𝓮𝓵𝓽𝓪  Ticket?
There are a few different ways to change the Name on a 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ticket. You can change your flight Name through 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮' official website. Log into your account, navigate to the "My Trips" section, enter your booking details and confirmation code. Alternatively, Contact 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮' customer service directly via phone ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA). Provide your booking information and request to change your flight Name through a customer service representative.
Can A Passenger Change Name On 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮?
Yes, passengers can change the Name of their 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight. They can do so by visiting the 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 website or contacting customer service ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) directly. Navigate to the "My Trips" section, input your booking details and reference code, and select the flight you wish to change. Choose the option to modify your flight Name, complete any required fee payment, +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 and await confirmation from 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 via email.
Can You Change The Name On A 𝓓𝓮𝓵𝓽𝓪  Airline?
Yes, changing the Name of your 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight is possible. Access their official website or call ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA), their customer service directly. Locate your booking under "Manage My Trip," input your reservation information, and choose the flight Name +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 change option. Ensure you settle any relevant Name adjustment charges and await confirmation from 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 upon completing the process.
How to Change Passenger Name on 𝓓𝓮𝓵𝓽𝓪  Ticket
How do I change my Name on the 𝓓𝓮𝓵𝓽𝓪  ticket?
Name Correction on 𝓓𝓮𝓵𝓽𝓪  flight Ticket
Change Name on 𝓓𝓮𝓵𝓽𝓪
Name Correction on 𝓓𝓮𝓵𝓽𝓪  Ticket
how do I change my Name on 𝓓𝓮𝓵𝓽𝓪  ?
Can I Change the Name on the 𝓓𝓮𝓵𝓽𝓪  flight Ticket
How to Change Name on 𝓓𝓮𝓵𝓽𝓪
How do I change my Name on the 𝓓𝓮𝓵𝓽𝓪  NameReservation?

Name Correction on 𝓓𝓮𝓵𝓽𝓪  Reservation
How can I change my Name on a 𝓓𝓮𝓵𝓽𝓪  ticket?
Can I change my Name on a 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight ticket?
How to Change Name on 𝓓𝓮𝓵𝓽𝓪  Ticket
Can I change the Name on my 𝓓𝓮𝓵𝓽𝓪  ticket?
change passenger Name on 𝓓𝓮𝓵𝓽𝓪  ticket
How do I change the Name on my 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight boarding pass?
How do I change a passenger's Name on a 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight flight?
How do I change the Name on my 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight ticket?
Can I change the Name on my 𝓓𝓮𝓵𝓽𝓪  s reservation?

Name Correction on 𝓓𝓮𝓵𝓽𝓪  flight Ticket
How can I change my Name on a 𝓓𝓮𝓵𝓽𝓪  ticket?
Name Correction on 𝓓𝓮𝓵𝓽𝓪  Boarding Pass
Can I change my Name on a 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight ticket?
Name Correction on 𝓓𝓮𝓵𝓽𝓪  flight Reservation
Name Correction on 𝓓𝓮𝓵𝓽𝓪  Ticket
Change Name on 𝓓𝓮𝓵𝓽𝓪  ticket
How to change the Name on 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 ticket
How to Change Passenger Name on 𝓓𝓮𝓵𝓽𝓪  Ticket
Can I change the Name on my 𝓓𝓮𝓵𝓽𝓪  ticket?
How do I change the Name on my 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight boarding pass?
How do I change a passenger's Name on a 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight flight?
How do I change the Name on my 𝓓𝓮𝓵𝓽𝓪  𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight ticket?
How do I change my Name on a 𝓓𝓮𝓵𝓽𝓪  ticket?

Change Name on 𝓓𝓮𝓵𝓽𝓪  flight Ticket
replace passenger Name on 𝓓𝓮𝓵𝓽𝓪  flight ticket
How Can I Modify a Passenger's Name on a 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 Ticket?
The "Manage My Booking" area can be accessed by first visiting the official 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 website. Entering their reservation data, choosing the flight they want to change, and changing the Name as necessary may all be done from here. As an alternative, customers can call 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 customer service directly ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) and ask for a Name modification. With 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮, both options guarantee convenience and adaptability when modifying travel arrangements.
How Can My 𝓓𝓮𝓵𝓽𝓪  Airline Flight Be change name ?
Is the Name of your 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 flight being upNamed? Go to their website or contact customer service ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA). Navigate to "Manage Travel," fill out the details of your reservation, and choose the flight that requires modification. Just follow the directions and pay the applicable fees to reschedule. A confirmation email from 𝓓𝓮𝓵𝓽𝓪 𝓐𝓲𝓻𝓵𝓲𝓷𝓮 with your upNamed trip details should arrive soon.
Can I Change My 𝓓𝓮𝓵𝓽𝓪  Name Reservation Name?
Reach out to customer service or visit the ☎ +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) or ☎ ++𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) OR +𝟭-𝟴𝟬𝟭-𝟴𝟱𝟱-𝟱𝟵𝟬𝟱 (OTA) 🔰(OTA) website. After login in, select "My Trips" and input the booking information and confirmation code. Find the button to edit your reservation after selecting your flight. Choose a new Name and pay any necessary fees by following the instructions. To finish the procedure, make sure you get an email or notice on their website confirming the adjustments you made.


Remove dynamics from simulation

Discussed in https://github.com/google-deepmind/mujoco/discussions/1533

Originally posted by aleada23 March 21, 2024
Good morning. I'm a student and I'm using MuJoCo for a project. I know that dynamic is an important feature for this engine, but I need to remove it from my environment.
I've created an environment, also using Robosuite, where a robot has to perform tasks. Now, I need to remove the dynamics from the environment to make computation lighter for implementing a new learning component. Is it possible to remove the dynamics? I would like to avoid any calculations related to it, as it isn't necessary in this new phase. The dynamics currently does not constitute a fundamental part of my simulation during the learning phase, so I can do without it. I am only interested in keeping some functionalities active, such as the rangefinder sensors, or obtaining the Jocobian for solving inverse kinematics for robot control. Therefore, I would like to do away with the dynamics completely removing the values. For instance, if I were to zero out masses and frictions, I would remove a significant portion of the dynamics from the simulation, but I believe the calculations would still be performed, keeping the simulation slow as it is now.
Any suggestion about this?
Thank you for your time

Yuval's suggestion under your previous post would probably work for you. If you have your own way of updating or setting qpos/qvel, you can just call individual sub-steps from mj_step as needed.
I recommend reading up of the simulation loop section in the docs, especially the breakdown of mj_step1. you can check the source code of the substeps inside mj_step1 (e.g. for mj_fwdPosition) or their summaries in the API documentation, if you need to go even more fine grained.

Thank you, I'll check the documentation that you provided.


Search input box should trim carriage return

I'm new for Atom so I don't have a clue how to fix this.
On Windows, I copy some text that have a trailing carriage return from other application, such as excel, notepad, then try to search the opening doc in Atom. Then I was surprising that there's no match. Because you cannot see the trailing carriage return in any form on the editor, you may not aware the fact that you are actually searching a 2-lines text.
The search input box seems to be a single-line one, so I guess we may need to trim CRs and LFs there.
Atom Version 0.181.0 2015/2/19 上午5:56:33

I believe this is a duplicate of https://github.com/atom/atom/issues/4400

God, there is a scroll bar there. Very funny.


fix: Increase timeout in testLocalDatabase

copilot:all

Current dependencies on/for this PR:

main

PR #3603   👈

This comment was auto-generated by Graphite.


upgrade package and project

is there any plan to upgrade the project to use latest version?

is there any plan to upgrade the project to use latest version?

I'm working on my project that using React Boilerplate and I always maintain it by update the packages and refactor code as well. Please check out my project https://github.com/ilhammeidi/enlite-starter


Incorporate upstream changes from cisagov/skeleton-generic

🗣 Description
Pull in upstream changes from cisagov/skeleton-generic.
💭 Motivation and Context
I have some changes to make to this repository, so it makes sense to first bring it up to date with the skeleton it is based on.
🧪 Testing
I ensured that the GitHub Actions all execute successfully.
🚥 Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (causes existing functionality to change)

✅ Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

This project should really be broken up into separate Packer and Terraform projects, but since this code is on its way out (in favor the new GoPhish code for PCA), I won't bother.


x/tools/internal/lsp: test failures due to data corruption

This could be a symptom of #37269, of #36605, or of some other undiagnosed memory-corruption bug. (I note goroutines in both golang.org/x/tools/go/packages.Load and golang.org/x/tools/internal/fastwalk.Walk in the stack dump.)
https://build.golang.org/log/4924e7126d7b849af0daebadc00289e321818f5e

020/02/26 22:48:02 no dep handle: no metadata for nosuchpkg
	package = nosuchpkg
2020/02/26 22:48:15 unable to compute error positions: no file for  in package golang.org/x/tools/internal/lsp/danglingstmt
	package = golang.org/x/tools/internal/lsp/danglingstmt
2020/02/26 22:48:15 unable to compute error positions: no file for  in package golang.org/x/tools/internal/lsp/danglingstmt
	package = golang.org/x/tools/internal/lsp/danglingstmt
2020/02/26 22:48:44 initial workspace load failed: couldn't run 'go': chdir /tmp/workdir/tmp/TestLSP_GOPATH210517143/lsp/src: no such file or directory
2020/02/26 22:48:44 initial workspace load failed: err: exit status 1: stderr: 2020/02/26 22:48:44 cannot determine current directory: getwd: no such file or directory

2020/02/26 22:49:32 no dep handle: no metadata for nosuchpkg
	package = nosuchpkg
2020/02/26 22:49:41 unable to compute error positions: no file for  in package golang.org/x/tools/internal/lsp/danglingstmt
	package = golang.org/x/tools/internal/lsp/danglingstmt
2020/02/26 22:49:41 unable to compute error positions: no file for  in package golang.org/x/tools/internal/lsp/danglingstmt
	package = golang.org/x/tools/internal/lsp/danglingstmt
2020/02/26 22:49:52 diagnose: could not generate diagnostics for go.mod file: err: exit status 1: stderr: golang.org/x/tools/internal/lsp/bad imports
	nosuchpkg: package nosuchpkg is not in GOROOT (/tmp/workdir/go/src/nosuchpkg)

2020/02/26 22:49:54 quick fixes failed: err: exit status 1: stderr: golang.org/x/tools/internal/lsp/bad imports
	nosuchpkg: package nosuchpkg is not in GOROOT (/tmp/workdir/go/src/nosuchpkg)

	file = file:///tmp/workdir/tmp/TestLSP_Modules744837051/lsp/suggestedfix/has_suggested_fix.go
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x0]
…
FAIL	golang.org/x/tools/internal/lsp	161.038s

CC @findleyr @stamblerre @ianthehat @matloob

/cc @heschik

Freebsd doesn't have an oversized dirent, so I don't think it was #37269. I fixed it anyway. I don't have any good guesses for the correct cause.

See also #37602, #37688.

Glancing at the builders, I don't see any occurrences. Closing.


Rethink domain-map.json to be a folder with each domain as file

This sounds better for handling more than a few domains, but will need to be merged for SSM handling - or have to be split with 1 SSM + 1 Edge lambda per domain


Should prompt values override argument values

I've run into a use case where I want to use prompts to make sure required arguments have been provided, and if they are, format and validate using the prompts correctly.
For example, I can setup my prompt.js as:
  // ...
  prompt: async ({ prompter, args }) => {
    return {
      ...await prompter.prompt({
        name: 'scriptName',
        type: 'input',
        message: 'What script should we add it to?',
        skip: () => args.scriptName !== undefined,
        initial: args.scriptName,
        format: kebabCase,
        result: kebabCase,
      }),
      ...await prompter.prompt({
        name: 'commandName',
        type: 'input',
        message: 'What command name should we use?',
        skip: () => args.commandName !== undefined,
        initial: args.commandName,
        format: kebabCase,
        result: kebabCase,
      }),
    }
  },
  // ...

In this case, I want to prompt the user to provide in addition to name, a scriptName and commandName. However, I don't want to prompt the user for the input if they've already provided through the arguments. For example:
hygen foo create-bar barName --script-name fooBar
... would only prompt for commandName, but scriptName would not be prompted. Also, since the scriptName argument was provided, the prompt will still run the result handler, kebab'ing the fooBar to foo-bar.
Now I would expect in my templates to use <%= scriptName %> and <%= commandName %> directly.
Based on a little digging, we found that this might be a really easy fix. Looking at hygen/params.ts at 1ccc4912f45f1ef18f6c4dc21f554d27e80e29f0 · jondot/hygen, if the cleanArgv and promptArgs lines are swapped in the Object.assign, then the prompts could override/extend the argument values.
Thoughts?

Now thinking about this a bit more too, the name argument could also be prompted if the user doesn't provide one. This could be a better experience when a user forgets to include a name and is not left with unnamed as the default name.

Especially when you build validations on the name prompt. The user could supply an incorrect name and with the current implementation the result from prompt would be simply ignored.
Imo promptArgs should come last.
const args = Object.assign({
     templates,
     actionfolder,
     generator,
     action,
     subaction,
 }, cleanArgv, name && { name }, promptArgs);

Looks like a good idea, will implement this per @fyyyyy latest version

Should be good now, closing up, thanks for the idea!


small changes to test out CI on pull request

Generating a pull request so that I can debug the conda3 issues that are getting in the way of Travis.

Testing all done.  Split the changes into two separate branches and sent PRs to python-control.


Bug 20180 axial renderer bottom origin

This puts the origin in the axial renderer in the bottom rather than the top.
Signed-off-by: Miklos Espak<EMAIL_ADDRESS>

Closing this. This PR is invalid. Axial origin was correct, coronal origin was wrong. All these issues have been resolved by another PR and are on the master now.


Add hotkey to resend last user message

Adds one of the features of #1:

Press Ctrl+R to repeat the previous prompt

I couldn't figure out how to stop current response, as I am not familiar with tokio::sync.
The code was extracted to a local macro to reduce duplication.
Hope this helps :)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 46 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.5%) to 47.086%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/application/ui.rs
0
46
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.5%

Covered Lines:
808

Relevant Lines:
1716

💛  - Coveralls

@darccyy Great idea, thank you!


Extend model container testing to all deployers

Extend model serialization/functionality testing of test_predict_function to all deployers (not just python).

Closed as it is resolved.


Implement simple service binding/selection

Part of an extension definition in the registry will describe objects that can be bound to a given extension.
Simplifying assumptions:

This initial implementation can be arbitrarily dumb and simple; querying Fedora (or a triple store) at will whenever it’s necessary to do so.  Once this is complete, create a github issue for optimizing the binding process (e.g. maintaining a cache) if it seems necessary.

Depends on:

#5 (extension and service registration model)

Testing:

Verify that the framework binds extensions when it should, doesn’t bind when it shouldn’t.
Update binding criteria in registry, verify that binding impl respects these changes
Delete extension, verify that binding impl can no longer bind to it

Implemented and tested in https://github.com/fcrepo4-labs/fcrepo-api-x/pull/31


Add --quiet or --no-progress-bars to spfs commit and push

Is your feature request related to a problem? Please describe.
Some spfs commands use console/text based progress bars. The progress bars seem, to clear the console as a side-effect. spfs commit and spfs push are examples of where this happens.
Users have found, when those commands are used in scripts, either directly or indirectly (e.g. from an application launcher, or renderfarm job launcher), useful output from other parts of the script is lost. It is cleared away by the console clearing that happens as part of the progress bar display. Losing key parts of their script's output annoying and ideally they'd like it to stop, or have an option stop it happening.
Describe the solution you'd like
Add --quiet or --no-progress-bars option to spfs commit and spfs push commands (and perhaps others with console clearing progress bars) to not output progress bars, or not clear the console/terminal window when using them, or similar. Then people, scripts, and tools have the option of seeing the progress bars or not.

Even though (we think, it's being tested in production) the screen clearing/redirect problem has gone away, users are asking for an option to hide the progress bars.
So I've reopened this so we can look at adding a --quiet on --no-progress-bars option to the spfs commands to let things that call these commands hide these bars as needed.


Create Modulus 23.11 image for development purposes available in MLWorkspace

@martin-muzelak transferred here, it's more relevant repo for such issue/task


rem: Use more precise spec link

The original link was for the entire font-relative lengths section (which also includes the em, ex, and ch units, some of which even have their own caniuse entries).
The new link is for the rem unit specifically, for precision.

Thanks!


SNOW-1346901 - Update the API Coverage as generated from a test run. Modify the coverage

SNOW-1346901 - Update the Snowpandas API Coverage as generated from a test run.
Modify the coverage generator to pickup the intermediate class names correctly for tests.

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


New data table from KeWang

Data table added by KeWang at 2016-01-21T19_19_04.526564

@keflavich @SirArthurTheSubmitter
Can you please merge this dataset ?


Extract common metrics and logging

Done:

extracted common grpc tracing and metrics from worker-executor to golem-common
added grpc tracing and metrics to worker service
switch to structured logging in

golem-common
worker-service (expect openapi)

added spans to golem-common retry and worker-service call_executor
extracted common log and config handling

logging now can be configured for stdout and file output separately
added config loader:

configs now derived from the config struct defaults; added missing defaults and aligned them with the current toml local defaults
added common command line options to dump the default (and custom examples for covering enum config cases) and the loaded configs as toml or env vars
to avoid drifting code defaults and toml values (and to cleanup obsolete ones) addd cargo make command to generate configs and sample env vars

added a new json formatter to flatten spans in logs:

spans are merged into the main message json object with the span name
in case of repeated spans only the last span is included

Todo in folllow up PR:

use structured logs everywhere
use grpc tracing everywhere
add OpenAPI tracing like we have for grpc

I like the changes! :)


Run dep ensure with dep 0.5

Recent change to our test infra have bumped the dep version we use to v0.5.
In future, this sort of thing will be handled by Bazel for us 😄
/assign

/test verify

/test verify

/release-note-none


Plot time-series data for data elements

Create graphs of time (year) vs. a data element selected.
Have the option to create for all counties for a state, or select certain counties. Or select counties or HUCS from several states.
Have the option to plot the y-axis with different ranges:

User defined range,
Data range for the plot
All data in the query (i.e. all counties’ values for a data element)

timeDF <- data.frame(
  year = c(1985, 1990, 1995, 2000),
  A = c(1,2,3,4),
  B = c(2,2,2,3),
  C = c(4,3,3,2)
)

library(ggplot2)

timePlot <- ggplot(data = timeDF) +
  geom_line(aes(x = year, y = A)) +
  geom_line(aes(x = year, y = B))

timePlot

library(tidyr)

longTime <- gather(timeDF, county, population, -year)

longPlot <- ggplot(data = longTime) +
  geom_line(aes(x = year, y = population, color = county))
longPlot

'#' time_series_data
#'
#' time_series_data
#'
#' @param data.elements character name of data element within available categories by year for state
#' @param years vector of integers specifying all years available for state. Defaults to NA which shows all years in dataset.
#' @param w.use is the datafile that includes all areas in all data elements for state
#' @param areas is a geographical area as defined in your datafile such as county, HUC, or aquifer
#' @param y.scale allows R to set the y-axis scale given available data range. Defaults to NA which lets R set the scale based on dataset values.
#' @param log = TRUE or FALSE allows user to set log scale, default is FALSE
#'
#'
#' @export
#'
#' @examples
#'
#' year1 <- 2005
#' year2 <- 2010
#' years <- c(year1, year2)
#' areas <- c("Dane","Milwaukee")
#' data.element <- "PS-GWPop"
#' w.use <- NA
#' time_series_data(w.use, data.element)
time_series_data <- function(w.use, data.elements, years= NA, areas= NA, y.scale=NA, log= FALSE){
return(NA)
}'
The above is what we (Gary, Laura, and Jen) came up with and we're saving it here for future reference

[ ] option for either clustered bar or dots (make new argument that accepts TRUE/FALSE)...going to change geom_line to either geom_point or geom_bar
[ ] optional legend
[ ] color code by area
[ ] remove "value" from axis label

:palm_tree:

:100:!

:v: :vertical_traffic_light: