Fix English on github-actions bot "✔ Take a coffee ☕"

Preconditions

[X] The feature has not been suggested in the past or it makes sense nowadays.

Current Situation
The wording "✔ Take a coffee ☕" is weird.
"Take a coffee" means to transport a coffee from one location to another.
"Take a coffee break" means to have a break (rest), and drink a coffee.
"Have a coffee" means to drink a coffee.
Proposed Change
Change wording to "Have a coffee"
Additional Context
n/a

Fixed. Thanks!


Load secret stores before other kinds of components

This makes it so users won't see a warning like component X references a secret store that isn't loaded if the component was just loaded later

Note: users could still see the warning in case a secret store references secrets from another secret store that is loaded after. For example, if secret store A references a secret in store B (it will still work, but there'll be a warning). This doesn't apply to secrets that are loaded from the built-in K8s secret store, which is always loaded as the very first thing.

Fixes #5727

/ok-to-test


Changes in number guessing game that appear more interractive and looks like good

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
Fixes #3217

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[ ] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @suhanachaudhary ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Please review and check that changes that i do in number guessing game

Thank you  @suhanachaudhary , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀

Thank you  @suhanachaudhary , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Any Docs for ovpn-cli

Hello
I am really insterested in this procject.
However, i'm stuckted with build ovpn-cli.
Is there any docs for ovpn-cli??
I don't know how to build it Can i get some instructions for building this?
https://github.com/OpenVPN/ovpn-dco-win/tree/master/ovpn-cli

I initially made this tool for dco-win driver development, since openvpn support for dco-win wasn't obviously implemented yet. I haven't maintained it since a while, but I know it still builds (according to GitHub Actions) and probably works. You can run it on two machines (you could even use ovpn-cli from the Linux dco driver) and have an encrypted tunnel.
You can check GitHub Actions script for build steps. Also I am able to build it with VS2022 and latest SDK/WDK. What exactly doesn't work for you?

i just want to build it myself.
how to install asio.hpp??
Can you give me a advice?


django-mptt<0.9

Is there any good reason to limit django-mptt to <0.9?

django-mptt 0.9 supports Django 1.11 and 2.0 but removed tests of supporting 1.9, 1.10.
@czpython, check tests and move the django-mptt limit to <0.10 if everything is ok and release new minor version. Everybody wants to upgrade their django to 1.11 at least ;)

Sounds sensible
PR Added


Loading spinner when node is loading doesn't seem to be aligned

The loading spinner doesn't seem to be aligned when a node is loading:

To Reproduce
Steps to reproduce the behavior:

Go to the design review with the selected larger imodel.
Expand and collapse any node.
When a node is expanding, we can see that the loading spinner is not aligned.

Expected behavior
Spinner to be aligned with text and other icons.
Desktop (please complete the applicable information):

OS: Windows 10
Browse: mozilla firefox

@FlyersPh9 Can you have a look at the visual, my initial look into this points more towards the

and

icons being too high, in comparison to the full height of the text (Eye and spinner seems aligned together and to the text, but I may be using a bad method to validate that)

I'm trying to reproduce using macOS current & Brave v 1.51.118.  I used the devtools to apply a gray background on the row & red on all items within the row.

It looks like the eyeball & folder icon are misaligned but the text and expand / collapse arrow are aligned.  I am unable to color the spinner red because it disappears too soon, even with throttling set to "offline".

Hi @simasjar, the issue was actually in iTwinUI component, and this was fixed in 2.12.8 (ref)
You can use this new iTwinUI package directly in your application and it should fix your issue.


how to set ncyBreadcrumbLink

Frist I am new，I try to change ncyBreadcrumbLink ，because my leader dont want to  going back pages

Hi,
You can try with parent: 'state.name'
Regards


Option to build when using cmake.launchTargetPath

Early version supported building the target when started from launch.json. This can still be done by running a build when the binary is requested via cmake.launchTargetPath.

There's no way (AFAIK) to know the debug config you have just been launch with. The ext does not know why or who called cmake.launchTargetPath. You could read the launch.json yourself, but there might be multiple launch configs in the file, and I'm not sure what the debug adapters would do if we added our own option into their debug configuration objects.

The only solution would be to provide two commands launchTargetPath and launchTargetPathWithoutBuild. I would close this issue and integrated a feature like a second command on request by the users.


Store func ref in this instead of state

OK to merge

Coverage decreased (-0.4%) to 41.558% when pulling e65c648d5343371301ad1d2963635a6fe87cded4 on qingweibinary:qingwei/fix_event_listener into 92513e9aaf7df43fd56f9d60f93a49da55b690da on binary-com:master.


Boost python CMake changes

This addresses an issue where:
  find_package(Boost COMPONENTS pythonXY)

Creates a broken Boost::python target on some implementation which subsequently stops other searches. This breaks our technique of progressively searching for boost targets should one fail i.e:
  find_package(Boost COMPONENTS pythonXY)
  find_package(Boost COMPONENTS pythonX)
  find_package(Boost COMPONENTS python)

These changes should continue to support some of this behaviour but also exposes options for users to control how boost python is found. That being said, the boost cmake situation is a mess and I'd rather spend any time in this area trying to transition to pybind as fast as possible.

Fixes #1353


"Curator of the week" empty on WPs website

Good catch. I'll need to go through it today anyway. I'll update the XML then and see if it fixes the problem.

I know what happened. Mirella by accident copied the  tag from the next person to the end and then the XML was invalid. Should be updated within the next hour or so, I think.

Ah okay,
Yeah I was awake enough to see it wasn't working, but not awake enough to find the mistake in the XML file.
Good you are ;)


Commit blamed to generic email

After setting up Git on a new machine, I forgot to set my actual email to user.email. I made a commit, and it was blamed to<EMAIL_ADDRESS>Now, I am unable to sign the CLA in a PR, since some of my commits aren't blamed to my actual email.
Adding the generic email to my account hasn't fixed it.

it looks like you solved this issue on your own, should we close it?

how You solve this?


crash

Description
What steps will reproduce the problem?

What is the expected output? What do you see instead?
 Please paste the full error.

Closing because of lack of response.


Update github files

Ignore. Projects with the dir .github already did not worked well in the script.


Goodbye message when server does not response/appears offline

Hi there,
Firstly nice mod.
Secondly it would be nice if the bot would say goodbye or something when the minecraft server is not responding anymore.
I currently got a little problem, that the server at some point appears to be offline and then the bot instead of saying "Server not responding" or "Server might be offline. Please check", the bot goes off.
Would be a nice to have feature.
BR
Jan

Hi.
Thanks for the feedback. That one might be a little hard or impossible to do.
The bot, or any mod in general requires constant updates from the server. If the server is not responding anymore, it effectively means the mods don't continue to run anymore. That's why the bot turns off without saying anything, as there is nothing telling it to stay alive anymore and discord disconnects it for not responding.
Depending on how the server stops responding, depends on how this could work. If the server just stays running, but does nothing (not responding basically), the behavior you mentioned will always be the expected behavior.
If the server actually crashes, but stays running, there might be a way to hook into that and have the bot deliver one last message before the server dies.  You created the mod and not the discord bot.
The server appears to be running just fin but the whole machine seems to be of the internet. So there is no server crash or so to help you out.
I think you can close this issue then if you want.

Well the discord bot is technically the mod lol, but if the machine itself goes offline (loses internet connection), then the bot can't communicate with discord and will go offline as well.
However, when the machine does regain internet connection, the bot is supposed to come back online. If it doesn't do that, then it is a bug


#245 non-personalized view for assignments

#245 .
This PR has one DB column update and cron job query update. Although it was not greatly needed but I felt it will be cleaner that way.
Currently anybody who has uniqname can access the tool and who ever figured out the course_number can access all the Views student dashboard has to offer. This is not just true for Assignment view and this PR is not handling that. That would be a different Issue.

Looks good to me, I like the cleanup here. I think we should change the format of the SQL in views to fstrings and triple quotes like cron.py file. But it probably should be removed from the views entirely. Good first step toward that cleanup.


Add TextToSpeech v1 pom.xml and java files

TTS v1 was recently introduced into googleapis/googleapis.
This takes the place of the weekly batch refresh.

PTAL

@garrettjonesgoogle TTS v1beta1 already exists, and there is a README.md file there in google-cloud-texttospeech. Should there be another README.md for just this new version?
I did update the google-cloud-texttospeech/README.md to point to the new v1 doc instead of v1beta1.

PTAL

@andreamlin  Not sure whether this line needs updating ? https://github.com/GoogleCloudPlatform/google-cloud-java/blob/master/google-cloud-clients/pom.xml#L754

@neozwu good call, just added that in.


Check underscore substitutions

This may be connected to issue #50, which was (temporarily) dealt with in #51

Developmental stages and tissue names CAN NOT HAVE SPACES because the Lucy index try to find them as independent words and return wrong results

There is a bug in the bar plot code that removes the underscores and break things later (heatmap)


fix: pages alternate lang code link issue fixed

this fixes #6 and #7

Thanks a lot for this @abhranil26 👏 I will gladly review it asap


Add authors section to docs page

@kris-brown I think you have to click merge. I don't have authorization. Thanks!


[SST 2 + Astro] Initial deployment happy path is broken

The happy path for initial deployment is in a non-working state. Below are the details of the setup as well as the steps to reproduce the various issues.
System Config
OS: macOS 12.6.2
Node: v18.12.1
Pkg installer: pnpm
Package Versions
dependencies:
astro 2.0.2

devDependencies:
astro-sst 2.0.0-rc.18
aws-cdk-lib 2.55.0
constructs 10.1.156
sst 2.0.0-rc.56

Project Setup
$ pnpm create astro@latest (default "yes" to all questions)
$ cd sst-test
$ pnpx create-sst@rc (default "yes" to all questions)

Failure Point 1
$ pnpm sst:deploy

This fails and results in:
Error: Failed to build function "dist/server/entry.handler"

Trace: Error: Failed to build function "dist/server/entry.handler"
    at file:///Users/samh/sst-test/node_modules/.pnpm/sst@2.0.0-rc.56/node_modules/sst/constructs/Function.js:190:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at process.<anonymous> (file:///Users/samh/sst-test/node_modules/.pnpm/sst@2.0.0-rc.56/node_modules/sst/cli/sst.js:54:17)
    at process.emit (node:events:525:35)
    at process.emit (node:domain:489:12)
    at process._fatalException (node:internal/process/execution:149:25)
    at processPromiseRejections (node:internal/process/promises:288:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)

Thanks to Andy Kenward's help, this can be worked around by creating an .npmrc file with these contents:
node-linker=hoisted

Failure Point 2
$ pnpm sst:deploy

It gets further this time thanks to the workaround above, but still fails:
✔  Building...

|  Site site/ServerCache AWS::CloudFront::CachePolicy CREATE_COMPLETE
|  Site site/AwsCliLayer AWS::Lambda::LayerVersion CREATE_COMPLETE
|  Site site/S3Uploader/ServiceRole AWS::IAM::Role CREATE_COMPLETE
|  Site Custom::S3AutoDeleteObjectsCustomResourceProvider AWS::IAM::Role CREATE_COMPLETE
|  Site site/ServerFunction/ServiceRole AWS::IAM::Role CREATE_COMPLETE
|  Site site/S3Handler/ServiceRole AWS::IAM::Role CREATE_COMPLETE
|  Site site/CloudFrontInvalidator/ServiceRole AWS::IAM::Role CREATE_COMPLETE
|  Site CustomResourceHandler/ServiceRole AWS::IAM::Role CREATE_COMPLETE
|  Site CustomResourceHandler AWS::Lambda::Function CREATE_FAILED
|  Site site/S3Bucket AWS::S3::Bucket CREATE_FAILED
|  Site LogRetentionaae0aa3c5b4d4f87b02d85b201efdd8a/ServiceRole AWS::IAM::Role CREATE_FAILED
|  Site site/CloudFrontInvalidator/ServiceRole/DefaultPolicy AWS::IAM::Policy CREATE_FAILED
|  Site site/S3Bucket AWS::S3::Bucket DELETE_COMPLETE
|  Site site/CloudFrontInvalidator/ServiceRole/DefaultPolicy AWS::IAM::Policy DELETE_COMPLETE
|  Site site/ServerCache AWS::CloudFront::CachePolicy DELETE_COMPLETE
|  Site Custom::S3AutoDeleteObjectsCustomResourceProvider AWS::IAM::Role DELETE_COMPLETE
|  Site site/S3Uploader/ServiceRole AWS::IAM::Role DELETE_COMPLETE
|  Site site/ServerFunction/ServiceRole AWS::IAM::Role DELETE_COMPLETE
|  Site LogRetentionaae0aa3c5b4d4f87b02d85b201efdd8a/ServiceRole AWS::IAM::Role DELETE_COMPLETE
|  Site site/AwsCliLayer AWS::Lambda::LayerVersion DELETE_COMPLETE
|  Site site/S3Handler/ServiceRole AWS::IAM::Role DELETE_COMPLETE
|  Site site/CloudFrontInvalidator/ServiceRole AWS::IAM::Role DELETE_COMPLETE
|  Site CustomResourceHandler AWS::Lambda::Function DELETE_COMPLETE
|  Site CustomResourceHandler/ServiceRole AWS::IAM::Role DELETE_COMPLETE
⠼  Site site/S3Bucket AWS::S3::Bucket DELETE_IN_PROGRESS
⠋  Site site/CloudFrontInvalidator/ServiceRole/DefaultPolicy     DELETE_IN_PROGR
AWS::IAM::Policy                                                 ESS

✖  Errors
   Site
   CustomResourceHandler: Resource handler returned message: "The role defined for the function cannot be assumed by Lambda. (Service: Lambda, Status Code: 400, Request ID: 14f0d6fa-416e-4435-b389-47399e69a1ce)" (RequestToken: 5d1bd98e-b189-5b6e-38c6-8f2305c8d9a6, HandlerErrorCode: InvalidRequest)

Very strange. On a second sst:deploy attempt right after the failure point 2 above, it worked. I didn't change anything in the code or config. Below is the full output:

Expand
✔  Building...

|  Site site/ServerCache AWS::CloudFront::CachePolicy CREATE_COMPLETE
|  Site site/AwsCliLayer AWS::Lambda::LayerVersion CREATE_COMPLETE
|  Site LogRetentionaae0aa3c5b4d4f87b02d85b201efdd8a/ServiceRole AWS::IAM::Role CREATE_COMPLETE
|  Site site/S3Uploader/ServiceRole AWS::IAM::Role CREATE_COMPLETE
|  Site Custom::S3AutoDeleteObjectsCustomResourceProvider AWS::IAM::Role CREATE_COMPLETE
|  Site site/CloudFrontInvalidator/ServiceRole AWS::IAM::Role CREATE_COMPLETE
|  Site site/ServerFunction/ServiceRole AWS::IAM::Role CREATE_COMPLETE
|  Site site/S3Handler/ServiceRole AWS::IAM::Role CREATE_COMPLETE
|  Site CustomResourceHandler/ServiceRole AWS::IAM::Role CREATE_COMPLETE
|  Site site/S3Bucket AWS::S3::Bucket CREATE_COMPLETE
|  Site CustomResourceHandler AWS::Lambda::Function CREATE_COMPLETE
|  Site LogRetentionaae0aa3c5b4d4f87b02d85b201efdd8a/ServiceRole/DefaultPolicy AWS::IAM::Policy CREATE_COMPLETE
⠴  Site site/ServerCache AWS::CloudFront::CachePolicy CREATE_IN_PROGRESS
|  Site Custom::S3AutoDeleteObjectsCustomResourceProvider AWS::Lambda::Function CREATE_COMPLETE
⠴  Site site/ServerCache AWS::CloudFront::CachePolicy CREATE_IN_PROGRESS
|  Site site/CloudFrontInvalidator/ServiceRole/DefaultPolicy AWS::IAM::Policy CREATE_COMPLETE
⠴  Site site/ServerCache AWS::CloudFront::CachePolicy CREATE_IN_PROGRESS
|  Site site/ServerFunction/ServiceRole/DefaultPolicy AWS::IAM::Policy CREATE_COMPLETE
|  Site site/S3Uploader/ServiceRole/DefaultPolicy AWS::IAM::Policy CREATE_COMPLETE
|  Site LogRetentionaae0aa3c5b4d4f87b02d85b201efdd8a AWS::Lambda::Function CREATE_COMPLETE
|  Site site/CloudFrontInvalidator AWS::Lambda::Function CREATE_COMPLETE
|  Site site/ServerFunction AWS::Lambda::Function CREATE_COMPLETE
|  Site site/S3Uploader AWS::Lambda::Function CREATE_COMPLETE
|  Site site/ServerFunction/FunctionUrl AWS::Lambda::Url CREATE_COMPLETE
|  Site site/ServerFunction/LogRetention Custom::LogRetention CREATE_COMPLETE
|  Site site/ServerFunction AWS::Lambda::Permission CREATE_COMPLETE
|  Site site/S3Handler/ServiceRole/DefaultPolicy AWS::IAM::Policy CREATE_COMPLETE
|  Site site/S3Handler AWS::Lambda::Function CREATE_COMPLETE
|  Site site/S3Deployment Custom::SSTBucketDeployment CREATE_COMPLETE
|  Site site/Distribution/Origin2/S3Origin AWS::CloudFront::CloudFrontOriginAccessIdentity CREATE_COMPLETE
|  Site site/S3Bucket/Policy AWS::S3::BucketPolicy CREATE_COMPLETE
|  Site site/S3Bucket/AutoDeleteObjectsCustomResource Custom::S3AutoDeleteObjects CREATE_COMPLETE
|  Site site/Distribution AWS::CloudFront::Distribution CREATE_COMPLETE
|  Site site/CloudFrontInvalidation Custom::SSTCloudFrontInvalidation CREATE_COMPLETE
|  Site site/Parameter_url AWS::SSM::Parameter CREATE_COMPLETE
⠇  Site site/ServerCache AWS::CloudFront::CachePolicy CREATE_IN_PROGRESS
⠼  Site site/AwsCliLayer AWS::Lambda::LayerVersion CREATE_IN_PROGRESS
⠼  Site site/ServerFunction/FunctionUrl AWS::Lambda::Url CREATE_IN_PROGRESS
⠋  Site site/ServerFunction/LogRetention Custom::LogRetention CREATE_IN_PROGRESS
⠹  Site site/S3Deployment Custom::SSTBucketDeployment CREATE_IN_PROGRESS
⠼  Site site/Distribution/Origin2/S3Origin      CREATE_IN_PROGRESS
AWS::CloudFront::CloudFrontOriginAccessIdentity
⠼  Site site/S3Bucket/Policy AWS::S3::BucketPolicy CREATE_IN_PROGRESS
⠏  Site site/S3Bucket/AutoDeleteObjectsCustomResource CREATE_IN_PROGRESS
Custom::S3AutoDeleteObjects

✔  Deployed:
   Site
   url: https://xx.cloudfront.net

Removal of stack (pnpm sst remove) is also non-functional:
Error: The stack output "url" is undefined

Trace: Error: The stack output "url" is undefined
    at file:///Users/samh/sst-test/node_modules/.pnpm/sst@2.0.0-rc.56/node_modules/sst/constructs/Stack.js:164:23
    at Array.forEach (<anonymous>)
    at EmptyStack.addOutputs (file:///Users/samh/sst-test/node_modules/.pnpm/sst@2.0.0-rc.56/node_modules/sst/constructs/Stack.js:161:30)
    at EmptyStack.Site (/Users/samh/sst-test/sst.config.ts:14:17)
    at stack (file:///Users/samh/sst-test/node_modules/.pnpm/sst@2.0.0-rc.56/node_modules/sst/constructs/FunctionalStack.js:20:35)
    at App.stack (file:///Users/samh/sst-test/node_modules/.pnpm/sst@2.0.0-rc.56/node_modules/sst/constructs/App.js:495:16)
    at Object.stacks (/Users/samh/sst-test/sst.config.ts:12:9)
    at Module.synth (file:///Users/samh/sst-test/node_modules/.pnpm/sst@2.0.0-rc.56/node_modules/sst/stacks/synth.js:52:20)
    at async file:///Users/samh/sst-test/node_modules/.pnpm/sst@2.0.0-rc.56/node_modules/sst/cli/commands/remove.js:27:16
    at async Object.handler (file:///Users/samh/sst-test/node_modules/.pnpm/sst@2.0.0-rc.56/node_modules/sst/cli/commands/remove.js:22:22)
    at process.<anonymous> (file:///Users/samh/sst-test/node_modules/.pnpm/sst@2.0.0-rc.56/node_modules/sst/cli/sst.js:54:17)
    at process.emit (node:events:525:35)
    at process.emit (node:domain:489:12)
    at process._fatalException (node:internal/process/execution:149:25)
    at processPromiseRejections (node:internal/process/promises:288:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)

Happy to report that all is well now!


GH-35067: [JavaScript] toString for signed BigNums

What changes are included in this PR?
Closes #22932
Basically, signed negative numbers were displayed as very large positive numbers.
Are these changes tested?
Yes, I've also added tests for bn.ts (BigNum) that was not tested before.
Are there any user-facing changes?
Negative numbers stored in BigNum will now be displayed as negative numbers instead of very large positive numbers.
Note that this change also affects decimals, because they are stored in BigNum as signed numbers. Decimals still don't convert to string correctly, because inserting the decimal dot is not implemented. Ref #28804.

Closes: #35067

I've spent a little time trying to get tests to pass, but something strange is happening:
the bn-tests.ts are failing only on -t es5 -m umd. I've debugged it to the finding that in this line, a.signed is false, even though I've constructed a signed number or a decimal (which is signed).
It may be a problem with how these prototypes are assigning to each other, but that is beyond me.

@aljazerzen 99% sure closure is mangling too aggressively, and we need to do if(!a['signed']) to defeat it.

@domoritz can you review this? @trxcllnt can it be merged with only one approval?

One review is fine. We can merge this.

Great. Please go ahead, as I don't have the permissions.

Thank you. I had to get back to my computer to use the merge script.


Cannot use context menu to create estimation session

When selecting from the backlog a single story or a group of stories. using the context menu and selecting to create a session does not work.

We are using

The Estimation opens with no details.
Not sure if it is related, but in the debugger I can see several errors one of which

Creating a session using the "+Create Session" button on the page works if you select a query or sprint.

Sorry - this exists as item 221


DBs and Tables are not updating after create

When you run a create database or create table, the created object doesn't show at the sidebar, you have to reload the complete app!

I think there is no database gui client (i.e. MySQL Workbench, pgAdmin) which shows newly created database/table without manually clicking on reloading data, but I agree we can try to implement this. Or at least put 'refresh button' which would reload databases and tables (like other clients do)

Even the auto refresh looking a best solution. We can not implement that because there is not a properly way to detect the query type in nodejs. Regex is not a good option and the best solution would be using AST of the query (which there is not any good one available in nodejs - is the same problem described here).
So the current best and simple solution is including a refresh button.

Random thought, on sql execute IF SQL string contains keyword "Create" then run the refresh menu function. I might be oversimplifying the issue.
i.e
if ( string.indexOf('create') > -1 ||  string.indexOf('Create') > -1)       refreshLeftMenu();

Sorry. In this case there is no simple solution. Your suggestions would not work with many situations 😢
INSERT INTO mytable VALUES ('I have created something today');

or
-- query created at 11/09/2011
SELECT * FROM mytable;

or
SELECT id, name, createdAt FROM people;

or
SELECT * FROM creations;

These are only the few simple cases I have just thought about right now. I'm sure there are others even more complex that a string "search" or even Regex would not work. Only a AST of the query would give us the full understanding of the query to be able to "react" over the content.

Your right. My idea would have unnecessarily done a refresh. I noticed there are a few AST related npm packages that we might be able to leverage. This is a little over my head, so I'm just going to follow along :)

@BornaP oh yes it is. I use Sequel Pro for OS X and it show stuff just after the query run out!

I think to begin a simple solution would be to add a refresh icon in the database, so we fetch the data once again.
It will not be automatic, but at least would give the support to refresh, and it might be a feature useful for other scenarios (like multiple users creating view/tables in same database) it would allow you to refresh and get the new things that others are generating...
And it also would be simple, and it will avoid user to have to close connection and reopen to get the new table/view/etc...
So I think it would be a good begin, afterwards we can check, some AST or another approach to handle those scenario where CREATE statements are generated through sqlectron...
What do you think guys?

may i give a go for it to implement a refresh icon what do you think @maxcnunes @BornaP ?

Sure, give it a go! :)

TLDR I guess will be possible to implement this auto reloading feature. I am working on it.
Since having a AST would give us some good analyse power over the executed queries. I tried find out some good sql-parser in node. But every parser I found is not fully implemented. Then I decided trying to create a bind from some existing one from C. But that would require creating a bind for each database client and some of them would not be possible because are private source (mssql). So my next attempt was writing a sql parser my self in node. But after some hard working and fun I just realised would take some free time that I am not really interesting in investing right now. So my last attempt was writing a sql parser only for our main needs. Which is identify the query statement types (e.g. Insert, Select, CreateTable, and etc.). sql-query-identifier is the result of this idea.
The postgres client already returns the query identifier (I guess is because of that the Postico hava that feature to auto reload tables after creating them). So my main idea is add to sqlectron-core this new feature returning the query type for each executed statement. sql-query-identifier will be used as fallback for every database which does not return the statement type (I guess only postgres will not use it).

Wow, that's some great news! The whole idea that you went on writing your own SQL parser is just impressive itself, and now that you have working solution that's just brilliant :) Bem feito @maxcnunes ! (hope I got it right haha)

Closing this issue since have been implemented on #156 and #160.


fixed #98

set all Exec.StdOutEncoding='utf-8'
Problems:
1.When the solution is in a non-ASCII character set path, the solution cannot be compiled, and the exception message is:"System.IO.DirectoryNotFoundException"

2.When there are non-ASCII characters in the git commit information or branch name or tag, there are garbled characters in the automatically generated ThisAssembly.g.cs

After analysis, it was found that the above-mentioned problems were caused by the incorrect default encoding used by msbuild.exe or dotnet msbuild when executing the Exec task in Target.
Solution：
Specify the output encoding of all Target->Exec tasks as 'utf-8',append code to Exec:
StdOutEncoding='utf-8'

Maybe amend the commit and add a bit more explanation on why this is necessary and what it fixes? (for posterity :)).
Thanks a lot for looking into this! Will merge as soon as the commit message is a bit clearer 💯

Maybe amend the commit and add a bit more explanation on why this is necessary and what it fixes? (for posterity :)).

hi,
I made changes to the commit message,please review
I'm sorry, my English is not good :)

Hi @pedoc , the commit still shows plainly as:

You should amend the commit, and provide a commit that explains what it achieves. This is a good writeup on what makes a good commit message.
Thanks!

Oh, I think you're editing the pull request title and description, but that's not changing the commit itself. You'd need to push an updated commit to achieve that

@kzu  Sorry I didn’t understand what you meant at first, now it’s processed. :)

Awesome 👍 . Thanks!


provide better error message for .stone scripts when the named stone isn't actually running

Right now ... this is the "error message"
rogue:stones>versionReport.stone -- test_superdoit_340
superdoit_tpz: /home/dhenrich/rogue/_homes/rogue/_issue_260/shared/gemstone/repos/superDoit/bin/../gemstone/superdoit_boot_2.tpz ini: /home/dhenrich/rogue/_homes/rogue/_issue_260/shared/gemstone/repos/superDoit/bin/../gemstone/topazini
Buffered output from initialization file /home/dhenrich/rogue/_homes/rogue/_issue_260/shared/gemstone/repos/superDoit/bin/../gemstone/topazini
topaz> # used to run the supderDoit scripts in versions that predate the topaz -S option
topaz> #
topaz> output push /dev/null only
topaz> input $gemstoneDir/superdoit_boot_debug_2.tpz
topaz> run
RUN can't be used prior to logging in.
... after error, skipping input source down to %
SKIPPED above method/doit due to error preceeding it
topaz> exit

closed in favor of #19 (test suite specifics)


Shebang handling

At the moment this PR merges only the current master into shebang-handling.
See #47

A bit hard to read this PR. Could we rebase the changes on top of master instead of merging?

TODO

[ ] review (I am beginner with TS-specific things)
[ ] allow to pass glob pattern in another way than using an environment variable
[ ] more tests
[ ] allow the user to disable scanning working dir against bash/sh shebang
[ ] give hasBashShebang only the first line of the file (do not match the entire content)

Sorry for stalling here. I've investigated the issue, and it turns out that all bash files (that VS Code can detect) are handled just fine. We don't need to read all the files in a project–unless we want to do just to definition across files (required more work).

It seemed to be natural that the results of analyzeing the rest of scripts are accessible for completion and jumping. Indeed: at the moment there is no need to make (almost?) unusable index.

It seemed to be natural that the results of analyzeing the rest of scripts are accessible for completion and jumping. Indeed: at the moment there is no need to make (almost?) unusable index.

My mistake. It is indeed used for indexing. https://github.com/mads-hartmann/bash-language-server/issues/47#issuecomment-593313329 👍

@przepompownia thanks for your work here. We now handle most of the cases here – except for reading all files.
I'm reluctant to implement parsing all the files in a project, that shouldn't be necessary. We might consider adding parsing all files without extensions though. :)


Feature Request: isEmpty | isNotEmpty

Can we have methods that directly tell us whether the DataFrame is empty or not instead of checking the rowCount?
Thank you so much in advance.

I can implement isEmpty if you are interested in this feature. As far as I can see it should be added to DataFrame.java with a corresponding tests in BasicDataFrameTest.java.

if you could, I would really appreciate. will we have isNotEmpty as well?

@carslan: Can you please verify that this implementation works for you?

sincere, apologies for so late response. it works as expected. thank you so much.


Check if PAGE_SIZE is already defined.

Fixes compile on alpine linux where PAGE_SIZE is already defined in /usr/include/bits/limits.h (and included via /usr/include/limits.h)

Thank you for the fix!


Incorporate use case tutorials

PR Checklist

[X] Referenced issue is linked (#642)
[X] Documentation in docs is updated

Description of changes

Added use case tutorials to the tutorial gallery
Fixed a bug in the DE base class: it was using adata.layer (doesn't exist) instead of adata.layers, causing the code to fail whenever the layer parameter was specified

The Dialogue part is still missing from the Zhang tutorial, but I'll create a separate PR for that, as I'll have to run that part on the cluster.

Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 65.55%. Comparing base (6e3ca9c) to head (eff67ef).
Report is 2 commits behind head on main.

Files with missing lines
Patch %
Lines

...ertpy/tools/_differential_gene_expression/_base.py
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #665   +/-   ##
=======================================
  Coverage   65.55%   65.55%
=======================================
  Files          47       47
  Lines        6105     6105
=======================================
  Hits         4002     4002
  Misses       2103     2103

Files with missing lines
Coverage Δ

pertpy/metadata/_cell_line.py
49.80% <ø> (ø)

...ertpy/tools/_differential_gene_expression/_base.py
32.32% <0.00%> (ø)


Tweak rendering quality property hint strings for consistency

Include a performance indication for all hints, not just for non-default values.
Fix leading/trailing whitespace in some property hints.

Thanks!


Tail-wag animation doesn't end smoothly on Chrome

It seems that Chrome handles CSS animations differently than Firefox does, causing the animation to end improperly:
https://gfycat.com/UnfinishedAdolescentGiantschnauzer
How it should look (and how it looks with the latest version of Firefox):
https://gfycat.com/HeartyShallowCobra
I'm not sure about other browsers; if someone could check Safari that would be appreciated.

Safari 12.1 https://gfycat.com/severalvastgrub
Firefox 66 https://gfycat.com/concretedecentarcticduck
Chrome 73 https://gfycat.com/illequatorialhedgehog
Looks a bit odd in all of them to me. Note in the Chrome one how the bird reverts back correctly unless it's reached "full flight" 😄

Fixed and merged in to master https://github.com/wagtail/wagtail/commit/74ce4adb6b4e206861d74d01bee93cea42b56c5f
@denizdogan  - thanks so much for fixing this, great to get this one in :D


[Bug] Discover Characteristics works on iOS, but not Android

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[X] iOS
[X] Android
[ ] UWP
[ ] .NET Standard

Version of Library
6.2.6
Version of OS(s) listed above with issue
iOS 12
Android 8.0.0
Steps to Reproduce

Create app that has the code shown below
Run on iOS the discover callback works
Run on Android the discover callback never gets called

Expected Behavior
Works on iOS, not on Android
Actual Behavior
Works on both
Here is my code:
`
if (!_connected)
Item.Device.Connect();
                            _ = Item.Device.WhenAnyCharacteristicDiscovered().Subscribe(async characteristic =>
                            {
                                if (characteristic.ToString().ToUpper().Equals("EB0A0002-AF09-4B25-B6AC-CD1ACA7D42E2"))
                                {
                                    await characteristic.Write(new byte[] { 0xFF });
                                    _connected = false;
                                }
                            });`

Connect is a request operation.  It could happen now or 30 mins from now.
Please take some time to review the samples and documentation before filing something.  This is not a support site.

Ok. Sorry for that. I was following an example, but maybe it was wrong. I will check the samples closer.

I found everything I needed and now everything is working great on iOS and Android.
Sorry again for not paying better attention before submitting this issue.
You are awesome and thank you a million for the plugin.


add conditional compilation details

since I just figured out how this works, might as well make it easier for the next person.

Thanks!


php 7 laravel 5.6 install error

this project works correctly in laravel 5.5. not working in laravel 5.6
please help how to fix this problem
$ composer require php-ffmpeg/php-ffmpeg
Using version ^0.11.1 for php-ffmpeg/php-ffmpeg
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Conclusion: don't install php-ffmpeg/php-ffmpeg v0.11.1-pl-1
- Conclusion: remove evenement/evenement v3.0.1
- Installation request for php-ffmpeg/php-ffmpeg ^0.11.1 -> satisfiable by php-ffmpeg/php-ffmpeg[v0.11.1, v0.11.1-pl-1].
- Conclusion: don't install evenement/evenement v3.0.1
- php-ffmpeg/php-ffmpeg v0.11.1 requires evenement/evenement ^2.0 || ^1.0 -> satisfiable by evenement/evenement[v1.0.0, v1.1.0, v2.0.0, v2.1.0].
- Can only install one of: evenement/evenement[v1.0.0, v3.0.1].
- Can only install one of: evenement/evenement[v1.1.0, v3.0.1].
- Can only install one of: evenement/evenement[v2.0.0, v3.0.1].
- Can only install one of: evenement/evenement[v2.1.0, v3.0.1].
- Installation request for evenement/evenement (locked at v3.0.1) -> satisfiable by evenement/evenement[v3.0.1].
Installation failed, reverting ./composer.json to its original content.

duplicate of #470


Relic

What does this PR do?

Fixes # (issue)
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests? [not needed for typos/docs]
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[x] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

@shogi880 @ananyahjha93 can you pls clarify what is this contribution about?
@shogi880 I see some issue, you are changing almost all repo ~250 files

@shogi880 any update here? :rabbit:
cc: @SeanNaren otherwise I am for closing it... :confused:

Hi @Borda
Sorry for the delay.
I'm new to GitHub and programming, so I think I've included a lot of log files.
I'll close it and request again after I clean it up.

btw, really thanks for this perfect library that is organized by you.


DNS rebinding failed on Ubuntu 20.04.1 LTS

OS: Ubuntu 20.04.1 LTS
I used the default version (79.0) of Firefox at first, and then I tried to upgrade Firefox to the latest version (95.0.1), but it failed.
It seems that the local service is directly accessed, and it is a 404 directly.
I tried <IP_ADDRESS> again and it failed

This is the dns query result

I tried a lot of this without rebinding successfully

Hi
I just successfully tried the "First then second" and "Multiple answers" rebinding strategies on Ubuntu 21.10 with Firefox 95.0.2.
Did you verify that the target service is vulnerable to DNS rebinding (https://github.com/nccgroup/singularity/wiki/Testing-for-Vulnerable-Services)?
I suggest to try the default "First then second" rebinding strategy first as it's the most reliable.
Did it work with Firefox 79.0?
If you still have issues, please provide some more information about the target service such as the output of curl -v --header "Host: attacker.com" http://<IP_ADDRESS>:8000/ and of curl -v http://<IP_ADDRESS>:8000/

Sorry, I found the reason, it's my network problem


provider: add the unused tag to the gettable and settable function argument.

Some builds care about function arguments being used or tagged as not.

Was this a build breaker - i.e. Is this urgent?

Can you change the commit to not use paramater :)

Oh, in the commit message.  It's fixed.

This pull request is ready to merge

Merged to master.  Thanks for the review.


Preliminary Section Card

Zeplin
DOD:

[x] A card that displays section index, content of first suggestion
[x] The section object should be passed as a prop
[x] Add buttons (same as zeplin)
[x] Disable back arrow (zee zeplin) when currently displayed suggestion is the first one
[x] Disable forward arrow when currently displayed suggestion is the last one

@yishain11 is this ready for PR?

@avirankatz Need to take into consideration (now or later) versions display order in section card on agreement page and on section page:
The parameter for sorting is by voting ratio -

The most agreed upon version, i.e. the version that it's pro voters number minus it's con voters number is the highest, should be displayed first.
The least agreed upon version, i.e. the version that it's pro voters number minus it's con voters number is the lowest, should be displayed last.
For versions that have the same voting ratio, sorting should be according to creation time, descending (i.e. newest first).
If there is an approved version, it should be positioned as first (on the left in LtR, on the right in RtL), but it should not be displayed by default. Approved version will be displayed only after user click on back arrow.

Please confirm that it is clear.

@Aharon-Porath Yes, it's clear.
However, if there's going to be some scoring field for suggestions (for the purpose of the consensus meter), won't it be useful for sorting? i.e. first suggestion is the one which has the highest score

@Aharon-Porath Yes, it's clear. However, if there's going to be some scoring field for suggestions (for the purpose of the consensus meter), wouldn't it also be useful for sorting? i.e. first suggestion is the one which has the highest score

Yes, it could be more simple.
As a general rule, the requirement for sorting/displaying suggestion (section version on a vote) is - the version that is the closest to be approved should be the most accessible to the user.
And if I will phrase it as a user story:
As a user I want to see first the versions with the highest chances to be approved, so I can vote for the ones that I agreed with and promote them to enter the draft, and to object to the ones that I disagree with to prevent them to enter the draft.


fix: useCookie default value as default state

Thanks! But I did that on purpose because we might want to add new props to persistState later. With the default value to the cookie, it will break the existing users (those who has cookies already), that can cause the props missing for them


[boost-spirit] build failure

Host Environment

OS: Windows 7
Compiler: MSVC 16.5

To Reproduce
Steps to reproduce the behavior:
./vcpkg install boost-spirit
Failure logs
PS C:\vc\vcpkg> ./vcpkg install boost-spirit
Your feedback is important to improve Vcpkg! Please take 3 minutes to complete our survey by running: vcpkg contact --survey
The following packages will be built and installed:
    boost-spirit[core]:x86-windows
Starting package 1/1: boost-spirit:x86-windows
Building package boost-spirit[core]:x86-windows...
Warning: abi keys are missing values:
    boost-algorithm
    boost-filesystem
    boost-foreach
    boost-iostreams
    boost-lexical-cast
    boost-locale
    boost-math
    boost-phoenix
    boost-proto
    boost-range
    boost-regex
    boost-thread
    boost-unordered

-- Using cached C:/VC/vcpkg/downloads/boostorg-spirit-boost-1.71.0.tar.gz
-- Using source at C:/VC/vcpkg/buildtrees/boost-spirit/src/ost-1.71.0-80737223c6
-- Packaging headers
-- Packaging headers done
-- Using cached C:/VC/vcpkg/downloads/boost_LICENSE_1_0.txt
-- Installing: C:/VC/vcpkg/packages/boost-spirit_x86-windows/share/boost-spirit/copyright
-- Performing post-build validation
There should be no empty directories in C:\vc\vcpkg\packages\boost-spirit_x86-windows
The following empty directories were found:

    C:/vc/vcpkg/packages/boost-spirit_x86-windows/include/boost/spirit/home/karma/nonterminal

If a directory should be populated but is not, this might indicate an error in the portfile.
If the directories are not needed and their creation cannot be disabled, use something like this in the portfile to remove them:

    file(REMOVE_RECURSE ${CURRENT_PACKAGES_DIR}/a/dir ${CURRENT_PACKAGES_DIR}/some/other/dir)

Found 1 error(s). Please correct the portfile:
    C:\vc\vcpkg\ports\boost-spirit\portfile.cmake
-- Performing post-build validation done
Error: Building package boost-spirit:x86-windows failed with: POST_BUILD_CHECKS_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: boost-spirit:x86-windows
  Vcpkg version: 2019.09.12-nohash

Additionally, attach any relevant sections from the log files above.

Note it doesn't happen on a fresh install.. could it be caused by cruft left from previous port versions?

@OlafvdSpek, thanks for reporting this issue!
However, I can't repro this issue, it's hard to say what caused the problem. From the failure that spirit/home/karma/nonterminal is empty, actually it should contains some headers, it looks you used cached boost-spirit source, it might due to the headers removed in cached source.

Are you saying there's a bug in the vcpkg caching system?

It's not a bug, I mean if you modified boost-spirit build tree, it will affect build results when you try to build it again.

I'm pretty sure I didn't do that.

Could you double confirm if C:/VC/vcpkg/buildtrees/boost-spirit/src/ost-1.71.0-80737223c6/include/boost/spirit/home/karma/nonterminal is empty?

No, I deleted the entire vcpkg instance once I noticed installing from scratch worked.
Feel free to close if you think it's a one-time issue.

Since we can't repro it, closed it now, and feel free reopen it if you encounter it again.


Ferdi 5.6.0 opens slack calls in default browser

Bug description:

I've switched from 5.5.0 to the beta and nightly in order to solve the bug with Microsoft Teams in https://github.com/getferdi/ferdi/issues/475#issuecomment-848918466 and I'm now observing a different issue, with Slack. By the way, the issue in https://github.com/getferdi/ferdi/issues/1457 may be related.
On Windows 10, with Microsoft Edge as default browser:

Ferdi 5.0.0 nicely opens Slack calls inside itself:

Ferdi 5.6.0-beta.6 unexpectedly launches default browser and opens Slack calls there

Ferdi 5.6.0-nightly.48 also launches default browser and opens Slack calls there

Environment:

Operating System: Windows 10 (20H2)

Ferdi Version: 5.5.0, 5.6.0-beta.6 and 5.6.0-nightly.48

Server:  no idea, but I'm logged in:

Same window comes up in ferdi as well (OS Arch Linux) . As soon as I make a call slack "Did you start this call from slack"  For joining the call I need to cancel and then join with the link inside the chat.

I can confirm that it is happening

I have noticed if I keep my "Left Shift" key pressed and making a click even into button, so it opens properly as a Ferdi New Window.
So "Left Shift" + Click on the button is an actual workaround (or maybe predesigned on purpose).

"left shift"+click does not open the Slack call (open channel call / direct call) for me at all. Channel huddles are opened in Ferdi
Normal clicking opens the external browser which is usable of course but not optimal.
OS: Manjaro, Ferdi: 5.6.3


UseDotNet@2 Does Not Propogate SDK Version to All Downstream Tasks When Using .NET 7

Question, Feature or Bug?
Possible Bug
Task Names

UseDotNet@2
DotNetCoreCLI@2

Environment

Server: Azure Pipelines hosted agent using windows-latest
SDK version: 7.0.x

Issue Description
After upgrading our pipeline to use .NET 7, attempts to run restore via DotNetCoreCLI@2 are failing. Based on the task logs, it appears that restore is still using the .NET 6 SDK, despite setting SDK version number to 7.0.x in an upstream call to UseDotNet@2.
Pipleine YML
pool:
  vmImage: 'windows-latest'

variables:
  build.configuration: 'Release'
  build.project: $(build.name).sln
  projects: '**/*.csproj'
  dotNetCoreSDK: 7.0.x

steps:
- task: UseDotNet@2
  inputs:
    packageType: sdk
    version: $(dotNetCoreSDK)

- task: DotNetCoreCLI@2
  inputs:
    command: restore
    projects: '$(projects)'
    feedsToUse: 'select'
    vstsFeed: 'xxxx'
    versioningScheme: byBuildNumber

...

Project File
Based on the restore task logs, this is the one project that fails to build. Worth noting: restore runs error-free on the solution locally via the CLI, and uses .net7 throughout.
<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>net7.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Ardalis.ApiEndpoints" Version="4.0.1" />
    <PackageReference Include="Ardalis.ListStartupServices" Version="1.1.4" />
    <PackageReference Include="Blazorise.Bootstrap" Version="1.0.6" />
    <PackageReference Include="Blazorise.Charts" Version="1.0.6" />
    <PackageReference Include="Blazorise.Icons.FontAwesome" Version="1.0.6" />
    <PackageReference Include="Hangfire" Version="1.7.31" />
    <PackageReference Include="Hangfire.AspNetCore" Version="1.7.31" />
    <PackageReference Include="IdentityModel" Version="6.0.0" />
    <PackageReference Include="Microsoft.AspNetCore.Authentication.OpenIdConnect" Version="7.0.0" />
    <PackageReference Include="Microsoft.AspNetCore.Components" Version="7.0.0" />
    <PackageReference Include="Microsoft.AspNetCore.Http.Abstractions" Version="2.2.0" />
    <PackageReference Include="Microsoft.AspNetCore.Mvc.NewtonsoftJson" Version="7.0.0" />
    <PackageReference Include="Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation" Version="7.0.0" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="7.0.0">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
    </PackageReference>
    <PackageReference Include="Microsoft.Extensions.Hosting" Version="7.0.0" />
    <PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" Version="7.0.0" />
    <PackageReference Include="NETStandard.Library" Version="2.0.3" />
    <PackageReference Include="Serilog.AspNetCore" Version="6.0.1" />
    <PackageReference Include="Serilog.Enrichers.Environment" Version="2.2.0" />
    <PackageReference Include="Serilog.Settings.Configuration" Version="3.4.0" />
    <PackageReference Include="Serilog.Sinks.File" Version="5.0.0" />
    <PackageReference Include="Serilog.Sinks.Seq" Version="5.2.1" />
    <PackageReference Include="Swashbuckle.AspNetCore" Version="6.4.0" />
    <PackageReference Include="Swashbuckle.AspNetCore.Annotations" Version="6.4.0" />
    <PackageReference Include="Wrak.ListComponentRoutes" Version="1.0.3" />
  </ItemGroup>

  <ItemGroup>
    <ProjectReference Include="..\XXXX.XXXX.Core\XXXX.XXXX.Core.csproj" />
    <ProjectReference Include="..\XXXX.XXXX.Infrastructure\XXXX.XXXX.Infrastructure.csproj" />
  </ItemGroup>

  <ItemGroup>
    <Content Update="wwwroot\favicon.ico">
      <ExcludeFromSingleFile>true</ExcludeFromSingleFile>
      <CopyToPublishDirectory>PreserveNewest</CopyToPublishDirectory>
    </Content>
  </ItemGroup>

</Project>

UseDotNet Task Logs
Use DotNet Task Logs.zip
Restore Task Logs
Restore Task Logs.zip
Restore Error
2022-11-09T17:06:23.9621427Z Build FAILED.
2022-11-09T17:06:23.9626297Z
2022-11-09T17:06:23.9679507Z        "D:\a\1\s\XXXXX.XXXXX.Web\XXXXX - XXXX.XXXX.XXXX.csproj" (Restore target) (1) ->
2022-11-09T17:06:23.9714031Z        (Restore target) ->
2022-11-09T17:06:23.9727033Z          D:\a\1\s\XXXXX.XXXXX.Web\XXXXX - XXXX.XXXX.XXXX.csproj : error NU1201: Project XXXXX.XXXXX.Core is not compatible with net6.0 (.NETCoreApp,Version=v6.0). Project XXXXX.XXXXX.Core supports: net7.0 (.NETCoreApp,Version=v7.0)
2022-11-09T17:06:23.9730732Z          D:\a\1\s\XXXXX.XXXXX.Web\XXXXX - XXXX.XXXX.XXXX.csproj : error NU1201: Project XXXXX.XXXXX.Infrastructure is not compatible with net6.0 (.NETCoreApp,Version=v6.0). Project XXXXX.XXXXX.Infrastructure supports: net7.0 (.NETCoreApp,Version=v7.0)
2022-11-09T17:06:23.9731590Z
2022-11-09T17:06:23.9732093Z     0 Warning(s)
2022-11-09T17:06:23.9732602Z     2 Error(s)

Exact same issue here as well, but for Publish. Using UseDotNet@2 setup for version: '7.x', which works fine for DotNetCoreCLI@2 on build and test, but fails on publish because it seemingly defaults to .NET 6.
error NU1201: Project <Redacted> is not compatible with net6.0 (.NETCoreApp,Version=v6.0). Project <Redacted> supports: net7.0 (.NETCoreApp,Version=v7.0)

any updates?

Wondering if anyone here has found a workaround for this issue?

So, I finally got to the bottom of this, and it turned out to be self-inflicted. The short of it is that a backup .csproj file targeting net6.0 had somehow found its way into the web project's root directory and was being picked up by the restore command. Naturally, it failed to build against dependencies targeting net7.0.
For those of you continuing to hit up against this issue, assuming you have Powershell available, you may find running the following script from your solution root helpful in flushing out potential offending files:
Get-ChildItem -Exclude "*.dll" -Include bin,obj -Recurse | Remove-Item -Force -Recurse
Get-ChildItem -File -Recurse | Select-String "net6.0" -List | Select Path


Store alarms in app instead of watch

Problems to resolve with that:

setting up an alarm is easier using the app (or at least I can have the option)
when changing watch (I have multiple) I want to see all the alarms set up on the new watch already (like apps and watchfaces).

It's not fun always syncing all the changes, and I have like 5 alarms to set up for a new watch...

I think this is out of scope at the moment. We would also need to have firmware support for that.

Can you coordinate with Rebble team (or whoever owns the firmware nowdays) to achieve this? It would be a very good addition.

At the current rate of RebbleOS development, without adding additional features that are currently out of scope, it will be done in 20 years at the earliest anyway. Let's maybe try to achieve the base firmware first before we come up with more features, and feel free to contribute to https://github.com/pebble-dev/RebbleOS to speed up the development so we don't have to wait until the 40s for it ;)


Fix wysiwyg center

This wasn't taking into account zoom properly.
The logic should probably get refactored a bit, it's not ideal that we're passing canvas, state and scale as different arguments. Also it's weird that the function that returns the center is computing the viewport translation. But I'm not motivated enough to fix it right now...
Also the small jump at the end is annoying!

Fixes #1100

It's also concerning that the position of the wysiwyg text is not sync'd with the position of the text once committed...


Release/v10.0.0

Let's wait on this until Garrett's two PRs are merged so we don't have to do another release.

As commentary for https://github.com/MyPureCloud/genesys-cloud-webrtc-sdk/pull/897/commits/384e9e5d60d05aaeec66b6c802591e4099696530, I fixed the intermittent test by just having the mocks always use localhost for the websocket. Here are the three pieces involved in what was going on:

The intermittent test is the only test using failStreaming at this point. We're using it to make sure we're handling invalid_token errors from streaming-client.
With the mock websocket server, we check failStreaming and return a SASL failure, which is what we want in this test and all we really need.
If wsHost is null, we'll use a real environment (I'll admit I'm not certain why this sometimes works...I didn't dig that far).

As far as I could tell, there wasn't a reason (any longer) to use null when we wanted streaming-client to fail, especially because of item 3 above, since that seems to be the opposite of what we want.


Additional invalid syntax

Hi! Following up from https://github.com/codeout/junoser/issues/24 as I finally had time to look at it more closely.
I installed v0.4.5 with gem install junoser and am getting a couple errors:
On various QFXs, running Junos 20 or Junos 14:
Invalid syntax:  set system license keys key "JUNOS123456789 xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx yyyyy"
On various MXs running Junos 17 or 18:
Invalid syntax:  set protocols bgp group IX4 family inet unicast prefix-limit teardown 80 idle-timeout forever
Invalid syntax:  set protocols bgp group IX6 family inet6 unicast prefix-limit teardown 80 idle-timeout forever
Invalid syntax:  set protocols bgp group Private-Peer4 family inet unicast prefix-limit teardown 80 idle-timeout forever
Invalid syntax:  set protocols bgp group Private-Peer6 family inet6 unicast prefix-limit teardown 80 idle-timeout forever

If you're curious, your tool allowed us to find some issues with our config templates: https://gerrit.wikimedia.org/r/c/operations/homer/public/+/806857
Thanks

Hi! I'll take a look into both invalid statements.

If you're curious, your tool allowed us to find some issues with our config templates:

This is awesome! Grad to see junoser working in your project.

Hi, published junoser 0.4.6 with the fix. It looks like a Juniper's .xsd bug.
Please try the latest version and reopen this issue if you see any further problems.
Thanks again for your bug report.


reverse doesn't work anymore

gs <- gsplot() %>%
   points(1:10, 1:10) %>%
   axis(1, at = seq(0,10,by=0.1),labels=FALSE, tcl=0.15) %>%
   axis(2, reverse=TRUE)
gs

no test for this as far as I could tell

Should probably happen within lim function, which would use rev if the axes is reverse

This seems to be fixed in 0.6.1, but still no test


ncl: time_operations uses wrong weights

The ncl function time_operations uses the length of the month as weights to calculate annual means:
https://github.com/ESMValGroup/ESMValTool/blob/90eaba9156b5f13d98ba2bc206b1e80277e1b025/esmvaltool/diag_scripts/shared/statistics.ncl#L247
However, it does not consider the calendar because toint strips the attributes and thus can end up using wrong weights. Consider the following example (2000 is a leap year):
time = (/0, 24/)
time@units = "hours since 2000-2-1 00:00:0.0"
time@calendar = "noleap"

date := cd_calendar(time,  0)
month := date(:, 1)
year := date(:, 0)
weights = days_in_month(toint(year), toint(month))
print(weights) ; -> 29

year_int = toint(year)
year_int@calendar = year@calendar
weights := days_in_month(year_int, toint(month))
print(weights) ; -> 28

@axel-lauer @schlunma you guys speak NCL, mind having a look? :beer:

I just took a look and implemented a fix (PR #1956). @schlunma could you please take a quick look (just 9 lines of code/comments) and approve the PR if you think this is fine?


adding acprule  and using category

Hello,
I have created the Category under the ACP and trying to add the rule in that category. Not sure if this feature is supported or not
I am using below to pass the category information
acprule1 = fmcapi.AccessRules(fmc=fmc1, acp_name=namer,catagory = 'testing')
but I see in debug "section":"Default","category":"--Undefined--".
Just wondering if anyone was able to post/put rules under the category?
Thanks for your help.

Found below link regarding the Access rules-Categories not supported with Rest API
https://community.cisco.com/t5/network-security/how-to-get-post-accessrule-categories/m-p/3380605#M9641

Good to know.  I guess we will have to revisit in the next code release and see if it is working.
Should we close this issue for now?

Thanks
Yes, we can close this issue.


Improve logging in ORC Writer

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-XXX

Description

[ ] Here are some details about my PR, including screenshots (if applicable):

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@rdsr can you create one apache jira ticket and link to this PR?

@ZihanLi58 added

Hi Team,
Could you please remove me from the goblin email list?
I tried unsubscribing it. For some reason, it didn’t work.
Thanks.
Logasubramani
On Wed, Aug 24, 2022 at 8:53 PM Abhishek Tiwari @.***>
wrote:

@.**** commented on this pull request.
In
gobblin-modules/gobblin-orc/src/main/java/org/apache/gobblin/writer/GenericRecordToOrcValueWriter.java
https://github.com/apache/gobblin/pull/3543#discussion_r954431460:

   log.info("Column vector: {}, resizing to: {}, child count: {}", cv.keys, resizedLength, cv.childCount);

     cv.keys.ensureSize(resizedLength, true);

   log.info("Column vector: {}, resizing to: {}, child count: {}", cv.values, resizedLength, cv.childCount);

suggestion: if all you need is a hash, then perhaps writing and reusing
hashing function in Gobblin Util can help?
—
Reply to this email directly, view it on GitHub
https://github.com/apache/gobblin/pull/3543#discussion_r954431460, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACSHLZEMADSUEZWAKZ27S2DV23GZLANCNFSM57Q22GBA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

+1 Approved


Is it possible to make sdf calculation differentiable?

Say I have a point p=(xyz), and a distance d = sdf(p), I want to do something like d.backward() to get p.grad? I was able to do it with TORCH_SDF library(a modified version of Kaolin), but it seems I cannot do it with pytorch_volumetric?

I think you may implement this with the sdf_grad in:
sdf_val, sdf_grad = sdf(pts)
However, instead of apply sdf_grad to sdf_val, it should be applied to pts directly. This may because the sdf function is rather implemented in an implicit way, which means there's no analytical differential relationship between sdf_value and pts.


Gittyup (Debian, xfce (X11, not Wayland), flatpak) now won't show GUI

After using it for a month or so, Gittyup (Debian, xfce (X11, not Wayland), flatpak) now seems to start, but does not show the graphical window.
If I start it with the command line with "flatpak run -v --branch=stable --arch=x86_64 --command=gittyup com.github.Murmele.Gittyup", the process starts, shows some messages/errors/warnings, and hangs.
One message is: 'Failed to load module "xapp-gtk3-module"', which, after a lot of googling, is something to do with flatpak, but not something that would keep a flatpak app from running. The next message (which further tells me that the last message was not a terminal error) is "Qt: Session management error", which is an ignorable message that can be eliminated by "unset SESSION_MANAGER" before starting the app. Not that it matters, but "sudo apt install xapp" and sudo apt install xapp-gtk3-module" do not find anything by those names in apt, but that was the extent to which I unnecessarily(?) tried to fix that problem.
If I follow the instructions here: https://docs.flatpak.org/en/latest/debugging.html, and run Gittyup in gdb, I get:
(gdb) run
Starting program: /app/bin/gittyup
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff27786c0 (LWP 24)]
[New Thread 0x7ffff1f776c0 (LWP 25)]
Gtk-Message: 14:49:16.097: Failed to load module "xapp-gtk3-module"
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
[New Thread 0x7fffebfff6c0 (LWP 26)]
[New Thread 0x7fffeaa786c0 (LWP 27)]
[New Thread 0x7fffea2776c0 (LWP 28)]
[New Thread 0x7fffe9a766c0 (LWP 29)]
[New Thread 0x7fffe92756c0 (LWP 30)]
[Thread 0x7ffff65e3880 (LWP 21) exited]
...then, after a 10 seconds or so:
[Thread 0x7fffe92756c0 (LWP 30) exited]
[Thread 0x7fffe9a766c0 (LWP 29) exited]
[Thread 0x7fffea2776c0 (LWP 28) exited]
[Thread 0x7fffeaa786c0 (LWP 27) exited]
...then there is nothing more in the logs, and no gui.
If I start it from xfce, I see this process tree: xfce4-panel─┬─bwrap───bwrap───gittyup───3*[{gittyup}]
When I used strace with "strace flatpak run -v --branch=stable --arch=x86_64 --command=gittyup com.github.Murmele.Gittyup |& tee gittyup.strace.log" and grepped through the output file, I saw that it was referencing many config files, so I tried uninstalling all flatpak apps, deleting ~/.var/app/com.github.Murmele.Gittyup, apt uninstalling flatpak, and reinstalling everything from scratch, and I see that it is no longer referencing the .git/gittyup files in my project directories (which, yes, I tried deleting previously), but still, no gui.
I even tried "sudo chmod u+s /usr/bin/bwrap" for giggles, but no dice.
The only file in the ~/.local/share/flatpak/ tree is config, which contains:
[core]
repo_version=1
mode=bare-user-only
min-free-space-size=500MB
The Appimage version of Gittyup works just fine. I wonder if it has anything to do with the environment or config file differences between the Appimage and the flatpak versions.
I have VSCodium installed in flatpak, and it works just fine. If I "strace flatpak run com.vscodium.codium |& tee vscodium" and use meld to diff the output with that of Gittyup, I see that it does the same miniconda3 bwrap stuff, but, besides the architectural differences, I don't see anything that stands out.
Everything was working fine, until I did an update on apt and flatpak (and maybe a "sudo shutdown -r now" while everything was running), so I tried installing and fully updating in a Debian VM, and it works fine. In the VM, however, I do not have miniconda installed, for one.
In the VM, where the Gittyup flatpak runs just fine (from xfce or terminal), grep returns no mention of "xapp-gtk3-module", but there is the "Qt: Session management error" line, followed by the screenshot I have included.
Regarding the apt and flatpak updates, here is what was updated in apt at that time:
Start-Date: 2024-06-17 14:55:31
Commandline: apt upgrade -y
Requested-By: user (1000)
Upgrade: containerd.io:amd64 (1.6.32-1, 1.6.33-1), docker-compose-plugin:amd64 (2.27.0-1debian.12bookworm, 2.27.1-1debian.12bookworm), docker-ce-cli:amd64 (5:26.1.3-1debian.12bookworm, 5:26.1.4-1debian.12bookworm), gstreamer1.0-gl:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), libarchive13:amd64 (3.6.2-1, 3.6.2-1+deb12u1), libavdevice59:amd64 (7:5.1.4-0+deb12u1, 7:5.1.5-0+deb12u1), libgstreamer-gl1.0-0:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), ffmpeg:amd64 (7:5.1.4-0+deb12u1, 7:5.1.5-0+deb12u1), libarchive-tools:amd64 (3.6.2-1, 3.6.2-1+deb12u1), gstreamer1.0-alsa:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), gir1.2-gst-plugins-base-1.0:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), libpostproc56:amd64 (7:5.1.4-0+deb12u1, 7:5.1.5-0+deb12u1), docker-buildx-plugin:amd64 (0.14.0-1debian.12bookworm, 0.14.1-1debian.12bookworm), docker-ce:amd64 (5:26.1.3-1debian.12bookworm, 5:26.1.4-1debian.12bookworm), libndp0:amd64 (1.8-1, 1.8-1+deb12u1), gstreamer1.0-x:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), libavcodec59:amd64 (7:5.1.4-0+deb12u1, 7:5.1.5-0+deb12u1), gstreamer1.0-plugins-base:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), docker-ce-rootless-extras:amd64 (5:26.1.3-1debian.12bookworm, 5:26.1.4-1debian.12bookworm), python3-pil.imagetk:amd64 (9.4.0-1.1+b1, 9.4.0-1.1+deb12u1), libavutil57:amd64 (7:5.1.4-0+deb12u1, 7:5.1.5-0+deb12u1), libswscale6:amd64 (7:5.1.4-0+deb12u1, 7:5.1.5-0+deb12u1), python3-pil:amd64 (9.4.0-1.1+b1, 9.4.0-1.1+deb12u1), libswresample4:amd64 (7:5.1.4-0+deb12u1, 7:5.1.5-0+deb12u1), libavformat59:amd64 (7:5.1.4-0+deb12u1, 7:5.1.5-0+deb12u1), libgstreamer-plugins-base1.0-0:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), firefox-esr:amd64 (115.11.0esr-1deb12u1, 115.12.0esr-1deb12u1), libavfilter8:amd64 (7:5.1.4-0+deb12u1, 7:5.1.5-0+deb12u1)
End-Date: 2024-06-17 14:55:53
I'm not sure how to see what versions of Gittyup dependencies were in flatpak before I did the flatpak app update. I think the versions of the dependencies are what the Gittyup flatpak app says it needs, though, and the Gittyup flatpak version hasn't changed in some time...should not the dependency versions installed in flatpak remain the same?
I have to point out that I've installed updating apt and flatpak apps in the VM works fine, and with xfce, so I don't think it is a version problem. In my hardware box with the problem, I've unintstalled and wiped out every config file I could find and resinstalled from scratch, which did not fix the problem, so I don't think it was a config file corruption problem. I do not have a standardized Debian config, as I install tools when I find them as solutions to problems I have, so it would be near impossible to recreate the environment I have.
For me, I'm fine with running the Appimage version. Maybe this is really a flatpak issue.
For the purposes of helping the community, I'm willing to try suggestions to resolve this issue.
gittyup.strace.log

Update1: I've copied the .git.gittyup directory back into my project folder and ran the Gittyup Appimage, pointed it to the project folder, and I'm getting:
" 8:36 PM - Indexer Crashed - The indexer worker process crashed. If this problem persists please contact us at ."
This problem happens even if I shut down Gittyup, delete .git/gittyup from my project folder, then run Gitttyup and point it at my project folder again.
This problem happens even if I open a project I haven't touched in weeks, so I don't think it is in any way something to do with corruption in my current project.
Update2: This is identical to https://github.com/Murmele/Gittyup/issues/776
Yes, I am getting the same kernel messages as issue 776.
I wonder if it is the cause of this Gittyup flatpak issue I filed.
Can someone toss me a clue?

FIXED...?
I was beat and ready to give up, then I thought I would give Gittyup one last shot.
I cloned the repository and compiled from source, AND IT WORKED.
I get a GUI, and I don't get "Indexer Crashed". Gittyup works perfectly.
I can create a new repository.
I can open my existing project.
I compiled from main, not from the most recent development branch.
This was after I tried the following:
flatpak uninstall com.github.Murmele.Gittyup
rm -rf ~/.var/app/com.github.Murmele.Gittyup
rm -rf ~/.local/share/flatpak/Gittyup
rm -rf ~/.local/share/Gittyup
rm -rf ~/.config/gittyup.github.com
rm -rf ~/python/step4
Then, I start the AppImage version of Gittyup and create a new project at ~/python/step4, and I get the same "Indexer Crashed" error.
Then I "flatpak uninstall com.github.Murmele.Gittyup" and run the flatpak version, and still, no gui.
I really didn't want to reinstall my system from scratch, only for something unknown to change, and have Gittyup stop working again.

Can you build the flatpak package using the DEBUG flag for gittyup?
just pass -DCMAKE_BUILD_TYPE=Debug to the cmake command inside the manifest
So the gui showed up with version Gittyup 1.3.0 but not with 1.4.0? Because recently we released 1.4.0 maybe this makes problems for you?
KDE Application Platform                org.kde.Platform                                                        5.15-23.08    flathub           system you probably have the newest platform version installed?
Can you try a flatpak update?

I've created a flatpak build on my Debian box with the -DCMAKE_BUILD_TYPE=Debug flag in the manifest.
It still does not open a GUI window. It crashes at exactly the same point in the strace logs.
I'm also attaching the merged log file from strace and bpftrace that my script produced.
The openat /dev/dri/renderD128 is at 22:29:56.246221
I did the "flatpak build-bundle" to send you the result in flatpak format.
Comments:I noticed that the com.github.Murmele.Gittyup.yaml in the 1.4 source tree is for version 1.3, so I fixed that.
I used the install.sh, build.sh, and createBundle.sh you pointed me to.
I modified install.sh a little:
flatpak remote-delete --user GittyupRepo
flatpak remote-add --user GittyupRepo $(pwd)/GittyupRepo --no-gpg-verify --if-not-exists
flatpak install --user GittyupRepo com.github.Murmele.Gittyup
If you want me to run that again differently, tell me.
I was not sure what environment I should be using to create this build, but maybe that is abstracted away by the flatpak-builder process.
I have an idea about a compiler option I want to try.
gittyup.flatpak.build.test.zip

Did you get a more readable stacktrace?

@johnny-mayo did you try running flatpak update? Flatpak comes with its own graphics libraries, which don't automatically get updated when your OS gets a graphics driver update. Running flatpak update normally installs the newly needed graphics libraries.

I finally got back to this issue and figured it out...well, because another flatpak app was touching
/dev/dri/renderD128 and dying a miserable death the same as Gittyup, according strace.
The TL;DR of it is that something in flatpak is trying to do something in the nouveau driver
that the nouveau driver does not support very well, and "pop goes the weasel" (dmesg below).
Solutions:

Use the Nvidia binaries (don't like this idea)
Maybe play with https://github.com/NVIDIA/open-gpu-kernel-modules
Blacklist nouveau from loading and lose accel in programs that run fine with it
Maybe disable the X11 Composite extension (but probably not)
flatpak override --user --env=LIBGL_ALWAYS_SOFTWARE=1 com.github.Murmele.Gittyup

A little more on that fifth option. It disables hardware rendering for the specified flatpak
app. See here:
(base) user@erying:~$ flatpak info --show-permissions com.github.Murmele.Gittyup
[Context]
shared=network;ipc;
sockets=x11;wayland;fallback-x11;ssh-auth;
devices=dri;
filesystems=home;/tmp;xdg-config/kdeglobals:ro;xdg-run/keyring;
[Session Bus Policy]
com.canonical.AppMenu.Registrar=talk
org.kde.kconfig.notify=talk
org.kde.KGlobalSettings=talk
org.freedesktop.Flatpak=talk
org.freedesktop.Notifications=talk
org.freedesktop.secrets=talk
[Environment]
LIBGL_ALWAYS_SOFTWARE=1
...so, it sets the LIBGL_ALWAYS_SOFTWARE as a default env var for the app,
so then you can just run it normally:
flatpak run com.github.Murmele.Gittyup
...and it just runs...without hardware acceleration.
Since Gittyup is not something that benefits from GPU acceleration, this works for me,
and I don't have to muck with 3rd party binaries or...well...I don't know what the
current stability is of Nvidia's open source driver, but it was alpha in 2022...almost
daily changes, though...
I would suggest adding the following line to the "finish-args:" section of:
https://github.com/Murmele/Gittyup/blob/master/com.github.Murmele.Gittyup.yml
--env=LIBGL_ALWAYS_SOFTWARE=1
Notes:
I am a little surprised "flatpak update" did not fix it. Nor did:
sudo flatpak override --device=all com.github.Murmele.Gittyup
Nor did making sure the following were installed and updated: vulkan-utils mesa-vulkan-drivers mesa-utils libgl1-mesa-glx libx11-xcb1 libxcb-dri3-0 libxcb-present0 libpciaccess0 libdrm2 libxshmfence1 libxxf86vm1 libbsd0
Nor did these help: --log-level=DEBUG, LIBGL_DEBUG=verbose, sudo systemctl stop apparmor, --filesystem=home, --repair
I did not try (but will if someone gives reason to):
flatpak install flathub org.freedesktop.Platform.GL.default
flatpak install flathub org.freedesktop.Platform.GL.nvidia-<driver_version>
flatpak install flathub org.freedesktop.Platform.GL32.default
As an aside, I would really like some input on https://github.com/Murmele/Gittyup/discussions/789
I've done quite a bit of googling...but is it a non-problem because of a common solution?
I'd like to know from someone that knows.
I hope to do the pull request tomorrow.
issue783.zip
In the attached issue783.zip file are all the scripts and Dockerfile needed to create an archlinux:latest docker image (like in the github CI) with everything installed that is necessary to build Gittyup.flatpak.
Start with README
Toodles,
johnny-mayo

But switching to Software Rendering is not the solution. It works for a lot of other distributions and it makes the software slower

I agree, completely. My solution is a hacky kluge work-around.
The problem is not with Gittyup. This used to work, then stopped, with the same 1.4 version of Gittyup. It also affects Anki flatpak in exactly the same way, according to strace logs, which is the reason I came back to this problem.
The factors involved, I think, are the video driver, video driver version, and flatpak (with its video shared objects and other support stuff) and possibly other library version issues in the system.
My few google searches gave me the impression this is not something of a priority on flatpak's side. They seem to point to something (anything?) else in the system and close the situation. "Not my problem" syndrome.
I don't have the resources to investigate this non-Gittyup problem further.
I would like Gittyup to work for more people.
Thank you,
johnny-mayo
P.S. I might not be able to do the pull request until tomorrow, if you still want to go this direction.

This seems to me like it's most likely a nouveau problem. Until recently, nouveau was so unstable and unfinished that even 2d desktop usage was problematic. You being on Debian Stable suggests that you are still using a nouveau version that is in such a state. From the dmesg you shared, it looks like this is a kernel bug and should be fixed there. Most likely it has already been fixed a while ago and Debian Stable is just missing said fix.
On Debian Testing, nouveau works surprisingly well nowadays, even if I would still not recommend it because some basic features are still missing.

Thank you very much for the input.
From my limited googling, I got the impression that even the proprietary Nvidia binary blobs were causing issues with flatpak, but I had no idea that Nouveau was in such a sad state of affairs on Debian stable. Maybe I should try out the open source Nvidia option?...they seem to be acting like it is important to put energies into its development.
Both the compiled from source and the AppImage versions of Gittyup work just fine with Nouveau. It seems to be more of a "flatpak thing" with Nouveau (and/or the kernel, you say?), which is ironic, considering one of the goals of flatpak it to be able to run apps on any Linux based OS, but instead the app runs anywhere but on flatpak. Again, the same problem affects the Anki flatpak, with the same "workaround" solution.
I am curious, though, since my assumptions may have been incorrect...how does Gittyup benefit from hardware acceleration?
Whatever the root cause(s) might be, the decision must be made as to whether it is better to completely avoid the possibility of the issue (at a performance cost?), or if it is better to try to make sure the users become aware of this workaround or be told they need a different video driver if they have problems with the flatpak version.
In that respect, I have no input. I'm here to help. I'm out of resources, though.
Thank you,
johnny-mayo

I would think that on a normal system, performance would be similar. It just renders stuff on the CPU instead of the GPU, which takes processing power away from something like a compiler running alongside Gittyup.
Where it might make a bigger difference are less powerful machines, like single board computers.
I think the main issue is likely just feeling wasteful rendering on the CPU, when there is a GPU available for the task, and also it feeling like we are fixing an issue in the wrong place.
One thing I am wondering though: As far as I know, LIBGL_ALWAYS_SOFTWARE is a feature of Mesa; Would that even work on systems not using Mesa (like proprietary Nvidia, proprietary AMD(?), and others)?

I offer my reflections, but in no way wish to steer opinions. This is just a thought experiment for me, at this point.
One little thing...Gittyup is built from an ubuntu-latest vm in the CI, and from that, the AppImage is built, which works just fine, but the flatpak version is built on an Arch docker image/container, and it doesn't work (if my very limited CI yml interpretation is correct)...not sure it would prove much if it actually worked, though.
I did not think to consider single board or other low-end computers. Two things come to mind. First, I hope it is no longer the case that hardware acceleration support on SBCs is generally lacking. Second, if the image Gittyup renders is static because the user is not manipulating the program during compile (or some other CPU intensive task (on an SBC?)), would there be any performance benefit from GPU acceleration?
From what I gather, LIBGL_ALWAYS_SOFTWARE where Mesa library is used for OpenGL rendering. Maybe this is a good thing, as it would not disable hardware acceleration, and, thus, be a performance detriment, except in the case of Mesa?
Here's a disgusting and terrible idea: In the flatpak version, point the manifest to run a wrapper script that sets LIBGL_ALWAYS_SOFTWARE only if the specific criteria leading to failure is met, so, something like:
#!/bin/bash
if lspci -k | grep -E "Kernel driver in use: nouveau"; then
if (do something here to figure out if the nouveau version is less than x.x); then
export LIBGL_ALWAYS_SOFTWARE=1
fi
fi
Launch the actual application
exec /path/to/your/application "$@"
I have no idea how to tell, across distros, using programs that are always installed, not requiring root, and not just looking at the symlinks, the version of nouveau in use.
I really have no idea what other factors should be considered, either. I do not see a lot of questions being asked when "program no workie" in flatpak discussions or issues.
Anyway, thought experiment. Infinite rabbit holes. I've got to leave this issue to others. I do, I do.
johnny-mayo


Update the code climate API token

The old token only applied to the
https://github.com/michaeldv/awesome_print repository, which has
since been moved to https://github.com/awesome-print/awesome_print
url.

Merging so that our code climate coverage badge updates when we push to travis.


Set up hideSimButtons for handoff via query string

Moved hideSimButtons flag to iframe query string so it can be accessed on load to avoid briefly showing controls on render.

Resolved conflicts @jwunderl review?


[nemeton web] FIX: Prolog tutorial link

TODO
Program Builders --> Challenges:
"Get started with OKP4 protocol: how to use the CLI tutorial" should link to https://docs.okp4.network/tutorials/prolog-1

@antho31
Fixed and available in staging https://nemeton.staging.okp4.network/builders/challenges#challenges


Remove telemetry

Gauge does not need to keep telemetry data anymore so

Remove telemetry code from Gauge
Remove telemetry messages
Remove the telemetry config
Archive and remove google analytics
Remove telemetry popups from visual studio code

I'll pick this up

This story is not too be picked up yet. We have left it in the backlog for now.

Ok, let me know when this can be picked up

@M4rk9696 We can start work on this.
We need to remove the telemetry package and all its references.

Getting following error after installing latest gauge (built from source).


No license in nuget since 2.5.0 because of wrong tag used

Description
With https://github.com/confluentinc/confluent-kafka-dotnet/pull/2192/files#diff-625d4f5deb9157fe8215f0f0aa6d44f4697beb50b8142cdbb3342a3353aad599R8 you changed to nuget license expression which is appreciated but you used the wrong tag, so now the nuget does not have any license.
see https://github.com/confluentinc/confluent-kafka-dotnet/pull/2192/files#r1693253202
How to reproduce
Check https://nuget.info/packages/Confluent.Kafka/2.5.0
Checklist
Please provide the following information:

[-] A complete (i.e. we can run it), minimal program demonstrating the problem. No need to supply a project file.
[x] Confluent.Kafka nuget version.
[-] Apache Kafka version.
[-] Client configuration.
[-] Operating system.
[-] Provide logs (with "debug" : "..." as necessary in configuration).
[-] Provide broker log excerpts.
[-] Critical issue.

Thanks for catching this bug. We've fixed it in https://github.com/confluentinc/confluent-kafka-dotnet/pull/2275


hillsborough_county_evictions_geocoded.csv formatting issue

Looks like there might be an issue with quoting vs delimiter issue  on a few rows?

I'm looking at this, but I'm no expert, so if someone else knows more, feel free to go for it.

It looks like the .csv is using doublequotes as an escape character for doublequotes inside fields. For instance, "11624 GROVEWOOD AVE ""B""" refers to the string '11624 GROVEWOOD AVE "B"'. That's confusing the read_csv() function because it reads anything in doublequotes as a string.
A regex to change the first doublequote to a more appropriate escape character, along with adding the escape character to the read_csv params, could work. I tried coming up with the regex myself but no luck so far.

I found and fixed the problems... PR coming..

Resolved by https://github.com/datakind/Mar21-housing-insecurity/pull/14


Hanging at 'Files successfully emitted, waiting for typecheck results...'  when using custom loaders

Describe the bug
Similar issue described here:
https://github.com/facebook/create-react-app/issues/8707
However, that specific issue seemed to have multiple causes, one of which was resolved. This bug is still prevalent. This bug was described in this specific comment in that issue: https://github.com/facebook/create-react-app/issues/8707#issuecomment-606475886
That issue seemed to affect ionic framework. The solution for them was to revert from 3.4.1 to 3.4.0. However, I am using react-scripts 4.0.1
Essentially, using any webpack loader (at least the three I used) will leave CRA hanging on "Files successfully emitted, waiting for typecheck results..."
I've tested workerize-loader, worker-loader, and comlink-loader (as you can tell I'm trying to incorporate web loaders into my project). Using any of these will cause the typechecking step to hang. However, running yarn tsc will run fine.
Did you try recovering your dependencies?
Doesn't make a difference. Problem is prevalent in a fresh CRA project.
Which terms did you search for in User Guide?
Error not found there. Only instance I can find online mentioning this issue is here (https://github.com/facebook/create-react-app/issues/8707). No other mention of the issue seems to exist elsewhere (stackoverflow, other GitHub issues, etc).
Environment
Environment Info:

  current version of create-react-app: 4.0.1
  running from /Users/noah/.npm/_npx/53533/lib/node_modules/create-react-app

  System:
    OS: macOS 11.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 14.8.0 - ~/.nvm/versions/node/v14.8.0/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.9 - ~/.nvm/versions/node/v14.8.0/bin/npm
  Browsers:
    Chrome: 87.0.4280.88
    Edge: 87.0.664.66
    Firefox: 84.0
    Safari: 14.0.2
  npmPackages:
    react: 17.0.1 => 17.0.1
    react-dom: ^16.9.0 => 16.9.0
    react-scripts: 4.0.1 => 4.0.1
  npmGlobalPackages:
    create-react-app: Not Found

Steps to reproduce

(Write your steps here:)

Install one of the worker loaders.
Implement workers

Details here: https://github.com/facebook/create-react-app/issues/8707#issuecomment-606475886

Check relevant commit in the reproducible demo for exact steps.
Expected behavior
CRA works like normal
Actual behavior
> npm run start

Starting development server...

(Hangs on this step rather than proceeding to "compiled with warnings" or "compiled successfully")
Files successfully emitted, waiting for typecheck results...

Reproducible demo
Fresh CRA project: https://github.com/NoahBres/webpack-loader-bug
Relevant commit for all the worker implementaions: https://github.com/NoahBres/webpack-loader-bug/commit/261d1f92cb6b460094f2349ea008f329cd35d691

I am experiencing this when including an .scss file from another .scss file.
Here is a starter project from the cra-typescript template, with node-sass, and a single sass file that includes another one.
https://github.com/colinsullivan/cra-sass-import-bug
Repro steps:
git clone git@github.com:colinsullivan/cra-sass-import-bug.git
yarn
yarn run start

Open src/colors.scss
Change the color
Save the file
Result:
Shell hangs on:
Files successfully emitted, waiting for typecheck results...
Expected result: app complies
$ node -v
v15.5.0

I am experiencing this when including an .scss file from another .scss file.
Here is a starter project from the cra-typescript template, with node-sass, and a single sass file that includes another one.
https://github.com/colinsullivan/cra-sass-import-bug
Repro steps:
git clone git@github.com:colinsullivan/cra-sass-import-bug.git
yarn
yarn run start

Open src/colors.scss
Change the color
Save the file
Result:
Shell hangs on:
Files successfully emitted, waiting for typecheck results...
Expected result: app complies
$ node -v
v15.5.0

I am having this issue frequently in various projects as well. Happens after I change the code a few times.

Ran into this issue myself today.

Ran into this today too with typescript.

So, I seem to have fixed this problem by making a bunch of free space on my computer (I went from 500mb to 2gb).

I missed this duplicate... I've analyzed the issue and posted a cause analysis here https://github.com/facebook/create-react-app/issues/10871

hello, I just want know, how do you fix this stuck problem finally @NoahBres
with  react-scripts: 4.0.1

hello, I just want know, how do you fix this stuck problem finally @NoahBres with react-scripts: 4.0.1

I had the same issue, but the only way I managed to solve it was to migrate the project to react-scripts: 5.0.1 , so I suggest doing that.

hello, I just want know, how do you fix this stuck problem finally @NoahBres with react-scripts: 4.0.1

I had the same issue, but the only way I managed to solve it was to migrate the project to react-scripts: 5.0.1 , so I suggest doing that.

I'm having the same alert with react-script 5.0.1

@gianluca932 and anyone else here who hasn't moved on to Vite: CRA is dead ⚰ . Vite is the easiest replacement. It is better than CRA in every way and unlike CRA, it is maintained.

When I tried to reproduce this issue using the fresh CRA project, I faced a different issue in the build on open-ssl,
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'

I have fixed this issue in the package.  with this PR https://github.com/NoahBres/webpack-loader-bug/pull/1. please check and let me know.


Add an option to prevent BackendFetch from sending X-Tolgee-Sdk-Type and X-Tolgee-SDK-Version

#3224 added headers that is sent on BackendFetch causes an unwanted side effect that the fetch now requires CORS preflight, which is not supported on some static host.

Hmm, yes you are right, it's actually quite pointless on BackendFetch, it's only there because it's using the same fetch function. I'll look at it.


For all the fields that expect an usize, if we send a negative integer we can see the word usize appear which doesn’t mean anything for most people. We should write « positive integer »

Closed by https://github.com/meilisearch/meilisearch/pull/3396


Move registration agency creation to factory

We usually have to create an state in order to create a registration agency for that state. This PR introduces a transient called for_state_abbreviation, which allows to set an specific state abbreviation directly in the factory.

This came out quite nicely.

@mike-burns thanks for the suggestion and thanks to Neil for showing me that you can use transients as part of other attributes, as in this case 😄


[SMALLFIX] Rephrase a sentence in docs/en/Security.md #75

Rephrase a sentence in docs/en/Security.md

@marshtompsxd  thanks for the grammar fix!


Added libunistring091

Added version 0.9.1 of library 'libunistring' to resolve some missing dependencies not provided in the latest releases of that library

turns out using overlays is better solution if you just wanna use different package version + more.

turns out using overlays is better solution if you just wanna use different package version + more.


Fix extras FKs and related names

Closes: #3067
What's Changed

Fix all related names

TODO

[ ] Explanation of Change(s)
[ ] Added change log fragment(s) (for more information see the documentation)
[ ] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example Plugin Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

  File "/home/runner/work/nautobot/nautobot/nautobot/extras/tests/test_filters.py", line 442, in setUpTestData
    CustomFieldChoice.objects.create(field=fields[num], value=f"Custom Field Choice {num}")

Probably needs to be changed to custom_field=fields[num].


Implement production component logic on jvm features

Re-implements the logic to build the production jar on top of JvmFeatures since much of the logic is shared between these two concepts. This reduces duplication and ensures the production logic and user-created features behave the same
Future work involves updating JVM software components to be multi-feature aware and dynamically advertise the variants of its features. Furthermore, we should deprecate calling registerFeature without a proper JVM component present and update registerFeature to add its features to the component to leverage the auto-variant-advertising functionality. Finally, we should remove the "extending" behavior of registerFeature when using the main source set.

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@jbartok I see your concern here. Most of the motivation for this work has been through conversation and has not been published as a design spec. I will make sure to create a proper design spec to distribute outside of the JVM team so we can have a proper review and consensus throughout the team.
To answer your immediate questions, the key point here is that a component does not have just one source set. The production code, test fixtures, registerFeature "things", and test suites all belong in the same component and have source sets themselves.
The Feature term here is new here as a proper term ("Capital F Feature"), though it pulls heavily from registerFeature which creates "feature variants". Though the term feature variants is really bad since it overloads the "variant" term which we use in dependency management heavily -- and these "feature variants" create many consumable configurations (variants) themselves.
For the precise definition of a Feature, I will link to the javadoc for JvmFeatureInternal (this class is intended to be made public in some form once this work becomes more stable) https://github.com/gradle/gradle/pull/24263/files#diff-d8a5d34187175e9a3e47ad629d29c3e1883a63d13ed52818cfc78d028af46d5cR29-R39
Hopefully this clears some stuff up. If you have more questions, concerns, or ideas I am happy to discuss further

@jbartok I see your concern here. Most of the motivation for this work has been through conversation and has not been published as a design spec. I will make sure to create a proper design spec to distribute outside of the JVM team so we can have a proper review and consensus throughout the team.
...
Hopefully this clears some stuff up. If you have more questions, concerns, or ideas I am happy to discuss further

Sorry, I have too little understanding of the area to have commented. Will try to do a better review as I get to it, lifting the request for changes in the meantime.

@jbartok For context, I have written up two specifications which outline the background behind these changes:
Components as a first-class construct
Partitioning components into features

Sorry some internal error occurs, please contact the administrator @blindpirate

@bot-gradle test and merge

I've triggered a build for you.


[Automation] Smithy Version Bump - 1.44.0

Automated pull request to bump Smithy version from 1.43.0 to 1.44.0

Needs update to brew formula to go out: https://github.com/smithy-lang/homebrew-tap/pull/18