StrategyViolatesRelationVariableMergeError when automergetohead a not-head conn.

I would like to use two connections to represent two users in my app to update data. But automergeothead seems not what I expected. I expect every conn can automergetohead directly.
two tutd connections
(1st tutd)
TutorialD (master/main):  a := true
TutorialD (master/main): :automergetohead union master

(2nd tutd)
TutorialD (master/main):
(enter after 1s tutd automergetohead. Not head anymore.)
TutorialD (<unknown>/main):
TutorialD (<unknown>/main): b := true
TutorialD (<unknown>/main): :automergetohead union master
ERR: MergeTransactionError StrategyViolatesRelationVariableMergeError
TutorialD (<unknown>/main): :jumphead master
The current transaction has uncommitted changes. If you continue, the changes will be lost. Continue? (Y/n): Y
TutorialD (master/main): b := true
TutorialD (master/main): :automergetohead union master

Does that mean for every conn that has lost its head state, I need to jumphead master first then automergetohead?
:jumphead then :automergetohead is a fast-forward commit.
When it comes to merging a detached transaction and a head, according to docs merge transactions in project-m36, Union Merge will union two relvars if names and types are the same.
But merging a := true and a := false gets the same error.
And I just found out that, in my case, union strategy might not be the right strategy.
tuple insertion will always be saved while tuple deletion will always be ignored.

To avoid TransactionIsNotAHead errors, branch the transaction graph and merge it to the head when ready to commit.

"restricted access sub-schema" might be another way to maintain consistency in multiple connections.

I'm having trouble reproducing this. Is this an empty database from scratch?
Are you using the on-disk persistence strategy or something else?

I'll add some more context to the strategy error so that we can see the underlying cause of the error.

Please try to reproduce this issue with branch 364_automerge_bug which includes more error context and Trace.Debug logging.

I think the above behavior is what is expected.
Could you try more than back and forth between Terminal 1 and 2 more than once?
Sometimes it failed at Terminal 2's first time and other times it failed at Terminal 1's second time. And I haven't found what makes the uncertainty.

Are you using the on-disk persistence strategy or something else?
This time, I did delete a database. Still the same.

tutd1:
TutorialD (master/main): a := true
TutorialD (master/main): :automergetohead union master
tutd2:
TutorialD (master/main): b := true
TutorialD (/main): :automergetohead union master
tutd1:
TutorialD (master/main): c := true
TutorialD (/main): :automergetohead union master
ERR: MergeTransactionError (StrategyViolatesRelationVariableMergeError (Just (NoSuchTransactionError 939815ec-cd65-4726-9c98-ad9a7d877c4d)))
TutorialD (/main):
and server:
(RelationVariable "true" (TransactionMarker 939815ec-cd65-4726-9c98-ad9a7d877c4d),RelationVariable "true" (TransactionMarker 939815ec-cd65-4726-9c98-ad9a7d877c4d))

Ah, ok- there may be race condition then. I'll automate something to reproduce the error.

Are you using tutd -n <db_name> or tutd -d <db_path> for the two clients?

I was tutd -n db -h <IP_ADDRESS> -p 6543 into a project-m36-server -n db -d db -h <IP_ADDRESS> -p 6543, so -d in tutd is invalid.
I might need more time to investigate this. I was bumping curryer-rpc and streamly and fixing my haskell-incremental-building snack fork at the same time during reproducing my error. Now it produces a new error NoSuchSessionError. I shouldn't bring too many variables into one reproduction.  Orz
Did you get the error after "back and forth" at least two times?

I am also seeing the NoSuchSessionError now. There is something very wrong with the over-the-wire protocol that the tests did not detect.
$ cabal run tutd -- -n db
Project:M36 TutorialD Interpreter 0.9.8
Type ":help" for more information.
A full tutorial is available at:
https://github.com/agentm/project-m36/blob/master/docs/tutd_tutorial.markdown
TutorialD (master/main): :showrelvars
┌─────────────────────────────────────────────────┬──────────┐
│attributes::relation {attribute::Text,type::Text}│name::Text│
├─────────────────────────────────────────────────┼──────────┤
│┌───────────────┬──────────┐                     │"!�"      │
││attribute::Text│type::Text│                     │          │
│└───────────────┴──────────┘                     │          │
│┌──────────┬─────────┐                           │"	"       │
││�e	::Text│*�::Text│                           │          │
│└──────────┴─────────┘                           │          │
└─────────────────────────────────────────────────┴──────────┘

Confirmed, I can produce the bug in curryer- you can peg yourself to curryer-rpc==0.3.1 if you want to run a fixed version before I resolve the bug (and figure out how it got past the tests).

Ok, I have updated the master branch to peg streamly to 0.9.0 so the corruption issues are gone, but I am still able to reproduce the issue you reported, so I'm looking at that next.

Ok, I think I see what's going on. The underlying error which is getting masked by the merge error is NoSuchTransactionError which should not happen. I'm not yet sure how this is possible...

The issue related to a piece of transaction graph trimming code that trimmed transaction related to the actual merge transactions when scanning for a common ancestor. Please try out the fix on 364_graph_merge_error_because_trimmed.

Confirmed! Each tutd automergetohead twice without an issue.
I was trying to pop the hood but I don't understand about merge much. Thank you!

It still happens if I ask tutd2 to update same name relvar.
If my last test, every update use different relvar names. And it succeeded.
This time, I use a := true back and forth between tutd1 and tutd2.
It fails at tutd2 automergetohead union master.
tutd1
TutorialD (master/main): a := true
TutorialD (master/main): :automergetohead union master

tutd2
TutorialD (master/main): a := true
TutorialD (<unknown>/main): :automergetohead union master
ERR: MergeTransactionError (StrategyViolatesRelationVariableMergeError (NoSuchTransactionError 694e3f51-068a-4ef1-80f8-5b57e6620d65))

It looks like you are using the correct branch (based on the error), but I am not able to reproduce this issue. Are the instructions above running against a completely empty database? Are you able to reproduce this error after every attempt?
If we're both running from the same branch, the error above definitely hints at another similar bug.

Just to be clear, there are now two 364_* branches. The fix for this issue is on master and 364_graph_merge_error_because_trimmed . 364_automerge_bug does not have the necessary fix.

Oops. forgot to report one condition. It happens after a merge happens, both of tutd quits, and then reconnect.
rm db -rf
project-m36-server -n db -d db
fst tutd: tutd -n db -h <IP_ADDRESS>
2nd tutd: tutd -n db -h <IP_ADDRESS>
fst tutd:
TutorialD (master/main): a:=true
TutorialD (master/main): :automergetohead union master

2nd tutd:
TutorialD (master/main): a:=true
TutorialD (<unknown>/main): :automergetohead union master

(which is fine at the moment.)
fst tutd: :quit
2nd tutd: :quit
(It seems I have to disconnect all of them first to reproduce the error.)
fst tutd: tutd -n db -h <IP_ADDRESS>
2nd tutd: tutd -n db -h <IP_ADDRESS>
fst tutd:
TutorialD (master/main): a:=true
TutorialD (master/main): :automergetohead union master

2nd tutd:
TutorialD (master/main): a:=true
TutorialD (<unknown>/main): :automergetohead union master

1fst tutd:
TutorialD (master/main): a:=true
TutorialD (<unknown>/main): :automergetohead union master
ERR: MergeTransactionError (StrategyViolatesRelationVariableMergeError (NoSuchTransactionError 200145cc-59b8-4a88-8a8e-0db0321ff4e7))

(It has to be automergetohead three times back and forth. I guess that is becuase 1st time is fast-forward. 2nd time is a real merge. And 3rd time hits the error. And the missing transaction is still root transaction this time.)
And yes, I am at * (HEAD detached at upstream/364_graph_merge_error_because_trimmed).
And yes, it's a simlar bug. T
And yes, it's reproducible to me.
It happens after both tutds quits a merged database. So not empty database.
The same part is missing root transaction. The difference is that it happens only after both tutds quit a merged database. Not one. If no merge happens at first-time connections, then the error is not reproducible.

Is it possible that the first merge creates another common ancestor so, somehow, that root transaction fails to be in the search result of referencedTransactionIds?

Ah, thanks for the additional details. I am now able to reproduce this.
I suspect the bug is in the same subGraphOfFirstCommonAncestor function, though I don't yet understand how. I'll get this fixed ASAP.

subGraphOfFirstCommonAncestor_debug_msg
I use trace-function-call and stacked-dag to get some info about subGraphOfFirstCommonAncestor. I guess you might be interested.
The reproduction steps are the same. Although I don't have the info step by step. But as you can see, at some point, subgraph indeed lost some transactions including root.  (I'll leave the question for my tomorrow...)

Ok, it turned out I missed properly recursing transactions necessary to reconstruct the subgraph, so, after multiple merges, some transactions were not included in the subgraph. Oops! It should be fixed now. Please try again.

Confirmed. The error is not reproducible anymore. Thank you!


Fix typos in keywords2vec README

Minor typos and rewording:

usefull -> useful
lets -> let's
didn't got -> didn't get
...

Thanks @slel !!!


fix: type casting

Description
This PR fixes #25
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

Thanks!


Selected drop down item is not updated when the model does

The ignore update on the scope.$watch of the drop down box is keeping the selected value from being programmatically selected. For example if you have the following list
 { label: 'First', id: 1 },
 { label: 'Second', id: 2}
]```
Initially setting the item to 2 works just fine. However, if you then set the item to 1 the drop down does not change.

In my case, the first time I select a dropdown value, the model is updated, but the dropdown still shows an empty value

Same issue happens in demo page http://clickermonkey.github.io/SemanticUI-Angular/examples/dropdown/directives.html at sm-dropdown-toggle / sm-dropdown-show / sm-dropdown-hide

Although not exhaustively tested, the following pull request might provide some insight into what is going on: https://github.com/ClickerMonkey/SemanticUI-Angular/pull/23

Closing, PR #23 was merged


Question: delay before function executes code

Is your question related to a specific version? If so, please specify:
Python Version: 3.8
Runtime Version: <IP_ADDRESS>
FUNCTIONS_WORKER_PROCESS_COUNT: 4
PYTHON_THREADPOOL_THREAD_COUNT: 1
What binding does your question apply to, if any? (e.g. Blob Trigger, Event Hub Binding, etc)
HTTP
Question
I've discovered in App Insights that sometimes there is a large time gap between a message about the function being executed and the first logging call in its handler.
For example the following log displays  a delay of more than a minute:
12/2/2022, 1:47:24.926 PM Executing 'Functions.sheet_entry_create' (Reason='This function was programmatically called via the host APIs.', Id=1eb08925-0df8-4e36-8f01-40b3fca9f0aa)
12/2/2022, 1:48:28.284 PM Starting executing function... <- coming from handler's logging.info call

I would like to understand what is causing that delay. Does it relate to a cold start?

Hi @Nuqlear - Thanks for the question, and apologies for the late reply. I've been meaning to write a doc for this as well - I'll work on that as well.

I would like to understand what is causing that delay. Does it relate to a cold start?

No - this isn't related to cold-start. It is related to how execution is sent from Host to PythonWorker. Below is the internal architecture of the Functions runtime (Host and the Python worker). In sync case, we (Python worker) receive the execution request and submit it to the ThreadPoolExecutor.

With the PYTHON_THREADPOOL_THREAD_COUNT set to 1 in your application; it'll queue up the request in the ThreadPoolExecutor as it only has one thread to work with and cannot schedule other executions. If the [PYTHON_THREADPOOL_THREAD_COUNT] is set, it changes the value of max_worker used by the ThreadPoolExecutor (doc link) - It'll use the pool of at most max_workers (set by PYTHON_THREADPOOL_THREAD_COUNT) threads to execute calls asynchronously.

Log from the host

12/2/2022, 1:47:24.926 PM Executing 'Functions.sheet_entry_create' (Reason='This function was programmatically called via the host APIs.', Id=1eb08925-0df8-4e36-8f01-40b3fca9f0aa)

This log is from the Python worker.
12/2/2022, 1:48:28.284 PM Starting executing function... <- coming from handler's logging.info call

Looking at your application usage patterns, your duration patterns range from 1 second to 90+ seconds. You would benefit significantly from using PYTHON_THREADPOOL_THREAD_COUNT to get more threads used in parallel - if you have enough CPU and Memory to allow it. I would recommend reducing the FUNCTIONS_WORKER_PROCESS_COUNT to 1 (# cores) and increasing PYTHON_THREADPOOL_THREAD_COUNT to around 2 * #cores + 1.
durationInS | count_
-- | --
1 | 91
2 | 256
3 | 155
4 | 105
5 | 65
6 | 55
7 | 54
8 | 56
9 | 44
10 | 32
11 | 19
12 | 20
13 | 9
14 | 8
15 | 4
16 | 8
17 | 8
18 | 10
19 | 1
20 | 4
21 | 4
22 | 1
23 | 6
24 | 4
25 | 4
26 | 3
27 | 2
29 | 3
30 | 2
32 | 3
33 | 2
36 | 3
39 | 1
44 | 1
47 | 1
48 | 1
62 | 3
68 | 1
69 | 2
70 | 1
73 | 1
74 | 4
76 | 1
79 | 1
93 | 1

Please re-open the issue if you need more information or are facing some other issue.

Thank you @vrdmr for such a detailed response.
I will look into the way to make adjustments to match your recommendations.


Kapacitor mail alert data format JSON to plain text

I configured TICK stack and it's working fine. Now I need to send mail alerts using kapacitor. kapacitor connected with chronograf and influxdb . kapacitor sending mail alerts in JSON format. I need alert data in plain text format. How can I change data format?

@partheshzeotap Are the Kapacitor tasks you are using created with Chronograf?
Kapacitor has the ability to send emails with plain text content via the details property of the alert node.
Chronograf does not expose that property yet.

@partheshzeotap I've added chronograf PR https://github.com/influxdata/chronograf/pull/835 to handle this issue.  Once it is merged you'll need to open your kapacitor alert rules and "resave" them so that they will now have the .details() field filled out.

I used TICK stack with docker and docker-compose. Using chronograf web-ui I m try to send alerts. @nathanielc

@goller @nathanielc
I blocked on this issue.
I clone "/feature/kapacitor-detail" branch but I am able to start docker container.
Error: exec /usr/bin/chronograf : permission denide
Please give me some solutions.

Please take the conversation to chronograf, thanks!


pods: 2.0.1-unstable-2024-08-11 -> 2.1.2

Description of changes
Updated to the newest release. Was unstable due to https://github.com/NixOS/nixpkgs/issues/332957.
changelog

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/1016/184

Is this still relevant?

Is this still relevant?

Yes, 2.1.2 is also still the current release.

nixpkgs-reviewd workflow started

Extra args: ``
Free space: true
Who asked: lucasew

TARGETS

x86_64-linux: true
x86_64-darwin: false
aarch64-darwin: false

Status and logs: https://github.com/nixosbrasil/nixpkgs-reviewd/actions/runs/12458349848

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 343501

x86_64-linux

:white_check_mark: 1 package built:

pods


Remove some code smells

@njam shouldn't we use javascript:void(0) instead of javascript:;?  http://stackoverflow.com/questions/134845/href-attribute-for-javascript-links-or-javascriptvoid0
@christopheschwyzer

/CM/layout/default/css/form.less line 278: shouldn't @sizeSwitch be assigned with : instead of =?
we never introduce LESS variable @breakpointSmall is this on purpose?

shouldn't we use javascript:void(0) instead of javascript:; in html-tag-a-href?  http://stackoverflow.com/questions/134845/href-attribute-for-javascript-links-or-javascriptvoid0

On that stackoverflow page somebody says javascript:; might not work in old IE version. And some people propose to prefer javascript:; over javascript:void(0).
I don't think we need to worry about those old IE versions. Is there another reason why you want to change it

@njam no real other reason. Just the IDE dont like javascript:;

True it doesn't like the "unnecessary ;". Not sure whether it would work without.
I would suggest to keep it as is to avoid problems in some browsers?

agree.

in layout/default/FormField/File/default.less is the font-familly even necessary? Can be default font AFAIK.

form.less: @sizeSwitch =  @sizeCheckbox + 4px; assignment with ":" instead "="

@njam please review.

@alexispeter could you review this?

CM_Model_StorageAdapter_Cache::_generateId() is this method needed?I can't find it anywhere in the class hierarchy, maybe legacy code? Could you investigate and remove it completely if appropriate?

rest looks good
I assume you had css checked

talked about it quickly with @njam, you can remove _generateId() and throw the exception in create()

less / css is fine

@alexispeter please review.

lgtm


Compiling error ChatFilter.cpp line 166 No member named

While compiling i ran into some errors.  I modified things as suggested by the compiler and got down to just this one. "mod-playerbots-AzerothCore/src/ChatFilter.cpp:166:47: error: ‘class Group’ has no member named ‘GetTargetIcon’; did you mean ‘SetTargetIcon’?" If i change it everything brakes and i get more errors.  Though set as it is i cant compile completely.

Please kindly note that this requires some custom changes to AzerothCore, so it is necessary to compile with a custom branch from my fork: https://github.com/ZhengPeiRu21/azerothcore-wotlk/tree/Playerbot
git clone https://github.com/ZhengPeiRu21/azerothcore-wotlk.git --branch Playerbot --single-branch

So i wanted to make sure i didn't mess something up.  I used the same mod files as my first attempt and a fresh clone from above.  Still getting lots of warnings and errors on build.  Tried a fresh mod files and clone. Still get build errors. Modified the guildbank cpp with the suggested changes and i got rid of those errors but made new ones. Not sure if its because of my other mods or what.

Used the same mod files from the first attempt except for i used clone (https://github.com/Embracefate989/mod-playerbots.git) --branch patch-1 as said in a later issue post and a fresh clone of the your core tree.  An i built just fine.

Playing around it was one of the modules i was compiling with.  I went back with this mod and core tree. An on my "blizz like" build with almost no other modules it complies fine. I don't know which modules, the one i was failing to build has tons of modules added.

@PupAce please close out this issue


delete_proj_spec_conf

Removing project specific configs

HI @ubyndr - looks like schema test GA not running automatically on PRs.  Please can you fix this. - Thanks

Also wondering if possible to test build on PR (or does this require more resources than we can get for free with GitHub actions?) -  looks very brittle:

I suspect the empty objects in the edited YAML are causing the problem - which I think is legal according to the current schema.  We need to think through what a good default config would be and how we should document it.

Also wondering if possible to test build on PR (or does this require more resources than we can get for free with GitHub actions?) - looks very brittle:

I can test this, and let you know.

I suspect the empty objects in the edited YAML are causing the problem - which I think is legal according to the current schema. We need to think through what a good default config would be and how we should document it.

I don't think this is valid;
neo_node_labelling: {}

🤯

HI @ubyndr - looks like schema test GA not running automatically on PRs. Please can you fix this. - Thanks

Done

I don't think this is valid;
neo_node_labelling: {}

Can we get the test running here so that we can see?
I may be wrong, but I think it is valid because there are no required keys specified in the object definition.
OTOH - I think the build fails because the code expects an object there.  We should align these two - probably by making the schema stricter.
If we do need an object of the right shape here for the build to work, then we need to discuss what constitutes a reasonable default config + make sure doc makes clear what needs to be deleted/edited before users build their own custom projects.  The current default is way too complex - hence this PR.

Can we get the test running here so that we can see?

Action is enabled again, and failing at the moment fyi

Check is now displaying (wasn't before - maybe some lag in GitHub?) However, I would like to see the reason for the fail in GA, but all I currently see is

@dosumis This branch should be working on your local, make sure you delete previous obask images.


ldap2pg should not revoke ldap_roles from a role that is to be dropped

In the case where ldap2pg needs to drop an LDAP role, the role is first removed from the ldap_roles role before it is actually dropped: https://github.com/dalibo/ldap2pg/blob/4082b163a0c282395eda149b34183c29913b13a2/ldap2pg/role.py#L129
Now, if anything goes wrong after this REVOKE command (e.g. if the REASSIGN OWNED BY ... or the DROP OWNED BY ... command fails for some reason), the user is left in the cluster and will remain there forever, because it isn't a member of the ldap_roles role anymore.

ldap2pg.yml

ldap2pg.yml
postgres:
  managed_roles_query: |
    SELECT DISTINCT role.rolname
    FROM pg_roles AS role
    LEFT OUTER JOIN pg_auth_members AS ms ON ms.member = role.oid
    LEFT OUTER JOIN pg_roles AS ldap_roles
      ON ldap_roles.rolname = 'ldap_roles' AND ldap_roles.oid = ms.roleid
    WHERE role.rolname = 'ldap_roles'
        OR ldap_roles.oid IS NOT NULL
    ORDER BY 1;
  ...

Expectations

ldap2pg should not revoke ldap_roles from a role that is to be dropped.

Hi @schmandr , thanks for this excellent feedback ! I'll take a look at this.


MSA creation protocol

Hi Pascal,
I was wondering what protocol was used to create MSAs. Is it identical to the one used in EVE?
Best regards,
Floris

Hi Floris,
Thanks for asking the question -- just realizing we did not include these details in the latest version of the paper!
We followed a process similar to the one described in the Tranception paper (see Appendix C). In summary: we ran Jackhmmer on UniRef100, exploring various bit scores (from 0.1 to 0.9) and selected the alignment with the highest number of significant Evolutionary Couplings (using the EV couplings pipeline).
For each assay, we aimed to generate an alignment for the full protein sequence. This helped ensure for instance that alignment-based methods would be able to score all assayed mutants. In a handful of cases this was impractical (e.g., very long sequences), and we instead created alignments for the mutated region (with a 10AA-long padding on both sides of the mutated region).
Best,
Pascal

Hi Pascal,
Thanks for clarifying!
Best,
Floris


add base testcases

For a selected managed cluster must be able to enable managed-serviceaccount addon

Validate the deployment of addon
For a selected managed cluster must be able to create managed-serviceaccount
Validate the creation of serviceaccount (on managedcluster)
Validate the creation of serviceaccount token secret on hub
Validate the validity of the serviceaccount token by comparing to the serviceaccount token on managedcluster

TODO:
Must be able to enable the managed-serviceaccount feature

validate the enablement
pending MCE/ACM inclusion of managed-serviceaccount feature

https://github.com/stolostron/backlog/issues/19256

/hold

this PR is on hold till managed-serviceaccount is integrated into ACM and MCE

/unhold


Adding yaml for a simple two-step workflow to clone the repo and then…

… create a PR to catch prod up with main.
Description
Adds a github actions workflow to create a PR when branches are merged with main.
Issues Resolved
#13
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@dblock - it does - as soon as the branch involved in the original PR (main) is updated, it becomes part of the PR and prevents another one from being made.


Debug.Log stuff

there's a bunch of things in the current update that kinda just spam debug.log on update, please fix next update, also sharing the photon code in debug.log also is kinda a security problem

I saw your reply to an old pull request that ansers this

I don't spam anything on update

Line 90 photonvr player, it's not update but still a bit annoying

Oh that, yeah that was meant to be removed on release


Unsupervised graph embedding demo

Hi!
I am trying to implement an unsupervised graph embedding based on the demo provided in the documentation.
I have noticed that the embedding model (embedding_model) is never compiled nor trained.
On the other hand, the model learning the graph distances (pair_model) is trained but it is never used for the embedding.
Is this missing in the demo?
Thank you very much!

Hi, there's a subtle trick here: the layers used for embedding_model are shared with pair_model, all the way down to the (trainable) weight matrices. In particular, training via pair_model is optimising the same layers used in embedding_model. One way to look at this is there's two phases, both of which use different views of the same core GCNSupervisedGraphClassification model:

training with the pair_model view, using pairs of graphs
prediction/embedding with embedding_model, using single graphs

This is controlled by the cell that contains:
pair_model = keras.Model(inp1 + inp2, vec_distance)
embedding_model = keras.Model(inp1, out1)

The inp1 and inp2 values are both feeding data through the basic model, just allowing us to do two matrices at the same time.
So, all in all, I agree that there's something missing in the demo, in the form of a clearer explanation of this process. Does the one above clarify it for you? (If it doesn't please do let me know, because it'll be great to have a good description before we put it into the documentation itself.)
Thanks for filing an issue!

Hi, there's a subtle trick here: the layers used for embedding_model are shared with pair_model, all the way down to the (trainable) weight matrices. In particular, training via pair_model is optimising the same layers used in embedding_model. One way to look at this is there's two phases, both of which use different views of the same core GCNSupervisedGraphClassification model:

training with the pair_model view, using pairs of graphs
prediction/embedding with embedding_model, using single graphs

This is controlled by the cell that contains:
pair_model = keras.Model(inp1 + inp2, vec_distance)
embedding_model = keras.Model(inp1, out1)

The inp1 and inp2 values are both feeding data through the basic model, just allowing us to do two matrices at the same time.
So, all in all, I agree that there's something missing in the demo, in the form of a clearer explanation of this process. Does the one above clarify it for you? (If it doesn't please do let me know, because it'll be great to have a good description before we put it into the documentation itself.)
Thanks for filing an issue!

Thank you very much for this great explanation and for your great work!
Yes, it is definitely clearer now.

Thank you very much for this great explanation and for your great work!
Yes, it is definitely clearer now.


Source?

Would you mind sharing the source code you are using to obtain the csv files?

Would be interested in this too!


I'd like to join this project's community

Your public repo
https://github.com/jamesholidaycc/gov4git-identity-public.git
Your public branch
main

approved


Permissionslist for shares missing definition

Description
The return of a single shares not possible due to missing definition for Permissionslist.
Reproduction
w.shares.share_permissions(name=<share_name>)

response:
   1324     request = SharePermissionsRequest(name=name)
   1326 json = self._api.do('GET', f'/api/2.1/unity-catalog/shares/{request.name}/permissions')
-> 1327 return PermissionsList.from_dict(json)

NameError: name 'PermissionsList' is not defined

Expected behavior
An permissionslist object
Other Information
missing class affil in method in databricks/sdk/service/SharesAPI - share_permissions:
    def share_permissions(self, name: str, **kwargs) -> catalog.PermissionsList:
        """Get permissions.

        Gets the permissions for a data share from the metastore. The caller must be a metastore admin or the
        owner of the share.

        :param name: str
          The name of the share.

        :returns: :class:`PermissionsList`
        """
        request = kwargs.get('request', None)
        if not request: # request is not given through keyed args
            request = SharePermissionsRequest(name=name)

        json = self._api.do('GET', f'/api/2.1/unity-catalog/shares/{request.name}/permissions')
        return >> PermissionsList.from_dict(json)

Hi @Oscarhewittlindberg, I have fixed this issue. Below is the PR for this. Please check and merge if you see fit.
https://github.com/databricks/databricks-sdk-py/pull/228
PS- This is my first open source contribution. Kindly let me know if the fix is appropriate or not.

Following up - is this issue still relevant?

@nfx hello! Reaching out since this NameError is still reproducible in databricks-sdk==0.25.1. Would it be possible to re-open the issue as long as the NameError persists just for visibility's sake? Or was it closed since this code is auto-generated and can't be fixed by a contribution? (see #228)


UseHttpLogging call before or after UseStaticFiles

Fixes  #28467
@JamesNK  possible review.
Public review  of the doc build:

download the HTML files
unzip
view HTML file in a browser.
For links outside the doc, remove the review. from URL.

Internal previews

📄 File
🔗 Preview link

aspnetcore/fundamentals/http-logging/index.md
aspnetcore/fundamentals/http-logging/index

@Kahbazi please review

@xsoheilalizadeh  thanks for the review and suggestion. I hate bling/chrome/call-outs but we'll see how this goes.


[Feature Request]提供自定义UI

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Not possible #13


keep merged columns as PooledArrays when possible

The default merge behavior of PooledArray is to always convert the result to a non pooled type.
This overrides that behavior when the non pooled column is of reasonable length.

Nice :+1:


Set up ShoppIt JavaFX application files

You should add /.classpath/ and /.project/ to gitignore before commiting. As such I have closed your pull request.


An expected pull request is mentioned in dry run logs even if there is no change

An expected pull request is mentioned in dry run logs even if there is no change
Fix #484
In the current state, this PR fix two bugs which by the way could be split into two Pull requests :)

In Dry mode, don't mention that a PR will be open if it's not the case (#484 )
Pull request object correctly using the updated configuration. This avoids open pull requests with a message containing templating instruction such as Bump app to {{ source "source" }}

Test
To test this pull request, you can run the following commands:

Run updatecli in dry mode and debug enable, with a updatecli configuration that shouldn't open a pullrequest. We shouldn't have pull request message
Run updatecli in dry mode and debug enable, with a updatecli configuration that should open a pull request and where the title contains templating instruction. We should have pull request message with the correct title

Additional Information
Tradeoff

Potential improvement
While working on this PR, I realize that we have confusion about what a pull request title should be. The title should be configured in the spec level and not at the pull request level.
pullrequestID:
  kind: github
  title: my title
  spec:
     label:
        - dependencies

or
pullrequestID:
  kind: github
  spec:
    title: my title
    label:
        - dependencies

At the moment the latter example, is implement in the code in a way that it's totally useless.
I also realize that the way to generate a pullrequest title is overly complicated and could drastically simplified by just having the two following cases
1 A title is specified in the spec, then we use that value
2. No title specified so we let GitHub should, which will be the first commit title

At the moment the latter example, is implement in the code in a way that it's totally useless.
I also realize that the way to generate a pullrequest title is overly complicated and could drastically simplified by just having the two following cases
1 A title is specified in the spec, then we use that value

No title specified so we let GitHub should, which will be the first commit title

@olblak do you mind opening an issue describing this thought process and pointing some code elements? That would allow us to discuss the subject, reach a consensus and then implement it in async :)

@olblak do you mind opening an issue describing this thought process and pointing some code elements? That would allow us to discuss the subject, reach a consensus and then implement it in async :)

Yep, yep, which is why I mentioned it in "Potential Improvement" section


Adapt to pre-commit.yaml file

Add pre-commit.yaml file for the code style check.

Thanks for working on this @Revathyvenugopal162.
The build is failing due to a circular error:

This happened to me before in the other PR I had open. I think it's related to the ordering of the imports in __init__.py. Is this possible?
If that is the case, we need to find the way to have the imports sorted alphabetically without breaking everything.

Thanks for working on this @Revathyvenugopal162.
The build is failing due to a circular import error:
This happened to me before in the other PR I had open. I think it's related to the ordering of the imports in __init__.py. Is this possible?
If that is the case, we need to find the way to have the imports sorted alphabetically without breaking everything.

Yeah, we have isort, we should add that for the sorting of import. let me see.


XML throws parsing exception after it removes all whitespace between attributes if CRLF (\r\n) appears

For XML text like this (i.e. e4x raw data during an HTTPService):
<mynode red="value1"\r\n green="value2" blue="value3" \r\nyellow="value4" />
The XML object will remove "\r\n " or " \r\n", causing the attributes to be squished together, throwing a parsing error.
The problem is trimXMLWhitespace():
		static private function trimXMLWhitespace(value:String):String 		{ 			return value.replace(/^\s+|\s+$/gm,''); 		}
The "^" and "$" are matching up with the literal newlines (\r\n).  Perhaps the original intent was to match just the beginning / end of the entire string.
A quick workaround is to either return just "value" or replace with a single space instead of blank:
		static private function trimXMLWhitespace(value:String):String 		{ 			return value.replace(/^\s+|\s+$/gm,' '); 		}
I would imagine that CRLF embedded in actual text values are also getting stripped out unintentionally, but haven't tested that.
Test case:
TestXML.mxml.txt
Test exception:
Uncaught Error: XML Parsing Error: not well-formed
Location: file:///C:/src/royale-test-xml/bin/js-debug/index.html
Line Number 1, Column 39:<parseRoot><myxml><mynode red="value1"green="value2" blue="value3"yellow="value4" /></myxml></parseRoot>
--------------------------------------^

@greg-dove It looks like you added the trim on creation of the XML about a year ago. Do you remember why?

I'll try and look at this quickly tomorrow too @Harbs. I hope there is a unit test that will fail if I remove it and that will tell me why. I'll add some new tests for the described examples above and figure it out.

There's two places it's used during parsing. One on line 571:
var xmlStr:String = ignoreWhitespace ? trimXMLWhitespace("" + xml) : "" + xml;
and a second time on line 637:
if (ignoreWhitespace) xml = trimXMLWhitespace( xml) ;
I cannot see a case where the first one is needed at all. I think the second time is always called.
I commented out both cases and XML tests pass with no errors.
We probably do need to strip out whitespace when parsing XML if ignoreWhitespace is true, but the way we're doing it is very simplistic and I'm not sure it's going to work. I'm not sure what the best way is though. Walking the tree and stripping out the whitespace after it's parsed is an expensive way of doing it and I don't see a way of stripping whitespace while parsing using DOMParser. We definitely do need unit tests for these cases either way...

FYI, here's the discussion which triggered the change:
https://lists.apache.org/list.html?dev@royale.apache.org:2019-6:Implicit casts and skipAsCercions
Unfortunately the paste is no longer valid.

My impression was that the places where trimXMLWhitespace() is used is solely for trimming leading and trailing space for the entire string (whether that's right or wrong), not embedded whitespace within the string (which seem to be handled already during parsing).  But I haven't traced through in detail.
So something like StringUtil.trim(), as opposed to replace() matching newlines.   However, StringUtil.trim() is probably too slow.  Perhaps changing "/gm" to "/g" is enough (turn off multi-line in the regexp);  docs seem to indicate that in an example.  Or not trimming at all.

IIRC, the reason we're trimming is to prevent empty text nodes. It's clearly doing the wrong thing in this case, so we need to figure out the correct way to do that.

@greg-dove It looks like we're dropping empty nodes (and trimming) here:
https://github.com/apache/royale-asjs/blob/develop/frameworks/projects/XML/src/main/royale/XML.as#L407
Perhaps we can really remove both cases of trimXMLWhitespace during parsing.
Do you agree?

Related: I'm not sure that trim() is doing the right thing. trim() treats no-break spaces as a space character, while the ECMA spec seems to only consider regular spaces. I also don't see where the ECMA spec says to remove leading and trailing space from text nodes (although I'm pretty sure that's correct)...

That should be working after the next build.
Sorry I only looked back at your last comment here after I committed the change Harbs. I did not try with non-breaking spaces etc. We probably need some additional tests to include things like that.
I removed that trimming support and went with String.trim for now because it is needed in some places. I added some extra tests, here:
https://github.com/apache/royale-asjs/blob/e0dcd7b199ac559709f9a35b301e49c75aaaa6d3/frameworks/projects/XML/src/test/royale/flexUnitTests/xml/XMLTesterGeneralTest.as#L161

The original issue is resolved.  The trim() fix is a slight bottleneck, but we're talking about 200ms on 15 MB of XML with many tabs to pretty-print and newlines after almost every node (see my mention of that in PR #1025), after preprocessing the data to remove "\r" characters.


Action does not work out of the box without a package.json file

Example output:
Run cypress-io/github-action@v1
  with:
    wait-on: http://localhost:5050
    spec: tests/initual-setup.js
    record: false
    config-file: cypress.json
    env: false
internal/fs/utils.js:220
    throw err;
    ^

Error: ENOENT: no such file or directory, open '/home/runner/work/polaris-web/polaris-web/package-lock.json'
    at Object.openSync (fs.js:440:3)
    at Object.readFileSync (fs.js:342:35)
    at Function.module.exports.309.hasha.fromFileSync (/home/runner/work/_actions/cypress-io/github-action/v1/dist/index.js:4486:54)
    at lockHash (/home/runner/work/_actions/cypress-io/github-action/v1/dist/index.js:2467:16)
    at getNpmCache (/home/runner/work/_actions/cypress-io/github-action/v1/dist/index.js:2475:16)
    at restoreCachedNpm (/home/runner/work/_actions/cypress-io/github-action/v1/dist/index.js:2518:21)
    at installMaybe (/home/runner/work/_actions/cypress-io/github-action/v1/dist/index.js:2816:5)
    at Object.104 (/home/runner/work/_actions/cypress-io/github-action/v1/dist/index.js:2837:1)
    at __webpack_require__ (/home/runner/work/_actions/cypress-io/github-action/v1/dist/index.js:22:30)
    at startup (/home/runner/work/_actions/cypress-io/github-action/v1/dist/index.js:37:19) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/home/runner/work/polaris-web/polaris-web/package-lock.json'
}

From https://github.com/agersant/polaris-web/commit/dcaf31ed3339aa6b49afb54e96e0ee790304744b/checks?check_suite_id=396158425

Note that I was able to work around this by adding the following step before the cypress action:
- name: Setup npm package
  run: npm init -y && npm install

Getting this error. I do have a package.json file in the working directory.
If I push the package-lock.json file - It works. Any help would be great.

Same problem as @sabin-bhattarai-cko. Config file is the same as the basic setup on ReadMe.md too.


Fix TestFragmentScanOptions test result does not match

Describe the bug, including details regarding any error messages, version, and platform.
Some typo causes dataset tests not run in CI, so this test failed but pass CI
Component(s)
Java

@jinchengchenghh let's add the failure and stacktrace in the description section.

Also, please add  [Java] Fix TestFragmentScanOptions test result does not match

Fixed in https://github.com/apache/arrow/pull/43503

@jinchengchenghh in my latest PR (rebased), I am getting this, https://github.com/apache/arrow/actions/runs/10344923592/job/28631183503?pr=43637#step:7:59380

I pushed my fix to this branch as you say https://github.com/apache/arrow/pull/43503, but it is missed in the merged commits...
I will pull a new request to solve

Do you have a backup for my fix? I cannot find it now, sad. @vibhatha

Oh, wait, I cannot see that diff in the merged PR, what happened to that?

Lucky thing, I find it in another folder. I have create a PR.

Issue resolved by pull request 43639
https://github.com/apache/arrow/pull/43639


Verify the Yale BSC doesn't repeat HD values across multiple entries.

I'm using the HD identifier to cross-match my data-set and the Yale Bright Star Catalog.
If the HD is not unique in the Yale BSC, then it would be less suitable as a cross-matching tool.

I added some analysis code for this catalog, that looks for duplicate HDs. None are found.


DO NOT MERGE! LTS preview

Linter check found the following problems:
Traceback (most recent call last):
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/_renderer.py", line 219, in render
    yaml_text = _get_template(meta_yaml, selector_dict).render(render_dict)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/_renderer.py", line 155, in _get_template
    return _jinja_silent_undef.from_string(meta_yaml_selectors_applied)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/jinja2/environment.py", line 1105, in from_string
    return cls.from_code(self, self.compile(source), gs, None)
                               ^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/jinja2/environment.py", line 768, in compile
    self.handle_exception(source=source_hint)
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/jinja2/environment.py", line 936, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "", line 482, in template
jinja2.exceptions.TemplateSyntaxError: Unexpected end of template. Jinja was looking for the following tags: 'elif' or 'else' or 'endif'. The innermost block that needs to be closed is 'if'.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/lint/init.py", line 722, in lint_file
recipe = _recipe.Recipe.from_file(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/recipe.py", line 231, in from_file
raise exc
File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/recipe.py", line 222, in from_file
recipe._load_from_string(text.read())
File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/recipe.py", line 154, in _load_from_string
self.render()
File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/recipe.py", line 271, in render
self.meta = renderer.render(
^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/_renderer.py", line 221, in render
raise JinjaRenderFailure(recipe_dir, message=exc.message, line=exc.lineno)
percy.render.exceptions.JinjaRenderFailure: (PosixPath('/tmp/abs_28o_u4dmqx/clone/recipe'), "Unexpected end of template. Jinja was looking for the following tags: 'elif' or 'else' or 'endif'. The innermost block that needs to be closed is 'if'. (at line 482)")
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/conda/envs/linter/bin/conda-lint", line 11, in
sys.exit(main())
^^^^^^
File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/run.py", line 114, in main
result = linter.lint(
^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/lint/init.py", line 626, in lint
msgs = self.lint_file(
^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/lint/init.py", line 739, in lint_file
recipe = _recipe.Recipe(recipe_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/recipe.py", line 93, in init
self.recipe_dir = recipe_file.parent
^^^^^^^^^^^^^^^^^^
AttributeError: 'str' object has no attribute 'parent'
ERROR conda.cli.main_run:execute(49): conda run conda-lint /tmp/abs_28o_u4dmqx/clone failed. (See above for error)

Linter check found the following problems:
Traceback (most recent call last):
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/_renderer.py", line 232, in render
    return ruamel.load(yaml_text.replace("\t", " ").replace("%", " "))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/main.py", line 434, in load
    return constructor.get_single_data()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/constructor.py", line 119, in get_single_data
    node = self.composer.get_single_node()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 76, in get_single_node
    document = self.compose_document()
               ^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 99, in compose_document
    node = self.compose_node(None, None)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 143, in compose_node
    node = self.compose_mapping_node(anchor)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 223, in compose_mapping_node
    item_value = self.compose_node(node, item_key)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 141, in compose_node
    node = self.compose_sequence_node(anchor)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 184, in compose_sequence_node
    while not self.parser.check_event(SequenceEndEvent):
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/parser.py", line 146, in check_event
    self.current_event = self.state()
                         ^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/parser.py", line 541, in parse_block_sequence_entry
    raise ParserError(
ruamel.yaml.parser.ParserError: while parsing a block collection
  in "", line 10, column 3:
      - url: https://gstreamer.freedes ...
      ^ (line: 10)
expected , but found '?'
  in "", line 15, column 3:
      patches:
      ^ (line: 15)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/lint/init.py", line 722, in lint_file
recipe = _recipe.Recipe.from_file(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/recipe.py", line 231, in from_file
raise exc
File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/recipe.py", line 222, in from_file
recipe._load_from_string(text.read())
File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/recipe.py", line 154, in _load_from_string
self.render()
File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/recipe.py", line 271, in render
self.meta = renderer.render(
^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/_renderer.py", line 255, in render
raise YAMLRenderFailure(recipe_dir, line=exc.problem_mark.line)
percy.render.exceptions.YAMLRenderFailure: /tmp/abs_1676_i5n52/clone/recipe
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/conda/envs/linter/bin/conda-lint", line 11, in
sys.exit(main())
^^^^^^
File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/run.py", line 114, in main
result = linter.lint(
^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/lint/init.py", line 626, in lint
msgs = self.lint_file(
^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/lint/init.py", line 739, in lint_file
recipe = _recipe.Recipe(recipe_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.11/site-packages/percy/render/recipe.py", line 93, in init
self.recipe_dir = recipe_file.parent
^^^^^^^^^^^^^^^^^^
AttributeError: 'str' object has no attribute 'parent'
ERROR conda.cli.main_run:execute(49): conda run conda-lint /tmp/abs_1676_i5n52/clone failed. (See above for error)

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:53: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:54: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:55: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:106: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:107: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:107: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:139: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:140: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: LGPLLR
ERROR: clone/recipe/meta.yaml:142: missing_summary: The recipe is missing a summary
ERROR: clone/recipe/meta.yaml:142: http_url: http://gstreamer.freedesktop.org/ is not https
ERROR: clone/recipe/meta.yaml:142: missing_license_family: The recipe is missing the about/license_family key.
WARNING: clone/recipe/meta.yaml:142: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
WARNING: clone/recipe/meta.yaml:142: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:172: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: LGPLLR
ERROR: clone/recipe/meta.yaml:174: missing_license_family: The recipe is missing the about/license_family key.
WARNING: clone/recipe/meta.yaml:174: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
ERROR: clone/recipe/meta.yaml:174: http_url: http://gstreamer.freedesktop.org/ is not https
WARNING: clone/recipe/meta.yaml:174: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:174: missing_summary: The recipe is missing a summary
ERROR: clone/recipe/meta.yaml:232: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: LGPLLR
ERROR: clone/recipe/meta.yaml:234: missing_license_family: The recipe is missing the about/license_family key.
ERROR: clone/recipe/meta.yaml:234: http_url: http://gstreamer.freedesktop.org/ is not https
WARNING: clone/recipe/meta.yaml:234: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
WARNING: clone/recipe/meta.yaml:234: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:234: missing_summary: The recipe is missing a summary
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:53: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:54: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:55: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:106: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:107: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:107: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:139: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:140: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: LGPLLR
ERROR: clone/recipe/meta.yaml:142: missing_summary: The recipe is missing a summary
WARNING: clone/recipe/meta.yaml:142: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:142: missing_license_family: The recipe is missing the about/license_family key.
ERROR: clone/recipe/meta.yaml:142: http_url: http://gstreamer.freedesktop.org/ is not https
WARNING: clone/recipe/meta.yaml:142: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
ERROR: clone/recipe/meta.yaml:172: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: LGPLLR
WARNING: clone/recipe/meta.yaml:174: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:174: missing_license_family: The recipe is missing the about/license_family key.
ERROR: clone/recipe/meta.yaml:174: http_url: http://gstreamer.freedesktop.org/ is not https
ERROR: clone/recipe/meta.yaml:174: missing_summary: The recipe is missing a summary
WARNING: clone/recipe/meta.yaml:174: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
ERROR: clone/recipe/meta.yaml:232: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: LGPLLR
WARNING: clone/recipe/meta.yaml:234: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
ERROR: clone/recipe/meta.yaml:234: missing_license_family: The recipe is missing the about/license_family key.
WARNING: clone/recipe/meta.yaml:234: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:234: http_url: http://gstreamer.freedesktop.org/ is not https
ERROR: clone/recipe/meta.yaml:234: missing_summary: The recipe is missing a summary
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:53: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:105: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:106: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:137: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:139: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: LGPLLR
WARNING: clone/recipe/meta.yaml:141: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
ERROR: clone/recipe/meta.yaml:141: http_url: http://gstreamer.freedesktop.org/ is not https
ERROR: clone/recipe/meta.yaml:141: missing_license_family: The recipe is missing the about/license_family key.
WARNING: clone/recipe/meta.yaml:141: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:141: missing_summary: The recipe is missing a summary
ERROR: clone/recipe/meta.yaml:171: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: LGPLLR
WARNING: clone/recipe/meta.yaml:173: missing_description: The recipe is missing a description
WARNING: clone/recipe/meta.yaml:173: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
ERROR: clone/recipe/meta.yaml:173: http_url: http://gstreamer.freedesktop.org/ is not https
ERROR: clone/recipe/meta.yaml:173: missing_summary: The recipe is missing a summary
ERROR: clone/recipe/meta.yaml:173: missing_license_family: The recipe is missing the about/license_family key.
ERROR: clone/recipe/meta.yaml:231: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: LGPLLR
WARNING: clone/recipe/meta.yaml:233: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:233: http_url: http://gstreamer.freedesktop.org/ is not https
ERROR: clone/recipe/meta.yaml:233: missing_license_family: The recipe is missing the about/license_family key.
WARNING: clone/recipe/meta.yaml:233: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
ERROR: clone/recipe/meta.yaml:233: missing_summary: The recipe is missing a summary
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:53: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:54: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:106: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:107: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:139: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:140: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: LGPLLR
ERROR: clone/recipe/meta.yaml:142: missing_license_family: The recipe is missing the about/license_family key.
ERROR: clone/recipe/meta.yaml:142: http_url: http://gstreamer.freedesktop.org/ is not https
WARNING: clone/recipe/meta.yaml:142: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
ERROR: clone/recipe/meta.yaml:142: missing_summary: The recipe is missing a summary
WARNING: clone/recipe/meta.yaml:142: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:172: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: LGPLLR
ERROR: clone/recipe/meta.yaml:174: missing_summary: The recipe is missing a summary
ERROR: clone/recipe/meta.yaml:174: http_url: http://gstreamer.freedesktop.org/ is not https
WARNING: clone/recipe/meta.yaml:174: missing_description: The recipe is missing a description
WARNING: clone/recipe/meta.yaml:174: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
ERROR: clone/recipe/meta.yaml:174: missing_license_family: The recipe is missing the about/license_family key.
ERROR: clone/recipe/meta.yaml:232: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: LGPLLR
ERROR: clone/recipe/meta.yaml:234: http_url: http://gstreamer.freedesktop.org/ is not https
WARNING: clone/recipe/meta.yaml:234: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
ERROR: clone/recipe/meta.yaml:234: missing_summary: The recipe is missing a summary
WARNING: clone/recipe/meta.yaml:234: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:234: missing_license_family: The recipe is missing the about/license_family key.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:53: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:54: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:106: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:107: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:139: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:53: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:54: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:106: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:107: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:139: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:53: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:54: host_section_needs_exact_pinnings: output "gstreamer": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:106: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:107: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:139: host_section_needs_exact_pinnings: output "gst-plugins-base": Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
Errors were found


Fix reinstall brick

Don't run this unless you can recover from a brick.
Situation: user installs enso, then reinstalls 3.60 (which uninstalls enso but not the backup MBR), then runs enso app and selects uninstall. Result: brick.
This fixes it by always overwriting block 0 with a copy of block 0 which when enso is installed would redirect the reads to block 1 but not writes, and when enso is not installed would not do anything.
Tests:

[x] Without the patch: Install enso, reboot, uninstall enso
[x] Without the patch: Install enso, flash 3.60, make nand backup !!, uninstall enso; confirm this bricks
[x] With the patch: Install enso, flash 3.60, make nand backup !!, uninstall enso; confirm this does not brick anymore
[x] With the patch: Install enso, reboot, uninstall enso
[x] With the patch: Install enso, reboot, uninstall enso, reboot, uninstall enso
Run all tests from the old google forms

make a nand backup every time you reflash 3.60!

Confirmed that original enso bricks with indicated steps. Confirmed patch fixes the problem. Because the mbr.bin payload is exactly the same, I did not feel the need to run the old tests.


pull request for e2e test at 11/14/2016 08:15:10

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

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.


Automatic Fan control

how to write a code for Automatic Fan control as FSM

I suggest you study finite state machines and attempt to build something. If you get stuck, services such as stackoverflow are a great place to help improve your knowledge of finite state machines and how to apply them to real-world problems.


app.stub directory issue

error when running :
php artisan infyom.publish:layout
 [ErrorException]                                                                                copy(C:\xampp\htdocs\sherkat\vendor/infyomlabs/core-templates/templates/scaffold/layouts/app.stub): failed to open stream: No such file or directory
there is no core-template directory

found out that "infyomlabs/core-templates": "5.3.x-dev" should be added to composer.json

@amin101 core-templates are no longer maintained. You should try to use adminlte-templates.

so maybe you should fix php artisan infyom.publish:layout running code as it requires core-templates .

Change config. Replace 'teplates' parameter from 'core-templates' to 'adminlte-templates' in laravel_generator.php config. Default parameter have a deprecated value.
Since the core-templates is no longer maintained, I wonder why it is still the default of the infyomlabs config.  The default should be adminlte-templates.  Or fix the install.


Misc key derivation changes

From last week's email chain, we ought:

Remove the optional 'password' salt throughout
Remove the 'revision' salt throughout
Not use the ship number to salt in childSeedFromSeed
Fix all seeds at 256 bits
Use an explicit out: 32 bytes argument to argon2
Use an explicit derivation path of m/44'/60'/0'/0/0

See the updated wallet spec for details.

idk if you're actively working on this rn, but I just pushed these changes.  Hope this is still useful!

No sweat.  I don't mind duplicating work in the slightest -- work first, ask questions later. 😄

(Just push em out and I'll merge/cut/etc. things appropriately).

Alright, the new changelist, completely replacing the one in the issue OP, is as follows:

[ ] Fix all seeds at 256 bits.
[ ] Display seeds as BIP39 mnemonics rather than hex strings.
[ ] Display BIP32 wallets as generated from the BIP39 mnemonic. That does a KDF that takes an optional password.
[ ] Remove the optional 'password' salt, but do support inputting a password alongside the mnemonic.
[ ] Rather than generating one ownership seed from a ticket, we need to be able to generate various ownership seeds from a ticket. This means that what we currently call the ownership seed needs to be salted and hashed, just like is done for the other seeds. Type here should be 'owner'.

Yes, we keep the ship number and revision parts of the salt, but the UI will (at least initially) just default to 0 for both, as a default "Urbit-style derivation path". The UI will also default to "no password" for the mnemonics initially. Neither of these UI defaults are anything the lib needs to care about, but just fyi.
Wallet spec will be updated with this soon. @msutherl please double-check this changelist and ping here when the wallet spec has been updated.

@msutherl we missed the BIP32 derivation path, which I've now added to the changelist.

To clarify, are we doing BIP39 mnemonics also for networking seeds? Or just hex there?

The hex is an intermediate representation that doesn't need to be exposed. BIP39 mnemonics are the output.

On Oct 24, 2018 at 3:36 PM,  <Fang (mailto:notifications@github.com)>  wrote:
To clarify, are we doing BIP39 mnemonics also for networking seeds? Or just hex there?
—
You are receiving this because you were mentioned.
Reply to this email directly,   view it on GitHub (https://github.com/urbit/keygen-js/issues/32#issuecomment-432851964), or   mute the thread (https://github.com/notifications/unsubscribe-auth/AAB8HgWBn_h5tk0DdCDtTjDbNNO-Yqalks5uoOuAgaJpZM4Xzqis).

But the networking seed is only relevant for Urbit itself, never goes into a hardware wallet or other Eth/Btc-related tech. Is Urbit going to do the mnemonic->seed conversion?
(This is fine, and I already have a lib for doing that, but I want to be explicit about whether we're doing that or not.)

@msutherl woah, I totally misread that.  Couldn't the Management Seed just as well be used to derive the networking keys?


support of openvpn 2.5.1

Hello,
the script support openvpn 2.5.1?
I am thinking to use openvpn repositories in debian 10 but i not know if the installer is optimized for version 2.5.1

try it. and give feed back ;)


28 integration tests export data from oracle to xml file

Integrations tests. Test scenarios with Oracle database reader and XML file writer. Closes #28.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

64 of 64 (100.0%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
814

Relevant Lines:
814

💛  - Coveralls


Fix #310

This also adds a template for bug submission

There is a test for this that should be changed:
https://github.com/IronLanguages/ironpython2/blob/55c538f9ec9a387f76fc4d114edeb9619d2df79f/Tests/test_stdconsole.py#L164

Yeah, I saw that after I created the pr and didn't get back to it today


Changes according to PR #1

Don't worry, seems much but isn't.

As we discussed, I'd create a new Plugin, which we could call COWorkflows. We could then put in all the removed scripts and not break compatibility. How about that? Don't know yet, where to git/host it though.

But, if you keep the scripts that you have removed here, why did you remove them here in the at all? What is the advantage to separate the Groovy/Java code from the Bash code in different plugins? (And BTW, are there functions in the Groovy code that call Bash scripts? These I would not move!)

The problem is, that I do not know, who wrote which script and how they can be published. The COWorkflows Plugin would be for internal use, whereas the proposed form would only keep non-problematic parts.

Well I could just ask around a few people. Still I don't know who wrote what.

O.k. -- now I get it. Good reason. Can we call the new plugin something else than a previously existing plugin? Maybe "COWorkflowInternal"?

Closed because of #4
This is a corrected version branched off of the proper base. Also at least some of the files are checked for usage.


Clean up Doze

Sensors is buggy, disable it. Move doze code into a device wrapper.

Fixed in pull #34


WSL xrdp issue (works in 2.0.4, doesn't work in 2.0.9)

Windows Version
Microsoft Windows [Version 10.0.19045.3693]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[ ] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-1
Distro Version
Ubuntu 22.04
Other Software
xrdp
Repro Steps
I've developed steps for using a full desktop environment (via mstsc and xrdp).  Over the past few months I've tested
Budgie
Cinnamon
Enlightenment
GNOME
KDE
LXDE
LXQT
MATE
Xfce
I periodically re-test (to make sure my steps work).  I have confirmed that works in 2.0.4 does NOT work in 2.0.9+
EUD-WSLwithdesktop-081223-1524-4.pdf
I just installed a fresh 22.04 instance on wsl 2.0.4 with GNOME.  I was immediately able to RDP to the desktop (via mstsc and xrdp).  I can see the dock and use apps.
After I update wsl to 2.0.9 - I can connect to xrdp and login, but I don't get a desktop.  If I install fresh under 2.0.9, I see the same behavior.
Expected Behavior
Consistent xrdp behavior between 2.0.4 and 2.0.9+
Actual Behavior
Inconsistent xrdp behavior between 2.0.4 and 2.0.9+
Diagnostic Logs
No response

@OneBlue  - I appreciate the info.  I haven't been upgrading as regularly as normal due to the recent issues with wsl-vpnkit.  Whatever this change is, it seems to impact multiple desktop environments (budgie, GNOME, KDE).   Xfce seems to still work on  2.0.14.  Appreciate your hard work.

Thanks much for the redirect.  I'm happy to provide any details as would be useful.

I would love to get someone to chime in on this?

So I decided to try to reset everything and try again.  I've uninstalled all the WSL bits and installed wsl 2.0.4.
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.58
MSRDC version: 1.2.4485
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25880.1000-230602-1350.main
Windows version: 10.0.19045.3803
I've installed Ubuntu 22.04 and the GNOME desktop.  I can connect to xrdp via remote desktop, no problem.

I shutdown the instances and update wsl to 2.0.14.
wsl --shutdown
wsl --update
wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.3803
I restart the Ubuntu instance and connect again:

Literally nothing has changed in the 5 minutes except upgrading wsl from 2.0.4 to 2.0.14.

@blakeduffey you don't happen to have somewhere on the logs something about dxgkrnl and/or ioctl failed, do you?

@blakeduffey when possible, can you recheck if those errors appear on WSL 2.0.4?

@Segment0895 - I will try that today and report back.

So I uninstalled WSL, installed WSL 2.04 (the Ubuntu instance is unchanged, I just left if.

Thanks

@Segment0895 - it was not :)
I thought I fixed it before anyone saw it.  I've replaced.

Ok, one theory down.
I'm out of ideas for now.
Thanks for your feedback! Maybe someone else can pick it up from here.

@Segment0895 -
So I tested again (wsl --shutdown and restart)
Connecting to RDP I do see:
/var/log/kern.log:Jan 31 14:58:37 1556579G-M29296 kernel: [    0.325213] hv_vmbus: registering driver dxgkrnl
/var/log/kern.log:Jan 31 14:58:37 1556579G-M29296 kernel: [    1.644580] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/kern.log:Jan 31 14:58:37 1556579G-M29296 kernel: [    3.254461] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/kern.log:Jan 31 14:59:00 1556579G-M29296 kernel: [   37.413300] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/kern.log:Jan 31 14:59:00 1556579G-M29296 kernel: [   37.858868] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/kern.log:Jan 31 14:59:00 1556579G-M29296 kernel: [   37.955305] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/kern.log:Jan 31 14:59:00 1556579G-M29296 kernel: [   38.066750] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/kern.log:Jan 31 14:59:01 1556579G-M29296 kernel: [   38.303145] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/kern.log:Jan 31 14:59:02 1556579G-M29296 kernel: [   39.926727] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/kern.log:Jan 31 14:59:03 1556579G-M29296 kernel: [   40.751973] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/syslog:Jan 31 14:58:37 1556579G-M29296 kernel: [    0.325213] hv_vmbus: registering driver dxgkrnl
/var/log/syslog:Jan 31 14:58:37 1556579G-M29296 kernel: [    1.644580] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/syslog:Jan 31 14:58:37 1556579G-M29296 kernel: [    3.254461] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/syslog:Jan 31 14:59:00 1556579G-M29296 kernel: [   37.413300] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/syslog:Jan 31 14:59:00 1556579G-M29296 kernel: [   37.858868] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/syslog:Jan 31 14:59:00 1556579G-M29296 kernel: [   37.955305] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/syslog:Jan 31 14:59:00 1556579G-M29296 kernel: [   38.066750] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/syslog:Jan 31 14:59:01 1556579G-M29296 kernel: [   38.303145] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/syslog:Jan 31 14:59:02 1556579G-M29296 kernel: [   39.926727] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22
/var/log/syslog:Jan 31 14:59:03 1556579G-M29296 kernel: [   40.751973] misc dxg: dxgk: dxgkio_query_statistics: Ioctl failed: -22

Confirm it also happens with XFCE. On XFCE it just happens when opening an app such as the terminal.
Apr 03 10:23:36 MYMACHINENAME kernel: potentially unexpected fatal signal 6. Apr 03 10:23:36 MYMACHINENAME kernel: CPU: 9 PID: 6881 Comm: x-terminal-emul Not tainted <IP_ADDRESS>-microsoft-standard-WSL> Apr 03 10:23:36 MYMACHINENAME kernel: RIP: 0033:0x7f3891a6ae2c Apr 03 10:23:36 MYMACHINENAME kernel: Code: ff ff 0f 46 ea eb 89 0f 1f 80 00 00 00 00 b8 ba 00 00 00 0f 05 89 c3 e8 02 a6 > Apr 03 10:23:36 MYMACHINENAME kernel: x-terminal-emul[6875]: segfault at 10 ip 00005561bcc4d87c sp 00007ffdfee57ac0 error 4 Apr 03 10:23:36 MYMACHINENAME kernel: RSP: 002b:00007f387a3ecf20 EFLAGS: 00000246 ORIG_RAX:<PHONE_NUMBER>0000ea Apr 03 10:23:36 MYMACHINENAME kernel: RAX:<PHONE_NUMBER>000000 RBX:<PHONE_NUMBER>0019e7 RCX: 00007f3891a6ae2c Apr 03 10:23:36 MYMACHINENAME kernel: RDX:<PHONE_NUMBER>000006 RSI:<PHONE_NUMBER>0019e7 RDI:<PHONE_NUMBER>0019e1 Apr 03 10:23:36 MYMACHINENAME kernel: RBP: 00007f387a3ee6c0 R08:<PHONE_NUMBER>000000 R09: 00007f387a3eca30 Apr 03 10:23:36 MYMACHINENAME kernel: R10:<PHONE_NUMBER>000008 R11:<PHONE_NUMBER>000246 R12:<PHONE_NUMBER>000006 Apr 03 10:23:36 MYMACHINENAME kernel: R13:<PHONE_NUMBER>000004 R14:<PHONE_NUMBER>000004 R15: 00007f3891be0200 Apr 03 10:23:36 MYMACHINENAME kernel:  in zutty[5561bcc33000+33000] Apr 03 10:23:36 MYMACHINENAME kernel: FS:  00007f387a3ee6c0 GS:<PHONE_NUMBER>000000

Just so this thread doesn't completely fade into oblivion
This issue persists on wsl version <IP_ADDRESS>
Versions of WSL up to 2.0.4 - I was able to install a desktop environment and connect via xrdp (I have documentation for Budgie, Cinnamon, MATE, Xfce, Enlightenment, GNOME, KDE, LXDE and LXQT).  After 2.0.4 (and up to <IP_ADDRESS>) - this no longer works.

Encountered the same issue on xrdp with Ubuntu 22.04. I haven't tried myself, but, maybe updating the Ubuntu version to 24.04 could solve this? Saw someone from YouTube doing the exact steps as I am, and his xrdp worked.
wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-2
WSLg version: 1.0.61
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26091.1-240325-1447.ge-release
Windows version: 10.0.22631.4169


Fix paging in volunteers and requests views

Jump to last page doesn't work well, maybe allow jump to specific page (long page list)

Show several pages in each direction, and fix jump to last (is now hard-coded for page 40)


Add onClick property.

Added onClick property, and description for it in Readme.md.

This is now include in the new react-avatar version 2.5.0 🎉.


Storage in gist/github

The way d3 blocks are organized, we can provide https://lab.audio/user/proj namespace mirroring gists as https://gist.github.com/use/proj, see https://bl.ocks.org/-/about, http://blockbuilder.org/

[ ] able to switch storage

Example: https://github.com/usmakestwo/githubDB
Would be nice to let user log in via github.


[Feature]    add some extra core table conf params under the CDC Ingestion with whole db synchronize mode

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
Due to difference data rows range between tables in a MySQL database, we hope to customize some table parameters （such as bucket, sink parallelism, etc)  during the synchronization of the entire CDC database .
as below:
orginal code :
<FLINK_HOME>/bin/flink run
/path/to/paimon-flink-action-0.5-SNAPSHOT.jar
mysql-sync-database
--warehouse hdfs:///path/to/warehouse
--database test_db
--mysql-conf hostname=<IP_ADDRESS>
--mysql-conf username=root
--mysql-conf password=123456
--mysql-conf database-name=source_db
--catalog-conf metastore=hive
--catalog-conf uri=thrift://hive-metastore:9083
--table-conf bucket=1
--table-conf changelog-producer=input
--table-conf sink.parallelism=1
--including-tables 'product|user|address|order'
add some extral table conf params like "--including-tables-buckets" and “--including-tables-sink.parallelism” :
<FLINK_HOME>/bin/flink run
/path/to/paimon-flink-action-0.5-SNAPSHOT.jar
mysql-sync-database
--warehouse hdfs:///path/to/warehouse
--database test_db
--mysql-conf hostname=<IP_ADDRESS>
--mysql-conf username=root
--mysql-conf password=123456
--mysql-conf database-name=source_db
--catalog-conf metastore=hive
--catalog-conf uri=thrift://hive-metastore:9083
--table-conf bucket=1
--table-conf changelog-producer=input
--table-conf sink.parallelism=1
--including-tables 'product|user|address|order'
--including-tables-buckets 'user:2|order:3'
--including-tables-sink.parallelism 'order:3'
Solution
No response
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

I think it is necessary to support more flexible table-level configuration in the CDC batch synchronization tool, and I am willing to participate in implementing this feature.
However, before we start implementing it, we need to discuss the way of parameter configuration and find a flexible, easy-to-extend, and error-resistant form.
I have found several ways of configuration:
Option 1
As @fujianhua168 suggested,  add the configuration name as a suffix to the parameter name, configure the value for each table separately in the parameter value, and use | to separate each table, like --including-tables-buckets 'user:2|order:3' and --including-tables-sink.parallelism 'order:3'.
This configuration method is relatively concise, but I am concerned that the format of the parameter value might become complex. This could lead to potential parsing errors when dealing with configuration values that include special characters in the future.
BTW, I think rather than using --including-tables-buckets as the parameter name, --table-conf-buckets may be more suitable.
Option 2
Keep the configuration method the same as the current table-conf,  but allow the table name to be added as a suffix after table-conf to declare that it is a configuration for a specific table, like --table-conf-user buckets=2 and --table-conf-order buckets=3.
This configuration method maintains a more consistent structure with the existing table-conf and is safer in value parsing. However, compared to Option 1, it may require users to configure more configuration items.
@fujianhua168 @JingsongLi, what do you think about it?
I also hope that more users of synchronization tools can participate in the discussion of parameter configuration methods. And do not hesitate to share your ideas for better configuration methods.

Supporting configured buckets number in table level is a reasonable requirement from my side, the requirement should be supported in MySQL CDC source firstly and then apply to Paimon Community. About the two approach, I prefer the first one as MySQL-CDC/Debezium has similar options like include-table.list.

I agree with @leonardBang. In my opinion, we can use format:
--table-conf-buckets  a=1,b=2,c=3

Thanks a lot for your reply.

Supporting configured buckets number in table level is a reasonable requirement from my side, the requirement should be supported in MySQL CDC source firstly and then apply to Paimon Community.

As I understood, table configuration like buckets is mainly used when the synchronization tool needs to create the Paimon table automatically. So I don't understand why this is related to CDC source.

About the two approach, I prefer the first one as MySQL-CDC/Debezium has similar options like include-table.list.

Option 1 is quite okay, but I did not find the include-table.list configuration example in MySQL-CDC/Debezium options: https://ververica.github.io/flink-cdc-connectors/master/content/connectors/mysql-cdc.html#connector-options

I agree with @leonardBang. In my opinion, we can use format: --table-conf-buckets a=1,b=2,c=3

--table-conf-buckets  a=1,b=2,c=3 format is quite better.

https://debezium.io/documentation/reference/stable/connectors/mysql.html#mysql-property-table-include-list

This feature is also useful on MySQL CDC side, where different tables can have different chunk (split) sizes.
Using a comma-separated list should be okay.

I think we can use regular expression ,it can use fewer configurations to express more scenarios, for example, --table-conf-buckets order.*=1 , user.*=2, shop=3 , all the tables with order prefix will has one bucket . if some table match many regular expression, we can adopt the first .

Thanks a lot for your meaningful suggestion.
I would like to support regular expressions for table name patterns in this new configuration like --including-tables do.


Fix Windows MSVC Compilation

Clang and Ninja can be a bit squirrely to work with on Windows, but commenting out this section in norm_test.cc allows the rest of the system to compile and run great with MSVC!
EDIT: Also, you folks might appreciate this little hobby project I've been working on on the side:
https://github.com/zalo/mujoco_wasm
https://zalo.github.io/mujoco_wasm

Ah, perhaps it's addressed by this commit:
https://github.com/deepmind/mujoco_mpc/pull/89/commits/1106f7413ede56a59b77360f1ee8abe4b915cc24
And may get rolled in when #89 gets merged...   I'll test that PR.

Nope, MSVC still dies on NormTest.cc, even in that PR with the inscrutable norm_test.cc(97): fatal error C1001: Internal compiler error.:
26>------ Build started: Project: task_test, Configuration: Release x64 ------
26>Building Custom Rule C:/Repositories/mujoco_mpc/mjpc/test/tasks/CMakeLists.txt
21>C:\Repositories\mujoco_mpc\mjpc\test\agent\norm_test.cc(97): fatal error C1001: Internal compiler error.
21>(compiler file 'D:\a\_work\1\s\src\vctools\Compiler\Utc\src\p2\main.c', line 213)
21> To work around this problem, try simplifying or changing the program near the locations listed above.
21>If possible please provide a repro here: https://developercommunity.visualstudio.com
21>Please choose the Technical Support command on the Visual C++
21> Help menu, or open the Technical Support help file for more information

Hi John,
Working on a PR https://github.com/zalo/mujoco_wasm/pull/4 right now to pause / unpause and still be able to apply forces / change position of objects.
Could you take a look to see if my logic is correct? I’m basically trying to mimic simulate.cc http://simulate.cc/. I think we should try and leverage mujoco's applyperturbpose and applyperturbforce. A bit stuck at the moment until i figure out the coordinate system.

Kevin

On Mar 21, 2023, at 7:20 PM, Johnathon Selstad @.***> wrote:
Nope, MSVC still dies on NormTest.cc, even in that PR with the inscrutable norm_test.cc(97): fatal error C1001: Internal compiler error.:
26>------ Build started: Project: task_test, Configuration: Release x64 ------
26>Building Custom Rule C:/Repositories/mujoco_mpc/mjpc/test/tasks/CMakeLists.txt
21>C:\Repositories\mujoco_mpc\mjpc\test\agent\norm_test.cc(97): fatal error C1001: Internal compiler error.
21>(compiler file 'D:\a_work\1\s\src\vctools\Compiler\Utc\src\p2\main.c', line 213)
21> To work around this problem, try simplifying or changing the program near the locations listed above.
21>If possible please provide a repro here: https://developercommunity.visualstudio.com
21>Please choose the Technical Support command on the Visual C++
21> Help menu, or open the Technical Support help file for more information
—
Reply to this email directly, view it on GitHub https://github.com/deepmind/mujoco_mpc/pull/88#issuecomment-1478831898, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACQIDCEOEEN7MLJRPPPMXEDW5JOXZANCNFSM6AAAAAAWAJ64FM.
You are receiving this because you are subscribed to this thread.


Short the server name if it's too long

Proposal:
Proposal written by Monkeyyy11
What is the title of your proposal?: Short the server name if it's too long
Is it a suggestion for the website or for the bot?: website
Explain your proposal more accurately (It's best to give as much information as possible, so that we can implement the proposal better): If the discord server name is longer than 30 characters, you should cut it
Why should we add this feature?: Because it doesn't look very nice if the dashboards list on the website is so big: https://i.imgur.com/NZRLnqN.png
ReportID: 93

➤ LenoxBot commented:
Approve:
good suggestion and important
Nickkel#6515

➤ LenoxBot commented:
if the server name is too lang (ex. skajdnkjasndkjasndkjasndkasndkjasndkajsdn), the website cuts it with points: skajdnkja...
Nickkel#6515

➤ LenoxBot commented:
Approve:
I agree with nickkel
Dadi#7808

➤ LenoxBot commented:
Approve:
I agree with nickkel too
Denarioyt#3352


:arrow_up: lodash@4

updates lodash to v4

Thanks for doing this.
Were you able to grok my crappy tests to verify that everything is working?
I'll look into merging this in the next few days.
Thanks again,
;-j

nope i couldn't get your tests to work lol 🙏

Merged with 155f662f02fba473b0d0b24cc1c8369ad8df22c9
Thanks again


Fix:#75 Vertically center Google Icon in login page

Closes #75  Add negative margin top on Google Icon to align with the text.
Try flex also but that didn't worked inspect the code a lot but nothing worked just this negative margin worked to align the google icon with the text.

@talhawebguru  Yeah, I agree, I tried alot to fix this as well. Is this fix responsive? did you try changing the screen sizes including mobile view?

Have you tried?
display: flex;
justify-content: center;
align-items: center;

yes it is responsive as it just a margin top negative to align with text  . it look like this.


Clean up native code

Summary
We moved native code to a different repo, removing them here
How did you test your changes?

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


[11.x] Adds feature to create Resource and Collection with --all flag

I've added a feature to create both files with --all or -a flag.
I've also written a test to ensure everything is working fine.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.