Travis: Ruby 2.4.0-preview2 supported, just

This PR elbows in support for 2.4.0-preview2 to be able to run the test suite.
It conditionally adds these gems to the Gemfile:

json 2.x
yayl-ruby at a very recent commit (no release of the gem as yet)

And it removes 2.4.0-preview2 from allowed failures.

Darn – too fiddly. But it's close for many of these gems.


Add "chance of X" to summaries?

It is often the case that there is a lot of precipitation predicted, but only with a small chance of occurring. (Such as "20% chance of snow (11-17 in.) overnight".) It would be excellent to support this case in the translations... but how do languages other than English handle such things? How generic should we make this?

Assuming the sentence is "[X]% chance of [condition] [when]", I suppose it can be translated in many languages.

Looong time since this was first brought up, but I think Romanian translations should be ok with this as well.


Add development documentation

Add a page on package development, which @jstac can use to fix he's PR #104 😆
https://267-241268229-gh.circle-artifacts.com/0/html/develop/contributing.html
Also @AakashGfude, perhaps you would like to add a page about writing/running tests, as you have a pretty good understanding of that now 😁

This LGTM - I think we should just give it a merge and @AakashGfude it would be awesome if made a follow-up PR with some testing instructions :-)

@choldgraf @chrisjsewell Gotcha. I will work on this tomorrow.


BUILD.bazel files cause package identification problems

Environment

OS Version: Ubuntu 20.04
Source or binary build? Source Edifice build with colcon

Description

Expected behavior: Build successfully completes
Actual behavior: Colcon package identification fails because it sees both cmake and bazel

Steps to reproduce

Install colcon as well as the colcon-bazel extension: https://github.com/colcon/colcon-bazel
Attempt to build the ignition edifice workspace with colcon

Output
An example of colcon list shows that ign-math and ign-utils are both ignored because they match against both CMake and Bazel.
$ colcon list
[0.368s] WARNING:colcon.colcon_core.package_identification:No valid Build content
[0.371s] WARNING:colcon.colcon_core.package_identification:_identify(src/ign-math) has multiple matches and therefore is being ignored: bazel, cmake
[0.435s] WARNING:colcon.colcon_core.package_identification:No valid Build content
[0.438s] WARNING:colcon.colcon_core.package_identification:_identify(src/ign-utils) has multiple matches and therefore is being ignored: bazel, cmake
ignition-cmake2	src/ign-cmake	(cmake)
ignition-common4	src/ign-common	(cmake)
ignition-fuel_tools6	src/ign-fuel-tools	(cmake)
ignition-gazebo5	src/ign-gazebo	(cmake)
ignition-gui5	src/ign-gui	(cmake)
ignition-launch4	src/ign-launch	(cmake)
ignition-msgs7	src/ign-msgs	(cmake)
ignition-physics4	src/ign-physics	(cmake)
ignition-plugin1	src/ign-plugin	(cmake)
ignition-rendering5	src/ign-rendering	(cmake)
ignition-sensors5	src/ign-sensors	(cmake)
ignition-tools	src/ign-tools	(cmake)
ignition-transport10	src/ign-transport	(cmake)
sdformat11	src/sdformat	(cmake)

As far as I can tell, there are a few ways to solve it.

If you aren't actively using bazel in colcon workspaces, remove the colcon-bazel extension
Alter the PRIORITY setting the colcon-bazel extension point to give CMake higher priority

Ref: https://github.com/colcon/colcon-core/blob/master/colcon_core/package_identification/init.py#L46
https://github.com/colcon/colcon-bazel/blob/master/colcon_bazel/package_identification/bazel.py#L26

Add a colcon.pkg to all ignition packages to make CMake explicit

Another alternative is to use a colcon.meta file in the root of your colcon workspace.
{
  "paths": {
    "src/ign-utils": {
      "type": "cmake"
    },
    "src/ign-math": {
      "type": "cmake"
    },
    "src/ign-common": {
      "type": "cmake"
    },
  }
}

I remember having this issue before:
https://github.com/ignitionrobotics/ign-plugin/pull/31#pullrequestreview-532959529

Option 1. sounds like a tough ask for all users and I'd like to avoid option 3 so we don't have one more file to maintain.
I didn't quite understand how a user can set the PRIORITY for option 2, is this something that can be set from ~/.colcon/defaults.yaml or something like that?
The colcon.meta option also sounds promising.

I didn't quite understand how a user can set the PRIORITY for option 2, is this something that can be set from ~/.colcon/defaults.yaml or something like that?
The colcon.meta option also sounds promising.
+1 to both options, I also wonder if a different default priority for Bazel should be pushed upstream? While I understand that it would be an arbitrary choice to say what's higher priority between CMake and Bazel, it sounds like anything better than the current behavior (skipping the package altogether) would be better?

I didn't quite understand how a user can set the PRIORITY for option 2, is this something that can be set from ~/.colcon/defaults.yaml or something like that?

Setting the priority wouldn't be a user choice.  The bazel extension itself would have to be modified upstream so that it had a higher/lower priority than CMake so that one will always "win".
From my observations, colcon is used more widely with cmake/ros projects, so it seems like that would be the sane default, and users could use one of the approaches above to "force" bazel.

I believe the colcon-bazel pull request will address this.  You can install that version via pip:
 pip3 install -e git://github.com/colcon/colcon-bazel@reduce_priority#egg=colcon-bazel --upgrade --user

For future visitors to this issue, I needed to tweak @mjcarroll 's command to this:
pip3 install git+https://github.com/colcon/colcon-bazel@master#egg=colcon-bazel --upgrade --user

in particular I needed to use git+https: instead of only git:, otherwise GitHub hung up on me. The other changes in my command are just to (1) not leave an editable version of the package hanging around, and (2) use the master branch of colcon-bazel since the relevant PR has been merged.


Jenkins running out of space issues

Over recent weeks Jenkins seems to be having space issues.
What can be done to resolve these, or alert that this is soon to happen so action can be taken?

duplicate


[VS Code] Joining collaboration session: Unable to connect to the host. Verify both you and the host are online.

Error:
Joining collaboration session: Unable to connect to the host. Verify both you and the host are online.
Steps to Reproduce:
1.
2.

Version Data

extensionName
VSLS

extensionVersion
1.0.766

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.37.1

platformName
Windows

platformVersion
10.0.15063

Hey @joanleonrs , is it possible this was a valid error message?

Closing due to inactivity. Please re-open if this you're still encountering the issue and can share more details. Thanks!


Migrate GCM to FCM

https://developers.google.com/cloud-messaging/android/android-migrate-fcm.
It is strongly recommended by Google to use FCM instead of GCM.
It should also improve the Android >=6 devices notifications management in doze mode.

the server has been updated


react-apollo has no exported member "MutationProps"

The one in the title is the error react gives me regarding the auto file generated by this tool.
My configuration file is this:
overwrite: true
schema:
  - "http://localhost:3000/graphql"
  - ./src/graphql/client-schema.graphql
documents: "src/graphql/**/*.ts"
generates:
  src/graphql/generated.tsx:
    config:
      noNamespaces: true
      contextType: ../graphql/context#MyContext
      withHooks: true
      withComponent: true

    plugins:
      - add: '/* eslint-disable */'
      - "typescript-common"
      - "typescript-client"
      - "typescript-react-apollo"
      - "typescript-server"
      - "typescript-resolvers"

Instead the installed packages are these:
    "graphql-code-generator": "^0.18.2",
    "graphql-codegen-add": "^0.18.2",
    "graphql-codegen-typescript-client": "^0.18.2",
    "graphql-codegen-typescript-common": "^0.18.2",
    "graphql-codegen-typescript-react-apollo": "^0.18.2",
    "graphql-codegen-typescript-resolvers": "^0.18.2",
    "graphql-codegen-typescript-server": "^0.18.2"

I managed to solve this problem by downgrading the "react-apollo" package realizing that in a working project the only different version was that of this package. So I replaced version 3.1.3 with version 2.5.8.
I'd like to know if there is another solution that doesn't involve downgrading.
Thanks in advance.

@NiccoloCase You're using old version of codegen. You can migrate to the latest version using this migration guide because new react-apollo is compatible with latest codegen.
https://graphql-code-generator.com/docs/migration/from-0-18


New example to list compute resource for SUBMIT_RUN job runs

Changes
From a discussion with @mgyucht on a request for getting a list of jobs submitted via jobs/submit and the associated compute resource(s). There are multiple compute-related fields returned in the response (both on the run, and on the task) so this example aims to disambiguate them.
Ran against AWS, Azure, GCP workspaces.
Tests

[ ] make test run locally
[ ] make fmt applied
[ ] relevant integration tests applied

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

Project coverage is 58.05%. Comparing base (94fc5e4) to head (69fac48).
Report is 14 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #572      +/-   ##
==========================================
+ Coverage   57.92%   58.05%   +0.12%
==========================================
  Files          45       44       -1
  Lines       27993    29738    +1745
==========================================
+ Hits        16216    17265    +1049
- Misses      11777    12473     +696

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


[demo] Docs link not available

Is this a BUG REPORT or FEATURE REQUEST?:
bug
What happened:
Syna's documentation is not accessible in the Syna demo.
What you expected to happen:
To be able to read the documentation.
How to reproduce it (as minimally and precisely as possible):
Visit the demo.
Anything else we need to know?:
I'm using https://about.okkur.io/syna/docs in syna-start. If that link can be activated it would be great.

syna/docs/ is based on v0.15. That means the docs would be for v0.15, while we released just v0.14.
We can do it, just wanted to mention the discrepancy.

Nice word. Didn't know it.
Totally forgot about the versioning on the docs. There are two arguments on this however. One is versioning and the other is that docs would be on the demo page and demo would be showing the latest build. Also the docs are way too out of sync for the release. Should we update the docs according to v0.14 and keep them on Github and in the next release move to docs on website?

Let's add the docs to the page with the v0.15 release. Keep the old docs link and mention they might be out of date. We can wait for v0.15 to launch on themes.gohugo.io, which also gives users the nice new docs page from the start so it makes sense to push this to v0.15. What do you think?

Should we still keep the old documentations?

You mean the readme etc.? I think as soon as we have the release and deployed it to okkur.org, we can move to a simple readme having a dev intro and linking prominently to the actual docs hosted on okkur.org. Or?

That sounds good. I didn't really remember the conversation we had on this.

This is now live. Most changes are live in preparation for v0.15. Currently we have a beta tag out and the v0.15 release branch will get the last fixes in the next few days.


Cleanup IR bypass code, removing overlay control and using groups

This PR

uses the IControl disabled functionality to grey out the controls
uses IControl groups to do the disabling in one go on relevant parameter changes
corrects a confusion between control tag and paramIdx (the EParams should not be interchanges with ECtrlTags!)

nice, can you tell me what you mean with this one please ?
corrects a confusion between control tag and paramIdx (the EParams should not be interchanges with ECtrlTags!)
Disabling the whole ir field would mean that an IR cant be loaded when IR is on bypass (cause the file - open icon is disabled), right ?

Yeah, so both in this PR and the previous one which added the new design, controls were given tags using parameter indexes. There are two separate lists of sequential integers that are used for different things - identifying parameters and identifying controls, so you shouldn't supply a parameter index to the control tag argument.
Since I added, the ir folder icon to the group that gets disabled you are correct that you can't click on it when the ir is disabled. That's easily changed though.

I like the fix on control tags vs param indices. What's the worst that can happen if not addressed?
On the other hand, I'd really like to keep the IR modifiable while disabled.
If it's not a crash-level risk then I'd rather not merge this PR to keep the latter over the former. But if it's fixable as you said then of course I'd happily merge if you can get that 🙂

It is a crash level risk, and all sorts of weird behaviour risk because it's just using the framework incorrectly!
It's easy to keep the IR modifiable, you just need to remove the relevant controls from the "IR_CONTROLS" group

Generally sticking a control on-top of other controls in order to disable them, although it might work, it is a hack and not the right approach, it involves more code and resources,

@sdatkinson @fichl in c0b1853c7bf25c3ef336e59873e812a42fa0d43e I've made it so the disabled controls still receive mouse events. 437fdb621d869461e55104be05df0d38e16fa0cc now also removes unused panel controls.

FWIW... in order to implement the left-right arrows to navigate IRs/NAMs some of this might change, but would be good to get this merged first

... this would be superseded by #242 but should be merged first!

@sdatkinson this one is ready! #242 replaces some of this stuff but would be great to merge this first


This is a fake PR to test cancelling workflows

Closing this because it showed that https://github.com/cython/cython/pull/5006 worked (and it wasn't a useful change!)


Unneeded namespace in BlazorServer example

I believe in the code under
"Add services and an endpoint for the SignalR hub",
using Microsoft.AspNetCore.ResponseCompression;
using BlazorServerSignalRApp.Server.Hubs;
the namespace "BlazorServerSignalRApp.Server.Hubs" is  not needed for your example.
I don't think this namespace exists and it does not compile until I remove it.
I'm still having trouble getting mine to work.  I downloaded the samples and the downloaded version works.  I'm comparing mine to that right now.
I believe this may be the line you wanted there:
using BlazorServerSignalRApp.Hubs;
The download and the version I am working through both have that line and not the other.
I'm not sure how I got that in there.  I may have used a smart tag.  I like to use the smart tags to insert the namespaces as I go instead of following the examples on the to usings so I can learn what the namespaces are.
I'm going to scrap and work my way through again.
I just wanted to report that little namespace thing.

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

ID: 85af7a99-672c-0438-dcc2-e8edfaf70c54
Version Independent ID: 85af7a99-672c-0438-dcc2-e8edfaf70c54
Content: Use ASP.NET Core SignalR with Blazor
Content Source: aspnetcore/blazor/tutorials/signalr-blazor.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @smiller7812 ... Yes, this is possible. Many code samples are pulled from the sample apps, but some aren't. This looks like a case where the code is static ... placed directly into the topic. This code must be manually updated but likely didn't get touched for the recent 6.0 release. I'll patch it up right now.
Thanks for reporting this. Leave this issue open. It will close automatically when the PR merges.

@smiller7812 ... Actually, let me revise that last remark ... now that I've looked closer.
That namespace was probably held over accidentally from the Blazor hosted WASM topic. It's not due to the 6.0 release. Yes, I think it should be removed.
I'll fix it right now. Leave this issue open. It will close automatically shortly.

Hummmm ... well ... it is in the sample app tho ...
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/tutorials/signalr-blazor/samples/6.0/BlazorServerSignalRApp/Hubs/ChatHub.cs#L4
I'll open it locally and see what's what. It is a bit strange that for the Blazor Server sample app that I retained the exact Hubs namespace from the hosted WASM solution (the Server project) ...
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/tutorials/signalr-blazor/samples/6.0/BlazorWebAssemblySignalRApp/Server/Hubs/ChatHub.cs#L4

There's another situation to take into account: Implicit usings for namespaces have resulted in these being optional. We'll be trying to work them OUT of the examples as we go. I'll drop them now where I can.


No Stats but Stream running - No automatic switching

Hey,
i setup nginx + automatic switching on a ubuntu vps. obs is running at home on a windows computer.
so far it is all working, i can connect to the rtmp, i can switch scenes through twitch chat etc.
But: i can not see any !bitrate, !sourceinfo or !obsinfo in chat.
The stat page is working and can be accessed.
i dont know how to fix it?
14:48 me: !sourceinfo
14:48 bot: [SRC] offline
14:48 me: !obsinfo
14:48 bot: [OBS] offline
14:49 me: !bitrate
14:49 bot: Current bitrate: offline
[7/7/2021] [2:03:19 PM] [OBS] › ℹ  info      Connecting & authenticating
[7/7/2021] [2:03:19 PM] [CHT] › ℹ  info      Connecting to twitch
[7/7/2021] [2:03:19 PM] [OBS] › ✔  success   Successfully connected
[7/7/2021] [2:03:20 PM] [CHT] › ✔  success   Successfully Connected
[7/7/2021] [2:03:20 PM] [CHT] › ✔  success   Authenticating and joining channel #me
config.json:
changed several times, from standard nginx to ip of nginx server from localhost/stat to ip/stat etc. etc. nothing changed there.
at the moment it is like this:
"rtmp": {
"server": "rtmp://IP:1935/publish/live",
"stats": "http://IP/stat",
"application": "publish",
"key": "live"
},
can anyone help here?

Sorry attached are my current config files.
nginx.config.txt
config.json-.txt

Hey @logmask ,
Are you streaming from OBS?

yes, OBS is running on windows on local pc
noalbs + nginx / node media server is on a ubuntu vps connecting through websocket to the obs on the computer
connection is fine, because i can change all scenes etc.
but i do not get any stats displayed in chat - also the switching is not working because there are no stats.
i just closed nginx server and started the built in node media server. i can connect with my mobile phone the rtmp stream. i can include it in obs. but i can not get any bitrate information etc. for automatic switichting and chat info.
this is right now with the built in node media server:
18:41 logmask: !b
18:41 logbotz: Current bitrate: offline
18:41 logmask: !s
18:41 logbotz: [SRC] offline
18:41 logmask: !o
18:41 logbotz: [OBS] offline
http://IP:8000/api/streams :
{"publish":{"live":{"publisher":{"app":"publish","stream":"live","clientId":"ID","connectCreated":"2021-07-07T16:41:40.821Z","bytes":17926089,"ip":"IP","audio":{"codec":"AAC","profile":"LC","samplerate":44100,"channels":1},"video":{"codec":"H264","width":1280,"height":720,"profile":"Baseline","level":3.1}},"subscribers":[]}}}

When you are streaming from OBS it should work, like actually streaming to twitch.


Absolutely no help

No examples given on usage.  Currently attempting to use in a LINQ Query Expression and and getting "could not be translated. Additional information: Translation of method 'Microsoft.EntityFrameworkCore.SqlServerDbFunctionsExtensions.DateDiffYear' failed. If this method can be mapped to your custom function, see https://go.microsoft.com/fwlink/?linkid=2132413 for more information. Either rewrite the query in a form that can be translated, or switch to client evaluation explicitly by inserting a call to 'AsEnumerable', 'AsAsyncEnumerable', 'ToList', or 'ToListAsync'. See https://go.microsoft.com/fwlink/?linkid=2101038 for more information."
queryable = from f in queryable
                    join e in context.Set<Experience>() on f.ID equals e.FacultyID
                    where
                        EF.Functions.DateDiffYear(e.StartDate, e.EndDate) >= years
                        && sp.Experience.Contains(e.TypeID)
                    select f;

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

ID: b826d5e1-f401-90e1-5fc8-62fdf10e6d43
Version Independent ID: 095d6b17-db1f-5b04-c487-71f24bde30fb
Content: SqlServerDbFunctionsExtensions.DateDiffYear Method (Microsoft.EntityFrameworkCore)
Content Source: dotnet/xml/Microsoft.EntityFrameworkCore/SqlServerDbFunctionsExtensions.xml
Product: ef-core-api
GitHub Login: @dotnet-bot
Microsoft Alias: avickers

@dave0783 can you please post a runnable code sample so that we can investigate? Also, can you confirm that you're running against SQL Server?

I passed the code snippet. After further review, we have determined that this is happening because our test environment is running SQLite; this error does not occur in the production environment using AzureSQL. That said, I still maintain the docs should still have example of usage; however, feel free to close this.
~Dave
On Feb 17, 2021, 4:20 PM -0500, Shay Rojansky<EMAIL_ADDRESS>wrote:

@dave0783 can you please post a runnable code sample so that we can investigate? Also, can you confirm that you're running against SQL Server?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Covered by https://github.com/dotnet/efcore/issues/17508


Do syntax highlighting for cubical terms in infowin

Right now Agda just dumps out some strings to show. It's fine but they're structured and easy enough to give some coloring to

https://github.com/Julian/lean.nvim does this by setting the infowin to a special filetype (which I added in #107) and then provides a syntax file for it: https://github.com/Julian/lean.nvim/blob/main/syntax/leaninfo.vim
we could probably do this too

This is probably a better technique than the current pretty-printer thing. I'd adore a similar PR on this front, if you have some energy @4e554c4c .


Allows enum types for id fields

This PR fixes an issue where enum types were being marked as invalid for id fields.
Also, I improved SchemaLoadingError, so that it shows the source of the error in jest, rather than inside the utility function. In addition, you can pass it an array of errors rather than strings. (It will still take those too!)
I also created the safelyLoadModel utility function, which uses Promise.allSettled to get a result that you can use toMatchObject, which allows for easier pattern-matching of complex responses.
For packages/schema/tests/schema/validation/datamodel-validation.test.ts, I broke up the expect calls into their own tests for easy identification of what went wrong when something breaks. They will of course show up as individual tests in the errors.

Thank you for working on the fix and clean-up @Ustice !


Feature/components

In this branch I:

[x] Deleted all the boilerplate from CRA (text, images, styles).
[x] Created a directory called components.
[x] Inside components, created a new Calculator.js file.
[x] In Calculator.js, created a React component that matches the provided design.
[x] Used class-based components.

Hi @VanessaAoki,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Notification not escaped

Laravel Version: 6.6.1
PHP Version: 7.3.5
Database Driver & Version:

Description:
Mail Notification line got a <code> tag added to the rendered html.
Steps To Reproduce:
Send a mail notification

Hey there,
Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to report back and I'll gladly help you out and re-open this issue.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!


Returning pgErrors option

What do you want to change?
Hi,
I am fairly new to sqlc, i like it alot, but I truly struggled with extracting proper data from the errors out of queries.
SQLC queries return the normal error which is just a string, while pg error that pgx uses for example has error codes and other very useful attributes
having a way to maybe instruct sqlc to generate code that adopts pgError instead of error would be extremely helpful
example usecase:
inserting a duplicate record into a users table would generate a message like this
ERROR: duplicate key value violates unique constraint "users_email_key" (SQLSTATE 23505)
such error messages cannot be sent to the client, it has to be formatted in a way or another to hide the nature of our database and be more user friendly.
What database engines need to be changed?
PostgreSQL
What programming language backends need to be changed?
Go

Well, turns out I can still parse that error message using pgconn.PgError itself actually
res, err := sqlc.somequery(ctx, ...)
if err != nil {
	var pgErr *pgconn.PgError
	if errors.As(err, &pgErr) {
		return &fiber.Error{
			Code:    fiber.StatusBadRequest,
			Message: pgErr.Message,
		}
	}
}


Migrate from global state to force the user to create SDK instance

The current SDK don't support talking with multiple tenants.
The user rely on the global state of the SDK module which makes it harder to debug problems

@f1cognite this is done, right?

Correct


Safe for catalina?

I see the build is failing, is this because of Catalina's changes to the readonly system partition? I'm hesitant to run this to test since it can be destructive.

The README needs to be updated. So there´s no travis-checks running..
I´m using it every single day and it works like a charm.. :)


Unhandled panic

While stress testing 500 tasks, I hit a panic
panic: runtime error: index out of range

goroutine 3758 [running]:
github.com/ohsu-comp-bio/funnel/util.NewDockerClient(0xc42000e468, 0x49f2366, 0x1b)
	/Users/buchanae/go/src/github.com/ohsu-comp-bio/funnel/util/docker.go:28 +0x20e
github.com/ohsu-comp-bio/funnel/worker.DockerCmd.Inspect(0xc42364b8d6, 0x6, 0xc42388d800, 0x2, 0x2, 0x4ee0d30, 0x0, 0x0, 0xc42364b924, 0xb, ...)
	/Users/buchanae/go/src/github.com/ohsu-comp-bio/funnel/worker/docker.go:92 +0xbb
github.com/ohsu-comp-bio/funnel/worker.(*stepRunner).inspectContainer(0xc4220a0300, 0x4e28740, 0xc4215f1b80)
	/Users/buchanae/go/src/github.com/ohsu-comp-bio/funnel/worker/step.go:94 +0x89
created by github.com/ohsu-comp-bio/funnel/worker.(*stepRunner).Run
	/Users/buchanae/go/src/github.com/ohsu-comp-bio/funnel/worker/step.go:50 +0x520

I have two fixes for this already, by the way.
The panic happened because we're not checking if a slice is nil. Also, in #144 I add a recover() call to the task runner, so panics (hopefully) won't crash the worker.
Possibly we need a recover() for all individual goroutines though?


Not able to decompress a tar.gz file

What steps did you take?
Tried to use Decompress to extract a tar.gz file
What did you expect to happen, and what actually happened instead?
Expected:  Contents to be extracted succesfully
Actual: Failed with the message -> format specified by source filename is not a recognized compression algorithm: tar.gz
How do you think this should be fixed?
https://github.com/mholt/archiver/blob/44285f7ed244a1c0c1de72a5ac145f585f784a89/targz.go#L26-L32
I noticed the CheckExt is checking for both extensions. But the file can have either one of them only. Think && has to change to ||
Also noticed this for a couple of other formats also. Eg. tarbz2

Oops, you might be right. Could you submit a PR?

Sure. I will fix the ones I can find that have the &&

I mistook another error and thought it was because of this. Existing code works fine.
 For a file which is tarred and gzipped.. like test.tar.gz, should I use Unarchive or DecompressFile?

Use Unarchive :)


v7.1.3 How to jump back and forth via years?

IMPORTANT - BEFORE CREATING YOUR ISSUE PLEASE READ THE FOLLOWING:

PLEASE STATE THE VERSION NUMBER you are using.
Are you using the latest version of JTAppleCalendar? Latest version is currently 7.1.3
PROVIDE ENOUGH INPORMATION SO I CAN RECREATE THE PROBLEM.

Hi, this is an amazing work. I have figured how to jump back and forth using month buttons. How would you (or anyone), suggest I implement a control to jump the calendar back or forward by a year?
Many thanks!

@daviddelmonte

get the current year youre on.
generate a date to the 1st of the following year
calendarView.scrollToDate(date)

Thanks.. That's great for one year plus or minus.. I need +- 5-10 years..

@daviddelmonte

get the current year youre on.
generate a date to the 1st of the next 5 years
calendarView.scrollToDate(date)

You can add how much ever years you want. And your code can be anyway you want. Here is an ugly example.
        guard let anyVisibleDate = calendarView.visibleDates().monthDates.first?.date else { return }
        let calendar = Calendar.current
        let year = calendar.component(.year, from: anyVisibleDate)
        let fiveMoreYears = year + 5

        let formatter = DateFormatter()
        formatter.calendar = calendar
        formatter.timeZone = calendar.timeZone
        formatter.dateFormat = "yyyy MM dd"
        let firstDateOfNextFiveYears = formatter.date(from: "\(fiveMoreYears) 01 01")
        print(firstDateOfNextFiveYears)

Thanks!! I ended up having a variable that the buttons would increment during a run. I can use that to add/subtract a year at a time..

cool

Sorry, I should have posted my code...
aYear is an Int..
Code is:

   @IBAction func nextYear(_ sender: Any) {
        self.aYear = self.aYear + 1
        //let nextYear = Date().nextYear + aYear
        let nextYear = Calendar.current.date(byAdding: .year, value: aYear, to: Date())
        calendarCollectionView.scrollToDate(nextYear!, animateScroll: true)

    }

    @IBAction func previousYear(_ sender: Any) {
        self.aYear = self.aYear - 1
        let previousYear = Calendar.current.date(byAdding: .year, value: aYear, to: Date())
        calendarCollectionView.scrollToDate(previousYear!, animateScroll: true)

    }


Update type of props.gl passed into WebGLRenderer

Per conversation in Spectrum here. Seems pretty straightforward. Sorry again for the delay. Please let me know if I missed something! 🙏

nice, thanks! will publish later


0.12 compatibility

It would be nice to have both master and 0.12 compatibility. This allows us to more easily apply new changes, and to keep 0.12 in CI. This can be done by comparing with @import("builtin").zig_version.
I don't think it makes sense to get compatibility with ALL development versions released in the meantime, so I think we'll only need to support latest master and latest stable.
Tasks:

[ ] Create some "compatibility" layer. Ideally, we only need to put a few things in it. Im thinking compat.zig or something where we just re-export renamed functions and write small wrappers. We'll see how well it goes.
[ ] Set up CI for 0.12 in addition to current master.
[ ] Update readme with explanation about new flow.

Supersedes https://github.com/Snektron/vulkan-zig/issues/124

@slimsag Would you be interested in maintaining compatibility with Mach nominated versions? It wouldn't be that much effort to add, but then there needs to be some infrastructure for keeping that up to date.


NPE at BIR when continue/break within lambda wrap

Description:
import ballerina/io;
public function main() {
    int[] arr = [1, 2, 3];
    foreach var item in arr {
        io:print(item);
        do {
            fail error("");
        } on fail error varName {
            continue;
        }
    }
}

Steps to reproduce:
Affected Versions:
SL beta 1
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Temporarily restricted the usage within break/continue usage within transaction and on-fail which are merely lambda wraps with #31250.
This is the same issue observed in https://github.com/ballerina-platform/ballerina-lang/issues/25558

Disabled few negative tests https://github.com/ballerina-platform/module-ballerinai-transaction/pull/222/commits/3590ef8157d3551d430035cf05711ce4e220f7e6


symfony 4.0  "snc_redis.default" service or alias has been removed

when i use $this->get("snc_redis.default")->hget($key, $field), error is display,
and in cache dir, public is false

snc_redis config is in /config/packages/framework.yaml
snc_redis:
clients:
default:
type:             predis
alias:            default
logging:          '%kernel.debug%'
dsn:              redis://localhost
cache:
type:             predis
alias:            cache
logging:          '%kernel.debug%'
dsn:              redis://localhost
profiler_storage:
type:             predis
alias:            profiler_storage
logging:          '%kernel.debug%'
dsn:              redis://localhost
session:
type:             predis
alias:            session
logging:          '%kernel.debug%'
dsn:              redis://localhost
monolog:
type:             predis
alias:            monolog
logging:          false
dsn:              redis://localhost

You are likely using AbstractController base class, which does not get the full container injected in Symfony 4. Either add snc_redis.default to the subscribed services or (better usually) inject the service via constructor injection.

@curry684 i just use predis now

That doesn't matter really, Symfony changed it's way of exposing services in 4 to be more efficient and performant.

@curry684 yes, Sy 4 is very like Java now, so i like it


ccmlib/scylla_node: _start_scylla: wait for repair

_start_scylla with wait_for_binary_proto=True may timeout
in debug mode when a node bootstraps with repair-based bootstrap.
Tolerate that by tracking repair - Repair \d+ out of \d+ ranges
log messages, to wait while reapir makes progress.
Allow 120 seconds of inactivity.
Signed-off-by: Benny Halevy<EMAIL_ADDRESS>Tested with materialized_views_test.py:TestMaterializedViews.mv_populating_from_existing_data_during_node_decommission_test in debug mode

@fruch please review


Make "wss" work the same as "wss2"

This is develop branch version of the patch applied to 0.50 to make sure "wss" and "wss2" work the same in the config. This fixes a bug reported in the forum.

@mellery451 if code never had bugs we'd be out of a job!

In 0.60.0-rc1


Update @yamada-ui/slider accessibility

Description
related https://github.com/yamada-ui/yamada-ui/issues/1505
This issue aims to address accessibility deficiencies in our slider component as per W3C guidelines.
The component currently does not meet the accessibility standards outlined in the W3C documentation.
The goal is to ensure the component is accessible to all users, including those using assistive technologies.
Ensure that all unchecked items in this checklist should be addressed.

[ ] If the value of aria-valuenow is not user-friendly, e.g., the day of the week is represented by a number, the aria-valuetext property is set to a string that makes the slider value understandable, e.g., "Monday".

Problem Statement/Justification
improve accessibility
Proposed Solution or API
No response
Alternatives
No response
Are you willing to participate in implementing this feature and create a pull request include the implementation?
None
Additional Information
No response

I'll try it.


Sharing large data objects

During the OPTIMADE meeting of 21-10-2022 and in the discussion on the trajectory endpoint #377, the idea was raised to have a more universal way of sharing large data objects that may be too large to comfortably fit in a single JSON response. This would require a way to return such properties across multiple responses and to specify which parts a user wants to retrieve.
Below I have given a description of how we could implement this. In some ways it is still quite minimalistic, and we could perhaps also think about how we would like to present datasets/tables in general.
I look forward to your feedback and once we agree on the rough outline sketched here, I will write a proposal with all the details to add it to the Optimade specification.
Marking
The user should somehow know which properties of an entry can be retrieved in pieces, i.e. are indexable.
One option is to have a field to list all the properties that can be indexed, for example:
indexable_properties: [cartesian_site_positions, _exmpl_kinetic_energy, _exmpl_potential_energy]
Another option would be to use a common prefix as suggested by @rartino for all properties, for example: series_cartesian_site_positions or indexed_cartesian_site_positions
Edit: Would such prefixes not interfere with the database specific prefixes?
What are your opinions on this ?
Indexing
In general, we cannot assume that all the properties use the same index, as was the case for the trajectories where the frame number was the common index. (i.e. two datasets may be present in one entry. For example, a trajectory from a Monte Carlo simulation which uses the Monte Carlo Step as the index and a set of radial distribution functions where the index corresponds to a distance from the central atom.)
Therefore, we should have a mechanism to specify for each property which range should be retrieved.
One way to do this would be to have a ranges query parameter :
ranges = cartesian_site_positions[1, 2000, 10], _exmpl_kinetic_energy[1, 2000], _exmpl_potential_energy[1, 2000]
The 1st value would be the index of the first value that should be returned, the 2nd value the index of the last value that should be returned and the 3rd value would be the step size.
We could also allow a more concise writing style where we allow multiple names per range such as:
ranges=cartesian_site_positions[1, 2000, 10], (_exmpl_kinetic_energy, _exmpl_potential_energy, _exmpl_constraint_force)[1, 2000]
Index_groups
To be able to know if the index of one property corresponds to with the index of another property, we need to know if both properties have the same index.
We therefore need to define an index for each group of correlated properties.
For example:
Index_groups: [{“name”: “trajectory”, “n_indexes”: 20000}, {“name”:“radial_distribution_function”, “n_indexes”:1000}]
Property descriptors
Similar to how we defined properties in the trajectory proposal, we could define each indexable property as a dictionary.
Here, we could reuse many of the properties already defined for the trajectory endpoint in PR#377 to describe how the values belong to the index. For brevity, I have not included all the details, but they can be found in PR#377.

serialization_format:

Description: To improve the compactness of the data while still maintaining  there are several ways to show to which frame a value belongs. Which method has been used is specified by the :property:serialization_format.

offset_linear

Description: If :property:frame_serialization_format is set to :val:"linear" this property gives the value at frame 1..
Examples:
:val:1.5

step_size_linear:

Description: If :property:frame_serialization_format is set to :val:"linear", this value gives the change in the value of the property per unit of frame number.
e.g. If at frame 3 the value of the property is 0.6 and :property:step_size_linear = 0.2 than at frame 4 the value of the property will be 0.8.
Examples:
:val:0.0005

offset_sparse:

Description: If :property:frame_serialization_format is set to :val: "explicit_regular_sparse" this property gives the frame number to which the first value belongs.
Examples:
:val:100

step_size_sparse:

Description: If :property:frame_serialization_format is set to :val: "explicit_regular_sparse", this value indicates that every step_size_sparse frames a value is defined.
Examples:
:val:100

sparse_frames:

Description: If :property:frame_serialization_format is set to :val:"explicit_custom_sparse", this field holds the frames to which the values in the value field belong.
Examples:
:val:[0,20,78,345]

values:

Description: The values belonging to this property.
The format of this field depends on the property and on the :property:frame_serialization_format parameter. It is only returned when the variable name is present in “ranges”.

In addition to these properties already defined in the trajectory proposal, we would also need to define which “index” the property uses.

index_group:
This property indicates which index belongs to this property. It matches one and only one of the values in the indexes property.
For example: "index_group":“radial_distribution_function”

Sub properties for Querying
It would take too much time to perform queries on all the values of a large property. Therefore, a number of sub properties can be defined which can be used to perform queries and make selections. Whether it makes sense to have these properties depends on the context and variable type, so I think they should all be optional.
Such properties are:

average  i.e. the average value of a numerical property.
min        i.e. the minimum value of a numerical property.
max       i.e. the maximum value of a numerical property.
set	       i.e. a set of all the values the property takes.

Thanks for putting this together. I realize from what you wrote that I like "ranged" (e.g., "ranged properties") as a keyword for all this.

Another option would be to use a common prefix as suggested by @rartino for all [indexable] properties. [...] Would such prefixes not interfere with the database specific prefixes?

If we go with this, the specification should probably say that these prefixes go after the database-specific prefix if present, e.g., _exmpl_ranged_cartesian_site_positions.

In general, we cannot assume that all the properties use the same index

This is an interesting extension of the design.
We were already discussing in #377 what to return for "ranged properties" when no range was provided. So, I would suggest to throw all the meta-data needed to handle these properties into those responses, instead of having separate properties as you suggest above, e.g., for "ranges" and "index groups".
So, very much in line with your own design in #377: the user first just sends a standard OPTIMADE query. Some members one get back somehow indicate that they are ranged, and directly in the response you get all the meta-data you need to query over those ranges. Based on that, a subsequent query with added OPTIMADE range parameters now give you a response where these keys instead map to actual data. Note: this is meant to just as closely as possible reflect your own design in #377.
So, something like this. A first regular query to the trajectory endpoint gives:
...
"ranged_cartesian_site_positions": {
  "range_id": "frames",
  "serialization_format": "linear",
  "offset_linear": 0,
  "step_size_linear": 1.5,
  "count": 4711,
},
"ranged_species_at_sites": {
  "range_id": "frames",
  "frame_serialization_format": "explicit_custom_sparse",
  "sparse_frames", [0,4,5,9],
  "values":[273,273,293,293],
  "count": 4711,
},
...

(Note how I implicitly have suggested here that range_id is a string identifier that connects multiple properties to the same range, i.e., your "index groups").
Looking at this response, you may, e.g., send a follow-up query with, e.q., the added REST query parameters: range_frames_start=12&range_frames_count=42, which would give you, e.g.,:
...
"ranged_cartesian_site_positions": [
  ... actual data for frame 12 to 53...
],
"species_at_sites": [
  ... actual data for frame 12 to 53...
]
...

This leads to very sensible syntax for querying either on the meta-data or ranged data.

For meta-data, just use the subfield query syntax and no range parameters, e.g.:
  filter=_exmpl_ranged_my_long_intlist,count>96

to get all entries where exmpl_ranged_my_long_intlist contains more than 96 values.

For ranged data, just use the list query syntax along with a range parameter for the range you want to query on:
filter=_exmpl_ranged_my_long_intlist HAS 42&range_intlist_start=1&range_intlist_count=1000

to get all entries where the number 42 occurs in the first 1000 values.

Finally, I suggest to take a look if you can cut down the options of the serialization_format. It seems to me there is some overlap in what they can provide, and interoperability is going to take a hit if there are too many ways of returning data. If one serialization format can be re-mapped into another cheaply on-the-fly as the endpoint returns data, then there really is no need for both IMO.

We were already discussing in https://github.com/Materials-Consortia/OPTIMADE/pull/377 what to return for "ranged properties" when no range was provided. So, I would suggest to throw all the meta-data needed to handle these properties into those responses, instead of having separate properties as you suggest above, e.g., for "ranges" and "index groups".

The bit of remaining data in "index_groups" could indeed be moved to the individual properties. We would only duplicate the length of the range, which is not much data compared to the whole property.

So, very much in line with your own design in https://github.com/Materials-Consortia/OPTIMADE/pull/377: the user first just sends a standard OPTIMADE query. Some members one get back somehow indicate that they are ranged, and directly in the response you get all the meta-data you need to query over those ranges. Based on that, a subsequent query with added OPTIMADE range parameters now give you a response where these keys instead map to actual data. Note: this is meant to just as closely as possible reflect your own design in https://github.com/Materials-Consortia/OPTIMADE/pull/377.

Yes, that is correct.
In the example you give, the ranged_species_at_sites property already has the fields values and sparse_frames in the first response. Those are however the fields that contain the main data, so I would only return those when specifically requested.
"range_id" seems to be a good name for what I called "index group".
The query parameters you suggest for retrieving ranges (range_frames_start and range_frames_count) are different from the ranges query parameter I suggested. Is there a reason you prefer these ?
The ranges query parameter I proposed has the advantage that you can retrieve multiple ranges in one request.
I was not planning to support queries on the data of the properties itself, as this would often be way too much information to process. We could add it in a future PR if there is a demand for it.
That is also why I thought about adding the aggregated properties (min, max, average, and set).
Considering the "serialization_format", we could perhaps drop constant, as I am not sure whether it adds that much compared to the normal way we declare variables. You could argue that constant is the default value for a property and that only when it is not constant you turn it into a ranged property. You could also use the linear option and set the step_size_linear to zero, so you effectively also have a constant value.

In the example you give, the ranged_species_at_sites property already has the fields values and sparse_frames in the first response. Those are however the fields that contain the main data, so I would only return those when specifically requested.

I'm not sure I follow this - if you mean that one should do something different from what I wrote as an example, can you edit the example?

The query parameters you suggest for retrieving ranges (range_frames_start and range_frames_count) are different from the ranges query parameter I suggested. Is there a reason you prefer these ?
The ranges query parameter I proposed has the advantage that you can retrieve multiple ranges in one request.

Apologies, I missed how you meant that as the query parameter syntax. While your syntax is more compact, it is more complex and will require actual parsing on the server side; maybe even a grammar... Is there any real benefit in trying to overload the query parameters this way other than to save URL space? By separating it up in multiple query parameters, it is also easier to specify that, e.g., range_frames_stepsize is allowed to be supported but not required. (I really like to design optional features so they lead to zero additional overhead for someone who does not want to bother with them.)
Furthermore, if we want to standardize range_frames_stepsize (like this, or with your syntax), we need to very carefully spell out how this interacts with the various ways data can be sparsely represented. Have you already thought about these things?

I was not planning to support queries on the data of the properties itself, as this would often be way too much information to process. We could add it in a future PR if there is a demand for it.

The complexity overhead for the specification in including this as an optional feature is minimal. It is going to be a single sentence. It also makes sense to allow it, when thinking of possible uses of ranged data outside of MD frames.

That is also why I thought about adding the aggregated properties (min, max, average, and set).

These are good - IMO they apply to the whole data, and should go in the response for the property key when not requesting a range. That makes it very easy to add your own data-base-specific aggregated properties. The only thing I don't see is a way to ask for, e.g., the average over a sub-range of data, but I'm OK with that feature not being supported.

Considering the "serialization_format", we could perhaps drop constant, as I am not sure whether it adds that much compared to the normal way we declare variables.

Good. But in your opinion, all the others are needed? I'll take a look through them to see if I agree. As I said, if someone can map one into another cheaply on-the-fly, then both are not necessary.

I'm not sure I follow this - if you mean that one should do something different from what I wrote as an example, can you edit the example?

Here, I have placed what I think should be returned for the ranged fields when the fields are not specified with the range parameter.
...
"ranged_cartesian_site_positions": {
  "range_id": "frames",
  "serialization_format": "linear",
  "offset_linear": 0,
  "step_size_linear": 1.5,
  "count": 4711,
},
"ranged_species_at_sites": {
  "range_id": "frames",
  "frame_serialization_format": "explicit_custom_sparse",
  "count": 4711,
}, ...

Apologies, I missed how you meant that as the query parameter syntax. While your syntax is more compact, it is more complex and will require actual parsing on the server side; maybe even a grammar... Is there any real benefit in trying to overload the query parameters this way other than to save URL space? By separating it up in multiple query parameters, it is also easier to specify that, e.g., range_frames_stepsize is allowed to be supported but not required. (I really like to design optional features so they lead to zero additional overhead for someone who does not want to bother with them.)

The way I formulated it now probably does require a grammar update. The advantage over the method, you suggested/in the original trajectory proposal, is that you can specify the range per property, and that it also specifies for which properties you want to retrieve all the data. In the old design, we would have to do multiple queries if we would want to use multiple different ranges. Each time, listing the appropriate fields under the response_fields parameter.

Furthermore, if we want to standardize range_frames_stepsize (like this, or with your syntax), we need to very carefully spell out how this interacts with the various ways data can be sparsely represented. Have you already thought about these things?

I am not sure what you mean exactly with "range_frames_stepsize".
I did think about what to do in case of sparse data when implementing the original trajectory proposal.
If no step size was specified (only a first and/or last frame) I would only return a value for those indexes for which a value has been defined. In case the step size parameter was present, I would return a value for each index specified by the step size parameter and None if no value had been defined for that index.

The complexity overhead for the specification in including this as an optional feature is minimal. It is going to be a single sentence. It also makes sense to allow it, when thinking of possible uses of ranged data outside of MD frames.

As long as it is fully optional, we could add it, although I wonder whether it will be implemented.

These are good - they apply to the whole data, and thus IMO should go in the response for the property key when not requesting a range. That makes it very easy to add your own data-base-specific aggregated properties. The only thing I don't see is a way to ask for, e.g., the average over a sub-range of data, but I'm OK with that feature not being supported.

Yes, that is the idea. My idea is that OPTIMADE is for data retrieval and not analysis, so calculating the averages over parts of the range does not seem like a core task of OPTIMADE for me.
Although I do know that some people actually deposited their trajectories into the BioExcel database because they also do some analysis.

Good. But in your opinion, all the others are needed? I'll take a look through them to see if I agree. As I said, if someone can map one into another cheaply on-the-fly, then both are not necessary.

Now I think of it, we could also drop "explicit". You could use "explicit_regular_sparse" instead, and then specify the step_size_sparse as 1 and the offset_sparse as 0.
(I think that if we have fewer options we could make the names a bit simpler too.)
That leaves us with three options, and each would include significantly more data as the others. Therefore, I think three methods("linear" (the value is defined by a linear equation), "regular"(the values are defined at fixed intervals), and "custom" (for each value the index is explicitly specified.) would be optimal.
In principle, we could still drop "regular" but that would double the size for some properties.
In theory, we could even make a more general equation option instead of linear, but that may require a whole new discussion on how to define equations unless we can find an already existing standard.

@JPBergsma IMO the specification is good as it is in this regard. partial_data_links is completely defined as the channel in which partial data is communicated via JSON:API-formatted responses, in parity with how we define property_metadata. It does not need to be seen as "metadata that applies to the whole entry" (and arguably it very much isn't; just like property_metadata it has separate keys for each property.) Give these parts of the specification another read as they presently are expressed in the develop branch and see if you agree.

I was just wondering whether the fields in partial_data_links should have property definitions, as you wrote you did not yet know where these should go for fields directly under meta.

partial_data_links doesn't need a property definition. It can only deliver partial data links in a format that is fixed and already fully documented in the specification. (Which should go in the static part of the JSON:API response schema, but that is not the same thing.)

Ok, than we can leave it like this.

I do not see why this issue cannot be closed with the merging of #467? If I don't hear anything here I will close it.

I do not see why this issue cannot be closed with the merging of #467? If I don't hear anything here I will close it.

I concur! Closed by #467


ISPN-15183 SIFS remove with no key can cause stats to not track free …

…size properly
https://issues.redhat.com/browse/ISPN-15183

Thanks @wburns


Proposal for rn-reusables-cli

I looked into how shadcn-ui works, it basically have a JSON to pull from:
https://ui.shadcn.com/registry
We can have a second repository to keep this json list from github, we can get inspiration from https://github.com/shadcn-ui/ui/blob/main/packages/cli/src/index.ts

(copied from your previous issue)
It's great to see your enthusiasm for enhancing the repo.
To help me categorize bugs from requests I've set up the Discussions section. Please add your idea to the "Ideas" category there and we'll close this issue.
Thanks!


Move header to consts file

Fixes #681
Reference #714

@shcheklein Oh I forgot about this. :sweat_smile:  I think @iAdramelk meant to replace className by id so that it can be unique.

@algomaster99 so, if you actually introduce the change required (unique id), I think this PR will become obsolete.

@shcheklein I can push one more commit and change the title? :laughing:

@algomaster99 👍

Doesn't seem to work as perfectly as the previous version. It doesn't scroll all the way to the header, the lower you go, the greater the offset. So at some point the CONTENTS table in the right side bar doesn't select the correct header either. Seems like a linear error in the offset math.

https://dvc-org-pr-717.herokuapp.com/doc/tutorials/versioning#automating-capturing

Also, this contains changes for #714 right? Just curious.

@jorgeorpinel This existed before changing it to id as well.
The problem is really weird though.
On checking the output of
 console.log(elementBoundary.top, '= top')

it shows two different results when hard-reloaded and then reloading by server.

The elementBoundary.top signifies the position of the header w.r.t. the viewport. I am confused how it shows two different outputs.
P.S. This is only happening with markdown files with large text inside.

@algomaster99 this a known issue with pages that have images - it takes time to load them. I think it can be fixed as a separate issue (by providing a hint along with the image? I don't know yet).
@iAdramelk @algomaster99 either I don't understand what the unique id mean or this is not done yet?

@shcheklein this is done. It was on hold because of https://github.com/iterative/dvc.org/pull/717#issuecomment-545170093

@shcheklein Can you open a separate issue for this delay in image loading? Also, have you thought of any solution to this?

@algomaster99 I think you should have more context to describe it - so, feel free to create a ticket :) No, I don't have any good solution in mind, except some complicated logic that will be calculating height of every # before loading. I would also take a look if it's a problem other people have tried to or solved already. I can imagine that any website that has images should have a similar issue, right?

@shcheklein Since this PR doesn't only involve changing className to id for the header, I think I should also add an id for tooltip-container.

@algomaster99 let's do as a separate one.

@algomaster99 we had similar problem on with right panel. We solved it using this code https://github.com/iterative/dvc.org/blob/master/src/Documentation/RightPanel/RightPanel.js#L11-L43
But in only solves it for images, if there is some other elements that can change container height, there is still be a bug.

Can't the scrolling (re)run after window.onload with some vanilla JS?

@jorgeorpinel if I remember correctly window.onload triggers before images are loaded.

Easiest way to solve this problem would be by using ResizeObserver, but unfortunately Safari and IE didn't support it and it's polyfills are large and slow.

The load event fires at the end of the document loading process. At this point, all of the objects in the document are in the DOM, and all the images, scripts, links and sub-frames have finished loading.

From https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/onload

@jorgeorpinel Yes, you are right. I misremembered what the problem was. window.onload is indeed fires after initial page load. But in our case we downloading and rendering markdown files after initial page load so we can't use window.onload to find if images are loaded or not.

Ah, makes sense thanks for the reminder. Oh well, scrolling seems to work great now 🙂

p.s. never mind, reloading URLs with #anchors in pages with images before the anchor (e.g. https://dvc.org/doc/tutorials/versioning#preparation) still misses the offset. Should we open a separate issue for this?

UPDATE: created #750 for this.


selinux-policy: Change SELinux policy module composition.

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

Change SELinux policy module composition so downstream users can replace or disable all policy modules.
Change Log

Change SELinux policy module composition.
Deprecate selinux-policy-modules.

Does this affect the toolchain?

NO
Test Methodology

Pipeline build id: 625074
Local upgrade testing

root [ /home/pebenito ]# rpm -ql selinux-policy-modules
(contains no files)
root [ /home/pebenito ]# rpm -q selinux-policy-modules
selinux-policy-modules-2.20240226-7.azl3.noarch


Release Google.Cloud.Kms.V1 version 3.4.0

Changes in this release:
New features

Add support for Coordinated External Keys (commit 08d67d7)

Created release for Google.Cloud.Kms.V1-3.4.0


Use gtfs-lib 3.3.0

 Issue by l-vincent-l
Monday Dec 11, 2017 at 15:30 GMT
Originally opened as https://github.com/catalogueglobal/datatools-server/pull/62

I couldn't validate this dataset https://www.data.gouv.fr/fr/datasets/tisseo-offre-de-transport-gtfs/ with the  3.2.0

l-vincent-l included the following code: https://github.com/catalogueglobal/datatools-server/pull/62/commits

 Comment by abyrd
Tuesday Dec 12, 2017 at 10:25 GMT

Hello @l-vincent-l . If you want to try out current code, check out the release version v3.2.0 of datatools-server, which depends on v3.3.0 of gtfs-lib. The issue here is not exactly that this single version update patch needs to be applied to the dev branch, it's that the dev branch would need to be caught up to master before additional development work is undertaken. No changes have occurred on dev since the last release off the master branch.

 Comment by l-vincent-l
Wednesday Dec 13, 2017 at 09:48 GMT

Ok, so I close this PR.


Unexpected token '?'

Getting unexpected token in the latest 8.0.1 and 8.0.0 versions when trying to run any concurrently commands
It is working fine till v7.6.0

What's your node version?
8.0.0 dropped support for Node 12, which allows concurrently to make use of syntax such as ?..

Right! In this case please upgrade to Node 14, or stick to concurrently v7.


make config file created same as the documentation

Either we make the documentation here refer to a "~ /.jira-cl.json" config file being created or we make the code create a "~/.jira-cli.json" file to match the docs.
Engineers rely on the docs as an accurate source of truth about what the code is doing.
Feel free to close this if the docs and repo readme are updated.

You're right @VincentHokie, thanks for the PR!


[KOGITO-8517] - Support external resources configuration for Workflow CR in devmode

Wait for https://github.com/kiegroup/kogito-serverless-operator/pull/66
See:https://issues.redhat.com/browse/KOGITO-8517
Signed-off-by: max<EMAIL_ADDRESS>
Description of the change:
Motivation for the change:
Checklist

[ ] Add or Modify a unit test for your change
[ ] Have you verified that tall the tests are passing?

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

Blocked by #66

@desmax74 can you review this PR to consider the new approach? I believe that your ConfigMap "creator" should be in the reconciler_dev.go file and also have a mutator for the workflow deployment. wdyt?

@ricardozanini sure, the PR was still in the limbo and in util for a reason :)

@ricardozanini sure, the PR was still in the limbo and in util for a reason :)

I just asked because you converted from "draft" to "ready", so I thought you considered this one final. :(

@ricardozanini sure, the PR was still in the limbo and in util for a reason :)

I just asked because you converted from "draft" to "ready", so I thought you considered this one final. :(

Was final for the APIs to handle the configmaps not final in the way to link the new structure.
I'm going to prepare an impl to handle one configmap per type and preserving the types in the workflow-external-resources-config configmap

@ricardozanini isn't this very similar with the CM stuff that you are adding?

@spolti it is. I think he will review it as soon as we merge #73

#73 is merged.

Replaced by https://github.com/kiegroup/kogito-serverless-operator/pull/81 becasue github is messed with this PR and the previous commit on the main


This fails on my system with storybook (app and tests its ok)

Bugs when trying to run this projects with storybook:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'storybook' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestorybook', 'storybook', 'poststorybook' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prestorybook, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/prjsprod/meteor_1.3/mantra-sample-blog-app/node_modules/.bin:/usr/bin:/usr/lib/hardening-wrapper/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/prjsprod/meteor_1.3/mantra-sample-blog-app
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'start-storybook -p 9001 -s ./public' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec storybook script
14 verbose stack Error<EMAIL_ADDRESS>storybook: start-storybook -p 9001 -s ./public
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:244:16)
14 verbose stack     at emitTwo (events.js:100:13)
14 verbose stack     at EventEmitter.emit (events.js:185:7)
14 verbose stack     at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:100:13)
14 verbose stack     at ChildProcess.emit (events.js:185:7)
14 verbose stack     at maybeClose (internal/child_process.js:850:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /home/prjsprod/meteor_1.3/mantra-sample-blog-app
17 error Linux 4.3.3-2-ARCH
18 error argv "/usr/bin/node" "/usr/bin/npm" "run" "storybook"
19 error node v5.11.0
20 error npm  v3.8.7
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>storybook: start-storybook -p 9001 -s ./public
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>storybook script 'start-storybook -p 9001 -s ./public'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the mantra-demo package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     start-storybook -p 9001 -s ./public
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs mantra-demo
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls mantra-demo
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
Thanks.

Same problem here and I'm running NPM 3.9.6
09:12 $ npm run storybook

><EMAIL_ADDRESS>storybook /Users/alexandreroba/projects/mantra-sample-blog-app
> start-storybook -p 9001 -s ./public

=> Loading static files from: /Users/alexandreroba/projects/mantra-sample-blog-app/public .
=> Loading custom .babelrc
=> Loading custom webpack config.

React Storybook started on => http://localhost:9001/

webpack built 8519f0f246defad03602 in 760ms
Hash: 8519f0f246defad03602
Version: webpack 1.13.1
Time: 760ms
            Asset    Size  Chunks             Chunk Names
preview.bundle.js  471 kB       0  [emitted]  preview
manager.bundle.js  913 kB       1  [emitted]  manager
chunk    {0} preview.bundle.js (preview) 166 kB [rendered]
    [0] multi preview 52 bytes {0} [built] [2 errors]
    [1]<EMAIL_ADDRESS>10.5 kB {0} [built]
    [2]<EMAIL_ADDRESS>2.76 kB {0} [built]
    [3]<EMAIL_ADDRESS>4.71 kB {0} [built]
    [4]<EMAIL_ADDRESS>13.4 kB {0} [built]
    [5] (webpack)/~/node-libs-browser/~/buffer/index.js 42.8 kB {0} [built]
    [7]<EMAIL_ADDRESS>340 bytes {0} [built]
    [8]<EMAIL_ADDRESS>12.8 kB {0} [built]
    [9]<EMAIL_ADDRESS>6.18 kB {0} [built]
   [10]<EMAIL_ADDRESS>1.54 kB {0} [built]
   [11]<EMAIL_ADDRESS>4.25 kB {0} [built]
   [12]<EMAIL_ADDRESS>2.34 kB {0} [built]
   [13]<EMAIL_ADDRESS>3.62 kB {0} [built]
   [14]<EMAIL_ADDRESS>38.4 kB {0} [built]
   [15]<EMAIL_ADDRESS>13.5 kB {0} [built]
   [16]<EMAIL_ADDRESS>405 bytes {0} [built]
   [17]<EMAIL_ADDRESS>16 bytes {0} [built]
   [18] (webpack)/~/node-libs-browser/~/buffer/~/base64-js/lib/b64.js 3.57 kB {0} [built]
   [19] (webpack)/~/node-libs-browser/~/buffer/~/ieee754/index.js 2.05 kB {0} [built]
   [20] (webpack)/~/node-libs-browser/~/buffer/~/isarray/index.js 132 bytes {0} [built]
   [21] (webpack)/~/node-libs-browser/~/process/browser.js 2.31 kB {0} [built]
chunk    {1} manager.bundle.js (manager) 372 kB [rendered]
    [0] multi manager 28 bytes {1} [built]
    [6]<EMAIL_ADDRESS>372 kB {1} [built]

ERROR in multi preview
Module not found: Error: Cannot resolve module 'webpack-hot-middleware/client' in /Users/alexandreroba/projects/mantra-sample-blog-app
 @ multi preview

ERROR in multi preview
Module not found: Error: Cannot resolve module 'babel' in /Users/alexandreroba/projects/mantra-sample-blog-app
 @ multi preview
^C
✘-INT ~/projects/mantra-sample-blog-app [master|✔]
09:16 $ npm --version
3.9.6


Android 5+: Bluetooth.startScanning scanFilters don't work

When passing a service UUID to startScanning() for use as scan filter, no peripheral is found.
This is reproducible on at least two different BT LE capable devices with differing variants of Android 6.
it is probably due to known issues in the BT LE implementation of Android 5/6 as mentioned here: https://github.com/EddyVerbruggen/nativescript-bluetooth-demo/issues/4
In fact I had the same problem when trying this myself some time ago with NativeScript as well as with native Android code (then testing on Android 5.1), following different examples from the web, and at some point decided to rather build a workaround.
I'd be happy if some in-deep Android developer would prove me wrong.
Otherwise, to make startScanning() work as expected and fully cross platform, the only reliable solution seems to be scanning for all devices on Android 5+, doing the filtering as an afterwork in the callback's onScanResult() and from there call onDiscovery() conditionally.
The alternative would be leaving that check to the app developer. But this would violate the cross platform idea and may well result in similar bug reports in the future.

Can you tell me which Android and BLE devices you tried this with and what the Service UUID is? Perhaps I can test with a similar set of devices and (perhaps) reach the same conclusions as you. Having the plugin do filtering after discovery would then make the most sense indeed.

In short: damn, it works now ... ;-)
Android devices:

LG Nexus 5 with Android 6.0.1 (CM 13.0-20160209 Nightly)
Nvidia Shield Tablet K1 with Android 6.0, build MRA58K.41524_664.1902

main testing peripheral:
blood pressure meter Medisana BW 300 connect, has service UUIDs: 1800, 1801, 180a, 180f, 1810
Originally (a few hours ago), I was scanning for service UUID 1810 (Blood Pressure) and both Android devices never found the peripheral. I did several clean builds during the test and especially no livesync.
While writing this comment I tested again with unchanged app code, but a fresh install of the plugin.
Now I see successful detections.
In both test runs I ensured that the peripheral actually has Bluetooth active when scanning.
So atm, I can't reproduce the condititions under which the problem occurs.
I did a recursive diff of the plugin (current fresh install vs. the one of the first test run) to make sure I didn't accidently break something before, but there was nothing that could have led to that.
Since this is not reproducible anymore, I suggest to close this concrete issue but to keep an eye on it.
However, while fiddling around, I found another Android issue with 128-bit-UUIDs only, but reportedly in both BLE APIs at least from 4.3 to 5.1, as the comments there suggest: https://code.google.com/p/android/issues/detail?id=59490&q=BLE&colspec=ID Type Status Owner Summary Stars

Ah man that's unpleasant! I'll leave this open so you can add to it if something similar pops up. Thanks for your elaborate comments!

Hey, just one question, I am not sure if it relevant to this issue. I tried to install the bluetooth demo on two Android mobile phones (both have Android 4.4) and they were not able to find each other. Is it expected that the plugin searching only for peripherals or also it supposed to search for other BLE phones?

@OldrichKruchna Good question. This plugin acts as 'Central' so it can connect to peripherals. If your phone can't act as a peripheral (which to my knowledge it can't) then that won't work.

Thank you for answer, I did some research and it seems that both IOS and Android support their phones to act as a peripheral, Android from version 5.0 and IOS from version 6:
Android 5.0, an Android device can now act as a Bluetooth LE peripheral device.
As of OS X v10.9 and iOS 6, Mac and iOS devices can also function as Bluetooth low energy peripherals
Would be pretty cool to support this functionality as well ;)

Hi I am testing on my Lenovo TAB2 with And. 5.0.1. I have iMac with BT keyboard and mouse but none of them (iMac 27 Retina, mouse, keyboar) are found :(.

@Pepan Because either those devices are not LE, or they're already engaged in a connection which most (all?) LE devices don't support.

Agree with @EddyVerbruggen its either the bluetooth is not LE or its already connected to other device.


ValueError: unichr() arg not in range(0x10000) (narrow Python build)

python: 2.7.10 (the macOS builtin Python)
os: macOS 10.11.5
here is my iconfont.css file
iconfont.css.txt
➜  ux_1473385914_8062558 icon-font-to-png --css iconfont.css --ttf iconfont.ttf --size 128
Traceback (most recent call last):
  File "/usr/local/bin/icon-font-to-png", line 16, in <module>
    command_line.run(sys.argv[1:])
  File "/Library/Python/2.7/site-packages/icon_font_to_png/command_line.py", line 97, in run
    keep_prefix=args.keep_prefix)
  File "/Library/Python/2.7/site-packages/icon_font_to_png/icon_font.py", line 24, in __init__
    self.css_icons, self.common_prefix = self.load_css()
  File "/Library/Python/2.7/site-packages/icon_font_to_png/icon_font.py", line 62, in load_css
    icons[name] = unichr(int(val[1:], 16))
ValueError: unichr() arg not in range(0x10000) (narrow Python build)

Does it work with Font Awesome ttf and css files?
Also from quick Google'ing:
https://github.com/lambdalisue/e4u/issues/1
https://github.com/HypothesisWorks/hypothesis-python/issues/29
So the quick fix should be to install latest Python via Homebrew, but I'll look into it and try to fix it on the default build in macOS too.


completion autopopup seems to be broken

Using a build of the IntelliJ plugin from master and IntelliJ 2016.3.4, autopopup of completion proposals no longer seems to work. I'm not sure at what point this broke.

What's happening is that an optimization we added to compute proposals faster is half-broken: when we add more characters to an existing identifier, we skip the typecheck part because we know it shouldn't affect the result. But, this results in a Node that has a no scope (yet), and the completion manager needs that scope to compute proposals:
        value fsv = FindScopeVisitor(node);
        fsv.visit(typecheckedRootNode);
        value scope = fsv.scope;

        if (!exists scope) {
            return;
        }

I got it working by finding the equivalent Node in the last typecheck compilation unit.


Add signatures to the generated index

Motivation
When we release plugins we can now add signatures and check them (see example: https://github.com/falcosecurity/falcoctl/pull/305)
Now we need to make sure that the index file we generate contains the signature section accordingly
Note that for plugins, the index file could in the future also contain plugins that are not generated from this repository, so we may want to rely to those third-party trusted plugin authors to supply that signature and add it to this repo.

I can work on this
/assign


Using PHP 7 trying to find the hash of an image.

Notice: imagecolorat(): 5,0 is out of bounds in path\pHash.php on line 192

Sorry, just seeing this now. The picture was too small.


Docker behat Laravel issues.

On version 1.12.1 behat comand runs db migrate from laravel super slow. I had to downgrade to version 1.12.0 in order to be able to run it smoothly.
I'm running on OS El capitan 10.11.6 and Laravel 5.1.
It takes over 5 minutes to run a simple scenario due to the slow migrate. doing a
php artisan migrate
takes over 2 minutes. DB only has 44 tables.

@juanmrad This seems to be an issue with Docker for Mac. Can you open an issue on this repository instead: https://github.com/docker/for-mac/, please?
I'll close this issue now as it's not a Docker engine issue and it's mostly Docker for Mac related.


SDDM: Plasma Wayland session is started on the same TTY

Describe the bug
When SDDM launches a Plasma Wayland session, it is supposed to launch it on a separate TTY to avoid certain problems. https://github.com/sddm/sddm/issues/1409
However, this is not done (on my end, they are both on TTY 7).
One of the issues caused by this is, for example, if you change TTY during the Plasma Wayland session, when returning the desktop is unusable (it's completely black, with only the cursor being in a cross form. This should be the behavior when selecting the TTY where SDDM is, but since they are both and same TTY...). This doesn't happen when Plasma Wayland is launched via TTY (dbus-run-session startplasma-wayland).
I didn't test whether this issue happens only on SDDM specifically.
Steps To Reproduce
Steps to reproduce the behavior:

Enable SDDM and Plasma.
Launch Plasma Wayland from SDDM.
Both are on the same TTY.

Expected behavior
They should be on different TTYs.
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.18.9-zen1, NixOS, 22.11 (Raccoon), 22.11pre390234.2770cc0b1e8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.9.1`
 - channels(root): `"nixos"`
 - channels(user): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

For me they are both on tty2, but switching back and forth between ttys does not seem to cause any problems. Is this related to virtualization stuff?
❯ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.18.8, NixOS, 22.11 (Raccoon), 22.11pre389487.18b14a254dc`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.9.1`
 - channels(root): `"nixos"`
 - channels(user): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Seems fixed now. I can switch between users and TTYs with no problem.
Closing.


How to get id voice channel?

How to get id voice channel?

$guild   = $discord->guilds->first();
$channel = $guild->channels->get('name', 'YOUR CHANNEL NAME');

@duwayy PHP Fatal error:  Call to a member function first() on null in /root/discordbot/main.php on line 48

I'm running this code without errors
//at this point discord instance is already created
$discord->on('ready', function () use ($discord, $channel) {

		$guild   = $discord->guilds->first();
		$channel = $guild->channels->get('name', 'Music Channel');

@duwayy PHP Catchable fatal error:  Argument 1 passed to Discord\Discord::joinVoiceChannel() must be an instance of Discord\Parts\Channel\Channel, null given, called in /root/discordbot/main.php on line 58 and defined in /root/discordbot/vendor/team-reflex/discord-php/src/Discord/Discord.php on line 1032
58:  $discord->joinVoiceChannel($channel)->then(function (VoiceClient $vc) use ($channel) {
$сhannel corresponds to what you wrote earlier

You have a problem with your bot, it does not connect to vocal channel. Test this code to be sure a channel is retrieved before attempting to pass $channel
$discord->on('ready', function () use ($discord, $channel) {

		$guild   = $discord->guilds->first();
		$channel = $guild->channels->get('name', 'YOURCHANNELNAME');
		$discord->joinVoiceChannel($channel)->then(function (VoiceClient $vc) {
    echo "Joined voice channel.\r\n";

}, function ($e) {
    echo "There was an error joining the voice channel: {$e->getMessage()}\r\n";
});

Closing due to age.


[LOC] Invalid link in an article

There is an invalid link in an article.
Repro steps:

Go to https://docs.microsoft.com/en-us/sharepoint/administration/designing-a-sharepoint-server-2016-farm-in-azure
Search for "Licensing Microsoft server products for use in virtual environments"
Click on the link

Actual results:
Link redirects to a non existing page
Expected results:
Link should redirect to an existing page
GH article:
https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/blob/live/SharePoint/SharePointServer/administration/designing-a-sharepoint-server-2016-farm-in-azure.md

@OfficeGlobal  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@officedocsbot assign @scanum

@OfficeGlobal Thank you for your feedback. We have made changes on the doc via PR https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/pull/1043

@OfficeGlobal Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

@officedocsbot close


merge code from dw-common-spec release 1.1.5

client

Aliyun EMR reader: consolidate Aliyun EMR Studio workflow export command, support folder filter and export with flow path property
DolphinScheduler reader: add adatper for dolphinscheduler3.x open api export

spec

add Table spec
consolidate manual workflow and do-while/for-each node spec

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.聿剑 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Linting does not work if .slim-lint.yml or .rubocop.yml misses on project

Linting does not work if .slim-lint.yml or .rubocop.yml configs are misses on my project folder. I see slimlint(ok) in the bottom left corner of sublime text. As long as I have the config files even blank the linting starts working.
SublimeLinter-contrib-slim-lint v3.1.0
slim-lint 0.16.1
SublimeText v3.1.0
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin17]

The following are shown on console of sublime text on debug mode
SublimeLinter: #2595 linter.py:1263   Running ...

  /Users/apple/dev/ruby/acc  (working dir)
  $ /Users/apple/.rbenv/shims/ruby -S slim-lint --config /Users/apple/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/slim_lint-0.16.1/config/default.yml --config /Users/apple/dev/ruby/acc/.slim-lint.yml /var/folders/rf/5r993pkn4qz4pddtj6vgv8240000gn/T/tmptg2vhi.slim

SublimeLinter: #2595 linter.py:955    slimlint: output:
  Unable to load configuration from '/Users/apple/dev/ruby/acc/.slim-lint.yml': No such file or directory @ rb_sysopen - /Users/apple/dev/ruby/acc/.slim-lint.yml
SublimeLinter: #2595 linter.py:995    slimlint: No match for line: 'Unable to load configuration from '/Users/apple/dev/ruby/acc/.slim-lint.yml': No such file or directory @ rb_sysopen - /Users/apple/dev/ruby/acc/.slim-lint.yml'
SublimeLinter: sublime_linter.py:449  Linting '_aside.html.slim' took 1.81s

I’m sorry @Abduvakilov, I no longer use slim and don’t currently have the time to maintain this linter. Would you be willing to investigate and open a PR? This may be related to #6.
Thank you for reporting this issue!

I have seen the same issue in another linter. The author is suggesting workaround to create blank configuration file. I may try to look at the code when i have time


Sorting of signatures

Sort both list of signatures by commonly (Wanderer and in-game) aids cognition. It would be useful if the sigantures where sorted by ID by default and there were column headers that allowed changing the sort.
I'm an experienced software engineer, but have limited experience with Elixir/Phoenix. If you're willing to assume the burden of telling me what I'm doing wrong, I'm happy to work on this.

Signature list sorting can be implemented on ui widget (react.js) level actually, we have all signatures data here.

I see. I haven't looked at PrimeReact before. Nifty componant libriary. I will have a PR up that adds sortable columns to the DataTable.

Do you have any objections to the default sort being ID and not age?

You can add a property to set the default sorting, so we can decide it later.

Hi! That's cool, but my suggestion give ability to sort by dropdown menu in header of widget (yes that's dropdown will be very small) or add it in settings of signatures. Now functional of signatures not finished and I working on it now.

You can add a property to set the default sorting, so we can decide later.

Will so. Should the current sort be perisisted between sesions?

Hi! That's cool, but my suggestion give ability to sort by dropdown menu in header of widget (yes that's dropdown will be very small) or add it in settings of signatures. Now functional of signatures not finished and I working on it now.

I'm hearing that the the goal to keep the UI small to ensure many signatures are visiable. A dropdown on the right of the title bar makes sense too and saves about a row and half of signtuare space.  How would reverse be implemented in a dropdown? Additional entries?

Will so. Should the current sort be perisisted between sesions?

I guess so, better to keep user settings as we do for other user-related settings (using LocalStorage).


Replace the old CN with the new one.

What problem would you like to solve or improve?
It is necessary for us to use the new utility cn in order to have better control over the components.
Describe your proposed solution or enhancement.
Replace the current cn in every component
Describe any alternative solutions you've considered (optional).
No response
Additional context or information (optional).
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Done!


rxjs Observable and operators are imported individually

Angular 5 no longer allows importing of the whole Rxjs library.

Hi @paulyipkh, thx for your PR, how can I test your branch on my project?
Doing in package.json
"ng2-responsive": "git+https://github.com/paulyipkh/ng2-responsive.git",
does not work
I know this is an npm & packaging question.

I think you should use rxjs/operators/xxx instead of rxjs/add/operator/xxx right?

I am sorry that I am very new to github and don't know how to work with it.
I only changed the import section of config.ts
`
import { Injectable, Directive, Input, TemplateRef, ViewContainerRef, ElementRef, OnInit, OnDestroy, Optional } from '@angular/core'
import 'rxjs/add/operator/debounce'
import 'rxjs/add/operator/share'
import 'rxjs/add/operator/map'
import 'rxjs/add/operator/debounceTime'
import 'rxjs/add/operator/defaultIfEmpty'
import 'rxjs/add/operator/startWith'
import 'rxjs/add/observable/fromEvent'
import { Subscription } from 'rxjs/Rx'
import { Observable } from 'rxjs/Observable'
import { Observer } from 'rxjs/Observer'
import { ResponsiveWindow } from '../responsive-window/index'
import { GLOBAL_INPUTS, REG_TABLETS, REG_MOBILES, REG_SMARTS_TV, REG_BROWSERS, REG_SORT_NAMES, REG_GAME_DEVICES, REG_BOTS, REG_OS, WINDOWS_OS_VERSION, LINUX_OS } from './const'
import { responsiveSubscriptions } from './interfaces'
`

Actually, I edit the config.js directly.
The change to config.ts show only be
`
import 'rxjs/add/operator/share'
import 'rxjs/add/operator/debounce'
import 'rxjs/add/operator/map'
import 'rxjs/add/operator/debounceTime'
import 'rxjs/add/operator/defaultIfEmpty'
import 'rxjs/add/operator/startWith'
import 'rxjs/add/observable/fromEvent'
import { Subscription } from 'rxjs/Subscription'
import { Observable } from 'rxjs/Observable'
import { Observer } from 'rxjs/Observer'
`

So you can not provide a working version? I'm noz sure if @ManuCutillas is reading this an providinf an ng5 version

When I figure out how to work with github, I will make the repository npm installable.
At the moment, I can only work with manually edited config.ts and compile it with tsc on my local machine.

@paulyipkh okay you compile it locally and install it on project from locally?
Can you explain better what do you intend with tsc? How do you compile with tsc? Do you intend ngc? Or what?

I'm going to do the merge and an optimization for Angular 5. Thank you very much everyone.

@ManuCutillas use the new literal operators instead of rxjs/add/operator to have a smaller bundle.
If you like I can do a PR for that

@mburger81 perfect, make the changes that you think are most appropriate and do the PR.
: )

One question for that,  how can I test your lib on an existing locally project. Jo don't have anything in package.json and I was not able to get work with packager. Can you help on it?

Right now I do not have any public project to leave you to test the library with a battery of unit tests. Maybe it's a good idea to work on this before refactoring the library. To make it easier to add improvements for all those who want to contribute to the library.

Ok, you can add the library directly in the package.json as "ngx-responsive": "https://github.com/ManuCutillas/ngx-responsive#master" with the URL of your fork. ; )

Are you sure? I think this is not working, I already tested it before and I tested it again. It is not working.
I can not use directly your master branch, there is no distribution folder in there.

@ManuCutillas I think also installing it from npm does not work!
If we do npm i ngx-responsive --save we got a file struture in this way

But if we do npm i ng2-responsive --save it is

So the first one is only source code and the second one is the compiled one with the right index file

I created a new PR #97 to handle this


AUD/USD Currency on getClients()

Having a few issues with clients who are set to non-USD currencies.
Nothing is returned when the client is set to AUD, but it returns the results fine when clients are set to USD.
Any tips or tricks around this?
Thanks!

See issue #41. Currently we use string comparison on description to deserialize enums. Harvest seems to like to change the descriptions of the currency values.
Can you send me a sample response with AUD to confirm this is the issue?

Thanks for that! Here's an example of the data returned via Postman.
Anytime any client is stored in AUD, it will cause the wrapper to return a null object on getClients().
[   {     "client": {       "id": XXXXXXXX,       "name": "Test Client",       "active": true,       "currency": "United States Dollar - USD",       "highrise_id": null,       "updated_at": "2016-12-07T11:19:38Z",       "created_at": "2016-12-07T10:45:29Z",       "statement_key": "3c8d77c01213935b8b66579e9fe31fce",       "default_invoice_kind": null,       "default_invoice_timeframe": null,       "address": "",       "cache_version":<PHONE_NUMBER>,       "currency_symbol": "$",       "details": "",       "last_invoice_kind": null     }   },   {     "client": {       "id": XXXXXXXX,       "name": "Test Client 2",       "active": true,       "currency": "Euro - EUR",       "highrise_id": null,       "updated_at": "2016-12-07T11:30:52Z",       "created_at": "2016-12-07T11:30:52Z",       "statement_key": "0e89949a5f3a8ff8ce04fc4fe35450a8",       "default_invoice_kind": null,       "default_invoice_timeframe": null,       "address": null,       "cache_version":<PHONE_NUMBER>,       "currency_symbol": "€",       "details": null,       "last_invoice_kind": null     }   },   {     "client": {       "id": XXXXXXXX,       "name": "Test Client 3",       "active": true,       "currency": "Australian Dollar - AUD",       "highrise_id": null,       "updated_at": "2016-12-07T22:18:01Z",       "created_at": "2016-12-07T11:32:46Z",       "statement_key": "b6c64fb061d967d6055da58c9ee8e266",       "default_invoice_kind": null,       "default_invoice_timeframe": null,       "address": "",       "cache_version":<PHONE_NUMBER>,       "currency_symbol": "$",       "details": "",       "last_invoice_kind": null     }   } ]

Looks like they've changed it from Australia Dollar - AUD to Australian Dollar - AUD

I've committed a fix for #41. I'll release a new build in a few minutes.


Add support for django 3.2

This updates Oscar's requirements to support Django 3.2 and fixes a test failure that appears related to this change to the Cookie storage hash format by using the new in 3.2 Signer.unsign_object() method to retrieve the human-readable message for the test assertion.

@solarissmoke no prob, I should have the capacity to address the deprecation warnings in the next week or so if that works for your release timeline.

@robalford that would be great, thank you.

@robalford I've incorporated your commits into #3704, where I've worked on the deprecation issues (we'd like to get a release out soon). Thanks for your help!


Use prometheus-operator mixin

As in title.
Blocked by https://github.com/prometheus-operator/prometheus-operator/pull/3506

Blocked by https://github.com/prometheus-operator/prometheus-operator/pull/3515

This is finished and ready for review. I have no idea why there are two checks for Travis CI, but CI passes.
@prometheus-operator/kube-prometheus-reviewers

lgtm


Add rust ci actions

Current dependencies on/for this PR:

nick/crates

PR #6   👈

This comment was auto-generated by Graphite.