Can't start Free image

I've pulled the free lite image, but it fails to start:
docker run --platform linux/amd64 container-registry.oracle.com/database/free:<IP_ADDRESS>-lite
Expanding oracle data
/home/oracle
Starting Oracle Net Listener.
Oracle Net Listener started.
Starting Oracle Database instance FREE.
Oracle Database instance FREE started.
Pluggable Database FREEPDB1 opened.

#####################################
########### E R R O R ###############
DATABASE SETUP WAS NOT SUCCESSFUL!
Please check output for further info!
########### E R R O R ###############
#####################################
The following output is now a tail of the alert.log:
  pga_aggregate_target     = 512M
  diagnostic_dest          = "/opt/oracle"
  enable_pluggable_database= TRUE
2024-07-31T15:51:47.237830+00:00
Oracle instance running with ODM in SGA: Oracle File Server ODM Library, Version: 1.0
Oracle instance running with ODM in SGA: FSDirect ODM Library Version 1.0
Broadcast on commit is enabled and is using Message mode.
--ATTENTION--
USER (ospid: 429): terminating the instance due to ORA error 442
Instance terminated by USER, PID = 429

ORA error 442 seems to suggest that more than one instance was started: https://docs.oracle.com/en/error-help/db/ora-00442/?r=23ai
What's going on?

What machine are you running the container on?
Could you share the /proc/cpuinfo file output

I'm on an M1 Mac. I've read that there's issues running the x86_64 image via Docker. I'm currently in the process of trying this blog post which suggests a different container runtime (Colima), which may solve the issue.
I'm not totally clear on why Docker Desktop can't run the container, it should be using Rosetta to run the container runtime and the container itself. This is also the first Docker image that I've had any issues running.

The Oracle Free images are currently not supported on Apple silicon.
You can use the 19.19 Enterprise ARM image on Mac M1:
container-registry.oracle.com/database/enterprise:<IP_ADDRESS>

I ended up installing Colima to get the free image to work. I'm still surprised it doesn't work with Docker Desktop (I thought the point of the container runtime was that it was a VM, so the host OS shouldn't matter, but it's working for me now so I'm happy to close this ticket off.


Feature: AST transformers

Ported from Kolasu, not yet as well-tested as in Kolasu (we're missing some infrastructure)

This is now good to go I think, I've ported all the necessary stuff from Kolasu.

+1


Async query example

Would be nice to have an example of an async query that takes some time to complete, and potentially have a built in spinner that's override-able.

Yeah I had a spinner originally, but changed it so the dropdown just doesn't open if it hasn't finished loading. Seemed simpler that way.
Side thought: The component only calls the getData prop once, when the input mounts. Should it be called every time the dropdown opens?

Yes we should definitely provide that option, for our use-case we make one fetch to gather all the field types and want to offer autocomplete functionality on the fly for each field as well. So if you're typing level we should be able to hit an autocomplete endpoint and get info, error etc. back as results.

Ah, we may have had a misunderstanding there. Does it not all come down at once following this format? I had thought all the enumerations would be included in the response of the initial request.
I can adjust the code to make async requests for the enums. In that case, would definitely need a spinner.

Ah yep, cool. We may have some options preloaded (that basics like level, request types, etc), but will need to make async requests to autocomplete, ideally we could show the options that are preloaded but append results as they come in.

So just to clarify what @binarylogic mentioned in slack while discussing this (https://timberio.slack.com/archives/G8ZSUPCV6/p1517621696000039):

You’ll get a complete schema to work with. It will include all of the fields names, types, and enumerations. We can also include short descriptions, etc. Sorry we didn’t flesh that out better. Basically it will have name, type, enumerations (array, can be empty or null) for every field.

That all still holds true, but enumerations might be a partial list?

I believe he intended to offer the autocomplete API eventually, not an immediate need but will let him jump in.

If that's the case, it might be helpful to differentiate between partial enum lists and full enum lists to avoid unnecessary API calls.

What's the advantage to that as opposed to just appending the autocomplete results to existing enums?

Hm, I suppose just avoiding unnecessary API calls. Really depends on what will come back from the autocomplete API, whether it includes the original preloaded suggestions, is diffed, etc. I would say we only include the enumerations array in the initial request if it's a full list, otherwise we query the autocomplete API.


Switch to embedded PackageIcon

Part of aspnet/AspNetCore-Internal#3146
Local build passes the smell test with these changes.

With the last change, this now includes the icon metadata in all .nuspec's, including the manually generated ones - @dougbu PTAL

Please retarget this change to 'release/3.0'. We'll need to do something a bit different in 2.x.

Closing in favor of https://github.com/aspnet/AspNetCore-Tooling/pull/1166


Switching language make menu labels disappear

Steps to reproduce :

load onyxia
switch language (bottom dropdown menu)

left menu labels will disappear and the UI will slowly resize
Screenshot :

Ok that makes sence to me.
I did a hack to prevent the previous bug that I couldn't reproduce.
I was expecting this bug to occur.
Thanks for reporting

Thank you for reporting


Ability to set custom  width and height for better quality

Hi,
Great component by the way!
Are you able to implement props that will allow custom width/height for the canvas?
We are losing some quality appearance with just the client viewport dimensions being passed.
Thank you.

Hi @AVargas89,
Thank you, I will try to look into it later today or tomorrow.

It seems to me that the loss of quality is caused by the scaling of the viewport, so setting a custom canvas width/height doesn't help. Currently, the canvas element inherits the size of its parent, and I find this approach more flexible than setting a specific canvas size with the props. You can set the size of the wrapper as follows, and vue-pdf-embed will adjust to fit:
<div :style="{ width: '320px' }">
  <vue-pdf-embed />
</div>

I see your point about the loss of quality and will prepare a release with a fix, however I wouldn't add width/height props.

Thank you! This solution worked for now :)

Anytime! New ideas and issues are welcome.
By the way, the quality loss fix has been released in 1.0.2


feat: iam-group-with-policies output group_arn

Description
Add group_arn to the outputs of the iam-group-with-policies module.
Motivation and Context
I was missing this feature for a personal project, where I am using the iam-assumable-roles module and want to refer to a group by its ARN.
Breaking Changes
No breaking changes, just adding a new output.
How Has This Been Tested?
I have tested this change on my aforementioned project. The output is there and I can refer to it in other resources.

v4.6.0 has been just released.


README fixes: badge, minor wording tweaks

Pretty tiny updates to the README.

@jamonholmgren @Titozzz While the failure of the "publish" CI job doesn't matter for this particular PR, it seems like something that will need to be fixed before any new version can be released...?
Error is "Invalid GitHub token."

I updated the GH_TOKEN "personal access token" to one of the new "fine-grained personal access tokens". Seeing if that is working now.

https://github.com/settings/personal-access-tokens/new
Note I needed to allow this within the react-native-webview organization, as it's not available by default.

So, that didn't work.
[2:10:27 AM] [semantic-release] › ✖  The command "git push --dry-run<EMAIL_ADDRESS>HEAD:master" failed with the error message remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/react-native-webview/react-native-webview.git/'

I can't add a classic "personal access token" for my own account as it has access to sensitive repos. It appears this fine-grained PAT isn't working properly. Ideas, @Titozzz ?

Hm. I see that the error you quoted was there in the original failure too, I just didn't think it was as significant as the "invalid token" error.
It looks like your change did resolve the invalid token error at least, so.... progress??? (unless that one was a red herring?)
I wonder if upgrading semantic-release might help....? ¯\_(ツ)_/¯

Nothing to worry about, I just used an expiring token following the new security recommandations. I'll update it before the next release. Hopefully soon, I did a new RC yesterday for new arch. If all good I'll prod

@Titozzz TY!


Cleanup the handling of single- and multi-platform lowering in ModuleContext

Previously, we introduced support for multi-platform lowering, by adding a new LoweringParameters object that can be used to specify a cross-lowering platform or even multiple platforms. But we had kept the ModuleContext.platform in place because some lowering rules were still referencing it. Now we replace ModuleContext.platform with ModuleContext.platforms, which removes the redundancy, simplifies the code, and makes it cleaer that the lowering rules should not simply assume single-platform lowering.
We still keep a property ModuleContext.platform, which throws an error when used while doing multi-platform lowering. We plan to remove this property once we clean uses in libraries.

Closing in favor of internal CL.


Proxy Service based on incoming port

I'm trying to define services for the same domain/path, using multiple frontend/backend ports. So service,domain/path,port 80 and then either the same or a different service,domain/path,port 443. Currently the first one wins and the second is ignored. Can the acl's be made to include matching the dest_port to the service port? Here is the flow from client to AWS ELB, to DF-P to service:
outside -> [443 ELB -> 443 DF-P -> 443 Service] AND
outside -> [80 ELB -> 80 DF-P -> 80 Service]
for the same domain/path
This way I can terminate SSL on ELB and keep cert out of HAProxy, but the service still knows the original port the request was sent on.

This feature is already developed (even though I forgot that it exists). You can use the srcPort with an index. You can see an example in https://proxy.dockerflow.com/swarm-mode-auto/#using-tcp-request-mode . Even though the example uses tcp, the same applies to http as well.
Can you please let me know if that's what you were looking for?

Here is what I've tried:

com.df.port.1=80
com.df.srcPort.1=80
com.df.port.2=443
com.df.srcPort.2=443

Also, just

com.df.srcPort.1=80
com.df.srcPort.2=443

and just:

com.df.port.1=80
com.df.port.2=443

In all cases, the proxy log repeats
2017/02/17 13:54:03 Processing request /v1/docker-flow-proxy/reconfigure?distribute=true&port.1=80&port.2=443&serviceDomain=...
for 4 mins and then stops, having not updated the config at all.
What I was able to do is define a service using

com.df.port=80
com.df.srcPort=80
and then a second service (using the same container) with
com.df.port=443
com.df.srcPort=443

and this will accomplish what I need, same container logic processing 2 different ports (across 2 different services though). I was wondering if this is what you had intended? Not suer I get how the port indexing is supposed to work.
P.S.
I don't mind so much doing this, as I might need to config this way to work around another problem: on ELB's I can support sticky session cookies to enforce using the same EC2 instance(service), where docker network mesh does not support sticky sessions. So this config allows me to run any service/port combination that can't be load-balanced as a separate service with a single replica, while running the same service on another port that can have multiple replicas.
Now I've seen some talk of having HAProxy provide the sticky session part. Any thoughts on that with DF-P?

The idea behind indexing is to treat a single service as if there are multiple services or endpoints. They can provide a similar result as what you did with two services that use the same image.
The most likely problem with your attempt to use indexes is that you missed servicePath. Labels should be something like:
com.df.srcPort.1=80
com.df.srcPort.1=80
com.df.servicePath.1=/something
com.df.srcPort.2=443
com.df.srcPort.2=443
com.df.servicePath.2=/something

Can you please try it out with servicePath indexed as well? If that didn't work, please post logs from swarm-listener. There should be the response from the proxy that will, hopefully, give us a clue why it rejected reconfigure requests.

Perfect! Adding servicePath.1 and .2 did the trick (with srcPort and port   .1 and .2)


make dotnet build pass on non-Windows

dotnet build will now work

now yes 😀

Could we also enable the tests in the build script so that it runs for all platforms?
https://github.com/filipw/dotnet-script/blob/3240ee1cc20c603610d3ba4e7b61de54174f8ebe/build/Build.csx#L79


Can't send mail from GMail-based accounts

I can't send mail from any GMail/Google Apps accounts. It seems like there is a known issue in the emailjs module that hasn't made it into a release yet.
Original issue: https://github.com/eleith/emailjs/issues/77
Pull request fixing the issue: https://github.com/eleith/emailjs/pull/76

I am using emailjs v0.3.16. I fixed by turning on "Allow less secure apps" in my google account settings. All works! Although I was using emailjs for some token based authentication.

You do not need to "Allow less secure apps".  IMHO, it is not a good idea to do so.
You can get it working by generating and using an app specific code instead.
I just checked the page to generate the code.

To use the Gmail service to send emails we must first add security in: My account> Account preferences > Sign-in & security > Signing in to Google > 2-Step Verification > Getting Started > Fill out the form and confirm > Activate
Generate a password for apps, go to My account> Sign-in & security > Signing in to Google > App passwords> Select App > Select device (Other) > Generate.
Use the app password to send mail, if you want after generate the password you can deactivate your 2-Step verification.


Update OpenCollective readme section

The current backer/sponsor links seem outdated to what is actually shown on the site.
Relates to #13122
For example on the individuals part, someone called "Scott Ferreira" shows up in third place with ~1000$ who previously didn't show up at all. You can view the updated readme here: https://github.com/Earlopain/rubocop/tree/readme-sponsors?tab=readme-ov-file#open-collective-for-individuals
Overall it seems to mirror exactly what OpenSearch is showing:
Website:

Readme current:

Readme next:

Before submitting the PR make sure the following are checked:

[ ] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[ ] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[ ] Feature branch is up-to-date with master (if not - rebase it).
[ ] Squashed related commits together.
[ ] Added tests.
[ ] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[ ] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Seems OC changed the format of the backer links at some point and we didn't notice it. Thanks for tackling this!


[package] Update winget templates

Winget templates require a few tweaks in order to publish packages successfully to microsoft/winget-pkgs

🎉 This issue has been resolved in v1.16.0 (Release Notes)


[2.0] Add coroutines versions of execute and setOnEach

This PR adds all of the coroutine equivalents for execute:

suspend () -> T
Deferred
Flow
And a new API:
Flow.setOnEach which is like onEach + setState + launchIn(viewModelScope)

cc @denis-bezrukov

@BenSchwab I chose Main.immediate because that tends to be the default for Jetpack scopes and has become the expectation for a default dispatcher on Android. However, your point is valid. It can be aided by https://github.com/airbnb/MvRx/issues/389 though.
I'm going to merge this but opened https://github.com/airbnb/MvRx/issues/404 to continue the discussion


chore(Pages): update “index”

Automatically generated by Netlify CMS

👷 Deploy Preview for happygobd-e76566 processing.

Name
Link

🔨 Latest commit
6b2168bbaa56e693950c6be44f22465fb4a5e772

🔍 Latest deploy log
https://app.netlify.com/sites/happygobd-e76566/deploys/62f242d7ef293c000982844c


CFP: Dynamic ConfigMap

Cilium Feature Proposal
This proposal presents a method for dynamically updating internal Cilium agent configurations from a ConfigMap without needing agent restarts. The agent will monitor the designated ConfigMap and automatically synchronize any changes with its in-memory database, stateDB. The new ConfigMap will be generated by the operator, which will observe the existing static ConfigMap (cilium-config) and other relevant CRDs.
CFP: Dynamic ConfigMap

I would appreciate your feedback :)
/cc @joamaki @bimmlerd @joestringer

@ovidiutirla once you think it is ready, can you also add this CFP as a PR to the design-cfp repo? https://github.com/cilium/design-cfps


single-spa-angular-cli not supporting Angular6+

I am using single-spa-angular-cli v0.4.1 and its perfectly supporting Angular V5. But not supporting Angular v6 or v7.
package.json of angular v5 app.
{ "name": "app3", "version": "0.0.0", "license": "MIT", "scripts": { "ng": "ng", "start": "ng serve", "build": "ng build --prod", "test": "ng test", "lint": "ng lint", "e2e": "ng e2e" }, "private": true, "dependencies": { "@angular/animations": "^5.2.7", "@angular/cdk": "^5.2.3", "@angular/common": "^5.2.9", "@angular/compiler": "^5.2.9", "@angular/core": "^5.2.9", "@angular/forms": "^5.2.9", "@angular/http": "^5.2.9", "@angular/material": "^5.2.3", "@angular/platform-browser": "^5.2.9", "@angular/platform-browser-dynamic": "^5.2.9", "@angular/router": "^5.2.9", "core-js": "^2.4.1", "rxjs": "^5.5.2", "zone.js": "^0.8.14" }, "devDependencies": { "@angular-devkit/core": "^0.4.3", "@angular/cli": "1.6.3", "@angular/compiler-cli": "^5.2.9", "@angular/language-service": "^5.2.9", "@types/jasmine": "~2.5.53", "@types/jasminewd2": "~2.0.2", "@types/node": "~6.0.60", "codelyzer": "^4.0.1", "jasmine-core": "~2.6.2", "jasmine-spec-reporter": "~4.1.0", "karma": "~1.7.0", "karma-chrome-launcher": "~2.1.1", "karma-cli": "~1.0.1", "karma-coverage-istanbul-reporter": "^1.2.1", "karma-jasmine": "~1.1.0", "karma-jasmine-html-reporter": "^0.2.2", "protractor": "~5.1.2", "ts-node": "~3.2.0", "tslint": "~5.7.0", "typescript": "^2.6.2" } }
package.json of angular v7 app.
{ "name": "app2", "version": "0.0.0", "scripts": { "ng": "ng", "start": "ng serve", "build": "ng build", "test": "ng test", "lint": "ng lint", "e2e": "ng e2e" }, "private": true, "dependencies": { "@angular/animations": "~7.0.0", "@angular/common": "~7.0.0", "@angular/compiler": "~7.0.0", "@angular/core": "~7.0.0", "@angular/forms": "~7.0.0", "@angular/http": "~7.0.0", "@angular/platform-browser": "~7.0.0", "@angular/platform-browser-dynamic": "~7.0.0", "@angular/router": "~7.0.0", "core-js": "^2.5.4", "rxjs": "~6.3.3", "zone.js": "~0.8.26" }, "devDependencies": { "@angular-devkit/build-angular": "~0.10.0", "@angular/cli": "~7.0.2", "@angular/compiler-cli": "~7.0.0", "@angular/language-service": "~7.0.0", "@types/node": "~8.9.4", "@types/jasmine": "~2.8.8", "@types/jasminewd2": "~2.0.3", "codelyzer": "~4.5.0", "jasmine-core": "~2.99.1", "jasmine-spec-reporter": "~4.2.1", "karma": "~3.0.0", "karma-chrome-launcher": "~2.2.0", "karma-coverage-istanbul-reporter": "~2.0.1", "karma-jasmine": "~1.1.2", "karma-jasmine-html-reporter": "^0.2.2", "protractor": "~5.4.0", "ts-node": "~7.0.0", "tslint": "~5.11.0", "typescript": "~3.1.1" } }
Please help me,
Thanks, advance.

Any update on this?

I am following upon this too. If someone here let us know how long is it gonna take before releasing a single-spa version that supports Angular 6 applications.

Any idea of how this is likely to take to support?

I believe v2.1 of single-spa-angular supports up to angular 7 already. I'm not sure about the CLI support, but according to Joel on the single-spa slack channel, he is working on that as well. It seems like the goal is to have angular and angular cli support in one library. You guys might want to follow up with Joel for more info. There's also an issue here: https://github.com/CanopyTax/single-spa-angular/issues/14

+1 for this. I am also looking to upgrade to 7 support


Avoid sharing Java packages between API and implementation libraries.

Using different packages for implementation classes will make it easier to avoid accessing non-public elements in the API library and help maintain backwards compatibility.

#483 moved all tags implementation classes into the package io.opencensus.impl.tags to separate them from the API.  Do you think there is any advantage to also separating the classes from the three implementation libraries, so that we have something like this?
opencensus-api:       io.opencensus.tags
opencensus-impl-core: io.opencensus.core.tags
opencensus-impl:      io.opencensus.impl.tags
opencensus-impl-lite: io.opencensus.impl.tags

or
opencensus-api:       io.opencensus.tags
opencensus-impl-core: io.opencensus.implcore.tags
opencensus-impl:      io.opencensus.impl.tags
opencensus-impl-lite: io.opencensus.impllite.tags

/cc @bogdandrutu

I don't think that is needed (separation between packages, the implementation packages are not intended to be shared with other non-internal implementations).

My second suggestion was related to https://github.com/census-instrumentation/opencensus-java/pull/343#discussion_r120812070.


Fix command line flag

Can one of the admins verify this patch?

@suryagaddipati We need a CLA to be signed: http://noms.io/ca_individual.html before we can accept your patch. Thanks for the help!

signed!

thanks again!


3rd Party Event Websites Promotion for cdCON 2021

[x] Research publications w/event calendars | Roxanne | Deadline: Dec. 11, 2021
[x] Reach out & confirm event calendar placements | Roxanne | Deadline: Jan. 10, 2021

Created list and reached out: https://docs.google.com/document/d/1kmG_2ss4J-ytE3KUjosA1LSzmtBt_KqPAQsfEEzg6Lg/edit#

Created list and reached out: https://docs.google.com/document/d/1kmG_2ss4J-ytE3KUjosA1LSzmtBt_KqPAQsfEEzg6Lg/edit#

great! ty, I've added this to the cdcon notes & also for the feb. 3rd mtg agenda to review.

great! ty, I've added this to the cdcon notes & also for the feb. 3rd mtg agenda to review.


candy crush game

I want to design a basic candy crush game .
The Tech stacks I use are  HTML, CSS, and JS.
Please assign me this issue.
Thankyou.

@harshithatnbr Sure. Go ahead

@harshithatnbr any update?

Sir I will update you by tomorrow.


add snark worker docs

Confirm that relative paths to images work before merging!

The images/paths are all good, just need to check the copy


Attaching to language server no longer shows output

Clone this branch of vscode extension samples
Open lsp-sample
npm i && npm run build
Run the compound Client + Server config, open a *.txt file
:bug: Notice the console.log statements in this commit neither show up in the host window's Output -> Language Server Example, nor in the Debug Console of the development window. It should print test on both initialization and completion.

I confirm that console.log messages are not shown. It pauses if I set a breakpoint, but nothing is shown in the server debug console.

ping @weinand

In can be easily verified with the lsp example: https://github.com/Microsoft/vscode-extension-samples/tree/master/lsp-sample

@roblourens @isidorn
I can reproduce this with the simple hello world extension:

console.log messages no longer appear in the debug console
I see an object "ApplicationInsights:CorrelationIdManager" instead:

Yes I see the same.
The issue is that I am not getting the Output event from the node debug extension neither I am getting the extension log from the broadcast service vscode:extensionLog. Forwarding to @roblourens
@roblourens if you are unaware of any changes in this area then we should bisect to find what change caused this regression
fyi @bpasero for broadcast service

Since console.log works for simple node.js programs (non-EH-debugging), I suspect the issue is with the broadcast service.

I cannot reproduce, for me it works:

I haven't tried it yet but I assume you guys have selected the correct debug console? Looks like this is about logs from the server and I think the broadcast service is only for EH not an LSP server.

I tested this:

yo code
typescript extension
run it

Normal EH logging works fine for me, I can repro the issue with logs from the language server. That's weird, I don't get events from node. Reproes with chrome devtools too. I'll look into it.

Probably it depends on which vscode version you are using, because updating the deps did the trick for me: https://github.com/Microsoft/vscode-extension-samples/pull/166
I still don't see any logging in the server debug console, but at least I can see it in the client output.

That still doesn't fix it for me. I'm very confused tbh. I don't see anywhere that are are intercepting console logging. Debugging into the console.log call, it seems to do the normal thing. I don't know how it gets lost.

It looks like the client wants to get stdout/err from the server, I guess to pipe logs through to the client. But it seems to not work? And we should still get logs through the debug protocol, and I don't. https://github.com/Microsoft/vscode-languageserver-node/blame/master/client/src/main.ts#L379
@dbaeumer do you know anything about this?

FYI the old sample has code similar to this in the server entry point:
import { createConnection, InitializeParams, InitializeResult } from 'vscode-languageserver';

const connection = process.argv.length <= 2 ? createConnection(process.stdin, process.stdout) : createConnection();

console.log = connection.console.log.bind(connection.console);
console.error = connection.console.error.bind(connection.console);

Where is that? I don't see it in the version that I have cloned.

@octref Did you write this. I am pretty sure I never added such code
import { createConnection, InitializeParams, InitializeResult } from 'vscode-languageserver';

const connection = process.argv.length <= 2 ? createConnection(process.stdin, process.stdout) : createConnection();

console.log = connection.console.log.bind(connection.console);
console.error = connection.console.error.bind(connection.console);

The stdout from the language server is written to the server's output channel here https://github.com/Microsoft/vscode-languageserver-node/blob/master/client/src/main.ts#L385. This has always been the case. I haven't changed this code in a long time. So I am confused that the output every made it to the debug panel.

Oh that's because I forked Vetur from html server, the original code belongs to @aeschli: https://github.com/Microsoft/vscode/commit/cb5a6e77db41283e8dc6bc8ab5c75c439d04320d#diff-953fd93988b92567bdca7e583d0c7373R20.

OK for people who want this to continue work as it was, add this to server entry point:
console.log = connection.console.log.bind(connection.console);
console.error = connection.console.error.bind(connection.console);


Connection refused: Not authorized

Hey! Just cloned the repo and pointed the server url to the remote staging api (//my.farmbot.io). I created an account and was logged in to the dashboard. I keep getting a react dev tools popup saying Connection refused: Not authorized. Any idea what is going on?

Eamon,
Thanks for the heads up! Your next step would be to Flash an Arduino with the latest stable firmware and hook it up to a machine running the latest stable RPi software. You'll need to run setup.rb on the Pi also (or just run it off your desktop for testing purposes). Did you get that far yet? My guess is that it's not connecting to MQTT properly because no device is configured.
Sorry for the vagueness on the setup process- we will be revamping the onboarding setup soon!
Does that help? Please let me know if you have any more issues and I can re-open accordingly.


MAINT: Use sphinx-gallery to generate examples and movies

Closing, this was due to GIF used to showcase the legacy viewer or other CLI prompts.
Those GIF don't exist anymore and sphinx-gallery is used to build the tutorials and examples gallery.


[Doc] Add troubeshooting of storagenetwork

Is your doc request related to a problem? Please describe or add related issue ID.
Users do not have feasible solution to troubleshoot the storagenetwork connectivity issue.
Describe the solution you'd like

Add a troubleshooting.

Document is updated.


[COMPAT] Beans Backpacks

I see you added compat for my mod and I just broke it in my latest update :) I was looking through your code and I wanted to clear some stuff up so our mods actually work together instead of having headaches and issues.

You've could've called the method backData.drop() to package up the backpack and place it where the player is stood, this still would've thrown Pot items onto the ground though.
You used the method backData.update(ItemStack.EMPTY) to cleat the back slot when you should've used backData.set(ItemStack.EMPTY). Update sets the item in the backslot and updates the info for the back renderer but Set updates curios/trinkets as well.

I was thinking separating the method drop() so that one part you can specify the direction x y z and it returns any ItemStacks it wants to drop onto the ground so you can collect them in your grave. Heres the new method to call the new drop() I put it away from the acutal class so incase of any future refactors since this time compat broke due to a refactor.
LMK if you have any more ideas or need anything else before I post this version.

I was unsure if you were forced to collect the backpack inventory because you didn't know how to properly place the backpack. I get now you want to store the backpack inside your grave no matter how beautiful my entities look.
The backData.drop() method clears the player's back data and tries to put what is can inside a backpack. If a player is wearing an elytra then it throws it onto the ground and if they're wearing a Decorated Pot it drops the inventory + the pot onto the ground as items.

Equipping Backpacks

The code that equips a backpack is wrapped inside this else statement. All you'd need is the backpack item, the inventory of it and the player it's going to.

Placing Backpacks

EntityAbstract.create() processes the item stack and location info into a backpack. It asks for a player entity just to reward the player with an advancement but otherwise I could replace it with a Level and UUID.

If those methods could help I'd want to write a special compat method since I'm constally moving my classes since this mod's my intro to modding and I keep finding stuff that could be re-written. To check if a player is wearing a backpack use backData.getStack(). That automatically checks Curios/Trinkets.

I also forgot to mention but I have 3 classes BackData BackSlot & InSlot. BackData hold all the info for everything in the mod while BackSlot is only the slot that appears in the inventory. With Curios/Trinkets installed the BackSlot never gets used and it's replaced with the InSlot which is tied to the last item inserted to the backpack. I saw you were using BackSlot instead of BackData in some cases and that could be another cause for C/T breaking

Yeah I almost felt bad for putting the backpack in the grave, instead of placing it. It does look very good!
But from what I gather I should use backData more and backSlot less.
I think I got the "equip" and "get" backpack functionality correctly, as it seems to work. It's implemented here (get) and here (equip).
Being able to place backpacks without a player reference would in my case make it possible to drop the backpack in its entity form when the grave module is either disabled, or instructed to drop the backpack in the world. But if that doesn't make sense within your mod you shouldn't have to do that. It technically works just dropping all the items on the ground normally.
If you did change it though, you wouldn't necessarily have to replace something. You could just overload the function with new variables and call one of them from the other.
Oh also I encountered log spam when hovering over the ender backpack in my inventory. It happened both this and last version, however I have only confirmed it happening outside my dev env last version (or at least some previous version, I haven't kept track of how many updates you've released since my initial compat). You might already know of it just thought I'd mention it since I did see it on 2 different versions.
But yes anyway I really appreciate you taking the time to try to improve the compatibility! Let me know if there's anything else you want me to do!

I can understand that you'd want to store the backpack since they could be destroyed in lava. I'll likely get an update out tomorrow with these changes and I'll let you know here when it's live.
As for the log spam it's likely that the the ender backpack didn't have it's key registered. A lot of it's code is placed onto of the rest of the backpack code when I should've just rewrote most of it so that it worked together. Instead I just have a lot of checks to see if it's a Ender Backpack. I'll check it out again.

20.1-0.17-v2 is live. I put all the helper methods inside of CompatHelper, hopefully this ends the generational war between inventory expansion mods and grave mods :)

Awesome! Thank you for going the extra mile with the compat class! I'm just waiting on more info regarding an issue with my graves, and then I'll update as well. In my opinion there's not really a war between inventory expansion mods and grave mods. I mean in my case, I like inventory expansion mods. I just don't know about all of them, and people only report (sometimes) when a crash happens.
But do let me know if you end up moving stuff around or changing something! Didn't find a "add to backpack" method, so I used the same as I did before, but other than that I'm now only using the CompatHelper static functions to handle the data. I'm open to changing stuff if you think it would make more sense in your mod!

I just meant a war because I see a lot of issues with other backpack mods and I get a lot of issues with grave mods so I assume we're not the only ones.
As for an add to backpack, do you need a method to add items? Using the createBackpackEntity() you can specify its inventory using the NonNullList<ItemStacks> stacks param (I think it would be a DefaultedList<ItemStack> in fabric) but I can add a method if you need to add items later than its creation.
Thanks for helping out though, like I said I've been getting reports for bugs with grave mods and I figured if its a reoccurring thing it must be something with my mod so I appreciate your help 😎 👍 👍 I'm pretty new to modding so if any of my implementation is unconventional I'd understand any criticism and I'm open to other ideas

I mean adding items to the backpack in the player inventory. And you don't have to implement that if you don't want to. I just noticed that you had a getter and setter for the backpack itself, but only a getter from the backpack contents.
When a mod is incompatible with a grave mod, the grave mod usually has to implement compatibility with the other mod, but if it has a strong enough API (like most popular ones do), the inventory expanding mod can implement compat too. I'm not aware of any inventory expansion mod that does this though. I'm usually the one implementing all compatibility between mods for YiGD (at least when it comes to inventory management).

The getBackpackInventory() getter is the actual item list so doing .clear() if they don't have a backpack and .addAll(itemStacks) would work. I was assuming you'd drop the backpack onto the ground if they already had one equipped but I can add a method to merge items into the backpack if thats what you're looking for. You'll have to do something with the items if the backpack fills up though.
FYI my item list isn't a fixed length like most containers in minecraft so make sure you don't try to get or place something out of it's index

My bad, I thought getBackpackInventory() created a copy for some reason lol.
Moving to setting the contents of the backpack that way I can no longer get the overflow back like I could with insertSilent(), but I'll insert into the same backpack the items was in originally, so it shouldn't ever overflow anyway.
Also the backpack is only dropped if the grave should drop all of its contents when claimed, or if the backpack should specifically drop on death (for example if graves are disabled).
Thanks for clearing that up though!

Ok so I know I mentioned like 2 weeks ago I would update soon, but I had exams that required my focus. Now they are done and I should be able to get an update out within a few days though (probably tomorrow if all goes to plan).
I did notice however when updating to the newest version, that the helper methods are no longer in the CompatHelper class?
To me it seems like it went away between Merge remote-tracking branch 'origin/20.1' into 20.1 and Cauldrons are now on the creative tab, where the latter commit must have changed parent commit, as looking at the commit history in the file currently doesn't show any evidence of these helper methods ever existing. I would assume this isn't intentional?

Not sure if you've noticed my question yet, so commenting on this again.
In my latest update I just used the classes and stuff by accessing player BackData and such, which I used before this issue was created. I'm absolutely fine with keeping it this way, I'm just not sure again if this change where these methods was removed was intentional or not

Oops, sorry for accidently ghosting you D: It looks like with those methods were deleted in a bad merge I made. I'll get move those methods back to CompatHelper in 20.1-0.23-v2 (for real this time)

Actually, I've been getting a lot of issue with over grave mods clearing my inventory on death. I'm going to have to find the exact like of code that starts processing a player's death and inject there but I know this'll mess up anything you'd want to do since I'm trying to get ahead of grave mod's injects.
I've just learnt about Functions and Runnables and they're super super powerful so I'll now have a Function run that executes my drop code.  I also changed how pots work since adding cauldrons. They no longer drop all their items and instead drop the pot item loaded with the inventory.
This is my first mod so I'm always learning new ways to handle my code and I think this is better option again and I hope exams went well! ;)

Actually Actually... I realized I just described an Event, so I made a cancelable event fired when the Back Slot should drop. You're given access to the BackpackInventory & BackSlot or a way to cancel my method entirely and write you're own implementation. Unless you have any suggestions, this is my last idea lol.

Updated the mod yesterday with the correct code. I'm sorry for taking so long, I've just done different things lately.
Compat between our mods should work now anyway. Thank you for the help in improving the compat, and make sure to let me know if you would notice the compat breaking in the future!


Lifecycle Method is called in Query.field().hasThisElement() when look up an element in embedded Array

As I create a local variable in the method hasThisElement() as below, it triggered the life cycle event 'prePersist' of the local variable which should only be called when persist to db.
createQuery(GroupChat.class).field("members").hasThisElement(new GroupMember(name,id));

it trigged a prePersist method defined in GroupMember, which would break the seach condition.
Morphia version: 0.107
JDK version: 1.7.0_07
Mongodb version: 2.11.4

related to #606


Added python 3.10 to tests

Added tox config for 3.10
Added python version 3.10 in tests

Fixes #29

@hillairet So there's also no problem with python 3.8 with the current list of requirements and code. Should require them all to pass before we can merge a PR?


Can't start Discurses: Syntax error

Hi, when I try to start discurses I'm getting the following error:

I'm on macOS High Sierra V 10.13.6

Hi! What Discurse version are you using?

It's Version 0.3.4

This seems to be related to https://github.com/Rapptz/discord.py/issues/1421

I am also getting this error. I'm on a Lenovo T61 with Manjaro (Arch, basically) with Python 3.7.1
My error is occurring in compat.py at line 32.
Full log:
Traceback (most recent call last):
  File "/usr/bin/discurses", line 11, in <module>
    load_entry_point('discurses==0.3.4', 'console_scripts', 'discurses')()
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 487, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2728, in load_entry_point
    return ep.load()
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2346, in load
    return self.resolve()
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2352, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3.7/site-packages/discurses/__main__.py", line 1, in <module>
    from . import discord
  File "/usr/lib/python3.7/site-packages/discurses/discord.py", line 6, in <module>
    import discord
  File "/usr/lib/python3.7/site-packages/discord/__init__.py", line 20, in <module>
    from .client import Client, AppInfo, ChannelPermissions
  File "/usr/lib/python3.7/site-packages/discord/client.py", line 38, in <module>
    from .state import ConnectionState
  File "/usr/lib/python3.7/site-packages/discord/state.py", line 36, in <module>
    from . import utils, compat
  File "/usr/lib/python3.7/site-packages/discord/compat.py", line 32
    create_task = asyncio.async
                              ^
SyntaxError: invalid syntax


Is this package being maintained?

Congrats on the 1.3 million weekly downloads, but no updates in 7 years, and no replies to issues?

Looks like validator has far more traction.

Hi @dandv unfortunately, validator.isURL('http://example.com:8042/over/there?name=férret#no#se') returns true whereas éand # are not allowed in respectively the query and the fragment.
I was facing the same issues so I decided to build a module as reliable as possible strictly based on RFC-3986: https://github.com/adrienv1520/node-uri
The main features of this project are:

parse any URI (URNs, URLs, URIs with IDNs support, etc.);
get the safe Punycode ASCII or Unicode serialization of a domain;
check an URI, HTTP/HTTPS/Sitemap URL, IP, domain is valid with clear checking errors;
encode/decode an URI, HTTP/HTTPS/Sitemap URL.

I hope it could help, despite the lack of TypeScript support.

Thank you @adrienv1520 for this package, fixes and fusion two of my packages


Monero ATM

If we receive even a low badge sponsorship budget, it is very likely that our electronic badges will work with POS and ATM machines on site.


⚠ Bofrost.at has degraded performance

In 31a3f43, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2514 ms

Resolved: Bofrost.at performance has improved in 2467066.


#4 link to docs re suppressing warnings

Look OK?
Or would you rather duplicate the instructions in both READMEs?
Some of the linked instructions are SBT-specific, which might not be that helpful if people are trying to use scapegoat without SBT.
(There aren't any instructions at the linked README about per-line suppression yet, AFAICS. I'll raise a PR.)

I think this is good.


3 SQL joins?

SQL Table:
[users] [user_documents] [documents]
How can I make an SQL join in all these tables?
The GraphQL Schema looks like:
user(id: 1) {
    fullName
    documents {
        fileName
    }
}

Use the junction feature.  It would look something like this for you as a "document" field using a custom "documentType" (that is assigned sqlTable: 'documents') inside your parent "user" type:
    // ...
    'document': {
        'type': new GraphQLList(documentType),
        'junction': {
            'sqlTable': `user_documents`,
            'sqlJoins': [
                ( parentTable, junctionTable ) => `${parentTable}.id = ${junctionTable}.user_id`,
                ( junctionTable, targetTable ) => `${junctionTable}.document_id = ${targetTable}.id`
            ]
        }
    },

...adjusting names of id columns to fit your setup (document_id and user_id are my assumptions)


Add one more ColorMap

This matches with Book figure(s), use by setting preference "Muscle Color Scheme" to "Book"
Fixes issue #
Brief summary of changes
One more option for muscle coloring
Testing I've completed
Loaded states files from existing examples and got colors that match Tom's
CHANGELOG.md (choose one)

no need to update because new option, hidden for now

I'm not sure users will know what "Book" means. Are there other descriptors you and @tkuchida have been using to describe this color scheme?

That's a good point @chrisdembia I wasn't planning on publishing this to users, but rather make it available internally to @tkuchida to tweak a little more or use for figures. If we reach a consensus we can document.

I've already made the changes locally and don't plan on using this feature.

Thanks @tkuchida
I will not merge this PR then until there's a specific need. I'll leave it open for potential future use and to show users what it takes to add a new ColorMap for muscles.


Full JSON-RPC 2.0 compliance for the VM service protocol

a2fd2023140f9d2a54e1593b16645aefb41903c7, cf0955a83eb3bf37a8006b204b6dc43a821c1d3b, 4153313dfd9293c49213798370bae3f75cd0ce0a, and 61ea0618ce6e29cf101bc9c062222f04b97f211a go a long way towards making the VM service protocol compatible. It's at the point where it should work out-of-the-box with most general-purpose JSON-RPC 2.0 clients, but but it's not yet fully compliant. I've noticed two divergences: the VM service protocol doesn't support batch requests, and it doesn't return the correct error responses for invalid input (instead of returning responses, it closes the socket).

Have we made progress here?


the last cell in the how-to notebook does not run

for row in database:
    meanHalflife, varHalflife = ebisu.priorToHalflife(row['model'])
    print("Fact #{} has half-life of ≈{:0.1f} hours".format(row['factID'], meanHalflife))

TypeErro---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
 in ()
1 for row in database:
----> 2     meanHalflife, varHalflife = ebisu.priorToHalflife(row['model'])
3     print("Fact #{} has half-life of ≈{:0.1f} hours".format(row['factID'], meanHalflife))
TypeError: 'float' object is not iterable
r                                 Traceback (most recent call last)
 in ()
1 for row in database:
----> 2     meanHalflife, varHalflife = ebisu.priorToHalflife(row['model'])
3     print("Fact #{} has half-life of ≈{:0.1f} hours".format(row['factID'], meanHalflife))
TypeError: 'float' object is not iterable

SO sorry about that, thank you so much for checking! I must have been using an older API for priorToHalflife there and never revisited the notebook after it changed. It is now fixed!

Hi Ahmed,
The final cell on the notebook now runs for me.
Thank you very much for the fast reply.
I think ebisu could be a valuable contribution.
Best regards,
Blaine
On Sat, Oct 6, 2018 at 12:13 PM Ahmed Fasih<EMAIL_ADDRESS>wrote:

SO sorry about that, thank you so much for checking! I must have been
using an older API for priorToHalflife there and never revisited the
notebook after it changed. It is now fixed!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fasiha/ebisu/issues/2#issuecomment-427590782, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AOeSC9VceUHnfwzAa8wE52cFkqKALaFaks5uiOSdgaJpZM4XLZ4Q
.

--
Best regards,
Blaine
Blaine Mooers, Ph.D.
Associate Professor
Department of Biochemistry and Molecular Biology
College of Medicine
University of Oklahoma Health Sciences Center
S.L. Young Biomedical Research Center Rm. 466
975 NE 10th Street
https://maps.google.com/?q=975+NE+10th+Street&entry=gmail&source=g, BRC
466
Oklahoma City, OK 73104-5419
office:<PHONE_NUMBER>   lab:<PHONE_NUMBER>
Faculty webpage
http://basicsciences.ouhsc.edu/biochemmolbiol/Faculty/bio_details/TabId/11753/ArtMID/30702/ArticleID/6430/Mooers-Blaine-HM-PhD.aspx
X-ray lab (LBSF)
http://research.ouhsc.edu/CoreFacilities/LaboratoryofBiomolecularStructureandFunction.aspx
SSRL
UEC
https://www-ssrl.slac.stanford.edu/content/about-ssrl/advisory-panels/ssrl-users-organization/members/ssrluo-2016-executive-committee-members
SSURF
EasyPyMOL https://github.com/MooersLab/EasyPyMOL Molecular Graphics
https://www.oumedicine.com/docs/default-source/ad-biochemistry-workfiles/moleculargraphicslinks.html
https://www.oumedicine.com/docs/default-source/ad-biochemistry-workfiles/MolecularGraphicsLinks.html
Small
Angle Scattering
http://www.oumedicine.com/docs/default-source/ad-biochemistry-workfiles/small-angle-scattering-links-27aug2014.html?sfvrsn=0
office:<PHONE_NUMBER>   lab:<PHONE_NUMBER>
e-mail<EMAIL_ADDRESS>(or<EMAIL_ADDRESS>

Thanks @MooersLab, we've been using it in a couple of flashcard apps, most recently fairly heavily with Curtiz, and having not seen any catastrophic failures (barring #1 which I hope to fix soon), my confidence in it is growing. I'm trying to work up the courage to ask Damien if he'd use it as the scheduling engine for Anki 😅, but Anki has so heavily invested in pre-scheduling due dates for cards, I'm sure it'd be a huge headache to unravel that assumption… I certainly cannot go back to having "due dates"—I study when I want to, sometimes a lot, sometimes not much, and the probabilities do their thing, and all is well 😊.


CodeUpdate: Test power on is blocked

During image activation, a power on is blocked until the activation is completed.

Thank you @anoo1 .
Could you pls let know equivalent development story.
openbmc/openbmc#1468 - Is all fall under this issue?


Red line of the playhead takes to much space

When I have freshly selected a time-in-point annotation (that has now an anchor) and I want to move this annotation I have to almost click on the edge of the annotation to be able to do so. Otherwise I move the playhead. This is because the red line of the playhead "takes to much space" in the sense of when clicking slightly right or left of the playhead I still move the playhead and not the annotation below.
Solution: Make this space much smaller (at least half as wide as now).

I am not sure I agree once more, sorry. :sweat_smile:
As someone with rather impaired vision, I dislike tiny UI elements with no leeway to click/drag them with a passion. The real problem in my opinion is that clicking on an annotation currently unconditionally moves the play head to that position. Now I'm not a user of the tool of course, but at least for me that is almost never the intention. Can you confirm this?
Maybe we can decomplect the interactions of "moving the play head" and "clicking annotations." somehow. We might even think about lifting the restriction of having to select an annotation to move/resize it in the first place. :thinking:

Related: #287.

Again (see https://github.com/opencast/annotation-tool/issues/287#issuecomment-577672612): The moving of the play head to the position of an annotation when clicking on it is a central feature of the annotation tool.
A different solution would be to differentiate between single and double click. Single click = annotation gets selected but play head does not get moved. Double click = annotation gets selected and play head jumps to the beginning of an annotation and activates the edit option (see:  https://github.com/opencast/annotation-tool/issues/321#issue-556224721).

looks fine. thx!


Altimeter position resets on scene change and on entering/leaving IVA

This is basically the same bug as Draggable Navball has, only I can't mitigate it by overriding the position gamesetting because there isn't one for the altimeter.

Fixed by PR #2


[Regression][Selection Line] Uncaught ReferenceError: value is not defined

https://github.com/KleeGroup/focus-components/blob/d6a80ff81a683cbd4fa6c827ec1e6fe56950de40/src/list/selection/list.js#L104
    _handleLineSelection(data, isSelected) {
        const {selectedItems} = this.state;
        const newSelectedItems = new Map();
        if (selectedItems !== null) {
            for (let [key, value] of selectedItems) {
                newSelectedItems.set(key, value);
            }
        }
        newSelectedItems.set(data, value);
        this.setState({selectedItems: newSelectedItems});
    },

Focus-Core v0.12.1-rc3
Focus-Components v0.7.10-rc4

Holy craps, this was fixed, I think the correction has been lost... I correct it right now, sorry

Okay thank you dude


when the v1.0 coming?

when the v1.0 coming?

I hope this month, but i think never :smile:

do you kuow why?  i like vibora

Frank is a little bit busy. He is working on a better release which should container all final stuff.
He said he want to release it on september (he doesn't said which september) but his last state was that he's looking for some names for third party modules for vibora like schemas or templating.
Another thing was that he's unclear if he split vibora in multiple modules or let it be in one big module. I think he choosed the first one.
He's also adding 100% test coverage which needs its time. Please be patient. I think the next release is coming on one or (worst case) two months. 😄

thank you!  thank open source! i am a chinese people, thank your answer... my englist is not good

I'm a huge fan of the design and usage of Vibora, but you should really push out a new release version if the entire codebase is crippled simply by a new reserved keyword.

hey, how the version 1 is doing?

thanks for the awesome project

when the v1.0 coming?

Please read my commet dudes...

No commits in more than 3 months. Is project dead?

@wooque Only 3 months.

go ahead frank. i have a future project that i want to use with vibora. i know you said that it can not be used be used in production but i am enthusiast

Any news

In Dezember a update is coming. Before Christmas he will push a branch.

Christmas will come！！！

D-5 remaining xD

Christmas is coming！！！

Christmas is here!

Bounced check

As far as contributing goes (helping)... I suppose this project is a bit on hold due to the total refactoring? As unless there's an outline of how it would be implemented, one would, if trying to contribute/build on this, would just be building on a different fork altogether. Does that seem a correct assertion?

Here's hoping 2019 proves early on to be the Year of the Viper :)

until v1.0, responder powered by starlette can be used.
Or anything else?


Support for Indexes

Currently indexes don't seem to be supported

It could be great to have at least unique indexes

Agreed @rodrigorn, I'll take a look at it soon.

how can I help @dmarcelino?

Thanks @rodrigorn. Can you take a look at PR #36? The key changes were done by @naderio and I think it will make you happy.


"owner" dropdown list has duplicated entries

Observation: In the v2/admin/tasks page, the dropdown menu listing all possible "owner" values has repeated entries.
Expected behavior: the list only has unique entries.
(I haven't checked yet whether this list is prepared in the backend or created in the webclient)

This happened when two users had the same slurm_user value. Fixed in #562.


Delete TextDiagrammable in favor of circuit_diagram_info magic method

Converted all text_diagram_info methods into circuit_diagram_info
Added support for any Iterable result out of circuit_diagram_info
Updated docs
CircuitDiagramInfo[Args] is now equatable and has a parsable repr

Fixes https://github.com/quantumlib/Cirq/issues/946

Automerge cancelled: A status check is failing.

Automerge: started

Automerge done.


implement 'Reverse X Values' for box plot

This functionality is implemented in Python:
https://github.com/dtcenter/METplotpy/issues/119


Pre-built plugin for Windows / Android for UE 4.11 ?

This is super awesome plugin!!!
Could you please provide a pre-built version for Windows / Android for UE4 4.11 ?

Thanks, the github repo includes binaries compiled for Windows.
Please follow the instructions in the following Wiki to get this to work on Windows.
https://wiki.unrealengine.com/Speech_Recognition_Plugin
Best bet is to download the example project, and examine the blueprint of the Character.
At the moment, this only works for Windows.
An Android port will be available in the coming weeks.

Oh, ok. Thanks.
Really looking forward Android version !!!

#woot !!

Would love to have this for Android, is this possible? Do you need help?

Sorry, since this time, I have been contacted by a company, and working on it exclusively as part of my work with them. Sorry about that. Once the project is finished, the plugin will be released...but unfortunately, it won't be any time soon.

Understood, but are you working on this project as your work now?
From what I can understand it will be a paid plugin now, or it will remain open source?
Thanks,

The project will use the android port, once the project is released (at a later date), the plugin and the code will be too. Can't say too much more, other than that.


Modify and remove trusted sources.

Also rearranged stream helper functions so that they would be closer to the streams query.
Will remove unnecessary facebookPages query (and possibly other unused queries/mutations) in a separate PR.


[Feature]: Enable configuration of non-dismissal of modals

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
https://theappsmith.slack.com/archives/C04P60V0VQE/p1706258566455659?thread_ts=1706258354.380199&cid=C04P60V0VQE
Why should this be worked on?
Use case: Not allowing a user to proceed further without taking required action on a pop-up window

Give the ability to configure the opening of a modal on top of another modal


[WIP] Updated to CSI v1.0.0

I don't consider this ready to be merged yet, having not yet tested the RBD plugin.  I'm submitting it now, primarily to request feedback.  The cephfs plugin is tested and working.

thanks @mcronce. Have you tried it on Kubernetes 1.12 too? If 1.12 is not working, we can create a branch for 1.13 and still continue rest of the work in master branch.
cc @mkimuram @mickymiek for potential merge conflicts

there is a gofmt and go vet error
0.03s$ test -z $(gofmt -s -l $GO_FILES)
The command "test -z $(gofmt -s -l $GO_FILES)" exited with 1.
0.53s$ go vet -v $(go list ./... | grep -v /vendor/)
cephfs/main.go:24:2: could not import github.com/ceph/ceph-csi/pkg/cephfs (can't find import: "github.com/ceph/ceph-csi/pkg/cephfs")

Re: Kubernetes 1.12, almost definitely not.  I know with certainty that driver registration fails on 1.12 - that's the reason I waited until today to submit this, I didn't want to go building kubelets from source and dropping them in my cluster, and I didn't want to submit a PR before at least slightly testing :)
I'm not sure if the plugin will fail to act, though.  My guess would be no, since there are protobuf changes between CSI 0.3.0 and CSI 1.0.0.
As far as the gofmt/go vet errors, I'll get them fixed up

Okey-dokey, so, this round of changes includes the following:

Ran gofmt on pkg/rbd/controllerserver.go
Fixed up errors in pkg/rbd/rbd.go that go vet mentioned
Changed the cephfs provisioner to utilize the name attribute provided in the CreateVolumeRequest (admittedly, this was the primary reason I pulled down the project and started work on it for my own needs haha) - CSI 1.0.0 mentions this at https://github.com/container-storage-interface/spec/blob/v1.0.0/csi.proto#L176 - I will push another commit that makes the same changes to the RBD plugin for volumes and snapshots once I get setup to test the RBD plugin

CSI 1.0.0 is less explicit about it for snapshots, but my interpretation of the note at https://github.com/container-storage-interface/spec/blob/v1.0.0/csi.proto#L843 is that it should be the same as volume names.  If anybody disagrees I'll leave that part out :)

I didn't get the same result from go vet that you did - after fixing what I got in pkg/rbd/rbd.go, I've got empty output:
$ go list ./... | grep -v '^/vendor'
github.com/ceph/ceph-csi/cephfs
github.com/ceph/ceph-csi/pkg/cephfs
github.com/ceph/ceph-csi/pkg/rbd
github.com/ceph/ceph-csi/rbd
$ go vet $(go list ./... | grep -v '^/vendor')
$

I do have the project checked out to ${GOPATH}/src/github.com/ceph/ceph-csi, would that make a difference?

Closing in favor of #105


[Bug] Compilation Error Could not render {{ metric('spend') }} / {{ metric('clicks') }}: 'metric' is undefined

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
DBT unable to compile project due to below error,
Server error: RPC server failed to compile project, call the "status" method for compile status: Compilation Error
Could not render {{ metric('spend') }} / {{ metric('clicks') }}: 'metric' is undefined
Running DBT cloud
Packages versions:

package: fivetran/ad_reporting
version: [">=1.0.0", "<1.1.0"]

Relevant error log or model output
upon DBT DEPS command:
Installing fivetran/netsuite
09:04:48    Installed from version 0.6.0
09:04:48    Updated version available: 0.6.2
09:04:48  Installing fivetran/ad_reporting
09:04:51    Installed from version 1.0.1
09:04:51    Up to date!
09:04:51  Installing fivetran/fivetran_log
09:04:53    Installed from version 0.6.3
09:04:53    Up to date!
09:04:53  Installing fivetran/netsuite_source
09:04:56    Installed from version 0.5.1
09:04:56    Up to date!
09:04:56  Installing fivetran/apple_search_ads
09:04:57    Installed from version 0.1.0
09:04:57    Up to date!
09:04:57  Installing fivetran/snapchat_ads
09:04:58    Installed from version 0.4.0
09:04:58    Up to date!
09:04:58  Installing fivetran/facebook_ads
09:04:59    Installed from version 0.5.0
09:04:59    Up to date!
09:04:59  Installing fivetran/google_ads
09:05:01    Installed from version 0.8.0
09:05:01    Up to date!
09:05:01  Installing fivetran/pinterest
09:05:02    Installed from version 0.6.0
09:05:02    Up to date!
09:05:02  Installing fivetran/linkedin
09:05:03    Installed from version 0.5.0
09:05:03    Up to date!
09:05:03  Installing fivetran/microsoft_ads
09:05:04    Installed from version 0.5.1
09:05:04    Up to date!
09:05:04  Installing fivetran/tiktok_ads
09:05:05    Installed from version 0.2.1
09:05:05    Up to date!
09:05:05  Installing fivetran/twitter_ads
09:05:06    Installed from version 0.5.0
09:05:06    Up to date!
09:05:06  Installing fivetran/fivetran_utils
09:05:07    Installed from version 0.3.9
09:05:07    Updated version available: 0.4.0
09:05:07  Installing dbt-labs/spark_utils
09:05:08    Installed from version 0.3.0
09:05:08    Up to date!
09:05:08  Installing fivetran/apple_search_ads_source
09:05:10    Installed from version 0.1.2
09:05:10    Up to date!
09:05:10  Installing fivetran/snapchat_ads_source
09:05:11    Installed from version 0.4.0
09:05:11    Up to date!
09:05:11  Installing fivetran/facebook_ads_source
09:05:13    Installed from version 0.5.0
09:05:13    Up to date!
09:05:13  Installing fivetran/google_ads_source
09:05:14    Installed from version 0.8.0
09:05:14    Up to date!
09:05:14  Installing fivetran/pinterest_source
09:05:16    Installed from version 0.6.0
09:05:16    Up to date!
09:05:16  Installing fivetran/linkedin_source
09:05:17    Installed from version 0.5.0
09:05:17    Up to date!
09:05:17  Installing fivetran/microsoft_ads_source
09:05:19    Installed from version 0.6.0
09:05:19    Up to date!
09:05:19  Installing fivetran/tiktok_ads_source
09:05:20    Installed from version 0.2.0
09:05:20    Up to date!
09:05:20  Installing fivetran/twitter_ads_source
09:05:21    Installed from version 0.5.0
09:05:21    Up to date!
09:05:21  Installing dbt-labs/dbt_utils
09:05:28    Installed from version 0.8.6
09:05:28    Updated version available: 0.9.2
09:05:28  Installing calogica/dbt_expectations
09:05:31    Installed from version 0.5.8
09:05:31    Updated version available: 0.7.0
09:05:31  Installing calogica/dbt_date
09:05:32    Installed from version 0.5.7
09:05:32    Updated version available: 0.6.2
09:05:32
09:05:32  Updates available for packages: ['fivetran/netsuite', 'fivetran/fivetran_utils', 'dbt-labs/dbt_utils', 'calogica/dbt_expectations', 'calogica/dbt_date']
Update your versions in packages.yml, then run dbt deps
Compilation Error
  Could not render {{ metric('spend') }} / {{ metric('clicks') }}: 'metric' is undefined

Expected behavior
expecting project to compile and allow for editing within DBT cloud IDE
dbt Project configurations
`
Name your project! Project names should contain only lowercase characters
and underscores. A good package name should reflect your organization's
name or the intended use of these models
name: 'elvie_bi'
version: '1.0.0'
config-version: 2
This setting configures which "profile" dbt uses for this project.
profile: 'default'
These configurations specify where dbt should look for different types of files.
The source-paths config, for example, states that models in this project can be
found in the "models/" directory. You probably won't need to change these!
model-paths: ["models"]
analysis-paths: ["analyses"]
test-paths: ["tests"]
seed-paths: ["seeds"]
macro-paths: ["macros"]
snapshot-paths: ["snapshots"]
target-path: "target_{{ env_var('HOSTNAME') }}"  # directory which will store compiled SQL files
clean-targets:         # directories to be removed by dbt clean

"target_{{ env_var('HOSTNAME') }}"
"dbt_packages"

Configuring models
Full documentation: https://docs.getdbt.com/docs/configuring-models
In this example config, we tell dbt to build all models in the example/ directory
as tables. These settings can be overridden in the individual model files
using the {{ config(...) }} macro.
models:
elvie_bi:
stg_amazon:
  schema: stg_amazon
  materialized: table

stg_netsuite:
  schema: stg_netsuite
  materialized: table

stg_finance:
  schema: stg_finance
  materialized: table

stg_hierarchies:
  schema: stg_hierarchies
  materialized: table

stg_operations:
  schema: stg_operations
  materialized: table

reporting_marketing:
  schema: reporting_marketing
  materialized: table

reporting_trading:
  schema: reporting_trading
  materialized: table

netsuite:
+schema: reporting_trading
netsuite_source:
+schema: stg_netsuite
ad_reporting:
+schema: reporting_marketing
facebook_ads:
+schema: stg_facebook_ads
facebook_ads_source:
+schema: stg_facebook_ads
facebook_ads_creative_history:
+schema: stg_facebook_ads
google_ads:
+schema: stg_google_ads
google_ads_source:
+schema: stg_google_ads
fivetran_log:
+schema: reporting_bi # leave blank for just the target_schema
#ADS MODELS
# disable both pinterest models if not using pinterest ads
pinterest:
enabled: false
pinterest_source:
enabled: false
# disable both microsoft ads models if not using microsoft ads
microsoft_ads:
enabled: false
microsoft_ads_source:
enabled: false
# disable both linkedin ads models if not using linkedin ads
linkedin:
enabled: false
linkedin_source:
enabled: false
# disable both twitter ads models if not using twitter ads
twitter_ads:
enabled: false
twitter_ads_source:
enabled: false
# disable both snapchat ads models if not using snapchat ads
snapchat_ads:
enabled: false
snapchat_ads_source:
enabled: false
# disable both tiktok ads models if not using tiktok ads
tiktok_ads:
enabled: false
tiktok_ads_source:
enabled: false
vars:
netsuite_data_model: netsuite2 #netsuite by default
netsuite_schema: raw_netsuite
netsuite_source:
# netsuite_database: your_database_name
# netsuite_schema: src_netsuite
netsuite_schema: netsuite_suiteanalytics
#ADS MODEL
ad_reporting__apple_search_ads_enabled: False
ad_reporting__pinterest_ads_enabled: False
ad_reporting__microsoft_ads_enabled: False
ad_reporting__linkedin_ads_enabled: False
ad_reporting__twitter_ads_enabled: False
ad_reporting__snapchat_ads_enabled: False
ad_reporting__tiktok_ads_enabled: False
facebook_ads_schema: raw_facebook_ads
google_ads_schema: raw_google_ads
#Fivetran Log DBT MODEL
fivetran_log_schema: raw_fivetran_log
fivetran_log_using_transformations: false # this will disable all transformation + trigger_table logic
fivetran_log_using_triggers: false # this will disable only trigger_table logic
fivetran_log_using_account_membership: false # this will disable only the account membership logic
fivetran_log_using_destination_membership: false # this will disable only the destination membership logic
fivetran_log_using_user: false # this will disable only the user logic
fivetran_log_using_sync_alert_messages: false # this will disable only the sync alert messages within the connector status model`
Package versions
packages:

package: fivetran/netsuite
version: 0.6.0

package: fivetran/ad_reporting
version: [">=1.0.0", "<1.1.0"]

package: fivetran/fivetran_log
version: 0.6.3

What database are you using dbt with?
bigquery
dbt Version

Unable to perform this request as project cannot compile
Additional Context
No response
Are you willing to open a PR to help address this issue?

[ ] Yes.
[X] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

Hi @Elvie-JackRockett thanks for raising this ticket! To get metrics to render, you'll need to add the dbt metrics package to your packages.yml. See our readme for more info. Let me know if that solves it!

Thanks for the speedy reply @fivetran-reneeli  I've added that in now (odd as it worked fine without this package before!)
Unfortunately its having an issue with the version:
**Runtime Error
Failed to read package: Runtime Error
This version of dbt is not supported with the 'metrics' package.
Installed version of dbt: =1.0.8
Required version of dbt for 'metrics': ['>=1.4.0-a1', '<1.5.0']
Check for a different version of the 'metrics' package, or run dbt again with --no-version-check
Error encountered in /usr/src/develop/user-80335/environment-113802/repository-90021/dbt_packages/metrics/dbt_project.yml
Error encountered in /usr/src/develop/user-80335/environment-113802/repository-90021/dbt_packages/metrics**

I use the version required as per that error message and still nothing

OK @fivetran-reneeli  I resolved following your guidsance and updating my IDE to DBT core 1.3
Thank you!

No problem! Thanks for the updates!


B #6464: backup execution PARALLEL mode fix

Description
There is a typo causing the PARALLEL execution mode to be not recognized
Branches to which this PR applies

[x] master
[x] one-6.8

[ ] Check this if this PR should not be squashed

Thanks!
Merged as per 7831e0e08e


Mesh.ToPolySurface crashes Revit if Mesh is too simple

Feeding a very simple mesh (in this case just four points) into Mesh.ToPolySurface will consistently crash Revit 2016 and 2017. Increasing the number of points will solve the issue so it's no big deal, but still interesting, I think.
SuperSimpleTopo.zip

Thanks for catching this one. I hadn't considered this option.

This should be fixed in the latest 110.0.2 release.


Renamed base branch to main

git branch -m master_update_2021_3 main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

I'll also remove the old master branch as everything is merged to main now.


Office 2016 with Project Pro for O365

We have purchased and deployed Office 2016 (standalone msi) to all our users. Recently we decided to move to Project Online for our Project Management. We tried to install the Project Pro for O365 and we were not able to.
What are the work arounds for this? Moving to Office 365 is not an option

@seanshan86 . Office 2016 keys and office  365 keys are different.  I think either only suite one can be installed windows
uninstall office  2016 and buy office 365 keys through Microsoft store,
and then download the installation file. install on windows and then activate

Unfortunately you can't mix Office 2016 VL MSI and Project 365 as this is not a supported configuration. I will close this issue due to the time passed since it was opened. If there are still technical issues, please post to https://techcommunity.microsoft.com/t5/microsoft-365-apps-for/bd-p/Microsoft365Apps. For documentation issues, please open a new issue here in GitHub.


Add command top

could i implement ps and top for this, also there already exist projects like bottom

Making this ticket about top only as there is another ticket about ps with a PR linked to it.


fix(template): testing helper PoC #2

What?
This is a different approach. Instead of mocking postMessage and addEventListener, this actually changes createFieldPlugin().
We used to have only createFieldPlugin() and now we also have internalCreateFieldPlugin(). The internalCreateFieldPlugin() accepts two more options:

postToContainer
listenToContainer

The createFieldPlugin calls the internalCreateFieldPlugin with those implementations, but in our testing helper, we mock @storyblok/field-plugin, and replaces createFieldPlugin with different implementations of postToContainer and listenToContainer.
But this requires us to actually export internalCreateFieldPlugin from the library, which is not that big of a deal, in my opinion. (of course, we could rename it)
Not sure which take I prefer (the previous one and this)
but probably a good food for thought :)

Current dependencies on/for this PR:

main

PR #304

PR #307

PR #316   👈

This stack of pull requests is managed by Graphite.


[WIP] use github API to query jobs

Substitute #2

Close it since it has been fixed in: https://github.com/openshift/release-tests/commit/0b2eafd7086d57b2b2e837007564c956e1255213


Podspec platform

I am currently working on a project with a minimum platform target of iOS 8.0 and need to generate a PDF. I found this library and tried to install it via cocoapods and found that i was unable to do so because of the platform in your podspec is :ios, "9.0".
So, I just tried to add the file SimplePDF.swift to the project and use it and found I was able to compile and use your library without problems.
Could you set your podspec's platform to `:ios, "8.0"``?

Sure, I will update it to 8.0 😀.

That was fast! :open_mouth:
Thanks a lot.


fix: avoid deprecated ts_utils.get_node_text

Conflict :dizzy_face:

:sweat_drops: yeah, already had this locally.


footer

Resolved. Footer was hidden behind the other content due to z-index. Added content to the footer


Fetch Failed Error

When I run:
MAILSLURP_API_KEY=***  MAILSLURP_INBOX_ID=*** FORM_NAME="Bobby Brown" FORM_PHONE="0176 5555555" npm run debug

The booking fails while waiting for the email verification code with output like this:
...
2024-01-09 16:20:16 debug: Retrieving booking page for https://service.berlin.de/terminvereinbarung/termin/time/1709030880/169/
2024-01-09 16:20:19 debug: Filling booking form for https://service.berlin.de/terminvereinbarung/termin/time/1709030880/169/
2024-01-09 16:20:19 debug: Writing the configured phone number if the feature is available ...
2024-01-09 16:20:19 debug: Reading all emails from MailSlurp inbox so we can wait for new unread emails ...
2024-01-09 16:20:24 debug: Waiting for email verification code to arrive at inbox with id ... ...
2024-01-09 16:21:25 error: Booking appointment failed at https://service.berlin.de/terminvereinbarung/termin/time/1709030880/169/: fetch failed

I am trying to run the program without setting MAILSLURP_INBOX_ID to see if that has any effect.
No emails have been received to the specified inbox ... maybe this is related to #14 ?

I'm also running behind a VPN, which might be impacting the MailSlurp API?

Perhaps this issue is related to how I created a MailSlurp inbox via the MailSlurp web UI.


[openapi-alps] Replace nodegit with better alternative

Dependency nodegit appears to be no longer maintained.  The last non-alpha release was published 3 years ago.
It should be replaced with a better alternative.  Options:

simple-git (2.6M weekly downloads, published 6 days ago)
isomorhpic-git (237k weekly downloads, published 6 months ago)

nodegit is no longer in pnpm-lock.yaml


Clean up Subject, Observable, and History interface

Remove start callback. This is in compliance with the ES spec.
Move Observable.hash to Subject.hash. It returns a Subject.
History is now a Subject, eliminating history.updates
Update Flow types. I think the new way Observables are structured is a lot nicer, in terms of Flow.

Why
1. Remove start callback. This is in compliance with the ES spec.
Besides being against the spec, I didn't like how Microcosm 12.x has a open and update command. Most of the time you know if an action has been opened. You just pushed it beyond that, I want to encourage next -> complete to be the same data type.
2. Move Observable.hash to Subject.hash. It returns a Subject.
This just sort of made sense
3. History is now a Subject, eliminating history.updates
I want all major pieces to adhere to the observable spec. I can see subscribing to history updates being useful for tooling. But mostly this is just an attempt at hygiene. Ideally, you could eventually do something like.

Codecov Report

Merging #481 into master will decrease coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #481      +/-   ##
==========================================
- Coverage   97.65%   97.62%   -0.03%
==========================================
  Files          29       29
  Lines         681      673       -8
  Branches      143      143
==========================================
- Hits          665      657       -8
  Misses         13       13
  Partials        3        3

Impacted Files
Coverage Δ

packages/microcosm/src/microcosm.js
84.37% <100%> (+0.5%)
:arrow_up:

packages/microcosm/src/effect-engine.js
100% <100%> (ø)
:arrow_up:

packages/microcosm-dom/src/presenter.js
100% <100%> (ø)
:arrow_up:

packages/microcosm/src/subject.js
100% <100%> (ø)
:arrow_up:

packages/microcosm-dom/src/action-form.js
100% <100%> (ø)
:arrow_up:

packages/microcosm/src/domain-engine.js
98.03% <100%> (+0.08%)
:arrow_up:

packages/microcosm/src/observable.js
100% <100%> (ø)
:arrow_up:

packages/microcosm-dom/src/action-button.js
100% <100%> (ø)
:arrow_up:

packages/microcosm/src/history.js
100% <100%> (ø)
:arrow_up:

packages/microcosm/src/coroutine.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


AJ-1242: disable primary key cache

Disables the cache for the primary key lookup.
I have deleted all references to the primary key cache, as opposed to commenting it out. We can always refer back to this PR to recreate history if/when we re-enable the cache.

Agreed with Bria, I appreciate all the trailmarker comments!


Error when running python setup.py develop: .* suffix can only be used with == or != operators     PyYAML (>=5.1.*)

I installed PyRep, Coppelia, and the requirement packages for peract already, and was trying to setup peract by running python setup.py develop. But I get the following error:
(peract_env) nan@nan-Alienware-m15:~/Desktop/peract$ python setup.py develop
running develop
/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/setuptools/command/develop.py:40: EasyInstallDeprecationWarning: easy_install command is deprecated.
!!

        ********************************************************************************
        Please avoid running ``setup.py`` and ``easy_install``.
        Instead, use pypa/build, pypa/installer or other
        standards-based tools.

        See https://github.com/pypa/setuptools/issues/917 for details.
        ********************************************************************************

!!
  easy_install.initialize_options(self)
/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!

        ********************************************************************************
        Please avoid running ``setup.py`` directly.
        Instead, use pypa/build, pypa/installer or other
        standards-based tools.

        See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
        ********************************************************************************

!!
  self.initialize_options()
running egg_info
writing peract.egg-info/PKG-INFO
writing dependency_links to peract.egg-info/dependency_links.txt
writing requirements to peract.egg-info/requires.txt
writing top-level names to peract.egg-info/top_level.txt
reading manifest file 'peract.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'peract.egg-info/SOURCES.txt'
running build_ext
Creating /home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/peract.egg-link (link to .)
peract 0.1.0 is already the active version in easy-install.pth

Installed /home/nan/Desktop/peract
Processing dependencies for peract==0.1.0
Traceback (most recent call last):
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3070, in _dep_map
    return self.__dep_map
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2863, in __getattr__
    raise AttributeError(attr)
AttributeError: _DistInfoDistribution__dep_map

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/_vendor/packaging/requirements.py", line 35, in __init__
    parsed = _parse_requirement(requirement_string)
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/_vendor/packaging/_parser.py", line 64, in parse_requirement
    return _parse_requirement(Tokenizer(source, rules=DEFAULT_RULES))
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/_vendor/packaging/_parser.py", line 82, in _parse_requirement
    url, specifier, marker = _parse_requirement_details(tokenizer)
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/_vendor/packaging/_parser.py", line 120, in _parse_requirement_details
    specifier = _parse_specifier(tokenizer)
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/_vendor/packaging/_parser.py", line 216, in _parse_specifier
    parsed_specifiers = _parse_version_many(tokenizer)
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/_vendor/packaging/_parser.py", line 231, in _parse_version_many
    tokenizer.raise_syntax_error(
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/_vendor/packaging/_tokenizer.py", line 165, in raise_syntax_error
    raise ParserSyntaxError(
pkg_resources.extern.packaging._tokenizer.ParserSyntaxError: .* suffix can only be used with `==` or `!=` operators
    PyYAML (>=5.1.*)
            ~~~~~~^

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "setup.py", line 3, in <module>
    setup(
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/setuptools/__init__.py", line 104, in setup
    return distutils.core.setup(**attrs)
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/setuptools/_distutils/core.py", line 185, in setup
    return run_commands(dist)
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
    dist.run_commands()
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
    self.run_command(cmd)
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/setuptools/dist.py", line 967, in run_command
    super().run_command(command)
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
    cmd_obj.run()
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/setuptools/command/develop.py", line 34, in run
    self.install_for_development()
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/setuptools/command/develop.py", line 126, in install_for_development
    self.process_distribution(None, self.dist, not self.no_deps)
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/setuptools/command/easy_install.py", line 785, in process_distribution
    distros = WorkingSet([]).resolve(
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/__init__.py", line 803, in resolve
    new_requirements = dist.requires(req.extras)[::-1]
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2786, in requires
    dm = self._dep_map
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3072, in _dep_map
    self.__dep_map = self._compute_dependencies()
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3082, in _compute_dependencies
    reqs.extend(parse_requirements(req))
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3135, in __init__
    super().__init__(requirement_string)
  File "/home/nan/.virtualenvs/peract_env/lib/python3.8/site-packages/pkg_resources/_vendor/packaging/requirements.py", line 37, in __init__
    raise InvalidRequirement(str(e)) from e
pkg_resources.extern.packaging.requirements.InvalidRequirement: .* suffix can only be used with `==` or `!=` operators
    PyYAML (>=5.1.*)
            ~~~~~~^

I also got this warning after installing the requirements for peract:
DEPRECATION: omegaconf 2.0.6 has a non-standard dependency specifier PyYAML>=5.1.*. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of omegaconf or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at https://github.com/pypa/pip/issues/12063

Anyone knows what's wrong? It seems the omegaconf==2.0.6 package is broken according to a similar issue here:
https://github.com/python-poetry/poetry/issues/4206

I saw this dependency problem on omegaconf is caused by hydra-core==1.0.5 in peract's requirements.txt. I changed that to hydra-core==1.1.0 and installed again, and it runs without error. I don't know if this can make future training or evaluation fail though.


'$attrs is readonly' and '$listeners is readonly'

I think it's a problem with Vue 2.4.4
check this issue - looks the same
https://github.com/apertureless/vue-chartjs/issues/151

Thanks for the report, I'll check it as soon as I can.

I tested my example project with 2.4.4 but found no issue. Can you explain how to reproduce it ?

I have same problem with Vue 2.4.2

Closing due to inactivity.

I am getting this error too. Is there a fix?

please provide an example on how to reproduce this.

I will try to make a reproduction soon. But this is happening to me developing a plugin for another package.
https://github.com/64robots/nova-image-cropper
Maybe its because of duplication of Vue instances but I can't figure out the solution.

I'm facing the same issue, using vue cropper in my component and trying to change a data value in the same component I get this error.

I'm facing the same issue, using vue cropper in my component and trying to change a data value in the same component I get this error.
Vue version 2.5.16
BTW if anyone else is getting this error I solved it by wrapping the cropper in it's own .vue file, kinda anoying to proxy everything but at least it's working without the warning.

@mnooblet This did not fix my issue. Can you please share the file you've created?

Wrapping in its own component is not working for me.  Any hep?

I'm re-opening this, please provide a sample project so that I can debug the issue.

Ive created a repo and I cant reproduce it. I think its because of the Vue.extend you have.
Im using this in a Laravel Nova package, and I believe your package is using the Vue instance from Nova, which causes this kind of warnings.
Im going to fork this repo and try to not using Vue.extend and see what happens

I fixed this issue in my project with this PR #40. Hope it helps!

Thanks, I'll check it out asap.

+1 We are waiting on this PR as well.


Update the content of Recursion Page of DSA in JS

Description
Description:
This issue is for updating the content of Recursion Page  of DSA (Data Structures and Algorithms) section  in our project. Here are the specific changes needed:
1. What is on this Page ? - Section

It should contain the list of topics covered in the video.

2. This Page should Contain Tabs - Learn and Assignment

Create tabs for "Learn" and "Assignment" sections.

3. Learn Section should contain Video and Notes

In the "Learn" section, add subsections for videos and notes.

4. Assignment section should contain assignments

In the "Assignment" section, include assignments related to the topics.

5. To update the content

Go to the Content folder of the root directory, then navigate to the batch folder, and then navigate to the DSA folder to make changes in the 'recursion.mdx' file.

Content Check:
For reference, please check the current content in the Recursion Content
Additional Information:
Please make sure to maintain consistency with the existing structure and style of the project. Let's enhance the DSA page to make it more user-friendly and informative.

I would like to work on it . please assign it to me

I would like to work on it . please assign it to me

Assigned to You ; Submit your PR ASAP

@AjinkyaD3 you have to raise the PR in Frontend Freak Repo. Not in your repo

@AjinkyaD3 Any Update on this Issue?

if it's not started then you can assign it to me

in case there is no update in this issue then you can assign this to me
i am gonna raise a pr
i almost solved it but waiting for @Vishal-raj-1 response sir

in case there is no update in this issue then you can assign this to me i am gonna raise a pr i almost solved it but waiting for @Vishal-raj-1 response sir
Assigned to You

In case there is  no update please assign this issue to me sir.I am working on it currently


Config flow changes

Hi,
I've added support for the new runtime data storage inside the config entries instead of hass.data[DOMAIN] (https://developers.home-assistant.io/blog/2024/04/30/store-runtime-data-inside-config-entry/). Furthermore, I've added the option to unload the config entry (just cleaning all entities) to make it possible to reload the config entry from the UI (for example when the AC became unavailable after cutting its power). Currently, you have to restart Home Assistant to reload the integration.
If there is anything I need to do, please let me know!
Thanks in advance!
Kind regards,
Wesley Vos

Hey,
Thank you for adding support of the data storage and unload.
I will merge it and test it.


Box2D WeldJoint throwing failed assertion exception

An assertion exception is thrown whenever I add a WeldJoint to the Box2D world, no matter the configuration.
'package:box2d_flame/src/math_utils.dart': Failed assertion: line 86 pos 10: 'out != v': is not true.
The exception is thrown in some matrix/vector multiplication function. out and v are two parameters of type Vector2 or Vector3.
I've traced the back stack and it seems like the two vectors are retrieved by calling popVec2 or popVec3 on the Box2D world pool and for some reason it returns the same vector in both calls (maybe it's returning null, I haven't checked).
I tried reconfiguring the WeldJointDef with different values and the same assertion exception was thrown.

I have never tried the WeldJoint I'm afraid, could you add a minimal example to reproduce the exception?

final bd = BodyDef()..type = BodyType.DYNAMIC;
final cs1 = CircleShape()..radius = 0.1;
final cs2 = CircleShape()..radius = 0.1;
final b1 = world.createBody(bd)..createFixtureFromShape(cs1, 1);
final b2 = world.createBody(bd)..createFixtureFromShape(cs2, 1);

final wjd = WeldJointDef()
  ..initialize(b1, b2, b1.worldCenter)
  ..collideConnected = false
  ..dampingRatio = 0.5
  ..frequencyHz = 0.5;

world.createJoint(wjd);

@spydon any insights on this?

I started looking into it, but I don't really get what is happening, @yahel-ck might be onto something about both being null. I will look more into it on Sunday.

@spydon any news on this?

Haven't had any time to look into it, will do it once the massive box2d refactor is merged

I just tried this, it works after the refactor.
So if you'll follow https://github.com/flame-engine/forge2d/pull/1 @yahel-ck you can start using that version, either now or when it is merged and published.


[Improvement]: Generate a main method for the testable jar

Description
ATM, the test runner has to handle the initialization of the module, and configurations, and stop them when executing tests. This is currently done by invoking the required methods through Reflection APIs in Java. This imposes limitations on the following features:

Migrating the test framework completely to Ballerina

The execution still has to be done using reflection since init, start and stop methods has to be handled by the test runner

Supporting bal test with GraalVM native image

The GraalVM native image needs an entrypoint

Suggested solution(s)
When performing the code generation, the testable jars should also be generated with a main which will handle the initialization, test execution and stopping of the module.

This is not a blocker for GraalVM implementation since we decided to use the main method in the test runner as the entrypoint.

Having Java main methods for each testable JARs as the entry points of execution (each testable jar needs to be run separately through java -cp command using separate Java processes) may have some limitations on test native image build and test debugging:

When build native images of tests, multiple images going to be generated (images will be generated per testable packages).

Debugging with test packages will be affected since debugger going to connect and disconnect to the port per execution of testable JARs - needs to start debugging manually through IDE/code editor each time upon one jar's completion.

So we need to have a single Java main to execute all of the testable JARs. We can keep the BTestMain.java for that as currently it's being used and use reflections to invoke main methods of testable JARs.


I get {"v":"*****","k":true,"ib":false,"ob":false,"initialized":true}

[Enter feedback here]
After following the document.
I got
{"v":"****","k":true,"ib":false,"ob":false,"initialized":true}
ib and ob is false
Can anyone tell me how to fix this?

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

ID: 6c72c259-a864-9e1c-b585-562d6bca80ff
Version Independent ID: 30a3fce8-d236-5c7b-88a0-003c971f2819
Content: .NET bot with direct line app service extension - Bot Service
Content Source: articles/bot-service-channel-directline-extension-net-bot.md
Service: bot-service
GitHub Login: @Kaiqb
Microsoft Alias: kamrani

@fifteenjoy, If everything is correct, the page will return this JSON content: {"k":true,"ib":true,"ob":true,"initialized":true}. This is the information you obtain when everything works correctly, where
k determines whether Direct Line App Service Extension (ASE) can read an App Service Extension Key from its configuration.
initialized determines whether Direct Line ASE can use the App Service Extension Key to download the bot metadata from Azure Bot Service
ib determines whether Direct Line ASE can establish an inbound connection with the bot.
ob determines whether Direct Line ASE can establish an outbound connection with the bot.
Can you double-check if you missed any of the steps? Did you save the settings in the app service configuration page?

@fifteenjoy, do you still need help?

Closing the issue. Please feel free to reopen if the issue persists.

Hello.  I am having the same issue.  I've tried to repeat these steps multiple times.


List test datasets

phy.utils.datasets.list_test_data() returns the list of datasets by parsing http://phy.cortexlab.net/data/

... Do we want to discriminate between what these bits of test data do?
I mean, we don't want to indiscriminately download ALL the test data. Should we have some metadata?

Maybe we can have test_..._data.md as well with some notes.
Then, list_test_data() shows the list of all datasets and their associated notes.
Ultimately, download_test_data('test_hybrid') will download the kwik, kwx, and raw.kwd files.


Black area when rendering

Mod Version: 0.4.5 - 1.20
Minercraft version: 1.20.1
latest.log

I need more context here - what exactly is your problem? Are the exported files blank, is the entire screen black, is the lighting on the area broken, or whatever else. In short, actually describe the problem - how you made it happen, how exactly it looks (screenshots do wonders here) and so on
Cheers