update protostuff to 1.5.2

That version provides better perf (especially on deser) on data with collections.

Thanks @dyu


Fix pull request template link

This is a bit meta, but your Github PR template links to a nonexistent CONTRIBUTING.md. This PR fixes that.

Gotcha 🥇
Thank you, didn’t saw this when moving file.

Picked as 208345a  -- thanks!


Fixed bug where a role with a dot in its name could not be deleted.

Fixes issue described in this hois-core ticket: https://github.com/xh/hoist-core/issues/370
Breaking change due to corresponding required change in hoist-core
Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[x] Caught up with develop branch as of last change.
[x] Added CHANGELOG entry, or determined not required.
[x] Reviewed for breaking changes: BREAKING CHANGE
[x] Updated doc comments: not required.
[x] Reviewed and tested on Mobile: not required.
[ ] Created Toolbox branch / PR: not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

Checked and last HR release we had that required a HC change was v64, the big multi-instance upgrade. Same story in the other direction (HC requiring HR).
Given small/targeted nature of this fix, it would be nice if we didn't need to force a breaking change, but at the same time the upgrade on both sides should be easy - if you have gotten to this point, both sides are trivial updates relative to what you have.
If we really wanted to, we could have the delete method here check the HC version and swap its impl, likewise on the HC side we could look for body vs. params. But given the above I do NOT think that's warranted. Just wanted to talk it out here in the PR.
Let's check in with @lbwexler as we were planning releases for as soon as today to confirm if we're good with both sides bumping up.

I don't think this fix is urgent.  I don't need it in the project I am working on right now.  No one else has found this bug.  I think we can wait and merge it in when the correlation id change is merged in, since that change also requires coordination between Hoist React and Hoist-Core.

I think we can wait and merge it in when the correlation id change is merged in, since that change also requires coordination between Hoist React and Hoist-Core.

Great idea, all for it!


Correction to powershell code

$Identity = 'CONTOSO\mdisvc'
This line should be changed to
The service account should have a $ sign appended to it - mdisvc$

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 12a9a5e8-afc3-7554-6a0b-248fae64a53f
Version Independent ID: 12a9a5e8-afc3-7554-6a0b-248fae64a53f
Content: Directory Service account recommendations - Microsoft Defender for Identity
Content Source: ATPDocs/directory-service-accounts.md
Service: microsoft-defender-for-identity
GitHub Login: @batamig
Microsoft Alias: bagol

Hi @LijuV-MSFT and thanks for your comment! @martin77s, can you confirm this before I update?

No. It's incorrect.
The reference on the (group managed) service account is stated right above that line:
"# Note that if the identity you want to grant the permissions to is a Group Managed Service Account (gMSA),
you need first to create a security group, add the gMSA as a member and list that group as the identity below"

Thanks @martin77s.
@LijuV-MSFT, please let us know if you have any more questions about this.


Update usage instructions

The current "usage" instructions aren't up to date with the latest version of labs-ci-cd. In addition, ci-playbook.yaml looks for openshift-applier in the wrong location.
This PR:

Updates the command in the readme to cover the latest version of labs-ci-cd
Adds notes on potential pitfalls with SELinux and project names
Fixes the location of applier in ci-playbook.yaml.

These changes are intended as a stopgap to get things working until the new containerized workflow is ready to go.

@rdebeasi fyi - this is out of date with #125 merged. we can discuss in person how to update the docs

I've updated the PR to cover the new playbooks. The changes now affect just the readme. (The ci-playbook.yaml changes are whitespace only.)
The new readme should address one of the items rom #113:

Discuss using the ci-playbook.yaml to test in a cluster that other users are testing in. there is no need to run in a local cluster

looks like CI fail is related to storage issues in the env. will wait for those to be resolved and then re run


Create status box for overdue responses that haven't been pulled via API [API v2 QA]

Description
If responses aren't retrieved with API selected as delivery method, they will become overdue like in "vault mode". This will need to be communicated with next steps to the client who will receive nagware etc.
Expected behaviour
A status box indicating that there are overdue responses and what to do next.
Consider revising the alerts that get shown for "Download" to mirror for "API" delivery method.
Additional context
We may also consider more detailed guidance for the retention of data and timelines for transparency.
Ideas
Something like this?

PR
https://github.com/cds-snc/platform-forms-client/pull/4767


drop support for extra response parameter for handlers decorated by @template

@template should be applied to coroutines that are accept only one position argument request.
Processing optional response param makes a mess.

Fixed


DNN-6439 Update jQuery UI JavaScript from 1.10.3 to 1.11.2

I ran dnn.js through uglify, not sure if there's a standard minifier that is used
This commit doesn't attempt to update CSS, but I didn't see any immediate red
flags when looking through the DNN form pattern (dialogs, tabs, section expand/collapse)

reviewed looks good (good to see the temporary code removed also) - merging into 7.4.1

im going to revert part of this change as it doesn't work - modal dialogs are no longer centered.

tested this again with jquery-ui 11.1.2 and jquery 11.1.3 and both still cause the modal windows to render in the bottom left of the screen. I tried debugging and couldn't see a quick resolution to this, so I am going to revert this pull request fully.

I created a new pull request with a correct fix for the modal dialog
https://github.com/dnnsoftware/Dnn.Platform/pull/330


ATTR_SUGGESTIONS hangs graph fix

Took over 10 min to run on one client's graph, causing it to hang.
Going to merge right away to fix the hang

👍


Added more details to query context to track query specific information including timers. Updated code to use TimerContext from query request to record times  for different phases of query.

Current coverage is 64.24% (diff: 83.63%)

No coverage report found for master at bca3a4a.

Powered by Codecov. Last update bca3a4a...0c53f95


How I can use this gem to start jruby server then sidekiq daemon running as same process

Hi,Thanks for this gem .but how i use it?
How I can use this gem to start jruby server then sidekiq daemon running as the same process?

Your use case isn't what the gem is about. This gem is used to start sidekiq with daemonization which means that you start it using sidekiq-daemon instead of sidekiq and it will automatically detach from the terminal and continue running in the background.


rm: Added descend messages for interactive mode Fixes #3817

Added descend functionality for rm's interactive mode
Setup
mkdir -p a/b/
touch a/at.txt a/b/bt.txt
rm -ri a

Current
rm: remove file 'test/a/b/bt.txt'? y
rm: remove file 'test/a/at.txt'? y
rm: remove directory 'test/a/b'? y
rm: remove directory 'test/a'? y

GNU
rm: descend into directory 'a'? y
rm: descend into directory 'a/b'? y
rm: remove regular empty file 'a/b/bt.txt'? y
rm: remove directory 'a/b'? y
rm: remove regular empty file 'a/at.txt'? y
rm: remove directory 'a'? y

After Commit (Using the same answers as before)
rm: descend into directory 'test/a'? y
rm: descend into directory 'test/a/b'? y
rm: remove file 'test/a/b/bt.txt'? y
rm: remove file 'test/a/at.txt'? y
rm: remove directory 'test/a/b'? y
rm: remove directory 'test/a'? y

After Commit (Don't descend into a/b)
rm: descend into directory 'test/a'? y
rm: descend into directory 'test/a/b'? n
rm: remove file 'test/a/at.txt'? y
rm: remove directory 'test/a'? y
./uutils/target/debug/rm: cannot remove 'test/a': Directory not empty

it would be nice if you could make GNU's test rm3.sh & rm5.sh work as they are also testing the
"descend into directory" thing.
bash util/run-gnu-test.sh tests/rm/rm3.sh
and
bash util/run-gnu-test.sh tests/rm/rm5.sh

For making a regression test do you guys know/have an example test where you interact with the child process stdout and stdin?
Progress report for the test:
I looked at rm3.sh and will have to look deeper and see what it is doing
For rm5.sh I should be able to fix it. It is currently failing because GNU doesn't ask to descend if the directory is empty

Just looked at rm3.sh and it seems to only be falling because our prompts aren't as descriptive as gnu.
For example GNU for an empty file with prompt:
rm: remove regular empty file 'z/empty'
While ours is just:
rm: remove file 'z/empty'
I might make that into a separate PR to give our prompts better descriptions

For making a regression test do you guys know/have an example test where you interact with the child process stdout and stdin?

Would the pipe_in method work?

I might make that into a separate PR to give our prompts better descriptions.

Yeah a separate PR makes sense I think.

Unfortunately, that won't work for this use case where the command waits for responses and does something different depending on it

Okay, I have created a very basic test for checking directory descending.

There seems to be some trouble on macos and windows:
test test_rm::test_rm_descend_directory has been running for over 60 seconds

So, the reason it was hanging up is because of CRLF vs LF when I was inserting it into stdin. I also had to remake the test because of something I noticed with WalkDir that depending on the system the order in which it traverses can differ.

Nice
Congrats! The gnu test tests/rm/rm5 is no longer failing!


cni: Use batch endpoint deletion API in chaining plugin

This commit is to leverage new batch endpoint deletion API instead of singular endpoint deletion based on ID. The main reason is to provide backward compatibility on upgrade path.
The current CNI attachment ID requires a valid containerIfName attribute, however, the endpoints created by old cilium versions (e.g. <1.15) are not having such details. Any CNI DEL command for these endpoints will lead to invalid lookup (e.g. DeleteEndpointIDNotFoundCode), and prevent cleaning up of related resources such as IP addresses.
The impact is only limited to CNI chaining mode, as batch endpoint deletion API is already used cilium-cni/cmd/cmd.go as part of #27351.
Old endpoint details without (or empty) ContainerIfName
{
  "ID": 423,
  "ContainerName": "",
  "dockerID": "415beb119c4b0910f62634510e921a447893195ebedc30ca0e9cd5bf02569645",
  "DockerNetworkID": "",
  "DockerEndpointID": "",
  "IfName": "eni22524e9e591",
  "IfIndex": 13,
  "ContainerIfName": "",
  "DisableLegacyIdentifiers": false,
  ...
}

New endpoint details with valid ContainerIfName (e.g. eth0)
{
  "ID": 3627,
  "ContainerName": "",
  "dockerID": "f89ccf654b878248442981d4c56fe3f50fa127f922b46ee6dccc94ae10e94b79",
  "DockerNetworkID": "",
  "DockerEndpointID": "",
  "IfName": "enia67a2d3c27d",
  "IfIndex": 45,
  "ContainerIfName": "eth0",
  "DisableLegacyIdentifiers": false,
  ...
}

Relates: #26894, #27351
Suggested-by: Sebastian Wicki<EMAIL_ADDRESS>

/test


Using math::SpeedLimiter on the diff_drive controller.

Signed-off-by: LolaSegura<EMAIL_ADDRESS>Summary
This replace the diff_drive controller speed limiter class for the one implemented in ignition math. Part of #810.
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[x] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸

this is looking good!
it's helpful to cross-reference issues from pull requests, so I would add that this is "Part of https://github.com/ignitionrobotics/ign-gazebo/issues/810" in the pull request description

I noticed that codecov is complaining about test coverage. We are not strict about requiring code coverage, but I think we can easily increase this for this test. I believe the diff_drive system has the following integration test:

https://github.com/ignitionrobotics/ign-gazebo/blob/ign-gazebo3/test/integration/diff_drive_system.cc

The test uses several different world files (search for test/worlds to find lines like this) such as test/worlds/diff_drive.sdf. This world has a plugin that specifies max_acceleration and max_velocity, but doesn't specify min_acceleration or min_velocity. If we added min_acceleration of -1 and min_velocity of 0.5, that will improve the coverage and add symmetry to the test. To get even more coverage and without changing the dynamics of the system we could add a min_jerk value of -Inf and a max_jerk value of Inf (I think that will work).
Since these are easy changes to improve code coverage, do you mind giving them a try? Thanks!

If we added min_acceleration of -1 and min_velocity of 0.5, that will improve the coverage and add symmetry to the test.

@scpeters  here when you mentioned the min_velocity did you meant to write -0.5? Because otherwise it would take the same value as the max_velocity.

If we added min_acceleration of -1 and min_velocity of 0.5, that will improve the coverage and add symmetry to the test.

@scpeters here when you mentioned the min_velocity did you meant to write -0.5? Because otherwise it would take the same value as the max_velocity.

thanks for catching that; I meant to write -0.5

@LolaSegura . I've tried it locally.

It seems that just adding the min_jerk and max_jerk properties are causing a miss behavior in the diff drive when moving forward(probably backward too).
Leaving those properties commented out the test moving forward works fine.
It is failing only one test when moving backward:

Expected: (expectedLowerPosition.Y()) < (expectedGreaterPosition.Y()), actual: 0.710173 vs 1.40412e-12

Re-check the desire angle you are publishing.

It is ready for review @scpeters

To get even more coverage and without changing the dynamics of the system we could add a min_jerk value of -Inf and a max_jerk value of Inf (I think that will work).

I try adding this limits as well, but I encounter a problem because when being parsed the limits where interpreted as zero, causing the test to fail. An option would be setting the <max_jerk> with a big value and the <min_jerk> with a small one to get more test coverage.

thanks for testing this; I just looked into it a bit deeper and found that it is a parsing issue with libsdformat (https://github.com/osrf/sdformat/issues/261).


Bump basicauth dependency version

Bump basicauth dependency version from 6.7.2 -> 6.7.3

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/3565427482

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/3565427482
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/3566696456

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/3566696456
Status: success

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/3566695548
Status: cancelled

Closing as this is bumped with https://github.com/wso2/product-is/pull/15230


Rename PSQLBackendMessage to PostgresBackendMessage

Motivation
We want to drop the PSQL prefix.
Changes

Rename PSQLBackendMessage to PostgresBackendMessage

Codecov Report

Merging #238 (6c7f68f) into main (63e7d57) will increase coverage by 1.60%.
The diff coverage is 71.87%.

@@            Coverage Diff             @@
##             main     #238      +/-   ##
==========================================
+ Coverage   39.82%   41.43%   +1.60%
==========================================
  Files         116      114       -2
  Lines        9413     8802     -611
==========================================
- Hits         3749     3647     -102
+ Misses       5664     5155     -509

Flag
Coverage Δ

unittests
41.43% <71.87%> (+1.60%)
:arrow_up:

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

Impacted Files
Coverage Δ

...es/PostgresNIO/Connection/PostgresConnection.swift
0.00% <0.00%> (ø)

...w/Connection State Machine/CloseStateMachine.swift
0.00% <0.00%> (ø)

...rces/PostgresNIO/New/Messages/Authentication.swift
75.00% <ø> (+15.62%)
:arrow_up:

...rces/PostgresNIO/New/Messages/BackendKeyData.swift
100.00% <ø> (ø)

Sources/PostgresNIO/New/Messages/DataRow.swift
95.58% <ø> (+4.41%)
:arrow_up:

...ostgresNIO/New/Messages/ParameterDescription.swift
100.00% <ø> (ø)

...ces/PostgresNIO/New/Messages/ParameterStatus.swift
100.00% <ø> (ø)

...urces/PostgresNIO/New/Messages/ReadyForQuery.swift
100.00% <ø> (ø)

...rces/PostgresNIO/New/Messages/RowDescription.swift
100.00% <ø> (ø)

Sources/PostgresNIO/New/PSQLChannelHandler.swift
60.53% <ø> (+10.86%)
:arrow_up:

... and 43 more


Add helper function Dirent.FollowSymlink()

Added a helper function for handling symlinks to Dirent. This function can be used as follows:
    err := godirwalk.Walk("./example", &godirwalk.Options{
        FollowSymbolicLinks: true,
        Callback: func(path string, de *godirwalk.Dirent) error {
            // resolve any symlinks we encounter to their linked filepath
            de, err := de.FollowSymlink()
            if err != nil {
                return err
            }

            log.WithFields(log.Fields{
                "path":      path,
                "IsRegular": de.IsRegular(),
                "IsDir":     de.IsDir(),
                "IsSymlink": de.IsSymlink(),
            }).Info("")

            return nil
        },
    })

This is useful because without following the symlink via filepath.EvalSymlinks() and creating a new Dirent, then the original Dirent on some systems will return de.IsSymlink() // true and de.IsDir() // false and de.IsRegular() // false, which can cause accidental mistakes. By using de.FollowSymlink() you can then be confident that de.IsDir() and de.IsRegular() will now return stat information about the followed symlink.
This PR also includes adding Dirent.Path() and Dirent.path to support absolute paths when following the symlink.
Note: There exists a subtle flaw in that you can't reassign and initialize a variable in the same := or = in golang, so instead these must be separated out. :/ The other option is to pre-declare both variables such as var err error or adding it to the function proto.

Can you provide a mini file system example that led you down the path of adding this functionality?
There is nothing in the new FollowSymLinks method that requires it to have internal representation of the Dirent structure. This method could very well be implemented in the callback:
		Callback: func(osPathname string, de *godirwalk.Dirent) error {
			// resolve any symlinks we encounter to their linked filepath
			if de.IsSymlink() {
				resolvedPath, err := filepath.EvalSymlinks(osPathname)
				if err != nil {
					return nil, err
				}
				absPath, err := filepath.Abs(resolvedPath)
				if err != nil {
					return nil, err
				}
				de, err = NewDirent(absPath)
				if err != nil {
					return nil, err
				}
			}

			log.WithFields(log.Fields{
				"path":      path,
				"IsRegular": de.IsRegular(),
				"IsDir":     de.IsDir(),
				"IsSymlink": de.IsSymlink(),
			}).Info("")

			return nil
		},

Or implemented as a function in a given program.
func NewDirentByFollowingSymlinks(osPathname string, de *godirwalk.Dirent) (*godirwalk.Dirent, error) {
	resolvedPath, err := filepath.EvalSymlinks(osPathname)
	if err != nil {
		return nil, err
	}
	absPath, err := filepath.Abs(resolvedPath)
	if err != nil {
		return nil, err
	}
	return NewDirent(absPath)
}

Then in the Callback, you could call this function:
		Callback: func(osPathname string, de *godirwalk.Dirent) error {
			// resolve any symlinks we encounter to their linked filepath
			if de.IsSymlink() {
				var err error
				de, err = NewDirentByFollowingSymlinks(osPathname, de)
				if err != nil {
					return nil, err
				}
			}

			log.WithFields(log.Fields{
				"path":      path,
				"IsRegular": de.IsRegular(),
				"IsDir":     de.IsDir(),
				"IsSymlink": de.IsSymlink(),
			}).Info("")

			return nil
		},

I have two primary and two minor concerns with adding this into godirwalk right now. My first concern is expanding the API without my clearly understanding the benefit of doing so, especially in light of the two alternate solutions I have provided above.
My second concern flows from the first. If we added FollowFromSymlink to the API, it has limited use because not everyone would necessarily want to create a new Dirent from the absolute pathname, but maybe simply the resolved path.
My third concern is minor, but storing the entire pathname in each Dirent structure adds memory churn, when it might not always be required.
Finally my final concern is some of the API calling semantics of the proposed FollowSymlink method. It calls by value rather than by pointer, making a copy of the Dirent, only to return a pointer of itself if the entry is not a symlink. Then for all of the error conditions, it returns a copy of the copy of the entry along with the error. This is a problem because it allows sloppy programming, where a user might not bother checking the error and might just check the first return value for something. Finally, in the happy case, it calls NewDirent which just allocates yet another chunk of RAM for the new Dirent instance.

Thanks for the review.
I'll address the minor concerns first about memory and relative path:

For the value receiver vs. pointer receiver, that can be changed and was simply a copy/paste from the other functions in dirent.go, I agree that a pointer receiver is better in this case.
For returning a new Dirent vs changing the underlying Dirent received via pointer, this is initially how I wanted to implement this but got different feedback from an private review first. I think that we could receive a pointer to FollowSymlink() and it would change the underlying dirent to receive information about the new node on the filesystem. Either way is fine with me.
For the extra pathname being stored, I found it strange that a Dirent doesn't know where it came from or how to represent itself, it's like it only stores the information related to some basic filesystem info. I think adding in path for Dirent in general would be a good choice to allow for more flexibility in this library

Why should we add this feature at all?
The use case that led me to this library is being able to walk filepaths in golang with the ability to interact with symlinks. This library is the most full featured and user friendly, and I think this additional API fits with godirwalk's calling card of "interacts with symlinks".
I could write an internal function that extends this api only in my one project, but I want to share this ability with the world and share in the user friendly functionality. Just knowing that a path is a symlink is great, because now we can interact with it, and being able to directly interact with symlinks as a first class citizen of this library is a cherry on top in my opinion. And that's why I sought to add this feature to godirwalk.
Clarification:

If we added FollowFromSymlink to the API, it has limited use because not everyone would necessarily want to create a new Dirent from the absolute pathname, but maybe simply the resolved path.

What do you mean by this where someone would only want to visit the symlink on the resolved path? In my understanding symlinks (as they're soft links) represent a relative path to another path on the system that must have an absolute representation. These symlinks could be relative to another relative path to the originating path used in the call to Walk() but it could also not be relative to that, so I'm a bit confused on what you mean by the resolved path as a resolved path may not exist relative to the original path for all symlinks we encounter while walking?


upgraded to 2.0.0

Good news please don't forget npm :)

@dougludlow I need dis

looks like the tests fail randomly

I think you should now trust to the Angular 2 following the semantic versioning and use ^ in dependencies. Also there is currently the ^ for @angular/forms for some reason.

@damiandennis, @jbrekle, @RoopeHakulinen - Thanks a ton guys. I pulled in these changes manually and updated the tests to use the Angular2 and everything should be good to go in v0.9.2.


Missing resource?

When building and trying to include the 1.2 version I'm getting the following error:
Error:(3, 5) No resource found that matches the given name (at 'android:actionModeCloseDrawable' with value '@drawable/abc_ic_ab_back_mtrl_am_alpha').
Thoughts?

OK, false alarm, the compile directive needed a @aar and it built...

https://github.com/javiersantos/AppUpdater/commit/846be26fa679bcb1ff2cac7a0dfa7fd788d075af


Added ability to send messages to contacts

The message input and send works now, though we'll probably have to drastically change the code when the database is set. Of course, since the database isn't done yet (as far as I'm aware), all the new messages sent won't persist when you refresh the page. When a new message is sent, the message log will automatically scroll down to the new message. Also, submitting a new message automatically clears the form so that users don't have to delete everything they already sent.
Also, I renamed the parameter for MessageLog function in MessageLog.jsx from stuff to parameters.

Actually since theres no overlap between main files, just gotta change the eslint error I believe.

Wait, what's the eslint error?

You added a space to the end of local variables I think


Sphinx Search Adapter

Just wondering if you would be interested in a Sphinx Search Adapter -- it technically isn't a database, but it speaks the MySQL protocol but the query language is similar but different: http://sphinxsearch.com/docs/current.html#sphinxql-reference

Hi Robert,
Yeah if you would like to work on a SphinxQL adapter, that would be cool.
Im assuming you can just use the MySQL driver to execute queries?
-Doug

Correct.  Just needs different query syntax & rules.


[UX/UI] Dates clipped in filters panel

Rounder dates are clipped by the up/down buttons. Can be resolved by decreasing right margin of the input boxes. Screenshot: https://drive.google.com/file/d/13YeywtdrewF89apuRHxjAlaBIoBDPEzA/view?usp=drive_link

@wrenaria this should be ready to test on dev.


Improve qiskit-card when on mobile

Motivation
We have a custom .. qiskit-card:: directive that Sphinx users can write to create a card element:
https://github.com/Qiskit/qiskit_sphinx_theme/blob/43d744242947cdc54d5a6f281b51a3acec92a571/example_docs/docs/sphinx_guide/custom_directives.rst?plain=1#L32-L42
That results in this style:
https://github.com/Qiskit/qiskit_sphinx_theme/blob/43d744242947cdc54d5a6f281b51a3acec92a571/tests/js/qiskit.test.js-snapshots/custom-directives-1-linux.png
https://github.com/Qiskit/qiskit_sphinx_theme/blob/43d744242947cdc54d5a6f281b51a3acec92a571/tests/js/qiskit.test.js-snapshots/custom-directives-3-linux.png
But these aren't fully complying with Carbon. While it was "good enough" for Furo 1.0, we'd like to better align with Carbon and qiskit.org. We especially want to improve the mobile design. See https://github.com/Qiskit/qiskit_sphinx_theme/pull/447#discussion_r1250583747.
How to try out the current setup
Follow https://github.com/Qiskit/qiskit_sphinx_theme/blob/main/CONTRIBUTING.md#run-locally and specifically use tox -e qiskit. In the example site in your browser, navigate to Custom Directives

~# Approach 1: use a web component~
~This is probably the best option. Follow the guide at https://github.com/Qiskit/qiskit_sphinx_theme/blob/main/CONTRIBUTING.md#updating-bundled-web-components for adding new web components.~
~For step 4, you will update the HTML here to instead be the new HTML element:~
https://github.com/Qiskit/qiskit_sphinx_theme/blob/43d744242947cdc54d5a6f281b51a3acec92a571/src/qiskit_sphinx_theme/directives.py#L51-L57
~See how we do the top nav bar for inspiration:~
https://github.com/Qiskit/qiskit_sphinx_theme/blob/43d744242947cdc54d5a6f281b51a3acec92a571/src/qiskit_sphinx_theme/theme/qiskit-sphinx-theme/page.html#L14-L16
~You'll also want to remove our custom code in _custom-directives.scss for qiskit-card.~
Approach 2: improve our styling to align with Carbon
This looks like changing the code in _custom-directives.scss, and possibly the HTML in directives.py, to better align the style with Carbon.
You'll probably want to look at the underlying HTML and CSS from Carbon. Note that I did not do this. I based all the current code on the old Pytorch code for cards, which was custom.
Reminder to use tox -e qiskit every time you make a change to see how it renders.

On-hold until we know exactly what happens with qiskit docs

Given that we are deprioritizing the qiskit theme and focusing on Qiskit Ecosystem, this is less important. The current implementation is "Carbon-compliant" enough for the Ecosystem.


Update cmdline-tools path

Hi,
Latest bump (5 months ago to current latest as of today) has changed the cmdline-tools path location.

Thanks mate for your contribution.
This is indeed a new issue, which I observed as well last night from one failed CI job, after bumping up Android SDK version from 6609375 to 6858069.
I'll check it out.

yup all makes sense @thyrlian - done thanks 👍

BTW, for future reference:
I've tested if we keep the nested/redundant cmdline-tools/cmdline-tools structure, once executing SDK update, it will mess up the tree structure (with below output):
Warning: Package "com.android.repository.impl.generated.v1.RemotePackage@b2d2115" (patcher;v4) should be installed in "/opt/android-sdk/patcher/v4" but it already exists.
Installing in "/opt/android-sdk/patcher/v4-2" instead.

Warning: Package "com.android.repository.impl.generated.v1.RemotePackage@862a774c" (emulator) should be installed in "/opt/android-sdk/emulator" but it already exists.
Installing in "/opt/android-sdk/emulator-2" instead.

Warning: Package "com.android.repository.impl.generated.v1.RemotePackage@5f48a0aa" (platform-tools) should be installed in "/opt/android-sdk/platform-tools" but it already exists.
Installing in "/opt/android-sdk/platform-tools-2" instead.

Just figured out, the problem was from the command sdkmanager --list.  I'll fix it now.

Here is the diagnosis:
With the barebone Android SDK, the sdkmanager is located at $ANDROID_SDK_ROOT/cmdline-tools/bin/sdkmanager, and under $ANDROID_SDK_ROOT/cmdline-tools/ there are only NOTICE.txt,  bin,  lib,  source.properties.  But when running sdkmanager --list, it flubs:
Error: Could not determine SDK root.
Error: Either specify it explicitly with --sdk_root= or move this package into its expected location: <sdk>/cmdline-tools/latest/

In fact, the expected tree structure <sdk>/cmdline-tools/latest/ would only appear after updating the SDK, thus I fixed the issue temporarily by passing the --sdk_root=$ANDROID_SDK_ROOT flag.  I would rather wait for Google to fix it properly.

Build succeeded with the fix.

ah yup - seeing that -

Would it be better to put into /latest?

I'm working on this, but not that optimistic.  The problem is, this suggested path only shows up after a manual SDK update.  Before that, you would only be able to find the old path - cmdline-tools/bin.
Probably I'll add both paths to environment variables, with a higher priority for the expected one, and do a cleanup once Google fix this.


Investigate switching Python linting to ruff

Seems like we can replace all existing linters and tooling with ruff
https://github.com/charliermarsh/ruff

Closed by https://github.com/rerun-io/rerun/pull/1378


Create cQube-4.0-Alpha branch in cQube_Edu Repository

To move all the cQube related code to "cqube-4.0_alpha"

All codes are moved to "cqube-4.0_alpha"


Fixing broken link

fixed broken link(404) to point to similar helpful page

Please make sure /en-us/ is not in any links as that is a language specifier. Without a language specifier in URL the page will open in whatever language the users web browser is set to use.
Let's confirm with @CarolynRowe if the link is correct too.

There have been a few cases lately of links that HAVE to go to en-us or they 404, usually  links to the product catalog.

@jambirk - seems to work fine for me: https://docs.microsoft.com/skypeforbusiness/skype-for-business-hybrid-solutions/plan-your-phone-system-cloud-pbx-solution/plan-phone-system-with-on-premises-pstn-connectivity    Are you getting a 404?

No, that one works okay for me. I think it's just links away from docs but still within microsoft we may need to worry about.


React 16.2 fragment syntax triggers

Reacr 16.2 introduced fragments. This feature is accompanied by a syntactic sugar. The following component is now valid in React:
import React from 'react';

export default () => (
  <>

  </>
)

When using the default ESLint parser, this causes a syntax error.
When using the babel-eslint parser, this triggers the quotes rule.

Any update?

You can try
jsx

import React, { Fragment } from 'react';

export default () => (
  <Fragment>

  <Fragment/>
)

Of course we can use Fragment component but that is not the point here. We want to use fragment shorthand.
https://reactjs.org/docs/react-api.html#reactfragment

Maybe you can use a workaround like, create a component named "f" and make it import fragment from react and pass down its prop children. This way you can use  not sure if this will work

Maybe you can use a workaround like, create a component named "f" and make it import fragment from react and pass down its prop children. This way you can use <f></f> not sure if this will work

Or you can just import fragment under the same "f" and alias 😂

Note: Fragment is only working for babel-eslint@^8, v7 doesn't support that, as wrongly stated on the React Fragment blog post.
eslint can be any bigger than 3
https://reactjs.org/blog/2017/11/28/react-v16.2.0-fragment-support.html#eslint

@fabiomcosta nope that still triggers the quotes rule

"babel-eslint": "^8.2.2",
"eslint": "^4.19.1"

The latest ones still have quotes error.

Just an update, this issue isn't with babel-eslint itself, as there isn't really anything we need to do related to parsing, the quotes rule itself doesn't know how to handle JSXFragment node types.
Until it get updated in ESLint proper (can track via the linked thread above), I've added a new quotes rule in eslint-plugin-babel that won't trip on JSX shorthand syntax.

Published with https://github.com/babel/eslint-plugin-babel/releases/tag/v5.0.0
It has a peerDep on ESLint 4.

Still getting the Strings must use singlequote error with:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
Finding it very difficult to debug why.

@jaydenseric did u try with babel 9 as stated above?

did u try with babel 9

I think you mean Babel v7 beta?
It's a<EMAIL_ADDRESS>project, which has the dependency<EMAIL_ADDRESS>I tried manually adding the latest Babel v7 to my project dependencies, but it didn't help.

Still getting the Strings must use singlequote error with:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
Finding it very difficult to debug why.

Same here with
<EMAIL_ADDRESS><EMAIL_ADDRESS>

any update?

not reproduced with:
"babel-eslint": "~10.0.1",
"eslint": "~5.11.1",

the package that comes with Create React App, react-app fix it.

Issue is still present for me.
"@babel/core": "^7.2.2",
...
"babel-eslint": "^10.0.1",
...
"eslint": "^5.13.0",

Until it get updated in ESLint proper

@existentialism I don't think this is the case anymore since ESLint 5 released but I'm not 100% sure. Seems like it from this discussion https://github.com/eslint/eslint/issues/9662


SRAM macros for Open MPW

Hi, I generated SRAM macros with OpenRAM, since I needed nearly 40 kB of RAM and it is almost impossible to provide it with 2 kB macros. I got Magic DRC errors and asked about it in the sky130 Slack channel. They told me that SRAM macros commonly have this issues and reccomended to turn off Magic DRC check while running user_project_wrapper. The flow passes but I have problems in precheck due to DRC issues. I also asked about it in the Slack channel and they told me that SRAM macros in the PDK directory are automatically excluded from DRC check, but they were not sure if users can add custom SRAM macros. Am I allowed to add my custom SRAM in caravel user project? If yes, how can I make the precheck tool to exclude my SRAM too?

Hi,
The DRC issues in precheck are on the eFabless end and you should talk to them. We generate the macros, but need their help on integration in the flow.
In terms of the very large memories, we are still verifying them. I can't guarantee anything works, but we are confident in the 1kbyte and possibly 2kbyte and 4kbyte.

I also opened the same issue in caravel_user_project repository, but I haven't got any answers yet. Just in case I am able to implement generated SRAMs in user project area, how can I verify my SRAM?

As far as I know, DRC issues with SRAM macros are common. So you should turn off Magic DRC when running user project wrapper. In the precheck stage checker excludes SRAM macros to ignore these DRC issues, thus your design will pass successfully. But I must indicate that I know this from slack discussions and my examinations on precheck scripts, I have not personally tried it yet.


🔥 API feature: Streaming option (JSON-lines)

Provide an option to get the iterator of the answers.
We can use cache_target variable for that (state None)

[x] optional tqdm

There is a still limitation for iterative data processing in the case when we caching information.


Add build status badge.

Remove bare link to build status and add a Travis CI badge, which both
links to and displays build status.

Thanks for correcting the Travis CI badge here Chris! It looks like I messed it up when switching from our private Travis to public Travis


Publish 7.1.0 to npm

It looks like the latest version on npm is still 7.0.4 at the moment.  Just tossing this in as a reminder.

Crap, thanks. I meant to do that last night.

I really wish there was a reasonable way to publish NPM from Travis.

Done.


feat: Update Makefile for packaging

includes:

use .PHONY targets only for convenience
silence build (only command-output; V=1 will print all commands)
build fully out-of-tree
build .so and .a files to allow for linking
install/uninstall rules for packagers
unified test building and running

NOTE: this commit also disabled the benchmark test because it appears to be broken (it calls poly1305_auth() which does not exist).
Closes: #1

You mentioned (in #1), that we might have to account for different architectures; did you mean CFLAGS-wise (e.g., -march=native and the like?) or did you mean something else?

You mentioned (in #1), that we might have to account for different architectures; did you mean CFLAGS-wise (e.g., -march=native and the like?) or did you mean something else?

You mentioned (in #1), that we might have to account for different architectures; did you mean CFLAGS-wise (e.g., -march=native and the like?) or did you mean something else?

I think I was mistaking the fact that you wanted to make static binary releases next to the source release.

I will try to take a look at your feedback this weekend!

Sorry for the delay! I fixed a few things that you requested, but I'm at a minor impasse on how to handle the final question (how to recursively discover files that is portable across host OSes.

I think it looks fine, thank you for taking the time, I'm gonna merge the new version now.

Damn, it breaks the build. I should have defined the GA to also build on pull-requests.

Oooh, that's my fault entirely (I didn't even notice that you had a CI workflow setup—my changes definitely changed the command slightly that you'd use to cut a new release). Feel free to revert the merge if you'd like and I'll ensure that the CI will work as-intended on-merge!

Are you okay with creating a new PR with the fix? that's less messy

I'm happy to, it might just need to wait till tonight (which is why I mentioned I'd be fine with the reversion). Completely up to you and I'm happy to fix my mistake either way ☺

Ok, looking forward to it new pr ;)
On Mon, 24 Jan 2022, 17:39 Sam Stuewe, @.***> wrote:

I'm happy to, it might just need to wait till tonight (which is why I
mentioned I'd be fine with the reversion). Completely up to you and I'm
happy to fix my mistake either way ☺
—
Reply to this email directly, view it on GitHub
https://github.com/DavyLandman/portable8439/pull/2#issuecomment-1020297932,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABL3E3F5BP2OZSYLPQHIO3UXV6EJANCNFSM5LCHBBHQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message
ID: @.***>

@DavyLandman I have most of the issues fixed for the workflow, but it looks like the algamized-test expects to get the go-package golang.org/x/crypto/chacha20poly1305 but cannot find it. Is that something that is handled fine on GitHub automatically?

@DavyLandman I have most of the issues fixed for the workflow, but it looks like the algamized-test expects to get the go-package golang.org/x/crypto/chacha20poly1305 but cannot find it. Is that something that is handled fine on GitHub automatically?

I think go should download it automatically, if you have the right version of go installed.


email notifier improvements

The email notifier uses email address in the config section header which ends up as key.  This which prevents having different notifiers with the same email address.
going to the same email address.

Replaced email address with a group name, and removed check that section header is an email address.
Add to email address as config item to.

The email notifier will only send a notification when all consumer groups fail.  To address this I added an option on the config on-single-fail to send notifications when any of the consumer groups fails.

should prob refactor to remove all the references to
"github.com/jeffmontagna/Burrow/"

Resolved by 1.0 rewrite


Map the Debris - altitude and orbital velocity values not matching for Moon

Challenge Name
https://www.freecodecamp.com/challenges/map-the-debris
Issue Description
Hi,
This is regarding the "map the debris" challenge.
In this, I have used the formula as per wikipedia, to calculate the orbital period given the semi major axis (radius of the earth + altitude of the object) and the GM value (as O = 2PISQRT(R^3/GM)).
This computes correctly for the test values given for sputnik, iss and hubble. However, it if off by 6 metres from the value given as the answer for moon.
I tried to tweak the input value, and found that about 0.5 metres less  specified as the height of the moon will match the expected answer.
It looks like either the given input data, or the expected results for moon are not in sync.
Can you please check, and advise ?
Browser Information

Browser Name, Version: Chrome, latest
Operating System: Windows 10
Mobile, Desktop, or Tablet: Desktop

Your Code
function orbitalPeriod(arr) {
var GM =<PHONE_NUMBER>;
var earthRadius = 6367.4447;
arr = arr.map(function(val){
var alt = val.avgAlt;
delete val.avgAlt;
var orb = Math.round( 2 * 3.1416 * Math.sqrt (Math.pow( (earthRadius + alt ), 3)/GM));
// As per wikipedia, the formula is ORB = 2PISQRT(R^3/GM);
val.orbitalPeriod = orb;
return val;
});
return arr;
}
//orbitalPeriod([{name : "sputnik", avgAlt : 35873.5553}]);
orbitalPeriod([{name: "iss", avgAlt: 413.6}, {name: "hubble", avgAlt: 556.7}, {name: "moon", avgAlt: 378632.553}]);
Screenshot

@srini5 This is caused by your approximation of pi. Instead, used Math.PI that is provided as part of the Javascript math functions. In the future, consider asking for help in the HelpJavascript chat room by clicking the help button on the challenge. Happy coding!

Thanks @dhcodes.
As directed, will ask for help in the future. Sorry for raising this directly here, this time.
Thank you for helping.


update READ  Me to add my name and profile

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

Thanks.


Gradle 2.13, javadoc + sources jars in maven builds

I can open another pull request without the gradle 2.13 update if you'd like, but the build times have improved with the newer gradle versions

Did gradlew and gradlew.bat get modified because of the Gradle update?

All of those files were updated after running the wrapper gradle task. The newer gradle versions have been providing some nice speed boosts so it'd be great to keep the library on the latest version if possible

Okay, thanks!


Potential dangling-pointer bug in function GetPyArrayDescrForTensor by holding a reference in a list after all its references released (a static analyzer report)

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
TensorFlow installed from (source or binary): source
TensorFlow version (commit): faad219
Python version: 3.8.5

Static analysis results, no POC.
This static analysis report has been manually reviewed to verify its validity.
Describe the current behavior
The path provided by the static analyzer is as follows.

A new reference is returned from PyTuple_New and pointed to by field.
https://github.com/tensorflow/tensorflow/blob/faad219fc46032a0ae9576ccc3076612cc1f5f72/tensorflow/python/lib/core/ndarray_tensor.cc#L341

A reference is stolen by function PyList_SetItem.
https://github.com/tensorflow/tensorflow/blob/faad219fc46032a0ae9576ccc3076612cc1f5f72/tensorflow/python/lib/core/ndarray_tensor.cc#L350

Refcnt decrement in macro Py_CLEAR will make the reference held in the list a dangling pointer.
https://github.com/tensorflow/tensorflow/blob/faad219fc46032a0ae9576ccc3076612cc1f5f72/tensorflow/python/lib/core/ndarray_tensor.cc#L352

Contributing

Do you want to contribute a PR? (yes/no): no
Briefly describe your candidate solution(if contributing):

A potential correct fix can be removing the following line.
https://github.com/tensorflow/tensorflow/blob/faad219fc46032a0ae9576ccc3076612cc1f5f72/tensorflow/python/lib/core/ndarray_tensor.cc#L352

Thanks for the report!
This looks legit to my eyes. I'm filing a fix removing that extra Py_Clear call.
As a note, the errorring code branch is invokes when calling .numpy() on a DT_RESOURCE tensor. This is likely rare.
For my education, what tool did you use to perform this static analysis?

@Snape3058 Could you please respond to the comment above ?Thanks!

@Snape3058,
Sorry for the late response. This issue was fixed now.
Please refer to the updated code here.
Please feel free to move this issue to closed status. Thank you.

LGTM
BTW, could you please attach the commit or PR fixing the problem below as a shortcut?
Thanks a lot.


Cannot disable the plugin

Hi,
The plugin works well, but on some environments we don't have redis enabled and we cannot disabled it without uninstalling it.
The plugin always fallback to its default configuration (<IP_ADDRESS>:6379) and ignore debug and debugIORedis parameters, it will spam the logs with:
[2022-10-19 16:05:10.110] http: GET index.html (4 ms) 200
[ioredis] Unhandled error event: Error: connect ECONNREFUSED <IP_ADDRESS>:6379
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
    at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)
[ioredis] Unhandled error event: Error: connect ECONNREFUSED <IP_ADDRESS>:6379
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
    at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)
[ioredis] Unhandled error event: Error: connect ECONNREFUSED <IP_ADDRESS>:6379
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
    at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)
[...]

Could you please make it so that when no (or specific values like -1) are filled in config the plugin is just disabled (like other strapi plugins which don't load when no config is provided).
Thanks !

+1

Thanks for this, I'll add an enable key here but can you confirm that setting strapi-plugin-redis: { enabled: false } doesn't disable it? If not then I can make sure I check it forcefully (this key is typically read by Strapi itself to know if it needs to load the plugin)

Thanks for your quick answer !
I tried with this in my plugin.js file but I still have the same errors:
module.exports = function ({ env }) {
  const config = {
    "strapi-plugins-redis": {
      enabled: false,
    },
    redis: {
      enabeld: false,
    },
[...]

My bad, I did a typo in the conf file (you can see it in my previous message).
With redis: { enabled: false } the plugin is indeed disabled in the standard way.


Investigate adding adapters for newline JSON stored in packed binary formats

[ ] ProtoBuf
[ ] Thrift
[ ] Message Pack
[ ] Avro

Not needed.


Avoiding the use of any type within library

Is there a particular reason that the library uses any, rather then being more explicit with the types?
When using common linting rules, such as @typescript-eslint/no-unsafe-call, when trying to call .stop() on a Service, linting will fail. Could the Service.stop definition be changed to void | undefined instead?
https://typescript-eslint.io/rules/no-unsafe-call/
Happy to provide a PR if a maintainer agrees.

@davidwinter Initially for speed during the original conversion but yes, agree this should be amended.
I'll have a look during the current review.
Thanks

Made improvements in PR #44


panic: runtime error: index out of range [1] with length 0

Steps to reproduce:
I create a Docker container running beta.2. I do a setup using the CLI interface influx. I save the container with the initialized DB to a new image. When I run the new image influxdb fails to query some data just writen to the DB. The query result in a server panic, see log below. To reproduce save the files creating to docker image and execute build. When build has created new image with the setup influxdb, start the image using
docker-compose -f obbaa-influxdb.yml up -d
Store some data to the created bucket pm-collection and try to query them. You should see the runtime error.
Expected behavior:
No server crash. Store and query data should work.
Actual behavior:
When starting my applications unit test, a few points are written to the db without an error, but when query the data back, the influxd has a runtime error index out of range. Sometimes it is also not possible to delete my bucket. Retrying the bucket delete ends the influxd process.
Environment info:
Dockerfile:
###########################################################################
# Copyright 2020 Broadband Forum
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
###########################################################################
FROM ubuntu:16.04
# Setup proxy if container is run on behind proxy host
ARG http_proxy
ARG https_proxy
ARG INFLUX_USER
ARG INFLUX_PW
ARG INFLUX_ORG
ARG INFLUX_BUCKET
ENV INFLUXDB_VERSION 2.0.0-beta.2
ENV DEBIAN_FRONTEND noninteractive
ENV TERM vt100
RUN set +ex &&
apt-get update &&
apt-get install -y apt-utils ca-certificates tzdata net-tools iproute2 wget &&
apt-get clean autoclean &&
apt-get autoremove --yes &&
rm -rf /var/lib/{apt.dpkg.cache.log} &&
wget --no-verbose --quiet https://dl.influxdata.com/influxdb/releases/influxdb_${INFLUXDB_VERSION}linux_amd64.tar.gz &&
mkdir -p /usr/src &&
tar -C /usr/src -xzf influxdb${INFLUXDB_VERSION}linux_amd64.tar.gz &&
rm influxdb${INFLUXDB_VERSION}_linux_amd64.tar.gz &&
mkdir /etc/influxdb &&
chmod +x /usr/src/influxdb*/influx* &&
cp -p /usr/src/influxdb*/influx* /usr/bin/ &&
cp -p /usr/src/influxdb*/README.md /etc/influxdb/ &&
cp -p /usr/src/influxdb*/LICENSE /etc/influxdb/ &&
mkdir /etc/influxdb/example &&
rm -rf /usr/src /root/.gnupg
EXPOSE 9999 22
RUN mkdir -p /var/opt/influxdb
COPY init-influxdb.sh /etc/influxdb/init-influxdb.sh
RUN chmod 755 /etc/influxdb/init-influxdb.sh
COPY entrypoint.sh /entrypoint.sh
RUN chmod 755 /entrypoint.sh
#COPY example/storeQuery.sh /etc/influxdb/example
#RUN chmod 755 /etc/influxdb/example/storeQuery.sh
#COPY example/rmRecords.sh /etc/influxdb/example
#RUN chmod 755 /etc/influxdb/example/rmRecords.sh
ENTRYPOINT ["/entrypoint.sh"]
CMD ["influxd"]
entrypoint.sh
#!/bin/bash
set -e
clean_up()
{
if [ "${pid}" != "" ]; then
kill ${pid}
exit 1
fi
}
if [ ! -f ${INFLUX_ROOT}/influxd.bolt -o ! -d ${INFLUX_ROOT}/engine ]; then
pid=
trap clean_up SIGHUP SIGINT SIGQUIT SIGTERM

echo "Starting influxd"
if [ ! -x /usr/bin/influxd ]; then
    echo "/usr/bin/influxd not found or not executable"
    exit 1
fi

/usr/bin/influxd run $@ >/var/log/influxdb.log 2>&1 &
pid=$!
if [ $? -ne 0 ]; then
    echo "Can't start influxd"
    exit 1
fi
sleep 1

echo "Setup influxdb"
/etc/influxdb/init-influxdb.sh
if [ $? -ne 0 ]; then
    echo "influxdb initialization failed"
    es=1
else
    echo "influxdb initialized"
    es=0
fi

echo "Stopping influxdb"
kill ${pid}
kes=$?
wait
if [ ${es} -eq 0 ]; then
    if [ ${kes} -ne 0 ]; then
        echo "Can't stop influxd"
        exit 1
    fi
else
    if [ ${kes} -ne 0 ]; then
        echo "Can't stop influxd"
    fi
    exit 1
fi
trap - SIGHUP SIGINT SIGQUIT SIGTERM
exit 0

fi
if [ "${1:0:1}" = '-' ]; then
set -- influxd "$@"
fi
exec "$@" >>/var/log/influxdb.log 2>&1
init-influxdb.sh
#!/bin/bash
# set -x
INFLUX_PATH=/usr/bin
INFLUX_USER=${INFLUX_USER:=influxdb}
INFLUX_PW=${INFLUX_PW:=influxdb}
INFLUX_ORG=${INFLUX_ORG:=broadband_forum}
INFLUX_BUCKET=${INFLUX_BUCKET:=pm-collection}
INFLUX_RETENTION=${INFLUX_RETENTION:=720}
INFLUX_PORT=${INFLUX_PORT:=9999}
timeout=10
while [ ${timeout} -gt 0 ]; do
netstat -ant | grep ${INFLUX_PORT}
if [ $? -eq 0 ]; then
break
fi
sleep 1
timeout=$((timeout - 1))
done
if [ ${timeout} -eq 0 ]; then
echo "influxd not online"
exit 1
fi
${INFLUX_PATH}/influx setup -f -o ${INFLUX_ORG} -b ${INFLUX_BUCKET} -u ${INFLUX_USER} -p ${INFLUX_PW} -r ${INFLUX_RETENTION}
if [ $? -ne 0 ]; then
echo "failed to setup influxdb"
exit 1
fi
exit 0
obbaa-influxdb-setup.yml
###########################################################################
# Copyright 2020 Broadband Forum
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
###########################################################################
version: "3.5"
services:
influxdb:
image: broadbandforum/influxdb:2.0.0-beta.2-0
container_name: obbaa-influxdb
command: --bolt-path /var/opt/influxdb/influxd.bolt --engine-path /var/opt/influxdb/engine --reporting-disabled
restart: on-failure
ports:
- "9999:9999"
environment:
- DEBUG=true
- INFLUX_USER=influxdb
- INFLUX_PW=influxdb
- INFLUX_ORG=broadband_forum
- INFLUX_BUCKET=pm-collection
- INFLUX_RETENTION=720
- INFLUX_PORT=9999
- INFLUX_ROOT=/var/opt/influxdb
obbaa-influxdb.yml
###########################################################################
# Copyright 2020 Broadband Forum
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
###########################################################################
version: "3.5"
services:
influxdb:
image: broadbandforum/influxdb:2.0.0-beta.2-2
container_name: obbaa-influxdb
command: --bolt-path /var/opt/influxdb/influxd.bolt --engine-path /var/opt/influxdb/engine --reporting-disabled
restart: on-failure
ports:
- "<IP_ADDRESS>:9999:9999"
environment:
- DEBUG=true
- INFLUX_USER=influxdb
- INFLUX_PW=influxdb
- INFLUX_ORG=broadband_forum
- INFLUX_BUCKET=pm-collection
- INFLUX_RETENTION=720
- INFLUX_PORT=9999
- INFLUX_ROOT=/var/opt/influxdb
build
#!/bin/bash
repository="broadbandforum/influxdb"
version="2.0.0-beta.2"
buildRelease="0"
release="2"
testDB="false"
check()
{
docker image ls -a | grep "influxdb.${version}-${release}" >/dev/null
if [ $? -eq 0 ]; then
echo "Image influxdb:${version}-${release} already exists."
exit 1
fi
docker image ls -a | grep "influxdb.${version}-${buildRelease}" >/dev/null
if [ $? -eq 0 ]; then
echo "Image influxdb:${version}-${buildRelease} already exists."
exit 1
fi
if [ -d /baa/stores/influxdb/engine -o -f /baa/stores/influxdb/influxd.bolt ]; then
echo "Database files exists in /baa/stores/influxdb"
exit 1
fi
}
arg=""
if [ "${https_proxy}" != "" ]; then
arg="--build-arg https_proxy=${https_proxy}"
fi
if [ "${http_proxy}" != "" ]; then
if [ "${arg}" = "" ]; then
arg="--build-arg http_proxy=${http_proxy}"
else
arg="${arg} --build-arg http_proxy=${http_proxy}"
fi
fi
check
docker image build ${arg} -t ${repository}:${version}-${buildRelease} .
if [ $? -ne 0 ]; then
echo "Failed to build image."
exit 1
fi
docker-compose -f obbaa-influxdb-setup.yml up -d
if [ $? -ne 0 ]; then
echo "Failed to execute docker-compose."
exit 1
fi
cid=docker container ls --filter=ancestor=${repository}:${version}-${buildRelease} --format "{{.ID}}"
while true; do
status=docker ps -a --filter=ancestor=${repository}:${version}-${buildRelease} --filter=status=exited --format "{{.Status}}"
if [[ "${status}" =~ "Exited" ]]; then
echo "db setup done."
break
fi
echo "Waiting for db setup ready"
sleep 1
done
docker commit ${cid} ${repository}:${version}-${release}
if [ $? -ne 0 ]; then
echo "Failed to commit docker image."
exit 1
fi
echo "start new image using >>docker-compose -f obbaa-influxdb.yml up -d<<"
exit 0
Config:
See obbaa-influxdb.yml
Logs:
root@d826dbbbbd92:/var/log# cat influxdb.log
ts=2020-02-05T15:08:09.063441Z lvl=info msg="Welcome to InfluxDB" log_id=0KmU9Ful000 version=2.0.0-beta.2 commit=455d40e0c build_date=2020-02-05T15:08:09Z
ts=2020-02-05T15:08:09.064688Z lvl=info msg="Resources opened" log_id=0KmU9Ful000 service=bolt path=/var/opt/influxdb/influxd.bolt
ts=2020-02-05T15:08:09.066739Z lvl=info msg="Opening Series File (start)" log_id=0KmU9Ful000 service=storage-engine service=series-file op_name=series_file_open path=/var/opt/influxdb/engine/_series op_event=start
ts=2020-02-05T15:08:09.071183Z lvl=info msg="Opening Series File (end)" log_id=0KmU9Ful000 service=storage-engine service=series-file op_name=series_file_open path=/var/opt/influxdb/engine/_series op_event=end op_elapsed=4.446ms
ts=2020-02-05T15:08:09.072465Z lvl=info msg="Index opened" log_id=0KmU9Ful000 service=storage-engine index=tsi partitions=8
ts=2020-02-05T15:08:09.073001Z lvl=info msg="Reloaded WAL" log_id=0KmU9Ful000 service=storage-engine path=/var/opt/influxdb/engine/wal duration=0.052ms
ts=2020-02-05T15:08:09.073019Z lvl=info msg=Starting log_id=0KmU9Ful000 service=storage-engine component=retention_enforcer check_interval=1h
ts=2020-02-05T15:08:09.073238Z lvl=info msg="Starting query controller" log_id=0KmU9Ful000 service=storage-reads concurrency_quota=10 initial_memory_bytes_quota_per_query=9223372036854775807 memory_bytes_quota_per_query=9223372036854775807 max_memory_bytes=0 queue_size=10
ts=2020-02-05T15:08:09.362445Z lvl=info msg=Listening log_id=0KmU9Ful000 transport=http addr=:9999 port=9999
ts=2020-02-05T15:08:09.646256Z lvl=info msg=Stopping log_id=0KmU9Ful000 service=scraper
ts=2020-02-05T15:08:09.646358Z lvl=info msg=Stopping log_id=0KmU9Ful000 service=task
ts=2020-02-05T15:08:09.646416Z lvl=info msg=Stopping log_id=0KmU9Ful000
ts=2020-02-05T15:08:09.646513Z lvl=info msg=Stopping log_id=0KmU9Ful000 service=nats
ts=2020-02-05T15:08:09.647139Z lvl=info msg=Stopping log_id=0KmU9Ful000 service=bolt
ts=2020-02-05T15:08:09.647208Z lvl=info msg=Stopping log_id=0KmU9Ful000 service=query
ts=2020-02-05T15:08:09.647222Z lvl=info msg=Stopping log_id=0KmU9Ful000 service=storage-engine
ts=2020-02-05T15:08:09.647245Z lvl=info msg=Stopping log_id=0KmU9Ful000 service=storage-engine component=retention_enforcer check_interval=1h
ts=2020-02-05T15:11:00.315960Z lvl=info msg="Welcome to InfluxDB" log_id=0KmUJhrl000 version=2.0.0-beta.2 commit=455d40e0c build_date=2020-02-05T15:11:00Z
ts=2020-02-05T15:11:00.317406Z lvl=info msg="Resources opened" log_id=0KmUJhrl000 service=bolt path=/var/opt/influxdb/influxd.bolt
ts=2020-02-05T15:11:00.319335Z lvl=info msg="Opening Series File (start)" log_id=0KmUJhrl000 service=storage-engine service=series-file op_name=series_file_open path=/var/opt/influxdb/engine/_series op_event=start
ts=2020-02-05T15:11:00.359210Z lvl=info msg="Opening Series File (end)" log_id=0KmUJhrl000 service=storage-engine service=series-file op_name=series_file_open path=/var/opt/influxdb/engine/_series op_event=end op_elapsed=39.877ms
ts=2020-02-05T15:11:00.363052Z lvl=info msg="Index opened" log_id=0KmUJhrl000 service=storage-engine index=tsi partitions=8
ts=2020-02-05T15:11:00.364098Z lvl=info msg="Reloaded WAL" log_id=0KmUJhrl000 service=storage-engine path=/var/opt/influxdb/engine/wal duration=0.100ms
ts=2020-02-05T15:11:00.364141Z lvl=info msg=Starting log_id=0KmUJhrl000 service=storage-engine component=retention_enforcer check_interval=1h
ts=2020-02-05T15:11:00.364647Z lvl=info msg="Starting query controller" log_id=0KmUJhrl000 service=storage-reads concurrency_quota=10 initial_memory_bytes_quota_per_query=9223372036854775807 memory_bytes_quota_per_query=9223372036854775807 max_memory_bytes=0 queue_size=10
ts=2020-02-05T15:11:00.654371Z lvl=info msg=Listening log_id=0KmUJhrl000 transport=http addr=:9999 port=9999
ts=2020-02-05T15:11:26.258485Z lvl=info msg=Unauthorized log_id=0KmUJhrl000 error="session not found"
ts=2020-02-05T15:12:02.149086Z lvl=info msg="Execute source panic" log_id=0KmUJhrl000 service=storage-reads error="panic: runtime error: index out of range [1] with length 0" stacktrace="goroutine 1016 [running]:\nruntime/debug.Stack(0xc0008f7da0, 0x2bddd00, 0x1cfef46)\n\t/usr/local/go/src/runtime/debug/stack.go:24 +0x9d\ngithub.com/influxdata/flux/execute.(*executionState).do.func1.1(0xc000b97980)\n\t/go/pkg/mod/github.com/influxdata/flux@v0.59.5/execute/executor.go:270 +0x192\npanic(0x1bad820, 0xc000a620e0)\n\t/usr/local/go/src/runtime/panic.go:679 +0x1b2\nencoding/binary.bigEndian.Uint16(...)\n\t/usr/local/go/src/encoding/binary/binary.go:100\ngithub.com/influxdata/influxdb/tsdb.ReadSeriesKeyMeasurement(...)\n\t/go/src/github.com/influxdata/influxdb/tsdb/series_file.go:447\ngithub.com/influxdata/influxdb/tsdb.parseSeriesKey(0x7f102756400e, 0x1, 0x3ffff2, 0x0, 0x0, 0x0, 0x40ca58, 0x90, 0x98, 0xc0008cadc0, ...)\n\t/go/src/github.com/influxdata/influxdb/tsdb/series_file.go:484 +0x534\ngithub.com/influxdata/influxdb/tsdb.ParseSeriesKeyInto(...)\n\t/go/src/github.com/influxdata/influxdb/tsdb/series_file.go:475\ngithub.com/influxdata/influxdb/storage.(*seriesCursor).Next(0xc0008cadc0, 0xc00083fd40, 0x8, 0xc00091f880)\n\t/go/src/github.com/influxdata/influxdb/storage/series_cursor.go:105 +0x8e\ngithub.com/influxdata/influxdb/storage/readservice.(*indexSeriesCursor).Next(0xc00036f520, 0xc00083fc80)\n\t/go/src/github.com/influxdata/influxdb/storage/readservice/cursor.go:112 +0x55\ngithub.com/influxdata/influxdb/storage/reads.(*resultSet).Next(0xc00036f5f0, 0x2c4ac48)\n\t/go/src/github.com/influxdata/influxdb/storage/reads/resultset.go:50 +0x41\ngithub.com/influxdata/influxdb/storage/reads.(*filterIterator).handleRead(0xc000edfea0, 0xc0001199e0, 0x2c361c0, 0xc00036f5f0, 0x0, 0x0)\n\t/go/src/github.com/influxdata/influxdb/storage/reads/reader.go:165 +0xea\ngithub.com/influxdata/influxdb/storage/reads.(*filterIterator).Do(0xc000edfea0, 0xc0001199e0, 0xc00095d901, 0xc000edfea0)\n\t/go/src/github.com/influxdata/influxdb/storage/reads/reader.go:143 +0x148\ngithub.com/influxdata/influxdb/query/stdlib/influxdata/influxdb.(*Source).processTables(0xc000fbe370, 0x2c21200, 0xc00083f6b0, 0x2c00e80, 0xc000edfea0, 0x15f08a4a8ba6de50, 0x15f08a4a8ba6de50, 0xc000b37560)\n\t/go/src/github.com/influxdata/influxdb/query/stdlib/influxdata/influxdb/source.go:74 +0x94\ngithub.com/influxdata/influxdb/query/stdlib/influxdata/influxdb.(*readFilterSource).run(0xc000fbe370, 0x2c21200, 0xc00083f6b0, 0x1f8f89db27cf00a6, 0x1cea0bd)\n\t/go/src/github.com/influxdata/influxdb/query/stdlib/influxdata/influxdb/source.go:151 +0x138\ngithub.com/influxdata/influxdb/query/stdlib/influxdata/influxdb.(*Source).Run(0xc000fbe370, 0x2c21200, 0xc00083f6b0)\n\t/go/src/github.com/influxdata/influxdb/query/stdlib/influxdata/influxdb/source.go:54 +0x2fc\ngithub.com/influxdata/flux/execute.(*executionState).do.func1(0xc00095d990, 0xc000b97980, 0x2c21200, 0xc00083f6b0, 0x2c00cc0, 0xc000fbe370)\n\t/go/pkg/mod/github.com/influxdata/flux@v0.59.5/execute/executor.go:275 +0xd7\ncreated by github.com/influxdata/flux/execute.(*executionState).do\n\t/go/pkg/mod/github.com/influxdata/flux@v0.59.5/execute/executor.go:250 +0xf8\n"
ts=2020-02-05T15:22:02.364419Z lvl=info msg="Cache snapshot (start)" log_id=0KmUJhrl000 service=storage-engine engine=tsm1 op_name=tsm1_cache_snapshot op_event=start
ts=2020-02-05T15:22:02.367937Z lvl=info msg="Snapshot for path written" log_id=0KmUJhrl000 service=storage-engine engine=tsm1 op_name=tsm1_cache_snapshot path=/var/opt/influxdb/engine/data duration=3.554ms
ts=2020-02-05T15:22:02.367974Z lvl=info msg="Cache snapshot (end)" log_id=0KmUJhrl000 service=storage-engine engine=tsm1 op_name=tsm1_cache_snapshot op_event=end op_elapsed=3.588ms

@peter-reinig thanks for opening this issue. Looks like it might be erroring on the Flux query based on the panic. Could you post the Flux query you were running when the panic occurred? I've assigned someone from the Flux team to take a look.

Here my query request:
#!/bin/bash
INFLUX_BIN=/usr/bin
INFLUX_ORG="broadband_forum"
INFLUX_BUCKET="pm-collection"
stopTime=date +%s
startTime=expr ${stopTime} - 10
${INFLUX_BIN}/influx write -o ${INFLUX_ORG} -b ${INFLUX_BUCKET} -p s 'measurement,hostName=dpu0,templateId=267 if:inerrors=7i,if:outerrors=564i '${startTime}
${INFLUX_BIN}/influx query -o ${INFLUX_ORG} 'from(bucket: "'${INFLUX_BUCKET}'") |> range(start: '${startTime}', stop: '${stopTime}') |> filter(fn: (r) => r._measurement == "measurement")|> filter(fn: (r) => r.hostName == "dpu0")'
In the mean time I was able to get around the problem by moving the db files (influxdb-bolt and engine/*) to an external docker volume. It looks like the db files created during setup are are different when creating them on an external volume compared to creating them in the docker file system and then do a docker commit to save the changes to a new docker image. May be the sparse files created do not work well in the dockers UFS file system?

It’s not working when the DB in inside the container. I use a filesystem outside the container to store the data.
Peter
Von: spigelli<EMAIL_ADDRESS>Gesendet: Mittwoch, 10. Juni 2020 23:53
An: influxdata/influxdb<EMAIL_ADDRESS>Cc: Reinig, Peter<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [influxdata/influxdb] panic: runtime error: index out of range [1] with length 0 (#16734)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
@peter-reinighttps://github.com/peter-reinig Ever find a workaround for this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/influxdata/influxdb/issues/16734#issuecomment-642287180, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOMG3JSWIKCSPHGQYPNAUE3RV76ELANCNFSM4KQOHQCA.

DZS KEYMILE - Shaping the Internet Connection Experience of the Future
KEYMILE GmbH
i. A. Peter Reinig
Head of R&D Network Management Solutions
Wohlenbergstr. 3
30179 Hannover
Germany
E-Mail<EMAIL_ADDRESS>Phone: +49 511 6747 697
https://www.keymile.com
Geschäftsführer: Kai Uebach - Rechtsform der Gesellschaft: GmbH, Sitz: Hannover - HRB: 208 693, Amtsgericht Hannover - USt-Id. Nr.: DE301700778 - WEEE-Reg.-Nr.: DE59336750 Details zur Verarbeitung Ihrer Daten finden Sie in unseren Hinweisen zum Datenschutz: https://www.keymile.com/web/keymile/datenschutzhinweise-nach-dsgvo-art.-13
Managing Director: Kai Uebach - Legal structure: GmbH, Registered office: Hanover - HRB 208 693, Local court: Hanover - VAT ID No.: DE301700778 - WEEE-Reg.-No.: DE59336750 Details on the processing of your data can be found in our privacy policy: https://www.keymile.com/web/keymile/data_protection_notice_pursuant_gdpr_article_13

Hi @peter-reinig just wondering about your use case ... is the idea to prepare a container that is initialized with data and use it in an ephermeral way?

Hi Adrian,
the use case is to provide an initialized container for regression testing using Bamboo (Continuous Integration and Buid Server).
Regards,
Peter
Von: Adrian Thurston<EMAIL_ADDRESS>Gesendet: Dienstag, 7. Juli 2020 19:10
An: influxdata/influxdb<EMAIL_ADDRESS>Cc: Reinig, Peter<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [influxdata/influxdb] panic: runtime error: index out of range [1] with length 0 (#16734)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi @peter-reinighttps://github.com/peter-reinig just wondering about your use case ... is the idea to prepare a container that is initialized with data and use it in an ephermeral way?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/influxdata/influxdb/issues/16734#issuecomment-655002414, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOMG3JTBI7K4VFDNUQBZA3DR2NJIDANCNFSM4KQOHQCA.

DZS KEYMILE - Shaping the Internet Connection Experience of the Future
KEYMILE GmbH
i. A. Peter Reinig
Head of R&D Network Management Solutions
Wohlenbergstr. 3
30179 Hannover
Germany
E-Mail<EMAIL_ADDRESS>Phone: +49 511 6747 697
https://www.keymile.com
Geschäftsführer: Kai Uebach - Rechtsform der Gesellschaft: GmbH, Sitz: Hannover - HRB: 208 693, Amtsgericht Hannover - USt-Id. Nr.: DE301700778 - WEEE-Reg.-Nr.: DE59336750 Details zur Verarbeitung Ihrer Daten finden Sie in unseren Hinweisen zum Datenschutz: https://www.keymile.com/web/keymile/datenschutzhinweise-nach-dsgvo-art.-13
Managing Director: Kai Uebach - Legal structure: GmbH, Registered office: Hanover - HRB 208 693, Local court: Hanover - VAT ID No.: DE301700778 - WEEE-Reg.-No.: DE59336750 Details on the processing of your data can be found in our privacy policy: https://www.keymile.com/web/keymile/data_protection_notice_pursuant_gdpr_article_13

Thanks @peter-reinig !
I'm not able to reproduce this with my own docker script that does the same kind of thing.
I noticed that you don't have any delay between the influx setup command and the kill of the server executing the setup. In one out of four tries this caused problems for me.
What happens if you add a between those two steps?

Hi Adrian,
I also played with delays between setting up and stopping the sever. Sometimes I had the impression that adding delays solve the problem, but ultimately I was not working reliable.
Regards,
Peter
Von: Adrian Thurston<EMAIL_ADDRESS>Gesendet: Mittwoch, 8. Juli 2020 15:38
An: influxdata/influxdb<EMAIL_ADDRESS>Cc: Reinig, Peter<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [influxdata/influxdb] panic: runtime error: index out of range [1] with length 0 (#16734)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Thanks @peter-reinighttps://github.com/peter-reinig !
I'm not able to reproduce this with my own docker script that does the same kind of thing.
I noticed that you don't have any delay between the influx setup command and the kill of the server executing the setup. In one out of four tries this caused problems for me.
What happens if you add a between those two steps?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/influxdata/influxdb/issues/16734#issuecomment-655525537, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOMG3JS4ZP43TOFXAS3EO5DR2RZERANCNFSM4KQOHQCA.

DZS KEYMILE - Shaping the Internet Connection Experience of the Future
KEYMILE GmbH
i. A. Peter Reinig
Head of R&D Network Management Solutions
Wohlenbergstr. 3
30179 Hannover
Germany
E-Mail<EMAIL_ADDRESS>Phone: +49 511 6747 697
https://www.keymile.com
Geschäftsführer: Kai Uebach - Rechtsform der Gesellschaft: GmbH, Sitz: Hannover - HRB: 208 693, Amtsgericht Hannover - USt-Id. Nr.: DE301700778 - WEEE-Reg.-Nr.: DE59336750 Details zur Verarbeitung Ihrer Daten finden Sie in unseren Hinweisen zum Datenschutz: https://www.keymile.com/web/keymile/datenschutzhinweise-nach-dsgvo-art.-13
Managing Director: Kai Uebach - Legal structure: GmbH, Registered office: Hanover - HRB 208 693, Local court: Hanover - VAT ID No.: DE301700778 - WEEE-Reg.-No.: DE59336750 Details on the processing of your data can be found in our privacy policy: https://www.keymile.com/web/keymile/data_protection_notice_pursuant_gdpr_article_13

Here is more information about running influxdb inside a docker container: https://www.influxdata.com/blog/running-influxdb-2-0-and-telegraf-using-docker/
i'm going to close this for now since it was opened against a pre-release version of influxdb. if you are still facing this problem, please open a new issue with the details.


Branding of OnlyOffice does not work in the current version.

Error description
Unfortunately, the branding of OnlyOffice does not work in the current version.
Steps for reproduction
The onlyoffice logo is in the upper left corner
Expected behavior
The customer Office logo appears on the top left
Additional context
The branding must also be available via WOPI, but currently it is not.

onlyoffice issue, closing here.


All in one Docker image

Current install is complex, running two docker images, and use REST API to upload dashboards.
A simpler solution will be to have one Docker image with all 3:
Prometheus
Grafanam
Dashboards

@tzach can we close this?


404 error while calling /v1/metering/collected/usage using post method

I am calling /v1/metering/collected/usage as below:
Url: http://abacus-usage-collector.apps.mydomain.com/v1/metering/collected/usage
Method: Post
Content-Type: application/json
Body:
{
"start":<PHONE_NUMBER>000,
"end":<PHONE_NUMBER>000,
"organization_id": "us-south:54257f98-83f0-4eca-ae04-9ea35277a538",
"space_id": "d98b5916-3c77-44b9-ac12-04456df23eae",
"consumer_id": "app:d98b5916-3c77-44b9-ac12-045678edabae",
"resource_id": "object-storage",
"plan_id": "basic",
"resource_instance_id": "d98b5916-3c77-44b9-ac12-04d61c7a4eae",
"measured_usage": [
{
"measure": "storage",
"quantity": 10
},
{
"measure": "api_calls",
"quantity": 10
}
]
}
I am sending same json as given in readme file. I am getting following response.
{
"message": "no_db_file",
"error": "not_found",
"reason": "no_db_file",
"name": "not_found",
"status": 404,
"noretry": true,
"nobreaker": true
}
Why I am getting Not found error?

Usually the response above means that the Abacus apps do not know the DB URL
To configure DB you need to set environment variables DB and DBCLIENT as described here: https://github.com/cloudfoundry-incubator/cf-abacus/blob/master/doc/conf.md#database

Any progress?

@hsiliev It's worked. Thanks


smart crop

A couple general comments:
Let's not commit the .DS_Store files, since that's a local Mac thing; we should add this to the gitignore for our fork of this repo.
Would it be possible to move the new files under /examples/custom instead of "examples/desktop/autoflip"? That way it will be clear going forward which files were modified/added by us, as opposed to the ones that come from the mediapipe developers.


Typo in README

They should use IncrBy
Command      Go API                 Description
-------      ------                 -----------
DECRBY       DB.Str().Incr          Decrements a number from the integer value of a key.
INCRBY       DB.Str().Incr          Increments the integer value of a key by a number.

The documentation is correct, it's Incr.


Skeleton files should be included in all problems to make it easier

I'm on the Python section, and I've found that only a few challenges include a skeleton file. This is helpful, since you can then start coding without the delay of creating your own file. Example: the Bob challenge comes with bob.py:
#
# Skeleton file for the Python "Bob" exercise.
#

def hey(what):

    return

It'd be great if a skeleton file like this was included in all of the challenges, to make things just a little bit easier for everyone.

On further inspection, this is completely the wrong repo to add an issue to. Sorry about that - I've added this issue to the correct repository.

Thanks!


Text to Speak doesn't work

I begin by apologizing as I am new to this world. But when using the Text to speech service provided in the Lovelace card, Alexa responds that the service called is not the right one. When I manually use the one below it works.
service: media_player.play_media
target:
entity_id: media_player.porch_echo
data:
media_content_type: custom
media_content_id: 'play angelos radio on apple music'
I am not able to change this service in the media player but can someone knowledgable take a look and see it it can be done.
Thanks.

The UI provided by HA will never work with the component. This is documented in the wiki. https://github.com/custom-components/alexa_media_player/wiki#notification-service


error when importing cfenv

ERROR in ./~/cfenv/lib/cfenv.js
Module not found: Error: Can't resolve 'fs' in '/Users/ei5875/Downloads/pbm-machine-learning-portal/node_modules/cfenv/lib'
 @ ./~/cfenv/lib/cfenv.js 5:7-20
 @ ./src/components/home/HomePage.js
 @ ./src/routes.js
 @ ./src/components/Root.js
 @ ./src/index.js
 @ multi ./src/webpack-public-path react-hot-loader/patch webpack-hot-middleware/client?reload=true whatwg-fetch ./src/index.js

ERROR in ./~/ports/index.js
Module not found: Error: Can't resolve 'fs' in '/Users/ei5875/Downloads/pbm-machine-learning-portal/node_modules/ports'
 @ ./~/ports/index.js 10:9-22
 @ ./~/cfenv/lib/cfenv.js
 @ ./src/components/home/HomePage.js
 @ ./src/routes.js
 @ ./src/components/Root.js
 @ ./src/index.js
 @ multi ./src/webpack-public-path react-hot-loader/patch webpack-hot-middleware/client?reload=true whatwg-fetch ./src/index.js

Your primary problem is that you are attempting to use cfenv within an app meant to be run on a web browser, I guess, since you're using webpack.
cfenv is designed to be run on a server, it's not going to do anything interesting in a browser.
Closing, but feel free to open if I'm missing some other context.


Fixes a server crashing bug

Occurs currently when someone submits a file upload without a type selected.
Product approved this approach to just set a default on the radio buttons.

@bmadhusu Yeah, I debated whether or not to include it, and sort of reversed my stance on it for this particular repo only. Given that exceptions in the Node app seem to bubble all the way out to killing the docker container right now, and quay.io is of dubious stability, I think it's maybe safer to include the change to the fleet template. Previous to this bug I would have expected the node process to crash, but nodemon to restart it without it breaking out and crashing the docker container. But maybe that's just a dev setting?
Anyway, given that any server exception could take down the process, and any user trying it multiple times can bring down the dashboard, the tradeoff of having this in place for the node app is maybe worth it over the chance that quay.io could go down between us uploading an image and a server trying to download it and failing and silently running old code.

All of which is to say I'm not super thrilled to include it, but the very real possibility of a user crashing the entire dashboard again with a different unknown bug is probably higher.


Setting that allows default selection of .ipynb or .dib when creating new notebook

When creating a new notebook through the command palette, a user always has to select whether they want to use the .ipynb format or the .dib format.
Would be nice if there were a setting that allowed users to select a default file type such that they don't have to select every time they create a new notebook. For users who stick to one file type (my assumption is most do this), it would reduce the creation of notebooks by one click.
Currently:

With setting:

The same would be useful for the default language.


refactor

This PR uses native dataset instead of OAI's generator.

Both GPU memory and utilization go down, but speed actually goes up (the global step rise faster)


Use the open-balena-api endpoints for device type & version info

That's on top of https://github.com/balena-io/balena-sdk/pull/668, so the final PR will not require any changes in the tests.
Resolves: #664
Depends-on: balena-io/resin-api#1829
HQ: balena-io/balena#1744
Change-type: minor
Signed-off-by: Thodoris Greasidis<EMAIL_ADDRESS>
Contributor checklist

[x] Includes tests
[ ] Includes typings
[ ] Includes updated documentation
[ ] Includes updated build output

@balena-ci retest


Scrolling with mouse wheel does not work on frozen columns

If you scroll up/down with the mouse wheel while the cursor is over a frozen column, the grid will not scroll.
http://jsfiddle.net/9w6LLbup/
I'm pretty sure it did work in the past ...

so how its going? any update?


Improve JavaScript Guide Documentation

This pull request enhances the JavaScript guide documentation by:
Adding detailed descriptions for each topic to improve clarity and context. Incorporating hyperlinks to relevant resources (e.g., MDN, official documentation, tutorials) for better usability and learning opportunities. These updates aim to create a more informative and user-friendly documentation experience.

Dont add in Readme.md. See contributing.md for steps on how to make a contribution.


Added my data

Created the object with my data in it.

Congrats 🎉, your PR got merged. To be eligible for the swags from iNeuron X ClueLess. Follow this steps.

SignIn / SignUp in ClueLess Website.

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.
@thefool76

hey @Rajdip019 this is my profile url My Profile


Changes to cleanup-cache workflow

Tested this in https://github.com/frelon/cache-test/actions/runs/7209527181/job/19640659692 and seems to work when permissions are added for the whole workflow and not only jobs.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (29a6223) 73.60% compared to head (93aafb1) 73.60%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1887   +/-   ##
=======================================
  Coverage   73.60%   73.60%
=======================================
  Files          69       69
  Lines        7332     7332
=======================================
  Hits         5397     5397
  Misses       1544     1544
  Partials      391      391

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


Undefined variable: mInfo

After installing all modules or boxes Etc... ,  and click the Button: [install module (0)]
PHP Notice:  Undefined variable: mInfo in X:\catalog\admin\modules.php on line 366.

the best would be hide or disable the button functionality.

No the best would be to get update the code to the appropriate result without notice, no?

Something like (around line 365 case default : ) :
    if ($new_modules_counter == 0) {     $heading[] = array('text' => 'No modules to install');     $contents[] = array('text' => '
' . 'No modules to install');     } else { ....      }
is that acceptable?

or before rendering tempate top
if ($new_modules_counter == 0) {
then redirect with session saved message to previous page

Somtehing would be print that no modules found. Left column will not supported only in legacy mode.

https://github.com/Gergely/oscommerce2/commit/0289418c93cf200a867cfba92f4d9221677887bd

If all modules uninstalled than same error catched (legacy code)
[30-Jul-2017 08:16:58 Europe/Budapest] PHP Notice:  Undefined variable: mInfo in \catalog\admin\modules.php on line 366

[30-Jul-2017 08:16:58 Europe/Budapest] PHP Notice:  Trying to get property of non-object in \catalog\admin\modules.php on line 366

[30-Jul-2017 08:16:58 Europe/Budapest] PHP Notice:  Undefined variable: mInfo in \catalog\admin\modules.php on line 368

[30-Jul-2017 08:16:58 Europe/Budapest] PHP Notice:  Trying to get property of non-object in \catalog\admin\modules.php on line 368


remove feature "aarch64-qemu-stdout"

because the latest kernel doesn't support this feature

bors r+

bors r+


Change type of selectsRange back to a boolean

Is your feature request related to a problem? Please describe.
I have installed the update to v7.x.x, and I noticed the type for the option selectsRange changed from a boolean to "true"-only. This makes optional and dynamic prop-filling more inconvenient for consuming libraries.
Describe the solution you'd like
old:
{ selectsRange: never, ... } & { selectsRange: true, ... }
proposed:
{ selectsRange: boolean, ... }

I agree


Add Directory Download Functionality to OPFS Explorer

Description
First of all, thank you for creating OPFS Explorer; it's a fantastic tool. I've been developing a web application that utilizes the Origin Private File System (OPFS), and your tool has been incredibly helpful during this process.
I found that I needed the ability to download directories as a whole, so I have implemented this feature and would like to contribute it back to the project.
Changes Made

Added Directory Download Feature:

Implemented a new functionality to download directories recursively.
Modified contentscript.js to handle a new message 'downloadDirectory', which initiates the download of the specified directory.
Ensured that fileHandles and directoryHandles are populated before invoking downloadDirectoryEntriesRecursive, to maintain consistency with the existing code structure.

User Interface Enhancements:

Updated devtools.js to add a download button (💾) next to directories and files in the UI. Users can click this button to download the entire directory or file.
Chose the floppy disk emoji (💾) as the icon for the download button. If you prefer a different icon or have any suggestions, please let me know, and I can update it accordingly.

Feedback Request
I would appreciate it if you could review this addition and let me know your thoughts on the implementation.
Do you think this approach aligns well with the project's direction?
Also, regarding the icon choice for the download button, if you have a preferred icon or style guidelines, please let me know, and I'm happy to make adjustments.
Thank you for considering this pull request!

Submitted to the Chrome Web Store, where it should go live as version 1.7.0 soon. Thanks again!

Thank you for merging this, I really appreciate it!


[2.6] Can't manage helm apps

Rancher Server Setup

Rancher version: 2.6.0
Installation option (Docker install/Helm Chart): Helm

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1, v1.20.6

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: v1.20.6, v1.21.4
Cluster Type (Local/Downstream):  Local

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

Describe the bug
I can't install and update apps from the catalog after upgrade rancher from 2.5.8. All installed charts have been disconnected from the repositories.
I see all my catalogs (legacy->catalogs) and installed apps.
I can't install charts because I don't see any applications from catalogs in the "+Charts".
If I try to edit the installed applications, I only see a field with a chart selection.
To Reproduce
Result
Expected Result
Screenshots

Additional context

I had a similar issue. To resolve it, I needed to add the same Helm chart catalog entries from the legacy section in the new "Apps & Marketplace" -> "Repositories" section too. Then I was able to upgrade the already installed instances.


demonstrate cherry-picking

add a simple cherry-picking demo to avoiding-conflicts episode

Fixed in 305b65b0d25272b0f82f33a9f3ff6349921a18fc.


You don't have permission to edit anything at the admin page

After I installed the app, I lost my permission in viewing admin page. I am a superuser.
You don't have permission to edit anything.
Any idea on how to resolve it?

Hi @weasteam,
Did you run migrate?

@lefterisnik, Yes, I did.
When I removed the app, I got permission back.

@lefterisnik: just a heads up that I see the same effect. Neither running makemigrations nor migrate finds anything to migrate.

Hi guys,
Which Django version do you use, in order to reproduce it?

Hey,
thanks for looking into this. I am using Django 1.11 with Python 3.4.2.

For me, Django version 1.10.5, Python 3.5.2

I had the same issue.
You need to place the admin_view_permission before django.contrib.admin in settings.py

I think a little clarification in the README would be nice:

You need to place the admin_view_permission before django.contrib.admin in settings.py

Hi all,
I've just updated the README.rst file as you suggested. Thanks for you feedback.


Migrate timerender tests to use the mockdate module or similar

As discussed in https://github.com/zulip/zulip/pull/25108#discussion_r1169382222, we should look at whether using a module like
https://www.npmjs.com/package/mockdate to test code involving date/times in the web/tests node test codebase.
There's probably plenty of other places that could use it too, but for this issue let's start with using it in one place and see if we like the API.

@zulipbot  claim

@zulipbot claim


Apple Mach-O Linker Error Group

Apple Mach-O Linker Error Group

Incorrectly linked IOKit headers

#162 #64 not a yalu bug please close

@beanjo55 precisely!

double precisely!

@timonline can u help me plz

@AbouImran the information is already on this repo if would look first

@beanjo55 I search but I can not find

@AbouImran This place is only for actual issue with Yalu, not being unable to compile the code on your side.
If you do not know how or can't find the info in this repo, then try searching in /r/jailbreak, twitter, or google.

@AbouImran then this isnt for you or haven't search hard enough

ipohne simulator

grow a brain

its ok its good now

A human can forget, miss things.
This is why we ask for help

@AbouImran that's fine but this is not the place to provide support. Only ISSUES


Updates quadratics list to avoid zonal mean trigger for cubed-sphere …

…fields
Types of change(s)

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Trivial change (affects only documentation or cleanup)
[ ] Refactor (no functional changes, no api changes)

Checklist

[ ] Tested this change with a run of GEOSgcm
[ ] Ran the Unit Tests (make tests)

Description
Related Issue

Note for @bena-nasa and @sdrabenh in case. This time_ave.x does not have the fixes for:

#2232
#2675


Fix AMD pattern.

Untested but proposed fix to #3629 using the standard UMD pattern as generated by Rollup.

Codecov Report

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

@@            Coverage Diff             @@
##           master    #3630      +/-   ##
==========================================
+ Coverage   88.68%   90.71%   +2.03%
==========================================
  Files         627       71     -556
  Lines       79681     4935   -74746
  Branches     1069     1069
==========================================
- Hits        70664     4477   -66187
+ Misses       9011      452    -8559
  Partials        6        6

Impacted Files
Coverage Δ

js/src/schema.ts
84.61% <0%> (-1.93%)
:arrow_down:

js/src/visitor/indexof.ts
97.26% <0%> (-1.37%)
:arrow_down:

js/src/ipc/metadata/message.ts
90.12% <0%> (-1.28%)
:arrow_down:

python/pyarrow/ipc.pxi

cpp/src/arrow/csv/chunker-test.cc

cpp/src/parquet/column_page.h

cpp/src/parquet/bloom_filter-test.cc

cpp/src/arrow/array/builder_decimal.cc

cpp/src/plasma/client.cc

cpp/src/arrow/io/test-common.h

... and 549 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 af60c2e...0930385. Read the comment docs.

Could you open a issue on JIRA https://issues.apache.org/jira/browse/ARROW and prepend "ARROW-XXXX: [JS] " to title of this pull request?
See also: https://cwiki.apache.org/confluence/display/ARROW/Contributing+to+Apache+Arrow

I created https://issues.apache.org/jira/browse/ARROW-4550.
@mbostock can you rename the PR title to "ARROW-4550: [JS] Fix AMD pattern"?

Renamed as requested. Thanks for looking at this!

@trxcllnt can you take a look at this? you're much more familiar with the build system

This looks ok to me. IIRC I used one of the standard UMD templates, and possibly modified it to match Webpack's umdNamedDefine output. I haven't used AMD in quite a while, so :+1: from me if this fixes it for @mbostock

Ok I'll do a smoke test locally then merge. Thanks @mbostock!

@mbostock is there a way to test this change in Observable before we cut an actual release?

@TheNeuralBit Yes, if you have the generated file somewhere, you can require the URL. GitHub makes this a little tricky because they force the content-type to be text/plain, but you can workaround that like so:
require(await fetch("https://gist.githubusercontent.com/mbostock/f421358acd00c94badaceed4d4034d36/raw/51026b908d68b94e191e8b4f3d5f46c41a4e00ac/amd-test.js").then(response => response.blob()).then(blob => URL.createObjectURL(blob)))

https://beta.observablehq.com/d/9e7bac640df7d65a
https://gist.github.com/mbostock/f421358acd00c94badaceed4d4034d36

Any update on when this will be released? It’s been a bummer that Apache Arrow is broken out of the box (at least on Observable) for about thirty days despite a fix being merged.

We will integrate the JS releases in the mainline releases and hopefully release this next week as 0.13.0

BTW absolutely nothing has blocked making a JavaScript release sooner, but no one has initiated those conversations on the mailing list

(i.e. @mbostock you or anyone could have asked on<EMAIL_ADDRESS>about making a release as soon as this patch was merged)

I didn’t think it was necessary to request a release given that the maintainers were apparently aware of the library being broken by evidence of the fact that this PR was merged, but I will keep that in mind for the future.

Yes, in the future, when something like this comes up, I would recommend being a "squeaky wheel" until you get what you need. The community must be given the opportunity to inspect the software before publishing it to NPM (a good thing IMHO, in light of some of the problems the ecosystem has had) but the release process is not complicated

Sorry @mbostock you're right we should've been on top of this.
I'm in favor of cutting an 0.4.1 release ASAP, all the JIRAs tagged for that release are already closed and several of them are bugfixes for 0.4.0. We can integrate with the mainline releases after that.

The new package is up https://www.npmjs.com/package/apache-arrow/v/0.4.1. Please let us know if any issues

Thanks! 👍 I’ve sent a corresponding suggestion to the Introduction to Apache Arrow on Observable.

@mbostock Could you create a JIRA account and tell me your account? I want to set you to the assignee of https://issues.apache.org/jira/browse/ARROW-4550 . Then we can list your name in 0.13.0 release note.


Possible "Get Watched" sorting bug?

Hi. The docs state that for endpoint Sync -> Get Watched

Returns all movies or shows a user has watched sorted by most plays.

However I noticed that its not really true. Attaching postman example below.
Plays are 23, 50, 10 so rather random.
Regards.

I think I'm seeing something similar on my end.
History from the history endpoint is correct, but watched is missing about a week's worth of items.

I think I'm seeing something similar on my end.
History from the history endpoint is correct, but watched is missing about a week's worth of items.

Remember Watched will not list multiple plays as history does.