Keep .X when setting filename to None

[X] Closes #1723
[ ] Tests added
[ ] Release note added (or unnecessary)

Does _to_memory_mode only get called by the filename setter anyways? And are there reasons to not just call to_memory from this setter?
If not worth to go in depths here anymore, the removed _ would fix a bug for now I guess

@eroell Please add a test to check the behavior is correct of this so we can verify the fix actually works

added, @ilan-gold


Consider a slightly less generic name

I think it's not too uncommon for a rails app to have a model called "EmailAddress" if you choose to allow a person to have many email addresses for example, and don't store an email address directly on a person record.
In this case, this gem's name conflicts with the model name.

See #42.

#64 Addresses this for me!


Sorting with verbatim fields does not work

Sorting with a custom sorting template using the eprint field does not work:
\documentclass{article}
\usepackage{filecontents}
\usepackage[backend=biber]{biblatex}

\DeclareSortingTemplate{eprint}{
    \sort[direction=descending]{\field{eprint}}
}

\begin{filecontents}{references.bib}
@article{A01,
    author = {Author, A.},
    year = {2014},
    title = {Alpha},
    eprint = {1402.1354},
}
@article{B02,
    author = {Buthor, B.},
    year = {2016},
    title = {Bravo},
    eprint = {1602.1354},
}
@article{C03,
    author = {Cuthor, C.},
    year = {2015},
    title = {Charlie},
    eprint = {1504.1354},
}
\end{filecontents}

\addbibresource{references.bib}

\begin{document}
\newrefcontext[sorting=eprint]
\nocite{*}
\printbibliography
\end{document}

moewew suggested this issue is not limited to eprint but to all verbatim and also uri fields.

Should be fixed in 2.13 DEV. Please note that you will also need biblatex 3.13 DEV.

Fixed in latest 2.13 release.


Add go 1.9.x to travis builds

I'm using 1.9.x at home, maybe you would like to support that version too?

Depending on what @svanharmelen thinks, may be a good move to also test against tip/1.x. Not sure how far back we support either.

I'm also using 1.9.x (don't we all :wink:) Looks good for now, but once 1.10 comes out later this month we should add that one and also use tip (and then maybe drop 1.7). But for now let's start with this 👍


Feature discusion: Block list. Usage and Design

Is your feature request related to a problem? Please describe.
I assume some people may have some pages for outdated, useless, or even ready-to-delete texts. For example, I have a page called GTD/Archived. It is a very long page, and it could appear in fireSeqSearch hits very frequently.
Describe the solution you'd like
I'd like to add a BlockList feature.
Additional context
However, I have several potential approaches to it, and I'm still in doubt.

Create a blocklist.txt, and te server would load it
Add an option in the web extension
Add a tag in some pages of logseq, and they'll be ignored
etc...

Please share your thoughts on this feature.
Note: Only English and Chinese posts are allowed in the issues section. English is preferred.
请使用英文或中文发 issue.

I added an option for zotero items https://github.com/Endle/fireSeqSearch/issues/122
Now sure if it's needed to block other pages


Release Google.Cloud.Functions.V1 version 1.2.0

Changes in this release:

Commit d4815e4: feat: add SecurityLevel option on HttpsTrigger
Commit 9ac0b1d: docs: minor formatting fixes to Cloud Functions reference docs
Commit ac367e2: feat: Regenerate all APIs to support self-signed JWTs
Commit 6aa7606:

fix: Updating behavior of source_upload_url during Get/List function calls
Regenerating cloud functions docs

Created release for Google.Cloud.Functions.V1-1.2.0


Add date-only ToString() for DateTime

Closes #4300

Silly question: Why do we need this?

@LarryOsterman, it is described in the bug that's linked in the description, #4300. We need this to interchange with the swaggers that require date and that do not accept datetime.

@LarryOsterman, it is described in the bug that's linked in the description, #4300. We need this to interchange with the swaggers that require date and that do not accept datetime.

FWIW, I feel fairly strongly that pull requests shouldn't force reviewer chase down the linked bug, especially if it's straightforward. The pull request description should contain at least a base level of information that the reviewers need. That is especially true for straightforward pull requests like this one.

As far as I know, Date and DateTime are usually implemented as two separate types in other languages, like .Net DateOnly, in Java LocalDate, in Python datetime.date. Is there a strong reason you want to reuse the same type for Date in our C++ SDK?

As far as I know, Date and DateTime are usually implemented as two separate types in other languages, like .Net DateOnly, in Java LocalDate, in Python datetime.date. Is there a strong reason you want to reuse the same type for Date in our C++ SDK?

Remember that Azure::DateTime is a wrapper around the std::chrono::time_point type, as such it encapsulates both time and dates (std::chrono doesn't distinguish between "time" and "date"). If we were to bifurcate the DateTime into Date and Time, they would still be wrappers around std::chrono based types.
I'm not sure that this use case is sufficiently unique to justify adding a brand-new time type (with all the inherent complexities of implementation (we'd need to add conversion functions between Date and DateTime, DateTime and Date, Time and DateTime, etc). In this case, we only need is a way of representing a time_point with a print representation which is just the full-date representation in RFC 2339.

Closing this PR for now, I'll get to it later and then I'll probably reopen it instead of submitting a new one. Thank you for your feedback, I'll address it.


Nx project tags and lint rule setup

[ ] define system for tagging Nx projects
[ ] automate boundary checks using @nx/enforce-module-boundaries lint rule options

See #75 for how we want to organize it.


Expanded row class/styling

Objective is to conditionally style a row based on expanded state. There doesn't appear to be a straightforward way of doing this. Seems like the only way to do this is to select on tr[width="100%"] which is quite fragile/not semantic.
I suggest creating an expandRowOptions or similar that should deprecate the very specific expandRowBgColor. Instead of only being able to style a row's color, add the following options:

expandRowOptions.className(string | callback(row) => string) -- applies string to every expanded row tr, or applies returned string of callback function which is passed the row data
expandRowOptions.style -- could accept an arbitrary map of styles to apply on a row when expanded, in order to provide consistent API to style background color

P.S., @AllenFang I'm aware of the feature freeze on this repo but it's unclear to me if the react-bootstrap-table2 repo is in a usable state yet for me to submit a PR there or if I should do it here instead

@stackptr thanks your suggestion, I'll improve it ASAP.
Any PR or issues is welcome here, but if the feature request is too big, I won't do it. For react-bootstrap-table2, It still on progress, and it's need some time to make react-bootstrap-table2 to have same feature/functionality with react-bootstrap-table. I hope  react-bootstrap-table2 can achieve 80% functionality in the end of this year.
Anyway, I can promise that react-bootstrap-table2 will have more functionality and less bug than react-bootstrap-table, thanks

After poking around with the code I see an undocumented BootstrapTable options prop key, expandBodyClass which seems to apply a class to an expanded row, although it is not removed when the row is collapsed.
Anyways, I'll be working on a PR for this over the next few days...

ohhh... yes, we have expandBodyClass, and you can control it very easy:
const options = {
      expandBodyClass: function(row, rowIndex, isExpanding) {
        if (!isExpanding) { //collapsed
          return null;
        } else {
          return YOUR_CUSTOM_CLASS
        }
      },
      expandParentClass: 'custom-expand-parent'  // expandParentClass also accept callback function
    };


revisit squash (secure mode) permissions

can privileged status be removed?
Does squash still need the ability to create serviceaccounts, clusterroles and clusterrolebindings?

Also restrict squash to creating debugger pods in the squash-debugger namespace only.

I had some success deploying squash with the following. Also removes the ability to create service accounts, cluster roles, and cluster role bindings.
The next big question, I would ask, is does plank really need to be able to use all verbs over customresourcedefinitions? Is allowing plank to manage the debugattachments really not enough?
---
# Namespace - squash-debugger
apiVersion: v1
kind: Namespace
metadata:
  name: squash-debugger

---
# Deployment - Squash
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "1"
  labels:
    app: squash
  name: squash
  namespace: squash-debugger
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: squash
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: squash
    spec:
      containers:
      - env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
        - name: HOST_ADDR
          value: $(POD_NAME).$(POD_NAMESPACE)
        - name: NODE_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: spec.nodeName
        image: soloio/squash:dev
        imagePullPolicy: IfNotPresent
        name: squash
        ports:
        - containerPort: 1234
          name: http
          protocol: TCP
        resources: {}
        securityContext:
          privileged: true
          procMount: Default
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /var/run/cri.sock
          name: crisock
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      serviceAccount: squash
      serviceAccountName: squash
      terminationGracePeriodSeconds: 30
      volumes:
      - hostPath:
          path: /var/run/dockershim.sock
          type: ""
        name: crisock

---
# Service Account - Squash
apiVersion: v1
kind: ServiceAccount
metadata:
  name: squash
  namespace: squash-debugger

---
# Role Binding - Squash
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: squash-rb-pods
  namespace: squash-debugger
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: squash-r-pods
subjects:
- kind: ServiceAccount
  name: squash
  namespace: squash-debugger

---
# Role - Squash
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  namespace: squash-debugger
  name: squash-r-pods
rules:
- apiGroups:
  - ""
  resources:
  - pods
  verbs:
  - get
  - list
  - watch
  - create
  - delete

---
# Cluster Role Binding - Squash
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: squash-crb-pods
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: squash-cr-pods
subjects:
- kind: ServiceAccount
  name: squash
  namespace: squash-debugger

---
# Cluster Role - Squash
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: squash-cr-pods
rules:
- apiGroups:
  - ""
  resources:
  - namespaces
  verbs:
  - list
- apiGroups:
  - squash.solo.io
  resources:
  - debugattachments
  verbs:
  - get
  - list
  - watch
  - create
  - update
  - delete
- apiGroups:
  - apiextensions.k8s.io
  resources:
  - customresourcedefinitions
  verbs:
  - get
  - list
  - watch
  - create
  - update
  - delete
  - register

---
# Service Account - Plank
apiVersion: v1
kind: ServiceAccount
metadata:
  name: squash-plank
  namespace: squash-debugger

---
# Role Binding - Plank
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: squash-plank-rb
  namespace: squash-debugger
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: squash-plank-r
subjects:
- kind: ServiceAccount
  name: squash-plank
  namespace: squash-debugger

---
# Role - Plank
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: squash-plank-r
  namespace: squash-debugger
rules:
- apiGroups:
  - ""
  resources:
  - pods
  verbs:
  - get
  - list
  - watch
  - create
  - delete

---
# Cluster Role Binding - Plank
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: squash-plank-crb
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: squash-plank-cr
subjects:
- kind: ServiceAccount
  name: squash-plank
  namespace: squash-debugger

---
# Cluster Role - Plank
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: squash-plank-cr
rules:
- apiGroups:
  - ""
  resources:
  - namespaces
  verbs:
  - list
- apiGroups:
  - squash.solo.io
  resources:
  - debugattachments
  verbs:
  - get
  - list
  - watch
  - create
  - update
  - delete
- apiGroups:
  - apiextensions.k8s.io
  resources:
  - customresourcedefinitions
  verbs:
  - get
  - list
  - watch
  - create
  - update
  - delete

I think you can remove the crd permissions on plank if you are in secure mode. This should be enough when using secure-mode:
# Cluster Role - Plank
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: squash-plank-cr
rules:
- apiGroups:
  - ""
  resources:
  - namespaces
  verbs:
  - list
- apiGroups:
  - squash.solo.io
  resources:
  - debugattachments
  verbs:
  - get
  - list
  - watch
  - update
  - delete

Thank you very much again for your help @mitchdraft. Sorry to be a bother again, but I missed this one before. Could the squash cluster role also possibly drop permissions for clusterwide CRDs in secure mode as well?
# Cluster Role - Squash
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: squash-cr-pods
rules:
- apiGroups:
  - apiextensions.k8s.io
  resources:
  - customresourcedefinitions
  verbs:
  - get
  - list
  - watch
  - create
  - update
  - delete
  - register

Yes, good observation, all of those crd permissions can be dropped. I think the docs need to be updated since a recent change. Now secure mode requires you to register the DebugAttachment crd yourself, which you can do with:
squashctl utils register-resource

@mitchdraft Thanks again for the help!


Unable to Change Overlays While Replay Recording is Paused

You are unable to change anything about the overlays while the replay recording is paused, but when it is being playing it you are able to change things just fine.

I've looked into ways to fix this problem, however every solution I think of either doesn't work, or is way beyond my development skills. If anyone has a potential solution to this problem, please let me know.

I've done some testing on things, and I've deduced that the issue is a result of Replay Mod pausing client ticks while the replay recording is paused. This results in the key bind checker not updating, as it uses the END_CLIENT_TICK event to check if a key is pressed. As a result the issue was not having to do with HudRenderCallback like I had initially thought.
I have a fix for this that is a bit unconventional, which is to use HudRenderCallback to check for key presses, rather than END_CLIENT_TICK. It works, but there are some other solutions I want to look into before finalizing this one, as it has some issues associated with it. Mainly, I believe that HudRenderCallback is updated every frame, and ideally I would like to not check for keypresses potentially hundreds of times a second, and also the tracking point movement is super fast now. Like 10x faster than it was before. I've done testing, and there is no meaning full impact on the performance of the game from checking for key presses using HudRenderCallback vs the END_CLIENT_TICK event, so it's a good enough solution to use.
TLDR:
I've figured out the problem. I have a solution that is good enough, but isn't perfect, so I'm still looking into other solutions. This problem will be fixed in the next update!


Add a new type of slide note

A slide note would be of the form float ">" float and start at the first float before ending at the second.

Closed by PR #63.


Update Github Migration Tests

Update all Github migration tests to use a new repo created just for these tests that won't accidentally be modified by regular users interacting with issues.
Fixes #8895

Codecov Report

Merging #8938 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #8938      +/-   ##
==========================================
- Coverage   41.25%   41.21%   -0.04%
==========================================
  Files         547      547
  Lines       70764    70764
==========================================
- Hits        29192    29167      -25
- Misses      37856    37874      +18
- Partials     3716     3723       +7

Impacted Files
Coverage Δ

models/unit.go
62.16% <0%> (-5.41%)
:arrow_down:

modules/process/manager.go
74.32% <0%> (-4.06%)
:arrow_down:

modules/migrations/github.go
79.53% <0%> (-3.89%)
:arrow_down:

models/repo_indexer.go
66.54% <0%> (-1.82%)
:arrow_down:

modules/migrations/migrate.go
21.22% <0%> (-1.68%)
:arrow_down:

modules/log/event.go
64.61% <0%> (-1.03%)
:arrow_down:

routers/repo/view.go
38.59% <0%> (-0.88%)
:arrow_down:

modules/migrations/gitea.go
8.05% <0%> (-0.64%)
:arrow_down:

models/repo.go
46.46% <0%> (-0.05%)
:arrow_down:

models/error.go
33.86% <0%> (+1.18%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


Improved View Location Preservation When Duplicating Existing Views in the UI (Split to New Tab/Window, Rebasing, etc.)

Windows 10 2491-dev Personal
This is a minor UX enhancement.
Right now, split to new tab:

Opens a new tab focused on _start
Focuses on that new tab
Your previous tab is moved one to the right of the new, _start focused tab

This is could be better in two ways:

the new tab should have the same view as the tab youre splitting, essentially I should get a copy of my current view. E.g. if I split a types window, I should get a second types tab, not _start
that new tab should not be in focus, so I retain my navigation history in the current focused view

Fixed in 2.2.2515-dev.


v0.2.5

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

49 of 70 (70.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-8.2%) to 71.674%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/RDFFormatter.js
47
68
69.12%

Totals

Change from base Build<PHONE_NUMBER>:
-8.2%

Covered Lines:
132

Relevant Lines:
169

💛  - Coveralls


Client Side Build

Please release a fully compiled build for using in the browser (client side). The NPM package does not allow this and requires the user to use modules.

The umd files are exactly that, which is the default "main" field of the package. There are also browser-ready ES modules if not using UMD.


0.2.4 does not run when it is called from CommonJS

This code works fine on v0.2.3, but does not run on v0.2.4:
const { loadTsConfig } = require("load-tsconfig");

const loaded = loadTsConfig(".")
console.log(JSON.stringify(loaded, undefined, "   "));

Error log:
node:internal/modules/cjs/loader:1373
    throw new ERR_INVALID_ARG_VALUE('filename', filename, createRequireError);
    ^

TypeError [ERR_INVALID_ARG_VALUE]: The argument 'filename' must be a file URL object, file URL string, or absolute path string. Received undefined
    at new NodeError (node:internal/errors:399:5)
    at createRequire (node:internal/modules/cjs/loader:1373:11)
    at Object.<anonymous> (/workspaces/dev/load-tsconfig-bug/node_modules/load-tsconfig/dist/index.cjs:139:107)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/workspaces/dev/load-tsconfig-bug/index.cjs:3:26) {
  code: 'ERR_INVALID_ARG_VALUE'
}

This seems to be because `dist/index.cjs' lines 138-139 are weird:
// src/index.ts
var import_meta = {};
var req = typeof globalThis.require === "function" ? globalThis.require : (0, import_module.createRequire)(import_meta.url);

Also note that this bug breaks tsup.

fixed in 0.2.5


Error on Ruby 3.0

I am attempting to run the inspec-gcp-cis-benchmark profile which utilizes this helper pack, and I've noticed that it works fine on Ruby 2.7, but when upgrading to Ruby 3.0 I receive the following error:
[2] pry(#<Inspec::Profile>)> e
=> #<ArgumentError: wrong number of arguments (given 1, expected 0)>
[3] pry(#<Inspec::Profile>)> e.backtrace
=> ["libraries/iam_bindings_cache.rb:31:in `initialize'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/resource.rb:127:in `block in initialize'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/resource.rb:60:in `supersuper_initialize'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/resource.rb:125:in `initialize'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/profile_context.rb:256:in `new'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/profile_context.rb:256:in `block (2 levels) in add_registry_methods'",
 "./inspec-gcp-cis-benchmark/controls/1.01-iam.rb:23:in `load_with_context'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/profile_context.rb:171:in `instance_eval'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/profile_context.rb:171:in `load_with_context'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/profile_context.rb:155:in `load_control_file'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/profile.rb:231:in `block in collect_tests'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/profile.rb:226:in `each'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/profile.rb:226:in `collect_tests'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/runner.rb:121:in `block in load'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/runner.rb:102:in `each'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/runner.rb:102:in `load'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/runner.rb:153:in `run'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/inspec-core-5.17.4/lib/inspec/cli.rb:313:in `exec'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor/command.rb:27:in `run'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch'",
 "/Users/rbclark/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor/base.rb:485:in `start'",

This manifests itself on the top level as
[2022-06-17T17:25:57-04:00] ERROR: Failed to load profile inspec-gcp-cis-benchmark: Failed to load source for controls/1.01-iam.rb: wrong number of arguments (given 1, expected 0)

I assume this has to do with changes in positional arguments between Ruby 2.7 and 3.0 however I've so far been unable to track down exactly how they need to be restructured in order to function properly.

I did some more digging on this and found the issue was not actually Ruby 3.0 but rather InSpec not handling parameters properly with Ruby 3.0. I have put up a PR on InSpec which fixes this problem: https://github.com/inspec/inspec/pull/6155


Question: How can I keep a multipart file in memory?

I need to parse many requests with images and forward them to another server.  Is there a way to avoid writing each one to a file?  I would rather access some sort of Buffer with the file's data in it.  Here is an example request:

curl -F<EMAIL_ADDRESS>-F "username=slim" http://localhost:3234/uploadImage

It sounds more like formidable question. I'm not very familiar, but can't do much from such packages. If you find some workaround around event listeners you can use koa-better-body than and pass IncomingForm instance to its options.

thank you

@jcalfee did you find a solution for that?


[WIP] Re-add dns addresses for containers after weave gets re-created

A bit dirty but there's (or at least was) bigger refactoring pending on weave startup logic so didn't want to refactor too much.
fixes #2079

A bit dirty but there's (or at least was) bigger refactoring pending on weave startup logic so didn't want to refactor too much.

Yes, see WIP branch over in https://github.com/kontena/kontena/blob/refactor/agent-weave-nodeinfo/agent/lib/kontena/launchers/weave.rb

I was trying to avoid the migration logic in the "full" network restart in this case as it might be bit expensive if there's lot of containers.

I was trying to avoid the migration logic in the "full" network restart in this case as it might be bit expensive if there's lot of containers.

Hmm... the code currently runs start if it sees a Docker container restart event for the weave container. Shouldn't that already handle this case by re-registering all the DNS names? Is that logic broken?

Hmm... the code currently runs start if it sees a Docker container restart event for the weave container. Shouldn't that already handle this case by re-registering all the DNS names? Is that logic broken?

Seems to be. :-/  Have to figure why...

Hmm... the code currently runs start if it sees a Docker container restart event for the weave container. Shouldn't that already handle this case by re-registering all the DNS names? Is that logic broken?

But in the weave update case it's not a restart, it's a destroy+start that the worker will see.

Right... should we just fix that logic to run self.start on both restart and start events? Would that be enough to fix this?

I guess the real breakage here re #1923 and #2079 was in #1398:

Attempted to fix WeaveWorker restart case by immediately starting if network_adapter.running?. I doubt this is 100% race-proof, but it might be good enough.

     def initialize
       info 'initialized'
-      subscribe('network_adapter:start', :on_weave_start)
+      if network_adapter.running?
+        self.start
+      else
+        subscribe('network_adapter:start', :on_weave_start)
+      end
     end

The side-effect of this is that the WeaveWorker no longer waits for the Weave actor to complete start and notify network_adapter:start. That means that it if the old version of weave is running at startup, it will immediately attach and register the container DNS names, even before the Weave actor has a chance to upgrade the weave container, or while it is in the middle of upgrading.

So the right fix might be to not have the WeaveWorker do anything until the Weave actor has completed launch (renamed from start). So instead of if network_adapter.running?, it should just check network_adapter.started?.
I think that one-liner fix might be enough to fix this?

Made a separate PR for this fix:  #2153

Merged #2153 as a minimal 1.2.0.rc2 fix for the weave upgrade case, but we still need some change to the weave restart logic to fix #2158.

Needs merge per #2153 conflict

Still needs merge for #2153, and presumably also  #2265

I was trying to avoid the migration logic in the "full" network restart in this case as it might be bit expensive if there's lot of containers.

IMO re my #2173 PR it would be better to just have a single "restart" behavior for all cases to keep the WeaveWorker simple, even at the expense of running unnecessary weaveexec attach operations, absent any evidence of issues caused by the unnecessary attaches. In particular, considering how rare the network_adapter:restart case here is - it just makes the already bug-prone WeaveWorker even harder to test, as opposed to a single regularly-tested code path.
If we do run into problems caused by runnings lots of weaveexec attach operations, then I suggest we extend the @migrate_containers logic to not re-attach containers that are already attached.

I think #2173 is a bit cleaner way to go, so maybe we should just close this one?

rebased


Collection getindex indexing starts at 1 for SQLite files

To reproduce:

Open QGIS, create a vector layer containing some MultiPolygons (not tested with other stuff) and save it as sqlite or spatialite.

import fiona
file = "..."
fiona.supported_drivers["SQLite"] = "rw"
with fiona.open(file) as f:
    print(len(f))  # e.g. 4
    print(f[-1]["id"])  # this is 3
    for p in f:
        print(p["id"])  # runs from 1 to 4
    print(f[0]["id"])  # errors

Output:
4
3
1
2
3
4
Traceback (most recent call last):
  File "/home/max/programs/anaconda3/envs/dr/lib/python3.7/site-packages/IPython/core/interactiveshell.py", line 3427, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-44-03daf2b261e4>", line 10, in <module>
    print(f[0]["id"])
TypeError: 'NoneType' object is not subscriptable

Expected behaviour: f[0]["id"] is 1 and f[-1]["id"] is 4 - which would match the behaviour of an identical ESRI shapefile.
Operating system
Debian 10 5.9.0-0.bpo.5-amd64
Fiona and GDAL version and provenance
fiona 1.8.17 via pip in conda env
gdal 3.1.4

This quirk is documented at https://fiona.readthedocs.io/en/stable/manual.html#collection-indexing. I'm sorry you got tripped up by it.

Thanks for the reply and sorry for not reading the docs carefully.


Menu item 'Check For Updates' should be disabled when there's no frontmost window

VSCode Version: 1.1.0
OS Version: Mac OS X 10.11.4

Steps to Reproduce:

Launch VSCode
Close all windows
Go to menu 'Code' and select 'Check For Updates'
Nothing, no alert, no message.  Like the menu item was never selected.

This is OK. The application will still be updated if there is an update in this situation.


Problems with simple record action

Hello,
I want to make a simple record action that when I click on it, it does something on the backend and when the response is received, the page is just refreshed.
My handler is like this:
handler: async (request, response, context) => {
          await CustomUserAdapter.blockUser(request.params.recordId, context.currentAdmin.providerType);
          return {
          };
        },

The problem that I encounter is in backend/controllers/api-controller at line 170:
    if (jsonWithRecord && jsonWithRecord.record && jsonWithRecord.record.recordActions) {
      return jsonWithRecord;
    }

    throw new _configurationError.default('handler of a recordAction should return a RecordJSON object', 'Action#handler');

The error is thrown here.
I've managed to hack my way into obtaining this by modifying the lines above to
    if (jsonWithRecord || jsonWithRecord.record && jsonWithRecord.record.recordActions) {
      return jsonWithRecord;
    }

     throw new _configurationError.default('handler of a recordAction should return a RecordJSON object', 'Action#handler');

and by adding an "after" handler that removes the record in order to avoid an error on the frontend.
      after: async (response, request, context) => {
          // response.record = undefined;
          return response;
        },

Is there a way to obtain this behaviour without these hacks?

A record must be returned by design but you can attempt to return an empty record if you don't want to show this to the user:
import { BaseRecord } from 'admin-bro;
...
return {
  record: new BaseRecord({}, context.resource),
}

Not tested but might work

That still does not work because in the api-controller the third condition in the "if" fails because jsonWithRecord.record.recordActions is undefined. :(

Could you try:
return {
  record: new BaseRecord({}, context.resource).toJSON(context.currentAdmin),
}

?
jsonWithRecord.record.recordActions might not be 100% needed in the condition but it's very likely that frontend components which depend on it will break if we simply remove that

Thank you! That works!


Can these codes be executed on standard GPUs?

It appears that these codes have been designed for execution on Cerebras hardware. Can they be easily adapted for deployment on standard GPUs such as the NVIDIA A100? Thanks a lot!

The instruction-tuning of CrystalCoder is performed on GPUs using a modified version (to support muP) of Megatron-LM, which can satisfiy your needs, but that codebase and instruct models haven't been released yet. We plan to release them in the very near future.


Filter outgoing IP for clients on server side

Has anyone solved the problem of filtering outgoing connections for wierguard clients on the server side without using AllowedIPs on the client side or in combination with it?
Something like a whitelists, easy to edit, ideally for each client its own. I would be grateful if someone would advise an existing solution.

Hello ItterVH. I’m not sure i understand your question. I’m also not sure I can help you, since I’m come from social sciences and this is a recent hobby. Trying to help you I ended up having my own question.
I did not understand, at first, logic behind the server and client configuration of allowed IP (and probably I still don’t!). If I got it correctly, on the server side you set the default allowed IPs. That´s the value that wg-portal will set by default to every peer that is created on the interface.conf file (wg0.conf) when you add a new client on wg-portal. If you choose to set a different AllowedIP on the client configuration tab, it will override the default allowed IP, setting an exclusive configuration for that peer on the respective peer entry of the .conf file. For that you have to check “Ignore Global Settings”.
Until I read your question, all my clients had the same default configuration. I’ve tried to create a new peer, following that logic, with custom AllowedIPs created on the client side and It just didnt’t work. The client on the interface.conf file is created exclusively with the Peer IP, and the “Ignore Global Settings” apparently doesn’t work.
Searching for an answer, I found Issue #24 that seams similar to this question.
Supposing that that I have wg-portal working in server mode, with the IP <IP_ADDRESS> and that Default Allowed IPs are <IP_ADDRESS>/24, how do I set a client to connect exclusively to a home network resource that is available at <IP_ADDRESS> (<IP_ADDRESS>/32)?

My question is for the case when a wireguard subnet has forwarding to an interface connected to the Internet and there is a need to allow clients to connect strictly to certain addresses on the Internet using a whitelist.
If this is configured only on the client side, a smart client can replace the AllowedIPs list with <IP_ADDRESS>/0 and be completely free to commit unnecessary disgrace.

The issue is solved by post-up / post-down scripts with iptable rules. Something like this:
ip_pool="<IP_ADDRESS>/24"
while read -r ip; do
iptables -A FORWARD -i wg0 --source $ip_pool --destination $ip -j ACCEPT
done < $whitelist
iptables -A FORWARD -i wg0 -j DROP
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

Question to the developer - is it possible to somehow get access to the AllowedIPs list that is stored in the portal database? It would be nice to be able to export it to a plain text file to use as a whitelist.

Sorry, kinda long IMHO - but i find this one of the more important topics around wireguard (IMHO)
I think it is best practice to run a firewall in any case with WG. Since the client can set the AllowedIps to whatever it likes, not tighten up the server side will have sensible consequences.
I'am new to wireguard, coming from OpenVPN and not used to the concept 'the client tells the server what he want to access' - this is really odd (by wireguard) - but it is conceptual by wireguard itself.
This said, once can simply limit using firewall forward rules, what the wg clients will be able to access (no matter of their wish).
This said, not sure this should be part of wg-portal at all, but if, it would be a huge responsibility and quiet a big effort too.
Concept/Design A "all clients equal":
Either we define that for one wg-instance (those one wg bridge) we consider all clients to be 'equally limited in their scope' - thus we can basically start up wireguard on wg0 and create the forward rules ourselves using the known allowedIps configuration (and this could be something wg-portal could do). E.g. wg-easy does something 'similar' (but not really using allowedIps at all).
I think this concept is mostly aligned how wireguard itself was designed - anything beyond 'all clients are equal' seems to be rather at home with openVPN in the first place
Concept/Design B "per client limitation":
IMHO this would need a different API, also given the clients individual AllowedIP rules and then creating FORWARD rules for the client tunnelIP, not for all clients to the outgoing allowedIp list for this specific client.
Possible but for sure way more effort then A and maybe way to off-grid for the usual use-case for wireguard.

Concept/Design B "per client limitation":
Just to add some food for thought I think that most of the info for the Concept/Design B "per client limitation" are already on the db:
select ips_str, allowed_ips_str, allowed_ips_srv_str from peers limit 2;
+-------------------------------------------+------------------------------------------+---------------------+
| ips_str                                   | allowed_ips_str                          | allowed_ips_srv_str |
--------------------------------------------+------------------------------------------+---------------------+
| <IP_ADDRESS>/32                            | <IP_ADDRESS>/24, <IP_ADDRESS>/16              |                     |
| <IP_ADDRESS>/32, fddc:6585:aedb:3232::4/128 | <IP_ADDRESS>/24, fddc:4f58:e4a2:2233::/52 |                     |
+-------------------------------------------+------------------------------------------+---------------------+

The ips_str syntax (comma separated values) is the same of nftables sets while  some effort is needed to separate  ipv4 and ipv6 address.
A oversimplified rule can be one like this:
nft add rule inet filter forward ip saddr { $ips_str_ipv4 , $allowed_ips_srv_str_ipv4} ip daddr {  $allowed_ips_str_ipv4 }
 accept
nft add rule inet filter forward ip6 saddr { $ips_str_ipv6 , $allowed_ips_srv_str_ipv6} ip daddr {  $allowed_ips_str_ipv6 }
 accept

I was tempted to generate a similar config with a crontab but a more efficient approach is to detect configuration changes and update the firewall config, triggering  a rules reload (in issue #142 gudata suggest to use systemd.path for similar job).
Concept/Design C "per group limitation":
A thing I really miss in  wg-portal is method to define common properties for users, something like groups or templates.
Now every users has his allowed_ips, if we add a db server we need to examine every peer to see if it needs to be updated with the new ip, and the user must re-download (or manually change) his config . Using a "group" o "template" feature, changing the template automatically updates every user belonging to it, but the user still needs to e-download (or manually change) his config. If the "group" o "template" can handle the firewall rules too, we can leave the allowed_ips quite permissive and restrict access with nftables or iptables (the first better). I know this is a big change and maybe needs a dedicated issue, I put it here just to add another option, so I don't dig deeper without a feedback


Use a stream processing friendly algorithm for calculating mean and population standard deviation

https://en.wikipedia.org/wiki/Algorithms_for_calculating_variance

The performance update has been included in v0.0.5.
Using the new benchmark, BenchmarkPeakDetector_NextBatch, it appears the new version is faster by a factor of more than 10.
Changes:

Use Welford's method on initialization.
Use a similar online algorithm for computing the next mean and population standard deviation.

New references:

https://stackoverflow.com/a/14638138/14797322
https://www.johndcook.com/blog/standard_deviation/
https://en.wikipedia.org/wiki/Algorithms_for_calculating_variance


Added requirement that XDM properties always have concrete types.

It was found that with enumeration support that types can be variable. This is something that can cause great difficulties in data interoperability and code generation from JSON Schema. So to close this hole I am proposing that all properties have concrete types.
Example of what we do not want to allow is :
Even more than that: the enum constraint can go without accompanying type constraint and contain values of different type, e.g.
{
"$schema": "http://json-schema.org/draft-06/schema#",
"$id": "https://ns.adobe.com/xdm/sample1",
"definitions": {
"False": {
"enum": [0, false, "false"]
}
},
"$ref": "#/definitions/False"
}
Please link to the issue #…

@cdegroot-adobe is it intentional to make this PR against your own repo?


Set country to "us" if provided default country is invalid

What has been done

Handled invalid defaultCountry values
Fixed related console error
Updated type for CountryIso2 to string (with auto-completion)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Apply contract read value hook to v1 and v2 contract readers

What does this PR do and why?
Apply contract read value hook to v1 and v2 contract reader hooks.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #1869

PR #1870

PR #1871   👈

This comment was auto-generated by Graphite.


Windows stand-alone version: install for all users (administrative privileges required)

Currently, DataLab Windows installer does not support installing for all users:

The installer does not ask for elevated privileges
Shortcuts are installed in current user start menu
Current user must have write access to the installation directory

Would it be necessary to support installing for all users as well?

Recently we switched from NSIS to WiX for various reasons.
The new WiX installer now takes into account the user profile permissions (install for all users if admin rights, install for current user otherwise)


net/http: unable to use getpeername to authenticate Unix socket requests

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?
go version go1.6.2 linux/amd64
What operating system and processor architecture are you using (go env)?
Fedora 24 X86_64
What did you do?
Go doesn't let me access the file descriptor of the connection socket in net.http.HandlerFunc's ServeHTTP() function. While I agree that users should not mess with the file descriptor when it is under control of a HTTP library, it also prevents other use cases. I have written a HTTP server that listens on a Unix domain socket file. Unix sockets are local sockets that have some interesting properties. For example they allow to get the pid, uid, gid and security context (SELinux label) of the peer. This feature can be used for authentication and authorization (GetsockoptUcred #3836, #16374).

With Go 1.6 neither http.ResponseWriter nor http.Request have a public field or func that let me access the connection object, file or file descriptor. The connection is contained within the package internal http.conn struct. I also looked into Go 1.7 RC. Request got a context, but I don't see how that might solve the problem at hand.
Some mailing list posts suggest to use http.Server's ConnState hook to track connections in a map. For IPv4 and IPv6 connection it is possible to map conn.RemoteAddr to conn and then use http.Request.RemoteAddr to retrieve the connection. After all the combination of (src ip, src port, dest ip, dest port) is a unique identifier for TCP over IP. However that is not true for AF_UNIX / SOCK_STREAM. Unix socket's don't implement getpeername(). For a UnixListener the RemoteAddr of a http.Request is always the string '@'. net.Conn and http.Request don't share any other field that could be used as a common identifier.
Eventually I worked around the problem with http.Hijack().  It also prevents HTTP 1/1 persistent connections. https://github.com/tiran/custodia_goforwarder/blob/master/custodia_goforwarder.go#L95
Please provide a better and simpler way to access the file descriptor.

There are many issues with exposing the underlying socket, which is why we haven't done so yet. What are you trying to do?
(instead of stating your problem, it seems you're asking for a specific solution?)

I like to authenticate local Unix connections inside the HTTP request handler ServeHTTP() with https://golang.org/pkg/syscall/#GetsockoptUcred and security context (#16374). syscall.GetsockoptUcred(int(fd), syscall.SOL_SOCKET, syscall.SO_PEERCRED) returns pid, uid and gid of the peer. The operating system ensures that these information are valid and correct.
I'm currently porting some parts of a Python application to Go. Specifically a HTTP forwarder that accepts connections on a Unix socket file, authenticate the request with peer credentials and security context of the connection and then forwards the HTTP request to an upstream service. It was very easy to write the Unix socket listener and HTTP forwarder with Go -- until I hit this road block.

Did you consider writing a net.Listener implementation?

Yes, I also looked into net.Listener and studied the low-level socket code. I couldn't figure out how to get the information into ServeHTTP() without a major rewrite or copy of the standard library. For example I looked into a way to give each UnixConn an unique RemoteAddr. The RemoteAddr is set very deeply inside the socket code (net/sock_posix.go func socket() and netFD.dial()).
I'm not a Go expert. How would a custom net.Listener help?

@tiran,
I'm not sure what you want, but perhaps https://raw.githubusercontent.com/mikioh/-stdyng/master/cmd/httpounix/main.go might be a help if your questions are simply:

How to use the net.Listener interface with net/http package?
How to scrape out the net.UnixConn?
Where is the best place to hook up the L4-L3 identifiers from the stack consists of HTTP over socket over AF_LOCAL protocol?

FWIW, the implementation of socket type and its methods vary between platforms, but in general you need to make a named socket if you want to know its near and far endpoint names even in the case of wildcard names.

@mikioh: the far end name does not matter (and most likely it's not even bound on Linux), what matters are the credentials of the process on the far end.
The actual issue is that there is no easy way of bubbling up this information from - say - an http.Server.ConnState callback all the way up to an http.HandlerFunc. And by "easy" I mean "short of rewriting net/http or using http.Hijack()".

If you wrote your own net.Listener wrapper it could return your own net.Conn implementation that embeds the actual net.Conn but overrides the RemoteAddr method, and your implementation could return not just the remote socket name but also the credentials.
So I don't think anything has to go into net/http to make this possible. Of course, it could be made easier, but I think we'd need to figure out how widespread the need for this is.

This is waiting on a concrete proposal at this point.

Sorry @gopherbot, this is still waiting on a concrete proposal.


Gazebo goes not responding after loading the window

Environment

OS Version: Ubuntu 24.04 LTS x86_64
Source or binary build? Binary v8.5.0
If this is a GUI or sensor rendering bug, describe your GPU and rendering system. Otherwise delete this section.

Rendering plugin: [ogre | ogre2]. tried both orge and ogre2

[ ] Sensor rendering error.
[ ] GUI rendering error.

EGL headless mode:

[ ] Running in EGL headless mode

Generally, mention all circumstances that might affect rendering capabilities:

[x] running on a dual GPU machine (integrated GPU + discrete GPU)
[ ] running on a multi-GPU machine (it has multiple discrete GPUs)
[x] running on real hardware
[ ] running in virtual machine
[ ] running in Docker/Singularity
[ ] running remotely (e.g. via SSH)
[ ] running in a cloud
[ ] using VirtualGL, XVFB, Xdummy, XVNC or other indirect rendering utilities
[ ] GPU is concurrently used for other tasks

[x] desktop acceleration
[ ] video decoding (i.e. a playing Youtube video)
[ ] video encoding
[ ] CUDA/ROCm computations (Tensorflow, Torch, Caffe running)
[ ] multiple simulators running at the same time

[ ] other...

Rendering system info:

On Linux, provide the outputs of the following commands:LANG=C lspci -nn | grep VGA  # might require installing pciutils
echo "$DISPLAY"
LANG=C glxinfo -B | grep -i '\(direct rendering\|opengl\|profile\)'  # might require installing mesa-utils package
ps aux | grep Xorg
sudo env LANG=C X -version  # if you don't have root access, try to tell the version of Xorg e.g. via package manager

On Windows, run dxdiag and report the GPU-related information.
On Mac OS, open a terminal and type system_profiler SPDisplaysDataType. Copy the output here.

[ ] Please, attach the ogre.log or ogre2.log file from  ~/.gz/rendering

LANG=C lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM107 [GeForce GTX 745] [10de:1382] (rev a2)

echo "$DISPLAY"
:1

LANG=C glxinfo -B | grep -i '\(direct rendering\|opengl\|profile\)'
direct rendering: Yes
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 745/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 535.183.01
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6.0 NVIDIA 535.183.01
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 535.183.01
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

ps aux | grep Xorg
abc-i9     17972  4.2  0.4 8299636 158812 tty2   Sl+  15:16   1:21 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3
abc-i9     21753  0.0  0.0   9468  2176 pts/2    S+   15:48   0:00 grep --color=auto Xorg

sudo env LANG=C X -version
[sudo] password for abc-i9:

X.Org X Server <IP_ADDRESS>
X Protocol Version 11, Revision 0
Current Operating System: Linux abci9-OptiPlex-7040 6.8.0-40-generic #40-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul  5 10:34:03 UTC 2024 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-40-generic root=UUID=1965d466-bc73-4cf0-88eb-604aea38dff2 ro quiet splash vt.handoff=7
xorg-server 2:21.1.12-1ubuntu1 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.42.2
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.

~/.gz/rendering does not exist

Description

Expected behavior: Gazebo launches with an empty world
Actual behavior: Gazebo windows opens and freezes then goes not responding

Steps to reproduce

Run gz sim

Output
OptiPlex-7040:~$ gz sim
Escalating to SIGKILL on [Gazebo Sim Server]
abc-i9@abci9-OptiPlex-7040:~$ gz sim --verbose
[Msg] Gazebo Sim GUI    v8.5.0
[Msg] Gazebo Sim Quick start dialog
[GUI] [Msg] Not showing Quick start menu.
[GUI] [Wrn] [Gui.cc:271] Waited for 10s for a subscriber to [/gazebo/starting_world] and got none.
[GUI] [Wrn] [Application.cc:908] [QT] file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Dialogs/DefaultFileDialog.qml:413:17: QML ToolButton: Binding loop detected for property "implicitHeight"
[GUI] [Wrn] [Application.cc:908] [QT] file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Dialogs/DefaultFileDialog.qml:309:21: QML Button: Binding loop detected for property "implicitHeight"
[GUI] [Wrn] [Application.cc:908] [QT] file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Dialogs/DefaultFileDialog.qml:309:21: QML Button: Binding loop detected for property "implicitHeight"
[GUI] [Wrn] [Application.cc:908] [QT] file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Dialogs/DefaultFileDialog.qml:413:17: QML ToolButton: Binding loop detected for property "implicitHeight"
[GUI] [Wrn] [Application.cc:908] [QT] file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Dialogs/DefaultFileDialog.qml:309:21: QML Button: Binding loop detected for property "implicitHeight"
[GUI] [Wrn] [Application.cc:908] [QT] file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Dialogs/DefaultFileDialog.qml:309:21: QML Button: Binding loop detected for property "implicitHeight"
[GUI] [Wrn] [Application.cc:908] [QT] file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Dialogs/DefaultFileDialog.qml:413:17: QML ToolButton: Binding loop detected for property "implicitHeight"
[GUI] [Wrn] [Application.cc:908] [QT] file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Dialogs/DefaultFileDialog.qml:309:21: QML Button: Binding loop detected for property "implicitHeight"
[GUI] [Wrn] [Application.cc:908] [QT] file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Dialogs/DefaultFileDialog.qml:309:21: QML Button: Binding loop detected for property "implicitHeight"
Escalating to SIGKILL on [Gazebo Sim Server]

gz sim --render-engine ogre fails similarly

can you try with -v 4 instead of --verbose, e.g.
gz sim shapes.sdf --verbose

and see if it prints some error output

Also, this might be related to a network configuration issue. See https://github.com/gazebosim/gz-transport/issues/476#issuecomment-2282728388

This was a network configuration issue as mentioned in https://github.com/gazebosim/gz-transport/issues/476#issuecomment-2282728388.
Adding this to https://gazebosim.org/docs/latest/troubleshooting/ would help.
Thank you.

@aadith-warrier, I'm glad that was the issue. I agree it would be good to add it to the troubleshooting page. Would you be able to create a PR to https://github.com/gazebosim/docs/edit/master/harmonic/troubleshooting.md?

Yeah sure. https://github.com/gazebosim/docs/pull/484


fix: pod cpu/memory usage metrics grouped by id as well

Pull Request
Required Fields
:mag_right: What kind of change is it?

fix

:dart: What has been changed and why do we need it?

Added id to group by for cpu/memory usage. When pod restarts the prometheus metrics for old and new pod sometimes overlap, creating spike in memory and cpu usage when 2 metrics are sumed together. Plotting then the incorectly high values which may be used to set up pod resources and limits incorrectly. See added screenshot where red and yellow lines are slightly overlapping which would cause spike without id.

@dotdc done


Water Veil

Adds Water Veil's on entry aqua ring, which restores 1/16th hp at the end of every turn.

Also updated the hidden power attacks to the buffed 70 BP


Support for yup-oauth2

Would it be acceptable to add support for yup-oauth2 here? I would really like to use it as it has token caching to file and it is more popular lib.
If replacing gauth completely is not wanted, then feature flags could be used to replace gauth with yup-oauth2.
My fork already has support for yup-oauth2.

In my opinion: definitely. Perhaps as a feature flag first, like you said.

Merged. Thank you for this big improvement.


protege: init at 5.6.4

Description of changes
The current protege-distribution package is derived directly from the upstream release archives, which include a number of pre-installed third-party plugins.
This PR introduces the "vanilla" Protégé build with no added plugins. More importantly, it is a source-based build, contrary to the current "distribution" build, and is better engineered overall.
This Protégé build is platform-independent and the derivation has been structured to support both Linux and Darwin, but, due to the lack of a Darwin machine at hand, I could not come up with a working installation for Darwin systems. Input from knowledgeable people is welcome and solicited.
I will try to refactor the old protege-distribution derivation into a source-based build as soon as technically possible, and maybe integrate it into the new derivation as a special case (maybe as a protegeFull package?).
Thanks go to @doronbehar for pointing me to maven.buildMavenPackage as a way to properly build Maven projects.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

BTW those maven patches are impressive :) Is there a chance you'd have an idea how to help here:
https://github.com/torakiki/pdfsam/issues/583
?

Thank you~! They're nothing special really.
Ok, I started looking into it. Iill report back under the relevant issue as soon as I have any positive outcomes (or negative outcomes different from the ones you obtained).

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

1 package failed to build:

protege

[INFO]
[INFO] --- enforcer:3.4.1:enforce (enforce-maven) @ protege-editor-core ---
[INFO] Rule 1: org.apache.maven.enforcer.rules.RequirePluginVersions passed
[INFO]
[INFO] --- resources:3.3.1:resources (default-resources) @ protege-editor-core ---
[INFO] Copying 188 resources from src/main/resources to target/classes
[INFO]
[INFO] --- compiler:3.13.0:compile (default-compile) @ protege-editor-core ---
[INFO] Recompiling the module because of changed dependency.
[INFO] Compiling 276 source files with javac [debug release 11] to target/classes
[WARNING] Supported source version 'RELEASE_8' from annotation processor 'org.glassfish.corba.annotation.processing.ExceptionWrapperProcessor' less than -source '11'
[INFO] /nix/tmp/nix-build-protege-5.6.4-maven-deps.drv-0/source/protege-editor-core/src/main/java/org/protege/editor/core/ui/workspace/Workspace.java: Some input files use or override a deprecated API.
[INFO] /nix/tmp/nix-build-protege-5.6.4-maven-deps.drv-0/source/protege-editor-core/src/main/java/org/protege/editor/core/ui/workspace/Workspace.java: Recompile with -Xlint:deprecation for details.
[INFO] /nix/tmp/nix-build-protege-5.6.4-maven-deps.drv-0/source/protege-editor-core/src/main/java/org/protege/editor/core/plugin/PluginUtilities.java: Some input files use unchecked or unsafe operations.
[INFO] /nix/tmp/nix-build-protege-5.6.4-maven-deps.drv-0/source/protege-editor-core/src/main/java/org/protege/editor/core/plugin/PluginUtilities.java: Recompile with -Xlint:unchecked for details.
[INFO]
[INFO] --- resources:3.3.1:testResources (default-testResources) @ protege-editor-core ---
[INFO] skip non existing resourceDirectory /nix/tmp/nix-build-protege-5.6.4-maven-deps.drv-0/source/protege-editor-core/src/test/resources
[INFO]
[INFO] --- compiler:3.13.0:testCompile (default-testCompile) @ protege-editor-core ---
[INFO] Recompiling the module because of changed dependency.
[INFO] Compiling 4 source files with javac [debug release 11] to target/test-classes
[WARNING] Supported source version 'RELEASE_8' from annotation processor 'org.glassfish.corba.annotation.processing.ExceptionWrapperProcessor' less than -source '11'
[INFO]
[INFO] --- surefire:3.2.5:test (default-test) @ protege-editor-core ---
[INFO] Using auto detected provider org.apache.maven.surefire.junit4.JUnit4Provider
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.protege.editor.core.platform.apple.MacUIUtil_TestCase
[WARNING] Tests run: 3, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 0.056 s -- in org.protege.editor.core.platform.apple.MacUIUtil_TestCase
[INFO] Running org.protege.editor.core.prefs.PreferencesTest
Jun 04, 2024 4:22:11 AM java.util.prefs.FileSystemPreferences$1 run
WARNING: Couldn't create user preferences directory. User preferences are unusable.
  Unix error code 2.
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.677 s <<< FAILURE! -- in org.protege.editor.core.prefs.PreferencesTest
[ERROR] org.protege.editor.core.prefs.PreferencesTest.testClearStringList -- Time elapsed: 1.674 s <<< ERROR!
java.lang.RuntimeException: java.util.prefs.BackingStoreException: Couldn't get file lock.
	at org.protege.editor.core.prefs.JavaBackedPreferencesImpl.clear(JavaBackedPreferencesImpl.java:42)
	at org.protege.editor.core.prefs.PreferencesTest.testClearStringList(PreferencesTest.java:18)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
	at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
	at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:316)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
	at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
	at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
Caused by: java.util.prefs.BackingStoreException: Couldn't get file lock.
	at java.prefs/java.util.prefs.FileSystemPreferences.removeNode(FileSystemPreferences.java:690)
	at org.protege.editor.core.prefs.JavaBackedPreferencesImpl.clear(JavaBackedPreferencesImpl.java:38)
	... 29 more

[INFO] Running org.protege.editor.core.ui.menu.PopupMenuId_TestCase
[INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.027 s -- in org.protege.editor.core.ui.menu.PopupMenuId_TestCase
[INFO] Running org.protege.editor.core.util.StringAbbreviator_TestCase
[INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 s -- in org.protege.editor.core.util.StringAbbreviator_TestCase
[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   PreferencesTest.testClearStringList:18 ? Runtime java.util.prefs.BackingStoreException: Couldn't get file lock.
[INFO]
[ERROR] Tests run: 24, Failures: 0, Errors: 1, Skipped: 3
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for protege-parent 5.6.4:
[INFO]
[INFO] protege-parent ..................................... SUCCESS [  1.474 s]
[INFO] protege-launcher ................................... SUCCESS [ 24.004 s]
[INFO] protege-common ..................................... SUCCESS [  0.973 s]
[INFO] protege-editor-core ................................ FAILURE [  6.604 s]
[INFO] protege-editor-owl ................................. SKIPPED
[INFO] protege-desktop .................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  44.591 s
[INFO] Finished at: 2024-06-04T04:22:14Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.2.5:test (default-test) on project protege-editor-core:
[ERROR]
[ERROR] Please refer to /nix/tmp/nix-build-protege-5.6.4-maven-deps.drv-0/source/protege-editor-core/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :protege-editor-core

But in the 2nd attempt it didn't fail... Something there is a bit flaky I suppose.
Other then that GUI seemed to work fine.

Thank you very much for the extensive review comments, @AndersonTorres, @doronbehar!
By the way, that (https://github.com/NixOS/nixpkgs/pull/316647#issuecomment-2146587576) failure sounds very weird. Seems like a concurrency problem in the tests? Well, but if the CI reported no issue, it means that everybody is going to get a correct package.

By the way, that (#316647 (comment)) failure sounds very weird. Seems like a concurrency problem in the tests? Well, but if the CI reported no issue, it means that everybody is going to get a correct package.

Usually Hydra and perhaps also ofborg are more prone to concurrency problems then normal users' machines. Worst case we'll modify things in a later PR if the build fails on Hydra. Also it's possible that it will fail on Hydra and it won't fail locally, so users may not notice this issue.

Thank you very much for the extensive review comments, @AndersonTorres, @doronbehar!

You are welcome :).


Support setting difficulty when PoW mining for miners over stratum connections

Hi.
Possibel to add diff when miner connect to stratum. Just at first Connection then get normal diff from the chain.
thank you.

Not sure I understand what you’d like. Do you have a link to a spec or behavior?

@atoulme Thank you for fast answer. Well it will make it esay for people who want to rent hashrate and solo mine on their own node.
So when miner connect to the node so at first connection the diff set to 0. So if you want to mine with NH you will be disconnected. Im not sure if you can use Extranonce to set diff at first connection or something. Thank you again
Pool difficulty too low (provided=0, minimum=0.9)... Error

Before first job (work) is provided, pool MUST set difficulty by sending:
{
"id": null,
"method": "mining.set_difficulty",
"params": [
0.5
]
}\n
First item of params array is difficulty in double data type. Conversion
between difficulty and target is done the same way as with Bitcoin;
difficulty of 1 is transformed to target being in HEX:
00000000ffff0000000000000000000000000000000000000000000000000000
If pool does not set difficulty before first job, then miner can assume
difficulty 1 was being set.
When difficulty is changed, miner starts using new difficulty for every
NEXT job that arrives

This sounds like something the community should help support, it's kinda hard to test and debug.
For now, I'd recommend you use Besu, add a pool software, and your miner connected to the pool software. eth-proxy, open-ethereum-pool come to mind.

@atoulme Set Diff only at first Connection. Just started at school with computer science. We learn to code in java. Gonna play with code and see:) Thank you anyway:)

@diega - is this something we should look to support? Or am I OK to close?

No need anymore.


How to create a namespace if it doesn't exists

I have a kind: Namespace template yaml like follows,
apiVersion: v1
kind: Namespace
metadata:
  name: {{ .Values.namespace }}
  namespace: ""

How do I make helm install create the above given namespace ({{ .Values.namespace }}) if and only if above namespace ({{ .Values.namespace }}) doesn't exits in the pointed kubernets cluster
Output of helm version: 2.9.1
Output of kubectl version: 2.9.1
Cloud Provider/Platform (AKS, GKE, Minikube etc.): Google Cloud

This is a known limitation of Helm. Helm will not do cross-namespace management, and we do not recommend setting namespace: directly in a template.
If you want to install resources in a namespace other than the default namespace, helm install --namespace=foo will create and install the resources in that namespace.
Does that help?

Hi Matthew,
Yeah, Thanks for the quick response. I'll proceed with your guidance.
Thanks,
Kasun Siyambalapitiya
On Fri, Aug 10, 2018 at 9:56 PM Matthew Fisher<EMAIL_ADDRESS>wrote:

This is a known limitation of Helm. Helm will not do cross-namespace
management, and we do not recommend setting namespace: directly in a
template.
If you want to install resources in a namespace other than the default
namespace, helm install --namespace=foo will create and install the
resources in that namespace.
Does that help?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/helm/helm/issues/4456#issuecomment-412134651, or mute
the thread
https://github.com/notifications/unsubscribe-auth/APoTVH8EqKs68e0Asn73skEWQL_xuQhCks5uPbQhgaJpZM4V35hN
.

--
Regards,
Kasun Siyambalapitiya

This is a known limitation of Helm. Helm will not do cross-namespace management, and we do not recommend setting namespace: directly in a template.
If you want to install resources in a namespace other than the default namespace, helm install --namespace=foo will install the resources in that namespace. If the namespace does not exist, it will create it.
Does that help?

What about a situation where you have 2 resources that should go in different namespaces??

Do you mean a helm chart containing resources/subcharts that need to be applied to different namespaces? ultimately we ended up breaking the charts apart to avoid different ns's

Do you mean a helm chart containing resources/subcharts that need to be applied to different namespaces?

Yes! For example openfaas needs two namespaces:

openfaas where the operator and related workload will exist
openfaas-fn where functions will be deployed to

Are the functions deployed as part of the same chart? I agree with @ragarcia26's advice of breaking up these components into individual charts. I imagine the operator and the functions serve separate functions of work and should be managed separately.

We use a helm chart to manage custom RBAC permissions.  That chart creates different Role and RoleBinding through centralized yaml config files.  So the chart needs to create different Role and RoleBinding in different namespaces.
I have problems when the namespace does not exist as it makes the helm install fail.
Right now I have to parse the yaml config files and figure out if a namespace does not exist already then create it with kubectl, only then can I run helm.
Any better suggestion?  Thanks.
For reference, here are more details about the chart: https://github.com/helm/charts/pull/11261#issuecomment-464493406

helm install --namespace foo should be able install all the roles and rolebindings in the foo namespace. The --namespace flag will create the namespace if it didn't exist.
For Helm 3, the namespace creation doesn't happen during helm install any more, so you'll have to create that namespace ahead of time as you do today.

My custom-RBAC chart creates Role and RoleBinding in more than one namespace through a single helm install, so the --namespace flag only helps for one namespace, not the others.
Unless I mis-understood?

@marckhouzam yes, you are correct helm only creates one namespace you specify with --namespace flag.
But going forward with Helm v3 you will need to create the namespace for the chart release as well, so better have one step in advance which does create all required namespaces.

How to create a namespace with helm v3?

Right now, use kubectl create namespace foo prior to helm install. When Helm 3.2.0 is released, use helm install ... --create-namespace.

Right now, use kubectl create namespace foo prior to helm install. When Helm 3.2.0 is released, use helm install ... --create-namespace.

That worked for me with helm 3.2.4
Like a charm!

if ! kubectl get namespaces -o json | jq -r ".items[].metadata.name" | grep staging;then   echo 'HALLO' fi


typescript support

this package works fine with javascript, however fails with typescript. any fix?

I fixed the typescript support here: https://github.com/travelhawk/multipart-lambda-ts-v2


Gimnazija vič

Gimnazija vič. Slovenija.
Gimnazija in Ljubljana Slovenija.
official website: GIMVIC

@erazem19 First stage of verification passed, official domain for Gimnazija vič, Ljubljana, Slovenija is gimvic.org as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@erazem19 Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Fix stacktrace in console handler

report.stacktrace is not always actually a stacktrace. It could also be a string. That is why the type is 'dynamic' Forcing it to be a stacktrace sometimes fails.

Thank you very much for your contribution!
Yes, that was definitely a bug, thanks for fixing it :)

Thanks for the great library and I'm glad to be able to contribute


Number prefixes in *.lex files

    "1_LanguageName": "C++",
    "2_FileExtentions": "*.c;*.cc;*.cpp;*.h;*.hpp",
    "3_Delimiters": "[]{}();",
    "4_NameSymbols": "$",
    "5_SpecialCombination": [],
    "6_LineComments": [
      "//"
    ],
    "7_OpenComments": [
      "/*"
    ],
    "8_ClosedComments": [
      "*/"
    ],
    "9_ToggledComments": [],

It's weird. Numbers are not needed here, you can read words. Numbers make it hard to read.

You are right except only one. Numbers help to make options sorting.
Without it I have a problem when I use any Json library. Them use lexical sorting and options will mixed in strange order for users.

but proper lib must keep order of JSON items when you add them.

No. They uses a some sort of map for storing data. Like a tree map.


Check for incompatible libraries (discord.py, pyfork etc)

Maybe use pkg_resources to check if any python libraries are installed and throw a warning?

dist = pkg_resources.get_distribution(discord.py) # or whatever module it is called

raises `pkg_resources.DistributionNotFound if not installed which we want


Added GitRepo utility decorators

This PR is a piece of my older PR, deprecated by now I think.
Adds:

pull_before decorator.
commit_after decorator.

@minuscorp sweet code!
Before making moves on this PR I would like to discuss the need that this code addresses. It would be nice to either 1.) have it used by another class or 2.) have a discussion about its future use and why we need it now. I apologize if this was already captured in another PR and I have missed it.

Let's wait to merge this until we have another PR that utilizes this new functionality 👍

I'd like to get this merged so I can move towards applying it into the codebase if that's ok with you 😄

I think it would be helpful if you could actually add in the usage you'd like inside this PR. That way we can have a working example.

I'll try to get this implemented soon!

Moving over to https://github.com/fastlane/ci/pull/459


add option to suppress logging job runs

From<EMAIL_ADDRESS>It's pretty nagging to schedule jobs on short intervals (say one second), and have schedule log each and every run.
Another RFC: IMO, as a library, a log level of debug would be more adequate.

Add option to default scheduler , too


[MM-16533] User deactivation does not work when "Disable bot accounts when owner is deactivated" is set to False

Summary

Should always display deactivateMemberModal, no matter what DisableBotsWhenOwnerIsDeactivated is set to.
Fixed another possible bug -- if there was no data returned from a redux action (or no bots?), the deactivateMemberModal wouldn't have opened. There's no reason (that I can see) to make that conditional on the returned data.
Not sure why the community member introduced the loading state variable -- it isn't used in the rest of the file. @sudheerDev?

Ticket Link

Fixes MM-16533

Related Pull Requests
#2879

@cpoile Loading flag is not needed i commented https://github.com/mattermost/mattermost-webapp/pull/2879#discussion_r291851454 to remove it but got lost somehow.

@sudheerDev thanks Sudheer for the clarification!


Consul UI only listening on localhost?

We deployed Mantl on AWS, and have 3 control nodes.
On each host, I can do the following without problems:
curl -vvv http://localhost:8500/ui/
However, The ui is not reachable from another host (including other control-nodes). This is an issue for the mantl-ui as it load-balances requests to the consul-ui:
nginx.conf from mantl-ui:
upstream consul {
        server 10.106.2.xx:8500;
        server 10.106.2.yy:8500;
        server 10.106.2.zz:8500;
    }

Consul version installed by Mantl:
# consul --version
Consul 'v0.6.4-234-gbc6338d'.dev ('bc6338db0fdd7712943f5267ca71529518a883a7+CHANGES')
Consul Protocol: 3 (Understands back to: 1)

It seems Consul UI only listens to the local loopback adapter now, or am I missing something here?
We are on Mantl 1.2 release now.
I verified that port 8500 is opened in my AWS security group.
When I try to open the Consul-UI from the MantlUI, I get the following error:

HTTP error code from Consul: 502 Bad Gateway
This is an error page for the Consul web UI. You may have visited a URL that is loading an unknown resource, so you can try going back to the root.
Otherwise, please report any unexpected issues on the GitHub page.

I see that my nginx error.log file in the nginx-consul image is filling up with errors like this:
2016/08/23 11:16:29 [notice] 38#0: signal process started
2016/08/23 11:17:22 [error] 40#0: *6 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /v1/kv/mantl-install HTTP/1.1", upstream: "http://[::1]:8500/v1/kv/mantl
2016/08/23 11:17:43 [error] 40#0: *168 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /v1/health/service/kibana-mantl-task?token=49ac0606-c9f6-4a11-a3fb-8f
2016/08/23 11:17:46 [notice] 53#0: signal process started
2016/08/23 11:17:49 [error] 55#0: *317 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /v1/health/service/kibana-mantl?token=49ac0606-c9f6-4a11-a3fb-8f51d65e
2016/08/23 11:17:49 [error] 55#0: *302 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /v1/kv/secure/service/nginx/auth/users?recurse=&token=49ac0606-c9f6-4a
2016/08/23 11:17:49 [error] 55#0: *315 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /v1/health/service/chronos?token=49ac0606-c9f6-4a11-a3fb-8f51d65e8683&
2016/08/23 11:18:00 [error] 55#0: *539 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /v1/health/service/mesos?index=839&tag=agent&token=49ac0606-c9f6-4a11-a
2016/08/23 11:18:18 [error] 55#0: *1296 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /v1/health/service/mesos?index=861&tag=leader&token=49ac0606-c9f6-4a
2016/08/23 11:18:30 [error] 55#0: *1307 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /v1/health/service/mesos?index=866&tag=agent&token=49ac0606-c9f6-4a1
2016/08/23 11:18:45 [error] 55#0: *2275 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /v1/health/service/hypergate-internal?index=945&passing=1&stale=&wait
2016/08/23 11:18:56 [error] 55#0: *4982 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /v1/health/service/elasticsearch?index=1150&token=49ac0606-c9f6-4a11
2016/08/23 11:19:12 [error] 55#0: *6116 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /v1/health/service/kafka-mantl?index=1345&token=49ac0606-c9f6-4a11-a
2016/08/23 11:19:28 [error] 55#0: *6954 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /v1/kv/services/docker/hypergate/proxy_http_version?stale=&wait=60000
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: *10171 1024 worker_connections are not enough while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /v1/health/service/consul?index=1445&token=49ac0606-c9f6-4a11-a3fb-8f51d6
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough
2016/08/23 11:19:37 [alert] 55#0: 1024 worker_connections are not enough

I'm trying to make sense of how the mantlUI works. Just to be sure I understand the flow correctly:

a request arrives at my ELB, where it gets redirected to the control nodes.
There it gets load-balanced again in the mantlUI to one of the consul nginx upstreams
Then it arrives at consul-nginx, which is a docker image configured in host-mode, and runs. another nginx proxy.
that proxy then redirects it the consulUI which runs on localhost:8500.

Isn't this a very complicated process, just to get to the ConsulUI ?

We probably could eliminate a step. The consul UI/API does currently not have authentication, so we use consul-nginx on the nodes to provide access control to the local consul process.
MantlUI has a broader overview of the entire cluster.


Milestones addition

Added milestones for:

ImmutableX
ApeX
ZKSpace
Rhino.fi
Fuel v1
Optimism

Resolves L2B-474


AttributeError: 'dict' object has no attribute 'iterkeys'

in python 3.4.1 error AttributeError: 'dict' object has no attribute 'iterkeys'
row 59 - for key in c.iterkeys():

Python 2.7.8 (default, Oct 20 2014, 15:05:19)
[GCC 4.9.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> c = {'a': 1, 'b': 2, 'c': 3}
>>> for key in c: print(key)
...
a
c
b
>>> for key in c.keys(): print(key)
...
a
c
b
>>> for key in c.iterkeys(): print(key)
...
a
c
b

Python 3.4.2 (default, Oct  8 2014, 13:08:17)
[GCC 4.9.1] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> c = {'a': 1, 'b': 2, 'c': 3}
>>> for key in c: print(key)
...
b
a
c
>>> for key in c.keys(): print(key)
...
b
a
c
>>> for key in c.iterkeys(): print(key)
...
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'dict' object has no attribute 'iterkeys'
>>>

So this problem not resolve, yet? ._.

Is this library meant to work in python3?

In python 3 use dict.items()


SpotInstanceRequest doesn't respect availability_zone parameter

Hello!

Vote on this issue by adding a 👍 reaction
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Issue details
SpotInstanceRequest always defaults to "us-east-1e", even though I'm specifying a different availability zone in the parameters.  I need a different zone because my instance type isn't available in us-east-1e.
Steps to reproduce

game_server = ec2.SpotInstanceRequest(
    "Ec2_Instance_GameServer_",
    ami="ami-04505e74c0741db8d",
    iam_instance_profile=instance_profile.name,
    instance_interruption_behavior="stop",
    instance_type="m5zn.large",
    key_name="craft-mac-work",
    security_groups=["launch-wizard-2"],
    spot_type="persistent",
    wait_for_fulfillment=True,
    spot_price="0.05",
    availability_zone="us-east-1c",
    tags={"Name": "cheap-worker"}
)

Also doesn't work by specifying in LaunchTemplate...
launch_template = ec2.LaunchTemplate(
    "Ec2_LaunchTemplate_GameServerLaunchTemplate_",
    placement=ec2.LaunchTemplatePlacementArgs(
        availability_zone="us-east-1c"
    )
)

game_server = ec2.SpotInstanceRequest(
    "Ec2_Instance_GameServer_",
    ami="ami-04505e74c0741db8d",
    iam_instance_profile=instance_profile.name,
    instance_interruption_behavior="stop",
    instance_type="m5zn.large",
    key_name="craft-mac-work",
    security_groups=["launch-wizard-2"],
    spot_type="persistent",
    wait_for_fulfillment=True,
    launch_template=ec2.SpotInstanceRequestLaunchTemplateArgs(
        id=launch_template.id
    ),
    spot_price="0.05",
    tags={"Name": "cheap-worker"}
)

Expected: SpotInstanceProvider respects the availability_zone that I provide.
Actual: us-east-1e is always chosen

Possibly related to https://github.com/hashicorp/terraform-provider-aws/issues/12680?  Testing!

Confirmed!  Damn... upstream....


Xcelerator Demo Application Information and Links - Add to CONTRIBUTING.md

Siemens and Siemens Xcelerator

Siemens Xcelerator - Siemens Xcelerator - Open Digital Business Platform at Siemens
Developer Portal - Developer Documentation Hub for Xcelerator Products
Insights Hub APIs
Typescript SDK for Insights Hub
Building X APIs
Siemens iX - Design System and components

Where to get help

Siemens iX Community
Developer Portal - Ask the chatbot ;)

Hey 👋


Use locks in favour of synchronized

I think it would be better to use thread locks instead of synchronized.
https://github.com/awslabs/aws-advanced-jdbc-wrapper/blob/11bac60c308235333d645ea6e9c67ecf59bcfce3/wrapper/src/main/java/software/amazon/jdbc/authentication/AwsCredentialsManager.java#L25

Fix was merged, closing issue.


Add the modifies_memory macro

Port the opcode modifies_memory macro from https://github.com/foundry-rs/foundry/blob/1281421e04144a8de0341f9cad9b623a012a74bf/crates/evm/core/src/opcodes.rs#L5-L25
Fixes #1263

There will be some modification to that part of code when EOF PR is merged, but this lgtm!


Fix windows signing with freeDiskSpaceBeforeBuild

Fixes https://github.com/pulumi/ci-mgmt/issues/1215.

I would suggest, instead of using the login action, we should just not delete the AZ CLI that we need. This would give us the flexibility to move the signing to the makefile without needing to revert this.
The AZ CLI removal is part of the large-packages option in the action: https://github.com/jlumbroso/free-disk-space
The current disk space savings in AWS are:
=> Android library: Saved 7.6GiB
=> Haskell runtime: Saved 5.4GiB
=> Large misc. packages: Saved 6.3GiB
=> Docker images: Saved 2.5GiB
=> Overall 22GiB

This would therefore reduce to approximately 16GiB savings instead, which I think should suffice. Alternatively, we could just disable large packages on the build job only.
Of the 2 minutes spent saving disk space, 1m 44s is spent on the large packages, so disabling this option would also save a significant amount of time in each run. Which might make it feasible to turn back on for the xyz package too - to increase our test coverage.

I would suggest, instead of using the login action, we should just not delete the AZ CLI that we need. This would give us the flexibility to move the signing to the makefile without needing to revert this.

Yeah, I initially went that route but then figured 6GB was a bit too much to trade off. I'll go ahead and hook it up that way, the login action needs an additional secret anyway.


Added: OnWeekChangedListener

ADD:

OnWeekChangedListener
Demo in SwappableBasicActivityDecorated.java

hi can you release new version ? i cant find this listener

@quentin41500 Is this ever going to be released?


Check for NoneType hits_terms

PR to address #450. This should prevent the NoneType error that occurs when get_hits_terms returns None. I also chose to edit the top counts text that gets displayed so that it doesn't appear empty.
Let me know if there's anything that should be changed, and thanks for this tool!

Looks. Thanks a ton!


Nest Js Intergration

Sorry for asking a very basic question .... I am getting started on NestJs and just learned how Kafka is amazing, but on Nestjs documentation its indicated that they dont support kafka ... so am wondering can KAFKAJS work with NestJs? Is there anyone here who has tried ?  Thank you.

Hi @reviloera, it should work just fine. I haven't done anything with NestJS but there is nothing preventing you to use Kafka (with KafkaJS) on NestJS.
What they don't support is Kafka on their abstraction layer:

The NATS is a simple, high performance open source messaging system.

so you won't be able to use their abstraction to interact with Kafka, like @MessagePattern, etc.

Hi @tulios thanks for the quick response.


feat(breadcrumbs): i18n support

Description
this is the follow up PR on #48
I split the PRs so if you didn't like this one, still be able to merge the other feature
when using breadcrumbs components, I found the need to be able to translate the title
so I turned my modifications into options and made a PR out of it
I hope this helps :)

also helps toward resolving #4

Hey @jd1378, thanks for the PR!
Overall I like the direction of this, going to think if there's a way to simplify it. Will try get back to you soon.

@harlan-zw any news on this ? is there anything else I should do ?

hmm
need any help ?

Sorry for the delay @jd1378, working on a v2.
This will be merged soon, feel free to use your own component in the mean time.

this needs to be updated before getting merged, I'm facing some issues
will update it when It's stable for myself

this needs to be updated before getting merged, I'm facing some issues will update it when It's stable for myself

Happy to co-author your work once I get the v2 beta more stable! Just to give you an update I have started work on this and slowly getting my personal sites migrated over

Small update on this
The breadcrumbs are going to be moved to a separate package called nuxt-seo-ui. It's currently private while I finalise the API.


Make the Globus group endpoint configurable.

This was hard-coded into the globus_auth provider. Alejandro needs to change it to test the new facebase branding on the Globus staging site.

Added the config parameter globus_auth_group_endpoint.

@bugacov has this worked for you?  can we close the issue?

@ljpearlman can you add this parameter and its default value to the sample config and/or documentation?


Fix the option object to rollup-replace plugin

The replacement should be in the argument object, instead of nested in values property.
Fixes #7243

How did this ever work before?

The docs still say that this should be inside values: https://github.com/rollup/rollup-plugin-replace#options

Hmm.. guess it got changed when it moved under the @rollup scope: https://github.com/rollup/plugins/tree/master/packages/replace#options

How did this ever work before?
Both ways still work for me, though Jeff is seeing different result.

Both ways still work for me, though Jeff is seeing different result.

Am a little nervous moving on without knowing what the difference is..

Am a little nervous moving on without knowing what the difference is..

I think it is this
.
Just checked, the values are also still supported but not documented.  I think it is safe to go with documented way.
https://github.com/rollup/plugins/blob/9c360f0f06c3760cc72a7c6451e22e5e13aec964/packages/replace/src/index.js#L18-L20

/azp run js - mgmt - pr


iOS - getItem when device locked

Hi - Thank you for the library.
We have a requirement where we need to fetch item from keychain when device locked w/o user interaction. Tried passing -
await SInfo.getItem('itemName', {
sharedPreferencesName: 'mySharedPrefs',
keychainService: 'myKeychain',
kSecAttrAccessible: 'kSecAttrAccessibleAfterFirstUnlock',
}).then((value) => {
if (value) {
itemName = value;
}
});
But this still gives an error - reject(@"protected_data_unavailable", @"Protected data not available yet. Retry operation", nil);
Ideally when setItem and getItem have this value (kSecAttrAccessibleAfterFirstUnlock) it should be able to fetch from keychain?

@dsim1463
Hi, I faced with the same problem.
At first, getItem method in RNSensitiveInfo.m check the following value:  UIApplication.sharedApplication.protectedDataAvailable.
But this value always returns false when iPhone is locked.
So, we can never get value from Keychain in this case.
Next, in the first place, getItem method doesn't add kSecAttrAccessible option to query for getItemWithQuery.
As a result, we can't get any value from Keychain with this library now.

@ShogoSaito0607 I managed to fix it for me using the following patch with patch-package. I can submit a PR but I don't know if removing the UIApplication.sharedApplication.protectedDataAvailable check is the right solution.
diff --git a/node_modules/react-native-sensitive-info/ios/RNSensitiveInfo/RNSensitiveInfo.m b/node_modules/react-native-sensitive-info/ios/RNSensitiveInfo/RNSensitiveInfo.m
index d9b5218..efbe068 100644
--- a/node_modules/react-native-sensitive-info/ios/RNSensitiveInfo/RNSensitiveInfo.m
+++ b/node_modules/react-native-sensitive-info/ios/RNSensitiveInfo/RNSensitiveInfo.m
@@ -213,17 +213,11 @@ RCT_EXPORT_METHOD(getItem:(NSString *)key options:(NSDictionary *)options resolv
                               [self getItemWithQuery:query resolver:resolve rejecter:reject];
                           }];
         return;
+    } else if([RCTConvert NSString:options[@"kSecAttrAccessible"]] != NULL){
+        CFStringRef kSecAttrAccessibleValue = convertkSecAttrAccessible([RCTConvert NSString:options[@"kSecAttrAccessible"]]);
+        [query setValue:(__bridge id _Nullable)(kSecAttrAccessibleValue) forKey:(NSString *)kSecAttrAccessible];
     }
-
-    dispatch_async(dispatch_get_main_queue(), ^{
-        if (UIApplication.sharedApplication.protectedDataAvailable) {
-            [self getItemWithQuery:query resolver:resolve rejecter:reject];
-        } else {
-            // TODO: could change to instead of erroring out, listen for protectedDataDidBecomeAvailable and call getItemWIthQuery when it does
-            // Experiment for now by returning an error and let the js side retry
-            reject(@"protected_data_unavailable", @"Protected data not available yet. Retry operation", nil);
-        }
-    });
+    [self getItemWithQuery:query resolver:resolve rejecter:reject];
 }

 - (void)getItemWithQuery:(NSDictionary *)query resolver:(RCTPromiseResolveBlock)resolve rejecter:(RCTPromiseRejectBlock)reject {

i have still same problem when i try to use kSecAttrAccessibleAfterFirstUnlock and still when i locked the app i lost item value any idea

@ahmeturganci were you able to fix that? I may have the same issue