RSS output link does not contain base url

What version of Hugo are you using (hugo version)?

$ hugo version
Hugo Static Site Generator v0.62.2/extended darwin/amd64 BuildDate: unknown

Does this issue reproduce with the latest release?
yes
Discription
This issue roughly started after Hugo 0.55, since I remembered thinking there was something wrong with the way I implement the new formatting.
For example, all my post as in RSS readers have since appeared as /post/2019/mm/title, which was not true before.
I use my own theme without specifying rss.xml, so I am assuming that this must be something to do with Hugo generator's embedded RSS template.
Any help is welcome!

Bump.
Further discription:
For example, following is the output of my website using default RSS template. Note how the <link>'s were wrongly generated.
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>loikein's notes</title>
<link>/</link>
<description>Recent content on loikein's notes</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-gb</language>
<lastBuildDate>Fri, 30 Nov 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="/index.xml" rel="self" type="application/rss+xml" />
<item><title>Notes on The Missing Semester of Your CS Education</title>
<link>/post/2020/05/notes-missing-semester/</link>
…

The built-in template uses Permalink which I'm confident adds the baseURL ... if it's set.

It is set, unfortunately.

My `config.yaml`:
baseUrl: 'https://notes.loikein.one/'
languageCode: en-gb
title: loikein's notes
theme: hugo-lithium-loikein
googleAnalytics: UA-143089736-1
disqusShortname: loikein-github
ignoreFiles:
  - \.md$
  - \.Rmd$
  - \.Rmarkdown$
  - \.ipynb$
  - _files$
  - _cache$
hasCJKLanguage: true
rssLimit: 50

publishDir: ../loikein.github.io

permalinks:
  post: '/:section/:year/:month/:slug/'

menu:
  main:
    - name: Notes
      url: /post/
      weight: 1
    - name: Writings
      url: /writings/
      weight: 2
    - name: Tags
      url: /tags/
      weight: 3
    - name: Search
      url: 'https://duckduckgo.com/?q=site%3Anotes.loikein.one'
      weight: 4
    - name: Source
      url: 'https://github.com/loikein/loikein.github.io'
      weight: 10

params:
  description: 'Personal research blog about math, economics and programming'
  footer: loikein
  disqusURL: 'https://notes.loikein.one'

  highlightjsVersion: 10.0.0
  highlightjsCDN: //cdnjs.cloudflare.com/ajax/libs
  highlightjsLang:
    - r
    - python
    - applescript

  highlightjsTheme: github
  favicon: favicon.ico
  logo:
    url: logo.png
    width: 50
    height: 50
    alt: Home

Same issue here with latest version.

Thank you for your reply! I always update Hugo automatically, but this issue is always there.

Try for fun to give the baseURL via commandline --baseURL="flaf", for some reason i need to do that to get it to work with normal baseURL

I have figured out my problem, which is not running build but only server locally. Running server locally does not bake baseURL into rss.xml as building would.
Helpful link: D.3 Building a website for local preview | blogdown: Creating Websites with R Markdown


Firebase dynamic link not opening the app iOS9

I have developed & installed an iOS app locally on my device.
And have set custom scheme in the info.plist as mydlink
Set associated domains as weel: applinks:.app.goo.gl
Created dynamic link on firebase as:
https://.app.goo.gl/?link=http://<mysite.com>/&ibi=&ius=mydlink&ifl=https://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id%3D%26mt%3D8&pt=
When i open or click on dynamic link, it opens app page in the "App Store" app and not opening app itself though its installed.
Can you point out here what i am missing..

The top answer here solved it for me:
http://stackoverflow.com/questions/32751225/ios9-universal-links-does-not-work
I was trying to open the deeplink in safari and that is not working.

HI I can open the iOS app locally when it's installed, but it opens the app stores also.

I have similar Issue, when I open link in for example gmail app, it redirect it to my application, but when I'm openning it in standard iOS mail app it goes straight to Safari and then to custom page or Apple Store depends what user choose.
After much digging I can't find what I could be missing.

When I use Chrome browse.  It is OK!

Some of this I think is just general universal link handling - safari entered links (and links from within your app) are going to go to the fallback view, but links within a webpage or using openUrl should work OK. I'll close this, but if anyone is having issues please open a specific issue (ideally with a complete long link that isn't working), or file an issue with Firebase Support: https://firebase.google.com/support/contact/troubleshooting/


[Bug]: SyntaxError: Unexpected token 'I', " In Filesys"... is not valid JSON

Extension Version
0.1.14
PHP Binary
Herd
Operating System
macOS
What happened?
The extension errors with the following:
2024-12-20 10:03:57.185 [info] Activating Laravel Extension...
2024-12-20 10:03:57.186 [info] Started
2024-12-20 10:04:08.838 [error] SyntaxError: Unexpected token 'I', "
In Filesys"... is not valid JSON
    at JSON.parse (<anonymous>)
    at /Users/jack/.vscode/extensions/laravel.vscode-laravel-0.1.14/dist/extension.js:60:1614

Mimimal Code Sample
No response

I had this problem after I installed the extension and ran it the first time.
Extension version: 0.1.14
PHP Binary: Homebrew, 8.4.1 (cli)
Operating System: macOS Sequoia 15.2
It didn't disappear after running "Developer: Reload Window," but it disappeared after I restarted VS Code.
Related code:
https://github.com/laravel/vs-code-extension/blob/9b69eeab8e6035aae8491f88f9ebd50f4d9369fb/src/support/parser.ts#L143-L146
https://github.com/laravel/vs-code-php-parser-cli/blob/main/app/Commands/DetectCommand.php


185382879-comments-yellow-styling

Fulfills ticket
185382879-comments-yellow-styling

@dennisrcao and @tealefristoe this PR broke a couple cypress tests. I think it is because the cypress tests are looking for specific colors in the comment area and now those colors are different.


2-digit numbers

Animation form:
2 digit numbers are being split

solved with  String split() Method


rtop prints (_none_)+let instead of let

Reason # let rec f = fun () => f ();
_none__none__none_let f : unit => 'a = <fun>

and
Reason # let g = fun n => print_int n;
_none_let g : int => unit = <fun>
Reason # g 1;
1- : unit = ()

This seems to be dependent on the unit return type? This function from int -> int doesn't have this behaviour:
Reason # let g = fun n => n + 1;
let g : int => int = <fun>

Possibly fixed by https://github.com/facebook/reason/commit/d06d8cf79b4667f334814107be103fe9b6f25df7
Will verify and close this if so...

This is fixed by the above commit:
Reason # let f = fun n => print_int n;
let f : int => unit = <fun>
Reason # let rec f = fun () => f ();
let f : unit => 'a = <fun>

@simonjbeaumont Thank you!


unexpected value for species.maturity.size.sp for Scomberomorus cavalla (FishBase ID: 120)

In #73, @agruss2 shared that the expected value for species.maturity.size.sp for  Scomberomorus cavalla (FishBase ID: 120) is 63.3 . However, the actual value was: 0.0 .
I was able to reproduce the result. Also, I found that the value 0.0 appears because only the first row in the fishbase table maturity contained a null value for the Lm column.
On inspection of the values retrieved from the fishbase api (see https://fishbase.ropensci.org/maturity?SpecCode=120&limit=5000), I found that 13 rows appeared. However, the value 63.3 does not appear. This is why, I suspect that the defined mapping in fishbase-mapping.csv might needs updating.
Also, I've changed the bridge implementation to map the first non-null value in the results.
This change resulting in the line species.maturity.size.sp2;50.0 to appears in osm_params-species.csv . The values seems to be consistent with those found in http://fishbase.org/Reproduction/MaturityList.php?ID=120 rather than the summary page http://fishbase.org/summary/120 .
@agruss2 The reported expected value could not be found with the mapping constraints defined in the fishbase-mapping.csv . Please revise the mapping or suggest alternative implementation.

@jhpoelen I thought about to best update the fishbase-mapping.csv (see https://github.com/jhpoelen/fb-osmose-bridge/blob/master/src/main/resources/com/github/jhpoelen/fbob/fishbase-mapping.csv).
To my mind, this is the only thing I needed to do to address the present issue.
If you need anything else from me, please let me know. Otherwise, please close the present issue.


Continuous Delivery - User with custom role can't edit allowedTargetNamespaces throws error

Setup

Rancher version: v2.7-head a49d36c
Fleet version: v0.6.0-rc.5
Browser type & version: Firefox Chrome

Describe the bug
A user with custom role to  list, create, update and get on fleetworkspaces resources can't edit an existing workspace when adding an allowedTargetNamespaces
To Reproduce

Add a new user role with permissions to list, create, update and get  on fleetworkspaces resources.
Create a new workspace with blank allowedTargetNamespaces
Edit the created workspace and try to add allowedTargetNamespaces

Result
Cannot read properties of undefined (reading 'linkFor')
Expected Result
The user with permissions to fleetworkspaces can edit a workspace's allowedTargetNamespaces successfully.

@mantis-toboggan-md The user will need permissions on GitRepoResource for this to work. The UI will need to check that the user has access to this resource. @Shavindra Did you not check this situation?

/backport v2.7.2

Validated working on:
Dashboard version: release-2.7.2 d1ea2d47b
Rancher version: v2.7-head-4a9b7ba
Fleet version: fleet-agent:v0.6.0-rc.5


Hold a briefing session with UW ML dept on ways to go about reading seven-segment-display

Possible solution

Launch the IPE and do some pre-processing
Take the G6PD image Create some segments where the reading will be collected
Join the spaces on seven-segment digits Get the whole number so no space within a digit
Run the new image through ML Kit Do post-processing to get the different values
Send to the RIM module for interpretation i.e (Result Interpretation Module)

Findings on this are documented here.


Replace Vec parameters by IntoIterator

Part of #174
Maybe I should use where clauses instead of fn foo<It: IntoIterator>(_: It). What do you think?

(Forgot to add my response to your where clause question in the review fuss, so i'm just gonna do it like this.)
The bounds aren't necessarily long so nah, this is fine.


core: Handle arguments returned by Text Generation Inference's Messages API

core: Handle tool arguments returned by Text Generation Inference's messages API

Description: The parser for OpenAI tool calls expects the function arguments to be returned as a string. This is true for OpenAI's own API, but not necessarily for OpenAI-compatible APIs like Text Generation Inference's (TGI) Messages API. TGI returns the arguments as a dictionary. Since some OpenAI-compatible tools refer to OpenAI's client library (which handles TGI's tool response correctly), it makes sense to also support them through LangChain's OpenAI wrappers. This PR checks the type of the returned arguments and correctly processes them accordingly.
Issue: #26777

hey! i believe this would be an issue with TGI not actually being openai-compatible
would recommend using the integration for TGI in langchain-huggingface instead!

Thanks for taking a look at this!
Unfortunately, there is no integration for TGI's Messages API in langchain-huggingface, best I can tell. TGI also officially refers to OpenAI's client library. Other serving platforms may also benefit from this flexibility (the linked issue uses koboldcpp, for example).

I have started discussion #27561 since this is touching multiple packages and may be more about finding the right tool for the job.


Redesigned the footer

You can check the design if any problem arises then you can tell me, I will change it.

https://github.com/Jagroop2001/AcmeRockets/issues/30


Hide restart button

#3144  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tommylau523 and the rest of your teammates on  Graphite


Complete constructor keyword after property declaration

Fixes #43650
This is my first pull-request here. Help and suggestions are appreciated.
All these four situations are fixed, expanding the case in original issue.
class A {
 bla
 constructor/*1*/(props) {}
}
class B {
 bla;
 constructor/*2*/(props) {}
}
class C {
 bla: number
 constructor/*3*/(props) {}
}
class D {
 bla: number;
 constructor/*4*/(props) {}
}

This seems like an oddly-specific fix, and I'm not sure if it really identifiers the root problem. Why weren't we offering up completions before?

In my opinion, this is a missing case of getting completions during class declaration.
The function tryGetObjectTypeDeclarationCompletionContainer checks the contextToken to give a completion.
https://github.com/microsoft/TypeScript/blob/f74f9cac1344f6c88078c65d89a4d496bd5a8525/src/services/completions.ts#L2835
However, it doesn't consider the implicit any case like:
class Foo {
   bar; // <- context token
   constructor/**/()
}

since there is no switch-case for contextToken as an Identifier. So it fall back to default, and check the contextToken using
https://github.com/microsoft/TypeScript/blob/f74f9cac1344f6c88078c65d89a4d496bd5a8525/src/services/completions.ts#L2737
This function doesn't consider the situation that contextToken is an Identifier either (but does for AsyncKeyword), resulting an undefined (no suggestion) return for completions.
What's more, for case with a TypeReference like:
class Foo {
  bar: number // <- context token w/o semicolon
  consturctor/**/()
}

The completion is blocked by https://github.com/microsoft/TypeScript/blob/f74f9cac1344f6c88078c65d89a4d496bd5a8525/src/services/completions.ts#L1816
which is a different case from the previous one.
The fix for this is made referring to a similar issue:
https://github.com/microsoft/TypeScript/blob/f74f9cac1344f6c88078c65d89a4d496bd5a8525/src/services/completions.ts#L2377

You need to actually check for an ASI-triggering newline if you want to prevent a completion at
class C {
  blah /*| constructor*/
}

I don’t know how important that is, though.

Hi, I'm not very sure of what you mean. I'm basically allowing instead of preventing completions. And the behavior for cursur at that position should be unchanged. Do these changes affect ASI in some way?

Updated. New fix available now.

@typescript-bot pack this

Ok, so this is what I meant about checking newlines: https://www.staging-typescript.org/play?ts=4.3.0-pr-43654-9#code/MYGwhgzhAEDC0G8BQ1oCNwAtrAPQCp9ckBfIA
If you trigger completions at the comment, you now get a completion for constructor which is invalid due to the lack of a semicolon or newline. Because of ASI, either a semicolon or a newline makes constructor a valid next token, but it’s not valid here.

I've adopted a validation using newline or semicolon. The completions for these two cases are blocked now as the original behavior in 4.3.0-beta:
class A {
  blah /*|con*/
}
class B {
  blah: number /*|con*/
}

And constructor will not be suggested for this:
class C {
  blah
  /**/
}

since
class C {
  blah
   = 123
}

is legal. Unless user types a c at that position.
During the debugging, I've found another issue of property with an initializer that might be controversial. In 4.3.0-beta, completions of private / protected / public / constructor can be triggered like this:
class C {
  blah = blah /*|p*/
}
// PLAYGROUND: https://www.staging-typescript.org/play?jsx=0&ts=4.3.0-beta#code/MYGwhgzhAEDC0G8BQ1oCNwAtoF51egAcB6AKlOKQF8g

It looks unlike an intended one. But I'm not sure and haven't fix this since it is guaranteed by some test cases like tests\cases\fourslash\completionsClassPropertiesAssignment.ts.

constructor should not but is now still suggested at:
class T {
  blah: number con/**/
}
const SomeConst = 123
class U {
  blah = SomeConst con/**/
}

I'm still working on this.

The simplifications are looking great. Let me know when you’re ready for another review. Thanks!

The fix should be all-rounded and reliable enough now. Please refer to the test case:
https://github.com/microsoft/TypeScript/blob/70adf96ed0b9445ec0468ff038588247f87a7c81/tests/cases/fourslash/completionConstructorKeywordAfterPropertyDeclaration.ts
for detail.
What's more, we've got a byproduct that, for 15-21 in the test case of situations that constructor should not be suggested, completions for private / public / protected are also blocked, which should be reasonable. (See https://github.com/microsoft/TypeScript/pull/43654#issuecomment-825549637)
At last, kindly ping @andrewbranch .

Thanks for your help. Have a nice day!


Add MirrorNode Client to make calls to real Mirror Node

Signed-off-by: Nana-EC<EMAIL_ADDRESS>Description:

Add axios-mock-adapter to allow http request mocks
Update test.env MIRROR_NODE_URL to point to localhost not live public testnet
Add MirrorNodeClient class to manage requests and pull out of mock Mirror Node
Update eth.ts w reference to MirrorNodeClient to allow for use
Update relay.ts setup to pass MirrorNodeClient to eth.ts

Related issue(s):
Fixes #
Notes for reviewer:

I went too far down the rabbit whole before realizing the tests are mostly testing axios, they actually belong in the eth.spec.ts and so can be move there in the follow up PRs that actually call the mirrorNodeClient.
I have stubbed out 1 for all so that it's an easily lift
mirrorNodeClient tests should focus on the param management

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

What is the difference between the "MirrorNode" and "MirrorNodeClient"? Does the new one replace the old one? Why have both?

From Slack:

We should be able to phase the mirrorNode class out with the mirrorNodeClient
My aim was to streamline development and reduce review time and conflicts when merging.
eth.ts should call the mirrorNodeClient and process the results as defined in 0.57.0

The code smells are bologna. Can we turn that particular warning off?

Yeah, that one annoyed me a bit. I could work around it with additional interfaces to force group items but that's a nice to have right now.
Will look into how to silence that smell


Fixes zero size issue when using an attributedTruncationToken

Fixes sizeThatFits issue where the size returned was 0 when using an attributedTruncationToken.
Addresses: #621 and #678.
You can run the test from commit [2be9753] to see the size being returned as (0, 0). Re-run the test with commit [	93cb76d] to see the test pass.

Just wondering if there is any feedback on this. It's been just over a month. :) I'd love to get this merged in to help others.

@jhersh Thanks, I'll knock that out quick. Just a heads up I'm seeing the testLabelTruncationVaryingWidthSizing test fail with the current top of the master branch [e44d8eb].


When installing new instances, provide a link to the admin interface

When installing a new instance this is what you get:

It would be useful to get a link to the admin page from this view

This was fixed in https://github.com/platzio/frontend/commit/4c09806fad2147575d5bc1bfdb5d34430b64ce05 (in v0.4.7-beta.4)


un-validate or un-discard a record from within the UI

Is your feature request related to a problem? Please describe.
after validating a record (by accident) I potentially want to revert this.
Describe the solution you'd like
This could be done by pressing the validate button again. I believe this used to be possible before.
Describe alternatives you've considered
N.A.
Additional context
N.A.

this also applies to un-discarding

Pending to be implemented into T2T at bulk action level


Deployment

User Story
As a bootcamp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criteria
Given a Prework Study Guide website,
When I visit the website using the URL,
Then I can access my website from any browser.

I did finish this. You can find the webiste at https://prodigalprogrammer.github.io/prework-study-guide/


Add missing Entity Types and Relation Types

Cognitive Services Language API - Healthcare changes for 2023-04-01

API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your engagement record.

Link to engagement record issue: https://github.com/Azure/azure-rest-api-specs/issues/22225

Is this review for (select one):

[ ] a private preview
[ ] a public preview
[x] GA release

Change Scope
In Text Analytics for Health, there are several Entity Types (NER capability) and Relation Types (Relation Extraction capability) that were added since the API had been updated last time.
These types are part of extensible enums and are actually returned by the API today. This addition to the API specification aims to reflect the existing state of things.
This change should solve [Text analytics] Missing enums in HealthcareEntityRelation and HealthcareEntityCategory · Issue #27406 · Azure/azure-sdk-for-python (github.com).

Design Document: N/A
Previous Open API Doc: analyzetext.json
Updated paths: N/A

❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

Adding Approved Breaking Change because it's just updating features in a dev branch.

@jhendrixMSFT Hi Joel, the service team has completed work here and I think this is ready to merge. Could you to the honors please?


Make sure the content width is sampled more often, when adjusting navigator.

Bug/issue #, if applicable: 101085867
Summary
Fixes the sampling rate of the content, when adjusting the sidebar. This will prevent the OnThisPage from staying visible until you release the mouse and ending the resizing.
Dependencies
NA
Testing
Steps:

Resize the navigator fast up to its maximum (drag fast to the right)
Assert the OnThisPage gets hidden when you reach the end, no need to release the mouse button.

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[ ] Added tests - no need, just changes to use throttle, which is mocked out.
[x] Ran npm test, and it succeeded
[x] Updated documentation if necessary

@swift-ci test


Incorrect version for node type definitions

The package.json has type definitions for Node.js 7, I believe coming from here:
https://github.com/castlabs/electron-releases/blob/906255316e95dcc1329d55a9ae36de9a91c803c6/package.json#L14
But Electron 1.8.1+ uses Node.js 8
https://electronjs.org/releases#1.8.1
This causes warnings when you try to use this package with an application that has a dependency on the Node.js 8 type definitions.
error TS4090: Conflicting definitions for 'node' found at<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Consider installing a specific version of this library to resolve the conflict.

Good catch, I'll make sure it gets fixed for 1.8.8 (and other future releases).

If you have not seen it already I published releases based on Electron 3.0.0-beta.9 and 1.8.8, both of which now has the same node version specified as the original release.

Just tried it out, looks good.  Thank you for the quick response.


i18n(zh-cn): Update authentication.mdx

Description (required)
Update authentication.mdx
Related issues & labels (optional)

#9703
Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

zh-cn
guides/authentication.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Improve GH actions haskell environment

Make a custom step to pull ghcup to install all tools for the project.
To set up a working environment, we install stack and configure it to use
globally installed GHC from ghcup. This makes it easier to cache
everything.
#286
The contribution:

[x] updates all affected documentation
[ ] provides commits messages which comply with the CONTRIBUTING.md > Committing the changes rules
[x] updates the completion scripts if requires
[ ] complies with all requirements from README.md > Hands-on development notes

@bees-hive/elegant-git-maintainers, please review.

merged


Can't get it to work with local development pod

I get this error:
NoMethodError - undefined method integrate_targets= for #<Pod::Config:0x007fb4bb0b0aa0>

Here's my Podfile:
source 'private-pod......-podspec.git'
source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '9.0'
plugin 'cocoapods-rome'
use_frameworks!

def common_pods_for_target
  pod 'test_pod_2', :path => '../test_pod_2/'
end

target :test_use_frameworks_2 do
  common_pods_for_target
end

And here's my podspec:
Pod::Spec.new do |s|
  s.name             = "test_pod_2"
  s.version          = "0.1.0"
  s.summary          = "Trying to get Cocoapods-Rome working"
  s.description      = "Hopefully will build dynamic framework for me..."
  s.homepage         = "https://github.com/****/some_source"
  s.license          = 'MIT'
  s.author           = { "Author" =><EMAIL_ADDRESS>}
  s.source           = {:git => "https://github.com/****/some_source.git"}
  s.platform     = :ios, '9.0'
  s.requires_arc = true
  s.source_files = 'Pod/Classes/**/*'
  s.resource_bundles = {
    'test_pod' => ['Pod/Assets/*.png']
  }
  s.dependency 'NGAParallaxMotion', '1.0.2'
  s.dependency 'Igor', '0.5.0'
  s.dependency 'UICKeyChainStore', '1.0.5'
  s.dependency 'AFNetworking', '2.5.2'
  s.dependency 'STHTTPRequest', '1.0.2'
  s.dependency 'SDWebImage'
  s.dependency 'SVProgressHUD', '1.0'
  s.dependency 'CocoaLumberjack/Swift'
  s.dependency 'ReactiveCocoa', '2.1.8'
  s.dependency 'BlocksKit', '2.2.5'
  s.dependency 'handlebars-objc', '1.4.3'
  s.dependency 'FontAwesome+iOS', '0.1.4'
  s.dependency 'FontAwesomeTools', '1.2'
  s.dependency 'ActiveRecord', '1.2.2'
  s.dependency 'UIView+AutoLayout'
  s.dependency 'FMDB', '2.6'
  s.dependency 'SimulatorStatusMagic', '1.7'

end

I'm using this command:
pod _1.0.0.beta.2_ --verbose install
This Podfile works fine when not using cocoapods-rome, so there are no issues there.
Any ideas?

I don't think Rome has been updated for the CocoaPods 1.0 beta yet.

That's true. Just tested without and it works. But the Compatibility with CP 1.0 beta commit led me to think otherwise, so I assumed it'd be ok.

Well, not so sure it's working, actually. I decided to try the dead-simple example in this project's readme:
platform :ios, '9.0'

plugin 'cocoapods-rome'

pod 'Alamofire'

and that fails.
Here are the steps I took:

Made simple Xcode project
Tried both pod _0.39.0_ install and simply pod install
Here's console output:

Analyzing dependencies
Downloading dependencies
Using Alamofire (3.1.5)
Generating Pods project
Sending stats
Building frameworks //FAILS AT THIS POINT
[!] /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -project Pods.xcodeproj -scheme Pods -configuration Release -sdk iphonesimulator -destination id=6150BC95-BE73-4E00-9752-E94492577D1B

Build settings from command line:
    SDKROOT = iphonesimulator9.2

2016-01-27 10:54:09.888 xcodebuild[87840:4904244] [MT] PluginLoading: Required plug-in compatibility UUID 9AFF134A-08DC-4096-8CEE-62A4BB123046 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/XToDo.xcplugin' not present in DVTPlugInCompatibilityUUIDs
...LOADS MORE ERRORS LIKE THIS

IIRC, commit 0eb0a10d17f58e18d97b5d9152c63506251f0c33 was only for making Rome installable together with 1.0 beta, so that further testing can be done.
The PluginLoading errors are related to having third-party Xcode plugins installed which don't have the right compatibility UUIDs, that's completely unrelated to Rome. Do you see any build-related errors after those?

They're all plugin errors until this one:
xcodebuild: error: Unable to find a destination matching the provided destination specifier:
		{ id:6150BC95-BE73-4E00-9752-E94492577D1B }

	Available destinations for the "Pods" scheme:
		{ platform:iOS Simulator, id:390A56B2-3ED5-45DA-9DEE-BF2593344C7B, OS:9.0, name:iPad 2 }
		{ platform:iOS Simulator, id:D789365D-057C-4B45-B3E9-57A62EF5CF78, OS:9.1, name:iPad 2 }
		{ platform:iOS Simulator, id:A96B63D0-C1C5-41F4-9AD8-31CF5D078493, OS:9.2, name:iPad 2 }
		{ platform:iOS Simulator, id:C2F62560-685E-4330-84E0-0A4292D82DD8, OS:9.0, name:iPad Air }
		{ platform:iOS Simulator, id:7305401B-B18D-47BB-817B-72C6FAF38023, OS:9.1, name:iPad Air }
		{ platform:iOS Simulator, id:8DBF4D27-E040-4EAF-A3EB-D3F3A40557B1, OS:9.2, name:iPad Air }
		{ platform:iOS Simulator, id:C581567F-BD76-4D93-87AB-991D0BBCA21B, OS:9.0, name:iPad Air 2 }
		{ platform:iOS Simulator, id:8C050D55-1CCF-4BA2-AB95-449D58508CE8, OS:9.1, name:iPad Air 2 }
		{ platform:iOS Simulator, id:94050BE2-F71A-40F2-B05A-C2F3C8E6BBB0, OS:9.2, name:iPad Air 2 }
		{ platform:iOS Simulator, id:99CE85C9-96B5-453C-8618-383A2090D0E1, OS:9.1, name:iPad Pro }
		{ platform:iOS Simulator, id:7D8F58DC-F4EE-4657-88B5-845AF28716A8, OS:9.2, name:iPad Pro }
		{ platform:iOS Simulator, id:2787B64A-C45B-44B5-B6E2-536A981E93A9, OS:9.0, name:iPad Retina }
		{ platform:iOS Simulator, id:B9BCACF3-B587-4016-83F8-BDB2B5C14804, OS:9.1, name:iPad Retina }
		{ platform:iOS Simulator, id:5012448F-9524-4AD4-A6C0-F1CEB2D6C4F9, OS:9.2, name:iPad Retina }
		{ platform:iOS Simulator, id:36ACD50A-FD84-43F7-ACD0-B6AD923985B2, OS:9.0, name:iPhone 4s }
		{ platform:iOS Simulator, id:52B52F1E-8AA9-4274-9BBB-BCAB01AF8E7C, OS:9.1, name:iPhone 4s }
		{ platform:iOS Simulator, id:3FFC3344-F788-4914-BB4C-F7D1CE4DA31A, OS:9.2, name:iPhone 4s }
		{ platform:iOS Simulator, id:7EECC2F5-4EF3-4D72-A81E-10CCDD6BEEB3, OS:9.0, name:iPhone 5 }
		{ platform:iOS Simulator, id:6FC4609D-0E21-479A-AE12-7F0AC5B6ECEF, OS:9.1, name:iPhone 5 }
		{ platform:iOS Simulator, id:30EAD8AB-43C6-4DF2-B7DB-1F7D2C3ACF94, OS:9.2, name:iPhone 5 }
		{ platform:iOS Simulator, id:C4C6980D-A8EA-4DA8-AEFD-EF886C631300, OS:9.0, name:iPhone 5s }
		{ platform:iOS Simulator, id:85789191-746F-44E2-9715-404471373D4A, OS:9.1, name:iPhone 5s }
		{ platform:iOS Simulator, id:9868A633-05C3-4E18-87C7-D95DE8CF18A0, OS:9.2, name:iPhone 5s }
		{ platform:iOS Simulator, id:82C336EF-39DD-4C35-B32B-87E1DB998E78, OS:9.0, name:iPhone 6 }
		{ platform:iOS Simulator, id:B930FBD2-1B80-400E-BCC8-1B95543957EF, OS:9.1, name:iPhone 6 }
		{ platform:iOS Simulator, id:59E045A8-3677-40BD-A014-13AD4384F983, OS:9.2, name:iPhone 6 }
		{ platform:iOS Simulator, id:8E80423A-DDDB-4C96-A991-8704CD68B348, OS:9.0, name:iPhone 6 Plus }
		{ platform:iOS Simulator, id:17856DBE-05B5-4BCA-972C-491C9F4C25E7, OS:9.1, name:iPhone 6 Plus }
		{ platform:iOS Simulator, id:CAB74A79-BFF2-48F8-8DEF-C1FA1CD595A1, OS:9.2, name:iPhone 6 Plus }
		{ platform:iOS Simulator, id:2131E03F-5B71-4F5B-8040-3FA5DF81A63B, OS:9.0, name:iPhone 6s }
		{ platform:iOS Simulator, id:9163E76C-F738-4719-A3AD-02FCF51CF1E1, OS:9.1, name:iPhone 6s }
		{ platform:iOS Simulator, id:31901D28-6F25-4DF9-A9C8-E6DC7A6941BC, OS:9.2, name:iPhone 6s }
		{ platform:iOS Simulator, id:8F4BD7BA-D458-45EA-8169-4CDA557E73BE, OS:9.0, name:iPhone 6s Plus }
		{ platform:iOS Simulator, id:93CB4783-AC32-41E6-AA86-6F5668945257, OS:9.1, name:iPhone 6s Plus }
		{ platform:iOS Simulator, id:01E317B3-D0E6-4ED8-893F-65931C282BEC, OS:9.2, name:iPhone 6s Plus }

What can I do about the plugin errors? Some of the plugins listed are things I don't care about, but I do care about others. And some seem vital, like:
Support/Developer/Shared/Xcode/Plug-ins/CocoaPods.xcplugin
Support/Developer/Shared/Xcode/Plug-ins/NCSimulatorPlugin.xcplugin
Support/Developer/Shared/Xcode/Plug-ins/Open With Application.xcplugin
Support/Developer/Shared/Xcode/Plug-ins/Snapshots.xcplugin

Interesting, seems like the simulator that has been picked cannot actually be used. Could you share the output of xcrun simctl list please?

xcrun simctl list

== Device Types ==
iPhone 4s (com.apple.CoreSimulator.SimDeviceType.iPhone-4s)
iPhone 5 (com.apple.CoreSimulator.SimDeviceType.iPhone-5)
iPhone 5s (com.apple.CoreSimulator.SimDeviceType.iPhone-5s)
iPhone 6 (com.apple.CoreSimulator.SimDeviceType.iPhone-6)
iPhone 6 Plus (com.apple.CoreSimulator.SimDeviceType.iPhone-6-Plus)
iPhone 6s (com.apple.CoreSimulator.SimDeviceType.iPhone-6s)
iPhone 6s Plus (com.apple.CoreSimulator.SimDeviceType.iPhone-6s-Plus)
iPad 2 (com.apple.CoreSimulator.SimDeviceType.iPad-2)
iPad Retina (com.apple.CoreSimulator.SimDeviceType.iPad-Retina)
iPad Air (com.apple.CoreSimulator.SimDeviceType.iPad-Air)
iPad Air 2 (com.apple.CoreSimulator.SimDeviceType.iPad-Air-2)
iPad Pro (com.apple.CoreSimulator.SimDeviceType.iPad-Pro)
Apple TV 1080p (com.apple.CoreSimulator.SimDeviceType.Apple-TV-1080p)
Apple Watch - 38mm (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-38mm)
Apple Watch - 42mm (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-42mm)
== Runtimes ==
iOS 8.1 (8.1 - 12B411) (com.apple.CoreSimulator.SimRuntime.iOS-8-1)
iOS 8.2 (8.2 - 12D508) (com.apple.CoreSimulator.SimRuntime.iOS-8-2) (unavailable, failed to open liblaunch_sim.dylib)
iOS 8.3 (8.3 - 12F70) (com.apple.CoreSimulator.SimRuntime.iOS-8-3) (unavailable, failed to open liblaunch_sim.dylib)
iOS 9.0 (9.0 - 13A344) (com.apple.CoreSimulator.SimRuntime.iOS-9-0)
iOS 9.1 (9.1 - 13B143) (com.apple.CoreSimulator.SimRuntime.iOS-9-1)
iOS 9.2 (9.2 - 13C70) (com.apple.CoreSimulator.SimRuntime.iOS-9-2)
tvOS 9.1 (9.1 - 13U5077a) (com.apple.CoreSimulator.SimRuntime.tvOS-9-1)
watchOS 2.0 (2.0 - 13S343) (com.apple.CoreSimulator.SimRuntime.watchOS-2-0)
== Devices ==
-- iOS 8.1 --
    iPhone 4s (39E8C3F3-70CC-43A2-8517-E946B9932FE4) (Shutdown)
    iPhone 5 (5FC75C61-390C-4C6B-A336-1D990DA9EDA4) (Shutdown)
    iPhone 5s (6150BC95-BE73-4E00-9752-E94492577D1B) (Shutdown)
    iPhone 6 (001BA6CB-3F0B-4AF0-9295-86BCB68B629F) (Shutdown)
    iPhone 6 Plus (426FBE58-01FC-4E67-8274-B6DD0E84EE65) (Shutdown)
    iPad 2 (ED46F7D2-7202-4D8D-A8F6-23C37B838D7A) (Shutdown)
    iPad Retina (D7CED68E-8B2E-4CB3-B420-123F49DCDE7F) (Shutdown)
    iPad Air (CF1E7E9B-04D6-4297-A51B-23F975668074) (Shutdown)
    Resizable iPad (953F0E2E-20F3-4ACA-A1D5-7F46635F369E) (Shutdown) (unavailable, device type profile not found)
    Resizable iPhone (A94468A2-61DE-4216-979D-784C3BF9A003) (Shutdown) (unavailable, device type profile not found)
-- iOS 8.2 --
    iPhone 4s (A50909B5-3AA5-4C50-8645-ECADEE3D0FE7) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPhone 5 (A227FC86-AF24-4B9B-9F90-FAFC0BA28128) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPhone 5s (A1198C9C-21A4-40CA-BC1B-BDB6A1DC3D31) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPhone 6 (6F4F5688-E48D-48D2-9D16-1871DD370067) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPhone 6 Plus (2A781066-4245-4A40-88CD-945169BBC2E2) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPad 2 (0754B8FA-B5BE-4045-A6C3-A1F707EBFCF0) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPad Retina (545E52E8-1D42-4E3B-AC39-A0DBD6A9E39C) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPad Air (09F8C637-B05E-434D-BE2D-A1E43C50E27F) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    Resizable iPad (AB910A9A-D1BB-4179-A12D-60EAA9942F3A) (Shutdown) (unavailable, device type profile not found)
    Resizable iPhone (FCE60C8D-D64D-4C55-BBBD-9B206EE67288) (Shutdown) (unavailable, device type profile not found)
-- iOS 8.3 --
    iPhone 4s (6CF24755-637B-42B0-AE3C-40C77EEFA580) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPhone 5 (16801BB7-20F9-4859-BA68-C393FFE95B8D) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPhone 5s (5E547229-838D-46FF-91F9-46A12F4B11A1) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPhone 6 (ACA7CF51-76D6-4EE4-A571-B46FAC9DF9D8) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPhone 6 Plus (DA693EFC-9E1D-4E3C-8F5F-102F313A94FB) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPad 2 (E3608883-E426-4CB7-9241-982B2A6F58BB) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPad Retina (9EE7FED5-3B40-4007-8CA7-6A038EDAE8B5) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    iPad Air (586629B1-5E94-486E-AECB-520B79B43C5F) (Shutdown) (unavailable, failed to open liblaunch_sim.dylib)
    Resizable iPad (A5F8456F-5D0F-40BF-AD6C-30B4099A8AE8) (Shutdown) (unavailable, device type profile not found)
    Resizable iPhone (03B453C2-09F0-4CDB-B853-AAA7E64A9078) (Shutdown) (unavailable, device type profile not found)
-- iOS 9.0 --
    iPhone 4s (36ACD50A-FD84-43F7-ACD0-B6AD923985B2) (Shutdown)
    iPhone 5 (7EECC2F5-4EF3-4D72-A81E-10CCDD6BEEB3) (Shutdown)
    iPhone 5s (C4C6980D-A8EA-4DA8-AEFD-EF886C631300) (Shutdown)
    iPhone 6 (82C336EF-39DD-4C35-B32B-87E1DB998E78) (Shutdown)
    iPhone 6 Plus (8E80423A-DDDB-4C96-A991-8704CD68B348) (Shutdown)
    iPhone 6s (2131E03F-5B71-4F5B-8040-3FA5DF81A63B) (Shutdown)
    iPhone 6s Plus (8F4BD7BA-D458-45EA-8169-4CDA557E73BE) (Shutdown)
    iPad 2 (390A56B2-3ED5-45DA-9DEE-BF2593344C7B) (Shutdown)
    iPad Retina (2787B64A-C45B-44B5-B6E2-536A981E93A9) (Shutdown)
    iPad Air (C2F62560-685E-4330-84E0-0A4292D82DD8) (Shutdown)
    iPad Air 2 (C581567F-BD76-4D93-87AB-991D0BBCA21B) (Shutdown)
-- iOS 9.1 --
    iPhone 4s (52B52F1E-8AA9-4274-9BBB-BCAB01AF8E7C) (Shutdown)
    iPhone 5 (6FC4609D-0E21-479A-AE12-7F0AC5B6ECEF) (Shutdown)
    iPhone 5s (85789191-746F-44E2-9715-404471373D4A) (Shutdown)
    iPhone 6 (B930FBD2-1B80-400E-BCC8-1B95543957EF) (Shutdown)
    iPhone 6 Plus (17856DBE-05B5-4BCA-972C-491C9F4C25E7) (Shutdown)
    iPhone 6s (9163E76C-F738-4719-A3AD-02FCF51CF1E1) (Shutdown)
    iPhone 6s Plus (93CB4783-AC32-41E6-AA86-6F5668945257) (Shutdown)
    iPad 2 (D789365D-057C-4B45-B3E9-57A62EF5CF78) (Shutdown)
    iPad Retina (B9BCACF3-B587-4016-83F8-BDB2B5C14804) (Shutdown)
    iPad Air (7305401B-B18D-47BB-817B-72C6FAF38023) (Shutdown)
    iPad Air 2 (8C050D55-1CCF-4BA2-AB95-449D58508CE8) (Shutdown)
    iPad Pro (99CE85C9-96B5-453C-8618-383A2090D0E1) (Shutdown)
-- iOS 9.2 --
    iPhone 4s (3FFC3344-F788-4914-BB4C-F7D1CE4DA31A) (Shutdown)
    iPhone 5 (30EAD8AB-43C6-4DF2-B7DB-1F7D2C3ACF94) (Shutdown)
    iPhone 5s (9868A633-05C3-4E18-87C7-D95DE8CF18A0) (Shutdown)
    iPhone 6 (59E045A8-3677-40BD-A014-13AD4384F983) (Shutdown)
    iPhone 6 Plus (CAB74A79-BFF2-48F8-8DEF-C1FA1CD595A1) (Shutdown)
    iPhone 6s (31901D28-6F25-4DF9-A9C8-E6DC7A6941BC) (Shutdown)
    iPhone 6s Plus (01E317B3-D0E6-4ED8-893F-65931C282BEC) (Shutdown)
    iPad 2 (A96B63D0-C1C5-41F4-9AD8-31CF5D078493) (Shutdown)
    iPad Retina (5012448F-9524-4AD4-A6C0-F1CEB2D6C4F9) (Shutdown)
    iPad Air (8DBF4D27-E040-4EAF-A3EB-D3F3A40557B1) (Shutdown)
    iPad Air 2 (94050BE2-F71A-40F2-B05A-C2F3C8E6BBB0) (Shutdown)
    iPad Pro (7D8F58DC-F4EE-4657-88B5-845AF28716A8) (Shutdown)
-- tvOS 9.1 --
    Apple TV 1080p (9F389158-5BB2-4171-A6AA-847017EE4CC6) (Shutdown)
-- watchOS 2.0 --
    Apple Watch - 38mm (7C253F1B-3290-426A-AAD0-5301BD657BFA) (Shutdown)
    Apple Watch - 38mm (5E43AFC1-3DCC-4F69-8079-2449E91AE2FF) (Shutdown)
    Apple Watch - 42mm (5063EC67-7273-444D-A2B9-9CDA8E74E5F6) (Shutdown)
    Apple Watch - 42mm (9B629602-CFDC-488E-BF49-8492CD08BA42) (Shutdown)
-- Unavailable: com.apple.CoreSimulator.SimRuntime.iOS-7-1 --
    iPhone 4s (BC813479-47B9-4AA6-B318-4624A626ACA1) (Shutdown) (unavailable, runtime profile not found)
    iPhone 5 (F199B402-6B6E-4E03-8517-F54005EDB88B) (Shutdown) (unavailable, runtime profile not found)
    iPhone 5s (6EB4584A-4392-457A-981C-BB085118BEA7) (Shutdown) (unavailable, runtime profile not found)
    iPad 2 (651C8FF2-B601-4458-9360-8D9EFBBBD629) (Shutdown) (unavailable, runtime profile not found)
    iPad Retina (85C34512-6145-4210-928A-0C7B628E54D1) (Shutdown) (unavailable, runtime profile not found)
    iPad Air (E8B5A8A0-2780-4AF3-85C0-B075E196DA0C) (Shutdown) (unavailable, runtime profile not found)
-- Unavailable: com.apple.CoreSimulator.SimRuntime.iOS-8-0 --
    iPhone 4s (261DCF2B-D82A-4AB9-96AC-57CA914933FD) (Shutdown) (unavailable, runtime profile not found)
    iPhone 5 (E1A73E97-0FE7-49E4-BF61-BF8A5F120306) (Shutdown) (unavailable, runtime profile not found)
    iPhone 5s (1BEF95A9-6642-48B9-A940-7CA8F8A2051B) (Shutdown) (unavailable, runtime profile not found)
    iPhone 6 (657D5B6C-7BD6-4419-9382-9628D581E17A) (Shutdown) (unavailable, runtime profile not found)
    iPhone 6 Plus (200F62D2-6AAC-4A3A-8912-FE50D2A22D52) (Shutdown) (unavailable, runtime profile not found)
    iPad 2 (3B9A7D06-1289-43A2-8D61-4DF12780D8F3) (Shutdown) (unavailable, runtime profile not found)
    iPad Retina (3DF49BE5-C2C2-4738-B50A-1DE8DE94321A) (Shutdown) (unavailable, runtime profile not found)
    iPad Air (8CAF3A5F-DC21-4E1C-B5BC-280A3B5A5E8E) (Shutdown) (unavailable, runtime profile not found)
    Resizable iPad (B355AA81-B131-4557-9DB2-E07C650A21D9) (Shutdown) (unavailable, runtime profile not found)
    Resizable iPhone (248D3ACE-0514-4526-8A34-5561270E3428) (Shutdown) (unavailable, runtime profile not found)
-- Unavailable: com.apple.CoreSimulator.SimRuntime.iOS-8-4 --
    iPhone 4s (E8785D45-61EE-4230-80A6-5FB7713EB4DC) (Shutdown) (unavailable, runtime profile not found)
    iPhone 5 (4BBE16CF-D716-4E6B-BA1E-01F77060C8C8) (Shutdown) (unavailable, runtime profile not found)
    iPhone 5s (9F93F1ED-A167-4A90-9307-1DD97CEB489C) (Shutdown) (unavailable, runtime profile not found)
    iPhone 6 (C3A6E2B1-0B49-40C7-827C-4C0525554339) (Shutdown) (unavailable, runtime profile not found)
    iPhone 6 Plus (8122D2C4-0046-44B5-853D-88A12B5104AE) (Shutdown) (unavailable, runtime profile not found)
    iPad 2 (C8587B1E-19AE-46E8-BF31-346947484E9A) (Shutdown) (unavailable, runtime profile not found)
    iPad Retina (1C16C650-F657-44B1-BBF8-1F2744A5F666) (Shutdown) (unavailable, runtime profile not found)
    iPad Air (461AED04-9132-469F-8532-875C1F0D3D59) (Shutdown) (unavailable, runtime profile not found)
    Resizable iPad (AE1191E5-C1BC-4E3A-AAC7-410CEDE47491) (Shutdown) (unavailable, runtime profile not found)
    Resizable iPhone (FBB8929F-E5B2-4B28-B4ED-F1232E512BD7) (Shutdown) (unavailable, runtime profile not found)
-- Unavailable: com.apple.CoreSimulator.SimRuntime.iOS-9-3 --
    iPhone 4s (9CBDD031-2C8E-4F3B-AFE7-A070317C04E3) (Shutdown) (unavailable, runtime profile not found)
    iPhone 5 (B311A66E-4BCB-4E94-A5F0-8EB619231516) (Shutdown) (unavailable, runtime profile not found)
    iPhone 5s (1F53F6C8-8093-40F7-9377-0BDD26F8ADF7) (Shutdown) (unavailable, runtime profile not found)
    iPhone 6 (3B6FDA48-A016-4744-9F1D-988FC5060DEF) (Shutdown) (unavailable, runtime profile not found)
    iPhone 6 Plus (1EC35C0A-847C-4158-91CA-03EDD3F716D1) (Shutdown) (unavailable, runtime profile not found)
    iPhone 6s (20ACF134-0A80-420B-A833-663243CC20DD) (Shutdown) (unavailable, runtime profile not found)
    iPhone 6s Plus (FDFE1228-B1D6-4A69-AD8D-9ED8F3936998) (Shutdown) (unavailable, runtime profile not found)
    iPad 2 (1C7C09AD-9695-45AF-A01B-64B4CA14B3C9) (Shutdown) (unavailable, runtime profile not found)
    iPad Retina (CF2D785A-3D92-41E1-B550-803DB65B9336) (Shutdown) (unavailable, runtime profile not found)
    iPad Air (74F3E623-61B6-4555-A9EE-01877AED9460) (Shutdown) (unavailable, runtime profile not found)
    iPad Air 2 (2502B30F-55EE-4D18-9198-86D0BD515E39) (Shutdown) (unavailable, runtime profile not found)
    iPad Pro (AB8A6D8E-5A68-464C-98C0-5122A2466957) (Shutdown) (unavailable, runtime profile not found)
-- Unavailable: com.apple.CoreSimulator.SimRuntime.tvOS-9-0 --
    Apple TV 1080p (B3D091C1-8B4E-4665-B674-36D1EF9EA464) (Shutdown) (unavailable, runtime profile not found)
-- Unavailable: com.apple.CoreSimulator.SimRuntime.tvOS-9-2 --
    Apple TV 1080p (AA764E6E-4FE5-446E-8ECE-1CE22944FE92) (Shutdown) (unavailable, runtime profile not found)
-- Unavailable: com.apple.CoreSimulator.SimRuntime.watchOS-2-2 --
    Apple Watch - 38mm (47480D51-BA88-4F3B-B9C3-A808048F7275) (Shutdown) (unavailable, runtime profile not found)
    Apple Watch - 42mm (81F20071-84EB-4E3F-808D-4A6659F69557) (Shutdown) (unavailable, runtime profile not found)
== Device Pairs ==
B930D21F-B334-4578-B2A8-6022D1E2E772 (disconnected)
    Watch: Apple Watch - 38mm (7C253F1B-3290-426A-AAD0-5301BD657BFA) (Shutdown)
    Phone: iPhone 6 (82C336EF-39DD-4C35-B32B-87E1DB998E78) (Shutdown)
F90DD288-E8FE-4B56-822A-7A8A8BF642A8 (disconnected)
    Watch: Apple Watch - 38mm (5E43AFC1-3DCC-4F69-8079-2449E91AE2FF) (Shutdown)
    Phone: iPhone 6s (31901D28-6F25-4DF9-A9C8-E6DC7A6941BC) (Shutdown)
2298CD81-8123-470B-B2C9-60E78C513982 (disconnected)
    Watch: Apple Watch - 42mm (5063EC67-7273-444D-A2B9-9CDA8E74E5F6) (Shutdown)
    Phone: iPhone 6 Plus (8E80423A-DDDB-4C96-A991-8704CD68B348) (Shutdown)
6E28608E-869C-4640-B65C-423094865495 (disconnected)
    Watch: Apple Watch - 42mm (9B629602-CFDC-488E-BF49-8492CD08BA42) (Shutdown)
    Phone: iPhone 6s Plus (01E317B3-D0E6-4ED8-893F-65931C282BEC) (Shutdown)
E3DC429A-413A-4940-9A63-D3DBA9AE87A7 (unavailable)
    Watch: Apple Watch - 38mm (47480D51-BA88-4F3B-B9C3-A808048F7275) (Shutdown)
    Phone: iPhone 6s (20ACF134-0A80-420B-A833-663243CC20DD) (Shutdown)
409823CC-DAE0-40A8-B0A9-69E6DF48A921 (unavailable)
    Watch: Apple Watch - 42mm (81F20071-84EB-4E3F-808D-4A6659F69557) (Shutdown)
    Phone: iPhone 6s Plus (FDFE1228-B1D6-4A69-AD8D-9ED8F3936998) (Shutdown)

Thanks, I see the issue now. Rome is not constraining the simulator search to the deployment target. This leads to it finding an 8.1 simulator in this case, but that is incompatible with the 9.0 deployment target.

Ok. Glad I was able to help find an actual bug.
Can you shed any light on the plugin errors discussed above?

You can find some info about that here http://buegling.com/blog/2014/6/5/xcode-6-plugins-and-you — basically plugin authors have to update their plugins for each new version of Xcode or they won't get loaded.

Ok, but one of the plugins listed is cocoapods!
And, I've built xcode projects on the command line before and not had this issue. Is Rome actually stopping the build because of these errors? (I can't know, as the simulator errors are definitely stopping my build). Odd that it would if xcodebuild doesn't.

Ah, this is not CocoaPods the tool, but an Xcode plugin for it, possibly https://github.com/kattrali/cocoapods-xcode-plugin. Those errors won't affect the build.

The actual bug with simulator search should be fixed by ac49307af83c8a5fc64fb4709b09a79da391a80e, thanks for reporting this, @ExoticObjects!

Shipped as 0.4.2

Sweet. After running gem update cocoapods-rome this worked. Thanks!


Add ability to test method before saving job

Is your feature request related to a problem? Please describe.
Add the ability to test method before saving a job in django-admin

Does not allow to save job if callable is invalid


[FLINK-10022][network][metrics] add metrics for input/output buffers

What is the purpose of the change
For debugging network issues, it would be nice to not only have the number of received/sent records and bytes but also the number of buffers, e.g. to identify low buffer fill rates which cause some overhead (there's a trade-off between sending full buffers and sending with low latency). This PR adds such metrics.
Brief change log

add

Verifying this change
This change added checks to existing tests such as:

TaskIOMetricGroupTest
SubtaskCurrentAttemptDetailsHandlerTest
SubtaskExecutionAttemptDetailsHandlerTest
JobVertexDetailsInfoTest
JobVertexTaskManagersInfoTest
JobDetailsInfoTest
SubtaskExecutionAttemptDetailsInfoTest
I also verified the metrics manually in Flink's web UI

Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? docs, JavaDoc

change log doesn't appear to be complete


Separate seed dictionary

Separate seed dictionary (mecab-ipadic-2.7.0-20070801) CSV files from repo.
Instead, we use mecab-ipadic-seed.

Coverage decreased (-0.01%) to 87.942% when pulling 276e67226cc476ff8341b87124781673fcbacb87 on separate-seed-dic into efc27e40e9197e48334d3081b797d6f2b77d2cea on master.


Let make choose amount of parallelization threads

Using 'make -j' without a certain number will leave the decision how
many threads to use to make. Typically, make will extract this from the
system's CPU information and choose the amount of CPU threads. (This
should then give the same result as using 'make -j$(nproc)'.)
Fixes #28
Change-Id: I030b39e647b758781a099c09aa05566bbbc233c2
Signed-off-by: Joakim Roubert<EMAIL_ADDRESS>

I tend to reject this PR because it is breaking our CI system due to too much RAM consumption.


UI Breaks with Nginx proxy_pass

Gitea version (or commit ref): 1.3.2
Git version: 2.7.4
Operating system: Ubuntu 16.04
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
Using a basic proxy_pass in Nginx breaks asset paths instantly. Fresh install with proxy_pass URL specified doesn't work.
Updating app.ini doesn't work
Proxy pass settings:
location / {
		proxy_pass http://[ip address]:3000;
		proxy_set_header Host $host;
    		proxy_set_header X-Real-IP $remote_addr;

		# First attempt to serve request as file, then
		# as directory, then fall back to displaying a 404.
		try_files $uri $uri/ =404;
	}

App works without Nginx on 3000, but that's kind of useless. I'm afraid it will break using a valid domain name.
Screenshots

This is the location block that I'll use:
        location / {
                proxy_pass http://unix:/var/run/gitea/gitea.sock;
                proxy_set_header Host $host;
        }

don't know if the try_files is actually necessary?

Please checkout our guide for using reverse proxies: https://docs.gitea.io/en-us/reverse-proxies/#using-nginx-as-a-reverse-proxy
Do the problems occur still after following our guide?

@niclashoyer maybe you can also contribute to https://docs.gitea.io/en-us/reverse-proxies/#using-nginx-as-a-reverse-proxy when using unixsock protocols.

My config is very much the same but I did not specify the server name and you might be right about the try methods; they’re in their by default and I’ve only ever had to add to them.
I’ll give this a try later.
Did not realize you had a special guide but to be honest I’ve never had to use special configuration for proxying a given web app from its port to port 80.
I build Nodejs apps and haven’t experienced this problem, but not familiar with Go enough to understand if it’s somehow different.

@methodbox You could also set the port of gitea to 80 or 433 (if you prefer https) but this may require root.

Here is a sample configuration that @thehowl posted to our Forum: https://discourse.gitea.io/t/call-gitea-as-a-subdomain-of-nginx/266/2

@JonasFranzDEV That’s a terrible recommendation from a security standpoint.
Your application should never also be it’s own web server, let alone be allowed to handle HTTPS transactions.
This coupled with the idea that you suggested root being the owner of the process makes me question the technical knowledge behind this project.
I appreciate that you may be a qualified Go developer but your grasp of server administration may be lacking if you’d even consider that response as one to be taken seriously.

@methodbox I don't see your point why a reverse proxy with no additional configuration should make a web application more secure. The only advantage might be that you could hide your gitea instance from the public. In addition you so called web server will be started also as root because no process could use a port <1024 without root permissions. I don not recommend running gitea as root but you could use other solutions like running gitea via docker which might be easier for not experienced user.
This project comes to you for free and the support many users are giving to you are also free.

To bind to a port below 1024, you can use setcap on Linux: sudo setcap 'cap_net_bind_service=+ep' /path/to/gitea.

The reverse proxy is only part of the few steps to add additional security but an application should never run as its own web server, if nothing else.
Nginx is definitely going to be able to handle more requests than the Go service daemon, for example.
There’s also the benefit of something that can manage all kinds of different insecure header requests, block POST requests by default and the list goes on.
Your app server should never be your web server. There’s plenty of info out there in the Nodejs world that you can google if you want to learn more.
That said, I missed a step in my Nginx server block - server_name - which seems to have resolved the issue.

Hey, I am having the same issue. Can you guys help me?

@MiguelNdeCarvalho perhaps this page could help you: https://docs.gitea.io/en-us/reverse-proxies/


implies endpoint of RPC server returns unsimplified implication

Currently, when I call the implies endpoint, it returns three things:

Substitution (if the implication holds, witnessing substitution).
Predicate (if the implication holds, witnessing predicate).
Implication (as far as I can tell, just antecedent #Implies consequent).

The last one seems fairly useless as is to me, because it just returns literally antecedent #Implies consequent, which I can construct myself if I want. It would be more useful if it returned the minimized/simplified implication, which would be #Top when the implication holds, #Bottom when it doesn't, and some simplified value otherwise.
Right now pyk emits a bunch of warnings because of this non-trivial implication being passed back. Not sure what we should be doing with it? Should we just drop it completely?

Can you provide an example for testing purposes? We can probably process that implication in several different ways and I'd like to know what you're looking for exactly.

Discussed this with Jost, and the pyk library will just ignore that third parameter that is passed back more than it is (turn it from warning to info/debug output).


Code reference

Types of changes

Changes visible to users:

[x] Contributing Guidelines (prefix: contrib - any improvements to documentation content for contributors - see Contributing to Tasks)

Internal changes:

[x] Infrastructure (prefix: chore - examples include GitHub Actions, issue templates)

Description

Add development dependency on the TypeDoc tool
Add new yarn script:

yarn code-docs

Add new page to the contributing site, showing how to use and maintain this facility:

Generating documentation of the code
There is a screenshot of this page below...

Motivation and Context

Make it much easy to see the class hierarchy
Make it easy to search the source code and navigate around it

How has this been tested?

Viewing the generated docs in Chrome
Viewing the new Contributing page in Obsidian

Screenshots (if appropriate)
The new Contributing page shows what the generated docs look like:

Checklist

[x] My code follows the code style of this project and passes yarn run lint.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] My change has adequate Unit Test coverage.

Terms

[x] My contribution follows this project's contributing guide
[x] I agree to follow this project's Code of Conduct

Hi @ilandikov This might be of interest...


useRuntimeConfig is not defined

Environment
Node version: 18.16.1
{
  "name": "nuxt-auth",
  "private": true,
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare",
    "lint": "eslint --max-warnings 0 .",
    "typecheck": "nuxt typecheck",
    "start": "NODE_ENV=production node .output/server/index.mjs"
  },
  "devDependencies": {
    "@nuxt/devtools": "latest",
    "@nuxtjs/color-mode": "^3.3.0",
    "@nuxtjs/eslint-config-typescript": "^12.0.0",
    "@nuxtjs/google-fonts": "^3.0.1",
    "@nuxtjs/tailwindcss": "^6.8.0",
    "@prisma/client": "^5.0.0",
    "@types/bcryptjs": "^2.4.2",
    "@types/node": "^20.4.2",
    "eslint": "^8.45.0",
    "nuxt": "^3.6.3",
    "nuxt-icon": "^0.4.2",
    "prisma": "^5.0.0",
    "typescript": "^5.1.6",
    "vue-tsc": "^1.8.5"
  },
  "dependencies": {
    "@auth/core": "^0.9.0",
    "@auth/prisma-adapter": "^1.0.1",
    "@hebilicious/authjs-nuxt": "^0.1.5",
    "@types/jsonwebtoken": "^9.0.2",
    "@vuelidate/core": "^2.0.3",
    "@vuelidate/validators": "^2.0.3",
    "bcryptjs": "^2.4.3",
    "jsonwebtoken": "^9.0.1"
  }
}

Reproduction
Here is the error that I got in my console:
[nuxt] [request error] [unhandled] [500] useRuntimeConfig is not defined
  at getServerOrigin /.nuxt/dev/index.mjs:842:24` and also at `at getServerToken .nuxt/dev/index.mjs:926:19

Describe the bug
I am trying to get the JWT, I have followed the instruction as written in the docs.
In my /server/jwt.get.ts file I have the following code:
import { authOptions } from "../api/auth/[...]"
import { getServerSession, getServerToken } from "#auth"
export default defineEventHandler(async (event) => {
  const session = await getServerSession(event, authOptions)
  const jwt = await getServerToken(event, authOptions)
  return { session, jwt }
})

but I get the following error in my console:
[nuxt] [request error] [unhandled] [500] useRuntimeConfig is not defined  2:34:39 AM
  at getServerOrigin

here is the code that I have defined in the /server/api/auth/[...].ts file:
import GithubProvider from "@auth/core/providers/github";
import GoogleProvider from "@auth/core/providers/google";
import type { AuthConfig } from "@auth/core/types"
import { NuxtAuthHandler } from "#auth";
import { PrismaAdapter } from "@auth/prisma-adapter";
import { PrismaClient } from "@prisma/client";
const prisma = new PrismaClient();
const runtimeConfig = useRuntimeConfig()

export const authOptions: AuthConfig = {
    adapter: PrismaAdapter(prisma),
    secret: 'fghjgsdfjhktrygjndfbvvsdvbtrhgfg',
    providers: [
        GithubProvider({
            clientId: runtimeConfig.GITHUB_CLIENT_ID,
            clientSecret: runtimeConfig.GITHUB_CLIENT_SECRET
        }),

        GoogleProvider({
            clientId: runtimeConfig.GOOGLE_CLIENT_ID,
            clientSecret: runtimeConfig.GOOGLE_CLIENT_SECRET
        })
    ]
}

export default NuxtAuthHandler(authOptions, runtimeConfig)

Additional context
Here is the error that I got in my console:
[nuxt] [request error] [unhandled] [500] useRuntimeConfig is not defined
  at getServerOrigin /.nuxt/dev/index.mjs:842:24

Logs
Here is the error that I got in my console:
[nuxt] [request error] [unhandled] [500] useRuntimeConfig is not defined
  at getServerOrigin /.nuxt/dev/index.mjs:842:24` and also at `at getServerToken .nuxt/dev/index.mjs:926:19

Fixed in https://github.com/Hebilicious/authjs-nuxt/releases/tag/v0.1.6


Add serde support for networks.

Add serde support for learnable parameters.
Add an example of training a network, saving it and loading it.

Will review asap.

I can add some more tests,  the sample works as part of one but I wanted to check the rest of it was ok first.

LGMT, should I merge?

LGTM, should I merge?

I've just fixed some warnings I had to make some minor changes to a few things in the core library to get the tests to run, so you may want to review them.


METRON-2195 lazy logging

Contributor Comments
This PR illustrates a proof on concept for a logging wrapper that supports lazy argument evaluation.   Lazy parameter evaluation technique is automatically supported in Java 8 native logging (which we don't use), and log4j 2.4+ (which we appear to use via SLF4J wrappers).
Unfortunately the lazy parameter evaluation provided by log4j 2.4+ is not currently exposed in the interfaces provided by the current SLF4J logging framework (support is scheduled for release with SLF4J 2.x)  So to support lazy evaluation while maintaining use of the current SLF4j logging libraries a wrapper is required.
Rationale for lazy parameter evaluation
Even though the logging framework will not construct a string unless the logging level indicates a log message will be needed, all parameter arguments are still evaluated by the JVM as part of the standard java parameter passing process.
Lazy parameter evaluation is a useful technique for when some arguments are very expensive to calculate (eg. Serialising a collection object into a JSON string).   When disabled logging calls are deeply nested under multiple levels of iteration, then there can be a real hidden cost to this unneeded parameter evaluation overhead.
This PR illustrates a technique of utilising a logging wrapper that supports lambdas as logging parameters. Typical scenarios where this could be used include code scenarios such as:

LOG.trace("Printed result of an expensive operation: {}", expensiveOperation().toString())

Where expensiveOperation().toString is executed regardless of what logging level is enabled.
The suggested code to use with this wrapper would be

private static final LazyLogger LOG = LazyLoggerFactory.getLogger(MethodHandles.lookup().lookupClass());
LOG.trace("Expensive operation only if trace logging enabled: {}", () -> expensiveOperation().toString()

As an example of usage
metron-platform/metron-writer/metron-writer-storm/src/main/java/org/apache/metron/writer/hdfs/HdfsWriter.java
has been updated to utilise this wrapper module.
The general guidance would be that any logging use that involves anything more than extremely basic string construction should use the lambda versions of the logging functions for performance reasons.
Error-level logging would be exempt from the requirement to use lambda versions of the logging functions due to error logging usually never being disabled, and thus no performance benefit is likely to come from forcing lazy parameter evaluation in this case.
If the lazy evaluation logging concept is approved I will add some unit testing before finalising the PR.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[ ] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[ ] Have you included steps or a guide to how the change may be verified and tested manually?

[ ] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh

[ ] Have you written or updated unit tests and or integration tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

[ ] Have you ensured that any documentation diagrams have been updated, along with their source files, using draw.io? See Metron Development Guidelines for instructions.

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

Can you rebase this on master?

I would like to see the results from an extended version of @mmiklavc 's performance test as applied after this change, IE a test using the lazy logger.
I think after the initial warm up, the times shouldn't be bad.

I like this a lot,  I think you should continue with the PR.
If you are going to limit the scope of this pr, please state that in the PR.

Rebasing caused a sea of errors. It was easier just to regenerate a new pull request.


CAS-2250 Registered services field lengths at 255

Fixes #2250

[] Changes the column length of String fields back to 255.
[] Removes the column length of Boolean fields.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

I started implementing MFA and the CAS management application an ran into more classes that specify illegal field lengths:
org.apereo.cas.adaptors.gauth.GoogleAuthenticatorRegistrationRecord
org.apereo.cas.services.OidcRegisteredService
org.apereo.cas.support.events.dao.CasEvent
org.apereo.cas.support.saml.services.SamlRegisteredService
org.apereo.cas.trusted.authentication.api.MultifactorAuthenticationTrustRecord


kvm.sh does not run correctly on Ubuntu/Linux Mint

Hi there,
I discovered today that the kvm.sh file does not execute correctly on debian based distros (i.e. Ubuntu/Mint). This is because the default shell for these systems is dash instead of bash.
I was able to get it running by removing the requirement for dash and revert to bash by following this guide: http://www.bloovis.com/wordpress/?p=163
It would be good to see this mentioned under the install notes for Linux, as I spent quite some time before I figured this out, and it was actually breaking my desktop session with the command added to the .profile file running on login, which was failing.
Cheers,
Justin

This issue is being closed because it has not been updated in 3 months.
We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.


[BUG] OpenShift Local start error: Error: failed to expose port <IP_ADDRESS>:2222

General information

Windows
Hypervisor: Hyper-V
Did you run crc setup before starting it (Yes/No)? N/A - extension does not have this option
Running CRC on: Laptop

CRC version
# Put `crc version` output here

CRC status
# Put `crc status --log-level debug` output here

CRC config
crc config view
- consent-telemetry                     : no

Host Operating System
systeminfo

Host Name:                 DESKTOP-BDDQV3I
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.19045 N/A Build 19045
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Ondrej
Registered Organization:
Product ID:                00330-80000-00000-AA049
Original Install Date:     2/10/2023, 10:15:11 AM
System Boot Time:          12/14/2023, 1:48:22 PM
System Manufacturer:       LENOVO
System Model:              20LAS3NJ0U
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 142 Stepping 10 GenuineIntel ~1910 Mhz
BIOS Version:              LENOVO N27ET29W (1.15 ), 8/8/2018
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             cs;Czech
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague
Total Physical Memory:     32,383 MB
Available Physical Memory: 25,663 MB
Virtual Memory: Max Size:  37,247 MB
Virtual Memory: Available: 30,532 MB
Virtual Memory: In Use:    6,715 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\DESKTOP-BDDQV3I
Hotfix(s):                 19 Hotfix(s) Installed.
                           [01]: KB5032005
                           [02]: KB5028853
                           [03]: KB5011048
                           [04]: KB5011052
                           [05]: KB5012170
                           [06]: KB5015684
                           [07]: KB5020683
                           [08]: KB5033372
                           [09]: KB5014032
                           [10]: KB5016705
                           [11]: KB5023794
                           [12]: KB5025315
                           [13]: KB5026879
                           [14]: KB5028318
                           [15]: KB5028380
                           [16]: KB5029709
                           [17]: KB5031539
                           [18]: KB5032392
                           [19]: KB5032907
Network Card(s):           4 NIC(s) Installed.
                           [01]: Intel(R) Ethernet Connection (4) I219-LM
                                 Connection Name: Ethernet
                                 Status:          Media disconnected
                           [02]: Intel(R) Dual Band Wireless-AC 8265
                                 Connection Name: Wi-Fi
                                 DHCP Enabled:    Yes
                                 DHCP Server:     <IP_ADDRESS>
                                 IP address(es)
                                 [01]: <IP_ADDRESS>
                                 [02]: fe80::8b80:6dfd:d1d0:dbd3
                           [03]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (Default Switch)
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: <IP_ADDRESS>
                                 [02]: fe80::6124:7e32:a7a9:3c7d
                           [04]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (WSL)
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: <IP_ADDRESS>
                                 [02]: fe80::7268:395a:1d25:d24
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Steps to reproduce

Install extension into podman desktop
Install CRC via PD
When asked about preset, choose openshift
Let is finish, pass through the error (you needed to reboot) - ignore that, reboot machine
Start PD again
Initialize and start Openshift local
There is an error

Expected
Started Openshift local resource
Actual
Error.

Logs
VM5:2 main ↪ [openshift-local] Error: failed to expose port <IP_ADDRESS>:2222 -> <IP_ADDRESS>:22: listen tcp <IP_ADDRESS>:2222: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.

    at DaemonCommander.start (C:\Users\Ondrej\.local\share\containers\podman-desktop\plugins\quayioredhatdeveloperopenshiftlocalextension\dist\extension.js:9367:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async startCrc (C:\Users\Ondrej\.local\share\containers\podman-desktop\plugins\quayioredhatdeveloperopenshiftlocalextension\dist\extension.js:25386:24)
    at async createCrcVm (C:\Users\Ondrej\.local\share\containers\podman-desktop\plugins\quayioredhatdeveloperopenshiftlocalextension\dist\extension.js:26661:24)
    at async Object.initialize (C:\Users\Ondrej\.local\share\containers\podman-desktop\plugins\quayioredhatdeveloperopenshiftlocalextension\dist\extension.js:26637:13)
    at async OK.initializeProvider (C:\Users\Ondrej\AppData\Local\Programs\podman-desktop\resources\app.asar\packages\main\dist\index.cjs:53:74943)
    at async C:\Users\Ondrej\AppData\Local\Programs\podman-desktop\resources\app.asar\packages\main\dist\index.cjs:345:19649
    at async WebContents.<anonymous> (node:electron/js2c/browser_init:2:88640)
console.<computed> @ VM5:2

Before gather the logs try following if that fix your issue - No

This is the result of podman-machine and crc fighting over the same port (2222). It's tracked in https://github.com/crc-org/crc/issues/3855


New helm plugin - official doc

Hello!
I create a new helm v3 plugin to help the community to fetch values from an older release.  helm-val
I would like to know what are the criteria to add a plugin to the official documentation?
Thanks

Hi @HamzaZo. Plugins and other third party projects can be listed under the Related Projects section. Please feel free to submit a PR to the helm-www repository.
https://github.com/helm/helm-www
Hope this helps.


I can not access any services from LAN

I am not sure if this is a bug with ansible-nas, your fork or something else.
But my issue is, I cant access the hemdall dash or sonarr in my SBC after installing this from your fork, I since then switched to the original but still no luck.
I can access the services from the SBC itself when logged in via ssh. So I can login with ssh<EMAIL_ADDRESS>I also just started a test webserver with python python3 -m http.server and I can access from LAN as well on http://<IP_ADDRESS>:8000/
So I am clueless why http://<IP_ADDRESS>:8989 does not work. Something about docker? Any ideas, any way I can debug this? I checked for stuff listening on ports and it seems all fine. And again with w3m (text browser) I can access services.

Hello.
I just did a test to install Heimdall on an Ubuntu 22.04.2 LTS VM and I can access it no problem over LAN on http://<IP_ADDRESS>:10080. So I would rather look for something on your host machine: firewall, permissions, docker, etc.

@anarion80 I am just coming back to this, I still have this issue. What I did was install Ubuntu 22.04 server directly on Zimaboard and during the server-setup it asked me to asked some common software and I picked Docker. So Docker was already installed b4 I ran any Ansible playbook on it.
Maybe that has something to do with it? Any hint what I may need to configure differently? I never used Docker.


Add Envelope Support

This PR implements the newer envelope format https://develop.sentry.dev/sdk/envelopes/#data-model for events only.
This is a stepping stone and a blocker to implementing transactions, attachments, and other features that are requested in #426, and #479.

Hi @mitchellhenke! Does it mean that Sentry v9.1.2 would no longer be supported? Since some users are stuck on 9.1.2 due to infrastructure complexity of the newer versions, would it be possible to keep the old API?

@syfgkjasdkn That's a good question, the change here is probably sufficient to be considered breaking. Maintenance of older major versions has typically been limited, though not dropped entirely.


chore(main): release 0.8.5

:robot: I have created a release beep boop
0.8.5 (2023-12-08)
Bug Fixes

add yes compliance (5d533db)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/kevinah95/hacienda/releases/tag/v0.8.5 :sunflower:


make macro expansion errors more helpful

The code is not indented properly. Have you tried using c.abort() instead of throwing an exception?

Right, fixed.

Not exactly much more helpful, but I suppose better than an AssertionError. Thanks!


docs(api): new and updated Tutorial protocol files

Overview

Update the Python protocol files linked from the Tutorial.
Test Plan

Verify that all linked protocols analyze in Opentrons App
~Verify that all linked protocols pass opentrons_simulate (when compatible with 2.15)~ I think it's OK to merge without this — protocols analyze and show expected Run Preview in edge app.
Compare code in snippets to protocol files and ensure no discrepancies

Note: Links to new Flex protocols will be broken in the sandbox until this merges. Manually check that the URLs match the file names.

Changelog

Added single- and multi-channel protocols for Flex
All protocols specify API level of 2.15
OT-2 protocols now instantiate pipette as left_pipette

Review requests

Check that my protocols work outside of my own system.
Check that my code represents the words and other code on the Tutorial page in the sandbox.
Risk assessment

v low. docs and non-executed code.

merged with Joe's suggestion. 🚀


use real systemd

Is there anything against using real systemd instead of your replacement ?
I have a working setup here: https://github.com/maci0/docker-systemd-unpriv

No, nothing against that. It's actually my long-term plan. There are some changes coming to the EL images WRT systemd so I'd prefer for them to land and use that as a basis for the work.

I have  freeipa-server and freeipa-client based on my systemd-unpriv container working here as well. It requires almost no custom code.
I think the most crucial part you implemented is the volume-test stuff. Might look into porting that to my solution as well, was it complete or did it still lack some stuff?
Do you think it is applicable to split up IPA into its components and have a docker container for each ?

I have freeipa-server and freeipa-client based on my systemd-unpriv container working here as well. It requires almost no custom code.

I'll be happy to take a look / review pull request.

I think the most crucial part you implemented is the volume-test stuff. Might look into porting that to my solution as well, was it complete or did it still lack some stuff?

The main reason why I did not push the volume-based approach as the main branches is, we need to get the upgrades fleshed out. With containers, it's easy to create IPA 3.3 image and start it and have the volume populated with 3.3 data and configuration, and then create 4.0 or 4.1 image and run new container, with the new code and old data. That's actually what I'm looking into right now.

Do you think it is applicable to split up IPA into its components and have a docker container for each ?

Container is basically separate machine from other service's point of view. Unless the other components know that their peers might not be on the same host (often Unix socket away) and get to assume they can be remote, it's likely to be hard to do. Also, the ipa-server-install and other utilities expect all configured components to be on the same host, which in case of containers means in the same container.
Many of the components also share configuration (like Kerberos client libraries) which would need to be solved somehow. That's why I did not attempt to do any splitting. It might be a useful thing to do and it might better fit the container paradigm but the effort should not be container-specific -- it should be about "make it possible for dirsrv (or other component X) to run on separate host and have that separate host configurable and have the rest of the system understand that configuration", not "move dirsrv (or other component X) to separate container". If you do the first, you will get the second for free. If you do the second, you will likely need to redo a lot of the work that went into the installer code.

@adelton
i just pushed my implemetation up here: https://github.com/maci0/docker-freeipa-server https://github.com/maci0/docker-freeipa-client
its nowhere near as complete as yours. lots of stuff is still hardcoded. but it demonstrates how easy it can be :)

Thanks, I will take a look.

how do the official RPM packages handle version upgrades ?
I suppose there is some post upgrade script which updates the database etc. Not sure if it would handle downgrades as well.

I suppose there is some post upgrade script which updates the database etc.

Right. But with containers, you do not run the rpm -U operation. Yes, I'm actually looking at the rpm scriptlets to run them.

it doesnt seem to do a let except of running
/usr/sbin/ipa-ldap-updater --upgrade --quiet >/dev/null || :
/usr/sbin/ipa-upgradeconfig --quiet >/dev/null || :```
and stopping ipa_kpasswd.service before
im not sure if it is applicable to simply run those commands every time and hope they know that the data doesnt need to be updates

The latest master and derived branches now support volumes, and with that upgrades to newer IPA versions. You might want to test that.
As for native systemd/systemd-container, I'm hitting multiple issues when attempting to use it across various OS versions (for example https://bugzilla.redhat.com/show_bug.cgi?id=1201657), so it is not a high priority at the moment.
I'm leaving this issue open for now.

Please check the master-systemd branch. It container systemd-based installation.

The systemd-based setup is now in master.


Fix typo in function TS_VERIFY_CTS_set_certs()

(I'm pretty sure, that) there's a typo in TS_VERIFY_CTS_set_certs()'s function name. It should be TS_VERIFY_CTX_set_certs().
I know that this change is an API break, but eventually it's necessary.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

A better solution would be to create a new function TS_VERIFY_CTX_set_certs(), and change  TS_VERIFY_CTS_set_certs() to call it. This part of the fix should be backported to 1.1.1.
Additionally, in master only, we should deprecate TS_VERIFY_CTS_set_certs(). Optionally, in master only, we could additionally make it a macro for TS_VERIFY_CTX_set_certs().

After your reply I changed the pull request. Now one commit adds an additional function TS_VERIFY_CTX_set_certs() and changes TS_VERIFY_CTS_set_certs() to call it. The second commit deprecates TS_VERFIY_CTS_set_certs().

How can the function be marked as deprecated? When I'm using the macro DEPRECATEDIN1_1_1(...) some CI checks fail.

As per the discussion above we should only be doing the deprecation in master. In master you need to use DEPRECATEDIN_3 (since the next version of OpenSSL will be 3.0).

@mattcaswell: I just don't know what mean by "deprecate it in master"...how can I change something directly on master? Can you merge this PR then?

Rebased to be mergeable.

@mattcaswell: I just don't know what mean by "deprecate it in master"...how can I change something directly on master? Can you merge this PR then?

You should use DEPRECATEDIN_3  to mark TS_VERIFY_CTS_set_certs in include/openssl/ts.h as deprecated.

@InfoHunter : I've done this, but now some builds fail. That's the problem I mentioned above.

Then you probably need to fix the calling to TS_VERIFY_CTS_set_certs inside OpenSSL's own code, say the ones in apps/...
From my understandings, after the deprecated flag is added to the function declaration, it's time for the users who build the application to handle the warnings/errors while compiling. The CI failures are because of a stricter compilation has been used by OpenSSL.

Note this line in the CI's log: cc1: all warnings being treated as errors, so I think someone build his code with the deprecated function, only a warning is generated but not mandated to not call the deprecated function.

@InfoHunter : Okay thanks, now it has worked.

Ping?

I agree. It is just to request documentation from somebody who adds a new feature. But requesting it from someone who only fixes a bug or just a typo is disproportionate IMHO (OpenSSL committers excluded from this rule).

Then how about someone opens a new PR including the documentation and claim that the new PR is based on this PR. (I recall we have done such things before...)

I opened a new PR #9838 to add the document. Please resolve the conflict in this PR and we can proceed, @Iniesta8 . Thanks!

@InfoHunter Done. Ready to merge.

@Iniesta8 , approved. Ping @mattcaswell and @levitte . (I think they are busy on releasing new versions ;-)

Ping @openssl/committers for a second review.

Ping again?

@Iniesta8 your pull request has been inactive for a while. Do you still intend to finish it? Or did your discussion discourage you?
I still think we can proceed along suggestion https://github.com/openssl/openssl/pull/9472#discussion_r323573205, where the 1.1.1 part is optional. If you want to fix it for master and 1.1.1, then it would probably be best to make create a separate pull request for 1.1.1. Otherwise, you can just skip the 1.1.1 part.
@mattcaswell what do you think? Is it worth fixing in 1.1.1?

How can I declare the macro as deprecated? DEPRECATED_IN_3(...) doesn't work for macros, right?

How can I declare the macro as deprecated? DEPRECATEDIN_3(...) doesn't work for macros, right?

Just guard it with an # if !OPENSSL_API_3.
https://github.com/openssl/openssl/blob/f246f54f18d380791cc60be4aea0fbc7253a9a20/include/openssl/dtls1.h#L27-L30
Note: You can set the api level to 3 on master by passing the --no-deprecated  (or --api=3.0.0) switch to the configure command. The former switch is easier to remember and always chooses the highest available api level.

We still need @openssl/omc re-approval.

Since we had five approvals, I took the freedom to dismiss the two outdated ones and keep only the three fresh ones.

Merged to master as 1af26e53bce7f075e27e2fa6a78764fa6620b8ab. Thank you @Iniesta8 for your patience and congratulations to your first successful contribution! Even more since it was less trivial than expected. ;-)


feat: Processing tasks in Arq through Redis

close https://github.com/keephq/helm-charts/issues/43

@Matvey-Kuk general comment - try to move all hardcoded values to templated values (e.g. "1gi" in redis)


Displaying test view results in 500 error

Bug description
Unsure if it's again me or if that's also others. At any rate, viewing test page results in 500 with
Template error:
In template /app/dojo/templates/base.html, error at line 703
   expected str, bytes or os.PathLike object, not NoneType
   693 :         }
   694 :
   695 :         function get_alerts() {
   696 :             $('.dropdown-alerts').html('

');
   697 :             $.get("{% url 'alerts_json' %}?limit=12", function (data) {
   698 :                 $('.dropdown-alerts').empty();
   699 :                 $.each(data, function(i, elem) {
   700 :                   var titleField = elem.fields.title ? elem.fields.title : elem.fields.description;
   701 :                   var display_title = titleField.length < 50 ? titleField : jQuery.trim(titleField).substring(0,50).trim(this) + '...';
   702 :                   var description = elem.fields.description
   703 :                   v ar display_description = description  ? description.length < 100 ? description : jQuery.trim(description).substring(0,100).trim(this) + '...': ''
   704 :                   var dropdown_alert = "alert-list" + i;
   705 :                   $('.dropdown-alerts').append('

' +
   708 :                                                htmlEscape(elem.fields.source) + '

');
   709 :                   $("#" + dropdown_alert).text(display_title);
   710 :                 });
   711 :                 $('.dropdown-alerts').append('
See All Alerts ' +
   712 :                                              '
');
   713 :                 $('.dropdown-alerts').append('
Clear All Alerts ' +

Traceback:

File "/usr/local/lib/python3.6/site-packages/django/core/handlers/exception.py" in inner
  34.             response = get_response(request)

File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py" in _get_response
  115.                 response = self.process_exception_by_middleware(e, request)

File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py" in _get_response
  113.                 response = wrapped_callback(request, *callback_args, **callback_kwargs)

File "./dojo/user/helper.py" in _wrapped
  79.         return view_func(request, lookup_value, *args, **kwargs)

File "./dojo/test/views.py" in view_test
  158.                    'bulk_edit_form': bulk_edit_form,

File "/usr/local/lib/python3.6/site-packages/django/shortcuts.py" in render
  36.     content = loader.render_to_string(template_name, context, request, using=using)

File "/usr/local/lib/python3.6/site-packages/django/template/loader.py" in render_to_string
  62.     return template.render(context, request)

File "/usr/local/lib/python3.6/site-packages/django/template/backends/django.py" in render
  61.             return self.template.render(context)

File "/usr/local/lib/python3.6/site-packages/django/template/base.py" in render
  171.                     return self._render(context)

File "/usr/local/lib/python3.6/site-packages/django/template/base.py" in _render
  163.         return self.nodelist.render(context)

File "/usr/local/lib/python3.6/site-packages/django/template/base.py" in render
  937.                 bit = node.render_annotated(context)

File "/usr/local/lib/python3.6/site-packages/django/template/base.py" in render_annotated
  904.             return self.render(context)

File "/usr/local/lib/python3.6/site-packages/django/template/loader_tags.py" in render
  150.             return compiled_parent._render(context)

File "/usr/local/lib/python3.6/site-packages/django/template/base.py" in _render
  163.         return self.nodelist.render(context)

File "/usr/local/lib/python3.6/site-packages/django/template/base.py" in render
  937.                 bit = node.render_annotated(context)

File "/usr/local/lib/python3.6/site-packages/django/template/base.py" in render_annotated
  904.             return self.render(context)

File "/usr/local/lib/python3.6/site-packages/django/template/loader_tags.py" in render
  62.                 result = block.nodelist.render(context)

File "/usr/local/lib/python3.6/site-packages/django/template/base.py" in render
  937.                 bit = node.render_annotated(context)

File "/usr/local/lib/python3.6/site-packages/django/template/base.py" in render_annotated
  904.             return self.render(context)

File "/usr/local/lib/python3.6/site-packages/django/template/defaulttags.py" in render
  209.                     nodelist.append(node.render_annotated(context))

File "/usr/local/lib/python3.6/site-packages/django/template/base.py" in render_annotated
  904.             return self.render(context)

File "/usr/local/lib/python3.6/site-packages/django/template/defaulttags.py" in render
  302.                     match = condition.eval(context)

File "/usr/local/lib/python3.6/site-packages/django/template/defaulttags.py" in eval
  876.         return self.value.resolve(context, ignore_failures=True)

File "/usr/local/lib/python3.6/site-packages/django/template/base.py" in resolve
  698.                 new_obj = func(obj, *arg_vals)

File "./dojo/templatetags/display_tags.py" in get_thumbnail
  871.     file_format = Path(filename).suffix[1:]

File "/usr/local/lib/python3.6/pathlib.py" in __new__
  1001.         self = cls._from_parts(args, init=False)

File "/usr/local/lib/python3.6/pathlib.py" in _from_parts
  656.         drv, root, parts = self._parse_args(args)

File "/usr/local/lib/python3.6/pathlib.py" in _parse_args
  640.                 a = os.fspath(a)

Exception Type: TypeError at /test/7011
Exception Value: expected str, bytes or os.PathLike object, not NoneType

Thanks to @valentijnscholten for the quick help.
@Maffooch it seems that your latest PR on uploads is messing up with the Google Sheet integration. I had it turned on.
Since the Google Sheet integration seems broken anyways due to other changes and since I was not really using it anyways, doing
update dojo_system_settings set enable_google_sheets = false ;
commit;

Made that error dissapear.
I think we'll need more tests.

Thanks to @valentijnscholten for the quick help.
@Maffooch it seems that your latest PR on uploads is messing up with the Google Sheet integration. I had it turned on.
Since the Google Sheet integration seems broken anyways due to other changes and since I was not really using it anyways, doing
update dojo_system_settings set enable_google_sheets = false ;
commit;

Made that error dissapear.
I think we'll need more tests.

It's because the files variable is used by both the generic fileupload and google sheets functionality. We could slap a enable_google_sheets=True flag on the integration tests similar to what we did with JIRA/GitHub.

It's because the files variable is used by both the generic fileupload and google sheets functionality. We could slap a enable_google_sheets=True flag on the integration tests similar to what we did with JIRA/GitHub.

I am not quite sure yet, but it seems that a new configuration "works". It may be this issue is raised through upgrading and not through the happy new configuration green field path.

I am not quite sure yet, but it seems that a new configuration "works". It may be this issue is raised through upgrading and not through the happy new configuration green field path.


Update install-biztalk-adapter-pack-2013-r2-and-2013.md

Updated formatting per User Story 1571029: https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/1571029

Docs Build status updates of commit 61546b9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/install-biztalk-adapter-pack-2013-r2-and-2013.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Minor formatting update related to User Story 1571029.
#sign-off

@tfosmark I signed-off on this Loc-fix PR yesterday, but it hasn't been reviewed. This is the first time I'm working in the biztalk-docs repo and I'm not sure if the workflow is different here than in other repos. Do you have the power to move the review process along?

Closing pull request because it was made, in error, against the live branch. I have recreated the updates in PR427 which I made against the master branch.


Script is not idempotent

Script does not undo any changes during failure.

Rather than using compensating actions, this will capture the contents of the manifest files at the start of the script and upon failure re-write the contents back to the files.

Not 100% idempotent but will revert import configuration files on failure


Lack of hint in Shark Attack

Describe the bug
Lack of hint in Shark Attack
Steps to reproduce the behavior
1.Navigate to https://arcade.makecode.com/beta#
2.Click Shark Attack----> Start Tutorial------>Add lives
3.Click step 3
Expect behavior
There shows a hint about this step

Actual behavior
Lack of hint in Shark Attack

Additional context
1.OS: Windows(rs6)
2.arcade version: 1.1.10
3.Microsoft MakeCode version: 6.2.10

These depends on the author of the tutorial. It is not necessary to have hints on every step.


[Enhancement]: Retry getting Ryuk image

Module
Core
Proposal
It seems that Unreliables is used wherever we want operations to be retried (like container startup).
Please add retries in ResourceReaper.start or in DockerClientFactory.checkAndPullImage.

The default number of attempts is 1: https://github.com/testcontainers/testcontainers-java/blob/master/core/src/main/java/org/testcontainers/containers/GenericContainer.java#L173 and the Ryuk container doesn't change this.
Does it mean it'll retry one time or not at all?

After looking at https://github.com/rnorth/duct-tape/blob/master/src/main/java/org/rnorth/ducttape/unreliables/Unreliables.java#L72 I guess it won't retry.

@nineinchnick startupAttempts has different semantics. The retry mechanism for image pulls is implemented in https://github.com/testcontainers/testcontainers-java/blob/master/core/src/main/java/org/testcontainers/images/RemoteDockerImage.java#L32.

Thanks @bsideup and @kiview for all the clarifications. It seems in the latest version it works as it should.
We've upgraded to 1.17.3 and will monitor our CI flakiness reports to see whether there is still some room for further improvement.
Thanks.


Browser compatibility? Especially IE 10

I couldn't find any documentation on the browser compatibility.
I'm wondering whether IE 10 is supported. IE 11 works out of the box.
Running the demos from http://phosphorjs.github.io/examples.html in IE 10 always yields SCRIPT5009: 'WeakMap' is undefined.
Building the DockPanel demo myself (from examples/example-dockpanel) yields a different error:
TypeError: Unable to set property 'mode' of undefined or null reference
at DockPanel (eval code:50:9)
...
upon line:
let dock = new DockPanel();

We support IE 11 and the most recent stable versions of Chrome, FF, and Edge.
We do not support IE 10.


return after last element if there's no callback

otherwise the last element in the array is created again

Thank you, I will be responding more detailed at https://forum.iobroker.net/post/506533


DKV1

Key
Value

View
https://database.shabados.com/sources/1/page/1094/line/22

Source
Sri Guru Granth Sahib Ji

Page
1094

ID
DKV1

Line
kwjlu hwr, qmol rsu; ibnu psy, hiB rs Cwru ]3]

Shabadarth (Vol. 3) | July 2010 | SGPC, Sri Amritsar

#95 #1480


Feature: Prevent bumping version if no new commits

How can i prevent bumping the version if the are no commits since previous version?

@portokallidis Unleash is currently designed to let you run whatever you want as long as your NPM prepublish script & git repo are in a good state. I am happy to have that changed so that the default is to not allow you to bump unless there have been commits. That could be achieved by updating Unleash so that it evaluates the current SHA against the SHA of any tag matching the current package.json name & version.