Appveyor CI Integration

We should integrate Appveyor and find out if there are any issues with Windows.

Since I moved to github actions, we should add windows to the os matrix there... but I have no experience with development in Windows, and wouldn't know how to install fontforge there...


cleanup: enable single note inputs and outputs for the mint module

I don't understand what exactly is going on. (I know still a draft, just saying).


How to convert the notes in 'opencpop/segments/transcriptions'?

Thank you very much for your great work. I notice that in the original transcription file of opencpop, the notes are like this: G#4/Ab4 G#4/Ab4 G#4/Ab4 G#4/Ab4 F#4/Gb4 F#4/Gb4 F#4/Gb4 F#4/Gb4 E4 E4 E4 E4 D#4/Eb4 D#4/Eb4 D#4/Eb4 D#4/Eb4 rest E4 E4 E4 E4 rest. Could you please tell me how do you convert the notes into numbers like "68 68 68 68 66 66 66..." as you've mentioned in https://github.com/MoonInTheRiver/DiffSinger/blob/master/usr/configs/midi/cascade/opencs/eg_opencpop.png? (I'm
new to music and midi)
Thanks:)

Ah, I see. Did you extract the notes from the corresponding midi file, split the midi notes according to the sentence, and add "0" to "rest"?

notes = [librosa.note_to_midi(x.split("/")[0]) if x != 'rest' else 0
for x in song_info[3].split(" ")]

Ah, I see. Did you extract the notes from the corresponding midi file, split the midi notes according to the sentence, and add "0" as "rest"?

Yes.
Our codes:
notes = [librosa.note_to_midi(x.split("/")[0]) if x != 'rest' else 0
for x in song_info[3].split(" ")]


[DDW-904]: Integrate google analytics

This PR adds Google Analytics into a Analytics integration branch.
Todos

[x] Discover how to properly pass user unique id to Analytics instance (from electron local storage)
[x] Handle Analytics acceptance
[x] Send Machine spec data after user accepts analytics
[x] Testing

Screenshots

Testing Checklist

Slack QA thread
[ ] Test

Review Checklist
Basics

[ ] PR assigned to the PR author(s)
[ ] input-output-hk/daedalus-dev and input-output-hk/daedalus-qa assigned as PR reviewers
[ ] If there are UI changes, Alexander Rukin assigned as an additional reviewer
[ ] All visual regression testing has been reviewed (Go to Github Actions tab -> Select Chromatic workflow -> Run on your working branch)
[ ] PR has appropriate labels (release-vNext, feature/bug/chore, WIP)
[ ] PR link is added to a Jira ticket, ticket moved to In Review
[ ] PR is updated to the most recent version of the target branch (and there are no conflicts)
[ ] PR has a good description that summarizes all changes
[ ] PR contains screenshots (in case of UI changes)
[ ] CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
[ ] There are no missing translations (running yarn manage:translations produces no changes)
[ ] Text changes are proofread and approved (Jane Wild / Amy Reeve)
[ ] Japanese text changes are proofread and approved (Junko Oda)
[ ] Storybook works and no stories are broken (yarn storybook)
[ ] In case of dependency changes yarn.lock file is updated

Code Quality

[ ] Important parts of the code are properly commented and documented
[ ] Code is properly typed with typescript types
[ ] React components are split-up enough to avoid unnecessary re-renderings
[ ] Any code that only works in main process is neatly separated from components

Testing

[ ] New feature/change is covered by acceptance tests
[ ] New feature/change is manually tested and approved by QA team
[ ] All existing acceptance tests are still up-to-date
[ ] New feature/change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review

[ ] Update Slack QA thread by marking it with a green checkmark

Closing - https://github.com/input-output-hk/daedalus/pull/2927 is replacing this PR.


Add test of alert_handler_reg_wrap.sv

It should be merged after https://github.com/antmicro/verilator/pull/262 and when https://github.com/alainmarcel/Surelog/issues/1323 is resolved.

Blocked by https://github.com/antmicro/verilator/pull/270

It waits for https://github.com/antmicro/verilator/pull/370


Add Exception Handling

@reillymck Looks good.  Have you verified that this still works with run_experiment.py?

Update I see that the parallel threads are all killed if an exception is raised. I will add a fix so that if the BfasstException is raised that it is just attached to the status list instead of killing all the threads.

@jgoeders I think I have made the proper adjustments in the code for the multithreading. However, I am trying to test it with one of the .yaml in the experiments folder. Due to code errors in the current main branch (for instance my current open issue), some of the .yaml files do not run correctly. Is there a proper .yaml for the CI test? @dallinjdahl which scripts are you planning on using for the CI test? I am not sure if just running the code under "check installation" is enough since we have multithreading + we have the experiment .yaml files. Maybe the CI should test that all experiment .yaml's still work with new PRs?

These features will be added in the flow_args pull request.


Final project check

This issue is written to be used as an agenda for the meeting on 8/10.
As mentioned in the call the week before, it would be wise to all check the current repository and the grading requirements.
Therefore each team member needs to provide feedback on our current repository as if you grade it. So that we can find optimalizations.
Kind regards,
Julian Peters

1.Github Repository
1.1 Research motivation
Maybe not the right question, because we ask how but shouldn't it be without the how? We only check if it influences it and not why it happens. Way of deployment is wrong, we knit an html file. Hence this should be changed under "Way of deployment". Furthermore shouldn't only the data_deployment.Rmd contain the research questions and the README only the goal and instructions on how to work with our github?
1.2 Repository structure and documentation
Well done, but simular README and data_deployment.Rmd question.
1.3 Breadth of contributions and way-of-working
Followed correctly.
2.Data preparation & analysis
2.1 Data exploration
Could add a rmarkdown file to the src subfiles analysis, data-preparation and paper explaining what happens in brief? We can extract the information given about those files from the README to structure our work further. And data exploration code can be put in such a rmarkdown file.
2.2 Data preparation
This is done correctly
2.3 Analysis and deployment
Current analysis file lacks dept. Could have coded the analysis so that the regression and plot are saved as a picture and those are called into the final paper in data_deployment.Rmd. This should be done by a function.

Source code and automation
3.1 Source code quality
src/data-preparation all files are good
src/analysis see comment above
src/data_deployment.Rmd seeing this file twice, hence needs to be deleted one. The most advanced file is good. Except things like title test 1 make is still in it. When you alter a file look further then only adding your part.

3.2 Degree of automation
The file runs automatic.

@JulianPetersIsCoding  about 1.1: with "how" we mean "how much": maybe rephrase the RQ to: "what is the effect of the length of a TV show on its rating?" to make it more clear?
furthermore, according to Tilburg Science Hub the readme should include the motivation and RQ -  check this link

@irisverzijl great then I know why that is added! Was unclear for me.

Additional remarks:
there is a data_deployment.html (output file) in the ratings_series_imdb\SRC\paper folder while it should be saved in the ratings_series_imdb\SRC\paper folder

1.1: Yes agreed with @JulianPetersIsCoding the readme has too much info probably?
1.2 good, except for the double data_deployment.Rmd file, which will be tackled
1.3 good
2.1 proficient
2.2 looks very good
2.3 great update iris!
3.1 I think this is quite well, given all the usage of custom functions, etc. the source code is of good quality
3.2 When the Rmd bug is fixed it is automated and therefore good

@jibbebeer  see previous comment about the readme - pointing to tilburg science hub
lets discuss in class


Adding new Advocate

Adding Thomas

OPS Build status updates of commit dfaf530:
:clock10: Preparing: average preparing time is 40 sec(s)

OPS Build status updates of commit dfaf530:
:clock10: Incremental building: average incremental building time is 36 sec(s)

OPS Build status updates of commit dfaf530:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

advocates/index.html.yml
:white_check_mark:Succeeded
View

advocates/map.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/thomas-maurer.png
:white_check_mark:Succeeded
View

advocates/thomas-maurer.yml
:white_check_mark:Succeeded
View

advocates/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Is waitid() system call provided?

Nix has waitpid,but no waitid

If there's a good case for it, we can always add it.  Would you care to submit a patch?

That syntax is valid, so probably the error is real.  You can use strace or ktrace to check what value was actually passed to the OS.

Thanks. I found that WEXITED can only be used in watid.


Update bootstrap-datetimepicker.js

add event input.changer() when datetimepicker hide

Per the contrib doc, please make your PRs to the development branch. PRs to the master will be closed.


[SPARK-16822] [DOC] [Support latex in scaladoc with MathJax]

What changes were proposed in this pull request?
LaTeX is rendered as simple code, in LinearRegression.scala
{{{
 L = 1/2n||\sum_i w_i(x_i - \bar{x_i}) / \hat{x_i} - (y - \bar{y}) / \hat{y}||^2 + regTerms
}}}

Test build #64044 has started for PR 14711 at commit 7cacb11.

cc @lins05 @srowen

Test build #64044 has finished for PR 14711 at commit 7cacb11.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64044/
Test PASSed.

I'm confused, isn't this related to SPARK-17095? you're already fixing mathjax issues there.

@srowen , Actually this fix (mathjax issues) for this JIRA only. As @sethah mentioned in his comment, he is working on SPARK-17095, he will send PR soon.

I'm referring to your PR https://github.com/apache/spark/pull/14688  I don't see that he said he's working on it, just that he encountered it while working on something else. I'd rather fix the mathjax issues of both forms in that PR at once.

ohh i got it. Can i close this PR..?

You can just merge the work over to the other PR. I think we want to fix latex that's rendering as code accidentally, and latex whose closing braces are mangled by scaladoc.


Return raw stored bytes for raw queries

Closes #275

[x] Update query to return raw bytes
[x] All unit tests pass
[x] Update cli and rest bindings for raw queries (we changed result format)
[ ] Manual testing of CLI and REST interfaces for raw query

I set up a chain and set up one instance of the hackatom contract.
CLI works as expected
$ wasmcli query wasm contract-state raw $CONTRACT 636F6E666967 --hex
{"verifier":"1X70Zro1JtMdC5gXPvnbUvkpiqU=","beneficiary":"/auu2mTPtQQlmqMoLBCfa9M+cpI=","funder":"vtvGhCLGUK8CHAef5ckHHZEvIpc="}
$ wasmcli query wasm contract-state all $CONTRACT
[{"key":"636F6E666967","val":"eyJ2ZXJpZmllciI6IjFYNzBacm8xSnRNZEM1Z1hQdm5iVXZrcGlxVT0iLCJiZW5lZmljaWFyeSI6Ii9hdXUybVRQdFFRbG1xTW9MQkNmYTlNK2NwST0iLCJmdW5kZXIiOiJ2dHZHaENMR1VLOENIQWVmNWNrSEhaRXZJcGM9In0="}]

And after an update REST works (using json.RawMessage):
$ curl http://localhost:1317/wasm/contract/cosmos18vd8fpwxzck93qlwghaj6arh4p7c5n89uzcee5/raw/636F6E666967?encoding=hex
{
  "height": "148",
  "result": {
    "verifier": "1X70Zro1JtMdC5gXPvnbUvkpiqU=",
    "beneficiary": "/auu2mTPtQQlmqMoLBCfa9M+cpI=",
    "funder": "vtvGhCLGUK8CHAef5ckHHZEvIpc="
  }
}


npmjs'es current node-saml packages < 4.0.0 are causing potentially dangerous situations from security pov

At the moment (7th Sep 2021) https://www.npmjs.com/package/node-saml 's release packages are different versions from zoellner/node-saml repository which was forked from node-saml/passport-saml quite some time (over a year) ago and started to live its own life after that.
Later node-saml/passport-saml was splitted to node-saml/passport-saml and node-saml/node-saml modules. I believe plan was to start releasing to https://www.npmjs.com/package/node-saml from node-saml/node-saml repository after 4.0.0 (and versions prior to that at the npmjs node-saml are from zoellner/node-saml github repository).
So at the moment versions at https://www.npmjs.com/package/node-saml are (and corresponding sources for those versions are):

4.0.0-beta.0

node-saml/node-saml/releases/tag/v4.0.0-beta.0
only package which was released from node-saml github organizations repository. Related comments and commits:

https://github.com/node-saml/node-saml/pull/9#issuecomment-867070934
https://github.com/node-saml/node-saml/pull/9#issuecomment-867221819
https://github.com/node-saml/node-saml/commit/c72e6fa7c90a67bd6945746f6b1905f5b6471a03

3.1.0

zoellner/node-saml/releases/tag/v3.1.0

3.0.0

zoellner/node-saml/releases/tag/v3.0.0

2.1.1

zoellner/node-saml/releases/tag/v2.1.1

2.1.0

zoellner/node-saml/releases/tag/v2.1.0

2.0.0

zoellner/node-saml/releases/tag/v2.0.0

1.1.0

zoellner/node-saml/releases/tag/v1.1.0

1.0.0

zoellner/node-saml/releases/tag/v1.0.0

So what is the problem?
node-saml/passport-saml current official versions are e.g. 3.0.0, 3.1.0, 3.1.1, 3.1.2 furthermore node-saml github organization has this node-saml/node-saml repository.
There is a chance that someone would associate https://www.npmjs.com/package/node-saml packages prior to upcoming 4.0.0 with node-saml/node-saml and start to use them as if those would have been versions from node-saml/node-saml (while in reality those are versions from zoellner/node-saml). People might not pay attention to clear statement at the beginning of node-saml/node-samls README.md: https://github.com/node-saml/node-saml/tree/d6dfa17be751b08b20cd0b97ac10344604e95c3a#installation
Do you think that there are already such projects which might have mixed/combined codes from zoellner/node-saml with codes from node-saml/passport-saml?
It certainly looks like it. node-saml/node-saml/network/dependents lists at the moment ( 7th Sep 2021) following repositories:

ais-one/cookbook
perforce/helix-authentication-service

ais-one/cookbook introduced dependencies to node-saml 3.1.0 and to passport-saml 3.1.2 see ais-one/cookbook/pull/161/files#diff-32de16448be43475c0d4a8884d0c289e4dbd204cda959fc6ae01bb3a37409bb0. So there is mixture of quite old codes from zoellner/node-saml and quite fresh stuff from node-saml/passport-saml. Furhtermore ais-one/cookbook seems to be some sort of "template project library" which is used to spawn projects for different SW stacks (including node-js / express with aforementioned mixture of saml libraries). So if this was not intentional the problem is going to escalate quite rapidly ( ping @ais-one )
perforce/helix-authentication-service was already using passport-saml 3.1.0 but added dependency to node-saml 3.1.0 at commit helix-authentication-service/commit/31609ffd (see this package.json diff) and started to use SAML from node-saml 3.1.0 (see this routes/saml.js diff). So MultiSamlStrategy comes from node-saml/passport-saml 3.1.0 and SAML seems to be coming from zeollner/node-saml 3.1.0 (if I interpreted code correctly) and combination might not work well together. ( ping @nlfiedler )
I repeat: I do not know whether those two repositories started to use zoellner/node-saml library versions intentionally. Most probably those were accidents and it is quite easy to see how those could happen. If those were accidents these two examples were probably just a tip of the iceberg of similar issues at private repositories. Maybe there should/could be more visible statement about source of different versions at npmjs node-saml and at node-saml/node-saml pages.
ping @markstos @cjbarth @zoellner

Hi,
Thanks for the info, I am maintainer for the cookbook.
It was supposed to be from organisation. Did not realize and should have
installed package with org name.
This can indeed potentially be dangerous.
I will update within this week. Need to also remove the release with the
wrong library
On Wed, 8 Sep 2021, 2:47 am srd90, @.***> wrote:

At the moment (7th Sep 2021) https://www.npmjs.com/package/node-saml 's
release packages are different versions from zoellner/node-saml
https://github.com/zoellner/node-saml repository which was forked from
node-saml/passport-saml https://github.com/node-saml/passport-saml
quite some time (over a year) ago and started to live its own life after
that.
Later node-saml/passport-saml https://github.com/node-saml/passport-saml
was splitted to node-saml/passport-saml
https://github.com/node-saml/passport-saml and node-saml/node-saml
https://github.com/node-saml/node-saml modules. I believe plan was to
start releasing to https://www.npmjs.com/package/node-saml from
node-saml/node-saml https://github.com/node-saml/node-saml repository
after 4.0.0 (and versions prior to that at the npmjs node-saml are from
zoellner/node-saml https://github.com/zoellner/node-saml github
repository).
So at the moment versions at https://www.npmjs.com/package/node-saml are
(and corresponding sources for those versions are):

4.0.0-beta.0

node-saml/node-saml/releases/tag/v4.0.0-beta.0
https://github.com/node-saml/node-saml/releases/tag/v4.0.0-beta.0
only package which was released from node-saml github
organizations repository. Related comments and commits:

#9 (comment)
https://github.com/node-saml/node-saml/pull/9#issuecomment-867070934
#9 (comment)
https://github.com/node-saml/node-saml/pull/9#issuecomment-867221819
c72e6fa
https://github.com/node-saml/node-saml/commit/c72e6fa7c90a67bd6945746f6b1905f5b6471a03

3.1.0
zoellner/node-saml/releases/tag/v3.1.0
https://github.com/zoellner/node-saml/releases/tag/v3.1.0

3.0.0

zoellner/node-saml/releases/tag/v3.0.0
https://github.com/zoellner/node-saml/releases/tag/v3.0.0

2.1.1

zoellner/node-saml/releases/tag/v2.1.1
https://github.com/zoellner/node-saml/releases/tag/v2.1.1

2.1.0

zoellner/node-saml/releases/tag/v2.1.0
https://github.com/zoellner/node-saml/releases/tag/v2.1.0

2.0.0

zoellner/node-saml/releases/tag/v2.0.0
https://github.com/zoellner/node-saml/releases/tag/v2.0.0

1.1.0

zoellner/node-saml/releases/tag/v1.1.0
https://github.com/zoellner/node-saml/releases/tag/v1.1.0

1.0.0

zoellner/node-saml/releases/tag/v1.0.0
https://github.com/zoellner/node-saml/releases/tag/v1.0.0

So what is the problem?
node-saml/passport-saml https://github.com/node-saml/passport-saml
current official versions are e.g. 3.0.0, 3.1.0, 3.1.1, 3.1.2 furthermore
node-saml https://github.com/node-saml/ github organization has this
node-saml/node-saml https://github.com/node-saml/node-saml repository.
There is a chance that someone would associate
https://www.npmjs.com/package/node-saml packages prior to upcoming 4.0.0
with node-saml/node-saml https://github.com/node-saml/node-saml and
start to use them as if those would have been versions from
node-saml/node-saml https://github.com/node-saml/node-saml (while in
reality those are versions from zoellner/node-saml
https://github.com/zoellner/node-saml). People might not pay attention
to clear statement at the beginning of node-saml/node-samls README.md:
https://github.com/node-saml/node-saml/tree/d6dfa17be751b08b20cd0b97ac10344604e95c3a#installation
Do you think that there are already such projects which might have
mixed/combined codes from zoellner/node-saml
https://github.com/zoellner/node-saml with codes from
node-saml/passport-saml https://github.com/node-saml/passport-saml?
It certainly looks like it. node-saml/node-saml/network/dependents
https://github.com/node-saml/node-saml/network/dependents lists at the
moment ( 7th Sep 2021) following repositories:

ais-one/cookbook https://github.com/ais-one/cookbook
perforce/helix-authentication-service
https://github.com/perforce/helix-authentication-service

ais-one/cookbook https://github.com/ais-one/cookbook introduced
dependencies to node-saml 3.1.0 and to passport-saml 3.1.2 see
ais-one/cookbook/pull/161/files#diff-32de16448be43475c0d4a8884d0c289e4dbd204cda959fc6ae01bb3a37409bb0
https://github.com/ais-one/cookbook/pull/161/files#diff-32de16448be43475c0d4a8884d0c289e4dbd204cda959fc6ae01bb3a37409bb0.
So there is mixture of quite old codes from zoellner/node-saml
https://github.com/zoellner/node-saml and quite fresh stuff from
node-saml/passport-saml https://github.com/node-saml/passport-saml.
Furhtermore ais-one/cookbook https://github.com/ais-one/cookbook seems
to be some sort of "template project library" which is used to spawn
projects for different SW stacks (including node-js / express with
aforementioned mixture of saml libraries). So if this was not intentional
the problem is going to escalate quite rapidly ( ping @ais-one
https://github.com/ais-one )
perforce/helix-authentication-service
https://github.com/perforce/helix-authentication-service was already
using passport-saml 3.1.0 but added dependency to node-saml 3.1.0 at
commit helix-authentication-service/commit/31609ffd
https://github.com/perforce/helix-authentication-service/commit/31609ffdb14837a3a3fd46ec4d7e8bf9e70e35d0
(see this package.json diff
https://github.com/perforce/helix-authentication-service/commit/31609ffdb14837a3a3fd46ec4d7e8bf9e70e35d0#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519)
and started to use SAML from node-saml 3.1.0 (see this routes/saml.js diff
https://github.com/perforce/helix-authentication-service/commit/31609ffdb14837a3a3fd46ec4d7e8bf9e70e35d0#diff-5d385258ea74c59af8e9e29c703497818c30d6386f4dec75d75d3d8795ac3816).
So MultiSamlStrategy comes from node-saml/passport-saml 3.1.0 and SAML
seems to be coming from zeollner/node-saml 3.1.0 (if I interpreted code
correctly) and combination might not work well together. ( ping @nlfiedler
https://github.com/nlfiedler )
I repeat: I do not know whether those two repositories started to use
zoellner/node-saml library versions intentionally. Most probably those
were accidents and it is quite easy to see how those could happen. If those
were accidents these two examples were probably just a tip of the iceberg
of similar issues at private repositories. Maybe there should/could be more
visible statement about source of different versions at npmjs node-saml and
at node-saml/node-saml pages.
ping @markstos https://github.com/markstos @cjbarth
https://github.com/cjbarth @zoellner https://github.com/zoellner
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/node-saml/node-saml/issues/21, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAWBHRK5FQ4JCFUTK4UCLLUAZM2VANCNFSM5DS7HVJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

The current https://www.npmjs.com/package/node-saml clearly has it linked to my personal repo and it's been this way since the beginning. I'm standing by to switch it over to the org repo as soon as there is a final release version

Hi Andreas, my apologies.
I had edited my comments. The email u received on my comment was before I
did more research
On Wed, 8 Sep 2021, 3:53 pm Andreas Zoellner, @.***>
wrote:

The current https://www.npmjs.com/package/node-saml clearly has it linked
to my personal repo and it's been this way since the beginning. I'm
standing by to switch it over to the org repo as soon as there is a final
release version
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/node-saml/node-saml/issues/21#issuecomment-915005096,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAWBHWULN3ADWVU6ZEHBTDUA4I6HANCNFSM5DS7HVJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


No primary key

Setup
Versions

Rust: 1.54.0-nightly
Diesel: CLI: 1.4.1
Database: MySQL 8.0
Operating System Ubuntu Linux 20.04 LTS

Feature Flags

diesel: mysql

Problem Description
Whenever running migrations, Diesel CLI says that my table has no primary keys, no matter if I specify or not.
The tables are generated, however the schema.rs is not generated.
What are you trying to accomplish?
I am trying to use migrations to make a table and generate a schema.rs.
What is the expected output?
A schema.rs that contains the table.
What is the actual output?
Running migration 2021-05-13-190719_testing Diesel only supports tables with primary keys. Table hello_world has no primary key
However, the tables are created. The schema.rs is not generated.
Are you seeing any additional errors?
Yes. Whenever attempting to use foreign keys, it seems to issue the same problem. It implies that I have no primary keys on any table.
Steps to reproduce

Running diesel migration run
up.sql
CREATE TABLE hello_world (
    id int AUTO_INCREMENT PRIMARY KEY,
    title varchar(100)
)

Checklist

[x] I have already looked over the issue tracker  and the disussion forum  for similar possible closed issues.

[x] This issue can be reproduced on Rust's stable channel. (Your issue will be
closed if this is not the case)
[x] This issue can be reproduced without requiring a third party crate

Can you verify that there is no other table without primary key in your schema?
Also can you verify that the information schema contains the required information about the primary key?

Closed as I cannot reproduce this with mysql version 8.0.20. Feel free to add more details that could help reproducing this issue. Otherwise I would guess that there is another table without primary key in your schema. You can use SHOW TABLES in your mysql command line client to check for existing tables.


Home page icon gets hidden by view event button

In this site view event button keeps hiding the home button which is unpleasant to look and also kill good user experience.
I would like to change this into more user friendly issue.
Please assign me this issue under hectoberfest2024 !!

Thanks for creating the issue in WildGuard! The issue has been assigned to you.
Before you start working on your PR, please make sure to:

⭐ Star the repository if you haven't already.
Pull the latest changes to avoid any merge conflicts.
Attach before & after screenshots in your PR for clarity.
Include the issue number in your PR description for better tracking.

Don't forget to follow @anuragverma108 – Project Admin & @PriyaGhosal -Project Collaborator  – for more updates!
We're excited to see your contribution as part of Hacktoberfest 2024! 🎉
Happy open-source contributing!


Feature/user service

-Need to build up the jar file first

Syntax to run the main from jar file is as follows:
java -jar path/to/your/jarfile.jar fully.qualified.package.Application

steps to run spring-boot with maven on Mac:

brew install springboot
brew install maven
mvn spring-boot:run

Please remove all .DS_STORE files.

Add getUserByToken
Add generateToken

To test the new method (getIdByToken()) using postman:
Enter a random user Id and a given token to the path of a GET request to receive the actual expected user Id.
Example:
URI: http://localhost:8080/api/users/16/token?token=cfcd208495d565ef66e7dff9f98764da
In the path above 16 represents the random user ID and the value after the equal sign is the given token.
Response for above would include a JSON object like below:
{
"user Id" : "17"
}

Good job!
A few things to include in your next PR:

What happens if two people input the same information when signing up? (duplicate entities)
Remove the lines you commented out.

If you have more time:

make id and token as request variables so that they can be accessed like "api/users?token=cfcd208495d565ef66e7dff9f98764da" and "api/users?id=1"


Feature/spacer

Fixes PXBLUE-1452

Changes proposed in this Pull Request:

Added spacer, unit test, doc, storybook
Marking as draft bc having trouble adding it to showcase drawer

Tried enforcing flex on drawer but didn't work

Since RN does not support "display: inline" and "display: inline-block" etc, I had to use flex for the "static layout" story.
Checked on both iOS and Android -- what I have committed so far works cross-platform.

Screenshots:
(A functional spacer with a <Text> component as its child.)

question - we show use of spacer in drawer and makes sense but was wondering if this would be used anywhere? and would there be any need for padding and margins to support the spacer element.

question - we show use of spacer in drawer and makes sense but was wondering if this would be used anywhere? and would there be any need for padding and margins to support the spacer element.

Huayun and I were struggling to find a good example of where it would be used. Probably not so much in our component library, but I could see it being used by product teams to build their own components. It's not a heavy hitter on mobile since there's usually less space, but it could come in handy.
The Spacer will support padding/margins through the style prop, or the styles (root) prop.


Support network changes

Currently connecting marina with mainnet network makes the app crash

@tiero should be fixed.
Preview url: dex-nextjs-iota.vercel.app


Refactor Code and Externalise matplotlib Code

This issue has been raised to implement the suggestions in PR #9.  This was to:

Replace the outcome_probability and score_probability with methods called fixture (for games yet to be played) and result (for games for which the result is known). These will return a dict of details to ensure that we actually get the full set of Brier scores for the match outcome, predicted goals against actual goals scored by the home and away team and the predicted score (e.g. 2 - 0).
Externalise the plotting functions so they're not actually part of the Footy class (for now put that code into the Jupyter notebook.

Preview of the new fixture method documentation is available at https://github.com/FootyStats/footy/blob/feature/fixture_method/docs/index.md#fixturehome_team-away_team


gjs: 1.68.1 -> 1.68.2

Motivation for this change
https://gitlab.gnome.org/GNOME/gjs/-/blob/1.68.2/NEWS
Version 1.68.2
--------------

- Crash and regression fixes backported from the development branch.

- Build fix to adjust to GLib renaming its main branch.

- Closed bugs and merge requests:

  * Fix crash in ByteArray.fromGBytes / ByteArray.fromString with 0-length input
    [!628, Philip Chimento]
  * subprojects: Use GLib main branch [!633, Philip Withnall]
  * Construct-only properties and GTK Builder. [#422, !635, Carlos Garnacho]
  * Data corruption when passing a 0-terminated array of GVariant [#269, !636,
    Evan Welsh]
  * Fix race condition in dynamic module resolution. [!641, Evan Welsh]
  * Ensure the correct realm is entered in the async executor [!644, Evan Welsh]
  * Assertion failure in toggle refs with debug mozjs [#416, !646, Evan Welsh]

This PR replaces #132924.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

3 packages marked as broken and skipped:

gnome.gnome-documents
libsForQt512.discover
libsForQt514.discover

45 packages built:

adapta-gtk-theme
chrome-gnome-shell
flatpak
flatpak-builder
foliate
gjs (gnome.gjs)
glade (gnome.glade)
gnome-builder
gnome.anjuta
gnome.gnome-books
gnome.gnome-characters
gnome.gnome-maps
gnome.gnome-session (gnome.gnome_session)
gnome.gnome-shell (gnome.gnome_shell)
gnome.gnome-software
gnome.gnome-sound-recorder
gnome.gnome-terminal (gnome.gnome_terminal)
gnome.gnome-tweaks (gnome.gnome-tweak-tool)
gnome.gnome-weather
gnome.gpaste
gnome.polari
gnome.pomodoro
gnome.sushi
gnomeExtensions.drop-down-terminal
gnomeExtensions.easyScreenCast
gnomeExtensions.gsconnect
gnomeExtensions.night-theme-switcher
gnunet-gtk
gtkpod
haskellPackages.gi-ostree
libsForQt5.discover (libsForQt515.discover ,plasma5Packages.discover)
malcontent-ui
minishift
ostree
pantheon.appcenter
pantheon.elementary-session-settings
pantheon.sideload
phosh
rpm-ostree
tangram
vala-language-server
vimix-gtk-themes
whitesur-gtk-theme
xdg-desktop-portal
xdg-desktop-portal-gtk

Thanks.


Update info.plist

Made RightClick compatible with any frontApp

Thank you, but why is this useful? Just like the problem (introduced with later OS X versions) of this not working properly when on the Desktop (it ignores selections when right-clicking), so does the same happen with apps.
What’s the benefit, if it works generically and won’t let you act on what you might want? It also does not work in every app (like Atom).

I changed two things:
-removed the conditions that was making  sure the frontMost App was Finder
-made sure the forwarded event is to the frontMost App instead of Finder
In SourceTree and the Desktop it is working properly for me and just does nothing in not supported apps such as Sublime Text or Chrome.
I am on Yosemite 10.10.3
Jules Robichaud-Gagnon

Le 2015-05-09 à 05:59, Vítor Galvão<EMAIL_ADDRESS>a écrit :
Thank you, but why is this useful? Just like the problem (introduced with later OS X versions) of this not working properly when on the Desktop (it ignores selections when right-clicking), so does the same happen with apps.
What’s the benefit, if it works generically and won’t let you act on what you might want? It also does not work in every app (like Atom).
—
Reply to this email directly or view it on GitHub.

You were right about the Desktop however it does work in Xcode and SourceTree.

it does indeed work in Xcode, and on text selections, even! Nice surprise.
Thank you for the contribution.


Suggestion: Mark Start Vertex

When rendering the pattern for an inputted pattern string, it'd be nice if the start vertex was highlighted somehow so it's easier to see.

The first line of a pattern has a larger triangle indicator, and it also has the triangle despite not changing colors. If you look for that, you can find the beginning of the pattern.

After some other comments on the discord to add the feature you suggested, I've done so. The start and end of the pattern are now marked with special dots that match the color of the connected line.


show error  when npm dist-tag ls renative-template-hello-world

npm dist-tag ls renative-template-hello-world
FAILED with ERROR:
Command failed with exit code 1 (EPERM): npm dist-tag ls renative-template-hello-world
npm ERR! dist-tag ls Couldn't get dist-tag data for Result {
npm ERR! dist-tag ls   type: 'tag',
npm ERR! dist-tag ls   registry: true,
npm ERR! dist-tag ls   where: undefined,
npm ERR! dist-tag ls   raw: 'renative-template-hello-world',
npm ERR! dist-tag ls   name: 'renative-template-hello-world',
npm ERR! dist-tag ls   escapedName: 'renative-template-hello-world',
npm ERR! dist-tag ls   scope: undefined,
npm ERR! dist-tag ls   rawSpec: '',
npm ERR! dist-tag ls   saveSpec: null,
npm ERR! dist-tag ls   fetchSpec: 'latest',
npm ERR! dist-tag ls   gitRange: undefined,
npm ERR! dist-tag ls   gitCommittish: undefined,
npm ERR! dist-tag ls   hosted: undefined
npm ERR! dist-tag ls }
npm ERR! code E404
npm ERR! 404 Not Found - GET https://repo.huaweicloud.com/repository/npm/-/package/renative-template-hello-world/dist-tags
npm ERR! 404
npm ERR! 404  'renative-template-hello-world@latest' is not in this registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

you have a misconfigured ~/.npmrc. You're pointing all your packages to  https://repo.huaweicloud.com registry and the helloworld template is published to npm. You can point only the packages you need from huawei to that repo and leave the rest to npm.
@wateverscopefromhuawei:registry= https://repo.huaweicloud.com/repository/...

instead of
registry= https://repo.huaweicloud.com/repository/...

I change one line in the ~/.npmrc
registry=https://registry.npm.taobao.org/
instead of
registry= https://repo.huaweicloud.com/repository/npm


doc dependencies

The Readme doc should include dependencies needed to build the app.
For postmarketOS (Alpine based), I had to install:
openssl-dev
glib-dev
cairo-dev
graphene-dev
pango-dev
gtk4.0-dev

Thanks for this vap0rtranz, I've updated the README with your dependency list.
Regarding your missing file error, I think it may be due to the icons folder not getting copied to your installation path. Take a look using the RUST_BACKTRACE=1 to confirm.
Cheers

P.S. the binary was built but there was an error:
    Finished dev [unoptimized + debuginfo] target(s) in 13m 48s
     Running `target/debug/weather-mobile`
error: could not execute process `target/debug/weather-mobile` (never executed)

Caused by:
  No such file or directory (os error 2)

Did the above copying of icons solve your problem?


Is it possible to resume by keeping track of where the file left off?

If I keep the current chunk information stored on the server side, would it be possible to skip the re-check process and speed up resuming? or is the chunk array needed? (I am working with >200Gig files, so it takes a long time)

All the server-side check is really doing is seeing if the chunk file exists (unless you added some custom logic), so if you have fewer chunks to check (use a larger chunkSize), it should be much faster. Not sure if that answer is good enough for you.


[EVENT REQUEST] - Table 840 "Cash Flow Forecast" - Function CalcAmount()

Dear AL Development Team,
In Table 840 "Cash Flow Forecast", function CalcAmount, we need an event here:

//OLD CODE
procedure CalcAmount(): Decimal
begin
	CalcFields("Amount (LCY)");
	exit("Amount (LCY)");
end;

//NEW CODE
procedure CalcAmount(): Decimal
begin
	//Init New Code
	OnBeforeCalcAmount(Rec);
	//End New Code
	CalcFields("Amount (LCY)");
	exit("Amount (LCY)");
end;

New publisher:
[IntegrationEvent(false, false)]
local procedure OnBeforeCalcAmount(var Rec: Record "Cash Flow Forecast")
begin
end;

Thank you.
Luis.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 13321.


Network interface never reach disabled state

Even when the network interface is down, waybar shows it as disconnected, never as disabled.
My config:
"network": {
        "interface": "wlp0s12f0",
        "format-wifi": "wifi",
        "format-link": "no ip",
        "format-disconnected": "disconnected",
        "format-disabled": "disabled",
    },

I disabled the interface with rfkill block wifi, sudo ip link set wlp0s12f0 down, NetworkManager, netctl. Still shows as disconnected. I tried different settings for the interface or interval option, same result.
Waybar v0.9.18 on Arch Linux.

I have the same problem
It seems that now networkmanager does not pass the disconnect status from virtual networks to waybar
try
format-disabled: disabled
format-disabled-if-down: true
I think everything will work if you use wlan

For me after running nmcli radio all off it shows format-disconnected.
It shows for format-disabled if I reload waybar.

Can confirm: no matter if I put format-disabled-if-down: true, it only renders the format-disabled after a reload of the sway bar.


[Monitoring V2] Switch windows-exporter to upstream Prometheus community chart

A followup on https://github.com/rancher/windows/issues/223 to switch entirely from Rancher's maintained Windows Exporter chart to upstream.

on rancher 2.9-head (4dd0c38a2aab4f77271c07d2c887ecf5bbcea5e3):
tested on v1.29.5+rke2r1 - fresh install of 103.1.1+up45.31.1 -- pass
upgrade k8s to 1.30.1 -- pass


Player Waiting: Make more engaging, possibly with an animation

https://github.com/hto-projects/friendpardy/pull/209

https://github.com/hto-projects/friendpardy/pull/209


Support some way of grouping tasks across packages

Rationale
As you mono_repo grows in size, the number of travis jobs tends to increase dramatically. It would be nice if we had a way of grouping tasks across packages to run together in the same travis job.
For instance see a recent build on the build repo, https://travis-ci.org/dart-lang/build/builds/512125780?utm_source=github_status&utm_medium=notification. We now have 25 different analyze/format tasks, which spend the majority of their time in setup and not actually doing work. These should ideally be groupable into a single travis job (as an opt in).
Proposal
Add a group_stages (or maybe group_by?) key to the travis section of the mono_repo.yaml. This will accept a list of stage names.
We will create a single travis job (per sdk version) for each of those named stages.
This would reduce the number of travis jobs for the analyze_and_format stage in the build mono_repo to 4, from 25 (we test on 4 different sdks right now).

cc @grouma @kevmoo


[Feature] How to create a pkl file for inference? #3029

What is the feature?
Hello, I am a beginner.
How to create a pkl file for inference?
Files like this-->
Thanks!
Any other context?
No response

去原文档找生成.pkl的代码，然后自己照着抄一个就行了


Adds Support for OpenSearch

what
Updates the module so it supports AWS OpenSearch Domains:

Switches out TF aws_elasticsearch resources for aws_opensearch
Updates README and defaults as appropriate
Pegs to v4 of the AWS Provider

why

AWS OpenSearch has superseded ElasticSearch, hence this module needs to support it.

references

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/opensearch_domain

Actually reading https://github.com/cloudposse/terraform-aws-elasticsearch/issues/131 I agree that this should be moved to a new module.


DBT metadata ingestion through OpenMetadata / Airflow

Setup OpenMetadata in order to integrate with our DBT pipelines (as code, contained in the data product). List of integrations to be tested:
https://docs.open-metadata.org/v1.4.x/connectors/ingestion/workflows/dbt
The DBT ingestion can be configured manually from the OpenMetadata UI as per the following instructions:
https://docs.open-metadata.org/v1.4.x/connectors/ingestion/workflows/dbt/configure-dbt-workflow-from-ui
In our case, the manifest.json will be retrived from the GitHub repository for the completed data pipeline, via the File Server method.

We can successfully configure services and ingestion now in OpenMetadata and the airflow integration is working as expected. See example below for sample data product.

However the dbt ingestion is still not working as per #48


onTouchStart is not working on mobile view

🐛 Bug report
Current Behavior
The button is able to be functional with onClick and onTouchStart on the normal web view and mobile simulator on Chrome. However, when I tried on my phone, the button is not functional. It means it is not triggering any event from onTouchStart even though it works on the phone simulator on Chrome.
Please see the code below
  <button           onTouchStart={() => alert("ds")}           style={{ cursor: "pointer" }}           onClick={() => alert("Good day")}         >           Click me  </button>

Expected behavior
onTouchStart needs to be triggered on the mobile view.

Reproducible example

Suggested solution(s)

Additional context

Your environment

Software
Version(s)

Razzle
3.16

Razzle Plugins

Node
12.14.0

Browser

npm/Yarn
6.14.5

Operating System
Mac OS

TypeScript
3.9.3

React
16.13.1

Closing as it needs more info. Reopen if you provide a minimal example.

the same issue


Not an issue just a question

I pulled the root files from my v2 goggles and i wanted to ask what does the debug menu do.I kinda don't want to risk my goggles just asking if anybody has tried it.
https://ibb.co/f8X5PHL
https://ibb.co/D9FFRgC

Right now the few debug menu can be presented moving around some xml items but honestly not really much can be done right now. Don't worry about messing with XML UI files, but ALWAYS BACKUP FIRST, so in case you change something and the UI does not appear you can simply restore the original XML and UI will work again.
If a wrong XML setup is done, the UI won't boot up, but after restore to a valid version the system will work again.

Try with this gist
Is a modified racing_device_menu.xml which enable some debug menus.

so i just adb push it and reboot?

Yes, but before that rename the original file to .original

Oh i got it thanks btw.Just an idea maybe you should make a discord server so that people can share hacks and ideas

There is already a discord server, take a look on the readme of the project 😜

https://discord.gg/3rpnBBJKtU


Remove "Thread" from the Navbar

No file has been added for the Thread tab, so remove it from the navbar too.

i would like to it!

@Nikblaze sure


NO_ISSUE: Upgrade to<PHONE_NUMBER>0-SNAPSHOT

Ensemble:
https://github.com/apache/incubator-kie-tools/pull/2442
https://github.com/apache/incubator-kie-sandbox-quarkus-accelerator/pull/12

@tiagobento we need to update the accelerator to import the jbpm-quarkus-devui-bom, right now the project still relies that jbpm-quarkus-devui comes from the kogito-bom


Support p256, p386 and p512

This also introduces noalg keys so we can use arbiterary hashing algorithms with the keys. This breaks the existing keys.

Ah, 386 brings me back :D


prevent other mod's features from generating on the moon

If it's possible
Like forestry hive, witchery stuffs...etc
Also lava on the moon is a bit strange I think

This is planned as far as I understand.
Also @zmaster587 https://github.com/BuiltBrokenModding/SkyIslandGenerator/blob/master/src/main/java/com/builtbroken/skyislandgenerator/world/WorldGenWrapper.java

Last commit should prevent oil/buildcraft water/beehives/mod gen in general from spawning on the moon and uninhabitable planets

Still happening in 1.0.3 on MC 1.10 - Forestry Hives all over a moon
Also there are a Tinker's Construct's slime islands with slimes constantly suffocating so i think this worldgen  feature should be also blacklisted from moons


JavaScript part of turbolinks on npm

Copied from https://github.com/turbolinks/turbolinks-classic/issues/658. Many details can be found there.
@sstephenson, we probably just need a package.json added, and then either one of us can publish to https://www.npmjs.com/package/turbolinks
I can submit a PR for this if you like.

I have disabled asset pipeline and use webpack instead, so Turbolinks on NPM would be great. But wouldn't it also require or make sense to implement some kind of module.export into it? So when using webpack/browserify it can be required, and not be put on the window object?

also want to see torbolinks on elixir/phoenix, +1

+1 for the npm

@sstephenson @packagethief Given that the npm repo is live, we should either add the package.json here or I should do it from a fork and push up the latest.

@sstephenson @packagethief Unless there's object, this weekend I'll try pushing this from my own fork to npm. It's somewhat more official if people grabbing the npm version get this from the official repo, but we do this for jquery-ujs and nobody has complained.
FWIW, we had 72K downloads of the "unofficial version" last month: https://www.npmjs.com/package/jquery-ujs
https://github.com/shakacode/jquery-ujs

The reason we haven’t published Turbolinks to npm is because we don’t have a CommonJS module wrapper around the library.
I’m guessing most people are going to expect require("turbolinks") to work, which in turn suggests they’d want to avoid automatic initialization and the global Turbolinks object, which means the process for getting Turbolinks working becomes significantly more involved and requires additional documentation, not to mention changes to the native adapters … which is really something I’d just like to avoid entirely.

@sstephenson I'm not sure on the commonjs part being essential. I just want to have the file included like I include jquery-ujs. It's a global there as well.
Examples:

https://github.com/shakacode/react_on_rails/blob/master/spec%2Fdummy%2Fapp%2Fassets%2Fjavascripts%2Fapplication_non_webpack.js.erb#L9 which gets included here: https://github.com/shakacode/react_on_rails/blob/master/spec%2Fdummy%2Fapp%2Fassets%2Fjavascripts%2Fapplication_static.js#L22

https://github.com/shakacode/react-webpack-rails-tutorial/blob/master/app%2Fassets%2Fjavascripts%2Fapplication_non_webpack.js#L5
which gets included here:  https://github.com/shakacode/react-webpack-rails-tutorial/blob/master/app%2Fassets%2Fjavascripts%2Fapplication_static.js#L14

Is it fair to say this is more about supporting Webpack than having the package published to npm? I.e. if we were to document this, we would have a section in the readme under Installation called “Insatllation with Webpack” rather than “Installation with npm,” right?

FWIW, Trix, which is published on NPM, has a similar issue (https://github.com/basecamp/trix/issues/119) that's broader than using Webpack. There's also Browserify, require.js, and who knows how many other module loaders.

FWIW, the maintainer of browserify rails moved to webpack!
https://github.com/browserify-rails/browserify-rails/pull/153#issuecomment-200659517
I'd recommend supporting webpack and then let those interested submit PRs later or other module systems.

OK, great. 👍
@justin808 Could you open a pull request that adds a package.json file and Webpack instructions to the readme?

@sstephenson Is there a standard license to pick: https://docs.npmjs.com/files/package.json#license

MIT

Done! See #58
I've even deployed to Heroku here: http://www.reactrails.com/

Published 5.0.0-beta3 to npm: https://www.npmjs.com/package/turbolinks


Improve work with struct (record) types

This PR attempts to improve (mainly internal) work with record types in several ways:

Adds reference to the struct layout (the Struct type) into SizedType. This allows to access the record's fields directly from the expression type, without the need to fall back to bpftrace.structs_. In fact, the work with bpftrace.structs_ is now completely hidden from the users of SizedType.
Preserves the original order of struct fields. Since we now allow to print structs, changing the field order could confuse the user.
Unifies the internal structure of records and tuples (classes Struct and Tuple are merged). The only difference is that tuple fields have empty names.

This should resolve #1396.
Checklist

[ ] Language changes are updated in docs/reference_guide.md
[x] User-visible and non-trivial changes updated in CHANGELOG.md
[x] The new behaviour is covered by tests

One embedded test failed, a restart should resolve it.


Volar breaks @types/react in monorepo when using takeover mode

Version
Volar: 1.8.3
TypeScript: 5.1.6
Steps to reproduce

Clone https://github.com/sqal/volar-react-types-bug
Make sure takeover mode is enabled (@builtin TypeScript and JavaScript Language Features extension is disabled)
Install dependencies npm run i
Open apps/react-app/src/main.tsx
You can run npm run type-check to verify there's no issue in my app

What is actually happening?
I see a lot of Typescript errors reported in my app that I shouldn't see, e.g.
Type 'Element' is not assignable to type 'ReactNode'.

What is expected?
No Typescript errors in react-app since all the code is correct.
Any additional comments?
It looks like volar breaks @types/react when I have installed vue somewhere in my monorepo.  Follow these steps to verify:

Go to apps/vue-app and remove vue from the dependencies
cd ../../ & npm i
Restart volar's server or restart vscode
Now everything works fine in my react-app, there's no issues

Also running into this. We have a monorepo with a Vue 3.x app and a Node backend that uses react-email. Using Volar renders the React/JSX part of react-email and the .tsx files almost unusable to due the amount of false negatives in terms of type errors. Disabling Volar and re-enabling the builtin Typescript extension works fine, but isn't really a good option when working on a monorepo with Typescript and Vue apps.

We are seeing this issue as well in a vue project that with several dependencies that rely on react. For now we are staying on vue-tsc version 1.6.5, but we might have to simply ignore those errors in the future if this is not fixed. #3259 looks like an obvious candidate for where this issue might have been introduced. Given that PR was only meant to improve performance but broke multiple projects, simply reverting that change might be the better way.

This seems to be a TS internal bug, for https://github.com/sqal/volar-react-types-bug, you can create the following file for to reproduce the error with the built-in TS extension.
// apps/react-app/src/_types.d.ts
import 'vue';

#3259 changes have been reverted by #3279 since v1.7.12.
But anyway, #3534 will solve this problem. and 2.0 will also no longer require takeover mode.


[NEW FEATURE] Native step 2 : Multiple nodes running

In this second step of the Native development, our goal is to be able to run multiple Luos_engine binaries (nodes) to be able to list them during detection, and to make them communicate. We consider the step 1 ( #290 ) as completed
Or final goal will be to have the button running on another node that the Gate and still be able to catch it on the pyluos side :

To do that, our main focus will be on the Robus HAL.
Communication
To exchange information it could be great to rely on WebSocket and to be able to broadcast to all off them information. For broadcasting we could use MQTT with a broadcast topic.
This part is open to contribution and brainstorming
Detection
We will need to find a way to list other services and to send them node ID. To send them Id we need to be able to send a non broadcast message. If We use MQTT each node could create a topic with it's node name allowing anyone to reach this specific service.
This part is open to contribution and brainstorming

@AltayAkkus made a proposition on #292 then we plan a call to discuss about it. In this comment I will try to resume this discussion and define more precisely how we plan to develop this.
First considered solution
One of the big challenge  is that unlike half-duplex serial, websockets are point to point. Robus communication highly rely on the broadcasting aspect so to make it work the same we have to find a way to do that with WebSockets.
If we want any node to be able to broadcast to any other one we will have to list all the node on all the node and connect all the node to all the node allowing any node to send information to all other ones :

This is heavy for each nodes and the complexity and needed ressources will be multiplied by the number of node on the system.
To finish, this imply to have an efficient node detection system before being able to exchange information or to maintain a static list of node addresses...
Kept solution based on @AltayAkkus proposition
Instead of trying to emulate how Robus connections are made on each node we could centralise this emulation in a dedicated program:

This way nodes stay simple. They only need to connect to the Robus_emulator' program. Robus_emulator` will be able to list all the available nodes by listing the clients to its WebSocket server.
Communication
Each received messages will be re-sent to other nodes.
Detection
PTP signals will be emulated by specific PTP messages between nodes and Robus_emulator. Those messages are the only one that will be not re-sent to all the other nodes. Robus_emulator will be able to send a received poke from one PTP to the next available node. The state of each PTP connection will be an OR operation between the 2 ptp states, exactly the same way it's working on the real world.
Robus_emulator network representation
Nodes will be represented as a chained list allowing to add and remove nodes dynamically and reshaping the virtual network easily.
Also we will have a  structure representing PTP links and storing the calculated state of the line depending on the different states of the PTP pins:

At each PTP state update we will recompute the line state then send an update to the other node if this update change the line state (line = PTPA || PTPB)

What about ISR emulation ? To simulate critical sections and realistic robus network messages, it could be great to have such a feature. Well, it's interesting for QA ! But users don't care about that.

I personally would refrain from MQTT as service discovery.
First off MQTT is a huge protocol, that can do a lot of things, using this for service discovery is extremely overkill.
The Broadcast also works via my proposition, in the same way the "real" Luos works.
If we would use MQTT we would have to inject the data into the PTP lines again, from the WebSocket server et cetera.
WebSockets are very performant, not Gigabit performant, but like 4k messages a second performant, I don't think there is a need for optimization.
@JeromeGalan can you elaborate on the ISR emulation? Injecting a fault, that one Node stops responding/broadcasting?
You could add such tools to your enterprise software package :D Adding it as a native feature, hm I dont know.
Excuse me for being absent so long, I am back to work and have a lot of things to do unfortunately

@AltayAkkus , for sure ISR emulation mocking can be a usefull feature for testing, monitoring and injecting strange behaviour. I'd already have such a need in a past life. But it's more interesting in embedded. For native, the question is open.

Welcome back to work @AltayAkkus, to be honest we don't had any time either to work on this.


Add --edge-zone to the "az vm image" commands

Resource Provider
Compute
Description of Feature or Work Requested
Add optional parameter --edge-zone to the following Az.Compute cmdlets:
az vm image list
az vm image list-offers
az vm image list-skus
az vm image list-publishers
az vm image show
Note: this was inadvertently not done as part of the previous issue:
https://github.com/Azure/azure-cli/issues/15988
MS Docs:
https://docs.microsoft.com/en-us/rest/api/compute/virtual-machine-images-edge-zone
Minimum API Version Required
2020-12-01
Swagger Link
https://github.com/Azure/azure-rest-api-specs/blob/compute-2020-12/specification/compute/resource-manager/Microsoft.Compute/stable/2020-12-01/compute.json
Powershell PR
https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/776

Compute


Improvements to slotting conversions / TimeInterpreter

Issue Number
#1869 / #1960
Overview

[x] Block instead of using a singleEraInterpreter if we don't yet have a proper TimeInterpreter.
[x] Remove TODO; explain why delegation time conversion never should fail
[x] Replace TimeInterpreter IO with TimeInterpreter (ExceptT IO ErrPastHorizon)
[x] Add, test and use endTimeOfEpoch e instead of timeOf =<< firstSlotInEpoch (e+1). This is needed to stay inside the forecast range when showing next_epoch when the node is in-sync, in Byron. Fixes #1960
[x] Make next_epoch and network_tip optional in the API. When the node is still syncing the Byron chain, it cannot know any slotting info close to the current time. Solving related problem to #1960
[x] Revise the names of the constructors of TimeInterpreter

Comments

I thought queries in Shelley could fail. This is wrong. Once in Shelley (for now the final era), they have unlimited forecast range. However, if the node is in Byron, we need to be careful.

bors try

Connecting to mainnet, when the node is still syncing, I often see
cardano-wallet-shelley network information
ConnectionError (HttpExceptionRequest Request {
  host                 = "localhost"
  port                 = 8090
  secure               = False
  requestHeaders       = [("Accept","application/json;charset=utf-8,application/json")]
  path                 = "/v2/network/information"
  queryString          = ""
  method               = "GET"
  proxy                = Nothing
  rawBody              = False
  redirectCount        = 10
  responseTimeout      = ResponseTimeoutDefault
  requestVersion       = HTTP/1.1
}
 NoResponseDataReceived)

Other times I saw the response without the next_epoch or network_tip, which would be expected, but with an unexpected ready sync_progress status.
{
    "node_tip": {
        "height": {
            "quantity": 435869,
            "unit": "block"
        },
        "epoch_number": 20,
        "slot_number": 3925
    },
    "sync_progress": {
        "status": "ready"
    }
}

With synced node in Byron, looking good:
cardano-wallet-shelley network information
Ok.
{
    "network_tip": {
        "epoch_number": 207,
        "slot_number": 12408
    },
    "node_tip": {
        "height": {
            "quantity": 4481319,
            "unit": "block"
        },
        "epoch_number": 207,
        "slot_number": 12408
    },
    "sync_progress": {
        "status": "ready"
    },
    "next_epoch": {
        "epoch_start_time": "2020-07-29T21:44:51Z",
        "epoch_number": 208
    }
}

It seems to work as I'd expect against Byron mainnet now. After 4b76ac2 I don't see any weird errors, or wrong sync progress.
Preferably I should add a regression test.
But should be reviewable now.

Added syncProgress regression test -> 95a9564

bors try

I am a little bit reluctant with all these unsafeExceptT ... If the error indeed is a true exception that callers shouldn't look for handling, then why is it returned as a value?
If that unsafeExceptT is there as a quick'n'dirty way of getting everything compiled without creating proper error types, then this is wrong.

If that unsafeExceptT is there as a quick'n'dirty way of getting everything compiled without creating proper error types, then this is wrong.

No. The errors unsafeExceptT here could be thrown in #1909 too (with throwIO, but hidden in the NetworkLayer)
Where it matters the most, this PR adds proper error handling.

If the error indeed is a true exception that callers shouldn't look for handling, then why is it returned as a value?

There are cases where error handling is needed, and here are cases where it is not. There are also places that work fine in Byron;Shelley, but will need to be re-thought in Byron;Shelley;Gougen (the time of delegation changes, and pool retirements).

bors try

bors try

bors try

Waited for the "trying" branch to pass. Then pushed a little update that reshaping the git history and, lowering the "PastHorizon" error from Critical to Error. Here was the diff:
$ git diff HEAD origin/anviking/1869/improve-time-interpreter
diff --git a/lib/shelley/src/Cardano/Wallet/Shelley/Network.hs b/lib/shelley/src/Cardano/Wallet/Shelley/Network.hs
index 833ff04f2..971cfbfc4 100644
--- a/lib/shelley/src/Cardano/Wallet/Shelley/Network.hs
+++ b/lib/shelley/src/Cardano/Wallet/Shelley/Network.hs
@@ -1051,4 +1051,4 @@ instance HasSeverityAnnotation (NetworkLayerLog b) where
         MsgWatcherUpdate{}                 -> Debug
         MsgChainSyncCmd cmd                -> getSeverityAnnotation cmd
         MsgInterpreter{}                   -> Debug
-        MsgInterpreterPastHorizon{}        -> Error
+        MsgInterpreterPastHorizon{}        -> Critical


sugar withdraw

what does it command do? I didn't understand docs. I minted all my NFTs. What will happen if I use this command?

It will close your candy machine instance and withdraw all the funds locked up in it and give it back to you. However, any unminted items will be deleted, so you should only use this command when you are done minting from your candy machine.


Multiple warnings due to invalid casting

I tried to compile mnist_reader.hpp and found errors like this:
It's because in the source code you can find the following castings that I believe to be invalid
         if (limit > 0 && count > limit) {
-            count = limit;
+            count = static_cast<unsigned int>(limit);
         }

I'll contribute PR for this a bit later. If you can't merge it immediately please suggest how to fix this PR. Thanks.

Hi savoptik,
Thanks for reporting that.
Can you tell with which compiler did you use to get a warning. And can you show the entire warning message from the compiler?
Thanks

Apple LLVM 10.0 from apple Xcode.
./mnist_reader.hpp:92:21: Implicit conversion loses integer precision: 'std::size_t' (aka 'unsigned long') to 'unsigned int'
And these warnings are about 6 PIECES.
Отправлено с Mac

20 дек. 2018 г., в 21:32, Baptiste Wicht<EMAIL_ADDRESS>написал(а):
Hi savoptik,
Thanks for reporting that.
Can you tell with which compiler did you use to get a warning. And can you show the entire warning message from the compiler?
Thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/wichtounet/mnist/issues/7#issuecomment-449093471, or mute the thread https://github.com/notifications/unsubscribe-auth/AiaN0kq1m5forCM70VpFJnMiWRhVqr9bks5u69e0gaJpZM4Zcbmv.


Add Scool Bochra

@ManbizBochra cscapitale.txt I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!


"WARNING: the gcp auth plugin is deprecated" come up even if followed all the instructions

I'm working with the gke cluster and have got a warning for any kubectl command.
W0509 17:55:55.415853  113282 gcp.go:120] WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.25+; use gcloud instead.
To learn more, consult https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke

Versions.
$ k version
W0509 18:01:34.450905  114335 gcp.go:120] WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.25+; use gcloud instead.
To learn more, consult https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.0", GitCommit:"4ce5a8954017644c5420bae81d72b09b735c21f0", GitTreeState:"clean", BuildDate:"2022-05-03T13:46:05Z", GoVersion:"go1.18.1", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"20+", GitVersion:"v1.20.15-gke.3400", GitCommit:"750002971a60d8a06e0a403c52724257f0f68481", GitTreeState:"clean", BuildDate:"2022-03-08T09:33:43Z", GoVersion:"go1.15.15b5", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.24) and server (1.20) exceeds the supported minor version skew of +/-1

I went to the page with instructions and installed a component with the apt-get command, updated bash, reconnect to the cluster and etc. But I still had been seeing the warning.
I said ok, my bad. Lets do it right way and install the component with gcloud components install gke-gcloud-auth-plugin command. But I was not able becuase I had installed google cli with the apt, so I reinstalled the gcloud cli, and did all the required operations described in the instruction. The result is the same and lame warning that pretty annoyes me.
The bottom line is that I did follow every instruction described in the doc and 2 ways but still see the warning. There are 2 ways. Or I do something wrong or I take the audacity to say we got a bug here.

This happened to me as well when upgrading kubectl to v1.24. I ended up downgrading back to v1.22

Can we have a way to disable this warning? It seems counter-productive.
Thank you!

@adam-epam  As far as I've seen on the internet there is no way to suppress the warning in kubectl ;/

might be wrong

Hello,
On my side I'm using a KUBECONFIG file, in which the auth-provider name is set to gcp
And I have this deprecated message too.
I don't know on which auth-provider name I should switch to be able to use the recommended gke-gcloud-auth-plugin.
any ideas ?
Thank you very much

Warning started appearing today, followed the instructions and still have the warning. Also in the KUBECONFIG file still have the auth provider set as gcp as @lasdou is mentioning below.
Any ideas?

I identified the problem, at least for my case... I had a wrong kubectl binary on my machine.
Seems that kubectl command I was using was from docker... I assume minikube.
I had to install kubectl from this guide and at the end had this warning:

WARNING:   There are other instances of Google Cloud tools on your system PATH.
Please remove the following to avoid confusion or accidental invocation:
/Applications/Docker.app/Contents/Resources/bin/kubectl

Just deleted that binary and problem solved.

@lbanchero your suggestion worked for me. I had installed minikube with brew and the version of kubectl that came with it was being used by my shell. Here is what I did:
$ brew uninstall kubectl --ignore-dependencies
$ gcloud components install kubectl
$ mv /Applications/Docker.app/Contents/Resources/bin/kubectl /Applications/Docker.app/Contents/Resources/bin/kubectl.bak

I note that the version installed by gcloud was v1.23.3 but the version I had previous from minikube was 1.24.0

I think the gcloud documentation has the flag set backwards.
I changed
USE_GKE_GCLOUD_AUTH_PLUGIN=False
to
USE_GKE_GCLOUD_AUTH_PLUGIN=true
~/.kube/config looks correct and I don't get the warning.


rebase: update golang.org/x/text to 0.3.6

update text package to 0.3.6 to fix  CVE-2020-28851
more details at https://github.com/golang/go/issues/42535 and https://bugzilla.redhat.com/show_bug.cgi?id=1922730
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>

What pulls this in? Can we not update the direct dependency that requires this package?

different vendors use different versions of text packages as this is a CVE it's good to stick to a version instead of identifying all the dependencies and updating all.

we already update the same package previously https://github.com/ceph/ceph-csi/pull/1497

If its only used for e2e and we don't need to fix this then we can close the PR and bug.
Thanks @nixpanic

we already update the same package previously #1497

That probably was not needed either. We should look into updating gomega instead:
$ go mod why -m golang.org/x/text
# golang.org/x/text
github.com/ceph/ceph-csi/e2e
github.com/onsi/gomega
github.com/onsi/gomega/matchers
golang.org/x/net/html/charset
golang.org/x/text/encoding

As we only pull in the package for e2e testing, I do not see a (strong) need to update the package with a replace in go.mod.


Minor Grammar Mistake Change

Under the "Configure access policies on resources" subheading, the wording was "...you might need to configure addition permissions on resources...". This was changed to "...you might need to configure additional permissions on resources..." since the word "addition" is not an adjective, which breaks grammar rules.

@bak-minsu : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; thanks.


Trim client names

Elaboration:
@RequiresAuthentication(clientName = "HeaderClient,AnonymousClient")
A space between the comma and AnonymousClient seems to cause some breaking issues.
Thanks for tracking!

PR: https://github.com/pac4j/pac4j/pull/511


Create a Business Service Using CDS

Tutorial URL: https://developers.sap.com/tutorials/cp-apm-01-create-business-service.html
In step 4, Test-run the service, the provision fails with an error message:

Could not create the 'Bookshop-Bookshop-hdi-container-D0c+OyVcyZOKxAkjEv' instance of the 'hana' service type for the 'Bookshop-hdi-container' resource. Could not create the 'Bookshop-Bookshop-hdi-container-D0c+OyVcyZOKxAkjEv' service instance. Failed to select a database for instance 5ac6723f-0b39-4819-99be-8a401b37cad5, no database mapped to organization 'a2f76378-b6d5-476c-ae43-da59bbaece64' space '1dff411e-3bb0-4734-8fe5-5f0a95a53f52'

The Hana entitlement is assigned to the correct space. A look at #2925 suggests the error might be related to the data center I'm working from (us30). I couldn't test in other regions because my account is not entitled to Hana there.

@chgeo can you help Johann with this issue?

Mere HANA entitlements are not sufficient.  Please check if there is a service instance of type 'hana-db' available for your space, which represents an actual HANA DB.
See here for how to create such an instance, and here to map it to different spaces within the same organization.

I do not have the hana-db service available to me. Is it even a part of the free Cloud Platform trial? If not, the tutorial cannot be completed with a free account, right?

Ok, so you are using a trial landscape?
I know there is a free HANA trial in eu10, but for us I am not sure.  @AlexRieder can you answer this?

The error I posted initially does not occur in eu10. I can create a hanatrial there without any problems, but not in us30, so something must be different there...

Yes, we would need a statement on HANA availability on us30 here, which is why I pinged @AlexRieder.

As far as I know there is no HANA on us30 (GCP) would it be an alternative to use us10?

Sure. Maybe making sure that Hana is available in the selected region should be added as a tutorial step, then.

@Apfohlmann can you add a statement for HANA in the prerequisites of the tutorial?  We shouldn't mention landscape names, though, since this is subject to change, but tell that HANA needs to be available in the trial account.

Apart from that, let's close this issue.

@chgeo I will add it to the tutorial.
@thecodester you can close this issue.


fix: input.css being public

Problem
Closes #328 being /assets/css/input.css being publicly accessible when using tailwind with htmx
Description of Changes:

moved /assets/css/input.css to /styles/input.css this makes it explicit that these are styles and will not be included in assets

Checklist

[ x ] I have self-reviewed the changes being requested
[ x ] I have updated the documentation (check issue ticket #218)

I also saw that when creating htmx project without tailwind no output.css file is being created. I did not change the code as I was unsure if that was the desired behaviour and if output.css will be the correct name for it as output.css felt not the right name for it.

@mdelapenya Can you check the issue that the linter caches?
Run cd gorilla-mux
Error: internal/database/database_test.go:27:3: undefined: testcontainers (typecheck)
		testcontainers.WithWaitStrategy(
		^
Error: Process completed with exit code 1.

I dont know but I have a hunch if we just run the tests again manually they will pass :D

I

I dont know but I have a hunch if we just run the tests again manually they will pass :D

I reran them twice, and they failed both times.

I cloned this branch and tried to reproduce it locally and the CI error happens to me too: But it's not related to testcontainers, but in the previous step, the "build templates" one (see https://github.com/Melkeydev/go-blueprint/actions/runs/12074694415/job/33715796303?pr=345#step:7:22)

25l/ Preparing...- Preparing...\ Preparing...| Preparing.../ Preparing...- Preparing...25h1002l1003l2024/11/29 19:34:02 Problem creating files for project. open /home/runner/work/go-blueprint/go-blueprint/chi/cmd/web/styles/input.css: no such file or directory
Error: open /home/runner/work/go-blueprint/go-blueprint/chi/cmd/web/styles/input.css: no such file or directory
exit status 1

If you take a look at the Integration tests pipeline, they all pass.

I think that shell script should exist the pipeline at the moment it fails, not continuing the workflow

I cloned this branch and tried to reproduce it locally and the CI error happens to me too: But it's not related to testcontainers, but in the previous step, the "build templates" one (see https://github.com/Melkeydev/go-blueprint/actions/runs/12074694415/job/33715796303?pr=345#step:7:22)

25l/ Preparing...- Preparing...\ Preparing...| Preparing.../ Preparing...- Preparing...25h1002l1003l2024/11/29 19:34:02 Problem creating files for project. open /home/runner/work/go-blueprint/go-blueprint/chi/cmd/web/styles/input.css: no such file or directory
Error: open /home/runner/work/go-blueprint/go-blueprint/chi/cmd/web/styles/input.css: no such file or directory
exit status 1

If you take a look at the Integration tests pipeline, they all pass.

Well @mdelapenya thank you for pointing out where it was failing. I was able to fix the issue as the command was actually failing. can you tell me the process of how you run the tests? I couldn't find any documentation related to that.

just so you know it is fixed now @Ujstor @Melkeydev

I also saw that when creating htmx project without tailwind no output.css file is being created. I did not change the code as I was unsure if that was the desired behaviour and if output.css will be the correct name for it as output.css felt not the right name for it.

We implemented just a bare-bones example without CSS, but we could add custom, simple CSS. For now, I am accepting the current implementation, and you could open another PR if you are interested.


Felix community page links mobile

@sonylomo, thanks for adding the links. I think it would be better if we used the Link tags instead of the generic a when working with react-router-dom.

As a best practice, Link is used when navigating to relative URLs provided by React Router e.g /events, /community e.t.c. However, a is for user-clickable hyperlinks to external pages/ absolute page links e.g "https://...`.

@sonylomo, thanks for adding the links. I think it would be better if we used the Link tags instead of the generic a when working with react-router-dom.

@Ase020 As a best practice, Link is used when navigating to relative URLs provided by React Router e.g /events, /community e.t.c. However, a is for user-clickable hyperlinks to external pages/ absolute page links e.g "https://...`. WDYT?

Ok. For this case, let's go with the a tags. Thanks for this new info. Everyday we learn something new.😅


sc.urls() call doesn't seem to be implemented

The sc.urls() call in the readme fails for me. Scanning the source tree I cannot find an implementation. What's up with that?

This seems to be related to https://github.com/itsmemattchung/speedcurve.py/issues/47
I've found that if I make a request with browsers='Chrome' (i.e. something other than 'all'), this works
E.g.
urls = site.urls
url = urls[0]
response = sc.url(url['url_id'], days=1, browser='chrome')

This seems to be related to #47

I've found that if I make a request with browsers='Chrome' (i.e. something other than 'all'), this works

Thanks for finding a workaround for this (and apologize for my long absence). I'm unsure why this doesn't work, considering that Speedcurve's official API actually defaults the browser to all, according to their documentation: https://api.speedcurve.com/#get-all-tests-for-a-url
In any case, I'll write a new integration test, verifying that the urls method is implemented as documented.

No worries, other things I've found:

The sites/ returns the supported browsers for the particular site e.g.

This is part of the response:
"browsers":[{"browser_id":"apple-iphone-6-plus"},{"browser_id":"chrome"}]

So users need to ensure they are requesting browsers that are configured for their site.

If you don't specify a browser param, this should return all browsers by default

Hope that helps! :)


Implement Filetree context menu

fixes #511

Note: since the context menu conflicts design-wise with the multiselect, we will disable it in #543

This is looking good @guergana !!
The "Do not show this again" does not seem to work. It keeps appearing every time I upload a file.

I checked it on Mac. I agree that there is still something going on the context menu within folders.
There is another problem. Faith adapted the original context menu to make it more generic (check comment added on the ticket a couple of weeks ago). We need to implement the generic option because we will have inconsistencies, like this one:

What I did for this case is to open the folder. @romicolman I have pushed a new commit with this solution:

What do you think?

Hi! I think there is a confusion. Right now, I see this:

Open Folder Location - The ODE folder where this file exists

The description creates confusion since we are distinguishing between folders and files in the app and in the sentence we are mixing both elements (The ODE FOLDER where this FILE exists)

Delete file - Only removes this file from the ODE folder

Again, mixed language.
This is my suggestion:
Add the same text for context menu on files and folders:

Open Location - The ODE folder where this element exists
Delete - Removes this element from the ODE folder

Hi! I think there is a confusion. Right now, I see this:
1. Open Folder Location - The ODE folder where this file exists

The description creates confusion since we are distinguishing between folders and files in the app and in the sentence we are mixing both elements (The ODE FOLDER where this FILE exists)
2. Delete file - Only removes this file from the ODE folder

Again, mixed language.
This is my suggestion:
Add the same text for context menu on files and folders:
1. Open Location - The ODE folder where this element exists

2. Delete - Removes this element from the ODE folder

oh, yes, i missed one of the names. @romicolman could you check again?


React to Roslyn rename of NullableContextOptions to Nullable.

Verified the fix with VS16.2-preview1 + latest CLI with modified Nullable entry on disk
Updated tests.
Note: This change will not pass the build until we have a new CLI that has an updated Roslyn that understands Nullable.

aspnet/AspNetCore#10218

How exactly is this going to work? Are Roslyn changing this for preview 6? This means at some point anyone who wants to use the components/mvc solution will need to get onto 16.2

Another wrinkle to consider is source-build and the bootstrapping problem. To build .NET Core of Linux distros, we need a prior version of .NET Core. At the moment, that prior version is the latest stable release (right now Preview 5). We either need a way to stage these kinds of breaking changes between previews, or a way to flow the newer compiler independently of the one bundled with the SDK.

@NTaylorMullen try applying this change to your PR: https://github.com/natemcmaster/AspNetCore-Tooling/commit/b416204aa5b5b8773b33b54deb216955ac556a94

@NTaylorMullen try applying this change to your PR: natemcmaster@b416204

Done, lets see if it builds 😄

FYI there is a new version of the compiler coming along soon. The next bot-PR which updates Arcade will have this. cref https://github.com/dotnet/arcade/pull/2856

@NTaylorMullen - we should make this change at our earliest available point.

@aspnet/build looks like I need to wait for preview6 to be in Arcade. Any update on that happening soon?

Turns out you should be able to use a newer SDK before then. @JunTaoLuo did you get the needed steps / doc from @markwilkie ?

Yes, in fact, it has already been applied. I have repro'ed this locally so I'm trying to see if I can figure out what's going on here.

I've resolved two issues: released preview 6 SDK does not have the compiler option rename NullableContext => Nullable, newer runtimes require a restore with Microsoft.NETCore.App.Host.{RID}.nupkg. The one remaining is that it seems like a different compiler is used for desktop apps? I see the following failures:
    Build_Components_WithDesktopMSBuild_Works [FAIL]
    Build_ProjectWithDependencyThatReferencesMvc_AddsAttribute_WhenBuildingUsingDesktopMsbuild [FAIL]
    Build_SimpleMvc_WithServer_UsingDesktopMSBuild_CanBuildSuccessfully [FAIL]
    Build_SimpleMvc_UsingDesktopMSBuildAndWithoutBuildServer_CanBuildSuccessfully [FAIL]
    Build_SimpleMvc_UsingDesktopMSBuildAndWithoutBuildServer_CanBuildSuccessfully [FAIL]

And they have the signature:
 "C:\Users\vsagent\AppData\Local\Temp\Razor\x1ejfjii.lfs\MvcWithComponents\MvcWithComponents.csproj" (Restore;Build target) (1) ->
      (WarnForExplicitVersions target) ->
        F:\workspace\_work\1\s\.dotnet\sdk\3.0.100-preview7-012517\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.targets(192,5): warning NETSDK1071: A PackageReference to 'Microsoft.NETCore.App' specified a Version of `3.0.0-preview7-27819-07`. Specifying the version of this package is not recommended. For more information, see https://aka.ms/sdkimplicitrefs [C:\Users\vsagent\AppData\Local\Temp\Razor\x1ejfjii.lfs\MvcWithComponents\MvcWithComponents.csproj]

      "C:\Users\vsagent\AppData\Local\Temp\Razor\x1ejfjii.lfs\MvcWithComponents\MvcWithComponents.csproj" (Restore;Build target) (1) ->
      (RazorCompileComponentDeclaration target) ->
        F:\workspace\_work\1\s\src\Razor\src\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.Component.targets(224,10): error MSB4064: The "Nullable" parameter is not supported by the "Csc" task. Verify the parameter exists on the task, and it is a settable public instance property. [C:\Users\vsagent\AppData\Local\Temp\Razor\x1ejfjii.lfs\MvcWithComponents\MvcWithComponents.csproj]
        F:\workspace\_work\1\s\src\Razor\src\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.Component.targets(189,5): error MSB4063: The "Csc" task could not be initialized with its input parameters.  [C:\Users\vsagent\AppData\Local\Temp\Razor\x1ejfjii.lfs\MvcWithComponents\MvcWithComponents.csproj]

          1 Warning(s)
          2 Error(s)

      Time Elapsed 00:00:17.04

released preview 6 SDK does not have the compiler option rename NullableContext => Nullable

Oh damn that's nuts. That means Roslyn inserted a different version into VS for preview6 than exists in the CLI. This is a non-starter for this release then. We don't want to move AspNetCore all the way up to using preview7 bits but that's what this PR would require for both repos. I'll postpone this until preview7 is released and we've moved both our repos to preview7.
@JunTaoLuo Really appreciate your help looking into this, saved us from catastrophic failure 😉.

Double check the Roslyn version in VS and CLI, I'm surprised that they inserted different versions.

Double check the Roslyn version in VS and CLI, I'm surprised that they inserted different versions.

It's possible they inserted a preview7 flavor into VS; however, I do know they inserted it because we were exploding VS without their fix 😄

@NTaylorMullen - should this be closed?

@NTaylorMullen - should this be closed?

Nope, waiting for preview7 to be released and then for this repo to consume the preview7 sdk.


How to rerender RSC?

How can we rerender(refetch) RSC to show updated data?

@Regaron We have undocumented API now in latest version of next.js could let you do that. Docs update will come soon.
Example
import { unstable_useRefreshRoot } from 'next/rsc'

export deafult function Page() {
   cons refresh = unstable_useRefreshRoot()
   // ...
   return <Content><button onClick={refresh}>update</button></Content>
}

Would love to hear the feedback from you


[Card group - default] Research whether - light variant - no URL

User Story

As a [user role below]:
DDS engineer

I need to:
investigate whether the current Web Components and React [Card group - default] components support a light variant and passing of no URL to create a static version of the Cards

so that I can:
help determine whether additional work is needed to support the AEM Product template

Additional information

{{user research}}
{{user insights}}
{{user metrics}}

Acceptance criteria

[ ] Investigation summary by the EOD Friday, May 7 posted to Slack and this issue.

Functional specs don't really have anything that should block this from happening.
Light and "static or default" context can be found on Carbon's tile page.

We might need to enable some sort of optional border, so functional specs will be needed at the very least for that.

React

allows for no URL (CTA arrow icon will always appear though)
light variant not possible, but should be easy fix
no border option

Web component

does not allow URL (if remove URL it looks completely broken)
light variant not possible
no border option


Edits based on comments + none policy implementation

Additional test cases
Enable none policy by default

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Updates from feedback including unit test cases + none policy by default
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Closing #38 and combining updates with this PR, will need rebase after #79343 is merged
Does this PR introduce a user-facing change?:

LGTM


[DASHBOARD] Restarting dockers removes images from existing posts

Problem is only for development, on staging and beta it works fine.


Restores stereoscopic functionality with SceneKit + SpriteKit on iOS …

Fixes Issue #20: Restores stereoscopic functionality when using Scenekit + Spritekit on iOS9

Hey @AnBi2199, thanks for you contribution!
Could you upload elsewhere a minimal example using SceneKit + SpriteKit so I can properly test this issue? Thanks.

Example Code:
http://pastebin.com/uNw7SirA (expires in 1 week)
first 5 lines describe what to import in the header file

Hi @AnBi2199,
I have tried this method (moving the line to the end like you did) and it didn't actually work. The left side of the screen was still cleared when the object that has the SpriteKit scene as a material was being rendered.
Please have a look at the comments on the Issue that you raised #20


@alloy => Force cache all framework based Fonts on app launch

Fixes https://github.com/artsy/eigen/issues/588
When we first made Eigen, we debated using JSON files to set up all UI, so that we could make layout changes realtime. See ARTheme - Example JSON. This is the “QA fix” rather than a  full fix which pre-caches fonts before the firstVC is set up.

https://github.com/artsy/eigen/issues/602 is the issue for a full fix

Can you add a beta changelog?

fpush'd

Superb!


Quickfix currencies select options not visible

fix #148
screen-shot a bit foggy, it's on a VM

Thanks!


Kotlin App Build Issue

I am developing the app using Kotlin and found error while using the com.firebaseui:firebase-ui-auth:3.3.0
Describe your environment

Android device: _____
Android OS version: _____
Google Play Services version: 11.8.0
Firebase/Play Services SDK version: 11.8.0
FirebaseUI version: 3.3.0

Step 3: Describe the problem:

Not able to use the FirebaseUI with Kotlin

Steps to reproduce:

Add FirebaseUI version 3.3.0
Build the App
Error occured

Observed Results:
*Error in Gradle Console

What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.

java.lang.RuntimeException: java.lang.RuntimeException: com.android.builder.dexing.DexArchiveMergerException: Unable to merge dex

Relevant Code:
implementation 'com.firebaseui:firebase-ui-auth:3.3.0'

Have you checked to ensure you've not hit dex limit?

Yes I believe @btrautmann is right.  @JitenderSha please see: https://developer.android.com/studio/build/multidex.html


Comb Sort | Python

Title - Comb Sort Algorithm
what will change -
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code
[ ] Improving Code
[ ] Improving Documentation
[ ] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[x] Python
[ ] C++
[ ] Java
[ ] C
[ ] Go
[ ] Other language

Self Check

Ask for issue assignment before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Happy Coding,

@div-bargali Hey, Can you please assign this issue to me?

Can you assign me this issue? I can do it in either C++ or Python

Hey, I would like to work on this issue. Please assign it to me.


[Feature]: @rspress/core need cjs output

What problem does this feature solve?
@rspress/core need cjs output
What does the proposed API look like?
@rspress/core need cjs output

What scenarios require cjs output?

What scenarios require cjs output?

I don't want to use the rspress CLI method; I want to manually import rspress/core and implement the build myself. This way, I can migrate my old project and seamlessly convert the configuration.

I don't want to use the rspress CLI method; I want to manually import rspress/core and implement the build myself. This way, I can migrate my old project and seamlessly convert the configuration.

I think the JS Api of esm format is available to meet your demands.

I don't want to use the rspress CLI method; I want to manually import rspress/core and implement the build myself. This way, I can migrate my old project and seamlessly convert the configuration.

I think the JS Api of esm format is available to meet your demands.

butr, my current CLI is in CJS format, and importing @rspress/core results in an error，just like  since No "exports" main defined in<EMAIL_ADDRESS> How should I solve this problem?

use ESM packages in CJS is a classic topic, you can search a lot of information or articles in Google. eg. https://antfu.me/posts/publish-esm-and-cjs

We shipped pure ESM packages to advocate the ecosystem to move from CJS to ESM at the beginning, so we do not plan to lean to dual package.

We shipped pure ESM packages to advocate the ecosystem to move from CJS to ESM at the beginning, so we do not plan to lean to dual package.

okay，thx


How to enable cors in HybirdWebview

How to enable cors in HybirdWebview?

@ndq2002 for the most part there shouldn't be a need to enable CORS because there are no web requests going on in typical scenarios. All the resources are static and loaded locally.
Can you show a code example of what you'd like to do, but doesn't work?

We are getting CORs errors when trying to access user information from AWS and when trying to load map data from Google Maps. We implemented a traditional hybrid webview for XF and do not see these errors.

Can you share a snippet about what code is running when the CORS error happens? Is it JS code that is part of the MAUI HybridWebView app doing a fetch() to an AWS location?

@ndq2002 @mnasers afaik all request are done with <IP_ADDRESS> domain in header, when using Blazor/Hybrid web view. This can be behind problems you're facing. hth

Hello,
Thanks for the response. I thought I was getting CORs errors due to the AppOrigin being set to <IP_ADDRESS> but I believe the CORs error I am receiving is due to the JavaScript code trying to call Google Maps directly. I think if we change it so our server makes the call to Google Maps instead, it will resolve the error.
There were other resources not loading that I thought were also due to CORs errors but it was because their mime type (.svg) wasn't included in the case statement inside CoreWebView2_WebResourceRequested.


Command to get another player's position

Expand the existing ::pos command to support ::pos [player], which displays the position of the specified player.

Should require moderator rights to use.
Should display something like "Player [playername] is not currently online." if the specified player is not logged in.

Mentoring from the project maintainers is available for anyone who wishes to work on this issue - please join our Slack team (link in the main project README) and let us know.

I assume this is an issue for beginners (from the mentoring label)?

Yes, absolutely, maybe we can make the labels clearer. Slack is probably the best way to ask for assistance, in #plugin-help.


Is it possible to make Nightlight compatible with sVim link hints

I opened an issue about it in sVim repo here:
https://github.com/flipxfx/sVim/issues/101
But I think it's something only Nightlight can fix.
With Nightlight on:

WIth Nightlight off:

As you can see, the letters in the colored boxes are clearly seen in the off version.
I would love to have both extensions work well together. I really rely on sVim for my work and I am loving using Nightlight now that Mojawe has been released.
Thank you.

I would recommend you set a custom style for .sVim-hint in sVim's settings, marking the background-color and color with !important.
You could also customize Nightlight by putting custom CSS for .sVim-hint in the injected script (GENERAL-HACKS seems like the logical place to put it).
I am against the idea of tailoring to a specific user's environment; that should be left to your own fork.